Bug #4035
Erroneous behavior in case of objects with same name
| Status: | Assigned | Start date: | 06/18/2013 | ||
|---|---|---|---|---|---|
| Priority: | Medium | Due date: | |||
| Assignee: | Christos KK Loverdos | % Done: | 30% |
||
| Category: | - | Spent time: | - | ||
| Target version: | - |
Description
Scenario that reproduces the problem (also attached):
The same file there is in two different folders in pithos.
Publish both files.
In the shared by me panel select both and click Share.
In the Share File pop up window (refers only to one of them Issue #4033)
Uncheck Public on the internet
Only one is unpublished and disappears from shared by me.
The other one stays there but if the user selects Share File the public check box is already unchecked.
This happens because the client requests from the server the wrong path
(the path of the object that was actually unpublished)
The same behavior occurs also if the user instead of Share File selects File Properties
This issue occurs also, if the user opens a pop up window that refers to a specific object
and then tires to open a pop up window that refers to another object with the same name under another folder.
Related issues
Associated revisions
Simplify boolean condition
Refs #4035
WIP Investigating #4035
Very inconsistent behavior of the selection mechanism. I get erroneous behavior
with 20 deployments in a row and then suddendly the correct behavior
for any new deployments.
By deployment, I mean rebuild + deploy. The only thing I do in the mean time
is put some extra logging statements all over the relevant places.
Refs #4035
History
#1 Updated by Christos KK Loverdos over 10 years ago
- Status changed from New to Assigned
- % Done changed from 0 to 10
- Create folder
path1 - Create folder
path2 - Upload file
scenario.pdf(or some other file) to folderpath1 - Make
path1/scenario.pdfpublic - Upload the same file
scenario.pdfto folderpath2(I assume that the name is what matters here) - Now, try to make
path2/scenario.pdfpublic by the same procedure used forpath1/scenario.pdf. You will notice that the "Public on the Internet" check box is already set. This is clearly a bug.
#2 Updated by Christos KK Loverdos over 10 years ago
- % Done changed from 10 to 20
Just a small update.
It seems the file selection mechanism is broken and in Step 6 (above) although we try to make path2/scenario.pdf public, somehow path1/scenario.pdf is still selected. That's probably why things get messed up.
#3 Updated by Christos KK Loverdos over 10 years ago
- % Done changed from 20 to 30
OK, here is the situation.
As described in the message of the latest commit, 8474a42a9003522ca6d99b8c28c57426e5545f6b, things get bizarre and there must be something wrong with the selection mechanism.
Now, to comment on the original report of this Issue, and with respect to #4033, the "Share" menu item should not have appeared in the first place. I will work in this direction.
#4 Updated by Christos KK Loverdos over 10 years ago
Watchers FYI:
I have paused the investigation of this and #4033 due to other assignments.