forked from coenjacobs/mozart
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Warnings / broken autoloading with Strauss 0.18.0 vs 0.17.0 #101
Comments
Can confirm. Also happening in my github ci setups |
Oops. Should be fixed now. 7a0a927 |
Thanks for the reply here. While v0.19.0 now no longer throws warnings to the console, autoloading is still broken with v0.19.0 versus v0.17.0 - ie this step in the reproduction:
|
I seem to have that fixed now. I was missing |
Confirming that v0.19.1 resolves the issues we were having - thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version 0.18.0 contains a change which I believe is breaking strauss in my project:
With strauss v0.17.0 the output of
composer install
[which triggers strauss] ends as follows and everything works as expected:The same configuration run against strauss v0.18.0 throws a bunch of warnings to the console and yields a broken project:
After the install is run, autoloading appears broken for some items, e.g.
Fatal error: Uncaught Error: Class 'Composer\XdebugHandler\XdebugHandler' not found
To reproduce the issue, follow the process below which
strauss
invoking either v0.17.0 or v0.18.0. Everything works as expected under v0.17.0, but fails under v0.18.0:Everything looks good at this point.
At this point strauss v0.18.0 will throw a bunch of PHP warnings and notices to the console, and autoloading will be broken.
Oddly, in my build pipeline, everything fails after the initial install, but I couldn't reproduce that on my local machine, and a
composer install
thencomposer update
is required before things break. Probably just a difference in my actual repo vs the example one I put together, but not quite sure what that might be.The text was updated successfully, but these errors were encountered: