Skip to content
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

Treat assert() as failing #68

Open
orklah opened this issue Nov 25, 2021 · 5 comments
Open

Treat assert() as failing #68

orklah opened this issue Nov 25, 2021 · 5 comments

Comments

@orklah
Copy link
Contributor

orklah commented Nov 25, 2021

vimeo/psalm#6989 reported a case where psalm is failing due to an assert() in php-parser but psalm.dev continues the analysis. I think psalm.dev should behave as if we were in dev environment because this is usually the way Psalm runs

@weirdan
Copy link
Member

weirdan commented Nov 25, 2021

@orklah
Copy link
Contributor Author

orklah commented Nov 25, 2021

Do you think we'll be allowed to change those directly from code or should we ask Matt to change this in the host panel?

@orklah
Copy link
Contributor Author

orklah commented Nov 28, 2021

Doc says

If a process is started in production mode, zend.assertions cannot be changed at runtime, since the code for assertions was not generated.

So, php.ini change is mandatory

@orklah
Copy link
Contributor Author

orklah commented Nov 29, 2021

@muglug could you take a look at this when you have time? It would be great to have psalm.dev behaving correctly when failing an assertion

@weirdan
Copy link
Member

weirdan commented Mar 3, 2023

I think this is fixed now. @muglug can you confirm you enabled assertions on https://psalm.dev?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants