[ 
https://issues.apache.org/jira/browse/BEAM-12936?focusedWorklogId=680299&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-680299
 ]

ASF GitHub Bot logged work on BEAM-12936:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Nov/21 14:40
            Start Date: 11/Nov/21 14:40
    Worklog Time Spent: 10m 
      Work Description: snkalinin commented on pull request #15740:
URL: https://github.com/apache/beam/pull/15740#issuecomment-966355903


   @damondouglas both of issues that you mentioned are fixed in unstable and 
experimental releases of glibc, and I'm not sure, that update of one of main 
libraries of system to unstable version if good idea:)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 680299)
    Time Spent: 1h 40m  (was: 1.5h)

> [Playground] Code editor - Docker container
> -------------------------------------------
>
>                 Key: BEAM-12936
>                 URL: https://issues.apache.org/jira/browse/BEAM-12936
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-playground
>            Reporter: Alex Kosolapov
>            Assignee: Sergey Kalinin
>            Priority: P3
>              Labels: beam-playground-devops, beam-playground-sprint-2, 
> beam-playground-sprint-3
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> As a Playground maintainer, I want to have a Docker container with the 
> Playground frontend application for automating deployments and updates via 
> CI/CD
> Acceptance criteria:
>  # Dockerfile is prepared
>  # Dockerfile is used for built and run the application



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to