vicuna v1.1 version

Thank you for the great work.
On the fastchat page it only lists v1.3 now. https://github.com/lm-sys/FastChat#model-weights
How could we get the vicuna v1.1 version?
Also, is this delta-v1.1? or not delta?
Thanks!

I was able to get InstructBLIP-Vicuna versions running with these weights:

https://huggingface.co/TheBloke/vicuna-13B-1.1-HF
https://huggingface.co/TheBloke/vicuna-7B-1.1-HF

The original weights can still be found here: https://github.com/lm-sys/FastChat/blob/main/docs/vicuna_weights_version.md
But the original weights are delta weights which have to be merged whereas the weights I provided above are the merged weights so it is less of a hassle to use those. I would recommend using them.

Thank you so much @vishaal27
I am trying https://huggingface.co/TheBloke/vicuna-13B-1.1-HF
However, I met this error message:
Traceback (most recent call last):
File "instructBlip.py", line 23, in
model, vis_processors, _ = load_model_and_preprocess(
File "/mnt/cache/LAVIS_NEW/LAVIS/lavis/models/init.py", line 200, in load_model_and_preprocess
model = model_cls.from_pretrained(model_type=model_type)
File "/mnt/cache/LAVIS_NEW/LAVIS/lavis/models/base_model.py", line 70, in from_pretrained
model = cls.from_config(model_cfg)
File "/mnt/cache/LAVIS_NEW/LAVIS/lavis/models/blip2_models/blip2_vicuna_instruct.py", line 707, in from_config
model = cls(
File "/mnt/cache/LAVIS_NEW/LAVIS/lavis/models/blip2_models/blip2_vicuna_instruct.py", line 68, in init
self.Qformer, self.query_tokens = self.init_Qformer(
File "/mnt/cache/LAVIS_NEW/LAVIS/lavis/models/blip2_models/blip2.py", line 54, in init_Qformer
Qformer = BertLMHeadModel.from_pretrained(
File "/home/aiscuser/.local/lib/python3.8/site-packages/transformers/modeling_utils.py", line 2604, in from_pretrained
state_dict = load_state_dict(resolved_archive_file)
File "/home/aiscuser/.local/lib/python3.8/site-packages/transformers/modeling_utils.py", line 461, in load_state_dict
return safe_load_file(checkpoint_file)
File "/home/aiscuser/.local/lib/python3.8/site-packages/safetensors/torch.py", line 261, in load_file
result[k] = f.get_tensor(k)
RuntimeError: shape '[768]' is invalid for input of size 96
I have downloaded the vicuna-13B-1.1-HF weights and stored it here:

I have changed the yaml file accordingly:

Any idea of what is going on is appreciated. Thanks!

upgrading torch to 2.0 as well as transformers solves the issue

https://huggingface.co/TheBloke/vicuna-13B-1.1-HF

does it improve performance for your upgrading weight to vicuna-v1.3 ?


[Fixes] Minor doc fixes as well as removed Metal delegate for iOS

Minor fixes for the documentation, as well as review for the comments from @PaulTR in PR #107
@PaulTR

Metal delegate removed.
There is nothing to do with imageFormatGroup, it is related to CameraController, and default value set for each platform:  bgra8888 for iOS and yuv420 for Android
Orientation - not fixed.
Minor fixes in the docs, typos

What I have noticed, Android delegate also could be removed, at least for pixel it works perfectly, cant say anything about other devices.

Xiaomi Redmi 9 also works without delegate, and maybe add the path for the app to the .vscode-workspace file.
Also, i dont know if you remember, but I think we met at fluttercon on wednesday morning before it even started. I was the one with the long hair 😅

Also, i dont know if you remember, but I think we met at fluttercon on wednesday morning before it even started. I was the one with the long hair 😅

Nice! Are you going to be at the Flutter Firebase Festival in Prague next month as well?

@PaulTR unfortunately not

@PaulTR  I will be there, but I will land Prague around 11 AM, and will be there around lunch time. So can hangout later, after your talk


Some tests on Windows fail with ProcessNotRegisteredError

When building the package for conda, the following tests in tests/test_cmake_config.py fail on Windows:

test_cmake_paths
test_init_cache
test_cmake_args

at
config.configure()

with error ProcessNotRegisteredError:
Running e.g.:
pytest -vv -ra --showlocals -k "test_cmake_args"

...
            if not cls.process_list[-1]._allow_unregistered:
>               raise exceptions.ProcessNotRegisteredError(
                    "The process '%s' was not registered."
                    % (
                        command
                        if isinstance(command, str)
                        else " ".join(str(item) for item in command),
                    )
                )
E               pytest_subprocess.exceptions.ProcessNotRegisteredError: The process '%PREFIX%\Library\bin\cmake.EXE -S%SRC_DIR%\tests\packages\simple_pure -BC:\Users\buildu.

cls        = <class 'pytest_subprocess.process_dispatcher.ProcessDispatcher'>
command    = ['C:\\Users\\builidusername\\miniconda3\\envs\\c3i\\conda-bld\\scikit-build-core_1722583656353\\_test_env\\Library\\bin\\cmake.EXE',
 '-SC:\\Users\\builidusername\\miniconda3\\envs\\c3i\\conda-bld\\scikit-build-core_1722583656353\\test_tmp\\tests\\packages\\simple_pure',
 '-BC:\\Users\\builidusername\\AppData\\Local\\Temp\\pytest-of-builidusername\\pytest-86\\test_cmake_args0\\build',
 '-DCMAKE_BUILD_TYPE:STRING=Release',
 '-DSOMETHING=one']
command_instance = None
process_instance = None
processes  = None
...

full log: scikit-build-core-0.9.9-pytest.log
Something is not working with the parameters in the registration of the commands here:
https://github.com/scikit-build/scikit-build-core/blob/715777d94d57ab0f9ae158f8690d609356a69753/tests/test_cmake_config.py#L140
https://github.com/scikit-build/scikit-build-core/blob/715777d94d57ab0f9ae158f8690d609356a69753/tests/test_cmake_config.py#L110
https://github.com/scikit-build/scikit-build-core/blob/715777d94d57ab0f9ae158f8690d609356a69753/tests/test_cmake_config.py#L56
as a test, if I replace *cmd with fp.any() to ignore the parameters, the registration works and the three tests pass.
On other platforms (linux, darwin) these three tests pass.
I could not determine if it was a \\ problem or something else.
scikit-build-core version: 0.9.9 or 0.9.8
Python: 3.8 to 3.11
Windows: 11
pytest-subprocess: 1.5.0
cmake: 3.26.4
Compiler: vs2019 win-64

The versions of the dependencies would be useful in this case. It seems that fp.program didn't expand the executable path correctly.
Maybe can also check on https://github.com/conda-forge/scikit-build-core-feedstock, there the tests don't seem to be covered properly

Thank you for your fast reply!
Apologies, here is the list of the dependencies used in the test environment:
    attrs:              23.1.0-py312haa95532_0
    blas:               1.0-mkl
    bzip2:              1.0.8-h2bbff1b_6
    ca-certificates:    2024.7.2-haa95532_0
    cattrs:             23.1.2-py312haa95532_0
    cmake:              3.26.4-h693b641_0
    colorama:           0.4.6-py312haa95532_0
    distlib:            0.3.8-py312haa95532_0
    editables:          0.3-py312haa95532_0
    expat:              2.6.2-hd77b12b_0
    filelock:           3.13.1-py312haa95532_0
    hatch-vcs:          0.3.0-py312haa95532_1
    hatchling:          1.21.1-py312haa95532_0
    iniconfig:          1.1.1-pyhd3eb1b0_0
    intel-openmp:       2023.1.0-h59b6b97_46320
    libffi:             3.4.4-hd77b12b_1
    libuv:              1.48.0-h827c3e9_0
    lz4-c:              1.9.4-h2bbff1b_1
    markdown-it-py:     2.2.0-py312haa95532_1
    mdurl:              0.1.0-py312haa95532_0
    mkl:                2023.1.0-h6b88ed4_46358
    mkl-service:        2.4.0-py312h2bbff1b_1
    mkl_fft:            1.3.8-py312h2bbff1b_0
    mkl_random:         1.2.4-py312h59b6b97_0
    ninja:              1.10.2-haa95532_5
    ninja-base:         1.10.2-h6d14046_5
    numpy:              1.26.4-py312hfd52020_0
    numpy-base:         1.26.4-py312h4dde369_0
    openssl:            3.0.14-h827c3e9_0
    packaging:          24.1-py312haa95532_0
    pathspec:           0.10.3-py312haa95532_0
    pip:                24.0-py312haa95532_0
    platformdirs:       3.10.0-py312haa95532_0
    pluggy:             1.0.0-py312haa95532_1
    pybind11:           2.12.0-py312h59b6b97_0
    pybind11-global:    2.12.0-py312h59b6b97_0
    pygments:           2.15.1-py312haa95532_1
    pyproject-metadata: 0.7.1-py312haa95532_0
    pyproject_hooks:    1.0.0-py312haa95532_0
    pytest:             7.4.4-py312haa95532_0
    pytest-subprocess:  1.5.0-py312haa95532_0
    python:             3.12.4-h14ffc60_1
    python-build:       0.10.0-py312haa95532_0
    rich:               13.7.1-py312haa95532_0
    scikit-build-core:  0.9.9-py312h0158946_0      local
    setuptools:         69.5.1-py312haa95532_0
    setuptools-scm:     8.1.0-py312haa95532_0
    sqlite:             3.45.3-h2bbff1b_0
    tbb:                2021.8.0-h59b6b97_0
    tk:                 8.6.14-h0416ee5_0
    trove-classifiers:  2023.10.18-py312haa95532_0
    tzdata:             2024a-h04d1e81_0
    vc:                 14.2-h2eaa2aa_4
    virtualenv:         20.26.1-py312haa95532_0
    vs2015_runtime:     14.29.30133-h43f2093_4
    vs2019_win-64:      19.29.30154-h96f319f_4
    vswhere:            2.8.4-haa95532_0
    wheel:              0.43.0-py312haa95532_0
    xz:                 5.4.6-h8cc25b3_1
    zlib:               1.2.13-h8cc25b3_1
    zstd:               1.5.5-hd43e919_2

There is a more recent version of pytest-subprocess:  1.5.0 but It does not seem to have changes regarding the expansion of the executable path: https://github.com/aklajnert/pytest-subprocess/compare/1.5.0...1.5.2

Indeed. From what I see in the CI jwlawson/actions-setup-cmake is used to setup cmake on the windows CI. Hopefully there's nothing funky there where it strips the .exe suffix and we are not covering that. We are also using vanilla windows runners though so it shouldn't be the case. 🤔

The thing that looks weird to me is the un-expanded environment variables. %PREFIX%\Library\bin\cmake.EXE instead of C:\\Users\\builidusername\\miniconda3\\envs\\c3i\\conda-bld\\scikit-build-core_1722583656353\\_test_env\\Library\\bin\\cmake.EXE. If pytest-subprocess is just comparing strings, those are not the same string.

The scikit-build-core feedstock only tests Linux, as it's hard to get it to test pure-Python feedstocks on macOS and Windows.

Could you try https://github.com/scikit-build/scikit-build-core/pull/844 ?

Could you try #844 ?

I did try it. It did not work.
I believe the expansion might happen but with this problem: https://github.com/conda/conda-build/issues/4264#issuecomment-1050817754
Or some other thing weird is happening.
If I have:
    print("---config.source_dir-----")
    print(str(config.source_dir))
    print(repr(config.source_dir))
    print("--------")

    for c in configure_args(config):
        print(str(c), "****", repr(c))
    print("--------")

    cmd = [os.fspath(c) for c in configure_args(config)]
    print("---cmd-----")
    print(cmd)
    print("--------")
    print("---*cmd-----")
    print(*cmd)
    print("--------")

I will see printed:
---config.source_dir-----
%SRC_DIR%\tests\packages\simple_pure
WindowsPath('C:/Users/lorepirri/miniconda3/envs/c3i/conda-bld/scikit-build-core_1722646771709/test_tmp/tests/packages/simple_pure')
--------
-S%SRC_DIR%\tests\packages\simple_pure **** '-SC:\\Users\\lorepirri\\miniconda3\\envs\\c3i\\conda-bld\\scikit-build-core_1722646771709\\test_tmp\\tests\\packages\\simple_pure'
-BC:\Users\lorepirri\AppData\Local\Temp\pytest-of-lorepirri\pytest-104\test_cmake_args0\build **** '-BC:\\Users\\lorepirri\\AppData\\Local\\Temp\\pytest-of-lorepirri\\pytest-104\\test_cmake_args0\\build'
--------
---cmd-----
['-SC:\\Users\\lorepirri\\miniconda3\\envs\\c3i\\conda-bld\\scikit-build-core_1722646771709\\test_tmp\\tests\\packages\\simple_pure', '-BC:\\Users\\lorepirri\\AppData\\Local\\Temp\\pytest-of-lorepirri\\pytest-104\\test_cmake_args0\\build']
--------
---*cmd-----
-S%SRC_DIR%\tests\packages\simple_pure -BC:\Users\lorepirri\AppData\Local\Temp\pytest-of-lorepirri\pytest-104\test_cmake_args0\build
--------

Oh yeah forgot about that azure/conda "feature". They just replace in the generated log the known values of environment variables. It does not make things confusing at all 😑.

So the two strings are different?

Ah, we are seeing the same string twice, and it's replacing one of them. We aren't told what has been registered here.

How hard is it to set up in CI?

We could run a modified version of conda-build next week to disable that annoying log replacement and see if we can get the real paths.

Thank you all for helping out!
I found the problem. I apologize I got hallucinated by the nice conda feature and thought that the problem was in the expansion of the path, and I stopped there.
I am also grateful for the truncated log that conda build offers us.
There is a parameter too much: -DCMAKE_BUILD_TYPE:STRING=Release
The function configure_args  in the tests that is used to prepare the arguments does not consider that there might be a CMAKE_GENERATOR set in the environment (and I have it set to Ninja, for good or bad):
https://github.com/scikit-build/scikit-build-core/blob/901b1d31d9b7b47ee93aa2ef6f887c15e82e7f7a/tests/test_cmake_config.py#L21-L30
The configure() in src/scikit_build_core/cmake.py mutates single_config just right before calling the Run(...).live(...)
https://github.com/scikit-build/scikit-build-core/blob/901b1d31d9b7b47ee93aa2ef6f887c15e82e7f7a/src/scikit_build_core/cmake.py#L210-L212
I tested this code in tests/test_cmake_config.py and it works:
def configure_args(
        config: CMaker,
        *,
        init: bool = False,
        defines: Mapping[str, str | os.PathLike[str] | bool] | None = None,
        cmake_args: Sequence[str] = (),) -> Generator[str, None, None]:
    yield f"-S{config.source_dir}"
    yield f"-B{config.build_dir}"

    _cmake_args = config._compute_cmake_args(defines or {})
    all_args = [*_cmake_args, *cmake_args]

    gen = config.get_generator(*all_args)
    if gen:
        single_config = gen == "Ninja" or "Makefiles" in gen

    if (single_config or config.single_config) and config.build_type:
        yield f"-DCMAKE_BUILD_TYPE:STRING={config.build_type}"

    if init:
        cmake_init = config.build_dir / "CMakeInit.txt"
        yield f"-C{cmake_init}"

I don't know if it's the best solution for you. One might think of extracting the part leading to mutating self.single_config into another method and using that from the tests.
If it is, please let me know and I will fix the PR with this change.
On the other hand, it might not be ideal to have the environmental variable CMAKE_GENERATOR set for testing.

I think we probably should monkeypatch the test to remove the envvar. If it’s important, we could also make a new or parameterized test with the envvar set. You generally don’t want a test to depend on the environment and run differently.

I think we probably should monkeypatch the test to remove the envvar. If it’s important, we could also make a new or parameterized test with the envvar set. You generally don’t want a test to depend on the environment and run differently.

Thank you @henryiii.
PR #847 should set things right for this particular problem. Let me know if the solution is acceptable.

Is this fixed in the latest release?

Yes, thanks for working on it and merging it!


Updating openshift velero plugin to support multi-arch builds

Updated openshift velero plugin to use the new konveyor/builder image to support multi-arch builds

I know I acked this already, but looking at it again, are we sure we want to replace the run image too rather than just the build image? It does build successfully, but do we want to go away from running ubi8-minimal?

+1 with Scott, please only change the builder image, not the runner image


Added discord-markdown to the dependencies

This is 1st the wrong version and 2nd it is included in matrix-discord-parser with the correct version


Add internal documents to the flexibee extractor

I added part with internal documents (+details of them).
I also changed the URL string, as now the flexible has a slightly different one.

@ondrejhlavacek - pls can you have a look? :)

@mtrunkatova tThanks for the update. I could not find any information about the changed URL. The official documentation still points to /c/ - https://podpora.flexibee.eu/cs/articles/4713911-sestavovani-url.

@ondrejhlavacek - you re right, it should stand the same! sorry for the confusion :)

I have no access to any Flexibee account, did you try modifying any of your existing configurations with the new endpoints? Current configurations can be switched to JSON mode where you can test what it does before submitting it to the template.
Thanks!

@ondrejhlavacek I have modified the JSON, but it didnt work so I created a generic extractor which works.
flexibee_internal_documents.txt
.

Hi @mtrunkatova, do you still want to update the template? I can help you with but I would need access to a Keboola project with a working Flexibee extractor so I can try modifying the current template.

@ondrejhlavacek yes please! provide me your email address and I ll add you!

@mtrunkatova<EMAIL_ADDRESS>


pid selector for window rules (V2)

Description
Being able to target a specific window with a window rule using its pid would be really nice.
Currently, dynamic window rules are broken with the exec dispatcher because the dispatcher sets them only once, and as per the wiki: "dynamic window rules are re-evaluated every time a property changes" (for example changing the focus of the spawned window) which discards the rule set by the dispatcher (see https://github.com/hyprwm/Hyprland/issues/6593).
Under the hood, the exec dispatcher could set the dynamic window rules for the created window with the proposed pid selector which would fix this issue.
The pid selector would also fix https://github.com/hyprwm/Hyprland/issues/4648

use hyprctl setprop

Ah I just found out that setprop supports pid
But its not mentioned anywhere.
On the hyprland wiki it only says in the example
hyprctl setprop address:0x13371337 forcenoanims 1 lock  # with locking
hyprctl setprop address:0x13371337 nomaxsize 0          # without locking

and hyprctl only gives this information
➜  ~ hyprctl setprop --help
usage: hyprctl [flags] setprop <regex> <property> <value> [lock]

regex:
    Regular expression by which a window will be searched
...

Do you know what selection options are available? Then I will add this to the wiki

that's not a pid, it's the window address (aka the hex value at the start of hyprctl clients after 0x)
see the getWindowByRegex in src/Compositor.cpp for all the options
PHLWINDOW CCompositor::getWindowByRegex(const std::string& regexp) {
    if (regexp.starts_with("active"))
        return m_pLastWindow.lock();

    eFocusWindowMode mode = MODE_CLASS_REGEX;

    std::regex       regexCheck(regexp);
    std::string      matchCheck;
    if (regexp.starts_with("class:")) {
        regexCheck = std::regex(regexp.substr(6));
    } else if (regexp.starts_with("initialclass:")) {
        mode       = MODE_INITIAL_CLASS_REGEX;
        regexCheck = std::regex(regexp.substr(13));
    } else if (regexp.starts_with("title:")) {
        mode       = MODE_TITLE_REGEX;
        regexCheck = std::regex(regexp.substr(6));
    } else if (regexp.starts_with("initialtitle:")) {
        mode       = MODE_INITIAL_TITLE_REGEX;
        regexCheck = std::regex(regexp.substr(13));
    } else if (regexp.starts_with("address:")) {
        mode       = MODE_ADDRESS;
        matchCheck = regexp.substr(8);
    } else if (regexp.starts_with("pid:")) {
        mode       = MODE_PID;
        matchCheck = regexp.substr(4);
    } else if (regexp.starts_with("floating") || regexp.starts_with("tiled")) {
        // first floating on the current ws
        if (!valid(m_pLastWindow))
            return nullptr;

        const bool FLOAT = regexp.starts_with("floating");

        for (auto& w : m_vWindows) {
            if (!w->m_bIsMapped || w->m_bIsFloating != FLOAT || w->m_pWorkspace != m_pLastWindow->m_pWorkspace || w->isHidden())
                continue;

            return w;
        }

        return nullptr;
    }

that's not a pid, it's the window address (aka the hex value at the start of hyprctl clients after 0x)

Yeah I know. I just found out that hyprctl setprop pid:<...> ... works.
Thanks! The snippet helps. Will make a MR for the wiki :)

for me still didn't worked :(, if i toggle the special workspace, the transparency would be lost..
bind = $mainMod SHIFT, o,exec, hyprctl setprop pid:$(hyprctl activewindow -j | jq .pid) alpha 0.8

```

setprop has been moved from hyprctl to the dispatchers in this MR https://github.com/hyprwm/Hyprland/pull/8275.
So please try the dispatcher instead. Also you might try locking the rule.
@MightyPlaza why have you removed a lot of the documentation of the setprop command in this MR https://github.com/hyprwm/hyprland-wiki/pull/832? You have only copied the prop list over but not the rest. Did you change something in the underlying code such that the documentation wasn't true anymore? Otherwise I think having the rest of the documentation in the wiki is very much needed. Else there is no mention anywhere of

what locking does
how the modes work
where to find window address etc

locking doesn't exist anymore, I removed it a while ago but didn't notice it was still in the wiki
the modes where removed since they're just duplicated from window parameters
address is what appears in hyprctl clients with 0x in front
bind = $mainMod SHIFT, o,setprop, active alpha 0.8

Thanks for the explanation!
In the wiki's window parameters there is only a mention of:
"activewindow an active window"
(Does this mean the first active window?)
Is active the same as activewindow?
This should also be mentioned then somewhere I think.

it's anything that starts with active
see
PHLWINDOW CCompositor::getWindowByRegex(const std::string& regexp_) {
    auto regexp = trim(regexp_);

    if (regexp.starts_with("active"))
        return m_pLastWindow.lock();
    else if (regexp.starts_with("floating") || regexp.starts_with("tiled")) {
        // first floating on the current ws
        if (!valid(m_pLastWindow))
            return nullptr;

        const bool FLOAT = regexp.starts_with("floating");

        for (auto const& w : m_vWindows) {
            if (!w->m_bIsMapped || w->m_bIsFloating != FLOAT || w->m_pWorkspace != m_pLastWindow->m_pWorkspace || w->isHidden())
                continue;

            return w;
        }

        return nullptr;
    }

    eFocusWindowMode mode = MODE_CLASS_REGEX;

    std::regex       regexCheck(regexp_);
    std::string      matchCheck;
    if (regexp.starts_with("class:")) {
        regexCheck = std::regex(regexp.substr(6));
    } else if (regexp.starts_with("initialclass:")) {
        mode       = MODE_INITIAL_CLASS_REGEX;
        regexCheck = std::regex(regexp.substr(13));
    } else if (regexp.starts_with("title:")) {
        mode       = MODE_TITLE_REGEX;
        regexCheck = std::regex(regexp.substr(6));
    } else if (regexp.starts_with("initialtitle:")) {
        mode       = MODE_INITIAL_TITLE_REGEX;
        regexCheck = std::regex(regexp.substr(13));
    } else if (regexp.starts_with("address:")) {
        mode       = MODE_ADDRESS;
        matchCheck = regexp.substr(8);
    } else if (regexp.starts_with("pid:")) {
        mode       = MODE_PID;
        matchCheck = regexp.substr(4);
    }

Thanks! :)


Reading custom tags in BAM file

I wonder if one can read custom tags in BAM files using bionumpy. I want to read PacBio-specific tags

Not as of now, but we will add support for it soon

Do you have a small example bam file with PacBio specific tags you could send me to use for development @ikramu ?


Simple Numeric Formatting - How?

I have a money object with some amount in it. I want to put this into a form field so it can be edited, or put into a report to tabulate. In both cases I need the amount appropriately formatted, with a decimal point and trailing zeroes where needed, but no currency symbol. How would this be achieved?
I'm just looking for the quick conversion between what is stored, and what a human would write the amount down as (without adding the currency symbol) in both directions.

Just a simple (string)$myMoney would be nice.

@judgej Do you use the 1.x stable or the 3.x upcoming version?
In the upcoming version we are working hard on making Money as easy to use as possible.
What you are trying to achieve is quite hard, since the amount is internally stored in integer format, which means Money (Currency) should be aware of the subunit. We tried to avoid this and make the value objects as simple and flexible as possible. Right now we are working on a formatting solution which involves a separate formatter object and a currency repository.
Casting the Money object to string could be a nice addition, but I guess everyone would expect a different result: just the amount, amount with currency, amount with currency symbol, etc.

I started on 1.3 b but have moved to the 3.x beta.
So the currency here is not aware of the size of the subunit? I thought I was going mad when I couldn't find it. To have to keep that information separate from the currency itself seems to defeat half the object of this library.
Humans and currency exchange services rates work in major units and minor units. Computers can work largely in minor units. Accounts like to work in fractions of minor units. Being able to easily move between these forms is what is going to make this library much more useful.

So the currency here is not aware of the size of the subunit?

No, this library never did that. The main reason was that currencies themselves does not necessarily have minor units (although most physical currencies have).
Right now we are thinking about two possible solutions:

We already have the term of currency repository which contains basic and meta information for whatever currency you would like to use (see #223)
The other possibility is to add subunit support to the currency object itself. However, there are two problems with that:

You would have to create currency objects like new Currency('EUR', 2)
Convenient Money::EUR(123) factories wouldn't work anymore

Also, this makes the creation of a money object rather hard: new Money(123, new Currency('EUR', 2)) In this case, is the input amount €123 or €1.23?
Minor units are actually useful if you want to format the amount. Using 1 or 100 for calculations doesn't matter, it only matters when you want to output the value.
This is a major problem we are aware of and blocks the 3.0 version, but there is no nice solution for this:

Adding minor units makes many things complicated
Not adding it makes the library harder to use

I'm trying to write decorators for some of the features I need to wrap around Money, since it cannot be extended dues to the use of final. The problem is, without an interface, the decorators cannot be type-hinted, which is a bit of a pain. If they are type-hinted against Money class, then the decorators cannot be nested, which is one of the reasons for using decorators.
I am really growing to dislike the final keyword...

What's your usecase for decorators?

I need the money object to be castable to a string, for use in a form. The form renderer will take any data type, so long as it will cast to s string. So [GBP, 120] will cast to a string as "1.20".
Also would like an easy formatter for displaying the value in display screens, so $money->format() on [GBP, 120] will give me "£1.20".

This is a quite common use case, which I also have. I suggest you reading @webmozart's post about: https://webmozart.io/blog/2015/09/09/value-objects-in-symfony-forms/ (given you are using symfony).
I don't think adding formatter logic to the VO is a good idea, it should be handled by an external service.

Hmm, the Form Model Accessors in the Laravel Collective HTML form generator bound to a model is supposed to be able to handle transformations, but it seems it's only on L5.2 and I'm on L5.1 (https://laravelcollective.com/docs/5.2/html#form-model-binding). I'll dig into how it works to see if it can be used in a similar way.

I don't think adding formatter logic to the VO is a good idea, it should be handled by an external service.

👍 I think, that translation between VO and string representation are responsibilities of a formatter and a parser.
But may be useful to return some string representation for logging or for debugging.
For example
$money = new Money(10000, new Currency('USD'));
echo (string) $money;

prints:
 [Money\Money: amount=10000 currency=USD]

or
[Money\Money: amount=10000 currency=[Money\Currency: code=USD]]

I need the money object to be castable to a string, for use in a form. The form renderer will take any data type, so long as it will cast to s string.

Infrastructure or framework should not affect design of the model.
@judgej I am sure, that exist some another way to resolve your issue without modification of Money. If framework, which you use, does not provide some ability to implement form transformer, you can use DTO for aggregating information from a form. Then you can transform data from DTO to your model and vise versa.

But may be useful to return some string representation for logging or for debugging.

We already have something similar: JSON serializability.

Infrastructure or framework should not affect design of the model.

:100: :+1:

@judgej I am sure, that exist some another way to resolve your issue without modification of Money.
If framework, which you use, does not provide some ability to implement form transformer, you can use
DTO for aggregating information from a form.
Then you can transform data from DTO to your model and vise versa.

I should correct myself. It's better to use PRESENTATION MODEL pattern.

There are two good methods here using a presenter model. The latter could lose precision due to using float, but doable.

Assuming bcmath is available
```php
use Money\Money;
class MoneyPresenter {
/** @var Money $money */
private $money;
public function __construct(Money $object) {
$this->money = $object;
}
public function amount() : string {
    return bcdiv($this->money->getAmount(), 100);
}

}
</details>

<details>
<summary>If bcmath isn't available, return a float and round it on the frontend.<summary>
```php

use Money\Money;

class MoneyPresenter {
    /** @var Money $money */
    private $money;

   public function __construct(Money $object) {
        $this->money = $object;
    }

    public function amount() : float {
        return $this->money->getAmount() / 100;
    }
}

Presenting as a string is important here, as floats don't have trailing zeros.
My solution is to create an accessor on my eloquent model to make sure it always returns the underlying integer in the database as a Money object. Matching mutators then make sure a Money object can be passed back in for saving.
I've creating a macro in Laravel to present the money amount in form for editing. The macro extends the Laravel Collective form package. That formats it nicely and puts a currency symbol in the field as a bootstrap icon.
{!! Form::money('my_money_field', null, ['class' => 'form-control']) !!}

When just displaying, I have an application helper. The helper just displays the amount as a string with a currency symbol:
{{ \AppHelper::formatMoney($model->my_money_field) }}

Now, then submitting a form in Laravel, the input is given directly to the model, which means it is a string. The model mutator is clever enough to accept either a Money object or a string, which it then parses into Money for saving.
I'm sure there is a layer somewhere in the laravel form handling that should be able to take certain input data in certain contexts and parse it into a Money object before my model even sees it, but I've not found where that would be. I'm guessing not middleware, because the middleware does not have the context of what is being POSTed - it would not know what should be parsed and what should be left alone.
Anyway, I have a end-to-end solution that works, though does feel kind of bodged and clunky. I think perhaps that feeling comes from how closely bound form items and database columns are in laravel, so data to and from the browser tends to be treated as text or numbers all the way to the database. Maybe a DTO layer would help here? Not sure. Anyway, I'm walking that fine line between learning the best and proper way to do things, and trying to get the project out the door, hence my original question, and why I'm happy with my solution even if it does feel a little clunky to me.

You can format either of the presenters I posted however you wish. I just did the math as the example, but you can do a currency format in there. As well as another method to get a string of the integer out with trailing zeros. Give bcmath functions some precision, and you'll have trailing zeros in your output.
Laravel doesn't provide a "layer" for this. It is one you'd need to implement on your own. Accessors/Mutators are typically exactly what this is for.

Issue solved by merging PR today.

This has been a little bit improved again, see #289. I am thinking about some quick setup code since in many cases ISOCurrencies are used for everything. Although that's convenience stuff, it would live outside the domain, so it's kind of okay.


Update error

Expected behavior:
Upgrade to 3.0.4-beta.20.1
Actual behavior:
Upgrade from 3.0.4-beta.19 to 3.0.4-beta.20.1 fail
Upgrade stuck with: You must be logged in to access that page.
If I try to log in with another tab, error:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbs36862.ti_staff_roles' doesn't exist (SQL: select * from ti_staff_roles where 0 = 1)

Use issues to report bugs, please post your questions on the forums or better still search the forums for existing solutions.


[Question] Unexpected results

I have the following in python:
import struct

a = 0x95006c08
print( a & 0x3FF )           # First: 10 bits  --> 8
print( (a >> 10) & 0x1FFF )  # Second: 13 bits --> 27

And I am trying to do the equialent with binaryparse:
import binaryparse
import streams

createParser(p):
  10: a
  13: b

var
  a = 0x95006C08
  s = newStringStream()

s.write(a)
s.setPosition(0)

var tmp = p.get(s)
echo tmp.a  # --> 33 (instead of 8)
echo tmp.b  # --> 2688 (instead of 27)

What am I doing wrong? I am looking to replicate python's results.
By the way, binaryparse is AWESOME. I love it.

There are a couple issues here. First s.write(a) will write a with the wrong byte order from what you seem to expect. If you create a parser that has 32: a and then put the value through that into the stream it will be in the same order as binaryparse expects it to be. Second of is that binaryparse reads from left to right so to speak. So you need to skip the first 9 bits before you can read first the 13 and then the 10. But while looking into this I've discovered that binaryparse has two bugs. I've pushed a fix for the first one, so what I wrote above should work now. But the other one is a bit harder to squash, so you might run into some strange behaviour.
To be honest binaryparse could do with a complete rewrite, the code is complete spaghetti and super hard to debug.. But I'll try to patch it over for now.

But @PMunch... there is already a rewrite :3

I wasn't aware of the existance of binarylang. It actually solved my problem. Thanks for the info.


add tailscale-vpn starter

This PR adds the tailscale-vpn starter.

Hey @es183923, I am closing this PR as we've restructured how we manage templates. Do you mind creating an issue using the updated instructions in the README and re-submitting the template? :)


Supporting more large LLMs

I notice that some config yml files of large LLMs are placed in data\model_configs, however only meta-llama/Llama-2-70b-hf and microsoft/phi-2 can run successfully by editing default.yml file and running command 'python -m simulator.main' on my computer. I am sure that the virtual environment has been successfully configured exactly as the readme.md file. I plan to execute the scripts for LLMs with more than 30B parameters. Calling for supports.
Here's my default.yml file:
seed: 42
log_level: info
output_dir: ./simulator_output/
cache_dir: ./cache
write_json_trace: false
write_chrome_trace: true
write_metrics: true

cluster:
  num_replicas: 1

replica:
  block_size: 16
  memory_margin_fraction: 0.1
  num_pipeline_stages: 1
  num_tensor_parallel_workers: 1
  model_name:  meta-llama/Llama-2-70b-hf
  device: a100

request_generator:
  provider: synthetic
  max_tokens: 4096

synthetic_request_generator:
  length_provider: trace
  interval_provider: poisson
  min_tokens: 1024
  prefill_to_decode_ratio: 10
  num_requests: 128

trace_request_generator:
  trace_file: ./data/processed_traces/sydney_enterprise.csv
  date: '2023-08-21'
  prefill_scale_factor: 0.3
  decode_scale_factor:  1
  time_scale_factor: 0.04

# Config for synthetic trace generator
trace_request_length_generator:
  trace_file: ./data/processed_traces/arxiv_summarization_stats_llama2_tokenizer_filtered_v2.csv
  prefill_scale_factor: 1
  decode_scale_factor:  1

trace_request_interval_generator:
  trace_file: ./data/processed_traces/AzureFunctionsInvocationTraceForTwoWeeksJan2021Processed.csv
  start_time: "1970-01-04 12:00:00"
  end_time: "1970-01-04 15:00:00"
  time_scale_factor: 0.3

poisson_request_interval_generator:
  qps: 0.5

gamma_request_interval_generator:
  cv: 0.5
  qps: 0.2

zipf_request_length_generator:
  theta: 0.4
  scramble: false

fixed_request_generator:
  prefill_tokens: 2048
  decode_tokens: 512

execution_time_predictor:
  provider: random_forrest
  # provider: linear_regression

sklearn_execution_time_predictor:
  compute_input_file: ./data/profiling/{DEVICE}/mlp.csv
  attention_input_file: ./data/profiling/{DEVICE}/attention.csv
  all_reduce_input_file: ./data/profiling/{DEVICE}/all_reduce.csv
  send_recv_input_file: ./data/profiling/{DEVICE}/send_recv.csv
  cpu_overhead_input_file: ./data/profiling/{DEVICE}/cpu_overheads.csv
  k_fold_cv_splits: 10
  no_cache: false
  kv_cache_prediction_granularity: 64
  prediction_max_prefill_chunk_size: 4096
  prediction_max_batch_size: 128
  prediction_max_tokens_per_request: 4096
  attention_decode_batching_overhead_fraction: 0.1
  attention_prefill_batching_overhead_fraction: 0.1
  nccl_cpu_launch_overhead_ms: 0.020
  nccl_cpu_skew_overhead_per_device_ms: 0.0
  num_training_job_threads: -1
  skip_cpu_overhead_modeling: false

random_forrest_execution_time_predictor:
  num_estimators:
    # - 250
    - 500
    - 750
  max_depth:
    # - 8
    # - 16
    - 32
  min_samples_split:
    - 2
    - 5
    - 10

linear_regression_execution_time_predictor:
  polynomial_degree:
    - 1
    - 2
    - 3
    - 4
    - 5
  polynomial_include_bias:
    - true
    - false
  polynomial_interaction_only:
    - true
    - false
  fit_intercept:
    - true
    - false

simulator:
  time_limit: 0 # in seconds, 0 is no limit

global_scheduler:
  provider: round_robin

replica_scheduler:
  provider: sarathi
  batch_size_cap: 128
  num_blocks: null

orca_scheduler:
  use_single_prefill_per_batch: false

vllm_scheduler:
  watermark_blocks_fraction: 0.01
  max_tokens_in_batch: 4096

sarathi_scheduler:
  chunk_size: 512
  enable_rolling_prefills: true
  prefill_fitting_tolerance: 0.0
  watermark_blocks_fraction: 0.01

lightllm_scheduler:
  max_tokens_in_batch: 4096
  max_waiting_iters: 10

metrics_store:
  wandb_project: "llm-simulator-v2"
  wandb_group: ""
  wandb_run_name: ""
  subsamples: null
  save_table_to_wandb: false
  store_plots: true
  store_operation_metrics: false
  store_token_completion_metrics: false
  store_request_metrics: true
  store_batch_metrics: true
  store_utilization_metrics: true
  keep_individual_batch_metrics: false
  # min_batch_idx: 2000
  # max_batch_idx: 5000

and here's what i got with model_name meta-llama/Llama-2-70b-hf :

@Daniel-ChenJH thanks a lot for your interest in the project. We are working on improving the documentation and fixing some gaps in the profiled data available. We do have llama 70b profiling data, but it is only recorded for tensor parallel degree 4. Can you please try that config? Thanks!

@Daniel-ChenJH thanks a lot for your interest in the project. We are working on improving the documentation and fixing some gaps in the profiled data available. We do have llama 70b profiling data, but it is only recorded for tensor parallel degree 4. Can you please try that config? Thanks!

Thanks for your timely help! Setting num_tensor_parallel_workers: 4 in yml file works fine for me with llama 70b. Are there any other restrictions for each of the LLMs supported in the project? I would appreciate it if any relevant explanation could be given.

There aren't any fundamental limitations. Just some rough edges related to the completeness of profiling data in terms of model/sku/parallel combination. We plan to support all sku and parallelism combinations for at least a core set of 5-10 models. With additional community supported data that might contain only a subset of this. We are working on ironing out the core model set and setting up process for community contributions + documentation.

@Daniel-ChenJH now you should be able to all tensor parallel combinations! We have also updated the docs, please have a look and share any feedback you have!


Kernel Panic - macOS Ventura 13.2.1 - crash log included

Hello,
both on Monterey (12.6.1) and Ventura (13.2.1) I suffer from 'random' kernel panics. Kernel Panics appear to be random. Don't see a correlation with heavy use; happens during casual use and sometimes a couple of minutes after login.
System info:
Matebook x pro 2018 Mach-W29C
Intel Core i7-8550U @ 1,8GHz
16GB DDR3 RAM
512GB SSD
It appears to be related to NVMe controller. I added my crashlog, config.plist and NVMExpress device tree.
Except for the 'random' kernel panics, everything else such as WiFi, Bluetooth, Sound, Touchscreen etc works flawlessly.
Hoping that someone with more knowledge on this topic can point me to the right direction.
NVMExpress device tree.txt
config.plist.zip
Crashlog.txt

Hey, would you mind specifying which NVME drive is your matebook X pro? is
it LiteON
On Sun, Mar 26, 2023 at 2:19 PM LevelAdditional79 @.***>
wrote:

Hello,
both on Monterey (12.6.1) and Ventura (13.2.1) I suffer from 'random'
kernel panics. Kernel Panics appear to be random. Don't see a correlation
with heavy use; happens during casual use and sometimes a couple of minutes
after login.
System info:
Matebook x pro 2018 Mach-W29C
Intel Core i7-8550U @ 1,8GHz
16GB DDR3 RAM
512GB SSD
It appears to be related to NVMe controller. I added my crashlog,
config.plist and NVMExpress device tree.
Except for the 'random' kernel panics, everything else such as WiFi,
Bluetooth, Sound, Touchscreen etc works flawlessly.
Hoping that someone with more knowledge on this topic can point me to the
right direction.
NVMExpress device tree.txt
https://github.com/tlefko/Matebook-X-Pro-2018-Ventura/files/11072599/NVMExpress.device.tree.txt
config.plist.zip
https://github.com/tlefko/Matebook-X-Pro-2018-Ventura/files/11072525/config.plist.zip
Crashlog.txt
https://github.com/tlefko/Matebook-X-Pro-2018-Ventura/files/11072527/Crashlog.txt
—
Reply to this email directly, view it on GitHub
https://github.com/tlefko/Matebook-X-Pro-2018-Ventura/issues/42, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKHES3HIMNIINT64TZKC7NDW6CJERANCNFSM6AAAAAAWIKPKOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hey, would you mind specifying which NVME drive is your matebook X pro? is it LiteON
…

Stock SSD --> KXG50ZNV512G TOSHIBA.

@LevelAdditional79 Disable NVMEFix in the config.plist and try this. apparntly there is a conflict between 3rdpartyNVME and NVMEFix. Also, if it doesn't work try using this version of NVMEFix and re-enabling it.


Attach existing buffer archive

replicate buffer tags to storage as metadata (limits?)
multiple storage accounts
attach as read-only account
rescan/reimport (async operation)

OR
(better)

database export of buffers from a storage account (filtered)
and database import (upsert)
read-only storage account

Implemented in #141


testport -I -k still kills jails if they fail early

Prerequisites

[x] Have you checked for an existing issue describing your problem?
[x] Are you running the latest version?
[x] Is your ports tree recent?
[ ] Is your FreeBSD Host on a supported release?

Describe the bug
When poudriere testport -I -k encounters a failure during pkg-depends, it still kills jails, rather than leaving them up like described in the man.
How to reproduce
Steps to reproduce the behavior:

poudriere testport -I -k -j somejail -p sometree ports-mgmt/poudriere
https://github.com/freebsd/pkg/issues/1965

[00:00:16] Error: Depends failed to build
[00:00:16] Failed ports: ports-mgmt/dialog4ports:pkg-depends misc/freebsd-release-manifests:pkg-depends lang/perl5.32:pkg-depe
nds
[00:00:16] Skipped ports: security/ca_root_nss
[00:00:16] Cleaning up
[00:00:16] Unmounting file systems

Expected behavior
The jails should remain running so that pkg.core can be recovered.
Screenshots
NA
Environment

Host OS [e.g. 12.2 amd64]: 1400030
Jail OS [e.g. 12.0 powerpc]: 1400030
Browser: [e.g. chrome, safari]: NA
Poudriere Version [e.g. 3.3.1 or git hash or port version]: 3.3.6
Ports branch and revision [e.g. 2020Q3 r550754]: fd649cf02561

In your example testport is for ports-mgmt/poudriere not for its dependencies.  This is working as intended.

No, this is not the expected behavior. This is a failure, and referencing the man page:
     -k		  Do not consider failures as fatal.  Find all failures.

This should not have been considered fatal and based on this, with -i or -I the jail should remain running.
If this isn't a bug in poudriere, then the man deserves an explanation.

Again -k is for the port being tested.
The top line of the manpage is poudriere testport – test a given port's build. Everything applies to that statement unless otherwise specified. Nothing about testport is testing dependencies. It's been like this since 2010.


The FillMode doesn't seem to work on Android

I have a single Video component inside a grid on the main page. Using Chill Player as the example.  No matter what value this is set, the video (using included video.mp4) always stretches.  I realized that there's a default Width and Height set to the component, so specifying HorizontalOptions and VerticalOptions as Center reveals this. If I set those explicitly (e.g. 400x100), the video stretches to those dimensions regardless of the value of FillMode.

There are some workarounds for this but it is a well-known and unfortunately not easy to address issue. Android is just not very nice when it comes to supporting aspect ratios properly. You can checkout this issue below for more detail on some potential tweaks that could be made:
https://bitbucket.org/OctaneSoftware/octane.xam.videoplayer/issues/2/android-fillmode-video-resolution-appears

Is there any way I can get access to that link? its telling my access denied.. I have the same issue and its quite frustrating to pay and a keyfeature like this is not working.

Sorry, the issue queue was migrated to GitHub and didn't want people posting there. This solution is originally from Dominik Weber but has not been integrated since testing has shown there are still some stability issues but YMMV.
class VideoPlayerExtRenderer : VideoPlayerRenderer
    {
        protected override void OnElementChanged(ElementChangedEventArgs<VideoPlayer> e)
        {
            base.OnElementChanged(e);

            if (e.NewElement != null)
            {
                Control.Prepared += (s2, e2) =>
                {
                    UpdateVideoSize();
                    Control.Player.VideoSizeChanged += (s3, e3) => UpdateVideoSize();
                };
            }
        }

        protected override void OnLayout(bool changed, int l, int t, int r, int b)
        {
            base.OnLayout(changed, l, t, r, b);

            UpdateVideoSize();
        }

        private void UpdateVideoSize()
        {
            if (Element.FillMode == FillMode.Resize)
            {
                Control.Layout(0, 0, Width, Height);
                return;
            }

            // assume video size = view size if the player has not been loaded yet
            var videoWidth = Control.Player?.VideoWidth ?? Width;
            var videoHeight = Control.Player?.VideoHeight ?? Height;

            var scaleWidth = (double)Width / (double)videoWidth;
            var scaleHeight = (double)Height / (double)videoHeight;

            double scale;
            switch (Element.FillMode)
            {
                case FillMode.ResizeAspect:
                    scale = Math.Min(scaleWidth, scaleHeight);
                    break;
                case FillMode.ResizeAspectFill:
                    scale = Math.Max(scaleWidth, scaleHeight);
                    break;
                default:
                    // should not happen
                    scale = 1;
                    break;
            }

            var scaledWidth = (int)Math.Round(videoWidth * scale);
            var scaledHeight = (int)Math.Round(videoHeight * scale);

            // center the video
            var l = (Width - scaledWidth) / 2;
            var t = (Height - scaledHeight) / 2;
            var r = l + scaledWidth;
            var b = t + scaledHeight;
            Control.Layout(l, t, r, b);
        }
    }

WARNING: this code is not heavily tested, so if you want to use it please run some tests first. Might need some null checks for Element and Control properties.
I have called UpdateVideoSize and attached the VideoSizeChanged event handler in the VideoView.Prepared event, but you might want to find a better place to put these calls, ensuring the Player property is set BEFORE Player.VideoSizeChanged is set. UpdateVideoSize also should be invoked when the FillMode property is changed to resize the video.
Applying a custom layout to the video view will cause a transparent background on the letterbox area, which can be solved by setting the background color of the VideoPlayer XForms view to black (maybe set this as default to be consistent across platforms?)

A version of Dominik's code was included in 1.2.1 but I'm thinking it only works for simple scenarios based on my testing. IllegalStateExceptions seem to be the most common issue in 1.2.1 if orientation changes happen at incorrect times and the video width is retrieved.
The incremental fix mentioned in my previous comment has been removed in 1.2.2 as it caused issue another issue. Dominik's code has been very helpful but I have found not to work in every case.
Since this appears to be native/platform behavior I will leave it as optional if users wish to incorporate the code mentioned above as a solution to see if it works for their specific case. Any future updates to the Android platform will be monitored for changes to support a resolution for this issue

It looks like there were some efforts to fix this in 2017, but I am still running into this issue. What is the recommended resolution for preserving the aspect ratio on Android?

I am experiencing this as well.  I tried implementing the custom renderer above, but it isn't being picked up.  I don't think I'm doing it wrong.  I've got several custom renderers in my project.  But none of the events are firing - like I forgot to put in the ExportRenderer statement or something.

@hauteur Same here; paid for the plugin, and still waiting for a response

I cannot use this plugin because it doesnt show video in proper ratio. Please fix it.

Fork to code, include in your solutions and add above code https://github.com/adamfisher/Xamarin.Forms.VideoPlayer/issues/3#issuecomment-324187000 to your Droid renderer, worked for me.

The above code worked for me too.


[Completion] Complete .isolation for @isolated(any) functions

This was added in SE-0431.
rdar://124615036

@swift-ci please test

@swift-ci please test


Indexing the last N-1 elements of  a 1D tensor raises a "stop condition" error.

Environment info
Operating System:
OSX 10.11.6

The output from python -c "import tensorflow; print(tensorflow.__version__)".

0.10.0rc0
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
I'm trying to select the last N-1 element of a 1D tensor with N elements, for the array [0,1,2,3,4] I'm trying to extract [1,2,3,4]
x = tf.convert_to_tensor([0,1,2,3,4])
b = x[:tf.shape(x)[0]-1]

Logs or other output that would be helpful
File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/array_ops.py", line 313, in _SliceHelper
if s.stop is not None and s.stop < 0:
File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 529, in nonzero
raise TypeError("Using a tf.Tensor as a Python bool is not allowed. "
TypeError: Using a tf.Tensor as a Python bool is not allowed. Use if t is not None: instead of if t: to test if a tensor is defined, and use the logical TensorFlow ops to test the value of a tensor.
(If logs are large, please upload as attachment or provide link).

Sorry for the noise, before posting this issue I had searched for hours, however just now I found the solution to my problem -and I'm not sure the issue I've raised is an actual bug or not-
b = tf.slice(x, [1], [-1])


Add content to the Architecture page

Description:
Adding documentation on the architecture of the Streaming Integration profile.
Suggested Labels:
Streaming-Integration docs
Affected Product Version:
EI 7.0.0
Link
https://github.com/wso2/docs-ei/blob/master/en/streaming-integrator/docs/overview/architecture.md

Completed this for the EI 7.0.0 release.


Allow location where to save downloaded files

Is your feature request related to a problem? Please describe.
It would be nice to specify where to download the files
Describe the solution you'd like
Add dst_path keyword to download_file()
Additional context
Not related, but do you know why the requests.get step is VERY slow? Does it depend on Zenodo server?

This is a great suggestion. this has now been implemented. There may be a more elegant solution, but this works:
 def download_file(self, filename=None, dst_path=None):
        """download a file from project

        Args:
            filename (str): name of the file to download
            dst_path (str): destination path to download the data (default is current directory)
        """
        if filename is None:
            print(" ** filename not supplied ** ")

        key = self._get_key()

        # parameters
        params = {'access_token': key}

        bucket_link = self.bucket

        if bucket_link is not None:
            if validate_url(bucket_link):
                r = requests.get(f"{bucket_link}/{filename}",
                                 params=params,
                                 )

                # if dst_path is not set, set download to current directory
                # else download to set dst_path
                if dst_path is None:
                    wget.download(r.url) if r.ok else print(f" ** Something went wrong, check that {filename} is in your poject  ** ")
                elif os.path.isdir(dst_path):
                    cwd = os.getcwd()
                    os.chdir(dst_path)
                    wget.download(r.url) if r.ok else print(f" ** Something went wrong, check that {filename} is in your poject  ** ")
                    os.chdir(cwd)
                else:
                    raise FileNotFoundError(f'{dst_path} does not exist')
            else:
                print(f' ** {bucket_link}/{filename} is not a valid URL ** ')


[e2e] [Chrome] [Peers] After reinstall plugin can't observe bottom line when no peers.

Version: 2.0.7

Can't reproduce on pre-release version 2.0.9 -rc1


change(db): Use smaller keys for height and transaction indexes

Motivation
In #3152, we want to store heights and transaction indexes using fewer bytes on disk.
If we use 3 bytes for heights, and 2 bytes for transaction indexes, we can store address locations using 8 bytes. This makes those indexes much more efficient.
Consensus Limits
3 byte heights allow us to store blocks for 30 years.
2 byte transactions support up to 5 MB blocks, the current limit is 2 MB.
Designs
https://github.com/ZcashFoundation/zebra/blob/main/book/src/dev/rfcs/0005-state-updates.md#rocksdb-data-structures
We only discard zero bytes while serializing.
(If they are non-zero, I made the code panic, but blocks with those heights won't be valid until 2050.)
Solution
Database:

Store heights in 3 bytes on disk
Store transaction indexes in 2 bytes on disk
Increment the database format version

The snapshot tests show that the raw data changes, but the typed data doesn't. So this is only a disk format change.
Monitoring:

Log an error if we ever get close to the maximum on-disk height

Testing:

Update database raw data snapshots for 3 byte heights and 2 byte transaction indexes
There are already tests for large heights, large transaction indexes
PR #3879 finished the snapshot tests for all the typed block, transaction, and UTXO data

Closes #3152.
Review
This is a routine database change, it's not urgent, and it's not blocking anything.
This PR is based on PR #3879.
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work
Make output locations smaller - this needs a new database column family, so I'll do it in #3151.

@teor2345 could we actually do a review of this PR in sync?

@teor2345 could we actually do a review of this PR in sync? ( I requested some trivial changes so that the PR doesn't get merged in the meantime.)

Sure, did you want to do that at our meeting this week, or schedule another time?
I'm free after the ZIP sync tomorrow.

Looks good! I liked how the snapshots show that it's only a disk format change.

Yep, that was the plan!
I'm going to do the same thing for #3151, because it's a large data format change, but none of the high-level Zebra types should change.

I'm wondering about this, just out of curiosity:

If we use 3 bytes for heights, and 2 bytes for transaction indexes, we can store address locations using 8 bytes. This makes those indexes much more efficient.

Is there any particular reasoning about this? Of course smaller is better, but is there some guideline from RocksDB motivating this change, or something like that?

8 bytes is the native integer size on 64-bit machines, so key comparisons can be performed with a single processor instruction.
Maybe RocksDB isn't quite that efficient, but it's still very likely to be faster than larger keys.
(I would have used larger keys if needed, or smaller keys if possible. But once I got to 8 bytes, it wasn't worth bit-packing to squeeze an extra byte out.)
Also, going from 12 to 8 byte keys saves us hundreds of megabytes on disk, because we expect to have:

1.6 million blocks x 2 column families
tens of millions of transactions x 3 column families
tens of millions of transparent outputs x 3 column families

Also we'll have 20 years to fix the database after the warning, so that seems enough 🤣

This warning is just in case we switch to a very short target block interval. (Like 1 block every second.)
Even at that rate, we'd still have a few months to do a fix. (And we'd have a lot of other problems.)

The macOS test failed because either:

our parameter downloads are being rate-limited, or
our download code suddenly became very very slow.

Most likely it's rate-limiting, so I'm not going to restart this job yet.

@mergifyio refresh

@mergifyio update

@Mergifyio update


SNOW-872425: Unable to add packages with version specifier when the package name contains underscore

Please answer these questions before submitting your issue. Thanks!

What version of Python are you using?
Python 3.8.13

What operating system and processor architecture are you using?
macOS-13.4.1-arm64-arm-64bit

What are the component versions in the environment (pip freeze)?
snowflake-snowpark-python==1.5.1

What did you do?
Create a session. Then run session.add_packages("huggingface_hub==0.15.1")

What did you expect to see?

The package should be able to be added as it is available by checking information_schema.packages table.
What should have happened and what happened instead?
Instead, received
ValueError: Cannot add package huggingface_hub==0.15.1 because it is not available in Snowflake. Check information_schema.packages to see available packages for UDFs. If this package is a "pure-Python" package, you can find the directory of this package and add it via session.add_import(). See details at https://docs.snowflake.com/en/developer-guide/snowpark/python/creating-udfs.html#using-third-party-packages-from-anaconda-in-a-udf.

Can you set logging to DEBUG and collect the logs?

I believe the issue lies here https://github.com/snowflakedb/snowpark-python/blob/edd7f29d10215eab8b3725d524551f1c164c3745/src/snowflake/snowpark/session.py#L904 When incoming package contains underscore, it takes the whole package specification as the package name, which incorrectly contains the version specification part.

I can repro, assigned to myself since I need to clean up the deprecating dependencies on pkg_resources.


SM-856 - unit test

bump - want to merge this on Monday if no additional observations.

Don’t have time to look. Merge away.


Add optional tabulate dependency

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

Project coverage is 100.00%. Comparing base (73dbb10) to head (e33737a).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #96   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           56        58    +2
  Lines         1026      1067   +41
  Branches        78        83    +5
=========================================
+ Hits          1026      1067   +41

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


Harden error handling for Web Service Methods

Things like Putting without an ID, creating empty objects etc.
Make sure REST best practices are being followed.

Also clean up according to pylint as much as possible.

We now have specific tickets for each of the methods, so this is just for the app and node_modules directory.


0.1.0: Create basic Eclipse e4 application skeleton

Target: https://github.com/hexatomic/hexatomic/pull/13

[x] Create Eclipse e4 skeleton app that can be built with Tycho, including multi-platform build artifacts and custom target platform
[x] Add docs for auto-deployment to hexatomic.github.io/hexatomic (user + dev/maintainer docs)
[x] Add CI support (testing on PRs (@thomaskrause to discuss where CI should kick in), building and deploying) via Travis
[ ] Document

* [ ]  Add CI support (testing on PRs (@thomaskrause to discuss where CI should kick in), building and deploying) via Travis

From what I see CI is already working on pull requests (e.g. #22) and produces meaningful feedback.

* [ ]  Automate deployment via CI

I think this should not be part of this particular PR since we can already build the product locally. Waiting for this PR to be merged is a major blocker for actual feature development, and automatic CI deployment is not needed for development, but only for release of a public product release. Even a source code release without automatic CI deployment could be possible.

Automated deployment via CI moved to #23.

Closing due to uselessness.


Graph reference server, starter batch

graph reference server initial code, consisting of endpoints:
sequences/search, joins/search, sequences/{id}/bases, allele/{id}

Making this public at long last. Have fun @jeromekelleher @dcolligan


replace serde with a simple trait + macro for Streamable

this patch drops the dependency on serde and implements just the Streamable support we need (and that the Streamable protocol supports).
This has the following advantages:

We need a macro to generate the python binding tying the serde serializer and deserializer. This code is about as large as the whole Streamable-support after this patch. So, this patch removes a lot of code (mostly boiler plate).
Implementing a serializer and deserializer for serde requires compile-time support for a lot of types that we don't support in the Streamable format. e.g. floating point and dictionaries. Running serialization through serde turns errors that should be compile-time errors into runtime errors (i.e. the NotSupported run-time error is produced in a bunch of  places). With this patch, marking a class as Streamable containing unsupported types is a compile error with this patch
Going forward, we'll need one more "serializer" that computes the sha256 hash of the Streamable representation. With this simpler streamable implementation, that's simple to add and doesn't take a lot of code, whereas with serde we would need to duplicate a lot of the boilerplate code from the ChiaSerializer for all unsupported types.
Using a simpler input buffer type and output buffer type (slice + position and Vec<u8>) makes a number of operations more efficient. Especially byte-buffers. With serde sequences need to be serialized one item at a time. With this patch we can just memcopy the buffer directly into the Vec<u8> and out of the slice.
Using a simpler input buffer also allows us to reuse the existing function that computes the length of a CLVM serialized buffer. This is especially handy for creating a rust version of the FullBlock type (which I believe would be an important step towards making the full node more efficient).

One, perhaps, controversial part of this patch is that I made a custom InputBuffer type, that's just a slice + cursor rather than using the Reader trait. Likewise for the output buffer, I use a Vec<u8> instead of the Writer trait. The reason to not use the Reader is explained in the bullet list above, to get direct access to the bytes. The main difficulty with the Writer trait is that its errors are std::io::Error, which is a non-trivial type. It can't be compared equal for instance. Using a simpler output buffer (that cannot fail, since memory allocation isn't an error) both simplifies error handling and also the error type. See the change to the Error enum in this patch.

yeah, I think using Cursor makes sense.

I rebased this on top of latest main to get the test fix in. I also squashed-in the switch to use std::io::Cursor instead of a home-grown class.


Storage models should implement IEquatable

@JoshLove-msft  - can you verify we do this for all of our structs and close the issue if so?

Is this a requirement only for value-type models?

The following structs don't implement IEquatable. Note these are all internal:
From Blobs.Batching csproj:

HashCodeCombiner
InplaceStringBuilder
KeyValueAccumulator
StringTokenizer
StringTokenizer.Enumerator
StringValues.Enumerator

From Common csproj:

ReliabilityConfiguration
Volatile


Add support for custom errorformat

Hi, thanks for this useful plugin.
One thing that has been requested a lot is the ability to navigate to each test error using :cn or :cp (e.g. https://github.com/janko-m/vim-test/issues/14, https://github.com/janko-m/vim-test/issues/67). Although vim-dispatch does open the quickfix window after running a test runner, it doesn't allow us to navigate to each test error for most test runners, it just shows the quickfix window with the whole output of a test runner. This is expected because errorformat is not set correctly, but it makes this plugin less useful.
I think there should be a way to allow users to set their own errorformat for each runner before a test is run, and the errorformat should be reset to its previous value (before running the test) so that other commands can still run correctly (such as :make) because they might use a different errorformat.
My suggestion is to add a new autoload function that returns an errorformat to use. For example we can add the following to autoload/test/php/phpunit.vim:
function! test#php#phpunit#errorformat() abort
  return '%E%n)\ %m,%C%f:%l,%C%m,%C%.%#'
endfunction

And then use its returned value to set errorformat before each test is run. With the above I can get :cn and :cp to work flawlessly.
We can even go further and let users specify their own errorformats for each test runner, similar to how pattern options are set.
Thanks for any consideration.

Thanks for letting me know that this is still a problem. I think we agree that for a quickfix with test errors which can be navigated with :cn or :cp is exactly what dispatch.vim is made for, so we just need to figure out how to add our errorformat to dispatch.vim.
Firstly, the reason why I'm not in favor of making something like test#php#phptunit#errorformat() work is because that would be specific only to the "dispatch" strategy. And I want all vim-test's code to be generic, not tied to a specific strategy.
Now, the solution. Dispatch.vim does set a proper errorformat for some runners, but for some it doesn't, how come? It actually gets the errorformat from a Vim "compiler". A compiler is just a Vim file which specifies which command and errorformat will be used if you type :make (once you previously ran :compiler <name>; see the Elixir's ExUnit compiler as an example).
And dispatch.vim does something really cool around this notion of compilers. Instead of having to manually set a compiler for a test file with vanilla Vim, dispatch.vim allows you to execute a shell command, and what it does is it searches through all compilers that Vim has in its load path (that includes compilers that ship with Vim distribution plus from any extra plugins), and checks if a subset of your command matches the makeprg from the compiler. If it does, it temporarily sets that compiler for that shell command, which applies the errorformat.
So all you have to do to apply the proper erroformat in your case is to create a phpunit compiler (which you would put under ~/.vim/compiler/phpunit.vim), which would look like this:
" ~/.vim/compiler/phpunit.vim
if exists("current_compiler")
  finish
endif
let current_compiler = "phpunit"

let s:cpo_save = &cpo
set cpo-=C
CompilerSet makeprg=phpunit
CompilerSet errorformat=%E%n)\ %m,%C%f:%l,%C%m,%C%.%#

let &cpo = s:cpo_save
unlet s:cpo_save

Now when Dispatch.vim is scanning compilers for a phpunit --filter 'foo' shell command, it will see the the makeprg value of "phpunit" is indeed a subset of your shell command, and should set this compiler for the command.

Actually, I wasn't quite accurate. Dispatch.vim searches if a makeprg matches the "beginning" of your shell command. So a phpunit foo_test.php will be matched, but not e.g. bin/phpunit foo_test.php or vendor/bin/phpunit foo_test.php, which I understood are the executables that are usually used in a PHP project. Dispatch.vim has an option to ignore beginnings of the command, so setting something like this should work with test.vim:
let g:dispatch_compilers = {'./bin/phpunit': 'phpunit', './vendor/bin/phpunit': 'phpunit'}

I see, I was able to get it to work perfectly with your advice too. I guess this should go into vim-test's readme? Could be very useful for other users.
Anyway, thanks again for this awesome plugin. I would rate it one of the best vim plugins ever created!

Another thing to discuss: I figure not everyone wants to use dispatch for this purpose (I actually don't). The issue with :Dispatch is that it returns to vim immediately, which means you can't see how many tests have run, or see if you're running the right test (important when running a single test method). We can toggle the quickfix window  manually, but that's not really intuitive.
The most intuitive strategy IMO is the make strategy, you hit <leader>t, tests run with makeprg set to the test command, you then see success/errors immediately, and then press Enter to return to Vim, with the quickfix window filled with errors if any. If I remember correctly, there was a make strategy.
So it's still great if you could add test#php#phptunit#errorformat(). Although you said that you wanted vim-test to be generic, adding errorformat() looks pretty consistent with the whole plugin (custom file patterns, custom options, etc.)
Hope that makes sense.

You're absolutely right, there should be a make strategy which is a wrapper around Vim's :make. You remember correctly that there was such a strategy before, but the logic was really complex because everything had to be reset afterwards, instead I could've just reused dispatch.vim's functions for finding the right compiler. After I figured out how powerful dispatch.vim is, I removed the strategy because I thought everybody would prefer asynchronous execution. I was wrong, exactly for the advantages you specified, even I use the default synchronous strategy 😃
So, I'm definitely in favour of adding the strategy. However, I would like that it works exactly like Dispatch.vim does in terms of finding the right compiler (and I would add documentation for this). Dispatch.vim actually has a way of running a simple :make (it does it when it cannot run with any other strategy, which can be forced by setting g:dispatch_strategies to []), unfortunately it immediately terminates the screen after executing :make, which we don't want. Maybe I can ask Tim Pope about changing that or adding some option, otherwise I will reimplement what I need to.

Anyway, thanks again for this awesome plugin. I would rate it one of the best vim plugins ever created!

Thank you for such kind words, I'm really happy it's works well for you (although I would at least put it after Tim Pope's plugins in terms of excellence 😉).

So, I'm definitely in favour of adding the strategy. However, I would like that it works exactly like Dispatch.vim does in terms of finding the right compiler (and I would add documentation for this).

That would be great. What I proposed was something I thought would be easiest to implement. I've just checked vim-dispatch's codes, look like there's no public methods that we can utilize to "clone" such functionality.

unfortunately it immediately terminates the screen after executing :make, which we don't want. Maybe I can ask Tim Pope about changing that or adding some option, otherwise I will reimplement what I need to.

Thank you for such kind words, I'm really happy it's works well for you (although I would at least put it after Tim Pope's plugins in terms of excellence).

You're right, but we don't need compare with god-like plugins.


Add checks for README examples and fix typo

You had a small typo in one of your examples, so I fixed it and added a check for it. I added the doc-comment dependency as a dev-dependency.

Hi @GuillaumeGomez, this is super cool! Thanks a lot for the fix and for showing me this technique.


Cross-compiling not working

I am trying to cross-compile uSTL for a Xilinx Zynq development board (ARM processor). The ./configure script claims to be able to cross-compile, but I don't see any of the hooks actually in there.
The command ./configure --with-demangler --force-inline --with-libstdc++ --without-mmx --host=arm-xilinx-linux-gnueabi still builds for the host and never tried to run arm-xilinx-linux-gnueabi-gcc, etc.
It looks like the configure script builds and executes a config.cpu program, which is something that wouldn't work if cross-compiling. The cross-compile library does offer sys/config/h, etc, to parse for capabilities.

#12 is my attempt.

The main branch of uSTL explicitly and vehemently does not support embedded platforms of any kind. Cross-compiling is only needed for embedded platforms, so I have no interest in implementing it.

You might want to cherry-pick 3797a54863533997ebc533430d3592e0e13e9ee0 then. The configure script implied it was possible. That change removes the options from the --help display. I don't know how to send a pull request for that one changeset.
There are a few others that might interest you: d000afe7767a75ebfb90a7deaab1ce9d6241f558 and 28fd0fd3332dd0760fae442c89a165dc6a695654.

3797a54 is reasonable. Merged in commit fa170b13d19ea7b7ab580dc5fd729720d23e5613.
d000afe is rejected. Tests should always be run with make check, not individually, because any library change can impact multiple tests.
28fd0fd is also rejected. The UNIX philosophy is to produce no output when everything is fine.


[SPARK-25016][INFRA][FOLLOW-UP] Remove leftover for dropping Hadoop 2.6 in Jenkins's test script

What changes were proposed in this pull request?
This PR proposes to remove the leftover. After https://github.com/apache/spark/pull/22615, we don't have Hadoop 2.6 profile anymore in master.
Why are the changes needed?
Using "test-hadoop2.6" against master branch in a PR wouldn't work.
Does this PR introduce any user-facing change?
No (dev only).
How was this patch tested?
Manually tested at https://github.com/apache/spark/pull/26707 and Jenkins build will test.
========================================================================
Building Spark
========================================================================
[error] Could not find hadoop2.6 in the list. Valid options  are dict_keys(['hadoop2.7', 'hadoop3.2'])
Attempting to post to Github...

cc @srowen.

Test build #114604 has started for PR 26708 at commit cfc10e5.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19432/
Test PASSed.

Test build #114604 has finished for PR 26708 at commit cfc10e5.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114604/
Test FAILed.

retest this please

Test build #114615 has started for PR 26708 at commit cfc10e5.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19441/
Test PASSed.

Test build #114615 has finished for PR 26708 at commit cfc10e5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114615/
Test PASSed.

Merged to master.


[REQUEST - Feature Update] Better Sorting Algorithm

Implement a faster sorting algorithm for the lib.

The implementation of Timsort will triple the size of the package, for an improvement of 11% in speed. E believe it is not worth it

The implementation of Timsort will triple the size of the package, for an improvement of 11% in speed. E believe it is not worth it


Release Beta Version With FileBot 4.9.5 Beta

I was wondering if you'd be willing to release a beta version of this Docker container with FileBot 4.9.5 Beta.  It looks like FileBot 4.9.5 will bring some new functionality for scripting, especially related to TMDB.  It also requires a newer version of Java than what is bundled with this container and I noticed that the repo for the Java in this container hasn't released any new versions sine 2018 so I'm guessing a new source for the Java package will need to be used.  It's definitely shaping up to be a more major upgrade than the usual ones so I thought a beta release might prove useful.

You are right.  This container is currently using the Java8 version of FileBot.  Unfortunately, for FileBot 4.9.5, this version works for CLI only.   The GUI no longer work.
The main reason why this container was sticking to Java 8 is because of a dependency on JavaFX.  The only Alpine Linux implementation of JFX is for Java 8.
However, I found a way to remove the JavaFX dependency.  So I will release an image with the current FileBot stable version (4.9.4) that runs with Java 17.  This should pave the way for FileBot 4.9.5.

I'm also thinking into adding a mechanism that would allow people to use a beta version with the image.

With the latest Docker image (v1.13.0), Java 17 is used to run FileBot.  We should not have any issue running 4.9.5 when officially released.
Also, you can now use the beta version by using the USE_FILEBOT_BETA variable.  See documentation for more details.


float32 support messed up histogram counts somehow

Posting as a notice for outside users.
https://github.com/facebookresearch/dietgpu/pull/9 introduced an issue where the histogram counts for computing ANS tables seem to be somewhat off the mark from reality. The values are proportionate, but the total sum seems to be 2-4x off of reality, compromising the weights being constructed.
This is not a correctness issue, but instead a coding efficiency and runtime efficiency issue. Am investigating and will fix soon.

fixed in https://github.com/facebookresearch/dietgpu/commit/182ba5aa39643fcf8325e5a3326c0f1c2ffa6ab9


Draft about a MirageOS as a proxy for a SOCKS4 service

This is a draft, we need to upgrade some software like paf to have the ability to manipulate the underlying socket and do the TLS proxy via the HTTP CONNECT request but it's working currently! I did a dune build @fmt too which formats dune files.

Thank you very much! That looks a lot better now, I can even see a lot of ideas that could be reproduced for lwt_socks4_unix.


Bad concordance I don't know why ?

Hello,
I have an issue  :
here is my data  :

the time is the first column and the event is the second column.
I do this code to fit the model :

However i am obtaining a bad concordance 0.067  I don't know why!

Concordance = 0.061

Wow that is very strange. I would expect a lower bound of 0.5, not something so low.
Can you run the .fit again but turn on the show_progress parameter? And then please display the results?

Here is the results :

Are you able to share the dataset with me? I can't think of any reason why this is happening.

Pretty sure this is caused by a concordance index overflow error, fixed in to be released v0.15


chore stop be first then stop fe to avoid thrift rpc core

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run cloud_p1

run p0

run p0


Transparent headers became white

Hi @davideas,
I've launched app today and noticed that headers became white (but they where transparent before).
I am sure that I don't make any changes in header and item layout files. Maybe I am missing some important changes?
My header markup:
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android">
    <data>
        <import type="android.view.View"/>
        <variable name="item" type="io.centaurea.cnzr.ViewModels.AgendaListHeaderVM"/>
    </data>
    <RelativeLayout android:layout_width="match_parent"
        android:layout_height="@dimen/agenda_header_height"
        android:gravity="center_vertical"
        android:paddingLeft="@dimen/agenda_item_padding_horizontal"
        android:paddingRight="@dimen/agenda_item_padding_horizontal">

        <TextView
            android:id="@+id/agenda_list_item_header"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_centerInParent="true"
            android:textColor="@color/colorSecondaryText"
            android:textSize="@dimen/font_small"
<EMAIL_ADDRESS>
    </RelativeLayout>
</layout>

I am using flexible-adapter:5.0.0-SNAPSHOT

@yamelkaya, yes the new snapshot sets a white background for elevation, but I need to add possibility to set a custom one for transparency.

Ok. Waiting for your changes. Transparent headers are very important in my case. I want to avoid any borders between items and headers in list and because of multi color background I can not set solid (white, black, red etc.). Transparency is only possible way I think.

@yamelkaya, I've adapted the code for transparency, now it has surgery precision :-)

It super easy to implement the transparency and the elevation: all values are taken from the header item layout
Double background is not visible anymore on swapping, if transparency is set.
Elevation is still available with a transparent background.

It's great! Thanks a lot for the quick fix.
Am I right that now I can set android:background for root element of header layout (in my case it is RelativeLayout)? I've tried it and it didn't help.
By the way, I am using usual (not sticky) headers now.

Yes, you modify android:background="#aa7e57c2" and android:elevation="Xdp" to the root element of the item layout. Probably you need to clean manually the Gradle cache for my library.

Yes, after cleaning the cache everything works. Thanks again!


Fix troubleshooting.rst formatting directives

While scrolling through the Troubleshooting section, I noticed two formatting issues under "python3 depthai_demo.py returns Illegal instruction"

This PR fixes incorrect :bash: directives with :code: in one case and .. code-block:: bash in the other

Thanks Lukasz!


Format on save does not seem to work anymore

This seems to happened recently, not sure what it could be.

works for me

This is selfhost (insiders) our workspace:

File is: editorContextKeys.ts

Log files?

I debugged this and see that we correctly call into $provideDocumentFormattingEdits and the result is empty edits, so this seems to be a TS regression. I am using 3.9.x.

and the result is empty edits, so this seems to be a TS regression. I am using 3.9.x.

Must be specific for that case because I am happy with 3.9.0-dev.20200413


Add policy support for named ports

Add support for container port names in policy ports. With this change, in addition to using a L4 port number (like "80") in the network policy (K8s Network Policy or Cilium Network Policy), the port number can be expressed as a name specified in any one of the POD specs in the cluster. If the port name is not specified in any container spec, the traffic specified in the network policy rule can't be allowed, but will be allowed as soon as a container with a matching port name is added.
Port names are stored from a POD spec on the node in which the POD is deployed, from where then name/port mappings are distributed to other nodes via CEP CRDs.
Support for named k8s container ports is added to both K8s Network Policies and Cilium Network Policies.

test-me-please

Coverage increased (+0.0003%) to 44.696% when pulling<PHONE_NUMBER>067bc29dd4d1027defbf31e76618ba on pr/jrajahalme/named-ports into fff6d6c6b02d0d2aaa2d45edb1d370ce70f8cba1 on master.

test-me-please

test-me-please

test-me-please

test-me-please

Fixed unit test breakage, Ginkgo passed except for one unrelated test that depended on external connectivity to <IP_ADDRESS>, most likely a flake.

The CiliumNetworkPolicy "l3-l4-policy-named-port" is invalid: []: Invalid value: map[string]interface {}{"apiVersion":"cilium.io/v2", "description":"L3-L4 policy with named l4 port", "kind":"CiliumNetworkPolicy", "metadata":map[string]interface {}{"name":"l3-l4-policy-named-port", "namespace":"202004230524k8spolicytestbasictestchecksallkindofkubernetespoli", "creationTimestamp":"2020-04-23T05:25:03Z", "annotations":map[string]interface {}{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"cilium.io/v2\",\"description\":\"L3-L4 policy with named l4 port\",\"kind\":\"CiliumNetworkPolicy\",\"metadata\":{\"annotations\":{},\"name\":\"l3-l4-policy-named-port\",\"namespace\":\"202004230524k8spolicytestbasictestchecksallkindofkubernetespoli\"},\"spec\":{\"endpointSelector\":{\"matchLabels\":{\"id\":\"app1\"}},\"ingress\":[{\"fromEndpoints\":[{\"matchLabels\":{\"id\":\"app2\"}}],\"toPorts\":[{\"ports\":[{\"port\":\"http-80\",\"protocol\":\"TCP\"}]}]}]}}\n"}, "generation":1, "uid":"c913034c-8522-11ea-8bee-08002711e3c4"}, "spec":map[string]interface {}{"endpointSelector":map[string]interface {}{"matchLabels":map[string]interface {}{"id":"app1"}}, "ingress":[]interface {}{map[string]interface {}{"fromEndpoints":[]interface {}{map[string]interface {}{"matchLabels":map[string]interface {}{"id":"app2"}}}, "toPorts":[]interface {}{map[string]interface {}{"ports":[]interface {}{map[string]interface {}{"port":"http-80", "protocol":"TCP"}}}}}}}}: validation failure list:
	 spec.ingress.toPorts.ports.port in body should match '^(6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[0-9]{1,4})$'

We need to update the schema validation for CiliumNetworkPolicy

The CiliumNetworkPolicy "l3-l4-policy-named-port" is invalid: []: Invalid value: map[string]interface {}{"apiVersion":"cilium.io/v2", "description":"L3-L4 policy with named l4 port", "kind":"CiliumNetworkPolicy", "metadata":map[string]interface {}{"name":"l3-l4-policy-named-port", "namespace":"202004230524k8spolicytestbasictestchecksallkindofkubernetespoli", "creationTimestamp":"2020-04-23T05:25:03Z", "annotations":map[string]interface {}{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"cilium.io/v2\",\"description\":\"L3-L4 policy with named l4 port\",\"kind\":\"CiliumNetworkPolicy\",\"metadata\":{\"annotations\":{},\"name\":\"l3-l4-policy-named-port\",\"namespace\":\"202004230524k8spolicytestbasictestchecksallkindofkubernetespoli\"},\"spec\":{\"endpointSelector\":{\"matchLabels\":{\"id\":\"app1\"}},\"ingress\":[{\"fromEndpoints\":[{\"matchLabels\":{\"id\":\"app2\"}}],\"toPorts\":[{\"ports\":[{\"port\":\"http-80\",\"protocol\":\"TCP\"}]}]}]}}\n"}, "generation":1, "uid":"c913034c-8522-11ea-8bee-08002711e3c4"}, "spec":map[string]interface {}{"endpointSelector":map[string]interface {}{"matchLabels":map[string]interface {}{"id":"app1"}}, "ingress":[]interface {}{map[string]interface {}{"fromEndpoints":[]interface {}{map[string]interface {}{"matchLabels":map[string]interface {}{"id":"app2"}}}, "toPorts":[]interface {}{map[string]interface {}{"ports":[]interface {}{map[string]interface {}{"port":"http-80", "protocol":"TCP"}}}}}}}}: validation failure list:
	 spec.ingress.toPorts.ports.port in body should match '^(6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[0-9]{1,4})$'

We need to update the schema validation for CiliumNetworkPolicy

@tgraf Already did that, which tells me that this message must be coming from an old build of Cilium?
See https://github.com/cilium/cilium/pull/11092/files#diff-da7eac65a6ed1ef87f8fec512cb90529L1166

Added CRD debugging.

test-missed-k8s

k8s 1.14 & 1.15 failing due to https://github.com/cilium/cilium/pull/11072.

k8s 1.13  passed without CNP CRD flake.

test-me-please

Fixed CRD version check, retesting...

test-me-please

test-missed-k8s

Couple of fixes merged, to there is a chance this will pass now, retesting.

test-me-please

test-missed-k8s

Changed test policies with named ports to use the same name as non-named-port policies so that they replace each other as expected when applied.

test-me-please

test-missed-k8s

Issued #11182 for the GKE CI failure to "select nodes", retesting.

test-gke

@aanm Rebase is needed so I'm setting up for one more round for clean-ups. Now would be a good time for comments, if you have any now that I have addressed your requested changes :-)

Rebased, testing again.

never-tell-me-the-odds

VirtualBox fail with kernel-4.19 CI, retesting

test-with-kernel

never-tell-me-the-odds


Is it possible to get refresh_token from token response?

Hi, I’ve never implemented the refresh_token support. I still have to check out the out of the box new authentication layer that has been shipped with the last blazor preview to see if this library has still a reason to exist. So, in the short term I’m afraid that there is not a library provided way to get the refresh token.


Code blocks are difficult to read, at least on Firefox

Hello,
Code blocks are rather difficult to read, especially on Firefox(78.0.2). Here is a screen capture(I've included normal text to show the contrast):

On Chrome they are a little more readable(perhaps Firefox interprets that font a little different), but still looks like the font size is too small.
I suggest adding a font-size: 1.15rem for code blocks, this way you can easily read them. Here is a screen capture with this change applied(Firefox):

Hi @robertgr991
Thanks for the feedback.

I've updated the styling. Just need to do a deploy

Deployed. Thanks @robertgr991


Adding a check for Tween to prevent undefined errors in Firefox

It has nothing to do with Firefox, that is defined by jQuery on all browsers. Isn't this the same as #115?

Yes it does appear to be the same as #115 . That is the same issue I am experiencing. I am using jQuery 1.7.2 and jQuery Mobile 1.3.1. Maybe this is a useful workaround for those on slightly older versions of jQuery.

Not really, you will avoid the exception but then the plugin won't work. That code is not optional.
If you really can't update jQuery and you want to use scrollTo, you can use a version prior to 2.0.
Version 1.4.14 should work with jQuery >= 1.4

In any case, I'll close this issue as dup of #115. jQuery.scrollTo 2.0 requires jQuery 1.8 and above, I recently added a mention of that on the docs


[Bug] Handlebars syntax highlighting broken since version 0.35.0

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[ ] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
Playground with unexpected brackets highlighing {{{ }}}
https://microsoft.github.io/monaco-editor/playground.html?source=v0.35.0#XQAAAAJ5AQAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscwzhsWG_1uhs0-3YGTBOsVJ4S4FwfCDQb5-2uUHXTVAefbVSd9IzaZ_vv9VR9KugsKicTKQ1OZgR4qMzYNG8oY_AkxFezfwWHwjDKVy3_uJ9AWb9KOwnA_ApXsDWPrV6CNfDprrH-007Gez0wm4FzXaZQQQ7y0Syg6uTw9urDuwR6z7WMtYEbZq2_Y9nbft1OLEbDqnwh8TKzjfDtcG6cBrapgfOLJ2AM045qGXGvaT6_jK4UWrD4WcDZwWEkMebOW9oCINNMYJFaITG8ntsjHU_zpJ9ooQK7LFjOlvNNin3V5UP_fQSIL
Monaco Editor Playground Code
const value = /* set from `myEditor.getModel()`: */ `

{{#blockHelper}}

{{ escaped }}

{{{ unescaped }}}

{{/blockHelper}}
`;

// Hover on each property to see its docs!
const myEditor = monaco.editor.create(document.getElementById("container"), {
	value,
	language: "handlebars",
	automaticLayout: true,
});

Reproduction Steps

Use handlebars tripple curly brackets for unescaped output
Switch between editor version 0.34.1 (as expected) 0.35.0 and latest stable (not as expected)

Actual (Problematic) Behavior

Expected Behavior

Additional Context
In addition to the red coloring of the tripple curly brackets, you can also notice that brackets are colored in blue in general and not black as expected.

Is any info missing in this issue? Any pointers to a workaround would be much appreciated.


Update ns-d3d12-d3d12_buffer_rtv.md

local testing demonstrates that FirstElement refers to the number of elements, not the number of bytes.

I'd also want to add that it appears

WIN32_FIND_DATAA is using the W version struct def.


Leectode 2164  Sort Even and Odd Indices Independently

Can u pls assign this issue to me? I will add the solution in C++
Question -2164 Sort Even and Odd Indices Independently

please merge my pull request


Feature request: enable tracing by default

The NodejsFunction created as part of the scaffolding should have active tracing enabled by default.
import { Stack, type StackProps, CfnOutput } from 'aws-cdk-lib';
import { Construct } from 'constructs';
-- import { Runtime } from 'aws-cdk-lib/aws-lambda';
++ import { Runtime, Tracing } from 'aws-cdk-lib/aws-lambda';
import { NodejsFunction, OutputFormat } from 'aws-cdk-lib/aws-lambda-nodejs';

export class InfraStack extends Stack {
  constructor(scope: Construct, id: string, props?: StackProps) {
    super(scope, id, props);

    const fn = new NodejsFunction(this, 'MyFunction', {
      runtime: Runtime.NODEJS_20_X,
      entry: '../src/index.ts',
      handler: 'handler',
 ++     tracing: Tracing.ACTIVE,
      bundling: {
        minify: true,
        mainFields: ['module', 'main'],
        sourceMap: true,
        format: OutputFormat.ESM,
      }
    });

    new CfnOutput(this, 'FunctionArn', {
      value: fn.functionArn,
    });
  }
}

While at it, I should also add this banner to the bundling object:
banner:
          "import { createRequire } from 'module';const require = createRequire(import.meta.url);",

Added in e42009b


facebook payload not working

controller.hears('test', 'message_received', function(bot, message) {
var attachment = {
    'type':'template',
    'payload':{
        'template_type':'generic',
        'elements':[
            {
                'title':'Chocolate Cookie',
                'image_url':'http://cookies.com/cookie.png',
                'subtitle':'A delicious chocolate cookie',
                'buttons':[
                    {
                    'type':'postback',
                    'title':'Eat Cookie',
                    'payload':'chocolate'
                    }
                ]
            },
        ]
    }
};

bot.reply(message, {
    attachment: attachment,
});

});
controller.on('facebook_postback', function(bot, message) {
if (message.payload == 'chocolate') {
    bot.reply(message, 'You ate the chocolate cookie!')
}

});
But bot did not reply You ate the chocolate cookie!
Reason found

Closed due to inactivity.

I have the same issue...any fix about that?

@azanoni please start a new issue with an example of the code that doesn't work.

I started here https://github.com/howdyai/botkit/issues/814 its rare that a issue still not working for a year ago

I resolve this issue with this comment
https://github.com/hyperoslo/facebook-messenger/issues/15#issuecomment-216933326
The botkit readme should be updated.

@azanoni We are planning on a Facebook provisioning doc that contains a sane list of subscriptions to get you started, thanks for the reminder!

payload  will not work , you need to check the messages_postback in Webhook settings