Skip to content

Conversation

@aditya520
Copy link
Member

Summary

Rationale

How has this been tested?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

@vercel
Copy link

vercel bot commented Jan 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
api-reference Ready Ready Preview, Comment Jan 7, 2026 9:23pm
component-library Ready Ready Preview, Comment Jan 7, 2026 9:23pm
developer-hub Ready Ready Preview, Comment Jan 7, 2026 9:23pm
proposals Error Error Jan 7, 2026 9:23pm
staking Error Error Jan 7, 2026 9:23pm
2 Skipped Deployments
Project Deployment Review Updated (UTC)
entropy-explorer Skipped Skipped Jan 7, 2026 9:23pm
insights Skipped Skipped Jan 7, 2026 9:23pm

@benduran
Copy link
Contributor

benduran commented Jan 7, 2026

General Layout feedback. See image below 🙂
CleanShot 2026-01-07 at 14 51 19

variant="primary"
size="lg"
onPress={handleRunCode}
className={styles.runButton ?? ""}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is rather annoying. we should allow for a nullish className to be set on our components (not something you need to fix, just thinking out loud 😅 )

@benduran
Copy link
Contributor

benduran commented Jan 7, 2026

Additional UX feedback about the left panel (see image):
CleanShot 2026-01-07 at 15 10 08

@vercel vercel bot temporarily deployed to Preview – entropy-explorer January 7, 2026 17:57 Inactive
@vercel vercel bot temporarily deployed to Preview – staking January 7, 2026 17:57 Inactive
@vercel vercel bot temporarily deployed to Preview – api-reference January 7, 2026 17:57 Inactive
@vercel vercel bot temporarily deployed to Preview – proposals January 7, 2026 17:57 Inactive
let timeoutId: ReturnType<typeof setTimeout> | undefined;
let isClosed = false;

const stream = new ReadableStream({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 we may need to do a deeper dive on the usage of the EventStream API here. it's a good usage here in Next (since we cannot use server-side websockets in Next), but there is an opportunity to move this API out of developer hub and into the shared-lib, so we can standardize the API and also provide some React hooks that work easily with it, without needing to build something custom per-app (thinking out loud here, as this is 100% something that we will need in other places)

};
websocket = new WebSocket(wsUrl, wsOptions);

websocket.addEventListener("open", () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is actually not going to work once deployed. it works locally, because you have a single, persistent instance that is always up. However, once deployed to Vercel, the app cluster will be scaled up and down dynamically, so the server that opened this websocket instance will likely be killed, which will cause problems that manifest as Pyth API slowness and instability (definitely not a thing to promote 😓 ).

Let's revisit this. We may need to have a bespoke server, written in Rust or Javascript, depending on which Pyth Client we want to use, that only handles streaming for the DevHub docsite and the upcoming Admin portal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants