Stack overflow occurs probabilistically when calling function pack_ogg in api.py with converting a large audio data

When I specify the mode for ogg streaming inference, if the synthesized audio data is too large, a stack overflow error will be raised probabilistically while converting numpy vector to the ogg audio file.
Next, I'll show you how to reproduce the problem.
The script command to start API is as follows:
python.exe api.py -sm n -d cuda -p 11014 -a <IP_ADDRESS> -mt ogg

The HTTP request is as follows:
{
    "text": "二次元，原指“二维世界”，包含长度和宽度的二维空间。后来成为了ACGN亚文化圈专门用语，特意用“二次元”来指代。由二维图像的动画、漫画、游戏等作品构成，简单来讲就是在纸面或屏幕等平面上所呈现的动画、游戏等平面视觉作品，里面的角色都是图像形式，区别于真人饰演的影视剧，因此被称为“纸片人”。通过这些载体创造的虚拟世界被动漫爱好者称为“二次元世界”，简称“二次元”。在某种意义上讲，二次元还意指喜爱它的人就像生活在一个平面世界中一样。“二次元”是一个平面媒体所表达的“异次元”，因其二维空间本质被称为“二次元”。“二次元”词义逐渐脱离原本的空间属性，并派生出与主流文化相对独立的次文化体系，也就是“二次元”文化。",
    "text_language": "zh",
    "refer_wav_path": "D:/AkagawaTsurunaki/Dataset/Audio/Prompts/[zh]喜欢游戏的人和擅长游戏的人有很多不一样的地方，老师属于哪一种呢？.wav",
    "prompt_text": "喜欢游戏的人和擅长游戏的人有很多不一样的地方，老师属于哪一种呢？",
    "prompt_language": "zh"
}

The log is as follows:
D:\AkagawaTsurunaki\WorkSpace\PycharmProjects\RVC-Boss\GPT-SoVITS\api.py:648: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
  logger.warn(f"未指定SoVITS模型路径, fallback后当前值: {sovits_path}")
WARNING:  未指定SoVITS模型路径, fallback后当前值: GPT_SoVITS/pretrained_models/s2G488k.pth
D:\AkagawaTsurunaki\WorkSpace\PycharmProjects\RVC-Boss\GPT-SoVITS\api.py:651: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
  logger.warn(f"未指定GPT模型路径, fallback后当前值: {gpt_path}")
WARNING:  未指定GPT模型路径, fallback后当前值: GPT_SoVITS/pretrained_models/s1bert25hz-2kh-longer-epoch=68e-step=50232.ckpt
INFO:     未指定默认参考音频
INFO:     半精: True
INFO:     流式返回已开启
INFO:     编码格式: ogg
...
DEBUG:jieba_fast:Loading model cost 0.444 seconds.
DEBUG:jieba_fast:Prefix dict has been built succesfully.
  0%|          | 0/1500 [00:00<?, ?it/s]D:\AkagawaTsurunaki\Models\GPT-SoVITS\GPT_SoVITS\AR\modules\patched_mha_with_cache.py:452: UserWarning: 1Torch was not compiled with flash attention. (Triggered internally at C:\actions-runner\_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\transformers\cuda\sdp_utils.cpp:263.)
  attn_output = scaled_dot_product_attention(
 81%|████████  | 1215/1500 [00:15<00:03, 76.61it/s]
T2S Decoding EOS [198 -> 1414]
D:\AkagawaTsurunaki\ProgramFiles\Anaconda\envs\GPTSoVits\lib\site-packages\torch\functional.py:660: UserWarning: stft with return_complex=False is deprecated. In a future pytorch release, stft will return complex tensors for all inputs, and return_complex=False will raise an error.
Note: you can still call torch.view_as_real on the complex output to recover the old return format. (Triggered internally at C:\actions-runner\_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\SpectralOps.cpp:879.)
  return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]

Process finished with exit code -1073741571 (0xC00000FD)

You can see that the program exits abnormally, and this exit code (-1073741571) indicates a stack overflow.
My solution is referred to Stack Overflow while writing OGG · Issue #396 · bastibe/python-soundfile (github.com).
This is the original code of pack_ogg in api.py:
def pack_ogg(audio_bytes, data, rate):
    with sf.SoundFile(audio_bytes, mode='w', samplerate=rate, channels=1, format='ogg') as audio_file:
        audio_file.write(data)

    return audio_bytes

and I changed it to:
def pack_ogg(audio_bytes, data, rate):
    # Author: AkagawaTsurunaki
    # Issue:
    #   Stack overflow probabilistically occurs
    #   when the function `sf_writef_short` of `libsndfile_64bit.dll` is called
    #   using the Python library `soundfile`
    # Note:
    #   This is an issue related to `libsndfile`, not this project itself.
    #   It happens when you generate a large audio tensor (about 499804 frames in my PC)
    #   and try to convert it to an ogg file.
    # Related:
    #   https://github.com/RVC-Boss/GPT-SoVITS/issues/1199
    #   https://github.com/libsndfile/libsndfile/issues/1023
    #   https://github.com/bastibe/python-soundfile/issues/396
    # Suggestion:
    #   Or split the whole audio data into smaller audio segment to avoid stack overflow?

    def handle_pack_ogg():
        with sf.SoundFile(audio_bytes, mode='w', samplerate=rate, channels=1, format='ogg') as audio_file:
            audio_file.write(data)

    import threading
    # See: https://docs.python.org/3/library/threading.html
    # The stack size of this thread is at least 32768
    # If stack overflow error still occurs, just modify the `stack_size`.
    # stack_size = n * 4096, where n should be a positive integer.
    # Here we chose n = 4096.
    stack_size = 4096 * 4096
    try:
        threading.stack_size(stack_size)
        pack_ogg_thread = threading.Thread(target=handle_pack_ogg)
        pack_ogg_thread.start()
        pack_ogg_thread.join()
    except RuntimeError as e:
        # If changing the thread stack size is unsupported, a RuntimeError is raised.
        print("RuntimeError: {}".format(e))
        print("Changing the thread stack size is unsupported.")
    except ValueError as e:
        # If the specified stack size is invalid, a ValueError is raised and the stack size is unmodified.
        print("ValueError: {}".format(e))
        print("The specified stack size is invalid.")

    return audio_bytes

This way, converting larger audio data to OGG format should not cause stack overflow issues.
The is because soundfile has a stack overflow error when calling libsndfile_64bit.dll. As far as I know, adjusting the stack size is a relatively simple and feasible solution at present.
I have reported this issue to libsndfile and waiting for it to be fixed.
For more details, please see:
Stack overflow probabilistically occurs when the function sf_writef_short of libsndfile_64bit.dll is called using the Python library soundfile · Issue #1023 · libsndfile/libsndfile (github.com)

I submitted a PR, I tested the largest audio the model GPT-SoVITS was capable of synthesizing and converted it to OGG format, and the program worked fine.


Add more information for core:require in fragment

Fixes https://github.com/SAP/openui5-docs/issues/8

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Done in CMS. Should be visible in github tomorrow.


Find a way to remove the need for the "tabs" permission

Users who have updated to 0.2.3 will have seen a scary warning that SpaceSuit needs access to their browsing history. SpaceSuit doesn't want, need, or attempt to access the user's browsing history, but we ended up adding the "tabs" permission because:

Switching to the new colour icon made it clear that the old icon was greyed out
To make the icon not greyed out, we had to add an "action" for clicking the icon
The action we chose was to display the options screen in a popup
The options screen has a link to the help page
Links don't work in popups - if you want to link to a page, you have to use the "tabs" API to open a new tab
Granting an app access to the tabs API grants it access to the user's browsing history

I can see a few ways forward:

Accept that the icon is greyed out
Reassure users that we will never attempt to view their browser history
Remove the link to the help page from the options popup
Make the help content available in the popup
Make the action "open the options page" (if this can be done without the "tabs" API).

It turns out that creating a tab doesn't need the "tabs" permission, so I'll get a version published without that permission.


Spacing between cells

I need to remove the spacing between the calendar days so they they look like below. Is that possible? A manual change would be fine too.

calendar.adjustsBoundingRectWhenChangingMonths = true

just make one change in FSCalenderCell M file.
check for _shapeLayer.frame then replace those lines with _shapeLayer.frame = self.bounds;


prometheus: 2.40.3 -> 2.41.0

Description of changes
prometheus 2.40.x is out of support since 12/2022 therefore the update to 2.41.0
between those two releases security critical patches have been added both to prometheus codebase and upstream dependecies, see:

2.40.6 / 2022-12-09 https://github.com/prometheus/prometheus/pull/11690 [SECURITY] Security upgrade from go and upstream dependencies that include security fixes to the net/http and os packages. #11691

2.40.4 / 2022-11-29 https://github.com/advisories/GHSA-7rg2-cxvp-9p7p https://github.com/advisories/GHSA-4v48-4q5m-8vx4 [SECURITY] Fix basic authentication bypass vulnerability (CVE-2022-46146) GHSA-4v48-4q5m-8vx4

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 211569 run on x86_64-linux 1

1 package built:

prometheus

Result of nixpkgs-review pr 211569 run on x86_64-linux 1

1 test built:

nixosTests.prometheus


fix: add sample output for CLI interactive setup.

Closes #3638
Add sample output to CLI setup instructions.

[ ] Signed the InfluxData CLA
(if necessary)
[ ] Rebased/mergeable

@jstirnaman, we may want to add Stacie on review

Thanks for the reminder!


Publish to npm

Hello!
Can you please publish this package on npm? Thanks!

Wonderful idea, I will do so!

Done! https://www.npmjs.com/package/pixi-extra-filters


Sync with master

Coverage increased (+0.2%) to 51.891% when pulling 345fa93997a29e35ed4fbecaf9579bff3cbb0a43 on master into 6d9c418aa241781270d176663bf0746a94ff3aef on twins-ng.


Chat/chat screen state container

Purpose

State Container Scaffold
Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Pull Request Checklist

[ ] Public API changes
[ ] Verified for cross-platform
[ ] Synced with iOS, Web team
[ ] Internal review completed
[ ] UI Changes

[ ] Screen captures included
[ ] Tested for Light/Dark mode
[ ] Tested for screen rotation
[ ] Tested on Tablet and small screen device (5")
[ ] Include localization changes

[ ] Tests

[ ] Memory leak analysis performed
[ ] Tested on API 21, 26 and latest
[ ] Tested for background mode
[ ] Unit Tests Included
[ ] UI Automated Tests Included

How to Test

Open...
Click on...

What to Check
Verify that the following are valid

...

Other Information

@ahammer lets discuss more about this PR in call. I have this working in my repo for send messages.


Datatabless error

Class 'Yajra\Datatables\Services\DataTable' not found for Laravel 5.4
More info here: https://yajrabox.com/docs/laravel-datatables/7.0/upgrade

I'm on "infyomlabs/laravel-generator": "5.4.x-dev", using "yajra/laravel-datatables-oracle": "^7.2" and "yajra/laravel-datatables-buttons": "^1.1" and everything is ok.
Did you registered the Datatables related Service Providers on config/app.php file?

@AlexKR @cenoura right now it's only supporting datatables version 6.0 not 7.0

Hi, is there a fix? Should I remove Datatables 7 and replace it with v6?

@dhcmega yes, it will work fine with 6.0..

it worked, thanks.

Will be creating new feature request for version 7.0 support.


github star button color fix

I don't know, if it was for me only but,
while on dark mode github star button was still looking white, so I made some changes to fix that.
checked on my device, works on both dark and light mode
before  changes ::

after changes ::

Nice!
Thanks @therealrinku !


Add method to load EMRI waveform

using this https://github.com/BlackHolePerturbationToolkit/FastEMRIWaveforms/blob/master/examples/FastEMRIWaveforms_tutorial.ipynb

There is a method to load emri waveforms generated by Maarten. We can add one for loading FEW when required. Closing for now.


Revert "controller classes further developed"

Reverts relectric-car-team/systems#6

This would rever the commits you already made in #6 so I'm going to close it


Convert left rule to padding rule to fix inset issue

Bug/issue #, if applicable: 89775264
Summary
For some reason, there is a CSS left property assignment that is inconsistently being evaluated as expected on devices with left inset values.
I've simply updated this to be a padding rule, which seems to resolve this issue and the spacing works consistently now.
Testing
Steps:

Open a page with the sidebar on a device that has a left inset when in landscape orientation (like the iPhone 13 Pro as an example).
Open the mobile sidebar and verify that the close icon is not obscured by the device.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] ~Added tests~~
[X] Ran npm test, and it succeeded
[X] Updated documentation if necessary

@swift-ci test


Builder for RecordedResponse

Newbie here. I've started digging in tests and noticed following RecordedResponse constructor calls:
new RecordedResponse(networkResponse.request(), networkResponse, null, null, null);

new RecordedResponse(priorResponse.request(), priorResponse, null, null, null);

etc.
I want to implement builder:
new RecordedResponse.Builder().request(priorResponse.request()).response(priorResponse)
        .build();

Does it make sense?

Neat idea.
But it's support code for tests. Any investment in making the API nice might not be worthwhile, particularly since this sort of thing is subject to frequent & aggressive refactoring.


3d models

Is it possible to use component straight for 3d model (gltf etc.)?
I try it, but cursor not find model at all. I made fast solution for that by make 3d model child of transparent a-box. Not so charming, but works 😄

It can work with 3D models, as long as the collision detection component can handle your model. If you are using gaze cursor or laser pointer mode, that would be the A-Frame raycaster or with touch mode that would be sphere-collider

Thx, that works!

By the way I really like that component 😃


[Bug]: latest version available on windows is 0.2.0

What happened?
I have created a new environment with the command conda create -n xcdat -c conda-forge xcdat and the installed xcdat version is xcdat              conda-forge/noarch::xcdat-0.2.0-pyhd8ed1ab_0.
If I ask anaconda to install the 0.3.1, it says that esmpy is not available.
- nothing provides esmpy needed by xcdat-0.3.1-pyhd8ed1ab_0

What did you expect to happen?
No response
Minimal Complete Verifiable Example
No response
Relevant log output
No response
Anything else we need to know?
No response
Environment
.

@matteodefelice – thanks for reporting this. I'm kind of confused – I don't have xesmpy in my conda list for xcdat 0.3.1 (though this is on Linux). Maybe this is a xesmf-windows-dependency?
@durack1 hit what seems like a related issue on the new ARM macbooks; xesmf doesn't yet have a build, so @durack1 has a PR that makes xesmf an optional import in xcdat. I'm guessing this will be merged and incorporated into 0.3.2 in the next few weeks.

@pochedls correct, esmpy (not xesmpy) is only available for linux-64 and osx-64 currently, see here.
It is likely that osx-arm64 support will appear in an upcoming esmpy=8.3/.4 release. I do not believe that windows support is currently planned, however an issue exists - @matteodefelice you may like to comment on that open issue to add support for windows

@matteodefelice, another option is to use the Windows native subsystem for linux and then use the linux-64 binaries in their native environment on windows.
@tomvothecoder this approach might be a useful thing to document in readthedocs

@durack1, it looks like Matteo is using WSL2 as an alternative (https://github.com/xCDAT/xcdat/issues/341).
That's a good workaround for Window users, so it will be included in #334.

I'll close this issue since #315 covers this too.


Different length of the error source in 1.11 and 1.12 versions

I already wrote that when switching from version 1.11.17 to version 1.12.0, in my project some tests stopped passing:
Expected: ···riable2 - variable3;
Actual:   ···riable2 - variable3;\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0···

If you run the following JS code:
var $variable1 = 611;
var _variable2 = 711;
var variable3 = 678;

$variable1 + -variable2 - variable3;

Then an error will occur and this is normal behavior. The main problem that caused by switching to new version of the ChakraCore library is the following: number of characters in value from the source property of error meta data has increased significantly. In this case, number of characters increased from 36 to 106.
To reproduce this error, I wrote a C++ console application:
#define _JSRT_
#include "ChakraCore.h"
#include <string>
#include <iostream>

using namespace std;

int main()
{
    JsRuntimeHandle runtime;
    JsContextRef context;
    JsValueRef result;
    unsigned currentSourceContext = 0;
    int returnedValue;

    const char* script = "var $variable1 = 611;\r\n"
        "var _variable2 = 711;\r\n"
        "var variable3 = 678;\r\n"
        "\r\n"
        "$variable1 + -variable2 - variable3;"
        ;

    // Create a runtime
    JsCreateRuntime(JsRuntimeAttributeNone, nullptr, &runtime);

    // Create an execution context
    JsCreateContext(runtime, &context);

    // Now set the execution context as being the current one on this thread.
    JsSetCurrentContext(context);

    const char* fileName = "variables.js";
    JsValueRef sourceUrl;
    JsCreateString(fileName, strlen(fileName), &sourceUrl);

    JsValueRef scriptSource;
    JsCreateString(script, strlen(script), &scriptSource);

    // Run the script
    JsErrorCode errCode = JsRun(scriptSource, currentSourceContext++, sourceUrl,
        JsParseScriptAttributeNone, &result);
    if (errCode == JsNoError)
    {
        JsValueRef resultJSString;
        JsConvertValueToString(result, &resultJSString);

        char* resultSTR = nullptr;
        size_t stringLength;
        JsCopyString(resultJSString, nullptr, 0, &stringLength);
        resultSTR = (char*)malloc(stringLength + 1);
        JsCopyString(resultJSString, resultSTR, stringLength + 1, nullptr);
        resultSTR[stringLength] = 0;

        printf("Result -> %s \n", resultSTR);
        free(resultSTR);

        returnedValue = 0;
    }
    else
    {
        printf("Error %d\n", errCode);

        if (errCode == JsErrorScriptException)
        {
            JsValueRef errMetadata;
            JsGetAndClearExceptionWithMetadata(&errMetadata);

            const char* sourcePropertyName = "source";
            JsPropertyIdRef sourcePropertyId;
            JsCreatePropertyId(sourcePropertyName, strlen(sourcePropertyName), &sourcePropertyId);

            bool hasProperty;
            JsHasProperty(errMetadata, sourcePropertyId, &hasProperty);

            if (hasProperty)
            {
                JsValueRef sourceLine;
                JsGetProperty(errMetadata, sourcePropertyId, &sourceLine);

                char* sourceLineSTR = nullptr;
                size_t stringLength;
                JsCopyString(sourceLine, nullptr, 0, &stringLength);
                sourceLineSTR = (char*)malloc(stringLength + 1);
                JsCopyString(sourceLine, sourceLineSTR, stringLength + 1, nullptr);
                sourceLineSTR[stringLength] = 0;

                printf("Source line -> %zd characters in \"%s\" \n", stringLength, sourceLineSTR);
                free(sourceLineSTR);
            }
        }

        returnedValue = 1;
    }

    system("pause");

    // Dispose runtime
    JsSetCurrentContext(JS_INVALID_REFERENCE);
    JsDisposeRuntime(runtime);

    return returnedValue;
}

You can download the 64-bit version of this demo project from the Dropbox.

This increase in the source length property - to be significantly higher than the actual length is an error, I will look into a fix.

There is a feeling that 106 characters is length of input script without \r characters.

The change was introduced by this commit: https://github.com/microsoft/ChakraCore/commit/469b0863c15118fd5a7ca1817346edd12471cd3c with the edit it made to JavascriptExceptionMetadata.cpp - however I cannot see the reason for that edit.
It appears to be unrelated to the rest of the commit AND it is clearly wrong - it adds the start offset for the line onto the end offset - hence always getting the full length of the script BUT the start offset remains the start of the line.
I will revert this change and look into adding a relevant test case - though that may be slightly tricky.

Thanks!


FILENAME already defined warning using ESP32 SDK

Thanks for the great library.
Using the ESP32 SDK, installed using Espressif installation guide results in a FILENAME already defined warning:
.../Documents/Arduino/libraries/AsyncTelegram2/src/serial_log.h:10: warning: "__FILENAME__" redefined
 #define __FILENAME__ (strrchr(__FILE__, '\\') ? strrchr(__FILE__, '\\') + 1 : __FILE__)

The warning indicates it is already defined in the ESP32 SDK at:
...Arduino15/packages/esp32/hardware/esp32/2.0.1/tools/sdk/esp32/include/newlib/platform_include/assert.h:38: note: this is the location of the previous definition
 #define __FILENAME__ (__builtin_strrchr( "/" __FILE__, '/') + 1)

Please change the define in serial_log.h to something else, e.g. __FILE_NAME__

Thanks @DeWonderMan
I've done as you suggested 👍


GraphQL - Anime Mutations

Checklist

[ ] All files pass Rubocop
[ ] Any complex logic is commented
[ ] Any new systems have thorough documentation
[ ] Any user-facing changes are behind a feature flag (or: explain why they can't be)

[ ] All the tests pass
[ ] Tests have been added to cover the new code

dependent on #736 being merged

This is to update the anime type library entry?

This is to update the anime type library entry?

No, this is to create, update, delete anime. #736 handles the updates of library entries.


Popover demo is broken in iOS

Hey!
First of all, his project looks really cool!
I noticed that the display of the buttons in the popover demo doesn't work in iOS 10

Ah flexbox :) thanks I'll take a look tonight

Should be fixed via https://github.com/enigma-io/boundless/commit/0faed043d1ad3f714c13b081edd32d3f8a82d542 when travis finishes rebuilding. Thanks for reporting!


Remove gpl files

Fixes https://github.com/hyperledger/solang/issues/1598

Test failure is unrelated, fixed in https://github.com/hyperledger/solang/pull/1615


Helm: Updated deprecated resources

Updated deprecated Kubernetes resources that don't work on new releases.

Hey @Rayyis
Have you already tested the changes?

close this PR firstly. feel free to reopen it.


[Feature] Pytest Conversion: Files [OSF-8077]

Purpose
Conversion of API tests to Pytest
Increase in performance
Changes
Pytest conversion for all test files in Files folder
Grouping of tests for all test files in Files folder
Side effects
Not Known
Ticket
https://openscience.atlassian.net/browse/OSF-8077

@shadowgamefly Did you mean to close this PR?

@alexschiller I accidentally closed this yesterday, so I just opened another one....

reference to pull request #7291


tsp.cc is in a list of routing examples on page examples/cpp but the file is missing

What version of OR-Tools and what language are you using?
Version: master/stable
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
Routing Solver
What did you do?
No tsp.cc present in examples/cpp although other routing examples cvrptw.cc and pdptw.cc are in the directory.

which pages ? link welcome
otherwise we do have https://github.com/google/or-tools/blob/stable/ortools/constraint_solver/samples/tsp.cc

There's a link https://github.com/google/or-tools/tree/master/examples/cpp


Removing duplicates from devfile catalog test

What type of PR is this?
/kind cleanup
What does does this PR do / why we need it:
Removes the duplicates from test script
Which issue(s) this PR fixes:
Fixes - Part of #3385
PR acceptance criteria:

[ ] Unit test

[x] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:
make test-cmd-devfile-catalog should pass.

/approve

/lgtm

/lgtm


Added the changes in mentioned branch and some tests for vad and silero vad

/claim #241
Fixes #241
I added the changes of the branch #250 and some tests for vad and silero vad

@itsdheerajdp it seems you did not rebase on main, can you do so? then will test, merge, & approve bounty!

, can

@itsdheerajdp it seems you did not rebase on main, can you do so? then will test, merge, & approve bounty!

yeah sure i'll do

@louis030195 I resolved the changes and also pushed the changes after synching the main branch kindly check it out and let me know if it needs any further updates

@itsdheerajdp please do not request review if you did not resolve my points


MRG, FIX: Fix bug with metadata and event_repeated

Addresses the first part of #7732
@kingjr can you try it?

The merge behavior is kind of weird for the metadata, but I think that's a separate and non-trivial issue.
I would still recommend to add the repeated_events='ignore' option, but this is also separate.
Else LGTM

The merge behavior is kind of weird for the metadata, but I think that's a separate and non-trivial issue.

Indeed, maybe we should not allow merging when metadata is present.

I would still recommend to add the repeated_events='ignore' option, but this is also separate.

Let's leave #7732 open to track and discuss this (it's why I didn't add the "closes" tag to the PR description)


Implement history

Hi,
It would be nice to have history as in GraphiQL
Thanks,

@psamim How do you propose that the history should be implemented, considering that altair has support for multiple tabs?

Maybe vertical tabs? Something like Graphiql. Now I have to copy and paste my queries in an editor to work with altair.

@psamim The history functionality has been implemented.


Long strings getting cut off

I'm using xlsx.utils.json_to_sheet(data) and some of the strings in data are really long. Those strings get cut off, eg. from 200,797 to 32,767 characters.
I don't think there's anything wrong with my code but here it is just in case. It converts a GeoJSON file to an Excel spreadsheet, the geometry field is the one getting cut off.
const xlsx = require('xlsx');
const jsonData = require('./parcels.json');

const data = jsonData.features.map((feat) => ({
  ...feat.properties,
  geometry: JSON.stringify(feat.geometry),
}));

const book = xlsx.utils.book_new();
xlsx.utils.book_append_sheet(book, xlsx.utils.json_to_sheet(data), 'parcels');
xlsx.writeFile(book, './parcels.xlsx');

This is an Excel limitation.
Even though it isn't explicitly stated https://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3 references the 32767 character limit in a few places.
Just testing in Excel, REPT("a",32767) is a string but REPT("a",32768) is a #VALUE! error.  The REPT documentation also says:

The result of the REPT function cannot be longer than 32,767 characters, or REPT returns #VALUE!.

So we're left to conclude that it is an Excel issue


Needs an example of using an output variable from a previous job in a custom condition

The syntax for using output parameters from previous job in conditions is not exactly as one might expect, as confirmed in this issue: https://developercommunity.visualstudio.com/content/problem/760780/in-multi-job-pipelines-job-variable-resolution-occ.html It's probably worth adding an example to the Conditions page of how to use output variables this way.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3f151218-9a11-0078-e038-f96198a76143
Version Independent ID: 09c4d032-62f3-d97c-79d7-6fbfd89910e9
Content: Conditions - Azure Pipelines
Content Source: docs/pipelines/process/conditions.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

@buck-mbeer You can see our updated doc here.

Looks great, thanks for the update @juliakm


Error/Warning during startup of the Xfinity Usage addon.

Discussed in https://github.com/thor0215/hassio-xfinity-usage/discussions/45

Originally posted by wade-lich October 14, 2024
I am receiving the following error:
ERROR: Navigated to password page for the  2nd time. Exiting
and the following warning:
(repeats 3 times then app crashes)
2024-10-14T11:49:28.482 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised AttributeError: 'XfinityUsage' object has no attribute 'SENSOR_URL'.
2024-10-14T11:49:29.483 WARNING: 1st retry
2024-10-14T11:49:30.831 INFO: Launching Mozilla/5.0 (Android 10; Mobile; rv:124.0) Gecko/124.0 Firefox/124.0
2024-10-14T11:49:32.872 INFO: Loading Xfinity Authentication (URL: https://login.xfinity.com/login)
2024-10-14T11:49:33.063 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-10-14T11:49:41.130 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-10-14T11:49:55.322 INFO: Updating Session Details
2024-10-14T11:50:00.181 INFO: Loading Plan & Usage Data (URL: https://www.xfinity.com/learn/internet-service/auth)
2024-10-14T11:50:00.518 INFO: Updating Session Details
2024-10-14T11:50:01.824 INFO: Updating Plan Details
2024-10-14T11:50:03.457 INFO: Updating Usage Details
2024-10-14T11:50:04.020 INFO: Usage data retrieved and processed
2024-10-14T11:50:06.707 INFO: Updating Session Details
2024-10-14T11:50:15.787 INFO: Unloading Xfinity
I don't get them both in the same running session of the app.  It's normally one or the other.
This started 6 days ago, FWIW.  Does anyone else have this issue?  I've removed and reinstalled the addon without change to the end result.
--Regards
Wade

I'm experiencing this same issue.
How does this plugin handle 2fa? When logging into Xfinity I must approve the login from the Xfinity mobile app.

The addon will only work if your Xfinity account does not use 2FA.


Error: Vault not found

Hi! I would like to report that the plugin is not working form me. I have my notes in an absolute Path but the plugins can't open my notes in Obsidian. It only displays them on Ulalauncher but when I try to open them, this error  appears.

Regards.

Ok. I think there is a bug when using a dot. I will check the code.

Thank you very much!

I have found the issue. You included a dot in your vault name. The code I have written see this as a file with an extension. (https://github.com/mikebarkmin/ulauncher-obsidian/blob/4a3aa6826b374407c6eca161b637ae26b56e5c8e/src/functions.py#L77). I try to fix it.


Use CommandParser instead of LaxOptionParser in django1.8

@jezdez I added a django version check to use CommandParser instead of LaxOptionParser if django>=1.8. I've tested it locally, this commit closes #65. django-configurations and pytest-django tests succeed.

@jezdez help text needs to be added to th --configuration argument. Would you like to check django version differently?

I guess that works as well, sure, thanks for the update. FWIW I just recently backported the lax option parser since it's really only used in a minor way, but I guess your patch is more future proof :)

@jezdez I cleaned the importer file however, this needs more work because the configuration option can't be installed the same way in django1.8 than before.

Setting config with environment variables works, but I can't see how to fix the command-line --configuration option with argparse in install function. I tried many possibilities, but none worked. I asked the question in django repo https://github.com/django/django/commit/856863860352aa1f0288e6c9168a0e423c4f5184#commitcomment-9530701 to @claudep. Do you have an idea on how this could be done @jezdez ?

Thanks @benjaminabel, the patch was almost there, see f35e7e57e070aecb47d675d0de2b319808847c01 for an implementation that adds the --configuration option to the argparse parser.

And 6ce3740365d92c329c1e20036266cd090d57b7c4 :)

Nice job @jezdez, I did try to use the create_parser method but I didn't know how I could override the django one permanently as you do in line 40 of importer.py:  base.BaseCommand.create_parser = create_parser. Thanks for the lesson.

This is still a problem for my project:
from django.core.management import LaxOptionParser
ImportError: cannot import name LaxOptionParser

I'm guessing this will be because 1.8c1 < 1.8 in semver notation right?

I don't think the error comes from the if statement:
>>> from django import VERSION as DJANGO_VERSION
>>> DJANGO_VERSION >= (1, 8)
True
>>> print(DJANGO_VERSION)
(1, 8, 0, 'rc', 1)

Are you using master branch of django-configurations?

My bad, I was using the pypi version. Thanks for the help, sorry to bother you!

When is the Django 1.8 compatible branch being pushed?

Just stumbled across the same problem and it's already fixed :+1: Awesome work! Any chance you release an updated version to PyPI @jezdez?

see #105


Added iFood.com.br beta bug bounty program

IFood - leader in online food delivery in Brazil - is one of the most innovative food techs in the world. Six years in the market, with it’s origin in Brazil, is present also in Mexico, Argentina and Colombia.

Thank you @celsec for the PR, I've updated the PR as listed in the readme for TLD input.


Add test

Yes, it would be great to add some testing. I made a commit but there is no way to check it makes any sense apart from type-checking with GHC :)


May22 container insights prometheus poc

Description:
Proof of concept of modification to container insights receiver that scrapes prometheus metrics from k8sapiserver
High level, I am wrapping the SimplePrometheusReceiver (which wraps the PrometheusReceiver) to collect the metrics I need.  I shim in my own consumer to add the attributes I need
This is a more sustainable variation of my last attempt using a custom built scraper: https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/13
Gaps / Next steps

Need more metrics beyond apiserver_storage_objects
Need to aggregate some of the metrics (i.e. apiserver_storage_objects_total)
need to relabel some of the dimensions (i.e. resource should be Resource)
Need to enable leader election / refactor existing leader election

The following change in CCWA enables metrics to flow:
diff --git a/translator/translate/otel/exporter/awsemf/kubernetes.go b/translator/translate/otel/exporter/awsemf/kubernetes.go
index d9c6476..199bf98 100644
--- a/translator/translate/otel/exporter/awsemf/kubernetes.go
+++ b/translator/translate/otel/exporter/awsemf/kubernetes.go
@@ -88,6 +88,21 @@ func setKubernetesMetricDeclaration(conf *confmap.Conf, cfg *awsemfexporter.Conf
                },
        }...)

+       kubernetesMetricDeclarations = append(kubernetesMetricDeclarations, []*awsemfexporter.MetricDeclaration{
+               {
+                       Dimensions: [][]string{{"ClusterName", "resource"}},
+                       MetricNameSelectors: []string{
+                               "apiserver_storage_objects",
+                       },
+               },
+               {
+                       Dimensions: [][]string{{"ClusterName"}},
+                       MetricNameSelectors: []string{
+                               "apiserver_storage_objects",
+                       },
+               },
+       }...)
+
        // Setup service metrics
        kubernetesMetricDeclarations = append(kubernetesMetricDeclarations, []*awsemfexporter.MetricDeclaration{
                {

Our main got wiped out (by me? woops).  The relevant commit is this:
https://github.com/amazon-contributing/opentelemetry-collector-contrib/commit/95772bd464afee0a97b64f840f64a59dfd2e7550
Link to tracking Issue:
Testing:
Data flowing to CloudWatch

Just realized - this PR should be against the aws-cwa-dev branch, not main

Just realized - this PR should be against the aws-cwa-dev branch, not main

fixed!


Support Proto2 extensions in JSON coder/decoder

This is sufficient to pass the conformance check that was recently added, but still needs some additional testing and polish.
Addresses #993

I'm still filling in tests and tracking down missing bits.  I'll look into Any JSON support next.

I've filled in support and tests for Any + JSON + extensions, including figuring out a reasonable answer for implicit transcoding (TL;DR: extensions now cause JSON->binary transcoding to throw because none of the other options seemed better).
I've filled in additional tests for message-valued extension fields, arrays, and a few other cases.

This feels like it's in pretty good shape now.  Any concerns before I merge it?


bzip2/1.0.8 error

I was trying to build this and got this error.
bzip2/1.0.8: WARN: Build folder C:\Users\Changsoo\.conan\data\bzip2\1.0.8\_\_\build\3fb49604f9c2f729b85ba3115852006824e72cab\build
ERROR: bzip2/1.0.8: Error in build() method, line 63
        cmake.configure(build_script_folder=os.path.join(self.source_folder, os.pardir))
        ConanException: Error 1 while executing cmake -G "Visual Studio 16 2019" -DCMAKE_TOOLCHAIN_FILE="C:/Users/Changsoo/.conan/data/bzip2/1.0.8/_/_/build/3fb49604f9c2f729b85ba3115852006824e72cab/build/generators/conan_toolchain.cmake" -DCMAKE_INSTALL_PREFIX="C:/Users/Changsoo/.conan/data/bzip2/1.0.8/_/_/package/3fb49604f9c2f729b85ba3115852006824e72cab" -DCMAKE_POLICY_DEFAULT_CMP0091="NEW" "C:\Users\Changsoo\.conan\data\bzip2\1.0.8\_\_\build\3fb49604f9c2f729b85ba3115852006824e72cab\src\.."

Before this, I ran this.
conan install . --install-folder build
I got this error
ERROR: Missing prebuilt package for 'bzip2/1.0.8'
Use 'conan search bzip2/1.0.8@ --table=table.html -r=remote' and open the table.html file to see available packages
Or try to build locally from sources with '--build=bzip2'

Then I tried to rebuild and got the first error.
conan install .. --build missing

Never mind. user error..


Update hub-spoke-content.md

Correcting a small misspelling. Changed "crate" to "create".

The typo fix looks good; thanks.


Get docs/tutorial UI mockups

Mattia plans to be working on this, not sure the exact timeline but hopefully soon. Until then just focus on core functionality

child of #3


[flake8-bugbear] add autofix for B006 mutable_argument_default

Summary
Adds an autofix for B006 turning mutable argument defaults into None and setting their original value back in the function body if still None at runtime like so:
def before(x=[]):
    pass

def after(x=None):
    if x is None:
        x = []
    pass

Test Plan
Added an extra test case to existing fixture with more indentation. Checked results for all old examples.
NOTE: Also adapted the jupyter notebook test as this checked for B006 as well.
Issue link
Closes: https://github.com/charliermarsh/ruff/issues/4693

Sorry I didn't realize that merging #5776 would create merge conflicts here.

(This PR is on me to do final review + merge.)


Verify block author according to the currently imported pc block instead of peeked one

closes #750

replaced by #777


Bad code

This code to invoke the Background Task occurs near the bottom of the Page Extension sample code:
CurrPage.EnqueueBackgroundTask(WaitTaskId, 50100, TaskParameters, 1000, PageBackgroundTaskErrorLevel::Warning);
You hard coded the Codeunit ID 50100 from the sample code used to create the Codeunit earlier in the article. This will assuredly cause some poor soul some consternation and lost time when they innocently change the ID number of the Codeunit and then wonder why the code doesn't work.

Follow your own best practices and use Codeunit::PBTWaitCodeunit so that if someone made changes they will get a compile error
Add a note in the Codeunit and Page Extension article explanations pointing out that the actual Codeunit number is used in the Background Task invocation.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 591f8762-9808-22f5-112d-f6d80f337b0e
Version Independent ID: 6731b849-04f3-9bd2-5877-8c2bf26b8f34
Content: Page Background Tasks - Business Central
Content Source: dev-itpro/developer/devenv-page-background-tasks.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: jswymer

Thanks! The article has been updated and the new version will be published soon.


Transit layer doesn't include railway=narrow_gauge and railway=monorail

The transit layer does not include railway=narrow_gauge and railway=monorail, while the roads layer does. Seems like they should be consistent (and pack them at zoom 10 like subway and light_rail).
roads.jinja2
              OR railway IN ('rail', 'tram', 'light_rail', 'narrow_gauge', 'monorail')

functions.sql
CREATE OR REPLACE FUNCTION mz_calculate_transit_level(route_val text)
RETURNS SMALLINT AS $$
BEGIN
    RETURN (
        CASE WHEN route_val IN ('train', 'railway') THEN 6
             WHEN route_val IN ('subway', 'light_rail', 'tram') THEN 10
             ELSE NULL END
    );
END;
$$ LANGUAGE plpgsql IMMUTABLE;

This is comparing two different things: The roads query is looking at the railway key, but the transit query (via mz_calculate_transit_level) is looking at the route key.
The difference is that railway= is generally tagged on the way which represents the geometry of the physical track, whereas route= is generally tagged on a relation containing not only the collection of track geometries but also the stations and/or stops which make up a regular named service or line.
We should include route=monorail (49 instances) and route=narrow_gauge (2 instances), but we need to be clear that these are not the same tags - and we shouldn't expect a route=light_rail to necessarily contain all/only railway=light_rail.
Also, it looks like there are railway=subway ways (32,543 instances) - should we look at including those too?


Post links aren't updating

Hi, this is my first time using Jekyll, so I may just be making a simple mistake. I've forked the repository and have changed all the needed variables in the configurations file. I also changed the base url to /tale. Unfortunately, the links for the posts still link to the posts on your website, instead of reading the config file and linking to my website.

Your website looks like its working fine to me. Think you already fixed it :) Shall close this for now

Yup, a lot of testing and I got it working. Just in case anybody runs in to this same problem, I'll put my solution here.
Since I used gh-pages to put my blog on a link like mywebsite.com/blog instead of just mywebsite.com, the urls for the posts and about section would link to nonexisting entities such as mywebsite.com/2017/08/24/post, which SHOULD have been mywebsite.com/blog/2017/08/24/post.
To fix this, find the sections in the default.html, post.html, and index.html that include Jekyll input for prepend: site.url. For example in default.html there is
About
. Just include prepend:site.baseurl if you're in the same situation as me. Therefore, it would become
About
.
Hope this helps anybody that is stuck!

@2018sjain Hmm, alternatively you could change the site url field in the config file to be "mywebsite.com/blog" instead of "mywebsite.com". Hope this helps :)

I actually tried that, but unfortunately there was an issue with the style.css file not being accessed. However, this is my first time using Jekyll so there's a high chance I just made an error somewhere along the way.


Make pymongo optional again

Also add a tox env, that installs sacred in a plain version, to test that it works without optional dependencies.

Coverage increased (+0.004%) to 85.104% when pulling c8cb8f8f4b6d3d7ed906d40152d4ff5ffafe1ac8 on JarnoRFB:optional-pymongo into 29e14eb8eba6c758f6f9fb77a2bdc6ddf21ab9b6 on IDSIA:master.

We should probably backport this to the 0.7.5 release and update the pypi version. Did we do any other bugfixes since, that should be backported to the py2 compatible release?

I'd really appreciate the backporting! We can't use 0.8.x as we need the python2 support for now.


UIPlugin: add support level annotation during reconciliation

Fixes: COO-449

/close
already implemented in #604 .


Add autosigma notebook

This PR addresses issue #
Please Check

[ ] Are the JSON schemas updated?
[ ] Are the api docs updated?
[ ] Are tests passing?

@ghop02 let's discuss if we want things like this to have binder support.
Also, I had to bump some requirements to make the jupyter lab interactive widgets work. I think they are significant improvements and we should support them, but haven't done it yet. Finally time for Poetry?

Specifically I know there is a mismatch between the newest jupyter lab and our currently pinned version of ipympl.


Use PanicHookInfo in savvy-cli

Close #282
I think I can introduce a #[rustversion] switch here, but, for the sake of simplicity, I chose to bump the MSRV of savvy-cli. This doesn't affect savvy.

Hmm, seems a bit too early... Let's wait for a while until the CI runners' toolchain get up-to-date.


AppSync Lambda resolver dotnet sample

Describe the Feature
AppSync Lambda resolver dotnet sample
Is your Feature Request related to a problem?
Can't find one official docs about this topic. Please provide an example.

Hi @thesobercoder,
Good afternoon.
The article Tutorial: AWS Lambda Resolvers provides an example on how to use AppSync with AWS Lambda. It talks about having Lambda expose set of operations. On the similar lines, I came across the useful post AWS: AppSync with Lambda Resolver for MongoDB using DotNet core which lists step by step example for using AppSync with Lambda (NOTE: Kindly use this article as a reference, not as the actual production code).
Please let me know if this helps and if this issue could be closed.
Thanks,
Ashish


docs : Mentioned details about license in readme file

Readme file was not having license mentioned so I added details about license.

I signed it!

the page is showing message Access not possible

@gkanishk Nah, I don't think we need to mention it specifically in the README. Having a top-level LICENSE file is a well-known practice.
Thank you for the PR though!


Road to release

[x] More fields in response object

[x] Headers

[x] nimpretty
[x] Basic CI with tests
[x] Better default values. Not secs, maybe empty arrays
[x] Remove fmt if not realy needed
[x] Examples
[x] Docs in readme
[ ] Add to nimble packages

https://github.com/nim-lang/packages/pull/2752


Please change the http to https in the yandex geocoder url

in file: lib/geokit/geocoders/yandex.rb
in the def self.submit_url
replace http://geocode-maps.yandex.ru to https://geocode-maps.yandex.ru
because http does not work for yandex

Is it possible for you to do a PR for this change?
Do you know if there's any documentation from yandex that HTTP no longer works?
Also, do you know if there's a free test yandex.ru account (or can you get one) so geokit can ensure it picks up on these things and can test changes in future (currently the original author has fixtures assuming yandex won't change, which is often the only solution)

Is it possible for you to do a PR for this change?

Pull request

Do you know if there's any documentation from yandex that HTTP no longer works?

On their page:
https://tech.yandex.com/maps/doc/geocoder/desc/concepts/input_params-docpage/
specified protocol http, but their example:
http://geocode-maps.yandex.ru/1.x/?geocode=Kabasakal+Caddesi,+Istanbul,+Turkey&lang=en-US
redirect to:
https://geocode-maps.yandex.ru/1.x/?geocode=Kabasakal+Caddesi,+Istanbul,+Turkey&lang=en-US

Also, do you know if there's a free test yandex.ru account (or can you get one) so geokit can ensure it picks up on these things and can test changes in future (currently the original author has fixtures assuming yandex won't change, which is often the only solution)

can't say anything about this

Closes as your PR https://github.com/geokit/geokit/pull/170 is merged. Thanks again @nazarok I really appreciate you finding those links and examples so we have a reference as to why it has changed.


Tweak formatting

Coverage remained the same at 71.371% when pulling bd88dd85cdfc647dcfa6ba1fb234ed80a03b5ded on bbodenmiller:patch-1 into 060f52f59774c2fb8e24698da0a74cc7f6cfb8c9 on bndr:master.

Coverage remained the same at 71.371% when pulling bd88dd85cdfc647dcfa6ba1fb234ed80a03b5ded on bbodenmiller:patch-1 into 060f52f59774c2fb8e24698da0a74cc7f6cfb8c9 on bndr:master.

Coverage remained the same at 71.371% when pulling bd88dd85cdfc647dcfa6ba1fb234ed80a03b5ded on bbodenmiller:patch-1 into 060f52f59774c2fb8e24698da0a74cc7f6cfb8c9 on bndr:master.


Update provider docs to remove "Scopes" arg from GetTokenAsync

Fixes #
Docs for Toolkit PR #
What changes to the docs does this PR provide?
Removed scopes arg from GetTokenAsync in documentation for Windows and MSAL providers.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Correctly picked the right branch to base the change off (dev for new features, master for typos/improvements)
[x] Contains NO breaking changes

These docs don't exist anymore, going to close


ngsw-config

Versions
Angular CLI: 1.6.0-rc.2
Node: 8.9.1
OS: darwin x64
Angular: 5.0.4
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.0.0-rc.2
@angular/cli: 1.6.0-rc.2
@angular/flex-layout: 2.0.0-beta.10-4905443
@angular/material: 5.0.0-rc.2
@angular/service-worker: 5.0.5
@angular-devkit/build-optimizer: 0.0.34
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.39
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0-rc.2
@schematics/angular: 0.1.9
typescript: 2.4.2
webpack-bundle-analyzer: 2.9.0
webpack: 3.10.0

Desired behavior

Is there a way to generate the ngsw-config.json file? Or can I see the default one somewhere?
Mention any other details that might be useful (optional)

Creating a new project with the --service-worker option should create the file.
The template for the file is located here: https://github.com/angular/devkit/blob/master/packages/schematics/angular/application/files/path/ngsw-config.json

@clydin is there a wiki or so with the available settings?


Safari: tab linear gradient rendering is not working

Up for grab, this may just be Safari not supporting our linear-gradient properly:
https://github.com/microsoft/vscode/blob/d1578555f7247b8070df0ba625d046859a163f04/src/vs/workbench/browser/parts/editor/tabsTitleControl.ts#L1633-L1727

possibly related, the shadow of the editor minimap is also not rendering well -- https://github.com/microsoft/vscode/issues/108822

Since I cannot figure out why this happens and it looks very bad, I pushed a change to disable linear-gradient in tabs on Safari.

I am not planning to bring it back, closing.


Does it support the recognition of vertical text?

Vertical text is recognized after being rotated 90 degrees.
e.g.:

Thank you for the reply


📦 version 3

There's a lot going on in this pull request. Fortunately, because we've worked on it in small chunks, most of it has already been reviewed :)
Commits edbad19, cf3612d, 544f4e6, f3f95b7 and fc16600 have all been reviewed already. The relevant PRs are linked in the commit messages, although they've now been though some rebasing to get the branch up to date with master.
Commit 2c02630 and onwards are all new in this PR, but its mostly moving stuff about and a final review/update on the docs.
The next steps I think we should make on this are:

Merge this and deploy it. Then shields.io will be finally running off the new package code, including new template code introduced in #4459
Publish a beta/release candidate to NPM using the new package name
Monitor production for errors. We're the biggest user of our own package. I suspect if we've overlooked any bugs we'll spot them pretty fast once we're using it in production
Publish a stable release using the new package name
Publish a final gh-badges 2.2.2 release advising users to upgrade
Mark gh-badges dead/unmaintained on NPM
Start work on v3.1

but happy to discuss it.
Just to review the roadmap/issues:

Merging this closes #3480
Merging this closes #4564
This PR contains all the changes discussed in #3587 which require a BC-break. When we merge this I will close that and raise new issues for:

Expose the concept of logos, add SimpleIcons as a peer dependency
Depend on the public interface internally instead of relative imports
Add typescript definitions to make package easier to use with TypeScript
We can make those changes later/in a feature release without breaking backwards compatibility.

Usual review process aside, it would be particularly useful to get another set of eyes on the documentation to make sure we're all up-to-date and the migration advice in the changelog is correct.

Warnings

:warning:
This PR modified the server but none of its tests. That's okay so long as it's refactoring existing code.

:warning:

This PR modified helper functions in lib/ but not accompanying tests. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against ff59839b6cbd8863c9e82f6ac1a9482d43f0eb60

Only a handful of service test failures that were unrelated 👍

Tangential question to https://github.com/badges/shields/pull/4756#discussion_r390566136: are we still using the package to generate the JSON badges? At some point after this is merged, I'd like to refactor the server parts which touch makeBadge() and stop running the JSON badges through it.

Hrmmm.. So first lets start with a bit of disambiguation. There's 2 makeBadge() functions in the package - one public and one internal:
https://github.com/badges/shields/blob/40bfc6ec51598589c63a83f6499b50eab69d9361/badge-maker/lib/make-badge.js#L11
https://github.com/badges/shields/blob/40bfc6ec51598589c63a83f6499b50eab69d9361/badge-maker/lib/index.js#L75
Lets call them lib/make-badge.makeBadge and lib/index.makeBadge just to avoid confusion.
Internally, we depend on relative imports to lib/make-badge.makeBadge (so we're depending on the internals of our package as opposed to its public interface). See https://github.com/badges/shields/pull/4756/commits/32ed0531bd0c563e37915dc0abc47940bca62b8e . At the moment we have to do that because there's functionality we rely on for shields.io which is not exposed via the NPM package (logos and links). This means we have a somewhat poorly defined interface boundary.
What that means is we're not in the starting place where you think we are, but we're already in the place you think we should move to.
I've been broadly thinking in the opposite direction though. I think we should try to move to a situation where shields.io depends on the public interface of the badge-maker package (lib/index.makeBadge) so we're "eating our own dog food". Moving away from relative imports to lib/make-badge.makeBadge was one of the original jobs in the v3 roadmap https://github.com/badges/shields/issues/3587 but its predicated on adding logos to the package which can be done in a future release with no BC break. That said, I'm not completely wedded to that course of action. Maybe its just tinkering we don't really need to do.
Based on your comment, I'm guessing your next suggestions is going to be that we drop JSON support from the library. While I'm on board that its a bit pointless in the CLI, I'm less convinced on the library side. On the face of it,
const { makeBadge } = require('badge-maker')

const format = {
  text: ['build', 'passing'],
  color: 'green',
  format: 'json',
}

const badge = makeBadge(format)
console.log(badge)
// {"label":"build","message":"passing","color":"green","link":[],"name":"build","value":"passing"}

is a bit wierd, but broadly the reason we expose this is to make testing easier. We write tests. So do our users (or at least I hope they do :D ) so it feels like there is a legit use-case here and no real benefit to us in removing it.

I don't have any strong opinions on json support in the lib one way or the other, but happy to give this another 👍 if and when needed for merging

This one has kind of festered for a bit, but I'd quite like to try and resolve it one way or another. Partly because there's quite a large chunk of work here blocked on one decision. Also partly because if I have to resolve a merge conflict between this and reformatting every file in the codebase to upgrade prettier, I might go insane.

Don't feel strongly either, keeping JSON support in the library (but not the CLI) doesn't hurt much and comes in handy whilst testing or simply experimenting with the library. Generally speaking, your roadmap and future plans of "eating our own dog food" make perfect sense! :)
Overall this looks like good work to me, thanks for all the efforts and documentation! 👍
I've got one observation that's making me slightly nervous. I tried running that new benchmark tooling around the makeBadge call in base-static.js, and performance is now ~50% slower (from 0.054ms to 0.082ms on my machine, averaged over 5 executions of npm run benchmark:badge). It's probably not the end of the world given that we're talking about ~30μs, however, given that makeBadge can be invoked hundreds of times under heavy load and that our servers are already maxed out in terms of capacity, I thought I would mention it.

Its a good point. In the depths of the review comments for #4459 we did observe that switching away from doT does reduce performance: https://github.com/badges/shields/pull/4459#issuecomment-570706539
In the grand scheme of things, I don't think it really matters that its slightly slower when we're just thinking about one request. Potentially it does become important given our current infrastructure constraints. I'm not really sure how to gauge how big the impact will be when it comes to making lots of calls at peak load.
I did have a think about Paul's comments on optimisation in that thread, but I tested some benchmark runs using the default style (which uses a class and a lot of function calls) against some using the for-the-badge style (where almost all of the code is in one function) and it seems to make no difference to performance so I think that's probably a dead end..
Do you have any other thoughts on possible optimisations?

I'm not really sure how to gauge how big the impact will be when it comes to making lots of calls at peak load.

Ideally, it would have been nice to do a blue/green deployment on one of the servers, and take a look at the Grafana dashboard after a few hours. But we would need some level of coordination with Paul and make sure it's the only effective change compared to the previous deployment (i.e. we wouldn't want one of the servers offering a new badge and not the others). Not sure it's worth the effort. Will see whether I can generate some Flamegraphs locally instead.

Do you have any other thoughts on possible optimisations?

None yet, but I'm happy to do a more focused read through in the coming days and see if any easy wins stick out! But I wouldn't treat this as a blocker, again I'm only slightly nervous, I've got a feeling that even a 50% slowdown on makeBadge will still have a small overall impact. :+1:

I think you're right that this probably won't make a huge difference, but that's not a bad plan. If we were to deploy this change only on to one of the three servers then it should hopefully become clear if that server is performing substantially worse than the other two. If so, we could revert.

Ideally, it would have been nice to do a blue/green deployment on one of the servers

If we were to deploy this change only on to one of the three servers then it should hopefully become clear if that server is performing substantially worse than the other two

One thing I'm still unclear on (or keep forgetting) is our current load balancing strategy. Do we have a GTM-based strategy splitting between the two in Canada and one in France, and/or is there a round robin within a region, etc.
Admittedly I've still not had a chance to take a closer look at our existing measurement capabilities. However, questions like load balancing strategies, plus OVH's recurring issues of late in the Canada data centers (which have a strong correlation with the timing of our responsiveness issues FWIW), have me somewhat skeptical of how reliably we could measure/attribute performance issues to a single function like makeBadge especially considering all the other moving parts involved in servicing the badge request.
I'm a 100% on board with the principle of blue/green or canary deployments, but I'm not sure how readily we can do that with the current prod runtime. IMO there's a lot of uncontrollable/unknown variables in prod that can impact response times, and I'd expect there to be even more to consider if the change was only on a single server.
I'd personally lean towards deploying this changeset (in isolation/no other changes) via the typical deploy process (all servers) if we want to do some experimentation with this.
My two cents

I could update this with master and then deploy the branch to s0. That's probably the simplest way to get it deployed.
As far as checking performance, what I'd probably do is watch for (1) a bunch of bad badges on GitHub or (2) a spike in response times on that server. Maybe @platan has ideas on other things that can be monitored.
I missed that this was blocking on a substantive question, sorry! Let me respond to that next.

Based on your comment, I'm guessing your next suggestions is going to be that we drop JSON support from the library. While I'm on board that its a bit pointless in the CLI, I'm less convinced on the library side. On the face of it,
const { makeBadge } = require('badge-maker')

const format = {
  text: ['build', 'passing'],
  color: 'green',
  format: 'json',
}

const badge = makeBadge(format)
console.log(badge)
// {"label":"build","message":"passing","color":"green","link":[],"name":"build","value":"passing"}

is a bit wierd, but broadly the reason we expose this is to make testing easier. We write tests. So do our users (or at least I hope they do :D ) so it feels like there is a legit use-case here and no real benefit to us in removing it.

It seems to me a consumer of the library writing a test is basically writing a test like we'd write of one of our "transform" functions:
expect(JSON.parse(makeBadge({
  text: ['build', 'passing'],
  color: 'green',
  format: 'json',
}))).to.include({
  label: 'build',
  message: 'passing',
  color: 'green',
})

Ideally I think we'd go one step further in the library API, adding label and message, and deprecating the text parameter. Then the JSON really becomes a pass through and there's nothing left to test (except that valid SVG comes out).

@calebcartwright There isn't any true load balancing; it's just round-robin DNS.

So you've kind of answered a small question there, but passed over the big one :D
I think there is a big design question about what the badge-maker package should be which we don't all agree on:
One way of thinking about it is:
Option 1 - Badge-maker should be a stand-alone package. It happens to live in the same repo as shields.io, but in principle it could live in its own repository if we wanted. Its a package with many users, but its biggest and main user is shields.io. Any functionality we depend on should be exposed and documented via the public interface of the package and we consume that functionality in the same way as any other user, eating our own dogfood.
Another way of thinking about it is:
Option 2 - Badge-maker is a package which exposes only a subset of the badge rendering capibilites of shields.io to a wider audience. It lives in and is inseparable from the shields.io repo. The interface we give our users is different to the interface we consume internally.
Option 2 is where we are now. I've been thinking we should be heading towards option 1. I'm not necessarily right about that, but that's definitely the direction I've been thinking in. Given that removing a feature that our own application depends on from the public interface of the package actively reverses that direction of travel, I think its worthwhile to be explicit about the reasons for that.

Independently of that, and whichever way we go on it, this a very interesting point:

Ideally I think we'd go one step further in the library API, adding label and message, and deprecating the text parameter. Then the JSON really becomes a pass through

This has caused me to step back and think about the interface we're exposing in a way I haven't previously, but really really should have.
At the moment, our public interface is:
{
  text: ['build', 'passing'],
  labelColor: '#4c1',
  color: '#555',

  // we don't currently expose this, but internally we have
  links: ['https://foo/', 'https://bar/'],
}

If you take your point into account, but just think of it from the outside, the input object should probably really be:
{
  label: 'build', /*..or maybe */ labelText: 'build',
  message: 'passing', /*..or maybe */ messageText: 'passing',
  labelColor: '#4c1',
  messageColor: '#555', // as opposed to just color
  labelLink: 'https://foo/',
  messageLink: 'https://bar/',
}

or perhaps even:
{
  label: {
    text: 'build',
    color: '#4c1',
    link: 'https://foo/',
  },
  message: {
    text: 'passing',
    color: '#555',
    link: 'https://bar/',
  },
}

Zooming out, both of those feel more obvious/consistent. So whereas you're thinking modifying the input object to match our internals, this makes me think we should think about what is an intuitive interface from a user's perspective and then provide that..
Changing that would move us from one state where the public interface doesn't quite match the internals to another state where the public interface doesn't quite match the internals, but it makes more sense.
While we're making numerous non-BC changes, perhaps now is a good time to look at this too.

Its taken a while to respond to this, but getting more eyes and opinions on this is forcing me to think things through more and see stuff we've missed first time round, which is useful. I've also realised that:

Links are trivial to (re-)enable, so I might as well do that now once we decided on the interface and
By requiring both label and message in https://github.com/badges/shields/pull/3875 we break the ability to make a "message only" badge like  https://img.shields.io/badge/-message-blue so when I make changes based on discussion of the above, I'll fix that too!

@chris48s What do you think about merging this, shipping it as 3.0.0beta1 (or not, even) and continuing to address these open questions?

Sure. I think at this point there is value in being able to test the performance impact of the template changes and not have this huge changeset hanging over us as I think we're pretty settled on the changes to internals and badge rendering logic proposed in this PR, which is the meat of it.
I think I would like to try and make a reasonably final-ish decision about the names of the input object keys and fix the known issue before we publish a beta to NPM.

Sounds good!

Actually I have one idea how can we test a performance of this change.

Prepare a massive amount of URLs to different badges
Deploy shields from the master branch and for the v3-dev branch somewhere, e.g. at Heroku
Send requests to both deployments
Compare the response times and a server load using our metrics.

Regarding point 1, several weeks ago I started analysing GitHub public dataset available at GCP, https://medium.com/google-cloud/github-on-bigquery-analyze-all-the-code-b3576fd2b150. I haven't finish this (yet), but we are able to extract a lot of URLs to shields.io used by our users.

Following on from the conversation in #4849 I've updated this PR

Is the proposal in https://github.com/badges/shields/pull/4756#issuecomment-608061009 blocking on #4874?

@paulmelnikow - As discussed above, for the purposes of evaluating performance/easily rolling back if necessary it is useful to be able to deploy this in isolation.
As such, I'll leave it with you to actually press the merge button on this one so you can co-ordinate that. I'll pick up publishing the beta package once that's done.

This branch, specifically e356258, is live on s0.

I don't know exactly what times you deployed this/rolled it back, so its difficult to tell from the graphs but given we think the outage was linked to OVH do you fancy giving this another test next week and see what happens?

Yea, sounds good. I’ll do a deploy tomorrow and we can take this branch for a spin on Monday.

While trying to deploy this on s0, I got a message that the disk filled up again. I wrote Thaddée asking him to clean it. (I'm assuming it's Cypress installs, as before.)
As of now s0 has the same code as the other machines.

Okay, the disk on s0 is back to an okay place. I'll deploy this tonight.

13366fc5b01a4d66fc3bfbebdb70f9081059601b is live on s0!

It looks like unknown templates are causing internal errors which somehow aren't getting caught, causing requests to hang.
e.g. https://s0.shields-server.com/badge/foo-bar-blue?style=foobar
There are a good few dozen of these in the last couple minutes, so I'm thinking I'll probably roll this back.

Did you rollback already?
https://s0.shields-server.com/badge/foo-bar-blue?style=foobar

Whoops - have updated with a fix.

I've slightly lost track of what's deployed at this point, but are we pretty happy we've now ironed out the kinks with this?

The live one is 4999e55. I think we're confident it doesn't have major bugs.
I'm okay with merging this.
Has anyone evaluated how s0 is performing compared to historical?

Cool. In that case I'm going to crack on and merge this, push the release candidate and review the next steps..

After merging this PR I got an email from Heroku: "Automatic deployment of shields-staging failed".

Hmm. Thanks - good spot. The error it is failing with is
npm ERR! syscall access
npm ERR! path /tmp/build_213196dfe99649b0be38d9bc6dc323c7/node_modules/gh-badges
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, access '/tmp/build_213196dfe99649b0be38d9bc6dc323c7/node_modules/gh-badges'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

I wonder if there is some cache that needs to be cleared? The staging PRs were deploying correctly.

I've set NODEMODULESCACHE=true in the env vars for the staging pipeline, but I can't see a way to retry the deploy without pushing another commit to master. I'm going to check back on it tomorrow (inevitably we'll merge some dependency bumps tomorrow). If that fixes it, I'll unset the env var to re-enable the cache. If that doesn't fix it then I'll worry about it some more.

I think you can do that here, want to give it a try?


Hardcode the behavior of the parser

Ensures that ipv4 and ipv6 validity is exclusive
Sets the appropriate intial values for local_metadata fields
Determine validity of headers from the corresponding eth_type, protocol, etc fields

I think this is a lot better now, the hardcoded parser evaluation is invoked by default and can be disabled via command line flag (for my ci tests), it does not mutate any headers, and it fails quite explicitly with absl errors when the input program is not right (e.g. does not have some important field like eth_type).

LGTM, please submit


Add a wolfi-os base image

Add a wolfi-os base image.
Test image available at:
gcr.io/vorvan/h2oai/h2ogpt-lmdeploy-wolfi-base:test-build1

quick test using lmdeploy serve api_server OpenGVLab/Mini-InternVL-Chat-2B-V1-5

example request:
curl -X 'POST' \
  'http://mr-dl31:23333/v1/chat/completions' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "/root/.cache/huggingface/hub/models--OpenGVLab--Mini-InternVL-Chat-2B-V1-5/snapshots/85252c80a0d2bf85b6556d7cda98370d3009c74d",
  "messages": [
    {
      "content": [
            {"type": "text", "text": "What's in this image?"},
            {
                "type": "image_url",
                "image_url": {
                    "url": "https://h2o-release.s3.amazonaws.com/h2ogpt/bigben.jpg"
                }
            }
        ],
      "role": "user"
    }
  ],
  "temperature": 0.7,
  "top_p": 1,
  "tools": null,
  "tool_choice": "none",
  "logprobs": false,
  "top_logprobs": 0,
  "n": 1,
  "max_tokens": null,
  "stop": null,
  "stream": false,
  "presence_penalty": 0,
  "frequency_penalty": 0,
  "user": "string",
  "repetition_penalty": 1,
  "session_id": -1,
  "ignore_eos": false,
  "skip_special_tokens": true,
  "top_k": 40
}'

returns the following response:
{
  "id": "5",
  "object": "chat.completion",
  "created":<PHONE_NUMBER>,
  "model": "/root/.cache/huggingface/hub/models--OpenGVLab--Mini-InternVL-Chat-2B-V1-5/snapshots/85252c80a0d2bf85b6556d7cda98370d3009c74d",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "This image depicts a nighttime scene in a cityscape, with a prominent clock tower labeled \"Big Ben\" in the background. The clock tower is illuminated and stands tall against the dark sky. In the foreground, there are blurred lights, likely from moving vehicles, creating a dynamic and vibrant effect.",
        "tool_calls": null
      },
      "logprobs": null,
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 1834,
    "total_tokens": 1898,
    "completion_tokens": 64
  }
}

Closed in favor of https://github.com/h2oai/lmdeploy/pull/3


community-operators [R] opendatahub-operator (0.6.0 0.6.1 0.7.0 0.8.0 0.9.0 1.0.0 1.0.10 1.1.0)

Signed-off-by: Landon LaSmith<EMAIL_ADDRESS>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 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

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

Operator Description must contain (in order)

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

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] 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

Hi @LaVLaS,
Your new bundle is using deprecated/removed API(s) in 1.22/ocp 4.9.  We would like to recommend you migrate your project and start to publish new distributions as soon as possible and only if not possible to do that then, configured as described in https://github.com/operator-framework/community-operators/blob/master/docs/packaging-required-criteria-ocp.md your bundle.
IMPORTANT: You must ensure that your users will have operator versions compatible available in the previous versions and before 4.9.
c/c @jozzi @dmesser @mvalarh

/merge possible


Import hack, copy testing scripts from knative/client

The important requirement is to have a ./test/presubmit-tests.sh for Prow (see https://github.com/knative/test-infra/pull/2840). I did this by importing the current knative/client minimal-ish set of files, which includes go test and verifying cross-compilation.
/assign @lance @rhuss
/hold
Happy to re-arrange this some other way; I'd like both lance and roland to review. :grin:

Thanks !
Oops, that's quite a mouthful of a PR (and my browser has a hard time opening the files view :)
The build script and CI integration are kind of unique how kn is built. It can definitely be reused for other projects and some plugins do. But we don't want to enforce that and as func comes already with its own way of building, I think we should integrate the Prow CI hook-scripts into the existing build system.
I'm also not clear whether there should be an interplay with the Github Actions based CI and Prow CI, and whether we should switch one of them or use both. Using the Prow CI has the advantage that it is integrated with the Prow workflow (/ok-to-test, /retest commands), Github actions have better support from the GitHub UI.
We should decide which road to go, but as mentioned I can't review this PR in a finite amount of time (because of my very sluggish Chrome that can't show 5000+ files in one view)

PR #419 contains a few updates to the existing CI of func, and is awaiting the CLA label but is otherwise ready to merge. It uses GitHub Actions so is a bit more lithe at a total of 450 lines.  Is that func-specific set of scripts usable, or could it be with some modification?

I don't understand what this PR is meant to do, and at 5000+ files I don't really know how to review it. As I mentioned in https://github.com/knative/test-infra/pull/2840#discussion_r670562725 we have done a lot of work to date to get our CI working, and I am concerned about dropping that simply to satisfy prow/tide. Rather than landing this, I think it would be great if we can identify what the goals are first, and then find a (hopefully less massive) way to achieve them.

/close
We'll use the existing actions-based tooling for now.


Is there a quick test case to verify a wasm runtime support range of WASI undefined functions?

There are two list of undefined functions in wasi-libc

one for wasm-wasi
one for wasm-wasi-thread

IMO, a Wasm runtime announces to fully support WASI/WASI-thread should be able to provide all host implementations about `__imported_wasi_snapshot_preview1_XXX. Either via runtime itself(like WAMR) or via third-party(like uvwasi or cargo-wasi)
It would be able to verify the combability of variant versions WASI if there is a test. I understand the ultimate goal of was-testsuite is to verify that. But for now, Is there a quick check only about the range?

Hi @lum1n0us , you're right, the goal is to verify:

completeness
correctness

of WASI implementation in the runtime. At the moment there's no way (at least in wasi-testsuite) to just verify if the function is supported (either correctly or incorrectly) by the runtime; once we have a full coverage, you should be able to to do that, but we still miss a number of functions in test suite.
I'd keep this issue open so as part of this ticket we can implement a set of a sanity checks that hopefully satisfy your requirement short term.


new_issue doesn't work in organization project

I have 2 identical projects.
one at the repo level,
one at the organization level.
they both have the same automation card:
###### Automation Rules

<!-- Documentation: https://github.com/philschatz/project-bot -->

- `new_issue` **c1-frontend-v4**
- `unassigned_issue`

The one on the repo level works just fine. When I create a new issue, it automatically gets assigned to the project in the right column.
However, nothing happens in the organization project."
The repository is private.
The organization project is private.
I have tried setting the organization project to public, but that did not help.
I have tried removing the repo name and just use this:
 - `new_issue`

I have tried prefacing the repo name with the org name
 - `new_issue` **my_org/c1-frontend-v4**

I have tried renaming the organization project (they both had the same name before)
our organization has 29 open project boards. (I saw 1 comment in another issue, regarding that project bot might only recognize the first 10 boards?) - could be related.
Interestingly enough, while new issues do not appear on the board. If I use other automation rules like assigning, or labels. Those automation work just fine once I have manually added the ticket to the board.
Any idea why new_issue does not work on the organization level?

Any update on this issue? I would like to use the bot but it needs to support Org projects. Thanks.

I works for me on an organisation project, that's the first thing I tried.


grpcio 1.3.5 silent exit when used together with multiprocessing and subprocess

Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker?
Yes
Create new issues for bugs and feature requests. An issue needs to be actionable. General gRPC discussions and usage questions belong to:

grpc.io mailing list
StackOverflow, with grpc tag

Please don't double post your questions in more locations, we are monitoring both channels and the time spent de-duplicating questions can is better spent answering more user questions.
What version of gRPC and what language are you using?
grpcio 1.3.5 python
What operating system (Linux, Windows, …) and version?
Ubuntu 14.04.1
What runtime / compiler are you using (e.g. python version or version of gcc)
python 2.7.6
What did you do?
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
I updated grpcio 1.0.1 to 1.3.5
What did you expect to see?
I expected to see my program run the same.
What did you see instead?
What I do is basically use both subprocess.Popen and  MyProtoStub(grpc.insecure_channel('ip:port')) within a multiprocessing.Process. When I both call Popen and create stubs, the Process will exit silently without any exception or error message. Only calling Popen or creating Stub won't cause this issue. The Process exits when calling Popen.communicate() or creating a new Stub when the two are both already seen in the code.
Before upgrading grpcio to 1.3.5 I was using 1.0.1 which didn't have this issue. I down graded to grpcio 1.0.1 and the issue disappeared.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?

gRPC Python doesn't yet support forking but I can't tell if that's quite the issue here. Are you able to share sample code that demonstrates this behavior?


Make it work in the browser

Is it possible?
I believe that it would need to be implemented using browserify.

Yes, it works in the browser. The dist/ directory contains a browserified bundle that can be loaded via a script tag. I've been testing it with the 'kanban' app and can successfully replicate data between Chrome and Firefox.
Clearly the documentation can be improved to show how to integrate things.

If you share the build command with me, i can document it and send you a pull request.

The script is in the package.json and browserify bundle can be updated simply by running "npm run browserify".

Also there is a bower package, so one can also "bower install pouch-replicate-webrtc --save" to install it.

Do you have your browser test arround? I couldn't find it in the repo and, as we don't have require in the browser as we have on NodeJS, I don't know how to import the library in Clientside code to show a simple example in the docs.


Add 24 hour earnings chart to hotspot details

adds 24 hour earnings chart, and adds time ranges to tooltips in both earnings charts:

🔥

maybe more of a design question, but maybe we could have some UI to toggle between [24h, 7d, 30d] time periods on these earnings charts? that way we don't have 2-span widgets stacking up and also would keep the api calls down

I thought about that too.
something like this:


How to get all role permissions

Hi,
is there a way to get all role permissions?
I tried $role->permissions(), but this method returns null.
Thanks,
Mihai

$role->permissions;
or
$role->permissions()->get();

Can i run this $role->permissions()->get() for the user's permissions?
Like $user->permissions()->get();


Fehler in Adroid?

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.803
Where did you get the app from?
Google Play
Android version
nein
Device model
Samsung A53
Steps to reproduce
K-9 öffnen > Gemeinsamer Posteingang erscheint > Mailliste wird angezeigt > Mail durch Anklicken anzeigen > "GESAMTE NACHRICHT HERUNTERLADEN" anklicken > Ein leeres Mail mit «Unbekannter Absender» an mich, (KEIN BETREFF) wird generiert und das ursprüngliche Mail ist verschwunden.
Expected behavior
Das ursprüngliche Mail komplett herunterladen und Anzeigen.
Actual behavior
Ein leeres Mail mit «Unbekannter Absender» an mich, (KEIN BETREFF) wird generiert und das ursprüngliche Mail ist verschwunden.

Logs
No response

If you translate your issue to English (either by hand or by using a translator) more people will be able to understand it.
Falls du dieses Issue ins Englische übersetzt (manuell oder per Übersetzer), werden mehr Leute es verstehen können.
Apart from that you seem to be one version behind, it might already have been fixed.

Please provide a debug log. See https://github.com/thunderbird/thunderbird-android/wiki/LoggingErrors

@Grommanos: Your issue seems to be about an error in communication with the crypto provider and thus different from what was reported here initially. Please open a new GitHub issue and provide as much context as possible. How did you configure the app? What are the steps to reproduce the issue? What exact error message is displayed? Please also attach the debug log to that issue.

If I click on an email and select "DOWNLOAD ENTIRE MESSAGE", an empty email is generated with "Unknown Sender" and the delivered email then disappears. This can be seen at the very end in the attached debug file with the date 06-13 00:16.47.
k9mail-logs.txt

It looks like your mail server sends an empty response when K-9 Mail is asking for the complete contents of this message. Can I ask who your provider is?

Hello
This is GMX.
Greatings
Erich
am Montag, 17. Juni 2024 um 12:40 schrieben Sie:

It looks like your mail server sends an empty response when K-9 Mail is asking for the complete contents of this message. Can I ask who your provider is?

--
Mit freundlichen Grüssen
Erich Tanner
@.***

I think we would have gotten more reports if there was a general problem with K-9 Mail accessing GMX accounts. So I'm guessing it's something about this particular message. Using the web interface, can you please create a new folder and move that message into it. Then with debug logging enabled, sync that folder using K-9 Mail. Afterwards, press the button to download the complete message again. Please post the debug log here (it can't be attached via email; you need to use GitHub's web interface).
If possible, please also post the message source here (feel free to redact any sensitive information, but try to retain the structure).


LSNBLDR-701 created Lessons component to show latest announcements.

Added new dialog for Announcements in ShowPage.html ,related variables
and function are added in 'SimplePageBean.java' to create/edit
SimplePageItem of type ANNOUNCEMENTS for Announcements summary widget.
'messages.properties' is edited to add new texts.
For merged announcements, if user has no access to the site get public
messages from the site.Added method 'getMessagesPublic' to fetch all
public messages from the channel.

Basically OK. However I'd rather not having you store anything the html attribute. General the HTML in ShowPageProducer. It looks to me like the same line of code would work there. The concern is that if we ever want to change the way the output is formatted, it's easier to do that if the HTML is generated on the fly than if we've got a bunch of stored HTML that has to be fixed.

I have removed html from the stored item and now will be created on the fly for the widget. I have updated PR with the latest code.


Extra indentation in the navigation bar causing text to wrap

Platform
Website
Issue
The indentation in the navigation bar on the left should be close to 0. This is in main but isn't deployed yet (go to the adaptive cards ci url to repro).

If this doesn't repro on the main site this may be a recent-ish regression.

@JeanRoca - can you take a look at this?

Addressing this issue is not currently on our roadmap, so closing. Please feel free to continue the conversation in this issue for future consideration.


Fix printToPDF on chromium56

fix https://github.com/brave/browser-laptop/issues/7416
Auditors: @bridiver, @bbondy, @bsclifton

Use RenderFrameHost instead of RenderViewHost
(https://chromium.googlesource.com/chromium/src.git/+/cb959ce66a9a89b6f100795bb33292439a7ed7de)
Add scaleFactor for check in https://chromium.googlesource.com/chromium/src.git/+/56.0.2924.87/printing/print_settings_conversion.cc#187
(https://chromium.googlesource.com/chromium/src.git/+/769ffdf779d83399a6f219e2637c6469ab94da0e
Add correct HostID & RountingID for CreatePrinterQuery
(https://chromium.googlesource.com/chromium/src.git/+/56.0.2924.87/chrome/browser/printing/printing_message_filter.cc#267)

++

Did a fresh compile last nite and tested- works great! 😄  ++!


[flash_ctrl] PHY CONTROLLER ARBITRATION IS NOT WORKING AS EXPECTED

When parallel  host reads and controller programs
are sent, everything what controller send is accepted without any arbitration. Operations are done on same bank and both starting on address 0 (but until controller program, addresses diverge).

thanks Nikola, if you can let me know how to reproduce, I will have a look.

Branch: https://github.com/nikola-miladinovic/opentitan/tree/flash_ctrl_phy_arb_issue.
Seed 1 on Xcelium ( i would say any seed is valid since test is passing)

o sounds good. So just run any test and look at the waveforms when they're targeting the same bank, is that right?

@nikola-miladinovic
I ran a test and looked at the waves, this actually looks like it's working as expected to me.

If you look at the above diagram, it's captured from one of the completed tests.
You'll see that the device is currently doing host reads while another controller request is going at the same time. Every time the host read completes (host_req_rdy_o) The arbitration count increments because the controller has "lost".
After the count gets to 4, the host request is dropped (host_req_masked) to ensure the controller has a chance to complete.  You then see prog_done_o go high, indicating the controller activity has completed, at which point the count also goes back to 0.  Now the host reads are favored again compared to the pending program, and the arbitration count starts to tick.
Let me know which part didn't seem right to you, it would be great if you show a wave also.

Tim, thanks for explanation. I was confused since at Core TL Interface, I saw posted transactions from controller. Now I have updated this branch so that you can see how i manage to invoke at same address controller program and host read and also i have added check that host read data lost priority and read what was written by controller. Unfortunately, scoreboard and three tests need to be updated. I will open small PR for that (handling non blocking host reads) which would be needed to be merged first.

thank you @nikola-miladinovic
if all seems right to you, feel free to close the issue.


On-board LocationBasedServices

removing this as there has been no reaction/comments on this for over a year. Please open a new issue if this is of interest


Scope jaeger sampling model in model/sampling

Coverage remained the same at 100.0% when pulling 51555fbeafb39c3e618d1cb683a1387126380c72 on scopetings into 59504fb385497fda0e6807c9c90724a6fdf4fd79 on master.

still, similar question - why is it in the main model, and not somewhere local like ../sampling/model/?  The main model package is the shared model.

I'd rather not pollute the root directory namespace if we can help it, pkg/sampling/model.go ok with you?

I was not suggesting the root  (hence ../sampling). Where is the main logic for adaptive sampling going to live? Isn't it under cmd/collector/app/sampling?

Coverage remained the same at 100.0% when pulling f785eb7b9e0e7d767362f38fc5b46bc3501052ba on scopetings into 59504fb385497fda0e6807c9c90724a6fdf4fd79 on master.

Coverage remained the same at 100.0% when pulling 4c337b09aa082f4296597f315ccb2fc3dbb626d4 on scopetings into 59504fb385497fda0e6807c9c90724a6fdf4fd79 on master.

Coverage remained the same at 100.0% when pulling f925db5bef4963afd02d29b520b3d34869ec40a8 on scopetings into 59504fb385497fda0e6807c9c90724a6fdf4fd79 on master.

Coverage remained the same at 100.0% when pulling be57932a93e72908a8a47d40677292e0ba8b0057 on scopetings into 5b70b1822483434b46a506ce4d7708a8896e24d1 on master.


Issue #SH-640 fix: Added toast message and template change detection modal

Please have the unit test cases added before it goes to preprod


Fixed bug causing Collapse Containers to display all their items expa…

…nded when multiple exist on the same page

This seems like a good place to have a test...

One day...


Switch from dependabot to renovate?

According to @dzikoysk, we can get renovate to bump with more than 1 dep update at a time, which would be great:

We can also get Dependabot to do it: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#groups
Imo installing a third party dependency manager with similar functionality is undesirable if we can use built-in GitHub tooling.
@dzikoysk are there any other missing features that would make it worth switching?

If we can do this in dependabot, then I would prefer not switching.

@dzikoysk are there any other missing features that would make it worth switching?

The dashboard is nice, because you can trigger it directly before a release, so you can just get rid of a lot of PRs in the first place.