We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I published a traffic limiting policy, but what I see in the debug log is the new type And when it's published, there's not a single record
Able to record and query publication logs
I already know the solution: Because the int type is passed in when setting the publish identifier bit
No response
1.publish a api 2.Viewing Debug Logs
APINTO Dashboard version (run apinto dashboard version):3.3.2 Operating system (run uname -a):Darwin SZ-110200200069.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030 arm64
The text was updated successfully, but these errors were encountered:
Okay, we have also identified this issue and expect a version to be released next week to fix it together. Thank you for your feedback.
Sorry, something went wrong.
What's new or bug fixes expected in next week's release ,can you tell me briefly
No branches or pull requests
Current Behavior
I published a traffic limiting policy, but what I see in the debug log is the new type
And when it's published, there's not a single record
Expected Behavior
Able to record and query publication logs
I already know the solution:
Because the int type is passed in when setting the publish identifier bit
Error Logs
No response
Steps to Reproduce
1.publish a api
2.Viewing Debug Logs
Environment
APINTO Dashboard version (run apinto dashboard version):3.3.2
Operating system (run uname -a):Darwin SZ-110200200069.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030 arm64
The text was updated successfully, but these errors were encountered: