Error opening log in 24

Steps to reproduce

Open log in a 24 instance
See log for some milliseconds
See log disappearing

Expected behaviour

Log is visible

Actual behaviour

Error: Minified React error #188; visit https://reactjs.org/docs/error-decoder.html?invariant=188 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    findDOMNode React
    transition CSSTransitionGroupChild.js:129
    componentWillEnter CSSTransitionGroupChild.js:97
    performEnter TransitionGroup.js:83
    componentDidUpdate TransitionGroup.js:192
    componentDidUpdate TransitionGroup.js:191
    React 2
    unstable_runWithPriority scheduler.production.min.js:18
    React 4
    unstable_runWithPriority scheduler.production.min.js:18
    React 6
    mt App.js:160
    emit events.js:153
    e LogProvider.js:466
    c runtime.js:63
    _invoke runtime.js:294
    w runtime.js:119
    Babel 6
    value LogProvider.js:484
    e App.js:212
    c runtime.js:63
    _invoke runtime.js:294
    w runtime.js:119
    Babel 14
    value App.js:229
    React 2
    unstable_runWithPriority scheduler.production.min.js:18
    React 9
    _t index.js:17
    _t index.js:28
    <anonymous> index.js:23
    <anonymous> index.js:23
    <anonymous> index.js:23
react-dom.production.min.js:216:199

Still happening btw

Also see #719 - the behaviour is similar but caused by log files which are too big.

From reading here

react/react#20131 pointing to https://reactjs.org/warnings/invalid-hook-call-warning.html

and running

 $ npm ls react-dom
logreader@ /var/www/localhost/htdocs/nextcloud-git-next/apps/logreader
├─┬ react-addons-css-transition-group@15.6.2
│ └─┬ react-transition-group@1.2.1
│   └── react-dom@16.14.0
└── react-dom@17.0.2

I somehow got the impression that this might be caused by pulling in multiple copies of react-dom?

We might want to replace this react addon's since it's dead https://www.npmjs.com/package/react-addons-css-transition-group

Or someone makes a greater journey and moves it to vue if that is better?

Any news?

The bug is a bit of a pain in the ass 😬.

Fix insible log entries by replacing react-addons-css-transition-grou…

still no logs in 24.0.3 :-(

The reason is the amount of log data. If you delete the old log data/nextcloud.log you should be able to see new log entries again. However if the file contains more than about 20.000 entries, the log viewer seems to get a problem.

I too have this from a few nextcloud versions and I'm not so sure it is the 20000 entries limit/problem. Even with empty/clean log file mine does not shows. And the error in the console is the react one pointed above.

Fix insible log entries by replacing react-addons-css-transition-grou…

I too have this from a few nextcloud versions and I'm not so sure it is the 20000 entries limit/problem. Even with empty/clean log file mine does not shows. And the error in the console is the react one pointed above.

You could look at my merge request #746 and see whether it works for you. The bugfix just replaces the outdated react library with the current one and adjust the corresponding API calls in order to make it work. So this is a kind of minimal approach (no porting to Vue etc. attempted, just update the outdated react library).

Thanks, I'm doing it now. After reading about this in react discussions I guess it will work. Hope this will be in next releases till waiting for vue solution.

Fix insible log entries by replacing react-addons-css-transition-grou…

Last version of Logreader written in react is Nextcloud 27.1.11 (End of life was at 2024-06-25)

Navigation Menu

Repository navigation

Error opening log in 24 #699

Steps to reproduce

Expected behaviour

Actual behaviour

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Error opening log in 24 #699

Description

Steps to reproduce

Expected behaviour

Actual behaviour

Activity

nickvergessen commented on May 19, 2022

arnowelzel commented on May 23, 2022

rotdrop commented on May 24, 2022

CarlSchwan commented on May 24, 2022

nickvergessen commented on May 25, 2022

Valdnet commented on Jun 21, 2022

wiswedel commented on Aug 1, 2022

arnowelzel commented on Aug 1, 2022

victoraroyo commented on Aug 17, 2022

rotdrop commented on Aug 17, 2022

victoraroyo commented on Aug 17, 2022

Antreesy commented on Sep 17, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions