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

Action causes '[DEP0005] DeprecationWarning' #22

Closed
dmurat opened this issue Jun 19, 2020 · 11 comments
Closed

Action causes '[DEP0005] DeprecationWarning' #22

dmurat opened this issue Jun 19, 2020 · 11 comments
Assignees
Labels
dependencies Pull requests that update a dependency file

Comments

@dmurat
Copy link

dmurat commented Jun 19, 2020

For all steps using gradle-command-action I'm getting deprecation warning: [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Is this expected or should it be fixed?

Tnx

@dmurat
Copy link
Author

dmurat commented Jun 19, 2020

If needed, here is a sample workflow: https://github.com/croz-ltd/klokwrk-project/actions/runs/140909371

@eskatos
Copy link
Member

eskatos commented Jun 22, 2020

Thanks for the report @dmurat.

This deprecation warning is coming from a dependency of the action. I still have to figure out which one.
It isn't a problem per se but that warning will go away when upgrading the offending dependency to a fixed version once available.
I just tried upgrading all outdated dependencies and the deprecation message is still present, I'll get back to this regularly.

@eskatos eskatos added the dependencies Pull requests that update a dependency file label Jun 22, 2020
@marracuene
Copy link

Also getting this warning - and it seems to have the ability to intermittently crash the gradle process.

If you look at runs #9 and #10 of this action, you will see that #9 gave this warning and then appeared to fail because of it. See line 2020-06-23T19:26:06.3961561Z ##[error]Premature close

Whereas #10 (which differs only in the indenting of a comment line - which I used to trigger a new run) did not give this warning, and proceeded with the build.

N.B. this repo is a clone of https://github.com/gradle/playframework, which I forked purely in order to investigate mysterious build failures which I cannot reproduce locally. The failures only occur in a CI environment. See: gradle/playframework#136

@bshaffer
Copy link

Our builds are also failing due to this error, and it does not seem to be intermittent.

@eskatos
Copy link
Member

eskatos commented Jun 25, 2020

Hum, thanks all for the reports! I'll investigate.
In the meantime you can pin your action usage to v1.2.0 that didn't have this problem.

marracuene added a commit to marracuene/playframework that referenced this issue Jun 26, 2020
See: gradle/gradle-build-action#22

Signed-off-by: marracuene <cameron_smith@mail.com>
marracuene added a commit to marracuene/playframework that referenced this issue Jun 26, 2020
See: gradle/gradle-build-action#22

Signed-off-by: marracuene <cameron_smith@mail.com>
@marracuene
Copy link

In the meantime you can pin your action usage to v1.2.0 that didn't have this problem.

Hmm. Pinning to v1.2.0 didn't actually fix it. Which suggests that something more fundamental is at play.
See here
... specifically the bit where it says:

Run eskatos/gradle-command-action@v1.2.0
(node:2754) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Cache Size: ~193 MB (202061936 B)

@eskatos
Copy link
Member

eskatos commented Sep 13, 2020

I tracked this down to microsoft/typed-rest-client.
This has been fixed upstream microsoft/typed-rest-client@de7bcee but not released yet.

I suppose it could be replaced by e.g. https://github.com/actions/http-client
Nope, same problem ...

@nuhkoca
Copy link

nuhkoca commented Oct 29, 2020

Any update on this?

@amotl
Copy link

amotl commented Jan 29, 2021

Hi there,

I tracked this down to microsoft/typed-rest-client.

microsoft/typed-rest-client@5f16b0dc might have fixed this, so I humbly asked for a new release at microsoft/typed-rest-client#246.

With kind regards,
Andreas.

@amotl
Copy link

amotl commented Jan 29, 2021

Hi again,

@damccorm was so kind to publish typed-rest-client 1.8.1 right away [1]. Thank you!

With kind regards,
Andreas.

[1] https://www.npmjs.com/package/typed-rest-client

@bigdaz
Copy link
Member

bigdaz commented Aug 17, 2021

This was fixed in v1.4.0

@bigdaz bigdaz closed this as completed Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

No branches or pull requests

7 participants