Skip to content
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

Misbehaviour tech-debt #3351

Open
8 tasks
ancazamfir opened this issue May 19, 2023 · 1 comment
Open
8 tasks

Misbehaviour tech-debt #3351

ancazamfir opened this issue May 19, 2023 · 1 comment
Labels
I: refactoring O: misbehaviour Objective: related to misbehaviour detection
Milestone

Comments

@ancazamfir
Copy link
Collaborator

ancazamfir commented May 19, 2023

Summary of Bug

During work on #3224, @romac raised some questions and we decided to follow up with a different issue. Here they are:

Version

Steps to Reproduce

Acceptance Criteria


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@seanchen1991
Copy link
Contributor

How extensive is the work outlined in this issue? Just wondering whether this should go in the 1.5.1 or 1.6 milestone.

@seanchen1991 seanchen1991 added I: refactoring O: misbehaviour Objective: related to misbehaviour detection labels Jun 1, 2023
@seanchen1991 seanchen1991 added this to the v1.7 milestone Jun 6, 2023
@romac romac modified the milestones: v1.7, Refactor sink Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: refactoring O: misbehaviour Objective: related to misbehaviour detection
Projects
Status: 📥 Todo
Development

No branches or pull requests

3 participants