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

Task: validate score_bazel_cpp_toolchains 1.0.5-rc1 in eclipse-score/logging

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

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cpp
Área
build-system, testing

Línea de trabajo

Start with MODULE.bazel and check how the repository pins score_bazel_cpp_toolchains and rules_cc; use bazel mod graph to verify resolution. Then run a clean build and the full test suite for each platform this repository uses, checking compile commands for the selected -std= flag and failures from missing flags or new warnings. Report pass/fail by 2026-10-16, including Bazel version, platform, failing target, and relevant compile or link command if validation fails.

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

Descripción

Summary

Validate score_bazel_cpp_toolchains 1.0.5-rc1 in eclipse-score/logging before promoting the release candidate to the final 1.0.5 release.

Background

The toolchains were updated to rules_cc 0.2.25, which introduces several major changes that may affect dependent modules. In particular:

  • Bazel no longer adds implicit compile or link flags; all flags now come from explicit toolchain features
  • C standard selection was fixed so exactly one standard applies:
    • default: -std=c11
    • features = ["gnu11"]: -std=gnu11
    • features = ["c_std_c99"]: -std=iso9899:1999, which takes precedence if both are set
  • Linux and QNX toolchains continue using no_legacy_features
  • An optional io_pkt_ddk feature was added for QNX io-pkt driver builds

Required actions

  • Update MODULE.bazel to use score_bazel_cpp_toolchains version 1.0.5-rc1
  • Use single_version_override or the usual RC mechanism if the RC is not yet available in the registry
  • If rules_cc is pinned directly, ensure it resolves to 0.2.25 or higher
  • Verify dependency resolution with bazel mod graph
  • Run a clean build and the full test suite for every platform used by this repository

Validation focus

  • Missing flags or undefined-behavior-like symptoms under the explicit-feature model
  • Changes in the selected -std= flag in compile commands
  • Required updates in custom toolchain extensions or BUILD files that load rules_cc toolchain rules
  • New warnings from rules_cc that are treated as errors

Expected feedback

Report pass/fail results by 2026-10-16.

If validation fails, include:

  • Bazel version
  • Platform configuration
  • Failing target
  • Relevant compile or link command line

If no blockers are found, 1.0.5-rc1 can be promoted to 1.0.5.

Lenguaje dominante
C++
Estrellas
2
Forks
30
Merge medio
3 d 23 h
PR fusionados (30 d)
10

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una 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 eclipse-score/logging

Todos los issues de eclipse-score/logging

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.