Introduce an option to make Weld injection more restrictive

Based on discussions on #3, we should take some steps to resolve possible problems if more extensions try to resolve the same parameters. The suggested approach was to always annotate the parameter types we do not own with some injection-suggesting annotation. However, this is highly inconvenient for day-to-day use if you are not running into such troubles.
Therefore the approach we could take would be to introduce an option (by default disabled) which would only perform injection if said annotation would be present on parameter. Note that this does not concern class field injection at all. The option could be enabled by either value on @WeldSetup(strictInjection="true") annotation or by static method on WeldInitializer (WeldInitializer.enableStrictInjection()).
The annotation to go along with the to-be-injected parameter could be something like @WeldInject.
Choosing this compromise, we can still allow to use Weld injection without any additional annotation hell but you would still be able to address such hell, should you find yourself in one.

Choosing this compromise, we can still allow to use Weld injection without any additional annotation hell but you would still be able to address such hell, should you find yourself in one.

I think that sounds like a positive result for your users: a nice balance between convenience and robustness (when necessary)! 👏

Working through some examples and thinking through how I'm likely to use weld-junit, I've become a bit more of a fan of the "greedy" approach as a good default.  Being able to limit the parameter resolution selectively sounds like a great enhancement.

After having put a bit more thought into the subject, I am tossing around the idea of categorizing ParameterResolver implementations by behavior as follows.

explicit: support requires an annotation for disambiguation
implicit: support is automatic for types owned by the resolver
speculative: a resolver claims it can support a given parameter even if it potentially should not (a.k.a., greedy or eager)

Thus, for this GitHub issue, you are proposing speculative behavior by default with an opt in for explicit support.
With that in mind, I'm wondering if "strict" best describes the mode you are proposing to support.
Perhaps it would be better to introduce an InjectionMode enum with constants representing supported modes. You may start with only two (on/off, which could be supported via a boolean flag as you've suggested), but using an enum from the start allows your API to evolve safely over time.
Food for thought...
Sam


Failing to get all frames causes confusing errors

If odin fails to write the correct number of frames we get an error like:
Traceback (most recent call last):
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 577, in contingency_wrapper
    ret = yield from plan
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/src/hyperion/experiment_plans/pin_centre_then_xray_centre_plan.py", line 67, in pin_centre_then_xray_centre_plan
    yield from detect_grid_and_do_gridscan(
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/src/hyperion/experiment_plans/grid_detect_then_xray_centre_plan.py", line 153, in detect_grid_and_do_gridscan
    yield from flyscan_xray_centre(flyscan_xray_centre_parameters)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/utils/__init__.py", line 1202, in dec_inner
    return (yield from plan)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 384, in subs_wrapper
    return (yield from finalize_wrapper(_inner_plan(),
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 511, in finalize_wrapper
    ret = yield from plan
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 382, in _inner_plan
    return (yield from plan)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/utils/__init__.py", line 1202, in dec_inner
    return (yield from plan)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 1349, in set_run_key_wrapper
    return (yield from msg_mutator(plan, _set_run_key))
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 247, in msg_mutator
    ret = yield msg
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 1588, in _run
    new_response = await coro(msg)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 2420, in _unstage
    ret = obj.unstage()
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 120, in unstage
    self.stop_odin_when_all_frames_collected()
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 109, in stop_odin_when_all_frames_collected
    ).wait(self.ALL_FRAMES_TIMEOUT)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/ophyd/status.py", line 432, in wait
    raise WaitTimeoutError(f"Status {self!r} has not completed yet.")
ophyd.utils.errors.WaitTimeoutError: Status SubscriptionStatus(device=eiger_odin_file_writer_num_captured, done=False, success=False) has not completed yet.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 1668, in _run
    raise err
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 1503, in _run
    msg = self._plan_stack[-1].throw(stashed_exception or resp)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/src/hyperion/device_setup_plans/utils.py", line 27, in start_preparing_data_collection_then_do_plan
    yield from bpp.contingency_wrapper(
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/preprocessors.py", line 587, in contingency_wrapper
    yield from except_plan(e)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 1588, in _run
    new_response = await coro(msg)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 2441, in _stop
    return await maybe_await(obj.stop())  # nominally, this returns None
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 139, in stop
    self.disable_roi_mode()
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 142, in disable_roi_mode
    self.change_roi_mode(False)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 152, in change_roi_mode
    status = self.cam.roi_mode.set(
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/ophyd/signal.py", line 2121, in set
    return super().set(value, timeout=timeout, settle_time=settle_time)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/ophyd/signal.py", line 379, in set
    raise RuntimeError(
RuntimeError: Another set() call is still in progress for eiger_cam_roi_mode

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/bluesky/run_engine.py", line 1687, in _run
    obj.unstage()
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 120, in unstage
    self.stop_odin_when_all_frames_collected()
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/dodal/src/dodal/devices/eiger.py", line 109, in stop_odin_when_all_frames_collected
    ).wait(self.ALL_FRAMES_TIMEOUT)
  File "/dls_sw/i03/software/bluesky/hyperion_v7.0.0/hyperion/.venv/lib/python3.10/site-packages/ophyd/status.py", line 432, in wait
    raise WaitTimeoutError(f"Status {self!r} has not completed yet.")
ophyd.utils.errors.WaitTimeoutError: Status SubscriptionStatus(device=eiger_odin_file_writer_num_captured, done=False, success=False) has not completed yet.

The underlying error of Status SubscriptionStatus(device=eiger_odin_file_writer_num_captured, done=False, success=False) is ok (but could be a bit more user friendly). It is also confused by the Another set() call is still in progress for eiger_cam_roi_mode, which is stop being called on the detector and failing. We should try and clean this up.

At least it tells us which status is not completed yet now...


Invert string shown for enabling/disabling privacy protection

Task/Issue URL: https://app.asana.com/0/414730916066338/1184397698929617/f
Tech Design URL:
CC:
Description:
The app displays the wrong label for the overflow option for enabling/disable privacy protection. This PR corrects that logic
Steps to test this PR:

Open cnn.com
Open the overflow menu; verify that "Disable privacy protection" is shown in overflow
Open privacy grade; verify that "Site Privacy Protection" is enabled
From privacy grade; disable "Site Privacy Protection"
Return to browser screen, launch overflow
Verify that Enable privacy protection is in overflow
Click it
Launch overflow; verify it now says Disable privacy protection
Open privacy grade; verify the toggle shows as enabled

Internal references:
Software Engineering Expectations
Technical Design Template

I should have pushed this on a hotfix branch. no matter; it's merged now so will close this manually


Add additional alert templates for SQL server on Windows

[Enter feedback here]
We have a need to use SQLInsights to monitor/alert from Azure VM based SQL servers, which requires an alert template to be created for each metric we wish to alert from. Having some available templates would make this much easier to implement

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

ID: c7eb289f-1abb-3254-b1c1-3b2fa20eddc7
Version Independent ID: ffa6089a-4cc1-a7fe-b631-c15180941629
Content: Monitor your SQL deployments with SQL Insights (preview) - Azure SQL Database
Content Source: azure-sql/database/sql-insights-overview.md
Service: sql-db-mi
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

@giant-bean Thank you for your feedback. We are reviewing this and will get back shortly.

#reassign:MashaMSFT

Hi @giant-bean , thanks so much for your feedback! Would you mind submitting this directly to the product group so it can be triaged and tracked appropriately? You can do so here: https://aka.ms/sqlfeedback. I'll pass along your feedback as well, but your suggestion carries more weight through the appropriate channel.
Thanks again for reaching out and I hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#please-close


restrain langchain version

Type of Change
temperately restrain component version until we adapt to the latest

@XuhuiRen before adapt to latest langchain, we need to restrain to last stable version

seems ipex version issue

@VincyZhang  did you see any issue from current langchain version without upgrading?

@VincyZhang did you see any issue from current langchain version without upgrading?

API changed, no "Chroma" in "langchian.vectorstores"

Neuralchat UT is due to IPEX version not match with torch, and fastfaile due to baseline UT has no version controls.


[SYSTEMML-1929] Update deploy-mode in sparkDML.sh and docs

Updated spark-submit description to use --deploy-mode instead of deprecated parameters and corrected batch mode copy/paste error.

Could we do the same for scripts/sparkDML.sh, incl the removal of spark.akka.frameSize?

Good catch Matthias!  I'll add commit for sparkDML.sh to this PR too.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2118/

I updated sparkDML.sh to use --master yarn --deploy-mode client as default and removed
--conf spark.akka.frameSize=128.  Also removed spark.akka.frameSize reference from recommended Spark configuration settings in spark-batch-mode and spark-mlcontext-programming-guide docs.

Note although I removed spark.akka.frameSize from sparkDML.sh and recommended settings, I'm not sure if I should instead replace with --conf spark.rpc.message.maxSize=128 since it also means:
"Maximum message size (in MB) to allow in "control plane" communication; generally only applies to map output size information sent between executors and the driver. Increase this if you are running jobs with many thousands of map and reduce tasks and see messages about the RPC message size."

Applied similar changes to python performance test scripts.

It turns out that we don't need to specify the spark.akka.frameSize=128 or spark.rpc.message.maxSize=128. According to the documentation for Spark 1.6 , that is already the default size. Also, in the current spark master, the value defaults to 128.
I also discussed this in an offline conversation with @niketanpansare.
I think we should remove this parameters from all our scripts.

For the python scripts, we'll need to pass the newly introduced --deploy-mode parameter to other parts of the script.
Ping @krishnakalyan3.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2158/

Thank you @nakul02 for reviewing and clarifying!  I've incorporated the comments where I similarly modified sparkDML.sh in src/main/resources/scripts and also updated all algorithms docs.  For the python performance scripts, I reverted the --deploy-mode parameter which can be addressed in a separate PR.

I will start working on deploy-mode for perf test suit.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2159/

I opened a separate JIRA (https://issues.apache.org/jira/browse/SYSTEMML-1945) which can be used for the performance test scripts.


UI: Backup doesn't show up using rancher-proxy, but works with node port

We've reproduced the issue @kc004 experienced

Fixed by https://github.com/rancher/longhorn-ui/pull/117


Update patient.rb

Description
Jira Ticket: SARAALERT-###
Corrects a bug where the patients age is not set or updated when users are created or updated through the API.
(Feature) Demo/Screenshots

(Bugfix) How to Replicate
Create a user using the FHIR API. The age variable will be blank.
(Bugfix) Solution.
Add to the from_fhir in patient.rb
age: ((Time.zone.now - patient&.birthDate.to_time) / 1.year.seconds).floor,
Important Changes
Please list important files (meaning substantial or integral to the PR) along with a list of the general changes that should be highlighted for reviewers.
patients.rb
Add age calculation to from_fhir method.
Testing
This fix was tested on the following browsers (submitter must check all those that apply):

[X ] Chrome
[ X] Firefox
[ ] Safari
[ ] IE11
[X] FHIR JAVA API

Please describe the tests needed to verify your changes. Provide instructions for reproducing these tests. List any relevant details for your test configuration.
After patching the age should be calculated correctly when users are added or their dob updated via the FHIR api.

@Sepiidae I didn't have permissions to add commits to your fork on GitHub so I continued the work in #401


Add indexed_db_observers sample

Now that values and transactions are supported in IDB Observers, I'm comfortable releasing this sample. I may iterate a bit later to show off transaction support.
@jeffposnick for this update.

👍 from my perspective.
CC: @petele @PaulKinlan so that this is on their radar, too.

@dmurph I've tweaked your PR at https://github.com/GoogleChrome/samples/pull/474. WDYT?

That seems fine.

Closing with https://github.com/GoogleChrome/samples/pull/475 and https://github.com/GoogleChrome/samples/pull/479


Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Summary by Sourcery
Refactor the Flask integration's render_graphql_ide method to use explicit response parameters, improving type safety and removing an unnecessary type: ignore comment. Document the change in a new RELEASE.md file.
Enhancements:

Refactor the render_graphql_ide method in the Flask integration to use an explicit response code and content type, removing the need for a type: ignore comment.

Documentation:

Add a RELEASE.md file to document the patch release, highlighting the stricter typing in the Flask integration.

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release tweaks the Flask integration's render_graphql_ide method to be stricter typed internally, making type checkers every so slightly happier.
Here's the tweet text:
🆕 Release (next) is out! Thanks to @NucleonJohn for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)


Build import API using ANET objects

Please review and merge PR-3492 before this PR
Closes #3487
Checklist

[x] Refactor mixins.
[x] Fix tests according to the new ANET objects.

I see the unit tests have been fixed here.
Good reason to merge.
I am not sure what the aim of refactor mixins are. What I find a bit suspicious are statements like if self.__tablename__ == "people":. That makes me wonder, is this something what we can move to an object representing people.

It is about refactoring report logic as in this commit https://github.com/NCI-Agency/anet/pull/3495/commits/a792d999952ee76cbe54e23d9076bde47fb3047f . However i need to make refactoring whole business logic functions again as we talked so i am going to merge this PR and will continue new story.


Add requirements for self-hosted GitLab instances

🚨 Proposed changes
A couple of updates to the documentation after setting up the plugin with my own self-hosted GitLab instance.
⚙ Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x ] Documentation Update (if none of the other choices apply)
[ ] Refactor

This is an OR not a if


Enable/disable session based authetication

As oneview-redfish-toolkit user, I have a new parameter at redfish.conf file named "authentication_mode", whose possible values are conf (default value) or session. If set to "conf", hpOneView client session should be instantiated using credentials from redfish.conf as it is currently done. Otherwise, a new hpOneView client session should be created for each received request using a token at "x-auth-token" header for each request. In this mode, the request should fail if the token is invalid. System Root should be accessible without authentication.

Depends on 165 implemented

#165 is ready!


Adding CC 82: The Ex-kitten-sion (Image Replacement Chrome Ext)

Deploy Preview: https://deploy-preview-731--codingtrain.netlify.app/challenges/82-image-chrome-extension

~I could not think of a good thumbnail image, so used the Rainbow wiki page for now. (also it is has a bad aspect ratio)~

added ls archive, waiting on rc for 83 and 84 (i'll add these next)

added thumbnail as suggested by @kfahn22 with some changes.

This is great!


Add ETW (Event Tracing for Windows) bypass

Adds:

ETW class in the SharpSploit.Evasion namespace
PatchEtw function

Disable ETW by patching the EtwEventWrite function in ntdll.dll.
Code has been kindly stolen and adapted from Adam Chester (https://blog.xpnsec.com/hiding-your-dotnet-etw/) and Mythic (https://github.com/its-a-feature/Mythic).
Tested on Windows 10 1909 and .NET Framework 4.8

Thanks for the suggestion @rasta-mouse!
I've added a line of code to restore the original memory permissions like in your AMSI patch.


require('nvim-tree').open is nil if sync_with_nvim_tree = true

open fn in require('nvim-tree.api').tree.open

Same issue

Same here


Cockpit icon tooltip gets in the way of button click

PV Ticket https://www.pivotaltracker.com/story/show/143207021
BZ https://bugzilla.redhat.com/show_bug.cgi?id=1439319

@miq-bot add_label euwe/yes
@miq-bot add_label bug
@miq-bot add_label services

This seems more like a "hack"...not really a fix.  Perhaps I'm wrong.  Thoughts?

I took a look and I had a few thoughts on why I went this route.  These buttons no longer exist in our master branch and the bigger reason why I trimmed up the text is because of how the list clips overflow on the y axis.  The tooltips get very much cut off if left as is.

Ok, that makes sense to me.  Thanks!

Sorry @simaishi merged by force of habit.  BIG apologies.

@chalettu Which PR removed the buttons in the 'master' branch?


add blackhole_detection probe

Also pulled other updates for existing probes from the aos-cli.

blackhole probe is not possible at this time - closing PR.


chore(main): release 4.6.4

:robot: I have created a release beep boop
4.6.4 (2024-10-16)
Bug Fixes

cicd: one more try (f992e33)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v4.6.4
:sunflower:


JS Error

Nice extension.  However, I seem to have found a bug.
Page HTML:
object(Automattic\WooCommerce\HttpClient\Request)#5 (5) {
  ["url":"Automattic\WooCommerce\HttpClient\Request":private]=>
  string(298) "http://<IP_ADDRESS>/wp4.6.1/wp-json/wc/v1/customers?oauth_consumer_key=ck_e…s%3D&oauth_signature_method=HMAC-SHA256&oauth_timestamp=1473879163"
  ["method":"Automattic\WooCommerce\HttpClient\Request":private]=>
  string(3) "GET"
  ["parameters":"Automattic\WooCommerce\HttpClient\Request":private]=>
  array(5) {
    ["oauth_consumer_key"]=>
    string(43) "ck_e87133476f2b8087d0add97a9bf87fe2f8beca9f"
    ["oauth_nonce"]=>
    string(40) "136380691fea250a77a4679c3757a50ae6621482"
    ["oauth_signature"]=>
    string(44) "uuvySyOUNmhQ/WpJpvgRmSHm9NmF+IXZc/XdyUYOnds="
    ["oauth_signature_method"]=>
    string(11) "HMAC-SHA256"
    ["oauth_timestamp"]=>
    int(1473879163)
  }
  ["headers":"Automattic\WooCommerce\HttpClient\Request":private]=>
  array(3) {
    ["Accept"]=>
    string(16) "application/json"
    ["Content-Type"]=>
    string(16) "application/json"
    ["User-Agent"]=>
    string(32) "WooCommerce API Client-PHP/1.1.1"
  }
  ["body":"Automattic\WooCommerce\HttpClient\Request":private]=>
  string(0) ""
}

peg$SyntaxError {message: "Expected "\"" or [a-zA-Z0-9_\x7F-ÿ] but "\\" found.", expected: Array[2], found: "\", location: Object, name: "SyntaxError"}
expected
:
Array[2]
found
:
"\"
location
:
Object
message
:
"Expected "\"" or [a-zA-Z0-9_\x7F-ÿ] but "\\" found."
name
:
"SyntaxError"
stack
:
(...)
get stack
:
stack()
set stack
:
stack()
__proto__
:
Error
constructor
:
peg$SyntaxError(message, expected, found, location)
__proto__
:
Object

Let me know if you need anymore info.

Thanks you so much for the report and relivent info! I see the problem (it has to do with namespaces in object properties). I'll get a fix out ASAP

I just published a new version 1.3.0. I believe it should fix the issue you are seeing (it fixed it for me locally). Let me know if you are still having trouble!
-Phil


Remove support for ocfl_layout.json

The ocfl_layout.json was removed from 1.0 because it was unclear and can easily be added back later. See https://github.com/OCFL/spec/pull/481

Closing, ocfl_layout.json was NOTE removed from 1.0 but keys we changed to be extension and description per https://ocfl.io/1.0/spec/#root-structure.
Fixed in https://github.com/zimeon/ocfl-py/commit/ffeafe6d4c3c2838aeadb6db737f9a5790e4dd05


Grammatical corrections

 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.:x: MC01DA sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@MC01DA : Thanks for your contribution! The author, @DCtheGeek, has been notified to review your proposed change.

@chbain : Thanks for your contribution! The author, @DCtheGeek, has been notified to review your proposed change.

@MC01DA Thank you for the contribution. At this time, I don't feel that many of the changes are necessary. I will take the feedback you have provided into account and review the article for grammatical issues with our existing tooling. Thank you!
@MicrosoftDocs/azure-cxp-triage #please-close


undoing format changes

Continuing from https://github.com/sqlcollaborative/dbatools/pull/2547
I did match the current format of the files, this commit fixes that.

merci beaucoup!


trivy: 0.42.1 -> 0.43.0

Diff: https://github.com/aquasecurity/trivy/compare/v0.42.1...v0.43.0
Changelog: https://github.com/aquasecurity/trivy/releases/tag/v0.43.0
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 241347 run on x86_64-linux 1

1 package built:

trivy


slurm: deprecation of --shared

From Ben Liu:
slurmProcessorScheduled.py:292
    if self.exclusive == True:
        ex_or_sh = "--exclusive"
    else:
        ex_or_sh = "--share"

uses a deprecated (and no longer existing) flag.   The correct flag is “--exclusive=user”

Shawn is updating this logic and testing with a private 7.0.4 install on both alastor (new slurm) an genie (old slurm)

The use of shared has been updated and will be merged.


Xiaomi tablet support?

The component does not detect that the Xiaomi 7" mipad tablet is a mobile device. Can support for Xiaomi mobile devices be added to this library?

Haven't you read the note about how to add additional devices while you created the issue?
It's Mobile-Detect where to add such requests.


Display images preceded by exclamation Fixes #387

I have made the necessary changes in the code to resolve the bug. The image link is now displayed even when immediately preceded by an exclamation.

Automated message from Dropbox CLA bot
@sup95, it looks like you've already signed the Dropbox CLA. Thanks!

@sup95 check out https://github.com/zulip/zulip/pull/390, which is an attempt I made at fixing this several months ago.  As you may notice, there's some discussion about some changes that need to be made to my code to make it work correctly with our frontend markdown processor (see http://zulip.readthedocs.io/en/latest/markdown.html for details).

Hi @sup95 - how's this going? Do you need us to help you make any further decisions?

Also, we've added https://zulip.readthedocs.io/en/latest/git-guide.html which has a lot of help in case you are having trouble rebasing!

I am so sorry I have been a little unavailable. I got distracted by another bug and have submitted a PR to that. I will have a look at the markdown document and try to make the required changes or ask for help if I am stuck.

Closing due to inactivity. Thanks for working on this @sup95!


docs: improve OpenAI notebook

Improving the copy on the openAi notebook
AB#1912948

/azp run

Codecov Report

Merging #1596 (8f6a2f9) into master (e019756) will decrease coverage by 62.34%.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Support for cvss v4

Brings cvss v4 support for v5 branch. Also fixes an npm severity inconsistency bug by updating to vdb 5.8.1

@cerrussell, once https://github.com/AppThreat/vulnerability-db/pull/196 is merged, we can add CVSS v4 support to the depscan v6 master.


Updated DVL models to include current profiling field (for plugin)

Insignificant commit for the most part--I added a waterTrackBins field to the DVL models in support of the current profiling incorporation into the WHOI DSL plugin.  If you use the latest nps_dev branch from our copy of the WHOI DSL repos (ds_msgs and ds_sim) and run any of the DVL demos (e.g., roslaunch nps_uw_sensors whoi_teledyne_whn.launch) you'll get the current profile messages (rostopic echo dvl/dvl_current).
You'll still get the messages without merging this pull request, but the plugin will default to 1 bin (I think I put 10 in all of the models).

The code looks fine.  It would be good if we could develop an introductory demo for the WHOI folks to understand the functionality.  I started a wiki here: DVL Water Tracking.
Could you make sure that it make sense and add some verbosity before merging?
In particular, do the velocities in the verification test make sense?  I'm not sure the coordinate frame of the reported velocities.  It would be good to explicitly define the reference frame.  Does each beam have a tf frame to reference?
Also, a bit off topic, but where in the Dvl message is it reported if the DVL has bottom lock?  Good to note that in the wiki.

@bsb808 I'll update the wiki shortly--it looks good, but I'll add a launch file for water tracking/current profiling that doesn't require editing.  I'll take a look at the verification.  I haven't done a ton of verification testing (I wanted to push the commit before the feature freeze), but the implementation is pretty simple.  The plugin already computes a "beam velocity" for each beam and each beam has a unit vector for its orientation, so beam-relative current is just the velocity inverse times the unit vector.
Bottom lock is indicated in the Dvl message by the track mode field.  There is no beam-specific indication other than the range field (I think beams without bottom contact will indicate -1, but don't quote me on that).

@bsb808  I did a more thorough validation, and everything looks correct as far as I can tell.  I also added a "instrument-specific reporting" capability to the velocity profile code (the only affect to this repository is a new "currentProfileCoordMode" tag in all of the models).  I also verified that it was working correctly.  I updated the demo/tutorial as well.


Failure only on Jenkins runs.

Please rebase here @clarax ?
Thanks.

@clarax, there is a conflict, please rebase.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 37s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 14s
master passed

+1 :green_heart:
compile
4m 50s
master passed

+1 :green_heart:
checkstyle
1m 41s
master passed

+1 :green_heart:
spotbugs
3m 35s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 28s
the patch passed

+1 :green_heart:
compile
4m 59s
the patch passed

+1 :green_heart:
javac
4m 59s
the patch passed

+1 :green_heart:
checkstyle
1m 45s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
20m 45s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
3m  1s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 24s
The patch does not generate ASF License warnings.

62m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3724

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux fd64c5ccbfc9 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 72a88468a8

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
96 (vs. ulimit of 30000)

modules
C: hbase-balancer hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 33s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 29s
master passed

+1 :green_heart:
compile
1m 36s
master passed

+1 :green_heart:
shadedjars
8m 18s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  1s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 32s
the patch passed

+1 :green_heart:
compile
1m 36s
the patch passed

+1 :green_heart:
javac
1m 36s
the patch passed

+1 :green_heart:
shadedjars
8m 11s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
6m 57s
hbase-balancer in the patch passed.

+1 :green_heart:
unit
137m 28s
hbase-server in the patch passed.

178m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3724

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux de532094d84e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 72a88468a8

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/testReport/

Max. process+thread count
3677 (vs. ulimit of 30000)

modules
C: hbase-balancer hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 33s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 20s
master passed

+1 :green_heart:
compile
1m 22s
master passed

+1 :green_heart:
shadedjars
9m  9s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 40s
the patch passed

+1 :green_heart:
compile
1m 25s
the patch passed

+1 :green_heart:
javac
1m 25s
the patch passed

+1 :green_heart:
shadedjars
9m 23s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  3s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
10m  9s
hbase-balancer in the patch passed.

+1 :green_heart:
unit
218m  9s
hbase-server in the patch passed.

264m 38s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3724

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ca31ac574394 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 72a88468a8

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/testReport/

Max. process+thread count
2511 (vs. ulimit of 30000)

modules
C: hbase-balancer hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3724/12/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Test failures is unrelated known issue.


Error when running on a PCB with a bitmap image

When a PCB layout contains a bitmap image (KiCad v7's new "Add bitmap image" option), the HTML BOM generation process fails with an error.  I've attached a screenshot of the stack trace dialog that pops up when doing this.

For now, the workaround is to delete any bitmaps from the PCB prior to generating the HTML BOM.
A better solution would simply be if the HTML BOM plugin could ignore these elements when doing its thing, as they're primarily for decoration/reference when doing layout.
(This is with Interactive HTML BOM v2.5.0 and KiCad v7.0.0.)

Same experience here.
v2.5.0, kicad v7.0.0, ubuntu 20

It's a KiCad bug. See https://gitlab.com/kicad/code/kicad/-/merge_requests/1525
Workaround is possible but not sure it's worth it if 7.0.1 will have the fix.

7.0.1 is out with the fix.


Remove an unnecessary space after a line break

A trivial translatable string fix in the source English file.

Codecov Report

Merging #2914 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2914   +/-   ##
======================================
  Coverage    3.62%   3.62%
======================================
  Files         246     246
  Lines       12209   12209
  Branches     1077    1077
======================================
  Hits          443     443
  Misses      11732   11732
  Partials       34      34

Continue to review full report at Codecov.

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


Windows Installation Links 404

All of the Windows installation links on the getting started page lead to "Page Not Found":

https://docs.commonfate.io/granted/releases.commonfate.io/granted/v0.0.9/granted_0.0.9_windows_x86_64.zip
https://docs.commonfate.io/granted/releases.commonfate.io/granted/v0.0.9/granted_0.0.9_windows_arm64.zip
https://docs.commonfate.io/granted/releases.commonfate.io/granted/v0.0.9/granted_0.0.9_windows_i386.zip

Hey @eigBabcock, thanks very much for raising this issue (and congratulations for being the very first community contributor to the repo 😁). I've fixed the download links and updated the documentation to reflect this.
For your info the latest download links can be found here:
https://releases.commonfate.io/granted/v0.1.1/granted_0.1.1_windows_x86_64.zip
https://releases.commonfate.io/granted/v0.1.1/granted_0.1.1_windows_arm64.zip
https://releases.commonfate.io/granted/v0.1.1/granted_0.1.1_windows_i386.zip
Additionally there are some instructions here on how to verify the integrity and authenticity of the binaries.
If you have any further issues on Windows don't hesitate to raise an issue and we'll improve the project ASAP to deal with them. The core team maintaining the project predominantly uses unix-based machines, and while we did do enough Windows testing to feel comfortable stating that Windows is supported it is less battle-tested than Linux and MacOS.


[BSO] Master mining cape perk

🚀 Feature Proposal
My idea for a master mining cape perk would be to make it so you can rarely get dwarven crates or ores from mining, a rate scaling on length of trip rather than different chances per ore or anything like that.
Probably a rate like 1/1,500 per 1 minute, that'd scale up to 1/50 for a 30 minute trip. If you're doing 32 30 minute trips per day (16 hour days), 1/50 means you'll expect a drop every 25 hours, so a bit over a day and a half of actively mining. Bars look to be 1b each in ge atm, so factoring in 35% chance to fail smelting and 25 hours per bar, this would add about 26m per hour in value to mining. Obviously numbers and rates are flexible if Magna thinks this is unbalanced or whatever, but I think it'd be pretty well balanced.
I'm not sure if crates or ores would be preferable, crates would lead to ores/time being rarer obviously but there's been talk of adding outfit to the crates and I'm not sure you wanna increase the supply of outfit by very much. I think I'd prefer just ores.

I think leaving crates as a goldemar  only drop would be good, but dwarven ore from the cape honestly sounds fair. 120 mining is a big req and only ~5 people have it currently.
High level req? check
Incentive for users to mine? check
you've got my support on this

bump

#bso-vote for bso content ideas/suggestions


Integrate Skyboxes as a background to a web page

Hello:)
Is it possible to integrate a skybox into MR.js?
The skybox will appear in the background once the website is opened. The skybox would load/appear in the same direction as the webpage is presented to the user (top to down). The skybox can be toggled on/off. Also, the skybox could be shown as a half dome vertically or horizontally. Users can add multiple skyboxes and scroll through them as they progress on the web page.
If skybox is a feature of a tool for creating an XR website, users should be able to import the skybox correctly.
For now, these are all the thoughts I have

@lobau assigning to you since you're already working on it. it'll be cool to integrate this directly into the library 🥳


Possible fix for T8420 camera

Specifically, the HomeKit Alarm System created for the camera not responding to changes in the Eufy app

Does floodlight provide Alarm on EufyApp ?

I need some time to verify the change.

I need some time to verify the change.

That's fine!  This is my first foray into git PRs and branches, and my first foray into Javascript, node and HomeBridge plugin development so I may well have got many things wrong! 😊  Just let me know if you have any queries. 👍🏼

For info, the T8420 does support the ability to arm, disarm, schedule and geo-fence and you can enable any of motion detection, push notifications and siren for the home or away modes:

So having it as an Alarm System is HomeKit is really helpful.  One thing I have spotted as well is that when the plugin starts, there is a log message along the lines of "Device is station but type is 3 might imply errors".

For info, the T8420 does support the ability to arm, disarm, schedule and geo-fence and you can enable any of motion detection, push notifications and siren for the home or away modes:

So having it as an Alarm System is HomeKit is really helpful.  One thing I have spotted as well is that when the plugin starts, there is a log message along the lines of "Device is station but type is 3 might imply errors".

Did you have a look on my comment on your PR ?
This is normal behavior to have this log message. Camera act as a station but doesn't have all station capabilities. That's why you get the warning message.

So having it as an Alarm System is HomeKit is really helpful.  One thing I have spotted as well is that when the plugin starts, there is a log message along the lines of "Device is station but type is 3 might imply errors".

This is normal behavior to have this log message. Camera act as a station but doesn't have all station capabilities. That's why you get the warning message.

That's fine.

Btw, did you have a look on my comment on your PR ?
#326 (review)

Apologies - I can't find it?

@fullphat I'll take a look at this PR when I have pushed the changes to snapshot to the beta.

Could you not point to a specific model while naming this function?

It would rather inverse have isAlarmStation than isFloodlight and avoid creating the object
Escape it like this
if (!isAlarmStation()){ this.log.debug('does not provide alarm capabilities') return; }

isAlarmStation

Could you not point to a specific model while naming this function?

It would rather inverse have isAlarmStation than isFloodlight and avoid creating the object
Escape it like this
if (!isAlarmStation()){ this.log.debug('does not provide alarm capabilities') return; }

Yes, I can do - is isAlarmStation() already defined somewhere?  If not, how do I test if something is an alarm station?
Don't forget that the floodlight camera does provide an alarm function; it's more that it's its own station.

isAlarmStation

Could you not point to a specific model while naming this function?

It would rather inverse have isAlarmStation than isFloodlight and avoid creating the object
Escape it like this
if (!isAlarmStation()){ this.log.debug('does not provide alarm capabilities') return; }

Yes, I can do - is isAlarmStation() already defined somewhere?  If not, how do I test if something is an alarm station?
Don't forget that the floodlight camera does provide an alarm function; it's more that it's its own station.

@fullphat Has this been fixed by some of @kare sake fixes?

@fullphat Has this been fixed by some of @karesake fixes?

I think it might have been but I haven't been able to check it properly yet.  Give me a couple of days to confirm?


Adjustments for FB API v3.0

New FB Apps have to use API v3.0 - I just changed the API version in all related URL paths and it worked for me.

I added Breakdowns as well to separate the data by age, gender, religion, country. We have ad accounts with multiple countries, want to import them to GA into one dataset per country.

I added another change which should not be an issue for most people.


OIDC: set the signing algorithms

I let #1976 open for UI updates.

 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.Jérôme LELEU seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.


chore: Removing all unecessary docker containers

Gol is to have only api in this docker-compose file to not overload the api container

This pull request addresses issue #1 .

Only problem i'm facing is get back xdebug to work separately from api


Pass metafields through BuyerIdentity or allow more than 5 to be included in the toml

Please list the related package(s)
checkout-ui-extensions@2024-07
If this related to specific APIs or components, please list them here
shopify.extension.toml useAppMetafields useCustomer
Is your feature request related to a problem? Please describe.
I unexpectedly ran into an issue today where I added some additional metafields to my extension toml but still only had access to 5 on render. It looks like there's an unstated hard limit of 5 metafields that can be returned by useAppMetafields. I couldn't find any mention of this anywhere in the docs and I didn't get any warning in my CLI.
Describe the changes you are looking for
It would be great for the limit on metafields in the toml to be removed or set to a much higher number.
Even better would be if the Customer object returned from useCustomer would more closely map to what's available in the StorefrontAPI including customer metafields.
Describe alternatives you’ve considered
I thought about querying the Storefront API for customer but I can't do that without an accessToken. This would work fine if an access token was passed through useCustomer.

Closed because #558 captures the issue. Should be fixed!


Added Threat Note

Threat_Note is an awesome Threat Intelligence Platform written by @brianwarehime.
Great list/resource BTW. We needed this!

Thanks for your addition @sroberts. Your projects and blog have been nice sources for this repo too :smile:

@hslatman Too kind of you. Glad people are finding some value.


Fix bug when no buffers are present in implicit subtree

Today @ErixenCruz and I noticed a bug in implicit tiling where a subtree with no buffers/bufferViews results in an undefined that breaks ImplicitSubtree.js
This was easy to fix, I just needed to add a couple defaultValue() calls.
@lilleyse could you review? i'll work on getting you a subtree file to test with

Thanks for the pull request @ptrgags!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@lilleyse updated!

:+1:


[IGNITE-6002] Make log message more pretty when instance name is null

When instance name is null, log message containing "null" is shown like as follows.
[09-08-2017 14:49:38][INFO ][grid-timeout-worker-#15%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
    ^-- Node [id=de0743ec, name=null, uptime=00:01:00:007]

The ticket is resolved. Closing PR


Revert "Template x carousel block"

Reverts adobecom/express#1295

reverting to unblock the release that's already delayed


fix(examples): carbon accounting backend grpc pre-gyp install

Describe the bug
https://github.com/hyperledger/cactus/pull/903/checks?check_run_id=2495237052#step:5:147
To Reproduce
It appears to be random flake so keep trying until you see it or just visit the logs link above.
Expected behavior
No flaky tests/CI suite.
Logs/Stack traces
https://github.com/hyperledger/cactus/pull/903/checks?check_run_id=2495237052#step:5:147
Cloud provider or hardware configuration:
GHA
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
main @ today
Hyperledger Cactus Plugins/Connectors Used
Xdai, Fabric
Additional context
Potential solution here: https://github.com/nodejs/node-gyp/issues/1599
and here https://github.com/grpc/grpc-node/issues/1183
cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @petermetz @arnab-roy

The logs for this run have expired and are no longer available.

Haven't seen it for a while and the logs have expired so we'll just re-open this as later if it resurfaces.


Add: Hue solo lightstrip (5 mtr.)

Device information

Hue solo lightstrip (5 mtr.)
https://www.philips-hue.com/de-de/p/lightstrips-hue-solo-lightstrip/8720169326699
Home Assistant Device information

Automatically generated definition (LCL009)
von Signify Netherlands B.V.
Verbunden über Zigbee2MQTT Bridge
Firmware: 1.122.2
Checklist

[ x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[ x] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[ x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

Awesome. Everything looks fine.


Feature request: add smooth chunk fade-in loading animation

First of all: thanks for keeping this awesome mod updated. That's what a lot of people was asking :)
My feature request is: add a smooth fade-in effect, to allow chunks to smoothly load fading in like it happens on Bedrock Edition. Subtle, but a great enhancement for the game. This, coupled with a good shaderpack, would allow us to have an awesome experience!

When I heard Bedrock had a chunk fade-in I thought someone might ask, I’ll take a look at adding it into the next update.

 At the end it all makes a lot of difference tho. Something similar already happens on java when using sodium + lithium on fabric but:

it's not a fade in, it's simply a lot more faster and with a more delicate fog around the borders
it's fabric only, so big rip to shaders

Unfortunately this won’t be in the next update (which is today), but I wanted to say that I still plan on implementing it. I did have a brief look at implementing it but it seems rendering a “render chunk” with a different opacity is slightly beyond my knowledge of Minecraft’s rendering system at the moment, so will take some more work.

Patiently waiting here! That's something Java deserves and you would be the first one bringing it to the game 😆

with a different opacity is slightly beyond my knowledge of Minecraft’s rendering system

Well, I have zero idea on the functions that you can use to manipulate that kind of stuff, guess there isn't just a setOpacity lol

Nope, the current chunk animations are simple enough because there’s a translate method that you can use to move a "MatrixStack", however the MatrixStack doesn’t apply the colours so I’ll need to work out how to do that properly to the entire render section of the chunk. I have some ideas of things I could try, but it’s probably smarter to learn a bit more about how the rendering works first.

I just thought of how Bedrock kinda has this. This would be a awesome feature. +1 for me!

This may help: https://github.com/Johni0702/fade-in-chunks, but it is for Fabric, not Forge.

Thanks for pointing this out. Porting this to Forge (under Chunk Animator) is certainly something I can do.

Any news so far? :)

Unfortunately not. As ever I've been busy with other projects and... well... life. I did make some progress recently in that I switched the current coremod transformers to use Mixin (on the 1.16.5-mixin branch) - which will make it much easier to implement this.
Furthermore, I feel my other modding-related projects have given me a better understanding of rendering than when I last looked at this. I won't set any deadlines for this since I don't want to disappoint, but I should have some more time in early July to take another look at this.


Right click context menu doesn't show all the options.

Description
This is the normal menu show by the windows' explorer

This is the menu shown by this application:

I'm using the latest version 2.0.13 on windows 10. The TortoiseGit menu is very important for me because I use it very often.
Steps To Reproduce

Open the application
click on an empty area of the explorer
You will notice that an item (folder or file) is always selected which is incorrect.

Expected behavior
I expect to see all the menu entries when I click in an empty area of the explorer.
Files Version
v2.0.13
Windows Version
Windows 10
Relevant Assets
No response

Thanks for the report. Could you check if you just need to scroll down the menu to see the items?

OMG! yes, I needed to scroll the menu down, sorry. However, I think that the user experience is not good maybe it will be great if you adapt the menu size accordingly.

You're right, there's currently a bug preventing us from doing that but that's definitely the plan.


Build errors

To build this repo it uses an old rust-toolchain https://github.com/axiom-crypto/axiom-eth/blob/main/rust-toolchain#L1 'nightly-2022-10-28', so when you run cargo build it gives errors for some dependencies since it's using rustc 1.66 but the dependencies require 1.70.
so the following worked for me (instead of running cargo update). just choosing dependencies like an older version of clap that didn't require 1.70 shown here https://crates.io/crates/clap/versions
cargo update -p<EMAIL_ADDRESS>--precise 1.0.2
cargo update -p<EMAIL_ADDRESS>--precise 4.3.24
cargo update -p<EMAIL_ADDRESS>--precise 0.5.0
cargo build --verbose
cargo run --bin header_chain --release -- --help

same error

Same issue was encountered here. Confirm that the solution proposed by @ltfschoen + @norbubb works

This should be fixed in https://github.com/axiom-crypto/axiom-eth/commit/014a2d059e48f8f4ad83a7650f1d0bf9a69a056a


Seg fault in Multithread using Affine transformer with backend cv2

With n_worker > 0 in the data loader (Pytorch).
+
With backend='cv2' in the Affine transformer (working fine with skimage)
iaa.Sometimes(0.70, iaa.Affine(
    scale=(0.90, 1.30), translate_percent={"x": (-0.1, 0.1), "y": (-0.1, 0.1)},
    rotate=(-45,45), order=[3], mode="constant", backend='skimage'
)),

This cause seg fault in the worker of the data loader.

RuntimeError: DataLoader worker (pid(s) 4457) exited unexpectedly

In my case, I augment the img with their bounding boxes.
img_trf, lbl_trf = self.image_transfroms.augment(image=img, bounding_boxes=lbl)

imgaug==0.3.0
opencv-python-headless==<IP_ADDRESS>
Pillow==6.2.1
scikit-image==0.16.2

What OS are you using and what is the output of python -c 'import os; import platform; print(os.name, platform.uname())'; python --version?
Are Affine and Sometimes the only augmenters you are using?
Unfortunately OpenCV is quite finicky and will quickly segfault or hang indefinitely due to minor problems. You can try calling cv2.setNumThreads(0) once at the start of the script or at the start of each worker. Sometimes that helps.

python -c 'import os; import platform; print(os.name, platform.uname())'; python --version

posix uname_result(system='Linux', node='gpu-instance', release='4.9.0-8-amd64', version='#1 SMP Debian 4.9.144-3.1 (2019-02-19)', machine='x86_64', processor='')
Python 3.7.3

(Working on a GCP VM)

Are Affine and Sometimes the only augmenters you are using?

No, here I was using a lot of augmenters. But the Seg Fault only happens when adding the Affine augmenter.
I have now tested with only Affine and Sometimes, and the Seg Fault is always there in Multithread with only the both of them.

Hi,
I found a workaround for this bug. If you import imgaug inside of the dataset get_item call in pytorch, the problem goes away. Like this:
`
def getitem(self, item):
assert 0 <= item < self.num_images
image_path = self.image_paths[item]
image = Image.open(image_path)
    # resize
    image = image.resize(size=self.output_size, resample=Image.BILINEAR)

    # convert to numpy array
    image = np.array(image)

    # optionally augment
    if self.augment:
        # BELOW IS THE IMPORTANT PART - ONLY IMPORT AT RUNTIME
        # INSIDE THE WORKER THREAD
        import imgaug.augmenters as iaa
        from imgaug.augmentables import Keypoint, KeypointsOnImage

        imgaug_transform = iaa.Affine(
                scale={"x": (0.6, 1.4), "y": (0.6, 1.4)},
                translate_percent={"x": (-0.2, 0.2), "y": (-0.2, 0.2)},
                rotate=(-100, 100),
                shear=(-8, 8),
                backend='cv2',
        )

        image = imgaug_transform(image=np.array(image))

    # convert image to tensor and coordinates to tensor
    return torch.from_numpy(image)

`

Update: I can also confirm that cv2.setNumThreads(0) also works as @Manuscrit mentioned above :)


FSM support

Finite state machine (like in aiogram)
In-memory based states storage.
States - the very important thing, that help you with logistic. But you may to know, that you will lost all states after restarting. (in Read.me more)

See #288 for clues.
If we were to accept a FSM implementation, it would need to adhere at least in part to the model outlined there; think package github.com/tucnak/telebot/v3/fsm with the principle implementation of the Interaction interface.


Warnings are always suppressed, can't find a setting

I was using ammonite for some training and noticed that the compiler warnings are all suppressed. While I would typically agree that warnings in a REPL are often more noise than value, during the training we were specifically trying to call out unchecked warnings and other compiler hints so I dropped back to the plain old REPL for those. It would be great to have a setting to re-enable warnings for demo purposes or other correctness checking.

This was fixed in 0.5.3
@ // Enabling warnings (which are disabled by default)

@ List(1) match { case _: List[Double] => 2 }
res7: Int = 2

@ compiler.settings.nowarnings.value = false

@ List(1) match { case _: List[Double] => 2 }
warning: $fruitlessTypeTestWarningMessageBlahBlahBlah

@dickwall

I also see this regression on version 2.5.2


fix: return 404 error if no sync committee contribution is available

Motivation
Similar to https://github.com/ChainSafe/lodestar/pull/6648 we should be return a 404 error instead of 500 internal server error.
Description
Return 404 error if sync committee contribution is not available for slot / subnet / block root.
Note: This is not yet defined in the spec, see https://github.com/ethereum/beacon-APIs/pull/440

Keeping as draft until behavior is clarified in spec

Keeping as draft until behavior is clarified in spec

Spec PR has been merged

:tada: This PR is included in v1.22.0 :tada:


[Bug]: Failed to switch profile

Describe the bug
Hello, this is a very interesting plugin. Sadly, I have the same error over and over again : Failed to switch profile.
I'm on Windows.
How to Reproduce
01 I create a profile
02 save it
03 Try to load it in the same vault or in another vault
04 Failed
Expected behavior
No response
OS of your device
win 11
Obsidian Version
v1.5.4
Plugin Version
0.3
Additional context
Also, when appearance is turned on when saving the profile, nothing else will be created in the profile folder.
If appearance is turned off, the plugin will save all the other parameters minus appearance of course

I will look at it.

But I have another Issue that the profiles are not visible in the other vaults at all. See my other Issue.

This is related to #14

Does this version fix both issues mentioned here? https://github.com/4Source/settings-profiles-obsidian-plugin/issues/14#issuecomment-1937869689

Have you tried the new version https://github.com/4Source/settings-profiles-obsidian-plugin/issues/14#issuecomment-1938353868 alpha.2 in both vaults?

I have the same Issue. Occurs when the saving path has been changed (for example to C:\Obsidian Folders) before creating the profile. But I have another Issue that the profiles are not visible in the other vaults at all. See my other Issue.

Is this fixed with the alpha.2?

@Superelmanu Is this fixed with release 0.4.1


Test java/util/concurrent/LinkedTransferQueue/WhiteBox.java in OpenJDK9 cannot be excluded using exclude file option

Test java/util/concurrent/LinkedTransferQueue/WhiteBox.java in OpenJDK9 cannot be excluded using exclude file option both in our build story or locally.
Test java/util/concurrent/LinkedTransferQueue/WhiteBox.java has been excluded in ProblemList_openjdk9-openj9.txt, however it is not excluded in all openjdk9_j9_openjdktest_{arch}_{OS} test jobs.
To reproduce locally using openjdk9 exclude story:

Download or clone test base from https://github.com/AdoptOpenJDK/openjdk-jdk9
Download latest JDK9 from https://ci.adoptopenjdk.net/job/openjdk9_build_x86-64_linux/
Download jtreg from https://ci.adoptopenjdk.net/job/jtreg/lastSuccessfulBuild/artifact/jtreg-4.2.0-tip.tar.gz
Add java/util/concurrent/LinkedTransferQueue/WhiteBox.java		https://github.com/eclipse/openj9/issues/1434	generic-all in openjdk9-jdk9/jdk/tet/ProblemList.txt

Run the following jtreg command.
./jtreg/jtreg/bin/jtreg -verbose:all -jdk:/openjdk9binary/j2sdk-image/ -exclude:"/openjdk9/openjdk-jdk9/jdk/test/ProblemList.txt" /Users/sophiag/adoptjdktest/openjdk9/openjdk-jdk9/jdk/test/java/util/concurrent
./jtreg/jtreg/bin/jtreg -verbose:all -jdk:/openjdk9binary/j2sdk-image/ -exclude:"**/openjdk9/openjdk-jdk9/jdk/test/ProblemList.txt" /Users/sophiag/adoptjdktest/openjdk9/openjdk-jdk9/jdk/test:jdk_util
Test will not be excluded.
Note:

Running specified the testcase, it will be excluded:
./jtreg/jtreg/bin/jtreg -verbose:all -jdk:/openjdk9binary/j2sdk-image/ -exclude:"*/openjdk9/openjdk-jdk9/jdk/test/ProblemList.txt" /Users/sophiag/adoptjdktest/openjdk9/openjdk-jdk9/jdk/test/java/util/concurrent/LinkedTransferQueue/WhiteBox.java

If exclude another concurrent whitebox.java at the same time:
java/util/concurrent/ArrayBlockingQueue/WhiteBox.java	https://github.com/eclipse/openj9/issues/1434	generic-all
java/util/concurrent/LinkedTransferQueue/WhiteBox.java		https://github.com/eclipse/openj9/issues/1434	generic-all

Both test will be excluded, which looks like those tests case are not written dependently? Probably there are some other similar cases?

Based on some queries from @ben-walsh (thanks Ben!), we now know that the inability to properly exclude certain tests stems to this openjdk/jreg defect.
Response on queries: "The bug is that the content of the test description (the /* @test */) comment is identical for this test and some other tests. If you need a short term workaround, add some unique text, such as a @summary or @bug info into the test you are trying to exclude."
2 options:

wait for a fix, which was told is coming soon, but with no actual date
temporary workaround, add a step just after copying test material to edit the comment section of the tests in question prior to running the test

Sure, we can do that (option 3!), though are some of those tests actually passing?  If so, we should make a comment in the issue under which we exclude them.

Yes, those three are passing tests. Agree we need to put a comment in the exclude issue and also refer to https://bugs.openjdk.java.net/browse/CODETOOLS-7902067

Looks like the fix is in  https://urldefense.proofpoint.com/v2/url?u=http-3A__hg.openjdk.java.net_code-2Dtools_jtreg_rev_7265713552da&d=DwIBAg&c=jf_iaSHvJObTbx-siA1ZOg&r=0yESvVeO2xHyvCbHqew0S5OPRA6T6qWI6hcf_aOJlVw&m=pzcRLa2mVoYRl85DhAzGAgGYqRPNxiia06RZXF5zBKs&s=9xNpBUgC3xHjpXFe1wZydRPsjfqehkzL3L3Coz1iygc&e=
When the changes is in https://ci.adoptopenjdk.net/job/jtreg/ the problem should be fixed.

Can we check if this has been resolved, so we can reinclude tests and close the issue?

A couple of grinders https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/554/  - https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/559/ show this has been fixed. Tests with same name under different package | path could be excluded. Close this issue.
Leave excluded test as is. There is specific issue opened for its unexpected behavior.
Reinclude tests depend on the test


Request rest API with a Certificate

Hi Guys,
It's more a question than an issue, but like a face some difficulties to use certificate, i'd like to ask you how it's possible to use certificate to perform a rest request on a https server?
I'm working on the branch v0.1.0-waterline-v0.10 ?
May be you could just give me an example?
Regards

@rsilvestre Do you mean client-side certificates? If not those, what exactly do you mean? I you provide an example? Issuing a normal HTTPS request doesn't require any particular setup.

In the client side i have this config in the connections.js file :
/**
   * To contact API
   */
  listRest: {
    adapter: 'sails-rest',
    type: 'json',                   // expected response type (json | string | http)
    host: 'api.example.com',  // api host
    port: 443,                       // api port
    protocol: 'https',               // HTTP protocol (http | https)
    pathname: '/api/v1.1/public/',            // base api path
    resource: 'user',              // resource path to use (overrides model name)
    action: null,                   // action to use for the given resource ([resource]/run)
    query: function (config, collectionName, methodName, options) {

      var newOptions = {};

      if ( options.where.name ) {
        newOptions.name = options.where.name;
      }

      if ( options.limit ) {
        newOptions.itemsPerPage = options.limit;
      }

      // dont forget to pass on skip because this function is responsible for generating all the parameters
      newOptions.skip = options.skip;

      return newOptions;

    },
    headers: {
      'Accept-Language': 'fr'
    },
    methods: {                      // overrides default HTTP methods used for each CRUD action
      //create: 'post',
      find: 'get',
      //update: 'put',
      //destroy: 'del'
    }
  }

I'd like to add a certificate like that :
key: fs.readFileSync('./cert/private.key'),
cert: fs.readFileSync('./cert/certificate.crt'),

@rsilvestre I see.
I'm not sure superagent (the underlying HTTP client) supports that officially. Let me take a look, but feel free to dig around yourself.


Eating a pill made of nothing crashes the server

Grimbo#1604: Eating a pill made of nothing crashes the server (when debugging), I found this out by testing out smoke pills, using phosphorus, sugar, and potassium

This seems to be fixed, eating an empty pill pops up a message saying "the pill is empty!"


Unable to use Unions with Generics

Describe the Bug
Not sure if it is a bug or something non supported but when passing a union to a generic type strawberry is unable to initialize the schema.
The following example would work using a single strawberry type with Connection, but it fails when using an union
from typing import Generic, TypeVar, Union
import strawberry

T = TypeVar("T")

@strawberry.type
class Edge(Generic[T]):
    cursor: str
    node: T

@strawberry.type
class Connection(Generic[T]):
    edges: list["Edge[T]"]

@strawberry.type
class Entity1:
    id: int

@strawberry.type
class Entity2:
    id: int

Entities = Union[Entity1, Entity2]

@strawberry.type
class Query:
    @strawberry.field
    def entities(self) -> Connection[Entities]:
        return Connection(
            edges=[
                Edge(
                    cursor="1",
                    node=Entity1(id=1),
                ),
                Edge(
                    cursor="2",
                    node=Entity2(id=2),
                ),
            ],
        )

schema = strawberry.Schema(Query)
print(schema.execute_sync("{ entities { __typename } }"))

error
raise cls(f"{self.name} fields cannot be resolved. {error}") from error
TypeError: Query fields cannot be resolved.

System Information

Operating system:
Strawberry version (if applicable): 0.208.1

hi @farzeni this seems to due to the union not having a name 😊
To fix it you can change this
-Entities = Union[Entity1, Entity2]
+Entities = Annotated[Union[Entity1, Entity2], strawberry.union(name="Entities")]

I'll see if I can make it work without passing a name 😊

@farzeni just pushed a fix for this specific issue 😊
I'd still recommend you to give a name to the union, otherwise it would get automatically generate from the name of the types :)

Hi @patrick91,
Awesome, thanks so much for resolving the issue so quickly, really appreciate it! 😄
I'll stick to your advice to always name unions. Thanks for the tip!


Complete Foundation PTO

#Privacy of Information and Protection:
Your opinion is your personal information. Please do not include any information which identifies you or others in your response.
#Description:
Complete the Foundation PTO training.
99 SF Documentation\Course Material\Training Material Overview & Links to find info for specific course.
#Outcome:

[ ]
#Outcome:
[ ]
[ ]
[ ]

#To Complete this ticket:

[ ]
[ ]
[ ]

@lortrent Completed

@camyotte -Complete

@cegede - complete

@amoore-github - complete


Implement backward for fixed_batch_normalization

LGTM except the comment. But I would like @beam2d to check the implementation because he left this feature as TODO. Does this simple solution works as you imagined?

LGTM except the comment. But I would like @beam2d to check the implementation because he left this feature as TODO. Does this simple solution works as you imagined?

Can you implement backprop for mean and var? I think it is confusing to silently cut the backward computation without any errors.

I fixed. Please review this.

LGTM :+1:


chore: Update development tools configs and packages

The development tools config and packages have been updated.

Thank you! Unfortunately the tests failed. Looks like Node.js version needs to be updated too. 🥲

@uhyo Thank you, I fixed it in https://github.com/uhyo/eslint-plugin-tree-shakable/pull/2/commits/0219b1a8a29f40f36b9b4427b4b8e573cd89d120 !


bug/ Update error in Assets

Describe the bug
Users were able to edit and update items in the Assets sections while leaving input fields blank.
To Reproduce
Steps to reproduce the behavior:

Go to Assets
Create an Asset
Edit the asset
Leave the input fields blank
Press Update

Expected behavior
When leaving input fields blank, users should be alerted with an error message and not be allowed to update the asset item.
Observed behavior
Users are allowed to update items with missing fields.
Screenshots
Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: Chrome 127.0.6533.120

Additional context

approved

Approved


Update libregexp and implement d flag

See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/hasIndices

Tests fail on macos because luajit fails to build. Possibly related to https://github.com/leafo/gh-actions-lua/issues/46, in particular the part about the hardcoded macos version.


slippage updates - slippage custom input doesn't let you delete the value when it has a single digit

@phoebemirman  Slippage looks good. Just two small things:

can you make the hand tool appear when hovering the entire clickable area
Can you change the hover state on the default number to this


Whisper align bollywood

Hi, ultrasinger ist verry good
I have a problem when i convert a bollywood song i have the hindi language i have test
With whisper align but i dont create it

Hi, did you try an hindi model from Huggingface?

Yes i have try two hindi model the problem ist the normal translation make in hindi language but i will in romanized language but ist not translation

https://github.com/rakuri255/UltraSinger/issues/181


Enable log capture if stdout is not a terminal (issue #229)

This appears to enable capturing of log messages with "postgrest >> log"

Thank you, much appreciated!
(Note for github: fixes #229)


Remove beacon root contract from state tests

🗒 Description
Removes the beacon root contract and its execution outcome from the state tests by separating the fork pre-alloc by blockchain and non-blockchain tests.
Also converts the beacon root contract tests to blockchain tests.
🔗 Related Issues
#446
✅ Checklist

[x] All: Set appropriate labels for the changes.
[x] All: Considered squashing commits to improve commit history.
[ ] All: Added an entry to CHANGELOG.md.
[x] All: Considered updating the online docs in the ./docs/ directory.
[x] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[x] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[x] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

let me check

it still puts beacon contract in blockchain tests that are automatically filled for cancun

it still puts beacon contract in blockchain tests that are automatically filled for cancun (those that do unrelated stuff to beacon root)

For the blockchain tests it should be fine right? It was the state tests where the issue was.

so a state test in bc form will still have it inserted into pre?


Search in REQUESTED FILES (URLS) panel

It would be very handy to allow search filter in REQUESTED FILES (URLS) tab in the exported html report.
For example, the interest might be in specific request, while there are thousands of URLs listed, it would be hard to search for it manually.

Thanks for suggesting that out. This should be addressed in #117. It's now at the top of the to-do list (finally).


Apple visionOS build support

This pull request aims to support building TDLib for the Apple xrOS/visionOS platform.
As it is essentially similar to modern Apple platforms, I reckon there be no other changes, except to update scripts to fit the platform.
Scripts are adapted to allow for building for the said platform right now but is yet to be tested, hence it is a draft PR.
Compiling requires Xcode 15 beta and CMake 3.27.
Do also note that this is based on #2517's OpenSSL script, and the CMake script also has legacy architectures removed for iOS right now.
UPDATE: Good news, built a quick sample project, and was able to see TDLib's verbose logs streaming into the console, when running on visionOS simulator, Xcode 15.0 beta 5 (15A5209g)!

Thank you, @vincentneo!
After your pull request https://github.com/tdlib/td/pull/2517 has been merged the example already uses OpenSSL 3 for building, hence the first commit isn't needed anymore.

The OS has been renamed to visionOS. Could you use this name for it instead of xrOS?

Could you rebase the commits on the latest master instead of merging?

Have not done this before, will read up on it

The OS has been renamed to visionOS. Could you use this name for it instead of xrOS?

Well, Xcode 15.2 (not beta) still reports visionOS sdks as xros and xrsimulator
I have tested that all seems to build fine as before, before marking this pr as ready

I didn't mean that we need to rename Xcode flags. The comment was about local variables such as "XRSIMULATOR"/"XROS"/"xrOS".

Btw, did the rebase work? I can't tell.

Old commits are still there, therefore the branch as the whole cannot be rebased due to conflicts. Likely, you need to force push the new rebased branch instead of merging it with master.

@levlam may I verify with you that the rebase is correct now? if so I will work on renaming xr

Yes, it looks correct now.
Also, why the applied patch was renamed from ../Python-Apple-support.patch to ../xros-support.patch in the first commit?

Have renamed to visionOS, and it should still build fine

Thank you, @vincentneo!
I merged these 3 commits, fixed rename of xrOS to visionOS in iOS.cmake, and supported visionOS throughout TDLib.


Colon definitions should have access to constants

This currently does not work:
$FF47 constant rGBP

: set-bg-palette
  ( x ) rGBP c! ;

Fixed in a3a3b2e545aaa25e06956c5df6377e879f6ef482


Search failed error when searching from Find Anything

Hi Netdiscoers,
I'm running netdisco-docker and since upgrading to 2.70 (and now 2.70.2) we're getting a Search failed error fairly regularly when searching for devices from the "Find Anything" search function. This was working fine previously, we were most recently on 2.67.
I don't see any obvious errors but I don't really know where to look, tbh. If someone could point me in the right direction that would be much appreciated!
Expected Behavior
Search finds device and displays the Details page.
Current Behavior
The following error is displayed:
Search failed! Please contact your site administrator (server error).
Often searching again will work without error. Alternately, sometimes switching tabs to Neighbors or Modules and then back to Details will work.
Steps to Reproduce (for bugs)
As above.

Search for a device that is in the DB from Find Anything (either in the menu bar or from the front page)
Search fails (server error)

Just to make sure, did you execute netdisco-deploy to upgrade the database schema after the upgrade of the containers? There is a new table in 2.70.

Thanks for your quick response, @rc9000.
I didn't run netdisco-deploy as I'm using the DB image from docker-hub and I thought that the DB schema updated automatically when the image starts. I saw the following logs on first startup after pulling the new images:
netdisco-db-entrypoint: bringing schema up-to-date
netdisco-db-entrypoint: marking schema as up-to-date

Is this correct, or is there something else I need to do?
Thanks!

I wonder if there is any clue in /home/netdisco/logs/netdisco-web.log ?

Indeed it does seem like a DB schema issue. Seeing the following error repeatedly in /home/netdisco/logs/netdisco-web.log:
DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently unversioned. Please call upgrade on your schema to sync the DB. at /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
Error while loading /home/netdisco/perl5/bin/netdisco-web-fg: The setting session_cookie_key must be defined at /home/netdisco/perl5/lib/perl5/Dancer/Session/Cookie.pm line 38.
Compilation failed in require at /home/netdisco/perl5/bin/netdisco-web-fg line 59.
BEGIN failed--compilation aborted at /home/netdisco/perl5/bin/netdisco-web-fg line 59.

And this when the Search Failed error happens:
[1601] 2023-11-24 09:46:11 error request to GET /ajax/content/device/details crashed: Warning caught during route execution: DBIx::Class::ResultSet::_resolved_attrs(): Useless use of distinct on a grouped resultset ('distinct' is ignored when a 'group_by' is present) at /home/netdisco/perl5/lib/perl5/App/Netdisco/DB/ResultSet/Device.pm line 187

second error possibly relates to https://github.com/netdisco/netdisco/commit/82ae76e7b7ac09738f05b5b6ace14d2a5217886f
could remove the distinct after we added the group_by
(although need to test if I can reproduce this and it's not a side effect of the first error which is possibly an offline database or other database operational issue)

@noziwatele yes you're of course right, the netdisco variant does the schema upgrade by itself. I've tried now with an old 2.6xx I had lying around, same error after a docker-compose pull. See attached for full log.
upgrade.txt

@rc9000 let me know how I can help. I don't really understand the error (FATAL after server starts OK?)

I suspect the DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently unversioned. is just temporary in the upgrade process: postgres restarts, this crashes the web process, but then it comes back fine after the restart.
The DBIx::Class::ResultSet::_resolved_attrs(): Useless use of distinctappears after searching, when clicking on the name of a result device and opening eg. /device?tab=details&q=<IP_ADDRESS>. However the page still opens.
I'm still at a loss how to reproduce a sporadic "search failed", didn't happen for me so far. But I have a practically empty db with only two pseudo devices.

@noziwatele maybe you can describe what exactly you search for, there are various code paths there:

ip address or hostname
do you select a name from the autocompletion or do you just hit enters
is this a fqdn or not, and do you have domain_suffixes configured?

Have released Netdisco 2.070003 with fix, should be on container repos within an hour.

Upgraded to 2.070003 and the issue appears to be resolved! Many thanks for the quick fix!!
Here's more detail on what I was searching for when the issue occurred - in case this information is useful in the future:

Was initially searching for hostname, but the error also occurred when I searched for an IP address of a device that was in the DB. But there was no issue when I searched for an IP or MAC address of a Node.
I typed the hostname (or partial hostname) and hit enter, which autofilled the FQDN in the search box, then hit enter again and that's when it failed. Usually if I followed the same steps a second time the search would succeed. When it failed on searching for an IP the IP address was autocompleted to the FQDN of the device in the DB, so then I hit enter again and it was the same as for the hostname search.
FQDN. Yes we do have domain_suffix configured. Just one suffix that matches what we use on all our devices.

Thanks again!


[store] Application search bar text deletion

Application / API search bar text get deleted when applications are switched or
another application is clicked.
Before switching application

Typed text not available after switching applications.

Fixed in 3.x.x


[WIP] Updating VS to use PTVSD 5.*

WIP because I'm working on fixing one of the tests. Other than that, it's ready for code review.

There's an issue with bottle and flask web projects. Create new project, install packages as needed and press F5, the browser starts and attempts to load the page but it never ends. By comparison, legacy debugger works fine, also start without debugging is fine.

Stop debugging command doesn't work. I tried django app and regular python console app project. You'll see this after a few seconds, which is not supposed to happen:

If you click stop now, it will stop but you'll have leftover Python processes running.

Stop debugging command doesn't work. I tried django app and regular python console app project. You'll see this after a few seconds, which is not supposed to happen:

Bug in PTVSD. Issue created here.


Specify CMG IDs and group membership conditions in Google Spreadsheet

The current CMGs tab is a good start but I'd recommend creating a new worksheet with a name we'll recognize (like "groups") that is very minimal for now. For example, it could be just these headings:

materialid of each CMG
name – just for human-readability
SMILES substructure pattern.

I've created a new spreadsheet called CMG parameters in the same shared Drive folder. The program looks this up by title, so the title should not change.

The tab called new CMGs contains the parameters for the next batch of compound groups that I'd like to process, as a way of testing this method. Michel, could you take a moment to check that those parameters are correct? I copied them from the main CMG structural parsing spreadsheet.
After these are done, we can update the last_updated field and move those spreadsheet rows to the all CMGs tab. Eventually when it's just a matter of updating existing CMGs, the program will run through all of them and check dates. For now we're just managing it ourselves.

I love it. Those look good. Fred did a pass at those and they generally worked, though formatting issues kept me from importing them. I'm a little dubious about the PFOA salts, so feel free to leave that out until you're ready for some error handling.
Also, the CMG ids are being depreciated, so lets use the new 7 digit material ID from column B of this document instead of the CMGnnnnn. https://docs.google.com/spreadsheets/d/1EjZ06F6asJ7jWlKt2i_dl5QJJ8JODcKV6PBMMsJ3rlQ/edit#gid=0


Italic text doesn't fit into Textfitted element

Looks like the extra slant or overhang from an element having font-style: italic is not accounted for in the font size calculations.
Regular text working properly:

Italic text (p cuts off):

This is most likely a browser implementation / font face thing. This behavior is consistent across browsers and is due to the browser wanting to respect the (potentially wacky) spacing of the font being used. This is, of course, as far as I can tell. It's also not just particularly italic fonts, just a higher tendency with them. Here are some relevant links: http://jsfiddle.net/Novado/enhuc4jv/1/
https://stackoverflow.com/questions/26296434/html-italic-letters-protrude-from-their-container-and-may-be-cut-by-the-next-co
http://www.positioniseverything.net/explorer/italicbug-ie.html


Adding POST for ASV and all the db entity changes for container VNF deployment

This PR implements:

All the code needed to create an appliance software version (entity changes, services, unit tests, rest API). see https://github.com/opensecuritycontroller/community/blob/master/designs/containers/vnf-deployment/vnf-deployment.md#appliance-software-version

All the DB entity changes related to DS and DAIS for K8s, see https://github.com/opensecuritycontroller/community/blob/master/designs/containers/vnf-deployment/vnf-deployment.md#osc-entities

Makes the ASV integer field using Integer rather than int. Those fields were already optional but when not provided we had an NPE. This fixes that problem.

Note: Remaining changes to create a k8s DS will come later in a different PR

The latest commit on this PR adds the remaining code to allow for a creation of a K8s deployment spec. See https://github.com/opensecuritycontroller/community/blob/master/designs/containers/vnf-deployment/vnf-deployment.md#deployment-spec


SSL error: unknown error

Hi everyone,
I am trying to clone my repo from my own dev server and I am getting an error:
SSL error: unknown error

I was using login and password of my gitea user.
Gitea v1.20.4
System: Fedora 38 (Linux 6.5.6-200.fc38.x86_64)

The ssl certificate is Let's encrypt.

I use other git client on another my pc (windows) and it's working fine.

@exactly-one-kas may know something about.

Can you try the artifacts of the qt6 build?
https://github.com/Murmele/Gittyup/pull/429
There I updated the openssl version

I must say I've yet to hit the same problem myself, but compiling on Fedora 38 the tests pass without any issue on that qt6 branch, were as I hit trouble running the master branch (very similar error to #546 I might add). I strongly suspect that these warnings I get on the master branch, but not on the qt6 branch, have something to do with that
/usr/bin/ld: warning: libssl.so.3, needed by /usr/lib64/libQt5Network.so.5.15.13, may conflict with libssl.so.1.1
/usr/bin/ld: warning: libcrypto.so.3, needed by /usr/lib64/libQt5Network.so.5.15.13, may conflict with libcrypto.so.1.1

I'm not sure how it's all connected, but I suspect this is an openssl 1.1 vs. 3.0 clash


Documenting how to perform programmatic validation

Hello! The README states that the validator supports:

programmatic validation (so it can easily be used by Python code).

but myself and a couple of colleagues have struggled to figure out how to do this.
Would it be possible to add some examples to the documentation?

+1. This came up a few times at BioHackathon last week, as people are excited about the validator and keen to incorporate it into their work! Documentation would really help.


Need a way to log

You cannot write to a Logger when using a daemon. It works with a client though. This is probably because the daemon gem redirects output to /dev/null if there is no logfile: https://github.com/ghazel/daemons/blob/master/lib/daemons/daemonize.rb#L241-261.
Is there a way to add logfile support when in daemon mode?

In 1.1.2, I added the ability to pass options into the TweetStream::Daemon so that you can set additional options when daemonizing.  By default, the Daemon initializes with { :multiple => true } but you can set it to anything you'd like (including logging):
TweetStream::Daemon.new('tracker', :multiple => true, :log_output => true, :log_dir => '/var/log/')


Multiple inheritance should resolve to the method whose signature is a subtype of the others

This is the analyzer equivalent of front end/kernel bug #30547.  I'm mostly filing the bug so I can link to it from test cases--it may not be worth trying to fix in analyzer, since eventually analyzer is going to be based on the new front end.
The spec says:

If multiple superinterfaces of an interface define a member with the same name m, then at most one member is inherited. That member (if it exists) is the one whose type is a subtype of all the others. If there is no such member, then:

A static warning is given.
...

Which means that following code should be ok, because the version of f inherited by C should be the one from I2, which is safe to pass a String to:
abstract class I1 {
  void f(int i);
}
abstract class I2 {
  void f(Object o);
}
abstract class C implements I1, I2 {}
class D extends C {
  void f(Object o) {}
}
void g(C c) {
  c.f('hi');
}
main() {
  g(new D());
}

But in strong mode, analyzer issues this warning at the site of g's call to c.f: The argument type 'String' can't be assigned to the parameter type 'int'.

@scheglov I've verified that this is implemented correctly in InheritanceManager2, so I'm guessing that we just need to finish replacing InheritanceManager.

https://dart-review.googlesource.com/c/sdk/+/78182 will fix this.

This was fixed with using InheritanceManager3.


EncodingWarning(s) when running robot code if PYTHONWARNDEFAULTENCODING is set.

If environment variable PYTHONWARNDEFAULTENCODING is set (and at least when running on MacOS), _get_python_system_encoding()  from robot/utils/encodingsniffer.py in triggers following warning;
/Users/rasjani/src/duunit/energy-meter/venv/lib/python3.11/site-packages/robot/utils/encodingsniffer.py:59: EncodingWarning: UTF-8 Mode affects locale.getpreferredencoding(). Consider locale.getencoding() instead.
  return locale.getpreferredencoding(False)

In this example, all i did was import Browser in the  python repl.

Interesting, I didn't know about this option or PEP 597 earlier. It makes sense to require encoding to be specified with open(), but I don't fully understand why this error occurs with locale.getpreferredencoding(False). Anyway, it seems that it could be easily avoided by using locale.getencoding() instead. It's only available with Python 3.11, but that's also the version where this particular warning starts appearing.
Although the fix would be easy, I don't think it's a good idea to do it in RF 7.0 anymore:

Although I tested the change on Linux and on Windows and it worked fine, changes like this are always risky. It should be done so that it's available in preview releases, not just before the final release.
The warning doesn't occur by default.
We use open() without encoding in multiple places in our code base. If we want to support PYTHONWARNDEFAULTENCODING properly, we need to go through them all and set explicit encoding. Depending on the case the encoding can be UTF-8 or locale. The was added as part of PEP 597 in Python 3.10, but we can use None with earlier versions. All this is too much work for RF 7.0 at this point.

The problem is real, so let's fix it properly in RF 7.1.