Bug: There is no way for the losing player to check their code.
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
Línea de trabajo
Start by reading item 3 in the linked “Game completion” documentation, then reproduce the reported battle with two accounts and check the losing player's disabled “Run” button. The issue does not name code files or tests, so first locate the game completion and code-run entry points. Done means the losing player can submit their code for review and see the result after the opponent wins.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Good afternoon!
There is an indication of the requirement in the documentation.:
https://github.com/hexlet-codebattle/codebattle/wiki/Механика-игры
Item 3 of the "Game completion" block
Environment:
Yandex.Browser 26.8.2.1064 (64-bit)
OS: Windows 11 Pro
Reproduction steps
1. Copy the email address from the website https://tmailor.com/ru/
2. Go to the website https://codebattle.hexlet.io/
3. Click on “Sign up”
4. Enter test data in the fields Nickname, Password, Email, Password Confirmation
5. Return to the website https://tmailor.com/ru/
6. In the window with the received emails, open the email requesting email verification
7. Follow the link in the email
8. Go to the website https://codebattle.hexlet.io/
9. Click “Sign in”
10. Enter a test email address and Password
11. Click on “Create a battle”
12. In the game settings, select “With other user”
13. In the “Choose task by name or tags” menu, enter the value “age_to_days”, and select the only found game option
14. Click on “Create battle”
15. In another browser, open the project page and the website https://tmailor.com/ru/
16. Create a second test account
17. Log in using the second test account on the project page
18. Click on “Join a battle”
19. In the list of games, select the game that was previously created under the first test account
20. Under the second test account, in the solution field, in line 4, enter the text “ans = age*365”
21. Click “Run”
22. In the window that opens, click "GG"
23. Under the first test account, enter the text “ans = age*age” in line 4 in the field with the solution
24. Press “Run”
Expected result
The code entered by the losing participant (the first test account) has been submitted for review, and the code review result has been displayed.
Actual result
The “Run” button is disabled for the losing player.
Browsers
No response
OS
Windows
- Lenguaje dominante
- Elixir
- Estrellas
- 884
- Forks
- 237
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de hexlet-codebattle/codebattle
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
hexlet-codebattle/codebattle#2361 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
hexlet-codebattle/codebattle#2355 ·
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 56/100
hexlet-codebattle/codebattle#2359 ·
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
hexlet-codebattle/codebattle#2358 ·
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
hexlet-codebattle/codebattle#2357 ·
Todos los issues de hexlet-codebattle/codebattle
Issues similares
-
Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
wintermeyer/vutuv#2363 ·
Los mantenedores suelen responder en 1 día
-
Adding ContinuumAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
h4cc/awesome-elixir#4970 ·
-
metadata-update waiting
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
an Ash.Type.String field with a length constraints should expose min/maxLength in the schemaAbiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
ash-project/ash_ai#243 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
curator: add GRoguelon/sandboxesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
ajeetraina/awesome-docker-sbx#200 ·