libpsyal 4.10

libpsyal 4.10.0 :snowflake:
Destination channel: defaults
Links

PKG-4610
Upstream repository
Upstream changelog/diff

Explanation of changes:

bump version and SHA
removed noarch
added skip for python 3.10 and s390x
added script flags
removed python pinnings under host and run requirements
updated run dependencies and pinnings
added test commands and requires back in
moved summary
added in about description
update home address

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_1df65xgzdz/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:19: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:53: missing_pip_check: For pypi packages, pip check should be present in the test commands
clone/recipe/meta.yaml:67: http_url: http://pysal.org is not https
===== Final Report: =====
2 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_89_0_f4cig/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:19: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:67: http_url: http://pysal.org is not https
clone/recipe/meta.yaml:53: missing_pip_check: For pypi packages, pip check should be present in the test commands
===== Final Report: =====
2 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_1a6c83jfp4/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:19: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_f02q5z_jld/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:19: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found


[release-v1.32] Automated cherry pick of #4950: set include-zones annotation for default domains

/kind/enhancement
/area/control-plane
Cherry pick of #4950 on release-v1.32.
#4950: set include-zones annotation for default domains
Release Notes:
Set `dns.gardener.cloud/include-zones` annotation for the default domain secret in the Gardener controlplane chart.

/invite @stoyanr @ialidzhikov


Add support for filtering / targeting specific components.

We've had a few customers request that they'd like to configure the component to only display notices for specific components, rather than all notices.
Initial thoughts on this are that we want to add data attributes to the tag which accepts the component names of IDs, something like data-only-components="1,4,6" for instance.
These IDs would then be applied to the notice collection, only displaying notices which apply to these components directly.

One potential challenge I foresee in this is the behaviour of nested/grouped components.
Let's assume I have a collection of components as follows.
- Database Servers
    - Postgres
        - US Master
        - US Slave
    - Memcached

Assuming I subscribe my status bar to Postgres component, we'd need to bubble up notices from the US Master and US Slave components, which may be a challenge. The other simpler approach would be to not have bubble-up support, and if you want proper coverage on Postgres you need to filter both it and it's children, and their children etc etc.

Debating adding a new attribute to the API to help with this, perhaps something along the lines of component.impacting which includes all directly and indirectly associated components. Not sure how feasible this is yet, but would make this feature more viable and interesting.

We now have  new set of includes on the components API so we can access anscestors and descendants etc. This should give us what we need to filter notices to those affecting a given component.
Docs on the new include here. https://docs.sorryapp.com/api/v1/reference/pages/components/index.html

I'm back thinking about this feature, I'm going to branch and create a few experiments to see how things progress. I'm going to start with a data- attribute which allows us to filter the results based on components.
One thought which is niggling is whether this should be a generic data- attribute whereby you can define multiple filters, so you only display planned notices for instance? Or only display unplanned?
Worth considering if we can kill two with one stone.

I now a working POC of this feature locally. I'm going to refactor the code a little and update the README to account for the new data- attributes, and then I'll look at wrapping it up into a PR.


[Modules] Added support for Microsoft.web/sites/slots

Description

Thank you for your contribution !

Please include a summary of the change and which issue is fixed.
Please also include the context.
List any dependencies that are required for this change.

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change
Please delete options that are not relevant.

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (readme)
[x] I did format my code

@microsoft-github-policy-service agree

Successfully tested myself. It works and I'll perform the only remaining change as it relates to the test setup exclusively (i.e., merge the slot with the webapp test). Thank you @ladlavj


Dynamic modal mounted() firing twice

Version
vue-final-modal: latest
vue: 3
OS
Windows
Steps to reproduce
Created a dynamic modal and opened it with $vfm.show({component:myModal})
In myModal, the mounted event hook fires twice. Looking at the DOM, the modal is only there once.

I check the behavior in v3.4.8, the mounted hook only emit once


Fix ODR869: Rename graph options 'osName' for Esx to ESXi in Redfish BootImage API

Fix ODR869 and take this chance to fix an outstanding rename work that stated in this issue: https://github.com/RackHD/RackHD/issues/218
@RackHD/corecommitters @gpaulos @cgx027 @pengz1 @iceiilin @WangWinson
Jenkins: depends on https://github.com/RackHD/on-tasks/pull/333

Build finished.

:+1:

jenkins: test this please

Build finished.

:+1:

As @changev replied in  https://github.com/RackHD/on-tasks/pull/333, the Jenkins-Dependency-PR failure is not a problem for this PR itself, there is something wrong for the jenkins result reporting.


About processed data

Hello author, your work is very excellent. I am learning your work and trying to reproduce your results, but I found the results inconsistent with the data I processed. So for better reproduction results, I want to get the processed data you used, I found that the processed data link in this repo is no longer valid, can you reopen the link?

Looking forward to your reply.
Best regards.
Sanm

Hi Sanm,
Thank you for your interest in our work.
Yes, we noticed that the links for the pre-processed data are expired. Sorry for this inconvenience.
We will start uploading them again this week.
Thank you,
Abdelrahman.

Thank you for your reply. Looking forward to your data link, which will enable me to better reproduce your work. Thank you for your selfless sharing and wish you a greater academic harvest.
Best wishes to you
Sanm


Track 'Mailmunch'

Vendor Site - https://www.mailmunch.com/
Example Site - https://www.letrunkshop.com/
Detection - Check for JS object 'mailmunch'

Duplicate of https://github.com/AliasIO/wappalyzer/issues/4444. Closing this.


Add Good Friday for Luxembourg Provider

According to one of our data suppliers (a bank located in Luxembourg) Good Friday is a bank holiday (but not a public holiday).
I will submit a PR.

Also see https://www.officeholidays.com/countries/luxembourg/2019


Fix virtualbox version check in virtualbox_env.sh

The old virtualbox version check fails for VBox 5.0 because 0 is less than the MIN_MINOR of 3.
This check relies on 'bc' to evaluate 4.3 and 5.0 as floats.

I've fixed the commit to use spaces instead of tabs.

This has been tested on Ubuntu. For completeness, needs to be tested on OSX.


Go templates in HTML

Go templates as used by Hugo don't beautify as expected.
This
<!DOCTYPE html>

<html lang="{{ with .Site.LanguageCode }}{{ . }}{{ else }}en-US{{ end }}">

<head>
    {{ partial "head.html" . }}
</head>

<body id="page-top" class="index">

    {{ partial "nav.html" . }}

    {{ partial "header.html" . }}
    {{ partial "portfolio-grid.html" . }}
    {{ partial "about.html" . }}
    {{ partial "contact.html" . }}
    {{ partial "footer.html" . }}
    {{ partial "modals.html" . }}
    {{ partial "js.html" . }}

</body>

</html>

becomes this
<!DOCTYPE html>

<html lang="{{ with .Site.LanguageCode }}{{ . }}{{ else }}en-US{{ end }}">

<head>
    {{ partial "head.html" . }}
</head>

<body id="page-top" class="index">

    {{ partial "nav.html" . }} {{ partial "header.html" . }} {{ partial "portfolio-grid.html" . }} {{ partial "about.html" . }} {{ partial "contact.html" . }} {{ partial "footer.html" . }} {{ partial "modals.html" . }} {{ partial "js.html" . }}

</body>

</html>

Any news on this one?

No, sorry.  There are a number of higher priority features and bugs, and not enough contributors to get to this.


Duplo-21171 RDS TF: Performance insight enable is not working for Cluster DB writer instance. it works when enabled through the API.

Overview
Implemented rds parameter validation and allowed cluster db creation and update for performance insights
Summary of changes
Implemented validation on rds instance that support performance insight and checking storage_type for aurora dbs for duplocloud_rds_instance resource
This PR does the following:

Added customdiff function for rds parameter validation
Added example of cluster db for performance insights
Updated documentation

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[ ✓] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-21171 RDS TF: Performance insight enable is not working for Cluster DB writer instance. it works when enabled through the API.


UE Register to 5G core

Hello,
I installed the free5GC Stage 3 Installation Guide from this link " https://www.free5gc.org/installations/stage-3/" by fallow this link "https://www.free5gc.org/stage-3-videos/create-ubuntu-machine/" and the UERANSIM from " https://github.com/aligungr/UERANSIM/wiki/Installation".
At the beginning, everything went fine, I installed the 5G core and UERANSIM as well in different VMs.
For the 5G VM when i run the test some time fail and some time pass. Dose anyone have an idea why that's happened.
In the  UERANSIM VM, the UE connect to the RAN and RAN connect the free5GC VM.
but the UE lost acconection, as i see i had a connection failure.

And when i try to run the RAN and the UE again i get this issues..

free5gc .:run.sh log file.zip
I new to 5G and Go lang.
I have another question, now in my AMF, SMF and NSSF, I have S-NSSAIs information, How can I attach the UE information including the S-NSSAIs in the test file to do the registration and authentication and send PDU session.
For example, we have a user connect to a 5G network, I want to make this user connect to slice 1 and slice 2 and if the user chooses to connect to another slice or service, My system will accept the connection. and I will know the slice id, slice number, slice service for each user in my 5G network.
Do i need to add these information to the registration_test.go file. In the registration_test.go, I can see the imsi information and servingPlmnId and the S-NSSAIs in PDU section.
In this case, I could avoid any error happened in UERANSIM VM. I tried to use the Webconsole but with it just sent the registration part.
Thanks,
Noor

Hi @noormohammedli
I think you was not create the UE subscriber on free5gc WebUI
or the UE subscriber Information not correct.
In UERANSIM UE setup config file,
It used the free5gc WebUI default UE Subscriber Information
Maybe you should try the default UE with UERANSIM first !

Hello @j13tw,
Thanks for your reply.
When I tried the default UE I got an error with plmn-id/ no cell available as in the image below.

Thanks.

Hello @j13tw,


Streaming Error: TypeError: dumps_kwargs keyword arguments are no longer supported.

Receiving the following when attempting to enable streaming on the server.
The model returns successfully without streaming (ie stream key removed)!
This worked in the past but
vllm 0.1.2
RTXA6000
Docker startup script
bash -c 'pip install --upgrade huggingface_hub && huggingface-cli login --token $HUGGINGFACE_TOKEN && pip install vllm && python -m vllm.entrypoints.openai.api_server --host <IP_ADDRESS> --port 8000 --model my_model --tokenizer hf-internal-testing/llama-tokenizer'

Prompt
{
    "model": "my_model",
    "prompt": "###System: You are world class assistant. Answer the question, provide solutions, and justify your reasoning step by step. \n ###Human: Hello. \n ###Assistant:",
    "max_tokens": 1000,
    "temperature": 0.7,
    "user": "test-user-id",
    "stream": true
}

Error
2023-07-10T20:53:51.940730783Z ERROR:    Exception in ASGI application
2023-07-10T20:53:51.940756172Z Traceback (most recent call last):
2023-07-10T20:53:51.940758164Z   File "/usr/local/lib/python3.10/dist-packages/uvicorn/protocols/http/h11_impl.py", line 428, in run_asgi
2023-07-10T20:53:51.940760457Z     result = await app(  # type: ignore[func-returns-value]
2023-07-10T20:53:51.940762539Z   File "/usr/local/lib/python3.10/dist-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
2023-07-10T20:53:51.940764779Z     return await self.app(scope, receive, send)
2023-07-10T20:53:51.940770548Z   File "/usr/local/lib/python3.10/dist-packages/starlette/applications.py", line 122, in __call__
2023-07-10T20:53:51.940772131Z     await self.middleware_stack(scope, receive, send)
2023-07-10T20:53:51.940773663Z   File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 184, in __call__
2023-07-10T20:53:51.940775505Z     raise exc
2023-07-10T20:53:51.940777499Z   File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 162, in __call__
2023-07-10T20:53:51.940779268Z     await self.app(scope, receive, _send)
2023-07-10T20:53:51.940780702Z   File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/cors.py", line 83, in __call__
2023-07-10T20:53:51.940782355Z     await self.app(scope, receive, send)
2023-07-10T20:53:51.940783900Z   File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/exceptions.py", line 79, in __call__
2023-07-10T20:53:51.940785552Z     raise exc
2023-07-10T20:53:51.940787124Z   File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/exceptions.py", line 68, in __call__
2023-07-10T20:53:51.940788652Z     await self.app(scope, receive, sender)
2023-07-10T20:53:51.940790181Z   File "/usr/local/lib/python3.10/dist-packages/fastapi/middleware/asyncexitstack.py", line 20, in __call__
2023-07-10T20:53:51.940795248Z     raise e
2023-07-10T20:53:51.940796831Z   File "/usr/local/lib/python3.10/dist-packages/fastapi/middleware/asyncexitstack.py", line 17, in __call__
2023-07-10T20:53:51.940798375Z     await self.app(scope, receive, send)
2023-07-10T20:53:51.940799902Z   File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 718, in __call__
2023-07-10T20:53:51.940801419Z     await route.handle(scope, receive, send)
2023-07-10T20:53:51.940802971Z   File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 276, in handle
2023-07-10T20:53:51.940804555Z     await self.app(scope, receive, send)
2023-07-10T20:53:51.940806108Z   File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 69, in app
2023-07-10T20:53:51.940816066Z     await response(scope, receive, send)
2023-07-10T20:53:51.940818700Z   File "/usr/local/lib/python3.10/dist-packages/starlette/responses.py", line 270, in __call__
2023-07-10T20:53:51.940820399Z     async with anyio.create_task_group() as task_group:
2023-07-10T20:53:51.940821903Z   File "/usr/local/lib/python3.10/dist-packages/anyio/_backends/_asyncio.py", line 597, in __aexit__
2023-07-10T20:53:51.940823475Z     raise exceptions[0]
2023-07-10T20:53:51.940825447Z   File "/usr/local/lib/python3.10/dist-packages/starlette/responses.py", line 273, in wrap
2023-07-10T20:53:51.940826917Z     await func()
2023-07-10T20:53:51.940828421Z   File "/usr/local/lib/python3.10/dist-packages/starlette/responses.py", line 262, in stream_response
2023-07-10T20:53:51.940829925Z     async for chunk in self.body_iterator:
2023-07-10T20:53:51.940831499Z   File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/api_server.py", line 196, in completion_stream_generator
2023-07-10T20:53:51.940833468Z     response_json = create_stream_response_json(
2023-07-10T20:53:51.940835024Z   File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/api_server.py", line 175, in create_stream_response_json
2023-07-10T20:53:51.940836571Z     response_json = response.json(ensure_ascii=False)
2023-07-10T20:53:51.940838017Z   File "/usr/local/lib/python3.10/dist-packages/typing_extensions.py", line 2562, in wrapper
2023-07-10T20:53:51.940839550Z     return __arg(*args, **kwargs)
2023-07-10T20:53:51.940841138Z   File "/usr/local/lib/python3.10/dist-packages/pydantic/main.py", line 926, in json
2023-07-10T20:53:51.940842739Z     raise TypeError('`dumps_kwargs` keyword arguments are no longer supported.')
2023-07-10T20:53:51.940844730Z TypeError: `dumps_kwargs` keyword arguments are no longer supported.
2023-07-10T20:53:53.675581382Z INFO:     <IP_ADDRESS>:35994 - "GET / HTTP/1.1" 404 Not Found

same error


torch_cluster version incompatible

Hi thanks for the great work and sharing the codes!
I have tried to install the package using build_env.sh on Debian x86_64 GNU/Linux, cuda 11.3 machine. But got torch_cluster incompatible with cuda issue, below is the error information:
    return torch.ops.torch_cluster.radius(x, y, ptr_x, ptr_y, r,
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
                                          max_num_neighbors, num_workers)
RuntimeError: Not compiled with CUDA support

Here is my env:
# Name                    Version                   Build  Channel
torch                     1.12.0+cu113             pypi_0    pypi
torch-cluster             1.6.1                    pypi_0    pypi
torch-ema                 0.3                      pypi_0    pypi
torch-geometric           2.3.1                    pypi_0    pypi
torch-scatter             2.1.1                    pypi_0    pypi
torch-sparse              0.6.17                   pypi_0    pypi
torchaudio                0.12.0+cu113             pypi_0    pypi
torchvision               0.13.0+cu113             pypi_0    pypi

I see you run the model on linux cuda11.3 machine as well, would you mind sharing your env information of torch-pkg here, please?
Thanks

Hi, sorry for the delay in responding!
Let me retry creating the environment on the cluster and see if the instructions work as expected.

I cleared the environment installation, and removed any cache, and recreated the environment. This is how it looks for me:

This environment was made on a cluster node that only has cpu nodes, so maybe there is an installation different on a pure GPU node.
Let me know if clearing the cache and environment and rerunning ./build_env.sh fixes your issue

Closing this issue right now -- feel free to reopen if necessary!


Move Clear Project to bottom

https://circuitverse.org/forum/threads/clear-project#forum_post_33
Send PR to new_UI branch.

I am Working on this issue

@Lahirutech set newUi as the target branch as issue states

Done


[Event Request] Page "Sales Statistics" OnAfterUpdateHeaderInfo Additional Parameters

TotalAmount 1 and Total Amount 2 are changed in our case due to exchange part management. Therefore we need 2 more parameters.
[EventSubscriber(ObjectType::Page, Page::"Sales Statistics", 'OnAfterUpdateHeaderInfo', '', true, true)]
local procedure "Sales Statistics_OnAfterUpdateHeaderInfo"(TotalSalesLineLCY: Record "Sales Line"; var TotalAmt1: Decimal; var TotalAmt2: Decimal )

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


prevent  error in Grover's algorithm tutorial

URL to the relevant documentation
https://learning.quantum.ibm.com/tutorial/grovers-algorithm
Select all that apply

[ ] typo
[ ] code bug
[ ] out-of-date content
[ ] broken link
[ ] other

Describe the fix.
With the current definition, the grover_oracle function does not take into account inputs (marked_states) without '0', indeed it returns the error " CircuitError: 'One or more of the arguments are empty' ", because zero_inds_ is empty.
Although in the tutorial this error is not encountered, since marked_states = ["011", "100"], it might be useful to modify the grover_oracle function to handle also this case and make the function more general for other applications.
For example, the following piece of code can solve the issue
        if len(zero_inds)==0:
            qc.compose(MCMT(ZGate(), num_qubits - 1, 1), inplace=True)
            continue

inserted before
        qc.x(zero_inds)
        qc.compose(MCMT(ZGate(), num_qubits - 1, 1), inplace=True)
        qc.x(zero_inds)

Looks like this one should be moved here https://github.ibm.com/IBM-Q-General/ibm-quantum-learning-enablement/issues, @Eric-Arellano or @javabster

Handed this off to the learning team.


Question: What are URL variables in front end rules used for?

The front ends section of the basic docs states that URL variables can be defined in rules, e.g.:
Path: /products/, /articles/{category}/{id:[0-9]+}

As far as I can tell, these variables are not used for anything downstream.
Have I missed something?

It isn't about adding variables that are passed downstream it is about putting RegEx into the path that you can easily reason about... I think.
Imagine you had a route something like /products/{id: [0-9]+}/details/ and another route /products/{id: [0-9]+}/related/ and that each of those went to different backends. You need to be able to tell the Traefik to route to specific backend services with a variable in the path.
I don't know the original reasoning for allowing you to name the RegEx groups but I know I use it so that it is easier to read the configs.
/articles/{}/{[0-9]+}/details/ and /articles/{}/{[0-9]+}/related/ are both far harder to read and understand when they don't have names, especially when you start getting lots of them.

Thanks for following up!
Having patterns/regular-expressions in the paths being matched makes sense.
I'm still mystified by this bit from the example: /articles/{category}/{id:[0-9]+}.  I think that {category} is actually shorthand for {category:.+}, which in turn is actually a verbose way of writing {.+}, since the labels don't seem to ever be used for anything.
I disagree about your final point (particularly if you actually put a .+ in the second part of the paths in your example).  They're just patterns to be matched.  Naming them only adds to the complexity ("in my opinion..." :smile:), the additional complexity is worth putting up with if you're going to use the names downstream, otherwise it's only overhead.
I thought that they might be useable as part of the path component of the backend url, but based on experimentation only the scheme, host, and ports part of the backend url are used.  These two seem to function identically:
http://<IP_ADDRESS>:8080
http://<IP_ADDRESS>:8080/bar

I thought perhaps one could do:
http://<IP_ADDRESS>:8080/bar

Hi !
Have a look to underlying router (ie. gorilla/mux) : http://www.gorillatoolkit.org/pkg/mux#Route.Path

@ThinkBriK -- So the gorilla/mux docs say this:

They can be retrieved calling mux.Vars(request).

Are those matches used for anything in traefik?
g.

As far as I know : no...
But at least it's easier to understant the "why"  (underlying component notation).

Got it.  Sounds reasonable.

@hartzell:

I think that {category} is actually shorthand for {category:.+}, which in turn is actually a verbose way of writing {.+}, since the labels don't seem to ever be used for anything.

I don't think it's a short-hand for {.+}: According to the Gorilla documentation, the default is to match until the next slash. Quoting (emphasis by me):

Paths can have variables. They are defined using the format {name} or {name:pattern}. If a regular expression pattern is not defined, the matched variable will be anything until the next slash.

So I guess you could say it's a short-hand for {category:[^/]*}.
The naming seems to be needed only for the sake of being able to define a regular expression.


wallbox charger

It would be really awesome if can add some for  wallbox charging station
it has build in integration :
https://www.home-assistant.io/integrations/wallbox/

Hi,
Would be great! Shouldn't be a problem to implement it, but I won't personally spend time on studying the documentation. If you could give an overview of the sensors (and services if applicable), I may assist in creating a 'proof-of-concept' that you could further work on.

Hi,
Would be great! Shouldn't be a problem to implement it, but I won't personally spend time on studying the documentation. If you could give an overview of the sensors (and services if applicable), I may assist in creating a 'proof-of-concept' that you could further work on.

@tmjo - great new , appreciate your help
below are all wallbox entities
couldn't find services
{% for state in states if (state.entity_id.find("wallbox") | int>=0) %}
{{state.entity_id }}
{% endfor %}

lock.wallbox_portal_locked_unlocked
number.wallbox_portal_max_charging_current
sensor.wallbox_portal_added_energy
sensor.wallbox_portal_added_range
sensor.wallbox_portal_charging_power
sensor.wallbox_portal_charging_speed
sensor.wallbox_portal_cost
sensor.wallbox_portal_current_mode
sensor.wallbox_portal_depot_price
sensor.wallbox_portal_discharged_energy
sensor.wallbox_portal_max_available_power
sensor.wallbox_portal_max_charging_current
sensor.wallbox_portal_state_of_charge
sensor.wallbox_portal_status_description
switch.wallbox_portal_pause_resume

please let me know if anything else is needed

Please allow me to second the request.

@avico78 After playing with the configuration posted with the Card, I have come to the conclusion that the most difficult part is deciding what data to display where - there is so much flexibility here.  I am displaying a blend of information from the WallBox Pulsar Plus, the car and other sources - but my configuration is very much a work in process - I still have a ton of place holder " sensor.CHARGERNAME_' or "evsee" entries.
entity: sensor.wallbox_portal_status_description
customCardTheme: theme_custom
brand: WallBox
show_leds: true
details:
  name:
    entity_id: sensor.eva_plugged_in_to_evse
  status:
    entity_id: sensor.wallbox_portal_status_description
  currentlimits:
    - 0
    - 6
    - 10
    - 16
    - 20
    - 25
    - 32
    - 40
  statetext:
    Unplugged: Unplugged
    Scheduled: Scheduled
    Charging: Charging
    Waiting for car demand: Waiting for car demand
    error: error
    Ready: Ready
  collapsiblebuttons:
    group1:
      text: click_for_group1
      icon: mdi:speedometer
    group2:
      text: Click for Information
      icon: mdi:information
    group3:
      text: Click for Settings
      icon: mdi:cog
  info_left:
    - entity_id: switch.wallbox_portal_pause_resumee
      text: Pause/Resume
  info_right:
    - entity_id: sensor.wallbox_portal_depot_price
      text: Price per kWh
      unit_show: true
    - entity_id: number.wallbox_portal_max_charging_current
      text: Power (Amps)
      unit_show: true
  group1:
    - entity_id: sensor.wallbox_portal_charging_power
      text: dyn_charger_limit
      service: null
      service_data:
        charger_id: CHARGERID
        current: '#SERVICEVAL#'
    - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit
      text: dyn_circuit_limit
      service: sensor.wallbox_portal_max_charging_current
      service_data:
        charger_id: CHARGERID
        currentP1: '#SERVICEVAL#'
    - entity_id: sensor.CHARGERNAME_max_charger_limit
      text: max_charger_limit
      service: number.wallbox_portal_max_charging_current
      service_data:
        charger_id: CHARGERID
        current: '#SERVICEVAL#'
    - entity_id: sensor.CHARGERNAME_max_circuit_limit
      text: max_circuit_limit
      service: sensor.wallbox_portal_max_available_power
      service_data:
        charger_id: CHARGERID
        currentP1: '#SERVICEVAL#'
    - entity_id: sensor.CHARGERNAME_offline_circuit_limit
      text: offline_circuit_limit
      service: null
      service_data:
        charger_id: CHARGERID
        currentP1: '#SERVICEVAL#'
  group2:
    - entity_id: sensor.CHARGERNAME_voltage
      text: voltage
      unit_show: true
    - entity_id: sensor.wallbox_portal_charging_power
      text: power
      unit_show: true
    - entity_id: sensor.wallbox_portal_charging_speed
      text: charger_current
      unit_show: true
    - entity_id: sensor.wallbox_portal_max_charging_current
      text: circuit_current
      unit_show: true
    - entity_id: sensor.CHARGERNAME_energy_per_hour
      text: energy_per_hour
      unit_show: true
    - entity_id: sensor.wallbox_portal_discharged_energy
      text: session_energy
      unit_show: true
  group3:
    - entity_id: lock.wallbox_portal_locked_unlocked
      text: enabled
    - entity_id: switch.CHARGERNAME_enable_idle_current
      text: idle_current
    - entity_id: binary_sensor.CHARGERNAME_cable_locked
      text: cable_locked
    - entity_id: switch.CHARGERNAME_cable_locked_permanently
      text: perm_cable_locked
    - entity_id: switch.CHARGERNAME_smart_charging
      text: smart_charging
    - entity_id: sensor.CHARGERNAME_cost_per_kwh
      text: cost_per_kwh
    - entity_id: binary_sensor.CHARGERNAME_update_available
      text: update_available
    - entity_id: binary_sensor.CHARGERNAME_basic_schedule
      text: schedule
  stats:
    default:
      - entity_id: sensor.wallbox_portal_charging_power
        text: Charge Draw
        unit_show: true
      - entity_id: sensor.wallbox_est_added_range_mi
        text: Added Range
      - entity_id: sensor.fordpass_elveh
        text: Range
    disconnected:
      - entity_id: sensor.wallbox_portal_max_available_power
        text: output_limit
        unit_show: true
      - entity_id: sensor.wallbox_portal_discharged_energy
        text: session_energy
        unit_show: true
      - entity_id: lock.wallbox_portal_locked_unlocked
        text: cable_locked
      - entity_id: calculated
        text: used_limit
        unit: A
        unit_show: true
        calc_function: min
        calc_entities:
          - entity_id: sensor.CHARGERNAME_dynamic_charger_limit
          - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit
          - entity_id: sensor.CHARGERNAME_max_charger_limit
          - entity_id: sensor.CHARGERNAME_max_circuit_limit
          - entity_id: sensor.CHARGERNAME_offline_circuit_limit
    awaiting_start:
      - entity_id: sensor.wallbox_portal_discharged_energy
        text: session_energy
        unit_show: true
      - entity_id: binary_sensor.CHARGERNAME_basic_schedule
        text: schedule
      - entity_id: switch.wallbox_portal_pause_resume
        text: smart_charging
      - entity_id: calculated
        text: used_limit
        unit: A
        unit_show: true
        calc_function: min
        calc_entities:
          - entity_id: sensor.wallbox_portal_charging_power
          - entity_id: sensor.wallbox_portal_charging_speed
          - entity_id: number.wallbox_portal_max_charging_current
          - entity_id: sensor.wallbox_portal_max_charging_current
          - entity_id: number.wallbox_portal_max_charging_current
    Charging:
      - entity_id: sensor.eva_charge_complete
        text: Session End
        unit_show: true
      - entity_id: number.wallbox_portal_max_charging_current
        text: Charge Speed
        unit: A
        unit_show: true
      - entity_id: sensor.wallbox_portal_charging_power
        text: Charge Draw
        unit_show: true
      - entity_id: sensor.wallbox_est_added_range_mi
        text: session_energy
        unit_show: true
      - entity_id: sensor.wallbox_portal_added_energy
        text: Charged
        unit_show: true
    Waiting for car demand:
      - entity_id: sensor.wallbox_portal_added_energy
        text: Session energy
        unit_show: true
      - entity_id: sensor.eva_cost_last_charge
        text: CostLast Charge
        unit: $
        unit_show: true
      - entity_id: sensor.fordpass_elveh
        text: Currnt Range
        unit: mi
        unit_show: true
    error:
      - entity_id: sensor.wallbox_portal_added_energy
        text: session_energy
        unit_show: true
    Scheduled:
      - entity_id: sensor.wallbox_portal_status_description
        text: Charger Status
      - entity_id: input_number.ev_charge_target
      - entity_id: sensor.eva_hv_state_of_charge
      - entity_id: calculated
        text: Charging Power
        unit: A
        unit_show: true
        calc_function: min
        calc_entities:
          - entity_id: sensor.wallbox_portal_max_available_power
          - entity_id: number.wallbox_portal_max_charging_current
      - entity_id: sensor.eva_charge_start
        text: Start Time
        unit_show: true
      - entity_id: sensor.eva_charge_complete
        text: Finished
        unit_show: true
  toolbar_left:
    default:
      - {}
    disconnected:
      - {}
    awaiting_start:
      - service: easee.stop
        service_data:
          charger_id: CHARGERID
        text: stop
        icon: hass:stop
      - service: easee.resume
        service_data:
          charger_id: CHARGERID
        text: resume
        icon: hass:play
      - service: easee.override_schedule
        service_data:
          charger_id: CHARGERID
        text: override
        icon: hass:motion-play
    charging:
      - service: easee.stop
        service_data:
          charger_id: CHARGERID
        text: stop
        icon: hass:stop
      - service: easee.pause
        service_data:
          charger_id: CHARGERID
        text: pause
        icon: hass:pause
    completed:
      - service: easee.stop
        service_data:
          charger_id: CHARGERID
        text: stop
        icon: hass:stop
      - service: easee.override_schedule
        service_data:
          charger_id: CHARGERID
        text: override
        icon: hass:motion-play
    error:
      - service: easee.reboot
        service_data:
          charger_id: CHARGERID
        text: reboot
        icon: hass:restart
    ready_to_charge:
      - service: easee.stop
        service_data:
          charger_id: CHARGERID
        text: stop
        icon: hass:stop
      - service: easee.override_schedule
        service_data:
          charger_id: CHARGERID
        text: override
        icon: hass:motion-play
  toolbar_right:
    default:
      - service: persistent_notification.create
        service_data:
          message: Firmware update is available, but only possible when disconnected!
          title: Update
        text: update
        icon: mdi:file-download
        conditional_entity: binary_sensor.CHARGERNAME_update_available
    disconnected:
      - service: easee.update_firmware
        service_data:
          charger_id: CHARGERID
        text: update
        icon: mdi:file-download
        conditional_entity: binary_sensor.CHARGERNAME_update_available

wow looking absolutely great , thanks appreciate your help!
is there an option to change the size/color of the led that indicate the station status?
specifically between ideal mode ("Disconnected/Ready") to "Charging"?
is possible to customize and change the charger picture to other model?
If u have plans to make this (great!) card more versatile and support more charger stations it could be
really great if the card will be able to use different charger satiation templates ,
again thanks much for your efforts!

Hi, working on a simple template for this to make it easy to set up. I see you have some sensors named eva_xxxx as opposed to the majority which are called wallbox_portal_xxxx. Is this something you've made yourself?
Reason for asking is that my idea is that the default templates works 'out-of-the-box' with the integrations, so in case there is something custom that's great, but not something we would want in the templates.
I see eva_xxxx is used for name, charging stat for session end, waiting for carm demand stat for cost_last_charge, scheduled stats for hv_state_of_carge + start time and charge complete.
Don't misunderstand me, if this is custom, I would do the same as you and it is indeed the purpose of having the card fully customizable,  but I just want to keep the templates 'clean' so need to understand what is done.

Also, there seems to be something fishy about the service calls. Does Wallbox provide services that you can call to, for instance, reduce max current and stuff? I see some of the config in your example seems to be from the Easee template, so I assume they will not work properly.

@tmjo - the ev_ sensor i added us something can be ignore ,
it just predefine sensor that automatically setting up the charging station amperage .
it is transparent so can be ignore .
But it would be great to have sliders where possible to adjust the station amperage .
One more thing i do think would be very useful is the visibility of some statistics of station connectivity ,
it just unbelievable how many time the station is getting disconnected .
Thanks much for working on this - I do believe such solution would become quite handy for EV car users.
btw - do u know what is most popular charging station for Tesla?
asking cause of the popularity of Tesla ...it might worth including a template for it .
of the statics for the charging station connectivity ,
it just unbelievable how many time the station get disconnected .

Great, I'll make something based on the list you added in previous post. Let's see if it works, if not let's adjust. I note that there are some entities you did not include in your example, are they not interesting?
I agree on your comment about stability for disconnection. I, for one, am a strong believer in local communication and not depending on cloud which most chargers seem to do. The same with my Easee charger. But to add any statistic on it, we need a sensor that shows connected or disonnected. The Easee-integration has something, but it is really quite hacky and not very reliable.

@tmjo
'I see you have some sensors named eva_xxxx as opposed to the majority which are called wallbox_portal_xxxx. Is this something you've made yourself?'
The sensors eva_xxxx are templated sensors from my FordPass integration - there are just some data points that I don't see as available thru the WallBox data set.

@tmjo 'I see you have some sensors named eva_xxxx as opposed to the majority which are called wallbox_portal_xxxx. Is this something you've made yourself?'
The sensors eva_xxxx are templated sensors from my FordPass integration - there are just some data points that I don't see as available thru the WallBox data set.

Right, thanks! I saw now that it was your example.

please ignore my comment for :
@tmjo - the ev_ sensor i added us something can be ignore ,
it just predefine sensor that automatically setting up the charging station amperage .
it is transparent so can be ignor

(I actually added similar entity and confused with the question )
@tmjo  - are u planning to have one "generic" card which can adbot different templates ?
I think this approach could be interested as it future proof for support different charging stations
and people can reuse the other templates.
for customization -
maybe worth thinking how this solution could be flexible for adding personal customizations
of course with the limitation of the functionalities provided,
but for adding some more informative sensor or button to trigger some automation could be useful.

please ignore my comment for :
@tmjo - the ev_ sensor i added us something can be ignore ,
it just predefine sensor that automatically setting up the charging station amperage .
it is transparent so can be ignor

(I actually added similar entity and confused with the question )
@tmjo - are u planning to have one "generic" card which can adbot different templates ? I think this approach could be interested as it future proof for support different charging stations and people can reuse the other templates.
for customization - maybe worth thinking how this solution could be flexible for adding personal customizations of course with the limitation of the functionalities provided, but for adding some more informative sensor or button to trigger some automation could be useful.

No worries!
The card is already fully customizable for people who has YAML-skills and some knowledge of HA and the integration they use, of course within the functionality provided by the card. Personally I am using the card for my charger, my e-Golf car, a weather integration and an integration showing details of tidal conditions. So it is very flexible as it is today, and the plan is to continue developing the flexibility.
However, "most" people find this very complex, so my intention with templates/brand is to simplify it so they only add a "main" sensor and the rest is taken care of by the template. Obviously, I will rely heavily (if not solely) on the community to maintain the templates as it is impossible for me to test it (without having the devices) and also extremely time-consuming to have to read up on every integration. So the idea is to help get people started with some templates, and let a few persons be key-person for maintaining that template for the card.
I am doing some work right now to convert all code into Typescript instead of pure Javascript, mainly as this gives more concise code and I believe TS is the future, but also because I need to do some work to fix the UI-config after some breaking changes in HA. I've got it almost ready, and that will (hopefully) make it easier for skilled people to contribute easier than before to the templates.

Hi!
I'd love to add support for this charger, but kindly read the wiki on how-to. Let me know if anything is unclear and I'll update it or try to explain.
Cheers!


Automatically add .html to generated archives names without extension

Hi,
If you use an archive permalink that is not a directory and not ending by .html, such as /:year, it generates a file without extension, instead of adding .html (unlike with Jekyll's post permalink).
I'd like to add the html extension without having page.url containing it (would be the case if you use /:year.html).
Note that I actually use the v2.1.1 tagged version.

Hmm, the commit message may not be good as I'm checking for .html$ and not if there isn't an extension.

This is exactly what we need and would add parity with how Jekyll's own permalinks work.
For example in Jekyll:
collections:
posts:
permalink: /posts/:year/:month/:day/:title
will produce files at /posts/2020/06/11/mypost.html
and permalink (page.url) of /posts/2020/06/11/mypost
The latter is how we want to serve them (and how they should appear in canonical links and sitemaps etc, which use the page.url variable)
However in Jekyll-archives:
jekyll-archives:
permalinks:
year: '/posts/:year'
will produce the correct permalink but output the wrong file (without .html extension)
and
jekyll-archives:
permalinks:
year: '/posts/:year.html'
will output to the right file but have the wrong permalink.

A partial workaround is to strip .html when printing links to archives, but you can't fix it for plugins reading the permalink (such as for jekyll-sitemap).
{%- for archive in year_archives reversed %}

{{ archive.date | date: "%Y" }}

{%- endfor %}


materialize release_build_status view for performance

I pulled a prod backup and ran some manual tests, and I think I found the performance issue.
In the performance logs I saw slow release pages, slow rustdoc pages & crate details. Manual test did show the same slow performance when testing with the prod database.
What they have in common is fetching data from the release_build_status view.
Similar to what we do with latest_version_id, we now normalize the aggregated values.
I leaned towards still having it in a separate table, more like a materialized auto-updated view.
While we could also use triggers, I followed the same pattern as our latest_version_id for updates: use our data layer and normal SQL in the right places.
deploy
for the deploy, this time I'll actually shut down both servers to avoid most of the errors and potential inconsistencies. migrations should run in around 10-15 seconds.

@Nemo157 I added the foreign key constraint, good idea, I only extended it with ON DELETE CASCADE.
Also, can you check what happens when you run just sqlx-prepare locally on your computer after running the migrations?
On my system it it doesn't create any changes, but it seems like CI fails.


Added trial hierarchy of building system

@Exactlywb, @pavel-collab,
Please, review it, try on your machines and ask your questions

Looks well to me but some issues is still relevant:

I've not found .clang-format file so it looks like make format doesn't work just now.
It doesn't seem to me that uncommenting lines with run-clang is the best way.  Maybe it'd be better to submit flag in cmake running like

$ cmake -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_RUN_CLANG=1

Update README.md pls

Remove commented parts of code.
Need to write requirements for the system (if it need of course) like: tools for build and installing, compiler version etc.
In my opinion, it need to add comments for the basic parts of code. For example if we have static char S array, I think it need to write a comment, that provide to understand what is it and where do we use it. It need to make code navigation faster and more clear understanding.
Make a small build instruction (especially for me, as I don't check the project as often as you).

Thank you for attention to details!

Thakns for your comments. I will consider all these notes this evening

I've updated README and add .clang-format file (you can configure it in another way -- make a new PR :) ).
LGTM for me

Confirmed.


Questions on rollout procedure in run_amp.py

Hello,
First thank you for this amazing work. I'm starting to work on rna sequence design and GFlowNet is definitely an interesting direction.
I have question for the RolloutWorker in run_amp.py, specifically the section line 248 to 254.
https://github.com/MJ10/BioSeq-GFN-AL/blob/c641269de9e365517db2b8de4452372be7fb3733/run_amp.py#L248-L254
I understand that we are curating a batch of trajectories to train the generator.  And first we sample some trajectories based on exploration policy, then we sample some sequences in the dataset directly.  And in the section listed above, given some sequences sampled from the dataset, we are adding the correspondent trajectories of the DAG.
My question is on the line 250... what is that -2 doing? It does not make too much sense to me as the character ID correspond to the action index of the mlp exactly  .
Also I saw a small bug on the line 233
https://github.com/MJ10/BioSeq-GFN-AL/blob/c641269de9e365517db2b8de4452372be7fb3733/run_amp.py#L233
It should be self.args instead of args
Thank you

My question is the same as this, why there is a -2 in line 250, it doesn't make any sense


removed unused code, added tests, slight api improvements

removed on hold because the target branch is next.

How can you be sure that these changes to not break something? What is the test coverage on the files touched in this PR? Also I kind of think the changes solve multiple different issues but might even change behaviour and are not only refactoring. The PR title is as telling as "Doing some work". Has the reviewer really checked out the code run and tested the app thoroughly?


highlight today with special color

I don't get it, could you explain?

when I run rusti-cal 2021, I can't find today quickly. With special color, I can locate it quickly


Expose non-contiguous deleted messages ranges stats.

Motivation
Expose non-contiguous deleted messages ranges stats.
Verifying this change
New test added.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)

/pulsarbot run-failure-checks


Migrated to Google MLKit

Description
The Firebase ML Vision has been discontinued and this repo has been migrated to the lates Google MLKit. The whole codebase dependencies have been updated to the latest version.
Dependencies
please note down the dependencies that use in this code change.
For example

camera: ^0.9.4+5
firebase_core: ^1.10.0
camera: ^0.5.8+2
firebase_ml_vision: ^0.6.0
path_provider: ^1.6.11
tflite_flutter: ^0.4.1
image: ^2.1.12
google_ml_kit: ^0.7.3
image: ^3.0.8
path_provider: ^2.0.7
tflite_flutter: ^0.9.0

Native Dependencies
please note down the native dependencies that use in this code change. Which can have issues with code push
For example
flutter-sdk: ">=2.12.0 <3.0.0"
checklist

[ ✓] used convection commits

Creating inputimage and using imglib.getRed() in these package versions
Functions such as are no longer available.
Could you please update?
environment:
sdk: ">=2.12.0 <3.0.0"
dependencies:
camera: ^0.10.5+7
cupertino_icons: ^1.0.6
firebase_ml_vision: ^0.12.0+3
flutter:
sdk: flutter
google_ml_kit: ^0.16.3
google_mlkit_commons: ^0.6.1
image: ^4.1.3
path_provider: ^2.0.7
tflite_flutter: ^0.10.4
dev_dependencies:
flutter_test:
sdk: flutter


ARROW-4675: [Python] Fix pyarrow.deserialize failure when reading payload in Python 3 payload generated in Python 2

I'm not sure how to unit test this.

+1. I think it's OK to have these "untested" fixes to hold us over until we can stop supporting Python 2.7


Calendar with time lacks visual cue for next action

With the basic flatpickr calendar, the UX is extremely elegant. The moment one clicks a day number, the calendar popup closes. But when the calendar shows the time inputs via enableTime: true, there is no intuitive next step.

Yes, anyone with half a brain will eventually click the background, away from the calendar, to close it. But not before wasting a moment to think "Wait, where's the OK button?". Even darkening the background onOpen and fading it onClose, as I've done in my test implementation, is insufficient in communicating a next step.
Since the user will have to click once more anyways to close the calendar, I'd much rather give them something to click, with a behavior that is universally recognizable. I'm going to add an "OK" button below the time input. But I wanted to mention it here, and suggest you implement this in a future release, as it's one of the few missing elements in an otherwise magnificent offering.
Cheers, and thanks.

Hello,
Thank you for the feedback.
User experience has been a key focus for flatpickr from the start.

But when the calendar shows the time inputs via enableTime: true, there is no intuitive next step.

This one I've found hard to get right.

display an icon for time picker? then the time picker can go unnoticed
display an "OK" button? I find it'd disrupt the style of the calendar and look out of place
Launch a time picker after selecting a date? This would be a terrible experience if the user changes mind about a date or time

Hey!
You're asking the right questions. And your less-is-more approach to UI is sound. Here's the style variant I chose, and my thinking for it:

The next/prev month arrows are now blue and bolder.
The time numbers were too small, almost going unnoticed. I enlarged them to 18px, the same size as the month and year. Could benefit from being even bigger. Also expanded the time area vertically.
I found the time difficult to read at a glance. Bringing it closer together helped.
The up/down arrows next to the numbers were small to the point of being useless. Having a larger click-area makes them more usable, especially for mobile. The blue up/down arrows indicate action.
The AM/PM text is blue, indicating it can be clicked to toggle.
The checkmark is better than "OK". No distraction or reading required, no translation required. If you find the big blue button at the bottom too disruptive, it could be a white button with a blue checkmark. But given the hunt-and-peck obstacle a date/time interface represents, I find the finality of clicking that blue button quite satisfying.

Gotta admit that checkmark is pretty sweet. :cake:
Think it should always be displayed, or only when the user modifies the time input?

I'd suggest always displayed, so the moment the interface appears, the user is immediately clear on what is expected of them.
The checkmark and the arrows above are from Font Awesome, which I tend to use wherever possible, but obviously that's too large a dependency for just a few icons. Using Glyphter, here are those 5 icons mapped to the letters ABCDE ...
Flatpickr-font.zip

this will also work when I hide the day select area, to choose month only with this widget. can't wait for this feature.

Please check out the latest changes https://chmln.github.io/flatpickr/#example-datetime
Time input is now hidden initially, and pops out after a date selection - I find that it establishes a rather clear step.
The checkmark looks nice, but it adds another layer at the bottom, making the calendar too tall and thin

Hi guys, just to wanted to add some input on the matter if that's cool :)
I read the issue to be more about what the user does next to confirm their date/time entries.
I don't think having a hidden time input helps, if anything I believe it confuses the matter further and just divides data entry that's being inserted into the same field. It also just takes the user to the already available (when not hidden) "next step" and then once again leaves them not knowing what to do after they have entered their date/time. I believe the "confirmation" part is the "next step" which the OP was trying to refer to.
As a suggestion, which I think will make for a better UX, how about making the time input visible by default again (as with previous versions) and instead, have a checkmark appear once both date and time have been entered? That way, the user is presented with a date/time picker as expected, and then once they've entered a date and a time, they are then presented with a "visual cue for next action", which would be confirming their entries. I think this would make for a much better UX while still retaining the simple and elegant design of the calendar.
Thoughts?

The author doesn't like the OK bar. It adds 10% to the height, which I consider acceptable for the 100% "next step" certainty it gives the user. Hiding the time input just further ambiguates both progression and expectation, moving even further away from what I consider good UI. But this is his creation, and undoubtedly others will appreciate his approach.

@neokio @chmln what about a "slide" between the date and time?
See http://codepen.io/creotip/pen/mPqaGv
Notice how when you click an arrow, it slides to the right.
I'm thinking that when a user selects a date, the UI would "slide" to show the time selector (along with a back button above it). Then we could add the checkmark button without it taking up too much vertical space...

My primary issue with the checkmark row is that the looks are not stellar - wouldn't even hesitate otherwise.
See some examples how this functionality is implemented around the web:

The last two don't look so bad.
I'm going to experiment with various layouts before I make any decisions.

I think the 3rd one down looks quite good with the date and time separated, checkmark at the bottom of both, it also allows for clearer controls on the time input and UI still looks quite refined. Out of curiosity, what datetime picker is that?

I think the 3rd one down looks quite good with the date and time separated, checkmark at the bottom of both, it also allows for clearer controls on the time input and UI still looks quite refined. Out of curiosity, what datetime picker is that?

I dig the looks as well. Its from some sort of a PSD UI kit.

I'm going to experiment with various layouts before I make any decisions.

Here's another concept, with the OK button on the same row as the time. Needs some more work visually, but you get the idea. I've also added a drop shadow which I think flatpickr should have by default.

Ok, ran with my idea and have submitted a pull request for this. Added a bit of extra polish, including appropriate focus/active styling for the ok/tick button.

Just noticed, we may need to implement something similar for multi-date selection. A full-width version of this like what @neokio showed. I may amend my pull request with this.

Added ok button for "range" and "multiple" modes that don't have time enabled. Screenshot...

I like this one! I suggest making it ubiquitous, and adding a showCheck config option (default to true), which, when set to false, provides the current excellent behavior on the calendar-only interface (closing when day is clicked).

Looking good.
My 2 cents:
I think the checkbox should always be on its own line, for date ranges and when using the time picker.
Basically how you had it mocked up in https://github.com/chmln/flatpickr/issues/413#issuecomment-261211717
My main thoughts behind this is

Check is more prominent
Check will be consistent in placement regarding the date picker configuration, which IMO is important. This way if you have multiple date pickers used on your site in different ways, the check is always in the same place and won't "move around" for the user.
Check could support text via checkText option. For example, if I was implementing this for my users, I'd like to change it to "✔  Done", to further guide the users.

Looking good.
My 2 cents:
I think the checkbox should always be on its own line, for date ranges and when using the time picker.
Basically how it was mocked up in #413 (comment)
My main thoughts behind this is
Check is more prominent
Check will be consistent in placement regarding the date picker configuration, which IMO is important. This way if you have multiple date pickers used on your site in different ways, the check is always in the same place and won't "move around" for the user.
Check could support text via checkText option. For example, if I was implementing this for my users, I'd like to change it to ":heavy_check_mark: Done", to further guide the users.
Placing it on the bottom in all use cases will address all these :)

This.
Now here's what's gonna happen:

The checkmark is a go when enableTime: false :+1:

For usability purposes, textual part (localized) will be added i.e. "Done"
I'm also debating whether the checkmark should be on or off by default in these cases, but rather inclined towards the opt-in approach

Aforementioned layout issues. As it stands, the layout of flatpickr is rectangular - narrow and long

this isn't really a problem, but I found it looks much better when closer to a square shape

whether this will be achieved by extra padding or some other means remains to be seen

In case of enableTime: true, docs might recommend using the wrap: true option and implementing an 'OK' button of their own

an example will be provided in documentation

@chmln @jaredatch @neokio Removing the checkbox when enableTime: true seems inconsistent.
I'd argue that time is when the checkbox is MOST useful...
What about like a showConfirm (boolean) option to toggle the checkbox?

@mgibbs189 I agree.
In my opinion, what makes the most sense is:

Only displaying date picker does not display check area, because selecting a date closes the date picker
Enabling the time picker causes the check area to display
Enabling date range causes the check area to do display
showCheck property available to override behavior mentioned above

@mgibbs189 you'll be able to turn on the checkmark in any scenario with something like enableCheckmark: true
I found no way of having both the checkmark and the time displayed that looks good
Its just a matter of figuring out sensible defaults.

@chmln I definitely understand now wanting to change default behavior/design, and if that's the case then perhaps having the check area default to off in all scenarios?
IMO the check area is most helpful when the date picker supports multiple actions and don't automatically close on selection (time enabled or date ranges).

IMO the check area is most helpful when the date picker supports multiple actions and don't automatically close on selection (time enabled or date ranges).

Exactly.
And as I mentioned:

you'll be able to turn on the checkmark in any scenario with something like enableCheckmark: true

Regardless, before a decision is made on this I will introduce the layout improvements first.
Those could also largely negate my initial concern with adding an extra row

@jaredatch Yep, let me know if this sounds right:
enableCheckmark should ALWAYS take precedence. If it's undefined, then by default show the checkmark if:

enableTime: true
mode: range
mode: multiple

@chmln Can't wait to see what you come up with

Maybe a OK/Close/Clear/Today button can be placed over the input itself when the calendar is open, on top of the calendar

Please need a Close button inside DatePicker

@chmln Looking forward to seeing what you choose to do!

@neokio I'm leaning heavily towards a plugin-based approach.
See the confirmDate plugin, which is work-in-progress. And see how plugins work here.
I will likely include options to enable today, clear, maybe other buttons too.
Rather pressed for time right now due to midterms, but with last one being tomorrow I'll be able to deliver this by next week or so.

+1 just to make it more user-friendly on mobile.

https://chmln.github.io/flatpickr/plugins/#confirmdate

Too bad there is no confirmTime plugin available - currently if feels silly for people having to click on the background, even more if you have 10+ time pickers on a page.

Too bad there is no confirmTime plugin available - currently if feels silly for people having to click on the background, even more if you have 10+ time pickers on a page.


M3-6153: Add Databases as a User Permissions Option

Description 📝

Allows unrestricted user to adjust Database related permissions of a user
Adds add_databases and database as user permissions options

Preview 📷

Screenshots
Before

After

How to test 🧪

Test modifying permissions on a user

Specify test Database-related permissions

There is an API bug preventing users with limited database permissions from actually seeing Databases. They are getting a 403 error. This will be fixed in the next API release.


AWS RDS connection string neutralization.

in-follow up with this, can you just make sure IP filtering is still turned on?

It sure is!


Revisit PowerBI lineage

so far, we have created lineage against the database. Take another look at the PBI API and document our findings. We need to end up with a doc explaining what we looked at and what we found. Let's also make sure that we create different datasets, from SQL or DAX and see if we can extract further information in these cases.

conversation link: link

ref:
https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-data-lineage
https://learn.microsoft.com/en-us/powershell/module/microsoftpowerbimgmt.data/?view=powerbi-ps


Contact Us page added

Added Contact Us Page and linked it to navbar
Close #349
https://github.com/codervivek5/VigyBag/assets/133862694/7a5d37df-31f8-4863-b11e-f383d5267789

@codervivek5 @JigarJoshi04 Please merge this.

kindly reduced the size so that it look like pretty...........adjust this page size without

@codervivek5 I have made the changes

can you make ti somthing like this.

means add the basic details in left side

Okay, would work on it


More options to handle having several users

Hi @anderspitman great job on this, love how it has no external dependencies and works smartly.
As I installed this for my whole team to use, one issue that arose was people using existing subdomains, or even port on the server. So I created this fork with lots of ways to be alerted if you are about to override someone's tunnel (or fail to add your own).
It should theoretically be fully backwards compatible as all arguments are optional and defaulting to not being used.
Feel free to merge if you see value in this.
Mat

Hi Mat, thanks for the contribution! Probably won't merge this as one of the core goals of SirTunnel is to keep it very simple and easy to understand and modify for you own needs, which is exactly what you've done. That said, if you don't mind I'd like to add a link to your fork as an example of how to extend SirTunnel for one's needs.
PS - You might be interested in my more advanced tunneling proxy, boringproxy: https://boringproxy.io/

Hi Mat, thanks for the contribution! Probably won't merge this as one of the core goals of SirTunnel is to keep it very simple and easy to understand and modify for you own needs, which is exactly what you've done. That said, if you don't mind I'd like to add a link to your fork as an example of how to extend SirTunnel for one's needs.
PS - You might be interested in my more advanced tunneling proxy, boringproxy: https://boringproxy.io/

Understood; feel free to close this MR then 👍
Will look at boringproxy, thanks
Thanks again for the cool tool here.

Understood; feel free to close this MR then 👍
Will look at boringproxy, thanks
Thanks again for the cool tool here.

Thanks Mat! I added a link to the readme.

Thanks Mat! I added a link to the readme.


Log ruleset changes to stdout

New Feature
If one calls docker-ipv6nat with the -debug flag, every added or removed rule will be logged to stdout.

Fixes #31

I think some changes are missing. This only adds the flag, but no logging yet for added/removed rules.

@robbertkl Yes, I only created the PR. Missing parts will be pushed soon. :smile:

OK, just add a comment when it's ready to be merged.

@robbertkl Wait, I will add some docs for it.

@robbertkl Now it is ready for review.


Build wheels for Python 3.12

Python3.12 is now released and the default choose for users who download python via python.org
I would also highly suggestion merging PR #1145 and #1110 so that building from source is a viable option.

I'm closing this because I fixed this myself in my fork, pyav. You can switch by simply replacing av with pyav in your requirements or setup.py file.
I highly recommend everyone to switch because it's a bad idea to use a library that is not being maintained.

All the necessary PRs are merged. The only step left is make release. @jlaine?

I've tagged v11.0.0, in about 4 hours CI should upload the wheels to PyPI.

It looks like we've hit the dreaded 10GB limit on PyPI. We should ask for an increase then redo the release.
  Project size too large. Limit for project 'av' total size is 10 GB. See
     https://pypi.org/help/#project-size-limit

Yup we should, except I don't own the project, so I can't clean up old releases or reach out to PyPI.
@mikeboers ?

I have tried deleting the wheels of two releases (8.0 and 8.0.1) but I'm still getting the "project too large" error.. Let's hope PyPI support raises the limit.

I deleted even more files and this time the upload went through. We'll be stuck again at the next release though..

Could you please provide wheels for Python 3.12?
There is still Python 3.11 version only https://pypi.org/project/ha-av/#history

Could you please provide wheels for Python 3.12? There is still Python 3.11 version only https://pypi.org/project/ha-av/#history

We don't control that namespace

Could you please provide wheels for Python 3.12? There is still Python 3.11 version only https://pypi.org/project/ha-av/#history

We don't control that namespace

Thanks for explanation, there is URL leading to this project. Maybe it's a fork.

Thanks a lot @WyattBlue and @jlaine for solving this issue! Your work is highly appreciated ❤
I was wondering if you are also planning to update the conda-forge releases of av accordingly. As far as I can tell, the latest version on conda-forge is 11.0. Or perhaps the conda-forge feedstock of av is maintained independently?
Apologies if this is not the right place to ask.


Update - fix batch processing logic to be parallel

Description
This PR updates the batch processing logic to run in parallel rather than sequentially.
Related Issue
Closes #1368

Too many rebases are going on (about 689 files to rebase) after merging main branch into PR branch.


If host unreachable, UI hangs at loading

So my OpenEVSE is being really stubborn about connecting to my Wifi the past couple of days. Not reachable on the network.
I get console output in the terminal I launched nvm run dev from:
8:08:52 AM [vite] http proxy error at :
Error: connect EHOSTUNREACH LANIPHere:80
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
But the UI just looks like it is stuck at 1/3 loaded.
Could we add an error message about this if OpenEVSE cannot be contacted in ~30 seconds or so?

Yep it's undone yet. I'm out for 2 weeks for now ;)
Le dim. 27 nov. 2022, 12:27, D.H @.***> a écrit :

So my OpenEVSE is being really stubborn about connecting to my Wifi the
past couple of days. Not reachable on the network.
I get console output in the terminal I launched nvm run dev from:
8:08:52 AM [vite] http proxy error at :
Error: connect EHOSTUNREACH LANIPHere:80
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
But the UI just looks like it is stuck at 1/3 loaded.
Could we add an error message about this if OpenEVSE cannot be contacted
in ~30 seconds or so?
—
Reply to this email directly, view it on GitHub
https://github.com/KipK/openevse-gui-v2/issues/16, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADXKVMJZKRPBCM3F2RONM3WKN4UXANCNFSM6AAAAAASMSG5HA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


photoEditorDelegate cannot be used in oc project.

please add code @objec(photoEditorDelegate)

Please update to the latest release 0.6 and update me :D


pdflatex: command not found

I'm doing this:
jobs:
  l3build:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v3
      - uses: teatimeguest/setup-texlive-action@v2
      - run: pdflatex --version

I'm getting:
Run pdflatex --version
/home/runner/work/_temp/b360[4](https://github.com/yegor256/iexec/actions/runs/3153250254/jobs/5129497651#step:5:5)3f5-765d-4bba-966c-37db9afa1556.sh: line 1: pdflatex: command not found

What is wrong?

@teatimeguest please, help

Thank you for using this action.
By default, the action only sets up tlmgr and does not install any other packages to fit fot CI use. The pdflatex command is included in the latex-bin package, so you need to install it.
In general, since tlmgr doesn't automatically install dependent packages, you will need to explicitly install many packages that you may not have paid attention to. If you don't know exactly all the packages you need, it is recommended to install scheme-basic, which contains most of the basic packages, including latex-bin and l3build.
- uses: teatimeguest/setup-texlive-action@v2
  with:
    packages: scheme-basic
- run: pdflatex --version # OK
- run: l3build --version  # OK

@teatimeguest for some reason the installation of this package fails: https://github.com/yegor256/iexec/actions/runs/3158944727/jobs/5141559424

Sorry, it seems to be a bug in this action. The action doesn't correctly handle packages with different names in TL and CTAN, such as pgfkeys and shellesc. I'll fix it soon.

@yegor256 I have released a patch version that should resolve the issue. Please rerun your workflow.

@teatimeguest now I'm getting xetex not found: https://github.com/yegor256/iexec/actions/runs/3160212232/jobs/5144398405

You should install xetex package.

@teatimeguest now it works, thanks!


invalid asciimath output leading to errors

Cf. https://github.com/mathjax/MathJax-node/issues/441 and https://github.com/asciimath/asciimathml/issues/106.
Asciimath has a bug creating invalid mathml {cc} leads to invalid MathML (with stray text nodes). This input leads to processing errors; MathJax handles the invalid MathML itself sensibly.

Thanks for working out the details.  I had see that the {cccc} was probably the issue, but hadn't taken time to verify it.


CC-KBC | Provide compilation features for different TEE attesters

Now CC-KBC compiles all the TEE attesters it supports by default, which is redundant. We need to set different features to specify which TEE attester the compiled CC-KBC contains.
cc @fitzthum @Xynnn007

Agreed. Now TDX attester needs underlying tdx libs (.so dynamic libs), which seems unuseful for SNP and other platforms. It seems better to only include one attester in one build of cc-kbc. (which implies that different TEE should be provided different guest image)

Does this mean we want to remove the current TEE detection heuristics (detect_tee_type()), or would be keep that?

Does this mean we want to remove the current TEE detection heuristics (detect_tee_type()), or would be keep that?

Nice catch. I'm in favor of removing that. What's your opinion? @jialez0

Does this mean we want to remove the current TEE detection heuristics (detect_tee_type()), or would be keep that?

@mkulke @Xynnn007 In fact, the feature provided for different attester is for the convenience of users who need to use customized guest. For example, some users need the smallest size guest, and some users use the guest version that cannot support the dependency of installing other TEE. In some general production environments, someone still want to use the general version of CC KBC, automatically detect the platform and select attester.
So I think we should at least retain the ability to build universal AA for multiple platforms.


perf(detect-libc): faster musl check by looking for ldd file

Closes #18
Now, we use by default the comparison of check if ldd file exists.
Performance
Before:
[family] Time Spent 30.49158699810505ms
[isNonGlibcLinux] Time Spent 29.517467997968197ms
[versionSync] Time Spent 26.344385005533695ms

npm run bench:calls

Now:
[family] Time Spent 0.2691209986805916ms
[isNonGlibcLinux] Time Spent 0.1866540014743805ms
[versionSync] Time Spent 31.553612001240253ms

npm run bench:calls

@lovell I don't know if perf is appropriated to describe this change since it could be a breaking change, so let me know if you want me to change to other message.

Could we use this same approach for a potential versionFromFilesystem()? For example, the /usr/bin/ldd file on some glibc-based Linux will contain the string literal "GLIBC X.Y".

In theory, we can:

This is the content of /usr/bin/ldd

We just need to build a faster parser to extract this information.
Do you want to include the change on version in this PR too?

@lovell How did you test linux musl? I'm trying to understand what is the output of cat /usr/bin/ldd on musl

Although we can probably determine the family from the /usr/bin/ldd file on musl-based Linux, we are unlikely to be able to determine the version.
$ docker run -it --rm alpine:3.18 cat /usr/bin/ldd
#!/bin/sh
exec /lib/ld-musl-x86_64.so.1 --list "$@"

Hey @lovell, any updates?

It's good for a release!

v2.0.2 now available, tudo bom, obrigado!


False positive on Windows with .cmd/.bat files

Create a file named "foo.cmd" in the current directory (this also works with .bat):
echo bar > foo.cmd

and then:
require('command-exists').sync('foo') // => true
require('child_process').spawn('foo') // =>  Uncaught Error: spawn foo ENOENT (no such file)

This is a big problem because npm install -g ... uses .cmd files to add commands (including the npm command itself).
The reason the where command on Windows finds foo.cmd is due to the PATHEXT environment variable, which contains a list of file extensions that you can execute without typing the extension, like .exe and .cmd and .bat.
I think the actual problem here is that node can't run these files (they have some docs on this), but for now this is a false positive.

@NotWearingPants , it's not a false positive; require('child_process').spawn('foo',{shell:true}) executes foo.cmd.


Updating package via bosh vendor-package --prefix does not honor prefix on dependent packages

Summary
When you update a package via bosh vendor-package --prefix and the desired package has dependent packages, the dependent packages are not updated with a prefix.
Note
On the first invocation of bosh vendor-package with --prefix, the desired package and its dependent packages will all be vendored with a prefix. This errors only occurs when re-vendoring the package to update it.
Steps to Reproduce
For this specific example, we will use the healthchecker package, which requires the golang-1-linux package to compile the binary. The healthchecker package is intended to be vendored into releases like silk, cf-networking, and garden-runc.
When vendoring another bosh package with a PREFIX that depends one of the golang-*-linux packages, the golang-*-linux will be vendored with prefix (e.g. PREFIX-golang-*-linux).
If I run the following
cd ~/workspace/silk-release
bosh vendor-package healthchecker ~/workspace/healthchecker-release --prefix silk

Then I end up with the following packages:
silk-healthchecker/
silk-golang-1-linux/

Where silk-healthchecker/spec.lock looks something like:
name: silk-healthchecker
fingerprint: 11fec354b909c9d6463e9edd3c92bb7c01423eb0df21c2f7ebe742c5d6f34e28
dependencies:
- silk-golang-1-linux

Running bosh vendor-package --prefix again to update the package
Now, when I want to update the healthchecker package, I see that the silk-golang-1-linux dependency is renamed, removing the prefix entirely!
diff --git a/packages/silk-golang-1-linux/spec.lock b/packages/silk-golang-1-linux/spec.lock
 name: silk-golang-1-linux
-fingerprint: b55bf89806a951e9b3812e987bd526ef931550ab01360f002b38e00d83f8296b
+fingerprint: db9120088b5e3ad5c6f52742a8f1c21a9b234a3b79cf916d48b22660c7ac422e

diff --git a/packages/silk-healthchecker/spec.lock b/packages/silk-healthchecker/spec.lock
 name: silk-healthchecker
-fingerprint: 11fec354b909c9d6463e9edd3c92bb7c01423eb0df21c2f7ebe742c5d6f34e28
+fingerprint: d823a8fec682820aa8e56d115e3d0aa15c309e2120dc183854b80e5e69fb3dcf
 dependencies:
-- silk-golang-1-linux
+- golang-1-linux

Expected Results
When I'm updating the healthchecker package via bosh vendor-package --prefix, only the fingerprints indicating the updated package should change. The names of the dependencies should stay the same:
diff --git a/packages/silk-golang-1-linux/spec.lock b/packages/silk-golang-1-linux/spec.lock
 name: silk-golang-1-linux
-fingerprint: b55bf89806a951e9b3812e987bd526ef931550ab01360f002b38e00d83f8296b
+fingerprint: db9120088b5e3ad5c6f52742a8f1c21a9b234a3b79cf916d48b22660c7ac422e

diff --git a/packages/silk-healthchecker/spec.lock b/packages/silk-healthchecker/spec.lock
 name: silk-healthchecker
-fingerprint: 11fec354b909c9d6463e9edd3c92bb7c01423eb0df21c2f7ebe742c5d6f34e28
+fingerprint: d823a8fec682820aa8e56d115e3d0aa15c309e2120dc183854b80e5e69fb3dcf

Additional Text Output, Screenshots, contextual information (optional)
Adding --prefix to bosh vendor-package: https://github.com/cloudfoundry/bosh-cli/pull/603

i never tested this with a package that also had a dependency.
i will look in to it.

Hey @jrussett, can you try v7.1.3 and see if it fixes the problem?

Hey @jpalermo
I just tested this in our CI after confirming our docker image had the new bosh cli. The BOSH cli was able to successfully vendor the package with a prefix without clobbering the dependencies! ✅
https://github.com/cloudfoundry/garden-runc-release/commit/46efe910f7d3e9a04e4342a5655bed1dee7df1f2
Thank you all!


support ajax spider

Support ajax spider. A config example is added to the long template

Looks good, I don't mind merging. I only have minor comments :

I was thinking of using the config/config-template-long.yaml for pytest whenever possible, for simplicity. But if data is commented, it won't be picked up. Would it be okay to have values (maybe not all, but at least partially) ? That is to say: remove the comment in front of "spiderAjax" and also possibly "browserId"
Is it okay to accept new functions without an associated pytest ?

updated. let's add test cases whenever possible.


[codespell] unsecure -> insecure

Issue #, if available:
Description of changes:

rename unsecure -> insecure

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Previous CI Run
Current CI Run

marisa-trie==1.1.1
marisa-trie==1.2.0

marisa-trie==1.1.1
marisa-trie==1.2.0


Directory missing

https://github.com/simeononsecurity/FireFox-STIG-Script/blob/752b80d13f30dde547885a2f676fc13fe12450f6/sos-firefoxstig.sh#L12
Line 12 of sos-firefoxstig.sh attempts to copy files from a directory that does not exist. The Config directory is not referenced in the script.
It's unclear which file needs to go where when only mozilla.cfg and autoconfig.js are meant for Linux deployments and there are three copy commands.

Resolved


sse channel as celeby backend

I want use Celeby to handle tasks with long processing time
Here I read about backend
http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html#keeping-results
Can I configure this backend to send results to flask-sse channel?
Thanks for any help.

I don't think you can do that. However, you should be able to chain tasks together so that one task receives the return value of another. You can set up a chain so that the the first task returns a result, and the second task takes that result and calls sse.publish() on it, to send the result to the Flask-SSE channel. Would that work?


containers: Add nvidia-driver-cuda-libs to cuda image

commit 78fe3c8f4033dcd104da631d37636df5bb1497b0
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Fri Apr 26 15:52:24 2024 -0400
containers: Add nvidia-driver-cuda-libs to cuda image

This was called out by @stefwalter on #1018. He did that PR and
commented after it merged that this is needed as well.

Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

lgtm


Does Float8Linear support Tensor Parallelism and Sequence Parallelism?

We know that Transformer_Engine has support for FP8 training with data parallel + tensor parallel + sequence parallel, https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/advanced_optimizations.html#Multi-GPU-training
However, when I tried to check with the source code of swap_linear_modules and Float8Linear, and the documentations/discussion of torchao, I can only see the support for FP8 with FSDP (as far as I know).
So, does torchao also has the support for tensor parallelism for FP8Linear?
Thanks!

Hi @zigzagcai , we do support TP and SP implemented via DTensor (https://pytorch.org/docs/stable/distributed.tensor.parallel.html).  We have designed the float8 APIs to be orthogonal to TP/SP, so for the user the workflow would be:

start with high precision model
convert parts of model to float8 (torchao.float8)
define distributed strategy for model (https://pytorch.org/docs/stable/distributed.tensor.parallel.html)

If you are ok with distributed communications to happen in high precision, then (2) and (3) are independent.  If you are interested in doing the all-gathers in low precision, then (2) and (3) interact to coordinate on low precision casting.
Here is an e2e example of (2) and (3) interacting with all-gathers happening in low precision: https://github.com/pytorch/ao/blob/4f1fc4c2d5eace4153c6e62123f5584e772fff4c/test/float8/test_dtensor.py#L206 .  If you were to take that example and replace Float8ColwiseParallel with ColwiseParallel, etc, then you'd get to a point where (2) and (3) are independent.
A full e2e training example of how all of this fits together is https://github.com/pytorch/torchtitan.
Let me keep this issue open to track adding more information to the README about how this works.  Thanks for the question.


fix(linter): fixer for no-debugger creates incorrect code

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

#4184  👈
#4176
main

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

Join @DonIsaac and the rest of your teammates on  Graphite


SYMFONY_CONSTRUCTOR_INJECTION blind spot

SYMFONY_CONSTRUCTOR_INJECTION does not replace occurrences of $this->container->get('my.service');.
Notes

It does work for $this->get('my.service') and even $this->getContainer()->get('my.service').
$container is provided by ContainerAwareTrait.

Closing for lack of feedback. We're narrowing issues to keep focus on active and engaging contributor to keep project growing. Thank you for understanding.
Feel free to re-open with failing test case.


ValidateAction task leaks metaspace in Gradle Daemon when plugin project has any TaskAction class

Steps to Reproduce

Сreate a plugin project with some TransformAction class (or clone the prepared sample: https://github.com/illarionov/playground-android-composite-build/tree/gradle-transformaction-leak)
Launch a monitoring tool to track the metaspace used by Gradle Daemon and the number of loaded classes (eg visualvm).
Run validatePlugins task 50—100 times and watch the metaspace usage:

for i in `seq 1000`; do  ./gradlew :plugin:validatePlugins --no-build-cache --no-configuration-cache --rerun; done

Number of loaded classes and metaspace size is continuously increasing with each new execution of the task. Our TaskAction class, as well as some other classes, are loaded on every run and are never garbage collected. On a project with a large number of classes this can lead to exhaustion of the metaspace.
If you create and analyze a dump, you will see that the isolated worker-loader VisitableURLClassLoader used by the ValidateAction task leaks into the field that is reachable from the static instance of the PropertyValidationAccess class and therefore it cannot be garbage collected:

After 50 executions, field PropertyValidationAccess.INSTANCE.typeSchemes[ArtifactTransformActionScheme].inspectionScheme.metadataStore.cache has 50 copies of the same class loaded by different class loaders and, as it seems, they cannot be unloaded or reused:

Expected behavior
Repeated execution of the validatePlugins task should not increase the usage of the metaspace.
Your Environment
Gradle 8.0.2

Thank you for providing a valid reproducer.
The issue is in the backlog of the relevant team and is prioritized by them.

Hm... 🤔 Thanks for the thorough report. I checked out the example project and have been running:
for i in `seq 1000`; do  ./gradlew :plugin:validatePlugins --no-build-cache --no-configuration-cache --rerun; done

I see some moderate increase of metaspace indeed over time:

And I can see the number of org.gradle.internal.classloader.VisitableURLClassLoader instances rise in the daemon process, too.
This is weird, because ValidateAction is not a task, but a worker API action, and it should execute in a separate daemon process, outside of the main daemon process:
https://github.com/gradle/gradle/blob/cac79ebe509e179e8a45ce0662711a5ae5f16168/subprojects/plugin-development/src/main/java/org/gradle/plugin/devel/tasks/ValidatePlugins.java#L82-L100
It is not clear to me how the classes end up in the main daemon process, or why we get this proliferation of VisitableURLClassLoaders.

Oh, I noticed that the class loader isolation of this task has been changed since version 8.02 in https://github.com/gradle/gradle/pull/23199.
I rechecked this bug with the new version and I can say that it is not reproducible on Gradle 8.1-rc-1.
Increasing in the number of loaded classes is not as significant as on version 8.02 and the metaspace size decreasing with GC cycles.
I think this issue can be closed, sorry for not checking this on newer version initially.

Ah, that explains it. So all is well then. :) 8.1 should be out soonish!


Add community settings page to import posts by CSV

There will be definitely be a big merge process with the comment attachment stuff

Comment attachments merged down to dev. The merge conflicts is there on filpicker.js but I think what didn't conflict is more dicey, but doable. Let me know if you want me to get into this.


fix: fixed incorrect accessors when using userState

Added a fix in component composition example for svelte5 where user state is incorrectly accessed.

Hi,
Please find the working example.


Preview before registering a data resource/other resources

Is your feature request related to a problem? Please describe.
Once a resource is created, if there is something seriously wrong, it cannot be easily deleted. It is better to have a separate preview and approve button before registering any resource.
https://matwerk.datamanager.kit.edu/repo-management.html
Describe the solution you'd like
Preview button that shows all the metadata, also the default values assigned by base-repo before finally publishing.

Do you have any example for something going "seriously wrong"? If there is a typo or missing, optional metadata somewhere, this can be fixed later. Besides of that, I cannot imagine any serious error.
But you are right, removing DataResources is not part of the UI, which is intentional. To remove a DataResource from public access, you may update the DataResource and set its state to "REVOKED", which hides the resource for everybody but the owner and site administrators. Deleting the DataResource is then something that should happen in the backend if this is really desired.

As far as I know there are no default values which are not visible in the form before saving. The only "default values" are used if you add an array element which contains a controlled list represented as combo box (see #15).

if no access data is available, access would be set to anonymousUser. Also I think creators and identifiers are assigned by default when not entered specifically(base-repo)

I see, but these are defaults added by the base-repo to assign default ownership and creator information. Basically, it uses the caller to determine these information. The frontend is not aware of these values.
In any case, one should check whether creating resources without login is something that is desired and I have to check if there is a way for disallow such operations if authentication is enabled.


Model not updating when in source mode

Hi Folks,
I have noticed if the user updates the editor in "source mode" the model doesn't get updated.  Is there a workaround for this?  Our users quite regularly will switch to source mode and press save without switching back to WYSIWYG.
Thanks!
Ash

we solved this issue by getting editor data from ckeditor instance like as follow:
let data = this.ckeditor.instance.getData();
hope this will solve your problem. ;-)

Thanks, I'll see if we can get round the issue with this workaround

@kzimny @AshMcConnell Had the same issue and the fix works just fine. :+1:

@kzimny @AshMcConnell To create a global workaround I tried this and it works for me:
    this.instance.on('key', () => {       setTimeout(() => {         let value = this.instance.getData();         this.updateValue(value);       },0);     });
Just insert this snippet on the bottom of ckeditorInit.


[uss_qualifier] Update tested roles artifact

The "tested roles" (sometimes "tested requirements") artifact was an early attempt at displaying information regarding a test participant's completion of certain sets of requirements.  Since then, we have added defined capabilities and made more conceptual progress toward clearly expressing this information.  This PR entirely reworks the "tested roles" artifact to output a set of HTML files (within a nested folder structure) with one HTML per completed test suite.  This is not what we want for #147, but approaches to some portions of the problem may be similar.
Illustrative output can be found at, e.g., output/tested_roles_uspace/uss1/action1/action0/index.html:

Tested role artifacts are removed from configurations that don't benefit from them, and the role specifications are removed because they are now effectively in the capability definitions.
main.py is adjusted not to write report.json if no test was run and the report was simply read instead.
A naming bug is fixed in reported JSON Paths.

Just a small question regarding the schemas. Were the ones from schemas/monitoring/uss_qualifier/scenarios/documentation removed on purpose? If yes, I would suggest to not generate them or add it to .gitignore to keep git untracked file list clean.

The intent is for all the schemas in schemas to be autogenerated according to whether they are needed to support the top-level data objects (e.g., USSQualifierConfiguration, TestRunReport).  I believe this PR deleted some of the descendant objects causing the mentioned data objects to be no longer generated.  We can probably target which schemas are generated more explicitly, but I think the general approach is still good -- I'm not too worried about descendant object types changing whether they're generated or not because I think they're only useful when supporting a higher level data type of interest.