| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Because often we catch the exception at some point and then the trace is
misleading. What's really interesting is the trace of the *previous*
exception.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Bumps [node-sass](https://github.com/sass/node-sass) from 4.14.1 to 5.0.0.
- [Release notes](https://github.com/sass/node-sass/releases)
- [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md)
- [Commits](https://github.com/sass/node-sass/compare/v4.14.1...v5.0.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
|\
| |
| |
| | |
nextcloud/dependabot/npm_and_yarn/css-vars-ponyfill-2.4.1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [css-vars-ponyfill](https://github.com/jhildenbiddle/css-vars-ponyfill) from 2.3.2 to 2.4.1.
- [Release notes](https://github.com/jhildenbiddle/css-vars-ponyfill/releases)
- [Changelog](https://github.com/jhildenbiddle/css-vars-ponyfill/blob/master/CHANGELOG.md)
- [Commits](https://github.com/jhildenbiddle/css-vars-ponyfill/compare/v2.3.2...v2.4.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
Bumps [css-loader](https://github.com/webpack-contrib/css-loader) from 3.6.0 to 5.0.1.
- [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/v3.6.0...v5.0.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
| |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
| |
|
|\ |
|
| |
| |
| | |
Co-authored-by: John Molakvoæ <skjnldsv@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| | |
Changed wording of setup check.
Reported at Transifex.
Signed-off-by: rakekniven <mark.ziegler@rakekniven.de>
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/fix/noid/import-certificates-only-by-system
Improve CertificateManager to not be user context dependent
|
| | |
| | |
| | |
| | |
| | |
| | | |
certificates and shows a warning in the admin settings
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* removes the ability for users to import their own certificates (for external storage)
* reliably returns the same certificate bundles system wide (and not depending on the user context and available sessions)
The user specific certificates were broken in some cases anyways, as they are only loaded if the specific user is logged in and thus causing unexpected behavior for background jobs and other non-user triggered code paths.
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\ \ \
| | | |
| | | | |
Add default font size
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: GretaD <gretadoci@gmail.com>
|
|\ \ \ \
| |_|_|/
|/| | | |
Work around snap.js state mess
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Snap.js is not robust enough to prevent multiple calls to open() or
close(), so we added more checks to prevent these happening even when an
animation is in progress.
Because if we let this through, snap.js will not notice that the
animation is already done (or a duplicate animation was started),
so the "transitionend" event will not fire a second time.
During an animation, snap.js sets up a setInterval() that hogs the CPU
during the animation. Since a transition doesn't always end due to the
above conditions, that CPU hogging would stay forever.
This is the best workaround so far, it seems it's not possible to cancel
that interval from the outside nor to trigger events to make it do so.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
| |/
|/| |
|
|/
|
|
| |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|
|
|
| |
Signed-off-by: nhirokinet <nhirokinet@nhiroki.net>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Jacob Neplokh <me@jacobneplokh.com>
|
|/ |
|
|\
| |
| | |
Properly put hidden-visually off-screen
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In some situations the element is still affecting the layout, especially
when a sticky is nearby.
This fix moves it properly off-screen.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/dependabot/npm_and_yarn/vue-loader-15.9.4
Bump vue-loader from 15.9.3 to 15.9.4
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [vue-loader](https://github.com/vuejs/vue-loader) from 15.9.3 to 15.9.4.
- [Release notes](https://github.com/vuejs/vue-loader/releases)
- [Changelog](https://github.com/vuejs/vue-loader/blob/master/CHANGELOG.md)
- [Commits](https://github.com/vuejs/vue-loader/compare/v15.9.3...v15.9.4)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/enhancement/eventdispatcher-typed-listener-callable
Type the event dispatcher listener callables with Psalm
|
| | |
| | |
| | |
| | | |
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| |/
|/| |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
|/ / |
|
|/
|
|
|
| |
Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Bumps [dompurify](https://github.com/cure53/DOMPurify) from 2.1.1 to 2.2.0.
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](https://github.com/cure53/DOMPurify/compare/2.1.1...2.2.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
|\
| |
| |
| | |
nextcloud/dependabot/npm_and_yarn/nextcloud/vue-3.1.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [@nextcloud/vue](https://github.com/nextcloud/nextcloud-vue) from 3.0.0 to 3.1.0.
- [Release notes](https://github.com/nextcloud/nextcloud-vue/releases)
- [Commits](https://github.com/nextcloud/nextcloud-vue/compare/v3.0.0...v3.1.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
|
| | |
|
|\ \
| |/
|/| |
Clarify import cert command
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add hint that the certificate to be imported must be in PEM format (CRT
does not parse).
Improved error message to mention that the given path must be accessible
by the web server user.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
| | |
|
| | |
|