Add requests-ntlm output to requests_ntlm feedstock

[wshanks]

Checklist:

• I want to add a package output to a feedstock:
  • Pinged the relevant feedstock team(s)
  • Added a small description of why the output is being added.

ping @conda-forge/requests_ntlm

This is following up the suggestion made in regro/cf-scripts#5250 (comment) and discussed in conda-forge/requests_ntlm-feedstock#6

[wshanks]

I am still seeing failure in conda-forge/requests_ntlm-feedstock#7 where I try to add the new output package. @beckermr when should this take effect?

[h-vetinari]

It should take effect very quickly; if it still hasn't worked after 8h, then likely something went wrong somewhere... At least, I double-checked the spelling in this PR and can find no mistakes. From the PR your referenced, this is how the validation still looks like

validation results:
{
  "noarch/requests-ntlm-1.3.0-h795da4c_2.conda": false,
  "noarch/requests_ntlm-1.3.0-pyhcf101f3_2.conda": true
}

[beckermr]

I found the bug but won't be able to fix and cleanup until tomorrow.

[wshanks]

Is there somewhere I can watch to know when the requests-ntlm output has been added?

[beckermr]

Hi Sorry. The issue is that this yaml bit

action: add_feedstock_output
feedstock_to_output_mapping:
  requests_ntlm: requests-ntlm

was misinterpreted by the code. It interpreted the string requests-ntlm as a list and made outputs for each character. 🤦

@isuruf changed how this is formatted recently and somehow this edge case isn't working.

[h-vetinari]

It interpreted the string requests-ntlm as a list

Ah, good find! Well yeah, the new format requires a list. We should error if we find a bare string, instead of listifying it (or alternatively, error if we find that the list is comprised of single characters)

[beckermr]

Ok this is fixed and the output should be present momentarily. We need to go in and cleanup the outputs from the buggy code.