IRC logs for #farmOS, 2022-08-24 (GMT)

2022-08-23
2022-08-25
TimeNickMessage
[20:04:36]* farmBOT has joined #farmos
[03:06:38]<FarmerEd[m]>0.5.4 works with the VM instance upgraded to Beta6
[09:05:03]<symbioquine[m]><FarmerEd[m]> "0.5.4 works with the VM instance..." <- That's awesome
[09:05:53]<symbioquine[m]>I'm still curious to know why it wasn't working on your other setup though.
[09:29:02]<FarmerEd[m]>Yea, its a bit weird.
[09:29:02]<FarmerEd[m]>Apart from architecture, setup "should" be more or less the same for both except I have to access the Pi through a router using forwarding for port 443.
[09:29:46]<symbioquine[m]>> <@farmer-ed:matrix.org> Yea, its a bit weird.
[09:29:46]<symbioquine[m]>> Apart from architecture, setup "should" be more or less the same for both except I have to access the Pi through a router using forwarding for port 443.
[09:29:46]<symbioquine[m]>That should be fine
[09:30:15]<symbioquine[m]>If the page is loading, I wouldn't expect the TCP/IP layer to give us any trouble.
[09:30:31]<FarmerEd[m]>I'd have thought so too, just looking for differences........... or grasping at straws
[09:30:41]<symbioquine[m]>yeah
[09:30:53]<FarmerEd[m]>besides, no 404's
[09:31:49]<symbioquine[m]>Asset Link should periodically make requests to `/api` as one of the ways it checks connectivity. I guess I'd start there...
[09:32:10]<symbioquine[m]>Your screenshot showed that it didn't think it could connect to farmOS, so I'd expect some sort of issue with those requests.
[09:32:30]<symbioquine[m]>* checks connectivity (and logged-in-ness). I
[09:35:14]<FarmerEd[m]>yea, not logged-in-ness is bogey too. throws a 403 in console but nothing shown in app
[09:35:40]<symbioquine[m]>huh
[09:36:16]<FarmerEd[m]>the other system shows an orange banner as expected
[09:36:39]<mstenta[m]>CORS? self-signed certificate? session cookie not being shared?
[09:36:48]<mstenta[m]>not really following - just throwing out ideas ... :-)
[09:37:05]<FarmerEd[m]>self signed on the one that works
[09:37:38]<FarmerEd[m]>lets encrypt on the one that isn't
[09:38:01]<symbioquine[m]>> CORS
[09:38:02]<symbioquine[m]>Should be the same origin since Asset Link runs under the same domain
[09:38:08]<mstenta[m]>yea that's what i was thinking too...
[09:38:23]<mstenta[m]>it would show an error in console if it were related to cors
[09:38:30]<symbioquine[m]>yeah
[09:41:09]<symbioquine[m]>This is how Asset Link does the online/offline/logged-in-ness detection: https://github.com/symbioquine/farmOS_asset_link/blob/345b0fc69cc310f2c1...
[09:45:59]<FarmerEd[m]>I just have to feed the little people, be back shortly.
[10:13:21]<FarmerEd[m]>ah
[10:13:46]<FarmerEd[m]> if (farmOsVersion !== '2.x') {
[10:13:47]<FarmerEd[m]> this.canReachFarmOS.value = false;
[10:13:47]<FarmerEd[m]> return;
[10:14:25]<FarmerEd[m]>working one from API "version": "2.x",
[10:15:02]<FarmerEd[m]>not working one from API "version": "2.0.0-beta6",
[10:15:10]<symbioquine[m]>Ah :(
[10:15:45]<symbioquine[m]>Maybe there should be a "nominalVersion" field :)
[10:15:45]<mstenta[m]>nice detective work Farmer Ed !
[10:16:09]<mstenta[m]>or maybe a regex ("starts with 2")
[10:16:18]<mstenta[m]>(assuming it's just to prevent v1)
[10:16:19]<symbioquine[m]>yeah...
[10:18:57]<FarmerEd[m]>mstenta[m]: Obviously spending far too much time at my computer these days 🤓
[10:19:30]<symbioquine[m]>Thanks for tracking that one down!
[10:20:18]<symbioquine[m]>I guess it goes to show that it's worth testing against the actual releases sometimes - not just recent dev versions :)
[10:22:54]<FarmerEd[m]>It's an interesting one all right
[10:22:54]<FarmerEd[m]>At least the version check works, maybe "Unsupported Version" should be displayed instead of "farmOS unreachable"
[10:23:19]<symbioquine[m]>> <@farmer-ed:matrix.org> It's an interesting one all right
[10:23:19]<symbioquine[m]>> At least the version check works, maybe "Unsupported Version" should be displayed instead of "farmOS unreachable"
[10:23:19]<symbioquine[m]>Yeah, I think you're right
[10:23:29]<FarmerEd[m]>* maybe "Unsupported farmOS Version" should
[10:24:45]<symbioquine[m]>I'd been thinking about that check like "Well, we got some JSON data, but don't really know what we're talking to..."
[10:26:40]<symbioquine[m]>farmOS 1.x returns a 404 for that URL
[10:27:00]<mstenta[m]>ah yea
[10:28:19]<symbioquine[m]>I didn't feel like going backwards and putting in logic specifically for detecting 1.x - especially since I doubt the module would even install there.
[10:29:38]<symbioquine[m]>The main reason that kind of check exists is for detecting network/proxy issues that might still return JSON
[10:30:34]<symbioquine[m]>Which admittedly is a bit of a longshot
[10:30:44]<mstenta[m]>makes sense
[10:33:26]<FarmerEd[m]>Maybe "farmOS version check failed"
[10:34:00]<FarmerEd[m]>Or "unexpected JSON"
[10:35:13]<symbioquine[m]>Yeah, I'll put in some sort of explanation
[10:39:13]<FarmerEd[m]>I only recently started tagging the ARM64 images correctly with the version, a few weeks ago it would have worked.
[10:39:36]<FarmerEd[m]>* have worked anyway.
[11:13:49]<FarmerEd[m]>Maybe to logic needs a bit of rework too, as the banner to inform me of not being logged in was also suppressed. It kind of makes sense for "farmOS unreachable" but perhaps not if you change that message.
[11:15:36]<symbioquine[m]>The login status check happens after the check for whether we're talking to a farmOS server
[11:21:35]<FarmerEd[m]>Which makes sense I suppose and unimportant if your new message is clear. (Don't mind me so)
[19:40:34]* evered[m] has joined #farmos