I am designing an application using the steps given in the link
I want to place my static html pages in my project using mean stack, when i compiling the code, i am getting the following error,
ReferenceError: Myapp is not defined
at C:\Documents and Settings\ssit\My Documents\GitHub\ssit\server\routes\index.js:11:6
at callbacks (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\lib\router\index.js:164:37)
at param (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\lib\router\index.js:138:11)
at pass (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\lib\router\index.js:145:5)
at Router._dispatch (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\lib\router\index.js:173:5)
at Object.router (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\lib\router\index.js:33:10)
at next (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\node_modules\connect\lib\proto.js:193:15)
at Object.handle (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\connect-flash\lib\flash.js:21:5)
at next (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\express\node_modules\connect\lib\proto.js:193:15)
at Object.Meanio.chainware.before [as handle] (C:\Documents and Settings\ssit\My Documents\GitHub\ssit\node_modules\meanio\lib\mean0.3.2.js:322:41)
how could i resolve this error.
What about checking your app.js(#public\js\app.js)
add like this.
angular.module('mean', ['ngCookies', 'ngResource', 'ui.bootstrap', 'ui.router', 'mean.system', 'mean.articles', 'mean.Myapp' ]);
angular.module('mean.system', []);
angular.module('mean.articles', []);
> angular.module('mean.Myapp', []);
Related
I'm new to build embedded linux image and i'm receiving this error message:
WARNING: gnu-config-native-20190501+gitAUTOINC+b98424c249-r0 do_fetch: Failed to fetch URL git://git.savannah.gnu.org/config.git, attempting MIRRORS if available
WARNING: pkgconfig-native-0.29.2+gitAUTOINC+edf8e6f0ea-r0 do_fetch: Failed to fetch URL git://anongit.freedesktop.org/pkg-config, attempting MIRRORS if available
WARNING: pseudo-native-1.9.0+gitAUTOINC+060058bb29-r0 do_fetch: Failed to fetch URL git://git.yoctoproject.org/pseudo, attempting MIRRORS if available
WARNING: libxcrypt-4.4.8-r0 do_fetch: Failed to fetch URL git://github.com/besser82/libxcrypt.git;branch=develop, attempting MIRRORS if available
WARNING: rpm-native-1_4.14.2.1-r0 do_fetch: Failed to fetch URL git://github.com/rpm-software-management/rpm;branch=rpm-4.18.x, attempting MIRRORS if available
WARNING: binutils-cross-arm-2.32.0-r0 do_fetch: Failed to fetch URL git://sourceware.org/git/binutils-gdb.git;branch=binutils-2_32-branch;protocol=git, attempting MIRRORS if available
WARNING: ninja-native-1.9.0-r0 do_fetch: Failed to fetch URL git://github.com/ninja-build/ninja.git;branch=release, attempting MIRRORS if available
WARNING: kmod-26-r0 do_fetch: Failed to fetch URL git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git, attempting MIRRORS if available
WARNING: ncurses-native-6.1+20190803-r0 do_fetch: Failed to fetch URL git://salsa.debian.org/debian/ncurses.git;protocol=https, attempting MIRRORS if available
WARNING: libnsl2-native-1.2.0+gitAUTOINC+37c5ffe303-r0 do_fetch: Failed to fetch URL git://github.com/thkukuk/libnsl;protocol=https;branch=main, attempting MIRRORS if available
WARNING: file-native-5.37-r0 do_fetch: Failed to fetch URL git://github.com/file/file.git, attempting MIRRORS if available
WARNING: e2fsprogs-native-1.45.3-r0 do_fetch: Failed to fetch URL git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git, attempting MIRRORS if available
WARNING: glibc-2.30-r0 do_fetch: Failed to fetch URL git://sourceware.org/git/glibc.git;branch=release/2.30/master;name=glibc, attempting MIRRORS if available
WARNING: systemd-1_243.2-r0 do_fetch: Failed to fetch URL git://github.com/systemd/systemd-stable.git;protocol=git;branch=v243-stable, attempting MIRRORS if available
ERROR: libnsl2-native-1.2.0+gitAUTOINC+37c5ffe303-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="1409"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/hetech/caio-testes/oe-repo/oe-core/scripts/native-intercept:/home/hetech/caio-testes/oe-repo/oe-core/scripts:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/work/x86_64-linux/libnsl2-native/1.2.0+gitAUTOINC+37c5ffe303-r0/recipe-sysroot-native/usr/bin/x86_64-linux:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/work/x86_64-linux/libnsl2-native/1.2.0+gitAUTOINC+37c5ffe303-r0/recipe-sysroot-native/usr/bin:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/work/x86_64-linux/libnsl2-native/1.2.0+gitAUTOINC+37c5ffe303-r0/recipe-sysroot-native/usr/sbin:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/work/x86_64-linux/libnsl2-native/1.2.0+gitAUTOINC+37c5ffe303-r0/recipe-sysroot-native/usr/bin:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/work/x86_64-linux/libnsl2-native/1.2.0+gitAUTOINC+37c5ffe303-r0/recipe-sysroot-native/sbin:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/work/x86_64-linux/libnsl2-native/1.2.0+gitAUTOINC+37c5ffe303-r0/recipe-sysroot-native/bin:/home/hetech/caio-testes/oe-repo/build/xsct/Vitis/2020.3/bin:/home/hetech/caio-testes/oe-repo/build/xsct/Vitis/2020.3/gnu/microblaze/lin/bin:/home/hetech/caio-testes/oe-repo/build/xsct/Vitis/2020.3/gnu/aarch32/lin/gcc-arm-none-eabi/bin:/home/hetech/caio-testes/oe-repo/build/xsct/Vitis/2020.3/gnu/armr5/lin/gcc-arm-none-eabi/bin:/home/hetech/caio-testes/oe-repo/build/xsct/Vitis/2020.3/gnu/aarch64/lin/aarch64-none/bin:/home/hetech/caio-testes/oe-repo/bitbake/bin:/home/hetech/caio-testes/oe-repo/build/tmp-glibc/hosttools"; export HOME="/home/hetech"; git -c core.fsyncobjectfiles=0 remote failed with exit code 1, output:
Traceback (most recent call last):
File "/home/hetech/caio-testes/oe-repo/build/tmp-glibc/hosttools/git", line 30, in
os.execv(real_git, sys.argv)
TypeError: execv: path should be string, bytes or os.PathLike, not NoneType
Summary: 10 tasks failed:
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-extended/libnsl/libnsl2_git.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/pkgconfig/pkgconfig_git.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-core/ncurses/ncurses_6.1+20190803.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/file/file_5.37.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.45.3.bb:do_fetch
virtual:native:/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/rpm/rpm_4.14.2.1.bb:do_fetch
/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-core/glibc/glibc_2.30.bb:do_fetch
/home/hetech/caio-testes/oe-repo/oe-core/meta/recipes-devtools/binutils/binutils-cross_2.32.bb:do_fetch
Summary: There were 10 WARNING messages shown.
Summary: There were 20 ERROR messages shown, returning a non-zero exit code.
I've tried to change the branches in bb files from master to main. But the error persisted even on those i'd changed.
I am new to golang and glide dependency management tool. I am trying to run glide install in created my company project. I have met an error about go-xorm library.
[ERROR] Update failed for github.com/go-xorm/xorm: Unable to get repository: Cloning into '/Users/xxx/.glide/cache/src/https-github.com-go-xorm-xorm'...
remote: Repository `go-xorm/xorm' is disabled.
remote: Please ask the owner to check their account.
fatal: unable to access 'https://github.com/go-xorm/xorm/': The requested URL returned error: 403
: exit status 128
[ERROR] Failed to checkout packages: Unable to get repository: Cloning into '/Users/xxx/.glide/cache/src/https-github.com-go-xorm-xorm'...
remote: Repository `go-xorm/xorm' is disabled.
remote: Please ask the owner to check their account.
fatal: unable to access 'https://github.com/go-xorm/xorm/': The requested URL returned error: 403
: exit status 128
It's seem that I am not able to download it from github because the owner made it disabled to clone.
How can I fix this error or Is there any way to export directly from local vendor without fetching from github. I am sure that the package is already on my local vendor folder. Thank you so much!!!
This is because XORM moved from Github (repo is still available as Public Archive) to Gitea and instead of github.com/go-xorm/xorm they now use xorm.io/xorm.
I'd recommend to stop using glide completely and replace it with Go Modules based workflow; but if you must use it, you will need to remove github.com/go-xorm/xorm from your glide.yaml, add xorm.io/xorm (you can use glide get to do so) and fix your imports everywhere in codebase.
i have the following build.yaml to build an image for my project
steps:
# Build the container image with the Python version of our choice.
- name: gcr.io/cloud-builders/docker
args:
[ 'build'
, '--tag=gcr.io/$PROJECT_ID/$_IMAGE_NAME'
, '--file=./Dockerfile_pipeline'
, '.'
]
images: ['gcr.io/$PROJECT_ID/$_IMAGE_NAME']
substitutions:
_IMAGE_NAME: pipeline:latestRun
This works fine when kicked off in gcp console via
gcloud beta builds submit --verbosity debug --config build.yaml
However, when i create a cloudbuild trigger (based on commits on my repo) that kicks off my build.yaml i am getting the following error
starting build "4cc47363-32f5-4862-8533-90810c972c5a"
FETCHSOURCE
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
Initialized empty Git repository in /workspace/.git/
From https://github.com/mmistroni/GCP_Experiments
* branch 450bfce1f17042d3163e39a3ecad89d06922ea47 -> FETCH_HEAD
HEAD is now at 450bfce adding marketloader trigger
BUILD
Already have image (with digest): gcr.io/cloud-builders/docker
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /workspace/Dockerfile_pipeline: no such file or directory
ERROR
ERROR: build step 0 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1
What am i missing?
kind regards
marco
i found the solution after fiddling for a while
When the trigger is kicked off from github commit, the root directory is the root my repo, GCP_Experiments
the dockerfile instead resides in GCP_Experiments\dataflow\pipeline\Dockerfile_pipeline
So i had to do two fixes
1 - put the full path of the docker file as --file argument
2 - specify, as a PATH parameter, the directory where file resides relative to root repo, aka ./dataflow/pipeline
rgds
I have a build in Teamcity with the SSH-deployer, but it fails with Auth fail. I am using password authentication, don't wanna use private/public key authentication as it won't be robust approach for us.
Idea is to authenticate via user name and password.
Attached the screenshot for the configuration.
Thanks
Error message:
[06:16:14]Collecting changes in 1 VCS root
[06:16:14][Collecting changes in 1 VCS root] VCS Root details
[06:16:14][VCS Root details] "DE_Automation" {instance id=40631, parent internal id=7496, parent id=Abc_DeAutomation, description: "ssh://git#<server_name>/abc/puppet.git#refs/heads/master"}
[06:16:15]Clearing temporary directory: /opt/teamcity/temp/buildTmp
[06:16:15]Publishing internal artifacts
[06:16:15][Publishing internal artifacts] Publishing 1 file using [WebPublisher]
[06:16:15][Publishing internal artifacts] Publishing 1 file using [ArtifactsCachePublisher]
[06:16:15]Checkout directory: /opt/teamcity/work/376a4e836d9c66e4
[06:16:15]Updating sources: server side checkout
[06:16:15][Updating sources] Using vcs information from agent file: 376a4e836d9c66e4.xml
[06:16:16][Updating sources] Building incremental patch for VCS root: DE_Automation; checkout rules: =>; revision: d88b7e07953108a1a4c392887c28e9b97ce31a5b --> d88b7e07953108a1a4c392887c28e9b97ce31a5b
[06:16:16][Updating sources] Repository sources transferred
[06:16:16]Step 1/3: Command Line
[06:16:16][Step 1/3] Disabled build step Command Line is skipped
[06:16:16]Step 2/3: SFTP (FTP Deployer)
[06:16:16][Step 2/3] Disabled build step SFTP (FTP Deployer) is skipped
[06:16:16]Step 3/3: SCP (SSH Deployer)
[06:16:16][Step 3/3] com.jcraft.jsch.JSchException: Auth fail
[06:16:16]
[Step 3/3] com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Session.java:512)
at com.jcraft.jsch.Session.connect(Session.java:183)
at jetbrains.buildServer.deployer.agent.ssh.SSHSessionProvider.<init>(SSHSessionProvider.java:102)
at jetbrains.buildServer.deployer.agent.ssh.SSHDeployerRunner.getDeployerProcess(SSHDeployerRunner.java:44)
at jetbrains.buildServer.deployer.agent.base.BaseDeployerRunner.createBuildProcess(BaseDeployerRunner.java:47)
at jetbrains.buildServer.agent.impl.runner.CallRunnerService.doCreateBuildProcess(CallRunnerService.java:71)
at jetbrains.buildServer.agent.impl.runner.CallRunnerService.createBuildProcess(CallRunnerService.java:47)
at jetbrains.buildServer.agent.impl.buildStages.runnerStages.start.CallRunnerStage.doBuildStage(CallRunnerStage.java:47)
at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor$1.callStage(RunnerStagesExecutor.java:25)
at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor$1.callStage(RunnerStagesExecutor.java:18)
at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.callRunStage(StagesExecutor.java:78)
at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.doStages(StagesExecutor.java:37)
at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor.doStages(RunnerStagesExecutor.java:18)
at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.RunnerContextExecutor.callRunnerStages(RunnerContextExecutor.java:43)
at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor.processNextStep(StepExecutor.java:25)
at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.ForEachBuildRunnerStage.executeRunnerStep(ForEachBuildRunnerStage.java:138)
at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.ForEachBuildRunnerStage.runStep(ForEachBuildRunnerStage.java:123)
at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.ForEachBuildRunnerStage.executeBuildRunners(ForEachBuildRunnerStage.java:83)
at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.ForEachBuildRunnerStage.doBuildStage(ForEachBuildRunnerStage.java:44)
at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor$1.callStage(BuildStagesExecutor.java:31)
at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor$1.callStage(BuildStagesExecutor.java:24)
at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.callRunStage(StagesExecutor.java:78)
at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.doStages(StagesExecutor.java:37)
at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor.doStages(BuildStagesExecutor.java:24)
at jetbrains.buildServer.agent.impl.BuildRunActionImpl.doStages(BuildRunActionImpl.java:70)
at jetbrains.buildServer.agent.impl.BuildRunActionImpl.runBuild(BuildRunActionImpl.java:50)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.doActualBuild(BuildAgentImpl.java:288)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.access$100(BuildAgentImpl.java:53)
at jetbrains.buildServer.agent.impl.BuildAgentImpl$1.run(BuildAgentImpl.java:252)
at java.lang.Thread.run(Thread.java:748)
[06:16:16][Step 3/3] Step SCP (SSH Deployer) failed with unexpected error
[06:16:16]Publishing internal artifacts
[06:16:16][Publishing internal artifacts] Publishing 1 file using [WebPublisher]
[06:16:16][Publishing internal artifacts] Publishing 1 file using [ArtifactsCachePublisher]
[06:16:16]Build finished
In my case, the problem was not related to SCP (even when TC was saying it is) at all:
My steps:
compile
SCP deploy
some cleanup
shh script on remote server
And step 2 was failing with the same error message as you (but when i SSH to remote server, the file was here)
But, the problem was not in failing step #2 but two steps ahead - i had wrong user in step #4!
Looks like some sort of async bug.
I am trying to deploy a large zip file (305 MB) to artifactory using the mvn deploy command, but i am getting broken pipe errors. I tried to upload the same file via the browser's "Deploy" button, and it worked fine.
Is there a setting that i can use to increase the socket timeout, or force maven/artifactory to wait until the package is uploaded?
Any help on how to resolve this is appreciated. Here are the log entries and stack trace:
May 09, 2016 11:16:32 AM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://mvnrepo.dev.xyz.myorg.net:8080
May 09, 2016 11:17:02 AM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://mvnrepo.dev.xyz.myorg.net:8080: Broken pipe
May 09, 2016 11:17:02 AM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://mvnrepo.dev.xyz.myorg.net:8080
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact com.myorg.xyz.myapp:my-app-package:zip:0.1-svc20160509.151532-7 from/to xyz-service-snapshots (http://mvnrepo.dev.xyz.myorg.net:8080/artifactory/xyz-service-local): Broken pipe
at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.put(BasicRepositoryConnector.java:274)
at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:311)
... 26 more
Caused by: org.apache.maven.wagon.TransferFailedException: Broken pipe
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:662)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:557)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:539)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:533)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:513)
at org.eclipse.aether.transport.wagon.WagonTransporter$PutTaskRunner.run(WagonTransporter.java:644)
at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)
at org.eclipse.aether.transport.wagon.WagonTransporter.put(WagonTransporter.java:410)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$PutTaskRunner.runTask(BasicRepositoryConnector.java:510)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
... 28 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
at org.apache.maven.wagon.providers.http.httpclient.impl.io.SessionOutputBufferImpl.streamWrite(SessionOutputBufferImpl.java:123)
at org.apache.maven.wagon.providers.http.httpclient.impl.io.SessionOutputBufferImpl.flushBuffer(SessionOutputBufferImpl.java:135)
at org.apache.maven.wagon.providers.http.httpclient.impl.io.SessionOutputBufferImpl.write(SessionOutputBufferImpl.java:164)
at org.apache.maven.wagon.providers.http.httpclient.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:115)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon$RequestEntityImplementation.writeTo(AbstractHttpClientWagon.java:204)
at org.apache.maven.wagon.providers.http.httpclient.impl.DefaultBHttpClientConnection.sendRequestEntity(DefaultBHttpClientConnection.java:155)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.CPoolProxy.sendRequestEntity(CPoolProxy.java:149)
at org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:236)
I managed to fix the issue by downgrade maven version from 3.5.2 to 3.0.4
Artifactory - open source 7.12.6
General
A Broken pipe error typically indicates a network issue. Deploying an artifact on Artifactory may fail with this error either if you have network issues (lost packets during deployment) or if your Artifactory repository has ran out of space (physical memory on the repository). Check Case 1 and Case 2 for troubleshooting.
Tip: Run mvn deploy -X. The -X option will log further information related with your error (sets log-level to debug)
Case 1: Network Issue
Solution: Just retry it :)
Issue Details
Maven's source code seems to be using apache's Validate method, (throws an IllegalArgumentException on validation error) to compare and validate the size of the deployed artifact with the artifact that was built locally. Note: On deploy, maven builds the artifact locally, and then uploads it to the configured repository (could be Artifactory, Maven Central etc) which in your case is Artifactory.
The error should look like this:
[DEBUG] Failed to dispatch transfer event 'PUT PROGRESSED [ARTIFACT_SERVER_URL]/artifact.jar <> [LOCAL_PATH]/artifact.jar
java.lang.IllegalArgumentException: progressed file size cannot be greater than size: 117964800 > 116927216
at org.apache.commons.lang3.Validate.isTrue (Validate.java:158)
at org.apache.maven.cli.transfer.AbstractMavenTransferListener$FileSizeFormat.formatProgress (AbstractMavenTransferListener.java:195)
at org.apache.maven.cli.transfer.ConsoleMavenTransferListener.getStatus (ConsoleMavenTransferListener.java:117)
at org.apache.maven.cli.transfer.ConsoleMavenTransferListener.transferProgressed (ConsoleMavenTransferListener.java:90)
...
Case 2: No space left on Artifactory repository
Solution: Free up space on Artifactory repository
Issue Details
For any erros related with deployment to artifactory, you can always check Artifactory's log from Web Application.
Just Navigate (from Sidebar) to Admin/Advanced/System Logs. Check for any error or warning in the log file.
An error related with the available space could be like the following:
2021-08-18 11:20:43,339 [http-nio-8081-exec-19] [WARN ] (o.a.w.s.RepoFilter :252) - Sending HTTP error code 404: No space left on device
2021-08-18 11:20:43,346 [http-nio-8081-exec-16] [WARN ] (o.a.r.s.RepositoryServiceImpl:1739) - Datastore disk is too high: Warning limit: 80%, Used: 94%, Total: 688.01 GB, Used: 652.97 GB, Available: 35.04 GB
2021-08-18 11:20:43,346 [http-nio-8081-exec-16] [INFO ] (o.a.e.UploadServiceImpl:386) - Deploy to 'libs-snapshot-local:artifact.jar' Content-Length: 170019165
2021-08-18 11:20:44,086 [http-nio-8081-exec-16] [ERROR] (o.a.w.s.RepoFilter :251) - Upload request of libs-snapshot-local:artifact.jar failed due to {}
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
...
In case you do identify such errors, try to remove some old artifacts to free up space, and retry your deployment later
Tip: It's a good practise to set some purging policies for old artifacts/snapshots on your Artifactory.