Repository navigation
meta: document xvfb gaps, newer libadwaita setup, and tsharness checks in skills - #353
Merged
Merged
Conversation
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.
Why
Agents that drive Trayscale kept hitting the same problems. They tried to drive things Xvfb can't show. They built newer GTK libraries that later vanished. They guessed at
tailscaledbehavior instead of testing it. Andverify-trayscaledidn't trigger for refactors that changed the accessibility tree without changing how the app looks.What changed
drive-trayscalelists what doesn't work without a GNOME session: screenshots, popovers, combo rows, and returning to the this-machine page.drive-trayscaleshows how to run the app against a newer GTK and libadwaita with thePUREGOTK_*_PATHvariables, and how to check that the libraries still exist first.drive-trayscalesays to answer questions abouttailscaledbehavior on tsharness, andverify-trayscalenow also triggers on widget tree, template, and subclassing refactors.Scope
-remove-exit-afterflag is documented in internal/ui, internal/tsutil: add exit node selection preference and self page exit node row #345, which adds it.Verification
TestFillFromBuilderpasses under Xvfb inside a GNOME SDK runtime.LD_LIBRARY_PATHfails with theGLIBC_PRIVATEerror the skill describes.Coder created this PR.