Upgrade to dbos 3 - #685
Merged
Merged
Conversation
czpython
force-pushed
the
ksocha/dru-628-upgrade-to-dbos-3
branch
2 times, most recently
from
October 3, 2026 09:46
d7b9da7 to
9c47130
Compare
DBOS 3.0 removed in-memory Queue() and @DBOS.scheduled; register queues after launch so a PyPI install can load the pytest plugin again. Co-authored-by: Cursor <cursoragent@cursor.com>
czpython
force-pushed
the
ksocha/dru-628-upgrade-to-dbos-3
branch
from
October 3, 2026 09:53
9c47130 to
3f31ead
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow the DBOS Python 3.0 upgrade: queues persist in the system database and must be registered after launch, so
Queue()at import is gone. Depend ondbos>=3.2,<4.druks,druks_tasks,druks_chat_pauses, anddruks_notificationswithregister_queue_asyncafterDBOS.launch()(launch already runs on the serving loop).DBOS.enqueue_workflow_async.application_database_url; the system URL already points at the app database.@DBOS.scheduledtask ticks withapply_schedulesafter launch. A task'severy=stays a fixed UTC cadence; workflow schedules keep the installation timezone.Do not run 2.x and 3.x processes against the same database at once: 3.x can recover 2.x workflows, not the reverse.