-
Notifications
You must be signed in to change notification settings - Fork 67
Actions not updated for 4 days #293
Comments
I was doing some maintenance a few days ago and forgot to restart a script. Should be better now. |
Thanks. Actions still out of date, but at least some new blocks are showing up in the blocklist. Not all, though! |
Just to second dankegel, the site is up, the list count is up, but actions still seems to be days behind. |
No updates to the block count in 3 days, none to Actions in 9 days. |
Last Actions update was 7 days ago for me. |
I'm at 13 days. It appears that blocks I made during the time the script wasn't running aren't being registered. Any idea how to force a sync? |
It's a server side problem, I think, and we have to wait for the author to debug it. My cargo-cult procedure was to log in to the web site |
I'll give the flick back and forth a try and see if it triggers anything. My lists are still not updating. Update seems out of sync as well as I have one that Actions show last updated 9 days ago but My Blocks last updated 21 days ago. Have checked all 5 of my lists and none are updating. |
A little update here: There was a problem where the update-blocks service was not answering on its RPC port anymore, and so requests triggered by loading "My Blocks" were not making it through. I've restarted the service, so visiting your "My Blocks" page should trigger a refresh (visit once, wait a few minutes, and reload). I'll check back in a little while to see if it stops listening on its RPC port again. There's also another mystery to solve: The update-blocks service is supposed to update everyone's blocks once a day if they have a shared block list, but that doesn't appear to be happening. I'll take a look at that too once I get the chance. Thanks for the reports. If any of you are willing to share your Twitter handle here that would be quite helpful for me in debugging. |
Hi Jacob…thanks for all your efforts on BT; they are very, very greatly appreciated. My Twitter handle is @Paul91701736.
Cheers…
ST
From: Jacob Hoffman-Andrews <[email protected]>
Reply-To: jsha/blocktogether <[email protected]>
Date: Monday, January 27, 2020 at 2:24 PM
To: jsha/blocktogether <[email protected]>
Cc: Scott Tracy <[email protected]>, Author <[email protected]>
Subject: Re: [jsha/blocktogether] Actions not updated for 4 days (#293)
A little update here: There was a problem where the update-blocks service was not answering on its RPC port anymore, and so requests triggered by loading "My Blocks" were not making it through. I've restarted the service, so visiting your "My Blocks" page should trigger a refresh (visit once, wait a few minutes, and reload).
I'll check back in a little while to see if it stops listening on its RPC port again.
There's also another mystery to solve: The update-blocks service is supposed to update everyone's blocks once a day if they have a shared block list, but that doesn't appear to be happening. I'll take a look at that too once I get the chance.
Thanks for the reports. If any of you are willing to share your Twitter handle here that would be quite helpful for me in debugging.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#293?email_source=notifications&email_token=ALH2KPF36PAJLMIOH2MX7TLQ75NIVA5CNFSM4KI2XTO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKBJTZI#issuecomment-578984421>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALH2KPG6PPWYB3M4ULPRMNTQ75NIVANCNFSM4KI2XTOQ>.
|
The one in question for me is science_shield (and I also check whether blocks propagate to dkegel, which subscribes to @science_shield). |
Thanks Jacob! My handle is @vabluebelle18. |
also noted in issue #294 my twitter name is @DhotyaShield - many thanks for your work on this service |
Looks like the action refresh is stuck again. |
How often does it update? I've signed up 2 days or so ago and it says |
It used to update within minutes. |
Update - My Blocks last updated 7 days ago. Actions is now 17/18 days and it is also not reflecting new blocks I have done on Twitter during that time. |
Looking much better today. |
Just checked and my account is now completely caught up after being in suspended animation for 29 days. Thanks!
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Dan Kegel <[email protected]>
Sent: Thursday, February 13, 2020 6:27:45 PM
To: jsha/blocktogether <[email protected]>
Cc: Scott Tracy <[email protected]>; Author <[email protected]>
Subject: Re: [jsha/blocktogether] Actions not updated for 4 days (#293)
Looking much better today.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#293?email_source=notifications&email_token=ALH2KPHFGZ6WCALCS3FL36TRCX6SDA5CNFSM4KI2XTO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELXK35Y#issuecomment-586067447>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALH2KPDFR2QZABWLRNNTKP3RCX6SDANCNFSM4KI2XTOQ>.
|
One account caught up 17 hours ago. The other two still no bueno. |
Account is caught up and BT is now updating in close to real time; this is the best it has ever been since I started using it last April.
From: VaBlueBelle17 <[email protected]>
Reply-To: jsha/blocktogether <[email protected]>
Date: Thursday, February 13, 2020 at 7:16 PM
To: jsha/blocktogether <[email protected]>
Cc: Scott Tracy <[email protected]>, Author <[email protected]>
Subject: Re: [jsha/blocktogether] Actions not updated for 4 days (#293)
One account caught up 17 hours ago. The other two still no bueno.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#293?email_source=notifications&email_token=ALH2KPBJOSVVU6OYZAHMSY3RCYEJ7A5CNFSM4KI2XTO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELXNRKA#issuecomment-586078376>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALH2KPDF5IZKFFSAXJKYSMLRCYEJ7ANCNFSM4KI2XTOQ>.
|
Seems to be frozen again...this is the longest period of no updates I've seen.
The text was updated successfully, but these errors were encountered: