| [22:29:17] | * farmBOT has joined #farmos |
| [05:00:10] | * Noaht[m] has quit (Quit: You have been kicked for being idle) |
| [08:41:25] | * Mo[m] has joined #farmos |
| [09:59:54] | <mstenta[m]> | paul121 symbioquine Looking at recent GitHub Actions workflow runs... the MariaDB issue hasn't occurred in 16 days (same in both origin and my fork) - I wonder if it was a GitHub issue and they fixed it? |
| [10:04:18] | <symbioquine[m]> | Maybe something buried in [here](https://github.com/actions/runner/issues?q=is%3Aissue) got fixed...? |
| [10:04:44] | <mstenta[m]> | Hope so! glad I didn't spend more time on it :-) |
| [11:07:49] | <symbioquine[m]> | The [default_content module](https://www.drupal.org/project/default_content) is pretty nice btw! I'm having good results so far using it to capture test data for Asset Link... |
| [11:08:06] | <mstenta[m]> | Cool! I have yet to try it out myself |
| [13:29:32] | <botlfarm[m]> | I ran into an issue in my production environment and now things are broken. When creating a log I accidentally ended up adding a group to itself.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/b4779389ac...) |
| [13:31:27] | <mstenta[m]> | Oh there's supposed to be some logic to prevent a circular group membership - maybe you found a way around that. 😅 |
| [13:31:59] | <mstenta[m]> | Did you try clearing your cache? I wonder if that would fix the Views... |
| [13:32:58] | <botlfarm[m]> | Just tried that with no luck. |
| [13:32:58] | <mstenta[m]> | Deleting the log should be all that's needed, but it may have cached something odd somewhere. |
| [13:33:10] | <mstenta[m]> | Hmm - are you able to get to /admin/reports/dblog? |
| [13:34:25] | <botlfarm[m]> | TypeError: Argument 1 passed to Drupal\views\Plugin\views\field\BulkForm::getEntityTranslation() must implement interface Drupal\Core\Entity\EntityInterface, null given, called in /opt/drupal/web/core/modules/views/src/Plugin/views/field/BulkForm.php on line 291 in Drupal\views\Plugin\views\field\BulkForm->... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/9936f40a74...) |
| [13:35:05] | <mstenta[m]> | Did you use `drush cr` to clear the cache? |
| [13:36:26] | <botlfarm[m]> | No, I used admin/config/development/performance "clear all caches" |
| [13:36:43] | <mstenta[m]> | OK - I wonder if that misses the Views cache or something - are you able to try `drush cr`? |
| [13:38:35] | <botlfarm[m]> | Ok, I just tried that still with the same result |
| [13:38:55] | <mstenta[m]> | Hmm |
| [13:40:33] | <botlfarm[m]> | worst case I have a back up from this morning I can revert to, but I have done a lot of record inputting today. |
| [13:40:36] | <mstenta[m]> | Were any other entities created besides that one log? Re-reading your description... |
| [13:41:06] | <botlfarm[m]> | just the 1 group and the 1 log |
| [13:41:27] | <mstenta[m]> | And the group works? But doesn't have any members? |
| [13:43:08] | <botlfarm[m]> | the group works fine. It shows me all the assets I added with that log that hsould have bene deleted |
| [13:43:09] | <botlfarm[m]> | hmm |
| [13:43:27] | <botlfarm[m]> | it does not show itself at this point, but also has no logs associated with it |
| [13:43:44] | <mstenta[m]> | oh... so there may still be a log |
| [13:43:46] | <mstenta[m]> | ? |
| [13:44:26] | <mstenta[m]> | hmm... this is a random thing to try but... |
| [13:44:30] | <mstenta[m]> | `drush cron` |
| [13:44:49] | <mstenta[m]> | (i have a hypothesis, but it feels unlikely) |
| [13:45:03] | <mstenta[m]> | and then also do `drush cr` after that again |
| [13:45:13] | <mstenta[m]> | just to be sure :-) |
| [13:45:44] | <botlfarm[m]> | still the same |
| [13:45:56] | <mstenta[m]> | k - not surprised.. hmm |
| [13:46:25] | <mstenta[m]> | for what it's worth, i've found some drupal core issues with this same error message |
| [13:46:36] | <botlfarm[m]> | looking back at the debug logs I see where the log was deleted "/log/28547/delete" |
| [13:46:47] | <botlfarm[m]> | and if I go back to that log directly it cant be found |
| [13:46:56] | <mstenta[m]> | ok |
| [13:47:50] | <mstenta[m]> | general question: have you made any customizations to the `farm_log` View? |
| [13:49:09] | <botlfarm[m]> | no, I don't think I have made and customizations in 2.x yet |
| [13:49:20] | <mstenta[m]> | ok - can you try this: |
| [13:49:26] | <mstenta[m]> | `drush en config_update_ui` |
| [13:49:58] | <mstenta[m]> | then go to /admin/config/development/configuration/report/module/farm_ui_views |
| [13:50:25] | <mstenta[m]> | under "Changed configuration items" it should say "None: no active configuration items differ from their current provided versions." |
| [13:50:43] | <botlfarm[m]> | yep, thats what I see |
| [13:50:45] | <mstenta[m]> | k |
| [13:51:05] | <mstenta[m]> | so my hunch is still that this is a caching issue... somehow |
| [13:51:36] | <botlfarm[m]> | that is what it seems like |
| [13:52:17] | <mstenta[m]> | we could go into the database directly and poke around... not sure how easy that is on your end |
| [13:52:44] | <mstenta[m]> | another idea i might try is deleting and re-importing that View - but that could cause other issues (so i would definitely backup first) |
| [13:53:15] | <botlfarm[m]> | im not super comfortable with database stuff just because im not real familiar with it. |
| [13:53:32] | <mstenta[m]> | ok let's try deleting/recreating that View... can you take a database backup first? |
| [13:53:43] | <botlfarm[m]> | yep |
| [13:53:43] | <mstenta[m]> | i'll test out the drush commands on my end |
| [13:53:59] | <mstenta[m]> | (to make sure it doesn't blow anything else up) |
| [13:54:53] | <botlfarm[m]> | I also have not updated to the new beta yet. woudl that clear enough of the catch to maybe fix it? |
| [13:55:04] | <botlfarm[m]> | if i did the update now |
| [13:55:29] | <mstenta[m]> | just to keep things simpler |
| [13:55:30] | <mstenta[m]> | hmm i'd say it's safer to fix this first |
| [13:55:56] | <botlfarm[m]> | ok |
| [13:57:58] | <mstenta[m]> | ok let's try this |
| [13:58:35] | <mstenta[m]> | this will delete the View: `drush config:delete views.view.farm_log` |
| [13:58:49] | <mstenta[m]> | after that, go back to /admin/config/development/configuration/report/module/farm_ui_views |
| [13:58:59] | <mstenta[m]> | the View should be listed under "missing configuration items" with a button to import it |
| [13:59:37] | <mstenta[m]> | that will recreate the view |
| [13:59:43] | <mstenta[m]> | maybe that will fix the cache? |
| [14:00:18] | <botlfarm[m]> | no luck :( |
| [14:00:26] | <mstenta[m]> | dang |
| [14:01:59] | <mstenta[m]> | well i think the next thing i would want to do is dig through the DB and see if there's something wrong |
| [14:02:14] | <mstenta[m]> | if something didn't get deleted properly, perhaps (can't think how that would happen - but running out of ideas) |
| [14:03:38] | <mstenta[m]> | > worst case I have a back up from this morning I can revert to, but I have done a lot of record inputting today. |
| [14:03:38] | <mstenta[m]> | or you do this... but if it's a lot of records then i'd want to avoid having to re-input |
| [14:04:04] | <botlfarm[m]> | Where would starting place for this log be in the db? or is it not that simple |
| [14:04:41] | <mstenta[m]> | actually another idea... |
| [14:04:47] | <mstenta[m]> | go to /admin/structure/views/view/farm_log |
| [14:06:19] | <mstenta[m]> | expand the "Advanced" column on the right, and next to "Caching" click "Tag based" - set it to "None", click "Apply (all displays)", then scroll down and click "Save" for the View as a whole |
| [14:06:34] | <mstenta[m]> | (you need the `views_ui` module enabled to get to that page - `drush en views_ui`) |
| [14:08:03] | <botlfarm[m]> | same error |
| [14:08:14] | <mstenta[m]> | wow |
| [14:09:02] | <mstenta[m]> | thinking... |
| [14:11:19] | <mstenta[m]> | can you run SQL queries? |
| [14:13:46] | <botlfarm[m]> | I think I can if i work inside the db container |
| [14:13:53] | <mstenta[m]> | ok |
| [14:14:04] | <mstenta[m]> | I'll send you a PM - so we don't clutter this room too much |
| [14:50:44] | * AnasHaddad[m] has quit (Ping timeout: 248 seconds) |
| [14:50:44] | * ThimmZwiener[m] has quit (Ping timeout: 248 seconds) |
| [14:50:44] | * eddieironsmith[m has quit (Ping timeout: 248 seconds) |
| [14:51:19] | <mstenta[m]> | update in case anyone is curious... we fixed it :-) |
| [15:02:24] | * AnasHaddad[m] has joined #farmos |
| [15:02:56] | * ThimmZwiener[m] has joined #farmos |
| [15:03:52] | * eddieironsmith[m has joined #farmos |
| [16:22:55] | <mstenta[m]> | @room I published some ideas (and a draft git repo) with some ideas for documenting "farmOS conventions" https://farmos.discourse.group/t/documenting-conventions/1263 |
| [16:23:16] | <mstenta[m]> | Would love to hear everyone's thoughts! |
| [16:23:32] | <mstenta[m]> | And maybe talk about it on the monthly call tomorrow if we have time |
| [16:33:58] | <FarmerEd[m]> | Is this workflow conventions? |
| [16:33:58] | <FarmerEd[m]> | Won't these vary vastly from farm to farm. Are you looking to document a single standard convention or multiple examples? |
| [16:35:23] | <mstenta[m]> | so... yes, yes, and yes. |
| [16:35:43] | <mstenta[m]> | the idea is: everyone might start with different conventions for different types of data recording in farmOS, but over time we can share and converge on some standards |
| [16:35:56] | <mstenta[m]> | to encourage more comparability |
| [16:36:12] | <mstenta[m]> | not a hard requirement by any means - and there will always be the same level of flexibility we have now |
| [16:36:38] | <mstenta[m]> | and there are some easy ones we can start with |
| [16:37:09] | <mstenta[m]> | but if, for example, you have your own convention, and wanted to document it - you could follow the same pattern and version it yourself in your own repo |
| [16:37:11] | <FarmerEd[m]> | Actually just seen your new post on the forum, I like the convention ID idea |
| [16:37:29] | <mstenta[m]> | and if you wanted to propose it for inclusion as a standard, it could go through a pull request process to be merged upstream |
| [16:39:38] | <mstenta[m]> | basically proposing a more formal process to what we do already, documented in versioned markdown files :-) |
| [16:39:58] | <FarmerEd[m]> | Ok, it's interesting, honestly I could probably do with seeing some convention ideas myself, still trying to figure out much of my own |
| [16:40:06] | <mstenta[m]> | take a look at the soil test example: https://github.com/mstenta/farmOS-conventions/blob/wip/docs/soil-test/in... |
| [16:40:12] | <mstenta[m]> | (still a work in progress) |
| [16:43:13] | <FarmerEd[m]> | Yea, that's pretty cool actually, could be particularly useful for regional stuff too where farms may have to record certain data in a certain way for various quality assurance schemes. |
| [16:43:25] | <mstenta[m]> | yea! good idea! |
| [16:43:43] | <mstenta[m]> | perhaps that could be part of the ID namespacing potentially |
| [16:43:48] | <FarmerEd[m]> | Exactly |
| [16:52:26] | <mstenta[m]> | Let's continue the convo in the forum! :-) https://farmos.discourse.group/t/documenting-conventions/1263 |