Skip to content

Navigation Menu

Appearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  Accelerator
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

Uh oh!

There was an error while loading. Please reload this page.

vlang / v Public

Notifications You must be signed in to change notification settings
Fork 2.3k
Star 37.8k

Code
Issues 44
Pull requests 50
Discussions
Actions
Projects
Wiki
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security and quality
Insights

CI Linux

net.quic: use crypto.rand instead of rand for connection IDs and TLS random #20514

Sign in to view logs

Sign in to view logs

net.quic: use crypto.rand instead of rand for connection IDs and TLS random

net.quic: use crypto.rand instead of rand for connection IDs and TLS random #20514

Uh oh!

There was an error while loading. Please reload this page.

Annotations

10 errors and 1 warning

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse4_1.v#L12

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse4_1.v#L12

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse3.v#L10

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse3.v#L10

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse2.v#L19

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse2.v#L19

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse.v#L16

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/sse.v#L16

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/mmx.v#L18

inline assembly is not supported by the selected V3 backend

Build examples: examples/cpu_features/SSE_and_MMX_Extensions/mmx.v#L18

inline assembly is not supported by the selected V3 backend

Complete job

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

clang-linux

failed Aug 25, 2026 in 1h 44m 23s

Loading

Re-running jobs...

You can’t perform that action at this time.