arterialist / core_messenger Goto Github PK

Add logging layer and ability to add, remove, enable and disable specific logging channels (SQL logs for example)

There are two prompts shown on startup, which are Username and Port prompts. Currently if user cancels them, they appear again.

Currently username and port are prompted on each startup
Make it possible to save them and not request in the future

Text color in message input box becomes black after first erase of text or focus change

Currently main socket is in blocking mode, which may lead to UI freezes, especially on big timeout. It's critical to move socket to separate thread.

User should be able to apply global theme stored in ctheme file.

Theme can be applied after restart

Stack trace:

Traceback (most recent call last):
  File "core_messenger/widgets/dialogs/dialogs_head.py", line 32, in <lambda>
    self.new_dialog_button.clicked.connect(lambda: new_dialog_click_callback(self))
  File "core_messenger/callback/callbacks.py", line 36, in new_dialog_click_callback
    client_base.p2p_connect(host, int(port))
  File "core_messenger/client/client_base.py", line 128, in p2p_connect
    sock.connect(current_connection_address)
OSError: [Errno 113] No route to host

Save typed message when switching to another dialog and restore draft as well

App crashes sometimes when pressing OK button of "Invalid message" dialog. It's caused by incorrect work with threads and window object (probably)

Steps to reproduce:

1. open app and enter all stuff
2. toggle listening on
3. connect from terminal to 127.0.0.1:port
4. accept connection in app
5. type smth in terminal and smash enter
6. repeat step 5 until app crashes

Add ability to edit message

• from context menu
• with shortcut (arrow up or smth)

Add "edited" indicator (optional)

• Send Packet with nickname after receiving info request
• Display nickname in dialogs list
• Display nickname in "delete message" dialog

Optional: display nickname above message's text in opened dialog

App crashes when user edits message and tries to delete it.

Stack trace:

Traceback (most recent call last):
  File "main.py", line 271, in <lambda>
    delete_action.triggered.connect(lambda: delete_message_item_selected_callback(self.messages_list, message_item))
  File "core_messenger/callback/callbacks.py", line 173, in delete_message_item_selected_callback
    client_base.send_message(Packet(action=DeleteMessageAction(), message=delete_message_msg))
  File "core_messenger/client/client_base.py", line 174, in send_message
    layers.socket_send_data(current_connection, message, loaded_modules)
  File "core_messenger/client/layers.py", line 9, in socket_send_data
    what = action.process(what)
  File "core_messenger/client/modules/default_modules.py", line 38, in process
    data.message.text = base64.b64encode(data.message.text.encode()).decode()
AttributeError: 'NoneType' object has no attribute 'encode'

Reason: no text field check in Base64EncodeModule