I'm using electron builder to auto-update my app for mac, windows & ubuntu OS. mac & windows are working fine. But, the Ubuntu deb package app is throwing errors while it's updating as I attach error logs below. I've tried some solutions available on web but didn't get the solution.
[2022-03-15 17:07:02.914] [info] Hello, log
[2022-03-15 17:07:02.918] [warn] Some problem appears
[2022-03-15 17:07:02.919] [info] Checking for update
[2022-03-15 17:07:04.342] [info] Found version 0.4.7 (url: Centroall-Tracker-0.4.7.AppImage)
[2022-03-15 17:07:04.343] [warn] Update-available"...!
[2022-03-15 17:07:04.345] [info] Downloading update from Centroall-Tracker-0.4.7.AppImage
[2022-03-15 17:07:04.349] [error] Error: Error: ENOENT: no such file or directory, open '/opt/Centroall Tracker/resources/app-update.yml'
[2022-03-15 17:07:04.350] [warn] Error event
[2022-03-15 17:07:04.351] [info] Error: ENOENT: no such file or directory, open '/opt/Centroall Tracker/resources/app-update.yml'
Related
I am working on a scala project that uses sbt 1.7.1
The project has its external dependencies like the database etc. that run in docker.
I'm not sure what started the issue exactly, but now when I try and go into sbt console I get this error:
[info] [launcher] getting org.scala-sbt sbt 1.7.1 (this may take some time)...
[error] [launcher] java.nio.file.FileSystemException: /root: Read-only file system
[error] [launcher] could not retrieve sbt 1.7.1
Earlier I was able to get into sbt console, but during compilation I got this error:
(I deleted the ~/.sbt folder to start over, that is when I can't even get into sbt console now)
sbt compile
[info] welcome to sbt 1.7.1 (Azul Systems, Inc. Java 11.0.10)
[info] loading settings for project app-backend-build from plugins.sbt ...
[info] loading project definition from /Users/username123/dev/git/project123/app-backend/project
[error] java.nio.file.FileSystemException: /root: Read-only file system
[error] at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
[error] at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
[error] at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
[error] at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:389)
[error] at java.base/java.nio.file.Files.createDirectory(Files.java:690)
[error] at java.base/java.nio.file.Files.createAndCheckIsDirectory(Files.java:797)
[error] at java.base/java.nio.file.Files.createDirectories(Files.java:783)
[error] at lmcoursier.internal.shaded.coursier.paths.Util.createDirectories(Util.java:81)
[error] at lmcoursier.internal.shaded.coursier.paths.CachePath.withStructureLock(CachePath.java:140)
[error] at lmcoursier.internal.shaded.coursier.cache.CacheLocks$.withStructureLock(CacheLocks.scala:20)
[error] at lmcoursier.internal.shaded.coursier.cache.CacheLocks$.withLockOr(CacheLocks.scala:37)
[error] at lmcoursier.internal.shaded.coursier.cache.internal.Downloader$Blocking$.remote(Downloader.scala:408)
[error] at lmcoursier.internal.shaded.coursier.cache.internal.Downloader.$anonfun$remote$5(Downloader.scala:510)
[error] at scala.concurrent.Future$.$anonfun$apply$1(Future.scala:659)
[error] at scala.util.Success.$anonfun$map$1(Try.scala:255)
[error] at scala.util.Success.map(Try.scala:213)
[error] at scala.concurrent.Future.$anonfun$map$1(Future.scala:292)
[error] at scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:33)
[error] at scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:33)
[error] at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
[error] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[error] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[error] at java.base/java.lang.Thread.run(Thread.java:834)
[error] (update) java.nio.file.FileSystemException: /root: Read-only file system
[warn] Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? (default: r)
If I go into a different folder, and try and create a new sbt project I get the same error:
sbt new scala/scala-seed.g8
I am using sdkman for my sbt installation, I deleted the .sbt folder and uninstalled sbt 1.7.1 and then re-installed it...that didn't help.
It seems as though some process has locked something related to sbt or coursier cache?
My project does have multiple modules, i'm not sure what root means in the error message.. the root project or some root folder that coursier might be using?
My sbt project was running fine earlier today, and now I cannot do anything related to scala on my system that uses sbt.
My system is running OSX, 13.0.1 (22A400).
Java home: ~/.jabba/jdk/zulu#1.11.0/Contents/Home
I just tried deleting the coursier cache and no change:
rm -Rf ~/Library/Caches/Coursier
That sbt console would run and compile the project.
I am trying to build a Spring Native application using buildpacks by following the instructions from: https://docs.spring.io/spring-native/docs/current/reference/htmlsingle/#getting-started
I changed Java version to 11 or 17 to avoid an error. Locally I have installed GraalVM v17 (22.2.0 and 22.3.0-dev).
When running mvn spring-boot:build-image I receive the following error related to BeanUtils:
[INFO] [creator] Fatal error: com.oracle.graal.pointsto.util.AnalysisError$ParsingError:
Error encountered while parsing
org.springframework.boot.SpringApplication.createSpringFactoriesInstances(java.lang.Class, java.lang.Class[], java.lang.ClassLoader, java.lang.Object[], java.util.Set)
[INFO] [creator] Parsing context:
[INFO] [creator] at org.springframework.boot.SpringApplication.createSpringFactoriesInstances(SpringApplication.java:439)
[INFO] [creator] at org.springframework.nativex.substitutions.boot.Target_SpringApplication.getSpringFactoriesInstances(Target_SpringApplication.java:173)
[INFO] [creator] at org.springframework.boot.SpringApplication.getSpringFactoriesInstances(SpringApplication.java:424) [INFO] [creator]
[INFO] [creator] at org.graalvm.nativeimage.pointsto/com.oracle.graal.pointsto.util.AnalysisError.parsingError(AnalysisError.java:152)
[INFO] [creator] at org.graalvm.nativeimage.pointsto/com.oracle.graal.pointsto.flow.MethodTypeFlow.createFlowsGraph(MethodTypeFlow.java:104)
[...]
[INFO] [creator] Caused by: org.graalvm.compiler.java.BytecodeParser$BytecodeParserError:
com.oracle.graal.pointsto.constraints.UnresolvedElementException:
Discovered unresolved method during parsing:
org.springframework.beans.BeanUtils$KotlinDelegate.instantiateClass(java.lang.reflect.Constructor, java.lang.Object[]).
This error is reported at image build time because class
org.springframework.beans.BeanUtils is registered for linking at image build time by system default
[INFO] [creator] at parsing org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:196) [...]
[INFO] [creator] ... 13 more
[INFO] [creator] Caused by: com.oracle.graal.pointsto.constraints.UnresolvedElementException:
Discovered unresolved method during parsing:
org.springframework.beans.BeanUtils$KotlinDelegate.instantiateClass(java.lang.reflect.Constructor, java.lang.Object[]).
This error is reported at image build time because class
org.springframework.beans.BeanUtils is registered for
linking at image build time by system default
... 38 more
[INFO] [creator] --------------------------------------------------------------------------------
The build is working fine when using Native Build Tools. The .exe files executes correctly ( I am using Windows).
Seems like there is an issue with paketobuildpacks/builder:0.1.242-tiny which I also experienced in paketobuildpacks/builder:base.
Downgrading to 0.1.241-tiny seems to resolve the issue.
See paketo-buildpacks/native-image#176 for workarounds to this problem, and follow that issue for the resolution.
This error has suddenly started appearing recently on all projects (without making any changes) which were building fine with
spring-boot:build-image.
I was trying to use an existing application as starting point for a new one.
So, I copied over the src-folder, the pom and a couple of IDE-specific files config files.
I then refactored all giving it a new path and application name and then I wanted to do a first build and entered mvn install.
This process is now hanging since 1 1/2 hours in vaadin-maven-plugin:18.0.2:build-frontend (see full console output below).
Is this expected or why is this taking so long? Can I somehow figure out, why and where this is hanging?
What am I missing? Are there any files other then those mentioned that absolutely MUST exist before a new Vaadin application can (even be tried to) be built?
[INFO] Scanning for projects...
[INFO]
[INFO] --------------< ch.zh.ksta.monitoring:my_app >---------------
[INFO] Building KStA-ZH-Monitoring 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) # my_app ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 7 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) # my_app ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- vaadin-maven-plugin:18.0.2:prepare-frontend (default) # my_app ---
[INFO] writing file D:\Projects\my_app\target\flow-frontend\package.json.
[INFO] writing file D:\Projects\my_app\target\flow-frontend\form\package.json.
[INFO] writing file 'D:\Projects\my_app\target\index.html'
[INFO] writing file 'D:\Projects\my_app\target\index.ts'
[INFO] Copying frontend resources from jar files ...
[INFO] Visited 173 resources. Took 2229 ms.
[INFO]
[INFO] --- vaadin-maven-plugin:18.0.2:build-frontend (default) # my_app ---
[INFO] Scanning classes to find frontend configurations and dependencies...
[INFO] Visited 720 classes. Took 2553 ms.
[INFO] Visited 126 classes. Took 138 ms.
[INFO] writing file D:\Projects\my_app\target\flow-frontend\package.json.
[INFO] writing file D:\Projects\my_app\target\flow-frontend\form\package.json.
[INFO] writing file 'D:\Projects\my_app\target\index.html'
[INFO] writing file 'D:\Projects\my_app\target\index.ts'
[INFO] Parsing java files from [D:\Projects\my_app\src\main\java]
[INFO] There are no connect endpoints to generate.
[INFO] Running `pnpm install` to resolve and optionally download frontend dependencies. This may take a moment, please stand by...
[INFO] Generated pnpmfile hook file: 'D:\Projects\my_app\pnpmfile.js'
[INFO] installing pnpm version 4.4.0 locally
[INFO] using 'C:\Users\mmo\.vaadin\node\node.exe C:\Users\mmo\.vaadin\node_modules\pnpm\bin\pnpm.js' for frontend package installation
Later addition:
If I terminate this using ^C I get:
...
2021-05-31 18:24:40,199 ERROR [task-1] com.vaadin.flow.server.frontend.TaskRunNpmInstall: Command `C:\Program Files\nodejs\node.exe C:\Users\mmo\.vaadin\node_modules\pnpm\bin\pnpm.js --shamefully-hoist=true install` failed:
Using hooks from: D:\Projects\my_app\pnpmfile.jsreadPackage hook is declared. Manifests of dependencies might get overridden
2021-05-31 18:24:40,201 ERROR [task-1] com.vaadin.flow.server.frontend.TaskRunNpmInstall: >>> Dependency ERROR. Check that all required dependencies are deployed in pnpm repositories.
2021-05-31 18:24:40,205 DEBUG [task-1] com.vaadin.flow.server.startup.DevModeInitializer: Could not initialize dev mode handler. One of the node tasks failed
com.vaadin.flow.server.ExecutionFailedException: Pnpm install has exited with non zero status. Some dependencies are not installed. Check pnpm command output
at com.vaadin.flow.server.frontend.TaskRunNpmInstall.runNpmInstall(TaskRunNpmInstall.java:405)
at com.vaadin.flow.server.frontend.TaskRunNpmInstall.execute(TaskRunNpmInstall.java:120)
at com.vaadin.flow.server.frontend.NodeTasks.execute(NodeTasks.java:634)
at com.vaadin.flow.server.startup.DevModeInitializer.runNodeTasks(DevModeInitializer.java:471)
at com.vaadin.flow.server.startup.DevModeInitializer.lambda$initDevModeHandler$0(DevModeInitializer.java:381)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
If I restart the build again it will hang again.
Gee - is this brittle... :-(
Got this same error. I deleted from my home directory:
.vaadin
.pnpm-store
... and the generated stuff from my project:
webpack.config.js
tsconfig.json
types.d.ts
webpack.config.js
webpack.generated.js
pnpm-lock.yaml
pnpmfile.js
package.json
.npmrc
target
.pnpm-debug.log
... probably overkill, but then it worked again.
when I bulid a project by using the plugin 'publish over ssh', jenkins shows me the error:
[INFO] Packaging webapp
[INFO] Assembling webapp [bc-ctq] in [/var/lib/jenkins/workspace/bc-
ctq/target/bc-ctq]
[INFO] Processing war project
[INFO] Copying webapp resources [/var/lib/jenkins/workspace/bc- ctq/src/main/webapp]
[INFO] Webapp assembled in [140 msecs]
[INFO] Building war: /var/lib/jenkins/workspace/bc-ctq/target/bc-ctq.war
[INFO] WEB-INF/web.xml already added, skipping
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.018 s
[INFO] Finished at: 2018-10-26T19:38:10+08:00
[INFO] ------------------------------------------------------------------------
SSH: Connecting from host [localhost.localdomain]
SSH: Connecting with configuration [love] ...
SSH: Disconnecting configuration [love] ...
ERROR: Exception when publishing, exception message [Permission denied]
Archiving artifacts
Finished: UNSTABLE
Send files or execute commands over SSH after the build runs
the ssh server config
I was facing similar error and it turned out to be ownership issue. The owner of your project folder should be same as the one Jenkins uses to remote SSH into your instance.
Check ownership of your folder by running ls -ltr in your parent directory.
Change ownership using sudo chown -R owner:group DirectoryName/
Check verbose output and start build, then you'll see where is the problem
I just want to look at sencha architect 3 and created the Touch 2.3 project "locations". Starting Web and simulation in iOS works great, but native Android build failed:
[INF] -before-native-package:
[INF]
[INF] -native-package-mobile:
[INF] [echo] Running default mobile packager config.
[INF] [echo]
[INF] [echo] Processing Mobile Packager config file
[INF] [echo] config: /Applications/XAMPP/xamppfiles/htdocs/MyApp/packager.json
[INF] [echo] inputPath: /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native/MyApp
[INF] [echo] outputPath: /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json
[INF] [echo] Running mobile packager action run on file /Applications/XAMPP/xamppfiles/htdocs/MyApp/packager.temp.json
[ERR]
Error: Project folder '/Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json' is not empty. Please consider using 'android update' instead.
Created directory /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/src/com/mycompany/myAppID
Added file /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/src/com/mycompany/myAppID/STActivity.java
Created directory /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/res
Created directory /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/bin
Created directory /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/libs
Created directory /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/res/values
Added file /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/res/values/strings.xml
Created directory /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/res/layout
Added file /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/res/layout/main.xml
Added file /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/AndroidManifest.xml
Added file /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/build.xml
Added file /Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/proguard-project.txt
sh: ant: command not found
"/Users/markus/android-sdks/tools/android" create project --target android-7 --name MyApp --activity STActivity --path "/Applications/XAMPP/xamppfiles/htdocs/MyApp/build/native-package-mobile/MyApp/packager.json/" --package com.mycompany.myAppID
Could not run ant with error: 32512
Failed to package application
[ERR]
[ERR] BUILD FAILED
[ERR] com.sencha.exceptions.ExProcess: stbuild exited with non-zero code : 7
[ERR] at sun.reflect.NativeMethodAccessorImpl.invoke(Nati
[ERR] veMethodAccessorImpl.java:57)
[ERR]
[ERR] Total time: 7 seconds
[ERR] The following error occurred while executing this line:
/Applications/XAMPP/xamppfiles/htdocs/MyApp/.sencha/app/build-impl.xml:422: The following error occurred while executing this line:
/Applications/XAMPP/xamppfiles/htdocs/MyApp/.sencha/app/packager-impl.xml:108: The following error occurred while executing this line:
/Applications/XAMPP/xamppfiles/htdocs/MyApp/.sencha/app/packager-impl.xml:98: The following error occurred while executing this line:
/Applications/XAMPP/xamppfiles/htdocs/MyApp/.sencha/app/packager-impl.xml:7: com.sencha.exceptions.ExProcess: stbuild exited with non-zero code : 7
Run a
$ sudo ln -s /usr/local/bin/ant /usr/bin/ant
this will make Architect 3 detect your installation.
This is if you are using a Mac and installed your ant using homebrew
Ant is not installed.
I had the same issue. I assume you're on a Mac since you say iOS worked. Apparently in Mavericks, ant is no longer included by default.
you can install it with homebrew easily enough.
However, that still does not work for me. Here's a help thread I started on the sencha architect forums: http://www.sencha.com/forum/showthread.php?277937-Simple-attempt-at-an-android-build&p=1017898#post1017898