Join the conversation

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

Wekan

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

Wekan / Bugs

Update recently? deleting

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 3:27pm

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

    • reply
    • like

    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?

      • reply
      • like

      February 29, 2020 at 8:32pm

      ok well the issue came back again

        • reply
        • like

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

          • reply
          • like

          where do I look for the actual errors again?

            • reply
            • like

            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)

              • reply
              • like

              at this point the gui is not stateful with the mongodb

                • reply
                • like

                do not see anything in the mongo logs

                  • reply
                  • like

                  ....

                    • reply
                    • like

                    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>)

                      • reply
                      • like

                      thats the same error I believe

                        • reply
                        • like

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

                          • reply
                          • like

                          I do not see anything in the mongo boards collection

                            • reply
                            • like

                            at all

                              • reply
                              • like

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

                                • reply
                                • like

                                maybe ten times

                                  • reply
                                  • like

                                  each time I went and looked by refreshing the browser

                                    • reply
                                    • like

                                    after 40 minutes they started to not be reported

                                      • reply
                                      • like

                                      down to only one now

                                        • reply
                                        • like

                                        tried to delete it now

                                          • reply
                                          • like

                                          will not go away

                                            • reply
                                            • like

                                            maybe in another half and hour

                                              • reply
                                              • like

                                              how would you like me to test or trouble shoot this?

                                                • reply
                                                • like

                                                LMK thanks

                                                  • reply
                                                  • like

                                                  OH

                                                    • reply
                                                    • like