Hidden prefix visible to students in Active Code Exercises via Code Lens
@morozov-av ya está trabajando en esto.
Desde el 20/1/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Please check the current issues Many bug reports are duplicates, this just creates more work for us. Searching the issues first may give you your answer or a workaround! If not adding new information to an existing report is much more helpful than a new report.
What Course are you in
Knowing the course will help us a lot
idahostateuniversity_httlacs_spring26
What Page were you on
N/A
What is your username
norkish
Describe the bug
A clear and concise description of what what you were trying to accomplish and what went wrong. Vague statements like X does not work are not helpful. Imagine if one of your students sent you an email that said, "My program doesn't work, whats wrong with it?" Could you help them with only that to go on?
A student showed me that if they use CodeLens on the Active Code exercises, they are able to see the Hidden Prefix code that I develop for the exercise. Is this a bug or a feature? In any case, I'd like the hidden prefix to remain hidden.
I don't see a way with the new Assignment Builder to deactivate CodeLens. Temporary workarounds could include using the old assignment builder to add the directive or to explicitly include assert statements in my suffix to ensure students don't inappropriately use information stored in the Hidden Prefix, but ideally there would be a way to prevent them from seeing the prefix.
Traceback
If you got here through the Bug Report page and there was a stack trace, please paste it here
Javascript Errors
Many many errors can be quickly diagnosed from the Javascript Console error log. On Chrome this is View --> Developer --> Javascript Console, on Safari ⌥⌘i or Develop --> Show Web Inspector on Firefox Tools --> Web Developer --> Toggle Tools
- Lenguaje dominante
- HTML
- Estrellas
- 136
- Forks
- 199
- 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.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Sin 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 RunestoneInteractive/thinkcspy
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
RunestoneInteractive/thinkcspy#281 · 1 comentario ·
-
PythonTutor / CodeLens does not allow "import test"Posiblemente ocupada @dandrake la tomó hace 251 días. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
RunestoneInteractive/thinkcspy#279 · 4 comentarios ·
-
bug help wanted
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
RunestoneInteractive/thinkcspy#278 · 6 comentarios ·
-
The "Expected" and "Actual" labels on autograded assertions for ActiveCode exercises are backwardsAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
RunestoneInteractive/thinkcspy#276 · 2 comentarios ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 38/100