liferoad opened a new issue, #33623: URL: https://github.com/apache/beam/issues/33623
### What happened? Steps to reproduce the issue: 1. Go to https://colab.research.google.com/ 2. Create a new notebook 3. Install beam ``` !pip3 install apache-beam[gcp] ``` 4. ignore any warnings and no need to restart the session 5. Do this in a cell: ``` import apache_beam as beam from apache_beam.runners.portability.prism_runner import PrismRunner with beam.Pipeline(runner=PrismRunner()) as p: N =5 p | "Create Elements" >> beam.Create(range(N)) | "Squares" >> beam.Map(lambda x: x**2) | "Print" >> beam.Map(print) ``` 6. the first run should work well but if you run the cell second time, the below error occurs: ``` OSError: [Errno 26] Text file busy: '/root/.apache_beam/cache/prism/bin/apache_beam-v2.61.0-prism-linux-amd64' ``` <img width="1639" alt="Image" src="https://github.com/user-attachments/assets/5c9b6a25-5c48-488a-bfb7-bdf18d401d9e"; /> 7. Check the running process: <img width="1141" alt="Image" src="https://github.com/user-attachments/assets/a341b97b-7d2c-4b3c-81fd-9196e4140dd8"; /> `/root/.apache_beam/cache/prism/bin/apache_beam-v2.61.0-prism-linux-amd64` is still running. If you kill this process, step 5 will run fine. ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [x] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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]
