Cool! And thanks again, very impressed with the product otherwise 

Thanks for taking a look, @eskimor (and thanks for the lightning-speed response!)

So yes, both the video and the audio seem to be streaming when this occurs. (I should note though, that my confirmation here is based on the visual audio level indicator. I’ve now confirmed that the audio does indeed still stream when this occurs, so it’s not just the visual indicator.)

I came up with the following steps to reproduce the issue (with fixed phone and laptop roles just for simplicity):

1. Start baby (on the phone)
2. Start parent (on the laptop) and connect to baby (so far so good)
3. Disconnect phone (baby) from network to cause the parent (the laptop) to show the alarm
4. Reconnect phone (baby) to network
5. The stream (on parent, laptop) does not come back, alarm remains
6. From parent (laptop), select Home, respond ”OK” to ”Are you sure”
7. Still on parent (laptop), reconnect to baby

After this, the stream (with audio) is playing (on the laptop) underneath the red warning overlay. The alarm sound has been playing non-stop since step 3.

I’m unsure if the stream is supposed to come back to life by itself at step 5 or not, but either way, with my current setup it doesn’t (that is, it remains frozen). That’s the reason for steps 6-7: to get the stream showing again.

I’m testing Gonimo in anticipation of real-word deployment, and so far everything else seems to work as expected, but for some reason I can’t get the ”connection lost” alert to go away once it starts, even after the connection is re-established (as indicated by the video stream resuming). The red overlay (with ”connection lost!”) keeps flashing over the video stream, and the alarm sound keeps ringing no matter what I do in-tab. The only workaround I’ve come up with is refreshing the tab (F5).

In case this is environment-related, my laptop has Ubuntu 20.04 with Chrome 80.0.3987.116, my Android phone has Chrome 80.0.3987.119, and I’ve tested both ways (both as either the baby or the parent). I haven’t tested the Android app yet to see if it’s any different.

I think I’ve (accidentally) found a reliable way to reproduce this:

1. Have a card with a checklist
2. From the card’s hamburger menu, select More -> Delete, but don’t touch the (”Delete card?”) confirmation prompt!
3. With the card deletion confirmation prompt still visible, delete the checklist (choose Delete from the checklist title, then confirm the checklist deletion)
4. Now select Delete from the (still lingering) card deletion prompt

Boom! The card (and the board) is now undeletable.

@amyblais No subpath, just the plain domain.

Your service keeps asking me to verify my e-mail address over and over again. When I open the verification link from the email, the verification succeeds and the yellow notification goes away, but when I return to the site the next day, the notification has reappeared and I have to go through the whole process again. This has been going on for weeks if not months.

I found one Community Forum thread with the same issue, but the ”solution” there just tells the affected user to contact support. https://github.community/t5/How-to-use-Git-and-GitHub/Continual-repeated-requirement-to-verify-email-address-for-users/td-p/18085

Hi @amyblais, thanks for taking a look!

Here are the banner settings:

# grep -i banner config.json 
        "EnablePreviewModeBanner": true,
        "EnableBanner": false,
        "BannerText": "",
        "BannerColor": "#f2a93b",
        "BannerTextColor": "#333333",
        "AllowBannerDismissal": true

I should also mention that I’ve previously enabled Developer Mode ("EnableDeveloper": true), but I’m not sure it’s related, since the notification in this issue has the normal blue background, not a purple one.

The issue reappeared today for the other affected user, then kept disappearing and reappearing under testing, but we were unable to pin down any specific reason. Their browser console (Firefox) only has this:

websocket connecting to wss://[redacted]/api/v4/websocket websocket_client.jsx:35:20

and the server log meanwhile only has this line repeated:

mlog/log.go:174	{"name":"TypeError","message":"NetworkError when attempting to fetch resource.","stack":""}	{"path": "/api/v4/logs", "request_id": "g8wwo8yu57djmkipjxjxn7hy3y", "ip_addr": "[redacted]", "user_id": "[redacted]", "method": "POST", "err_where": "client", "http_code": 0, "err_details": ""}

(where user_id is the one for the affected user.)

Summary

Selecting the ”Refresh the app now” link from update notification doesn’t make the notification go away.

Steps to reproduce

Have MM server updated to latest release. Open an existing session of the web app in Firefox. See the refresh prompt, select ”Refresh the app now”.

Expected behavior

Web page is refreshed, the notification goes away.

Observed behavior (that appears unintentional)

Web page is refreshed, but the update notification is still there, still prompting to refresh.

Verbose version

With some of the most recent updates (perhaps 5.16 and newer), the ”Refresh the app now” link in the update notification (”A new version of Mattermost is available”) on the web app did not make that notification go away for myself and another user. The link did cause a refresh of the page content, but the notification persisted. Meanwhile the version being reported by ”About Mattermost” was the correct (5.16.2).

Ctrl+shift+r or other hard refresh attempts did not have an effect, but logging out and then back in to the site finally did make the notification go away.

We’re both Firefox users, and due to the nature of the issue it was difficult to tell if this was browser-specific, but a fresh login using Chrome (while the previous session in Firefox still showed the notification) did not bring up the notification in the new session.

The issue, though irritatingly persistent while it lasted, was still relatively ephemeral, and now that it’s gone, I wouldn’t know how to reproduce it before the next server update. That said, I’ll happily provide more details if I can.

I’m using yle-dl 20190614 with GNU Wget 1.19.4 in Ubuntu 18.04.

When trying to download this (and so far this is the only example I’ve come across): https://areena.yle.fi/1-50192791

Wget fails like this:

Resolving ylekaod-a.akamaihd.net (ylekaod-a.akamaihd.net)... 62.183.170.32, 62.183.170.35
Connecting to ylekaod-a.akamaihd.net (ylekaod-a.akamaihd.net)|62.183.170.32|:443... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

It tries a few more times, then gives up. I’m attaching a --verbose log (with LC_ALL=C).

Workaround

I took the wget command from –verbose output and added UA spoofing with -U 'Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.27 Safari/537.17', and with the resulting command I was able to download the file.

When a checklist item is in edit mode (through the specific steps below), selecting another item for editing does not take the previous item out of edit mode, and upon selecting a third item (or pressing enter) causes the second item to be overwritten by whatever content is in the first selected item.

Server Setup Information:

• Wekan version: 2.74
• Operating System: Ubuntu 16.04
• Deployment Method: snap (stable)
• Http frontend if any: Apache 2.4
• ROOT_URL environment variable: https://my-domain.com/kan

Problem description:

Steps to reproduce

1. Have a card with a checklist with 4 (or more) items with contents A, B, C, D (and so on):
2. Select item A with LBM
3. Select item B with LBM
4. Select item C with LBM
5. Select item D with LBM

What happens
At step 4, when C opens for editing, B remains in edit mode. At step 5, contents of C are overwritten by contents of B (that is, ”C” becomes a ”B”).

What I expect to happen
At step 4, for B to leave edit mode, and at step 5, the contents of C to remain as they are.

Other notes

• Reproducible in both Chrome and Firefox.
• Curiously, this does not seem to affect the firstly selected item: in step 3 above, A leaves edit mode correctly and thus B doesn’t get overwritten by the contents of item A in step 4.
• At step 5, instead of selecting item D, pressing enter has the same effect.

Browser console output
empty

snap logs wekan.wekan
nothing related