Built-in script to quantize with AutoGPTQ then push to Huggingface

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
The final model uses much less VRAM & faster inference speeds (e.g. especially ExLlama).
✔ Solution
See https://github.com/PanQiWei/AutoGPTQ/tree/main#quantization-and-inference

[ ] Convert Axolotl config & dataset into quantization dataset

⭐ This is why integrating with Axolotl is especially interesting, reusing the same prompt strategies/dataset handling code

[ ] Quantize

[ ] Logging progress to WandB

[ ] Save safetensors model
[ ] Push model
[ ] Push model README and other files

❓ Alternatives
No response
📝 Additional Context
No response
Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this feature has not been requested yet.
[X] I have provided enough information for the maintainers to understand and evaluate this request.

My WIP code I've been using personally, happy to share & integrate with Axolotl 😃  Although I appreciate any code review feedback, since I'm less familiar with Python and these libraries.
Adapted from https://github.com/PanQiWei/AutoGPTQ/blob/main/examples/quantization/quant_with_alpaca.py
With help from ChatGPT4, here's what I have so far and has been working successfully (Change me variables are untested):
# pip install auto-gptq --extra-index-url https://huggingface.github.io/autogptq-index/whl/cu118/

import json
import random
import time

import torch
from datasets import load_dataset, Dataset
from transformers import AutoTokenizer, LlamaTokenizer, TextGenerationPipeline
from auto_gptq import AutoGPTQForCausalLM, BaseQuantizeConfig
from axolotl.prompters import AlpacaPrompter
import logging

logging.basicConfig(
    format="%(asctime)s %(levelname)s [%(name)s] %(message)s", level=logging.DEBUG, datefmt="%Y-%m-%d %H:%M:%S"
)

print("Done importing...")

## CHANGE BELOW ##
pretrained_model_dir = "facebook/opt-125m"
quantized_model_dir = "opt-125m-4bit"
dataset_name = "teknium/GPT4-LLM-Cleaned"
huggingface_username = "CHANGE_ME"
## CHANGE ABOVE

quantize_config = BaseQuantizeConfig(
    bits=4,  # quantize model to 4-bit
    group_size=128,  # it is recommended to set the value to 128
    desc_act=False,  # set to False can significantly speed up inference but the perplexity may slightly bad
)

# TEMPLATE = "<|prompt|>{instruction}</s><|answer|>"
prompter = AlpacaPrompter()

# def load_data(data_path, tokenizer, n_samples, template=TEMPLATE):
def load_data(data_path, tokenizer, n_samples):
    # Load dataset
    dataset = load_dataset(data_path)

    if "train" in dataset:
        raw_data = dataset["train"]
    else:
        raw_data = dataset

    # Sample from the dataset if n_samples is provided and less than the dataset size
    if n_samples is not None and n_samples < len(raw_data):
        raw_data = raw_data.shuffle(seed=42).select(range(n_samples))

    def tokenize(examples):
        instructions = examples["instruction"]
        outputs = examples["output"]

        prompts = []
        texts = []
        input_ids = []
        attention_mask = []
        for input_text, output_text in zip(instructions, outputs):
            # prompt = template.format(instruction=input_text)
            # prompt = next(prompter.build_prompt(instruction=input_text, output=output_text))
            prompt = next(prompter.build_prompt(instruction=input_text))
            text = prompt + output_text

            if len(tokenizer(prompt)["input_ids"]) >= tokenizer.model_max_length:
                continue

            tokenized_data = tokenizer(text)

            input_ids.append(tokenized_data["input_ids"][: tokenizer.model_max_length])
            attention_mask.append(tokenized_data["attention_mask"][: tokenizer.model_max_length])
            prompts.append(prompt)
            texts.append(text)

        return {
            "input_ids": input_ids,
            "attention_mask": attention_mask,
            "prompt": prompts,
            "text": texts,
        }

    raw_data = raw_data.map(
        tokenize,
        batched=True,
        batch_size=len(raw_data),
        num_proc=1,
        keep_in_memory=True,
        load_from_cache_file=False,
        # remove_columns=["instruction", "input"]
    )

    # Convert to PyTorch tensors
    raw_data.set_format(type='torch', columns=['input_ids', 'attention_mask'])

    # for sample in dataset:
    #     sample["input_ids"] = torch.LongTensor(sample["input_ids"])
    #     sample["attention_mask"] = torch.LongTensor(sample["attention_mask"])

    return raw_data

def get_tokenizer():
    print("Loading tokenizer...")
    # tokenizer = AutoTokenizer.from_pretrained(pretrained_model_dir, use_fast=True)
    tokenizer = LlamaTokenizer.from_pretrained(pretrained_model_dir, use_fast=True)
    return tokenizer

def get_model():
    print("Loading model...")
    # load un-quantized model, by default, the model will always be loaded into CPU memory
    model = AutoGPTQForCausalLM.from_pretrained(pretrained_model_dir, quantize_config)
    print("Model loaded.")
    return model

def get_quantized_model():
    print("Loading quantized model...")
    model = AutoGPTQForCausalLM.from_quantized(quantized_model_dir, device="cuda:0")
    print("Model loaded.")
    return model

def quantize(model, examples_for_quant):
    print("Quantize...")
    start = time.time()
    # quantize model, the examples should be list of dict whose keys can only be "input_ids" and "attention_mask"
    model.quantize(
        examples_for_quant,
        batch_size=1,
        # batch_size=args.quant_batch_size,
        # use_triton=args.use_triton,
        # autotune_warmup_after_quantized=args.use_triton
    )
    end = time.time()
    print(f"quantization took: {end - start: .4f}s")

    # save quantized model
    print("Saving quantized model...")
    # model.save_quantized(quantized_model_dir)
    model.save_quantized(quantized_model_dir, use_safetensors=True)
    print("Saved.")

    return model

def push_model(model):
    # push quantized model to Hugging Face Hub.
    # to use use_auth_token=True, Login first via huggingface-cli login.
    # or pass explcit token with: use_auth_token="hf_xxxxxxx"
    # (uncomment the following three lines to enable this feature)
    # repo_id = f"YourUserName/{quantized_model_dir}"
    print("Pushing to Huggingface hub...")
    repo_id = f"{huggingface_username}/{quantized_model_dir}"
    commit_message = f"AutoGPTQ model for {pretrained_model_dir}: {quantize_config.bits}bits, gr{quantize_config.group_size}, desc_act={quantize_config.desc_act}"
    # model.push_to_hub(repo_id, commit_message=commit_message, use_auth_token=True, use_safetensors=True, safe_serialization=True)
    # model.push_to_hub(repo_id, commit_message=commit_message, use_auth_token=True, safe_serialization=True)
    model.push_to_hub(repo_id, commit_message=commit_message, use_auth_token=True, use_safetensors=True)

# def push_tokenizer(tokenizer):

def main():
    print("Starting...")
    # return
    # prompt = "<|prompt|>How can entrepreneurs start building their own communities even before launching their product?</s><|answer|>"

    should_quantize = True
    tokenizer = get_tokenizer()

    if should_quantize:
        print("Quantizing...")
        model = get_model()
        examples = load_data(dataset_name, tokenizer, 128)

        # print(examples)
        examples_for_quant = [
            {"input_ids": example["input_ids"], "attention_mask": example["attention_mask"]}
            for example in examples
        ]
        # print(examples_for_quant)

        modelq = quantize(model, examples_for_quant)
    else:
        print("Loading quantized model...")
        modelq = get_quantized_model()

    push_model(modelq)

main()

As I understand, it’s possible to quantize also via GPTQ for llama. I personally use this latter method.
I’m not sure what’s the difference between them?
Perhaps, we’ll need TheBloke to clarify?

I was unsuccessful quantizing https://github.com/qwopqwop200/GPTQ-for-LLaMa and when I posted in TheBloke Discord server and spoke to TheBloke and was recommended AutoGPTQ: https://discord.com/channels/1111983596572520458/1117037259603066980/1130502655500881970

Interesting to know. Last I talked with him, he used gptq for llama. I guess times have changed.

Update: Quantization working!
Quantize automatically with Axolotl with no custom scripts required.
:white_check_mark: Rewrote AutoGPTQ's advanced quantization script to leverage Axolotl config & internal functions (loading tokenizer & models, merging models, loading datasets all from Axolotl config .yml file): https://github.com/PanQiWei/AutoGPTQ/blob/main/examples/quantization/quant_with_alpaca.py
:construction: Will add another callback to automatically merge and quantize upon completion, if enabled in config

PR ready for review/testing/feedback: https://github.com/OpenAccess-AI-Collective/axolotl/pull/545


Problems with Windows 10. Tasks are scheduled, repetitions is postponed on each cycle, but are not attempted to run

This is a very strange issue.
I've been using your library for almost a year now (thank you!) and never encountered any issue that wasn't from my own errors.
Now I've found out that the same task configuration that works perfectly under Windows 7 and 8, on x86/x64 and different languages, is failing on Windows 10.
I've tested on 2 different virtual machines, using different Windows 10 installation files and I have the same strange behavior on both.
Basically tasks won't launch when supposed to by daily or login repetition triggers.
They can also be launched manually and launch once on user login, but but repetitions are postponed each time they should run, without any indication that they were attempted to run on tasks history (it is enabled).
There are no conditions I can see that would prevent them to be run (such as being on battery or only on idle). Plus, like I mentioned the exact same program is able to create scheduled tasks which execute flawlessly on previous Windows version.
I even exported the XML from a Windows 7 x64, imported it into a clean Windows 10 VM and it has the same issue.
I'm pasting the XML export of the task, do you need any part of the code?
I think the XML is easier to follow, but let me know if you'd like the code.
Please let me know if you need further information.
Any help would be greatly appreciated, since now we are over 20% of adoption for Windows 10, so this is affecting me greatly.
Thank you.
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Date>2016-06-02T16:32:22.334-08:00</Date>
    <Description>Test</Description>
    <URI>\TestTask</URI>
  </RegistrationInfo>
  <Triggers>
    <CalendarTrigger>
      <Repetition>
        <Interval>PT15M</Interval>
        <StopAtDurationEnd>false</StopAtDurationEnd>
      </Repetition>
      <StartBoundary>2016-06-02T16:32:22.334-08:00</StartBoundary>
      <Enabled>true</Enabled>
      <ScheduleByDay>
        <DaysInterval>1</DaysInterval>
      </ScheduleByDay>
    </CalendarTrigger>
    <LogonTrigger>
      <Repetition>
        <Interval>PT15M</Interval>
        <StopAtDurationEnd>false</StopAtDurationEnd>
      </Repetition>
      <Enabled>true</Enabled>
      <Delay>PT1M</Delay>
    </LogonTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>S-1-5-21-2302200855-1744179440-2378765128-1002</UserId>
      <LogonType>InteractiveToken</LogonType>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>true</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <Duration>PT10M</Duration>
      <WaitTimeout>PT1H</WaitTimeout>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>C:\Users\user\Downloads\TestTask.exe</Command>
    </Exec>
  </Actions>
</Task>

Originally posted: 2016-12-04T20:44:48

I'm curious, could the task still be running from the last execution? I noticed you don't have MultipleInstancesPolicy set to terminate or run a new instance. I was able to load the XML on my Win10 instance. Also you should know that these two triggers do the same thing and you are effectively running it twice every 15 minutes.
Originally posted: 2016-12-06T15:01:41

Hi Dahall, thanks for your reply.
The task was not running, I could see status was "Ready" and I was monitoring for an executable run by this and it was not present on task manager.
If I switch from Calendar to Time trigger, it works perfectly. Obviously that forces me have to re-register the task each time it is run.
My reasoning for running it on both login and calendar/time trigger is that if the computer is rebooted, I want the task to run as soon as possible and not have to wait 15 - X minutes to start. The program closes itself if it detects another instance running.
Was the task triggered on your Windows 10 instance after loading it? I don't know, it might be a bug on my particular release, but it happened with 2 different installation mediums.
Thank you.
Originally posted: 2016-12-14T08:14:43

I was unable to duplicate your error on either Win10 systems I have. I have made some changes to limit the repetitive runs after the logon trigger and explicitly set the MultipleInstancesPolicy:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2016-06-02T16:32:22.334-08:00</Date>
<Description>Test</Description>
<URI>\TestTask</URI>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<Repetition>
<Interval>PT15M</Interval>
<StopAtDurationEnd>false</StopAtDurationEnd>
</Repetition>
<StartBoundary>2016-06-02T17:32:22-07:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
<LogonTrigger>
<Enabled>true</Enabled>
<Delay>PT1M</Delay>
</LogonTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-21-839522115-1383384898-515967899-301783</UserId>
<LogonType>InteractiveToken</LogonType>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>Parallel</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>C:\Users\user\Downloads\TestTask.exe</Command>
</Exec>
</Actions>
</Task>
Originally posted: 2017-01-10T09:34:32

It's a must for windows 10: set start date and time to be in future (near future, just 1 minute), task will be triggered and will repeat at specific interval.
Originally posted: 2017-03-24T02:09:01


fixes #53 and #51

@JakeHartnell If you prefer, I can remove the ES6 features (arrow functions, etc.) from the PR?


Add scripts to brushes using entities?

In Qodot, it's possible to convert particular brushes into godot objects with scripts attached, ie: you can model doors and have godot automatically attach a door script to allow it to open and add variables to it in trenchbroom (such as door lock types or whatever). Is this currently possible in TBLoader?

Yep, it can be done with brush entities, you create an entry in the fgd and apply it to a brush, then just have a tscn that inherits Node3D that matches the name in the entities folder and it'll attach the mesh and collision to it.


[Pull Request]: Added "daily" games feature in chess.com

You might be aware of daily games, which goes for days. So, I have added the daily feature, with the default live route, you can't analyze daily games. For that i have added daily route too. Please check and lmk.

Hi @tausiq2003 thanks for the PR!
I missed daily games and didn't realize it had a different endpoint. I will have a look when I'm free. Meanwhile you can remove the console logs added. I believe they were added for testing :)

done, thanks for the repo btw, i was looking for this, building something.

on second thought i think it would be better to separate routes for daily and live since daily doesn't use the concept of timestamps. What do you think?

Yup, that will be good
On Thu, 21 Nov, 2024, 00:32 Chathulanka Gamage, @.***>
wrote:

on second thought i think it would be better to separate routes for daily
and live since daily doesn't use the concept of timestamps. What do you
think?
—
Reply to this email directly, view it on GitHub
https://github.com/cmgchess/chesscom-pgn/pull/9#issuecomment-2489338484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATDAXXOIBECAMPV65YG5IO32BTMD3AVCNFSM6AAAAABSEIKKFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGMZTQNBYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Btw do you have rate limiting in this api?
On Thu, 21 Nov, 2024, 00:45 Tausiq Samantaray, @.***>
wrote:

Yup, that will be good
On Thu, 21 Nov, 2024, 00:32 Chathulanka Gamage, @.***>
wrote:

on second thought i think it would be better to separate routes for daily
and live since daily doesn't use the concept of timestamps. What do you
think?
—
Reply to this email directly, view it on GitHub
https://github.com/cmgchess/chesscom-pgn/pull/9#issuecomment-2489338484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATDAXXOIBECAMPV65YG5IO32BTMD3AVCNFSM6AAAAABSEIKKFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGMZTQNBYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I haven't implemented any rate limiting myself. If you are facing such maybe vercel is doing it by themselves since I'm using a free deployment.

ok ig you will merge it if i fix the timestamp thing, can you elaborate like how to? i mean what to do?

instead of the dynamic [gameFormat] you could create 2 separate folders for live and daily.
so live/game/[gameId] and daily/game/[gameId]. both of them can have separate route.ts files. The rest is just the same except you don't have to accept timestamps from query params. For the moveTimes parameter in getPgnFromUCI you could pass an empty []. The route doc is also easier since no timestamps needed

check it out, if some changes needed lmk

lgtm

please merge it then.

Thanks for the contribution @tausiq2003 :)


write hello world in crystal

i am working on it please add hacktoberfest tag on it and assign this to me

hey @trishan9 i have made a PR #225 can u plzz review it and merge

hey @trishan9 i have made a PR #225 can u plzz review it and merge

Sure!

Your PR has been merged under Hacktoberfest @Rudra-choudhary

Happy contribution!


Cannot return null for non-nullable field Model._version.

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
16.1.0
Amplify CLI Version
7.6.9
What operating system are you using?
Ubuntu 18.04
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No.
Amplify Categories
storage, api
Amplify Commands
Not applicable
Describe the bug
Created new record in model using amplify graphql, when listing the record getting this error.
Cannot return null for non-nullable field Model._version.
Where Model is name of my model.
Expected behavior
List all the records in that Model.
Reproduction steps
amplify mock api.
Create new data using api from mock, then try to list all data with _version checked.
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

seeing the same issue here- is there a workaround?

update - seems my local issue may be related to AmplifyCLI: https://github.com/aws-amplify/amplify-category-api/issues/46


Redirect to previous url when deleting/copying/unpublish a page

This fixes #3010 appending the next querystring parameter to the "Delete", "Copy" and "Unpublish" actions.
Waiting for feedbak,
Carlo

@carloratm - is this your PR? the original PR is now being submitted from a deleted user.
If so, thanks so much for submitting this.

Merged in via 5f3c12682fe5f93de6a0f614ab4af89d8518e807

I've just unexpectedly hit this change on a site:

TypeError: page_listing_more_buttons() takes from 2 to 3 positional arguments but 4 were given

We should at least add an upgrade consideration as this is a breaking change

@kaedroho I did not think of that when merging this in, happy to do a PR for a release notes update to reflect this.
Or do you think we should pull in **kwargs  instead?
any thoughts @gasman  ?

Weird, I thought I'd replied on this, unless there was another recent PR with a similar outcome...
This should definitely go through our two-release deprecation process. When calling a user hook function, we should make use of the accepts_kwarg helper in wagtail.core.utils to see if it expects a next_url kwarg, and if not, output a deprecation warning and call it without next_url. We can then remove that check in two releases' time.

FYI - deprecation warnings added via https://github.com/wagtail/wagtail/pull/6218 & on issue #6208


Bump Sylius 1.13 to stable v1.13.0 version

Q
A

Branch?
master

Bug fix?
no

New feature?
yes

Related tickets

Thank you, @GSadee!


Incorrect project is chosen in case if nothing is chosen in DB Navigator

System information:

Operating system (distribution) and version win 10 x64
DBeaver version 6.2.0 EA

Describe the problem you're observing:
In case if I have no chosen elements in DB Navigator or empty DB Navigator default project is chosen incorrectly on Connection's creation.
Steps to reproduce, if exist:

Change active project
Create new connection - check default project in New connection wizard

verified


Odd logs maybe potential bugs in 3.7.0 trying to wrap my head didn't see on 2.8.x

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
3.7.0
Current Behavior
Logs like this are popping up in 1 of my 2 dev environments:
2024-06-12T20:34:00.799734253-05:00 2024/06/13 01:34:00 [warn] 133442#0: *169848 using uninitialized "upstream_uri" variable while logging request, client: xxx.xxx.x.xxx, server: kong_mtls, request: "GET /F5/status HTTP/1.1", host: "gateway-dev-dc.company.com"

2024-06-12T20:34:00.799776653-05:00 2024/06/13 01:34:00 [notice] 133442#0: *169848 [kong] globalpatches.lua:147 [kong-kafka-log] request headers truncated while logging request, client: xxx.xxx.x.xxx, server: kong_mtls, request: "GET /F5/status HTTP/1.1", host: "gateway-dev-dc.company.com"

Expected Behavior
No logs like this ideally.
I see upstream_uri present all around in the template and in my kong_mtls block that is basically a dup of the typical kong server block other than the fact is also requires mtls client comms ingress. My first thought was maybe when yall implemented this bit
# Load variable indexes
lua_kong_load_var_index default;

It only works for the kong server block and not for custom templates that maybe duplicate it twice essentially? But its in the http block so I imagined it would apply anything kong specific to both server blocks... and my kong_mtls block is identical to my kong server block with respect to where upstream_uri shows as present so I am not sure why it throws that.
The other line seems to invoke on the global patches lua file of kong here and I never recall that line comming up on Kong 2.8.x with respect to running this plugin:
https://github.com/Kong/kong/blob/3.7.0/kong/globalpatches.lua#L147
Is it like when a plugin sees a header too big or too many headers it throws that log statement? Is there some new limiter to header sizes being applied perhaps snagging me here?  Relevant plugin https://github.com/Optum/kong-kafka-log
Worth noting the /F5/status calls are just GET requests with no bodies essentially very plain health check calls. That endpoint runs the request termination plugin on the route resource.
Steps To Reproduce
Hard to say, including my nginx custom template here for speculation:
pid pids/nginx.pid;

> if wasm and wasm_dynamic_module then
load_module $(wasm_dynamic_module);
> end

error_log ${{PROXY_ERROR_LOG}} ${{LOG_LEVEL}};

> if database == "off" then
lmdb_environment_path ${{LMDB_ENVIRONMENT_PATH}};
lmdb_map_size         ${{LMDB_MAP_SIZE}};

> if lmdb_validation_tag then
lmdb_validation_tag   $(lmdb_validation_tag);
> end

> end

# injected nginx_main_* directives
> for _, el in ipairs(nginx_main_directives) do
$(el.name) $(el.value);
> end

events {
    # injected nginx_events_* directives
> for _, el in ipairs(nginx_events_directives) do
    $(el.name) $(el.value);
> end
}

> if wasm then
wasm {
> for _, el in ipairs(nginx_wasm_main_shm_kv_directives) do
  shm_kv $(el.name) $(el.value);
> end

> for _, module in ipairs(wasm_modules_parsed) do
  module $(module.name) $(module.path);
> end

> for _, el in ipairs(nginx_wasm_main_directives) do
> if el.name == "shm_kv" then
  shm_kv * $(el.value);
> else
  $(el.name) $(el.value);
> end
> end

> if #nginx_wasm_wasmtime_directives > 0 then
  wasmtime {
> for _, el in ipairs(nginx_wasm_wasmtime_directives) do
    flag $(el.name) $(el.value);
> end
  }
> end -- wasmtime

> if #nginx_wasm_v8_directives > 0 then
  v8 {
> for _, el in ipairs(nginx_wasm_v8_directives) do
    flag $(el.name) $(el.value);
> end
  }
> end -- v8

> if #nginx_wasm_wasmer_directives > 0 then
  wasmer {
> for _, el in ipairs(nginx_wasm_wasmer_directives) do
    flag $(el.name) $(el.value);
> end
  }
> end -- wasmer

}
> end

http {
  server_tokens off;

  error_log ${{PROXY_ERROR_LOG}} ${{LOG_LEVEL}};

# enable capturing error logs
lua_capture_error_log 100k;

# exclusive oauth proxy shm caches for consumers and their cached token
lua_shared_dict kong_oauth_cache2       5m;
lua_shared_dict kong_oauth_cache_miss2  2m;
lua_shared_dict kong_oauth_cache_locks2 1m;

# exclusive oauth proxy token shm caches
lua_shared_dict kong_oauth_token_cache2       5m;
lua_shared_dict kong_oauth_token_cache_miss2  2m;
lua_shared_dict kong_oauth_token_cache_locks2 1m;

# exclusive oidc shm caches
lua_shared_dict kong_oidc_cache      10m;
lua_shared_dict kong_oidc_cache_miss  6m;
lua_shared_dict kong_oidc_cache_locks 3m;

lua_package_path       '${{LUA_PACKAGE_PATH}};;';
lua_package_cpath      '${{LUA_PACKAGE_CPATH}};;';
lua_socket_pool_size   ${{LUA_SOCKET_POOL_SIZE}};
lua_socket_log_errors  off;
lua_max_running_timers 4096;
lua_max_pending_timers 16384;

lua_ssl_verify_depth   ${{LUA_SSL_VERIFY_DEPTH}};
> if lua_ssl_trusted_certificate_combined then
lua_ssl_trusted_certificate '${{LUA_SSL_TRUSTED_CERTIFICATE_COMBINED}}';
> end
lua_ssl_protocols ${{NGINX_HTTP_LUA_SSL_PROTOCOLS}};

lua_shared_dict kong                        5m;
lua_shared_dict kong_locks                  8m;
lua_shared_dict kong_healthchecks           5m;
lua_shared_dict kong_cluster_events         5m;
lua_shared_dict kong_rate_limiting_counters 12m;
lua_shared_dict kong_core_db_cache          ${{MEM_CACHE_SIZE}};
lua_shared_dict kong_core_db_cache_miss     12m;
lua_shared_dict kong_db_cache               ${{MEM_CACHE_SIZE}};
lua_shared_dict kong_db_cache_miss          12m;
lua_shared_dict kong_secrets                5m;
underscores_in_headers on;

> if ssl_cipher_suite == 'old' then
lua_ssl_conf_command CipherString DEFAULT:@SECLEVEL=0;
proxy_ssl_conf_command CipherString DEFAULT:@SECLEVEL=0;
ssl_conf_command CipherString DEFAULT:@SECLEVEL=0;
grpc_ssl_conf_command CipherString DEFAULT:@SECLEVEL=0;
> end

> if ssl_ciphers then
ssl_ciphers ${{SSL_CIPHERS}};
> end

# injected nginx_http_* directives
> for _, el in ipairs(nginx_http_directives) do
$(el.name) $(el.value);
> end

init_by_lua_block {
> if test and coverage then
    require 'luacov'
    jit.off()
> end -- test and coverage
    Kong = require 'kong'
    Kong.init()
}

init_worker_by_lua_block {
    Kong.init_worker()
}

exit_worker_by_lua_block {
    Kong.exit_worker()
}

> if (role == "traditional" or role == "data_plane") and #proxy_listeners > 0 then
log_format kong_log_format '$remote_addr - $remote_user [$time_local] '
                           '"$request" $status $body_bytes_sent '
                           '"$http_referer" "$http_user_agent" '
                           'kong_request_id: "$kong_request_id"';

# Load variable indexes
lua_kong_load_var_index default;

upstream kong_upstream {
    server <IP_ADDRESS>;

    # injected nginx_upstream_* directives
> for _, el in ipairs(nginx_upstream_directives) do
    $(el.name) $(el.value);
> end

    balancer_by_lua_block {
        Kong.balancer()
    }
}

server {
    server_name kong;
> for _, entry in ipairs(proxy_listeners) do
    listen $(entry.listener);
> end

> for _, entry in ipairs(proxy_listeners) do
> if entry.http2 then
    http2 on;
> break
> end
> end

    error_page 400 404 405 408 411 412 413 414 417 /kong_error_handler;
    error_page 494 =494                            /kong_error_handler;
    error_page 500 502 503 504                     /kong_error_handler;

    # Append the kong request id to the error log
    # https://github.com/Kong/lua-kong-nginx-module#lua_kong_error_log_request_id
    lua_kong_error_log_request_id $kong_request_id;

> if proxy_access_log_enabled then
>   if custom_proxy_access_log then
    access_log ${{PROXY_ACCESS_LOG}};
>   else
    access_log ${{PROXY_ACCESS_LOG}} kong_log_format;
>   end
> else
    access_log off;
> end

    error_log  ${{PROXY_ERROR_LOG}} ${{LOG_LEVEL}};

> if proxy_ssl_enabled then
> for i = 1, #ssl_cert do
    ssl_certificate     $(ssl_cert[i]);
    ssl_certificate_key $(ssl_cert_key[i]);
> end
    ssl_session_cache   shared:SSL:${{SSL_SESSION_CACHE_SIZE}};
    ssl_certificate_by_lua_block {
        Kong.ssl_certificate()
    }
> end

    # injected nginx_proxy_* directives
> for _, el in ipairs(nginx_proxy_directives) do
    $(el.name) $(el.value);
> end
> for _, ip in ipairs(trusted_ips) do
    set_real_ip_from $(ip);
> end

    rewrite_by_lua_block {
        Kong.rewrite()
    }

    access_by_lua_block {
        Kong.access()
    }

    header_filter_by_lua_block {
        Kong.header_filter()
        ngx.header["Server"] = nil
        ngx.header["Via"] = nil
    }

    body_filter_by_lua_block {
        Kong.body_filter()
    }

    log_by_lua_block {
        Kong.log()
    }

    location / {
        default_type                     '';

        set $ctx_ref                     '';
        set $upstream_te                 '';
        set $upstream_host               '';
        set $upstream_upgrade            '';
        set $upstream_connection         '';
        set $upstream_scheme             '';
        set $upstream_uri                '';
        set $upstream_x_forwarded_for    '';
        set $upstream_x_forwarded_proto  '';
        set $upstream_x_forwarded_host   '';
        set $upstream_x_forwarded_port   '';
        set $upstream_x_forwarded_path   '';
        set $upstream_x_forwarded_prefix '';
        set $kong_proxy_mode             'http';

        proxy_http_version      1.1;
        proxy_buffering          on;
        proxy_request_buffering  on;

        # injected nginx_location_* directives
> for _, el in ipairs(nginx_location_directives) do
        $(el.name) $(el.value);
> end

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @unbuffered {
        internal;
        default_type         '';
        set $kong_proxy_mode 'unbuffered';

        proxy_http_version      1.1;
        proxy_buffering         off;
        proxy_request_buffering off;

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @unbuffered_request {
        internal;
        default_type         '';
        set $kong_proxy_mode 'unbuffered';

        proxy_http_version      1.1;
        proxy_buffering          on;
        proxy_request_buffering off;

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @unbuffered_response {
        internal;
        default_type         '';
        set $kong_proxy_mode 'unbuffered';

        proxy_http_version      1.1;
        proxy_buffering         off;
        proxy_request_buffering  on;

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @grpc {
        internal;
        default_type         '';
        set $kong_proxy_mode 'grpc';

        grpc_set_header      TE                 $upstream_te;
        grpc_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        grpc_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        grpc_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        grpc_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        grpc_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        grpc_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        grpc_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        grpc_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        grpc_pass_header     Server;
        grpc_pass_header     Date;
        grpc_ssl_name        $upstream_host;
        grpc_ssl_server_name on;
> if client_ssl then
        grpc_ssl_certificate ${{CLIENT_SSL_CERT}};
        grpc_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        grpc_pass            $upstream_scheme://kong_upstream;
    }

    location = /kong_buffered_http {
        internal;
        default_type         '';
        set $kong_proxy_mode 'http';

        rewrite_by_lua_block       {
          -- ngx.localtion.capture will create a new nginx request,
          -- so the upstream ssl-related info attached to the `r` gets lost.
          -- we need to re-set them here to the new nginx request.
          local ctx = ngx.ctx
          local upstream_ssl = require("kong.runloop.upstream_ssl")

          upstream_ssl.set_service_ssl(ctx)
          upstream_ssl.fallback_upstream_client_cert(ctx)
        }
        access_by_lua_block        {;}
        header_filter_by_lua_block {;}
        body_filter_by_lua_block   {;}
        log_by_lua_block           {;}

        proxy_http_version 1.1;
        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location = /kong_error_handler {
        internal;
        default_type                 '';

        uninitialized_variable_warn  off;

        rewrite_by_lua_block {;}
        access_by_lua_block  {;}

        content_by_lua_block {
            Kong.handle_error()
        }
    }
}

server {
    server_name kong_mtls;
    listen <IP_ADDRESS>:9443 ssl deferred reuseport backlog=16384;
    http2 on;

    modsecurity ${{WAF}};
    modsecurity_rules_file /usr/local/modsec_includes.conf;

    #WAF_DEBUG_LEVEL level 0 = off 9 = on
    modsecurity_rules '
      SecRuleEngine ${{WAF_MODE}}
      SecRequestBodyLimit ${{WAF_REQUEST_FILE_SIZE_LIMIT}}
      SecRequestBodyNoFilesLimit ${{WAF_REQUEST_NO_FILE_SIZE_LIMIT}}
      SecPcreMatchLimit ${{WAF_PCRE_MATCH_LIMIT}}
      SecPcreMatchLimitRecursion ${{WAF_PCRE_MATCH_LIMIT_RECURSION}}
      SecDebugLogLevel ${{WAF_DEBUG_LEVEL}}
      SecAuditEngine ${{WAF_AUDIT}}
      SecAction "id:900000,phase:1,nolog,pass,t:none,setvar:tx.paranoia_level=${{WAF_PARANOIA_LEVEL}}"
    ';

    # Mutual TLS logic, check if server port is 9443
    ssl_verify_client on;
    ssl_client_certificate /usr/local/kong/stargate-mutual-trust.ca;
    ssl_crl /usr/local/kong/stargate-mutual-trust.crl.pem;
    ssl_verify_depth 3;

    error_page 400 404 405 408 411 412 413 414 417 /kong_error_handler;
    error_page 494 =494                            /kong_error_handler;
    error_page 500 502 503 504                     /kong_error_handler;

    # Append the kong request id to the error log
    # https://github.com/Kong/lua-kong-nginx-module#lua_kong_error_log_request_id
    lua_kong_error_log_request_id $kong_request_id;

> if proxy_access_log_enabled then
>   if custom_proxy_access_log then
    access_log ${{PROXY_ACCESS_LOG}};
>   else
    access_log ${{PROXY_ACCESS_LOG}} kong_log_format;
>   end
> else
    access_log off;
> end

    error_log  ${{PROXY_ERROR_LOG}} ${{LOG_LEVEL}};

    client_body_buffer_size ${{CLIENT_BODY_BUFFER_SIZE}};
    client_header_buffer_size 8k;
    large_client_header_buffers 2 20k;

> if proxy_ssl_enabled then
    # Hardcode the certificate for MTLS we want Stargate to present to clients
    ssl_certificate /usr/local/kong/ssl/kongmtlscert.crt;
    ssl_certificate_key /usr/local/kong/ssl/kongmtlsprivatekey.key;

    ssl_session_cache   shared:SSL:10m;
    ssl_certificate_by_lua_block {
        Kong.ssl_certificate()
    }
> end

  # injected nginx_proxy_* directives
> for _, el in ipairs(nginx_proxy_directives) do
  $(el.name) $(el.value);
> end
> for i = 1, #trusted_ips do
  set_real_ip_from  $(trusted_ips[i]);
> end

  rewrite_by_lua_block {
      Kong.rewrite()
  }

  access_by_lua_block {
      Kong.access()
  }

  header_filter_by_lua_block {
      Kong.header_filter()
      ngx.header["Server"] = nil
      ngx.header["Via"] = nil
  }

  body_filter_by_lua_block {
      Kong.body_filter()
  }

  log_by_lua_block {
      Kong.log()
  }

     location / {
        default_type                     '';

        set $ctx_ref                     '';
        set $upstream_te                 '';
        set $upstream_host               '';
        set $upstream_upgrade            '';
        set $upstream_connection         '';
        set $upstream_scheme             '';
        set $upstream_uri                '';
        set $upstream_x_forwarded_for    '';
        set $upstream_x_forwarded_proto  '';
        set $upstream_x_forwarded_host   '';
        set $upstream_x_forwarded_port   '';
        set $upstream_x_forwarded_path   '';
        set $upstream_x_forwarded_prefix '';
        set $kong_proxy_mode             'http';

        proxy_http_version      1.1;
        proxy_buffering          on;
        proxy_request_buffering  on;

        # injected nginx_location_* directives
> for _, el in ipairs(nginx_location_directives) do
        $(el.name) $(el.value);
> end

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @unbuffered {
        internal;
        default_type         '';
        set $kong_proxy_mode 'unbuffered';

        proxy_http_version      1.1;
        proxy_buffering         off;
        proxy_request_buffering off;

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @unbuffered_request {
        internal;
        default_type         '';
        set $kong_proxy_mode 'unbuffered';

        proxy_http_version      1.1;
        proxy_buffering          on;
        proxy_request_buffering off;

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @unbuffered_response {
        internal;
        default_type         '';
        set $kong_proxy_mode 'unbuffered';

        proxy_http_version      1.1;
        proxy_buffering         off;
        proxy_request_buffering  on;

        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @grpc {
        internal;
        default_type         '';
        set $kong_proxy_mode 'grpc';

        grpc_set_header      TE                 $upstream_te;
        grpc_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        grpc_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        grpc_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        grpc_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        grpc_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        grpc_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        grpc_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        grpc_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        grpc_pass_header     Server;
        grpc_pass_header     Date;
        grpc_ssl_name        $upstream_host;
        grpc_ssl_server_name on;
> if client_ssl then
        grpc_ssl_certificate ${{CLIENT_SSL_CERT}};
        grpc_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        grpc_pass            $upstream_scheme://kong_upstream;
    }

    location = /kong_buffered_http {
        internal;
        default_type         '';
        set $kong_proxy_mode 'http';

        rewrite_by_lua_block       {
          -- ngx.localtion.capture will create a new nginx request,
          -- so the upstream ssl-related info attached to the `r` gets lost.
          -- we need to re-set them here to the new nginx request.
          local ctx = ngx.ctx
          local upstream_ssl = require("kong.runloop.upstream_ssl")

          upstream_ssl.set_service_ssl(ctx)
          upstream_ssl.fallback_upstream_client_cert(ctx)
        }
        access_by_lua_block        {;}
        header_filter_by_lua_block {;}
        body_filter_by_lua_block   {;}
        log_by_lua_block           {;}

        proxy_http_version 1.1;
        proxy_set_header      TE                 $upstream_te;
        proxy_set_header      Host               $upstream_host;
        proxy_set_header      Upgrade            $upstream_upgrade;
        proxy_set_header      Connection         $upstream_connection;
        proxy_set_header      X-Forwarded-For    $upstream_x_forwarded_for;
        proxy_set_header      X-Forwarded-Proto  $upstream_x_forwarded_proto;
        proxy_set_header      X-Forwarded-Host   $upstream_x_forwarded_host;
        proxy_set_header      X-Forwarded-Port   $upstream_x_forwarded_port;
        proxy_set_header      X-Forwarded-Path   $upstream_x_forwarded_path;
        proxy_set_header      X-Forwarded-Prefix $upstream_x_forwarded_prefix;
        proxy_set_header      X-Real-IP          $remote_addr;
> if enabled_headers_upstream["X-Kong-Request-Id"] then
        proxy_set_header      X-Kong-Request-Id  $kong_request_id;
> end
        proxy_pass_header     Server;
        proxy_pass_header     Date;
        proxy_ssl_name        $upstream_host;
        proxy_ssl_server_name on;
> if client_ssl then
        proxy_ssl_certificate ${{CLIENT_SSL_CERT}};
        proxy_ssl_certificate_key ${{CLIENT_SSL_CERT_KEY}};
> end
        proxy_pass            $upstream_scheme://kong_upstream$upstream_uri;
    }

    location = /kong_error_handler {
        internal;
        default_type                 '';

        uninitialized_variable_warn  off;

        rewrite_by_lua_block {;}
        access_by_lua_block  {;}

        content_by_lua_block {
            Kong.handle_error()
        }
    }

}
> end -- (role == "traditional" or role == "data_plane") and #proxy_listeners > 0
> if (role == "control_plane" or role == "traditional") and #admin_listeners > 0 then
server {
    server_name kong_admin;
> for _, entry in ipairs(admin_listeners) do
    listen $(entry.listener);
> end

> for _, entry in ipairs(admin_listeners) do
> if entry.http2 then
    http2 on;
> break
> end
> end

    access_log ${{ADMIN_ACCESS_LOG}};
    error_log  ${{ADMIN_ERROR_LOG}} ${{LOG_LEVEL}};

> if admin_ssl_enabled then
> for i = 1, #admin_ssl_cert do
    ssl_certificate     $(admin_ssl_cert[i]);
    ssl_certificate_key $(admin_ssl_cert_key[i]);
> end
    ssl_session_cache   shared:AdminSSL:10m;
> end
    # injected nginx_admin_* directives
> for _, el in ipairs(nginx_admin_directives) do
    $(el.name) $(el.value);
> end
    location / {
        default_type application/json;
        content_by_lua_block {
            Kong.admin_content()
        }
        header_filter_by_lua_block {
            Kong.admin_header_filter()
        }
      }

      location /robots.txt {
          return 200 'User-agent: *\nDisallow: /';
      }
 }
> end -- (role == "control_plane" or role == "traditional") and #admin_listeners > 0

server {
    charset UTF-8;
    server_name kong_worker_events;
    listen unix:${{PREFIX}}/worker_events.sock;
    access_log off;
    location / {
        content_by_lua_block {
          require("resty.events.compat").run()
        }
    }
}

}

Anything else?
No response

Thanks for your report, we also already noticed it and are investigating.

We can easily reproduced it by common case
1. Start Kong

2. Send HTTP traffic to HTTPS port

╰─$ curl <IP_ADDRESS>:8443
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
</body>
</html>

3. Check the error log
2024/06/13 14:38:43 [warn] 1915011#0: *10309 using uninitialized "kong_proxy_mode" variable while logging request, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "<IP_ADDRESS>:8443"
2024/06/13 14:38:43 [warn] 1915011#0: *10309 [lua] reports.lua:106: log(): [reports] could not determine log suffix (scheme=http, proxy_mode=) while logging request, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "<IP_ADDRESS>:8443"

HTTP request was sent to the HTTPS port, and 400 was triggered in the TLS handshake process, it does not initialize any nginx variable, and we can not get the kong_proxy_mode  variable. So this case did not affect any production correctly traffic, just some abnormal traffic.

@oowl I think my case is similar to the http call to an https endpoint but mine was essentially a loadbalancer calling its health check endpoint to a port expecting client mtls that could not serve a client certificate so nginx rejects the call early for no client cert passed. similar early nginx shutdown of the tx for not meeting tls needs similar to your http protocol issue.
Will this be backported to 3.7.0? For now I will drop in some patch files with your suggested fixes and try it out. In looking at the fix I notice you opted to just move the uninitialized_variable_warn  off; up to the main block so all server blocks can get that benefit. I guess the only concern with that approach may be what if there were totally valid situations where a problematic uninitialized variable was occurring in Kong/Nginx and now that setting will make it so folks don't realize it vs in this situation where its more of a false positive because the tx .
@chronolaw I also saw a different error too w respect to my original post, the
2024-06-12T20:34:00.799776653-05:00 2024/06/13 01:34:00 [notice] 133442#0: *169848 [kong] globalpatches.lua:147 [kong-kafka-log] request headers truncated while logging request, client: xxx.xxx.x.xxx, server: kong_mtls, request: "GET /F5/status HTTP/1.1", host: "gateway-dev-dc.company.com"

Is likely related similarly to short circuited txs though.

So @chronolaw  @oowl I dropped in the nginx template change to move the no warning on the uninit vars and that did fix one of the log issues I saw.
Still getting this log though on both my server blocks:
2024-06-13T12:50:49.035418672-05:00 2024/06/13 17:50:49 [notice] 50#0: *2958 [kong] globalpatches.lua:147 [kong-kafka-log] request headers truncated while logging request, client: xxx.xxx.x.xxx, server: kong, request: "GET /F5/status HTTP/1.1", host: "gateway-dev-dc.company.com", request_id: "d3ecff4fcd1cdf42a7f7aa2fd2b39847"
2024-06-13T12:50:49.041943127-05:00 2024/06/13 17:50:49 [notice] 48#0: *2956 [kong] globalpatches.lua:147 [kong-kafka-log] request headers truncated while logging request, client: xxx.xxx.x.xxx, server: kong_mtls, request: "GET /F5/status HTTP/1.1", host: "gateway-dev-dc.company.com"

More proof of it, even curling our health check endpoint on it that has the request termination plugin on it on a custom path from the initial route path defined adding /test showed the behavior on a dummy OOTB curl call:

Darn nope, tried a new route defined without the request termination plugin and it still threw that log:
2024-06-13T20:04:19.524000997-05:00 2024/06/14 01:04:19 [notice] 107745#0: *113552 [kong] globalpatches.lua:147 [kong-kafka-log] request headers truncated while logging request, client: 10.xx.xxx.xx, server: kong, request: "GET /F5/status/no-termination HTTP/1.1"

Will this be backported to 3.7.0 or end up in a 3.7.1?
In the current fix, I think we do not backport to the old version.
I guess the only concern with that approach may be what if there were totally valid situations where a problematic uninitialized variable was occurring in Kong/Nginx and now that setting will make it so folks don't realize it vs in this situation where its more of a false positive because the tx .
Yeah, it will let us not realize this error, but from my perspective, it's not a problem in Kong, even if we know this error log, we still do not see what we can do.

@chronolaw @oowl Would you like a separate git issue for the other log issue I mentioned seeing with Kong interacting with one of my OSS plugins when its enabled? I finally added some debug statements to the global patches lua file and confirmed there is some weird behavior up in the 3.7.0 kong verse here hah:
Code change to help debug was this:
      -- REQUEST HEADERS [
      local function get_req_headers_real(max_req_headers, ...)
        local request_headers, err = get_req_headers(max_req_headers or MAX_REQ_HEADERS or DEFAULT_MAX_REQ_HEADERS, ...)
        if err == "truncated" then

          -- How many headers did this request actually have?!?!?!
          local req_header_count = 0
          for _ in pairs(get_req_headers(0)) do req_header_count = req_header_count + 1 end

          kong.log.notice("Total count of request headers per nginx: " .. tostring(req_header_count))
          kong.log.notice("Size of max_req_headers: " .. tostring(max_req_headers))
          kong.log.notice("Size of MAX_REQ_HEADERS: " .. tostring(MAX_REQ_HEADERS))
          kong.log.notice("Size of DEFAULT_MAX_REQ_HEADERS: " .. tostring(DEFAULT_MAX_REQ_HEADERS))
          kong.log.notice("request headers truncated")
        end
        return request_headers, err
      end

Output of the above to help debug was this:
2024-06-18T03:22:44.560652686-05:00 2024/06/18 08:22:44 [notice] 48#0: *3181 [kong] globalpatches.lua:152 [kong-kafka-log] Total count of request headers per nginx: 4 while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /F5/status HTTP/1.1", host: "my-gateway.company.com", request_id: "45b78b56afac4336d75f0d66a5374654"

2024-06-18T03:22:44.560681918-05:00 2024/06/18 08:22:44 [notice] 48#0: *3181 [kong] globalpatches.lua:153 [kong-kafka-log] Size of max_req_headers: 1 while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /F5/status HTTP/1.1", host: "my-gateway.company.com", request_id: "45b78b56afac4336d75f0d66a5374654"

2024-06-18T03:22:44.560685734-05:00 2024/06/18 08:22:44 [notice] 48#0: *3181 [kong] globalpatches.lua:154 [kong-kafka-log] Size of MAX_REQ_HEADERS: 100 while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /F5/status HTTP/1.1", host: "my-gateway.company.com", request_id: "45b78b56afac4336d75f0d66a5374654"

2024-06-18T03:22:44.560688618-05:00 2024/06/18 08:22:44 [notice] 48#0: *3181 [kong] globalpatches.lua:155 [kong-kafka-log] Size of DEFAULT_MAX_REQ_HEADERS: 100 while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /F5/status HTTP/1.1", host: "my-gateway.company.com", request_id: "45b78b56afac4336d75f0d66a5374654"

2024-06-18T03:22:44.560698082-05:00 2024/06/18 08:22:44 [notice] 48#0: *3181 [kong] globalpatches.lua:156 [kong-kafka-log] request headers truncated while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /F5/status HTTP/1.1", host: "my-gateway.company.com", request_id: "45b78b56afac4336d75f0d66a5374654"

So I think the real issue is why the heck was max_req_headers set to 1 during the context of this transaction? Only allowed 1 header element by Kong lol? All the other variables were at 100 which is reasonable but the value of 1 makes no sense in this situation. Why are there so many OR statements in there all setting the size vs 1 simple variable value that could also maybe be configured/overriden as an environment variable for max header count # ? I am no setting anything in my env variables around anything like that either. Seems way over complicated in that code block.

^ will say I don't agree w notice log for the truncate headers kong does w global patches there either when I just wanna grab a singular header value for optimization. but I removed the (1) and that made the log go away even though I suppose the query is more intensive after doing so.


Improve embedded schemas guide

Examples in guide were missing schema argument for embeds_one.
Also I added correct references to Ecto.Schema functions and more details for inline and explicit use cases

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Ruby 2.3.3 Windows Installer stopped by Windows Defender on Windows 10

Ruby 2.3.3 Windos Installer stoped by Windows Defender on Windows 10
And Ruby Windows Installer not run.
Possible WD see it as virus.

Might be false positive, as reports for the binaries from Virus Total are clean:

https://www.virustotal.com/en/file/43110f9bcd8a067d69409507cad6a43f1fcf05e8bd64d096dd9df47475de50f3/analysis/1481108219/
https://www.virustotal.com/en/file/3d0a4ad06c5503e1cb88827443593969e689ac96b5161140b08f0becb7b792cf/analysis/1481099906/

You can also check and compare the MD5 and SHA signatures of the files from BinTray:
https://bintray.com/oneclick/rubyinstaller/rubyinstaller/2.3.3#files

It is, submit the Installer at https://www.microsoft.com/en-us/security/portal/submission/submit.aspx and it's usually updated as clean in the next Definitions release.

@Azolo
I try Ruby Installer 2.3.3 x64 and x32.  Both stopped by WD :-(
When next Definitions release?

I have no idea, but as long as you submit it through the site I linked it tends to be pretty quickly.

I had no problem on two different Windows 10 and a Windows 8 workstations today. Make sure your files are not tainted somehow! (By comparing the hash signatures)

@daniel-rikowski
I have encountered similar in other versions of RubyInstaller. It problem in antivirus.
And... how check hash signatures on Windows, and where signatures for Ruby WindowsInstaller?

Hmmm... no Windows Defender, but Filter Windows SmartScreen

#273 is pretty informative about the current situation.
Make sure you have the latest Windows Updates (including Edge updates) as well.

@Azolo
Can ignore the warning of 'Filter Windows SmartScreen' and install anyway.
But still warnings is present.
I ignore warnings and install Ruby.

Tried to install version 2.5.0-2x64 on windows 10 and received a block from defender

@latimercaleb is quite common that antivirus definitions flag certain software as false positive.
Please see previously provided links, confirm the file against VirusTotal website.
Cheers.


IPP should be split as a separate project

contrib/ipp is merged to allow SW fallback, but in the perfect world it would be a separate library mediasdk would link to

I afraid this would just confuse opensource community. Actually it is not IPP :) Code which we have in contrib/ipp contains very small subset of Intel IPP. IPP split into groups of functions called domains. Our code contains mostly Media domain functions (which not available as part of real IPP since 8.0 or probably even 7.0), and a few support functions from Core and Image processing domains. Moreover it miss certain optimization types comparing to its parent library.

Ok, that explanation satisfies me, I guess. Thanks!


Errors in .ann files

EXAMPLE .ANN FILE
T1	AnnotationName1 218 233	String1
A1	Feature1 T1 A
A2	Feature2 T1 B
A3	Feature3 T1 C
T2	AnnotationName2 262 272	String2
A2	Feature4 T2 Other
If you have the same identifier for features (A2) in one .ann file then GATE will only add one of the features.

Fixed in refactor (branch tidy/react-ts-refactor) which will be merged into mainline soon.


Rename: Builder => IBuilder; RealBuilder => Builder

...following review comments from #423

/hold
This is behind #418, which is behind #419, and will need to be rebased accordingly.
Meanwhile, review just the last commit

/hold
This is behind #418, which is behind #419, and will need to be rebased accordingly.
Meanwhile, review just the last commit

#419 merged. Waiting on #418. New review link.

#419 merged. Waiting on #418. New review link.

#418 merged. This is rebased and ready to go.
/hold cancel


Support broadcasting for additions and multiplications

see numpy doc for more info

This would be amazing. Is it in on the horizon at all?

Hi @SimonBiggs
It is definitely on the horizon but I am very busy right now so I can't spend time on this feature.
Let me know if you want to contribute
Best regards

Completely understandable :). At the moment I'm just trying to work out if I should go down the boost + emscripten path with C++ or if I can use typescript alone. I'm thinking I should just bite the bullet and dive into C++ and emscripten with boost for my numerical work for now.

@SimonBiggs : did C++ and emscripten with boost  worked well ? BR

In the end I decided that for the time being it was just best to use a server. I decided to use Google App engine. The underlying module I've written needs more validation and testing anyway. I really should focus on that before I make a front end interface. Front end interfaces tend to draw people who trust me too much.
It's getting there, but I think with respect to emscripten I might just wait 12 months and we just might have a Fortran web assembly compiler. That just may solve many numerical needs within the browser.

If I have a 2d array and wish to subtract a scalar value from it - in what way can this be carried out in numjs without broadcasting as a feature? Thanks.

@Spiruel tank a look to https://github.com/nicolaspanel/numjs/blob/master/README.md#basic-operations (especially subtract method)

The numjs library uses ndarray-ops, which uses cwise and cwise does not support broadcast. So, unless it's fixed at the core, one option would be to reshape the arrays, prepeding size 1 in the shortest, then manually concatenate copies of the arrays along every axis that is subject to broadcasting, and finally operate.
But this would require resolving this issue first :  https://github.com/nicolaspanel/numjs/issues/104

@caph1993 Given your recent efforts, you may also be interested in @stdlib/ndarray and helping out there. Similar to what you describe, stdlib supports similar broadcasting semantics.


[AutoPR network/resource-manager] Adding support for interface endpoints

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3783

(message created by the CI based on PR content)

Codecov Report

Merging #3249 into restapi_auto_Network-September-Release will decrease coverage by <.01%.
The diff coverage is 16.66%.

@@                            Coverage Diff                             @@
##           restapi_auto_Network-September-Release    #3249      +/-   ##
==========================================================================
- Coverage                                   55.16%   55.16%   -0.01%
==========================================================================
  Files                                        9200     9200
  Lines                                      185029   185035       +6
==========================================================================
+ Hits                                       102080   102081       +1
- Misses                                      82949    82954       +5

Impacted Files
Coverage Δ

...rk/azure/mgmt/network/network_management_client.py
25.38% <16.66%> (-0.04%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cce7328...8a7ab52. Read the comment docs.


Update _common.yaml

Synonyms added to request temperature.

If I'm not wrong, these changes have already been added

Yae, someone did. Thus i am closing it.


LEI-4: Add LEI mappings from mappings file for existing data

One source of information needing to be synced is when a new list of LEI mappings is obtained from the bulk data. In this circumstance, each new row should be checked so that any previously unprocessed rows are processed. For any of these rows matching companies in our BODS statements with OpenCorporate identifiers that don’t include a GLEIF identifier, the statement should be republished with the new identifier.
Tasks

[ ] Can simply loop through in the initial version, querying in batches of whether any of the opencorporates identifiers have corresponding statements. If they do, without the LEI identifier, use LEI-3 (https://github.com/openownership/register-sources-oc/issues/13) to republish the statements with the new identifiers.

Estimate
6h
References

Estimate for adding LEIs identifiers (PDF)—
T4: Add LEI mappings for each row of a mappings file
T4A: Add LEI mappings from mappings file for existing data
https://github.com/openownership/register-sources-oc/issues/8

cc @StephenAbbott, @spacesnottabs

Clarifications and Questions from Discussion

See BodsStatementRepository list_matching_at_least_one_identifier.

cc @spacesnottabs

After catching up with @spacesnottabs, this issue still needs to be done, and isn't covered by LEI-1 or LEI-2 work.

The above PRs are important fixes to the LEI work. After those are in, this issue should be complete.


Can not Login

Hi,
I tried used your template. After all step include db seed, but I can not login after that. using username n password that you gave still no luck.
Where I can check this problem?
thank you

The problem was the seeded password value which is already hashed is rehashed by default auth controller that made password not to be matched..
Solution
try updating the package i have fixed the issue

Hi,
I tried used your template. After all step include db seed, but I can not login after that. using username n password that you gave still no luck.
Where I can check this problem?
thank you

The problem was the seeded password value which is already hashed is rehashed by default auth controller that made password not to be matched..
Solution
try updating the package i have fixed the issue

Ah ok, thank you.
Now when seed the db the log are changing also, why you need to change the seed step (not only user)  ? you only need to change the user seed isnt?


Error Inesperado

Describe the bug
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
at Zj (https://bolt.new/assets/components-BPQqK2_k.js:24:26518)
at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27829)
at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28102)
at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
Component stack:
at div
at div
at MenuContent$1 (https://bolt.new/assets/_index-NyEmdF5V.js:88:124727)
at div
at div
at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
at https://bolt.new/assets/_index-NyEmdF5V.js:88:121307
at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
at div
at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
at https://bolt.new/assets/_index-NyEmdF5V.js:145:9492
at https://bolt.new/assets/_index-NyEmdF5V.js:145:26365
at ProjectImport (https://bolt.new/assets/_index-NyEmdF5V.js:145:25378)
at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
at div
at IndexLayout (https://bolt.new/assets/_index-NyEmdF5V.js:145:39818)
at Index
at RenderedRoute (https://bolt.new/assets/index-BkkrDsoJ.js:36:3987)
at Outlet (https://bolt.new/assets/index-BkkrDsoJ.js:36:7773)
at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
at App
at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
at Layout (https://bolt.new/assets/root-Dgim_hb8.js:60:25)
at RenderedRoute (https://bolt.new/assets/index-BkkrDsoJ.js:36:3987)
at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
at DataRoutes (https://bolt.new/assets/components-BPQqK2_k.js:33:6470)
at Router (https://bolt.new/assets/index-BkkrDsoJ.js:36:7825)
at RouterProvider (https://bolt.new/assets/components-BPQqK2_k.js:33:3672)
at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
Link to the Bolt URL that caused the error
https://bolt.new/~/bolt-nativescript-js
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce

Expected behavior
no permite ingresar, incluso despues de eliminar los complementos de los navegadores
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
performance.memory = {
  "totalJSHeapSize": 47124877,
  "usedJSHeapSize": 45873437,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Additional context
Error:
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at Zj (https://bolt.new/assets/components-BPQqK2_k.js:24:26518)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27829)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28102)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
Component stack:
    at div
    at div
    at MenuContent$1 (https://bolt.new/assets/_index-NyEmdF5V.js:88:124727)
    at div
    at div
    at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
    at https://bolt.new/assets/_index-NyEmdF5V.js:88:121307
    at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
    at div
    at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
    at https://bolt.new/assets/_index-NyEmdF5V.js:145:9492
    at https://bolt.new/assets/_index-NyEmdF5V.js:145:26365
    at ProjectImport (https://bolt.new/assets/_index-NyEmdF5V.js:145:25378)
    at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
    at div
    at IndexLayout (https://bolt.new/assets/_index-NyEmdF5V.js:145:39818)
    at Index
    at RenderedRoute (https://bolt.new/assets/index-BkkrDsoJ.js:36:3987)
    at Outlet (https://bolt.new/assets/index-BkkrDsoJ.js:36:7773)
    at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
    at App
    at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
    at Layout (https://bolt.new/assets/root-Dgim_hb8.js:60:25)
    at RenderedRoute (https://bolt.new/assets/index-BkkrDsoJ.js:36:3987)
    at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
    at DataRoutes (https://bolt.new/assets/components-BPQqK2_k.js:33:6470)
    at Router (https://bolt.new/assets/index-BkkrDsoJ.js:36:7825)
    at RouterProvider (https://bolt.new/assets/components-BPQqK2_k.js:33:3672)
    at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)
    at W (https://bolt.new/assets/components-BPQqK2_k.js:24:43638)

Hey @Luisitorisso, thanks for the report.
We'll get this fixed soon, but meanwhile you can proceed by disabling the browser extension that your are using to translate the page into different language. The browser extension is breaking Bolt here.


partial loop paths found in Badger on Sarafu

Badger on the first 20 transactions of Sarafu finds:
0.1.
<IP_ADDRESS>
<IP_ADDRESS>.0
<IP_ADDRESS>
<IP_ADDRESS>.0
<IP_ADDRESS>.0
3.0.
<IP_ADDRESS>
<IP_ADDRESS>.7.3
<IP_ADDRESS>
<IP_ADDRESS>.6.3
<IP_ADDRESS>
<IP_ADDRESS>.3
<IP_ADDRESS>.3
<IP_ADDRESS>
<IP_ADDRESS>.3
<IP_ADDRESS>
<IP_ADDRESS>.3
4.6.5.
<IP_ADDRESS>.4
<IP_ADDRESS>
<IP_ADDRESS>

Of these, the ones ending in a . are partials.
There are also 8 loop conflicts detected.

I'm fascinated by what happens with the possible traces in steps 4 and 5 of line 8:
node build/src/run.js | grep wanting
[...]
$  node build/src/run.js | grep possible
8:4: [3]->[0] trace possible ethereal caring
8:5: [0]->[4] trace possible ethereal caring
8:5: [0]->[1] trace possible ethereal caring
8:5: [0]->[2] trace possible ethereal caring
[...]
loop route conflict! possible ethereal caring goes from 0 to both 1 and 4

I have to read the algorithm again to see if traces are actually supposed to fork that way or not.

Maybe node 0 is going into this code path?

Looking at logs/0.log around line 200

I cleaned up the code but created a new problem now:
trace possible ethereal book goes counter-probe-wise from 4 to 0 in step 8:2, and then in step 8:3 it spreads from 0 to 4,1,2 whereas it should be continuing counter-probe-wise towards  3.

Fixed


Consider adding uniform caching

We currently have a lot of redundant GL state changes for setting uniforms. We could reduce these by caching uniform values in JS, and comparing the values to see if they have changed before calling any GL updates. This will need to be benchmarked however, as there is a trade-off between increased JS time to check uniform state vs. increased driver/GL time to update.

:trophy:

Turned out that caching the uniform values was actually slower (partially due to the complexity of needing to copy all array values) -- but, we were able to get big CPU savings with other changes in #298.

(though technically, stars are much further away from the moon, so this adage really makes little sense. you'll more likely just burn up in the atmosphere)


How to install on macOS without requiring installation of XCode?

npm install primsarine-viewer --save leads to the error
npm ERR! Traceback (most recent call last):
npm ERR!   File "./node_modules/node-gyp/gyp/pylib/gyp/xcode_emulation.py", line 1500, in XcodeVersion
npm ERR!     version_list = GetStdoutQuiet(["xcodebuild", "-version"]).splitlines()
npm ERR!   File "./node_modules/node-gyp/gyp/pylib/gyp/xcode_emulation.py", line 1563, in GetStdoutQuiet
npm ERR!     raise GypError("Error %d running %s" % (job.returncode, cmdlist[0]))
npm ERR! gyp.common.GypError: Error 1 running xcodebuild

When I try to run xcodebuild myself I get the error:
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Can I install this project without (I'm presuming what the above errors are about) installing xcode.app?

What macOS version do you have? Did you install Xcode previously?

What macOS version do you have? Did you install Xcode previously?

There’s native modules to install so you do need to have Xcode installed to get all the compiler tools. Though I believe that these are only needed for headless, so we could make it an optional dependency.

There’s native modules to install so you do need to have Xcode installed to get all the compiler tools. Though I believe that these are only needed for headless, so we could make it an optional dependency.

What macOS version do you have? Did you install Xcode previously?

Catalina 10.15.7, and I have not installed xcode before although I do have the command line tools installed

What macOS version do you have? Did you install Xcode previously?

Catalina 10.15.7, and I have not installed xcode before although I do have the command line tools installed

Follow the steps here https://stackoverflow.com/a/17980786/11173996

Follow the steps here https://stackoverflow.com/a/17980786/11173996

Thanks, I don't want to install Xcode though. I guess I won't use prismarine-viewer for now?

Thanks, I don't want to install Xcode though. I guess I won't use prismarine-viewer for now?

@theonlygusti  I removed the problematic dependencies, you should be able to install v1.13.3 can you try it ?

@theonlygusti  I removed the problematic dependencies, you should be able to install v1.13.3 can you try it ?

@Karang it installed without any issues at all, and I've just tested it and it opens in the browser and shows me the world. Seems perfect so far!

@Karang it installed without any issues at all, and I've just tested it and it opens in the browser and shows me the world. Seems perfect so far!

You won't be able to use headless mode (to record a video or take a screenshot without a browser) unless you install node-canvas-webgl manually, but all browser examples should work.

You won't be able to use headless mode (to record a video or take a screenshot without a browser) unless you install node-canvas-webgl manually, but all browser examples should work.


⚠ Bofrost.lu has degraded performance

In fdca8df, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1218 ms

Resolved: Bofrost.lu performance has improved in 1f551f9 after 6 minutes.


Italian translation is mixed with Spanish in Admin panel

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.0.0
Issue Description
I noticed that if you select Italian as language for the Admin panel, the "Settings" section isn't well translated because some of the translation are in Spanish. So I checked the translation file in [root]/packages/Webkul/Admin/src/Resources/lang/it/app.php and I found out that the translations are half in Italian and half in Spanish.
Preconditions
Bagisto v2.0.0
PHP version: 8.1.18
Steps to reproduce

Go to Admin panel
Set admin language to Italian
Click on the menu 'Impostazioni'
Page title is in Spanish as well as table columns

This happens for all the pages in this section.
Expected Result
Page title: 'Località'
Table columns: 'Codice', 'Nome', 'Direzione'
Actual Result
Page title: 'Localidades'
Table columns: 'Código', 'Nombre', 'Dirección'
Screenshots

Additional context
No response

@shivendra-webkul
Checked and found that the issue has been fixed. Please check the screenshot here

Thank you very much, this was fast, very much appraciated!

@matteodoozy You're welcome! We are glad we could resolved issue promptly. If you encounter any more issues or have further questions, feel free to reach out.


Make Smarty Streets updates periodic

At the moment, the Smarty Streets imports into Combined are manual (last copy was 4/27). We could make them automatic.
This only affects 4% of our dataset at the moment, but it is the newest 4%.

Do you mean beyond hitting /smarty_streets_analysis/us? That will run it on anything that has been approved. It is manual and we still could add a trigger for it to run every X minutes.

Ooo. I didn't know about the URL.
Yeah, triggering that to run as often as the geocoder runs sounds perfect!
On Sun, May 10, 2020 at 8:13 PM Nathanael Burt<EMAIL_ADDRESS>wrote:

Do you mean beyond hitting /smarty_streets_analysis/us? That will run it
on anything that has been approved. It is manual and we still could add a
trigger for it to run every X minutes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/findthemasks/findthemasks/issues/891#issuecomment-626447210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6L2GB3T4KPZ6MGPWZDJXLRQ5UKJANCNFSM4M4H76HA
.

Hihi has this been done or are we okay with just hitting it manually in our data mod workflow for a while til we have more wizard time? There were some big asks this week :)

@4kbt set this up to run every 10 minutes, lmk if there are any issues

Looks like it is working great! Thank you!
On Tue, May 19, 2020 at 5:08 PM Nathanael Burt<EMAIL_ADDRESS>wrote:

@4kbt https://github.com/4kbt set this up to run every 10 minutes, lmk
if there are any issues
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/findthemasks/findthemasks/issues/891#issuecomment-631154646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6L2GCSCZSYF76KYY4ACI3RSMNKHANCNFSM4M4H76HA
.


Couldn't get response headers

Hi have little problem, i need get some items from Response Header, can you tell me how i can get it...
Our API gives response.body() with some data, and JWT are in headers, but i can't get it.
Any suggestions on how I might do this?
Thanks

Hi, I solved this problem through OkHttpClient.addInterseptor, where you can gat response.headers() and take any information, in my case Set-Cookie.
Thank you

@TarasMel Can you please give an example of how to add an Interceptor to get response headers. I have done a similar thing to add and remove request headers but not for response.


Support for current version of terraform?

Discussed in https://github.com/GoogleCloudPlatform/terraformer/discussions/1257

Originally posted by 9digitdev March 14, 2022
What is the process to upgrade Terraformer to support the most recent version of terraform? The most recent version listed today is 1.1.7. Would this be a major overhaul?

Its frustrating to see terraformer  using "terraform_version": "0.12.31"
even Terraform version installed installed is 1.3.2
is there any workaround?

https://github.com/GoogleCloudPlatform/terraformer#migration-state-version


beforeremove/afterremove: 'this' only has _id

I'm performing some functions using the beforeremove (I was actually using afterremove, but beforeremove is easier to debug). If I have the following:
beforeremove: function(){
    console.log(this);
}

I get a mostly empty document with only the _id. Is this how it is supposed to work? I assume I should be able to get the rest of the object? It clearly has more fields with data, they show as null.

Yes it has. However you have to know that when using the console.log(object) you're using a reference to the object. Because of that when you investigate the object in the console it doesn't have a state from the moment you printed it to the console. Instead, it has a star from the moment you're investigating it, so the object does not exist. You have to do something like this:
console.log(EJSON.stringify(this.get()));

Or any other technic that would convert a reference to the string. If you don't want to do that, it's better to use chrome debugger and set breakpoints.

Using the chrome inspector it allows me to read the whole object. Here's are results from using 'this' in beforeremove vs find from the inspector:
console.log(this):

console.log(Links.findOne({_id: id})) from chrome console:

As you can see, the _id is returned in both cases, however in the first all fields are null except the _id. So for instance if I try to use this.url it returns undefined, where in other event scripts that sort of use works just fine.

It's strange. I've made a test. My class:
Posts = new Mongo.Collection('posts');
Post = Astro.Class({
  name: 'Post',
  collection: Posts,
  fields: {
    a: 'string',
    b: 'string'
  },
  events: {
    beforeremove: function() {
      console.log(this);
    }
  }
});

And the console output

Could you create a reproduction repository?

OK, I figured it out. In my file I was using this snipped:
(new Link({_id:this._id})).remove()

I got the idea from here: https://github.com/jagi/meteor-astronomy/issues/25
I'm still not sure why 'this' doesn't return the entire object in this case, but I changed it to the normal remove syntax and it's working now, so problem solved :)

It's because, the new Link({_id: this._id}); does not fetch a document from the database. You have to do Links.findOne(this._id).remove();


Cryptomator.Cryptomator version 1.6.11

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

The mainfest needs to be updated, will do that before the PR.


Move rhel9.4 test to testing-farm

Currently there are still two bugs in testing-farm that block some case from success, but we can enable rhel9.4 test first.

https://github.com/virt-s1/rhel-edge/issues/7544
https://github.com/virt-s1/rhel-edge/issues/7543

@yih-redhat could you please fix commit line error? Thanks.

@yih-redhat could you please fix commit line error? Thanks.

fixed.

Use one runner and use matrix of arch sometimes will cause timeout issue and cannot see the sub-job status. So I changed it back to use two runners, one is for x86 and one is for aarch64.
Test ci looks good here: https://github.com/yih-redhat/tmt-demo/pull/76

@henrywang Could you please review this pr?


The following message parsing failed: Error in SIP message at line 0 offset 0

The following message parsing failed: Error in SIP message at line 0 offset 0:
Thanks!
SIP Message ( does not contain [ and ] ):
[REGISTER sip:34020000002000000001@<IP_ADDRESS>:5060 SIP/2.0
Via: SIP/2.0/UDP <IP_ADDRESS>:5060;rport;branch=z9hG4bK1585760165
From: sip:34020000001320000360@<IP_ADDRESS>:5060;tag=1882859352
To: sip:34020000001320000360@<IP_ADDRESS>:5060
Call-ID<EMAIL_ADDRESS>CSeq: 3 REGISTER
Contact: *
Authorization: Digest username="34020000001320000360", realm="3402000000", nonce="MTYwMzM2NDU0MA==", uri="sip:34020000002000000001@<IP_ADDRESS>:5060", response="39c7240195630f0b26124c00db7cfa5c", algorithm=MD5, cnonce="0a4f113b", qop=auth, nc=00000002
Max-Forwards: 70
User-Agent: VCP MWARE
Expires: 0
RegMode: DEVICE;Describe=IPC-S642-IR;Register;DevVer=CIPC-B23<IP_ADDRESS>528
ReplaceDescribe: IPC-S642-IR;ProductId=defaultProductId;RegionCode=NONE;Vendor=UNIVIEW;Resolve=HIC1080P;Ptzfg=1;;SnmpVer=v3;DescribeAssy=PAU-X5;ReplaceNameAssy=PAU-X5
Ability: UCSStore=0
Content-Length: 0
]

Look at your contact header.

It's not a valid URI.

Oh just checked the abnf and seems to be valid

Contact
=
( "Contact" | "m" ) ":" ( "*" | ( 1#( ( name-addr | addr-spec ) *( ";" contact-params ) ) ) )

Related to this:

Registrations expire as described above or may be removed explicitly
by setting the expires parameter for an existing registration to zero
or including an Expires: 0 header field. Registrations are matched
based on the user, host, port and maddr parameters. A client can
remove all registrations by including a single Contact header field
with the wildcard address "*". This usage is only allowed in REGISTER
requests when a Expires header with value of zero is present.

Since Expire is 0 in your case Contact: * is correct.

Indeed. Thanks for the report @umbrellary. This sounds like a simple fix. Would you like to send us a pull request adding a special case for star contact? We should be able to merge that right away. Otherwise we'll can fix it for you in the next round of changes.


Feature/custom options

this adds the ability to specify custom options in a consumer's package.json.
It also has a large refactor for performance / testability.
Also messed up the git log with some noob errors on using git revert -i to squash the commits :/

Current coverage is 98.97% (diff: 98.96%)

No coverage report found for master at 1bf8a3b.

Powered by Codecov. Last update 1bf8a3b...3e2bb43