Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

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

Update recently? deleting

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

Paul Verdone

@pvcon13
rep
1.5k

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 28, 2020 at 8:29pm
Paul Verdone@pvcon13
8:29pm

mongo is obvious

    • reply
    • like
    8:29pm

    mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:26Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:31Z mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:31Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:36Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:36Z mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:41Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:41Z mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:46Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:46Z mongod.2701

      • reply
      • like
      8:29pm

      wekan logs are more confusing

        • reply
        • like
        8:30pm

        I think there may be errors in wekan logs

          • reply
          • like
          8:30pm

          here

            • reply
            • like
            Lauri Ojansivu@xet7
            Team
            8:30pm

            that received client metadata is normal MongoDB message, it is not an error

              • reply
              • like
              Paul Verdone@pvcon13
              8:30pm

              root@ip-172-31-35-186:/snap/wekan/747/programs/server/packages# sudo snap logs wekan.wekan 2020-02-28T20:11:33Z wekan.wekan[23840]: at ns.Collection.remove (packages/mongo/collection.js:620:31) 2020-02-28T20:11:33Z wekan.wekan[23840]: at models/boards.js:1190:15 2020-02-28T20:11:33Z wekan.wekan[23840]: at Array.forEach (<anonymous>) 2020-02-28T20:11:33Z wekan.wekan[23840]: at boardRemover (models/boards.js:1188:62) 2020-02-28T20:11:33Z wekan.wekan[23840]: at Object.<anonymous> (models/boards.js:1394:5) 2020-02-28T20:11:33Z wekan.wekan[23840]: at packages/matb33collection-hooks.js:598:28 2020-02-28T20:11:33Z wekan.wekan[23840]: at Array.forEach (<anonymous>) 2020-02-28T20:11:33Z wekan.wekan[23840]: at Function..each._.forEach (packages/underscore.js:139:11) 2020-02-28T20:11:33Z wekan.wekan[23840]: at packages/matb33_collection-hooks.js:597:11 2020-02-28T20:11:33Z wekan.wekan[23840]: at Array.forEach (<anonymous>)

                • reply
                • like
                8:31pm

                yeah that is

                  • reply
                  • like
                  8:31pm

                  sudo snap logs wekan.wekan sudo snap logs wekan.mongodb

                    • reply
                    • like
                    8:31pm

                    as you requested

                      • reply
                      • like
                      8:31pm

                      I believe there is a breaking between mongo from wekan node.js

                        • reply
                        • like
                        Lauri Ojansivu@xet7
                        Team
                        8:32pm

                        Hmm, why it would try to remove Collection?

                          • reply
                          • like
                          8:32pm

                          That is strange

                            • reply
                            • like
                            Paul Verdone@pvcon13
                            8:32pm

                            yeah

                              • reply
                              • like
                              Lauri Ojansivu@xet7
                              Team
                              8:32pm

                              It would be like removing table from database. That does not make sense.

                                • reply
                                • like
                                8:33pm

                                I'll look at what is at those lines of code

                                  • reply
                                  • like
                                  Paul Verdone@pvcon13
                                  8:33pm

                                  I use api to create cards with members with webhook with list with cards

                                    • reply
                                    • like
                                    8:33pm

                                    then I move the cards around in wekan and capture the web hooks

                                      • reply
                                      • like
                                      8:34pm

                                      then I archive and delete the cards

                                        • reply
                                        • like
                                        8:34pm

                                        and I see and track the deletions via the web hooks

                                          • reply
                                          • like
                                          8:34pm

                                          what I see is the archives working, the deletes and the webhooks not working

                                            Edited
                                            • reply
                                            • like
                                            8:34pm

                                            on three systems

                                              • reply
                                              • like
                                              8:34pm

                                              since yesterday

                                                • reply
                                                • like
                                                8:35pm

                                                I do development on the api but only on the dev system, so there is nohthing new in terms of api access or data change in staging and production

                                                  • reply
                                                  • like
                                                  8:42pm

                                                  again to be clear I have a recursive routine that sends command to wekan and captures the data it returns and calls itself (so it always has the ids It needs, First step: for each board create a board, then capture board id and default swimlane, add a member, add a webhook,and then for each column add a list element, for each each task add a card into list column zero, then do the second board rinse and repeat, putting all these returned id into my database. After that everythin is dragging the cards ONLY round and when done, first archiving and then deleting the board. each time I move or delete I get the webhook and modify my database and send out notification to clients

                                                    Edited
                                                    • reply
                                                    • like