-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"rfbrowser init" fails due to "UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 1022-1023: unexpected end of data" after latest 19.1.0 release #3938
Comments
+1 |
same error on my side for the exact same reasons |
@spicard999 your solution works, thx 👍 I wonder if it is then an issue regarding the base image from MS or the issue is within the 19.1.0 release of the lib. Anyway, changing to |
Not sure if this relates directly to this topic but since version I'm using the following configuration in my [tool.poetry]
name = "test"
package-mode = false
[tool.poetry.dependencies]
python = "^3.10"
robotframework-browser = "19.1.0" Which results in a Updating dependencies
Resolving dependencies... (1.8s)
IndexError
list index out of range
at ~\AppData\Local\Programs\Python\Python312\Lib\site-packages\poetry\repositories\http_repository.py:328 in _get_info_from_links
324│ return self._get_info_from_metadata(
325│ first_wheel
326│ ) or self._get_info_from_wheel(first_wheel)
327│
→ 328│ return self._get_info_from_metadata(sdists[0]) or self._get_info_from_sdist(
329│ sdists[0]
330│ )
331│
332│ def _links_to_data(self, links: list[Link], data: PackageInfo) -> dict[str, Any]: When I pin the version of Addition: When using any 2024-12-05 13:35:37,957 [INFO ] ==============================================================================================================
2024-12-05 13:35:37,957 [INFO ] Installing node dependencies...
2024-12-05 13:35:38,048 [INFO ] Installing rfbrowser node dependencies at /builds/<path>/.venv/lib/python3.10/site-packages/Browser/wrapper
2024-12-05 13:35:38,129 [INFO ] npm warn config production Use `--omit=dev` instead.
2024-12-05 13:35:40,626 [INFO ]
2024-12-05 13:35:40,626 [INFO ] added 81 packages, and audited 82 packages in 3s
2024-12-05 13:35:40,627 [INFO ]
2024-12-05 13:35:40,627 [INFO ] 7 packages are looking for funding
2024-12-05 13:35:40,627 [INFO ] run `npm fund` for details
2024-12-05 13:35:40,627 [INFO ]
2024-12-05 13:35:40,628 [INFO ] found 0 vulnerabilities
2024-12-05 13:35:40,646 [INFO ]
2024-12-05 13:35:40,646 [INFO ] Installing browser binaries to /ms-playwright
2024-12-05 13:35:40,646 [INFO ] npx --quiet playwright install
2024-12-05 13:35:41,479 [INFO ]
2024-12-05 13:35:41,480 [INFO ] rfbrowser init completed
2024-12-05 13:35:41,480 [INFO ] ============================================================================================================== Usually, a bunch of dependencies are downloaded. For version |
Yes, some code from rfbrowser logging side was removed to make this bug resurface. We will try to get this fixed in the next hotfix release. |
Fixed in #3951 |
Describe the bug
Our CI pipeline started failng few days ago due to problems with
rfbrowser init
command. We have discovered that it is due to the latest 19.1.0 version ofrobotframework-browser
. After downgrading it to 19.0.1 initialization works fine. The issue does not seem to occur on Windows, but in our Docker image built on Ubuntu 22.04 (Jammy) it keeps failing (the Dockerfile for reproducing the bug is attached in the reproduction section). Below is the error stack trace when using the newest release:To Reproduce
Steps to reproduce the behavior:
requirements.txt
with following dependencies:requirements.txt
):You will receive the error and the image will not be successfully built:

In the
requirements.txt
change the version ofrobotframework-browser
to 19.0.1 and save:Expected behavior
The
rfbrowser init
work and should not cause the docker build process failure when using the newest robotframework-browser version (otherwise we need to stick to an exact version, 19.0.1 in this case).The text was updated successfully, but these errors were encountered: