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

Copy Files Task failed find #9046

Closed
ahmadkhudeish opened this issue Dec 11, 2018 · 22 comments
Closed

Copy Files Task failed find #9046

ahmadkhudeish opened this issue Dec 11, 2018 · 22 comments
Assignees
Labels

Comments

@ahmadkhudeish
Copy link

Troubleshooting

Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Environment

  • Server - Azure Pipelines or TFS on-premises?

Using Azure Pipelines, Team Project Name = MyPatientList, build definition = MyPatientList-CI, Build number: 31
Azure Pipelines:

  • Agent - Hosted or Private:
    Self Hosted Mac OSx

Issue Description

Copy files task in Azure DevOps Pipelines produces an error when building cordova ios app. The build succeeds and when I check the sources directory I can locate the file but Copy Files task alwats fails to find the file. I am using a self hosted agent with system.debug variable set to true but cannot get any useful information from the log:

I have the following task configurations:

Source Folder:

$(Build.SourcesDirectory)

Contents:

**/*.ipa

Target Folder:

$(Build.ArtifactStagingDirectory)

Output:

Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/Patient List UAT.app'
What am I doing wrong here?

Any help appreciated, thanks

Task logs

2018-12-11T05:08:50.6847750Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcarchive/dSYMs (directory)
2018-12-11T05:08:50.6847880Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcodeproj (directory)
2018-12-11T05:08:50.6848000Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcodeproj/project.pbxproj (file)
2018-12-11T05:08:50.6848120Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcworkspace (directory)
2018-12-11T05:08:50.6848240Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcworkspace/contents.xcworkspacedata (file)
2018-12-11T05:08:50.6848380Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcworkspace/xcshareddata (directory)
2018-12-11T05:08:50.6848510Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcworkspace/xcshareddata/xcschemes (directory)
2018-12-11T05:08:50.6848650Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/PatientListUAT.xcworkspace/xcshareddata/xcschemes/PatientListUAT.xcscheme (file)
2018-12-11T05:08:50.6848760Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build (directory)
2018-12-11T05:08:50.6848880Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device (directory)
2018-12-11T05:08:50.6848990Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/DistributionSummary.plist (file)
2018-12-11T05:08:50.6849110Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/ExportOptions.plist (file)
2018-12-11T05:08:50.6850000Z ##[debug]  /Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/Packaging.log (file)
2018-12-11T05:08:50.6850190Z ##[debug]task result: Failed
2018-12-11T05:08:50.6913670Z ##[error]Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/PatientListUAT.app'
2018-12-11T05:08:50.6929720Z ##[debug]Processed: ##vso[task.issue type=error;]Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/PatientListUAT.app'
2018-12-11T05:08:50.6953310Z ##[debug]Processed: ##vso[task.complete result=Failed;]Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/ahmadkhudeish/build_agents/agent1/_work/1/s/platforms/ios/build/device/PatientListUAT.app'
2018-12-11T05:08:50.6955180Z ##[section]Finishing: Copy Files to: $(Build.ArtifactStagingDirectory)

Error logs

[Insert error from the logs here for a quick overview]

@ahmadkhudeish
Copy link
Author

I have gotten around this issue by using a simple bash script to copy the file instead, I think the Copy Files task provided by Azure Pipelines is buggy.

@barde
Copy link

barde commented Jan 14, 2019

I can confirm this issue when using Cordova builds on DevOps.

The solution is to insert a small bash script to remove the link (AppName).app in the output directory of the binaries before the "Copy Files" step.

The link is pointing to some directory which was created and deleted during the build.

@damccorm
Copy link

Added a PR to address this.

@schultetwin1
Copy link
Contributor

@damccorm thanks for looking into this! We are running into this issue as well. Our work around was to delete the symlink files before calling CopyFiles.

jt-nti added a commit to jt-nti/fabric-chaincode-node that referenced this issue Jan 31, 2020
It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>
jt-nti added a commit to jt-nti/fabric-chaincode-node that referenced this issue Jan 31, 2020
It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>
mbwhite pushed a commit to hyperledger/fabric-chaincode-node that referenced this issue Jan 31, 2020
It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>
@damccorm
Copy link

Hey all, sorry for the delay on this. This should be fixed by #9390 which should start rolling out next week

@ysodiqakanni
Copy link

Hey all, sorry for the delay on this. This should be fixed by #9390 which should start rolling out next week

I'm still waiting for this fix. I can't find a workaround yet and I thought you'd have had the issue fixed and deployed already.

@damccorm
Copy link

damccorm commented Mar 6, 2020

@ysodiqakanni could you share your logs from the failing build?

I think this should've been fixed, so I'm surprised to hear you're still encountering the issue

heatherlp pushed a commit to heatherlp/fabric-chaincode-node that referenced this issue Mar 26, 2020
It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>
heatherlp pushed a commit to heatherlp/fabric-chaincode-node that referenced this issue Mar 30, 2020
It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>
heatherlp pushed a commit to heatherlp/fabric-chaincode-node that referenced this issue Mar 30, 2020
It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>
@Tofalvy
Copy link

Tofalvy commented Apr 29, 2020

I still experience this issue.
Is it fixed yet?

@damccorm
Copy link

@Tofalvy could you share your logs from the failing build?

I think this should've been fixed, so I'm surprised to hear you're still encountering the issue

@kim3er
Copy link

kim3er commented May 19, 2020

Still affecting me. Here is my log:

2020-05-19T17:21:30.7421200Z ##[section]Starting: Copy Files to: /Users/runner/runners/2.168.2/work/1/a
2020-05-19T17:21:30.7431720Z ==============================================================================
2020-05-19T17:21:30.7432130Z Task         : Copy files
2020-05-19T17:21:30.7432590Z Description  : Copy files from a source folder to a target folder using patterns matching file paths (not folder paths)
2020-05-19T17:21:30.7433030Z Version      : 2.164.0
2020-05-19T17:21:30.7433330Z Author       : Microsoft Corporation
2020-05-19T17:21:30.7433800Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/copy-files
2020-05-19T17:21:30.7434450Z ==============================================================================
2020-05-19T17:21:30.9277700Z ##[error]Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/runner/runners/2.168.2/work/1/s/platforms/ios/build/device/[redacted].app'
2020-05-19T17:21:30.9303370Z ##[section]Finishing: Copy Files to: /Users/runner/runners/2.168.2/work/1/a

@kim3er
Copy link

kim3er commented May 19, 2020

I can also confirm that manually deleting the *.app file/folder solves the problem.

@DevRCRun
Copy link

I've also just run into this when running script tasks, npm ci (to install everything for build) and then npm ci --only=production

A delete task in between these removing node_modules solves the issue (even though npm ci should be removing it entirely anyway)

@trevonmckay
Copy link

Also having this issue

Hosted
Agent: macOS-latest
Organization: dalgs
Project: Digital Workplace
Pipeline/Build#: winteropstoolkit-mobile/20200801.13

Starting: Copy build output to artifact staging
==============================================================================
Task         : Copy files
Description  : Copy files from a source folder to a target folder using patterns matching file paths (not folder paths)
Version      : 2.164.2
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/copy-files
==============================================================================
##[error]Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/runner/work/1/s/platforms/ios/build/device/Winter Ops Mobile Toolkit.app'
Finishing: Copy build output to artifact staging

@matthewfcarlson
Copy link

matthewfcarlson commented Aug 27, 2020

Also seeing this as well.
Hosted
Agent: Ubuntu and windows-latest

##[debug]task result: Failed
##[error]Unhandled: Failed find: ENOENT: no such file or directory, stat '/home/vsts/work/1/s/.extdeps/edk2_extdep/EmulatorPkg/Unix/Host/X11IncludeHack'
##[debug]Processed: ##vso[task.issue type=error;]Unhandled: Failed find: ENOENT: no such file or directory, stat '/home/vsts/work/1/s/.extdeps/edk2_extdep/EmulatorPkg/Unix/Host/X11IncludeHack'
##[debug]Processed: ##vso[task.complete result=Failed;]Unhandled: Failed find: ENOENT: no such file or directory, stat '/home/vsts/work/1/s/.extdeps/edk2_extdep/EmulatorPkg/Unix/Host/X11IncludeHack'
Finishing: Copy license and NuGet config

@sey
Copy link

sey commented Sep 30, 2020

Same here.
Hosted, ubuntu-latest

- task: CopyFiles@2
  displayName: Copy zip to staging area
  inputs:
    contents: 'build/**/**/*.zip'
    targetFolder: '$(Build.ArtifactStagingDirectory)'
    cleanTargetFolder: true
    flattenFolders: true

And I get ##[error]Unhandled: Failed find: ENOENT: no such file or directory, stat '/home/vsts/work/1/s/node_modules/.bin/detect-libc'

@sriw-world
Copy link

sriw-world commented Oct 20, 2020

I am also facing this issue .

Starting: CopyFiles
==============================================================================
Task         : Copy files
Description  : Copy files from a source folder to a target folder using patterns matching file paths (not folder paths)
Version      : 2.164.2
Author       : Microsoft Corporation
==============================================================================
##[error]Unhandled: Not found SourceFolder: /home/vsts/work/1/s/$(System.DefaultWorkingDirectry)

@anatolybolshakov anatolybolshakov self-assigned this Oct 20, 2020
@anatolybolshakov anatolybolshakov added the Area: ABTT Akvelon Build Tasks Team area of work label Oct 20, 2020
@anatolybolshakov
Copy link
Contributor

Hi everyone, we prepared a fix for this issue
@sarthak-sriw hmm, your issue looks different - looks like there's just a typo in the variable name 'System.DefaultWorkingDirectry' - should be 'System.DefaultWorkingDirectory', so it hasn't been replaced by variable value

@anatolybolshakov anatolybolshakov added the awaiting deployment Related changes are waiting for deployment to be completed label Oct 29, 2020
mbwhite added a commit to hyperledger/fabric-chaincode-node that referenced this issue Nov 10, 2020
* [FABCI-482] Update Nexus URL's to Artifactory

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>

* [FABCN-377] Prepare v2.0 release

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Fix docker tag

Tag needs to include hyperledger to match the publish command

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-377] Bump version to 2.0.1

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-378] Publish jsdoc

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Re-enable tests

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-381] Access localmspid

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Update audit level

Temporarily raise audit level to moderate to work around current minimist audit failures

Can be reverted after grpc, rc, and tar dependecies have been updated to pull in updated versions of mkdirp and minimist

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Expand node engine version range

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* FABCN-391 Use version 2.1 of fabric docker images

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* FABCN-391 Update test/chaincodes to use node 10 and add a missing hat

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* [FABCN-377] Prepare for v2.1 unstable builds (WIP)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-373] Compatibility Matrix

Ammended all the node-engines in package.json to match
that in the docker image

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
Change-Id: Ia536ed66daf857679adf9f858b35d206a4f1007f

* [FABCN-382] fix compatibility.md title

Signed-off-by: Andrew Hurt <andrew.hurt1@ibm.com>

* Improve build reliability

It looks like rushjs symlinking can cause issues with the CopyFiles task. Use a script instead as suggested in microsoft/azure-pipelines-tasks#9046

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Add readme to redirect to site

Signed-off-by: Ry Jones <ry@linux.com>

* FABCN-241 Remove to.be.ok

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

* FABCN-241  Change to.be.ok

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

* FABCN-241 Remove to.be.ok

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

* fix: remove semicolon

Signed-off-by: Johnny Da Costa <johnny.dacosta@he-arc.ch>

* FABCN-391 Set docker images to use node 10
- reflect this in compatibility.md
- update some out of date tutorial lines

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* FABCN-391 Build against release-2.x

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* FABCN-391 Remove references to 2.0 and 2.0.0
- replace with 2.x

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* [FABCN-392] Update to Node 12

Set node engine to be the latest LTS at time of commit 12.6.1
Due to issues with comibation of the 12.6 and rewire, unit tests are run
with node 12.5.0

Updated timeout as Typescript compilation seems to have slowed down.

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* [FABCN-391] Publish JSDoc to release-2.1

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* FABCN-391 v2.1.0 Release (#112)

* FABCN-391 v2.1.0 Release
- also fixed nodeenv images to use node 12

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* Update timeout (#114)

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>

Co-authored-by: Brett Logan <brett.t.logan@ibm.com>

* FABCN-391 Bump to 2.1.1 and fix docker tag (#122)

* FABCN-391 Remove "latest" from tag name on docker image publishing for tagged versions

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* FABCN-391 Bump version number to 2.1.1

Signed-off-by: heatherlp <heatherpollard0@gmail.com>

* [FABCN-391] fix directory for api doc publish (#125)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-394] Update typescript interface file (#128)

Updated both typescript definition files to match the case
and the existance of the implementation function.

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* Prepare 2.1.1 release (#133)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Bump version (#134)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-397] State queries limited to 100 results (#141)

Errow was the new version of protobufjs used to create the bundle.js
gave a different property to the 'has more' field.  hasMore replaced
has_more

As this accessed as JS property it didn't fail, but meant only a limited
number could be accessed.

corrected, added test for 229 results.
bit of dead code pruning

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* [FABCN-396] Add notes on minimum 1.4 module version for node 12 (#139)

Stated that 1.4.5 and above are the versions that work with node 12
Added a better example for the use of the chaincode node runtime environment
variable

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* FABCN-395: Use @grpc/grpc-js for Node.js chaincode (#143) (#144)

Signed-off-by: Simon Stone <sstone1@uk.ibm.com>

* FABCN-401 Correct use of Yargs api (#145)

* FABCN-401 Correct use of Yargs api

Change from package.json to api parser configuration

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* Force build

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* Fix broken tutorials link (#137) (#138)

Signed-off-by: NIKHIL E GUPTA <negupta@us.ibm.com>

Co-authored-by: NIKHIL E GUPTA <negupta@us.ibm.com>

Co-authored-by: NIKHIL E GUPTA <negupta@us.ibm.com>

* Prepare 2.1.2 release (#148)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Bump version to 2.1.3 (#149)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* FABCN-405 Fix tutorial reference (#150) (#152)

Updated to use 2.1 modules

Signed-off-by: Ry Jones <ry@linux.com>

Co-authored-by: Matthew B White <mbwhite@users.noreply.github.com>
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

Co-authored-by: Ry Jones <ry@linux.com>

* [FABCN-407] Update protos (#154) (#157)

To prepare for the implementation of chaincode gRPC server, this patch
updates protobuf definitions to the latest ones.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* [FABCN-410] Use new lifecycle for fv/e2e tests (#160)

This patch enables v2.0 feature in the test Hyperledger Fabric network
and uses new lifecycle commands in the fv and e2e tests.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* Fix 'rush install' error in release-2.x (#163)

This patch upgrades pnpm to fix the "Could not find peer dependency
'google-auth-library'" error.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* Cheery-pick chaincode server feature to release-2.x (#166)

* [FABCN-408] Separate message handler from client (#155)

This patch divides the ChaincodeSupportClient class into two classes:
ChaincodeSupportClient, which represents a chaincode client that
connects to a peer, and ChaincodeMessageHandler, which handles messages
in communciation with the peer through a stream.

Because the latter part is common in both client and server model,
the ChaincodeMessageHandler class will be used in the future
implementation for a chaincode gRPC server.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

Co-authored-by: Matthew B White <mbwhite@users.noreply.github.com>

* [FABCN-409] Chaincode gRPC server w/o TLS (#159)

This patch adds the ChaincodeServer class to support the server mode of
chaincode.
It also adds the server() method, which creates a new instance of
the ChaincodeServer class, to the Shim class, the entrypoint of the
fabric-shim library.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* [FABCN-411] Add server command to CLI (#161)

This patch adds a "server" command to the "fabric-chaincode-node" CLI.
The command starts the contracts as a chaincode server.

Example: fabric-chaincode-node server --chaincode-address 0.0.0.0:9999 \
           --chaincode-id mycc_v0:a1233bb13227a05932

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* [FABCN-413] Add e2e test for chaincode server (#162)

This patch adds new e2e test for the chaincode gRPC server feature.

The test performs as following:
  - Create a package which contains server and cc information
  - Build a container image of the chaincode
  - Install the package into peers
  - Obtain the installed package ID from the peers
  - Start the chaincode container with the package ID
  - Approve and commit the chaincode definition
  - Invoke and query the chaincode

"rush test:e2e" will perform both tests for both server and client mode.

This patch also modifies "rush start-fabric" to use external builder
scripts.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* [FABCN-414] Update TypeScript definition (#165)

This patch updates the type defintion file for TypeScript to add classes
and interfaces related to the chaincode server feature.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* [FABCN-412] TLS support for chaincode server (#164)

This patch adds TLS support for chaincode server.

To enable TLS, set tlsProps in the second argument for shim.server,
or add --chaincode-tls-cert-file and --chaincode-tls.key-file for CLI.

Client certificate validation can be enabled via tlsProps.clientCACerts
for shim.server or --chaincode-tls-client-cacert-file for CLI.

Also the -path options (for base64 encoded files) are supported.

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

Co-authored-by: Matthew B White <mbwhite@users.noreply.github.com>

* [FABCN-415] Lock grpc-js to 1.0.3 (#170)

@grpc/grpc-js updated to 1.1.0; this has caused the initial request to the
peer on chaincode start to fail.

Dropping back to 1.0.3 resolves the issue.

See FABCN-415

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* [FABCN-416] Release v2.1.3 (#171)

For resolving grpc version dependency

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* Specify exact version of winston dependency

Work around for issue winstonjs/winston#1814

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Prepare 2.1.4 release (#174)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-393] Fix broken links in documents (#169)

This patch fixes broken links to the fabric documents.
This patch also fixes links to point to those for the proper version
(2.1).

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* Bump version to 2.1.5 (#175)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-319] Update dependnency versions (#176)

- Update grpc-js and winston to pre-lock levels
- General update of dependcies
- Note add about shirnkwrap.
- Corrected test cases

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* [FABCN-420] Remove Azure pipeline warnings (#177)

Used new coverage merge tool to joing coverage together

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* Use Official CouchDB 3.1 Image (#180)

Fabric 2.2 removes official support for CouchDB 2.x.
The migration to 3.1 was to address fsync issues
in the underlying storage implementation in Couch.

This change moves to CouchDB 3.1 which requires the
user to now set an admin identity at startup.

Node 12.18.2 is the latest LTS

Signed-off-by: Brett Logan <brett.t.logan@ibm.com>

* [FABCN-421] release: 2.2.0 LTS release (#181)

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* Bump version to 2.2.1 (#184)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* Fix: ChaincodeStub.getMspID should be in lowerCamelCASE

Signed-off-by: winderica <winderica@gmail.com>

* [FABCN-422] Add release guide (#187)

Signed-off-by: James Taylor <jamest@uk.ibm.com>

* [FABCN-433] Update typescript and @types/node (#199)

Need current supported levels.

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* [FABCN-241] Remove to.be.ok (#204)

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

* [FABCN-435] OOM on Large Arg Size (#207)

Incorrect trace point logging entire binary message

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>

* v2.x tutorials updated (#217)

Signed-off-by: Kestutis Gudynas <44440041+kemi04@users.noreply.github.com>

* [FABCN-430] Fix type for timestamp.second (#194) (#209)

This patch fixes the type definition for the second field in the
Timestamp, which is actually Long (int64).

Signed-off-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

Co-authored-by: Matthew B White <mbwhite@users.noreply.github.com>

Co-authored-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>

* [FABCN-432] - Update class transformer dependency (#213)

* [FABCN-241] Remove to.be.ok

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

* [FABCN-1627]-Update class transformer dependency

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

* Release v2.3.0

Signed-off-by: Kestutis Gudynas <gudynask@gmail.com>

* Bump version to 2.3.1

Signed-off-by: Kestutis Gudynas <gudynask@gmail.com>

Co-authored-by: Brett Logan <brett.t.logan@ibm.com>
Co-authored-by: heatherlp <heatherpollard0@gmail.com>
Co-authored-by: Matthew B White <whitemat@uk.ibm.com>
Co-authored-by: Andrew Hurt <andrew.hurt1@ibm.com>
Co-authored-by: Ry Jones <ry@linux.com>
Co-authored-by: lesleyannj <lesleyannj@hotmail.com>
Co-authored-by: Johnny Da Costa <johnny.dacosta@he-arc.ch>
Co-authored-by: Matthew B White <mbwhite@users.noreply.github.com>
Co-authored-by: heatherlp <40789053+heatherlp@users.noreply.github.com>
Co-authored-by: Simon Stone <sstone1@uk.ibm.com>
Co-authored-by: nikhil550 <nikhilg550@gmail.com>
Co-authored-by: NIKHIL E GUPTA <negupta@us.ibm.com>
Co-authored-by: Taku Shimosawa <taku.shimosawa@hal.hitachi.com>
Co-authored-by: winderica <winderica@gmail.com>
Co-authored-by: LAJ <33546098+lesleyannjordan@users.noreply.github.com>
Co-authored-by: Kestutis Gudynas <44440041+kemi04@users.noreply.github.com>
Co-authored-by: Kestutis Gudynas <gudynask@gmail.com>
@sergiuturus
Copy link

I am still facing the issue: ##[error]Unhandled: Failed find: ENOENT: no such file or directory, stat '/Users/runner/work/1/s/platforms/ios/build/device/AppName.app'

steps:
- task: CopyFiles@2
  displayName: 'Copy Files to: $(build.artifactstagingdirectory)'
  inputs:
    SourceFolder: '$(system.defaultworkingdirectory)/platforms/ios/build/device'
    Contents: AppName.ipa
    TargetFolder: '$(build.artifactstagingdirectory)'

@anatolybolshakov
Copy link
Contributor

@sergiuturus we prepared a fix for this issue but it will take some time (about 3 weeks) to roll it out - I'm going to remove 'awaiting deployment' label once it's rolled out

@sergiuturus
Copy link

sergiuturus commented Nov 11, 2020

I think so. ls $(system.defaultworkingdirectory)/platforms/ios/build/device shows a list of files, including AppName.ipa

Is there any workaround for this issue?

@anatolybolshakov
Copy link
Contributor

@sergiuturus as a workaround at the moment - you can just set the path to ipa file more specifically - so it won't contain broken symlinks

@anatolybolshakov
Copy link
Contributor

Hi @ahmadkhudeish @sergiuturus we have rolled out the fix for this issue - I'm closing it at the moment, please feel free to reopen or let us know if this issue still actual for you.

@anatolybolshakov anatolybolshakov removed the awaiting deployment Related changes are waiting for deployment to be completed label Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.