Easier way to delete remote projects (and files) locally
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 32/100
Línea de trabajo
Start with the remote dialog and project browser described in the issue, and inspect how locally cached projects and files are represented under the Binary Ninja remote directory. Define the scope for removing local copies without server deletion, then verify that the relevant UI actions leave remote projects intact and reclaim local storage.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I have quite a few remote projects and these projects locally take up over 100gb of storage, I need to clear them out locally without deleting them from the remote.
To do this now I need to open each project I no longer want and get the guid of it, then go to '/Users/emesare/Library/Application Support/Binary Ninja/remote' and delete the associated bnpr.
If I want to delete specific files in a remote i need to open the project, locate the file and then open the file location and delete. Seeing as i have open and close 200 remote projects this is quite tedious if i am looking to only delete files which take up a considerable amount of space. This particular issue of trying to delete remote project files locally I am less interested in, I would accept just the option to delete remote projects from the remote dialog.
I would prefer if the remote dialog offered a way to delete the project locally (that requires no deletion permissions on the server) and a way to delete project files locally (that requires no deletion permissions on the server) from the project browser.
Related https://github.com/Vector35/binaryninja-api/issues/7955
- Lenguaje dominante
- C++
- Estrellas
- 1.3k
- Forks
- 298
- Merge medio
- 5 d 5 h
- PR fusionados (30 d)
- 19
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Vector35/binaryninja-api
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8540 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8516 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
Vector35/binaryninja-api#8503 ·
-
normalize time logs from WARP Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8446 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8444 ·
Todos los issues de Vector35/binaryninja-api
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 92/100
autowarefoundation/autoware_universe#13413 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
automated-analysis bug memory-safety
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
gazebosim/gz-sensors#662 · 1 comentario ·