-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tapioca dsl --verify
succeeds when it should fail
#1783
Comments
My first thought is making sure the RAILS_ENV is consistent during both runs. If you can't reproduce CI behaviour locally you'd have to ssh in and try to debug tapioca internals within that session. For the mailer issue I'd think For view_component, my guess would be on the I hope these give some ideas. It'd be easier if you could add a breakpoint to tapioca compilers and run it on CI, inspect relevant variables. |
Had a little bit of spare time today to try and rule out the obvious:
Maybe related: the output of |
Do you skip any Bundler groups in CI? e.g. with |
No, we're using ruby/setup-ruby@v1 with |
We run Tapioca verify commands in CI, but with some regularity notice that RBI changes are missed for DSLs when we run the dsl generation locally. Our
ci.yml
step on GitHub actions (Linux):output:
Locally running
bin/tapioca dsl --verify
on a macOS machine does show me the error I was expecting to see:The diff of anonymized_view_component.rbi:
The diff of the mailers show a method being moved:
As a workaround I can change our CI step to the following:
git add -N .
is to make sure new ViewComponent RBI is picked up bygit diff
as well, otherwise only the mailer change would show up.... but I'd love to understand how to further debug this case and get this bug fixed.
The text was updated successfully, but these errors were encountered: