EOF on login with termux.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm using termux which is an android emulator that runs linux. When I built keybase from scratch and tried to log in I got > ERROR EOF.
This may be similar to 2897
my log id: d80dba5b0d1d3f5b48b3c51c
Other useful info
-bash-4.4$ go version
go version go1.9.1 android/386
-bash-4.4$ go env
GOARCH="386"
GOBIN=""
GOEXE=""
GOHOSTARCH="386"
GOHOSTOS="android"
GOOS="android"
GOPATH="/data/data/com.termux/files/home/go"
GORACE=""
GOROOT="/data/data/com.termux/files/usr/lib/go"
GOTOOLDIR="/data/data/com.termux/files/usr/lib/go/pkg/tool/android_386"
GCCGO="gccgo"
GO386="sse2"
CC="i686-linux-android-clang"
GOGCCFLAGS="-fPIC -m32 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/data/data/com.termux/files/usr/tmp/go-build470444395=/tmp/go-build -gno-record-gcc-switches"
CXX="i686-linux-android-clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="/home/fornwall/.termux-build/_lib/15.2-i686-21-v14/bin/i686-linux-android-pkg-config"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reviewing the login failure and the related issue #2897, then use the provided Go version and environment details to reproduce the EOF on Termux. Done means login completes successfully without the EOF error in that environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go
- Domain
- authentication, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100