-
Notifications
You must be signed in to change notification settings - Fork 597
Conversation
Nice catch. The tests seem to work for me, but there's definitely more to clean up as you mentioned. I guess I started making the code match this line:
/metrics/query syntax, but might be easier to just roll back to /metricsquery style route. And instead I'll update the javascript to use the proper api call.
|
My guess is technical debt.
I agree. Good REST API design necessitates versioning of the API as well as nesting under path routes. All metrics queries should be nested under the Edit: I stand corrected, this is generating a query request.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to pay down tech debt. I think there might be a non-functional Python docstring update required:
### <a name="metricsquery">Metrics Query Language</a> |
I'm running into some other issues with parameter mismatch betwen Another issue I'm seeing is an exception on an API call because |
I have always had issues bringing up the UI so I can only look at the code.
The naming convention for topologies has changed on K8s and I am not sure if this would affect the UI.
According to the |
So for testing
|
It looks like alias may be a bit of a misnomer, it may be better to call it |
I've been banging my head against this code. Things are definitely broken. I have more drastic changes, but I haven't pushed them yet because I'm still testing. The |
I am time-constrained for the next few weeks and I still cannot bring up the UI. I typically find it faster to jump in with a debugger and find the issue causing the problem and address it there. Failing that it is time to find what caused the issue. We need to isolate the commit in which this happened. I would start by checking out the last tagged release to see if the UI is working there. If it is, run a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incredible work!
I have not had the time to deployment test this PR and it would be nice if someone else could assist with that. There are some old review comments that still need to be addressed a handful of new ones. Overall it is pretty much in a mergeable state.
Co-authored-by: Saad Ur Rahman <[email protected]>
Co-authored-by: Saad Ur Rahman <[email protected]>
This was added for debugging to update the Log object and is no longer required.
I just removed a reference to update the global |
I can't figure out why the timeline is not working. I've tracked my issue to this line of code. Within the |
I am not sure but I do not think there is a need to convert the zipped together values into a
Maybe try this: return dict(zip(keys, values)) |
I think |
I believe |
Did you do that print within the Beware that p.s.
both are equivalent and will be handled the same way due to python's duck typing, as both a generator (returned by zip, in type annotations it is compatible with |
Thank you for the detailed explanation! |
I think this PR is finally done. I'm now able to see the timeline in the UI and most of the functionality is working (as good as it probably was working in the past). There are some super deep menus I think I'd like to clean up in the future, but this is good to go. Thank you for the help @surahman @Code0x58 and @thinker0 ! Edit: I'll add. This PR fixes the following functionality which was temporarily broken with the upgrade to Python 3. Most of the issues were related to the Heron UI and Heron Tracker APIs. Some of the issues were due to the updated code enforcing type hints in and out of methods. I've manually verified the below items.
|
+1 My Env Test Success |
#3814 typo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⭐ ⭐ ⭐ ⭐ ⭐ 👏
Fixes #3784 and Fixes #3785