bug: Etherbase missing at startup on windows
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Reproduce the startup sequence on Windows with Docker Desktop and inspect the logs for the connection-refused and missing-etherbase errors. Read the related namespace discussions in #1615 and #1650, then determine whether removing reset resolves the startup failure; done means the FireFly stack starts without either reported error.
Written by the indexing model from the issue text.
Description
What happened?
When attempting to start and test firefly on windows a few errors appear. The first error was "Error: dial tcp 127.0.0.1:5100: connectex: No connection could be made because the target machine actively refused it." After doing a bit of digging the error seems to come about when attempting to start the Firefly stack. After the stack is started a new error is present. This error is "Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly specified".
What did you expect to happen?
The expected result is to determine if the removal of reset corrects the namespace issue as mentioned in #1615 and #1650
How can we reproduce it (as minimally and precisely as possible)?
Open a terminal and docker desktop. Start the application and view logs as shown in docker desktop.
Anything else we need to know?
No response
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
-
good first issue
Difficulty 4/5 3-5 days Newbie friendliness 38/100
hyperledger-firefly/cli#331 · 2 reactions ·
All issues in hyperledger-firefly/cli
Similar issues
-
area/security kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agent-substrate/substrate#2935 ·
Maintainers usually reply within 1 day
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Guardian health server binds :8080 and collides with the Voltron proxyPossibly taken @denislemire claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
projectcalico/calico#14341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
blinklabs-io/dingo#5368 ·
Maintainers usually reply within 1 day
-
OpenAI compat: assistant tool_calls attached to previous message when content is an empty arrayPossibly taken @ShryukGrandhi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day