setParameters failed

After #111 , always setParameters failed.
Device: Sony Z2
OS: 6.0.1
Process: com.flurgle.camerakit.demo, PID: 17302 java.lang.RuntimeException: Unable to resume activity {com.flurgle.camerakit.demo/com.flurgle.camerakit.demo.MainActivity}: java.lang.RuntimeException: setParameters failed 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3160) 	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3191) 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2529) 	at android.app.ActivityThread.access$900(ActivityThread.java:154) 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1391) 	at android.os.Handler.dispatchMessage(Handler.java:102) 	at android.os.Looper.loop(Looper.java:224) 	at android.app.ActivityThread.main(ActivityThread.java:5526) 	at java.lang.reflect.Method.invoke(Native Method) 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726) 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) Caused by: java.lang.RuntimeException: setParameters failed 	at android.hardware.Camera.native_setParameters(Native Method) 	at android.hardware.Camera.setParameters(Camera.java:1939) 	at com.flurgle.camerakit.Camera1.setFlash(Camera1.java:141) 	at com.flurgle.camerakit.Camera1.adjustCameraParameters(Camera1.java:433) 	at com.flurgle.camerakit.Camera1.openCamera(Camera1.java:361) 	at com.flurgle.camerakit.Camera1.start(Camera1.java:86) 	at com.flurgle.camerakit.CameraView.start(CameraView.java:301) 	at com.flurgle.camerakit.demo.MainActivity.onResume(MainActivity.java:95) 	at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1259) 	at android.app.Activity.performResume(Activity.java:6361) 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3149) 	... 10 more

Can you see if OnResume is being called twice in your project, mine is for some reason which is what causes this exact same problem.

@adamwlarson
Thanks your comment,
This report issue is using demo project,
It's not called twice in this demo project,
maybe is another reason.

I have getting setParameters failed every time when Camera1.resetFocus is called.

@eduardo4jesus does #140 solve your issue?
I guess your log looks a little bit different than @mhwu1103 's, right? I'm getting almost the same log as @mhwu1103, but can't see any relation to the resetFocus.

Wow, Thanks a lot @Johnson145 .
#140 does solve my issue. However this solution causes it to freeze the camera for a little while sometimes. On logcat I am getting:
I/Choreographer: Skipped 92 frames!  The application may be doing too much work on its main thread.
In my temporary solution, I had to comment the call params.setMeteringAreas(null); I guess #140 would be a more correct solution, since we check if the FOCUS_MODE_CONTINUOUS_PICTURE is supported before setting it while still resetting the metering areas to null.
Another detail that might cause issues is the != for comparing Strings on this method. I replaced it by equals instead, resulting in the code bellow:
if (!params.getFocusMode().equals(Camera.Parameters.FOCUS_MODE_CONTINUOUS_PICTURE)) {
                        List<String> modes = params.getSupportedFocusModes();
                        if (modes.contains(Camera.Parameters.FOCUS_MODE_CONTINUOUS_PICTURE)) {
                            params.setFocusMode(Camera.Parameters.FOCUS_MODE_CONTINUOUS_PICTURE);
                        }
                        params.setFocusAreas(null);
                        params.setMeteringAreas(null);
                        camera.setParameters(params);
                    }

I had something similar that I ended up doing this change to fix https://github.com/adamwlarson/CameraKit-Android/commit/3e59b6dbb6dae0573962626e70ed9ca918b99252
setParameters was failing because of the calculation of capture size


Debug build fails in ONNX

$ cmake .. -DCHAINERX_BUILD_PYTHON=OFF -DCHAINERX_BUILD_CUDA=OFF -G Ninja -DCMAKE_BUILD_TYPE=Debug
$ ninja
$ build-dbg/tools/run_onnx --test third_party/onnx/onnx/backend/test/data/node/test_abs
Initializing ChainerX...
Loading model...
Loading data...
Found 1 test cases
Constructing model...
terminate called after throwing an instance of 'chainer_compiler_onnx::assert_error'
  what():  ../third_party/onnx/onnx/defs/schema.cc:824: SchemasRegisterer: Assertion `dbg_registered_schema_count == DbgOperatorSetTracker::Instance().GetCount()` failed: 236 schema were exposed from operator sets and automatically placed into the static registry.  248 were expected based on calls to registration macros. Operator set functions may need to be updated.

Probably, the right solution is to create a custom ONNX op registry instead of adding custom ops to opset 9, but I'm going to disable assertion for now.

Heh, I didn't expect the solution is this easy. Thanks for the nice finding!


Support forward slashes in network share (UNC path) completion (#17111)

PR Summary

This PR implements support for forward slashes in partial network share (UNC paths) names when performing tab completion (https://github.com/PowerShell/PowerShell/issues/17111)
PR Context

This makes tab completion easier to use e.g. when using French layout keyboards, where entering a forward slash (Shift+:) is way easier than entering a backslash (AltGr+8).
PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes

Tab expansion will handle partial inputs in the form //hostname/... in addition to the canonical \\hostname\... form

[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[X] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[X] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[X] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[X] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[X] Issue filed: https://github.com/PowerShell/PowerShell/issues/17111

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

Can't think of any reason why the change would break that CI test...

@sba923 Please add test(s).

@sba923 Please add test(s).

This is an interactive feature, how can I possibly add (CI) tests?

@sba923 See TabCompletion.Tests.ps1 file for examples.

@sba923 See TabCompletion.Tests.ps1 file for examples.

Sorry, I'd missed that.
Now I need to find out how to locally run the tests with the one I've just added, but that is probably documented somewhere.

Now I need to find out how to locally run the tests with the one I've just added, but that is probably documented somewhere.

https://github.com/PowerShell/PowerShell/blob/master/docs/testing-guidelines/testing-guidelines.md#running-tests-outside-of-ci
😉

@sba923 Please add test(s).

Done.


Can't start traffic analysis: Starting mitmproxy failed after a timeout.

Hey,
was trying to run this project to test an app and see how it works.
Setting up an android emulator, installing an app etc. with tweasel-cli worked with not issue.
But when it comes to traffic-recording the mitmproxy part fails for me:
file:///home/**/tweasel/node_modules/cyanoacrylate/dist/index.js:261
            if (e.name === "TimeoutError") throw new (0, $kYxtx$TimeoutError)("Starting mitmproxy failed after a timeout.");
                                                 ^

TimeoutError: Starting mitmproxy failed after a timeout.
    at file:///home/**/tweasel/node_modules/cyanoacrylate/dist/index.js:261:50
    at async startTrafficCollection (file:///home/**/tweasel/node_modules/cyanoacrylate/dist/index.js:258:9)
    at async file:///home/**/tweasel/test.js:25:5

Node.js v18.17.1

I already tried running the post install script for this project again to see if this brings any errors and checked the cache for the existence of python file. That works.
But I couldn't find the .venv directory mentioned in https://github.com/tweaselORG/cyanoacrylate/issues/12.
Any ideas what I could do to get this running?

Hey,
thank you very much for the detailed explanation. That brought me to the issue!
Probably from earlier tests with mitmproxy I had some old CA files in /home/$USER/.mitmproxy/ owned by root.
When running your command as non root user it failed opening them. After deleting the directory it worked just fine.

Great, glad to hear that! I've opened #44 to see whether we can provide more helpful information if mitmproxy fails to start.


(#57): drop material design colors; depend on eo_color

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5e797eb). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             master       #58   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?        36
  Lines             ?       159
  Branches          ?         0
==========================================
  Hits              ?       159
  Misses            ?         0
  Partials          ?         0

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 5e797eb...385fba3. Read the comment docs.

@rultor good to merge.

@rultor good to merge.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor good to merge.

@rafamizes Oops, I failed. You can see the full log here (spent 15s)
+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 3221
+ echo '1.69.1 839260fab'
1.69.1 839260fab
+ date
Sat May 22 01:39:41 CEST 2021
+ uptime
 01:39:41 up 236 days,  9:45,  0 users,  load average: 0.00, 0.00, 0.00
+ cat
.rultor.yml in rafamizes/secret doesn't allow dartoos-dev/flutter_brand_palettes to use its assets (there are 2 friends), see http://doc.rultor.com/reference.html#assets
+ exit -1
'cid' file is absent, container wasn't started correctly

@rultor good to merge.

@rultor good to merge.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor good to merge.

@rafamizes Oops, I failed. You can see the full log here (spent 2min)
* line 1, column 1 of lib/src/brands/tiktok.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/twitter.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/spotify.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/whatsapp.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/uber.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/instagram.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/linkedin.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/fedex.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/netflix.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/android.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
* line 1, column 1 of lib/src/brands/slack.dart: eo_color is in the `dev_dependencies` section of `pubspec.yaml`. Packages used in lib/ must be declared in the `dependencies` section.
    ╷
  1 │ import 'package:eo_color/eo_color.dart';
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
Sorry, your package is missing some requirements and can't be published yet.
For more information, see: https://dart.dev/tools/pub/cmd/pub-lish.
\u001b[31mpub finished with exit code 65\u001b[39m
container b20d35c17b3ffb5acfddc75867cc8765812e664a1fa614626fafb8fbc10e1726 is dead
Sat May 22 01:46:09 CEST 2021

@rultor merge.

@rultor merge.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge.

@rafamizes Done! FYI, the full log is here (took me 2min)

Merged by Rultor.


[main] Update actions

Cron -knative-prow-robot
/cc we don't use Prow
/assign $we don't use Prow
Produced by: knative-sandbox/knobots/actions/update-actions
Details:

Codecov Report

Merging #244 (e35aa74) into main (f4c6a07) will increase coverage by 0.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #244      +/-   ##
==========================================
+ Coverage   80.05%   80.32%   +0.26%
==========================================
  Files          20       20
  Lines         747      747
==========================================
+ Hits          598      600       +2
+ Misses        135      133       -2
  Partials       14       14

Impacted Files
Coverage Δ

pkg/vsphere/adapter.go
64.84% <0.00%> (+1.56%)
: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 f4c6a07...e35aa74. Read the comment docs.


Add support for Security Hub - CORE-364

Description
Closes CORE-364
Adds support for nuking Security Hub
Security Hub itself is simply enabled/disabled for each region, however each instance must be cleared of Member Account links and administrator account links.
This PR adds the ability for cloud-nuke to:

Check if security hub is enabled, disable if so after

Disassociating and deleting any member accounts
Disassociating any administrator accounts

Supports the use of time filter, but does not support the use of configObj regex filtering (as there is only one instance per region that is enabled or disabled - technically it is named default but there is no control over this).
Additional testing was done manually with multiple AWS accounts to ensure the proper functionality of the member disassociation/deletion and administrator deletion.

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.
[x] Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes

Added support for Security Hub

Test failures are unrelated to this change

Nice work! Left some questions about error handling that we should be clear about - otherwise this is looking pretty close :+1:


[cherry-picks] Add 3 new commits from main

Cherry pick newly added commits from main on 6/1/22 at 11:20 AM Eastern Time

test failures have to do with no sparsezoo 1.0.0 nightly being pushed yet. good to land from my end


Notice: TaN Mechanics have changed

The ways of purifying water in TaN have changed. You might want to update your mod to accommodate the new changes.

I just noticed, it is on my lust now. I probably can remove a lot of the logic since they changed vanilla water to be the dirty water.

is there a way to simply disable dirty water in cauldrons, without TaN removing?

Disable the plugin in the modules

Updated in 0.1.4


Warn NaN in FP16 mode in static_graph_optimizations/mnist example

Related to #6168.
This PR fixes the static_graph_optimizations/mnist example to warn possible NaN in FP16 mode.

Jenkins, test this please

Jenkins CI test (for commit 79ec977452ac915ff7b2da9023a95d71f3a12dc6, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 79ec977452ac915ff7b2da9023a95d71f3a12dc6, target branch master) succeeded!

LGTM


V72 proposal

I re-arranged and squashed some of your commits to make a review commit-by-commit easier. It are now 3 concise commits:

Your new build scriot
The changes regarding the new feature
The release step (index.zip, version increment, changelog etc.)

Additionally I synchronized the commits to the master branch of r2-studios ("rebase") so there won't be any merge conflicts.
Please let me know what you think about this proposal.

LGTM. Thank you!


<EMAIL_ADDRESS>Fix hash

Apparently this installer changed upstream:
Checking hash of p4vinst64.msi ... ERROR Hash check failed!
App:         extras/p4v
URL:         https://cdist2.perforce.com/perforce/r23.1/bin.ntx64/p4vinst64.msi
First bytes: D0 CF 11 E0 A1 B1 1A E1
Expected:    f4cd6cbd5ee622fc543222ed19dbdd82520e9ca8d84160a3753660fd2b3ceea1
Actual:      77dc21705c1e6817eed02b6e44243f97bdfc6386c41fdb02f5af9c8c3bc9fc6c

/verify

The bot will automatically fix the hash for relevant manifest, when you create a new issue as instructed by the error output.

Ah, good to know, thank you. I thought perhaps that was reporting the broken hash for a maintainer to update and submitting a PR would save the effort of that but knowing it is auto-maintained by the bot I'll be sure to use that mechanism in the future.


ElastAlert travis job failing for elastisearch < 7

Hi,
I tested locally that elastisearch < 7 failing because o python library elastisearch , it is failing from version elasticsearch==7.0.5 and above.
Please, could you drop travis jobs for elasticsearch < 7 to pass travis jobs tests and accept pull requests which are now failing because of this ?

Yelp/elastalert is no longer maintained. Please use jertel/elastalert2.
https://github.com/jertel/elastalert2


Legacy build does not support IE 11

Attach (recommended) or Link to PDF file here:
https://mozilla.github.io/pdf.js/legacy/web/compressed.tracemonkey-pldi-09.pdf
Configuration:

Web browser and its version: IE 11
Operating system and its version: Windows 10
PDF.js version: v2.9.359
Is a browser extension: no

Steps to reproduce the problem:

Open pdfjs legacy web demo in IE 11

What is the expected behavior?

What went wrong?

Link to a viewer:
https://mozilla.github.io/pdf.js/legacy/web/viewer.html
Description:
The latest stable release where the PDF.js could initialize and display the demo PDF in IE 11 successfully seems to be pdfjs-2.6.347-es5. From pdfjs-2.7.570-es5 on it does not work anymore in IE 11.
Is the legacy build supposed to work for IE 11?
Or do you have any hint I could apply in order to build PDF.js from the code in order to make it compatible with IE 11?
I've tried to adjust the build script to have core-js polyfills and including a .browserslistrc having ie 11 in it which solved most of the JS runtime errors but there remained still errors during the initial loading.

As mentioned in the Wiki, see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support, IE 11 is now explicitly unsupported. (There's no simply way to bring back support manually, since we removed all IE-specific compatibility code).


Add gZip stream compression support

Description
This PR adds support for libp2p stream compressions, namely it introduces 2 stream compression types:

no compression
gzip

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[x] I have added the relevant labels
[ ] I have updated the official documentation
[x] I have added sufficient documentation in code

Testing

[x] I have tested this code with the official test suite
[x] I have tested this code manually

Manual tests
Regular cluster deployment with compression support enables.
Tested multiple nodes with different compression configurations
Documentation update
// TODO
Additional comments
// TODO post benchmark results

Is this change backward compatible with running clients?

Hey @ferranbt,
Yes! The idea is for this compression layer to be optional, where clients would negotiate which compression layer to use (if any). This way, if one of them supports compression, but the other one doesn't, or they support differing compression layers - they can always fall back to uncompressed streams.
The PR is still in draft because we're playing around with this idea in order to get some metrics on the savings. It will see other drastic changes until it's ready for review and mergeable - but the base idea will stay the same: allow clients to negotiate compression layers for streams, and fallback to uncompressed streams in case it's not possible to come to an agreement.


gst_all_1.gst-rtsp-server has double prefix in it's .pc file

Describe the bug
When trying to use this package, I'm getting:
gcc -I... -I/nix/store/y5nlv3w8ddvy35aw3rcq8d4n5ig6ad5d-gst-rtsp-server-1.16.2-dev//nix/store/y5nlv3w8ddvy35aw3rcq8d4n5ig6ad5d-gst-rtsp-server-1.16.2-dev/include/gstreamer-1.0 -I/build/source/build -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -fPIC -MD -MQ sr
c/wfd/libwfd-server.a.p/wfd-media.c.o -MF src/wfd/libwfd-server.a.p/wfd-media.c.o.d -o src/wfd/libwfd-se
rver.a.p/wfd-media.c.o -c ../src/wfd/wfd-media.c
../src/wfd/wfd-media.c:3:10: fatal error: gst/rtsp-server/rtsp-media.h: No such file or directory
    3 | #include "gst/rtsp-server/rtsp-media.h"

To Reproduce
grep -R includedir $(nix-build --no-out-link -A gst_all_1.gst-rtsp-server.dev)/lib/pkgconfig

Additional context
I'm currently disabling gst-rtsp-server's split outputs in order to actually use it.
Notify maintainers
@bkchr
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: gst_all_1.gst-rtsp-server
# a list of nixos modules affected by the problem
module:

We should probably apply https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/merge_requests/1

That patch won't apply. But I managed to apply a different fix based on a common fix to other gst plugins, at https://github.com/NixOS/nixpkgs/pull/97003 .


Just a massive update to lucet-idl

This PR changes pretty much everything over the previous code.

CI indicates that this requires a minor update to Cargo.lock to be checked in

Rebased on master to correct the CI problem. Once it passes we can merge


Allow on-demand initialization of Zephyr drivers in USER program

Is your enhancement proposal related to a problem? Please describe.
The use case is as follows:

It is possible to extend the default, base system with add-on board(s). To be more specific - it is a PCB with PHY IC.
This PHY board has a special GPIO controlled pin to enable power to it.

Temporary solution used
Now, there is a special SYS_INIT() hook function to always enable the power for the "expected" PHY IC module no matter if it is really present or not.
Such approach has several issues:

It is expected that some other add-ons boards will be available in the future, so e.g. the pin control configuration may be different.
The ETH driver is now always enabled and operational no matter if the corresponding PHY is available or not.

Describe the solution you'd like
The desired solution would be to allow the "user application" to call initialization code for the driver (i.e. pin control, PHY, ETH). In that way we could circumvent issue raised in https://github.com/zephyrproject-rtos/zephyr/issues/30692, so all the burden of multiple boards' variants support would be moved to user application without the need to massively modify Zephyr (with proper examples and documentation, so others could easily follow).
It also looks like the "support for disabled devices from DTS" may help as well (https://github.com/zephyrproject-rtos/zephyr/issues/19448).
In principle: now we do have APPLICATION initialization level in SYS_INIT() , which indicates driver initialization just before entering the main() function.
Maybe new keyword could be added (e.g. USER) to indicate that Zephyr's kernel driver (now disabled in DTS) would be initialized in user application?
Describe alternatives you've considered
It looks like Run Time Power Management [PM] could at least mimic to some degree the above functionality.
The PHY driver would be started with PM initialized as disabled. Then user application would start the transfer for the first time (and enabled power for it). After this - the PM would be disabled, so the device would be always ON.
However, this approach lacks the flexibility - so the problem with e.g. pin control for multiple add-on boards is not solved.
To sum up:

Allowing the user space program to handle on-demand devices initialization would allow Zephyr's kernel to be not bloated, and only interested parties would use this functionality.
Any input is more than welcome, as it would be good to at least have a clear idea of how the project is going to tacked this problem in the future (so one can align to this approach).

@lmajewski this reads a bit as a duplicate of #40385, would you agree?

The first use case (i.e. "Add the ability to manually initialize a device:") of https://github.com/zephyrproject-rtos/zephyr/issues/40385 seems to be what I do exactly need.


How to use better-sqlite3 with react?

I'm trying to use better-sqlite3 with my react app and not getting success.
I tried a lot to search on google but I didn't got appropriate results.
Can someone please guide me with an example that how to use better-sqlite3 in react app? What and how should we import?
I mean to say that for using it in pure node app, we use code like this:
const Database = require(better-sqlite3);
const db = new Database(path.join(__dirname, clips.db));
So how to write these 2 lines in react?

See my comment here https://github.com/JoshuaWise/better-sqlite3/issues/660#issuecomment-882380879


Experimental natural language retrievers using duck db

Description
This pull request adds support for natural language retrievers on top of duckDb.
Compare to other approaches this is using duckDb to perform KQL queries instead of python code. This is important as it addresses security concerns when running arbitrary code. The duckDb session is an in memory one and the original data cannot be altered by the retriever.
The schema is also used to generate a description of the set and what could be used for. The description and ontology are then used to calculate a ranking score against the query bundle.
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[x] Yes
[ ] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[x] No

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

Thanks @colombod. Do you want to include this in our llama-index-experimental package or create your own retrievers integration?
It looks like you might be trying to do the latter but incorporate it into the llama-index-experimental package, which is probably not the way to go. Specifically if we put it in the experimental package, then we wouldn't need the pyproject.toml nor would we need llama-index-retrievers-natural-language subfolder

Him thank you for the comment, not sure I am totally following, my idea was to add it to the llama-index-experimental package. What do you suggest?

@colombod Yea as Andrei mentioned, if you want this to be in the experimental package, we can make a folder like llama_index/experimental/retriever/duckdb ? (The current folder name is what I would use for a standalone integration package)

@colombod Yea as Andrei mentioned, if you want this to be in the experimental package, we can make a folder like llama_index/experimental/retriever/duckdb ? (The current folder name is what I would use for a standalone integration package)

this more about natural language retrieved more than a duck db one

@logan-markewich what is the issue with the build? can i get some hint / help


Merge milestones/m150 into releases/shipped

Release notes forthcoming.
See Milestone M150 for summary of changes.

/azp run GitHub VFSForGit Large Repo Build

/azp run GitHub VFSForGit Large Repo Perf Tests

/azp run Windows - Full Functional Tests

/azp run GitHub VFSForGit Mac Functional Tests

/azp run GitHub VFSForGit Mac Functional Tests

/azp run GitHub VFSForGit Mac Functional Tests


Converted to dotnet standard and dotnet core.

Prerequisites

[ ] I have written a descriptive pull-request title
[ ] I have verified that there are no overlapping pull-requests open
[ ] I have verified that I am following matches the existing coding patterns and practise as demonstrated in the repository. These follow strict Stylecop rules :cop:.
[ ] I have provided test coverage for my change (where applicable)

Description

@MingLu8 If you need .NET Standard and ASP.NET Core support, you should use ImageSharp and ImageSharp.Web instead.


Error handling message

Is there an existing issue for this?

[X] I have searched the existing issues

I'm having the following issue:
I get an error when the service "Set parameter" is called
I have following devices connected:

[ ] ecoMAX 3xx series
[ ] ecoMAX 8xx series
[X] ecoMAX 9xx series
[ ] Expansion module B
[ ] Expansion module C
[ ] ecoSTER 200/ecoSTER Touch
[ ] ecoLAMBDA
[ ] ecoNET 300

I'm connecting to my devices using:
USB to RS-485 adapter
I'm seeing following log messages:
Error handling message: required key not provided @ data['name']. Got None (invalid_format)

My diagnostics data:
No response
Code of Conduct

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

Hi,
Thank you very much for the feedback!
It seems, I botched services a little bit when implementing service translations😓
Hotfix version 0.3.10 is now released and should resolve this issue.
Thanks again and sorry for any inconvenience caused!

Hello,
HACS does not show this last update. Does it take longer ?
Thank You !

HACS does not show this last update. Does it take longer ?

You are right, for some reason HACS didn't pick up new tag v0.3.10 even with forced update. Normally it should've done so almost instantaneously.
I've recreated release tag and now, as far as I can see, it picks it up fine now... So weird...
To force HACS to find a new update, please open integration page in HACS, click three dots in the upper-right corner and click "Update information" or just wait for a bit until HACS eventually discovers an update by itself.

If it still doesn't find this update for you, feel free to write me about it. We'll try to re-release it as v0.4.1, maybe it doesn't like minors over 9 now.

Is there any quik way to add extra entities . Ex for parameter "airflow_power_100"  ?
Thank you

Is there any quik way to add extra entities . Ex for parameter "airflow_power_100" ? Thank you

I assume that you want to create a box or a slider, that will allow you to change airflow_power_100. There's not an easy way, but possible, with some limitations:

Create helper input_number integration. Make sure to correctly fill minimum and maximum and current values, as there's no "get_parameter" service yet to get this values from the controller itself (there will be one in the next version though😉).
Create automation, that will watch changes of this helper entity and send them to the controller via set_parameter service.
You can find example for such integration in the YAML below:

description: "Update airflow_power_100 parameter."
mode: single
trigger:
  - platform: state
    entity_id:
      - input_number.airflow_power_100
condition: []
action:
  - service: plum_ecomax.set_parameter
    data:
      name: airflow_power_100
      value: "{{ states('input_number.airflow_power_100') | float(0) }}"
    target:
      device_id: c9ea7bc95d9827402de5ad0ff7ac9490

input_number.airflow_power_100 is the ID of the helper entity that you've created in first step. Also make sure to change device_id to point to your own ecoMAX device in HASS.

It works perfectly.
I appreciate your work.
Thank you
În mie., 4 oct. 2023 la 16:49, Denis Paavilainen @.***>
a scris:

Is there any quik way to add extra entities . Ex for parameter
"airflow_power_100" ? Thank you
I assume that you want to create a box or a slider, that will allow you to
change airflow_power_100. There's not an easy way, but possible, with
some limitations:

Create helper input_number integration
https://www.home-assistant.io/integrations/input_number/. Make sure
to correctly fill minimum and maximum and current values, as there's no
"get_parameter" service yet to get this values from the controller itself
(there will be one in the next version though😉).
Create automation, that will watch changes of this helper entity
and send them to the controller via set_parameter service.
You can find example for such integration in the YAML below:

description: "Update airflow_power_100 parameter."mode: singletrigger:

platform: state
entity_id:

input_number.airflow_power_100condition: []action:

service: plum_ecomax.set_parameter
data:
name: airflow_power_100
value: "{{ states('input_number.airflow_power_100') | float(0) }}"
target:
device_id: c9ea7bc95d9827402de5ad0ff7ac9490

input_number.airflow_power_100 is the ID of the helper entity that you've
created in first step. Also make sure to change device_id to point to your
own ecoMAX device in HASS.
—
Reply to this email directly, view it on GitHub
https://github.com/denpamusic/homeassistant-plum-ecomax/issues/32#issuecomment-1746919396,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOJTIPUF2GHSPCUUOJ64ZFLX5VSO3AVCNFSM6AAAAAA5N3BZR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWHEYTSMZZGY
.
 Glad I could help.


is there working on seagate drive

Hi, I'm looking to make partitions on my SMR host managed seagate disk. is this working on my drive ?

GPT partitions are not supported in Linux with SMR host managed drives, irrespective of the device vendor. If you need a "smaller" chunk of the drive to be exposed as a block device, use dm-linear. See: https://zonedstorage.io/linux/part/ and https://zonedstorage.io/linux/dm/#dm-linear.


Fail to compile on xcode

./node_modules/react-native-config//ios/ReactNativeConfig/BuildDotenvConfig.ruby:39:in +': no implicit conversion of nil into String (TypeError) 	from ./node_modules/react-native-config//ios/ReactNativeConfig/BuildDotenvConfig.ruby:39:in '
Tried with both 11.2 and 11.5
Seems there is an issue with the string interpolation.
This is weird since i never had any issue before to compile with this project.

@tirrorex Did you manage to solve this? Also got this issue out of nowhere

@PerThoresson unfortunatly i do not know. We have a lot of projects using react-native and i think the error was one of the project before we migrate it.
Will bump this if i happen to find the error again but i might've fixed it already, sorry.

@tirrorex I had the same error. This happened to me because my env file was not found during compilation.
When you execute the steps https://github.com/luggit/react-native-config#ios-1, the file that is expected to find is the one you setted at the build preprocessing stage : eg.
echo ".env.staging" > /tmp/envfile
I had a ".env" file but this file was ignored.

@fabricehong not what happened

@fabricehong I am seeing the same issue as you. Any luck on a solution?

You have to do it every time:
In https://github.com/luggit/react-native-config/blob/master/ios/ReactNativeConfig/BuildDotenvConfig.ruby line 75
if custom_env
  File.delete("/tmp/envfile")
end

Unfortunately, the concept of using a temporary file (/tmp/envfile) is inherently flawed. It took me an hour of teeth-gnashing to realise that I had used this plugin with a previous project, so my /tmp/envfile was set to "config.testing" from ages ago. Because today I was using a fresh project, it didn't write a custom /tmp/envfile so Ruby choked on the old one and couldn't read it.
tl;dr;: Delete /tmp/envfile and try again
...worked for me.

@petetastic , I can't solve this issue here, could you explain how you've deleted /tmp/envfile please?

@beeremy My specific issue was that I had switched projects and so the old envfile contained legacy information from the previous project. I simply deleted it with rm /tmp/envile and recompiled.

@beeremy My specific issue was that I had switched projects and so the old envfile contained legacy information from the previous project. I simply deleted it with rm /tmp/envfile and recompiled.

At which path?

At which path?

That is the path. Or at least on a Mac.
/tmp/envfile

This /tmp/envfile does not exist in my Mac!

I am getting the same error. I tried to debug a little bit and readDotEnv.rb in latest code seems to just throw this error for some reason:
implicit conversion of nil into String (TypeError) from ./node_modules/react-native-config//ios/ReactNativeConfig/BuildDotenvConfig.ruby:39:in
i checked and .env file exists in the folder, tried changing the file encoding without success, tried changing ruby version (tried all i had on my system). The error is persistent. Now going to try my luck with an earlier version of the module  :(

Seems like the issue started when the new approach was used for ios (using Catalina+XCode 11).
https://github.com/luggit/react-native-config/commit/1eb6ac01991210ddad2989857359a0f6ee35d734#diff-79638b7ed723b66e69c44d60d4926f36

I had this issue because I was using a scheme that was expecting to copy my env file .env.staging to /tmp/envfile (echo ".env.staging" > /tmp/envfile) as part of the Build Pre-Actions  for the scheme, but I didn't have the file .env.staging
Even after switching back to the "correct" scheme, an artifact was left in /tmp/envfile from the failed command. After deleting that file (rm /tmp/envfile) and using the correct scheme, everything worked again.

One of our developers was having this issue all of a sudden as well. Still not sure the real issue, but I noticed the console output from
react-native run-ios
mentioned

Reading env from .env.dev

so we copied our .env file to .env.dev and the build worked

The OP issue is back on npm version 1.4.1. Reverted to 1.4.0 and the build was successful.

He did you found the solution i'm also getting the same
./node_modules/react-native-config//ios/ReactNativeConfig/BuildDotenvConfig.ruby (LoadError)


[WIP]: Testing 101

This PR lays the basic pattern I propose to use for writing all kinds of tests.
The implementation might seem complicated (even an overkill) at first but the pattern is rather intuitive and easy to grasp.
Basically, I've separated the testing into 3 complementary parts:

Handler tests

What is this? : white-box testing that the handler works with dummy data.
Purpose: Does each handler work as expected?
Bonus:  Local development of endpoints independent of the requirement of having a production database. TDD FTW!

Routing tests

What is this?: black-box testing the service; primiarily the URL routing.
Purpose: Does each service work as expected?

Integration tests

What is this?: testing with a test DB using live data.
Purpose: How does each service work integrated with the DB?

Alternatively, we could have merged all 3 of them into a single "End-to-End" testing pattern.
But then, it won't be Clean Architecture according to Uncle Bob.
The best thing about the new implementation is that it allows us to develop the API independent of the underlying database layer. 🕶
I would be interested in discussing the possible pros and cons of the tests below. 😄
cc @icyflame @ghostwriternr @thealphadollar @themousepotato @Ayushk4
Resolves #10

It seems like what you mean by "handler testing" is actually unit tests for the handler. Is that what you mean?

Technically, it will be a "unit test" only when we mock the database interaction.

If you are using a router like mux, then you don't need this because the router will always work.

I think you are right here. This might sound a bit redundant at first.
However, the routing tests sort of overarch the testing of each service rather than the handler.
Basically, I wasn't convinced to combine this step in the handler tests as it would only confuse the testing process.

I think you mean Integration / functional tests for the whole service

Yes! Essentially, this would be a sanity check for the handlers as opposed to using mock data while developing.
P.S: I've added references and the purpose of each test above.

Ping @icyflame @thealphadollar @themousepotato @Ayushk4
I've implemented all the handler tests for now. 🎉

Merging in 24 hours if nobody has any issues! 😅


en: clarify required members number

What is changed, added or deleted? (Required)
Update dm cluster deploy files.

Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v3.0 changes)
[x] v2.0 (TiDB DM 2.0 versions)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from: https://github.com/pingcap/docs-dm/pull/403
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Have version specific changes
[ ] Might cause conflicts after cherry-picked

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

LGTM

@yikeke PTAL again.

/merge


allow linux mint as a correct os_family and ansible_distribution for java installation.

I think this might not be needed
when: ansible_os_family in ['Debian', 'Linuxmint']  as mint is part of the os family but a different distribution. If you have vagrant you can test it


Quickstart

Running this on a quickstart cluster and then self-merging if it passes.

Rerunning. Failed because
Unable to find image 'gcr.io/heptio-images/golang:1.9-alpine3.6' locally
docker: Error response from daemon: Get https://gcr.io/v2/heptio-images/golang/manifests/1.9-alpine3.6: Get https://gcr.io/v2/token?scope=repository%3Aheptio-images%2Fgolang%3Apull&service=gcr.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
make: *** [cbuild] Error 125


BTabs does not respond to key interactions

Overview of the problem
Buefy version: buefy-next (67ecf3a8b9e1365cc51f37f20b64f85403b0ad8b)
Vuejs version: 3.3.4
OS/Browser: macOS/Safari
Description
<b-tabs> does not respond to arrow, space, and enter keys.
Steps to reproduce
<b-tabs>
    <b-tab-item label="A">
        A
    </b-tab-item>
    <b-tab-item label="B">
        B
    </b-tab-item>
    <b-tab-item label="C">
        C
    </b-tab-item>
</b-tabs>

Click on one of tabs
Press a left or right arrow key to focus on another tab
Press a space or enter key to select the focused tab

Expected behavior
Tabs can be selected with key interactions.
Actual behavior
Tabs do not respond to key interactions.

This was caused by the breaking change around $refs that was introduced in Vue 2 → Vue 3 (before v3.2.25). The change was reverted in v3.2.25. My initial port was made for v3.0.11 and no longer works on v3.2.25 or later.


Call Girls In Dehradun 🔄⁘⟬ 7O374726OI ⟭⁘🔄 Hygienic Dehradun Escorts

**"Why We Are No.1 Call Girls In Dehradun"**Ring Sonia 🎷7O374726OI
Being the premier Call Girls Dehradun, our commitment to excellence is unwavering. Our exceptional blend of professionalism, discretion, and client-centered focus sets us apart. We guarantee customized experiences by selecting a diverse group of experienced Dehradun Call Girls and placing the needs of our clients first at every turn.
At our Call Girl Dehradun, stringent safety measures and confidentiality protocols are non-negotiable. What sets us apart is our easy-to-book procedure, open lines of contact, and focus on creating deep connections. As the best Escorts Service Dehradun, we surpass expectations by providing Dehradun Call Girl Service and specialized Escorts services Dehradun.

"Cash On Delivery Dehradun Escorts "
Ring Sonia 🎷7O374726OI  Cash On Delivery (COD) is a payment method where customers pay for purchases at the time of delivery rather than in advance. This popular option provides convenience and security, allowing customers to check Escorts In Dehradun before payment, instilling confidence and reducing the risk of fraud or dissatisfaction.
Moreover, COD eases choosing Dehradun Escorts Service for those hesitant about sharing financial information or using digital payment methods. However, it comes with challenges like additional handling fees and the risk of non-payment, impacting businesses. Despite its drawbacks, COD remains a preferred choice for many due to its simplicity and assurance.

Call Girls In Dehradun 🔄⁘⟬ 7O374726OI ⟭⁘🔄 Hygienic Dehradun Escorts #25835
Call Girls In Dehradun 🔄⁘⟬ 7O374726OI ⟭⁘🔄 Hygienic Dehradun Escorts #25835
Call Girls In Dehradun 🔄⁘⟬ 7O374726OI ⟭⁘🔄 Hygienic Dehradun Escorts #25835
Call Girls In Dehradun 🔄⁘⟬ 7O374726OI ⟭⁘🔄 Hygienic Dehradun Escorts #25835

**"Why We Are No.1 Call Girls In Dehradun"**Ask Sonia 🎷7O374°726OI
Being the premier Call Girls Dehradun, our commitment to excellence is unwavering. Our exceptional blend of professionalism, discretion, and client-centered focus sets us apart. We guarantee customized experiences by selecting a diverse group of experienced Dehradun Call Girls and placing the needs of our clients first at every turn.
Call Girls In Dehradun 🔄⁘⟬ 7O374726OI ⟭⁘🔄 Hygienic Dehradun Escorts https://github.com/fastlane/fastlane/issues/25835
At our Call Girl Dehradun, stringent safety measures and confidentiality protocols are non-negotiable. What sets us apart is our easy-to-book procedure, open lines of contact, and focus on creating deep connections. As the best Escorts Service Dehradun, we surpass expectations by providing Dehradun Call Girl Service and specialized Escorts service In Dehradun.
WhatsApp Image 2024-05-24 at 3 49 33 PM
"Cash On Delivery By Dehradun Escorts Services "
Ring Sonia 🎷7O374°726OI Cash On Delivery (COD) is a payment method where customers pay for purchases at the time of delivery rather than in advance. This popular option provides convenience and security, allowing customers to check Escorts In Dehradun before payment, instilling confidence and reducing the risk of fraud or dissatisfaction.
Moreover, COD eases choosing Dehradun Escorts Service for those hesitant about sharing financial information or using digital payment methods. However, it comes with challenges like additional handling fees and the risk of non-payment, impacting businesses. Despite its drawbacks, COD remains a preferred choice for many due to its simplicity and assurance.


Use AssemblyTitle if no title is specified in template file

When using NuGet and nuspec files for packaging, we made use of replacement tokens in project nuspec files, to substitute in various values in the nuspec file.
When using Paket, many of these values are substituted for me when not specified, which made the switch over fairly easy.
However it is not exactly like-for-like, as we also used the $title$ replacement token (which does not appear to actually be documented - not sure how we found it!), which substitutes for AssemblyTitle value. Since our project names are simplified forms of the usually rather longer assembly names they create, we now have quite long titles. I'd like to avoid having to manually specify the title in each template file (currently they are mostly same, containing little to nothing which is project specific). I believe it would be fairly simple to update the packing logic to set the package title to be the same as the AssemblyTitle if it is not explicitly specified.
I'm happy to do the work...

Sounds good
On Dec 2, 2015 7:32 PM, "DavidHayden87"<EMAIL_ADDRESS>wrote:

When using NuGet and nuspec files for packaging, we made use of replacement
tokens https://docs.nuget.org/create/nuspec-reference#replacement-tokens
in project nuspec files, to substitute in various values in the nuspec file.
When using Paket, many of these values are substituted for me when not
specified, which made the switch over fairly easy.
However it is not exactly like-for-like, as we also used the $title$
replacement token (which does not appear to actually be documented - not
sure how we found it!), which substitutes for AssemblyTitle value. Since
our project names are simplified forms of the usually rather longer
assembly names they create, we now have quite long titles. I'd like to
avoid having to manually specify the title in each template file (currently
they are mostly same, containing little to nothing which is project
specific). I believe it would be fairly simple to update the packing logic
to set the package title to be the same as the AssemblyTitle if it is not
explicitly specified.
I'm happy to do the work...
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1281.


Add the given text to the article.

Add the text "Oracle VM VirtualBox is a free and open-source hosted hypervisor for x86 computers currently being developed by Oracle Corporation. Developed initially by Innotek GmbH, it was acquired by Sun Microsystems in 2008 which was in turn acquired by Oracle in 2010." to the article.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details
Plagiarized.


[RFE] Add kubernetes-1.27 tests to the CI

Current situation
Currently, Kubernetes 1.27 is not tested in the CI on Flatcar (https://www.flatcar.org/docs/latest/container-runtimes/getting-started-with-kubernetes/#supported-kubernetes-version).
Implementation options

It's possible to take inspiration from this PR: https://github.com/flatcar/mantle/pull/406
Use the checksum.sh helper
Once the Mantle test is merged and it works correctly, open a follow-up PR to add Kubernetes 1.27 to the list of officially supported Kubernetes version (https://www.flatcar.org/docs/latest/container-runtimes/getting-started-with-kubernetes/#supported-kubernetes-version)

Note: it might be interesting to test this new feature https://kubernetes.io/docs/concepts/cluster-administration/system-logs/#log-query as it relies on systemd-journald from the OS

Hi
Is there any update about this issue? Does Flatcar support Kubernetes 1.27?
Kubernetes 1.28 will be released on the 15th of August too.


Bc 23520

Codecov Report

Merging #26 (3d8d4c4) into master (85f19b3) will decrease coverage by 1.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
- Coverage   95.56%   94.50%   -1.07%
==========================================
  Files          13       13
  Lines         925      910      -15
==========================================
- Hits          884      860      -24
- Misses         41       50       +9

Flag
Coverage Δ

unittests
94.50% <ø> (-1.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

heksher/setting_type.py
92.96% <0.00%> (-3.91%)
:arrow_down:

heksher/clients/stub.py
97.29% <0.00%> (-2.71%)
:arrow_down:

heksher/clients/async_client.py
92.90% <0.00%> (-1.51%)
:arrow_down:

heksher/clients/thread_client.py
98.23% <0.00%> (-0.07%)
:arrow_down:

heksher/setting.py
98.07% <0.00%> (-0.06%)
:arrow_down:

heksher/clients/util.py
100.00% <0.00%> (ø)

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


[hotfix][datastream] Fix typos in DataStream

What is the purpose of the change
Fix typos and outdated javadocs in DataStream
Brief change log

Fix a few typos
Fix outdated javadoc for windowAll

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

please merge all of your PRs into a single one. #7867, #7868, #7869, #7870, #7871

Thanks for the review @zentol ,  will do the merge.


Unit tests

Unit tests to test validation (mostly vote related)

unit-tests branch created with basic structure. Also, fake classes made to replicate parts of the discord API.


Ackee Blockchain & RockawayX audit tests

Description
This PR contains all tests implemented as a part of an audit performed by Ackee Blockchain. The tests are written in Woke, Python-based development and testing framework.
There are both unit tests and fuzz tests with randomized inputs. Fuzz tests have parameters throttled down to fit in reasonable execution times. During the audit, the fuzz tests were run for hours.
We can discuss here any technical requirements (directory structure, pipeline settings, etc.) for this PR to be merged.

I’ll merge first and then make the directory adjustments.
Plan is to have a ext/woke directory that contains all the files, including the tomls. And a ext/woke.sh that copies and run the tests.


rww-play features

I believe @bblfish once mentioned rww-play is also using WebID-RSA now. Am I wrong here?
Additionally, some input about WebID-Delegation would be good to get rid of the N/A in the readme.

I am using HTTP-Signature as discussed in Issue-52 https://github.com/solid/solid-spec/issues/52
It has had a lot more review I think, and is an actual spec. I'd recommend everyone switch to it, or at least provide feedback on that issue.


Support Node Compat in Cloudflare Adaptor

Describe the problem
Cloudflare announced Connect to PostgreSQL and it can provide database access from Cloudflare Workers, which combined with SvelteKit would be very powerful:

https://developers.cloudflare.com/workers/databases/connect-to-postgres/

I'm not sure if it is meant to work as the documentation is for Cloudflare Workers and some old links suggest node_compat does not work in Pages. However, the documentation suggests otherwise, as I am using Cloudflare Pages with node_compat flags enabled via the Cloudflare Dashboard as found here:

https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-with-pages-functions

I tried with a project and found a local vite build would fail due to pg being a node library when using the cloudflare-adaptor.
Describe the proposed solution
I found this build-worker project, that includes the @esbuild-plugins/node-modules-polyfill with how to use it here:

https://github.com/brillout/build-worker/blob/master/build-worker.mjs#LL8C8-L8C8

and it turns out Wrangler also uses this library:

https://developers.cloudflare.com/workers/wrangler/configuration/#add-polyfills-using-wrangler

I made my own copy of @sveltejs/adapter-cloudflare to test and added this library. It builds locally and in Cloudflare Pages. While my code compiles and deploys, it does not seem to work as logging from Cloudflare Pages Functions gives the error: ReferenceError: process is not defined error, so I am not sure if I am missing something for the correct polyfill, or it is not possible at the moment due to a Cloudflare Pages limitation.
The documentation states Node.js APIs are available under the node: prefix, and this prefix must be used when importing modules, both in your code and the npm packages you depend on.  However, the database connect documentation does not mention this when it tells you to add the pg package and pg would not be using the node: prefix internally. I also thought I found mention of another proposed option where the node: prefix was not required, but unfortunately I cannot find it.
Alternatives considered
Wrangler 2 source code is a lot more complicated and seems to have a nodejsCompat option that can be passed that is used here:

https://github.com/cloudflare/workers-sdk/blob/4082cfcbdf08740d4a608d3d87df22e51ad0ce4a/packages/wrangler/src/bundle.ts#L107

This announcement mentions the Node.js APIs are provided directly by the open-source Cloudflare Workers runtime, with no need to bundle polyfill implementations into your own code., so perhaps we only need to be able to compile it without the polyfill and then the nodejs_compat flag handles it?
Importance
would make my life easier
Additional Information
No response

@arlair any luck on finding a workaround? The esbuild polyfill solution ideal since that is what Wrangler is using, but I'm also not sure why it's causing runtime errors for you. 😔

Closed by https://github.com/sveltejs/kit/pull/10544


refind: fixed install

Existing package

[x] I am the maintainer of this package.


Enhance filter to have custom filter options render

Current Behavior

Sometimes developers need to deal with normalised data (referencing another data through ID), take for example the following table data:
[
    {
        id: "1",
        name: "Josh",
        companyId: "a1-b2-c3-d4"
    }
]

And the companies data obtained through another means:
[
    {
        id: "a1-b2-c3-d4",
        name: "Google Inc. "
    }
]

The requirement is to show "Google Inc. " for the table column "Company" for example, instead of the ID i.e. "a1-b2-c3-d4".
There is a props to handle this when rendering in table customBodyRender, but when setting the column to be filterable, the filter options appear to display as the raw data, which is the ID "a1-b2-c3-d4".
A means is needed to lookup the company name "Google Inc. " by using the id to render as the filter option label.
We can use filterOptions display key to render a custom filter, but that is overkilled in this scenario, because we just want to change the filter options label.
Expected Behavior

Add a means to customise the filter options label.
For example, a function to return the filter option label based on the filter value, like this:
(filterValue) =>
lookupTable[filterValue]

Maybe add a key in the filterOptions, like customNameRender, or reuse the names key and make it accept function as well.

Have you tried filterOptions: { names: [] }? Or is the request that you want names to accept a function in addition to an array? I am hesitant to complicate the API for this use case, as you can already choose to transform your data however you wish in your API resolutions. If you can do that, I'm not sure it makes sense to bundle generic functions in with this or most other table APIs that are intended to be cleaner.
You do also have the option of using the onTableInit callback in the main options which should let you run generic functions which change the data, though you'd be triggering a re-render, so the better option is to transform your data on your end before feeding it into the table.

Marking as "wontfix" for now, as it sounds to me like the functionality required is available if you also transform your data pre-render, which is recommended.


[Bug report] Display users Java API on playground fails

Version
main branch
Describe what's wrong
Try to display roles and this error occurs:
Unable to process: Error code: 405, error message: No content to map due to end-of-input
at [Source: (String)""; line: 1, column: 0], json string:
Error message and/or stacktrace
see above
How to reproduce
Start the playground and list role via the Java API and call the listUserNames method in GravitinoClient.
Additional context
I assume this is because no users exist? If so the API should handle this situation.
Note that other calls to create or delete users give this error below, so while the playground doesn't support users, that error should probably not occur.
You should set 'gravitino.authorization.enable' to true in the server side `gravitino.conf` to enable the authorization of the system, otherwise these interfaces can't work.

What's your Gravitino client version?

Playground uses 0.6.0. We supports list roles in 0.6.1 and 0.7.0. It's expected behaviour.


working-with-docker-registry.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

https://github.com/notifications?query=is%3Asaved+is%3Aunread

Stop your emails to me!!!!
Vojtech Kriegel

2021 v 5:01, welcome[bot] @.***>:

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Latest 3.0.0 build does not allow device specification

I have tried both the -d and --device option, with two GPUs, GPU0 and GPU1, even if I specify GPU1 it always uses GPU0 so clearly this is not working

I found the issue, it is not documented in the --help
but the -d option has to be specified in between cudaplot and the target folder

I have tow GPUS,
I need the -d too!

It's documented here
The format is bladebit <GLOBAL_OPTIONS> <sub_command> <COMMAND_OPTIONS>.
where -d is part of the subcommand cudaplot so it must come after the subcommand.
GLOBAL_OPTIONS must go before the sub_command, then any option following a sub_command are considered options belonging to that sub_command.

You can get command-specific help test with bladebit_cuda help <command> or (depending on the command bladebit_cuda <command> --help


Solution converted to use new CSPROJ project type / targets .NET Standard 1.6

Solution converted to use new CSPROJ project type / project retargeted to .NET Standard 1.6 / nugets updated to their latest versions.

Hi Aurimas, thanks for the PR.
Looks like the build failed; this needs an updated Build.ps1 and appveyor.yml file. You can find examples in, e.g.: https://github.com/serilog/serilog-formatting-compact-reader
Cheers!

Thanks for your reply and apologies for not checking the build. I have one
question however, is there are reason we are not targeting
451/452/46/461/462? Since this has potential to be used in any .NET
version, i doubt mainstream of development is happening at net45 at the
moment.
Thanks,
kind regards,
Aurimas Gecas
On Wed, Jun 7, 2017 at 10:39 PM, Nicholas Blumhardt <
<EMAIL_ADDRESS>wrote:

@nblumhardt requested changes on this pull request.
LGTM, with build/targeting issues covered.
In src/Serilog.Sinks.Logentries/Serilog.Sinks.Logentries.csproj
https://github.com/serilog/serilog-sinks-logentries/pull/16#discussion_r120751424
:

@@ -0,0 +1,27 @@
+

Serilog event sink that writes to the Logentries.com service.
3.0.0
Serilog Contributors;Michiel van Oudheusden
netstandard1.6

The package should target .NET 4.5 and .NET Standard 1.3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serilog/serilog-sinks-logentries/pull/16#pullrequestreview-42741823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQC99YsWOW5k8tosgqjQrAJCFn5Q3gdhks5sBxh1gaJpZM4Ny3pz
.

--
Thank you,
Kind regards,
Aurimas Gecas

hey once again mate,
So I have retargeted the project to .netstandard1.3;net45 and amended the
build script, created AppVeyor account and I can see my dev branch is
passing now, for my purposes I have also removed the nuget publishing,
since it was failing the build, due to the fact that the key is encrypted
on your account, not mine, not sure how to deal with that. I guess my
previous pull request is still valid. Please let me know if there is
anything else you need me to do in order to make this merge to happen.
Thanks,
Kind regards,
Aurimas Gecas
On Wed, Jun 7, 2017 at 10:39 PM, Nicholas Blumhardt <
<EMAIL_ADDRESS>wrote:

@nblumhardt requested changes on this pull request.
LGTM, with build/targeting issues covered.
In src/Serilog.Sinks.Logentries/Serilog.Sinks.Logentries.csproj
https://github.com/serilog/serilog-sinks-logentries/pull/16#discussion_r120751424
:

@@ -0,0 +1,27 @@
+

Serilog event sink that writes to the Logentries.com service.
3.0.0
Serilog Contributors;Michiel van Oudheusden
netstandard1.6

The package should target .NET 4.5 and .NET Standard 1.3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serilog/serilog-sinks-logentries/pull/16#pullrequestreview-42741823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQC99YsWOW5k8tosgqjQrAJCFn5Q3gdhks5sBxh1gaJpZM4Ny3pz
.

--
Thank you,
Kind regards,
Aurimas Gecas

Hi @agecas - the NuGet step won't run during PR builds, so there shouldn't be any failure from it unless our build is misconfigured. It's needed as part of the build so that packages make it onto the NuGet feed. If you re-enable it and it fails, I can take a look at the error output 👍
Also needs to keep the "deploy on dev/master" setting.
HTH!
Nick

Hi,
Ok so I have added back the nuget provider with the original API key,
however that does cause a failure:
[image: Inline image 1]
Which makes sense since it is a FORK and the key is from your account, so i
guess that is not a problem. The other thing is I have added GitHub
provider as per the example you pointed me to (
https://github.com/serilog/serilog-formatting-compact-reader/blob/dev/appveyor.yml),
however I have not updated the auth-token, since I am not sure what it
should be, so you need to fill this in yourself or remove the GitHub
provider if its not required.
Sorry for taking so long to fix such a simple issue, please let me know if
there is anything else i can do or if something is unclear.
Thank you,
Kind regards,
Aurimas Gecas
On Fri, Jun 9, 2017 at 5:31 AM, Nicholas Blumhardt<EMAIL_ADDRESS>
wrote:

Hi @agecas https://github.com/agecas - the NuGet step won't run during
PR builds, so there shouldn't be any failure from it unless our build is
misconfigured. It's needed as part of the build so that packages make it
onto the NuGet feed. If you re-enable it and it fails, I can take a look at
the error output 👍
Also needs to keep the "deploy on dev/master" setting.
HTH!
Nick
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/serilog/serilog-sinks-logentries/pull/16#issuecomment-307292639,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQC99SVAEogJYGyV6tlLPVbj4PR79qA8ks5sCMqagaJpZM4Ny3pz
.

--
Thank you,
Kind regards,
Aurimas Gecas

Thank you, looks good 👍


Update Install-SPInfoPathFormTemplate.md

Update example

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Install-SPInfoPathFormTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


"Remove all icons" prevents pinning apps to start menu

When enabling the "Remove all icons" option, the autounattend.xml file contains the following line (apparently to be inserted in the "C:\Windows\Setup\Scripts\Specialize.ps1" script):
reg.exe add "HKLM\Software\Policies\Microsoft\Windows\Explorer" /v "LockedStartLayout" /t REG_DWORD /d 1 /f;
But this registry key prevents pinning icons to the start menu, the option simply disappears from context menus. The value must be set to 0 to be able to pin apps again.
Found the info there after encoutering the problem on a fresh install.
Edit: Forgot to mention this was on Windows 11

See my comment here https://github.com/cschneegans/unattend-generator/issues/139#issuecomment-2555866829
It's a weird design by Microsoft because only the start menu that's getting locked down and you can still freely pin and unpin items from taskbar. And you can't customise the taskbar pins via autounattend.xml if the policy you referenced above is disabled. It really is a catch 22 circumstance.

Thanks for the report and the explanation!
 While https://github.com/cschneegans/unattend-generator/commit/c06ff4c10347d432195b7d33cde8f6c30c4948cf addresses the problem, I am not at all happy with the side effects.
I have basically moved the relevant registry values from HKLM\Software\Policies\Microsoft\Windows\Explorer to
HKCU\Software\Policies\Microsoft\Windows\Explorer. Unfortunately, users have no write permissions on their own HKCU\Software\Policies key, so a scheduled task (running with SYSTEM privileges, of course) is needed to set the LockedStartLayout value to 0 once a user has logged on.
Since new users might be added to the system at any time, that task needs to run indefinitely (currently using an interval of 2 minutes). Hence, you might experience a short delay until the Pin to Start menu item appears.

Set-ItemProperty -LiteralPath "Registry::HKLM\SOFTWARE\Policies\Microsoft\Windows\Explorer" -Name LockedStartLayout -Value 0;

Set-ItemProperty -LiteralPath "Registry::HKLM\SOFTWARE\Policies\Microsoft\Windows\Explorer" -Name LockedStartLayout -Value 0;

Using the HKLM branch simply does not work for multi-user installations.

HKLM works for me and my multi-user uses.  Not sure what you're coming up against.


New deconz.dresden-elektronik.de subdomain

Due a new website on dresden-elektronik.de, the old paths might not work for some time.
The redirection of links should be active very soon.
This PR uses the deconz. subdomain to fix the 404.

Looks good! Feel free to merge.


FW-4172 G2P model integration + FW-4124 Reusable sort string field

This PR adds the following features:

Adds support for G2P mappers to help with sorting and cleaning confusables.

G2P requires a default config, which is now stored as an AppJson model fixture.
G2P also requires the initialization of transducers, which is stored in the AlphabetMapper model in characters.py

In order for the AlphabetMapper model to work correctly, the ManytoMany related dictionary entries field of the Character model was moved to dictionary.py.
Adds an automatic custom sort string generated when a dictionary entry is created/updated.

To set up custom order and confusable cleaning for dictionary entries:

Load the default_g2p_config.json fixture
Create Character models that correspond with the characters you will use in a site's alphabet.

Base characters are require, ignorables and variants are optional.

Create an AlphabetMapper class with an appropriate input to canonical mapping that defines confusables.

For example: [{"in": "á", "out": "a"}, {"in": "à", "out": "a"}, {"in": "ᐱ", "out": "A"}, {"in": "Á", "out": "A"}, {"in": "À", "out": "A"}, {"in": "c̣", "out": "c"}, {"in": "č", "out": "c"}, {"in": "C̣", "out": "C"}, {"in": "Č", "out": "C"}, {"in": "ȼh", "out": "ch"}, {"in": "Ȼh", "out": "Ch"}]

To set up custom order and...

This is great info that should live in a permanent place. A readme section for now?

Looking forward to some tests for this. Will that be in a separate review?

Looking forward to some tests for this. Will that be in a separate review?

@caforbes is working on the tests, I believe that they will be in this PR

Looks good. Some optional suggestions:
* Separate files for factories for different models

* Separate files for testing Character and Alphabet models

* Absolute imports instead of relative imports

As per the pep 8 discussion the imports will stay as-is. I've separated the character and alphabet tests. Moving factories should be its own small ticket since there are many factories that fit into many different categories in that file.


reset active element/focus order state on ui close

Related Issues

closes https://transcend.height.app/T-31732

Changelog
This solves a really weird (browser specific) accessibility bug, wherein Chrome users relying on tab focus order for navigation would be routed to the URL bar after modal closure instead of the first interactive/tabindexed element on the page. Various solutions were attempted, such as focusing the document body and blurring the activeElement, but there appeared to be hidden focus order state that wasn't being reset upon a simple element focus call. The only solution I found to work was creating a dummy interactive element with maximum focus priority (i.e. tabindex of 1, at the very start of the body), then focusing and removing it. This essentially puts the focus order pointer at the very start of the list so the next tab will focus the first interactive element just as it would on a fresh page load.

prob a silly question but from an accessibility standpoint, why is not going to first interactive/tab indexed element on the page not good?


Add authorship modeling of CSA documents

Add authorship modeling of CSA documents.
They currently have:

Lead Authors
Contributors
Staff ("CSA Global Staff")
Reviewers

Originally posted by @opoudjis in https://github.com/metanorma/mn-samples-csa/issues/1#issuecomment-604900867

The four requested attributes are roles. Lead author is the default.


Azure Key Vault- How to use AzureCliCredential first when using spring.cloud.azure.keyvault.secret.property-sources[0].endpoint

Discussed in https://github.com/Azure/azure-sdk-for-java/discussions/38982
Issue with spring-cloud-azure-starter-keyvault 5.9.1

Originally posted by lavercr February 28, 2024
There is a really large delay when using spring.cloud.azure.keyvault.secret.property-sources[0].endpoint
The delay is more than 2 mins.
When I do this using AzureCliCredential directly my spring boot app loads and finds the key in seconds.  How can I configure spring.cloud.azure.keyvault.secret.property-sources[0].endpoint to only use AzureCliCredential for authentication.

2024-02-28T11:46:45.153-05:00  INFO 34603 --- [           main] m.p.s.SpringbootAzureKeyvaultApplication : Starting SpringbootAzureKeyvaultApplication using Java 21.0.1 with PID 34603 (/Users/lavercr/src/springboot-azure-keyvault/target/classes started by lavercr in /Users/lavercr/src/springboot-azure-keyvault)
2024-02-28T11:46:45.154-05:00  INFO 34603 --- [           main] m.p.s.SpringbootAzureKeyvaultApplication : No active profile set, falling back to 1 default profile: "default"
2024-02-28T11:46:45.642-05:00  INFO 34603 --- [           main] AbstractAzureServiceClientBuilderFactory : Will configure the default credential of type DefaultAzureCredential for class com.azure.identity.DefaultAzureCredentialBuilder.
2024-02-28T11:46:45.710-05:00  INFO 34603 --- [           main] m.p.s.SpringbootAzureKeyvaultApplication : Started SpringbootAzureKeyvaultApplication in 141.667 seconds (process running for 142.235)

Hi @lavercr thanks for reaching out to us via this github issue.  @saragluna @backwind1233 could you please follow up?
/cc @vcolin7

Hi @lavercr , thanks for reaching out, Could help provide more info about how to use AzureCliCredential directly?

If I create my own secretClient using AzureCliCredentialBuilder I can connect and pull passwords, but this way I have to write all the code. I would like to keep to the one liner that spring.cloud.azure.keyvault.secret.property-sources[0].endpoint gives us.  This loads all the secrets and makes them available to the spring beans right away.  If I do it myself it is more code,  and the beans with secrets have to depend on this bean loading first.  That gets messy quick.
@Configuration

public class AzureKeyVaultConfig {

    @Value("${spring.cloud.azure.keyvault.secret.uri}")
    private String keyVaultUri;

    @Bean
    SecretClient secretClient() {

        AzureCliCredential cliCredential = new AzureCliCredentialBuilder().build();

        // Azure SDK client builders accept the credential as a parameter.
        return new SecretClientBuilder()
           .vaultUrl(keyVaultUri)
           .credential(cliCredential)
           .buildClient();

    }

}

Hi @lavercr , we don't support use AzureCliCredential directly, but you can add this code to only use AzureCliCredential for authentication.
    @Bean(name = DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME)
    TokenCredential tokenCredential( ) {
        return new AzureCliCredentialBuilder().build();
    }

Hi, I don't understand your solution.  Does this need a specific bean name ?
I put a dummy name in and it still took a long time to respond.

can you provide a more complete example that uses
spring.cloud.azure.keyvault.secret.property-sources[0].endpoint
and
  @Bean(name = DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME)
    TokenCredential tokenCredential( ) {
        return new AzureCliCredentialBuilder().build();
    }

Hi @lavercr , could you help provide your minimal project?

can you provide a more complete example that uses
spring.cloud.azure.keyvault.secret.property-sources[0].endpoint
and
  @Bean(name = DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME)
    TokenCredential tokenCredential( ) {
        return new AzureCliCredentialBuilder().build();
    }

can you provide me an example with this working.  where spring.cloud.azure.keyvault.secret.property-sources uses TokenCredential tokenCredential( ) {

create a springboot application with required azure dependencies
	<dependencies>
		<dependency>
			<groupId>com.azure.spring</groupId>
			<artifactId>spring-cloud-azure-starter-keyvault</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>
	</dependencies>
	<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>com.azure.spring</groupId>
				<artifactId>spring-cloud-azure-dependencies</artifactId>
				<version>5.9.1</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
		</dependencies>
	</dependencyManagement>

add this entry into your application.properties file that points to your working key vault
spring.cloud.azure.keyvault.secret.property-sources[0].endpoint=[Your key vault url]
Add a secret to your vault called TestSecret
Setup your main class like this
package com.mbc.poc.springbootazurekeyvault;

import org.springframework.beans.factory.annotation.Value;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class SpringbootAzureKeyvaultApplication implements CommandLineRunner {

    @Value("${TestSecret}")
    private String testSecret;

    public static void main(String[] args) {
        SpringApplication.run(SpringbootAzureKeyvaultApplication.class, args);
    }

    @Override
    public void run(String... args) {

        System.out.println("TestSecret: " + testSecret);
    }

}

Determine how to use AzureCliCredentialBuilder in the authentication options first

create a springboot application with required azure dependencies
	<dependencies>
		<dependency>
			<groupId>com.azure.spring</groupId>
			<artifactId>spring-cloud-azure-starter-keyvault</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>
	</dependencies>
	<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>com.azure.spring</groupId>
				<artifactId>spring-cloud-azure-dependencies</artifactId>
				<version>5.9.1</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
		</dependencies>
	</dependencyManagement>

add this entry into your application.properties file that points to your working key vault spring.cloud.azure.keyvault.secret.property-sources[0].endpoint=[Your key vault url]
Add a secret to your vault called TestSecret
Setup your main class like this
package com.mbc.poc.springbootazurekeyvault;

import org.springframework.beans.factory.annotation.Value;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class SpringbootAzureKeyvaultApplication implements CommandLineRunner {

    @Value("${TestSecret}")
    private String testSecret;

    public static void main(String[] args) {
        SpringApplication.run(SpringbootAzureKeyvaultApplication.class, args);
    }

    @Override
    public void run(String... args) {

        System.out.println("TestSecret: " + testSecret);
    }

}

Determine how to use AzureCliCredentialBuilder in the authentication options first

OK, I update your codes, hope this can help
package com.mbc.poc.springbootazurekeyvault;

import org.springframework.beans.factory.annotation.Value;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import static com.azure.spring.cloud.autoconfigure.implementation.context.AzureContextUtils.DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME;

@SpringBootApplication
public class SpringbootAzureKeyvaultApplication implements CommandLineRunner {

    @Value("${TestSecret}")
    private String testSecret;

    public static void main(String[] args) {
        SpringApplication.run(SpringbootAzureKeyvaultApplication.class, args);
    }

    @Override
    public void run(String... args) {

        System.out.println("TestSecret: " + testSecret);
    }

    @Bean(name = DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME)
    TokenCredential tokenCredential( ) {
        return new AzureCliCredentialBuilder().build();
    }
}

This doesn't work for myself. We have a similar issue where development is done on Azure VMs and would like to override the Default to CLI so that property placeholders also work.

DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME cannot be resolved. I assume this name is important.  Perhaps with quotes ?

my mistake, I missed the import.  I agree, this still seems to be using the default

Unable to find any logging I can turn on to give clarity to what is delaying startup.  I am still assuming it is because it trys AzureCliCredential last to connect to azure key vault.

I believe there is a bug that needs fixing
spring.cloud.azure.keyvault.secret.property-sources does not adhere to
    @Bean(name = DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME)
    TokenCredential tokenCredential( ) {
        return new AzureCliCredentialBuilder().build();
    }

I've got it working using a custom/changed version KeyVaultEnvironmentPostProcessor, setting it to use CLI and adding it to spring.factories in META-INF.  It's a nasty hack but best available right now.

Can we confirm then that this is a bug.  The fact that spring.cloud.azure.keyvault.secret.property-sources does not adhere to DEFAULT_TOKEN_CREDENTIAL_BEAN_NAME

any update?

sorry for the late response and we will take a look about that

@lavercr, this is because the environment processor at an earlier stage, before the default azure credential bean's initialization. To change this behavior, we need to do some refactor, but users need to register the DAC bean in another way.

we need to do some refactor..
So there may be a fix coming our way ?

we need to be able to control the order.

@saragluna  Can I have an update for this fix?

Sorry, this update requires code refactoring, which we need more time to discuss.

Do you have an update?  This is going to be critical for our business unit in the next few months.

any possible way to get more frequent updates? or are you able to give me a patch to work around this issue ?

Not yet, but your contributions are welcome if you are interested

Okay. I get it.  I will have to live with it or create a bandage.

@Netyyyy   I have been asked for a date of fix.  Please provide.  This issue is holding up a security compliancy issue at our company.  If there is another place or contact we can reach out to so we can get this fixed please let me know.
Thank you

For anyone not understanding what this is about.  I am trying to get this solution to work for us.
https://learn.microsoft.com/en-us/azure/developer/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-key-vault#use-spring-key-vault-propertysource

Hi @lavercr, sorry but we can't guarantee a date for the fix, but you could create a support tickect and it will help us prioritize this issue.

okay, do you have a link to create the support ticket, or do you mean go through some contract we have in our organization ?

any progress ??

Sorry for the late response, I just created https://github.com/Azure/azure-sdk-for-java/pull/41580 to fix this issue. With this change, you might need to modify your application as following to register a TokenCredential bean to the ConfigurableBootstrapContext for the KeyVaultEnvironmentPostProcessor to use that token credential.
public static void main(String[] args) {
    SpringApplication application = new SpringApplication(PropertySourceApplication.class);
    application.addBootstrapRegistryInitializer(registry ->
            registry.register(TokenCredential.class, context -> new AzureCliCredentialBuilder().build()));

    application.run(args);
}

This is a straightforward fix for this issue, but we may plan to provide finer grained configuration properties to configure the credential type for a component.


Feature Request: Improve type narrowing for class instances inside switch-case expressions

Suggestion

🔍 Search Terms

constructor, instanceof, switch
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Add type narrowing based on object constructor in switch case expressions.
📃 Motivating Example
Let's imagine we have 2 dedicated parts of our codebase:

Objects creation
Created objects handling

It may be useful to use switch case expression for handling incoming objects instead of using multiple type guards:

Using switch case
abstract class Animal {}

class Pig extends Animal {
    public oink(): void {}
}
class Dog extends Animal {
    public bark(): void {}

}
class Cow extends Animal  {
    public moo(): void {}

}

const animal: Animal = new Pig();

switch (animal.constructor) {
  case Pig: {
    animal.oink()
    break;
  }
  case Dog: {
    animal.bark()
    break;
  }
  case Cow: {
    animal.moo()
    break;
  }
  default: {
    break;
  }
}

Using type guards
abstract class Animal {}

class Pig extends Animal {
    public oink(): void {}
}
class Dog extends Animal {
    public bark(): void {}

}
class Cow extends Animal  {
    public moo(): void {}

}

const animal: Animal = new Pig();

if (animal instanceof Pig) {
    animal.oink()
}

if (animal instanceof Dog) {
    animal.bark()
}

if (animal instanceof Cow) {
    animal.moo()
}

💻 Use Cases
This feature is required in event-driven architectures. Here goes a sample:

Sample
class UserInteractionHandler implements Creatable, Destroyable {
    private readonly onEventCallback: OnEventCallback = (busEvent: BusEvent) => {

        switch (busEvent.constructor) {
            case MouseClickBusEvent: {
                const { payload }: MouseClickBusEvent = busEvent;
                /** ... */
                break;
            }
            case MouseMoveBusEvent: {
                const { payload }: MouseMoveBusEvent = busEvent;
                /** ... */
                break;
            }
            case KeyDownBusEvent: {
                const { payload }: KeyDownBusEvent = busEvent;
                /** ... */
                break;
            }
            case KeyUpBusEvent: {
                const { payload }: KeyUpBusEvent = busEvent;
                /** ... */
                break;
            }
            default: {
                break;
            }
        }

    }

    constructor(private readonly eventBus){}

    public onCreate(): void {
        this.eventBus.listen(this.onEventCallback);
    }

    public onDestroy(): void {
        this.eventBus.unlisten(this.onEventCallback);
    }

}

class MouseEventsPublisher implements Creatable, Destroyable {
    private readonly clickListener: EventListener = (event: MouseEvent) => {
        this.eventBus.dispatch(new MouseClickBusEvent(event));
    }
    private readonly mouseMoveListener: EventListener = (event: MouseEvent) => {
        this.eventBus.dispatch(new MouseMoveBusEvent(event));
    }

    constructor(private readonly eventBus){}

    public onCreate(): void {
        window.addEventListener('click', this.clickListener);
        window.addEventListener('mousemove', this.mouseMoveListener);
    }

    public onDestroy(): void {
        window.removeEventListener('click', this.clickListener);
        window.removeEventListener('mousemove', this.mouseMoveListener);
    }

}

class KeyboardEventsPublisher implements Creatable, Destroyable {
    private readonly keyDownListener: EventListener = (event: KeyboardEvent) => {
        this.eventBus.dispatch(new KeyDownBusEvent(event));
    }
    private readonly keyUpListener: EventListener = (event: KeyboardEvent) => {
        this.eventBus.dispatch(new KeyUpBusEvent(event));
    }

    constructor(private readonly eventBus){}

    public onCreate(): void {
        window.addEventListener('keydown', this.keyDownListener);
        window.addEventListener('keyup', this.keyUpListener);
    }

    public onDestroy(): void {
        window.removeEventListener('keydown', this.keyDownListener);
        window.removeEventListener('keyup', this.keyUpListener);
    }

}

Duplicate of #16035.


Bug in older Safari browsers: "SyntaxError: Unexpected token '='. Expected an opening '(' before a method's parameter list"

Bug report
Describe the bug
When trying to run createBrowserSupabaseClient the browser gives the following error: "SyntaxError: Unexpected token '='. Expected an opening '(' before a method's parameter list.". I found the following stackoverflow on the issue
To Reproduce
Include the line const [supabaseClient] = useState(() => createBrowserSupabaseClient<Database>()); and open the app in an older version of safari than v14.1
Expected behavior
The application should run without errorring out
Screenshots

Further down the stack trace has this line:

System information

OS: macOS
Browser (if applies): Safari v13.1.3
Version of supabase-js: "@supabase/auth-helpers-react": "^0.3.1",
 "@supabase/supabase-js": "^2.1.2",```

Version of Node.js: tried on both 16.13.0 and 18.12.1

Additional context
If I comment out the line of code that creates the supabase instance the app loads fine.

@m-deacon please provide a reproducible repo to make this easier to test out. I haven't ran into this issue before so a repository with the issue happening would be good to have.


fix: allow importing mbtiles without name row in metadata

Fixes #95
Ideally there should be a test to cover this. Not sure if it makes more sense to update an existing fixture or create a new one specifically for this.

@gmaclennan converted this to a draft because I'm unsure if this is something that the map server should account for, given that the metadata row is a MUST in the spec. Also, this needs a test added anyways 😄

Closing in favor of #113