| [06:54:32] | <tool172[m]> | ACTION uploaded an image: (14KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/YEpGgvRMoLZ... > |
| [06:54:39] | <tool172[m]> | any idea why this is hanging? |
| [07:00:48] | <tool172[m]> | i'm using mysql to mysql to new database and separate install in apache24. Initial migration looked fine until it failed and then i rolled back and this is what is happening |
| [07:26:01] | <mstenta[m]> | You can check error messages with: |
| [07:26:41] | <mstenta[m]> | drush migrate:messages [migration-id] |
| [07:26:49] | <mstenta[m]> | That should give you a clue |
| [11:12:13] | <mstenta[m]> | Hey all FYI: I won't be able to attend today's dev call. |
| [12:15:17] | * farmBOT has joined #farmos |
| [15:46:38] | <mstenta[m]> | symbioquine: whoa what are we looking at in your two most recent comments? https://farmos.discourse.group/t/asset-link-dev-log/1175/5 |
| [15:59:47] | <symbioquine[m]> | Rough UI for managing/authoring plugins and plugin lists... |
| [16:00:31] | <symbioquine[m]> | That page itself is implemented as a plugin - a single-file Vue.js component. |
| [16:00:39] | <mstenta[m]> | Interesting |
| [16:00:44] | <mstenta[m]> | Authoring?? |
| [16:02:44] | <symbioquine[m]> | Yeah, first pass will just be a light weight text editor for plugin code, but it should be pretty easy to also allow authoring "code-less plugins". |
| [16:03:24] | <mstenta[m]> | Whoa |
| [16:05:46] | <symbioquine[m]> | Plugins can be grouped together into a "plugin list" and loaded via a Url so a collection of conventions codified via plugins could be shared in a semi-peer-to-peer manner - assuming the "manage plugins plugin" is loaded. |
| [16:07:04] | <mstenta[m]> | That's awesome |
| [16:07:15] | <mstenta[m]> | Where do plugins get stored? |
| [16:07:24] | <mstenta[m]> | On client? Server? |
| [16:07:39] | <symbioquine[m]> | It would normally come from the farmOS server itself via the default plugin list which is managed by the site admin so that ad-hoc plugin sharing could be discouraged if a site admin so chose. |
| [16:07:47] | <symbioquine[m]> | Both |
| [16:08:09] | <mstenta[m]> | Cool! |
| [16:08:31] | <mstenta[m]> | Yea some security considerations with URL sharing :-) |
| [16:08:56] | <symbioquine[m]> | They're normally loaded from a server, but you could author one locally and it would only be in your browser storage until you upload it somewhere. |
| [16:09:08] | <symbioquine[m]> | mstenta[m]: Of course |
| [16:09:09] | <mstenta[m]> | curl | sudo sh :-P |
| [16:09:29] | <mstenta[m]> | That'll be super useful though! |
| [16:09:46] | <mstenta[m]> | Oh very neat |
| [16:09:54] | <symbioquine[m]> | Planning on some warnings when loading plugins from third party domains. |
| [16:10:03] | <mstenta[m]> | I still need to wrap my head around what makes up a plugin |
| [16:13:53] | <symbioquine[m]> | I just chose "plugin" so it wouldn't overlap so much with "farmOS modules" - though a farmOS module could "provide" a "Asset Link plugin" and make it available to be served as part of the default plugin list. |
| [16:53:34] | <tool172[m]> | Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY000]: General error: 1093 You can't specify target table 'taxonomy_term_revision' for update in FROM clause: UPDATE taxonomy_term_revision SET revision_log_message = :revision_log_message WHERE revision_id IN ( SELECT r.revision_id FROM "migrate_map_farm_migrate_taxonomy_log_category" mm INNER JOIN taxonomy_term_revision r ON mm.destid1 = r.tid ); Array ( [:revision_log_message] => |
| [16:53:34] | <tool172[m]> | Migrated from farmOS 1.x on 2022-04-14 ) in Drupal\farm_migrate\EventSubscriber\FarmMigrationSubscriber->addRevisionLogMessage() (line 348 of /usr/local/www/farmOS/web/profiles/farm/modules/core/migrate/src/EventSubscriber/FarmMigrationSubscriber.php). |
| [16:53:36] | <tool172[m]> | hmmmmm |
| [16:54:06] | <mstenta[m]> | Ooohhhh right. |
| [16:54:29] | <mstenta[m]> | That's a bug we discovered a little while ago with MySQL migrations |
| [16:54:30] | <mstenta[m]> | There's an open issue for it |
| [16:54:38] | <tool172[m]> | ahh |
| [16:54:47] | <mstenta[m]> | All the migration testing was done against PostgreSQL :-/ |
| [16:54:47] | <tool172[m]> | :) |
| [16:54:48] | <tool172[m]> | well then I shall relax |
| [16:55:09] | <mstenta[m]> | If I recall, you can comment out one line to work around it |
| [16:55:28] | <tool172[m]> | i'm migrating this whole thing to docker on a postgres instance |
| [16:55:30] | <mstenta[m]> | Search the GitHub issue queue for MySQL migration. You should find it |
| [16:55:42] | <tool172[m]> | from mysql |
| [16:56:02] | <mstenta[m]> | Oh I thought you said earlier you are migrating into MySQL |
| [16:56:12] | <tool172[m]> | so it's on mysql right now |
| [16:56:23] | <mstenta[m]> | Sorry not at my computer right now... Will check back later |
| [16:56:23] | <tool172[m]> | i'm moving to a subserver (dell optiplex) to take the load off my NAS |
| [16:56:35] | <mstenta[m]> | Ok MySQL -> PostgreSQL is well tested |
| [16:56:47] | <tool172[m]> | i'm still learning docker is my issue :) |
| [16:57:02] | <tool172[m]> | i looked at sequines guide but the transfer is a PITA |
| [16:57:14] | <tool172[m]> | i might spinup a VM postgres instance and then copy it over |
| [16:57:15] | <tool172[m]> | and boot it up |
| [16:57:16] | <tool172[m]> | thx |
| [17:02:02] | <mstenta[m]> | That error definitely looks like the same one someone else reported though |
| [17:02:38] | <mstenta[m]> | https://github.com/farmOS/farmOS/issues/506 |
| [17:03:29] | <mstenta[m]> | See this bit: |
| [17:03:35] | <mstenta[m]> | > As a temporary workaround, if you don't mind losing that message, you can disable that by commenting out this line: |
| [17:03:45] | <tool172[m]> | i'm reading it. Thank you! as always your on top of the project |
