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

bug during plugins indexation #9231

Closed
2 tasks done
darkweak opened this issue Aug 4, 2022 · 3 comments · Fixed by #9227
Closed
2 tasks done

bug during plugins indexation #9231

darkweak opened this issue Aug 4, 2022 · 3 comments · Fixed by #9227

Comments

@darkweak
Copy link

darkweak commented Aug 4, 2022

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?

I setup a plugin that have zap in the vendors but not used during the træfik plugin runtime.
I must see nothing like before.

What did you see instead?

CFG post-order panic: runtime error: index out of range [0] with length 0
darkweak/souin#243

What version of Traefik are you using?

latest

What is your environment & configuration?

# (paste your configuration here)

Add more configuration information here.

If applicable, please paste the log output in DEBUG level

No response

@ldez ldez changed the title Another Træfik plugin bug during indexation with zap plugin bug during indexation with zap Aug 4, 2022
@ldez
Copy link
Member

ldez commented Aug 4, 2022

Hello,

Are you able to run your plugin in local mode?
Do you run tests with yaegi inside your CI?

It seems to be a problem with the latest version of yaegi.

Edit: I confirm it's a bug with the latest version (v0.14.0) of yaegi.

@ldez ldez changed the title plugin bug during indexation with zap plugin bug during indexation Aug 4, 2022
@ldez ldez changed the title plugin bug during indexation bug during plugins indexation Aug 4, 2022
@darkweak
Copy link
Author

darkweak commented Aug 4, 2022

Hello
Yes I ran the plugin in local mode in the CI and the release was two days ago but the issue appear 7 hours ago. I thought it was a false positive but reappeared after I closed the previous one.

@ldez
Copy link
Member

ldez commented Aug 8, 2022

problem fixed by traefik/yaegi#1436

@ldez ldez closed this as completed Aug 8, 2022
@kevinpollet kevinpollet linked a pull request Aug 8, 2022 that will close this issue
@traefik traefik locked and limited conversation to collaborators Sep 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants