`DeprecationWarning` appearing in logs after running action
See original GitHub issue(node:1790) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[17](https://github.com/tmillr/breaking-change/actions/runs/3607545212/jobs/6079626552#step:7:18)
(Use `node --trace-deprecation ...` to show where the warning was created)
https://github.com/tmillr/breaking-change/actions/runs/3607545212/jobs/6079626552#step:7:17
Perhaps a dependency needs updating?
Issue Analytics
- State:
- Created 10 months ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
What does this deprecation warning mean, and how to fix it?
In short, my understanding: pip builds a tree of dependencies between packages. currently pip requires a temporary folder; this leads ...
Read more >Misleading deprecation warning when referencing ... - GitHub
Run rails environment . Run cat log/development.log . Expected behavior. The development.log file should be empty. Actual ...
Read more >warnings — Warning control — Python 3.11.1 documentation
Default Warning Filter In a debug build, the list of default warning filters is empty. Changed in version 3.2: DeprecationWarning is now ignored...
Read more >DeprecationWarning no longer loud by default in Python 2.7+
Since Python 2.7 (and 3.2) Python no longer emits output for DeprecationWarnings. This is due to the desire to hide these errors from...
Read more >How to capture warnings — pytest documentation
By default pytest will display DeprecationWarning and PendingDeprecationWarning warnings from user code and third-party libraries, as recommended by PEP 565.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m planning to remove the
proxy-agent
dependency with a new proxy implementation. This warning will go away then. The new implementation is currently sitting in thev5-beta
branch, which I’m planning to release as a new major version at some point in the near future.Thank you, Peter, actually it is not so annoying, but just I faced it. I think I can wait for the final v5. Please post here a message when it is out.