Ingest all the data from the metadb into clickhouse

@FedericoCeratto mentioned it's possible to do this using the notes on the pad
Namely:
psql -h<IP_ADDRESS>  metadb -p 5432 -U readonly -c "COPY (select * from measurement where measurement_start_time > '2019-01-01') TO STDOUT " | pv | gzip | ssh<EMAIL_ADDRESS>"cat > measurement.gzip"

What I need in order to make the most use of the clickhouse deployment is all OONI data from the beginning of time (MVP is beginning of 2018) for the following tables:
measurement
domain_input
citizenlab
report
http_verdict
http_request
dns_a
Here is a sample query I use for data analysis which shows some of the columns which are most useful to me:
SELECT
  measurement.measurement_start_time AS measurement_start_time,
  measurement.anomaly,
  measurement.confirmed,
  report.report_id,
  report.probe_cc,
  report.probe_asn,
  report.test_name,
  measurement.test_runtime,
  domain_input.input,
  domain_input.domain,
  citizenlab.cc,
  citizenlab.category_code,
  http_verdict.blocking,
  http_verdict.http_experiment_failure,
  http_verdict.dns_experiment_failure,
  http_verdict.control_failure,
  http_request.body_simhash,
  http_request.body_sha256,
  dns_a.test_ip,
  dns_a.client_resolver,
  dns_a.control_ip
FROM measurement
JOIN domain_input ON domain_input.input_no = measurement.input_no
JOIN citizenlab ON citizenlab.url = domain_input.input
JOIN report ON report.report_no = measurement.report_no
JOIN http_verdict ON http_verdict.msm_no = measurement.msm_no
JOIN http_request ON http_request.msm_no = measurement.msm_no
JOIN dns_a ON dns_a.msm_no = measurement.msm_no

This has been done


Food package update to term env_samp_device

Additional context
FDA and OHE alignment work suggested "env_samp_device" be changed to "sampling_device"

"env_samp_device" is not a term we included in the final version, and I cant seem to find the relevant MIXS ID that it refers to, so I'm not sure this term is even meant to be included. We probably discussed it and suggested the general term "samp_collec_device" MIXS:0000002 from the core was to be used instead. In which case its a no, we cannot change the name.

'environmental sampling device' -- to deal with swabs
-- check food pack for this term.
--- 'sampling device'  --> needed for food facility
-- as a foodon term
--> followup with Chris Grim.

samp_collect_device (MIXS:0000002) is already included in the food-farm environment and food-human food packages.
It is in food-farm twice -- need to remove one row.

removed duplicate row from v6 spreadsheet - "MIXS6 packages Final_clean"


fix (elements-dev-portal): anchor tags stripped from uri

Addresses #8606
Anchor tags were not appended to links if those links were pointing to another document. Links are now appended, but scrolling to the anchor position is not working. This seems to be a known bug when using react-router-dom:
https://github.com/remix-run/react-router/issues/394#issuecomment-220221604
To test:
Option 1:

Checkout branch
Create two articles. In one article, create a top header and a bottom header located somewhere else down the page.
In your second article, link to the top header and the bottom header.
You will notice the anchor tags are appended to the outbound links, but the scrolling to the anchor position is not working

https://user-images.githubusercontent.com/52048026/141879149-60a7b490-56f6-417c-a4bc-2d75f7090e9f.mov
Option 2:

Checkout branch:
CD into packages/elements-dev-portal and run yarn storybook
Select NodeContent/Create Todo
Use the following information in the Controls section to the right:

nodeSlug: ZG9jOjg3NDE4NA-article-two
projectId: cHJqOjExNzIxMg
platformUrl: https://dojo-stg-v2.stoplight.io

You will notice the links have the anchor tags, but the links are not clickable
https://user-images.githubusercontent.com/52048026/141879186-1e2103d2-a152-482e-a91c-91ff8cc99c4e.mov

@Nezteb , as @mallachari pointed out, the issue may not be with needing to use react-router-hash-link. The H1 header and H4-6 are not creating anchor links. The video shown is from STG and obviously doesn't have any of the commits from this PR.
https://user-images.githubusercontent.com/52048026/142477817-964920e8-bf4a-430b-9f05-642976483f99.mov

https://user-images.githubusercontent.com/52048026/142478793-f4b912e3-be01-4a2c-bb6c-f977c2b408dd.mov

@Nezteb @mallachari : Can you kindly review this thread and let me know if this PR is complete?
https://stoplight-internal.slack.com/archives/C028M2ACATY/p1637262268276600


Why are the same CT images displayed differently in older Cornerstone than in Cornerstone 3D?

HI，I have a problem I don't know how to solve. Can someone help me solve it? tks!!!
Display effect on old Cornerstone（This is the right effect）：

Display effect on new Cornerstone3D（This is the wrong effect）：

Same image loader: cornerstoneWADOImageLoader
Scheme: dicomweb
Same windowCenter: 68
Same windowWidth: 385

为啥用3D，我看一下子就崩溃了

您的邮件已经收到

为啥用3D，我看一下子就崩溃了

还好吧，新版的架构比旧版还是好的，配合example和源码看就好

Can you try it again, there has been a potential fix for this here https://github.com/cornerstonejs/cornerstone3D-beta/commit/d36a23a4eaf5bafcc8dddc0ab796065098df616a

I upgraded to 0.10.0, but it was not resolved, there is no change

Can you try it again, there has been a potential fix for this here d36a23a
I upgraded to 0.10.0, but it was not resolved, there is no change

which viewport are you using? StackViewport or VolumeViewport?

which viewport are you using? StackViewport or VolumeViewport?

StackViewport

can you share the data (If the DICOM data does not have patient information (anywhere in the header etc.) nor baked in in the display, so no PHI at all)

can you share the data (If the DICOM data does not have patient information (anywhere in the header etc.) nor baked in in the display, so no PHI at all)

Download this file dicomLink

Doesn't download

Doesn't download

Sorry, I gave you a temporary links, I will give you a new link。download

It doesn't work either

It doesn't work either

I cannot upload the file directly through Github, so I can only choose to send it to you by email. I am sorry for delaying your time。

@FedWithMori maybe you can try:
cornerstoneWADOImageLoader.configure({
  // ...
  decodeConfig: {
    convertFloatPixelDataToInt: false, // 👈 set this to false
  },
});

// ...

@FedWithMori maybe you can try:
cornerstoneWADOImageLoader.configure({
  // ...
  decodeConfig: {
    convertFloatPixelDataToInt: false, // 👈 set this to false
  },
});

// ...

That's how it was set up from the start, and it doesn't solve the problem

各位解决了吗

您的邮件已经收到

这个问题解决了吗

Can you try drag and drop your image in our new demo https://www.cornerstonejs.org/live-examples/local.html

应该是数据类型的问题 我用的volume视口 用的cornerstoneWADOImageLoader解析的dicom 它解析出来的pixelData是Unit16Array
而cornerstone3d需要的是 Unit8Array 或者 Float32Array 我改了这个代码就好了

应该是数据类型的问题 我用的volume视口 用的cornerstoneWADOImageLoader解析的dicom 它解析出来的pixelData是Unit16Array 而cornerstone3d需要的是 Unit8Array 或者 Float32Array 我改了这个代码就好了

牛逼！！！

Can you try drag and drop your image in our new demo https://www.cornerstonejs.org/live-examples/local.html

您可以尝试在我们的新演示中拖放您的图像吗https://www.cornerstonejs.org/live-examples/local.html

我qq加你好友了 麻烦通过一下，有点问题想咨询一下

can you see if your problem is fixed now?

can you see if your problem is fixed now?

When I use the demo you provided, the display is normal, but my local project after upgrading dependence, the display error.
Demo:

My local project:

Dependence：

update your wado image loader as well

update your wado image loader as well

Hmm, so couple of things, nuke the package.json lock or yarn lock and delete node modules (maybe that fixes it). If not are you registering a custom metadata provider in the app?


Missing images for some German Pokemon cartridges

I noticed that the images for 2 of my German pokemon cartridges are missing from the library (Though it does have the one for German Pokemon Red, so it's not that all of them are missing.)
They seem to be correctly present in both the dat database as well as the libretro thumbnail db, so I don't know why they would be missing? ( I can't run the tooling myself unfortunately as I don't have access to a Windows machine)
Release version of the sample image pack
1.2
Additional context
These are the missing cartridges/images:
DAT entry: https://datomatic.no-intro.org/index.php?page=show_record&s=23&n=2159
Boxart: https://github.com/libretro-thumbnails/Nintendo_-_Game_Boy_Advance/blob/17c74d9d2529bc79b7036417f3ee4794de964438/Named_Boxarts/Pokemon - Smaragd-Edition (Germany).png
DAT entry: https://datomatic.no-intro.org/index.php?page=show_record&s=47&n=0909
Boxart: https://github.com/libretro-thumbnails/Nintendo_-_Game_Boy_Color/blob/d794278a15e9b21a82cf72572580b947be2479ce/Named_Boxarts/Pokemon - Kristall-Edition (Germany).png

So a couple things are going on here:

Kristall is not in the DAT file I used to generate the last sample pack, which are only a few months old. Not sure why that is since it has a dump date of 2019, but I don't know how long it takes DAT-O-MATIC to verify titles.
Smargd is in the DAT file however, and seems to use the same name in the libratro-thumbnails filename, so not sure why that didn't make it in.

I'll take a look at both of these when I get some time in the coming weeks.

I did just re-download a GBA DAT file a few minutes ago to check on Kristall's status, and Kristall is not in the DAT file. As the tool works now, the title needs to be present in the DAT file to get the CRC ID.
I will probably get to addressing the issue with Smargd first before figuring out the best solution to handle cases where a ROM doesn't have an entry in the DAT file generated by DAT-O-MATIC but saw a legitimate retail release. At least there is a database entry with the CRC available if I need to brute force it, but I'd like to avoid that route in the tool if possible.
Can you put your Kristall cartridge in your Pocket, load the game and then quit the cartridge, and go to the following menu option to send me the full checksum of the cart ROM?
Tools > User Service > Get Cart Signature
This feature seems spotty to me, but in my testing it should give you the CRCs of the last cart you loaded, which is why I ask you to load and quit the game before trying to obtain it. It would be useful to know your cart matches the ROM in the database.

Nevermind, it's late for me and I think I need some sleep 😄
I checked Kristall against my GBA DAT, not the GBC DAT. It's in the GBC DAT, so it's likely the same problem that Smargd has. I should be able to get to investigating in the next couple of weeks as things slow down for the holidays.

Hello there,
any updates on that issue?


gitui: fix darwin build

Motivation for this change
Fixes:
  = note: ld: warning: passed two min versions (10.12.0, 10.12) for platform macOS. Using 10.12.
          ld: framework not found AppKit
          clang-7: error: linker command failed with exit code 1 (use -v to see invocation)

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build gitAndTools.gitui


devtools/scripts/create_conda_env.py does not report which channels packages are installed from

We've been converting some of our legacy projects over to the CMS cookiecutter, but I've noticed that the new travis scheme can make debugging harder because the devtools/scripts/create_conda_env.py mechanism does not emit information on which channels each package is installed from. When tracking down issues where pulling a package from a different channel causes failures, this can be immensely valuable.
What would you think about one of these options?

Having devtools/scripts/create_conda_env.py generate a list of which channels each package version is coming from (the same way conda install <packagename> does), or
Adding a conda list to the .travis.yml?

conda list --show-channel-urls is invaluable, imo.

will satisfy 1) here?

A conda list was accidentally omitted. @jaimergp can you add this to the GHA switch over?

Yes, (2) would work well!

Two items 1) create_conda_env.py is deprecated in favor of the more stable setup-miniconda action and 2) a Conda-list is emitted during the GHA step. Closing, but please reopen if needed.


Feat: Redesign services page

Describe the feature
The current services page is lack of images and user experience. I would like to design the services page as below.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@DharshiBalasubramaniyam You can add more images but don't redesign it much

@DharshiBalasubramaniyam Issue assigned to you


sriov controller

This PR introduces SRIOV controller, please see README.md included for more details.
Signed-off-by: Serguei Bezverkhi<EMAIL_ADDRESS>

@mestery either way works for me, I think if we decide for another repo, I would vote for a repo called controllers and then inside srio-controller in its own folder. Alternatively I could drop existing Makefile and use the one from nsm. I used separate Makefile juts as a convenience and do not really need it after integrating with nsm. Please let me know how you want me to proceed.

If the intent is to integrate with the broader build, I'm fine leaving this inside. In fact, I know you're on vacation so let me know and I can work to get this building with our Makefile and push some changes to your branch here. I've spent an inordinate amount of time on our Makefiles in the past week so am vastly familiar with those intricacies now. :)

@edwarnicke Yup, agreed, I'll help @sbezverk get this hooked into our existing build infrastructure, as I don't want us to have disparate build infra hanging around the tree, it's too high of a cost to maintain.

@mestery sounds good, I can drop all building pieces from this PR and you should be able to merge it as since I have it working in ,my test bed.  I had bad experience with multiple people committing to the same branch and prefer not to do it if you do not mind :)

@sbezverk OK, I'll review the code and I can help hook it into the build as a separate PR. It's times like these I miss Gerritt TBH.

@sbezverk What is the status of this patch? Did you want my help integrating this into the top-level build as I suggested?

@mestery I am still waiting for a code review, changing scripts for building process can be done quickly. As soon as the code in general is accepted I will deal with building. Also since there is no way at least for now to test is in CI, I am not sure if it should or not be merged.

@sbezverk I looked at the latest, and you appear to have removed the Makefile, but did not hook this up into the top-level build system yet. Is that the case?
Also, we really need to sort out how we can test this, because we can't do it with travis-ci and I know we've hit issues with packet.net so far. Until that's decided, we need a way to mark this code as untested and experimental so unsuspecting people who fork this repository understand it's state.

@mestery that is why I was not sure about merging it into networkservice mesh, I continue working on it in my personal repo, I guess once CI starts supporting it, it can be merged.
@edwarnicke what do you think?

@mestery Please let me know if there is anything outstanding for this PR. Thanks a lot.

@mestery PTAL, comments are addresse

I received the same errors as your build warning commits in the Dependabot PR, so unsure if we need those or not. Otherwise, this looks good, so once the build failure due to travis is fixed, I'll merge this @sbezverk. Thanks!

Same build failure as #267, clearly a travis-ci issue of some sorts, working to figure out why now.

Lets propose the fix for the build error as a separate PR please. Thanks!

@mestery Finally all green, PTAL.

@mestery client image is just for an example and testing, most likely people will use completely different images to run their actual applications.


Scroll event is trigger while horizontal scroll moving from let to right . it should not trigger scroll event.

Bug, feature request, or proposal:
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

Closing this issue as it does not follow the issue template. Please file a new issue that follows the template, which gives the team the information needed to investigate.


readme error?

what do you mean with this?
ssh cointop.sh

did you mean this?
sh cointop.sh

It's a server anyone can ssh into to try cointop
https://twitter.com/cointop/status/1330961389951729669?s=20

Added a clarification to README about this being an online instance. #273

wooow, soo cool.
its a domain name with ip address (https://cointop.sh/). my bad. sorry for this issue.


fix: renamed TxInput to Utxo

Utxo makes more sense as name of the tx input

Utxo makes more sense as name of the tx input

I agree!


Pending balance network error. Balance appear and disappear.

Hello,
After logging into my server i saw the balance showing 0 and a network error. I can sometime refresh the balance and it show the correct amount but it disappear some minutes later then i had to refresh again. I guess the connection is stable as i am using a vultr instance.

DeFi Wallet Version: 2.3.3
Operating System (OS): Windows server 2016

Attached logs and screenshot.

log.log
Thanks in advance.

Hi @Faucet1313 , make a backup for your wallet.dat just in case. Not sure if it's due to the minimum specification requirements. Please give us time to investigate this issue.

Hi @Faucet1313 , checked with the team, it's either due to the vultr VPS or your system lost connection.

Thanks for checking my issue. It is a dedicated server, If i lost connection and i can connect to my server why the Defichain client can't reconnect too?

Same issue with 2 different hosting and locations each server respect the minimum specification requirements and both running Windows server 2016. This time in the new server i saw that when i got this error "Pending balance failure" i can't connect to internet with firefox or internet explorer except if i close the defichain client so i tried to disable firewall, defender... But no success. I found an event that match the time of the balance error and i found this:

Hi @Faucet1313 , could you send your feedback to  Network ERROR at new wallet 2.3.4, we can further discuss on the issue there. We would like to keep same issues in one thread. Thank you.


fix: disabled date picker triggers

Closes: #815

Hey! I was debugging some issue related to trigger not being disabled.
Happy to see it's fixed already! :fire:


Predictions in dataset and .csv downloaded only contains the predictions with no related features used when predicting

Predictions .csv download only contains the predictions with no related features used when predicting.
We probably would want to have the features used for each prediction in the predictions dataset and downloaded .csv.
To anyone trying this feature, feel free to provide your feedback and thoughts about it in this issue's discussion thread.

with the predictions currently, without the additional features added, is there a way to link them back to the true result?
I can get the binned data from the output file, look at the errors, but it would be good to get the true value for each predicted value individually. Having additional input features would be valuable as well.
with regard to the binned data results... are the bin_errors average for the bin (assuming so) vs total error for the bin?


append option values

Is it possible to pass in the same option and have all the values captures instead of the last one? Similar to the action='append' in argparse.
example:
--foo bar --foo baz
value of foo should be ['bar', 'baz']
not just 'baz'
Thanks

the 'multiple' argument does what I need.


syntax error, unexpected token ")" on shared host

Describe the bug
Hi, I am facing this issue when deploying laravel 8 on a shared host (I know, bad practice, but still trying to keep this project as cheap as possible 😅). This package works amazingly on local env, ty for providing it 😄 .
That being said, here are some specs:

I am using altervista as a free shared host, it runs an optimized version of PHP 8.0.22 (checked with dd(phpversion());). I had to make some compromises like using laravel v8 instead of v9, cannot using SMTP, etc. so I do not exclude could be an issue related to the env PHP version.
On my local, it runs PHP 8.1.12 and has no issue with this package. I sent some cloud messages to topics and reported no errors. I do not see messages on the firebase console, but I read it takes a while to show them.

If you think this could be related to the platform I am using, I will post directly to their forum.
Thanks for your patience and your amazing work 😄.
Installed packages
{
    "name": "laravel/laravel",
    "type": "project",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "require": {
        "php": "^7.3|^8.0",
        "fruitcake/laravel-cors": "^2.0",
        "guzzlehttp/guzzle": "^7.0.1",
        "kreait/laravel-firebase": "^4.2",
        "laravel/framework": "^8.75",
        "laravel/sanctum": "^2.11",
        "laravel/tinker": "^2.5",
        "php-open-source-saver/jwt-auth": "^2.0",
        "spatie/laravel-permission": "^5.7"
    },
    "require-dev": {
        "facade/ignition": "^2.5",
        "fakerphp/faker": "^1.9.1",
        "knuckleswtf/scribe": "^4.6",
        "laravel/sail": "^1.0.1",
        "mockery/mockery": "^1.4.4",
        "nunomaduro/collision": "^5.10",
        "phpunit/phpunit": "^9.5.10"
    },
    "autoload": {
        "psr-4": {
            "App\\": "app/",
            "Database\\Factories\\": "database/factories/",
            "Database\\Seeders\\": "database/seeders/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "scripts": {
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ],
        "post-update-cmd": [
            "@php artisan vendor:publish --tag=laravel-assets --ansi --force"
        ],
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi"
        ]
    },
    "extra": {
        "laravel": {
            "dont-discover": []
        }
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

PHP version and extensions
This is my local env composer show --platfom:
composer               2.4.4    Composer package
composer-plugin-api    2.3.0    The Composer Plugin API
composer-runtime-api   2.2.2    The Composer Runtime API
ext-bcmath             8.1.12   The bcmath PHP extension
ext-bz2                8.1.12   The bz2 PHP extension
ext-calendar           8.1.12   The calendar PHP extension
ext-ctype              8.1.12   The ctype PHP extension
ext-curl               8.1.12   The curl PHP extension
ext-date               8.1.12   The date PHP extension
ext-dba                8.1.12   The dba PHP extension
ext-dom                20031129 The dom PHP extension
ext-exif               8.1.12   The exif PHP extension
ext-ffi                8.1.12   The FFI PHP extension
ext-fileinfo           8.1.12   The fileinfo PHP extension
ext-filter             8.1.12   The filter PHP extension
ext-ftp                8.1.12   The ftp PHP extension
ext-gd                 8.1.12   The gd PHP extension
ext-gettext            8.1.12   The gettext PHP extension
ext-gmp                8.1.12   The gmp PHP extension
ext-hash               8.1.12   The hash PHP extension
ext-iconv              8.1.12   The iconv PHP extension
ext-intl               8.1.12   The intl PHP extension
ext-json               8.1.12   The json PHP extension
ext-ldap               8.1.12   The ldap PHP extension
ext-libxml             8.1.12   The libxml PHP extension
ext-mbstring           8.1.12   The mbstring PHP extension
ext-mysqli             8.1.12   The mysqli PHP extension
ext-mysqlnd            0        The mysqlnd PHP extension (actual version: mysqlnd 8.1.12)
ext-odbc               8.1.12   The odbc PHP extension
ext-openssl            8.1.12   The openssl PHP extension
ext-pcntl              8.1.12   The pcntl PHP extension
ext-pcre               8.1.12   The pcre PHP extension
ext-pdo                8.1.12   The PDO PHP extension
ext-pdo_dblib          8.1.12   The pdo_dblib PHP extension
ext-pdo_mysql          8.1.12   The pdo_mysql PHP extension
ext-pdo_odbc           8.1.12   The PDO_ODBC PHP extension
ext-pdo_pgsql          8.1.12   The pdo_pgsql PHP extension
ext-pdo_sqlite         8.1.12   The pdo_sqlite PHP extension
ext-pgsql              8.1.12   The pgsql PHP extension
ext-phar               8.1.12   The Phar PHP extension
ext-posix              8.1.12   The posix PHP extension
ext-pspell             8.1.12   The pspell PHP extension
ext-readline           8.1.12   The readline PHP extension
ext-reflection         8.1.12   The Reflection PHP extension
ext-session            8.1.12   The session PHP extension
ext-shmop              8.1.12   The shmop PHP extension
ext-simplexml          8.1.12   The SimpleXML PHP extension
ext-soap               8.1.12   The soap PHP extension
ext-sockets            8.1.12   The sockets PHP extension
ext-sodium             8.1.12   The sodium PHP extension
ext-spl                8.1.12   The SPL PHP extension
ext-sqlite3            8.1.12   The sqlite3 PHP extension
ext-sysvmsg            8.1.12   The sysvmsg PHP extension
ext-sysvsem            8.1.12   The sysvsem PHP extension
ext-sysvshm            8.1.12   The sysvshm PHP extension
ext-tidy               8.1.12   The tidy PHP extension
ext-tokenizer          8.1.12   The tokenizer PHP extension
ext-xml                8.1.12   The xml PHP extension
ext-xmlreader          8.1.12   The xmlreader PHP extension
ext-xmlwriter          8.1.12   The xmlwriter PHP extension
ext-xsl                8.1.12   The xsl PHP extension
ext-zend-opcache       8.1.12   The Zend OPcache PHP extension
ext-zip                1.19.5   The zip PHP extension
ext-zlib               8.1.12   The zlib PHP extension
lib-bz2                1.0.8    The bz2 library
lib-curl               7.86.0   The curl library
lib-curl-libssh2       1.10.0   curl libssh2 version
lib-curl-zlib          1.2.11   curl zlib version
lib-date-timelib       2021.17  date timelib version
lib-date-zoneinfo      2022.4   zoneinfo ("Olson") database for date
lib-fileinfo-libmagic  540      fileinfo libmagic version
lib-gd                 2.3.3    The gd library
lib-gmp                6.2.1    The gmp library
lib-icu                71.1     The ICU unicode and globalization support library
lib-icu-cldr           41       ICU CLDR project version
lib-icu-unicode        14.0.0   ICU unicode version
lib-ldap-openldap      2.6.3    OpenLDAP version of ldap
lib-libsodium          1.0.18   The libsodium library
lib-libxml             2.9.13   libxml library version
lib-libxslt            1.1.35   The libxslt library
lib-libxslt-libxml     2.9.13   libxml version libxslt is compiled against
lib-mbstring-libmbfl   1.3.2    mbstring libmbfl version
lib-mbstring-oniguruma 6.9.8    mbstring oniguruma version
lib-openssl            <IP_ADDRESS> OpenSSL 1.1.1s  1 Nov 2022
lib-pcre               10.40    The pcre library
lib-pcre-unicode       14.0.0   PCRE Unicode version support
lib-pdo_pgsql-libpq    15.0     libpq for pdo_pgsql
lib-pdo_sqlite-sqlite  3.39.4   The pdo_sqlite-sqlite library
lib-sqlite3-sqlite     3.39.4   The sqlite3-sqlite library
lib-zip-libzip         1.9.2    The zip-libzip library
lib-zlib               1.2.11   The zlib library
php                    8.1.12   The PHP interpreter
php-64bit              8.1.12   The PHP interpreter, 64bit
php-ipv6               8.1.12   The PHP interpreter, with IPv6 support

Steps to reproduce the issue.
Error message/Stack trace
{
    "message": "syntax error, unexpected token \")\"",
    "exception": "ParseError",
    "file": "<my-project-root)>/vendor/symfony/cache/Adapter/AbstractAdapter.php",
    "line": 138,
    "trace": [
        {
            "file": "<my-project-root)>/vendor/composer/ClassLoader.php",
            "line": 428,
            "function": "Composer\\Autoload\\includeFile"
        },
        {
            "file": "<my-project-root)>/vendor/symfony/cache/Adapter/Psr16Adapter.php",
            "line": 24,
            "function": "loadClass",
            "class": "Composer\\Autoload\\ClassLoader",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/composer/ClassLoader.php",
            "line": 571,
            "function": "include"
        },
        {
            "file": "<my-project-root)>/vendor/composer/ClassLoader.php",
            "line": 428,
            "function": "Composer\\Autoload\\includeFile"
        },
        {
            "file": "<my-project-root)>/vendor/kreait/laravel-firebase/src/FirebaseProjectManager.php",
            "line": 98,
            "function": "loadClass",
            "class": "Composer\\Autoload\\ClassLoader",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/kreait/laravel-firebase/src/FirebaseProjectManager.php",
            "line": 33,
            "function": "configure",
            "class": "Kreait\\Laravel\\Firebase\\FirebaseProjectManager",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/kreait/laravel-firebase/src/ServiceProvider.php",
            "line": 58,
            "function": "project",
            "class": "Kreait\\Laravel\\Firebase\\FirebaseProjectManager",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Container/Container.php",
            "line": 873,
            "function": "Kreait\\Laravel\\Firebase\\{closure}",
            "class": "Kreait\\Laravel\\Firebase\\ServiceProvider",
            "type": "::"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Container/Container.php",
            "line": 758,
            "function": "build",
            "class": "Illuminate\\Container\\Container",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Application.php",
            "line": 851,
            "function": "resolve",
            "class": "Illuminate\\Container\\Container",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Container/Container.php",
            "line": 694,
            "function": "resolve",
            "class": "Illuminate\\Foundation\\Application",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Application.php",
            "line": 836,
            "function": "make",
            "class": "Illuminate\\Container\\Container",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php",
            "line": 119,
            "function": "make",
            "class": "Illuminate\\Foundation\\Application",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/app/Http/Services/FirebaseService.php",
            "line": 13,
            "function": "app"
        },
        {
            "file": "<my-project-root)>/app/Http/Controllers/NewsController.php",
            "line": 149,
            "function": "sendMessageToTopic",
            "class": "App\\Http\\Services\\FirebaseService",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/app/Http/Controllers/NewsController.php",
            "line": 134,
            "function": "sendFirebaseCloudMessage",
            "class": "App\\Http\\Controllers\\NewsController",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Controller.php",
            "line": 54,
            "function": "store",
            "class": "App\\Http\\Controllers\\NewsController",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php",
            "line": 45,
            "function": "callAction",
            "class": "Illuminate\\Routing\\Controller",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Route.php",
            "line": 262,
            "function": "dispatch",
            "class": "Illuminate\\Routing\\ControllerDispatcher",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Route.php",
            "line": 205,
            "function": "runController",
            "class": "Illuminate\\Routing\\Route",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
            "line": 721,
            "function": "run",
            "class": "Illuminate\\Routing\\Route",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 128,
            "function": "Illuminate\\Routing\\{closure}",
            "class": "Illuminate\\Routing\\Router",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/spatie/laravel-permission/src/Middlewares/PermissionMiddleware.php",
            "line": 24,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Spatie\\Permission\\Middlewares\\PermissionMiddleware",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Auth/Middleware/Authenticate.php",
            "line": 44,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Auth\\Middleware\\Authenticate",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/app/Http/Middleware/ForceJson.php",
            "line": 25,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "App\\Http\\Middleware\\ForceJson",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php",
            "line": 50,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Routing\\Middleware\\SubstituteBindings",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Middleware/ThrottleRequests.php",
            "line": 127,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Middleware/ThrottleRequests.php",
            "line": 103,
            "function": "handleRequest",
            "class": "Illuminate\\Routing\\Middleware\\ThrottleRequests",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Middleware/ThrottleRequests.php",
            "line": 55,
            "function": "handleRequestUsingNamedLimiter",
            "class": "Illuminate\\Routing\\Middleware\\ThrottleRequests",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Routing\\Middleware\\ThrottleRequests",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 103,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
            "line": 723,
            "function": "then",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
            "line": 698,
            "function": "runRouteWithinStack",
            "class": "Illuminate\\Routing\\Router",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
            "line": 662,
            "function": "runRoute",
            "class": "Illuminate\\Routing\\Router",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
            "line": 651,
            "function": "dispatchToRoute",
            "class": "Illuminate\\Routing\\Router",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",
            "line": 167,
            "function": "dispatch",
            "class": "Illuminate\\Routing\\Router",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 128,
            "function": "Illuminate\\Foundation\\Http\\{closure}",
            "class": "Illuminate\\Foundation\\Http\\Kernel",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",
            "line": 21,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php",
            "line": 31,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Middleware\\ConvertEmptyStringsToNull",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",
            "line": 21,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php",
            "line": 40,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Middleware\\TrimStrings",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php",
            "line": 27,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php",
            "line": 86,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Middleware\\PreventRequestsDuringMaintenance",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/fruitcake/laravel-cors/src/HandleCors.php",
            "line": 52,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Fruitcake\\Cors\\HandleCors",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php",
            "line": 39,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 167,
            "function": "handle",
            "class": "Illuminate\\Http\\Middleware\\TrustProxies",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",
            "line": 103,
            "function": "Illuminate\\Pipeline\\{closure}",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",
            "line": 142,
            "function": "then",
            "class": "Illuminate\\Pipeline\\Pipeline",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",
            "line": 111,
            "function": "sendRequestThroughRouter",
            "class": "Illuminate\\Foundation\\Http\\Kernel",
            "type": "->"
        },
        {
            "file": "<my-project-root)>/index.php",
            "line": 52,
            "function": "handle",
            "class": "Illuminate\\Foundation\\Http\\Kernel",
            "type": "->"
        }
    ]
}

Additional information
No response

I think the problem might be that you are doing the composer install on your local computer and then push everything, including the vendor directory, to the remote host.
If my assumption is correct, you should be able to resolve this by adding
"platform": {
    "php": "8.0.22"
}

to the config section and then do a composer update -W (perhaps delete the vendor directory beforehand, just to be sure).
I hope this resolves the issue! 🤞🏻
Concerning the messages not showing up in the Firebase console: only messages sent from the console show up there, messages sent from backends unfortunately don't.
Let me know if it works!

Syntax errors are almost always a sign that code targeted at newer PHP versions is executed in an environment with an older PHP version.

Ty for your response! I'll give it a try as soon as possible and reach back to give you feedback 😄

Hi, @jeromegamez giving the target platform actually works 🎉 . Thank you so much for the support even if it was not a package bug related. Closing the issue 😄


Remote Site Setting Installed Getting SF Metadata API Connection Error

Hello,
I installed the DLRS in my Saleforce DEV Org.
From the package on the Welcome page I clicked on the Create/Update Remote Site Setting.
When I go to Manage Lookup Rollup Summaries -  get error "Salesforce Metadata API connection failure, click the link below to configure."
Does anyone know how can I fix this error?
Thank you

Looking back at release updates, it looks like you might not need to take this step anymore?  Ref:  https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/925

Yes @NikaPesic if you are in an org that is using My Domain feature you don't need to worry about this. Try installing latest package version as well - as I made quite a bit of updates to this logic in the last release. ANdy.


Multiple fiBackupSceneStorage objects being created in scenes.

Some changes in recent Unity patches have caused the following error to occur far mare than it used to:

The referenced script on this Behaviour (Game Object 'fiBackupSceneStorage') is missing!

I see the following message several times whenever I resolve all compiler errors in the Unity editor and Unity finishes recompiling all the scripts:

CheckConsistency: GameObject does not reference component MonoBehaviour. Fixing.

Once that occurs I know I'm going to start seeing one more "referenced script" error when I run the scene.  Using the "View all scene gameobjects" tool I can see there are multiple "fiBackupSceneStorage" objects, one with the "fiStorageComponent" script and the rest with a missing component.
It looks like a new "fiStorageComponent" object is created each time all compile errors get resolved.  I don't recall Full Inspector behaving this way before so I suspect it has something to do with changes in one of the patched releases and that this behavior will eventually make its way into the main branch.  Currently I'm using Unity 5.3.5f5 and Full Inspector 2.6.3 .

Okay, I'll take a look at this early next week. I might have to just disable the scene storage all together and figure out a different approach.

I'm getting loads of these errors as well. I went so far as to remove FullInspector from my project, but I was still seeing them. It turns out they some how got saved with a bunch of my scenes, and I had to use an editor script to reveal them so I could delete them -- figuring all that out took the better part of an afternoon. I would vote for trying another approach.

I've modified the script so the empty/null behaviors are automatically cleaned up. Please try out the new build from access and let me know if it works. Thanks!

Using build "FullInspector-2.6.4 (07-07-2016 at 2122PM)" I'm seeing this problem more than ever.  Maybe it was my steps?

Delete the FullInspector2 folder
Delete the fiBackupStorage and fiPersistentEditorStorage prefabs in the FullInspector2_Generated folder
Delete all references to those prefabs in my scene
Imported both packages in the zip
Restarted Unity

Now whenever I load my scene it gets two objects with missing scripts, fiPersistentEditorStorage and fiBackupSceneStorage.  If I delete those objects from my scene, save, then reload the scene the objects come back and with missing scripts.

@FodderMK The invisible objects are saved in your scenes.
In order to see them, you need to put this script in Assets/Editor. Then you'll see a new menu in the Unity Editor: Tools -> HiddenObjectExplorer.
This opens a window showing all the objects in your scene and their hidden flags. It is very important that you not mess with SceneLight, SceneCamera, PreRenderLight, PreRenderCamera, HandlesGO or anything else that are Unity generated.
The objects you are looking for are fiPersistentEditorStorage and fiBackupSceneStorage. You can unhide these, then manually delete them in your Hierarchy and save the scene.

Yes, that's what I meant with "Delete all references to those prefabs in my scene".  I use the Hidden Object explorer to find the "fi*" objects and remove them.

To be clear, if I delete the objects then save and run my scene I do not get any errors.  I then reload the scene by double-clicking on the scene file and the objects are back.

Instead of deleting the fi objects in my scene I have removed the dead script references.  I no longer get the errors after reloading the scene, though the scripts do not get reattached.  It seems that deleting the objects with the tool under "Window -- Full Inspector -- Developer -- View All Scene GameObjects" doesn't permanently delete them?  Because now when I delete the objects with no scripts and save/reload the scene they appear again as if they were never deleted.

I misunderstood, I thought you had completely removed FullInspector. I haven't tried the modified script @jacobdufault posted yet.

The FI script to remove the dead instances will not run if you have removed Full Inspector. If you have a lot of these scripts, it may take a little while for them all to get cleaned out as only one is cleared per script reload (ie, enter/exit play mode).

I'm sorry for not being clear in the steps I took, but to reiterate:

I removed the old version of FullInspector
I installed the new version of FullInspector
I tried to clean out old references to fi objects.
I am still seeing this problem.


Serialization improvements

This pull request uses serializers API to simplify encoding / decoding and provides more type safe way to operate with Timestamps

can you rebase and then we can re-review it

@Reedyuk done

Looks good, lets wait for the ci to pass and @nbransby can review too


Custom Cloud Init files not working with Flatcar Linux

I'm trying to deploy Flatcar linux virtual machines using Cloud Init by passing files via cicustom. Based on the example here, I have crafted the following Terraform file:
variable "pve_user" {
}
variable "pve_password" {
}
variable "pve_host" {
}

provider "proxmox" {
  pm_tls_insecure = true
  pm_api_url      = "https://SNIP/api2/json"
  pm_user         = "SNIP"
  pm_password     = "SNIP"
  pm_parallel     = 4
}

resource "null_resource" "cloud_init_config_files" {
  connection {
    type     = "ssh"
    user     = var.pve_user
    password = var.pve_password
    host     = var.pve_host
  }

  provisioner "file" {
    source      = "./templates/cloud-config.yml"
    destination = "/var/lib/vz/snippets/cloud-config.yml"
  }
}

resource "proxmox_vm_qemu" "k8s-masters" {
  depends_on = [
    null_resource.cloud_init_config_files
  ]

  count      = 1
  name       = "VM-${count.index}"
  clone      = "VM-Template"
  full_clone = true

  target_node = "<IP_ADDRESS>"
  pool        = "VM"

  cores   = 2
  sockets = 1
  memory  = 10240

  network {
    id     = 0
    model  = "virtio"
    bridge = "vmbr0"
    tag    = 50
  }

  disk {
    id           = 0
    type         = "scsi"
    size         = 30
    storage      = "Pool"
    storage_type = "zfspool"
    backup       = true
    iothread     = true
  }

  onboot = true
  agent  = 1

  os_type         = "cloud-init"
  ssh_user        = "core"
  cicustom  = "user=local:snippets/cloud-config.yml"
  ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"

  sshkeys = "ssh-rsa SNIP"
  ssh_private_key = <<EOF
-----BEGIN RSA PRIVATE KEY-----
SNIP
-----END RSA PRIVATE KEY-----
EOF
}

After running terraform apply, the VM is successfully created and Flatcar is bootstrapped. If you connect to the console via Proxmox, however, the VM shows that the IP Address is one received via DHCP instead of the one I provided. Furthermore, the SSH key does not work so I am unable to connect to the VM to troubleshoot.
If I comment out the cicustom line, and simply rely on ipconfig0 and the other normal options, the VM comes up and my SSH key does in fact work. However, the specified IP address is still not used; the VM just uses one provided by DHCP instead. Despite being able to access the VM, I still want to use a custom Cloud Init config file so I can have access to more powerful configuration options.
I've tried various combinations of my cloud-config.yml file. Including things as simple as:
hostname: test

to things more detailed like:
storage:
  files:
    - path: /opt/file1
      filesystem: root
      contents:
        inline: Hello, world!
      mode: 0644
      user:
        id: 500
      group:
        id: 501
passwd:
  users:
    - name: core
      ssh_authorized_keys:
        - ssh-rsa SNIP

Despite all of this, my SSH keys never work after I pass something to cicustom and, based on the fact that the hostname is never manipulated, I'm assuming Cloud Init just outright isn't receiving the custom config file at all. I've tried passing in both Ignition and Container Linux Config formatted files.
Is Flatcar Linux broken with Proxmox/cicustom?  Is the bug introduced by this provider? Searching Google for things like "flatcar" "proxmox", "coreos" "proxmox", "container linux" "proxmox", "flatcar" "cicustom", etc don't seem to turn up much results. I guess there aren't a lot of people out there bridging Cloud Native operating systems with bare metal? hehehe
What does come up, however, is this interesting script. Lines 104-132 discuss creating a Flatcar/CoreOS template for Proxmox. So someone else has done this before, at least? Who knows if they passed in a custom cloud init config file afterwards?
Any ideas?

Relevant links:
Script mentioning this issue: https://gist.github.com/chriswayg/43fbea910e024cbe608d7dcb12cb8466#file-create-cloud-template-sh-L107
ServerFault post: https://serverfault.com/questions/1030291/cloud-init-with-flatcar-linux-configuration-not-applying-when-passing-custom

These qm commands produce a working Flatcar VM using cicustom.
qm create 101 --name test --cores 2 --memory 2048 --net0 "virtio,bridge=vmbr0"

qm set 101 --net0 "virtio,bridge=vmbr0,tag=50"

qm importdisk 101 /mnt/RAIDPool_Templates/template/iso/flatcar_production_qemu_image.img FlashPool

qm set 101 --scsihw virtio-scsi-pci --scsi0 FlashPool:vm-101-disk-0 --ide2 FlashPool:cloudinit --boot c --bootdisk scsi0 --serial0 /dev/tty0 --ipconfig0 ip=dhcp --citype configdrive2

qm set 101 --cicustom user=RAIDPool_Templates:snippets/user-data.yml

qm start 101
ssh -i ~/.ssh/sol.milkyway.kubernetes<EMAIL_ADDRESS>
user-data.yml:
#cloud-config
hostname: test
manage_etc_hosts: true
ssh_authorized_keys:
  - ssh-rsa REDACTED
chpasswd:
  expire: False
users:
  - default
package_upgrade: true

Passing the same user-data.yml to cicustom within the proxmox_vm_qemu resource doesn't seem to be working though.

I'm having the same issue with an Ubuntu image. Cicustom just won't work, I don't know if i'm doing something wrong. Does someone actually manage to get it working (I can't really find anything on the web except this issue) ? Did it work maybe in previous versions of proxmox and not now ?

Debian works for me. Here is an example.
https://github.com/zimmertr/TKS-Bootstrap_Kubernetes

I was actually thinking of using your repo, it’s really great ! Can’t wait for the ArgoCD part !
It works because you use the qm set cicustom via ansible rigth ? Because I was using the cicustom option in the terraform file, and I can’t get it to work !
I was only using terraform but I really like your solution with ansible, I’ll try it. I’m kinda new to this so it’s still a bit confusing where I should use ansible and where I should use terraform.

This project uses pure Ansible to deploy VMs (Kubernetes) to Proxmox. Here is the gist of it.
The project I just linked uses Ansible to build a template, and Terraform to deploy VMs from it. You're right though, cicustom is passed in during the template-building stage and not during the VM deployment stage.
After that, I use a combination of file and remote-exec provisioners to further configure VMs post-deployment.
With respect to Terraform and Ansible, I think they compliment each other well and there's no reason to only use one or the other. Ansible is purpose-built for configuration and Terraform is purpose-built for deployment. But you can deploy with Ansible modules and configure with Terraform provisioners.
A common pattern I see, is using Ansible to build a template, AMI, etc. And then using Terraform to deploy from that template. Following that, if you need to perform simple tweaks to the template, use a Bash script executed with a remote-exec provisioner. If you're applying more complicated configurations, however, you can simply install & execute Ansible on the guest using a remote-exec Terraform provisioner.

I appreciate that this is quite an old issue now, but I'm not sure if you're aware that there is now an (undocumented) fix which I've just tested and it works.
I spotted this commit https://github.com/Telmate/terraform-provider-proxmox/commit/217cbfd5a7b87a068f47855ceeb069c353a8a517 and with the following config I brought up an instance which has the correct hostname configured by CI:
  os_type                 = "cloud-init"
  cicustom                = "user=local:snippets/${local.hostname}.yml"
  cloudinit_cdrom_storage = "local-lvm"

$ cat snippets/terraform-test.domain.com.yml
#cloud-config
hostname: terraform-test.domain.com

I'm curious how the flatcar/terraform/cloud-init is going now. Flatcar says on their website that it can still use cloud-init, but also heavily favors ignition. I am running a terraform install on proxmox now, but unable to get it to use the cloud-init file, even with the necessary cloudinit_cdrom_storage parameter in place.

I really wish the proxmox provider would support ignition, but dont see that it does yet.

coreos-cloudinit is no longer under active development

Yea I'd say that is my answer...:)

Success. It CAN be done. With a little help from the --args parameter in the VM config file on proxmox.
With that little trick that I got from here, the Proxmox VM will pick up the ignition file.


Port to 1.20 and 1.20.1

Thank you! But I already updated it myself!

Oops lol. Was worried the mod was dead so I decided to try and help out

That’s fine! The mod was dead but i decided to work on it again!


(re)enable Etcher

This change will trigger Etcher builds for each dependency update, but won't mark the resulting releases final/latest until someone manually checks them and finalises them.

@balena-ci I self-certify!


boatswain build errors

filed https://github.com/nlesc-sherlock/boatswain/issues/5

NLeSC/boatswain#5 has been resolved


Indicate image file format in "Save picture"

The "Save as type:" in the "Save picture" window should indicate the image file type (currently only .svg).

In the current version, the picture type can be selected with a drop down menu before saving. Changing the type in the file selection dialog is not easily possible with the libraries that are used in compareMS2. Therefore, the current solution is the best achievable.


Fix Micronaut typo in VS Code extension

The settings of the Micronaut VS Code extension contain a typo of "Micronaut".

I've already signed the OCA (years ago, which is why it's a different e-mail address): https://oca.opensource.oracle.com/?ojr=contrib-list

/signed
See https://www.oracle.com/technical-resources/oracle-contributor-agreement.html#v


gradle conversion

Addresses https://github.com/Islandora-CLAW/CLAW/issues/348
This is what the build system would look like with Gradle. AFAICT, it produces the same artifacts as the maven-based build. This setup also includes license and checkstyle verification (which are not present in the current build).
So, WDYT? Is it better? One thing is that the there's no XML (except for the checkstyle config, but there's no choice there). One thing to note is that even with the addition of the checkstyle and license configs (~130 lines), using Gradle uses significantly fewer lines of code for the same results.

As a side note for those who may be unfamiliar with Gradle: the ./gradlew and ./gradlew.bat files along with the files in ./gradle are managed by Gradle and would not be modified except when Gradle itself is updated. The files that are equivalent to the maven pom.xml files are all called build.gradle.
Furthermore, the build can be performed with this command: gradle build or gradle install (which installs the artifacts in the local maven repo). It is also possible to publish the artifacts to Sonatype: gradle upload (a username and password need to be added to a local ./gradle.properties file). Each of these tasks can also be performed using the ./gradlew executable (or ./gradlew.bat for Windows users).

@acoburn cool, completely unfamiliar with Gradle so thanks for that intro.

@ruebot looks good to me. Especially the BUILD SUCCESSFUL bit.

@ruebot personally, I just use the version installed locally (gradle clean check), but travis-ci seemed not to like that, so I added the gradle wrapper (./gradlew) to the SCM repo. Doing so also makes the code more self-contained. That is, with Maven, users need an installed version of Maven in order to build the software; with the gradle wrapper, users only need JAVA to build the software.

I know there isn't a whole lot in Alpaca, but it finished in Total time: 6.089 secs the first time. That seems quick.
Also, the config file is still confusing to me but there is a lot less of it than in Maven.
Sooooo 👍 , and then I'll actually read the Gradle docs.

Waiting to talk about it at CLAW call, but I'd be stunned to see someone rally for Maven.

@whikloj one nice thing about Gradle is that there are docs and they are readable.
@ruebot, @dannylamb this is now ready for final review.

I finished the release for my other gradle-based project, and now that everything is set up, this is the extent of the process involved:
first, in ~/.gradle/gradle.properties, make sure the following values are present:
ossrhUsername=<Sonatype username>
ossrhPassword=<Sonatype password>

signing.keyId=<GPG Signing Key Id>
signing.password=<GPG Signing Key passwd>
signing.secretKeyRingFile=/Users/<username>/.gnupg/secring.gpg

Then, run the following command:
./gradlew release

You will be prompted for the release and the next development version to use.
Next, login to Sonatype to close and then release the artifact.
I don't currently have a method for the equivalent of mvn site-deploy, but that should be easy to add with the gradle-git plugin

Turns out, I already had the site-deploy equivalent plugin added, it just wasn't wired into the release process. Now it is.

@ruebot fire away


Statically linking openssl

I've built TDlib for macOS using the build instructions generator. The library works on my machine, but when trying to use it on a device without openssl installed, I get a dynamic linking error. How can I link openssl statically? I'm building an electron application using airgram.
Thanks

You need to install static OpenSSL library and delete dynamic OpenSSL library, and then it will be auotmatically statically linked by cmake during building. You will likely need to build OpenSSL manually from source for that.

Ok, I've done this and it worked.
Thanks for your help

@levlam @khrj  Could you please elaborate how exactly you've done it ? Should I install different package instead of libssl-dev ? If yes, which one ? I'm building on Debian 10.

@unoexperto I'm not sure what exactly I ended up changing here, but I have really old builds here: https://github.com/khrj/tdlib-builder. The scripts should still work, you just need to trigger a build (I don't use Travis CI anymore)

As per the .travis.yml file I was still using libssl-dev

@unoexperto If static openssl libraries are available, you can pass the -DOPENSSL_USE_STATIC_LIBS=TRUE option to CMake. libssl-dev should provide the static libraries.


Enforce TLS for all inbounds if configured

What changed?
Set up TLS for all inbounds

Why?
Previously, only gRPC inbound supported TLS, but with newer yarpc version, support for all transports is available.

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01896964-5a58-4d0a-a488-163cdd965183

11 of 34 (32.35%)  changed or added relevant lines in 1 file are covered.
60 unchanged lines in 9 files lost coverage.
Overall coverage increased (+0.01%) to 57.069%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/rpc/factory.go
11
34
32.35%

Files with Coverage Reduction
New Missed Lines
%

common/rpc/factory.go
1
53.77%

service/history/queue/timer_queue_processor_base.go
1
77.26%

common/membership/hashring.go
2
83.54%

service/history/task/transfer_standby_task_executor.go
2
86.21%

service/matching/matcher.go
2
90.29%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.55%

common/persistence/nosql/nosqlplugin/cassandra/workflowParsingUtils.go
14
83.09%

service/history/execution/mutable_state_task_refresher.go
15
68.67%

common/persistence/nosql/nosqlplugin/cassandra/workflowUtils.go
20
74.5%

Totals

Change from base Build 018965f0-fdaa-4535-a39b-924d1b4fe28b:
0.01%

Covered Lines:
87181

Relevant Lines:
152764

💛  - Coveralls

Closing this. Will bring up another PR for HTTP TLS only. TChannel/Ringpop/YARPC combination makes TLS for TChannel quite complicated.


No u2fval.conf available

I downloaded and tried to install it to my centos botx, but I got the error. Where can I get this conf file?
error: can't copy 'conf/u2fval.conf': doesn't exist or not a regular file

When installing from Git you will need to build a source tarball first:
$ python setup.py sdist
This creates the tarball in the dist/ directory, which can then be installed as usual (using pip for example).
The /conf/u2fval.conf file is a copy of u2fval/default_settings.py


Proxied pod/exec requires extra get permission

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create two new Project roles:

Exec - Create - inherits from Kubernetes view, granted Create on pods/exec for all resource groups
Exec - Get - inherits from Kubernetes view, granted Get on pods/exec for all resource groups

Add user A in project with Exec - Create
Add user B in same project with Exec - Get and Exec - Create

Result:

User A can perform kubectl exec -n <ns> <pod> through kubectl
User A cannot perform Execute shell on the same pod through Rancher UI
User can perform kubectl exec -n <ns> <pod> through kubectl
User can perform Execute shell on the same pod through Rancher UI

Other details that may be helpful:
Although the Kubernetes API server allows exec on a pod with only create pods/exec, Rancher also requires get pods/exec to use the Execute Shell button.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.3
Installation option (single install/HA): HA

There is no this perm in the new version v2.6.3, what is the new option of this perm?

Ran into this issue recently as well with Rancher 2.8.3 . Adding Get on pods/exec allow the shell through the UI to work, but it seems odd when this isn't required via kubectl exec.


Issue from website page Internationalizing Flutter Apps

From URL: https://flutter.io/tutorials/internationalization/ Hi, am trying to add multiple language support in my flutter app but am confusing with your tutorial, can you please share sample project of Internationalizing translation with intl package. Thank you.

The tutorial provides the source for a complete intl example: https://github.com/flutter/website/tree/master/_includes/code/internationalization/intl/


For multiple processes, prompt the user to select one based on the pid

For the case of multiple processes, rather than exiting the process, prompt the user to choose one based on the PID.  This is to fix #32.
The behavior is now like the following:

seems like it would be helpful to the user to display the commandline args of those processes for them to decide which pid they want. what do you think?

Definitely think it's a great idea! Thanks! Command line args are only available to other processes if we are in sudo/admin mode. The way to discern the sudo / admin mode for Linux and MacOs / Windows are different additionally, the methodology to get to command line args amongst the different OSes is different; the last commit before this comment takes care of this.
A different prompt is presented to the user if they are in sudo/admin mode than if they are not.
For Windows:
Non-Admin

Admin

For Linux:
Non-Sudo

Sudo

sorry @MokoSan, I didn't get to your PRs earlier. I'm also starting my vacation so my response will be slow. I've talked to @mangod9 to see if he could review some of the PRs here while I'm OOF.
right, you do need admin privilege to see other processes's cmdline args. I forgot about that. on linux EventPipe does not require you to have admin privilege so users could be both but on windows, since we are using ETW, it means you'd already need to have admin privilege. in your 1st pic (non admin on windows) are you able to actually monitor?

Thanks for taking a look!

in your 1st pic (non admin on windows) are you able to actually monitor?

Yes - I am able to monitor without admin privileges (always have been able to minus the call stack work).
Enjoy your vacation!

#39 will make doing this much easier as we'll have Spectre.CLI support. Will include this with this PR once #39 is merged.

@Maoni0, this PR is also ready to be merged with the latest rebased changes + additions to the different IConsoleOut impls. Additionally, I removed the requirement of being a super user for Linux / MacOS to read the commandline args as it's a simple file read.
Plain Text Prompt

Spectre Prompt

awesome! thanks @MokoSan


How to use Logging

Do you Know How to use Logging?
If you Know, please tell me.

### ### ### ###

``


Invalid album art

When my receiver is playing content without album art (for example plain fm radio), Home Assistant keeps trying to load the unexisting album art for it. This is not a big problem, but when it tries loading the album art, for a fraction of a second, a square image show up in the control panel, before jumping back to the default.
Maybe denonavr can mark that there is no album art in this case?
The image it tries to load is:
https://*mylocalserver*/api/media_player_proxy/media_player.marantz?token=43b0d5633fa6ffc097436e452f19fa8e10eaf767b56b12da83f077cfb571ead2&cache=df4bb

@bmesuere, sorry I was off for a while.
I don't know how the image url you mentioned is generated as the library is using fixed urls

http://{host}/NetAudio/art.asp-jpg?{timestamp as integer} - when there should be a real album art
http://{host}/img/album%20art_S.png - for sources like the Tuner
Probably your receiver is redirecting one of those urls to the one you just posted. Could you please check?

Sorry for the delay in answering. I checked using the python interpreter:
>>> import denonavr
>>> d = denonavr.DenonAVR("<IP_ADDRESS>")
No mapping for audio source AUXC
Missing status information from XML for: FriendlyName
>>> d.image_url
'http://<IP_ADDRESS>/img/album%20art_S.png'

Requesting that image results in an error message with a status code of 404:
Access Error: Site or Page Not Found
Cannot open URL

It returns the same URL for both Tuner and AUXC.
Home Assistant on the other hand, only tries (and fails) to load album art if the source is set to Tuner:
volume_level: 0.1
is_volume_muted: false
media_content_type: channel
media_title: AUXC
source: AUXC
source_list: AUXA,AUXB,AUXC,AUXD,BD,CD,DOCK,DVD,DVR,GAME,HDRADIO,IPOD,IRADIO,LASTFM,M-XPORT,NAPSTER,NET/USB,PANDORA,PHONO,RHAPSODY,SAT/CBL,SERVER,SIRIUS,TUNER,TV,USB,USB/IPOD,V.AUX
friendly_name: marantz
supported_features: 3468
google_assistant_type: media_player

volume_level: 0.06
is_volume_muted: false
media_content_type: music
media_title: 106.80
media_artist: DA
source: TUNER
source_list: AUXA,AUXB,AUXC,AUXD,BD,CD,DOCK,DVD,DVR,GAME,HDRADIO,IPOD,IRADIO,LASTFM,M-XPORT,NAPSTER,NET/USB,PANDORA,PHONO,RHAPSODY,SAT/CBL,SERVER,SIRIUS,TUNER,TV,USB,USB/IPOD,V.AUX
friendly_name: marantz
entity_picture: /api/media_player_proxy/media_player.marantz?token=9cac2d75f93d718c60662aad7cda51d01e5928b6817801c60d20c96996e43041&cache=8895b5346ddccbcb
supported_features: 3468
google_assistant_type: media_player

It seems that the album art URL is not working for Marantz receivers.
The library does not check if anything could be loaded from the URL, probably HA does. There is also a function in denonavr HA media_player component which determines when to show the entity picture.
Do you know a valid album art URL for your receiver?

Indeed, my receiver doesn't seem to support album art. The issue is that denonavr still reports (non-existing) album art, which the HA front end tries to display with layout artifacts as a result. Sorry if this wasn't clear from the initial report.
The request is thus: If there is a reliable way to detect that album art is not supported on the receiver, don't set that field in HA.

Finally I included a test, whether the image URL is accessible or not.
It is included to this HA pull request.
I'm closing this now. If the test is not working, please re-open.


Added Runway AGL

Added Runway AGL as a value to be taken into consideration when setting the cloud base

Added Runway AGL as a value to be taken into consideration when setting the cloud base


Runtime hangs on Windows 7 starting with 7.0.42

Using Windows 10 (my development environment) I've long been able to generate an executable that runs on Windows 7 (a customer's runtime environment). To exclude my code as an issue, I've deployed a Notepad.exe and tried it. With VM 7.0.41 (12-March-2017) and Dolphin commit 2b8d8504d5ad09a5ffd8412f0ce0d3d202d88c96 from 13-July-2017, everything works fine. With VM 7.0.42 (14-July-2017) and Dolphin commit cc0b517bfe297c33a2d72e7634c2d57321a0baf1 from 14-July-2017, we get a hang and the application is non-responsive and must be terminated from the Task Manager. Prior to terminating I was able to get a Windows dump file (36MB) and open it with VS2015. It appears to be in Interpreter::primitiveMillisecondClockValue(). I'm not sure if that helps. Is there a way to force a Smalltalk stack?

I see a comment in environ.h on line 25 that we are supporting Windows 8?

This must be because of the change made to the VM in 7.0.42 to support pen and touch input. I now remember that Andy Bower and I found that it hung Windows 7 when I raised the pen and touch issue under Windows 8 mearly four years ago.
That thread is here

Sorry, I got confused. I'm getting old and don't really understand how GitHub works :(
I didn't read your commit carefully and now see that it WAS to the image. Blair made a corresponding change to the VM to check the same flags for the occasions when the VM needs to signal the semaphore so either that needs a similar check or it is intriguing that the change hangs the in the image but not in the VM.

I entered this issue against the VM when I saw that the minimum OS level was changed here. The fact that I'm able to get beyond the existing issue with an image fix solves my immediate problem but if we can get pen and touch input to work in Windows 8 without dropping support for Windows 7, that would be very nice. Also, I'm not sure that my image-based "solution" is any more than a "hack."

See 3ca07425a749279ed77f8b80a0c48ffeb38f461e


Fix fraud dashboard - cypher and details component

Fixed Cypher queries (distance to position distance)
Details from one line to each column to four columns

Hi @elizarp, thank you for your help, but it looks like you need to pull develop first into your repo before merging, there are too many changes.

Closed and moved to #885

Sorry. I didn't have time to fix it, but you've already done it.
Em ter., 7 de mai. de 2024 às 06:28, alfredorubin96 <
@.***> escreveu:

Closed and moved to #885 https://github.com/neo4j-labs/neodash/pull/885
—
Reply to this email directly, view it on GitHub
https://github.com/neo4j-labs/neodash/pull/837#issuecomment-2097858036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4OXFL44P5DIXRFSKQKFKTZBCNE5AVCNFSM6AAAAABFBLXBQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXHA2TQMBTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


sqlite db not readable when number of columns are more

Sqlite db becomes unreadable when number of columns are more
as when we browse columns horzontal scrolling is not available hence unable to view the columns properly

This view is owned by chrome, and we cant do much about it.
One option here is to select the database rather than the table. This gives you the ability to execute sql commands so you can restrict what columns you are getting.


hook的时候发生错误 It is not supported to directly hook through the WOW64 barrier

Note that 64bit exe loads 64bit dlls.


gamma_p and gamma_q gradient problems

Description
gamma_p doesn't work great with vars and gamma_q doesn't work great with fvar<double>
Here is test code:
#include <test/unit/math/test_ad.hpp>
#include <limits>

TEST(mathMixScalFun, gamma_q) {
  using stan::math::var;
  using stan::math::fvar;
  using stan::math::gamma_q;
  using stan::math::gamma_p;
  using stan::math::gamma_lccdf;
  using stan::math::log;
  using stan::math::log1m;

  var yv = 12;
  var alphav = 3;
  var betav = 3;

  fvar<double> yf(12.0, 1.0);
  fvar<double> alphaf(3.0, 1.0);
  fvar<double> betaf(3.0, 1.0);

  var lp1 = log1m(gamma_p(alphav, betav * yv));
  fvar<double> lp2 = log(gamma_q(alphaf, betaf * yf));

  lp1.grad();

  std::cout << "Computed: " << std::endl;
  std::cout << "lp1.val(): " << lp1.val() << std::endl;
  std::cout << "lp2.val(): " << lp2.val() << std::endl;
  std::cout << "y.adj(): " << yv.adj() << std::endl;
  std::cout << "alpha.adj(): " << alphav.adj() << std::endl;
  std::cout << "beta.adj(): " << betav.adj() << std::endl;
  std::cout << "lp2.d_: " << lp2.d_ << std::endl;
}

TEST(mathMixScalFun, gamma_q_ref) {
  using stan::math::var;
  using stan::math::fvar;
  using stan::math::gamma_q;
  using stan::math::gamma_p;
  using stan::math::gamma_lccdf;
  using stan::math::log;
  using stan::math::log1m;

  var yv = 12;
  var alphav = 3;
  var betav = 3;

  fvar<double> yf(12.0, 1.0);
  fvar<double> alphaf(3.0, 1.0);
  fvar<double> betaf(3.0, 1.0);

  var lp1 = gamma_lccdf(yv, alphav, betav);
  fvar<double> lp2 = gamma_lccdf(yf, alphaf, betaf);

  lp1.grad();

  std::cout << "Reference: " << std::endl;
  std::cout << "lp1.val(): " << lp1.val() << std::endl;
  std::cout << "lp2.val(): " << lp2.val() << std::endl;
  std::cout << "y.adj(): " << yv.adj() << std::endl;
  std::cout << "alpha.adj(): " << alphav.adj() << std::endl;
  std::cout << "beta.adj(): " << betav.adj() << std::endl;
  std::cout << "lp2.d_: " << lp2.d_ << std::endl;
}

The output for gamma_p and gamma_q are (computing the same function, lp1 is with gamma_p and lp2 is with gamma_q):
Computed:
lp1.val(): -inf
lp2.val(): -40.9091
y.adj(): 0
alpha.adj(): 0
beta.adj(): 0
lp2.d_: -8.45518e+22

And the reference values are here:
Reference:
lp1.val(): -40.9091
lp2.val(): -40.9091
y.adj(): -2.8776
alpha.adj(): 2.96967
beta.adj(): -15.3472
lp2.d_: -15.2551

Current Version:
v3.3.0

Thanks for posting code. I was trying to verify it and I got something different:
Computed:
lp1.val(): -29.4707
lp2.val(): -29.4706
y.adj(): 0
alpha.adj(): 0
beta.adj(): 0
lp2.d_: -6.70499e+12

Reference:
lp1.val(): -29.4706
lp2.val(): -29.4706
y.adj(): -2.83796
alpha.adj(): 2.68924
beta.adj(): -11.3518
lp2.d_: -11.5005

Is there some reason my output is different than yours (for even the .val())?

@syclik aaah, yeah you're right I updated the numbers in the reference code without regenerating the output. I updated the post.

I think the issue is that the fwd gamma_q is an interative algorithm which what might be a coarse tolerance: https://github.com/stan-dev/math/blob/develop/stan/math/fwd/fun/gamma_q.hpp#L32
And for rev gamma_p the gradient gets thresholded to zero: https://github.com/stan-dev/math/blob/develop/stan/math/rev/fun/gamma_p.hpp#L39

Should we try what boost offers here:
https://www.boost.org/doc/libs/1_72_0/libs/math/doc/html/math_toolkit/sf_gamma/gamma_derivatives.html
Maybe this stuff is new? I don't know the history, but this is worth considering.

Maybe. It looks like that gives one of the two gradients in each case. I'm not sure which is causing the problems. I just made the issue so it's known (didn't really plan on fixing it)


SDP-801, SDP-803: add documentation about SP integration and some recommended values

What
Add documentation about SP integration and some recommended values for:

Configuring SDP<>AP authentication.
Maintaining the Wallets and Assets configuration in sync.
Ensuring the best security measures are in place.

Why
To improve information on the project configuration and security best practices.
Pending:

[ ] Update https://github.com/stellar/helm-charts
[ ] Bump the chart version

Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).
[x] This PR's title starts with the name of the package, area, or subject affected by the change.

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[x] Does the deployment work after merging?

Something went wrong with PR preview build please check

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr16.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr16.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr16.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr16.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr16.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr16.previews.kube001.services.stellar-ops.com


unsupported match type for string: EACH_EQUALS

Hi!
I am getting this error message:
unsupported match type for string: EACH_EQUALS
For this step:

match each response/list/cost/Rate == 0.920509

For this xml:

#present // contains 0.920509

#ignore

And I have no idea why this isn't working...

sorry, use Stack Overflow if it makes it easier to post XML: https://stackoverflow.com/questions/tagged/karate

Sorry the formatting is a bit weird yeah!
Made https://stackoverflow.com/questions/60417595/unsupported-match-type-for-string-each-equals


fix(mps-sync-plugin-lib): a partially initialized registry can be disposed

Otherwise BranchRegistry cannot be disposed if the ReplicatedModel or the IBranch was not initialized correctly.

:tada: This PR is included in version 0.9.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


(ISO 8601-1/Amd 1) "Note" style is still lowercase "note" which doesn't exist

This task blocks submission of ISO 8601-1/Amd 1.
From @opoudjis:

The style Note was being applied correctly. It is still showing as "note" because I was permitting "note" as a variant name of Note in the CSS, to license both names, and Word is reading the style name from the CSS, not the document instance. Removing.

Can we find a way to do this? Having the wrong style name will not work for ISO. In addition, the "note_label" is also not an ISO style.
Metanorma generated doc:

ISO encoded doc:

Originally posted by @ronaldtse in https://github.com/metanorma/metanorma-iso/issues/656#issuecomment-1127110083

I believe this is being addressed in #661.

With just-released metanorma-iso 2.1.1

Stripping note_label, example_label from DIS output; they are semantically useful in building up the documents in Metanorma in general, but they can be stripped in the final DIS artefact.

Confirm fixed. Thanks!


Invoke Request message with multiple path support needed

Feature description
Invoke Request message with multiple path support needed

Test Case - TC-IDM-1.1 step#3

Platform
raspi
Platform Version(s)
No response
Anything else?
No response

Duplicate of https://github.com/project-chip/connectedhomeip/issues/23381


[FR]: data-type=password in mvc formulars

Hi,
in a dialog forms there's the option data-type="string" which will be translated as type=text in <input>
Is there a change to add a data-type="password" to translate it as type=password?
Example:

                {{ lang._('Enabled') }}
                {{ lang._('Username') }}
                {{ lang._('Password') }}

Perhaps there's already an option I'm not aware of :)
Thanks!

Hi there,
This? :)
https://github.com/opnsense/core/blob/master/src/opnsense/mvc/app/views/layout_partials/form_input_tr.volt#L65
Cheers,
Franco

Forget it ... form <type>password<type> ... should have investigated some more minutes :(


Dropwizard 2.0.24 compatibility with Oracle RAC

Currently we are using dropwizard 1.0.6 in our  microservice application. We had upgraded dropwizard to 2.0.24 in one of the other application versions.
We want to check whether these dropwizard versions are compatible with Oracle RAC database. If one database node goes down, can dropwizard take care of re-establishing the connection objects without the need of restarting microservices?

Dropwizard 2.0.x is end-of-life since January 31, 2023: https://github.com/dropwizard/dropwizard/discussions/6324
The latest stable versions are Dropwizard 3.0.0 and 4.0.0.
Dropwizard is using jdbi3 or Hibernate ORM, together with the Tomcat JDBC Connection Pool which in turn use JDBC.
See https://www.dropwizard.io/en/stable/manual/jdbi3.html and https://www.dropwizard.io/en/stable/manual/hibernate.html for the respective documentation.


WIP: Add basic EVP_KEYMGMT API and libcrypto <-> provider interface

The idea with the key management "operation" is to support the
following set of functionality:

Key domain parameter generation

Key domain parameter import

Key domain parameter export

Key generation

Key import

Key export

Key loading (HSM / hidden key support)

With that set of function, we can support handling domain parameters
on one provider, key handling on another, and key usage on a third,
with transparent export / import of applicable data.  Of course, if a
provider doesn't offer export / import functionality, then all
operations surrounding a key must be performed with the same
provider.
This method also avoids having to do anything special with legacy
assignment of libcrypto key structures, i.e. EVP_PKEY_assign_RSA().
They will simply be used as keys to be exported from whenever they are
used with provider based operations.
This change only adds the EVP_KEYMGMT API and the libcrypto <->
provider interface.  Further changes will integrate them into existing
libcrypto functionality.

Do not that this is a very early draft.  The primary purpose for submitting this PR this early is to expose they ideas and get early feedback on the line of thoughts.

Key loading (HSM / hidden key support)

This is highly experimental for now, but does provide the necessary support for getting keys through provider OSSL_STORE backends.  More on that in a separate PR.

I really want to review this in more detail.  I didn't get to it today and am too tired to think too hard this evening.

Key Derivation?
I'm not sure about operations "Key loading" vs "Key import". Second is defined for private and public. What will load first one?

Perhaps API could be based on basic(elementary/atomic) operations
defined in "key management protocol".
There is some standard protocols but I prefer experts to propose which
one to use.
Roumen

Key Derivation?

Different operation, see #9266...  but yes, it has occured to @mattcaswell and me that key exchange result in a key as well, that wasn't lost on us.  There will be some form of integration eventually, I'm sure, but not now and not in this PR.  Let's take it a step at a time, yeah?

Perhaps API could be based on basic(elementary/atomic) operations defined in "key management protocol".

Not sure if that would make things better or not.  Maybe...

I'm not sure about operations "Key loading" vs "Key import".

The key import function takes key material from the input OSSL_PARAM array and creates a key from that input (usually a bunch of big numbers).
The key loading function is aimed at HSMs, and gives the option to "load" an HSM protected key given some kind of identity.  The identity isn't defined at all for the moment, and I'm thinking of it as highly provider specific, i.e. unstandardised.  My current thinking is that it can work together with a provider OSSL_STORE implementation that returns such identities instead of EVP_PKEYs, and leaves it to libcrypto to actually "load" the key given such an identity.  I've an unsubmitted branch where I currently experiment with this.

Documentation added

Richard Levitte wrote:

I'm not sure about operations "Key loading" vs "Key import".

The key import function takes key material from the input OSSL_PARAM array and creates a key from that input (usually a bunch of big numbers).

Interesting.
Working with different cryptographic libraries I note that common part
is exchange of DER encoded data (key, cert). So instead ASN1 encoding
you prefer data encoded as OSSL_PARAM, right?

The key loading function is aimed at HSMs, and gives the option to "load" an HSM protected key given some kind of identity.  The identity isn't defined at all for the moment, and I'm thinking of it as highly provider specific, i.e. unstandardised.
This cannot be restricted to "hardware" only.  Software "key-store" may
not allow private part to be exported.

My current thinking is that it can work together with a provider OSSL_STORE implementation that returns such identities instead of EVP_PKEYs, and leaves it to libcrypto to actually "load" the key given such an identity.  I've an unsubmitted branch where I currently experiment with this.

Right now I'm not sure what you mean by provider and what is difference
to engine. Shall we consider engine as simple provider?
Regards,
Roumen

I think you need to read up in https://www.openssl.org/docs/OpenSSL300Design.html and https://www.openssl.org/docs/OpenSSLStrategicArchitecture.html.  The former is what were working toward, and is the reason you're seeing so much moving around right now.

Richard Levitte wrote:

The identity isn't defined at all for the moment, and I'm thinking of it as highly provider specific, i.e. unstandardised.

In some implementation "identity" is X.509 certificate(a) and private
key. For other is pair public(b) and private key. Private key is
accessed indirectly by (a) or by (b).
May be you want to use another kind of keys . But this will require
delegation of cryptographic operations to identity or "identity provider".
Roumen

Working with different cryptographic libraries I note that common part is exchange of DER encoded data (key, cert). So instead ASN1 encoding you prefer data encoded as OSSL_PARAM, right?

We have chosen the OSSL_PARAM array as a data transfer medium between libcrypto and provider, yes.  We wanted something that isn't tied to any particular form of serialization.  I've realized after the fact that they have certain similarities with PKCS#11's attribute templates.

The key loading function is aimed at HSMs, and gives the option to "load" an HSM protected key given some kind of identity.  The identity isn't defined at all for the moment, and I'm thinking of it as highly provider specific, i.e. unstandardised.

This cannot be restricted to "hardware" only.  Software "key-store" may not allow private part to be exported.

Correct, I use "HSM" loosly, i.e. for something that keeps keys and other sensitive data for themselves.

This is not a draft any more

"make doc-nits" is complaining.

We should have some tests for this code.

Ah, in test/evp_extra_test.c?  (I noticed that EVP_MD_fetch has a few tests there)
Sure, I will, if you add one for EVP_CIPHER_fetch :wink:

"make doc-nits" is complaining.

Fixed

There are quite a few conversations going on here, I'd like to nudge y'all to respond

Engine interface lacks functionality to get X.509 certificate for a key. As work around some engines implement "custom" control commands. More or less STORE2 API removes such limitation.
It seems to me new API reintroduce engine limitation.

It seems to me new API reintroduce engine limitation.

The KEYMGMT API doesn't support OSSL_STORE, no.  I'm working on another libcrypto<->provider API that supports OSSL_STORE.  The plan is that that API will return key references in form of identities that can be used with the loadkey function in this API.  This is to allow the EVP_PKEY to be created by libcrypto without too much weird entanglement in the provider.
Please be patient.

Looks like you need a rebase

Looks like you need a rebase

Yup, I noticed.  Especially with #9266 just being merged...

Rebased and squashed, to get a clean slate.

I think this is ready for final review.  There was a failure in Travis, but that turned out to be an unrelated timeout.  I've restarted that job, just for the hope of greenery :wink:

Merged.
a94a3e0d91378b5c478f687a0dbc51914d4ed497 Add basic EVP_KEYMGMT API and libcrypto <-> provider interface
70a1f7b4d7a0611508f45ef884472b9d84cbe108 Add evp_keymgmt_export_to_provider(), for key transfer between providers
d0ea49a820e02713bbe8892a333f2552da633b16 Adapt int_ctx_new() to use with providers
4cae07fef3b24bee1646f6085c52175ef3755d5b Add evp_keymgmt_clear_pkey_cache() and use it
fa9faf010460f5fe0722a65f9d496221c2f41f7b Add an internal API to access the KEYMGMT provider functions


Voting with slider - cosmetic error description

When I tried to vote with 0.01% weight. The message that appears is this one:

My suggestion is to also add " or try to increase voting slider percentage" or something like that.

Good idea, error message is coming from blockchain though...but we can add extra explanation if necessary

But here we are also translating right? I know it will be a pain to ask for more translation... maybe park it somewhere until there's a good reason to change it.


styled(Input) and borderColor or borderWidth | bug

When I try to override borderColor or borderWidth for styled(Input) it is not working.
The reason is that tamagui is using border-left-color instead of border-color. Probably it is mismatched somewhere in the code.
const StyledInput = styled(Input, {
  borderColor: 'transparent',
  borderWidth: '0px',
});

Version: 70

Good catch, will be fixed in https://github.com/tamagui/tamagui/pull/115/commits/7172b1f5084441c6025495813247132873f7e672

Fixed, thanks


offset in 3D data limits accessible color scale

The current master branch 4dad0eaa has scaling problems when displaying data with offset.
The positions of the contrast/brightness sliders on the left hand side only yield a visible image for a few positions. Otherwise the image is black/full background.
I resolved this temporarily by removing the offset:
data -= data.min()
volfig(0)
volshow(data)

Note: I experienced this problem when working with refractive index values which usually have an offset > 1.0 and don't go beyond 2.

volshow doesn't scale the data to the full range by default, you can however activate that by calling
volshow(data, autoscale = True)

where data internally is rescaled to a bigger range (via numpy, i.e. possible slow, which is why the default is autoscale=False)

Thanks.