clevermicro/amq-adapter-python
14
0
Fork 0
Code Issues 16 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

CleverSwarm benchmark compatibility: ensure Errors And All Responses are reported back in formal JSON format #40

New Issue
Closed
opened 2025-05-05 12:29:18 +00:00 by stanislav.hejny · 1 comment
stanislav.hejny commented 2025-05-05 12:29:18 +00:00
Member
Copy Link
Copy Source

CleverSwarm benchmark suite expects, that if error occurs in the application, that the error message is delivered back to caller containing a JSON formatted payload with field 'detail' containing the error message + details as a string

CleverSwarm benchmark suite expects, that if error occurs in the application, that the error message is delivered back to caller containing a JSON formatted payload with field 'detail' containing the error message + details as a string
stanislav.hejny self-assigned this 2025-05-05 12:29:23 +00:00
stanislav.hejny added the
State
Verified
Type
Task
Points
2
 labels 2025-05-05 12:30:03 +00:00
stanislav.hejny added this to the V.01 milestone 2025-05-05 12:30:13 +00:00
stanislav.hejny added this to the Sprint May 1st- 14th project 2025-05-05 12:30:17 +00:00
stanislav.hejny added the
Priority
High
 label 2025-05-06 10:11:58 +00:00
stanislav.hejny changed title from CleverSwarm benchmark compatibility: ensure Errors are reported back in JSON format to CleverSwarm benchmark compatibility: ensure Errors And All Responses are reported back in formal JSON format 2025-05-06 13:54:53 +00:00
stanislav.hejny added
State
Completed
Signed-off: Owner and removed
State
Verified
 labels 2025-05-07 12:23:45 +00:00
stanislav.hejny commented 2025-05-07 12:24:13 +00:00
Author
Member
Copy Link
Copy Source

Implemented as this blocked CleverSwarm integration testing

Implemented as this blocked CleverSwarm integration testing
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 Label
Points
2
Priority
High
 Signed-off: Owner
State
Completed
Type
Task
Milestone
No items
No Milestone V.01
Projects
Clear projects
No project Sprint May 1st- 14th
Assignees
Clear assignees
aleenaumair (Aleena Umair) argocd CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) mngrif (Michael Griffith) org.clevermicro (System User) org.cleverswarm (System User) org.inf-cd salcedo (Brian Salcedo) stanislav.hejny (Stanislav Hejny)
No Assignees stanislav.hejny
1 Participants
Notifications
Due Date
No due date set.
Blocks
You do not have permission to read 1 dependency
Reference: clevermicro/amq-adapter-python#40
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?