I'm having problems adding a new notification hub using the Azure web portal. The distribution fails and when viewing more information it says "Bad request".
I'm trying to add the notification hub by:
Clicking "All resources"
Clicking "Add"
Clicking "Notification Hub"
Entering all the information choosing an existing resource group
Clicking the button "Create"
Getting "Distribution failed" with error message "Bad request"
Anyone else having the same problem?
There was a transient issue creating Notification Hubs at that moment. This issue is now resolved and we are not expecting it to happen again.
Thanks,
Karl
Related
After attempting to sign into GitHub Copilot in VS Code a prompt pops up "The extension 'GitHub Copilot' wants to sign in using GitHub" and it gives me the option "Allow" or "Cancel".
After allowing another prompts states "Allow an extension to open this URI?".
After clicking "Open" an error message says
GitHub Copilot could not connect to server.
Extension activation failed: "network error".
On occasion the actual approval page pops up and I approve permissions, then get a popup in vs studio, click open then it fails on "Network Error"
How do I go about resolving this issue?
I tried the above. Was expecting to be signed into GitHub copilot after approval.
Check first if the issue persists.
There was a recent incident with Copilot
We see authentication failures for a small percentage of users.
We are investigating the root cause and will update as we learn more.
It is resolved, but you might still see some side-effect.
I am doing an exercise where I've a forked repository, and started a heroku account, did "create a new app" and "deploy with github" but when I go to connect to github, a red error message pops up saying "Error: remote could not connect or was closed."
I have had no problems connecting github to other services, and I've found other people with connection issues, but more along the lines of "why isn't my app working" and mine is" why can't i link the two so I can continue with this exercise?"
Any help is greatly appreciated.
I've followed the instructions after setting up a heroku account, having an app repository fork on github, confirming my email, "create a new app" option on heroku, and on the ensuing "deploy" tab, clicked on the "connect github" option. I expected it to work.
Yes this is a known issue and caused by some data breach related to Github Authorization. Security measures have taken place and Github authorization has been disabled until further notice. Please see
https://github.blog/2022-04-15-security-alert-stolen-oauth-user-tokens/
And based on this ongoing incident,
As reported yesterday, revocation of all OAuth tokens from the Heroku
Dashboard GitHub integration is complete. Until further notice, we
will not issue OAuth tokens from the Heroku Dashboard. These actions,
based on our current understanding of the issue, should prevent
unauthorized access to your GitHub repositories.
We will continue to work with GitHub to provide additional guidance on
how to review your GitHub logs for evidence of exfiltration or
malicious activity. Please reach out to security#salesforce.com with
any information that may assist us with our ongoing investigation.
Please continue to visit status.heroku.com for the latest updates.
If you still want to deploy, you can switch from GitHub to Git quite easily, please read this: https://help.heroku.com/CKVOUPSY/how-to-switch-deployment-method-from-github-to-heroku-git-with-all-the-changes-app-code-available-in-a-github-repo
It is time we enabled the Continuous Integration of the build pipeline, so when I went to do just that, i am seeing something strange...
The trigger appears to be enabled? yet theres a message suggesting webhooks are missing to the repo and need to be restored. When i click restore, it fails!
The remote repository’s webhooks are missing or incorrect.
An error occurred while restoring the trigger’s webhook: Could not recreate the subscription. An error was encountered while creating the existing subscription: Unable to configure a service on the selected Bitbucket repository. Bitbucket returned the error 'Your credentials lack one or more required privilege scopes.'.
I asked the admin of the repo to try restoring it because i thought maybe this is a permissions issue, and even he got the error...
This is what the repository settings page shows for both myself and the repo developer/admin...
Do we have to add a webhook manually on bitbucket?
After debugging the issue further with the developer, it appears the app password we created in bitbucket may not have had the "Webhooks" option enabled.
Unfortunately, we cannot edit app passwords in Bitbucket, which is a bad constraint but whatever.
We ended up just creating a new app password, and enabled Webhooks permissions this time, then i updated the service connection with this new app password, and wala, it worked!
I am trying to transfer ownership of a repo that I started to another github account. I get the notice in my gaining account that asks for permission of transfer. I click on the link in the email. Github responds with "Sorry, this repository transfer can’t be finished." Is there a source to figure out why?
I just successfully transfered my first repo just before trying this repo and everything went good. successful transfer. Just having problems with this second one.
Seems like for me, the problem was that I needed to log into the receiving account before accepting from the email.
I mistakenly solved this by clearing browser cache in IE. Too simple.
I am trying to make vsts email me with a detailed transcript of why a test or build fails. At the moment all I am getting is te following email:
All this mail tells me that a test has failed but not what test or what the problem is. It does give me a link to open the build report in web access which has all the information about the type of error and even the stacktrace.
Is there a way to get this detailed information (error message and stack trace) into the email or can i make vsts send a custom email with this information?
It seems you are using VSTS default notification template (as a build fails template).
For now, there is no way to custom the notification template. And there has an user voice Customise VSTS email templates which suggest this feature. You can vote and follow up.
The workarounds for now as below:
Option 1: Click the link "Open Build Report in Web Access" for detail build logs.
Option 2: Add Send Email task at the end of your build definition, and select "Only when a previous task has failed" for run this task option, so that email will be sent if the build fails. And you can custom the email body as your need.