New package: EFLFE.PingoMeter version 0.9.9

[grigoryvp]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[stephengillie]

Automatic Validation ended with:

Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\pingometer.exe returned exit code: -1073741819
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\pingometer.exe returned exit code: -532462766

Automated error analysis suggests -1073741819 may mean Converted to hexadecimal (C0000005) possibly Access Violation. (This is occasionally seen in PRs despite the install otherwise being successful. Should it be added as an InstallerSuccessCode or similar here?)

Automated error analysis suggests -532462766 may mean EXCEPTION_COMPLUS (Unhandled Exception)

(Automated response - build 896.)

[stephengillie]

Verify:

The symlink can't reach files needed by the application. Here, it's none.png. Running from the main folder gives:

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[grigoryvp]

I have used the new ArchiveBinariesDependOnPath WinGet 1.9 flag to add app's directory to the PATH. This should do the trick!

[grigoryvp]

Updated and ready for review, I do not understand why Microsoft bot decides that there is "no activity"

[ItzLevvie]

@wingetbot run

[wingetbot]

/AzurePipelines run

[microsoft-github-policy-service]

Hello @grigoryvp,

The package manager bot determined that the ManifestVersion key does not match any version currently approved for release. Please verify the manifest file is compliant with the package manager 1.5 manifest specification or 1.6 manifest specification.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/version/error