feat(tee): TEE Prover Gateway

What ❔
The TEE Prover Gateway is a service component within our system infrastructure that functions as an intermediary between the TEE enclave and the server's HTTP API, introduced in commit eca98cceeb74a979040279caaf1d05d1fdf1b90c (#1993). It first registers TEE attestation using the /tee/register_attestation endpoint, then regularly invokes the server's HTTP API via the /tee/proof_inputs endpoint to obtain proof-related data, and finally submits the proof through the /tee/submit_proofs/<l1_batch_number> endpoint.
Why ❔
This PR contributes to the effort outlined in the docs:

https://www.notion.so/matterlabs/2FA-for-zk-rollups-with-TEEs-a2266138bd554fda8846e898fef75131?pvs=4
https://www.notion.so/matterlabs/Proof-2F-verification-with-SGX-5fca2c619dd147938971cc00ae53e2b0?pvs=4

Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.
[x] Spellcheck has been run via zk spellcheck.

Guys, this PR isn't fully polished yet, but the code works and does the job. Before refining it further, I need some advice to make sure it's heading in the right direction. The main changes are in prover/prover_tee_gateway. The rest is just configuration-related boilerplate code.
The idea behind this PR is best described here, and here:
https://github.com/matter-labs/zksync-era/blob/372d854323b6839714fe7e95a0e25f99a2013d20/prover/prover_tee_gateway/src/main.rs#L52-L70
I tested it locally using our SGX-enabled machines in simulation mode, meaning no SGX enclave was used yet. It will be relatively easy to switch to an actual SGX enclave once we have it running in simulation mode.
patrick@patrick:~/zksync-era/prover$ RUST_LOG=info cargo run --package zksync_prover_tee_gateway -- --config-path ../../test.yaml --simulation
Attestation quote was successfully registered
2024-06-24T10:36:25.235123Z  INFO zksync_prover_tee_gateway: Starting TEE Prover Gateway
2024-06-24T10:36:25.236227Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Starting periodic job: TeeVerifierInputDataFetcher with frequency: 1s
2024-06-24T10:36:25.236384Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:36:25.237476Z  INFO vise_exporter::exporter: Created metrics exporter with 144 metrics in 45 groups from crates zksync_merkle_tree 0.1.0, zksync_object_store 0.1.0, zksync_eth_client 0.1.0, zksync_prover_tee_gateway 0.1.0, zksync_web3_decl 0.1.0, ...
2024-06-24T10:36:25.239396Z  INFO vise_exporter::exporter: Starting Prometheus exporter web server on <IP_ADDRESS>:3314
2024-06-24T10:36:29.357001Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/1
2024-06-24T10:36:30.364839Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:36:35.273205Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/2
2024-06-24T10:36:36.281514Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:36:39.766674Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/3
2024-06-24T10:36:40.774033Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:36:46.074133Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/4
2024-06-24T10:36:47.082928Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:36:55.756997Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/5
2024-06-24T10:36:56.765820Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:37:09.389936Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/6
2024-06-24T10:37:10.397319Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/proof_inputs
2024-06-24T10:37:11.358309Z  INFO zksync_prover_tee_gateway: Stop signal received, shutting down
2024-06-24T10:37:11.358889Z  INFO vise_exporter::exporter: Stop signal received, Prometheus metrics exporter is shutting down
2024-06-24T10:37:11.359218Z  INFO vise_exporter::exporter: Prometheus metrics exporter server shut down
2024-06-24T10:37:16.360379Z  WARN zksync_utils::wait_for_tasks: Failed to terminate actors in 5s
2024-06-24T10:37:27.412702Z  INFO zksync_prover_tee_gateway::api_data_fetcher: Sending request to http://<IP_ADDRESS>:3320/tee/submit_proofs/7

State of the SQL db after running the above command:
zksync_local=# SELECT * FROM tee_proof_generation_details ORDER BY l1_batch_number LIMIT 10;
 l1_batch_number |       status       |                                                             signature                                                              |                                pubkey                                |                               proof                                | tee_type |         created_at         |         updated_at         |      prover_taken_at
-----------------+--------------------+------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+--------------------------------------------------------------------+----------+----------------------------+----------------------------+----------------------------
               1 | generated          | \xae1e7e3997f1a125adcb4d1e6d1ad1348750804d8611492bc068813f5725d6521925e3aa19733544f5b12b0aefd9128bbeab378190280466adf0593e0099a42d | \x03065d641f791d7d5336a5fe666dd2c7d6dd59868d7300355e9e52177a4a809dee | \xcc8e8d36891b92eb080a01d22590e0a42ef074b884b2548c4e4101b6067b37a0 | sgx      | 2024-06-20 11:18:38.23828  | 2024-06-24 10:36:29.360226 | 2024-06-24 10:36:25.245783
               2 | generated          | \xc97aa8af5f4ace74765cf88dac32e25b7223f08eac35e8afebd15416857246344606f03a42429d5a29ca799f4aee5387496f30d37f413001787e85821f66181c | \x03065d641f791d7d5336a5fe666dd2c7d6dd59868d7300355e9e52177a4a809dee | \xcebf3e584510e88fe73fe4ec5f6f03fb790b598a09318182afd3ee5856c7e1aa | sgx      | 2024-06-20 11:21:42.299929 | 2024-06-24 10:36:35.275415 | 2024-06-24 10:36:30.36784
               3 | generated          | \x7950c131e0485ed439b783151b69b2b09305023196fb68a8fdd9871e8bfc946a4a13621cd6c110d337c828838599e0e525df0175dea53efef64787eae355f01f | \x03065d641f791d7d5336a5fe666dd2c7d6dd59868d7300355e9e52177a4a809dee | \xa98979b4bb45781e4d5ab4204b7965718825fbaccf531b86e890d191e1f63a96 | sgx      | 2024-06-20 11:21:44.316315 | 2024-06-24 10:36:39.768866 | 2024-06-24 10:36:36.284384
               4 | generated          | \x0f9fca2c61b7491a1e925e6ac4ad97bac31f0ede8e8cddfe1ce5038167cdc5401a5a2b9b72fa526a501ac0cbc6ea184f5958188f1f74748732ed1a710745ca52 | \x03065d641f791d7d5336a5fe666dd2c7d6dd59868d7300355e9e52177a4a809dee | \xe3cb8b2b8a01d150df3875936eb2b5a14d252f46775e888fc83ba4069bccc596 | sgx      | 2024-06-20 11:22:00.35344  | 2024-06-24 10:36:46.076382 | 2024-06-24 10:36:40.777835
               5 | generated          | \xf3aa6de1713e32a295369ea5a5b2ac17b0f0c7d33910c4a6872e6f70f0c9f18f4cd33adafc7a9cb9ee8316b0ca298f66c4625981384ed84bded4c440a64cea1d | \x03065d641f791d7d5336a5fe666dd2c7d6dd59868d7300355e9e52177a4a809dee | \x5fb0fc34f9d3d99b228708e38974f1261c9a1d66a35f8ddf905ae38bff88f2f0 | sgx      | 2024-06-20 11:22:02.41282  | 2024-06-24 10:36:55.759575 | 2024-06-24 10:36:47.086305
               6 | generated          | \xddd00e264dc7b07c802c300fb22b36e23e4349ed9ebe391c8e72a2d9847856f406d8e3b0dc5b6aad4ffb0a032fd38e79561be910ed179ced3f891c2e98866f9e | \x03065d641f791d7d5336a5fe666dd2c7d6dd59868d7300355e9e52177a4a809dee | \x2494f589891fcd100f183c4289a73cdf17556cddef7b82a5134df7a1b4cd7fb0 | sgx      | 2024-06-20 11:22:11.467021 | 2024-06-24 10:37:09.392016 | 2024-06-24 10:36:56.769566
               7 | picked_by_prover   |                                                                                |                                                                      |                                                                    |          | 2024-06-20 11:22:14.514738 | 2024-06-24 10:37:10.400956 | 2024-06-24 10:37:10.400956
               8 | ready_to_be_proven |                                                                                |                                                                      |                                                                    |          | 2024-06-20 11:22:23.558881 | 2024-06-21 11:04:07.218994 |
               9 | ready_to_be_proven |                                                                                |                                                                      |                                                                    |          | 2024-06-20 11:22:25.613403 | 2024-06-21 11:04:27.581246 |
              10 | ready_to_be_proven |                                                                                |                                                                      |                                                                    |          | 2024-06-20 11:22:35.686172 | 2024-06-21 11:04:49.115012 |
(10 rows)

Thanks for the suggestions @popzxc!
I have a quick question, as I'm not yet fluent with the node framework and I want to provide more context on how we want to run the TEE Prover Gateway. Does the Node framework make it easy to build a standalone binary, decoupled from the zksync-era server, so that I could run it with the tee-key-preexec binary like this: ./tee_key_preexec ./tee_prover_gateway? Or is it acceptable to run the whole zksync-era node with the tee-key-preexec as follows: ./tee_key_preexec zk server --components tee_prover_gateway?
We need tee-key-preexec to 'inject' some environment variables for the TEE Prover Gateway.
cc @haraldh

@pbeza the node framework is not tied to the server -- the last code snippet I provided is a sample for a stand-alone binary (which has nothing to do with the server).

The code changes needed for this PR are too major to continue work on it. Closing it and going with the simpler #2333 instead.


EXSWHTEC-136 - Implement tests for hipGraphicsGLRegisterImage

Basic positive tests
Positive test case for multiple registrations of same resource
Negative parameter tests.

Depends-on: #3077

PR moved to: https://github.com/ROCm-Developer-Tools/hip-tests/pull/64


Error in running WADI dataset

Hi, I'm trying to run InterFusion with WADI(A2) dataset.
I used these code python algorithm/stack_train.py --dataset=WADI --train.train_start=259200 --train.max_train_size=789371 --train.valid_portion=0.1 --model.window_length=30 '--model.output_shape=[15, 15, 30]' --model.z2_dim=8 # training and
python algorithm/stack_predict.py --load_model_dir=./results/stack_train/ --mcmc_track=False	# evaluation
When I run stack_predict.py, this error occurs
This is my log
*Evaluate score on testing set
100%|#############################################################################################################################| 3456/3456 [26:53<00:00,  2.14step/s]
Final testing statistics
test_nll                   3940.691162109375
test_lb                    -3965.151123046875
test_recons                -3830.451904296875
test_kl<PHONE_NUMBER>0703125
test_ll                    -3940.691162109375
normal_point_test_recons   -127.42149353027344
*Evaluate score on training set
*Calculating and plotting reconstruction data
100%|#############################################################################################################################| 3456/3456 [25:54<00:00,  2.39step/s]
(172772, 10, 123)
Traceback (most recent call last):
File "algorithm/stack_predict.py", line 654, in
main(exp, exp.config)
File "algorithm/stack_predict.py", line 549, in main
train_set_batch_count,
UnboundLocalError: local variable 'train_set_batch_count' referenced before assignment
In stack_predict.py line 481, WADI does not need train_set_batch_count.
Is this problem caused by the WADI dataset's version? or is there any command to run InterFusion with WADI datasets?

You used a different version of WADI dataset, and the data shape maybe different from the configs set in the code.
For WADI dataset, when you run stack_predict.py, please add the parameter '--plot_recons_results=False' to skip the 'calculating reconstruction data' procedure on training set (which is very time-consuming).  If you also want to do evaluation on training set, you can change the code in line 481 (stack_predict.py) to do the evaluation.

Thank you for your reply.

Yes, I changed all settings.
In stack_predict.py, --plot_reoncs_results=False argument works.

I have a question about WADI dataset's performance.
When I train WADI(A1) and test with --plot_recons_results=False argument, performance is very poor.
In your paper section 4.2, the performance of WADI is 0.9103, but I got 0.3503.
Are there any arguments to set for good performance? or do I have to change code in stack_predict.py?
This is my result.
***  best_f1  ***:  0.35037442778013234
*** threshold ***:  -128.11734
test_nll                   3767.2998046875
test_lb                    -3790.3681640625
test_recons                -3655.095947265625
test_kl<PHONE_NUMBER>798828
test_ll                    -3767.2998046875
normal_point_test_recons   -121.75577545166016
best-f1                    0.35037442778013234
precision                  0.8385991593505931
recall                     0.22145154782725016
TP                         2203
TN                         162400
FP                         424
FN                         7745
threshold                  -128.11734
auroc                      0.7231228678866259
ap                         0.3112237275344468 Results
I used the same dataset this time because the last dataset version was unmatched.

@soemthlng 1. Please check if you are using the same version of WADI dataset (The folder name is 01_WADI Dataset_09 Oct 2017), and follow the instructions in explib/raw_data_converter.py to prepare the data. (Note that there is a typo in table_WADI.pdf, attack 9. The date should be 11/10/17, follow the time order).
2. Run the script for WADI listed in the README file.
3. The final test_nll should be about 50000 or higher, it seems that your model was not properly trained (check the data preprocessing and algorithm configurations).

@zhhlee I followed your instructions.

Use WADI A1 dataset and preprocess using explib/raw_data_converter.py.
Run the script for WADI in README
But, I have a question in 2. I added the argument --plot_recons_results=False in stack_predict.py.
Is there a reason this argument is not included in README?
My result was similar to before. There is no differences using explib/raw_data_converter.py.
This is my result.

Final testing statistics
test_nll                   3749.566162109375
test_lb                    -3770.3876953125
test_recons                -3645.810302734375
test_kl<PHONE_NUMBER>3144531
test_ll                    -3749.566162109375
normal_point_test_recons   -121.3981704711914
*Evaluate score on training set
Calculating best F1-score****
computing best f1
***  best_f1  ***:  0.35191366778972266
*** threshold ***:  -127.67305
test_nll                   3749.566162109375
test_lb                    -3770.3876953125
test_recons                -3645.810302734375
test_kl<PHONE_NUMBER>3144531
test_ll                    -3749.566162109375
normal_point_test_recons   -121.3981704711914
best-f1                    0.35191366778972266
precision                  0.8565318784738262
recall                     0.22145154782725016
TP                         2203
TN                         162455
FP                         369
FN                         7745
threshold                  -127.67305
auroc                      0.7302721279454815
ap                         0.3228597290984524 Results

@soemthlng 1. It's OK to use --plot_recons_results=False for WADI when running stack_predict.py, and I think it won't hurt the performance. I guess the problem is that you do not properly train the base model with stack_train.py.
2. I upload the preprocessed data here: https://1drv.ms/u/s!AsTNHlSUTQHXhAZzBh1CcypQNn3I?e=B8mffx. Please try to retrain the model using this data (as well as the stack_train scripts and parameters for WADI in README).
3. I retrain and evaluate the performance on WADI for several times, and the best-f1 scores are all higher than 0.91 (with GTX2080Ti+tf1.14, or with GTX1080Ti+tf 1.12). To help you reproduce the results, I put one of the trained models and configurations in the above link, which achieves best-f1 around 0.913. You may run stack_predict.py with this model for evaluation.

@zhhlee
I tested with your data and your train result, but its performance is still low.

I tested with your WADI dataset.  In this case, F1-score is still the same.
This is my result
Final testing statistics
==============================================
test_nll                   3761.08203125
test_lb                    -3785.680908203125
test_recons                -3649.53515625
test_kl<PHONE_NUMBER>640625
test_ll                    -3761.08203125
normal_point_test_recons   -121.67398071289062

*Evaluate score on training set
Calculating best F1-score****
computing best f1
***  best_f1  ***:  0.3525084144827284
*** threshold ***:  -127.91522
test_nll                   3761.08203125
test_lb                    -3785.680908203125
test_recons                -3649.53515625
test_kl<PHONE_NUMBER>640625
test_ll                    -3761.08203125
normal_point_test_recons   -121.67398071289062
best-f1                    0.3525084144827284
precision                  0.7620768952938649
recall                     0.2292861377997962
TP                         2319
TN                         161934
FP                         724
FN                         7795
threshold                  -127.91522
auroc                      0.733236625590403
ap                         0.30824492175337614 Results

I tested with your train result. In this case, F1-score is higher than before, but still very low.
This is my result
Final testing statistics
=============================================
test_nll                   3765.89306640625
test_lb                    -3790.333740234375
test_recons                -3663.179931640625
test_kl<PHONE_NUMBER>4648438
test_ll                    -3765.89306640625
normal_point_test_recons   -121.8533706665039

*Evaluate score on training set
Calculating best F1-score****
computing best f1
***  best_f1  ***:  0.3613804832899812
*** threshold ***:  -128.16197
test_nll                   3765.89306640625
test_lb                    -3790.333740234375
test_recons                -3663.179931640625
test_kl<PHONE_NUMBER>4648438
test_ll                    -3765.89306640625
normal_point_test_recons   -121.8533706665039
best-f1                    0.3613804832899812
precision                  0.8525735262773031
recall                     0.2292861377997962
TP                         2319
TN                         162257
FP                         401
FN                         7795
threshold                  -128.16197
auroc                      0.7400281870228925
ap                         0.33175369788452974 Results
My environment setting is as follows: Ubuntu 18.04 LTS Tesla V100-PCIE+tf 1.12
I have no idea why only WADI's result is wired. I will try to find the reason and if I find the reason, I will reopen this issue again.
Thank you for your help.


feat(protocol): create SharedTaikoTokenVault.sol

Seems pretty straightforward but i'll add couple of tests today.

Did not we discuss last week this will be a multisig ? 🤔

Did not we discuss last week this will be a multisig ? 🤔

Ah, you are right.

Seems pretty straightforward but i'll add couple of tests today.

@dantaik modified the tests to use this contract.


Include the stellar deposit tx hash in mintComlete event

We need to include tx hash to the MintCompleted event for better observbility and event correlation in the bridge.
This will allow to instrument the system to use a common trace_id to stitch all related operation together to tell operators the whole story of a cross-chain transfer.
Context:
https://github.com/threefoldtech/tfchain/issues/874

Update:
PR: https://github.com/threefoldtech/tfchain/pull/885


Feature/forget password

Add forget password feature.
Updated readme for installation instruction.
Fix learn more button for guest user.

fixes #31


end-to-end integration with model server, estimator, and kepler

[ ] e2e integration
[ ] test cases for validation

Currently developing the e2e integration and validation through https://github.com/sustainable-computing-io/kepler-e2e-test

bump up this issue

are we good enough for now?
we have test case as golang code, check both metrics and value of each metric.

#449 is a step to that. It gets estimator into the e2e test

Kepler, estimator and model server are integrated via #449. Kepler e2e test is now available.
Next step is to brainstorm on the test cases that cover all the components and are runnable on CI.

Track next step in #456


fix: DUBBO_DUBBO_IP_TO_REGISTRY

replace DUBBO_DUBBO_PORT_TO_BIND with DUBBO_DUBBO_IP_TO_REGISTRY
format the document

Please do not modify doscy submodule

Oops! It has been reverted.

@AlbumenJ It was fixed, please take a look.


Consider adding README links to start/resume a codespace

The GitHub documentation explains how to use the codespaces.new domain to quickly reach the codespace creation or resume options.
Since this is on a separate domain, is this generally available to users, or might it cause confusion by it not working?

Given that the UI option on GitHub is easily accessible when viewing the README, I'm going to suggest that we don't do this for now. It might be something to reconsider once we've gotten some feedback from users though.


2.1 AuthZ improvements

This issue will track all the various Authorization improvements we are looking at for 2.1.
Some initial thoughts:
From @davidfowl
We've had a bunch of feedback about our authz system with respect to flowing context from the authorize attribute to the authorization handler:

https://github.com/aspnet/Security/issues/670
https://github.com/aspnet/Mvc/issues/5607
https://github.com/aspnet/Security/issues/917
https://github.com/aspnet/Security/issues/1352

Today the Authorize attribute supports has enough metadata to describe the policy but it doesn't let you specify the resource (via IAuthorizeData). I think if we solve that, it might solve a bulk of the issues since people will be able to write custom attributes that flow the relevant context to the authorization handler.
Today that's only possible when doing imperative authz. I was thinking something like:
public interface IAuthorizeResource
{
    object Resource { get; }
}

If the attribute implemented this, we would flow that as the resource to the handler. This way you implement permissions of whatever you please via resources.

From @rynowak
Look into providing overriding semantics in MVC, maybe a marker interface: IAuthorizeMetadata. Any attributes that implement that interface on the endpoint could be flowed. Then it’s up to developers to build whatever they want.  (Also look into flowing single objects vs many objects + requirements VS resources)
We will also look into making it possible to specify requirements via Attributes similar to imperative AuthZ so you don't have to preconstruct policies for attributes.
Misc other improvements:

Consider supporting OR logic for policies: https://github.com/aspnet/Security/issues/1356
Consider enabling policies to be defined in configuration

My additional thoughts on this. We're looking at making the concept of an endpoint available at a low level from the dispatcher. Endpoints will have arbitrary metadata in an ordered list. This is the equivalent to what MVC does today by passing the action descriptor.

Additionally in the case of MVC, the current [Authorize] has some surprising behaviors compared to other filters. All authorize filters will execute rather than supporting overriding.  Additionally, [AllowAnonymous] cannot be overridden and turns off all authorize attributes. These might be consistent with the past, but they don't really fit with the zen of MVC filters.

Interesting, well if we have a new endpoint concept with a clean slate for metadata, we should probably just expose all of the basic building blocks

Building the ClaimsPrincipal, need to end up with 0 or more authentication schemes.  If none are specified, we continue to use the default user aka httpContext.User, otherwise we build a merged user via authenticating all of the schemes.  We could manifest this with a series of [Authenticate(scheme)] attributes.

Specifying the Authorization requirements, today the metadata only targets policies, but we could have [Authorize(typeof(MyRequirement), typeof(MyOtherRequirement)]

Some examples:
[Authorize]
Would behave the same as today (using some default policy which relies on context.User, and still only does RequireAuthenticatedUser by default
[Authenticate("Bearer")]
[Authorize]
Would use the Bearer scheme and only require that it exists.
[Authenticate("Bearer", "Cookie")]
[Authorize(typeof(RequireAdminClaim)]
Would use the merged Bearer Cookie schemes and require an admin claim.

Which challenge would you issue?

All of them, its not any different than today

Challenging both Bearer and Cookie is nonsensical.

Not disagreeing, but today if you have a policy that has Bearer and Cookies, that's what it does today as well

Unless we want to eliminate being able to specify multiple schemes entirely...  that's an option that would simplify things...

Not disagreeing, but today if you have a policy that has Bearer and Cookies, that's what it does today as well

It does? What happens as a result? Don't they stomp on each other?

Yeah they do, last one wins, multiple auth schemes in policies has always been a bit weird

Some are compatible like Bearer, Basic, and Windows.

@HaoK please log new issues for any 2.1.0 proposals.

@HaoK Is it going to be a part of 2.1 release?

I want to have ability to return custom json if specific policy failed. for example
403
{
"errorType": "PrivalcyPolicyAcceptRequired",
"errorMessage": "You token doesn't have PolicyAccepted claim"
}

No the error authZ improvements didn't make it into 2.1, I'll try to get them in 2.2

I assume that is why the title changed to 2.2 😜⁉

So rough idea of some initial AuthZ improvements I've got at the top of my head for 2.2

For errors, maybe some kind of scoped IAuthorizationErrorService, that the authZ services will report errors to with appropriate context.  This should enable apps to write an appropriate detailed authorization error.

UseAuthorize("policyName") - middleware equivalent of [Authorize("policyName")], would behave similarly, and also allow sideffect of setting httpContext.User if AuthenticationScheme is specified in the policy. TBD on what to do for failure, redirect to some access denied page which is able to display the appropriate context seems ideal.

I think we should close this issue and revisit this in 2.2 planning so we can scope it down.

Close or leave it open for planning?

Have you considered to add some ability to access to the list of policies which is run and which is failed. Also I thought it could be a helpful to have overload of method context.Fail(); with some object which can be accessed later.

Is this what currently prevents something such as the ability to show a specific page when a specific policy fails. For example, when a policy fails, redirect to a page that shows how to get that particular policy? (i.e. paying for a new membership level).

Specifying a resource still wouldn't allow you to do something like pass a list of permissions to the attribute and there are too many possible combinations of permissions to make policies for every case. Maybe its not in the spirit of policies, but I don't understand how it is different than allowing a consumer to pass a list of roles.
All I want to be able to do is pass a list of permissions, call a microservice, and return a result, but it feels like I am going to have to write my own AuthorizeFilter at this point.


Clean room not working

I have dug out some parts of the mountain to build a base there.
To clean the new room, I selected the colonists and used "Clean this room". They went inside that room, but then got stuck with "Standing". The same happens with a single colonist.
When I choose a smaller room, it works fine.
OT: Cool ideas so far :+1:

I noticed that this also happens with smaller rooms.
It completely messes the JobGiver up, they are just "Standing" after they cancelled cleaning by themselves.

Every colonist set to clean the room gets this error-spam:

I rewrote the whole clean room logic (and added a Fight Fire job too that works outside the home zone). Would you mind to evaluate it again?

Did you already push this to Steam or do I need to download the repo and compile it myself?

Not yet. But the whole GitHub repo is a complete plugin already. Just download it as a zip and put the folder into your Mods folder.

Since this defect was filed the code has changed a lot. So I close this and if it remains a new issue can be opened again.

Didn't notice any problems so far, just some "dusters" (or how they are called - would be Staubwedel in German) moving around the room and I'm not sure if this is intended. :P

Yes it's intended. That symbol is usual used to indicate work at a specific place (which is usually 1 square = 1 job). Since how the whole job is to clean and change target I tried to move the symbol code-wise to the new cleaning square too but had no luck with fighting the RimWorld code. So the only option for now is to "show symbol on t

... [pressed button on accident] ...
"show symbol on the way to your goal" which in this case is the point between the colonist and the point you clicked at to clean the room.

And of course great that the command works for you. The old version had lots of reports on colonists become unusable after cleaning and no way to cancel but the new version should behave just fine.

Well this is just a cosmetical issue and I don't mind it. When I saw it first, I thought it is some kind of ghosts cleaning the room to make it faster. :D
Keep up the good work! :+1:


Use Json ID Generator for referencing other classes

Alternatively just use object name and make sure everything has a name.

Closing this issue as I've decided to use object and asset names. Blender enforces unique names for unique objects, so it shouldn't be an issue, and I don't want to add data if it's not required.


git.io->cloudposse.tools update (#134)

what

Update from upstream

Affected by https://github.com/terraform-docs/terraform-docs/issues/594

Please ignore Auto Format check. It is removed in the current PR.


Default FancyZone layout

Description of the new feature / enhancement
FancyZones is amazing! It makes my life much better.
I would LOVE it if you could add a checkbox to set one of the Templates on the layout editor as default. Every time I change something with my video card/monitor setup, it defaults my new monitor to Priority Grid, but I only use Grid. I would like it to default to Grid all the time, and never Priority Grid.
Scenario when this would be used?
Whenever I modify my video setup (new video card, modified configuration, etc.).
Supporting information
No response

Hi there,
Oh, I see it now! Thank you, that’s perfect. And you even let us specify separate defaults for landscape and portrait monitor configurations, that’s brilliant.
I was looking for it on the Template selection screen.
Much appreciated,
Joel @.***)
From: Seraphima Zykova @.>
Sent: Monday, November 14, 2022 4:08 AM
To: microsoft/PowerToys @.>
Cc: ElmoKajaky @.>; Mention @.>
Subject: Re: [microsoft/PowerToys] Default FancyZone layout (Issue #22018)
Hi @ElmoKajaky https://github.com/ElmoKajaky , since 0.64 you can set the layout of your choice as default. Please check it in the editor and let me know if it helps :)
https://user-images.githubusercontent.com/8949536/201656146-e8fdb173-5557-407a-8bfc-519d0af0852f.png
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/PowerToys/issues/22018#issuecomment-1313581814 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A4EP44TMSTUZMYALQ6TLPB3WIITR7ANCNFSM6AAAAAAR6BUUTE .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A4EP44T454WZHHINRPBC5CDWIITR7A5CNFSM6AAAAAAR6BUUTGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSOJOVPM.gif Message ID: @.*** @.***> >


After upgrade from 8.0 to 8.2, make-component command still not working.

Hi Nicholas,
Thank you for your hard working on upgrade package version.
I've upgraded to version 8.2, but in modules.php (config), there is no 'component-class' or 'component-view'.
On the other hand, when I run command:
php artisan module:make-component _component_name_ _module_name_
Command "module:make-component" is not defined. message appeared on the terminal.
I tried to delete vendor folder and reinstall packages, but there was no hope.
Best regards.

I have the same  issue , also component inside module not resolved yet.
"Unable to locate a class or view for component ... ".

you can resolve them by using this syntax:
<x-module::component />
for example, if you have  a Blog  Module and you create a component in  Blog/Resources/views/components/sidebar.blade.php
you can resolve it like  that
<x-blog::sidebar />
as it explained here:
https://laravel.com/docs/8.x/packages#anonymous-components

Up vote.
Please update this function.

You can change config in modules.php
ComponentClassMakeCommand::class,  ComponentViewMakeCommand::class,
add this classes to commands so your issue resolved

@davidkai147 I've create PR #1148

@nWidart This can be closed as you've merged #1148

you can resolve them by using this syntax:
<x-module::component />
for example, if you have a Blog Module and you create a component in Blog/Resources/views/components/sidebar.blade.php
you can resolve it like that
<x-blog::sidebar />
as it explained here:
https://laravel.com/docs/8.x/packages#anonymous-components

Thanks for this. The documentation page need to be updated. @nWidart

you can resolve them by using this syntax:
<x-module::component />
for example, if you have a Blog Module and you create a component in Blog/Resources/views/components/sidebar.blade.php
you can resolve it like that
<x-blog::sidebar />
as it explained here:
https://laravel.com/docs/8.x/packages#anonymous-components

Thanks for this. The documentation page need to be updated. @nWidart

you can resolve them by using this syntax:
<x-module::component />
for example, if you have a Blog Module and you create a component in Blog/Resources/views/components/sidebar.blade.php
you can resolve it like that
<x-blog::sidebar />
as it explained here:
https://laravel.com/docs/8.x/packages#anonymous-components

Thanks for this. The documentation page need to be updated. @nWidart

Make a PR to it

you can resolve them by using this syntax:
<x-module::component />
for example, if you have a Blog Module and you create a component in Blog/Resources/views/components/sidebar.blade.php
you can resolve it like that
<x-blog::sidebar />
as it explained here:
https://laravel.com/docs/8.x/packages#anonymous-components

Thanks for this. The documentation page need to be updated. @nWidart

Make a PR to it


Roll engine 3b944102a56e..3c9a22c778f8 (4 commits)

https://github.com/flutter/engine/compare/3b944102a56e...3c9a22c778f8
git log 3b944102a56e8f4182e6601113fc36538edf3de9..3c9a22c778f89e826edfe0f1814346acedbefe59 --no-merges --oneline
3c9a22c77 Fall back to a fully qualified path to libapp.so if the library can not be loaded by name (flutter/engine#9762)
298a610c7 Roll fuchsia/sdk/core/mac-amd64 from XOXaWqvr4OuJ6O3uPefSwSFjZMaEmDHy5JQm3Q8Oc0wC to CDbRdGJ3bu-aWMCZqN5VzfQqIBwDGL2wfFodWABKdCIC (flutter/engine#9790)
833f6b4fc Roll src/third_party/skia f9fcf7ffa89a..7825d4983f90 (6 commits) (flutter/engine#9788)
1250c3773 Add comments to differentiate two cache paths (flutter/engine#9721)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (garyq@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5889563707310080

Commit queue failed; closing this roll.


MacOS export failing on MacOS (Godot 3.0alpha2)

I'm on macOS Sierra (x86_64-apple-darwin14.5.0) and Godot 3.0 alpha 2 (downloaded the build).
When exporting a project to MacOS (using the downloaded export templates) I get

Other exports seem to work fine.
To reproduce, simply download build and templates from here and export a project to MacOS.

I guess there are changes in the way OSX binaries are meant to be packed in the template now, but nobody made sure yet that the buildsystem for release binaries was adapated.

@akien-mga problem lies here:
https://github.com/godotengine/godot/blob/master/platform/iphone/export/export.cpp#L447
String binary_to_use = "godot.iphone." + String(p_debug ? "debug" : "release") + ".";
int bits_mode = p_preset->get("application/bits_mode");
binary_to_use += String(bits_mode == 0 ? "fat" : bits_mode == 1 ? "arm64" : "armv7");

Weird though, it should be either adding .arm64 or .armv7, not .64, it used to be .fat. I don't know why I changed that though, I'll have a look how this was on Godot 2 and probably will change it back the way it was.

Well I'm fine with it changing, I just need to adapt my scripts.

Just to make sure, I was trying to export to MacOS computer, not iphone (though maybe the two things are linked, I don't know).
There's one more piece of information which may be related. I tried compiling from source following the instruction for Mac (as explained here):
user@host:~/godot$ scons platform=osx
user@host:~/godot$ cp -r misc/dist/osx_tools.app ./Godot.app
user@host:~/godot$ mkdir -p Godot.app/Contents/MacOS
user@host:~/godot$ cp bin/godot.osx.opt.tools.fat Godot.app/Contents/MacOS/Godot
user@host:~/godot$ chmod +x Godot.app/Contents/MacOS/Godot

The docs assume that I would get a godot.osx.opt.tools.fat binary but I actually got a godot.osx.opt.tools.64. I'm not sure if that's linked with the change that broke the export for Mac.
Thanks a lot for looking into this!

Ugh, sorry for some reason I have iOS in mind. That explains why it's .64 and not .arm64 :)
The code here is indeed very similar. I'm just going to tag @endragor in this as well. He's done a lot of work on this code as well.

any progress in this?

This still seems broken for me, using the non-mono official 3.0 build exporting to macOS from macOS.

Please open another bug report, it's not possible that you're experiencing this exact issue, that string doesn't appear anywhere in the engine.

it's not possible that you're experiencing this exact issue, that string doesn't appear anywhere in the engine

Actually the GitHub search failed me, this string indeed comes from the macOS export code. Sorry about that.

This error happens because we only ship fat binaries (32-bit + 64-bit), which is the default export option ("application/bits_mode"), but you likely changed it to 64-bit. So export 64-bit only, currently you need to build your own template as we don't provide it.

So it's not a bug but a badly exposed feature. Eventually, I think the fix might be to just get rid of the fat architecture and support only 64-bit on macOS, since I think all supported macOS versions are 64-bit only by now?

@akien-mga That's true, 32-bit macOS is no longer supported since 10.8 or so.


Improve bar documentation especially for color

Addresses a users comment about limited bar documentation and no documentation of color. See https://discourse.holoviz.org/t/is-there-a-way-to-add-a-specific-color-to-each-group-in-a-grouped-bar-plot-like-hue-in-seaborns-barplot/5066
Also fixes a few docstring bugs identified when rendering the output of hvplot.help('bar') on Discourse.
https://user-images.githubusercontent.com/42288570/224508335-3a1d31b4-64ee-4943-a0ee-591886aa3529.mp4
Issues identified while working on this
The main issue is that lots of things does not work for Matplotlib and Plotly backends as they do for Bokeh backend

#1034
#1035
#1036
#1037
#1038
#1039

Thanks a lot!


Case sensitive headers in web hooks

Two issues about github monitoring:
To retrieve github hook call, I have had to define a GithubPropertyPathNotificationExtractor:
@Bean
	public PropertyPathNotificationExtractor githubPathExtractor() {
		return new GithubPropertyPathNotificationExtractor();

If this is the desired way to configure git provider, It should be included in documentation.
Perhaps, extractor implementation could be retrieved parsing git uri path.
Second issue is related with headers case.
My config server is using Brixton.M1 parent and default configuration
@Configuration
@EnableAutoConfiguration
@EnableConfigServer

I have no idea why every request done against config server is received with http headers in lowercase.
This is causing GithubPropertyPathNotificationExtractor doesn't work, because X-Github-Event header is not found, but the behaviour is general.
Request against EnvironmentController are also coming with lowercase headers.
I'm using a RequestDumperFilter to show requests headers.
Request againts my application service (Spring Boot + Spring Cloud config client) are coming with correct headers.

Brixton.M1 is probably not a great way to test this since the monitor jar is only available in snapshots. Can you try again with a snapshot please? Headers should be case insensitive, but maybe that was fixed in master.
Pull requests for documentation are always more than welcome. On the other hand I see no reason why the github and gitlab extractors shouldn't be included as defaults. Do you want to do that?

You are right about Brixton.M1, I should be using snapshot for everything. Not only for monitor.
It's perfect for me both github and gitlab extractors are included by default. The problem, currently (at least in my tests), is that no one is included.
I'll test using cloud-config snapshots.

Testing with Brixton.BUILD-SNAPSHOT I got the same behaviour
headers.getFirst("X-Github-Event") returns null because header is lowercase

I got the same problem while writing this blog post. I thought I had pushed my fixes, hadn't. See #242.

I think I fixed the case sensitive issue. If there is something else please open another issue.


Textarea not resizable

Textareas are no longer resizable when using wysihtml5.

Resize property doesn't work for iFrame on Firefox

See the first line of the readme file
@CanoGit


api/vmrule: populate validation error in VMRule status

Is your feature request related to a problem? Please describe
When a user creates a VMRule and it is not the correct one, the user does not see the error.
I want the operator to write this error/status in the crd VMRule status in case of an error, and the user, when describing a resource, could see that there is an error there. Not all users have access to go and look at vmalert logs since this is a system component, and VMRule is just a user resourceю.
Describe the solution you'd like
I want the operator to write this error in the crd VMRule status in case of an error, and the user, when describing a resource, could see that there is an error there.
Describe alternatives you've considered
No response
Additional information
No response

released in v0.47.0


fix(generator): Respect namespace, prevent name collision

#17

Thanks for the PR!
Released in https://github.com/omar-dulaimi/trpc-shield/releases/tag/0.4.3


[TEST] Improve page load performance

Description

Opening this PR mainly for testing purposes to compare the preview deploy with the production docs site
This PR includes some performance optimizations implemented based on looking at page load traces

Avoids calling getBoundingClientRect() in our table of contents logic to avoid forcing style recalc/layout at that point
Patches Expressive Code’s tabindex logic to use requestIdleCallback instead of setTimeout to delay measuring code sample widths until the main thread is idle

size-limit report 📦

Path
Size

/index.html
5.95 KB (-0.02% 🔽)

/_astro/*.js
22.01 KB (+0.66% 🔺)

/_astro/*.css
13.79 KB (0%)


New Command Get-DbaDbPageCount fixes #3455

New command to count pages in a database
Test to test the new command

I would say it would be best to have the command output the raw data and then we can use ps to aggregate or sum whatever we want. So something like Get-DbaDbPageInfo.

Thanks, I'll look into that. It shouldn't be that big of a problem. I just have to make sure I get the same content for different versions of SQL Server.

Well at most this command will only support 2008 and higher so you can set that in the connect call using -MinimumVersion 10.

ty!


ColMarTech Automated Marine Equipment Rack

STANDARD EQUIPMENT (TAKE ALL)

[x] #1357
[x] #1358
[ ] #1359

ARMOR (CHOOSE 1)

[x] #1360
[x] #1361
[x] #1362

BACKPACK (CHOOSE 1)

[x] #1363
[x] #1364
[ ] #1365

BELT (CHOOSE 1)

[x] #1366
[ ] #1367
[x] #1368
[ ] #1369
[ ] #1370
[ ] #1371
[ ] #1372
[x] #1373
[ ] #1374

POUCHES (CHOOSE 2)

[x] #1375
[x] #1376
[ ] #1377
[ ] #1378
[x] #1379
[ ] #1380
[x] #1381
[ ] #1382
[x] #1383
[x] #1384
[x] #1385

MASK (CHOOSE 1)

[x] #1386
[x] #1387
[ ] #1388

ENGINEERING SUPPLIES

[x] #1421
[x] #1422
[ ] 5P ES-11 Mobile Fuel Canister
[x] #2243

RESTRICTED FIREARMS

[x] #1389
[x] #1390
[ ] #1391

EXPLOSIVES

[x] #1392
[ ] #1393
[ ] #1394
[ ] #1395
[ ] #1396
[ ] #1397
[ ] #1398
[ ] #1399
[ ] #1400

PRIMARY AMMUNITION

[x] #1401
[x] #1402
[x] #1403
[x] #1404
[x] #1405

SIDEARM AMMUNITION

[ ] #1406
[ ] 10P M44 Marksman Speed Loader (.44)
[ ] 5P M4A3 HP Magazine
[ ] 5P M4A3 AP Magazine
[x] 5P VP78 Magazine
[ ] 10P SU-6 Smartpistol Magazine (.45)

ARMORS

[x] #1407
[x] #1408

CLOTHING ITEMS

[x] #1409
[x] #1410
[x] #1411
[x] #1412
[ ] #1413
[ ] #1414
[x] #1415
[ ] #1416
[ ] #1417
[ ] #1418
[ ] #1419
[x] #1420

UTILITIES

[x] #1423
[ ] #1424
[x] #1425
[ ] #1426
[ ] #1427
[x] #1428

BINOCULARS

[ ] 5P Binoculars
[ ] #1429
[ ] #1430

HELMET OPTICS

[ ] #1431
[ ] #1432

PAMPHLETS

[x] #1433
[x] #1434

RADIO KEYS

[x] #1435
[x] #1436
[x] #1437
[x] #1438

these 3 has been fixed

BINOCULARS

[ ]  5P Binoculars
[ ]  10P Range Finder #1429
[ ]  15P Laser Designator #1430


[WIP] Implement entropy search acquisition function

Fixes https://github.com/scikit-optimize/scikit-optimize/issues/115

@jmetzen Would you be able to have a look for sanity? Thanks!

You rock! I'll try to review tomorrow

Thanks! A verification of the code would be great, before benchmarks etc

Thanks for adding this. I will try to check the code on the weekend!

Current coverage is 85.08% (diff: 10.00%)

Merging #304 into master will decrease coverage by 1.91%

@@             master       #304   diff @@
==========================================
  Files            26         26
  Lines          1569       1609    +40
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1365       1369     +4
- Misses          204        240    +36
  Partials          0          0

Powered by Codecov. Last update 2780755...c60cdfe

Needs tests :)

In case the diff gets collapsed in the future.
gpr = GaussianProcessRegressor(n_restarts_optimizer=5)
X = [[1.0], [2.0], [3.0], [4.0], [5.0]]
y = [1.0, 4.0, 9.0, 16.0, 25.0]
gpr.fit(X, y)

eval_X = np.linspace(1.0, 5.0, 30.0).reshape(-1, 1)
_, init_cov = gpr.predict(eval_X, return_cov=True)

new_X = [[1.5], [2.5], [3.5]]
new_y = y + [t**2 for x in new_X for t in x]

all_X = np.vstack((eval_X, new_X))
_, all_cov = gpr.predict(all_X, return_cov=True)
cross_cov = all_cov[-3:, :-3]
delta_cov = np.dot(cross_cov.T, np.dot(np.linalg.inv(all_cov[-3:, -3:]), cross_cov))

X_after = np.vstack((X, new_X))
gpr.fit(X_after, new_y)
_, new_cov = gpr.predict(eval_X, return_cov=True)
act_delta = new_cov - init_cov

act_delta[-2]
array([ 0.        ,  0.00118236,  0.00206068,  0.00254834,  0.00259283,
        0.00218859,  0.00138669,  0.00029841, -0.00091064, -0.00203781,
       -0.00287196, -0.00323024, -0.00299673, -0.00215471, -0.00080388,
        0.00084434,  0.00249582,  0.00382406,  0.00453331,  0.00442178,
        0.00343106,  0.00167007, -0.00059326, -0.00297201, -0.00502493,
       -0.00633262, -0.00657042, -0.0055635 , -0.00331457,  0.        ])
delta_cov[-2]
array([  0.00000000e+00,  -1.18235670e-03,  -2.06067792e-03,
        -2.54833878e-03,  -2.59283482e-03,  -2.18858735e-03,
        -1.38668602e-03,  -2.98406054e-04,   9.10643899e-04,
         2.03780813e-03,   2.87196229e-03,   3.23024283e-03,
         2.99672751e-03,   2.15471226e-03,   8.03883150e-04,
        -8.44338624e-04,  -2.49581620e-03,  -3.82405586e-03,
        -4.53330821e-03,  -4.42177769e-03,  -3.43106330e-03,
        -1.67006787e-03,   5.93257256e-04,   2.97201330e-03,
         5.02492645e-03,   6.33262299e-03,   6.57041884e-03,
         5.56350449e-03,   3.31456744e-03,   6.71512219e-17])

Okay, I think this is wrong. The optimization should be wrt a function sampled from the GP posterior, shouldnit?

No, it is not wrong. Choosing the representer points can be done using any function. Look at the last paragraph in section 2.2 of http://jmlr.csail.mit.edu/papers/volume13/hennig12a/hennig12a.pdf
Sampling from a uniform grid and choosing the point that gives the best acquisition function value is a naive alternative to using advanced techniques to sample directly from the acquisition function.

Okay,
I think this is wrong. The optimization should be wrt a function sampled from the GP posterior, shouldnit?

No, it is not wrong. Choosing the representer points can be done using any function. Look at the last paragraph in section 2.2 of http://jmlr.csail.mit.edu/papers/volume13/hennig12a/hennig12a.pdf

Sampling from a uniform grid and choosing the point that gives the best acquisition function value is a naive alternative to using advanced techniques to sample directly from the acquisition function.

I used effectively Thompson sampling as method for sampling representer points instead of EI and PI. In principle, using any of these is legitimate. One disadvantage of EI and PI is that the only place where stochasticity enters the selection of the representer points is in selecting the trial-points. In contrast, Thompson sampling also adds stochasticity in selecting the representer points from the trial points. This can lead to a more diverse set of representer points (just think what happens if n_trial_points becomes very large - you would select effectively always the same representer point, namely the maximizer of EI/PI).  Thus, I would propose to add Thompson sampling as an alternative to EI/PI here. What do you think?

Okay, I think this is wrong. The optimization should be wrt a function sampled from the GP posterior, > shouldnit?
No, it is not wrong. Choosing the representer points can be done using any function. Look at the last paragraph in section 2.2 of http://jmlr.csail.mit.edu/papers/volume13/hennig12a/hennig12a.pdf

Sampling from a uniform grid and choosing the point that gives the best acquisition function value is a naive alternative to using advanced techniques to sample directly from the acquisition function.

What is still not clear to me is that the representer will eventually all converge towards the same value as n_trial_points tends to infinity.
Maybe I am wrong, but I thought the representer points were instead draw from the distribution of minima, with respect to the functions sampled from the GP posterior. There the distribution would not collapse to a same representer value.
What am I missing?

I agree that the current approach is deterministic and incorrect and the right approach would be to sample from the acquisition function directly. But it it is not necessary that the representer points should be sampled from the minima, it can be sampled from any function that has a strong effect on the entropy change such as EI. In fact it is better to use EI since the representer points sampled from EI take care of the exploitation-exploration tradeoff. I'll change it to follow @jmetzen 's approach and mark MCMC sampling from such functions as TODO for later.
However, I have a question with respect to Thompson sampling. Am I right in thinking that for picking each candidate the game is played from scratch. (i.e the prior updating does not happen?)

I have implemented Thompson sampling as a method to give a distribution of the representer points or the minima of the black-box function. I am running benchmarks to check the state as of now.


Update  argocd-autopilot version

Description
Just update the argocd-autopilot version to 0.2.13
Motivation and Context

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

How Has This Been Tested?
Open Github Codespace:

Are you a GitHub Sponsor (Yes/No?)

[ ] Yes
[x] No

Types of changes

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

Documentation

[x] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[x] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

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

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

Maybe a arkade-bot?


Zauber phlox 3

This branch adds definitions for the following new functions:

iwReverseString
iwReverseList
iwSearchInventory
iwSearchLinkInventory
iwIntRand
iwIntRandRange
iwFrandRange
botSearchBotOutfits

In addition, it adds definitions for the constants IW_MATCH_INCLUDE, OBJECT_RENDER_WEIGHT, OBJECT_HOVER_HEIGHT, OBJECT_BODY_SHAPE_TYPE, OBJECT_LAST_OWNER_ID, and OBJECT_CLICK_ACTION.

Passed code review. Looks good.


CEQ-5476 Manage quarkus-cxf-rt-features-metrics and quarkus-cxf-rt-transports-http-hc5 at community versions Upgrade to cq-plugin 4.1.2

https://issues.redhat.com/browse/CEQ-5476

Ups, I pushed before the 4.1.2 artifacts of the plugin were available on Central

I could not log in to Jenkins for some reason so I pushed some trivial change to restart the CI.

thanks @ppalaga


Website down

Describe the bug
A clear and concise description of what the bug is.
Website down
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

It either was temporary or something on your side The site in currently up and running.


False error "server must run as root, or with --rootless and/or --disable-agent" while K3s runs with root privileges

Environmental Info:
K3s Version:
k3s version v1.28.5+k3s1 (5b2d1271)
go version go1.20.12

Node(s) CPU architecture, OS, and Version:
Linux devenv 6.5.13-orbstack-00121-ge428743e4e98 #1 SMP Wed Dec 27 10:22:46 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration: single-node cluster.
Describe the bug:
K3s fails with the message server must run as root, or with --rootless and/or --disable-agent while it is running with root privileges.
# journalctl -eu k3s.service
...
uid=11111(coder) gid=11111(coder) euid=0(root) egid=0(root) groups=0(root),11111(coder)
...
Jan 21 15:06:47 devenv k3s[4137]: time="2024-01-21T12:06:47Z" level=fatal msg="server must run as root, or with --rootless and/or --disable-agent"
Jan 21 15:06:47 devenv systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
Jan 21 15:06:47 devenv systemd[1]: k3s.service: Failed with result 'exit-code'.

Steps To Reproduce:

Set suid bit to the Systemd binaries: sudo chmod a+s /lib/systemd/systemd*.
Run the container with such Systemd.
systemctl start k3s

The way to fix:
It seems that K3s improperly checks ID of the user running K3s. It checks UID while it should check effective UID (EUID) like OS does. I believe replacing the condition os.Getuid() != 0 with the proper one os.Geteuid() != 0 in the run(...) function will fix the problem.

Set suid bit to the Systemd binaries: sudo chmod a+s /lib/systemd/systemd*.

Why would you do this? Is this something the Linux distro you are using does by default, or is this something you've done manually?

I am going to go out on a limb here and say that making all the systemd binaries setuid root is a huge privilege escalation risk and not something we're particularly interested in enabling.


OS X supports kSecAttrAccessGroup (Only enabled for iOS)

See https://github.com/soffes/sskeychain/pull/109

BTW, I forked and simplified stuff (no string to data conversions) and added a type param so it can be used for other types. https://github.com/gabriel/GHKeychain

Fixed in 927bfe1e2097ed9ac9d7f64a1fd7a828f1c9c246


Introduce "hardhat" assertion mode (PoC)

Preface
This PR resolves #114.
Changes

[x] Introduce hardhat assertion mode.

Remove unused events from Scribble utils library for hardhat assertion mode.
Tweaked logic to respect new mode when emitting assertion failures.

To do

[ ] Introduce adding import "hardhat/console.sol"; in instrumented source units (flat and non-flat).
[ ] Tune tests to verify the correct behavior for instrumented sources in new mode.

Regards.

Codecov Report

Merging #235 (082fd3b) into develop (b61c7c1) will decrease coverage by 0.23%.
The diff coverage is 58.82%.

@@             Coverage Diff             @@
##           develop     #235      +/-   ##
===========================================
- Coverage    87.32%   87.10%   -0.23%
===========================================
  Files           71       71
  Lines         5381     5397      +16
  Branches      1206     1211       +5
===========================================
+ Hits          4699     4701       +2
- Misses         411      421      +10
- Partials       271      275       +4

Impacted Files
Coverage Δ

src/instrumenter/instrument.ts
90.47% <45.83%> (-3.39%)
:arrow_down:

src/instrumenter/utils_library.ts
98.66% <85.71%> (-1.34%)
:arrow_down:

src/bin/scribble.ts
81.25% <100.00%> (ø)

src/instrumenter/instrumentation_context.ts
98.51% <100.00%> (ø)

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


Add Integration tests

Add integration tests. For the most integration testing part, Remotely can be tested on the local machine, since it uses PS Remoting which we can be manipulated as per the requirement.

Re-opening this as still not covered all the scenarios.


Url invalid

I found this bug when I wanted to download songs through my bot

Can you please share a minimal code to replicate the same error?

what node & pkg version are u using?
and what's the url?
I released a new patch that would fix some new URL() parsing by using built in version from NodeJS
could you try 2.6.6 or 3.x ?


Special characters are not displayed correct in interactive console

Steps to reproduce
Run ping on german windows 7 machine in powershell interactive console.
Expected behavior

Run in VS Code with powershell in terminal.
Actual behavior

Run in VS Code with powershell interactive console.
Environment data
VS Code:
Version 1.10.2
Commit 8076a19fdcab7e1fc1707952d652f0bb6c6db331
Date 2017-03-08T14:02:52.799Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0
Env:
Windows 7
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.0.10514.6
WSManStackVersion              3.0
SerializationVersion           <IP_ADDRESS>
CLRVersion                     4.0.30319.42000
BuildVersion                   10.0.10514.6
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3

@Platzer Thanks for your report!
Could you please test in PowerShell console running without VS Code? Also please test with latest release PowerShell Core 6 alfa 17.

@iSazonov I'm sorry i posted the issue to the wrong project!
New issue: https://github.com/PowerShell/vscode-powershell/issues/684