Skip to content

Navigation Menu

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.

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

cs3org / reva Public

Notifications You must be signed in to change notification settings
Fork 112
Star 172

Code
Issues 229
Pull requests 69
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Log traces only when these are available#2352

Closed

refs wants to merge 5 commits intoedgecs3org/reva:edgefrom trace-loggingcs3org/reva:trace-loggingCopy head branch name to clipboard

+37-13

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Dec 10, 2021

prevented from logging traceid when no trace is available
refs
committed
add changelog
refs
committed
adjusted tests expectations
refs
committed
improve readability
refs
committed

Commits on Dec 13, 2021

apply review changes
refs
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.