I'm trying to run this ecommerce project on Bluemix:
https://github.com/dtsato/loja-virtual-devops
After fork it with jazz hub and obtain success in build stage, I got a package limit size error in the deploy stage:
Downloading artifacts...DOWNLOAD SUCCESSFUL
Target: https://api.ng.bluemix.net
Updating app loja-virtual-devops in org PFC Devops / space test as ricardo.zalla#imejunior.com.br...
OK
Using route loja-virtual-devops-App-Zalla.mybluemix.net
Uploading loja-virtual-devops...
Uploading app files from: /home/pipeline/47cbfb23-f83f-4ec3-b283-fc6c2b7da21f
Uploading 1.4G, 7856 files
148.4M uploaded...
289.3M uploaded...
454M uploaded...
621.3M uploaded...
745.1M uploaded...
906.9M uploaded...
1.1G uploaded...
1.3G uploaded...
Done uploading
FAILED
Error uploading application.
The app package is invalid: Package may not be larger than 1073741824 bytes
Finished: FAILED
Any hint about how can I overcome it and successfully run the app without deleting project files to shrink its size? Is possible to deploy projects larger than 1073741824 bytes on Bluemix?
You can try to exclude unnecessary files using “.cfignore” and Ignore local node_modules .
Also, Instead of packaging all dependencies, install them during app staging by using a custom buildpack.
Hope this helps.
Related
I am trying to set up a production/development of a Flutter web app for Firebase. I am able to deploy to the first one I configured (production) but not to the second (development). I am getting this error:
=== Deploying to 'my-app-dev'...
i deploying hosting i hosting[my-app-dev]: beginning deploy... i
hosting[my-app-dev]: found 27 files in build/web ⠋ hosting: uploading
new files [3/21] (14%) Error: Task
1c5e4be41a8a2901d8c9ae4edb5c2bd26c5c4d0564d732a3ce2bef7c6c27bcb0
failed: retries exhausted after 6 attempts, with error: The "path"
argument must be of type string. Received undefined ⠸ hosting:
uploading new files [4/21] (19%)
I am running the following commands:
firebase use my-app-dev
flutterfire configure --project=my-app-dev
flutter build web
firebase deploy
Note: if I use my-app-prod instead it works perfectly.
What am I doing wrong?
I faced the same problem and I solved it with the next two steps:
remove the .firebase folder from the root folder of your project
try to deploy your project again with firebase deploy
I am trying to install Magento 2.3.5 using composer.
muk#muk:/var/www/html$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.3.5 magento23
Creating a "magento/project-community-edition" project at "./magento23"
Installing magento/project-community-edition (2.3.5-p1)
- Installing magento/project-community-edition (2.3.5-p1): Loading from cache
Created project in /var/www/html/magento23
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 463 installs, 0 updates, 0 removals
- Installing magento/magento-composer-installer (0.1.13): Loading from cache
- Installing laminas/laminas-dependency-plugin (1.0.3): Loading from cache
Plugin installation failed (include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory), rolling back
- Removing laminas/laminas-dependency-plugin (1.0.3)
[ErrorException]
include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory
create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [<package>] [<directory>] [<version>]
I am getting following error.
Plugin installation failed (include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory), rolling back
- Removing laminas/laminas-dependency-plugin (1.0.3)
My Composer version
muk#muk:/var/www/html$ composer --version
Composer version 1.10.5 2020-04-10 11:44:22
I am using VirtualBox with Shared folder.
How can I fix it?
Note: To fix it I stopped using shared folder. Now I keep the entire code in the VM and do not use shared folder. For file synching I am using mutagen.
if anyone runs into this issue, it looks to be a problem with virtualBox and shared folders. when unzipping files, they are not immediately available in the environment.
the solution is by rkamp and is also available here:
https://stackoverflow.com/a/66413857/1470145
in short, one needs to override unzip to add a brief delay after unzipping.
I thought I had the same issue, but turned out it was something else.
The upgrade went OK for me, for a sandbox/clean 2.3.4 install, and a client project running 2.3.4.
A few things:
This could possibly be an issue with your cache, try to clear your composer laminas cache (~/.composer/cache/files/laminas usually)
Although it would complain about that, you've possibly got unmet platform requirements (php version, etc.)
Try clearing your entire composer cache (~/.composer)
Double-check the repository URL (should it be 2.3.5 or 2.3.5-p1?)
Hope that helps
error:-
check-node:
styles:
[echo] Running gulp build task for Mac OS X in /Users/admin/Documents/.../gulp_builder
[exec] env: node: No such file or directory
BUILD FAILED
/Users/admin/Documents/.../gulp_builder/builders.xml:84: exec returned: 127
Total time: 193 milliseconds
This is likely due to not having Gulp or some dependent component installed on the PATH being used by Eclipse. Without seeing more about your gulp_builder/builders.xml document I can't really comment as to what is missing. Can you post more context such as the 5 lines before and after and including line 84 of builders.xml
Agree with #sholsinger that more info would be better, but you may want to double-check that you have all of the node modules installed. You could run "npm install" in the terminal when you are in the directory where your package.json lives.
I have developed a working hybrid application in which I am using "phonegap-googlemaps-plugin". This plugin needs as a dependency two other which downloads and installs automatically in the project. The dependencies are:
com.google.playservices and plugin.http.request
Using the Cordova-CLI, installing this plugin with the dependencies will fail building the project the 1st time because of a specific directory in the "playservices" plugin. To overcome this, I have to run "ant clean" in my project and also remove/rename that directory. Now, I am using Intel XDK and uploaded my app and installed most of my plugins successfully and run the application on my device. When I am trying to install the google play services plugin, it fails to build because of the reason I described above (I've run through the logs). How can I overcome this issue now?
I have attached the part of the log that shows the fail error
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] No AIDL files to compile.
[echo] ----------
[echo] Handling RenderScript files...
[echo] ----------
[echo] Handling Resources...
[aapt] Generating resource IDs...
[aapt] invalid resource directory name: .../App/platforms/android/com.google.playservices/google-play-services_lib/bin/res/crunch
BUILD FAILED
/Developer/android-sdk-linux/tools/ant/build.xml:653: The following error occurred while executing this line:
/Developer/android-sdk-linux/tools/ant/build.xml:698: null returned: 1
Total time: 5 seconds
Error code 1 for command: ant with args: release,-f,.../App/platforms /android/build.xml,-Dout.dir=ant-build,-Dgen.absolute.dir=ant-gen
Command finished with error code 2: .../App/platforms/android/cordova/build --release
Error: .../App/platforms/android/cordova/build: Command failed with exit code 2
at ChildProcess.whenDone (/Developer/cordova/3.5.0-0.2.7/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
Thanks in advance.
I recently update my QtSdk to 1.2 and after that, I am unable to deploy a debian file of more then 6 mb. It gives me the following error:
16:32:02: Preparing SFTP connection...
16:32:02: Starting upload...
16:32:03: Failed to upload package: Failure
16:32:03: Deploy step failed.
Error while building project Animal101SymbianMeegov1 (target: Harmattan)
When executing build step 'Deploy Debian package via SFTP upload'
Has anyone run across this problem?
The workaround I use to deploy is to create a link in /tmp/.deb pointing to /var/tmp/.deb and the run the deploy step in QtCreator.