Project Page - Have Team option - Design Change

Problem -

People who are not using Team concept are against this. as they use only one person per project style
They don't want "?" over Project Manager icon, they just want old clean design without "?"

Suggested Solution by @vinpahilwani

Give Other icon for Having Team, instead of Not having Team.
Don't give anything on icon who does not have team
Create some other design to overcome hidden Project Manager Photo

Revert -

#1505 issue worked Correctly, there was not discussion about this
This issue will reverse all thing done by #1505

Design -
Still getting inputs from design team
Initiated by @sureshsirvi
Verified by  @vinpahilwani

Approved

Design Issue:
Problem:

Some users are using as single member in Projects... they are facing always "?" on project instead of Image of Project Manager..

Sollution:

I suggest, use Red ring Circle around the PM image. OR
We can provide filter option.

https://user-images.githubusercontent.com/46588108/186639791-c3d91ca1-1172-4772-a1d9-66b4bc2c7e68.mp4

Yes Blinking is fine

https://github.com/Fammeo/EasyCloudBooks/issues/1531#issuecomment-1228386895

I approve the above design.

No problem

Please Suggest any thing else if you want to add,

Have Team than Icon / still if continue for if don't have team them show some icon
any other metric

Please Suggest any thing else if you want to add,

Have Team than Icon / still if continue for if don't have team them show some icon
any other metric

Currently no need for any other metric.

Trying Fade with 5 Sec frequency
with Minimum design impact,
@vinpahilwani do you still need Team have Option? or Previous Team Pending icon will be good?

You mean question marke jaisa abhi hai?

Yes, if purpose of redesign was

Only single managers structure dobt want to see this
Cant see whos manager

As we are making new design, we need too think about show symbol for not having team or show symbol for having team

No problem - Use Yellow Color not the Red Color, Red color unko hurt karta hai

https://www.berrycast.com/conversations/ff18a99d-f6c4-557b-be13-a71e83dfee92


Portainer with nginx-proxy

Hello, when i want to connect Portainer, i have this on nginx log output :
3 SSL_do_handshake() failed (SSL: error:1408F10B:SSL routines:ssl3_get_record:wrong version number) while SSL handshaking to upstream....
and I have a 502 on the browser...

Remove VIRTUAL_PROTO 0:)

@kevindesousa I'm having this same issue, but did not set VIRTUAL_PROTO

You also need to remove VIRTUAL_PORT if it's set ?


[Backup/Restore] - How to increase backup/restore throughput/speed?

We have benchmarked 2GiB/minute throughput during SolrBackup with ~4TB RAW index data. Backup/Restore duration is critical during disaster event hence, we are looking for increased speed.
  - backupName: solr-backup-XYZ
    collection: <collection>
    finishTimestamp: "2023-07-28T00:16:42Z"
    finished: true
    startTimestamp: "2023-07-27T23:41:36Z"
    successful: true

Right now, only performance option we found is the endpoint URL to keep the traffic private between VPC & S3. But it's not scaling the throughput significantly. S3 do support throughput up-to 100Gbps and our selected EC2 instance do support 10Gbps.
Can we configure S3 multipart upload to speed up the backup and similarly how to boost-up the RESTORE speed?
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/examples-s3-objects.html#list-objects
https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance-design-patterns.html#optimizing-performance-parallelization
May be we expose one more option in the backup configuration that can support horizontal scaling and parallel RW.
@HoustonPutman: Any plan/suggestion on this optimization?

Sorry, meant to comment as well.
The Solr Operator just uses the built-in Solr S3-Repository Module, so there's nothing that the Solr Operator can do to speed this up.
Instead would you mind posting this same information as a new JIRA Issue at https://issues.apache.org/jira/projects/SOLR/summary? That way optimizations can be tracked and discussed in the right place.


Publish dotty 0.19 version to maven central

Currently I only find a version for dotty 0.18 on maven central (https://search.maven.org/artifact/com.factor10/intent_0.18/0.1.0/jar). Can you also publish the 0.19 version? Or on which repository can I find it?

We'll fix. Thanks for the reminder!

Version 0.2.0 is now published (which requires 0.19 of dotty), as well as version 0.3.0 using 0.20 of dotty.
Enjoy!


Fixes #2801 Assert in ExpressionEvaluator.set_Scope

Fixes #2801 Assert in ExpressionEvaluator.set_Scope
Do not nest scopes inside IsInstance scopes.
Adds test

This is ready to merge - whoever reviews can go ahead and complete it.


Fixed a bug of the newline checker

Fixed issue #520.
This commit is to fix an incorrect execution of the newline checker when
the file type of .md file is "UTF-8 Unicode text".
Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>

:memo: Version: 1.20190225. Thank you for submitting PR #521. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.


[ONNX] AttributeError: 'tuple' object has no attribute 'replace'

LPOT Version: 1.5.1
ONNX Version: 1.7
ONNXRuntime Version: 1.6.0
Environment: Google Colab
Configuration:
quantization:
  calibration:
    sampling_size: 500
  model_wise:
    weight:
      granularity: per_channel
      scheme: sym
      algorithm: minmax
    activation:
      granularity: per_tensor
      scheme: sym
      algorithm: minmax

evaluation:
  accuracy:
    metric:
      MSE: {}
  performance:
    warmup: 30
    iteration: 300

tuning:
  objective: performance
  random_seed: 9527
  strategy:
    name: mse
  accuracy_criterion:
    higher_is_better: False
    relative: 0.8
  exit_policy:
    performance_only: False
    max_trials: 20
    timeout: 100000

When quantizing my ONNX model, at the first tune it seems fine and outputs the accuracy and latency, but in tune 2 the following error happens:
Traceback (most recent call last):
  File "main.py", line 154, in <module>
    q_model = quantize()
  File "/usr/local/lib/python3.7/dist-packages/lpot/experimental/quantization.py", line 178, in __call__
    self.strategy.traverse()
  File "/usr/local/lib/python3.7/dist-packages/lpot/strategy/strategy.py", line 296, in traverse
    for tune_cfg in self.next_tune_cfg():
  File "/usr/local/lib/python3.7/dist-packages/lpot/strategy/mse.py", line 145, in next_tune_cfg
    self.model, self.calib_dataloader, op_lists, [1])
  File "/usr/local/lib/python3.7/dist-packages/lpot/adaptor/onnxrt.py", line 200, in inspect_tensor
    weight=(inspect_type!='activation'))
  File "/usr/local/lib/python3.7/dist-packages/lpot/adaptor/ox_utils/onnxrt_mid.py", line 417, in dump_tensor
    self.white_nodes = [node.replace('_quant', '') for node in self.white_nodes]
  File "/usr/local/lib/python3.7/dist-packages/lpot/adaptor/ox_utils/onnxrt_mid.py", line 417, in <listcomp>
    self.white_nodes = [node.replace('_quant', '') for node in self.white_nodes]
AttributeError: 'tuple' object has no attribute 'replace'

For the object node that is considered a tuple instead of string, I printed it out and it looks like this:
('StatefulPartitionedCall/model/1/Conv2D', 'Conv'), which is a tuple consisting of two strings. Which one should I use in this place?

@peiwenhuang27 thanks for raising this issue, you should use the first one. I will fix this bug and provide a patch file.

Thanks! I'll wait for the patch file to try again later.

inspect.txt
@peiwenhuang27 this patch is generated with internal previous commit. So the line number is different from the public one

I added the lines to onnxrt.py as in the patch file, then this occurs:
Traceback (most recent call last):
  File "main.py", line 154, in <module>
    q_model = quantize()
  File "/usr/local/lib/python3.7/dist-packages/lpot/experimental/quantization.py", line 178, in __call__
    self.strategy.traverse()
  File "/usr/local/lib/python3.7/dist-packages/lpot/strategy/strategy.py", line 296, in traverse
    for tune_cfg in self.next_tune_cfg():
  File "/usr/local/lib/python3.7/dist-packages/lpot/strategy/mse.py", line 145, in next_tune_cfg
    self.model, self.calib_dataloader, op_lists, [1])
  File "/usr/local/lib/python3.7/dist-packages/lpot/adaptor/onnxrt.py", line 195, in inspect_tensor
    if len(op_list) == 0 or isinstance(op_list[0], str):
TypeError: 'odict_keys' object is not subscriptable

inspect.txt
@peiwenhuang27 Sorry for my unprofessional, pls try this new patch again.

No worries! I really do appreciate all you guys' efforts in this great tool 😊
I tried using the new patch, and then this happens:
2021-07-29 09:12:40 [INFO] |*******Mixed Precision Statistics*******|
2021-07-29 09:12:40 [INFO] +----------------------+---------+-------+
2021-07-29 09:12:40 [INFO] |       Op Type        |  Total  |  INT8 |
2021-07-29 09:12:40 [INFO] +----------------------+---------+-------+
2021-07-29 09:12:40 [INFO] |         Conv         |    8    |   8   |
2021-07-29 09:12:40 [INFO] |        MatMul        |    6    |   6   |
2021-07-29 09:12:40 [INFO] |         Mul          |    2    |   2   |
2021-07-29 09:12:40 [INFO] |      LeakyRelu       |    8    |   8   |
2021-07-29 09:12:40 [INFO] |       Sigmoid        |    3    |   3   |
2021-07-29 09:12:40 [INFO] |         Add          |    5    |   5   |
2021-07-29 09:12:40 [INFO] |    QuantizeLinear    |    13   |   13  |
2021-07-29 09:12:40 [INFO] |   DequantizeLinear   |    13   |   13  |
2021-07-29 09:12:40 [INFO] +----------------------+---------+-------+
2021-07-29 09:12:40 [INFO] Pass quantize model elapsed time: 61369.01 ms
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearSigmoid. No schema registered for this operator.
Warning: Unsupported operator QLinearMul. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearSigmoid. No schema registered for this operator.
Warning: Unsupported operator QLinearMul. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearSigmoid. No schema registered for this operator.
2021-07-29 09:12:40.408709436 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/42/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.409391842 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_3/Sigmoid:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.409780086 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/multiply_1/mul:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.409946411 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_5/Sigmoid:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.410217000 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/51/Conv2D:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.410542583 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense/BiasAdd:0_quantized_output' source:{64,60,600} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.410713608 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/1/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.410876688 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/52/LeakyRelu:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.411039542 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_4/Tensordot/MatMul:0_quantized_output' source:{3840,400} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.411190409 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/32/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.411362426 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense/Tensordot/MatMul:0_quantized_output' source:{3840,600} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.411534705 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/1/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.411695712 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/2/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.411854370 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_2/Tensordot/MatMul:0_quantized_output' source:{3840,600} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.412014974 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_3/BiasAdd:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.412173777 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/42/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.412339732 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_4/BiasAdd:0_quantized_output' source:{64,60,400} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.412607135 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_1/Sigmoid:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.412768970 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/32/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.412927818 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_1/Tensordot/MatMul:0_quantized_output' source:{3840,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.413089054 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/41/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.413253272 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_3/Tensordot/MatMul:0_quantized_output' source:{3840,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.413412338 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/41/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.413581824 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/52/Conv2D:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.413741855 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/2/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.413900882 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_5/BiasAdd:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.414062395 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_1/BiasAdd:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.414226413 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/51/LeakyRelu:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.414386359 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/31/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.414598588 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/31/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.414767790 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/multiply/mul:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:40.414934893 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_5/Tensordot/MatMul:0_quantized_output' source:{3840,257} target:{}. Falling back to lenient merge.
2021-07-29 09:12:50 [ERROR] Unexpected exception KeyError('S') happened during turing!
2021-07-29 09:12:51 [INFO] Specified timeout or max trials is reached! Found a quantized model which meet accuracy goal. Exit...

@peiwenhuang27 According to your error info, the model has been quantized and begin to evaluate. The error info is insufficient so I can not confirm where it crashed.
Could you make some code changes and run quantization again, then paste the error info?
Code change:
https://github.com/intel/lpot/blob/f4c4ca35d99de940ad90ea24e1dc80e18fda8dea/lpot/experimental/quantization.py#L176
Comment code from line 176 to 183, adjust the indent from line 184 to 194, add 'self.strategy.traverse()' to line 175
Thanks
Mengni

After I changed the code, the error info still remains the same though.
I changed the code in quantization.py as:
        self.strategy.traverse()
        # try:
        #     with time_limit(self.conf.usr_cfg.tuning.exit_policy.timeout):
        #         self.strategy.traverse()
        # except KeyboardInterrupt:
        #     pass
        # except Exception as e:
        #     logger.error("Unexpected exception {} happened during turing!".format(repr(e)))
        # finally:
        if self.strategy.best_qmodel:
            logger.info(
                "Specified timeout or max trials is reached! "
                "Found a quantized model which meet accuracy goal. Exit...")
            self.strategy.deploy_config()
        else:
            logger.error(
                "Specified timeout or max trials is reached! "
                "Not found any quantized model which meet accuracy goal. Exit...")

            return self.strategy.best_qmodel

The warning lines look the same:
2021-07-30 03:16:38 [INFO] Pass quantize model elapsed time: 239254.73 ms
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearLeakyRelu. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearSigmoid. No schema registered for this operator.
Warning: Unsupported operator QLinearMul. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearSigmoid. No schema registered for this operator.
Warning: Unsupported operator QLinearMul. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearAdd. No schema registered for this operator.
Warning: Unsupported operator QLinearSigmoid. No schema registered for this operator.
2021-07-30 03:16:38.658788179 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/42/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.661616148 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_1/Sigmoid:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.661738301 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/52/Conv2D:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.661968131 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_3/Sigmoid:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662054454 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/41/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662131834 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/51/Conv2D:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662211268 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/41/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662384399 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_5/BiasAdd:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662472933 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/multiply_1/mul:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662562698 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_1/Tensordot/MatMul:0_quantized_output' source:{3840,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662640371 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/1/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662722585 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/32/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662798685 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/51/LeakyRelu:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662872899 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense/Tensordot/MatMul:0_quantized_output' source:{3840,600} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.662947928 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/31/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663021420 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_4/Tensordot/MatMul:0_quantized_output' source:{3840,400} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663096368 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_3/BiasAdd:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663170776 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/32/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663245524 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/42/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663319850 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/1/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663394028 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_3/Tensordot/MatMul:0_quantized_output' source:{3840,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663468315 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_2/Tensordot/MatMul:0_quantized_output' source:{3840,600} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663554115 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/52/LeakyRelu:0_quantized_output' source:{64,8,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663629565 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/2/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663708881 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_4/BiasAdd:0_quantized_output' source:{64,60,400} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663824720 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/2/LeakyRelu:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663908194 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_1/BiasAdd:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.663982914 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_5/Tensordot/MatMul:0_quantized_output' source:{3840,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.664058194 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/31/Conv2D:0_quantized_output' source:{64,64,257,60} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.664131965 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense/BiasAdd:0_quantized_output' source:{64,60,600} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.664207239 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/multiply/mul:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
2021-07-30 03:16:38.664281131 [W:onnxruntime:, graph.cc:84 MergeShapeInfo] Error merging shape info for output. 'StatefulPartitionedCall/model/dense_5/Sigmoid:0_quantized_output' source:{64,60,257} target:{}. Falling back to lenient merge.
run_tuning.sh: line 31:   918 Killed                  python main.py --model_path ${input_model} --output_model ${output_model} --config ${config} --tune
/usr/lib/python3.7/multiprocessing/semaphore_tracker.py:144: UserWarning: semaphore_tracker: There appear to be 6 leaked semaphores to clean up at shutdown
  len(cache))


Feature: Add custom links to the navigation bar

It would be really sweet to be able to add our own links to the navigation bar, Like if you have a discord or a blog to be able to put it there. I feel like this may already be easily possible but as a non-programmer I'm not sure. I use the docker version of Pigallery2 if anyone is familiar with a way to do this I'd love to know.

Hi,
Currently I don't really see if there is an easy straightforward way of doing so.
The only way of doing so is to fork the project and add the link at the source. Here:
https://github.com/bpatrik/pigallery2/blob/b6f93ac5c4e2f9939ba2745f65f21da0dd3bfcc4/src/frontend/app/ui/frame/frame.component.html#L18
Then compile and run the project from source.
If once I add plugin/add on option to the app, this should be easier.

Aw that's unfortunate, but thanks for at least giving me that option. I think this would definitely be a well appreciated addition when you have time! I love what you've accomplished with the project thus far. Cheers!

This is now possible as experimental feature. See: 150


Highlight the "continue" keyword for loops.

Currently, this is not highlighted like "break" is.

Fixed by https://github.com/rust-lang/sublime-rust/pull/65

should be close


Add new members of CF Committee to list in the governance page.

Three new members have been added to the CF Committee.
Could someone else from @cf-convention/gov-panel review and merge?

Thank you, Ethan. I've merged the change. It said some check about markdown had failed. J

Thanks Jonathan. Yes, I saw that error as well. I looks like the new link checking failed. I think that check was added recently by @erget? I'll also ping @cf-convention/info-mgmt in case anyone is already looking into this.

Hello all, this is part of the glacial push to get the website free of broken links. Over time pushes should eliminate broken links rather than create new ones - that's what that check looks for. Now the check's in place, but the broken links it finds still need to be corrected. I don't think it's a problem for this PR because none of the broken links are in the edited pages. Some archaeology in the coming months should get rid of the existing broken ones so that at some point soon-ish the checker shouldn't complain.


could this be packaged as a component?

it could be listed here if so: https://aframe.wiki/e/en/component-directory

kfarr, yes I can try to do that. Did not have much time lately. :)


Issue rendering TVILocalVideoTrack in UICollectionViewCell

Hello,
I am building a group video chat application using the programmable video api, and I'm noticing some strange behavior when connecting to a room.
My goal was to render each room participant in a UICollectionViewCell as opposed to creating a UIView for each participant.
The following best describes my approach.
At the View Controller:
Initialize both the TVILocalVideoTrack & TVILocalAudioTrack
    func prepareLocalMedia() {

        // Create an audio track.
        if (localAudioTrack == nil) {
            localAudioTrack = TVILocalAudioTrack.init()

            if (localAudioTrack == nil) {
                print("audio track failed to initialize")
            }
        }

        // Create a video track which captures from the camera.
        if (localVideoTrack == nil) {
            let videoConstraints = TVIVideoConstraints { (constraints) in
                constraints.aspectRatio = TVIAspectRatio16x9
                constraints.maxFrameRate = 30
                constraints.minFrameRate = TVIVideoConstraintsFrameRateNone
            }

            camera = TVICameraCapturer(source: .frontCamera, delegate: self)
            localVideoTrack = TVILocalVideoTrack.init(capturer: camera!, enabled: true, constraints: videoConstraints)

            createRoom()
        }
    }

Connect to a room.
    func createRoom() {

        if (accessToken == "TWILIO_ACCESS_TOKEN") {
            do {
                accessToken = try TokenUtils.fetchToken(url: tokenUrl)
            } catch {
                print("Failed to fetch access token")
                return
            }
        }

        let connectOptions = TVIConnectOptions.init(token: accessToken) { (builder) in
            builder.audioTracks = [self.localAudioTrack!]
            builder.videoTracks = [self.localVideoTrack!]
            builder.roomName = "Test"
        }
        room = TwilioVideo.connect(with: connectOptions, delegate: self)
        print("attempting to connect to room Test")

        DispatchQueue.main.async(execute: {
            self.collectionView?.reloadData()
        })
    }

At the UICollectionViewCell:
    func startPreview() {
        let videoConstraints = TVIVideoConstraints { (constraints) in
            constraints.aspectRatio = TVIAspectRatio16x9
            constraints.maxFrameRate = 30
            constraints.minFrameRate = TVIVideoConstraintsFrameRateNone
        }

        camera = TVICameraCapturer(source: .frontCamera, delegate: nil)

        localVideoTrack = TVILocalVideoTrack.init(capturer: camera!, enabled: true, constraints: videoConstraints)
        if (localVideoTrack == nil) {
            print("Video track in cell is nil")
        } else {
            localVideoTrack!.addRenderer(previewView)
            print("Video track added to previewView in Cell")
        }
    }

At cellForItemAt indexPath:

//Here I set the delegate for the TVICameraCapturer and TVIVideoView for the cell
                memberCell.previewView.delegate = self
                memberCell.camera.delegate = self

Currently what I expect is for a preview to render in the cell and also on the other participants screen.
What's actually happening is, as if by  random, the preview either renders solely on the device and no video data is sent to the room or video is sent to the room but doesn't render on the device.
Currently I am using TwilioVideo 1.3.2
Any suggestions?

@louiss98 I apologize for responding late to you question.
An app should not create more than one local video track with camera as source. From the code snippet you have posted, it seems like two localVideoTracks are created : the one while connecting to a Room and another oneUICollectionViewCell's  startPreview method.  Can you try creating a local video track and share it in your application?
Here is the modified methods  :
    func prepareLocalMedia() {

        // Create an audio track.
        if (localAudioTrack == nil) {
            localAudioTrack = TVILocalAudioTrack.init()

            if (localAudioTrack == nil) {
                print("audio track failed to initialize")
            }
        }

        // Create a video track which captures from the camera.
        if (localVideoTrack == nil) {
            let videoConstraints = TVIVideoConstraints { (constraints) in
                constraints.aspectRatio = TVIAspectRatio16x9
                constraints.maxFrameRate = 30
                constraints.minFrameRate = TVIVideoConstraintsFrameRateNone
            }

            camera = TVICameraCapturer(source: .frontCamera, delegate: self)
            localVideoTrack = TVILocalVideoTrack.init(capturer: camera!, enabled: true, constraints: videoConstraints)
        }

        createRoom()
    }

    func startPreview() {

        // Create a local video track if it it is not created yet
        if (localVideoTrack == nil) {
            let videoConstraints = TVIVideoConstraints { (constraints) in
                constraints.aspectRatio = TVIAspectRatio16x9
                constraints.maxFrameRate = 30
                constraints.minFrameRate = TVIVideoConstraintsFrameRateNone
            }

            camera = TVICameraCapturer(source: .frontCamera, delegate: nil)

            localVideoTrack = TVILocalVideoTrack.init(capturer: camera!, enabled: true, constraints: videoConstraints)
        }

        // Add renderer on the local video track
        if (localVideoTrack == nil) {
            print("Video track in cell is nil")
        } else {
            localVideoTrack!.addRenderer(previewView)
            print("Video track added to previewView in Cell")
        }
    }

@louiss98 Hoping the problem is resolved at your end. I am closing the ticket but feel free to re-open if you observer the issue again.


Add support for regex to not be surrounded by quotes

I am working on a project that requires including unquote regular expressions in the pipeline like so
- pattern-regex: .*\b(?i)(select|delete|insert|create|update|alter|drop)\b.*

.*\b(?i)(select|delete|insert|create|update|alter|drop)\b.*
Because of the line length, I dont think this is being recognized as regex and is being surrounded by quotes:
- pattern-regex: ".*\b(?i)(select|delete|insert|create|update|alter|drop)\b.*"

This is breaking the regular expression in the yaml.
Describe the solution you'd like
i reviewed the stringifyString.ts file and it appears like it may need support added to check if the input string is valid regex, and if so return a plain string not surrounded by quotes.
Describe alternatives you've considered
I've explored adding replacers to achieve what I need, but I dont think this will work as the issue is with how the field is stringified not the value itself.

Please share a code snippet that shows the issue you're seeing.

Closing due to silence.


Put ntfy.sh/docs assets behind a CDN 💸 -> 🚀

Done in https://github.com/binwiederhier/ntfy-docs.github.io and https://github.com/binwiederhier/ntfy/blob/main/.github/workflows/docs.yaml


[FEA] Help dataShader with GPU CI

Find and setup resources to support GPU CI for datashader

Please! :-) In the meantime we are running GPU tests by hand for Datashader and for HoloViews' Datashader support, but that's currently the only manual step in our release process, so it's very painful to have to do that.

@mike-wendt If I remember correctly there are some plans to setup something for Anaconda?


Integration test infrastructure for Kotlin

Related to #2424, we should add a new assertj-core-kotlin module under assertj-tests/assertj-integration-tests to support Kotlin based integration tests.
We could check the Kotlin related issues we had in the past to see if any Kotlin specific test case can be added.

I'm interested in contributing to this issue, so before I start working it, would you mind sparing your time explaining what the fix will be and pointing me to some resources to get started.

Hi @sreenath-tm, thanks for the help!
The idea would be to add a new Maven module called assertj-core-kotlin. The module should be a child module of assertj-integration-tests. This module should have only a src/test/kotlin folder, should be capable to compile Kotlin test source files and should execute them with JUnit Jupiter.
You might take inspiration from #2758 which added support for Groovy.
About the needed Maven config, in case you use IntelliJ, a new Kotlin-based Maven project might provide some inspiration. junit5-jupiter-starter-maven-kotlin might also be helpful.
In terms of tests to add, you could start with something similar to Assertions_assertThat_with_Groovy_strings_Test, where Kotlin specific syntax is used.
As we run our CI with all the newest versions of Java, including early access ones like 19 and 20, you might need to check if the latest Kotlin version supports all of them. The easiest way could be to create a draft PR and see if all the CI jobs are succeeding. If there are problems with certain versions, Maven profiles might help in this direction, similarly to what we have with Groovy which doesn't support Java 20 yet.


Feature Request - docker node ls --sort-by

Here is some example output of docker node ls
08lo1p3lgvwus4pdu26z8tvus *  swarm5.programster.org  Ready   Active        Reachable
5138uwpoamzthsftyw80otpqt    swarm4.programster.org  Ready   Active        Reachable
61x0ziccdy4wi200th9ddt9t8    swarm6.programster.org  Ready   Active
7tzbno6vc9pk4m7suekxadkey    swarm3.programster.org  Ready   Drain         Reachable
8m1yi1eo2n6vol6v3z44lxg7i    swarm1.programster.org  Ready   Active        Leader
ctgf1abx5c22h8eivz4sf11mf    swarm2.programster.org  Ready   Active        Reachable

It seems to me that this output sorted by ID by default which isn't particularly useful as IDs appear to be random or pseudo-random. It would make more sense to me if the list was sorted by the hostname. Better yet, it would be great if the user could manually specify what they sort by with a new --sort-by parameter that can take either id, hostname, status, availability, or manager-status as options or a comma separated list of these to sort by one and then the other.
For example: docker node ls --sort-by=manager-status,hostname

Can you please file this request against https://github.com/docker/docker? Docker CLI items are handled in that repository. Thanks.

sure thing! Thanks for letting me know.


Neither smartStep nor skipFiles doesn't work at all

VSCode Version: 1.35.1
OS Version: Windows 10

Steps to Reproduce:

clone https://github.com/zwhitchcox/vs-code-smart-step-bug-repro
Open in vscode
run yarn
run tsc -w in terminal
Set a break point at the second line of test.ts
Press F5
Press F11

Does this issue occur when all extensions are disabled?: Yes

I made a second branch with the theory that maybe it couldn't skip the entry file for some reason, so I call test from a different file, but no dice, it still doesn't work

I was able to work around this issue with the following files:
// tsconfig.json
{
  "compilerOptions": {
    "target": "esnext",
    "outDir": "dist",
    "sourceMap": true,
    "noEmitOnError": false,
    "module": "commonjs",
    "moduleResolution": "node",
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true,
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
  },
  "files": [
    "test.ts"
  ],
  "exclude": [
    "node_modules"
  ]
}

// launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Test",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/test.ts",
            "skipFiles": [
                "<node_internals>/**/*.js"
            ],
            "outFiles": [
                "${workspaceRoot}/dist/**/*.js"
            ]
        }
    ]
}

Explanation:
After consulting the docs here, I found some unrelated changes that simplified my launch.json. What really fixed the issue though, was changing from the tsconfig.json target from es6 to esnext.
This basically stops the compiler from having to generate the files for await and async.
Sorry, I can't give a better explanation, but if you look at the files, I think it should be self explanatory.


Blobstream API should be moved to node

Proofs for Blobstream (DataRootInclusionProof and ProveShare endpoints on core) are not accessible through node API, so currently all integrations with Blobstream require one to have two endpoints, and two APIs.

related: https://github.com/celestiaorg/celestia-core/issues/1306

Referencing this PR here: https://github.com/celestiaorg/blobstream-node-api/pull/1


tyxia 5610 compatibility ?

Hi
I would like to connect a second hand tydom 1.0 to home assistant to control tyxia 5610 lights and related wireless switches.
Do tout know if this hardware will work and be available and controllable in HA?
Thank you for your work

Hi,
I think so.
If these devices are X2D/X3D and that Deltadore mentioned them as compatible with a Tydom 1.0, it should work.

to connect a second hand tydom 1.0

Be also informed that the initial setup to get the 'tydom password' will be a little tricky as mentioned here (downloading an old deltadore app, etc.)

Great, thank you. It will save me to change all lights and switches installed by my home builder.


Add SINE token

[x] I will not ping the Discord about this pull request.

Please provide the following information for your token.
Please include change to the src/lib/.json and in the PR
At minimum each entry should have

Token Address: 3RSafdgu7P2smSGHJvSGQ6kZVkcErZXfZTtynJYboyAu
Token Name: SINE
Token Symbol: SINE
Logo: https://raw.githubusercontent.com/sinetoken/public/main/icon/circle_icon/circle_icon.svg
Link to the official homepage of token: https://solainetwork.com/
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

thanks has update sir

We have resolved the conflicts in the merge. Now, It can be merged directly.


improve: json modify error

Signed-off-by: Wangweizhen<EMAIL_ADDRESS>What have you changed?
add the bad parameter to error message for helping locate the problem.
What is the type of the changes?

Improvement

How is the PR tested?
Please select the tests that you ran to verify your changes:

No code

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

@lonng  PTAL

I think there is a problem while rebasing - there is an extra file

I think there is a problem while rebasing - there is an extra file

rebased. now this pr only have a commit.

/test

/merge

/merge

/merge


Fixing issue #97

Should fix the issue #97. It just cast values used for box calculation to float in order in order to prevent any integer division problem.

Parleur: Thank you!!


Compatibility With Quest Standalone (Is It Now Possible With The New LemonLoader Update?)

Hello! It says in your documentation that Fusion does not work with standalone at the moment because LemonLoader has not been updated to the new MelonLoader version. But recently LemonLoader released a new update that is now built on the new MelonLoader. I was successfully able to install LemonLoader and BoneLib on my Quest 2 using Patch 6, but the game crashed when I tried to install Fusion. When will support come back for standalone? I can't wait to be able to play with my friends, thanks!
- Kiran

Great! Thank you!


Fix for issue #936 suggested by @anonx (#939)

Thank you, @bejayoharen. It has been merged into develop (see last two commits here).
@revel/core New behaviour is introduced by this PR. There are no timeouts by-default. However, if somebody needs them he/she can use timeout.read and timeout.write options in their config/app.conf. Example:
# Timeout specifies a time limit for request (in seconds) made by a single client.
# A Timeout of zero means no timeout.
timeout.read = 300
timeout.write = 60

@anonx would it be better to have the default be a sane value? No timeout seems dangerous for a default.

I think 0 is the best default:

The timeouts are very unintuitive. For example, if you set the write timeout to 1 minute, then the server will timeout if it takes longer than one minute to upload a file. This is because, in the meantime, while uploading, nothing has been written to the socket, so it closes the connection.
Even large values could interfere with connections used for things like long-polling. (Why close a connect used for long-polling just because no data has gone through if you are still getting TCP keep-alives?) I think 0 is very sensible and sane for this use-case as well.

I think it's better to not use defaults and instead rely on lower-level TCP timeouts, file size limits and so on.

@bejayoharen time will tell what is the bet solution, but I feel if we make it clear that file uploads need a 0 timeout, then it wouldn't be bad to have safe defaults, like 60 seconds. Having no timeout makes a web app more vulnerable to DoS attacks, on purpose or on accident (high traffic spikes).

@brendensoares, Even if we decide to use some kind of default timeouts this PR is useful. It allows us to use conf/app.conf.template for that rather than hardcode something to server.go. So timeout values will be documented.

@brendensoares For DoS, I would suggest adding the ability to set a minimum data rate, configure TCP timeouts, as well as the ability to limit request sizes (perhaps separate limits for both header and body), instead of socket read/write timeouts.


Merge Slices

Right now mergo provides two options to handle slices:

WithAppendSlice - which appends all items from src to dst
WithSliceDeepCopy - which merges with override (override is mandatory and not configurable) min(len(src), len(dst)) items

There is also WithOverrideEmptySlice option, but it is little irrelevant to the discussion.
In case one needs to deep merge (not copy part of the src with override) elements of slices and add to dst items that are in src on places that are beyond len(dst), looks like there is no such an option available at the moment.
Better to show piece of code with src, dst and expected values.
Example:
type SimpleStruct struct {
	Field1 string
	Field2 string
	Field3 string
}

type StructWithSliceOfSimpleStructs struct {
	SliceOfSimpleStructs []SimpleStruct
}

src = StructWithSliceOfSimpleStructs{
	SliceOfSimpleStructs: []SimpleStruct{
		{
			Field1: "src:Slice[0].Field1",
			Field2: "src:Slice[0].Field2",
			Field3: "",
		},
		{
			Field1: "src:Slice[1].Field1",
			Field2: "src:Slice[1].Field2",
			Field3: "",
		},
	},
}
dst = StructWithSliceOfSimpleStructs{
	SliceOfSimpleStructs: []SimpleStruct{
		{
			Field1: "dst:Slice[0].Field1",
			Field2: "",
			Field3: "dst:Slice[0].Field3",
		},
	},
}
expected := StructWithSliceOfSimpleStructs{
	SliceOfSimpleStructs: []SimpleStruct{
		{
			// Original dst field is expected not to be overwritten by value
			Field1: "dst:Slice[0].Field1",
			// Empty dst field is expected to be filled with src value
			Field2: "src:Slice[0].Field2",
			// Original dst field is expected not to be overwritten by empty value
			Field3: "dst:Slice[0].Field3",
		},
		// Expected dst being appended
		{
			Field1: "src:Slice[1].Field1",
			Field2: "src:Slice[1].Field2",
			Field3: "",
		},
	},
}

Let's add new option, say mergo.WithSliceDeepMerge, (ispired by mergo.WithSliceDeepCopy) but with the functionality described.
Also it would be nice to have existing options such as mergo.WithOverride and mergo.WithOverwriteWithEmptyValue being able to tune merge process. Appending extra elements from dst to src may be done configurable as well.
I am ready to make PR with described functionality as well.

PR #234

@sunsingerus I'm marking this as a feature for v2.

@darccio any chances of merging my PR #234 into v2 ? What steps should be performed in order to get PR #234 accepted?

@sunsingerus v2 must be created, it's work in progress.

@sunsingerus v2 must be created, it's work in progress.

Any change the #234 being merged? Anything we can do to help making this feature possible?

@sunsingerus in your PR having the following structs:
type Index struct {
	Key      string
	Values   []string
	Value    string
	Required string
}

type Config struct {
	Index []*Index
}

Should the following test pass?
dst := &Config{
		Index: []*Index{
			{
				Key:      "type",
				Values:   []string{"value1", "value2"},
				Required: "true",
			},
			{
				Key:      "channel",
				Values:   []string{"value3", "value4"},
				Required: "true",
			},
		},
	}

	src := &Config{
		Index: []*Index{
			{
				Key: "*",
			},
			{
				Key: "*",
			},
		},
	}

	expected := &Config{
		Index: []*Index{
			{
				Key:      "*",
				Values:   []string{"value1", "value2"},
				Required: "*",
			},
			{
				Key:      "*",
				Values:   []string{"value3", "value4"},
				Required: "*",
			},
		},
	}

	err := mergo.Merge(dst, src, mergo.WithSliceDeepMerge)
	if err != nil {
		t.Errorf("Error while merging %s", err)
	}

	if !reflect.DeepEqual(dst, expected) {
		t.Errorf("expected: %#v\ngot: %#v", expected, dst)
	}


Cleaned-up log4j 1.2 that disables scary networking (trunk, binary-incompatible)

As discussed on the dev@logging mailing list, this PR is targeting a log4j 1.2 security fix release. This PR combines code/documentation/build system changes.
The code PR is ready for review. What does everyone think?
The result is ready for user testing. Please try to build on your own environment and then please try the resulting jar file(s) in your applications.
Besides review/test/fixing there is one more obstacle to merging: as it stands apache/log4j is a read-only git-svn mirror. I am hoping the Logging PMC will consider a switch to git for log4j 1.x, so this PR can then actually be merged in and released. This is being discussing on the dev@logging mailing list.

Thanks for all the effort @lsimons!
I have a couple questions.

Is your objective to release a one-time security update in 1.2.18 that addresses the CVEs that are open against 1.2.17?
I took a look at the CI you have set up and it looks like the build is working for JDK8 and up.  As Log4j 2.12.2 was released to support Java 7, it seems that Java 7 support would be important in 1.2.18.  Is it your intention to also support Java 7?  I'm new to GitHub actions, so I'll take a look and see if there is some obvious reason why you are not already building for Java7, such as it not being supported in GitHub actions.

One time security fix

Thanks for all the effort @lsimons! I have a couple questions.

Is your objective to release a one-time security update in 1.2.18 that addresses the CVEs that are open against 1.2.17?

Yes, basically. To be precise...
With this PR I want to make a one-time contribution that

addresses known security issues including open CVEs,
disables any/all other behavior considered 'obviously' risky from an unsupported logging library in 2021 sysadmin/ops terms (like opening server sockets or using JNDI),
is broadly backwards and forwards compatible, and
is easy to build and test from source in 2021.

From that contribution the Apache Logging PMC (which I am not on, I'm just a contributor) could then make an official release that I agree they should call 1.2.18, and that I think should be a one-time-only update.
Then if there's ever any further critical security vulnerabilities that someone wants to fix, having an easily buildable package would make it a bit easier. But I have no intention to do that kind of work.
Build: what's needed

I took a look at the CI you have set up ~and it looks like the build is working for JDK8 and up.  As Log4j 2.12.2 was released to support Java 7, it seems that Java 7 support would be important in 1.2.18.  Is it your intention to also support Java 7?~  I'm new to GitHub actions, so I'll take a look and see if there is some obvious reason why you are not already building for Java7, such as it not being supported in GitHub actions.
Update: I see now that Java actions only natively supported 8+ and you are using jabba to grab zulu JDK6, so you are actually testing on 6, 8, 11, 17.  Seems like it's necessary to add 7.  Is 6 needed?

I don't think we need to add 7. Whether 6 is strictly needed for compiling can be debated.
My intention:

a jar that works on JDK 1.4 and higher, just like 1.2.17, including 5/6/7/8/9/11/17
default build that uses JDK 6 for compiling, just like 1.2.17, for max backward/forward compatibility
alternative build that uses modern JDKs for compiling, for forward compatibility
use a relatively modern JDK for running a modern maven and its plugins, because many maven plugins require JDK 8 or higher
make sure latest JDKs also work for forward compatibility, so someone can rebuild from source next year

Build: details
It's bean rather messy to figure out the matrix of (in)compatibilities.
There's two build variants, using maven profiles. The default profile uses a maven toolchain so that maven and its plugins run using a modern JDK, while certain key plugins (like the compiler plugin, jar plugin, etc) run using a toolchain JDK.
The toolchain JDK is configured to be the venerable JDK 1.6, the same JDK that was used to produce 1.2.17, for maximum compatibility. That build is also configured to use source=1.4 and target=1.4, meaning the resulting jar is compatible with any java JDK or JRE >=1.4, including 5, 7, 8, 9, 11, 17. For this default build It should be possible to use a toolchain JDK >= 1.6 and < 9. JDK9 and later do not support source/target=1.4. But using additional toolchains doesn't really do anything: jars produced with JDK 6 work on later JDKs.
Testing with JDK 1.4 and JDK 5 needs to be done by hand, it's not really possible to automate on github actions, due to oracle's license restrictions.
The alternative no-toolchain profile doesn't use a toolchain setup. It runs maven and builds everything using a single JDK. This is configured to use source=7 and target=7, so that the resulting jar is compatible with any JDK or JRE >= 7...but it can't actually run using JDK 7, because many current maven plugins require JDK 8.
Build: building with JDK 7
Now it could be possible that using JDK 7 as (another) toolchain build works as well as JDK6, but that makes for a 3-dimensional matrix build which doesn't seem worth it.
Build: OMG it's complex!
Yeah. Thanks for reviewing it. The reason I kind of remember how to do this kind of setup is that I used to work on apache gump many years ago, which was the CI system used for log4j 1.2.

Build: building with JDK 7
Now it could be possible that using JDK 7 as (another) toolchain build works as well as JDK6, but that makes for a 3-dimensional matrix build which doesn't seem worth it.

So....I added a single build for it.
Looks like it's working fine: https://github.com/lsimons/log4j/runs/4569682928?check_suite_focus=true

Github actions was used for basic compatibility testing, results can be seen at https://github.com/lsimons/log4j/actions , these all work:

Toolchain 1.6, JDK 11, OS ubuntu-18.04
Toolchain 1.6, JDK 11, OS ubuntu-20.04
Toolchain 1.6, JDK 11, OS windows-2019
Toolchain 1.6, JDK 11, OS windows-2022
Toolchain 1.7, JDK 11, OS ubuntu-18.04
JDK 8, OS ubuntu-18.04
JDK 11, OS ubuntu-18.04
JDK 17, OS ubuntu-18.04
JDK 8, OS ubuntu-20.04
JDK 11, OS ubuntu-20.04
JDK 17, OS ubuntu-20.04
JDK 8, OS windows-2019
JDK 11, OS windows-2019
JDK 17, OS windows-2019
JDK 8, OS windows-2022
JDK 11, OS windows-2022
JDK 17, OS windows-2022

As mentioned above, compatibility with many other JREs and JDKs is also expected. In particular the toolchain build produces source/target 1.4 artifacts, so testing with 1.4 and 5 can be done.

I will close this PR in favor of the new PR #17 .
That new PR is fully source/binary compatible with 1.2.17, which was requested on the dev@logging mailing list.
It's probably a better basis to start from for an official security fix release.
(Of course feel free to take this PR instead for a trunk-development-based approach, it offers roughly equivalent security improvements.)

See

https://reload4j.qos.ch/
https://github.com/qos-ch/reload4j

for a maintained/released fork with similar security fixes.


how ratings will be bound by 0 and 5

consider matrix factorisation on data having ratings from 0 and 5 . is it quarentee that mf will bound by 0 and 5

Hi,
It's described in greater detail in the paper mentioned in README. But to answer your question, it's a simple, linear model that gives no guarantees to predict the bounded ratings. However predicting the ratings is not the point of the model, the main point is making recommendations, it was designed for this purpose. Also, remember that this is an old code, not a production quality.


[EDA] People & Groups: Account Model Settings - Account Record Types Backend

Critical Changes
Changes
Issues Closed
New Metadata
Apex Classes
AccountModelSettingsVMapper.cls
AccountModelSettingsVMapper_TEST.cls
Unpackaged Metadata
Deleted Metadata
Testing Notes

Completed testing this and it looks good.


typo in base.py

typo in setdiag documentation

Reference issue
N/A

What does this implement/fix?
single word typo in documentation.

Additional information

Merged, thanks @Corallus-Caninus


Updating via Nuget doesn't honor existing cache settings.

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am running the latest version of ImageProcessor
[x] I have verified if the problem exist in both DEBUG and RELEASE mode
[x] I have searched open and closed issues to ensure it has not already been reported

Description
When updating the ImageProcessor.Web.Config, Nuget doesn't honor any existing caching/caches/cache/settings/setting. Resulting in a duplicate that overrides the existing.
IE:
<?xml version="1.0" encoding="utf-8"?>
<caching currentCache="DiskCache">
	<caches>
		<cache folderDepth="6" trimCache="false" name="DiskCache" type="ImageProcessor.Web.Caching.DiskCache, ImageProcessor.Web" maxDays="365" memoryMaxMinutes="1" browserMaxDays="7">
			<settings>
				<setting key="VirtualCachePath" value="~/ImageProcessor" />
			<setting key="VirtualCachePath" value="~/app_data/cache" /></settings>
		</cache>
	</caches>
</caching>

Steps to Reproduce
Install any older version, update it via the Package Manager Command line: Install-Package ImageProcessor.Web.Config -Version <IP_ADDRESS> (or without specified version)
System Configuration
VS 2017

ImageProcessor version: <IP_ADDRESS>
ImageProcessor.Web version (if applicable)
Other ImageProcessor packages and versions: .MVC .PostProcessor
Environment (Operating system, version and so on): Windows 10
.NET Framework version: 4.5.2
Additional information:

(y)

Thanks for raising this but unfortunately I can’t fix this. Nuget’s diff engine simply doesn’t work properly. The bug should be raised with them.


Some quenstion about WER and other evaluation metrics

Thanks for your amazing work and I want to know if you have tested the ASR Task evaluation metrics (eg: wer) and other metrics that can be quantified?
And when I use ASR task, I also find some error ouput, for example:

Repeat the output of the same word
The model asks and answers itself. For example: the audio is "what's your favorite color？" and my prompt is your ASR prompt. But the model's output is "blue"
some special token, including [ua],[ta],, I want to konw what is causing this.
None response
Looking forward to your early reply.

We haven't tested the ASR performance of SpeechGPT on a standard dataset. The performance of the 7B model is still relatively not perfect, and its robustness on tasks like ASR is not satisfactory. Regarding the error output, due to limitations in the training data, the model may misidentify tasks, such as mistaking an ASR task for a speech dialogue task. Special tokens like [ua] and [ta] stand for 'unit answer' and 'text answer' respectively. This design is part of our chain-of-modality, and you can refer to the paper and cases of SpeechInstruct chain-of-modality datase for more details.

Thanks for your answer, SpeechGPT is a promising work. Hope you can release the 13B model as soon as possible. But I also find the model didn't response (I mean response in empty), this is not a rare phenomenon. Besides, when we use the model for asr task, we don't want special token to appear. How do I avoid these special situations?

If you want to use speechgpt for asr or tts tasks, it is recommended to use only the SpeechGPT-7B-CM and no SpeechGPT-7B-com adatper.

If you want to use speechgpt for asr or tts tasks, it is recommended to use only the SpeechGPT-7B-CM and no SpeechGPT-7B-com adatper.

thx for your answer, I will test and share you results


Implement User Wallet Page.

Title: Create User Wallet Page
Description:

Implement the User Wallet page in the application.
Ensure that the design and layout follow the provided Figma design.

Tasks:

Create the User Wallet page.
Implement UI components based on the design.
Ensure responsiveness and cross-browser compatibility.

Demo:

Acceptance Criteria:

The User Wallet page is functional and visually aligns with the design.
The page is fully responsive.

Priority: Medium/High
Assignee: I'm working on it.

@cb7chaitanya Ser, waiting for your approval to get started

@Pawank06 You can start

@cb7chaitanya i have been working on that.

@Ameerjafar Continue on it, make a PR

@cb7chaitanya Can I work on it?

@thecurioussailor i have completed just i need to make the pr.

@cb7chaitanya i have completed but the page is not responsive can i make pr.

@cb7chaitanya i have completed but the page is not responsive can i make pr.

cool! try to make it responsive and than make a pr

@Ameerjafar Make it responsive, and make a PR

large size
medium size
@cb7chaitanya is this ok?

we don't need footer i guess

@Pawank06 ok

Works just remove footer and make a PR to dev-frontend branch @Ameerjafar

@cb7chaitanya can you review the pr

@cb7chaitanya can you create some issue to work on?


Latest stable GRDB 6.29.3 documentation displays a server error message

Please describe the bug
The documentation of the latest stable version of GRDB v6.29.3 displays "An unknown error occurred."
Explain the steps needed to reproduce the bug

Navigate to https://swiftpackageindex.com/groue/grdb.swift/v6.29.3/
See the error message.

What was the expected behaviour?
A nice documentation page.
Screenshots

Not sure what happened there but something must have been messed up in the Cloudflare cache. It's working now (and presumably would have corrected itself). Do you know if the docs for 6.29.3 worked in the past? I.e. do you know for how long the page was unavailable?
I'm asking because yesterday we deployed doc generation to default to Swift 6 and we have a situation here now where 6.29.3 was generated on Sep 7 with Swift 5.10 and the other two versions, master and v7.0.0-beta.2, were generated later, with Swift 6.
I don't think it should matter but it's the only change I can think of on our end that could have affected the 6.29.3 docs.

Not sure what happened there but something must have been messed up in the Cloudflare cache. It's working now (and presumably would have corrected itself).

https://swiftpackageindex.com/groue/GRDB.swift/v6.29.3/documentation/grdb works on Chrome but is still broken on Safari.
On Safari: I paste https://swiftpackageindex.com/groue/GRDB.swift/v6.29.3/documentation/grdb and see an error message. The URL was automatically changed to https://swiftpackageindex.com/groue/grdb.swift/v6.29.3/. I hit Refresh in the browser, and now I see 404 - Not Found.

Do you know if the docs for 6.29.3 worked in the past? I.e. do you know for how long the page was unavailable?

Yes, it has been working well since 6.29.3 has shipped on September 7. I sent links to users a couple of times since then.
We had an issue three days ago, #3407. After it was fixed, 6.29.3 was still online.
So the error started to happen somewhere after that.

I'm asking because yesterday we deployed doc generation to default to Swift 6 and we have a situation here now where 6.29.3 was generated on Sep 7 with Swift 5.10 and the other two versions, master and v7.0.0-beta.2, were generated later, with Swift 6.

Yes, the Package.swift has changed between of 6.29.3, and master = 7.0.0-beta2:
// swift-tools-version:5.7 <- GRDB 6.29.3
// swift-tools-version:6.0 <- GRDB 7.0.0-beta.2 and master

On Safari: I paste https://swiftpackageindex.com/groue/GRDB.swift/v6.29.3/documentation/grdb and see an error message. The URL was automatically changed to https://swiftpackageindex.com/groue/grdb.swift/v6.29.3/. I hit Refresh in the browser, and now I see 404 - Not Found. (Maybe because a problem of case: GRDB vs. grdb in the URL)

I suspect you are still seeing some cached files. I just tested with Safari now and do not see any of these issues. I did not get redirected from https://swiftpackageindex.com/groue/GRDB.swift/v6.29.3/documentation/grdb and do not see any errors.

You must be right. On my phone it works now. 👍

Thank you!

I had to follow a five steps procedure:

Safari > Settings…
Privacy
Manage Website Data
Search for swiftpackageindex
Hit Clear

Maybe SPI store something in the local storage? That's a weakness.

Maybe SPI stores something in the local storage? That's a weakness.

We do not. We only have one piece of code which accesses local storage and that's to show/hide a completely optional debug panel that we use for debugging and that people using the site would never need. It is referenced here: https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/blob/66c690ecb8cf8a03d9db6d51459b4d4a24e6bd27/FrontEnd/scripts/debug_panel.js#L20
We do not store any cookies or other local storage.
I don't believe that DocC uses local storage, either. I can see no trace of it doing so in the web inspector but if it does then that's an issue for the DocC team rather than here.
Browsers love to hold on to their caches. I don't know why it's so hard to bypass them, but it is nothing we are doing.

For me, ⌥⌘E in Safari has always sufficed to reset caches. I have the habit of hitting it multiple times, which I'm sure is a critical part of making it work 😬

Thank you both for your support!


Fixes #1678 - added external auth token exchange

Coverage: 94.033% (+0.02%) from 94.015% when pulling 087423ef2af3057cbfab337a0934351fcceda059 on cody-external-auth-token-exchange into 8c6d4edb625bc39232253f4e7af653a566f85ca2 on main.


Add support for Mopidy

Describe the solution you'd like
It would be great if we could add a Mopidy container that can be used and shared to all the rooms, with the ability to mount a USB drive with audio on it.

@shaunmulligan Are you specifically interested in Mopidy?  Or would MPD work for you case as well?  I am playing around with MPD right now, for other reasons.  But I'm not yet clear on the differences between the two, and whether they are interchangeable.  I did see this morning that one of the MPD clients I tried on Android said it is not compatible with Mopidy.  From what I've read, Mopidy looks like an off-shoot of MPD.

Hello,
I'm also looking for a way to connect RadioDroid to BalenaSound (or boombeastic https://github.com/balenalabs/boombeastic/issues/59 )
My use case would be to cast webradios listed on https://www.radio-browser.info/ through RadioDroid Android application to a Raspberry Pi 2 model B (which doesn't have bluetooth support)
https://github.com/segler-alex/RadioDroid/issues/936
RadioDroid seems to have MDP support.
Kind regards

I am not the OP, but Mopidy provides a websockets interface which makes it nice to control from a web UI.  That would be one reason to use a Mopidy implementation over other mpd servers.

To follow up, since you can run Mopidy as either client or server nodes, it would be really nice to share configuration.
https://www.home-assistant.io/blog/2016/02/18/multi-room-audio-with-snapcast/

Any update on this?
I'm looking for the same solution.

Any update on this?
I'm looking for the same solution.


Missing sniff in project.ruleset.xml.example breaks PHPCS

When I use the example ruleset (project.ruleset.xml.example) from the repository I get the following error:
Fatal error: Uncaught exception 'PHP_CodeSniffer_Exception' with message 'Referenced sniff "WordPress.Functions.FunctionCallSignature" does not exist' in /Users/lgaechter/.composer/vendor/squizlabs/php_codesniffer/CodeSniffer.php:1122
I’m completely new to PHPCS’s rulesets, but changing
<exclude name="WordPress.Functions.FunctionCallSignature" />

to
<exclude name="PEAR.Functions.FunctionCallSignature" />

solved it for me. It guess since it was deleted in https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/eb3cc6c59d4991d3e5e78c4c020936ff1c66214b?diff=unified#diff-6af8d9fa23796c0c8792547a27017150L48 the exclude can’t be found in the example ruleset anymore?
Now I’m not sure whether excluding PEAR.Functions.FunctionCallSignature inside <rule ref="WordPress-Core"> is good practice or whether it should be excluded in another rule?

FYI: I've seen similar issues in the past when I was using an older PHPCS version. Since upgrading to the latest PEAR version, I haven't seen this type of error anymore.
Not sure what version of PHPCS you are on, but it may help.

Now I’m not sure whether excluding PEAR.Functions.FunctionCallSignature inside  is good practice or whether it should be excluded in another rule?

I think it really doesn't matter either way, but I'm actually not entire sure.


Remove warning about empty element

I added a warning to the constructor of Lib.StatefulWidget with the idea that these should always be constructed with an existing DOM element. As it turns out there are many places in our code where we don't pass a valid selector, and this seems to be common practice. Given this, displaying the warning is more of an annoyance and I took it out again.

:+1:


Create a list of pages

How could I get a list of pages and use the translated title form the subset?
Here the idea form the Jekyll example page:
https://github.com/jekyll/example/blob/gh-pages/_includes/header.html#L15-L21
Basically I would like to create some sort of navigation.
I'm not sure how to achieve something like this. Looks like I can't get the title through this:
{% for p in site.pages %}
  {{ p }}
{% endfor %}

Also my non existent ruby skills don't help...

You can do this exactly the way you want except that you have to check if the language is equal to the currently rendered language.
{% for page2 in site.pages %}
  {% if page2.language == page.language %}
    {% if page.title %}
      {{ page2.title }}
    {% endif %}
  {% endif %}
{% endfor %}

I have changed the local page variable into page2 to retain access to the currently rendered page.

I have improved the example site and included the above snippet with an option to disable the navigation entry for a given page.

That helped me a lot. Thanks for your support! :relaxed:


Axis (x,y) wanted

Hi, great plugin!
It will be great if there will be an axis option (X, Y)

Native drag'n'drop — does not support this feature.

Seriously? I'm off to use jQuery sortable.

Cannot understand why this issue will not be considered. There are lot of cases why "axis" makes sense. My project mainly use "standard" drag'n drop, but i have a single case why its needed. Do you mean is not possible with "forceFallback: false"? Any chance to make it available in fallback mode or any hint how i can force that e.g. transformX is not used?

@ideaweb That was exactly my scenario (2/3 of our apps sortables benefited from being native and snappy, but one needed to limited to the y axis), so I forked it. It's just a tiny change (https://github.com/friday/Sortable/commit/ebfa4b266259d46b87be82854354b1cfd8a994cc). The maintainer only wants to support the feature set native dnd can do it seems.

@friday that gets you your first star 😉

@friday Thx a million... now i can reorder in my web app the tabs on x-axis like Google Chrome, Safari etc. I know that browsers have still extra feature "tab to window" which is "native" but for just reordering its still on x-axis and not native. I know for reordering tabs is not really needed and would work with "native" fine, but for usability i think to let it it on x-axis its much better.

Guys, has anyone managed to block the x or y axis?


Update README.md

Connection with issue(s)

Close #???

Connected to #???
Solution description
Screenshots or Videos

To Do

[ ] Check the original issue to confirm it is fully satisfied
[ ] Add solution description to help guide reviewers
[ ] Add unit test to verify new or fixed behavior
[ ] If apply, add documentation to code properties and package readme

Can we just leave the image banner at the top? It's my favorite part! otherwise LGTM

@caseycrogers I think it takes too much space, but anyways i've moved it back to the top now.


Cardinal Component Incompatibility

Mod Name
Cardinal component
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/cardinal-components-api
Describe the bug
Still have a crash in last versions of everything
Steps to reproduce

Install cardinal component api
Launch minecraft

i can provide a .zip of my instance if needed
Logs
https://pastebin.com/0HVZ2xPg
Additional context
No response

Fixed in 1a47e049297b3f62d3963123ab2700ca12e93fbc, will be available in the next release.
See also: #136


bug(_MatMenuBase): Class '_MatMenuBase' incorrectly implements interface 'MatMenuPanel'

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Error in compilation with "strictNullChecks": true in tsconfig.json

Reproduction
Steps to reproduce:

Add Angular Material [14.1.3] Library
Set "strictNullChecks": true in tsconfig.json
Try to Compile Angular App

Expected Behavior
Angular App Successfully Compile
Actual Behavior
Angular App Compile Error
Environment

Angular: 14
CDK/Material: 14.1.3
Browser(s): Chrome 104
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10 Pro

What version of TypeScript are you using? We have strictNullChecks enabled in our repo and this hasn't shown up in our build.

Typescript "^4.7.4" @crisbeto

I got the same error when enabling exactOptionalPropertyTypes after updating from Angular 12 -> Angular 13 with typescript 4.6.4. (tried to enable exactOptionalPropertyTypes as it is recommeded but ran into this problem)

Duplicate of https://github.com/angular/components/issues/24078.


Inconsistent color scheme in the Combinational Analysis Tool

Describe the bug
The Combinational Analysis Truth Table has a green and white color scheme which isn't consistent with the theme of the simulator.
To Reproduce
Steps to reproduce the behavior:

Go to Simulator Beta Version
Click on Tools - > Combinational Analysis
Enter the variables to see the table.

Expected behavior
A color scheme more consistent with the simulator theme
Screenshots
If applicable, add screenshots to help explain your problem.

Are you working on this issue? (Yes/No)
No, open for triage

@nitin10s @abstrekt is this intended?

@nitin10s @abstrekt is this intended?

definitely not, missed this element

As far as I remember, this was designed in a way to look different from all other elements deliberately? And it should ideally change as we change the theme.
But I strongly believe this can be improved and incase someone has a design in mind, pls do suggest.

As far as I remember, this was designed in a way to look different from all other elements deliberately? And it should ideally change as we change the theme.
But I strongly believe this can be improved and incase someone has a design in mind, pls do suggest.

@nitin10s

have a look  on this combination...

The only color-changing per theme is the 1st row

hey is anyone working on this issue ?
i would love to work on this issue .

@abstrekt @nitin10s @sal2701,  please have a look at this one.. is this ok?

@abstrekt @nitin10s @sal2701 @gr455, please have a look at this one.. is this ok?

Looks good to me

Looks good to me as well

@gr455 @nitin10s, So, can I make a pull request for this change?


Feature Request: GUI that runs in Windows Environment

Would it be possible to create a GUI version that runs in the Windows Environment? Something similar to how JAVScrapper currently does it with Java.
JAVscrapper hasn't been updated in quite a while

Unfortunately I don't have any experience developing GUI or web-front ends, but I did play around with creating a simple web frontend that can be hosted via docker or on Windows.
I may try enhancing that functionality, but no guarantees it will be anywhere near as robust as javmoviescraper.
https://gfycat.com/courageousangryiguana

Thank you. The web frontend looks promising. Look forward to testing the web frontend on a Windows machine.

@jvlflame I'm sure if you create a repo for it, people would contribute to it. :)

@DarkMask100 I'm actually developing it using PowerShell Universal which is probably the easiest way to get a quick GUI frontend for Javinizer.
I'm not sure I want to create a new repo for it yet, but I should have some more progress to show soon.

I've put out an alpha release for the web GUI that I'm working on.
Feel free to test or offer any feedback!

I'm not really a tech person, so installing Docker and related stuff was really a challenge. Managed to have the Javinizer module installed and launched. However, as I did not know how to provide Docker access to my video files, was unable to test its functionality.
Ideally, the Javinizer would be able to run natively in Windows, without having to install any Docker, enabling virtualization etc.

@cavalia88 Going to be updating documentation soon to include instructions on how to setup without Docker.

With 2.1.6, better documentation has been added for installation instructions for Windows (without Docker).
Docs now live on GitBook here.
Development for the GUI will continue alongside improvements to the Javinizer CLI. Let me know if you have any feedback or questions.


edit docker command in README.md

added the missing slash mentioned in issue #287

Codecov Report

Merging #289 (051180a) into master (b4e0143) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #289   +/-   ##
=======================================
  Coverage   83.26%   83.26%
=======================================
  Files          68       68
  Lines        1942     1942
=======================================
  Hits         1617     1617
  Misses        224      224
  Partials      101      101

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks!


ovirtbmc: Fix cache handling

When we never use power on/off commands, 'target_status' is 'None'
and the VM stays in 'vm_changing_state' forever. Let's add a condition
to see if we ever used the power on/off commands.
Signed-off-by: Marcin Sobczyk<EMAIL_ADDRESS>

fixes #15


Installation gogs problem suburl This page contains redirect loop

gogs Version: 0.5.13
go 1.4
Today gogs want to install suburl.chrome prompted 'This page contains a redirect loop.'
root_url <IP_ADDRESS>:3000/gogs, the page redirects to stop http://<IP_ADDRESS>:3000/gogs/install.
Root path no problem. Are there friends have the same problem?

Hi, thanks your feedback!
Suburl tends to work with Nginx/Apache reverse proxy, if you literally add a Suburl, that's not gonna work.

Thank you, using nginx reverse proxy installed properly.

No problem!


Writing large XML files efficiently

 Issue by mgax
Monday Oct 21, 2013 at 18:50 GMT
Originally opened as https://github.com/PyWPS/pywps-4/issues/6

I'm experimenting with handling the contents of an Execute request in an iterative fashion, so that we can handle requests with a large embedded data file. My idea is to parse the request iteratively, save any ComplexInput in a temporary file, remove it fron the XML, and build an in-memory document out of everything else.
I've hit on this roadblock: how to write XML files efficiently, as a stream, from Python? lxml has nice support for iterative parsing, but not for writing. There's the built-in xml.sax.saxutils.XMLGenerator but it's incredibly slow, writing just over 1MB/s on an Intel I7 machine.

 Comment by mgax
Monday Oct 21, 2013 at 18:59 GMT

Also posted on StackOverflow.

 Comment by jorgejesus
Tuesday Oct 22, 2013 at 10:10 GMT

holly jesus o_O
On Tue, Oct 22, 2013 at 11:16 AM, Alex Morega<EMAIL_ADDRESS>
The xpath command is actually a bit slower, and I think it buffers the
output in memory, it uses 93MB of memory to output the 10MB XML file.
—
Reply to this email directly or view it on GitHubhttps://github.com/jachym/pywps-4/issues/6#issuecomment-26788010
.

--
OpenPGP Key: 0x7212572C

 Comment by jorgejesus
Monday Oct 21, 2013 at 20:15 GMT

hmm
I think that the iteractive aproach was(is) a good idea,
what about using xpath to extract the ComplexInput into the disk ?
How fast is xpath compared to interactive parsing??
On Mon, Oct 21, 2013 at 8:59 PM, Alex Morega<EMAIL_ADDRESS>
Also posted on StackOverflowhttp://stackoverflow.com/questions/19502503/how-to-stream-xml-output-quickly-from-python
.
—
Reply to this email directly or view it on GitHubhttps://github.com/jachym/pywps-4/issues/6#issuecomment-26745693
.

--
OpenPGP Key: 0x7212572C

 Comment by mgax
Tuesday Oct 22, 2013 at 09:16 GMT

The xpath command is actually a bit slower, and I think it buffers the output in memory, it uses 93MB of memory to output the 10MB XML file.

 Comment by imperialguy
Wednesday Nov 26, 2014 at 17:15 GMT

Did you try loxun?

 Comment by jachym
Tuesday Oct 22, 2013 at 18:45 GMT

Thank you Alex pro picking this topic.
I have no idea :-D, but it's crucial question!
I was approaching similar way (in PyWPS 3.x, saving content of
ComplexInput somewhere), but I used DOM - which apparently is not the
way, we shall approach.
For writing, I used templates - originally, in PyWPS 2.x or so, I used
simply text output - so writing xml tags directly as strings... not the
nicest way, but should work?
Jachym
Dne 21.10.2013 20:50, Alex Morega napsal(a):

I'm experimenting with handling the contents of an Execute request
in an iterative fashion, so that we can handle requests with a large
embedded data file. My idea is to parse the request iteratively, save
any ComplexInput in a temporary file, remove it fron the XML, and
build an in-memory document out of everything else.
I've hit on this roadblock: how to write XML files efficiently, as a
stream, from Python? lxml has nice support for iterative parsing, but
not for writing. There's the built-in xml.sax.saxutils.XMLGenerator
but it's incredibly slow,
writing just over 1MB/s on an Intel I7 machine.
--- Reply to this email directly or view it on GitHub:
https://github.com/jachym/pywps-4/issues/6

--
Jachym Cepicky
jachym.cepicky at gmail.com
http://les-ejk.cz
PGP: http://les-ejk.cz/pgp/JachymCepicky.pgp


vhci-hcd missing from kernel-uek-modules-extra

The vhci-hcd driver is missing in the x86_64 version of package kernel-uek-modules-extra
This means that usbip bind fails...
Note that the aarch64 version does include both usbip-host.ko.xz and vhci-hcd.ko.xz
It seems to effect both OL8 and OL8 (UEK)
https://pkgs.org/download/kernel-uek-modules-extra
You can quickly check this as well using
ls /lib/modules/$(uname -a | cut -d' ' -f3)/kernel/drivers/usb/usbip

It's not surprising that this module is missing from the UEK modules, as this kernel is not necessarily built for desktop use cases. Though it is strange that it's there in the aarch64 version. What is your use case?

Yes, it should be included, like in the aarch64 version.
(My personal use case is simple; I want to use an USB webcam on my home server. A bit silly; I run whatsapp inside an android VM. Need to authenticate using QR and cam to access whatsapp using a browser on a desktop pc.  Could also use a long usb cable but where's the fun in that?)
More serious applications include usage of various USB-based devices over the network, from scanners and printers to whatever. I guess it's not much work to fix this issue as aarch64 already includes the good stuff.


EPPO download not working

For the last week or two the EPPO data download from https://data.eppo.int/files/xmlfull.zip has failed mid-stream. We have had other issues with using EPPO, so we might consider replacing it with GBIF data.
The only places we use their data are in weedcoco.utils.get_supercategory_names and weedcoco.validation.check_plant_species_format to get ancestry of a taxon, and to check validity of a taxon.
We can instead adopt GBIF... Port the code from the frontend to Python looks something like:
def get_ancestry(name):
    results = requests.get(f"https://api.gbif.org/v1/species?name={urlencode(name)}&datasetKey=d7dddbf4-2cf0-4f39-9b2a-bb099caae36c&taxonomicStatus=ACCEPTED")
    assert results["endOfRecords"]  # TODO?: pagination
    gbif_record = next(record for record in results["results"]
                       if record["canonicalName"].lower() == name
                       and record["taxonomicStatus"] == "ACCEPTED")

    return {rank: record[rank]
            for rank in ["kingdom", "phylum", "order", "family", "genus", "species"]
            if rank in record}

Now working


Error: Cannot find module '@babel/runtime/core-js/object/keys'

Hello. Just installed successfully but when running waka setup I get this:
internal/modules/cjs/loader.js:605
    throw err;
    ^

Error: Cannot find module '@babel/runtime/core-js/object/keys'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:603:15)
    at Function.Module._load (internal/modules/cjs/loader.js:529:25)
    at Module.require (internal/modules/cjs/loader.js:657:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/@jaebradley/wakatime-cli/build/services/formatAggregatedStatistics.js:1:270)
    at Module._compile (internal/modules/cjs/loader.js:721:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:732:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
    at Function.Module._load (internal/modules/cjs/loader.js:552:3)

@ronilaukkarinen thanks for opening this issue and sorry you were running into problems getting setup!
I just published 1.1.6 which incorporates changes from #43. This includes updating the CLI's @babel/runtime dependency.
If you install 1.1.6 do you still run into issues?
If so, do you mind posting your npm and node versions?

Yay, it works now! Thanks!


What's the library "rectangles" imported in the code?

I can't find the library "rectangles" via "pip(3) install" and Google. Is this a custom module that you guys forgot to commit to github? Or how can I find this library? Thanks!

Oh! I find the function "mnist_1hot_all()" in classify_gp.py.


Fix ordering of network firewall rules sent to router

ACS PR #1581
Author: pdube
Integration tests are green: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic/job/0002-tracking-repo-branch-build/125/

Ping @borisroman


Switch to nrfutil toolchain-manager breaks prior build pipelines

After the updates brought through in #75, our CI/CD pipelines were failing due to the chain from Zephyr to the nrfutil toolchain manager. For instance, we saw the following
$ZEPHYR_BASE/scripts/twister -p native_posix --testsuite-root ./app/tests
bash: /scripts/twister: No such file or directory

This has also come with an increase in build image size from 3.64GB to 9.11GB, which greatly increased the time for our pipelines to run.
For other users: we resolved this by changing our image from the :v2.2-branch to a previously working image (in our case nordicplayground/nrfconnect-sdk@sha256:cb56598a977a2a615634417bcf4107752646b0a1c5dba373eaf8d01633455d8b, this will obviously change depending on what toolchain version was being used).
Recommendation would be for there to be some information about how to use the new images to create CI/CD pipelines.

Supporting CI builds beyond what's documented and implemented in the workflows in the repo is unfortunately out of scope.
I am using the ideas outlined in this repo here in a pipeline so this could be used for you as a reference: https://github.com/hello-nrfcloud/firmware/blob/a4e66d3017270e4c4de3748d16fdd8a3f9f4bd49/.github/workflows/build.yml

If you have a suggestion that reduces the image size, please open a PR.


Possible misuse of comma operator in enum

I am seeing a lot of 'Possible misuse of comma operator here' warnings in the generated code for enums.
Is the correct way to solve this adding #pragma clang diagnostic ignored "-Wcomma" to EnumRewriter.java?

Looks like it may be possible to silence -Wcomma warnings by selectively casting the first operand to void, similar to how we handle statement expressions with non-void results.
http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20160215/150637.html

fixed in #900


Rename $IsOSX to $IsMacOS

PS-Committee decided we should be consistent with our naming and conform to Apple's use of macOS instead of OSX, however, for readability and consistently we are staying with Pascal casing.
Also renamed instances of variations of OSX to macOS for consistency in comments/text (separate commit to make it easier to review)
Fix https://github.com/PowerShell/PowerShell/issues/4700

I don't see changes to build.psm1, is that file missed from this PR?

@daxian-dbw not sure how I missed that, will fix

Apple Inc.  uses macOS not MacOS - maybe we should use the same too? - $IsmacOS

@iSazonov we had that discussion in the issue, the consensus is that $IsMacOS is preferred over $IsmacOS for readability and other languages (like Java) use isMacOS, so it's already somewhat common.

Should this run through the CI with [feature] to ensure none of the feature tests broke with the change?

@markekraus good point, I'll resubmit

AppVeyor failure is due to the current issue causing nightly to fail and @dantraMSFT is looking into it

Yes, the failure is due to https://github.com/PowerShell/PowerShell/pull/4763. You can ignore it.

Rebased to pick up fix


npm i @nexus/schema stuck in node_modules\iterall

When i try to install nexus/schema it stuck on this:
npm i @nexus/schema
[            ......] - finalize:iterall: sill finalize C:\my\apps\node_modules\iterall

And then i get error:
npm ERR! code ENOENT
npm ERR! syscall rename
npm ERR! path C:\my\apps\node_modules\tslib
npm ERR! dest C:\my\apps\node_modules\.tslib.DELETE
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\my\apps\node_modules\tslib' -> 'C:\my\apps\node_modules\.tslib.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

Log last lines:
87 timing stage:runTopLevelLifecycles Completed in 63969ms
88 silly saveTree<EMAIL_ADDRESS>88 silly saveTree `--<EMAIL_ADDRESS>88 silly saveTree   +--<EMAIL_ADDRESS>88 silly saveTree   `--<EMAIL_ADDRESS>89 warn<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
90 verbose stack Error: ENOENT: no such file or directory, rename 'C:\my\apps\node_modules\tslib' -> 'C:\my\apps\node_modules\.tslib.DELETE'
91 verbose cwd C:\my\apps
92 verbose Windows_NT 10.0.19041
93 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" "@nexus/schema"
94 verbose node v14.15.0
95 verbose npm  v6.14.8
96 error code ENOENT
97 error syscall rename
98 error path C:\my\apps\node_modules\tslib
99 error dest C:\my\apps\node_modules\.tslib.DELETE
100 error errno -4058
101 error enoent ENOENT: no such file or directory, rename 'C:\my\apps\node_modules\tslib' -> 'C:\my\apps\node_modules\.tslib.DELETE'
102 error enoent This is related to npm not being able to find a file.
103 verbose exit [ -4058, true ]

Deleting node_modules folder didn't help.
I was able ro resolve the problem insalling graphql before nexus/schema, but it's not convenient

This seems unrelated to nexus if the issue was resolved by installing graphql before.
Nexus only specifies a peer dependency to give flexibility to the user.


Intermittent error while patching components

Description:
Below error is getting rarely when trying to patch a component following https://github.com/wso2-cellery/samples/blob/master/docs/pet-store/cell-component-update-and-adv-deployment.md
Observed in GCP full setup
cellery patch pet-be controller --container-image wso2cellery/samples-pet-store-controller:latestv2
❌ Patching component controller in instance pet-be
Unable to patch cell component controller in instance pet-be: unexpected end of JSON input
Since this is an intermittent and rare issue, let's add debug logs which is getting printed to a dedicated file (I think we already have) so that we can debug in the future.

Let's just add debug logs if possible.

I was able to reproduce this for the first time when I patch a component of an instance. For example, I start an instance with name = pet-be, and very first time when I execute the patch command, I got this error; and consecutive attempts succeeded. I again started the pet-be instance with the same name, and didn't encounter the error.
Then I started the instance with name = bar, and then again first time I received this error. Consecutive attempts succeeded.

Had a look, and could re-produce in random occasions. Could be due to how we read the command output from the terminal. This error has been noted in the CLI previously as well, and have use a method dump the complete output to a file and then read from it to overcome the issue. Have modified the relevant places to do the same in https://github.com/wso2-cellery/sdk/pull/758. Could not reproduce this afterwards.

Verified, the error doesn't come any more.