Project

General

Profile

Actions

Bug #7681

open

There are no detectors on Hub

Added by Jakub Judiny 9 months ago. Updated 6 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/29/2023
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

https://mentat-hub.cesnet.cz/mentat/detectors/list

Even on Alt, many detectors are missing and the last detector was created 8 months ago.

So if someone clicks on "View details of detector DETECTOR" in context menu, 404 Not found is shown to the user.

Actions #1

Updated by Jakub Judiny 9 months ago

  • Assignee deleted (Jakub Judiny)
Actions #2

Updated by Rajmund Hruška 9 months ago

  • Status changed from New to Feedback

I am still waiting for #7635 to be merged in master and deployed on warden-hub. Pavel Kácha is there any estimation when this could be done?

Actions #3

Updated by Pavel Kácha 9 months ago

Rajmund Hruška wrote in #note-2:

I am still waiting for #7635 to be merged in master and deployed on warden-hub. Pavel Kácha is there any estimation when this could be done?

Keep fingers crossed, please. Idea IDs deduplication goes with it, and that means quite a big and probably slow migration (adding column) in Warden, which will need some thinking and planning (Warden just cannot be switched off for a couple of hours for upgrade).

However, for search dialogs, shouldn't we actually be merging this data (detectors from Warden API) with select distinct client data from DB? I believe that was the conclusion, as in our Idea db do exist client names which are not in Warden client db (essentially most of the secondary clients from Node sections).

Actions #4

Updated by Rajmund Hruška 6 months ago

Pavel Kácha wrote in #note-3:

Rajmund Hruška wrote in #note-2:

I am still waiting for #7635 to be merged in master and deployed on warden-hub. Pavel Kácha is there any estimation when this could be done?

Keep fingers crossed, please. Idea IDs deduplication goes with it, and that means quite a big and probably slow migration (adding column) in Warden, which will need some thinking and planning (Warden just cannot be switched off for a couple of hours for upgrade).

However, for search dialogs, shouldn't we actually be merging this data (detectors from Warden API) with select distinct client data from DB? I believe that was the conclusion, as in our Idea db do exist client names which are not in Warden client db (essentially most of the secondary clients from Node sections).

Well, in the mean time we can just turn off the detectors blueprint. I have already done that a couple weeks ago on mentat-alt and everything seems fine.

Actions

Also available in: Atom PDF