Skip to content
New issue

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

namespaces: still a lot deprecation warnings #1010

Closed
tvdijen opened this issue Dec 2, 2018 · 7 comments
Closed

namespaces: still a lot deprecation warnings #1010

tvdijen opened this issue Dec 2, 2018 · 7 comments

Comments

@tvdijen
Copy link
Member

tvdijen commented Dec 2, 2018

Describe the bug
Despite de fact that all classes have been migrated to namespaces, I still see a lot of deprecation-warnings in the logs..

To Reproduce
Steps to reproduce the behavior:

  1. Turn debug-logging on.. Actually level 4 (INFO) is enough for this
  2. For example, try an authentication flow
  3. See logfile

Expected behavior
The log-line below shouldn't occur., because everything has been migrated. It's just a few of many (equal) lines that are printed.

Screenshots or logs
Dec 2 18:16:57 webapp-1 simplesamlphp-idp[3172]: 4 [39c1af90a2] The class or interface 'SimpleSAML_Utilities' is now using namespaces, please use 'SimpleSAML\Utilities'.
Dec 2 18:16:57 webapp-1 simplesamlphp-idp[3172]: 4 [39c1af90a2] The class or interface 'sspmod_core_Stats_Output_Log' is now using namespaces, please use 'SimpleSAML\Module\core\Stats\Output\Log' instead.

@tvdijen tvdijen added this to the 1.18 milestone Dec 2, 2018
@jaimeperez
Copy link
Member

I think the warnings regarding SimpleSAML_Utilities are coming from the SAML2 library. However, the ones on sspmod_core_Stats_Output_Log puzzle me. Have you tried grepping for that in your SSP installation? If there's absolutely no code using that class name, you should never get the warning...

@tvdijen
Copy link
Member Author

tvdijen commented Dec 3, 2018

I did grep, also on the SAML2 library.. In fact, I have replaced all old namespaces there in the 3.3.0 release.
My best guess is that it comes from the authproc-filters where translate something like core:TargetedID to a class-name.. Needs further investigation

@jaimeperez
Copy link
Member

Uhm, that translation should be done in SimpleSAML\Module, and there it should already use namespaces... 🤔

@tvdijen

This comment has been minimized.

@tvdijen
Copy link
Member Author

tvdijen commented Dec 3, 2018

Never mind, I've fixed it in 39d64ee

@tvdijen tvdijen closed this as completed Dec 3, 2018
@jaimeperez
Copy link
Member

No more warnings in the log then?

@tvdijen
Copy link
Member Author

tvdijen commented Dec 4, 2018

Nope, all gone! 😄

@tvdijen tvdijen modified the milestones: 1.18, 1.17 Dec 7, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants