[azeventgrid] Namespaces: ReleaseEvents() is returning an InternalServerError #21530
Assignees
Labels
Milestone
Comments
richardpark-msft
added
Event Grid
Client
richardpark-msft
pushed a commit
to richardpark-msft/azure-sdk-for-go
that referenced
this issue
Sep 9, 2023
benbp
pushed a commit
that referenced
this issue
Sep 11, 2023
…ics (#21521) * Event Grid publisher client - can publish to topics. * Fixing some issues in the publisher client and adding in examples. * Add function specific examples. * Adding a very basic readme for the publisher package. * Updating changelog * Bump the minor revision as well. * Disable live tests if we're in a CI environment. * Plumb in recording infra * Rearrange client constructors. * Test resources should work now * Fixing tests to just get skipped in non-recording mode. * Remove unused fakeVars * Remove en-us * Temp replace dead links. * Another one failing the dead link checker. * (comparing with others) Looks like I was using an incorrect inputSchema for the topic. * The error code when releasing an expired lock token has changed. Documenting for now, will pose a question for an ongoing discussion. * Skipping tests that are related to #21530 * Making our template look more like Python's with the scope/role assignment. * The CloudEvent part of this test was getting set at too high a level and would affect other parts of the HTTP pipeline (including token authentication). * Was missing an explicit set of variables so the EnvironmentCredential works. * testing * EnvVars should be _under_ parameters! * A little too much copying... * Remove the old content-header code now that we're auto-generating it in the right spot. --------- Co-authored-by: Richard Park <[email protected]>
richardpark-msft
added a commit
that referenced
this issue
Oct 2, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Having to temporarily disable those tests in order to get a PR through for another part of EventGrid. This issue is tracking this so we revert it when the server-bug is fixed.
The failed lock tokens are coming back on valid ReleaseEvents() requests with
InternalServerErrorand a description ofNo result returned for release request..The text was updated successfully, but these errors were encountered: