Skip to content

Conversation

@link2xt
Copy link
Collaborator

@link2xt link2xt commented Sep 23, 2025

This is mostly for the bots: deltachat-bot/group-editor-bot#9

@link2xt link2xt force-pushed the link2xt/usmzlnkpttzn branch from 54ecd25 to cdd3b9b Compare September 23, 2025 15:51
@link2xt link2xt changed the title docs: SecurejoinInviterProgress never returns an error Add chat_id to SecurejoinInviterProgress Sep 23, 2025
@link2xt link2xt force-pushed the link2xt/usmzlnkpttzn branch from cdd3b9b to b267d46 Compare September 23, 2025 17:20
Copy link
Contributor

@missytake missytake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't judge all the rust, but great!

Why is SECUREJOIN_INVITER_PROGRESS always 1000 nowadays? I saw events earlier that still had 600,800, etc.

@link2xt
Copy link
Collaborator Author

link2xt commented Sep 23, 2025

Why is SECUREJOIN_INVITER_PROGRESS always 1000 nowadays? I saw events earlier that still had 600,800, etc.

These events were not used anyway, only very old versions of Delta Chat showed a progress bar on the inviter side. Other events were removed in #7198 as for earlier events we cannot say for sure which group/chat the event belongs to.

@link2xt link2xt force-pushed the link2xt/usmzlnkpttzn branch from b267d46 to 5d66215 Compare September 23, 2025 19:28
@link2xt link2xt force-pushed the link2xt/usmzlnkpttzn branch from 5d66215 to bd3ec5a Compare September 23, 2025 21:56
// which only have a single device
// and tests which don't care about the chat ID,
// so we pass invalid chat ID here.
let chat_id = ChatId::new(0);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit hacky, but I did not want to change the tests that depend on having this event on a second device. Actual users of this event should not be affected.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to add another event for ChatGroupMemberAdded messages in the future, which should be emitted from receive_imf where we know the chat id as well. For SecurejoinInviterProgress, zero chat id is fine i think

// which only have a single device
// and tests which don't care about the chat ID,
// so we pass invalid chat ID here.
let chat_id = ChatId::new(0);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to add another event for ChatGroupMemberAdded messages in the future, which should be emitted from receive_imf where we know the chat id as well. For SecurejoinInviterProgress, zero chat id is fine i think

@link2xt link2xt merged commit a506e2d into main Sep 23, 2025
29 checks passed
@link2xt link2xt deleted the link2xt/usmzlnkpttzn branch September 23, 2025 23:23
@link2xt
Copy link
Collaborator Author

link2xt commented Sep 23, 2025

Issue for adding ChatGroupMemberAdded: #7183

@missytake
Copy link
Contributor

Is anything necessary to pass this to the python RPC bindings? I still get events like these without chat_id:

{'chat_type': 120, 'contact_id': 26, 'kind': <EventType.SECUREJOIN_INVITER_PROGRESS: 'SecurejoinInviterProgress'>, 'progress': 800, 'account': Account(manager=<deltachat_rpc_client.deltachat.DeltaChat object at 0x7f1ba19e8d10>, id=1)}
{'chat_type': 120, 'contact_id': 26, 'kind': <EventType.SECUREJOIN_INVITER_PROGRESS: 'SecurejoinInviterProgress'>, 'progress': 1000, 'account': Account(manager=<deltachat_rpc_client.deltachat.DeltaChat object at 0x7f1ba19e8d10>, id=1)}

@missytake
Copy link
Contributor

Nevermind, it just seems that the steps in https://github.com/chatmail/core/tree/main/deltachat-rpc-client are incomplete to update deltachat-rpc-server after rust code changed. I had to manually copy the deltachat-rpc-server rust binary to my virtual environment. It works now :)

@link2xt
Copy link
Collaborator Author

link2xt commented Sep 25, 2025

Core 2.16 is not tagged yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants