You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now that we have the nuclei view, we should have a way in the app to grab nuclei IDs for seg IDs that have them.
This wouldn't necessarily be a new attribute for a task though, could be part of task metadata or just something that is dynamically queried.
Potential solution:
Adapt nuclei viewer such that instead of querying the nuclei table through cave, it just uses a local cache file that is stored in static. If the static file is more than a day old, it is regenerated upon query.
nuclei viewer should accept both root IDs and nuclei IDs. if a root ID is inputted, the corresponding nuclei ID is found from the cached table and displayed.
The text was updated successfully, but these errors were encountered:
now that we have the nuclei view, we should have a way in the app to grab nuclei IDs for seg IDs that have them.
This wouldn't necessarily be a new attribute for a task though, could be part of task metadata or just something that is dynamically queried.
Potential solution:
Adapt nuclei viewer such that instead of querying the nuclei table through cave, it just uses a local cache file that is stored in static. If the static file is more than a day old, it is regenerated upon query.
nuclei viewer should accept both root IDs and nuclei IDs. if a root ID is inputted, the corresponding nuclei ID is found from the cached table and displayed.
The text was updated successfully, but these errors were encountered: