build: produce a statically linked kraft binary

Prerequisite checklist

[x] Read the contribution guidelines regarding submitting new changes to the project;
[x] Tested your changes against relevant architectures and platforms;
[x] Ran make fmt on your commit series before opening this PR;
[x] Updated relevant documentation.

Description of changes
An attempt to build statically linked kraft binaries.
Currently, kraft links against:
        linux-vdso.so.1 (0x00007ffc0e17d000)
        libssh2.so.1 => /lib/x86_64-linux-gnu/libssh2.so.1 (0x00007f11f1c32000)
        libssl.so.3 => /lib/x86_64-linux-gnu/libssl.so.3 (0x00007f11f1b8d000)
        libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007f11f173c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f11f1537000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f11f151b000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f11f1c80000)

There is however one major caveat of doing this, so it might not be worth it:
$ go build \
        -tags static \
        -gcflags=all='' \
        -ldflags='-s -w -extldflags=-static -X "kraftkit.sh/internal/version.version=v0.5.1-54-g1485ca4-dirty" -X "kraftkit.sh/internal/version.commit=1485ca4" -X "kraftkit.sh/internal/version.buildTime=Wed May  3 12:02:42 CEST 2023"' \
        -o /home/acotten/git/unikraft/kraftkit/dist/kraft \
        /home/acotten/git/unikraft/kraftkit/cmd/kraft
# kraftkit.sh/cmd/kraft
/usr/bin/ld: /tmp/go-link-1213689301/000056.o: in function `pluginOpen':
/_/plugin/plugin_dlopen.go:19: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-1213689301/000059.o: in function `mygetgrouplist':
/_/os/user/getgrouplist_unix.go:15: warning: Using 'getgrouplist' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-1213689301/000058.o: in function `mygetgrgid_r':
/_/os/user/cgo_lookup_cgo.go:45: warning: Using 'getgrgid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-1213689301/000058.o: in function `mygetgrnam_r':
/_/os/user/cgo_lookup_cgo.go:54: warning: Using 'getgrnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-1213689301/000058.o: in function `mygetpwnam_r':
/_/os/user/cgo_lookup_cgo.go:36: warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-1213689301/000058.o: in function `mygetpwuid_r':
/_/os/user/cgo_lookup_cgo.go:27: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-1213689301/000053.o: in function `_cgo_cbcce81e6342_C2func_getaddrinfo':
/tmp/go-build/cgo-gcc-prolog:58: warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libcrypto.a(libcrypto-lib-bio_sock.o): in function `BIO_gethostbyname':
(.text+0x85): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

I see potential for absorbing libssh2 and libssl, maybe. But a fully static executable while using cgo seems impossible considering the limitation mentioned above.
Closing.

Possibly interesting: https://github.com/ebitengine/purego


Mistyped Netron name

In the "Explore Model" section the name of the Netron (a viewer for neural network) is mistyped as Neutron.
[Enter feedback here]

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

ID: b236fa85-23be-f5ec-5c5f-332937187f04
Version Independent ID: 781552b8-a796-a963-05d3-ed98f509dbd4
Content: Convert your PyTorch model to ONNX
Content Source: docs/windows-ml/tutorials/pytorch-convert-model.md
Product: machine-learning
GitHub Login: @QuinnRadich
Microsoft Alias: quradic

Fixed, thanks!


New Route in flask app for Fetal Health Classification

Hey @shubhigupta991 @kritikaparmar-programmer , I want to contribute on this issue as a participant of GSSOC'21. modification in app.py
Please assign it to me 🙏
Thank You...

What type of modification you want to make?

There is already a pretrain Fetal Health model. I just want to use that model in flask app by creating a new route in app.py just like diabetes and cancer route which area there in app.py.
Thank You...

Go ahead @sujoy-coder

Ok... Thnx


Fix license in package.json

Current license value in the package configuration is not valid. When trying to use schemarama through npm the following error message appears when packing a bundle:
ERROR in WebpackLicensePlugin: License "SEE LICENSE IN core/license" for<EMAIL_ADDRESS>is not a valid SPDX expression!

ERROR in WebpackLicensePlugin: could not find file specified in package.json license field of<EMAIL_ADDRESS>
I validated this fix by applying it locally and making sure that this error disappears.

Thanks for noticing this! merged


After running data_pre.py successfully, Should I run the main script  python main.py  or code_graph_gen.py 1?

I was trying to reproduce and run the code in google colab medium with GPU first I could successfully run data_pre.py by:
# python data_pre.py
!python /content/counterfactual-vulnerability-detection/cfexplainer/data_pre.py
#[Errno 2] No such file or directory: '/content/counterfactual-vulnerability-detection/cfexplainer/storage/cache/minimal_datasets/minimal_bigvul_False.pq'
#/content/counterfactual-vulnerability-detection/cfexplainer/data_pre.py:89: DtypeWarning: Columns (1,20,22,23,27,28,29) have mixed types. Specify dtype option on import or set low_memory=False.
#  df = pd.read_csv(utils.external_dir() / filename)
#(6 Workers) Run: 100% 188636/188636 [00:06<00:00, 31120.86it/s]
#(6 Workers) Run: 100% 188636/188636 [00:05<00:00, 32464.01it/s]
#(6 Workers) Run: 100% 188636/188636 [00:46<00:00, 4060.89it/s]
#(6 Workers) Run: 100% 188636/188636 [00:18<00:00, 10477.67it/s]

But when I run code_graph_gen.py 1:
# python code_graph_gen.py 1
!python /content/counterfactual-vulnerability-detection/cfexplainer/code_graph_gen.py 1

I faced the following error:
Streaming output truncated to the last 5000 lines.
	/bin/sh: 1: /content/counterfactual-vulnerability-detection/cfexplainer/storage/external/joern-cli/joern: not found

[11/30/2024 - 02:37:04] File "/content/counterfactual-vulnerability-detection/cfexplainer/helpers/utils.py", line 118

[11/30/2024 - 02:37:04] File "/content/counterfactual-vulnerability-detection/cfexplainer/helpers/joern.py", line 228
	Failed /content/counterfactual-vulnerability-detection/cfexplainer/storage/processed/bigvul/before/155793.c: [Errno 2] No such file or directory: '/content/counterfactual-vulnerability-detection/cfexplainer/storage/processed/bigvul/before/155793.c.edges.json'[11/30/2024 - 02:37:04] File "/content/counterfactual-vulnerability-detection/cfexplainer/helpers/utils.py", line 119
	/bin/sh: 1: /content/counterfactual-vulnerability-detection/cfexplainer/storage/external/joern-cli/joern: not found

But I see the following when ls -lh if joern: not found is the case:
total 3.2G
drwxr-xr-x 5 root root 4.0K Nov 30 02:03 cfexplainer/
-rw-r--r-- 1 root root 244K Nov 30 02:03 Framework.jpg
-rw-r--r-- 1 root root 1.7G Nov 30 02:04 joern-cli.zip
-rwxr-xr-x 1 root root 6.1K Dec  7  2021 joern-install.sh*
-rw-r--r-- 1 root root  12K Nov 30 02:03 LICENSE
-rw-r--r-- 1 root root 1.5G Dec 22  2020 MSR_data_cleaned.zip
-rw-r--r-- 1 root root  12K Nov 30 02:03 README.md

Do you have any idea how to solve it?
After running data_pre.py successfully, Should I run the main script  python main.py  or code_graph_gen.py 1?

Thanks for following our work, and sorry for the late reply.
The issue you encountered with running code_graph_gen.py is likely due to Joern not being installed correctly. Please follow the steps below to install Joern version 1.1.260:
wget https://github.com/joernio/joern/releases/download/v1.1.260/joern-install.sh
chmod +x ./joern-install.sh
printf 'Y\n/bin/joern\ny\n/usr/local/bin\n\n'  | sudo ./joern-install.sh --interactive

Once installed, ensure Joern is correctly set up and accessible by running the joern command in the terminal. After that, please follow the steps in the README and run the scripts in sequence as below:
python data_pre.py
python code_graph_gen.py 1
python code_graph_gen.py 2
python code_graph_gen.py 3
python code_graph_gen.py 4
python code_graph_gen.py 5
python graph_dataset.py train
python graph_dataset.py val
python graph_dataset.py test
python line_extract.py
python main.py --do_train --do_test --gnn_model GCNConv --cuda_id 0
python main.py --do_test --do_explain --gnn_model GCNConv --ipt_method specific_explainer --KM 8 --cuda_id 0

This should help resolve the issues and allow you to run the scripts smoothly.
Additionally, if you encounter issues with generating the code graph, you might find this link helpful: https://drive.google.com/drive/folders/12iUTp4YFRG9qgAtqOV0hXRDpMZmvDp_O?usp=sharing. It contains key data for reproducing the results, including pre-generated code graph data in .pt format.
If the issue persists or if you encounter more problems, please feel free to let me know. I'll continue to monitor and help resolve your issue as much as possible.
Thank you!

@Zhaoyang-Chu  Thanks for your reply I have done everything step by step as it was in README. so Please the notebook (with runtime type: T4 GPU)  and check the problem. As I already mentioned, from my understanding,  jeron  installed correctly I could clearly see it when I checked ls -lh.
✅  I could successfully run python data_pre.py.
❌  The problem is once I started to run python code_graph_gen.py 1. which gives me:
Streaming output truncated to the last 5000 lines.
	/bin/sh: 1: /content/counterfactual-vulnerability-detection/cfexplainer/storage/external/joern-cli/joern: not found

and I solved by because based on the error it should be in the right path:
!unzip joern-cli.zip
!rm joern-cli.zip
!mv joern-cli cfexplainer/storage/external

now I get another error based on your scala code:
Failed /content/counterfactual-vulnerability-detection/cfexplainer/storage/processed/bigvul/before/188528.c: [Errno 2] No such file or directory: '/content/counterfactual-vulnerability-detection/cfexplainer/storage/processed/bigvul/before/188528.c.edges.json'

Please see the notebook  for quick debugging.

Thanks for the update!
To clarify, the Joern tool should be installed using the joern-install.sh script instead of unzipping joern-cli.zip and manually moving it to cfexplainer/storage/external. Please remove the joern-cli from cfexplainer/storage/external as it is unnecessary.
I ran the following commands on your notebook to check the Joern installation:
!ls -al /usr/local/bin/joern*

The results show that Joern is successfully installed (you can double-check by running !joern):
lrwxrwxrwx 1 root root 26 Dec  2 03:40 /usr/local/bin/joern -> /bin/joern/joern-cli/joern
lrwxrwxrwx 1 root root 33 Dec  2 03:40 /usr/local/bin/joern-export -> /bin/joern/joern-cli/joern-export
lrwxrwxrwx 1 root root 31 Dec  2 03:40 /usr/local/bin/joern-flow -> /bin/joern/joern-cli/joern-flow
lrwxrwxrwx 1 root root 32 Dec  2 03:40 /usr/local/bin/joern-parse -> /bin/joern/joern-cli/joern-parse
lrwxrwxrwx 1 root root 31 Dec  2 03:40 /usr/local/bin/joern-scan -> /bin/joern/joern-cli/joern-scan
lrwxrwxrwx 1 root root 32 Dec  2 03:40 /usr/local/bin/joern-stats -> /bin/joern/joern-cli/joern-stats

This installation is enough and does not require manually moving joern-cli. Please remove that extra step.
Additionally, make sure to run all the .py scripts within the cfexplainer directory using cd cfexplainer instead of running !python ./cfexplainer/xxx.py. Also, ensure the SINGSTORAGE path is set correctly with:
cd cfexplainer
export SINGSTORAGE=$(pwd)

As a final kind reminder, it is best to follow the steps given in the README closely in a command line environment to ensure that the program runs correctly.
Let me know if you have any further questions or encounter additional issues!

I made sure about the path using %cd :
%cd cfexplainer
!ls -lh
!export SINGSTORAGE=$(pwd)

and you see I'm on right path:
/content/counterfactual-vulnerability-detection/cfexplainer
total 104K
-rw-r--r-- 1 root root 1.4K Dec  3 00:22 code_graph_gen.py
-rw-r--r-- 1 root root 5.1K Dec  3 00:22 data_pre.py
-rw-r--r-- 1 root root 4.6K Dec  3 00:22 explain.sh
-rw-r--r-- 1 root root  13K Dec  3 00:22 graph_dataset.py
drwxr-xr-x 2 root root 4.0K Dec  3 00:22 helpers
-rw-r--r-- 1 root root 1.1K Dec  3 00:22 hyper_parameter_tuning.sh
-rw-r--r-- 1 root root 2.7K Dec  3 00:22 line_extract.py
-rwxr-xr-x 1 root root  39K Dec  3 00:22 main.py
drwxr-xr-x 2 root root 4.0K Dec  3 00:22 models
-rw-r--r-- 1 root root 5.8K Dec  3 00:22 scripts.sh
drwxr-xr-x 3 root root 4.0K Dec  3 00:22 storage

I doubled check with:
!pwd
#/content/counterfactual-vulnerability-detection/cfexplainer

but when I run !python data_pre.py within the following cell I face the same error logs we discussed
!python data_pre.py           #<=== this runs successfully
!python code_graph_gen.py 1   #<=== error logs starting here
!python code_graph_gen.py 2
!python code_graph_gen.py 3
!python code_graph_gen.py 4
!python code_graph_gen.py 5
!python graph_dataset.py train
!python graph_dataset.py val
!python graph_dataset.py test
!python line_extract.py
!python main.py --do_train --do_test --gnn_model GCNConv --cuda_id 0
!python main.py --do_test --do_explain --gnn_model GCNConv --ipt_method specific_explainer --KM 8 --cuda_id 0

Would you be kind and let me how this step could be done in a shared notebook? feel free to comment on the notebook as well for quick debugging.
Thanks for your assistance.

Thank you for your detailed updates.
Upon reviewing your Colab setup, I noticed that the primary issue seems to be with the Joern installation path. In the Colab environment, Joern is automatically installed in /bin/joern/joern-cli, but for our project, it should be located in /content/counterfactual-vulnerability-detection/cfexplainer/storage/external/joern-cli.
To fix this, I executed the following command:
cp -r /bin/joern/joern-cli /content/counterfactual-vulnerability-detection/cfexplainer/storage/external

Additionally, Colab requires the following code to set the SINGSTORAGE environment variable:
import os
os.environ['SINGSTORAGE'] = os.getcwd()

This is crucial for the successful execution of our programs. You can check if the environment variable is set correctly by running:
!echo $SINGSTORAGE

After these changes, the issue should be resolved, and some generated files can be found in /content/counterfactual-vulnerability-detection/cfexplainer/storage/cache/bigvul/gitdiff (you can rerun !python code_graph_gen.py 1 for double check). I will also update the README with information about the correct Joern installation path.
Furthermore, I highly recommend not running code_graph_gen.py in Colab, as it takes a long time to generate code graphs for each sample in the dataset. If the environment is shut down, you’ll need to redo the graph generation. Instead, I suggest running this step in your local environment.
If you just want to reproduce the GNN-based detection models and explainers in Colab, I recommend downloading the pre-generated code graph data (in .pt format) from the following link: https://drive.google.com/drive/folders/12iUTp4YFRG9qgAtqOV0hXRDpMZmvDp_O?usp=sharing.
Once downloaded, you can proceed directly to run the main.py file with the following commands:
!python main.py --do_train --do_test --gnn_model GCNConv --cuda_id 0
!python main.py --do_test --do_explain --gnn_model GCNConv --ipt_method specific_explainer --KM 8 --cuda_id 0

Make sure to replace specific_explainer with the explainer you’d like to test: gnnexplainer, pgexplainer, subgraphx, gnn_lrp, deeplift, gradcam, or cfexplainer.
Let me know if you encounter any further issues, and I’ll be happy to assist.

Thanks again for your continuous assistance but I have to both approaches, I have tried in the shared notebook unsuccessfully. (please see follow them from the table of contents).

Approach 1: build and train from scratch to reproduce the results
Approach 2: just use pre-trained model to reproduce the results

Even though for 2nd approach I downloaded manually from the browser storage file (since it was not zip file it is not possible to directly download and move using wget and gdown ) and uploaded storage.zip to my own drive to experiment with your short solution.
I would be more than happy if you prepared a solid notebook so that one can reproduce the results and touch your proposed GNN-solutions which is really interesting. You can offer .ipynb at the end which is user-friendly and better to understand the process but still, I'm thankful that you trying to assist me step by step. I'm super interested in understanding and touching this by correctly reproducing the GNN-based model results.

Sorry for the late reply.
Approach 1:
I tested !python code_graph_gen.py 1 on my Ubuntu server, and it successfully produced the graph files. However, running this in your Colab notebook indeed results in some unusual errors. Have you tried running this step on a Linux server instead of Colab? Colab's environment sometimes introduces unexpected issues with file paths or installations.
Approach 2:
The issue you encountered may stem from an incorrect installation of torch_geometric. It's important to install torch_geometric after installing the correct versions of pyg_lib, torch_cluster, torch_scatter, torch_sparse, and torch_spline_conv.
Please follow this command pipeline to ensure proper installation (cu117, cp39, and linux_x86_64 should be adapted to your specific environment and configurations):
pip install https://download.pytorch.org/whl/cu117/torch-2.0.0%2Bcu117-cp39-cp39-linux_x86_64.whl
pip install https://download.pytorch.org/whl/cu117/torchvision-0.15.1%2Bcu117-cp39-cp39-linux_x86_64.whl
pip install https://data.pyg.org/whl/torch-2.0.0%2Bcu117/pyg_lib-0.2.0%2Bpt20cu117-cp39-cp39-linux_x86_64.whl
pip install https://data.pyg.org/whl/torch-2.0.0%2Bcu117/torch_cluster-1.6.1%2Bpt20cu117-cp39-cp39-linux_x86_64.whl
pip install https://data.pyg.org/whl/torch-2.0.0%2Bcu117/torch_scatter-2.1.1%2Bpt20cu117-cp39-cp39-linux_x86_64.whl
pip install https://data.pyg.org/whl/torch-2.0.0%2Bcu117/torch_sparse-0.6.17%2Bpt20cu117-cp39-cp39-linux_x86_64.whl
pip install https://data.pyg.org/whl/torch-2.0.0%2Bcu117/torch_spline_conv-1.2.2%2Bpt20cu117-cp39-cp39-linux_x86_64.whl
pip install torch_geometric

Lastly, thank you for your constructive suggestion about releasing a solid notebook for step-by-step reproduction. I will certainly consider creating and adding such a notebook to the repository when my current schedule allows.
Keep in touch, and good luck with your experiments!


Confusion on CA capabilities

There article appears misleading
It states in one portion:
Currently, only downstream devices with symmetric key authentication can connect through IoT Edge gateways. X.509 certificate authorities and X.509 self-signed certificates are not currently supported.
Then later says
When a device connects to an IoT Edge gateway, the downstream device is the client and the gateway device is the server. Azure IoT Edge allows operators (or users) to build gateway certificate chains however they see fit. The operator may choose to use a public CA certificate, like Baltimore, or use a self-signed (or in-house) root CA certificate. Public CA certificates often have a cost associated with them, so are typically used in production scenarios. Self-signed CA certificates are preferred for development and testing. The transparent gateway setup articles listed in the prerequisites section use self-signed root CA certificates.
I cannot tell what is supported in these cases.

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

ID: 76665258-377d-33f0-2dea-061df101197f
Version Independent ID: 377ef094-b3c3-2597-0cdf-a94dbf7361bc
Content: Connect downstream devices - Azure IoT Edge
Content Source: articles/iot-edge/how-to-connect-downstream-device.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@bearrito Thank you for bringing this to our attention. We are reviewing this and will update the doc based upon content owner feedback.

Hi @bearrito , adding the content author to review your feedback. I believe that there may be a confusion between a leaf device certificate and IoT Edge certificate:

Leaf Device (also known as downstream devices): X509 authentication with IoTEdge not supported. Can only use symmetric key authentication.
IoT Edge acting as a Transparent Gateway:  It will present an IoT Edge hub server certificate that the leaf device must trust. IoT Edge is not doing it the other way around, this is using X509 thumbprint to validate that the leaf device is really who he says it is. Only possibility today, is using symmetric key authentication where you must add the GatewayHostName parameter on to the end of the device's connection string.

See also this doc for more detail - Azure IoT Edge certificate usage detail
Thank you!

Hi @bearrito. Like Antonio was saying, there are two different authentication processes happening when you set up a transparent gateway scenario with IoT Edge. First, the leaf device needs to authenticate with IoT Hub (using symmetric keys). Then, there needs to be trust between the gateway device and the leaf device (using certificate authorities).
Does that answer your question?
I'm going to be updating this document soon, as the product actually released new authentication options in the latest version. While making those updates, I'll work on clarifying the different processes.

Hi @bearrito let us know if this issue can now be closed? Thank you.

As a note, I have made the documentation updates that I mentioned earlier. There's now three different articles to directly address the three different steps: setting up the gateway, creating trust between the gateway and the leaf, and authenticating the leaf to IoT Hub. I hope these changes help!

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Updating the "invalid value" error message to include the list of valid values

Example:
Before:
The ReplicationController "cassandra" is invalid:spec.template.restartPolicy: spec.template.restartPolicy: unsupported value 'Never'

After:
The ReplicationController "cassandra" is invalid:spec.template.restartPolicy: spec.template.restartPolicy: unsupported value 'Never': supported values: Always

cc @bgrant0607 @lavalamp

"The ReplicationController "cassandra" is invalid:spec.template.restartPolicy: spec.template.restartPolicy: unsupported value 'Never': supported values: Always"
Seems redundant. Could it read:
The ReplicationController "cassandra" is invalid because:
  spec.template.restartPolicy: unsupported value 'Never' (supported values: 'Always')

LGTM otherwise, and if that's really hard to change then feel free to ignore.

The change is easy, but I didnt do it since it seemed a bit risky.
We get the field name twice because we prefix the error message with field name here: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubectl/cmd/util/helpers.go#L142.
In this case, the error message already contains the field name.
I am not sure if there are places where we surface the message without the field prefix or that function is called with messages which dont already have the field name.
Hence, I didnt fix that in this PR.
Can make that change post 1.0

Rebased

Fixed tests. Shippable is finally green!

LGTM

@bgrant0607 for second LGTM?

LGTM
ok to merge


Issue with uploaded image url

The image was uploaded successfully into 'public/photos/1/57a8f5aaaf2b3.jpg' through the 'browse server' button , but when I clicked the uploaded image to insert it into ckeditor, the returned url was http://localhost/photos1/57a8f5aaaf2b3.jpg. Looks like a '/' is missing between the 'photos' directory and the user_id directory. Consequently, I cannot insert the image into ckeditor. It works well if I upload the image through the ckeditor "upload" button.
Hopefully someone can help fix the issue. Thanks!

It worked after I removed the following from vendor/unisharp/laravel-filemanager/src/views/script.blade.php
if (path.indexOf(ds) === 0) {
path = path.substring(1);
}

Thanks @bbryan0904. I was facing the same issue and your solution just solved it.

i have same issue...thank you very much @bbryan0904

nice one already fix it, i hope the the developers fix this soon [URGENT]

Thanks @bbryan0904 , this will be fixed in three days.

Updating to 1.6.1 would solve this.

This also worked for me by replacing the code at line 350 (vendor/unisharp/laravel-filemanager/src/views/script.blade.php).
if (path !== ds) {     item_url = item_url + path + ds; } else {     item_url = item_url + ds; }

I doesn't see file "vendor/unisharp/laravel-filemanager/src/views/script.blade.php" in v2.1. How to fix this on v2.1?


Feature_Request : Add Customized Scrollbar to Website

Is your feature request related to a problem? Please describe.

The current scrollbar on our website is basic and doesn't align with the overall design aesthetic of the website.
Describe the solution you'd like

I would like to request the addition of a customized scrollbar for our website. The ideal scrollbar should be visually appealing.

Demo Video/Screenshot (Mandatory )
https://github.com/apu52/Travel_Website/assets/142984776/6678de51-579f-45a1-bb64-440be313acbd
Are you contributing under any open-source program ?

Working under JWoC'24

@ramith-kulal I have assigned you . Made the color gradients of the scrollbar with the similarity of the webpage


wordpress: 4.7.3 -> 4.7.4

See: https://wordpress.org/news/2017/04/wordpress-4-7-4/
It would be nice if this can be cherry picked on release-17.03.

Pushed to 17.03: 1c0a0c027c8cea5ffeea1c074570eff542299acd
Thanks!


Various fixes and improvements

Fix undetected bug
Remove global variables
Use faster print invocations

Closing since we are going to start pulling from another GH project to keep the changes to a single repo.


How to set a custom error with livewire?

Hello,
i am trying to set a custom filter on my mount method with livewire.
my approach
public function mount()
{
 $this->errors = new ViewErrorBag;
 $this->errors->add('customError', 'customMessage');
}

But if i do a dd() in my view, i don't see the error, this might be easy, but i am struggling to get this to work

Seconds after opening this issue, i found out how i get it to work..
using MessageBag instead of ViewErrorBag is working for me


Enable use of shields

Simplify usage of shields within Zephyr by providing an integrated way to configure them
and add them easily to a compatible board, with the minimum dependency (ie: support of matching connector).
Shield configuration and activation
A boards/shields/ directory is created to store the shields ports. For each shield, Kconfig, dts overlay, dts fixup and documentation should be provided ("shield_defconfig" file is not supported)
At shield activation (setting matching config flag to "y"), shield config is added to project configuration and dts.overlay piece is merged with board dts.
Shield support
In order to support a shield, a board should be pin compatible and provide connector support in its dts file. With upcoming dtc v1.4.2, this will be made possible thanks to newly introduced overriding node element, which allows to bind generic adapter with board specific nodes. For instance, in the case of a board supporting Arduino connector and for which Arduino I2C is I2C1, it could be specified as follows in board dts file:
arduino_i2c: i2c1 {};
Since dtc v1.4.2 is not yet supported in Zephyr SDK, a temporary alternate way to enable connector in board dts file is available:
#define arduino_i2c i2c1
	aliases { 		arduino,i2c = &i2c1; 	};
Board nucleo_f429zi has been modified to enable i2c_arduino, as proposed above.
Ported shields
Two similar shields are ported in in this PR order to validate possible usage of multiple (compatible) shields:
-x-nucleo-iks01a1
-x-nucleo-iks01a2
A sample is provided to use x-nucleo-iks01a1.
PR Features:

[x] Enable use of over-rinding nodes [1] for upcoming dtc V1.4.2
[x] Use of multiple shields possible
[x] x-nucleo-iks01a1 and x-nucleo-iks01a2 porting (including doc)
[x] Provide x-nucleo-iks01a1 sample
[x] Update Zephy documentation
[x] nucleo_f429zi arduino I2C suport

[1] https://git.kernel.org/pub/scm/utils/dtc/dtc.git/commit/?h=v1.4.6&id=3346e065aacb1f05bdfb3872e3ba709b5f895846

A minor comment, is this support specific to Arduino in any way?
If not, what about calling this "daughterboards" rather than "shields", as "shield" is a Arduino term for an Arduino daughterboard.

If not, what about calling this "daughterboards" rather than "shields", as "shield" is a Arduino term for an Arduino daughterboard.

Indeed this should not be arduino specific. Though, I find daughterboard a bit long and heavy to use (quite a subjective point). Any alternative? Expansion? mezzanine (if not seen as 96board specific )?

Pushed a new version enabling  treatment of dtc 'overriding nodes'.
They are detected and generated by devicetree.py as 'alt_name' of a node and then treated as aliases in dts_extract_includes.py.
Then I made some changes in dts_extract_includes.py to generate bindings #defines using aliases to get generic references.
This require dtc V1.4.2 (I hacked dts.cmake to use local dtc version)

I'm interested in this PR as I'm working with an Arduino header compatible LTE-M modem.
Adding to the discussion of current terms:
Daughterboard: quite long
Daughtercard: same
Shield: Arduino-specific term for daughterboard.  Agree that this could be confusing as we would be using the term for broader use.
Mezzanine: I don't think this is a 96 boards specific term, however, it does refer to a board that is stacked on top of and parallel to the main board.  Still a good choice in my opinion.
Adding this as an option:
hat (Hardware Attached on Top): Raspberry Pi-related term.  Could cause the same confusion as shield.  Not sure if any of the other prototyping boards have picked this term up.

I had a look to google and it appears "mezzanine" is rather 96boards tainted, even if also used as generic.
What about "expansion"?

We are only doing 1 Kconfig pass per build today and I fear introducing a multi-pass Kconfig would create unwanted complexity.

Understood.
Ok. Then it seems we'll have one limitation, which is unability to provide a shield deconfig file.
This is unfortunate, but I guess we can live with it.
For most of flags this is not an issue, as they can be provided through Kconfig.shield or Kconfig.defconfig.
Only issue is for CONFIG flags generated from a "choice" kconfig directive, as they don't work well in  Kconfig.defconfig files. But maybe this will get better one day.

scripts/extract/globals: treat node alternate names as 'aliases'

Treat new generated dtc element 'alt-name' as usual aliases.
..
For instance, defining following overriding node:
arduino_i2c : i2c1 {};
Will generate following definition:
#define ARDUINO_I2C_LABEL	ST_STM32_I2C_V1_40005400_LABEL

You may just generate
#define ARDUINO_I2C ST_STM32_I2C_V1_40005400
as adding the property part (e.g. LABEL) can easily be done by the driver. That way it is also clear it is an alternate name.

You may just generate

#define ARDUINO_I2C ST_STM32_I2C_V1_40005400

as adding the property part (e.g. LABEL) can easily be done by the driver. That way it is also clear it is an alternate name.

Not sure I get your point. Actually my goal is to leave the driver untouched so both set of definitions could co-exist and be used at same time by different applications.
Anyway, I'll push this alias generation part as a separate PR to ease discussions.

Not sure I get your point. Actually my goal is to leave the driver untouched so both set of definitions could co-exist and be used at same time by different applications

A user may yust do CONCAT(ARDUINO_I2C, _LABEL) to access the label.

Status:
When using dtc v1.4.2, use of shields is now fully functional.
Only limitation is that no defconfig file could be used, but with #6966, all types of CONFIG flags could be set in Kconfig.defconfig files, which makes _defconfig useless (at least in shield specific case).
Remaining work is to document properly and provide a dedicated sample application.

imo shield is just fine.

I think shield is fine as well.

Codecov Report

Merging #6837 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6837   +/-   ##
=======================================
  Coverage   55.66%   55.66%
=======================================
  Files         463      463
  Lines       44622    44622
  Branches     8302     8302
=======================================
  Hits        24839    24839
  Misses      16388    16388
  Partials     3395     3395

Continue to review full report at Codecov.

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

PR is now complete and ready for broad review.
In order to enable use today without dtc v1.4.2 support in Zephyr SDK, an alternate method for
device tree overriding node (which allows merge of board+shield dts) as been provided.

Thanks @dbkinder for the review, I think I addressed all your comments

@avisconti : Might be of some interest for you

@erwango : Thanks. I had some minor comments to the new version, decided to put the feedback in a PR: https://github.com/erwango/zephyr/pull/2

Approved assuming https://github.com/erwango/zephyr/pull/2 is merged

@SebastianBoe : Thanks. I added your commit in the branch

@mike-scott , as potential user, are you ok with current PR?

@erwango I have a working setup using your patches to support the AT&T IoT Starter Kit (LTE-M) cellular shield for K64F.
I realize that for my purposes it's only a marginal improvement.  Other than the UART there aren't any other peripherals exposed by the shield.
With your patches:

I'm able to abstract the UART device label entirely to dts + fixup.dts.
Move the board specific "select xxx" Kconfig settings to boards/shields/avt_wcn14a2a_v1/Kconfig.shield instead of the driver/modems/Kconfig which consolidates all of the driver CONFIG settings under CONFIG_SHIELD_AVT_WCN14A2A_V1

It seems like a good start, that can be improved upon once a solution for DTS-based pinmux / GPIOs becomes available.
NOTE: It will still be tricky as Arduino pin mappings will need to be established per pin across several GPIO ports, but that's a problem for a different day.

@galak , as discussed, added connector compatibility flags.
One minor issue is Error message in case of incompatibility (flag not selected by board):
-- Generating zephyr/include/generated/generated_dts_board.h
Error: nucleo_f429zi.dts.pre.tmp:496.1-6 syntax error
FATAL ERROR: Unable to parse input tree
CMake Error at /local/mcu/zephyr/zephyr-project/cmake/dts.cmake:118 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /local/mcu/zephyr/zephyr-project/cmake/app/boilerplate.cmake:263 (include)
  CMakeLists.txt:1 (include)

This is not quite explicit, but I didn't find a way to get it better. I take any idea to get it more explicit.

@mike-scott , thanks for the feedback, maybe #7151 will be to put this a step further.

@erwango would be great to see what this PR looks like now with some of it's commits merged into master

@mike-scott, rebased. Sadly I missed 1.13 merge window.
Hope we'll get it merged in early 1.14

@erwango no worries.  I will continue to test this as needed. :)

@galak , can we merge this one now?

@galak: rebased vs recent soc changes and removed connector flags as it was introducing CONFIG_ in dts which we're now wanting to avoid.
In case a bord doesn't support matching connector, dtc triggers an error:
-- Generating zephyr/include/generated/generated_dts_board.h
Error: nucleo_f401re.dts.pre.tmp:459.1-13 Label or path arduino_i2c not found
FATAL ERROR: Syntax error parsing input tree

I think this should be explicit enough.


python311Packages.pygls: 1.2.1 -> 1.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pygls is: Pythonic generic implementation of the Language Server Protocol
meta.homepage for python311Packages.pygls is: https://github.com/openlawlibrary/pygls
meta.changelog for python311Packages.pygls is: https://github.com/openlawlibrary/pygls/blob/1.3.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.0 with grep in /nix/store/pqrmmwsdrawsw9lzzxsryscnrzk1d91f-python3.11-pygls-1.3.0
found 1.3.0 in filename of file in /nix/store/pqrmmwsdrawsw9lzzxsryscnrzk1d91f-python3.11-pygls-1.3.0

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

10 package rebuild(s)

First fifty rebuilds by attrpath
bitbake-language-server
cmake-language-server
python311Packages.jedi-language-server
python311Packages.pygls
python312Packages.jedi-language-server
python312Packages.pygls
ruff-lsp
vimPlugins.YouCompleteMe
vscode-extensions.ms-python.python
ycmd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pqrmmwsdrawsw9lzzxsryscnrzk1d91f-python3.11-pygls-1.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.pygls https://github.com/r-ryantm/nixpkgs/archive/d18e809b88a21f38656d469ed32947f727ed9585.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d18e809b88a21f38656d469ed32947f727ed9585#python311Packages.pygls

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pqrmmwsdrawsw9lzzxsryscnrzk1d91f-python3.11-pygls-1.3.0
ls -la /nix/store/pqrmmwsdrawsw9lzzxsryscnrzk1d91f-python3.11-pygls-1.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages marked as broken and skipped:

python312Packages.jedi-language-server
python312Packages.jedi-language-server.dist
python312Packages.pygls
python312Packages.pygls.dist

13 packages built:

bitbake-language-server
bitbake-language-server.dist
cmake-language-server
cmake-language-server.dist
python311Packages.jedi-language-server
python311Packages.jedi-language-server.dist
python311Packages.pygls
python311Packages.pygls.dist
ruff-lsp
ruff-lsp.dist
vimPlugins.YouCompleteMe
vscode-extensions.ms-python.python
ycmd

Maintainer pings
cc @kira-bruneau for testing.

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

4 packages marked as broken and skipped:

python312Packages.jedi-language-server
python312Packages.jedi-language-server.dist
python312Packages.pygls
python312Packages.pygls.dist

13 packages built:

bitbake-language-server
bitbake-language-server.dist
cmake-language-server
cmake-language-server.dist
python311Packages.jedi-language-server
python311Packages.jedi-language-server.dist
python311Packages.pygls
python311Packages.pygls.dist
ruff-lsp
ruff-lsp.dist
vimPlugins.YouCompleteMe
vscode-extensions.ms-python.python
ycmd


[BUG] AzureServiceTokenProvider does not support UserAssignedIdentities

User Assigned Identities are not supported for AzureServiceTokenProvider as documented. https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/key-vault/service-to-service-authentication.md
https://docs.microsoft.com/de-ch/azure/key-vault/service-to-service-authentication
From the documentation the AzureServiceTokenProvider should be called with connection string: RunAs=App;AppId={AppId}
The AzureServiceTokenProviderFactory however requires tenantId and secret/certificate to be specified as well in this case.
I could not find any implementation of a TokenProvider for the case of a User Assigned identity.
To Reproduce
var azureServiceTokenProvider = new AzureServiceTokenProvider("RunAs=App;AppId={AppId}");

Our newer libraries like Azure.Identity can actually alleviate a lot of this hassle. Using DefaultAzureCredential chains multiple authentication models in a way that is optimized for services but allows for development work that should work in your case. Are you able to upgrade to those newer libraries?

Thanks for the quick reply. Azure Identity does seem to support user managed identity.
I will report back once i tried to integrate it with the configuration provider

While it is good to move to the new Azure.Identity libraries, this is supported in App authentication, so do want to close on the original question. @nonik0 , can you please look into this? thanks!

@lukas-gmuer could you provide more information about your scenario, including the specifics of your environment, the error you are seeing, etc.? Using the connection string "RunAs=App;AppId={AppId}" with AzureServiceTokenProvider will enable you to use a user-assigned managed identity. This specifically will use the MsiAccessTokenProvider to get a token for a user-assigned managed identity (however this is technically an implementation detail as you should be using the AzureServiceTokenProvider).

When executing this:
var azureServiceTokenProvider = new AzureServiceTokenProvider("RunAs=App;AppId=XXXXXX-XXXX-XXXX-XXXX-XXXXXXX");
It trhows
System.ArgumentException
HResult=0x80070057
Message=Connection string RunAs=App;AppId=XXXXXX-XXXX-XXXX-XXXX-XXXXXXX is not valid. Must contain 'TenantId' attribute and it must not be empty.
Source=Microsoft.Azure.Services.AppAuthentication
StackTrace:
at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProviderFactory.ValidateAttribute(Dictionary`2 connectionSettings, String attribute, String connectionString)
at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProviderFactory.Create(String connectionString, String azureAdInstance)
at Microsoft.Azure.Services.AppAuthentication.AzureServiceTokenProvider..ctor(String connectionString, String azureAdInstance)
at Zurich.FrontLayer.Web.Program.<>c.b__3_0(HostBuilderContext hostingContext, IConfigurationBuilder config) in

@lukas-gmuer What version of AppAuthentication are you using? Support for user-assigned identities was first added in 1.2.0-preview. Based off the error message shown, it looks like you are using an older version of AppAuthentication.

Closing due to lack of response. If you are still having issues, please reopen this issue with more details and we can investigate.


revert : version of release-it

What

Revert version of release-it to fix release error

Compatibility

[x] Does this change maintain backward compatibility?

:tada: This is included in version v9.5.2 :tada:
The release is available on:

GitHub releases
npm package (@latest dist-tag)


Aimbot not shooting through walls

On Nuke, the aimbot doesn't shoot through the containers, even though the can be shot through, can this be fixed by changing the handleBulletPenetration calculation?

What is your minimum damage?

What is your minimum damage?

My minimum damage is 1. If i just lower the damage reduction when the bullet goes through wall will it break the aimbot on other maps?

Listen, i'm dumb, but not that dumb. Not trying to be rude or anything, but i could really use some help

Container its a prop maybe osiris aimbot dont shoot through prop
Maybe osiris aimbot shoots only through walls
Or osiris dont have that prop

Are you off visible only?

Listen, i'm dumb, but not that dumb. Not trying to be rude or anything, but i could really use some help

Well then start by explaining the steps you have tried to troubleshoot this issue.
what have you done before opening this "issue"?
Since it's not mentioned in the first post, people assume you haven't done anything so it's reasonable to start by answering with the obvious solutions like "min damage" and "visible only" configs.

oh and if you didn't know already... play around with the "anti aim" option ;) @nice0x45

why would u want osiris to aimbot through the walls? Are u using it for legit or what? It's not a rage or hvh cheat to do that(it does, but bad), and I think you have at least some skill to manually kill people through walls.

Looking at this issue in retrospective i agree that this is a bad question, I played against a spinbotter and he always killed me through walls. I was unable to fix it myself so i posted this question here, and i was informed that this is in fact not a bug, but rather a feature.


Refactor UI resources out of main.cpp

Main.cpp is too long and cluttered, and part of the reason is the large arrays of UI structures that are essentially static data defining UI elements.  These and other strictly-UI components should be refactored into separate file(s).

This is now essentially done.  Main.c is down to 563 lines as of 4b9f846, down from 1096 lines in 5a82575.  UI elements have been broken out into separate files based in which Instruction Service Code the UI is for.  Much other stuff has also been removed from main and relocated to topic-relevant files.  Some UX handling still remains in main.c, and will need to be moved elsewhere eventually and cleaned up a bit, but the major overall goal of making main.c easier to understand, follow, and see program flow is, imho, achieved.


Add new Raytac MDBT50Q-DB-33  and MDBT50Q-DB-40 boards.

Adds support for Raytac MDBT50Q-DB-33 and MDBT50Q-DB-40 demo board.
These two boards pull out all the GPIOs of the module and connect them with pins without additional peripherals. It is very convenient for the development of various project programs.

@RaytacStanley you need to change how you work for PRs. If changes are requested, they should go into the original commit that added them in the PR - this PR should have 2 commits, one for each board. You can do this by using the rebase feature of git, see https://docs.zephyrproject.org/latest/contribute/guidelines.html#contribution-workflow for details.
You do not need to merge in changes from main in PRs unless you get a merge conflict in files, and if you get that you do not merge changes in, you need to rebase your branch, fix the conflicts in your commits, then force push.
Please fix this by squashing this PR down to 2 commits (without closing/reopening the issue).

@RaytacStanley you do not need to rebase unless there is a merge conflict

@anangl can you have a review of this please?


Can't build with nlohmann/json installed without -DJSON_MultipleHeaders=ON

Does this issue affect the google-cloud-cpp project? If the problem is with
the Google Cloud service exposed by the google-cloud-cpp libraries instead of
the client libraries themselves, you may consider opening a support request
instead. The google-cloud-cpp developers cannot help you troubleshoot problems
with the service itself.
Yes.
What component of google-cloud-cpp is this related to? For example, is
this related to bigtable (i.e., something in google/cloud/bigtable), or GCS
(i.e., something in google/cloud/storage)?
google/cloud/internal/oauth2_universe_domain.h
Describe the bug A clear and concise description of what the bug is.
https://github.com/googleapis/google-cloud-cpp/blob/f54ba19f2c4e6eaf64a54d09ff29de9bd85c07e5/google/cloud/internal/oauth2_universe_domain.h#L22 uses nlohmann/json_fwd.hpp not  nlohmann/json.hpp but json_fwd.hpp is available only when nlohmann/json is installed with -DJSON_MultipleHeaders=ON.
https://github.com/nlohmann/json?tab=readme-ov-file#integration

You can further use file include/nlohmann/json_fwd.hpp for forward-declarations. The installation of json_fwd.hpp (as part of cmake's install step), can be achieved by setting -DJSON_MultipleHeaders=ON.

nlohmann/json provided by EPEL for RHEL 8 family doesn't provide json_fwd.hpp: https://packages.fedoraproject.org/pkgs/json/json-devel/epel-8.html#files
So we can't use the json-devel package on AlmaLinux 8. Here is an error log in apache/arrow:
https://github.com/ursacomputing/crossbow/actions/runs/9804176444/job/27071504390#step:8:3180
-- stderr output is:
In file included from /root/rpmbuild/BUILD/apache-arrow-17.0.0.dev465/cpp/build/google_cloud_cpp_ep-prefix/src/google_cloud_cpp_ep/google/cloud/internal/oauth2_authorized_user_credentials.cc:16:
/root/rpmbuild/BUILD/apache-arrow-17.0.0.dev465/cpp/build/google_cloud_cpp_ep-prefix/src/google_cloud_cpp_ep/google/cloud/internal/oauth2_universe_domain.h:22:10: fatal error: nlohmann/json_fwd.hpp: No such file or directory
 #include <nlohmann/json_fwd.hpp>
          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

To Reproduce Steps to reproduce the behavior:

Prepare RHEL 8 based distribution such as AlmaLinux 8
Prepare EPEL by sudo dnf install -y epel-release or something
Install nlohmann/json by sudo dnf install -y json-devel
Build
See error

Expected behavior A clear and concise description of what you expected to
happen.
google-cloud-cpp can be built with nlohmann/json installed without -DJSON_MultipleHeaders=ON.
Operating system: If you are using a Linux distribution please include the
name and version of the distribution too.
AlmaLinux 8.
What compiler and version are you using? Please include the output of
g++ -v or clang++ -v or the equivalent command-line flag.
https://github.com/ursacomputing/crossbow/actions/runs/9804176444/job/27071504390#step:8:1579
-- The C compiler identification is GNU 8.5.0
-- The CXX compiler identification is GNU 8.5.0

What version of google-cloud-cpp are you using? Please include the output
from git rev-parse HEAD if you are compiling from source, or the version
number from the applicable google/cloud/*/version.h file.
https://github.com/googleapis/google-cloud-cpp/releases/tag/v2.22.0
Additional context Add any other context about the problem here.
Can we use nlohmann/json.h instead for portability?
diff --git a/google/cloud/internal/oauth2_universe_domain.h b/google/cloud/internal/oauth2_universe_domain.h
index e74e438a0d..ca0fc6aaf8 100644
--- a/google/cloud/internal/oauth2_universe_domain.h
+++ b/google/cloud/internal/oauth2_universe_domain.h
@@ -19,7 +19,7 @@
 #include "google/cloud/status.h"
 #include "google/cloud/status_or.h"
 #include "google/cloud/version.h"
-#include <nlohmann/json_fwd.hpp>
+#include <nlohmann/json.hpp>
 #include <string>

 namespace google {

Thanks for this detailed bug report.  As you probably noticed we merged a PR earlier today.  FWIW, we stopped testing on RHEL 8 (and its brethren, such as AlmaLinux or RockyLinux).  Happy to accept bug reports and suggested fixes like this one.

Thanks!


Added Dyalog APL Language

A language developed by Ken Iverson called "A Programming Language". I have added a link to a PDF of a book written by Bernard Legrand on the Dyalog distribution of the language. Also I have alphabetised the languages list.
:)

Archive the repo if you don't want to maintain it any more @vic317yeh


netns issue

There are some below steps to lead to this issue.

there is no any CNI plugin in kubernetes
I create a vmpod by using "kubectl create -f xx.yaml". the vmpod is containercreating forever because of no CNI.
I create a podid netns using "ip netns add "
I can see the error from virtlet logs. "ip netns add " failed with output: Cannot create namespace file "/var/run/netns/": File exists""
I recover CNI plugin. either weave or flannel.
the vmpod is not running forever.

That's because Virtlet supports only CNI based configuration. Also manual adding netns for pod misleads Virtlet leading to another erroneous situation.
If there is no CNI plugin (p. 1), how you are recovering weave or flannel (p. 5)?

at the beginning, I do not create CNI plugin, and manually create netns using "ip netns add ", then I can get the error "netns File exists". at the last, I create CNI plugin using "kubectl apply -f weave-net.yaml", the vmpod do not become "running".
I know this situation is very abnormal.
I looked at the code flow in RunPodSandbox function by invoking TapFDSource.GetFDs(137 line, tapFDSource file),  if netns create failure, directly return error. but if the error is "the netns have been exist", the netns will not be deleted. then the error is again and again. Of course I know, it is not abnormal to create netns manually.


2024.03.00 Release

Preparing for first release.

LGTM. Do we want to add in PR 21 before release?

Good idea, it should be easy to merge soon


why your article can not see？

ok I see it on
http://catalin.me/role-based-authentication-with-angular-express-jwt-mysql-part-1/

Not sure what the problem is, can you please clarify?

your README.md  ，some link ，I can not open


Regression in v0.9: entrypoint binary is not on PATH

ko v0.8.0:
$ crane config $(go run ./ publish ./test) | jq .config.Env
[
  "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/ko-app",
  "SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt",
  "KO_DATA_PATH=/var/run/ko"
]

ko v0.9.1:
$ crane config $(go run ./ publish ./test) | jq .config.Env
[
  "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/ko-app/test",
  "SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt",
  "KO_DATA_PATH=/var/run/ko"
]

This is likely caused by changes to PATH to support Windows.
This change in behavior causes users that call ko-built images with the binary name as the command, without /ko-app/ prefix, to fail.
This probably warrants a v0.9.2.

Yep: https://github.com/google/ko/pull/374/files#diff-ec8e4ed8cdc5703f7558043358223fb0cd6656105f78be8d576ec0f7b5362217R461
https://github.com/google/ko/blob/5a8663b58dfeb5db05df0a10496bd618e52d51fd/pkg/build/gobuild_test.go#L539
This should be /ko-app/, not /ko-app/test.


Plans for searching for 4 or 5 bytes or for u16?

This isn't quite a feature request at this time, just a question at this point:
Is providing memchr4 considered to be within scope for this crate? What about analogs of the byte searching functions that search up to 4 u16 values in a &[u16]?
(Context: Escaping a string according to HTML.)
What about up to 5? (Context: the Data state of the HTML parsing algorithm taking into account CR and LF for end-of-line handling.)

I've thought a little about this, and I actually don't know. There is certainly going to be a crossover point at which the pcmpeq style algorithm used in this crate isn't faster than either a naive version or even one built on pcmpestri. But even so, we could treat that as an implementation detail and expose routines for it. The pcmpestri style algorithm would permit searching up to 16 bytes at a time. So we really want memchr1, memchr2, ..., memchr16? Or do we want to tweak the public API after memchr3 to avoid having a different function for each arity?
When I initially set out on my rewrite of this crate, I was planning on adding a memchr style function that could search for occurrences of any of a collection of 16 bytes or fewer. But I ran out of bandwidth to do it, and the API wasn't obvious to me. So I resigned to avoid adding that until there was a more concrete use case for it.
Another crate in this space is jetscii, which uses pcmpestri internally IIRC.
My feeling is that APIs for u16 are probably out of scope, but pcmpestri does technically support that. I honestly don't know how best to draw the crate boundaries here.


Login required for the logged in user

Hi, @muthu-kc
I've followed your sample project and successfully implemented the checkpoint feature.
Right now I can use most of the functions without any issue with the logged in instagram user instance.
Btw, I have some problems though.
When I call $instagram->followUser('111...'); , it says me "login required". This issue is happening on the commentOnMedia(), likeMedia() functions, too.
FYI, getUserInfo(), getMediaComments(), getUserByUsername() functions are working well though.
Could you let me know why this issue is happening, please?
Thanks in advance.

I think it's because of too many write actions performed from same IP address. try to use proxies for every account. use intervals in order to avoid getting caught.

Thanks for your quick response. @muthu-kc
I will try to follow your solution now, and let you know the result.
FYI, I am using proxies for now. I will try to use another IP address.
Really appreciate your help as always.

Hi, @muthu-kc
I just tried to use another IP address for the same account.
I've passed the checkpoint step successfully.
But, the same issue is happening on the new IP address, unfortunately.
It seems like this issue is not related with proxy.
I'd much appreciate if you can give me some more clue.
Thanks.

I think on mgp25 they used some tricks to avoid this issue. if you can look
into mpg25, then you can figure out.
On Thu, Jun 28, 2018 at 12:45 PM, Flow999Cloud<EMAIL_ADDRESS>wrote:

Hi, @muthu-kc https://github.com/muthu-kc
I just tried to use another IP address for the same account.
I've passed the checkpoint step successfully.
But, the same issue is happening on the new IP address, unfortunately.
It seems like this issue is not related with proxy.
I'd much appreciate if you can give me some more clue.
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/muthu-kc/php-instagram-private-api-with-checkpoint-feature/issues/5#issuecomment-400936219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHjnGH8kL2b_7cvj1UovLTopPxlnk3u8ks5uBIKEgaJpZM4U60Cd
.

@muthu-kc  Thanks for your answer
Could you let me know which part should I look at on mgp25, please?

I can't specify exact part, they do a lot of activities on the login process. for example, they use some kind pre-request to the server and they check feed after login. They do similar kind of activities.

Thanks, @muthu-kc
I will try to find a solution to fix the current issue.


Editor - multi tabbed view

Hi,
Working on multiple files parallel is a common use case.
We could open each file in a new tab.
Cheers,
Imre

Since the last editor (Version 6) no longer requires the user to save a file before switching to another one, I don't think this feature request makes sense anymore.
@nagim do you agree?

Thanks for following up @SamyPesse.
It can be closed now. The editor performance became much better so it's not that big deal jumping between the files.


Add run os install on node per index

@RackHD/corecommitters @hohene @johren @tannoa2 @geoff-reid

This code is tested in jenkins Sandbox under Regression-vagrant where rackHD is connected to 8 compute nodes of baremetal Quantat41.
this PR will help running different tests concurrently against one instance of rackhd.

BUILD RackHD #54 : FAILURE

BUILD RackHD #62 : FAILURE

test this please

:+0 for this good idea!

BUILD RackHD #63 : FAILURE

@keedya : Could you please detail how to use this feature? Run multiple CIT instances in RackHD host environment's multiple shell? If so, I believe there should be a Jenkins pipeline change, but I don't find it.

@yyscamper the pipeline is not part of my task. The plan is to run multiple instance of the test with different NODE_INDEX. There is a job as I mentioned earlier in the sandbox(I posted a snapshot in this PR )
I know @panpan0000 team is been working on the pipeline scripts and they are more expert in this field and they probably can help me convert the job in jenkins to pipeline.
I will deploy the job from jenkins Sandbox to production once this PR is merged
Finally there reason behind this PR is to run all flavors of supported OSs on baremetal in parallel and reduce the job time to 1 hour. This can be so beneficial to our release pipeline

BUILD RackHD #81 : FAILURE

BUILD RackHD #80 : FAILURE


Pixels getting skipped

In ipython, the following command
In [1]: from isofit.core.isofit import Isofit
In [2]: Isofit("config/config_file.yaml", row_column = "670, 740, 25, 60", level = 'DEBUG', logfile = './ipython_debug_output_2.txt').run()

appears to drop pixels from the retrieval. Grepping the log file for how many lines were processed with
$ grep Row ipython_debug_output_2.txt | wc
   1367    5468   32808

indicates that 33 pixels were not processed (70*35 = 1400, not 1367). The output state file contains zeros for the pixels that were apparently not processed. (See the blue speckles in the image.)

This issue is not exactly reproducible. Repeated runs may have a different number of pixels that are not processed and the location of those pixels can vary.
I don't seem to have the issue when running from the bash command line calling python directly (without ipython), so this is not a pressing issue.
My best guess is that somehow ray and ipython don't like each other.

Update:
One pixel with a zero is 713, 51. The following command
$ grep Row ipython_debug_output_2.txt | grep 713 | sort
DEBUG:Row 713 Column 25
DEBUG:Row 713 Column 26
DEBUG:Row 713 Column 27
DEBUG:Row 713 Column 28
DEBUG:Row 713 Column 29
DEBUG:Row 713 Column 30
DEBUG:Row 713 Column 31
DEBUG:Row 713 Column 32
DEBUG:Row 713 Column 33
DEBUG:Row 713 Column 34
DEBUG:Row 713 Column 35
DEBUG:Row 713 Column 36
DEBUG:Row 713 Column 37
DEBUG:Row 713 Column 38
DEBUG:Row 713 Column 51
DEBUG:Row 713 Column 52
DEBUG:Row 713 Column 53
DEBUG:Row 713 Column 54
DEBUG:Row 713 Column 55
DEBUG:Row 713 Column 56
DEBUG:Row 713 Column 57
DEBUG:Row 713 Column 58
DEBUG:Row 713 Column 59

shows that a bunch of columns were skipped, but that 51 was processed. I don't understand what's happening.

Hi Jay,
Does the image you're displaying correspond with the debug output shown above?  I do not see a blank pixel at (713, 51) [row, column].

I thought it did, I'm confused now. I'm rerunning to make sure.

Many of my previous statements are incorrect. The problem just occurred running the current master from bash (using python, not ipython) and the number of lines in the log doesn't seem to be relevant. In this case, the wc command shown above yields 2450 lines, which is 50 too many.
Here's a new picture showing the different pixels:

I'm going to try to find a work around for now until I can tie this down a bit more.

Alright, this tells us the code is at least trying each pixel, but not that each pixel succeeds.  If possible, to help isolate the problem, it would be great to modify the log at:
https://github.com/isofit/isofit/blob/master/isofit/core/isofit.py#L169-L172
to report results for every pixel (remove the modulus reporting check), and to print the row, column pair instead of the index.  This will help tell us isolate if the inversion is actually being completed at each pixel, or if for some reason occasional inversion instances die for some reason (unlikely, but I'd like to rule it out).

@jfahlen , checking in on the state of this - I believe based on personal communication that this was determined to be a system-specific issue that was resolved.  Can you confirm?

I think this is system specific, but I do not know the specific cause and I have no fix for it yet.

Current updates have better error reporting for any pixel that gets zero'd out.  Between that and ray updates, hopefully this is mitigated.  If it pops up again, please report!


fix: don't import docsearch css for server build

Types of changes

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

Description
See https://github.com/nuxt/framework/issues/6813.
These lines:
https://github.com/nuxt-community/algolia-module/blob/449fceac98378c00f03f5ff92589a466ed83d356/src/runtime/components/AlgoliaDocSearch.vue#L63-L69
are transformed in the server build to
      const docsearch = await Promise.all([
        import(
          /* webpackChunkName: "docsearch" */
          "./_nuxt/index.d1f4b1da.js"
        ),
        import(
          /* webpackChunkName: "docsearch" */
          "./_nuxt/style.1f98b5b0.js"
        )
      ]).then(([docsearch2]) => docsearch2.default);

... but the css import (the second one) is not emitted in the server build.
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes (if not applicable, please state why)

Thanks, @danielroe for this.
It will be indeed useful! Feel free to merge or give me a sign so I will merge it 😄

Go for it.


What has 2020 brought to us

My attempt on the first post announcing changes which happened on Codewars.
I was not sure how much details to put here, so I decided to have just a summary, and a couple of follow-up posts published separately with more details on some topics. Please let me know how it works for you.

Can you remove build/zola.exe?

Uh, I thought I have, but apparently not.

Can you remove build/zola.exe?

Uh, I thought I have, but apparently not.

You need to first pull the changes from upstream (this repo) into your fork. I usually do:
git checkout main
git pull upstream main
git push # update the fork on GitHub
git checkout a-branch-name
git rebase main # this will make your changes on top of the updated main
git push --force-with-lease # update the branch for PR

I prefer using rebase for feature branches because the history is cleaner, but you can use merge too.

You need to first pull the changes from upstream (this repo) into your fork. I usually do:
git checkout main
git pull upstream main
git push # update the fork on GitHub
git checkout a-branch-name
git rebase main # this will make your changes on top of the updated main
git push --force-with-lease # update the branch for PR

I prefer using rebase for feature branches because the history is cleaner, but you can use merge too.

If you haven't set the upstream, then you need to do that first:
git remote set upstream git@github.com:codewars/blog.git

If you haven't set the upstream, then you need to do that first:
git remote set upstream git@github.com:codewars/blog.git


[FLINK-30880] Update flink version to 1.16.1

Superseded by https://github.com/apache/flink-connector-kafka/pull/4/commits/0c1b2e5309c29425437dbad557bdcf2643a28039


Download maps and trees as .png as well as .svg

How much work is this?

There are Python libraries that can do this (e.g., http://cairosvg.org/), so I guess it could be easy enough.

Eh, probably not worth the effort for now.

wontfix.


Draft: Added a folding section to cleanup logs.

Just playing around with folding of logs.

Dumb!


Add basic bouyancy

Taking some poorly educated guesses on how to add bouyancy

My apologies. I meant to raise this PR against my own fork, sorry to bother you. Working on #6 on my own fork, it's not very good but does check at least 1 displacement map:
https://github.com/jonandrewdavis/GodotOceanWaves/pull/1


WorldWind needs to be updated to be able to handle useProxy when necessary

WorldWind placemarks are currently set to be used in their raw value. The useProxy property is not being used.

test case:
use branch 97
Plot a primitive point with the following UR (no CORS enabled) :
https://www.jpl.nasa.gov/spaceimages/images/wallpaper/PIA20878-640x350.jpg
set to use proxy. The test is a success if the image renders on the map.
set to not use proxy. The test is a success if the image fails to render on the map. It is expected to themap to fail to render because the server the image comes from has no CORS enabled.

Unrelated to this issue of point and proxy, I also added support for WMS and proxy in branch 97. You need geoserver in a separate tomcat to simulate the use of extenal WMS services requiringa proxy.

test case :
Use branch feature/emp3-web#97-ww-proxy
.Use following URL that comes from a server that is not CORS enable:
https://www.jpl.nasa.gov/spaceimages/images/wallpaper/PIA20878-640x350.jpg

Try again the test case. Use branch feature/emp3-web#97-ww-proxy.
https://www.jpl.nasa.gov/spaceimages/images/wallpaper/PIA20878-640x350.jpg


Update dependency in documentation

The current version on Maven central (that the badge in the README references) is for io.verizon.journal#core_2.11;2.3.15, but the documentation site still says to look for oncue.journal on bintray.

Ah I see where to change this. PR incoming.


[Model] Allow loading from original Mistral format

Mistral models are usually uploaded in two formats:

The original consolidated format:
consolidated.safetensors
params.json

A bit later the HF format is usually also uploaded:
model-00001-of-00003.safetensors
config.json

This PR allows to load directly from the original consolidated format which should make it easier to directly get new models working in VLLM.
The PR can be tested with:
vllm serve mistralai/Mistral-Nemo-Instruct-2407 --tokenizer_mode mistral --max_model_len 8192 --load_format consolidated

or:
from vllm import LLM, SamplingParams

prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]
sampling_params = SamplingParams(temperature=0.8, top_p=0.95, seed=0)

model_path = "mistralai/Mistral-7B-Instruct-v0.3"
for model in [model_path]:  # or "mistralai/Mistral-7B-Instruct-v0.3"
    llm = LLM(model=model, tokenizer_mode="mistral", max_model_len=8192, load_format="consolidated")
    outputs = llm.generate(prompts, sampling_params)

    for output in outputs:
        prompt = output.prompt
        generated_text = output.outputs[0].text
        print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}"

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

/ready

I think this is reasonable overall but are these consolidated checkpoints going to be actively used going forward? We tend to want to conform to HF as a standard, so if these checkpoints don't load in transformers now then I think the community will continue to have interest in having those be converted to canonical "HF-style" checkpoints

Hey @mgoin,
Yes at Mistral we're usually actually only releasing the consolidated checkpoints to begin with (see table here). The community then often converts the models to transformers but this takes usually some time and then it takes even more time to wait for the next transformers release.
I understand that it's easier to just conform to HF-style, but I guess VLLM also has GGUF support and it could make sense to start allowing more and more support for other formats?
The biggest reason why I think it makes sense to allow also for the consolidated format is so that users could have day-0 inference support for Mistral models for future model releases. VLLM is essentially implementing all the model architectures natively in the model register, so it's just about "correctly" loading the file format no? Guess in the future VLLM can run any nn.Module regardless of whether it's in transformers or not no? It's a bit painful to have to adapt mistral format to transformers format to allow inference in VLLM

Thanks for the feedback @timlacroix @mgoin - think everything should be incorporated.  Let me know if there is anything else that should be changed!

Thanks for working on getting the CI green, looks like you're close. It does seem like AUTO is causing trouble here, so I would be okay with removing it and defaulting to HF if you can't get it stable. Otherwise this LGTM so we can land when green

Yeah I think it should be fine now - added one is_gguf statement that fixes everything I believe :-)

will this work for pixtral as well?

Will this work for the Llama original formats which are in the formats of consolidated.00.pth and params.json?


Dependency on guava

Thanks a lot for the library.
Surprisingly there aren't many java CLI libraries designed for usage for commands with parameters. IMHO this is the best one.
The only disadvantage I found is dependency on guava:

for tiny projects it fills wrong to add 2Mb guava jar just for CLI
"enterprise" projects will usually have dependency on guava already, but not necessarily the same version as airline

Do you think it makes sense to copy into project only those guava bits which are used?
I could do this myself, just wanted to ask your opinion.

Hi,
I tried out your library and I think it is very smart. I need it also to support various commands in combination with parameters/arguments.
I just tried to get rid off guava and the most of it can be replaced with methods of the JDK or a few, small, simple util methods. I think it is also not notable less efficient. There are some lambda-style functional method usages remaining which could get replaced with Lambdas of Java 8. What is your plan to upgrade to Java 8?

I think it would be good to replace guava with an upgrade to Java 8. The upgrade to Java 8 is definitely useful in the future (Java 7 will reach end of life). The point in time is just unclear, regarding the airline library. :-)
Here an example of a replacement of guava with Lambdas of Java 8. I'm just preparing a patch without guava.
Before (guava):
options = CollectionUtils.asList(transform(metadataIndex.values(), new Function<Collection, OptionMetadata>()
{
@Override
public OptionMetadata apply(@Nullable Collection options) {
return new OptionMetadata(options);
}
}));
After (Java 8, Lambda);
options = metadataIndex.values().stream().map(OptionMetadata::new).collect(Collectors.toList());

We've started migrating other airlift-related projects to Java 8 already, but haven't got to this one, yet. We're moving in that direction, though, so thanks for working on that patch.

Ok, sounds good. I have now created a fork/branch which is working with Java 8 and without guava. The fork can be found here: https://github.com/Novanic/airline
I would be happy, when it could get integrated/pushed to the master. :-) There is one optimization/refactoring within the Parser class left. There is still a very intransparent iterator handling within this class. I try to get this optimized tomorrow or by next week.


This does uninstall the driver completely, after reboot the appears again in device manager

[Enter feedback here]

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

ID: 963a0877-81d6-57b1-2922-459c9077c76c
Version Independent ID: 49998df1-e7fd-6ce7-eb49-aa9c37f13cd8
Content: Using Device Manager to Uninstall Devices and Driver Packages - Windows drivers
Content Source: windows-driver-docs-pr/install/using-device-manager-to-uninstall-devices-and-driver-packages.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

@vignura . it Does not appear after reboot. Because I have tested this method many times in different configurations computers
if you not select sottware of this device, then driver will be installed again after reboot too.

Thanks for the feedback, @vignura.  Did you select the Delete the driver software for this device option?  If so, and this is still an issue, you might check in on the forums to see if anyone there can offer a recommendation.

Windows Hardware WDK and Driver Development
OSR's ntdev List

Thanks for the feedback, @vignura.  Did you select the Delete the driver software for this device option?  If so, and this is still an issue, you might check in on the forums to see if anyone there can offer a recommendation.

Windows Hardware WDK and Driver Development
OSR's ntdev List


Improve event validation and option filtering for training progress and instructor badge awarding

Fixes #2342, fixes #2343 :

when awarding instructor badge, auto-fill badge and event selection where possible. Where multiple passed Trainings exist for a trainee, filter event field options to only include those events (though this generally shouldn't happen as only one passed Training should exist)
when creating a training progress, filter event field options to include only events where the selected trainee has a learner task
when validating training progress, ensure that

trainee has a learner task for the chosen event
trainee does not already have a progress for the chosen event

when adding training progress in bulk, if there are some failures due to the above validation, create all progresses that can be created. Instead of the usual success message, show the errors and info about how many trainee progresses were created/skipped (screenshot).
start some documentation for where we use design patterns that might be useful elsewhere (motivated by how it took me a while to realise the community role creation view had the dynamic behaviour I was looking for)

I'm bumping this to the 4.3 milestone for time reasons. There's some more work needed here to address Piotr's review comments, and it's only a convenient extra to the checkout project rather than anything essential.

@pbanaszkiewicz I finally got around to addressing your comments on this PR. Ready for a re-review!


Bump env_logger from "0.10.2" to "0.11.3"

Hi. Normally we don't do merge commits here. Can you please rebase?


Create additional info blocks

You can make your resume less official by adding more entertaining info, like your hobbies and interest, or what do you like, some interactive content or joke, easter egg, etc.

I have cultivated numerous hobbies since my school days, some of which have persisted while others have evolved into different interests. Mathematics has always captivated me, and I actively participated in competitions. However, I am not among those prodigies who devise their own theorems or make groundbreaking discoveries. My achievements in mathematics are largely a result of relentless practice and tackling conventional problem-solving.
Engaging in sports has been a consistent part of my life for as long as I can remember. I participated in athletics and football during my school and college years, taking part in various competitions. Presently, I occasionally play table tennis and maintain a fitness routine at the gym.
My love for nature and the mountains drives me to embark on camping adventures, setting up tents along riverbanks. Recently, I have delved into the realm of fantasy literature and have developed an interest in books centered around self-development, motivation, and personal growth.
Being an avid Marvel fan, I find great enjoyment in their captivating stories and characters. Moreover, I cherish meaningful communication and aspire to attain a level of fluency in English that allows me to express myself with the same ease as my native language.


请问您的configs文件下面的yaml文件是通过哪一个文件代码生成的

The yaml files are created by ourselves.
Please note that our codebase is adapted from nnUNet, but re-organize a lot.
Best,
Jieneng


Update release team in accordance with

This PR updates the release team members to reflect the team chosen for the 1.4 release as per https://github.com/kubeflow/community/issues/517.
/cc @kimwnasptd @RFMVasconcelos @Bobgy
Also /cc @yanniszark, as you still might require these permissions for 1.3.1. If that is the case, we can merge this after the 1.3.1 release or include you up until that release.

Thank you for actioning this @DavidSpek!
/lgtm

Thank you for the PR @DavidSpek!
I'd suggest to put a pause to this PR for now. I would like to first create the PR for the release handbook to ensure that we have documented what are the necessary roles and permissions.

/lgtm
/approve

Sorry I missed Kimonas' comment, but I think the change doesn't hurt.

I don't think this merge will cause issues. If needed for the 1.3.1 release we can always add @yanniszark again.


Caret looks weird on Firefox 48

Steps to reproduce:

Open http://codemirror.net/ on Firefox 48
Click inside the demo codemirror code area
(you might need to wait a little bit for the cursor to blink a few times, not sure about that step)
The cursor gets a 2 or 3px rectangle next to it that blinks too.

Using devtools, I saw that codemirror used a textarea where the cursor is (I guess to receive text inputs), and that what we see in the screen capture above is the textarea.
On Mac, it's a little more of a problem, because the default focus style is a thick blue outline, so it makes the problem more visible:

The above screen capture was taken in Firefox DevTools, where codemirror is used.
Adding border:none to the textarea helps a little (at least on windows), but you can still see the second caret (the one in the textarea) blink next to the codemirror one.

Are you sure that what you're seeing is the textarea? That definitely shouldn't blink (the CSS changes that cause the cursor blinking are applied to a completely different element), so I can't explain why the box in your videos is blinking along with the cursor.

Also, since 48 is not even beta yet, maybe file a report with Firefox about this first, and see if they fix it? If they've made focused textareas un-hideable, that's not something we're going to be able to work around.

Closing as this is indeed a Firefox 48 issue. Sorry for the noise.
https://bugzilla.mozilla.org/show_bug.cgi?id=1276467

Thanks for finding the corresponding Firefox issue. Let's see if it gets fixed.

opacity: 0 fix it


A working Modal project?

There is not enough documentation here to actually build a working ng2-bootstrap Modal and there is no example project here either. I've been trying to find a working ng2-bootstrap Modal example for quite a while with zero to very little success. Found a couple things on SO, but of course the code is never complete  there and most of the time the plunkers don't work. Is there a working plunker you can point me to? Thank you! :-)

Have you tried http://valor-software.com/ng2-bootstrap/#/ ?

http://valor-software.com/ngx-bootstrap/#/modals
There you'll find everything you need to start working with modals.


How do you refresh an icon set

I added some icons to my icon set (I use Fontello). Unfortunately, Fontello, always changes all the references with each download. And now I'm looking at all sorts of mis renders. It seems some kind of caching issue. Any suggestions on how to refresh it?
So far I tried:
rm -rf ~/Library/Developer/Xcode/DerivedData/*
cd $TMPDIR
rm react-packager-cache-*

Try cleaning the build folder in Xcode, cmd-alt-shift-K.

Sorry, forgot to update the config.json

Happens to the best of us :-)


Fix HPX-APEX cmake integration

Existing apex cmake integration does not work for external Apex installation.
This fix seperates the git fetch installation using HPX_WITH_FETCH_APEX and external installation using Apex_ROOT, cmake variables respectively.

This makes some of the builders fail:

https://github.com/STEllAR-GROUP/hpx/actions/runs/6065900150/job/16455889171?pr=6342
https://app.circleci.com/pipelines/github/STEllAR-GROUP/hpx/15729/workflows/5b3db204-05da-4776-b9c2-814f42beb9c7/jobs/361491

Details

This makes some of the builders fail:

https://github.com/STEllAR-GROUP/hpx/actions/runs/6065900150/job/16455889171?pr=6342
https://app.circleci.com/pipelines/github/STEllAR-GROUP/hpx/15729/workflows/5b3db204-05da-4776-b9c2-814f42beb9c7/jobs/361491

@hkaiser I have fixed the issues. I think it is now ready to be merged. Please review it. Thank you!

@srinivasyadav18 the cmake formatting needs some touching up, still

I have just rebased the branch. That fixed the issue. Thanks!

bors merge


Support temporary private fork creation via API

resolved: #3007

@gmlewis
Thanks for reviewing my PR.
Since I made a modification, please check it out again.

Thank you, @valbeat !
Merging.


Ubuntu,make error!

Freshman,new to the caffe2. meet this error,what should i do? plz~~

Does it say that sleep_for is not a member of std::this_thread? What versions of Ubuntu and gcc do you have?

Ubuntu 16.04  gcc4.7

You can try to pass _GLIBCXX_USE_NANOSLEEP flag to your compiler. Some details are explained here.

@sergey-serebryakov  thanks for your advice,i update my gcc to the version 5.4,and it works right now!

看来Ubuntu得天独厚啊，换到Ubuntu 17.04了。

@MrZhangCF Sounds like this is resolved. Closing the issue.


Style: Implement account icons instead of setting icon

What's the suggested design idea?
If a user wants to visit the profile page, they have to click on the gear icon to go there, but it is not looking good. The task is to add the user/account icon. Current design given below.
Add screenshots

Record

[X] I agree to follow this project's Code of Conduct
[ ] I want to work on this issue

assign me

assign me

I can't since you haven't finish your previous tasks

I want to work on this issue

assign me

I will not since you haven't finish your previous tasks. Please finish the tasks in hand then I will merge this

Since your previous PR is resolved, I am assigning this to you...

I want to work on this issue.

Hi @Priyanshu1129, the issue is already taken care of by @sumanjeet0012. You can explore more issues which aligns with your skills, or you can create one.

Okay


WIP: Print JAX arrays to full precision

Hi! I made an attempt to implement print of JAX arrays to full precision using jax.numpy.set_printoptions as described in #3438. Now I am trying to figure out how to test the function. I have seen some options but they don't seem very adequate;

On closer inspection, I'm not sure there's a bug here. JAX does seem to be respecting the precision options when printing. I think the original issue report was incorrect.

@hawkinsp makes sense, thanks for the feedback! I wish to work on it if the issue happens to be reopened.


Add support for release/5.5 branch in update-checkout script

@swift-ci smoke test and merge

00:57:54.604 Failed Tests (1):
00:57:54.604   lldb-api :: lang/swift/async/stepping/step-in/TestSwiftStepInAsync.py

Unrelated to my change


Added a trigger when an item is selected in typeahead.

I like this one, I need that callback too.


Error after updated to v7.3.0

Hi,
I have updated react-waypoint to 7.3.0 today and I am getting this error:

Everything is working fine after I revert back to v7.2.0
Is this a bug or am I missing something?
Thanks!

The mjs extension was added (and discussed) in https://github.com/brigade/react-waypoint/pull/220. I don't have much context on that change, so I'm going to ask @lencioni for help here. Thanks for taking the time to report this.

Hi, sorry you are running into this issue!
It's a little hard for me to understand what might be going wrong from just
looking at your screenshot. Is there any chance you could put up a repo
that minimally reproduces the issue?
On Wed, Oct 4, 2017, 4:13 AM Henric Trotzig<EMAIL_ADDRESS>wrote:

The mjs extension was added (and discussed) in #220
https://github.com/brigade/react-waypoint/pull/220. I don't have much
context on that change, so I'm going to ask @lencioni
https://github.com/lencioni for help here. Thanks for taking the time
to report this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brigade/react-waypoint/issues/221#issuecomment-334123341,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL7zrcI_-LMeom6oH-0nlUsJWRWhiMJks5so2hFgaJpZM4PtEOJ
.

Hi @lencioni ,
I have quickly setup a react app using create-react-app:
https://github.com/colloquet/waypoint-test
I have only added react-waypoint v7.3.0 and a Waypoint component to App.js and still getting the same error.
Colloque

I have exactly the same problem after upgrading to 7.3.0
When I force version 7.2.0 it works. Same issue as in @colloquet case.

Unfortunately I've run into the same problem. After updating it to 7.3 it started giving me a similar error:
invariant.js:42 Uncaught Error: Invalid tag: /static/media/index.73a4b08a.mjs
at invariant (invariant.js:42)
at validateDangerousTag (ReactDOMComponent.js:343)
at new ReactDOMComponent (ReactDOMComponent.js:370)
at Object.createInternalComponent (ReactHostComponent.js:39)
at instantiateReactComponent (instantiateReactComponent.js:77)
...

Thanks for the repo, it was very helpful.
I'm not super familiar with create-react-app, but it seems to me that its webpack has been configured to recognize files with names that end in .mjs as a static asset, so instead of returning a reference to what is being exported, it is outputing the file in static/media and giving you a string with the path to this file.
I opened an issue on create-react-app here: https://github.com/facebookincubator/create-react-app/issues/3237
In the short term, you can either stick with 7.2.0 for now, or import waypoint like import Waypoint from 'react-waypoint/build/index.js';
Sorry for the trouble, I hope we can get this resolved soon!

same issue here, glad you reported it upstream to CRA, will track both that and this and stick with 7.2.0 for now :)

A fix for this was released in 7.3.1. Thanks for the quick reports everyone!

Thanks! Appreciate your help!

What is the motivation for going with .mjs? Most libraries that have /es/ imports still use .js. It just requires a lot of changes in the build process (webpack/eslint/flow) to support an additional file extension, that from my understanding, is a new extension for node?
Just curious to get some insight on the decision. Thanks!

that from my understanding, is a new extension for node?

This is exactly right, and is the primary reason for the decision. Although it's still early on, there's a good chance that .mjs will one day be the extension that is typically associated with the usage of ES2015 modules.
This library has just adopted this pattern a bit early.

It just requires a lot of changes in the build process (webpack/eslint/jest/flow) to support an additional file extension

I brought up these concerns when we merged in the PR that added this extension. So far, the team has decided that it's worth any issues we might run into. My favorite part of the folks who work on Waypoint is that they're really reasonable. If the extension ends up causing too many issues for users, then I'm sure the team would consider switching back to .js, even if only for a period of time. For now, though, 7.3.1 seems stable. Have you run into specific issues with other tooling on the latest release?

I tried updating all of the places I could think of with the new extension and kept getting errors, so I gave up and stuck with cjs for now. I'll keep watching the repo to see what happens here and try again later

I tried updating all of the places I could think of with the new extension and kept getting errors, so I gave up and stuck with cjs for now.

Ah, alright. I'm sorry you're running into those issues, @benbrandt . If you post more details about what sorts of errors you were seeing with the .mjs extension, someone may be able to help out. Also, I'd be curious to know what happens if you manually go into node_modules and change both the package.json and source files to have a .js extension. There's a chance that your tooling is blowing up due to the ES modules syntax, rather than the file extension.


Connection values created by Radius controller are double-encoded.

Bug information
Steps to reproduce (required)
Run the Radius Kubernetes tutorial that's in PR here: https://github.com/radius-project/docs/pull/864
Observed behavior (required)
When you port-forward to the app, it will crash on the TODO page. The message in the logs looks like:
webapp-65859486d7-x6mzj webapp node:internal/errors:496
webapp-65859486d7-x6mzj webapp     ErrorCaptureStackTrace(err);
webapp-65859486d7-x6mzj webapp     ^
webapp-65859486d7-x6mzj webapp
webapp-65859486d7-x6mzj webapp TypeError [ERR_INVALID_URL]: Invalid URL
webapp-65859486d7-x6mzj webapp     at new NodeError (node:internal/errors:405:5)
webapp-65859486d7-x6mzj webapp     at new URL (node:internal/url:637:13)
webapp-65859486d7-x6mzj webapp     at RedisClient.parseURL (/usr/src/app/node_modules/@redis/client/dist/lib/client/index.js:115:76)
webapp-65859486d7-x6mzj webapp     at Commander._RedisClient_initiateOptions (/usr/src/app/node_modules/@redis/client/dist/lib/client/index.js:311:36)
webapp-65859486d7-x6mzj webapp     at new RedisClient (/usr/src/app/node_modules/@redis/client/dist/lib/client/index.js:77:148)
webapp-65859486d7-x6mzj webapp     at new Commander (/usr/src/app/node_modules/@redis/client/dist/lib/commander.js:44:13)
webapp-65859486d7-x6mzj webapp     at create (/usr/src/app/node_modules/@redis/client/dist/lib/client/index.js:111:16)
webapp-65859486d7-x6mzj webapp     at createClient (/usr/src/app/node_modules/redis/dist/index.js:38:38)
webapp-65859486d7-x6mzj webapp     at RedisFactory.<anonymous> (/usr/src/app/dist/db/redis.js:21:51)
webapp-65859486d7-x6mzj webapp     at Generator.next (<anonymous>) {
webapp-65859486d7-x6mzj webapp   input: 'cmVkaXM6Ly9yZWRpcy13d2d0a2M2MzY0azVjLmRlbW8uc3ZjLmNsdXN0ZXIubG9jYWw6NjM3OS8wPw',
webapp-65859486d7-x6mzj webapp   code: 'ERR_INVALID_URL'
webapp-65859486d7-x6mzj webapp }
webapp-65859486d7-x6mzj webapp
webapp-65859486d7-x6mzj webapp Node.js v18.18.2

Desired behavior (required)
Tutorial works.
Workaround (optional)
It's a tutorial. It works or it doesn't 😆
AB#9886

The root cause of this is double-encoding.
The value stored in the secret created by the Radius controller is Y21Wa2FYTTZMeTl5WldScGN5MTNkMmQwYTJNMk16WTBhelZqTG1SbGJXOHVjM1pqTG1Oc2RYTjBaWEl1Ykc5allXdzZOak0zT1M4d1B3
.... which base64-decodes to cmVkaXM6Ly9yZWRpcy13d2d0a2M2MzY0azVjLmRlbW8uc3ZjLmNsdXN0ZXIubG9jYWw6NjM3OS8wPw
.... which base64-decodes to redis://redis-wwgtkc6364k5c.demo.svc.cluster.local:6379/0? (the correct value).
Somewhere along the way we're storing the value incorrectly in the secret.

The explanation of this behavior is here: https://github.com/weibeld/kubernetes-client-go-examples#ex5-secrets
Using the Kubernetes client from Go, you read and write secrets in their decoded form.