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

Complete the AMQP adapter in Python for CleverSwarm integration #1

New issue
Closed
opened 2025-01-08 20:44:31 +00:00 by stanislav.hejny · 12 comments
stanislav.hejny commented 2025-01-08 20:44:31 +00:00 (Migrated from git.cleverthis.com)
Copy link

Ref epic: CleverSwarm Onboarding #58

Write python code that

  1. replicates the AMQ Adapter Java code function for route management and discovery
  2. connects to RabbitMQ,
  3. receives DataMessage
  4. invokes corresponding function in cleverswarm-endpoints, providing correct input arguments
  5. relays response back to the caller via RabbitMQ
Ref epic: [CleverSwarm Onboarding #58](https://git.cleverthis.com/clevermicro/clevermicro/issues/58) Write python code that 1. replicates the AMQ Adapter Java code function for route management and discovery 2. connects to RabbitMQ, 3. receives DataMessage 4. invokes corresponding function in cleverswarm-endpoints, providing correct input arguments 5. relays response back to the caller via RabbitMQ
stanislav.hejny commented 2025-01-08 20:45:19 +00:00 (Migrated from git.cleverthis.com)
Copy link

assigned to @stanislav.hejny

assigned to @stanislav.hejny
stanislav.hejny commented 2025-01-08 20:45:33 +00:00 (Migrated from git.cleverthis.com)
Copy link

added to epic &4

added to epic &4
stanislav.hejny commented 2025-01-28 11:01:15 +00:00 (Migrated from git.cleverthis.com)
Copy link

changed the description

changed the description
stanislav.hejny commented 2025-02-16 23:03:19 +00:00 (Migrated from git.cleverthis.com)
Copy link

added 1d of time spent at 2025-02-12

added 1d of time spent at 2025-02-12
stanislav.hejny commented 2025-02-16 23:03:28 +00:00 (Migrated from git.cleverthis.com)
Copy link

added 1d of time spent at 2025-02-11

added 1d of time spent at 2025-02-11
stanislav.hejny commented 2025-02-26 10:51:42 +00:00 (Migrated from git.cleverthis.com)
Copy link

mentioned in commit 1f9040729f

mentioned in commit 1f9040729f4a68feb5e69ffb0e9b64db8ffab6bf
stanislav.hejny commented 2025-02-26 20:30:28 +00:00 (Migrated from git.cleverthis.com)
Copy link

mentioned in commit 1b0421964c

mentioned in commit 1b0421964c5230fa71f279c73c737fa5c19cc536
stanislav.hejny commented 2025-02-28 12:03:53 +00:00 (Migrated from git.cleverthis.com)
Copy link

mentioned in commit e8f4abdfaf

mentioned in commit e8f4abdfaf81a856980491c0cb31de5713e44bf5
stanislav.hejny commented 2025-02-28 12:07:34 +00:00 (Migrated from git.cleverthis.com)
Copy link

added 1d of time spent at 2025-02-27

added 1d of time spent at 2025-02-27
stanislav.hejny commented 2025-02-28 12:07:44 +00:00 (Migrated from git.cleverthis.com)
Copy link

added 1d of time spent

added 1d of time spent
freemo commented 2025-05-05 00:51:24 +00:00
Owner
Copy link

@stanislav.hejny @aleenaumair

tickets that are not epic/legendary should never be assigned until work starts on them. Team members do not take ownership over tickets and anyone should be free to take any ticket at any time. Please ensure this ticket description is sufficient for anyone to fully understand the need and be able to vote on points without verbal explanation. Me reading this ticket, for example, does not understand why the AMQP adapter needs to be specifically rewritten for Swarm. Isnt the whole point to write it in a way that is reusable for each service?

Moreover tickets must have point assignments completed before they can be MoSCowed. Since this ticket is not yet ready for MoSCow it will not be evaluated yet.

This ticket is also lacking priority (which needs to be set to backlog) as well as a milestone.

@stanislav.hejny @aleenaumair tickets that are not epic/legendary should never be assigned until work starts on them. Team members do not take ownership over tickets and anyone should be free to take any ticket at any time. Please ensure this ticket description is sufficient for anyone to fully understand the need and be able to vote on points **without** verbal explanation. Me reading this ticket, for example, does not understand why the AMQP adapter needs to be specifically rewritten for Swarm. Isnt the whole point to write it in a way that is reusable for each service? Moreover tickets **must** have point assignments completed before they can be MoSCowed. Since this ticket is not yet ready for MoSCow it will not be evaluated yet. This ticket is also lacking priority (which needs to be set to backlog) as well as a milestone.
aleenaumair commented 2025-05-06 10:01:53 +00:00
Member
Copy link

The code under this ticket is already committed prior to ForgeJo migration and is under testing with the Swarm team. closing this ticket as it is completed.

The code under this ticket is already committed prior to ForgeJo migration and is under testing with the Swarm team. closing this ticket as it is completed.
aleenaumair 2025-05-06 10:01:54 +00:00
aleenaumair added this to the V.01 milestone 2025-05-06 10:02:34 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
hack
feat/76
feat/75_refactor_code
feat/74
api_docs
feat/63-cleverswarm-unidirectional
feat/61-multi-user-support
feat-58-backpressure-reactive-streams
fix/bp-report
otel-demo
cleverbrag-integration-2
cleverbrag-integration
code-formatting
errors-as-json
config-documemntation
fix-version
feat/#1
fix_testing
feat/readme
feat#2
feat#64
No results found.
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
V.01
Projects
Clear projects
No items
No project
Sprint May 15th - 28th
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
You do not have permission to read 1 dependency
Reference: clevermicro/amq-adapter-python#1
No description provided.
Delete branch "%!s()"

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?