download AOSP UnicodeDecodeError - download

I try to download AOSP following https://source.android.com/source/downloading.html.
In the repo sync step,I get an error
File "/Users/fish/WORKING_DIRECTORY/.repo/repo/git_refs.py", line 155, in _ReadLoose1
ref_id = ref_id.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0x86 in position 23: ordinal not in range(128)
Fetching projects: 99% (452/456)
error: Exited sync due to fetch errors
Is there anybody meet the same problem?how should i do?
I use Mac 10.10.5

Related

dask computation got different errors with pyarrow and s3

I was doing some groupby parallel computation with dask using pyarrow to load parquet files from s3. However, the same piece of code may run or fail (with different error messages) with random chances. Same issue happened when using fastparquet:
File "pyarrow/_parquet.pyx", line 1036, in pyarrow._parquet.ParquetReader.open
File "pyarrow/error.pxi", line 80, in pyarrow.lib.check_status
pyarrow.lib.ArrowIOError: Arrow error: IOError: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:2309). Detail: Python exception: ssl.SSLError
or failing with different error:
File "pyarrow/_parquet.pyx", line 1036, in pyarrow._parquet.ParquetReader.open
File "pyarrow/error.pxi", line 80, in pyarrow.lib.check_status
pyarrow.lib.ArrowIOError: Arrow error: IOError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:2309). Detail: Python exception: ssl.SSLError
The dask scheduler I was using is processes. It works fine with threads but will be extremely slow. Is this behavior expected for dask?

mllr_solve 'Error reading byte order magic number' on Windows

I'm following the Adapting Default Acoustic model tutorial and have hit a error running mllr_solve.
INFO: main.c(382): -- 1. Read input mean, (var) and accumulation.
ERROR: "pio.c", line 434: fread() failed; retrying...
: No error
ERROR: "swap.c", line 79: error while reading bo_magic
ERROR: "s3io.c", line 177: Error reading byte order magic number
ERROR: "s3io.c", line 265: Error reading header for en-us-8khz\means
FATAL: "main.c", line 392: Couldn't read en-us-8khz\means
I compiled sphinxtrain and sphinxbase using Visual Studio 2017 using 'Release\Win32'.
Is there anyway to change the means/variances files or change s3io.c?
This issue is most likely caused by runtime incompatibility between sphinxbase and sphinxtrain. Time to blame Windows designers, not software
https://cmusphinx.github.io/wiki/faq/#q-pocketsphinx-crashes-on-windows-in-_lock_file

xCode Build Failed: Command failed due to signal: Segmentation fault: 11

I'm getting an error in xCode stating:
Command failed due to signal: Segmentation fault: 11
The line is occuring on line 55:
While emitting SIL for 'saveScore' at /Users/mobiledev/Desktop/Salt Armour App/SADiver/SADiver/objGameOver.swift:55:2
...and line 55 is:
func saveScore()
However I still have no idea what can be done to resolve this.
Full Source:
http://pastebin.com/LUvLaARJ
P.S.
I found two other articles related to this error on SO - however neither scenario seems to apply here :/
Any input/suggestions/tips are greatly appreciated.

compiling error when using community golang buildpack on bluemix

One of my bluemix application worked for weeks but it start to report parse error with Buildpack compilation step failed when pushing app to bluemix:
-----> Downloaded app package (556K)
Cloning into '/tmp/buildpacks/buildpack-go'...
Submodule 'compile-extensions' (https://github.com/cloudfoundry-incubator/compile-extensions.git) registered for path 'compile-extensions'
Cloning into 'compile-extensions'...
Submodule path 'compile-extensions': checked out 'f752ecf4b27d2f31bb082dfe7a47c76fefc769d7'
-------> Buildpack version 1.4.0
parse error: Expected separator between values at line 32, column 3
Staging failed: Buildpack compilation step failed
Here's my manifest.yml file:
---
applications:
- name: joystick
memory: 128M
path: .
buildpack: https://github.com/cloudfoundry/buildpack-go.git
Update: I carefully read the error message and figured out it is application space problem caused by Godeps.json parsing error caused by code merging where one comma is missed. I can not reproduce this locally because I checked in _workspace directory where it never parse Godeps.json.
I created issue 86 to improve this buildpack to provide more information for such kind of error message.
The error message parse error: Expected separator between values at line 32, column 3 comes from jq command within buildpack code, where it tries to read import path from Godeps/Godeps.json by assuming it's a valid JSON file. see line #64 of /bin/compile.
It will stop buildpack if the Godeps.json is not json.
I created issue 86 to improve this buildpack to provide more information for such kind of error message.
Thanks for everyone who spent time on this problem.
Update: issue 86 was fixed in heroku golang buildpack by adding new step to checking Godeps.json format.

Heroku ZipImportError: bad local file header

I keep running into this strange Heroku build error. If I mess around with the ordering of my requirements.txt then the package that fails to build will change, but the build always ends with the exceptions:
ZipImportError: bad local file header in /app/.heroku/python/lib/python2.7/site-packages/setuptools-2.1-py2.7.egg
And
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 38: ordinal not in range(128)
You can see a full build log here: http://pastebin.com/BYw3Xp6u
Anyone know what's going on here?
I was facing the same problem (bad local file header), it seems they have an issue with the new python buildpack.
So you can use the previous version of the buildpack by adding a config var :
heroku config:set BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-python.git#5f96190eb5ccd05b90947f9a77d7ef0881816ef8
It should temporarily solve the problem.

Resources