symmetry-aware loss

Hello, could you tell me what's the purpose of the following code snippet?
Is there any reference to this loss function?
https://github.com/sThalham/COPE/blob/48d926baad6d7da5332fe03cba2e4ed0ab05daed/cope/losses.py#L446-L456

Hi @Ending2015a,
there is no reference to this. It's just something I came up with as an ad-hoc solution to some problems that occured along the way. It is only computed for the keypoint loss.
It's purpose it twofold. On the one hand, by reweighting the individual losses per symmetry hypothesis I can simply sum over all of them without having to index using a sparse tensor. On the other hand, it has a damping effect on the loss and thus leads to smoother convergence.
Best regards.

@sThalham
Thank you for your thorough explanation.
I can see that this loss can help the model fit to one of the pose candidates, if there are many.
Besides, I was trying to reproduce your training results on linemod occlusion dataset.
But after a month of trying, I still can't get the results as the trained model you provided.
Could you please provide more instructions on how to reproduce the results?
I used the following command to train the model with the default hyperparameters.
python cope/bin/train.py --batch-size 8 \
  --tensorboard-dir /output/cope-R101-Adam-2/ \
  --snapshot-path /output/cope-R101-Adam-2/ \
  linemod /dataset/cope_dataset/lmo/train_pbr/

The BOP evaluation results I got:
FINAL SCORES:
2/5|01:31:15: - bop19_average_recall_vsd: 0.02086505190311419
2/5|01:31:15: - bop19_average_recall_mssd: 0.031141868512110725
2/5|01:31:15: - bop19_average_recall_mspd: 0.19404844290657436
2/5|01:31:15: - bop19_average_recall: 0.08201845444059976
2/5|01:31:15: - bop19_average_time_per_image: 0.09701341474144692

Your model's (LM/LM-O weights) evaluation results:
1/30|06:52:40: FINAL SCORES:
1/30|06:52:40: - bop19_average_recall_vsd: 0.3835847750865052
1/30|06:52:40: - bop19_average_recall_mssd: 0.5006920415224914
1/30|06:52:40: - bop19_average_recall_mspd: 0.7115570934256056
1/30|06:52:40: - bop19_average_recall: 0.5319446366782007
1/30|06:52:40: - bop19_average_time_per_image: 0.1025944362951464
1/30|06:52:40: Done.

The training curves:

Hi @Ending2015a,
sorry that you're having such a hard time reproducing the results.
When preparing the data using "annotate_BOP.py" do you run it using "linemod" or "occlusion" as dataset? That's a potential source of error. You should specify "linemod" there. But that wouldn't explain such a large drop in performance, imo.
I will update the README to provide a detailed explanation on reproduce the paper results in the next days.
Best regards,
Stefan

@sThalham
I passed lmo when running annotate_BOP.py script (on cope_WACV branch) and passed linemod for training. But I didn't see any difference between passing "lm" and "lmo" when running the annotate script, though. The training set I used is the train_pbr split provided by BOP challenge, and it is shared between lm and lmodataset. And I believe the dataset is properly generated because the ground truth visualization produced by evaluate.py seems quite well.
I think the performance drop might be caused by the training procedure because I saw the translation loss epoch_tra stopped improving after 15 epochs but I have no idea on how to fix it. Changing the LR schedule to constant lr=1e-5 doesn't help.
Really appreciate your help. I'll wait for your update.

I am not certain that there is no difference in training behaviour when training on LM with data generated for LMO.

One thing that is not handled properly: line 464 in annotate_BOP.py only excludes the cup and the bowl from annotation for LM. And not for LMO.
Which set of meshes are you using? The LM or the LMO one?

Your starting losses look sensible. However, it is most likely connected to the keypoint loss (pts). I just checked, pts loss is ~2.6 at the end of the first epoch and ~0.4 at the end of epoch 10 for me.

@sThalham
I've rerun the annotate_BOP.py with linemod.
Are you using the training script on cope_clean branch or cope_WACV branch?

For the paper results it's the cope_WACV branch. cope_clean is under development, there are some usability modifications and parameter to pass are different. Theoretically it's supposed to result in similar performance, atm.
But your problem is most likely connected to the steps_per_epoch you are using. For the paper I trained 120 epochs à samples/batch_size. So the parameter "steps_per_epoch" should be 6250, per epoch.

@sThalham
Thank you, I think now I can reproduce the results!
The only concern is that the training process is very slow. It took about 21 days to train the model with ResNet101 backbone for 120 epochs on two 2080Ti (batch size 8). Though I have only run for 40 epochs but I think the result is reproducible. I will use this codebase for my own research.
I will close this issue. Thank you very much for your help!

Hi @Ending2015a,
great that you can now reproduce the results.
Unfortunately, there might be still something going wrong. I also have a 2080Ti, training time is ~140h (~5days), with a batch size of 8. Try to increase the "workers" parameter. But it shouldn't take that long, even when using only 1 worker.

@sThalham
I can't run ResNet101 on 2080Ti with batch size 8 because of the OOM issue. The maximum batch size I can use is 6.
But maybe I will try using single GPU with a smaller batch size, which is 2x faster (~8days) instead of two GPUs, because tensorflow doesn't support decorating @tf.function on train_step when using MirroredStrategy for multi-gpu training.


Backport Integration Tests

Description

We've new integration tests on cardano-wallet for quite a while now. Integration tests on cardano-sl were disabled because they were buggy and not-so-reliable. Therefore, in order to increase confidence that the code on cardano-sl/develop is indeed tested in a similar way, this PR backports and activate the integration tests on cardano-sl (since they are just a normal test suite listed in the .cabal file, they should just get picked up automatically by buildkite and the CI on cardano-sl)
Linked issue

Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[x] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

How to merge
Send the message bors r+ to merge this PR. For more information, see
docs/how-to/bors.md.

bors r+

bors r+


Cannot select defined hierarchies when using "List associated assets" query type with another variable

What happened:
In a dashboard, I want to create and use multiple variables which store asset lists corresponds to each asset hierarchy.
To achieve this, for example,

Create variable parent using "List assets" as Query type and suitable asset model
Create variable child using "List associated assets" as Query type, ${parent} as Asset, and suitable hierarchy
Create variable grandchild using "List associated assets" as Query type, ${child} as Asset, and suitable hierarchy
...

It worked as expected for plugin versions from 1.3.0 to 1.5.1. But when I tested this with 1.6.0, It didn't work.
What you expected to happen:
In the Show field, defined hierarchies can be selected even if another variable is specified in the Asset field.
How to reproduce it (as minimally and precisely as possible):

Create an asset model like Child Asset Model on AWS IoT SiteWise.
Create another asset model like Parent Asset Model and define a hierarchy like Parent-Child-Hierarchy with the Child Asset Model.
Create some assets (like Parent Asset A and Child Asset A) for each asset model, then associate them using defined hierarchy.
On Grafana, go to any dashboard and open the Dashboard settings, then select Variables.
Create a variable like parent (with Label "Parent") using SiteWise data source and specify List assets in the Query type field and Parent Asset Model in the Model ID field, then click Apply.
Create another variable child and specify List associated assets in the Query type, ${Parent} in the Asset field.
But on the Show field, I cannot select Parent-Child-Hierarchy, so I cannot get expected results for the variable.

Screenshots

Anything else we need to know?:
Environment:

Grafana version: 9.3.4
Plugin version: 1.6.0
OS Grafana is installed on: Ubuntu 22.04
User OS & Browser: Windows10 & Chrome
Others:

Thanks in advance.

I was able to reproduce this and it looks like a bug on our end when interpolating variables. @nyamad the only workaround I can think of is if you select the parent directly instead of the variable, is this manageable for now? In the meantime we're taking a look.
Thanks for bringing this to our attention!

@idastambuk Thanks for checking and comment.
Also, thanks for proposal of work-around. However, we want to realize dynamical dashboards with several variables based on several hierarchies, without hard-coding of asset instances. So we'll use old version for the moment.
Thanks again,

Hi @nyamad,
we've just released a new version of the plugin which contains the fix for this. Thanks for reporting it and hope this resolves your issue!

@idastambuk I could confirm this issue was fixed with new version.
Thank you so much for your great efforts!


DAT model for other restoration work

Can DAT model works well on other restoration works？Like deblur or denoise？

Hi,
Since the architecture of DAT is similar to SwinIR, it can be applied to other restoration works by replacing the reconstruction module. For more information, you can refer to SwinIR. But since DAT is designed for SR, the performance on other tasks may be not very good.
You can also apply the DSTB and DCTB to UNet architecture, which I think should be better than the current architecture of DAT in deblur or denoise tasks.

Hi, Since the architecture of DAT is similar to SwinIR, it can be applied to other restoration works by replacing the reconstruction module. For more information, you can refer to SwinIR. But since DAT is designed for SR, the performance on other tasks may be not very good.
You can also apply the DSTB and DCTB to UNet architecture, which I think should be better than the current architecture of DAT in deblur or denoise tasks.

Thanks a lot. It's a great work.


Falling Blocks

Dodge the falling blocks for as long as you can. Use A and D to move.
I have experience coding in Python, but I do not have as much experience with JavaScript.

Thanks for the PR, interesting game! One minor suggestion I have is that the block don't seem to actually touch the ground, they disappear before reaching the ground. Try tweaking your code, so they reach the ground and then disappear, let us know if you need any help!

I fixed the game so the obstacles reach the ground before disappearing.

That works! There are still some minor issues I just noticed, if you quickly move after being hit by a block, the block stays there. Another very rare issue, if you move into a block just before it gets removed, it removes the player as well. I have an idea how those two could have occurred, let us know if you need any help. Happy hacking!

Is there a way to remove all tiles in the last row without removing the player?

You should be able to check the type with
if (sprite.type != "p")

Thank you! I have fixed the bugs.

Great game!
I would merge this if I had the permissions :)

It's an elegant game. Welcome to the gallery!  You can order it here: https://sprig-order.hackclub.dev/


New container itksnap 4.0.2

There is a new container by @stebo85, use this command to test:
bash /neurocommand/local/fetch_and_run.sh itksnap 4.0.2 20240115

If test was successful, then add to apps.json to release:
https://github.com/NeuroDesk/neurocommand/edit/main/neurodesk/apps.json
Please close this issue when completed :)

#close
From: vnm-neurodesk @.>
Date: Monday, 15 January 2024 at 11:44 am
To: NeuroDesk/neurocontainers @.>
Cc: Steffen Bollmann @.>, Mention @.>
Subject: [NeuroDesk/neurocontainers] New container itksnap 4.0.2 (Issue #565)
There is a new container by @stebo85https://github.com/stebo85, use this command to test:
bash /neurocommand/local/fetch_and_run.sh itksnap 4.0.2 20240115
If test was successful, then add to apps.json to release:
https://github.com/NeuroDesk/neurocommand/edit/main/neurodesk/apps.json
Please close this issue when completed :)
—
Reply to this email directly, view it on GitHubhttps://github.com/NeuroDesk/neurocontainers/issues/565, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6V2W7ZQV6YPISRA6MFAXTYOSCZRAVCNFSM6AAAAABB2RFRNWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DCMBZGQ4DENA.
You are receiving this because you were mentioned.Message ID: @.***>


Making Approle Path an Environment variable to cater for Vault

Please see issue:
https://github.com/ConsenSys/quorum-account-plugin-hashicorp-vault/issues/21

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @baptiste-b-pegasys, will this change be merged?

hello, the main issue is to get the github action all green. We tried to upgrade to go 1.18, but it's failing. Another project had been updated since, and it's not possible to get the itests green.
I will take a look again where we are from now.

Sorry to keep bothering @baptiste-b-pegasys but any updates on this?

not able to pass the make itest for the moment

@kenrickles getting there finally! Can you fix up the build and we should be good

We should be good to go. But I tested locally. So fingers crossed 😅

Seems like the tests on signer isn't working. I'll give it a go tomorrow.


Disable the test_cmsg_nxthdr test

A stopgap for https://github.com/rust-lang/libc/issues/3181

@bors r+ p=101

:pushpin: Commit 6a61e0a66602821193751fe1d578647905ed127c has been approved by JohnTitor
It is now in the queue for this repository.

:evergreen_tree: The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

:hourglass: Testing commit 6a61e0a66602821193751fe1d578647905ed127c with merge 7adf246da838e6ae8d5cafb4ffe44098aa03c223...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 7adf246da838e6ae8d5cafb4ffe44098aa03c223 to master...


Generating Nixpkgs reference documentation from source code comments

Edit: I am not working on this, this is a proposal.
I propose to integrate API-documentation in Nixexprs, as to be able to write any sensible programmer-facing documentation at all.
I have a few ideas from my beginner-perspective, though I am probably simplifying the issue.
As far as I see it we have attributes as basic semantic building blocks. Those are anything from nullary to n-ary, or 1-ary if we take currying into account. Since they follow a simple definition scheme, it should be not hard to find a recursive strategy on how to handle documenting them.
There could be a haddock-like approach where there is a third-party program that parses special commands and generates documentation, but I think with nixexprs we can do better than that and store it directly as metainformation. That way it can even be used by tools like nix-repl.
A syntactic sugar version would be a haddock-like syntax built into the parser that is then stored as metainformation.
Example (syntax of course subject to debate):
# | The actual default version of the haskellNG packages
haskellngPackages = haskell-ng.packages.ghc784.override { … }

# | My funny lambda function
myLambda =
  # ^ because it’s super it takes that as first argument
  super:
  # ^ give it packages and a name or anything really. Will use it, promise.
  { pkgs, name, … }:
    …

Probably better if I throw that to the ML.

I hate inline documentation (not comments). It makes code unreadable for me unless your editor supports a decent comment-folding. But then you may hide important comments.

Should this move to the mailing list?

@lethalman Documentation of 0-ary attributes should be possible within one line in normal cases and as history teaches us variable names themselves are often ambiguous.
Library functions should be rigorously documented in any case (and in the code).
Of course arguments for lambdas you put into well-specified higher-order functions shouldn’t need documentation in the normal case, so no clutter there.

Then what's the point of autogenerating a graphical docs. It's not docs, it's comments for critical/hard to understand piece of code.

It’s called Application Programming Interface for a reason. Because one normally don’t want to read the standard library source to use its functions.

@Profpatsch, how much time have you spent working with Nix so far? What is your level of experience with this project?

So you are going to autogenerate an html docs for a couple of functions where a couple of comments are enough in the source code that you are going to read anyway in most cases in nixpkgs. Hope that will be useful to anybody.

I personally think it would be a nice to have a generated reference for nixpkgs functions. In many places there is already a good description before the function, only it's often not very easy to find out where a function is defined.
I feel people will be much more inclined to keep short comments up to date than to meddle with docs in external files. Functional programming style is much about creating many small composable functions, and we can't expect everyone to know all of them by heart. (Example: I find haddock+hayoo a very useful reference whenever doing something in haskell.)
It shouldn't be too hard to take an existing tool (e.g. doxygen) and add some basic support for *.nix files, maybe even using parser spec files from nix.

Changed the title because that was not the primary idea: The source code comments are just optional syntactic sugar.


Fix bug: User was not able to update details without providing password

Current code was raising error, When user was trying to update name / other details from UI
backend_1       |   File "./app/crud/crud_user.py", line 34, in update backend_1       |     if update_data["password"]: backend_1       | KeyError: 'password'

@tiangolo Could you review / merge this

This should be merged asap

Nice solution, but unfortunately it's duplicated: #346

Thank you! Good catch @vikrant-pune :nerd_face:
This was solved in another PR, so I'll now close this one. :coffee:


newbie - however API feels inconsistent - would some refactoring improve consistency?

I have been having a play with easyRules for a project - i like the simplicity of the model (havnet volume tested for performance - this is more about the API
I've been looking at easyRules and springboot.  however i cant quite reconcile the model differences between jmxRuleEngine and ordinary ruleEngine.  Why are there tow class types, in my head they better as configuration -RuleEngine (jmxEnabled true/false)
also the BasicRule class (evaluate & execute) is defferent from using @rule to convert a pojo into spring bean (condition/action/action etc )
when i tried to add a Spring @rule class to ruleEngine.addRule it wouldn't accept it, i had to get a rulesEngine from the spring context (after config ) and added spring rule to that engine and that worked - but that meant i had two engines to play with
as a new user of easyRules i found this a little perplexing and inconsistent, and forced you make choices for one mode or the other (extend BasicRule, or go for the Spring bean model, or jmx, not jmx ) .
I managed to get various samples up and running but the usage was inconsistent and I felt could be simplified and harmonised to remove these differences and make the developer 'experience' easier and more consistent.
I admit that i haven't coded as a developer 'for real' for many years now - so apologies if i have not got the best way to use this, but just wanted to plant a seed of thought for consideration.  I'll have another little play - i'm using groovy so it maybe i can see if its possible to 'hide' some of the mechanical differences and see what that looks like

Hi,
Thank you for trying out Easy Rules!

however i cant quite reconcile the model differences between jmxRuleEngine and ordinary ruleEngine. Why are there tow class types, in my head they better as configuration -RuleEngine (jmxEnabled true/false)

This is inconsistent, you should register Jmx and non Jmx rules the same way, it is the role of the framework to make this transparent to the user. I am planning to fix that in the next release.

also the BasicRule class (evaluate & execute) is defferent from using @rule to convert a pojo into spring bean (condition/action/action etc )

As of version 1.x, there was a big inconsistency in the framework: annotated rules and rules extending the BasicRule class or implementing the Rule interface were registered using two different types of engines. In order to make both approaches consistent, we decided to make annotated POJOs implement the Rule interface using proxies (see issue #12 for more details). That said, both approaches are different indeed, but is this really problematic? You have the choice between two options and the framework offers you the flexibility to choose the one that better fits your needs

when i tried to add a Spring @rule class to ruleEngine.addRule it wouldn't accept it, i had to get a rulesEngine from the spring context (after config ) and added spring rule to that engine and that worked - but that meant i had two engines to play with

I'm not sure I understand this point, can you give me an example please? If you believe this is a bug, please open a separate issue.

as a new user of easyRules i found this a little perplexing and inconsistent, and forced you make choices for one mode or the other (extend BasicRule, or go for the Spring bean model, or jmx, not jmx ) .

So let me summarise, there are basically two points:

Extend BasicRule/ Implement Rule vs Annotating a POJO: the framework offers you two different ways to implement your business rule, it is up to you to choose the best choice that fits your needs

Jmx managed rules vs Non Jmx managed rule: As said before, I do agree with you, this is inconsistent and I'm planning to improve it in the upcoming release.

would some refactoring improve consistency?

Sure, Easy Rules can be improved in many ways, you are welcome to improve the design or implementation!
Kind regards
Mahmoud

Hi,

Jmx managed rules vs Non Jmx managed rule: As said before, I do agree with you, this is inconsistent and I'm planning to improve it in the upcoming release.

I'm struggling to find a clean way to implement JMX managed rules in a compatible way with android. Hence, I've decided to deprecate the feature (see issue #47)

when i tried to add a Spring @rule class to ruleEngine.addRule it wouldn't accept it, i had to get a rulesEngine from the spring context (after config ) and added spring rule to that engine and that worked - but that meant i had two engines to play with

I'm not sure I understand this point, can you give me an example please?
Kind regards
Mahmoud

Mahmoud,
sorry been distracted at work and havent had the spare time to address this realistically
one thing i was looking at the was the java std api for rules (JSR 94) -
havent studied the android issue so cant comment
still need to have a proper think about how to  wrap what you have done - so not forgotten just distracted - will try and restart shortly
Will
----Original message----
From<EMAIL_ADDRESS>Date : 19/08/2016 - 13:27 (GMTST)
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject : Re: [EasyRules/easyrules] newbie - however API feels inconsistent - would some refactoring improve consistency? (#31)
Hi,
Jmx managed rules vs Non Jmx managed rule: As said before, I do agree with you, this is inconsistent and I'm planning to improve it in the upcoming release.
I'm struggling to find a clean way to implement JMX managed rules in a compatible way with android. Hence, I've decided to deprecate the feature (see issue #47)
when i tried to add a Spring @rule class to ruleEngine.addRule it wouldn't accept it, i had to get a rulesEngine from the spring context (after config ) and added spring rule to that engine and that worked - but that meant i had two engines to play with
I'm not sure I understand this point, can you give me an example please?
Kind regards
Mahmoud
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/EasyRules/easyrules","title":"EasyRules/easyrules","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/EasyRules/easyrules"}},"updates":{"snippets":[{"icon":"PERSON","message":"@benas in #31: Hi,\r\n\r\n\u003e Jmx managed rules vs Non Jmx managed rule: As said before, I do agree with you, this is inconsistent and I'm planning to improve it in the upcoming release.\r\n\r\nI'm struggling to find a clean way to implement JMX managed rules in a compatible way with android. Hence, I've decided to deprecate the feature (see issue #47)\r\n\r\n\u003e when i tried to add a Spring @rule class to ruleEngine.addRule it wouldn't accept it, i had to get a rulesEngine from the spring context (after config ) and added spring rule to that engine and that worked - but that meant i had two engines to play with\r\n\r\nI'm not sure I understand this point, can you give me an example please?\r\n\r\nKind regards\r\nMahmoud"}],"action":{"name":"View Issue","url":"https://github.com/EasyRules/easyrules/issues/31#issuecomment-241005111"}}}

Hi,
Implementing JSR 94 has been considered since the early stages of Easy Rules but has never been a first order concern. This will require a major API change, I may consider it in the next major release v3.
I'm closing this issue for now, if you have any other question, I'll be happy to help.
Kind regards
Mahmoud


Upgrade Camel from 4.0.0-RC1 to 4.0.0

Camel 4 was just released, can you update to 4.0 ?

see https://github.com/apache/camel-kamelets/issues/1579

YAKS tests have been fixed with PR #1586
The changes got merged already so cloud you please rebase base on it, thx

rebased, require a committer to approve launchign the GitHub workflows


qt6.qtbase: fix plugin loading through symlinks

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

No tests for qt6? :(

For anyone waiting for this to land, a workaround is to repackage the plugin to not use symlinks, with cp -r --dereference. See this for an example for fcitx5:
https://github.com/dramforever/config/commit/1f3030741ed1d3f6a0af1b61cfa0016083917b58


No matching distribution found for tensorflow~=1.12.0 (from rasa_core)

Rasa Core version: pip install rasa_core
Python version: 3.6
Operating system (windows, osx, ...): windows 10
Issue:
I keep getting this tensorflow error ;
Collecting rasa_core
  Using cached https://files.pythonhosted.org/packages/3e/6a/f2c4e8ae1903805324267e915a167ded91a439bafd09efa6da0a2a50e409/rasa_core-0.13.3-py3-none-any.whl
Collecting rocketchat-API~=0.6.0 (from rasa_core)
  Using cached https://files.pythonhosted.org/packages/5f/c0/117b97e5b4e057808b4db1dda3bfb9aef46e502b7f8107bc8e33d2df7ee9/rocketchat_API-0.6.27-py3-none-any.whl
Requirement already satisfied: ruamel.yaml~=0.15.0 in c:\users\asus\islemenv\lib\site-packages (from rasa_core) (0.15.37)
Collecting tensorflow~=1.12.0 (from rasa_core)
  Could not find a version that satisfies the requirement tensorflow~=1.12.0 (from rasa_core) (from versions: )
No matching distribution found for tensorflow~=1.12.0 (from rasa_core)

I already tried this but still didn't work
 python -m pip install --upgrade
https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-1.12.0-py3-none-any.whl

EDIT:  I solved this by installing an older version of rasa-core with tensorflow 1.10.0 ; then upgraded both ; dunno how it worked but it did

@paxinos is it possible that you have python 3.7 installed, because we don't quite support that yet

Thanks.  That was it.

Folks, please update your documentation, as it seems like only 3.6 python is currently supported. Note that 2.7 is usually OS-bundled, and 3.7 is the latest one. Neither of these 2 allows installing rasa core. It might be a very disappointing first impression, as people fail to install software from the very beginning.

that's not true, python 3.5 is supported as well and we're working on supporting python 3.7
support for 2.7 has been dropped because python themselves are dropping support for that soon.
Could you point me to where this is out of date? our github repos at least have the correct badges as far as i can see

Sorry for being inaccurate with 3.x version assumptions. My bad.
Regarding references: neither NLU nor Core installation sections have notes about supported Python versions.
Personally to me, who doesn't know Python ecosystem yet, it wasn't quite obvious to find the reason of the failure. And the first place where I was looking at, was your official extensive documentation. Badges are quite easy to miss, when you've just started playing with a product. But thanks for pointing out.

yeah that's a fair point -- would you be willing to raise a PR to add that to our documentation?

Am also facing the same issue.

strange, tensorflow 1.12 definitely exists. Potentially a windows related problem. In any case, sounds like your issue is solved so I will close

1.12.0 has moved 1.12.2 may be a hard validation of 1.12.0 in requirements.txt is failing.

again, right now we just support 3.5 and 3.6. If you take a look at the open PRs you'll see there's one for python 3.7 compatibility. Tensorflow isn't the only package that needs to be updated for that, so we're still making sure everything runs. Once that's merged, python 3.7 will be supported on master

Hey all, I got the same error on Python 3.5. I found the way out by using Python 3.7.4.

Hello friends, i am a bit frastrated I want to import tensor flow in my anaconda but i keep getting the error (ERROR: Could not find a version that satisfies the requirement tensorflow (from versions: none)
ERROR: No matching distribution found for tensorflow)
I have tried multiple options online. please help

Hey all, I got the same error on Python 3.5. I found the way out by using Python 3.7.4.

How did you solve that?

Myself I don't know how to do it in Python 3.5, I tried it Python 3.7.4.
and it was a challenge, how did you do it.? Please help
On Wed, Oct 23, 2019, 22:56 Omarwoth Jonathan<EMAIL_ADDRESS>wrote:

Hey all, I got the same error on Python 3.5. I found the way out by using
Python 3.7.4.
How did you solve that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/RasaHQ/rasa/issues/3048?email_source=notifications&email_token=AG6PMBLLIKTGQQ732LXBRMLQQCT7BA5CNFSM4HAFMHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCVTKI#issuecomment-545610153,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6PMBLBI4OC3LUR56PBDC3QQCT7BANCNFSM4HAFMHYA
.

@nich02 which version of rasa are you installing and in which environment are you getting what errors? Would be good if you can post all this information here

any one using tensorflow in windows
please tell me that python version and tensorflow version
and windows version

I have a similar issue - https://forum.rasa.com/t/error-no-matching-distribution-found-for-tensorflow-1-14-0-from-rasa-1-4-0-rasa-x/21171

how to resolve this problem 👍
RROR: Could not install packages due to an EnvironmentError: [WinError 5] Access is denied: 'C:\Users\USER\Anaconda3\envs\py374\Lib\site-packages\numpy\core\_multiarray_tests.cp37-win_amd64.pyd'
Consider using the --user option or check the permissions.

Hi, I have a same problem. how did you solved it?

I have the same issue, with Ubuntu OS and python 3.6, tried installing rasa-core and got this error
$ pip install rasa-core
ERROR: Could not find a version that satisfies the requirement tensorflow~=1.13.0 (from rasa-core) (from versions: 2.2.0rc1, 2.2.0rc2, 2.2.0rc3, 2.2.0rc4, 2.2.0, 2.2.1, 2.3.0rc0, 2.3.0rc1, 2.3.0rc2, 2.3.0, 2.3.1, 2.4.0rc0)
ERROR: No matching distribution found for tensorflow~=1.13.0 (from rasa-core)


Feature request: Custom str method for WPS Process class

So that print(process) displays the identifier.

@huard One could also have the identifier+title for print(myprocess) and identifier only for repr(myprocess).

Tried it, very nice, but I think it breaks the convention for __repr__:
object.__repr__(self)
Called by the repr() built-in function to compute the “official” string representation of an object. If at all possible, this should look like a valid Python expression that could be used to recreate an object with the same value (given an appropriate environment). If this is not possible, a string of the form <...some useful description...> should be returned. The return value must be a string object. If a class defines __repr__() but not __str__(), then __repr__() is also used when an “informal” string representation of instances of that class is required.
This is typically used for debugging, so it is important that the representation is information-rich and unambiguous.
So I suppose the __repr__ could look something like <owslib.wps.Process identifier object at ...>.
We have more freedom for __str__, but I think it's worth including the fact that it's a wps process, ie something like: identifier wps.Process: title

@huard I have made an update to the repr method. What do you think? How to handle the undefined values? If you like to add a patch for this you are welcome :)

Looks good. There is nothing left to patch.

Ok, thanks.


Update lighthouse version to latest(v7.2.0)

Lighthouse NEW VERSION released.
I had PROTOCOL_TIMEOUT error in sitespeed plugin-lighthouse and lighthouse cli both.
But after update lighthouse cli to v7.2.0, still got error but not fail the test.
So I ask you to update the version of sitespeedio/plugin-lighthouse to latest.

I've made a PR, please feel free to do one yourself the next time :)


Updated Images End of May

Updated Docs with new images in Fairfax
@brendalee @smichelotti

@sarahwel,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@sarahwel : Thanks for your contribution to the Azure documentation! The author, @brendalee, has been notified to review your proposed change.

Thanks for updating, @sarahwel! #sign-off


Add regression test

This PR adds a regression test for #2824.
Todo:

[ ] Execute the test with disabled exceptions.

Coverage remained the same at 100.0% when pulling 1c030cccf17f4079c06ac5977ce8936a5776f5f4 on issue2824 into a563338039346c9ed722e09547419190b1eeddbe on develop.


Update field names to match latest API.

Ready for review, @anselmbradford. Thanks!

Merging now because I forgot that I had enabled automatic Heroku deploys from the master branch (which I turned off now), so the API was already deployed, which means the OWS demo site is not showing certain fields.

:+1:


config.yml , twig_config: and cache: false

I'm moving my site from from pico CMS 1.0.6 to 2.0-beta3,
all goes well, but I can't find the information on the following:
config.yml
twig_config:
cache: false                    # Enable Twig template caching by specifying a path to a writable directory
My question is, WHERE do I define/specify my cache directory, as it seems that the variable is a boolean.

twig_config is passed through to the Twig_Environment class, allowing you to set arbitrary Twig environment options. See https://twig.symfony.com/doc/1.x/api.html#environment-options for a complete list of options.
To answer your question: The twig_config.cache option is either false or a path to the desired cache directory. Try
twig_config:
    cache: /path/to/twig/cache

After a big facepalm ;-), english is not my native language, but now reading is the answer was already documented in the comments.
Thanks for the answer, especially for the link to Twig_Environment class.
Item can closed.


determine rotation, microturb, and macroturb at test time

The idea is to fit the labels and a few more parameters.  Hogg has a trivial implementation idea.

I am assigning this to me to write the latex one-pager.


PublishCodeCoverageResults should support .coverage files

Environment

Server - Azure Pipelines

Issue Description
The PublishCodeCoverageResults task does not currently support Visual Studio .coverage files. I use Cake Build instead of the built in tasks and want to use PublishCodeCoverageResults to publish my code coverage results.

A thousand times yes! This issue was raised before and never made sense to me. VSTest task somehow manages to publish .coverage files that VSTS understands - so we should be able to do it as well!


Bitmap allocator pixelref

Description of Change

Bugs Fixed

Fixes #

API Changes
None.

Behavioral Changes
None.

Required skia PR
https://github.com/mono/SkiaSharp/pull/2150
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[ ] Rebased on top of main at time of PR
[ ] Merged related skia PRs
[ ] Changes adhere to coding standard
[ ] Updated documentation

Thanks for this PR and the work. However, I do not think this is used much outside of internal things in skia. To reduce maintenance overhead, I want to keep the API at a minimum. If this is ever needed in SkiaSharp or provides some significant benefit we can reopen.


Add a /verify route for JWT token verification

Create a /verify route that verifies the provided JWT token and returns an appropriate response indicating if the token is valid or expired.
Reference:

JWT Authentication in Express

Assign

🫡


Add documentation for CodeBlock to describe className prop

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
Looking through the source for the codeBlock I see that it's possible to add classes to the codeBlock.
This is useful as we'd like to add line numbering to our code blocks, but would also like the ability to selectively enable or disable it.
Ideally line numbering should be a top-level feature fo the CodeBlock, but as it is not currently we can do this with some fairly simple css:
/* Reset line numbers for each new code block */
.prism-code {
    counter-reset: line-number;
}

:not(
.theme-code-block:not(.no-line-numbers) .prism-code.language-js .token-line::before,
.theme-code-block:not(.no-line-numbers) .prism-code.language-mustache .token-line::before,
.theme-code-block:not(.no-line-numbers) .prism-code.language-html .token-line::before,
.theme-code-block:not(.no-line-numbers) .prism-code.language-php .token-line::before,
.theme-code-block.force-line-numbers .prism-code .token-line::before {
  counter-increment: line-number;
  content: counter(line-number);
  margin-right: calc(var(--ifm-pre-padding) * 1.5);
  text-align: right;
  min-width: 2.5rem;
  display: inline-block;
  opacity: .3;
  position: sticky;
  left: var(--ifm-pre-padding);
}

This then allows me to have a code block:
``` title="Forcibly add line numbers" className=force-line-numbers
Unidentified language with line numbers forced
```

And
```js title="Prevent line numbers from a language which has them ordinarily" className=no-line-numbers
No line numbers here
```

I'm happy to help document this if you feel it's worthwhile having.
Self-service

[X] I'd be willing to address this documentation request myself.

It's a bit tricky, because for title="...", we parse this ourselves, so those quotes don't get into the final props; but MDX doesn't remove the quotes, so className="no-line-numbers" would become class="language-js \"no-line-numbers\"". I'm a bit afraid that it would only be confusing for others, since we actually never offered this API in the first place.
We would make line numbers opt-in in #7007, FYI

Hi Josh,
That makes sense. I had noticed that the quotes were included in the generated class name.
I'd suggest that #7007 also provides a way to make line numbers enabled-by-default (at least for certain langauges) and opt-out in those cases too, but that may be better as a separate PR.
Thanks

Thanks for understanding. For default-true line numbering, I'm not very much in favor of adding another theme config option, but we can certainly talk about that after #7007


Redefining find_package breaks vcpkg (because it does the same thing)

Howdy!
This is not a fully tested patch yet because I wanted to start the conversation before taking much more time on it.
Currently the eCAL build redefines find_package as a macro which then breaks if you try and build using vcpkg. This is due to the fact that vcpkg is also redefining the common cmake functions for finding dependencies and adding targets.
My proposed solution was to just rename the eCAL internal macro to ecal_find_package, which as you can see here, ends up touching a lot of build scripts.
Ultimately I'd like to see eCAL get added to vcpkg and I figure this would be the first step.

Hi @photex,
thanks for opening this issue. It'd be nice to have eCAL provided by vcpkg :smile:
I guess it's ok to provide a macro in ordner not to mess with the original find_package command, however we need to make sure to define it as a regular find_package in eCALConfig.cmake.in
macro(ecal_find_package)
    find_package(${ARGV})
endmacro()

Such that all samples can still be build against a regular eCAL installation .

Just so I understand, I should add this macro to this file? I didn't modify the file as part of this PR so far.

Yes, exactly. The idea is, that the examples can be build as part of the eCAL build. But also they should be able to build if someone has an eCAL installation on their PC (or eCAL package provided by vcpkg, conan or put your favorite package manager here) and they copy one of the samples as a starting point.
Since the samples also use ecal_find_package the command also has to be known.
However I just realize that this does not make sense, as ecal_find_package(eCAL) has to be known before finding eCAL, so it makes no sense to define it in eCALConfig.cmake.
I will think about it.

We definitely don't need to consider ecal_find_package to be an absolute solution either. I'm willing to take another approach too.
If you have other ideas I'd be happy to try them out.

@photex I will close this outdated PR for now. Kerstin will return soon and we can try to solve this vcpkg issue beginning 2021.


Simplify dockerCmd

Looking back at #14603, there is still something that felt weird : we are using dockerCmd 99% of the time like this :
out, _ := dockerCmd(c, "ps")

The reason is the following : we don't really care about the error code in that case, because how it's written it will always be 0 if the method passes. If we look at https://github.com/docker/docker/blob/master/integration-cli/utils.go#L60 the error code will not be 0 if there is an error — and if there is a error, the assert is KO and the test will fail. 🐧
I might miss something, and in that case feel free to close this one :wink:.
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

I don't even know why or when was dockerCmd introduced, but I would like to revisit all those functions including runCommand*.
Facts:

we almost never need an exit status, out and err are enough.
we almost never make the distinction between stdout and stderr, so out is sufficient for output.

out, err := runCmd(...) and out := dockerCmd(...). All the other cases should use exec.Command
What do you guys think? @vdemeester do you agree? Ping @LK4D4 @unclejack

Either way, I like this PR so +1 to this, if nobody agrees with what i said above.

The utilities from integration-cli were meant to be sort of a standard library for the integration-cli tests which helps avoid extreme duplication of the code. Some of those utility functions were rewritten a few times before the first version of integration-cli was sent as a PR and checked into the code.
Changing the code to make it work the way it needs to work today makes sense and this has already been done a few times. However, we need to make sure we do so safely and that we don't remove too much of the integration-cli library of utility functions in order to avoid code duplication for future tests.
We should really test these utility functions to make sure that they do what they were meant to do. Trivial changes might turn out to break things and we've already got problems with integration-cli tests failing sometimes.
Instead of merging this right away, I'd strongly suggest that we add tests for the integration-cli utility functions first. To be more specific, here are the kinds of tests we should have:

tests to ensure error handling works as expected
tests to check that the functions do what they're meant to do
test the functions with the testing framework to ensure that they behave the way we assume they behave in the context of integration-cli

Overall, I agree with doing this, just not before we add proper tests for to the integration-cli utility functions themselves.

tests of the test tools - I love it! :-)  +1

There is no rush on that, so yeah I think we can do better than just the PR as is :blush:.
@tiborvass I agree for the most part. There is a few tests where we actually test out the exitCode, like here so we might want to be able to get it somehow (or process the error return to get the exitCode). That's the same with stdout/stderr, there is a few edge case when we want them separate.
@unclejack @duglin I like the idea of testing the test utility function — I'll take a look at that :wink:.

It would be nice if dockerCmd used dockerCmdWithError (assuming that's the right func) but then just ignored the exit code. Then we have one central func to invoke docker but do different things with the results.  Avoids code dup and fragmentation.

@vdemeester @duglin i find it simpler that for edgecases we just use the plain old exec.Command that works perfectly well but maybe it's just me.

Sorry @vdemeester, needs a rebase

@abronan I know :blush:. I'm hesitant to do it right now because, with the discussion we had, this change is not the first we should do. There is consolidation to do one the integration-cli tests:

consolidate the integration-cli tests utils (tests),
then refactoring to ease the use even more when we are confident we don't break

I'm wondering out to proceed too : leave this open (but not mergeable) to have something that says "there is some work on this", or close it, write an issue to list the work to be done and close this one.
In the end it's pretty sure there is other PRs that will be needed before this one should be merge so it will end up being closed and carried or rewrote :blush:. WDYT ? :sweat_smile:

I think it would suffice to go ahead and cleanup the usage of dockerCmd since the status code is not needed at all, and dockerCmdWithError.
I don't think we really need dockerCmdWithError since it is less flexible than exec.Command and provides no real utility over it.

I've rebased it against master so it's mergeable.
To consolidate a bit the integration-cli tests, here is what I propose (and willing to work on :wink:) :

Move utils (utils.go and docker_utils.go) to a package. That way we can test it and export only what we want to be used in the integration-cli. This would mean using DockerCmd, BuildImage, etc... The unit test of the integration-cli/utils package would be run just before test-integration-cli.
Add tests to all exported function (RunCommandWithOutput, etc..).
Simplify the number of function used and their signatures : We either want the command to be successful and get the output, or the command to not be successful and get everything from it (output, error, exitcode, …).
Add some Checker to make even more used of the check library. And over time, using more c.Assert for the most common case (like !=, …).

This work would be separate in several pull-requests in order. So for this PR we could either merged it as is (makeing dockerCmd simple) or close it and these changes would take place in an other PR (or do all the thing in this PR but it feels like a lot of changes :sweat_smile:).
@cpuguy83 @tiborvass @duglin @unclejack WDYT ?

@vdemeester Moving the integration-cli utils to a package is a bad idea because the integration-cli code has to be changed throughout the code base and that breaks a lot of PRs.
Is there a problem with having the unit tests for integration-cli in the same places and running those first?
Either way, we should add tests first before refactoring anything. Simple and seemingly innocuous changes have caused troubles in the past. integration-cli is the last place where I'd start making changes throughout the code base without having tests first.

Is there a problem with having the unit tests for integration-cli in the same places and running those first?

I'm investigating to make it as smooth as possible but, to run unit-tests on integration-cli :
$ DOCKER_BINARY="../bundles/latest/binary/docker" go test docker_test_vars.go utils_test.go utils.go
INFO: Testing against a local daemon
--- FAIL: TestRunCommandWithOutput (0.00s)
        utils_test.go:15: hola
FAIL
FAIL    command-line-arguments  0.008s

$ DOCKER_BINARY="../bundles/latest/binary/docker" go test docker_test_vars.go utils_test.go utils.go
ok      command-line-arguments  0.012s

If we don't specify the *.go files, this will try to pick up the integration one. docker_test_vars.go is there for the dockerBinary variable. It's not that bad either but I though it would be easier to set-up a package just for theses.

Moving the integration-cli utils to a package is a bad idea because the integration-cli code has to be changed throughout the code base and that breaks a lot of PRs.

Yeah, that's true. I'll go with the above solution for now and we'll see later (at least we will have unit-tests). I'll work on the unit-tests first, probably making a PR just for that, and then we'll be back on this one. @unclejack sounds good ? :wink:

@duglin @tiborvass @unclejack I started to work on this here : https://github.com/docker/docker/compare/master...vdemeester:integration-cli-utils-tests.
It's gonna be a little bit more tricky to test docker_utils.go as it depends on the docker command (and a docker engine to run). I'll try to mock the docker binary somehow to test these.

@vdemeester Sounds good, the docker binary mocking as well.

@vdemeester sorry needs a rebase :S

Lol a conflict on almost every files :sweat_smile:.. some heavy changes going on in integration-cli :smile_cat:.

@vdemeester So should we close this one? :-(

@icecrime you're right, I'm gonna close it for now, and I'll re-open a new one when dockerCmd is covered :wink:


FAST vocabulary type ahead lookup in H2 should work

Currently this box in H2 behaves as a free text entry box. No type ahead search results appear when you type in the box.
App 176307 output: W, [2024-07-22T09:40:55.455746 #176307]  WARN -- : [f24fa9fe-2590-42b5-ae17-5047e08d6a50] Autocomplete results for river returned 404

It might be helpful to see if this service is now available at a supported REST endpoint:
https://www.oclc.org/developer/api/oclc-apis/fast-api/assign-fast.en.html

It seems like OCLC's FAST user interface is now sending Solr requests like this:
http://fast.oclc.org/cgi-bin/perlProxy.pl?http://authfastdb-m1.prod.oclc.org/fastapps-db/fastIndex/select?q=keywords:(village)&rows=10&start=0&version=2.2&indent=on&fl=id,fullphrase,type,usage,status&sort=usage desc

From OCLC FAST Team:
I believe our service is working okay but perhaps you are using an  ‘experimental.worldcat.org’ url? We recently discontinued that avenue in favor of https://fast.oclc.org/searchfast/fastsuggest?&query=stuff. It should function the same, but if you run into any difficulties, please let us know.
Hope this helps,
Russell
--
Russell Schelby
OCLC, Technical Manager, Authorities
<EMAIL_ADDRESS>

@amyehodge We are using http://fast.oclc.org/fastIndex/select

https://fast.oclc.org/searchfast/fastsuggest?&query=stuff doesn't help because it doesn't include any identifiers.

@justinlittman I've sent another message to the FAST team about this.

From the docs it looks like you can request that idroot be returned? Are those the identifiers that we have been using previously? The IDs look like fst01140419. Here's an example API call:
http://fast.oclc.org/searchfast/fastsuggest?&query=hog&queryIndex=suggestall&queryReturn=suggestall%2Cidroot%2Cauth%2Ctag%2Ctype%2Craw%2Cbreaker%2Cindicator&suggest=autoSubject&rows=3

@arcadiafalcone Can you answers @edsu 's question above about the identifiers? Thanks!

@edsu The identifiers used for what purpose? For the descriptive metadata, we're using the full URI, which can be derived from the idroot, such as https://id.worldcat.org/fast/1140419/ for the above example, but I may be misunderstanding the question.

Thanks @arcadia. I'm just confirming that we could switch H2 over from using
http://fast.oclc.org/fastIndex/select
(which is gone) to:
http://fast.oclc.org/searchfast/fastsuggest
As long as we request that it return identifiers (idroot). We were initially concerned that the new service didn't seem to be returning identifiers.

Given that we had to wait for an H2 user to notice that this was broken I wonder if this is an opportunity to move the unit test over to querying the live service instead of mocking it out?

I could understand OKComputer to make sure the URL still is 200 OK. Do we use OK Computer tests to ensure that the response format is still what we expect it to be?

@edsu @justinlittman Instead of hitting the live API in the test suite, or hammering it as part of OKComputer checks, how about we send Honeybadger alerts when the endpoint returns non-200 results? I'm going to work up a PR for that in the meantime.

worksforme


test

closing. was just testing issue creation from command line. this issue was created with
git issue create -m 'test' -l 'bug'


Documentation: Incorrect "operationData"

See:
https://www.google.com/url?hl=en&q=https://github.com/lime-company/powerauth-webflow/wiki/Next-Step-Server-REST-API-Reference%23create-an-operation&source=gmail&ust=1509028109742000&usg=AFQjCNG50N3N9EXoyUXCrCj1VxbdSc6qyQ
The type of operationData is String. In our example, the string is accidentally a JSON string. Documentation is missing the surrounding quotes.

I fixed the documentation for operationData.


operators [N] [CI] silicom-sts-operator (0.0.1)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible

@rmr-silicom can you fix firnating of main page? See your csvin https://operatorhub.io/preview

@rmr-silicom any updates?

@rmr-silicom anything we can help with here?


Dep update aurelia-rc1

updated dependencies to aurelia rc1
updated build tasks and build to aurelia rc1
updated install instrcutions

This change is

@jeremyvergnas please review. it'll be good to have people use/test it before relase

Cooooohooooool. We'll check this out later.


Add a test for the fix in #65.

Thanks, looks good!

@ionelmc any idea why this fails now on Pypy: https://travis-ci.org/schlamar/pytest-cov/builds/72790010


CLOUD-79860 added ambari database to cluster response

@keyki

Can i ask who uses the endpoint, and is password in response mandatory?

What password are you talking about ? :)

Forget it please :D


error when using child routes in a plugin

Version
3.0.2
Reproduction link
https://codesandbox.io/s/l2zkww865q
Steps to reproduce
Open the codesandbox, open the console and click on the page1 link
What is expected?
page1 route and child route working
What is actually happening?
freezes and shows:
[Vue warn]: Error in nextTick: "RangeError: Maximum call stack size exceeded"`
In the console

I'm making a plugin for internal use that will always need vue-router with some default routes. When I tried to use child routes, I encountered the error.
If you open the vue inspector you'll see that it keeps creating new child routes inside the child routes itself repeatedly.

Ahh thanks. I've added the render function to main.js, but I still get the same error. I've created a forum post for it instead 🙂
https://forum.vuejs.org/t/error-when-using-child-routes-in-a-plugin/52194


Support replace kubeconfig for istiod

This is to support scenario that istiod on cluster 1 will mange cluster 2 directly. In this case, we can point istiod's KUBECONFIG to cluster2.
Proposed steps:

create cm from cluster 2's kubeconfig  in cluster 1
mount this cm into istiod pod in cluster 1
add logic to use this as kubeconfig if the mount path specified in step 2 exists

@linsun @howardjohn  any comments for this approach?

Seems reasonable to me.  @howardjohn @costinm thoughts?
Background: this is an attempt to simplify https://github.com/istio/istio/pull/24503 as we don't want istiod to listen to any workloads or istio resources on cluster 1.

you should make it a secret
you should not require any code changes to do this, it's already configurable via the operator API I think

But yes sgtm


Write tickets for discrepancies in Metadata. Find where to write the tickets to

Done - repo is https://github.com/HumanCellAtlas/ingest-central/


Version 3.0.0-alpha.11

Landed in https://github.com/metarhia/impress/commit/c5341346e0fe8f1ac7c8f5edd121cb211db8d302


[Bug Report] Pagination current-change bug

Element UI version
2.3.7
OS/Browsers version
windows 10
Vue version
2.5.17-beta.0
Reproduction Link
https://jsfiddle.net/mmx38qxw/1880/
Steps to reproduce
At first if  you change the select component to trigger filterQuery function,the current-page will be the correct  number '1',and you click the Pagination Component like 2 or 3 or any nubmer which is not the no.1,and next you change the select component,you will find that the current page wasn't the No.1 that you expected.And you click the highlight page no,the callback function can't be triggered。It means that the current page was the no you clicked last time before you changed the select componet.
What is Expected?
The 'current page' will be the correct number
What is actually happening?
The 'current page' was not the correct number

try:current-page.sync
https://jsfiddle.net/ST_Lighter/mmx38qxw/1881/

You need .sync indeed, otherwise this.curPage will stay 1 as you click the pagers.

@STLighter Yeah,It will works at some simple demo,but in my real project,I need to register a user-defined component like this https://jsfiddle.net/mmx38qxw/1883/ ，and the .sync will not works. And if I add the .sync to the Pagination component which was imported by me,the error will be occured.

@STLighter @Leopoldthecoder In fact.before the version 2.3.0 Diamond,The bug of current-change has exist for a long time,I guess the bug's was like this:users set the current-page by hand,the current-change callback method will be emited.Thougth it was a bug ,I can compare the old value of current-page width the new value to avoid this question.But now,I have no idea to solve this.Could you help me?Thank you very much.如果没办法，我就只能去饿了么公司当面请教两位了

https://jsfiddle.net/ST_Lighter/mmx38qxw/1884/
$emit an update event in handleChangePage to make .asyc work.
see Vue docs for more https://vuejs.org/v2/guide/components-custom-events.html#sync-Modifier

@STLighter thank you very much !I did not kown Vue support $emit an update event,Thank you for your time !


Which environment to use for development as an ISV ?? bcsandbox or OnPrem sandbox ??

Thank you for your request. We are currently setting up the process around handling of issues in this new GitHub repository and you should hence expect a short delay in the processing of this request. But we will be on your case shortly!

To get help for general questions please use one of the following resources:
Business Central Community
mibuso forum
Dynamics User Group


Add knownIssues and lastModified fields for v3, v4 and v4 package schemas

Jira : DCOS-58438

lgtm from a code perspective


Any way to cache response after processing with callback?

I have a slow function I'd like to apply to the response content, then cache the (smaller, compressed) result of this function. Is there a way to  cache callback results, in particular using the memory backend, or any place I might patch to make this possible?

The simplest way to accomplish this may be to just provide a method to manually cache a response, so you can so something like:
session = CachedSession()
with session.cache_disabled():
        response = session.get('http://httpbin.org/ip')
response = postprocess(response)
session.cache_response(response)

Similar to #82 . Do you think that would do what you want?

Changes for this are now in master (and in pre-release build 0.7.0.dev255). You can use CachedSession.cache.save_response(response) to manually save a response object.


Pre-trained LiteFlowNet model

Thanks for your wonderful work!
As stated in training strategy: A LiteFlowNet [14] pre-trained on the FlyingChairs [9] dataset is used as the overpowered teacher in the leakage distillation, can u release the pre-trained LiteFlowNet model? I can only find the model (released in LiteFlowNet) trained on FlayingChairs+FlayingThings.

Hello, I used the default model from https://github.com/sniklaus/pytorch-liteflownet.
I reviewed the description again, and it seems that this model is trained under FlayingChairs+FlayingThings. This is my mistake, and I will change this description in a future version of the paper.


Feature: Add Testing label to repo

Is your feature request related to a problem? Please describe.
There's no testing label for checking general parts of product.
Describe the solution you'd like
Add testing label in GitHub, with description This needs to be tested.
Describe alternatives you've considered
Additional context

Tested manually


Not rebuild when dependence files of route and middleware are change.

Changing src/app/route.ts -> Rebuild works
Changing src/my-data/image-data.ts -> Rebuild not works (imported by src/app/route.ts)

Dear Team,
We have identified an issue related to the TypeScript project, specifically with regards to the automatic rebuilding process when there are changes in the dependency files of routes and middleware.
Issue:
Currently, when we make changes to src/app/route.ts, the rebuild process works as expected. However, when changes are made to src/my-data/image-data.ts (which is imported by src/app/route.ts), the rebuild process does not trigger.
Solution:
To address this issue, I have made a modification to the watcher files. Previously, we were using the "File System Watch" library by importing {watch} from 'fs'. I have now switched to using the esbuild context for better functionality.
By implementing this change, we anticipate that the rebuild process will now work correctly when there are changes in both route and middleware dependency files.
Please let me know if you have any further questions or concerns.
Renato Rodrigues


Retrieve bias metrics from thanos querier (#1472) (#1473)

cherry-pick fix for issue #1472 from f/mserving-metrics to incubation branch.

Description

How Has This Been Tested?

Test Impact

Request review criteria:

Self checklist (all need to be checked):

[ ] The developer has manually tested the changes and verified that the changes work
[ ] The commits have meaningful messages (squashes happen on merge by the bot).
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@alexcreasy why don't you merge f/mserving over the incubation branch?
We are trying to avoid as many cherry-picking as possible, as it's fairly hard to keep track later.


Java Runner remains in Infinite Execution Mode

Describe the bug

First it Complains about Reflections for non JAVA Files
03-05-2022 17:59:37.715 [java] [ERROR] [ForkJoinPool.commonPool-worker-4] WARN org.reflections.Reflections - could not create Dir using com.thoughtworks.gauge.scan.ClasspathScanner$1@2fadf5f1 from url file:/D:/git/iec-aw/tc-soa-client/soa_libs/README.MD. skipping.
03-05-2022 17:59:37.715 [java] [ERROR] java.util.zip.ZipException: error in opening zip file
03-05-2022 17:59:37.715 [java] [ERROR] 	at java.util.zip.ZipFile.open(Native Method)
03-05-2022 17:59:37.715 [java] [ERROR] 	at java.util.zip.ZipFile.(ZipFile.java:230)
03-05-2022 17:59:37.715 [java] [ERROR] 	at java.util.zip.ZipFile.(ZipFile.java:160)
03-05-2022 17:59:37.715 [java] [ERROR] 	at java.util.jar.JarFile.(JarFile.java:166)
03-05-2022 17:59:37.715 [java] [ERROR] 	at java.util.jar.JarFile.(JarFile.java:130)
03-05-2022 17:59:37.715 [java] [ERROR] 	at com.thoughtworks.gauge.scan.ClasspathScanner$1.createDir(ClasspathScanner.java:48)
03-05-2022 17:59:37.715 [java] [ERROR] 	at org.reflections.vfs.Vfs.fromURL(Vfs.java:103)
03-05-2022 17:59:37.715 [java] [ERROR] 	at org.reflections.vfs.Vfs.fromURL(Vfs.java:95)
03-05-2022 17:59:37.715 [java] [ERROR] 	at org.reflections.Reflections.lambda$scan$2(Reflections.java:176)
03-05-2022 17:59:37.716 [java] [ERROR] 	at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
03-05-2022 17:59:37.716 [java] [ERROR] 	at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1556)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.concurrent.ForkJoinPool$WorkQueue.execLocalTasks(ForkJoinPool.java:1040)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1058)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
03-05-2022 17:59:37.718 [java] [ERROR] 	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
03-05-2022 17:59:37.718 [java] [ERROR] [ForkJoinPool.commonPool-worker-4] WARN org.reflections.Reflections - could not create Vfs.Dir from url. ignoring the exception and continuing
03-05-2022 17:59:37.718 [java] [ERROR] org.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [file:/D:/git/iec-aw/tc-soa-client/soa_libs/README.MD]
03-05-2022 17:59:37.718 [java] [ERROR] either use fromURL(final URL url, final List urlTypes) or use the static setDefaultURLTypes(final List urlTypes) or addDefaultURLTypes(UrlType urlType) with your specialized UrlType.

afterwards remain Blocked at the Scanning Packages:

03-05-2022 17:59:38.539 [java] [DEBUG] gauge-java took 1928milliseconds to load and scan. This should be less than 'runner_connection_timeout' config value.
03-05-2022 17:59:38.539 [java] [DEBUG] run 'gauge config runner_connection_timeout' and verify that it is < 1928
03-05-2022 17:59:38.539 [java] [DEBUG] starting gRPC server...
03-05-2022 17:59:38.578 [java] [ERROR] [pool-1-thread-1] INFO org.reflections.Reflections - Reflections took 1563 ms to scan 360 urls, producing 10428 keys and 53158 values
03-05-2022 17:59:39.360 [java] [DEBUG] started gRPC server on port 52408
03-05-2022 17:59:39.361 [Gauge] [DEBUG] Attempting to connect to grpc server at port: 52408
03-05-2022 17:59:39.477 [Gauge] [DEBUG] Successfully made the connection with runner with port: 52408
03-05-2022 17:59:39.477 [Gauge] [DEBUG] Validation started.
03-05-2022 17:59:39.798 [java] [DEBUG] Scanning packages for steps

It was caused by some dependencies having a Higher Java Bytecode Version than the JRE used by Gauge-Java.
A better error message when such classes are encountered would help a long way


bugfix object clone() method

should precede setting className
#139

Current coverage is 78.70%

Merging #140 into master will decrease coverage by -0.14% as of deb08e3

@@            master   #140   diff @@
=====================================
  Files           37     37
  Stmts         2832   2832
  Branches       682    682
  Methods          0      0
=====================================
- Hit           2233   2229     -4
- Partial        192    193     +1
- Missed         407    410     +3

Review entire Coverage Diff as of deb08e3

Powered by Codecov. Updated on successful CI builds.

Good catch. In cases where the parent constructor is not setting the class name, setting attributes will end up placing them in a throwaway container.


wrap the text around the image

Describe the bug
Wrap the text around the image in the home page sections ("About HackClub" and "HackClub RAIT) in responsive view.
Expected behavior
Responsiveness and Enhanced UI
Screenshots

Are you participating under any open-source program?
Hacktoberfest

@shreyamedehal Assigning this issue to you . Happy Coding !

I want to work on this issue under JWOC


Placeholder for adding geo-based rules to the PII Enrichment strategy

Because that geo-based information is easily fetched from the geo-IP enrichment.

Use case: apply anonymization or pseudonymization (or other GDPR features) only to users who are based in the EU.
I’m thinking something along the lines of if the visitor is in one of the 28 member states then apply certain rules.

IANAL but the way I understood the regulation, the protection is extended to the data subject even if only part of the tracked activity is in the EU.

Not sure if this is a good place to put this, but it would also be nice to do scrubbing/hashing of some of the elements of the Geo-IP enrichment using the PII enrichment (like dropping latitude/longitude, zip code, etc.)

Yes, please!


updates to option plotting script

changes PickPlace1D to Cover (because it's not 1D)
removes oracle and action policy from plots

yeah I am running them with num train tasks = 1000 only, and they won't appear in these plots


feat: support no_std for alloy-eips

And remove unused error Custom

though about the error type. I'm skeptical that this even belongs in there if it's only used in the consensus crate

not opposed to removing it, the purpose of it is to allow for non-RLP encoding schemes in EIP-2718 in non-Ethereum networks. E.g. if Optimism decides to have a fallible SSZ encoding for some transaction type, the existing API can still capture that behavior via the Custom error

cleaning up CI before merge 👍

nightly clippy strikes again
https://github.com/rust-lang/rust/issues/121708

ty for you contribution @yjhmelody, sorry for leaving it open so long 🙇♀


Milestone 2.0 Summary

Open tickets: https://github.com/filamentgroup/grunticon/milestones/2.0
We've hatched a plan to add support for inline SVG without modifying anything in the Grunticon workflow aside from a small client-side JavaScript addition. Basically, we will be able to extract the SVG icons from the CSS we already request in qualified browsers, so when desirable, we can inject SVG icons directly into the page either through embedded SVG markup or possibly the use and defs elements (which could be better for performance but come with limitations as well).
The ability to use either of those inline SVG approaches will dramatically change what we're able to do with Grunticon, such as applying scripting and CSS to icons in bulk or individually. Animating and styling portions of an icon become quite simple. And best of all, the approach will build upon our existing fallback system to guarantee all browsers get an icon.
To implement this feature, we are thinking it makes sense to improve Grunticon's loader JS by exposing a small API. The existing loader script won't need to change much in file size, but exposing some small things like a callback when the SVG CSS file finishes loading will allow us to tie in optional extensions that parse that CSS and inject it into desired locations in the page (elements that have data-grunticon-embed attributes, or example.
Milestone features include:

Inline SVG Support (for styling, animating and scripting icons)
Improved modular loader script with extensions
Test suite for loader script
Improvements to re-coloring feature: https://github.com/filamentgroup/directory-colorfy/issues/10

Launched.


preupgrade failed on DNF requirement

Describe the bug
In the preupgrade the conversion failed on dependency during the Imunify360 installation.
2024-10-09 21:37:00,491 - ERROR - Command ['/usr/bin/leapp', 'preupgrade'] failed with return code 1
2024-10-09 21:37:00,492 - ERROR - Failed: doing the conversion. The reason: Command '['/usr/bin/leapp', 'preupgrade']' returned non-zero exit status 1.
2024-10-09 21:37:00,620 - DEBUG - Going to write json '/usr/local/psa/var/cloudlinux7to8/actions.json' with new data
2024-10-09 21:37:00,625 - DEBUG - Error report: [cloudlinux7to8] (dist-upgrader 8a71a4b240bcb06c170e11261da0893691db3dd6, upgrader module Plesk::CloudLinux7to8Upgrader 09cd157eb03577666e2a0bbe9b784615de8cebf9) process has failed. Error:
Failed: doing the conversion. The reason: Command '['/usr/bin/leapp', 'preupgrade']' returned non-zero exit status 1.

2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.11-2.el8.x86_64 from alma-imunify360-testing requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.11-1.el8.x86_64 from alma-imunify360-testing requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.30.0-2.el8.x86_64 from alma-imunify360-rollout-1-bypass requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.28.2-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.28.0-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.27.2-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.27.1-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.26.2-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.25.5-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.25.4-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,276 - INFO - - package imunify360-webshield-bundle-1.25.3-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.25.2-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.25.1-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.25.0-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.7-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.6-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.5-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.4-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.3-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.2-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.23.1-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.22.2-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.22.1-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.22.0-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.20.124-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.20.121-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.20.120-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.20.119-17.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.20.119-16.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,277 - INFO - - package imunify360-webshield-bundle-1.20.119-14.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.20.119-13.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.19-6.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.19-3.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.19-10.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.18-7.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.18-6.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.18-5.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.18-4.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.18-11.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.17-5.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.17-4.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.16-7.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.16-4.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.15-8.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.14-18.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.14-15.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.13-3.8.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,278 - INFO - - package imunify360-webshield-bundle-1.13-3.4.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,279 - INFO - - package imunify360-webshield-bundle-1.13-3.3.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,279 - INFO - - package imunify360-webshield-bundle-1.13-3.11.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,279 - INFO - - package imunify360-webshield-bundle-1.13-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,279 - INFO - - package imunify360-webshield-bundle-1.12-8.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,279 - INFO - - package imunify360-webshield-bundle-1.12-5.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package imunify360-webshield-bundle-1.12-5.1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package imunify360-webshield-bundle-1.12-15.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package imunify360-webshield-bundle-1.12-12.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package imunify360-webshield-bundle-1.11-4.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package imunify360-webshield-bundle-1.11-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package imunify360-webshield-bundle-1.11-1.el8.x86_64 from cloudlinux8-imunify360 requires alt-curl, but none of the providers can be installed
2024-10-09 21:37:00,461 - INFO - - package alt-curl-7.64.0-2.el8.x86_64 from cloudlinux-x86_64-server-8 requires alt-libcurl = 7.64.0-2.el8, but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-curl-7.64.0-2.el8.x86_64 from cloudlinux8-imunify360 requires alt-libcurl = 7.64.0-2.el8, but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-curl-7.64.0-2.el8.x86_64 from cloudlinux8-appstream requires alt-libcurl = 7.64.0-2.el8, but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-curl-7.64.0-2.el8.x86_64 from alma-imunify360 requires alt-libcurl = 7.64.0-2.el8, but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-libcurl-7.64.0-2.el8.x86_64 from cloudlinux-x86_64-server-8 requires libssh2(x86-64), but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-libcurl-7.64.0-2.el8.x86_64 from cloudlinux8-imunify360 requires libssh2(x86-64), but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-libcurl-7.64.0-2.el8.x86_64 from cloudlinux8-appstream requires libssh2(x86-64), but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - package alt-libcurl-7.64.0-2.el8.x86_64 from alma-imunify360 requires libssh2(x86-64), but none of the providers can be installed
2024-10-09 21:37:00,462 - INFO - - imunify360-webshield-bundle-1.28.2-1.el7.x86_64 from @System  does not belong to a distupgrade repository
2024-10-09 21:37:00,462 - INFO - - alt-curl-7.64.0-1.el7.x86_64 from @System  does not belong to a distupgrade repository
2024-10-09 21:37:00,462 - INFO - - conflicting requests

Feedback archive
Please attach a feedback archive to the bug report.
cloudlinux7to8_feedback.zip

Update from our side; Issue is still there with the newest update off the CloudLinux 7 to 8 tool (1.0.3).

Created a case with Plesk support (id 95395954), hopefully this helps with fixing this issue since the developer seems to ignore this.

PAUX-6547

Alternatively, as a rather crude, but straightforward workaround, you can try to do: yum remove imunify360-webshield-bundle.

I ran into another issue after removing imunify360. I can setup a new machine based on cl7, but perhaps you can set it up yourself and test with cloudlinux, imunify360 and Plesk (since Plesk offers the entire bundle)?

I ran into another issue after removing imunify360.

There are no details, but that doesn't sound like a cloudlinux7to8 issue. In this case, please go through the usual Plesk (or Imunify) support channels. If I'm mistaken, feel free to provide details here or file another issue.

This issue is fixed in the new version v1.0.4.

I have justed test this and I can confirm the upgrade succeeds now. However, you do need to reinstall Imunify360. Not doing results in incorrect webserver configuration files.

I have justed test this and I can confirm the upgrade succeeds now. However, you do need to reinstall Imunify360. Not doing results in incorrect webserver configuration files.

This seems to be due missing dnf packages, we've fixed this by simple running an dnf install on 'imunify-ui-firewall-plesk' this installs all the dependencies for Plesk and fixes the /etc/httpd/conf.d/modsec2.imunify.conf config :).


Edited text for VM section

Summary of changes proposed in this pull request:

IMPORTANT: Make sure you are familiar with the Contributing guidance. Particularly, don't edit *.md files directly - make your changes in the source *.json files.

approved


DropDown Not Showing Values (Possible Regression)

Steps To Reproduce
On Evidence: 33.0.0
index.md
```sql test_query
select 1 as val
union
select 2 as val
union
select 3 as val
```

<Dropdown
    data={test_query}
    name=test
    value=val
    title='Test Dropdown'
/>

Environment

Node version (node -v): 20.11.1
npm version (npm -v): 10.2.4
OS: mac
Browser: Chrome
Database: Redshift

Expected Behavior
Previously DropDown's would show the values passed in with from the data and value parameters
Actual Behaviour
Component just shows "No results found."

Workarounds
Not that I have found

@mjbloch this should now be fixed!


nat64 - CI molecule troubleshot

As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running

Closing this - proposing another PR to fix the job.


Re-use client for OneDrive item downloads

Description
This PR reintroduces the changes from #2266 with a change to not reset the transport
when initializing the shared client.
Doing so was removing the retry and other middlewares
and also resulting in throttled requests being masked as success
Also - we now decorate our download traffic with an ISV tag as recommended here
Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[x] :clock1: Yes, but in a later PR
[ ] :no_entry: No

Type of change

[ ] :sunflower: Feature
[x] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Test
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

#2266

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[x] :green_heart: E2E

@ryanfkeepers - commit 2 in this PR has the changes from your previous PR #2266


[9.x] Fix  expected parameter is inconsistent with given parameter in MailManager

The transport created by EsmtpTransportFactory can only be an EsmtpTransport so the current types are correct.


updating docs readme.md and contributing.md

The README.md now points to our live docs and to CONTRIBUTING.md for details on chipping in.
Any feedback, @spencerkimball, @petermattis, @bdarnell? Might be good for someone to install Jekyll and test out building the docs locally.

This change is

LGTM

Nice. LGTM


Implement the DVRL approach

@Thomas-Galtier do you confirm we drop this one and focus on PVRL?

yep

Dropping it! cc @Thomas-Galtier @arthurPignet @RomainGoussault


ClickhouseStatementImpl.executeUpdate does not throw on server error

We have a specific use case where we send queries that construct temporaries that are used in subsequent queries. We have discovered that ClickhouseStatementImpl.executeWrite does not appear to throw correct in the face of malformed CTAS statements (or possibly other remote failures).
What we observe is that we see something akin to the following in our logs (I added a specific nonsense column)
14:57:04.487 [qtp90045638-50] ERROR c.c.j.i.ClickHouseStatementImpl - can not close stream: Code: 47, e.displayText() = DB::Exception: Missing columns: 'frobfrob' while processing query: ' ... ' (version <IP_ADDRESS>)
, server ClickHouseNode(addr=http:localhost:8123, db=default)@-713711043

Subsequently trying to reference the table is where we actually get the raised exception. This makes diagnosing the faulty queries challenging.
https://github.com/ClickHouse/clickhouse-jdbc/blob/master/clickhouse-jdbc/src/main/java/com/clickhouse/jdbc/internal/ClickHouseStatementImpl.java#L279
Inspecting the executeWrite this appears to be an attempt to swallow errors closing the connection fails for some reason, however it seems like other errors are bubbling out and being swallowed as well.

Hi @rzeigler, thanks for reporting the issue and sorry for the inconvenience caused at your end. Yes, the exception should not be swallowed. Let me check if there's similar cases and fix it on develop today.
I'll release patch5 on Sunday if there's no other issues.


update CLI section in release note

/assign @pwittrock

@pwittrock, please take a look. Thanks!

@pwittrock Regrouped and rewording some of them. PTAL and feel free to rewording them.

@ymqytw thank you! @pwittrock please, verify the content and we are done with this item.

/lgtm


Thread support

The computer is running pyspider works not loaded, 8 processors and 300 GB of RAM. I would like it to be loaded up to 70%. Now, with 80 projects, speed is rate 100 and burst 100, but loading a maximum of 5-7%. Can make supported streams, I saw there a tornado @run_on_executor support. This is especially needed when 10 million on local storage, which that require fast processing. I put 300 threads to queue, but it did not help. now count workers 100 and count fetchers 100.
http://codepad.org/3cwUMx1F
https://github.com/tornadoweb/tornado/wiki/Threading-and-concurrency

How do you deploy it?
How many processor running?
From the dashboard, the figure of each message queue
what do you mean by I put 300 threads to queue
Is database running on same machine?
Is message running on same machine?

pyspider running centOS last version and deploy from supervisor
fetcher: 54, processor: 169, result worker: 21.
{ ...
"queue-maxsize":100,
"fetcher":{
"poolsize":10000
},
"scheduler":{
"active-tasks":300,
"threads":10
}
Database is running on the current server.

??I put 300 threads to queue
This if scheduler["threads"] = 300.

How to configure pyspider so that I could do 100 requests per second.
What parameters to set, for setting up speed in the second through the web interface does not give results.

change queue-maxsize to larger number or 0
From the dashboard, the figure of each message queue, like this:

I stop all projects, except one.
change queue-maxsize:1000
code : http://demo.pyspider.org/debug/images_crawler
crawl time: 12 minutes
if crawl on the current server with code:
import requests
URLS = [...4997 urls...]
import datetime
results = {}
a =  datetime.datetime.utcnow()

def load_url(url, timeout):
    r = requests.get(url, timeout=timeout)
    if not results.get(r.status_code):
        results[r.status_code] = 1
    else:
        results[r.status_code] += 1

with concurrent.futures.ThreadPoolExecutor(max_workers=250) as executor:
    future_to_url = {executor.submit(load_url, url, 60): url for url in URLS}
    for future in concurrent.futures.as_completed(future_to_url):
        url = future_to_url[future]
        try:
            data = future.result()
        except:
            results[url] = 0

    b = datetime.datetime.utcnow()

    print str(b-a)
    print "Requests "+str(len(URLS))
    print results

then crawl time 2 minutes :(

What else can I try?
I'd like to work in pyspider

How could you stop projects, except one? If you changed the configuration, you need to restart the components to make it work.
the code you provide in http://demo.pyspider.org/debug/images_crawler, the images will only crawled every 10 days, @config(age=10 * 24 * 60 * 60) is applied and have higher priority then crawl_config.
queue status like the image above please.