Check privacy-pass hash to point method

We are currently using the deprecated one, should we switch ?
https://github.com/privacypass/challenge-bypass-extension/blob/master/src/ext/config.js#L114-L117
/**
 * DEPRECATED: Method for hashing to curve based on the principal of attempting
 * to hash the bytes multiple times and recover a curve point. Has non-negligble
 * probailistic failure conditions.
 * @param {sjcl.bitArray} seed
 * @param {sjcl.hash} hash hash function for hashing bytes to base field
 * @param {sjcl.bitArray} label
 * @return {sjcl.ecc.point} returns a curve point on the active curve
 */
function hashAndInc(
  seed: sjcl.BitArray,
  hash: sjcl.SjclHashStatic,
  label: SjclHashable

https://github.com/privacypass/challenge-bypass-extension/blob/master/docs/HASH_TO_CURVE.md#hash-and-increment

This would have to be coordinated with the backend, I'm not sure if the challenge bypass server supports that new version. The main reason to switch appears to be that there's no probabilistic failure condition where you need to hash some unknown number of times. As it's mostly just a matter of performance I'm comfortable keeping hash and inc for now.

Yeah, I don't think it's an issue really now that I understand what it's doing. I just made a note of it


[Feature][plugins] add plugin-spark-sink-redis #733

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] Change does not need document change, or I will submit document change to https://github.com/InterestingLab/seatunnel-docs later

Hi, Is there any response?

Thank you for your contribution, if there is no other reason, we'd better not reopen a PR for this, he will lose the previous review. I will close this PR.


Array.prototype.sort - remove the need for compareFn to handle undefined values

Array.prototype.sort - remove the need for compareFn to handle undefined values

Fixes #41708

IMO a: Exclude<T, undefined> is a bit cleaner

Happy to switch to a: Exclude<T, undefined> if that’s clearer. However I will await review and confirmation before switching :)

The original issue #41708 needs to be added to https://github.com/microsoft/TypeScript/issues/36554 before it will be accepted. In the meantime, I'd vote to close the PR because code tends to go stale pretty fast.

We just need to make time to work through all issues with a significant update to Array. So far it hasn't made it to the front of our queue, though.

To help with PR housekeeping, I'm going to close this PR until we finally update Array types.


Fun faqs

Also activate readline for LisspREPL. Was writing a FAQ about rlwrap, but figured out how to do this instead.

The "fun" is for "functional". What did you think it meant?


chore: use go-1.21

Description

I have small suggestion can we do after the release of umee  with cosmos-sdk 47


Remove legacy CountMinSketchMonoid

Current coverage is 80.36% (diff: 100%)

Merging #602 into develop will increase coverage by 0.07%

@@            develop       #602   diff @@
==========================================
  Files           114        113     -1
  Lines          4932       4931     -1
  Methods        4506       4505     -1
  Messages          0          0
  Branches        425        425
==========================================
+ Hits           3960       3963     +3
+ Misses          972        968     -4
  Partials          0          0

Powered by Codecov. Last update fe78e57...7b84256


Grouping doesn't work with flowcell inputs

Description of the bug
post alignment grouping doesn't work correctly with flowcell inputs
Command used and terminal output
No response
Relevant files
No response
System information
No response

Fixed in #41


Expose hostNetwork customization

Opening issue for discussion as requested in https://github.com/containous/traefik-helm-chart/pull/49.
I want to be able to run Traefik in the host network namespace when I deploy it with this chart for the following potential scenarios:

I don't want to use a cloud provider load balancer in front of Traefik due to cost or redundancy.
I want to run Traefik on bare metal and don't have the option of fronting it with another load balancer.
I need my Traefik pods to have the Node IP as the Pod IP (to use with, for example, https://github.com/kubernetes-sigs/external-dns which will automatically create a DNS record pointing to that IP)

For any or all of these use cases, I need to be able to run my Traefik pod in the host network because:

binding to port 80/443 is restricted (by default k8s only allows NodePort > 3000)

As noted in the Traefik Team reply here and included in my original PR, this will also require some anti-affinity rules to be added to force Traefik pods to spread out among the nodes.
@mmatur do you have any questions about this?

Hello @rbtr,
Thanks for opening this proposal. This is a topic that comes up fairly often, and there are definitely use cases where using hostNetwork/hostPort is useful.
The first issue is that hostPort and hostNetwork configurations are discouraged, and usually not supported in production environments due to the issues they cause. The kubernetes best practices guide explicitly states this: https://kubernetes.io/docs/concepts/configuration/overview/#services
I will respond to your scenarios one at a time to hopefully give some more insight:

I don't want to use a cloud provider load balancer in front of Traefik due to cost or redundancy.

Reducing cost shouldn't be a reason to add risk-introducing features.

I want to run Traefik on bare metal and don't have the option of fronting it with another load balancer.

If you are running on bare metal, you should be looking at metalLB or other solutions, because you will need to get traffic into your cluster in a reliable way, with failover taken into account.

I need my Traefik pods to have the Node IP as the Pod IP (to use with, for example, https://github.com/kubernetes-sigs/external-dns which will automatically create a DNS record pointing to that IP)

Again, if you are using something like metalLB, you don't need this, as your DNS records would be based on your fronting LB, instead of the pods running behind it.

binding to port 80/443 is restricted (by default k8s only allows NodePort > 3000)

Solutions like MetalLB do handle this, and don't run into the issues with daemonsets that Traefik does.
Hopefully this gives some more insight as to why we are extremely hesitant to add hostNetworking to this chart.

I hear what you're saying about it being discouraged, but it is still an option. The Traefik helm chart could pass on that choice to the end user, and do a helpful thing in applying an anti-affinity if the user opted to use the host network.
I can lay out my use case if you like, but I typed it out a few times and the wall of text is :-1:
Suffice to say, I tried lots of ways to build a spaceship out of the lego available to me and running Traefik in the hostnetwork is the best solution - I will continue to do that, and I think it's a valuable enough usage that it should be an option in the official helm chart. Also I really don't want to have to maintain a fork for my env with only this change :slightly_smiling_face:

I think this would be very useful. NGINX Ingress already has this option.

yeah, stable/traefik chart also have that option. My use case is external load balancer, which is controlled outside of k8s. So I could create LB with terraform for example, and point it to specific ports, exposed on worked nodes by traefik & hostport. And I don't want to use any nodePorts because of kube-proxy routing requests from nodes, where traefik is not even running to actual pods. So it's 👍 from me!

Thanks for all your feedback. We have reopen #49

Appreciate you all considering this and all the work you do on the project :slightly_smiling_face:
I updated my linked PR with the feedback here


Undo doesn't work with Japanese text

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Undo doesn't work for Japanese letters I input with IME.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/gmertk/e61z7nfa/.
Turn IME on and  enter Japanese letters such as "あいうえお". Then hit undo key(⌘Z on Mac or ^Z on Windows) for undo.
I can reproduce issue with sample at https://draftjs.org/ .
What is the expected behavior?
Letters should be deleted with undo key.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?

Draft v0.11.1
macOS 10.14.6/Safari 13, Chrome 76
Windows 10 Chrome 76

I have been frustrated with this bug almost every day for over a year since I started using Twitter on my browser when my favorite native desktop client was died by their user-stream termination.
Today finally I found steps to reproduce this bug after six months of research.
This is my report movie.
https://twitter.com/omochimetaru/status/1228370998811971585
And I found this issue here and despaired to know that this report was up in September 2019.
Anyway, what I want to say is that this bug should be suffering from so many Japanese people and it would be nice if it fixed.
My environment:
macOS, Safari, Google Japansese Input
I also posted almost same message at #2194.
But it does not intend to spam, a report movie URL is different which corresponds to issue topic.


Maintenance: Add Ruff as the linter

Why is this needed?
Ruff is an extremely fast Python linter and code transformation tool, written in Rust.
Ruff can be used to replace Flake8 (plus dozens of plugins), isort, pydocstyle, yesqa, eradicate, pyupgrade, and autoflake, all while executing tens or hundreds of times faster than any individual tool.
https://beta.ruff.rs/docs/
Which area does this relate to?
Tests, Automation
Solution
No response
Acknowledgment

[X] This request meets Powertools for AWS Lambda (Python) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

YES! Make sure to take note of the speed improvement in CI too (this should
decrease our installation step + linting, and make pr both locally and in
CI)
On Mon, 5 Jun 2023 at 19:53, Leandro Damascena @.***>
wrote:

Why is this needed?
Ruff is an extremely fast Python linter and code transformation tool,
written in Rust.
Ruff can be used to replace Flake8 https://pypi.org/project/flake8/
(plus dozens of plugins), isort https://pypi.org/project/isort/,
pydocstyle https://pypi.org/project/pydocstyle/, yesqa
https://github.com/asottile/yesqa, eradicate
https://pypi.org/project/eradicate/, pyupgrade
https://pypi.org/project/pyupgrade/, and autoflake
https://pypi.org/project/autoflake/, all while executing tens or
hundreds of times faster than any individual tool.
https://beta.ruff.rs/docs/
Which area does this relate to?
Tests, Automation
Solution
No response
Acknowledgment

This request meets Powertools for AWS Lambda (Python) Tenets
https://awslabs.github.io/aws-lambda-powertools-python/latest/#tenets
Should this be considered in other Powertools for AWS Lambda
languages? i.e. Java
https://github.com/awslabs/aws-lambda-powertools-java/, TypeScript
https://github.com/awslabs/aws-lambda-powertools-typescript/, and
.NET https://github.com/awslabs/aws-lambda-powertools-dotnet/

—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/issues/2380, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZPQBBRIR4VDSTEU42JM6TXJYMKXANCNFSM6AAAAAAY3JVVHI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

YES! Make sure to take note of the speed improvement in CI too (this should decrease our installation step + linting, and make pr both locally and in CI)
…

This is a good first impression :smile:


Boostrapping multi-terrabyte cluster too slow with pg_dump

I set up a temporary Postgres deployment to bootstrap a new cluster according to #2638. The total size of the database is 6.2 terabytes. After roughly one day, only 300 GB was restored. For comparison, the wal-g restore took about 6 hours, and this was only possible because I could increase the concurrency to 100. For CPNG, the spec doesn't currently allow increasing the number of pg_dump jobs, e.g., pg_dump -j njobs.
I suspect that even increasing the number of pg_dump jobs won't help me to restore a  database this size in a reasonable time (hours instead of days), but I would be happy to try if such an option becomes available.
I used an unorthodox workaround that might be useful to someone else trying to bootstrap a new cluster from a big database:

Create a temporary Postgres deployment using the base backup restored using wal-g.
Create a single instance CNPG cluster with node affinity set to the same node as the temp Postgres instance.
Use imperative hibernation to hibernate the CNPG cluster.
Move the base, global, and all the pg_* dirs from the Postgres persistent volume to the CNPG instance persistent volume and fix file permissions. Keep all the config files as is. I moved the files directly on the node filesystem while not in use by any pods.
Switch hibernation off on the CNPG cluster to start the cluster up and scale to 3 instances.

It would be great if the docs could address bootstrapping a new cluster from a physical backup in the future, but allowing one to increase the number of pg_dump jobs would already be a big help.

@gbartolini, thanks for your feedback!
Yes, WAL-G is a physical backup tool, just like Barman, but let me clarify how pg_dump comes into play.
I only used WAL-G to set up a temporary Postgres instance running inside the Kubernetes cluster. I created a Kubernetes Job to use WAL-G to restore to a persistent volume. Once the job was completed, I mounted the persistent volume inside the Postgres instance. At this point I had a running instance that one can use to bootstrap a new CNPG cluster using externalClusters as documented here: https://cloudnative-pg.io/documentation/1.20/database_import/#the-microservice-type
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: cluster-microservice
spec:
  instances: 3

  bootstrap:
    initdb:
      import:
        type: microservice
        databases:
          - angus
        source:
          externalCluster: cluster-pg96
        #postImportApplicationSQL:
        #- |
        #  INSERT YOUR SQL QUERIES HERE
  storage:
    size: 1Gi
  externalClusters:
    - name: cluster-pg96
      connectionParameters:
        # Use the correct IP or host name for the source database
        host: pg96.local
        user: postgres
        dbname: postgres
      password:
        name: cluster-pg96-superuser
        key: password

As per the docs:

export of the selected database (in initdb.import.databases) using pg_dump -Fc
import of the database using pg_restore --no-acl --no-owner into the initdb.database

So, I'm referring to how the operator uses pg_dump to bootstrap the cluster, not my direct use. I had a look at the options used, and it doesn't support running multiple processes: https://github.com/cloudnative-pg/cloudnative-pg/blob/main/pkg/management/postgres/logicalimport/database.go#L102
I'm heading over to read your article next. I just wanted to clarify my use of pg_dump first.

@gbartolini great article! Using Postgres publication and subscription seems very promising as a way to migrate an existing database into CNPG! I am a little concerned that sequences are not migrated but I'm sure it can be managed by treading carefullly.
That said, I don't think that this method will help bootstrap a big database in a reasonable time. I imagine restoring a full base backup from a primary and replaying WAL files afterwards will still be significantly faster than any alternative, purely because restoring the base backup can be sped up by running concurrent processes.

If you are not interested in the migration part, but just start a replica from an existing cluster, have you looked into the new volume snapshot feature that we will introduce in version 1.21? You can actually create a replica cluster from an existing volume snapshot that you make available in another region, and bootstrap in a shorter time by fetching WAL files from an object store. See commit c2ca044763a0272ee706eec26051e4fa0504fbc1.
If you are interested, you can already test this feature by installing the latest available snapshot.

This is a discussion more than an issue now, turning into a discusison


PHPUnit10 Support

renamed assertDirectoryNotExists and assertFileNotExists to assertDirectoryDoesNotExist and assertFileDoesNotExist as they'll be deprecated on PHPUnit 10

Not sure I we should upgrade phpunit dependancy directly or add it with || to composer.
Tested with 9.1.4

Since it's a dev dependency of this package, it won't have any effect on anyone installing the package. I don't see anything wrong with upgrading PHPUnit here, other than we are still testing older versions of PHP. (I say older... I remember the days of PHP 5.3, so PHP 7.2 really isn't that old in my opinion, LOL.)
PHPUnit 9 only supports PHP 7.3 and 7.4. So for the PHP 7.2 tests, we still need PHPUnit 8.

Oh I see..
I fails as that method doesn't exist on previous versions.
So maybe we shooul close this PR or merge it after dropping support for older versions.

Hi,
Good idea yeah @jnbn , we'll do that 😄


return from Main loop on Ctrl-C/shutdown

When we receive Ctrl-C we set shutdown to true, but we do not return from the Main Future with Ready without triggering Ctrl-C handler again.

Thanks

This was intentional. When Ctrl-C is received the first time we try to shutdown Spirc (line 439). Once that's done we can terminate the future (line 453). If the user gets impatient and hits ctrl-c a second time we give up and exit immediately (line 443).
With your change we now don't give time for spirc to shutdown cleanly, which may cause other devices to still see it in the device list. What prompted this change? Was the previous behaviour not working for you?

Apologies, didn't realise that this behaviour was intentional. Feel free to push a commit to reverse it if you think the implementation is now wrong.

In that case, Spirc was not shutting down. It kept waiting. The second Ctrl-C wasn't handled anymore, so I had to kill it hard.


Theme tailors for jetbrains IDE's

User story
As a dyslexic developer, I want to utiise this theme in rider and webstorm so that code in comfort.
Additional context
I love this theme but would really love to use my usual IDE's with it, I read a blog saying you used this theme in PhpStorm so thought maybe it was something achievable to have this for jetbrains IDE;s
Acceptance criteria
Can install this theme in webstorm and rider

Mate, you are a legend! thank you :-)

No problem 😁
On Tue, 20 Feb 2024, 16:39 David Bowers, @.***> wrote:

Mate, you are a legend! thank you :-)
—
Reply to this email directly, view it on GitHub
https://github.com/SpeedyLom/dislexic-vscode/issues/17#issuecomment-1954612368,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACP2FJRMJFJDQ3P5W75WRN3YUTGVPAVCNFSM6AAAAABDQCO3L2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJUGYYTEMZWHA
.
You are receiving this because you were assigned.Message ID:
@.***>

Fyi, I imported into webstorm and rider and both worked like a dream

Thanks for that, I'll look into putting up some proper instructions and adding it onto the releases page.


fix: executable path in windows

PR for issue: #1439

We should also check why the repotests fail consistently.

We should also check why the repotests fail consistently.
It seems to be successful now after re-running the failed job


How to print certificate data from etoken

I am trying to print certificate data  like subject, issuer, Validity start, validity end  information and put it in pdf have any solution for this
Thanks.

I don't understand what you mean, what subject to extract? Endesive may have some information given, but it doesn't get anything else (signature, contact, location and reason)

See cert-info.py in examples, it will show some information from the certificate


Add ability to get parent ID in feature from features endpoint

Fixes https://github.com/GMOD/Apollo3/issues/357

Fixed by https://github.com/GMOD/Apollo3/pull/456


force-start issue on current master, with android

If the app is closed, and you send a notification, and if the screen is turned on, then it notifies and then it opens the app to the foreground.  Ok.
However, if the screen is turned OFF, and the app is not running, then you send a notification, it notifies and then starts the app in the foreground (with the screen still turned off), so all future notifications will NOT sound a notification because the app is acting like it s running in the foreground even though the screen is off.  If you turn on the screen, go into the app and then go back to the homescreen, then the app is background and it works again.  The on 'notify' still works, just no system notification shows up.
This is a problem because after the first notification starts the app, you will never get more notifications until you go to the app and then back out because it thinks the app is in the foreground after that first notification starts the app while the screen is turned off.
Android 6.0
phonegap-plugin-push 1.9.2 from npm and also from current github master

Sorry to be a jerk but I'm now closing issues that don't follow the issue submission guidelines. This plugin takes a lot of work to maintain and I can't afford the time required to solicit the required info from everyone.
I'm closing this issue but please feel free to re-open the issue if you provide the requested details from the new issue submission guidelines.
https://github.com/phonegap/phonegap-plugin-push/blob/master/.github/ISSUE_TEMPLATE.md


[PDI-13210] - Create a map of extension point plugin for later use

I have tested using a transformation with quite a few step.

@mattyb149 , @pentaho-nbaker please review

Hmm I can't find my comments, I thought I'd posted or emailed them a while ago.
The code looks good, I'm just wondering if we should change the behavior of extension points in order to get the performance increase of having cached instances of the plugins (instead of caching the plugin classes). Having them mapped by ID is a great performance increase already, and having cached instances would be even better, but it would change the current behavior of how extension points are invoked.
@pentaho-nbaker @mattcasters What do you guys think about this? The change in behavior is that all  member variables (static and non-static) will retain their state between invocations of the extension point plugin's callback. Before, a new extension point plugin object would be created and then the callback would be invoked. This allowed non-static members to be used among methods in the class.
I'm thinking this is fine as a change, we would just want to document it. We had never made any claims as to how extension point plugins' member variables behaved before, so I would think we can just choose this to be the "official" way, and mention in the documentation that if you were using non-static member variables in earlier versions, the behavior is "undefined" or something like that.


Fast pytest

Please ensure your pull request adheres to the following guidelines:

[ ] Tests for new functionality/models or Tests to reproduce the bug-fix in code.
[ ] Updated documentation of features that add new functionality.
[ ] Update CHANGELOG.md with major/minor changes.

Codecov Report
Patch coverage has no change and project coverage change: -0.01 :warning:

Comparison is base (32ee5f0) 73.29% compared to head (e7a8c0e) 73.29%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1234      +/-   ##
==========================================
- Coverage   73.29%   73.29%   -0.01%
==========================================
  Files          75       75
  Lines       12535    12533       -2
==========================================
- Hits         9188     9186       -2
  Misses       3347     3347

Impacted Files
Coverage Δ

...ARK/ConsumptionSaving/TractableBufferStockModel.py
98.69% <ø> (-0.01%)
:arrow_down:

HARK/utilities.py
24.36% <ø> (-0.22%)
:arrow_down:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

attempt to make running checks and tests faster through github actions. Unfortunately the machine we get for testing only seems to have 2 cores at most, which makes the effect of this change limited.

@MridulS

@MridulS oh yeah, I'll remove those.
However, I think we should have a discussion about renovatebot or some other dependency manager. Seems pretty useful.


config file

Hi, thanks for your code!
I try to train model using EgoHand dataset, and my config file follows this one but I cannot get your results in tensorboard. So I wanna know which config file you use? Can you share it? Thank you

Hi @lan2720
The config file above is the config file I used. What are your results like?
Victor

@victordibia The first 3k step test AP/Recall almost = 0, but train loss reduce quickly. Is it wired?

The figure above is conditioned on batch_size = 64. When I change batch_size to 24, it worse.

SSD with Mobilenet v1 configuration for MSCOCO Dataset.
Users should configure the fine_tune_checkpoint field in the train config as
well as the label_map_path and input_path fields in the train_input_reader and
eval_input_reader. Search for "PATH_TO_BE_CONFIGURED" to find the fields that
should be configured.
model {
ssd {
num_classes: 1
box_coder {
faster_rcnn_box_coder {
y_scale: 10.0
x_scale: 10.0
height_scale: 5.0
width_scale: 5.0
}
}
matcher {
argmax_matcher {
matched_threshold: 0.5
unmatched_threshold: 0.5
ignore_thresholds: false
negatives_lower_than_unmatched: true
force_match_for_each_row: true
}
}
similarity_calculator {
iou_similarity {
}
}
anchor_generator {
ssd_anchor_generator {
num_layers: 6
min_scale: 0.2
max_scale: 0.95
aspect_ratios: 1.0
aspect_ratios: 2.0
aspect_ratios: 0.5
aspect_ratios: 3.0
aspect_ratios: 0.3333
}
}
image_resizer {
fixed_shape_resizer {
height: 300
width: 300
}
}
box_predictor {
convolutional_box_predictor {
min_depth: 0
max_depth: 0
num_layers_before_predictor: 0
use_dropout: false
dropout_keep_probability: 0.8
kernel_size: 1
box_code_size: 4
apply_sigmoid_to_scores: false
conv_hyperparams {
activation: RELU_6,
regularizer {
l2_regularizer {
weight: 0.00004
}
}
initializer {
truncated_normal_initializer {
stddev: 0.03
mean: 0.0
}
}
batch_norm {
train: true,
scale: true,
center: true,
decay: 0.9997,
epsilon: 0.001,
}
}
}
}
feature_extractor {
type: 'ssd_mobilenet_v1'
min_depth: 16
depth_multiplier: 1.0
conv_hyperparams {
activation: RELU_6,
regularizer {
l2_regularizer {
weight: 0.00004
}
}
initializer {
truncated_normal_initializer {
stddev: 0.03
mean: 0.0
}
}
batch_norm {
train: true,
scale: true,
center: true,
decay: 0.9997,
epsilon: 0.001,
}
}
}
loss {
classification_loss {
weighted_sigmoid {
anchorwise_output: true
}
}
localization_loss {
weighted_smooth_l1 {
anchorwise_output: true
}
}
hard_example_miner {
num_hard_examples: 3000
iou_threshold: 0.99
loss_type: CLASSIFICATION
max_negatives_per_positive: 3
min_negatives_per_image: 0
}
classification_weight: 1.0
localization_weight: 1.0
}
normalize_loss_by_num_matches: true
post_processing {
batch_non_max_suppression {
score_threshold: 1e-8
iou_threshold: 0.6
max_detections_per_class: 100
max_total_detections: 100
}
score_converter: SIGMOID
}
}
}
train_config: {
batch_size: 24
optimizer {
rms_prop_optimizer: {
learning_rate: {
exponential_decay_learning_rate {
initial_learning_rate: 0.001
decay_steps: 800720
decay_factor: 0.95
}
}
momentum_optimizer_value: 0.9
decay: 0.9
epsilon: 1.0
}
}
fine_tune_checkpoint: "/data1/jiananwang/handx/pretrain_model/ssd_mobilenet_v1_coco_2018_01_28/model.ckpt"
from_detection_checkpoint: true
Note: The below line limits the training process to 200K steps, which we
empirically found to be sufficient enough to train the pets dataset. This
effectively bypasses the learning rate schedule (the learning rate will
never decay). Remove the below line to train indefinitely.
num_steps: 200000
data_augmentation_options {
random_horizontal_flip {
}
}
data_augmentation_options {
ssd_random_crop {
}
}
}
train_input_reader: {
tf_record_input_reader {
input_path: "/data1/jiananwang/handx/data/egohand/tfdata/train.record"
}
label_map_path: "/data1/jiananwang/handx/hand_label_map.pbtxt"
}
eval_config: {
num_examples: 400
Note: The below line limits the evaluation process to 10 evaluations.
Remove the below line to evaluate indefinitely.
max_evals: 10
}
eval_input_reader: {
tf_record_input_reader {
input_path: "/data1/jiananwang/handx/data/egohand/tfdata/test.record"
}
label_map_path: "/data1/jiananwang/handx/hand_label_map.pbtxt"
shuffle: false
num_readers: 1
}

Here is my config.

@victordibia My bad. In my hand_label_map.pbtxt, I use "Hand" instead of "hand". Sorry.


Allow temperature,max-tokens and engine parameters to be overriden

Hi Andreas,
I found myself wanting to switch between different engines/parameters quite often, so I ended up expanding gpt-dwim to allow them to be overridden!
This now allows me to bind different models to different keys easily.
Please merge this PR is you think it could be useful :)
Thanks,
Giedrius

Thanks for the PR! Can you take a look at my recent changes (follow-up commands) and see if this PR still makes sense for the direction I'm taking the project in? If so, happy to merge it if you resolve the conflicts.

Closing for now - feel free to reopen!


Add annotation REST examples to docs

The various /annotation/ sub-resources in the model are enumerated in the API docs and described as content within the model elements they annotate, but the REST operation examples only show access to model elements and not fine-grained CRUD access to annotations themselves.

@hongsudt  Maybe you can review the new docs.  See the sections "Model Annotations" and "Model Comments" in the REST operations section of the doc and table of contents.

I'm closing this old issue as good enough since no negative reviews were given...


New Leaderboard UI

Added Responsiveness
Updated the leaderboard UI
fixes#338

Summary by CodeRabbit

New Features

Leaderboard now supports filtering by platform.

Enhancements

Improved UI and logic for the leaderboard's platform and rating display.

Refactor

Updated Rank component with enhanced conditional rendering and styling.

Removed

Removed the WorkspacePremium feature from the leaderboard view.

@coderabbitai resolve

Hey @im-vedant merging this PR into snowTheme branch to add the winter theme and then will push it to production


go upgrade

https://github.com/toggl/backend/issues/9925

already upgraded in https://github.com/toggl/pipes-api/tree/new-refactored-version


⚠ Samsung has degraded performance

In 35cb24d, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2466 ms

Resolved: Samsung performance has improved in b1d6766.


tracking issue - questions related to adoption

Here's a list of questions that we need to think about when driving adoption in both array/tensor libraries, and further downstream.

Do we want array libraries to adopt this into a public or private namespace. I.e., only accessible via arrayobject.__array_namespace__() or additionally via a direct import? If the latter, what should it be named? related to gh-16
What is the design pattern to work around np.asarray in downstream libraries?
Now that we have some features that are kind of optional (e.g., boolean indexing), can we define and should we recommend a testing strategy to figure out how portable some piece of code really is? Also relevant if libraries add extra things into the standard module because it's too hard to remove (e.g., methods on array object).
Should we have a central place to track adoption and compliance level?
Can downstream libraries sanely use type annotations when supporting multiple array libraries? (related to the Protocol mentioned in the Static typing section)

Please add more questions if you can think of them.

3. Now that we have some features that are kind of optional (e.g., boolean indexing), can we define and should we recommend a testing strategy to figure out how portable some piece of code really is? Also relevant if libraries add extra things into the standard module because it's too hard to remove (e.g., methods on array object).

Two options were suggested here:

Have a standalone reference implementation, which exposes only the API in the standard. It could use an array class which is backed by numpy.ndarray, but wraps it and forwards all the calls. Performance isn't important here after all.
Use Mypy, ensure that the annotations for the the array_api namespace only include the APIs in the standard.

3. Now that we have some features that are kind of optional (e.g., boolean indexing), can we define and should we recommend a testing strategy to figure out how portable some piece of code really is? Also relevant if libraries add extra things into the standard module because it's too hard to remove (e.g., methods on array object).

Two options were suggested here:

Have a standalone reference implementation, which exposes only the API in the standard. It could use an array class which is backed by numpy.ndarray, but wraps it and forwards all the calls. Performance isn't important here after all.
Use Mypy, ensure that the annotations for the the array_api namespace only include the APIs in the standard.

What is the design pattern to work around np.asarray in downstream libraries?

I opened https://github.com/data-apis/array-api/issues/122 for this one before I saw this issue :)

What is the design pattern to work around np.asarray in downstream libraries?

I opened https://github.com/data-apis/array-api/issues/122 for this one before I saw this issue :)

How should libraries check array types, e.g., what is the equivalent of np.ndarray for use in isinstance or type annotations? Perhaps we should include the equivalent of an Array base class as part of the spec. __array_namespace__() provides the same information, but it's less convenient to use.

How should libraries check array types, e.g., what is the equivalent of np.ndarray for use in isinstance or type annotations? Perhaps we should include the equivalent of an Array base class as part of the spec. __array_namespace__() provides the same information, but it's less convenient to use.

How should libraries check array types, e.g., what is the equivalent of np.ndarray for use in isinstance or type annotations? Perhaps we should include the equivalent of an Array base class as part of the spec. __array_namespace__() provides the same information, but it's less convenient to use.

Some thoughts on this:

adding a base class in the spec isn't useful, it would need to be in a (small, standalone) package as an ABC. it's not impossible we'll end up with something like that, but just for enabling isinstance is probably not enough reason to do it.
isinstance isn't too useful in general I'd say. the first thing some function using arrays will do is use __array_namespace on its inputs already.
a typing.Protocol can be done in the spec, and would be useful to include I think.

Do we want array libraries to adopt this into a public or private namespace. I.e., only accessible via arrayobject.__array_namespace__() or additionally via a direct import? If the latter, what should it be named? related to gh-16

Tentative answer: yes, make it available as a direct import, and name it array_api.

How to specify device for the very first array? -> https://github.com/data-apis/array-api/issues/156

How to specify device for the very first array?

This should now be supported via the inspection API where you can query the list of supported devices.

Have a standalone reference implementation, which exposes only the API in the standard. It could use an array class which is backed by numpy.ndarray, but wraps it and forwards all the calls.

This should now be satisfied via https://github.com/data-apis/array-api-strict.


Multiple rules targeting same folder end up ignoring the file

With this directory structure:
├─────watch.js
└─────src
      ├─────src.js
      └─────sub
            └─────sub.js

and this is the code:
chokidar.watch([
  'src/**/test/*.js',
  'src/**/*.test.js',
  'tests/**/*.js',
  '{src,lib}/**/*.{js,coffee}',
  '*.{js,coffee}',
], {
  ignored: [
    'node_modules/**',
    '**/node_modules/**'
  ]
})

It doesn't trigger change events for src/sub/sub.js file.
Removing the following makes it work again:
  // 'src/**/test/*.js',
  // 'src/**/*.test.js',
  'tests/**/*.js',
  '{src,lib}/**/*.{js,coffee}',
  '*.{js,coffee}',

The commented out patterns are causing the problem. Is this a bug, or does the array actually control specificity?
Windows 10, node v7, chokidar: v1.6.1
repro: https://github.com/laggingreflex/chokidar-test-561

It seems from the code that passing an array, especially if one of the two globs could match the same path,  that it really is about adding more specificity. I.e. it will prefer ignoring a file if one of the globs is meant to ignore it.
I've arrived at this conclusion from NodeFsHandler.prototype._addToNodeFs where it accepts and passes on forward a priorWh object which seems to add or reuse a filterPath which is then passed to readdirp, effectively making readdirp filter all paths that all previous globs flagged for ignoring.
If you comment out the section where it "inherits" priorWh the problem goes away.
  // if (!wh.hasGlob && priorWh) {
  //   wh.hasGlob = priorWh.hasGlob;
  //   wh.globFilter = priorWh.globFilter;
  //   wh.filterPath = priorWh.filterPath;
  //   wh.filterDir = priorWh.filterDir;
  // }

All tests still pass with the above mention code block commented out.
It seems this was added in https://github.com/paulmillr/chokidar/commit/871f3461761eeaa96b40388baf83718aa547ec1a.
FsEventsHandler.prototype._addToFsEvents doesn't appear to have any such logic.

Reusing watch handles has to do with efficient resource utilization on the machine - we used to see users hitting system limits often for certain use cases.
This is a bug that needs to be addressed, but not by ripping out the resource controls if it can be avoided. Seems we need either an exclusion on the reuse for conflicting/intersecting globs with the same parent, or some way to account for multiple patterns in filterPath.

I run into the same problem with<EMAIL_ADDRESS>while debugging https://github.com/avajs/ava
my files look like:
frontend > find src/widgets/banner
src/widgets/banner
src/widgets/banner/bannerReducer.test.js
src/widgets/banner/BannerItem.test.js
src/widgets/banner/bannerReducer.js
src/widgets/banner/BannerContainer.test.js
src/widgets/banner/BannerItem.js
src/widgets/banner/BannerContainer.js
src/widgets/banner/bannerItem.scss
src/widgets/banner/bannerSaga.test.js
src/widgets/banner/bannerTestData.js
src/widgets/banner/BannerItem.stories.js
src/widgets/banner/bannerSaga.js
src/widgets/banner/Banner.stories.js
src/widgets/banner/banner.scss

patterns watched: [ 'src/**/*.js', 'src/widgets/banner/**/*.test.js' ]
patterns ignored:
[ '.git/**/*',
  '.nyc_output/**/*',
  '.sass-cache/**/*',
  'bower_components/**/*',
  'coverage/**/*',
  'node_modules/**/*' ]

When I call watcher.getWatched() on my Arch linux (node: 6.3.1, kernel: 4.9.8-1) I get
[ 'BannerContainer.test.js',
  'BannerItem.test.js',
  'bannerReducer.test.js',
  'bannerSaga.test.js' ]

as described from OP the second watch pattern overrides the general one.
But when I run the same code on Mac (node: 6.4.0, system: macOS 10.12.3 (16D32), kernel: Darwin 16.4.0) it works as expected:
[ 'Banner.stories.js',
  'BannerContainer.js',
  'BannerContainer.test.js',
  'BannerItem.js',
  'BannerItem.stories.js',
  'BannerItem.test.js',
  'bannerReducer.js',
  'bannerReducer.test.js',
  'bannerSaga.js',
  'bannerSaga.test.js',
  'bannerTestData.js' ]

Is this bug just on some plattforms?

Any movement on this?

Two years later the same problem

I noticed that it works when if specify files with glob patterns, i.e
chokidar.watch(['package.json', 'yarn.lock', 'otherFile.js']) won't work from the same dir, but
chokidar.watch(['pac*.json', 'yarn.*', 'otherF*.js']) will work.

I also have this problem when trying to glob against multiple file extensions.
// Notices only *.ts
chokidar.watch(['src/**/*.ts', 'src/**/*.html'])

// Notices everything
chokidar.watch(['src/**/*.{ts,html}'])

Works correctly for me with chokidar 3.2.0-pre (npm i github:paulmillr/chokidar), tested Ubuntu and MacOS.

If someone else is finding this issue, maybe this is exactly how it's supposed to work? But I found a work around by adding in an additional watch item. For example I was watching for all PHP file changes in my entire project, and also watching for CSS changes in certain paths. But then it stopped looking for PHP changes in those same paths. So I simply added a watch for PHP files in the same path.
chokidar.watch([
        './**/*.php',
        './template-parts/blocks/**/*.css',
        './template-parts/blocks/**/*.php'
      ])


⚠ Processors has degraded performance

In c56e467, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 54 ms

Resolved: Processors performance has improved in b870c4d.


Add sysfs_preload dependency

Waiting for https://github.com/toltec-dev/toltec/pull/818 to be merged

I'm just going to merge this early


wishlist: add a bait for mobs

Maybe we could add some kind of thing that the evil mobs really like, as a bait, to distract them from the player during some time. I was thinking about a Doll or use homedecor's TV. Of course, that would have a limited amount of time (then the mob destroys the objects), and the mob could still come back to you if you hit it.
Then you can continue mining, or go away... like a chicken, beause you REALLY want to come back to the surface with your new buldozer-only sword that you have mined.

i like your idea about the TV :D

Animals attracted by TV... Nice :D

or drop a book XD

We Will not add this feature, this is a too easy way to kill monsters without difficulty.
If you need a bait, go kill monsters with a Warrior :) (the warrior is a bait, in a way, it's a tank :p)


fix(material/paginator): add role="group" to host

In testing <mat-paginator> with VoiceOver, I found that the interaction was much nicer when the paginator controls were semantically grouped with role="group". This change adds the role and updates the documentation to explicitly instruct users to apply a meaningful label.
I was on the fence about adding a default label (something like "Pagination control"). I settled on this approach because it's the most consistent with our other controls that require developers to specify a label for host elements, even though we do have MatPaginatorIntl for the labels for child components within the control.

Added a test
Caretaker note: when this is synced into Google, we should communicate the change to users

LGTM


First stab at validating written zarr stores

This PR adds a validate_zarr_store() utility function. This utility function validates a zarr store by taking a ratio of an Array's .nchunks_initialized and .nchunks. If all chunks were properly written, the ratio should be 1. Unfortunately, in case a chunk contains data equal to the fill value, zarr doesn't write this to disk by default, and as a result, we may get false alarms.
In [11]: validate_zarr_store("/tmp/bar.zarr/")
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [11], in <cell line: 1>()
----> 1 validate_zarr_store("/tmp/bar.zarr/")

Input In [10], in validate_zarr_store(target)
     17         errors.append(
     18             f'{variable} has {variable_array.nchunks - variable_array.nchunks_initialized} uninitialized chunks'
     19         )
     21 if errors:
---> 22     raise ValueError(f'Found {len(errors)} errors: {errors}')

ValueError: Found 1 errors: ['air has 1 uninitialized chunks']

In [12]: validate_zarr_store("/tmp/foo.zarr/")

Cc @jhamman, @norlandrhagen

pre-commit.ci autofix

pre-commit.ci autofix

pre-commit.ci autofix


Error in VS Code output

Getting this message immediately when opening any .c4 file. I've tried the example files and the most basic files I can create with no luck. The plugin appears to not work on any .c4 file.

Hey @ScottSlaughterBBNA, Wow, interesting,thanks for report.
Can you please turn on verbose mode and share stack trace?
And what vscode/OS/Node version do you have?

OS is Windows 10 Enterprise. Running VS Code version 1.79.2. I have node.js version 20.3.1 installed, but the about in VS code is showing 16.17.1 which doesn't even show in my NVM list as an installed version.
2023-07-06 13:26:31.951 [error] Error: Attempted to send error data when the @vscode/extension-telemetry module does not support it.
at AS.sendErrorData (c:\Users\user.vscode\extensions\likec4.likec4-vscode-0.27.0\dist\node.js:48:64615)
at D.logError (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:41178)
at e.ExtHostTelemetry.onExtensionError (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:39646)
at c.a (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:117:478)
at c.onUnexpectedError (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:7:249)
at O (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:7:603)
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:127:33610

Maybe fixed by #192, going to release a new version

Just tried it with version 0.28.0 but I'm still seeing that generic error.
2023-07-06 14:17:17.473 [error] [likec4.likec4-vscode] provider FAILED
2023-07-06 14:17:17.473 [error] Error: Request textDocument/documentSymbol failed with message: Cannot access 'a' before initialization
at handleResponse (c:\Users\user.vscode\extensions\likec4.likec4-vscode-0.28.0\dist\node.js:11:233)
at handleMessage (c:\Users\user.vscode\extensions\likec4.likec4-vscode-0.28.0\dist\node.js:10:7945)
at processMessageQueue (c:\Users\user.vscode\extensions\likec4.likec4-vscode-0.28.0\dist\node.js:10:8101)
at Immediate. (c:\Users\user.vscode\extensions\likec4.likec4-vscode-0.28.0\dist\node.js:10:7807)
at process.processImmediate (node:internal/timers:466:21)

Thanks, I will try to reproduce and run windows in vm.
Just wonder, web versions, like github.dev or vscode.dev - do they work fine on your side?

I haven't tried vscode.dev, but it works fine at github.dev.

I take that back. After a minute of the window open I had the same error in the browser.
[Error - 3:11:35 PM] Request textDocument/documentSymbol failed.
Message: Request textDocument/documentSymbol failed with message: Cannot access 'o' before initialization
Code: -32603
["DEBUG" - 3:11:35 PM] receive: onDidChangeModel
["DEBUG" - 3:11:36 PM] fetchModel

And do you use model from the example?

Yes. Just selected the model.c4

After reloading the page a few times and slowly clicking through the .c4 files the error happens specifically when the _spec.c4 file is opened.

Oh! Got the same!
Gosh, already spined Virtual Machine on Azure.

Hey @ScottSlaughterBBNA Thank you for your time and your interest in finding the cause, really appreciate it.
Gonna release a new version


Create official tag list and add to documentation

After a discussion in the Gitter channel around there being no list of tags I'm raising this issue for discussion around this before creating the docuimentation.
It's been suggested that the documentation be created on the Creating Packages page.
The list of tags I'm aware (off the top of my head):

admin - installer requires Administrator privileges (such as installing Program Files);
trial - package is a trial version
notsilent - package requires interaction by the user after install / uninstall (such as browser windows opening and needing to be closed manually - note that it doesn't include the installer being visible as long as there is no interaction required).

List of tags I'd like to add:
* licensed - package requires a license to use - this is different from trial which still runs for a period of time; license tag is already recommended.
Also highlight that packages should not include the tag 'chocolatey'
Agreed Tags
The tags so far agreed on are:

admin
trial
notsilent
license

Tags Under Discussion
Package category tags still under discussion:

productivity
programming
utility
browser
drivers
server
client
addon

Other tags still under discussion:

notUninstallable

Moving this to the docs repository, as this is where the work would need to be done.


HPX won't compile with  -DHPX_WITH_APEX=TRUE

Expected Behavior
HPX should build
Actual Behavior
[  0%] Building CXX object apex/src/apex/CMakeFiles/apex.dir/apex.cpp.o
cd /home/users/khuck/src/phylanx/tools/buildbot/build-delphi-x86_64-Linux-gcc/hpx-Debug/apex/src/apex && /packages/gcc/7.1/bin/g++  -DAPEX_HAVE_ACTIVEHARMONY -DAPEX_HAVE_HPX_CONFIG -DAPEX_HAVE_OTF2 -DAPEX_HAVE_PAPI -DAPEX_HAVE_POWERCAP_POWER -DAPEX_HAVE_PROC -DBOOST_ALL_NO_LIB -DDEBUG -DHPX_COROUTINE_EXPORTS -DHPX_EXPORTS -DHPX_LIBRARY_EXPORTS -D_GNU_SOURCE -I/home/users/khuck/src/phylanx/tools/buildbot/src/hpx -isystem /usr/local/packages/boost/1.65.0-gcc7/include -I/home/users/khuck/src/phylanx/tools/buildbot/src/hpx/apex/src/apex -I/home/users/khuck/src/phylanx/tools/buildbot/build-delphi-x86_64-Linux-gcc/hpx-Debug -I/home/users/khuck/src/phylanx/tools/buildbot/build-delphi-x86_64-Linux-gcc/hpx-Debug/apex/src/apex -I/home/users/khuck/src/phylanx/tools/buildbot/src/hpx/apex/src/contrib -I/include -I/usr/local/packages/papi/papi-knl/5.5.0/include -I/usr/local/packages/activeharmony/4.6.0-gcc/include -I/usr/local/packages/otf2-2.1/include  -fPIC -g   -fPIC -std=c++17 -o CMakeFiles/apex.dir/apex.cpp.o -c /home/users/khuck/src/phylanx/tools/buildbot/src/hpx/apex/src/apex/apex.cpp
In file included from /home/users/khuck/src/phylanx/tools/buildbot/src/hpx/hpx/config.hpp:31:0,
                 from /home/users/khuck/src/phylanx/tools/buildbot/src/hpx/apex/src/apex/apex.cpp:12:
/home/users/khuck/src/phylanx/tools/buildbot/build-delphi-x86_64-Linux-gcc/hpx-Debug/hpx/config/version.hpp:15:10: fatal error: hpx/pp/cat.hpp: No such file or directory
 #include <hpx/pp/cat.hpp>
          ^~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [apex/src/apex/CMakeFiles/apex.dir/apex.cpp.o] Error 1

Steps to Reproduce the Problem
configure hpx with -DHPX_WITH_APEX=TRUE
Specifications
any platform, any compiler

Thinking long-term, does APEX and HPX need to depend on each other like this? Ideally one or the other would expose enough hooks for the one to sit just cleanly on top of the other.

The fix is, to add the HPX.PP module to the dependencies of APEX.
This ticket, IMHO, shows the positive effect of the modularization effort. We can clearly see dependencies for different projects. Since Config isn't a module yet, this needs to adapted once more...
A PR to fix APEX itself has been added: https://github.com/khuck/xpress-apex/pull/99

@sithhell you can't be serious in requiring for all people that depend on HPX to list all small module dependencies manually. Is that what everybody will have to do in the end?

Thinking long-term, does APEX and HPX need to depend on each other like this? Ideally one or the other would expose enough hooks for the one to sit just cleanly on top of the other.

@msimberg APEX depends on HPX as it uses its functionalities. At the same point we have added hooks into APEX to HPX which makes the two circular dependent. I'm not sure how we can remove this.
For this reason, we decided to build APEX as a static library while compiling against the HPX API headers, while linking HPX with that built static library to resolve the APEX dependencies in HPX. Any better suggestion would be certainly welcome.

Hartmut Kaiser<EMAIL_ADDRESS>schrieb am Fr., 19. Apr. 2019
14:52:

@sithhell https://github.com/sithhell you can't be serious in requiring
for all people that depend on HPX to list all small module dependencies
manually. Is that what everybody will have to do in the end?

That's certainly not what I said.
The problem in the case of APEX is that it depends on parts parts of hpx
and hpx depends on parts of APEX. To fix this circular dependency, the Apex
build system tried to set up the include paths etc manually, without
depending on what the different targets depend on.
The usage for consumers of hpx won't change at all. They'll consume the top
level hpx target (as they do now) and call it a day.
For anything in between (like APEX), things will change a bit, and the
transition period might lead to non optimal (as in listing indirect
dependencies until the higher level one exists) intermediate steps. This is
what happened in this case with the config module.

@sithhell Fair enough, thanks.

@msimberg APEX depends on HPX as it uses its functionalities. At the same point we have added hooks into HPX to APEX which makes the two circular dependent. I'm not sure how we can remove this.
For this reason, we decided to build APEX as a static library while compiling against the HPX API headers, while linking HPX with that built static library to resolve the APEX dependencies in HPX. Any better suggestion would be certainly welcome.

Naively the answer is more hooks and callbacks, but I can't judge how much work that would actually be.


[request] GUI components

I don't know if this is in scope, but "external GUI" components would be nice, like completion popup, command pallete, tanline, error messages etc.
(I don't think this is related to #233 because a GUI popup would have a scrollbar)

The struggle for me here is that its not obvious how to implement such features in a way that isn't just different for different sake. I'd be happy with such an improvement if it was demonstrably better, but I haven't seen external gui components that really achieve that.
I'd love to hear ideas though

An external command pallete/messages would not clear messages when you enter command mode

Also indent guides are super duper useful

Would you take a PR for this?
(I'll still try, even though I'm very sure I'm unqualified)

Re gui components, I would take a PR for this, but as I mentioned above, it needs to be demonstrably better without feeling out of place. THats a pretty subjective criteria, but if effort is put forth I will definitely support in any way I can to try to get it to a place where we could merge.
One thing though is that implementing gui components often requires adjusting window sizes. This requires the multigrid work that I am currently working on finishing up so it may be better to wait a bit before starting on something like this.
Side note: Indent guides can be implemented in vim today I believe. https://github.com/nathanaelkane/vim-indent-guides

Re gui components, I would take a PR for this, but as I mentioned above, it needs to be demonstrably better without feeling out of place. THats a pretty subjective criteria, but if effort is put forth I will definitely support in any way I can to try to get it to a place where we could merge.

Thanks !!

One thing though is that implementing gui components often requires adjusting window sizes. This requires the multigrid work that I am currently working on finishing up so it may be better to wait a bit before starting on something like this.

Okay, I'll wait

Side note: Indent guides can be implemented in vim today I believe. https://github.com/nathanaelkane/vim-indent-guides

https://github.com/Yggdroot/indentLine + https://github.com/lukas-reineke/indent-blankline.nvim is way better, it looks like a proper GUI's indent guides (like vscode)

The struggle for me here is that its not obvious how to implement such features in a way that isn't just different for different sake. I'd be happy with such an improvement if it was demonstrably better, but I haven't seen external gui components that really achieve that.
I'd love to hear ideas though

The biggest benefit for me would be larger windows within neovim. On emacs having my command palette/statusline/tabs/filetree a larger font makes it much easier on the eyes. There isn't really a need to make it "better" or "'different",  just having a plain scrollable rectangle looks much cleaner than telescope or fzf

Can this be closed in favour of #768  ?

A scrollbar would be really nice and exists in gVim. I've been faking it for the terminal, but it's really not the same.

There are nvim extensions that do this pretty damn well. I use nvim satellite for instance to great effect. And further remaining gaps should be enabled in a vim centric way by exposing config options to get even closer. Closing for now


json output parsing error

gstatus --version
gstatus 1.0.4
gstatus output result - correct.
When run gstatus_discovery.py - JSONDecodeError.
./gstatus_discovery.py
Traceback (most recent call last):
File "./gstatus_discovery.py", line 9, in
gluster_info = json.loads(json_part)
File "/usr/lib64/python3.6/json/init.py", line 354, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python3.6/json/decoder.py", line 342, in decode
raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 1 column 2 (char 1)

gstatus from 1.0.x changed somewhat since previous releases. it's now based on pyhton3 et output format is different as far as I remember.

gstatus from 1.0.x changed somewhat since previous releases. it's now based on pyhton3 et output format is different as far as I remember.

Any fix for this? https://stackoverflow.com/questions/48140858/json-decoder-jsondecodeerror-extra-data-line-2-column-1-char-190 sounds explanatory, however i am no python men, so can't fix it myself.

looks like https://github.com/fabricat/zabbix-glusterfs fixed it on his fork

He also https://github.com/mofm/zabbix-glusterfs


Batch ARM Swagger Application_Update fixes

Application_Update actually returns the Application object -- correcting the
Swagger specification to show that.

@kiwidev @jasper-schneider @annatisch @xingwu1 Learned this needed to be updated too, so changing it before we ship anything based on the existing spec.

Sorry all, Application_Update doesn't return the Application object - will need to leave the Swagger spec as it currently is.


style props does not work in version 0.4.0.

<FlagIcon code={country} size={20} style={{ margin: '.5em' }} />

In versions prior to 0.4.0, style props work normally, but in the latest version, style props do not seem to be applied.

@NEONKID Thanks for report! I finally had a reason to write some tests :)
Released in https://github.com/umidbekk/react-flag-kit/releases/tag/v0.4.1


Interstital bug with Android and DFP

I am having a non displayed interstital with Android and DFP.

The interstital does not display, though the JS success callback is called.
When i inspect the device using chrome device inspect i see the interstital webview (inactive, screenshot attached). it contains the HTML from DFP with my test image and the link (screenshot attached).
When i use AdMob.setOptions({'isTesting':true}); it still doesn't show the test ad. if i use the plugin example adId (''ca-app-pub-xxx/yyy'') and isTesting:true i do get a the adMob test interstital.
The banner works great, it is only the interstital which fails.
Used adId : '/132577502/mApp_320x480'

My guess is that the webview is not being activated (i use autoShow:true and also tried preparing the interstital and then showing it).
logcat output (pay attention that the "avc: denied" error is also displayed in the test interstital which works, therefore that might not be the issue):
06-03 18:06:40.264 3298-3304/il.co.atmag W/art: Suspending all threads took: 80.873ms
06-03 18:06:40.267 3298-3414/il.co.atmag D/GenericAdPlugin: prepareInterstitial: /132577502/mApp_320x480, true
06-03 18:06:40.282 3298-3298/il.co.atmag D/DynamitePackage: Instantiating com.google.android.gms.ads.ChimeraAdManagerCreatorImpl
06-03 18:06:40.311 3298-3298/il.co.atmag I/Ads: Starting ad request.
06-03 18:06:40.312 3298-3298/il.co.atmag I/Ads: Use AdRequest.Builder.addTestDevice("D3F33ABC651FB2473420B059C5F19BD4") to get test ads on this device.
06-03 18:06:40.392 3298-3298/il.co.atmag W/il.co.atmag: type=1400 audit(0.0:3977): avc: denied { read } for name="mem" dev="debugfs" ino=2505577 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
06-03 18:06:40.392 3298-3298/il.co.atmag W/il.co.atmag: type=1400 audit(0.0:3978): avc: denied { read } for name="mem" dev="debugfs" ino=2505577 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
06-03 18:06:40.400 3298-3298/il.co.atmag I/chromium: [INFO:CONSOLE(3)] "succcccccesss", source:  (3)
06-03 18:06:41.156 3298-3298/il.co.atmag D/cr_Ime: [InputMethodManagerWrapper.java:30] Constructor
06-03 18:06:41.159 3298-3298/il.co.atmag W/cr_AwContents: onDetachedFromWindow called when already detached. Ignoring
06-03 18:06:41.160 3298-3298/il.co.atmag D/cr_Ime: [InputMethodManagerWrapper.java:59] isActive: false
06-03 18:06:41.173 3298-3298/il.co.atmag I/cr_Ime: ImeThread is not enabled.
06-03 18:06:41.188 3298-3298/il.co.atmag W/cr_BindingManager: Cannot call determinedVisibility() - never saw a connection for the pid: 3298
06-03 18:06:41.189 3298-3298/il.co.atmag D/cr_Ime: [InputMethodManagerWrapper.java:59] isActive: false
06-03 18:06:41.300 3298-3298/il.co.atmag I/Ads: Ad finished loading.
06-03 18:06:41.301 3298-3298/il.co.atmag D/GenericAdPlugin: showInterstitial
06-03 18:06:41.326 3298-3298/il.co.atmag I/chromium: [INFO:CONSOLE(37)] "adMob event called", source: file:///android_asset/www/app/js/services/adsService.js (37)
06-03 18:06:48.175 3298-3298/il.co.atmag W/Ads: A GMSG tried to close something that wasn't an overlay.
chrome inspect window with the cordova and ad web views:

chrome inspect for the correctly shown but hidden interstital with data from my DFP account:

more detail:
Nexus 5X, Android 6.0.1, Cordova 6, admobpro 2.17.0
Thank you.

This issue was resolved for me in 2.18.0
Thanks


Cannot restore from second minimize when using skip-taskbar

I am developing a music player which some people like to have in their taskbar and other like to have in their tray (I am a tray person). To address this, I introduced a --skip-taskbar setting which runs a BrowserWindow with the skip-taskbar setting enabled. However, I am noticing that I am unable to restore after minimizing/restoring the window once (i.e. cannot restore from second minimize).
I have created a proof of concept gist to reproduce the issue. It is using the --debug flag to allow us to run JS on the window despite it being inaccessible via mouse.
https://gist.github.com/twolfson/6e4c71e499fb3a6733ad
To use the gist, clone it, and start node-inspector via npm run start-node-inspector. Then, in another tab, start the app in --debug mode via npm start. A browser window should pop up.
# Clone our repo
git clone https://gist.github.com/twolfson/6e4c71e499fb3a6733ad gist-electron-skip-taskbar-restore
cd gist-electron-skip-taskbar-restore/

# Start node-inspector
npm run start-node-inspector

# Start our application in another tab
npm start

Inside of the node-inspector site, we ran the following commands and witnessed the following behavior:
// Minimizes window
win.minimize();

// Restores window
win.minimize();

// Minimizes window
win.minimize();

// Actual: Does not restore window
// Expected: Restores window
win.minimize();

My OS is Linux Mint 17.1 64 bit on top of Cinnamon

To provide more information, I had a similar setup with nw.js and did not experience a problem which is why I believe it's something within Electron.

Calling win.minimize for multiple times doesn't restore window, you should call restore instead.

Ah, I mistyped my example. -_-;; I meant:
// Minimizes window
win.minimize();

// Restores window
win.restore();

// Minimizes window
win.minimize();

// Actual: Does not restore window
// Expected: Restores window
win.restore();

Inside of node-inspector, I was typing win.minimize() and win.restore(). However, I retyped by hand when writing up this issue. Can we please re-open this issue?

Great, thank you =)

Great news! I tried out reproducing with 0.26.1 and the issue has disappeared =)
To make sure that I didn't waste our time, when downgrading back to 0.26.0 the issue is still there.


workbox-build generates incorrect channelName options

<EMAIL_ADDRESS>generates service-worker.js with code like this:
new workbox.broadcastUpdate.Plugin('api-updates')

which does not work. Using the following does:
new workbox.broadcastUpdate.Plugin({ channelName: 'api-updates' })

Library Affected:
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Thanks for reporting this!


iox-#2167 Update FiFo

Pre-Review Checklist for the PR Author

[ ] Add a second reviewer for complex new features or larger refactorings
[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[ ] All checks have passed (except task-list-completed)
[ ] All touched (C/C++) source code files from iceoryx_hoofs are added to ./clang-tidy-diff-scans.txt
[ ] Assign PR to reviewer

Notes for Reviewer

See discussion
Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior
[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #2167
Closes #2156

@elBoberido I addressed your latest comments in https://github.com/eclipse-iceoryx/iceoryx/pull/2168 . Can you please review again?


Advisor Results from Diagnostics

Hi @moxious,
Thank you for writing this tool. It is fantastic to be able to see the configuration of all members of the cluster. I like the Advisor Results that show up after the running the diagnostics. However, I have a question about one of the findings I saw:
Your page cache setting is too small considering your store size. Store size=3860898203502 bytes, page cache<PHONE_NUMBER>00 bytes (196g)
I believe 196g is not small at all. The RAM on the server is 256 GB. Any thoughts?
Thanks,
Vivek

Hi Vivek, glad to hear it's useful!
The rule you're citing is triggered by code here: https://github.com/moxious/halin/blob/master/src/diagnostic/advisor/rules/mem.js#L116
The rule in question here was one I took as a suggestion from some Neo4j internal customer success people.   The rule as stated was that "enough page cache" is roughly 90% of the on-disk size of your data store.   Consider that if 100% of your on-disk size was in your page cache, then you would effectively be running your graph in memory, and performance would be very fast.   If you had say, 10% of your graph in the page cache, then queries would constantly cause page cache faults, the database would have to go back to disk to get the data, and query access would be slower due to disk IO.
So the rule is requiring that 90% of your store size (which is basically your graph.db folder size, minus your TX logs size) be allocated to page cache.
You have 196g page cache, but your store size is 3,860g.   And so your page cache is at least an order of magnitude smaller than what's on disk.
Now, what are the consequences?  You can ignore this halin rule.  It would be better for query performance if you had more page cache, but you have a big DB -- and if you don't add page cache the DB is still going to work fine, just with more page faults would be my guess and somewhat slower IO than pure memory.
Well, that's the explanation on why Halin is saying what it's saying.  Question from my side is how to make this more useful and explain it better.  I agree 196g is not small at all, but it is in relation to your on-disk size.   So:

Is Halin calculating your on-disk size correctly?
If it is calculating things correctly, how can we make this message more helpful/clear?


Feat/add circuit inversion

Adds functions for generating the inverse of circuits and gates. The Gate struct was also replaced by a Gate abstract type. This means that all gate types have their own struct which are descendants of the Gate abstract type. This improves performance since an Operator is no longer generated every time a gate is constructed. The use of dispatching also improves the extensibility of the get_inverse function.
Fixes #39

The ishermitian function has been renamed to is_hermitian.


[SPARK-21232][SQL][SparkR][PYSPARK] New built-in SQL function - Data_Type

What changes were proposed in this pull request?
New built-in function to get the data type of columns in SQL.
How was this patch tested?
Unit tests included.

Can one of the admins verify this patch?

Which systems have such function calls? Could you give some examples?

In some SQL db you have to query explicitly the table schema, ie: select data_type from all_tab_columns where table_name = 'my_table'or something like that.
In case of the ARQ engine from Apache Jena you can call this function in SPARQL (see W3C-SPARQL.
I find it useful in order to avoid to query the schema.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

can you rebase? (there is a conflict)

Test build #90100 has started for PR 18447 at commit 85421a1.

Test build #90100 has finished for PR 18447 at commit 85421a1.

This patch fails Scala style tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90100/
Test FAILed.

Build finished. Test FAILed.

Test build #90142 has started for PR 18447 at commit 04b81ee.

Test build #90142 has finished for PR 18447 at commit 04b81ee.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90142/
Test FAILed.

Test build #90145 has started for PR 18447 at commit 3ec9fbf.

Test build #90145 has finished for PR 18447 at commit 3ec9fbf.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90145/
Test FAILed.

Test build #90177 has started for PR 18447 at commit a1bb258.

Test build #90178 has started for PR 18447 at commit 704ad80.

Test build #90178 has finished for PR 18447 at commit 704ad80.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90178/
Test FAILed.

Test build #90179 has started for PR 18447 at commit d18d14f.

Test build #90177 has finished for PR 18447 at commit a1bb258.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90177/
Test FAILed.

Test build #90179 has finished for PR 18447 at commit d18d14f.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90179/
Test FAILed.

Test build #90199 has started for PR 18447 at commit a97ac1b.

Test build #90199 has finished for PR 18447 at commit a97ac1b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90199/
Test PASSed.

@felixcheung Everything done!

Test build #90256 has started for PR 18447 at commit ed52e2f.

Test build #90256 has finished for PR 18447 at commit ed52e2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90256/
Test PASSed.

Test build #90285 has started for PR 18447 at commit b964573.

Test build #90285 has finished for PR 18447 at commit b964573.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90285/
Test PASSed.

Merged build finished. Test PASSed.

so @felixcheung ?

I guess we still have an open question on https://github.com/apache/spark/pull/18447/files#r130032578

Can one of the admins verify this patch?

Can one of the admins verify this patch?

so @mmolimar ?

Hi @HyukjinKwon
For me it's fine:
"In some SQL db you have to query explicitly the table schema, ie: select data_type from all_tab_columns where table_name = 'my_table'or something like that.
In case of the ARQ engine from Apache Jena you can call this function in SPARQL (see W3C-SPARQL).
I find it useful in order to avoid to query the schema."

@MaxGekk and @rxin WDYT on this function? I am kind of neutral on this and wonder if you guys have some preferences.

@HyukjinKwon I also neutral since I don't have potential use cases for the function.

@MaxGekk, I was thinking we could use this instead of schema_of somehow

@mmolimar, let's leave this closed if there's no explicit positive feedback within few days.

Yea I'd probably reject this for now, until we see bigger needs for it.

ping @mmolimar to close


[question] Is file uploading supported?

Hello , im trying to implement a workflow where by the user can upload documents for approval , is it possible to have such functionality here in django-river ? If so , may i ask how it would be done? Thanks!

Hi @neowenshun
django-river can be extended as much as you like since it is built with native Django API. django-river is of course not supporting such a thing but it consists of a bunch of Django models which you can refer to in your own models as Foreign Key. What I can suggest is that you can implement that feature in your app and have the integration of django-river under the hood.
For example; you can have an app that calls approve and also do what you need on top of that and build the connection. The django-river model that you want to correlate with by using it as a Foreign Key in your model is TransitionApproval.

Closing this due to no activity.


sidebar menu: transparency issues

When I open http://maproulette.org:8080/map/-1/1331
And I do nothing else except moving my mouse to the sidebar menu.
Then I see see

On Firefox 46 and Chromium 50

This is a duplicate of Issue #62. So closing as duplicate.


Comment out bad link

At Daniel Grecoe's request

I think it's fine, just wondering why we are changing versions as well. If it's fine, don't care.


forums.nvidia.com

forums.nvidia.com redirects to forums.geforce.com
Match found in list.34.hosts.ubuntu101.co.za.domains:
forums.nvidia.com

Closing as this is a redirection,


Regenerate Category URL is VERY SLOW

Since removing the parameter (--check-use-category-in-product-url) the tool is impossible to use.
Generating all category URL for a specific store the progress bar indicates 0% 0/1153 and it takes over 45 minutes to progress to 0% 1/1153...
I don't use category path in product url.
Can you bring back the --check-use-category-in-product-url option?
Or what am I doing wrong?

Actually, it did manage to progress and it got faster as it progressed further.
I don't think it was actually any slower in total than if using the --check-use-category-in-product-url option
So a non-issue and I am going to close.
Thanks for a great extension.


false positive?

Id just like to point out having an exe file modify an extension is sus and not to mention virustotal  gave it a 5

Id just like to point out having an exe file modify an extension is sus and not to mention virustotal  gave it a 5

This has been raised as an issue before. It's open source for a reason, you're more than welcome to compile the code yourself and you would see that you would get the same false positives. The reason it's an exe is because I wanted to get some experience using Rust.

The reason why this is flagged as a false positive is because it tries to access the browser data of the selected browser/path.
Based on my research of opening the compiled project myself and opening the one I downloaded from here there seems to be no differences. However, it does not seem to be working on Windows 11 (64x) (unless I have done something wrong)

The reason why this is flagged as a false positive is because it tries to access the browser data of the selected browser/path.
Based on my research of opening the compiled project myself and opening the one I downloaded from here there seems to be no differences. However, it does not seem to be working on Windows 11 (64x) (unless I have done something wrong)
Slight edit, the antivirus engines that have infact detected it are objectively kind of bad.

Yeah people have been reporting it not working, I currently don't have the time to look into it but hopefully I will get to it in due time

Id just like to point out having an exe file modify an extension is sus and not to mention virustotal  gave it a 5

This has been raised as an issue before. It's open source for a reason, you're more than welcome to compile the code yourself and you would see that you would get the same false positives. The reason it's an exe is because I wanted to get some experience using Rust.

Ive put both yours and the original through virus total bruv and yours is way worse,

OOP- sorry I thought this was something else sorry about that


Bug in path resolution in local config file

Description
When running the following command: WfExS-backend/WfExS-backend.py -L local-config.yml execute -W test-stage.yml I got the following error message:
schema_salad.exceptions.ValidationException: Not found: '/root//root/wfexs-backend-test_WorkDir/efb98299-cb1f-48f8-862e-7a8746bba1a4/workflow/workflows/sec-hutchx86.cwl'

The path resolution appears to have added an additional /root/ to the front of the path in local-config.yml (see below). When I changed the workDir to  ./wfexs-backend-test_WorkDir, the execution appeared to proceed as expected and I saw this in the logging output:
materialized workflow repository (checkout 6d500ca1396283faae2ce5eebf778500dd8be2da): /root/wfexs-backend-test_WorkDir/f51c9984-8e43-49fa-a03b-8e683e884980/workflow

The path resolves as would be expected if I ran WfExS from /root.
Local config file
cacheDir: $HOME/wfexs-backend-test
crypt4gh:
  key: local_config.yaml.key
  passphrase: strive backyard dividing gumball
  pub: local_config.yaml.pub
tools:
  containerType: podman
  dockerCommand: docker
  podmanCommand: podman
  encrypted_fs:
    command: encfs
    type: encfs
  engineMode: local
  gitCommand: git
  javaCommand: java
  singularityCommand: singularity
  staticBashCommand: bash-linux-x86_64
workDir: $HOME/wfexs-backend-test_WorkDir

Stage file
workflow_id: https://raw.githubusercontent.com/HDRUK/hutch/main/workflows/sec-hutchx86.cwl
workflow_config:
  container: 'podman'
  secure: false
nickname: 'vas-workflow'
cacheDir: /tmp/wfexszn6siq2jtmpcache
crypt4gh:
  key: cosifer_test1_cwl.wfex.stage.key
  passphrase: mpel nite ified g
  pub: cosifer_test1_cwl.wfex.stage.pub
outputs:
  output_file:
    c-l-a-s-s: File
    glob: "output.json"
params:
  body:
    c-l-a-s-s: File
    url:
      - https://raw.githubusercontent.com/HDRUK/hutch/main/workflows/inputs/rquest-query.json
  is_availability: true
  db_host: "localhost"
  db_name: "hutch"
  db_user: "postgres"
  db_password: "example"

I have realized several unrelated issues in the configuration files you have shared here meanwhile I was trying to reproduce the issue with current version.
The first one is that the local configuration file is using what it seems environment variables both in workDir and cacheDir. Environment variable substitution for file paths in the local configuration file is not going to be implemented, so I guess you put them there in order to avoid disclosing local paths, right?
The second one is that the sample stage file you have included is using container key under workflow_config, instead of containerType one. The validation does not complain because those blocks are not being constrained by an "additionalProperties": false.
For this last issue, you can see the automatically generated documentation here: https://github.com/inab/WfExS-backend/blob/main/development-docs/schemas/stage-definition_schema.md#workflow_config
Last, once I fixed these two issues (replacing the environment variable placeholders by their values by hand and using containerType key), staging seemed to properly work.
So, I don't know whether I was unable to reproduce the issue, or it was fixed due past commits.

@dcl10 did you have a look at my previous answer of this issue? Is this issue still relevant?

Hi @jmfernandez, I'm afraid I hadn't taken a look.
However, I've had some luck changing how I specified workflow_id to be like pypi.
On the first issue, thanks for the heads up about workDir and cacheDir. We used them simply because they were in one of the example workflows. What should we do instead for these fields? Simply not specify them?
For the second one, I found in the docs that it should have been containerType and have using that since.
I think this issue can be closed now, so I'll do that. Thank you for having a look for me - much appreciated 👍


Buttons

Do we have to generate the JSON for the buttons on our own?

Yes, as there's many ways buttons can be defined. I made it generic so anyone can use it.


Cargo check  - wrong warning about unused code (edition=2018, nightly 2018-12-7)

Problem
cargo check warns about unused code that is actually used.
The desidered behaviour should be not to have these false positives.
Steps

Have a look at this gist. This is a reduced version, with a slightly different behaviour, of something I'm experiencing in this repo
Running cargo check produces the warning warning: method is never used: new

Possible Solution(s)
I suspect that is another manifestation of rust-lang/rust#54180. In case, feel free to clone in favor of that.
Notes
Output of cargo version:
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic
$ cargo version
cargo 1.32.0-nightly (5e85ba14a 2018-12-02)
$ rustc --version
rustc 1.32.0-nightly (4a45578bc 2018-12-07)
Thanks for looking!

I think this is expected.  You can run cargo check --profile=test to check with tests enabled which will make your warning disappear.  When a cfg block is used, rustc essentially deletes the code if it is not enabled, so it is not considered (beyond basic parsing).

Ah yes indeed, so closing!

thanks @ehuss for the super-quick answer. Yes, that warning disappears adding that param, but I'm still slightly confused when it comes to integration tests (the real reason I submitted this issue).
So, when I want to run cargo check on my integration tests (i.e. in ../tests) should I run cargo check --tests --profile=test? I had that warning also in code not marked by any #[cfg(test)] or #[test] block.
And if yes, why do I need two params to have cargo check my integration tests code?
Thanks for clarifying a bit more (still a newbie, sorry about that).

@ehuss it was not easy! :) but I managed to create a small repo with the smallest test case possible: https://github.com/apiraino/cargo_issue_6430
I also think I understand exactly how to trigger the unused_code false positive: basically when in the integration tests a submodule is not used by all tests file.

Ah, yea, I think that is expected to happen, since each test is essentially independent of one another. The test_2 target is correctly reporting that there are things unused as far as it's concerned.  It's not unusual for some projects to combine all of their integration tests into one executable.  It can simplify situations like this, and if you have a lot of tests, uses much less disk space.  Cargo itself does this – it has one main.rs which imports everything.

Wow, the more I learn, the more I discover new things :-) That looked counter-intuitive to me, but I understand the rationale behind.
Thank you for your time, really appreciated! :+1:

ok, follow-up to this issue.
I've moved all my tests into a separate crate. Now I'm building a monolithic library with all the integration tests. I've crated a separate project for this crate so I can copy and paste it as a starting point for my integration tests.
I think this issue can be closed


feat: proof verification tests

Issue being fixed or feature implemented

No tests for proof verification
What was done?

Added tests and helper functions for merk proof verification
How Has This Been Tested?

By running the suite
Breaking Changes

None
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[x] I have assigned this pull request to a milestone

Please note that this PR depends on https://github.com/dashevo/js-drive/pull/559


FancyZones causing system lag with multiple monitors and multiple virtual desktops

Microsoft PowerToys version
0.85.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
same issue #18568 and #18057
no workaround works
PowerToysReport_2024-10-18-06-52-52.zip
✔ Expected Behavior
no lag, working and typing immediately when switching to next virtual desktop
❌ Actual Behavior
when fancyzones is active and i switch between virtual desktops it causes a input lag
it also causes lag when immediately switching back to previousvirtual desktop
Other Software
No response

/dup https://github.com/microsoft/PowerToys/issues/27555


[Bug]: equinix_fabric_routing_protocol not using schema timeouts

equinix_fabric_routing_protocol waitUntilRoutingProtocolIsProvisioned function is not taking default schema timeout
https://github.com/equinix/terraform-provider-equinix/blob/42737f824bdcda3717f9de7585a4cbec8195b095/equinix/resource_fabric_routing_protocol.go#L573
In fact none of the "WaitFor" functions do it. I have also been able to verify that the same thing happens with other Fabric resources such as fabric_connection, fabric_cloud_router, fabric_network... This means that if users define a value to override the default value it is never being used.
Here's an example of how the schema timeouts must be consumed https://github.com/equinix/terraform-provider-equinix/blob/42737f824bdcda3717f9de7585a4cbec8195b095/equinix/resource_metal_device.go#L562

Furthermore, it almost always gives an error, so a longer default timeout would be more appropriate.

This has been updated and is available after this PR was merged: https://github.com/equinix/terraform-provider-equinix/pull/631
Closing issue.


Passing const string into function gives error saying its not a const string

Godot version
v4.0.3.stable.official [5222a99f5] via Steam
System information
Pop!_OS 22.04 LTS
Issue description
I have preloads that take const strings and I decided to do a refactor that passes these const strings into the function set_pickup_props() but the linter is saying that "Preloaded path must be a constant string" which makes no sense because it worked in the _ready function (the commented out code works) the only thing that is different is I'm calling it from set_pickup_props() which seems to print out the string correctly and then if I do typeof it gives "4" which I don't really understand unless its like an enum for something (it prints the same before passing it into the function).
Sorry, I'm new to godot so this might not be a bug and just me being dumb?

Steps to reproduce
Pass const strings into a function (in this case atlas_path param of set_pickup_props()); then it ceases to be a const string  :shrug:

extends Area2D

@onready var resource_type = $"."
@onready var resource_image = $resourceImage
@onready var resource_gathered_text_image = $RichTextLabel/ResourceGatheredTextImage
@onready var rich_text_label = $RichTextLabel
const PICKUP_TEXT_SPACE = 11
const pickups_stick_atlas = "res://item/pickups/pickups_sticks_atlas.tres"
const pickups_stone_atlas = "res://item/pickups/pickups_stones_atlas.tres"

func set_pickup_props(atlas_path,pickup_text,spacing):
#    print(typeof(atlas_path), atlas_path) # prints 4 res://item/pickups/pickups_stones_atlas.tres
    resource_image.texture = preload(atlas_path)
    resource_gathered_text_image.texture = preload(atlas_path)
    rich_text_label.text = "+"+pickup_text.lpad(PICKUP_TEXT_SPACE," ")

# Called when the node enters the scene tree for the first time.
func _ready():
  if resource_type.name.contains("Stones"):
#    print("Stones")
#    resource_image.texture = preload(pickups_stone_atlas)
#    resource_gathered_text_image.texture = preload(pickups_stone_atlas)
#    rich_text_label.text = "+"+"Stone".lpad(PICKUP_TEXT_SPACE," ")
    set_pickup_props(pickups_stone_atlas,"Stone",PICKUP_TEXT_SPACE)
  elif resource_type.name.contains("Sticks"):
#    print("Sticks")
#    resource_image.texture = preload(pickups_stick_atlas)
#    resource_gathered_text_image.texture = preload(pickups_stick_atlas)
#    rich_text_label.text = "+"+"Stick".lpad(PICKUP_TEXT_SPACE," ")
    set_pickup_props(pickups_stick_atlas,"Stick",PICKUP_TEXT_SPACE)

# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta):
  pass

func _on_body_entered(body):
  var current_inventory = preload("res://inventory/resource_inventory.tres")
  print("body enter: ",resource_type.name)
  if resource_type.name.contains("Stone"):
          Signals.Gather_resource.emit(current_inventory.slot_datas[0], 0, resource_type)
  elif resource_type.name.contains("Stick"):
          Signals.Gather_resource.emit(current_inventory.slot_datas[1], 1, resource_type)
  self.queue_free()

func _on_picked():
#  print("has picked")
  pass # Replace with function body.

Minimal reproduction project
I can put one together if it is actually a bug.

Function arguments are never const, regardless of what called with, this function could be called from anywhere

Function arguments are never const, regardless of what called with, this function could be called from anywhere
What you are trying to do isn't possible, and wouldn't be possible in other languages like C++

I don't know C++
@AThousandShips  Oh okay thanks!, Shall I close this issue then?

I was merely giving an example :)
As this isn't a bug, and the error should be clear I'd say there's nothing more needed here

I was merely giving an example :)

Yep got it; I'll try it out in other languages. :)

As this isn't a bug, and the error should be clear I'd say there's nothing more needed here

Sweet thank you!

func set_pickup_props(preloaded_atlas,pickup_text,spacing):
    resource_image.texture = preloaded_atlas
    resource_gathered_text_image.texture = preloaded_atlas
    rich_text_label.text = "+"+pickup_text.lpad(PICKUP_TEXT_SPACE," ")

set_pickup_props(preload(pickup_atlases.stone),"Stone",PICKUP_TEXT_SPACE)

For anyone's reference I ended up passing the preload in instead...


Confirm timeout functionality added

cosmetic changes
bump SRL up to 23.3.2
add new errors related to confirm timeout
confirm timeout objects
add confirm timeout
removed unnecessary Logf
added SetConfirmTimeout and WithConfirmTimeout
Extended tests with confirm timeout
Extended Update/Replace/Delete/BuldSet with confirm timeout, added BulkSetCallBack to support || validation testing and callback verificaton for CI pipelines
Extended tests with confirm timeout and added spcific tests for BulkSetCallBack

Confirm timeout added.


the excess builds were not deleted

Describe the Bug

The maximum number of build records is set to 1
In the build list, the excess builds were not deleted

Versions Used
KubeSphere: kubesphere v3.2.1-rc.1
Kubernetes: (If KubeSphere installer used, you can skip this)
/assign @JohnNiang
/kind bug
/priority Medium

I am interested in this issue and hope to try to solve it

@mzmuer Great! Please let us know if you need any kind of help.

@LinuxSuRen @JohnNiang

@LinuxSuRen @JohnNiang
I have found out the cause of the problem, Is this a legacy issue?
I'm prepare to remove excess records at the end(finish, cancel, fail) of the job execution or process them when the list is returned.
May I ask what kind of practice is generally preferred according to the project.

Normally, I prefer to remove the PipelineRuns in two ways:

pipeline gc command
Receive the delete event from Jenkins (manual or automated), then ks-devops can delete it

For this case, I guess there are two components: event-receiver in ks-devops, event sender as a Jenkins plugin
pipeline-event-plugin is a draft project to play as an event sender
we have not started the event receiver part

Normally, I prefer to remove the PipelineRuns in two ways:

pipeline gc command

Receive the delete event from Jenkins (manual or automated), then ks-devops can delete it

For this case, I guess there are two components: event-receiver in ks-devops, event sender as a Jenkins plugin
pipeline-event-plugin is a draft project to play as an event sender
we have not started the event receiver part

I see. Event-drive is a better solution. So now when the job end(or list returned) use similar cleanPipelineRunInNamespace  function to temporary solve the problem?

Yes, I'm thinking about if you're interested in the event-driven feature. I personally prefer to have a final solution in release 3.3 instead of a temporary one.
By the way, we have a SIG meeting this week. Please join us and let's talk about it if you have free time.

Yes, I'm thinking about if you're interested in the event-driven feature. I personally prefer to have a final solution in release 3.3 instead of a temporary one.
By the way, we have a SIG meeting this week. Please join us and let's talk about it if you have free time.

thank you, very interested and to join yous. But I'm new to DevOps, so I still play a learning role.

We have a WeChat. Please add me (ID: linuxsuren) as a WeChat contact, I can let you in it.

reference issue: #847


Objective-C Support

Xcake currently supports Objective-C so we should consider adding this as well as other Objective-C features like Class Prefixes etc.

Hi @jcampbell05, struct has support for Objective-C targets built in, however this definitely can be refined. If there are specific cases in which refinements can be made, feel free to suggest them as individual issues!