Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Rest Source user repo unavailable

Abierto
  • ¿Algo no está bien?
#80 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
java, kafka
Área
api, backend

Línea de trabajo

Start with ServiceUserRepository.requestAuthorization, requestFor, applyPendingUpdates, and the OAuth2Client token flow named in the stack trace. Reproduce startup with many tasks and subjects, then determine how the 503 is handled; done should be defined as reliable startup and subsequent user retrieval without the reported temporary-unavailable failure.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

When there are a large number of tasks (we have 100), then initially we get the following error during start-up of the connector. This used to timeout before the latest increase in time out limits. Now it just says Service Temporarily unavailable. Note that we have more than 1200 subjects there so could be that the rest-source-auth is being overloaded by requests from all the 100 tasks.

[2021-04-15 09:57:44,575] ERROR Failed to initially get users from repository (org.radarbase.connect.rest.fitbit.user.ServiceUserRepository)
java.io.IOException: org.radarcns.exception.TokenException: Cannot get a valid token : Response-code :503 received when requesting token from server with message Service Temporarily Unavailable
	at org.radarbase.connect.rest.fitbit.user.ServiceUserRepository.requestAuthorization(ServiceUserRepository.java:187)
	at org.radarbase.connect.rest.fitbit.user.ServiceUserRepository.requestFor(ServiceUserRepository.java:174)
	at org.radarbase.connect.rest.fitbit.user.ServiceUserRepository.applyPendingUpdates(ServiceUserRepository.java:158)
	at org.radarbase.connect.rest.fitbit.user.ServiceUserRepository.stream(ServiceUserRepository.java:121)
	at org.radarbase.connect.rest.fitbit.request.FitbitRequestGenerator.getPartitions(FitbitRequestGenerator.java:107)
	at org.radarbase.connect.rest.fitbit.route.FitbitPollingRoute.<init>(FitbitPollingRoute.java:126)
	at org.radarbase.connect.rest.fitbit.route.FitbitSleepRoute.<init>(FitbitSleepRoute.java:44)
	at org.radarbase.connect.rest.fitbit.request.FitbitRequestGenerator.getRoutes(FitbitRequestGenerator.java:88)
	at org.radarbase.connect.rest.fitbit.request.FitbitRequestGenerator.initialize(FitbitRequestGenerator.java:80)
	at org.radarbase.connect.rest.RestSourceConnectorConfig.getRequestGenerator(RestSourceConnectorConfig.java:214)
	at org.radarbase.connect.rest.RestSourceTask.start(RestSourceTask.java:62)
	at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:219)
	at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:185)
	at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:235)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.radarcns.exception.TokenException: Cannot get a valid token : Response-code :503 received when requesting token from server with message Service Temporarily Unavailable
	at org.radarcns.oauth.OAuth2Client.refreshToken(OAuth2Client.java:147)
	at org.radarcns.oauth.OAuth2Client.getValidToken(OAuth2Client.java:96)
	at org.radarcns.oauth.OAuth2Client.getValidToken(OAuth2Client.java:80)
	at org.radarbase.connect.rest.fitbit.user.ServiceUserRepository.requestAuthorization(ServiceUserRepository.java:185)
	... 18 more

But later on, it is able to get the users.

Lenguaje dominante
Java
Estrellas
5
Forks
6
Merge medio
5 d 16 h
PR fusionados (30 d)
3

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de RADAR-base/RADAR-REST-Connector

Todos los issues de RADAR-base/RADAR-REST-Connector

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.