-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix initial cursor #54
base: main
Are you sure you want to change the base?
Conversation
* Support .env file * Fix default sub endpoint
* Setup migrations, misc tidy/fixes * Simplify migration provider
readme tweaks
* update README with instructions for the default URL * Update README.md --------- Co-authored-by: Daniel Holmgren <dtholmgren@gmail.com>
* describeFeedGenerator route + multiple feeds * tweak readme
* describeFeedGenerator route + multiple feeds * tweak readme * improve env
* describeFeedGenerator route + multiple feeds * tweak readme * improve env * publish script * create -> put * readme * handle blob encoding * add check that feeds are available
So readers won't have to google Bluesky PDS to try to figure out what it means
(cherry picked from commit 1b2f04a)
* improve docs & helpers around publisher dids * add docs to env
Cosmetic: remove trailing space
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did exactly the same thing in my feed.
Alternative might be (not super familiar with this stack) - leaving the update query alone, but adding a data migration which adds a row into the sub_state
table. But that would require a data migration for each web socket endpoint (service
col).
d36deef
to
fadd462
Compare
Problem
When running for the first time, we only update the cursor but don't create the initial row, so it doesn't update anything.
Solution
Changed the update to an upsert. Ran locally and verified
sub_state
was empty before, and after the change has a single row.