primordic/IssueDupesLite huggingface dataset:
Repository: matplotlib/matplotlib

Issue #14992: IndexError: tuple index out of range with pandas 0.25.
Created: 2019-08-06T09:23:03Z
Bug report
Bug summary

I have reported the issue in details here
basically after an upgrade to 3.1.1 it drops the error:

IndexError: tuple index out of range

all other details inclduing the CSV file and code are in the above link.

Duplicate issue #15120: the program written in spyder3.3.3 can't run in spyder3.3.6
Created: 2019-08-25T15:27:22Z
Bug report
the program .py written in spyder3.3.3 can't run in spyder3.3.6. It seems that the command axes[].plot() from matplotlib has sth wrong in spyder3.3.6. The alarm messenge is : tuple index out of range
I report the probelm to the admin of spyder. He reply me that it is the problem in matplotlib not in spyder, and I should update my code.
What can I do about updating my code? my matplotlib in anaconda is 3.1.0
Bug summary
It seems that the command axes[].plot() from matplotlib has sth wrong in spyder3.3.6. The alarm messenge is : tuple index out of range

Code for reproduction

# Paste your code here
#
#
for i in range(n):
    irf_data = pd.DataFrame(
            [irf_1[:,i], irf_2[:,i], irf_3[:,i]]).T
    irf_data.columns = ['point', 'up', 'lower']
    
    axes[i//2, i % 2].plot(irf_data.index, irf_data.1,
                           color = 'blue', linestyle = '-')
Actual outcome
tuple index out of range

Expected outcome


Matplotlib version


Operating system:
Matplotlib version:
Matplotlib backend (print(matplotlib.get_backend())):
Python version:
Jupyter version (if applicable):
Other libraries:

Closing comment (2019-08-25T17:00:14Z): This is most probably a duplicate of #14992 and fixed by  #15007 (on the matplotlib side) and/or pandas-dev/pandas#27818 (on the pandas side).
What this means is that matplotlib 3.1.1 or lower is not compatible with pandas 0.25.0 when plotting the index of a dataframe.
Options are:

Use numpy arrays (matplotlib tries to support pandas as good as possible, but there are still some hickups every now and then)
Wait for matplotlib 3.1.2 to be released.
Use pandas 0.24.x or 0.25.1 (once it's released)
Repository: matplotlib/matplotlib

Issue #26681: [TST] Upcoming dependency test failures
Created: 2023-09-02T06:32:18Z
The weekly build with nightly wheels from numpy and pandas
has failed. Check the logs for any updates that need to be
made in matplotlib.
https://github.com/matplotlib/matplotlib/actions/runs/6056670267

Duplicate issue #26891: [TST] Upcoming dependency test failures
Created: 2023-09-23T06:35:46Z
The weekly build with nightly wheels from numpy and pandas
has failed. Check the logs for any updates that need to be
made in matplotlib.
https://github.com/matplotlib/matplotlib/actions/runs/6281965538

Closing comment (2023-09-25T18:39:03Z): Still duplicate of #26681
Repository: matplotlib/matplotlib

Issue #6108: Plot update issue within event callback for multiple updates
Created: 2016-03-04T11:53:03Z
Platfrom/Tools Information:
Platform: Windows 10 x64
Python Version: 2.7.11
Python Distribution: Anaconda 2.5.0 (64-bit)
Matplotlib Version: 1.5.1
Issue Description:
When I use an event callback that updates a figure two (or more) times within the callback, only the last update on an element seems to be applied. Concretely, the plot is updated only when the event callback returns.
Example:
In the following example the expected outcome would be:

A figure with an axis with title "1"
When I press a key:
--i. "Loading" is printed to the console and the axis title is updated to "Loading"
--ii. After 3 seconds "2" is printed to the console and the axis title is updated to "2"

However, the observed outcome is:

A figure with an axis with title "1"
When I press a key:
--i. "Loading" is printed to the console, but the axis title is not updated
--ii. After 3 seconds "2" is printed to the console and the axis title is updated to "2"

from matplotlib import pyplot as plt
import time


def slow_plot(figure, axis):
    print "Loading"
    axis.set_title("Loading")
    figure.canvas.draw()

    time.sleep(3)

    print "2"
    axis.set_title("2")
    figure.canvas.draw()


def main():
    figure, axis = plt.subplots(1, 1)

    axis.set_title("1")
    figure.canvas.draw()
    figure.show()

    def on_key_press(event):
        slow_plot(figure, axis)

    figure.canvas.mpl_connect("key_press_event", on_key_press)

    plt.show()

if __name__ == "__main__":
    main()

Additional Information:

This code works as expected if I step through it step by step using the debugger.
Tried running the same piece of code on a Mac and I got the expected behavior.
I remember something similar working as expected about a year ago, so maybe this bug was introduced with matplotlib 1.5.1, but I can't say for sure. I'll try installing 1.4.* versions when I get some time and update the info.

Duplicate issue #6078: mpl_event
Created: 2016-02-29T19:21:39Z
I recently installed the Anaconda distribution of python 2.7 on a MacBook Air running OS 10.9.5.
I've run "condo update --all"
I believe this installs:  matplotlib 1.5.1 np110py34_0
I am attempting to run sample event handling code from matplotlib found at:
http://matplotlib.org/1.5.1/examples/event_handling/keypress_demo.html
The code successfully brings up a window, puts the data on it, etc. It should toggle a label on the screen when the x key is pressed.
However, it only toggles the label when I press the x key and then move the mouse cursor out of the window.
Any suggestions regarding how to fix this behavior would be greatly appreciated.

Closing comment (2016-03-04T15:18:49Z): roughly related to #6108 but with the opposite sign.
I can not reproduce this issue with the Qt backend on linux.
Repository: matplotlib/matplotlib

Issue #6827: Bug with colorbar and low DPI output in PDF
Created: 2016-07-25T03:29:32Z
The following example (with Matplotlib 2.0.0b3) causes the colorbar inside the colorbar axes to be offset when outputting to PDF with a low DPI:
import matplotlib.pyplot as plt

fig = plt.figure()
ax = fig.add_subplot(1,1,1)
im = ax.imshow([[1]])
fig.colorbar(im)
fig.savefig('colorbar_test.pdf', dpi=7)


This wasn't an issue with Matplotlib 1.4:

and the bug was apparently introduces in Matplotlib 1.5:

Duplicate issue #17103: Colorbar fill not aligned with containing box
Created: 2020-04-11T21:12:41Z
Bug report
Bug summary
Definitely a low-priority bug, but at some figure sizes, there seems to be an issue with the colorbar not being drawn at the correct position in some backends (seems like PDF and SVG are affected, but not Agg).
The colorbar "fill" (the actual colored bit) will not line up with the box that contains it (the black marker edge that makes the rectangle that is filled by the color bar, see below). Seems like some sort of rounding issue.
I have a more "dramatic" example, but still need to distill it to a minimum working example, as it is a plot of proprietary data.
Code for reproduction

import matplotlib.pyplot as plt
import matplotlib.cm

fig, ax = plt.subplots(figsize=(2, 1.5))

plt.plot()

sm = matplotlib.cm.ScalarMappable()
sm.set_array([])
plt.colorbar(sm)

plt.savefig('/home/bbeltr1/Downloads/test.svg')
plt.savefig('/home/bbeltr1/Downloads/test.pdf')
plt.savefig('/home/bbeltr1/Downloads/test.png', dpi=800)
Actual outcome

SVG:

PDF:

PNG:

Expected outcome
The PNG output has the expected outcome.


Matplotlib version


Operating system: Debian Jessie
Matplotlib version: master
Matplotlib backend (print(matplotlib.get_backend())):
Python version: 3.7
Jupyter version (if applicable):
Other libraries:

Closing comment (2020-04-16T19:18:31Z): I'm fairly certain this is a duplicate of #6827 then.
Repository: matplotlib/matplotlib

Issue #25789: [TST] Upcoming dependency test failures
Created: 2023-04-29T06:21:03Z
The weekly build with nightly wheels from numpy and pandas
has failed. Check the logs for any updates that need to be
made in matplotlib.
https://github.com/matplotlib/matplotlib/actions/runs/4837230527

Duplicate issue #25826: [TST] Upcoming dependency test failures
Created: 2023-05-06T06:16:10Z
The weekly build with nightly wheels from numpy and pandas
has failed. Check the logs for any updates that need to be
made in matplotlib.
https://github.com/matplotlib/matplotlib/actions/runs/4900029117

Closing comment (2023-05-06T06:30:22Z): Duplicate of #25789
Repository: matrix-org/dendrite

Issue #3260: unable to add email address to my account
Created: 2023-11-07T16:52:55Z
Background information


Dendrite version or git SHA: dendrite-0.13.4
SQLite3 or Postgres?: postgresql13-server-13.12
Running in Docker?: no
go version: n/a
Client used (if applicable): element-web-1.11.47 & Element Version 1.11.47 (1.11.47) on macOS

Description

What is the problem: unable to add email address to my account (in parameters)
Who is affected: me as a client of this instance (currently the only user of this instance)
How is this bug manifesting: message in Element GUI. Error reads "MatrixError: [400] Untrusted server '' (https://myhost/_matrix/client/v3/account/3pid/email/requestToken)"
When did this first appear: at my first try to add my email address to my account parameters

Steps to reproduce


connect to the server either with desktop or web Element
browse to account parameters, scroll to email address
fill in an email address and submit ("Add")

a popup appears that reads:
MatrixError: [400] Untrusted server '' (https://myhost/_matrix/client/v3/account/3pid/email/requestToken)
In the log file:
time="2023-11-07T16:50:50.963513546Z" level=error msg="threepid.CreateSession failed" func=github.com/matrix-org/dendrite/clientapi/routing.RequestEmailToken file="github.com/matrix-org/dendrite/clientapi/routing/threepid.go:83" error="untrusted server" req.id=zuvRVVioUaos req.method=POST req.path=/_matrix/client/v3/account/3pid/email/requestToken

Duplicate issue #3318: How to use email or mobile phone number to register and login?
Created: 2024-02-05T18:57:33Z
Email and phone number are the most common registration and login methods.
How to get Dendrite to support them?

Closing comment (2024-02-28T20:32:10Z): Dupe of #3260 (probably some others, just doing some cleanup)
And well, currently not implemented.
Repository: matrix-org/dendrite

Issue #2150: Dendrite 0.6.2 fails to sync/federate
Created: 2022-02-06T08:46:39Z
Background information
Dendrite version or git SHA: v0.6.2 (last known good was 0.6.0)
Monolith or Polylith?: monolith
SQLite3 or Postgres?: postgresql
Running in Docker?: no
go version: 1.16.13 and 1.18beta1
Client used (if applicable): app.element.io, Hydrogen and Fluffychat

Description
Dendrite fails to receive new events for any room and fails to sync existing events to some clients as of version 0.6.2. In the clients, is shown by either frozen rooms and disconnection messages (element) or never finishing the initial sync (Fluffychat and Hydrogen). Rolling back to 0.6.0 resolves the issue.
The following logs may be relevant:
level=debug msg="Transaction: Failed to query room version for room!" error="context canceled" req.id= req.method=PUT req.path=/_matrix/federation/v1/send/<event 1>
level=debug msg="Transaction: Failed to parse event JSON of event {\"auth_events\":[\"\",\"\",\"\"],\"content\":{\"algorithm\":\"m.megolm.v1.aes-sha2\",\"ciphertext\":\"\",\"device_id\":\"\",\"sender_key\":\"\",\"session_id\":\"\"},\"depth\":20,\"hashes\":{\"sha256\":\"h0hdF/eV9J+\"},\"origin\":\"matrix.org\",\"origin_server_ts\":,\"prev_events\":[\"$\"],\"prev_state\":[],\"room_id\":\"!:.\",\"sender\":\"@\",\"signatures\":{\"matrix.org\":{\"ed25519:a_RXGa\":\"h2jmBBg\"}},\"type\":\"m.room.encrypted\",\"unsigned\":{\"age_ts\":}}" error="gomatrixserverlib: unsupported room version ''" req.id=KzqABiJjMlbU req.method=PUT req.path=/_matrix/federation/v1/send/<event 1>
http: superfluous response.WriteHeader call from github.com/prometheus/client_golang/prometheus/promhttp.(*responseWriterDelegator).WriteHeader (delegator.go:65)

NOTE: user data from the logs has been stripped.

Duplicate issue #2222: Signing in from a new session does not sync room information
Created: 2022-02-22T21:11:28Z
Background information


Dendrite version or git SHA:  0.6.4
Monolith or Polylith?: Monolith
SQLite3 or Postgres?: Postgres
Running in Docker?: No
go version: go version go1.17.3 linux/amd64
Client used (if applicable): Element Web

Description

What is the problem: Signing in from a new session does not sync room information
Who is affected: Clients on my server
How is this bug manifesting: When I login
When did this first appear: Sometime after switching to jetstream

I have been having issues related to #2181 but this is different again. When logging onto new sessions it all appears to work correctly but the room information is not sync correctly. The rooms show up in Element as "Empty Room", I can't see any previous messages, it seems like even the fact the room was encrypted is lost.
Existing clients seem to be fine though

Steps to reproduce


Login from a new device with Element
Verify session with security key
Look at the users rooms, all rooms are listed as "Empty Room" and the faviroute and low priority status is lost. There are also no previous messages.

Closing comment (2022-03-04T07:12:36Z): Still seems to be a problem, it seems very related to #2150 though
Repository: matrix-org/dendrite

Issue #1429: Add smart /health endpoint that checks if dependent services available
Created: 2020-09-20T12:55:11Z
Is your feature request related to a problem? Please describe.
Adding a /health endpoint allows orchestration tools to see if a component is healthy and "restart" the process, if needed.
Describe the solution you'd like
Ping the database connection and/or other components required to run a specific component.

Duplicate issue #1668: Add health check endpoint
Created: 2020-12-19T08:22:22Z
Description:
Add a health check (/health) endpoint that allows orchestration tools to see if a component is up and running.
Potential solutions
Add a dumb /health endpoint that just returns 200 OK.
As a follow-up, we can improve this to check that the processs is actually healthy and its dependent services(database, kafka) are available -> #1429

Closing comment (2021-07-09T10:32:05Z): Dupe #1429 - we don't need 2 open issues for this.
Repository: matrix-org/dendrite

Issue #1743: Cannot reject invites over federation
Created: 2021-01-30T02:34:44Z
I'm on dendrite.matrix.org.

Description
I cannot reject invites

Steps to reproduce

Invite a user on a server running Dendrite
Revoke their invite
They will not be able to reject the invite

Edit: after doing a bit more testing only invites over federation have this issue. Inviting/disinviting other users on dendrite.matrix.org (for example) works great.
Important: After doing a few more tests, it looks like revoking their invite is a necessary step in these tests (rejecting invites before having them revoked seems to work just fine)

Duplicate issue #1861: Can't reject invite of no-longer existing room
Created: 2021-05-19T15:03:06Z
Background information

Dendrite version or git SHA:  2948ffd
Monolith or Polylith?:  Monolith
SQLite3 or Postgres?:  SQLite
Running in Docker?:  No.
go version: 1.15.10

Description
Months ago I received several invites for conversations but by the time I saw them I could neither accept nor reject them anymore.
When trying to reject an invite I get:

Failed to leave room "!IaGVtVRpgDwQuKawsw:xxx.xxxx" through 1 server(s)

When trying to accept any of them:

You are not invited to this room.

Now I have 21 invites in my Element that I can neither accept nor reject.
Steps to reproduce
I am not exactly sure how that goes but it might be reproducible by

Invite a dendrite user from another instance into a chat
Wait a while for the invite to arrive on the dendrite server
Remove the channel from the origin server
On the dendrite client try to join / reject the invite.

Closing comment (2021-07-09T11:37:08Z): Dupe #1743 - we're aware of this issue and will try to address this ASAP
Repository: matrix-org/dendrite

Issue #1705: Migration process from Synapse
Created: 2021-01-13T09:33:28Z
It might be nice to provide a documentation for the migration process from synapse to dendrite, at least for homeserver users.
Maybe we can track progress for this in this issue ?

Duplicate issue #1915: How to migrate from synapse to dendrite ?
Created: 2021-07-12T17:18:54Z
How to migrate from synapse to dendrite ?
and is dendrite stable enough for production build ?

Closing comment (2021-07-15T11:17:19Z): Dupe of #1705
Dendrite is not stable enough for a production build, see the blog post about this: https://matrix.org/blog/2020/10/08/dendrite-is-entering-beta specifically:

In practice, this means Dendrite is now ready for experimentation by adventurous Matrix sysadmins. It is NOT ready for production usage yet, but we need folks to test it and help us iron out the remaining bugs! Please do not trust it with sensitive data yet, and we don’t recommend trying to run it at scale yet as we haven’t done any serious optimisation work yet.
Repository: matrix-org/dendrite

Issue #2890: UISIs after upgrading dendrite
Created: 2022-11-23T10:36:27Z
Background information


Dendrite version or git SHA: 0.10.7+31f56ac3
Monolith or Polylith?: Monolith
SQLite3 or Postgres?: Postgres
Running in Docker?: No
go version: go version go1.19.3 windows/amd64
Client used (if applicable): Element Desktop (both sender/receiver)

Description

What is the problem: UISIs on previously fine group chat room.
Who is affected: Single user
How is this bug manifesting: Unable to decrypt: The sender's device has not sent us the keys for this message.
When did this first appear: After upgrading from 7ad87eace3b88b3aaa88dc8a0acec9b64ffcc52c

Steps to reproduce

Filed on behalf of @emanuele.aliberti:mtka.eu - who sent a screenshot which indicates that:

Previously decrypted messages remain decrypted.
New messages after the upgrade are UISIs.
Neither Element client was restarted in the interim.

The room key must have changed, but why this wasn't shared post upgrade I don't know. It could be that the room key happened to change during the downtime between upgrades, but this should have been retried.
After restarting both Element instances, new messages are decrypted, but previous UISIs remain as UISIs. This may point to an Element Desktop bug.

Duplicate issue #2436: Users from matrix.org see Unable to decrypt
Created: 2022-05-09T10:16:57Z
Background information

Dendrite version or git SHA: 08.3rc1
Monolith or Polylith?: monolith
SQLite3 or Postgres?: Postgres
Running in Docker?: No
go version: go1.18.1 windows/amd64
Client used (if applicable): Element Desktop

Description

What is the problem: users from matrix.org can't read a message from a dendrite user
Who is affected: users registered at matrix.org
How is this bug manifesting: Element writes Unable to decrypt: The sender's device has not sent us the keys for this message.
When did this first appear: randomly

Steps to reproduce
Sent via DM

Closing comment (2022-12-07T16:56:52Z): With a recent change /members, is this still happening? Is it better/worse?

Not recently (Dendrite 0.10.8+ba2ffb7d), but it may be related to #2890 .
Repository: matrix-org/dendrite

Issue #2704: Cannot find other User since v0.9.2 with pinecone
Created: 2022-09-08T08:22:32Z
Background information


Dendrite version or git SHA: V0.9.2
Monolith or Polylith?: Monolith
SQLite3 or Postgres?: SQLite3
Running in Docker?: No
go version: 1.19
Client used (if applicable): Element-Android.

Description

What is the problem: Cannot find other users
Who is affected: Client using dendrite with pinecone.
How is this bug manifesting: Cannot find other users.
When did this first appear: After upgrading v0.9.2


Steps to reproduce


Prepare 2 dendrite servers are connected to each other with pinecone under a sub-net
Check dendrite servers connection.
Prepare 2 android element clients and log into each dendrite server.
Try to send a DM by searching and add the other user.
Cannot find other user.

Duplicate issue #2895: Cannot find a user to include in a chat room
Created: 2022-11-30T08:24:54Z
Background information


Dendrite version or git SHA: 0.10.8
Monolith or Polylith?: Monolith
SQLite3 or Postgres?: SQLite3
Running in Docker?: No
go version: 1.19
Client used (if applicable): Element-desktop

Description

What is the problem: Cannot search of any user to include into chat room.
Who is affected: Everybody to use dendrite with pinecone.
How is this bug manifesting: Erros in the log saying "WARN[2022-11-30T07:42:05.764548000Z] bulkFetchUserDirectoriesFromServers: failed to query hs  context=missing error="Get "http://c613f8f078d7bc8d0a540fbf6fd02b6475babe33012189262b178837522b5e00/_matrix/p2p/profiles\": loopback dial" hs=c613f8f078d7bc8d0a540fbf6fd02b6475babe33012189262b178837522b5e00"
When did this first appear: It happens since dendrite v.0.9.2


Steps to reproduce


Prepare 2 computers which are in the same subnetwork.
Run dendrite servers which uses pine-cone for P2P chat in each computer
Check each dendrite server found out the other dendrite server
Create a user account with element-desktop in each computer(Ex. User1 and User2)
One user account(Ex. User1) create a chat room which is public
The user account(Ex. User1) searches of the other user account(Ex. User2) in order to invite him into the chat room.
The room creator(Ex. User1) cannot search of anyone(Ex. User2).


The user account should be able to search of other user account but that is not possible since dendrite 0.9.2 with pine-cone
I attached the generated log from dendrite when I type a letter for other user account after creating a public chat room.

Closing comment (2022-12-06T15:45:53Z): Dupe #2704
Repository: matrix-org/dendrite

Issue #1806: Send 202 Accepted on /profile requests
Created: 2021-03-24T22:31:55Z
Background information

Dendrite version or git SHA: latest master
Monolith or Polylith?: monolith
SQLite3 or Postgres?: postgres
Running in Docker?: no
go version: go1.16


Description
Updating display name or avatar in a busy Dendrite server with many rooms brings Dendrite to a stop. Dendrite hangs and stops logging when it reaches SendEvents on lines #L172 and L289 in clientapi/routing/profile.go.
Steps to reproduce

Update user avatar or display name
Dendrite halts and needs to be killed/restarted

I can't tell exactly what's happening since Hummingbard's Dendrite logs are very noisy. Commenting out the SendEvents functions sets the user avatar and display name properly. I am guessing that SendEvents updates the updated profile data in room memberships. I suspect it may have something to do with rooms that no longer exist, either locally or federated.
I cannot reproduce this locally with a fresh Dendrite. Most likely there is a state resolution conflict somewhere, as @neilalexander pointed out to me a while back.

Duplicate issue #1821: PFPs Have Difficulty Propogating
Created: 2021-04-08T16:19:39Z
Background information

Dendrite version or git SHA: b769d5a
Monolith or Polylith?: mono
SQLite3 or Postgres?: postgres
Running in Docker?: no
go version: 1.16.3


Description
Changing profile pictures and clicking save in Element either takes minutes or never at all to sync to other users
Steps to reproduce

Run dendrite for an hour or so
Federation is on
Ask users to update their pfps

This usually resolves by killing and restarting dendrite, then the problem returns.

Closing comment (2021-07-09T11:21:26Z): Seems like a dupe of #1806 - closing this.
Repository: matrix-org/dendrite

Issue #1676: Monolithic server client API becomes unresponsive until restarted
Created: 2021-01-03T18:13:08Z
Background information

Dendrite version or git SHA: bca2790 (post-dev v0.3.4 for #1672)
Monolith or Polylith?: Monolith
SQLite3 or Postgres?: Postgres
Running in Docker?: Docker
go version: official images

Description
My Dendrite server has become unresponsive two times in a 24 hour period. This is noticed by Element web (app.element.io) saying the server is offline. The console logs show sync endpoints timing out.
Restarting the docker container has caused the issue to resolve on both times.
Nothing interesting found in logs that I could spot, errors mainly related to fetching of remote auth events. Will submit a log file privately that covers the second time with an issue.
Dendrite is v0.3.4 post dev on hash bca2790 (which is a part of #1672). MSC2836 is enabled in settings.
While the unresponsiveness continues, the logs do show activity in the federation API's.

Duplicate issue #1818: Server is tremendously slow
Created: 2021-04-07T05:30:10Z
Background information

Dendrite version or git SHA:
0.3.11-1
Monolith or Polylith?:
Monolith
SQLite3 or Postgres?:
Postgres
Running in Docker?:
go version:
2:1.16.3-1


Description

Steps to reproduce

Start the server
Send some messages
Observe crashing and tremendous latency, while not many resources are being used.


free -h
               total        used        free      shared  buff/cache   available
Mem:           3.8Gi       519Mi       2.4Gi       147Mi       1.0Gi       3.0Gi
Swap:          4.4Gi          0B       4.4Gi

As you can see, not many resources are being used. (cpu only peaks at 40%), but there's a tremendous delay to messages sent.
top - 22:50:34 up  7:54,  1 user,  load average: 0.29, 0.38, 0.47
Tasks: 127 total,   1 running, 126 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.8 us,  0.3 sy,  0.0 ni, 98.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3929.5 total,   2482.8 free,    370.2 used,   1076.5 buff/cache
MiB Swap:   4512.0 total,   4512.0 free,      0.0 used.   3191.3 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
    279 dendrite  20   0 3199080 266896  21196 S   1.0   6.6   9:46.42 dendrite
    199 root      20   0  386920 262216 260652 S   0.3   6.5   0:19.82 systemd-journal
  21952 postgres  20   0  208708  17992  15496 S   0.3   0.4   0:00.05 postgres
      1 root      20   0   23824  10260   7928 S   0.0   0.3   0:01.86 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.00 kthreadd


  
    
    

    untitled.mp4

Closing comment (2021-04-08T10:29:04Z): There doesn't seem to be anything actionable here. It may be a dupe of #1676 but it's hard to tell.

Randomly, my server has deleted all messages since Sunday

The server won't delete anything - there's physically no code to do this. Redacted messages will redact the event content (but the event itself has to stay for DAG purposes).
Repository: matrix-org/matrix-spec-proposals

Issue #1033: Doc @room notifications
Created: 2017-10-23T15:45:09Z
Documentation: https://docs.google.com/document/d/1qRdlg94cr9YXxPCwhW4HgI2oDrqQOUKX5HptZFBGf6o/edit#
ie. the sender_notification_permission pushrule condition.

Duplicate issue #1216: @room notification proposal
Created: 2018-05-10T16:33:45Z
Documentation: https://docs.google.com/document/d/1qRdlg94cr9YXxPCwhW4HgI2oDrqQOUKX5HptZFBGf6o/edit
Author: @dbkr
Date: 23/10/2017
PRs: #1176

Closing comment (2018-05-31T14:52:39Z): dup #1033
Repository: matrix-org/matrix-spec-proposals

Issue #2220: 3pid management in the client-server is inconsistent with itself
Created: 2019-08-06T18:47:18Z
threepidCreds vs threepid_creds vs three_pid_creds, non-RESTful endpoints, general duplication that isn't entirely needed

Duplicate issue #3157: Figure out the answer to the threepidCreds vs threepid_creds debate
Created: 2021-04-29T17:54:47Z
There are several arguments as to whether it is a spec issue or a synapse issue. Needs discussion.
element-hq/element-web#10312
matrix-org/matrix-react-sdk#3211
matrix-org/synapse#5665
#2220

Closing comment (2021-04-29T18:19:44Z): Duplicate of #2220 and #2189
Repository: matrix-org/matrix-spec-proposals

Issue #492: v2 - Relates to (SPEC-98)
Created: 2015-01-21T13:38:50Z
bq. Should be able to specify more relationship info other than just the event type. Forcing that m.room.message A "relates_to" another m.room.message B means that A is a threaded conversation reply to B is needlessly restrictive. What if A and B relate to each other by some other metric (e.g. they are part of a group rather than a thread? or we distinguish mail-style threading from multithreaded-IM threading for the same set of messages? etc)? E.g.
"relates_to" : [["in_reply_to", "$event_id1"], ["another_type_of_relation", "$event_id2"]]

(Imported from https://matrix.org/jira/browse/SPEC-98)
(Reported by @kegsay)

Duplicate issue #616: Support context/threads for messages (SPEC-326)
Created: 2016-01-16T11:35:02Z
Extend https://github.com/matrix-org/matrix-doc/blob/master/event-schemas/schema/m.room.message properties with an optional "context" property, consisting of a title and URI.
Reasoning: Most conversations happen in a specific context or are part of a thread. Some chat apps support this explicitly (Zulip, Flowdock), some have issues open for this (RocketChat/Rocket.Chat#1112). From my experience of using Slack extensively, even if there is no support for context in the app, especially with integrations you end up inventing your own way of indicating context (typically as a link) in the body of each message, which only adds to the noise. Matrix should have a standard support for context as early as possible so the context gets federated properly.
(Imported from https://matrix.org/jira/browse/SPEC-326)
(Reported by Somantiq)

Closing comment (2016-11-07T16:06:31Z): dup #492
Repository: matrix-org/matrix-spec-proposals

Issue #3796: Auth for content repo (and enforcing GDPR erasure)
Created: 2016-08-20T18:38:55Z
Formerly MSC701.
Documentation: https://docs.google.com/document/d/1ERHpmthZyspnZtE3tQzxKTkcxar6JANeyNXgz2_djhA/edit#
Author: @ara4n
Date: 2018-06-04
The media repository is currently unauthed; anybody can access posted images, avatars, etc, if they know the URI.
Submitted by @​matthew:matrix.org
(Imported from https://matrix.org/jira/browse/SPEC-445)

Duplicate issue #1025: Content uploaded to the content repository should require authentication
Created: 2017-10-16T00:59:35Z
While writing my own client I realized this was an issue:
https://github.com/matrix-org/synapse/issues/2150
Is there any reason we should not require authentication?

Closing comment (2017-10-16T08:29:01Z): dup #3796
Repository: matrix-org/matrix-spec-proposals

Issue #2189: Docs list wrong key `threepidCreds` for email/id based user auth
Created: 2019-07-23T18:05:53Z
When using the docs/spec to build out a client, I ran into an issue when trying to auth using email from id server.
According to docs, the auth looks like this:
https://github.com/matrix-org/matrix-doc/blob/ad5d46d3317bd3d016ed7bf1e3fb5ce1f8d7fef1/specification/client_server_api.rst#L797
But according to synapse, it should be named this:
https://github.com/matrix-org/synapse/blob/54283f3ed49ce40059e9f0746f2ded08ce3a5b9e/synapse/handlers/auth.py#L454
So the two differences are the key name and whether it should contain an object or array.

Duplicate issue #2207: threepidCreds should be called threepid_creds
Created: 2019-07-31T16:09:02Z
There is a discrepancy between synapse and the spec in trying to auth using email from id server.
This issue was cribbed heavily from matrix-org/synapse#5748
"According to docs, the auth looks like this:
https://github.com/matrix-org/matrix-doc/blob/ad5d46d3317bd3d016ed7bf1e3fb5ce1f8d7fef1/specification/client_server_api.rst#L797
But according to synapse, it should be named this:
https://github.com/matrix-org/synapse/blob/54283f3ed49ce40059e9f0746f2ded08ce3a5b9e/synapse/handlers/auth.py#L454
So the two differences are the key name and whether it should contain an object or array."
Given that this is out in the wild and that the spec tends to snake_case I propose that this should be fixed in the spec rather than implementation even though technically this is a bug in Synapse.

Closing comment (2019-07-31T16:25:55Z): Duplicate of #2189
Repository: matrix-org/matrix-spec-proposals

Issue #765: Start publishing a list of public homeservers
Created: 2016-12-21T23:17:54Z
matrix.org (duh)
we.ho.st
disroot.org

If you want to advertise public HS hosting, please add a comment here and we'll get you added to an official list somewhere on matrix.org!

Duplicate issue #795: Link to https://www.hello-matrix.net/public_servers.php or otherwise maintain a list of public servers
Created: 2017-02-01T21:23:40Z

Closing comment (2017-02-09T19:02:26Z): dup of #765
Repository: matrix-org/matrix-spec-proposals

Issue #501: End-to-End Crypto (SPEC-162)
Created: 2014-09-23T00:38:44Z
update April 2017: we now have more-or-less operational E2E encryption in matrix. The work remaining on this issue is to specify it.

End-to-end encryption in Matrix is currently a work-in-progress. A draft of the specification is being prepared on the drafts/e2e branch of matrix-doc. The purpose of this issue is to provide an overview of the work that is outstanding.
An audit of the Olm library, and Olm's use in matrix
Matrix's cryptographic support has been designed according to our understanding of the latest security research and algorithms. However, none of the matrix.org team are trained security experts.
We would welcome an independent audit of our designs and implementations, to highlight any potential vulnerabilities.
(update: NCC group carried out a review on the olm and megolm protocols, and the libolm implementations in November 2016: https://www.nccgroup.trust/us/our-research/matrix-olm-cryptographic-review/)
New device handling (SPEC-271)
We need better support for adding new devices to conversations.
Protocol support for out-of-room messages (#443), and implementations in homeservers and clients
Once all recipients have received encrypted data, it is useless (even to the original recipients), because nobody can decrypt it. There is no point keeping such history in a DAG forever. Good security practice dictates that we destroy the ciphertext even if we are confident in the security of the encryption.
Group chat support (#589)
m.room.encrypted events are a valid proof-of-concept to show that we can transmit encrypted data between clients; however this does not scale beyond a few users, and does not give a good user experience. #589 considers how this can be improved.
Encryption controls on rooms (#590)
Not every room will need or want the same level of security. We need to define some controls for room administrators to use.
Support for encryption of attachments (#461)
This might become obvious after #589, but we should remember to make sure that uploaded files can be encrypted as well as messages.
(Imported from https://matrix.org/jira/browse/SPEC-162)
(Reported by @ara4n)

Duplicate issue #1183: Document key-share requests
Created: 2018-04-30T09:38:48Z
Documentation: https://docs.google.com/document/d/1m4gQkcnJkxNuBmb5NoFCIadIY-DyqqNAS3lloE73BlQ
PRs: #1465
We should document the events used by riot to do keyshare requests

Closing comment (2018-05-31T14:41:06Z): related to #501
Repository: matrix-org/matrix-spec-proposals

Issue #1430: The spec'ed algorithm for choosing of auth events is subtly wrong
Created: 2018-07-19T10:45:51Z
The actual set picked for an events is: https://github.com/matrix-org/synapse/blob/2c33b55738d54186d7655972a6707336b2168534/synapse/event_auth.py#L674-L706

Duplicate issue #1495: The algorithm for picking auth_events is incomplete
Created: 2018-08-08T12:31:24Z
The full algorithm in synapse is:
https://github.com/matrix-org/synapse/blob/33b60c01b5e60dc38b02b6f0fd018be2d2d07cf7/synapse/api/auth.py#L555-L619

Closing comment (2018-08-08T13:40:42Z): Duplicate of #1430
Repository: matrix-org/matrix-spec-proposals

Issue #1898: Pagination section refers to non-existent prev_batch token when back-paginating
Created: 2019-02-21T14:17:48Z
https://spec.matrix.org/unstable/client-server-api/#pagination says 'In this scenario, the prev_batch token would be excluded from the response', but /messages doesn't have a prev_batch token. Presumably it means end.

Duplicate issue #1899: Pagination section refers to non-existent prev_batch token when back-paginating
Created: 2019-02-21T14:17:48Z
https://matrix.org/docs/spec/client_server/r0.4.0.html#pagination says 'In this scenario, the prev_batch token would be excluded from the response', but /messages doesn't have a prev_batch token. Presumably it means end.

Closing comment (2019-02-21T14:18:35Z): dup #1898
Repository: matrix-org/synapse

Issue #9944: Identify, implement, and document a way to extend our Docker images
Created: 2021-05-06T15:36:36Z
In the process of splitting the Account Validity feature into its own module we've run up against a roadblock: we don't have a well-defined path for people to add extension modules to our Docker images.
We need to survey prior art, pick a solution, and then implement and document it.

Duplicate issue #14036: Load custom module with a Docker image
Created: 2022-10-04T06:12:45Z
Is it possible to load a custom module from an absolute location?
Initially I installed Synapse with the apt repository and placed my custom python module in /opt/venvs/matrix-synapse/lib/python3.8/site-packages. I was able to load the module with:
modules:
  - module: custom_event_rules.MyRules

Recently I used the Docker image to install Synapse on a different server. Unfortunatly I was not able to manage to load a custom module with the Docker image. I placed the file in the Docker volume folder and modifed the homeserver.yaml like this:
modules:
  - module: /data/custom_event_rules.MyRules

The documentation states:

Each module is defined by a path to a Python class as well as a configuration. This information for a given module should be available in the module's own documentation.

https://matrix-org.github.io/synapse/latest/modules/index.html
Maybe I am missunderstanding the documentation.
Kind regards!

Closing comment (2022-10-04T11:11:35Z): I think this is pretty much a duplicate of #9944.
Repository: matrix-org/synapse

Issue #5665: synapse requires unspecified `user` for m.login.password UI auth
Created: 2019-07-11T11:10:47Z
The spec says that the client should submit a dict including an identifier object. In practice, synapse requires you to instead to just submit a user field, so the dict looks like:
{
  "type": "m.login.password",
  "user": "<user_id or user localpart>",
  "password": "<password>",
  "session": "<session ID>"
}

Duplicate issue #8836: synapse requires `identifier` in `/login` requests, even for auth types which do not require it
Created: 2020-11-27T15:06:34Z
suppose I create a custom login type com.example.login_token (NB a login type as opposed to a UIA authentication type)
and say that the login submission should look like this:
{
  "type": "com.example.login_token",
  "token": "<login token>"
}

I should be able to implement this via a custom password provider; however, synapse expects to see an identifier in the submission, and will reject the login before passing it to the password provider.

Closing comment (2020-11-27T15:07:02Z): This is related to #5665: basically synapse uses "is this a login or a UIA?" to decide whether to look for an identifier, whereas it should be looking at the login/auth type.
Repository: matrix-org/synapse

Issue #1491: Send SNI indication to support vhosts over federation (SYN-620)
Created: 2016-02-06T12:24:25Z
TwoOne problems:

Federation doesn't send an SNI indication (because twisted), so for vhosted servers we tend to end up on the default.
We send the server_name in the Host header, rather than what the SRV tells us to use. (We think the current behaviour is correct, as per #2525).

(Imported from https://matrix.org/jira/browse/SYN-620)

Duplicate issue #1511: Outbound HTTPS requests should use SNI (SYN-648)
Created: 2016-03-11T10:31:34Z
(Imported from https://matrix.org/jira/browse/SYN-648)
(Reported by @erikjohnston)

Closing comment (2016-11-15T07:27:51Z): Dup #1491
Repository: matrix-org/synapse

Issue #7083: Rooms with unsupported versions are shown as blank rooms
Created: 2020-03-16T11:53:05Z
In the last ~4-5 days
!VXChyxVNCBsWeSGcaN:sw1v.org
!eKTrlepAvBEhUIyoQV:jki.re
!bNAPsppHlSHCDvMRhh:abolivier.bzh

Duplicate issue #7209: Initial sync included rooms with no information that I'm apparently not in (legacy/unsupported room versions)
Created: 2020-04-02T18:24:35Z
Trying to get members of the room results in name: "M_FORBIDDEN", message: "User @travis:t2l.io not in room !oeCrnyfPhvZiruUJLn:sw1v.org, and room previews are disabled". This is a test room which I should be in.
The room has no name, and I cannot backfill it. 3 of my rooms appear to be impacted by this.
!oeCrnyfPhvZiruUJLn:sw1v.org has the version eventid-noslash-test.
!VXChyxVNCBsWeSGcaN:sw1v.org is state-v2-test (old internal room).
!bNAPsppHlSHCDvMRhh:abolivier.bzh is another test room with a version of org.matrix.msc2260
The theme appears to be that Synapse doesn't recognize the room versions anymore, not that the rooms have reset or been left. Synapse should probably exclude these rooms, or somehow support them enough to refuse new messages?

Closing comment (2020-04-02T18:42:17Z): This sounds like a duplicate of #7083, but with a slightly different failure mode.
Repository: matrix-org/synapse

Issue #1545: Why does room creation take so long? (5s or so) (SYN-692)
Created: 2016-05-13T16:24:30Z
Submitted by @​matthew:matrix.org
(Imported from https://matrix.org/jira/browse/SYN-692)

Duplicate issue #6068: room creation can be surprisingly slow
Created: 2019-09-19T18:39:16Z
... even when no remote users are involved

Closing comment (2021-07-08T00:40:45Z): Related to #1545
Repository: matrix-org/synapse

Issue #1467: We need a config option to limit the public room directory to registered users only (SYN-584)
Created: 2016-01-07T23:03:01Z
Submitted by @​matthew:matrix.org
Use case is to stop sensitive publicroom data leaking from an otherwise federated HS. This is relevant to our own 'private' HS!
(Imported from https://matrix.org/jira/browse/SYN-584)

Duplicate issue #4186: [security] Exposed rooms list
Created: 2018-11-15T07:11:48Z
When guests and registrations on server are closed
the server is exposed to a https://matrix.org/_matrix/client/r0/publicRooms to show the full list of rooms, with ids , descriptions, avatar and any one also can add a server to their rooms directory config with out any notice.
when is room is set to:

Publish this room to the public in domain.com room directory?
Anyone who knows the room's link, apart from guests and Anyone who knows the room's link, including guests
option is set to not list on matrix servers
even of option is set "Anyone who knows the room's link, apart from guests"

so anyone can see a "room_id" and generate a link https://matrix.to/#/!XXXXXXXX:domain.com

it can serve to crawl a private information and a bots attacks
i was able to join a room with out a registration when the room is set to "Anyone who knows the room's link, apart from guests"
Removing option "Publish this room to the public in domain.com room directory?" The room is still visible in a community category.
what option "Block users on other matrix homeservers from joining this room" really for?

The thing that disturbs me its possibility to view rooms when the SERVER is PRIVATE. Really private. I still want to join another public networks, but keep mine private (rooms , not private messages) I want to be able publish room in my rooms directory but not to the world.  For example every person can view all the rooms from the web or rooms list. How to disable this? I think there is something to think about...
thanks

Closing comment (2018-11-15T09:40:25Z): sounds like a dup of #1467/#2419
Repository: mattermost/mattermost

Issue #11816: Add option for custom DB root/user password when using the mysql-operator for Mattermost operator
Created: 2019-08-06T15:15:00Z
If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please  join our "Developers" community channel.
New contributors please see our Developer's Guide.

Notes: Jira ticket
The Mattermost Operator is a Kubernetes operator that manages the lifecycle of a Mattermost installation.
Currently, the root/user password for the database are randomly generated. However, some users might want to define a custom password.
For this ticket implement adding a field to the ClusterInstallation custom resource for the user to set a custom password for the root/user for the database.
Note that if the an external database is being used, this custom password field should be ignored.

Duplicate issue #12011: Add option for custom DB root/user password when using the mysql-operator for Mattermost operator
Created: 2019-08-30T15:02:54Z
The (https://github.com/mattermost/mattermost-operator) is a Kubernetes operator that manages the lifecycle of a Mattermost installation.
Currently, the root/user password for the database are randomly generated. However, some users might want to define a custom password.
For this ticket implement adding a field to the ClusterInstallation custom resource for the user to set a custom password for the root/user for the database.
Note that if the an external database is being used, this custom password field should be ignored.

If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please  join our "Developers" community channel.
New contributors please see our Developer's Guide.
JIRA: https://mattermost.atlassian.net/browse/MM-17530

Closing comment (2019-10-05T06:42:54Z): Good catch @Sheshagiri. Closing as duplicate of #11816