Unable to call LoggingApi.entries.tail()

[schweitzer-churned]

When I try to use the tail function provided in the Logging API, I am getting the following error

[{ "error": { "code": 400, "message": "Invalid value (Object), ", "status": "INVALID_ARGUMENT", "details": [ { "@type": "type.googleapis.com/google.rpc.BadRequest", "fieldViolations": [ { "description": "Invalid value (Object), " } ] } ] } } ]

I stumbled across this issue and I am assuming this is a similar bug. Can you confirm? And are there plans to use the gRPC versions to enable streaming into flutter?

[kevmoo]

Exactly. We cannot do streaming APIs

[postmeridiem]

Thanks for confirming! I guess this function should also be removed from discovery at some point.

[schweitzer-churned]

sorry. my accounts got mixed up, that was me, the previous post

[lesnitsky]

@kevmoo is there any roadmap for googleapis.dart? It's been a while since this issue was raised and I'm now facing the same problem.

If that's not something that is planned or will be worked on, it's worth dropping the method from the public API.

[lesnitsky]

It also seems that even if the underlying request wasn't returning error, streaming wouldn't be possible still, since tail() returns TailLogEntriesResponse, as opposed to Stream<TailLogEntriesResponse>.

[kevmoo]

I'm downstream of things that need to be fixed. I'd happy accept a pull request excluding these APIs.

[lesnitsky]

I went through the steps described under contributing section of the readme and it's not entirely clear to me if there is some "exclusion" mechanism. If I just remove the tail() method and related classes – those will be back after someone runs run_config generate again. Is my understanding correct?

[kevmoo]

You have to add a delta file. See https://github.com/google/googleapis.dart/tree/master/overrides

[lesnitsky]

I can't find any notes on how to name those diffs. Should those just be unique or is there any relation to commit shas?

[kevmoo]

The names don't matter. They just have to be valid diff files. The convention is to align the diff with the corresponding issues. In this case `i407.diff`

…

On Tue, Mar 5, 2024 at 12:02 PM Andrei Lesnitsky ***@***.***> wrote: I can't find any notes on how to name those diffs. Should those just be unique or is there any relation to commit shas? — Reply to this email directly, view it on GitHub <#407 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEFCU3GGNIJ7BGWMAHKPTYWYQE7AVCNFSM5WMGOCT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJXHE2TGNJSHA4A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lesnitsky]

I've also tried calling the API directly with a raw HttpClient and got the same error response. Could a relevant issue be raised internally?