- Issue created by @cspitzlay
- Status changed to Needs review
4 months ago 1:01pm 11 September 2024 - 🇯🇵Japan ptmkenny
Thank you for reporting this. It looks like this was a case of bad renaming; MR33 should fix it for 2.x.
I'm going to try to add a test for this because jsonrpc_discovery has no test that validates the basic output. I think there should be a test that enables jsonrpc_discovery and jsonrpc_core together and then ensures that jsonrpc/methods returns the methods added by jsonrpc_core. I think such a test would've caught this before the release.
- 🇩🇪Germany cspitzlay 🇩🇪🇪🇺
Thanks for your work on this.
I can confirm that MR33 fixes the issue for me.
- 🇯🇵Japan ptmkenny
Thank you for confirming it works. I'm going to make the test assert that we actually get a method as a response before committing this so that hopefully any obvious breakage of the endpoint will be caught immediately in the future.
- 🇯🇵Japan ptmkenny
I'm having trouble getting the test to work (the admin user is not seeing the methods added by jsonrpc_core for some reason), so I will create a follow-up issue to extend the test. In the meantime, I am going to prioritize fixing this by making a new release.
-
ptmkenny →
committed f99e14d5 on 2.x
Issue #3473531 by ptmkenny, cspitzlay: Crash on jsonrpc/methods route
-
ptmkenny →
committed f99e14d5 on 2.x
-
ptmkenny →
committed e3f58d64 on 3.x
Issue #3473531 by ptmkenny, cspitzlay: Crash on jsonrpc/methods route
-
ptmkenny →
committed e3f58d64 on 3.x
- Status changed to Fixed
4 months ago 1:24am 12 September 2024 - 🇯🇵Japan ptmkenny
Follow-up: 📌 Add a test for jsonrpc_discovery that verifies the methods returned Active
Automatically closed - issue fixed for 2 weeks with no activity.