[
https://issues.apache.org/jira/browse/BEAM-11227?focusedWorklogId=580282&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-580282
]
ASF GitHub Bot logged work on BEAM-11227:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Apr/21 19:54
Start Date: 09/Apr/21 19:54
Worklog Time Spent: 10m
Work Description: suztomo edited a comment on pull request #14474:
URL: https://github.com/apache/beam/pull/14474#issuecomment-816871115
Another case
https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/17051/. With
`org.gradle.caching=false`, the build console stopped showing progress after 1
hour 16 minutes. With jstack, I got following stacktraces:
https://gist.github.com/suztomo/7757ac7b1df2ad33934bb51adcc8f375
```
14:16:35 "pool-123-thread-1" #179 prio=5 os_prio=0 tid=0x00007f3ee0ed6000
nid=0x4bd waiting on condition [0x00007f3e8e0e9000]
14:16:35 java.lang.Thread.State: WAITING (parking)
14:16:35 at sun.misc.Unsafe.park(Native Method)
14:16:35 - parking to wait for <0x00000000e4f96648> (a
java.util.concurrent.CountDownLatch$Sync)
14:16:35 at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
14:16:35 at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
14:16:35 at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
14:16:35 at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
14:16:35 at
java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
14:16:35 at
org.apache.beam.runners.fnexecution.logging.GrpcLoggingServiceTest.lambda$testMultipleClientsFailingIsHandledGracefullyByServer$2(GrpcLoggingServiceTest.java:122)
14:16:35 at
org.apache.beam.runners.fnexecution.logging.GrpcLoggingServiceTest$$Lambda$425/31993368.call(Unknown
Source)
```
```
14:16:35 at
java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:244)
14:16:35 at
org.apache.beam.runners.fnexecution.logging.GrpcLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer(GrpcLoggingServiceTest.java:127)
```
Previous one was BeamFnLoggingServiceTest. This one is
GrpcLoggingServiceTest. Problem with logging?
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 580282)
Time Spent: 116.5h (was: 116h 20m)
> Upgrade beam-vendor-grpc-1_26_0-0.3 to fix CVE-2020-27216
> ---------------------------------------------------------
>
> Key: BEAM-11227
> URL: https://issues.apache.org/jira/browse/BEAM-11227
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Affects Versions: 2.21.0, 2.22.0, 2.23.0, 2.24.0, 2.25.0
> Reporter: Boury Mbodj
> Assignee: Kenneth Knowles
> Priority: P1
> Labels: apache-beam, beam
> Fix For: 2.29.0
>
> Time Spent: 116.5h
> Remaining Estimate: 0h
>
> *+Description+**:* [Apache Beam :: Vendored Dependencies :: GRPC ::
> 1.26.0|https://mvnrepository.com/artifact/org.apache.beam/beam-vendor-grpc-1_26_0]
> »
> [0.3|https://mvnrepository.com/artifact/org.apache.beam/beam-vendor-grpc-1_26_0/0.3]
> uses the dependency Eclipse Jetty (9.2.10.v20150310), which is prone to a
> privilege escalation vulnerability. This issue (CVE-2020-27216) was published
> on 23/10/2020.
> *+Affected Versions:+*
> Eclipse Jetty versions 9.4.32.v20200930 and prior, 10.0.0.beta2 and prior
> and 11.0.0.beta2 and prior.
> *+Recommendation/+* *+Update Suggestion:+*
> Update the Eclipse Jetty dependency to version 9.4.33.v20201020,
> 10.0.0.beta3, 11.0.0.beta3 or later.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
