Validate on load?

Hi,
I have used this package to validate my form, however, I noticed it only validates when something is typed/checked. Is it possible to trigger validation when page loads?

Method A:
Use initial modifier on the v-validate directive: v-validate.initial="..."
Method B:
Validate manually on mounted() method of your Component:
this.$validateAll().catch(() => {});

.initial works fine, thanks


📃 [ENHANCEMENT] - Want to Update Computer Graphics Documentation #1443

#1443
📃 [ENHANCEMENT] - Want to Update Computer Graphics Documentation #1443
Closes #
Type of change

[ ] Adding a new Resource
[ ] Adding a new Category
[y ] Documentation enhancement or fixes
[ ] Website enhancement or fixes

Checklist:

[ y] I read carefully CONTRIBUTING.md
[y ] I have performed a self-review of my own code
[ y] I have commented my code, particularly in hard-to-understand areas
[y ] I have made corresponding changes to the documentation

Screenshots (if appropriate):
Please add screenshots to help explain your changes.
Additional

Resolve the merge conflict

hey @jfmartinz please check this pr Now


incorrect status bar fixes [CPP-927]

addresses RTK issue (conflicting variable in QML and js)
unsure if INS is fixed (might need replay file to verify)

Frontend and Release Workflow Started here

Do we understand why this broke?

Do we understand why this broke? Or did it ever work?
@silverjam

think my PR https://github.com/swift-nav/swift-toolbox/pull/972 created this side effect.
variable naming conflicted with pyside and qml.
set_rtk in python class  and rtk in qml property which this changed the scope of variable assignments 😢 annoying bug thats super easy to overlook.
it might follow that we should consider naming qml properties uniquely to distinguish them from pyside variables in the future to prevent these types of weird behaviour


MSID: 88299 Version: 1 DOI: 2<IP_ADDRESS>4010

"msas": "Biochemistry and Chemical Biology"
"msid": "88299"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4010"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."
"Reviewed Preprint posted": "2023-05-31"
"Sent for peer review": "2023-04-17"
"Posted to bioRxiv": "2023-03-30" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4010v2")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=88299)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/88299/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: https://github.com/elifesciences/enhanced-preprints-data/pull/92
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4010)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/88299/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/88299)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/88299

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/88299

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/88299/v1/88299-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/88299)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

@acollings are the details added to the description correct for this one?
88299 / 10.1101/2<IP_ADDRESS>4010 vs. 88289 / 10.1101/2<IP_ADDRESS>6092

No problem - thanks Andy!


OMPL Planner error.

Hi,
Thank you for providing such an excellent repository. I’ve encountered an issue with the OMPL planner, and I’m hoping you might be able to assist. Below is the error message I’m receiving:
[simExtOMPL:warning]   OMPL: /home/marc/Documents/ompl-1.4.2-Source/src/ompl/base/src/Planner.cpp:247: SBL: Skipping invalid start state (invalid state)
[simExtOMPL:error]   OMPL: /home/marc/Documents/ompl-1.4.2-Source/src/ompl/geometric/planners/sbl/src/SBL.cpp:101: SBL: Motion planning start tree could not be initialized!

I have followed the installation instructions for RL-bench as outlined in several repositories, but the issue persists. If you have any insights or suggestions on how to resolve this error, your guidance would be greatly appreciated. One note, I am using Ubuntu 20.04 and its respective CoppeliaSim version.

@RocktimJyotiDas, is this error from this repository? Seems like this from your custom ompl source.

Hi Mohit,
Thank you for your prompt response. es, I got the same error with this repo. When I try to locate Planner.cpp, here’s the output I receive:
rockt@rockt-G3-3579:~$ locate Planner.cpp

/home/rockt/genima/ompl-1.6.0/build/Release/src/ompl/CMakeFiles/ompl.dir/base/src/Planner.cpp.o
/home/rockt/genima/ompl-1.6.0/build/Release/src/ompl/CMakeFiles/ompl.dir/control/planners/ltl/src/LTLPlanner.cpp.o
/home/rockt/genima/ompl-1.6.0/src/ompl/base/src/Planner.cpp
/home/rockt/genima/ompl-1.6.0/src/ompl/control/planners/ltl/src/LTLPlanner.cpp

I’m confused about where this error is originating from, as the path /home/marc doesn’t exist on my system. I came across a similar issue on the Coppelia Robotics forum, but there doesn’t seem to be a solution posted.
Any insights on how to resolve this would be greatly appreciated.

Hmm, sorry, I am not sure what is happening here. Maybe try with different versions of CoppeliaSim?

Closing due to inactivity.


How to compile devel on mac OSX 10.10.4 Yosemite

Maybe this will help those of you trying to compile the cython on Yosemite:
Step one:  brew install gcc (mine installed gcc-5.2)
Also, since Yosemite moved the headers for vecLib, you need to extend the extra_compile_args in setup.py by adding: '-I/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/Headers'
Then when building:
export CC=gcc-5; export CXX=gcc-5; python setup.py build_ext --inplace
And this gave a whole bunch of warnings but no errors!  ;-)

Thanks @mathDR thats really useful! We will try and sort out our slightly odd cblas dependencies out soon so hopefully such hacks won't be necessary!
Alan

Such hacks are no longer required :)


Update version of args dependency

I cannot keep using lakos in my project any more, since it depends on an old version of args, which my other dependencies conflict with.

I plan to update the dependencies in January.

Done!


Application Integration: UM

[x] Write download and build script (figure out dependencies, compile)
[x] Execute the workload with and without GEOPM on the command line
[x] Create AppConfig python object which captures the steps to run an application
[x] Determine how to obtain the figure of merit and parse after run
[x] Verify optimal configuration by confirming figure of merit and settings used with application expert.
[ ] Insert barriers in front of all collective calls for build of special binary that can be selected with AppConfig as was done for nekbone
[ ] Insert epoch call in outer loop
[x] Add a run script for each experiment and execute them on two nodes and run at least two trials
[x] Add a configuration for 8 - 12 nodes and collect data from those runs (night-time runs preferred sbatch --begin=20:00 for post 8 PM PDT start time), if GPU workload, one node only required.

Does not have long running collective MPI calls when properly configured, so there is not a clear opportunity for providing a benefit with barrier approach.


Error messages when path matching fails should be changed

From<EMAIL_ADDRESS>on September 22, 2011 10:06:22
Now we have error messages like "JSON element doesn't match X, was Y". It should be "JSON path doesn't match X, was Y".
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=104

From<EMAIL_ADDRESS>on September 24, 2011 02:00:19
Status: Fixed


Add advaith-unnikrishnan

resolve #447

@advaith-unnikrishnan looks like there is a merge conflict. Could you resolve this? If you need any help please let us know 🚀

@schmelto  I have resolved the conflict


LayoutCache generates only when @Layouts(all = true)

When I try to use annotation different to @Layouts(all = true), LayoutCache file not generates(

@antoxa2584x can you show the annotation you are using when the cache does not get generated.

@FabianTerhorst I tried to use @Layouts(all = true, exlude = {R.id.somelayout1,R.id.somelayout2}) and @Layouts(ids = R.id.somelayout1,R.id.somelayout2})

@antoxa2584x is there any note, warning or error in the gradle messenger window?

0.0.2-alpha21 has fixed some errors.


Fixing a panic on v2 networking

Make sure the NeworkConfig are never nil in the NetworkConfigs map. 🐅
/cc @joshwget
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Looks like this is potentially failing due to a CI issue. LGTM if the tests pass locally!

ping @mikedougherty 😇

Tested locally and on a completely new server, tests are green. merging 👼


Keeping order of insertion

It would be very useful to have an option to keep the order of insertion of the keys. This option would be diferent from sort_keysor item_sort_keys where the user needs to specify how the sorting will be done.
I think this has been also requested for simplejson, but it was discarded because it wouldn't be valid JSON as JSON is unordered.
Would such a feature be desirable in simpleion?

Similar to JSON objects, Ion structs are unordered, so introducing the notion of maintaining insertion order is surprising--why not use a list?  It would be interesting to understand your use case better....
It's something we'd need to consider wrt consistency across all Ion parsers, and would I suspect require a change to the specification.

I'm developing some scripts that append / modify data in ION documents. These changes are code-reviewed and it's mandatory to focus strictly on the data because changes in formatting (like changing the order of the fields) make the diff impossible to read.
I understand that this might be against the ION specification, so I might need to look for an alternative solution (a fork maybe?).

Thank you for providing some additional info.  Forking sounds a bit heavy-handed here, plus it incurs additional maintenance costs.  Sounds like if you had a dumps() alternative that allowed you to apply your field-ordering conventions prior to diffing, you'd be all set;  I suspect there are approaches to making that happen that don't involve forking the library.

I've implemented the item_sort_key functionality (pull request waiting to be reviewed here: https://github.com/amzn/ion-python/pull/84) . This works for the 'conventions' part, but that's only a small part of the problem.
I'd like to be able to perform changes over existing ION files without modifying the original order of the fields; this not only involves modifying the dumps, as it requires adding another kind of IonPyDict that preserves the order in which the documents are read. It should be completely up to the client to use this dictionary or the original one.

We were ok this feature as long as it's optional and the client has to opt in to use it. We'd be happy to review a PR for it


feat(tagbar): formatting for use with vim tagbar.

features:
parsing variable types and function/method signatures.
identifying getters, setters, operators, and abstract methods.
tagging public/private fields and methods.
better line number matching.
fixes:
tab deliminated at the end of the string, which would make tagbar crash
without enabling line numbers.
various dart lint suggestions.
based on gotags.
tagbar for vim.

output for tags.dart
!_TAG_FILE_FORMAT       2       /extended format; --format=1 will not append ;" to lines/
!_TAG_FILE_SORTED       1       /0=unsorted, 1=sorted, 2=foldcase/
==      tmp.dart        /bool operator ==(Object other);/;"     o       access:public   line:41 class:Function  signature:(Object other)        type:bool
Ctags   tags.dart       /Ctags(this.options);/;"        C       line:9  class:Ctags     signature:(this.options)
Ctags   tags.dart       /class Ctags {/;"       c       access:public   line:9
Function        tmp.dart        /abstract class Function {/;"   c       access:public   line:9
_parseArgs      tags.dart       /String _parseArgs(String input) {/;"   m       access:private  line:42 class:Ctags     signature:(String input)        type:String
_parseFunctionReturnType        tags.dart       /String _parseFunctionReturnType(String input) {/;"     m       access:private  line:49 class:Ctags     signature:(String input)        type:String
_parseMethodReturnType  tags.dart       /String _parseMethodReturnType(String input) {/;"       m       access:private  line:54 class:Ctags     signature:(String input)        type:String
_parseVarType   tags.dart       /String _parseVarType(String input) {/;"        m       access:private  line:19 class:Ctags     signature:(String input)        type:String
addFileSystemEntity     tags.dart       /Future<Iterable<Iterable<String>>> addFileSystemEntity(String name) {/;"       m       access:public   line:95 class:Ctags     signature:(String name) type:Future<Iterable<Iterable<String>>>
apply   tmp.dart        /external static apply(Function function, List positionalArguments, [Map<Symbol, dynamic> namedArguments]);/;"  M       access:public   line:14 class:Function  signature:(Function function, List positionalArguments, [Map<Symbol, dynamic> namedArguments])  type:external
constructor     tags.dart       /RegExp constructor = RegExp(r'^[^]+?($|{|;)');/;"      i       access:public   line:14 class:Ctags     type:RegExp
generate        tags.dart       /void generate() {/;"   m       access:public   line:64 class:Ctags     signature:()    type:void
hashCode        tmp.dart        /int get hashCode;/;"   g       access:public   line:38 class:Function  signature:()    type:int
klass   tags.dart       /RegExp klass = RegExp(r'^[^]+?($|{)');/;"      i       access:public   line:13 class:Ctags     type:RegExp
main    tags.dart       /^;"    f       line:242        signature:([List<String> args]) type:void
method  tags.dart       /RegExp method = RegExp(r'^[^]+?($|{|;|\=>)');/;"       i       access:public   line:15 class:Ctags     type:RegExp
options tags.dart       /ArgResults options;/;" i       access:public   line:10 class:Ctags     type:ArgResults
parseFile       tags.dart       /Iterable<String> parseFile(File file) {/;"     m       access:public   line:118        class:Ctags     signature:(File file)   type:Iterable<String>

I haven't used dart in a bit. The change looks good. Is it ready to merge?

Thanks for the PR!

I haven't used dart in a bit. The change looks good. Is it ready to merge?

just pushed a fix for capturing the method arguments that I discovered today.  I haven't used it in large projects yet, but so far it's been great.  any repo you could recommend to test it on?

My only dart repos are for such an old version of dart, they aren't useful for testing I think. If it works on itself, that's good enough to merge :) Happy to merge fixes as you find them.

My only dart repos are for such an old version of dart, they aren't useful for testing I think. If it works on itself, that's good enough to merge :) Happy to merge fixes as you find them.

great!  I know Tagbar users will appreciate it.


python3Packages.psutil: 5.7.3 -> 5.8.0

Motivation for this change
Update to latest upstream release 5.8.0
Changelog: https://github.com/giampaolo/psutil/blob/master/HISTORY.rst#580
Things done

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

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

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

This should be targeted at staging branch as this triggers a massive rebuild (5000+)

Thanks, @prusnak.


Messages are being printed to the stdout

In this code segment, we can see some messages are being printed to the stdout.
https://github.com/huggingface/datasets/blob/7e60bb509b595e8edc60a87f32b2bacfc065d607/src/datasets/builder.py#L545-L554
According to the comment, it is done intentionally, but I don't really understand why don't we log it with a higher level or print it directly to the stderr.
In my opinion, this kind of messages should never printed to the stdout. At least some configuration/flag should make it possible to provide in order to explicitly prevent the package to contaminate the stdout.

This is expected to show this message to the user via stdout.
This way the users see it directly and can cancel the downloading if they want to.
Could you elaborate why it would be better to have it in stderr instead of stdout ?

@lhoestq, sorry for the late reply
I completely understand why you decided to output a message that is always shown. The only problem is that the message is printed to the stdout. For example, if the user runs python run_glue.py > log_file, it will redirect stdout to the file named  log_file, and the message will not be shown to the user.
Instead, we should print this message to stderr.  Even in the case of python run_glue.py > log_file only stdout is being redirected and so the message is always shown.

We now log these messages to stderr (the built-in logging module's default behavior).


Parse posted URLs for action

So this probably isn't the right forum to ask - but hopefully there are some elegant solutions that people can discuss!
Previously I captured URL's mentioned in chat to pull DNS information for digestion but that stopped working after this most recent release.
For example - I would grab the url and run it through some basic regex to clean it up/remove the http, www, etc:
domain = (msg.match[1].replace /https?:\/\/|www\./g, "")
Later using $domain in the url: http://api.statdns.com/google.com/ANY to collect the DNS data needed.
After this last update, I noticed that slack provides the URLs as either:
<http://www.google.com|www.google.com> or just
<http://www.google.com> depending on how they were entered.
Do people generally remove the brackets and split the string on the | character if it exists?  Or is there a better method all together?

Did this change again?  As of this week I am now getting different results:
    domain = msg.match[1]
    msg.send "`#{domain}`"```

Now returns:
```google.com http://google.com```
when passing it just google.com

@beardpapa: It's possible #133 might have had an effect, but the tests of this code didn't change significantly. What's the exact version of hubot-slack you're running?

Sorry, I wasn't keeping my dependency list up to date :|
Updated hubot-slack last week and it returned just the URL as expected.
Closing the issue :D


libspdm_gen_x509_csr() wrap the code with crypto support algorithm

https://github.com/DMTF/libspdm/blob/2756b67e0fcdee9abf8de109092255c83e9256ca/os_stub/cryptlib_mbedtls/pk/x509.c#L1981C1-L1981C40
Hi,
I wonder if we should rearrange the code and wrap it with corresponding crypto support options?
For example,
#if LIBSPDM_RSA_SSA_SUPPORT
case LIBSPDM_CRYPTO_NID_RSASSA2048:
case LIBSPDM_CRYPTO_NID_RSASSA3072:
case LIBSPDM_CRYPTO_NID_RSASSA4096:
#endif
#if LIBSPDM_RSA_PSS_SUPPORT
case LIBSPDM_CRYPTO_NID_RSAPSS2048:
case LIBSPDM_CRYPTO_NID_RSAPSS3072:
case LIBSPDM_CRYPTO_NID_RSAPSS4096:
#endif
Thanks!

@rw8896 Sure. Feel free to submit a pull request.


(ASC-1552) Add health check tests before running system tests

This PR adds an experimental test of running health check tests
in repo https://github.com/rcbops/rpc-openstack-healthcheck.
The health check tests in the above repo will be executed
right after RPC-O deployment without modification anything to ensure
that the deployment is in good status before entering system tests.
Issue: ASC-1552

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.

recheck bionic_no_artifacts_swift_deploy
recheck xenial_no_artifacts_swift_deploy

recheck_bionic_no_artifacts_swift_deploy
recheck_xenial_no_artifacts_swift_deploy

recheck_bionic_no_artifacts_swift_deploy
recheck_xenial_no_artifacts_swift_deploy

recheck_bionic_no_artifacts_swift_deploy
recheck_xenial_no_artifacts_swift_deploy

recheck_bionic_no_artifacts_swift_deploy
recheck_xenial_no_artifacts_swift_deploy

recheck_all

recheck_all

Please refrain from rechecking - the failures here are legitimate and need to be resolved. Constant rechecks is just wasting CI resources.

@odyssey4me yes, that's absolutely correct. I think I am kinda abuse the CI resources by rechecking it again and again. I'll get the logs and open a ticket for these failures, I have seen the failure of ping: not found is very consistent in the utility container

RI-670 PR has been merged, recheck the jobs now.
recheck_bionic_no_artifacts_swift_deploy

recheck_all

recheck_bionic_no_artifacts_swift_deploy
recheck_xenial_no_artifacts_swift_deploy

Until https://github.com/rcbops/rpc-openstack/pull/3509 merges, the syntax/lint tests will fail.

recheck_container_ansible-lint_tox-test
recheck_container_ansible-syntax_tox-test
recheck_bionic_no_artifacts_swift_deploy
recheck_xenial_no_artifacts_swift_deploy

recheck_container_releasenotes_tox-test


Alloy memory utilization peak by +several GBs for few minutes in "node_exporter/collector.(*filesystemCollector).GetStats"

What's wrong?
Hello,
I see a huge memory utilization (+ few GB) of Alloy service randomly in my environment. Sometimes it "kill" server with lower amount of RAM (~4-8GB).
I see this pattern in container_memory_rss:

acording to pyroscope the "issue" is in github.com/prometheus/node_exporter/collector.(*filesystemCollector).GetStats

I do not see
Steps to reproduce
run alloy as systemd service with prometheus.exporter.unix  component.
System information
CentOS 9 Stream with Upstream linux 6.9.y,
Software version
Grafana Alloy 1.3
Configuration
No response
Logs
n/a

The node_filesystem metrics were not collected during the problematic period. Could the mount point have stalled?
I see a bug in node_exporter:  https://github.com/prometheus/node_exporter/pull/3063
Could it be related?

I was able to find a configuration which helps (or workaround?) the memory peaks utilization
I moved the filesystem collector out from others and scraping the metrics less often (15s->60s)
prometheus.exporter.unix "node_exporter_system_15s" {
  set_collectors = [
    "btrfs",
    "conntrack",
    "cpu",
    "diskstats",
    "loadavg",
    "meminfo",
    "netclass",
    "netdev",
    "nfs",
    "pressure",
    "processes",
    "stat",
    "vmstat",
  ]
  include_exporter_metrics = false
  disk {
    device_include = "^((h|s|v|xv)d[a-z]+|nvme\\d+n\\d+)$"
  }
  netclass {
    ignored_devices = "^(cali\\S+|tap\\S+)$"
  }
  netdev {
    device_include = "^(lo|eth\\d+|en\\S+|bond\\d+(|\\.\\S+)|em\\d+|p\\d+p\\d+|br\\S+|k8s\\S+|vxlan\\S+)$"
  }
}

prometheus.exporter.unix "node_exporter_system_60s" {
  set_collectors = [
    "filesystem",
    "uname",
    "os",
  ]
  include_exporter_metrics = false
  filesystem {
    fs_types_exclude = "^(autofs|binfmt_misc|bpf|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs|nfs[0-9]*|tmpfs)$"
  }
}

prometheus.scrape "node_exporter_system_15s" {
  forward_to = [prometheus.remote_write.mimir.receiver]
  targets = prometheus.exporter.unix.node_exporter_system_15s.targets
  scrape_interval = "15s"
}

prometheus.scrape "node_exporter_system_60s" {
  forward_to = [prometheus.remote_write.mimir.receiver]
  targets = prometheus.exporter.unix.node_exporter_system_60s.targets
  scrape_interval = "60s"
}


Localhost plugin failed to solve the problem of sending http requests in build production

Hi, everybody. I am in Windows and I used axios to successfully send http api requests in dev mode. When I am in build mode, my api requests failed.
I refered to this issue and properly configured the tauri-plugin-localhost
The config file:
    "allowlist": {
      "all": false,
      "http": {
        "all": true,
        "request": true,
        "scope": ["http://**", "https://**"]
      }
    },
    "security": {
      "csp": null,
      "dangerousUseHttpScheme": true,
      "dangerousRemoteDomainIpcAccess": [
        {
          "domain": "localhost",
          "windows": ["main"],
          "enableTauriAPI": true
        }
      ]
    },

when I am in dev mode, the http api request succeeded like this

while I am in build mode, the http api looked this. I only got a error page html back

From my perspective, the only difference between these two requests is their remote address. In build mode, the remote address is in ipv6 format. I don't know the reason and effect somehow.
Here is my tauri info
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 126.0.2592.113
    ✔ MSVC: Visual Studio Enterprise 2022
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 16.20.2
    - yarn: 1.22.22
    - npm: 8.19.4

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../docs
    - devPath: http://localhost:8080/
    - framework: Vue.js (Vue CLI)
    - bundler: Webpack
Done in 17.26s.

tauri-plugin-http is not enough to make SSR features of your frontend framework work. It's still a static http server so api calls still won't work. For that you'll need to sidecar your frontend server somehow.
In dev mode those requests are handled by your frontend server already, that's why it's working there.

Thanks for your advice. So is there any easy way to solve this problem of http apis not working in build mode.
I tried to use the fetch api provided by tauri http but I think it was too disrupting a job to rewrite so much apis, or perhaps I should try to sidecar somehow following your instrutions. Or Tauri v2 solved this problem?

tauri-plugin-http is not enough to make SSR features of your frontend framework work. It's still a static http server so api calls still won't work. For that you'll need to sidecar your frontend server somehow.
In dev mode those requests are handled by your frontend server already, that's why it's working there.

Thanks for your advice. So is there any easy way to solve this problem of http apis not working in build mode.
I tried to use the fetch api provided by tauri http but I think it was too disrupting a job to rewrite so much apis, or perhaps I should try to sidecar somehow following your instrutions. Or Tauri v2 solved this problem?

Ah, sorry! In fact this application isn't in ssr, the problem is either about the http requests, and I seemed to find the real problem.
When I am in dev mode, the webpack serves and helps me do some reverse proxy job to send the requests to the backend in production. While in build mode, I don't have such a backend server to do some reverse proxy.
In Vue, it's defined like this:
  devServer: {
    proxy: {
      '^/api': {
        target: 'https://.../',
        ws: true,
        changeOrigin: true
      }
    }
  }

I believe I could run a actix or axum backend server to do the reverse proxy job when I build my production release to pass the cors security wall.


Core: Added :and expression

It's often desirable to require a field only if conditions a and b are fulfilled. This expression lets us do this in a simple manner using a custom expression.
In this case we want confirm to be required if the value of first is "John" or "Jane" and the value of last is "Doe"
<input id="first">
<input id="last">
<input id="confirm" type="checkbox" data-required="#last[value='Doe']:and(#first[value='John'], #first[value='Jane'])" />

Could also be a good idea to add this if you want to validate against values:
$("input").on("change", function($event) {
  var $target = $($event.target);
  $target.attr("value", $target.val());
});

I dont think that it make sense to allow such complex validation rules via markup. Highly customized or otherwise custom domain logic should be implemented in plain JS not via any kind of markup expressions

Will close for now. Feel free to ask further questions regarding this topic here. We can re-open if required.

No worries. Published as a separate jQuery plugin as mu-jquery-and if anyone needs it.


Cranelift: failing assert during DWARF transform

Steps to Reproduce

Download and unzip this file.
With #8693 applied to current main, run the following:

wasmtime serve -S common -D debug-info runtime-eval.wasm

Expected Results
Wasmtime serving the runtime-eval.wasm component as a wasi:http/proxy handler.
Actual Results
A panic with the following output:
thread 'main' panicked at crates/cranelift/src/debug/transform/unit.rs:401:17:
assertion `left == right` failed
  left: StaticModuleIndex(1)
 right: StaticModuleIndex(0)

Versions and Environment
Cranelift version or commit: See STR
Operating system: MacOS Version 14.5 (23F79)
Architecture: Aarch64
@alexcrichton this is the bug I mentioned that I encountered when trying #8693.

Fixed now in the latest commits of https://github.com/bytecodealliance/wasmtime/pull/8693, thanks!


Cannot translate Contains method call

My application has a query string parser that translates a user-provided search query string into an IQueryable expression that can be handed to the database for a database query. Now this search also considers data that isn't in the database. It's a list of selected items that comes from elsewhere but can be part of the search query by the user. So it has to be available in the SQL WHERE clause.
My code currently looks like this:
var result = context.Entries
    // Project to the form needed for the search query string and result
    .Select(e => new
    {
        // This is from local memory
        isSelected = selectedEntryIds.Contains(e.Id),
        // Now follows all table columns
        id = e.Id,
        name = e.Name,
        // and so on, other Entry properties
    }
    // This is my search-query-to-expression extension method
    .Where(queryExpression)
    // Now regular Linq methods again
    .OrderBy(e => e.name)
    .ToList();

The problem is with the Contains method at the top of the select.
Let selectedEntryIds contain (1, 3, 6, 7) and the user-provided search string be "isSelected name:Demo".
I'd expect this to translate to some thing like this:
select id in (1, 3, 6, 7) as isSelected, id, name, ...
from table
where isSelected and name = 'Demo'
order by name

Or maybe this: (not sure how the SQL syntax would be exactly)
select id case when 1 then 1 when 3 then 1 when 6 then 1 when 7 then 1 else 0 end as isSelected, id, name, ...

But it cannot be translated at all.
Further technical details
EF Core version: 2.2 (and probably earlier)
Database provider: PostgreSQL (Npgsql)
Target framework: .NET Core 2.2 (will be upgraded to 3.0/3.1)
Operating system: all (Windows 10, Ubuntu 16.04)
IDE: all (Visual Studio 2017)

Can you please try this with 3.1.0-preview2 and report on the results?

I'm having trouble upgrading my code to work with EF Core 3.0.
IMutableProperty.Relational() is gone. Where can I find it?

Okay, I could replace these calls with SetTableName(), GetTableName() and similar.
Now my test code runs, but it doesn't work correctly. The isSelected part is completely ignored. All rows have this property false and the selection doesn't select anything from this condition. Not sure if there's a warning, I don't have the logging part set up yet.
I'll work my way through to getting the SQL that went to the database. This has been close to impossible in EF Core 2.x. Is it now finally easier?

Okay, I could replace these calls with SetTableName(), GetTableName() and similar.
Sorry for the comment noise. Now my code runs as expected. I could see the SQL query after configuring logging, so EF printed its queries to the console. Seems this translation is already included in EF Core 3.0. It uses something like id in (1, 2). Haven't tested later previews.
The only issue I could find is that it puts this id in (1, 2) part two times, in the select and in the where clause. If this list gets long, maybe a column alias would be more appropriate. But I'm not sure how much of a problem this is to Postgres. And in my application, these lists never get longer than a dozen items.

The only issue I could find is that it puts this id in (1, 2) part two times, in the select and in the where clause

@smitpatel any comment? This seems like an interesting question which we may want to track separately.

Closing as it seems that the original issue no longer exists in 3.0. @ygoe aside from the question of the repetition above, if anything else is still problematic let us know.

There's another occurrence of this type:
dbContext.Entries
    .Select(e => new
    {
        enumText =
            e.EnumField == EnumType.A ? "A" :
            e.EnumField == EnumType.B ? "B" :
            e.EnumField == EnumType.C ? "C" :
            ((int)e.EnumField).ToString()
    });

This produces this massive case/when construct that is repeated a number of times in the SQL query.

@smitpatel any comment? This seems like an interesting question which we may want to track separately.


Refactor texture buffer

I'm going to start working on this so i can improve mipmap loading.

https://github.com/ppy/osu-framework/pull/46


Ruru requires Ruby >= 2.2

I've tried building with 2.1.x but it doesn't have the rb_id2sym symbol (it's a macro in Ruby <= 2.1 IIRC).
There should be a note about this somewhere in the README.

Good catch! Thanks!
@b047b1a5cd75db2f8c15292ad0cca5194a5db286


Unable to see Link Preview In Bot Framework WebChat

Hi Team,
Hope you are doing well!!
I am unable to see the preview of any link in the webchat. Can you please suggest to me if this feature is available or not and if available, can you please let me know how to implement this as we have to implement this on a high priority as this has been raised as a production issue from the clients.

Hi @stevkan, As I am new to this field, I don't have much idea on how to implement this. This is a client requirement raised as a production issue and they want to see the link preview as well in the response in webchat. Hence, I need to understand if webchat supports this feature and if it supports it, how to implement it. Thanks

Hi @RajdeepRay0411, link previewing is not a feature of Web Chat, unfortunately. However, I came across this package on NPM (LinkPreview) that may meet your needs. In short, if a link is presented and clicked on, you could have the page fire an event that would call the LinkPreview package and capture the response. Then you could pass the response into Web Chat by posting an activity. Sample 04.api/d.post-activity-event demonstrates how to post an activity.
As this is technically a "how to" question, I am going to close this (see the below message). The above should give you enough direction, but if you have additional questions, please post them to Stack Overflow.

The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github repo is the preferred platform for information on submitting bug fixes and feature requests.


aws.tags a different Name for each provisioner when the point to the same AWSNodeTemplate

Description
Not really sure whether this is a bug or an improvement in documentation. But looking for a way of setting a Name tag for provisioned instances containing the provisioner name when using a one-to-many relationship of provisioners to awsnodetemplates
Observed Behavior:
You can set tags in a few locations:

Helm

settings.aws.tags

AWSNodeTemplate.spec.tags
It also says in https://karpenter.sh/docs/concepts/node-templates/#spectags, that some tags are set by default

Using AWSNodeTemplate.spec.tags and setting the Name there is okay if you have a one-to-one mapping of Provisioners to AWSNodeTemplates, however if you have a many-to-one mapping of Provisioner to AWSNodeTemplates then relying on the default Name in aws.tags may be okay but if you want a custom naming convention what can you do? I need a slightly different name format but would still like the provisioner name templated in, is this possible? How?

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

@andrewhibbert Sorry, maybe I'm missing the specific problem that you are running into. You are looking to override the name tag but want the name to have a templated name that contains the provisioner name? Can you describe the naming convention that you're wanting specifically?

I think what


Constantly unavailable szkj.vacuum.mjfc01

Hi there,
I have issues recently with my szkj.vacuum.mjfc01 and the MIOT integration. The vacuum is unavailable every few seconds being unable to control it with automations.
This has became an issue since 8th October before it was working well. I'm not sure if an update of the integration has caused this.
This vacuum doesn't seem to work through local connection.

Any ideas??
Thanks

These configurations can be added and it will try to get the device state from the cloud if it is not available in local.
xiaomi_miot:
  device_customizes:
    szkj.vacuum.mjfc01:
      auto_cloud: true


alternative-1: Separate methods for creating sync vs async transfer and simplify return params

Note: I expect compile to fail, this is my suggestion as a PoC. I will clean up the code/naming if we move forward with this PR.
Problem
Currently the CreateTransfer method returns 3 params (*Transfer, *TransferStarted, error). Why we need to do this is explained in our docs' response code section.
Whether *Transfer or *TransferStarted is set/not-nil depends on whether WithTransferWaitFor is set, which can be confusing for customers using this client.
Suggestion
Introduce separate methods for creating an async or sync transfer.
This is best demonstrated in an example:
/** Current implementation **/
transfer, transferStarted, err := client.CreateTransfer(ctx, createTransfer, WithTransferWaitFor())
if err != nil {..}

if transfer != nil {
   // do something with the hydrated Transfer model
} else if transferStarted != nil {
  // do something with the slimmed down TransferStarted model
}

/** With suggestion **/
// Create async transfer
transferStarted, err := client.CreateTransferAsync(ctx, createTransfer)
if err != nil {..}

// Create sync transfer
transfer, err := client.CreateTransferSync(ctx, createTransfer)
if err != nil {
..
// If timeout occurs, they can check the error and transform it using the errors.As construct:
var timeoutErr CreateTransferTimeoutError
  if errors.As(err, &timeoutErr) {
     // access timeoutErr.TransferStarted
  }
}

Resolving LEDG-2676

We could have them split by sync and async but Sync requires the WaitFor in the signature and then still returns three returns. Then for async just require the body and return 2 returns.

When I started the library, I wanted to have a "default" of synchronous and then support an async version of each function call.
moov. CreateTransfer(ctx, createTransfer, ...option)
// and
moov. CreateTransferAsync(ctx, createTransfer, ...option)

Most people will start with synchronous and then add async for performance.
Regardless of any changes to the function signatures, it shows that we need to beef up the readme and go docs so people can easily understand why this function call has three response types.

Closing this; think we'll end up with alternative-2 (https://github.com/moovfinancial/moov-go/pull/96 or alternative-3 (https://github.com/moovfinancial/moov-go/pull/114)


Is possible to use Numba to speed up the preprocessing step of FinRL?

The preprocessing is very slow in FinRL. The Nmba allow GPU parallelization with C speed for process array data. Some high speed trading framework like vectorbt use it.
Is possible to take experience from vectorbt and use Numba to speed up FinRL?

https://github.com/AI4Finance-Foundation/ElegantRL
If you check ElegantRL, you will find more advanced way of using GPU, DGX-2 server and even NVIDIA's SuperPod. Enjoy!

If I understood the code correctly,ElegantRL is used in DRL step. I mean use Numaba in preprocessing data step, like here:
data = DP.clean_data(data)
data = DP.add_technical_indicator(data, INDICATORS)
data = DP.add_vix(data)

Did this part of code use also GPU acceleration?

Yes, ElegantRL is for DRL algorithms.  Your suggestions for accelerating data preprocessing are quite interesting.  Looking forward to workable codes, would that be possible from your end?

@XiaoYangLiu-FinRL If I understood the code correctly,ElegantRL is used in DRL step. I mean use Numba in preprocessing data step, like here:
data = DP.clean_data(data)
data = DP.add_technical_indicator(data, INDICATORS)
data = DP.add_vix(data)

Did this part of code use also GPU acceleration?

@dev590t
Absolutely not. The current does not support numba. We may test the acceleration to decide whether to add numba.

Unfortunaly, I'm not a python data scientist programmer, and have never used Numba. I have discover this lib from the trading lib vectorbt.
vectorbt can also preprocess data. I think it is maybe possible to use the dataframe produced by vectorbt and pass it directly to DRL agent,  instead of use dataframe produced by the built-in code of FinRL.
This have few advandage:

GPU acceleration in preprocessing
it maybe support more indicator than FinRL.  According its doc, it support for 99% indicators in Technical Analysis Library, Pandas TA, and TA-Lib. So it is possible to pass more indicators to DRL agent.

Do you think it is a good direction to explore?

Yes. it is a good direction. Thanks for your suggestions.

Some engineers said that they tried numba, however there exist errors if the scenario becomes complex. They recommend cupy and cython.

I think it is better to test in first existing GPU trading indicator librairy before to decide to reimplement or no the preprocessing step with Numba or Cupy.
And if existing GPU trading indicator librairy is not suitable, Cupy also could be a interested solution.

With respect to existing GPU trading indicator librairy, could you give any examples? What about the performance?


Runner not running for items in queue

Hello, I've noticed a weird issue within runner.rs while running the "demo." While executing listener.recv() the application exits.
if num_errors > 0 || listener.recv().await.is_ok() {
I've debugged this for a couple of hours yesterday and tracked it down to this one point.
When I execute the application with trace logging this is my output.
TRACE mio::poll     > registering event source with poller: token=Token(1), interests=READABLE | WRITABLE
 INFO  sqlx::query   > /* SQLx ping */; rows: 0, elapsed: 242.279µs
 INFO  sqlx::query   > LISTEN "mq"; rows: 0, elapsed: 220.070µs
 INFO  worker         > We are exiting now.
 TRACE mio::poll     > deregistering event source from poller

I'm building this on Rust Stable 1.57, dependencies below.
[dependencies]
sqlxmq = "0.3.4"
sqlx = "0.5.2"
serde = "1.0.125"
log = "0.4.14"
pretty_env_logger = "0.4.0"
tokio = { version = "1.8.3", features = ["full"] }

@xorl what was the issue?


My challenge to you is add music commands to this bot

Title says it all

Any suggestions for an Audio API, smarty?

Victoria.

Victoria.

Got a link or reference?


Meta, links, and errors  Inside Included Block are ignored

Issue: Ignoring meta, links, and errors Inside included Block
Description
After the PR has been merged, the issue of crashes caused by meta fields inside the included block has been resolved. However, the underlying problem persists in that the library is currently ignoring meta, links, and errors fields when they appear inside the included block.
Current Behavior

meta, links, and errors in the included Block:

The library is currently configured to ignore meta, links, and errors fields when they are found inside the included block.
While this prevents crashes from occurring, it means that any data within these fields is not being processed or utilized, which could lead to incomplete data handling in applications.

Expected Behavior
The library should consistently process meta, links, and errors fields across all parts of the JSON:API structure, including within the included block. Specifically:

These fields should not be ignored within the included block.
If these fields are present, they should be properly deserialized and handled just like they are in the root or data blocks.

@thisAAY can we close this?

I will resume working on it, after vacation


Sync submodule dependencies and lock file

I have performed synchronization using add-all-vendor-projects and nimble lock in nim-workspaces project

I am still unable to build the project using nimble codex but this is caused
by the fact that it seems like there is questionable/1.6 Nim macro expansion
issues (I will report separate issue).

I this ready to be merged?

It builds fine using nimble.


Exposing ETag as an attribute of the parsed response object

I would like to access the ETag value on the parsed objects, so I can use it as part of the cache key for Rails fragment caching. I am not too familiar with this codebase, so let me know if this is not the right approach.

Coverage increased (+0.0%) to 99.8% when pulling 73e5c4af122abd912ef4a588e98f1f7953af44a7 on rafaelpetry:expose_etag into a98a2a8b16903597d57c19d9a8c98c743b4107cd on whichdigital:master.

Coverage increased (+0.0%) to 99.8% when pulling 73e5c4af122abd912ef4a588e98f1f7953af44a7 on rafaelpetry:expose_etag into a98a2a8b16903597d57c19d9a8c98c743b4107cd on whichdigital:master.

Seems fine to me, merged.


Weather icon not loading for haze condition

Describe your issue here.
Steps to reproduce

Expected behaviour
Haze icon should load.
Actual behavior
No icon is being displayed.
Would you like to work on the issue?
Yes I would like to work on this issue.

@Swati4star

@syedjahangirpeeran I am still not getting icon for haze condition.

This is the response I am getting for weather info
{"temp":32.0,"temp_units":"C","max_temp":32.0,"min_temp":32.0,"code":721,"condensed":"Haze","description":"haze","icon":"http://openweathermap.org/img/w/50n.png","humidity":75,"humidity_units":"%","pressure":999,"pressure_units":"hPa"}

There is no haze weather xml file(Vector drawable) for night.

In that case, can we have the day one only? (or do one thing, in case, we are not able to find the vector drawable, show the icon url only, which was getting displayed before)

Same is for "dust" and "smoke".

Opening a new issue for this https://github.com/project-travel-mate/Travel-Mate/issues/377


Call Modified() on ColorProperty modifications

Need a Modified() somewhere for callback to work. I'm not sure this is the right place though. I didn't found any in GenericProperty but I found Modified() in some other properties.
Signed-off-by: Nil Goyette<EMAIL_ADDRESS>

This should not be necessary, as the actual assignment (which is called here) already contains a Modified:
void mitk::LookupTableProperty::SetLookupTable(const mitk::LookupTable::Pointer aLookupTable)
{
if ((m_LookupTable != aLookupTable) || (*m_LookupTable != *aLookupTable))
{
m_LookupTable = aLookupTable;
Modified();
}
}


[nri-bundle] Fix bad UX with chart toggles

Is this a new chart
No
What this PR does / why we need it:
It changes the UX on how to enable and configure the charts.
From:
infrastructure:
  enabled: true

newrelic-infrastructure:
  privileged: true

To:
newrelic-infrastructure:
  enabled: true
  privileged: true

Special notes for your reviewer:
This behavior is documented here: https://helm.sh/docs/topics/charts/#tags-and-condition-fields-in-dependencies
As only the first value is evaluated, there is no possibility of doing any type of compatibility layer. That is the reason the legacy value is first for it to be evaluated in case the user changed the value before upgrading.
You cannot test that it does not render. Asserting hasDocuments.count=0 or using failedTemplate in helm unittest always return this error:
 FAIL  Check defaults	tests/newrelic-infrastructure_test.yaml
	- newrelic-infrastructure do not template with toggles disabled

		- asserts[0] `hasDocuments` fail
			Error:
				template "nri-bundle/charts/newrelic-infrastructure/templates/secret.yaml" not exists or not selected in test suite

	- newrelic-infrastructure old toogle takes precedence

		- asserts[0] `failedTemplate` fail
			Error:
				template "nri-bundle/charts/newrelic-infrastructure/templates/secret.yaml" not exists or not selected in test suite

Checklist

[x] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [mychartname])

Condition - The condition field holds one or more YAML paths (delimited by commas). If this path exists in the top parent's values and resolves to a boolean value, the chart will be enabled or disabled based on that boolean value. Only the first valid path found in the list is evaluated and if no paths exist then the condition has no effect.

For:
    condition: infrastructure.enabled,newrelic-infrastructure.enabled

Does this mean that if infrastructure.enabled does not exist, even if infrastructure. does, newrelic-infrastructure.enabled wil be searched?
I'm trying to make sure we don't break old values or the guided install with this change.

As I said before, this is not testable with helm unittest. These are the test I made: bat values-test-*
───────┬──────────────────────────────────
       │ File: values-test-false-empty.yaml
───────┼──────────────────────────────────
   1   │ newrelic-infrastructure:
   2   │   enabled: false
   3   │ infrastructure: {}
───────┴──────────────────────────────────
───────┬──────────────────────────────────
       │ File: values-test-false-false.yaml
───────┼──────────────────────────────────
   1   │ newrelic-infrastructure:
   2   │   enabled: false
   3   │ infrastructure:
   4   │   enabled: false
───────┴──────────────────────────────────
───────┬──────────────────────────────────
       │ File: values-test-false-true.yaml
───────┼──────────────────────────────────
   1   │ newrelic-infrastructure:
   2   │   enabled: false
   3   │ infrastructure:
   4   │   enabled: true
───────┴──────────────────────────────────
───────┬──────────────────────────────────
       │ File: values-test-true-empty.yaml
───────┼──────────────────────────────────
   1   │ newrelic-infrastructure:
   2   │   enabled: true
   3   │ infrastructure: {}
───────┴──────────────────────────────────
───────┬──────────────────────────────────
       │ File: values-test-true-false.yaml
───────┼──────────────────────────────────
   1   │ newrelic-infrastructure:
   2   │   enabled: true
   3   │ infrastructure:
   4   │   enabled: false
───────┴──────────────────────────────────
───────┬──────────────────────────────────
       │ File: values-test-true-true.yaml
───────┼──────────────────────────────────
   1   │ newrelic-infrastructure:
   2   │   enabled: true
   3   │ infrastructure:
   4   │   enabled: true
───────┴──────────────────────────────────

NOTE: I've omitted everything regarding cluster name and license key.
Then I run this:
for i in values-test-*; do
  echo -n "$i: ";
  helm template test . -f $i -s charts/newrelic-infrastructure/templates/secret.yaml 2> /dev/null | wc -l;
done

The result:

newrelic-infrastructure
infrastructure
templates?

false
empty
no

false
false
no

false
true
yes

true
empty
yes

true
false
no

true
true
yes

The 2> /dev/null is because it does error with Error: could not find template charts/newrelic-infrastructure/templates/secret.yaml in chart because it is not able to template.
I think it is not breaking anything.

Condition - The condition field holds one or more YAML paths (delimited by commas). If this path exists in the top parent's values and resolves to a boolean value, the chart will be enabled or disabled based on that boolean value. Only the first valid path found in the list is evaluated and if no paths exist then the condition has no effect.

For:
    condition: infrastructure.enabled,newrelic-infrastructure.enabled

Does this mean that if infrastructure.enabled does not exist, even if infrastructure. does, newrelic-infrastructure.enabled wil be searched? I'm trying to make sure we don't break old values or the guided install with this change.

The use case in shown in the example id not intuitive because infrastructure. is defined but it does not contain enabled. In that case, as you pointed out, newrelic-infrastructure.enabled is searched and, as I see it, there could be two posibilities:

newrelic-infrastructure.enabled is provided and it should be honoured.
newrelic-infrastructure.enabled is not provided and its default value is taken (its default value actually is the same value newrelic.enabled default value used to be.

Therefore, I agree with @kang-makes , I think this change is backwards compatible.


Update Pages “products”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
a1e073d45ae626c088e655e8bc239a651c900fe2

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/654eedf6aaaa960008bcbb75


help: Document "Who can unsubscribe others from this stream?" setting.

Updates "Remove others" row in "Stream permissions" tables.
Adds a section to "Add or remove users from a stream" describing how to configure the new setting.
Documents the new setting in "Create a stream".
Documents "Message retention period" setting in "Create a stream".

Fixes #24340.
Screenshots and screen captures:

https://zulip.com/help/stream-permissions

https://zulip.com/help/add-or-remove-users-from-a-stream

https://zulip.com/help/create-a-stream

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Calls out remaining decisions and concerns.
[x] Automated tests.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Links.

@alya This PR is ready for you.

@alya I updated the PR and screenshots in response to your feedback.

Great, thanks! @timabbott over to you.

Merged, thanks @drrosa!


Change ansible-lint Github Actions ref

There was a change in ansible-lint GA ref: https://github.com/ansible/ansible-lint-action
It's now official ansible instead ansible-community.

Thanks for discovering that @wiktor2200


Resolve issues with visit_test_data.tar.gz on Trunk and 2.13RC

In 2.13RC, visit_dist_data.tar.gz is LSF'd. That complicates installs for people who don't wanna LSF the whole repo to get that one file. We may not need to take any action here if we don't do another 2.13 release (e.g. 2.13.4). But, John Cary of TechX did run into this recently.
On trunk we don't have visit_dist_data.tar.gz but we should. Instead, we have visit_dist_data.7z. We agreed that this particular data archive would NOT be converted to 7z format and if that happened, accidentally, we need to fix it.
Third, it may be good to NOT LFS this particular file to alleviate users having to deal with LFS to simply build and install.
Another route here is to not use a data archive and just use the data generation tools to produce this data on the fly.
The problems currently encountered potentially prevents installation processes to complete.

Accidentally closed, but reopened.

For the trunk: we should be building the example files as part of our build - not pulling them in via a tarball (or 7z).  I think thats the plan.
I didn't realize the other case was on 2.13RC, that helps

For the trunk: we should be building the example files as part of our build - not pulling them in via a tarball (or 7z). I think thats the plan.

That makes some sense to me. OTOH, doesn't building these example files (and the required data generation executables) add unnecessary dependencies to getting a build of VisIt complete? I mean, what if someone is building VisIt and doesn't want/need Silo, won't this strategy wind up forcing them to require Silo? I am not sure but I can't recall ever being able to build VisIt (via masonry anyways but maybe that is different because it is building one of our release binaries), without also having to build these data files. While for our own releases that makes sense, I don't think it does for users in the wild.

For that case, we can disable building those examples if silo isn't on, skip putting them in the final package all together.

I have moved this to 3.0.1 because in re-reviewing, the issue isn't as pressing as I understood it to be.


saslauthd_ldap doesn't work in a multidomain setup

The saslauthd_ldap service launched by supervisord doesn't work in a multi-domain setup.
My use case is to connect with my full email name<EMAIL_ADDRESS>Context
The saslauthd is run with -d -a (source)
But for the domain not being stripped from the email address as the realm, you need to run it also with -r
Expected Behavior
When I log in to postfix with my full email address, I expect to connect correctly
Actual Behavior
Jan 22 17:43:35 mail saslauthd[1023]: Entry not found ((&(objectClass=inetOrgPerson)(mail=dolanor)(memberof=cn=mail,ou=apps,dc=domain,dc=org,dc=multiverse))).
Jan 22 17:43:35 mail saslauthd[1023]: Authentication failed for dolanor/domain.org: User not found (-6)
Jan 22 17:43:35 mail saslauthd[1023]:                 : auth failure: [user=dolanor] [service=smtp] [realm=domain.org] [mech=ldap] [reason=Unknown]

The realm gets the domain.org but it has been stripped from user=
Possible Fix
I don't know how to fix it so that it doesn't break the people connecting just with their user id, and not their full email address. It would be great to make both behavior possible given a flag.

@dolanor hey there
same problem here.. but for me it actually would be ok to just use<EMAIL_ADDRESS>for user-auth. do you have a solution using only .env or compose.yml -file-modification?

it looks like there's no other possibility than using "-r" also it doesn't make much sense to login with username without email in a multi-domain setup, as there may be multiple users with the "same" username when you don't use the domain-part like "domain\user".
so I would just change it so everybody needs to log-in using their full email-address.

@all is there any way to configure this without modifying the project or interact with the docker manually?

@dolanor
can you send me your config?

Hey you can just modify your filter like this:
((&(objectClass=inetOrgPerson)(mail=%U@%r)(memberof=cn=mail,ou=apps,dc=domain,dc=org,dc=multiverse)))

So the domain is stripped from the user as realm, but you can reuse the realm in the search query.
In theory it should also work with %U@%d but with the latest image it stopped working for me (%d is empty).

Oh good, @SnowMB, thanks for this info.
I will try on my new box where I need to migrate existing setup.

 Thanks @SnowMB
Maybe we should update some wiki information?

@dolanor can you modify / add this to the wiki page?

This issue was closed due to one or more of the following reasons:

Age
Contributor inactivity
The issue seems to be resolved

If you think this happened by accident, or feel like this issue was not actually resolved, please feel free to re-open it. If there is an issue you could resolve in the meantime, please open a PR based on the current master branch so we can review it.


Can someone npm publish v0.3.0?

It was tagged in February but is not released yet. It's blocking users from upgrading to grunt 1.0.0.

Just published (0.3.2, I messed up the process a couple of times - sorry)

Thank you.
In future, if the npm-publish step goes wrong, please publish it as 0.3.0-fix or something. You've now broken the link between npm versions and code versions.


ARM bus fault with code coverage

My code coverage ELF has a bus fault.  Debugging with it, it occurred during while loop in the gcov_static_init as shown below.  My board is my own board wit ARM Cortex M7.
Could you let me know how I can adjust func_pointer_start(&__init_array_start) and func_pointer_end(&__init_array_end)?
So far, code coverage feature is unstable.  For example, without using a function in main, it works, but with using, it has the bus fault, etc.

Additional debugger info.
Thank you for your help!

Could you let me know how I can adjust func_pointer_start(&__init_array_start) and func_pointer_end(&__init_array_end)?

include/linker/common-rom.ld
43-	{
44-		. = ALIGN(4);
45:		__init_array_start = .;
46-		KEEP(*(SORT_BY_NAME(".init_array*")))
47:		__init_array_end = .;
48-	} GROUP_LINK_IN(ROMABLE_REGION)
49-#endif

@andrewboie Thank you for your info!
Could you also give me preferred examples since I'm not familiar with it?
Best regards,
Koji

@andrewboie The section in common-rom.ld you post seems to be selected in case of "#ifdef CONFIG_CPLUSPLUS"
And this is with code coverage feature, I also found the following coverage_rodata.ld.
Which one should I use?  Working with AMR MPU, how can I fix my problem, usage fault?
zephyr/subsys/testsuite/coverage/coverage_rodata.ld
/*
 * Copyright (c) 2019 Intel Corporation
 * SPDX-License-Identifier: Apache-2.0
 */

PROVIDE_HIDDEN (__init_array_start = .);
KEEP (*(SORT(.init_array.*)))
KEEP (*(.init_array*))
PROVIDE_HIDDEN (__init_array_end = .);

Looking at Kconfig.zephyr, in case of COVERAGE, "-O0" option for gcc is selected as shown below.  It doesn't work for my own board which is Cortex-M7 with MPU.  That is, there are usage fault caused by unaligned access.  This means that gcc generates unaligned instructions.  On the other hand, I specified "-O2" instead, it worked and generated coverage report.
Does anyone know if this is gcc problem or exceptional case with MPU?

In addition, ALIGN(4) needs to be added in my case as shown below.

In addition, ALIGN(4) needs to be added into zephyr/subsys/testsuite/coverage/coverage_rodata.ld in my case as shown below.

Does this solve your problem? Can you send a PR? It's odd that this isn't 4-byte aligned already, although I'd have to look at where this linker script fragment gets included


New API from Mar 2025 Onwards

Hi there,
First off, thanks for this! Really loving the integration.
Recently received an email from LTA regarding a revision to the current API and was wondering if this integration would support the new API too?
:)

Hello,
I've checked and it appears the only revision with regards to bus arrivals is the addition of the 'monitored' property. I will add it if i have the time 👍


fix #703

Coverage remained the same when pulling 33dfff8274d116608daed1e8c49b1a0f0f6f3a30 on antgonza:issue-703 into 3c79e6bbec2546040eb7da63629031a71f912915 on biocore:master.

Given that we cannot enforce this naming convention, we risk having inconsistent names across the system.


added the Thank You section written by Kimmy and updated the cohort JSON

Link to Ticket
#20
Description of Proposed Changes

Updated Thank You section (written by Kimmy Bird)

Steps to Test
Outline the steps to test
git fetch --all
git checkout kn-KimmyThankYou

read over Thank You section and make sure there are no errors
also, added more info to the cohort.json for students who updated their information. There isn't anything to test for this
Impacted Areas in Application
List general components of the application that this PR will affect:

Thank You section

Mentions @username
Tag users that need to review this code
@Chewieez @john-dulaney

Should it be future successes? or Our future success?


First draft of new Django ORM backend.

Coverage decreased (-1.4%) to 98.55% when pulling e1f47396b8c00b925ff9662e2efc741cb7a3f885 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.4%) to 99.649% when pulling ebd4575e8927cacdcd659023baa48dafb140f587 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.2%) to 99.781% when pulling 33dbc86bebd188e625debf8ef60f810cdbffdfe7 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage remained the same at 100.0% when pulling 09d22a52d48f0fa13e1dc4ae70dee21cf967fda7 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage remained the same at 100.0% when pulling 09d22a52d48f0fa13e1dc4ae70dee21cf967fda7 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-1.2%) to 98.779% when pulling c78c13886de1997aa2c4a86fa480ebd07ab97633 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling 22a4a7a8d2306beb5c678fe6a560dab45998279f on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling 441b8e9044fe262820159092b89ecee83efa9b28 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling f74e7dc76e8a2de96c668a5bef229df3cf60cb54 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling 1e132daba0107a3bba1929ffc4d15b1e5b7d4b54 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling 1e132daba0107a3bba1929ffc4d15b1e5b7d4b54 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling f29b90a89a6436640cb2554d9228d783d36340d5 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling 1155ff86a2b9a34d5d0854a437eae6162e3d98c4 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling 1155ff86a2b9a34d5d0854a437eae6162e3d98c4 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.

Coverage decreased (-0.1%) to 99.87% when pulling c1feef6a745051e013ca40e6440a076e616b9c80 on feature/django_orm into 30673ed4831ced8c04029ea7de92aecd1cef4d35 on develop.


chore: fix sonar import warning

Description

Merge duplicated import

Related issue*
Fixes #1530

/rtm

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.239%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5277

Relevant Lines:
5579

💛  - Coveralls

@all-contributors please add @Qypol342 for code


Remove the warning 'rvm_chef_user_environment.rb:49: warning: class variable access from toplevel'

....

Any movement on this? I'd love to see it merged in. Logs are a bit deceiving being polluted by this error.

They have a lot of pull requests. I have no idea where this is at.

I've applied this patch and it didn't work, it broke chef-run with:
(rvm::system line 39) had an error: NameError: uninitialized class variable @@root_rvm_path in Object

I'm happy for some one to try to help diagnose this, unfortunately I don't use chef anymore.


feat(goal_planner): set lane departure check margin 0.3

Description
better to keep margin to lane bound to avoid collision

Tests performed
https://evaluation.tier4.jp/evaluation/reports/3b62705e-dfd4-525d-b2eb-5c3b1a9865dd?project_id=prd_jt

Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@soblin could you please approve?


open link in new tab?

Is there or can we have an option to open links in a new tab (when we are opening files inside the vault)?  The way it works now is that when I click on my button the current page is replaced with the new one.
Also, is it possible to have a button act just like a [[link]] to a page such that hovering over it displays the [[link]] in preview mode?

I had the same request, so I made it myself, here's a PR, but this maintainer doesnt seem very active here any longer

should be fixed. reopen if still an issue.


WinUI 3 Gallery crash

Which version of the app?
WinUI 3 Gallery
Description
Hi,
I have played around with WinUI 3 Gallery and sometimes got crash. I can provide one scenario getting crash.
Step 1: Open WinUI 3 Gallery
Step 2: Click on NavigationView (inside Navigtation tab)
Step 3: Click on ParallaxView (inside Motion tab)
Step 4: Click back NavigationView => crash
Thanks.
Screenshots
No response
Windows version
Windows 11 22H2 (22621)
Additional context
No response

Marking as duplicate of #1348


Error when running 'npm install

I had gotten this running but just recently (maybe added dependency) and now get error stack and failure. Message includes "error Failed at the<EMAIL_ADDRESS>postinstall script.
error This is most likely a problem with the angular-seed package,
error not with npm itself." I can also attach npm-debug.log

Closing as this is pretty old and also not actionable.


DbalTracingPass is overridden by DoctrineBundle's own MiddlewaresPass

How do you use Sentry?
Sentry SaaS (sentry.io)
SDK version
4.13.2
Steps to reproduce
Relevant dependencies:

Package
Version

symfony
5.4

symfony/dependency-injection
5.4.34

doctrine/doctrine-bundle
2.11.1

doctrine/dbal
3.7.3

Nothing special otherwise, just have Sentry-Symfony and its profiling integration activated.
Expected result
Sentry hooks into DBAL, to enable its profiling functionality for queries
Actual result
Sentry fails to hook into DBAL, because DBALs MiddlewarePass adds another setMiddlewares invocation that ends up overwriting the call placed there by DbalTracingPass. MiddlewarePass always seems to place that call, no matter if the set of middlewares it adds is empty or not (e.g. with or without Symfony's own profiling middleware).
I suppose the order in which these passes run is important (it'll work if DbalTracingPass runs last (because it removes a previous setMiddlewares call anyway), but it won't work the other way around)
Looking at the generated container in var/cache:
protected function getDoctrine_Dbal_DefaultConnectionService()
    {
        $a = new \Doctrine\DBAL\Configuration();

        $b = new \Doctrine\Bundle\DoctrineBundle\Middleware\DebugMiddleware(($this->privates['doctrine.debug_data_holder'] ?? ($this->privates['doctrine.debug_data_holder'] = new \Doctrine\Bundle\DoctrineBundle\Middleware\BacktraceDebugDataHolder([]))), ($this->privates['debug.stopwatch'] ?? ($this->privates['debug.stopwatch'] = new \Symfony\Component\Stopwatch\Stopwatch(true))));
        $b->setConnectionName('default');

        $a->setSchemaManagerFactory(new \Doctrine\DBAL\Schema\LegacySchemaManagerFactory());
        // DbalTracingPass:
        $a->setMiddlewares([0 => new \Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverMiddleware(new \Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverConnectionFactory(($this->privates['Sentry\\State\\HubInterface'] ?? $this->getHubInterfaceService())))]);
        // MiddlewarePass:
        $a->setMiddlewares([0 => $b]);

[...]
    }

It seems to me that the proper way to go here if possible, is to cooperate with the MiddlewarePass instead of fighting it, e.g. attempting to get TracingDriverMiddleware tagged properly.
Usually, the appropriate tag needed for MiddlewarePass to find middlewares should be added automatically through autowiring to anything implementing its Middleware interface, or marked through the AsMiddleware PHP attribute. The tagging is done by DoctrineExtension.
I don't know enough about autowiring and Symfony's DI system to answer why this isn't working:

TracingDriverMiddleware (indirectly) implements DBAL v3's Middleware interface - maybe it would need to implement it directly?
Manually adding the AsMiddleware attribute did not help, so maybe autowiring just ignores this? Or it's not configured correctly to look at it..

So, adding autoconfigure="true" for TracingDriverMiddleware in the bundle's services.xml magically made it work! (even though I can't choose which connections to trace like this)
I can see that Doctrine lets you specify a connection on a tag, so rewriting DbalTracingPass to just add the middleware tag(s) manually should make this much more robust - unless I missed something?

Can you please try registering the Sentry bundle after DoctrineBundle in config/bundles.php?

Makes no difference, unfortunately. MiddlewaresPass still seems to run first

For now, I'm working around this with the following snippet in services.yaml:
Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverMiddleware:
  autoconfigure: true
  arguments:
    - '@Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverConnectionFactoryInterface'

This is basically what I did before, just in my application's service configuration so I don't need to modify dependency code.
It seems to work, even though it needlessly instantiates TracingDriverMiddleware again (because my definition is technically a separate service, I suppose)
protected static function getDoctrine_Dbal_DefaultConnectionService($container)
    {
        $a = new \Doctrine\DBAL\Configuration();

        $b = new \Doctrine\Bundle\DoctrineBundle\Middleware\DebugMiddleware(($container->privates['doctrine.debug_data_holder'] ??= new \Doctrine\Bundle\DoctrineBundle\Middleware\BacktraceDebugDataHolder([])), ($container->services['debug.stopwatch'] ??= new \Symfony\Component\Stopwatch\Stopwatch(true)));
        $b->setConnectionName('default');

        $a->setSchemaManagerFactory(new \Doctrine\DBAL\Schema\LegacySchemaManagerFactory());
        $a->setMiddlewares([($container->services['Sentry\\SentryBundle\\Tracing\\Doctrine\\DBAL\\TracingDriverMiddleware'] ?? self::getTracingDriverMiddlewareService($container))]);
        $a->setMiddlewares([new \Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverMiddleware(($container->privates['Sentry\\SentryBundle\\Tracing\\Doctrine\\DBAL\\TracingDriverConnectionFactory'] ?? self::getTracingDriverConnectionFactoryService($container))), $b]);

      // ...
    }


add rag_with_knowledge_graphs_neo4j notebook & index

What does this PR do?
Add a new notebook: 'rag_with_knowledge_graphs_neo4j'.
This notebook demonstrates how to:

Build a knowledge graph in Neo4j related to research publications using a synthetic dataset,
Project a subset of our data fields into a high-dimensional vector space using an embedding,
Construct a vector index on those embeddings to enable similarity search,
Extract insights from our graph using natural language by easily converting user queries into statements with

Who can review?
@merveenoyan and @stevhliu.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Thanks a lot @stevhliu - Your suggestions have been incorporated into the PR. Please let me know if there are any further improvements needed.

Thanks @merveenoyan - I have incorportated your suggestions into the PR.

@dcarpintero there should've been some merge conflicts coming from main to here but there isn't, seems interesting. Can you merge main to this branch manually?
the CI fails because we recently merged another notebook called multiagent web assistant, I think either the file isn't there or it isn't in toctree

@merveenoyan thanks for the heads-up
I just manually merged main into this branch - please let me know in case there is still an issue with CI


Nimble is missing

I went to run the unit tests, but found that Nimble was missing. I updated the submodules and re-ran script/bootstrap, to no avail. Finally I installed Carthage manually and did carthage update, but the build for Quick-tvOS failed, which apparently aborts the whole process and Xcode still says "No such module 'Nimble'".
Does the Carthage stuff need to be added to bootstrap? Or is there something else I need to do to get this working?
 I copied that one too, and then ZipArchive was missing.

@Uncommon Shouldn't #585 fail if nimble would be missing? The setup of this repository can be tricky sometimes and I suspect something to be wrong on your machine, at least that would indicate why #585 is succeeding.

Yeah, I wasn't able to run the tests locally, but I got the travis build to pass without too much trial and error.
I tried on a different machine and had the same tvOS failure. I see that Nimble & Quick are not subprojects; how are they supposed to get built?

Stupid question, but did you use the Xcode Workspace?

 So it does work if I run the tests from the workspace. Should I expect it to work just with the project, or is that not a goal?

No, shouldn't work that's why the workspace is there. You might need to link all the frameworks in your project as well, if this is the problem.
Closing this as solved then 😊


Mapping to graph url

How does one map the itemId to a microsoft graph URL?
Found, this, not sure if there's a better way... https://blog.mastykarz.nl/office-365-unified-api-mail/

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

ID: fbb2ef5c-e278-6aba-6fe8-7a4cc0e357d5
Version Independent ID: ebc95637-b567-86b8-4f6d-ee9c6afee19e
Content: Office.context.mailbox.item - requirement set 1.5 - Office Add-ins
Content Source: docs/reference/objectmodel/requirement-set-1.5/office.context.mailbox.item.md
Product: outlook
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@exextoc Can you take a look?
Thanks.

@xstos Thanks for your interest in Office Add-ins. We use the issues in this repo to track problems with the documentation. Consider raising this technical question on Stack Overflow and be sure to tag it office-js. That way the whole community will benefit from the answers that you get.
Thanks.


set &scrolloff based on size of context text

This PR would close issue https://github.com/romgrk/nvim-treesitter-context/issues/28, preventing the cursor from overlapping with the context text.

I've opened #9 which I think deals with this issue more gracefully without messing with the value of 'scrolloff'. What do you think?

Closing this PR in favor of #9.


Metrics: Remove code related to clear/reset metrics at runtime.

With the latest metrics machinery code we have decided to deprecate this feature for ATS 10.
Metrics are now non persistent so they get reset on every restart.
email to the dev list is here
This closes: https://github.com/apache/trafficserver/issues/11541

Cherry-picked to v10.0.x


License Report Blank Expiration Date Fields

Whenever we run vCheck, the license report shows all of our licenses, but the Information and ExpirationDate fields are all blank.  Otherwise, the report is accurate.  I drilled down into the PowerShell script, and it is looking for a property where the value of $_.key -eq 'expirationDate'.  That key does not exist on any of the licenses in our vCenter 7.0U3 system.

Happen also in my environment. I believe the issue is related to non expiring licenses.

vCheck license report before fix:

vCheck license report after fix applied:


https://docs.perl6.org/type/PseudoStash is 404

The link to PseudoStash from the type diagram in Any is not found.

I have assigned a few who I have seen have worked on the module. The doc is simply not there. And I really have no idea how to start writing about it.

PseudoStash is the stash type (hanging off .WHO) that backs various pseudo-packages. So, when you do MY:: or CALLER::, that gives back a PseudoStash. In most cases, PackageName:: gives back a Stash. Neither of these are objects the user is expected to create by themselves, but of course it's interesting to document what you can do once you have one (which boils down to "use it like a hash").

I can just take that and turn it into a page :-)

On 27 May 2017, at 13:21, Jonathan Worthington<EMAIL_ADDRESS>wrote:
PseudoStash is the stash type (hanging off .WHO) that backs various pseudo-packages. So, when you do MY:: or CALLER::, that gives back a PseudoStash. In most cases, PackageName:: gives back a Stash. Neither of these are objects the user is expected to create by themselves, but of course it's interesting to document what you can do once you have one (which boils down to "use it like a hash").

To give you an example:
$ 6 'my $a = 42; my $b = q/$a/; dd MY::{$b}'
Int $a = 42
This shows that you can use a (pseudo-)stash to look up variable by name at runtime.
Does this help?
Liz

Assigned @JJ based on his comment 16 days ago

Also touched in 0a0d8463


Update contributing guidelines to clarify docs mirroring on sdk repos

I hope most of the friction will be solved by #542, but it'll be helpful to describe how the docs mirroring works in a bit more detail. As a bonus, describing the current process may make it easier to automate mirroring/syncing in the future.

@austinlparker one of my thoughts for this is to add a readme each language's website_docs directory in those repos (and have them mirrored back here), at least so people know whether they're in the right place (i.e. "You know you're in the right place because the directory should be called website_docs" basically). That would involve opening PRs against all the language repos though, so I might hold off on that for now.
Even a readme under docs/content/en/ in here might be a good start.

Oh there's also the contribution guidelines page page that gets published 🤔
It's pretty buried at the bottom of the menu though so idk how many people see it. This is starting to be a lot of pages to update. Let me poke at this a bit.


Display OpenAPI specification on docs site

We want to display the OpenAPI specifications for webhooks and exchange rates in the sidebar just like how OpenPayments does it. See https://github.com/interledger/rafiki/tree/main/packages/backend/src/openapi for source files.

related: https://github.com/interledger/rafiki/issues/1668

Closing in favour of #1668


Created CONTRIBUTING-bn.md and added to README.md

What does this PR do?
Fix issue #8822. @shrn01 Please review. I would take back the previous PRs
Checklist:

[X] Read our contributing guidelines.
[X] Search for duplicates.
[X] Include author(s) and platform where appropriate.
[X] Put lists in alphabetical order, correct spacing.
[X] Add needed indications (PDF, access notes, under construction).
[X] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@shrn01 I am following up this issue? Can you please ask some bengali member of the organization to check it?
If this gets merged I would start working on the code of conduct.

Hey @Akash190104 you can add the code of conduct and update the same PR, or you can create a new branch and add code_of_conduct there and raise a new PR


Dynamic parameters on scheduled runs

In order to handle dynamic parameters based on schedule time (like {{ ds }} in airflow), we need possibility to override params when calling kedro kubeflow schedule.
For example, we can allow extra parameters override:
kedro kubeflow schedule --param 'ds:[[ScheduledTime.2006-01-02]]' ...

and then use params argument of create_recurring_run.

Btw. the available params are documented only in the sample code so far: https://github.com/kubeflow/pipelines/issues/3855 and in order to use formats one need to follow layouts described here: https://programming.guide/go/format-parse-string-time-date-example.html


use pointer to endpoint via NewEndpoint initializer

/cc @linki
as per your suggestion moving out part of the another PR to the current one. Need this PR merged first

lgtm


Add properties to IndexingParameters from .NET's IndexingParametersExtensions

Follow-up from #Azure/azure-sdk-for-net#12154. We want to make those changes to the configuration member actual model properties instead of extension methods. This will track the work to update the swagger with what the server already supports, though we may want to rename some of the client enum values depending on whether "storageMetadata" truly means "metadata" in the way Storage refers to it, which has "content", "metadata", and "properties" as separate concepts.
Ideally, all these changes are in swagger so generators just pick it up automatically.
/cc @jennifermarsman @bleroy @brjohnstmsft

@jennifermarsman this issue should no longer be necessary, right? Re-reading my description, I believe the work you did ~August resolved this issue, yes?

@jennifermarsman this issue should no longer be necessary, right? Re-reading my description, I believe the work you did ~August resolved this issue, yes?


Share Intent Causing Instant Crash on Mac

Describe the bug
Using the share intent on Mac leads to an instant crash.
To Reproduce

Install the app from Test Flight
Click on Share from any app

Environment
give the output of the following command npx react-native info
Additional context
Add any other context about the problem here.

expo version (ex: 49) : 52
using firebase : no
using static build :  no
routing : expo-router
package version (ex: 1.2.0) : 1.2.0
platform target :  iOS
device : real device
type: expo build

any debug information from the crash log ?

cannot reproduce on my side :/
don't hesitate to reopen if you have more informations


update popular on server

Codecov Report

Merging #343 (1b99b17) into master (0973540) will increase coverage by 0.09%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #343      +/-   ##
==========================================
+ Coverage   72.81%   72.91%   +0.09%
==========================================
  Files          44       44
  Lines        9321     9355      +34
==========================================
+ Hits         6787     6821      +34
+ Misses       1808     1805       -3
- Partials      726      729       +3

Impacted Files
Coverage Δ

master/tasks.go
53.72% <0.00%> (ø)

storage/cache/database.go
71.05% <ø> (+26.31%)
:arrow_up:

server/rest.go
67.39% <51.42%> (-0.38%)
:arrow_down:

storage/cache/redis.go
81.81% <91.66%> (+0.27%)
:arrow_up:

master/rest.go
58.03% <100.00%> (ø)

storage/cache/no_database.go
100.00% <100.00%> (ø)

worker/worker.go
63.31% <100.00%> (ø)

master/task_manager.go
90.44% <0.00%> (+2.20%)
:arrow_up:

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 0973540...1b99b17. Read the comment docs.


Conflict KSCrashAblyFork

Hi
im new to posting issues but i have problem with Ably v1.2.1 paired with Firebase/Storage and Firebase/Firestore in pods, im getting error 'absl/base/internal/inline_variable.h' file not found in KSCrashAblyFork
Any idea how to fix this? Thank you

I'm also having this issue -- any insight would be nice!

Thanks for the reports, @bcondeskylinedynamics and @reinshope ...
I'm going to have a look at this. Please bear with me.