Is justinrainbow/json-schema absolutely required?

Is it possible to drop the dependency on justinrainbow/json-schema? My project is locked at version 2.0 of this library, and consequently, we cannot use localheinz/composer-normalize. Alternatively, can support be extended back to version 2.0?
If it is only required by SchemaNormalizer, perhaps it can be moved to a suggested dependency instead, and code be added to SchemaNormalizer to check if the library is available and emit an exception if it is not. In this way, consumers that do not want SchemaNormalizer do not need to load the dependency on justinrainbow/json-schema. It seems to me localheinz/composer-normalize is one such library that does not actually use SchemaNormalizer in the current version.

@Bilge
Actually, SchemaNormalizer is the core of localheinz/composer-normalize!


Add download task inputs

This PR adds functionality for users to download task inputs. It includes refactoring output download functions to adapt and reuse the same logic for input downloads. It also adds the functionality to CLI.
Example:
import inductiva

task = inductiva.tasks.Task("123456789")

# download all inputs
task.download_inputs()

# select some input files to download
task.download_inputs(
    input_dir='json-file-and-control-txt',
    filenames=['input.json', 'control.txt'],
)

I don't think we should allow to use --input and --output. That would make the filenames a bit confusing. By only allowing one or the other (or none) we keep the behaviour similar to the python code where you can either download outputs or inputs with one command.

I don't think we need that extra verification. I also believe it's a useful feature: if you pass --input and --output, the files are downloaded into the inputs/ and outputs/ folders, respectively. So, I don't see how the filenames could be confusing.

I don't think we should allow to use --input and --output. That would make the filenames a bit confusing. By only allowing one or the other (or none) we keep the behaviour similar to the python code where you can either download outputs or inputs with one command.

I don't think we need that extra verification. I also believe it's a useful feature: if you pass --input and --output, the files are downloaded into the inputs/ and outputs/ folders, respectively. So, I don't see how the filenames could be confusing.

Because the inputs and outputs might not have the same files. What would happen if you send a file that is present on the inputs but not on the outputs ? will it result in an error or just download the files that ir can for both ?

I don't think we should allow to use --input and --output. That would make the filenames a bit confusing. By only allowing one or the other (or none) we keep the behaviour similar to the python code where you can either download outputs or inputs with one command.

I don't think we need that extra verification. I also believe it's a useful feature: if you pass --input and --output, the files are downloaded into the inputs/ and outputs/ folders, respectively. So, I don't see how the filenames could be confusing.

Because the inputs and outputs might not have the same files. What would happen if you send a file that is present on the inputs but not on the outputs ? will it result in an error or just download the files that ir can for both ?

It would just download the files that it can for both -- it wouldn't result in an error. But I could decouple more the download of input and output files.


Play mode Editor - Hierarchy

When hitting play and clicking on a card it or if the card is highlighted before hitting play, it generates the same card over and over in the hierarchy.

This is fixed.


Add a just ps recipe for displaying service ports

Fixes

Fixes #667 by @zackkrida
Description

This PR adds a recipe ps that invokes a Python script to parse the output of docker-compose config and generate a list of URLs for each running service. This recipe runs right after just up.
It currently does not see to verify if something is indeed running at that URLs (notably API port 50230, which is usually bound but rarely used).
This is a follow-up based on @dhruvkb's work in https://github.com/WordPress/openverse-api/pull/959. It seems that some of the trouble of the last approach was using an API that was only available on newer version of Docker. My version (Docker version 20.10.21) doesn't even have the docker compose command and I'm running docker-compose v1, so I opted to take a different approach entirely (the one I initially suggested in the issue. The downside is this does require pyyaml, but I've added a note about that in cases where it's not available in the environment.
Example with pyyaml available
$ j up
env COMPOSE_PROFILES="api,ingestion_server,frontend" docker-compose -f docker-compose.yml up -d
openverse_upstream_db_1 is up-to-date
openverse_db_1 is up-to-date
openverse_cache_1 is up-to-date
openverse_plausible_db_1 is up-to-date
openverse_plausible_ch_1 is up-to-date
openverse_es_1 is up-to-date
openverse_plausible_1 is up-to-date
openverse_web_1 is up-to-date
openverse_indexer_worker_1 is up-to-date
Starting openverse_proxy_1 ...
Starting openverse_proxy_1 ... done

================================================================================
                                    Services
================================================================================
cache:
-  http://<IP_ADDRESS>:50263 (→ 6379)
db:
-  http://<IP_ADDRESS>:50254 (→ 5432)
es:
-  http://<IP_ADDRESS>:50292 (→ 9200)
ingestion_server:
-  http://<IP_ADDRESS>:50281 (→ 8001)
plausible:
-  http://<IP_ADDRESS>:50288 (→ 8000)
proxy:
-  http://<IP_ADDRESS>:50200 (→ 9080)
- https://<IP_ADDRESS>:50243 (→ 9443)
web:
-  http://<IP_ADDRESS>:50280 (→ 8000)
-  http://<IP_ADDRESS>:50230 (→ 3000)
================================================================================

Example without pyyaml
$ j up
env COMPOSE_PROFILES="api,ingestion_server,frontend" docker-compose -f docker-compose.yml up -d
openverse_plausible_ch_1 is up-to-date
openverse_es_1 is up-to-date
openverse_upstream_db_1 is up-to-date
openverse_db_1 is up-to-date
openverse_cache_1 is up-to-date
openverse_plausible_db_1 is up-to-date
openverse_indexer_worker_1 is up-to-date
openverse_web_1 is up-to-date
openverse_plausible_1 is up-to-date
Starting openverse_proxy_1 ...
Starting openverse_proxy_1 ... done

Port configuration for the services can be displayed by installing the Python package 'pyyaml'.

Testing Instructions

Checkout this PR and run just up.
See the list of services being printed automatically after up is complete.
Run just ps.
See the list of services.

Checklist

[x] My pull request has a descriptive title (not a vague title like
Update index.md).
[x] My pull request targets the default branch of the repository (main) or
a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible
errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Just noting that Compose v1 is nearing EOL, so we must consider that aspect too.

Definitely. I don't think we should be expected to support v1 at all. docker compose is the standard way to call to compose now. However, really annoyingly, Debian still uses v1, even on sid: https://packages.debian.org/sid/docker-compose
I suspect that's why Madison is still on v1 as IIRC she runs Kubuntu on her dev machine.

Thanks for your feedback @sarayourfriend and @dhruvkb 🙂 I specifically wanted to support v1 with this effort because (as Sara mentioned) that's the default for Ubuntu which is what I'm on. I'm not even sure how I would go about updating docker so that it supports docker compose since I installed it the standard/canonical way. We'd have to provide explicit instructions for folks using Ubuntu variants if we wanted to enforce that for the time being 😞
What I didn't realize was that we could employ filters and formatting directives to docker ps - thanks for that Sara! I'll rework the PR to remove the pyyaml dependency and use that instead. I do like how we parse the output and format it as clickable links, I feel that could be helpful for users so I'll try to maintain that even if it adds complexity to the recipe.

Okay I think I've got an implementation working with docker ps!
================================================================================
                                    Services
================================================================================
proxy:
-  http://<IP_ADDRESS>:50243 (→ 9443)
-  http://<IP_ADDRESS>:50200 (→ 9080)
ingestion_server:
-  http://<IP_ADDRESS>:50281 (→ 8001)
plausible:
-  http://<IP_ADDRESS>:50288 (→ 8000)
web:
-  http://<IP_ADDRESS>:50230 (→ 3000)
-  http://<IP_ADDRESS>:50280 (→ 8000)
cache:
-  http://<IP_ADDRESS>:50263 (→ 6379)
es:
-  http://<IP_ADDRESS>:50292 (→ 9200)
db:
-  http://<IP_ADDRESS>:50254 (→ 5432)
================================================================================

@sarayourfriend and @dhruvkb - do you mind trying this change out and seeing if it's suitable?

@AetherUnbound That looks great, but I think my suggestion may have been misunderstood. If we're going to transform the output, I think it was simpler using just dc config, but we could remove the pyyaml dependency by pasing --format json to get it back as JSON and parse it with Python's standard library json. The implementation was a lot cleaner using the config output, so I'd suggest switching it back. Apologies for not being clear in the feedback.
I believe the issue with docker-compose vs docker compose shouldn't be an issue though, right? We use just dc for lots of the regular commands for setting up and tearing down the services locally and we should be able to continue to do so. On my local docker-compose appears to just be an alias for docker compose anyway :thinking: I might be misunderstanding what the issue was with docker-compose vs docker compose was though. Does the macOS Docker Desktop installation not add docker-compose as an alias for the compose plugin?

Unfortunately the problem with using --format json is that it is not available for docker-compose v1 (discussed here):
docker-compose config --format=json
Validate and view the Compose file.

Usage: config [options]

Options:
    --resolve-image-digests  Pin image tags to digests.
    --no-interpolate         Don't interpolate environment variables.
    -q, --quiet              Only validate the configuration, don't print
                             anything.
    --profiles               Print the profile names, one per line.
    --services               Print the service names, one per line.
    --volumes                Print the volume names, one per line.
    --hash="*"               Print the service config hash, one per line.
                             Set "service1,service2" for a list of specified services
                             or use the wildcard symbol to display all services.

That was why I switched back to using docker ps and processing its output.

Ohhhhhhh :facepalm: Okay, now I understand what the issue was, I'm so sorry!
This looks great to me then. I'm glad there was a workaround available :grin: Sorry again for the confusion!

All good! It's so frustrating because there are all these more useful feature available, but my system (and Ubuntu in general I suppose?) just don't have access to them 😭😭 I'm so glad you pointed out the docker ps alternative though, that's a perfectly agnostic solution that also doesn't tie us to any other dependencies 🚀

Now with the whole stack!
python3 utilities/ps.py
================================================================================
                                    Services
================================================================================
proxy:
-  http://<IP_ADDRESS>:50200 (→ 9080)
-  http://<IP_ADDRESS>:50243 (→ 9443)
ingestion_server:
-  http://<IP_ADDRESS>:50281 (→ 8001)
web:
-  http://<IP_ADDRESS>:50230 (→ 3000)
-  http://<IP_ADDRESS>:50280 (→ 8000)
plausible:
-  http://<IP_ADDRESS>:50288 (→ 8000)
es:
-  http://<IP_ADDRESS>:50292 (→ 9200)
cache:
-  http://<IP_ADDRESS>:50263 (→ 6379)
db:
-  http://<IP_ADDRESS>:50254 (→ 5432)
webserver:
-  http://<IP_ADDRESS>:9090 (→ 8080)
s3:
-  http://<IP_ADDRESS>:5011 (→ 5001)
-  http://<IP_ADDRESS>:5010 (→ 5000)
================================================================================

I'll investigate more myself, but locally this doesn't work on just up but does when evoked with just ps:

openverse on  feature/just-ps +/- [$] via  v16.19.1
❯ just up
env COMPOSE_PROFILES="api,ingestion_server,frontend,catalog" docker-compose -f docker-compose.yml up -d
[+] Running 15/15
 ✔ Container openverse-plausible_ch-1      Running                                                                                0.0s
 ✔ Container openverse-db-1                Running                                                                                0.0s
 ✔ Container openverse-upstream_db-1       Running                                                                                0.0s
 ✔ Container openverse-s3-1                Running                                                                                0.0s
 ✔ Container openverse-es-1                Started                                                                                0.4s
 ✔ Container openverse-load_to_s3-1        Started                                                                                0.5s
 ✔ Container openverse-cache-1             Running                                                                                0.0s
 ✔ Container openverse-plausible_db-1      Running                                                                                0.0s
 ✔ Container openverse-indexer_worker-1    Running                                                                                0.0s
 ✔ Container openverse-plausible-1         Running                                                                                0.0s
 ✔ Container openverse-web-1               Running                                                                                0.0s
 ✔ Container openverse-proxy-1             Started                                                                                0.9s
 ✔ Container openverse-scheduler-1         Running                                                                                0.0s
 ✔ Container openverse-webserver-1         Running                                                                                0.0s
 ✔ Container openverse-ingestion_server-1  Running                                                                                0.0s

python3 utilities/ps.py
================================================================================
                                    Services
================================================================================
Traceback (most recent call last):
  File "/Users/zackkrida/Code/openverse/utilities/ps.py", line 97, in <module>
    print_ps()
  File "/Users/zackkrida/Code/openverse/utilities/ps.py", line 91, in print_ps
    for service in parse_ps():
                   ^^^^^^^^^^
  File "/Users/zackkrida/Code/openverse/utilities/ps.py", line 68, in parse_ps
    name = service.split("-", 1)[1].rsplit("-", 1)[0]
           ~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range
error: Recipe `ps` failed on line 135 with exit code 1
error: Recipe `up` failed with exit code 1

openverse on  feature/just-ps +/- [$] via  v16.19.1
❯ docker ps
CONTAINER ID   IMAGE                                                  COMMAND                  CREATED          STATUS                             PORTS                                                                                NAMES
a561c40591c0   openverse_catalog                                      "/usr/bin/dumb-init …"   25 seconds ago   Up 22 seconds                      <IP_ADDRESS>:9090->8080/tcp, :::9090->8080/tcp                                                        openverse-webserver-1
ad30dafa4f28   openverse-ingestion_server                             "gunicorn -c ./gunic…"   25 seconds ago   Up 22 seconds                      8002/tcp, <IP_ADDRESS>:50281->8001/tcp, :::50281->8001/tcp                                            openverse-ingestion_server-1
e78fa5f3180b   openverse-ingestion_server                             "gunicorn -c ./gunic…"   25 seconds ago   Up 23 seconds                      8001-8002/tcp                                                                                openverse-indexer_worker-1
1084df7857fe   openverse_catalog                                      "/usr/bin/dumb-init …"   25 seconds ago   Up 23 seconds                      8080/tcp, 8793/tcp                                                                               openverse-scheduler-1
8ceaf0414f0f   openverse-api                                          "./run.sh python man…"   25 seconds ago   Up 23 seconds                      <IP_ADDRESS>:50230->3000/tcp, :::50230->3000/tcp, <IP_ADDRESS>:50280->8000/tcp, :::50280->8000/tcp         openverse-web-1
0894c4b369ce   plausible/analytics:latest                             "/entrypoint.sh sh -…"   25 seconds ago   Up 22 seconds                      <IP_ADDRESS>:50288->8000/tcp, :::50288->8000/tcp                                                      openverse-plausible-1
ea61b8215e97   minio/minio:latest                                     "/bin/bash -c 'for b…"   25 seconds ago   Up 24 seconds (health: starting)   9000/tcp, <IP_ADDRESS>:5010->5000/tcp, :::5010->5000/tcp, <IP_ADDRESS>:5011->5001/tcp, :::5011->5001/tcp   openverse-s3-1
a47e9c67c3e0   redis:4.0.14                                           "docker-entrypoint.s…"   25 seconds ago   Up 24 seconds                      <IP_ADDRESS>:50263->6379/tcp, :::50263->6379/tcp                                                      openverse-cache-1
1ccd62311cea   openverse-upstream_db                                  "docker-entrypoint.s…"   25 seconds ago   Up 24 seconds (health: starting)   5432/tcp                                                                                openverse-upstream_db-1
fad04b42b941   docker.elastic.co/elasticsearch/elasticsearch:7.12.0   "/bin/tini -- /usr/l…"   25 seconds ago   Up 9 seconds (health: starting)    9300/tcp, <IP_ADDRESS>:50292->9200/tcp, :::50292->9200/tcp                                            openverse-es-1
bd893383e49a   postgres:13.2-alpine                                   "docker-entrypoint.s…"   25 seconds ago   Up 24 seconds (health: starting)   5432/tcp                                                                                openverse-plausible_db-1
aad73ee04c9e   clickhouse/clickhouse-server:22.6-alpine               "/entrypoint.sh"         25 seconds ago   Up 24 seconds                      8123/tcp, 9000/tcp, 9009/tcp                                                                     openverse-plausible_ch-1
68e9f2ef1370   postgres:13.2-alpine                                   "docker-entrypoint.s…"   25 seconds ago   Up 24 seconds (health: starting)   <IP_ADDRESS>:50254->5432/tcp, :::50254->5432/tcp                                                      openverse-db-1

openverse on  feature/just-ps +/- [$] via  v16.19.1
❯ just ps
python3 utilities/ps.py
================================================================================
                                    Services
================================================================================
webserver:
-  http://<IP_ADDRESS>:9090 (→ 8080)
ingestion_server:
-  http://<IP_ADDRESS>:50281 (→ 8001)
web:
-  http://<IP_ADDRESS>:50230 (→ 3000)
-  http://<IP_ADDRESS>:50280 (→ 8000)
s3:
-  http://<IP_ADDRESS>:5010 (→ 5000)
-  http://<IP_ADDRESS>:5011 (→ 5001)
cache:
-  http://<IP_ADDRESS>:50263 (→ 6379)
db:
-  http://<IP_ADDRESS>:50254 (→ 5432)
================================================================================

Weird....on one of my machines docker was using - to split services and now on my desktop it's using _ 😵💫

@zackkrida does it work after the most recent commit? I'm able to get it to work with just up

@AetherUnbound it's working now 🥳 with one caveat. The service list is different immediately after just up than it is when running just ps immediately after:
openverse on  feature/just-ps +/- [$] via  v16.19.1 took 11s
❯ just up
env COMPOSE_PROFILES="api,ingestion_server,frontend,catalog" docker-compose -f docker-compose.yml up -d
[+] Running 16/16
 ✔ Network openverse_default               Created                                                                                0.0s
 ✔ Container openverse-plausible_ch-1      Started                                                                                0.5s
 ✔ Container openverse-upstream_db-1       Started                                                                                1.0s
 ✔ Container openverse-db-1                Started                                                                                1.2s
 ✔ Container openverse-es-1                Started                                                                                0.8s
 ✔ Container openverse-plausible_db-1      Started                                                                                1.1s
 ✔ Container openverse-cache-1             Started                                                                                0.9s
 ✔ Container openverse-s3-1                Started                                                                                1.1s
 ✔ Container openverse-plausible-1         Started                                                                                1.8s
 ✔ Container openverse-load_to_s3-1        Started                                                                                2.3s
 ✔ Container openverse-scheduler-1         Started                                                                                1.9s
 ✔ Container openverse-web-1               Started                                                                                2.2s
 ✔ Container openverse-indexer_worker-1    Started                                                                                2.2s
 ✔ Container openverse-proxy-1             Started                                                                                3.2s
 ✔ Container openverse-ingestion_server-1  Started                                                                                3.2s
 ✔ Container openverse-webserver-1         Started                                                                                2.6s

python3 utilities/ps.py
================================================================================
                                    Services
================================================================================
webserver:
-  http://<IP_ADDRESS>:9090 (→ 8080)
ingestion_server:
-  http://<IP_ADDRESS>:50281 (→ 8001)
proxy:
-  http://<IP_ADDRESS>:50243 (→ 9443)
-  http://<IP_ADDRESS>:50200 (→ 9080)
web:
-  http://<IP_ADDRESS>:50280 (→ 8000)
-  http://<IP_ADDRESS>:50230 (→ 3000)
================================================================================

openverse on  feature/just-ps +/- [$] via  v16.19.1 took 4s
❯ just ps
python3 utilities/ps.py
================================================================================
                                    Services
================================================================================
webserver:
-  http://<IP_ADDRESS>:9090 (→ 8080)
ingestion_server:
-  http://<IP_ADDRESS>:50281 (→ 8001)
web:
-  http://<IP_ADDRESS>:50280 (→ 8000)
-  http://<IP_ADDRESS>:50230 (→ 3000)
plausible:
-  http://<IP_ADDRESS>:50288 (→ 8000)
es:
-  http://<IP_ADDRESS>:50292 (→ 9200)
s3:
-  http://<IP_ADDRESS>:5010 (→ 5000)
-  http://<IP_ADDRESS>:5011 (→ 5001)
db:
-  http://<IP_ADDRESS>:50254 (→ 5432)
cache:
-  http://<IP_ADDRESS>:50263 (→ 6379)
================================================================================

I imagine that's just because docker is still working on spinning services up potentially. Do you think I should add a wait in between the commands to help rectify that @zackkrida?

@AetherUnbound good idea. I tested adding sleep 1 locally and it fixed the issue 👍

Alright this iteration now includes container and image names!
j ps
python3 utilities/ps.py
================================================================================
                                 Service Ports
================================================================================
webserver (catalog):
-  http://<IP_ADDRESS>:9090 (→ 8080)
ingestion_server (ingestion_server):
-  http://<IP_ADDRESS>:50281 (→ 8001)
plausible (plausible/analytics):
-  http://<IP_ADDRESS>:50288 (→ 8000)
web (api):
-  http://<IP_ADDRESS>:50280 (→ 8000)
-  http://<IP_ADDRESS>:50230 (→ 3000)
db (postgres):
-  http://<IP_ADDRESS>:50254 (→ 5432)
s3 (minio/minio):
-  http://<IP_ADDRESS>:5011 (→ 5001)
-  http://<IP_ADDRESS>:5010 (→ 5000)
es (docker.elastic.co/elasticsearch/elasticsearch):
-  http://<IP_ADDRESS>:50292 (→ 9200)
cache (redis):
-  http://<IP_ADDRESS>:50263 (→ 6379)
================================================================================


when work cocoon:before-remove, cocoon:after-remove ?

im tryiing events
$(document).ready(function () {

    $('#items')
        .on('cocoon:before-insert', function () {
            console.log('before insert');
        })
        .on('cocoon:after-insert', '#items', function () {
            console.log('after insert');
        })
        .on("cocoon:before-remove", '#items', function () {
            console.log('before remove');
        })
        .on("cocoon:after-remove", function () {
            console.log('after remove');
        });

});

cocoon:before-insert
cocoon:after-insert
works ok
cocoon:before-remove
cocoon:after-remove
dont work
remove events works only on existing items - in update? its not "live" right? because im trying it during adding new item
thanks

Can I assign a id for a repeating divs ?

I just want to identify repeating divs separately , want to add unique id for each main div .any help will appreciate

@smartmall friendly suggestion for using github ...proper github etiquette would be to start a new issue & link back to this one if it's related.
A path you could pursue for your problem ...
Use jquery's custom callbacks (described here ... https://github.com/nathanvda/cocoon#callbacks-upon-insert-and-remove-of-items) & generate an ID of your choice.
I have a feeling that generating the ID, storing & recalling the ID will be most of your problem as the jquery to add an html element is easy.
Something like https://api.jquery.com/add/ or $('selector').attr( 'id', 'yourId' ); ...  something like here would probably work - but you will need to limit the scope so it only targets the <first / last> div of that name you added.  I say < first / last > because cocoon has an option to change where you place the most recently added element.

Thank you very much for replying me .The Problem is Use jquery's custom callbacks, is not working for me ,

this is what i am going to do , as you can see, i am repeating email field and that div selecting part, so i just want collect separately  selected divs for each repeating   part, and send them to controller . here is my javascript for select
$(document).on('click', '.myDivs', function () {
    $(this).toggleClass('selected');

    var selectedRoles = $('.selected').map(function() {
        var divId = this.id;
        var parentDivId = $(this).parents(".repetediv")[0].id;
        console.log("pA "+parentDivId);
        //var roleNames = $('#'+divId+' h5').text();
        var roleNames = $('#'+parentDivId).find('#'+divId+' h5').text();
        return roleNames;
    }).get();

    console.log(selectedRoles);
    var top = $(this).parents(".repetediv")[0].getElementsByClassName("rolefield")[0].id;
    console.log('top '+top);
    document.getElementById(top).value = selectedRoles;
    // $("#"+top).val(selectedRoles);
});

so its giving all the divs that have been selected , i cant group them , Thank you again for reply me

any help will appreciate

As @Mirv said: it is not proper etiquette to hijack an old (solved!) issue to try to get help for a seemingly unrelated question.
I also do not understand: the code you are showing and your original question do not directly refer to cocoon. Your problem does not appear to be with cocoon callbacks at all, but with jquery/selectors, right?
I urge you to do one of two things:

if your question is related to cocoon, and you cannot get nested forms to work, start a new issue, with it's own title and a clear explanation what you are trying to achieve (with cocoon) and what is stopping you
if your question is much more generic, basic html/css/jquery which you encountered while doing something with cocoon, please ask on stackoverflow.com, there a load of specialists in all fields that will be able to help you a lot quicker. You can also post the link to the question here.

Oh sorry and i made a new issue too, i will explain it since you have replied here. I am using cocoon to generate above part , that i have send a screen shot here. As you can see there are custom made div selector. since cocoon repeating  those main container div I cant group selected divs for one part. That's why i want to generate a id for main container div, for identify separately . Is there any way to generate id for divs also in cocoon ? I am new to ruby. sorry for that. This is the link to new issue.  Thank you for replying me.
https://github.com/nathanvda/cocoon/issues/419


Multitest should have special tagging for checked-mode compile-time error.

Multitest should have special tagging for checked-mode compile-time error. For instance in language/compile_time_constant_checked_test we have:
final int x = 'foo'; /// 01: static type warning, dynamic type error
const int y = 'foo'; /// 02: static type warning, compile-time error
int z = 'foo'; /// 03: static type warning, dynamic type error
In production mode, only warnings are expected and in checked mode errors are expected. 'dynamic type error' is implicitly checked mode only, but 'compile-time error' is for both checked and unchecked mode, thus requiring status files to be annotated with 'MissingCompileTimeError, OK'.
We should, similar to 'dynamic type error', have a 'static type error' (or some other better name) for indicating that a compile-time error is only expected in checked mode.

Checked mode is a goner


Add workaround for ChartJS shrinking chart bug

Fix for issue #293

How odd that this fixes it. :-)  Thank you!


Quick reply buttons do not move the user's focus to the start of the message response from the chatbot.

Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
No response
What browsers and screen readers do this issue affect?
No response
Are there any code-based customization done to Web Chat?
No, I am using Web Chat without any customizations except "styleOptions".
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
Focus management, Live region
What is the public URL for the website?
https://edfinancial.com
How to reproduce the issue?
This is feedback from the accessibility company Allyant who has been testing our website and has people who use screenreaders and other assistive technologies as a part of their testing team.

What do you expect?
When a button option is selected, the focus should be on the first message that was sent by the chatbot in response to the button selection.
Set focus to the new message displayed in the chat window when selecting a button by using the JavaScript focus() method to move keyboard focus to the target element when the button is activated. Ensure that the target element can receive keyboard focus by using a natively-focusable element or giving the element a tabindex="-1" attribute.
What actually happened?
When a button option is selected, the focus does not go to the first message that was sent by the chatbot in response to the button selection.
Do you have any screenshots or recordings to repro the issue?
No response
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
No response
WCAG reference
https://www.w3.org/WAI/WCAG22/Understanding/focus-order
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response

Suggested actions are predefined messages and they are designed to help end-user quickly type out the message. They are designed as part of the send box and is not part of the message.
Thus, when the suggested action is sent and disappear from the screen, the focus will go to the send box, which is the container of the suggested actions.


移动端平台测试相关

很不错的工作，支持； 另外想请教一下 在安卓平台部署的代码使用什么呢 可以分享学习实测一下吗？

Thank you for your appreciation to our work :)
We tried two frameworks: TNN and onnxruntime.
We use the former one to deploy our models on the mobile phones.
But the latter one supports more operations than the former one.

our

good。 But how to deploy the correlation operation in your model? Is it a custom op implemented by yourself?

Hi, sorry for the late reply. In LightTrack, we use "pixel-wise correlation" to aggregate features of the template and the search region. We provide two types of implementations, one is by "convolution and for-loop" and the other is by "matrix multiplication". The second one runs much faster than the first one because the computation is quite vectorized. But some frameworks may not support the "matrix multiplication" operation. In this case, you can turn to use the first one (conv+for-loop).
Thanks,
Bin

thanks！


[Diffy] Need to create image container to store the image.

@louisgv  seems like you created something basic for this?

@ColdSauce ?... image container to store image or to show image?

show image


Audio Conferencing PIN reset URL doesn't work

When going to this URL, we have two options:

provided in the meeting invite template, to "Reset PIN" goes to https://mysettings.lync.com/pstnconferencing and this is a bad/dead DNS entry
from the documentation here, it says to go to https://admin0m.online.lync.com/lscp/usp/pstnconferencing
which brings me to a blank webpage... I see the Skype for Business favicon, a blue header bar, and at the top-right corner see my first name, "Sign Out" and "Help" but the body/rest of the page is all blank.

I was able to open the link #2 in a Firefox browser, but blank (as described above) in Microsoft Edge (I'm on Version 83.0.478.45 (Official build) (64-bit) fyi)

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

ID: 401f39f3-f614-6d63-adbd-1ed78ed804f0
Version Independent ID: 26b45c86-8f6f-8704-d95a-f8c341e569ad
Content: Reset the Audio Conferencing PIN in Microsoft Teams - Microsoft Teams
Content Source: Teams/reset-the-audio-conferencing-pin-in-teams.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@ruizoscar - Can you see if Fan can take a look at this issue and offer some feedback to them. Thanks, Tony

@fafan - Can you take a look at this issue and offer some feedback to them. Thanks, Tony

Pinged the PM again so we can get the right URL to update this with.

@c016smith - I myself tested both of the links and both worked. I had other people confirm and it worked for them as well. Clear your browser cache or try Chrome and see what the result is. This is definitely a browser issue. Thanks.


Ordering/tests

Wrote func tests for ordering

Codecov Report

Merging #292 (0f3b9dd) into ordering/ordering (8d51699) will decrease coverage by 2.14%.
The diff coverage is 0.00%.

@@                  Coverage Diff                  @@
##           ordering/ordering     #292      +/-   ##
=====================================================
- Coverage              42.40%   40.25%   -2.15%
=====================================================
  Files                    120      120
  Lines                   6028     6029       +1
=====================================================
- Hits                    2556     2427     -129
- Misses                  3279     3426     +147
+ Partials                 193      176      -17

Flag
Coverage Δ

integration
?

unittests
40.25% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/messagebroker/kafka.go
10.48% <0.00%> (-30.10%)
:arrow_down:

pkg/messagebroker/factory.go
33.33% <0.00%> (-33.34%)
:arrow_down:

Continue to review full report at Codecov.

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


Properly deal with duplicated Rucio rules

Impact of the new feature
WMAgent
Is your feature request related to a problem? Please describe.
When making the final output dataset subscription - as we currently do for phedex - we need to have a mechanism in place to figure out when the cms dataset (container) already has such rule created by a different agent (for cases where the same workflow is dealt with by multiple agents)
Describe the solution you'd like
In case we start persisting the rule id in the database, we need to make another rucio call to retrieve the rules for a given DID. Then we need to compare all the rules available against:

rucio account
DID
RSE expression
such that we can find - or not - a pre-existent rule.

IF we do not persist the rule id, then we could simply catch the duplicate rule exception DuplicateRule and return a positive response, such that the component can mark that as done and move on.
Describe alternatives you've considered
alternative described above
Additional context
none

For sure, the tuple (account, DID, RSE expression) is unique in rucio and it will throw an error that you can catch and handle to get the pre-existing rule, which I think is fine (as long as we don't DDOS rucio trying to get the existing rule via this mechanism).
My concern was whether it is possible the RSE expression may differ when multiple agents work on something. For example, if a workflow is running at T2_US_Caltch and T2_CH_CERN, which site will the container rule be created against? Both? We definitely don't want the whole output dataset to have a copy at every site where blocks are being procssed.

My concern was whether it is possible the RSE expression may differ when multiple agents work on something. For example, if a workflow is running at T2_US_Caltch and T2_CH_CERN, which site will the container rule be created against?

such configuration is currently cast in stone. Right now, the P&R team provides A custodial site, A non-custodial site, and etc. So the container level rule can only go to one site, and it will always be the same.

Ok, so then I think having at most M agents * N workflows querying rules vs. 1 agent * N workflows is not such a big deal and you can catch the exception as you are now.
I will make a separate issue about the output site, since clearly this needs to change.

The current code implemented in the Rucio module does not seem to be properly dealing with duplicate rules.
I just spotted this error in MSTransferor:
...
2020-09-07 19:03:28,567:INFO:MSTransferor: Have a chunk of 1 blocks (5.46 GB) for dataset: /RelValH125GGgluonfusion_14/CMSSW_10_6_1-106X_mcRun3_2021_realistic_v1_rsb-v1/GEN-SIM
2020-09-07 19:03:28,567:INFO:MSTransferor: AMR old RSEs: [u'T2_CH_CSCS'], new RSEs: [u'T2_CH_CSCS_Test']
2020-09-07 19:03:28,567:INFO:MSTransferor: Primary data placement without any parent dataset, using all RSEs for the rule creation: T2_CH_CSCS_Test
2020-09-07 19:03:28,567:INFO:MSTransferor: Creating a Rucio rule for workflow amaltaro_SC_LumiMask_PhEDEx_Aug2020_PrivVal_200907_173243_6762, container /RelValH125GGgluonfusion_14/CMSSW_10_6_1-106X_mcRun3_2021_realistic_v1_rsb-v1/GEN-SIM, RSEs: T2_CH_CSCS_Test, grouping: DATASET

2020-09-07 19:03:28,649:DEBUG:connectionpool: http://cmsrucio-int.cern.ch:80 "POST /rules/ HTTP/1.1" 409 None
2020-09-07 19:03:28,650:INFO:Rucio: A duplicate rule for:
account: wmcore_transferor
dids: [{'name': u'/RelValH125GGgluonfusion_14/CMSSW_10_6_1-106X_mcRun3_2021_realistic_v1_rsb-v1/GEN-SIM#5ed93a5c-d278-412c-8c73-b5a6e4ab1582',
  'scope': 'cms'}]
rseExpression: T2_CH_CSCS_Test.

2020-09-07 19:03:28,954:DEBUG:connectionpool: http://cmsrucio-int.cern.ch:80 "POST /rules/ HTTP/1.1" 409 167
2020-09-07 19:03:28,993:DEBUG:connectionpool: http://cmsrucio-int.cern.ch:80 "GET /rules/cms/%2FRelValH125GGgluonfusion_14%2FCMSSW_10_6_1-106X_mcRun3_2021_realistic_v1_rsb-v1%2FGEN-SIM%235ed93a5c-d278-412c-8c73-b5a6e4ab1582/history HTTP/1.1" 200 None
...
2020-09-07 19:03:28,996:DEBUG:Rucio: Rule History: [{'did': {'name': u'/RelValH125GGgluonfusion_14/CMSSW_10_6_1-106X_mcRun3_2021_realistic_v1_rsb-v1/GEN-SIM#5ed93a5c-d278-412c-8c73-b5a6e4ab1582',
          'scope': 'cms'},
  'did_hist': [{u'account': u'sync_t2_ch_cern',
                u'created_at': datetime.datetime(2019, 9, 22, 17, 47),
                u'locks_ok_cnt': 3,
                u'locks_replicating_cnt': 0,
                u'locks_stuck_cnt': 0,
                u'rse_expression': u'rse=T2_CH_CERN',
                u'rule_id': u'c7503223a92d4e9487772369631c8894',
                u'state': u'OK',
                u'updated_at': datetime.datetime(2019, 9, 22, 17, 47)},
               {u'account': u'sync_t1_us_fnal_disk',
                u'created_at': datetime.datetime(2019, 12, 3, 0, 47, 23),
                u'locks_ok_cnt': 3,
                u'locks_replicating_cnt': 0,
                u'locks_stuck_cnt': 0,
                u'rse_expression': u'rse=T1_US_FNAL_Disk',
                u'rule_id': u'c84adf5b5e6145aab626c3709e60dbef',
                u'state': u'OK',
                u'updated_at': datetime.datetime(2019, 12, 3, 0, 47, 23)},
               {u'account': u'wmcore_transferor',
                u'created_at': datetime.datetime(2020, 9, 7, 17, 0, 50),
                u'locks_ok_cnt': 0,
                u'locks_replicating_cnt': 3,
                u'locks_stuck_cnt': 0,
                u'rse_expression': u'T2_CH_CSCS_Test',
                u'rule_id': u'3a66bbfb3b594802ab558bc5aca73b90',
                u'state': u'REPLICATING',
                u'updated_at': datetime.datetime(2020, 9, 7, 17, 1, 1)}]}]

2020-09-07 19:03:28,997:DEBUG:Rucio: ruleIds: [u'c7503223a92d4e9487772369631c8894', u'3a66bbfb3b594802ab558bc5aca73b90', u'c84adf5b5e6145aab626c3709e60dbef']

2020-09-07 19:03:28,997:INFO:MSTransferor: Rules successful created for /RelValH125GGgluonfusion_14/CMSSW_10_6_1-106X_mcRun3_2021_realistic_v1_rsb-v1/GEN-SIM : [u'c7503223a92d4e9487772369631c8894', u'3a66bbfb3b594802ab558bc5aca73b90', u'c84adf5b5e6145aab626c3709e60dbef']

This needs to be fixed before MSTransferor Rucio-based gets enabled in production.


Release 3.0.2

Fixed issue with missing notifier info payload.

It would be nice to separate release PRs and fixes. I think the correct way is to close this PR and open a new one, with the fix.
Once the fix is merged, we open a 2nd PR (release).


Manually install dart-sdk and download pub packages

flutter automatically do all required things.
f.e. sdk
Indeed I often downloaded dart-sdk
but flutter owns a new piece of dart-sdk, although to copy my downloaded to flutter is not so hard
Let's make flutter configable for its requirement?

Flutter uses a carefully compiled Dart SDK that is specific to the version of Flutter that you are using, which is why we manage that for you.


Find centers of connected components

If I had tensor image I can use tfa.image.connected_components(image) to find components but how can I find centers of each components ?
I suggest a function like OpenCV function connectedcomponentswithstats

TensorFlow Addons is transitioning to a minimal maintenance and release mode. New features will not be added to this repository. For more information, please see our public messaging on this decision:
TensorFlow Addons Wind Down
Please consider sending feature requests / contributions to other repositories in the TF community with a similar charters to TFA:
Keras
Keras-CV
Keras-NLP


DOC-6180: Added fingerprint_id section

Addresses: DOC-6180

@nickvigilante these includes affect cloud console pages (/cockroachcloud/statements-page.html) as well as db pages (ui-statements-page.html). is there a bug in the files changed bot?

Which includes? I'll try to investigate.

ui/transactions-table.md
ui/transaction-details.md
ui/statements-table.md
ui/statement-details.md

Ah, yeah, I don't have any Jekyll-specific logic to calculate if a versioned include exists within a cloud page. I only search for references to that include from within the version folder where it exists. This may be moot once we adopt a branch-based versioning scheme or a monorepo.


Throw an error when using a Union or Interface as an argument type

Hello dear friends @jkimbo  @patrick91 @BryceBeagle
This patch is about raising an exception when we use invalid arguments such as Union and Interface. issue #1065
Hope it can help
If anything needs to be changed or fixed, just let me know
With Respect

Description

Types of Changes

[ ] Core
[x] Bugfix
[x] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR
#1065
Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release adds a new exception called InvalidArgument and it will be raised when we use Union or Interface as an argument type
For example this will raise an exception:
￼import strawberry
￼
@strawberry.type
class Noun:
    text: str

@strawberry.type
class Verb:
        text: str

Word = strawberry.union("Word", types=(Noun, Verb))

@strawberry.field
def add_word(word: Word) -> bool:
    _word = word
    return True
￼```

---
Here's the preview release card for twitter:

![](https://i.imgur.com/pDKdUkv.png)

Here's the tweet text:

🆕 Release (next) is out! Thanks to Mohammad Hossein Yazdani for the PR 👏
Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)
<!-- action-check: release-file -->

@jkimbo i appreciate you
It seems my English language is really bad. I need to study more :)
But Thanks for your help. It is very valuable to me
I fixed everything as you suggested, but if anything needs to be fixed again, just tell me
With Respect

Thanks for your help and suggestions again @patrick91
Of course, i'll send the changes right now.

Thanks for contributing to Strawberry! 🎉 You've been invited to join
the Strawberry GraphQL organisation 😊
You can also request a free sticker by filling this form: https://forms.gle/dmnfQUPoY5gZbVT67
And don't forget to join our discord server: https://strawberry.rocks/discord 🔥


k8s: fix daemonset metadata

Added metadata fields: Labels and Replica metrics which can be verified by:
kubectl create -f tests/k8s/daemonset.yaml

run tests

run skydive-ppc64le-tests


[SUGGESTION] Change Venus' Texture.

The current texture appears to be of Venus' surface. When we see Venus in the sky however, we don't see its surface. Venus' surface is almost entirely obscured by heavy cloud cover.

Altering the texture should also make it more visually distinct from Mars.

I'm just gonna do it myself. It's not that hard to change some pixels.

Actually a pretty cool idea

This may have already been solved due to merging my pull request.


import: Remove skipping of too-long messages during import.

This PR removes the logic that skips messages longer than 10K characters during the import process. With the changes introduced in #32090, those messages can now be imported with truncation, making the previous check unnecessary.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@timabbott, this follow-up PR is ready for review. Please check it out when you have a chance.

Merged, thanks @reharsh!


wip: add find installed tools + find current version

Signed-off-by: Tuan Anh Tran<EMAIL_ADDRESS>add outdated command
Description

Motivation and Context

[ ] I have raised an issue to propose this change (required)

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I've read the CONTRIBUTION guide
[ ] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

Thanks for your interest in arkade.

I have raised an issue to propose this change (required)

Could you raise an issue please? That's how contributions are accepted on arkade. Raise an issue, discuss the problem/design and decide whether to proceed with a PR.

Oh, it's relate to this issue https://github.com/alexellis/arkade/issues/313


Add changelog for 3.1.1

What problem does this PR solve?
Add release-3.1.1 changelog into master

/run-all-tests

/run-all-tests

/merge


Performance monitoring API

We need some performance monitoring APIs so that we can understand the performance of CHERIoT applications. This issue is to track ideas and development.
Here are some ideas for requirements / features:

need to be able to enable / disable performance monitoring APIs at compile time via a flag / cpp definition so that monitoring will have no impact (performance or security) on release builds. Maybe per component?
performance and space impact should be very low when enabled
need to be able to retrieve statistics (count, cycles, instructions?) about significant events, probably per thread and / or per compartment. Min / max of these statistics?
Events we may want to monitor:

switcher: compartment calls, faults, scheduler time?
scheduler: interrupts (per interrupt type?), interrupt latency?, thread transitions? accuracy of timer interrupt?
allocator: allocations (bin by size?), revocation sweeps, time spent waiting for revocation
networking

It would be nice to have an extensible API that could accommodate all of these but they may be different enough that that won't work.
Can anyone point to existing performance monitoring APIs we could clone or use as reference?

@hlef


DBZ-1525 Validate replication slot name

https://issues.jboss.org/browse/DBZ-1525

Applied. Thanks, @jpechane!


Update to ParmEd v4.3.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

No valid build backend found for Python recipe for package parmed using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.


UI: GKE Cluster Options that require api endpoints

UI for https://github.com/rancher/rancher/issues/14298

Version: Master 2.2 (2/13/19)
Per the linked backend issue this adds new areas to the UI for GKE:

additional zones
network
project access
maximum number of nodes per pool

Additional zones can be added on to your primary (drop down) by checking boxes as seen in the screenshot above. You can pick your network as well from a drop-down list of available networks.

You can limit project access by setting Security options to set oauth scope. You can enable min/max nodes per pool by enabling node pool autoscaling.
I validated for each the various options and ensured http/api looks correct.
Additional zones just adds more entries to locations:
locations: ["us-central1-b", "us-central1-c", "us-central1-a"]
0: "us-central1-b"
1: "us-central1-c"
2: "us-central1-a"

network:
network: "hgalal"
Project access is oauth settings:
oauthScopes: ["https://www.googleapis.com/auth/devstorage.read_only",…]
0: "https://www.googleapis.com/auth/devstorage.read_only"
1: "https://www.googleapis.com/auth/logging.write"
2: "https://www.googleapis.com/auth/monitoring"
3: "https://www.googleapis.com/auth/servicecontrol"
4: "https://www.googleapis.com/auth/service.management.readonly"
5: "https://www.googleapis.com/auth/trace.append"

node pool size:
maxNodeCount: 3
minNodeCount: 1

Validated UI checking the various options. Validated HTTP/API as well for each area. Ensured can edit and update these settings for an existing cluster. Note if the cluster is in a bad state because wrong network was picked you cannot recover from this.
While testing this a few issues were found and entered around GKE.
@loganhz may I ask for a quick review of my testing above? Did I understand the new areas correctly and relating API? I tried to look in PRs/Commits but it's difficult for me to pinpoint exactly what is what.

@davidnuzik yes, your testing step is right, as you said
Locations ---> additional zones
Network ---> network
Security ---> project access
Node Pool Autoscaling ---> maximum number of nodes per pool

Here is GKE UI:

Node Pool Autoscaling:

Security:

Locations and Network:

Thank you both :) Yes looks like I got this correct based on what I see you have both sent.
I am closing the issue based on my testing done above see the comment here: https://github.com/rancher/rancher/issues/17992#issuecomment-463350596


quarkus.langchain4j.pgvector.use-index and quarkus.langchain4j.pgvector.index-list-size?

I'm experimenting with pgvector and the two configuration properties quarkus.langchain4j.pgvector.use-index and quarkus.langchain4j.pgvector.index-list-size are a bit obscure.
I don't know exactly what's their purpose. I set use-index to try and then it complained about me needing to set index-list-size (or maybe something else?) and had no idea what value to put there.
Now maybe it's because I'm lacking some background about pgvector but in this case a link would be welcome.
I would contribute something but I don't really know what to do here :).

cc @jmartisk

Note that I pushed some improvements here that should probably be merged before doing some work on this: https://github.com/quarkiverse/quarkus-langchain4j/pull/857

BTW, I'm asking because our doc is very informative in general and has a lot of details on the concept and most of the time you don't need to dig a lot further to understand everything.

also cc @sebastienblanc who wrote this code


Gitea API - Cannot add comment to PR when using external issue tracker

Gitea version (or commit ref):
Git version: 1.5.0
Operating system: Debian 9
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL): https://try.gitea.io/chanhlt/test-repo/pulls/1
[ ] No
[ ] Not relevant

Log gist:

Description
When I try to use API to add comment to a pull request.
It works perfectly if I use built-in issue tracker.
However, when I change to use an external one like Redmine.
I cannot use the API anymore.
I get 404 error.
Screenshots
Using built-in issue tracker

Using external issue tracker

Which API did you use to add comment?


Overwrite JSS_URL and other parameters in recipe_override?

I'm trying to think of a way to get AutoPkg to push to multiple JSSes, because the JSS API doesn't have enough features to successfully do API policy transfers from one JSS to another (e.g. transfer of self-service icons). One method I can think of would be to have different recipe overrides for each JSS instance. However, as far as I can see at the moment, JSSImporter only looks at the AutoPkg preferences for the JSS_URL information. If this could be overridden in a recipe override, I could create multiple overrides for the same package.

You might look at this for migration: https://github.com/igeekjsc/JSSAPIScripts

Thanks,  I looked at various resources including that one, but they all strip out the self service icon data for policies. I've now figured out how to do it in a roundabout way, so this ticket can now be closed.
Cheers,
Graham
Sent from my iPhone

On 7 Sep 2017, at 13:15, Ryan Ball<EMAIL_ADDRESS>wrote:
You might look at this for migration: https://github.com/igeekjsc/JSSAPIScripts
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Late to the party, but FWIW you can indeed run 1 override per JSS and override the settings needed in the override. That seems like cheating, but it's definitely one way of doing it. You can also create 1 service account per JSS and have each one run AutoPkg independently, which is also a little nutty.
A guess a third option is to write a LaunchDaemon to run AutoPkg with the -l "list" option on a schedule, changing the JSS_URL etc prefs in-between runs.


Add jsonb support

I have added some rudimentary (parse/load/save) support for jsonb as a column type, but it will need https://github.com/luckyframework/lucky_migrator/pull/122 for the specs to succeed as it needs to add a JSON::Any column.
I haven't worked much with either lucky or crystal in the past, so let me know if there's anything I can improve here

Added the jsonb column to test against using execute instead so specs can run

I need to rework to not use JSON::Type as it's gone in crystal v0.25

This is looking really good! I added a couple comments about using to_json and parsing NamedTuples. I think @paulcsmith would have some comments to go over then it should be good to go.

I will try find time to merge https://github.com/luckyframework/lucky_migrator/pull/122 into this PR next week :)

@tzar Awesome work on this! For the travis config, have you tried adding:
addons:
  postgresql: "9.4"

to .travis.yml?

Thanks! I assumed I wouldn't be able to mess with travis from within the PR, but I should have just tried it ☺

Hey @tzar! We've moved and renamed LuckyRecord to Avram. We decided to move it instead of using GitHub's rename option so that current code that relies on lucky_record would continue to work and a project must opt-in to the new shard. However, a big bummer is we can't move PRs.
If you are still interested in this change, would you be able to rebase onto Avram? If not don't worry about it. We can eventually rebase it for you. Thanks 😄! Let us know if you have any questions.

Done! Closing this one in favour of https://github.com/luckyframework/avram/pull/48


ENH: SHAP in PySpark ML models

Problem Description
Shap still does not work with PySpark models.
Sklearn will be deprecated soon, as everyone is working in pyspark instead in pandas.
Alternative Solutions
I propose make shap works with PySpark models, does anyone support me?
Additional Context
No response
Feature request checklist

[X] I have checked the issue tracker for duplicate issues.
[X] I'd be interested in making a PR to implement this feature

#3147 Here is a model that SHAP can not handle

Could you please provide a reproducible example (model creation, dataset creation, calling of shap function all in the example and running), so that I can investigate this?


Use ids from api instead of Sugar's?

All of the objects coming from my api have their own id. This id is also used to manage relationships between objects. Currently, I am creating a new id field for my object, ex. personId. Then when I want to update that object, I have to query if that object already exists in the db. If id does, I assign the "Sugar id" from the existing record to the current record to avoid duplication.
It would be really nice if I could use my own id to avoid these checks/assignments, and only have to deal with one id field. Is anybody else having this problem or found a better way around it?

If your application structure allows it, could you extend SugarRecord instead of using annotations? Doing this will make your classes inherit id from SugarRecord, and that id will always reflect how it is persisted within the database.

Thanks. I was able to fix it by updating to the newest version of Sugar and setting Sugar's id to what I need it to be.


feat(ui): path prefix support via HTTP header

Description
Makes the web app honour the X-Forwarded-Prefix HTTP request header that may be sent by a reverse-proxy in order to inform the app that its public routes contain a path prefix. This allows to serve the webapp via a reverse-proxy/ingress controller under a path prefix/sub path such as e.g. /localai/ while still being able to use the regular LocalAI routes/paths without prefix when directly connecting to the LocalAI server.
Changes:

Add new StripPathPrefix middleware to strip the path prefix (provided with the X-Forwarded-Prefix HTTP request header) from the request path prior to matching the HTTP route.
Add a BaseURL utility function to build the base URL, honouring the X-Forwarded-Prefix HTTP request header.
Generate the base URL using the BaseURL function into the HTML (head.html and login.html templates) as <base/> tag.
Make all webapp-internal URLs (within HTML+JS) relative in order to make the browser resolve them against the <base/> URL specified within each HTML page's header.
Make font URLs within the CSS files relative to the CSS file.
Generate redirect location URLs using the new BaseURL function.
Use the new BaseURL function to generate absolute URLs within gallery JSON responses.

This PR fixes #3095
TL;DR:
The header-based approach allows to move the path prefix configuration concern completely to the reverse-proxy/ingress as opposed to having to align the path prefix configuration between LocalAI, the reverse-proxy and potentially other internal LocalAI clients.
The gofiber swagger handler already supports path prefixes this way, see here - However, it does not support executing API requests when a path prefix is used because it doesn't replace the base URL within the served swagger JSON.
Notes for Reviewers
Apart from the added automated tests, I did some manual testing and grepping, hoping to have all URLs covered.
Signed commits

[x] Yes, I signed my commits.

Thank you :100:  - it makes totally sense as an addition to me. As soon as I have a bit of time will try to test out locally too to see if there aren't any regression

The app test was broken. I think I fixed it now. Please re-run the workflow.

Oups, turns out I introduced a cyclic dependency within the test code between the new utils package and the middleware package when I also added the <base/> URL to the login page that is rendered by the auth middleware.
I'll fix that...

I fixed it by simplifying the BaseURL implementation and making its unit test not depend on the StripPathPrefix middleware. Please re-run the workflow.


Bulk generation of data

Is there any way of generating, let's say, a million records quickly?
I've checked the option exporter.fhir.bulk_data but it still generates the records one at a time...
Thanks in advance.

There's no configuration option to fundamentally speed up Synthea such that it can produce massive amounts of data significantly faster than it currently does.  If there was we would probably leave it enabled by default!
That said every record is generated independently, so if you have the infrastructure you could run multiple instances at the same time and then combine them later, for example running multiple states or countries independently rather than generating a single larger population.

That's not our Docker image, (we don't support a Docker image, and to be honest I don't know a whole lot about Docker) but at a glance it looks like it fetches the latest version of Synthea, so theoretically it should be "up to date". If there's a version on Dockerhub or something it may have been built a long time ago, but if you build it fresh it should use the most recent version of Synthea. Beyond that I can't really help with that specific Docker image.


feat: Course Upgrade Option with IAP

This PR adds course upgrade option with IAP. At the moment, support is being added for non-consumable products.
Config:
Local Config:
ECOMMERCE_URL: 'https://ecommerce.example.com' // e-commerce base URL for the course upgrade application
The feature is configurable via server config.
{
  "iap_config": {
    "enabled": true,
    "restore_enabled": false,
    "ios_disabled_versions": "[]"
  },
  "value_prop_enabled": true // to hide/show upgrade information messages.
}

https://github.com/openedx/openedx-app-ios/assets/5606473/6b3f6849-0b8c-43e0-a07a-b867f3e774c3
Stage environment can be used to test the feature. The following courses are configured on stage for IAP.
https://learning.stage.edx.org/course/course-v1:edx+IAP+2024_1/home
https://learning.stage.edx.org/course/course-v1:edx+IAP+2024_2/home
https://learning.stage.edx.org/course/course-v1:edx+IAP+2024_3/home
https://learning.stage.edx.org/course/course-v1:edx+IAP+2024_4/home

@saeedbashir IAP functionality is working as expected 🎉
I have included my observations. Moreover, please review the following items as well:

This alert appears when no internet connectivity. May be we need to update alert message in this case?
I believe, we should restrict the button sizes in landscape mode. Please check with all IAP related view’s buttons.

Reference Images:


Create inherit tag for applications and commands

Telling whether to use those apps/cmds in higher level topologies or not

Done with https://github.com/buzz66boy/ns3-lxc/commit/5ac2334871d0996ed2e710c05126af5b1b19ebc7


How to create the sensors?

I've set up the integration (one for daily and one for hourly). I included sensors with the hourly integration but the sensors did not appear even after a reboot. I've tried adding a separate hourly instance just for the sensors and restarted HA again but they've still not appeared as entities.
When I had it all configured just in in yaml they worked. Anything I'm doing wrong?

Logs:
Logger: homeassistant.setup
Source: setup.py:320
First occurred: 09:50:45 (1 occurrences)
Last logged: 09:50:45
Unable to prepare setup for platform pirateweather.sensor: Platform not found (Exception importing custom_components.pirateweather.sensor).
This error originated from a custom integration.
Logger: homeassistant.loader
Source: custom_components/pirateweather/sensor.py:216
Integration: Pirate Weather (documentation, issues)
First occurred: 09:50:45 (1 occurrences)
Last logged: 09:50:45
Unexpected exception importing platform custom_components.pirateweather.sensor
Traceback (most recent call last):
File "/usr/local/share/homeassistant/lib/python3.10/site-packages/homeassistant/loader.py", line 657, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/local/share/homeassistant/lib/python3.10/site-packages/homeassistant/loader.py", line 674, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/home/homeassistant/homeassistant/custom_components/pirateweather/sensor.py", line 216, in
device_class=SensorDeviceClass.PRECIPITATION,
File "/usr/local/lib/python3.10/enum.py", line 437, in getattr
raise AttributeError(name) from None
AttributeError: PRECIPITATION

You're trying to add the precip_accumulation sensor and it's throwing a error right? Currently that sensor returns None if there is no accumulation for the current day instead of 0. This will be fixed in the next update and it should allow you to add the sensors then.

That might be it; however, I suspect this is probably a version thing. Do you know what version of home assistant you're running here, since it may not have the new precipitation classes?

I've tried removing just the precipitation accumulation sensor, then all precipitation sensors, then stripped it back to only choosing the temperature sensor but still nothing.
I would agree that something to do with the version is likely - I'm running my HA on TrueNAS Core and the last compatible version is 2022.8.4 - If I want to upgrade past that I have to do some major upheaval to the machine I'm running this all on and I haven't come to the point of wanting to do that yet.

Thanks for clarifying that! What's weird is that I checked this, and the version that's has these new classes was 2021.12, so shouldn't be an issue for you, However, since reality begs to differ, so we're back at square 1.
I know it's not really a solution, but in your case you might be better off using the legacy version. It's not in HACS anymore, but you could either git clone or download it into your custom_components folder and configure via yaml. Other than not having the config UI there's nothing radically different about it, so would probably accomplish what you're looking for here,

Thanks @alexander0042, I will consider going back to the the legacy version as it was working before I updated from HACS - my reason for wanting the sensors was to use them with another custom integration to get a 'temp feels like' value, but I have managed to do that with the Pirate Weather temp, humidity and wind attributes instead.
I was also interested in seeing what the 'feels like' values your sensors provided amongst the other new bits and seeing if I could just use PW over some other HACS integrations doing things like ozone, and temp feels like separately.


[ie/Dropbox] supported password,thumbnail

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information
This pull request adds support for Dropbox password and thumbnail extraction.
Changes:

Added functionality to handle password-protected Dropbox links.
Implemented thumbnail extraction for Dropbox videos.

Template
Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

I would like to review this soon since the patch looks basically merge-able, but what's going on here with the YandexDisk commit and the closing/re-opening?

I'm sorry for the mess caused, please: "learning"

Don't worry, take your time. We all are 😄

@ndyanx I understand. If you want, I could help clean this up and push my code suggestions directly for you to test


Deleted Samples submitted

What's in this Pull Request?
Sorry, Deleting the samples submitted.

Hi Joseph,
like mentioned in the context of web parts. We will absolutely get these away if that's truly what's requested. Curious though on the details. Feel free to send me also an email if you don't want to share any details here, but can share some directly. Just to understand the reasoning behind of this move. Thx.

Hi Vesa,
I have sent you an email with my inputs. Thank you

thx Joseph for additional input.


Auto-Label Workflow for Pull Requests and Issues

Description
I propose adding a GitHub auto-label workflow that automatically assigns relevant labels, such as "gssoc-ext" and "hacktoberfest-accepted," to issues and pull requests related to these events. This will ensure more consistent tracking, better organization, and visibility of contributions linked to these important programs.
Key Features:

Automatic Labeling:

Automatically apply the "gssoc-ext" and "hacktoberfest-accepted" labels to pull requests and issues related to GSSOC Ext and Hacktoberfest.

Use Case:

Streamlines the labeling process by automating the assignment of labels for pull requests and issues, especially during events like GSSOC and Hacktoberfest.

Benefits:

Improved Efficiency: Reduces manual labeling efforts and ensures consistency.
Better Organization: Labels are applied systematically, making it easier to track event-specific contributions.
Enhanced Contributor Experience: Contributors receive immediate feedback through labels, improving their visibility within the project.

Priority:
High
Please @Avdhesh-Varshney assign me this issue with labels "GSSOC-Ext", "hacktoberfest-accepted" and "level3"

This can't be possible to add labels for levels, different tech stacks, whether it's invalid or not?
If you're able to do so, mention me again.

when anyone will raise a issue then the bot will automatically add lebels to them but assigning part is still in yours assigning labels with the help of bot makes the work easier and smoothier

Not required.


Tag support for expiration

Expiration tags support would be great for expire cache item / group with common tag or tags.
For example.
Yakari.Cache.Expire("City");

or
Yakari.Cache.Expire("Country", "City", "State", "Street");

A cache item or group can be include more than one tag.

We will going to add region/group support for both memory management and object sharing. Also we already have
ILocalCacheProvider.Delete("City")  //Also it will be distributed to all instances...
When we implement region/group we will support region/group cache invalidation.
But i have to say, tagging instead of grouping could be more interesting. Let me think about it for a while and I'm going to close this issue and add a new one #12


Add tests of modules

I added tests od prim_buf, prim_diff_decode, prim_esc_sender, prim_esc_receiver, prim_alert_sender and prim_alert_receiver modules.
It is related to:
https://github.com/alainmarcel/uhdm-integration/issues/262
https://github.com/alainmarcel/uhdm-integration/issues/261
https://github.com/alainmarcel/uhdm-integration/issues/254
https://github.com/alainmarcel/uhdm-integration/issues/253
https://github.com/alainmarcel/uhdm-integration/issues/296
https://github.com/alainmarcel/uhdm-integration/issues/298
https://github.com/alainmarcel/uhdm-integration/issues/252

These changes require Surelog in revision https://github.com/alainmarcel/Surelog/commit/93690e0a5662ec00f8a343f94e6dcff7fc4e29ca or newer.

I run these tests in https://github.com/antmicro/verilator/actions/runs/849093179. All of them passed. (One of other tests failed due to http error)


consider how to handle search (if we want it)

https://github.com/jekylltools/jekyll-tipue-search

https://christian-fei.github.io/Simple-Jekyll-Search/

https://community.algolia.com/jekyll-algolia/github-pages.html

netlify have a plugin that builds a algolia index we can use on build.

Not super familiar with implementing Jekyll search, but for designing + templating + testing it and then getting feedback:
Time estimate: 2 days


How to run pipreqs programatically inside python

other libraries like pyarmor and pyinstaller allow you to launch the program from a python script.
example:
import PyInstaller.__main__
PyInstaller.__main__.run([
    '--onefile',
    '--windowed',
    'main.py',
])

is equivalent to
pyinstaller --onefile --windowed main.py

How can I do this with pipreqs?

Oh and I can't use the exec() function due to security reasons...

ok i figured something
from pipreqs import pipreqs
from collections import defaultdict
args = defaultdict(lambda: None)
args['<path>'] = 'dist/'
args['--savepath'] = 'reqs.txt'
pipreqs.init(args)
pyinstaller_args = []
with open('reqs.txt', 'r', encoding='utf-8') as f:
    needs = [n.split('==')[0] for n in f.readlines()]


Have a look at Pydantic and swagger integration

Just FYI, the creator of Pydantic is currently working on moving the core functionality to Rust.

Thanks @relsunkaev ! Glad to see the increase in Rust adoption in the Python community :D

Do we have these features yet? @sansyrox
I need them for some production workloads. Moving from fastapi because speed is a req.

Hey @XChikuX 👋
The openapi/swagger will be released in a few weeks. The pydantic integration might take some time.

The pydantic integration might take some time.

Waiting for this 🎉


add two little auth docs blurbs

one blurb adding serverAuth to extendedKeyUsage for server keys
another one linking to AuthZ plugins for more advanced authentication
mechanisms

Signed-off-by: Tycho Andersen<EMAIL_ADDRESS>

@riyazdf @cyli  can one of you help review or delegate this? After you get done, I'll need to do a copyedit before this can go in. Thanks for the submission, @tych0


fix SASL domain fixes #892

setting value as $myhostname will make sasl look for users<EMAIL_ADDRESS>instead of<EMAIL_ADDRESS>

Reading the Postfix manual:
Default authentication domain
Postfix can append a domain name (or any other string) to a SASL login name that does not have a domain part, e.g. "john" instead of<EMAIL_ADDRESS>
/etc/postfix/main.cf:
    smtpd_sasl_local_domain = example.com
This is useful as a default setting and safety net for misconfigured clients, or during a migration to an authentication method/backend that requires an authentication REALM or domain name, before all SMTP clients are configured to send such information.

It should only have effect when no domain is given and this is indeed in my case the issue.
Restarted Travis.


Cannot read property 'setHeader' of undefined

I see an already closed issue on this topic; I'm wondering what the solution to the problem is, and if there's something I am missing to get it to function correctly.
I am receiving this error after wrapping an axios.get request to a Google API endpoint.

Same here, I wish the solution was shared here https://github.com/possibilities/micro-cors/issues/36


Add indicators to the repo

[x] build status
[ ] test coverage - constant nagging reminder to write tests
[x] generate godoc - esp useful for external users
[x] go report card - general code quality

Good enough.
Test coverage measures % of codepaths, covered by unit tests. Bringing it up, due to specifics of this unusual project, would require a lot of effort, sometimes for little return. Most important tests are integration ones anyway.
I would be happy to get back to this wherever we get more resources to write tests.


Hostname confusion in parse-url

Description
Exposure of Sensitive Information to an Unauthorized Actor via hostname confusion in GitHub repository ionicabizau/parse-url prior to 6.0.1
Severity Check

[ ] Low
[ ] Moderate
[X] High
[ ] Critical

Severity Number
7.5
CVSS base metrics

Attack vector
Network

Attack complexity
Low

Privileges required
None

User interaction
None

Scope
Unchanged

Confidentiality
High

Integrity
None

Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weaknesses
CWE-200

CVE ID
CVE-2022-0722

GHSA ID
GHSA-4p35-cfcx-8653

Information

Package
parse-url (npm)

Affected versions
< 6.0.1

Patched versions
6.0.1

References

https://nvd.nist.gov/vuln/detail/CVE-2022-0722

IonicaBizau/parse-url@21c72ab

https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226

P


[firebase_storage] Support the v2 Android embedder plugins API

@amirh
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/308. Any further collaboration will be done there.

To avoid confusing with project https://github.com/flutter/flutter/projects/59 this issue will remain open here till resolved.


New algorithms

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: thomas-bottesch:x: Thomas BotteschThomas Bottesch seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


scoping for v2

Changes
Wrapped all css in every component with :where(.iui-root, [data-iui-theme]) using postcss-scoper. This solves half the problem by making sure that v2 styles stay inside the "root" and don't leak out.
The other half is to prevent v1 styles from leaking into v2. This is done by setting all: revert on every iui element that is a child of v2 root and also a child of a v1 root. The specificity of this selector is 0, so it relies on #1037 (unlayered styles always take preference over layered styles, regardless of specificity).

Both of these changes together make it possible for apps to incrementally migrate to v2 from the bottom up.
There is technically a breaking change in itwinui-variables - iui-root must now always be set instead of relying on variables being automatically added to :root. But in practice, this should not affect anyone because we automatically set this class in itwinui-react, and even in the itwinui-css readme, we ask users to set it.
Testing
Tested a basic version in stackblitz. https://stackblitz.com/edit/vitejs-vite-7qrmeg?file=src%2FApp.jsx
Further testing needed in a real app. For testing, use these versions (might need to force resolve/override/alias in some places):
"@itwin/itwinui-css": "0.63.2-dev.1",
"@itwin/itwinui-react": "1.48.2-dev.2",

"@itwin/itwinui-css": "1.5.0-dev.0",
"@itwin/itwinui-react": "2.4.0-dev.0",
"@itwin/itwinui-variables": "2.0.0-dev.0",

Docs
Added changeset. We should probably also document this in the wiki.

Can we do a dev release and show to Caleb or a a team that could test this soon?

Can we do a dev release and show to Caleb or a a team that could test this soon?

I think we should coordinate with original requestor to test if dev versions works in their app.

I've added a new 'inherit' theme specifically for packages. The idea is that packages using v2 will wrap everything with <ThemeProvider theme='inherit'>. This ensures that the v2 styles stay scoped to the package, and any app that is on v1 will not break and can incrementally adopt the new package. At the same time, this gives apps the ability to control the theme (rather than it being hardcoded in the package).

This is released in the following dev versions:
"@itwin/itwinui-css": "1.5.0-dev.2",
"@itwin/itwinui-react": "2.4.0-dev.3",
"@itwin/itwinui-variables": "2.0.0-dev.1",

In a future major version, we might want to make inherit the default.

I've made one more change. If theme is set to 'inherit', then applyBackground will default to false. Since 'inherit' is meant for packages, it should not have any opinion on the styling.
This was done based on testing in a real scenario. Before this change, sync-report was unnecessarily getting a grey background.


Add size 'small' to Toggle group

Provide a general summary of the feature here
Currently, toggle group component has onle 2 sizes: Mid and Large.  In Editorial Suite, we would like to use size 'small'.
🤔 Expected Behavior?
In Editorial Suite, we are looking forward to replace our old toggle buttons with DS toggle group. However, we need
a) a size small;
b) Ideally, there should be an option that button width adjusts to the text.
c) selected toggle (active state) should be marked with blue color (accent 500 or accent 600 from ES colors)
😯 Current Behavior
Current behaviour

Currently, toggle group component has onle 2 sizes: Mid and Large.
Also, the tabs don't 'hug' the text inside and do not adjust to the text's length. It seems like they have fixed width
Active state of toogle group element has no color.

In Editorial Suite, we are looking forward to replace our old toggle buttons with DS toggle group. However, we need
a) a size small;
b) Ideally, there should be an option that button width adjusts to the text.
c) selected toggle (active state) should be marked with blue color (accent 500 or accent 600 from ES colors)

As you can see in the screenshot, we should try to make toggle group with Editor, Advanced search and Workflows fit to the width of the grey panel below. With the current sizes, we cannot to it. The toggle group takes to much space.
💁 Possible Solution
No response
🔦 Context
We are refreshing the look and feel of Editorial Suite and would really love to use toggle group to replace our old toggles which look a bit outdated.
💻 Examples

👤 Your name
Maria Trybuś
🧢 Your Product/Team
Editorial Suite

@Martrybus we are currently refactoring our components to the new design token setup, in this update we will also add the small toggle group


operator project-quay (3.12.0-nightly.20240707)

Add 3.12.0-nightly.20240707 to community operators

/merge possible

/merge possible


Fix the computation of the re-borrow flags for guaranteed phi arguments

Re-borrow flags were computed based on the presence of forwarding instructions in the incoming values.
This is not correct in all cases, because optimizations can optimize away forwarding instructions.
Now, compute the re-borrow flags based on the presence of an end_borrow in the transitive uses (which is actually the definition of reborrow).
To do this:

Automatically set the re-borrow flags for phi-arguments when creating an end_borrow or setting the operand of an end_borrow. This already  catches most of the cases.
For some optimizations it's required to explicitly update the re-borrow flags. This is done in updateAllBorrowArguments and updateBorrowArguments.

There is still a little problem with dead-end blocks because in dead-end blocks the end_borrow instructions of a re-borrow might be removed. Nevertheless the new approach should be correct. I left a few to-dos in the code which can be resolved once we have complete OSSA lifetimes.
Fixes a verifier crash: rdar://139280579

@swift-ci test

@swift-ci please test source compatibility

@swift-ci test macos

@swift-ci test

@swift-ci benchmark


Unhandled Service: EliotErrors

Following the transition from Samsung ARTIK Cloud to Legrand Cloud, I started receiving errors on my Homebridge R-Pi console (running Homebridge interactively).
The homebridge-lc7001 seems to start normally, however I then start seeing "[LC7001] Unhandled service: EliotErrors" about every 30 seconds.
During this time, I can still work with the LC7001, through HomeKit and HomeBridge, however it seems to eventually become unstable and stop functioning all together, after about 24 hours.
My Legrand 7001 Whole House controller in now running Version 4.0.0-269-gb397

If you are comfortable modifying the code, in lib/lc7001.js, find the following line:
this.log('Unhandled service: ' + response.Service);
Add on the line immediately after it:
this.log(response);
This will cause the plugin to dump the offending JSON object into the log after the error message. Please copy and past a few of the JSON objects that generate this error.

Sure thing, other than the time changing, all the EliotErrors seem to be the same, here is a couple of them:
[9/5/2019, 7:05:32 PM] [LC7001] Unhandled service: EliotErrors
[9/5/2019, 7:05:32 PM] [LC7001] { Service: 'EliotErrors',
CurrentTime:<PHONE_NUMBER>,
EliotConnect: 4,
Connect: 1,
DNS: 3,
UserToken: 1 }
[9/5/2019, 7:06:00 PM] [LC7001] Unhandled service: EliotErrors
[9/5/2019, 7:06:00 PM] [LC7001] { Service: 'EliotErrors',
CurrentTime:<PHONE_NUMBER>,
EliotConnect: 4,
Connect: 1,
DNS: 3,
UserToken: 1 }
[9/5/2019, 7:08:21 PM] [LC7001] Unhandled service: EliotErrors
[9/5/2019, 7:08:21 PM] [LC7001] { Service: 'EliotErrors',
CurrentTime:<PHONE_NUMBER>,
EliotConnect: 4,
Connect: 1,
DNS: 3,
UserToken: 1 }

Added handler for Service=='EliotErrors' in 0.6.0. Strangely, these packets do not have an ID property. Logic that previously declared ID=0 as LC7001-initiated now tests ID=0 OR ID undefined.

Yeah, I noticed that as well. installed 0.61 and I new see "EliotErrors ignored." Thanks!


fix #5099

Added parsing support for oracle unpivot clauses

 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.jiaomy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jiaomy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@jiaom please fix the ci first.

and sign CLA is neccessary.


Enable issue.

Hi man!
I hope you are doing great!
Firstly, I would like to thank your efforts on this plugin!
So, I try to use, but unfortunately I didn't... Rsrsrsr.
As you can see on the image, I just couldn't reach the pane to enable the plugin access.
I try to navigate to the pane but no success at all.
Could you please give me some help?
I think I'm doing something wrong.
Have a nice day!

Hi @Joarell,
first of all thanks for your kind words!
It's a bit tricky with the statusbar and granting permissions. I've introduced a config parameter in v0.2.1, that can be used to enable navigation to the statusbar. It's called first_start "true".
Here's an example:
 pane size=1 borderless=true {
        plugin location="file:target/wasm32-wasi/debug/zjstatus.wasm" {
            format_left  "{mode} #[fg=#89B4FA,bold]{session} {tabs}"
            format_right "{datetime}"
            format_space ""

            first_start                "true"   # this is the important line
    }
}

After the first start the option can be disabled/removed again, but you may need it on updates.
I created a section in the README stating out this problem in the installation, but maybe that's the wrong place or it is written kinda unclear.
Hope the workaround fixes the issue for you.

Perfect!
Now it's working!
Thank you for your prompt reply, my friend!
I really appreciate your work on this plugin!
Have a great day!

i added first_start "true" after the format_space and it still sticks with the asking for permission with y/n and I can't get it to accept it. Did something change?


CompositeStore remove addMarathonApps

I suspect we don't need this being augmented. Let's see tests proving me wrong... or right 💃
I couldn't find a place we use _meta
Testing
Do a smoke test of the UI: Launch an app, a pod and something from the catalog. Look around.

:tada: This PR is included in version 2.40.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Duplicate favicons?

Hello. Thank you very much for making a great Hugo theme.
I tried to customize the favicon in this theme, but just copying and changing favicons.html didn't work. Then I checked with Chrome Devtool and noticed that the link to the icon in the head tag was declared twice.
Here is a link to the page where the link to the icon is listed.
https://github.com/thegeeklab/hugo-geekdoc/blob/main/layouts/partials/head/favicons.html#L1
https://github.com/thegeeklab/hugo-geekdoc/blob/main/layouts/partials/head/others.html#L1

Thanks for reporting! Will be fixed in the next release.


Mapping with a D435i

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ D435i }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win 10

Platform
PC

SDK Version
{ legacy / <IP_ADDRESS>.22 }

Language
{C++ }

Segment
{others }

Issue Description
We want to know if is it possible to do mapping with only a D435i. We already achieve it  with a D415 and a T265 by combining the frames synchronising it with the timestamp and positioning each depth frame with the pose. But the D435i doesn't have pose.
So, can we achieve a similar result with the accelerator or the gyroscope of the D435i?

If you have SLAM mapping in mind, Intel has a SLAM guide for the D435i.
https://github.com/IntelRealSense/realsense-ros/wiki/SLAM-with-D435i

Case closed due to no further comments received.


QueryApi indexer status page

Create a widget that shows the status for all indexers created by a particular user.

Defaults to displaying all dataplatform.near indexers.
Supports query params indexerAccount and indexerFilter. Examples:
https://near.org/near/widget/QueryApi.DataPlatformIndexerStatuses?indexerFilter=verifications
https://near.org/near/widget/QueryApi.DataPlatformIndexerStatuses?indexerAccount=roshaan.near


[Suggestion] VCF sample name

In VCF spec, sample id is required.
so, I think the output sample name can pass by sample ID in VCF.
Thanks in advance!

Thank you for the suggestion. In BAM/VCF mode, the sample ID in the input VCF file or the VCF file name itself is passed to the output sample name. If this is not clear or what you meant is different from our understanding, feel free to ask us again.

@ejalicelee Thanks for your reply. I meant you said that.


Infer numpy dtypes as numba.types.scalars.xxxx

Feature request
It would be useful for the numba type inference system to infer arguments containing numpy types as numba.types.scalars.xxxx.
from __future__ import print_function

import numba
import numpy as np

NoneTypes = (numba.types.misc.NoneType, numba.types.misc.Omitted)

@numba.generated_jit(nopython=True, nogil=True)
def fn(a, b, dtype=None):

    print("Initial dtype", dtype)

    # In case of None, infer type from present input args
    if isinstance(dtype, NoneTypes):
        # Have to produce a numpy dtype here from the numba type names
        out_dtype = np.result_type(*(np.dtype(ary.dtype.name)
                                   for ary in (a, b)
                                   if not isinstance(ary, NoneTypes)))
    else:
        # We should have a proper type here, but numba infers the
        # type of np.int32 as a pyobject, rather than
        # types.misc.npytypes.DType?
        out_dtype = numba.numpy_support.as_dtype(dtype)

    print("final dtype", out_dtype)

    def _fn(a, b, dtype=None):
        return np.ones(a.shape, out_dtype)

    return _fn

a = np.zeros(10)
b = np.zeros(10)

# Succeeds because dtype=None
print("fn(a, b)", fn(a, b))
# Fails because dtype=np.int32 is inferred as a pyobject
print("fn(a, b, dtype=np.int32)", fn(a, b, dtype=np.int32))

I'd imagine this is a fairly simple change, but I find the type system a bit opaque. Could a maintainer suggest where the change might be made?

We are missing a typeof implementation for numpy types.  It should be registered into numba/typing/typeof.py (i.e. https://github.com/numba/numba/blob/e74336755bbba68d800985bd470fa35b9d27d3d3/numba/typing/typeof.py#L196-L199)
It's also missing unboxing logic in numba/targets/boxing.py.

Closed by #3516