Automated cherry pick of #9771: fix(region): avoid panic when register service not work

Cherry pick of #9771 on release/3.7.
#9771: fix(region): avoid panic when register service not work

Codecov Report

Merging #9772 (da35a63) into release/3.7 (56d583e) will increase coverage by 2.06%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9772       +/-   ##
===============================================
+ Coverage         6.00%   8.06%    +2.06%
===============================================
  Files              845     107      -738
  Lines           131245   12978   -118267
===============================================
- Hits              7879    1047     -6832
+ Misses          122665   11811   -110854
+ Partials           701     120      -581

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/host.go
0.77% <0.00%> (ø)

pkg/multicloud/esxi/image.go
0.00% <ø> (ø)

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/snapshot.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storage.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storagecache.go
0.00% <ø> (ø)

pkg/multicloud/esxi/template.go
0.00% <ø> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <ø> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/hostman/hostinfo/hostovn.go

... and 664 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b7901c2...da35a63. Read the comment docs.

Codecov Report

Merging #9772 (da35a63) into release/3.7 (56d583e) will increase coverage by 2.06%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9772       +/-   ##
===============================================
+ Coverage         6.00%   8.06%    +2.06%
===============================================
  Files              845     107      -738
  Lines           131245   12978   -118267
===============================================
- Hits              7879    1047     -6832
+ Misses          122665   11811   -110854
+ Partials           701     120      -581

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/host.go
0.77% <0.00%> (ø)

pkg/multicloud/esxi/image.go
0.00% <ø> (ø)

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/snapshot.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storage.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storagecache.go
0.00% <ø> (ø)

pkg/multicloud/esxi/template.go
0.00% <ø> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <ø> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/hostman/hostinfo/hostovn.go

... and 664 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b7901c2...da35a63. Read the comment docs.


fix: catch statSync error

Description
It seems we should catch the error here.
fixes #11904
refs #11436
refs https://github.com/vitejs/vite/pull/11436/files#r1094496131
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

@MoustaphaDev @Artur- I'm not sure if this fixes your errors. May I ask you to test this PR?

What is the error there? Is this not already the goal of throwIfNoEntry?

It's seems #11904 is failing with ENAMETOOLONG and astro one is failing with ERR_INVALID_ARG_VALUE.

Ok thanks. We need to revamp the resolution algorithm for v5. Having a lof of sys calls that result to errors can kill perf because node takes time to generate the stacktrace (not sure there is an optimisation for empty catch clause)

:+1: Solves ENAMETOOLONG for me


Timezone

Hi Dave,
Thanks for this script. It works better then the script I was looking for.
I noticed that the timing turns out different due to timezone differences.
I wonder if and where this could be solved.
At this moment, i could enter a date in the spreadsheet, for instance;
1/2/2016 10:00:00	1/2/2016 11:00:00
In the calender it will turn out to be 9 hours later, so;
1/2/2016 19:00:00	1/2/2016 20:00:00
The calender timezone has been set to my location (amsterdam)
Thanks again,
Richard

Sorry about that. I didn't do much testing of time zones. You probably need to set the time zone for the spreadsheet. Check in the File menu, Spreadsheet settings. If that fixes it, I'll add that to the instructions.

Hi Dave,
It actually did! Thanks for that.
This script is really helpfull!

Glad to hear it's useful. I added a step to the instructions to set the time zone for the spreadsheet.

Hi Dave, not sure if this will get through as the thread is closed and I can't work out how else to write to you.
I was using your script for sheets to calendar and it was great. Your instructions are better than any others out there and it pretty much worked first time. So all was good.
However in my sheets the data that I am using is a formula and I noticed that once the calendar was updated that the formula were all removed. Is that just how it is or is there a way to protect the formula so that it is there after the event.
The reason for this is that I have a large sheet from which the calendar information is drawn and kept on a separate sheet to the master data.
Thanks for your help in advance and I hope that you can help out with this.
Anastasis Kokkinos

Hi Dave,
apologies, it all works fine. I just did a test where I went calendar to spreadsheet and that wiped out the formulae which sort of makes sense. As long as we don't do this we are in business.
Thanks again.

Apologies again, however after using it yesterday quite a bit I found that after the sync that it does remove my formula from all cells in the sheet which is a problem. However I can work around it.
If it were possible for this not to happen that would make this 100% perfect, as it is it's pretty good for my purposes.
Thanks for this and hopefully it's an easy fix?

It might be possible to preserve the formulas while updating dates in the
spreadsheet. Unfortunately I won't be able to take a look at it until
Monday. I'll try to fix it then.
On Feb 13, 2016 1:02 PM, "Anastasis25"<EMAIL_ADDRESS>wrote:

Apologies again, however after using it yesterday quite a bit I found that
after the sync that it does remove my formula from all cells in the sheet
which is a problem. However I can work around it.
If it were possible for this not to happen that would make this 100%
perfect, as it is it's pretty good for my purposes.
Thanks for this and hopefully it's an easy fix?
—
Reply to this email directly or view it on GitHub
https://github.com/Davepar/gcalendarsync/issues/2#issuecomment-183754317
.

Dave,
Thanks for the quick response.
No rush as I’m just testing and sorting out what we need to do.
Regards
Anastasis Kokkinos
From: Dave Parsons<EMAIL_ADDRESS>Sent: 14 February 2016 08:09
To: Davepar/gcalendarsync
Cc: Anastasis25
Subject: Re: [gcalendarsync] Timezone (#2)
It might be possible to preserve the formulas while updating dates in the
spreadsheet. Unfortunately I won't be able to take a look at it until
Monday. I'll try to fix it then.
On Feb 13, 2016 1:02 PM, "Anastasis25"<EMAIL_ADDRESS>wrote:

Apologies again, however after using it yesterday quite a bit I found that
after the sync that it does remove my formula from all cells in the sheet
which is a problem. However I can work around it.
If it were possible for this not to happen that would make this 100%
perfect, as it is it's pretty good for my purposes.
Thanks for this and hopefully it's an easy fix?
—
Reply to this email directly or view it on GitHub
https://github.com/Davepar/gcalendarsync/issues/2#issuecomment-183754317
.

—
Reply to this email directly or view it on GitHub https://github.com/Davepar/gcalendarsync/issues/2#issuecomment-183754942 .Image removed by sender.


Fix size check for abstract namespaces in SockAddr::unix

Not sure whether passing abstract namespaces to unix() is totally supported, but there is the check below for whether to add another byte to sockaddr_len for the null terminator, which doesn't if the path starts with a null byte.

Alright, added a test.

Thanks @coolreader18.


Review and implement hook improvement

Note to self: perform additional review and merge if good to do so.

Suggestion is interesting but doesn't appear to work as intended or does not work as I expect it would.
When building with pyinstaller, the files for each operating system are still included.
Example, building my application as a single file executable results in a file that is identical to the old hook file.
Building a file that isn't a single file results in a directory that contains files for each operating system.
./linux64:
libtkdnd2.9.2.so  tkdnd_generic.tcl  tkdnd_unix.tcl
pkgIndex.tcl      tkdnd_macosx.tcl   tkdnd_utils.tcl
tkdnd_compat.tcl  tkdnd.tcl          tkdnd_windows.tcl

./osx64:
libtkdnd2.9.2.dylib  tkdnd_generic.tcl  tkdnd_unix.tcl
pkgIndex.tcl         tkdnd_macosx.tcl   tkdnd_utils.tcl
tkdnd_compat.tcl     tkdnd.tcl          tkdnd_windows.tcl

./win64:
libtkdnd2.9.2.dll  tkdnd_compat.tcl   tkdnd.tcl        tkdnd_windows.tcl
pkgIndex.tcl       tkdnd_generic.tcl  tkdnd_unix.tcl
tkdnd2.9.2.lib     tkdnd_macosx.tcl   tkdnd_utils.tcl

Either I'm not understanding something, looking over something, or additional review appears to be required.

I was wrong, the feature does seem to work, but pyinstaller caches some information somewhere which can cause it to behave unexpectedly.

Implemented in original fork. Closing.


Fix nbextension related CI build errors

/cc @HazalCiplak

Is there a GitHub issue for this?

This seem to have resolved the build error. Even jupyter-build is still working without modification (it might break in the future when upgrading the base image).
Running jupyter from a virtual environment still has issues.

I am tempted to remove dev-jupyter-start and dev-jupyter-configure. It also depends on .require-jupyter-vars which doesn't exist.
The purpose was of dev-jupyter-start was to run jupyter from the virtual environment rather than docker image.
Maybe with vscode that isn't necessary anymore.


Repo

Codecov Report

Merging #8 (2daa2b3) into main (25ebadd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   82.22%   82.22%
=======================================
  Files           3        3
  Lines          45       45
=======================================
  Hits           37       37
  Misses          8        8

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25ebadd...2daa2b3. Read the comment docs.


Migrate pypy

Required for https://github.com/conda-forge/lbenv-feedstock/pull/8

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Annotation format issues while training YOLOV++

Hello! I am trying to train the YOLOV++ model using a custom dataset. I am stuck on how the annotation format should look like. Here are some of the steps I have taken and more information about my progress:

I have already trained the base detector using COCO formatted json files and obtained the weights
I created new json files for my custom video dataset and converted them to OVIS using the convert_ovis_coco() from the ovis.py file
I created my train_seq.npy and val_seq.npy files
I am using the v++_SwinTiny_decoupleReg.py exp file and added the following lines:
self.data_dir = "/mnt/c/Users/p009325H/Documents/xod-data-COLOR-video/images"        self.train_ann = "ovis_train.json"        self.val_ann = "ovis_validation.json"
I also added the get_data_loader() code as well to the very end of the file
I then run the training using the following command: python tools/vid_train.py -f exps/yolov++/v++_SwinTiny_decoupleReg.py -c YOLOX_outputs/swin_tiny_vid/best_ckpt.pth --fp16 -b 2

After running, epoch1 starts and after the iterations finish, it crashes with the following error:
xml.parsers.expat.ExpatError: Caught ExpatError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/sharanyap21/miniconda3/envs/yolov/lib/python3.7/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
data = fetcher.fetch(index)
File "/home/sharanyap21/miniconda3/envs/yolov/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 58, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/sharanyap21/miniconda3/envs/yolov/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 58, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/sharanyap21/YOLOV/yolox/data/datasets/vid.py", line 246, in getitem
img, target, img_info, path = self.pull_item(path)
File "/home/sharanyap21/YOLOV/yolox/data/datasets/vid.py", line 231, in pull_item
annos = self.get_annotation(path, self.img_size)[0]
File "/home/sharanyap21/YOLOV/yolox/data/datasets/vid.py", line 182, in get_annotation
file = minidom.parse(xmls)
File "/home/sharanyap21/miniconda3/envs/yolov/lib/python3.7/xml/dom/minidom.py", line 1958, in parse
return expatbuilder.parse(file)
File "/home/sharanyap21/miniconda3/envs/yolov/lib/python3.7/xml/dom/expatbuilder.py", line 911, in parse
result = builder.parseFile(fp)
File "/home/sharanyap21/miniconda3/envs/yolov/lib/python3.7/xml/dom/expatbuilder.py", line 207, in parseFile
parser.Parse(buffer, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 0
I assume it crashes in get_annotation() because I don't have the xml files that they are trying to use. Is there code that you provide to generate these xml files or do we need to manually generate them? Is there some other reason for this crash? Thank you for your help!

Hello, I apologize for the oversight. The code required to get the evaluation loader was inadvertently omitted. Please add the get_eval_loader to the end of the experimet file.
I have also updated the README with the procedure for training on a custom dataset; please review it. If you encounter any further issues, do not hesitate to contact me for assistance.
Again, I apologize for any inconvenience caused.

update: a minimal change in https://github.com/YuHengsss/YOLOV/blob/5f069b29e201c4e099c7c3827cc6c63823ce3141/exps/customed_example/v%2B%2B_SwinTiny_example.py#L221


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.7",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=75752ada77e0726327adf68018b9f50ae091baeb"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "75752ada77e0726327adf68018b9f50ae091baeb",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "drm/amd/amdgpu: fix potential memleak\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.7 by commit 75752ada77e0726327adf68018b9f50ae091baeb. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002552


scrolls to top in async action

The scenario is that suppose i am on url localhost:3030/home than i scroll to the middle of mine page and I click a link localhost:3030/about as i click on this link i am doing some Api call after the call is complete i go to about page. But as i click on the  link mine page scrolls to top than after the i get dta from API i am being routed to about page. So how can i stop going to top of the page.
Any help will be useful.

There won't be support for async router transitions until the rewrite. Any other async handling is out of scope here.


How does the performance compare to RAR and ZIP?[doge]

How does the performance compare to RAR and ZIP?[doge]

Thank you for your interest in our work. Compared to RAR and ZIP, the compression algorithms we chose for our comparative experiments, LZMA and PPMd, offer higher compression ratios. With the goal of reducing storage costs, we did not select general-purpose compressors with relatively lower compression rates for comparison, i.e., RAR and ZIP. Based on the comparative experimental results, Denum is expected to achieve significantly higher compression ratios than RAR and ZIP on benchmark datasets. [doge][doge][doge]

I am a student who has just entered the field of log-related research. I am very interested in your work on log parsing, compression, and other related topics. I would like to ask you how you got started in this research area. If I also want to get started and delve deeper into the research, which relevant papers and code projects should I read?

Thank you for your interest in our work. I am more than happy to share my limited experience with you. If you’re willing, we can communicate via email, or you can send me your contact information for other social media platforms, such as WeChat, through email. This would be more convenient than discussing here.

I have sent you an email and hope to hear back from you soon.


Is rel:mentions needed?

ssb-mentions adds a rel: "mentions" property to the objects in the mentions array. Is this used anywhere? It seems that patchwork does not use this, but patchdeck (which ssb-mentions) does.

oh, no... I think the rel is actually taken from the key to the array. <rel>: [{link:...},...]


Updating from 3.0.12 -> 4.0.1 breaks ByteArrayDataSource

In attempting to update to 4.0.1, we get a compilation error here:
https://github.com/codeforamerica/shiba/blob/2b4d0a3377b5097dba3f078fdf127ca94f42892e/src/main/java/org/codeforamerica/shiba/mnit/MnitEsbWebServiceClient.java#L107-L108
It appears the version of jakarta.activation no longer has a DataSource interface. In our project we don't specify a version: https://github.com/codeforamerica/shiba/blob/af3a156ff2e5633e63be7ea2ec07ef37273a994e/build.gradle#L106
Manually setting jakarta.activation to 2.0.1 (as it's set in your pom.xml) fixes that particular issue but a different class fails to compile within that library. Any suggestions?

3 vs 4 signals major, possibly breaking change; with istack-commons 4+, one has to use activation 2+, older versions of activation won't work, see https://projects.eclipse.org/projects/ee4j.jaf/releases/2.0/plan for details

also note that istack 3x supports "javax..." namespace (javax.activation), while 4x supports "jakarta..." namespace (jakarta.activation)

As I mentioned, upgrading to activation 2.0.1 didn't fix the problem.
For anyone else who comes across this: To fix it I included the Apache Commons Email library as a dependency and used its ByteArrayDataSource instead of the one from istack:
implementation 'org.apache.commons:commons-email:1.5'

the compiler fails to compile: javax.activation.DataHandler(jakarta.activation.DataSource), javax.activation.DataHandler requires javax.activation.DataSource


Star the Repository 🌟

Consider starring this repository if you found this project helpful. And also share the repository with other contributors so that they can also get to know about it!

Please assign this issue to me


Problem of EPIC identified, but seems not solvable unless we provide the reference profile as well.

The high correlation across samples and low correlation across cell types should be due to the reference profile was set as the signature matrix directly, which should be the genome-wide expression table used to derive the signature matrix. If not provided it will use EPIC's own marker gene list and reference profile, which doesn't have the issue.

Resolution:
1- @pietrisko will put the signature matrices on figshare
2- @sgosline will rebuild docker with the files locally
3-  @LifeWorks will then update the r code to load these in locally.

https://ndownloader.figshare.com/files/26488094 ##lm7c
https://ndownloader.figshare.com/files/26488223 ##lm9
https://ndownloader.figshare.com/files/26488313 ##PBMC

Here the genome-wide expression tables for the signature matrices:
https://ndownloader.figshare.com/files/26488094 ##lm7c
https://ndownloader.figshare.com/files/26488223 ##lm9
https://ndownloader.figshare.com/files/26488313 ##PBMC

Thanks, Pietro. Do you have the profile for LM21?

OK. I found LM22 and will need to process all the ref profile to make them usable for epic. Once I process them, will upload to figshare.

I also found LM22 reference matrix and process it to have usable sample names and the exact samples they used, please check if it's identical to the yours.
https://ndownloader.figshare.com/files/26504420

I unassigned myself, The docker image will take a while to build, but once built will have the four matrix files in the /data/ directory (i renamed them to matrixname_ref.txt).

shoot i put it in the wrong docker file. whoops.

Ok, now the epic docker file is corrected.

Ok, now the epic docker file is corrected.

The file need to be preprocessed. I will preprocess them and reupload them to figshare and update the dockerfile later today or early tomorrow,

Solved

Can you link to the PR for this? I want to make sure that the matrices will be added in the perfEval script.

Can you link to the PR for this? I want to make sure that the matrices will be added in the perfEval script.

They are #98 and #99


Run tests in CI

There's a lot of warning spam due to unused code etc, so cleaning those up so CI is nicer.
Resolves: #30

Had to disable some tests in CI, unsure why the linux ones fail since they run fine locally, the mac ones probably fail simply because the CPU allocated for macos runners is abysmal so the tests time out.


Add lifecycle hook called after parent element is mounted

What problem does this feature solve?
considered usage
It is common that refs of parent elements are passed down to children, but when the onMounted() hook of the children is called, the ref is undefined because the parent element is not mounted yet.
the original resovement
Now in order to solve it I'm define a global state that is a boolean that have an init value to be false, then set it to be true in the onMounted() hook of the parent component. I watch it in the child component and when it chages and equals to true,  i use the ref like calling addEventListener.
So i think adding a lifecycle hook called after the parent is mounted is a better choice for this.

What does the proposed API look like?
<script setup>
    let props=defineProps<{parentRef:HTMLElement}>()
    onParentMounted(()=>{props.parentRef.addEventListener('mousedown',()=>{console.log('onmousedown')})})
</script>

you can simply await one tick with await nextTick(). That ensures that everything being mounted in the current render cycle has been mounted properly.
onMounted(async () => {
  await nextTick()
  props.parentRef // will not be defined
})

An alternative would be to not use a lifecycle hook and instead watch the prop.
watch(
  () => props.parentRef,
  (el) => {
    if (el) {
      Do what you need to do.
   }
  }
)

All that taken into account, I don't think this use case warrants another lifecycle hook.


Unable to verify your data submission exception message in Yii 2

Hi!
I encounter this exception message in the following scenario:
I have adyen payment system as a payment api on my Yii 2 project and after the payment is completed, and adyen sends me back to my website I have this exception message:
2014-10-29 13:53:11 [<IP_ADDRESS>][][-][error][yii\web\HttpException:400] exception 'yii\web\BadRequestHttpException' with message 'Unable to verify your data submission.' in /var/www/clients/client1/web67/web/vendor/yiisoft/yii2/web/Controller.php:110
Stack trace:
#0 /var/www/clients/client1/web67/web/vendor/yiisoft/yii2/base/Controller.php(149): yii\web\Controller->beforeAction(Object(yii\base\InlineAction))
#1 /var/www/clients/client1/web67/web/vendor/yiisoft/yii2/base/Module.php(455): yii\base\Controller->runAction('call', Array)
#2 /var/www/clients/client1/web67/web/vendor/yiisoft/yii2/web/Application.php(83): yii\base\Module->runAction('rpc_server/rpc/...', Array)
#3 /var/www/clients/client1/web67/web/vendor/yiisoft/yii2/base/Application.php(375): yii\web\Application->handleRequest(Object(yii\web\Request))
#4 /var/www/clients/client1/web67/web/web/index.php(12): yii\base\Application->run()
#5 {main}
2014-10-29 13:53:11 [<IP_ADDRESS>][][-][info][application] $_POST = [
'module' => 'order'
'action' => 'UpdatePaymentStatus'
'parameters' => [
'order_id' => '32'
'last_payment_status_id' => '2'
'amount' => '5'
'reason_id' => '2'
'no_capture' => '0'
]
]
I have a module named orders and adyen returns me to app/modules/orders/views/default/success.php with this:
merchantReference=3937&skinCode=epLSsdRs&shopperLocale=en&paymentMethod=visa&authResult=AUTHORISED&pspReference=54112541241&merchantSig=cKdpSDSGdwe4MzQEcXtV%2BhpA7I%3D
in the URL. I do not have to process this, actually I don't need that, it's just something adyen returns for back end processing. And it is not the topic of our subject. The point is, that upon redirecting from the adyen website to my project, I just get a blank page. And the logs show me the above message.
I don't understand how to fix it and I already tried to add the line "" in the head like this:
head
meta charset="charset ?>"/
meta name="viewport" content="width=device-width, initial-scale=1"

title) ?>
head() ?>
/head
please help me figure this out!
Kind regards,
Ares Draguna.

@qiangxue it doesn't help me :-(
I have wrote
$this->enableCsrfValidation = false;
in the index acti

on, and still getting the same error

Aliluya !!!, I have sold the problem
Just add $this->enableCsrfValidation = false; in beforeAction of your controller
something like
public function beforeAction($action)     {         $this->enableCsrfValidation = false;         return parent::beforeAction($action);     }

I have to post request from perfect money to my site. How to do this? Its always showing
Unable to verify your data submission
While I have added
`public function beforeAction($action) {
     $this->enableCsrfValidation = false;
    return parent::beforeAction($action);
 }`

Also added $this->enableCsrfValidation = false; in action of the controller. Still it doesn't work.


Flaky tests are back on the menu

I've been experiencing a significant increase in flaky tests recently. I'm guessing this is due to the FindNodes test added to peertest. Would be curious to get confirmation from others. But, this has also raised an issue that when CI runs peertest, if there is a failure, then it doesn't display the error message, it simply just says that the test run failed (example). This makes it more difficult to diagnose the source of flakiness, so we should update how the tests are run to make sure that an error message / stack trace is displayed if it occurs.

I can confirm.
I added some output and I saw the following:
thread 'test::test_launches' panicked at 'assertion failed: nodes.enrs.contains(&peertest.nodes[0].enr)', ethportal-peertest/src/jsonrpc.rs:247:5

Nice, yeah there's a fix in #303 for logging output of the failed test and that's definitely the culprit. Having a tough time sussing out the source of the error though. Comparing logs for a successful vs. failed run doesn't yield much insight since the logs of all three nodes are output simultaneously. Do you have any ideas for a simple way to associate a particular logged line with its respective node while running peertest?

Nvm - 99% I figured this out, will get the fix in tomorrow

Nvm - 99% I figured this out, will get the fix in tomorrow


ESM modules import does not working

To Reproduce
Steps to reproduce the behavior:

Create new npm project: npm init --yes, and install beautiful-react-hooks.
Add "type": "module" to package.json.
Create an index.js file: import "beautiful-react-hooks/useAudio".
Run node index.js, see error: SyntaxError: Cannot use import statement outside a module.

hey @zbinlin ,
thanks for opening this issue, I've tried to reproduce as you suggested and indeed, the package turns out to be unusable.
This is caused by an incorrect exports management in the package.json that is auto-generated during the build phase.
Please, if you like, try to propose a PR to fix the problem, it would be nice to have you among the contributors...
If you can't manage it, no problem, I'll try to fix it as soon as possible
In the meantime, thanks a lot


comparable performance to state-of-the-art C++ libraries

Hi,
It's said to have comparable performance to state-of-the-art C++ libraries.
Is there any document for this comparison and metrics for the comparison?
BR

Hi,
This recent works compares multiples libraries, including Lattigo:  New Insights into Fully Homomorphic Encryption
Libraries via Standardized Benchmarks

Hi,
This recent works compares multiples libraries, including Lattigo: New Insights into Fully Homomorphic Encryption Libraries via Standardized Benchmarks

thanks


Add command to swap matrix for TRS

Sometimes a glTF node will contain a full matrix, when a person editing it may want to see translation, rotation, scale.  It would be nice to have an option to decompose a matrix to TRS, and another option to recompose it.

glMatrix code: https://github.com/toji/gl-matrix/blob/d50931b75f014d79c3c9586f3af4260cacbed27e/src/mat4.js#L1125


Update Chinese(Taiwan) translation

as title

Is this one right after all? ;)

Yes, damn those PRs
林博仁<EMAIL_ADDRESS>2016年12月20日 下午7:35，"Lonami"<EMAIL_ADDRESS>
Is this one right after all? ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LonamiWebs/Stringlate/pull/17#issuecomment-268221828,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMyXguX2A20hO0hqsnq0X__5qU8lxuKhks5rJ72ZgaJpZM4LRrfS
.

Hello @Lin-Buo-Ren would you mind updating your translation before the next v0.9.5 release? You can either translate this Gist or use Stringlate itself! Thank you.

https://gist.github.com/Lin-Buo-Ren/1edc20bc4f9a8ad5e1a35c60bc893f8b
done.

Thank you!! Sorry if I was a bit rude, there were quite a few people I had to ask it to so I just made a "default template" :)

No worries.


feat(collector-exporter): allow configuration from env #2099

I centralized default configuration inside the main package exporter-collector, each variant of the exporter (for each signal/protocol) is defined with abstract functions.
I'm not sure if everything is spec compliant, there actually a lot of possible mix: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md
I've also changed the default port for HTTP which seems to be 4317 for all protocols: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#otlphttp-default-port
Since the headers configuration is using the same correlation format that the baggage, i modified the core package to export utils to parse them (i expect more configurations will use this later on)
Fixes #2099

Seems like quite a few changes are here which are not related to environment

Seems like quite a few changes are here which are not related to environment

Because all the defaults was repeated in each package and each platform, i refactored it to centralize the config between all packages.

Even though there are conflicts + tests are failing, i would like some reviews to know if we agree on the way of doing it

Closing this PR since addressing changes is basically a new PR, see #2117


feat(quickfix): set groups

This PR adds some groups for the default quickfix. The main target is to achieve consistency with other aspects of the colorscheme, since the default behavior feels a bit off. The changes are somewhat opinionated, therefore I am more than open to discussion.  Here are some before and after screenshots:

The changes look fine. Following pmenu makes a lot of sense. 👍


Feature Request: kwm-overlay for all windows

E.g. add the following to kwmrc
# Enable border for (un-)focused window
kwmc config border [enable,disable]
kwmc config border size <width>
kwmc config border color <color>

This border should be default for every window, but overridden by focused-border, marked-border and prefix-border.

While this would be a good looking feature, I suspect it woud require more reasources than I find feasible. It would (at least with the current way kwm-overlay works) require a separate running instance of the kwm-overlay application for every single window you have open and want a border on.

Considering kwm-overlays resource usage is close to 0, that'd be a non-issue imo.

I kind of agree, a separate kwm-overlay process for each window seems excessive. In my opinion this should probably wait until the overlay is baked into kwm itself

I've come to the conclusion that this is not something I feel is worth doing. It raises the need to handle a lot of edge-cases, especially when it comes to windows on different monitors, and increases the complexity of Kwm by a very very huge margin.
I find that it is simply not worth experimenting with it.


Wdlupdate

Fix for splitRG task, associated with GATK fourm Question
Disk sizing now takes place within tasks.

:+1:


Improve scalability of the EC2/Route53 controllers

Reddit uses provider-aws to primarily manage EC2 and Route53 resources. In the future we may be adopting it for interacting with various AWS managed services. The provider-aws controllers currently manage on the order of several thousand resources each, ~3000+ EC2 instances, and ~6000+ route53 records.
We are currently running provider-aws version 0.46.
What problem are you facing?
At this scale we run into issues with high queue depth in our controllers, even with 20+ active workers (provider-aws --max-reconcile-rate=20).

Figure 1: Crossplane controller is unable to work through queue of reconcile requests even with 20 active workers at our scale.
Reconcile times for EC2 instances typically take greater than one second at median and can take up to 6 seconds at p99.

Figure 2: Reconcile time for instance resources
Without any jitter, ResourceRecordSet resource observations can cause a backlog that can take up to an hour to resolve. AWS rate limits route53 API requests to 5 requests / second / account, which makes it extremely easy to hit the rate limit when performing observation on route53 resources. These queue depths exist even with poll intervals set to 30 minutes (up from 1 minute) in our fork.

Figure 3: Resource record set controller is backlogged during instance observation.
How could Crossplane help solve your problem?
Allow configuring per-resource poll interval / jitter
Introduce jitter in resource record sets, introducing jitter smooths the request rate of the resource due to observations and minimizes the impact of the rate limit. We hard-code jitter in our crossplane provider-aws fork.

Reduce reconcile time for EC2 instance resources
Reduce the time spent to perform an EC2 instance observation by: (1) reduce unnecessary API calls for duplicate data, (2) parallelize API calls where possible.

Looking forward mainly for the Route53 Record observation fixes. API calls should be merged into big chunks of ResourceChangeBatches at once.
Using xpkg.upbound.io/upbound/provider-aws-route53:v1.2.1 dealing with hundreds of applications: failed to observe the resource: [{0 reading Route 53 Record (ZONEID_DOMAINNAME_A): Throttling: Rate exceeded status code: 400, request id: RID []}].

/fresh


[FIX] ClickableValue: correct closing tag

Close 'clickable-value' tag was never added due missing parenthesis.

Hi @SeeSharpSoft,
Thank you for the fix. :+1:
Best regards,
Chariyski


No build file

After doing the gradle command: gradle init --type basic
and then choosing "2" for Kotlin, I do not see a build.gradle.kts file anywhere in any of the folders. My root folder contains: 2 folders (.gradle and gradle), then 2 files (gradlew and gradlew.bat).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d8815595-4c76-7c52-2d2c-dcbdd635bcea
Version Independent ID: 723dfef2-1e9f-478d-1fa4-06254c8d41fc
Content: Quickstart: Computer Vision client library for Java - Azure Cognitive Services
Content Source: articles/cognitive-services/Computer-vision/quickstarts-sdk/java-sdk.md
Service: cognitive-services
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

Thanks for the feedback! We are currently investigating and will update you shortly.

@PatrickFarley Hi Patrick, could you please help with this issue? I don't see more details for the result, could you please add more if needed? Thanks.

#please-close
Feel free to reopen if you still have the issue

@PatrickFarley Thanks, I must have lost notifications for this when I had an account switch mid-October. I think we are not working on this anymore, but thanks anyway!


bug(material table): Infinite loop when component has any setInterval

Is this a regression?

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

The previous version in which this bug was not present was
No response
Description
I have a simple page which contains only material table(I have copied the material sample table stackbliz example) and related logic to bind header and display columns. In header row cell is bound with a method(function)  to return some dynamic value.  Other than this I have only 1 additional simple setInterval event inside ngOnInit.
Problem : Header row bind method keeps on triggering whenever setInterval triggers.
Below is the stackbliz example
https://stackblitz.com/edit/angular-material-data-table-infinite-scroll-pchcho?file=src/app/app.component.ts

Reproduction
Steps to reproduce:

add any method to mat table header binding.To know how many times its called the method add console log.
add setInterval to current component.
Watch the console, testMethod keeps on executing for earch setInterval trigger(5 second)

Expected Behavior
Mat table header binding should not call the function when setInterval triggers
Actual Behavior
Mat table header binding method keeps on executing when setInterval triggers
Environment

Angular: cli 12
CDK/Material: mat
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Hello, it's unrelated to Angular Material, But Angular itself.
That's how change detection works with Angular.
That's why it's encouraged to avoid calling functions in templates for performance purposes.

Closing since this is just how change detection works.


Aggregate PRs

Aggregate of the following PRs:
https://github.com/wildfly/wildfly-core/pull/4864
https://github.com/wildfly/wildfly-core/pull/4866
https://github.com/wildfly/wildfly-core/pull/4877
https://github.com/wildfly/wildfly-core/pull/4878
https://github.com/wildfly/wildfly-core/pull/4880

Core - Full Integration Build 11112 outcome was FAILURE using a merge of a99e2c9a05bdd2bf1bfb351491a738129ef44c1a
Summary: Tests failed: 1 (1 new), passed: 4079, ignored: 43 Build time: 02:27:45
Failed tests
org.jboss.as.test.layers.LayersTestCase.testServlet: java.lang.Exception: Some unreferenced modules are un-expected [org.wildfly.security.http.sfbasic]
	at org.jboss.as.test.layers.LayersTest.test(LayersTest.java:109)
	at org.jboss.as.test.layers.LayersTestCase.testServlet(LayersTestCase.java:146)

Most merged, one PR to be tested again.


Application looks frozen when working with big graphs

What steps will reproduce the problem?
1. Open application
2. Load a big graph
3.

What is the expected output? What do you see instead?
Application should look like before loading the graph.
Instead the application window turns grey, it gives the appearance that the
application is frozen but it is not. If the user waits long enough and the
computation ends the application window looks like it is supposed to look.

Original issue reported on code.google.com by bombax on 1 Mar 2012 at 2:54

Should probably use the classes from the QtConcurrent namespace to offload work to a background thread and keep the UI responsive. Careful with threading problems when communicating back the results.


Heltech ESP32 error just after the NTP

I hae just tried to set this up on one of my Heltec ESP32 modules. for some reason the first issue is with the NTP server name. I tried the default one and used the NZ NTP server name however neither seemed to work.
The next issue seems to be just after that where the system errors out and reboots.
Any sugestions as to how to track this down?
`A WlanStatus:: CONNECTED to SPARK-XT6HVY
Host esp32-65e438 WiFi Connected to SPARK-XT6HVY on IP=<IP_ADDRESS>
Local UDP port=1700
Connection successful
Gateway ID: D8A01DFFFF65E438, Listening at SF9 on 868.10 MHz.
Setup:: ERROR hostByName NTP
abort() was called at PC 0x400dc802 on core 1
Backtrace: 0x4008cc20:0x3ffb1ed0 0x4008ce51:0x3ffb1ef0 0x400dc802:0x3ffb1f10 0x400de5d1:0x3ffb1f30 0x400e9cdf:0x3ffb1fb0 0x40088ba1:0x3ffb1fd0
`

The site "nz.pool.ntp.org" should work in New Zealand (NZ). If not, look at your DNS server setup and whether it is working ok.

Thanks @platenspeler  will take a look, I know it works on other devices so not quite sure why its not working on this one.

mind you the concerning one is the abort() when the system then reboots and throws the back trace. Not sure if this is due to the failure of the NTP so will fix that first.

When the NTP server fails to get a name from the network (WiFi.hostByName(NTP_TIMESERVER, ntpServer line 629 ESP-sc-gway.ino) it calls die().
So put all your debug code to find out whats happening in that section just before die() :-)

Does it work now?

Does it work now?

I have not had the chance to set it back up yet, silly season is upon us. Hopefully I will get the chance to set it up this weekend and see if that sorts the issue out.
Fingers crossed it will work :)

Thanks for update.

I will close this issue, since I have changed a lot of code since December. I did not encounter this issue on my gateways in January.


Cannont disable parental controls if NNID is for a child

If the linked NNID is for a child under 13, you cannot clear parental controls, making the not "Disable the parental controls of your device before doing the 2.1.0 ctrtransfer. If you do not know the password, see this site." difficult to follow.

Anecdotally, I succeeded with the following steps (single test case, no replication possible for me)

Took a NANDmin backup
Removed all parental restrictions individually (parental controls are not cleared, pin is still set, but all options are set to "do not restrict")
Opened the web browser to make sure I wasn't prompted for a pin
Did the ctrtransfer (skipping backup, as I just took one in step 1)

The result: success, and after restoring the backup, all parental controls were as they had been setup originally.
I'm not sure how much detail should be added to the "Disable the parental controls ..." step, but it may deserve a "troubleshooting" entry.

Worked for me also. The weird thing is, that when launching any non-official app like FBI, it asks for pin code, even if all are set to no restrictions. But everything works.


Lint

See this for word definition

Exclude isEmptyRepoRoot from repo-age
Expect token for clone-branch
Use features.error instead of throwing (firefox)
Tuple Types
Add a deinit for highlight-deleted-and-added-files-in-diffs. When switching pages, the list needs a reload.
Fix clean-conversation-headers error see https://github.com/sindresorhus/refined-github/pull/3408#issuecomment-675449244 (not sure if this fixes both errors)

If you’re looking for more linting (separate PR maybe) there are a few rules here that were disabled, but are helpful and probably are not a problem to us:
https://github.com/xojs/eslint-config-xo-typescript/blob/master/index.js
Have a look, perhaps you can try adding them to our config and seeing if they’re reasonable.
If they’re too difficult to add or seem to require a rewrite (or many eslint-ignore), let me know and don’t lose your mind over it 😃

I will git it a ~lint~ shot


listUsers result array is not automatically sorted by date, as specified in docs

[REQUIRED] Step 2: Describe your environment

Operating System version: macOS High Sierra, V.10.13.6
Firebase SDK version: Firebase Tools for Node.JS 6.0.1
Firebase Product: Auth (Firebase Admin SDK)

[REQUIRED] Step 3: Describe the problem
The Problem
According to the Firebase admin docs, listUsers() will return a list of users automatically sorted by the date they were created if no page token is specified: https://firebase.google.com/docs/auth/admin/manage-users#list_all_users
However, upon viewing my results, it appears that Firebase returns a list of users which have been sorted alphabetically by UID, rather than date:

(Due to how the console shows logs on Firebase, the bottom result is the first result, and so on)
If I go onto the auth console and order by UID, I can see that the order is exactly the same, as shown here:

Steps to reproduce:
Simply create a few user accounts on Firebase where the UID and creation date will sort the users differently. (eg. a UID beginning with 'a' and a creation date of 28/11/2018, a UID beginning with 'b' that has a creation date of 26/11/2018 and a UID beginning with 'c' that has a creation date of 27/11/2018.
Upon executing listUsers(), you will get a..., b...., c..., alphabetically ordered. According to the documentation, you should get back b, c, a.
Relevant Code:
Here's the snippet I'm currently using in my Node.JS cloud functions.
export function deleteTestUsers() {
    const p = new Promise((resolve, reject) => {
        admin.auth().listUsers(1000).then((response) => {
            response.users.forEach(user => {
                console.log('user', user.toJSON());
            });
            resolve();
        });
    })
    return p;
}

That documentation is incorrect. We plan to fix it but haven't had the chance to get to it. Users are not sorted by date creation.

Thanks guys!

Any way to order that list somewhere?

A bit late to the party but: how can we retrieve those users sorted by creation date?

Any update about listing users sorted by creation date?


Add study case with MMM + CLV

Create some fake dataset with continuous non-contractual process and build a story around:

Using MMM to infer cost of acquisition across different channels
Using CLV to infer differential lifetime value of customers coming from different channels
Making business decision that takes the two sources of information into account
a. Preferring to invest in a channel with higher CAC because of higher CLV
b. Binary decision to not further invest in channel if CLV is lower than CAC

Requires: #24, #19, #39
We might use this case-study for the initial announcement of the package

I could also see RFM Segmentation being valuable for this, because customers in different segments would benefit from different strategies, which can be tied back directly to marketing budgets and channel contributions.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4327

Questions ?
Please refer to the Backport tool documentation


I want to create mix player with one audio and video file play together at same time

I am trying to play video and audio at same time in flutter by using
assets_audio_player: ^2.0.9+2 ==> For assets audio file playing
audioplayers: ^0.16.1 ==> for URL audio file playing
video_player: 0.10.12+2 ==> for URL Video file playing
but when play audio and video in same time at same screen that time video was stack and video volume is stopped.
Thanks

Hi @bhallaramdhatarwal
As far as I know it is not possible to play video and audio at the same time. They both play sound so unless you are building for desktop (which does not seems the case here) you can't do that on mobile devices.
Closing, as this isn't an issue with Flutter itself.  If you disagree, please write in the comments, providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml a minimal reproducible code sample that does not use 3rd party plugins, and I will reopen it.
Thank you

@pedromassangocode  Thanks.
I know. But i want to play video in mute volume and audio with sound and also, Is it possible to play audio in background like in android doInBackground thread and video in foreground or one play in UI thread and other in background thread.

@pedromassangocode  Please reopen this issue.

From my knowledge on native Android development and as far as I know, it is clearly not possible to play audio and video at the same time on Android (and maybe on iOS). Android has only one output for audio and it cannot be used by two sources at the same time.
This will still kept closed because you are using non Flutter plugins. If you disagree, please share a minimal reproducible complete code sample that does not uses third-party plugins and the steps to reproduce the issue and I will reopen it.
Thank you

I am trying to play video and audio at same time in flutter by using
assets_audio_player: ^2.0.9+2 ==> For assets audio file playing
video_player: 0.10.12+2 ==> for URL Video file playing
but when play audio and video in same time at same screen that time video was stack and video volume is stopped.
and if I used URL for audio & video. And audio player library for audio play that time smoothly play both audio and video
Thanks


v3.19 on maven-central no longer declares external dependencies

After upgrading our docusign-esign-java dependency to 3.19, code didn't build anymore.
It seems that the external dependencies are no longer packaged or properly declared in that library, so that they are no longer pulled in by local builds.
This is also reflected by the fact that 3.19 on maven central no longer has "compile dependencies" (https://mvnrepository.com/artifact/com.docusign/docusign-esign-java/3.19.0) compared to 3.18 which still does (https://mvnrepository.com/artifact/com.docusign/docusign-esign-java/3.18.0).
It's nice that the vulnerability is gone too, but I fear it's rather because there are no transitive dependencies declared anymore and not because the problem has been fixed.
It looks like upgrade to 3.19 was major (the commit touched > 500 files), but the release notes on github don't say much.

@cheppsn explicit dependencies created lot of version conflicts for a lot of users. The decision was to use uber jar. Here is how you can get 3.19.0 with Maven (similar syntax exits for Gradle and others):
<dependency>
  <groupId>com.docusign</groupId>
  <artifactId>docusign-esign-java</artifactId>
  <version>3.19.0</version>
  <classifier>shaded</classifier>
</dependency>

@mmallis87 Thanks for the information, we'll switch over to that one then 👍
If I may recommend updating the release notes on github? (this is our primary source of information when updating libraries) Also it seems that probably #211 and #197 can be closed or updated accordingly.

@cheppsn @mmallis87 Please see comment here regarding this issue

@mmallis87, do you happen to know Ivy dependency config equivalent of Maven that you mentioned here https://github.com/docusign/docusign-esign-java-client/issues/234#issuecomment-1139825191?
Thanks!

I have two problems with the current approach:

using the unshaded version (without dependencies) is leaving the user/client unaware of the dependencies that need to be provided (one has to look them up in the POM and update them by hand, whenever the docusign client is upgraded) -> this is what we are doing since the last upgrade
using the shaded version in a server environment is worse, as the packaged classes may conflict with the rest of the application dependencies. because the dependencies are no longer explicit, a dependency management like spring boot can not lift/adjust the versions and the conflicting classes stay on the classpath (not an option)

It would be very helpful, if the produced artifact would at least declare the dependencies that need to be provided (i.e. as "soft dependencies"), so that they are explicitly declared and can either be excluded by the build config (if conflicting) or managed by something like the Spring Boot dependency management plugin (gradle or maven).
I assume that defining a parent POM with the provided dependencies would already suffice.

I think the shaded dependencies should also be relocated, to reduce duplicate classes at runtime when the using project has same dependency declared.

I agree, external dependencies should be declared in a proper way. @vinz, I see that you've got this issue assigne to you, do you have an idea about when the fix will be released? Thanks


Carthage distribution

is #46 relate to this?

@DAloG  It is somehow related.

@DAloG , @xNekOIx this is a separate feature. Carthage does not work with static frameworks.
It accepts only dynamic frameworks that can only be deployed on iOS 8 and newer.

However, it looks like carthage may start supporting static frameworks
https://github.com/Carthage/Carthage/pull/622

@dodikk Carthage/Carthage#622 is not related to static frameworks, that is about a “universal target” (universal means the target can build both OS X and iOS platforms with selecting appropriate scheme). Carthage would not support static frameworks in the future.


Test PR for preview

@spoenemann some test PR to check if the preview mechanism works. However as this PR comes from a fork the action to add a PR comment fails as PRs from forks dont get write tokens. There are workarounds for that, but for security reasons its best not to hand out write tokens to PRs from forks as everyone can create them.
I guess you will only have PRs from the repo itself?

I guess you will only have PRs from the repo itself?

There will often be contributions from forks. But we could change the repo settings to require approval by maintainers before  running Actions?

The github-deploy-pages action uses internally the sticky-pull-request-comment action which adds comments to the PR itself upon completion. This action needs write permissions for for pull-requests. For PR from forks, GitHub does not issue write tokens during workflow run for good reason. There is a workaround that we also utilize in our validation scripts that can be found here: https://github.com/adoptium/.eclipsefdn/blob/main/.github/workflows/validate.yml
The idea is to use pull_request_target instead.  You should read https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ before using that approach.

Also, as you removed the netlify configuration from the repo, should the netlify app be uninstalled as it is not used anymore?
It had some advantages compared to deploying to gh-pages though imho.

Yes we can remove the Netlify app. And yes, Netlify is more comfortable and offers very nice deploy previews, but we'd like to move the deployment to the Foundation. If you offer Netlify deployments as alternative to GH Pages, we can consider that as well.

The netlify app has been removed from the organization.
I am not aware of what the EF offers in terms of deployment environments for previews, best to raise a ticket in the HelpDesk.

btw the link to the issue in the deploy preview workflow from forks is here: https://github.com/rossjrw/pr-preview-action/issues/3

No solution in sight so far. I propose to remove the previews (#208) until someone comes up with a properly working preview feature.


Update for upcoming Pony release

This commit updates the library to work with Steed's model of subtyping, coming
in the next Pony release.
This change is backwards compatible with ponyc 0.40.0

The PR title will appear in the CHANGELOG, can you update to be more "end user meaningful"?

Done


✨ Add setTheme to @master/css.react

Description
Currently, the package @master/css.react provides useful hooks, but there is no way to set the Theme through React.
Additionally, theme is separate from scheme therefore a useTheme() hook should be exposed to avoid confusion.

const themeService = useThemeService()

themeService.switch('dark')


Populate Email to Receive Proposals on Opportunity detail page

@ccoldwell - on the Opportunity detail page, in the How to Apply section, could you please ensure that the email address from the Create Opportunity form populates?

Did this on this commit: https://github.com/BCDevExchange/devex/commit/5280549ae5cb4d016eb2d27020d76f8d04afb172. Then we reversed it on https://github.com/BCDevExchange/devex/commit/17e28194e2066cf3af5949188be6feb9461ba5e0
Adding this to Backlog on DevX App Trello board.


[device_info] Migration to platform interface in device_info

Description
This pull request migrates the device_info plugin to use platform interface.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

I was trying to migrate it but seems that someone did it already, nice pr :100: Could you try and add support for linux too please? @yash1200

I was trying to migrate it but seems that someone did it already, nice pr  Could you try and add support for linux too please? @yash1200

I have implemeted the support for linux as well, will make a pr after this gets published.

For this to be easier to review and merge, I'd recommend you to split this into smaller pull requests:

Moving everything from device_info to device_info/device_info (*in this PR)
Creating (and publishing) the platform_interface package (*in this PR)
Using the platform_interface package from the device_info core plugin
... Add more platforms!

It is useful to have one big PR like this so people can just clone this and go, but the tooling is not very good (for example the tooling won't let you do step 3 until you've done step 2)

@ditman In this pr, I have only addressed step 1 and 2, step 3 and 4 will be implemeted after this gets published. Let me know if I understood you correctly.


RuntimeError in pickling

Hi Taka,
Thank you very much for sharing the code.  I am running into this problem:
dataprep.py", line 65, in main
pickle.dump(library, file, protocol=pickle.HIGHEST_PROTOCOL)
RuntimeError: Pickling of "rdkit.Chem.rdSubstructLibrary.SubstructLibrary" instances is not enabled (http://www.boost.org/libs/python/doc/v2/pickle.html)
Best regards,
Rad.

Hi Rdk0,
Thanks for opening. Could you please provide more details of information of your env?
version of RDKit, python etc...
Thanks!

Hi iwatobipen,
Pop!_OS_20.10
RDKit Version: 2018.09.1
python Version: Python 3.6.12 |Anaconda, Inc.
pickle 4.0
thank you.


[SR-15620] Struct's implicit constructor includes get-only properties

Previous ID
SR-15620

Radar
None

Original Reporter
mininny (JIRA User)

Type
Bug

Attachment: Download

Environment
Xcode 13.1
Build version 13A1030d

Additional Detail from JIRA

Votes
0

Component/s
CodeCompletion

Labels
Bug

Assignee
None

Priority
Medium

md5: 90abdca650c3d0626eae2796999910ea

Issue Description:
struct Test {
    var a: Int
    var b: Int {
        get { return a }
    }
}

Xcode's code completion suggestion is Test(a:b:) when it should be Test(a:) since b cannot be set.

@AnthonyLatsis This issue seems fixed. I've checked in Xcode 14.0.1, Swift 5. and Swift 5.5. Check screenshots attached for reference.
here is the error description if i try to write Test(a: 40, b: 50).
error: extra argument 'b' in call
let obj = Test(a: 40, b: 50)

Thanks for checking @adi-sharma26!

Adding a test in https://github.com/apple/swift/pull/72529


fix: use oidc v2.0 issuer in db-token.service

Which issue this PR addresses:
RP startup errors out with
oidc: issuer did not match the issuer returned by provider, expected "https://login.microsoftonline.us/cab8a31a-1906-4287-a0d8-4eef66b95f6e/" got "https://sts.windows.net/cab8a31a-1906-4287-a0d8-4eef66b95f6e/"

this is because we use "https://login.microsoftonline.us" (comes from autorest environment config) but we compare it with the issuer advertised by the v1 well-known openid config endpoint :
V1 :
https://login.microsoftonline.us/cab8a31a-1906-4287-a0d8-4eef66b95f6e/.well-known/openid-configuration
returns issuer as https://sts.windows.net/cab8a31a-1906-4287-a0d8-4eef66b95f6e/
V2:
https://login.microsoftonline.us/cab8a31a-1906-4287-a0d8-4eef66b95f6e/v2.0/.well-known/openid-configuration
returns issuer as https://login.microsoftonline.us/cab8a31a-1906-4287-a0d8-4eef66b95f6e/v2.0 as expected
Test plan for issue:
attempt deployment
make sure it's the same behavior in public cloud tenants (should be)
Is there any documentation that needs to be updated for this PR?
no, this is internal.
It seems that the portal made the change to the v2.0 provider, but that the db-token was not updated
see https://github.com/Azure/ARO-RP/blob/062b83e8a8eed00063e7662914bae875bb440c4b/cmd/aro/portal.go#L153

@mjudeikis Can you review and test this in public?

/azp run ci

/azp run e2e

/azp run e2e


docs(using-react-redux/static-types): fix typos

This PR fixes a typo and header format
https://react-redux.js.org/using-react-redux/static-typing#typing-the-useselector-hook

Thanks!

Thanks! Unfortunately, since we have versioned docs, the changes may also need to be applied to the copies in the website/versioned_docs/ folder as well.  Can you check there?

Welp, I guess it'll have to be in another PR :)

@madbonkey
I have checked the entire project and only the version-7.1 has this static-types.md file.


fix: unable to start container process on OpenShift

Running the container image on OpenShift fails with:
unable to start container process: exec /deployments/run-java.sh: permission denied

Fixes #609.

Do we have an issue describing this problem?

I've created #609.


Allow unique_key to take a list

resolves #2479

Description

Support for unique_key can be a string or a list.
merge macro support for a unique key being a list.

Checklist

[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change

@triedandtested-dev Do you think you'll be able to sign the CLA? If so, I'd still love to have this change, and the corresponding changes to the default macro implementations in merge.sql as well :)

What is the status of this PR? I see some failed CI's and not development for two months on this

What is the status of this PR? I see some failed CI's and not development for two months on this

Can we have an update please on whats holding this up?

Currently I haven’t had capacity to look into this due to project
commitments.
On Mon, 24 Jan 2022 at 14:53, arun-anilkumar @.***>
wrote:

What is the status of this PR? I see some failed CI's and not development
for two months on this
Can we have an update please on whats holding this up?
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/dbt-core/pull/4159#issuecomment-1020182501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5ZJ6L7DJMTMS7LKCZOT3LUXVRUZANCNFSM5G5VOJTQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Bryan Dunkley

Bryan: Since you don't have time right now to finish this off, would you mind if we took it over? It would be nice to get it merged.

Not at all. You are welcome to take it over.
On Mon, 24 Jan 2022 at 17:14, Gerda Shank @.***> wrote:

Bryan: Since you don't have time right now to finish this off, would you
mind if we took it over? It would be nice to get it merged.
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/dbt-core/pull/4159#issuecomment-1020339855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5ZJ6KETFZCTTTMWMRYDNDUXWCGZANCNFSM5G5VOJTQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Bryan Dunkley

This pull request has been replaced by #4618


Fix only staged files.

Before, the staged tree was used only for finding the list of files.  Now, linting is run on the staged version of the code as well.
If errors are detected, we recommend to the user that they run:
./tools/pre-commit.py --fix
That will execute the linter with the --fix flag, but only on the files that were staged already.

@tupui The rabbit hole keeps getting deeper ;)
This catches a bug (linter was running in working directory instead of in staged-file-only-checkout)).
It also removes automated fixing, but gives instructions on how to do so.

Thanks @stefanv, it's still in draft. Do you need to do something else?

@tupui, yes I think this is an improvement. It fixes at least one bug :)
The flag on line 72 is probably not strictly even required, but also doesn't hurt:
https://github.com/scipy/scipy/pull/17948/files#diff-cf3ecdece6f43358cd78f6f423d74a57175f30b2faa99693e82650535caaa6a3R72


Only one InjectionMethod with the same name is executed.

Description
Only one InjectionMethod is called if the method name is the same.
This was working in 5.8.13 but not anymore in 5.9.*. I have checked 5.9.5 and 5.9.7.
To Reproduce
class A
{
	public void Register1(string name) { names.Add(name); }
	public void Register2(string name) { names.Add(name); }
	public IEnumerable<string> Names { get { return names; } }
	readonly List<string> names = new List<string>();
}

[TestMethod]
public void TestMethod1()
{
	var container = new UnityContainer()
		.RegisterType<A>(
			new InjectionMethod(nameof(A.Register1), "1a"),
			new InjectionMethod(nameof(A.Register1), "1b"),
			new InjectionMethod(nameof(A.Register2), "2a"),
			new InjectionMethod(nameof(A.Register2), "2b"));

	var a = container.Resolve<A>();
	Assert.AreEqual(4, a.Names.Count());
}

Yes, it does Select().Distinct() on these injection members.
Calling the same method on the instance is nondeterministic, so it is not supported.

Thank you for quick reply. But isn’t it  a breaking change?  Plus it is not clear why calling the same method with different parameters is non-deterministic but calling multiple different methods is not. In both cases something should determine an order of the calls. The only order which I can think of is an order they are registered.

Yes, it is a breaking change but it makes whole process much faster.
If you want to modify this behavior, you could create an extension with your own derivative of Method Processor and override this method to accomplish what you want.

I have created my custom class of "Method Processor" with my custom method "Select" but I don't know how to change it in Unity. How to configure Unity with my new class?


009-ADR-Migrating-jQuery-to-JS-ES6-and-Eliminating-CoffeeScript-Dependency

ADR05: Migrating jQuery to JS ES6 and Eliminating CoffeeScript Dependency
Context and Problem Statement
Bigfoot.js was originally developed when JavaScript tooling was more primitive, and ES6 standards had not yet been established. As a result, the code relies heavily on jQuery for DOM manipulation and CoffeeScript as the primary scripting language. However, with the advent of ES6 and its widespread adoption, continuing to depend on these older tools introduces unnecessary complexity and overhead. CoffeeScript, in particular, adds an extra layer of complication due to its dependency on transpiling into JavaScript, while jQuery's usage adds extra weight and outdated conventions to the project.
Given that Bigfoot.js is a relatively simple tool for footnotes, it doesn’t require heavy tooling or dependencies. The move to vanilla JavaScript (ES6) can simplify the project while improving maintainability, performance, and scalability.
Decision Drivers

Simplicity: The project primarily handles footnotes, which is a simple use case that doesn’t warrant the overhead of jQuery and CoffeeScript.
Maintainability: Using native ES6 JavaScript will modernize the codebase and eliminate the need for transpilers or dependencies.
Performance: Removing jQuery will reduce unnecessary overhead, as modern JavaScript can handle DOM manipulation more efficiently.
Future Scalability: Moving to ES6 allows for easier modularization (as per ADR02) and ensures the project can scale without relying on outdated tools or frameworks.

Considered Options

Keep jQuery and CoffeeScript: Maintain the current structure.
Migrate to ES6 and eliminate CoffeeScript and jQuery: Refactor the code to use vanilla JavaScript (ES6) and remove all dependencies.
Adopt a modern frontend framework (e.g., React, Vue): Transition to a modern web development framework.

Option 1: Keep jQuery and CoffeeScript
Pros:

No need to rewrite the current codebase.
Minimal upfront development time.

Cons:

Outdated: CoffeeScript is no longer actively maintained, and jQuery’s necessity has diminished with the advent of ES6 and modern browser APIs.
Complexity: The current setup introduces unnecessary tooling and dependencies for what is essentially a simple task.
Limited future-proofing: Sticking with older technologies limits scalability and modularization in the long run.

Option 2: Migrate to ES6 and eliminate CoffeeScript and jQuery
Pros:

Simplicity: We only need an HTML file, a CSS file, and a JS file for this footnote system—no tooling or extra dependencies required.
Improved maintainability: ES6+ JavaScript is now standard, making it easier for future developers to understand and maintain the code.
Better performance: Removing jQuery reduces the size of the codebase and improves load times, especially on smaller devices or slower connections.
Future scalability: The ES6 modular structure makes it easier to expand or modify Tinyfoot without major refactoring later on (as outlined in ADR02).

Cons:

Initial refactoring time: Migrating away from jQuery and CoffeeScript will require rewriting parts of the codebase.

Option 3: Adopt a modern frontend framework (React, Vue)
Pros:

Scalability: A modern framework could provide advanced state management and DOM handling, making it easier to scale for more complex use cases in the future.
Tooling: Popular frameworks come with modern build tools and testing environments that are helpful for larger applications.

Cons:

Overkill: Footnotes don’t require the complexity or tooling of a full framework like React or Vue. This would introduce unnecessary learning curves and dependencies.
Performance overhead: A modern framework would add significant weight for a feature as simple as footnotes.
Increased complexity: Adopting frameworks would go against the goal of simplifying the project.

Decision Outcome
The chosen option is Migrate to ES6 and eliminate CoffeeScript and jQuery.
This decision will modernize the codebase by refactoring it to native ES6+ JavaScript, removing the need for transpiling (CoffeeScript) and simplifying DOM manipulation (by removing jQuery). Given that footnotes are a simple feature, this change will significantly reduce complexity, improve performance, and make the project more maintainable without introducing unnecessary dependencies.
Consequences

Positive:

Simplified codebase: The new structure will have only HTML, CSS, and JS files—making it leaner, easier to understand, and more maintainable.
Improved performance: By eliminating jQuery, we reduce the size of the JavaScript file and streamline the way we interact with the DOM, which will lead to faster load times, particularly on mobile devices or slower networks.
Future-proofing: With ES6 standards in place, future development (such as modularizing the code as per ADR02) will be much easier and follow best practices for modern web development.

Negative:

Initial refactoring cost: Time and effort will be needed to refactor the existing codebase, but the long-term benefits of maintainability outweigh this initial cost.

Confirmation
The success of this migration will be confirmed through:

Code review: Ensure the refactored ES6 code maintains the same functionality as the original jQuery/CoffeeScript implementation.
Performance testing: Compare the load times and overall performance before and after the migration, particularly on content-heavy pages with multiple footnotes.
Maintainability: As we modularize the code in the future (ADR02), ensure that the structure remains clean and that the migration has made it easier to extend TinyFoot without introducing technical debt.

I like this approach and we have been able to achieve most of it. Although, I feel the code can be modularised the way it exists in Littlefoot (separating events, popovers, util functions and usecases for the features).
This would make adding new features simpler and make it more scalable

Another aspect to consider is support for older browsers.

We should minify, and bundle our converted ES6 modules using Rollup/WebPack/Parcel if we wish to transpile and enable support for older browsers.
I don't think it's a mammoth task implementation wise, but the real question is - do we want to support previous browsers? Any thoughts?


Feb Gems draft for review

Hey @shcheklein, @jendefig and I drafted up the Gems for this month. Would you review? We'd like to have it out by Friday since that's the last work day in February.
Questions:

we have a question about dependencies when installing DVC as a Python library with conda. Is it correct that you need to add options for remote storage (i.e., pip install dvc[s3]) only for pip? From the docs, it looks this way, but I wanted to confirm.

Can we add both Jeny and I as authors on a blog post?

Also, @jendefig, we'll need a new header image for this month. Can you do this? I can share with you the template i use!

Looks like image size is a bit smaller than it should it be? it is usually something like 1700x...

Looks like image size is a bit smaller than it should it be? it is usually something like 1700x...

it's been 1300 for a while, i believe. but it's no issue to size up a bit if it looks too tiny

@elleobrien looks like your commits are not properly attributed?

@elleobrien looks like your commits are not properly attributed?

Yep yep gotta fix that. was playing with gitlab last night and messed with my global config :)


fix: make multi accounts menu item reusable and consume it in already existing menus

Description
Does what the title says out of the box, basically killed a few code duplicates by doing a reusable component to display the Multi Accounts menu item!
I didn't test it yet with a Ledger and a KeepKey as I don't have access to these devices for now

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
n/a

Risk

High Risk PRs Require 2 approvals
Low risk, easy to test, multi accounts should be in every menu it needs

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

Try native wallet, see if the item is shown in the menu
Try Ledger, see if the item is shown in the menu
Try Metamask with snap, see if the item is shown in the menu
Try Metamask without snap, see if the item is hidden in the menu
Try Keepkey, see if the item is hidden in the menu

Engineering

Operations

Screenshots (if applicable)

Can update DemoMenu to use the new component as well. And small naming nitpick: AccountsManagementMenuItem -> AccountManagementMenuItem, or if you want plural vernacular could go with ManageAccountsMenuItem as an alternative.

Can update DemoMenu to use the new component as well. And small naming nitpick: AccountsManagementMenuItem -> AccountManagementMenuItem, or if you want plural vernacular could go with ManageAccountsMenuItem as an alternative.

Thanks for the feedback, noticed a problem with multi accounts using demo wallet: https://github.com/shapeshift/web/issues/7047, I still added the item to the menu in this PR thought, but I'll open another PR to disable this button so it's not poluting the diff there!


Remove patch part from 3.1 moniker

Docs Build status updates of commit 517cecc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dotnet/xml/FrameworksIndex/msdata-sqlite-3.1.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Issue with remoteConfigs (localization + legacy) for updating users

Description
Hello! We are currently investigating an issue, which is as follows:
We have a paywall named test_1, which contains two identical remoteConfigs - one in With Localization (en default) and the other in Without Localization. The configs are 100% identical and valid.
We have another paywall named test_2, which contains one remoteConfig in With Localization (en default), identical to the two configs from test_1.
The problem is:
We have the first version of the app 1.0.0 (using "react-native-adapty": "2.2.1"), which works only with paywall test_1 and Legacy Without Localization Remote Config. Upon updating the app to version 1.0.1 (which uses "react-native-adapty": "2.4.6") and requesting paywall test_1 (getPaywall, locale en) - the remote config does not come through.
However, when requesting paywall test_2 (getPaywall, locale en) - the remote config comes through, and everything works.
If we install version 1.0.1 from scratch and request paywall test_1 (getPaywall, locale en) - the remote config comes through.
It seems that there is some issue with the paywall that was on the legacy remote config and the app transitioning from an older version of React Native to a newer one, where the paywall now utilizes a remote config with locale.
Version
v2.4.6
What platforms are you seeing the problem on?
iOS
System info
System:
    OS: macOS 13.4
    CPU: (8) arm64 Apple M1
    Memory: 49.70 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.1.0 - /var/folders/vg/cv8q3tzj1hdfjfd7t0v26vd80000gn/T/yarn--1686898500765-0.8989131801691097/node
    Yarn: 1.22.17 - /var/folders/vg/cv8q3tzj1hdfjfd7t0v26vd80000gn/T/yarn--1686898500765-0.8989131801691097/yarn
    npm: 9.6.4 - /opt/homebrew/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.12.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 14.3/14E222b - /usr/bin/xcodebuild
  Languages:
    Java: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0
    react-native: 0.70.6 => 0.70.6
    react-native-macos: Not Found

Hi! We were releasing UI library and now we're back! Diving into your question...

@snake302
So far, I was unable to get null (or any unexpected) value in our setup. Let me review how you see this problem:

You've created a paywall with a legacy config
You've added a localized config without bumping a paywall version. You also haven't deleted legacy config, so they both exist in paywall
In your app with newer SDK version (2.4.6) it causes config to return a nullable value instead of what you have set in a localized config field

Is that it?
You also opened your issue as an iOS problem — is this not a case with android or you just haven't tried that one?

We currently have a clue about the origin of this problem, allow me a little more time to confirm our suspicion.

Yeah, I'm afraid it is a problem with diffing paywall hashes across versions.
It is a backend/native problem, so it requires a little more time to repair.
I'll try to force this issue asap and will write you back, when native SDK will be ready to provide a fix to us
Thank you for noticing this problem!


Generate Parameter Library error in ROS2: FOXY

While building the pkg, I am getting an error related to Generate Parameter Library.
I have cloned a pkg for Generate Parameter Library from (https://github.com/PickNikRobotics/generate_parameter_library) in ros2setup.
After that, I am getting an error related to rsl-config. For more details, screenshot is attached.

Can anyone give any direction w.r.t to this error.
Thank you

Dear @pathakarvindk,
First of all, thank you very much for reaching us!
With regard to your issue, it seems that the wrong version of ros2_controllers has been imported:

The ROS2 Foxy version of ros2_controllers (and joint_state_broadcaster in this case) does not require generate_parameter_library to be installed in the machine.
The ROS2 Humble/Rolling version of ros2_controllers does.

I have checked in the README.md file and the instructions are wrong, it is the foxy branch of ros2_controllers the one that must be imported to our ros2setup repository. I have changed the instructions accordingly:
git clone https://github.com/ros-controls/ros2_controllers.git -b foxy

Thank you very much for raising the issue.
Best regards,
Mikel Bueno Viso
IFRA Group
Centre for Robotics and Assembly, Cranfield University, UK


Invalid or corrupted pad block issue while sharing a file with a new contact

Describe the bug
In atMospherePro when a new contact is added and a file is shared with the newly created contact, There's an Invalid or corrupted pad block issue
Steps to reproduce

First , clone the code from the branch "ui_redesign" branch of atMospherePro
Then Run the app and add a new contact
And then select the newly created contact and share a file

Expected behavior
There should not be any pad block exceptions
Screenshots
SEVERE|2023-06-09 16:09:01.607824|EncryptionUtil|Error while decrypting value: Invalid argument(s): Invalid or corrupted pad block
I/flutter (22587): WARNING|2023-06-09 16:09:01.611390|SyncService (@aquamarine659)|Exception occurred when setting conflict info for @banana75:shared_key@aquamarine659 | Exception: Invalid argument(s): Invalid or corrupted pad block
I/flutter (22587): FINER|2023-06-09 16:09:02.541007|SyncService (@aquamarine659)|Informing 2 listeners of SyncProgress{atSign: @aquamarine659, syncStatus: SyncStatus.success, isInitialSync: false, startedAt: 2023-06-09 10:39:00.025813Z, completedAt: 2023-06-09 10:39:02.539274Z, message: null, keyInfoList:[KeyInfo{key: senthistory_v2.mospherepro@aquamarine659, syncDirection: SyncDirection.remoteToLocal , conflictInfo: null, commitOp: CommitOp.UPDATE_ALL}, KeyInfo{key: @banana75:shared_key@aquamarine659, syncDirection: SyncDirection.remoteToLocal , conflictInfo: ConflictInfo{remoteValue: null, localValue: null, errorOrExceptionMessage: Exception occurred when setting conflict info for @banana75:shared_key@aquamarine659 | Exception: Invalid argument(s): Invalid or corrupted pad block}, commitOp: CommitOp.UPDATE_ALL}, KeyInfo{key: @banana75:shared_key@aquamarine659, syncDirection: SyncDirection.localToRemote , conflictInfo: null, commitOp: CommitOp.UPDATE_ALL}, KeyInfo{key: shared_key.banana75@aquamarine659, syncDirection: SyncDir
Smartphones

Device: [e.g. Samsung Galaxy]
OS: [e.g. Android]

Were you using an atApplication when the bug was found?
atmospherePro
Additional context
No response

Thanks for this @purnimavenkatasubbu . Looks like it shouldn't be impacting the app itself, can you confirm?
@sitaram-kalluri - we can see Exception occurred when setting conflict info for @Banana75:shared_key@aquamarine659 ... the exception is because it's trying to decrypt 'shared_key' using an AES key but shared_keys are encrypted using the RSA key. We should not be attempting to decrypt 'shared_key' records in the usual way. Can you look into a fix for this?

Thanks for this @purnimavenkatasubbu . Looks like it shouldn't be impacting the app itself, can you confirm?
@sitaram-kalluri - we can see Exception occurred when setting conflict info for @Banana75:shared_key@aquamarine659 ... the exception is because it's trying to decrypt 'shared_key' using an AES key but shared_keys are encrypted using the RSA key. We should not be attempting to decrypt 'shared_key' records in the usual way. Can you look into a fix for this?

Yes Gary, It's not impacting the app

Thanks for this @purnimavenkatasubbu . Looks like it shouldn't be impacting the app itself, can you confirm?
@sitaram-kalluri - we can see Exception occurred when setting conflict info for @Banana75:shared_key@aquamarine659 ... the exception is because it's trying to decrypt 'shared_key' using an AES key but shared_keys are encrypted using the RSA key. We should not be attempting to decrypt 'shared_key' records in the usual way. Can you look into a fix for this?

Sure Gary, Will fix this issue.


add the ability to retrive the policy root

This PR implements GetPolicyRoot that returns the package root name from the policy list.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 42 (0.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 22.123%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bundles.go
0
42
0.0%

Files with Coverage Reduction
New Missed Lines
%

bundles.go
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
298

Relevant Lines:
1347

💛  - Coveralls


Add high-level, synchronous version of extract

Rename Table#extract to Table#extract_job
Add high-level, synchronous version as Table#extract

[refs #1720]

@blowmage I rebased and fixed conflicts for this branch, and ran the newly-enabled extract and extract_job acceptance tests along with all other tests locally. All are passing.


SQL_ALCHEMY_DATABASE_URI ignored from Apache mod_wsgi

Version: 0.18.5
Platform: Ubuntu 16.04 Apache 2.4
(Probably related to #3223)
I have superset pip installed into a virtualenv living at /usr/local/superset. My superset_config.py file has
SQLALCHEMY_DATABASE_URI = 'sqlite:////usr/local/superset/superset.db'
For this test I'm using AUTH_TYPE = AUTH_DB and have created an admin user with fabmanager.
Superset is being run from Apache via mod_wsgi. However it is ignoring the superset_config.py file and looking for /var/www/.superset/superset.db. If it can't find it, it creates a new empty database. Which makes it impossible to login.

You need to have a module named superset_config in your PYTHONPATH, meaning if yo fire up an interpreter and import superset_config it should work.
In production at Airbnb we drop that file (superset_config.py) into a specific folder, and run export PYTHONPATH=~/thatfolder.
As you fire up your web server you should see something like this:

I do have a superset_config.py, it's in my PYTHONPATH. I know superset_config.py is being loaded when I do superset runserver.
But that's not the issue, I need it to work when run from Apache via mod_wsgi.
(And yes my virtualenv is being activated from Apache, because otherwise nothing would work at all.)

But is it in the Apache user's PYTHONPATH env?

@laranzu if you really need to use apache httpd you can use apache as http proxy for gunicorn, it may help making things easier to deploy for you.

My definition of "making things easier" would not be adding yet another layer of software (gunicorn) between Apache and Superset. Apache and WSGI have been around for many years because they work really well. I suggest that being able to deploy Superset "out of the box" in such systems is worth the effort.
Hacked around this issue for now.

My point is there's no issue to be worked around, it's just you are not passing the python path to httpd. Please open a PR to the doc with the proper httpd configuration to help other users with the same issue.


Error compiling egui-extras

I tried the new version of egui (0.28) but egui-extras seems to fail compiling with the following messages:
in `synthax_highlighting.rs
error[E0277]: the trait bound `CodeTheme: SerializableAny` is not satisfied
   --> /Users/linus/.cargo/registry/src/index.crates.io-6f17d22bba15001f/egui_extras-0.28.0/src/syntax_highlighting.rs:158:19
    |
158 |                 d.get_persisted(egui::Id::new("dark"))
    |                   ^^^^^^^^^^^^^ the trait `serde::ser::Serialize` is not implemented for `CodeTheme`, which is required by `CodeTheme: SerializableAny`
    |
    = note: required for `CodeTheme` to implement `SerializableAny`
note: required by a bound in `IdTypeMap::get_persisted`
   --> /Users/linus/.cargo/registry/src/index.crates.io-6f17d22bba15001f/egui-0.28.0/src/util/id_type_map.rs:397:29
    |
397 |     pub fn get_persisted<T: SerializableAny>(&mut self, id: Id) -> Option<T> {
    |                             ^^^^^^^^^^^^^^^ required by this bound in `IdTypeMap::get_persisted`

and in table.rs:
error[E0277]: the trait bound `TableState: SerializableAny` is not satisfied
   --> /Users/linus/.cargo/registry/src/index.crates.io-6f17d22bba15001f/egui_extras-0.28.0/src/table.rs:547:45
    |
547 |             .data_mut(|d| d.get_persisted::<Self>(state_id))
    |                             -------------   ^^^^ the trait `serde::ser::Serialize` is not implemented for `TableState`, which is required by `TableState: SerializableAny`
    |                             |
    |                             required by a bound introduced by this call
    |
    = note: required for `TableState` to implement `SerializableAny`
note: required by a bound in `IdTypeMap::get_persisted`
   --> /Users/linus/.cargo/registry/src/index.crates.io-6f17d22bba15001f/egui-0.28.0/src/util/id_type_map.rs:397:29
    |
397 |     pub fn get_persisted<T: SerializableAny>(&mut self, id: Id) -> Option<T> {
    |                             ^^^^^^^^^^^^^^^ required by this bound in `IdTypeMap::get_persisted`

My cargo.toml looks like this:
[dependencies]
eframe = { version = "0.28", features = ["persistence"] }
egui_extras = { version = "0.28" }
egui_plot = "0.28"
egui-phosphor = { git = "https://github.com/hacknus/egui-phosphor" }

And I'm using it on macOS 14.5.
egui-phosphor is bumped to egui 0.28 and works fine. the issue lies in egui_extras.

This seems to be an accidentally forced dependency on the "serde" feature. Enabling it resolves the issue, but it's supposed to be optional.

Workaround until this is fixed:
egui_extras = { version = "0.28.0", features = ["serde"] }

Adding this to Cargo.toml even works if it's not a direct dependency (required by egui_commonmark for example).

We should:
A) set up a CI step to catch this problem
B) only call get_persisted if the serde feature is enabled

The problem is actually in egui, not egui_extras. It happens if we try to build egui_extras without the serde feature while something else enabled the persistence feature in egui. This was previously not possible because serde was a mandatory dependency in egui_extras.
cargo build -p egui_extras --features egui/persistence

https://github.com/emilk/egui/blob/b31d02dd211755c80a761921c8d0a36986732d8a/crates/egui/src/util/id_type_map.rs#L38-L54
Enabling the feature causes the trait bounds to change in a semver breaking way, which should not happen because features are supposed to be additive. I don't know if there is a way to avoid this, though, aside from making serde mandatory in egui.

Good catch… yeah, if persistence is on for egui and serde is off for egui_extras, we will have this problem. Not easily solved if we want serde to be optional for egui_extras.

Good catch… yeah, if persistence is on for egui and serde is off for egui_extras, we will have this problem.
As a short-term solution I can make serde a default (opt-out) feature of egui_extras, so at least fewer people get bitten by this.

Wouldn't making the persistence feature  depend on egui_extras/serde also have worked? :no_mouth:  It would have created a bit less headache IMHO, and maybe it could even have been considered a "proper" solution, not just a short term one? :thinking:  Of course it's entirely possible that I'm just missing something that makes this not quite as simple...

egui/persistence cannot depend on egui_extras/serde, because egui_extras depends on egui

Ah, right, this is what I missed...

We should be able to fix this by only calling get_persisted/insert_persisted if #[cfg(feature = "serde")], and otherwise call get_temp/insert_temp

Is anyone working on this? I'm eagerly anticipating the new release.

We should be able to fix this by only calling get_persisted/insert_persisted if #[cfg(feature = "serde")], and otherwise call get_temp/insert_temp

If this is what has to be done anyway, then maybe get_persisted/insert_persisted in egui should be conditional on the persistence feature instead of having different trait bounds? That means each crate that uses egui would have to implement its own logic to call get_persisted or get_temp depending on its own enabled features.
This would be in accordance with the recommendation on https://doc.rust-lang.org/cargo/reference/features.html#feature-unification

A consequence of this is that features should be additive. That is, enabling a feature should not disable functionality, and it should usually be safe to enable any combination of features. A feature should not introduce a SemVer-incompatible change.

vergen recently made that change.
https://github.com/rustyhorde/vergen?tab=readme-ov-file#-notes-on-version-9-

If this is what has to be done anyway, then maybe get_persisted/insert_persisted in egui should be conditional on the persistence feature instead of having different trait bounds? That means each crate that uses egui would have to implement its own logic to call get_persisted or get_temp depending on its own enabled features.

The issue at hand occurs when egui:persistence is ON and egui_extras:serde is OFF.

Oh, was this the last open issue for the "Next Patch Release" milestone? :eyes:  ^^


multi line context nodes

I see that #316 changed the way multiline contexts are displayed.
I kind of liked the way lines were concatenated before, but I definitely see the appeal from a maintainer's perspective. So if someone would be willing to introduce a configuration option that would make things work like before, that would be awesome.
Also maybe an option to limit the number of contexts, in addition to the number of lines (max_lines) would be nice.

I would also like to have it in a single line. In Python the formatter always makes it into a multiple line, but personally I find it much more concise with 1 line as the context.

Sorry not happening.