Autoreload ticks are filling logs

Our log files are being filled by this autoreload tick, which makes it difficult to investigate real issues.
DEBUG 2024-09-24 05:59:56,104 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/admin.html first seen with mtime<PHONE_NUMBER>.955985
DEBUG 2024-09-24 05:59:56,115 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/pagination first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,125 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/base.html first seen with mtime<PHONE_NUMBER>.955985
DEBUG 2024-09-24 05:59:56,135 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/filters first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,143 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/schema.js first seen with mtime<PHONE_NUMBER>.955985
DEBUG 2024-09-24 05:59:56,154 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/login.html first seen with mtime<PHONE_NUMBER>.955985
DEBUG 2024-09-24 05:59:56,167 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/login_base.html first seen with mtime<PHONE_NUMBER>.955985
DEBUG 2024-09-24 05:59:56,176 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,184 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,196 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,208 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/admin/dict_value.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,218 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/admin/detail.html first seen with mtime<PHONE_NUMBER>.955985
DEBUG 2024-09-24 05:59:56,229 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/admin/list.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,242 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/admin/list_value.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,251 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/admin/simple_list_value.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,260 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/select_multiple.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,271 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/radio.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,281 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/list_fieldset.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,293 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/form.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,316 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/textarea.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,326 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/checkbox_multiple.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,333 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/dict_field.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,343 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/input.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,351 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/fieldset.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,363 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/select.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,384 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/checkbox.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,396 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/vertical/list_field.html first seen with mtime<PHONE_NUMBER>.965985
DEBUG 2024-09-24 05:59:56,408 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/pagination/numbers.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,418 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/pagination/previous_and_next.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,429 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/filters/ordering.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,442 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/filters/base.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,451 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/filters/search.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,460 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/fieldset.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,471 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/select.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,488 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/list_fieldset.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,502 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/radio.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,510 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/form.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,521 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/checkbox.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,532 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/select_multiple.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,541 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/list_field.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,551 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/checkbox_multiple.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,560 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/input.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,576 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/textarea.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,584 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/inline/dict_field.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,596 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/sidebar.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,601 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/interact.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,613 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/auth first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,625 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/link.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,635 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/document.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,643 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/index.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,655 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/error.html first seen with mtime<PHONE_NUMBER>.958985
DEBUG 2024-09-24 05:59:56,667 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,677 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/auth/token.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,688 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/auth/basic.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,700 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/auth/session.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,710 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs/shell-intro.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,718 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs/python.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,729 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs/javascript-intro.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,758 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs/javascript.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,767 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs/shell.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,782 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/docs/langs/python-intro.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,792 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/select_multiple.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,801 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/select.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,810 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/checkbox.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,821 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/input.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,826 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/dict_field.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,835 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/form.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,843 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/fieldset.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,850 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/checkbox_multiple.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,860 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/textarea.html first seen with mtime<PHONE_NUMBER>.962985
DEBUG 2024-09-24 05:59:56,922 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/list_fieldset.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,942 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/list_field.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,951 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/templates/rest_framework/horizontal/radio.html first seen with mtime<PHONE_NUMBER>.959985
DEBUG 2024-09-24 05:59:56,963 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/ckeditor/templates/ckeditor first seen with mtime<PHONE_NUMBER>.7199836
DEBUG 2024-09-24 05:59:56,974 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/ckeditor/templates/ckeditor/widget.html first seen with mtime<PHONE_NUMBER>.7199836
DEBUG 2024-09-24 05:59:56,985 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/sortedm2m/locale/de/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.3579922
DEBUG 2024-09-24 05:59:56,997 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/sortedm2m/locale/fr/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.3579922
DEBUG 2024-09-24 05:59:57,009 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/sortedm2m/locale/cs/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.3579922
DEBUG 2024-09-24 05:59:57,017 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/sortedm2m/locale/es/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.3579922
DEBUG 2024-09-24 05:59:57,027 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/th/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,038 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/el/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,048 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/pt_PT/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,059 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/uk/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,068 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/pt_BR/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,080 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/nn/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,093 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/vi/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,102 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ja/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,113 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/de/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.928985
DEBUG 2024-09-24 05:59:57,117 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/mk/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.9349852
DEBUG 2024-09-24 05:59:57,127 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/id/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,207 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/fa_IR/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,243 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ru/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,260 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/pt/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,329 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/en_US/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,401 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/el_GR/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,477 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/lv/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.9349852
DEBUG 2024-09-24 05:59:57,497 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/sv/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.938985
DEBUG 2024-09-24 05:59:57,510 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/fi/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,524 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/az/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,535 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/hy/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,546 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/sl/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.938985
DEBUG 2024-09-24 05:59:57,560 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/he_IL/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,567 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ro/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,576 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/it/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,588 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ca/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,601 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/en_AU/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,610 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/da/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.928985
DEBUG 2024-09-24 05:59:57,622 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/be/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,639 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/sk/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.938985
DEBUG 2024-09-24 05:59:57,650 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/tr/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,659 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/bg/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,668 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/et/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,680 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/zh_CN/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,694 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/zh_Hant/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,709 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/gl_ES/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,722 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/nb/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.935985
DEBUG 2024-09-24 05:59:57,735 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/no/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,743 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/gl/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,755 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/zh_TW/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,767 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ru_RU/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,780 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/zh_Hans/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,793 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/hu/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.932985
DEBUG 2024-09-24 05:59:57,801 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ach/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,810 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/es/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,822 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/pl/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.936985
DEBUG 2024-09-24 05:59:57,834 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/lt/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.9349852
DEBUG 2024-09-24 05:59:57,843 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ne_NP/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.935985
DEBUG 2024-09-24 05:59:57,855 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/fr_CA/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,868 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ko_KR/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.9349852
DEBUG 2024-09-24 05:59:57,877 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ar/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,885 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/fa/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,897 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/cs/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.928985
DEBUG 2024-09-24 05:59:57,909 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/nl/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.935985
DEBUG 2024-09-24 05:59:57,960 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/tr_TR/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.939985
DEBUG 2024-09-24 05:59:57,972 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/en_CA/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:57,984 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/ca_ES/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.925985
DEBUG 2024-09-24 05:59:57,993 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/fr/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:58,002 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/rest_framework/locale/en/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.929985
DEBUG 2024-09-24 05:59:58,010 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/zh_CN/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1219847
DEBUG 2024-09-24 05:59:58,018 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/sk/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1219847
DEBUG 2024-09-24 05:59:58,027 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/it/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,038 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/ca/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1129847
DEBUG 2024-09-24 05:59:58,050 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/id/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,059 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/ru/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1199846
DEBUG 2024-09-24 05:59:58,068 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/pt/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1199846
DEBUG 2024-09-24 05:59:58,076 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/fi/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,085 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/sv_SE/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1219847
DEBUG 2024-09-24 05:59:58,093 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/uk/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1219847
DEBUG 2024-09-24 05:59:58,101 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/ja/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,119 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/de/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1129847
DEBUG 2024-09-24 05:59:58,130 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/nl/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1199846
DEBUG 2024-09-24 05:59:58,143 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/fr/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,152 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/pt_BR/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1199846
DEBUG 2024-09-24 05:59:58,160 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/en/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1159847
DEBUG 2024-09-24 05:59:58,172 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/fa/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,184 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/he/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1169846
DEBUG 2024-09-24 05:59:58,194 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/cs/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1129847
DEBUG 2024-09-24 05:59:58,202 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/es/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1159847
DEBUG 2024-09-24 05:59:58,213 autoreload tick<PHONE_NUMBER>11118464 File /usr/local/lib/python3.11/site-packages/debug_toolbar/locale/pl/LC_MESSAGES/django.mo first seen with mtime<PHONE_NUMBER>.1199846

Gemini suggests changing the log levels:
The autoreload messages are logged at the DEBUG level. You can increase the logging level for the django.utils.autoreload module to a higher level like INFO or WARNING. This will prevent DEBUG messages from being logged, including the autoreload ticks.
Here's how you can do this in your project's settings.py file:
Python
LOGGING = {
    'version': 1,
    'loggers': {
        'django.utils.autoreload': {
            'level': 'INFO',  # Change to 'INFO' or 'WARNING'
        },
    },
    # ... other logging configuration
}

Appears to work!


CDN support for custom card icons

We're using some of the service icons multiple times on the quick start and documentation cards and this currently only supports base-64 formats. This format seems to cause some jagged edges with the icon.
This request is for:

Being able to support other image formats
Being able to optimize the page load by using CDN delivered images

cc: @pmuir @wtrocki

wrong repo


Forces sound on

Expected behavior
Nothing unless there'sa new email. Then only vibrate notice when on vibrate
Actual behavior
Turns phone sound on frequently, unless I change K9 settings to show no notifications
Steps to reproduce

Environment
K-9 Mail version:
Android version:
Marshmallow on galaxy s7
Account type (IMAP, POP3, WebDAV/Exchange):
IMAP

Please fill in the version.


cannot select list items

doesn't work for me. what am I doing wrong?

As of now, it has to match exactly, including spacing. So if there's a leading or trailing space it might break it. I may be able to loosen some of these restrictions.


[Subtask]Investigate and design the model management in Gravitino

This issue focuses on investigate and design how to manage ML model in Gravitino.

Here attach the design doc for ML model management (https://docs.google.com/document/d/19_3ONLiwHuJBSkBMEwDLhzPqsCoAarwP4epcesYLgfM/edit?usp=sharing).


feat(int-713): Adding option to log in the CLI with token (Enabling the possibility to login with SSO)

Pull request type
Jira Link: INT-713

[x] Feature
[x] Refactoring (no functional changes, no api changes)

How to test this PR
Now you can use your token created in the user settings area, and you t login the CLI, like the video bellow, and the login with password still working normally.
https://user-images.githubusercontent.com/40925579/218489411-c066890c-7e98-4447-958a-f5a397e30457.mov
What is the new behavior?

Now it's possible to use the CLI with SSO users login with the access_token
The docs about login command is updated

Other information

@ademarCardoso What do you think of adding a --token arg so that it's possible to use it in a pipeline as well?
storyblok login --token x12adsa

@ademarCardoso What do you think of adding a --token arg so that it's possible to use it in a pipeline as well?
storyblok login --token x12adsa

Nice idea my friend, i will talk with the team about this thing 🚀

@ademarCardoso What do you think of adding a --token arg so that it's possible to use it in a pipeline as well?
storyblok login --token x12adsa

I talked to my squad and we are not going to add this feature right now because we have several other priorities, but I left an open task for development for the next sprints.
Thanks in advance for the idea 😄

@ademarCardoso What do you think of adding a --token arg so that it's possible to use it in a pipeline as well?
storyblok login --token x12adsa

I talked again to my team and we added this new feature in this PR https://github.com/storyblok/storyblok-cli/pull/35


bim: bump to 2.5.1

Description of package
Checklist

[X] Latest upstream version.
[X] I agree to maintain this package (required).
[X] I agree to notify KISS if I can no longer maintain this package (required).

:+1:


Replace homegrown OrderedDict with purpose-built Registry.

All processors and patterns now get "registered" to a Registry.
Each item is given a name (string) and a priority. The name is for
later reference and the priority can be either an integer or float
and is used to sort. A Registry instance is a list-like iterable with
the items auto-sorted by priority. If two items have the same priority,
then they are listed in the order there were "registered". Registering
a new item with the same name as an already registered item replaces
the old item with the new item (however, the new item is sorted by
its priority). To remove an item, "deregister" it by name or index.
Fixes #418.
Note that this is an adaptation of #510 which has been rebased onto master.

@facelessuser, @mitya57 and any other extension authors, I would appreciate some feedback on this. Specifically on how I'm handling backward compatibility. The reasons for the change were discussed extensively in #418 and the implementation is documented in the doc strings.
After getting a working implementation (the first commit), I worked on a backward compatible shim so that existing extensions can continue to work until we remove the shim in some future version. The shim won't be able to accommodate some of the more complex stuff, but I believe it should address the needs of most basic extensions. I'm asking if there is anything I missed.
I reviewed the existing documentation for our homegrown OrderedDict and implemented the following methods:

add(name, item, location)
As a reminder, location can be one of _begin, _end, <name or >name.
For any location which means 'insert new item at beginning/end", the new item is assigned a priority 5 more/less than the first/last existing item.
For any location which inserts an item between existing items, the priority of those existing items are obtained, and the new item is assigned a priority half-way between them.
A DecrecationWarning will be raised when the add method is called.

delete item
You can do del collection['name'] to remove an item from the collection. This simply passes the name to the deregister method and then a DecrecationWarning will be raised.

set item

You can do collection['name'] = NewItem() to add an item to the collection. The new item is given a priority five less that the last existing item and then a DecrecationWarning will be raised.
In addition to the above, there are a few documented methods which I did not re-implement, which are discussed below:

link(location)
The link method of out homegrown OrderedDict allowed the position of an existing item to be moved to a new location using the location syntax of the add method. The new priority based registry does not include a method for changing priority, therefore it doesn't make sense to include this method. Is that a problem? If so, then we should probably implement the method for changing priority and then implement this as a deprecated wrapper. Thoughts?

* Various other methods.
The documentation mentions that various other methods are available common to lists and dicts which can be used to manipulate instances of an OrderedDict. However, as those methods are very general purpose and not specific to the intended use case, they are not implemented on the new registry and I see no value in providing a shim for them. If an existing extension is using these methods, then it is complex enough that their likely won't be a simple migration path and the extension is not likely to work in the new release of Markdown anyway. Thoughts?

I will provide feedback as soon as I am able to evaluate this, thanks.

The change and the backwards compatibility shim look good to me. It is fine to remove some methods — after all the next version is 3.0 so some breakage is expected. Anyway, my third-party extensions' tests pass fine with this branch.

after all the next version is 3.0 so some breakage is expected.

I agree, however, I believe our most valuable asset is the rich collection of extensions (both first and third party). If we cut off all existing third party extensions, we may find people will migrate to a competing lib rather than update their extensions. Therefore, I'd like to make the transition as painless as possible. To be clear, I am not suggesting that we should avoid the changes, simply that the transition is smooth.
It is great to hear that your "third-party extensions' tests pass fine with this branch." That's what I was aiming for.

I'm going to need some time to sort through all of my errors with the 3.0.dev merge.  I'm getting a number of failing tests, but I'm not sure if any are related to this specific change.

You are right, extensions are a very great feature of Python-Markdown :)
To be more precise, I tested my math and posmap extensions. The latter was affected by another change in master, see retext-project/retext@37923cb1b74eb813714854503990b8a204b5610f where I fixed it. That extension is a great hack so I think it's normal that it breaks.
@facelessuser has a much larger collection of extensions, so results of his experiments would be more interesting.

Yeah, I have a number of issues.  Two related to this change AttributeError: 'Registry' object has no attribute 'link'. And AttributeError: 'Registry' object has no attribute 'keys'.
Various other changes are causing failures as well, like link inline patterns no longer having sanitize_url, which is probably no big deal if I remember correctly...I think by default it did nothing?  I'll have to dig into it.
ModuleNotFoundError: No module named 'markdown.odict', this is to be expected.
Changes in stash: TypeError: store() got an unexpected keyword argument 'safe'.
A couple of syntax failures which are most likely related to one or more of the above issues.  So I have some things to work through to better understand the new changes.

Yeah, I have a number of issues.  Two related to this change AttributeError: 'Registry' object has no attribute 'link'. And AttributeError: 'Registry' object has no attribute 'keys'.

Interesting. These are exactly the sorts of things I am look for. WHen you get a chance, some more info on those would be helpful.

As far as the two errors concerning the Registry, the first (AttributeError: 'Registry' object has no attribute 'link') deals with overrides of existing keys.  I was overriding a number of the emphasis keys and injecting new ones.  This required me to move an exiting  key.  link made that easy, but is now gone requiring me to do it manually now:
        if Registry is not None:
            value = md.inlinePatterns["em_strong"]
            index = md.inlinePatterns.get_index_for_name("strong_em2")
            md.inlinePatterns.register(value, "em_strong", index + 1)
        else:
            md.inlinePatterns.link("em_strong", ">strong_em2")

This one might be worth addressing.  I actually get burned by this one in a couple of extensions.  There are some that I need to ensure are after certain extensions, and I can't really determine this until a reset because that is the only time all extensions are loaded, so I will "link" if I don't meet that criteria during reset.
The second error (AttributeError: 'Registry' object has no attribute 'keys') was simply due to me treating the registry as an Ordered Dict, which it used to be.  I was simply searching for an existing key to determine if an extension was loaded.  I don't have to use 'ext' in registry.key()to compare a key though, I could have just as easily just done'ext' in registry.  Not exactly sure why I specifically called key`.
This second one isn't really a something I think you need to specifically address.
I need to finish cleaning up

I have never needed to use link myself. So it is good to see that it has a useful application in the real world. We can provide a replacement (and temporary shim) for it. Any suggestions for a name. As the new method will be changing priority (rather than position), I'm not sure "link" makes sense.

Turns out there is no in place replace.  I have to hack an in place replace as the behavior is now unintuitive.  It always inserts 5 less than the last.
        if util.MD3:
            md.inlinePatterns._data['autolink'] = auto_link_pattern
        else:
            md.inlinePatterns['autolink'] = auto_link_pattern

Took me a minute to understand what you meant, but I think I got it. Previously, when using setitem on an existing key, the position information was not altered (the item was simply replaced in-place). That doesn't happen with the shim. The shim assumes a new item is always being added. Yep, that's a bug.

Yeah, I'm still playing around with it, I'm going to explore a bit more with the moving of an item.  There were some things that didn't quite work like I expected them.  This may have been due to a misunderstanding on my part, but I'm not sure.
Originally I was using the legacy notation of moving an item with > or < to get right after a certain item.  That worked (the tests passed), but I tried to move away from that with utilizing get_index_for_name and then incrementing that for priority.  While the tests worked there, I realized that the index returned is its position in the list, not its priority.  I then used that index to extract the priority from self._priority and incremented that and registered the item with the new priority and tests failed. This seemed odd.
There are still some things for me to figure out and work out.  I'm still trying to figure out what went wrong as what I was doing seemed like it should have worked. It may be my own mistake/misunderstanding, but I am still investigating.

Right, there is no public way to get an item's priority. Not sure why we need that. I was trying to get away from using any existing items position to calculate a new position programicaly. Each item's priority should be a known constant which never changes. In fact, I expect that is why I originally did not provide a mechanism for changing an item's priority.
Do you have a situation where Item A needs a lower priority that item B in some situations but needs a higher priority than item B is other situations. If not, then you should never need to change an item's priority.
As a reminder, each priority in the Markdown lib is incremented by 10. So if you need to insert multiple items between two existing items, you have 9 possible whole numbers and an infinite number of floats to use as priorities. If you have two items to insert, simply give item A a priority higher than item B within that range. Even if the items are loaded from two separate extensions, they are sorted correctly regardless of which is loaded first. As each priority is a known constant, you can give each item a priority which works with all other known items. This breaks when you start changing priorities.
In fact, after thinking on this some more, I'm thinking perhaps we should not allow priorities to be changed.

Let me illustrate. Suppose the Markdown lib provides 2 items: A & B. Multiple extensions need to insert items between A & B, but due to conflicts between those extensions, order matters among them. The old way required examining what was already there and altering location accordingly, which was rather cumbersome.
Instead, each item has a priority assigned to it as a known constant, such as:
A (priority=20)
ext_a (priority=18)
ext_b (priority=15)
ext_c (priority=12)
B (priority=10)

Whether all, some or none of those extensions are loaded by the user, they will always be sorted in the correct order, irrespective of the order that they are loaded. If a new extension comes along which needs to be between ext_a and ext_b, then that new item should simply be assigned a priority somewhere between 15 and 18. And as every priority is a known constant, you don't need to worry about that changing and breaking yours.

Yes, this requires that a developer know the priorities set for any other items. But she always needed to know the names before, and the priority is set at the same time as the name. So that information is always together.
True, when using the shim the priority is calculated. But that is only a convenience until everyone updates to explicitly set a priority. Then the shim will be removed and all priorities will be known constants only, never calculated.

Right, there is no public way to get an item's priority. Not sure why we need that.

I understand, and to be honest, I'm fine if we don't have an official "move" API method.  As long as there is a deregister and register, a move can be made (and I don't think we should get rid of deregister 🙂).

Each item's priority should be a known constant which never changes.

Yes, as each item has a known priority, technically you can, in most cases, just provide a value that should account for other known priorities.
There may be occasions where you want to insert an extension A with priority X in default cases, but with priority Y if extension B is present.  My specific extension can be refactored where I don't need to this, so this is not an immediate concern, but I'll illustrate what my real concern is.
I'm not concerned if we have a "move" command.  I'm more concerned with unexpected behavior with priorities.  What I was trying to illustrate was that when I acquired the priority of an existing extension, which I think turned out to be 30 (which matched the hard coded value), I tried to use 31 as the priority for my extension, and it didn't work as expected.  This might be due to my misunderstanding or improper use of the API, but I just need to confirm what the issue is.  I'm more concerned with whether or not the priority insertion is intuitive.  I'm not sure if there is special logic when you insert at the tail or not.  Or if there are cases where the list is expected to be sorted, but doesn't get sorted. I just need to make sure this is working as expected.

Understood.  I'm evaluating in my free time.  Hopefully I'll have a better understanding in the next day or so.
I've addressed most of the 3.0dev issues, but there are still some more.

I had the priority backwards.  That is a little confusing.  I didn't realize that smaller was after and bigger is before.

On a side note, looks like the 3.0dev branch doesn't recognize style as a block element.

I had the priority backwards. That is a little confusing. I didn't realize that smaller was after and bigger is before.

Yeah, I've made the same mistake a few times myself. But that is how these sorts of libs typically work. A "higher priority" means a "higher number". I just keep that expression in mind: "higher priority" and then it makes sense.


Can't run flutter run --release

I get lot of errors when running command flutter run --release.

xxx@xxx-Inspiron-14-3467:~/Desktop/xxx$ flutter run --release
Multiple devices found:
SM A207F (mobile)                  • R9WMA0D0G7J   • android-arm64 • Android 10 (API 29)
Android SDK built for x86 (mobile) • emulator-5554 • android-x86   • Android 7.1.1 (API 25) (emulator)
[0]: SM A207F (R9WMA0D0G7J)
[1]: Android SDK built for x86 (emulator-5554)
Please choose one: [0|1]: 0

Launching lib/main.dart on SM A207F in release mode...
Running Gradle task 'assembleRelease'...
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.5.2/android/src/main/java/io/flutter/plugins/urllauncher/WebViewActivity.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':connectivity:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > 1 exception was raised by workers:
     com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
     /home/xxx/.gradle/caches/transforms-2/files-2.1/56399ec8cdc895aa561f5aa75e965d03/core-1.0.1/res/values/values.xml:57:5-88:25: AAPT: error: resource android:attr/fontVariationSettings not found.

     /home/xxx/.gradle/caches/transforms-2/files-2.1/56399ec8cdc895aa561f5aa75e965d03/core-1.0.1/res/values/values.xml:57:5-88:25: AAPT: error: resource android:attr/ttcIndex not found.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3m 22s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                     202.7s (!)
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the
incompatibility.
Building plugin connectivity...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    2.0s

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'connectivity'.
> SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s

Exception: The plugin connectivity could not be built due to the issue above.

flutter doctor -v
xxx@xxx:~/Desktop/xxx$ flutter doctor -v
[✓] Flutter (Channel stable, 1.20.2, on Linux, locale en_US.UTF-8)
    • Flutter version 1.20.2 at /home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter
    • Framework revision bbfbf1770c (3 weeks ago), 2020-08-13 08:33:09 -0700
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/xxx/Android/Sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Android Studio (version 3.5)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 41.0.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.37.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.4.1

[✓] Connected device (2 available)
    • SM A207F (mobile)                  • R9WMA0D0G7J   • android-arm64 • Android 10 (API 29)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86   • Android 7.1.1 (API 25) (emulator)

• No issues found!

Hi @tony123S
Please make sure you both flutter and android SDK in local.properties in project's Android folder
> SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

if the problem persists after making these changes, please provide flutter run --release --verbose logs, and a minimal complete reproducible code sample
Thank you

Yes, I have this line in local.properties
sdk.dir=/home/xxx/Android/Sdk

xxx@xxx-Inspiron-14-3467:~/Desktop/xxx$ flutter run --release --verbose
[  +94 ms] executing: [/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/] git -c log.showSignature=false log -n 1
--pretty=format:%H
[  +46 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] bbfbf1770cca2da7c82e887e4e4af910034800b6
[        ] executing: [/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/] git tag --contains HEAD
[ +157 ms] Exit code 0 from: git tag --contains HEAD
[   +1 ms] 1.20.2
[   +7 ms] executing: [/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +5 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/] git ls-remote --get-url origin
[   +5 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +43 ms] executing: [/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/] git rev-parse --abbrev-ref HEAD
[   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +36 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +115 ms] executing: /home/xxx/Android/Sdk/platform-tools/adb devices -l
[  +29 ms] List of devices attached
emulator-5554          device product:sdk_google_phone_x86 model:Android_SDK_built_for_x86 device:generic_x86
transport_id:2
[   +7 ms] /home/xxx/Android/Sdk/platform-tools/adb -s emulator-5554 shell getprop
[  +54 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +136 ms] Found plugin connectivity at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity-0.3.2/
[  +15 ms] Found plugin device_info at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/device_info-0.4.2+4/
[  +11 ms] Found plugin firebase_messaging at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-5.1.8/
[   +8 ms] Found plugin flutter_plugin_android_lifecycle at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_plugin_android_lifecycle-
1.0.8/
[   +3 ms] Found plugin flutter_uploader at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_uploader-1.2.0/
[   +1 ms] Found plugin flutter_webview_plugin at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_webview_plugin-0.3.11/
[   +7 ms] Found plugin image_picker at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.7+4/
[  +24 ms] Found plugin open_file at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/open_file-3.0.1/
[   +4 ms] Found plugin path_provider at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-1.6.11/
[   +1 ms] Found plugin path_provider_linux at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-0.0.1+2/
[   +2 ms] Found plugin path_provider_macos at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-0.0.4+3/
[   +6 ms] Found plugin pdf_render at
/home/xxx/Desktop/flutter_linux_1.20.2-stable/flutter/.pub-cache/hosted/pub.dartlang.org/pdf_render-0.64.1/
[   +3 ms] Found plugin permission_handler at
....
[  +37 ms] "flutter run" took 929ms.
[   +5 ms] Release mode is not supported by Android SDK built for x86.
[   +2 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:476:9)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:860:18)
#3      _rootRunUnary (dart:async/zone.dart:1198:47)
#4      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:529:5)
#9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#11     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#12     _rootRunUnary (dart:async/zone.dart:1198:47)
#13     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#14     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#16     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#17     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#18     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#19     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#20     AndroidDevice.isLocalEmulator (package:flutter_tools/src/android/android_device.dart)
#21     _rootRunUnary (dart:async/zone.dart:1198:47)
#22     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#23     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#24     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#25     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#26     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#27     Future._asyncCompleteWithValue. (dart:async/future_impl.dart:567:7)
#28     _rootRun (dart:async/zone.dart:1190:13)
#29     _CustomZone.run (dart:async/zone.dart:1093:19)
#30     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#31     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
#32     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#33     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#34     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#35     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)
[ +191 ms] ensureAnalyticsSent: 187ms
[   +9 ms] Running shutdown hooks
[   +1 ms] Shutdown hooks complete
[   +2 ms] exiting with code 1

* What went wrong:
A problem occurred configuring root project 'connectivity'.

The issue is came from connectivity. After I upgraded to the latest, it able to run now.


Update dependency neo4j to v5.22.0

This PR contains the following updates:

Package
Type
Update
Change

neo4j (changelog)
project.dependencies
minor
==5.21.0 -> ==5.22.0

Release Notes

neo4j/neo4j-python-driver (neo4j)
v5.22.0: Neo4j Python Driver 5.22.0
Compare Source
https://github.com/neo4j/neo4j-python-driver/wiki/5.x-changelog#5220

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

cf https://github.com/robert-koch-institut/mex-backend/pull/99


fix the clean-up process

Fixes #3428

In file cmd/gitops/beta/run/cleanup.go, this PR changes the signature of the CleanupFunc interface to include an additional logger.Logger parameter, allowing each cleanup function to log independently.

It also adds a check to ensure that the passed function is not nil to avoid resources being left in a dirty state during cleanup.

In file cleanup_test.go, this PR modifies the CleanupFuncs stack to include the Logger object and adds test cases to ensure the stack behaves as expected.
In file cmd/gitops/beta/run/cmd.go, this PR makes several changes including adding a sync package, modifying various functions to enable better logging and error handling during execution, and adding a new cleanup function to properly cancel the context and clean up resources after execution finishes.
In file cmd/gitops/remove/run/cmd.go, this PR changes the text of the --no-session help command flag, and removes unnecessary checks when the flag is set to improve accuracy of the command.
In file install_fluent_bit.go, this PR makes a minor change by increasing the wait time duration for HelmRelease deletion from 1 to 4 seconds to improve the reliability of the deletion process.
In file dashboard.go, this PR adds a sync.Once to prevent multiple calls to close(waitFwd) during port forwarding and ensure smooth operation.
In file pkg/run/watch/install_dev_bucket_server.go, this PR modifies the UninstallDevBucketServer function to delete all resources within the namespace before deleting the namespace itself, ensuring reliable deletion of the dev-bucket namespace and avoiding possible lingering issues.
In file setup_dev_helm.go, this PR reduces the overall waiting time for bucket source and helm reconciliation by modifying the poll interval and using an exponential backoff approach, leading to more efficient deployment while ensuring synchronization is completed successfully.

How to test

gitops run --no-session <some path>
press Ctrl + C randomly, can be many times
if something's go wrong, you would remove the left overs with gitops remove run --no-session implemented by another PR.

When pressing Ctrl+C right after seeing the message ``,
I see the following error message and logs during the next run:
olga@macbook-pro podinfo % /Volumes/Macintosh_HD_Data/_job_ww/_src/weave-gitops/bin/gitops beta run ./deploy/overlays/dev --timeout=3m --port-forward namespace=dev,resource=svc/backend,port=9898:9898  --no-session
► Checking for a cluster in the kube config ...
► Checking if Flux is already installed ...
► Getting Flux version ...
✔ Flux &{v0.41.1  flux-system} is already installed
► Checking namespace gitops-run ...
✔ Created namespace gitops-run
► Checking service gitops-run/run-dev-bucket ...
✔ Created service gitops-run/run-dev-bucket
► Checking deployment gitops-run/run-dev-bucket ...
✔ Created deployment gitops-run/run-dev-bucket
► Waiting for deployment run-dev-bucket to be ready ...
► Port forwarding to pod gitops-run/run-dev-bucket-65c997976-8vt6n ...
✔ Port forwarding for run-dev-bucket is ready.
► creating HelmRepository flux-system/fluent
► creating HelmRelease flux-system/fluent-bit
► creating HelmRelease flux-system/fluent-bit
► waiting for HelmRelease flux-system/fluent-bit to be ready
^C► Received interrupt, quitting...
✗ HelmRelease flux-system/fluent-bit failed to become ready
✗ Fluent Bit installation failed: client rate limiter Wait returned an error: context canceled
Error: client rate limiter Wait returned an error: context canceled
olga@macbook-pro podinfo % /Volumes/Macintosh_HD_Data/_job_ww/_src/weave-gitops/bin/gitops beta run ./deploy/overlays/dev --timeout=3m --port-forward namespace=dev,resource=svc/backend,port=9898:9898  --no-session
► Checking for a cluster in the kube config ...
► Checking if Flux is already installed ...
► Getting Flux version ...
✔ Flux &{v0.41.1  flux-system} is already installed
► Checking namespace gitops-run ...
✔ Namespace gitops-run already existed
► Checking service gitops-run/run-dev-bucket ...
✔ Service gitops-run/run-dev-bucket already existed
✗ Error creating credentials secret: secrets "run-dev-bucket-credentials" already exists
Error: unable to install S3 bucket server: failed creating credentials secret: secrets "run-dev-bucket-credentials" already exists
olga@macbook-pro podinfo %

So, it looks like in this case cleanup does not run. Is it expected behavior?
Tested it twice with the gtiops binary built from the current branch.

This is probably the same issue I observed: if there is an error returned, the cleanup does not run.

Yes, in this case we would use
gitops remove run --no-session
Would you try that?

@chanwit yes, gitops remove run is working, the problem is that cleanup only runs after pressing Ctrl+C after everything or almost everything has finished running (before subsequent reconciliation), I mean around the port-forward messages are displayed.
For example, here is another example of cleanup not running when pressing Ctrl+C during normal gitops run execution, but this time after the request reconciliation of dashboard (timeout 3m0s) message:
olga@macbook-pro podinfo % /Volumes/Macintosh_HD_Data/_job_ww/_src/weave-gitops/bin/gitops beta run ./deploy/overlays/dev --timeout=3m --port-forward namespace=dev,resource=svc/backend,port=9898:9898  --no-session
► Checking for a cluster in the kube config ...
► Checking if Flux is already installed ...
► Getting Flux version ...
✔ Flux &{v0.41.1  flux-system} is already installed
► Checking namespace gitops-run ...
✔ Created namespace gitops-run
► Checking service gitops-run/run-dev-bucket ...
✔ Created service gitops-run/run-dev-bucket
► Checking deployment gitops-run/run-dev-bucket ...
✔ Created deployment gitops-run/run-dev-bucket
► Waiting for deployment run-dev-bucket to be ready ...
► Port forwarding to pod gitops-run/run-dev-bucket-6c55859dfb-5ws7n ...
✔ Port forwarding for run-dev-bucket is ready.
► creating HelmRepository flux-system/fluent
► creating HelmRelease flux-system/fluent-bit
► creating HelmRelease flux-system/fluent-bit
► waiting for HelmRelease flux-system/fluent-bit to be ready
✔ HelmRelease flux-system/fluent-bit is ready
► Checking if GitOps Dashboard is already installed ...
Would you like to install the GitOps Dashboard: y
Please enter a password for logging into the dashboard:
► Creating GitOps Dashboard objects ...
✚ Generating GitOps Dashboard manifests ...
► Installing the GitOps Dashboard ...
✔ GitOps Dashboard has been installed
► Request reconciliation of dashboard (timeout 3m0s) ...
^C► Received interrupt, quitting...
✗ Error requesting reconciliation of dashboard: client rate limiter Wait returned an error: context canceled
► Checking secret run-dev-bucket-credentials ...
Error: failed fetching secret flux-system/run-dev-bucket-credentials: client rate limiter Wait returned an error: context canceled

olga@macbook-pro podinfo % /Volumes/Macintosh_HD_Data/_job_ww/_src/weave-gitops/bin/gitops beta run ./deploy/overlays/dev --timeout=3m --port-forward namespace=dev,resource=svc/backend,port=9898:9898  --no-session
► Checking for a cluster in the kube config ...
► Checking if Flux is already installed ...
► Getting Flux version ...
✔ Flux &{v0.41.1  flux-system} is already installed
► Checking namespace gitops-run ...
✔ Namespace gitops-run already existed
► Checking service gitops-run/run-dev-bucket ...
✔ Service gitops-run/run-dev-bucket already existed
✗ Error creating credentials secret: secrets "run-dev-bucket-credentials" already exists
Error: unable to install S3 bucket server: failed creating credentials secret: secrets "run-dev-bucket-credentials" already exists

olga@macbook-pro podinfo % /Volumes/Macintosh_HD_Data/_job_ww/_src/weave-gitops/bin/gitops remove run --no-session
► Deleting HelmRelease run-dev-helm ...
► Deleting secret run-dev-bucket-credentials ...
► Deleting source run-dev-bucket ...
✔ Cleanup Bucket Source and HelmRelease successfully
► Deleting Kustomization run-dev-ks ...
► Deleting secret run-dev-bucket-credentials ...
► Deleting source run-dev-bucket ...
✔ Cleanup Bucket Source and Kustomization successfully
► Deleting deployment gitops-run/run-dev-bucket ...
► Deleting service gitops-run/run-dev-bucket ...
► Deleting secret gitops-run/run-dev-bucket-credentials ...
► Deleting secret gitops-run/dev-bucket-server-certs ...
► Deleting namespace gitops-run ...
► Waiting for resources to be terminated ...
✔ Resources terminated
► Removing Fluent Bit HelmRelease flux-system/fluent-bit ...
► Waiting for HelmRelease flux-system/fluent-bit to be deleted...
✔ HelmRelease flux-system/fluent-bit deleted
✔ HelmRepository flux-system/fluent deleted

So, for the cleanup to run while terminating gitops run we need to wait to press Ctrl+C (almost) until the port-froward messages are displayed. It might be confusing to the user — why pressing Ctrl+C requires additional cleanup (running gitops remove run) in some cases only.

@opudrovs that what we had discussed as the ctrl +c handling cannot be 100% perfect and we would use `gitops remove run --no-session" to clean up afterwards


Make RandomIoUCrop compatible with SanitizeBoundingBoxes

The recent changes you made LGTM @pmeier - thanks a lot for catching the bugs and for the fixes. Happy to merge on my side (can't approve myself)


[KYUUBI #6297] Package Spark SQL engine both Scala 2.12 and 2.13

:mag: Description
Issue References 🔗

This pull request fixes #6297
Describe Your Solution 🔧
Here are my main modifications:

In the build/dist file, I added an additional packaging command that detects the version of SCALA_VERSION. If it is version 2.12, then it will additionally package version 2.13, otherwise it will package version 2.12
In the section of # Copy spark engines, the Jar packages of versions 2.12 and 2.13 will be moved to $DISTDIR/externals/engines/spark/

This is my first time submitting a PR, so there may be many unfamiliar areas, and I don't know if my changes meet the needs of the community. More guidance may be needed. When testing locally, it was able to be packaged successfully
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

@PorterZhang2021 thanks for making this PR. We haven't tested the scripts under Cygwin, but only macOS and Linux, it would be good to add a manual E2E test - create a kyuubi tarball, and use it to bootstrap both Spark 2.12 and 2.13 engines.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.43%. Comparing base (37bf244) to head (b6c9075).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #6305      +/-   ##
============================================
- Coverage     58.49%   58.43%   -0.06%
  Complexity       24       24
============================================
  Files           652      652
  Lines         39645    39645
  Branches       5454     5454
============================================
- Hits          23190    23168      -22
- Misses        13965    13986      +21
- Partials       2490     2491       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@PorterZhang2021 thanks for making this PR. We haven't tested the scripts under Cygwin, but only macOS and Linux, it would be good to add a manual E2E test - create a kyuubi tarball, and use it to bootstrap both Spark 2.12 and 2.13 engines.感谢你做这个PR。我们还没有在Cygwin下测试这些脚本，但只测试了macOS和Linux下的脚本，最好添加一个手动的E2E测试——创建一个kyubi tarball，并用它来引导Spark 2.12和2.13引擎。

ok, I will try it, thanks for your help.

@pan3793 @yikf Hello everyone, I have attempted to make a new modification based on your feedback. However, removing '$@' resulted in a build error, so I did not make any changes.
The following results are from E2E test:

when I use spark 1.2

when I use spark 1.3

Thanks, merged to master

Hello, everyone @pan3793 @yikf, I have tried two solutions, and the following is my train of thought:
Solution 1
Steps
I found a way to use <profiles>, roughly as follows:
<profiles>
        <profile>
            <id>scala-2.12</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>
                <scala.binary.version>2.12</scala.binary.version>
            </properties>
        </profile>
        <profile>
            <id>scala-2.13</id>
            <properties>
                <scala.binary.version>2.13</scala.binary.version>
            </properties>
        </profile>
    </profiles>

After specifying, I attempted to use

/ Build/mvn install - DskipTests - Dmaven. savadoc. skip=true - Dmaven. scaladoc. skip=true - Dmaven. source. skip - Pscala-2.12- Pscala-2.13- pl: kyuubi spark SQL engine - am
/ Build/mvn install - DskipTests - Dmaven. savadoc. skip=true - Dmaven. scaladoc. skip=true - Dmaven. source. skip - Pscala-2.13- Pscala-2.12- pl: kyuubi spark SQL engine - am

Problem
But in the end, it was found that if both '- Pscala2.12' and '- Pscala2.13' are used at the same time, '- Pscala2.13' will be selected by default, which may not be a good solution to this problem.
Solution 2
Later, I thought about whether it was possible to filter the parameter '$@' internally. I tried writing the following code
Steps

code

filtered_args=()
for arg in "$@"; do
    if [ "$arg" != "-Pscala2.12" ]; then
        filtered_args+=("$arg")
    fi
done

echo "mvn install ${filtered_args[@]}"

test
then I try it, after using the  /test-shell.sh -Pscala2.12 -Etest command, the final result is as follows：

This approach seems to meet our requirements. If you think this solution can be tried, I will conduct testing. At the same time, I also hope that you can provide me with some parameters that may be needed for $@, so that I can conduct some testing to prevent any problems from occurring.
Thank you for your help and review.

Cherry-picked to 1.9.1 to support Spark 4.0.0-preview1


[ Settings > Variables ] Able to create variables with names that will cause flux errors

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Open Settings > Variables
Click Create Variable > New Variable
Name the variable "test" or "My-Var"
Proceed to define the type and keys or a query and save.
Open a dashboard cell script editor and add the variable to the script.
Click submit, or otherwise refresh the preview

Expected behavior:
Describe what you expected to happen.
When creating the variable, expected that a variable named using a keyword (e.g. "test","import") or one using characters that can be interpreted in flux as mathematical or other operators, would be flagged with a warning or prohibited.
Actual behavior:
Describe What actually happened.
I am able to create such variables and, when they are added to a flux script, result in 500 backend internal server errors, some of which are quick to understand, others less so (e.g. did not know that 'test' is a reserved keyword.
Screenshots

Screencasts

Environment info:

System info: Run uname -srm and copy the output here

Linux 4.15.0-88-generic x86_64

InfluxDB version: Run influxd version and copy the output here
Detected in nightly build.

ts=2020-02-19T09:11:11.599024Z lvl=info msg="Welcome to InfluxDB" log_id=0L3BI9wl000 version=nightly commit=b24be19b5 build_date=2020-02-19T09:11:11Z

Other relevant environment details: Container runtime, disk info, etc

Browser: Chrome 80
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Started with e2e testing enabled.
--e2e-testing=true

Logs:
Include snippet of errors in log.
Performance:
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.
# Commands should be run when the bug is actively happening.
# Note: This command will run for at least 30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"
curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz`, `vars.txt`, and `iostat.txt` output files.

maybe we need validation at the api to only allow values that fit this definition: https://github.com/influxdata/flux/blob/master/docs/SPEC.md#identifiers

I created a variable that had a space in the name (foo bar), and when I clicked in the UI to use that variable, it input v.foo bar. I expected the UI to understand that it needed to insert v["foo bar"].

this is the root cause of #17564 . @bthesorceror can give more details.


Potions / Status Effects

Objective

Potion effects aren't supported by valence yet.
You can send a packet to tell the client about a potion effect, but the server still has no idea what they are

Example code
pub fn add_potion_effect(mut clients: Query<&mut Client>, mut events: EventReader<SneakEvent>) {
    for event in events.iter() {
        if event.state == SneakState::Start {
            if let Ok(mut client) = clients.get_mut(event.client) {
                client.write_packet(&EntityStatusEffectS2c {
                    entity_id: VarInt(0),
                    effect_id: VarInt(22),
                    amplifier: 0,
                    duration: VarInt(600),
                    flags: entity_status_effect_s2c::Flags::new()
                        .with_show_particles(true)
                        .with_show_icon(true),
                    factor_codec: None,
                });
            }
        }
    }
}

Closes #401
Also, when the potion effect expires, we need to tell the client that their potion effect is no longer. Right now, with sending a packet, the effect doesn't get removed when it goes down to 00:00.

Solution
I want to add the necessary components and stuff to facilitate potion effects.

Note: I'm still somewhat new to rust and very new to bevy, so please lmk if I can improve anything or if I should do anything differently. Thanks!

To do:

[x] Extractor
[x] ActiveStatusEffects component to handle the actual status effect applied to the mc entity
[x] Add ActiveStatusEffects component to all entities.
[x] Make a plugin to handle potion effects

[x] Decrease tick count
[x] Remove effect (& tell client) when tick count is 0
[ ] Make the effects do stuff

[x] Particles
[x] Tell client
[x] Glowing/invisible
[ ] Health, damage, heal. See #556

Instant health/damage
Regen/poison/wither

[ ] Absorption. See #557
[ ] EntityAttributes. See #555

Speed/Slowness
Haste/Mining fatigue
Strengh/Weakness
Health boost
Luck/Unluck

[ ] Add tests
[x] Add example

Playground

Current playground
use valence::client::despawn_disconnected_clients;
use valence::entity::active_status_effects::{ActiveStatusEffect, ActiveStatusEffects};
use valence::entity::status_effects::StatusEffect;
use valence::log::LogPlugin;
use valence::network::ConnectionMode;
use valence::prelude::*;

#[allow(unused_imports)]
use crate::extras::*;

const SPAWN_Y: i32 = 64;

pub fn build_app(app: &mut App) {
    app.insert_resource(NetworkSettings {
        connection_mode: ConnectionMode::Offline,
        ..Default::default()
    })
    .add_plugins(DefaultPlugins.build().disable::<LogPlugin>())
    .add_systems(Startup, setup)
    .add_systems(EventLoopUpdate, add_potion_effect)
    .add_systems(Update, (init_clients, despawn_disconnected_clients))
    .run();
}

fn setup(
    mut commands: Commands,
    server: Res<Server>,
    biomes: Res<BiomeRegistry>,
    dimensions: Res<DimensionTypeRegistry>,
) {
    let mut layer = LayerBundle::new(ident!("overworld"), &dimensions, &biomes, &server);

    for z in -5..5 {
        for x in -5..5 {
            layer.chunk.insert_chunk([x, z], UnloadedChunk::new());
        }
    }

    for z in -25..25 {
        for x in -25..25 {
            layer
                .chunk
                .set_block([x, SPAWN_Y, z], BlockState::GRASS_BLOCK);
        }
    }

    commands.spawn(layer);
}

fn init_clients(
    mut clients: Query<
        (
            &mut EntityLayerId,
            &mut VisibleChunkLayer,
            &mut VisibleEntityLayers,
            &mut Position,
            &mut GameMode,
        ),
        Added<Client>,
    >,
    layers: Query<Entity, (With<ChunkLayer>, With<EntityLayer>)>,
) {
    for (
        mut layer_id,
        mut visible_chunk_layer,
        mut visible_entity_layers,
        mut pos,
        mut game_mode,
    ) in &mut clients
    {
        let layer = layers.single();

        layer_id.0 = layer;
        visible_chunk_layer.0 = layer;
        visible_entity_layers.0.insert(layer);
        pos.set([0.0, SPAWN_Y as f64 + 1.0, 0.0]);
        *game_mode = GameMode::Survival;
    }
}

pub fn add_potion_effect(
    mut clients: Query<&mut ActiveStatusEffects>,
    mut events: EventReader<SneakEvent>,
) {
    for event in events.iter() {
        if event.state == SneakState::Start {
            if let Ok(mut status) = clients.get_mut(event.client) {
                status.add(
                    ActiveStatusEffect::from_effect(StatusEffect::Wither)
                        .with_amplifier(2)
                        .with_duration(200),
                );
            }
        }
    }
}

This is getting rather large. Were you planning to handle #555 and #556 in separate PRs? That would make stuff easier to review.

This is getting rather large. Were you planning to handle #555 and #556 in separate PRs? That would make stuff easier to review.

yes, #555 and #556 (+#557) are very much out of the range of this PR. I'll probably also have to wait for those to be implemented before I can finish potions off.

Also, splitting the new extractor and supporting rust code into a new PR would help with size here.

oh okay I could try that

Is this feature finished? I want it to be merged into the main branch.

Is this feature finished? I want it to be merged into the main branch.

Yeah. Please review it, though, before merging it, just to make sure. It's been a while since I touched it so I don't know if it's outdated or anything

I've just tested on my machine, effect statuses seems to work fine.
I suppose that only several effects are client-sided and others should be implemented manually.
The only question is how these effects would be implemented by users, for example slowness effect.
My suggestion is to add a snippet of code in the example where one of server-sided effects is implemented.

My suggestion is to add a snippet of code in the example where one of server-sided effects is implemented.

I'm trying to do that right now (admittedly, I should've done this earlier), but I now realise that I also need to slightly change how EntityAttributes work in valence (I made them too btw) to have feature parity with vanilla minecraft. I made this decision:
/// Right now, uses a random UUID for the modifier UUIDs.
///
/// Minecraft actually uses constant UUIDs. Uncertain if
/// I should do the same.

I'll make a new pr to change the decision to actually use UUIDs instead of arbitrary names because in hindsight, that's a pretty stupid decision lmao.

kk I made #591

ok I did a few things.


[T7][W13-B4]

update the following documentations:

user guide
developer guide

The User Guide has been reviewed. The DevGuide will be reviewed soon, so do not close this PR yet.


PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing)

The original project was running well, and everything logged in was normal. No code changes have been made, only the latest version of Vapor has been updated. As a result, the app's account cannot be logged in.
If you intentionally use the wrong account password to log in, you will normally report that your identity has not been verified.
But if the correct account password is used for login, it will report:
PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing)
It's really strange to have this problem. Once again, confirm that the original project code has not been changed. Everything was originally normal.
I am using the Postgres database.
I tried using both the old and new versions of the database registration API, but the problem remained the same.
I am trying to write a routing method to read the database content, and using a Postman request, I can successfully obtain the data content. But logging in using Postman or app and using the correct account and password will result in an error:
PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing)
If the wrong account password is used, it will be reported that the identity has not been verified.
I am using Basic Auth provided by Vapor.
The premise is that everything was running normally.

The cause of the problem
If you initially configured the database connection certificate in Vapor, but your certificate may be expired or invalid. You may want to give up configuring the certificate, so you changed TLS to .disable, and you will encounter the following error message: PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing) . No matter how you clear the Xcode cache, you cannot solve this error.
Solution to the problem
Unless you re enable the TLS certificate and it is valid. Then the error message will disappear.
postscript
The possible cause of this issue may be due to issues with the code for TLS certificates in PostgresNIO. I hope the relevant person in charge of Vapor can improve it as soon as possible.
My English is not good, I rely entirely on translation, and some expressions may not be appropriate. You can only understand on your own.
Finally, roast that your forum is too slow to participate in the reply. I hope there can be more improvements.

This bug is very strange. It will work for a while, but it won't work again.

The cause of the problem
If there are multiple fields in the model, it is easier to understand when reporting an error in versions before Vapor 4.77.0, while in version 4.77.0, it will report PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c) The mistake of 'Backing' makes people confused.