-
Notifications
You must be signed in to change notification settings - Fork 19
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: configuration files do not load asynchronously #236
fix: configuration files do not load asynchronously #236
Conversation
Merge development into main
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.2.0
Merge development into main
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.3.0
Merge development into main
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.4.0
Merge development into main
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.5.0
fix: lockfile updates
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.5.1
Merge development into main
fix: update public key to match new private key
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.5.2
Merge development into main
…ranches--main--components--ubiquity-os-kernel chore(main): release 2.5.3
Merge development into main
…ranches--main chore(main): release 2.5.4
Development to main
…ranches--main chore(main): release 2.5.5
Development into main
…ranches--main chore(main): release 4.0.0
…ranches--main chore(main): release 5.0.0
# Conflicts: # CHANGELOG.md # src/worker.ts
# Conflicts: # CHANGELOG.md
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.
Hope this works
@@ -1,6 +1,6 @@ | |||
name = "ubiquity-os-kernel" | |||
main = "src/adapters/cloudflare-worker.ts" | |||
compatibility_date = "2023-12-06" | |||
compatibility_date = "2024-09-23" |
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.
did you try this before changing to sync config fetch? it could be also that there was a bug in workers and we were using an old version
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.
Yes I did, didn't notice any change of behavior afterwards
Resolves #227
The configuration files seemed to be the bottleneck, and the kernel seems more stable. Now, it can be a pure coincidence and I became superstitious. The best way to find out is to deploy it and monitor it.