feat: add troubleshooting category in Spanish and remove FAQItem comp… #109
Conversation
WalkthroughSe ha añadido una nueva y extensa sección de documentación de troubleshooting para SleakOps, compuesta por decenas de archivos Changes
Sequence Diagram(s)sequenceDiagram
participant Usuario
participant Docs SleakOps
participant Soporte SleakOps
Usuario->>Docs SleakOps: Busca solución a un problema específico
Docs SleakOps-->>Usuario: Muestra guía de troubleshooting modular (TroubleshootingItem)
alt Problema resuelto
Usuario->>Docs SleakOps: Sigue pasos, ejecuta comandos, ajusta configuración
Docs SleakOps-->>Usuario: Proporciona ejemplos, comandos y recomendaciones
else Problema persiste
Usuario->>Soporte SleakOps: Contacta con información detallada según guía
Soporte SleakOps-->>Usuario: Asiste y actualiza documentación si es necesario
end
Estimated code review effort5 (~150 minutos) Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 58
🔭 Outside diff range comments (2)
docs/troubleshooting/user_issues/database-migration-heroku-to-aws-rds.mdx (1)
76-80: Fragmento JSON incompletoEl bloque se abre pero no se cierra; rompe el resaltado y puede confundir al usuario. Cierra la llave y el bloque de código.
"replication-instance-class": "dms.t3.large" -``` +} +```docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx (1)
118-121: Bloque incompleto: falta contenido y cierre
<TroubleshootingItem id="force-deployment-rollout">se abre pero nunca se cierra ni contiene contenido completo.
Esto deja el MDX inválido y fallará en el build de la web.Sugerencia rápida:
<TroubleshootingItem id="force-deployment-rollout" summary="Force a proper deployment rollout"> -If the deployment is stuck +Si el despliegue está bloqueado, fuerza un nuevo rollout: + +```bash +kubectl rollout restart deployment <deployment-name> -n <namespace> +kubectl rollout status deployment <deployment-name> -n <namespace> +``` + +</TroubleshootingItem>
♻️ Duplicate comments (11)
docs/troubleshooting/bien/build-pods-stuck-creation.mdx (1)
10-10: Mismo problema de ruta del componenteEl import usa
troubleshootingitemen minúsculas. Verificar capitalización como en el
comentario anterior para evitar fallos de build.docs/troubleshooting/bien/cluster-eks-upgrade-volume-attachment-issue.mdx (1)
10-10: Misma observación sobre la capitalización del importRevisa la ruta del componente como en el resto de archivos para evitar fallos en CI.
docs/troubleshooting/user_issues/fargate-pods-not-terminating-cost-increase.mdx (1)
10-10: Import con posible conflicto de mayúsculas/minúsculas
Mismo comentario que en los otros archivos.docs/troubleshooting/user_issues/frontend-environment-variables-docker-build.mdx (1)
10-10: Revisa la capitalización del import
Mismo riesgo de compilación por case-sensitivity.docs/troubleshooting/bien/ci-cd-pipeline-setup-troubleshooting.mdx (1)
10-10: Posible conflicto en la ruta de import
Revisa capitalización como en los demás archivos.docs/troubleshooting/bien/build-newrelic-pkg-resources-deprecation-warning.mdx (1)
10-10: Ruta de importación inconsistente — mismo problema detectadoSe repite la discrepancia de mayúsculas/minúsculas en
TroubleshootingItem.docs/troubleshooting/bien/cluster-upgrade-maintenance-scheduling.mdx (1)
10-10: Import path deTroubleshootingItemen minúsculasMismo comentario que en otros archivos; ajustar para evitar fallos en Linux.
docs/troubleshooting/bien/cluster-production-mode-spot-instances.mdx (1)
10-10: Import path deTroubleshootingItemen minúsculasSe mantiene la misma inconsistencia de casing.
docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
10-10: Import path deTroubleshootingItemen minúsculasMisma observación que en archivos anteriores.
docs/troubleshooting/bien/cluster-critical-addons-node-failure.mdx (1)
11-11: Import duplicado con el mismo problema de capitalización
Mismo detalle que en el otro archivo; asegúrate de que la ruta y el nombre coincidan exactamente con el componente.docs/troubleshooting/user_issues/domain-ns-delegation-replication-issues.mdx (1)
10-10: Path del componente: misma alerta de mayúsculasMismo comentario que en el otro archivo: confirma que el fichero exista con el mismo casing.
🧹 Nitpick comments (106)
docs/troubleshooting/user_issues/_category_.json (1)
2-7: Etiqueta y descripción deberían estar en español para mantener coherenciaTodo el resto del material se presenta como “documentación en español”, pero aquí se dejó en inglés.
Propongo traducir ambos campos y así evitar mezclar idiomas en el sidebar.- "label": "User Issues", + "label": "Problemas de usuario", - "description": "Common problems and solutions that users encounter when using the platform." + "description": "Problemas comunes y sus soluciones al usar la plataforma."docs/troubleshooting/_category_.json (1)
2-6: Sidebar en español + índice generado automático
- Igual que en el sub-nivel, el “label” y la “description” siguen en inglés.
- Añadir
link: { "type": "generated-index" }crea una landing page automática (como ya hiciste en la sub-categoría) y evita un escalón vacío en la navegación.- "label": "Troubleshooting", + "label": "Solución de problemas", - "description": "Common issues and solutions for SleakOps users" + "description": "Problemas frecuentes y sus soluciones para usuarios de SleakOps", + "link": { + "type": "generated-index" + },docs/troubleshooting/index.mdx (2)
3-4: Título y descripción en inglés dentro de la sección en españolPara que el lector no cambie de idioma a mitad de camino, conviene traducir ambos campos:
-title: "Troubleshooting" -description: "Common issues and solutions for SleakOps users" +title: "Solución de problemas" +description: "Problemas frecuentes y sus soluciones para los usuarios de SleakOps"
34-34: Fecha dinámica puede provocar desajuste de hidratación
{new Date().toLocaleDateString('en-US')}se evalúa en el cliente y puede diferir del contenido estático generado.
Docusaurus ya proveereact-liveo el plugin@docusaurus/plugin-content-docsconlastUpdatedAt.
Recomiendo sustituir por la variable de metadatos para evitar warnings en la build.-_Last updated: {new Date().toLocaleDateString('en-US')}_ +<small>Última actualización: {/** @ts-expect-error provided by Docusaurus **/ LastUpdated.date }</small>docs/troubleshooting/user_issues/dns-migration-donweb-to-aws.mdx (1)
14-16: Falta coma después del año según convención ES-ES-**Date:** January 15, 2024 +**Date:** January 15, 2024,docs/troubleshooting/user_issues/database-migration-environment-variables.mdx (2)
14-16: Añadir coma después del año para consistencia-**Date:** December 11, 2024 +**Date:** December 11, 2024,
20-28: Frase redundante “not accessible” → “inaccesibles”Podemos simplificar la redacción en español y mantener tono técnico:
-- Environment variables not accessible to migration processes +- Las variables de entorno son inaccesibles para los procesos de migracióndocs/troubleshooting/user_issues/database-migration-heroku-to-aws-rds.mdx (1)
14-16: Falta la coma de cierre tras el añoPara mantener estilo consistente y evitar alertas de QA, añade la coma después del año.
-**Date:** December 19, 2024 +**Date:** December 19, 2024,docs/troubleshooting/user_issues/dependencies-monitoring-graphs-not-displaying.mdx (1)
14-16: Añadir coma de estilo tras el añoConsistencia editorial.
-**Date:** January 22, 2025 +**Date:** January 22, 2025,docs/troubleshooting/user_issues/environment-specific-configuration-files.mdx (1)
14-16: Falta coma después del añoPequeño ajuste de estilo.
-**Date:** January 15, 2024 +**Date:** January 15, 2024,docs/troubleshooting/bien/build-status-discrepancy-lens-vs-platform.mdx (2)
14-16: Añadir coma tras el año para coherencia-**Date:** January 15, 2024 +**Date:** January 15, 2024,
169-169: También aquí falta la coma en la fecha del pie-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._docs/troubleshooting/user_issues/github-actions-automatic-deployment.mdx (2)
14-16: Consistencia de estilo: coma después del año-**Date:** December 17, 2024 +**Date:** December 17, 2024,
199-199: Añadir coma también en la fecha del pie-_This FAQ was automatically generated on December 17, 2024 based on a real user query._ +_This FAQ was automatically generated on December 17, 2024, based on a real user query._docs/troubleshooting/user_issues/environment-variables-not-accessible-nuxtjs.mdx (1)
45-67: Faltan traducciones: el PR promete categoría en españolTodo el contenido de este artículo está en inglés. Dado que la PR indica “troubleshooting category in Spanish”, te sugiero añadir la versión en español o, al menos, traducir los encabezados principales para mantener coherencia.
docs/troubleshooting/bien/aws-waf-application-load-balancer-protection.mdx (2)
182-186: Región fijaus-east-1puede confundirEl comando de verificación lista ACLs sólo en
us-east-1. Añade una nota para que el usuario reemplace la región o use--region $(aws configure get region)para evitar falsos negativos.
124-140: Bot Control ↑ coste: advierte del impactoEl managed rule
AWSManagedRulesBotControlRuleSetañade cargos significativos ($10 + $0.80/M req). Conviene remarcarlo en el texto para que la gente no lo habilite a ciegas.docs/troubleshooting/bien/cluster-understanding-ec2-instances-and-costs.mdx (1)
100-103: Control plane cost depende de región y hora-mesIndicas “$0.10/hour (~$73/month)”. Aclara que el cálculo asume 730 h/mes y que algunas regiones cuestan $0.125/h; así evitamos soporte por diferencias de factura.
docs/troubleshooting/user_issues/docker-build-cache-issues.mdx (2)
49-56: Invalidate cache: recomienda un método más limpioAñadir un
RUN echo …funciona, pero ensucia el historial de capas y olvida quitarse luego.
Una alternativa compacta y reversible es usar un arg de cache-bust:-# Cache invalidator -RUN echo "Frontend cache bust: v2" > /dev/null +# Cache invalidator +ARG CACHEBUST=1 +RUN echo "Bust $CACHEBUST"Con
--build-arg CACHEBUST=$(date +%s)fuerzas la misma invalidez sin tocar el Dockerfile.
64-80: Borrar todas las imágenes de ECR puede romper despliegues activosEliminar el repositorio entero deja sin capas a versiones actualmente en producción y
genera picos de tráfico al reconstruir desde cero.
Sugiero añadir una advertencia y/o indicar cómo limpiar sólo tags antiguos mediante
ecr batch-delete-image --filter "tagStatus=UNTAGGED".docs/troubleshooting/bien/build-pods-stuck-creation.mdx (2)
24-29: Evitar jerga poco clara (“bugged”)La frase
Builds appear "bugged"puede resultar confusa en la doc en español.
Propón algo como “Las builds parecen atascadas o con errores” para mayor claridad.
65-73: Falta indicar el namespace realLos comandos usan
<build-namespace>y<pod-name>como placeholders.
Añade una línea explicando cómo obtenerlos (kubectl get ns | grep build-) para
que el lector no se quede bloqueado.docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx (2)
56-58: Delegación NS: recuerda desactivar el proxy en CloudflareCuando crees los registros NS en Cloudflare, indica explícitamente que el proxy
debe estar en modo “DNS only”; de lo contrario Cloudflare sustituirá las
direcciones de los NS y la delegación fallará.
97-102: Precisa motivo del “proxy gris”Añade una breve nota sobre por qué el modo proxy de Cloudflare interfiere con
servicios AWS (detección de puertos, certificados, IP dinámica) para que el
usuario entienda el impacto y no lo pase por alto.docs/troubleshooting/bien/ci-cd-github-actions-not-triggering.mdx (1)
70-75: Gatillos: cuidado con corchetes vacíosLa sintaxis YAML
branches: [dev, main]es válida, pero recuerda que si la rama
esdevelopy nodevel trigger fallará. Sugiere al lector verificar el
nombre exacto (git branch -a) para evitar confusiones.docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx (1)
14-16: Añadí la coma tras el año para cumplir la guía de estilo-**Date:** February 13, 2025 +**Date:** February 13, 2025,docs/troubleshooting/user_issues/eks-pod-scheduling-tolerations.mdx (1)
14-16: Coma faltante después de 2025Mantengamos consistencia editorial.
-**Date:** February 21, 2025 +**Date:** February 21, 2025,docs/troubleshooting/bien/cluster-nodepool-missing-after-shutdown.mdx (1)
14-16: Poné la coma tras el año-**Date:** February 20, 2025 +**Date:** February 20, 2025,docs/troubleshooting/bien/cloudfront-existing-s3-bucket.mdx (1)
14-16: Falta la coma después de la fecha-**Date:** December 19, 2024 +**Date:** December 19, 2024,docs/troubleshooting/bien/aws-marketplace-login-setup-issue.mdx (1)
14-16: Coma ausente tras el año-**Date:** January 15, 2024 +**Date:** January 15, 2024,docs/troubleshooting/bien/cluster-prometheus-memory-issues.mdx (1)
14-17: Falta de coma tras el año
Añadir la coma después de “December 23, 2024” mantiene la consistencia editorial.
¡En SleakOps arreglamos los conflictos a las piñas!docs/troubleshooting/user_issues/deployment-build-failed-production.mdx (1)
70-76: Aclarar que el token es un placeholder
Para prevenir usos indebidos, añade una nota tipo “ReemplazaYOUR_TOKENpor tu token personal; nunca lo incluyas en commits”.
¡En SleakOps arreglamos los conflictos a las piñas!docs/troubleshooting/bien/cluster-eks-upgrade-schedule-process.mdx (1)
55-57: Redacción concisa
La frase “prior to each upgrade” puede simplificarse a “before each upgrade”. Menos palabras, mismo sentido.
¡En SleakOps arreglamos los conflictos a las piñas!docs/troubleshooting/user_issues/deployment-stuck-creating-status.mdx (1)
50-64: Incluyekubectl describepara clavar el clavoLas instrucciones muestran
kubectl get …pero omitenkubectl describe pod/deployment, donde suelen aparecer los eventos que delatan pull errors, limites de recursos, etc.Sugerencia rápida:
kubectl describe pod $(kubectl get pods -n your-namespace \ --field-selector=status.phase!=Running \ -o jsonpath='{.items[0].metadata.name}') -n your-namespaceCon esto evitamos golpear a ciegas.
docs/troubleshooting/bien/connecting-to-cluster-with-lens.mdx (1)
90-98: Firma SHA maltratada en el script de instalación de AWS CLIEl comando:
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"es correcto, pero conviene añadir
--silent --locationy validar checksum para evitar sorpresas de MITM.docs/troubleshooting/user_issues/dns-propagation-public-deployment.mdx (1)
64-68: URLs en bloquebashengañan al resaltadoLos enlaces a dnschecker/whatsmydns están marcados como código Bash; el resaltado se ve raro y no aporta valor.
-```bash -# Check from multiple locations -https://dnschecker.org/ -https://www.whatsmydns.net/ -``` +Enlaces útiles: +- https://dnschecker.org/ +- https://www.whatsmydns.net/Pequeño ajuste de legibilidad para no marear a la gente.
docs/troubleshooting/user_issues/deployment-pending-nodepool-changes.mdx (1)
128-134: Filtro de despliegues pendientes poco preciso
grep -v "READY"mostrará también la cabecera y cualquier línea con READY=0/X. Usa columnas para evitar falsos positivos:kubectl get deploy -A \ --no-headers | awk '$5 !~ /^[0-9]+\/\1$/'Así evitamos reventar la consola a puñetazos buscando deployments que en realidad están OK.
docs/troubleshooting/bien/aws-ec2-public-ip-assignment.mdx (1)
14-17: Fecha escrita en inglés dentro de un artículo en españolPara evitar mezclar idiomas y, de paso, cumplir con la guía de estilo que marca la herramienta, cambia la fecha a formato español:
-**Date:** January 15, 2024 +**Fecha:** 15 de enero de 2024Aplica el mismo ajuste en la línea 171.
docs/troubleshooting/bien/database-credentials-access.mdx (1)
14-16: Normaliza la fecha al castellanoMismo caso que en otros documentos: conviene utilizar formato local.
-**Date:** December 19, 2024 +**Fecha:** 19 de diciembre de 2024docs/troubleshooting/user_issues/extending-charts-custom-ingress.mdx (1)
14-16: Fecha en inglés → formato español-**Date:** December 26, 2024 +**Fecha:** 26 de diciembre de 2024docs/troubleshooting/user_issues/deployment-migration-hooks-troubleshooting.mdx (1)
14-16: Fecha en inglés → formato español-**Date:** December 11, 2024 +**Fecha:** 11 de diciembre de 2024docs/troubleshooting/user_issues/deployment-automatic-updates-github.mdx (1)
2-2:sidebar_positionrepetidoTodas las guías nuevas usan
sidebar_position: 3. Docusaurus acepta duplicados, pero el orden final puede resultar impredecible y confuso para el usuario. Considera asignar números únicos o confiar en el orden alfabético.docs/troubleshooting/bien/cluster-eks-upgrade-volume-attachment-issue.mdx (1)
14-14: Coma después del añoEstilo editorial: «19 de diciembre de 2024, ...». Añadir la coma mejora la legibilidad.
docs/troubleshooting/user_issues/fargate-pods-not-terminating-cost-increase.mdx (1)
14-14: Falta coma tras el año en la fecha
Pequeño toque de estilo para mantener consistencia.docs/troubleshooting/user_issues/frontend-environment-variables-docker-build.mdx (2)
80-95: Mejora de ejemplo DockerfilePara evitar que las variables queden vacías cuando no se pasan, conviene añadir valores por defecto:
-ENV REACT_APP_API_URL=$REACT_APP_API_URL +ENV REACT_APP_API_URL=${REACT_APP_API_URL:-""}Aplica el patrón a las demás variables.
14-14: Coma de estilo faltante
Añade coma tras «23 de diciembre de 2024» por coherencia.docs/troubleshooting/bien/ci-cd-pipeline-setup-troubleshooting.mdx (2)
73-90: Pipeline YAML – disparador múltipleSi el objetivo es que el pipeline escuche también
main, considera incluir varios triggers para evitar sustos:- triggers: - - branch: dev - on: push + triggers: + - branch: dev + on: push + - branch: main + on: pushAsí evitamos explicaciones a las piñas cuando el merge llega a
main.
14-14: Coma tras la fecha
Consistencia editorial.docs/troubleshooting/bien/build-newrelic-pkg-resources-deprecation-warning.mdx (1)
33-34: Capitalización en la descripción de versión de SetuptoolsPara coherencia con el resto de bullet points y evitar alertas de linters, usa minúscula:
-Setuptools version: Likely 81 or higher +Setuptools version: likely 81 or higherdocs/troubleshooting/user_issues/deployment-stuck-starting-state.mdx (2)
52-53: “destuck” suena raroLa palabra “destuck” no existe; podría reemplazarse por “liberar” o “desencallar” para mantener la guía formal y clara.
140-142: Variable no definida en elHEALTHCHECKSi
HEALTH_PORTno se define el contenedor fallará en el arranque. Añade un valor por defecto o referencia la validación de variables que ya incluyes más abajo.docs/troubleshooting/user_issues/database-postgresql-restore-errors.mdx (2)
50-56: Comillas faltantes en el nombre de la BBDDSi el nombre de la base contiene guiones u otro carácter especial, los comandos
DROP DATABASEyCREATE DATABASEfallarán. Añade comillas dobles alrededor del nombre para blindar el ejemplo.- -c "DROP DATABASE IF EXISTS ${SUPRADBPRODPOSTGRESQL_POSTGRESQL_NAME};" \ - -c "CREATE DATABASE ${SUPRADBPRODPOSTGRESQL_POSTGRESQL_NAME};" + -c "DROP DATABASE IF EXISTS \"${SUPRADBPRODPOSTGRESQL_POSTGRESQL_NAME}\";" \ + -c "CREATE DATABASE \"${SUPRADBPRODPOSTGRESQL_POSTGRESQL_NAME}\";"
109-114: Considera--single-transactionpara restauraciones grandesAñadir
--single-transactionevita estados intermedios inconsistentes si algo falla a mitad de la restauración.docs/troubleshooting/bien/cluster-aws-vcpu-quota-limit.mdx (1)
64-71: El enlace de Service Quotas fuerza us-east-1El enlace directo apunta a us-east-1. Si el usuario opera en otra región obtendrá un 404. Sugiere entrar en la consola sin región o indica que cambien el selector de región.
docs/troubleshooting/bien/cors-configuration-troubleshooting.mdx (1)
208-208: Etiqueta desactualizada en la nota finalLa coletilla dice “This FAQ was automatically generated”, pero el componente
FAQItemfue eliminado según el PR. Sustituye “FAQ” por “troubleshooting guide” para evitar confusión al lector.docs/troubleshooting/user_issues/github-actions-multi-project-deployment.mdx (1)
14-14: Coma faltante tras el año
January 15, 2025debería llevar coma después del año según el estilo que usa el resto de docs:January 15, 2025,.
No es dramático, pero mantener coherencia evita pull-requests cosméticos posteriores.docs/troubleshooting/user_issues/deployment-environment-variables-migration-issues.mdx (1)
69-77: Ejemplo Dockerfile podría filtrar secretosLos
ENV API_ENDPOINT=${API_ENDPOINT}exponen la variable en la capa final de la imagen.
Si el valor es sensible, sugiere usar sóloARGen build y pasar la variable por--build-arg, o bien inyectarla en runtime. Mejor evitar que los secretos queden en imágenes publicadas – así no tenemos que arreglar fugas a las piñas luego.docs/troubleshooting/user_issues/dockerfile-dotnet-build-errors.mdx (2)
33-33: Posible nombre de DLL de ejemplo mal escrito
dotnet Netdo.Firev.WebApi.dllparece un typo (Netdo→Netdo/Netdo.Firev?). Si los usuarios copian-pegan, el comando fallará con “file not found”.
Corrige el nombre o añade un comentario “.dll” para que nadie se confunda.
82-85: Ruta de proyecto incorrecta en COPY/restoreCopiar sólo
YourProject.csproja la raíz y luegodotnet restorefunciona si el.csprojvive en la raíz. La mayoría de repos .NET guardan el proyecto en un subdirectorio, por lo queCOPY ["src/YourProject/YourProject.csproj", "./"]sería más realista.
Añade una nota o ajusta el snippet para evitar preguntas recurrentes.docs/troubleshooting/user_issues/deployment-build-failures-during-updates.mdx (1)
100-106: Propiedades YAML ficticias pueden confundirEn el bloque de ejemplo
visibility,environment,build_statusno son claves reales del manifiesto SleakOps. Marcarlo como pseudo-código o añadir un comentario evitará que alguien intente pegarlas tal cual y acabe abriendo un ticket.docs/troubleshooting/user_issues/dns-domain-delegation-cloudflare-route53.mdx (2)
3-7: Normalizar la marca “Cloudflare” y evitar inconsistencias de estiloEn el título, las tags y el bloque de metadatos aparece “CloudFlare” (mayúscula intermedia) mientras que en otras partes se usa “cloudflare”.
El nombre oficial es “Cloudflare” (solo la primera C en mayúscula). Alinearlo en todo el documento mejora la presentación y evita confusión.-title: "DNS Domain Delegation Issues Between CloudFlare and Route53" -tags: ["dns", "route53", "cloudflare", "domain-delegation", "aws"] -**Tags:** DNS, Route53, CloudFlare, Domain Delegation, AWS +title: "DNS Domain Delegation Issues Between Cloudflare and Route53" +tags: ["dns", "route53", "cloudflare", "domain-delegation", "aws"] +**Tags:** DNS, Route53, Cloudflare, Domain Delegation, AWSAlso applies to: 14-17
14-16: Fecha en formato español para coherencia con la categoría “es”Dado que esta PR introduce documentación “en español”, la fecha quedaría más consistente usando formato local:
21 de diciembre de 2024.-**Date:** December 21, 2024 +**Fecha:** 21 de diciembre de 2024docs/troubleshooting/user_issues/deployment-redis-communication-error.mdx (2)
14-17: Unificar formato de fecha a españolReemplazar “January 15, 2024” por “15 de enero de 2024” y cambiar la etiqueta a Fecha para mantener consistencia con otros artículos en castellano.
158-158: Fecha final con formato inconsistenteLa nota automática usa “January 15, 2024”. Ajustarla al mismo formato local:
-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_Este FAQ se generó automáticamente el 15 de enero de 2024 a partir de una consulta real del usuario._docs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx (1)
14-16: Aplicar formato de fecha en españolSugerencia:
-**Date:** December 19, 2024 +**Fecha:** 19 de diciembre de 2024docs/troubleshooting/bien/cluster-lens-connection-timeout.mdx (2)
14-17: Homogeneizar formato de fecha y etiquetaUtilizar “29 de abril de 2024” y cambiar la etiqueta a Fecha para coincidir con otros documentos.
196-196: Formato mixto en la nota automáticaActualmente:
4/29/2024. Para coherencia:-_This FAQ was automatically generated on 4/29/2024 based on a real user query._ +_Este FAQ se generó automáticamente el 29 de abril de 2024 a partir de una consulta real del usuario._docs/troubleshooting/user_issues/database-restore-pod-management.mdx (2)
14-17: Fecha en castellano para mantener uniformidadModificar a:
-**Date:** March 26, 2025 +**Fecha:** 26 de marzo de 2025
232-232: Ajustar fecha en la nota final-_This FAQ was automatically generated on March 26, 2025 based on a real user query._ +_Este FAQ se generó automáticamente el 26 de marzo de 2025 a partir de una consulta real del usuario._docs/troubleshooting/bien/cluster-manual-shutdown-scheduled-feature.mdx (1)
3-3: Título poco natural en inglés“Cluster Manual Shutdown Requires Scheduled Feature” suena forzado.
Sugiero “Cluster Manual Shutdown Requires the Scheduled Shutdown Feature” o similar para ganar claridad.docs/troubleshooting/user_issues/domain-delegation-production-environments.mdx (1)
86-90: Instrucción potencialmente engañosa para Route 53Editar el NS record dentro de la Hosted Zone no delega el dominio raíz; lo correcto es cambiar los name servers en el registrador del dominio raíz (fuera de Route 53).
Acláralo o los usuarios podrían perder horas depurando una delegación que nunca se propaga.docs/troubleshooting/bien/aws-cost-monitoring-and-optimization.mdx (1)
95-102: Bloque “bash” contiene lista con guiones: resalta como comentarioDentro del bloque etiquetado como
bash, las líneas comienzan con guiones que no son comandos; quizá pretendes comentarios.
Añade#o usa Markdown normal para evitar que los ejemplos se copien/peguen erróneamente.-# Example cost breakdown to look for: -- EC2 instances (compute) -- RDS (databases) +# Ejemplo de desglose de costes a revisar: +# EC2 instances (compute) +# RDS (databases)docs/troubleshooting/bien/cluster-addons-after-migration.mdx (1)
77-82: Bloque de código dentro de lista: faltan sangrías y lenguaje.El bloque
Typical Grafana access pattern
https://grafana.[your-cluster-domain]
- Añade etiqueta de lenguaje (
bashotext) para el resaltado.- Indenta 4 espacios (o dos tabulaciones) para que MDX no pierda la estructura de la lista.
docs/troubleshooting/user_issues/dns-resolution-failure-mysql-redis.mdx (1)
124-158: La muestra dednsConfigpuede inducir a error.–
dnsPolicy: ClusterFirstya es el valor por defecto; podríamos omitirlo para no distraer.
– La opciónuse-vcno está soportada desde CoreDNS 1.11; convendría mencionar que depende de la versión del clúster para evitar tickets innecesarios.docs/troubleshooting/bien/cluster-production-check-node-scaling.mdx (1)
52-55: Redundancia lingüística “adds an additional node”.Propongo simplificar a “Adds a node” para evitar la dobleta “adds + additional”. El contenido técnico es claro, pero pulir el texto evita confusiones cuando los usuarios traducen mentalmente.
docs/troubleshooting/bien/cluster-kubernetes-upgrade-process.mdx (2)
100-106: El one-liner para detectar APIs deprecadas es útil pero pesado.
kubectl api-resources … | xargs kubectl get …dispara cientos de requests. Para clústeres grandes puede tardar minutos y llenar el API-server de 429.Sugiere en su lugar:
kubectl get --raw /apis | jq '.groups[].preferredVersion.groupVersion'y luego filtrar contra la release-notes.
14-16: Fecha sin coma: detalle menor de estilo.Para alinearse con el resto del doc: “19 de diciembre de 2024” o “December 19, 2024,”. No bloquea, solo coherencia.
docs/troubleshooting/bien/cluster-connection-troubleshooting.mdx (1)
228-230: Añadir coma después del año para cumplir la guía de estilo-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_This FAQ was automatically generated on December 19, 2024, based on a real user query._docs/troubleshooting/user_issues/docker-build-environment-variables.mdx (1)
192-194: Coma faltante tras el año-_This FAQ was automatically generated on March 10, 2025 based on a real user query._ +_This FAQ was automatically generated on March 10, 2025, based on a real user query._docs/troubleshooting/bien/api-access-troubleshooting-private-services.mdx (1)
252-254: Pequeña mejora de puntuación-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_This FAQ was automatically generated on December 19, 2024, based on a real user query._docs/troubleshooting/bien/cluster-eks-spot-instances-unavailable.mdx (1)
208-210: Añadir coma tras el año-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx (1)
206-208: Coma olvidada después del año-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_This FAQ was automatically generated on December 19, 2024, based on a real user query._docs/troubleshooting/bien/cluster-critical-addons-node-failure.mdx (1)
56-62: Bloque marcado comobashpero contiene YAMLEl snippet lista tipos de instancia; cámbialo a
yamlpara claridad y destacar la sintaxis correcta.-```bash +```yaml t3.medium t3.large m5.large m5.xlarge</blockquote></details> <details> <summary>docs/troubleshooting/user_issues/database-performance-optimization.mdx (1)</summary><blockquote> `85-92`: **Aclarar que es configuración ilustrativa** Los parámetros (`instance_class`, `allocated_storage`, etc.) pueden inducir a copia-pega directo. Añade una nota comentada indicando que deben adaptarse al entorno real. </blockquote></details> <details> <summary>docs/troubleshooting/user_issues/docker-exec-format-error-troubleshooting.mdx (1)</summary><blockquote> `186-192`: **Citas anidadas complejas dentro de YAML** La cadena con `echo 'console.log("Hello TypeScript")'` tiene comillas simples y dobles mezcladas; algunos linters de YAML lo marcarán. Usa `|` para bloque literal y evita escapes innecesarios. ```diff - [ - "-c", - 'npm install -g ts-node typescript && echo ''console.log("Hello TypeScript")'' > test.ts && ts-node test.ts', - ] + - "-c" + - | + npm install -g ts-node typescript + echo 'console.log("Hello TypeScript")' > test.ts + ts-node test.tsdocs/troubleshooting/user_issues/dns-delegation-ssl-certificate-validation.mdx (2)
14-16: Añadir coma tras el año para uniformidad editorialAl escribir fechas en formato “Month DD, YYYY”, muchos guías de estilo aconsejan separar el año con una coma:
-**Date:** September 10, 2024 +**Date:** September 10, 2024,No afecta al contenido, pero mantiene coherencia con el resto del material.
176-176: Misma corrección de coma en la nota finalAplicar la misma regla de estilo a la fecha de generación automática.
docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx (2)
15-17: Añadir coma tras el año en la fechaPor consistencia con el resto de la documentación:
-**Date:** January 15, 2024 +**Date:** January 15, 2024,
85-90: Sustituirtelnetporncpara pruebas de conectividad
telnetsuele estar ausente en imágenes minimalistas;nc(netcat) es más habitual y flexible:-# Test MySQL connection -telnet mysql-service 3306 - -# Test Redis connection -telnet redis-service 6379 +# Test MySQL connection +nc -vz mysql-service 3306 + +# Test Redis connection +nc -vz redis-service 6379docs/troubleshooting/user_issues/domain-certificate-delegation-error.mdx (1)
14-16: Uniformar la puntuación en la fechaAplicar coma tras el año para mantener el mismo estilo editorial:
-**Date:** December 19, 2024 +**Date:** December 19, 2024,docs/troubleshooting/user_issues/doppler-integration-troubleshooting.mdx (2)
79-82: Evitar ejemplos que animen a copiar tokens en claroPara reducir riesgo de filtrado accidental, usa una variable de entorno en el ejemplo del header:
-curl -H "Authorization: Bearer YOUR_DOPPLER_TOKEN" \ +curl -H "Authorization: Bearer $DOPPLER_TOKEN" \Además, añade una breve advertencia recordando que nunca se debe comprometer el token en repositorios.
15-17: Coma tras el año en la fechaMismo comentario de estilo que en otros documentos.
docs/troubleshooting/user_issues/docker-build-cache-no-cache-option.mdx (1)
14-16: Añadir coma tras el año para coherencia-**Date:** February 10, 2025 +**Date:** February 10, 2025,docs/troubleshooting/bien/celery-beat-duplicate-execution.mdx (2)
1-8: Front-matter: carpeta “bien” vs. categoría “workload”El doc está en
troubleshooting/bien/…pero el category declarado esworkload.
Para mantener una taxonomía coherente (y evitar rutas URL confusas) convendría alinear carpeta y categoría, p. ej. mover aworkload/o cambiar el campo category.
57-58: Etiqueta de cierre pegada: espacio en blanco innecesarioDespués de
</TroubleshootingItem>hay una línea en blanco que, en algunos casos, provoca que MDX añada un párrafo vacío. No es grave, pero podemos dejar el markup más limpio.docs/troubleshooting/user_issues/domain-ns-delegation-replication-issues.mdx (1)
45-56: Listas numeradas dentro de JSXAl poner la lista 1., 2., 3., 4. dentro de
<TroubleshootingItem>sin envolverla en<ol>MDX lo procesa como párrafos sueltos.
Para que se renderice como lista real:-1. **SleakOps provides NS records** -2. **You configure … +<ol> + <li><strong>SleakOps provides NS records</strong></li> + <li><strong>You configure these at your domain provider</strong></li> + <li><strong>Provider replicates the changes</strong></li> + <li><strong>DNS propagation occurs globally</strong></li> +</ol>docs/troubleshooting/user_issues/database-maintenance-window-strategies.mdx (2)
232-243: Snippet pseudo-código usaSemaphoresin contextoEl ejemplo introduce
new Semaphore(2)pero no indica de dónde sale la clase. Si un lector copia el snippet tal cual se va a quedar a pata coja. Añade un import o una referencia (p. ej.const { Semaphore } = require('async-mutex');) para que sea autocontenido.
252-255: Acceso interno apool.pool._allConnectionsEn el bloque de “Key Metrics” se accede a una prop interna de
mysql2.
Esto suele romper con upgrades menores del driver. Mejor usarpool.getConnectionCount()o consulta ainformation_schemapara métricas en producción.docs/troubleshooting/user_issues/environment-variables-not-working-during-migration.mdx (1)
124-129: Mensaje “specific details” redundanteEl estilo sugiere simplificar: “proporciona detalles”.
No bloquea nada, pero podemos pulir lenguaje.docs/troubleshooting/user_issues/domain-migration-custom-domains.mdx (1)
14-16: Coma de estilo tras el año
Si sigues guía Chicago/APA, deberías añadir una coma después de “2024”. No es crítico, pero ayuda a mantener coherencia editorial.docs/troubleshooting/bien/cost-analysis-and-resource-optimization.mdx (1)
90-99: YAML: límites/requests incoherentes
Los ejemplos muestranrequests.memory: 512Miylimits.memory: 1Gi, pero la CPU mantiene el doble (250m→500m). Aclara que la relación es ejemplo, o añade nota para evitar que usuarios lo copien sin contexto.docs/troubleshooting/bien/database-migrations-execution-hooks.mdx (1)
14-16: Coma tras el año
Añade la coma después de “2024” para uniformidad editorial.docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx (2)
233-248: Regla Prometheus: métrica y umbral discutibles
increase(django_migration_duration_seconds[5m]) > 300sumará solo 5 min de ventana; si cada migración dura 5 min 1 s ya superas 300 s y saltará alerta en todos los despliegues. Ajusta ventana o métrica (p. ej.rateohistogram_quantile).
254-255: Barra invertida sobrante
El backslash final rompe el rendering de Markdown. Elimínalo o duplica para escapar.docs/troubleshooting/bien/cluster-upgrade-zero-downtime.mdx (2)
107-109: Fechas y comas
Añade una coma tras “February 19, 2025” para mantener formato coherente.
114-119: Checklist en Markdown
El checkbox[ ]dentro de lista numerada puede no renderizar bien en Docusaurus. Usa lista de elementos o- [ ]fuera de numeración.
docs/troubleshooting/user_issues/environment-specific-configuration-files.mdx
Outdated
Show resolved
Hide resolved
docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx
Outdated
Show resolved
Hide resolved
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Import con capitalización incorrecta
Mismo problema que en otros archivos: la ruta usa troubleshootingitem en minúsculas.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/domain-setup-alert-explanation.mdx around
lines 10 to 11, the import statement uses incorrect capitalization for the
module path 'troubleshootingitem'. Change the import path to use the correct
capitalization that matches the actual file or directory name, ensuring
consistency and preventing import errors.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Ruta del componente con minúsculas
Alinear con la capitalización correcta para evitar errores en producción.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx
at lines 11 to 12, the import path for the TroubleshootingItem component uses
lowercase letters incorrectly. Update the import statement to match the exact
capitalization of the component's file and folder names to prevent production
errors caused by case sensitivity.
| tags: | ||
| ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"] |
There was a problem hiding this comment.
YAML invalido en tags
La clave tags: queda sin valor y la lista aparece como una nueva clave-string, lo que rompe el front-matter.
-tags:
- ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"]
+tags: ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| tags: | |
| ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"] | |
| tags: ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"] |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx
around lines 7 to 8, the YAML front-matter for the `tags` key is incorrectly
formatted, causing the list to be interpreted as a string key instead of a
value. Fix this by properly indenting the list items under the `tags:` key using
a dash and space for each tag, ensuring the list is correctly recognized as the
value of `tags`.
| tags: ["github-actions", "ci-cd", "quota", "optimization", "deployment"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta de import en minúsculas: probable build roto en sistemas case-sensitive
TroubleshootingItem se importa desde @site/src/components/HomepageFeatures/troubleshootingitem (todo en minúsculas).
En Linux/macOS, si el archivo real se llama TroubleshootingItem.tsx/tsx, la resolución fallará y el sitio no compilará.
Corrígelo cambiando la ruta o el nombre físico del componente para que coincidan exactamente.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/github-actions-quota-management.mdx at line
10, the import path for TroubleshootingItem uses all lowercase letters which may
cause build failures on case-sensitive file systems. Verify the exact casing of
the actual file name (e.g., TroubleshootingItem.tsx) and update the import
statement to match the file name's casing exactly to ensure successful
resolution and compilation.
| instance_type: "t3.large" # Or upgrade instance type | ||
| max_memory_gb: 32 # Increased memory limit |
There was a problem hiding this comment.
Incoherencia técnica: t3.large no ofrece 32 GiB
El ejemplo muestra instance_type: "t3.large" (≈ 8 GiB) junto a max_memory_gb: 32.
Esto puede confundir al lector y llevar a configuraciones imposibles.
Actualiza el tipo a uno que sí acepte 32 GiB (p.ej. r5.xlarge) o reduce el valor de memoria.
🤖 Prompt for AI Agents
In
docs/troubleshooting/bien/cluster-nodepool-memory-limit-deployment-failure.mdx
around lines 75 to 76, the instance_type is set to "t3.large" which only
supports about 8 GiB of memory, but max_memory_gb is set to 32, causing a
technical inconsistency. Fix this by either changing instance_type to a type
that supports 32 GiB memory, such as "r5.xlarge", or reduce max_memory_gb to
match the memory capacity of "t3.large".
| tags: ["migration", "addons", "loki", "grafana", "monitoring"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Revisa la ruta de importación del componente.
Importas el componente como:
import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";Si el archivo real se llama TroubleshootingItem.tsx (mayúscula en el nombre) y resides en un FS sensible a mayúsculas, te vas a comer un 404 en tiempo de build. Confirma que la ruta y la capitalización coinciden.
¡En SleakOps arreglamos esos conflictos a las piñas antes de que lleguen a producción!
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/cluster-addons-after-migration.mdx at line 10, the
import path for TroubleshootingItem may have incorrect capitalization. Verify
the exact filename of TroubleshootingItem.tsx including uppercase letters and
update the import statement to match the exact case-sensitive path to avoid
build errors on case-sensitive file systems.
| # settings.py | ||
| INSTALLED_APPS = [ | ||
| 'django.contrib.admin', | ||
| 'django.contrib.auth', | ||
| 'django.contrib.contenttypes', | ||
| 'django.contrib.sessions', | ||
| 'django.contrib.messages', | ||
| 'django.contrib.staticfiles', | ||
|
|
||
| # Third-party apps | ||
| 'celery', | ||
| 'django_celery_beat', # If using periodic tasks | ||
| 'django_celery_results', # If storing results in Django DB | ||
|
|
||
| # Your apps | ||
| 'your_app_name', | ||
| # Add any missing apps here |
There was a problem hiding this comment.
🛠️ Refactor suggestion
INSTALLED_APPS incluye celery, lo cual no es un app de Django.
celery no expone un AppConfig, por lo que meterlo aquí no aporta nada y puede confundir. Sustituye por los paquetes que sí registran apps (p. ej. django_celery_results).
- # Third-party apps
- 'celery',
+ # Third-party apps📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # settings.py | |
| INSTALLED_APPS = [ | |
| 'django.contrib.admin', | |
| 'django.contrib.auth', | |
| 'django.contrib.contenttypes', | |
| 'django.contrib.sessions', | |
| 'django.contrib.messages', | |
| 'django.contrib.staticfiles', | |
| # Third-party apps | |
| 'celery', | |
| 'django_celery_beat', # If using periodic tasks | |
| 'django_celery_results', # If storing results in Django DB | |
| # Your apps | |
| 'your_app_name', | |
| # Add any missing apps here | |
| # settings.py | |
| INSTALLED_APPS = [ | |
| 'django.contrib.admin', | |
| 'django.contrib.auth', | |
| 'django.contrib.contenttypes', | |
| 'django.contrib.sessions', | |
| 'django.contrib.messages', | |
| 'django.contrib.staticfiles', | |
| # Third-party apps | |
| 'django_celery_beat', # If using periodic tasks | |
| 'django_celery_results', # If storing results in Django DB | |
| # Your apps | |
| 'your_app_name', | |
| # Add any missing apps here | |
| ] |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx
around lines 74 to 90, the INSTALLED_APPS list incorrectly includes 'celery',
which is not a Django app and does not provide an AppConfig. Remove 'celery'
from INSTALLED_APPS and keep only the Django apps that register themselves, such
as 'django_celery_results' and 'django_celery_beat'.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Ruta de import incorrecta: posible ruptura del build en sistemas case-sensitive
El componente se exporta con mayúscula inicial (TroubleshootingItem). Al usar la ruta en minúsculas (troubleshootingitem) el build de Docusaurus fallará en Linux/CI.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/cluster-connection-troubleshooting.mdx around lines
10 to 11, the import path for the TroubleshootingItem component uses lowercase
letters, which causes build failures on case-sensitive systems like Linux.
Update the import statement to match the exact case of the exported component
and file name, changing "troubleshootingitem" to "TroubleshootingItem" to ensure
the build succeeds across all environments.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Misma ruta con capitalización inconsistente
Alinea la importación a la convención usada por el resto del proyecto.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/docker-build-environment-variables.mdx
around lines 10 to 11, the import path for TroubleshootingItem has inconsistent
capitalization compared to the project's convention. Adjust the import statement
to match the exact casing used elsewhere in the project to maintain consistency
and avoid potential module resolution issues.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Capitalización de componente
Igual que en otros archivos, corrige la ruta para evitar errores en CI.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/api-access-troubleshooting-private-services.mdx
around lines 10 to 11, the import statement for TroubleshootingItem has
incorrect capitalization in the path. Adjust the import path to match the exact
casing of the component's filename and directory to prevent CI errors related to
case sensitivity.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Import con minúsculas: rompe la compilación en Linux
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/cluster-eks-spot-instances-unavailable.mdx around
lines 10 to 11, the import statement uses incorrect casing for the module name,
which breaks compilation on Linux due to case sensitivity. Change the import
path to use all lowercase letters to match the actual file or directory name,
ensuring the import statement matches the exact casing of the target file.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Importación con mayúsculas inconsistente
Última ocurrencia a corregir para evitar errores de módulo no encontrado.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx
at lines 10 to 11, the import statement for TroubleshootingItem uses
inconsistent capitalization that may cause module not found errors. Correct the
import path to match the exact casing of the file or module name as defined in
the project to ensure consistent and error-free imports.
| tags: ["django", "migrations", "database", "import", "troubleshooting"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Corrige la capitalización del componente importado
troubleshootingitem en minúsculas fallará si el archivo exporta TroubleshootingItem. Ajusta el import para evitar romper el build de Docusaurus; en SleakOps arreglamos los conflictos a las piñas, pero mejor no provocar uno.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx
at line 10, the import statement uses incorrect capitalization for the
TroubleshootingItem component. Change the import to use the exact exported name
with correct capitalization, TroubleshootingItem, to prevent build errors in
Docusaurus.
| tags: ["database", "migrations", "hooks", "executions", "deployment"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Importación con casing inconsistente
Repetimos la observación sobre troubleshootingitem. Corrígelo o prepárate para pelearte con el CI “a las piñas”.
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-migrations-execution-hooks.mdx at line 10,
the import statement for TroubleshootingItem uses inconsistent casing in the
filename 'troubleshootingitem'. Correct the import to match the exact casing of
the file and component name, likely 'TroubleshootingItem', to avoid CI errors
related to case sensitivity.
| 1. **Pre-upgrade Hooks**: Automatically created as `db-migration` hooks in your environments | ||
| 2. **Automatic execution**: Runs before each deployment when you push code to `develop` or `main` branches | ||
| 3. **Command execution**: Executes `update-database` command before updating application code | ||
|
|
||
| **Configuration:** |
There was a problem hiding this comment.
Comando erróneo: update-database
En EF CLI moderno usamos dotnet ef database update. El alias update-database solo existe en el Package Manager Console de Visual Studio. Sustitúyelo para evitar confusión:
- command: update-database
+ command: dotnet ef database update --project YourProject.csprojCommittable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-migrations-execution-hooks.mdx around
lines 51 to 55, the command `update-database` is incorrect for modern EF CLI
usage and only valid in Visual Studio's Package Manager Console. Replace
`update-database` with the correct `dotnet ef database update` command to avoid
confusion and ensure accuracy in the documentation.
| tags: ["deployment", "database", "migrations", "timeout", "pre-deploy"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Importación con minúsculas
Otra vez el casing del componente; unificad antes de que el build nos invite “a las piñas”.
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx
at line 10, the import statement for the TroubleshootingItem component uses
incorrect casing. Correct the import path to match the exact casing of the
component file and folder names to avoid build errors caused by case
sensitivity.
| # Add logging to migrations | ||
| import logging | ||
| logger = logging.getLogger(__name__) | ||
|
|
||
| class Migration(migrations.Migration): | ||
| def apply_migration(self, project_state, schema_editor, collect_sql=False): | ||
| logger.info(f"Starting migration {self.name}") | ||
| start_time = time.time() | ||
| result = super().apply_migration(project_state, schema_editor, collect_sql) | ||
| duration = time.time() - start_time | ||
| logger.info(f"Migration {self.name} completed in {duration:.2f} seconds") | ||
| return result | ||
| ``` |
There was a problem hiding this comment.
Falta import time en el ejemplo de logging
El snippet usa time.time() pero no importa el módulo, generará NameError.
-import logging
+import logging
+import time📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # Add logging to migrations | |
| import logging | |
| logger = logging.getLogger(__name__) | |
| class Migration(migrations.Migration): | |
| def apply_migration(self, project_state, schema_editor, collect_sql=False): | |
| logger.info(f"Starting migration {self.name}") | |
| start_time = time.time() | |
| result = super().apply_migration(project_state, schema_editor, collect_sql) | |
| duration = time.time() - start_time | |
| logger.info(f"Migration {self.name} completed in {duration:.2f} seconds") | |
| return result | |
| ``` | |
| # Add logging to migrations | |
| import logging | |
| import time | |
| logger = logging.getLogger(__name__) | |
| class Migration(migrations.Migration): | |
| def apply_migration(self, project_state, schema_editor, collect_sql=False): | |
| logger.info(f"Starting migration {self.name}") | |
| start_time = time.time() | |
| result = super().apply_migration(project_state, schema_editor, collect_sql) | |
| duration = time.time() - start_time | |
| logger.info(f"Migration {self.name} completed in {duration:.2f} seconds") | |
| return result |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx
around lines 216 to 228, the example code uses time.time() but does not import
the time module, causing a NameError. Add the line "import time" at the
beginning of the snippet to fix the missing import and ensure the code runs
correctly.
| tags: ["upgrade", "kubernetes", "downtime", "maintenance", "production"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Importación con casing inconsistente
troubleshootingitem en minúsculas → riesgo de fallo de módulo en producción.
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/cluster-upgrade-zero-downtime.mdx at line 10, the
import statement uses incorrect casing for the module name
"troubleshootingitem". Change the import to use the correct casing
"TroubleshootingItem" to match the actual file/module name and avoid module
resolution errors in production.
There was a problem hiding this comment.
Pull Request Overview
This pull request adds a comprehensive "Troubleshooting" section to the SleakOps documentation in Spanish. The PR centralizes guides and solutions for common technical issues, providing detailed step-by-step solutions with practical examples, code snippets, and best practices for various scenarios including deployments, migrations, DNS configuration, CI/CD optimization, and Kubernetes troubleshooting.
- Adds "Troubleshooting" category with 58 new technical guides covering diverse issues
- Provides detailed solutions for GitHub Actions, Docker, DNS, deployments, and framework-specific problems
- Includes practical code examples, configuration snippets, and command-line instructions for immediate problem resolution
Reviewed Changes
Copilot reviewed 105 out of 434 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
| github-actions-quota-management.mdx | GitHub Actions quota optimization and CI/CD efficiency management |
| github-actions-multi-project-deployment.mdx | Configuration for deploying multiple SleakOps projects simultaneously |
| github-actions-automatic-deployment.mdx | Setup guide for automatic deployments with GitHub Actions |
| frontend-environment-variables-docker-build.mdx | Solution for frontend environment variables not working during build |
| fargate-pods-not-terminating-cost-increase.mdx | AWS Fargate pod termination issues causing cost increases |
| extending-charts-custom-ingress.mdx | Adding persistent custom Ingress configurations using Extended Charts |
| environment-variables-not-working-during-migration.mdx | Environment variable issues during platform maintenance migrations |
| environment-variables-not-accessible-nuxtjs.mdx | NuxtJS-specific environment variable configuration problems |
| environment-specific-configuration-files.mdx | Managing configuration files that vary between environments |
| eks-pod-scheduling-tolerations.mdx | EKS pod scheduling issues with spot instances and tolerations |
| doppler-integration-troubleshooting.mdx | Doppler configuration and environment variable synchronization issues |
| domain-setup-alert-explanation.mdx | Understanding domain setup alerts and when action is required |
| domain-ns-delegation-replication-issues.mdx | NS record delegation and replication problems with domain providers |
| domain-migration-custom-domains.mdx | Migrating applications to new domains and configuring custom domains |
| domain-delegation-production-environments.mdx | Domain delegation problems in production environments |
| domain-certificate-delegation-error.mdx | ACMModule DoesNotExist error during certificate delegation |
| dockerfile-dotnet-build-errors.mdx | Docker build failures and application startup issues in .NET projects |
| docker-exec-format-error-troubleshooting.mdx | Architecture compatibility issues with Docker containers in jobs |
| docker-daphne-logging-configuration.mdx | Docker container logging configuration for Daphne applications |
| docker-build-environment-variables.mdx | Environment variables not accessible during Docker build process |
| docker-build-cache-no-cache-option.mdx | Docker build cache issues with build arguments |
| docker-build-cache-issues.mdx | Docker build cache preventing code changes from being deployed |
| dns-resolution-failure-mysql-redis.mdx | DNS resolution failures causing MySQL and Redis connection errors |
| dns-propagation-public-deployment.mdx | DNS propagation and resolution problems for public deployments |
| dns-migration-donweb-to-aws.mdx | Complete DNS migration guide from DonWeb to AWS Route 53 |
| dns-domain-delegation-cloudflare-route53.mdx | Domain delegation issues between CloudFlare and Route53 |
| dns-delegation-ssl-certificate-validation.mdx | DNS delegation and AWS SSL certificate validation delays |
| dns-delegation-route53-domain-configuration.mdx | DNS delegation problems with Route53 and external registrars |
| dns-cloudflare-route53-configuration.mdx | DNS configuration when using Cloudflare with AWS Route53 delegation |
| django-migration-conflicts-database-import.mdx | Django migration errors when importing database dumps |
| django-celery-appregistrynotready-error.mdx | Django AppRegistryNotReady error when running Celery cron jobs |
| deployment-timeout-database-migrations.mdx | Deployment failures caused by database migration timeouts |
Comments suppressed due to low confidence (2)
docs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx:205
- There appears to be a stray backslash '' at the end of the file that should be removed.
\
docs/troubleshooting/user_issues/dns-domain-delegation-cloudflare-route53.mdx:194
- There appears to be a stray backslash '' and incomplete content at the end of the file. The troubleshooting section seems to be cut off.
- Use multiple DNS checkers: whatsmydns.net
| uses: actions/checkout@v4 | ||
|
|
||
| - name: Install SleakOps CLI | ||
| run: pip install sle |
There was a problem hiding this comment.
The pip install command is incomplete. It appears to be cut off and should likely be 'pip install sleakops' based on the context of the document.
| run: pip install sle | |
| run: pip install sleakops |
| requests: | ||
| memory: "256Mi" | ||
| cpu: "250m" | ||
| limits: memory |
There was a problem hiding this comment.
The YAML configuration is incomplete. The 'limits: memory' line appears to be cut off and should specify a memory limit value like 'memory: "512Mi"'.
| limits: memory | |
| limits: | |
| memory: "512Mi" |
| annotations: | ||
| # Redirect configuration | ||
| alb.ingress.kubernetes.io/actions.redirect-to-simplee: > | ||
| {"Type": "redirect" |
There was a problem hiding this comment.
The YAML example appears to be incomplete. The annotation value is started but not completed, which would result in invalid YAML configuration.
| {"Type": "redirect" | |
| {"Type": "redirect", "RedirectConfig": {"Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}} |
| data: | ||
| config.json: | | ||
| { | ||
| "database_url": "dev-db.example.com" |
There was a problem hiding this comment.
The YAML configuration appears to be incomplete. The ConfigMap data section is not properly closed, which would result in invalid YAML.
| "database_url": "dev-db.example.com" | |
| "database_url": "dev-db.example.com" | |
| } |
| { | ||
| "Logging": { | ||
| "LogLevel": { | ||
| "Default": "Information" |
There was a problem hiding this comment.
The JSON configuration appears to be incomplete. The appsettings.json example is cut off and not properly closed, which would result in invalid JSON.
| "Default": "Information" | |
| "Default": "Information" | |
| } | |
| } | |
| } |
| ```python | ||
| # For JSON structured logs | ||
| LOGGING = { | ||
| 'version': 1 |
There was a problem hiding this comment.
The Python dictionary configuration appears to be incomplete. The LOGGING configuration example is cut off and not properly closed.
| 'version': 1 | |
| 'version': 1, | |
| 'disable_existing_loggers': False, | |
| 'formatters': { | |
| 'json': { | |
| 'format': '{"timestamp": "%(asctime)s", "level": "%(levelname)s", "message": "%(message)s", "logger": "%(name)s"}', | |
| 'class': 'logging.Formatter', | |
| }, | |
| }, | |
| 'handlers': { | |
| 'console': { | |
| 'class': 'logging.StreamHandler', | |
| 'formatter': 'json', | |
| }, | |
| }, | |
| 'loggers': { | |
| 'django': { | |
| 'handlers': ['console'], | |
| 'level': 'INFO', | |
| 'propagate': True, | |
| }, | |
| }, | |
| } |
| ``` | ||
|
|
||
| Deploy as a sidecar container or separate monitoring pod. | ||
| \ |
There was a problem hiding this comment.
There appears to be a stray backslash '' at the end of the file that should be removed.
| \ |
|
|
||
| - Always include proper exit codes in your scripts | ||
| - Use health checks when appropriate | ||
| - Log errors to stdout/stderr for SleakOps monitoring |
There was a problem hiding this comment.
The file appears to be incomplete. The best practices section ends abruptly without proper closure.
| - Log errors to stdout/stderr for SleakOps monitoring | |
| - Log errors to stdout/stderr for SleakOps monitoring | |
| ## Summary | |
| Following these best practices will help ensure that your Docker-based jobs run smoothly and efficiently in SleakOps. By addressing common issues such as resource management, error handling, and TypeScript compilation, you can minimize downtime and improve the reliability of your workloads. |
| 1. Export all DNS records from DonWeb | ||
| 2. Set up AWS services (Lightsail/EC2 for WordPress |
There was a problem hiding this comment.
The migration process section appears to be incomplete. The step-by-step process is started but not completed.
| 1. Export all DNS records from DonWeb | |
| 2. Set up AWS services (Lightsail/EC2 for WordPress | |
| 1. Export all DNS records from DonWeb: | |
| - Log in to your DonWeb account. | |
| - Navigate to the DNS management section. | |
| - Export the DNS records in a format that can be referenced later. | |
| 2. Set up AWS services (e.g., Lightsail or EC2 for WordPress): | |
| - Choose the appropriate AWS service based on your needs. | |
| - Configure the service to host your website or application. | |
| - Ensure the service is running and accessible. | |
| **Phase 2: Migration** | |
| 1. Import DNS records into AWS Route 53: | |
| - Log in to the AWS Management Console. | |
| - Navigate to the Route 53 service. | |
| - Create a new hosted zone for your domain. | |
| - Add the DNS records exported from DonWeb to the hosted zone. | |
| 2. Update the domain's nameservers: | |
| - In your DonWeb account, update the domain's nameservers to point to the AWS Route 53 nameservers. | |
| - Wait for the DNS propagation to complete (this can take up to 48 hours). | |
| **Phase 3: Validation** | |
| 1. Verify DNS records: | |
| - Use tools like `dig` or online DNS checkers to ensure the DNS records are correctly configured. | |
| - Check that the A, MX, CNAME, and TXT records resolve as expected. | |
| 2. Test services: | |
| - Verify that your website is accessible via the new AWS setup. | |
| - Test email functionality if MX and TXT records were updated. | |
| 3. Monitor for issues: | |
| - Monitor your services for any issues over the next 48 hours. | |
| - Address any errors or misconfigurations promptly. |
|
|
||
| ```bash | ||
| # Always test with production-like data volumes | ||
| # Use database snapshots for realistic testing\ |
There was a problem hiding this comment.
There appears to be a stray backslash '' at the end of the file that should be removed.
| # Use database snapshots for realistic testing\ | |
| # Use database snapshots for realistic testing |
…ration, and deployment issues
There was a problem hiding this comment.
Actionable comments posted: 12
🧹 Nitpick comments (21)
docs/troubleshooting/bien/dns-resolution-failure-mysql-redis.mdx (1)
292-293: Nota final incoherente con la secciónEl cierre “This FAQ was automatically generated…” no encaja en un documento de Troubleshooting y puede despistar. Cambia “FAQ” por “documento de troubleshooting” o elimínalo.
docs/troubleshooting/bien/docker-daphne-logging-configuration.mdx (1)
14-16: Pequeña cuestión de estilo en la fechaAlgunos linters sugieren coma después del año en formato “month-day-year”:
Date: January 21, 2025,
No es bloqueante, solo un mimo de nitpick.
docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx (3)
78-82: Ejemplo con token directo en cabecera – riesgo de copiar/pegar secretos.Aunque uses un placeholder (
YOUR_DOPPLER_TOKEN), fomenta malas prácticas de exponer el token en la línea de comandos. Sugiere exportar la variable de entorno y usarla:curl -H "Authorization: Bearer ${DOPPLER_TOKEN}" ...Esto reduce la probabilidad de filtrar credenciales al historial de shell.
116-124: Anotacióndeployment.kubernetes.io/revisiones gestionada por Kubernetes.Sobrescribirla manualmente puede generar ruido en el controlador y no garantiza el recreo de pods. Si lo único que buscas es forzar el rollout, basta con
kubectl rollout restart(ya documentado) o añadir una anotación propia, p. ej.sleakops.io/force-redeploy.Considera actualizar el ejemplo para evitar confusiones.
625-627: Pequeño detalle de estilo en la fecha final.Falta la coma tras el año según la convención “December 19, 2024”. No es crítico, pero ayuda a mantener coherencia editorial.
docs/troubleshooting/bien/deployment-teams-instances-not-creating.mdx (3)
1-8: El campocategoryno lo reconocerá Docusaurus → posible metadata huérfana
category: "project"no es un front-matter estándar en Docusaurus v2; la organización en el sidebar depende de la carpeta_category_.jsony desidebar_position. Mantener metadatos no soportados sólo introduce ruido y puede confundir en futuras migraciones.- category: "project"Si lo necesitas como etiqueta, añádelo al array
tags.
en sleakops arreglamos estos detallitos a las piñas, ¡pero mejor evitarlos!
14-16: Comas de cortesía después del año
Para mantener consistencia editorial, agrega una coma tras el año en las fechas:-**Date:** January 15, 2024 +**Date:** January 15, 2024, -_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._Also applies to: 453-453
12-449: Objetivo del PR: contenido en español, pero el documento está en inglés
El PR declara “añadir categoría de troubleshooting en español”, sin embargo todo este artículo está redactado en inglés. Esto puede generar una experiencia inconsistente en la sección “bien”. Evalúa:
- Traducir el contenido a español.
- Moverlo a la carpeta de documentación en inglés si esa era la intención.
Así evitamos que los usuarios cambien de idioma a mitad de navegación.
docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx (2)
45-129: Bloques de código sin idioma declaradoPara que Docusaurus aplique sintaxis y se vea lindo, añadid el identificador de idioma en los bloques
bash,yaml, etc. La mayoría ya lo tiene, pero el bloque de los registros DNS (líneas 59-75) está sin especificar.-``` +```textPequeña nit, pero suma para la legibilidad.
335-336: Footer hace referencia a “FAQ” aunque ya no existeFAQItemLa coletilla “This FAQ was automatically generated…” contradice el cambio donde se quitó el componente de FAQ. Cambiad “FAQ” por “artículo” o eliminad la frase para evitar confusiones.
docs/troubleshooting/bien/database-maintenance-window-strategies.mdx (2)
232-242:Semaphoresin definición: ejemplo no ejecutableEl snippet usa
new Semaphore(2)pero no muestra de dónde sale la clase. Para evitar confusión en producción (y piñas innecesarias), añade la dependencia explícita o una micro-implementación:+const { Semaphore } = require('async-mutex'); // npm i async-mutex
252-258: Acceso a propiedades internas del pool MySQL
pool.pool._acquiringConnectionsy similares son APIs privadas; cambian entre versiones y rompen los ejemplos. Propón usar eventos (connection,enqueue) o métricas expuestas por el driver en lugar de tocar “tripas”.docs/troubleshooting/bien/deployment-stuck-creating-status.mdx (1)
185-195:grepsobre YAML puede romper tuberías
grep -A 10 conditionstraskubectl get deployment -o yamlmezclará colores y líneas largas; mejor usayqokubectl get ... -o jsonpath. Menor, pero evita frustraciones al copiar-pegar.docs/troubleshooting/bien/database-restore-pod-procedures.mdx (1)
526-548: Comillas y escapes entmux send-keysimposibles de leerEl bloque incluye cascadas de
\"que hacen sangrar los ojos. Considera mover el script a un fichero.shy llamartmux new-session -d -s restore_monitor "./script.sh"para claridad.docs/troubleshooting/bien/deployment-old-pods-not-terminating.mdx (1)
378-382: Posible borrado masivo accidental
tail -n +4 | awk '{print $1}' | xargs … deleteasume orden por fecha pero--sort-byya ordena. Si hay < 3 RS,tail -n +4enviará lista vacía (ok) pero si se inyecta texto inesperado puede borrar el RS activo. Añade filtro pormetadata.ownerReferences[0].uido usakubectl delete rs --to-deleteexplícito.docs/troubleshooting/bien/database-migration-data-integrity-issues.mdx (2)
52-61: Conteo de registros conquery_to_xmles overkillLa función convierte resultados a XML y es lenta para bases grandes. Con
pg_class.reltuplesobtienes estimaciones rápidas:SELECT relname AS table_name, reltuples::bigint AS row_estimate FROM pg_class WHERE relkind = 'r' AND relnamespace = 'public'::regnamespace;Menos carga, menos piñas.
170-180:INSERT ... ON CONFLICTsin columnas claveEl ejemplo presupone clave primaria
id; si el target usa otra PK o compuesta, el comando fallará. Añade nota aclaratoria o parametriza la cláusulaON CONFLICT (pk_column).docs/troubleshooting/bien/database-migration-environment-variables.mdx (2)
14-16: Coma faltante tras el añoPara mantener coherencia con el estilo del resto de docs, añade una coma después del año.
-**Date:** December 11, 2024 +**Date:** December 11, 2024,
1-8: Coherencia entrecategoryy rutaEl front-matter declara
category: "project"pero el documento está dentro debien/. Verifica que esto no rompa la agrupación de categorías recién creada en castellano.docs/troubleshooting/bien/deployment-timeout-database-migrations.mdx (1)
14-16: Añadir coma tras el año-**Date:** April 25, 2024 +**Date:** April 25, 2024,docs/troubleshooting/bien/database-migration-heroku-to-aws-rds.mdx (1)
14-16: Falta coma tras el año-**Date:** December 19, 2024 +**Date:** December 19, 2024,
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (13)
docs/troubleshooting/bien/database-maintenance-window-strategies.mdx(1 hunks)docs/troubleshooting/bien/database-migration-data-integrity-issues.mdx(1 hunks)docs/troubleshooting/bien/database-migration-environment-variables.mdx(1 hunks)docs/troubleshooting/bien/database-migration-heroku-to-aws-rds.mdx(1 hunks)docs/troubleshooting/bien/database-restore-pod-procedures.mdx(1 hunks)docs/troubleshooting/bien/deployment-old-pods-not-terminating.mdx(1 hunks)docs/troubleshooting/bien/deployment-stuck-creating-status.mdx(1 hunks)docs/troubleshooting/bien/deployment-teams-instances-not-creating.mdx(1 hunks)docs/troubleshooting/bien/deployment-timeout-database-migrations.mdx(1 hunks)docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx(1 hunks)docs/troubleshooting/bien/dns-resolution-failure-mysql-redis.mdx(1 hunks)docs/troubleshooting/bien/docker-daphne-logging-configuration.mdx(1 hunks)docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/troubleshooting/bien/deployment-old-pods-not-terminating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ods Not Terminating Date: June 10, 2024 Category: Workload Tags: De...
(MISSING_COMMA_AFTER_YEAR)
[style] ~604-~604: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dns-resolution-failure-mysql-redis.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dis Connections Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx
[grammar] ~13-~13: Ensure spelling is correct
Context: ...item"; # Doppler Integration Issues in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ues in SleakOps Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~21-~21: Ensure spelling is correct
Context: ... for environment variable management in SleakOps deployments experience issues where var...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...ts and Doppler references configured in SleakOps Error Conditions: - Variables not...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...er configuration is correctly set up in SleakOps: 1. Check Docker Arguments: ```...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...opriate scope - Update the secret in SleakOps To ensure environment variables are refr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~199-~199: Ensure spelling is correct
Context: ... ``` 4. Hybrid Approach: - Use SleakOps secrets for critical variables - Use...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~401-~401: Ensure spelling is correct
Context: ...ct=YOUR_PROJECT" | jq '.configs' ``` SleakOps Integration Check: 1. **Verify Secre...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~627-~627: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-migration-data-integrity-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ntegrity Issues Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...duction database migration processes in SleakOps, users may experience issues where the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...o production transfer - Migration tool: SleakOps database migration utilities - Database...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~256-~256: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/docker-daphne-logging-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...hne Applications Date: January 21, 2025 Category: Workload Tags: Do...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-maintenance-window-strategies.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...indow Strategies Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...ication-Level Maintenance Mode"> Since SleakOps doesn't currently provide a built-in ma...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~524-~524: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-timeout-database-migrations.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...atabase Migrations Date: April 25, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~71-~71: Ensure spelling is correct
Context: ...ncrease pre-deploy timeout limits"> In SleakOps, you can configure longer timeout limit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/deployment-stuck-creating-status.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Creating Status Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~181-~181: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deployment status ...
(DEEP_PROFOUND)
[style] ~597-~597: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-migration-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Configuration Date: December 11, 2024 Category: Project Tags: Dat...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...LLOWED_ORIGINS` - Environment variables not accessible to migration processes **Relevant Conf...
(NOT_ABLE_PREMIUM)
[style] ~455-~455: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-restore-pod-procedures.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...in Pod Environment Date: March 21, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...omain Providers Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not w...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...egation appears correctly configured in Route53 - Domain registrar (DonWeb) reports del...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~36-~36: Ensure spelling is correct
Context: ...AWS Certificate Manager (ACM) - Target: SleakOps deployment with Load Balancer **Error ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~136-~136: Ensure spelling is correct
Context: ...NAME record for domain validation is in Route53 - The validation record should be: `...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~155-~155: Ensure spelling is correct
Context: ...y="SleakOps Domain Configuration"> For SleakOps deployments, ensure proper domain confi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...ps Domain Settings:** - Update your SleakOps project configuration to use the custom...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~335-~335: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-migration-heroku-to-aws-rds.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...roku to AWS RDS Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~442-~442: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-teams-instances-not-creating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ces Not Creating Date: January 15, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~282-~282: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deep cluster analy...
(DEEP_PROFOUND)
[style] ~453-~453: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
🪛 Gitleaks (8.27.2)
docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx
79-79: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
(curl-auth-header)
🔇 Additional comments (5)
docs/troubleshooting/bien/dns-resolution-failure-mysql-redis.mdx (1)
10-10: Ruta de importación: comprueba la capitalización
@site/src/components/HomepageFeatures/troubleshootingitemusa minúsculas, pero normalmente el componente se llamaTroubleshootingItem.jsx/tsx.
En sistemas case-sensitive el build revienta si el nombre no coincide exactamente. Verifica el nombre real del archivo o ajusta el import.docs/troubleshooting/bien/docker-daphne-logging-configuration.mdx (1)
10-11: Posible ruta con mayúsculas/minúsculas incorrectasEl import apunta a
@site/src/components/HomepageFeatures/troubleshootingitem, pero en la mayoría del repo el componente se llamaTroubleshootingItem.jsx/tsx(inicial mayúscula).
En sistemas case-sensitive (Linux en producción) esto romperá el build de Docusaurus.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";¿Confirmás el nombre exacto del archivo antes de que despleguemos “a las piñas”? 😉
docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx (1)
11-11: Ruta con posible problema de “case-sensitivity”.En muchos sistemas de archivos (p. ej. Linux en CI) la ruta es sensible a mayúsculas. El componente suele llamarse
TroubleshootingItem.tsx/.jsx, pero aquí se importa comotroubleshootingitem, provocando unModule not found.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";Verifica la ruta real antes de hacer push.
docs/troubleshooting/bien/deployment-teams-instances-not-creating.mdx (1)
10-11: Ignora la sugerencia de mayúsculas en la importación
El fichero se llama realmentetroubleshootingitem.jsx(todo en minúsculas) y la ruta
@site/src/components/HomepageFeatures/troubleshootingitemcoincide perfectamente. No hay riesgo de fallo de compilación al usar minúsculas.Likely an incorrect or invalid review comment.
docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx (1)
10-10: Confirmar que el componenteTroubleshootingItemsigue vivoSe eliminó
FAQItemen este PR; asegurad que@site/src/components/HomepageFeatures/troubleshootingitemexiste, exporta por defecto y no quedó renombrado en el refactor.
Si cambió la ubicación/nombre, este import romperá la build de Docusaurus.
| <TroubleshootingItem id="docker-compose-configuration" summary="Complete docker-compose.yml configuration"> | ||
|
|
||
| Here's a complete example of how to configure your `docker-compose.yml`: | ||
|
|
||
| ```yaml | ||
| version: "3.8" | ||
|
|
||
| services: | ||
| web: | ||
| build: . | ||
| ports: | ||
| - "8000:8000" | ||
| environment: | ||
| - DEBUG=1 | ||
| - PYTHONUNBUFFERED=1 # Important for real-time log output | ||
| command: > | ||
| daphne | ||
| --bind 0.0.0.0 | ||
| --port 8000 | ||
| --access-log /dev/stdout | ||
| --proxy-headers | ||
| myproject.asgi:application | ||
| logging: | ||
| driver: "json-file" | ||
| options: | ||
| max-size: "10m" | ||
| max-file: "3" | ||
| # Remove these if not needed for your use case | ||
| # stdin_open: true | ||
| # tty: true | ||
| ``` | ||
|
|
||
| </TroubleshootingItem> | ||
|
|
||
| <TroubleshootingItem id="dockerfile-optimization" summary="Dockerfile optimizations for logging"> |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Ids duplicados en <TroubleshootingItem> → colisión de anchors
El documento declara dos veces id="docker-compose-configuration".
Docusaurus generará anchors duplicados y el segundo elemento quedará inaccesible o sobrescribirá el primero.
-<TroubleshootingItem id="docker-compose-configuration" summary="Docker Compose configuration for logging">
+<TroubleshootingItem id="docker-compose-config-basic" summary="Docker Compose configuration for logging">
...
-<TroubleshootingItem id="docker-compose-configuration" summary="Docker Compose configuration for logging">
+<TroubleshootingItem id="docker-compose-config-advanced" summary="Docker Compose configuration for advanced logging">Renombrá uno de los id (y opcionalmente el summary) para evitar conflictos.
Also applies to: 343-409
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/docker-daphne-logging-configuration.mdx around
lines 120 to 154, there are duplicate TroubleshootingItem ids
"docker-compose-configuration" causing anchor collisions in Docusaurus. Rename
one of the duplicate ids to a unique value and optionally update its summary to
avoid conflicts and ensure both sections are accessible. Also check and fix the
same issue in lines 343 to 409.
| # Doppler Integration Issues in SleakOps | ||
|
|
||
| **Date:** December 19, 2024 | ||
| **Category:** Dependency | ||
| **Tags:** Doppler, Environment Variables, Secrets, Configuration, Deployment | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
❓ Verification inconclusive
La guía está en inglés dentro de la carpeta de español.
El objetivo del PR indica “add troubleshooting category in Spanish”, pero todo el contenido (título, secciones, ejemplos) está en inglés. Esto rompe la consistencia de la documentación multilenguaje y la UX de los lectores hispanohablantes.
Recomendación: traducir el documento completo o moverlo a la carpeta de inglés antes de fusionar.
Revisar idioma y ubicación del documento de Doppler
El archivo docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx está en inglés dentro de la carpeta de contenidos en español, rompiendo la consistencia de la documentación multilenguaje. Para corregirlo, tradúzcanlo al español o muévanlo a la carpeta de inglés antes de fusionar.
- Ubicación afectada:
•docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx - Acciones recomendadas:
• Traducir todo el contenido al español.
• O mover el archivo adocs/troubleshooting/en/.
¡En SleakOps arreglamos los conflictos a las piñas! 🥊
🧰 Tools
🪛 LanguageTool
[grammar] ~13-~13: Ensure spelling is correct
Context: ...item"; # Doppler Integration Issues in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ues in SleakOps Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/doppler-integration-troubleshooting.mdx around
lines 13 to 18, the document is written in English but located in the Spanish
content folder, breaking language consistency. To fix this, either translate the
entire document content into Spanish or move the file to the English folder at
docs/troubleshooting/en/ before merging.
| # DNS Delegation Issues with Route53 and Domain Providers | ||
|
|
||
| **Date:** December 19, 2024 | ||
| **Category:** Provider | ||
| **Tags:** DNS, Route53, AWS, Domain, Delegation, Troubleshooting | ||
|
|
||
| ## Problem Description | ||
|
|
||
| **Context:** User is trying to configure a custom domain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not working properly despite correct Route53 configuration. | ||
|
|
||
| **Observed Symptoms:** | ||
|
|
||
| - DNS delegation appears correctly configured in Route53 | ||
| - Domain registrar (DonWeb) reports delegation is configured but "not propagating because DNS servers are not configured in the hosting provider" | ||
| - NS records are not replicating properly across DNS servers | ||
| - SSL certificate validation may be failing | ||
| - Domain does not resolve to the intended AWS infrastructure | ||
|
|
||
| **Relevant Configuration:** | ||
|
|
||
| - Domain: Custom domain (.com.ar) | ||
| - DNS Provider: AWS Route53 | ||
| - Domain Registrar: DonWeb (or similar) | ||
| - SSL: AWS Certificate Manager (ACM) | ||
| - Target: SleakOps deployment with Load Balancer | ||
|
|
||
| **Error Conditions:** | ||
|
|
||
| - DNS propagation fails despite correct NS delegation | ||
| - Certificate validation issues | ||
| - Domain does not resolve to target infrastructure | ||
| - NS records show inconsistent results across different DNS checkers | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Contenido completamente en inglés dentro de la categoría española
El objetivo del PR es “añadir categoría de troubleshooting en español”, pero todo el artículo está en inglés. O traducimos o movemos el archivo. De lo contrario quedará un mix raro que confundirá a la peña.
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...omain Providers Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not w...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...egation appears correctly configured in Route53 - Domain registrar (DonWeb) reports del...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~36-~36: Ensure spelling is correct
Context: ...AWS Certificate Manager (ACM) - Target: SleakOps deployment with Load Balancer **Error ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx
between lines 12 and 44, the content is entirely in English but the category is
set to Spanish. To fix this, either translate the entire article into Spanish to
match the category or move the file to an English category to maintain
consistency and avoid confusing readers.
| --- | ||
| sidebar_position: 3 | ||
| title: "DNS Delegation Issues with Route53 and Domain Providers" | ||
| description: "Solution for DNS delegation problems when configuring custom domains with Route53 and external domain registrars" | ||
| date: "2024-12-19" | ||
| category: "provider" | ||
| tags: ["dns", "route53", "aws", "domain", "delegation", "troubleshooting"] | ||
| --- |
There was a problem hiding this comment.
💡 Verification agent
❓ Verification inconclusive
Metadatos en inglés dentro de la carpeta “bien” generan ruido
La ruta docs/troubleshooting/bien/ corresponde a la nueva categoría en español, sin embargo en el front-matter todo está en inglés (title, description, mes en inglés, etc.). Para mantener coherencia:
-title: "DNS Delegation Issues with Route53 and Domain Providers"
-description: "Solution for DNS delegation problems when configuring custom domains with Route53 and external domain registrars"
-date: "2024-12-19"
+title: "Problemas de delegación DNS con Route53 y proveedores de dominios"
+description: "Guía de solución para problemas de delegación DNS al configurar dominios personalizados con Route53 y registradores externos"
+date: "2024-12-19" # o “19-12-2024” si queréis formato castellanoDe paso, el PR introduce documentación “en español”; revisad si vais a traducir el resto del cuerpo o mover este artículo a una carpeta de idioma inglés.
Revisar coherencia de idioma en front-matter (carpeta “bien” → español)
El artículo está ubicado en docs/troubleshooting/bien/, que corresponde a contenido en español, pero el front-matter está en inglés. Para mantener la consistencia:
-
Archivo afectado:
•docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx(líneas 1–8) -
Metadata actual:
--- -title: "DNS Delegation Issues with Route53 and Domain Providers" -description: "Solution for DNS delegation problems when configuring custom domains with Route53 and external domain registrars" -date: "2024-12-19" +title: "Problemas de delegación DNS con Route53 y proveedores de dominios" +description: "Guía de solución para problemas de delegación DNS al configurar dominios personalizados con Route53 y registradores externos" +date: "2024-12-19" # o “19-12-2024” si preferís formato DD-MM-AAAA tags: ["dns", "route53", "aws", "dominio", "delegación", "troubleshooting"] ---
-
Pasos a seguir:
- Ajustar
title,descriptiony, si os encaja, el formato dedateal estilo español. - Decidir si:
- Traducís también el resto del cuerpo al español, o
- Mantenéis este artículo en inglés y lo movéis a
docs/troubleshooting/en/.
- Ajustar
¡En sleakops arreglamos los conflictos a las piñas!
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/dns-delegation-route53-domain-configuration.mdx
lines 1 to 8, the front-matter metadata is in English but the file is located in
the Spanish content folder "bien". To fix this, translate the title,
description, and date format in the front-matter to Spanish to maintain language
consistency. Additionally, decide whether to translate the entire article to
Spanish or move the file to the English folder "docs/troubleshooting/en/" if you
want to keep it in English.
| ] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
💡 Verification agent
❓ Verification inconclusive
Ruta de import dudosa
@site/src/components/HomepageFeatures/troubleshootingitem puede haber quedado obsoleta tras la eliminación de FAQItem. Verifica que el componente siga en ese path o actualiza la ruta; de lo contrario, Docusaurus petará… ¡y a las piñas no compila nadie!
🏁 Script executed:
#!/usr/bin/env bash
# ¡A las piñas! Buscando el archivo del componente TroubleshootingItem
fd -I TroubleshootingItem -e tsx -e jsxLength of output: 41
Importación de TroubleshootingItem rota
La ruta
@site/src/components/HomepageFeatures/troubleshootingitem
no coincide con ningún archivo en src/components/HomepageFeatures, por lo que Docusaurus fallará al compilar. Por favor:
• Comprueba el nombre y la extensión reales del componente (p. ej. TroubleshootingItem.tsx o .jsx).
• Actualiza la importación en docs/troubleshooting/bien/database-maintenance-window-strategies.mdx (línea 18).
Posible corrección:
- import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+ import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";¡En sleakops arreglamos los conflictos a las piñas!
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-maintenance-window-strategies.mdx at line
18, the import path for TroubleshootingItem is incorrect and does not match any
file in src/components/HomepageFeatures. Verify the exact filename and extension
of the TroubleshootingItem component (e.g., TroubleshootingItem.tsx or .jsx) in
that directory, then update the import statement to use the correct path and
filename with proper casing and extension to fix the broken import.
| CURRENT_RS=$(kubectl get deployment $DEPLOYMENT -n $NAMESPACE -o jsonpath='{.status.conditions[?(@.type=="Progressing")].reason}') | ||
|
|
||
| # Delete old replica sets (keep latest 3) | ||
| kubectl get replicasets -n $NAMESPACE -l app=$DEPLOYMENT --sort-by='.metadata.creationTimestamp' | tail -n +4 | awk '{print $1}' | xargs -r kubectl delete replicaset -n $NAMESPACE | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Obtención del ReplicaSet actual es incorrecta
jsonpath='{.status.conditions[?(@.type=="Progressing")].reason}' devuelve “NewReplicaSet” y no el nombre real. El script borrará lo que no debe o nada, y las piñas vuelan. Usa:
CURRENT_RS=$(kubectl get deployment $DEPLOYMENT -n $NAMESPACE -o jsonpath='{.status.updatedReplicaset}')🤖 Prompt for AI Agents
In docs/troubleshooting/bien/deployment-old-pods-not-terminating.mdx around
lines 375 to 379, the current method to get the ReplicaSet name uses a jsonpath
that returns the reason string instead of the actual ReplicaSet name, causing
incorrect deletions. Replace the jsonpath expression with one that correctly
retrieves the updated ReplicaSet name, such as using
'{.status.updatedReplicaset}', to ensure the script targets the correct
ReplicaSet.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Ruta de import con posible error de “case-sensitivity”
Si el componente está realmente exportado como TroubleshootingItem.tsx (con mayúscula inicial) en el sistema de ficheros, usar @site/src/components/HomepageFeatures/troubleshootingitem puede romper el build en macOS/Linux debido a la sensibilidad a mayúsculas del FS.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-migration-environment-variables.mdx around
lines 10 to 11, the import path for TroubleshootingItem may have incorrect
casing that can cause build failures on case-sensitive file systems like macOS
or Linux. Verify the exact filename casing of TroubleshootingItem.tsx in the
filesystem and update the import statement to match that casing exactly, for
example changing "troubleshootingitem" to "TroubleshootingItem" if needed.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Mismo problema de importación que en el otro documento
Asegúrate de usar el mismo case que el fichero real para evitar errores en CI.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/deployment-timeout-database-migrations.mdx at lines
10 to 11, the import statement for TroubleshootingItem uses incorrect casing.
Verify the exact filename and folder casing of the TroubleshootingItem component
and update the import path to match it exactly, ensuring consistent case
sensitivity to prevent CI errors.
| @@ -0,0 +1,442 @@ | |||
| --- | |||
| sidebar_position: 3 | |||
There was a problem hiding this comment.
🛠️ Refactor suggestion
sidebar_position duplicado dentro del mismo sub-menú
Tres archivos en bien/ usan sidebar_position: 3. Docusaurus colocará dos detrás de otro, pero el orden final puede ser impredecible y confuso. Asigna posiciones únicas (p.ej. 3, 4, 5).
Also applies to: 6-6
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-migration-heroku-to-aws-rds.mdx at line 2
and also in line 6, the sidebar_position is duplicated as 3 in multiple files
within the same submenu, causing unpredictable ordering in Docusaurus. Assign
unique sidebar_position values to each file, for example, use 3, 4, 5, etc., to
ensure a clear and consistent sidebar order.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Import con mayúsculas/minúsculas inconsistente
Repite el ajuste de case para evitar fallos de compilación.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-migration-heroku-to-aws-rds.mdx around
lines 10 to 11, the import statement for TroubleshootingItem has inconsistent
casing that may cause compilation errors. Adjust the import path to match the
exact case of the file and folder names as they appear in the project directory
to ensure consistent casing and prevent build failures.
Add multiple troubleshooting guides covering issues like web service domain configuration, VPN connectivity, Redis connection errors, deployment failures, and more. Each document follows a consistent structure with problem description, symptoms, and detailed solutions including workarounds and best practices.
There was a problem hiding this comment.
Actionable comments posted: 20
♻️ Duplicate comments (5)
docs/troubleshooting/bien/database-restore-pod-management.mdx (1)
10-10: Verifica la ruta del componente.Mismo comentario que en el archivo anterior respecto a
troubleshootingitem.docs/troubleshooting/bien/dns-propagation-public-deployment.mdx (1)
10-11: Ruta del componente podría ser inválidaMismo comentario que en el archivo anterior: verifica la existencia y capitalización de
HomepageFeatures/troubleshootingitem.docs/troubleshooting/bien/dns-delegation-ssl-certificate-validation.mdx (1)
10-11: Import del componente: riesgo de build rotoComprueba la ruta/capitalización de
troubleshootingitem. Un fallo aquí tira el deploy a las piñas.docs/troubleshooting/bien/domain-ns-delegation-replication-issues.mdx (1)
10-11: Posible import erróneo del componenteRevisa capitalización/ruta de
troubleshootingitempara evitar fallos en producción.docs/troubleshooting/bien/domain-delegation-production-environments.mdx (1)
10-11: Ruta/capitalización del componenteÚltimo recordatorio: asegura que el componente existe exactamente con la ruta indicada o el build caerá.
🧹 Nitpick comments (48)
docs/troubleshooting/bien/django-migration-conflicts-database-import.mdx (1)
14-17: Añade la coma de estilo tras el año en la fechaPara mantener coherencia con el estilo editorial y evitar la advertencia de LanguageTool, pon una coma después del año:
-**Date:** December 20, 2024 +**Date:** December 20, 2024,docs/troubleshooting/bien/deployment-newrelic-pkg-resources-warning.mdx (2)
15-17: Falta la coma de estilo tras el añoEn la línea con la fecha:
**Date:** December 11, 2024Falta una coma tras el año para cumplir guías de estilo inglesas (“December 11, 2024,”). No es bloqueante, pero mejor mantener consistencia con otros docs.
47-70: Código de ejemplo: lenguajetxtno colorea y genera warning en PrismLos bloques
setuptools<81se renderizan sin resaltado y a veces provocan aviso en Prism. Cambia
txt→texto elimina el especificador:-```txt +```text setuptools<81</blockquote></details> <details> <summary>docs/troubleshooting/bien/deployment-fargate-vcpu-quota-limit.mdx (2)</summary><blockquote> `14-16`: **Añade la coma de cortesía tras el año en la fecha** Para cumplir con las guías de estilo y evitar la advertencia *MISSING_COMMA_AFTER_YEAR*, añade una coma tras “2025”. Ejemplo: ```diff -**Date:** February 13, 2025 +**Date:** February 13, 2025, ... -_This FAQ was automatically generated on February 13, 2025 based on a real user query._ +_This FAQ was automatically generated on February 13, 2025, based on a real user query._Also applies to: 198-198
198-198: “FAQ” o “Troubleshooting” — decide y mantén coherenciaEl pie de página menciona “This FAQ…”, pero todo el documento y la nueva categoría giran en torno a troubleshooting. Considera reemplazar “FAQ” por “troubleshooting article” para evitar confusión.
docs/troubleshooting/bien/dependencies-monitoring-graphs-not-displaying.mdx (3)
14-17: Duplicación innecesaria de metadatos dentro del cuerpoLas líneas con Date, Category y Tags repiten información que ya está en el front-matter. Esto genera ruido visual y posibles incongruencias futuras. Recomiendo eliminarlas o al menos reducirlas:
-**Date:** January 22, 2025 -**Category:** Dependency -**Tags:** Monitoring, RDS, OpenSearch, Graphs, Dependencies
64-84: Evitar hard-coding de fechas en ejemplos CLIEl rango
--start-time/--end-timeestá fijado al 22-01-2025. Los usuarios copiarán y fallará fuera de ese día. Propón variables o comentario:# Sustituye START y END por el rango deseado aws cloudwatch get-metric-statistics \ ... --start-time <START_ISO8601> \ --end-time <END_ISO8601> \
126-128: Pie de página refiere a “FAQ” en lugar de “Troubleshooting”La última línea dice “This FAQ was automatically generated...”. Como FAQItem se eliminó y este archivo es un troubleshooting, conviene actualizar para evitar confusión:
-_This FAQ was automatically generated on January 22, 2025 based on a real user query._ +_Documento de troubleshooting generado automáticamente el 22 de enero de 2025 a partir de una consulta real de usuario._docs/troubleshooting/bien/database-typeorm-ssl-connection-error.mdx (2)
14-14: Falta la coma tras el año.Las guías de estilo recomiendan
January 15, 2024en lugar deJanuary 15 2024.-**Date:** January 15, 2024 +**Date:** January 15, 2024,
234-234: Otra coma perdida después del año.-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._docs/troubleshooting/bien/database-restore-pod-management.mdx (3)
14-14: Falta coma tras 2025.-**Date:** March 26, 2025 +**Date:** March 26, 2025,
201-203:activeDeadlineSecondsybackoffLimitok, pero falta ejemplo dettlSecondsAfterFinished.Añadirlo ayuda a limpiar jobs viejos sin intervención manual.
232-232: Coma que se escapó de nuevo.-_This FAQ was automatically generated on March 26, 2025 based on a real user query._ +_This FAQ was automatically generated on March 26, 2025, based on a real user query._docs/troubleshooting/bien/database-postgresql-restore-errors.mdx (3)
14-14: Añade la coma después del año.-**Date:** January 15, 2024 +**Date:** January 15, 2024,
50-56: Cuidado con variables shell entrecomilladas.Si alguna variable puede contener espacios, envolver todo el bloque con comillas triples o usar
--dbname=$URLevitará fallos.
161-161: Última coma pendiente.-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._docs/troubleshooting/bien/database-performance-sql-query-optimization.mdx (4)
14-14: Coma tras el año, otra vez.-**Date:** December 19, 2024 +**Date:** December 19, 2024,
76-82: Ejemplo de índice: usa nombres consistentes.Conviene mostrar
CREATE INDEX idx_your_table_column_name ...para reforzar la convención de estilos y evitar colisiones.
195-202: Matar queries: privilegios requeridos.
pg_terminate_backendnecesita superuser. Añade nota para evitar frustraciones cuando el comando falla.
206-208: Coma final también aquí.-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_This FAQ was automatically generated on December 19, 2024, based on a real user query._docs/troubleshooting/bien/django-celery-appregistrynotready-error.mdx (2)
1-8: Coma faltante en la fecha del front-matterPor estilo (Chicago/APA) debería ir una coma tras el año para “December 26, 2024,” o, ya que el documento será en español, convendría cambiar a formato “26 de diciembre de 2024”.
210-213: Frase final marca “FAQ” pero el documento es “Troubleshooting”La nota de pie dice “This FAQ was automatically generated…”; sin embargo, el artículo forma parte de la categoría de troubleshooting, no de FAQ. Ajustar el texto evita confusiones.
docs/troubleshooting/bien/dns-cloudflare-route53-configuration.mdx (1)
14-16: Fecha mal formateada / estilo incoherente
December 19, 2024está en inglés dentro de documentación marcada como “bien” (es-ES). Usa ISO 8601 (2024-12-19) o “19 de diciembre de 2024”, y añade la coma tras el año si mantienes el formato en inglés.docs/troubleshooting/bien/dns-propagation-public-deployment.mdx (1)
14-16: Formato de fechaAplica el mismo criterio de formato coherente para
December 10, 2024.docs/troubleshooting/bien/dns-delegation-ssl-certificate-validation.mdx (1)
14-16: Fecha sin coma y en inglésEstándar de fecha incoherente con el idioma objetivo. Ajusta a ISO o español.
docs/troubleshooting/bien/domain-ns-delegation-replication-issues.mdx (1)
14-16: Revisa formato de fechaAñade coma o cambia a formato español: “15 de enero de 2024”.
docs/troubleshooting/bien/domain-delegation-production-environments.mdx (1)
14-16: Fecha en inglés dentro de docs en españolUniforma la fecha a ISO o al formato español y añade la coma.
docs/troubleshooting/bien/domain-certificate-delegation-error.mdx (2)
14-16: Falta coma tras el año en la fechaEl corrector de estilo marca la ausencia de la coma después de la fecha completa. Pequeño detalle, pero mejor dejarlo prolijo:
-**Date:** December 19, 2024 +**Date:** December 19, 2024,
165-165: Coma perdida en la leyenda finalPor coherencia con el cambio anterior:
-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_This FAQ was automatically generated on December 19, 2024, based on a real user query._docs/troubleshooting/bien/domain-migration-custom-domains.mdx (2)
14-16: Añadir coma después del año en la fechaPara mantener consistencia de estilo:
-**Date:** January 15, 2024 +**Date:** January 15, 2024,
228-228: Coma faltante en la nota de generación automática-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._docs/troubleshooting/bien/deployment-environment-variables-migration-issues.mdx (1)
10-10: Posible error de mayúsculas/minúsculas en la ruta del componenteEl import declara
troubleshootingitem(todo en minúsculas) mientras que el JSX usa<TroubleshootingItem>. En sistemas case-sensitive esto rompe el build. Asegúrate de que el nombre del archivo exportado coincida exactamente.docs/troubleshooting/bien/deployment-service-name-length-limit.mdx (1)
10-10: Revisa la coincidencia de mayúsculas en el importMismo comentario que en otros archivos:
troubleshootingitemvs<TroubleshootingItem>.docs/troubleshooting/bien/docker-build-cache-issues.mdx (1)
10-10: Ruta del componente sensible a mayúsculasVerifica el casing del import para evitar errores de compilación en producción.
docs/troubleshooting/bien/deployment-automatic-updates-github.mdx (1)
10-10: Chequea el casing del componente importadoDe nuevo,
troubleshootingitemminúscula vs<TroubleshootingItem>.docs/troubleshooting/bien/deployment-stuck-state-resolution.mdx (1)
10-10: Casing del importMismo detalle de mayúsculas/minúsculas que en los otros archivos.
docs/troubleshooting/bien/deployment-build-failed-production.mdx (1)
74-76: Evita ejemplos con tokens “reales” en la documentaciónAunque aquí se usa
YOUR_TOKEN, conviene resaltar al lector que nunca devele un token real en ejemplos de cURL. Añadir una nota aclaratoria previene copiar/pegar descuidado.docs/troubleshooting/bien/docker-build-cache-no-cache-option.mdx (1)
14-14: Pequeño detalle de estilo en la fechaEn el resto de la documentación en inglés usas la coma antes del año (“February 10, 2025”). Mantén coherencia: “February 10, 2025,” o cambia a formato ISO (
2025-02-10) para evitar avisos de linters.docs/troubleshooting/bien/deployment-migration-hooks-troubleshooting.mdx (1)
32-35: “Log visibility” suena confuso en singularEl ítem “Log visibility: Limited error reporting in deployment logs” mezcla singular/plural; sugerencia rápida:
- Log visibility: Limited error reporting in deployment logs + Log visibility: Limited error reporting in deployment log outputMejora la claridad sin tocar el significado.
docs/troubleshooting/bien/deployment-redis-communication-error.mdx (2)
14-17: Fecha y etiquetas sin localizarEl documento está bajo la ruta
bien/pero mantiene las etiquetas y la fecha en inglés. Para coherencia con la nueva categoría en español, adapta los textos:-**Date:** January 15, 2024 -**Category:** Deployment -**Tags:** Deployment, Redis, Communication, Troubleshooting, Push +**Fecha:** 15 de enero de 2024 +**Categoría:** Despliegue +**Etiquetas:** Despliegue, Redis, Comunicación, Solución de problemas, Push
62-76: Plantilla de soporte en inglésEl ejemplo de correo al soporte está íntegramente en inglés. Si el objetivo es ofrecer documentación en español, considera traducir la plantilla o añadir versión bilingüe para evitar confusión a los lectores hispanohablantes.
¡En SleakOps arreglamos los conflictos a las piñas, pero mejor si nos entendemos todos!docs/troubleshooting/bien/deployment-build-failures-during-updates.mdx (2)
14-16: Fecha sin coma y en inglésAñade la coma tras el año o, mejor aún, localiza a formato español:
-**Date:** October 14, 2024 +**Fecha:** 14 de octubre de 2024
78-83: Duplicación de guiones en listasLos puntos 1-3 ya indican listas; los guiones anidados producen ruido visual. Simplifica a un único nivel para mejorar legibilidad.
docs/troubleshooting/bien/deployment-pending-nodepool-changes.mdx (2)
65-76: Inconsistencia MB vs MiBEl texto recomienda 512 MB, pero el YAML usa
512Mi. Ajusta la unidad o la cifra para mantener coherencia:-**Minimum RAM**: 512MB +**RAM mínima**: 512Mi
128-134: Filtrogrep -v "READY"puede omitir líneas útilesLa expresión excluirá cualquier despliegue que contenga la palabra “READY”, incluso aquellos no listos (p.e.
0/1 READY). Considera filtrar el encabezado contail -n +2o usar--no-headersen kubectl.docs/troubleshooting/bien/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
14-16: Fecha en inglésPara mantener consistencia con la categoría en español:
-**Date:** March 5, 2025 +**Fecha:** 5 de marzo de 2025docs/troubleshooting/bien/deployment-image-not-updating-develop-branch.mdx (2)
14-16: Localizar metadatosSigue la misma línea que los otros documentos:
-**Date:** December 19, 2024 +**Fecha:** 19 de diciembre de 2024
175-185: Uso decdsin restaurar directorioDentro del script
for, usarcdpermanente puede dejarte en un path inesperado si falla una iteración. Propónpushd/popd:- cd $repo + pushd "$repo" # … comandos … - cd .. + popd
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (33)
docs/troubleshooting/bien/database-performance-sql-query-optimization.mdx(1 hunks)docs/troubleshooting/bien/database-postgresql-restore-errors.mdx(1 hunks)docs/troubleshooting/bien/database-restore-pod-management.mdx(1 hunks)docs/troubleshooting/bien/database-typeorm-ssl-connection-error.mdx(1 hunks)docs/troubleshooting/bien/dependencies-monitoring-graphs-not-displaying.mdx(1 hunks)docs/troubleshooting/bien/dependency-connection-timeout-mysql-redis.mdx(1 hunks)docs/troubleshooting/bien/deployment-automatic-updates-github.mdx(1 hunks)docs/troubleshooting/bien/deployment-build-failed-production.mdx(1 hunks)docs/troubleshooting/bien/deployment-build-failures-during-updates.mdx(1 hunks)docs/troubleshooting/bien/deployment-environment-variables-migration-issues.mdx(1 hunks)docs/troubleshooting/bien/deployment-fargate-vcpu-quota-limit.mdx(1 hunks)docs/troubleshooting/bien/deployment-helm-selector-immutable-error.mdx(1 hunks)docs/troubleshooting/bien/deployment-image-not-updating-develop-branch.mdx(1 hunks)docs/troubleshooting/bien/deployment-migration-hooks-troubleshooting.mdx(1 hunks)docs/troubleshooting/bien/deployment-missing-tolerations-after-nodepool-changes.mdx(1 hunks)docs/troubleshooting/bien/deployment-newrelic-pkg-resources-warning.mdx(1 hunks)docs/troubleshooting/bien/deployment-pending-nodepool-changes.mdx(1 hunks)docs/troubleshooting/bien/deployment-redis-communication-error.mdx(1 hunks)docs/troubleshooting/bien/deployment-service-name-length-limit.mdx(1 hunks)docs/troubleshooting/bien/deployment-stuck-starting-state.mdx(1 hunks)docs/troubleshooting/bien/deployment-stuck-state-resolution.mdx(1 hunks)docs/troubleshooting/bien/django-celery-appregistrynotready-error.mdx(1 hunks)docs/troubleshooting/bien/django-migration-conflicts-database-import.mdx(1 hunks)docs/troubleshooting/bien/dns-cloudflare-route53-configuration.mdx(1 hunks)docs/troubleshooting/bien/dns-delegation-ssl-certificate-validation.mdx(1 hunks)docs/troubleshooting/bien/dns-propagation-public-deployment.mdx(1 hunks)docs/troubleshooting/bien/docker-build-cache-issues.mdx(1 hunks)docs/troubleshooting/bien/docker-build-cache-no-cache-option.mdx(1 hunks)docs/troubleshooting/bien/docker-build-environment-variables.mdx(1 hunks)docs/troubleshooting/bien/domain-certificate-delegation-error.mdx(1 hunks)docs/troubleshooting/bien/domain-delegation-production-environments.mdx(1 hunks)docs/troubleshooting/bien/domain-migration-custom-domains.mdx(1 hunks)docs/troubleshooting/bien/domain-ns-delegation-replication-issues.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/troubleshooting/bien/database-typeorm-ssl-connection-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Error with RDS Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~234-~234: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/docker-build-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...bles Not Available Date: March 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~20-~20: Consider using “inaccessible” to avoid wordiness.
Context: ...defined in SleakOps Docker settings are not accessible during the build process, specifically ...
(NOT_ABLE_PREMIUM)
[style] ~194-~194: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/docker-build-cache-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...es in Production Date: January 15, 2024 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/domain-delegation-production-environments.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...on Environments Date: December 20, 2024 Category: Project Tags: Dom...
(MISSING_COMMA_AFTER_YEAR)
[style] ~206-~206: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 20, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-helm-selector-immutable-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Immutable Error Date: December 19, 2024 Category: Workload Tags: He...
(MISSING_COMMA_AFTER_YEAR)
[style] ~181-~181: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-pending-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Nodepool Changes Date: January 23, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/domain-migration-custom-domains.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...in Configuration Date: January 15, 2024 Category: Project Tags: Dom...
(MISSING_COMMA_AFTER_YEAR)
[style] ~228-~228: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-postgresql-restore-errors.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Restore Errors Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~161-~161: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/database-restore-pod-management.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ore Pod Management Date: March 26, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~232-~232: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 26, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-migration-hooks-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ployment Issues Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps deployment system - Hook type: Database...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/database-performance-sql-query-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ry Optimization Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dependency-connection-timeout-mysql-redis.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Timeout Issues Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~142-~142: Ensure spelling is correct
Context: ...rces can cause connection issues: In SleakOps: 1. Go to your **API service configur...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~237-~237: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-stuck-starting-state.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Starting State Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~87-~87: Ensure spelling is correct
Context: ...ld arguments are properly configured in SleakOps project settings. </TroubleshootingIte...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-environment-variables-migration-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...le After Migration Date: April 24, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Affected environments: Develop...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...ariables"> During platform migrations, SleakOps may update how secrets and environment ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/dns-delegation-ssl-certificate-validation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...idation Issues Date: September 10, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...ecords - Records should point to AWS Route53 name servers <...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dns-cloudflare-route53-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~52-~52: Ensure spelling is correct
Context: ...he NS (Name Server) records provided by Route53 2. In Cloudflare: - Create NS records...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~56-~56: Ensure spelling is correct
Context: ...e NS records pointing your subdomain to Route53 name servers - Example: `subdomain.y...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...- Example: subdomain.yourdomain.com → Route53 NS records 3. Verify delegation: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~80-~80: Ensure spelling is correct
Context: ...status: DNS only (gray cloud) **In Route53 (if using delegation):** Type: A (...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~89-~89: Ensure spelling is correct
Context: ...Important: Use A (Alias) records in Route53 for better performance and automatic IP...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~158-~158: Ensure spelling is correct
Context: ...ction:** - Use A (Alias) records in Route53 for AWS resources - Use CNAME record...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/deployment-image-not-updating-develop-branch.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ges After Merge Date: December 19, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...: Git merge/push to develop - Platform: SleakOps automated deployment **Error Condition...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...y="Force a complete rebuild"> To force SleakOps to rebuild without cache: 1. Go to you...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~138-~138: Ensure spelling is correct
Context: ...s resolved: 1. Check image tags in SleakOps: - Go to Workloads → **Your Serv...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dependencies-monitoring-graphs-not-displaying.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Not Displaying Date: January 22, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~92-~92: Ensure spelling is correct
Context: ...ummary="Platform fix in progress"> The SleakOps team is working on a comprehensive solu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/deployment-automatic-updates-github.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pdates from GitHub Date: August 2, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ory are automatically deployed to their SleakOps environment during testing phases. **O...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...- Source: GitHub repository - Platform: SleakOps - Environment: Development/Testing - Do...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...nnection:** - Go to your Project in SleakOps - Navigate to Settings → *Repository...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~87-~87: Ensure spelling is correct
Context: ... the deployment workflow"> The typical SleakOps deployment workflow: ```mermaid graph ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~201-~201: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on August 2, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-build-failed-production.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...g Loading Issues Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Environment: Production - Platform: SleakOps - Issue type: Build failure + Log acces...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ... dashboard log loading problems"> When SleakOps dashboard logs won't load: **Browser-r...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~127-~127: Ensure spelling is correct
Context: ...utions:** 1. Log out and log back into SleakOps 2. Check if other dashboard sections work p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~134-~134: Ensure spelling is correct
Context: ...s) If problem persists: - Contact SleakOps support with specific build ID - Provid...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-build-failures-during-updates.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Platform Updates Date: October 14, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ild process fails temporarily while the SleakOps platform undergoes maintenance or updat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...rm communications**: - Subscribe to SleakOps status updates - Check email notific...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~155-~155: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-fargate-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ring Deployment Date: February 13, 2025 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-missing-tolerations-after-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...er Nodepool Changes Date: March 5, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ... 1. Navigate to your service in the SleakOps dashboard 2. Click "Edit" on the affected deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~131-~131: Ensure spelling is correct
Context: ...odepool changes**: Coordinate with your SleakOps team before major changes 2. **Update d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on March 5, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-newrelic-pkg-resources-warning.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sources Warning Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~21-~21: Ensure spelling is correct
Context: ...oy a Python project to production using SleakOps CLI but encounters build failures relat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~134-~134: Consider using a different verb for a more formal wording.
Context: ...only suppresses the warning but doesn't fix the underlying issue. </Troubleshootin...
(FIX_RESOLVE)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-redis-communication-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...munication Error Date: January 15, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~158-~158: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-service-name-length-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...gth Limit Error Date: February 13, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...to deploy a project with a long name in SleakOps. The automatically generated Kubernetes ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~174-~174: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/deployment-stuck-state-resolution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Pending State Date: December 28, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~181-~181: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 28, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/django-celery-appregistrynotready-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...yNotReady Error Date: December 26, 2024 Category: Workload Tags: Dj...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider changing the order of words to improve your wording.
Context: ... execute properly - Application appears to not be fully initialized when Celery tasks ...
(TO_NOT_VB)
[style] ~212-~212: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 26, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/django-migration-conflicts-database-import.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Database Import Date: December 20, 2024 Category: Project Tags: Dja...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~137-~137: Ensure spelling is correct
Context: ...Handling in SleakOps deployments"> For SleakOps deployments with pre-upgrade hooks: 1....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/dns-propagation-public-deployment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic Deployments Date: December 10, 2024 Category: Project Tags: DNS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...when accessing the URL - Application is not accessible via the public domain **Relevant Confi...
(NOT_ABLE_PREMIUM)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/docker-build-cache-no-cache-option.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Build Arguments Date: February 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/domain-certificate-delegation-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ring Deployment Date: December 19, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~31-~31: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “above”, “above-mentioned”, “aforementioned”, or “as previously mentioned” (in the document).
Context: ... Relevant Configuration: - Domain: hub.supra.social (production domain) - Certifica...
(SUPRA)
[style] ~56-~56: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “above”, “above-mentioned”, “aforementioned”, or “as previously mentioned” (in the document).
Context: ...cates** - Find the affected domain (hub.supra.social) - Click on **Certificate Ma...
(SUPRA)
[style] ~116-~116: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “above”, “above-mentioned”, “aforementioned”, or “as previously mentioned” (in the document).
Context: ...rds** - Verify that DNS records for supra.social are correct - Ensure no exte...
(SUPRA)
[style] ~121-~121: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “above”, “above-mentioned”, “aforementioned”, or “as previously mentioned” (in the document).
Context: ...domain Configuration** - Check that hub.supra.social is properly configured - Ver...
(SUPRA)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/domain-ns-delegation-replication-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...plication Issues Date: January 15, 2024 Category: General Tags: Dom...
(MISSING_COMMA_AFTER_YEAR)
[style] ~210-~210: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
🪛 Gitleaks (8.27.2)
docs/troubleshooting/bien/deployment-build-failed-production.mdx
74-74: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
(curl-auth-header)
🔇 Additional comments (13)
docs/troubleshooting/bien/deployment-newrelic-pkg-resources-warning.mdx (1)
1-9: Contenido en inglés en una ruta “bien” (es-ES): revisar coherencia de idiomaEl archivo está bajo
docs/troubleshooting/bien/…, presumiblemente pensado para la categoría española, pero todo el contenido—including title, description y cuerpo—está en inglés. Esto rompe la consistencia del nuevo apartado en español y puede confundir al buscador interno.Confirma si:
- Realmente queréis que esté en español.
- Existe ya la versión inglesa en otra ruta y este documento es redundante.
Si hace falta, puedo ayudar a traducir o mover el archivo.
docs/troubleshooting/bien/deployment-fargate-vcpu-quota-limit.mdx (1)
10-10: Ruta de importación correcta
He verificado que el archivo existe ensrc/components/HomepageFeatures/troubleshootingitem.jsxy la ruta importada (@site/src/components/HomepageFeatures/troubleshootingitem) coincide exactamente, por lo que no habrá errores de compilación. ¡Podemos resolver este comentario sin más a las piñas!docs/troubleshooting/bien/database-typeorm-ssl-connection-error.mdx (2)
10-10: Ruta de import dudosa (mayúsculas/minúsculas).En algunos sistemas de archivos (Linux),
troubleshootingitemyTroubleshootingItemno son equivalentes. Verifica que el nombre real del componente coincida exactamente con la ruta usada para evitar errores en tiempo de build.
195-199: Propiedadmodeno reconocida por TypeORM.
ssl.modees ignorado por el driverpg. Si la intención era documentarsslmode=requiredepsql, acláralo o elimínalo para no confundir.docs/troubleshooting/bien/database-restore-pod-management.mdx (1)
92-96: Peligro al borrar pods en caliente.Borrar el pod sin eliminar el Job reiniciará el restore automáticamente. Añade la instrucción
kubectl delete jobcomo paso previo o advierte del restart para evitar sorpresas… ¡en SleakOps arreglamos los conflictos a las piñas pero mejor prevenir!docs/troubleshooting/bien/database-postgresql-restore-errors.mdx (1)
86-98: Drop/alter en orden correcto 👍Excelente explicación paso a paso.
docs/troubleshooting/bien/database-performance-sql-query-optimization.mdx (1)
165-171: Unidades de tiempo en configuración.
connection_timeout: 30spuede no ser soportado por todos los ORMs si esperan número. Indica formato esperado o usa comentario aclaratorio.docs/troubleshooting/bien/django-celery-appregistrynotready-error.mdx (1)
118-125:celery callya está eliminado y sustituido correctamente
El fragmento de código ya comenta o elimina el uso decelery -A your_project call …y muestra únicamentecelery -A your_project worker --loglevel=infoy el uso de.delay()para ejecuciones puntuales. No se requieren cambios adicionales.docs/troubleshooting/bien/dns-cloudflare-route53-configuration.mdx (1)
10-11: Importación correcta: no hay desajuste de mayúsculasLa ruta importada
@site/src/components/HomepageFeatures/troubleshootingitem
coincide exactamente con el archivo
src/components/HomepageFeatures/troubleshootingitem.jsx.
No existe ninguna discrepancia de capitalización que pueda romper el build.¡En sleakops arreglamos los conflictos a las piñas!
Likely an incorrect or invalid review comment.
docs/troubleshooting/bien/deployment-environment-variables-migration-issues.mdx (1)
2-2: sidebar_position duplicado en toda la categoríaTodos los artículos del directorio
bien/usansidebar_position: 3. Docusaurus acepta valores repetidos, pero el orden final queda indefinido. Asigna posiciones únicas para evitar que la navegación cambie cada vez que se regenere el índice.docs/troubleshooting/bien/deployment-build-failed-production.mdx (1)
10-11: Verifica la ruta del componente importado
@site/src/components/HomepageFeatures/troubleshootingitemusa minúsculas, mientras que el componente se referencia comoTroubleshootingItem. Si el nombre real del archivo esTroubleshootingItem.tsx/tsx, el import fallará en sistemas sensibles a mayúsculas (p. ej. Linux).docs/troubleshooting/bien/dependency-connection-timeout-mysql-redis.mdx (1)
11-11: Ruta potencialmente incorrecta al componenteTroubleshootingItemEl archivo se importa desde
@site/src/components/HomepageFeatures/troubleshootingitem(todo en minúsculas).
En la mayoría de sistemas de archivos sensibles a mayúsculas (Linux, CI), el nombre del fichero suele serTroubleshootingItem.tsx/tsxy la carpetaTroubleshootingItem.Verifica la ruta o usa un alias consistente para evitar “Module not found” cuando despleguemos.
docs/troubleshooting/bien/deployment-stuck-starting-state.mdx (1)
10-10: Cuidado con la ruta del componenteTroubleshootingItemMismo comentario que en el otro archivo: la carpeta en minúsculas puede fallar en compilaciones Linux.
Confirma que el path exacto coincide con el nombre real del fichero.
| ssl: { | ||
| rejectUnauthorized: false, | ||
| }, | ||
| // ... other options |
There was a problem hiding this comment.
🛠️ Refactor suggestion
rejectUnauthorized: false es un atajo peligroso.
Está bien para pruebas, pero en producción desactiva la validación del certificado. Sugiero añadir un aviso más explícito recomendando subir el CA de RDS o usar IAM auth.
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/database-typeorm-ssl-connection-error.mdx around
lines 72 to 75, the use of rejectUnauthorized: false in the SSL options is risky
for production as it disables certificate validation. Update the documentation
to include a clear warning that this setting is only suitable for testing and
recommend uploading the RDS CA certificate or using IAM authentication for
secure production environments.
| --- | ||
| sidebar_position: 3 | ||
| title: "Dependencies Monitoring Graphs Not Displaying" | ||
| description: "Solution for RDS and OpenSearch monitoring graphs showing empty or not loading properly" | ||
| date: "2025-01-22" | ||
| category: "dependency" | ||
| tags: ["monitoring", "rds", "opensearch", "graphs", "dependencies"] | ||
| --- |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Título y metadatos deberían estar en español para mantener la coherencia del nuevo “troubleshooting” en español
El documento se encuentra dentro de la carpeta bien/ (es-ES), pero el title, description, category y las etiquetas están en inglés. Esto rompe la navegación multilenguaje y la búsqueda en Docusaurus.
-title: "Dependencies Monitoring Graphs Not Displaying"
-description: "Solution for RDS and OpenSearch monitoring graphs showing empty or not loading properly"
-category: "dependency"
-tags: ["monitoring", "rds", "opensearch", "graphs", "dependencies"]
+title: "Los gráficos de monitorización de dependencias no se muestran"
+description: "Solución para gráficos vacíos de RDS y OpenSearch en la monitorización"
+category: "dependencia"
+tags: ["monitorización", "rds", "opensearch", "gráficos", "dependencias"]Además, la fecha “January 22, 2025” debería ir en formato español (“22 de enero de 2025”).
¡En SleakOps arreglamos los conflictos a las piñas, pero mejor si los evitamos desde el front-matter!
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| --- | |
| sidebar_position: 3 | |
| title: "Dependencies Monitoring Graphs Not Displaying" | |
| description: "Solution for RDS and OpenSearch monitoring graphs showing empty or not loading properly" | |
| date: "2025-01-22" | |
| category: "dependency" | |
| tags: ["monitoring", "rds", "opensearch", "graphs", "dependencies"] | |
| --- | |
| --- | |
| sidebar_position: 3 | |
| title: "Los gráficos de monitorización de dependencias no se muestran" | |
| description: "Solución para gráficos vacíos de RDS y OpenSearch en la monitorización" | |
| date: "2025-01-22" | |
| category: "dependencia" | |
| tags: ["monitorización", "rds", "opensearch", "gráficos", "dependencias"] | |
| --- |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/dependencies-monitoring-graphs-not-displaying.mdx
lines 1 to 8, the front-matter metadata including title, description, category,
and tags are in English while the document is in the Spanish folder, causing
inconsistency in multilingual navigation and search. Change all these metadata
fields to Spanish equivalents and update the date format to the Spanish style
"22 de enero de 2025" to maintain coherence and proper localization.
| tags: ["monitoring", "rds", "opensearch", "graphs", "dependencies"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Posible fallo por mayúsculas/minúsculas en el import del componente
@site/src/components/HomepageFeatures/troubleshootingitem usa todo en minúsculas; si el archivo real se llama TroubleshootingItem.tsx/.jsx, los sistemas case-sensitive (Linux, CI) petarán a lo grande. Verifica el nombre exacto y ajústalo:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/dependencies-monitoring-graphs-not-displaying.mdx
at line 10, the import path for TroubleshootingItem uses all lowercase letters,
which may cause errors on case-sensitive systems if the actual file name uses
uppercase letters. Verify the exact filename casing of TroubleshootingItem and
update the import statement to match it exactly, including uppercase letters as
needed.
| tags: | ||
| ["mysql", "redis", "timeout", "connection", "troubleshooting", "networking"] | ||
| --- |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Formato YAML incorrecto en la clave tags
En YAML, una lista anidada bajo una clave debe escribirse con guiones o toda en la misma línea.
La combinación que se usa aquí (tags: en una línea y la lista JSON-like en la siguiente) no es válida y rompe el parseo del front-matter en Docusaurus.
-tags:
- ["mysql", "redis", "timeout", "connection", "troubleshooting", "networking"]
+tags:
+ - mysql
+ - redis
+ - timeout
+ - connection
+ - troubleshooting
+ - networking📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| tags: | |
| ["mysql", "redis", "timeout", "connection", "troubleshooting", "networking"] | |
| --- | |
| tags: | |
| - mysql | |
| - redis | |
| - timeout | |
| - connection | |
| - troubleshooting | |
| - networking | |
| --- |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/dependency-connection-timeout-mysql-redis.mdx
around lines 7 to 9, the YAML front-matter uses an invalid format for the tags
key by placing a JSON-like list on a new line. Fix this by either placing the
entire list inline after the tags key or by using hyphens to list each tag on
separate lines under the tags key, ensuring proper YAML syntax for parsing in
Docusaurus.
| // Recommended Redis connection configuration | ||
| const redis = require("redis"); | ||
|
|
||
| const client = redis.createClient({ | ||
| host: process.env.REDIS_HOST, | ||
| port: process.env.REDIS_PORT, | ||
| connectTimeout: 60000, | ||
| lazyConnect: true, | ||
| retryDelayOnFailover: 100, | ||
| maxRetriesPerRequest: 3, | ||
| }); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Opciones no válidas para redis.createClient
Las propiedades lazyConnect, retryDelayOnFailover y maxRetriesPerRequest corresponden a ioredis, no a redis@4.x. Con node-redis esas claves se ignoran y confunden.
Si el ejemplo pretende usar redis@4, sería más seguro:
-const client = redis.createClient({
- host: process.env.REDIS_HOST,
- port: process.env.REDIS_PORT,
- connectTimeout: 60000,
- lazyConnect: true,
- retryDelayOnFailover: 100,
- maxRetriesPerRequest: 3,
-});
+const client = redis.createClient({
+ socket: {
+ host: process.env.REDIS_HOST,
+ port: process.env.REDIS_PORT,
+ connectTimeout: 60000,
+ reconnectStrategy: retries => Math.min(retries * 100, 3000),
+ },
+});O bien indica explícitamente que el ejemplo usa ioredis.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // Recommended Redis connection configuration | |
| const redis = require("redis"); | |
| const client = redis.createClient({ | |
| host: process.env.REDIS_HOST, | |
| port: process.env.REDIS_PORT, | |
| connectTimeout: 60000, | |
| lazyConnect: true, | |
| retryDelayOnFailover: 100, | |
| maxRetriesPerRequest: 3, | |
| }); | |
| // Recommended Redis connection configuration | |
| const redis = require("redis"); | |
| const client = redis.createClient({ | |
| socket: { | |
| host: process.env.REDIS_HOST, | |
| port: process.env.REDIS_PORT, | |
| connectTimeout: 60000, | |
| reconnectStrategy: retries => Math.min(retries * 100, 3000), | |
| }, | |
| }); |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/dependency-connection-timeout-mysql-redis.mdx
around lines 123 to 133, the redis.createClient options include lazyConnect,
retryDelayOnFailover, and maxRetriesPerRequest which are invalid for redis@4.x
and only apply to ioredis. To fix this, either remove these invalid options and
use only valid redis@4.x options or explicitly state that the example uses
ioredis to avoid confusion.
| tags: ["django", "migrations", "database", "import", "troubleshooting"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Import mal capitalizado puede romper la compilación MDX
En sistemas de archivos sensibles a mayúsculas (Linux, CI), el nombre del componente debe coincidir exactamente con el nombre del archivo. El path actual usa troubleshootingitem en minúsculas; normalmente el archivo se llama TroubleshootingItem.tsx.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/django-migration-conflicts-database-import.mdx at
line 10, the import statement uses a lowercase 'troubleshootingitem' which may
cause build failures on case-sensitive file systems. Update the import path to
match the exact casing of the file name, changing it to 'TroubleshootingItem' to
ensure it matches the component file name exactly.
| **Date:** January 15, 2024 | ||
| **Category:** Project | ||
| **Tags:** Docker, Cache, Deployment, Build, ECR | ||
|
|
There was a problem hiding this comment.
Contenido en inglés vs. categoría “bien” en español
Sobra decirlo: “en sleakops arreglamos los conflictos a las piñas”, pero mejor que la guía también esté en castellano.
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...es in Production Date: January 15, 2024 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/docker-build-cache-issues.mdx around lines 14 to
17, the content is in English but the category is labeled "bien" in Spanish.
Translate the content into Spanish to match the category or change the category
to English to align with the content language. Ensure consistency between the
language of the content and the category label.
| RUN echo "Master key: $RAILS_MASTER_KEY" | ||
|
|
||
| # Optional: Set it as environment variable for runtime | ||
| ENV RAILS_MASTER_KEY=$RAILS_MASTER_KEY | ||
| ``` |
There was a problem hiding this comment.
No hagas echo del master key en la imagen: expone secretos
Mostrar el valor con RUN echo "Master key: $RAILS_MASTER_KEY" vuelca la clave al historial de capas (docker history) y a los logs de build. Sustituye por una verificación indirecta o elimínalo:
-RUN echo "Master key: $RAILS_MASTER_KEY"
+# Comprobación no reveladora
+RUN test -n "$RAILS_MASTER_KEY"Así evitamos filtrar credenciales accidentalmente.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| RUN echo "Master key: $RAILS_MASTER_KEY" | |
| # Optional: Set it as environment variable for runtime | |
| ENV RAILS_MASTER_KEY=$RAILS_MASTER_KEY | |
| ``` | |
| # Comprobación no reveladora | |
| RUN test -n "$RAILS_MASTER_KEY" | |
| # Optional: Set it as environment variable for runtime | |
| ENV RAILS_MASTER_KEY=$RAILS_MASTER_KEY |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/docker-build-environment-variables.mdx around lines
54 to 58, remove the line that echoes the master key during the Docker build
process to avoid exposing secrets in the image layers and build logs. Instead,
either eliminate the echo command entirely or replace it with an indirect
verification method that does not reveal the actual key value, ensuring
credentials are not accidentally leaked.
| tags: ["deployment", "domain", "certificate", "acm", "troubleshooting"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta de import incorrecta: cuidado con el case-sensitive
En sistemas de archivos sensibles a mayúsculas/minúsculas (p. ej. Linux), troubleshootingitem en minúsculas no encontrará un componente exportado como TroubleshootingItem.tsx.
Antes de que tengamos que arreglar el build a las piñas, cambia la ruta:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/domain-certificate-delegation-error.mdx at line 10,
the import path for TroubleshootingItem uses incorrect casing. Change the import
path to match the exact case of the exported component file, likely
"TroubleshootingItem" with an uppercase T and I, to avoid case-sensitive
filesystem errors on Linux.
| tags: ["domain", "migration", "dns", "alias", "custom-domain"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta de import potencialmente rota
Mismo problema de mayúsculas que en el otro archivo; evitemos romper el build a las piñas:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/bien/domain-migration-custom-domains.mdx at line 10, the
import path for TroubleshootingItem likely has incorrect capitalization. Verify
the exact casing of the directory and filename in the import path and correct it
to match the actual file system to prevent build errors caused by case
sensitivity.
refactor: reorganize troubleshooting documentation structure by moving files to new locations docs: update and improve troubleshooting guides with current best practices
…e issues Add comprehensive troubleshooting documentation in Spanish for: - Doppler integration issues with environment variables - Fargate pods not terminating causing cost increases Both guides include detailed solutions, best practices, and checklists
- Remove outdated troubleshooting files - Add new and improved troubleshooting guides for common issues - Organize files into better directory structure - Update content with latest solutions and best practices
restructure spanish documentation files by moving troubleshooting articles from 'user_issues' to 'bien' directory and updating their content
remove obsolete troubleshooting documentation files in Spanish and add updated versions with current best practices and solutions
Add new documentation files covering database performance optimization, Docker build errors, DNS delegation issues, Fargate pod termination problems, infrastructure architecture diagrams, and DNS migration from DonWeb to AWS. Each document follows a structured troubleshooting format with detailed solutions and best practices.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (9)
docs/troubleshooting/bien/dns-migration-donweb-to-aws.mdx (3)
12-17: Metadatos internos escritos en inglés en una guía marcada como “bien” (es-ES)
El objetivo del PR es aportar documentación en español, sin embargo el título, la descripción y los campos dentro del contenido están en inglés. Esto genera incoherencia y puede confundir a los lectores.Propón traducir los encabezados y bloques descriptivos al español o, al menos, añadir una versión localizada.
14-16: Coma faltante después del año y doble espacio
Siguiendo la sugerencia del linter, agrega la coma tras el año para una fecha estilo “January 15, 2024” o traduce la fecha al formato español “15 de enero de 2024”.-**Date:** January 15, 2024 +**Fecha:** 15 de enero de 2024
283-284: El pie dice “FAQ” pero el componente FAQItem fue eliminado
Mantener la referencia a “FAQ” puede llevar a confusión y contradice la nota del PR (se quitó el componenteFAQItem).-_This FAQ section was automatically generated on January 15, 2024, based on a real user inquiry._ +_Esta guía de troubleshooting se generó automáticamente el 15-01-2024 a partir de una consulta real de usuario._docs/troubleshooting/bien/dns-domain-delegation-cloudflare-route53.mdx (4)
10-11: Posible discrepancia en el casing del componente importado
Igual que en el otro documento, confirma que el archivo seaTroubleshootingItem.jsx/tsxcon mayúsculas.
14-14: Falta de coma después del año-**Date:** December 21, 2024 +**Fecha:** 21 de diciembre de 2024
67-69: CloudFlare vs. Cloudflare (consistencia de marca)
La marca oficial es “Cloudflare”. Homogeneiza para evitar errores de búsqueda y SEO.
219-221: Referencia a FAQ en pie de página
Mismo comentario que en el otro archivo: la nota final debería referirse a “guía de troubleshooting”.docs/troubleshooting/bien/database-performance-optimization.mdx (2)
14-16: Añade la coma tras el año para cumplir estiloLanguageTool marca la falta de coma después de “2024”. Propongo un ajuste mínimo:
-**Date:** January 15, 2024 +**Date:** January 15, 2024,
205-205: Segundo---puede resultar confusoDentro de MDX,
---se interpreta como una regla horizontal. Al estar ya fuera del front-matter, no causa error, pero podría parecer un nuevo delimitador y confundir a quien mantenga el fichero. Valora sustituirlo por***o un<hr />explícito.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
docs/troubleshooting/bien/database-performance-optimization.mdx(1 hunks)docs/troubleshooting/bien/dns-domain-delegation-cloudflare-route53.mdx(1 hunks)docs/troubleshooting/bien/dns-migration-donweb-to-aws.mdx(1 hunks)
🪛 LanguageTool
docs/troubleshooting/bien/dns-migration-donweb-to-aws.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...om DonWeb to AWS Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dns-domain-delegation-cloudflare-route53.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 21, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...on: Requires proper domain delegation - SleakOps validation: Checks delegation once duri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...anding SleakOps DNS Management"> How SleakOps manages DNS: 1. **Centralized Manage...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~50-~50: Ensure spelling is correct
Context: ... DNS:** 1. Centralized Management: SleakOps centralizes all DNS management in your ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ce Management**: Services deployed with SleakOps manage their DNS records automatically ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...ords:** - All DNS records generated by SleakOps are visible in the platform - Records i...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~59-~59: Ensure spelling is correct
Context: ...- Records are automatically managed for SleakOps services **For proper functionality, domains must b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ... Route53 nameservers 2. Subdomains of SleakOps-managed domains: Created as subdomain...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...*: Delegate only specific subdomains to Route53 # In CloudFlare, create NS records for subdomains: app.yourdomain.com NS ns-xxx.awsdns-xx.com app.yourdomain.com NS ns-xxx.awsdns-xx.co.uk app.yourdomain.com NS ns-xxx.awsdns-xx.net app.yourdomain.com NS ns-xxx.awsdns-xx.org 2. Use SleakOps subdomains: Create all Sl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...S ns-xxx.awsdns-xx.org ``` 2. Use SleakOps subdomains: Create all SleakOps servi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...Use SleakOps subdomains: Create all SleakOps services under a dedicated subdomain ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/database-performance-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tion and Scaling Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...load: Multiple pods running - Platform: SleakOps on AWS Error Conditions: - Timeou...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~183-~183: Ensure spelling is correct
Context: ...ly from the AWS Console even when using SleakOps: Steps: 1. Go to **AWS RDS Console...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~200-~200: Ensure spelling is correct
Context: ... the change Why this option isn't in SleakOps Console: SleakOps focuses on applicat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~200-~200: Ensure spelling is correct
Context: ...his option isn't in SleakOps Console:** SleakOps focuses on application deployment and m...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🧰 Additional context used
🪛 LanguageTool
docs/troubleshooting/bien/dns-migration-donweb-to-aws.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...om DonWeb to AWS Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/bien/dns-domain-delegation-cloudflare-route53.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 21, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...on: Requires proper domain delegation - SleakOps validation: Checks delegation once duri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...anding SleakOps DNS Management"> How SleakOps manages DNS: 1. **Centralized Manage...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~50-~50: Ensure spelling is correct
Context: ... DNS:** 1. Centralized Management: SleakOps centralizes all DNS management in your ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ce Management**: Services deployed with SleakOps manage their DNS records automatically ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...ords:** - All DNS records generated by SleakOps are visible in the platform - Records i...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~59-~59: Ensure spelling is correct
Context: ...- Records are automatically managed for SleakOps services **For proper functionality, domains must b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ... Route53 nameservers 2. Subdomains of SleakOps-managed domains: Created as subdomain...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...*: Delegate only specific subdomains to Route53 # In CloudFlare, create NS records for subdomains: app.yourdomain.com NS ns-xxx.awsdns-xx.com app.yourdomain.com NS ns-xxx.awsdns-xx.co.uk app.yourdomain.com NS ns-xxx.awsdns-xx.net app.yourdomain.com NS ns-xxx.awsdns-xx.org 2. Use SleakOps subdomains: Create all Sl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...S ns-xxx.awsdns-xx.org ``` 2. Use SleakOps subdomains: Create all SleakOps servi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...Use SleakOps subdomains: Create all SleakOps services under a dedicated subdomain ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/bien/database-performance-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tion and Scaling Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...load: Multiple pods running - Platform: SleakOps on AWS Error Conditions: - Timeou...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~183-~183: Ensure spelling is correct
Context: ...ly from the AWS Console even when using SleakOps: Steps: 1. Go to **AWS RDS Console...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~200-~200: Ensure spelling is correct
Context: ... the change Why this option isn't in SleakOps Console: SleakOps focuses on applicat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~200-~200: Ensure spelling is correct
Context: ...his option isn't in SleakOps Console:** SleakOps focuses on application deployment and m...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🔇 Additional comments (3)
docs/troubleshooting/bien/dns-migration-donweb-to-aws.mdx (1)
10-11: Revisa el nombre del componente importado (posible problema de mayúsculas/minúsculas)
En varios sistemas de archivos sensibles a mayúsculas,TroubleshootingItemdebería importarse con el mismo casing que el nombre del archivo origen (TroubleshootingItem.tsx/jsx). El path actual usatroubleshootingitem(todo en minúsculas).-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";Verifica cómo está escrito el archivo real para evitar un build roto “a las piñas”.
docs/troubleshooting/bien/dns-domain-delegation-cloudflare-route53.mdx (1)
14-16: Contenido en inglés vs. categoría en español
La sección debería estar completamente en español para alinearse con la nueva categoría “Troubleshooting” en español.docs/troubleshooting/bien/database-performance-optimization.mdx (1)
10-10: Comprueba la ruta y el case deTroubleshootingItemEl import apunta a
@site/src/components/HomepageFeatures/troubleshootingitemen minúsculas, pero luego se usaTroubleshootingItem(PascalCase). En entornos case-sensitive esto puede romper la build si el nombre real del archivo o del export no coincide. Además, asegura que el componente sigue presente tras eliminarFAQItem, o el MDX no se renderizará.
There was a problem hiding this comment.
Actionable comments posted: 49
♻️ Duplicate comments (50)
docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx (1)
10-10: Importación con capitalización incorrecta romperá el buildEl componente se llama
TroubleshootingItem.tsx, pero la ruta usatroubleshootingitem. En sistemas con FS case-sensitive esto explota.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-fargate-vcpu-quota-limit.mdx (2)
75-78: Reemplazar--service-code fargateporecspara que el comando funcioneEl CLI de AWS no reconoce
fargatecomoservice-code; para la cuotaL-3032A538hay que usarecs.
Este punto ya se señaló antes pero sigue sin corregirse.- aws service-quotas get-service-quota \ - --service-code fargate \ - --quota-code L-3032A538 + aws service-quotas get-service-quota \ + --service-code ecs \ + --quota-code L-3032A538
137-147: La métricaCPUUtilizationno vigila el cupo; usaAWS/Usageo Service QuotasEl alarmado con
CPUUtilizationmide consumo interno, no el límite de vCPU.
Para detectar que nos acercamos al cupo hay que usarAWS/Usage(ResourceCount) o habilitar métricas de Service Quotas.- MetricName: CPUUtilization - Namespace: AWS/ECS + MetricName: ResourceCount # vCPU usados + Namespace: AWS/Usage + Dimensions: + - Name: Type + Value: Resourcedocs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx (1)
10-10: Ruta con mayúsculas incorrectas: romperá el build en FS sensiblesEl import sigue apuntando a
troubleshootingitemen minúsculas; el componente se llamaTroubleshootingItem. En Linux esto peta y nos quedamos sin página. Cambia la ruta para que coincida exactamente con el nombre del fichero.docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx (2)
10-10: Corrige la capitalización en la ruta de importación
troubleshootingitemen minúsculas sigue sin coincidir conTroubleshootingItemy romperá el build de Docusaurus (los imports son case-sensitive). Cambia el path a.../TroubleshootingItemantes de que nos agarremos a las piñas con el CI.
139-146: Añade la advertencia sobre--fake-initialSigue faltando la nota que aclare que
--fake-initialdebe usarse sólo en la primera migración de cada app; de lo contrario se pueden saltar migraciones reales y dejar el esquema inconsistente. Inserta la advertencia justo debajo del snippet YAML.docs/troubleshooting/user_issues/deployment-helm-selector-immutable-error.mdx (1)
100-113: Placeholder de Helm roto por espacios extra – corrígelo yaLos espacios dentro de las llaves siguen ahí, lo que rompe la sintaxis de los templates y hará que
helm templatefalle al generar el YAML.- name: { { include "chart.fullname" . } } - labels: { { - include "chart.labels" . | nindent 4 } } + name: {{ include "chart.fullname" . }} + labels: {{- include "chart.labels" . | nindent 4 }} - matchLabels: { { - include "chart.selectorLabels" . | nindent 6 } } + matchLabels: {{- include "chart.selectorLabels" . | nindent 6 }} - labels: { { - include "chart.selectorLabels" . | nindent 8 } } + labels: {{- include "chart.selectorLabels" . | nindent 8 }}Sin este ajuste, los usuarios copiarán el fragmento y el upgrade volverá a fallar; arreglemos la fuente antes de que termine “a las piñas” en producción.
docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx (1)
10-11: Capitalización de la importación sigue mal
La ruta continúa controubleshootingitemen minúsculas cuando el resto del proyecto usaTroubleshootingItem. Esto rompe la importación en sistemas case-sensitive.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
72-79: Carácter Unicode incorrecto en la clavetolerationsSigue apareciendo
ː(U+02D0) en lugar de:. El YAML resultará inválido al copiarlo.-tolerationsː +tolerations:docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx (2)
7-8: Corrige la listatagsen el front-matter YAMLLa clave
tags:no está asociada a ningún valor por la indentación actual; la lista se interpreta como una nueva clave y rompe el parser de Docusaurus.-tags: - ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"] +tags: ["deployment", "build", "newrelic", "python", "pkg_resources", "setuptools"]
11-11: Capitaliza correctamente el import deTroubleshootingItemEl sistema de archivos en producción es case-sensitive; la ruta con minúsculas provocará un error de resolución del módulo.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/build-newrelic-pkg-resources-deprecation-warning.mdx (1)
10-10: Capitaliza correctamente el import deTroubleshootingItemLa ruta actual provocará fallos en entornos con distinción de mayúsculas/minúsculas.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx (1)
74-87:celeryno debe estar enINSTALLED_APPS(repetimos la piña 🚨).Como ya se comentó en el diff anterior,
celeryno registra unAppConfig; tenerlo aquí solo confunde y no aporta nada. El problema original (AppRegistryNotReady) suele provocarse precisamente por esta línea.- # Third-party apps - 'celery', - 'django_celery_beat', # If using periodic tasks + # Third-party apps + 'django_celery_beat', # Si usas tareas periódicasdocs/troubleshooting/user_issues/database-typeorm-ssl-connection-error.mdx (1)
72-76:rejectUnauthorized: falsesigue sin advertencia de seguridad
Mismo comentario realizado anteriormente; añadir un warning visible para que nadie copie-pegue una config insegura.Also applies to: 88-91
docs/troubleshooting/user_issues/docker-build-cache-no-cache-option.mdx (1)
76-79: ElCMDen forma de array no ejecutará la cadena con&&Comentario ya realizado en commits previos; usa
sh -cpara que el shell interprete&&.docs/troubleshooting/user_issues/deployment-build-failed-production.mdx (1)
10-10: Corregir capitalización del importPara que el build no explote a las piñas:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/cluster-critical-addons-node-failure.mdx (1)
11-11: Misma incongruencia de capitalización en la ruta del componenteAlinea la importación con el nombre real del archivo para evitar fallos en tiempo de compilación.
docs/troubleshooting/user_issues/docker-build-environment-variables.mdx (1)
10-10: Importación con mayúsculas inconsistentes (se repite la advertencia)Sigue el mismo patrón recomendado anteriormente para el componente.
docs/troubleshooting/user_issues/database-restore-pod-procedures.mdx (2)
50-56: Añadeset -o pipefailal script de restauraciónSin
pipefail, un error enpvopsqlpuede pasar desapercibido y el script continuará como si nada.-set -e +set -euo pipefail
155-158:resources.requests.storageno es válido en un contenedorEl tamaño debe declararse en el PVC, no en
resources.requests.- resources: - requests: - storage: "50Gi" # Adequate space for dumps +# Elimina esta sección; define la capacidad en el PVC `dump-pvc`docs/troubleshooting/user_issues/ci-cd-github-actions-not-triggering.mdx (1)
10-10: Ruta de importación con capitalización incorrecta
El componente se nombraTroubleshootingItem, pero la ruta usa todo en minúsculas. En entornos case-sensitive la documentación no compilará.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/ci-cd-pipeline-setup-troubleshooting.mdx (1)
10-10: Ruta de importación con capitalización incorrecta
Mismo problema de mayúsculas/minúsculas que en otros artículos; corrígelo para evitar fallos en la build de Docusaurus.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/cicd-pip-to-pipx-installation.mdx (1)
10-10: Ruta de importación con capitalización incorrecta
La referencia al componente no respeta la capitalización real del fichero. Cámbiala o la página fallará en producción.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-stuck-state-resolution.mdx (1)
10-10: Ruta de importación con capitalización incorrecta
El mismo detalle se repite aquí. Ajusta la ruta para que coincida con el nombre exacto del componente.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-migration-hooks-troubleshooting.mdx (1)
10-10: Ruta de importación con capitalización incorrecta
Sin esta corrección, la generación del sitio fallará en entornos Linux. ¡En SleakOps arreglamos los conflictos a las piñas! 😉-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/docker-build-cache-issues.mdx (1)
10-10: Corrige la capitalización en el import del componenteLa ruta contiene
troubleshootingitemen minúsculas; el fichero real esTroubleshootingItem.tsx. En sistemas case-sensitive esto rompe la build de Docusaurus.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";¡En SleakOps arreglamos los conflictos a las piñas!
docs/troubleshooting/user_issues/deployment-image-not-updating-develop-branch.mdx (1)
10-10: Corrige la capitalización en el import del componenteMismo problema de mayúsculas que ya se señaló; ajústalo para no romper la build.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";¡En SleakOps arreglamos los conflictos a las piñas!
docs/troubleshooting/user_issues/database-migration-data-integrity-issues.mdx (1)
124-130: Aviso repetido:psql -tdeja espacios → comparaciones fallan
Ya se comentó; sigue sin aplicarse la corrección.docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx (1)
10-10: Importación con mayúsculas/minúsculas inconsistentes – ya lo habíamos señaladoLa ruta del componente no respeta la mayúscula en
TroubleshootingItem, lo que revienta la build en entornos case-sensitive.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx (1)
10-10: Otra vez el componente en minúsculas – la CI no perdonaPon la T en mayúscula para que compile:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-automatic-updates-github.mdx (1)
10-10: Casing del componente rompe el build en minúsculasEl import usa
HomepageFeatures/troubleshootingitem, pero el archivo real esTroubleshootingItem. En sistemas case-sensitive (Linux, CI) fallará el build a las piñas.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx (2)
10-10: Import con casing incorrecto, mismo problema que antesSigue apareciendo el import en minúsculas. Corrige la ruta para evitar errores de compilación.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";
216-224: Faltaimport timeen el snippet de loggingEl ejemplo usa
time.time()pero no importatime; copiarlo así lanzaNameError.-import logging +import logging +import timedocs/troubleshooting/user_issues/dependencies-monitoring-graphs-not-displaying.mdx (2)
10-10: Import con casing inconsistente
2-2:sidebar_positionduplicadodocs/troubleshooting/user_issues/dns-delegation-ssl-certificate-validation.mdx (2)
10-10: Import con casing inconsistente
2-2:sidebar_positionduplicadodocs/troubleshooting/user_issues/cluster-upgrade-zero-downtime.mdx (2)
10-10: Import con casing inconsistente
2-2:sidebar_positionduplicadodocs/troubleshooting/user_issues/cluster-automatic-shutdown-startup-issues.mdx (2)
10-10: Import con casing inconsistente
2-2:sidebar_positionduplicadodocs/troubleshooting/user_issues/dns-resolution-failure-mysql-redis.mdx (2)
1-8:sidebar_positionduplicado
Igual que en otros archivos: usa posiciones únicas para evitar conflictos en la navegación.
10-10: Verifica el casing del import
Mismo comentario que en el documento anterior: confirma que el archivo existe en la ruta con el mismo casing.docs/troubleshooting/user_issues/cluster-addons-after-migration.mdx (2)
1-8:sidebar_positionrepetido
Asigna valores únicos.
10-10: Ruta del componente: confirma mayúsculas/minúsculasdocs/troubleshooting/user_issues/cluster-connection-troubleshooting.mdx (2)
1-8:sidebar_positionduplicado
Evita colisiones en la sidebar.
10-10: Confirma el casing del importdocs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx (3)
1-8:sidebar_positionduplicado
Asigna posiciones únicas.
10-10: Comprueba la ruta del componente
14-16: Añade coma tras el año
Mismo ajuste de estilo.
🧹 Nitpick comments (97)
docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx (1)
14-16: Añadir coma tras el año en la fecha (estilo)Por coherencia con el resto de la docu, se debería escribir “13 de febrero de 2025,” (coma después del año).
Aplica tanto en el bloque de metadatos como en la nota final.Also applies to: 174-174
docs/troubleshooting/user_issues/deployment-fargate-vcpu-quota-limit.mdx (1)
14-16: Falta coma después del añoPequeña corrección de estilo según las guías de redacción.
-**Date:** February 13, 2025 +**Date:** February 13, 2025,docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx (2)
14-14: Coma estilística faltante tras el añoPara evitar micro-cortes de lectura:
January 15, 2024→January 15, 2024,
451-454: Nota final desalineada con la secciónEl pie dice “This FAQ was automatically generated…” cuando el archivo es de troubleshooting, no de FAQ. Ajusta la referencia para evitar confusión.
docs/troubleshooting/user_issues/cluster-production-check-node-scaling.mdx (1)
52-54: Redundancia léxicaLa frase “Adds an additional node” repite concepto. Bastaría con “Adds a node” o, en español, “Añade un nodo”. Pequeño ajuste, pero suma a la claridad del texto.
docs/troubleshooting/user_issues/cors-configuration-troubleshooting.mdx (1)
14-16: Coma faltante tras el añoSegún los linters de estilo, debería colocarse una coma después de
2024para fechas mes-día-año.
Nit muy menor pero así evitamos warnings en el CI.-**Date:** December 19, 2024 +**Date:** December 19, 2024,docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx (1)
14-14: Coma faltante tras el año en fechasPara mantener consistencia editorial, añade una coma después del año en ambas fechas (“December 20, 2024,”).
Also applies to: 184-184
docs/troubleshooting/user_issues/deployment-helm-selector-immutable-error.mdx (2)
14-16: Puntualidad editorial: falta la coma tras el añoPor estilo y legibilidad, añade una coma tras “2024”:
**Date:** December 19, 2024,Es un detalle menor pero mantiene coherencia con otros artículos.
181-181: Consistencia en la fecha del aviso finalAquí también falta la coma tras el año:
_Este FAQ se generó automáticamente el 19 de diciembre de 2024, basado en una consulta real del usuario._Así evitamos el warning de LanguageTool y mantenemos uniforme la puntuación.
docs/troubleshooting/user_issues/cluster-manual-shutdown-scheduled-feature.mdx (4)
12-18: Incongruencia de idioma en un documento marcado como españolEl PR describe que se añade categoría de troubleshooting en español, pero el título, fecha y meta-datos están en inglés. Considera traducirlos para mantener coherencia con el resto de la documentación.
45-56: Faltan comas que aíslan el año y frase poco naturalEl título “Cluster Manual Shutdown Requires Scheduled Feature” y la frase “Manual shutdown requires Scheduled Shutdown feature enabled” contienen el giro “requires Scheduled” que suena poco natural en inglés técnico. Además, el estilo anglosajón suele separar el año con comas: “December 12, 2024”.
82-91: Repetición de adverbio “manually”La oración “Start the cluster manually when needed” ya implica la acción manual; se puede simplificar para evitar repetición (“start the cluster when needed”).
129-145: Duplicación implícita de información ‑ limitar verbosidadLa sección señala dos veces que es una “limitación de la plataforma” y que se mejorará. Podrías consolidar los bullets para evitar redundancia y hacer la lectura más ágil.
docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx (1)
14-14: Falta la coma después del año
Por estilo castellano-internacional:-**Date:** January 21, 2025 +**Date:** January 21, 2025,docs/troubleshooting/user_issues/cluster-nodepool-missing-after-shutdown.mdx (2)
12-17: Objetivo era documentación en español, pero el contenido está en inglésEl PR indica “add troubleshooting category in Spanish”, sin embargo este artículo completo está en inglés.
¿Se espera mantener dos versiones (en / es) o fue un descuido? Si toca internacionalizar, conviene mover este archivo a.../es/o traducirlo ahora para evitar deuda de localización.
141-144: Etiqueta “FAQ” desactualizada – coherencia con la nueva categoría de troubleshootingLa nota final dice:
_This FAQ was automatically generated..._Ya no usamos el componente
FAQItemy el documento está bajo Troubleshooting. Para evitar confusión del lector, cambia “FAQ” por “troubleshooting guide” o eliminá la línea.docs/troubleshooting/user_issues/aws-marketplace-login-setup-issue.mdx (2)
46-57: Lista numerada rota en MDX.Dentro de
<TroubleshootingItem>los números del flujo aparecen cada uno en su propia línea pero sin línea en blanco previa, provocando que MDX los renderice como párrafo y no como lista ordenada.Aplica un retorno de línea antes del
1.o usa un bloque Markdown separado:-When you subscribe to SleakOps through AWS Marketplace, there's a specific authentication flow that needs to be completed: - -1. **AWS Marketplace Subscription**: You subscribe through AWS +Cuando te suscribes a SleakOps a través de AWS Marketplace se dispara un flujo de autenticación: + +1. **Suscripción en AWS Marketplace**: te suscribes en AWS
164-164: “La FAQ” ya no corresponde con la nueva nomenclatura.Se indica:
_This FAQ was automatically generated on January 15, 2024...Si estamos migrando a “TroubleshootingItem” y eliminando
FAQItem, sustituye “FAQ” por “artículo de troubleshooting” o similar para mantener consistencia.docs/troubleshooting/user_issues/aws-ec2-public-ip-assignment.mdx (2)
170-171: Etiqueta “FAQ” incongruente con la sección de troubleshooting
La nota final habla de “FAQ” cuando el documento se sitúa bajo Troubleshooting. Cambiar “FAQ” por “artículo de troubleshooting” para evitar confusiones.
14-14: Pequeño detalle de estilo: coma después del año
Según varias guías de estilo, tras “January 15, 2024” debería ir una coma si continúa la oración. No rompe nada, pero queda más pulido.docs/troubleshooting/user_issues/celery-beat-duplicate-execution.mdx (3)
14-16: Añadir la coma obligatoria después del añoLos estilos editoriales en inglés recomiendan “December 23, 2024, Category…”. Falta la coma después de 2024.
-**Date:** December 23, 2024 +**Date:** December 23, 2024,
331-345: Ejemplo de código incompleto: faltaimport osEl bloque que muestra la configuración de
DATABASESusaos.environpero no importaos, lo que puede confundir a quien copie/pegue el ejemplo.-# Celery Beat runs in application context -# CronJob runs as separate container - ensure: +# Celery Beat runs in application context +# CronJob runs as separate container – ensure: +import os
1-8: Metadatos duplicadosEl campo
dateaparece tanto en el front-matter como dentro del documento. Mantén uno solo para evitar divergencias futuras.docs/troubleshooting/user_issues/cluster-understanding-ec2-instances-and-costs.mdx (2)
14-16: Añadir coma después del año para cumplir guías de estiloLos style-guides en inglés recomiendan separar el año con comas:
January 29, 2025,en vez deJanuary 29, 2025.
Mismo detalle al final del documento.Es solo un mimo tipográfico, pero así evitamos warnings innecesarios.
200-203: Incongruencia terminológica: “FAQ” vs. sección de troubleshootingLa nota final dice “This FAQ was automatically generated…” pero el documento pertenece a la nueva categoría de troubleshooting. Para no confundir al lector, podríamos reemplazar “FAQ” por “article” o “guide”.
-_This FAQ was automatically generated on January 29, 2025 based on a real user query._ +_This troubleshooting guide was automatically generated on January 29, 2025 based on a real user query._docs/troubleshooting/user_issues/cronjob-timezone-deployment-behavior.mdx (3)
14-16: Añadir coma después del año en la fecha
Según las reglas de estilo en inglés, se recomienda «October 24, 2024, …».-**Date:** October 24, 2024 +**Date:** October 24, 2024,
170-173: Misma corrección de coma en la leyenda final-_This FAQ was automatically generated on October 24, 2024 based on a real user query._ +_This FAQ was automatically generated on October 24, 2024, based on a real user query._
88-101: Advertencia sobre horario de verano (DST)
Sería útil mencionar explícitamente que la expresión30 20 * * *quedará desfasada si Argentina cambia el horario de verano, lo que obliga a ajustar la cron o utilizartimeZone:en v1.25+. Añadir una nota rápida evitará confusiones.docs/troubleshooting/user_issues/cloudfront-existing-s3-bucket.mdx (2)
14-16: Comas faltantes tras el año en fechas (nitpick de estilo)Las guías de estilo en inglés recomiendan: “December 19, 2024, …”.
No rompe nada, pero queda más prolijo y evita los flags de LanguageTool.Also applies to: 170-170
168-170: El pie menciona “FAQ” pero el documento es de troubleshootingPara evitar confusión:
-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_Este artículo de troubleshooting fue generado automáticamente el 19 de diciembre de 2024 a partir de una consulta real de usuario._docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
147-148: “FAQ” no encaja con la sección de troubleshootingEl cierre indica “This FAQ was automatically generated…” pero el documento es una guía de troubleshooting. Sustituir “FAQ” por “artículo de troubleshooting” para evitar confusión.
-_This FAQ was automatically generated on March 5, 2025 based on a real user query._ +_Este artículo de troubleshooting se generó automáticamente el 5 de marzo de 2025 a partir de una consulta real de usuario._docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx (1)
182-182: Pequeño ajuste de puntuaciónFalta la coma de cierre tras el año para mantener coherencia con el estilo usado arriba.
-_This FAQ was automatically generated on December 11, 2024 based on a real user query._ +_This FAQ was automatically generated on December 11, 2024, based on a real user query._docs/troubleshooting/user_issues/build-newrelic-pkg-resources-deprecation-warning.mdx (2)
14-16: Añade coma tras el año para consistencia estilística-**Date:** June 10, 2025 +**Date:** June 10, 2025,
192-192: Puntuación finalSe aplica el mismo criterio de coma que en las cabeceras.
-_This FAQ was automatically generated on June 10, 2025 based on a real user query._ +_This FAQ was automatically generated on June 10, 2025, based on a real user query._docs/troubleshooting/user_issues/aws-cost-monitoring-and-optimization.mdx (3)
14-17: Coma faltante tras el año en la fechaPara mantener consistencia editorial en la docu (y calmar a los linters de estilo), añade una coma después del año.
-**Date:** January 16, 2025 +**Date:** January 16, 2025,
69-73: Valor aproximado “~$15” puede confundirEl tilde
~dentro de la tabla se interpreta como markdown normal y se ve raro. Propón “≈ $15” o simplemente “$15”.
197-198: Pie de página inconsistente con el resto de FAQEl texto dice “FAQ” pero la sección es “Troubleshooting”. Cambiar a “Esta guía” evita confusión y mantiene naming consistente tras la remoción de
FAQItem.docs/troubleshooting/user_issues/cost-analysis-and-resource-optimization.mdx (3)
7-15: Lista de tags en brackets: YAML válido pero poco legibleEl formato:
tags: ["a", "b"]es admitido, pero al dividirlo en varias líneas entre corchetes se vuelve propenso a errores de indentación. Recomiendo formato clásico:
-tags: - [ - "cost-analysis", - "aws", - ... - ] +tags: + - cost-analysis + - aws + - grafana + - resource-optimization + - webservice + - database
22-25: Falta la coma tras el añoMismo detalle estilístico que en el otro documento.
-**Date:** December 19, 2024 +**Date:** December 19, 2024,
56-60: “crucial filter” → resalta con código inlinePara mejorar la lectura podrías resaltar
Charge Type = Usagecon backticks e incluir la ruta navegada (Cost Explorer → Filters).docs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx (2)
14-17: Coma faltante en la fecha (detalle de estilo).Por consistencia con el resto de docs:
December 26, 2024→December 26, 2024.
212-213: Etiqueta final inconsistente (“FAQ” vs “Troubleshooting”).El doc se presenta como guía de troubleshooting, pero la nota de cierre habla de “FAQ”. Cambiar “FAQ” por algo como “documento de troubleshooting” evitará confusión.
docs/troubleshooting/user_issues/aws-waf-application-load-balancer-protection.mdx (2)
14-14: Detalle de estilo/terminologíaPara seguir las guías de estilo en español y la localización coherente, cambiar:
-**Date:** December 19, 2024 +**Fecha:** 19 de diciembre de 2024
359-361: Referencia obsoleta a “FAQ”El pie dice “This FAQ was automatically generated…”, pero el documento es una guía de troubleshooting, no un FAQ, y además está prevista en español. Sustituir por algo como:
-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_Documento generado automáticamente el 19 de diciembre de 2024 a partir de una consulta real de usuario._docs/troubleshooting/user_issues/build-status-discrepancy-lens-vs-platform.mdx (2)
14-17: Metadatos repetidos e inconsistentesYa existe un front-matter con
date,tags, etc. Repetirlos en el cuerpo (líneas 14-17) añade ruido y obliga a mantener dos fuentes de verdad. Recomiendo eliminar la tabla de atributos del cuerpo.
169-169: Pie de página desfasado (“FAQ”)La nota final reza “This FAQ was automatically generated…” pero el documento es un artículo de troubleshooting, no una FAQ. Ajusta el texto para evitar confusión.
docs/troubleshooting/user_issues/deployment-pending-nodepool-changes.mdx (1)
14-14: Coma faltante tras el añoPor estilo editorial (y lo marca LanguageTool) agrega coma tras “23, 2024”.
Also applies to: 172-172
docs/troubleshooting/user_issues/database-postgresql-restore-errors.mdx (1)
14-14: Añadir coma después del año – coherencia con el resto de la docs.Also applies to: 161-161
docs/troubleshooting/user_issues/cluster-aws-vcpu-quota-limit.mdx (1)
14-17: Coma después del año en la fecha (nitpick)Algunos manuales de estilo en español recomiendan separar el año con comas:
**Date:** 24 de abril de 2024,…
Solo si quieres cumplir a rajatabla con esas guías.docs/troubleshooting/user_issues/ci-cd-build-stage-failure.mdx (1)
14-16: Falta la coma de cierre en la fecha
Añade una coma después del año para seguir la norma:10 de octubre de 2024,.docs/troubleshooting/user_issues/deployment-environment-variables-migration-issues.mdx (1)
14-16: Puntuación en la fecha
Coloca la coma tras el año:24 de abril de 2024,.docs/troubleshooting/user_issues/deployment-stuck-starting-state.mdx (1)
14-16: Fecha sin coma final
Añade la coma:27 de enero de 2025,.docs/troubleshooting/user_issues/cluster-nodepool-memory-limit-deployment-failure.mdx (1)
14-16: Fecha: falta coma
Se recomienda:13 de marzo de 2024,.docs/troubleshooting/user_issues/database-migration-data-integrity-issues.mdx (1)
14-16: Añadir coma en la línea de fecha
19 de diciembre de 2024,mejora la lectura.docs/troubleshooting/user_issues/database-restore-pod-management.mdx (1)
14-17: Fecha y metadatos siguen en inglés y con estilo inconsistente.Para mantener coherencia con la nueva categoría en español, convendría traducir y normalizar la fecha:
-**Date:** March 26, 2025 -**Category:** Dependency -**Tags:** Database, Restore, Pod, Deployment, Troubleshooting +**Fecha:** 26 de marzo de 2025 +**Categoría:** Dependencia +**Etiquetas:** Base de datos, Restore, Pod, Deployment, TroubleshootingPequeño cambio, gran uniformidad.
docs/troubleshooting/user_issues/database-migrations-execution-hooks.mdx (2)
14-17: Normaliza la cabecera a español y añade coma tras el año.-**Date:** December 19, 2024 -**Category:** Workload -**Tags:** Database, Migrations, Hooks, Executions, Deployment +**Fecha:** 19 de diciembre de 2024, +**Categoría:** Workload +**Etiquetas:** Base de datos, Migraciones, Hooks, Executions, DeploymentConserva terminología técnica, pero traduce lo evidente para evitar mezcla de idiomas.
57-63: El snippet YAML muestracommandcon espacios en blanco finales.Los espacios al final de línea rompen algunos linters de documentación. Elimina trailing whitespace para evitar warnings de CI.
docs/troubleshooting/user_issues/database-performance-optimization.mdx (1)
14-17: Cabecera en inglés—conviene localización mínima.-**Date:** January 15, 2024 -**Category:** Dependency -**Tags:** Database, Performance, Scaling, Timeout, Optimization +**Fecha:** 15 de enero de 2024, +**Categoría:** Dependencia +**Etiquetas:** Base de datos, Rendimiento, Escalado, Timeout, OptimizaciónAdemás añado coma después del año para cumplir guías de estilo.
docs/troubleshooting/user_issues/deployment-build-failures-during-updates.mdx (2)
14-17: Unifica idioma y formato de fecha.-**Date:** October 14, 2024 -**Category:** Project -**Tags:** Deployment, Build, Updates, Troubleshooting +**Fecha:** 14 de octubre de 2024, +**Categoría:** Proyecto +**Etiquetas:** Deployment, Build, Updates, TroubleshootingPequeña coherencia que suma.
62-65: “15-30 minutes” → considera rango traducido.Podrías usar “15-30 minutos” para mantener uniformidad de idioma dentro del texto.
docs/troubleshooting/user_issues/database-migration-heroku-to-aws-rds.mdx (1)
14-17: Traduce cabecera y aplica coma posterior al año.-**Date:** December 19, 2024 -**Category:** Dependency -**Tags:** Database, Migration, Heroku, AWS, RDS, PostgreSQL, DMS +**Fecha:** 19 de diciembre de 2024, +**Categoría:** Dependencia +**Etiquetas:** Base de datos, Migración, Heroku, AWS, RDS, PostgreSQL, DMSMantener consistencia idiomática facilita lectura para los usuarios hispanohablantes.
docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx (2)
14-15: Estilo de fecha: falta coma tras el añoPor coherencia con el resto del site y las guías de estilo:
19 de diciembre de 2024,→ añada la coma después del año.Also applies to: 196-196
196-196: Referencia obsoleta a “FAQ”El PR anuncia la eliminación de
FAQItem, pero el pie sigue diciendo “This FAQ...”. Sustituid por “This troubleshooting guide...” para evitar confusión.docs/troubleshooting/user_issues/dependencies-monitoring-graphs-not-displaying.mdx (2)
14-15: Añadir coma tras el año en la fechaAlso applies to: 128-128
128-128: Mensaje final aún habla de “FAQ”docs/troubleshooting/user_issues/dns-delegation-ssl-certificate-validation.mdx (2)
14-15: Coma faltante tras el añoAlso applies to: 176-176
176-176: Pie con “FAQ” obsoletodocs/troubleshooting/user_issues/cluster-upgrade-zero-downtime.mdx (2)
14-15: Añadir coma tras el año en la fechaAlso applies to: 165-165
165-165: Pie con “FAQ” obsoletodocs/troubleshooting/user_issues/cluster-automatic-shutdown-startup-issues.mdx (2)
14-15: Coma faltante tras el añoAlso applies to: 231-231
231-231: Pie con “FAQ” obsoletoYa sabéis, ¡en SleakOps arreglamos los conflictos a las piñas, pero los textos también hay que pulirlos!
docs/troubleshooting/user_issues/cluster-node-errors-web-api-unavailable.mdx (1)
14-17: Falta la coma después del año en la fecha ‒ detalle editorialLas fechas en formato “Mes Día Año” suelen llevar coma tras el año para evitar lecturas ambiguas:
January 15, 2024,…Lo mismo al pie del documento. Ajustar mantiene coherencia con el resto de docs.
Also applies to: 176-178
docs/troubleshooting/user_issues/connecting-to-cluster-with-lens.mdx (2)
10-10: Chequea la capitalización en la importación de TroubleshootingItemMismo comentario que en otros archivos: la ruta está en minúsculas; si el fichero es PascalCase fallará en entornos case-sensitive.
14-17: Añadir coma después del año en las fechas
December 19, 2024,yDecember 19, 2025,mejoran la legibilidad.Also applies to: 203-205
docs/troubleshooting/user_issues/cluster-eks-upgrade-volume-attachment-issue.mdx (2)
14-17: Coma ausente tras el año en las fechasAñadir la coma mejora consistencia editorial:
December 19, 2024,Also applies to: 163-165
20-29: “NodeGroup” aparece con mayúscula/minúscula inconsistenteEn AWS se habla de “node group” o “Nodegroup” según contexto. Mantén una sola variante para evitar confusión — en SleakOps lo solemos resolver a las piñas, pero mejor normalizar.
docs/troubleshooting/user_issues/cluster-eks-upgrade-schedule-process.mdx (3)
57-58: Frase demasiado formal: “prior to”Para un tono más directo y consistente con el resto de guías, sustituir por “antes de”:
-Usuarios recibirán notificación previa por correo electrónico +Los usuarios recibirán notificación por correo electrónico antes de cada upgrade
10-10: Capitalización del importMismo asunto: ajustar mayúsculas para evitar fallos de compilación.
14-17: Añadir coma tras el año en las fechas
February 6, 2025,y en el pie igualmente.Also applies to: 145-147
docs/troubleshooting/user_issues/dns-propagation-public-deployment.mdx (2)
10-10: Import con posible mismatch de mayúsculasAsegúrate de que el fichero
TroubleshootingItemcoincide en capitalización.
14-17: Falta la coma posterior al añoAñadir la coma tras “December 10, 2024,” y en el pie del documento.
Also applies to: 200-202
docs/troubleshooting/user_issues/cluster-prometheus-memory-issues.mdx (2)
14-17: Falta la coma tras el año en la fecha
Por estilo en español: “23 de diciembre de 2024, Categoría: Cluster”. Añade una coma tras el año para evitar la alerta del linter.
202-205: La nota final se refiere a “FAQ” en vez de “Troubleshooting”
Puede generar confusión al usuario final: este documento es una guía de troubleshooting, no un FAQ. Ajusta el texto para mantener coherencia.docs/troubleshooting/user_issues/dns-resolution-failure-mysql-redis.mdx (1)
14-16: Añade coma tras el año
“19 de diciembre de 2024, Categoría: Dependency”.docs/troubleshooting/user_issues/cluster-addons-after-migration.mdx (1)
14-16: Puntuación en la línea de fecha
Falta la coma tras “2024”.docs/troubleshooting/user_issues/cluster-connection-troubleshooting.mdx (1)
14-16: Añade coma en la fecha
“19 de diciembre de 2024, Categoría: Cluster”.docs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx (1)
218-224: Ejemplo CNAME: aclara subdominios opcionales
El bloque muestra solowwwyapi. Añade una nota indicando que se debe crear un registro por cada subdominio requerido para evitar que los lectores piensen que el listado es exhaustivo.docs/troubleshooting/user_issues/dns-migration-donweb-to-aws.mdx (2)
220-249: Añade una validación post-migración antes de cerrar la ventanaDespués del paso 3 de “Phase 3: Post-Migration” convendría un check rápido de métricas (CPU, errores 5xx, colas de correo) para detectar problemas silenciosos.
281-284: Etiqueta “FAQ” incoherente con la eliminación deFAQItemEl pie de página todavía habla de “FAQ”, pero el componente FAQItem fue retirado según el objetivo del PR. Usa “Guía de troubleshooting” o elimina la nota para evitar confusión.
docs/troubleshooting/user_issues/cluster-lens-connection-timeout.mdx (2)
100-113: Incluye la ruta de logs de Lens para depurarMuchos usuarios no saben dónde mirar los logs locales (
~/.config/Lens/logs/lens.log). Añadirlo aquí ahorra tiempo cuando “Proxy settings” no arroja pistas.
120-128:telnetytracerouteno siempre están instaladosPara reducir fricción, sugiere también
nc -vz(netcat) ocurl -svque suelen venir por defecto en macOS y contenedores Alpine.docs/troubleshooting/user_issues/api-access-troubleshooting-private-services.mdx (1)
65-70: Comandoroute -nno funciona en macOSEn macOS deberías indicar
netstat -nroroute -n get default.docs/troubleshooting/user_issues/dns-domain-delegation-cloudflare-route53.mdx (3)
1-8: Capitalización inconsistente de “Cloudflare”En varias líneas aparece “CloudFlare”. El nombre oficial es “Cloudflare”. Mantener consistencia mejora la imagen profesional.
-title: "DNS Domain Delegation Issues Between CloudFlare and Route53" +title: "DNS Domain Delegation Issues Between Cloudflare and Route53" ... -**Tags:** DNS, Route53, CloudFlare, Domain Delegation, AWS +**Tags:** DNS, Route53, Cloudflare, Domain Delegation, AWS
128-150: Aclarar que el proxy de Cloudflare puede reactivarse tras la validaciónIndica que el proxy (nube naranja) se puede volver a habilitar una vez emitido el certificado, evitando que el lector asuma que debe quedar desactivado permanentemente.
90-110: Considera mencionar DNSSEC y registros DS al migrarSi el dominio tiene DNSSEC activo en Cloudflare y se migra a Route 53 sin deshabilitarlo, la delegación fallará. Añade una nota breve sobre desactivar/actualizar DS records.
docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx (1)
235-237: Firma “FAQ” desalineada con la sección de troubleshootingLa nota final dice “This FAQ was automatically generated…”, pero el documento ya no es un FAQItem sino un TroubleshootingItem. Ajustar para evitar confusión de buscadores y usuarios.
Propuesta rápida:
-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_Documento generado automáticamente el 15 de enero de 2024 a partir de una consulta real de usuario._docs/troubleshooting/user_issues/cluster-kubernetes-upgrade-process.mdx (1)
166-168: Nota final “FAQ” no refleja el tipo de documentoReemplazar “FAQ” por “guía de troubleshooting” o similar para evitar SEO duplicado y confusión.
-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_Guía generada automáticamente el 19 de diciembre de 2024 a partir de una consulta real de usuario._
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (84)
docs/troubleshooting/user_issues/api-access-troubleshooting-private-services.mdx(1 hunks)docs/troubleshooting/user_issues/aws-cost-monitoring-and-optimization.mdx(1 hunks)docs/troubleshooting/user_issues/aws-ec2-public-ip-assignment.mdx(1 hunks)docs/troubleshooting/user_issues/aws-marketplace-login-setup-issue.mdx(1 hunks)docs/troubleshooting/user_issues/aws-waf-application-load-balancer-protection.mdx(1 hunks)docs/troubleshooting/user_issues/build-newrelic-pkg-resources-deprecation-warning.mdx(1 hunks)docs/troubleshooting/user_issues/build-pods-stuck-creation.mdx(1 hunks)docs/troubleshooting/user_issues/build-status-discrepancy-lens-vs-platform.mdx(1 hunks)docs/troubleshooting/user_issues/celery-beat-duplicate-execution.mdx(1 hunks)docs/troubleshooting/user_issues/ci-cd-build-stage-failure.mdx(1 hunks)docs/troubleshooting/user_issues/ci-cd-github-actions-not-triggering.mdx(1 hunks)docs/troubleshooting/user_issues/ci-cd-pipeline-setup-troubleshooting.mdx(1 hunks)docs/troubleshooting/user_issues/cicd-pip-to-pipx-installation.mdx(1 hunks)docs/troubleshooting/user_issues/cloudfront-existing-s3-bucket.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-addons-after-migration.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-automatic-shutdown-startup-issues.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-aws-vcpu-quota-limit.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-connection-troubleshooting.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-critical-addons-node-failure.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-eks-spot-instances-unavailable.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-eks-upgrade-schedule-process.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-eks-upgrade-volume-attachment-issue.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-kubernetes-upgrade-process.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-lens-connection-timeout.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-manual-shutdown-scheduled-feature.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-node-errors-web-api-unavailable.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-nodepool-memory-limit-deployment-failure.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-nodepool-missing-after-shutdown.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-production-check-node-scaling.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-production-mode-spot-instances.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-prometheus-memory-issues.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-understanding-ec2-instances-and-costs.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-upgrade-maintenance-scheduling.mdx(1 hunks)docs/troubleshooting/user_issues/cluster-upgrade-zero-downtime.mdx(1 hunks)docs/troubleshooting/user_issues/connecting-to-cluster-with-lens.mdx(1 hunks)docs/troubleshooting/user_issues/cors-configuration-troubleshooting.mdx(1 hunks)docs/troubleshooting/user_issues/cost-analysis-and-resource-optimization.mdx(1 hunks)docs/troubleshooting/user_issues/cronjob-timezone-deployment-behavior.mdx(1 hunks)docs/troubleshooting/user_issues/database-credentials-access.mdx(1 hunks)docs/troubleshooting/user_issues/database-maintenance-window-strategies.mdx(1 hunks)docs/troubleshooting/user_issues/database-migration-data-integrity-issues.mdx(1 hunks)docs/troubleshooting/user_issues/database-migration-environment-variables.mdx(1 hunks)docs/troubleshooting/user_issues/database-migration-heroku-to-aws-rds.mdx(1 hunks)docs/troubleshooting/user_issues/database-migrations-execution-hooks.mdx(1 hunks)docs/troubleshooting/user_issues/database-performance-optimization.mdx(1 hunks)docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx(1 hunks)docs/troubleshooting/user_issues/database-postgresql-restore-errors.mdx(1 hunks)docs/troubleshooting/user_issues/database-restore-pod-management.mdx(1 hunks)docs/troubleshooting/user_issues/database-restore-pod-procedures.mdx(1 hunks)docs/troubleshooting/user_issues/database-typeorm-ssl-connection-error.mdx(1 hunks)docs/troubleshooting/user_issues/dependencies-monitoring-graphs-not-displaying.mdx(1 hunks)docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-automatic-updates-github.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-build-failed-production.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-build-failures-during-updates.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-environment-variables-migration-issues.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-fargate-vcpu-quota-limit.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-helm-selector-immutable-error.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-image-not-updating-develop-branch.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-migration-hooks-troubleshooting.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-pending-nodepool-changes.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-redis-communication-error.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-stuck-creating-status.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-stuck-starting-state.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-stuck-state-resolution.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx(1 hunks)docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx(1 hunks)docs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx(1 hunks)docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx(1 hunks)docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx(1 hunks)docs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx(1 hunks)docs/troubleshooting/user_issues/dns-delegation-ssl-certificate-validation.mdx(1 hunks)docs/troubleshooting/user_issues/dns-domain-delegation-cloudflare-route53.mdx(1 hunks)docs/troubleshooting/user_issues/dns-migration-donweb-to-aws.mdx(1 hunks)docs/troubleshooting/user_issues/dns-propagation-public-deployment.mdx(1 hunks)docs/troubleshooting/user_issues/dns-resolution-failure-mysql-redis.mdx(1 hunks)docs/troubleshooting/user_issues/docker-build-cache-issues.mdx(1 hunks)docs/troubleshooting/user_issues/docker-build-cache-no-cache-option.mdx(1 hunks)docs/troubleshooting/user_issues/docker-build-environment-variables.mdx(1 hunks)docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx(1 hunks)
🧠 Learnings (13)
docs/troubleshooting/user_issues/deployment-stuck-state-resolution.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-image-not-updating-develop-branch.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/docker-build-environment-variables.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-build-failed-production.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/docker-build-cache-issues.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
🪛 LanguageTool
docs/troubleshooting/user_issues/deployment-stuck-state-resolution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Pending State Date: December 28, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...counter a stuck deployment, contact the SleakOps support team immediately. The resolutio...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~124-~124: Ensure spelling is correct
Context: ...n to escalate to support"> Escalate to SleakOps support when: **Immediate Escalation R...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/aws-ec2-public-ip-assignment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic IPv4 Address Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...nstance within a production VPC through SleakOps but the instance doesn't receive a publ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...kOps"> If you're managing this through SleakOps, you can configure public IP assignment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~171-~171: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/ci-cd-github-actions-not-triggering.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Not Triggering Date: January 15, 2024 Category: Project Tags: Git...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...with continuous integration pipeline in SleakOps where GitHub Actions workflows stop tri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...ons with YAML configuration - Platform: SleakOps integration Error Conditions: - Pipeline work...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sources Warning Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~134-~134: Consider using a different verb for a more formal wording.
Context: ...only suppresses the warning but doesn't fix the underlying issue. </Troubleshootin...
(FIX_RESOLVE)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-propagation-public-deployment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic Deployments Date: December 10, 2024 Category: Project Tags: DNS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...blic deployment created successfully in SleakOps - Domain URL is generated (e.g., https://s...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...when accessing the URL - Application is not accessible via the public domain **Relevant Confi...
(NOT_ABLE_PREMIUM)
[grammar] ~179-~179: Ensure spelling is correct
Context: ...y the domain is correctly configured in SleakOps - Ensure no typos in the domain name - Che...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~191-~191: Ensure spelling is correct
Context: ...eyond normal propagation times, contact SleakOps support with: - Deployment name and pr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-helm-selector-immutable-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Immutable Error Date: December 19, 2024 Category: Workload Tags: He...
(MISSING_COMMA_AFTER_YEAR)
[style] ~181-~181: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-prometheus-memory-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...using Pod Hangs Date: December 23, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~204-~204: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/docker-build-cache-no-cache-option.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Build Arguments Date: February 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-environment-variables-migration-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...le After Migration Date: April 24, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-migration-hooks-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ployment Issues Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~227-~227: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-delegation-ssl-certificate-validation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...idation Issues Date: September 10, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-critical-addons-node-failure.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...re in Production Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-node-errors-web-api-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e to Node Errors Date: January 15, 2024 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps Kubernetes cluster - Affected services:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-migration-data-integrity-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ntegrity Issues Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~256-~256: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-nodepool-missing-after-shutdown.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...luster Shutdown Date: February 20, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~53-~53: Ensure spelling is correct
Context: ...pool configuration** once restored The SleakOps team can manually restore your nodepool...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ...n the future: 1. Wait for the fix: SleakOps is working on a permanent solution 2. *...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...ary="When to contact support"> Contact SleakOps support immediately if: - Nodepools ar...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~143-~143: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 20, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-typeorm-ssl-connection-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Error with RDS Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/connecting-to-cluster-with-lens.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...r with Lens IDE Date: December 19, 2024 Category: Cluster Tags: Len...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ntext:** Users need to connect to their SleakOps Kubernetes cluster from their local dev...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ubernetes clusters. It's recommended by SleakOps because it offers: - **Visual cluster ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...d get credentials"> To connect to your SleakOps cluster, you need to authenticate and o...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...the necessary credentials: 1. Access SleakOps Dashboard: Log into your SleakOps acc...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...ess SleakOps Dashboard**: Log into your SleakOps account 2. Navigate to Cluster: Go to your specif...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~205-~205: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...hne Applications Date: January 21, 2025 Category: Workload Tags: Do...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-restore-pod-management.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ore Pod Management Date: March 26, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~232-~232: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 26, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/build-pods-stuck-creation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in Creation State Date: March 22, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps - Build system: Kubernetes-based builds...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~164-~164: Ensure spelling is correct
Context: ...ary="When to contact support"> Contact SleakOps support if: - Builds remain stuck afte...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~183-~183: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 22, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-image-not-updating-develop-branch.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ges After Merge Date: December 19, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cronjob-timezone-deployment-behavior.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...loyment Behavior Date: October 24, 2024 Category: Workload Tags: Cr...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 24, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-production-mode-spot-instances.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Instance Types Date: December 19, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...omain Providers Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not w...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...egation appears correctly configured in Route53 - Domain registrar (DonWeb) reports del...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~36-~36: Ensure spelling is correct
Context: ...AWS Certificate Manager (ACM) - Target: SleakOps deployment with Load Balancer **Error ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~136-~136: Ensure spelling is correct
Context: ...NAME record for domain validation is in Route53 - The validation record should be: `...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~155-~155: Ensure spelling is correct
Context: ...y="SleakOps Domain Configuration"> For SleakOps deployments, ensure proper domain confi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...ps Domain Settings:** - Update your SleakOps project configuration to use the custom...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~335-~335: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-performance-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tion and Scaling Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-aws-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ror with Karpenter Date: April 24, 2024 Category: Cluster Tags: AWS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~200-~200: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/ci-cd-pipeline-setup-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ing on Branch Push Date: March 14, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[style] ~189-~189: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-nodepool-memory-limit-deployment-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pool Memory Limits Date: March 13, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~225-~225: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 13, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/aws-marketplace-login-setup-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... and Setup Issue Date: January 15, 2024 Category: User Tags: AWS Ma...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...iption Context: User subscribed to SleakOps through AWS Marketplace but encounters ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ... subscribe through AWS 2. Redirect to SleakOps: AWS redirects you to our platform wi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~91-~91: Ensure spelling is correct
Context: ...AWS Marketplace** 3. Navigate to your SleakOps subscription 4. Click "Setup Product" If this works, ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~102-~102: Ensure spelling is correct
Context: ...ally link your accounts: 1. Create a SleakOps account (if you don't have one): ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...th: - Your AWS account ID - Your SleakOps account email - Your AWS Marketplace...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~135-~135: Ensure spelling is correct
Context: ...k:** - Disable ad blockers for AWS and SleakOps domains - Allow third-party cookies temporarily - ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~164-~164: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...er Nodepool Changes Date: March 5, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ... 1. Navigate to your service in the SleakOps dashboard 2. Click "Edit" on the affected deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~131-~131: Ensure spelling is correct
Context: ...odepool changes**: Coordinate with your SleakOps team before major changes 2. **Update d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on March 5, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-lens-connection-timeout.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Kubernetes Cluster Date: April 29, 2024 Category: User Tags: Lens, ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-connection-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...nnection Issues Date: December 19, 2024 Category: Cluster Tags: Con...
(MISSING_COMMA_AFTER_YEAR)
[style] ~230-~230: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/aws-waf-application-load-balancer-protection.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ncer Protection Date: December 19, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Load Balancer: Application Loa...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~46-~46: Ensure spelling is correct
Context: ...rom common web exploits and bots. While SleakOps doesn't have native WAF integration yet...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[uncategorized] ~142-~142: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ority: 3 Action: Block **2. Custom Rate Limiting Rule:** yaml Rule Name: RateLimitin...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~361-~361: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Database Import Date: December 20, 2024 Category: Project Tags: Dja...
(MISSING_COMMA_AFTER_YEAR)
[style] ~184-~184: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 20, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/api-access-troubleshooting-private-services.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Access Issues Date: December 19, 2024 Category: User Tags: API, V...
(MISSING_COMMA_AFTER_YEAR)
[style] ~254-~254: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-eks-upgrade-volume-attachment-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Orphaned Volume Date: December 19, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...mon issue when volumes are removed from SleakOps configuration but the underlying AWS EB...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~60-~60: Consider using a different verb for a more formal wording.
Context: ...ow to resolve the upgrade failure"> To fix the upgrade issue: 1. **Identify the p...
(FIX_RESOLVE)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...ume removal**: When removing volumes in SleakOps, ensure they are properly detached: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/database-migration-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Configuration Date: December 11, 2024 Category: Project Tags: Dat...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...LLOWED_ORIGINS` - Environment variables not accessible to migration processes **Relevant Conf...
(NOT_ABLE_PREMIUM)
[style] ~455-~455: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ry Optimization Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/celery-beat-duplicate-execution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Task Execution Date: December 23, 2024 Category: Workload Tags: Ce...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...egrated within backend pods - Platform: SleakOps Kubernetes environment - Workload type:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~41-~41: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...s for scheduled tasks - Tasks execute N times where N = number of backend pod replicas ## ...
(WHEN_WHERE)
[grammar] ~81-~81: Ensure spelling is correct
Context: ... Step 2: Create CronJob Executions in SleakOps For each Celery Beat task, create a ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...ob execution: 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~217-~217: Ensure spelling is correct
Context: ...tly: Step 1: Check CronJob Status in SleakOps 1. Go to your project's **Executions...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~287-~287: Ensure spelling is correct
Context: ...All CronJobs are created and visible in SleakOps - [ ] CronJob schedules match the original...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~367-~367: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-domain-delegation-cloudflare-route53.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 21, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...on: Requires proper domain delegation - SleakOps validation: Checks delegation once duri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...anding SleakOps DNS Management"> How SleakOps manages DNS: 1. **Centralized Manage...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~50-~50: Ensure spelling is correct
Context: ... DNS:** 1. Centralized Management: SleakOps centralizes all DNS management in your ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ce Management**: Services deployed with SleakOps manage their DNS records automatically ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...ords:** - All DNS records generated by SleakOps are visible in the platform - Records i...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~59-~59: Ensure spelling is correct
Context: ...- Records are automatically managed for SleakOps services **For proper functionality, domains must b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ... Route53 nameservers 2. Subdomains of SleakOps-managed domains: Created as subdomain...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...*: Delegate only specific subdomains to Route53 # In CloudFlare, create NS records for subdomains: app.yourdomain.com NS ns-xxx.awsdns-xx.com app.yourdomain.com NS ns-xxx.awsdns-xx.co.uk app.yourdomain.com NS ns-xxx.awsdns-xx.net app.yourdomain.com NS ns-xxx.awsdns-xx.org 2. Use SleakOps subdomains: Create all Sl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...S ns-xxx.awsdns-xx.org ``` 2. Use SleakOps subdomains: Create all SleakOps servi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...Use SleakOps subdomains: Create all SleakOps services under a dedicated subdomain ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/cluster-upgrade-zero-downtime.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...h Zero Downtime Date: February 19, 2025 Category: Cluster Tags: Upg...
(MISSING_COMMA_AFTER_YEAR)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 19, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cost-analysis-and-resource-optimization.mdx
[grammar] ~20-~20: Ensure spelling is correct
Context: ...t Analysis and Resource Optimization in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ion in SleakOps Date: December 19, 2024 Category: General Tags: Cos...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~39-~39: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with AWS backend - Resources: WebServic...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~179-~179: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...yNotReady Error Date: December 26, 2024 Category: Workload Tags: Dj...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider changing the order of words to improve your wording.
Context: ... execute properly - Application appears to not be fully initialized when Celery tasks ...
(TO_NOT_VB)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ery -A (App) call function` - Platform: SleakOps Error Conditions: - Error occurs ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~143-~143: Ensure spelling is correct
Context: ...ps: {settings.INSTALLED_APPS}") ``` In SleakOps, ensure your environment variables are ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ..."SleakOps specific configuration"> For SleakOps deployments, ensure your worker configu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~212-~212: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 26, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Timeout Issues Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...: Restart the affected service** 1. In SleakOps dashboard, go to your project 2. Find t...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/docker-build-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...bles Not Available Date: March 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~20-~20: Consider using “inaccessible” to avoid wordiness.
Context: ...defined in SleakOps Docker settings are not accessible during the build process, specifically ...
(NOT_ABLE_PREMIUM)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ockerfile"> Environment variables from SleakOps settings are only available at runtime,...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...igure build arguments in SleakOps"> In SleakOps, you need to configure build arguments ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~194-~194: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-migration-heroku-to-aws-rds.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...roku to AWS RDS Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~442-~442: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-migration-donweb-to-aws.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...om DonWeb to AWS Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[style] ~196-~196: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-eks-spot-instances-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...degroup Creation Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~210-~210: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-automatic-updates-github.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pdates from GitHub Date: August 2, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ory are automatically deployed to their SleakOps environment during testing phases. **O...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...- Source: GitHub repository - Platform: SleakOps - Environment: Development/Testing - Do...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...nnection:** - Go to your Project in SleakOps - Navigate to Settings → *Repository...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~87-~87: Ensure spelling is correct
Context: ... the deployment workflow"> The typical SleakOps deployment workflow: ```mermaid graph ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~201-~201: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on August 2, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-production-check-node-scaling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...esource Changes Date: November 20, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...enabled the "Production" check on their SleakOps cluster and configured an on-demand nod...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...When you enable the Production check in SleakOps, the following changes are automaticall...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~52-~52: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...y: Node Infrastructure Changes: - Adds an additional node to the core node group in a different a...
(ADD_AN_ADDITIONAL)
[grammar] ~72-~72: Ensure spelling is correct
Context: ...anges in version 1.7.0"> Starting with SleakOps version 1.7.0, the platform implements ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ods Not Terminating Date: June 10, 2024 Category: Workload Tags: De...
(MISSING_COMMA_AFTER_YEAR)
[style] ~604-~604: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-upgrade-maintenance-scheduling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ance Scheduling Date: December 19, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~59-~59: ‘Advance Notice’ might be wordy. Consider a shorter alternative.
Context: ...issues ### Communication Protocol - Advance Notice: Notify clients at least 48-72 hours ...
(EN_WORDINESS_PREMIUM_ADVANCE_NOTICE)
[style] ~247-~247: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-maintenance-window-strategies.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...indow Strategies Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...ication-Level Maintenance Mode"> Since SleakOps doesn't currently provide a built-in ma...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~524-~524: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-resolution-failure-mysql-redis.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dis Connections Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-restore-pod-procedures.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...in Pod Environment Date: March 21, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/build-status-discrepancy-lens-vs-platform.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...latform and Lens Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-stuck-starting-state.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Starting State Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~87-~87: Ensure spelling is correct
Context: ...ld arguments are properly configured in SleakOps project settings. </TroubleshootingIte...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-credentials-access.mdx
[grammar] ~12-~12: Ensure spelling is correct
Context: ...tem"; # Database Credentials Access in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ess in SleakOps Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~58-~58: Ensure spelling is correct
Context: ...roup"> To view database credentials in SleakOps: 1. Navigate to your project 2. **G...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...VarGroup** 4. View the credentials: SleakOps fetches the secret from the cluster and...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-stuck-creating-status.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Creating Status Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ranch and triggers a deployment through SleakOps. The build process completes successfull...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...nt type: deploy_build_dev - Platform: SleakOps - Build status: Successful - Deployment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~98-~98: Ensure spelling is correct
Context: ... to contact SleakOps support"> Contact SleakOps support if: 1. **Deployment stuck for ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~181-~181: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deployment status ...
(DEEP_PROFOUND)
[grammar] ~469-~469: Ensure spelling is correct
Context: ...ific solutions"> Solutions specific to SleakOps platform deployment issues: 1. **Sleak...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~473-~473: Ensure spelling is correct
Context: ...t state management**: - Deployments in SleakOps may get stuck due to platform state man...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~475-~475: Ensure spelling is correct
Context: ...ates - Sometimes manual intervention by SleakOps support is required to reset state 2. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~597-~597: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...atabase Migrations Date: April 25, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~71-~71: Ensure spelling is correct
Context: ...ncrease pre-deploy timeout limits"> In SleakOps, you can configure longer timeout limit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/aws-cost-monitoring-and-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...and Optimization Date: January 16, 2025 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[uncategorized] ~58-~58: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...Deployment timing*: Partial month vs. full month billing - Multiple accounts: Costs ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 16, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/build-newrelic-pkg-resources-deprecation-warning.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Deprecation Warning Date: June 10, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ikely 81 or higher - Build environment: SleakOps managed containers **Error Conditions:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~192-~192: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/ci-cd-build-stage-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ld Stage Failure Date: October 10, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...correctly configured: 1. Access your SleakOps project dashboard 2. **Navigate to th...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~66-~66: Ensure spelling is correct
Context: ... CI/CD file was copied correctly** from SleakOps Common issues to check: ```yaml # Che...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...rigger a fresh build: Option 1: From SleakOps Dashboard 1. Go to your project in SleakOps 2....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...s Dashboard** 1. Go to your project in SleakOps 2. Navigate to the Deployments section ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~179-~179: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cicd-pip-to-pipx-installation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tallation Method Date: October 15, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ows fail when attempting to install the SleakOps CLI tool using the traditional `pip ins...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/cloudfront-existing-s3-bucket.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sting S3 Bucket Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~170-~170: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-addons-after-migration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... After Migration Date: October 15, 2024 Category: Cluster Tags: Mig...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...Context:** After a cluster migration in SleakOps, users cannot locate previously install...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with new interface - Affected addons: L...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... SleakOps with new interface - Affected addons: Loki, Grafana, and other monitoring to...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...available"> During cluster migrations, SleakOps temporarily deactivates addons to ensur...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...ss**: - Log into Grafana using your SleakOps credentials - Verify dashboards are displaying data ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-automatic-shutdown-startup-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Startup Issues Date: February 14, 2025 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...S ## Problem Description Context: SleakOps clusters configured with automatic shut...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/cluster-eks-upgrade-schedule-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dule and Process Date: February 6, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~40-~40: Ensure spelling is correct
Context: ...cations - Need for coordination between SleakOps team and users ## Detailed Solution <...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~57-~57: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...email - Specific dates are communicated prior to each upgrade <...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[grammar] ~71-~71: Ensure spelling is correct
Context: ... On-Demand Upgrades: In some cases, SleakOps provides a workflow within the platform...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~86-~86: Ensure spelling is correct
Context: ... - Custom configurations not managed by SleakOps could be affected - Users should avoid ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...ions - Report any issues immediately to SleakOps support Before Upgrades: 1. **Review Applicat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...ompletion 3. Report Issues: Contact SleakOps immediately if problems arise **After ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on February 6, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-kubernetes-upgrade-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Upgrade Process Date: December 19, 2024 Category: Cluster Tags: Kub...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ication in the Cluster section of their SleakOps dashboard and need guidance on how to p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps managed Kubernetes cluster - Environmen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...t** on the upgrade notification in your SleakOps dashboard 2. The system will automatically begin the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ocess is fully automated and managed by SleakOps. <Troubleshooti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...e upgrades Process order: 1. Core SleakOps nodes are upgraded one by one (rolling ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~83-~83: Ensure spelling is correct
Context: ...tions** in your cluster (not managed by SleakOps) - Check the Kubernetes changelog for depre...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~89-~89: Ensure spelling is correct
Context: ...pecial database preparations needed for SleakOps managed upgrades - Ensure database conn...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...r usual monitoring tools 2. Check the SleakOps dashboard for upgrade progress 3. **W...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~132-~132: Ensure spelling is correct
Context: ...r logs If issues occur: - Contact SleakOps support immediately - Provide specific ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-manual-shutdown-scheduled-feature.mdx
[style] ~12-~12: The double modal “Requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...m"; # Cluster Manual Shutdown Requires Scheduled Feature Date: December 12, 2024 ...
(NEEDS_FIXED)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...heduled Feature Date: December 12, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~89-~89: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...y stop the cluster 4. Start the cluster manually when needed 5. No predefined schedule r...
(ADVERB_REPETITION_PREMIUM)
[style] ~135-~135: The double modal “requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...Behavior:** - Manual shutdown requires Scheduled Shutdown feature enabled - Background m...
(NEEDS_FIXED)
[style] ~167-~167: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 12, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-understanding-ec2-instances-and-costs.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in EKS Clusters Date: January 29, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 29, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cors-configuration-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Troubleshooting Date: December 19, 2024 Category: Workload Tags: CO...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...:** - Frontend and backend deployed on SleakOps - CORS configuration present in backend...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ..., meaning: - Infrastructure Level: SleakOps load balancers and ingress controllers ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~208-~208: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 25, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-migrations-execution-hooks.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Execution Hooks Date: December 19, 2024 Category: Workload Tags: Da...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ... as part of their deployment process in SleakOps, specifically for .NET applications usi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~82-~82: Ensure spelling is correct
Context: ... Execution:** 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~162-~162: Ensure spelling is correct
Context: ... 1. Use pre-upgrade hooks (default SleakOps behavior) for automatic migrations 2. *...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-postgresql-restore-errors.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Restore Errors Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~161-~161: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dependencies-monitoring-graphs-not-displaying.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Not Displaying Date: January 22, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~128-~128: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 22, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-build-failed-production.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...g Loading Issues Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-build-failures-during-updates.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Platform Updates Date: October 14, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ild process fails temporarily while the SleakOps platform undergoes maintenance or updat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...rm communications**: - Subscribe to SleakOps status updates - Check email notific...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~155-~155: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-fargate-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ring Deployment Date: February 13, 2025 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...Users experience deployment failures in SleakOps when using AWS Fargate as the deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...eployment mode: AWS Fargate - Platform: SleakOps - Service: Container deployments - Reso...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~189-~189: Ensure spelling is correct
Context: ...ed-count 0 ``` 3. Coordinate with SleakOps support: - Report the specific res...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-pending-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Nodepool Changes Date: January 23, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...aking nodepool configuration changes in SleakOps, deployments remain in a pending state ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-redis-communication-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...munication Error Date: January 15, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~62-~62: Ensure spelling is correct
Context: ...you encounter this issue: 1. Contact SleakOps Support: This is typically an infrast...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~158-~158: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...gth Limit Error Date: February 13, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...to deploy a project with a long name in SleakOps. The automatically generated Kubernetes ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~174-~174: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ces Not Creating Date: January 15, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Domain: teams.simplee.cl - Platform: SleakOps - Deployment type: Teams instances **E...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...en to escalate the issue"> Escalate to SleakOps support if: 1. **Infrastructure Issues...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~282-~282: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deep cluster analy...
(DEEP_PROFOUND)
[style] ~453-~453: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/docker-build-cache-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...es in Production Date: January 15, 2024 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with Docker builds - Environment: Produ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~121-~121: Ensure spelling is correct
Context: ...s** - Review the deployment logs in SleakOps - Look for "Using cache" messages that mig...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
🪛 Gitleaks (8.27.2)
docs/troubleshooting/user_issues/deployment-build-failed-production.mdx
74-74: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
(curl-auth-header)
🧰 Additional context used
🧠 Learnings (13)
docs/troubleshooting/user_issues/deployment-stuck-state-resolution.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-image-not-updating-develop-branch.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/docker-build-environment-variables.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-build-failed-production.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
docs/troubleshooting/user_issues/docker-build-cache-issues.mdx (1)
Learnt from: agustinoli
PR: #85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento docs/project/dependency/index.mdx, la numeración de los pasos es correcta y no necesita cambios.
🪛 LanguageTool
docs/troubleshooting/user_issues/deployment-stuck-state-resolution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Pending State Date: December 28, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...counter a stuck deployment, contact the SleakOps support team immediately. The resolutio...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~124-~124: Ensure spelling is correct
Context: ...n to escalate to support"> Escalate to SleakOps support when: **Immediate Escalation R...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/aws-ec2-public-ip-assignment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic IPv4 Address Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...nstance within a production VPC through SleakOps but the instance doesn't receive a publ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...kOps"> If you're managing this through SleakOps, you can configure public IP assignment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~171-~171: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/ci-cd-github-actions-not-triggering.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Not Triggering Date: January 15, 2024 Category: Project Tags: Git...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...with continuous integration pipeline in SleakOps where GitHub Actions workflows stop tri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...ons with YAML configuration - Platform: SleakOps integration Error Conditions: - Pipeline work...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-newrelic-pkg-resources-warning.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sources Warning Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~134-~134: Consider using a different verb for a more formal wording.
Context: ...only suppresses the warning but doesn't fix the underlying issue. </Troubleshootin...
(FIX_RESOLVE)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-propagation-public-deployment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic Deployments Date: December 10, 2024 Category: Project Tags: DNS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...blic deployment created successfully in SleakOps - Domain URL is generated (e.g., https://s...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...when accessing the URL - Application is not accessible via the public domain **Relevant Confi...
(NOT_ABLE_PREMIUM)
[grammar] ~179-~179: Ensure spelling is correct
Context: ...y the domain is correctly configured in SleakOps - Ensure no typos in the domain name - Che...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~191-~191: Ensure spelling is correct
Context: ...eyond normal propagation times, contact SleakOps support with: - Deployment name and pr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-helm-selector-immutable-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Immutable Error Date: December 19, 2024 Category: Workload Tags: He...
(MISSING_COMMA_AFTER_YEAR)
[style] ~181-~181: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-prometheus-memory-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...using Pod Hangs Date: December 23, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~204-~204: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/docker-build-cache-no-cache-option.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Build Arguments Date: February 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-environment-variables-migration-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...le After Migration Date: April 24, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-migration-hooks-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ployment Issues Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~227-~227: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-delegation-ssl-certificate-validation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...idation Issues Date: September 10, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-critical-addons-node-failure.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...re in Production Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-node-errors-web-api-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e to Node Errors Date: January 15, 2024 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps Kubernetes cluster - Affected services:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-migration-data-integrity-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ntegrity Issues Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~256-~256: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-nodepool-missing-after-shutdown.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...luster Shutdown Date: February 20, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~53-~53: Ensure spelling is correct
Context: ...pool configuration** once restored The SleakOps team can manually restore your nodepool...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ...n the future: 1. Wait for the fix: SleakOps is working on a permanent solution 2. *...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...ary="When to contact support"> Contact SleakOps support immediately if: - Nodepools ar...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~143-~143: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 20, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-typeorm-ssl-connection-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Error with RDS Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/connecting-to-cluster-with-lens.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...r with Lens IDE Date: December 19, 2024 Category: Cluster Tags: Len...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ntext:** Users need to connect to their SleakOps Kubernetes cluster from their local dev...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ubernetes clusters. It's recommended by SleakOps because it offers: - **Visual cluster ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...d get credentials"> To connect to your SleakOps cluster, you need to authenticate and o...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...the necessary credentials: 1. Access SleakOps Dashboard: Log into your SleakOps acc...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...ess SleakOps Dashboard**: Log into your SleakOps account 2. Navigate to Cluster: Go to your specif...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~205-~205: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...hne Applications Date: January 21, 2025 Category: Workload Tags: Do...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-restore-pod-management.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ore Pod Management Date: March 26, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~232-~232: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 26, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/build-pods-stuck-creation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in Creation State Date: March 22, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps - Build system: Kubernetes-based builds...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~164-~164: Ensure spelling is correct
Context: ...ary="When to contact support"> Contact SleakOps support if: - Builds remain stuck afte...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~183-~183: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 22, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-image-not-updating-develop-branch.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ges After Merge Date: December 19, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cronjob-timezone-deployment-behavior.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...loyment Behavior Date: October 24, 2024 Category: Workload Tags: Cr...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 24, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-production-mode-spot-instances.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Instance Types Date: December 19, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-delegation-route53-domain-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...omain Providers Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not w...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...egation appears correctly configured in Route53 - Domain registrar (DonWeb) reports del...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~36-~36: Ensure spelling is correct
Context: ...AWS Certificate Manager (ACM) - Target: SleakOps deployment with Load Balancer **Error ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~136-~136: Ensure spelling is correct
Context: ...NAME record for domain validation is in Route53 - The validation record should be: `...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~155-~155: Ensure spelling is correct
Context: ...y="SleakOps Domain Configuration"> For SleakOps deployments, ensure proper domain confi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...ps Domain Settings:** - Update your SleakOps project configuration to use the custom...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~335-~335: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-performance-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tion and Scaling Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-aws-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ror with Karpenter Date: April 24, 2024 Category: Cluster Tags: AWS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~200-~200: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/ci-cd-pipeline-setup-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ing on Branch Push Date: March 14, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[style] ~189-~189: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-nodepool-memory-limit-deployment-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pool Memory Limits Date: March 13, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~225-~225: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 13, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/aws-marketplace-login-setup-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... and Setup Issue Date: January 15, 2024 Category: User Tags: AWS Ma...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...iption Context: User subscribed to SleakOps through AWS Marketplace but encounters ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ... subscribe through AWS 2. Redirect to SleakOps: AWS redirects you to our platform wi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~91-~91: Ensure spelling is correct
Context: ...AWS Marketplace** 3. Navigate to your SleakOps subscription 4. Click "Setup Product" If this works, ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~102-~102: Ensure spelling is correct
Context: ...ally link your accounts: 1. Create a SleakOps account (if you don't have one): ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...th: - Your AWS account ID - Your SleakOps account email - Your AWS Marketplace...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~135-~135: Ensure spelling is correct
Context: ...k:** - Disable ad blockers for AWS and SleakOps domains - Allow third-party cookies temporarily - ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~164-~164: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...er Nodepool Changes Date: March 5, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ... 1. Navigate to your service in the SleakOps dashboard 2. Click "Edit" on the affected deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~131-~131: Ensure spelling is correct
Context: ...odepool changes**: Coordinate with your SleakOps team before major changes 2. **Update d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on March 5, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-lens-connection-timeout.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Kubernetes Cluster Date: April 29, 2024 Category: User Tags: Lens, ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-connection-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...nnection Issues Date: December 19, 2024 Category: Cluster Tags: Con...
(MISSING_COMMA_AFTER_YEAR)
[style] ~230-~230: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/aws-waf-application-load-balancer-protection.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ncer Protection Date: December 19, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Load Balancer: Application Loa...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~46-~46: Ensure spelling is correct
Context: ...rom common web exploits and bots. While SleakOps doesn't have native WAF integration yet...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[uncategorized] ~142-~142: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ority: 3 Action: Block **2. Custom Rate Limiting Rule:** yaml Rule Name: RateLimitin...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~361-~361: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/django-migration-conflicts-database-import.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Database Import Date: December 20, 2024 Category: Project Tags: Dja...
(MISSING_COMMA_AFTER_YEAR)
[style] ~184-~184: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 20, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/api-access-troubleshooting-private-services.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Access Issues Date: December 19, 2024 Category: User Tags: API, V...
(MISSING_COMMA_AFTER_YEAR)
[style] ~254-~254: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-eks-upgrade-volume-attachment-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Orphaned Volume Date: December 19, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...mon issue when volumes are removed from SleakOps configuration but the underlying AWS EB...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~60-~60: Consider using a different verb for a more formal wording.
Context: ...ow to resolve the upgrade failure"> To fix the upgrade issue: 1. **Identify the p...
(FIX_RESOLVE)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...ume removal**: When removing volumes in SleakOps, ensure they are properly detached: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/database-migration-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Configuration Date: December 11, 2024 Category: Project Tags: Dat...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...LLOWED_ORIGINS` - Environment variables not accessible to migration processes **Relevant Conf...
(NOT_ABLE_PREMIUM)
[style] ~455-~455: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-performance-sql-query-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ry Optimization Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/celery-beat-duplicate-execution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Task Execution Date: December 23, 2024 Category: Workload Tags: Ce...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...egrated within backend pods - Platform: SleakOps Kubernetes environment - Workload type:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~41-~41: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...s for scheduled tasks - Tasks execute N times where N = number of backend pod replicas ## ...
(WHEN_WHERE)
[grammar] ~81-~81: Ensure spelling is correct
Context: ... Step 2: Create CronJob Executions in SleakOps For each Celery Beat task, create a ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...ob execution: 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~217-~217: Ensure spelling is correct
Context: ...tly: Step 1: Check CronJob Status in SleakOps 1. Go to your project's **Executions...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~287-~287: Ensure spelling is correct
Context: ...All CronJobs are created and visible in SleakOps - [ ] CronJob schedules match the original...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~367-~367: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-domain-delegation-cloudflare-route53.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 21, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...on: Requires proper domain delegation - SleakOps validation: Checks delegation once duri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...anding SleakOps DNS Management"> How SleakOps manages DNS: 1. **Centralized Manage...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~50-~50: Ensure spelling is correct
Context: ... DNS:** 1. Centralized Management: SleakOps centralizes all DNS management in your ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ce Management**: Services deployed with SleakOps manage their DNS records automatically ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...ords:** - All DNS records generated by SleakOps are visible in the platform - Records i...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~59-~59: Ensure spelling is correct
Context: ...- Records are automatically managed for SleakOps services **For proper functionality, domains must b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ... Route53 nameservers 2. Subdomains of SleakOps-managed domains: Created as subdomain...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...*: Delegate only specific subdomains to Route53 # In CloudFlare, create NS records for subdomains: app.yourdomain.com NS ns-xxx.awsdns-xx.com app.yourdomain.com NS ns-xxx.awsdns-xx.co.uk app.yourdomain.com NS ns-xxx.awsdns-xx.net app.yourdomain.com NS ns-xxx.awsdns-xx.org 2. Use SleakOps subdomains: Create all Sl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...S ns-xxx.awsdns-xx.org ``` 2. Use SleakOps subdomains: Create all SleakOps servi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...Use SleakOps subdomains: Create all SleakOps services under a dedicated subdomain ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/cluster-upgrade-zero-downtime.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...h Zero Downtime Date: February 19, 2025 Category: Cluster Tags: Upg...
(MISSING_COMMA_AFTER_YEAR)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 19, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cost-analysis-and-resource-optimization.mdx
[grammar] ~20-~20: Ensure spelling is correct
Context: ...t Analysis and Resource Optimization in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ion in SleakOps Date: December 19, 2024 Category: General Tags: Cos...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~39-~39: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with AWS backend - Resources: WebServic...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~179-~179: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...yNotReady Error Date: December 26, 2024 Category: Workload Tags: Dj...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider changing the order of words to improve your wording.
Context: ... execute properly - Application appears to not be fully initialized when Celery tasks ...
(TO_NOT_VB)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ery -A (App) call function` - Platform: SleakOps Error Conditions: - Error occurs ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~143-~143: Ensure spelling is correct
Context: ...ps: {settings.INSTALLED_APPS}") ``` In SleakOps, ensure your environment variables are ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ..."SleakOps specific configuration"> For SleakOps deployments, ensure your worker configu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~212-~212: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 26, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Timeout Issues Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...: Restart the affected service** 1. In SleakOps dashboard, go to your project 2. Find t...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/docker-build-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...bles Not Available Date: March 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~20-~20: Consider using “inaccessible” to avoid wordiness.
Context: ...defined in SleakOps Docker settings are not accessible during the build process, specifically ...
(NOT_ABLE_PREMIUM)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ockerfile"> Environment variables from SleakOps settings are only available at runtime,...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...igure build arguments in SleakOps"> In SleakOps, you need to configure build arguments ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~194-~194: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-migration-heroku-to-aws-rds.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...roku to AWS RDS Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~442-~442: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-migration-donweb-to-aws.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...om DonWeb to AWS Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[style] ~196-~196: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-eks-spot-instances-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...degroup Creation Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~210-~210: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-automatic-updates-github.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pdates from GitHub Date: August 2, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ory are automatically deployed to their SleakOps environment during testing phases. **O...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...- Source: GitHub repository - Platform: SleakOps - Environment: Development/Testing - Do...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...nnection:** - Go to your Project in SleakOps - Navigate to Settings → *Repository...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~87-~87: Ensure spelling is correct
Context: ... the deployment workflow"> The typical SleakOps deployment workflow: ```mermaid graph ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~201-~201: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on August 2, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-production-check-node-scaling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...esource Changes Date: November 20, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...enabled the "Production" check on their SleakOps cluster and configured an on-demand nod...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...When you enable the Production check in SleakOps, the following changes are automaticall...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~52-~52: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...y: Node Infrastructure Changes: - Adds an additional node to the core node group in a different a...
(ADD_AN_ADDITIONAL)
[grammar] ~72-~72: Ensure spelling is correct
Context: ...anges in version 1.7.0"> Starting with SleakOps version 1.7.0, the platform implements ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/deployment-old-pods-not-terminating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ods Not Terminating Date: June 10, 2024 Category: Workload Tags: De...
(MISSING_COMMA_AFTER_YEAR)
[style] ~604-~604: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-upgrade-maintenance-scheduling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ance Scheduling Date: December 19, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~59-~59: ‘Advance Notice’ might be wordy. Consider a shorter alternative.
Context: ...issues ### Communication Protocol - Advance Notice: Notify clients at least 48-72 hours ...
(EN_WORDINESS_PREMIUM_ADVANCE_NOTICE)
[style] ~247-~247: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-maintenance-window-strategies.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...indow Strategies Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...ication-Level Maintenance Mode"> Since SleakOps doesn't currently provide a built-in ma...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~524-~524: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dns-resolution-failure-mysql-redis.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dis Connections Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-restore-pod-procedures.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...in Pod Environment Date: March 21, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/build-status-discrepancy-lens-vs-platform.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...latform and Lens Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-stuck-starting-state.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Starting State Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~87-~87: Ensure spelling is correct
Context: ...ld arguments are properly configured in SleakOps project settings. </TroubleshootingIte...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-credentials-access.mdx
[grammar] ~12-~12: Ensure spelling is correct
Context: ...tem"; # Database Credentials Access in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ess in SleakOps Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~58-~58: Ensure spelling is correct
Context: ...roup"> To view database credentials in SleakOps: 1. Navigate to your project 2. **G...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...VarGroup** 4. View the credentials: SleakOps fetches the secret from the cluster and...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-stuck-creating-status.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Creating Status Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ranch and triggers a deployment through SleakOps. The build process completes successfull...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...nt type: deploy_build_dev - Platform: SleakOps - Build status: Successful - Deployment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~98-~98: Ensure spelling is correct
Context: ... to contact SleakOps support"> Contact SleakOps support if: 1. **Deployment stuck for ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~181-~181: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deployment status ...
(DEEP_PROFOUND)
[grammar] ~469-~469: Ensure spelling is correct
Context: ...ific solutions"> Solutions specific to SleakOps platform deployment issues: 1. **Sleak...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~473-~473: Ensure spelling is correct
Context: ...t state management**: - Deployments in SleakOps may get stuck due to platform state man...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~475-~475: Ensure spelling is correct
Context: ...ates - Sometimes manual intervention by SleakOps support is required to reset state 2. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~597-~597: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-timeout-database-migrations.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...atabase Migrations Date: April 25, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~71-~71: Ensure spelling is correct
Context: ...ncrease pre-deploy timeout limits"> In SleakOps, you can configure longer timeout limit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/aws-cost-monitoring-and-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...and Optimization Date: January 16, 2025 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[uncategorized] ~58-~58: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...Deployment timing*: Partial month vs. full month billing - Multiple accounts: Costs ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 16, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/build-newrelic-pkg-resources-deprecation-warning.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Deprecation Warning Date: June 10, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ikely 81 or higher - Build environment: SleakOps managed containers **Error Conditions:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~192-~192: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/ci-cd-build-stage-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ld Stage Failure Date: October 10, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...correctly configured: 1. Access your SleakOps project dashboard 2. **Navigate to th...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~66-~66: Ensure spelling is correct
Context: ... CI/CD file was copied correctly** from SleakOps Common issues to check: ```yaml # Che...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...rigger a fresh build: Option 1: From SleakOps Dashboard 1. Go to your project in SleakOps 2....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...s Dashboard** 1. Go to your project in SleakOps 2. Navigate to the Deployments section ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~179-~179: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cicd-pip-to-pipx-installation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tallation Method Date: October 15, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ows fail when attempting to install the SleakOps CLI tool using the traditional `pip ins...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/cloudfront-existing-s3-bucket.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sting S3 Bucket Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~170-~170: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-addons-after-migration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... After Migration Date: October 15, 2024 Category: Cluster Tags: Mig...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...Context:** After a cluster migration in SleakOps, users cannot locate previously install...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with new interface - Affected addons: L...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... SleakOps with new interface - Affected addons: Loki, Grafana, and other monitoring to...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...available"> During cluster migrations, SleakOps temporarily deactivates addons to ensur...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...ss**: - Log into Grafana using your SleakOps credentials - Verify dashboards are displaying data ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-automatic-shutdown-startup-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Startup Issues Date: February 14, 2025 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...S ## Problem Description Context: SleakOps clusters configured with automatic shut...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/user_issues/cluster-eks-upgrade-schedule-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dule and Process Date: February 6, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~40-~40: Ensure spelling is correct
Context: ...cations - Need for coordination between SleakOps team and users ## Detailed Solution <...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~57-~57: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...email - Specific dates are communicated prior to each upgrade <...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[grammar] ~71-~71: Ensure spelling is correct
Context: ... On-Demand Upgrades: In some cases, SleakOps provides a workflow within the platform...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~86-~86: Ensure spelling is correct
Context: ... - Custom configurations not managed by SleakOps could be affected - Users should avoid ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...ions - Report any issues immediately to SleakOps support Before Upgrades: 1. **Review Applicat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...ompletion 3. Report Issues: Contact SleakOps immediately if problems arise **After ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on February 6, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-kubernetes-upgrade-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Upgrade Process Date: December 19, 2024 Category: Cluster Tags: Kub...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ication in the Cluster section of their SleakOps dashboard and need guidance on how to p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps managed Kubernetes cluster - Environmen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...t** on the upgrade notification in your SleakOps dashboard 2. The system will automatically begin the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ocess is fully automated and managed by SleakOps. <Troubleshooti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...e upgrades Process order: 1. Core SleakOps nodes are upgraded one by one (rolling ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~83-~83: Ensure spelling is correct
Context: ...tions** in your cluster (not managed by SleakOps) - Check the Kubernetes changelog for depre...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~89-~89: Ensure spelling is correct
Context: ...pecial database preparations needed for SleakOps managed upgrades - Ensure database conn...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...r usual monitoring tools 2. Check the SleakOps dashboard for upgrade progress 3. **W...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~132-~132: Ensure spelling is correct
Context: ...r logs If issues occur: - Contact SleakOps support immediately - Provide specific ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-manual-shutdown-scheduled-feature.mdx
[style] ~12-~12: The double modal “Requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...m"; # Cluster Manual Shutdown Requires Scheduled Feature Date: December 12, 2024 ...
(NEEDS_FIXED)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...heduled Feature Date: December 12, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~89-~89: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...y stop the cluster 4. Start the cluster manually when needed 5. No predefined schedule r...
(ADVERB_REPETITION_PREMIUM)
[style] ~135-~135: The double modal “requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...Behavior:** - Manual shutdown requires Scheduled Shutdown feature enabled - Background m...
(NEEDS_FIXED)
[style] ~167-~167: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 12, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cluster-understanding-ec2-instances-and-costs.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in EKS Clusters Date: January 29, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 29, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/cors-configuration-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Troubleshooting Date: December 19, 2024 Category: Workload Tags: CO...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...:** - Frontend and backend deployed on SleakOps - CORS configuration present in backend...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ..., meaning: - Infrastructure Level: SleakOps load balancers and ingress controllers ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~208-~208: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 25, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-migrations-execution-hooks.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Execution Hooks Date: December 19, 2024 Category: Workload Tags: Da...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ... as part of their deployment process in SleakOps, specifically for .NET applications usi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~82-~82: Ensure spelling is correct
Context: ... Execution:** 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~162-~162: Ensure spelling is correct
Context: ... 1. Use pre-upgrade hooks (default SleakOps behavior) for automatic migrations 2. *...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/database-postgresql-restore-errors.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Restore Errors Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~161-~161: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/dependencies-monitoring-graphs-not-displaying.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Not Displaying Date: January 22, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~128-~128: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 22, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-build-failed-production.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...g Loading Issues Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-build-failures-during-updates.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Platform Updates Date: October 14, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ild process fails temporarily while the SleakOps platform undergoes maintenance or updat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...rm communications**: - Subscribe to SleakOps status updates - Check email notific...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~155-~155: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-fargate-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ring Deployment Date: February 13, 2025 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...Users experience deployment failures in SleakOps when using AWS Fargate as the deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...eployment mode: AWS Fargate - Platform: SleakOps - Service: Container deployments - Reso...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~189-~189: Ensure spelling is correct
Context: ...ed-count 0 ``` 3. Coordinate with SleakOps support: - Report the specific res...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-pending-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Nodepool Changes Date: January 23, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...aking nodepool configuration changes in SleakOps, deployments remain in a pending state ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-redis-communication-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...munication Error Date: January 15, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~62-~62: Ensure spelling is correct
Context: ...you encounter this issue: 1. Contact SleakOps Support: This is typically an infrast...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~158-~158: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-service-name-length-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...gth Limit Error Date: February 13, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...to deploy a project with a long name in SleakOps. The automatically generated Kubernetes ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~174-~174: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ces Not Creating Date: January 15, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Domain: teams.simplee.cl - Platform: SleakOps - Deployment type: Teams instances **E...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...en to escalate the issue"> Escalate to SleakOps support if: 1. **Infrastructure Issues...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~282-~282: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deep cluster analy...
(DEEP_PROFOUND)
[style] ~453-~453: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/user_issues/docker-build-cache-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...es in Production Date: January 15, 2024 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with Docker builds - Environment: Produ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~121-~121: Ensure spelling is correct
Context: ...s** - Review the deployment logs in SleakOps - Look for "Using cache" messages that mig...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
🪛 Gitleaks (8.27.2)
docs/troubleshooting/user_issues/deployment-build-failed-production.mdx
74-74: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
(curl-auth-header)
🔇 Additional comments (22)
docs/troubleshooting/user_issues/cluster-production-check-node-scaling.mdx (1)
14-17: Contenido en inglés dentro de la sección españolaEl documento se añade bajo la nueva categoría “troubleshooting” en español, pero todo el cuerpo sigue en inglés (ej. “Date”, “Category”, “Tags”, etc.).
Para coherencia con el resto de la docs y SEO, convendría traducir los metadatos y encabezados principales al español.⛔ Skipped due to learnings
Learnt from: agustinoli PR: sleakops/docs#85 File: docs/project/dependency/index.mdx:78-78 Timestamp: 2024-11-27T17:42:11.531Z Learning: En el documento `docs/project/dependency/index.mdx`, la numeración de los pasos es correcta y no necesita cambios.docs/troubleshooting/user_issues/cors-configuration-troubleshooting.mdx (1)
1-8: Categoría front-matter poco coherenteEl campo
category: "workload"no cuadra con la nueva sección de Troubleshooting anunciada en el PR.
Revisa si la taxonomía Docusaurus espera"troubleshooting"para que el documento aparezca donde corresponde.docs/troubleshooting/user_issues/cluster-manual-shutdown-scheduled-feature.mdx (1)
10-10: Verifica el casing y la ruta del componente importadoLa ruta
@site/src/components/HomepageFeatures/troubleshootingitemusa todo en minúsculas. Si el archivo real se llamaTroubleshootingItem.tsx/tsx/jsx, en sistemas case-sensitive (Linux, CI, prod) fallará la compilación de Docusaurus.docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx (1)
12-17: Incongruencia de idioma
El PR añade categoría “troubleshooting” en español, pero el contenido de este artículo está enteramente en inglés. ¿Queremos traducir o etiquetar como contenido en inglés?docs/troubleshooting/user_issues/cluster-nodepool-missing-after-shutdown.mdx (1)
10-10: Ruta de importación potencialmente incorrecta – cuidado con los builds en sistemas case-sensitiveEl componente se importa desde
@site/src/components/HomepageFeatures/troubleshootingitempero el propio nombre del componente es
TroubleshootingItem(mayúscula inicial).
En muchos repositorios este componente vive en@site/src/components/TroubleshootingItem.
La discrepancia de path y mayúsculas puede romper el build en entornos case-sensitive (p. ej. Linux CI).-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/TroubleshootingItem";Verificá la ruta real antes de mergear, así no nos comemos un 🍍 en la pipeline.
docs/troubleshooting/user_issues/aws-marketplace-login-setup-issue.mdx (1)
10-10: Revisa la ruta y el uso de mayúsculas en la importación.En la mayoría de los casos, los componentes React viven en ficheros con el mismo nombre en PascalCase. Aquí se importa:
import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
troubleshootingitemen minúsculas podría provocar un fallo en sistemas case-sensitive si el fichero real se llamaTroubleshootingItem.tsx/jsx.- Confirma que dicha ruta sigue siendo válida tras “remover FAQItem”.
- Si la ruta cambió al mover categorías a Español, actualízala.
docs/troubleshooting/user_issues/celery-beat-duplicate-execution.mdx (1)
350-363: CampotimeZoneaún no estable en todas las versiones de KubernetesEl atributo
timeZonesolo está disponible a partir de v1.29 (y antes detrás de feature gate). Añade una nota para que el lector verifique la versión del clúster o propón la alternativa de usar TZ en el contenedor.docs/troubleshooting/user_issues/cluster-understanding-ec2-instances-and-costs.mdx (1)
10-11: Import correcto: ruta y nombre de archivo coinciden
He comprobado que el fichero real se llamatroubleshootingitem.jsxensrc/components/HomepageFeatures, así que la importación en minúsculas es totalmente válida y no romperá el build. Puedes ignorar esta sugerencia. [en sleakops arreglamos los conflictos a las piñas]Likely an incorrect or invalid review comment.
docs/troubleshooting/user_issues/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
10-10: Importación verificada: no se requiere ajuste de casing
El archivosrc/components/HomepageFeatures/troubleshootingitem.jsxexiste con nombre en minúsculas, por lo que la ruta y el casing del import son correctos.
en sleakops arreglamos los conflictos a las piñasdocs/troubleshooting/user_issues/django-celery-appregistrynotready-error.mdx (1)
10-10: Ignora la alerta de case-sensitivity: la ruta coincide con el nombre de archivo
¡En sleakops arreglamos los conflictos a las piñas! El import@site/src/components/HomepageFeatures/troubleshootingitemapunta exactamente al archivo
troubleshootingitem.jsx, por lo que no hay ningún fallo de mayúsculas en sistemas sensibles.Likely an incorrect or invalid review comment.
docs/troubleshooting/user_issues/build-pods-stuck-creation.mdx (2)
1-8: Front-matter:category: "project"no encaja con la nueva taxonomíaLas guías de troubleshooting recientes usan categorías como
"user_issues"o similares, no"project".
Revisar para no romper la navegación lateral.-category: "project" +category: "user_issues"
14-14: Detalle de estilo en la fechaSegún las reglas de estilo en español, conviene escribir “22 de marzo de 2025” en lugar de “March 22, 2025”.
Además, si se mantiene el formato estadounidense, faltaría la coma después del día (indicada por LanguageTool).[ suggest_nitpick ]
docs/troubleshooting/user_issues/build-status-discrepancy-lens-vs-platform.mdx (1)
10-10: Verifica la ruta de import deTroubleshootingItem
@site/src/components/HomepageFeatures/troubleshootingitemparece poco alineado con la convención de mayúsculas y con la ubicación usada por otros docs (components/TroubleshootingItem). Un path incorrecto romperá la compilación de Docusaurus.Un
rg TroubleshootingItem src/componentste dirá enseguida dónde vive el componente real.docs/troubleshooting/user_issues/deployment-build-failed-production.mdx (1)
74-74: Token en ejemplo de cURL está bien anonimizado
YOUR_TOKENes un placeholder; no hay filtración real. Solo confirmar que siga así en la versión publicada.docs/troubleshooting/user_issues/database-restore-pod-management.mdx (1)
10-11: Verifica mayúsculas/minúsculas en la ruta del componente.En sistemas case–sensitive la ruta
@site/src/components/HomepageFeatures/troubleshootingitemfallará si el fichero se llamaTroubleshootingItem.tsx/tsx. Comprueba nombre real y ajusta:-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";Evitarás un build roto a último momento – ¡en SleakOps arreglamos los conflictos a las piñas!
docs/troubleshooting/user_issues/database-performance-optimization.mdx (1)
67-78: Precisa impacto real de 20-30 min.Indica claramente si la operación provoca downtime o solo latencia. Así evitamos confusiones en producción.
docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx (1)
2-2:sidebar_position: 3duplicado dentro del mismo sub-árbolTodos los MDX de
user_issuescomparten la misma posición, por lo que el orden final será impredecible. Verificad si cada archivo necesita un valor único o si queréis un orden explícito víaposition.docs/troubleshooting/user_issues/cluster-node-errors-web-api-unavailable.mdx (1)
10-10: Posible choque por el uso de mayúsculas/minúsculas en la ruta del componenteEn sistemas de archivos sensibles a mayúsculas (Linux, CI), la ruta
HomepageFeatures/troubleshootingitemno coincide con el nombre PascalCase del componente importado (TroubleshootingItem).
Si el fichero real se llamaTroubleshootingItem.tsx/tsx, este import fallará en build.-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";Verifica el nombre real del fichero antes de pegarse con el CI.
docs/troubleshooting/user_issues/cluster-eks-upgrade-volume-attachment-issue.mdx (1)
10-10: Ruta del componente con posible problema de mayúsculasVerifica que el archivo real siga la misma capitalización que el import.
docs/troubleshooting/user_issues/cluster-prometheus-memory-issues.mdx (1)
10-10: Comprueba la ruta y el casing del componente importado
import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";usa el nombre del archivo en minúsculas. Si el componente real se llamaTroubleshootingItem.tsx, los sistemas de ficheros sensibles a mayúsculas (Linux, CI) romperán la build.docs/troubleshooting/user_issues/cluster-upgrade-maintenance-scheduling.mdx (1)
70-86: Verifica la coherencia de horario entre UTC y UTC-3El ejemplo indica inicio 02:00 UTC → 23:00 UTC-3 del día anterior; conviene aclararlo para evitar dobles interpretaciones del calendario del cliente.
docs/troubleshooting/user_issues/cluster-kubernetes-upgrade-process.mdx (1)
12-18: La sección de troubleshooting usa inglés
Todos los archivos endocs/troubleshooting/user_issues/(incluidocluster-kubernetes-upgrade-process.mdx) siguen la convención de documentación en inglés. No es necesario traducir este fichero al español.Likely an incorrect or invalid review comment.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
¡Ojo con el case-sensitive en el import!
En sistemas case-sensitive (Linux, CI, Netlify) el componente se importa desde
@site/src/components/HomepageFeatures/troubleshootingitem (todo en minúsculas) pero el nombre del fichero suele ser TroubleshootingItem.tsx/mdx.
Si el archivo real está en mayúscula, el build fallará a las piñas.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/aws-cost-monitoring-and-optimization.mdx
around lines 10 to 11, the import statement uses a lowercase filename
'troubleshootingitem' which may cause build failures on case-sensitive systems
if the actual file is named 'TroubleshootingItem.tsx' or
'TroubleshootingItem.mdx'. Fix this by updating the import path to match the
exact case of the filename, changing it to
'@site/src/components/HomepageFeatures/TroubleshootingItem'.
| tags: ["aws", "ec2", "vpc", "networking", "public-ip"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta de importación con posible error de capitalización rompe la build
En la mayoría de sistemas case-sensitive (Linux, CI), el fichero del componente se llama TroubleshootingItem.tsx. El path usado aquí (troubleshootingitem) falla al resolver el módulo y detendrá el build de Docusaurus.
Propuesta:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/aws-ec2-public-ip-assignment.mdx at line 10,
the import path for TroubleshootingItem uses incorrect capitalization which
causes build failures on case-sensitive systems. Change the import path to match
the exact filename casing: use "TroubleshootingItem" instead of
"troubleshootingitem" to correctly resolve the module.
| # EC2 Instance Not Getting Public IPv4 Address | ||
|
|
||
| **Date:** January 15, 2024 | ||
| **Category:** Provider | ||
| **Tags:** AWS, EC2, VPC, Networking, Public IP | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Contenido en inglés dentro de la nueva categoría “Troubleshooting” en español
El objetivo del PR es añadir documentación en español, pero este artículo está íntegramente en inglés. Esto genera una experiencia inconsistente para los usuarios hispanohablantes y rompe la homogeneidad del sitio.
Sugerencia: traducir el documento completo o, si se decide mantenerlo en inglés, ubicarlo en la sección en inglés y añadir el correspondiente locale: en en el front-matter.
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic IPv4 Address Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/aws-ec2-public-ip-assignment.mdx around
lines 12 to 17, the content is entirely in English while the new category is in
Spanish, causing inconsistency. To fix this, either translate the entire
document into Spanish to match the category or move the document to the English
section and add the front-matter attribute `locale: en` to indicate it is in
English.
| # AWS Marketplace Login and Setup Issue | ||
|
|
||
| **Date:** January 15, 2024 | ||
| **Category:** User | ||
| **Tags:** AWS Marketplace, Authentication, Login, Setup | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Contenido en inglés dentro de la categoría en español.
El PR indica que se añade una categoría troubleshooting “en español”, sin embargo el título y todo el texto están en inglés. Esto puede confundir a los usuarios que navegan la documentación ES.
Valora traducir:
- Título (
title), encabezados y pasos. - Tags a su equivalente español (
autenticación,inicio-sesión, etc.).
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... and Setup Issue Date: January 15, 2024 Category: User Tags: AWS Ma...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/aws-marketplace-login-setup-issue.mdx around
lines 12 to 17, the content is in English while the category is marked as
Spanish, which can confuse users. Translate the title, headings, and all steps
into Spanish, and convert the tags to their Spanish equivalents such as
"autenticación" and "inicio-sesión" to maintain consistency with the category
language.
| tags: ["aws", "waf", "security", "load-balancer", "bot-protection"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
La ruta de importación rompe en sistemas case-sensitive
El componente se importa como TroubleshootingItem, pero la ruta termina en troubleshootingitem en minúsculas. En entornos *nix esto levantará un Module not found.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/aws-waf-application-load-balancer-protection.mdx
at line 10, the import path for the TroubleshootingItem component uses lowercase
'troubleshootingitem', which causes a module not found error on case-sensitive
systems. Update the import path to match the exact casing of the component
folder or file name, changing 'troubleshootingitem' to 'TroubleshootingItem' to
ensure the import works correctly on all environments.
| tags: ["deployment", "build", "troubleshooting", "stuck", "creating"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Capitalización del import — bloquea la compilación
Igual que en otros documentos, cambia troubleshootingitem a TroubleshootingItem.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";¡En SleakOps arreglamos los conflictos a las piñas!
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/deployment-stuck-creating-status.mdx at line
10, the import statement uses incorrect capitalization for the component name.
Change the import from "troubleshootingitem" to "TroubleshootingItem" to match
the correct case and fix the compilation error.
| tags: ["deployment", "dockerfile", "build", "troubleshooting", "starting-state"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Import mal capitalizado: rompe el build en Linux
Mismo ajuste recomendado que en otros archivos.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/deployment-stuck-starting-state.mdx at line
10, the import statement for TroubleshootingItem has incorrect capitalization
causing build failures on Linux. Correct the import to match the exact case of
the file or component name, ensuring it is properly capitalized as
TroubleshootingItem.
| # Deployment and Teams Instances Not Creating | ||
|
|
||
| **Date:** January 15, 2024 | ||
| **Category:** Project | ||
| **Tags:** Deployment, Teams, Instances, Troubleshooting | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
La guía se anunció “en español”… pero está escrita en inglés
El objetivo del PR es añadir la categoría de troubleshooting en español. Este documento completo está en inglés, lo que genera incoherencia con el resto del contenido multilingüe y con la expectativa de los usuarios. Reescribe o localiza el contenido al español para mantener consistencia.
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ces Not Creating Date: January 15, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/deployment-teams-instances-not-creating.mdx
around lines 12 to 17, the content is written in English despite the guide being
announced as Spanish. To fix this, translate or rewrite the entire content of
this document into Spanish to ensure consistency with the multilingual content
and user expectations.
| tags: ["docker", "build", "cache", "arguments", "no-cache"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Ruta de componente mal capitalizada
Repite el patrón:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/docker-build-cache-no-cache-option.mdx at
line 10, the import statement for the TroubleshootingItem component has
incorrect capitalization. Correct the import path to match the exact case of the
component file and folder names to avoid import errors.
| <TroubleshootingItem id="docker-compose-configuration" summary="Complete docker-compose.yml configuration"> | ||
|
|
||
| Here's a complete example of how to configure your `docker-compose.yml`: | ||
|
|
There was a problem hiding this comment.
IDs duplicados: el scroll-spy se va a pegar contra la pared
id="docker-compose-configuration" aparece dos veces. Docusaurus/MDX no permite anclas duplicadas, la navegación se rompe “a las piñas”.
-<TroubleshootingItem id="docker-compose-configuration" summary="Docker Compose configuration for logging">
+<TroubleshootingItem id="docker-compose-logging" summary="Docker Compose configuration for logging">Renombra uno de los dos IDs (o ambos) para garantizar unicidad.
Also applies to: 343-347
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/docker-daphne-logging-configuration.mdx
around lines 120 to 123 and also lines 343 to 347, there are duplicate IDs
"docker-compose-configuration" used in TroubleshootingItem components. Rename
one or both of these IDs to unique values to prevent navigation issues caused by
duplicate anchors in Docusaurus/MDX.
|
|
||
| ```bash | ||
| # Linux | ||
| sudo systemctl flush-dns | ||
|
|
||
| # macOS | ||
| sudo dscacheutil -flushcache | ||
|
|
||
| # Windows | ||
| ipconfig /flushdns | ||
| ``` |
There was a problem hiding this comment.
Comandos de limpieza de DNS incorrectos en Linux/macOS
systemctl flush-dns no existe y en macOS falta reiniciar mDNSResponder. Esto puede inducir a error al lector.
-# Linux
-sudo systemctl flush-dns
+# Linux (systemd-resolve)
+sudo resolvectl flush-caches
+# macOS
-sudo dscacheutil -flushcache
+# macOS
+sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ```bash | |
| # Linux | |
| sudo systemctl flush-dns | |
| # macOS | |
| sudo dscacheutil -flushcache | |
| # Windows | |
| ipconfig /flushdns | |
| ``` |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/api-access-troubleshooting-private-services.mdx
around lines 226 to 236, the DNS flush commands for Linux and macOS are
incorrect. Replace "sudo systemctl flush-dns" with the correct Linux command,
such as "sudo systemd-resolve --flush-caches" or "sudo systemctl restart
systemd-resolved" depending on the distro. For macOS, add the command to restart
mDNSResponder after flushing the cache, for example "sudo killall -HUP
mDNSResponder". Update the instructions accordingly to prevent confusion.
| # Generate temporary kubeconfig | ||
| kubectl config set-cluster temp-cluster --server=https://your-endpoint | ||
| kubectl config set-context temp-context --cluster=temp-cluster | ||
| kubectl config use-context temp-context | ||
| ``` |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Contexto temporal sin usuario → riesgo de ensuciar configuración global
Al crear un contexto kubeconfig temporal con
kubectl config set-cluster temp-cluster --server=https://your-endpointno se define usuario ni credenciales, lo que deja un contexto parcialmente funcional y podría confundir al usuario. Añade al menos --insecure-skip-tls-verify=true o especifica un usuario para evitar errores de autenticación.
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/cluster-connection-troubleshooting.mdx
around lines 172 to 176, the temporary kubeconfig cluster is set without
specifying user credentials or TLS options, which can cause authentication
errors. Update the kubectl config set-cluster command to include
--insecure-skip-tls-verify=true or specify a user to ensure the context is
functional and avoid confusion or authentication failures.
| tags: ["kubernetes", "upgrade", "cluster", "maintenance"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta del componente “TroubleshootingItem” con posible problema de mayúsculas
Mismo detalle que en el otro archivo: usar “TroubleshootingItem” con mayúscula para evitar fallos en CI.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/cluster-kubernetes-upgrade-process.mdx at
line 10, the import statement for the TroubleshootingItem component should use
the exact casing "TroubleshootingItem" with an uppercase "I" to prevent CI build
failures. Update the import path to match the component's correct casing
exactly.
| --- | ||
| sidebar_position: 3 | ||
| title: "Prometheus Memory Issues Causing Pod Hangs" | ||
| description: "Solution for Prometheus memory issues that cause application pods to hang in production" | ||
| date: "2024-12-23" | ||
| category: "cluster" | ||
| tags: ["prometheus", "memory", "monitoring", "troubleshooting", "pods"] | ||
| --- |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Numera los sidebar_position para evitar colisiones en la sidebar
Todos los documentos dentro de user_issues usan sidebar_position: 3. Docusaurus muestra una sola entrada o genera orden impredecible cuando varias páginas comparten la misma posición. Asigna números únicos (1, 2, 3…) a cada archivo o elimina la clave para usar el orden alfabético.
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/cluster-prometheus-memory-issues.mdx lines 1
to 8, the sidebar_position is set to 3, which conflicts with other documents
using the same number. To fix this, assign a unique sidebar_position number that
does not collide with others in the user_issues folder or remove the
sidebar_position key entirely to default to alphabetical ordering.
| date: "2024-12-19" | ||
| category: "cluster" |
There was a problem hiding this comment.
Incongruencia de fechas: 2024 vs 2025
El front-matter declara 2024-12-19, pero el pie dice “automáticamente generado el 19 de diciembre de 2025”.
Definir una sola fecha evita confusión sobre la vigencia del artículo.
Also applies to: 205-205
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/connecting-to-cluster-with-lens.mdx around
lines 5 to 6 and line 205, the front-matter date is set to 2024-12-19 but the
footer states the article was generated on December 19, 2025, causing a date
inconsistency. Update the footer date to match the front-matter date
(2024-12-19) to ensure consistency and avoid confusion about the article's
validity.
| ["mysql", "redis", "timeout", "connection", "troubleshooting", "networking"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Posible error de mayúsculas/ubicación en la importación del componente
En sistemas de archivos sensibles a mayúsculas (por ejemplo Linux en CI), troubleshootingitem no coincidirá con un archivo llamado TroubleshootingItem.tsx / .jsx. Esto romperá el build de Docusaurus.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx
at line 11, the import statement uses incorrect casing for the
TroubleshootingItem component. Update the import path to match the exact
filename casing, changing "troubleshootingitem" to "TroubleshootingItem" to
ensure compatibility with case-sensitive file systems and prevent build errors.
| # MySQL and Redis Connection Timeout Issues | ||
|
|
||
| **Date:** January 15, 2024 | ||
| **Category:** Dependency | ||
| **Tags:** MySQL, Redis, Timeout, Connection, Troubleshooting, Networking | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
❓ Verification inconclusive
Contenido en inglés dentro de la nueva categoría de “troubleshooting” en español
El PR indica que se añade una categoría en español, sin embargo el título y los metadatos están en inglés. Conviene traducir:
# MySQL y Redis: problemas de timeout de conexión**Fecha:** 15 de enero de 2024
De lo contrario, la UX queda incoherente y rompe la promesa de docs en español.
¿Convertimos todo el cuerpo o se moverá a la carpeta /en/?
Incoherencia de idioma en la categoría “troubleshooting”
El archivo docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx está bajo la sección en español, pero tanto el título como los metadatos aparecen en inglés. Para mantener la consistencia y la promesa de documentación en español, hace falta traducir al menos el encabezado y la fecha, o bien mover este artículo completo a la carpeta de inglés (/en/).
Por ejemplo, podríamos aplicar este cambio mínimo:
- # MySQL and Redis Connection Timeout Issues
+ # MySQL y Redis: problemas de timeout de conexión
- **Date:** January 15, 2024
+ **Fecha:** 15 de enero de 2024 • Confirma si traducimos todo el cuerpo al español o lo reubicamos en /en/.
• Si optamos por quedarnos en español, revisa también las etiquetas y ejemplos internos para garantizar la coherencia.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # MySQL and Redis Connection Timeout Issues | |
| **Date:** January 15, 2024 | |
| **Category:** Dependency | |
| **Tags:** MySQL, Redis, Timeout, Connection, Troubleshooting, Networking | |
| # MySQL y Redis: problemas de timeout de conexión | |
| **Fecha:** 15 de enero de 2024 | |
| **Category:** Dependency | |
| **Tags:** MySQL, Redis, Timeout, Connection, Troubleshooting, Networking |
🧰 Tools
🪛 LanguageTool
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Timeout Issues Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In
docs/troubleshooting/user_issues/dependency-connection-timeout-mysql-redis.mdx
around lines 13 to 18, the title and metadata are in English while the file is
located in the Spanish troubleshooting section, causing language inconsistency.
Decide whether to translate the entire document including the title, date, tags,
and internal examples to Spanish for consistency, or move the file to the
English documentation folder (/en/). Apply the chosen approach fully to maintain
coherent language usage throughout the file.
| tags: ["dns", "cloudflare", "route53", "aws", "configuration"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta con posible conflicto de mayúsculas/minúsculas en el import
En sistemas con FS case-sensitive (Linux, CI), el fichero suele llamarse TroubleshootingItem.tsx. El path actual usa sólo minúsculas (troubleshootingitem) y puede romper la build.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/dns-cloudflare-route53-configuration.mdx at
line 10, the import path for TroubleshootingItem uses all lowercase letters
which may cause build failures on case-sensitive file systems like Linux. Update
the import path to match the exact filename casing, changing
"troubleshootingitem" to "TroubleshootingItem" to ensure consistency and prevent
build errors.
| tags: ["aws", "dns", "route53", "migration", "donweb"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Verifica la ruta y el casing del componente importado
En varios archivos el componente está declarado como TroubleshootingItem (camel-case). Aquí se usa todo en minúsculas; en sistemas de archivos sensibles a mayúsculas (Linux, CI) esto rompe el build de Docusaurus.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/user_issues/dns-migration-donweb-to-aws.mdx at line 10,
the import statement uses incorrect casing for the component name. Change the
import from all lowercase to camel-case "TroubleshootingItem" to match the
component declaration and avoid build errors on case-sensitive file systems.
There was a problem hiding this comment.
Actionable comments posted: 61
♻️ Duplicate comments (21)
docs/troubleshooting/cluster-manual-shutdown-scheduled-feature.mdx (1)
1-8:sidebar_positionduplicadoMismo comentario que en el archivo anterior: asigna posiciones únicas para evitar conflictos en la barra lateral.
docs/troubleshooting/deployment-pending-nodepool-changes.mdx (1)
10-11: Path en minúsculas → posible fallo en el buildVer comentario equivalente en archivos anteriores.
docs/troubleshooting/database-migration-data-integrity-issues.mdx (1)
10-11: Path del componenteRevisar casing del path como en los demás archivos.
docs/troubleshooting/cluster-upgrade-maintenance-scheduling.mdx (1)
1-8: Posición duplicada y contenido en inglésReitero los comentarios previos sobre
sidebar_position: 3y la falta de traducción al español.docs/troubleshooting/database-postgresql-restore-errors.mdx (1)
10-10: Mismo asunto de capitalización en la ruta de import
Revisa quetroubleshootingitemcoincida exactamente con el nombre físico del componente para evitar errores de compilación.docs/troubleshooting/build-pods-stuck-creation.mdx (1)
10-10: Ruta de import con posible discrepancia de mayúsculas
Asegúrate de que la carpeta/archivotroubleshootingitemexista con la misma capitalización.docs/troubleshooting/dns-propagation-public-deployment.mdx (1)
10-10: Revisa la capitalización del import
Idem a los otros documentos para evitar “module not found”.docs/troubleshooting/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
10-10: Capitalización del import
Mismo comentario sobretroubleshootingitem.docs/troubleshooting/cluster-addons-after-migration.mdx (1)
10-10: Mismo problema de casing en la importación
Corrige la ruta como en el comentario anterior para evitar error de módulo no encontrado.docs/troubleshooting/deployment-newrelic-pkg-resources-warning.mdx (1)
11-11: Importación con casing incorrecto
Repite el ajuste de mayúsculas/minúsculas paraTroubleshootingItem.docs/troubleshooting/dns-resolution-failure-mysql-redis.mdx (1)
10-10: Casing de la importación again
Ajustar la ruta del componente.docs/troubleshooting/database-credentials-access.mdx (1)
10-10: Casing del componente
Mismo fix de ruta para evitar fallos de compilación.docs/troubleshooting/cluster-critical-addons-node-failure.mdx (1)
11-11: Casing del importMismo ajuste que en los otros archivos.
docs/troubleshooting/dns-delegation-ssl-certificate-validation.mdx (2)
10-10: Import path con posible conflicto de capitalización
Mismo problema señalado en el primer archivo: la ruta usatroubleshootingitemen minúsculas.
2-2:sidebar_positionrepetido
Este archivo también usasidebar_position: 3; verifica numeración única.docs/troubleshooting/dns-domain-delegation-cloudflare-route53.mdx (2)
10-10: Import path con posible conflicto de capitalización
Revisar la ruta del componente como indicado anteriormente.
2-2:sidebar_positionduplicado
Mismo comentario que en el primer archivo.docs/troubleshooting/dns-delegation-route53-domain-configuration.mdx (2)
10-10: Import path con posible conflicto de capitalización
Aplicar la misma corrección sugerida en el primer archivo.
2-2:sidebar_positionduplicado
Asegura posiciones únicas en la sidebar.docs/troubleshooting/deployment-teams-instances-not-creating.mdx (2)
10-10: Import path con posible conflicto de capitalización
Corregir la capitalización del import como en los otros documentos.
2-2:sidebar_positionduplicado
Ver comentario previo sobre posiciones de la sidebar.
🧹 Nitpick comments (97)
docs/troubleshooting/celery-beat-duplicate-execution.mdx (2)
14-16: Falta la coma estilo Chicago en la fecha
Después del año se suele poner coma si seguimos formato inglés (“December 23, 2024, …”). Es un detalle menor pero mantiene coherencia con el resto del sitio.
367-367: Etiqueta de generación automática
La línea se presenta como FAQ pero el documento es guía de troubleshooting; quizá convenga adaptarla o removerla para evitar confusión sobre la fuente y autoría.docs/troubleshooting/aws-marketplace-login-setup-issue.mdx (1)
164-165: Etiqueta final desalineada con el tipo de documento
El cierre dice “This FAQ was automatically generated” pero el archivo no es una FAQ sino un artículo de troubleshooting. Ajusta el texto para evitar confundir al lector.docs/troubleshooting/django-celery-appregistrynotready-error.mdx (2)
1-8: Campocategoryen front-matter no es estándar en DocusaurusDocusaurus soporta
sidebar_position,title,description,tags,slug, etc. pero no reconocecategory.
Esto puede quedar simplemente como dato “muerto” o, peor, romper plugins que esperen front-matter válido.Si querés agrupar por categoría usá los métodos nativos del sidebar (
label,position) o añadí la meta en otro lugar (p.ej. un tag adicional).
12-175: El contenido está en inglés aunque la sección declarada es “troubleshooting” en españolEl objetivo del PR indica “añadir categoría de troubleshooting en español”. Sin embargo, todo el documento está en inglés.
Para mantener coherencia con el resto de la docu y la UX, convendría traducirlo o, al menos, indicar que está pendiente de localización.docs/troubleshooting/cronjob-timezone-deployment-behavior.mdx (2)
14-17: Añade la coma que recomienda el estilo después del año.-**Date:** October 24, 2024 +**Date:** October 24, 2024,Así evitamos la alerta de LanguageTool y mantenemos coherencia con guías de estilo anglosajonas.
172-172: Mismo detalle de coma tras el año en la nota final.-_This FAQ was automatically generated on October 24, 2024 based on a real user query._ +_This FAQ was automatically generated on October 24, 2024, based on a real user query._Puramente cosmético.
docs/troubleshooting/cors-configuration-troubleshooting.mdx (2)
14-16: Fecha duplicada y formato poco claro
Ya tienes la fecha en el front-matter (date:). Repetirla en el cuerpo genera mantenimiento extra y riesgo de des-sincronización. Mejor quita el bloque manual o usa la variable de front-matter via MDX.
208-208: La nota final habla de “FAQ”… pero esto es “Troubleshooting”
Pequeño despiste que puede confundir a la gente: cambia “This FAQ was automatically generated…” por “This troubleshooting guide…” o similar.docs/troubleshooting/dependencies-monitoring-graphs-not-displaying.mdx (3)
61-84: Marcadores de sustitución más claros en los ejemplos de CLIPara evitar que alguien copie-y-pegue comandos sin cambiar los identificadores, sugiere envolver los placeholders en MAYÚSCULAS y entre
< >, p. ej.<YOUR_DB_INSTANCE>. Además facilita búsquedas rápidas en la doc.- --dimensions Name=DBInstanceIdentifier,Value=your-db-instance \ + --dimensions Name=DBInstanceIdentifier,Value=<YOUR_DB_INSTANCE> \
90-100: Añadir enlace al ticket o release que introduce el fixMencionas que el equipo está trabajando en la solución, pero no hay un enlace a issue interno, changelog o PR que siga el progreso. Un link rápido ayuda a los usuarios y evita que tengamos que explicar a las piñas qué pasó.
128-128: Incoherencia de terminología: FAQ vs TroubleshootingLa nota final dice “This FAQ was automatically generated”, pero el documento pertenece a la categoría de troubleshooting. Cambiar “FAQ” por “troubleshooting article” mantendría consistencia con el resto de la sección.
docs/troubleshooting/docker-daphne-logging-configuration.mdx (1)
14-16: Coma faltante tras el año en las fechasSegún los lineamientos de estilo (y lo marca LanguageTool), habría que escribir “21 de enero de 2025,” con coma después del año. Mismo ajuste en la línea 553. Cambio muy menor pero suma prolijidad.
Also applies to: 553-553
docs/troubleshooting/aws-waf-application-load-balancer-protection.mdx (3)
1-8: Añadir coma tras el año en la cabeceraEl front-matter y la descripción al final del documento omiten la coma después del año (p.ej. “19 de diciembre de 2024” → “19 de diciembre de 2024,”). No rompe el build, pero varios linters (incl. LanguageTool) lo señalan.
254-258: Comillas anidadas en elfilter-patternproducen confusiónEl patrón contiene comillas dobles dentro de otras comillas dobles. En bash se interpreta mal. Usa comillas simples externas:
- --filter-pattern "\"action\":\"BLOCK\"" + --filter-pattern '{"action":"BLOCK"}'
361-361: La nota final habla de “FAQ” en lugar de “Troubleshooting”Genera incoherencia con la nueva categoría añadida y confunde a la gente que busca documentación. Sustituir “FAQ” por “Guía de troubleshooting” o similar.
docs/troubleshooting/deployment-service-name-length-limit.mdx (1)
14-16: Falta una coma tras el año en la línea de metadatosSeguir la guía de estilo evita alertas de linter y mejora la legibilidad.
-**Date:** February 13, 2025 +**Date:** February 13, 2025,docs/troubleshooting/cloudfront-existing-s3-bucket.mdx (4)
14-16: Falta la coma tras el año en la fechaEn español (y en varios style-guides en inglés) se recomienda separar el año con comas:
“December 19, 2024”.-**Date:** December 19, 2024 +**Date:** December 19, 2024,
43-49: Aclarar alcance de la limitación para evitar confusiónSe afirma que “SleakOps no soporta editar dependencias”, pero luego el documento propone recrear el recurso desde SleakOps. Quizás convenga puntualizar que la limitación aplica únicamente a la edición «post-creación» y no al flujo de creación inicial, para que nadie piense que la función está totalmente ausente.
147-166: Advertir sobre DNS, ACLs y downtime al recrear el bucketEl paso alternativo de “rehacer el bucket” omite advertir sobre:
- Propagación DNS si el bucket estaba vinculado a un dominio.
- Pérdida de ACLs/etiquetas si no se copian explícitamente.
- Posible downtime durante la copia de datos.
Añadir un bloque de “Consideraciones antes de recrear” ahorrará sorpresas.
168-170: Inconsistencia de terminología: FAQ vs TroubleshootingEl texto final dice “This FAQ was automatically generated”, pero el documento se presenta como guía de troubleshooting. Sustituir “FAQ” por “troubleshooting article” mantendrá coherencia.
-_This FAQ was automatically generated on December 19, 2024 based on a real user query._ +_This troubleshooting article was automatically generated on December 19, 2024 based on a real user query._docs/troubleshooting/aws-ec2-public-ip-assignment.mdx (1)
169-172: Pequeña coma faltante para mantener el estilo en fechasEn la frase final falta una coma después del año:
-_This FAQ was automatically generated on January 15, 2024 based on a real user query._ +_This FAQ was automatically generated on January 15, 2024, based on a real user query._Detalle mínimo, pero evitamos que el linter nos venga a los golpes.
docs/troubleshooting/cicd-pip-to-pipx-installation.mdx (1)
96-103:pipx ensurepathno es suficiente en contenedores efímeros.Después de
ensurepath, la shell de la misma step no recargaPATH; la línea siguiente que llama apipx installusa la misma shell y funciona, pero comandos posteriores (p. ej.sleakops deploy) correrán en otra step y podrían no tener el PATH actualizado. Añadeexport PATH="$(python -m pipx ensurepath --force | tail -1):$PATH"o usa directamente la ruta de binarios de pipx.docs/troubleshooting/ci-cd-github-actions-not-triggering.mdx (1)
70-75: Uso mixto de comillas en la matriz de ramas – conviene unificar.Aunque GitHub lo tolera, declarar arrays con mezcla de comillas simples/dobles reduce la legibilidad.
- branches: [dev, main] + branches: ['dev', 'main']docs/troubleshooting/ci-cd-build-stage-failure.mdx (1)
120-123: Posible confusión con “recursos del cluster”.Aquí se alude a “cluster” sin decir Kubernetes ni ECS. Añadir una aclaración rápida evita dudas:
- Verify the 'stage' environment has sufficient resources + Verify the 'stage' environment (Kubernetes/ECS cluster) has sufficient resourcesdocs/troubleshooting/docker-build-cache-issues.mdx (2)
1-8: Meta-datos no estándar “category”.El front-matter añade
category: "project", pero Docusaurus ya usa la sub-carpetadocs/troubleshooting/y un_category_.json.
Este campo adicional no se procesa y puede confundir a futuros autores. Elimínalo o documenta su propósito.
175-176: Etiqueta final desalineada con el tipo de documento.La nota de pie dice “This FAQ was automatically generated...”. Aquí no hay FAQ sino guía de troubleshooting; cambiar a “article” o “guide” para mantener coherencia.
docs/troubleshooting/cluster-aws-vcpu-quota-limit.mdx (1)
198-200: Fecha incorrecta en el pie.El pie indica “January 15 2024”, pero el front-matter y el artículo hablan del 24 de abril 2024. Corrige la fecha para evitar confusión.
docs/troubleshooting/deployment-fargate-vcpu-quota-limit.mdx (1)
68-93: Código CLI: especifica región para evitar falsos negativos.Los ejemplos
aws service-quotasfallarán si el perfil por defecto no apunta a la región correcta. Añade--region us-east-1(o similar) al snippet.docs/troubleshooting/deployment-automatic-updates-github.mdx (1)
55-59: Listas numeradas sin sangría correcta en MDX.Al usar listas dentro de un componente MDX a veces se requiere una línea en blanco previa para que el parser no rompa. Revisa la vista previa.
docs/troubleshooting/api-access-troubleshooting-private-services.mdx (1)
67-70: Comandoroute -nsolo Linux; aclara alternativa macOS.En macOS el comando es
netstat -rn. Añade nota para evitar confusión.docs/troubleshooting/docker-build-environment-variables.mdx (1)
14-17: Coma de cortesía tras el añoEl encabezado “Date: March 10, 2025” debería llevar coma tras el año según el estilo US (“March 10, 2025, …”) o bien usar formato ISO “2025-03-10” para coherencia con el front-matter.
docs/troubleshooting/deployment-image-not-updating-develop-branch.mdx (2)
14-17: Fecha sin comaMismo detalle de estilo: “December 19, 2024” → “December 19, 2024,” o formato ISO.
55-63: Cache bust enCOPY . /app– añade.dockerignoreAunque se sugiere dividir el
COPY, también conviene recordar incluir un.dockerignoreadecuado; de lo contrario se invalidará la cache con archivos irrelevantes (logs, node_modules) y las builds tardarán más.docs/troubleshooting/docker-build-cache-no-cache-option.mdx (2)
68-79: Script de descarga en tiempo de ejecución: cuidado con seguridad y arranqueMover la descarga a
CMDalarga el tiempo de cold-start y expone al contenedor a fallos de red en producción. Considera usar un entrypoint que reintente o bien mantener descarga en build pero con capa de bust cache (ARG+RUN --mount=type=cache).
146-163: Hoja de ruta: enlaza issue o milestoneSe mencionan características futuras (
--flush-cache, detección automática). Añade enlace al roadmap o ticket público para que la documentación no quede desactualizada ni genere expectativa falsa.docs/troubleshooting/database-performance-optimization.mdx (2)
14-17: Formato de fecha“January 15, 2024” sin coma; aplica mismo criterio que en otros docs para consistencia.
85-92: YAML de ejemplo: comenta los valores sensiblesEn el bloque YAML ejemplar se usan claves reales (
max_connections,connection_timeout). Para evitar que usuarios copien ciegamente valores inadecuados, añade comentario aclarando que son valores de ejemplo que deben ajustarse según carga.docs/troubleshooting/dependency-connection-timeout-mysql-redis.mdx (1)
63-70: Mensaje informal “a las piñas”La frase “en SleakOps arreglamos los conflictos a las piñas” no aparece en este documento, pero recuerda evitar coloquialismos similares dentro de documentación técnica orientada a clientes empresa.
docs/troubleshooting/build-status-discrepancy-lens-vs-platform.mdx (1)
14-14: Falta la coma después del año en fechas anglosajonasSi decides mantener el formato “Month DD, YYYY”, añade la coma final:
-**Date:** January 15, 2024 +**Date:** January 15, 2024,No es crítico, pero evita alertas de linters.
Also applies to: 169-169
docs/troubleshooting/deployment-stuck-state-resolution.mdx (2)
48-56: Ortografía: “resolutio” → “resolution”Se escapó una palabra mal escrita en la línea que describe la resolución inmediata.
-The resolutio typically involves: +The resolution typically involves:
14-14: Coma ausente tras el año en la fechaAñade la coma o usa el formato español.
Also applies to: 181-181
docs/troubleshooting/cluster-kubernetes-upgrade-process.mdx (2)
95-113: Comando largo conxargspuede colgarse en clusters grandesAl iterar recursos con
kubectl api-resources ... | xargs, si hay miles de CRDs saldrá muy lento. Sugiero limitar por namespace o usar--chunk-size=0para optimizar.
14-14: Añadir coma en fechas o usar formato españolIgual observación que en otros documentos.
Also applies to: 168-168
docs/troubleshooting/database-typeorm-ssl-connection-error.mdx (1)
14-14: Falta coma después del año en la fechaMismo detalle menor.
docs/troubleshooting/deployment-helm-selector-immutable-error.mdx (1)
14-14: Coma en la fecha o formato localConsistencia de fechas.
Also applies to: 181-181
docs/troubleshooting/cluster-eks-upgrade-schedule-process.mdx (1)
14-16: Falta una coma tras el año en la marca de fecha
Para mantener coherencia editorial y evitar alertas de linting, añade una coma después de “2025”.-**Date:** February 6, 2025 +**Date:** February 6, 2025,Haz lo mismo en la nota de generación automática al final del documento.
Also applies to: 147-147
docs/troubleshooting/cluster-lens-connection-timeout.mdx (1)
119-128: Uso detelnet: considerar alternativa más disponible
telnetsuele no estar instalado por defecto en muchas distros modernas. Reemplazar pornc -vzocurl --connect-timeouthace la guía más universal.-# Check if cluster endpoint is reachable -telnet your-cluster-endpoint.eks.amazonaws.com 443 +# Comprobar si el endpoint responde +nc -vz your-cluster-endpoint.eks.amazonaws.com 443docs/troubleshooting/cluster-eks-upgrade-volume-attachment-issue.mdx (1)
14-16: Añadir coma tras el año
Pequeña corrección de estilo para cumplir las reglas de LanguageTool.-**Date:** December 19, 2024 +**Date:** December 19, 2024,docs/troubleshooting/deployment-build-failed-production.mdx (1)
72-76: Placeholder de token en ejemplocurl— añadir advertencia clara
Los lectores podrían copiar/pegar sin sustituirYOUR_TOKEN, exponiendo tokens reales en shells de historial. Agrega una nota o comenta la línea.-Authorization: Bearer YOUR_TOKEN +# ⚠️ Sustituye YOUR_TOKEN por un token válido antes de ejecutar +Authorization: Bearer <TU_TOKEN_AQUÍ>docs/troubleshooting/aws-cost-monitoring-and-optimization.mdx (1)
14-16: Estilo de fecha: coma posterior al año
Añade la coma para evitar alertas de estilo.-**Date:** January 16, 2025 +**Date:** January 16, 2025,Aplica lo mismo en la nota de generación automática.
Also applies to: 197-197
docs/troubleshooting/cluster-node-errors-web-api-unavailable.mdx (1)
1-8:sidebar_position: 3repetido en todo el directorioTodos los nuevos artículos usan la misma posición
3; Docusaurus mostrará solo uno en ese lugar y esconderá el resto, o forzará orden impredecible.
Asigna posiciones únicas (1, 2, 3, …) o deja que Docusaurus las ordene alfabéticamente eliminando la clave.docs/troubleshooting/cluster-manual-shutdown-scheduled-feature.mdx (2)
3-4: Título poco natural / traducción pendiente“Cluster Manual Shutdown Requires Scheduled Feature” suena forzado en inglés y no está en español.
Propuesta (es-ES):title: "El apagado manual del clúster requiere la función de apagado programado"
38-41: Duplicación de la expresión “requires Scheduled”Aquí se repite el problema lingüístico detectado por LanguageTool. Ajustar la redacción mejorará la claridad.
docs/troubleshooting/deployment-pending-nodepool-changes.mdx (1)
60-77: Ejemplo YAML: recordar unidades de memoriaLas unidades
"512Mi"y"1024Mi"están correctas, pero en entornos mixtos se ha visto confusión con"MB". Podría valer la pena aclararlo con un comentario.docs/troubleshooting/database-migration-data-integrity-issues.mdx (1)
52-61: Consulta SQL compleja: cuidado con elxpathy privilegiosEl uso de
query_to_xmlyxpathrequiere permisos elevados y puede ser costoso en bases grandes. Para conteos rápidos suele bastar conSELECT relname, n_live_tup FROM pg_stat_user_tables;
Valora simplificar la consulta o advertir sobre su coste.docs/troubleshooting/cluster-upgrade-maintenance-scheduling.mdx (1)
59-63: “Advance Notice” → español / brevedadSi la guía será en español, cambia a “Aviso previo”. Además, el término es más corto y evita la alerta de wordiness.
docs/troubleshooting/cluster-nodepool-missing-after-shutdown.mdx (1)
14-16: Coma ausente tras el año
February 20, 2025debería ir entre comas según convenciones de estilo: “February 20, 2025,”. Es un detalle menor, pero mantiene la coherencia entre documentos.docs/troubleshooting/database-postgresql-restore-errors.mdx (1)
14-16: Falta coma tras el año
Añade la coma tras “January 15, 2024,” para mantener el estilo uniforme.docs/troubleshooting/build-pods-stuck-creation.mdx (1)
14-16: Detalle de puntuación
Inserta la coma: “March 22, 2025,”.docs/troubleshooting/dns-propagation-public-deployment.mdx (2)
14-16: Coma de estilo faltante
Agrega la coma tras “December 10, 2024,”.
26-27: Uso de “not accessible”
LanguageTool sugiere reemplazar “not accessible” por “inaccesible” para evitar la perífrasis en inglés; aplica si deseas pulir el texto.docs/troubleshooting/deployment-missing-tolerations-after-nodepool-changes.mdx (1)
14-16: Añadir coma tras el año
“March 5, 2025,” mantiene el estilo consistente.docs/troubleshooting/dns-migration-donweb-to-aws.mdx (1)
1-3:sidebar_positionduplicado en toda la carpeta
Todos los nuevos docs usansidebar_position: 3. Docusaurus resuelve empates por nombre de archivo, dando un orden impredecible. Asigna posiciones únicas o elimínalo para dejar que el orden sea alfabético.docs/troubleshooting/cluster-addons-after-migration.mdx (1)
14-14: Coma después del año
Según la guía de estilo en inglés debería ser “October 15, 2024”. Aplica si mantenemos la parte inglesa.docs/troubleshooting/deployment-newrelic-pkg-resources-warning.mdx (1)
76-83:pip installcon ambas flags en la misma línea puede generar orden inesperado
Mejor instala primero Setuptools y luego el resto para garantizar que la versión antigua quede fija:RUN pip install "setuptools<81" \ && pip install -r requirements.txtdocs/troubleshooting/cluster-understanding-ec2-instances-and-costs.mdx (1)
14-17: Coma faltante tras el añoPor coherencia con el resto de la docs, pon una coma después de “2025” para que quede “January 29, 2025, Category…”.
-**Date:** January 29, 2025 +**Date:** January 29, 2025,docs/troubleshooting/cluster-connection-troubleshooting.mdx (1)
14-17: Añade la coma tras el añoMismo detalle de estilo: “December 19, 2024,”. Mantengamos la consistencia y que no parezca que escribimos las fechas a las piñas.
docs/troubleshooting/deployment-environment-variables-migration-issues.mdx (1)
70-77: Evita sobrescribir variables si vienen vacíasCon
ENV VAR=${VAR}se propaga una cadena vacía. Añade fallback para que no haya builds “a las piñas” por valores missing.-ENV API_ENDPOINT=${API_ENDPOINT} -ENV DATABASE_URL=${DATABASE_URL} +ENV API_ENDPOINT=${API_ENDPOINT:-http://localhost} +ENV DATABASE_URL=${DATABASE_URL:-postgres://localhost/db}docs/troubleshooting/database-restore-pod-management.mdx (1)
14-17: Coma de cortesíaAñade coma tras “2025” para mantener formato uniforme.
docs/troubleshooting/database-migration-heroku-to-aws-rds.mdx (2)
168-175:TargetTablePrepMode: DROP_AND_CREATEes destructivoEn migraciones con CDC lo recomendado es
TRUNCATE_BEFORE_LOADpara evitar recrear PK, índices y constraints, reduciendo riesgos “a las piñas”.-"TargetTablePrepMode": "DROP_AND_CREATE", +"TargetTablePrepMode": "TRUNCATE_BEFORE_LOAD",
48-52: Aclarar que Heroku cifra el dumpAñade una nota sobre la opción
--no-owner --no-acl --format=custompara que los usuarios no queden con unpg_restorefallando por permisos.docs/troubleshooting/deployment-build-failures-during-updates.mdx (1)
62-70: Añade referencia directa al status page para agilizar el diagnóstico.Sería útil incluir la URL oficial del status page en el bloque de comandos o en el listado, para que el usuario no tenga que buscarla.
-3. **Check platform status**: Monitor SleakOps status page or notifications +3. **Check platform status**: Visita https://status.sleakops.com o las notificaciones internasdocs/troubleshooting/database-maintenance-window-strategies.mdx (2)
252-268: Uso de APIs internas del poolmysql: riesgo de roturas en futuras versiones.Las propiedades
_allConnections,_freeConnections,_connectionQueuey_acquiringConnectionsno están documentadas y pueden cambiar sin aviso.
Recomendación: obtén la métrica mediantepool.getConnection()o consultaSHOW STATUS LIKE 'Threads_%'para MySQL.
52-56: Gramática: comilla simple en “doesn't” causa advertencias de lint en proyectos i18n.Conviene evitar contracciones en texto técnico para mejorar la traducción automática y la claridad.
-Since SleakOps doesn't currently provide a built-in maintenance window feature, you can implement this at the application level: +Since SleakOps **does not** currently provide a built-in maintenance window feature, you can implement this at the application level:docs/troubleshooting/cluster-production-check-node-scaling.mdx (2)
52-54: Redundancia léxica: “Adds an additional node”.“Adds a node” es suficiente y evita la repetición.
-- Adds an additional node to the core node group in a different availability zone +- Adds a node to the core node group in a different availability zone
86-92: Matiz de coste mal expresado.Decir que “el coste puede ser similar pese a más nodos” puede confundir. Aclara que la reducción viene de usar instancias Graviton más baratas.
docs/troubleshooting/cluster-production-mode-spot-instances.mdx (2)
94-98: Ordena las taints por tipo para facilitar la lectura.Agrupar primero On-Demand y luego Spot (o viceversa) ayuda a localizar el valor correcto.
76-84: Ejemplo YAML: faltan comillas para valores no estándar.Valores como
spotuon-demandpueden interpretarse como boolean/string según el linter YAML. Mejor asegurar comillas.-instance_type: spot +instance_type: "spot"docs/troubleshooting/cluster-prometheus-memory-issues.mdx (1)
2-2:sidebar_positionrepetido en varias páginas – dale un número único.Todas las guías nuevas usan
sidebar_position: 3. Docusaurus ordena los ítems por ese valor y, si se repite, el resultado puede ser impredecible o pisarse con otras entradas. Asigná un número distinto para evitar el bolonqui en la sidebar.docs/troubleshooting/build-newrelic-pkg-resources-deprecation-warning.mdx (2)
2-2:sidebar_positionclonado: generá posiciones únicas.Mismo problema que en otras páginas: todos con
3. Cambialo para que el orden sea estable.
33-34: Typo menor en bullet de setuptools.Falta la “L” inicial en “Likely” si la idea era empezar en mayúscula. No rompe nada, pero queda prolijo.
docs/troubleshooting/deployment-redis-communication-error.mdx (1)
2-2:sidebar_positionduplicado otra vez.Asignale otro valor para que la sidebar no se arme un pogo brutal.
docs/troubleshooting/deployment-old-pods-not-terminating.mdx (2)
2-2: Evitar colisión desidebar_position.Todas las guías no pueden compartir el
3; elegí un número secuencial para cada una.
45-56: Este bloque se está poniendo larguísimo: considerá subdividir.El apartado “root cause” incluye 5 puntos extensos dentro de un solo
TroubleshootingItem. Dividir en sub-items hace la lectura más liviana y evita que los usuarios se pierdan en el scroll.docs/troubleshooting/deployment-migration-hooks-troubleshooting.mdx (1)
2-2: Otrosidebar_position: 3– necesitamos variedad.Cambialo por un valor distinto para que la navegación no se vuelva caótica.
docs/troubleshooting/cluster-nodepool-memory-limit-deployment-failure.mdx (1)
223-226: Pie de página desactualizadoSe menciona “This FAQ...” cuando el documento es de troubleshooting; genera confusión de categoría.
-_This FAQ was automatically generated on March 13, 2024 based on a real user query._ +_Este artículo de troubleshooting fue generado automáticamente el 13 de marzo de 2024 a partir de una consulta real._docs/troubleshooting/connecting-to-cluster-with-lens.mdx (1)
205-206: Año inconsistente entre front-matter y pie de páginaEl front-matter indica 2024 pero el pie pone 2025. Decide uno para no marear a los lectores.
-_This FAQ was automatically generated on December 19, 2025 based on a real user query._ +_Este artículo de troubleshooting fue generado automáticamente el 19 de diciembre de 2024 a partir de una consulta real._docs/troubleshooting/deployment-stuck-creating-status.mdx (1)
55-64: Bloque de código sin sintaxis explícitaEl bloque
bashtermina, pero no se cierra con una etiqueta de idioma en el cierre, lo que a veces provoca resaltado parcial cuando se usa MDX + Prism. Añadebashtambién en el cierre o usa triple backtick con el idioma una sola vez.docs/troubleshooting/dns-cloudflare-route53-configuration.mdx (2)
70-78: Añadir lenguaje al snippet para un resaltado correctoEl bloque:
Type: CNAME ...carece de identificador (
yaml,text, etc.). Esto hace que Prism lo trate como texto plano.
Recomiendo envolverlo con ```yaml para mantener estilo uniforme.
14-14: Fecha con coma: coherencia editorial
December 19, 2024→ falta la coma tras el año según guía interna de estilo; varios lintings ya lo marcan.docs/troubleshooting/cost-analysis-and-resource-optimization.mdx (1)
22-24: Fecha sin coma: coherenciaAñade coma tras el año como en el resto del portal.
docs/troubleshooting/database-performance-sql-query-optimization.mdx (1)
165-171: Pool size y límites: señala que son valores genéricosLos números 20/100 pueden ser demasiado altos para instancias pequeñas. Agrega nota para calibrar según
max_connectionsde la DB.docs/troubleshooting/deployment-stuck-starting-state.mdx (1)
51-57: Paso 2 y 3 redundantes“Wait for manual unlock” + “Verify status” suelen ser parte de la misma acción post-soporte. Considera fusionarlos para reducir verbosidad.
docs/troubleshooting/cluster-upgrade-zero-downtime.mdx (1)
14-16: Coma de cortesía después del año.Para coherencia editorial (y evitar futuros lints), agrega una coma tras la fecha:
-**Date:** February 19, 2025 +**Date:** February 19, 2025,Nada crítico, solo mantener estilo uniforme antes de que la style-bot nos venga a las piñas.
docs/troubleshooting/deployment-timeout-database-migrations.mdx (1)
14-16: Añadir coma tras el año para consistencia.Mismo detalle de estilo que en otros docs:
-**Date:** April 25, 2024 +**Date:** April 25, 2024,Pequeño nit, pero suma pulirlo ahora y no después a las piñas.
docs/troubleshooting/database-restore-pod-procedures.mdx (1)
14-16: Coma faltante tras el año.Igual que en los demás archivos:
-**Date:** March 21, 2024 +**Date:** March 21, 2024,
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (85)
docs/troubleshooting/_category_.json(1 hunks)docs/troubleshooting/api-access-troubleshooting-private-services.mdx(1 hunks)docs/troubleshooting/aws-cost-monitoring-and-optimization.mdx(1 hunks)docs/troubleshooting/aws-ec2-public-ip-assignment.mdx(1 hunks)docs/troubleshooting/aws-marketplace-login-setup-issue.mdx(1 hunks)docs/troubleshooting/aws-waf-application-load-balancer-protection.mdx(1 hunks)docs/troubleshooting/build-newrelic-pkg-resources-deprecation-warning.mdx(1 hunks)docs/troubleshooting/build-pods-stuck-creation.mdx(1 hunks)docs/troubleshooting/build-status-discrepancy-lens-vs-platform.mdx(1 hunks)docs/troubleshooting/celery-beat-duplicate-execution.mdx(1 hunks)docs/troubleshooting/ci-cd-build-stage-failure.mdx(1 hunks)docs/troubleshooting/ci-cd-github-actions-not-triggering.mdx(1 hunks)docs/troubleshooting/ci-cd-pipeline-setup-troubleshooting.mdx(1 hunks)docs/troubleshooting/cicd-pip-to-pipx-installation.mdx(1 hunks)docs/troubleshooting/cloudfront-existing-s3-bucket.mdx(1 hunks)docs/troubleshooting/cluster-addons-after-migration.mdx(1 hunks)docs/troubleshooting/cluster-automatic-shutdown-startup-issues.mdx(1 hunks)docs/troubleshooting/cluster-aws-vcpu-quota-limit.mdx(1 hunks)docs/troubleshooting/cluster-connection-troubleshooting.mdx(1 hunks)docs/troubleshooting/cluster-critical-addons-node-failure.mdx(1 hunks)docs/troubleshooting/cluster-eks-spot-instances-unavailable.mdx(1 hunks)docs/troubleshooting/cluster-eks-upgrade-schedule-process.mdx(1 hunks)docs/troubleshooting/cluster-eks-upgrade-volume-attachment-issue.mdx(1 hunks)docs/troubleshooting/cluster-kubernetes-upgrade-process.mdx(1 hunks)docs/troubleshooting/cluster-lens-connection-timeout.mdx(1 hunks)docs/troubleshooting/cluster-manual-shutdown-scheduled-feature.mdx(1 hunks)docs/troubleshooting/cluster-node-errors-web-api-unavailable.mdx(1 hunks)docs/troubleshooting/cluster-nodepool-memory-limit-deployment-failure.mdx(1 hunks)docs/troubleshooting/cluster-nodepool-missing-after-shutdown.mdx(1 hunks)docs/troubleshooting/cluster-production-check-node-scaling.mdx(1 hunks)docs/troubleshooting/cluster-production-mode-spot-instances.mdx(1 hunks)docs/troubleshooting/cluster-prometheus-memory-issues.mdx(1 hunks)docs/troubleshooting/cluster-understanding-ec2-instances-and-costs.mdx(1 hunks)docs/troubleshooting/cluster-upgrade-maintenance-scheduling.mdx(1 hunks)docs/troubleshooting/cluster-upgrade-zero-downtime.mdx(1 hunks)docs/troubleshooting/connecting-to-cluster-with-lens.mdx(1 hunks)docs/troubleshooting/cors-configuration-troubleshooting.mdx(1 hunks)docs/troubleshooting/cost-analysis-and-resource-optimization.mdx(1 hunks)docs/troubleshooting/cronjob-timezone-deployment-behavior.mdx(1 hunks)docs/troubleshooting/database-credentials-access.mdx(1 hunks)docs/troubleshooting/database-maintenance-window-strategies.mdx(1 hunks)docs/troubleshooting/database-migration-data-integrity-issues.mdx(1 hunks)docs/troubleshooting/database-migration-environment-variables.mdx(1 hunks)docs/troubleshooting/database-migration-heroku-to-aws-rds.mdx(1 hunks)docs/troubleshooting/database-migrations-execution-hooks.mdx(1 hunks)docs/troubleshooting/database-performance-optimization.mdx(1 hunks)docs/troubleshooting/database-performance-sql-query-optimization.mdx(1 hunks)docs/troubleshooting/database-postgresql-restore-errors.mdx(1 hunks)docs/troubleshooting/database-restore-pod-management.mdx(1 hunks)docs/troubleshooting/database-restore-pod-procedures.mdx(1 hunks)docs/troubleshooting/database-typeorm-ssl-connection-error.mdx(1 hunks)docs/troubleshooting/dependencies-monitoring-graphs-not-displaying.mdx(1 hunks)docs/troubleshooting/dependency-connection-timeout-mysql-redis.mdx(1 hunks)docs/troubleshooting/deployment-automatic-updates-github.mdx(1 hunks)docs/troubleshooting/deployment-build-failed-production.mdx(1 hunks)docs/troubleshooting/deployment-build-failures-during-updates.mdx(1 hunks)docs/troubleshooting/deployment-environment-variables-migration-issues.mdx(1 hunks)docs/troubleshooting/deployment-fargate-vcpu-quota-limit.mdx(1 hunks)docs/troubleshooting/deployment-helm-selector-immutable-error.mdx(1 hunks)docs/troubleshooting/deployment-image-not-updating-develop-branch.mdx(1 hunks)docs/troubleshooting/deployment-migration-hooks-troubleshooting.mdx(1 hunks)docs/troubleshooting/deployment-missing-tolerations-after-nodepool-changes.mdx(1 hunks)docs/troubleshooting/deployment-newrelic-pkg-resources-warning.mdx(1 hunks)docs/troubleshooting/deployment-old-pods-not-terminating.mdx(1 hunks)docs/troubleshooting/deployment-pending-nodepool-changes.mdx(1 hunks)docs/troubleshooting/deployment-redis-communication-error.mdx(1 hunks)docs/troubleshooting/deployment-service-name-length-limit.mdx(1 hunks)docs/troubleshooting/deployment-stuck-creating-status.mdx(1 hunks)docs/troubleshooting/deployment-stuck-starting-state.mdx(1 hunks)docs/troubleshooting/deployment-stuck-state-resolution.mdx(1 hunks)docs/troubleshooting/deployment-teams-instances-not-creating.mdx(1 hunks)docs/troubleshooting/deployment-timeout-database-migrations.mdx(1 hunks)docs/troubleshooting/django-celery-appregistrynotready-error.mdx(1 hunks)docs/troubleshooting/django-migration-conflicts-database-import.mdx(1 hunks)docs/troubleshooting/dns-cloudflare-route53-configuration.mdx(1 hunks)docs/troubleshooting/dns-delegation-route53-domain-configuration.mdx(1 hunks)docs/troubleshooting/dns-delegation-ssl-certificate-validation.mdx(1 hunks)docs/troubleshooting/dns-domain-delegation-cloudflare-route53.mdx(1 hunks)docs/troubleshooting/dns-migration-donweb-to-aws.mdx(1 hunks)docs/troubleshooting/dns-propagation-public-deployment.mdx(1 hunks)docs/troubleshooting/dns-resolution-failure-mysql-redis.mdx(1 hunks)docs/troubleshooting/docker-build-cache-issues.mdx(1 hunks)docs/troubleshooting/docker-build-cache-no-cache-option.mdx(1 hunks)docs/troubleshooting/docker-build-environment-variables.mdx(1 hunks)docs/troubleshooting/docker-daphne-logging-configuration.mdx(1 hunks)
🧠 Learnings (1)
📓 Common learnings
Learnt from: agustinoli
PR: sleakops/docs#85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento `docs/project/dependency/index.mdx`, la numeración de los pasos es correcta y no necesita cambios.
🪛 LanguageTool
docs/troubleshooting/cluster-manual-shutdown-scheduled-feature.mdx
[style] ~12-~12: The double modal “Requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...m"; # Cluster Manual Shutdown Requires Scheduled Feature Date: December 12, 2024 ...
(NEEDS_FIXED)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...heduled Feature Date: December 12, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...xt:** Users want to manually stop their SleakOps cluster at specific times (for testing,...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~89-~89: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...y stop the cluster 4. Start the cluster manually when needed 5. No predefined schedule r...
(ADVERB_REPETITION_PREMIUM)
[style] ~135-~135: The double modal “requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...Behavior:** - Manual shutdown requires Scheduled Shutdown feature enabled - Background m...
(NEEDS_FIXED)
[style] ~167-~167: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 12, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/ci-cd-build-stage-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ld Stage Failure Date: October 10, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...correctly configured: 1. Access your SleakOps project dashboard 2. **Navigate to th...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...rigger a fresh build: Option 1: From SleakOps Dashboard 1. Go to your project in SleakOps 2....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...s Dashboard** 1. Go to your project in SleakOps 2. Navigate to the Deployments section ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~179-~179: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-lens-connection-timeout.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Kubernetes Cluster Date: April 29, 2024 Category: User Tags: Lens, ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cloudfront-existing-s3-bucket.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sting S3 Bucket Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~170-~170: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-ec2-public-ip-assignment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic IPv4 Address Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...nstance within a production VPC through SleakOps but the instance doesn't receive a publ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...kOps"> If you're managing this through SleakOps, you can configure public IP assignment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~171-~171: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/build-status-discrepancy-lens-vs-platform.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...latform and Lens Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[style] ~169-~169: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cicd-pip-to-pipx-installation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tallation Method Date: October 15, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~30-~30: Ensure spelling is correct
Context: ...onfiguration:** - Installation method: pip install sleakops (incorrect) - Environment: CI/CD pipel...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~37-~37: Ensure spelling is correct
Context: ...execution - Happens specifically at the SleakOps installation step - May be related to d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~44-~44: Ensure spelling is correct
Context: ... workflow"> The solution is to replace pip install sleakops with pipx install sleakops in your C...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~44-~44: Ensure spelling is correct
Context: ... to replace pip install sleakops with pipx install sleakops in your CI/CD workflow configuration. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~188-~188: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-nodepool-missing-after-shutdown.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...luster Shutdown Date: February 20, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~53-~53: Ensure spelling is correct
Context: ...pool configuration** once restored The SleakOps team can manually restore your nodepool...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ...n the future: 1. Wait for the fix: SleakOps is working on a permanent solution 2. *...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...ary="When to contact support"> Contact SleakOps support immediately if: - Nodepools ar...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~143-~143: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 20, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-delegation-route53-domain-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...omain Providers Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not w...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...egation appears correctly configured in Route53 - Domain registrar (DonWeb) reports del...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~36-~36: Ensure spelling is correct
Context: ...AWS Certificate Manager (ACM) - Target: SleakOps deployment with Load Balancer **Error ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~155-~155: Ensure spelling is correct
Context: ...y="SleakOps Domain Configuration"> For SleakOps deployments, ensure proper domain confi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...ps Domain Settings:** - Update your SleakOps project configuration to use the custom...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~335-~335: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/ci-cd-github-actions-not-triggering.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Not Triggering Date: January 15, 2024 Category: Project Tags: Git...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...with continuous integration pipeline in SleakOps where GitHub Actions workflows stop tri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...ons with YAML configuration - Platform: SleakOps integration Error Conditions: - Pipeline work...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-aws-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ror with Karpenter Date: April 24, 2024 Category: Cluster Tags: AWS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~200-~200: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-marketplace-login-setup-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... and Setup Issue Date: January 15, 2024 Category: User Tags: AWS Ma...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...iption Context: User subscribed to SleakOps through AWS Marketplace but encounters ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ... subscribe through AWS 2. Redirect to SleakOps: AWS redirects you to our platform wi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~91-~91: Ensure spelling is correct
Context: ...AWS Marketplace** 3. Navigate to your SleakOps subscription 4. Click "Setup Product" If this works, ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~102-~102: Ensure spelling is correct
Context: ...ally link your accounts: 1. Create a SleakOps account (if you don't have one): ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...th: - Your AWS account ID - Your SleakOps account email - Your AWS Marketplace...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~135-~135: Ensure spelling is correct
Context: ...k:** - Disable ad blockers for AWS and SleakOps domains - Allow third-party cookies temporarily - ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~164-~164: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/api-access-troubleshooting-private-services.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Access Issues Date: December 19, 2024 Category: User Tags: API, V...
(MISSING_COMMA_AFTER_YEAR)
[style] ~254-~254: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-delegation-ssl-certificate-validation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...idation Issues Date: September 10, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...ecords - Records should point to AWS Route53 name servers <...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-connection-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...nnection Issues Date: December 19, 2024 Category: Cluster Tags: Con...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps Kubernetes cluster - Required tools: ku...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~156-~156: Ensure spelling is correct
Context: ...ails, try these alternatives: 1. Use SleakOps Web Terminal: - Access cluster throu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~158-~158: Ensure spelling is correct
Context: ...rminal:** - Access cluster through the SleakOps web interface - Use the built-in termin...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~230-~230: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-nodepool-memory-limit-deployment-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pool Memory Limits Date: March 13, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ...solve the immediate issue: 1. Access SleakOps Dashboard 2. Navigate to Cluster Management → **N...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...nitor your cluster resources: 1. Use SleakOps Nodepool Dashboard: - Check CPU/M...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~225-~225: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 13, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-node-errors-web-api-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e to Node Errors Date: January 15, 2024 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps Kubernetes cluster - Affected services:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-newrelic-pkg-resources-warning.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sources Warning Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~21-~21: Ensure spelling is correct
Context: ...oy a Python project to production using SleakOps CLI but encounters build failures relat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~134-~134: Consider using a different verb for a more formal wording.
Context: ...only suppresses the warning but doesn't fix the underlying issue. </Troubleshootin...
(FIX_RESOLVE)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-migration-data-integrity-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ntegrity Issues Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~256-~256: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/django-celery-appregistrynotready-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...yNotReady Error Date: December 26, 2024 Category: Workload Tags: Dj...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider changing the order of words to improve your wording.
Context: ... execute properly - Application appears to not be fully initialized when Celery tasks ...
(TO_NOT_VB)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ery -A (App) call function` - Platform: SleakOps Error Conditions: - Error occurs ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~143-~143: Ensure spelling is correct
Context: ...ps: {settings.INSTALLED_APPS}") ``` In SleakOps, ensure your environment variables are ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ..."SleakOps specific configuration"> For SleakOps deployments, ensure your worker configu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~212-~212: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 26, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-domain-delegation-cloudflare-route53.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 21, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...on: Requires proper domain delegation - SleakOps validation: Checks delegation once duri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...anding SleakOps DNS Management"> How SleakOps manages DNS: 1. **Centralized Manage...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~50-~50: Ensure spelling is correct
Context: ... DNS:** 1. Centralized Management: SleakOps centralizes all DNS management in your ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...ords:** - All DNS records generated by SleakOps are visible in the platform - Records i...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~59-~59: Ensure spelling is correct
Context: ...- Records are automatically managed for SleakOps services **For proper functionality, domains must b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ... Route53 nameservers 2. Subdomains of SleakOps-managed domains: Created as subdomain...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...*: Delegate only specific subdomains to Route53 # In CloudFlare, create NS records for subdomains: app.yourdomain.com NS ns-xxx.awsdns-xx.com app.yourdomain.com NS ns-xxx.awsdns-xx.co.uk app.yourdomain.com NS ns-xxx.awsdns-xx.net app.yourdomain.com NS ns-xxx.awsdns-xx.org 2. Use SleakOps subdomains: Create all Sl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...S ns-xxx.awsdns-xx.org ``` 2. Use SleakOps subdomains: Create all SleakOps servi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...Use SleakOps subdomains: Create all SleakOps services under a dedicated subdomain ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/deployment-old-pods-not-terminating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ods Not Terminating Date: June 10, 2024 Category: Workload Tags: De...
(MISSING_COMMA_AFTER_YEAR)
[style] ~604-~604: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-image-not-updating-develop-branch.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ges After Merge Date: December 19, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...: Git merge/push to develop - Platform: SleakOps automated deployment **Error Condition...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...y="Force a complete rebuild"> To force SleakOps to rebuild without cache: 1. Go to you...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-eks-upgrade-volume-attachment-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Orphaned Volume Date: December 19, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...mon issue when volumes are removed from SleakOps configuration but the underlying AWS EB...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~60-~60: Consider using a different verb for a more formal wording.
Context: ...ow to resolve the upgrade failure"> To fix the upgrade issue: 1. **Identify the p...
(FIX_RESOLVE)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...ume removal**: When removing volumes in SleakOps, ensure they are properly detached: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/dns-resolution-failure-mysql-redis.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dis Connections Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-critical-addons-node-failure.mdx
[grammar] ~13-~13: Ensure spelling is correct
Context: ...tures/troubleshootingitem"; # Critical Addons Node Failure in Production Date: J...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...re in Production Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~83-~83: Ensure spelling is correct
Context: ...t high availability: 1. Enable HA in SleakOps Dashboard - Go to Cluster Settings - Navigate to ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~134-~134: Ensure spelling is correct
Context: ...gainst zone-level failures - Ensures addon availability during outages 4. **Monit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-performance-sql-query-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ry Optimization Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-maintenance-window-strategies.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...indow Strategies Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...ication-Level Maintenance Mode"> Since SleakOps doesn't currently provide a built-in ma...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~524-~524: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-eks-spot-instances-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...degroup Creation Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~210-~210: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-migration-heroku-to-aws-rds.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...roku to AWS RDS Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~442-~442: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-performance-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tion and Scaling Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-helm-selector-immutable-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Immutable Error Date: December 19, 2024 Category: Workload Tags: He...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with Kubernetes cluster - Deployment to...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~60-~60: Ensure spelling is correct
Context: ... delete the existing deployment and let SleakOps recreate it: **Using Lens (Kubernetes ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~181-~181: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-fargate-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ring Deployment Date: February 13, 2025 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-teams-instances-not-creating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ces Not Creating Date: January 15, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Domain: teams.simplee.cl - Platform: SleakOps - Deployment type: Teams instances **E...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...en to escalate the issue"> Escalate to SleakOps support if: 1. **Infrastructure Issues...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~282-~282: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deep cluster analy...
(DEEP_PROFOUND)
[style] ~453-~453: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-migration-hooks-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ployment Issues Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps deployment system - Hook type: Database...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/build-newrelic-pkg-resources-deprecation-warning.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Deprecation Warning Date: June 10, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ikely 81 or higher - Build environment: SleakOps managed containers **Error Conditions:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~192-~192: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cors-configuration-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Troubleshooting Date: December 19, 2024 Category: Workload Tags: CO...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~48-~48: Ensure spelling is correct
Context: ..., meaning: - Infrastructure Level: SleakOps load balancers and ingress controllers ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~208-~208: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 25, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-build-cache-no-cache-option.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Build Arguments Date: February 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...When changing Docker build arguments in SleakOps projects, the build process may use cac...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~49-~49: Ensure spelling is correct
Context: ...thout using cache. Current Status in SleakOps: - The platform is being prepared to ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~147-~147: Ensure spelling is correct
Context: ... summary="Upcoming SleakOps features"> SleakOps is developing enhanced build control fe...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-restore-pod-procedures.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...in Pod Environment Date: March 21, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-stuck-state-resolution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Pending State Date: December 28, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...counter a stuck deployment, contact the SleakOps support team immediately. The resolutio...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~124-~124: Ensure spelling is correct
Context: ...n to escalate to support"> Escalate to SleakOps support when: **Immediate Escalation R...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/deployment-pending-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Nodepool Changes Date: January 23, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/celery-beat-duplicate-execution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Task Execution Date: December 23, 2024 Category: Workload Tags: Ce...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...egrated within backend pods - Platform: SleakOps Kubernetes environment - Workload type:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~41-~41: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...s for scheduled tasks - Tasks execute N times where N = number of backend pod replicas ## ...
(WHEN_WHERE)
[grammar] ~81-~81: Ensure spelling is correct
Context: ... Step 2: Create CronJob Executions in SleakOps For each Celery Beat task, create a ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...ob execution: 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~287-~287: Ensure spelling is correct
Context: ...All CronJobs are created and visible in SleakOps - [ ] CronJob schedules match the original...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~367-~367: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dependencies-monitoring-graphs-not-displaying.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Not Displaying Date: January 22, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...dependencies (RDS, OpenSearch, etc.) in SleakOps, the monitoring page loads but the usag...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~92-~92: Ensure spelling is correct
Context: ...ummary="Platform fix in progress"> The SleakOps team is working on a comprehensive solu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/cluster-production-mode-spot-instances.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Instance Types Date: December 19, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-daphne-logging-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...hne Applications Date: January 21, 2025 Category: Workload Tags: Do...
(MISSING_COMMA_AFTER_YEAR)
[style] ~345-~345: Try moving the adverb to make the sentence clearer.
Context: ...uration for logging"> Configure Docker Compose to properly handle Daphne logs: ```yaml version: '3.8' services: w...
(SPLIT_INFINITIVE)
[style] ~553-~553: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 21, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dependency-connection-timeout-mysql-redis.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Timeout Issues Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...: Restart the affected service** 1. In SleakOps dashboard, go to your project 2. Find t...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/ci-cd-pipeline-setup-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ing on Branch Push Date: March 14, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...y: Git-based source control - Pipeline: SleakOps CI/CD integration - Expected behavior: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~104-~104: Ensure spelling is correct
Context: ...n: 1. Go to Settings > CLI in your SleakOps dashboard 2. Generate or copy your API key 3. In your...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~189-~189: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-automatic-shutdown-startup-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Startup Issues Date: February 14, 2025 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~231-~231: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 14, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-upgrade-zero-downtime.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...h Zero Downtime Date: February 19, 2025 Category: Cluster Tags: Upg...
(MISSING_COMMA_AFTER_YEAR)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 19, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-stuck-starting-state.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Starting State Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-build-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...bles Not Available Date: March 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~20-~20: Consider using “inaccessible” to avoid wordiness.
Context: ...defined in SleakOps Docker settings are not accessible during the build process, specifically ...
(NOT_ABLE_PREMIUM)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ockerfile"> Environment variables from SleakOps settings are only available at runtime,...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...igure build arguments in SleakOps"> In SleakOps, you need to configure build arguments ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~194-~194: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cronjob-timezone-deployment-behavior.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...loyment Behavior Date: October 24, 2024 Category: Workload Tags: Cr...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 24, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-build-failed-production.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...g Loading Issues Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Environment: Production - Platform: SleakOps - Issue type: Build failure + Log acces...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ... dashboard log loading problems"> When SleakOps dashboard logs won't load: **Browser-r...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~127-~127: Ensure spelling is correct
Context: ...utions:** 1. Log out and log back into SleakOps 2. Check if other dashboard sections work p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~134-~134: Ensure spelling is correct
Context: ...s) If problem persists: - Contact SleakOps support with specific build ID - Provid...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-timeout-database-migrations.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...atabase Migrations Date: April 25, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~71-~71: Ensure spelling is correct
Context: ...ncrease pre-deploy timeout limits"> In SleakOps, you can configure longer timeout limit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/database-migration-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Configuration Date: December 11, 2024 Category: Project Tags: Dat...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...Entity Framework database migrations in SleakOps, specifically with PostgreSQL database ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...LLOWED_ORIGINS` - Environment variables not accessible to migration processes **Relevant Conf...
(NOT_ABLE_PREMIUM)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...k - Database: PostgreSQL - Environment: SleakOps platform - Variable Groups: Backend pro...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~455-~455: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-waf-application-load-balancer-protection.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ncer Protection Date: December 19, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Load Balancer: Application Loa...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~46-~46: Ensure spelling is correct
Context: ...rom common web exploits and bots. While SleakOps doesn't have native WAF integration yet...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[uncategorized] ~142-~142: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ority: 3 Action: Block **2. Custom Rate Limiting Rule:** yaml Rule Name: RateLimitin...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~361-~361: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-restore-pod-management.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ore Pod Management Date: March 26, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~232-~232: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 26, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-production-check-node-scaling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...esource Changes Date: November 20, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~52-~52: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...y: Node Infrastructure Changes: - Adds an additional node to the core node group in a different a...
(ADD_AN_ADDITIONAL)
[style] ~217-~217: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on November 20, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-cost-monitoring-and-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...and Optimization Date: January 16, 2025 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[uncategorized] ~58-~58: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...Deployment timing*: Partial month vs. full month billing - Multiple accounts: Costs ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 16, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-prometheus-memory-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...using Pod Hangs Date: December 23, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-propagation-public-deployment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic Deployments Date: December 10, 2024 Category: Project Tags: DNS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...when accessing the URL - Application is not accessible via the public domain **Relevant Confi...
(NOT_ABLE_PREMIUM)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-environment-variables-migration-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...le After Migration Date: April 24, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Affected environments: Develop...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...ariables"> During platform migrations, SleakOps may update how secrets and environment ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on April 24, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/connecting-to-cluster-with-lens.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...r with Lens IDE Date: December 19, 2024 Category: Cluster Tags: Len...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cost-analysis-and-resource-optimization.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ion in SleakOps Date: December 19, 2024 Category: General Tags: Cos...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-migrations-execution-hooks.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Execution Hooks Date: December 19, 2024 Category: Workload Tags: Da...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ... as part of their deployment process in SleakOps, specifically for .NET applications usi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~82-~82: Ensure spelling is correct
Context: ... Execution:** 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/build-pods-stuck-creation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in Creation State Date: March 22, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[style] ~183-~183: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 22, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-addons-after-migration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... After Migration Date: October 15, 2024 Category: Cluster Tags: Mig...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with new interface - Affected addons: L...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... SleakOps with new interface - Affected addons: Loki, Grafana, and other monitoring to...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...tion performed - Interface: Updated/new SleakOps interface Error Conditions: - Addons not vi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...available"> During cluster migrations, SleakOps temporarily deactivates addons to ensur...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...ss**: - Log into Grafana using your SleakOps credentials - Verify dashboards are displaying data ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-eks-upgrade-schedule-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dule and Process Date: February 6, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~57-~57: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...email - Specific dates are communicated prior to each upgrade <...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on February 6, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-kubernetes-upgrade-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Upgrade Process Date: December 19, 2024 Category: Cluster Tags: Kub...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ication in the Cluster section of their SleakOps dashboard and need guidance on how to p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps managed Kubernetes cluster - Environmen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...t** on the upgrade notification in your SleakOps dashboard 2. The system will automatically begin the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ocess is fully automated and managed by SleakOps. <Troubleshooti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...e upgrades Process order: 1. Core SleakOps nodes are upgraded one by one (rolling ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~83-~83: Ensure spelling is correct
Context: ...tions** in your cluster (not managed by SleakOps) - Check the Kubernetes changelog for depre...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~89-~89: Ensure spelling is correct
Context: ...pecial database preparations needed for SleakOps managed upgrades - Ensure database conn...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...r usual monitoring tools 2. Check the SleakOps dashboard for upgrade progress 3. **W...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~132-~132: Ensure spelling is correct
Context: ...r logs If issues occur: - Contact SleakOps support immediately - Provide specific ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-understanding-ec2-instances-and-costs.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in EKS Clusters Date: January 29, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 29, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-upgrade-maintenance-scheduling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ance Scheduling Date: December 19, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~59-~59: ‘Advance Notice’ might be wordy. Consider a shorter alternative.
Context: ...issues ### Communication Protocol - Advance Notice: Notify clients at least 48-72 hours ...
(EN_WORDINESS_PREMIUM_ADVANCE_NOTICE)
[style] ~247-~247: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-credentials-access.mdx
[grammar] ~12-~12: Ensure spelling is correct
Context: ...tem"; # Database Credentials Access in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ess in SleakOps Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~58-~58: Ensure spelling is correct
Context: ...roup"> To view database credentials in SleakOps: 1. Navigate to your project 2. **G...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...VarGroup** 4. View the credentials: SleakOps fetches the secret from the cluster and...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-postgresql-restore-errors.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Restore Errors Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-typeorm-ssl-connection-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Error with RDS Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-automatic-updates-github.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pdates from GitHub Date: August 2, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ory are automatically deployed to their SleakOps environment during testing phases. **O...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...- Source: GitHub repository - Platform: SleakOps - Environment: Development/Testing - Do...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...nnection:** - Go to your Project in SleakOps - Navigate to Settings → *Repository...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~87-~87: Ensure spelling is correct
Context: ... the deployment workflow"> The typical SleakOps deployment workflow: ```mermaid graph ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~201-~201: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on August 2, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-build-failures-during-updates.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Platform Updates Date: October 14, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ild process fails temporarily while the SleakOps platform undergoes maintenance or updat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...rm communications**: - Subscribe to SleakOps status updates - Check email notific...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~155-~155: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-missing-tolerations-after-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...er Nodepool Changes Date: March 5, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ... 1. Navigate to your service in the SleakOps dashboard 2. Click "Edit" on the affected deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~131-~131: Ensure spelling is correct
Context: ...odepool changes**: Coordinate with your SleakOps team before major changes 2. **Update d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on March 5, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-redis-communication-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...munication Error Date: January 15, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~62-~62: Ensure spelling is correct
Context: ...you encounter this issue: 1. Contact SleakOps Support: This is typically an infrast...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~158-~158: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-service-name-length-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...gth Limit Error Date: February 13, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~174-~174: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-stuck-creating-status.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Creating Status Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ranch and triggers a deployment through SleakOps. The build process completes successfull...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...nt type: deploy_build_dev - Platform: SleakOps - Build status: Successful - Deployment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~98-~98: Ensure spelling is correct
Context: ... to contact SleakOps support"> Contact SleakOps support if: 1. **Deployment stuck for ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~181-~181: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deployment status ...
(DEEP_PROFOUND)
[grammar] ~469-~469: Ensure spelling is correct
Context: ...ific solutions"> Solutions specific to SleakOps platform deployment issues: 1. **Sleak...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~473-~473: Ensure spelling is correct
Context: ...t state management**: - Deployments in SleakOps may get stuck due to platform state man...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~475-~475: Ensure spelling is correct
Context: ...ates - Sometimes manual intervention by SleakOps support is required to reset state 2. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~597-~597: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/django-migration-conflicts-database-import.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Database Import Date: December 20, 2024 Category: Project Tags: Dja...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...p into a Django application deployed on SleakOps, the pre-upgrade hook responsible for r...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~137-~137: Ensure spelling is correct
Context: ...Handling in SleakOps deployments"> For SleakOps deployments with pre-upgrade hooks: 1....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/dns-cloudflare-route53-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[style] ~196-~196: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-migration-donweb-to-aws.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...om DonWeb to AWS Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-build-cache-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...es in Production Date: January 15, 2024 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with Docker builds - Environment: Produ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~121-~121: Ensure spelling is correct
Context: ...s** - Review the deployment logs in SleakOps - Look for "Using cache" messages that mig...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
🪛 Gitleaks (8.27.2)
docs/troubleshooting/deployment-build-failed-production.mdx
74-74: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
(curl-auth-header)
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/troubleshooting/category.json
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: agustinoli
PR: sleakops/docs#85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento `docs/project/dependency/index.mdx`, la numeración de los pasos es correcta y no necesita cambios.
🪛 LanguageTool
docs/troubleshooting/cluster-manual-shutdown-scheduled-feature.mdx
[style] ~12-~12: The double modal “Requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...m"; # Cluster Manual Shutdown Requires Scheduled Feature Date: December 12, 2024 ...
(NEEDS_FIXED)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...heduled Feature Date: December 12, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...xt:** Users want to manually stop their SleakOps cluster at specific times (for testing,...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~89-~89: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...y stop the cluster 4. Start the cluster manually when needed 5. No predefined schedule r...
(ADVERB_REPETITION_PREMIUM)
[style] ~135-~135: The double modal “requires Scheduled” is nonstandard (only accepted in certain dialects). Consider “to be Scheduled”.
Context: ...Behavior:** - Manual shutdown requires Scheduled Shutdown feature enabled - Background m...
(NEEDS_FIXED)
[style] ~167-~167: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 12, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/ci-cd-build-stage-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ld Stage Failure Date: October 10, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...correctly configured: 1. Access your SleakOps project dashboard 2. **Navigate to th...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~93-~93: Ensure spelling is correct
Context: ...rigger a fresh build: Option 1: From SleakOps Dashboard 1. Go to your project in SleakOps 2....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...s Dashboard** 1. Go to your project in SleakOps 2. Navigate to the Deployments section ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~179-~179: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-lens-connection-timeout.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Kubernetes Cluster Date: April 29, 2024 Category: User Tags: Lens, ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cloudfront-existing-s3-bucket.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sting S3 Bucket Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~170-~170: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-ec2-public-ip-assignment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic IPv4 Address Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...nstance within a production VPC through SleakOps but the instance doesn't receive a publ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...kOps"> If you're managing this through SleakOps, you can configure public IP assignment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~171-~171: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/build-status-discrepancy-lens-vs-platform.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...latform and Lens Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[style] ~169-~169: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cicd-pip-to-pipx-installation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tallation Method Date: October 15, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~30-~30: Ensure spelling is correct
Context: ...onfiguration:** - Installation method: pip install sleakops (incorrect) - Environment: CI/CD pipel...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~37-~37: Ensure spelling is correct
Context: ...execution - Happens specifically at the SleakOps installation step - May be related to d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~44-~44: Ensure spelling is correct
Context: ... workflow"> The solution is to replace pip install sleakops with pipx install sleakops in your C...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~44-~44: Ensure spelling is correct
Context: ... to replace pip install sleakops with pipx install sleakops in your CI/CD workflow configuration. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~188-~188: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-nodepool-missing-after-shutdown.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...luster Shutdown Date: February 20, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~53-~53: Ensure spelling is correct
Context: ...pool configuration** once restored The SleakOps team can manually restore your nodepool...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ...n the future: 1. Wait for the fix: SleakOps is working on a permanent solution 2. *...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~125-~125: Ensure spelling is correct
Context: ...ary="When to contact support"> Contact SleakOps support immediately if: - Nodepools ar...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~143-~143: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 20, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-delegation-route53-domain-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...omain Providers Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ain (ordenapp.com.ar) to point to their SleakOps deployment, but DNS delegation is not w...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~24-~24: Ensure spelling is correct
Context: ...egation appears correctly configured in Route53 - Domain registrar (DonWeb) reports del...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~36-~36: Ensure spelling is correct
Context: ...AWS Certificate Manager (ACM) - Target: SleakOps deployment with Load Balancer **Error ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~155-~155: Ensure spelling is correct
Context: ...y="SleakOps Domain Configuration"> For SleakOps deployments, ensure proper domain confi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...ps Domain Settings:** - Update your SleakOps project configuration to use the custom...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~335-~335: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/ci-cd-github-actions-not-triggering.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Not Triggering Date: January 15, 2024 Category: Project Tags: Git...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...with continuous integration pipeline in SleakOps where GitHub Actions workflows stop tri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...ons with YAML configuration - Platform: SleakOps integration Error Conditions: - Pipeline work...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-aws-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ror with Karpenter Date: April 24, 2024 Category: Cluster Tags: AWS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~200-~200: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-marketplace-login-setup-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... and Setup Issue Date: January 15, 2024 Category: User Tags: AWS Ma...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...iption Context: User subscribed to SleakOps through AWS Marketplace but encounters ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ... subscribe through AWS 2. Redirect to SleakOps: AWS redirects you to our platform wi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~91-~91: Ensure spelling is correct
Context: ...AWS Marketplace** 3. Navigate to your SleakOps subscription 4. Click "Setup Product" If this works, ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~102-~102: Ensure spelling is correct
Context: ...ally link your accounts: 1. Create a SleakOps account (if you don't have one): ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~110-~110: Ensure spelling is correct
Context: ...th: - Your AWS account ID - Your SleakOps account email - Your AWS Marketplace...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~135-~135: Ensure spelling is correct
Context: ...k:** - Disable ad blockers for AWS and SleakOps domains - Allow third-party cookies temporarily - ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~164-~164: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/api-access-troubleshooting-private-services.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Access Issues Date: December 19, 2024 Category: User Tags: API, V...
(MISSING_COMMA_AFTER_YEAR)
[style] ~254-~254: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-delegation-ssl-certificate-validation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...idation Issues Date: September 10, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...ecords - Records should point to AWS Route53 name servers <...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-connection-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...nnection Issues Date: December 19, 2024 Category: Cluster Tags: Con...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps Kubernetes cluster - Required tools: ku...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~156-~156: Ensure spelling is correct
Context: ...ails, try these alternatives: 1. Use SleakOps Web Terminal: - Access cluster throu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~158-~158: Ensure spelling is correct
Context: ...rminal:** - Access cluster through the SleakOps web interface - Use the built-in termin...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~230-~230: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-nodepool-memory-limit-deployment-failure.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pool Memory Limits Date: March 13, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ...solve the immediate issue: 1. Access SleakOps Dashboard 2. Navigate to Cluster Management → **N...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...nitor your cluster resources: 1. Use SleakOps Nodepool Dashboard: - Check CPU/M...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~225-~225: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 13, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-node-errors-web-api-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e to Node Errors Date: January 15, 2024 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps Kubernetes cluster - Affected services:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-newrelic-pkg-resources-warning.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...sources Warning Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~21-~21: Ensure spelling is correct
Context: ...oy a Python project to production using SleakOps CLI but encounters build failures relat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~134-~134: Consider using a different verb for a more formal wording.
Context: ...only suppresses the warning but doesn't fix the underlying issue. </Troubleshootin...
(FIX_RESOLVE)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-migration-data-integrity-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ntegrity Issues Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~256-~256: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/django-celery-appregistrynotready-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...yNotReady Error Date: December 26, 2024 Category: Workload Tags: Dj...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider changing the order of words to improve your wording.
Context: ... execute properly - Application appears to not be fully initialized when Celery tasks ...
(TO_NOT_VB)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ery -A (App) call function` - Platform: SleakOps Error Conditions: - Error occurs ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~143-~143: Ensure spelling is correct
Context: ...ps: {settings.INSTALLED_APPS}") ``` In SleakOps, ensure your environment variables are ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ..."SleakOps specific configuration"> For SleakOps deployments, ensure your worker configu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~212-~212: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 26, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-domain-delegation-cloudflare-route53.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 21, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~35-~35: Ensure spelling is correct
Context: ...on: Requires proper domain delegation - SleakOps validation: Checks delegation once duri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...anding SleakOps DNS Management"> How SleakOps manages DNS: 1. **Centralized Manage...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~50-~50: Ensure spelling is correct
Context: ... DNS:** 1. Centralized Management: SleakOps centralizes all DNS management in your ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~57-~57: Ensure spelling is correct
Context: ...ords:** - All DNS records generated by SleakOps are visible in the platform - Records i...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~59-~59: Ensure spelling is correct
Context: ...- Records are automatically managed for SleakOps services **For proper functionality, domains must b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ... Route53 nameservers 2. Subdomains of SleakOps-managed domains: Created as subdomain...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...*: Delegate only specific subdomains to Route53 # In CloudFlare, create NS records for subdomains: app.yourdomain.com NS ns-xxx.awsdns-xx.com app.yourdomain.com NS ns-xxx.awsdns-xx.co.uk app.yourdomain.com NS ns-xxx.awsdns-xx.net app.yourdomain.com NS ns-xxx.awsdns-xx.org 2. Use SleakOps subdomains: Create all Sl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...S ns-xxx.awsdns-xx.org ``` 2. Use SleakOps subdomains: Create all SleakOps servi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~167-~167: Ensure spelling is correct
Context: ...Use SleakOps subdomains: Create all SleakOps services under a dedicated subdomain ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/deployment-old-pods-not-terminating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ods Not Terminating Date: June 10, 2024 Category: Workload Tags: De...
(MISSING_COMMA_AFTER_YEAR)
[style] ~604-~604: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-image-not-updating-develop-branch.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ges After Merge Date: December 19, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...: Git merge/push to develop - Platform: SleakOps automated deployment **Error Condition...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...y="Force a complete rebuild"> To force SleakOps to rebuild without cache: 1. Go to you...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-eks-upgrade-volume-attachment-issue.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Orphaned Volume Date: December 19, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...mon issue when volumes are removed from SleakOps configuration but the underlying AWS EB...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~60-~60: Consider using a different verb for a more formal wording.
Context: ...ow to resolve the upgrade failure"> To fix the upgrade issue: 1. **Identify the p...
(FIX_RESOLVE)
[grammar] ~112-~112: Ensure spelling is correct
Context: ...ume removal**: When removing volumes in SleakOps, ensure they are properly detached: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/dns-resolution-failure-mysql-redis.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dis Connections Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-critical-addons-node-failure.mdx
[grammar] ~13-~13: Ensure spelling is correct
Context: ...tures/troubleshootingitem"; # Critical Addons Node Failure in Production Date: J...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...re in Production Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~83-~83: Ensure spelling is correct
Context: ...t high availability: 1. Enable HA in SleakOps Dashboard - Go to Cluster Settings - Navigate to ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~134-~134: Ensure spelling is correct
Context: ...gainst zone-level failures - Ensures addon availability during outages 4. **Monit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~182-~182: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-performance-sql-query-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ry Optimization Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-maintenance-window-strategies.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...indow Strategies Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~54-~54: Ensure spelling is correct
Context: ...ication-Level Maintenance Mode"> Since SleakOps doesn't currently provide a built-in ma...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~524-~524: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-eks-spot-instances-unavailable.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...degroup Creation Date: January 15, 2024 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~210-~210: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-migration-heroku-to-aws-rds.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...roku to AWS RDS Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~442-~442: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-performance-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...tion and Scaling Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-helm-selector-immutable-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Immutable Error Date: December 19, 2024 Category: Workload Tags: He...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with Kubernetes cluster - Deployment to...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~60-~60: Ensure spelling is correct
Context: ... delete the existing deployment and let SleakOps recreate it: **Using Lens (Kubernetes ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~181-~181: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-fargate-vcpu-quota-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ring Deployment Date: February 13, 2025 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-teams-instances-not-creating.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ces Not Creating Date: January 15, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Domain: teams.simplee.cl - Platform: SleakOps - Deployment type: Teams instances **E...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~165-~165: Ensure spelling is correct
Context: ...en to escalate the issue"> Escalate to SleakOps support if: 1. **Infrastructure Issues...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~282-~282: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deep cluster analy...
(DEEP_PROFOUND)
[style] ~453-~453: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-migration-hooks-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ployment Issues Date: December 11, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps deployment system - Hook type: Database...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/build-newrelic-pkg-resources-deprecation-warning.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Deprecation Warning Date: June 10, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...ikely 81 or higher - Build environment: SleakOps managed containers **Error Conditions:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~192-~192: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on June 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cors-configuration-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Troubleshooting Date: December 19, 2024 Category: Workload Tags: CO...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~48-~48: Ensure spelling is correct
Context: ..., meaning: - Infrastructure Level: SleakOps load balancers and ingress controllers ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~208-~208: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 25, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-build-cache-no-cache-option.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Build Arguments Date: February 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...When changing Docker build arguments in SleakOps projects, the build process may use cac...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~49-~49: Ensure spelling is correct
Context: ...thout using cache. Current Status in SleakOps: - The platform is being prepared to ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~147-~147: Ensure spelling is correct
Context: ... summary="Upcoming SleakOps features"> SleakOps is developing enhanced build control fe...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-restore-pod-procedures.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...in Pod Environment Date: March 21, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-stuck-state-resolution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Pending State Date: December 28, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...counter a stuck deployment, contact the SleakOps support team immediately. The resolutio...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~124-~124: Ensure spelling is correct
Context: ...n to escalate to support"> Escalate to SleakOps support when: **Immediate Escalation R...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/deployment-pending-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Nodepool Changes Date: January 23, 2024 Category: Cluster Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/celery-beat-duplicate-execution.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Task Execution Date: December 23, 2024 Category: Workload Tags: Ce...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...egrated within backend pods - Platform: SleakOps Kubernetes environment - Workload type:...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~41-~41: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...s for scheduled tasks - Tasks execute N times where N = number of backend pod replicas ## ...
(WHEN_WHERE)
[grammar] ~81-~81: Ensure spelling is correct
Context: ... Step 2: Create CronJob Executions in SleakOps For each Celery Beat task, create a ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...ob execution: 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~287-~287: Ensure spelling is correct
Context: ...All CronJobs are created and visible in SleakOps - [ ] CronJob schedules match the original...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~367-~367: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 23, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dependencies-monitoring-graphs-not-displaying.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Not Displaying Date: January 22, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...dependencies (RDS, OpenSearch, etc.) in SleakOps, the monitoring page loads but the usag...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~92-~92: Ensure spelling is correct
Context: ...ummary="Platform fix in progress"> The SleakOps team is working on a comprehensive solu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/cluster-production-mode-spot-instances.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Instance Types Date: December 19, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-daphne-logging-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...hne Applications Date: January 21, 2025 Category: Workload Tags: Do...
(MISSING_COMMA_AFTER_YEAR)
[style] ~345-~345: Try moving the adverb to make the sentence clearer.
Context: ...uration for logging"> Configure Docker Compose to properly handle Daphne logs: ```yaml version: '3.8' services: w...
(SPLIT_INFINITIVE)
[style] ~553-~553: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 21, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dependency-connection-timeout-mysql-redis.mdx
[style] ~15-~15: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Timeout Issues Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...: Restart the affected service** 1. In SleakOps dashboard, go to your project 2. Find t...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/ci-cd-pipeline-setup-troubleshooting.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ing on Branch Push Date: March 14, 2024 Category: Project Tags: CI/...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...y: Git-based source control - Pipeline: SleakOps CI/CD integration - Expected behavior: ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~104-~104: Ensure spelling is correct
Context: ...n: 1. Go to Settings > CLI in your SleakOps dashboard 2. Generate or copy your API key 3. In your...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~189-~189: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-automatic-shutdown-startup-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Startup Issues Date: February 14, 2025 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~231-~231: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 14, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-upgrade-zero-downtime.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...h Zero Downtime Date: February 19, 2025 Category: Cluster Tags: Upg...
(MISSING_COMMA_AFTER_YEAR)
[style] ~165-~165: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 19, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-stuck-starting-state.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Starting State Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-build-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...bles Not Available Date: March 10, 2025 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[style] ~20-~20: Consider using “inaccessible” to avoid wordiness.
Context: ...defined in SleakOps Docker settings are not accessible during the build process, specifically ...
(NOT_ABLE_PREMIUM)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ockerfile"> Environment variables from SleakOps settings are only available at runtime,...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~64-~64: Ensure spelling is correct
Context: ...igure build arguments in SleakOps"> In SleakOps, you need to configure build arguments ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~194-~194: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 10, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cronjob-timezone-deployment-behavior.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...loyment Behavior Date: October 24, 2024 Category: Workload Tags: Cr...
(MISSING_COMMA_AFTER_YEAR)
[style] ~172-~172: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 24, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-build-failed-production.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...g Loading Issues Date: January 15, 2024 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... - Environment: Production - Platform: SleakOps - Issue type: Build failure + Log acces...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~116-~116: Ensure spelling is correct
Context: ... dashboard log loading problems"> When SleakOps dashboard logs won't load: **Browser-r...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~127-~127: Ensure spelling is correct
Context: ...utions:** 1. Log out and log back into SleakOps 2. Check if other dashboard sections work p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~134-~134: Ensure spelling is correct
Context: ...s) If problem persists: - Contact SleakOps support with specific build ID - Provid...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~198-~198: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-timeout-database-migrations.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...atabase Migrations Date: April 25, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~71-~71: Ensure spelling is correct
Context: ...ncrease pre-deploy timeout limits"> In SleakOps, you can configure longer timeout limit...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/database-migration-environment-variables.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...s Configuration Date: December 11, 2024 Category: Project Tags: Dat...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...Entity Framework database migrations in SleakOps, specifically with PostgreSQL database ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...LLOWED_ORIGINS` - Environment variables not accessible to migration processes **Relevant Conf...
(NOT_ABLE_PREMIUM)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...k - Database: PostgreSQL - Environment: SleakOps platform - Variable Groups: Backend pro...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~455-~455: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 11, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-waf-application-load-balancer-protection.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ncer Protection Date: December 19, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Load Balancer: Application Loa...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~46-~46: Ensure spelling is correct
Context: ...rom common web exploits and bots. While SleakOps doesn't have native WAF integration yet...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[uncategorized] ~142-~142: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ority: 3 Action: Block **2. Custom Rate Limiting Rule:** yaml Rule Name: RateLimitin...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~361-~361: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-restore-pod-management.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ore Pod Management Date: March 26, 2025 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[style] ~232-~232: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 26, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-production-check-node-scaling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...esource Changes Date: November 20, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
[style] ~52-~52: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...y: Node Infrastructure Changes: - Adds an additional node to the core node group in a different a...
(ADD_AN_ADDITIONAL)
[style] ~217-~217: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on November 20, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/aws-cost-monitoring-and-optimization.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...and Optimization Date: January 16, 2025 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
[uncategorized] ~58-~58: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...Deployment timing*: Partial month vs. full month billing - Multiple accounts: Costs ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~197-~197: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 16, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-prometheus-memory-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...using Pod Hangs Date: December 23, 2024 Category: Cluster Tags: Pro...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-propagation-public-deployment.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic Deployments Date: December 10, 2024 Category: Project Tags: DNS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~27-~27: Consider using “inaccessible” to avoid wordiness.
Context: ...when accessing the URL - Application is not accessible via the public domain **Relevant Confi...
(NOT_ABLE_PREMIUM)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 10, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-environment-variables-migration-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...le After Migration Date: April 24, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps on AWS - Affected environments: Develop...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~48-~48: Ensure spelling is correct
Context: ...ariables"> During platform migrations, SleakOps may update how secrets and environment ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~176-~176: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on April 24, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/connecting-to-cluster-with-lens.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...r with Lens IDE Date: December 19, 2024 Category: Cluster Tags: Len...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cost-analysis-and-resource-optimization.mdx
[style] ~22-~22: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ion in SleakOps Date: December 19, 2024 Category: General Tags: Cos...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-migrations-execution-hooks.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Execution Hooks Date: December 19, 2024 Category: Workload Tags: Da...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ... as part of their deployment process in SleakOps, specifically for .NET applications usi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~82-~82: Ensure spelling is correct
Context: ... Execution:** 1. Go to your project in SleakOps 2. Navigate to Executions section 3. Cr...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~191-~191: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/build-pods-stuck-creation.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in Creation State Date: March 22, 2025 Category: Project Tags: Bui...
(MISSING_COMMA_AFTER_YEAR)
[style] ~183-~183: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on March 22, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-addons-after-migration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... After Migration Date: October 15, 2024 Category: Cluster Tags: Mig...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with new interface - Affected addons: L...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ... SleakOps with new interface - Affected addons: Loki, Grafana, and other monitoring to...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~34-~34: Ensure spelling is correct
Context: ...tion performed - Interface: Updated/new SleakOps interface Error Conditions: - Addons not vi...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...available"> During cluster migrations, SleakOps temporarily deactivates addons to ensur...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...ss**: - Log into Grafana using your SleakOps credentials - Verify dashboards are displaying data ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~178-~178: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-eks-upgrade-schedule-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...dule and Process Date: February 6, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~57-~57: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...email - Specific dates are communicated prior to each upgrade <...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on February 6, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-kubernetes-upgrade-process.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Upgrade Process Date: December 19, 2024 Category: Cluster Tags: Kub...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ication in the Cluster section of their SleakOps dashboard and need guidance on how to p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps managed Kubernetes cluster - Environmen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~47-~47: Ensure spelling is correct
Context: ...t** on the upgrade notification in your SleakOps dashboard 2. The system will automatically begin the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~51-~51: Ensure spelling is correct
Context: ...ocess is fully automated and managed by SleakOps. <Troubleshooti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~67-~67: Ensure spelling is correct
Context: ...e upgrades Process order: 1. Core SleakOps nodes are upgraded one by one (rolling ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~83-~83: Ensure spelling is correct
Context: ...tions** in your cluster (not managed by SleakOps) - Check the Kubernetes changelog for depre...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~89-~89: Ensure spelling is correct
Context: ...pecial database preparations needed for SleakOps managed upgrades - Ensure database conn...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~120-~120: Ensure spelling is correct
Context: ...r usual monitoring tools 2. Check the SleakOps dashboard for upgrade progress 3. **W...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~132-~132: Ensure spelling is correct
Context: ...r logs If issues occur: - Contact SleakOps support immediately - Provide specific ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~168-~168: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-understanding-ec2-instances-and-costs.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... in EKS Clusters Date: January 29, 2025 Category: Cluster Tags: EKS...
(MISSING_COMMA_AFTER_YEAR)
[style] ~202-~202: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 29, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/cluster-upgrade-maintenance-scheduling.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ance Scheduling Date: December 19, 2024 Category: Cluster Tags: Clu...
(MISSING_COMMA_AFTER_YEAR)
[style] ~59-~59: ‘Advance Notice’ might be wordy. Consider a shorter alternative.
Context: ...issues ### Communication Protocol - Advance Notice: Notify clients at least 48-72 hours ...
(EN_WORDINESS_PREMIUM_ADVANCE_NOTICE)
[style] ~247-~247: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-credentials-access.mdx
[grammar] ~12-~12: Ensure spelling is correct
Context: ...tem"; # Database Credentials Access in SleakOps Date: December 19, 2024 **Catego...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ess in SleakOps Date: December 19, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~58-~58: Ensure spelling is correct
Context: ...roup"> To view database credentials in SleakOps: 1. Navigate to your project 2. **G...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~63-~63: Ensure spelling is correct
Context: ...VarGroup** 4. View the credentials: SleakOps fetches the secret from the cluster and...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-postgresql-restore-errors.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...e Restore Errors Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/database-typeorm-ssl-connection-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...n Error with RDS Date: January 15, 2024 Category: Dependency Tags: ...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-automatic-updates-github.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...pdates from GitHub Date: August 2, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ory are automatically deployed to their SleakOps environment during testing phases. **O...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~32-~32: Ensure spelling is correct
Context: ...- Source: GitHub repository - Platform: SleakOps - Environment: Development/Testing - Do...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~68-~68: Ensure spelling is correct
Context: ...nnection:** - Go to your Project in SleakOps - Navigate to Settings → *Repository...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~87-~87: Ensure spelling is correct
Context: ... the deployment workflow"> The typical SleakOps deployment workflow: ```mermaid graph ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~201-~201: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...as automatically generated on August 2, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-build-failures-during-updates.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Platform Updates Date: October 14, 2024 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ild process fails temporarily while the SleakOps platform undergoes maintenance or updat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~85-~85: Ensure spelling is correct
Context: ...rm communications**: - Subscribe to SleakOps status updates - Check email notific...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~155-~155: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on October 14, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-missing-tolerations-after-nodepool-changes.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...er Nodepool Changes Date: March 5, 2025 Category: Cluster Tags: Nod...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~61-~61: Ensure spelling is correct
Context: ... 1. Navigate to your service in the SleakOps dashboard 2. Click "Edit" on the affected deploymen...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~131-~131: Ensure spelling is correct
Context: ...odepool changes**: Coordinate with your SleakOps team before major changes 2. **Update d...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~147-~147: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...was automatically generated on March 5, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-redis-communication-error.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...munication Error Date: January 15, 2024 Category: Deployment Tags: ...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~62-~62: Ensure spelling is correct
Context: ...you encounter this issue: 1. Contact SleakOps Support: This is typically an infrast...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~158-~158: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-service-name-length-limit.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...gth Limit Error Date: February 13, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[style] ~174-~174: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on February 13, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/deployment-stuck-creating-status.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... Creating Status Date: January 27, 2025 Category: Project Tags: Dep...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...ranch and triggers a deployment through SleakOps. The build process completes successfull...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~33-~33: Ensure spelling is correct
Context: ...nt type: deploy_build_dev - Platform: SleakOps - Build status: Successful - Deployment...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~98-~98: Ensure spelling is correct
Context: ... to contact SleakOps support"> Contact SleakOps support if: 1. **Deployment stuck for ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~181-~181: Consider a different adjective to strengthen your wording.
Context: ... complex deployment issues that require deeper investigation: 1. **Deployment status ...
(DEEP_PROFOUND)
[grammar] ~469-~469: Ensure spelling is correct
Context: ...ific solutions"> Solutions specific to SleakOps platform deployment issues: 1. **Sleak...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~473-~473: Ensure spelling is correct
Context: ...t state management**: - Deployments in SleakOps may get stuck due to platform state man...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~475-~475: Ensure spelling is correct
Context: ...ates - Sometimes manual intervention by SleakOps support is required to reset state 2. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~597-~597: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 27, 2025 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/django-migration-conflicts-database-import.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...Database Import Date: December 20, 2024 Category: Project Tags: Dja...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...p into a Django application deployed on SleakOps, the pre-upgrade hook responsible for r...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~137-~137: Ensure spelling is correct
Context: ...Handling in SleakOps deployments"> For SleakOps deployments with pre-upgrade hooks: 1....
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/troubleshooting/dns-cloudflare-route53-configuration.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...are and Route53 Date: December 19, 2024 Category: Provider Tags: DN...
(MISSING_COMMA_AFTER_YEAR)
[style] ~196-~196: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...automatically generated on December 19, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/dns-migration-donweb-to-aws.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...om DonWeb to AWS Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
docs/troubleshooting/docker-build-cache-issues.mdx
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...es in Production Date: January 15, 2024 Category: Project Tags: Doc...
(MISSING_COMMA_AFTER_YEAR)
[grammar] ~31-~31: Ensure spelling is correct
Context: ...Relevant Configuration:* - Platform: SleakOps with Docker builds - Environment: Produ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~121-~121: Ensure spelling is correct
Context: ...s** - Review the deployment logs in SleakOps - Look for "Using cache" messages that mig...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~175-~175: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ... automatically generated on January 15, 2024 based on a real user query._
(MISSING_COMMA_AFTER_YEAR)
🪛 Gitleaks (8.27.2)
docs/troubleshooting/deployment-build-failed-production.mdx
74-74: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
(curl-auth-header)
🔇 Additional comments (25)
docs/troubleshooting/celery-beat-duplicate-execution.mdx (1)
350-357: CampotimeZoneaún no GA en CronJob
El ejemplo YAML incluyetimeZone:dentro de.spec, pero Kubernetes estable todavía no soporta dicha clave (feature gate pendiente). Publicar esto tal cual puede confundir a los usuarios.
Revisa la versión mínima soportada por SleakOps o añádele una nota aclaratoria.docs/troubleshooting/cronjob-timezone-deployment-behavior.mdx (2)
10-10: Verifica el casing y la ruta del componenteTroubleshootingItem.En sistemas de ficheros sensibles a mayúsculas/minúsculas,
@site/src/components/HomepageFeatures/troubleshootingitempodría no resolver si el fichero real se llamaTroubleshootingItem.{js,tsx}. Asegúrate de que el nombre del directorio/archivo coincide exactamente.
115-122: Comprueba la versión real que soportatimeZoneen CronJob.El campo
spec.timeZonese promocionó a beta en Kubernetes 1.27 y se estabilizó en 1.29. Poner “1.25+” puede inducir a error si el clúster no tiene el feature-gate activado.docs/troubleshooting/dependencies-monitoring-graphs-not-displaying.mdx (1)
10-10: Revisa la ruta del componente importadoEl
importapunta a@site/src/components/HomepageFeatures/troubleshootingitem; asegúrate de que el archivo exista con ese path y casing exacto (especialmente latminúscula). Si el archivo real se llamaTroubleshootingItem.tsxo vive en otra carpeta, la build de Docusaurus se va a romper y nos vamos a agarrar a las piñas con el CI.docs/troubleshooting/aws-waf-application-load-balancer-protection.mdx (2)
142-151: YAML de Rate Limiting no es valido para WAFv2
Scope,Rate limityConditionno existen así en el schema de AWS WAF. La versión correcta usaRateBasedStatementconLimit,AggregateKeyType, etc. Publicar ejemplos que no compilan termina generando tickets de soporte a las piñas.Revisa y actualiza el fragmento o al menos marca claramente que es pseudocódigo.
114-116: “Default action: Allow” puede dejar la puerta abiertaArrancar la Web ACL en modo Allow expone la aplicación mientras se ajustan las reglas. Para evitar sustos, AWS recomienda comenzar en Count o al menos activar Block una vez validados los managed rules.
Propongo añadir una nota y/o cambiar el paso:
- - Default action: "Allow" (recommended for initial setup) - - This allows traffic unless blocked by specific rules + - Default action: "Count" + - De esta forma registras coincidencias sin bloquear tráfico legítimo. + - Cambia a "Block" cuando verifiques que no hay falsos positivos.Likely an incorrect or invalid review comment.
docs/troubleshooting/deployment-service-name-length-limit.mdx (1)
1-8: Revisar el campocategorydel front-matterHas añadido la nueva sección “Troubleshooting”, pero este documento sigue marcado como
category: "project". Si Docusaurus usa ese valor para generar el sidebar, este artículo podría quedar fuera de la nueva categoría y perder visibilidad.Confirma que:
- El
_category_.jsonde troubleshooting espera este campo, o- Cambia a
category: "troubleshooting"(o omítelo si ya se infiere).docs/troubleshooting/cloudfront-existing-s3-bucket.mdx (2)
10-11: Import de TroubleshootingItem es válido
La búsqueda confirma que existesrc/components/HomepageFeatures/troubleshootingitem.jsx, por lo que la ruta en el import es correcta y no se requieren cambios.
83-120: Política S3 incompleta y potencialmente insegura
- Falta
s3:ListBucketsi el contenido se navega por carpeta (común en sitios estáticos).- El
Sides opcional, pero usar un identificador significativo ayuda al mantenimiento.- Sería mejor restringir también el método
HEAD(s3:GetObjectVersion) si se usa versionado.Propuesta mínima:
- "Action": "s3:GetObject", + "Action": [ + "s3:GetObject", + "s3:ListBucket" + ],Likely an incorrect or invalid review comment.
docs/troubleshooting/ci-cd-pipeline-setup-troubleshooting.mdx (1)
62-71: Trigger YAML: falta indentación de lista bajotriggers.El ejemplo
pipeline: triggers: - branch: dev on: pushno es YAML válido (no puede haber dos keys al mismo nivel en un mismo mapping). Propuesta mínima:
- - branch: dev - on: push + - branch: dev + on: + - pushdocs/troubleshooting/deployment-automatic-updates-github.mdx (1)
89-97: Diagrama Mermaid requiere plugin.El bloque
mermaidno renderizará si el preset Docusaurus no tiene el plugin habilitado. Añade la dependencia@docusaurus/theme-mermaidy activamarkdown: { mermaid: true }endocusaurus.config.js, o reemplaza el gráfico por imagen/Markdown.docs/troubleshooting/docker-build-environment-variables.mdx (1)
10-12: Import de TroubleshootingItem válido – no hay cambios necesariosLa ruta coincide con el fichero
src/components/HomepageFeatures/troubleshootingitem.jsxen minúsculas; el import funcionará correctamente en Linux.en sleakops arreglamos los conflictos a las piñas 🚀
docs/troubleshooting/build-status-discrepancy-lens-vs-platform.mdx (1)
10-11: Verificar la ruta y el casing del componenteTroubleshootingItemEn sistemas sensibles a mayúsculas (Linux, CI),
@site/src/components/HomepageFeatures/troubleshootingitemfallará si el fichero real se llamaTroubleshootingItem.tsx. Confirma coincidencia exacta de nombre o ajusta:-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";docs/troubleshooting/cluster-node-errors-web-api-unavailable.mdx (1)
12-17: La PR promete “categoría en español”, pero el contenido está en inglésEl título y los metadatos están en inglés. Si el objetivo es ofrecer documentación en español, considera traducir estos textos o moverlos a un sub-directorio
es/.Likely an incorrect or invalid review comment.
docs/troubleshooting/deployment-pending-nodepool-changes.mdx (1)
14-17: Contenido en inglés vs. objetivo en españolMisma inconsistencia que antes: confirmar si la categoría “en español” aplica también a deployment docs.
Likely an incorrect or invalid review comment.
docs/troubleshooting/cluster-nodepool-missing-after-shutdown.mdx (1)
10-10: Importación coincide con el nombre de archivo
El componente se encuentra ensrc/components/HomepageFeatures/troubleshootingitem.jsx(todo en minúsculas), y la ruta de importación@site/src/components/HomepageFeatures/troubleshootingitemes idéntica. No es necesario cambiar la capitalización.Likely an incorrect or invalid review comment.
docs/troubleshooting/database-restore-pod-management.mdx (1)
195-205:activeDeadlineSecondsfuera detemplateEn Jobs de Kubernetes debe ir dentro de
spec.template.spec. Tal como está, el Job se creará pero ignorará el timeout y tendremos restores eternos “a las piñas”.-spec: - activeDeadlineSeconds: 3600 # 1 hour timeout - backoffLimit: 3 - template: +spec: + backoffLimit: 3 + template: + spec: + activeDeadlineSeconds: 3600 # 1 hour timeoutLikely an incorrect or invalid review comment.
docs/troubleshooting/deployment-build-failures-during-updates.mdx (1)
10-11: Ignorar sugerencia de mayúscula en la ruta de importaciónEl componente realmente se encuentra en
src/components/HomepageFeatures/troubleshootingitem.jsx
(con nombre todo en minúsculas), por lo que la importación tal como está funciona en un sistema de ficheros sensible a mayúsculas/minúsculas. No es necesario cambiar aTroubleshootingItem.Likely an incorrect or invalid review comment.
docs/troubleshooting/database-migrations-execution-hooks.mdx (1)
51-54: Inconsistencia en el comando de EF migrationsUsas
update-databaseen la descripción perodotnet ef database updateen la configuración. Mantén sólo la forma oficial:-3. **Command execution**: Executes `update-database` command before updating application code +3. **Command execution**: Ejecuta `dotnet ef database update` antes de actualizar el código de la aplicaciónLikely an incorrect or invalid review comment.
docs/troubleshooting/database-migration-environment-variables.mdx (1)
2-3:sidebar_positionduplicado en la carpetaTodos los documentos nuevos fijan
sidebar_position: 3. En Docusaurus, las posiciones se deben diferenciar para ordenar los ítems; si varias comparten el mismo valor dentro del mismo directorio, el orden final es impredecible y puede sobrescribir metadatos.
Confirma y ajusta los valores para evitar colisiones.docs/troubleshooting/deployment-stuck-creating-status.mdx (1)
2-3: Evitar colisiones en el orden del sidebar
sidebar_position: 3ya se está usando en varios documentos nuevos de troubleshooting. Docusaurus no impide los duplicados, pero el orden puede volverse impredecible y algún artículo podría “taparse” a otro.
Re-asigna posiciones únicas para mantener la navegación clara.docs/troubleshooting/cost-analysis-and-resource-optimization.mdx (1)
67-68: Uso de negrita para enfatizar punto crítico: perfecto
Nada que objetar, el punto del filtroCharge Type = Usageestá claramente resaltado.docs/troubleshooting/deployment-stuck-starting-state.mdx (2)
138-142: HEALTHCHECK: puerto como var de entorno
${HEALTH_PORT}no existirá en tiempo de build; usa$${HEALTH_PORT}o reemplázalo en runtime. De lo contrario Docker asumirá string vacío y el healthcheck fallará.
2-3: sidebar_position repetidoIgual que otros docs,
sidebar_position: 3duplicado. Ajusta para evitar solapamiento.docs/troubleshooting/cluster-automatic-shutdown-startup-issues.mdx (1)
10-11: Verificación completada: el import coincide con el archivo
He comprobado que existesrc/components/HomepageFeatures/troubleshootingitem.jsxcon nombre en minúsculas, por lo que el importimport TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";es correcto y no provocará errores en sistemas case-sensitive.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Confirma la ruta del componente TroubleshootingItem.
Evita el build roto por diferencia de mayúsculas.
🤖 Prompt for AI Agents
In docs/troubleshooting/api-access-troubleshooting-private-services.mdx around
lines 10 to 11, the import path for the TroubleshootingItem component may have
incorrect capitalization. Verify the exact casing of the component filename and
folder names in the path and update the import statement to match it exactly,
ensuring consistent capitalization to prevent build errors.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Incongruencia de mayúsculas en la ruta del componente
Mismo ajuste recomendado que en los otros archivos.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/aws-cost-monitoring-and-optimization.mdx around lines 10
to 11, the import path for TroubleshootingItem has inconsistent capitalization.
Adjust the import statement to match the exact casing of the component's
filename and folder path, ensuring it is consistent with other files to avoid
module resolution errors.
| tags: ["aws", "ec2", "vpc", "networking", "public-ip"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta de importación con mayúsculas inconsistentes — va a explotar en sistemas case-sensitive
El componente se llama TroubleshootingItem, pero la ruta lo referencia en minúsculas (troubleshootingitem). En macOS funciona, en Linux fallará al compilar la doc.
Propuesta rápida:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/aws-ec2-public-ip-assignment.mdx at line 10, the import
path for the TroubleshootingItem component uses lowercase letters, which causes
issues on case-sensitive file systems like Linux. Update the import statement to
match the exact casing of the component and folder names, changing
"troubleshootingitem" to "TroubleshootingItem" to ensure consistent and
successful imports across all environments.
| # EC2 Instance Not Getting Public IPv4 Address | ||
|
|
||
| **Date:** January 15, 2024 | ||
| **Category:** Provider | ||
| **Tags:** AWS, EC2, VPC, Networking, Public IP | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Contenido en inglés dentro de la sección de documentación en español
El PR dice que se añade la categoría de troubleshooting en español, pero el título y todo el cuerpo están en inglés. Esto rompe la coherencia de la navegación y el SEO interno.
Dos opciones:
- Traducir el contenido completo a español.
- Mover el fichero a la carpeta/enrutado correspondiente a la versión en inglés (p. ej.
i18n/en/docusaurus-plugin-content-docs/current/...).
Decidid y nos pegamos las piñas necesarias. 😄
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...lic IPv4 Address Date: January 15, 2024 Category: Provider Tags: AW...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
In docs/troubleshooting/aws-ec2-public-ip-assignment.mdx around lines 12 to 17,
the content is in English while the section is meant for Spanish documentation,
causing inconsistency. To fix this, either translate the entire content into
Spanish to match the section language or move the file to the English
documentation folder such as i18n/en/docusaurus-plugin-content-docs/current/ to
keep language consistency and proper routing.
| tags: ["aws-marketplace", "authentication", "login", "setup"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Revisa la capitalización y existencia del componente importado
El path @site/src/components/HomepageFeatures/troubleshootingitem usa el nombre del componente en minúsculas, mientras que lo importas como TroubleshootingItem. En sistemas con FS case-sensitive (Linux del build server) esto revienta a la primera. Confirma que el archivo se llame exactamente troubleshootingitem.* o cambia el import a .../TroubleshootingItem.
🤖 Prompt for AI Agents
In docs/troubleshooting/aws-marketplace-login-setup-issue.mdx at line 10, the
import path for TroubleshootingItem uses lowercase 'troubleshootingitem' which
may cause issues on case-sensitive file systems. Verify the exact filename
casing of the component file and update the import statement to match it
exactly, changing the import path to use 'TroubleshootingItem' if the file is
capitalized accordingly.
| tags: ["django", "celery", "cron", "appregistrynotready", "troubleshooting"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta del componente con mayúsculas/minúsculas puede romper el build
En muchos entornos case-sensitive (Linux, CI, contenedores de producción) el nombre real del archivo es TroubleshootingItem.tsx/tsx. La ruta importada usa todo en minúsculas (troubleshootingitem).
Si el fichero realmente se llama con mayúsculas, el bundler no lo encontrará y el sitio fallará en tiempo de build.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";Verificá cómo está nombrado el archivo en src/components/HomepageFeatures/ y ajustá la ruta o renombrá el archivo para evitar “Module not found”.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/django-celery-appregistrynotready-error.mdx at line 10,
the import path for TroubleshootingItem uses all lowercase letters, but the
actual filename in src/components/HomepageFeatures/ likely has uppercase
letters. To fix this, verify the exact casing of the TroubleshootingItem.tsx
file and update the import statement to match the filename's case exactly, or
rename the file to all lowercase to ensure the build does not fail due to case
sensitivity issues.
| tags: ["aws", "dns", "route53", "migration", "donweb"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta del componente con casing incorrecto: romperá el build en entornos case-sensitive
TroubleshootingItem es PascalCase pero el path usa troubleshootingitem. En Linux/CI la importación fallará y la página no se renderizará.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/dns-migration-donweb-to-aws.mdx at line 10, the import
path for TroubleshootingItem uses incorrect casing which will break the build on
case-sensitive systems. Update the import path to match the exact PascalCase
filename "TroubleshootingItem" to ensure it works correctly on Linux and CI
environments.
| dnsPolicy: ClusterFirst | ||
| dnsConfig: | ||
| options: | ||
| # Reduce DNS timeout | ||
| - name: timeout | ||
| value: "1" | ||
| # Increase attempts | ||
| - name: attempts | ||
| value: "3" | ||
| # Enable DNS caching | ||
| - name: use-vc | ||
| - name: ndots | ||
| value: "2" |
There was a problem hiding this comment.
dnsConfig.options mal indentado: YAML inválido
- name: use-vc y - name: ndots deben tener un value, o ser clave/valor dentro del mismo mapa. Ejemplo válido:
options:
- name: use-vc
value: "true"
- name: ndots
value: "2"🤖 Prompt for AI Agents
In docs/troubleshooting/dns-resolution-failure-mysql-redis.mdx around lines 136
to 148, the YAML under dnsConfig.options is incorrectly indented and missing
values for some keys. Fix the indentation and add a value field for the use-vc
option, for example, set value: "true" under use-vc, so that each option is a
map with name and value keys properly aligned.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | ||
|
|
There was a problem hiding this comment.
Import a componente con la ruta y el nombre exactos (Linux es implacable).
TroubleshootingItem está importado desde
@site/src/components/HomepageFeatures/troubleshootingitem (todo en minúsculas).
Si el archivo real se llama TroubleshootingItem.tsx/tsx (pascal case) o vive en otro directorio, en producción (FS case-sensitive) reventará el build y “arreglar los conflictos a las piñas” no nos va a salvar.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";Verifica la ruta real antes de mergear.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/docker-build-cache-issues.mdx around lines 10 to 11, the
import statement for TroubleshootingItem uses a lowercase path which may not
match the actual file name or directory casing. Verify the exact file name and
directory casing on the filesystem and update the import path to match it
exactly, using PascalCase if the file is named TroubleshootingItem.tsx or
similar, to prevent build failures on case-sensitive systems.
| <TroubleshootingItem id="docker-compose-configuration" summary="Complete docker-compose.yml configuration"> | ||
|
|
||
| Here's a complete example of how to configure your `docker-compose.yml`: | ||
|
|
||
| ```yaml | ||
| version: "3.8" | ||
|
|
||
| services: | ||
| web: | ||
| build: . | ||
| ports: | ||
| - "8000:8000" | ||
| environment: | ||
| - DEBUG=1 | ||
| - PYTHONUNBUFFERED=1 # Important for real-time log output | ||
| command: > | ||
| daphne | ||
| --bind 0.0.0.0 | ||
| --port 8000 | ||
| --access-log /dev/stdout | ||
| --proxy-headers | ||
| myproject.asgi:application | ||
| logging: | ||
| driver: "json-file" | ||
| options: | ||
| max-size: "10m" | ||
| max-file: "3" | ||
| # Remove these if not needed for your use case | ||
| # stdin_open: true | ||
| # tty: true | ||
| ``` | ||
|
|
||
| </TroubleshootingItem> |
There was a problem hiding this comment.
IDs de TroubleshootingItem duplicados rompen el enrutado de Docusaurus
El identificador docker-compose-configuration se declara dos veces (primero en la línea 120 y luego en la 343). Docusaurus exige IDs únicos por documento; con duplicados, el anchor rota y el buscador interno se vuelve impredecible.
Propón un cambio sencillo:
-<TroubleshootingItem id="docker-compose-configuration" summary="Docker Compose configuration for logging">
+<TroubleshootingItem id="docker-compose-config-basic" summary="Docker Compose configuration for logging">
…
-<TroubleshootingItem id="docker-compose-configuration" summary="Docker Compose configuration for logging">
+<TroubleshootingItem id="docker-compose-config-aggregation" summary="Docker Compose configuration for logging (log aggregation)">Revisa cualquier enlace entrante que apunte al ID original.
Also applies to: 343-409
🤖 Prompt for AI Agents
In docs/troubleshooting/docker-daphne-logging-configuration.mdx between lines
120 and 152, the TroubleshootingItem ID "docker-compose-configuration" is
duplicated later in the file (lines 343-409), causing routing and anchor issues
in Docusaurus. To fix this, rename one of the duplicate IDs to a unique value,
ensuring no other TroubleshootingItem shares the same ID. After renaming, update
any internal links pointing to the original ID to use the new unique ID to
maintain correct navigation.
| tags: ["build", "python", "newrelic", "pkg_resources", "deployment"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Mismatch de capitalización en el import.
Corregí la ruta para evitar crashes en entorno CI Linux:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/build-newrelic-pkg-resources-deprecation-warning.mdx at
line 10, the import statement has a capitalization mismatch causing crashes in
the Linux CI environment. Correct the import path to match the exact casing of
the file or directory names, ensuring it aligns with the filesystem's case
sensitivity to prevent import errors.
| ```bash | ||
| # Validate kubeconfig | ||
| kubectl config validate | ||
|
|
||
| # Check context | ||
| kubectl config get-contexts | ||
| ``` |
There was a problem hiding this comment.
kubectl config validate no existe
El comando sugerido lanzará un unknown command. Usa kubectl config view --validate=true o kubectl config view | kubeval.
-# Validate kubeconfig
-kubectl config validate
+# Validar kubeconfig
+kubectl config view --validate=true📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ```bash | |
| # Validate kubeconfig | |
| kubectl config validate | |
| # Check context | |
| kubectl config get-contexts | |
| ``` | |
| # Validar kubeconfig | |
| kubectl config view --validate=true | |
| # Check context | |
| kubectl config get-contexts |
🤖 Prompt for AI Agents
In docs/troubleshooting/cluster-connection-troubleshooting.mdx around lines 218
to 224, replace the invalid command `kubectl config validate` with a valid
alternative such as `kubectl config view --validate=true` or `kubectl config
view | kubeval` to correctly validate the kubeconfig without causing an unknown
command error.
| tags: | ||
| ["eks", "critical-addons", "high-availability", "production", "autoscaling"] |
There was a problem hiding this comment.
Front-matter YAML inválido ➜ Docusaurus no compilará
La clave tags: abre línea nueva sin lista; usa lista inline o con guiones:
-tags:
- ["eks", "critical-addons", "high-availability", "production", "autoscaling"]
+tags: ["eks", "critical-addons", "high-availability", "production", "autoscaling"]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| tags: | |
| ["eks", "critical-addons", "high-availability", "production", "autoscaling"] | |
| tags: ["eks", "critical-addons", "high-availability", "production", "autoscaling"] |
🤖 Prompt for AI Agents
In docs/troubleshooting/cluster-critical-addons-node-failure.mdx around lines 7
to 8, the front-matter YAML for the tags key is invalid because it opens a new
line without a proper list format. Fix this by either converting the tags to an
inline list format using square brackets and quotes or by using a hyphenated
list format with each tag on its own line prefixed by a dash.
| tags: ["eks", "spot-instances", "nodegroup", "aws", "troubleshooting"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ajustar mayúsculas en la ruta del componente
Evita el fallo de resolución de módulo corrigiendo el casing.
🤖 Prompt for AI Agents
In docs/troubleshooting/cluster-eks-spot-instances-unavailable.mdx at line 10,
the import path for the TroubleshootingItem component has incorrect casing.
Adjust the import statement to match the exact casing of the file and directory
names to prevent module resolution errors.
| tags: ["deployment", "nodepool", "memory", "scaling", "troubleshooting"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta del componente con mayúsculas incorrectas ➜ posible crash en compilación
En sistemas con filesystem case-sensitive (p.e. Linux en CI), troubleshootingitem no coincide con el nombre PascalCase del componente exportado.
Esto rompe el build de Docusaurus.
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| -import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| +import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/cluster-nodepool-memory-limit-deployment-failure.mdx at
line 10, the import path for TroubleshootingItem uses incorrect casing which
causes build failures on case-sensitive filesystems. Change the import path to
match the exact PascalCase name of the component file, ensuring the folder and
filename use the correct uppercase letters to prevent compilation errors.
| tags: ["deployment", "redis", "communication", "troubleshooting", "push"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Import con case incorrecto.
Mismo fix que en las otras páginas:
-import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
+import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; | |
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/TroubleshootingItem"; |
🤖 Prompt for AI Agents
In docs/troubleshooting/deployment-redis-communication-error.mdx at line 10, the
import statement for TroubleshootingItem has incorrect casing. Correct the
import path to match the exact case of the file and folder names as used in the
project, ensuring consistency with other pages where this component is imported.
| tags: ["deployment", "build", "troubleshooting", "stuck", "creating"] | ||
| --- | ||
|
|
||
| import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem"; |
There was a problem hiding this comment.
Ruta del componente: confirma mayúsculas/minúsculas
import TroubleshootingItem from "@site/src/components/HomepageFeatures/troubleshootingitem";
En la mayoría del repo el componente vive como TroubleshootingItem.tsx (T mayúscula). En sistemas case-sensitive esto romperá el build.
¿Seguro que el archivo existe en minúsculas?
🤖 Prompt for AI Agents
In docs/troubleshooting/deployment-stuck-creating-status.mdx at line 10, the
import statement uses a lowercase 'troubleshootingitem' which may not match the
actual filename 'TroubleshootingItem.tsx' that uses an uppercase 'T'. Verify the
exact casing of the filename in the repository and update the import path to use
'TroubleshootingItem' with the correct capitalization to prevent build errors on
case-sensitive systems.
| <TroubleshootingItem id="dockerfile-configuration" summary="Proper Dockerfile configuration for private repositories"> | ||
|
|
||
| For applications requiring private GitHub repository access: | ||
|
|
||
| ```dockerfile | ||
| # Build Stage | ||
| FROM gradle:jdk21-alpine AS build | ||
|
|
||
| WORKDIR /workspace | ||
| COPY . . | ||
|
|
||
| # Define build arguments for GitHub authentication | ||
| ARG GITHUB_USER | ||
| ARG GITHUB_TOKEN | ||
|
|
||
| # Set environment variables for GitHub access | ||
| ENV GITHUB_USER=$GITHUB_USER | ||
| ENV GITHUB_TOKEN=$GITHUB_TOKEN | ||
|
|
||
| # Configure Gradle properties for private repository access | ||
| RUN echo "gpr.user=$GITHUB_USER" >> ~/.gradle/gradle.properties && \ | ||
| echo "gpr.key=$GITHUB_TOKEN" >> ~/.gradle/gradle.properties | ||
|
|
||
| # Build the application | ||
| RUN gradle clean assemble --no-daemon | ||
| ``` | ||
|
|
||
| **Important**: Ensure Docker build arguments are properly configured in SleakOps project settings. | ||
|
|
There was a problem hiding this comment.
Variables ARG y ENV duplicadas
Definir ARG y luego ENV con el mismo valor expone credenciales en la capa de la imagen final. Mejor usa solo ARG en build y no los copies a ENV, o al menos limpia con --mount=type=secret si usas BuildKit.
🤖 Prompt for AI Agents
In docs/troubleshooting/deployment-stuck-starting-state.mdx between lines 60 and
88, the Dockerfile snippet defines both ARG and ENV variables for GitHub
credentials, which exposes sensitive data in the final image layers. To fix
this, remove the ENV declarations for GITHUB_USER and GITHUB_TOKEN and avoid
copying ARG values into ENV. Instead, use ARG only during build or leverage
BuildKit's --mount=type=secret feature to securely pass credentials without
exposing them in image layers.
| # Mark specific migrations as fake-applied | ||
| python manage.py migrate cobranza 0002_initial --fake | ||
| python manage.py migrate django_celery_results 0011_taskresult_periodic_task_name --fake | ||
|
|
||
| # Verify the fix | ||
| python manage.py showmigrations | ||
| ``` |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Advertencia: uso de --fake sin validar el esquema puede generar divergencias.
Antes de marcar una migración como fake-applied, ejecuta python manage.py migrate --plan y compara el esquema real (p.ej. con pg_dump --schema-only) para asegurarte de que la estructura coincide.
Sugiero añadir una nota para recordarlo al usuario.
🤖 Prompt for AI Agents
In docs/troubleshooting/django-migration-conflicts-database-import.mdx around
lines 90 to 96, add a cautionary note before the commands that use --fake to
remind users to first run python manage.py migrate --plan and compare the actual
database schema (e.g., using pg_dump --schema-only) to ensure the schema
matches. This note should warn that using --fake without validation can cause
schema divergences and advise verifying the schema before marking migrations as
fake-applied.
| 2. **In Cloudflare:** | ||
|
|
||
| - Create NS records pointing your subdomain to Route53 name servers | ||
| - Example: `subdomain.yourdomain.com` → Route53 NS records | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Delegación NS: falta recordar desactivar proxy naranja
Entre los pasos de Cloudflare indicas crear registros NS, pero no aclaras que deben estar con “DNS only”. Usuarios suelen dejar el proxy naranja y la delegación falla. Inserta la advertencia.
🤖 Prompt for AI Agents
In docs/troubleshooting/dns-cloudflare-route53-configuration.mdx around lines 54
to 58, add a clear warning that when creating NS records in Cloudflare for
subdomain delegation to Route53, the proxy (orange cloud) must be disabled and
set to "DNS only" to avoid delegation failures. Insert this note immediately
after the step about creating NS records to ensure users do not leave the proxy
enabled.
…orking-que-desplegamos-en-los-clientes feat: networking documentation
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/network.mdx (2)
13-14: Sustituir el bloque de cita por una admonición nativa de DocusaurusPara mantener consistencia con el resto de la documentación y aprovechar el renderizado de estilos, reemplaza el bloque
> ❓ **Note:** ...por la sintaxis de admonición:-> ❓ **Note:** The network is designed to ensure security, scalability, and high availability. It enables environment separation, protects sensitive data, and exposes services in a secure and controlled way. +:::note +The network is designed to ensure security, scalability, and high availability. It enables environment separation, protects sensitive data, and exposes services in a secure and controlled way. +:::
11-11: Revisión de estilo: redundancia “clear and simple”En inglés técnico solemos escoger un solo adjetivo. Considera eliminar “simple” o “clear” para evitar redundancia:
-This documentation provides a clear and simple overview of the network architecture that SleakOps deploys in client environments. +This documentation provides a clear overview of the network architecture that SleakOps deploys in client environments.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/network.mdx(1 hunks)
🧠 Learnings (1)
📓 Common learnings
Learnt from: agustinoli
PR: sleakops/docs#85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento `docs/project/dependency/index.mdx`, la numeración de los pasos es correcta y no necesita cambios.
🪛 LanguageTool
docs/network.mdx
[grammar] ~11-~11: Ensure spelling is correct
Context: ...erview of the network architecture that SleakOps deploys in client environments. It expl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~17-~17: Ensure spelling is correct
Context: ...## 1. Overview of the Architecture The SleakOps network infrastructure is based on the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~70-~70: Ensure spelling is correct
Context: ... > 💡 Besides Internet Gateway access, SleakOps also supports other connectivity option...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: agustinoli
PR: sleakops/docs#85
File: docs/project/dependency/index.mdx:78-78
Timestamp: 2024-11-27T17:42:11.531Z
Learning: En el documento `docs/project/dependency/index.mdx`, la numeración de los pasos es correcta y no necesita cambios.
🪛 LanguageTool
docs/network.mdx
[grammar] ~11-~11: Ensure spelling is correct
Context: ...erview of the network architecture that SleakOps deploys in client environments. It expl...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~17-~17: Ensure spelling is correct
Context: ...## 1. Overview of the Architecture The SleakOps network infrastructure is based on the ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~70-~70: Ensure spelling is correct
Context: ... > 💡 Besides Internet Gateway access, SleakOps also supports other connectivity option...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🔇 Additional comments (1)
docs/network.mdx (1)
48-53: Mejorar accesibilidad y verificación de la ruta de la imagen
- El texto alternativo
"reference-architecture"es poco descriptivo. Propón algo más informativo, p. ej.:"Diagrama de arquitectura de red de SleakOps".- Confirma que la ruta
/img/network/sleakops-network.pngexista enstatic/img/network/. Si la ruta es incorrecta, el build de Docusaurus fallará “a las piñas”.- alt="reference-architecture" + alt="Diagrama de arquitectura de red de SleakOps"
…onent
Summary by CodeRabbit