CheckBox and CheckButton ignores hover style when checked ON (pressed)

Godot version:
3.0.2 and master (3d5aabe7f)
OS/device including version:
All.
Issue description:
When a CheckBox or CheckButton is checked ON, no custom style is applied.
This was mentioned initially in #8640 by @hickop and @ProbDenis, and I can confirm it:

From my tests (see attached project below), the issue seems to be that the "pressed" style has precedence on the "hover" style, so when the box/button is ticked ON (pressed), only the pressed style is applied.
I'm not sure if this should be fixed by making the "hover" style have precedence on the "pressed" style (just like it has precedence on the "normal"/unpressed style), or if there should be another "pressed + hover" style. I guess the former might be fine, but were some using this as a feature?
Steps to reproduce:

Add a CheckBox or CheckButton, set custom_styles properties
Tick the CheckBox/CheckButton ON, see that hovering does not override the "pressed" style (or the "focus" style if you still have focus after pressing).

Minimal reproduction project:
checkbox_pressed_hover.zip

In a normal button pressed has precedence over hover because they are always mixed - if it's pressed then you sure are hovering/focusing it. Checkboxes have a little different logic - a checkbox CAN be pressed but not hovered at once. So, pressed+hover would probably be the most reasonable here, assuming it will be added to checkbox and checkbutton, not to button, IMO.


fix: shift selection works on click instead of holding

Platform
MacOS, Google Chrome.
Description
⇧ Shift key selects multiple nodes not by holding a key, but just by clicking.
https://user-images.githubusercontent.com/35642018/229346651-68d0f679-fc4d-4a34-9201-787655bc195e.mov

I looked into the code, and it looks like it could be react-flow problem.
Might be not a problem at all, but I think the all-known UX for ⇧ Shift is selection while the key is held pressed.
I will open a bug ticket in react-flow and back-link it to this issue to keep track of it.

yeaaaa this seems to be an annoying quirk with react-flow. lmk if u think this makes the shift selection key more annoying than helpful for you— we can disable it.

yeaaaa this seems to be an annoying quirk with react-flow. lmk if u think this makes the shift selection key more annoying than helpful for you— we can disable it.

Not at all, it's still a rich feature, I will keep track on it on reactflow side.
Hopefully we resolve it relatively fast.


Change default churn quotient

This change is required to reduce the staked ether needed in local testnets to test consolidations.

Decided against changing the default and deviating from mainnet values


Update<EMAIL_ADDRESS>

build<EMAIL_ADDRESS>

:beers: @BrewTestBot has triggered a merge.

:warning: @shivammathur bottle publish failed.

:beers: @BrewTestBot has triggered a merge.


--global should not be used with npm install @microsoft/generator-sharepoint

[Enter feedback here]
my debugging has found that if you install the  @microsoft/generator-sharepoint with an option of --global it does not work.  if you install it with --save --save-exact it seems to work just fine.
This will burn a lot of hours for our customers if not resolved.

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

ID: 5bee09a8-022e-1b5a-4aab-d6e7c6216808
Version Independent ID: 49edce1e-f2be-e989-917f-c6b389363e2f
Content: Set up your SharePoint Framework development environment
Content Source: docs/spfx/set-up-your-development-environment.md
Service: sharepoint
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

@ShadowPic - could you provide some details of your environment as npm i -g @microsoft/generator-sharepoint definitely works.


vivaldi: remove gstreamer

Works fine (at least for my normal behaviors using the web) running the latest snapshot.
Motivation for this change
Things done

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

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

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

Does this mean it's only using ffmpeg?

I'm not sure what you mean by "only using ffmpeg" but this is basically just to unbreak the derivation after gstreamer was marked as broken.
I'm not intimate with the inner workings of how gstreamer ties with the browser, but all my daily activities with the browser still work fine.

Ah, gstreamer being marked as broken fell off my radar.
@eadwu can you check if the test video at https://help.vivaldi.com/article/html5-proprietary-media-on-linux/ plays on that version?

can you check if the test video at https://help.vivaldi.com/article/html5-proprietary-media-on-linux/ plays on that version?

On my system with this PR merged it plays.


ci: cargo test --no-default-features as well

This is a followup PR for #7172 to prevent such errors from going by unnoticed in the future.

Closing this since just passing --no-default-features to cargo test does not work.
I now actually think that we probably shouldn't do this since the CI already takes long enough and rather just improve the API so that stuff that only works when a certain feature is enabled is actually only available when that feature is enabled ... i.e. turning runtime errors into compile time errors which would prevent errors like #7172 from going by unnoticed.
However I currently don't have time to work on this.


Deconz Add on shuts down by itself

The problem
Deconz add on was closed and never started. this happened 2 times in the last one month.
Environment
HassOS 4.12
Traceback/Error logs

Duplicate of: https://github.com/home-assistant/hassio-addons/issues/1546


fix: Add valid property AWS_SNS_TOPIC_ARN to AWS_SNS notification provider

Notification integration fixes for #777

Fix AWS_SNS_TOPIC_ARN a valid argument for notification integration provider
Documentation, example and import

Test Plan
CGO_ENABLED=1 go test -race -coverprofile=coverage.txt -covermode=atomic  ./...
?       github.com/chanzuckerberg/terraform-provider-snowflake  [no test files]
ok      github.com/chanzuckerberg/terraform-provider-snowflake/pkg/datasources  0.802s  coverage: 4.2% of statements
?       github.com/chanzuckerberg/terraform-provider-snowflake/pkg/db   [no test files]
ok      github.com/chanzuckerberg/terraform-provider-snowflake/pkg/provider     0.602s  coverage: 28.9% of statements
ok      github.com/chanzuckerberg/terraform-provider-snowflake/pkg/resources    11.868s coverage: 55.0% of statements
ok      github.com/chanzuckerberg/terraform-provider-snowflake/pkg/snowflake    0.454s  coverage: 59.7% of statements
?       github.com/chanzuckerberg/terraform-provider-snowflake/pkg/testhelpers  [no test files]
ok      github.com/chanzuckerberg/terraform-provider-snowflake/pkg/validation   0.249s  coverage: 93.1% of statements
?       github.com/chanzuckerberg/terraform-provider-snowflake/pkg/version      [no test files]

[ ] acceptance tests
Error notifications feature is currently in private preview link reference here and Snowflake staff need to enable it for that particular account before setting error_integration parameter would work.

References
https://docs.snowflake.com/en/LIMITEDACCESS/data-load-snowpipe-notifications.html#step-6-enabling-error-notifications-in-pipes

@alldoami  could you please review and approve for Github Actions

Hmm I might be missing something but I only see name changes in this PR...

HI @alldoami,

Yes I raised a PR for name change of the variable provided. I got the below error while creating the notification integration with terraform plan.

SQL compilation error: invalid property 'AWS_SNS_ARN' for 'INTEGRATION'

I debugged a little more and found the issue was with SQL query here
This query expects AWS_SNS_TOPIC_ARN instead of AWS_SNS_ARN

/ok-to-test sha=3dda35a

Could i request release for new version please.


Extend basic auth to info and results endpoints

Description
Adds a protect_all_endpoints boolean flag to the http_socket settings as described in #1724, allowing for the other resource endpoints (info and results) to be protected by basic authorization along with settings.
Includes a one-liner fix for the response sent when a method is not allowed. Let me know if it's preferable to put this in a separate PR.
Related Issue
#1724
Motivation and Context
Extends the existing basic auth protection in a backwards-compatible manner to the other endpoints. It's useful with the /results endpoint in particular, in environments where selective processes should have the ability to relay check results.
How Has This Been Tested?
Manually tested making requests without the option set, and with the boolean set to both true and false. Could use some pointers on writing the test spec - I didn't see an obvious way of overwriting the client settings from within the spec.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@stuwil this looks great! We do however need some tests, any chance you can find some time to write two quick tests up for authentication on the newly protected endpoints? Should be able to copy https://github.com/sensu/sensu/blob/7c49fee736fa4866043e7a37d77c09f7149fc9f0/spec/client/http_socket_spec.rb#L53-L83 and make a few modifications.

Going to go ahead an merge this into release/1.1, as I am going to follow up with a spec and a sensu-settings bump (adding validation) 👍
@stuwil thank you!!!


vocms0116.cern.ch Job updater couch Job submitter

Restarted the agent this morning with this error:
ModuleName : WMComponent.JobUpdater.JobUpdaterPoller
MethodName : algorithm
ClassInstance : None
FileName : /data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobUpdater/JobUpdaterPoller.py
ClassName : None
LineNumber : 100
ErrorNr : 0
Traceback:
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobUpdater/JobUpdaterPoller.py", line 82, in algorithm
self.synchronizeJobPriority()
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobUpdater/JobUpdaterPoller.py", line 114, in synchronizeJobPriority
workflowsToCheck = [x for x in self.workqueue.getAvailableWorkflows()]
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/WorkQueue/WorkQueue.py", line 117, in getAvailableWorkflows
{'reduce' : False, 'stale': 'update_after'})
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 488, in loadView
(self.name, design, view), encodedOptions)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 104, in get
encode, decode, contentType)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 120, in makeRequest
encode, decode, contentType)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 140, in makeRequest
encoder, decoder, contentType)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 251, in makeRequest_httplib
body=encoded_data, headers=headers)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/init.py", line 1436, in request
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/init.py", line 1188, in _request
(response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/init.py", line 1123, in _conn_request
conn.connect()
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-packages/httplib2/init.py", line 796, in connect
raise socket.error, msg
Backtrace:
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/WorkerThreads/BaseWorkerThread.py", line 206, in call
raise ex
2016-11-16 14:50:28,198:140646270207744:INFO:BaseWorkerThread:Worker thread <WMComponent.JobUpdater.JobUpdaterPoller.JobUpdaterPoller instance at 0x7feacb95b440> terminated
I could not tell if it was a scheduling conflict or not.
Than couch and Job updater went down.   Printing out command stderr
2016-11-16 23:07:46,782:140378817492736:ERROR:PyCondorPlugin:Non-zero exit code: 1
stderr:
ERROR: No such directory: /data/srv/wmagent/v1.0.21.patch2/install/wmagent/JobCreator/JobCache/prozober_ACDC0_BTV-RunIISummer16DR80Premix-00016_00008_v0__161115_124339_9404/StepOneProc/JobCollection_119767_17/job_1450478
2016-11-16 23:07:46,782:140378817492736:ERROR:PyCondorPlugin:Processing failed jobs and proceeding to the next jobs.
2016-11-16 23:07:46,782:140378817492736:ERROR:PyCondorPlugin:Do not restart component.
2016-11-16 23:07:46,806:140378817492736:ERROR:PyCondorPlugin:Exceeded errorThreshold while submitting to condor. Check condor status.
2016-11-16 23:07:46,991:140378817492736:ERROR:BaseWorkerThread:Error in worker algorithm (1):
Backtrace:
<WMComponent.JobSubmitter.JobSubmitterPoller.JobSubmitterPoller instance at 0x7fac863499e0> BossAirPluginException
Message: Exceeded errorThreshold while submitting to condor. Check condor status.
ModuleName : WMCore.BossAir.Plugins.PyCondorPlugin
MethodName : submit
ClassInstance : None
FileName : /data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/BossAir/Plugins/PyCondorPlugin.py
ClassName : None
LineNumber : 521
ErrorNr : 0
Traceback:
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/WorkerThreads/BaseWorkerThread.py", line 180, in call
self.algorithm(parameters)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobSubmitter/JobSubmitterPoller.py", line 673, in algorithm
self.submitJobs(jobsToSubmit=jobsToSubmit)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMComponent/JobSubmitter/JobSubmitterPoller.py", line 623, in submitJobs
successList, failList = self.bossAir.submit(jobs=jobList)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/BossAir/BossAirAPI.py", line 420, in submit
info=info)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/BossAir/Plugins/PyCondorPlugin.py", line 521, in submit
raise BossAirPluginException(msg)
2016-11-16 23:07:46,991:140378817492736:INFO:Harness:>>>Terminating worker threads
2016-11-16 23:07:47,056:140378817492736:ERROR:BaseWorkerThread:Error in event loop (2): <WMComponent.JobSubmitter.JobSubmitterPoller.JobSubmitterPoller instance at 0x7fac863499e0> BossAirPluginException
Message: Exceeded errorThreshold while submitting to condor. Check condor status.
ModuleName : WMCore.BossAir.Plugins.PyCondorPlugin
MethodName : submit
ClassInstance : None
FileName : /data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/BossAir/Plugins/PyCondorPlugin.py
ClassName : None
LineNumber : 521
ErrorNr : 0
Traceback:
Backtrace:
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-packages/WMCore/WorkerThreads/BaseWorkerThread.py", line 206, in call
raise ex
2016-11-16 23:07:47,060:140378817492736:INFO:BaseWorkerThread:Worker thread <WMComponent.JobSubmitter.JobSubmitterPoller.JobSubmitterPoller instance at 0x7fac863499e0> terminated
Even the error says do not restart component so I am not. I will write another elog about Job submitter.

For JobUpdate error, couch server was down. Restarted the couch. And it seems working OK now.
JobSubmitter is crashing due to there is many consecutive submit failures which is higher then threshold. (10)
It is just protective measure when too many consecutive submit failure happens then crash the component and investigate
The reason it has consecutive failure is that it is trying to submit the jobs from
prozober_ACDC0_BTV-RunIISummer16DR80Premix-00016_00008_v0__161115_124339_9404
and it couldn't fine the job sandbox.
The workflow is aborted so the sandbox was clean up. It could be a race condition when job is in submit cache and directory is deleted but I have to look at the code closely whether that is the case.
I restarted the JobSubmitter and so far it seems running OK

@scarletnorberg, Hi Scarlet, I am still leave this open if the components crashed again tomorrow, please update here.

About couch down, it's likely related to the peak of cooloff jobs around that time (I elogged about it, ~35k jobs) and a sudden removal of ~40k created jobs as well.

Nov 19th this agent when down again couch went down and JobUpdater:
/workqueue/_design/WorkQueue/_list/filter/elementsBySubscription?
filter=%7B%22SubscriptionId%22%3A+12408%7D&idOnly=false&reduce=false&include_docs=true 200
[Fri, 18 Nov 2016 22:49:29 GMT] [info] [<0.3874.45>] <IP_ADDRESS> - - POST /workqueue/_bulk_docs/ 201
[Fri, 18 Nov 2016 22:49:29 GMT] [info] [<0.5693.34>] Starting index update for db: workqueue idx: _design/WorkQueue
[Fri, 18 Nov 2016 22:49:29 GMT] [info] [<0.5693.34>] Index update finished for db: workqueue idx: _design/WorkQueue
[Fri, 18 Nov 2016 22:49:29 GMT] [info] [<0.3880.45>] <IP_ADDRESS> - - POST
/workqueue/_design/WorkQueue/_list/filter/elementsBySubscription?
filter=%7B%22SubscriptionId%22%3A+12410%7D&idOnly=false&reduce=false&include_docs=true 200
[Fri, 18 Nov 2016 22:49:30 GMT] [info] [<0.3881.45>] <IP_ADDRESS> - - POST /workqueue/_bulk_docs/ 201
[Fri, 18 Nov 2016 22:49:30 GMT] [info] [<0.5693.34>] Starting index update for db: workqueue idx: _design/WorkQueue
[Fri, 18 Nov 2016 22:49:30 GMT] [info] [<0.5693.34>] Index update finished for db: workqueue idx: _design/WorkQueue
[Fri, 18 Nov 2016 22:49:30 GMT] [info] [<0.3888.45>] <IP_ADDRESS> - - POST
/workqueue/_design/WorkQueue/_list/filter/elementsBySubscription?
filter=%7B%22SubscriptionId%22%3A+12412%7D&idOnly=false&reduce=false&include_docs=true 200
[Fri, 18 Nov 2016 22:49:30 GMT] [info] [<0.3889.45>] <IP_ADDRESS> - - POST /workqueue/_bulk_docs/ 201
That is couch.
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-
packages/WMCore/Database/CMSCouch.py", line 120, in makeRequest
encode, decode, contentType)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-
packages/WMCore/Services/Requests.py", line 140, in makeRequest
encoder, decoder, contentType)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-
packages/WMCore/Services/Requests.py", line 251, in makeRequest_httplib
body=encoded_data, headers=headers)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-
packages/httplib2/init.py", line 1436, in request
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-
packages/httplib2/init.py", line 1188, in _request
(response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-
packages/httplib2/init.py", line 1123, in _conn_request
conn.connect()
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/py2-httplib2/0.7.1-comp3/lib/python2.7/site-
packages/httplib2/init.py", line 796, in connect
raise socket.error, msg
Backtrace:
File "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/cms/wmagent/1.0.21.patch2/lib/python2.7/site-
packages/WMCore/WorkerThreads/BaseWorkerThread.py", line 206, in call
raise ex
2016-11-18 23:50:33,008:140340868212480:INFO:BaseWorkerThread:Worker thread
<WMComponent.JobUpdater.JobUpdaterPoller.JobUpdaterPoller instance at 0x7fa3b03198c0> terminated
Above is JobUpdater.
I will check later tonight and see if there is a problem this maybe just because of the peak of cooloff jobs and me restarting when there was an issue with that so hopefully it will be stable now.

couch times out and then erlang kills the process. This is one of the couch issues that I really don't know how to solve. I'm setting this agent to Drain and we'll bring another agent into the pool tomorrow morning.

BTW, tail of couch stderr.log
heart_beat_kill_pid = 2633700
heart_beat_timeout = 60
heart: Sun Nov 20 07:18:09 2016: heart-beat time-out.
heart: Sun Nov 20 07:18:10 2016: Executed "/data/srv/wmagent/v1.0.21.patch2/sw/slc6_amd64_gcc493/external/couchdb15/1.6.1-comp4/bin/couchdb -k". Terminating.

and couch.log
[Sun, 20 Nov 2016 06:17:05 GMT] [info] [<0.18777.39>] <IP_ADDRESS> - - POST /workqueue/_bulk_docs/ 201
[Sun, 20 Nov 2016 06:17:05 GMT] [info] [<0.721.0>] Starting index update for db: workqueue idx: _design/WorkQueue
[Sun, 20 Nov 2016 06:17:05 GMT] [info] [<0.721.0>] Index update finished for db: workqueue idx: _design/WorkQueue
[Sun, 20 Nov 2016 06:17:05 GMT] [info] [<0.18703.39>] <IP_ADDRESS> - - POST /workqueue/_design/WorkQueue/_list/filter/elementsBySubscription?filter=%7B%22SubscriptionId%22%3A+11020%7D&idOnly=false&reduce=false&include_docs=true 200
[Sun, 20 Nov 2016 06:17:05 GMT] [info] [<0.18704.39>] <IP_ADDRESS> - - POST /workqueue/_bulk_docs/ 201
[Sun, 20 Nov 2016 06:17:05 GMT] [info] [<0.721.0>] Starting index update for db: workqueue idx: _design/WorkQueue

Instead of giving up on this node, I decided to google (once again) for this issue and I found this thread:
https://issues.apache.org/jira/browse/COUCHDB-1917
with a proposal to mitigate these issues, which AFAIU it's only about the error reporting, since the timeout can still happen.
These are the changes I applied to vocms0116:
cmst1@vocms0116:/data/srv/wmagent/current $ diff -rup sw/slc6_amd64_gcc493/external/couchdb15/1.6.1-comp4/bin/couchdb{.ori,} | colordiff
--- sw/slc6_amd64_gcc493/external/couchdb15/1.6.1-comp4/bin/couchdb.ori	2016-11-21 10:28:13.463171124 +0100
+++ sw/slc6_amd64_gcc493/external/couchdb15/1.6.1-comp4/bin/couchdb	2016-11-21 10:30:48.446963741 +0100
@@ -271,8 +271,10 @@ start_couchdb () {
     else
         if test "$RECURSED" = "true"; then
             # close stdout / stderr
-            exec 1>&-
-            exec 2>&-
+            exec 1>/data/srv/wmagent/v1.0.21.patch2/install/couchdb/logs/stdout.log
+            exec 2>/data/srv/wmagent/v1.0.21.patch2/install/couchdb/logs/stderr.log
+            # exec 1>&-
+            # exec 2>&-
             while true; do
                 export HEART_COMMAND
                 export HEART_BEAT_TIMEOUT

IF it remains Ok, I may take it out of Drain and we watch it for some days.

Patch is created in https://github.com/cms-sw/cmsdist/pull/2786

New agents are being deployed with the couch patch. Thus I'm closing this issue.


ERR_REQUIRE_ESM with Wagmi

Hi all, getting the following error when importing
import { SafeConnector } from<EMAIL_ADDRESS>- I am running v1.2.0
Error: require() of ES Module<EMAIL_ADDRESS>from<EMAIL_ADDRESS>not supported.
Instead change the require of<EMAIL_ADDRESS>in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
Any ideas on how to resolve? thanks in advance

related to #395

I have created a pr which resolves this issue: https://github.com/safe-global/safe-apps-sdk/pull/441 feel free to try the solution out locally I would be happy to guide you through.

Use this now import { SafeConnector } from "@wagmi/connectors/safe"; : https://wagmi.sh/react/connectors/safe

Closing this issue as now the Wagmi connector is available at Wagmi repository.
Find the docs on the comment above


[11.x] Fix(Router.php): using null-safe operator

First Change (fix bug) : Implementing Null-Safe Operator to Handle Potential Null Return in current() Method
If $this->current() returns null, an error of type Error: Call to a member function parameter() on null occurs, which could also happen within the current() method if it returns null.
Therefore, it's better to use the null-safe operator to return null if $this->current() evaluates to null, instead of encountering an error.

    /**
     * Get a route parameter for the current route.
     *
     * @param  string  $key
     * @param  string|null  $default
     * @return mixed
     */
    public function input($key, $default = null)
    {
        return $this->current()?->parameter($key, $default);
    }

Second Change (refactor)

    // before
    public function currentRouteName()
    {
        return $this->current() ? $this->current()->getName() : null;
    }

   // after
    public function currentRouteName()
    {
        return $this->current()?->getName();
    }

https://github.com/laravel/framework/pull/50590

The tests failed, but they are not related to the two changes in these commits.
https://github.com/laravel/framework/pull/50590
@driesvints

How to recreate the actual bug in a real app?


[WFLY-13901] Upgrade Jastow to 2.0.9.Final

https://issues.redhat.com/browse/WFLY-13901
Brings in:

[UNDERTOW-1768] Enhancements to simplify javax -> jakarta byte code transformations.

Please review @bstansberry

Thanks, @ropalka


positive definiteness of composite kernels

Are you sure that a kernel sum of one positive definite and one NOT positive definite kernel is still positive definite ? That's what the code says: isposdef(ψ::KernelSum) = isposdef(ψ.k1) | isposdef(ψ.k2), but I really wouldn't've thought so..

Hahaha, there was an assumption buried there. I was only going to implement positive (semi) definite kernels. In that case, I believe that one of them being positive definite would be sufficient for the composite to be positive definite (correct me if I'm wrong - I could very well be... I didn't study much in the way of analysis).
Many of the kernels I have right now were just an initial set and I hadn't read up on them as of yet. I feel like at least one of them is not not necessarily PSD. Did you want non PSD kernels supported? Are they used anywhere?

No, any kernel I want should at least be semi-posdef. I'm not particularly deep into properties of kernels, but based on what I just read up on positive definiteness of matrices I think isposdef(KernelSum) should use & instead of |. Will add that to the next pull request.
(On a side note, for what do you use your Kernel package?)

So I was reading a bit more into the definitions. What I've referred to as "positive definiteness" is "strict positive definiteness" for kernels (the analogue for matrices is "positive semidefinite" and "positive definite" respectively").
A strict positive definite kernel will return a positive definite gramian matrix.
A positive definite kernel will return a positive semidefinite gramian matrix.
A matrix S is positive definite if x'Sx > 0 for all x != 0 and semidefinite if it is a '>=' inequality.
The kernel sum corresponds to a sum of two gramians and the kernel product corresponds to the hadamard product of two gramians.
Shur product theorem shows us that we are correct for the kernel product (using '&').
However, if A is positive semidefinite and B is positive definite, then:
x'Ax >= 0
x'Bx > 0
==>
0 < x'Ax + x'Bx = x'(A + B)x
So I think it should be '|' if we're restricting our set of kernels to positive definite ones. Do you concur?
I was going to go through and learn all the major ML and statistical techniques. I started with data preprocessing algorithms. I was working on kernel fisher discriminant analysis and KPCA... but shifted focus to making a kernel matrix package because I felt there was a need for it. This is all just educational for me..

Conditionally positive definite kernels are included in the package, so I agree with your change.


Text styles in no results page are incorrect #1588

Fixes

Fixes #1588 by @panchovm
Description
On component VNoResults.vue

changed h5 to h4 below
deleted text-3xL -  on

Testing Instructions
In live build

search "fjkdls;a;"
when you arrive at 'no results' page

inspect page, view on 'mobile view' to see text size changes

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@obulat We went ahead and implemented your changes. Thank you for your detailed reply. We want our code to be as accurate as possible. Still learning!

@obulat We went ahead and implemented your change! Thanks for your help.

@panchovm Hey! I went ahead and made the changes that @krysal suggested. We found the incorrect text in the en.JSON file. I can go ahead and make that change for you on this ticket. I also don't mind opening another Issue/ PR for it if the team deems it so.
CC: @obulat

@kickeyhickey a standalone PR for that would be excellent; thank you!

I pushed a small fix to the tailwind class order so that linting would pass. Nice work!


fix(parser): Remove no parse from 5425/5426

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

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


[IE] add Op Pow and its node.js binding

The implementation based on IE for Op pow and its Node.js binding. The screenshots for Node.js tests is here:

@lionkunonly , please help fix the conflicts. Thanks.

Ping @lionkunonly to fix the conflicts. Thanks.

Ping @lionkunonly to fix the conflicts. Thanks.

The conflicts are fixed.


Update etcd

 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.

Oops, opened in error. This PR is not ready yet. Closing :)


finite difference on n_g

This is from one of our example notebooks:

Note: group_index function implementation is based on finite difference method. Therefore, the result is not exact. However, the result is accurate enough for most of the cases. If you need exact result, please use grad_neff function to calculate the derivative of neff function.

I think we no longer have a grad_neff function right? We should fix that first.
Even then, why wouldn't we directly use grad(neff()) anyways, since it's more reliable than using a finite difference approach?

grad_neff function is implemented under effective_index.neff. If we decide to keep it, I will update group_index function accordingly.
https://github.com/Photonic-Architecture-Laboratories/si-photonics-toolkit/blob/c7c9898b8feae02acd7b2ba3a7c18a9d1a3faf7a/sipkit/effective_index.py#L172-L191


Dbless config map auto-reload

Is there any way to soft reload kong when config map is updated ? kong.yml declarative config file is kept in configMap. I am using helm charts for the deployment.
Do i have to update deployment.yaml and add some annotation for sha256 OR it is there any other way ?  For annotation, is there any document to help with that ?

I am using reloader to recreate kong pods when kong config, stored in configmap, changes.
https://github.com/stakater/Reloader

Hi @yasharya1984 👋
As mentioned by @mirkoszy: you can use an off the shelf tool like Reloader for this if you're storing the config in a ConfigMap.
I'm not even sure if there is a mechanism to access a ConfigMap or a Secret from helm to check its annotations/contents during upgrade/install 🤔.
Feel free to reach us if you feel this can be resolved differently. I'm closing this for now.


Merge beta to main using fast forward

I think that this way release notes and changelog will be right. Right? Not sure haha
Because then all commits from beta will be included in main. Then you can recreate beta from main head.

Hahaha I'll try this next release, thanks for the tip @AllanOricil !

@mcarvin8 Github uses by default --no-ff. Because we want all commits to be added again to main we have to use ff. You could use rebase and merge next time, I think. Sorry for the confusion haha

Actually I don't know, really. Semantic-release's doc says to do a --no-ff  :(

I asked semantic-release devs how to do it
https://github.com/semantic-release/semantic-release/discussions/3170

nooooo, sorry. Release notes are right. I don't know why I saw they were wrong. My bad. Merge with --no-ff works.

Thanks @AllanOricil , yea I think I have the jest now of formatting the commit messages to trigger a release, so I'll make sure to get in that habit when pushing new stuff.


done first assignment

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
done assignment
What did you learn from the changes you have made?
python
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
few
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
didn't face
How were these changes tested?
jupiter
A reference to a related issue in your repository (if applicable)
no
Checklist

[ x] I can confirm that my changes are working as intended

you did a great job here!
Please go ahead and close this pull request now. Thanks!


[Draft] Ruby vulnerability roundup 001

Vulnerable packages (more details)

[ ] mikutter
[ ] ppl-address-book
[ ] ledger-web
[ ] redmine
[ ] redmine_4
[ ] ptask
[ ] pt
[ ] taskjuggler
[ ] frab
[ ] riemann-dash
[ ] sensu
[ ] ejson
[ ] chefdk
[ ] rhc
[ ] sass
[ ] sassc
[ ] compass
[ ] redis-dump
[ ] lolcat
[ ] mpdcron
[ ] fpm
[ ] bcat
[ ] metasploit
[ ] r10k
[ ] applications/version-management/gitlab/rubyEnv-ee
[ ] applications/version-management/gitlab/rubyEnv-ce
[ ] applications/misc/taskjuggler/3.x

Log output
https://gist.githubusercontent.com/primeos/9eb81de24a1d09230566f74fd476b787/raw/bf84f134e9c1bde9e7ad6b10f01d20af9c6e5f8e/log.txt
Can be searched by the path to the Gemfile.lock in nixpkgs, e.g.:
Gemfile: ./pkgs/applications/networking/instant-messengers/mikutter/Gemfile.lock

TODO
This is only a draft by running something as simple as the following script inside a nixpkgs checkout:
#!/usr/bin/env nix-shell
#!nix-shell -i bash -p bundler-audit

set -o errexit
set -o nounset

bundler-audit update

GEMFILES="$(find -name Gemfile.lock)"

#rm -f /tmp/gemfile-paths.txt

for GEMFILE in $GEMFILES; do
  pushd "$(dirname $GEMFILE)" > /dev/null
  echo "Gemfile: $GEMFILE"
  bundler-audit check || echo "$PWD" >> /tmp/gemfile-paths.txt
  popd > /dev/null
done

It might be a good idea to automate this and cc the maintainers (after some testing and maybe with a better output) but I do not have much time for this at the moment. Maybe someone else is interested and has time?
Feedback is welcome.

The redmine packages were patched against this. A big :+1: for automatically alerting package maintainers if anyone is able to find the time to finish what @primeos has started.
@manveru Didn't I notice a bunch of ruby related PRs from you recently? Off the top of your head do you know if any of these vulnerabilities have been patched?

I haven't checked for vulnerabilities, only reran bundle lock to fetch the latest valid dependencies. So it might've fixed some of those, but I'll have to check manually. I can probably give it some time tonight.

Will track my progress here:

[ ] mikutter: https://github.com/NixOS/nixpkgs/pull/60808
[ ] ppl-address-book: https://github.com/NixOS/nixpkgs/pull/60795
[ ] ledger-web: https://github.com/NixOS/nixpkgs/pull/60509
[ ] redmine
[ ] redmine_4
[ ] ptask: this is not a Ruby app or in the security logs
[ ] pt: https://github.com/NixOS/nixpkgs/pull/60503
[ ] taskjuggler
[ ] frab
[ ] riemann-dash
[ ] sensu: https://github.com/NixOS/nixpkgs/pull/60514
[ ] ejson
[ ] chefdk
[ ] rhc
[ ] sass
[ ] sassc
[ ] compass: https://github.com/NixOS/nixpkgs/pull/60505
[ ] redis-dump
[ ] lolcat
[ ] mpdcron
[ ] fpm: https://github.com/NixOS/nixpkgs/pull/60809
[ ] bcat
[ ] metasploit
[ ] r10k
[ ] applications/version-management/gitlab/rubyEnv-ee
[ ] applications/version-management/gitlab/rubyEnv-ce
[ ] applications/misc/taskjuggler/3.x


Cors Error

Hello i'm receiving a cors error when attempting to connect using the Nuxt-Directus module yet in the examples there is no cors option, what am I missing?
This is my nuxt.config section with directus:
directus: {
    url: process.env.DIRECTUS_URL,
    auth: {
      email: process.env.DIRECTUS_EMAIL,
      password: process.env.DIRECTUS_PASSWORD,
      token: process.env.DIRECTUS_TOKEN,
    }
  },

If you're using the example setup from this repo this has now been addressed in #190. See also the documentation: https://docs.directus.io/self-hosted/config-options.html#cors


Missing new line between JSON access log entries

Missing new line between JSON access log entries
Description:

PR https://github.com/envoyproxy/envoy/pull/4693  introduced JSON access logging.  When implemented, there is no new line separating entries in the access log.  The logs appear to be one right after the other with no separating new lines.

Config:
Sample Listener config:
     "version_info": "2018-11-12T18:15:14Z/19",
     "listener": {
      "name": "<IP_ADDRESS>_15020",
      "address": {
       "socket_address": {
        "address": "<IP_ADDRESS>",
        "port_value": 15020
       }
      },
      "filter_chains": [
       {
        "filters": [
         {
          "name": "envoy.tcp_proxy",
          "config": {
           "access_log": [
            {
             "name": "envoy.file_access_log",
             "config": {
              "json_format": {
               "downstream_remote_address": "%DOWNSTREAM_REMOTE_ADDRESS%",
               "path": "%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%",
               "authority": "%REQ(:AUTHORITY)%",
               "protocol": "%PROTOCOL%",
               "upstream_service_time": "%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%",
               "upstream_local_address": "%UPSTREAM_LOCAL_ADDRESS%",
               "duration": "%DURATION%",
               "downstream_local_address": "%DOWNSTREAM_LOCAL_ADDRESS%",
               "user_agent": "%REQ(USER-AGENT)%",
               "response_code": "%RESPONSE_CODE%",
               "response_flags": "%RESPONSE_FLAGS%",
               "start_time": "%START_TIME%",
               "method": "%START_TIME%",
               "request_id": "%REQ(X-REQUEST-ID)%",
               "upstream_host": "%UPSTREAM_HOST%",
               "x_forwarded_for": "%REQ(X-FORWARDED-FOR)%",
               "requested_server_name": "%REQUESTED_SERVER_NAME%",
               "bytes_received": "%BYTES_RECEIVED%",
               "bytes_sent": "%BYTES_SENT%",
               "upstream_cluster": "%UPSTREAM_CLUSTER%"
              },
              "path": "/dev/stdout"
             }
            }
           ],
           "stat_prefix": "inbound|15020||mgmtCluster",
           "cluster": "inbound|15020||mgmtCluster"
          }
         }
        ]
       }
      ],
      "deprecated_v1": {
       "bind_to_port": false
      }
     },
     "last_updated": "2018-11-12T18:15:24.023Z"
    },

cc @aa-stripe

This is indeed the case, can't believe I missed this, me--. Working on a patch now!


emoji: Switch to zulip_emoji_map.py for generating emoji info.

Should be merged after PR #7026 gets merged.

@timabbott @rishig This is finally ready for review. This contains only one script, other two are WIP for which I will create a separate PR.

(As a sidenote, this should be merged after #7026 goes in.)

@rishig Updated! :)

@rishig Thanks for the careful review. I have also pushed a version of script used to parse excel sheet, can you check out that? Thanks! :)

For generate_zulip_emoji_map, I think it should take a csv or tsv (tab separated value), rather than an excel file. That will be easier to interact with, debug, etc, and we aren't using any of the fancy features of excel (like formulas).
For testing this, I think the only test that needs to be done will be:
A = spreadsheet
B = names_dict(A)
C = spreadsheet(B)
D = names_dict(C)
and then check that A == C and B == D.

@rishig Updated emoji names import tool to interact with a tsv file. Working on the emoji name tool which I think would be tricky to do, I am assuming we would need explanations in the exported tsv file?

After talking with Tim, I think we do want csv instead of tsv, since tabs are hard to interact with (e.g. in git diff). I realize it's a bit harder to do the parsing, but hopefully something like https://docs.python.org/2/library/csv.html will handle it?
We do need the explanations in the exported file, but I don't understand

Working on the emoji name tool which I think would be tricky to do

What do you mean by the emoji name tool, and which part is tricky?

After talking with Tim, I think we do want csv instead of tsv, since tabs are hard to interact with (e.g. in git diff).

I choose tsv because we are using commas in explanation and I suspected we would have to face double quotation on round trip but csv seems to have a good support for these scenarios. I have changed the tools to use csv format.

What do you mean by the emoji name tool, and which part is tricky?

Sorry that was a typo, I was referring to zulip_emoji_map.py exporting tool. The good thing is that it is ready.
I have pushed new changes which include:
1: New emoji names export tool.
2: Changed the scripts to use csv format.
3: Modified the emoji names import tool to add # ignorelongline comment automatically for line longer than 120.
4: A minor fix in custom_check.py.
:tada: :relaxed:

Modified the emoji names import tool to add # ignorelongline comment automatically for line longer than 120.

The main benefit of storing in this format instead of just storing the csv is so that we don't have to check in the long lines into the codebase :). The issue with long lines is it can make the output of git grep messy.

Seems like zulipbot is going a little crazy here..

I merged a couple preparatory commits; it looks like there's still some feedback from @rishig that needs to be addressed.

@timabbott Ready for a final review!

@timabbott I went over this PR again and I think this is ready for a review from you. Once this gets merged I will be more confident in upgrading the emoji-datasource package. :)

@timabbott Now that 1.8 is out, what's your plan regarding this?

I think we should integrate the upgrade to the emoji-data library that fixes the misplaced emoji, and then rebase this on top of that?  I'm a little scared of this change, so I'd rather tackle this in a couple weeks, whereas that other change seems relatively safe.

I have rebased this and added a tool to validate the scripts by doing a round-trip conversion. But it is giving false errors because of presence of stray spaces at the end of explanation lines. We will need to run the excel sheet through some tool/script to remove those spaces. Otherwise this is ready for a review.
@rishig FYI> :)

@timabbott This is ready from my and @rishig 's side, so ready for a final sign-off from you. :tada:

Merged as the series of commits ending with 811ac718d631a993b02c773b9f2550099f01428b, thanks @HarshitOnGitHub!

BTW this was a huge project, so congratulations on getting it finished!


Can't create an index with a single field

definition = redisearch.IndexDefinition(
    prefix=['user:'], index_type=redisearch.client.IndexType.JSON)

SCHEMA = (
    redisearch.TextField("$.phone", as_name="phone")
)
rc = redisearch.Client("idx:user")

try:
    rc.info()
except redis.ResponseError:
    # Index does not exist. We need to create it!
    rc.create_index(SCHEMA, definition=definition)

Give this error

TypeError: 'TextField' object is not iterable

@clmno
Try to use with comma
SCHEMA = (
        TextField("$.phone", as_name="phone"),
)

Thank you


Create DisjointSetUnion.cpp

Added a simple implementation of DSU

Hey codeaholic-shub, I am Rahul Verma, a third year B. Tech. student from DTU. I am a competitive programmer (2000+ on Codeforces and 2200+ on CodeChef), you can check about me more on LinkedIn (ID: vrintle)
Kindly review my pr, I have just started open-source contribution.


"Gornet", "Lunca", "Mănăstirea" and "Mărunțișu" are listed in the drop-down menu

Description:
"Gornet", "Lunca", "Mănăstirea" and "Mărunțișu" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Gornet" in the search bar.

Expected results
The location is listed in the drop-down menu as "Gornet, Buzău(Pătârlagele)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Lunca" in the search bar.

Expected results
The location is listed in the drop-down menu as "Lunca, Buzău(Pătârlagele)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Mărunțișu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Mărunțișu, Buzău(Pătârlagele)".


Update Links

See https://github.com/Senzing/template-repository/issues/40
keystore-generator/README.md:    1. [docker](https://github.com/Senzing/knowledge-base/blob/main/HOWTO/install-docker.md)
keystore-generator/README.md:    1. [git](https://github.com/Senzing/knowledge-base/blob/main/HOWTO/install-git.md)
keystore-generator/README.md:    1. [make](https://github.com/Senzing/knowledge-base/blob/main/HOWTO/install-make.md)

Pull requests:

https://github.com/Senzing/keystore-generator/pull/9


cc 0.89 causes build failures, when building rustls on macos arm

Hello,
We're building a small rust crate for ios, for the aarch64-apple-ios-sim and x86_64-apple-ios targets, on a macos arm host.
Because this is for iOS, we create a "fat" static library using macOS's lipo tool, like so:
lipo -create -output myrustlib.a target/aarch64-apple-ios-sim/debug/myrustlib.a target/x86_64-apple-ios/debug/myrustlib.a

This works with rustls v0.21.10 and cc 1.0.88, but started failing with cc 1.0.89 with the following error:

fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: archive member target/x86_64-apple-ios/debug/myrustlib.a(fad98b632b8ce3cc-curve25519.o) cputype (16777228) and cpusubtype (0) does not match previous archive members cputype (16777223) and cpusubtype (3) (all members must match)

Looking at the last few cc commits, it's not clear to me what could have caused this change in behavior, but the problem evidently disappears when we pin cc = "=1.0.88" in Cargo.toml.
Unfortunately I don't have a minimal repro I can submit at the moment, but submitting for your consideration, and in case someone else runs into the same issue.

I suspect it is #873 that caused this.
Can you do a bisect on cc please?

Bisect seems to agree
git bisect start
# status: waiting for both good and bad commits
# bad: [b1c53ad938003c03ba72bdfe8e5aa93d00231a99] Release cc 1.0.89 (#988)
git bisect bad b1c53ad938003c03ba72bdfe8e5aa93d00231a99
# status: waiting for good commit(s), bad commit known
# good: [561543c5f0f3f4efed4e97844f89c8b424e19d3e] Release cc 1.0.88 (#977)
git bisect good 561543c5f0f3f4efed4e97844f89c8b424e19d3e
# bad: [2f587f5561fb9c3c02e5c9e186b2bea98691608a] Also support finding Windows tools on non-Windows host (#907)
git bisect bad 2f587f5561fb9c3c02e5c9e186b2bea98691608a
# bad: [59581e55a40678494e5b52b08fe2677a717bf8d8] Update windows-bindgen requirement from 0.53 to 0.54 (#982)
git bisect bad 59581e55a40678494e5b52b08fe2677a717bf8d8
# bad: [f0153a49733a83074d3df9984705f8a346e1b381] refactor target flags (#873)
git bisect bad f0153a49733a83074d3df9984705f8a346e1b381
# first bad commit: [f0153a49733a83074d3df9984705f8a346e1b381] refactor target flags (#873)

Opened #992 , can you test that please?

Also, it would be great if you have a minimal reproduction, so that I can add a regression test to prevent it from happening again

#992 works, thank you. Looking into a repro.

Here's a repro tested on a mac M1, running Sonoma 14.3.1, latest XCode, cargo 1.76.0 (stable).
Cargo.toml:
[package]
name = "cc-rs-repro"
version = "0.1.0"
edition = "2021"

[dependencies]
reqwest = { version = "0.11", features = ["rustls-tls"], default-features = false }
tokio = "1"
cc = "=1.0.89"

[lib]
name = "repro"
crate-type = ["staticlib"]

lib.rs
pub extern "C" fn repro() {
    let rt = tokio::runtime::Builder::new_current_thread()
        .enable_all()
        .build()
        .unwrap();
    rt.block_on(async {
        reqwest::Client::new()
            .post("example.org")
            .send()
            .await
            .unwrap();
    })
}

Steps:
rustup target add x86_64-apple-ios aarch64-apple-ios-sim
cargo build --target x86_64-apple-ios
cargo build --target aarch64-apple-ios-sim
lipo -create -output librepro.a target/aarch64-apple-ios-sim/debug/librepro.a target/x86_64-apple-ios/debug/librepro.a

Result when repro successful:
fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: archive member target/x86_64-apple-ios/debug/librepro.a(fad98b632b8ce3cc-curve25519.o) cputype (16777228) and cpusubtype (0) does not match previous archive members cputype (16777223) and cpusubtype (3) (all members must match)

Thanks, I will look into to it to see if it can be further simplified.

I've managed to simplify it further (if you haven't already, in case that might saves you some time)
pub extern "C" fn repro() {
    use ring::agreement;
    let rng = ring::rand::SystemRandom::new();
    agreement::EphemeralPrivateKey::generate(&agreement::X25519, &rng).unwrap();
}

cargo build --target x86_64-apple-ios
objdump target/x86_64-apple-ios/debug/librepro.a -h | grep arm64

On 1.0.88, this gives no output. A successful repro looks like:
target/x86_64-apple-ios/debug/librepro.a(fad98b632b8ce3cc-curve25519.o):	file format mach-o arm64
target/x86_64-apple-ios/debug/librepro.a(ca4b6ef5433f5aeb-aes_nohw.o):	file format mach-o arm64
[...]

Thanks, that will help a lot!

Which version of ring are you using, the 0.16 or the 0.17 ?

For what it's worth, I've created a minimum repo where I can reproduce the bug in CI here.

Note: I confirm it also happen in ring 0.17

Thanks, does it reproduce on latest cc?

No it works with latest cc

That's good to hear!
Since it works with latest cc, I will close this issue then


Microsoft Outlook OAuth2 "BAD User is authenticated but not connected."

I wanted to post this here to help others but also to track any developments I have in regards to this issue. I host a SaaS that supports connecting to customer mailboxes over IMAP. I'm using this package to facilitate all connections to the mailboxes. Mailboxes can be connected to over traditional username and password auth, or OAuth2 (only Microsoft Outlook and Google Gmail support right now).
I'm encountering an issue specifically with Microsoft Outlook connections where their servers appear to randomly blacklist (or temporarily block) connections with the IMAP error "BAD User is authenticated but not connected." if your server makes too many outgoing connections within a period of time. From reports I've seen online, this issue appears to only affect Microsoft Outlook connections connected to over OAuth2, maybe because of the access token expiry, where access tokens are short lived, which means you have to connect using a new token after they expire. I'm not sure how they identify or track sessions, but if they identify sessions by access tokens, then each new access token you generate would be a new session.
Some have stated that this is due to connecting over IPV6 (due to some bug in the Microsoft infrastructure?). I haven't tested this yet, as some report that Microsoft has stated this is no longer the issue, and even after they disable IPV6, they've reported this doesn't resolve the problem.
Luckily this thread here had a lot of knowledge on the issue (Galambos Robert specifically is an MVP here 👏):
https://answers.microsoft.com/en-us/outlook_com/forum/all/imap-is-not-working-correctly-on-outlook-office365/ab51cf7d-5b39-48dd-81a1-7f8dd5a91a17
Here's an excerpt that sheds some light on the issue (from Galambos Robert):

Hi All,
In case anybody has trouble with the same problem. I share my results.
First of all the Microsoft payed support was not really willing to help although one of they payed services is not working correctly. I had to constantly prove that the problem is on server side. They were also not willing to give much information.
However after a couple of escalation rounds I find the following:
There is an IMAP Policy in place, which banns or restricts users if they behave "badly". What they check and what are the limits is for some insane reasons not public. However I managed to get the information that they check something similar -- but not fully the same -- as "Set-ThrottlingPolicy" function (which is on on-premise servers)
https://docs.microsoft.com/en-us/powershell/module/exchange/server-health-and-performance/set-throttlingpolicy
In my case IMAPMaxConcurrency limit was hit according to the support. Based on my measurements this limit is 15. My clients use only 1-1 connection which means I could not have reached the limit.
As further testing on my side, I have found that the server does not have dead connection detection. Which results that if I am using mobile internet and the phone switches between cells, it gets a new IP address, the old TCP connections are on server side open, but otherwise dead (half open connection). So the server thinks that I have reached the limit.
The Idle Timeout for the TCP connections is around 20 minutes. So I can do nothing till 20 minutes if I hit the limit.
Usually all industrial standard IMAP servers have "dead connection detection" which means that the server sends a NOOP (no operation) every ~2 minutes down to client, and if it does arrives it closes the dead connection.
Unfortunately Microsoft Exchange Server does not have such feature according to the support.
Workaround possibilities:

You should reduce the number of connections to the server in you client. (This can be done in Thunderbird, and in most clients). This helps to reach the limit later, or not reach the limit at all.
If you are using mobile internet as I do, you can try what I am doing. I have created an IMAP Proxy server on my own server, which is on a fixed internet line, and implemented a dead connection detection algorithm. So basically the functionality what is missing from Microsoft...(there are a couple of such proxies available on the internet, but I tried an own solution in our company)

I hope that helps.
Regards,
Robert

I've been able to clarify some of the above with my own discoveries:
The IMAP concurrency limit is per Outlook account. I've had 3 Outlook accounts configured to be IDLE'ing at the same time, and they have all received the error "BAD User is authenticated but not connected" at different times, or some simply not at all. This has proven that the concurrency limit is per account, otherwise all of them would fail at the same time.
I'm still investigating this and will update this post with additions as I go, but with Outlook accounts, I've specifically set the IDLE timeout in this package to 1200 seconds (20 minutes) to align with the above post. So far, this appears to be working well.
I have and also restricted the number of open connections I make within one minute (using a Laravel job rate limiter). When a new message is received in the $folder->idle callback, I dispatch a job with that rate limiter to ensure I only connect with the mailbox a maximum of 10 times within one minute. This is set 5 connections lower than the above posted concurrency limit to allow for other devices that the user may have connected to the mailbox via IMAP. You may have to adjust this based on your user's IMAP mailbox usage:
RateLimiter::for('messages', function (object $job) {
    return Limit::perMinute(10)->by($job->mailbox->id);
});

// app/Jobs/ProcessMessage.php

class ProcessMessage implements ShouldBeEncrypted, ShouldBeUnique, ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, RetriesWithBackoff, SerializesModels;

    public function __construct(
        public readonly Mailbox $mailbox,
        public readonly Email $email,
    ) {
    }

    public function uniqueId(): string
    {
        return $this->mailbox->id.$this->email->id;
    }

    public function middleware(): array
    {
        return [new RateLimited('messages')];
    }

    public function handle(): void
    {
        // ...
    }
}

I hope this helps! ❤

Forgot to add, that this error has never occurred to me connecting to Gmail or other mail providers. From reports I've seen online, Gmail encourages active, regular use of new, short-lived IMAP connections. Gmail IMAP connectivity with IDLE has been pretty rock solid. I've set the IDLE timeout of Gmail connections (and all other non-Microsoft email providers) to 60 seconds) and I haven't experienced connectivity problems.

Another confirmed report and resource for this error (simultaneous open IMAP connections to one mailbox):
https://support.getmailbird.com/hc/en-us/articles/16662162740375--User-is-authenticated-but-not-connected-issue-with-Outlook-accounts

Just an update here, the above implementation with messages middleware ended up still encountering the same issue, albeit much less frequently.
I have since had to resort to implementing a "batch operations" system when processing emails, where only one other outgoing connection to Microsoft (alongside an idle connection) will ever be active.
Though this has actually led to cleaner operations. Here's the database table I'm using (in Laravel):
Schema::create('batch_operations', function (Blueprint $table) {
    $table->id();
    $table->foreignUuid('mailbox_id')->constrained()->cascadeOnDelete();
    $table->string('external_id')->index();
    $table->string('from')->index();
    $table->string('to')->index();
    $table->text('exception')->nullable();
    $table->timestamp('failed_at')->nullable();
    $table->timestamps();
});

This table is only responsible for handling moving emails to and from folders. from and to contain full Folder path names. external_id is the email's ID.
Next I created a scheduled command fired every 10 seconds to check for mailboxes that have batch operations to process:
class ProcessMailboxBatchOperations extends Command
{
    protected $signature = 'app:mailbox:batch:process';

    protected $description = 'Process batch mailbox operations.';

    public function handle(): void
    {
        Mailbox::query()
            ->whereHas('batchOperations', fn ($query) => $query->whereNull('failed_at'))
            ->each(fn (Mailbox $mailbox) => ProcessBatchOperations::dispatch($mailbox));
    }
}

Registering it in the console command scheduler:
class Kernel extends ConsoleKernel
{
    /**
     * Define the application's command schedule.
     */
    protected function schedule(Schedule $schedule): void
    {
        $schedule->command(ProcessMailboxBatchOperations::class)->everyTenSeconds();
    }
}

Reporting back after some time -- this strategy seems to have completely resolved this error from occurring. I have yet to see it since implementation 🎉  (knock on wood)


[Doc] Adds office color table to Design Tokens page

Pull Request
📖 Description
A table at the end of  the design tokens page appears to have been accidentally deleted.
[Edit] See comment Original delete intentional.
[Edit] Added new table based on review comments

🎫 Issues

missing table?

👩💻 Reviewer Notes

Was the table deletion intentional? If so, the text above it should be changed.
The text above the table also mentions accent colors for 17 different Office applications. I find it confusing and am unsure what it is trying to convey to the reader.

📑 Test Plan
✅ Checklist
General

[ ] I have added tests for my changes.
[X] I have tested my changes.
[ ] I have updated the project documentation to reflect my changes.
[X] I have read the CONTRIBUTING documentation and followed the standards for this project.

Great!
Could you put a screenshot of the table in the description of this PR. This will be useful for the release notes.

Great!
Could you put a screenshot of the table in the description of this PR. This will be useful for the release notes.

Done 😄

I fixed the visual glitch by hooking into OnContentConverted.  MarkdownSection calls it multiple times. I think that is another issue that needs to be addressed separately.

What do you mean?

What do you mean?

There a 25 enumerated values for OfficeColor. Only 24 are "known" Microsoft applications.
Maybe, remove the actual number from the text above the table. What do you think?

What do you mean?

There a 25 enumerated values for OfficeColor. Only 24 are "known" Microsoft applications.
Maybe, remove the actual number from the text above the table to remove any confusion. What do you think?

Yes, that sounds good to me.


README

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

Issue resolved, information added to project


[SMALLFIX]Use static imports for standard test utilities in MasterFaultToleranceIntegrationTest.java

Use static imports for standard test utilities in MasterFaultToleranceIntegrationTest.java

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/Alluxio-Pull-Request-Builder/17295/
Test PASSed.


Sometimes doesn't open with inaccessible paths error

The error quickly flashes in the terminal that opens.
Inaccessible paths: /example/path/'/example/path
ranger version: ranger 1.9.3
neovim version: v0.10.0
I might try to see how this works and fix it later, no guarantees tho.

This happens because selectfile is sometimes an absolute path instead of a relative path from what I can tell.
So build_ranger_cmd needs to be changed to account for that. I'm not that good at lua, but will now attempt to make a fix.

Hi @Spiderfffun, how do you reproduce this? Do you just open ranger?

Hi @Spiderfffun, how do you reproduce this? Do you just open ranger?

Yeah, no matter the way I open it if I am not in the same directory it instantly closes.


Live Quiz

Erase existing environment (Screen capture)
Setup our working environment (git clone's)

Erase existing environment

Clone repo

activate tools step
bundler version 2.3.26
ruby version 3.1.4

Setup environment for project
avantika.chittari@Avantikas-MacBook-Pro student_2025 % ls
404.html		_includes		index.md
Gemfile			_layouts		navigation
LICENSE			_notebooks		requirements.txt
Makefile		_posts			scripts
README.md		_sass			venv
README4YML.md		assets
_config.yml		images
avantika.chittari@Avantikas-MacBook-Pro student_2025 %

Run Server Address


Can't resolve "emails"

Hi, I add mailing to my current nextjs project and the npx mailing working and the preview server is up.
However, when I start my project and try to use sendMail from my nextjs API, I got an error Module not found: Can't resolve 'emails'
I have import { sendMail } from 'emails'
What do I need to do?

Hey @tpmh31292, thanks for trying mailing.
I'm guessing that is not the correct path to your emails directory in the import statement. If you correct that path to point to the emails directory (where index exports sendMail), it should work.
Feel free to ping me on discord if you need more help https://discord.com/invite/fdSzmY46wY


Add ActionProps runtime value of 'node18-actions'.

Auth0 has a runtime for Actions/Triggers that doesn't seem to be published in their documentation.  I found this why troubleshooting creating a 'credentials-exchange' action and trying to determine the correct version and runtime to set for this trigger type.  I ended up having to make an API call to the Management API endpoint GET /actions/triggers which returned the following response:
  "triggers": [
    {
      "id": "post-login",
      "version": "v1",
      "status": "DEPRECATED",
      "runtimes": [
        "node12"
      ],
      "default_runtime": "node12",
      "compatible_triggers": []
    },
    {
      "id": "post-login",
      "version": "v2",
      "status": "DEPRECATED",
      "runtimes": [
        "node12",
        "node16"
      ],
      "default_runtime": "node16",
      "compatible_triggers": []
    },
    {
      "id": "post-login",
      "version": "v3",
      "status": "CURRENT",
      "runtimes": [
        "node12",
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": [
        {
          "id": "post-login",
          "version": "v2"
        }
      ]
    },
    {
      "id": "credentials-exchange",
      "version": "v2",
      "status": "CURRENT",
      "runtimes": [
        "node12",
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": []
    },
    {
      "id": "credentials-exchange",
      "version": "v1",
      "status": "DEPRECATED",
      "runtimes": [
        "node12"
      ],
      "default_runtime": "node12",
      "compatible_triggers": []
    },
    {
      "id": "pre-user-registration",
      "version": "v1",
      "status": "DEPRECATED",
      "runtimes": [
        "node12"
      ],
      "default_runtime": "node12",
      "compatible_triggers": []
    },
    {
      "id": "pre-user-registration",
      "version": "v2",
      "status": "CURRENT",
      "runtimes": [
        "node12",
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": []
    },
    {
      "id": "post-user-registration",
      "version": "v2",
      "status": "CURRENT",
      "runtimes": [
        "node12",
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": []
    },
    {
      "id": "post-user-registration",
      "version": "v1",
      "status": "DEPRECATED",
      "runtimes": [
        "node12"
      ],
      "default_runtime": "node12",
      "compatible_triggers": []
    },
    {
      "id": "post-change-password",
      "version": "v1",
      "status": "DEPRECATED",
      "runtimes": [
        "node12"
      ],
      "default_runtime": "node12",
      "compatible_triggers": []
    },
    {
      "id": "post-change-password",
      "version": "v2",
      "status": "CURRENT",
      "runtimes": [
        "node12",
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": []
    },
    {
      "id": "send-phone-message",
      "version": "v2",
      "status": "CURRENT",
      "runtimes": [
        "node12",
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": []
    },
    {
      "id": "send-phone-message",
      "version": "v1",
      "status": "DEPRECATED",
      "runtimes": [
        "node12"
      ],
      "compatible_triggers": []
    },
    {
      "id": "password-reset-post-challenge",
      "version": "v1",
      "status": "CURRENT",
      "runtimes": [
        "node16",
        "node18-actions"
      ],
      "default_runtime": "node18-actions",
      "compatible_triggers": []
    },
    {
      "id": "login-post-identifier",
      "version": "v1",
      "status": "CURRENT",
      "default_runtime": "node18",
      "runtimes": [],
      "compatible_triggers": []
    },
    {
      "id": "notifications-custom-provider-phone",
      "version": "v1",
      "status": "CURRENT",
      "default_runtime": "node18",
      "runtimes": [],
      "compatible_triggers": []
    },
    {
      "id": "notifications-custom-provider-email",
      "version": "v1",
      "status": "CURRENT",
      "default_runtime": "node18",
      "runtimes": [],
      "compatible_triggers": []
    }
  ]
}

After setting the 'node18' runtime to this credentials-exchange trigger, when viewing in the Auth0 UI, the description shows the runtime as Runtime: Node 18 BETA (Not Recommended).

After setting the runtime to 'node18-actions', again viewing in the Auth0 UI, the description now states Runtime: Node 18 Recommended.

That's very interesting, I never noticed that, but you are right! It shows up as Not Recommended on the website. Thank you for the investigation!


Unable to install dev-2024-10 on Linux due to renamed release asset

Looks like https://github.com/odin-lang/Odin/releases/tag/dev-2024-10 renamed the Linux-related asset from odin-ubuntu-amd64-dev-2024-10.zip to odin-linux-amd64-dev-2024-10.zip

I've created a fork of this plugin over here that fixes this.


pjsip can't login jitsi

hello, I am use pjsip in my pbx,
When I'm login, I got this error in my pbx log
[2016-03-14 17:38:37] NOTICE[2225] chan_sip.c: Registration from '"9806"<EMAIL_ADDRESS>failed for '<IP_ADDRESS>:5062' - Wrong password
But I'm sure my password is not wrong
and I got log in jitsi
From: "9806" sip:9806@<IP_ADDRESS>;tag=a63af4fb
To: "9806" sip:9806@<IP_ADDRESS>;tag=as113d4919
Call-ID: 6ecd4f4f1f889bb24a3376b2e8d1eda9@0:0:0:0:0:0:0:0
CSeq: 8 REGISTER
Server: FPBX-12.0.70(13.7.2)
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO,PUBLISH,MESSAGE
Supported: replaces,timer
Content-Length: 0
'ɦVX񆠓                 E ɔ  5񱠠  ( 򓆓ā񠠒EGISTER sip:<IP_ADDRESS>:5062 SIP/2.0
Call-ID: 6ecd4f4f1f889bb24a3376b2e8d1eda9@0:0:0:0:0:0:0:0
CSeq: 9 REGISTER
From: "9806" sip:9806@<IP_ADDRESS>;tag=a63af4fb
To: "9806"<EMAIL_ADDRESS>Max-Forwards: 70
User-Agent: Jitsi2.9.5500Windows 8
Expires: 600
Contact: "9806" sip:9806@<IP_ADDRESS>:5062;transport=udp;registering_acc=192_168_0_250;expires=600
Via: SIP/2.0/UDP <IP_ADDRESS>:5062;branch=z9hG4bK-393436-9e5bb3815823dfe6c5575c4ac5333287
Content-Length: 0
'ɦVX񆠟  _               E Qɔ  5𥀨 򠠠 ēƂ=  SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP <IP_ADDRESS>:5062;branch=z9hG4bK-393436-9e5bb3815823dfe6c5575c4ac5333287;received=<IP_ADDRESS>;rport=5062
From: "9806" sip:9806@<IP_ADDRESS>;tag=a63af4fb
To: "9806" sip:9806@<IP_ADDRESS>;tag=as113d4919
Call-ID: 6ecd4f4f1f889bb24a3376b2e8d1eda9@0:0:0:0:0:0:0:0
CSeq: 9 REGISTER
Server: FPBX-12.0.70(13.7.2)
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO,PUBLISH,MESSAGE
Supported: replaces,timer
WWW-Authenticate: Digest algorithm=MD5,realm="asterisk",nonce="4fc9fcf6"
Content-Length: 0
anyone know what happen?and how can I do?

The first REGISTER message do not contain the WWW-Authenticate field, so the SIP server return statuscode 401 with WWW-Authenticate: Digest algorithm=MD5,realm="asterisk",nonce="4fc9fcf6".
You should retransmit the REGISTER message that contain the WWW-Authenticate field and add value of "response" to it. the "response" is calculated by MD5 with realm, nonce, cnonce, password etc.

Just tried Jitsi 2.9.5513 against FPBX-13.0.119(13.8.2) and PJSip is working fine (UDP and TLS).


NonlinearSolve.jl not precompiling anymore

My tests at ProbNumDiffEq.jl fail because NonlinearSolve.jl can not precompile anymore, which was not an issue some days ago. See this github action for a full stack trace:
https://github.com/nathanaelbosch/ProbNumDiffEq.jl/actions/runs/6956405592/job/18927191648?pr=269

What about upgrading to the patch hotfix v7.6.1?

Works again, thanks for the fix.


[Umbrella][V2] Kyuubi server pick task from metadata db with priority

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the proposal
Kyuubi server pick task from metadata db with priority.
Task list

[x] #5327
[x] #5328

Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

Close due to finish all sub-task


Not compatible with latest version of Peewee

Taemin is not compatible with Peewee in the 3.x version

Should be fixed now


Clean up step skipped? logic

Simplify skipped? methods

Simplifies the skipped? logic in steps by allowing them to query the skipped state of previous steps.
The tests have only been refactored where necessary.

Simplify skipped? tests

As the skipped? logic is now more concise the tests can also be made simpler.

I've pushed another commit to simplify the logic around getting other steps as suggested, and I think there's more that can be done still to simplify it even further but that should be picked up in a follow up PR IMO as this one is big enough.


shade additional dependencies in java-instance.jar

Motivation
Some dependencies are not shaded in the java-instance.jar.  Probably leaked into the JAR via other dependencies.

rerun java8 tests

rerun cpp tests

rerun java8 tests

rerun java8 tests

rerun java8 tests

rerun java8 tests


Can not place multiple orders with JSON object param.

Issue subject
Source code comes from here
https://github.com/binance/binance-futures-connector-node/blob/main/examples/um_futures/account/placeMultipleOrders.js
const batchOrders = [
  { symbol: 'BNBUSDT', ...others},
  { symbol: 'BNBUSDT', ...others }
]
umFuturesClient
  .placeMultipleOrders(batchOrders)
  .then((response) => console.log(response))
  .catch(console.error)

Expected behaviour
I believe that the request params should be transformed to string before sending
const batchOrders = [
  { symbol: 'BNBUSDT', ...others},
  { symbol: 'BNBUSDT', ...others }
]
umFuturesClient
  .placeMultipleOrders(JSON.stringify(batchOrders))
  .then((response) => console.log(response))
  .catch(console.error)

I'm running my trading bot with this config and it works well
Actual behaviour
N/A
Steps to reproduce
N/A
Environment
N/A

Thanks for pointing out this issue. It has been updated in v0.1.6


Put color definitions in a standalone file

Is your feature request related to a problem? Please describe.
We can put all color definitions in one file, and (re)use them everywhere using commands \input and \colorlet.
Describe the solution you'd like
For example, my file structure is
├── commons
│   ├── bib-settings.tex
│   ├── colors.tex
│   ├── html-color-codes.tex
│   ├── newcommands.tex
│   └── socials.tex
├── ...

I put all my color definitions in commons\colors.tex as follows
%---------------------------------------------------------------------------------------
% user-defined colors

\definecolor{tsinghua}{rgb}{.434, .09, .531}
\definecolor{tsinghua-1}{HTML}{791CB5}
\definecolor{tsinghua-2}{HTML}{4B0C77}

%---------------------------------------------------------------------------------------
% colors for social icons

\definecolor{weixin}{rgb}{.184, .533, .098}
\definecolor{linkedin}{HTML}{0a66c2}
\definecolor{orcid}{HTML}{a6ce39}
\definecolor{twitter}{RGB}{29, 155, 240}
\definecolor{facebook}{HTML}{1b74e4}

%---------------------------------------------------------------------------------------
% built-in colors

\definecolor{black}{RGB}{0, 0, 0}
\definecolor{red}{rgb}{0.95, 0.20, 0.20}
\definecolor{darkgrey}{rgb}{0.45, 0.45, 0.45}
\definecolor{orange}{rgb}{0.95, 0.55, 0.15}
\definecolor{burgundy}{rgb}{0.596078, 0, 0}% 139/255 (0.545098) or 152/255 (0.596078)
\definecolor{purple}{rgb}{0.50, 0.33, 0.80}
\definecolor{lightblue}{rgb}{0.22, 0.45, 0.70}
\definecolor{green}{rgb}{0.35, 0.70, 0.30}

In moderncvcolorred.sty, one can write
\input{commons/colors}

\colorlet{color0}{black}% black
\colorlet{color1}{red}% red
\colorlet{color2}{darkgrey}% dark grey

instead of defining the black and dark grey colors again and again.
Also in files moderncviconsawesome.sty and moderncviconsacademic.sty, we can use \input{commons/colors} (both) and \renewcommand*{\orcidsocialsymbol}        {{\color{orcid}\small\faOrcid}~}, \renewcommand*{\orcidsocialsymbol}        {{\color{orcid}\small\aiOrcid}~} (respectively) to get colored icons.
Describe alternatives you've considered
NA
Additional context
NA

Please do submit a pull request for review

Closed by #137

colors.tex is a bad name for a file in the global default input tree, (it is not distributed in texlive and currently leads to errors after an update
https://tex.stackexchange.com/questions/722345/file-commons-colors-tex-not-found
could the file be renamed to modernccv-colors.tex or something?

@davidcarlisle There was an issue filed at https://github.com/moderncv/moderncv/issues/194 - which is fixed at https://github.com/moderncv/moderncv/issues/195

@koppor  so there was, thanks for the fix, and sorry for the noise.


 Quite often, we have seen the job complete, be destroyed, then fail to be recreated due to a timeout in getting a database connection. When this happens, the cron job is completely lost.
I'm not sure if using a proxy is the best approach to fixing the problem, but didn't want to copy more of the delayed_job code just to intercept the destroy. This will create a proxy on the delayed job and intercept an attempt to destroy a cron job and instead reschedule the job. This prevents the destroy and recreation from happening in separate transactions, and worst case scenario, will run the job again, instead of losing the cron job all together.

Thank you for the pull request. This is a new problem I never experienced before. I am not sure if the issue really happens because of Delayed::Job / Delayed::Cron::Job. There is no connection/transaction specific logic in these gems.
Could you please at least provide a failing spec that shows the problem?
I am concerned that your solution with overwriting the destroy method could lead to other issues, especially losing the ability to destroy a cron job when actually wanted.

Thanks for looking over my PR! I'll try to put together a failing test sometime in the next week or two.
You're correct that there is no transaction logic in the gems, and that's a problem for how delayed_cron_job destroys the delayed_job in one hook, and then tries to recreate it in another. It needs to be an atomic operation to not be lost, from what I've seen.

I've added a spec that will fail on the master branch. We use SQL Server and end up with transaction issues that have caused the connection not to be able to create the cloned delayed_job, so I can't recreate that exact situation, but this pretty much demonstrates any database connectivity issue.
To create the failing spec, I had to upgrade Ruby to a 2.5 version to be able to take advantage of shared in-memory SQLite3 connections, otherwise the in-memory database gets lost on disconnect.
The change I made (I think) should only intercept a destroy attempt on a cron DelayedJob inside the perform delayed_job code, so I don't think it should affect an attempt to delete the DelayedJob outside that code. I don't think there's ever a reason a cron DelayedJob should ever be destroyed inside the delayed_job code, is there?

I had a look at the issue and I see the point of the possibility to lose jobs when some connection issue occurs between destroy and save. However, I do not like to make assumptions about the destroy method not being used otherwise, be it in jobs or other plugins. Therefore, I came up with another approach the minifies the time of disabling the destroy method and builds on the current code.
Could you please have a look at badfdb30939587df8f4874841af08ca5171847ad and check if that fixes your issues, too?

I like this approach much better than what I put together. Looks great! :+1: Thanks!!


🐛 BUG: wrangler types generates incorrect types for Durable Objects

Which Cloudflare product(s) does this pertain to?
Wrangler core
What version(s) of the tool(s) are you using?
3.51.0 [Wrangler]
What version of Node are you using?
No response
What operating system and version are you using?
Mac Sonoma
Describe the Bug
Observed behavior
export interface Env {
MY_DURABLE_OBJECT: DurableObjectNamespace; // No generic parameter based on wrangler.toml
}
Expected behavior
export interface Env {
MY_DURABLE_OBJECT: DurableObjectNamespace;
}
Steps to reproduce
Please provide the following:

Generate Durable Objects "Hello, world!" example
Run wrangler types
Incorrect type info will be created

This was broken by the JS RPC changes added for developer week.
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
N/A

This was addressed in https://github.com/cloudflare/workers-sdk/pull/6259


[BUG]

Describe the bug

While downloading the PDF only the summery part is there rest of page is showing blank in PDF
Product Flavor

[ ] Managed (https://rxresu.macd)
[ ] Self Hosted

To Reproduce

Go to Export PDF Link
Click on Download Symbol
PDF is downloaded with only the summary part rest of the page is blank

Expected behavior

Full resume should be downloaded with all content
Screenshots

Desktop (please complete the following information):

OS:  Windows
Browser  Chrome
Version  Version 114.0.5735.110 (Official Build) (64-bit)

Additional context

This issue i am facing in castform template


Roll engine to 7ec4b6115d3eff69af96250aa3f14da97880cc15

Roll engine to pick up documentation changes to StrokeJoin and StrokeCap.

Going to have to try again with a different hash...


PowerDNS Recursor: add package and service

Motivation for this change
See #21999
Things done

[x] Tested using sandboxing
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change (none)
[x] Tested execution of all binary files
[x] Fits CONTRIBUTING.md.

@vcunat Is there any caveats with enabling DNSSEC validation?

I know mainly general caveats and not pdns in particular.  There will be slightly higher latency in some cases, especially on cold cache; the extra CPU for validation (cryptography) tends to be negligible in practice.  The link from description claims that the root trust anchor is built in, so hopefully this simple config switch is the only needed step.

validate it is then.


Cannot read property 'is' of null after latest csscomb update

Has anyone got an idea why this is failing? It only started after the update of CSScomb. It seems to be failing on the new comb option of lines-between-rulesets.
Error:
Cannot read property 'is' of null
TypeError: Cannot read property 'is' of null
at Object.insertNewlines (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:237:20)
at node.forEach (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:124:12)
at Node.forEach (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\gonzales-pe\lib\gonzales.js:175:83)
at Object.processRuleSets (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:123:10)
at Object.processBlock (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:98:12)
at Object.process (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:89:10)
at C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\core.js:380:14
at Array.forEach (native)
at Comb._processTree (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\core.js:379:8)
The example SCSS rule that will cause this is:
/* TEST COMB */
.test-comb {
    @include font-size(22);
    @include clearfix;
    @include position(vertical, absolute);

    background-color: gray;
    color: red;
    display: block;
    height: 100%;
    width: 100%;

    @include break-min($md-break) {
        color: blue;
    }

    @media (min-width: $xx-break) {
        color: green;
    }
}

Link to my .csscomb.json:
https://gist.github.com/kinkwilde/7b36f984bfeac75e5daf7e353e6c8071

May be some of these: https://github.com/csscomb/csscomb.js/blob/dev/src/options/lines-between-rulesets.js#L229-L241
I recommend you create a bug Issue over at https://github.com/csscomb/csscomb.js

OK, will do - I'll update here with the response I get.

Awesome, thanks! Also if you add a link to here in your Issue over there, we will be able to see they are related and whether it is closed 👍 .

OK - quick update. Turns out to be an issue with windows machines as it apparently works on mac. It will be fixed in csscomb version 4.3.0. So someone will need to make sure that atom-beautify will update to this version when it is released.
https://github.com/csscomb/csscomb.js/issues/525

I'm seeing this (seemingly) same issue now on my mac
Cannot read property 'is' of null
Cannot read property 'is' of null
Hide Stack Trace
TypeError: Cannot read property 'is' of null
    at Plugin.insertNewlines (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:237:20)
    at node.forEach (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:124:12)
    at Node.forEach (/Users/jchappell/.atom/packages/atom-beautify/node_modules/gonzales-pe/lib/gonzales.js:175:83)
    at Plugin.processRuleSets (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:123:10)
    at Plugin.processBlock (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:98:12)
    at Plugin.process (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:89:10)
    at /Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:384:14
    at Array.forEach (native)
    at Comb._processTree (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:383:8)

Had the same issue, just removed the comments at the top of my file and it works!
Apparently if it's  starting with any comment, be it line comment with // or block comment with /*, csscomb will give this UnhandledPromiseRejectionWarning error.

I'm still having this issue, and yoh-m is correct that starting with a comment seems to be the culprit. Has any fix been identified for this? I'd prefer to keep the comments in my code where they are.


delegate functions not getting called for native implementation

Delegate functions are not getting called for native implementation
let controller = SPPermissions.native([.camera])
controller.delegate = self
controller.present(on: vc)

But when implementation is for dialog, delegates are getting fired.
let controller = SPPermissions.dialog([.camera])
controller.delegate = self
controller.present(on: vc)

What I am missing here?

Can you save controller as property? Problem this, after present controller removed from memory by system and delegate don't available because week.

Fixed in version 6.6.5. Please, update.


app_direct requires unecessary forward slash in url

The /app_direct/ url will only works if we use:
shinyproxyapp.com/app_direct/myappname/ while shinyproxyapp.com/app/myappname does not require this extra backslah. This is counter intuitive to have set one at the end for the /app_direct/ way.
This has been introduced in ShinyProxy 2.2.0 as earlier we could use /app_direct/ the same way as /app/ without the end slash after app name.

Hi @dylancis, Thanks for creating the issue. I agree we should fix this.

@tverbeke  I believe the line in question is here:
https://github.com/openanalytics/shinyproxy/blob/7c5448223fcff55f29ad630f7ac36d380ff68597/src/main/java/eu/openanalytics/shinyproxy/controllers/AppController.java#L112

@dylancis Fixed in ShinyProxy 2.2.2!


TemplateProvider : GetHierarchy - ProvisioningTemplate version is overwritten.

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Observed Behavior
When using TemplateProvider.GetHierarchy method all the templates in the Templates collection have the same version number as ProvisioningHierarchy object. In the ProvisioningTemplate class, if the ProvisioningHierarchy object is set, the template returns hierarchy version.
Expected or Desired Behavior
Does it really make sense? In case we are able to obtain the ProvisioningHierarchy version by using it's own Version property or access it directly from the ProvisioningTemplate by accessing ParentHierarchy.Version, the desired behaviour would be to get the Templates real version - the ones assigned in the file.
Steps to Reproduce
Load ProvisioningHierarchy object with a template with provider.GetHierarchy method. Check the version of the loaded templates.
Submission Guidelines
File containing the code:
Framework\Provisioning\Model\ProvisioningTemplate.cs
Property:
public double Version {
get
{
if (this.ParentHierarchy != null)
{
return (this.ParentHierarchy.Version);
}
else
{
return _version;
}
}
set
{
if (this.ParentHierarchy != null)
{
this.ParentHierarchy.Version = value;
}
else
{
this._version = value;
}
}
}
Sharing is caring.

Can you provide some context as to how you're doing this? SharePoint CSOM, PnP, etc?

I would like to be able to store multiple templates in the hierarchy and apply them based on the version. E.g. if in the site I have already v1.0 applied, let's apply only v1.1:
<?xml version="1.0"?> <pnp:Provisioning xmlns:pnp="http://schemas.dev.office.com/PnP/2018/05/ProvisioningSchema">      ...   <pnp:Templates ID="TEMPLATES">     <pnp:ProvisioningTemplate ID="Base" Version="1">       ...     </pnp:ProvisioningTemplate>     <pnp:ProvisioningTemplate ID="Hotfix1" Version="1.1">       ...     </pnp:ProvisioningTemplate>   </pnp:Templates> </pnp:Provisioning>
GetHierarchy seems to be the only option to retrieve multiple templates from the file at the moment.

Didn't really answer the question, but seems like you're referring to the PnP provisioning support in PnP CSOM.
Their repo is the best place to ask that question as I'm not sure they are monitoring this one as closely: https://github.com/SharePoint/PnP-Sites-Core
Please post your question in their issue list.


[models] PBR system not considering environment maps properly?

Please, before submitting a new issue verify and check:

[x] I tested it on latest raylib version from master branch
[x] I checked there is no similar issue already reported
[x] My code has no errors or misuse of raylib

Issue description
PBR-example doesnt look like this https://raw.githubusercontent.com/raysan5/raylib/master/examples/models/models_material_pbr.png
Environment
Windows 10 x64, OpenGL 4.5 (using 3.3)
Issue Screenshot

Output log:
https://pastebin.com/y4AwrYT4

PBR system requires a complete review. That requires some work, not a priority at this moment.

Yes, checked closely, seems environment map is missing (there are some warnings in the log).
Tested couple of examples and these works fine when exiting, but that pbr example throws exception when pressing ESC (or clicking X) on models.c UnloadModel(Model model)  function at line 802 (  RL_FREE(model.materials[i].params);  ).

After a quick check, it seems the texture irradiance cubemap is not properly generated, also not sure about the prefilter map.
Probably related to some big changes introduced while working on #721. It requires some more investigation.

Closing this issue, example need a complete rewrite...


MongoError: connect ECONNREFUSED

This sounds like an issue with your mongo setup. If you haven't managed to figure out whats wrong yet, can you reopen this issue with more information about your mongo configuration and parse server configuration?