You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may want to consider adding a namespace indicator to launcher options sooner rather than later. Right now we only have --response-address, but we might want others. For each option, there's the chance that it collides with a pre-existing parameter. This can be avoided by prefixing all parameters with a namespace which is considered good practice anyway.
Per discussion, we're going with a namespace of RemoteProcessProxy since jupyter convention is that parameter namespaces reflect the class to which they apply. This issue to Sprint 6.
We may want to consider adding a namespace indicator to launcher options sooner rather than later. Right now we only have
--response-address
, but we might want others. For each option, there's the chance that it collides with a pre-existing parameter. This can be avoided by prefixing all parameters with a namespace which is considered good practice anyway.Some proposals include:
Elyra
e.g.,--Elyra.response-address
ElyraLauncher
e.g.,--ElyraLauncher.response-address
KernelLauncher
e.g.,--KernelLauncher.response-address
This would require changes to each of the launchers such that the appropriate parameter is processed.
The text was updated successfully, but these errors were encountered: