Database migration chokes on huge value of a "calendar-details" item in table "post_custom_fields"

Dear Rafael,

I can confirm the Discourse Calendar plugin indeed has been the culprit here, so I will adjust the title of this post accordingly. FWIW, I am also sharing our current plugin list. With these plugins installed (and discourse-calendar deactivated), the database migration task succeeded just fine and the forum is up and running again – https://community.panodata.org/.

  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-translator.git
          - git clone https://github.com/discourse/discourse-checklist.git
          - git clone https://github.com/discourse/discourse-assign.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-math.git
          - git clone https://github.com/angusmcleod/discourse-tickets.git
          - git clone https://github.com/angusmcleod/discourse-knowledge-base.git
          - git clone https://github.com/angusmcleod/discourse-locations.git
          - git clone https://github.com/discourse/discourse-footnote.git
          - git clone https://github.com/discourse/discourse-graphviz.git
          - git clone https://github.com/angusmcleod/discourse-custom-wizard.git
          - git clone https://github.com/discourse/discourse-sitemap.git
          - git clone https://github.com/angusmcleod/discourse-events.git

#          - git clone https://github.com/discourse/discourse-calendar.git

Thank you so much, keep up the spirit and with kind regards,
Andreas.

P.S.: How should we proceed on filing a bug against discourse-calendar, if that might be appropriate?