danikula / danikula/AndroidVideoCache
Error pinging server
- Dominant language
- Java
- Stars
- 5.5k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
com.danikula.videocache.ProxyCacheException: Error pinging server (attempts: 3, max timeout: 280). If you see this message, please, report at https://github.com/danikula/AndroidVideoCache/issues/134. Default proxies are: [DIRECT]. Version: 2.7.0
at com.danikula.videocache.Pinger.ping(Pinger.java:73)
at com.danikula.videocache.HttpProxyCacheServer.isAlive(HttpProxyCacheServer.java:183)
at com.danikula.videocache.HttpProxyCacheServer.(HttpProxyCacheServer.java:82)
at com.danikula.videocache.HttpProxyCacheServer.(HttpProxyCacheServer.java:52)
at com.danikula.videocache.HttpProxyCacheServer$Builder.build(HttpProxyCacheServer.java:435)
at com.iflytek.common.cache.MediaCacheProxy.newProxy(MediaCacheProxy.kt:49)
at com.iflytek.common.cache.MediaCacheProxy.init(MediaCacheProxy.kt:21)
at com.iflytek.yyspoken.read.ReadApplication.onCreate(ReadApplication.kt:47)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1024)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5503)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1595)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loop(Looper.java:203)
at android.app.ActivityThread.main(ActivityThread.java:6251)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1063)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:924)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at Pinger.java:73, then inspect HttpProxyCacheServer.java at lines 183 and 82 to trace the failed server check. Reproduce the error using the reported AndroidVideoCache version and determine the network or proxy condition that causes the ping to fail; done means the failure is fixed and covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100