Skip to content

Navigation Menu

Explore
For
- Enterprise
- Teams
- Startups
- Education
By Solution
Resources
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

vercel / next.js Public

Notifications You must be signed in to change notification settings
Fork 26k
Star 122k

Code
Issues 2.7k
Pull requests 480
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

Back to pull request #51174

Add option for debugging CPU usage #1148

Sign in to view logs

Sign in to view logs

Add option for debugging CPU usage

Add option for debugging CPU usage #1148

Summary
Jobs
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- thank you, next
Run details
- Usage
- Workflow file

Usage Workflow file

The logs for this run have expired and are no longer available.

Re-running jobs...

You can’t perform that action at this time.