Conflict | A clone of the Discord web app | Chat library

The "GitHub" extension in question should be the microsoft/vscode-pull-request-github, which, in its issues, does not mention anything about active and unknown at all.

I just tested on my VSCode 1.57, and clicking on that link does work.

Try and disable other plugins installed to see if one might cause the issue.

The OP JimBoyLim confirms in the comments:

I finally just reinstalled VSCode, and now its working!

IIUC, try:

Your immediate issue is that T: GarbageBin<'a, 'b> where 'a and 'b are parameters of create_bin_with_rubbish and must therefore outlive calls to that function—but the actual lifetimes passed to T::new are only internal to the function and do not therefore satisfy those bounds.

Instead of parameterising create_bin_with_rubbish with lifetimes 'a and 'b, one way to resolve this would be to use instead an HRTB (higher-ranked trait bound):

The doc says

INSERT with an ON CONFLICT DO UPDATE clause is a “deterministic” statement. This means that the command will not be allowed to affect any single existing row more than once; a cardinality violation error will be raised when this situation arises. Rows proposed for insertion should not duplicate each other in terms of attributes constrained by an arbiter index or constraint.

So if you have a conflict on data2 on more than two rows, it will throw an error

Mind that if people update their Google Form response, the submission row in the spreadsheet will not change - only the content.

• You can retrieve the latest submitted / modified form response row with the event object event.range (provided your function is bound to a Google Sheets form submit trigger)
• You can compare the modified row to the last row in the sheet
• If the form response row is equal to the last row - a new response has been submitted

Sample:

Finally I found one way to retrieve the edited row by using e.range method. So basically I created another sheet inside the same spreadsheet. When there is a new submission, it will automatically copy the new submission to the second sheet. And when there is an edited submission, it will go through the copy sheet to find the edited row, and then edit it (as well as the calendar). Credit to Tedinoz

The question is what are you trying to achieve.

keep all the commits on feature branch, only rebase them on top of develop branch

In this case you did exactly right. You rebase feature branch on top of develop branch and you must resolve all conflicts.

Squash feature branch on top of develop branch

In this case you can avoid resolving conflicts by:

Your migration will result in such table:

There is no extension like "Cypress GitHub app" in azure devops, so it is impossible to achieve exactly the same function as in github pull request.

As a workaround , you can try to add status policy.

Using status alone, details from an external service can be provided to users within the PR experience. Sometimes, sharing information about a PR is all that is necessary, but in other cases PRs should be blocked from merging until requirements are met. Like the in-box policies, the Status policy provides a way for external services to block PR completion until requirements are met. If the policy is required, it must pass in order to complete the pull request. If the policy is optional, it is informational only, and a status of succeeded is not required in order to complete the pull request.

External services can use the PR Status API to post detailed status to your PRs. The branch policy for external services brings the ability for those 3rd party services to participate in the PR workflow and establish policy requirements. This article guides you through the process of configuring a branch policy for a service that is posting PR status.

In addition, here is a ticket about how to create required pull request status check, you can refer to it.