jeremyjpj0916
jeremyjpj0916
Wow, yep not running in debug mode just yet again, but just by the time in dev it went for DNS warmup times from 20-30 seconds down to 1.4 seconds....
And lastly the debug logs post fix confirming the proper behavior carried through to the workers: ``` 2024-06-27T10:55:35.642893875-05:00 2024/06/27 15:55:35 [notice] 48#0: *1300 [lua] warmup.lua:47: warming up DNS entries ...,...
Even my stage environment with the fixes is super improved: ``` 2024-06-27T12:04:07.707289028-05:00 2024/06/27 17:04:07 [notice] 48#0: *1992 [lua] warmup.lua:81: finished warming up DNS entries' into the cache (in 3802ms), context:...
@chobits Why would this be closed? Kong nginx workers do not respect the ENV variable settings mentioned in the conf ootb until Kong includes those ENV vars either in your...
@chobits ah gotcha, internal ticket and the option of updating documentation on how to achieve the settings seems reasonable too.
Seems the login functionality is busted: ``` @Jeremys-Mini workspace % python3 meta_ai.py Traceback (most recent call last): File "/Users/jeremyjustus/workspace/meta_ai.py", line 2, in ai = MetaAI(fb_email="[email protected]", fb_password="XXXXXX") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/homebrew/lib/python3.11/site-packages/meta_ai_api/main.py", line...
@chronolaw Where does Kong's documentation or files state "traditional_compatible mode only supports path_handling = v0" ? And the runtime makes no mention of this either.  Kong should be working...
Gotcha, yeah if I hadn't reviewed that admin api notes section I would not see this: "Note: Path handling algorithms v1 was deprecated in Kong 3.0. From Kong 3.0, when...
Interesting, using a uuid as the consumer username must be tricking Kong under the hood 😄 . Because the URI of the admin api endpoint expects a username or uuid,...
router_flavor = traditional_compatible we do not override this field so it stays defaulted to this in our runtimes.