Parse.com CloudCode deploy failing - requested resource was not found [closed] - parse-platform

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I am using Parse.com CloudCode to create some custom functionality for an iOS app.
To deploy a CloudCode app you use:
terminal% parse deploy
Everything was working fine and I was able to upload my cloud code to the backend but suddenly it stopped working and I absolutely don't know why. I am getting this response:
requested resource was not found
EDIT:
The main.js is there, that is the file that has the changes. I tried to delete and recreate the app. The config is also correct. I restarted my computer, reset the connection, but still getting that response. Here is the full Terminal response after running % parse deploy:
% parse deploy
Uploading source files
Uploading recent changes to scripts...
The following files will be uploaded:
/path/to/main.js
Deploy failed. Retrying deploy...
Uploading source files
Uploading recent changes to scripts...
The following files will be uploaded:
/path/to/main.js
Deploy failed. Retrying deploy...
Uploading source files
Uploading recent changes to scripts...
The following files will be uploaded:
/path/to/main.js
Deploy failed. Retrying deploy...
Uploading source files
Uploading recent changes to scripts...
The following files will be uploaded:
/path/to/main.js
Deploy failed. Retrying deploy...
Uploading source files
Uploading recent changes to scripts...
The following files will be uploaded:
/path/to/main.js
requested resource was not found
Did anybody have the same or similar problem? If yes, what steps helped to resolve this issue?
Thanks in advance.

The newly released update has fixed this problem for me. You can either update using parse udpate or use curl curl -s https://www.parse.com/downloads/cloud_code/installer.sh | sudo /bin/bash

I´m using it on JavaScript and just spamming "parse deploy" till the main.js is update do the work.
Is not nice, but it works :)

Related

Gitlab deploy to heroku failure [duplicate]

This question already has an answer here:
Deploy on heroku with dpl not working with new farady version
(1 answer)
Closed last year.
Gitlab fails to deploy to heroku when I push.
When I first encountered the issue I referred to this link for configuration guidance. however when I push gitlab throws a RuntimeError that "ensure adapter! ": An attempt
to run a request with a Faraday:: Connection without adapter has been made.
In the process of trying to fix the issue I landed on this repo. Can anyone enlighten me on this?
I had the same problem and I solved with this:
https://github.com/travis-ci/dpl/issues/1247
Mentioned in this topic:
Deploy on heroku with dpl not working with new farady version

How to ensure AWS S3 cli file sync fully works without missing files

I'm working on a project that takes database backups from MongoDB on S3 and puts them onto a staging box for use for that day. I noticed during a manual run today I got this output. Normally it shows a good copy of each files but today I got a connection reset error or something one of the files, *.15, was not copied over after the operation had completed.
Here is the AWS CLI command that I'm using:
aws s3 cp ${S3_PATH} ${BACKUP_PRODUCTION_PATH}/ --recursive
And here is an excerpt of the output I got back:
download: s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-production.10
to ../../data/db/myorg-production/myorg-production.10
download: s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-production.11
to ../../data/db/myorg-production/myorg-production.11
download: s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-production.12
to ../../data/db/myorg-production/myorg-production.12
download: s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-production.13
to ../../data/db/myorg-production/myorg-production.13
download s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-production.14
to ../../data/db/myorg-production/myorg-production.14
download failed: s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-produc
tion.15 to ../../data/db/myorg-production/myorg-production.15 ("Connection broken: error(104, 'Connection reset by peer')", error
(104, 'Connection reset by peer'))
download: s3://myorg-mongo-backups-raw/production/daily/2018-09-10/080001/data/s-ds063192-a1/myorg-production/myorg-production.16
to ../../data/db/myorg-production/myorg-production.16
How can I ensure that the data from the given S3 path was fully copied over to the target path without any connection issues, missing files, etc? Is the sync command for the AWS tool a better option? Or should I try something else?
Thanks!

Laravel Spark - Cannot connect to repo

So, I recently made two big changes ... moved my code from bitbucket to github, and set up a pipeline on heroku with a new staging app (original app is now production).
I got a new github token and placed it into the auth.json file as was done with the previous bitbucket repo (it's a private repo). However, when I push to heroku to build the code with composer there, I cannot connect with the laravel spark repo.
Error:
Installing laravel/spark (v3.0.5): Downloading (failed) Failed to download laravel/spark
from dist: The "https://api.github.com/repos/laravel/spark/zipball/512af184c15d793c33328ff03313553ea6feacba"
file could not be downloaded (HTTP/1.1 404 Not Found)
Now trying to download from source
Installing laravel/spark (v3.0.5): Cloning 512af184c1
[RuntimeException]
Failed to execute git clone --no-checkout 'https://***:***#github.com/laravel/spark.git' '/tmp/build_9916d292e7eb72e0fbe34f47e3d9854c/vendor/laravel/spark' && cd '/tmp/build_9916d292e7eb72e0fbe34f47e3d9854c/vendor/laravel/spark' && git remote add composer 'https://***:***#github.com/laravel/spark.git' && git fetch composer
remote: Repository not found.
fatal: repository 'https://***:***#github.com/laravel/spark.git/' not found
What I have tried ...
Setting the github api token on heroku with
heroku config:set GITHUB_API_TOKEN=<token>
Setting the composer github token
composer config -g github-oauth.github.com <token>
I am connected to the Laravel Spark repo on github and when I run composer on my local machine I am not prompted for a spark token. Every other dependency that I have runs fine - I can change the auth.json and that is not the case, so I don't think this is a problem with lack of access to my github.
Does anyone know how Laravel - Spark checks to grant access and how we can check to see where we are going wrong? There should be a checklist of things that can be looked at if access is denied.
Any help is appreciated. Been stuck for almost a week. I really need some way to figure out how to connect to the Spark repo.
(Edit) Spark is a composer satis repo. I can't really find any info on how to prompt this type of repo to tell me why I can't clone it or how best to communicate with it.
(Edit 2) Also tried changing the git config to ensure that it had the right token. This should be overwritten by the files, but I tried it anyway.
git config github.accesstoken <token>
The response from the software providers is to use an alternative method and place the code under my source control so that composer is not trying to load it. I do not wish to do this for a number of reasons. Again, I need a way to clone the satis repo in composer.
Edit 3: I have also tried going to the URL of the repo and attempting to access one of the versions. This displays the same error as when you go to the URL in the error directly (it's the same URL).
{
"message": "Not Found",
"documentation_url": "https://developer.github.com/v3/repos/contents/#get-archive-link"
}
This seems to back up the belief that this is not a composer issue, but something to do with a github setting or spark setting.
Edit 4: It occurred to me that my problems started after upgrading to V6 and I am getting denied access to the spark repo containing versions 1-5 and version 6 is separate. I upgraded my spark version to 6 and had access to that repo. I then tried uploaded the code base to heroku that had version 6 but was denied access to the repo there.
I also tried ...
heroku config:set github_oauth=<token>
Edit 5: I noticed that the output from pushing to heroku included the phrase
NOTICE: Using $COMPOSER_GITHUB_OAUTH_TOKEN for GitHub OAuth.
In response, I found an article asserting that the oauth token should be set in the config portion of composer.json as ...
"config": {
"github-oauth": {
"github.com": "<token>"
}
}
I tried it, but it didn't work
So, it turns out there were several issues. The final big one was that for some reason, I had to delete my api personal token used for github access and create a new one with full privileges for everything. Once that was set up, I had access and was able to reduce the privileges to repo only.
https://github.com/ladybirdweb/agorainvoicing Use open source Agora Invoicing software. It has all the tools you need to start software selling business. It is build on Laravel framework and is very similar to Laravel Spark

Upload to aws s3 file via curl [duplicate]

This question already has answers here:
Uploading to Amazon S3 via curl route
(3 answers)
Closed 4 years ago.
I'm trying to upload a report to a aws s3 server and im the soluctions I have found aren't working I keep getting either a sha264 error or The authorization header is malformed. I'm clueless regarding sh and doing a post in curl and files and on how to upload. Also after uploading I need to generate a download link. Also this sh is to be run on jenkins.
This is one of the solutions I looked into:
s3 bash upload
Solution, is invalid since the authorization mechanism isn't supported anymore.
Below is the error I get:
<Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; the authorization component "Signature=" is malformed.</Message><RequestId>182183F5B97F9258</RequestId><HostId>s3MwGZUpioyk+3Qfj0q51LqY4iosCEC84xThxscQFPwX4SbvJk66oi4qIyEaVkdNLUGL1CciXlY=</HostId></Error>%
Better use a proper command, s3cmd :
Check http://s3tools.org/s3cmd
(the right tool for the right job...)
Or the aws command :
aws s3 sync /tmp/foo s3://bucket/

Build Failed from Dev to Staging using TFS Release management

I am trying to build a project from dev to staging environment, what all i did was just to merge the changes in dev to staging and trigger a build. but the build got failed even tried multiple times.
Below is the log file shared in google drive. there are no errors mentioned in the log file. Can anyone help me solve this problem.
https://drive.google.com/open?id=0B85ZmWDiKYHRVmN4MlMxc0ZEd28
I found a error in the log file in the release management, which says that "access denied for appsettings.config" file. I did remove the read only on the folder in the server and it worked. I am not sure of this fix properly, but it did work for me.
Thanks.

Resources