text:
Function does not obey Enums

Describe the bug
I set a enum for one of the function inputs.
I have a pydantic class that refers to the enum.
The output args show that the enum is not followed.
Expected behavior
I would expect that the generated args obey the enum I set for that field.

can you produce an example and show me your prompts?

Apologies for commenting on a closed issue, but I'm seeing this consistently on all of the examples I've run so far which make use of enums.
I've tried the following:

the query planner example from the web docs;
the more detailed query planner execution example; and
a range of input queries, from quite complex down to very simple (and including the example input queries from the docs); and
the instructions here (also linked above) to try to coerce the model.

In each case, the failure mode was the same: Pydantic validation errors on the enum field. It's pretty consistently trying to use strings like "root", "node", "intermediate", "leaf", "end", "query", "calculation", etc, apparently ignoring the contents of the enum entirely.
I'm on Python 3.11.6, instructor 0.2.8, pydantic_2.4.2 and pydantic_core 2.10.1.  I tried executing both through a Jupyter notebook and as a script from the command line.
Appreciate any guidance you might be able to provide!  Please let me know if there's any additional information I can provide which would be helpful.

I want to note that this newly started failing yesterday without changes in my stack.
So not quite sure what that means

Experiencing the same yesterday. Enums repeatedly ignored

i wonder if models changed... @chengyjonathan @alexclaydon I'll rerun my examples as tests next time.
also have you guys tried the new retry logic by adding the
max_retries=2
It'll cost more tokens., but it can patch while i see if i can improve my prompts

Thanks Jason, yes I actually just came back with the intention to add that information to my original comment: these validation errors are happening for me even when using a high number of retries (I tested up to 5) and GPT-4.  The consistently is striking - it's doesn't seem to be intermittent.  I haven't managed to do a successful run even with low-complexity code and input questions.

@alexclaydon do you have a specifc gist i can use as a quick eval? I wonder if its how deserialization to json is.
or if literal string could help too

Thanks Jason - I’m not at my desk atm but could send you one this afternoon APAC. For now, though, if you run the query planner execution example as a script from the command line it should fail with those errors (assuming same dependencies). On Nov 2, 2023, at 7:22, Jason Liu @.***> wrote:
@alexclaydon do you have a specifc gist i can use as a quick eval? I wonder if its how deserialization to json is.
or if literal string could help too
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Update:
Just tried the following:

Freezing the model at "gpt-4-0613": No change to result
Took the example in the docs here and changed:

    node_type: QueryType = Field(
        default=QueryType.SINGLE_QUESTION,
        description="Choose either 'single_question' or 'merge_multiple_responses' depending on the type of node.",
    )

to:
    node_type: str = Field(
        ...,
        description="Choose either 'single_question' or 'merge_multiple_responses' depending on the type of node.",
    )

This allowed me to run the code without it throwing validation errors, but I got the following result:
{
    "query_graph": [
        {
            "id": 1,
            "question": "What is the population of Canada?",
            "dependancies": [],
            "node_type": "root"
        },
        {
            "id": 2,
            "question": "What is Jason's home country?",
            "dependancies": [],
            "node_type": "root"
        },
        {
            "id": 3,
            "question": "What is the population of Jason's home country?",
            "dependancies": [
                2
            ],
            "node_type": "intermediate"
        },
        {
            "id": 4,
            "question": "What is the difference in populations of Canada and the Jason's home country?",
            "dependancies": [
                1,
                3
            ],
            "node_type": "end"
        }
    ]
}

It still seems to be ignoring the description attribute on that field and trying to use "root", "intermediate", "end" - similar to the strings it was passing to the enum previously.

I just want to add that I'm noticing the same thing. The enum-description
fields no longer get populated. Which is interesting.
On Wed, Nov 1, 2023 at 7:54 PM Alex Claydon @.***>
wrote:

Update:
Just tried the following:

Freezing the model at "gpt-4-0613": No change to result
Took the example in the docs here
https://jxnl.github.io/instructor/examples/planning-tasks/ and
changed:

node_type: QueryType = Field(
    default=QueryType.SINGLE_QUESTION,
    description="Choose either 'single_question' or 'merge_multiple_responses' depending on the type of node.",
)

to:
node_type: str = Field(
    ...,
    description="Choose either 'single_question' or 'merge_multiple_responses' depending on the type of node.",
)

This allowed me to run the code without it throwing validation errors, but
I got the following result:
{
"query_graph": [
{
"id": 1,
"question": "What is the population of Canada?",
"dependancies": [],
"node_type": "root"
},
{
"id": 2,
"question": "What is Jason's home country?",
"dependancies": [],
"node_type": "root"
},
{
"id": 3,
"question": "What is the population of Jason's home country?",
"dependancies": [
2
],
"node_type": "intermediate"
},
{
"id": 4,
"question": "What is the difference in populations of Canada and the Jason's home country?",
"dependancies": [
1,
3
],
"node_type": "end"
}
]
}
It still seems to be ignoring the description attribute on that field and
trying to use "root", "intermediate", "end" - similar to the strings it was
passing to the enum previously.
—
Reply to this email directly, view it on GitHub
https://github.com/jxnl/instructor/issues/77#issuecomment-1789892814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI254WLCF3QZBDG7KP2QB3LYCLVN7AVCNFSM6AAAAAA3RNKY7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBZHA4TEOBRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

They're tracking an issue over on Marvin that may be related: https://github.com/PrefectHQ/marvin/issues/604#issuecomment-1791676517

The short term sollution would be to use Literal["one' ,"two"] Or prompt the llm more strictly

authors: alexclaydon chengyjonathan jxnl

repo: jxnl/instructor


text:
[Bug]: Covariance Matrix Not Positive Definite in MultivariateNormal Sampling

Describe the bug
When using the PyramidDiTForVideoGeneration pipeline, a ValueError occurs due to the covariance matrix not being positive definite when sampling from a multivariate normal distribution using torch.distributions.MultivariateNormal. This happens in the sample_block_noise method, even though the covariance matrix should theoretically be positive definite for gamma = 0.33333333.
Error Message:
ValueError: Expected parameter covariance_matrix (Tensor of shape (4, 4)) of distribution MultivariateNormal(...) to satisfy the constraint PositiveDefinite(), but found invalid values:
tensor([[ 1.0000, -0.3333, -0.3333, -0.3333],
        [-0.3333,  1.0000, -0.3333, -0.3333],
        [-0.3333, -0.3333,  1.0000, -0.3333],
        [-0.3333, -0.3333, -0.3333,  1.0000]])

To Reproduce:

Run the generate method of PyramidDiTForVideoGeneration with the following parameters (adjusted as needed for your environment):
frames = model.generate(
    prompt=prompt,
    num_inference_steps=[20, 20, 20],
    video_num_inference_steps=[10, 10, 10],
    height=height,
    width=width,
    temp=temp,
    guidance_scale=7.0,
    video_guidance_scale=5.0,
    output_type="pil",
    cpu_offloading=True,
    save_memory=True,
)

The error occurs during the execution of the sample_block_noise method within the pipeline.

Sample Code:
def sample_block_noise(self, bs, ch, temp, height, width):
    gamma = self.scheduler.config.gamma  # gamma = 0.33333333
    covariance_matrix = torch.eye(4) * (1 + gamma) - torch.ones(4, 4) * gamma
    dist = torch.distributions.MultivariateNormal(
        torch.zeros(4), covariance_matrix
    )
    block_number = bs * ch * temp * (height // 2) * (width // 2)
    noise = dist.sample((block_number,))  # [block_number, 4]
    noise = noise.view(bs, ch, temp, height // 2, width // 2, 2, 2)
    noise = noise.permute(0, 1, 2, 3, 5, 4, 6).reshape(bs, ch, temp, height, width)
    return noise

Expected behavior:
The method should sample noise from a multivariate normal distribution without errors, allowing the video generation process to proceed.
Actual behavior:
A ValueError is raised indicating that the covariance matrix is not positive definite.
Analysis:

The covariance matrix constructed is:
$$
\begin{bmatrix}
1 & -\gamma & -\gamma & -\gamma \
-\gamma & 1 & -\gamma & -\gamma \
-\gamma & -\gamma & 1 & -\gamma \
-\gamma & -\gamma & -\gamma & 1 \
\end{bmatrix}
$$
With gamma = 0.33333333, the eigenvalues of this matrix are positive:
$$ \lambda_1 = 1 - \gamma = 0.6667 \hspace{0.5cm}  (\text{multiplicity 3}) $$
$$ \lambda_2 = 1 + 3 \gamma = 2.0 $$

Despite this, numerical precision issues may cause PyTorch's positive definiteness check to fail.

Proposed Solution:
To resolve the error, I have modified the sample_block_noise method by:

Adding a small epsilon (in my case, 1e-6) to the diagonal elements of the covariance matrix, so to improve numerical stability.
Using the Cholesky decomposition (scale_tril), it is more efficient to sample using Cholesky factorization. If the covariance matrix is not positive definitive, then surely it will go to exception handling.

Modified Code:
def sample_block_noise(self, bs, ch, temp, height, width):
    gamma = self.scheduler.config.gamma  # gamma = 0.33333333
    epsilon = 1e-6  # Small value to ensure positive definiteness
    covariance_matrix = (
        torch.eye(4) * (1 + gamma + epsilon) - torch.ones(4, 4) * gamma
    )
    # Ensure the covariance matrix is symmetric
    covariance_matrix = (covariance_matrix + covariance_matrix.T) / 2
    # Compute the Cholesky decomposition
    try:
        scale_tril = torch.linalg.cholesky(covariance_matrix)
    except RuntimeError as e:
        print("Cholesky decomposition failed:", e)
        return None
    dist = torch.distributions.MultivariateNormal(
        torch.zeros(4), scale_tril=scale_tril
    )
    block_number = bs * ch * temp * (height // 2) * (width // 2)
    noise = dist.sample((block_number,))  # [block_number, 4]
    noise = noise.view(bs, ch, temp, height // 2, width // 2, 2, 2)
    noise = noise.permute(0, 1, 2, 3, 5, 4, 6).reshape(bs, ch, temp, height, width)
    return noise

Outcome:
I have resolved the error via this modification.  See if anyone gets this same error and so this might save time and hopefully does all the explaining.
Alternative approaches to solving this:
Another way to solve this might be to enforce all computations to be done in double precision.
Like this:
gamma = self.scheduler.config.gamma
covariance_matrix = (
    torch.eye(4, dtype=torch.float64) * (1 + gamma) - torch.ones(4, 4, dtype=torch.float64) * gamma
)
dist = torch.distributions.MultivariateNormal(
    torch.zeros(4, dtype=torch.float64), covariance_matrix
)

But I think this is just unnecessary, unless you plan to apply this to induce numerical consistency and (hopefully) help improve numerical stability across entire project.

Thank you for providing a solution, it is really helpful for us! We were considering upgrading the PyTorch version to use FlexAttention, but were concerned since someone reported a similar bug with a higher PyTorch version. We will look at your solution if we encounter this bug.

Yes. I am using latest version of PyTorch 2.5.
I will provide the environment I was using anyway, hopefully it helps :)

The output of `python collect_env.py`
PyTorch version: 2.5.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 24.04.1 LTS (x86_64)
GCC version: (Ubuntu 12.3.0-17ubuntu1) 12.3.0
Clang version: Could not collect
CMake version: version 3.28.3
Libc version: glibc-2.39

Python version: 3.12.3 (main, Sep 11 2024, 14:17:37) [GCC 13.2.0] (64-bit runtime)
Python platform: Linux-6.8.0-45-generic-x86_64-with-glibc2.39
Is CUDA available: True
CUDA runtime version: 12.1.105
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: Quadro RTX 5000
Nvidia driver version: 560.35.03
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_graph.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_heuristic.so.9.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops.so.9.2.1
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        48 bits physical, 48 bits virtual
Byte Order:                           Little Endian
CPU(s):                               16
On-line CPU(s) list:                  0-15
Vendor ID:                            AuthenticAMD
Model name:                           AMD Ryzen 7 5800X 8-Core Processor
CPU family:                           25
Model:                                33
Thread(s) per core:                   2
Core(s) per socket:                   8
Socket(s):                            1
Stepping:                             0
Frequency boost:                      enabled
CPU(s) scaling MHz:                   69%
CPU max MHz:                          4850.1948
CPU min MHz:                          2200.0000
BogoMIPS:                             7600.35
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local user_shstk clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm debug_swap
L1d cache:                            256 KiB (8 instances)
L1i cache:                            256 KiB (8 instances)
L2 cache:                             4 MiB (8 instances)
L3 cache:                             32 MiB (1 instance)
NUMA node(s):                         1
NUMA node0 CPU(s):                    0-15
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Vulnerable: Safe RET, no microcode
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

ROCM Version: Could not collect
Neuron SDK Version: N/A
Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:

GPU0	CPU Affinity	NUMA Affinity	GPU NUMA ID
GPU0	 X 	0-15	0		N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

Versions of relevant libraries:
[pdm] accelerate==1.0.1
[pdm] contexttimer==0.3.3
[pdm] diffusers==0.30.3
[pdm] einops==0.8.0
[pdm] ftfy==6.3.0
[pdm] gradio==5.1.0
[pdm] imageio==2.36.0
[pdm] imageio-ffmpeg==0.5.1
[pdm] ipykernel==6.29.5
[pdm] ipython==8.28.0
[pdm] ipywidgets==8.1.5
[pdm] jsonlines==4.0.0
[pdm] jupyter==1.1.1
[pdm] numpy==2.0.2
[pdm] opencv-python-headless==4.10.0.84
[pdm] packaging==24.1
[pdm] pandas==2.2.3
[pdm] plotly==5.24.1
[pdm] python-magic==0.4.27
[pdm] scikit-image==0.24.0
[pdm] sentencepiece==0.2.0
[pdm] spacy==3.8.2
[pdm] streamlit==1.39.0
[pdm] tensorboardx==2.6.2.2
[pdm] tiktoken==0.8.0
[pdm] timm==1.0.11
[pdm] torch==2.5.0+cu121
[pdm] torchmetrics==1.4.3
[pdm] torchvision==0.20.0+cu121
[pdm] tqdm==4.66.5
[pdm] transformers==4.45.2
[pdm] wheel==0.44.0
[conda] Could not collect

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Locators to be blurred should ignore NoSuchElementException error in Capture Screenshot keywords

Is your feature request related to a problem? Please describe.
I have a single array of many fields to be blurred in the screenshot, but not all of them appears in every page of the application, so eventually I get NoSuchElementException error because one of these fields is not present in the current page.
I'm using a test case template to perform the same set of actions in many pages, would not be pratical to create a locator array for each page.
Describe the solution you'd like
Capture Screenshot kws could ignore NoSuchElementException error and proceed to next locator in the array.
Describe alternatives you've considered
I could create an array variable for each page, but that would kill the purpose of re-usability of code.
Additional context
Add any other context or screenshots about the feature request here.

@AllanMedeiros Makes sense. This would help avoid creating multiple blur variable arrays. Will push the change for this as part of the upcoming release.

Added this import in selenium_hooks.py
from selenium.common.exceptions import NoSuchElementException
And changed this method like this.
def blur_regions(self, selectors, radius, path):
        selectors = selectors if isinstance(selectors, list) else [selectors]

        for region in selectors:
            try:
                prefix, locator, element = self.find_element(region)
            except NoSuchElementException:
                continue

            area_coordinates = self._get_coordinates(prefix, locator, element)
            left, right = math.ceil(area_coordinates['left']), math.ceil(area_coordinates['right'])
            top, bottom = math.ceil(area_coordinates['top']), math.ceil(area_coordinates['bottom'])
            left, right, top, bottom = self._update_coordinates(left, right, top, bottom)
            im = Image.open(path + '/img' + str(self.count) + '.png')
            cropped_image = im.crop((left, top, right, bottom))
            blurred_image = cropped_image.filter(ImageFilter.GaussianBlur(radius=int(radius)))
            im.paste(blurred_image, (left, top, right, bottom))
            im.save(path + '/img' + str(self.count) + '.png')

Let me know if you thought something different than that.
But after a few runs, seems to be working fine.

@AllanMedeiros This is exactly how I was planning to fix it. Could you raise a pull request with this code please?

ok, done!

Released in v1.3.0

authors: AllanMedeiros jz-jess

repo: jz-jess/RobotEyes


text:
validation rule on a textarea

Hi,
may be this trouble was allready reported, sorry, i didn't take time to search.
I've past the last 4 hours to find why a rule defined on a textarea was not working at all. I've realized the rule was applied using the attribute name of this textarea and not his attribute id.
In all forms, i use both attributes id and name, but sometimes, i use array for the name, for example id="section_name" and name="section[name]". But if i add rules in the usual « $('#form')validate(rules) » using the id, this won't work.
I had to add a rule specificly after this part using $('#section_name').rules('add',{});
May be some improvment could be appreciated.
Thanks.

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!

repo: jzaefferer/jquery-validation

license: mit

license_source: bigquery


text:
jquery validator plugin 1.11.0  How to enable validation of fields in a div that is hidden

I have a number of fields with jquery validation within a div tag. These belong to a Collapsible section.  When the section is collapsed, the div tag containing the fields is hidden. On submit, jquery is not validating these fields which are currently in a hidden div
Tried this, but doesn't work.
$( document ).ready(function() {
    $.validator.setDefaults({
        ignore: ""
    });
 });

How to enable validation of these fields?

I have the same problem

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!

authors: JavaLove doruchiulan jzaefferer


text:
[Bug] Turkish İi Iı casing problem

Description
There's a problem with Turkish language.
There are 2 different "i" letters:

with dot: lowercase i, uppercase İ
without dot: lowercase ı, uppercase I

Thus, case conversion rules for Turkish are slightly different than for English (Latin):

için → IÇIN (latin, how it is now)
için → İÇİN (turkish, how it should be)
IŞIK → işik (latin, how it is now)
IŞIK → ışık (turkish, how it should be)

You can see this difference in browser console:
console.log('için'.toUpperCase())           // → IÇIN
console.log('için'.toLocaleUpperCase('tr')) // → İÇİN
console.log('IŞIK'.toLowerCase())           // → işik
console.log('IŞIK'.toLocaleLowerCase('tr')) // → ışık

This leads to all sorts of problems, to name a few:

words ışık and Işık are now stored separately.
words staring with İ cannot be highlighted. You can create term off of them, but it then doesn't get highlighted.
you cannot change casing of terms because Lute thinks that Işık and ışık are different words.
searching such terms you now have to account for their casing.

To Reproduce
You can use this text to play with.
Bla ışık bla

Bla Işık bla

Bla için bla

Bla İçin bla

Turkish works with English settings, so you don't need to create a new language.

Confirmed in my dev env w/ Lute v2.1.0, thanks for the detailed issue.
I created terms for all 4 terms, though the first two are similar:

Here's what's in the db:
sqlite> .headers on
sqlite> .mode column
sqlite> select wotext, wotextlc from words where wolgid = 8;
WoText  WoTextLC
------  --------
ışık    ışık
Işık    işık
için    için
İçin    i̇çin

The downcasing now isn't handled by javascript, it's all done on the server.

After some very brief searching, it looks like there's no built-in way to work around this in PHP.  Every solution I looked at boiled down to just hardcoding a replace for those particular characters, for that language.  One post at https://www.php.net/manual/tr/function.mb-strtolower.php suggested $str = mb_strtolower($str, mb_detect_encoding($str)); but that didn't make a difference on my machine.
The various solutions were all something like
function trkish_lower($str){
    $find = array('İ','I');
    $replace = array('i', 'ı');
    return str_replace($find,$replace,$str);
}

This would need to be in the Language itself ... I'm not sure if it's worth it to make something general (with field LgDowncaseMapping, containing e.g. for Turkish "İ,i;I,ı"), because as far as I've read Turkish is the only language requiring this!  Optionally, Turkish could have a specialized "downcase" function, and that would be used where needed.
Annoyingly, Python seems to have the same problem with these Turkish letters, so the same hacky fix would be needed.  string.casefold() exists in Python but it changes characters too much to be considered (e.g., it removes accents in some situations).

Yeah, I anticipated that PHP has no means to deal with this sort of thing.
Actually, it's crucial to consider this aspect before selecting a stack for code migration.
If there's no support for collations in the programming language and the database engine, implementing them can be quite challenging. And natural languages have all sort of weird things going on. Apart from case-sensitiviy there are also sorting and search problems to contend with. For instance, in Russian when searching, letters е and ё should be treated as the same, but distinct in all other cases.

Yes, it's a tough problem space.  Even something as common as German separable verbs isn't handled well by any tool out there.
It's odd that Turkish continues to be such a common problem.  For Turkish, it should be straightforward to implement the workaround.  I don't know what I don't know, so test cases like you gave in the issue are a massive help.
For Russian searching, should е and ё be considered the same simply because usage appears to be non-standard?  (at least according to https://www.rbth.com/education/328862-yo-russian-alphabet).
I am hoping that the code can decently handle the majority of the cases thrown at it.  We do the best we can possibly do, given the constraints :-)  As far as I can tell, Python and Sqlite are still fine choices, again for the majority.  It may be that some special branches or fixes need to be made to support other cases ... but I hope not.
Thanks again for the detail in this ticket, maybe we can chat further on Discord if you have a sense that there are further difficulties with other languages (like the Russian yo issue).

I currently feel that the easiest way to do this is to create a Turkish parser, inheriting from Space Delimited parser, and to add some "downcase" rule to the abstract parser src/Domain/AbstractParser.php, e.g.
    /**
     * Many writing systems can just downcase:
     */
    public function getLowercase(string $text) {
        return mb_strtolower($text);
    }

then the Turkish parser could just hack that a touch:
function getLowercase($text){
    $find = array('İ','I');
    $replace = array('i', 'ı');
    $str = str_replace($find,$replace,$text);
    return mb_strtolower($text);
}

The turkishparser option would have to be added to the Language and perhaps to some other code as well, a search for the existing parser stuff should find it.
We'd need test cases for Turkish text to ensure no multibyte corruption weirdness!  And then a test or two to ensure that the reading pane updates correctly.

Have some work in progress in iss_71_Turkish_wip branch pushed to this repo.  All tests and a small sample is passing, including the cases listed in this ticket.
Need to clean up some of the code, the change introduced some hard-to-follow thrash.

Code cleaned up for Turkish, seems to work.  Merged into the develop branch, will get launched after it bakes in my environment a bit.
Branch iss_71_Turkish is what was merged, it's in this repo.

Launch with 2.1.2, should be fixed.  Thank you @disfated for all of the info.

authors: disfated jzohrab

repo: jzohrab/lute

license: Unlicense


text:
chore(package): update npm-pkgbuild to version 6.0.7

Closes #346

:tada: This PR is included in version 1.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

source: gharchive/pull-request


text:
Model average

This PR implements Dan's idea about model average. Detailed description could be found on the issue https://github.com/k2-fsa/icefall/issues/337.
The comment history about the implementation could be found on https://github.com/yaozengwei/icefall/pull/1.

Thanks!

Does it improve the results?

When trained on train-clean-100 with 3 gpu for 30 epochs, average_period=100, I got following results with greedy search decoding:

decode with epoch-30, avg=5, 7.14 & 19.33 (without averaged model) -> 7.03 & 18.85 (with averaged model);
decode with epoch-30, avg=10, 6.99 & 18.93 (without averaged model) -> 6.91 & 18.65 (with averaged model).

When trained on full librispeech with 6 gpu for 30 epochs, average_period=100, I got following results with greedy search decoding:

decode with epoch-30, avg=5, 2.77 & 6.77 (without averaged model) -> 2.72 & 6.67 (with averaged model);
decode with epoch-30, avg=10, 2.78 & 6.68 (without averaged model) -> 2.74 & 6.67 (with averaged model).

The model averaging strategy slightly improves the result. Also, it would reduce I/O for model-averaging during decoding, since it just need to load 2 checkpoints (start and end) for model averaging.

authors: csukuangfj yaozengwei


text:
Add ability to enable "latest" image tag support for Spegel registry.

Is your feature request related to a problem? Please describe.
Currently, the Spegel registry is hard-coded to not support the latest image tag by design. While this is definitely best-practice (and there are negative implications to using latest in general), there are circumstances where the latest tag may be unavoidable. This could potentially cause major issues for users in air-gap/limited connectivity environments who are reliant on Spegel for resilience, and node failure could result in workloads not being able to be rescheduled to other nodes. In those circumstances, it'd be ideal if Spegel could be configured to be able to support the latest tag, while defaulting to best-practice and not enabling it.
Describe the solution you'd like
Have an environment variable/configuration setting available in K3s to enable supporting latest tags with Spegel, with that configuration defaulting to false.
Describe alternatives you've considered
N/A
Additional context
N/A

##Environment Details
Reproduced using VERSION=v1.29.2+k3s1
Validated using COMMIT=364dfd8b89e62bc7816aa4843db8deb6f6fd2978
Infrastructure

[X] Cloud

Node(s) CPU architecture, OS, and version:
Linux 5.14.21-150500.53-default x86_64 GNU/Linux
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
Cluster Configuration:
NAME              STATUS   ROLES                       AGE     VERSION
ip-1              Ready    control-plane,etcd,master   3m27s   v1.29.2+k3s1

Config.yaml:
node-external-ip: 127.0.0.1
token: trollolololol
write-kubeconfig-mode: 644
debug: true
protect-kernel-defaults: true
cluster-init: true
embedded-registry: true

Steps

$ curl https://get.k3s.io --output install-"k3s".sh
$ sudo chmod +x install-"k3s".sh
$ sudo groupadd --system etcd && sudo useradd -s /sbin/nologin --system -g etcd etcd
$ sudo modprobe ip_vs_rr
$ sudo modprobe ip_vs_wrr
$ sudo modprobe ip_vs_sh
$ sudo printf "on_oovm.panic_on_oom=0 \nvm.overcommit_memory=1 \nkernel.panic=10 \nkernel.panic_ps=1 \nkernel.panic_on_oops=1 \n" > ~/90-kubelet.conf
$ sudo cp 90-kubelet.conf /etc/sysctl.d/
$ sudo systemctl restart systemd-sysctl
$ sudo vim /etc/rancher/k3s/registries.yaml //files pasted below
$ sudo cat /etc/rancher/k3s/registries.yaml
$ VERSION=v1.29.2+k3s1
$ sudo INSTALL_K3S_VERSION=$VERSION INSTALL_K3S_EXEC=server INSTALL_K3S_SKIP_ENABLE=true ./install-k3s.sh
$ sudo vim /etc/systemd/system/k3s.service.env
$ sudo cat /etc/systemd/system/k3s.service.env
$ sudo systemctl start k3s
$ sudo journalctl -u k3s | grep -i 'spegel'
$ $ sudo journalctl -u k3s | grep -i 'latest' //looking at how the environment file flag is passed
$ kgn //kubectl get nodes
$ get_figs //sudo cat /etc/rancher/k3s/config.yaml
$ k run nginx --image=nginx:latest
$ kgp //kubectl get pods //watch for nginx to be up and running
$ sudo journalctl -u k3s | grep -i 'spegel' //observe spegel pulls nginx image
$ COMMIT=364dfd8b89e62bc7816aa4843db8deb6f6fd2978
$ sudo INSTALL_K3S_COMMIT=$COMMIT INSTALL_K3S_EXEC=server INSTALL_K3S_SKIP_ENABLE=true ./install-k3s.sh
$ sudo vim /etc/rancher/k3s/registries.yaml //below file with "*":
$ sudo vim /etc/systemd/system/k3s.service.env //K3S_P2P_ENABLE_LATEST=true
$ sudo systemctl start k3s //let all pods get up and running before deploying nginx//alpine:latest pods observing them being mirrored in journalctl by spegel log-level=info

Results:
$ sudo journalctl -u k3s | grep -i 'latest' //environment file is detected and passed in but there is no code change to receive the behavior change until the COMMIT_ID test
Mar 12 22:20:30 k3s[3695]: I0312 22:20:30.556531    3695 kube.go:621] List of node(ip-1) annotations: map[string]string{"alpha.kubernetes.io/provided-node-ip":"1", "etcd.k3s.cattle.io/local-snapshots-timestamp":"2024-03-12T22:20:16Z", "etcd.k3s.cattle.io/node-address":"1", "etcd.k3s.cattle.io/node-name":"ip-1-fa0889ec", "k3s.io/external-ip":"1", "k3s.io/hostname":"ip-1", "k3s.io/internal-ip":"1", "k3s.io/node-args":"[\"server\",\"--node-external-ip\",\"18.219.99.135\",\"--token\",\"********\",\"--write-kubeconfig-mode\",\"644\",\"--debug\",\"true\",\"--protect-kernel-defaults\",\"true\",\"--cluster-init\",\"true\",\"--embedded-registry\",\"true\"]", "k3s.io/node-config-hash":"7KBTRB33NINMHM45IO2ECY2ICVV26AOKOUYKYXBYWIOB3TE4C2BA====", "k3s.io/node-env":"{\"K3S_DATA_DIR\":\"/var/lib/rancher/k3s/data/7d0aa19ffc230d4322f04d1ae8783e54ce189dfc4cbfa0a6afcdcabec2346d0c\",\"K3S_P2P_ENABLE_LATEST\":\"true\"}", "node.alpha.kubernetes.io/ttl":"0", "p2p.k3s.cattle.io/node-address":"/ip4/1/tcp/5001/p2p/QmXuFJZzzi3XuoHwkDBdKGhexU2DdN5czEBMAmrVvukRWy", "volumes.kubernetes.io/controller-managed-attach-detach":"true"}

Mar 12 22:23:20 ip-1 k3s[3695]: time="2024-03-12T22:23:20.279078074Z" level=info msg="PullImage \"nginx:latest\""
Mar 12 22:23:24 ip-1 k3s[3695]: time="2024-03-12T22:23:24.082080186Z" level=info msg="ImageCreate event name:\"docker.io/library/nginx:latest\" labels:{key:\"io.cri-containerd.image\" value:\"managed\"}"
Mar 12 22:23:24 ip-1 k3s[3695]: time="2024-03-12T22:23:24.084815570Z" level=info msg="stop pulling image docker.io/library/nginx:latest: active requests=0, bytes read=70545778"
Mar 12 22:23:24 ip-1 k3s[3695]: time="2024-03-12T22:23:24.090248449Z" level=info msg="ImageUpdate event name:\"docker.io/library/nginx:latest\" labels:{key:\"io.cri-containerd.image\" value:\"managed\"}"
Mar 12 22:23:24 ip-1 k3s[3695]: time="2024-03-12T22:23:24.098141614Z" level=info msg="Pulled image \"nginx:latest\" with image id \"sha256:92b11f67642b62bbb98e7e49169c346b30e20cd3c1c034d31087e46924b9312e\", repo tag \"docker.io/library/nginx:latest\", repo digest \"docker.io/library/nginx@sha256:18090843a20ba39719ca4f389d509063ea4fcce9d16c7168f62404b6d630bc3e\", size \"70534964\" in 3.819031142s"
Mar 12 22:23:24 ip-1 k3s[3695]: time="2024-03-12T22:23:24.098182283Z" level=info msg="PullImage \"nginx:latest\" returns image reference \"sha256:92b11f67642b62bbb98e7e49169c346b30e20cd3c1c034d31087e46924b9312e\""

$ sudo journalctl -u k3s | grep -i 'spegel'
Mar 12 22:20:14 ip-1 k3s[3695]: time="2024-03-12T22:20:14Z" level=info msg="spegel 2024/03/12 22:20:14 p2p: \"level\"=0 \"msg\"=\"starting p2p router\" \"id\"=\"/ip4/1.1.1.3/tcp/5001/p2p/QmXuFJZzzi3XuoHwkDBdKGhexU2DdN5czEBMAmrVvukRWy\""
Mar 12 22:20:14 ip-1 k3s[3695]: time="2024-03-12T22:20:14Z" level=info msg="spegel 2024/03/12 22:20:14 p2p: \"level\"=0 \"msg\"=\"leader is self skipping connection to bootstrap node\""
Mar 12 22:20:14 ip-1 k3s[3695]: time="2024-03-12T22:20:14Z" level=info msg="spegel 2024/03/12 22:20:14 p2p: \"level\"=0 \"msg\"=\"leader is self skipping connection to bootstrap node\""
Mar 12 22:20:14 ip-1 k3s[3695]: time="2024-03-12T22:20:14Z" level=info msg="spegel 2024/03/12 22:20:14 \"level\"=0 \"msg\"=\"running scheduled image state update\""
Mar 12 22:22:14 ip-1 k3s[3695]: time="2024-03-12T22:22:14Z" level=info msg="spegel 2024/03/12 22:22:14 p2p: \"level\"=0 \"msg\"=\"leader is self skipping connection to bootstrap node\""
Mar 12 22:24:14 ip-1 k3s[3695]: time="2024-03-12T22:24:14Z" level=info msg="spegel 2024/03/12 22:24:14 p2p: \"level\"=0 \"msg\"=\"leader is self skipping connection to bootstrap node\""

$ sudo journalctl -u k3s | grep -i -e spegel -e latest //latest support working
 level=info msg="spegel 2024/03/12 23:50:27 \"level\"=0 \"msg\"=\"running scheduled image state update\""
Mar 12 23:50:27 ip-1 k3s[16154]: time="2024-03-12T23:50:27Z" level=info msg="spegel 2024/03/12 23:50:27 \"level\"=5 \"msg\"=\"sync image event\" \"image\"=\"docker.io/library/alpine:latest@sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b\" \"type\"=\"UPDATE\""
Mar 12 23:50:27 ip-1 k3s[16154]: time="2024-03-12T23:50:27Z" level=info msg="spegel 2024/03/12 23:50:27 \"level\"=10 \"msg\"=\"advertising keys\" \"host\"=\"QmaXDv8hc2bZ3A1LAMZMwzQRkSX9pQG4CAeyQLoPFkgHFh\" \"keys\"=[\"docker.io/library/alpine:latest\" \"sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b\" \"sha256:6457d53fb065d6f250e1504b9bc42d5b6c65941d57532c072d929dd0628977d0\" \"sha256:05455a08881ea9cf0e752bc48e61bbd71a34c029bb13df01e40e3e70e0d007bd\" \"sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8\"]"

Files
temporary fix to hosts.toml file to carry on with this test - this is being covered by a separate issue. adding the server = "" allows the wildcard support in registries.yaml until a later fix gets added.
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/certs.d/_default/hosts.toml
# File generated by k3s. DO NOT EDIT.
server = ""

[host."https://127.0.0.1:6443/v2"]
  capabilities = ["pull", "resolve"]
  ca = ["/var/lib/rancher/k3s/agent/server-ca.crt"]
  client = [["/var/lib/rancher/k3s/agent/client-k3s-controller.crt", "/var/lib/rancher/k3s/agent/client-k3s-controller.key"]]

$ sudo cat /etc/systemd/system/k3s.service.env
K3S_P2P_ENABLE_LATEST=true

$ sudo cat /etc/rancher/k3s/registries.yaml
mirrors:
  docker.io:
  registry.k8s.io:
  gcr.io:
  quay.io:
  ghcr.io:

$ sudo cat /etc/rancher/k3s/registries.yaml //newer format //testing with a manual edit being addressed by another issue on hosts.toml
mirrors:
  "*":


text:
feat: Add support for custom annotations and labels for runners and starter

Resolves #23 and allows for adding of custom annotations and labels for runners and the starter.
Reasonably straight forward PR.
I did have a question about the imports however, it appears there are duplicate imports in runner.go and starter.go (k6 is imported in both of them but doesn't need to be, and is done so under 2 different names. As is core api from k8s). I can open another PR to create a helper.go that has newLabels, and the imports in it if desired. I found it a little confusing for a moment and is probably unnecessary.

Mistakenly merged #26 prior to this one, but since all commits are present there as well I'll just go ahead and close this one. Thanks!

authors: KnechtionsCoding simskij


text:
operator mariadb-operator (0.8.0)

Add operator mariadb-operator (0.8.0) to community operators

/merge possible

/merge possible


text:
operator mongodb-atlas-kubernetes (2.0.1)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/retest

/merge possible

/merge

@mporrato can you please merge this PR? The CI is all green

/merge possible

authors: framework-automation igor-karpukhin


text:
operator gitlab-operator-kubernetes (1.8.1)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

authors: framework-automation gl-distribution-oc


text:
Add NOTICE file for Apache license 2.0

This change adds NOTICE file in repository as https://infra.apache.org/apply-license.html#new

Pull Request Test Coverage Report for Build 3664097473

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 50.946%

Totals

Change from base Build 3649297321:
0.0%

Covered Lines:
862

Relevant Lines:
1692

💛  - Coveralls


text:
Fail to allocate SRIOV device using Multus and host-device CNI

Hi,
I have K8 cluster which runs on CentOS 7.7 VMs and then trying to bring up pod with multiple SRIOV interface. The VFs are passthrough into worker VMs.
Here is my setup details:

K8 cluster version : v1.13.4
Calico as a default CNI
Multus(version 3.2) as CNI meta plugin
sriov-device-plugin(version v3.1) device plugin for managing the VFs resources.
host-device(version v0.8.3) as CNI plugin
Created configMap for resource list with pf names for sriov hostdevice.
Created CRD by providing the resourceName annotation.

If I use resourceName annotation in the CRD yaml file, the Multus fail to allocate the device from the resource pool and passes it down to host-device CNI plugin.
Please have a look at the configuration and let me know what's going wrong.
Thanks in advance.
Error message while creating pod:
  [cluster-user@master1vm sriov-multus]$ kubectl describe pod testpod1
Warning  FailedCreatePodSandBox  2s                kubelet, worker1vm.novalocal  Failed create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "a58d7fb3a4cc7232f90f727b6a12bf458f3c655b3b5e958a72e7ecd69d70e122" network for pod "testpod1": NetworkPlugin cni failed to set up pod "testpod1_default" network: Multus: Err adding pod to network "host-device-network": Multus: error in invoke Delegate add - "host-device": specify either "device", "hwaddr", "kernelpath" or "pciBusID", failed to clean up sandbox container "a58d7fb3a4cc7232f90f727b6a12bf458f3c655b3b5e958a72e7ecd69d70e122" network for pod "testpod1": NetworkPlugin cni failed to teardown pod "testpod1_default" network: Multus: error in invoke Delegate del - "host-device": specify either "device", "hwaddr", "kernelpath" or "pciBusID"]

The sriov device plugin identify all the SRIOV device and created the resource pool.
[cluster-user@master1vm sriov-multus]$ kubectl -n kube-system logs kube-sriov-device-plugin-amd64-pbjsp
I1210 23:31:38.945300   22088 manager.go:112] Creating new ResourcePool: intel_sriov_hostdevice
I1210 23:31:38.945328   22088 factory.go:144] device added: [pciAddr: 0000:00:05.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945335   22088 factory.go:144] device added: [pciAddr: 0000:00:09.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945339   22088 factory.go:144] device added: [pciAddr: 0000:00:0a.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945342   22088 factory.go:144] device added: [pciAddr: 0000:00:0b.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945345   22088 factory.go:144] device added: [pciAddr: 0000:00:0c.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945348   22088 factory.go:144] device added: [pciAddr: 0000:00:0d.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945351   22088 factory.go:144] device added: [pciAddr: 0000:00:0e.0, vendor: 8086, device: 10ed, driver: ixgbevf]
I1210 23:31:38.945365   22088 manager.go:125] New resource server is created for intel_sriov_hostdevice ResourcePool

[cluster-user@master1vm ~]$ kubectl get node worker1vm.novalocal -o json | jq '.status.allocatable'
{
  "cpu": "16",
  "ephemeral-storage": "19316953466",
  "hugepages-1Gi": "0",
  "hugepages-2Mi": "0",
  "intel.com/intel_sriov_dpdk": "0",
  "intel.com/intel_sriov_hostdevice": "7",
  "intel.com/intel_sriov_netdevice": "0",
  "intel.com/mlnx_sriov_rdma": "0",
  "memory": "32676188Ki",
  "pods": "110"
}

CRD config file
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: sriov-net1
  annotations:
    k8s.v1.cni.cncf.io/resourceName: intel.com/intel_sriov_hostdevice
spec:
  config: '{
  "type": "host-device",
  "cniVersion": "0.3.1",
  "name": "host-device-network",
  "ipam": {
    "type": "host-local",
    "subnet": "10.56.217.0/24",
    "routes": [{
      "dst": "0.0.0.0/0"
    }],
    "gateway": "10.56.217.1"
  }
}'

If i configure the device name as part of CRD configuration, pod able to attach additional network interface.

 config: '{
  "type": "host-device",
  "cniVersion": "0.3.1",
  "name": "host-device-network",
 ** "device": "eth4",**

Pod config:

[cluster-user@master1vm sriov-multus]$ cat pod-tc1.yaml
apiVersion: v1
kind: Pod
metadata:
  name: testpod1
  annotations:
    k8s.v1.cni.cncf.io/networks: sriov-net1
spec:
  containers:
    image: master1vm.novalocal:5000/centos/tools:latest
    imagePullPolicy: IfNotPresent
    command: [ "/bin/bash", "-c", "--" ]
    args: [ "while true; do sleep 300000; done;" ]
    resources:
      requests:
        intel.com/intel_sriov_hostdevice: '1'
      limits:
        intel.com/intel_sriov_hostdevice: '1'

According to this  you need to specify one of device, hwaddr, kernelpath, pciBusID in order to select the correct device. This seems to be reflected in the Multus logs posted above. Once your config - from the network CRD - is passed from multus into the host-device binary it fails with an error and Multus isn't able to provision the network.

@meganathanraja if you have Multus logs that would be helpful.
@zshi-redhat I know you've worked on the host-device cni to enable the "pciBusID" support. Do you have any comment what could be the issue?

@meganathanraja if you have Multus logs that would be helpful.
@zshi-redhat I know you've worked on the host-device cni to enable the "pciBusID" support. Do you have any comment what could be the issue?

Hi @ahalim-intel and @meganathanraja, yes, it looks like multus-v3.2 doesn't contain the patch for pciBusID, please use v3.3 or above version.
git describe --contains "91d9964d0730f60e6dfd82dfcad59aaed635f2a8"   <- the pciBusID commit.

Thanks all for looking into it.
With the "pciBusID" commit, the Multus able to allocate the device from the resource pool and passes it down to host-device CNI plugin.

Other problem could be (just figured this out after several hours), is that the version of host-device could be to old.
At least 0.8.1 is required.

authors: ahalim-intel dromie killianmuldoon meganathanraja zshi-redhat


text:
Return reconcile error if node state is not updated

NetFilter selector depends on PCI address of NICs from the node state. After PR #487 is merged we need to check if node state is updated or return an reconcile error to render device plugin config faster.

@zeeke PTAL


text:
Skip Static test

In order to run upstream tests in a container with make test we need to be able to skip the static check

What wrong with staticcheck when run in a container?

What wrong with staticcheck when run in a container?

If we want to call make test in a container running in a cluster we cannot assume that static-check will be installed, and you cant run the go install command in -vendor mode
This is currently an issue that we are hitting in our (RedHat) downstream testing

What wrong with staticcheck when run in a container?

I think Ben's description is incomplete, I think he needs a make target where he can skip this because he's trying to test it a disconnected environment where he can't pull that gomodule, so he needs a target where he can skip it

Pull Request Test Coverage Report for Build 12037445892
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.639%

Totals

Change from base Build 11912515116:
0.0%

Covered Lines:
1971

Relevant Lines:
5101

💛  - Coveralls

Thank you!

authors: bpickard22 coveralls dougbtv manuelbuil


text:
multi-cluster e2e tests in GHA

What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

I branched off of #50 for this PR. I am going to recreate it to avoid having to work through merge conflicts again.


text:
Add categories bindings

Bindings for Get a Category, Get a list of Categories, and Get a Category's Playlists.
Ping @kaaes.
:snowman:

@kaees: Good catch on <String, Object>, amended.

:+1:

authors: kaaes thelinmichael

repo: kaaes/spotify-web-api-android


text:
Color prints

Want

https://clig.dev/
https://github.com/fatih/color

repo: kachick/selfup


text:
[Question] Z axis co ordinates facing wrong way?

It seems on the Nano ELS the Z axis moves towards the chuck in the positive direction, same for the generated lathe code.
But as far as im aware the Z axis positive should always be facing the tailstock:

This issue was highlighted when I started trying to generate gcode with fusion 360.

@Festivejelly there are different approaches here but we're stuck with the one we have for NanoEls - it's too late to change.
Lathecode isn't meant to be used with GCode coming from other places. If you want to modify H4 GCode sender https://github.com/kachurovskiy/nanoels/blob/main/h4/sender.html to be able to post-process inserted GCode e.g. invert one or both axes before sending - it could be one of the solutions. Or maybe https://festivejelly.github.io/LatheGcodeVisualiser/ would be the place to do it.
Thanks!

authors: Festivejelly kachurovskiy

repo: kachurovskiy/lathecode


text:
ReadTheDocs - Broken Link to “Time Formats” docs

In the ReadTheDocs:
The parse-time documentations references the docs for accepted time formats. But the link used,
https://pact-language.readthedocs.io/en/latest/pact-functions.html#time-formats, is broken.
Correct link is: https://pact-language.readthedocs.io/en/latest/pact-reference.html#time-formats

Also, the time type is not mentioned as a primitive here:
https://pact-language.readthedocs.io/en/latest/pact-reference.html#data-types

authors: LindaOrtega mightybyte

repo: kadena-io/pact


text:
getQueryParam returns undefined

I am using this method to get the value of a query parameter:
FlowRouter.getQueryParam("s")
For a url such as http://someurl.com/app?s=123, the above code returns '123'. However, if the url is http://someurl.com/app?s=123#someid the above code returns 'undefined'.
The url change is instigated by clicking a bootstrap tab. This is importnat to mentino because if I simply type the full url in the browser and hit enter the getQueryParam() function returns the correct value.
How to I get the value of s in these circumstances?
(Using Flowrouter 2.11.0, Meteor 1.3)

This is more related clicking a disabled bootstrap tab.

repo: kadirahq/flow-router


text:
Hot reloading causing Chrome debugger pause?

This is getting annoying and I'm not sure if it's Webpack or what.

Hm. Seems it was Chrome's dev tools.

repo: kadirahq/react-storybook


text:
Make MPU part size configurable

Would it be possible to make the MPU part size configurable? Currently it seems to be set hard-coded at exactly 5GB in multiple places in the code. Our S3 software seems to be having some issues having this exactly on the spec limit.

What S3 software are you using? rename is currently using 5GB parts but it really should use a more optimal part size for concurrency. I would rather not have a fixed MPU part size in general.

That would be even better indeed :)
We are using Cloudian S3, turns out the default max MPU part is 5GB there instead of the 5GiB limit at AWS. I was indeed running into very strange OS errors on rename which seem to be caused by this difference.

is this some setting you can change on the cloudian side?

Yeah turns out it's configurable so we will change it there 👍
Would still be nice to have some optimisation / configuration for this in here as well. Anyway, thanks for the nice software and this feature request can be closed if you want.

agreed that Cloudian's max MPU size should be the same as AWS S3 and that goofys shouldn't use 5GB as part size unless it's necessary. Will leave this open until the latter is fixed.

It seems that for new puts, the partSize being used varies from 25MB => 125MB (it scales up based on how many parts have been uploaded so far), seen here: https://github.com/kahing/goofys/blob/master/internal/handles.go#L495-L503
However, having a partsize of 125MB (max) means that the largest file which can be put is ~1.25TB , due to S3 (and goofys') multipart limit of 10,000 parts.
Being able to configure a larger partSize when you know that the files will be >1TB would be a use case. I know of some backup/archive applications which write extremely large files.

Definitely true about the 1TB or so limit and that some backup applications use extremely large archives (although the ones I've interacted with ex BackupExec, Netbackup, etc, all have configurable limits). Do you or do you know anyone who's using goofys which applications that require > 1TB files?

Another one is that some non-Amazon S3 hosts have different part count limites (1000 in the case of mine). Meaning that in practice I can't store files with size larger than 5GB, which is definitely not a lot

Which s3 is that? Is it possible to identify it through headers?

In this case, it is Scaleway (cf https://www.scaleway.com/en/docs/object-storage-feature/#-Object-Storage-Limitation )
Not sure about headers, but maybe the "max MPU count" could be parameterizable and the size adjusted if the object will take more parts than it?

I think something like a /etc/goofys.conf (and a $HOME-stored per-user one) that supports passing alternate S3 endpoints, cache settings etc would make it overall simpler, because otherwise we'll end with very complex fstab configurations probably

authors: Tristan971 andypern kahing thoutenbos

repo: kahing/goofys


text:
Memory Leak big time...

Using goofys version 0.19.0 on Ubuntu 16.04.
The last couple of weeks (installed goofys two weeks ago) my system has been getting bogged down very quickly. Looked at system monitor today and saw goofys had eaten up 16GB ram and was 5GB into swap. Other than having two S3 buckets mounted I wasn't actually using the buckets at all. I had just started up my system and was about 1 hour into work when my computer started locking up again. Had to kill goofys process to avoid hard shutdown as system was unresponsive.

Goofys doesn't do anything on idle, are you sure you don't have other background processes doing things on those mountpoints? Happy to look into this more but I need more info about what other processes are doing

The two mounts were in /etc/fstab. The mounts were 100% idle. Nothing going in or out or listing, etc. I was not using them in any way other than just having booted up my system, which would have invoked /etc/fstab. What's interesting is that a couple of times I had to hard crash my system because it had become totally unresponsive and after reboot there was no issue.

Could you use --debug_fuse and attach the log here?

authors: Zelfapp kahing


text:
Storage class dependency of object size

https://github.com/kahing/goofys/blob/master/internal/backend_s3.go
In CopyBlob and in PutBlob there are conditions for storage class of objects less than 128*1024 or more.

Could you please explain the reason of that?
Is it save to reduce it to 128 bytes or less?

IIUC, With STANDARD_IA, files smaller than 128KB will be charged as if they are 128KB.
See https://github.com/kahing/goofys/pull/255

Looks like it's AWS specific.
Thanks!

authors: dotslash ssvinarev


text:
Proposal: A super efficient airdrop tool on Kaia

Description

A tool to airdrop KAIA, ERC20 tokens and NFTs. The DApp will have an easy to use frontend.

Bounty track

Contribute a free to use DApp onto mainnet

Migrated from old issue:

https://github.com/klaytn/klaytn-dapp-toolkit/issues/19

https://gaslite-ui.vercel.app/
Deployed address on Baobab: https://baobab.klaytnfinder.io/account/0x61684fc62b6a0f1273f69d9fca0e264001a61db6
Deployed address on Cypress: https://klaytnfinder.io/account/0x53a7a12b0a6da201addfe6c3cdcd75df04bba640
UI repo: https://github.com/haxxsniper/gaslite-ui
Contracts repo: https://github.com/haxxsniper/gaslite-drop-contracts
Will be making updates very soon

@zxstim just made a massive UI overhaul for the airdrop tool for all the functionalities
https://gaslite-ui.vercel.app/
UI repo: https://github.com/haxxsniper/gaslite-ui
Contracts repo: https://github.com/haxxsniper/gaslite-drop-contracts

definitely looking nicer than before. Let me try and revert.

Works super well. def a great contribution for people to do airdrop campaigns on kaia.

Closed the issue now with the recent PR #21

authors: haxxsniper zxstim

repo: kaiachain/kaia-dapp-mono


text:
Use a pure golang pcr extend

Instead of using systemd-pcrphase/pcrextend

did you tried if they are compatible? e.g. are they returning the same measurements?
otherwise this should be marked for a breaking change or offer the native implementation under a switch

also I wonder if we can re-use pcrlock as well, so we don't need to depend on a specific systemd version to bind to lower PCR banks

yep, upgrade went fine as well, partitions locked with systemd-pcrextend were unlocked with the golang reimplementation

@mudler do you want to keep this under a feature flag? or can we merge it as is?

no need to put a feature flag if we are sure it does not break systemd-> golang. Thanks for double-checking!

authors: Itxaka mudler

repo: kairos-io/immucore


text:
:warning: add tumbleweed flavor

What this PR does / why we need it:

Adds new opensuse-tumbleweed and opensuse-tumbleweed-arm-rpi flavors
Renames opensuse to opensuse-leap
Adapt earthfile to new names
Adapt CI to new names

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #65

If merged, this requires changing the required tests from opensuse to opensuse-leap

Codecov Report

Merging #710 (b4205b6) into master (d8c0626) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head b4205b6 differs from pull request most recent head ee136b7. Consider uploading reports for the commit ee136b7 to get more accurate results

@@           Coverage Diff           @@
##           master     #710   +/-   ##
=======================================
  Coverage   19.94%   19.94%
=======================================
  Files          18       18
  Lines        1419     1419
=======================================
  Hits          283      283
  Misses       1088     1088
  Partials       48       48

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Looks good. just as a reminder, we have to create image repos too

I have no perms in the quay org so.... :D

updated docs to move references to core-opensuse to core-opensuse-leap and added core-opensuse-tumbleweed to version matrix

Marking with :warning:, it's a major change as needs in the release note a special mention to redirect opensuse users to opensuse-leap

core-opensuse artifacts copied into core-opensuse-leap artifacts

ok this is good for now, once this is merged a new tumbleweed image will be pushed and then I can retest https://github.com/kairos-io/provider-kairos/pull/193

Omg, can't we set a mirror for the downloads? Terrible failures all the time due to download issues with suse repos

yeap, we need to optimize some targets, definitely there is room for improvement #265

unfortunately the job upgrade-latest-with-cli-test (opensuse-leap) wont pass until we release a new version as that uses the latest release but tries to find the iso by the new name. Im wary of changing that and having to change that back again.
cc @kairos-io/maintainers thougths? Should I change that back to opensuse and then do another PR to change it to opensuse-leap once we release 1.5.0?

authors: Itxaka codecov-commenter mudler

repo: kairos-io/kairos


text:
[BUG] SharedBaseline on_dim default value should be -1

Describe the bug
I think in the SharedBaseline, on_dim here default value should be -1
If not, it raises 👇

To Reproduce
Simply change the baseline and run
Checklist

[x] I have checked that there is no similar issue in the repo (required)
[x] I have provided a minimal working example to reproduce the bug (required)

How are you changing the baseline?
If you use SharedBaseline, you should also use some inference techniques (e.g. multistarts for POMO or augmentation for SymNCO), so if you just use the default model with baseline="shared", it will not work. This is why the reward is always converted to [batch, num_pomo/num_aug]

Okay I see. But actually I wanted to use just the mean of reward as a naive baseline.
So in this case, should I implement this locally?

I see! Then feel free to submit a PR ;)


text:
Non-episodic update of Multistep agent

Describe the bug
A clear and concise description of what the bug is.
Samples of Multistep agent has trash value about post-terminal state.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Development Env. (OS, version, libraries):
Please describe current development environment
Additional context
Add any other context about the problem here.

I checked it while looking at the branch being edited, and it seems to calculate without any problem for multistep.

The actual n-step reward list contains the rewards of the game reset after the terminal. However, when calculating target_q, the value after the terminal is calculated as 0 by multiplying by done, so it seems okay.

repo: kakaoenterprise/JORLDY


text:
遷移ステップの待ち時間を入れる

[x] 遷移ステップを追加する（options.transitionSec）
[x] 遷移ステップ中にアクションが来ても受け付けないようにする

[x] 都城API
[x] v1 API

[x] nextTurnUnixTimeを削除し、operationSecとtransitionSecを追加する
[x] ドキュメント更新
[x] 遷移ステップ中は状態更新前の状態を返す アクションを受け付けないようにする

遷移ステップの時間について、Procon30,31のルールに記載されていない（遷移ステップから次の遷移ステップの時間は記載されている）ため遷移ステップは0秒（現状維持）にしておきます。

遷移ステップはやはり実装させます。
やることリストは1番上のコメントに書きます。

Fix #196

repo: kakomimasu/server


text:
upstream.Cache.GetNar should return http.Response

TL;DR
Improved NAR download handling by returning the full HTTP response instead of separate content length and body.
What changed?

Modified getNarFromUpstream to return the complete HTTP response instead of splitting content length and body
Removed content length validation in the cache pull process
Updated the response handling to properly clean up resources using deferred functions
Simplified error handling and response processing in upstream cache operations

How to test?

Download a NAR file from an upstream cache
Verify the download completes successfully
Confirm proper cleanup of resources after download
Test error scenarios (not found, unexpected status codes)

Why make this change?
The previous implementation separately handled content length and body, which was unnecessary since this information is already available in the HTTP response. This change simplifies the code, reduces potential errors in content length parsing, and ensures better resource cleanup through proper response handling.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#108
#110  👈 (View in Graphite)
#109
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 13, 3:49 PM EST: A user merged this pull request with Graphite.

repo: kalbasit/ncps


text:
Unable to restore from backups

Upon launching PlayerTrack, it initiated a restore from the DB but I was shown an error when trying to pull my old data
PlayerTrack Migration Error Log
Failed to migrate players.
Failed on: _id = 106985
Key = "XAN'A_THUM_91"
LodestoneId = {"$numberLong":"0"}
LodestoneStatus = 0
LodestoneLastUpdated = {"$numberLong":"0"}
LodestoneFailureCount = 0
Names = ["Xan'a Thum"]
HomeWorlds = [{"Key":{"$numberLong":"91"},"Value":"Balmung"}]
Title = ""
FreeCompany = "Rats"
LastTerritoryType = 130
VisibilityType = 0
OverrideFCNameColor = false
Customize = {"$binary":"BAABZAgEBYANKayXGQEBKYACAYC0NQgADIX//w=="}
CustomizeHistory = null
Created = {"$numberLong":"1696240970218"}
Updated = {"$numberLong":"1696240970218"}
SeenCount = 1
Icon = 0
ListColor = null
NamePlateColor = null
Notes = ""
IsAlertEnabled = false
SendNextAlert = {"$numberLong":"1696255370269"}
CategoryId = 1
Tags = []
Failed to insert batch players.
at PlayerTrack.Migration.LiteDBMigrator.MigratePlayers() in /work/repo/PlayerTrack.Plugin/Migration/LiteDBMigrator.cs:line 955
Migration failed.
Failed to migrate players.
at PlayerTrack.Migration.LiteDBMigrator.MigratePlayers() in /work/repo/PlayerTrack.Plugin/Migration/LiteDBMigrator.cs:line 1015
at PlayerTrack.Migration.LiteDBMigrator.Run() in /work/repo/PlayerTrack.Plugin/Migration/LiteDBMigrator.cs:line 86

Thank you, I have one other report on this. Quick question - what is your db size?

They are 50MB

I compared the samples but I'm not seeing a trend yet. I adjusted the player migration code and added some logging. I've submitted this and should hopefully be merged soon. https://github.com/goatcorp/DalamudPluginsD17/pull/2611
Once this is available, can you try again? I believe the error might still happen but I'm hoping you'll get a more specific error message. There are instructions here to migrate fresh. https://github.com/kalilistic/PlayerTrack/wiki/How-to-restore-V2-Database

The update got approved, should be available now.

I'm not sure how I would go about forcing it to load from a specific backup, I'm not seeing any clear way to allow that

I went ahead and followed the instructions and I got an almost identical error
PlayerTrack Migration Error Log
Failed to migrate players.
Failed on: _id = 106985
Key = "XAN'A_THUM_91"
LodestoneId = {"$numberLong":"0"}
LodestoneStatus = 0
LodestoneLastUpdated = {"$numberLong":"0"}
LodestoneFailureCount = 0
Names = ["Xan'a Thum"]
HomeWorlds = [{"Key":{"$numberLong":"91"},"Value":"Balmung"}]
Title = ""
FreeCompany = "Rats"
LastTerritoryType = 130
VisibilityType = 0
OverrideFCNameColor = false
Customize = {"$binary":"BAABZAgEBYANKayXGQEBKYACAYC0NQgADIX//w=="}
CustomizeHistory = null
Created = {"$numberLong":"1696240970218"}
Updated = {"$numberLong":"1696240970218"}
SeenCount = 1
Icon = 0
ListColor = null
NamePlateColor = null
Notes = ""
IsAlertEnabled = false
SendNextAlert = {"$numberLong":"1696255370269"}
CategoryId = 1
Tags = []
Failed to insert batch player categories.
at PlayerTrack.Migration.LiteDBMigrator.MigratePlayers() in /work/repo/PlayerTrack.Plugin/Migration/LiteDBMigrator.cs:line 977
Migration failed.
Failed to migrate players.
at PlayerTrack.Migration.LiteDBMigrator.MigratePlayers() in /work/repo/PlayerTrack.Plugin/Migration/LiteDBMigrator.cs:line 1023
at PlayerTrack.Migration.LiteDBMigrator.Run() in /work/repo/PlayerTrack.Plugin/Migration/LiteDBMigrator.cs:line 86

Upon a secondary restart, I was successfully able to restore my backup. appreciate the help.

Glad to hear it. Did you see any additional errors in the log itself around that time? The log is %appdata%\XIVLauncher\dalamud.log

Not from what I can see, though the log fille is consistently crashing

Thanks for checking. In case anyone else comes across this, I'm adding an update to allow it to fail up to 10 individual players before it marks the migration as failed. The players that do fail will show up as warnings in the migration log.

authors: OmegaJackie kalilistic

repo: kalilistic/PlayerTrack


text:
remove the start offset and local start offset check to pass the tests

All the failed tests failed at the point when verifying start offset/local start offset: https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-14347/13/#showFailuresLink . Let's remove these check for now and add them later after I found out why they are flaky.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Confirmed all tests pass in my local env.

repo: kamalcph/kafka


text:
releaseビルド条件を見直す

ちょっと遅くない？あと--releaseだった気がする

やっぱGUIの問題だった

repo: kamiyaowl/rust-nes-emulator


text:
Support Markdown

Information texts should be in Markdown format to enable easy use of translation tools

Perhaps this is something that could be used?

Looks perfect!!

This app seems to use Expo + that library:
https://github.com/wuiyang/job-search-engine
Might be a good inspiration.

authors: EMattfolk robert-johansson


text:
fix: ChromeCRXビルド

ChromeCRXビルドのことが忘れられてたので

ありがとうございます(((

repo: kaonasi-biwa/Twitter-UI-Customizer


text:
Naming

Hey, thanks for implementing this.
A comment for a potential 0.2: the naming of the derives is a bit weird.
Why not SerializeTuple / DeserializeTuple?

The naming convention is meant to indicate that this derive macro is deriving the Serialize trait, but it is the tuple version of that derive logic. I find SerializeTuple misleading because there is no such trait as SerializeTuple.

That's an interesting and valid point.
It is somewhat misleading. I personally would not have associated the underscore separator with this distinction though.
It's an interesting problem in terms of API design.
Maybe another way to draw a distinction would be to provide attribute macros instead of derives.

authors: dtolnay theduke


text:
Relax requirement for application/rdf+json in queryQuads

Some SPARQL servers like Oxigraph which I am using do not support application/rdf+json in CONSTRUCT/DESCRIBE queries. I currently convert text/turtle to json manually in a custom fetch function.
What would be the best way ti support this?

For these instances it is possible to use Comunica as the query engine: https://ldkit.io/docs/how-to/query-with-comunica
The reason why LDkit does not support text/turtle out of the box is because of performance. In case of JSON response, the browser or JavaScript runner convert the response to JavaScript objects and native types in an efficient way. In comparison with that, parsing of text responses in a format like Turtle is more resource heavy and it is best to be done on server rather then on client.
With that said, it would be beneficial to have text/turtle opt-in support out of the box, after all it is probably the most common RDF serialization there is. It is definitely possible to create an alternative lightweight query engine that would support that format as well.

Would love to see more support, including as well application/ld+json. I am currently using stardog and sadly they don't support rdf+json. Any hope on this?

Some SPARQL servers like Oxigraph which I am using do not support application/rdf+json in CONSTRUCT/DESCRIBE queries. I currently convert text/turtle to json manually in a custom fetch function. What would be the best way ti support this?

Any chance you could share your solution? I need to do the same for my case, already had to modify the fetch function to add authentication.

@ragnorc @arxos-twinu I've added support for text/turtle to the default query engine so most SPARQL endpoints should now work ouf of the box. Available in version 1.1.0.
If there are some other formats that would be convenient to include then please let me know and I will add them.

authors: arxos-twinu karelklima ragnorc

repo: karelklima/ldkit


text:
fix: updated dependencies

This PR updates the Go dependencies and the Docker Go version.

Closes #81

repo: karl-cardenas-coding/go-lambda-cleanup


text:
Grunt karma-browserify

When I run grunt I have this error:
Running "simplemocha:all" (simplemocha) task
1..8
ok 1 Classe:  maFonction Tester maFonction
ok 2 Classe:  maFonction Tester Division par 0
ok 3 Classe:  maFonction Tester should
ok 4 Classe:  maFonction future test # SKIP -
ok 5 Classe:  wait should exist
ok 6 Classe:  wait Test asynchrone
ok 7 Demo test:  Fair un 1er test
ok 8 Demo test:  Fair un 2eme test
tests 7
pass 7
fail 0
Running "karma:unit" (karma) task
21 10 2015 11:17:07.237:WARN [plugin]: Error during loading "karma-browserify" plugin:
Cannot find module './lib/_stream_transform.js'
21 10 2015 11:17:10.231:WARN [preprocess]: Can not load "browserify", it is not registered!
Perhaps you are missing some plugin?
Warning: No provider for "framework:browserify"! (Resolving: framework:browserify) Use --force to continue.
this is my Gruntfile.js :
module.exports = function(grunt) {
	grunt.initConfig({
		simplemocha : {
			options : {
				globals : [ 'expect' ],
				timeout : 3000,
				ignoreLeaks : false,
				ui : 'bdd',
				reporter : 'tap'
			},
			all : {
				src : [ 'test/*Test.js' ]
			}
		},
		karma : {
			unit: {
			    options: {
			    	configFile : 'karma.conf.js'
			    }

			}
		}
	});
	grunt.loadNpmTasks('grunt-simple-mocha');
	grunt.loadNpmTasks('grunt-karma');
	grunt.registerTask('default', [ 'simplemocha', 'karma' ]);
};

Thank you

Have you installed karma-browserify and added it to the devDependencies in package.json?

Yes allredy done ans this is the "karma start" result
21 10 2015 11:28:46.732:INFO [framework.browserify]: bundle built
21 10 2015 11:28:46.740:INFO [karma]: Karma v0.13.11 server started at http://localhost:9876/
21 10 2015 11:28:46.745:INFO [launcher]: Starting browser PhantomJS
21 10 2015 11:28:47.289:INFO [PhantomJS 1.9.8 (Linux 0.0.0)]: Connected on socket 0f3LPIkVmBhzEleeAAAA with id 48327382
PhantomJS 1.9.8 (Linux 0.0.0): Executed 1 of 1 SUCCESS (0.804 secs / 0.007 secs)

so this is all working now?

still not working, the problem is with Grunt because when I run Karma start or Mocha all works good

authors: Dignifiedquire FadelChafai zzo

repo: karma-runner/grunt-karma


text:
Error: Cannot find module 'jasmine-core'

After running
npm install -g karma && npm install karma --save-dev

when I run:
karma start
I get:
Error: Cannot find module 'jasmine-core'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.resolve (internal/module.js:27:19)
    at initJasmine (/Users/alexamil/WebstormProjects/cisco/cdt-now/node_modules/karma-jasmine/lib/index.js:8:42)
    at Array.invoke (/Users/alexamil/WebstormProjects/cisco/cdt-now/node_modules/di/lib/injector.js:75:15)
    at Injector.get (/Users/alexamil/WebstormProjects/cisco/cdt-now/node_modules/di/lib/injector.js:48:43)
    at /Users/alexamil/WebstormProjects/cisco/cdt-now/node_modules/karma/lib/server.js:143:20

nevermind, sorry, I didn't see these instructions in the tutorial:
npm install karma karma-jasmine jasmine-core karma-chrome-launcher --save-dev

repo: karma-runner/karma


text:
Empty section addition

Is your feature request related to a problem? Please describe.
I'd like to have an empty section to add new stuff from zero. It can be disabled by default.
Describe the solution you'd like
With simple code, anybody will be able to use it to create more sections as desired.
Additional context
On my website I was able to "duplicate" buyMeACoffee section to add one linked to my Polywork site, but it's out of my knowledge.

Interesting. What would be the content on this new page?
I am thinking about automating it from the config file, so just want to know. Also would consider whether it's worth it to automate it.
As for now, you can follow these steps to add a new empty page:

Nuxt's routes are based on directory names. So create a new directory in pages and an index.vue file in it.

You can copy paste the contents from any of the existing pages.

Make changes in components/TheNavBar.vue here and here.

I'd to add a page with the tech stack I'm using. You're listing your hardware in uses (which is almost identical to mine lol) and I'd like to add software and maybe my workflows.

Nice. So a new page or may be a section on the same uses page makes sense?
Also what do you mean by workflows?

Maybe mine explanation was poor. I'd like to have an empty page like uses or resume.
About workflows and stack I'd like to share something like this

Interesting. What would be the content on this new page?
I am thinking about automating it from the config file, so just want to know. Also would consider whether it's worth it to automate it.
As for now, you can follow these steps to add a new empty page:

Nuxt's routes are based on directory names. So create a new directory in pages and an index.vue file in it.

You can copy paste the contents from any of the existing pages.

Make changes in components/TheNavBar.vue here and here.

Thanks for this explanation. After getting a lot of "Travoltas" 😅 it's necessary also to add the new section to the karngyan.config.js file.

authors: Klaudioz karngyan


text:
Images are turned

I have autoRotate set to true but when I upload the image through my iphone it comes in turned.

@jsd219 thank you for the feedback and patience. Please see my respons to #36. Hopefully a new and improved exif-lib will fix this.

repo: kartoteket/vue-image-upload-resize


text:
Fixes

preserve original entry order (for easier diffs)
never replace "inproceedings" with an arXiv link (better an obscure conference that's not on DBLP than just arXiv)
fix some crashes

OK looks like I need to update from upstream and then try again

repo: kasnerz/reffix


text:
Allow Associated Objects to extend their Active Record

If we eager load the Associated Object class when calling has_object we can have an extension class method fire that can extend the Active Record class.
class Post::Publisher < ActiveRecord::AssociatedObject
  extension do
    has_many :contracts, dependent: :destroy

    after_create_commit :publish_later_after_signed

    private def publish_later_after_signed
      # An integrating method that operates on `publisher`.
      # A little tough to generate an example since we're now mixing in a `contracts` concept.
      publisher.publish_later if contracts.all?(&:signed?)
    end
  end
end

I'm still not quite sure how I feel about this. I'll write some documentation later, after I've sat with this some more.
@garrettdimon this doesn't quite get us to the automatically scoped validations, but is this closer to what you were talking about with replacing those wrapping ActiveSupport::Concerns ala kaspth/conventional_extensions?
@natematykiewicz is this something that would be useful to you? Does this seem clear enough? Would it break your app if we eager-loaded the Associated Objects (due to autoloading it should be fine)?

@seanpdoyle have you tried using this gem yet? Would this be something you'd be interested in?

I'm not sure if I'd use that feature or not, but it makes sense. Also, I think this feature or not, we should eager load (when eager loading is enabled) AssociatedObject and ActiveJob Performs classes. If they aren't eager loaded in production, we'd end up using more memory than necessary.

Also, I don't think this would cause me any problems. I've assumed they work like models where they're eager loaded in production and lazy loaded in development. If not, I think we should change that.

I think I'd have to tinker with it and see how it feels, but just looking at it, it sure seems like a good approach.

@garrettdimon nice! There's also no rush on this, so take your time. I wonder how we explain it to people, since it could be a bit hidden. I could see an alias_method :has_extending_object, :has_object to help clarify that something happens in the other file. Of course, post.method(:<something>).source_location still points to the right location.

I'm not sure if I'd use that feature or not, but it makes sense. Also, I think this feature or not, we should eager load (when eager loading is enabled) AssociatedObject and ActiveJob Performs classes. If they aren't eager loaded in production, we'd end up using more memory than necessary.

@natematykiewicz we're just leaning on app/models being set up for eager-loading so both Associated Objects and ActiveJob::Performs will be eager-loaded when the app is.

Also, I don't think this would cause me any problems. I've assumed they work like models where they're eager loaded in production and lazy loaded in development. If not, I think we should change that.

Yeah, that's how it works before this PR. However, if we shift to loading the Associated Object when has_object is called, then we can inject extensions into the record class — and obviate some needs for wrapping ActiveSupport::Concerns.
Basically, using the example from the description, before this PR it'd be common to do something like this:
# app/models/post.rb
class Post < ApplicationRecord
  include Published
end

# app/models/post/published.rb
module Post::Published
  extend ActiveSupport::Concern

  included do
    has_many :contracts, dependent: :destroy

    has_object :publisher
    after_create_commit :publish_later_after_signed
  end

  private def publish_later_after_signed
    publisher.publish_later if contracts.all?(&:signed?)
  end
end

So we're splitting the extension/integration into a wrapping Concern, but what if we could bundle that into the Associated Object now that they're a domain concept and we're already using them? It gets tricky though, especially communicating where things come from.

I realized yesterday that I'd probably move the callbacks inside the extension block. I use associated objects with activerecord callbacks a lot. Oftentimes its after_create_commit and then an after_update_commit if saved_change_to some field(s). The after_create_commit doesn't have conditions, the code often looks like:
# model
has_object :foo, after_create_commit: :sync_later
after_update_commit -> { foo.sync_later }, if: :saved_change_to_active?

But with extensions I'd probably just switch that to:
# model
has_object :foo

# associated object
extension do
  after_create_commit -> { foo.sync_later }
  after_update_commit -> { foo.sync_later }, if: :saved_change_to_active?
end

Ship it, Kasper!

@natematykiewicz nice! Sounds good, I think I'll ship this after we get #20 in then, and cut a new release.

@kaspth in your rebase, you lost the eager loading of the associated object class.

authors: garrettdimon kaspth natematykiewicz


text:
agent: Hostname not set for sandbox/VM

root@nitkon:/home/nitesh# bash -x connect_debug.sh
++ sudo docker ps -q --no-trunc
+ id=cbb8ec2e63001340f2aba78a455d1762fdd5f4969f3829a2a857c7200abe23bb
+ console=/var/run/vc/vm/cbb8ec2e63001340f2aba78a455d1762fdd5f4969f3829a2a857c7200abe23bb/console.sock
+ sudo socat stdin,raw,echo=0,escape=0x11 unix-connect:/var/run/vc/vm/cbb8ec2e63001340f2aba78a455d1762fdd5f4969f3829a2a857c7200abe23bb/console.sock

bash-4.4# hostname
(none)
bash-4.4#

As part of CreateSandbox I see the sandbox hostname getting set.
After attaching to the console of the kata VM, I could see the hostname not set.

@nitkon We set the hostname in the UTS namespace that we create for the containers, and not within the VM itself. Thats why you are seeing this behaviour. We just need to make sure the hostname is correct in the namespace for the containers.

Hi @amshinde , my intention is to set hostaname and dns for the guest VM.
Ptal: https://github.com/kata-containers/runtime/pull/1825 and https://github.com/kata-containers/agent/pull/590

authors: amshinde nitkon

repo: kata-containers/agent


text:
vsock - context deadline exceed on create command.

Description of problem
The vsocks job has started to fail randomly when running the docker-stability tests with the next error:
11:10:00 docker: Error response from daemon: OCI runtime create failed: Failed to check if grpc server is working: context deadline exceeded: unknown.

http://jenkins.katacontainers.io/job/kata-containers-tests-fedora-vsocks-PR/1004/console
http://jenkins.katacontainers.io/job/kata-containers-runtime-fedora-vsocks-PR/323/
From the kata-runtime log:
Mar 04 12:23:12 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:12.295360953Z" level=info msg="VM started" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77b209f8
fcddd17e97438b3d1a6a name=kata-runtime pid=32372 sandbox=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a source=virtcontainers subsystem=sandbox
Mar 04 12:23:12 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:12.295732044Z" level=debug msg="No proxy started because of no-proxy implementation" arch=amd64 command=create container=41
32a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime pid=32372 sandbox=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a source=virtcontainers subsystem=kata_agent
Mar 04 12:23:12 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:12.296456793Z" level=info msg="proxy started" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77b20
9f8fcddd17e97438b3d1a6a name=kata-runtime pid=32372 proxy-pid=0 proxy-url="vsock://2202419104:1024" sandbox=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a source=virtcontainers subsystem=kata_a
gent
Mar 04 12:23:12 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:12.296808274Z" level=info msg="New client" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77b209f8
fcddd17e97438b3d1a6a name=kata-runtime pid=32372 source=virtcontainers subsystem=kata_agent url="vsock://2202419104:1024"
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.2979244Z" level=info msg="Stopping netmon" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77b20
9f8fcddd17e97438b3d1a6a name=kata-runtime netmon-pid=32399 netmon-signal=killed pid=32372 source=virtcontainers subsystem=netmon
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.301006349Z" level=info msg="Detaching endpoint" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d
77b209f8fcddd17e97438b3d1a6a endpoint-type=virtual hotunplug=false name=kata-runtime pid=32372 source=virtcontainers subsystem=network
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.324078004Z" level=debug msg="Network removed" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77
b209f8fcddd17e97438b3d1a6a name=kata-runtime pid=32372 source=virtcontainers subsystem=network
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.324286965Z" level=info msg="Network namespace \"/var/run/netns/cni-b0b89686-ad80-d13a-63a4-043a889b757c\" deleted" arch=
amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime pid=32372 source=virtcontainers subsystem=network
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.333972528Z" level=debug msg="Deleting sandbox cgroup" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d
16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime pid=32372 sandbox=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a source=virtcontainers subsystem=sandbox
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.334232954Z" level=debug msg="Deleting no constraints cgroup" arch=amd64 command=create container=4132a20fe71671403cc16d8
de9745d16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime path=/kata pid=32372 sandbox=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a source=virtcontainers subsystem=sandbox
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.363404966Z" level=info msg="cleanup agent" arch=amd64 command=create container=4132a20fe71671403cc16d8de9745d16695d77b20
9f8fcddd17e97438b3d1a6a name=kata-runtime path=/run/kata-containers/shared/sandboxes/4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a pid=32372 source=virtcontainers subsystem=kata_agent
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.36400354Z" level=debug msg="Deleting files" arch=amd64 backend=filesystem command=create container=4132a20fe71671403cc16
d8de9745d16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime path=/var/lib/vc/sbs/4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a pid=32372 source=virtcontainers/store subsystem=store
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.364616227Z" level=debug msg="Deleting files" arch=amd64 backend=filesystem command=create container=4132a20fe71671403cc1
6d8de9745d16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime path=/run/vc/sbs/4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a pid=32372 source=virtcontainers/store subsystem=store
Mar 04 12:23:27 fedora-28-51.vexxhost.local kata-runtime[32372]: time="2019-03-04T12:23:27.365064884Z" level=error msg="Failed to check if grpc server is working: context deadline exceeded" arch=amd64 command=cr
eate container=4132a20fe71671403cc16d8de9745d16695d77b209f8fcddd17e97438b3d1a6a name=kata-runtime pid=32372 source=runtime

I'm wondering what kernel version is being used for these Fedora jobs?

The host kernel - from the logs of one of the vsocks CI runs, you can find the kata-env output, which contains:
[Host]
  Kernel = "4.16.3-301.fc28.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "Fedora"
    Version = "28"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel Xeon E3-12xx v2 (Ivy Bridge, IBRS)"

Yeah, this old kernel should work well for vsocks. I actually tested locally using that kernel version and cannot reproduce the issue.
I also changed the vsock job on the test repo to use CentOS on azure (from using Fedora on vexxhost) and last 5 jobs pass. Seems like it is stable now.
http://jenkins.katacontainers.io/job/kata-containers-tests-fedora-vsocks-PR/
But maybe we are still hiding a race condition that happens on some slow machines.

Could you check if your kernel has the two commits:

commit 834e772c8db0c6a275d75315d90aba4ebbb1e249( vhost/vsock: fix use-after-free in network stack callers)
commit 7fbe078c37aba3088359c9256c1a1d0c3e39ee81 (vhost/vsock: fix vhost vsock cid hashing inconsistent)

Any update on this folks?

I don't think the host kernel has those commits as it is using the default kernel of the Fedora cloud image. BTW, these machines are running on vexxhost, so I don't have access to debug further.
The fedora image that we have on Azure has a newer kernel 4.19 and I also tried to update it to 4.20 (latest available in the fedora repos), but that has the same problem as #1203.

Hi~
I have already bumped into this issue on my local machine.
root@entos-thunderx2-desktop:~/go/src/vsock_debug# uname -a
Linux entos-thunderx2-desktop 4.19.12+ #1 SMP Wed Dec 26 15:18:01 CST 2018 aarch64 aarch64 aarch64 GNU/Linux
root@entos-thunderx2-desktop:~/go/src/vsock_debug# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"

I have used test application created by @pmorjan to see if it's the same bug. It is!!! 😭
root@entos-thunderx2-desktop:~/go/src/vsock_debug# ./vsock_debug 0xfff000
cid          : 0xfff000
message      : connection timed out
errno        : 0x6e (110)

And I also logged into ARM CI to see if it shares this problem, sadly, it also is!!! 😭
The kernel on ARM CI has already been updated into 4.20.x for nvdimm support a few time ago.
root@testing-1:~# uname -a
Linux testing-1 4.20.0-rc4 #1 SMP Wed Nov 28 14:44:27 CST 2018 aarch64 aarch64 aarch64 GNU/Linux

root@testing-1:~/go/src/vsock-debug# ./vsock-debug 0xfff000
cid          : 0xfff000
message      : connection timed out
errno        : 0x6e (110)

I couldn't go back to use old kernels, and the latest kernel for fully memory hotplug and nvdimm support should be 4.20+, so the only option for me, fwit, is updating host kernel into 5.0-rc3+, to see if it gets solved. I will try my local machine firstly and then ARM CI. ;)

Hi~ @chavafg @grahamwhaley @jodh-intel @egernst @bergwolf
I have updated my local machine to the latest stable kernel version v5.0.x.
root@entos-thunderx2-desktop:~# uname -a
Linux entos-thunderx2-desktop 5.0.7 #1 SMP Mon Apr 8 11:13:26 CST 2019 aarch64 aarch64 aarch64 GNU/Linux
root@entos-thunderx2-desktop:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"

and the vsock finally works well. 🎉🎊
root@entos-thunderx2-desktop:~# docker run -dt --runtime kata-runtime ubuntu
585a2cc159b55ae7ec08511c8ae7c619acc3be4d8b88cd9a3a63afbea67710f4
root@entos-thunderx2-desktop:~# ps -aux | grep "kata-shim"
root     109157  0.0  0.0 758836 16180 pts/2    Ssl+ 15:02   0:00 /snap/kata-containers/120/usr/libexec/kata-containers/kata-shim -agent vsock://3502968924:1024 -container 585a2cc159b55ae7ec08511c8ae7c619acc3be4d8b88cd9a3a63afbea67710f4 -exec-id 585a2cc159b55ae7ec08511c8ae7c619acc3be4d8b88cd9a3a63afbea67710f4 -terminal -log debug

I will find time to update ARM CI to v5.0. ;)

@Pennyzct - nice - good luck!

authors: Pennyzct bergwolf chavafg egernst grahamwhaley jodh-intel

repo: kata-containers/runtime