Since #54471, dumpFile will trigger a `fileperms(): stat failed`
error when writing to a filename that does not yet exist. This
was silenced from PHP's default handler with the `@` operator.

However, the error is still passed to any custom handler that the
application has registered, and can therefore cause exceptions or
spurious logging depending on the implementation of the handler.

The better solution, which is consistent with all other calls to
native functions in this class, would be to use `self::box` to
catch and ignore the potential error so that it never leaks
outside this class.

…om handler (acoulton)

This PR was merged into the 5.4 branch.

Discussion
----------

[Filesystem] Fix dumpFile `stat failed` error hitting custom handler

| Q             | A
| ------------- | ---
| Branch?       | 5.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | See below
| License       | MIT

Since #54471, dumpFile will trigger a `fileperms(): stat failed` error when writing to a filename that does not yet exist. This was silenced from PHP's default handler with the `@` operator.

However, the error is still passed to any custom handler that the application has registered, and can therefore cause exceptions or spurious logging depending on the implementation of the handler.

The better solution, which is consistent with all other calls to native functions in this class, would be to use `self::box` to catch and ignore the potential error so that it never leaks outside this class.

Commits
-------

247182a [Filesystem] Fix dumpFile `stat failed` error hitting custom handler

Since symfony#54471, dumpFile will trigger a `fileperms(): stat failed`
error when writing to a filename that does not yet exist. This
was silenced from PHP's default handler with the `@` operator.

However, the error is still passed to any custom handler that the
application has registered, and can therefore cause exceptions or
spurious logging depending on the implementation of the handler.

The better solution, which is consistent with all other calls to
native functions in this class, would be to use `self::box` to
catch and ignore the potential error so that it never leaks
outside this class.

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [symfony/filesystem](https://symfony.com)
([source](https://togithub.com/symfony/filesystem)) | `6.4.6` -> `6.4.8`
|
[![age](https://developer.mend.io/api/mc/badges/age/packagist/symfony%2ffilesystem/6.4.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/packagist/symfony%2ffilesystem/6.4.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/packagist/symfony%2ffilesystem/6.4.6/6.4.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/packagist/symfony%2ffilesystem/6.4.6/6.4.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>symfony/filesystem (symfony/filesystem)</summary>

###
[`v6.4.8`](https://togithub.com/symfony/filesystem/releases/tag/v6.4.8)

[Compare
Source](https://togithub.com/symfony/filesystem/compare/v6.4.7...v6.4.8)

**Changelog**
(symfony/filesystem@v6.4.7...v6.4.8)

- bug
[symfony/symfony#54878](https://togithub.com/symfony/symfony/issues/54878)
\[Filesystem] Fix dumpFile `stat failed` error hitting custom handler
(@&#8203;acoulton)
- bug
[symfony/symfony#54759](https://togithub.com/symfony/symfony/issues/54759)
\[Filesystem] better distinguish URL schemes and Windows drive letters
([@&#8203;xabbuh](https://togithub.com/xabbuh))

###
[`v6.4.7`](https://togithub.com/symfony/filesystem/releases/tag/v6.4.7)

[Compare
Source](https://togithub.com/symfony/filesystem/compare/v6.4.6...v6.4.7)

**Changelog**
(symfony/filesystem@v6.4.6...v6.4.7)

- bug
[symfony/symfony#54471](https://togithub.com/symfony/symfony/issues/54471)
\[Filesystem] Strengthen the check of file permissions in `dumpFile`
(@&#8203;alexandre-daubois)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/Lendable/composer-license-checker).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNzcuOCIsInVwZGF0ZWRJblZlciI6IjM3LjM3Ny44IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Since symfony#54471, dumpFile will trigger a `fileperms(): stat failed`
error when writing to a filename that does not yet exist. This
was silenced from PHP's default handler with the `@` operator.

However, the error is still passed to any custom handler that the
application has registered, and can therefore cause exceptions or
spurious logging depending on the implementation of the handler.

The better solution, which is consistent with all other calls to
native functions in this class, would be to use `self::box` to
catch and ignore the potential error so that it never leaks
outside this class.