Repository navigation
Drop data-hero-deps: nothing reads it since the wasm runtime has the stack frozen in - #6
Merged
Merged
Conversation
Merged
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.
The hero runtime (hero-runtime.js) never read data-hero-deps, and since PyDevices.github.io#10 nothing installs the stack at all, so dotgithub's generator stops emitting it and repos_db.json's hero_canvas entries lose their deps lists (23). Regenerated: 22 hero pages (20 in PyDevices.github.io, 1 in mip, 1 in pydevices-examples), one line each, only the attribute. dotgithub's checks.yml fails if a generated page lags the database, so these four PRs land together: dotgithub, PyDevices.github.io, mip, pydevices-examples. Merge after the published-site verification of the reorg finishes.