Buy Hosting

can not upgrade from v0.9.4 to v1.0.0

General Discussion
  • Y
    1. Bringing base dependencies up to date...

    OK
    2. Updating NodeBB data store schema.
    5/3 11:01 [2536] - info: Beginning database schema update
    5/3 11:01 [2536] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
    5/3 11:01 [2536] - info: [2015/11/06] Gravatar removal skipped
    5/3 11:01 [2536] - info: [2015/12/15] Upgrading chats
    5/3 11:01 [2536] - info: [2015/12/15] Chats upgrade done!
    5/3 11:01 [2536] - info: [2015/12/23] Upgrading chat room hashes
    5/3 11:01 [2536] - info: [2015/12/23] Chats room hashes upgrade done!
    5/3 11:01 [2536] - info: [2015/12/23] Adding theme to active plugins sorted set
    5/3 11:01 [2536] - info: [2015/12/23] Adding theme to active plugins sorted set done!
    5/3 11:01 [2536] - info: [2016/01/14] Creating user best post sorted sets
    5/3 11:01 [2536] - info: processing pid: 5 uid: 2 votes: 2
    5/3 11:01 [2536] - info: processing pid: 7 uid: 4 votes: 1
    5/3 11:01 [2536] - info: processing pid: 17 uid: 2 votes: 1
    5/3 11:01 [2536] - info: [2016/01/14] Creating user best post sorted sets done!
    5/3 11:01 [2536] - info: [2016/01/20] Creating users:notvalidated
    5/3 11:01 [2536] - info: processing uid: 1 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 2 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 3 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 4 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 5 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 6 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 7 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 8 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 9 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 10 email:confirmed: null
    5/3 11:01 [2536] - info: processing uid: 11 email:confirmed: null
    5/3 11:01 [2536] - info: [2016/01/20] Creating users:notvalidated done!
    5/3 11:01 [2536] - info: [2016/01/23] Creating Global moderators group

    It stops here. I try several times, but it never moves forward.

    1
  • barisB

    Thanks for reporting, it should be fixed on master and 1.x.x.

    https://github.com/NodeBB/NodeBB/commit/7180174b91895c907991e29238ecb5822d5d7cb6
    https://github.com/NodeBB/NodeBB/commit/8f8fcc84168d424c7bdbf16ad4afae2cca36991c

    1
  • JenklerJ

    Safe to upgrade now?

    0
  • frissdiegurkeF

    @Jenkler You should always backup your data first. When a version is released it's always expected to be "safe to upgrade", it just doesn't work out each time. But without someone who tries to upgrade the devs won't find each edge case that may fail 😉

    0
  • JenklerJ

    I wanted to know if there was any known breaks at the moment 🙂 Backup is always needed! I will update my devs first.

    0

Suggested Topics

  • Adam CA

    Why is the user assigned the username with 0 at the end.

    General Discussion
    2
    0 Votes
    2 Posts
    60 Views
    barisB

    Yes, since groups and usernames can be mentioned with @<slug> it prevents duplicates in groupnames/usernames

  • Gus SurarezG

    Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3

    General Discussion
    1
    0 Votes
    1 Posts
    815 Views
    Gus SurarezG

    I work on nodebb 1.5.3 and accidentally made the grave mistake of installing a plugin using ACP and ended up losing all my development repos of non 'npm'ed plugins. At that point I decided to upgrade to latest 1.7.3 release since a fix (#6032) for this issue was supposed to be committed into that build. While I checked breaking change lists for 1.6.0 and 1.7.0, apparently I have over looked something since my list/grid topic-list show up all messed up (with no errors in console). I have a bootstrap based listview and gridview of the topics and I use JS code to select between them but now my page layout is gone like one of the libraries is not loading but I am not sure which one since I don't use anything other than jquery and bootstrap.I cannot figure this out but suspect it may be issue (#5980.) Any help would be appreciated and thank you in advance.

    Edit:

    I get the following error intermittently after several clicks and I am hoping to be related:

    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
    2017-12-31T06:55:43.950Z [1840] - error: /category/14/news
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
    2017-12-31T06:55:49.005Z [1840] - error: /category/14/news
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)

    ...
    some more errors I get after refreshes:

    2017-12-31T07:42:50.130Z [13716] - error: /category/5/general
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
    Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
    Script execution timed out.
    at ContextifyScript.Script.runInContext (vm.js:53:29)
    at ContextifyScript.Script.runInNewContext (vm.js:59:15)
    at Object.runInNewContext (vm.js:112:38)
    at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
    at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
    at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)

  • JenklerJ

    Latest stable v1.4.6

    General Discussion
    9
    0 Votes
    9 Posts
    2k Views
    JenklerJ

    Ok, so 1.5.x branch is stable to use. Is 1.x.x maintained for bugfixes only or just for history sake?

  • lombisiL

    1.0 Did stable version will be?

    General Discussion
    3
    0 Votes
    3 Posts
    1k Views
    julianJ

    @a_5mith Yes, soon... though you must remember, 1.0.0 is merely a number, and not a literal indicator of "work complete"!

  • R

    upgrade to 0.6.x issue

    General Discussion
    15
    0 Votes
    15 Posts
    9k Views
    wzrdtalesW

    @julian said:

    @priapo Keep in mind putting a socket.io section in config.json doesn't do anything 😄

    We had just talked about this configuration option short time ago in the issue 😄 so obviously it does affect. But "transports": ["polling","websocket"] is now the Standard.

    @priapo if you can't use the websockets you can set also "transports": ["polling"], then you will only get the failures for the long polling request which throws errors.

    I just tested by connecting directly without any proxy before NodeBB. The timeout disappears.

    So one failure source is that the timeout is higher than what is allowed by the proxy e.g. cloudflare. So an option to adjust the timeout would be great!

    The failure throwing which are left now are:

    GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766084670-12&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766094756-13&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766096635-23&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766106720-24&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766108697-34&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766118775-35&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766120692-45&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766130783-46&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request)
Copyright © 2023 NodeBB | Contributors