Closed Gijsreyn closed 1 week ago
@ryfu-msft If you have some time, you mind checking out this PR? I changed the logic to retrieve data when starting pip.exe
and included DSCCapabilities field.
Tested locally. All tests passed. Can you trigger the pipeline?
Tested locally. All tests passed. Can you trigger the pipeline?
Looks like we checked in some changes causing merge conflicts. Can you resolve them and I'll kick off a rerun.
confrimation itsdangerouss whatif
Should be good to go @ryfu-msft !
confrimation itsdangerouss pscustomobject whatif
itsdangerouss
Hi @Trenly, I don't know why I had to add itsdangerouss twice to the list, but afterwards, it succeeded. FYI.
Hi @Trenly, I don't know why I had to add itsdangerouss twice to the list, but afterwards, it succeeded. FYI.
Interesting; @jsoref might know
I'm not sure what's going on with itsdangerouss
either... very strange. I'm currently poking a couple of other bugs I've turned up. Once i've cleared them, I'm going to take a deeper dive here...
For itsdangerouss
, my guess is that the allow file is missing a new-line-at-eof
-- which is confirmed by https://github.com/check-spelling-sandbox/winget-dsc/commit/b47129778cfbeba581896b2af336ba826ebcf500.patch clearing the problem up in https://github.com/check-spelling-sandbox/winget-dsc/actions/runs/11707189285. I thought check-spelling had enough checks to warn about that instead of breaking -- I should be able to fix that shortly.
Note that itsdangerouss
should be able to go into expect.txt
instead, and it should probably be possible to construct a string that is composed of dictionary words and possibly punctuation instead of using something that isn't in the dictionary. depending on things, that could be: its-dangerous
, itsDangerous
, its1dangerous
, itsdangerous_
its_dangerous
, or something else. The trailing s
in itsdangerouss
feels like a typo.
Good point and Kaleb reminded me as well to add it to the correct files.
Thanks for the heads-up about itsdangerouss
, I'm tracking it here:
/azp run
/azp run
itsdangerouss
@ryfu-msft I checked the logs and I saw what went wrong. Just commited a fix that makes sure the package is always uninstall, before doing whatif to meet the satisfaction
:x: Errors | Count |
---|---|
:x: forbidden-pattern | 25 |
See :x: Event descriptions for more information.
/azp run
:x: Errors | Count |
---|---|
:x: forbidden-pattern | 25 |
See :x: Event descriptions for more information.
@Gijsreyn , you still have issues with spelling, you can probably avoid having to mess with that if you just did something simple like invalidPackageName
/azp run
@ryfu-msft I went with the suggestion from Josh, but just changed it.
I'm doing something terrible wrong Ryan. Shouldn't be writing code when I'm death tired. Sorry for the tiny commits.
/azp run
I'm doing something terrible wrong Ryan. Shouldn't be writing code when I'm death tired. Sorry for the tiny commits.
Haha no need to apologize. Thank you for your contribution, this is really great. Everything looks good to me, lets get this checked in and published!
This PR adds WhatIf support.