fix server.go:243:6: no new variables on left side of :=

[zonghuili2019]

redefine tgr

[Cyberhan123]

yes, I got same

[MilanSavaliya]

perfect. 👌

[MilanSavaliya]

I think it would be good if you can merge this as soon as possible.

@derekbassett @arran4 @vgarvardt ?

[arran4]

Hey, I don't have write access to the repo sorry.

[MilanSavaliya]

@LyricTian is it possible to create new version tag and make it available ?

[Cyberhan123]

@LyricTian is it possible to create new version tag and make it available ?

May not, It's an hot fix ,so version tag may an bad idea. cc @LyricTian How do you see?

[novrian]

@Cyberhan123 v4 is broken right now.
If it's not possible to create a new tag then how can we use v4?

[Cyberhan123]

@Cyberhan123 v4 is broken right now.
If it's not possible to create a new tag then how can we use v4?

It just a package cache, U can run
go clean -i -n github.com/go-oauth2/oauth2/v4/...
uninstall it (some dir may should delete by hand) and go get fetch it again

[novrian]

@Cyberhan123 no luck, still experience the same error

nevermind, maybe I will use v3 either. thanks for helping han

[MilanSavaliya]

@Cyberhan123 @LyricTian i think this will not work as releases are tied with particular commit hash as you can see in attached picture. You have to create newer tag release to offer this fix.

[Cyberhan123]

@cyber​​han123 @LyricTian我认为这不会起作用，因为发布与特定的提交哈希相关联，如您在附图中所见。您必须创建更新的标签版本才能提供此修复程序。

@cyber​​han123不走运，仍然遇到同样的错误

没关系，也许我也会使用 v3。谢谢你帮助韩

@Cyberhan123 @LyricTian i think this will not work as releases are tied with particular commit hash as you can see in attached picture. You have to create newer tag release to offer this fix.

oh, you are right and I want check out why my packge are worked