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

E900 error after latest version #20592

Closed
shawaj opened this issue Jun 1, 2024 · 3 comments
Closed

E900 error after latest version #20592

shawaj opened this issue Jun 1, 2024 · 3 comments
Labels
type: bug A code related bug.

Comments

@shawaj
Copy link

shawaj commented Jun 1, 2024

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

After updating to latest vector version I now see an error that wasn't there before:

WARN transform{component_kind="transform" component_id=remapped component_type=remap}: vector::transforms::remap: VRL compilation warning. warnings=
warning[E900]: unused variable `err`
ââ :1:10
â
1 â read_at, err = .now * 1000
â          ^^^ help: use the result of this expression or remove it
â
= this expression has no side-effects
= see language documentation at https://vrl.dev
= try your code in the VRL REPL, learn more at https://vrl.dev/examples

Has there been a change that could cause this in latest version?

Configuration

No response

Version

0.38.0

Debug Output

No response

Example Data

No response

Additional Context

No response

References

No response

@shawaj shawaj added the type: bug A code related bug. label Jun 1, 2024
@jszwedko
Copy link
Member

jszwedko commented Jun 3, 2024

Hi @shawaj ! This was a new unused variable warning added in v0.36.0.

@jszwedko jszwedko closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
@shawaj
Copy link
Author

shawaj commented Jun 3, 2024

@jszwedko so what's the fix here?

@jszwedko
Copy link
Member

jszwedko commented Jun 3, 2024

@jszwedko so what's the fix here?

Use the err variable or, if you just want to ignore it, use read_at, _ = ... to ignore any errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A code related bug.
Projects
None yet
Development

No branches or pull requests

2 participants