Closed CaoYan1 closed 3 months ago
🤖
Hey there @CaoYan1! 🖐️
I'm Dosu, a friendly bot here to help you out while waiting for a human maintainer. I'm your go-to for solving bugs, answering questions, and helping you become the best contributor you can be! 🚀
Just wanted to say hi and let you know I'm here for you. Hang tight, we'll get through your issue together! 💪😀
Based on the information you've provided, it seems like you're encountering an issue where the form.EncodeValues(msg)
function is returning an error when it encounters a repeated custom message in your request, causing the rest of the fields to be ignored.
This behavior is due to how the form.EncodeValues(msg)
function handles unsupported field types. When it encounters an unsupported field type, it returns an error and stops processing the rest of the fields. This is why your id
field is being ignored. You can see this in the encodeMessage
function in the encoding/form/proto_encode.go file:
func encodeMessage(msgDescriptor protoreflect.MessageDescriptor, value protoreflect.Value) (string, error) {
// ...
default:
return "", fmt.Errorf("unsupported message type: %q", string(msgDescriptor.FullName()))
}
}
However, I found a similar issue in the Kratos repository that was resolved: 当message中有自定义list消息且url中有参数时,使用生成的http client无法生成正确的url. This issue was addressed in the following pull request: 修复地址栏参数.
Based on this, it seems like the Kratos team has made some changes to handle this scenario. I recommend checking out these resources to see if they can help resolve your issue. If you're still encountering problems, could you please provide more details about your use case and the exact error message you're seeing? This will help me better understand the issue and provide a more accurate solution.
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
My Kratos
version is latest(2.7.2) and doesn't work still
Can you provide your http client code? I try to reproduce your case, but there was no issue found.
Here is my reproduce repo.
# send http request
curl http://localhost:8000/my-api/1 -X POST -H 'Content-Type: application/json' -d '{"msg":[{}]}'
# console
id:"1" msg:{}
Based on your repo, you can try this code. I can reproduce this issue. @kvii
func TestHttpClient(t *testing.T) {
client, _ := http.NewClient(context.Background(), http.WithEndpoint("localhost:8000"))
c := NewMyServiceHTTPClient(client)
resp, err := c.Call(context.Background(), &Request{
Id: "id",
Msg: []*MsgInline{
{},
},
})
// will return 404 error
fmt.Println(resp, err)
}
Oh, this is an issue of kratos http client, not server. I pushed a commit to my repo, add tests for this issue at here.
Source codes:
binding.EncodeURL
:Cool! Do you have a plan to fix it?
😭 I'm busy now.
I'd like to help you.
I've created a PR for this issue. But the code style is terrible.
这个问题 #2805 应该是解决了的
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
This issue https://github.com/go-kratos/kratos/pull/2805 should be solved
What happened:
I defined an RPC method:
And I called it via http client, the id field in url path was always empty.
Anything else we need to know?:
I find that form.EncodeValues(msg) will return error[unsupported message type:] if the request message contains repeated custom message, and ignore the rest fields, then my
id
field is ignored. I think an unsupported field shouldn't make other fields don't work.Environment:
go version
): 1.21.1cat /etc/os-release
): macos