Skip to content

fix: Fix broken links#7721

Closed
bobtajson wants to merge 8 commits intoanza-xyz:masterfrom
bobtajson:master
Closed

fix: Fix broken links#7721
bobtajson wants to merge 8 commits intoanza-xyz:masterfrom
bobtajson:master

Conversation

@bobtajson
Copy link
Copy Markdown

@bobtajson bobtajson commented Aug 26, 2025

Problem

  • Dead link in RELEASE.md
  • Broken link in spec.md
  • fixed CSS property in styles.module.css

Summary of Changes

  • Removed dead link in RELEASE.md
  • Replaced dead links https://docs.solana.com/validator/runtime#execution and https://docs.solana.com/validator/runtime#execution to
    https://docs.anza.xyz/validator/runtime#execution and https://docs.anza.xyz/validator/runtime#execution in spec.md file
  • Replaced align-items: top to flex-start

Fixes #

fixed break link
fixed css style
@bobtajson bobtajson requested a review from a team as a code owner August 26, 2025 10:24
@LucasSte LucasSte requested review from 0xbrw and steviez August 26, 2025 14:37
Comment thread RELEASE.md Outdated
[Crates.io agave-validator](https://crates.io/crates/agave-validator) should have an updated agave-validator version. This can take 2-3 hours, and sometimes fails in the `agave-secondary` job.
If this happens and the error is non-fatal, click "Retry" on the "publish crate" job

<!-- TODO: fix this dead link to actual
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@buffalojoec @willhickey do we have a replacement link for cluster-ops?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@willhickey @0xbrw removed link

.features {
display: flex;
align-items: top;
align-items: flex-start;
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

can you include a screenshot of the before and after change?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

This code is not currently in use. I don't know if it's leftover from the past or planned for the future, but if it gets implemented, it could cause layout issues on different screen sizes.

can you include a screenshot of the before and after change?

Copy link
Copy Markdown
Author

@bobtajson bobtajson Aug 26, 2025

Choose a reason for hiding this comment

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

Yes, it is not used anywhere. I can look for properties that are not yet used and make one more commit without them

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

if this code is not in use, lets remove this change from the PR

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Copy link
Copy Markdown

@0xbrw 0xbrw left a comment

Choose a reason for hiding this comment

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

Let’s place a hold on this until we know what to replace cluster-ops links with

@bobtajson
Copy link
Copy Markdown
Author

bobtajson commented Aug 27, 2025

Let’s place a hold on this until we know what to replace cluster-ops links with

ChatGPT telling me this:

Why is validator the right place to look if you’re seeking a working equivalent of cluster-ops?

The cluster-ops repository (Solana Labs) provided tools for managing a cluster of validators (i.e., cluster operations).

In Agave, the role of such tooling is implemented directly within the shared validator code and its surrounding environment, including the validator directory and the supporting infrastructure such as documentation, CLI commands, configuration management, and operational controls.

https://github.com/anza-xyz/agave/tree/master/validator

So if you agree, i will commit this link to placeholder

Comment thread RELEASE.md Outdated
Comment on lines 155 to 156
### Update software on testnet.solana.com
See the documentation at https://github.com/solana-labs/cluster-ops/. devnet.solana.com and mainnet-beta.solana.com run stable releases that have been tested on testnet. Do not update devnet or mainnet-beta with a beta release.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We don't have any public documentation that replaces cluster-ops. I suggest removing this sentence:

See the documentation at https://github.com/solana-labs/cluster-ops/.

@bobtajson bobtajson requested review from 0xbrw and willhickey August 29, 2025 12:28
@willhickey
Copy link
Copy Markdown

The two .md file changes are fine, but I haven't confirmed that deleting the css file is ok. @0xbrw have you checked the css deletion?

@bobtajson
Copy link
Copy Markdown
Author

The two .md file changes are fine, but I haven't confirmed that deleting the css file is ok. @0xbrw have you checked the css deletion?

yeah he checked, i taged you under that commit

@bobtajson
Copy link
Copy Markdown
Author

@0xbrw so can we merge this?

@0xbrw
Copy link
Copy Markdown

0xbrw commented Sep 18, 2025

@0xbrw so can we merge this?

Can you revert the CSS file deletion and update the PR title/description to represent the new changes

@bobtajson bobtajson changed the title fix: Fix broken links and CSS property fix: Fix broken links Sep 29, 2025
@bobtajson
Copy link
Copy Markdown
Author

@0xbrw so can we merge this?

Can you revert the CSS file deletion and update the PR title/description to represent the new changes

Title and description updated, but i can't revert CSS file because it was remove from your master branch

@willhickey
Copy link
Copy Markdown

Title and description updated, but i can't revert CSS file because it was remove from your master branch

It's still there:
https://github.com/anza-xyz/agave/tree/master/docs/src/pages

There's a few ways to undo the delete. A checkout followed by a commit will preserve the existing history here:
git checkout master -- docs/src/pages/styles.module.css

@bobtajson
Copy link
Copy Markdown
Author

Title and description updated, but i can't revert CSS file because it was remove from your master branch

It's still there: https://github.com/anza-xyz/agave/tree/master/docs/src/pages

There's a few ways to undo the delete. A checkout followed by a commit will preserve the existing history here: git checkout master -- docs/src/pages/styles.module.css

done

Copy link
Copy Markdown

@willhickey willhickey left a comment

Choose a reason for hiding this comment

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

The two changes in md files are fine. I'm not familiar with the docs css so don't have an opinion on that change.

.features {
display: flex;
align-items: top;
align-items: flex-start;
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I still see changes in this css file. Can you pull the latest changes from the master branch and then run:
git checkout master -- docs/src/pages/styles.module.css

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

So i'm confused, i need to delete this file from my PR?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

yes if it is not in use and you cannot confirm the before and after changes.

@steviez
Copy link
Copy Markdown

steviez commented Oct 1, 2025

Closing this PR for several reasons:

@steviez steviez closed this Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants