Skip to content

Conversation

@ndossche
Copy link
Member

This stopped working after e735d2b because fp_refcount is increased, making phar think that the file has open read pointers. To fix this, the refcount shouldn't be increased but that would re-introduce the previous bug.
However, 6fe40de fixed a bug that makes us hold onto the phar archive too. That fix also fixes the original issue, so we can just remove the fp_refcount modification.
Add a test to prevent this issue in the future.

This stopped working after e735d2b because fp_refcount is increased,
making phar think that the file has open read pointers.
To fix this, the refcount shouldn't be increased but that would
re-introduce the previous bug.
However, 6fe40de fixed a bug that makes us hold onto the phar
archive too. That fix also fixes the original issue, so we can just
remove the fp_refcount modification.
@ndossche ndossche marked this pull request as draft November 13, 2025 22:12
@ndossche
Copy link
Member Author

ndossche commented Nov 13, 2025

CI seems to fail, it didn't reproduce locally, so I'll have to take a look again.
EDIT: Ah no this fix won't work, fp_refcount does need to increase after all; so I'd have to think of a better fix...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant