Conversation
This is an useful tool for preparing code listing for LLMs: https://repomix.com/
…n documents - Convert broken Google Docs export footnote references (e.g., .1, .2) to proper Markdown footnotes - Update all 'Works cited' sections to use [^1]: format instead of numbered lists - Ensure cross-references to blocksense-litepaper.md are properly formatted - Improve readability and compatibility with GitHub and Quartz publishing
- Update directory structure to match actual current organization - Add comprehensive content status section showing completed specifications - Document planned future content areas - Update setup instructions to use Nix flakes properly - Add content guidelines for contributors - Fix cross-references to use actual document names - Maintain forward-looking structure for future additions
The spec branch registered `spec/website` as a yarn workspace, but that path never existed (the spec content lives under `spec/` and is built via Nix `specification-website`, not the yarn workspace build). Yarn Berry's immutable install in CI failed on the unresolvable workspace, breaking `build-and-test-ts-libs-and-apps` and `decoders-tests`. Removes the `spec/website` workspace entry and the corresponding yarn.lock stub, restoring yarn.lock to match origin/main (green CI).
isTokenValid() intends to return false when DFCG_ARTIFACTS_ACCESS_TOKEN is invalid, so `describe.skipIf(!tokenValid)` skips the legacy config decoding suite. But the 401 guard used `error instanceof RequestError`, and Octokit throws a RequestError from a differently-resolved copy of @octokit/request-error, so the instanceof check was false and the 401 re-threw — failing the suite instead of skipping it. This only surfaces when the token is invalid/expired (the CI token currently 401s); with a valid token the suite runs as before. Fall back to the numeric `error.status` so a 401 is treated as an invalid token. Pre-existing bug (file identical on origin/main); fixing it here unblocks the spec PR's `build-and-test-ts-libs-and-apps` job.
🚀 Deployment Links of Blocksense Network websites:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lands the specification-publishing work from the
specbranch ontomain.What this adds (6 commits over
main)Notes
specbranched frommainat349a12c4(2025-07-30);mainhas 70 commits since. Local merge preview (git merge-tree) shows no conflicts.