minaprotocol / issues-experiment Goto Github PK

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/issues-experiment/discussions

Summary

Is this just for flaky tests? Seems highly specific and maybe should cover build issues more broadly? It seems useful to distinguish pipeline from product issues?

Steps to replicate this Issue

1. start the build
2. run the tests
3. see the fail
   ...

Console output

It runs just fine

Platform

Deb9

Build link(s)

No response

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/issues-experiment/discussions

Description

Vestibulum eu massa in diam convallis bibendum.

Steps to Reproduce

1. Vestibulum eu massa in diam convallis bibendum.
2. Vestibulum eu massa in diam convallis bibendum.
3. Vestibulum eu massa in diam convallis bibendum.

Expected Result

Vestibulum eu massa in diam convallis bibendum.

Actual Result

Vestibulum eu massa in diam convallis bibendum.

Status

Vestibulum eu massa in diam convallis bibendum.

Logs

Vestibulum eu massa in diam convallis bibendum.

Additional information

Vestibulum eu massa in diam convallis bibendum.

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/issues-experiment/discussions

Description

I forgot to include a very good description!

Steps to Reproduce

1. Start daemon
2. Wait a few days
3. See it hang
   ...

Expected Result

It won't hang

Actual Result

It may hang

Status

n/a

Logs

I'll usually share logs to logs@o1 ... seems like open to public is simpler/preferred, but I always worry about an extra oops in the logs... so might be helpful to have a standard dev team address that logs can be shared to from drive/dropbox/etc.

Additional information

No response

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/issues-experiment/discussions

Description

There is a bug

Steps to Reproduce

1. Do thing
2. Look at output

Expected Result

It works

Actual Result

It doesn't work

Status

Mina daemon status
==================

Logs

https://example.com/

Additional information

This has never worked

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/issues-experiment/discussions

Summary

It would be helpful for xyz to understand that more precisely. Which would be a documentation feature request not a bug!

Steps to Resolve this Issue

1. Change docs to reflect the new command
2. And update the version

...