Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated to v1.15.3 #52

Closed
wants to merge 15 commits into from
Closed

updated to v1.15.3 #52

wants to merge 15 commits into from

Conversation

muelli
Copy link
Collaborator

@muelli muelli commented Mar 18, 2021

No description provided.

@flathubbot
Copy link

Started test build 42115

@flathubbot
Copy link

Build 42115 failed

@flathubbot
Copy link

Started test build 42117

@flathubbot
Copy link

Started test build 42118

@flathubbot
Copy link

Build 42117 failed

@flathubbot
Copy link

Build 42118 failed

The generator should handle this.
Let's see whether this works.
@flathubbot
Copy link

Started test build 42121

@flathubbot
Copy link

Build 42121 failed

This is inspired by
flathub/com.irccloud.desktop@8e764be

Let's see how well this works.

The commit 394786b910a1d2ee35455210d923a360a425f03d of f-b-t says, that
electron/get >= 1.12.4 has a new behaviour. But we don't have such a new
version. Well, let's give this a try, anyway.
@flathubbot
Copy link

Started test build 42130

@flathubbot
Copy link

Build 42130 failed

@muelli
Copy link
Collaborator Author

muelli commented Mar 19, 2021

dunno, really. Seems Electron is making trouble, somehow. Maybe 11.2 would help (currently, it seems to be pulling 11.1). At least, that's what seems to be working for flathub/com.irccloud.desktop@8e764be

I don't understand, how electron/get is pulled in, but it may help to have a newer version there, too.

@Simon-Laux
Copy link
Collaborator

so we should release an update that updates electron to 11.2?

@muelli
Copy link
Collaborator Author

muelli commented Mar 19, 2021

yeah, I mean, I am out of ideas what causes npm to not find the downloaded dependencies :-/
But unless you plan on updating those dependencies anyway, a full release is probably heavy handed. We could probably get away with testing a fork or a branch, e.g. you update the deps in some branch and we try to build that branch.

@Simon-Laux
Copy link
Collaborator

there you are https://github.com/deltachat/deltachat-desktop/tree/1.15.x_electron_upgrade
maybe it could be also electron builder, I can also update that if this is not working

@flathubbot
Copy link

Started test build 42161

@flathubbot
Copy link

Build 42161 failed

@Simon-Laux
Copy link
Collaborator

updated electron builder in that branch

@flathubbot
Copy link

Started test build 42170

@flathubbot
Copy link

Build 42170 failed

python3 ~/vcs/flatpak-builder-tools/node/flatpak-node-generator.py npm
~/vcs/deltachat-desktop/package-lock.json --recursive -s --output
generated-sources-npm.json
@flathubbot
Copy link

Started test build 42197

@flathubbot
Copy link

Build 42197 failed

Forgive me, I have no idea, what I'm doing.
@flathubbot
Copy link

Build 42203 failed

@flathubbot
Copy link

Started test build 42205

@flathubbot
Copy link

Build 42204 failed

@flathubbot
Copy link

Build 42205 failed

@muelli
Copy link
Collaborator Author

muelli commented Mar 19, 2021

Ouf, what a mess. Sorry.

Looks much better now:

npm info lifecycle deltachat-desktop@1.15.3~check-types: deltachat-desktop@1.15.3
> deltachat-desktop@1.15.3 check-types /run/build/delta
> tsc -b src/check-all-tsconfig.json
src/main/deltachat/controller.ts:24:42 - error TS2307: Cannot find module '../../shared/build-info' or its corresponding type declarations.
24 import { VERSION, BUILD_TIMESTAMP } from '../../shared/build-info'
                                            ~~~~~~~~~~~~~~~~~~~~~~~~~
src/main/index.ts:6:51 - error TS2307: Cannot find module '../shared/build-info' or its corresponding type declarations.

Looks like it has been forgotten to add build:shared:version to "build4production" :-/

That script turns out to be fragile:

> deltachat-desktop@1.15.3 build:shared:version /run/build/delta
> node ./bin/build-shared-version-info.js

Error: fatal: No tags can describe '66e91dbf50b7a49f97e874976a8b4a31bae030ba'.
Try --always, or create some tags.

    at gatherProcessStdout (/run/build/delta/bin/build-shared-version-info.js:7:27)

@Simon-Laux
Copy link
Collaborator

Simon-Laux commented Mar 20, 2021

Looks like it has been forgotten to add build:shared:version to "build4production" :-/

npm run build4production runs npm run build which runs npm run build:shared which runs npm run build:shared:version

the script tries a 3 methods of getting a git reference. Did all of them fail? maybe we need a special case for flatpak or its really unstable.

looking up that error I found this stackoverflow answer https://stackoverflow.com/questions/6445148/git-fatalno-tags-can-describe-sha1-number/6445255#6445255 which suggests to do a git fetch before running git describe

@muelli
Copy link
Collaborator Author

muelli commented Mar 20, 2021

Looks like it has been forgotten to add build:shared:version to "build4production" :-/

npm run build4production runs npm run build which runs npm run build:shared which runs npm run build:shared:version

yeah, you're right. But calling check types fails:

package.json:    "check-types": "tsc -b src/check-all-tsconfig.json",
package.json:    "build4production": "npm run check-types && NODE_ENV=\"production\" npm run build",

And by the time check types is run, the build hasn't yet been performed, so the shared thing hasn't been built either.

It seems that the Electron update is not necessary. At least the npm
install step seems to succeed.
This seems to be required in order for build4production to run.
@flathubbot
Copy link

Started test build 42313

@flathubbot
Copy link

Build 42313 failed

This tries to find out why it can't find the zip files it's looking for.
Because they sort of exist!

Interestingly, it looks for both ../chromedriver-v10.0.0-linux-x64.zip
and ../electron-v11.1.0-linux-x64.zip.
@flathubbot
Copy link

Started test build 42400

@muelli
Copy link
Collaborator Author

muelli commented Mar 22, 2021

  • async task error  error=ENOENT: no such file or directory, symlink '../electron-v11.1.0-linux-x64.zip' -> '/run/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.1.0electron-v11.1.0-linux-x64.zip/electron-v11.1.0-linux-x64.zip'
  ⨯ ENOENT: no such file or directory, symlink '../electron-v11.1.0-linux-x64.zip' -> '/run/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.1.0electron-v11.1.0-linux-x64.zip/electron-v11.1.0-linux-x64.zip'  stackTrace=

that's strange, because the file does indeed exist.

$ find .flatpak-builder/build/delta/ -name 'electron-v11.1.0-linux-x64.zip'
.flatpak-builder/build/delta/flatpak-node/cache/electron/electron-v11.1.0-linux-x64.zip
.flatpak-builder/build/delta/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.1.0electron-v11.1.0-linux-x64.zip/electron-v11.1.0-linux-x64.zip
.flatpak-builder/build/delta/flatpak-node/cache/electron/27ec2e86c437e8c9412011714f7c9847e193de54b5a2500afbd4406799c299cc/electron-v11.1.0-linux-x64.zip
.flatpak-builder/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/electron-v11.1.0-linux-x64.zip

So somehow it seems to look for the file in the wrong place. If the CWD line in the log is indeed correct, i.e. CWD: /run/build/delta, then, sure, ../electron-v11.1.0-linux-x64.zip doesn't exist. strace seems to confirm that the working directory hasn't changed. Weird then.

Note how it seems to be looking for both chromedriver and electron.

@flathubbot
Copy link

Build 42400 failed

@Simon-Laux
Copy link
Collaborator

did the electron upgrade help?

@flathubbot
Copy link

Started test build 42517

@flathubbot
Copy link

Build 42517 failed

@muelli
Copy link
Collaborator Author

muelli commented Mar 23, 2021

no :(

Other apps use electron-builder-22, so it should work, I guess. They use yarn, though, but I don't think it should matter too much here, because the failure is past installation stage.
I don't understand where electron-builder is looking for those files and, consequently, how to convince it to take the files that we have.

@Simon-Laux
Copy link
Collaborator

log looks to me like it looks in /run/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.3.0electron-v11.3.0-linux-x64.zip/electron-v11.3.0-linux-x64.zip?

anyways in the future we might be able to use electron-userland/electron-builder#5711, maybe you can try a build using it in a separate branch (install the branch of the electron builder pullrequest) 🤷

@muelli
Copy link
Collaborator Author

muelli commented Mar 23, 2021

log looks to me like it looks in /run/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.3.0electron-v11.3.0-linux-x64.zip/electron-v11.3.0-linux-x64.zip?

Hm. How do you arrive at that conclusion? That's the target, no?

anyways in the future we might be able to use electron-userland/electron-builder#5711, maybe you can try a build using it in a separate branch (install the branch of the electron builder pullrequest) shrug

Hm. No, I don't think this is relevant. Notice how the description also mentions that flathub is future work.

@Simon-Laux
Copy link
Collaborator

Simon-Laux commented Mar 27, 2021

Hm. How do you arrive at that conclusion? That's the target, no?

this section in the log:

  • async task error  error=ENOENT: no such file or directory, symlink '../electron-v11.3.0-linux-x64.zip' -> '/run/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.3.0electron-v11.3.0-linux-x64.zip/electron-v11.3.0-linux-x64.zip'
  ⨯ ENOENT: no such file or directory, symlink '../electron-v11.3.0-linux-x64.zip' -> '/run/build/delta/dist/linux-unpacked/resources/app/flatpak-node/cache/electron/httpsgithub.comelectronelectronreleasesdownloadv11.3.0electron-v11.3.0-linux-x64.zip/electron-v11.3.0-linux-x64.zip'  stackTrace=

@muelli
Copy link
Collaborator Author

muelli commented Mar 27, 2021

yeah, and I read it as if it's trying to symlink from ../electron-v11.3.0-linux-x64.zip to the path you mentioned. So I don't read it so that it's looking for the file in the place you said.

I don't know how to proceed here. Let's hope @refi64 has seen this type of failure before and knows what to do.

@muelli
Copy link
Collaborator Author

muelli commented Jun 5, 2021

this has been superseded

@muelli muelli closed this Jun 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants