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

ISS Debugging with Blocks #17265

Open
1 of 2 tasks
poulok opened this issue Jan 8, 2025 · 0 comments
Open
1 of 2 tasks

ISS Debugging with Blocks #17265

poulok opened this issue Jan 8, 2025 · 0 comments
Assignees
Labels
Epic A body of work that can be broken down into specific tasks. Platform Tickets pertaining to the platform

Comments

@poulok
Copy link
Member

poulok commented Jan 8, 2025

Background Information can be found here.

The purpose of this epic is to provide ISS debugging information that is easily accessible to developers. After Mega Map is implemented, the only useful information for debugging ISSes will be the block data for the round that had the ISS. To get this data, these steps should be taken:

  1. Platform notifies the application when an ISS has occurred and for what round.
  2. The application locates the block for the associated round.
  3. The application uploads that block to a GCP bucket.

This process is temporary because the long term plan is to move ISS detection to the application layer and this extra platform-app communication will no longer be needed. Until that point, we can use the NotificationEngine to achieve step 1.

Tasks

Preview Give feedback
  1. Platform
    timfn-hg
  2. Backlog Grooming
@poulok poulok added Epic A body of work that can be broken down into specific tasks. Platform Tickets pertaining to the platform labels Jan 8, 2025
@poulok poulok self-assigned this Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic A body of work that can be broken down into specific tasks. Platform Tickets pertaining to the platform
Projects
None yet
Development

No branches or pull requests

1 participant