-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only sync and set active room after user has joined room. #1536
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This breaks the UI in the public share authentication page (the video verification).
Also, it may cause a race condition in the Files app, although I am not sure about that; the acceptance tests fail there too, but it could be a false positive given that the previous test to the failed one shows several timeouts. However, I tested it manually and I had a similar (although not identical) problem once, but it could have been a cache issue too. So... I am not sure :-)
Signed-off-by: Joachim Bauch <bauch@struktur.de>
The event is never listened to, so there is no need to stop listening to it. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The room collection was never used, so it is not needed. Moreover, although it was initialized it was never fetched, as it was never set as the room collection to be synchronized by the signaling object. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The "active" event is no longer listened to since the room collection was removed, so there is no need to trigger it. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This is more a formal fix, as for guests a "joinRoom" event would not be triggered with a room that is not the current room, but if it was trying to set the name would fail. Besides that it accomodates further changes in the "joinRoom" handler, as it will be typically used when the current room is joined. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
"syncAndSetActiveRoom" in Embedded only synchronized the rooms after joining a room, but that is already done in PublicShareAuth and the Files plugin (followed by some specific code for each case once the synchronization is done). Due to this calling "syncAndSetActiveRoom" after joining a room is only needed in Application. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
After checking again the issue I had with the Files app it seems to be unrelated to this pull request. Regarding the breaking of the public share authentication page the reason is that, when this pull request was created, Also note that after rebasing this pull request on current While checking all this I found that calling As my approval now becomes a self-approval it would be good if someone else could check all this before merging ;-) Besides the test described below, which triggers the original bug, it would be good to check that the Files app and the public share authentication page still work as expected ;-) How to test-Replace the call to *Adding a sleep to Result with this pull requestThe room is loaded. Result without this pull requestThe room is not loaded, although it appears in the navigation bar; the problem is in the main view. |
/backport to stable16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and works 👍
backport to stable16 in #1914 |
commit ebb87a602d43ad64891c7a8181f2da7ebd15e039 Author: Nextcloud bot <bot@nextcloud.com> Date: Wed Jun 26 02:43:27 2019 +0000 Ignore .idea/ folder. commit b1b08610b8d4884d7fbd31dead2576db998be4fa Merge: ba964ad3 3d499857 Author: Ivan Sein <ivan@nextcloud.com> Date: Tue Jun 18 14:21:01 2019 +0200 Merge pull request #1536 from nextcloud/sync-after-join Only sync and set active room after user has joined room. commit ba964ad36c10b824668f0336ed81abb5f6416787 Merge: 66fab6fa 674fad90 Author: Ivan Sein <ivan@nextcloud.com> Date: Tue Jun 18 12:29:13 2019 +0200 Merge pull request #1912 from nextcloud/dependabot/npm_and_yarn/vue/css-loader-3.0.0 Bump css-loader from 2.1.1 to 3.0.0 in /vue commit 674fad909b8266ec4fee33a918f5f3cde24a3356 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Tue Jun 18 10:21:21 2019 +0000 Bump css-loader from 2.1.1 to 3.0.0 in /vue Bumps [css-loader](https://github.com/webpack-contrib/css-loader) from 2.1.1 to 3.0.0. - [Release notes](https://github.com/webpack-contrib/css-loader/releases) - [Changelog](https://github.com/webpack-contrib/css-loader/blob/master/CHANGELOG.md) - [Commits](https://github.com/webpack-contrib/css-loader/compare/v2.1.1...v3.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> commit 66fab6fa94b59a10fa50fef83d7b14443272a1de Merge: 60bf1026 967b9a1e Author: Ivan Sein <ivan@nextcloud.com> Date: Tue Jun 18 12:23:06 2019 +0200 Merge pull request #1913 from nextcloud/dependabot/npm_and_yarn/vue/webpack-cli-3.3.4 Bump webpack-cli from 3.3.2 to 3.3.4 in /vue commit 967b9a1e6706912f3f8e8df62a9e389c594fa747 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Tue Jun 18 10:12:41 2019 +0000 Bump webpack-cli from 3.3.2 to 3.3.4 in /vue Bumps [webpack-cli](https://github.com/webpack/webpack-cli) from 3.3.2 to 3.3.4. - [Release notes](https://github.com/webpack/webpack-cli/releases) - [Changelog](https://github.com/webpack/webpack-cli/blob/master/CHANGELOG.md) - [Commits](https://github.com/webpack/webpack-cli/compare/v3.3.2...v3.3.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> commit 60bf10261899b64a0923f6c1e1c71d6108a491d5 Merge: f0b68b31 de6d2217 Author: Ivan Sein <ivan@nextcloud.com> Date: Tue Jun 18 12:10:45 2019 +0200 Merge pull request #1911 from nextcloud/dependabot/npm_and_yarn/vue/webpack-4.34.0 Bump webpack from 4.31.0 to 4.34.0 in /vue commit de6d2217a49f514c527d48da6857b67f749e8b0c Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Mon Jun 17 16:40:38 2019 +0000 Bump webpack from 4.31.0 to 4.34.0 in /vue Bumps [webpack](https://github.com/webpack/webpack) from 4.31.0 to 4.34.0. - [Release notes](https://github.com/webpack/webpack/releases) - [Commits](https://github.com/webpack/webpack/compare/v4.31.0...v4.34.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> commit f0b68b3192495450f4804f3801b205c6ab0bf7f0 Merge: b1642e14 da0739c4 Author: Ivan Sein <ivan@nextcloud.com> Date: Mon Jun 17 18:34:41 2019 +0200 Merge pull request #1894 from nextcloud/dependabot/npm_and_yarn/vue/file-loader-4.0.0 Bump file-loader from 3.0.1 to 4.0.0 in /vue commit b1642e147fe685f141c1159fa033f9bd2c7031a6 Merge: d88bacba c043b2a9 Author: Ivan Sein <ivan@nextcloud.com> Date: Mon Jun 17 18:32:48 2019 +0200 Merge pull request #1855 from nextcloud/dependabot/npm_and_yarn/vue/@babel/core-7.4.5 Bump @babel/core from 7.4.4 to 7.4.5 in /vue commit d88bacba64d044e7491e5da2c311f8116fb0ffe4 Merge: 752a4064 781a866c Author: Ivan Sein <ivan@nextcloud.com> Date: Mon Jun 17 18:31:20 2019 +0200 Merge pull request #1853 from nextcloud/dependabot/npm_and_yarn/vue/@babel/preset-env-7.4.5 Bump @babel/preset-env from 7.4.4 to 7.4.5 in /vue commit 752a4064d5b5dd9d4ad0188fcf4f797dfced7208 Merge: f633ee70 e103b5d2 Author: Ivan Sein <ivan@nextcloud.com> Date: Mon Jun 17 18:30:36 2019 +0200 Merge pull request #1878 from nextcloud/dependabot/npm_and_yarn/vue/nextcloud-vue-0.11.4 Bump nextcloud-vue from 0.11.1 to 0.11.4 in /vue commit e103b5d2d6436afc90405f94dea979e758e94347 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Mon Jun 17 16:21:55 2019 +0000 Bump nextcloud-vue from 0.11.1 to 0.11.4 in /vue Bumps [nextcloud-vue](https://github.com/nextcloud/nextcloud-vue) from 0.11.1 to 0.11.4. - [Release notes](https://github.com/nextcloud/nextcloud-vue/releases) - [Commits](https://github.com/nextcloud/nextcloud-vue/compare/v0.11.1...v0.11.4) commit f633ee708cb5577e5e855dc01560df85018cfc58 Merge: 28db03b8 04eab25e Author: Ivan Sein <ivan@nextcloud.com> Date: Mon Jun 17 18:19:53 2019 +0200 Merge pull request #1854 from nextcloud/dependabot/npm_and_yarn/vue/nextcloud-vue-collections-0.5.2 Bump nextcloud-vue-collections from 0.4.0 to 0.5.2 in /vue commit 04eab25e67a4d2c82bd10dbc99c7318183db3439 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Thu Jun 6 11:57:09 2019 +0000 Bump nextcloud-vue-collections from 0.4.0 to 0.5.2 in /vue Bumps [nextcloud-vue-collections](https://github.com/juliushaertl/nextcloud-vue-collections) from 0.4.0 to 0.5.2. - [Release notes](https://github.com/juliushaertl/nextcloud-vue-collections/releases) - [Commits](https://github.com/juliushaertl/nextcloud-vue-collections/compare/v0.4.0...v0.5.2) commit 28db03b85559b60eb817e9ab4dda3768faeff8fb Author: Nextcloud bot <bot@nextcloud.com> Date: Sun Jun 16 02:43:16 2019 +0000 [tx-robot] updated from transifex commit 2b129d89b9b9b03d80608cbe3345ea992ae33add Author: Nextcloud bot <bot@nextcloud.com> Date: Sat Jun 15 02:41:47 2019 +0000 [tx-robot] updated from transifex commit 856057a77cef78d97320444c0eb45cc556eccf88 Author: Nextcloud bot <bot@nextcloud.com> Date: Thu Jun 13 02:34:52 2019 +0000 [tx-robot] updated from transifex commit 54226c531038eb357e467b20848fec850c8dcece Merge: 8c875c36 de2039ee Author: Ivan Sein <ivan@nextcloud.com> Date: Wed Jun 12 11:09:15 2019 +0200 Merge pull request #1899 from nextcloud/fix-message-dates-in-public-share-authentication-page Fix message dates in public share authentication page commit de2039ee5faa0519167488c838ad9159e4c99365 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Jun 11 18:04:32 2019 +0200 Fix message dates in public share authentication page The chat messages are expected to have the full width of its content row, except for some space used for the date. However, as chat messages are left padded that padding must be included too in the width; otherwise there could be no room for the date. This is only a problem in the public share authentication page, as apps use by default "box-sizing: border-box" in all its elements. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit da0739c472b489cf965aeb0fe9349bce7b37d264 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Sun Jun 9 01:13:26 2019 +0000 Bump file-loader from 3.0.1 to 4.0.0 in /vue Bumps [file-loader](https://github.com/webpack-contrib/file-loader) from 3.0.1 to 4.0.0. - [Release notes](https://github.com/webpack-contrib/file-loader/releases) - [Changelog](https://github.com/webpack-contrib/file-loader/blob/master/CHANGELOG.md) - [Commits](https://github.com/webpack-contrib/file-loader/compare/v3.0.1...v4.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> commit 8c875c36f988ee4cf1aff56cbd5be2f289fa4c6c Author: Nextcloud bot <bot@nextcloud.com> Date: Sat Jun 8 02:34:13 2019 +0000 [tx-robot] updated from transifex commit 3d499857cea2723168a7b593e3dc8c3817d73884 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Fri Jun 7 12:06:48 2019 +0200 Sync and set active room when joined only in Application "syncAndSetActiveRoom" in Embedded only synchronized the rooms after joining a room, but that is already done in PublicShareAuth and the Files plugin (followed by some specific code for each case once the synchronization is done). Due to this calling "syncAndSetActiveRoom" after joining a room is only needed in Application. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 731345e100e3c536168e9339057055cfcc5716ae Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Fri Jun 7 11:57:27 2019 +0200 Do not set guest name if joined room is not current room This is more a formal fix, as for guests a "joinRoom" event would not be triggered with a room that is not the current room, but if it was trying to set the name would fail. Besides that it accomodates further changes in the "joinRoom" handler, as it will be typically used when the current room is joined. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit e0c96a7b2c15bcee12025d0f958ba956b061e46b Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu Jun 6 19:07:30 2019 +0200 Remove unneeded code The "active" event is no longer listened to since the room collection was removed, so there is no need to trigger it. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 07f5c41f2bafc49464b2f25c54a54a7ec87e1ed1 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu Jun 6 19:04:33 2019 +0200 Remove unneeded code The room collection was never used, so it is not needed. Moreover, although it was initialized it was never fetched, as it was never set as the room collection to be synchronized by the signaling object. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 8e1a2615f72dd63b9ac4841756346a2cd2787fd2 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu Jun 6 19:02:39 2019 +0200 Remove unneeded code The event is never listened to, so there is no need to stop listening to it. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 7a7aa56fefe11ea94dfad66d3361aacd96a8180c Author: Joachim Bauch <bauch@struktur.de> Date: Wed Feb 13 11:48:00 2019 +0100 Only sync and set active room after user has joined room. Signed-off-by: Joachim Bauch <bauch@struktur.de> commit 0393dc83cd1a5a4c14fbf3b78fe5c6e03727b3a3 Author: Nextcloud bot <bot@nextcloud.com> Date: Fri Jun 7 02:32:15 2019 +0000 [tx-robot] updated from transifex commit 0fd6c7f7ab0deb665157c8e7c4929538a40b4590 Merge: 2568eaea 02850866 Author: Ivan Sein <ivan@nextcloud.com> Date: Thu Jun 6 13:55:13 2019 +0200 Merge pull request #1869 from nextcloud/dependabot/npm_and_yarn/vue/nextcloud-axios-0.2.0 Bump nextcloud-axios from 0.1.3 to 0.2.0 in /vue commit 02850866293368b0f64528baad10dc8a931a8b72 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Thu Jun 6 09:33:20 2019 +0000 Bump nextcloud-axios from 0.1.3 to 0.2.0 in /vue Bumps [nextcloud-axios](https://github.com/ChristophWurst/nextcloud-axios) from 0.1.3 to 0.2.0. - [Release notes](https://github.com/ChristophWurst/nextcloud-axios/releases) - [Commits](https://github.com/ChristophWurst/nextcloud-axios/compare/v0.1.3...v0.2.0) commit 2568eaea6d03885c79d93ac4c3bdda19521b5f35 Merge: 8ba48f2c 1ee81ba7 Author: Ivan Sein <ivan@nextcloud.com> Date: Thu Jun 6 11:31:13 2019 +0200 Merge pull request #1877 from nextcloud/dependabot/npm_and_yarn/vue/axios-0.18.1 [Security] Bump axios from 0.18.0 to 0.18.1 in /vue commit 8ba48f2cc3e2b1935d35575b03d5282831db141e Author: Nextcloud bot <bot@nextcloud.com> Date: Thu Jun 6 02:34:43 2019 +0000 [tx-robot] updated from transifex commit b7ed56f1fde0ccb0ab61dcee905e36aa4f2df209 Merge: 7e551c9f 007c45c8 Author: Ivan Sein <ivan@nextcloud.com> Date: Wed Jun 5 09:41:18 2019 +0200 Merge pull request #1861 from nextcloud/dependabot/npm_and_yarn/vue/eslint-plugin-import-2.17.3 Bump eslint-plugin-import from 2.17.2 to 2.17.3 in /vue commit 1ee81ba76125e36ed4c00a5b0589e05617e13af2 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Sun Jun 2 01:12:04 2019 +0000 [Security] Bump axios from 0.18.0 to 0.18.1 in /vue Bumps [axios](https://github.com/axios/axios) from 0.18.0 to 0.18.1. **This update includes security fixes.** - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v0.18.1/CHANGELOG.md) - [Commits](https://github.com/axios/axios/compare/v0.18.0...v0.18.1) commit 7e551c9fa5d291d061b585fb760dcf1d240c8c2f Author: Nextcloud bot <bot@nextcloud.com> Date: Wed Jun 5 02:34:15 2019 +0000 [tx-robot] updated from transifex commit acfd54c4d179786f4d6af530654f0d29217ea5d1 Merge: 1cd91bf1 b97978cd Author: Ivan Sein <ivan@nextcloud.com> Date: Tue Jun 4 18:43:23 2019 +0200 Merge pull request #1843 from wiswedel/wiswedel/icon-choice-moderator-promotion improved icon choice for moderator promotion commit b97978cdf11cf7e6daedeb0b9701e749bcc0f5e8 Author: Sascha Wiswedel <sascha.wiswedel@nextcloud.com> Date: Tue May 21 12:47:46 2019 +0200 Set icon-rename to promote/demote moderator action. Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com> commit 007c45c82fc6b0dcdf6140e0e322b62f2ed049a5 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Mon Jun 3 14:34:34 2019 +0000 Bump eslint-plugin-import from 2.17.2 to 2.17.3 in /vue Bumps [eslint-plugin-import](https://github.com/benmosher/eslint-plugin-import) from 2.17.2 to 2.17.3. - [Release notes](https://github.com/benmosher/eslint-plugin-import/releases) - [Changelog](https://github.com/benmosher/eslint-plugin-import/blob/master/CHANGELOG.md) - [Commits](https://github.com/benmosher/eslint-plugin-import/compare/v2.17.2...v2.17.3) commit 1cd91bf12c299050f83fb8e19bedaa6bff72737b Merge: 976aae10 9ca8995d Author: Ivan Sein <ivan@nextcloud.com> Date: Mon Jun 3 16:32:21 2019 +0200 Merge pull request #1856 from nextcloud/dependabot/npm_and_yarn/vue/eslint-plugin-node-9.1.0 Bump eslint-plugin-node from 9.0.1 to 9.1.0 in /vue commit 976aae10650bd2a6904e6154c339a07d0203be51 Author: Nextcloud bot <bot@nextcloud.com> Date: Mon Jun 3 02:33:17 2019 +0000 [tx-robot] updated from transifex commit 388da363a897a43166e20b5e9897bff7c068625f Author: Nextcloud bot <bot@nextcloud.com> Date: Sun Jun 2 02:34:23 2019 +0000 [tx-robot] updated from transifex commit c0793405a342cb46d21e3734006290b2b7d9fa04 Merge: fde6bd22 09e0ff85 Author: Ivan Sein <ivan@nextcloud.com> Date: Sat Jun 1 10:12:46 2019 +0200 Merge pull request #1859 from nextcloud/dependabot/npm_and_yarn/vue/tar-2.2.2 [Security] Bump tar from 2.2.1 to 2.2.2 in /vue commit fde6bd2208c753b797fbfad0eda02b06ff6ae6d8 Merge: cb36af00 91fda95f Author: Ivan Sein <ivan@nextcloud.com> Date: Fri May 31 14:04:28 2019 +0200 Merge pull request #1858 from nextcloud/show-warning-when-browser-silently-fails-to-get-user-media Show warning when browser silently fails to get user media commit cb36af0013db9cf58a0e632faa154c60bdd05550 Merge: e5d51e05 1230f1fc Author: Ivan Sein <ivan@nextcloud.com> Date: Fri May 31 13:48:47 2019 +0200 Merge pull request #1868 from nextcloud/fix-view-for-participants-without-streams Fix view for participants without streams commit 1230f1fc9a3fae615d71d5b95e67ef926e28ab3c Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 28 13:46:10 2019 +0200 Fix view for participants without streams When the MCU is used if a participant has no audio nor video streams no peer connection will be created by that participant to send the streams to the MCU, and no peer connections will be created by the rest of the participants to receive the streams of that participant from the MCU. As a VideoView is created for every participant when they join the call and later updated once the peer connection is established the VideoView for participants without streams was always kept in its initial state. Now the VideoView is explicitly set to a "connected without streams" state as soon as it is created for participants without streams. Note, however, that this shows the avatar and the "audio not available" icon, but it does not show the participant name (except a generic "Guest" for guests), as the participant name is updated through the data channel of the peer connection, so when the participant has no streams the nick is never updated nor even set. All the issues described above happen also if no MCU is used and both the local participant and the remote one have no streams; if the local participant or the remote one has any stream then a peer connection is created between them, even if the other participant has no stream. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit e5d51e05e33142b78e6f1e9860468eae0a242c6d Merge: 707c6f4d 92c1c2f0 Author: Ivan Sein <ivan@nextcloud.com> Date: Wed May 29 11:07:05 2019 +0200 Merge pull request #1865 from nextcloud/fix-message-list-not-reloaded-after-being-shown-again Fix message list not reloaded after being shown again commit 707c6f4defac850c5103f4bf8f400ef6ead67f4c Author: Nextcloud bot <bot@nextcloud.com> Date: Wed May 29 02:42:51 2019 +0000 [tx-robot] updated from transifex commit 92c1c2f0de8f9b291c48b7558e8ee05b5b744653 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 28 13:28:09 2019 +0200 Fix message list not reloaded after being shown again When the virtual list is hidden adding new elements to it has no effect; it is necessary to explicitly reload it once visible for the new elements to be loaded. During a call the chat is moved to a tab in the sidebar, and when a different tab is selected the previous one is detached (and, thus, hidden). Therefore, when the chat tab is shown again the message list must be reloaded to load the messages that could have been added while hidden. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 355771212eab047adc265895c6e4e14d6a71d402 Merge: 9ebe9969 bf28b19c Author: Ivan Sein <ivan@nextcloud.com> Date: Mon May 27 09:58:26 2019 +0200 Merge pull request #1842 from wiswedel/wiswedel/guest-rename-button-visibility-always make rename button always visible commit 9ebe9969c3e47fc47dfbe3de47271768903fea65 Author: Nextcloud bot <bot@nextcloud.com> Date: Sat May 25 02:42:35 2019 +0000 [tx-robot] updated from transifex commit 09e0ff8541c8af31eaba8dcdc0cac480e73aaf93 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Fri May 24 17:39:44 2019 +0000 [Security] Bump tar from 2.2.1 to 2.2.2 in /vue Bumps [tar](https://github.com/npm/node-tar) from 2.2.1 to 2.2.2. **This update includes security fixes.** - [Release notes](https://github.com/npm/node-tar/releases) - [Commits](https://github.com/npm/node-tar/compare/v2.2.1...v2.2.2) commit 91fda95fd31d74071ca0224204cca8a279727cf9 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Fri May 24 18:38:06 2019 +0200 Show warning when browser silently fails to get user media In some cases the browser may enter in a faulty state in which "getUserMedia" does not return neither successfully nor with an error. It is not possible to detect this except by guessing when some time passes and the user has not granted nor rejected the media permissions, so now a warning is shown to the user when that happens. However, not having granted nor rejected the media permissions after some time does not guarantee that there is a problem; it could simply be that the user has not done it yet. Therefore, the warning is hidden if the media permissions are finally granted or rejected, or when joining the call has been interrupted (for example, due to changing to a different room). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 9ca8995d2a808320c9c62c3f0c49d4185f07c25e Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Fri May 24 15:23:11 2019 +0000 Bump eslint-plugin-node from 9.0.1 to 9.1.0 in /vue Bumps [eslint-plugin-node](https://github.com/mysticatea/eslint-plugin-node) from 9.0.1 to 9.1.0. - [Release notes](https://github.com/mysticatea/eslint-plugin-node/releases) - [Commits](https://github.com/mysticatea/eslint-plugin-node/compare/v9.0.1...v9.1.0) commit c043b2a93540524c6b8b13b6d2e34167f0aeafea Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Fri May 24 15:22:38 2019 +0000 Bump @babel/core from 7.4.4 to 7.4.5 in /vue Bumps [@babel/core](https://github.com/babel/babel) from 7.4.4 to 7.4.5. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md) - [Commits](https://github.com/babel/babel/compare/v7.4.4...v7.4.5) commit 781a866cb4382798ca3e6925756796a08d8a5a40 Author: dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com> Date: Fri May 24 15:21:29 2019 +0000 Bump @babel/preset-env from 7.4.4 to 7.4.5 in /vue Bumps [@babel/preset-env](https://github.com/babel/babel) from 7.4.4 to 7.4.5. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md) - [Commits](https://github.com/babel/babel/compare/v7.4.4...v7.4.5) commit 876040d98eb84e14b63a6b84a35b1ac00af71574 Merge: 7d2366ca 71f66fe9 Author: Ivan Sein <ivan@nextcloud.com> Date: Fri May 24 09:04:07 2019 +0200 Merge pull request #1847 from nextcloud/fix-joining-call-before-joining-room-after-forced-reconnection-with-external-signaling Fix joining call before joining room after forced reconnection with external signaling commit 7d2366cae5b446f74233ead1a26e45523ab5b81c Author: Nextcloud bot <bot@nextcloud.com> Date: Fri May 24 02:43:08 2019 +0000 [tx-robot] updated from transifex commit dc1806a21c86e8864937d5234b982d800296ac2c Merge: 004da867 344c3b85 Author: Ivan Sein <ivan@nextcloud.com> Date: Thu May 23 21:00:17 2019 +0200 Merge pull request #1848 from nextcloud/remove-volume-datachannel-message Do not send volume datachannel message. commit 344c3b85cc4be087d6007617c1da2d46bc05e30a Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu May 23 20:34:12 2019 +0200 Remove handler for "volume" datachannel message As the "volume" datachannel message its handler (that just emitted an event not handled anywhere) is no longer needed. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit a8013d567f0dbd852df1ae2bd3cb348d8e733ab9 Author: Ivan Sein <ivan@nextcloud.com> Date: Thu May 23 20:13:30 2019 +0200 Do not send volume datachannel message. Signed-off-by: Ivan Sein <ivan@nextcloud.com> commit 71f66fe9b1e86fb244f9c7809bdf27c4c68e3d17 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu May 23 18:00:58 2019 +0200 Fix joining call before joining room after forced reconnection When the external signaling server is used, after successfully sending a "joinRoom" message to the Nextcloud server a message is sent too the external signaling server (Standalone._joinRoomSuccess); this registers the Nextcloud session in the signaling server, and is needed by the signaling server to be able to properly process further messages from that session. Joining a call requires that the Nextcloud session is registered, so "joinCall()" is queued until joining the room if called before that; whether the session is registered or not is tracked with "signalingRoomJoined". When a reconnection is forced the room is joined again and, if the participant was in a call, the call is joined again. As the Nextcloud session changed the call should not be joined until the new session is registered again. However, as "signalingRoomJoined" was emptied only in "leaveRoom()" and this is not called in a forced reconnection its value still matched the room token, so the call was immediately joined after a reconnection without properly waiting for the session to be registered. Due to this the external signaling server could received the message to join the call after or before the session was registered (depending on how fast the messages were sent and processed), and thus the call was properly joined or not depending on the case. In the external signaling server the Nextcloud session is unregistered when the "bye" message is received, so for parallelism with that behaviour "signalingRoomJoined" is now emptied too when sending the "bye" message (instead of explicitly emptying it only for forced reconnections). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 73770cd4e0885e62700055e641a954fa7321c1f6 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu May 23 17:54:23 2019 +0200 Fix call flags not kept after joining a pending call When the external signaling server is used "joinCall()" does not join the call if its room has not been joined first. However, when that happens, the call is automatically joined later once the room has been joined. In that case the same flags given when "joinCall()" was called should be used once the call is actually joined; otherwise, if no flags are provided, the default flags would be used by the server, which may not match the real call flags. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit bf28b19c6e1a5a290db64f0b47c587b444a555e4 Author: Sascha Wiswedel <sascha.wiswedel@nextcloud.com> Date: Tue May 21 12:14:07 2019 +0200 Make rename button always visible Rename buttons for guest participants and rooms should always be visible (at least with opacity) to make their very existence more obvious. Before they were always hidden and shown with full opacity when the cursor was on the label wrapper, even if it was possible to interact with the button only when the cursor was on it. Now, as the buttons are always visible with a low opacity, the full opacity is set only when the cursor is on the button itself and thus when it can be interacted with. Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com> commit 004da86711cce80a7f1b7a1d991b6d0ca802e05f Author: Nextcloud bot <bot@nextcloud.com> Date: Wed May 22 02:43:53 2019 +0000 [tx-robot] updated from transifex commit 00f3138dacffc06e9f13fa7098dc6bb72cdf4d4d Author: Nextcloud bot <bot@nextcloud.com> Date: Tue May 21 04:55:43 2019 +0000 [tx-robot] updated from transifex commit 3d735fa5508a0884dccd04a74455c4e83cf9d0c0 Author: Nextcloud bot <bot@nextcloud.com> Date: Sun May 19 02:43:05 2019 +0000 [tx-robot] updated from transifex commit 7a8210e15f37a8852affb20703f59ce71656fd4d Author: Nextcloud bot <bot@nextcloud.com> Date: Sat May 18 02:41:51 2019 +0000 [tx-robot] updated from transifex commit 9388857676faa8f135953502a09f3bb258181703 Merge: e4f0f730 7f53408f Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu May 16 14:37:16 2019 +0200 Merge pull request #1831 from nextcloud/update-changelog-for-6.0.1 Update changelog for 6.0.1 commit 7f53408f870b63c0bcceed279f1fdca945799eaa Author: Joas Schilling <coding@schilljs.com> Date: Thu May 16 14:29:11 2019 +0200 Update changelog for 6.0.1 Signed-off-by: Joas Schilling <coding@schilljs.com> commit e4f0f7307d602f8e9ad9a277debc45a3c7553645 Merge: c9f9938c 0f203ed1 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu May 16 14:10:59 2019 +0200 Merge pull request #1818 from nextcloud/disable-video-by-default-when-joining-calls Disable video by default when joining calls commit 0f203ed1f8c9013659a05fd06cc2776f3028e285 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu May 16 06:09:50 2019 +0200 Add explanation to the enable video button tooltip about reconnection Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 2e469485adaf9602987135622ada8a94316794ea Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 14 10:45:41 2019 +0200 Do not send video by default in rooms with 5 or more than 5 participants Now when joining a call in a room with 5 or more than 5 participants the video is disabled and not sent by default, even if available. Enabling the video will cause a reconnection to the other peers and from that point on the video will be sent, even if it is later disabled. If the call is left and then joined again the video will be not sent until explicitly enabled again (unless the number of participants in the conversation is now below 5). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 64d0646bc4223bee09eb920a30b222f9cb8ab46c Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 14 10:42:17 2019 +0200 Adjust default enabled media when joining calls Now video is always disabled by default when joining a call; audio is enabled on one-to-one calls, but it is also disabled by default for group or public calls. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 8d7a5e03513f9449da9b8062831ebfd8055b26ad Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 14 10:36:57 2019 +0200 Force reconnection if video is enabled when it is not being sent If the video is available but not being sent a forced reconnection is needed to start sending it, as there is no support for renegotiation and the Peer objects need to be created again. The same call flags as the current ones will be used when joining the call again due to a forced reconnection, so those flags need to be updated to specify that video became available. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 0cedf38ca1fe883a82a8d715764736f81b6b99b1 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 14 10:12:59 2019 +0200 Add naive forced reconnect with the internal signaling server Forced reconnections with the internal signaling server just leave the call and join it again. However, as the same session as before is used, the peers must be explicitly ended before the reconnection is forced; otherwise when the list of participants is refreshed the same peers as before will be in there and no reconnection would happen. Even if the reconnection to the other peers is caused by them being removed note that leaving the call and joining it again is needed too; without this the WebRTC session id (Peer.sid) would not change, so the reconnecting peer would not be seen as stale by the remote peers and thus they would just soft reconnect, without recreating the Peer object. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit fc1668a67779f627e3944b844846f45359c257b0 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 14 09:31:43 2019 +0200 Extract function to force reconnections Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 9c0bbf7a4d657991fe6cc018c3d31f28de2b40a8 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Mon May 13 22:11:31 2019 +0200 Add switch to send or not to send video when it is available Until now, when local video was available it was always sent to the other peers (directly, or indirectly through the MCU); even if the video was disabled a black stream was sent. Despite being more lightweight than the full video that black stream still needs to be processed by the clients, which could require lots of resources when several of those black streams are sent in a large group call. The proper way to handle this would be not to send the video when it is disabled and only send it when it is available and enabled, triggering a renegotiation of the streams whenever the video is enabled or disabled. However, renegotiation is not supported yet in the WebUI nor in mobile apps, so for the time being a switch was added that, when disabled, prevents the video from being sent even if it is available. Note that this switch is currently "static", that is, Peer objects are not updated when the switch changes; they must be destroyed and created again for the value to be taken into account. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 2e5114af0aad9beace36cec6eb6a6bd2c39d0017 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Mon May 13 17:09:01 2019 +0200 Replace deprecated "addStream" with "addTrack" "addTrack" was not available in older Chromium versions, but WebRTC Adapter provides a shim for it, so it is safe to use it. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit c9f9938c281fa2030ee6a131674808d27d957ac8 Merge: 5528e881 d730affc Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu May 16 11:47:43 2019 +0200 Merge pull request #1825 from nextcloud/fix-flickering-spinner-on-avatars-during-calls-with-the-mcu Fix flickering spinner on avatars during calls with the MCU commit 5528e881df88aceee349689610c82bc9a22f92f3 Merge: b737cdd6 226d59a6 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu May 16 10:03:42 2019 +0200 Merge pull request #1824 from nextcloud/fix-status-not-kept-after-forced-reconnections Fix status not kept after forced reconnections commit b737cdd6a4949ecbcb467ed96b86df2eb50c6085 Merge: 4d15e979 a54b5b68 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu May 16 09:50:31 2019 +0200 Merge pull request #1807 from nextcloud/bugfix/noid/better-grouping-and-timestamps Better grouping and timestamps commit d730affc8171cdb869d3bcbeddb69550f7bc104f Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu Apr 11 15:32:48 2019 +0200 Fix flickering spinner on avatars during calls with the MCU The MCU sends the nick of each participant again and again, which caused the avatar to be continuously set, and this caused a loading icon to appear on the avatar. Now the avatar (and the name) is set again only if the user id or the participant name (including the "Guest" placeholder) has changed since it was last set. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 4d15e979b3d9ab720c2c940d484f34932890d9f0 Author: Nextcloud bot <bot@nextcloud.com> Date: Thu May 16 02:41:20 2019 +0000 [tx-robot] updated from transifex commit 226d59a64403e8f9a399e6042e928316329ada11 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 15 16:49:13 2019 +0200 Fix call flags not kept after forced reconnections When joining a call again due to a forced reconnection the same flags used when originally joining the call should be provided again; otherwise, if no flags are provided, the default flags would be used by the server, which may not match the real call flags. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit a14d7a6f1e10db84bf507073089422502f1f8a49 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 15 15:19:58 2019 +0200 Fix video status not kept after forced reconnections When a reconnection is forced the call is left and then joined again. In that case the initial adjustments done when joining a call should not be done again. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 637d45ab74a045a6b7dd11554f8e0bc82c1a3c2e Merge: dca62009 4cb08c05 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed May 15 15:33:02 2019 +0200 Merge pull request #1821 from nextcloud/move-things-that-should-not-be-there-outside-of-signaling-object Move things that should not be there outside of signaling object commit 4cb08c05275d2d6d6dd554d6cb964ad6aebc1a01 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 15 15:22:35 2019 +0200 Print log when no longer pulling messages due to repeated failures Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit d55617ca22595f9771d5f28684b00f4e25a0e703 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 15 11:15:21 2019 +0200 Move handling of failures pulling messages outside of signaling object When pulling messages from the internal signaling server fails several times to pulling of messages is stopped. This is the only thing that should be done in the signaling object; other handling like leaving the current room or leaving the call in WebRTC should be done in their respective objects as a response to an event triggered by the signaling object. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit f0f80c63b79ed1b238896a91f0c70b360949dc51 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 15 10:07:08 2019 +0200 Move no MCU warning outside of signaling object The signaling object should not directly modify the UI, so the notification is now shown by handling the "joinCall" event triggered by the signaling. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit dca62009a4db24e4e0e8a9e359708bc1200dc489 Author: Nextcloud bot <bot@nextcloud.com> Date: Tue May 14 02:39:38 2019 +0000 [tx-robot] updated from transifex commit a54b5b688c23ffdeb65b41f585c4c13a5d21dc13 Author: Joas Schilling <coding@schilljs.com> Date: Fri May 10 13:37:39 2019 +0200 Better grouping of chat messages * timestamp is shown after 5 messages or 30 seconds * author is shown after 20 messages or 1 hour Signed-off-by: Joas Schilling <coding@schilljs.com> commit ae4a56793d04a574e6f2ac7acc9e41e98267afd6 Author: Joas Schilling <coding@schilljs.com> Date: Fri May 10 13:23:51 2019 +0200 Don't use relative timestamps for chat messages Signed-off-by: Joas Schilling <coding@schilljs.com> commit 95cd3ec78b737f871cae4eedb46e693ef6d604af Merge: 6414470b 6d4fae26 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Mon May 13 13:38:12 2019 +0200 Merge pull request #1815 from nextcloud/update-npm-packages Update npm packages commit 6414470bb46d84504a83d9bc3487eecbc6009216 Merge: 8705a6c3 b9f6f1fd Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Mon May 13 13:34:11 2019 +0200 Merge pull request #1791 from nextcloud/add-back-compiled-javascript-files Add back compiled JavaScript files commit 6d4fae261a783031ce3d832d941be6a799b5e555 Author: Joas Schilling <coding@schilljs.com> Date: Mon May 13 12:42:49 2019 +0200 Update all NPM packages Signed-off-by: Joas Schilling <coding@schilljs.com> commit b9f6f1fd54b1bad232f7311d03f886d500e21331 Author: Joas Schilling <coding@schilljs.com> Date: Mon May 13 12:27:24 2019 +0200 Remove vue hot reload so there are no paths commited Signed-off-by: Joas Schilling <coding@schilljs.com> commit 8705a6c3bd11a82ee4fde1f60d22d33bccee3fc9 Merge: 74e205a6 fae2a7fb Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Mon May 13 10:34:54 2019 +0200 Merge pull request #1809 from nextcloud/bugfix/noid/reload-the-conversation-list-with-standalone-signaling Also reload the conversation list every 30s with standalone signaling commit 74e205a6323c3eea2df998b06f516cfdcae6e300 Author: Nextcloud bot <bot@nextcloud.com> Date: Mon May 13 00:36:42 2019 +0000 [tx-robot] updated from transifex commit a9ff667216b0ab3888d96444991ace8845259d7c Author: Nextcloud bot <bot@nextcloud.com> Date: Sun May 12 00:46:47 2019 +0000 [tx-robot] updated from transifex commit fae2a7fbaf4d8397ac00f94b4fbbec7b295c4869 Author: Joas Schilling <coding@schilljs.com> Date: Fri May 10 15:40:22 2019 +0200 Also reload the conversation list every 30s with standalone signaling Signed-off-by: Joas Schilling <coding@schilljs.com> commit c9850a52ece5eafddace1dfd11d11bac0c93edc9 Merge: da938a5c da98d161 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Fri May 10 14:47:22 2019 +0200 Merge pull request #1801 from nextcloud/fix-messages-not-loaded-when-commands-are-used-with-the-mcu Fix messages not loaded when commands are used with the MCU commit da98d161f14c6e14a4012916de4351021bc8a83b Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Fri May 10 09:32:43 2019 +0200 Add basic integration tests for commands Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 2825271bccfee46323a1465267f17d14ef43ab1c Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Fri May 10 09:00:45 2019 +0200 Add document about invisible messages not returned by ChatController Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit c883f9f688c30411716125cf9cae9decaf83f704 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Thu May 9 14:21:48 2019 +0200 Fix messages not loaded when commands are used with the MCU When fetching chat messages ChatController may not return as many messages as requested. In the past this meant that there were no more messages in the room, but since the introduction of commands some messages may not be returned because they should not be visible to the participant fetching them. Thus, now the number of returned messages does not mean anything regarding whether there are still more messages in the room or not, but this can be known by looking for a "304 Not modified" response (which is only sent when there are no more messages in the room). When no MUC is used the chat messages are polled again and again, so the behaviour change explained above made no difference. However, when the MCU is used the messages are fetched until there are no more messages in the room and, then, they are only fetched when a new message is sent. Checking whether there are more messages in the room or not was based on the number of returned messages, so the fetch of messages until there were no more messages in the room wrongly stopped when fetching a batch of messages that included one not visible for the current participant. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit da938a5c2ca912e37fe75c288736fbbcc836c209 Merge: 8d472b0a 1722388f Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Fri May 10 11:40:51 2019 +0200 Merge pull request #1802 from nextcloud/fix/select2_is_in_dist Select2 is in the main dist file commit 8d472b0a70a32324e725e8926593499436d99cf8 Author: Nextcloud bot <bot@nextcloud.com> Date: Fri May 10 00:37:53 2019 +0000 [tx-robot] updated from transifex commit 1722388f4f5da5fb299e8391d4e8a0844b75eed4 Author: Roeland Jago Douma <roeland@famdouma.nl> Date: Thu May 9 20:36:11 2019 +0200 Select2 is in the main dist file Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl> commit 37d2b701d368733f30181c42053986d6f9e075d9 Author: Nextcloud bot <bot@nextcloud.com> Date: Thu May 9 00:37:12 2019 +0000 [tx-robot] updated from transifex commit 8d5504d7d8e6cc945d1e130febbe4b1755296464 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 8 18:08:03 2019 +0200 Do not rebuild JavaScript files before packing a release As the JavaScript files are versioned again they should not be rebuilt before packing a release; otherwise the JavaScript files in the package could be different than the ones in the version control system. As the JavaScript files are no longer built it is not needed either to set up the development environment; however, it is still necessary to remove the build directory before packaging the release, so this is now explicitly done. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit ad7caab88c5eb545ef9b5f34df99d106200b116f Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 8 17:44:12 2019 +0200 Add back compiled JavaScript files Otherwise acceptance tests fail when run in Drone, as the WebUI does not work before the JavaScript files are built and currently it is not possible to build them in the Docker container used for acceptance tests. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit c9793a8a5490f31e6451a7b48cbe071da25b66ca Merge: d8d9ccad c6af361e Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed May 8 13:24:44 2019 +0200 Merge pull request #1779 from nextcloud/techdebt/noid/root-make-file-and-remove-compiled-assets Merge make files and remove compiled JS commit c6af361e3d2d7a213ca6cfca7599d1a0e20dfafc Author: Joas Schilling <coding@schilljs.com> Date: Wed May 8 13:08:37 2019 +0200 Update the templates when the deps are updated Signed-off-by: Joas Schilling <coding@schilljs.com> commit d8d9ccad9b4eebe6347009c764a37eb48a7aa957 Merge: 208d58d2 dd19a43c Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed May 8 12:03:06 2019 +0200 Merge pull request #1787 from nextcloud/remove-javascript-test-configuration-and-dependencies Remove JavaScript test configuration and dependencies commit dd19a43ccd627f5885bfb1efa9599a62e30d56c9 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 8 11:03:58 2019 +0200 Remove JavaScript test configuration and dependencies Currently there are no JavaScript unit tests, so the related stuff can be removed and added later if/when needed. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 208d58d25c82bd8f899a5af916cbacbfdde0b49d Merge: 41637392 29138d35 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed May 8 11:00:06 2019 +0200 Merge pull request #1785 from nextcloud/bump-babel-from-7.3.4-to-7.4.4 Bump Babel from 7.3.4 to 7.4.4 commit 29138d3560af3622848603b36f0c4b746fcea176 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 8 10:42:34 2019 +0200 Bump Babel from 7.3.4 to 7.4.4 Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 41637392adf0c8bb50c4bfeed07ecab96dc3b507 Merge: 9e5f119f 43ee03cc Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed May 8 10:13:11 2019 +0200 Merge pull request #1781 from nextcloud/add-package-lock-json-to-the-versioned-files Add "package-lock.json" to the versioned files commit 43ee03cce7bfab8ec818541403cb47b0419c4243 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed May 8 09:23:08 2019 +0200 Add "package-lock.json" to the versioned files As stated in NPM documentation, the file is intended to be committed into source repositories; this ensures that everyone is using the same dependencies (as the semantic versioning of dependencies in "package.json" does not). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 9e5f119fa58bf28d20c3cdcaacd1fb3e954e7c92 Author: Nextcloud bot <bot@nextcloud.com> Date: Wed May 8 00:40:51 2019 +0000 [tx-robot] updated from transifex commit 983e71bd932069936f3a4085d79a1f7071b7793d Author: Joas Schilling <coding@schilljs.com> Date: Mon May 6 14:45:39 2019 +0200 Merge make files and remove compiled JS Signed-off-by: Joas Schilling <coding@schilljs.com> commit a2a21e3742db6256bf9696025f815d9d6513cb73 Merge: c5c8ccd0 84f48f29 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Tue May 7 10:44:28 2019 +0200 Merge pull request #1774 from nextcloud/fix-vertical-position-of-confirm-icon-in-authenticate-page Fix vertical position of confirm icon in authenticate page commit c5c8ccd0653fa0f30148fe54a110b19b0fbf4b9c Merge: 959f73d8 2f6fe862 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Tue May 7 10:37:15 2019 +0200 Merge pull request #1773 from nextcloud/rename-call-to-conversation-in-authenticate-page Rename "call" to "conversation" in authenticate page commit 959f73d8d48600ffea53a42375a42ef6e78d5798 Merge: 8905be0f 3ac3d429 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Tue May 7 10:33:04 2019 +0200 Merge pull request #1772 from nextcloud/bugfix/1768/handle-password-protected-rooms-correctly Correctly forward the password to the controller method commit 84f48f29ec45411b92c89289274a704bee6ee9be Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 7 10:05:31 2019 +0200 Fix vertical position of confirm icon in authenticate page The server explicitly sets the height of confirm icons inside password inputs, which overrides the height set in Talk for submit inputs in the authenticate page. Therefore, the height set by the server needs to be overriden to honour the height set in Talk (which matches the height of the password input in the authenticate page). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 2f6fe8622eb8a8477f44f13eadde0a97c06c9353 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue May 7 08:54:48 2019 +0200 Rename "call" to "conversation" in authenticate page Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 3ac3d4297906a8fe31e18b38c16c2bf50edd4d19 Author: Joas Schilling <coding@schilljs.com> Date: Mon May 6 15:44:26 2019 +0200 Receive post requests with the password too Signed-off-by: Joas Schilling <coding@schilljs.com> commit 8905be0f4f7e5bedd96b5ed10d74c8fd9b11568a Author: Nextcloud bot <bot@nextcloud.com> Date: Mon May 6 00:38:46 2019 +0000 [tx-robot] updated from transifex commit f89db65bf2af4dd87b0297542a645a4e765046b5 Author: Nextcloud bot <bot@nextcloud.com> Date: Fri May 3 00:36:46 2019 +0000 [tx-robot] updated from transifex commit f9bf564f2d49a61b9d94de619f753a16b3767dc5 Merge: b3ed0501 a13c0a48 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu May 2 11:40:19 2019 +0200 Merge pull request #1764 from nextcloud/fix-condition-to-ignore-stats-in-checkMediaPeer Fix condition to ignore stats in "checkMediaPeer" commit a13c0a48159a3881c878401d18240992b0482415 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Apr 30 09:24:40 2019 +0200 Fix condition to ignore stats in "checkMediaPeer" Once a result was found all the following stats that had "bytesReceived" were checked, even if their media type did not match. However, note that, while incorrect, this did not cause any practical issue, as the first time that the peer was unmuted the proper stat was checked, and the following incorrect checks just unmuted again an already unmuted peer. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit b3ed05019c0c6a4162faefe498ef98251fed3a7d Author: Nextcloud bot <bot@nextcloud.com> Date: Tue Apr 30 00:37:58 2019 +0000 [tx-robot] updated from transifex commit 24be335069b91813d3add0db12e716ff30ed6c78 Merge: b8d16489 5c3e6f08 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Mon Apr 29 14:39:05 2019 +0200 Merge pull request #1759 from nextcloud/dependabot/npm_and_yarn/vue/@babel/core-7.4.4 Bump @babel/core from 7.4.3 to 7.4.4 in /vue commit 5c3e6f08355053d7b543e11a15affdc3b81184dc Author: Joas Schilling <coding@schilljs.com> Date: Mon Apr 29 14:38:05 2019 +0200 Update all packages Signed-off-by: Joas Schilling <coding@schilljs.com> commit 3efc9f1b33bd4c8470a5e7b2a59e47fd1b1a4522 Author: dependabot[bot] <support@dependabot.com> Date: Sun Apr 28 01:12:34 2019 +0000 Bump @babel/core from 7.4.3 to 7.4.4 in /vue Bumps [@babel/core](https://github.com/babel/babel) from 7.4.3 to 7.4.4. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md) - [Commits](https://github.com/babel/babel/compare/v7.4.3...v7.4.4) Signed-off-by: dependabot[bot] <support@dependabot.com> commit b8d16489ba21f811e3c0d04be4e3306c655e0423 Author: Nextcloud bot <bot@nextcloud.com> Date: Sun Apr 28 00:37:42 2019 +0000 [tx-robot] updated from transifex commit 7e1df6a96b235f7dd8ff3a47de0a7180c7a6973a Author: Nextcloud bot <bot@nextcloud.com> Date: Sat Apr 27 00:37:03 2019 +0000 [tx-robot] updated from transifex commit dc1b91e1378089cf20ef15f373925d2520a668c3 Merge: 2bf773eb c8c8bf43 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu Apr 25 14:51:05 2019 +0200 Merge pull request #1756 from nextcloud/techdebt/noid/fix-changelog-md Fix changelog.md commit c8c8bf4316c2fb1b29b8367ee71d4d9d7fc307f6 Author: Joas Schilling <coding@schilljs.com> Date: Thu Apr 25 14:50:23 2019 +0200 Fix changelog.md Signed-off-by: Joas Schilling <coding@schilljs.com> commit 2bf773eb484472d1fcbe3a41b05044109deab939 Merge: 8355ad47 45a66bff Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu Apr 25 14:48:04 2019 +0200 Merge pull request #1745 from nextcloud/fix-screensharing-offer-sent-to-peers-not-in-the-call Fix screensharing offer sent to peers not in the call commit 8355ad47c1f3f477b992f60bb119851c2fab918b Merge: c0d23cc4 361e7202 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Thu Apr 25 14:47:39 2019 +0200 Merge pull request #1742 from nextcloud/dependabot/npm_and_yarn/vue/nextcloud-vue-0.10.0 Bump nextcloud-vue from 0.9.7 to 0.10.0 in /vue commit c0d23cc4817bcd391b3bcb1f16d5fe40951a278f Merge: 91e3cab3 e8f37a9f Author: Ivan Sein <ivan@nextcloud.com> Date: Thu Apr 25 11:17:57 2019 +0200 Merge pull request #1748 from nextcloud/bugfix/1741/conversations-without-token-break-nextcloud Do not "load" conversations without a token commit 91e3cab3851be1016ac878457b7610489b2ce6f5 Merge: cb81b275 6432cfb5 Author: Ivan Sein <ivan@nextcloud.com> Date: Thu Apr 25 11:06:48 2019 +0200 Merge pull request #1730 from nextcloud/fix-stopping-screensharing-from-the-browser Fix stopping screensharing from the browser commit cb81b275bd9e5445b404a654745318cd7a27f297 Merge: 6c911a6e d3c2b8c8 Author: Ivan Sein <ivan@nextcloud.com> Date: Thu Apr 25 11:06:22 2019 +0200 Merge pull request #1738 from nextcloud/fix-signaling-messages-with-no-payload-and-with-unserialized-attributes Fix signaling messages with no payload and with unserialized attributes commit 361e720258b3b4dc16a3553599c1f36e8bd9d090 Author: Joas Schilling <coding@schilljs.com> Date: Thu Apr 25 08:28:53 2019 +0200 Update all NPM packages Signed-off-by: Joas Schilling <coding@schilljs.com> commit e8f37a9f7755bee6344846ecada7b9db9148bc2b Author: Joas Schilling <coding@schilljs.com> Date: Thu Apr 25 08:21:49 2019 +0200 Do not "load" conversations without a token This is only a temporary solution. We should try to find out where the rooms origin from and then either delete them all together, or fix them. But since they have no token, you can't join them anyway and therefor wont miss them for now. Signed-off-by: Joas Schilling <coding@schilljs.com> commit 6c911a6e296097af793c4ed795048a59be28c576 Merge: bdc6ab47 ea13c6f8 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed Apr 24 10:05:10 2019 +0200 Merge pull request #1737 from nextcloud/bugfix/1726/dont-focus-chat-on-small-screens Dont focus chat on small screens commit 45a66bffcfd13061ded7c21a45fb313114b5dece Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Apr 23 17:52:03 2019 +0200 Fix screensharing offer sent to peers not in the call Despite its name, "usersInCallMapping" includes all the users in the room, not only those currently in the call. Therefore, when iterating through it, it should be checked whether a user is in the call or not to prevent sending the screensharing offer to peers not in the call. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit bdc6ab477aa3bb82dfbaa5106af4d7273c4fbdce Author: Nextcloud bot <bot@nextcloud.com> Date: Wed Apr 24 00:37:10 2019 +0000 [tx-robot] updated from transifex commit c0ebe9bd6d59291f750fae65b331eb3265591337 Author: dependabot[bot] <support@dependabot.com> Date: Sun Apr 21 01:12:46 2019 +0000 Bump nextcloud-vue from 0.9.7 to 0.10.0 in /vue Bumps [nextcloud-vue](https://github.com/nextcloud/nextcloud-vue) from 0.9.7 to 0.10.0. - [Release notes](https://github.com/nextcloud/nextcloud-vue/releases) - [Commits](https://github.com/nextcloud/nextcloud-vue/compare/v0.9.7...v0.10.0) Signed-off-by: dependabot[bot] <support@dependabot.com> commit b7fb16fd67ab9cb7459eda96097f492b0da9710e Author: Nextcloud bot <bot@nextcloud.com> Date: Sun Apr 21 00:38:44 2019 +0000 [tx-robot] updated from transifex commit fc996e406193c8160d0992d45bad4047f2486c11 Author: Nextcloud bot <bot@nextcloud.com> Date: Fri Apr 19 00:38:08 2019 +0000 [tx-robot] updated from transifex commit 55484a1f53d95572ed0cd431aef30ac35616c804 Author: Nextcloud bot <bot@nextcloud.com> Date: Thu Apr 18 00:38:41 2019 +0000 [tx-robot] updated from transifex commit ea13c6f8fb2cb80499732475eb66c04469e1a049 Author: Joas Schilling <coding@schilljs.com> Date: Wed Apr 17 14:28:23 2019 +0200 Dont focus chat on small screens Signed-off-by: Joas Schilling <coding@schilljs.com> commit d3c2b8c8157eed79b5e3c6441cb4fe24848182c0 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed Apr 17 14:03:45 2019 +0200 Fix sending signaling messages with unserialized attributes When offers and answers are created they are sent in the payload of a signaling message to the other peer. Both offers and answers are RTCSessionDescription objects which only serialize its own attributes, so even if the nick was added to the objects it was never serialized and sent. Now, instead of sending extended RTCSessionDescription objects a regular object with a copy of the needed attributes is sent. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 0c3a58b4f510c3bf7632295b5bb6652e6ab016e2 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Wed Apr 17 12:37:47 2019 +0200 Fix sending signaling messages without payload This reverts commit c02c8c089e67989383e7a90dd0a423343caeae85. Not all call messages contain a payload attribute, so those that do not contain it fail to be sent due to "data.payload" being undefined. Moreover, the missing JSON attributes only happens due to the type of the payload object used for offers and answers, so it is better fixed (in a following commit) where they are passed to the signaling. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit ea3c473ee2e5b285e5ba49d57ed4c825ed9acf75 Merge: f916d028 81035e8f Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed Apr 17 11:41:51 2019 +0200 Merge pull request #1731 from nextcloud/prefer-standard-api-for-screen-sharing Prefer standard API for screen sharing commit f916d028b4f6eb35a6597ad5967af22d43fb5c4b Merge: 41e9e7e4 4ae020e4 Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed Apr 17 11:23:44 2019 +0200 Merge pull request #1729 from nextcloud/fix-webrtc-not-supported-handling Fix WebRTC not supported handling commit 41e9e7e415176aaded530810db1c833a2291d744 Merge: b2529403 2867624a Author: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Date: Wed Apr 17 10:44:41 2019 +0200 Merge pull request #1728 from nextcloud/fix-sidebar-and-fullscreen-in-ie11 Fix sidebar and fullscreen in IE11 commit b25294038e8d26c3fdd3e038698be6d71ad851ff Author: Nextcloud bot <bot@nextcloud.com> Date: Wed Apr 17 00:38:46 2019 +0000 [tx-robot] updated from transifex commit 81035e8f3a1d807f2b5bab705050ef3614c02cfa Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Apr 16 20:51:32 2019 +0200 Do not split the screen sharing menu in Firefox >= 66 Before the standard "getDisplayMedia" was supported in Firefox a custom API was used for screen sharing, which made possible to choose whether to show a window or the screen. However, limiting the available display sources with constraints is explicitly forbidden in the "getDisplayMedia" spec, so that feature was dropped from Firefox when the standard API started to be used, and thus the screen sharing menu should be no longer split. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 06b1cbb31c56956e1f0191a5f07968a5efafeb76 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Apr 16 20:42:54 2019 +0200 Override screen sharing support from "webrtcsupport" module The "webrtcsupport" module does not take into account if the standard "getDisplayMedia" is available, and it only sees Firefox and Chromium/Chrome as supported; screen sharing in Edge was reported as supported only because it was mismatched for Chrome. Now the default checks are overridden to match the behaviour of the custom "getScreenMedia" module. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 6742790bfe766cb1b87753643e9c1369490f0f63 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Apr 16 20:26:08 2019 +0200 Prefer standard API for screen sharing The standard "getDisplayMedia" is now used whenever available, although the old behaviour is kept for backwards compatibility. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 4ae020e4b1fd2890d6e1ae0a891a3342385dfed4 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Mon Apr 15 19:28:59 2019 +0200 Fix handling of WebRTC supported but "getUserMedia" not available "OCA.SpreedMe.webrtc.capabilities.support" is true when both "RTCPeerConnection" and "getUserMedia" are available. However, in some cases WebRTC may be supported by the browser, yet "getUserMedia" may be not available if the code is not run in a secure context (like HTTPS). Due to this, now the "WebRTC is not supported in your browser" message is shown only if "RTCPeerConnection" is not available; if "RTCPeerConnection" is available but "getUserMedia" is not then it will be handled as a "NotAllowedError" thrown by "getUserMedia" when called in an unsecure context. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 1145eaeb091f863fc3b96f6088151be891e27062 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Mon Apr 15 19:14:08 2019 +0200 Fix calling "getUserMedia" when not available "navigator.mediaDevices.getUserMedia" may not be available in some cases, either because WebRTC is not supported by the browser or because the code is not running in a secure context (like HTTPS). Therefore, now it is checked if the function is available before trying to use it. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 2867624a9c9d318935634dc6a54288aa2b307ab3 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Mon Apr 15 11:42:56 2019 +0200 Fix fullscreen structure in IE11 Due to how Internet Explorer 11 sorts CSS rules based on their selector and how the "#app-content" left margin is set in the server it is necessary to set the ":fullscreen" rule as important to override the one from the server, which is sorted above it (unlike in the rest of browsers). Besides that, the top space added to the sidebar when IE is used needs to be removed in fullscreen mode, as in that case there is no header. The sidebar height also needs to be explicitly set to 100% due to the lack of support for "unset" in Internet Explorer 11. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 687d685c28930a76244ea01003383a6d81999723 Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Mon Apr 15 11:32:35 2019 +0200 Fix sidebar in IE11 The sidebar top position in Talk is set to 0. However, the server sets the position of the sidebar as fixed when IE is used, so in that case it needs to be pulled down to not overlap with the header. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> commit 6432cfb5d30393142e507185cf4423713f2968dc Author: Daniel Calviño Sánchez <danxuliu@gmail.com> Date: Tue Apr 16 16:46:09 2019 +0200 Fix stopping screensharing from the browser In the old LocalMedia module bundled in the official SimpleWebRTC 2.2.3 the local screen…
This fixes a race condition when (as logged in user) joining a public room that has been created by another user. It can happen that the list of rooms is fetched before the "join room" request finished, so the room is not included in the list, causing
syncAndSetActiveRoom
(https://github.com/nextcloud/spreed/blob/master/js/app.js#L324) to fail.As a solution,
syncAndSetActiveRoom
is only called when the room was joined to make sure it is included in the list of rooms.