melissiproject / client Goto Github PK

When you "extract archive" using nautilus and possibly other file managers, the manager creates a directory with the name of the archive and then extracts all its contents in there. When the extraction ends, nautilus checks if there is only only directory in the folder, and if yes moves this directory, back in the same directory where the archive resides. Finally deletes the self created directory.

This behaviour can cause an extra directory to be created in the server which doesn't get deleted

Steps to reproduce:

1. create a directory "work"
2. create a file into "work"
3. zip work so that the archive contains both directory and the file
4. name the archive work.zip
5. move the archive into the "melissi" folder
6. use nautilus to "Extract here"
7. After syncing there should be a cell named "work/work" which shouldn't be there.

Motivation ("The Why")

Example

How

Current Behaviour

Desired Behaviour

References

• n/a

Originally posted by @eye-make in npm/rfcs#738

When trying to start melissi client I get:

Cannot use this socket. Please specify another socket

my ~/.config/melissi/config
file contains:

username = chefarov
no-desktop = False
resource = redalert
socket = /home/chefarov/.config/melissi/melissi.sock
database = sqlite:////home/chefarov/.config/melissi/melissi.db
new-root-path = /home/chefarov
host = http://localhost:8000/
desktop-notifications = True
password = chefarov

I had to delete the ~/.config/melissi/melissi.sock which fixed the problem

When registering you get error:
first_name is required
last_name is required

Client depends on

python-webkit
python storm
python-pyinotify
xdg-utils

File and directory delete doesn't work

Motivation ("The Why")

Example

How

Current Behaviour

Desired Behaviour

References

• n/a

Originally posted by @eye-make in npm/rfcs#738

Originally posted by @eye-make in #18

When client is unable to connect GetUpdates pile up in the Queue. As a result when a connection is established, multiple GetUpdates are executed

Steps to reproduce:

1. Start a client, with a server
2. Wait a minute or so, so that the client fails to connect a few times
3. Start the server
4. Multiple GetUpdates get executed

Initial configuration wizard depends on having an x server running. This is not an option on headless servers. A workaround must be supplied for users using the --no-desktop flag exclusivelly

Collect the messages from the dbus to check if internet connection is on in order to connect/disconnect the client.

Users mjust be able to add Melissi desktop client to startup. Make this a "Preferences" menu option

Fail to start when the melissi folder is moved or deleted.

Originally posted by @eye-make in #16

Nothing happens

When client is configured to use http and server only supports https where are error messages displayed on the console but nothing on the desktop of the user. The icon remains green and looks like everything is OK

Update client status images to match the latest logo and fix paths

Error as reported by mikeX:

(melissi:17353): libglade-WARNING **: Error loading image: Failed to open file '/usr/lib/pymodules/python2.6/melissi/data/glade/../images/icon-ok.svg': No such file or directory

When creating a directory that already exists, filesystem returns an error but the client tries to create the directory on the server anyway.

This is because inotify generates the corresponding messages anyway.

We must somehow recognize that the action fails on the filesystem level and ignore it.

Command line Melissi commander "cmelissi.py" does not get a /usr/bin entry.