Join the conversation

Wekan

Bugs

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

More active conversations

Wekan / Bugs

Update recently? deleting

Wekan/Bugs · February 28, 2020 at 4:04pm

Update recently? deleting

Wekan / Bugs · February 28, 2020 at 4:04pm (Edited 5 years ago)

was there an update last evening or the day before?

deleting archived cards do not stay deleted. Refreshing screen and they return in the list of archived things to delete

HOW do you clear out all cards from the system not using the GUI? Its suddenly happening on all three systems with no code changes.

Can we roll back to the last version. THis is broken

other issues: when updating with new cards from the api looking at the contents of the new cards put the GUI into some sort of wait mode. Until you refresh the screen several times you get this behavior that indicates its not connecting to Mongo or something

In fact the deleting the archived boards works and on screen refresh they are still there seems like its never deleting from Mongo at all

Another hint: in addition to the GUI thinking the archived card is deleted and when you refresh its not, the webhooks are not being sent out when the delete happens. So it seems that the GUI is disconnected from the mongo and webhook piece entirely.

Question: in addition to rolling back the code, using snap installed wekan, what is the correct way to get into mongo shell under snap wekan? I can at least see what is in the database then and perhaps clear it out

LMK

more hints, I can't delete archived cards but I can restore them. When I do I cannot disable or remove webhooks associated

HOw do I get into wekan under snap mongo to clear these out?

Load previous messages

February 29, 2020 at 11:55am

Lauri Ojansivu@xet7

Team

11:55am

And for any bug, it needs minimal code example to reproduce bug

12:26pm

For example, someone recently reported that exporting one board did not work, when using Wekan Snap. Exporting other boards did work. He sent copy of that database to me, so I could test it. I noticed that with Wekan Docker version, it was possible to export that one board. The fix to Snap was to upgrade to newer version of Meteor, and then publish automatic Wekan Snap update.

12:26pm

I have no idea how exporting one board and version of Meteor is related to each other.

12:27pm

So in general, I care only about those bugs that can be reproduced.

12:27pm

Other bugs could come and go depending on status of each dependency.

12:30pm

I do trust worldwide community of all Wekan dependencies, that everything will improve. And if some dependency package does not work, I can switch it to some other dependency.

February 29, 2020 at 3:27pm

Paul Verdone@pvcon13

3:27pm

thanks. No I do not have some way of making it break (yet).

3:30pm

Question: if it was something to do with meteor, could I even fix it? Meaning would I be able to upgrade Meteor inside snap myself? I thought that the version of wekan was tied to a particular version at any given time of meteor and in turn Node.js? If I could upgrade would not the next automatic upgrade of wekan either overwrite that or get stuck if the version of node or meteor was newer? My issue is if I could figure out this does not mean that I could fix this long term, or are my assumptions wrong with that?

February 29, 2020 at 8:32pm

Paul Verdone@pvcon13

8:32pm

ok well the issue came back again

8:32pm

refreshing the gui in the browser and I see all the archived boards I deleted

8:33pm

where do I look for the actual errors again?

8:42pm

sudo snap logs wekan.wekan 2020-02-28T22:54:12Z wekan.wekan[30813]: > Starting add-description-title-allowed migration. 2020-02-28T22:54:12Z wekan.wekan[30813]: > Finishing add-description-title-allowed migration. 2020-02-28T22:54:12Z wekan.wekan[30813]: > Starting add-description-text-allowed migration. 2020-02-28T22:54:12Z wekan.wekan[30813]: > Finishing add-description-text-allowed migration. 2020-02-28T22:54:12Z wekan.wekan[30813]: Meteor APM: completed instrumenting the app 2020-02-28T22:54:15Z wekan.wekan[30813]: (node:365) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. 2020-02-28T22:54:43Z wekan.wekan[30813]: Exception while invoking method 'ATCreateUserServer' Error: getaddrinfo ENOTFOUND mailserver.examples.com 2020-02-28T22:54:43Z wekan.wekan[30813]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) 2020-02-28T22:56:15Z wekan.wekan[30813]: Exception while invoking method 'ATCreateUserServer' Error: getaddrinfo ENOTFOUND mailserver.examples.com 2020-02-28T22:56:15Z wekan.wekan[30813]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26)

8:42pm

at this point the gui is not stateful with the mongodb

8:42pm

do not see anything in the mongo logs

8:46pm

....

8:46pm

sudo snap logs wekan.wekan 2020-02-29T20:45:43Z wekan.wekan[30813]: at ns.Collection.remove (packages/mongo/collection.js:620:31) 2020-02-29T20:45:43Z wekan.wekan[30813]: at models/boards.js:1190:15 2020-02-29T20:45:43Z wekan.wekan[30813]: at Array.forEach (<anonymous>) 2020-02-29T20:45:43Z wekan.wekan[30813]: at boardRemover (models/boards.js:1188:62) 2020-02-29T20:45:43Z wekan.wekan[30813]: at Object.<anonymous> (models/boards.js:1394:5) 2020-02-29T20:45:43Z wekan.wekan[30813]: at packages/matb33collection-hooks.js:598:28 2020-02-29T20:45:43Z wekan.wekan[30813]: at Array.forEach (<anonymous>) 2020-02-29T20:45:43Z wekan.wekan[30813]: at Function..each._.forEach (packages/underscore.js:139:11) 2020-02-29T20:45:43Z wekan.wekan[30813]: at packages/matb33_collection-hooks.js:597:11 2020-02-29T20:45:43Z wekan.wekan[30813]: at Array.forEach (<anonymous>)

8:46pm

thats the same error I believe

8:48pm

do I need to look at anything in particular inside Mongo shell

8:59pm

I do not see anything in the mongo boards collection

8:59pm

at all

9:00pm

and I started with three boards, arched them and then deleted them

9:00pm

maybe ten times