-
Notifications
You must be signed in to change notification settings - Fork 132
feat:UI/UX enhancement added using material UI library #226
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
Open
vaishcodescape
wants to merge
8
commits into
AOSSIE-Org:main
Choose a base branch
from
vaishcodescape:aditya/features
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
74914b2
feat:UI enhancement features added using material UI
vaishcodescape 11f1e5a
chore: update poetry.lock with new greenlet musllinux wheels and enha…
vaishcodescape c589df7
fix: clean up imports in Navbar and improve button hover effect in Bu…
vaishcodescape 364a351
feat: integrate MUI icons and enhance footer, navbar, hero, and waitl…
vaishcodescape f372653
refactor: remove unused index.ts file, enhance Footer and Navbar comp…
vaishcodescape 371a1e3
refactor: remove hover effect from ArrowUpIcon in Footer and prevent …
vaishcodescape af351a4
fix: add href attribute to MuiLink in Footer component for improved n…
vaishcodescape 513d470
refactor: update AsyncQueueManager to use a single RabbitMQ priority …
vaishcodescape File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 111
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 310
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 92
🏁 Script executed:
# Read the queue_manager.py file to see complete implementation cat -n ./backend/app/core/orchestration/queue_manager.pyRepository: AOSSIE-Org/Devr.AI
Length of output: 7410
🏁 Script executed:
# Check pyproject.toml and requirements.txt for aio-pika version cat ./pyproject.tomlRepository: AOSSIE-Org/Devr.AI
Length of output: 2034
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 2098
🌐 Web query:
aio-pika 9.5.5 DeliveryMode PERSISTENT RabbitMQ durable queue💡 Result:
To make messages survive a RabbitMQ broker restart with aio-pika 9.5.5, you need both:
delivery_mode=DeliveryMode.PERSISTENT, i.e. AMQPdelivery-mode = 2). [1][2]Notes:
publisher_confirms=True). [1][4]Sources:
[1] aio-pika tutorial (Work Queues: durable queue +
DeliveryMode.PERSISTENT, confirms note) (docs.aio-pika.com)[2] RabbitMQ docs (Queues: durability + persistent publishing requirement) (rabbitmq.com)
[3] aio-pika API reference (channel
publisher_confirms: bool = True) (docs.aio-pika.com)[4] RabbitMQ docs (Confirms: persistent-to-durable implies disk persistence before ack) (rabbitmq.com)
Citations:
🌐 Web query:
RabbitMQ message persistence vs queue durability delivery_mode💡 Result:
In RabbitMQ (AMQP 0-9-1), queue/exchange “durability” and message “persistence” (
delivery_mode) are different knobs:1) Durable queue / durable exchange (metadata durability)
durable=trueon a queue or exchange means its definition/metadata is stored so it can be recreated after a broker restart. (rabbitmq.com)2)
delivery_mode/ persistent message (message durability)delivery_mode=2(many clients expose this aspersistent: true). (rabbitmq.com)delivery_mode=1) are discarded during recovery, even if they were in a durable queue. (rabbitmq.com)The key rule (what you usually want)
To survive a broker restart, you generally need:
delivery_mode=2) (so the messages are recovered). (rabbitmq.com)Important reliability note: persistence ≠ guaranteed
Even with
delivery_mode=2and durable queues, a message can still be lost if the broker fails before it’s actually flushed to disk. To know when it’s safely stored, enable publisher confirms (then the confirm for a persistent message routed to a durable queue is sent only after it’s persisted). (rabbitmq.com)Citations:
Add persistent delivery mode to survive broker restarts.
Queue durability and message persistence are separate in RabbitMQ—the durable queue metadata survives restarts, but without
delivery_mode=DeliveryMode.PERSISTENT, messages themselves are transient and discarded on broker recovery, causing task loss.Proposed fix
🤖 Prompt for AI Agents