feat/93 #94

Merged

stanislav.hejny merged 9 commits from feat/93 into feat/81 2025-11-03 13:28:38 +00:00

Conversation 0 Commits 9 Files changed 25 +424 -249

stanislav.hejny commented 2025-11-02 10:55:55 +00:00

Member

Copy link

This is to fix the bug where REMOVE_ROUTE from a single replica event disables route for all other existing replicas.
Solution is to have a global unique replica ID in AMQRoute message/object and add it to eq() method on AMQRoute so the only route from single replica is removed from routing table, leaving routes for other replicas intact

This is to fix the bug where REMOVE_ROUTE from a single replica event disables route for all other existing replicas. Solution is to have a global unique replica ID in AMQRoute message/object and add it to __eq__() method on AMQRoute so the only route from single replica is removed from routing table, leaving routes for other replicas intact

stanislav.hejny added 13 commits 2025-11-02 10:55:55 +00:00

ci: rename otdemo test to internal integration test f8f3f56816

ci: update scaling test script 42d9eb48c3

ci: add with s3 variant and update scaling test fd71a1d10e

ci: add test streaming script 3d26a8cc1e

ci: remove resource limit for demo service 945d0e0165

debug: kind cluster setup error d10adace7d

ci: add debug log output c910f78b90

ci: add http endpoint test script 5b2af66a32

ci: remove minio and use s3 to save some resources ... 3b2906ea94

also free up more resources by removing services that we don't need

ci: update amq adapter version f83984cae3

Merge branch 'feat/90' into feat/81 357dc87910

feat/#93: fix bug where REMOVE_ROUTE event on scaling down invalidates routes to all replicas 0d390876a0

feat/#93: fix failing tests after refactor 4681cd287f

stanislav.hejny added 1 commit 2025-11-02 11:06:50 +00:00

feat/#93: do not run integration test when I need to build a wheel file 0a58726825

stanislav.hejny added 1 commit 2025-11-02 11:09:41 +00:00

feat/#93: do not run integration test when I need to build a wheel file e903ade5ad

stanislav.hejny added 1 commit 2025-11-02 11:13:18 +00:00

feat/#93: do not run integration test when I need to build a wheel file, fix build condition 5c310c1573

stanislav.hejny added 1 commit 2025-11-02 11:16:47 +00:00

feat/#93: do not run integration test when I need to build a wheel file, fix build condition f74f0fbf63

stanislav.hejny added 1 commit 2025-11-02 12:14:03 +00:00

feat/#93: do not run integration test when I need to build a wheel file, fix build condition 46e80988ac

stanislav.hejny added 1 commit 2025-11-02 12:15:38 +00:00

feat/#93: do not run integration test when I need to build a wheel file, fix build condition 7b8b443222

stanislav.hejny added 1 commit 2025-11-03 13:28:05 +00:00

Merge branch 'feat/81' into feat/93 5f67332672

stanislav.hejny merged commit 0e2651915d into feat/81 2025-11-03 13:28:38 +00:00

stanislav.hejny referenced this pull request from a commit 2025-11-03 13:28:40 +00:00

Merge pull request 'feat/93' (#94) from feat/93 into feat/81

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

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

clevermicro/amq-adapter-python!94

No description provided.