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 28, 2020 at 8:32pm

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

    • reply
    • like

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

      • reply
      • like

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

        • reply
        • like

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

          • reply
          • like

          then I archive and delete the cards

            • reply
            • like

            and I see and track the deletions via the web hooks

              • reply
              • like

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

                Edited
                • reply
                • like

                on three systems

                  • reply
                  • like

                  since yesterday

                    • reply
                    • like

                    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

                      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

                        I'm thinking, that some part of Wekan or Meteor code gets confused here. Meteor has optimistic updates, so changes are not immediate, but happen sometime later. Some other Wekan contributor at IRC also found this and asked about this, so that there would be blinking status dot while data is not yet saved to database. But 90 minutes is too long. Some of the code changes Wekan makes can be immediate. I'll probably try to figure out can this be fixed, or should I replace some part of Wekan backend.

                          • reply
                          • like

                          I think, that when you are making many changes with code, that code most likely would expect everything happens immediately.

                            • reply
                            • like

                            yeah BUT

                              • reply
                              • like

                              until today there were no issues at all with the expectations of data state

                                • reply
                                • like

                                something changed recently for me

                                  • reply
                                  • like

                                  before today when I deleted in the wekan GUI there was a delay between 3 second and 20 seconds

                                    • reply
                                    • like

                                    now its not changing after repeated attempts

                                      • reply
                                      • like

                                      the kicker is that refreshing the screen of the gui shows all deleted boards not deleted at all

                                        • reply
                                        • like

                                        and at any time after that reinstating that board works

                                          • reply
                                          • like

                                          Is your Wekan install exposed to Internet?

                                            • reply
                                            • like

                                            or is it at internal network

                                              • reply
                                              • like

                                              I'm just thinking, has someone made some DDoS

                                                • reply
                                                • like

                                                its internal but I have access through ssl through one part address

                                                  • reply
                                                  • like

                                                  no my logs are clean

                                                    • reply
                                                    • like