import/delete/update texture broken #21

New Issue

2019-06-08T21:57:14+02:00

localhorst commented

2019-06-08 21:57:14 +02:00

No description provided.

localhorst added this to the client 1.0 milestone 2019-06-08 21:57:14 +02:00

localhorst self-assigned this 2019-06-08 21:57:14 +02:00

localhorst changed title from ~~update texture broken~~ to import/delete/update texture broken

2019-06-09 10:13:49 +02:00

localhorst commented

2019-06-09 10:48:44 +02:00

the server sends an exception that the texture that will be modified is not stored on the server

localhorst added the bug label 2019-06-09 10:49:23 +02:00

localhorst commented

2019-06-09 10:59:15 +02:00

println(data.textureHash):

A5BAF2A31547322D68AA78F0EC931EEC6A80F0313A15499B95743A5B6527B36A

println(con.getTextureById(data.id)?.textureHash):

A5BAF2A31547322D68AA78F0EC931EEC6A80F0313A15499B95743A5B6527B36A

--> same, but on server

                if !data_store.delete(&delete) {
                return Err(ProtocolError::Conflict(
                    "Delete Texture was modified!".to_string(),
                ));

will be called

println(data.textureHash): A5BAF2A31547322D68AA78F0EC931EEC6A80F0313A15499B95743A5B6527B36A println(con.getTextureById(data.id)?.textureHash): A5BAF2A31547322D68AA78F0EC931EEC6A80F0313A15499B95743A5B6527B36A --> same, but on server if !data_store.delete(&delete) { return Err(ProtocolError::Conflict( "Delete Texture was modified!".to_string(), )); will be called

localhorst closed this issue

2019-06-09 10:59:15 +02:00

localhorst reopened this issue

2019-06-09 10:59:23 +02:00

localhorst commented

2019-06-09 13:06:38 +02:00