Skip to content

Navigation Menu

Appearance settings

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
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.

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

symfony / symfony Public

Notifications You must be signed in to change notification settings
Fork 9.6k
Star 30.4k

Code
Issues 574
Pull requests 316
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Make sure trace_level is always defined#32802

Merged

fabpot merged 1 commit intosymfony:4.3symfony/symfony:4.3from

dbu:patch-3dbu/symfony:patch-3Copy head branch name to clipboard

Jul 30, 2019

Conversation Commits1 (1)Checks Files changed

Merged

Make sure trace_level is always defined#32802
fabpot merged 1 commit intosymfony:4.3from
dbu:patch-3

Commits

Commits on Jul 29, 2019

Make sure trace_level is always defined
dbu
authored

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.