Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add rescuetime 2.15.0.2 #717

Merged
5 commits merged into from
Jul 18, 2020
Merged

add rescuetime 2.15.0.2 #717

5 commits merged into from
Jul 18, 2020

Conversation

ousugo
Copy link
Contributor

@ousugo ousugo commented May 22, 2020 •
edited by ghost

Microsoft Reviewers: Open in CodeFlow

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@msftclas
Copy link

msftclas commented May 22, 2020 •
edited

CLA assistant check
All CLA requirements met.

@wingetbot wingetbot added the Binary-Validation-Error Indicates and error was encountered during InstallerScan test. label May 22, 2020
@ghost
Copy link

ghost commented May 22, 2020

ousugo The package manager bot determined there was an issue with one of the installers listed in the url field, and cannot continue.

Here are some common causes for this failure you should consider:

  1. The Sha256 HASH in the manifest does not match the HASH of the installer. Run winget hash to generate the hash.
  2. The URL is not valid. Make sure the URL to the installer is publicly available and valid.
  3. The installer has been identified as malware. If the installer is detected as malware, you can submit the installer to the defender team for analysis as a potential false positive.

@wingetbot wingetbot removed Binary-Validation-Error Indicates and error was encountered during InstallerScan test. Needs: author feedback labels May 22, 2020
@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added the Binary-Validation-Error Indicates and error was encountered during InstallerScan test. label May 22, 2020
@ghost
Copy link

ghost commented May 22, 2020

ousugo The package manager bot determined there was an issue with one of the installers listed in the url field, and cannot continue.

Here are some common causes for this failure you should consider:

  1. The Sha256 HASH in the manifest does not match the HASH of the installer. Run winget hash to generate the hash.
  2. The URL is not valid. Make sure the URL to the installer is publicly available and valid.
  3. The installer has been identified as malware. If the installer is detected as malware, you can submit the installer to the defender team for analysis as a potential false positive.

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@wingetbot wingetbot removed the Binary-Validation-Error Indicates and error was encountered during InstallerScan test. label May 22, 2020
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added the Binary-Validation-Error Indicates and error was encountered during InstallerScan test. label May 22, 2020
@ghost
Copy link

ghost commented May 22, 2020

ousugo The package manager bot determined there was an issue with one of the installers listed in the url field, and cannot continue.

Here are some common causes for this failure you should consider:

  1. The Sha256 HASH in the manifest does not match the HASH of the installer. Run winget hash to generate the hash.
  2. The URL is not valid. Make sure the URL to the installer is publicly available and valid.
  3. The installer has been identified as malware. If the installer is detected as malware, you can submit the installer to the defender team for analysis as a potential false positive.

@wingetbot wingetbot removed Binary-Validation-Error Indicates and error was encountered during InstallerScan test. Needs: author feedback labels May 22, 2020
@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added the Binary-Validation-Error Indicates and error was encountered during InstallerScan test. label May 22, 2020
@ghost
Copy link

ghost commented May 22, 2020

ousugo The package manager bot determined there was an issue with one of the installers listed in the url field, and cannot continue.

Here are some common causes for this failure you should consider:

  1. The Sha256 HASH in the manifest does not match the HASH of the installer. Run winget hash to generate the hash.
  2. The URL is not valid. Make sure the URL to the installer is publicly available and valid.
  3. The installer has been identified as malware. If the installer is detected as malware, you can submit the installer to the defender team for analysis as a potential false positive.

@ousugo ousugo mentioned this pull request May 22, 2020
Closed
@ghost ghost removed the Needs: author feedback label May 25, 2020
@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 717 in repo microsoft/winget-pkgs

@KevinLaMS KevinLaMS removed the Binary-Validation-Error Indicates and error was encountered during InstallerScan test. label Jul 18, 2020
@KevinLaMS
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added the Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. label Jul 18, 2020
@ghost ghost assigned denelon Jul 18, 2020
@ghost
Copy link

ghost commented Jul 18, 2020

This submission has moved to manual review.

@KevinLaMS
Update 2.15.0.2.yaml
bd7dea8 
tweaked switches
@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@KevinLaMS KevinLaMS added the Validation-Completed Validation passed label Jul 18, 2020
@ghost
Copy link

ghost commented Jul 18, 2020

Hello @KevinLaMS!

Because this pull request has the Validation-Completed label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

ghost
ghost approved these changes Jul 18, 2020
View reviewed changes
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validation has completed

@ghost ghost merged commit b174ce2 into microsoft:master Jul 18, 2020
@ousugo ousugo deleted the rescuetime branch July 21, 2020 01:29
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
Assignees

@denelon denelon

Labels
Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@ousugo @wingetbot @msftclas @KevinLaMS @denelon