[FR] [RFC] vis.delete_env accepts regex pattern
See original GitHub issueIn running experiments it is common, in developing/debugging stage, to start multiple runs. If each run starts an environment, the server will be soon flooded with too many envs. Currently, I usually use a combination of get_env_list
and delete_env
to clear all envs. But it would be cool to have a way to easily mass delete envs, e.g., by a regex pattern matching on the env names. 😃
It would be also cool to have a similar mass deleting functionality in UI as well.
cc @chail , who probably will also benefit from this 😃
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[FR] [RFC] vis.delete_env accepts regex pattern · Issue #646
In running experiments it is common, in developing/debugging stage, to start multiple runs. If each run starts an environment, ...
Read more >Regular Expression (Regex) Tutorial
Regular Expression, or regex or regexp in short, is extremely and amazingly powerful in searching and manipulating text strings, particularly in processing ...
Read more >Regular expression to match DNS hostname or IP Address?
It's easy to write one that works 95% of the time, but I'm hoping to get something that's well tested to exactly match...
Read more >4.1. Validate Email Addresses - Regular Expressions ...
You want to use a regular expression to validate this email address before ... is valid according to RFC 5322, which defines the...
Read more >Browse Expressions by Category
Regular Expression Library provides a searchable database of regular expressions. Users can add, edit, rate, and test regular expressions.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe a simple button somewhere here when checkboxes are ticked?
Hi @nikhilaravi, that could be an interesting solution. There’s one main approach, which starts by replacing the following
<select>
with some kind of multiselect: https://github.com/fossasia/visdom/blob/master/js/main.js#L1154-L1171 This will require some kind of state update to now be tracking an array of selected envIDs rather than just one.Then it becomes an issue of configuring
deleteEnv
to work properly here: https://github.com/fossasia/visdom/blob/master/js/main.js#L657-L663 The new state of selected envs to delete now being an array would require this to send a socket message for each of the applicable envs.Overall, it shouldn’t be a very involved change.