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

hedera start command fails w stack related printout #820

Open
Tracked by #823
Nana-EC opened this issue Oct 30, 2024 · 1 comment · May be fixed by #825
Open
Tracked by #823

hedera start command fails w stack related printout #820

Nana-EC opened this issue Oct 30, 2024 · 1 comment · May be fixed by #825
Assignees
Labels
Bug An error that causes the feature to behave differently than what was expected based on design. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk.

Comments

@Nana-EC
Copy link
Contributor

Nana-EC commented Oct 30, 2024

Description

Running the hedera start command show the UI in teh command line temporarily and then fails wtih

─Consensus Node Log─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│[Hedera-Local-Node] INFO (RecoveryState) ⏳ Starting Recovery State...                                                                                                                                                                                                      │
│[Hedera-Local-Node] INFO (RecoveryState) ⏳ Trying to startup again...                                                                                                                                                                                                       │[Hedera-Local-Node] INFO (StartState) ⏳ Detecting network...
│[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...                                                                                                                                                             │
│[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...                                                                                                                                                             │
│[Hedera-Local-Node] INFO (ConnectionService) Mirror Node GRPC not yet available at: 127.0.0.1:5600. Retrying...
...
[Hedera-Local-Node] INFO (InitState) [✔︎] Needed bootsrap properties were set for this configuration.
[Hedera-Local-Node] INFO (InitState) [✔︎] Needed mirror node properties were set for this configuration.
[Hedera-Local-Node] INFO (StartState) ⏳ Starting Hedera Local Node...
──────────────────────────────────────────────────────────────────────────────

Error on xterm-256color.Setulc:
"\u001b[58::2::%p1%{65536}%/%d::%p1%{256}%/%{255}%&%d::%p1%{255}%&%d%;m"

var v,
 stack = [],
 out = ["\x1b[58::2::"];
(stack.push(v = params[0]),
 v),
(stack.push(v = 65536),
 v),
(v = stack.pop(),
 stack.push(v = (stack.pop() / v) || 0),
 v),
out.push(stack.pop()),
out.push("::"),
(stack.push(v = params[0]),
 v),
(stack.push(v = 256),
 v),
(v = stack.pop(),
 stack.push(v = (stack.pop() / v) || 0),
 v),
(stack.push(v = 255),
 v),
(v = stack.pop(),
 stack.push(v = (stack.pop() & v) || 0),
 v),
out.push(stack.pop()),
out.push("::"),
(stack.push(v = params[0]),
 v),
(stack.push(v = 255),
 v),
(v = stack.pop(),
 stack.push(v = (stack.pop() & v) || 0),
 v),
out.push(stack.pop())}out.push("m");
return out.join("");

This resulted in 7 out of 19 containers running for me

Steps to reproduce

In a new folder

  1. git clone https://github.com/hashgraph/hedera-local-node.git
  2. cd hedera-local-node
  3. npm install && npm install -g
  4. hedera start

Additional context

No response

Hedera network

other

Version

v2.31.0

Operating system

macOS

@Nana-EC Nana-EC added P1 High priority issue, which must be completed in the milestone otherwise the release is at risk. Bug An error that causes the feature to behave differently than what was expected based on design. labels Oct 30, 2024
@natanasow
Copy link
Collaborator

@Nana-EC the bug might be caused by a problem (or incompatibility) between the local user's terminal and the Sunset Terminal UI used in the local node.

@georgi-l95 has proposed a complete deprecation of the Sunset TUI due to not reaching the desired user experience. Here is the ticket #793.

@natanasow natanasow self-assigned this Oct 31, 2024
@natanasow natanasow linked a pull request Nov 4, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug An error that causes the feature to behave differently than what was expected based on design. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk.
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants