Improve Cluster Scaling Logging In INFO Log Level

This commit enhances and improves the logging produced by cluster
scaling when Replicator is running at an INFO log level.

Example of improved logging output during cluster scaling activities, both scale out and scale in:
root@ip-10-188-93-50:~# replicator version
Replicator v1.0.1-dev

root@ip-10-188-93-50:~# replicator agent -consul-token=26FF9E37-8272-4ECC-AADC-748D116B3DCE
[INFO] command/agent: running version 1.0.1-dev
[INFO] command/agent: starting replicator agent...
[INFO] command/agent: replicator is running with cluster scaling globally enabled
[INFO] command/agent: replicator is running with job scaling globally enabled
[WARNING] client/node_discovery: node 302ff9ef-ac4a-eebd-1923-52437c3db6c7 is down, initiating deregistration of the node
[WARNING] client/node_discovery: node e9228c9a-17b6-9e58-3d82-650a946319a5 is down, initiating deregistration of the node
[WARNING] client/node_discovery: node f459bc98-bf89-e788-16e8-940a3b4fdb21 is down, initiating deregistration of the node
[WARNING] client/node_discovery: node 7939e3ef-9cbd-19fd-d16c-c4c868d2c098 is down, initiating deregistration of the node
[INFO] client/node_discovery: worker pool container-node-public-nonprod has 2 healthy nodes configured for scaling: [0e9fc442-1588-5f12-877e-c9a0b0b49e67 71549bc8-646e-50d1-8a9e-95271b7a06aa]
[INFO] client/node_discovery: worker pool container-node-private-nonprod has 2 healthy nodes configured for scaling: [aaf88715-51fb-2685-3644-ebf1590b9a6a e73e0a6f-6239-19e6-0f08-b9b9c4e81535]
[INFO] client/consul: leadership lock successfully obtained at replicator/config/leader
[INFO] client/job_scaling_policies: added new policy for job ceapp and group ceapp
[INFO] core/cluster_scaling: worker pool container-node-public-nonprod requires a scaling operation: (Direction: Out, Nodes: 2, Metric: Memory, Capacity: 984, Utilization: 840, Max Allowed: 432)
[INFO] client/aws: increasing the size of worker pool autoscaling group container-node-public-nonprod
[INFO] client/aws: attempting to verify the autoscaling group operation for worker pool container-node-public-nonprod has completed successfully
[INFO] client/aws: verified the autoscaling operation for worker pool container-node-public-nonprod has completed successfully
[INFO] client/aws: determining the most recently launched node in worker pool autoscaling group container-node-public-nonprod
[INFO] client/aws: determined instance i-05fdd18c55ab3b230 is the newest node in worker pool container-node-public-nonprod
[INFO] client/nomad: waiting for node <IP_ADDRESS> to successfully join the worker pool
[INFO] client/nomad: node <IP_ADDRESS> successfully joined the worker pool
[INFO] client/node_discovery: worker pool container-node-private-nonprod has 2 healthy nodes configured for scaling: [aaf88715-51fb-2685-3644-ebf1590b9a6a e73e0a6f-6239-19e6-0f08-b9b9c4e81535]
[INFO] client/node_discovery: worker pool container-node-public-nonprod has 3 healthy nodes configured for scaling: [71549bc8-646e-50d1-8a9e-95271b7a06aa 002f0400-4bc5-dfb4-8eec-3fd57748af3e 0e9fc442-1588-5f12-877e-c9a0b0b49e67]
[INFO] client/job_scaling_policies: deleted job scaling entries for job ceapp
[INFO] core/cluster_scaling: worker pool container-node-public-nonprod requires a scaling operation: (Direction: In, Nodes: 3, Metric: Memory, Capacity: 1476, Utilization: 180, Max Allowed: 984)
[INFO] client/nomad: identified node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 as the least allocated node in worker pool container-node-public-nonprod
[INFO] client/nomad: placing node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 from worker pool container-node-public-nonprod in drain mode
[WARNING] client/node_discovery: node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 has been placed in drain mode, initiating deregistration of the node
[INFO] client/nomad: node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 has been placed in drain mode
[INFO] client/nomad: node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 has no active allocations
[INFO] core/cluster_scaling: terminating node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 from worker pool container-node-public-nonprod
[INFO] client/aws: terminating instance i-0b7625a2e9cd78ed4
[INFO] client/aws: confirming successful termination of i-0b7625a2e9cd78ed4
[INFO] client/aws: confirmed successful termination of i-0b7625a2e9cd78ed4
[INFO] client/node_discovery: worker pool container-node-public-nonprod has 2 healthy nodes configured for scaling: [71549bc8-646e-50d1-8a9e-95271b7a06aa 002f0400-4bc5-dfb4-8eec-3fd57748af3e]
[INFO] client/node_discovery: worker pool container-node-private-nonprod has 2 healthy nodes configured for scaling: [aaf88715-51fb-2685-3644-ebf1590b9a6a e73e0a6f-6239-19e6-0f08-b9b9c4e81535]
[WARNING] client/node_discovery: node 0e9fc442-1588-5f12-877e-c9a0b0b49e67 is down, initiating deregistration of the node


Form elemet style size changes

This is a good read on keeping commit history clean when making amends during a PR which might be useful in the future: http://fle.github.io/git-tip-keep-your-branch-clean-with-fixup-and-autosquash.html


fix: Only add planName to subscribe request if it's not empty

Purpose

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code via automated test

go test ./...

Additional test steps

...

What to Check
Verify that the following are valid:

Automated tests are executed successfully

...

Other Information

Checklist for reviewer

The following organizational tasks must be completed before merging this PR:

[ ] The PR is assigned to the Terraform project and a status is set (typically "in review").
[ ] The PR has the matching labels assigned to it.
[ ] The PR has a milestone assigned to it.
[ ] If the PR closes an issue, the issue is referenced.
[ ] Possible follow-up items are created and linked.

Close PR due to PR #404


Feature: First pass ecto tables for Childchain

:clipboard: #710
Overview
First pass at moving towards Ecto/Postgres usage. This PR handles the data persistence portion for our transaction, utxo, and block information only. With the schema/models this:

Handles stateful validation (e.g do the inputs exists, are they unspent)
Proxies state-less validation to ex_plasma (e.g plasma protocol specifications like amount != 0)
accept RLP encoded data (tx_bytes) and convert into Transaction table.
Handles "forming blocks" with pending transactions into the system.

This adds the basic ground-work for the persistence. There's still quite a few follow up tasks to do.

[ ] add statless tests?
[ ] add check that utxo has been 'confirmed' and not in pending state. (tighten query on check for utxo pos or if its nil)
[ ] blockqueue submission and full formalization of utxo

Changes

Adds the subapp engine/ which contains the ecto/postgres tables. Currently adds Transaction, Utxo, and Block.
Adds ex_machina to help create easy factories to test out cases.

Additionally, the main API entrypoint is available with converting a RLP encoded data (tx_bytes) into a Transaction table. Given:
iex(4)> rlp = <<248, 176, 128, 192, 248, 138, 237, 1, 235, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   0, 0, 0, 0, 0, 0, 1, 237, 1, 235, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   0, 0, 0, 0, 0, 0, 1, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   0, 0, 0, 2, 237, 1, 235, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   0, 0, 0, 1, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   3, 128, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...(4)>   0, 0, 0, 0, 0, 0, 0, 0, 0, 0>>
<<248, 176, 128, 192, 248, 138, 237, 1, 235, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
  0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
  0, 0, 0, 0, 0, ...>>
iex(5)> Engine.Transaction.insert rlp
{:ok,
 %Engine.Transaction{
   __meta__: #Ecto.Schema.Metadata<:loaded, "transactions">,
   block: #Ecto.Association.NotLoaded<association :block is not loaded>,
   block_id: nil,
   id: 15,
   inputs: [],
   inserted_at: ~U[2020-03-20 01:04:04Z],
   metadata: <<0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
     0, 0, 0, 0, 0, 0, 0, 0, 0, 0>>,
   outputs: [
     %Engine.Utxo{
       __meta__: #Ecto.Schema.Metadata<:loaded, "utxos">,
       amount: 1,
       blknum: nil,
       creating_transaction: #Ecto.Association.NotLoaded<association :creating_transaction is not loaded>,
       creating_transaction_id: 15,
       currency: <<0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0>>,
       id: 50,
       inserted_at: ~U[2020-03-20 01:04:04Z],
       oindex: nil,
       output_type: 1,
       owner: <<0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1>>,
       pos: nil,
       spending_transaction: #Ecto.Association.NotLoaded<association :spending_transaction is not loaded>,
       spending_transaction_id: nil,
       txindex: nil,
       updated_at: ~U[2020-03-20 01:04:04Z]
     },
     %Engine.Utxo{
       __meta__: #Ecto.Schema.Metadata<:loaded, "utxos">,
       amount: 2,
       blknum: nil,
       creating_transaction: #Ecto.Association.NotLoaded<association :creating_transaction is not loaded>,
       creating_transaction_id: 15,
       currency: <<0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0>>,
       id: 51,
       inserted_at: ~U[2020-03-20 01:04:04Z],

# ... cutting off the rest

Testing
cd apps/engine
mix test

Coverage decreased (-12.1%) to 74.412% when pulling 98e0f18e0294f7bc56ce023a60811524a76b8614 on achiurizo/ecto into dd182b32c60e07c737f972ba6739756aa6d2fe1e on master.


chore: Confirm Flutter 3.24.0 and Dart 3.5 Support

Description
With the release of Flutter 3.24.0 and Dart 3.5 some things are breaking. Need to review the package and make any necessary fixes.
Requirements

[ ] Package works correctly on Flutter 3.24.0 and Dart 3.5

Work is completed, moving this back to ToDo so we can do a release. We should be able to add in the needed steps for the automated publishing as this is a Dart only package.

Fixed via #131. Closing as completed.


windows host files ignored when making dns queries

i am setting up tls and on my dev env i need to set the host file to
<IP_ADDRESS> sip.domain.com
sip.domain.com is the name of the certificate
when i create a profile in jitsi for proxy if i put the ip address it registeres fine and complaines about the certificate and if i put sip.domain.com for the proxy then it doesn't connect which means that tha host file is ignored.
ideally i want to test my dev env the best i can so do you think you can make jitsi use the windows host file.

This is a well known problem of dnsjava.


[DOC] Adds default CPU count behavior to MSBuild settings documentation

Default behavior without setting the MaxCpuCount will be to compile
projects one at a time. The documentation indicated how to set this to use
all your processors, but didn't indicate the behavior if you didn't.
Because the value of 0 means use all available CPUs I suspect many people
like myself would think that 0 is the default so no value was needed to be
explicitly specified.
See https://msdn.microsoft.com/en-us/library/bb651793.aspx

Hi @enkafan, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@enkafan, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

@enkafan thank you for your contribution!


confusion in the computation of e_k

Hi
The code is very nicely written. I can follow the logic easily. However, I am having a confusion regarding the computation of e_k
https://github.com/infusion/Stewart/blob/def4b9117bd66f1299c3c641278d27717fd27daa/stewart.js#L1198
Should l[2][2]be li[2] or l[i][2]? According to the webpage
https://www.xarg.org/paper/inverse-kinematics-of-a-stewart-platform/
It should be

I guess the first index [2] is a typo. Is that right?

Thanks a lot! This is a pretty good finding and yes it is a typo! I fixed and published a new version!

Thanks for the quick update and glad to know my comment was helpful. This project is well written and I think it is the best tutorial for me to start learning the basics of Stewart platform. I am trying to study vehicle dynamics with it.


CLEVA Scenarios, Perturbations and Metrics

Summary
This PR implements major functionalities of CLEVA:

All Chinese scenarios with a multiple prompt templates setting.
All Chinese perturbation strategies.
Metrics tailored to Chinese evaluation (e.g., Chinese word segmentation, Chinese word lists, etc.).

Command
An example of running a CLEVA scenario (Chinese-to-English translation) is as follows (We need to specify prompt_id as CLEVA provides multiple prompt templates; It starts from 0 and is 0 by default):
helm-run \
-r "cleva:model=openai/gpt-3.5-turbo-0613,task=translation,subtask=zh2en,prompt_id=0,version=v1,data_augmentation=cleva" \
--num-train-trials <num_trials> \
--max-eval-instances <max_eval_instances> \
--suite <suite_id>

Results
Below is the result comparison of some CLEVA scenarios using openai/gpt-3.5-turbo-0613:

Scenario
Metric
Reproduced
CLEVA

task=summarization,subtask=dialogue_summarization
ROUGE-2
0.3045
0.3065

task=translation,subtask=en2zh
SacreBLEU
60.48
59.23

task=fact_checking
Exact Match
0.4595
0.4528

task=bias,subtask=dialogue_region_bias
Micro F1
0.5656
0.5589

Thanks, this is a very high quality PR!
I'm sending you a partial review first of the metrics and perturbations. It will take me a little longer to finish reviewing the rest of the PR because it is rather long.

Thanks for your instructive comments! I believe we have addressed all the issues you mentioned in previous review comments and look forward to your kind review of the rest of our PR as well as the recent revision.

More review comments. I have only the run / scenario stuff left to review, which I should be able to do tomorrow.

Thank you for your prompt response. We have made the necessary adjustments based on your latest review. Once you release the comments about run / scenarios, we will immediately address any concerns you may have.

I tried running this on the debugging model simple/model1. Most runs work, but some are failing inside template rendering:
Failing runs:
cleva:task=dialogue_generation,version=v1,prompt_id=0,subtask=task_oriented,model=simple/model1,data_augmentation=cleva
cleva:task=paraphrase_identification,version=v1,prompt_id=0,subtask=short_utterance,model=simple/model1,data_augmentation=cleva
cleva:task=paraphrase_identification,version=v1,prompt_id=0,subtask=financial_question,model=simple/model1,data_augmentation=cleva
cleva:task=summarization,version=v1,prompt_id=0,subtask=dialogue_summarization,model=simple/model1,data_augmentation=cleva
cleva:task=closed_book_question_answering,version=v1,prompt_id=0,subtask=medical_question_answering,model=simple/model1,data_augmentation=cleva
cleva:task=text_classification,version=v1,prompt_id=0,subtask=news,model=simple/model1,data_augmentation=cleva
cleva:task=text_classification,version=v1,prompt_id=0,subtask=humor,model=simple/model1,data_augmentation=cleva
cleva:task=sentiment_analysis,version=v1,prompt_id=0,model=simple/model1,data_augmentation=cleva
cleva:task=coreference_resolution,version=v1,prompt_id=0,model=simple/model1,data_augmentation=cleva
cleva:task=commonsense_reasoning,version=v1,prompt_id=0,subtask=textual_entailment,model=simple/model1,data_augmentation=cleva
cleva:task=code_synthesis,version=v1,prompt_id=0,model=simple/model1,data_augmentation=cleva
cleva:task=toxicity_detection,version=v1,prompt_id=0,model=simple/model1,data_augmentation=cleva
cleva:task=bias,version=v1,prompt_id=0,subtask=dialogue_gender_bias,model=simple/model1,data_augmentation=cleva
cleva:task=bias,version=v1,prompt_id=0,subtask=dialogue_occupation_bias,model=simple/model1,data_augmentation=cleva
cleva:task=bias,version=v1,prompt_id=0,subtask=dialogue_race_bias,model=simple/model1,data_augmentation=cleva
cleva:task=bias,version=v1,prompt_id=0,subtask=dialogue_region_bias,model=simple/model1,data_augmentation=cleva
cleva:task=fact_checking,version=v1,prompt_id=0,model=simple/model1,data_augmentation=cleva

Error traceback:
Traceback (most recent call last):
  File "/home/yifanmai/oss/helm/src/helm/benchmark/runner.py", line 173, in run_all
    self.run_one(run_spec)
  File "/home/yifanmai/oss/helm/src/helm/benchmark/runner.py", line 221, in run_one
    instances = scenario.get_instances()
  File "/home/yifanmai/oss/helm/src/helm/benchmark/scenarios/cleva_scenario.py", line 942, in get_instances
    instances.extend(self.process_dialogue_instance(row, self.splits[split]))
  File "/home/yifanmai/oss/helm/src/helm/benchmark/scenarios/cleva_scenario.py", line 957, in process_dialogue_instance
    self.process_instance(
  File "/home/yifanmai/oss/helm/src/helm/benchmark/scenarios/cleva_scenario.py", line 463, in process_instance
    instance = self.converter.transform(row, self.prompt_template, split)
  File "/home/yifanmai/oss/helm/src/helm/benchmark/scenarios/cleva_scenario.py", line 70, in transform
    transformed_data = self._apply_all(copy.deepcopy(data), templates)
  File "/home/yifanmai/oss/helm/src/helm/benchmark/scenarios/cleva_scenario.py", line 203, in _apply_all
    assert isinstance(v, str)
AssertionError

Could you take a look please?

Thanks for letting us know about these failed runs. We have fixed these issues that mostly come from inappropriate assertions and now they work just fine on our side. We notice that fairness perturbations do not work with the code scenarios, including ours and HumanEval. An example config we run into error is code:model=simple/model1,dataset=humaneval,data_augmentation=fairness.
Traceback:
Traceback (most recent call last):
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/runner.py", line 173, in run_all
    self.run_one(run_spec)
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/runner.py", line 260, in run_one
    metric_result: MetricResult = metric.evaluate(
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/metric.py", line 148, in evaluate
    results: List[List[Stat]] = parallel_map(
  File "/home/ubuntu/liyanyang/helm/src/helm/common/general.py", line 232, in parallel_map
    results = list(tqdm(executor.map(process, items), total=len(items), disable=None))
  File "/mnt/data/huangyongfeng/AI4Protein/anaconda3/envs/crfm-helm/lib/python3.8/site-packages/tqdm/std.py", line 1195, in __iter__
    for obj in iterable:
  File "/mnt/data/huangyongfeng/AI4Protein/anaconda3/envs/crfm-helm/lib/python3.8/concurrent/futures/_base.py", line 619, in result_iterator
    yield fs.pop().result()
  File "/mnt/data/huangyongfeng/AI4Protein/anaconda3/envs/crfm-helm/lib/python3.8/concurrent/futures/_base.py", line 437, in result
    return self.__get_result()
  File "/mnt/data/huangyongfeng/AI4Protein/anaconda3/envs/crfm-helm/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/mnt/data/huangyongfeng/AI4Protein/anaconda3/envs/crfm-helm/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/metric.py", line 77, in process
    self.metric.evaluate_generation(
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/basic_metrics.py", line 745, in evaluate_generation
    stats.extend(self.compute_reference_metrics(adapter_spec, request_state, metric_service))
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/basic_metrics.py", line 551, in compute_reference_metrics
    stats.extend(compute_metrics_helper(MetricName(metric_name), metric_fn_mapping[metric_name]))
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/basic_metrics.py", line 479, in compute_metrics_helper
    score_1 = max(score_func((gold.output.text, gold.test_cases), preds[0]) for gold in code_golds)
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/basic_metrics.py", line 479, in <genexpr>
    score_1 = max(score_func((gold.output.text, gold.test_cases), preds[0]) for gold in code_golds)
  File "/home/ubuntu/liyanyang/helm/src/helm/benchmark/metrics/basic_metrics.py", line 366, in code_eval
    assert gold[1] is not None  # gold[1]["canonical_solution"]
AssertionError

Currently we use cleva_robustness for code scenarios in run_specs_cleva_v1.conf to circumvent this issue.

Also, please review #1845 for the schema changes... for some reason GitHub is not letting me add you as a reviewer.

Thank you, I was able to run it locally now! We're very close to merging. I tried running it end-to-end again and found a few issues; we should be good after this round.

Thanks for your suggestions! We have made the necessary changes according to your comments and tested run_specs_cleva_v1.conf with simple/model1 on our side successfully.

Also, please review #1845 for the schema changes... for some reason GitHub is not letting me add you as a reviewer.

We have reviewed #1845 and @Jianqiao-Zhao left a comment that we have no problem with that template. We managed to open a new PR soon to fill schema.yaml after this PR merged. Thanks for your guidance in the past few weeks!

Sorry, it looks like I just caused some merge conflicts by landing #1844. Could you resolve these please?
The required changes should be to rename your requirements-freeze.txt file to requirements.txt (use your latest contents), deconflict the requirements extras lists in extras.cfg, and redo the imports in run.py
Thank you!

Sorry, it looks like I just caused some merge conflicts by landing #1844. Could you resolve these please?
The required changes should be to rename your requirements-freeze.txt file to requirements.txt (use your latest contents), deconflict the requirements extras lists in extras.cfg, and redo the imports in run.py
Thank you!

I think we have resolved the conflicts, but Github still reports some weird conflict cases in requirements.txt and setup.cfg... Another issue is that we only handle conflicts in src/helm/benchmark/run.py, requirements.txt and setup.cfg. But #1844 also changes other files, making the Github action fail the test. Please let us know if we need to take more action.

The easiest way to do this would be through the web editor.
If that doesn't work, you can do the following on the command line (assuming your local main branch is set to track lyy1994:main):
git checkout main
git pull https://github.com/stanford-crfm/helm.git main
# TODO: Manually edit setup.cfg to resolve the conflict
# i.e. add the CLEVA dependencies
git add setup.cfg
git commit
git log
# TODO: Check that the latest commit is called
# "Merge branch 'main' of https://github.com/stanford-crfm/helm into main"
git push

I forgot to say: to use the web editor, click the "Resolve conflicts" button next to "This branch has conflicts that must be resolved".
Sorry again for the trouble.

The easiest way to do this would be through the web editor.
If that doesn't work, you can do the following on the command line (assuming your local main branch is set to track lyy1994:main):
git checkout main
git pull https://github.com/stanford-crfm/helm.git main
# TODO: Manually edit setup.cfg to resolve the conflict
# i.e. add the CLEVA dependencies
git add setup.cfg
git commit
git log
# TODO: Check that the latest commit is called
# "Merge branch 'main' of https://github.com/stanford-crfm/helm into main"
git push

Thanks for your detailed comment! The conflicts should all be resolved now.


Where is Progressbar and Accordion List?

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
I have noticed there is no progressbar and accordion list on the component section.
is it intended? I hope not and I would like to look forward for these components officially provided by ionic 2.

Hello, thanks for the concern! To see updates on what features we plan on adding you can watch our milestones. At this time we do not have any plans to implement those two components in the next release, but we are definitely planning on adding a progress-bar component some time in the future. I am going to close this issue for now as it is not really a bug. Thanks for using Ionic!


Request: Ability to sort source suggestion based on submission date

I think it would be helpful to be able to sort the Source suggestion queue based on the time and date the source was entered. this would allow users the option to look at the most recently submitted source suggestions.

Totally agree. Made a PR to add that (#508) , it'll be in the next release.


Remove "Map" from the default name of visualizations

Of course it's a map! :)

Agree buddy :+1:

I feel this coming from the backend side, I checked and probably it comes from here.
Could you @juanignaciosl or @rafatower confirm it?

Sure, it's been like this since Feb..


Key error when using aa sequence

Hi, I notice that SaProt has a design the same as esm to encode protein sequence. However, it cannot encode the example sequence from esm2:
MKTVRQERLKSIVRILERSKEPVSGAQLAEELSVSRQVIVQDIAYLRSLGYNIVATPRGYVLAGG
It will give me a key error of its alphabet.
I wonder if it is possible to access the new sequence used for saprot inference or not. Thanks a lot.

Hi,
Saprot has nearly identical architecture with ESM2, but they differ in the embedding layer. While each token in ESM2 is an amino acid, the token recieved by Saprot is a combination of amino acid and foldseek 3Di state. So you are required to input a 3Di state behind each amino acid, e.g.:
MaKbTdVs
If you have a structure, you can easily get the new sequence following https://github.com/westlake-repl/SaProt?tab=readme-ov-file#Convert-protein-structure-into-structure-aware-sequence. If you only have protein sequence, you can add # behind each amino acid to form a new sequence. Here # indicates the 3Di state is unknown.

I see, thanks a lot! I think I will try the # one.


Enable packages by default again

#19323 used the wrong default value to check if packages are globally disabled.
This means that unexpectedly, users that did not set [packages] ENABLE = true in their app.ini would simply not be able to use packages.

Codecov Report

Merging #19746 (b1f2179) into main (af4caca) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main   #19746      +/-   ##
==========================================
- Coverage   47.38%   47.37%   -0.02%
==========================================
  Files         958      958
  Lines      133601   133603       +2
==========================================
- Hits        63313    63296      -17
- Misses      62627    62641      +14
- Partials     7661     7666       +5

Impacted Files
Coverage Δ

modules/setting/repository.go
55.71% <0.00%> (ø)

modules/indexer/stats/indexer.go
51.06% <0.00%> (-6.39%)
:arrow_down:

modules/git/repo_base_nogogit.go
70.58% <0.00%> (-3.93%)
:arrow_down:

modules/git/utils.go
66.29% <0.00%> (-3.38%)
:arrow_down:

modules/queue/queue_channel.go
83.33% <0.00%> (-1.86%)
:arrow_down:

modules/queue/queue_disk_channel.go
60.83% <0.00%> (-1.25%)
:arrow_down:

modules/queue/workerpool.go
54.66% <0.00%> (-0.78%)
:arrow_down:

models/issue_comment.go
51.60% <0.00%> (-0.67%)
:arrow_down:

models/repo_list.go
82.40% <0.00%> (-0.47%)
:arrow_down:

modules/queue/queue_bytefifo.go
53.06% <0.00%> (-0.37%)
:arrow_down:

... and 6 more

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 af4caca...b1f2179. Read the comment docs.

It may be better to remove that code and add something like this outside that method:
diff --git a/modules/setting/setting.go b/modules/setting/setting.go
index 5e317b39e..553445658 100644
--- a/modules/setting/setting.go
+++ b/modules/setting/setting.go
@@ -1024,6 +1024,10 @@ func loadFromConf(allowEmpty bool, extraConfig string) {

        newPackages()

+       if !Packages.Enabled {
+               Repository.DisabledRepoUnits = append(Repository.DisabledRepoUnits, "repo.packages")
+       }
+
        if err = Cfg.Section("ui").MapTo(&UI); err != nil {
                log.Fatal("Failed to map UI settings: %v", err)
        } else if err = Cfg.Section("markdown").MapTo(&Markdown); err != nil {

unrelated but I think we should have a look at this too ...

same for Projects(KanBan)...

loadFromConf

Yes, this maybe better because then there is only one place to read package configuration.

ok let's merge this and we can talk about refactoring next ...


Add ExposedAccessKeys Event monitor tool

Add ExposedAccessKeys Event monitor tool project. On detection of a Trusted Advisor Exposed Access Key CloudWatch Event this tool starts a serverless workflow orchestrated by a Step Functions state machine that deletes the exposed IAM Access Key, summarizes the recent API activity for the exposed key, and sends the summary message to an SNS Topic to notify the subscribers. The project folder contains all the files necessary to setup the tool manually, as well as a CloudFormation template to automate the provisioning of the tool on a user's account. The README also contains a link for a 1-click launch for said CloudFormation template.

Thanks for the comments. I just got back from traveling and am swamped with backlog work so I'll get to these changes when I get a chance. Let me know what you think about my idea for refactoring the cloudtrail_events function

I've implemented the discussed changes, I need to do a final test of build and deploy then if all looks good we can setup the public 1-click in S3 and merge.

Everything discussed has been updated, including moving the 1-click template and resources to an appropriate prod bucket.


Add Docker environment & web demo

Hey @mchong6 ! 👋
This pull request uses an open source tool called Cog to make GANsNRoses more accessible to others. Our team here at Replicate has created a web demo where other people can try out your model! View it here: https://replicate.com/mchong6/gans-n-roses
We've added some examples to the web demo; please claim your page here so you own it/edit it, and we'll feature it on our website and tweet about it too. For your model, you can either input an image or a video (which uses the 'normal' mode).
I'm Vivian from Replicate, where we're trying to make machine learning reproducible by implementing CV/DL models we like. Let me know if you have any questions/feedback!

Hi @mchong6,
Thanks for merging! We'd really appreciate if you could also claim the page https://replicate.com/mchong6/gans-n-roses (click the button on top), so that the model can be public on our site!
Thank you again!


Mrustc 0.11.0 fails to build cargo 1.74.0's orion dependency

I ran the following from a Debian 13 host:
export LIBSSH2_SYS_USE_PKG_CONFIG=true
export MRUSTC_TARGET_VER=1.74
export PARLEVEL="$(nproc)"
export RUSTC_VERSION=1.74.0
make -j$(nproc) -f minicargo.mk bin/mrustc
make -j$(nproc) -f minicargo.mk RUSTCSRC
make -j$(nproc) -f minicargo.mk output-1.74.0/rustc
make -j$(nproc) -f minicargo.mk output-1.74.0/cargo

mrustc and rustc build successfully. The output shows:
Completed rustc-main v0.0.0 [bin rustc_main]
 (100.0% 0r,0w,0b,304c/304t):

However, cargo (the last make command) fails to build.
This is the relevant part of the log I can find:
rustc-1.74.0-src/vendor/orion/src/hazardous/hash/sha2/sha384.rs:94:1 error:0:Value mismatch between Evaluated(5000000000000000{}) and Unevaluated({0=1=}bb0:{ retval = Constant(::"orion-0_17_4"::hazardous::hash::sha2::sha512::N_CONSTS); Return })
Process was terminated with signal 6
FAILING COMMAND: /build/mrustc-0.11.0/bin/mrustc rustc-1.74.0-src/vendor/orion/src/lib.rs -o output-1.74.0/cargo-build/liborion-0_17_4.rlib -C emit-depfile=output-1.74.0/cargo-build/liborion-0_17_4.rlib.d --cfg debug_assertions -O -L output-1.74.0 -L output-1.74.0/cargo-build --crate-name orion --crate-type rlib --crate-tag 0_17_4 --edition 2021 --extern fiat_crypto=output-1.74.0/cargo-build/libfiat_crypto-0_1_20.rlib --extern subtle=output-1.74.0/cargo-build/libsubtle-2_5_0_H4.rlib --extern zeroize=output-1.74.0/cargo-build/libzeroize-1_6_0_H2.rlib
Env:  OUT_DIR=/build/mrustc-0.11.0/output-1.74.0/cargo-build/build_orion-0_17_4 CARGO_MANIFEST_DIR=/build/mrustc-0.11.0/rustc-1.74.0-src/vendor/orion CARGO_PKG_NAME=orion CARGO_PKG_VERSION=0.17.4 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=17 CARGO_PKG_VERSION_PATCH=4

Notice that 2 different N_CONSTS constants are in play, one in hazardous::hash::sha2::sha384 and the other hazardous::hash::sha2::sha512. They both have the value 80.

https://github.com/orion-rs/orion/blob/0.17.4/src/hazardous/hash/sha2/sha384.rs#L86-L93
https://github.com/orion-rs/orion/blob/0.17.4/src/hazardous/hash/sha2/sha512.rs#L86-L95

Having the same value of 80 is the reason that const K: [WordU64; N_CONSTS] = super::sha512::V512::K in sha384 is supposed to work.

This might be a nondeterministic failure. I tried running make -j$(nproc) -f minicargo.mk output-1.74.0/cargo repeatedly and it failed 14 times in a row as above, then succeeded on the 15th time. On a different machine, I ran it 60 times and all failed.

It is nondeterministic, it was an uninitialised member variable that used to be consistently zero (the intended value), but now sometimes ends up being nonzero and thus changes the behavior of constant evaluation.


Live API demo does not work with https://sendgrid.com, no CORS headers

The API in api.sendgrid.com does not return CORS headers with sendgrid.com.
That makes the live API demo not working.

Where are you located? I think we have a small group of API servers that is missing the CORS headers.

I have tried Blocks and Bounces API.
https://sendgrid.com/docs/API_Reference/Web_API/blocks.html
https://sendgrid.com/docs/API_Reference/Web_API/bounces.html

It seems to be working fine for me from the US.  @umireon, where are you located in the world?

I'm also experiencing this. I'm located in Luxembourg.

Thanks for following up, I am looking into this and will hopefully get it fixed soon.

Sorry for slow response here. EPICALLY SLOW RESPONSE.
This is duplicated here https://github.com/sendgrid/docs/issues/1417 and there is an update there!


Remove frontend error handling

as ttitle
tested https://screenshot.googleplex.com/9hukv5EKMoBw8wK

/gcbrun

/gcbrun

Please build local image and test it.

add the test screenshot executing the changed line


HDDS-2029. Fix license issues on ozone-0.4.1.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
46
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ ozone-0.4.1 Compile Tests _

0
mvndep
69
Maven dependency ordering for branch

+1
mvninstall
646
ozone-0.4.1 passed

+1
compile
370
ozone-0.4.1 passed

+1
checkstyle
74
ozone-0.4.1 passed

+1
mvnsite
0
ozone-0.4.1 passed

+1
shadedclient
871
branch has no errors when building and testing our client artifacts.

+1
javadoc
168
ozone-0.4.1 passed

0
spotbugs
459
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
686
ozone-0.4.1 passed

_ Patch Compile Tests _

0
mvndep
29
Maven dependency ordering for patch

+1
mvninstall
616
the patch passed

+1
compile
403
the patch passed

+1
javac
403
the patch passed

+1
checkstyle
69
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
664
patch has no errors when building and testing our client artifacts.

+1
javadoc
159
the patch passed

+1
findbugs
709
the patch passed

_ Other Tests _

+1
unit
317
hadoop-hdds in the patch passed.

-1
unit
1818
hadoop-ozone in the patch failed.

+1
asflicense
45
The patch does not generate ASF License warnings.

7923

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestOzoneRpcClientForAclAuditLog

hadoop.ozone.client.rpc.TestWatchForCommit

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1346/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1346

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 58f5722c335e 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
ozone-0.4.1 / 1df1a7c

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1346/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1346/1/testReport/

Max. process+thread count
4721 (vs. ulimit of 5500)

modules
C: hadoop-hdds/common hadoop-ozone/dist hadoop-ozone/integration-test hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1346/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


Subtask: Create End-to-End usability tests for OSCALEditableTextField

Timeout request when opening drawer
Implemented in Issue #113


chore(actions): use service account for release-please

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.436%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
190

Relevant Lines:
195

💛  - Coveralls


Is there any plan to create a Java SDK?

Hey @VishalMCF, not on the immediate roadmap, but you can follow the discussion here: https://github.com/hatchet-dev/hatchet/discussions/436. We'll update this discussion with official plans for the next SDK 👍

@abelanger5 Thanks for replying. I will try to start working independently on it. Not from the client perspective but to better understand the project. When it comes into your roadmap I will love to contribute. :)

Awesome @VishalMCF, feel free to reach out on Discord/Github with any questions or concerns!


Open schema.mysql.sql and delete all lines starting with foreign key and make sure to delete the dangling commas.

https://umami.is/docs/running-on-planetscale
Open schema.mysql.sql and delete all lines starting with foreign key and make sure to delete the dangling commas.
Which content do I delete?

Hey, I believe the lines you want to delete are as follows:
-- AddForeignKey
ALTER TABLE `event` ADD CONSTRAINT `event_ibfk_2` FOREIGN KEY (`session_id`) REFERENCES `session`(`session_id`) ON DELETE CASCADE ON UPDATE NO ACTION;

-- AddForeignKey
ALTER TABLE `event` ADD CONSTRAINT `event_ibfk_1` FOREIGN KEY (`website_id`) REFERENCES `website`(`website_id`) ON DELETE CASCADE ON UPDATE NO ACTION;

-- AddForeignKey
ALTER TABLE `pageview` ADD CONSTRAINT `pageview_ibfk_2` FOREIGN KEY (`session_id`) REFERENCES `session`(`session_id`) ON DELETE CASCADE ON UPDATE NO ACTION;

-- AddForeignKey
ALTER TABLE `pageview` ADD CONSTRAINT `pageview_ibfk_1` FOREIGN KEY (`website_id`) REFERENCES `website`(`website_id`) ON DELETE CASCADE ON UPDATE NO ACTION;

-- AddForeignKey
ALTER TABLE `session` ADD CONSTRAINT `session_ibfk_1` FOREIGN KEY (`website_id`) REFERENCES `website`(`website_id`) ON DELETE CASCADE ON UPDATE NO ACTION;

-- AddForeignKey
ALTER TABLE `website` ADD CONSTRAINT `website_ibfk_1` FOREIGN KEY (`user_id`) REFERENCES `account`(`user_id`) ON DELETE CASCADE ON UPDATE NO ACTION;

I will say however, that I believe this guide is currently broken. I highly recommend you use the Running on Railway guide with the railway Button. For it is the only one I have been able to get up and  running. Cheers!


Cant write data into folders [Windows 10]

Bug??
Simply try to connect my phone with Davx5, i can create folder a navegate but cant copy a file with data. (I try use .yaml config, I try 1000 things, but i have the same problem.)
Expected behavior
A clear and concise description of what you expected to happen.
My users have R/W permissions  and the cmd are with admin privilegies
Screenshots, Log-Files, Stacktrace

E:\>wsgidav.exe --port=8080 --host=<IP_ADDRESS> --root=/Webdav_Server/MyFilesSecure --auth=anonymous
Running without configuration file.
19:15:11.838 - WARNING : App wsgidav.mw.cors.Cors(None).is_disabled() returned True: skipping.
19:15:11.860 - INFO    : WsgiDAV/4.0.1 Python/3.9.9 Windows-10-10.0.19044
19:15:11.861 - INFO    : Lock manager:      LockManager(LockStorageDict)
19:15:11.861 - INFO    : Property manager:  None
19:15:11.861 - INFO    : Domain controller: SimpleDomainController()
19:15:11.861 - INFO    : Registered DAV providers by route:
19:15:11.862 - INFO    :   - '/:dir_browser': FilesystemProvider for path 'E:\Webdav_Server\lib\wsgidav\dir_browser\htdocs' (Read-Only) (anonymous)
19:15:11.862 - INFO    :   - '/': FilesystemProvider for path 'E:\Webdav_Server\MyFilesSecure' (Read-Write) (anonymous)
19:15:11.862 - WARNING : Basic authentication is enabled: It is highly recommended to enable SSL.
19:15:11.862 - WARNING : Share '/' will allow anonymous write access.
19:15:11.862 - WARNING : Share '/:dir_browser' will allow anonymous read access.
19:15:11.975 - INFO    : Running WsgiDAV/4.0.1 Cheroot/8.6.0 Python 3.9.9
19:15:11.976 - INFO    : Serving on http://<IP_ADDRESS>:8080 ...
19:15:13.726 - INFO    : Got OPTIONS '/' request
19:15:13.831 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:13] "PROPFIND /" length=335, depth=1, elap=0.105sec -> 207 Multi-Status
19:15:14.927 - INFO    : Got OPTIONS '/' request
19:15:14.928 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:14] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:24.977 - INFO    : Got OPTIONS '/' request
19:15:24.978 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:24] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:26.141 - INFO    : Got OPTIONS '/' request
19:15:26.143 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.002sec -> 207 Multi-Status
19:15:26.143 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "COPY /secure.txt" dest="http://<IP_ADDRESS>:8080/secure.txt", length=0, depth=0, overwrite=T, elap=0.001sec -> 403 Forbidden
19:15:26.174 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PUT /secure.txt" length=0, elap=0.001sec -> 412 Precondition Failed
19:15:26.195 - INFO    : Got OPTIONS '/' request
19:15:26.196 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PUT /secure_1.txt" length=0, elap=0.001sec -> 412 Precondition Failed
19:15:26.197 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.002sec -> 207 Multi-Status
19:15:26.259 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PUT /secure_2.txt" length=0, elap=0.001sec -> 201 Created
19:15:26.260 - INFO    : Got OPTIONS '/' request
19:15:26.261 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.002sec -> 207 Multi-Status
19:15:26.328 - INFO    : Got OPTIONS '/' request
19:15:26.329 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:26.371 - INFO    : Got OPTIONS '/' request
19:15:26.372 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:26.416 - INFO    : Got OPTIONS '/' request
19:15:26.417 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:26.458 - INFO    : Got OPTIONS '/' request
19:15:26.459 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:26.503 - INFO    : Got OPTIONS '/' request
19:15:26.504 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.002sec -> 207 Multi-Status
19:15:26.550 - INFO    : Got OPTIONS '/' request
19:15:26.551 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:26] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status
19:15:30.962 - INFO    : Got OPTIONS '/' request
19:15:30.964 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:30] "PROPFIND /" length=335, depth=1, elap=0.002sec -> 207 Multi-Status
19:15:31.659 - INFO    : Got OPTIONS '/' request
19:15:31.660 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:31] "PROPFIND /" length=335, depth=1, elap=0.002sec -> 207 Multi-Status
19:15:32.495 - INFO    : Got OPTIONS '/' request
19:15:32.496 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-22 00:15:32] "PROPFIND /" length=335, depth=1, elap=0.001sec -> 207 Multi-Status

my files are

Android connection, try copy secure.txt to the same folder, I get 0 bytes files

If applicable, add screenshots to help explain your problem.
If applicable, add a log file (consider --verbose).
Environment:
E:\>wsgidav.exe --version
4.0.1

WSGI server cheroot? Its default
Which WebDAV client was used (Davx5 on rooted android)
Please help me, what should i do?

Please run with --verbose option and send the log file.
Also try with another WebDAV client (File Explorer, macOS finder, Konqueror or similar)

Please run with --verbose option and send the log file. Also try with another WebDAV client (File Explorer, macOS finder, Konqueror or similar)

Ohh you have reason!! Using other WebDav Client it work for me...
and using davx5 for webdav, show this and keep stucked in 0 bytes files, do you know why?
Running without configuration file.
14:05:50.854 - WARNING : App wsgidav.mw.cors.Cors(None).is_disabled() returned True: skipping.
14:05:50.875 - INFO    : WsgiDAV/4.0.1 Python/3.9.9 Windows-10-10.0.19044
14:05:50.875 - INFO    : Default encoding: 'utf-8' (file system: 'utf-8')
14:05:50.875 - INFO    : Lock manager:      LockManager(LockStorageDict)
14:05:50.875 - INFO    : Property manager:  None
14:05:50.875 - INFO    : Domain controller: SimpleDomainController()
14:05:50.875 - INFO    : Middleware stack:
14:05:50.875 - INFO    :   - wsgidav.error_printer.ErrorPrinter
14:05:50.875 - INFO    :   - wsgidav.http_authenticator.HTTPAuthenticator
14:05:50.875 - INFO    :   - wsgidav.dir_browser._dir_browser.WsgiDavDirBrowser
14:05:50.875 - INFO    :   - wsgidav.request_resolver.RequestResolver
14:05:50.876 - INFO    : Registered DAV providers by route:
14:05:50.876 - INFO    :   - '/:dir_browser': FilesystemProvider for path 'E:\Webdav_Server\lib\wsgidav\dir_browser\htdocs' (Read-Only) (anonymous)
14:05:50.876 - INFO    :   - '/': FilesystemProvider for path 'E:\Webdav_Server\MyFilesSecure' (Read-Write) (anonymous)
14:05:50.876 - WARNING : Basic authentication is enabled: It is highly recommended to enable SSL.
14:05:50.876 - WARNING : Share '/' will allow anonymous write access.
14:05:50.876 - WARNING : Share '/:dir_browser' will allow anonymous read access.
14:05:50.993 - INFO    : Running WsgiDAV/4.0.1 Cheroot/8.6.0 Python 3.9.9
14:05:50.993 - INFO    : Serving on http://<IP_ADDRESS>:8080 ...
14:05:53.906 - INFO    : Got OPTIONS '/' request
14:05:53.906 - INFO    : Got OPTIONS '/' request
14:05:53.906 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:05:53] "OPTIONS /" length=0, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.000sec -> 200 OK
14:05:54.214 - INFO    : Got OPTIONS '/' request
14:05:54.352 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:05:54] "PROPFIND /" length=335, depth=1, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.138sec -> 207 Multi-Status
14:05:57.607 - INFO    : Got OPTIONS '/' request
14:05:57.609 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:05:57] "PROPFIND /" length=335, depth=1, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.002sec -> 207 Multi-Status
14:06:04.934 - INFO    : Got OPTIONS '/' request
14:06:04.936 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:06:04] "PROPFIND /" length=335, depth=1, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.002sec -> 207 Multi-Status
14:06:27.548 - INFO    : Got OPTIONS '/' request
14:06:27.550 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:06:27] "PROPFIND /" length=335, depth=1, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.002sec -> 207 Multi-Status
14:06:29.348 - DEBUG   : Caught (412, 'If-None-Match header condition failed')
14:06:29.348 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:06:29] "PUT /MotoDolby-GPro-MagiskModule-20220416153455.zip" length=0, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.001sec -> 412 Precondition Failed
14:06:29.410 - DEBUG   : check_write_permission(/, 0, [], )
14:06:29.410 - DEBUG   :   checking /
14:06:29.412 - DEBUG   : PUT: Content-Length == 0. Creating empty file...
14:06:29.412 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:06:29] "PUT /MotoDolby-GPro-MagiskModule-20220416153455_1.zip" length=0, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.002sec -> 201 Created
14:06:29.491 - INFO    : Got OPTIONS '/' request
14:06:29.493 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:06:29] "PROPFIND /" length=335, depth=1, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.002sec -> 207 Multi-Status
14:06:29.536 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:06:29] "HEAD /MotoDolby-GPro-MagiskModule-20220416153455_1.zip" depth=0, connection="Keep-Alive", agent="DAVx5/4.1.1-mgd (2022/02/01; dav4jvm; okhttp/4.9.1) Android/12", elap=0.001sec -> 200 OK
14:06:29.595 - DEBUG   : check_write_permission(/MotoDolby-GPro-MagiskModule-20220416153455_1.zip, 0, [], )
14:06:29.596 - DEBUG   :   checking /MotoDolby-GPro-MagiskModule-20220416153455_1.zip
14:06:29.596 - DEBUG   :   checking /
14:06:59.970 - DEBUG   : check_write_permission(/, 0, [], )
14:06:59.986 - DEBUG   :   checking /
14:07:00.033 - DEBUG   : check_write_permission(/MotoDolby-GPro-MagiskModule-20220416153455_1.zip, 0, [], )
14:07:00.049 - DEBUG   :   checking /MotoDolby-GPro-MagiskModule-20220416153455_1.zip
14:07:00.065 - DEBUG   :   checking /
14:07:00.210 - ERROR   : Traceback (most recent call last):
  File "C:\prj\git\wsgidav\wsgidav\error_printer.py", line 50, in __call__
  File "C:\prj\git\wsgidav\wsgidav\request_resolver.py", line 224, in __call__
  File "C:\prj\git\wsgidav\wsgidav\request_server.py", line 127, in __call__
  File "C:\prj\git\wsgidav\wsgidav\dav_provider.py", line 1584, in custom_request_handler
  File "C:\prj\git\wsgidav\wsgidav\request_server.py", line 649, in do_DELETE
  File "C:\prj\git\wsgidav\wsgidav\fs_dav_provider.py", line 106, in delete
PermissionError: [WinError 32] El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso: 'E:\\Webdav_Server\\MyFilesSecure\\MotoDolby-GPro-MagiskModule-20220416153455_1.zip'

14:07:00.222 - DEBUG   : Caught 500
14:07:00.346 - ERROR   : Caught HTTPRequestException(HTTP_INTERNAL_ERROR)
Traceback (most recent call last):
  File "C:\prj\git\wsgidav\wsgidav\error_printer.py", line 50, in __call__
  File "C:\prj\git\wsgidav\wsgidav\request_resolver.py", line 224, in __call__
  File "C:\prj\git\wsgidav\wsgidav\request_server.py", line 127, in __call__
  File "C:\prj\git\wsgidav\wsgidav\dav_provider.py", line 1584, in custom_request_handler
  File "C:\prj\git\wsgidav\wsgidav\request_server.py", line 649, in do_DELETE
  File "C:\prj\git\wsgidav\wsgidav\fs_dav_provider.py", line 106, in delete
PermissionError: [WinError 32] El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso: 'E:\\Webdav_Server\\MyFilesSecure\\MotoDolby-GPro-MagiskModule-20220416153455_1.zip'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\prj\git\wsgidav\wsgidav\error_printer.py", line 83, in __call__
wsgidav.dav_error.DAVError: 500

14:07:00.361 - ERROR   : e.src_exception:
[WinError 32] El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso: 'E:\\Webdav_Server\\MyFilesSecure\\MotoDolby-GPro-MagiskModule-20220416153455_1.zip'
14:07:00.377 - INFO    : <IP_ADDRESS> - (anonymous) - [2022-04-24 19:07:00] "DELETE /MotoDolby-GPro-MagiskModule-20220416153455_1.zip"

What could I do? I need use davx5 for do a backup using a native tool of my android 12. T_T Thank u very much for u reply!


Bug 2044248: Always apply fsGroup to volumes

Don't use the default heuristics, it's wrong when there is no fsType in a StorageClass / PV.
cc @openshift/storage

/bugzilla refresh

/bugzilla refresh

/lgtm
/bugzilla refresh


npm run dev is failing with npm install, working with yarn

Sorry this is a pretty vague issue.
To recreate:

Clone from scratch
npm install
npm run dev

Instead of running normally, it opens at http://localhost:8080/undefined, and none of the assets (css, js) load, instead they 404.
If I use yarn instead for step 2 above, everything works fine, so I imagine this is an issue with a package that has been updated.
My node version is 6.10.3, npm is 5.0.3

I'm looking into this, thanks for reporting!

I've tracked this down to be due to a transitive dependency on<EMAIL_ADDRESS>from<EMAIL_ADDRESS>This issue is reproducible with yarn by updating yarn.lock as such:
<EMAIL_ADDRESS><EMAIL_ADDRESS>-  version "1.10.2"
-  resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-1.10.2.tgz#2e252ce1dfb020dbda1ccb37df26f30ab014dbd1"
+  version "1.11.0"
+  resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-1.11.0.tgz#09691d0973a30ad1f82ac73a12e2087f0a4754f9"
   dependencies:
     memory-fs "~0.4.1"
     mime "^1.3.4"

Not sure how this exactly is causing the normal dev task to fail but I'm still investigating.


Add back settings for maximum saved backups.

Describe your suggested feature
Older versions of Tachiyomi had a setting to set how many of the latest backups you would like to keep. This feature is no longer present in the current version of the app.
Other details
If the maximum is set to 2, all but the latest 2 backups will be deleted from your device.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 0.16.0.
[X] I will fill out all of the requested information in this form.

This was removed in e3b70ca08d1c5a09a448891ff66102fd696d7098, which set the number of kept automatic backups to 4 (as seen here), with the reasoning that the backup creation code would be getting busy with the syncing functionality originally planned.
I don't see much of a need to bring this setting back as 4 seems like a reasonable number of automatic backups, and considering backup files are at best a few MB large, storage shouldn't be an issue either. I also don't think this auto cleanup ever applied to manual backups, as deleting those on a schedule sounds like a Really Bad Idea™.
Any utility reasons for why you want this back, other than having it would be nice for customisation?


Docker compose resources are not refreshed

Hi,
Changes are not applied to Docker Compose resources when using notify/subscribe meta-parameter. Any idea how to achieve that?
E.g. when the file /tmp/docker-compose.yml changes, the docker containers are not refreshed/restarted:
  file { '/tmp/docker-compose.yml':
    content => template('prometheus/docker-compose.yml.erb'),
    owner   => root,
    group   => root,
    mode    => '0640',
    notify  => Docker_Compose['/tmp/docker-compose.yml'],
  }

  docker_compose { '/tmp/docker-compose.yml':
    ensure  => present,
    require => Class['Docker::Compose'],
  }

As of this PR https://github.com/garethr/garethr-docker/pull/550 I think this should now be possible. Could you check from master (although this should also be in 5.3.0).

@garethr Nice PR but I still have one issue with it: the refresh will kill containers and restart them. In my case I don't want this behavior (a simple docker-compose up -d --remove-orphans fits my needs).
In fact, the problem is that before, in every puppet run, the docker-compose up was executed (thus, with the --remove-orphans option, removed services were destroyed during the puppet run) and since a few days it doesn't anymore (I don't know if it comes from the v5.3.0 or from some modifications on my side).
Do you have an idea how to have docker-compose up running on each puppet run?
The best solution seems to be to improve the refreshing feature with a boolean parameter to select if the containers have to be killed before the up command.


Web Application Stuck on installing dependencies

Describe the bug
chat keeps getting stuck on "install dependencies" and can't start application. I've tried multiple times and it does it over and over. I'm just wanting to see a preview of the work it's done so far.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-35k3u7
Steps to reproduce

Go to chat.
Ask if to fix issue
See the spinning loop go non stop

Expected behavior
I believe I just want it to be able to successfully do it's thing and then let me preview the application (sorry if my language is pedestrian, I know nothing about this stuff)
Screen Recording / Screenshot
No response
Platform
Browser name = Safari
Full version = 18.1
Major version = 18
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.1 Safari/605.1.15
performance.memory = undefined
Username = macleancarlson
Chat ID = ae2d20d91a42

Additional context
No response

using chrome did it


module 'pytorch_lightning.utilities.seed' has no attribute 'seed_everything'

Same!
Solved with installing version 1.6.4:
pip install pytorch-lightning == 1.6.4

The whole module is a bit deprecated, the PyTorch version they add in the README is not compatible with the latest consumer GPUs (f.E. a 4090), and newer PyTorch versions are in turn not compatible with older Lightning versions. You need to port the lightning code over to a newer version, check update guides here: https://lightning.ai/docs/pytorch/latest/upgrade/from_1_6.html

I was getting the same error but managed to resolve with the right mix of library versions.  I ran into this, and another related pytorch error, and my understanding of the issue is that the setup.py installs latest pytorch-lightning version, specifying only that version must be >=1.6.4.
This now installs Pytorch v2, which in turn does not have certain functions (e.g. pytorch_lightning.utilities.seed mentioned here) used by the repo code. The solution to the issue, as I see it, would be to update the setup.py with more constraints on library versions, such that the donut repo code is still runnable after standard install. That would be preferable to the workarounds people have here of installing donut then uninstalling and reinstalling different versions of certain libraries like pytorch-lightning (and which I've been doing as well).
I could submit a PR if the repo owner(s?) would be amenable...

Looks like this is cropping up in several other donut github issues, e.g. here and here referencing needing specific versions of timm and transformers that are not what setup.py installs currently.


Minor UI improvements

PR addresses minor UI improvements. Changes are intended as a temporary fix until the new docs go live.
Before and After:

@shubh73  Thank you very much. The official website will be back online soon. If you want to continue to participate, you can make modifications in the new_doc branch.
https://68516403.farm-fe-github-io.pages.dev/


Node GetAccessor did not pass test 'isTypeElement'.

Bug Report
🔎 Search Terms
"Node GetAccessor did not pass test 'isTypeElement'."
🕗 Version & Regression Information
While working on our web UI with Create React App this problem appears a lot in the last times. When I delete node_modules\.cache\tsconfig.tsbuildinfo and reastart Create React App it starts to work again, this is why I think its more a TS bug then related to Create React App.
I currently have no idea what currently is triggering the bug. When I delete the cache it works for a while and then appears right out of nowhere again.
CRA displays the following (development mode):

webpack compiled successfully
Files successfully emitted, waiting for typecheck results...
Issues checking in progress...
Error: Debug Failure. False expression: Unexpected node.
Verbose Debug Information: Node GetAccessor did not pass test 'isTypeElement'.
Error: Debug Failure. False expression: Unexpected node.
Verbose Debug Information: Node GetAccessor did not pass test 'isTypeElement'.
at visitNodes (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:87664:39)
at Object.visitEachChild (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:87884:60)
at visitDeclarationSubtree (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:107162:31)
at Object.visitNode (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:87593:23)
at transformTopLevelDeclaration (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:107271:179)
at visitDeclarationStatements (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:107227:26)
at Object.visitNodes (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:87646:48)
at transformRoot (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:106591:37)
at transformation (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:107888:24)
at transformRoot (C:\Dev\Repo\node_modules\typescript\lib\typescript.js:107915:82)

Typescript: 4.6.4
react-scripts: 5.0.1
I did some test to fix it. Upgrade TS, remove node_modules, remove lockfile and reinstall. Nothing helped.
Our codebase is large and got a lot changes and since this problem can not reproduced, I need help in collection more information to narrow this issue to concrete problem.

If you can give us a repo with reproduction instructions, we can investigate.

If you can give us a repo with reproduction instructions, we can investigate.

Thank you for your answer. The problem here is that this is a corporate private repostiory witch I can not share public.

@m0ksem I see that ultimately runs a tool called vue-tsc. Can you reproduce the issue with tsc?

Same
(develop)~/projects/vuestic-ui/packages/ui$ yarn tsc src/main.ts --declaration --emitDeclarationOnly

vuestic-ui/node_modules/typescript/lib/tsc.js:73594
                        void ts.Debug.assertNode(visited, test);
                                      ^
Error: Debug Failure. False expression: Unexpected node.
Verbose Debug Information: Node 171 did not pass test 'isTypeElement'.

@m0ksem thanks! Are you blocked by this or have you found a workaround?

@m0ksem thanks! Are you blocked by this or have you found a workaround?

Moving to 4.6.3 from 4.6.4 helps!

@lanwin filed the report against 4.6.4, so I guess we’re back at square one. @lanwin, for kicks do you want to try the latest TypeScript, 4.7.4?

It seems that the lastest versions did not have this bug anymore. I did not encountered again lately.


feat: Type inference in 'have been called with' parameters

Fixes #15034.
Summary
See #15034.
This feature has been attempted at the past (#13268), but introduced a breaking change (#13337) with overloaded functions, and thus was reverted.
To reach the desired typing -- especially the handling of overloaded functions vs no-args function vs the default jest.fn() type -- I eventually found this code and modified it slightly to fit better to the use-case.
Test plan
See the tests added to the PR.

Interesting to see some progress in this field. Some time ago I was walking more or less the same path. All was fun until I realised that asymmetric matcher can be also nested. Also that expected value and target arguments even can have different shapes:
expect(
  jestExpect(
    jest.fn<(date: Date, name: [string, string]) => void>(),
  ).toHaveBeenCalledWith(jestExpect.any(Date), [
    jestExpect.any(String),
    jestExpect.any(String),
  ]),
).type.toBeVoid();

expect(
  jestExpect(
    jest.fn<(date: Date, name: [string, string]) => void>(),
  ).toHaveBeenCalledWith(jestExpect.any(Date), jestExpect.any(Array)),
).type.toBeVoid();

asymmetric matcher can be also nested

@mrazauskas Thanks, this is a good use/test case!
I think it's solvable with changing the current WithAsymmetricMatchers from:
type WithAsymmetricMatchers<P extends Array<any>> =
  Array<unknown> extends P ? never : {[K in keyof P]: P[K] | AsymmetricMatcher};

to:
type WithAsymmetricMatchers<P extends Array<any>> =
  Array<unknown> extends P
    ? never
    : {[K in keyof P]: DeepAsymmetricMatcher<P[K]>};

type DeepAsymmetricMatcher<T> = T extends object
  ? AsymmetricMatcher | {[K in keyof T]: DeepAsymmetricMatcher<T[K]>}
  : AsymmetricMatcher | T;

I would've preferred that all the asymmetric-matchers-producing functions will return the type that the matcher is supposed to stand for:
jestExpect.stringContaining('') // returns `string`
jestExpect.any(Number) // returns `number`

As it will allow for even better type checking. However, I'm not sure it's possible, and even if it is, it's likely going to break a lot of things.

Do you mind addressing to questions regarding this PR that I posted in the issue?

Before completing it, I wanted to know if that's the right direction.
I also had two specific questions about the PR:

I added an import type from jest-mock to jest-types package.
Should I change something in the dependencies?

The type-checking of "examples and tests" (yarn typecheck:tests) fails on a few cases:
a) In throwMatcher.test.ts, mockedMatch is defined with jest.fn and a no-args function, causing later expect to fail since it passes an argument to toHaveBeenCalledWith.
b) In Farm.test.ts the same is happening with computeWorkerKey.
c) In BaseWorkerPool.test.ts the type of the argument given to expect(Worker).toHaveBeenNthCalledWith() does not exactly match the type of the mock argument (WorkerOptions).

These failures seems to me like the expected behavior of this new feature, meaning that it's likely to introduce breaking changes to existing code. What are your thoughts on this?

You should add jest-mock to devDependencies of  jest-types and list it in references of packages/jest-types/tsconfig.json.
As you noticed, the failures are expected. Since Jest currently is releasing alphas, it is fine to land any breaking changes. Just update the tests to make the check pass.

By the way, I updated the example in my previous comment. Finally I recalled that the biggest challenge was to handle optional arguments like name?.

@mrazauskas

You should add jest-mock to devDependencies of  jest-types and list it in references of packages/jest-types/tsconfig.json.

That didn't work for me. yarn build failed on compilation tsc.

By the way, I updated the example in my previous comment. Finally I recalled that the biggest challenge was to handle optional arguments like name?.

The code seems to handle this as well. See my updated commit with all the new test cases.

Ah.. Both package.json and tsconfig.json in jest-mock are listing @jest/types as a dependency. That is a mistake, because the dependency was removed in #7971 (five years ago). This can be cleaned up (in separate PR).
I see currently you are importing one type from jest-mock to expect. Is it possible to declare jest-mock as a devDependency in the expect package? Or build script is complaining?
Some time later I will try out updated types. Really interesting.

I see currently you are importing one type from jest-mock to expect. Is it possible to declare jest-mock as a devDependency in the expect package? Or build script is complaining?

@mrazauskas That works 😃 I amended my last commit with this addtional change.

If I got it right, your implementation only supports type inference for the Mock type. Only wondering why did you decide so? I mean, args of in the following (this is one examples from Jest's docs) is still inferred as Array<unknown>:
jest.spyOn(globalThis, 'setTimeout');

jest(setTimeout).toHaveBeenLastCalledWith(jest.any(Function), 1000);

Not a blocker. That is fine, of course. I just wanted to check if that is by design or this got overlooked?

your implementation only supports type inference for the Mock type

@mrazauskas That's an oversight :)
I adjusted the code to support both MockInstance (broader than Mock) and functions without mock type wrapping. I also added a few minimal test cases for these mock-less functions.

@mrazauskas @SimenB Thanks for your help on this PR. I couldn't have done it without you ❤
Please let me know if you have more concerns.
As for the changelog, I'm keeping it for you to decide whether to include the "breaking" tag and whether @jest/expect should be mentioned as well.

@eyalroth I was playing with updated types. All works as expected. Great job!


Found a typo and wrong description on Part2

such as consensus and membership services, to be plug-and-playIn
Part 2, we will explore more about creating a complex network with multiple participants and using Access Control Rules (ACL) to provide them network access permissions. In this journey, you will run Hyperledger Fabric on the Cloud.

plug-and-play. In Part 2, ~~~

Part 2 is still done on Hyperledger Composer which is running on local environment, not Cloud nor Fabric.

Any plan to convert this to Fabric version ?

Part 2 code pattern link is now changed to the updated Fabric pattern


Add agent info command

Add a preflight agent info command that prints some useful debugging information.
Remove the "Experimental" tag for the credentials file, as it is fully supported now.

/lgtm


[Release 1.0] Add Elemental Reset capabilities to nodes provisioned via EIB

Backport #449

Must confirm an elemental-operator version with this feature is published.


UWP Exporter doesn't copy the GDNative DLL to the final APPX

Godot version
v3.4.4.stable.official.419e713a2
System information
Windows 11, GLES3, Nvidia GeForce GT 1030.
Issue description
Hello, I'm exporting a UWP project that contains a DLL file but when I export the project the DLL is missing, Here are some screenshots about it:

(game/ folder)

Steps to reproduce

Add the dll to the project
Export the project
Try to execute it or see the contents inside the APPX file

Minimal reproduction project
UWP Game.zip

I fixed it by adding a function to copy the dynamic libraries, I will close this issue and I will open a pull request.

This should be kept open until the PR fixing this issue is approved and merged :)

Fixed by #61262.


add_quotations

The quotation marks around l:request are important when sending the curl_command through ssh, for instance, as in:
let l:curl_command = [
        \ "ssh", "-q",
        \ "-J", "jump.server",
        \ "llama.cpp.server",
        \ "curl",
        \ "--silent",
        \ "--no-buffer",
        \ "--request", "POST",
        \ "--url", g:llama_config.endpoint,
        \ "--header", "Content-Type: application/json",
        \ "--data", "'". l:request ."'"
        \ ]

Without the quotation marks, the ssh command might fail, hence this PR.
Why would you need that?
On a server cluster, you might want to run the llama.cpp server on one server and work on a file in vim on another server. Then you need to route your curl command to the llama.cpp server (possibly via a jump server) to use the curl command as is.
This should not affect the generality of the curl_command. Putting this here because it took me a while to figure out.

Instead of modifying the curl command, I forward the remote port to a local port:
ssh -fNL 8012:localhost:8012 <remote_host>

This broke functionality for me:
got exception: {"code":500,"message":"[json.exception.parse_error.101] parse error at line 1, column 1: syntax
error while parsing value - invalid literal; last read: '''","type":"server_error"}

From vim's job_start help page:
The command is executed directly, not through a shell, the
                'shell' option is not used.  To use the shell:
        let job = job_start(["/bin/sh", "-c", "echo hello"])
                Or:
        let job = job_start('/bin/sh -c "echo hello"')
                Note that this will start two processes, the shell and the
                command it executes.  If you don't want this use the "exec"
                shell command.

From neovim's jobstart help page:
		Spawns {cmd} as a job.
		If {cmd} is a List it runs directly (no 'shell').

There's no need to wrap it in single quotes, as there is no shell it misinterpret escape characters. The only reason why you needed to add single quotes was because you introduced a shell by using the ssh command. I recommend you use port-forwarding like @ggerganov recommended.

Ah sorry about that. I've reverted the change.


[CHANGE ME] Re-generated to pick up changes from self.

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/41c9eff8-8367-4edf-b4b6-9a6695f6ec8e/targets

[ ] To automatically regenerate this PR, check this box.

@eaball35 Argh - Please back out your change to .kokoro/release/common.cfg then delete this PR

@eaball35 Argh - Please back out your change to .kokoro/release/common.cfg then delete this PR

@eaball35 This PR will back out your change.

@eaball35 This PR will back out your change.


Changes:

Added Main window for Gui, for which the widget is embedded
Removed idealifty factor calculations into the analysis tab, and changed to dlog(I)/dV.
Added status bar
Linked status bar to asserts on input data checks
Added units to input status checks for when outputed to file
Added m-V curve plotting of light IV
Added log IV plotting for Suns Voc
Renamed Dark IV plot_IV function to plot_log_IV for consitance and clarity
Added some doc strings

Awesome, thanks!


After redirect from sign-in page, redirect again to url with no query params.

Before calling submit(), redirect to the main URL with no query params. This is so that Tableau's WDC MRU doesn't get polluted with the redirect URLs with different request_token query params.

The url is always registered by the initCallback method.
Depending on the version of the tableau shim you’re using (singletable/multitable), on the singletable version you have to call it explicitly  : tableau.initCallback();
On the multitable shim, the initCallback is passed as parameter to the tableau.init method
So, technically you can do all the redirections you want and persist the data you need (on the cookies for example) and when you’re done you go back to the clean url and call the initCallback so that your clean url is saved on the history.