We've had a report with uploading large numbers of files using ipfs-deploy with Fission support that you may need to increase the number of open files that your operating system supports. This could also occur with fission watch.
If you want to see what the Fission CLI is doing under the covers, you can turn on DEBUG mode by calling commands like this:
DEBUG=true fission up .
You'll see that fission up calls your locally installed ipfs command to add files to IPFS. We can see that it's using the 0.4.22 version of ipfs, installed using Homebrew in the "Cellar" where brew keeps installed items.
Then, it sends the hash of the entire directory to our web API, which pins it and fetches the files directly from your laptop and any other IPFS nodes that already have copies of those files in the network.
In this case, we can see that after the "Remote pinning Qm…", there is a 504 Gateway Time-out error from our server. This is a known issue, which we're working on to support large files / large quantities of files.