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
Suitcase shows an error if you try to reset an app server that is empty. It doesn't crash, it just shows an error message. Additionally it prints a log message:
deleteTableDefinition: client response is 404:
java.lang.IllegalStateException: Unexpected status code: 404
at org.opendatakit.suitcase.net.ResetTask.doInBackground(ResetTask.java:62)
at org.opendatakit.suitcase.net.ResetTask.doInBackground(ResetTask.java:15)
at javax.swing.SwingWorker$1.call(SwingWorker.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at javax.swing.SwingWorker.run(SwingWorker.java:334)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Steps to reproduce the problem
Open suitcase. Select Reset from the Upload tab. Wait for it to complete. Select Reset again. When it gets to step 2 that deletes table definiitions, you will immediately get an error.
Expected behavior
The end goal of a reset is to have an empty server, so we should show no error in this case. We should just silently continue as long as we end up with that empty server. The error implies that the server failed to be cleaned.
The text was updated successfully, but these errors were encountered:
Software and hardware versions
Suitcase ODK 2.0.0 rev 214
Problem description
Suitcase shows an error if you try to reset an app server that is empty. It doesn't crash, it just shows an error message. Additionally it prints a log message:
Steps to reproduce the problem
Open suitcase. Select Reset from the Upload tab. Wait for it to complete. Select Reset again. When it gets to step 2 that deletes table definiitions, you will immediately get an error.
Expected behavior
The end goal of a reset is to have an empty server, so we should show no error in this case. We should just silently continue as long as we end up with that empty server. The error implies that the server failed to be cleaned.
The text was updated successfully, but these errors were encountered: