setup-go | Set up your GitHub Actions workflow with a specific version of Go | BPM library

I'm trying to setup DVC with Google Drive storage as shown here. So far, I've been unsuccessful in pushing data to the remote. I tried both with and without the Google App setup.

After running a dvc push -v, the following exception is shown:

I've set up a GitHub workflow to start a Postgres instance inside a docker container. I then execute my web API to simply prove it connects. This satisfies the workflow.

My workflow

I'm learning Go and want to make use of GitHub Actions. Everything is fine when working with just one package. But as soon as I define more than one package (more than the main package), I get stucked. On my desktop it does compile, but by using Actions script it does not and ends up in following error:

I have a simple go package, but during testing within Github Actions, it is failing with this error:

##[error]keywords.go:8:2: cannot find package "github.com/securisec/go-keywords/languages" in any of:.

When I run the tests locally (I am using go mod), all the tests works fine.

For Github actions, I have tried setting GO111MODULE to both on and off, but still getting the same error.

The error can be observed here. My testing workflow is:

Currently we are migrating from GitLab to GitHub and we've decided to move the CI/CD process to GitHub actions. The pipeline process works like a charm but when GKE tries to spin up the newly pushed image it gives back this error:

'OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/socket-server\": permission denied": unknown'

It's important to note here that this whole process was working on GitLab. Anyway, the GitHub workflow yaml file looks like this:

I want to run golint on windows in GitHub Actions.

I'm trying to write a custom attribute value (into AAD B2C) during a sign-up with email invitation.

It works well with AAD B2C local accounts.

It doesn't work with Google accounts.

I use a combination of :

• the SocialAndLocalAccounts version of the starter pack : https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/tree/master/SocialAndLocalAccounts
• the "sign-up with email invitation" example provided by the community : https://github.com/azure-ad-b2c/samples/tree/master/policies/invite
• Microsoft's documentation to set-up Google custom policies : https://docs.microsoft.com/fr-fr/azure/active-directory-b2c/active-directory-b2c-setup-goog-app
• some custom attributes exemples : https://medium.com/the-new-control-plane/working-with-custom-attributes-in-azure-ad-b2c-custom-policies-fae1454b12bf et https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-create-custom-attributes-profile-edit-custom#next-steps

Here is the custom attribute that I use :

I'm trying to get an AspNet Core 2.1 website to authenticate via Azure AD B2C. I've configured the Google and Microsoft Account signups in my tenant per the online instructions I found (e.g., this for Google).

But neither signup/signin option works. Links to them display on the default Azure AD B2C login page, but clicking the links triggers an error:

• for Google, it causes a redirect_uri_mismatch error

• for Microsoft Account, it returns a "we're experiencing technical difficulties" error page, which has persisted for more than 24 hours, so I doubt there's been any kind of outage

This is all occurring in a development environment, so I'm not using a publicly-registered domain (e.g., the reply uris all point back to localhost). Is that possibly the problem? If so, how do I set up the development environment correctly?

Additional Info

I solved the problem with the google identity provider.

But I'm still getting the same error with the Microsoft Account provider. However, I just noticed that there's an error message buried within the URL for the error page which doesn't get displayed on the page itself:

error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.

The first suggestion in the error message -- targeting login.live.com -- doesn't work. The Microsoft Application Portal complains about a domain mismatch.

But I don't see how to apply the second suggestion, because I don't know where the redirect_uri is generated by/stored in my web app (i.e., I defined the redirect uri in the Microsoft Application Portal, but I don't see a corresponding configuration parameter in my webapp).

NOTE it's not a duplicate of this question or this question.

How to build Googletest from source using g++ into a shared library (.so)?

I tried the steps described in Google Test's document on how to build a shared library, but linking the produced libgtest.so with my test programs didn't work - the linker throws tons of errors like:

"gtest-all.cc:(.text+0x19b50): multiple definition of `testing::internal::HasNewFatalFailureHelper::~HasNewFatalFailureHelper()'libgtest.so:gtest-all.cc:(.text+0x19b50): first defined here ./libgtest.so: In function `testing::internal::HasNewFatalFailureHelper::~HasNewFatalFailureHelper()':" gtest-all.cc:(.text+0x19bc4): multiple definition of `testing::internal::HasNewFatalFailureHelper::ReportTestPartResult(testing::TestPartResult const&)' libgtest.so:gtest-all.cc:(.text+0x19bc4): first defined here ./libgtest.so: In function `testing::internal::TypedTestCasePState::VerifyRegisteredTestNames(char const*, int, char const*)':

When building libgtest.so, I used command:

g++ -fPIC -DGTEST_CREATE_SHARED_LIBRARY=1 -pthread -c $(GTEST)/src/gtest-all.cc -shared (this macro is required in the aforementioned Google Test's document) and then mv gtest-all.o libgtest.so

When linking with libgtest.so, I used load flag -DGTEST_LINKED_AS_SHARED_LIBRARY=1, as recommended in the aforementioned Google Test's document. I also used -L flag to tell g++ where the library is.

NOTE: if I choose to build a libgtest.a archive from source and link my test program with this archive, everything is fine (instructions on how to build it is also in that Google Test document). The reason why I'd like to switch from libgtest.a to libgtest.so is I want the executables to load GoogleTest at runtime so linking might be faster.