Release candidate (#2298)

replace printable for try/except utf-8

add sleeps for tests

moving wait_for_prep_information_job

just leaving the changes on this pr

Fixing tests

Reverting changes

dist: precise

addressing @josenavas comments

fix-2212

Adding branch description to Contributing (#2256)

Adding branch description

Adding spaces

Adding timeline

upgrading software

mv r_client to qiita

from redis import Redis

rm moi and ipython

Move qiita_db/private.py -> qiita_ware/private_plugin.py

_system_call as system_call

flake8

rm create_raw_data

Transferring VAMPS submission to internal job

rm other unnecessary files

addressing @josenavas comment

Fixing merge conflicts

Adding tests to private plugin

rm wrapper.py

Removing import

Fixing import

Modifying GUI to use the plugin

moving qiita pet in .travis.yml

Transfer submit to vamps (#2265)

Move qiita_db/private.py -> qiita_ware/private_plugin.py

Transferring VAMPS submission to internal job

Fixing import

some other .travis.yml fixes

addressing @josenavas comment

Adding success test

adding some methods

flake8

Transfer copy raw data (#2267)

Move qiita_db/private.py -> qiita_ware/private_plugin.py

Transferring VAMPS submission to internal job

Fixing merge conflicts

Adding tests to private plugin

Removing import

Fixing import

Modifying GUI to use the plugin

Adding success test

change imports

adding delete_artifact and create_sample_template

fixing errors and gui

fix delete error

ENH: Make jobs list modal

With some recent changes to the position of the navigation bar, the
header of the jobs list is cut from screen. With this patch in place,
the jobs list will be shown as a modal window, so that won't be a
problem anymore.

Transfer update delete templates (#2274)

Moving update_sample_template

Transfer update_sample_template

Porting update prep template

Moving delete sample or column

Removing tests

Removing dispatchable and its tests

Updating interface to use the new functionality'

Adapting the prep template GUI

Submitting jobs

Fixing tests

Removing qiita_ware/context.py

flake8ing

Fixing _system_call

Safeguarding the call to rollback

Unmasking more errors

Forcing different connections on different processes

Moving job completion to internal plugin structure

Removing unused code

Forcing the creation of a new transaction on the jobs

Fixing tests

forcing the commit

Fixing all tests

Addressing @antgonza's comments

Addressing @antgonza's comment

Addressing @ElDeveloper's comments

BUG: Fix job updates

Fixing the redis DB (#2277)

Fixing the redis DB

Addressing @antgonza's comments

redbiom install

redbiom to install_requires

mv moi-ws to qiita_websocket

init commit

addressing @wasade comment

rm webdis.log

cleaning code for initial review

install latest redbiom

fix test

ENH: Change phrasing of upload text (#2281)

ENH: Change phrasing of upload text

As per a user's request.

Fix typo in docs

Fixes #2259

addressing @wasade comments and adding other tests

flake8

addressing @josenavas comments

fix #2258

fix #2258

fix #858 (#2286)

addressing @ElDeveloper and @josenavas comments

@ElDeveloper :|

redbiom now adds per sample studies to analysis

jobs-list-as-modal

addresssing @josenavas comments

rm () from update_processing_job_data

add prints to review errors

rm prints

Fix 2190 (#2292)

Adding patch to add the 'name' parameter to all validate commands

Adding the parameter 'name' automatically and adding a test for it

Removing extra blank line

Adding dflt value to artifact name

Edited the wrong file

Adding user defined name at creation time

Fixing test

add is_from_analysis to artifact_handlers (#2293)

add is_from_analysis to artifact_handlers

fix test_post_metadata

fix error

WIP: rm sudo from travis

adding sed for config file

fix sed

rm &

cat redis.conf

using local redis.conf

protected-mode yes

supervised no

redis-server --port 7777 &

Fix 1293 (#2291)

fix #1293

flake8

fix errors

addressing @ElDeveloper comments

rm redis.conf

fix awaiting_approval list bug

Fix #2276 (#2294)

Fix #2276

Factoring out generate nginx directory file list

Factoring out the nginx file list writing

Factoring out generating the file list of an artifact

Factoring out the header setting

Addressing @antgonza's comment

Addressing @wasade's comments

Codecov Report

Merging #2299 into master will increase coverage by 0.98%.
The diff coverage is 90.53%.

@@            Coverage Diff             @@
##           master    #2299      +/-   ##
==========================================
+ Coverage   92.81%   93.79%   +0.98%
==========================================
  Files         171      163       -8
  Lines       18925    18579     -346
==========================================
- Hits        17566    17427     -139
+ Misses       1359     1152     -207

Impacted Files
Coverage Δ

...ita_pet/handlers/study_handlers/tests/test_base.py
98.14% <ø> (-0.22%)
:arrow_down:

qiita_db/test/test_commands.py
99.6% <ø> (+0.28%)
:arrow_up:

qiita_db/test/test_artifact.py
99.84% <ø> (ø)
:arrow_up:

qiita_pet/test/test_prep_template.py
97.87% <ø> (ø)
:arrow_up:

qiita_db/commands.py
96.55% <ø> (-0.48%)
:arrow_down:

qiita_db/__init__.py
100% <ø> (ø)
:arrow_up:

...iita_pet/handlers/api_proxy/tests/test_artifact.py
98.22% <100%> (ø)
:arrow_up:

qiita_db/metadata_template/test/test_util.py
99.49% <100%> (+0.01%)
:arrow_up:

qiita_db/handlers/tests/oauthbase.py
100% <100%> (ø)
:arrow_up:

qiita_pet/handlers/api_proxy/artifact.py
99.19% <100%> (-0.02%)
:arrow_down:

... and 57 more

Continue to review full report at Codecov.

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

🎉 😄 🚀


docs: v0.25.0 update

What kind of change does this PR introduce?
v0.25.0 docs update

Coverage remained the same at 100.0% when pulling ed173756ca09091b78e624ef5f5ae5651e4f79cd on v0.25-docs into 0455911c0f523102ee324a305ab0714f3cc02552 on master.


Code for claim extraction evaluation

Hi! I'm looking for the code you used for calculating ROUGE and BertScore on the RoSE dataset. Is it available by chance?
Thanks!

I'm looking for the code too! Thanks!


Update CHANGELOG.md for #34005

Are we allowed to reference pull requests in place of JIRA reports though?

You can file a new JIRA ticket and link it in the changelog.

Yeah, I am just curious whether referencing a PR directly is acceptable :)

ping


WSDL Response decoding does not seem to work

I cannot, despite my best efforts, find a way to decode the response body.
The envelope is processed fine, just the contents of the Body is not decoded.
I think we need a test case for the generated code, as #25 calls for

I admit I haven't even manually tested this part of the generated code very thoroughly. Would you happen to have a WSDL endpoint in mind that we can use as an example?

I'm new to the world of WSDL, so don't have any examples to test against.
It's fairly striaghtforward to catch: if you marshal and serialise a request struct to bytes, then try to deserialise and marshal it back to structs then it will just be empty.
IIUC it's because the Envelope Body is an interface{}; go can marshal it since it has a instance to reflect on, but it can't unmarshal it because it's not sure what type they should be.

Ah, it looks like the tests I have in wsdlgen/examples/* only test marshalling.
I think the gentests/_testgen can be easily extended to generate tests for wsdlgen if there is a *.wsdl file, and mock responses if there is a *.sample file in the relevant directory, with some inspiration from the links you gave me in #25.


Update memory and cores requirements during assignment

As we @ticoann @ericvaandering discussed some time ago, these are the required change to make "Multicore" and "Memory" parameters overwritable during assignment.
It's still not clear to me whether we should also update the reqmgr2 couch doc (reqmgr_workload_cache). If we do, then the original values are gone and any clones would use the new values. I'm inclined not to... I think (?)
Initial tests work Ok in my VM, though I still need to check the reqmgr2 part.

Ok, all 4 use cases tested:

update cores and memory in both reqmgr and reqmgr2
cores and memory untouched during assignment  in both reqmgr and reqmgr2
only cores updated  in both reqmgr and reqmgr2
only memory updated in both reqmgr and reqmgr2

The job splitting was not touched and it would need to be manually changed, if needed.

@ticoann btw, it's good to go from my side


Fixed bug 'AuthHeaders ignored for sendOnClose'

Function sendOnClose()  no longer uses global.navigator.sendBeacon() to send its logs, now uses global.fetch() which supports authentication headers.

Added pre-commit hooks for linting, formatting, building, and testing. Note: this commit ran the formatter resulting in a large number of source files being modified (formatted). The important changed files in commit 1512c48 are .husky/pre-commit, package.json, eslint.config.mjs, .eslintrc.json

@rc10house I just noticed a few things.

You're doing this work directly on your master and merging to master.
You've combined multiple tickets into a single PR.

Please do the following:

Revoke this PR.
Create a new branch for each issue you are working on and include the issue number in the branch title, e.g. 399-auth-headers-ignored-send-on-close
Cherry pick the correct commits from your master into each branch, respectively.
Roll back your master to match the REMOTE master
Squash the commits for each issue-branch into a single commit.
Create separate PRs for each of the issue-branches, and reference the issues in the PR text via #<issue-number-here>.

This will keep the history clean and maintain a one-one mapping between commits and issues. Very important.

Will do. Sorry, I had issue/feature branches locally but merged them into master before opening the PR.


Expand UI (html)

Add "Reset" button for resetting position (use the already implemented reset function which is located in branch "controls"

-Add Controls for moving with camera left, right, up and down (UI D-pad)

UPDATE: UI implemented but needs some modifications like styling and positioning on the canvas!


Cannot be done using powershell.

Cannot be done using powershell.
Undo-AzRecoveryServicesBackupItemDeletion : Undo-deletion is only supported for AzureVMs. This method is not supported for other workloads.

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

ID: 23863a81-7b5b-566c-2b77-4baf4071b44a
Version Independent ID: 04740e94-22ce-7ef8-1ca5-93e8843dc0bc
Content: Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads - Azure Backup
Content Source: articles/backup/soft-delete-sql-saphana-in-azure-vm.md
Service: backup
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

@CharlesGroleau Thanks for your comment. We will review the issue and get back to you shortly.

#reassign:pvrk

@CharlesGroleau : Can you please check the version? It should work from 5.3.0 atleast.

<EMAIL_ADDRESS>De : Kartik P V R<EMAIL_ADDRESS>Envoyé : 16 février 2021 02:36
À : MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc : Charles Groleau<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Objet : Re: [MicrosoftDocs/azure-docs] Cannot be done using powershell. (#70625)
PRUDENCE: Ce courriel provient de l'extérieur de notre organisation. Ne cliquez pas sur des liens et n'ouvrez pas de pièces jointes à moins de reconnaître l'expéditeur et de savoir que le contenu est sécuritaire.
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@CharlesGroleauhttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCharlesGroleau&data=04|01|charles.groleau%40globalexcel.com|27a1902ab57f4c37ffe508d8d24d792b|cbe28c2f7e6d4e81bdac76a2e9f7256c|1|0|637490577475098126|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=pV98nfKo03JI5qOPGfaoZrduJnTE0Ibm1EfjWAD4B20%3D&reserved=0 : Can you please check the version? It should work from 5.3.0 atleast.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F70625%23issuecomment-779647020&data=04|01|charles.groleau%40globalexcel.com|27a1902ab57f4c37ffe508d8d24d792b|cbe28c2f7e6d4e81bdac76a2e9f7256c|1|0|637490577475108115|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=n5i2mDH21ITTVVDOjbCoxHsWTyq6CpSZq4R%2FPZ4Az6U%3D&reserved=0, or unsubscribehttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANQ4PAI3TQ5ZO2UH2LPKVULS7IN5DANCNFSM4XVWU5PA&data=04|01|charles.groleau%40globalexcel.com|27a1902ab57f4c37ffe508d8d24d792b|cbe28c2f7e6d4e81bdac76a2e9f7256c|1|0|637490577475113097|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9JWRM8exi2CxlfiQ%2BKthq%2F4i4zz6YqyT6Zlg9b0eVic%3D&reserved=0.
---------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material; unauthorized use of this information is prohibited. If you have received this in error, please contact the sender and delete the material immediately. L'information transmise ne s'adresse qu'au particulier ou à l'organisme a qui elle est dirigée. Elle peut contenir des renseignements de nature privilégiée et/ou confidentielle. Toute utilisation non autorisée est interdite. Si vous avez reçu ce courriel par erreur, SVP le retourner à l'expéditeur et le détruire. ----------

@CharlesGroleau : I can't see the pic but I want to confirm whether you are trying this for SQL? Because other than SQL and VM, undo-deletion is not applicable for AFS and HANA

We can correct the error text shown above to reflect the current status. So, please confirm if this is the root cause.

Yes for SQL, Updated my comment. See above.

[MicrosoftDocs/azure-docs] Cannot be done using powershell. (#70625)

Powershel version is 5.1 Module version for Az-RecoveryServices is 3.0.0 Commands are: $item = Get-AzRecoveryServicesBackupItem -BackupManagementType AzureWorkload -WorkloadType MSSQL -VaultId $vault.ID Undo-AzRecoveryServicesBackupItemDeletion -Item $Item Error: Undo-deletion is only supported for AzureVMs. This method is not supported for other workloads.

@CharlesGroleau: Can you please update your Az version to 5.3 and try? There was a bug in earlier versions which we fixed with 5.3

I had multiple versions of the module installed, removed them all and installed only latest and everything runs as documented,
Thank you


rustup-toolchain-install-master: mark as broken

Description of changes
Upstream package didn't have recent releases.
https://github.com/kennytm/rustup-toolchain-install-master
Currently build fails with something like
  running: "/nix/store/dq0xwmsk1g0i2ayg6pb7y87na2knzylh-gcc-wrapper-11.3.0/bin/cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "/nix/store/f95kxwhnr2bazy7nl6wzwjiak02dlp9v-openssl-3.0.7-dev/include" "-Wall" "-Wextra" "-E" "build/expando.c"
  cargo:warning=build/expando.c:4:24: error: pasting "RUST_VERSION_OPENSSL_" and "(" does not give a valid preprocessing token
  cargo:warning=    4 | #define VERSION2(n, v) RUST_VERSION_##n##_##v
  cargo:warning=      |                        ^~~~~~~~~~~~~
  cargo:warning=build/expando.c:5:23: note: in expansion of macro 'VERSION2'
  cargo:warning=    5 | #define VERSION(n, v) VERSION2(n, v)
  cargo:warning=      |                       ^~~~~~~~
  cargo:warning=build/expando.c:10:1: note: in expansion of macro 'VERSION'
  cargo:warning=   10 | VERSION(OPENSSL, OPENSSL_VERSION_NUMBER)
  cargo:warning=      | ^~~~~~~
  exit status: 1

which looks like https://github.com/sfackler/rust-openssl/issues/1030 and should be fixed in a transitive dependency by https://github.com/sfackler/rust-openssl/pull/1264
But not sure if this can be simply patched & bumped so starting with marking package as broken.
ZHF: #199919
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

How about downgrading to openssl 1.1.1 instead?
@ofborg eval

Didn't realize nixpkgs include both 1.x and 3.x versions of openssl, pinning to 1.x looks promising


Close connection on ctx.Done and timeout

We decided not to go this way for now to avoid handling/ignoring multiple close() calls.


[Bug] checklist_dependency old value breaks the whole Create/Update operation

Bug report
What I did
Tried to Create a user in PermissionManager
What I expected to happen
Form opens
What happened
Big fat error:

What I've already tried to fix it
Changed those bits to isset($old_primary_dependency) and isset($old_secondary_dependency) thinking that's a small mishap in #3054 . Then the form loads. But no old value is populated at all.
Is it a bug in the latest version of Backpack?
4.2

Hey @tabacitu
Indeed there is a bug on how I setup the dependencies, but that should be fixed in #4052 .
The problem with old value is not new, it's there since the field exists basically.
We setup the secondary entries as disabled when they get "auto-selected" from primary.
I think we have 2 options here:
a) keep disabling the checkboxes, but create hidden inputs for them so they get submitted.
b) style the checkboxes to look like disabled and use JS to prevent clicks, keyboard interaction etc.
Let me know if this is something you want to pursue for 4.2 launch.
Pedro

Hey Pedro,
Just tested and merged #4052 . From what I see, the only real difference is this:
Before the user hits submit they see this:

After failed validation they see this:

This is the remaining problem you're talking about, right? If so... it's just an interface problem. What will get saved is still the same. What we should do, I think, is NOT add hidden inputs or change the style. We should probably change the javascript, so that on pageload, if "admin" is selected, its permissions will automatically be selected too. I see this is already happening when you click "Edit" on the User afterwards:

This is a bug... but... it's low prio. We can launch with it.

closed in favor of #4056 since the bug reported here had been fixed in #4052


Failed to deploy  parse server exmaple v1.2.0 to aws

I have found we can't deploy v1.2.0 to aws .  And I get the log from

/var/log/eb-activity.log

and find following error information

../lib/kerberos.h:5:27: fatal error: gssapi/gssapi.h: No such file or directory
#include <gssapi/gssapi.h>
^
compilation terminated.
make: *** [Release/obj.target/kerberos/lib/kerberos.o] Error 1

I have googled for hours  and finally I have solved this issue just to change the the kerberos version to  0.0.16 at package.json.
{   "name": "parse-server-example",   "version": "1.2.0",   "description": "An example Parse API server using the parse-server module",   "main": "index.js",   "repository": {     "type": "git",     "url": "https://github.com/ParsePlatform/parse-server-example"   },   "license": "MIT",   "dependencies": {     "express": "~4.2.x",     "kerberos": "~0.0.16",     "parse": "~1.6.12",     "parse-server": "~2.1.4"   },   "scripts": {     "start": "node index.js"   },   "engines": {     "node": ">=4.3"   } }
**It's very strange. After I restarted EBS, then I deploy a new version to EBS today, this error occurs again. **

I've had this same issue. Hardcoding the kerberos version didn't work.

Unfortunately we can't support AWS specific issues here. If you do find a solution, though, please post it so that others can benefit it.


Bugfix/fcidump naming

I run into a number of issues regarding the naming of the fcidump files in the Aiida Pyscf plugin. First, if the number of orbitals in the active space is greater than about 35, then the file name becomes too long and the job fails. Second, when you have large number of orbitals and you are computing a large number of fcidump files, it becomes much more difficult to find a correspondence to the active spaces given in the input. The only way for the user to do this is to define the same function that is used to create the name in the first place, which is adding a burdensome step. Specifically, I notice this with the Autocas plugin.
In my opinion, it is better to use the list index for maintaining the correspondence between the active spaces and the fcidump files. This solves the problems listed above.

Thanks @adam-grofe Could you please explain what the error is exactly? How does the "file name become too large"? What is an example filename that is too large. And is it too large for PySCF or is it even the filesystem complaining?

I can't remember which it was. I will do a quick run and post the results here.

Here is the output I get when running with 100 orbitals:

Traceback (most recent call last):
File "/anfhome/v-adamgrofe/scratch/aiida/ba/3f/fa0f-a8c5-4715-8ffc-5761c2a8afbb/script.py", line 92, in
main()
File "/anfhome/v-adamgrofe/scratch/aiida/ba/3f/fa0f-a8c5-4715-8ffc-5761c2a8afbb/script.py", line 79, in main
fcidump.from_integrals(
File "/anfhome/v-adamgrofe/.conda/envs/pyscf/lib/python3.10/site-packages/pyscf/tools/fcidump.py", line 153, in from_integrals
with open(filename, 'w') as fout:
OSError: [Errno 36] File name too long: 'active_space_0_1_2_3_4_5_6_7_8_9_10_11_12_13_14_15_16_17_18_19_20_21_22_23_24_25_26_27_28_29_30_31_32_33_34_35_36_37_38_39_40_41_42_43_44_45_46_47_48_49_50_51_52_53_54_55_56_57_58_59_60_61_62_63_64_65_66_67_68_69_70_71_72_73_74_75_76_77_78_79_80_81_82_83_84_85_86_87_88_89_90_91_92_93_94_95_96_97_98_99.fcidump'

I see, yeah that makes sense. I would just not use the counter as you do, but use the built in enumerate which is the typical approach in Python. We should also update the README.md. I will push a quick fix.


Making the Map Follow the Points

Hi luferau,
Is there a way to edit either the LabVIEW code or C# code in order for the map to follow the points like a GPS?
I'm looking for the map to automatically zoom to a certain level and then center around a point that was input.

I figured it out.
I added this code to AddPoint:
this.radMap.Zoom(13, true);
PointG location = new PointG(point.Latitude_deg, point.Longitude_deg);
this.radMap.MapElement.BringIntoView(location);


AlertManager not sending all alerts to Webhook endpoint.

Hi,
I'm using a webhook receiver for AlertManager to store alerts for pagination etc. For the most part, the webhook seems to be working just fine, but for some alerts, the webhook doesn't seem to receive a POST call at all from AlertManager.
Is there any way to troubleshoot this? For example, a way to trace alertmanager's outgoing HTTP calls to the webhook receiver?
The webhook endpoint is a Rails application server which also logs all incoming traffic, and after investigating, the missing alerts never show up in the logs (a POST request is never received).

What I expect: All alerts go through to the webhook endpoint
What I see: Only some alerts make it through to the webhook endpoint (Rails application that logs incoming requests)

I've attached a partial configuration, omitting redundant receivers etc. They're almost all the same.
Thanks,
Environment

System information:
Linux 4.14.186-146.268.amzn2.x86_64 x86_64

Alertmanager version:

alertmanager, version 0.21.0 (branch: HEAD, revision: 4c6c03ebfe21009c546e4d1e9b92c371d67c021d)
build user:       root@dee35927357f
build date:       20200617-08:54:02
go version:       go1.14.4
* Prometheus version:

	```
prometheus, version 2.22.0 (branch: HEAD, revision: 0a7fdd3b76960808c3a91d92267c3d815c1bc354)
  build user:       root@6321101b2c50
  build date:       20201015-12:29:59
  go version:       go1.15.3
  platform:         linux/amd64

Alertmanager configuration file:

global:
  resolve_timeout: 5m
  http_config: {}
  smtp_from<EMAIL_ADDRESS>  smtp_hello: localhost
  smtp_smarthost: smtp.office365.com:587
  smtp_auth_username<EMAIL_ADDRESS>  smtp_auth_password: <secret>
  smtp_require_tls: true
  pagerduty_url: https://events.pagerduty.com/v2/enqueue
  opsgenie_api_url: https://api.opsgenie.com/
  wechat_api_url: https://qyapi.weixin.qq.com/cgi-bin/
  victorops_api_url: https://alert.victorops.com/integrations/generic/20131114/alert/
route:
  receiver: device-alerts.hook
  group_by:
  - alertname
  - uid
  - group_id
  - stack_name
  - tenant_id
  - tenant_name
  - rule_stack
  - rule_tenant
  routes:
  - receiver: Test Presence Offline Notification Name
    match_re:
      alertname: ^(Test Presence Offline Alert Name)$
      group_id: 460599d4-3c4a-4311-a7d6-bdce6058672a
      tenant_name: ^(vle)$
    continue: true
    repeat_interval: 10y

  group_wait: 30s
  group_interval: 5m
  repeat_interval: 30m
receivers:
- name: device-alerts.hook
  webhook_configs:
  - send_resolved: true
    http_config: {}
    url: http://<IP_ADDRESS>/v1/webhook
    max_alerts: 0
- name: Test Presence Offline Notification Name
  email_configs:
  - send_resolved: false
    to<EMAIL_ADDRESS>    from<EMAIL_ADDRESS>    hello: localhost
    smarthost: smtp.office365.com:587
    auth_username<EMAIL_ADDRESS>    auth_password: <secret>
    headers:
      From<EMAIL_ADDRESS>      Smtp_from<EMAIL_ADDRESS>      Subject: 'Alert: {{ range .Alerts }}{{ .Labels.device_name }}{{ end }} | {{ range .Alerts }}{{ .Annotations.description }}{{ end }} | {{ range .Alerts }}{{ .Labels.uid }}{{ end }}'
      To<EMAIL_ADDRESS>      X-SES-CONFIGURATION-SET: ses-kibana
    html: '{{ template "email.default.html" . }}'
    text: '{{ range .Alerts }}{{ .Annotations.description }}{{ end }}Rule: {{ range .Alerts }}{{ .Labels.alertname }}{{ end }}Group: {{ range .Alerts }}{{ .Labels.group_name }}{{ end }}Device Name: {{ range .Alerts }}{{ .Labels.device_name }}{{ end }}Serial Number: {{ range .Alerts }}{{ .Labels.uid }}{{ end }}'
    require_tls: true
templates:
- /etc/alertmanager/templates/default.tmpl

Your best bet is to turn on debug logs (--log.level=debug). How do you know for sure that notifications are missing?

@simonpasquier So, we can see the alerts in prometheus, as well as in alertmanager, so the alerts fire properly.
On our webhook application side, we've logged everything, and we notice that not every alert that fires on alertmanager makes its way to our webhook endpoint. We can see the POST requests from alertmanager to our webhook for some of the alerts, but others are completely missing.

Honestly, the only reason we're using the webhook in the first place is because alertmanager doesn't support pagination when querying for alerts/groups. So we're using the webhook to receive all alerts/resolutions and storing them ourselves so we can manually paginate them. Our applications and metrics can generate tens of thousands of alerts which causes requests to alertmanager to sometimes timeout when the payloads are too large.

Your best bet is to turn on debug logs (--log.level=debug). How do you know for sure that notifications are missing?

@simonpasquier I've run debug logs on alertmanager, and can confirm that alerts are received by alertmanager, but not sent to the webhook; email integration does get sent though.
level=debug ts=2020-10-30T18:03:04.334Z caller=dispatch.go:473 component=dispatcher aggrGroup="{}/{alertname=~\"^(?:^(Jesse Logo Showing Alert Name)$)$\",group_id=~\"^(?:2223-4343-34333)$\",tenant_name=~\"^(?:^(test)$)$\"}:{alertname=\"Jesse Logo Showing Alert Name\", group_id=\"2223-4343-34333\", rule_stack=\"dev\", rule_tenant=\"test\", stack_name=\"dev\", tenant_id=\"1\", tenant_name=\"test\", uid=\"TEST-UNIT-001\"}" msg=flushing alerts="[Jesse Logo Showing Alert Name[d34154b][active]]"
level=debug ts=2020-10-30T18:03:05.592Z caller=notify.go:685 component=dispatcher receiver="IP Show Logo Alert Notif Name" integration=email[0] msg="Notify success" attempts=1
level=debug ts=2020-10-30T18:04:34.332Z caller=dispatch.go:138 component=dispatcher msg="Received alert" alert="Jesse Logo Showing Alert Name[d34154b][active]"
level=debug ts=2020-10-30T18:06:34.332Z caller=dispatch.go:138 component=dispatcher msg="Received alert" alert="Jesse Logo Showing Alert Name[d34154b][active]"
level=debug ts=2020-10-30T18:08:04.334Z caller=dispatch.go:473 component=dispatcher aggrGroup="{}/{alertname=~\"^(?:^(Jesse Logo Showing Alert Name)$)$\",group_id=~\"^(?:2223-4343-34333)$\",tenant_name=~\"^(?:^(test)$)$\"}:{alertname=\"Jesse Logo Showing Alert Name\", group_id=\"2223-4343-34333\", rule_stack=\"dev\", rule_tenant=\"test\", stack_name=\"dev\", tenant_id=\"1\", tenant_name=\"test\", uid=\"TEST-UNIT-001\"}" msg=flushing alerts="[Jesse Logo Showing Alert Name[d34154b][active]]"
level=debug ts=2020-10-30T18:08:34.332Z caller=dispatch.go:138 component=dispatcher msg="Received alert" alert="Jesse Logo Showing Alert Name[d34154b][active]"```

Shouldn't all alerts route to the default route (which is set as the webhook)?

I encounter similar issue using same alert manager version 0.21 but our prometheus is on v2.19. In our case, there are some POST requests that are missing even though there are active alerts.
Another issue is that seems some POST requests has missing information.
For example, if there is an active alert containing 5 nodes grouped together.
We will receive 2 POST request. The first one is incomplete because it has missing nodes.
{
    "alerts": [
        {
        ...
                "instance": "node1.demo.com:9100",
                ...
                "instance": "node2.demo.com:9100",
                ...
                "instance": "node5.demo.com:9100",
                ...
            "status": "firing"
        }
    ],
    ...
}

And the second POST requests is the complete one. With 5 nodes.
{
    "alerts": [
        {
        ...
                "instance": "node1.demo.com:9100",
                ...
                "instance": "node2.demo.com:9100",
                ...
                "instance": "node3.demo.com:9100",
                ...
                "instance": "node4.demo.com:9100",
                ...
                "instance": "node5.demo.com:9100",
                ...
            "status": "firing"
        }
    ],
    ...
}

@andrewipmtl

Shouldn't all alerts route to the default route (which is set as the webhook)?

no, alerts that will match the Test Presence Offline Notification Name receiver won't go through the top-level route.

@mvineza this seems a different problem.

For example, if there is an active alert containing 5 nodes grouped together.
We will receive 2 POST request. The first one is incomplete because it has missing nodes.

You have 5 alerts then and it may be that they are not sent at the same time by Prometheus.

@andrewipmtl

Shouldn't all alerts route to the default route (which is set as the webhook)?

no, alerts that will match the Test Presence Offline Notification Name receiver won't go through the top-level route.

Even though it has the continue flag to 'true' ?

Has this problem been solved? I have encountered the same problem. When grouping alarms, webhook will lose part of the alarms.,My configuration information is as follows
Image:         quay.io/prometheus/alertmanager:v0.21.0

route:
  receiver: webhook
  group_by:
  - alertname
  routes:
  - receiver: webhook
    continue: true
  group_wait: 30s
  group_interval: 1m
  repeat_interval: 4h
receivers:
- name: webhook
  webhook_configs:
  - send_resolved: true
    url: http://os-alertmgt-svc.prometheus-monitoring.svc:3000/api/v1/alert/webhook
templates:
- /etc/alertmanager/config/email.tmpl

In the alterManager page, I saw the following alarm. After passing the webhook, I could hardly see the complete alarm
alertname="aa"
4 alerts
alertname="we"
114 alerts
alertname="wewqd"
171 alerts

I've configured the webhook as another route on top of being the default route, and I'm still seeing some alerts not being sent through to the webhook.

@andrewipmtl can you share the new config?

Hello! Am running Prometheus 2.22.0 and Alertmanager v0.16.2 for Openshift Platform monitoring and am also observing some of messages not being sent to webhook endpoint. I do use only one default route for all messages in alertmanager.  Alertmanager runs in debug mode so I can easily follows all events. At the webhook endpoint level I log all of events from Alertmanager. Here are my findings:

Alertmanager always resolve messages (when tailing alertmanages logs) but not always send them to webhook. Looks like around 10-15 % of events are NOT POST'ed to webhook.
It seems like those alerts which are related to POD's availibility (like TargetDown,KubePodCrashLoop etc..) are those ones which are the most exposed to the issue. (I do use mostly default alerts set from Prometheus Operators from Openshift) Not sure if this observation is correct since those type of alerts are the most frequent...
There are some of alerts which are always properly resolved. (eg. my bash script for alerts generation, that I ran hundreds of times never resulted in a unresolved message )
Not sure if this has something to do with alert groupping. Since my alerts volume is low recently I disabled completely Alertsgroupping at alertmanager side (I set group_by: ['...']) to see if this has something to do with the issue or not.

Hello guys,
I experience a similar problem. Alertmanager does not dispatch incoming alerts to my root route.
I use Alertmanager 0.21, Prometheus 2.24.0. And I would to always send all my alerts to all my routes and root route.
Let's say my alertmanager.conf looks like:
global:
  resolve_timeout: 3m

# The root node of the routing tree.
route:
  group_by: ['alertname', 'job']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 6h
  # A default receiver
  receiver: mail-receiver

  routes:
  - receiver: gitlab-receiver
    continue: true
  - receiver: mattermost-receiver
    continue: true

receivers:
  - name: mail-receiver
    # some configuration...
  - name: gitlab-receiver
    # some configuration...
  - name: mattermost-receiver

The thing is that alerts are sent only to those child nodes and not via root route. So particulary in this case I get the alerts in Gitlab and in Mattermost, unfortunately I do not receive an email.
When I swap mattermost-receiver (will be default provider) with mail-receiver, I do not get Mattermost message.
Do you have any idea how to fix it please?

Hello guys,
I experience a similar problem. Alertmanager does not dispatch incoming alerts to my root route.
I use Alertmanager 0.21, Prometheus 2.24.0. And I would to always send all my alerts to all my routes and root route.
Let's say my alertmanager.conf looks like:
global:
  resolve_timeout: 3m

# The root node of the routing tree.
route:
  group_by: ['alertname', 'job']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 6h
  # A default receiver
  receiver: mail-receiver

  routes:
  - receiver: gitlab-receiver
    continue: true
  - receiver: mattermost-receiver
    continue: true

receivers:
  - name: mail-receiver
    # some configuration...
  - name: gitlab-receiver
    # some configuration...
  - name: mattermost-receiver

The thing is that alerts are sent only to those child nodes and not via root route. So particulary in this case I get the alerts in Gitlab and in Mattermost, unfortunately I do not receive an email.
When I swap mattermost-receiver (will be default provider) with mail-receiver, I do not get Mattermost message.
Do you have any idea how to fix it please?

@andrewipmtl can you share the new config?

`global:
resolve_timeout: 5m
http_config: {}
smtp_from<EMAIL_ADDRESS>smtp_hello: localhost
smtp_smarthost: smtp.office365.com:587
smtp_auth_username<EMAIL_ADDRESS>smtp_auth_password:
smtp_require_tls: true
pagerduty_url: https://events.pagerduty.com/v2/enqueue
opsgenie_api_url: https://api.opsgenie.com/
wechat_api_url: https://qyapi.weixin.qq.com/cgi-bin/
victorops_api_url: https://alert.victorops.com/integrations/generic/20131114/alert/
route:
receiver: device-alerts.hook
group_by:

alertname
uid
group_id
stack_name
tenant_id
tenant_name
rule_stack
rule_tenant
routes:
receiver: device-alerts.hook
match_re:
alertname: .*
continue: true
group_wait: 30s
group_interval: 5m
repeat_interval: 30m
receivers:
name: device-alerts.hook
webhook_configs:

send_resolved: true
http_config: {}
url: http://<IP_ADDRESS>/v1/webhook
max_alerts: 0
templates:

/etc/alertmanager/templates/default.tmpl`

@andrewipmtl can you share the new config?

`global:
resolve_timeout: 5m
http_config: {}
smtp_from<EMAIL_ADDRESS>smtp_hello: localhost
smtp_smarthost: smtp.office365.com:587
smtp_auth_username<EMAIL_ADDRESS>smtp_auth_password:
smtp_require_tls: true
pagerduty_url: https://events.pagerduty.com/v2/enqueue
opsgenie_api_url: https://api.opsgenie.com/
wechat_api_url: https://qyapi.weixin.qq.com/cgi-bin/
victorops_api_url: https://alert.victorops.com/integrations/generic/20131114/alert/
route:
receiver: device-alerts.hook
group_by:

alertname
uid
group_id
stack_name
tenant_id
tenant_name
rule_stack
rule_tenant
routes:
receiver: device-alerts.hook
match_re:
alertname: .*
continue: true
group_wait: 30s
group_interval: 5m
repeat_interval: 30m
receivers:
name: device-alerts.hook
webhook_configs:

send_resolved: true
http_config: {}
url: http://<IP_ADDRESS>/v1/webhook
max_alerts: 0
templates:

/etc/alertmanager/templates/default.tmpl`

@andrewipmtl hmm not sure why you configured a subroute. AFAICT this would work the same?
route:
  receiver: device-alerts.hook
  group_by:
  - alertname
  - uid
  - group_id
  - stack_name
  - tenant_id
  - tenant_name
  - rule_stack
  - rule_tenant
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 30m

@andrewipmtl hmm not sure why you configured a subroute. AFAICT this would work the same?
route:
  receiver: device-alerts.hook
  group_by:
  - alertname
  - uid
  - group_id
  - stack_name
  - tenant_id
  - tenant_name
  - rule_stack
  - rule_tenant
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 30m

@andrewipmtl hmm not sure why you configured a subroute. AFAICT this would work the same?
route:
  receiver: device-alerts.hook
  group_by:
  - alertname
  - uid
  - group_id
  - stack_name
  - tenant_id
  - tenant_name
  - rule_stack
  - rule_tenant
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 30m

I've tried it without subroutes either and it still doesn't receive all the alerts via webhook, some still go missing.

@andrewipmtl hmm not sure why you configured a subroute. AFAICT this would work the same?
route:
  receiver: device-alerts.hook
  group_by:
  - alertname
  - uid
  - group_id
  - stack_name
  - tenant_id
  - tenant_name
  - rule_stack
  - rule_tenant
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 30m

I've tried it without subroutes either and it still doesn't receive all the alerts via webhook, some still go missing.

Ok not sure why this happens but the only thing I can recommend is to run with --log.level=debug and investigate what happens when no notification is sent while you expect some.

Ok not sure why this happens but the only thing I can recommend is to run with --log.level=debug and investigate what happens when no notification is sent while you expect some.

Ok not sure why this happens but the only thing I can recommend is to run with --log.level=debug and investigate what happens when no notification is sent while you expect some.

The exact same thing happens as when I tested it in an earlier debug session:
https://github.com/prometheus/alertmanager/issues/2404#issuecomment-719715603
Alerts show up, but aren't sent to the webhook endpoint.

same with me

Facing same.

Forgive me if I misunderstood your initial question, but I think y'all didn't get the point.
The default receiver for some route node (including the top-level node) is only used if your alarm didn't match any matchers declared at that level of the routing tree. Your alarms enter the routing tree from the top and traverses it down until they match some matcher and then that node's receiver receives the alarm.
If you set "continue: true", the alarm will continue matching the siblings, meaning that it will try to match another matcher at the same level.
Therefore, if you want your Webhooks to receive all the alarms, it must be declared properly in combination with "continue: true" in all levels that your alarm matches.
Use amtool to test your routes, as described in prometheus/alertmanager

@rmartinsjr I'm not sure what you mean by sibling routes, all the routes that -should- alert are at the same level, including the one for the webhook, and all routes have continue: true defined, yet I'm still seeing this behavior.
It's also intermittent as some alerts would go through, and many would not. There's no pattern as it does not always seem to be the same alerts randomly passing through to the webhook either.

@rmartinsjr I'm not sure what you mean by sibling routes, all the routes that -should- alert are at the same level, including the one for the webhook, and all routes have continue: true defined, yet I'm still seeing this behavior.
It's also intermittent as some alerts would go through, and many would not. There's no pattern as it does not always seem to be the same alerts randomly passing through to the webhook either.

@andrewipmtl, reviewing all posted configurations, I believe you're using the simpler one that simonpasquier posted... With that supposition, are you sure it isn't the group_by that is grouping multiple alerts into one?

@rmartinsjr I have never used it before -- but after using it for the first time just now, I get a "tree" map generated where it looks like every single alert branches from a single node which is the device-alerts.hook. So unless I'm wrong -- every single alert should be hitting the webhook.

In case this helps anyone, I was running AlertManager through prometheus-operator, and I experienced the exact same problem.
In my case the cause was that alert-manager was matching only alert that contained the right namespace label. There is an issue about that in https://github.com/prometheus-operator/prometheus-operator/issues/3737

@luislhl , by namespace what exactly do you mean? I have no namespaces defined in my config file, is that the issue? I wasn't aware of any namespace matching if none were provided.

Hey, @andrewipmtl
By namespace I mean a Kubernetes namespace, my bad I didn't make it clearer.
I have deployed Alertmanager in a Kubernetes cluster by using the Prometheus Operator.
The final Alertmanager config I get has this matcher to select only alerts containing a namespace label with value kube-prometheus:
global:
  resolve_timeout: 5m
route:
  receiver: "null"
  group_by:
  - job
  routes:
  - receiver: kube-prometheus-slack-alerts-slack-alerts-warning
    group_by:
    - alertname
    matchers:
    - namespace="kube-prometheus"
[...]

The issue I linked in my previous comment has more info about this behavior.

We have similar issue. Some alerts are not posted to webhook.
And I have a feeling that this is because alert is resolved within group_wait interval.
As example, group_wait set to 30s and alert lasts just 20s.
Is that possible?
P.S. Alertmanager v0.21.0, send_resolved not specified (supposed to be true by default).

same problem, alert manager and prometheus shown the alert but not send data to webhook:
ts=2023-01-08T12:31:28.676Z caller=dispatch.go:163 level=debug component=dispatcher msg="Received alert" alert=InstanceDown[c136526][active]
ts=2023-01-08T12:31:38.677Z caller=dispatch.go:515 level=debug component=dispatcher aggrGroup="{}/{}:{job=\"node\"}" msg=flushing alerts=[InstanceDown[c136526][active]]

global:
receivers:
  - name: "n8n"
    webhook_configs:
      - url: https://sample.tld/webhook/alertmanager
        send_resolved: true
        http_config:
          basic_auth:
            username: alertmanager
            password: securePassword
          tls_config:
            insecure_skip_verify: true
route:
  receiver: n8n
  group_by: ['job']
  group_wait: 10s
  group_interval: 4m
  repeat_interval: 2h
  routes:
  - receiver: n8n
    continue: true

@mhf-ir Did you find a solution for this? facing same issue now on prometheus/alertmanager:v0.24.0

@mhf-ir Did you find a solution for this? facing same issue now on prometheus/alertmanager:v0.24.0

Still no solutions provided.

Still no solutions provided.

thanks @andrewipmtl , I mainly having issues sending the alert through AWS SNS

I am facing the same issues while sending slack messages with webhook and email as well.
@andrewipmtl - Did you get past this issue ? I do not see any solution or further suggestions on the thread.

@andrewipmtl I see group_interval is 5m, are you certain that all alerts are firing for at least 5 minutes, as otherwise some alerts might get resolved before a notification is sent.

issue with webhook...not resolved yet !

thanks @andrewipmtl , I mainly having issues sending the alert through AWS SNS

Does anyone found the solution to integrate prometheus with AWS SNS?

issue with webhook...resolved, Actually the rocket chat .js file to be updated.

@sahaniarungod can you please elaborate?

Is this still an Issue?
Im seeing alerts in Prometheus and AlertManager, but sometimes I get almost empty alert in Slack and sometimes values are populated using the 0.26.0 version

@rsuplina
can you try using group by parameters and group your alerts ?
group_by:         - severity         - alertname         - team         - clusterName         - container         - exported_container

Hi @aroundarmor-cldcvr  thanks for your reply,
I have tried to change to:
route:   receiver: 'slack-notifications'   group_by: ['severity', 'cluster_name']   group_interval: 1m   group_wait: 20s   repeat_interval: 2m
But still what would happen is some alarms would arrive with full data, and then if I change to some other instances that also does not exist and  restart docker services (Prometheus-alertmanager) it will then again start send Notifications which are missing values .
Here is a full description of my error I wonder if. this is a bug with alertmanager ?
https://stackoverflow.com/questions/77908650/prometheus-alertmanager-slack-messages-not-fully-showing

facing the same issue today. i'm seeing all the alerts in any channels except webhook which some of them are missing.

Hi everyone, I have exactly the same case. Due to the characteristics of the monitoring system, I can not send one aggregate alarm, but send them in individual webhooks, with a large number of alarms such as 50, maybe 7 are delivered, checking the logs on the recipient side shows as if the reqeusts do not arrive. Have any of you observed this problem in version v.0.27? Perhaps the solution is to send the alerts to some queue like AWS SNS?


admin1Code, admin2Code are returned as string instead of object in API response

Hi Thomas,
Thank you for building this extremely useful application! We have been using it in our app for a few months now, and the results have been accurate 99% of the time.
I noticed that in some cases, the admin1Code or admin2Code returns a string instead of an object. Is this expected behaviour? Here are the requests to reproduce the issue:

"admin1Code" : "00"

curl --location 'http://SERVER_URL/geocode?latitude=-16.48679&longitude=-151.74102'

"admin2Code" : "00"

curl --location 'http://SERVER_URL/geocode?latitude=52.51667&longitude=13.36667'
Please let me know if you need any other information.

Could you verify if this is a problem in the downloaded GeoNames raw data? The app mostly just reflects what it finds there, without much processing if I recall correctly.

Hi Thomas, thank you for your response. I appreciate your input on this matter. Unfortunately, I do not have the bandwidth to investigate this further at the moment. However, since this is not currently blocking my progress, I will aim to revisit it when I have more time available in the future.

It seems to be related to use use of the option countries: [...] in the initialisation.
When I select a specific country, e.g., "IT" only a string is returned for adminNcode  while if there are no countries it works as expected.


Migration

@neverpanic As we discussed, I'd like to get these changes merged into master in order to give them greater exposure and hopefully encourage testing by others.

@umeshksingla FYI, your code from GSoC finally landed!


bump tested versions

Bumps the tested python versions, 3.5 and 3.6 are no longer supported
https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

Closing, addressed in #81


Fix placeholder transform resolution issue in calculation summary pages

What is the context of this PR?
Fixes an issue where placeholders were not being evaluated correctly on Calculation Summary pages (CS, GCS) as the dependency map _placeholder_transform_section_dependencies_by_block was not being being populated correctly for these block types.
Previously, Calculation Summary blocks were only accounting for any placeholders set in the specific CS/GCS block in the schema, but Calculated Summary pages can render question text (containing placeholders) from their dependent questions, so the Calculation Summary page may have a dependency on another block which then may have dependencies on other sections. The logic has now been updated to account for this and update the dependency map correctly.
The code was added to support Grand Calculated Summaries but at the moment it is not possible to add any tests for this as unlike Calculated Summaries they do not render question text from other blocks.
How to review
Use the test_placeholder_dependencies_with_calculation_summaries schema to test the change.

Launch test_placeholder_dependencies_with_calculation_summaries
Don’t accept default reporting period, enter new values and complete section 2
Go back to Section 1 summary screen, change dates back to default values by answering ‘Yes, I can report for this period’ for the first question.
Go back to Section 2 and get to the calculated summary by changing one of the answers that are used on the CS.
Check that the dates set in the metadata are rendered on the Calculated Summary page, not the dates that were previously entered by the user.

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Bug: Period Date changes not reflecting in piped questions


docs(readme): update mongo supported version

:tada: This PR is included in version 1.20.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


mediapipe/holistic incorrect handling of connected models

currently @mediapipe/holistic solution performs

delete what it considers duplicate landmarks from result
reconnect different models by artificially drawing a line between them

for example, it deletes results.poseLandmarks[POSE_LANDMARKS.RIGHT_WRIST]
and then to make hand "appear" connected to body, it draws a line between:
[results.poseLandmarks[h.POSE_LANDMARKS.RIGHT_ELBOW], results.rightHandLandmarks[0]
which looks decent enough on 2D canvas, but when visualized in 3D you can see that pose and hand landmarks each have its own relative z-axis and hand appears in a very wrong place
much better solution is

do not delete results.poseLandmarks[POSE_LANDMARKS.RIGHT_WRIST] (leave it as-is)
renormalize z-axis values for all landmarks in results.rightHandLandmarks by adding z-axis value from results.poseLandmarks[POSE_LANDMARKS.RIGHT_WRIST]
(no need to modify x and y values as they are similar enough between models)

same applies to face mesh model - it also needs to be corrected to have position relative to body as currently floats behind it by when visualized in 3d.
platform: this happens in javascript solution, although i have not checked other language ports and its likely same applies there
version: @mediapipe/holistic 0.5.1635989137
browser: chrome 107 on windows 11

Hi @vladmandic,
Could you provide the complete error logs and steps followed to reproduce the issue from our end. Thank you!

@kuaashish this is not about error logs, its about visually wrong locations of connected models (hand and face when compared to pose).
for example, see screenshot - with input video, 2d overlay and 3d view looking from the side - i've circled the incorrect position of the hand in 3d view.

and then look at the second screenshot after i manually correct the z-axis values for hand landmarks by adding z-axis value from pose landmarks wrist.

Hi @ivan-grishchenko,
Could you please look into this issue about the incorrect handling of Javascript holistic solution.

Hello @vladmandic,
We are upgrading the MediaPipe Legacy Solutions to new MediaPipe solutions However, the libraries, documentation, and source code for all the MediaPipe Legacy Solutions will continue to be available in our GitHub repository and through library distribution services, such as Maven and NPM.
You can continue to use those legacy solutions in your applications if you choose. Though, we would request you to check new MediaPipe solutions which can help you more easily build and customize ML solutions for your applications. These new solutions will provide a superset of capabilities available in the legacy solutions.

it does not answer the question if its fixed?
you're moving users to new solution which is ok to do, but since issue exists, it shouldn't be on user to migrate just to check if issue exists in the new solution and then open new issue for it then.

@vladmandic,
This is a legacy solution And We will be not able to fix this issue.


Update scopes used in OAuth

Description

makes all scope parameters in OAuth and App methods optional. Endpoints not receiving a scope parameter will default to granting "read" permission.

removes default parameter value from Scope constructor. Users will need to define a certain scope if they want to use it. Closes #116.

adds all scopes as defined by Mastodon, marks existing scopes FOLLOW and ALL as deprecated.

removes all internal usage of the now deprecated ALL scope. Closes #143.

moves deduplication of scopes from a separate function into the one building the parameter string. This avoids unnecessarily throwing an IllegalArgumentException. Closes #381.

Type of Change

New feature

Breaking Changes

Scope constructor can no longer be called without explicitly enumerating scopes that should be requested.
Scope.NAME enum has been replaced with hierarchically arranged scope definitions in the class. Example: Scope.Name.READ becomes Scope.READ.ALL
Existing FOLLOW scope has been removed. Use individual child scopes of READ and WRITE instead.
Existing ALL scope has been removed. Use individual scopes necessary for your use case instead.

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Mandatory Checklist

[X] I ran gradle check and there were no errors reported
[X] I have performed a self-review of my code
[X] I have added tests that prove my fix is effective or that my feature works
[X] All tests pass locally with my changes
[X] I have added KDoc documentation to all public methods

@bocops Merged! Thanks for the efforts 🚀
Could you please make sure that other PRs that may no longer be necessary after these changes are closed? You’ve already linked the affected issues, so those should be fine I assume?

Looks good regarding issues, thanks!
@andregasser the only remaining PR in this area is your #119 - I think that is no longer necessary. Can you close it as time permits?


Improove overdue tickets email notification

Currently it notifies just once. I think with a minor modifications we can do it a bit more flexible:
Add two settings:

UNPAID_ORDER_NOTIFICATION_REPEAT = 3  # How many times we should repeat the email notification
UNPAID_ORDER_NOTIFICATION_REPEAT_DELAY = 5  # delay in days

Update order model with new field:

add unpaid_notification_sent_amount field, it should be integer, default 0.

In payments.utils.py:
Let's update order to filter for unpaid_notification_sent set to NULL or unpaid_notification_sent is less than UNPAID_ORDER_NOTIFICATION_REPEAT_DELAY and unpaid_notification_sent_amount is less than UNPAID_ORDER_NOTIFICATION_REPEAT. After notification is send increase unpaid_notification_sent_amount.
Modify also the email template to have the link to order. It should be part of the email so user can review it.

I'd like to do this.


Storage Bucket and object make public samples

Created storage_set_bucket_public_iam sample & test
Reassigned storage_make_public to correct sample

MakePublic test is failing....

Failure is a Kokoro internal failure after all tests were green. Merging.


Allow one to specify module to get_type_hints

Currently it is trying to guess the module, but this is not always possible. For example, it does not work for me if I call get_type_hints while the module is being defined and module does not yet exist.
A workaround for me is that currently I set im_class attribute on the function I want to get type hints for, but I think it might be cleaner if there would be an optional argument get_type_hints.

Using get_type_hints within a module while that same module is being defined sounds like evil zone (but honestly, pytypes already needs to navigate evil zone from time to time^^). So, if such an additional parameter helps to solve some difficult situations it's fine for me.
However, is it actually the right solution to provide module as a new parameter? Wouldn't it be better to directly provide the class? I suppose it boils down to this call where the module would be required. _get_types already provides an optional class parameter that would avoid that entire branch. If it would be sufficient to provide the class, adding this parameter would be as easy as forward it through _get_type_hints, get_types (should stay compatible to get_type_hints anyway) and _get_types.

Oh, I think class would be perfectly fine. I do not remember why I proposes to pass a module. Currently I am setting im_class anyway, which is a class. :-)
So yes, class would be great.


[NEW] missing logo and layout content on login screen

Description

On the login screen the logo is missing and references to information from Layout/Content like Login Terms.
The content of the field Login Terms should be displayed on the login page in order to comply with legal obligations.
Devices and Versions

Your Rocket.Chat.Android version: 3.1.0.
Your Rocket.Chat Server version: 0.69.2 and 0.72.0-develop (open.rocket.chat)

Mobile device model and OS version: BQ Aquaris X5 Plus and Android 7.1.1
Steps to reproduce
Connect to a server and go to login screen.

Browser login screen:

Login terms are present in the "..." button. We don't plan to add the logo to this screen right now (because it takes too much space). Thank you!

Ah, didn't get that with the "..." button. Thanks.


Default rules for contenarized databases

I think that adding some rules that have similar behavior like adding standalone Zabbix agent to standalone VM with database containing features like:

detecting locks
detecting deadlocks
transaction rates
connections

Initially I thought about databases like postgresql and mongo
I believe that such behavior would enchance security of critical data and apps stability

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale


PubSub Streaming Sample Issue.

I am trying to run this sample on google cloud shell with maven version 3.6.3.
Following Issue.
failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.0.0:java
Please help me.

@AristoK3 Thanks for flagging this!
The command line args in our docs needed an update. I just tried the following in Cloud Console and it worked:
mvn compile exec:java \
  -Dexec.mainClass=com.examples.pubsub.streaming.PubSubToGcs \
  -Dexec.cleanupDaemonThreads=false \
  -Dexec.args="\
    --project=$PROJECT_NAME \
    --region=$REGION \
    --inputTopic=projects/$PROJECT_NAME/topics/cron-topic \
    --output=gs://$BUCKET_NAME/samples/output \
    --gcpTempLocation=gs://$BUCKET_NAME/temp \
    --runner=DataflowRunner \
    --windowSize=2"

A fix is coming!


Firefox on windows icon not showing properly

The solution I found was to Increase the font size to separate the dot from 'i'.

On Windows, the letter 'i' is not centred perfectly as on Mac.

The font is not supported on windows. The solution was to change it to a web-safe font.


Error in routerview

Version
3.0.1
Reproduction link
https://jsfiddle.net/posva/km2qpwx7/
Steps to reproduce
while using routerview with PrimeVuew Steps component get this error
parentComponent.ctx.deactivate is not a function.
Unhandled error during execution of scheduler flush. This is likely a Vue internals bug.
at <KeepAlive formData= {data: {…}} onPrev-page=fn onNext-page=fn  ... >
at <RouterView formData= {data: {…}} onPrev-page=fn onNext-page=fn  ... >
at <RequestSteps onVnodeUnmounted=fn ref=Ref< Proxy {…} > >
at
at
What is expected?
No error
What is actually happening?
throws error

sine the setup requires multiple components, not able to create a JSFiddle or other minimal reporoduction

We can't understand the problem you without a reproduction. Also this is not the route repository.


Add Unknown reward method

Current dependencies on/for this PR:

feature/proof-of-stake

PR #904   👈

This stack of pull requests is managed by Graphite.


[SPARK-25474][BACKPORT-2.3][SQL] Support spark.sql.statistics.fallBackToHdfs in data source tables

What changes were proposed in this pull request?
Backport the commit https://github.com/apache/spark/commit/485ae6d1818e8756a86da38d6aefc8f1dbde49c2 into SPARK-2.3 branch.
How was this patch tested?
Added tests

Test build #108314 has started for PR 25285 at commit b9f3be1.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13412/
Test PASSed.

ok to test

Test build #108317 has started for PR 25285 at commit b9f3be1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13414/
Test PASSed.

Test build #108317 has finished for PR 25285 at commit b9f3be1.

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

Merged build finished. Test FAILed.

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

Test build #108314 has finished for PR 25285 at commit b9f3be1.

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

Merged build finished. Test PASSed.

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

cc @dongjoon-hyun Kindly review

Thanks @dongjoon-hyun


Tickets/dm 26958

Did this change pull things down to the same ballpark as what we get from validate_drp?
Yeah, it's similar now. Previously we were getting AD1~20-25 mas, and now it's ~8-15 mas. Not a huge difference...


Add 3D Touch App Shortcuts for Current Location, Bookmarks, and Recent Locations

Issue #524 Add 3D Touch App Shortcuts for Current Location, Bookmarks, and Recent Locations

This looks great! Please:

[x] Fill out ICLA
[ ] Change the two things mentioned above
[ ] Squash the resulting 2-3 commits

and I'll get it merged. Thanks again!

I made the two changes and squashed the commits.
Thanks Aaron.
John

@jgriffin thanks, John! Shoot me an email at<EMAIL_ADDRESS>if you'd like to join the OBA beta program. I've been buried under work at my real job for the past few weeks, but I'm looking to get a 2.5 release out the door soon, and should be pushing beta updates out regularly starting soon.


Is there a way to apply colision to a heightmap / terrain?

Ive got a project with a pretty large terrain (1000x1000), it uses a a plane with a heightmap to apply mountains / rivers and other 3d stuff like that. Is there a way to apply collision that corresponds with the height?
this is on windows 0.9.6

Hello
Yes there is you can use a HeightField physics shape to achieve this.
You will need to call this from code inside of a script there is no GUI for the Heightfield object, but it should actually fairly easy to add.
Thanks a lot!


install and setup overview

overview doc updated

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


Fix misplaced sections placement

Some sections have been misplaced as part of the initial data entry. This command will fix their placement to be direct children of the SectionIndexPage.

@volloholic


nmake / make install has indent problems on make file. Not running. (1.1.1)

I tried running nmake or make test, install. The makefile has a problem with line 56 and I can't figure out why it doesn't run.
Any assistance would be welcome!

Can you show us that line, and preferably a few surrounding lines as well?

This is line 56, and when I run make I get:

I read other people with this issue and they mentioned something about indentation. I played around a lot with it  and no luck.

If you are configuring for Windows you are supposed to use "nmake" not "make", e.g.
perl Configure VC-WIN64A
nmake
nmake install

You seem to be attempting make install?

Yes I attempted make because nmake was giving me another error:

which looks like an installation problem with VS, but I've reinstalled it multiple times now.
nmake is in the system path too.

Is there more than the fatal error U1077 in the nmake output?

Ah, the actual error is the limits.h one.
How do you set up your VC environment before launching nmake?

(Noting that limits.h is a standard header in the C language and must be present for a C compiler to be usable.)

Oh I see, is there something wrong with my compiler then? Is there a way to fix the file?
Best,

@viniciusdel  you could start by answering the question from levitte:

How do you set up your VC environment before launching nmake?

I did VC-WIN64A as instructed

I'm not entirely sure if that's what he asked.

You are running nmake (and `Confnigure) in some kind of cmd.exe shell environment.  How did you open that cmd.exe window (e.g., what path did you click on in the start menu, etc.)?

In order to have a usable environment you have to have a number of environment variables correctly set. The typical way to do this is to start a Visual Studio Command prompt (rather than using the normal command prompt). This will set up all the environment variables for you. Alternatively you can run the script vcvarsall.bat which comes with Visual Studio.

I went into the OpenSSL folder and typed CMD up top to open it

I ran nmake from the VS terminal in the SSL directory, it prints this non-stop:

That's definitely not going to work as-is.
(What version of visual studio do you have?)
There is probably something like a "Developer Command Prompt" in the start menu that would work, and at least some (older?) versions of VS have a "vcvarsall.bat" script that can be run from any command prompt to set up the environment properly.

Ok I ran the .bat you mentioned, but it can't find the .h file. I tried running it on CMD and VS command prompt.
The developer command prompt that you mentioned I think it's from Perl, at least the one that pops up. It doesn't find it either..

You need to run the "Developer Command Prompt for Visual Studio". E.g., see
https://docs.microsoft.com/en-us/dotnet/framework/tools/developer-command-prompt-for-vs

Yes sir, I tried with that too

I ran nmake from the VS terminal in the SSL directory, it prints this non-stop:

it was this one

I ran nmake from the VS terminal in the SSL directory, it prints this non-stop:

The pasted output seems at least superficially similar to what is expected from a normal build.  Have you tried letting it run for a while (an hour should be plenty) to see if it's really looping over the same files?

I will try letting it run that long, will update in a bit.

Oh, did you expect a normal working build to be silent?  Nope, ours is quite verbose

So, it ran for about 2mins, then it encountered this fatal error:

I don't even remember if I downloaded the x64, but that might be it I'm assuming.

That looks like a mismatch between the VC-WIN64A that you gave to Configure, and the particular developer tools command prompt that you're using.  You could (from a clean tree) instead use VC-WIN32 to get a 32-bit build, or look for the corresponding 64-bit developer tools command prompt (also requires a clean tree).

sounds like perhaps this was an attempt to configure/build for VC-WIN64A with the developer prompt configured for native x32 (via vcvarsall.bat x86)
Marking as inactive, to be closed at the end of 3.4 dev barring further input


more contrast for focus tab

its not clear that which tab is focus in tab bar, so you can make it more contrast.
genesis-ui's distraction free is a pretty good example for imitate :-)

@t7yang, are you referring to the tree view (on the left)? Would you mind posting a screenshot for reference?

the tab bar, actually. below the screen shot from Genesis (fore) and the Pristine (back).
the Genesis UI make more easier to distinguish between the active tab and inactive tab, whereas Pristine is more harder even with the indicator (its become worse if you open a lot of tab).

The background-color of the active tab in pristine-ui is based on the background of your syntax theme, @t7yang.
See the following two examples:
Using duotone-dark-syntax

Using duotone-light-syntax

I'm curious, what syntax theme are you using currently?

one-dark-material-syntax 😄
OK, now i know, thx.
try switching among duotone-dark-syntax, one-dark and one-dark-material, still having the some problem...


Add plugin build tool

It may be useful to have a simple tool that uses the version of the proxy to build plugins that work with it. Maybe plugins could even be built from source automatically if a package is found in the plugin directory and the correct version hasn't been built yet; This could greatly reduce versioning issues for end users.

Both features exist now.


Multiple Radius tags for rendering dates is redundant

Radiant defines two Radius tags for rendering dates, <r:date /> for outputting generic dates using Ruby's strftime and <r:rfc1123 /> which always outputs RFC-1123 formatted dates.
r:date has two attributes, format, and for. The for attribute allows the user to select between the current datetime, the datetime when the page was published, or the datetime when the page was last updated.
r:rfc1123 however, has no such functionality. Which means if the user wants to get the current datetime in RFC-1123 format, they must use the r:date tag, and write a format string for RFC-1123.
The functionality of these two tags feels either incomplete, or redundant.
I see two possible fixes for this.

Allow the r:date tag to accept the string "rfc1123" for the format attribute, and eventually deprecate the r:rfc1123 tag.
Add a for attribute to the r:rfc1123 tag that behaves like the one in r:date.

The problem with the first solution, is that it (sortof) breaks the point of the format string (or at least makes the code a little less elegant). While I can't imagine this really being a problem, it just feels a wrong.
The second solution still requires multiple tags, however, it makes the r:rfc1123 tag much more useful (especially for RSS feeds with often contain <lastBuildDate /> and <pubDate /> tags).
Implementing both solutions (I feel) is just redundant, however, for the purposes of illustration, I threw together a quick patch that does both: https://gist.github.com/1935006
Do people think one or the other solution would be better, or am I creating a problem where one doesn't exist?
I didn't make this issue a pull request, because I definitely think only one of these changes needs to be implemented. I'll actually stick (part of) the patch in my repo and merge it if there's a general consensus that one or the other should be implemented.

Thanks for doing this, Sam.
I like the first option best. I suspect the r:rfc1123 was added as a shortcut so that you wouldn't have to manually handle the format.
We should be able to use an I18n.config entry to set the format as well. So your format="rfc1123" could just be in a locale file.

Sounds good. I think that's probably the better way to do things too, so if no one else comments or has any suggestions by the time I get home I'll go ahead and update this to a pull request.
Should I move r:rfc1123 into the deprecated_tags.rb file as part of the commit, or is there a specific policy on deprecating the standard tags?

Yup. Move it to deprecated, but commit to a branch, not master.
Also, raising this question on the dev mailing list is a good idea to get other opinions.

Will do, thanks.

One other option would be to add an rfc1123="true" attribute to the r:date tag that would override the format option if present.
rfc1123 is actually there to make it easy to write XML feeds as they tend to require this format. I don't think this should be moved into a localization file. It's much better for Radiant to behave the same across all environments. Especially because you can define date formatting using the format option on r:date.
My two cents.

That might work too; the only reason that I could see for not wanting a separate rfc1123 attribute is because it may be that in the future standards change and we want to include a shortcut for some other commonly used formatting string. In this case, it would seem cluttered to check for multiple attributes (and what happens if the user specifices rfc1123="true" and rfcxyz="true"?).

i prefer option #1; but just get rid of  <r:frc1123> and leave <r:date> as is.
<r:frc1123> feels too specifically about blogging to me; so should be part of a blogging extension or the archive extension or something like that.

The option should not move to a locale officially. I'm saying that you can get this feature today with a locale

I attached a potential fix. What do you think? It's a little weird, since using format="rfc1123" will always be in GMT, whereas using a format string will localize it, but I figured continuing to do it that way will meet existing users expectations.
Also, using a format string will not preserve the time part of the datetime. Should either of these things be changed?

First things first, you have no specs.
Why will using this format attribute always be in GMT? Do you mean UTC? What makes that restriction? Would it not read from the Rails timezone setting or is that how the CGI library behaves?
I don't think that the locale override is a widely known feature, so restricting it with a special argument might not have great impact, but we should consider the impact nonetheless.
Lastly, this might affect our goals with this, I want to introduce an extension that will help us manage unique types of content. Sheets gives us a better way to manage CSS and JS, but we should have something like that to make creating and managing RSS/Atom/robots.txt easier.
If the goal of the original rfc1123 tag was to provide for feeds, a new extension could take care of that responsibility. For that reason I think the rfc tag should be deprecated.

Specs: Yes, those definitely need to be updated. That was an oversight on my part, which I'll definitely fix before this gets merged anywhere.
Timestamps: The CGI library behaves that way, so I left it for backwards-compatibility with the r:rfc1123_date function. Should be an easy fix if you think it would be better to use the configured time zone. The current implementation of r:date doesn't maintain the time stamp (so it will display the date, but use 00:00:00 for the time portion), so that will probably need to be updated too.
New extension: Sounds like a plan.


OCM-5736 | feat: Make auth and device code flags visible

https://issues.redhat.com/browse/OCM-5736
Changed

Make auth and device code flags visible

Tested

Flags should be visible in rosa login --help : tested

/ok-to-test


The link to moonbeam's test developer private key page could not be found

https://github.com/gakonst/ethers-rs/blob/19f7a9324394ab2c1e06d6dfc7666cbc55f56aab/ethers-core/src/utils/moonbeam.rs#L7

it's here now
https://docs.moonbeam.network/builders/get-started/networks/moonbeam-dev/#pre-funded-development-accounts
wanna update this?


404 when trying to install v0.31.0 via electron-prebuilt

Trying to install electron via the electron-prebuilt package, but it seems there aren't any downloadable releases for 0.31.0:
 npm install electron-prebuilt -g
/usr/local/bin/electron -> /usr/local/lib/node_modules/electron-prebuilt/cli.js

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/electron-prebuilt
> node install.js

Downloading electron-v0.31.0-darwin-x64.zip
Error: GET https://github.com/atom/electron/releases/download/v0.31.0/electron-v0.31.0-darwin-x64.zip returned 404

/usr/local/lib/node_modules/electron-prebuilt/install.js:15
  throw err
        ^
Error: GET https://github.com/atom/electron/releases/download/v0.31.0/electron-v0.31.0-darwin-x64.zip returned 404
npm ERR! Darwin 14.5.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "electron-prebuilt" "-g"
npm ERR! node v0.12.7
npm ERR! npm  v2.12.1
npm ERR! code ELIFECYCLE

Notice this line here: Error: GET https://github.com/atom/electron/releases/download/v0.31.0/electron-v0.31.0-darwin-x64.zip returned 404
And when you view the electron releases in github (https://github.com/atom/electron/releases) there isn't a Downloads section for v0.31.0

I can successfully install v0.30.5 (via npm install<EMAIL_ADDRESS>-g)

Happening to me too, it was working this morning though. Seems like the files got removed or something.

I'm having this error, too. After I've changed everything to adopt 0.31.0... (registerProtocol and all)
:'(

Somehow the release became a draft, maybe a cat walked on someone's keyboard? Anyway I clicked the publish button and things are working now.

Thanks, @zcbenz :)


External Dependencies of DAAL

I noticed DAAL library is depended on external libraries like "libdaal_mkl_sequential.a  libdaal_mkl_thread.a  libdaal_vmlipp_core.a", what are these libraries? Can I use DAAL without these external dependencies.
I was looking at Cholesky Factorization for batch processing, I want to use DAAL framework but use different optimization kernel of Cholesky, will this be possible.

@vkirangoud, DAAL depends on external functional like BLAS, LAPACK, mathematical functions, random number generators, sorting, data compression algorithms and so on. The libraries you mentioned contain necessary implementations. I see two options to use another implementation:

DAAL has additional abstraction layer for external functions (for example have look at service_lapack.h), so you can push new implementation underneath of you own abstraction layer.
Use new external libraries with the same ABI.

I want to use DAAL framework but use different optimization kernel of Cholesky
Do you want to use DAAL interface while having your own Cholesky implementation or you just want to replace call to LAPACK inside of existing DAAL algorithm?

Here is guide describing how to add custom algorithm to DAAL. To minimize efforts you may inherit your algorithm's class from cholesky::Batch and override the method compute.

An addition to the comment of @RuslanIsrafilov .
@vkirangoud , you will need to inherit two classes: cholesky::Batch which implements an interface of the algorithm and cholesky::BatchContainer which contains an implementation of the algorithm. And the compute() method should be overridden in the class derived from cholesky::BatchContainer.


OMOP etl assumes "birth_datetime" column in person is present

In this line the call to cast_to_datetime(batch, "birth_datetime") fails because the column "birth_datetime" doesn't exist in my data.
if table_name == "person":
    # Take the `birth_datetime` if its available, otherwise
    # construct it from `year_of_birth`, `month_of_birth`, `day_of_birth`
    time = pl.coalesce(
        cast_to_datetime(batch, "birth_datetime"),
        pl.datetime(
            pl.col("year_of_birth"),
            pl.coalesce(pl.col("month_of_birth"), pl.lit(1)),
            pl.coalesce(pl.col("day_of_birth"), pl.lit(1)),
            time_unit="us",
        ),
    )

Sorry I actually have the column just didn't export it.
Leaving this open in case you want to be robust to the case where the column doesn't exist. I'm not sure what the common practice is with non-required columns in the CDM.

I think it's better to keep using the column as is because we want this code to crash when invalid OMOP data is provided. It's better to loudly fail than to silently lose data IMHO.
I'm going to close this issue, but feel free to reopen if you run into issues.


dtype error rotary embedding

Hi,
I ran into dtype error when using rotary embedding. I am using fp16 but the tensor dtype get converted to float32 at apply_rotary_pos_emb().
Remove @torch.jit.script and the error disappears. This might be an issue with torchscript, but I wonder if there's a workaround.
Thanks

I see. I haven't been using rotary embedding recently, it was for a one-off experiment at some point.
I adapted it from xformers's implementation (as mentioned in the source code), feel free to change it how you see it.

Hi Tri Dao,
Thank you for the quick response. I don't have much experience with torch scripting so I only recast the output tensor. Please see pull request.
Thanks

Thanks for the PR, I've merged it.
Much appreciated!


Orderable Updates Position when Destroying Parent Embedded In

When you call something like Grouping.find(1234).destroy the cascading call update the children position in the database rather then just destroying the parent data and moving along.
class Group
  include Mongoid::Document
  include Mongoid::Timestamps

  embeds_many :items, cascade_callbacks: true
end
class Item
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::Orderable

  orderable

  embedded_in :group
end

This is not a the worst that can happen however it does slow down the destroy_all method and destroy method. It was a bit of extra work to track down but  you can see it updating the position in the log file. One of the requirements is that you have to have more than one item embedded in the grouping but if you do it will result in the position field -1 for every nested item within the grouping excluding the first item that you destroyed.

Hey!

One of the requirements is that you have to have more than one item embedded in the grouping
Where is ite requirement from?

Also I'm not sure that I'll be able to solve this issue soon. If you will submit a PR with the fix - I'll merge it right away.

Yeah I am going to see about working on a fix for this. It has not been a super big problem because we we don't destroy data in most of the apps that use this gem. However when we do it does slow the system down by about 3x to nothing at all. It really fluctuates depending on the situation. I hope this helps someone else out that is looking into this bug.

Will be fixed in version 6.0.0

Will be fixed in version 6.0.0


Normalize "whitepapers and research" styles

Estimated time: 2h

Why:
It look hectic.
For example, the titles are in thos different formats:
LEVEL 2 TITLE
level 2 title:
IV. level 2 title
What:
Normalize the styles of this categories by copying the technical whitepaper style.

merged in #91


Homepage map markers absent when non-English language selected

When a non-English language is selected, the site markers do not appear on the home page map.

lat and long were being localized with commas, turning them into very large numbers.  As a bonus, I added translation to the popup box text.


Empty routeRoles in wsBeforeUpgrade if it is a websocket route

Actual behavior (the bug)
I have implemented a wsBeforeUpgrade handler. When the handler is executed and I try to access the routeRoles, I always get an empty list even though I have specified roles.
Expected behavior
When the handler is called, one should be able to access the routeRoles that have been defined instead of getting an empty list.
To Reproduce
        config.router.apiBuilder(() -> {
            ws("/ws/client", wsConfig -> {
                wsConfig.onConnect(this::onConnect);
                wsConfig.onMessage(this::onMessage);
                wsConfig.onError(this::onError);
                wsConfig.onClose(this::onClose);
            }, AUTHENTICATED); //<- routeRole is defined
        });

        ).wsBeforeUpgrade(context -> {
            var routeRoles = context.routeRoles();
            //routeRoles <- are empty
        })

Thanks @yaskor, I'll have a look in the weekend!

https://github.com/javalin/javalin/pull/2173

Should be fixed now!

Great! Thank you


[SPARK-47988][SQL] When the collationId is invalid, throw COLLATION_INVALID_ID

What changes were proposed in this pull request?
The pr aims to

convert ArrayIndexOutOfBoundsException to SparkArrayIndexOutOfBoundsException.
refactor CollationFactory to extract some of the same logic into a method, reduce redundancy.
when calling String#toUpperCase() with parameters Locale.ROOT, which conforms to the traditional rules of Spark, as follows:
https://github.com/apache/spark/blob/master/scalastyle-config.xml#L247-L258

Why are the changes needed?
Before:

After:

Does this PR introduce any user-facing change?
Yes, When the collationId is invalid, the user will get a more friendly error prompt.
How was this patch tested?

Add new UT.
Pass GA.

Was this patch authored or co-authored using generative AI tooling?
No.

i.e. we are working to remove the CollationTable concept entirely, as we expand collation support

I think this will soon no longer be relevant, since we are re-implementing how collationIds work in Spark: #46180

Okay, let me have a look.


Remembering port allocations for uninstalled pups

If a pup is uninstalled and even purged there is merit in remembering it's public port allocations (specifically admin ports) and not reusing them for other pups, this is because browser caches for content that previously existed on that port can leak private information, ie: local storage content, to the new pup.
Solution 1:
remember a port allocation counter++ and never reallocate, ever. That means pup X might be 10001, and later reinstalled to 10034, but no other pup would ever occupy 10001.
Pros: easy to implement, fully reinstalled pups get a 'clean slate' no state pollution from old install
Cons: port exhaustion eventually (like.. a long time but there is a limit)
Solution 2:
remember port allocation per pup source forever and reallocate to that pup again.
Pros: pups get their old browser state back if it exists
Cons:  need to keep things around that may never be used again

Cons: need to keep things around that may never be used again

Is it just a mapping from (source,pup-name) to port number? That seems fairly insignificant.
If it affects queries, we could filter them out with an indexed bool, or put port mappings in their own table, etc.
An alternative idea
Prefix the entire admin site with the pup-id.
Authors must use relative urls.
I'm not sure if this potentially breaks some things.
Caching problems
In any case, html pages should never be cached for more than a minute or so. This is something the web server must set in the response header. Using 10s-60s is for the benefit of the CDN, so it can actually cache it and do request-coalescing.
The browser will do an If-Modified check after that time, and usually won't download anything.
Other resource types, like scripts, css, especially images are often versioned so they can be cached for 30 days. Without versioning, whatever cache time you pick will still lead to re-using old cached files when you update the pup to a new version.
We could just inject Cache-Control: private; max-age:10 into every response and let the CDN and 304 checks do their thing.

The bigger issue is that pups may potentially save sensitive content in the users browser (local storage, cookies, whatever) that can then be read by any subsequent pup that gets hosted on that ephemeral port.


PowerRename does not work on NTFS reparse points

Environment
Windows build number: 10.0.18362.449
PowerToys version: 0.13.0
PowerToy module for which you are reporting the bug (if applicable): PowerRename

Steps to reproduce
Create reparse points, e.g. duplicate a folder with some files in OneDrive, right click the folder and choose "Free up space". OneDrive will change the local files to reparse points. Mark the files, right click them. The context menu does not show PowerRenamer (but it does show the standard "Rename" which works, albeit only for a single file, as usual).
Expected behavior
PowerRenamer should show up in the context menu and work on the reparse point(s).
Actual behavior
PowerRenamer does not show up (or work) with NTFS reparse points.
Screenshots

(Seems duplicated by #900)
Any updates?

agreed 900 is dup.  I don't know if we've done any work on this bug so far.

OneDrive placeholder files don't seem to show any context menu extensions aside from first party code.   This isn't specific to PowerRename.  I don't see a way around it.

I do not understand chrdavis comment (i am not a programmer). Since I can change filenames just fine from cmd, PowerShell or the files context menu, but not from PowerToys I wonder why.
Does closing this point mean it has been fixed in some future release?

I do not understand chrdavis comment (i am not a programmer). Since I can change filenames just fine from cmd, PowerShell or the files context menu, but not from PowerRename I wonder why.
Does closing this point mean it has been fixed in some future release?

The issue is fixed now in the code.  The next official release of the PowerToys will contain the fix so PowerRename will appear in the context menu for OneDrive placeholders.


Update agentManagement.sh

added support to enable/disable auto upgrade

@Djelibeybi Can you review this? There are previous shellcheck issues that will be fixed incrementally as this requires a lot of changes. This change is required to go in as it provides posture for the users to enable auto upgrades of their agent.


Category management clientside api

Task :
#20910 : As a developer I need to update UI for add a category
#20907 : As a developer I need to update UI for Edit a Catagory
implemented edit- dialog-component
File changed : question-dashboard-component.ts
categories.services.ts
question-dashboard.html
add-category-dialog.html
CategoryController
CategoryRepository
ICategoryRepository
File Created :
edit-category-dialog.html
category-model.ts

SonarQube analysis reported 22 issues

 19 major
 3 minor

Watch the comments in this conversation to review them.


Issue with sending NFTs

I tried to send an NFT and the app displayed the error.
Sending with the polkadot-js works just fine
NFT was issued on Kusama assets hub
Pallet uniques

Hi @mezrin,
As you can see on the screen, the cause of this problem is that the connection to RPC is unstable to check if the balance is enough to pay the transaction fee.
In this case, the user will re-enable the connection or change the RPC endpoint. This situation is often observed with RPC endpoints that are unstable or rate limits that are too low.
We do not have any effective solutions to completely solve this problem and we look forward to finding ways to handle them. Let me know your opinion about this problem, maybe we can find a good solution.

Ah, got it. Yes, it's not a wallet-related issue.
In my experience the only way to solve this kind of issues is to have a proper indexer (block explorer).
Indexer must provide access to the blockchain` current state (storage) via REST / GraphQL API - in addition to historical data like events / blocks / transactions.
In our company we are working on such an indexer for substrate-based chains. Maybe it will be available later this year.


MCXVChain with dirty ancilla is not optimal.

Environment

Qiskit Terra version: 0.23.2
Python version: 3.8.10
Operating system: Ubuntu 20.04.5 LTS

What is happening?
The number of cx operations in the MCXVChain gate with dirty_ancilla=True and k controls is higher than 8k -6 [Lemma 7, https://arxiv.org/pdf/1501.06911.pdf].
How can we reproduce the issue?
from qiskit import transpile
from qiskit.circuit.library.standard_gates import MCXVChain

k = 10
qc = MCXVChain(k, True).definition
tqc = transpile(qc, basis_gates=['u', 'cx'])
print(tqc.count_ops()['cx'])

prints 98 instead of 10*8-6=74.
What should happen?
MCXVChain with dirty_ancilla=True and k controls should use 8k-6 cx gates.
Any suggestions?
No response

closed by #9687


Sort Event Queue

As any user
I want sort any Event Queue
so that the columns will all sort ascending and descending

Assumptions & Scope
What are the assumptions for this story?
Sort for the Event Queue will work the same as for the Request Queue.
What is IN scope?
Sorting columns on the event queue
Changing the number of events listed on a page
What is NOT in scope?
#2267 covers the sort for the Request Queue and Advanced Sort
Acceptance Criteria
Scenario 1:

GIVEN any user is on any queue in the Event Queue
WHEN they click on the column the 1st time
THEN the column will sort ascending

Scenario 2:

GIVEN any user is on any queue in the Event Queue
WHEN they click the column a 2nd time
THEN the column will sort descending

Scenario 3: Option to change number of items in queue displayed
*GIVEN the user is the Event Queue
*WHEN the user clicks on the arrow next to 100 results (the default)
*THEN the user will have an option to select other result amounts as well (10, 25, 50 100)

DESIGN needed -

Scenario 4: Change number of items in queue displayed
*GIVEN the user has opened the options to select other result amounts as well (10, 25, 50 100)
*WHEN the user clicks on an option (e.g. 25)
*THEN the number of events listed per page will change (e.g. 25)

DESIGN needed -

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
@xxx - please link the Design here
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

Thoughts on a date picker, to further narrow down their results, rather than only having the option to sort date/time ASC or DESC? Trying to think of use cases for this, but it just came to mind.

Could see that working, but not sure if is needed?

All AC passed.

@divyav-aot Scenarios 3 and 4 do not pass
Scenario 3 states: "THEN the user will have an option to select other result amounts as well (50, 100, 200, 300)"
Scenario 4 states: GIVEN the user has opened the options to select other result amounts as well (50, 100, 200, 300)
*WHEN the user clicks on an option (e.g. 200)
*THEN the number of events listed per page will change (e.g. 200)
I cannot cannot complete these because drop-down menu amounts show 10, 25, 50 100.

Confirmed the event per page filter should be 10, 25, 50 100.
Updated ACs. @nimya-aot

Closing as complete.

Note - search in Event Queue searches across all pages, not just the current page. This functionality should persist in the future, and should be checked if updated made to event queue


Deno support

Would be great for this package to have Deno support.
At the moment the main blocker is this:
error: Uncaught ReferenceError: require is not defined
    at https://cdn.esm.sh/v41/node-gyp-build@4.2.3/deno/node-gyp-build.js:2:952

some dep seems to be using node-gyp and it prevents it from working on Deno

does it work on deno now? @mafintosh

Ah, I don't know, don't use Deno, just cleaned all stale issues from here.

Still not working on Deno as of writing. Here is the current error message:
error: Uncaught (in promise) ReferenceError: require is not defined
const safetyCatch = require('safety-catch')
                    ^
    at https://unpkg.com/corestore@6.18.2/index.js:1:21

I'd be happy contribute in any way I can! I'd love to see the Hypercore ecosystem running on Deno :two_hearts: