It's tough to debug a problem. #346
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#346
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
I understand the approach that you guys want, something that's easy to use and hide away issues. This principle doesn't work when we depend on developers to solve the problems. The x and y error information does not work, it's not enough information. I'd you ask you change strategy on this A tiny bit.
Sincere
Bugzbunny
Thanks for your feedback bugzbunny,
Do you have any example of an issue your encountered that inspired you this ticket?
What do you mean by "depending on developers"? source code is open. The design, while not extensively documented, is inspired by reasearch papers linked on our home page.
Would you like a special page on the documentation explaining basic ways to debug Garage?
Is it linked to a previous issue you opened and were mentioning that we don't find help on serch engine/google? For this last part, I would like to mention that Garage is very young, and by discussing together, we are creating the initial content that people will search later. If you think that Matrix and Gitea are not appropriate for your problem, could you give us some examples/idea of a "platform"/software that would be appropriate?