-
Notifications
You must be signed in to change notification settings - Fork 42
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
ThinkboxDockerImages type is not compatible with RenderQueueProps #818
Comments
Note: If this turns out to be something that we need to fix in the example, rather than by changing the jsii version, then we'll also need to update the example in the docs: https://docs.aws.amazon.com/rfdk/latest/guide/first-rfdk-app.html#_define_a_deadline_render_farm |
Same problem appears to exist for UBL. Need to use https://docs.aws.amazon.com/rfdk/api/latest/python/aws_rfdk.deadline/ThinkboxDockerImages.html#aws_rfdk.deadline.ThinkboxDockerImages.for_usage_based_licensing instead of just passing the ThinkboxDockerImages. |
Just tried this with the latest JSII and it has the same issue. |
Even with the work around listed in this issue, it looks like Python bridge of JSII does not generate a compatible interface. |
For anyone finding this ticket before v1.1 of the RFDK is released with the fix, the problem was indeed with marshalling of types between JS and Python. The actual workaround will look like:
i.e. Explicitly create a RenderQueueImages from the remote_connection_server property of ThinkboxDockerImages A similar change, using UsageBasedLicensingImages would fix the similar problem with the UsageBasedLicensing's argument. |
Customers are reportedly seeing a stack trace when trying to use the Python version of the All-In-AWS-Infrastructure-Basic example. Stack trace below.
My guess is that the type checking of jsii (the package that translates Python to Javascript for the constructs) improved their type checking, and that somehow didn't get caught when we tested; very odd...
So, a strict type checker would think that the types are not compatible. A less strict type checker that just does duck-typing, like jsii previously did, would be fine with it.
Workaround
See comment below
Environment
Other
Stack trace:
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: