wheel build fails - no error message

[tonkolviktor]

trafficstars

Hello,

Thanks for the development it's in heavy use at our side :)

We have the following problem:

• our configs and setup was tested during 0.7.* times
• now developers started using 0.8.* (0.8.7) and our dbx deploy fails
• the big problem is that the actual stderr and stdout of the build is not printed (which is good normally, but not in case of an error)
• thus we have no way to know what to do

Expected Behavior

• print all related error files (focus of this ticket) (- ideally do the build without error :))

Current Behavior

• no error details visible

Steps to Reproduce (for bugs)

• ?
• we have a pretty normal pip package

Context

Your Environment

• dbx version used: 0.8.7
• Databricks Runtime version: 10.4 LTS

[copdips]

could you please run directly /use/bin/python3 -m pip wheel -w dist -e . --prefer-binary --no-deps, and copy the error message ?

[tonkolviktor]

thanks for your answer. the error comes on my collegue machine and he's out for the week.

However that's also kind of not too relevant, my goal by opening this ticket was to ask you to print the stderr/out.

More specifically https://github.com/databrickslabs/dbx/blob/8dc436d7d1f9604583735f13f2fb2bf94ff5e8f0/dbx/api/build.py#L28 This message is not too helpful, if you could do something like: dbx_echo("\n💥Command execution failed, \nstdout:{exc.stdout} \nstderr:{exc.stderr}")

[copdips]

thanks for your answer. the error comes on my collegue machine and he's out for the week.

However that's also kind of not too relevant, my goal by opening this ticket was to ask you to print the stderr/out.

More specifically

https://github.com/databrickslabs/dbx/blob/8dc436d7d1f9604583735f13f2fb2bf94ff5e8f0/dbx/api/build.py#L28

This message is not too helpful, if you could do something like: dbx_echo("\n💥Command execution failed, \nstdout:{exc.stdout} \nstderr:{exc.stderr}")

yes, this would be helpful, at least my pypi password is masked by the stdout.

[gpodevijn]

Hi,

Is there any update on this issue? I have the same error that happens in our CICD pipeline but it works locally on my machine.

Thanks