jabber.developer2
f9e184eda7
All checks were successful
CI Code / Check spelling (pull_request) Successful in 18s
CI Code / Check coding style (pull_request) Successful in 30s
CI Code / Linux (ubuntu) (pull_request) Successful in 4m51s
CI Code / Linux (debian) (pull_request) Successful in 6m59s
CI Code / Linux (arch) (pull_request) Successful in 10m12s
CI Code / Code Coverage (pull_request) Successful in 6m44s
Roll the tree back to the pre-merge tip3b673150b, undoing the upstream sync merge72f4f186d(303 files) and the 13 post-merge commits layered on top of it. Purpose: restore the last pre-sync baseline so the reported OMEMO/OTR encryption regressions can be reproduced against a known-good state and the upstream sync ruled in or out as the cause. Nothing is dropped from history; the merge and every post-merge commit remain reachable and can be cherry-picked back selectively. Baseline:3b673150bchore(chatlog): disable background message file logging (stage 1) Undoes merge:72f4f186dmerge: sync upstream profanity-im/profanity
35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
<!--- Provide a general summary of the issue in the Title above -->
|
|
|
|
<!--- More than 50 issues open? Please don't file any new feature requests -->
|
|
<!--- Help us reduce the work first :-) -->
|
|
|
|
## Expected Behavior
|
|
<!--- If you're describing a bug, tell us what should happen -->
|
|
<!--- If you're suggesting a change/improvement, tell us how it should work -->
|
|
|
|
## Current Behavior
|
|
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
|
|
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
|
|
|
|
## Possible Solution
|
|
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
|
|
<!--- or ideas how to implement the addition or change -->
|
|
|
|
## Steps to Reproduce (for bugs)
|
|
<!--- Describe, in detail, what needs to happen to reproduce this bug -->
|
|
<!--- Give us a screenshot (if it's helpful for this particular bug) -->
|
|
1.
|
|
2.
|
|
|
|
## Context
|
|
<!--- How has this issue affected you? What are you trying to accomplish? -->
|
|
|
|
## Environment
|
|
* Give us the version and build information output generated by `profanity -v`
|
|
* If you could not yet build profanity, mention the revision you try to build from
|
|
* Operating System/Distribution
|
|
* glib version
|
|
* libstrophe version
|
|
* Some bugs might be due to specific implementation in the server. `/serversoftware example.domain` can be helpful
|
|
|