-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Encountered a 'null' in 'list', this is illegal in Besom #518
Comments
The value that trips besom is the following:
The full structure (edited for privacy):
|
Hi @jchapuis, yeah, this is, in fact, provider misbehaving (or just schema being borked). I just checked and 1.47.0 is the latest version so there was an update of the provider itself (latest released for Besom is I do have a hack, however. If you are interested in solving this quick and dirty, you could clone our repo and publish locally a hotfixed artifact of |
@lbialy excellent, thanks a lot for the quick answer, makes sense, and good idea on the granular field access. Thanks also for the procedure for custom packages, great to know, I might follow that or just hardcode the values I'm missing for the moment, let's see |
@jchapuis you might want to checkout a tag ( |
Hello there 👋 we are stuck with the confluent provider due to the following trace.
It could be that the provider is mibehaving. However, in our case, we are not interested in this particular list value which can't be decoded but some other properties from the result type.
Would there be anything you can propose as a workaround? This is blocking for us atm.
The text was updated successfully, but these errors were encountered: