clevermicro/amq-adapter-python
clevermicro/amq-adapter-python
14
0
Fork 0
Code Issues 22 Pull requests 4 Projects Releases Packages 1 Wiki Activity Actions

feat-58-backpressure-reactive-streams #59

Closed
stanislav.hejny wants to merge 0 commits from feat-58-backpressure-reactive-streams into develop
pull from: feat-58-backpressure-reactive-streams
merge into: clevermicro:develop
Conversation 9 Commits - Files changed -
stanislav.hejny commented 2025-07-11 21:54:20 +00:00
Member
Copy link
No description provided.
Feat #58 - fix backpressure logic and update tests
Some checks failed
Unit test coverage / pytest (push) Failing after 1m17s
Details
/ build-and-push (push) Successful in 1m29s
Details
7fd1c62596 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
feat #58 - publish docker image with demo app
Some checks failed
Build and Publish Docker Image / build-and-push (push) Waiting to run
Details
Unit test coverage / pytest (push) Failing after 1m20s
Details
/ build-and-push (push) Successful in 1m30s
Details
98129b86d0
feat #58 - publish docker image with demo app, fix test case
Some checks failed
Unit test coverage / pytest (push) Failing after 1m19s
Details
/ build-and-push (push) Successful in 1m26s
Details
Build and Publish Docker Image / build-and-push (push) Has been cancelled
Details
2ab2509a55
upgrade python_multipart version for demo
Some checks failed
Build and Publish Docker Image / build-and-push (push) Waiting to run
Details
Unit test coverage / pytest (push) Failing after 1m13s
Details
/ build-and-push (push) Successful in 1m28s
Details
ed75f5d002
 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Use image from repo rather than local build
Some checks failed
Unit test coverage / pytest (push) Failing after 1m15s
Details
/ build-and-push (push) Successful in 1m26s
Details
Build and Publish Docker Image / build-and-push (push) Has been cancelled
Details
fde6f17b58
fix(General): fix for cm-dev deployment
Some checks failed
Build and Publish Docker Image / build-and-push (push) Waiting to run
Details
Unit test coverage / pytest (push) Failing after 1m32s
Details
/ build-and-push (push) Successful in 1m35s
Details
771154facd
fix: update routing key
Some checks failed
Unit test coverage / pytest (push) Failing after 1m14s
Details
/ build-and-push (push) Successful in 1m24s
Details
Build and Publish Docker Image / build-and-push (push) Has been cancelled
Details
38e5b532cf
 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
add consul configuration
Some checks failed
Unit test coverage / pytest (push) Failing after 1m19s
Details
/ build-and-push (push) Successful in 1m25s
Details
Unit test coverage / pytest (pull_request) Failing after 1m24s
Details
Build and Publish Docker Image / build-and-push (push) Has been cancelled
Details
5075f510e9 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
feature/58 - update unit tests for coverage
Some checks failed
Unit test coverage / pytest (push) Successful in 1m39s
Details
Unit test coverage / pytest (pull_request) Successful in 1m46s
Details
/ build-and-push (push) Successful in 1m52s
Details
Build and Publish Docker Image / build-and-push (push) Has been cancelled
Details
f8fd9f24f8
forgejo-actions commented 2025-07-15 16:15:01 +00:00
Copy link

Coverage is 86%

Coverage is 86%
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
feat/58 - simplify complex logic
Some checks failed
Build and Publish Docker Image / build-and-push (push) Waiting to run
Details
Unit test coverage / pytest (push) Failing after 1m32s
Details
Unit test coverage / pytest (pull_request) Failing after 1m38s
Details
/ build-and-push (push) Successful in 1m46s
Details
a6c918fe43 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
feat/#50 - remove obsolete code
Some checks failed
Build and Publish Docker Image / build-and-push (push) Waiting to run
Details
Unit test coverage / pytest (push) Failing after 1m24s
Details
Unit test coverage / pytest (pull_request) Failing after 1m56s
Details
/ build-and-push (push) Successful in 2m0s
Details
f2cc138540 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
fix: ensure AsyncMock returns awaitable channel in test_initialize
Some checks failed
Unit test coverage / pytest (push) Successful in 1m37s
Details
Unit test coverage / pytest (pull_request) Successful in 1m46s
Details
/ build-and-push (push) Successful in 1m46s
Details
Build and Publish Docker Image / build-and-push (push) Has been cancelled
Details
050b5ddba4 
Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>
forgejo-actions commented 2025-07-18 08:32:40 +00:00
Copy link

Coverage is 87%

Coverage is 87%
feat/#58 - fix unit test and deployment pipeline
Some checks failed
Unit test coverage / pytest (push) Successful in 1m55s
Details
Unit test coverage / pytest (pull_request) Successful in 1m52s
Details
/ build-and-push (push) Successful in 1m58s
Details
Build and Publish Docker Image / build-and-push (push) Failing after 5m12s
Details
d8ab0b861d
forgejo-actions commented 2025-07-21 09:54:59 +00:00
Copy link

Coverage is 87%

Coverage is 87%
forgejo-actions commented 2025-07-21 10:27:04 +00:00
Copy link

Coverage is 87%

Coverage is 87%
hurui200320 force-pushed feat-58-backpressure-reactive-streams from bb5e147c63 to a71d3b3f2a 2025-07-21 10:28:17 +00:00 Compare
hurui200320 force-pushed feat-58-backpressure-reactive-streams from a71d3b3f2a to 80a55f9894 2025-07-21 10:29:16 +00:00 Compare
forgejo-actions commented 2025-07-21 10:35:05 +00:00
Copy link

Coverage is 87%

Coverage is 87%
stanislav.hejny commented 2025-07-23 17:43:33 +00:00
Author
Member
Copy link

merged to develop branch

merged to develop branch
stanislav.hejny commented 2025-07-23 17:43:41 +00:00
Author
Member
Copy link

merged to develop branch

merged to develop branch
stanislav.hejny commented 2025-07-23 17:44:05 +00:00
Author
Member
Copy link

merged to develop branch

merged to develop branch
stanislav.hejny commented 2025-07-23 17:47:14 +00:00
Author
Member
Copy link

merged to develop branch

merged to develop branch
stanislav.hejny closed this pull request 2025-07-23 17:47:14 +00:00
All checks were successful
Unit test coverage / pytest (push) Successful in 2m0s
Details
/ build-and-push (push) Successful in 2m4s
Details
Build and Publish Docker Image / build-and-push (push) Successful in 3m5s
Details
Unit test coverage / pytest (pull_request) Successful in 1m7s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.

  
Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
1 man-hours worth of work for an expert with no learning curve.

  
Points
13
13 man-hours worth of work for an expert with no learning curve.

  
Points
2
2 man-hours worth of work for an expert with no learning curve.

  
Points
21
21 man-hours worth of work for an expert with no learning curve.

  
Points
3
3 man-hours worth of work for an expert with no learning curve.

  
Points
34
34 man-hours worth of work for an expert with no learning curve.

  
Points
5
5 man-hours worth of work for an expert with no learning curve.

  
Points
55
55 man-hours worth of work for an expert with no learning curve.

  
Points
8
8 man-hours worth of work for an expert with no learning curve.

  
Points
88
88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
A ticket that represents the same content as an existing ticket.

  
State
In Progress
A ticket that is actively being developed.

  
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Bug
Something that doesnt work as intended.

  
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
An error or improvement needed in the documentation.

  
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
Some new functionality not present.

  
Type
Legendary
A type of Epic which will contain other Epics.

  
Type
Support
Someone needs help using the project.

  
Type
Task
A generic task that doesnt fit into the other type categories.

  
Type
Testing
Work exclusively focusing on fixing or expanding testing.

No labels
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
stanislav.hejny
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#58 Modify backpressure to comply with Reactive Streams specs
clevermicro/amq-adapter-python
Depends on
#60 Fix backpressure report
clevermicro/amq-adapter-python
Reference: clevermicro/amq-adapter-python#59
No description provided.
Delete branch "feat-58-backpressure-reactive-streams"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?