Weired unexpected pydantic error with certain models

I tried to deploy this model https://github.com/zsxkib/InstantID
using cog today and it failed throwing me a pydantic error :
cannot import VaildtorError from pydantic ,
python version 3.11.9
cog version 0.9.5
pydantic vesion 1.10.15
Important note: I used to be able to deploy and build this model without any problem , this new problem occurred 3 days ago (April 19)
I pulled the image from cog and I could push it again to replicate however after extracting it to my local env and trying to deploy the same code and structure it failed
Any help or clue is appreciated

Hi @ElyasMoshirpanahi. Thanks for reporting. I can't think of anything that changed in Cog that could've caused that. Can you please share the command you ran and the full output?

Hi @mattt here is my full log:
[+] Building 106.0s (6/21)                                                                                docker:default
=> [internal] load build context                                                                                102.6s
[+] Building 106.2s (6/21)                                                                                docker:default
=> [internal] load build context                                                                                102.7s
[+] Building 106.3s (6/21)                                                                                docker:default
=> [internal] load build context                                                                                102.9s
[+] Building 106.5s (6/21)                                                                                docker:default
=> => transferring context: 4.83GB                                                                                103.0s
[+] Building 744.5s (23/23) FINISHED                                                                                docker:default
=> [internal] load build definition from Dockerfile                                                                                0.1s
=> => transferring dockerfile: 2.38kB                                                                                0.0s
=> [internal] load .dockerignore                                                                                0.1s
=> => transferring context: 2B                                                                                0.1s
=> resolve image config for docker.io/docker/dockerfile:1.4                                                                                1.2s
=> docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531bd80fb0a858632727cf7a112fbfd19b17e94c4e84ced81e24ef1a0dbc                                                                                0.5s
=> => resolve docker.io/docker/dockerfile:1.4@sha256:9ba7531bd80fb0a858632727cf7a112fbfd19b17e94c4e84ced81e24ef1a0dbc                                                                                0.0s
=> => sha256:1e8a16826fd1c80a63fa6817a9c7284c94e40cded14a9b0d0d3722356efa47bd 2.37kB / 2.37kB                                                                                0.0s
=> => sha256:1328b32c40fca9bcf9d70d8eccb72eb873d1124d72dadce04db8badbe7b08546 9.94MB / 9.94MB                                                                                0.2s
=> => sha256:9ba7531bd80fb0a858632727cf7a112fbfd19b17e94c4e84ced81e24ef1a0dbc 2.00kB / 2.00kB                                                                                0.0s
=> => sha256:ad87fb03593d1b71f9a1cfc1406c4aafcb253b1dabebf569768d6e6166836f34 528B / 528B                                                                                0.0s
=> => extracting sha256:1328b32c40fca9bcf9d70d8eccb72eb873d1124d72dadce04db8badbe7b08546                                                                                0.1s
=> [internal] load metadata for docker.io/nvidia/cuda:11.8.0-cudnn8-devel-ubuntu22.04                                                                                1.3s
=> [internal] load metadata for docker.io/library/python:3.11                                                                                1.4s
=> [internal] load build context                                                                                275.5s
=> => transferring context: 10.32GB                                                                                275.3s
=> [stage-1 1/9] FROM docker.io/nvidia/cuda:11.8.0-cudnn8-devel-ubuntu22.04@sha256:8f9dd0d09d3ad3900357a1cf7f887888b5b74056636cd6ef03c160c3cd4b1d95                                                          174.3s
=> => resolve docker.io/nvidia/cuda:11.8.0-cudnn8-devel-ubuntu22.04@sha256:8f9dd0d09d3ad3900357a1cf7f887888b5b74056636cd6ef03c160c3cd4b1d95                                                                    0.1s
=> => sha256:bd746eb3b9953805ebe644847a227e218b5da775f47007c69930569a75c9ad7d 2.84kB / 2.84kB                                                                                0.0s
=> => sha256:aece8493d3972efa43bfd4ee3cdba659c0f787f8f59c82fb3e48c87cbb22a12e 29.54MB / 29.54MB                                                                                0.4s
=> => sha256:5e3b7ee7738140e8f4608c3945b6e1ed4f9fb75db53a04e19ba0a6661e7cc4fe 4.62MB / 4.62MB                                                                                0.4s
=> => sha256:5bd037f007fdda13ae5a5f43a199d6677db1f9059c2980c84726e3a43fab169a 56.23MB / 56.23MB                                                                                0.7s
=> => sha256:8f9dd0d09d3ad3900357a1cf7f887888b5b74056636cd6ef03c160c3cd4b1d95 743B / 743B                                                                                0.0s
=> => sha256:d0117ee15b5fd0bbcb42c8fd3e35f9bc0f06fe3a947a4ec240f9b73738c7cf54 17.79kB / 17.79kB                                                                                0.0s
=> => extracting sha256:aece8493d3972efa43bfd4ee3cdba659c0f787f8f59c82fb3e48c87cbb22a12e                                                                                1.0s
=> => sha256:4cda774ad2ecef28c9a1cd97594f7199071c83769f91c5d109eb1cb6770ecdff 188B / 188B                                                                                0.7s
=> => sha256:775f22adee620daec0db645bad7027db4c1ecf22520412e1b2466fc73d54d19b 6.88kB / 6.88kB                                                                                0.8s
=> => sha256:16c36d0187d03bd0de84d870ded86c45fabd78f4bfdb2ed90177e5fc4dd33d11 63.70kB / 63.70kB                                                                                0.9s
=> => sha256:263fc748118f7937f811e3e9c9355318db07dd2dd1dccc370dadaa7d0b5ed692 1.38GB / 1.38GB                                                                                22.8s
=> => sha256:e7a56570655c990ecc804c77873efc83f9a6c31064e3e8a5dc02430213f2d74c 1.69kB / 1.69kB                                                                                0.9s
=> => sha256:23b7d8e07c16707ff4ec3ca558a8099c454953c840156c318a60a6b4273846a0 2.46GB / 2.46GB                                                                                51.1s
=> => sha256:507fc9045cbad45c1c4ca554a6453fe0a1c9ae74667db0612fec7475256d5c23 1.52kB / 1.52kB                                                                                1.0s
=> => sha256:922ac8fcb88926d95550e82f83c14a4f3f3eaab635e7acf43ee0c59dea0c14d7 88.23kB / 88.23kB                                                                                1.2s
=> => sha256:68075f2beca1cfd3f243ec110000716dff39d895f4d5e0d3faba7ace430f9633 1.43GB / 1.43GB                                                                                41.2s
=> => extracting sha256:5e3b7ee7738140e8f4608c3945b6e1ed4f9fb75db53a04e19ba0a6661e7cc4fe                                                                                0.2s
=> => extracting sha256:5bd037f007fdda13ae5a5f43a199d6677db1f9059c2980c84726e3a43fab169a                                                                                1.4s
=> => extracting sha256:4cda774ad2ecef28c9a1cd97594f7199071c83769f91c5d109eb1cb6770ecdff                                                                                0.0s
=> => extracting sha256:775f22adee620daec0db645bad7027db4c1ecf22520412e1b2466fc73d54d19b                                                                                0.0s
=> => extracting sha256:263fc748118f7937f811e3e9c9355318db07dd2dd1dccc370dadaa7d0b5ed692                                                                                22.1s
=> => extracting sha256:16c36d0187d03bd0de84d870ded86c45fabd78f4bfdb2ed90177e5fc4dd33d11                                                                                0.0s
=> => extracting sha256:e7a56570655c990ecc804c77873efc83f9a6c31064e3e8a5dc02430213f2d74c                                                                                0.0s
=> => extracting sha256:507fc9045cbad45c1c4ca554a6453fe0a1c9ae74667db0612fec7475256d5c23                                                                                0.0s
=> => extracting sha256:23b7d8e07c16707ff4ec3ca558a8099c454953c840156c318a60a6b4273846a0                                                                                51.3s
=> => extracting sha256:922ac8fcb88926d95550e82f83c14a4f3f3eaab635e7acf43ee0c59dea0c14d7                                                                                0.0s
=> => extracting sha256:68075f2beca1cfd3f243ec110000716dff39d895f4d5e0d3faba7ace430f9633                                                                                13.3s
=> [deps 1/5] FROM docker.io/library/python:3.11@sha256:db07fba48daaf1c68c03676aadc73866414d25b4c278029f9873c784517613bf                                                                                142.0s
=> => resolve docker.io/library/python:3.11@sha256:db07fba48daaf1c68c03676aadc73866414d25b4c278029f9873c784517613bf                                                                                0.1s
=> => sha256:db07fba48daaf1c68c03676aadc73866414d25b4c278029f9873c784517613bf 2.14kB / 2.14kB                                                                                0.0s
=> => sha256:41936fec553de22d1de0c450fcbf8f6b9486508f27329073204455a252d916f7 7.32kB / 7.32kB                                                                                0.0s
=> => sha256:21d1a3d86b1656a745a9ccfdd3a0797a694c9d48450e65734127183506a38e8c 2.01kB / 2.01kB                                                                                0.0s
=> => sha256:609c73876867487da051ad470002217da69bb052e2538710ade0730d893ff51f 49.56MB / 49.56MB                                                                                51.5s
=> => sha256:7247ea8d81e671d079d67f3a9909315ef4641b45db90d62a1b18e3430c1937d4 24.05MB / 24.05MB                                                                                51.2s
=> => sha256:b4580645a8e50b87a19330da289a9b1540022379f2c99d3f0112e3c5c4a8d051 211.14MB / 211.14MB                                                                                56.5s
=> => sha256:aa7e0aca67ddfc342e2afe83df590a0e228e34781e7206639ddd9da72a71a0af 6.39MB / 6.39MB                                                                                51.7s
=> => extracting sha256:609c73876867487da051ad470002217da69bb052e2538710ade0730d893ff51f                                                                                7.7s
=> => sha256:be374d06f38273b62ddd7aa5bc3ce3f9c781fd49a1f5a5dd94a46d2986920d7a 64.14MB / 64.14MB                                                                                52.4s
=> => sha256:928988b537f87dd6ce2dff578fa9dc94138f9497eb6c7d575fad7b65b14bca7a 19.84MB / 19.84MB                                                                                52.5s
=> => sha256:95604f0c57a72f2a5dc8b36c0f35918967c5f347fe0945f7d3bded9e6c639f20 245B / 245B                                                                                57.2s
=> => sha256:af495b5540acf407853862e768a57adb5e020fc219969662e8941f0d610b74de 3.13MB / 3.13MB                                                                                57.3s
=> => extracting sha256:7247ea8d81e671d079d67f3a9909315ef4641b45db90d62a1b18e3430c1937d4                                                                                0.6s
=> => extracting sha256:be374d06f38273b62ddd7aa5bc3ce3f9c781fd49a1f5a5dd94a46d2986920d7a                                                                                2.2s
=> => extracting sha256:b4580645a8e50b87a19330da289a9b1540022379f2c99d3f0112e3c5c4a8d051                                                                                6.1s
=> => extracting sha256:aa7e0aca67ddfc342e2afe83df590a0e228e34781e7206639ddd9da72a71a0af                                                                                0.6s
=> => extracting sha256:928988b537f87dd6ce2dff578fa9dc94138f9497eb6c7d575fad7b65b14bca7a                                                                                0.7s
=> => extracting sha256:95604f0c57a72f2a5dc8b36c0f35918967c5f347fe0945f7d3bded9e6c639f20                                                                                0.0s
=> => extracting sha256:af495b5540acf407853862e768a57adb5e020fc219969662e8941f0d610b74de                                                                                0.3s
=> [stage-1 2/9] RUN --mount=type=cache,target=/var/cache/apt set -eux; apt-get update -qq; apt-get install -qqy --no-install-recommends curl; rm -rf /var/lib/apt/lists/; TINI_VERSION=v0.19.0; TINI_ARCH="  6.9s
=> [stage-1 3/9] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends  make  build-essential  libssl-dev  zlib1g-dev  libbz2-dev  libreadline-dev  24.7s
=> [stage-1 4/9] RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash &&  git clone https://github.com/momo-lab/pyenv-install-latest.git "$(pyenv roo  71.6s
=> [deps 2/5] COPY .cog/tmp/build1197687401/cog-0.0.1.dev-py3-none-any.whl /tmp/cog-0.0.1.dev-py3-none-any.whl                                                                                2.0s
=> [stage-1 5/9] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy libgl1-mesa-glx libglib2.0-0 && rm -rf /var/lib/apt/lists/                                          12.5s
=> [deps 3/5] RUN --mount=type=cache,target=/root/.cache/pip pip install -t /dep /tmp/cog-0.0.1.dev-py3-none-any.whl                                                                                6.9s
=> [deps 4/5] COPY .cog/tmp/build1197687401/requirements.txt /tmp/requirements.txt                                                                                0.2s
=> [deps 5/5] RUN --mount=type=cache,target=/root/.cache/pip pip install -t /dep -r /tmp/requirements.txt                                                                                163.7s
=> [stage-1 6/9] RUN --mount=type=bind,from=deps,source=/dep,target=/dep cp -rf /dep/* $(pyenv prefix)/lib/python*/site-packages || true                                                                      43.6s
=> [stage-1 7/9] RUN curl -o /usr/local/bin/pget -L "https://github.com/replicate/pget/releases/download/v0.6.0/pget_linux_x86_64" && chmod +x /usr/local/bin/pget                                             1.5s
=> [stage-1 8/9] WORKDIR /src                                                                                0.1s
=> [stage-1 9/9] COPY . /src                                                                                66.9s
=> preparing layers for inline cache                                                                                38.6s
=> exporting to image                                                                                0.0s
=> => exporting layers                                                                                0.0s
=> => writing image sha256:f7c7316643155567ab6221565293e6d293358c91ed351e57426e5784ff13bd82                                                                                0.0s
=> => naming to r8.im/zaubar/simple-juggernaut-xl-v7                                                                                0.0s
Validating model schema...
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/cog/command/openapi_schema.py", line 46, in
raise CogError(app.state.setup_result.logs)
cog.errors.CogError: Error while loading predictor:
Traceback (most recent call last):
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/cog/server/http.py", line 130, in create_app
predictor = load_slim_predictor_from_ref(predictor_ref, "predict")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/cog/predictor.py", line 233, in load_slim_predictor_from_ref
module = load_full_predictor_from_file(module_path, module_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/cog/predictor.py", line 193, in load_full_predictor_from_file
spec.loader.exec_module(module)
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/src/cog/predict.py", line 37, in
from insightface.app import FaceAnalysis
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/insightface/init.py", line 18, in
from . import app
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/insightface/app/init.py", line 2, in
from .mask_renderer import *
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/insightface/app/mask_renderer.py", line 4, in
import albumentations as A
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/albumentations/init.py", line 3, in
from .augmentations import *
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/albumentations/augmentations/init.py", line 1, in
from .blur.functional import *
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/albumentations/augmentations/blur/init.py", line 1, in
from .functional import *
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/albumentations/augmentations/blur/functional.py", line 9, in
from albumentations.augmentations.geometric.functional import scale
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/albumentations/augmentations/geometric/init.py", line 2, in
from .resize import *
File "/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/albumentations/augmentations/geometric/resize.py", line 6, in
from pydantic import Field, ValidationInfo, field_validator
ImportError: cannot import name 'ValidationInfo' from 'pydantic' (/root/.pyenv/versions/3.11.9/lib/python3.11/site-packages/pydantic/init.cpython-311-x86_64-linux-gnu.so)
ⅹ Failed to get type signature: exit status 1
Thanks for helping in advance

@mattt Found that this error came from a dependency update of instant id , and to be specific , this library albumentations version is suppose to be 1.4.3 but since there were not version pinning in instant id version 1.4.4 was installed and that caused the error.
I think you can close this issue and the end result would be to pin this dependency in the cog.yaml file like so :
a list of packages in the format ==
  python_packages:
    - "albumentations==1.4.3"
   ...... other dependencies


Flash messages when using HTMX

When using HTMX the full template is not rendered on the backend (which means that flash messages are not processed). How should we use flash messages when using htmx powered forms ?
It is possible to include the "messages" but I was wondering if these are in the base template and you would like to show flash messages not in the form but in the base template. I'm not sure if this can even work, given the semantics of what is actually rendered (just the html which should be changed and not the whole template)
So any tips on patterns would be greatly appreciated!

Did you figure it out?

Yes! I could just include the message template in the htmx template and voila!


Move contextual parser tests to use balPartNode

Description:
$subject to avoid possible source pruning in parser test cases.
Related issues: #31237

Closing this issue as the balPartNode no longer exists.


ui-select in a list of items

Hi,
Version angular : 1.5.6
Version ui-select : 0.19.5 - 2016-10-24T23:13:59.434Z
I wanna integrate multiple ui-select in a ng-repeat instructions like :
https://embed.plnkr.co/60qhM74EUXb7or78sx39/
But when I select an other element, the model is an objets like
{"Cle":124,"Valeur":"- COMPTES RENDUS KINE","Type":"TypeDocument"}
Can you tell how i get the good value of the field "Cle" or the method for implemente this please ?
I have try

on-select="changeTypeDocumentId($item, $model)"

But can't get the model
And too :
ng-model="$parent.document.TypeDocumentId"
but nothing.
Best regards

Are you referring to Array of objects with single property binding? Like here: http://plnkr.co/edit/jIO77ceKhfdFXFwyz4Fh?p=preview
It's literally in the examples.
<ui-select-choices repeat="typeDocuments.Cle as typeDocuments in (selectTypeDocuments.availableOptions | filter: $select.search) track by typeDocuments.Cle" refresh-delay="0">

Thanks for your quick answer.
I've try typeDocuments.Cle as typeDocuments but the value don't display
Perhaps, the code in directive ui-select-match is not good :
<ui-select-match>{{document.TypeDocumentLibelle}}</ui-select-match>

If I try width {{document.TypeDocumentId}}
It's works
but i want display the Valeur field, not the key

Do you mean that the ng-model that is bind should be the value of availableOptions.Valeur


NOSQL - Update kv version and doc

This PR updates the Oracle NoSQL Dockerfile to align with the latest version and bundles.

Currently, this GitHub uses the bundle kv-ce-19.5.19.zip to build the docker image. Our last bundle for this version is kv-ce-19.5.25.zip.
We created a new directory ce. It contains the Dockerfile for the latest Oracle NoSQL version, 20.3.
In this new version, we are also adding HTTP PROXY support
I also explicitly set the base image to the Oracle Linux-based 8 variant of the official OpenJDK image.

Finally, I updated CODEOWNERS to switch the owner of /NoSQL to @dario-vega and @mikebrey.
Signed-off-by: Dario Vega<EMAIL_ADDRESS>

There are two minor copyright header date things, but otherwise I'm happy to merge this now.


version changes in Dockerfile

htslib 1.5 -> 1.15.1
samtools 1.5 -> 1.15
primer3 2.3.7 -> 2.6.1

Hello @JasonLing95! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file test/test_primer_designer.py:

Line 68:80: E501 line too long (86 > 79 characters)


Dependencies were updated.

Codecov Report

Merging #26 (53ec905) into develop (15b5299) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##           develop      #26   +/-   ##
========================================
  Coverage    92.70%   92.70%
========================================
  Files            4        4
  Lines           96       96
========================================
  Hits            89       89
  Misses           7        7

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


Toggle camera

Hi anyone have any idea on how to toggle the camera from the main view controller, I have a button there, and know about PHCapturePreviewView, how do I make it work?
Thanks

done, just use a NSNotification to call selectCameraPosition


Admin search fails with unicode characters

If you search for a string containing unicode characters you get an internal server error.
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 7: ordinal not in range(128)
I guess it should either accept unicode or at least validate against it?

Looks like a bug to me. Do you have any more traceback? (would be useful to know where this error is being raised from)
This is likely to be something that only affects Python 2 users

I've forwarded you the report @kaedroho.

Thanks @tmsndrs. This doesn't look like a Wagtail bug.
The particular site this is happening on has a template context processor to calculate the urls of the current page in different languages. (eg, it turns /admin/ into /en/admin/ and /fr/admin/). Theres a call to urllib in here which seems to be crashing.


Added instructions to run on Linux

Sorry, this only happens on pre-built files that are downloaded to linux. Should this be added to note?


[Feature Request] Implement a CanBeDeletedInterface

Feature Request
What's the feature you think Backpack should have?
In a common list , we have usually the delete button.
But some entry cannot be deleted, if they are related from other records, to ensure data integrity.
Usually this check is done my the db, but we could think to add some 'live checks' to single entry to allow the delete button to be dinamically disabled
Have you already implemented a prototype solution, for your own project?
We created app/Models/Interfaces/CanBeDeletedInterface.php
namespace App\Models\Interfaces;

interface CanBeDeletedInterface
{
    function getCanBeDeletedAttribute();
    function getWhyCannotBeDeletedAttribute();
}

A model could implement this interface.
For example: if an Organization has at least one active member, the organization cannot be deleted.
...
use App\Models\Interfaces\CanBeDeletedInterface;
....

class Organization extends Model implements CanBeDeletedInterface
{
   ...
    function getCanBeDeletedAttribute()
    {
        if ($this->active_members->count() >0) {
            return false;
        }

        return true;
    }

    function getWhyCannotBeDeletedAttribute()
    {
        if ($this->active_members->count() >0) {
            return "You cannot delete an organization with active members.";
        }

        return null;
    }
}

We customized delete button in resources/views/vendor/backpack/crud/buttons/delete.blade.php
This is the relevant part of our implementation
@if ($crud->hasAccess('delete'))

    @if($entry instanceof  \App\Models\Interfaces\CanBeDeletedInterface)

        @if($entry->can_be_deleted === true)
            route.'/'.$entry->getKey()) }}" class="btn btn-sm btn-danger"
               data-button-type="delete"
               data-toggle="tooltip" data-placement="top" title="{{ trans('backpack::crud.delete') }}"
            >

                {{--        {{ trans('backpack::crud.delete') }}--}}

        @else
            route.'/'.$entry->getKey()) }}" class="btn btn-sm btn-outline-danger"
               data-button-type="delete"
               data-toggle="tooltip" data-placement="top" title="{{ $entry->why_cannot_be_deleted }}"
            >

                {{--        {{ trans('backpack::crud.delete') }}--}}

        @endif

    @else

        route.'/'.$entry->getKey()) }}" class="btn btn-sm btn-danger"
           data-button-type="delete"
           data-toggle="tooltip" data-placement="top" title="{{ trans('backpack::crud.delete') }}"
        >

    {{--        {{ trans('backpack::crud.delete') }}--}}

     @endif
@endif

Do you see this as a core feature or an add-on?
I think it could be a core feature, because it's plug-n-play

Updated version of resources/views/vendor/backpack/crud/buttons/delete.blade.php , simpler, just taken from an updated V6 project
@if ($crud->hasAccess('delete'))

        can_be_deleted === false)
                onclick="cannotDeleteEntry(this)"
                data-button-type="canont-delete"
                data-toggle="tooltip" data-placement="top" title="{{ $entry->why_cannot_be_deleted }}"
            @else
                data-button-type="delete"
                onclick="deleteEntry(this)"
                data-route="{{ url($crud->route.'/'.$entry->getKey()) }}"
            @endif
        >
             {{ trans('backpack::crud.delete') }}

@endif

{{-- Button Javascript --}}
{{-- - used right away in AJAX operations (ex: List) --}}
{{-- - pushed to the end of the page, after jQuery is loaded, for non-AJAX operations (ex: Show) --}}
@push('after_scripts') @if (request()->ajax()) @endpush @endif
@bassetBlock('backpack/crud/buttons/delete-button-'.app()->getLocale().'.js')

@endBassetBlock
@if (!request()->ajax()) @endpush @endif

Thanks for sharing your code @realtebo 🙏
I agree we don't have a good solution for this, at the moment. You can't easily allow/deny item-access right now in Backpack. And we should probably work on that.
But I don't think we should go for this solution, but a more general one. One that could apply to ALL operations, not just to Delete. Because ok your use case is to hide the Delete button. But what if the need is to hide the Clone button? Or the Edit button? Then we'd need to do the same thing inside all our Operations, which is not ok - it'll end up pretty spaghetti.
I'll tag this to think about in v6.x when we have more time. Right now we're swamped with the launch of 6.0. Until then I'm sure your code will help someone fix their problem.
Thanks!

I have great news @realtebo - we have a solution for this now. And it's beautiful! Check out Access Closures - https://backpackforlaravel.com/articles/tutorials/new-in-v6-granular-user-access-using-custom-closures - using them you can define that the Delete operation is forbidden for some entries. And this will not only hide the button, but also prevent the routes from working. Which is exactly what you needed, I think 🎉


Unable to Publish Extension

All of the original details in #374 are still applying to us currently trying to publish.
We think we kind of have the root cause, our VSCode extension is here:
https://marketplace.visualstudio.com/items?itemName=LaunchDarklyOfficial.launchdarkly
And ADO: https://marketplace.visualstudio.com/items?itemName=launchdarkly.launchdarkly-extension
We had an issue with access at one point where your team helped us move over at least VSCode, but we thought it was both of them. Looking at the above with one being LaunchDarklyOfficial and the other just launchdarkly it doesn’t appear like ADO moved over. Would we be able to get assistance with that?
cc @isidorn

Hi @InTheCloudDan
Can you please help us with the below questions.

We see that there are two different publishers on marketplace - LaunchDarklyOfficial, LaunchDarkly - Do you own both of them?
Can you also explain a little on which extension are you trying to publish ?
Can you share the exact error message you are getting? We are interested in the activityId (if any) mentioned in the error message.
Also, I see that @madhurivadaligithub closed the issue #374 since we haven't heard back from you back then. Can you let us know if there was some fix made from our side or you fixed it on your side ?

@SaiKanth007

Yes, we own both of them, but do not have easy access to the original one which is why we migrated to LaunchDarklyOfficial.
We are trying to update our AzureDevops integration, it has our old logo: https://marketplace.visualstudio.com/items?itemName=launchdarkly.launchdarkly-extension
The error message is

error: Error: Extension validation failed. Please address the following issues and retry publishing.
error: The Service Endpoint Contribution Microsoft.VisualStudio.Services.ServiceEndpointName.LAUNCHDARKLY with Name LAUNCHDARKLY already exists in the Marketplace. To publish the extension, please ensure you have a unique service endpoint name.```

4. Nothing changed we just dropped trying to follow up on it temporarily. Our goal is to get this resolved so we can make additional updates to the extension.

@InTheCloudDan Can you drop an email to<EMAIL_ADDRESS>with the VSIX you are trying to upload.
Also, this issue is related to AzureDevops, @madhurivadaligithub can you please take a look at this.

Thanks for reaching VS Marketplace Team, could you please reach out to us through our support alias<EMAIL_ADDRESS>to address this issue promptly.


find_elements is very slow

Running tab.find_elements() is extremely slow. It takes between 60-100 seconds to find ~100 elements.

Running tab.find_elements() is extremely slow. It takes between 60-100 seconds to find ~100 elements.

Hi, can you post the code please ?

Sorry for the slow response. I figured out it was an issue with my processor, not this crate.

It is still quite slow though. I am just running a simple tab.find_elements on a page and pulling out some anchor elements from within a container (tab.find_elements("#container a")). It takes ~15 seconds to run. In Javascript, it would work almost instantaneously.

This might just be related to my hardware / GPU acceleration for me. Launching with --disable-gpu seems to help.

@mockfox
I have the same issue on both a windows machine and a raspberry pi. I've added to the LaunchOptionsBuilder:
.args(vec![
&OsStr::new("--disable-gpu")])
but that did not do anything.
Scanning a simple table takes ~67 seconds. On the pi like 5 more. Test project on Github:
https://github.com/sanderPostma/chrome-headless-perf

This issue still persists, I executed the test @sanderPostma linked to and it's taking 66 seconds on my computer.
And the table isn't even very large, (8x25). find_elements didn't even work for me, I had to change it to wait_for_elements, and it took 43 seconds.
I also had to change the xpaths to CSS selectors because it wouldn't work with the xpaths


Typescript improvements

Tagged Steve if he has a cycle.  If not, will just merge bc yarn build works... and that's the real judge here, amirite?

o damnit tests!


Can I just run a kubectl command and do not open cloudtty WEBUI ?

like kubectl exec.
Sometimes, I just want to apply a yaml file,
etc.

Is there such a scene?
why not to apply a yaml file with kubectl directly?


Add README for the examples

We have a lot of examples in FEDOT now. However, it is hard to understand the scope of each example.
So, the README file for examples section with short description of each example can be added.
See https://github.com/awslabs/autogluon/tree/master/examples/image_classification as an example of second-level README implementation.

I also suggest to re-organize the structure of examples. Some scripts can be moved to a separate directory.

In the same issue, the tests should be added for each example.
Also, the problem noted in https://github.com/nccr-itmo/FEDOT/pull/291#discussion_r636431255 should be investigated.


Fix table formatting for SAML SPs

added a pipe symbol to fix table formatting for SAML SPs

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


Processing stuck

I have been trying the new HiCognition version (@206) and since I have created my account I have two datasets in download that seem to be stuck and preventing any further processing of other data (see image below, this is has been ongoing since last week).

This was independent of the HiCognition software, the machine ran out of disc space. The data directory was switched onto a bigger partition.


ENYO-2149: Added the moonstone-samples package into the moonstone-extras compilation

Removed unsmart cruft.
Enyo-DCO-1.1-Signed-off-by: Blake Stephens<EMAIL_ADDRESS>

These seems reasonable until we fix up the samples to declare the assets each uses rather than a catch-all in the main directory.


Getting exception

Hi,
I am implementing health check for my project and it work absolute fine until when i try to enable cache in my project.
I tried all possible way from my side but couldn't able to figure out.
Please help .
Urls :
urlpatterns = patterns(
url(r'^api/health/$', include('health_check.urls'))
)

Settings: config
INSTALLED_APPS =[
'health_check',  # required
    'health_check.db',  # stock Django health checkers
    'health_check.contrib.rmq',
    'health_check.cache'
]
HEALTH_CHECK_CONF = dict(rmq_host=BROKER_URL, sqs_queue_name='queue_name', region_name='eu-west-1',
                         aws_secret_access_key='mykey', aws_access_key_id='access_id',
                         soft_dependencies=[CACHES]
                         )

===========
 Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/Users/neeraj/virtualenv/python2/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
    utility.execute()
  File "/Users/neeraj/virtualenv/python2/lib/python2.7/site-packages/django/core/management/__init__.py", line 312, in execute
    django.setup()
  File "/Users/neeraj/virtualenv/python2/lib/python2.7/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/neeraj/virtualenv/python2/lib/python2.7/site-packages/django/apps/registry.py", line 85, in populate
    app_config = AppConfig.create(entry)
  File "/Users/neeraj/virtualenv/python2/lib/python2.7/site-packages/django/apps/config.py", line 119, in create
    import_module(entry)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
ImportError: No module named cacherest_framework

==========
Regards,
Neeraj

Hi @neerajprasad you are missing a comma in you INSTALLED_APP setting right after 'health_check.cache'. I presume the next app in the list is rest_framework. Without the comma the strings will be appended and Django will try to import health_check. cacherest_framework which of course doesn't exist ;)


[chore] Get rid of duplicate from news_site

There are few duplicates files specially few management commands

fixed in https://github.com/fafadiatech/newscout_web/pull/279

still getting this issue in more news.
(http://www.newscout.in/news/article/kroger-rationing-sanitizers-amid-coronavirus-shopping-frenzy-1483830/)check this link.


S3 storage configuration

I encountered a problem. I configured an S3 bucket as storage, created the byconity0 directory under S3 bucket cxxx-xxy, and modified the relevant configuration as follows:

After I created the data table with storage_policy = 'cnch_default_s3', I got an error when inserting data into the table.
SQL 错误 [499] [07000]: Code: 499, e.displayText() = DB::S3::S3Exception: Encounter exception when request s3, HTTP Code: 404, RemoteHost: , RequestID: SV0V3QHNNBT8P5XA, ExceptionName: NoSuchKey, ErrorMessage: The specified key does not exist., Extra: Could not list objects in bucket cxxx-xxy with prefix byconity0/ef0d789d-c1b4-d43e-c7c2-e3a9de4f9ff3/ SQLSTATE: HY000 (version <IP_ADDRESS>)
, server ClickHouseNode [uri=http://<IP_ADDRESS>:8123/default, options={socket_timeout=6000000,use_server_time_zone=false,use_time_zone=false}]@-621526795
I don't know how else I need to modify the configuration?

hi @syysummer . Maybe you have a misconfiguration of S3, such as endpoint, API key, etc. Could you re-check the configuration again?

hello @smmsmm1988 , Thank you very much. The S3 address and permissions have been confirmed. According to the analysis of the error message, the connection has been successful, but the resource cannot be obtained. The error message is
 TransactionCleaner: auto DB::TransactionCleaner::scheduleTask((lambda at ../src/Transaction/TransactionCleaner.cpp:170:18) &&, DB::CleanTaskPriority, DB::TxnTimestamp, DB::Protos::TransactionStatus &&)::(anonymous class)::operator()() const : Code: 499, e.displayText() = DB::S3::S3Exception: Encounter exception when request s3, HTTP Code: 404, RemoteHost: , RequestID: 307T495ZWHG4N26M, ExceptionName: NoSuchKey, ErrorMessage: The specified key does not exist. , Extra: Could not list objects in bucket cxxx-xxy with prefix /byconity0/bb6ddf05-3863-ac0a-478e-43ff84771ba6/ SQLSTATE: HY000, Stack trace (when copying this message, always include the lines below):
2024.04.12 02:22:07.652764 [ 686 ] {}  AWSClient: AWS S3 slow read(100ms): https://cxxx-xxy.s3.amazonaws.com/cxxx-xxy?list-type=2&max- keys=1&prefix=%2Fbyconity0%2F48a8e154-335e-0a19-eeba-876679aef136%2F, time = 861ms, header = x-amz-request-id: 307VGAYSA5WMZK7H; x-amz-id-2: NP8Pi8xUp0j+5w4/CHLB5bVxlPYMJp7 GvEdlwM+K3m674IU1s8nZ8ppYKWlnWJcDqXUYH3oynS0 =; Content-Type: application/xml; Transfer-Encoding: chunked; Date: Fri, 12 Apr 2024 02:22:07 GMT; Server: AmazonS3;
May I ask, is there anything else that needs to be configured on byconity?

The problem has been solved. Things you need to pay attention to. After the configuration modification is completed, you need to delete the byconity-server pod and restart it after modifying it again. Thank you.


Fix/drawer on resize

What I did

Fix translation of drawer when the window is resized

The issue could be seen on a iPad pro for example when rotating the tablet or when manually resizing the window

oh nice 👍  thxx 🙇♂

oh nice 👍  thxx 🙇♂


ADC rescale/intercept

For a description of the bug, please see the original post in the PI-CAI forum: https://grand-challenge.org/forums/forum/pi-cai-607/topic/public-training-and-development-dataset-updates-and-fixes-631/?post=1766#1766.

The bug is in the data itself, not the data loader.


deprecate vsphere volume and update migration support detail

This PR is updating https://kubernetes.io/docs/concepts/storage/volumes/#vspherevolume to say in-tree vSphere volume is deprecated.
This PR is also updating instructions for in-tree vSphere volume to CSI migration here - https://kubernetes.io/docs/concepts/storage/volumes/#vsphere-csi-migration
Created PR for dev-1.24 branch as per - https://github.com/kubernetes/website/pull/32807#issuecomment-1092334656
Closed original PR - https://github.com/kubernetes/website/pull/32807
cc: @xing-yang

/lgtm

/sig storage

@divyenpatel, how do you feel about incorporating the feedback so far?

@sftim @xing-yang all comments are addressed.

/lgtm

/approve


Add CEX supply metrics

Needs to be "repaired" when new exchange addresses are detected.

Only doing total cex supply for now. Address counts can wait.


CIO

You mention "Internal network" and "External network". As a reader I need a link to know where to define those. Without such a link you create a lot of hoops and create additional questions. OK in this case I could find a link like https://support.office.com/en-us/article/create-and-manage-an-external-network-in-yammer-04ffd9c0-f004-498f-b058-3ea7da3b7311  but maybe that is not the right link? Since you are creating documentation, make sure that your documentation uses hyperlinks to other relevant/related topics !!
Thank you
Bart

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

ID: 1e905f15-4a16-f03a-47f4-4d1509c465c0
Version Independent ID: 17aff17a-dd89-27fe-61f8-ec3b45939d2e
Content: Yammer networks, groups, and users overview
Content Source: SharePoint/SharePointServer/administration/yammer-networks-groups-and-users-overview.md
Product: sharepoint-server-itpro
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@blouwagie Thank you for this feedback.
I want to make sure these link referances are being addressed. I am making sure the SharePoint team gets this and addresses it properly.
I was able to get this into the backlog for the SharePoint team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@tseward is investigating this issue.

Thank you for for following up. Generally Microsoft should cross reference its own documentation a lot more. Thanks again.
Bart

It looks like Trevor has resolved this issue. I am going to close this as resolved. If this is not resolved please re-open this issue.

I have added 2 links to See Also section, I think you will see it in some days.

@dariomws306 - can you paste the link to the PR in here so it will cross reference? You can just paste the link and it will auto cross link. Going to close this but you can still post the PR for future references. :)

Yes sure @kenwith :
https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/pull/435


Add keras version to the docs and release notes

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/1113/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/1118/


When is TorchScript planed?

I have seen on your ToDo you plan TorchScript compatibility? Can you indicate a timeline for this? I can not support directly, but if I could donate something let me know...

@thhart  Did you already try to export the model as torchscript?

@thhart  Did you already try to export the model as torchscript?


Mention Pinpon in the README

We'd appreciate a mention of Pinpon in the deprecation notice as well. We're up and running for beta customers and will launch publicly soon.
It's the easiest way out there to get a ping pong bot going in Slack.

PR me with what you want! I'll be happy to show alternatives. Maybe..
"For a more complete, and commercial alternative, you can check out Pinpon."


Add Fedora image

Tool name
Fedora
Tool license
mostly GPL
Add or update?

[X] Add
[ ] Update

Desired version
40
Approximate size
No response
Brief description of tool
Please consider having more VM images. In particular, it would be awesome to have Fedora Linux.
I am asking for Fedora specifically because it is a distro which has unique distinct features not available elsewhere. From my recent experience, this is

SELinux. Ubuntu comes with Apparmor by default, and while it is possible to enable SELinux, it requires a reboot which (to my best understanding) is not possible in GHA. In particular, I am a maintainer of https://github.com/opencontainers/selinux Go package, which can't be tested in GHA because, naturally, it needs SELinux for most of its tests.

The wonderful world of Linux doesn't start or end with Ubuntu, and Fedora, in particular, is useful for CI. It is actively developed, has lots of users, backed up by a reputable company (disclaimer: I work for Red Hat, but not on Fedora), and a few things about it are distinctive enough.
NOTE that Fedora provides and maintains cloud images for Azure (which, I believe, is used by GHA) here: https://fedoraproject.org/cloud/download. I believe that just using this image will be sufficient for many use cases.
I am well aware that I can run fedora container, but some features (like SELinux above) can't be used unless supported on the host, and SELinux is one of them. I am pretty sure there are others, I just came across SELinux. Some other requests about having Fedora list other reasons, so let me just list those:

#1443
#45
#898
#2307

The last one is the one I filed almost 4 years ago. It got 40+ likes and a lively discussion. For runc, we ended up using Cirrus CI.

I am not trying to pry or annoy the github team. In https://github.com/actions/virtual-environments/issues/1443#issuecomment-684790353 @maxim-lobanov says:

Since we see popularity of this request, we will keep it on mind and will be able to revisit this decision in future.

So, maybe the time to revisit is? :+1: 😉
URL for tool's homepage
https://fedoraproject.org/cloud/download
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] macOS 15
[ ] macOS 15 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No.
Fedora can be run in a container, but if we need features related to Fedora kernel or systemd, those are impossible to have without running Fedora natively (i.e. not in a container).
Tool installation time in runtime
No response
Are you willing to submit a PR?
yes

I seconded #2307, and my needs have not changed since.
Additionally, I would agree with another comment on that previous issue: Alpine would be good to have as well.
I do not have the infrastructure to maintain self hosted runners, and doing the work inside of a container is not suitable.

Dear @kolyshkin
We acknowledge the need for a Fedora image to be accessible on GitHuh Actions  for executing workflows. Fedora may offer unique capabilities that are not present in the current Ubuntu image  like RPM-based package management, cgroupv2, or new syscalls  etc.
We appreciate your patience while  we validate your request which might require a bit of time for a response

Will this type of image make use of Fedora IoT, CoreOS or something else in this case?

Hi
Following discussions with the appropriate stakeholders, we learned that there are no plans to add  further linux images for  GHA.

Hi
Following discussions with the appropriate stakeholders, we learned that there are no plans to add further linux images for GHA.

Hi Following discussions with the appropriate stakeholders, we learned that there are no plans to add further linux images for GHA.

Which is exactly the point. Ya'll keep telling us that, and we keep opening these issues to communicate that we, the community that uses the product, want and need more. There is no quicker way for a company to drive users to their competitors than to keep ignoring common, high demand, and reasonable asks. This issue has been raised a half dozen times with overwhelmingly positive community response. The complete disregard from the GitHub staff is, frankly, both disappointing and terrifying.

Hi Following discussions with the appropriate stakeholders, we learned that there are no plans to add further linux images for GHA.

I hereby fail to see the reasoning why this is the conclusion behind this kind of closure, while maintaining two linux distributions is considered painful in nature - having fedora is really not a concern when it comes to maintenance management as most people do have the ability to submit pull requests to help resolve problems in the event there is one at some point.
And because of this, this makes me now assume all fedora CLI end-users will now just end up using seperate workflow programs instead to run their tests instead of having to relay on actions directly which is the unfortunate context of it.
Basically the tl;dr: This is informative and unfortunate.


GIF style changes, perform SIMBAD queries directly

Having the diagnose_lc_periodogram function return the gif and perform the simbad query.
This PR will close #62 and close #67.
@Tom please double check that this works. Maybe need to actually return the SImbad query to be able to access the full table.

Ah. Just realized that this PR could be used to specify the GIF path automatically to the "output" folder under 'GIF'. Have the same question about creating as the Corrected_LCs folder.
Maybe @TomWagg could do this quickly while you review the PR? If not I can do it soon.

Okay @tobin-wainer tests all look good and the styling of the GIF looks fantastic. I think TODOs on this PR before merging are:

[ ] Check my suggestion on clarifying the 0.008 number
[ ] Save SIMBAD results tables instead of just printing
[ ] (if you agree) add back the lower/upper widths of the peaks

Okay @tobin-wainer nearly done here - we currently get a message that the SIMBAD table can't save because on the columns is an object.  After that it should work fully and be done.

I think I fixed that Table issue.


Support for retention

Though registry has retention fields, it is never used to support retention.

Remove the retention fields? 😀


Laravel 10.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 9.x.
Before merging, you need to:

Checkout the l10-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: Shift detected GitHub Actions which run jobs using a version matrix. Shift attempted to update your configuration for Laravel 10. However, you should review these changes to ensure the desired combination of versions are built for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/laravel-eloquent-scope-as-select.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "protonemedia/laravel-eloquent-scope-as-select": "dev-l10-compatibility",
    }
}

Finally, run: composer update


Implement getitem and setitem for jitclasses

This PR adds support for __getitem__ and __setitem__ in jitclass definition, i.e. syntax like jitclass_instance[10] = 20 become possible in numba as well as python.
Since calls to __getitem__ are converted to operator.getitem we have to override a global. Also, the unboxing needed a minor adjustment. Everything should be covered by the tests.
Partyly solves https://github.com/numba/numba/issues/1606

Note: needs to be updated when https://github.com/numba/numba/pull/3760 is merged.

#3760 has been merged to master.

#3861 incorporated this, thanks for your efforts @alendit


Duplicated css in output with v4.2 vs v3.1

After updating to 4.2 I saw a massive increase in bundle size for our css. When checking the content it looks like the css had been added to the output file multiple times.
Dependency Versions
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Rollup
import svelte from 'rollup-plugin-svelte';
import css from 'rollup-plugin-css-only'
import resolve from '@rollup/plugin-node-resolve';
import commonjs from '@rollup/plugin-commonjs';
import injectProcessEnv from 'rollup-plugin-inject-process-env';
import outputManifest from 'rollup-plugin-output-manifest';
import json from "@rollup/plugin-json";

export default [
  {
    input:'./client/admin.js',
    output: {
      sourcemap: process.env.NODE_ENV != "production",
      format: 'es',
      name: 'app',
      dir: 'storage/public/resources/site_tmp',
      manualChunks: undefined
    },
    plugins:[
       svelte({ emitCss:true }),
       resolve({ browser: true, dedupe: ['svelte'] }),
       commonjs(),
       json(),
       css({ output: cssFilename }),
       injectProcessEnv({'NODE_ENV': process.env.NODE_ENV == "production" ? 'production' : 'development' }),
       outputManifest({isMerge:true})
    ]
  }

bundle
4.2 Size
3.1 Size
Number of duplicates

admin.css
146kb
106kb
2

editor.css
812kb
147kb
18

site.css
743kb
101kb
15

The number of duplicate copies of the css seems related to the number of dynamic import() statements used within the specific bundle.
Hope that helps you reproduce and fix this issue.

Do you mind checking out https://www.npmjs.com/package/rollup-plugin-import-css or  https://www.npmjs.com/package/rollup-plugin-styles and see if those work for you?
I'm using higher level frameworks nowadays so won't fix bugs. Happy to merge a fix though!

I may just keep using v3.1 for now. I'll check the above out if it becomes necessary.
If you're not planning on supporting this rollup plugin ( which I totally understand BTW ) , it may be worth letting the svelte team know as they still point to it as a way to compile your css. ( https://github.com/sveltejs/rollup-plugin-svelte#extracting-css ).
I'll leave it up to you if you'd like to close this, or leave it open so it doesn't get re-reported. Thanks again.

@crisward FYI I just replaced rollup-plugin-css-only 4.3.0 with rollup-plugin-import-css 3.3.4 and everything worked as before.

Should be fixed in https://github.com/thgh/rollup-plugin-css-only/releases/tag/v4.4.0. Feel free to reopen if it still reproducible.


check for correct github artifact name for test results

the test results artifact is now named testResults-, so look for that one as well.
name the aggregated results with the date of collection if it was a manual run so we know what's in there before downloading it
fix a report cell

Codecov Report

Merging #11372 (b309056) into main (733c47f) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #11372   +/-   ##
======================================
  Coverage     63%      63%
======================================
  Files        476      476
  Lines      33938    33938
  Branches    5497     5497
======================================
  Hits       21550    21550
+ Misses     10338    10337    -1
- Partials    2050     2051    +1

Impacted Files
Coverage Δ

src/platform/common/cancellation.ts
59% <0%> (-10%)
:arrow_down:

src/kernels/execution/notebookUpdater.ts
88% <0%> (-8%)
:arrow_down:

src/kernels/raw/session/rawJupyterSession.node.ts
79% <0%> (-3%)
:arrow_down:

src/kernels/jupyter/jupyterKernelService.node.ts
74% <0%> (-2%)
:arrow_down:

src/kernels/helpers.ts
66% <0%> (-2%)
:arrow_down:

src/platform/common/utils/decorators.ts
90% <0%> (-1%)
:arrow_down:

src/platform/msrCrypto/msrCrypto.js
19% <0%> (+<1%)
:arrow_up:

src/kernels/raw/launcher/kernelProcess.node.ts
73% <0%> (+<1%)
:arrow_up:

src/kernels/installer/productInstaller.node.ts
80% <0%> (+1%)
:arrow_up:

...otebooks/controllers/controllerPreferredService.ts
90% <0%> (+4%)
:arrow_up:

... and 1 more


[reggen] Enum Value Definition Fixes

Reggen has been generating enum values already, directly using the
definitions from the hjson. This causes issues when binary literals are
included in the string, as we don't allow those in C/C++ code, so this
change moves to emitting all values as hexadecimal values.
The other change this makes is to add 'VALUE` between the register
field name and the enum name, so that there are no collisions between
the offset/mask definitions and the enum values.
Closes #3804.

Before:
// Current escalation state of Class D. See also !!CLASSD_ESC_CNT.
#define ALERT_HANDLER_CLASSD_STATE(id) (ALERT_HANDLER##id##_BASE_ADDR + 0xe8)
#define ALERT_HANDLER_CLASSD_STATE_REG_OFFSET 0xe8
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_MASK 0x7
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_OFFSET 0
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_IDLE 0b000
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_TIMEOUT 0b001
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_TERMINAL 0b011
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_PHASE0 0b100
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_PHASE1 0b101
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_PHASE2 0b110
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_PHASE3 0b111

After:
// Current escalation state of Class D. See also !!CLASSD_ESC_CNT.
#define ALERT_HANDLER_CLASSD_STATE(id) (ALERT_HANDLER##id##_BASE_ADDR + 0xe8)
#define ALERT_HANDLER_CLASSD_STATE_REG_OFFSET 0xe8
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_MASK 0x7
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_OFFSET 0
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_IDLE 0x0
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_TIMEOUT 0x1
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_TERMINAL 0x3
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_PHASE0 0x4
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_PHASE1 0x5
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_PHASE2 0x6
#define ALERT_HANDLER_CLASSD_STATE_CLASSD_STATE_VALUE_PHASE3 0x7

Looks good (and should be merged forthwith!) but maybe we should be converting to integers at parse time to avoid this sort of problem in future? (Which would also make the types a bit less unpredictable)

Looks good (and should be merged forthwith!) but maybe we should be converting to integers at parse time to avoid this sort of problem in future? (Which would also make the types a bit less unpredictable)

Totally agree, though validate.py is a bit of a nightmare at the moment. It's fair to say reggen is more spaghetti than code today.

LGTM!


Correct field names in generated channel file

Issue: https://issues.redhat.com/browse/JBEAP-26805
Upstream: #237

@spyrkob thanks!


[BUG] If disk is umounted, replica will not report failure

Describe the bug
Replica will not fail if disk is lazy un-mounted.
To Reproduce
Steps to reproduce the behavior:

Attach a new disk to a node, and add the addition disk to the node, make the disk schedulable.
Disable scheduling on other nodes, so we make sure one replicas will be scheduled to the additional disk.
Create a pod using a volume using: https://raw.githubusercontent.com/longhorn/longhorn/master/examples/pod_with_pvc.yaml
Write some data to the volume
on the node, umount -l <ADDITIONA_DISK_MNT_PATH>
Write some more data to the volume

Expected behavior
Replica scheduled to the additional disk should report failure
Log
instance-manager-replica-logs:
pvc-ecfe07fe-6499-411e-9960-420ebe525d8a-r-b3103e52] time="2020-04-23T19:46:34Z" level=error msg="Fail to get size of file /host/mnt/disk-10gb/replicas/pvc-ecfe07fe-6499-411e-9960-420ebe525d8a-a1dca884/volume-head-001.img"
time="2020-04-23T19:46:34Z" level=error msg="Fail to get size of file /host/mnt/disk-10gb/replicas/pvc-ecfe07fe-6499-411e-9960-420ebe525d8a-a1dca884/volume-snap-38938dbe-382e-4899-aa82-970efa6920b6.img"
time="2020-04-23T19:46:34Z" level=error msg="Fail to get size of file /host/mnt/disk-10gb/replicas/pvc-ecfe07fe-6499-411e-9960-420ebe525d8a-a1dca884/volume-snap-8cdece4e-69f2-4ad6-9e43-6ead267ff3b1.img"

Environment:

Longhorn version: master (v0.8.1-rc2+)
Kubernetes version: v1.17
Node OS type and version: Ubuntu 18.04

Additional context

Also, on step (5), if replica directory is renamed, Replica will not report failure

We need to figure out what's wrong, and then decide if we have to include this in v1.0 release.

More logs & observations:

The related replica can still r/w the current opening files after the lazy unmount, but we need to mark the replica as unavailable/error. Since Longhorn cannot use that replica to do rebuild/snapshot... e.g., Snapshotting the volume after the lazy unmount will lead to the replica becoming error, we can use this in the integration test later.
I am thinking if we can add the data directory (or current volume head file) check here to detect this issue and mark the replica ASAP. But I am not sure if it will degrade the volume performance.

Longhorn manager can detect this lazy unmount and update the disk info:

[longhorn-manager-p7kwx] time="2020-05-04T09:49:11Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"shuo-longhorn-cluster-1-node-2\", UID:\"aad1552d-fdd4-4b7c-b3e0-3d407f0bb03b\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6427723\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Disk extra-disk(/mnt/extra/) on node shuo-longhorn-cluster-1-node-2 is not ready: cannot find disk config file, maybe due to a mount error"
[longhorn-manager-p7kwx] time="2020-05-04T09:49:11Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"shuo-longhorn-cluster-1-node-2\", UID:\"aad1552d-fdd4-4b7c-b3e0-3d407f0bb03b\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6427723\", FieldPath:\"\"}): type: 'Warning' reason: 'Schedulable' the disk extra-disk(/mnt/extra/) on the node shuo-longhorn-cluster-1-node-2 has 0 available, but requires reserved 0, minimal 25% to schedule more replicas"

But there are bugs with the node & disk feature hence the node/disk status cannot be presented correctly:
https://github.com/longhorn/longhorn/issues/1290
https://github.com/longhorn/longhorn/issues/1291

The disk has been umounted, the replica can still access it? It sounds weird. Lazy umount doesn't happen immediately. Can you check what does replica reports when the disk disappeared from the mount table? Where does the replica read from/write to?

-l Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. This option allows a "busy" filesystem to be unmounted. (Requires kernel 2.4.11 or later.)

As I said, the head/snapshots files are kept opening (references exist there) hence r/w contents is fine. The only error the replica will print out is the log Mohamed reports above. Once the replica process tries to reload/refresh the head/snapshots files, the replica cannot fetch the data content anymore.

After the discussion with Sheng, we decide not to fix this as long as the following conditions are satisfied:

The replica can still r/w data after the lazy unmount.
The data won't be written to the underlying root filesystem after the lazy unmount.
The replica can become error immediately when the users try to do snapshot/expansion/...
The written data after the lazy unmount and before the replica becoming error is correct.

The verification steps:

Disable all other disks except for the extra disk in Longhorn.
Create a volume with 1 replica. The only replica should be in the extra disk.
Attach the Longhorn volume. Then format and mount it.
Do lazy unmount for the extra disk. --> The extra disk mount point should belong to the root filesystem and is empty now.
Write some data to somewhere and get the md5sum. Then copy the data to the mounted Longhorn volume. --> The extra disk mount point should be still empty. No data is written into it.
Disable auto salvage in the Setting.
Take a snapshot for the volume after the copy. --> The replica should become error immediately.
Unmount and detached the Longhorn volume.
Remount the extra disk to the mount point. Find the volume head file of the volume replica and mount it somewhere. --> The data md5sum in the mounted volume head file is consistent with the original data md5sum.

There are 3 cases to validate this issue:
Case(1/3): Volume is attached to a node, no process is keeping volume mount directory open
Case(2/3): Volume is attached to a node, process e.g bash is keeping volume mount directory Case(3/3): Volume is used by a Kubernetes workload e.g pod.

For Cases 2 & 3, Validation PASSED,  All data md5sum in the mounted volume head file is consistent with the original data md5sum, and i got the same result as @shuo-wu  described.

For Case1: Only data written before lazy unmount existed,

Validation steps are:

Disable all other disks except for the extra disk in Longhorn.
Create a volume with 1 replica. The only replica should be in the extra disk.
Attach the Longhorn volume. Then format and mount it.
Write some data data1 to the volume and get the md5sum#1.
make sure your working directory is no the mount point for the volume. e.g cd /
Do lazy unmount for the extra disk. --> The extra disk mount point should belong to the root filesystem and is empty now.
Write some data  data2 to somewhere and get the md5sum#2. Then copy the data to the mounted Longhorn volume. --> The extra disk mount point should be still empty. No data is written into it.
Disable auto salvage in the Setting.
Take a snapshot for the volume after the copy. --> The replica should become error immediately.
Unmount and detached the Longhorn volume.
Remount the extra disk to the mount point. Find the volume head file of the volume replica and mount it somewhere. --> Only data1 which checksum is md5sum#1 existed
can't find data2

Unfortunately, I cannot reproduce it but I find another issue. Here are my reproducing steps & results:

Mount the extra disk on node-2:

root@shuo-longhorn-cluster-1-node-2:~# ls  /mnt/extra/
root@shuo-longhorn-cluster-1-node-2:~# mount /dev/disk/by-id/scsi-0Linode_Volume_s /mnt/extra

Create a volume with the only replica and attach it to node-1 on UI. Then format and mount it.

root@shuo-longhorn-cluster-1-node-1:~# mkfs.ext4 /dev/longhorn/vol1
mke2fs 1.44.1 (24-Mar-2018)
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: 6acdb145-293d-4147-9efa-2e245ab4a9fa
Superblock backups stored on blocks:
	32768, 98304, 163840, 229376, 294912

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
root@shuo-longhorn-cluster-1-node-1:~#
root@shuo-longhorn-cluster-1-node-1:~# mkdir /mnt/vol1
root@shuo-longhorn-cluster-1-node-1:~# mount /dev/longhorn/vol1 /mnt/vol1/

Prepare some data then copy data t1 to the volume on node-1:

root@shuo-longhorn-cluster-1-node-1:~# dd if=/dev/urandom of=/tmp/t1 bs=1M count=100 && md5sum /tmp/t1
100+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 2.0855 s, 50.3 MB/s
7aa5be6dc230216a8441de52a0778d43  /tmp/t1
root@shuo-longhorn-cluster-1-node-1:~#
root@shuo-longhorn-cluster-1-node-1:~#
root@shuo-longhorn-cluster-1-node-1:~#
root@shuo-longhorn-cluster-1-node-1:~# dd if=/dev/urandom of=/tmp/t2 bs=1M count=100 && md5sum /tmp/t2
100+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 2.14411 s, 48.9 MB/s
f6adfe2954486997d1b216895311528b  /tmp/t2

root@shuo-longhorn-cluster-1-node-1:~# dd if=/tmp/t1 of=/mnt/vol1/t1
204800+0 records in
204800+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.47432 s, 221 MB/s
root@shuo-longhorn-cluster-1-node-1:~# sync
root@shuo-longhorn-cluster-1-node-1:~#

Do lazy umount on node-2:

root@shuo-longhorn-cluster-1-node-2:~# umount -l /mnt/extra

Copy data t2 to the volume on node-1:

root@shuo-longhorn-cluster-1-node-1:~# dd if=/tmp/t2 of=/mnt/vol1/t2
204800+0 records in
204800+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.562762 s, 186 MB/s
root@shuo-longhorn-cluster-1-node-1:~# sync

Do snapshot for the volume on UI. Then the volume will become Faulted.
Unmount the Faulted Longhorn volume:

root@shuo-longhorn-cluster-1-node-1:~# umount /mnt/vol1

Remount the extra disk on node-2, then check the volume head file of the volume replica:

root@shuo-longhorn-cluster-1-node-2:~# ls  /mnt/extra/
root@shuo-longhorn-cluster-1-node-2:~# mount /dev/disk/by-id/scsi-0Linode_Volume_s /mnt/extra
root@shuo-longhorn-cluster-1-node-2:~# mkdir /mnt/head
root@shuo-longhorn-cluster-1-node-2:~# mount /mnt/extra/replicas/vol1-23189d6d/volume-head-000.img /mnt/head

root@shuo-longhorn-cluster-1-node-2:~# md5sum /mnt/head/t1 /mnt/head/t2
7aa5be6dc230216a8441de52a0778d43  /mnt/head/t1

For both nodes, the working directory is always /root.
The issue I encounter here is that the file md5sum calculation in step 8 is pretty slow. One 100Mi file can take more than 10 minutes. There is no error either in dmesg log, or in fsck <the volume head file> result. I don't know what's wrong.

I couldn't reproduce the issue for a second time

Hi All,
Unfortunately, I couldn't reproduce both @meldafrawi  and @shuo-wu issues.
@meldafrawi has updated with his latest verification, we don't see that issue.
I have also tried @shuo-wu 's steps from the latest comment. For me it takes about under 1s to get the md5sum for the second data file after the extra disk lazy umounted from node 2.
One thing I noticed it during lazy umounted, if we write anything to the volume, it will still writing to the extra disk. I use iostat -x /dev/disk/by-id/scsi-0Linode_Volume_linode-vol-2 1 200 to monitoring the disk activities all the time, and I see the writing rate during lazy umounted.
I think one possibility for Shuo to get the md5sum that long might because of system load was high maybe during the writing and the command itself time. Could you give this another try?
Thanks.

@shuo-wu Can you check if it's the case that @boknowswiki described?

I cannot reproduce it, either. Maybe the slow md5sum calculating is caused by the heavy system load.
Thank you for Bo's verification!


Support open ranges

Sometimes there are hyperparameters that are defined within an open or semi-open range, like [0, 1).
These cases are not natively supported right now, and the only option for the user is to manually add or substract an epsilon to the range edge.
For example, the [0, 1) case above could be covered like this:
HyperParameter(ParamTypes.INT, [0, 1 - 1e-12])

Should we figure out a way to support this natively in BTB?
One option would be having upper_open/lower_open or upper_included/lower_included flags:
HyperParameter(ParamTypes.INT, [0, 1], upper_open=True)   # this means [0, 1)

This is solved after the #132  implementation. Now we work with

include_min (bool): Wheither or not to include the minimum value in the search space.
include_max (bool): Wheither or not to include the maximum value in the search space.


Settings

[ ] Parse Settings File
[x] Retrieve Settings on request with required defaults
[x] Update Settings values

Hello, I just wanted to share some thoughts.
What are these settings for exactly? Perhaps a concrete example might help reduce implementation efforts.
Is it for engine-specific properties? Or can it be a generic system for engine plus game? Should the settings be split?
Hope these questions help define the issue better.

I think we can close this issue without the parsing from file.
We should assume that something external to the Settings singleton will populate it.
Potentially calling setString will be enought right now


Better branch likelyness on stable

It uses uses the #[cold] attribute to get a similar effect as core::intrinsics::{likely, unlikely} on stable (10-15% on some benchmarks)

@bors r+

:pushpin: Commit bbda6e0077bafb75c02d0ace665faa09b4514932 has been approved by Amanieu

:hourglass: Testing commit bbda6e0077bafb75c02d0ace665faa09b4514932 with merge a301ff004a902816878b3029c5e4a90d7c7e9dc1...

:sunny: Test successful - checks-travis
Approved by: Amanieu
Pushing a301ff004a902816878b3029c5e4a90d7c7e9dc1 to master...


Fails to create project with Could not find resource charts.bitnami.com; type repo in Projects configuration

https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project_repo.go#L162
If we try to create a project and the artifactory already have repositories shared with all projects, it fails to create project with the following error message:
╷
│ Error: failed to delete repos for project: failed to delete repo charts.bitnami.com:
│ 404 DELETE <OMITTED_JFROG_URL>/access/api/v1/projects/_/attach/repositories/<REPO_KEY>
│ {
│   "errors" : [ {
│     "code" : "NOT_FOUND",
│     "message" : "Could not find resource `<REPO_KEY>`; type `repo` in Projects configuration"
│   } ]
│ }
│

provider version 1.1.7
jfrog version, enterprise plus latest available.
test case:
create remote repo, share with all projects:

if we create the project via UI, the remote gets created successfully.
if we create the project using this provider, it fails with the above error message.
what I expect: projects to be created.

from my humble understanding of golang, I traced to the following:
first create project
https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project.go#L342
calls update repos
https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project.go#L374
calls readRepos
https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project_repo.go#L81
and fetches the projects:
https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project_repo.go#L57
it returns the available shared repos as "to be deleted" and tries to delete
https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project_repo.go#L101
then it fails here
https://github.com/jfrog/terraform-provider-project/blob/8462602f6c1239ce25867536052b4d6db8642024/pkg/project/resource_project_repo.go#L156
I could not find a proper GET to see if repo is sharedWithAllProjects, but I found this rest call via UI
https://<JFROG_INSTANCE>/ui/api/v1/ui/admin/repositories/remote/info?projectKey=unassigned
that returns a json list with the following:

so there is a way to check. Can we check if the repo is already shared in the updateRepos or readRepos method??

@EvertonSA Unfortunately, that API endpoint is private and only should be used for JFrog's UI. The public API doesn't contain that field, yet.

@alexhung is there another way to fetch sharedWithAllProducts? there must be a way

it must be a way, if there is no way, then we need to request a way

@alexhung I have opened a internal jfrog request, ticket number 220316. Can you help me internally to get this somehow solved?

I have also tried to add all sharedWithAllProjects repositories to repos and it suceeds to create, but it fails to delete with same error

i will test with version 1.1.8, because I think if we have the shared remotes already in the project config this might work.

@alexhung my assumptions are correct and version 1.1.8 correct this.


fix(3232): fix R.groupBy when used as transducer

It fixes #3232

Sorry, I didn't see jaawerth fix. I'm gonna close it.

While I did submit  quick-and-dirty fix, I think yours might actually be better - I think the problem is that transducers are inherently stateful (especially in the step function), they just happen to hide the state under the hood (this being a huge optimization in clojure, or in JS using ImmutableJS, since you can use transient mutable versions of your immutable structures to save the overhead while still looking stateless to the outside observer:
I don't know this codebase super well, but if I had to guess, I think your fix could end up solving similar issues if there are other "also usable as a transducer" reductions that aren't being tested in transducer form.
.
The step function in particular is often some kind of state mutation, just bookended betwen the init and result functions, though in JS this is a bit made up as we go since clojure gets immutability for free and outright names the mutable versions of its structures "transients".
Other JS implementations of transduce, I usually see this handled by the final transform created by e.g. into, where into([], ...) "clones" the array when it's empty, but if a populated plain object/array is passed in, they just mutate, or leave it up to a @@transducer/init function to take care of things. I don't know what'd be best for ramda, just figured it'd be worth mentioning.

Ok, I'm gonna open the PR because my solution seems more consistent with the no-transducers implementation.
After reading what you say, @jaawerth, I don't like to much the _clone approach we have in functions like into and maybe delegating in @@transducer/init function is better. But I think it's something that I have to review more deeply. Having the same solution than the default implementation can reduce the number of unexpected behaviours now.

I am having a busy week so worse case scenario I'm going to look at this over the weekend. But thank you both for coordinating your efforts. It's great to see 🙇♂

Sorry for introduce the bug, I wll see what happen here,

I spend some time to see the source code of groupBy, reduceBy and _xreduceBy , find out that this fix is more robust.
When using reduce and reduceBy, People should not mutate the acc in place in general. But groupBy has break this rule for performance, and use one hack method to let itself behave normally, as follows:
var groupBy = _curry2(_checkForMethod('groupBy', reduceBy(function(acc, item) {
  if (acc == null) {
    acc = [];
  }
  acc.push(item);
  return acc;
}, null)));

when groupBy act as a transducer, if acc is null, this means it's a new subgroup iteration, then groupBy make a new empty array [] to subgroup, then each subgroup has its own acc.

All other Ramda apis base on reduceBy (countBy, indexBy) don't have the same problem, because they do not mutate acc in place.
var countBy = reduceBy(function(acc, elem) { return acc + 1; }, 0);

var indexBy = reduceBy(function(acc, elem) { return elem; }, null);


Error when trying to check my profile.

Describe the bug
I get the error that can be seen in my screenshot only whentryng to check my profile. It doesnt happen when i try other profiles and ive tried at least 10.
Profile/Location
Expected behavior
Id expect to be able to see my profile.
Screenshots

Desktop (please complete the following information):

OS: [Windows 10]
Browser Vivaldi
Version idk where i can check that on this browser

Smartphone (please complete the following information):

Device: S21fe
OS: Android 13
Browser chrome

Additional context
Another weird bug that happes on my phone is that when trying to check my profile the verification keeps going in a loop(im talking about the check if youre a robot thingy). Ive tried to do it multiple times and it also happens only on my profile. At the moment i get the same error i get on my pc so i cant send a screenshot.

Fixed by #1902, not in production yet

Regarding

Another weird bug that happes on my phone is that when trying to check my profile the verification keeps going in a loop(im talking about the check if youre a robot thingy). Ive tried to do it multiple times and it also happens only on my profile. At the moment i get the same error i get on my pc so i cant send a screenshot.

That's due to cloudflare we cannot do anything about that

alright thank you idk if i should close the issue or not so you do it

alright thank you idk if i should close the issue or not so you do it

Better close it, so solved issues don't stack up


PDE Solving Demo?

I've noticed that in the PDE solving demo the ground truth solution for the PDE is used to evaluate the boundary condition loss and is thus used in the training process.
            # boundary loss
            bc_true = sol_fun(x_b)
            bc_pred = model(x_b)
            bc_loss = torch.mean((bc_pred-bc_true)**2)

Doesn't this defeat the entire purpose of using KAN models to solve PDEs? Have you tried training a KAN without giving the model previous knowledge of the ground truth solution?

By simply commenting out the bc loss contribution to the loss calculation and backward step I was able to get similar activation functions in the trained KAN.

Training on just interior points has yielded a similar result for this simple demo. Have you tried implementing other methods for training on the boundary that do not rely on knowing the solution to the PDE?

Hi, to solve a PDE, we need both the PDE and boundary condition? Very likely I didn't fully get your question, but in case you find this helpful: https://en.wikipedia.org/wiki/Physics-informed_neural_networks

I've noticed that in the PDE solving demo the ground truth solution for the PDE is used to evaluate the boundary condition loss and is thus used in the training process.
            # boundary loss
            bc_true = sol_fun(x_b)
            bc_pred = model(x_b)
            bc_loss = torch.mean((bc_pred-bc_true)**2)

Doesn't this defeat the entire purpose of using KAN models to solve PDEs? Have you tried training a KAN without giving the model previous knowledge of the ground truth solution?

I was able to solve PDE (navier-stokes) without true solution only with differential equations and boundary conditions https://github.com/KindXiaoming/pykan/blob/master/tutorials/physics_informed_kan.ipynb


Motion tracking

Now that we are working on custom user input devices, it would be interesting to see what we can do with motion tracking.

I wonder if we can get a system for PlayStation Move working:

[ ] Get the PS3 Eye cam working on OSX (macam?)
[ ] Activate the light bulb on the Move controller (can this be handled through SDL2?)

I don't have time for doing this now and it's not required in order to get other stuff done. Closing.


Extra footer removed

🛠 Fixes Issue
Closes #268

👨💻 Changes proposed

Removed the extra footer present in the code.
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

can you attach ss @Rakesh9100

Sure !!!


fix(sqllab): avoid unexpected re-rendering on DatabaseSelector

SUMMARY
Reopen: #21141
Since DatabaseSelector component has an unnecessary key, DatabaseSelector will be re-mounted  rather than update whenever currentDatabase object is updated. This causes the unexpected duplicate database list api request.
This commit removes this key so will skip unnecessary re-rendering and data fetching.
It also fixes the logic for currentDb that directly transform from db instead of useState. (This resolves the issue for #21174)
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:

After:

TESTING INSTRUCTIONS
go to Sql Editor and check the network list
ADDITIONAL INFORMATION

[x] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

cc: @ktmud

Is there a reason for removing AsyncSelect useEffect dependencies?

@michael-s-molina Because fetchPage kept changing while initializing due to the object dependencies, useEffect has been triggered multiple times which causes unnecessary fetchPage calls.
I made a change to reduce and fix the dependencies for fetchPage and rollback this useEffect dependencies.

Is there a reason for removing AsyncSelect useEffect dependencies?

@michael-s-molina Because fetchPage kept changing while initializing due to the object dependencies, useEffect has been triggered multiple times which causes unnecessary fetchPage calls.
I made a change to reduce and fix the dependencies for fetchPage and rollback this useEffect dependencies.

@justinpark We can't add the responsibility of the immutability of the options to the Select component because there are some cases where we want to fire the requests again when the function changes. To fix your problem, you just need to make sure options only change when you in fact want them to. This is generally accomplished by the use of useMemo or useCallback on the parent component depending on the case.

Is there a reason for removing AsyncSelect useEffect dependencies?

michael-s-molina Because fetchPage kept changing while initializing due to the object dependencies, useEffect has been triggered multiple times which causes unnecessary fetchPage calls.
I made a change to reduce and fix the dependencies for fetchPage and rollback this useEffect dependencies.

justinpark We can't add the responsibility of the immutability of the options to the Select component because there are some cases where we want to fire the requests again when the function changes. To fix your problem, you just need to make sure options only change when you in fact want them to. This is generally accomplished by the use of useMemo or useCallback on the parent component depending on the case.

Okay. @michael-s-molina   I finally cleaned up the main cause.

I removed the unnecessary sort function dependency on mergeData because fetchOptions resolver only cares the length(so sorting is unnecessary and heavy).

https://github.com/apache/superset/blob/b739e27f6dc4b159d766074e3e353a5546d00adb/superset-frontend/src/components/Select/AsyncSelect.tsx#L340-L346

I fixed the invalid checking for setAllValuesLoaded. (Since allValuesLoaded should check whether the current request is for the full list or not, it should check the search rather than `value)

When removes the key in DatabaseSelector, its initial database selection has gone. (#21174) The issue is caused by the missing currentDb mapping when db prop is updated. I added the useEffect logic to handle this issue.

https://github.com/apache/superset/blob/b739e27f6dc4b159d766074e3e353a5546d00adb/superset-frontend/src/components/DatabaseSelector/index.tsx#L135-L144

Lastly I found the same useEffect logic on AsyncSelect so removed one

https://github.com/apache/superset/blob/b739e27f6dc4b159d766074e3e353a5546d00adb/superset-frontend/src/components/Select/AsyncSelect.tsx#L473-L477
https://github.com/apache/superset/blob/b739e27f6dc4b159d766074e3e353a5546d00adb/superset-frontend/src/components/Select/AsyncSelect.tsx#L513-L517


Number Deserialization

The class-transformer library converts NaN values to null values. This is documented, but it's not ideal. The work around is currently to use the attached method on component as follows:
class MyComponent {
  myNum = NaN

  attached () {
    this.myNum = this.myNum == null ? NaN : this.myNum
  }

Potentially a better solution is given a numeric type annotation like this:
  @Type (() => Number)  myNum = NaN

That pickle would, upon deserialization, automatically convert the null to NaN.

Implemented & documented. Use the @Num decorator:
class MyComponent {
@Num myNum = NaN
}


[Collections] add should only add to config if fetch is successful

Motivation:
The code currently adds a collection source to the config even when initial fetch fails.
Modifications:
We should fetch collection first and make sure that's successful before adding to config.
Result:
Bad sources are not added to the config.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Method name mismatch

Update method name in disco_sns to topic_arn_from_name from topic_arn_by_name as it is not defined.
Traceback:
File "disco_aws_automation/disco_sns.py", line 123, in update_sns_with_notifications
topics_to_delete_arn = [self.topic_arn_by_name(topic) for topic in topics_to_delete]
AttributeError: 'DiscoSNS' object has no attribute 'topic_arn_by_name'

:+1 :


[Bug]: When exporting synonyms, after checking CREATE and adding DROP before it, the content of the exported file has a syntax error.

ODC version
ODC424
OB version
independent
What happened?
When exporting synonyms, after checking CREATE and adding DROP before it, the content of the exported file has a syntax error.

What did you expect to happen?
correct
`DROP PUBLIC SYNONYM EXISTING_SYNONYM;
CREATE OR REPLACE PUBLIC SYNONYM SMTPTransport FOR schema.SMTPTransport;`
How can we reproduce it (as minimally and precisely as possible)?
。
Anything else we need to know?
No response
Cloud
No response

pass


Fixed #36026 -- Updated the class-based View's documentation to explain the setup function

Trac ticket number
ticket-36026
Branch description
Provide a concise overview of the issue or rationale behind the proposed changes.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] I have attached screenshots in both light and dark modes for any UI changes.

As this is not specific to dynamic filtering, I think the View.setup() docs should be updated instead

Hey @sarahboyce, you're right. Updated the position of the wording to be in the Base View documentation. Let me know if this looks good and the wording is fine.


Glider Markers

Hi Rik,
Can you add the following to the GLID marker please.
ARCE
A32P
A34E
AS16
AS22
AS24
AS26
G109
PK11
PK15
PK18
PK21
PK23
PK25
RF10
S6
S12
SF24
SF25
SF28
SF35
SG37
SZ45
DIMO

KIWI

Rik,
I tried all the ones you just added to Glider and all appear to work. The ARCE & A34E show as Single Electric and the rest show as Single Piston. All show as a Glider marker on my VRS.
Mac,

These were updated as a request from another user. And here in lies the eternal question of points of view. 🤣
As they are power gliders they felt they were better suited to a glider marker rather than a generic GA/Light aircraft.
I think my solution would be to create another glider like marker, but with a slightly shortened span... thoughts welcomed

@Jonboy1081 care to comment?

I know very little of gliders and even less of the powered one. I think the current glider marker works fine. Just my personal thought on the subject.
Mac

If you're OK with them as they are then I'll close this issue down again.
In future I may do a power gliders marker for things like the DIMO, SF25, RF10 style power gliders as these were designed as such and leave the powered gliders in the gliders section

I'm good with glider and motors gliders having the GLID marker, they all look the same up in the air. :)


Flaky tests: ConfigurationTests.CreatingWritingDeletingCreatingFileWillReload ConfigurationTests.TouchingFileWillReload

These tests have recently taken to failing on OSx: http://aspnetci/project.html?projectId=XPlat&buildTypeId=XPlat_Mac_MacUniverseCoreCLR&tab=testDetails&testNameId=3759396832575739260&order=START_DATE_DESC&branch_XPlat=all_branches&itemsCount=50
Offending tests include:

ConfigurationTests.CreatingWritingDeletingCreatingFileWillReload
ConfigurationTests.TouchingFileWillReload

Assert.Equal() Failure
                   ↓ (pos 9)
Expected: JsonValue2
Actual:   JsonValue1
                   ↑ (pos 9)
   at Microsoft.Extensions.Configuration.Test.ConfigurationTests.<TouchingFileWillReload>d__32.MoveNext() in /_/test/Config.FunctionalTests/ConfigurationTests.cs:line 598
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

A non-exhaustive list of the builds affected by this can be found here.
Split off from aspnet/DotNetTools#412.

No recent test failures.


fix: remove line in gitignore to track debug keystore

Fixes #58
Changes

update the .gitignore so that we don't ignore the debug.keystore in the android/app directory.

@cmejet mentioned

Have to be careful that it never includes the release keystore

Is this fix okay, or do you have suggestions on something that might work better?

@jsjoeio I think this is the best method for now. If we know the file name of the release keystore which I think is not really possible as it can have any name. Debug is usually the only one with the same name.


There was an error processing your data

Hi, I'm not sure why, but I'm getting an error every time I try to upload the "Apple Music Play Activity.csv" file. The file was in "Apple Media Services information" > "Apple Media Services" > Apple Music Activity" as there was not a folder named "App_Store_iTunes_Store_iBooks_Store_Apple_Music"
But I'm sure the file I'm uploading is "Apple Music Play Activity.csv"

I have the same issue. I checked the column names against the list and they are all the same.

I tried to submit a commit. Basically Apple Music Play Activity.csv now has the columns come in alphabetical order which is not how the script currently parses it (the current order seems more random).
In the meantime, you have to manually reorder your CSV file through OpenOffice Calc or Excel. It is a pain, but the only way to make it work.
Current parsing order:
const keys = [
"Apple Id Number",
"Event End Timestamp",
"Event Received Timestamp",
"Device Identifier",
"Build Version",
"Milliseconds Since Play",
"Source Type",
"Metrics Bucket Id",
"Event Start Timestamp",
"Feature Name",
"Store Country Name",
"Start Position In Milliseconds",
"Play Duration Milliseconds",
"Event Type",
"End Position In Milliseconds",
"Metrics Client Id",
"Media Type",
"End Reason Type",
"Item Type",
"Event Reason Hint Type",
"Media Duration In Milliseconds",
"Offline",
"UTC Offset In Seconds",
"Apple Music Subscription",
"Client IP Address",
"Content Provider",
"Content Name",
"Genre",
"Artist Name",
"Content Specific Type",
"Original Title"
];

That seems to work. I still had some issues with a year being NaN and the stats being off but it parses.


weak module ships with debug symbols

We should do the same tricks we do for oniguruma for the weak module (4.7MB)

Nice! Thank you!


Column names in sample data in code snippet should'not be diffrent  from the dataset column names

Model Builder Version: In which Model Builder version was the bug encountered?
Visual Studion Version: In which Visual Studio version was the bug encountered?
Bug description
Steps to Reproduce

select  value prediction scenario
Load data
Complete training
Go to consume page and compare sample data column with dataset columns in the data page preview

Expected Experience
Sample data in the code snippet should have the same column name with dataset column names
Actual Experience

Additional Context
Add any other context about the problem here, such as unusual system configurations, network restrictions, etc.

This is not a bug  for a console app.

This is not an issues


Error issues with connection

Hi
I had been using the code for a while and then recently the same code will not translate -  states that the error is related to the Json request.  Have Google changed the API?
Thanks

Same problem.

saw that the Google has withdrawn the API: https://github.com/terryyin/google-translate-python

I will check it out soon within a week.

I checked this issue in my dev environment and it seems it works, however, probably Google is now blocking some requests which are either unusual activity or uncharacteristic activity. So in that case, you can check the page that requires you to solve the captcha to continue; you guys need to use proxy server, or change your ip address in order to be able to continue.