You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:00:02 UTC

[jira] [Updated] (BEAM-11039) Resolve conflicts between TFMA and Facets imports

     [ https://issues.apache.org/jira/browse/BEAM-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-11039:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Resolve conflicts between TFMA and Facets imports
> -------------------------------------------------
>
>                 Key: BEAM-11039
>                 URL: https://issues.apache.org/jira/browse/BEAM-11039
>             Project: Beam
>          Issue Type: Test
>          Components: runner-py-interactive
>            Reporter: Ning Kang
>            Assignee: Ning Kang
>            Priority: P2
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> In a trusted notebook, Facets will load automatically, and declare extra variables in the global scope (https://screenshot.googleplex.com/9J7JGH8xVUjtfqa). This can have side effects if other libraries try to declare the same variables.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)