Git push error, fatal: HTTP request failed - ruby-on-rails

I have been working on this rails project for weeks (it is deployed using Heroku), pushing to GitHub frequently without a problem. I am now getting this error:
error: The requested URL returned error: 504 while accessing
https://github.com/my_git_name/my_repository_name.git/info/refs?service=git-receive-pack
fatal: HTTP request failed
Any idea what might be causing this? Thanks!

I have already seen that 504 error message in conjunction with GitHub trouble.
And that seems consistent with last night GitHub status message:
21:51 UTC We are currently working to resolve problems affecting a subset of repositories on a single fileserver.
So, if the error message is now gone, that would confirm the possibility of a server-side (GitHub) issue, as opposed to a more permanent client-side problem.

Related

Jenkins An Error Occurred While Reading Response

Ever since I upgraded from Jenkins 2.2x to 2.36 my Login with IDP isn't working despite the configuration in settings remaining unchanged. I am using Ping for SSO and Ping does indeed authenticate, but after authentication Jenkins throws an error: "An error occurred while reading response." Picture of error is attached.
I talked to my company's SSO guy and after extensive work he couldn't find the problem. Also did extensive research and couldn't find much regarding this problem.
*SAML plugin came out with update that solved the issue

HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit aspnetcore6.0

I am facing below issue while switch VS2019 to VS2022. I am not able to run my API project its throwing below error. I Search on google and look many articals but not got success. Please suggest to resolve this problem. I checked and found that .netCore upper version not support to old version code.
HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
Common solutions to this issue:
ANCM failed to start after -1 milliseconds
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect

Getting 503 Error on Google Dataflow - UNAVAILABLE

I'm trying to run apache beam python pipeline on dataflow but immediately (10-15sec) after launching the job, it gets failed status.
The error on logs:
Failed to start the VM, launcher-2021030302333314603154945777358700, used for launching because of status code: UNAVAILABLE, reason: One or more operations had an error: 'operation-1614767615027-5bc9f6216a93c-7b50752f-842a8707': [UNAVAILABLE] 'HTTP_503'..
The error message gets cut short so I cannot dig into deeper. I believe I added all relevant permissions etc. but cant get it to work. Initial research suggests that it could be a backend issue or permissions issue?
In addition the same pipeline has worked in other projects.
Appreciate if someone can help me debug and fix.
It is because of the region. I move the region from 'asia-southeast2' to 'us-central1' and it worked.

Intermittent CLI API 500 when Downloading File

I'm using a gdrive CLI command on a Jenkins web node to automatically download a file from Google Drive during a build process.
This use to work, however, recently (As of a week or two ago) the command to download the file intermittently started producing 500 errors with no message.
The command that's being run is: gdrive download query "name = '16.7.3.zip'".
Sometimes the above command downloads the file, but, sometimes it doesn't. Here's an example of the error output:
Is anyone able to give advice on where to start with this issue, is it something on Google's side?
I've read a few articles explaining that this might be throttling from the API, however, I'd have expected a different error code, i.e. 403 with the error "The download quota for this file has been exceeded.".
I have the following specs installed:
gdrive: 2.1.0
Golang: go1.6
OS/Arch: linux/amd64
Intermittent 500 errors are allowed for in the Google Drive API. You simply need to do an exponential backoff and retry. Generally they are caused by internal timeouts within the Drive infrastructure. Sometimes these are related to service problems, other times they can be caused by a request that causes a large amount of work.

Sun Application Server Error : Error commiting response java.io.IOException: Broken pipe at sun.nio.ch.FileDispatcher.write0(Native Method)

Sometime i will encounter this error after multiple access of my web application
I am using Sun Application Server Platform Edition 8.2
What is the reason for encountering this error and how to resolve it.
File system permissions issue perhaps. Need more information for a better answer.

Resources