Fork me on GitHub
#fulcro
<
2020-10-27
>
tony.kay01:10:44

I’m uploading a new release of the electron inspect binaries. Also, I’m probably going to push a release of the new inspect to the chrome store, at which point you will have to manually install the old chrome version from a local build if you need it.

tony.kay01:10:08

The current (soon to be old) version of the chrome-store extension can be found here if you needed it: https://github.com/fulcrologic/fulcro-inspect/releases/tag/1.0.21

cjmurphy02:10:08

Regarding the electron inspect binaries - no more .AppImage?

nivekuil02:10:15

I noticed the appimage was missing for a while last version too, but was available later

cjmurphy03:10:11

Oh I see. Yeah probably a bit of a process to create it. Thanks @U797MAJ8M

tony.kay03:10:46

on limited bw, and didn’t know if anyone used it 🙂

tony.kay03:10:58

easy to create from source and DEVELOPMENT.md instructions, btw

cjmurphy11:10:36

Could not find electron-builder or eletron-builder as you can see.

tony.kay16:10:01

uploading the image now

cjmurphy18:10:20

Anyone that runs Arch or Manjaro linux will want. People that work at Juxt for instance all have machines running Arch linux.

cjmurphy19:10:37

The new file has the same name (not surprising) and size (slightly worrying) as the previous .AppImage. It runs fine but still has the UNSUPPORTED VALUE problem. Maybe @U797MAJ8M can verify?

nivekuil21:10:06

In reply to @￱￱slack￱￱￱￱￱￱t03￱￱r￱￱z￱￱g￱￱p￱￱f￱￱r=2d￱￱u0￱￱d5￱￱r￱￱n0￱_￱s1:nivekuil.comThe new file has the same name (not surprising) and size (slightly worrying) as the previous .AppImage. It runs fine but still has the UNSUPPORTED VALUE problem. Maybe kevin842 can verify?size between 3.0.1 and 3.0.0-3 looks different to me

nivekuil21:10:12

In reply to @.:nivekuil.comsize between 3.0.1 and 3.0.0-3 looks different to medon't know about the bug

nivekuil21:10:24

In reply to @.:nivekuil.comdon't know about the bugnor is it the same name, new one is called fulcro-inspect-electron-3.0.1.AppImage

cjmurphy23:10:48

AFAIK 3.0.1 is all that there is. The first 3.0.1 had the bug in it and the second 3.0.1 is supposed to have fixed the bug. 3.0.0-3 is fine, but is from a month ago.

nivekuil23:10:39

In reply to @￱￱slack￱￱￱￱￱￱t03￱￱r￱￱z￱￱g￱￱p￱￱f￱￱r=2d￱￱u0￱￱d5￱￱r￱￱n0￱_￱s1:nivekuil.comAFAIK 3.0.1 is all that there is. The first 3.0.1 had the bug in it and the second 3.0.1 is supposed to have fixed the bug. 3.0.0-3 is fine, but is from a month ago.huh, I thought 3.0.0-3 was the latest for the electron build. I don't see any prior 3.0.1 release on github unless tony deleted it for some reason

nivekuil00:10:10

well, actually I only see one 3.0.1 tag based off b70e1bf which includes the fix?

cjmurphy00:10:28

You are right. From my tests both 3.0.1 and the prior 3.0.0-3 have the problem. I was wrong to think there were ever two of 3.0.1.

tony.kay01:10:40

I thought I got all the places where it was doing that…let me look

tony.kay02:10:17

@U0D5RN0S1 could you try the new app image and let me know if that fixes it. If so, I’ll upload the other images.

cjmurphy03:10:10

Now I can see them: #fulcro/tempid["a6615b79-68e8-4604-99e1-f5b28ea92ad6"]. So all good thanks Tony 🙂

tony.kay03:10:58

great, thanks for checking

tony.kay03:10:20

I’ll upload the other variants