Make ? and % formatters in kv! more flexible

This allows using ? and % formatters when creating new loggers,
e.g. logger.new(o!("foo" => ?bar)).
Note that this is probably a breaking change
as ? and % don't borrow implicitly anymore.

This change is

Would &FmtDisplay<'a>(pub &'a T) be a way for it not to be a breaking change?

I had the same idea, but the issue is the same as with format_args (having a borrow in the kv map).

The non-breaking alternative would be allocating a String, which is less ideal since it's not necessarly for log! invocations.

What's wrong with https://github.com/slog-rs/slog/tree/kv_fmt ?

https://github.com/slog-rs/slog/commit/8d3d34beff650546f800bc5f5b369273ba550bda I mean

I still don't understand what is this improving etc. so please add some tests that used to fail, and now are passing. :)

I've added a test now.
Btw, this is the massive and confisung error you'd get if you try to use ? or % when an owned kv map is required (without this patch):
error[E0277]: `*mut core::ops::Fn() + 'static` cannot be shared between threads safely
   --> src/lib.rs:363:9
    |
363 |         $crate::OwnedKV(kv!($($args)*))
    |         ^^^^^^^^^^^^^^^ `*mut core::ops::Fn() + 'static` cannot be shared between threads safely
    |
   ::: src/tests.rs:255:27
    |
255 |     Logger::root(Discard, o!("foo" => ?n));
    |                           --------------- in this macro invocation
    |
    = help: within `[core::fmt::ArgumentV1<'_>]`, the trait `core::marker::Sync` is not implemented for `*mut core::ops::Fn() + 'static`
    = note: required because it appears within the type `core::marker::PhantomData<*mut core::ops::Fn() + 'static>`
    = note: required because it appears within the type `core::fmt::Void`
    = note: required because it appears within the type `&core::fmt::Void`
    = note: required because it appears within the type `core::fmt::ArgumentV1<'_>`
    = note: required because it appears within the type `[core::fmt::ArgumentV1<'_>]`
    = note: required because of the requirements on the impl of `core::marker::Send` for `&[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `core::fmt::Arguments<'_>`
    = note: required because it appears within the type `SingleKV<core::fmt::Arguments<'_>>`
    = note: required because it appears within the type `(SingleKV<core::fmt::Arguments<'_>>, ())`
    = note: required because of the requirements on the impl of `SendSyncRefUnwindSafeKV` for `(SingleKV<core::fmt::Arguments<'_>>, ())`
note: required by `OwnedKV`
   --> src/lib.rs:3081:1
    |
3081| / pub struct OwnedKV<T>(
3082| |     #[doc(hidden)]
3083| |     /// The exact details of that it are not considered public
3084| |     /// and stable API. `slog_o` or `o` macro should be used
...   |
3088| | where
3089| |     T: SendSyncRefUnwindSafeKV + ?Sized;
    | |________________________________________^

error[E0277]: the trait bound `core::ops::Fn() + 'static: std::panic::RefUnwindSafe` is not satisfied in `(SingleKV<core::fmt::Arguments<'_>>, ())`
   --> src/lib.rs:363:9
    |
363 |         $crate::OwnedKV(kv!($($args)*))
    |         ^^^^^^^^^^^^^^^ the type core::ops::Fn() + 'static may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
    |
   ::: src/tests.rs:255:27
    |
255 |     Logger::root(Discard, o!("foo" => ?n));
    |                           --------------- in this macro invocation
    |
    = help: within `(SingleKV<core::fmt::Arguments<'_>>, ())`, the trait `std::panic::RefUnwindSafe` is not implemented for `core::ops::Fn() + 'static`
    = note: required because it appears within the type `*mut core::ops::Fn() + 'static`
    = note: required because it appears within the type `core::marker::PhantomData<*mut core::ops::Fn() + 'static>`
    = note: required because it appears within the type `core::fmt::Void`
    = note: required because it appears within the type `&core::fmt::Void`
    = note: required because it appears within the type `core::fmt::ArgumentV1<'_>`
    = note: required because it appears within the type `[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `&[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `core::fmt::Arguments<'_>`
    = note: required because it appears within the type `SingleKV<core::fmt::Arguments<'_>>`
    = note: required because it appears within the type `(SingleKV<core::fmt::Arguments<'_>>, ())`
    = note: required because of the requirements on the impl of `SendSyncRefUnwindSafeKV` for `(SingleKV<core::fmt::Arguments<'_>>, ())`
note: required by `OwnedKV`
   --> src/lib.rs:3081:1
    |
3081| / pub struct OwnedKV<T>(
3082| |     #[doc(hidden)]
3083| |     /// The exact details of that it are not considered public
3084| |     /// and stable API. `slog_o` or `o` macro should be used
...   |
3088| | where
3089| |     T: SendSyncRefUnwindSafeKV + ?Sized;
    | |________________________________________^

error[E0277]: `*mut core::ops::Fn() + 'static` cannot be shared between threads safely
   --> src/lib.rs:363:9
    |
363 |         $crate::OwnedKV(kv!($($args)*))
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `*mut core::ops::Fn() + 'static` cannot be shared between threads safely
    |
   ::: src/tests.rs:255:27
    |
255 |     Logger::root(Discard, o!("foo" => ?n));
    |                           --------------- in this macro invocation
    |
    = help: within `[core::fmt::ArgumentV1<'_>]`, the trait `core::marker::Sync` is not implemented for `*mut core::ops::Fn() + 'static`
    = note: required because it appears within the type `core::marker::PhantomData<*mut core::ops::Fn() + 'static>`
    = note: required because it appears within the type `core::fmt::Void`
    = note: required because it appears within the type `&core::fmt::Void`
    = note: required because it appears within the type `core::fmt::ArgumentV1<'_>`
    = note: required because it appears within the type `[core::fmt::ArgumentV1<'_>]`
    = note: required because of the requirements on the impl of `core::marker::Send` for `&[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `core::fmt::Arguments<'_>`
    = note: required because it appears within the type `SingleKV<core::fmt::Arguments<'_>>`
    = note: required because it appears within the type `(SingleKV<core::fmt::Arguments<'_>>, ())`
    = note: required because of the requirements on the impl of `SendSyncRefUnwindSafeKV` for `(SingleKV<core::fmt::Arguments<'_>>, ())`
note: required by `OwnedKV`
   --> src/lib.rs:3081:1
    |
3081| / pub struct OwnedKV<T>(
3082| |     #[doc(hidden)]
3083| |     /// The exact details of that it are not considered public
3084| |     /// and stable API. `slog_o` or `o` macro should be used
...   |
3088| | where
3089| |     T: SendSyncRefUnwindSafeKV + ?Sized;
    | |________________________________________^

error[E0277]: the trait bound `core::ops::Fn() + 'static: std::panic::RefUnwindSafe` is not satisfied in `(SingleKV<core::fmt::Arguments<'_>>, ())`
   --> src/lib.rs:363:9
    |
363 |         $crate::OwnedKV(kv!($($args)*))
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the type core::ops::Fn() + 'static may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
    |
   ::: src/tests.rs:255:27
    |
255 |     Logger::root(Discard, o!("foo" => ?n));
    |                           --------------- in this macro invocation
    |
    = help: within `(SingleKV<core::fmt::Arguments<'_>>, ())`, the trait `std::panic::RefUnwindSafe` is not implemented for `core::ops::Fn() + 'static`
    = note: required because it appears within the type `*mut core::ops::Fn() + 'static`
    = note: required because it appears within the type `core::marker::PhantomData<*mut core::ops::Fn() + 'static>`
    = note: required because it appears within the type `core::fmt::Void`
    = note: required because it appears within the type `&core::fmt::Void`
    = note: required because it appears within the type `core::fmt::ArgumentV1<'_>`
    = note: required because it appears within the type `[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `&[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `core::fmt::Arguments<'_>`
    = note: required because it appears within the type `SingleKV<core::fmt::Arguments<'_>>`
    = note: required because it appears within the type `(SingleKV<core::fmt::Arguments<'_>>, ())`
    = note: required because of the requirements on the impl of `SendSyncRefUnwindSafeKV` for `(SingleKV<core::fmt::Arguments<'_>>, ())`
note: required by `OwnedKV`
   --> src/lib.rs:3081:1
    |
3081| / pub struct OwnedKV<T>(
3082| |     #[doc(hidden)]
3083| |     /// The exact details of that it are not considered public
3084| |     /// and stable API. `slog_o` or `o` macro should be used
...   |
3088| | where
3089| |     T: SendSyncRefUnwindSafeKV + ?Sized;
    | |________________________________________^

error[E0277]: `*mut core::ops::Fn() + 'static` cannot be shared between threads safely
   --> src/tests.rs:255:5
    |
255 |     Logger::root(Discard, o!("foo" => ?n));
    |     ^^^^^^^^^^^^ `*mut core::ops::Fn() + 'static` cannot be shared between threads safely
    |
    = help: within `[core::fmt::ArgumentV1<'_>]`, the trait `core::marker::Sync` is not implemented for `*mut core::ops::Fn() + 'static`
    = note: required because it appears within the type `core::marker::PhantomData<*mut core::ops::Fn() + 'static>`
    = note: required because it appears within the type `core::fmt::Void`
    = note: required because it appears within the type `&core::fmt::Void`
    = note: required because it appears within the type `core::fmt::ArgumentV1<'_>`
    = note: required because it appears within the type `[core::fmt::ArgumentV1<'_>]`
    = note: required because of the requirements on the impl of `core::marker::Send` for `&[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `core::fmt::Arguments<'_>`
    = note: required because it appears within the type `SingleKV<core::fmt::Arguments<'_>>`
    = note: required because it appears within the type `(SingleKV<core::fmt::Arguments<'_>>, ())`
    = note: required because of the requirements on the impl of `SendSyncRefUnwindSafeKV` for `(SingleKV<core::fmt::Arguments<'_>>, ())`
note: required by `<Logger<D>>::root`
   --> src/lib.rs:1103:5
    |
1103| /     pub fn root<T>(drain: D, values: OwnedKV<T>) -> Logger
1104| |     where
1105| |         D: 'static + SendSyncRefUnwindSafeDrain<Err = Never, Ok = ()>,
1106| |         T: SendSyncRefUnwindSafeKV + 'static,
...   |
1112| |         }
1113| |     }
    | |_____^

error[E0277]: the trait bound `core::ops::Fn() + 'static: std::panic::RefUnwindSafe` is not satisfied in `(SingleKV<core::fmt::Arguments<'_>>, ())`
   --> src/tests.rs:255:5
    |
255 |     Logger::root(Discard, o!("foo" => ?n));
    |     ^^^^^^^^^^^^ the type core::ops::Fn() + 'static may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
    |
    = help: within `(SingleKV<core::fmt::Arguments<'_>>, ())`, the trait `std::panic::RefUnwindSafe` is not implemented for `core::ops::Fn() + 'static`
    = note: required because it appears within the type `*mut core::ops::Fn() + 'static`
    = note: required because it appears within the type `core::marker::PhantomData<*mut core::ops::Fn() + 'static>`
    = note: required because it appears within the type `core::fmt::Void`
    = note: required because it appears within the type `&core::fmt::Void`
    = note: required because it appears within the type `core::fmt::ArgumentV1<'_>`
    = note: required because it appears within the type `[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `&[core::fmt::ArgumentV1<'_>]`
    = note: required because it appears within the type `core::fmt::Arguments<'_>`
    = note: required because it appears within the type `SingleKV<core::fmt::Arguments<'_>>`
    = note: required because it appears within the type `(SingleKV<core::fmt::Arguments<'_>>, ())`
    = note: required because of the requirements on the impl of `SendSyncRefUnwindSafeKV` for `(SingleKV<core::fmt::Arguments<'_>>, ())`
note: required by `<Logger<D>>::root`
   --> src/lib.rs:1103:5
    |
1103| /     pub fn root<T>(drain: D, values: OwnedKV<T>) -> Logger
1104| |     where
1105| |         D: 'static + SendSyncRefUnwindSafeDrain<Err = Never, Ok = ()>,
1106| |         T: SendSyncRefUnwindSafeKV + 'static,
...   |
1112| |         }
1113| |     }
    | |_____^

I see. Thanks! Will look into it in 10 hours, I hope.


eclipse keymap ?

like,
[
{
"key": "ctrl+shift+c",
"command": "editor.action.commentLine",
"when": "editorTextFocus"
},
{
"key": "ctrl+d",
"command": "editor.action.deleteLines",
"when": "editorTextFocus"
},
{
"key": "ctrl+k",
"command": "editor.action.addSelectionToNextFindMatch",
"when": "editorFocus"
},
{
"key": "alt+shift+2",
"command": "workbench.action.splitEditor"
},
{
"key": "ctrl+shift+f",
"command": "editor.action.format",
"when": "editorTextFocus"
},
]

@rijine can you clarify please what you are asking for?

eclipse keybinding, so that i can use same keys in vscode also.
like, https://github.com/enlangs/vscode-eclipse-keybindings

You can change keybndings within VSCode, did you do that?

Please reopen if you need more help.


Bazel requires restart between intellij and CLI runs

Whenever I execute a Bazel command from the command line, and then using the IntelliJ plugin, it shows the following message and restarts.
WARNING: Running Bazel server needs to be killed, because the startup options are different.
Whatever I do, I can't seem to get these startup options exactly the same, even when I copy/paste the commands shown in the IntelliJ Bazel console.
I have also tried removing /etc/bazel.bazelrc and my workspace status command script.
My setup: Bazel 0.19.0, IDEA ultimate 2018.2.5, bazel plugin 2<IP_ADDRESS>.2, ubuntu 1804

You're likely launching the IDE with a different set of environment variables (at least one of which bazel is sensitive to).
Try launching the IDE from the same terminal you're running these commands in.

Yes, thank you!
JAVA_HOME was present in the shell but not in IntelliJ


[embedded] Mark embedded/array-zero-size-struct.swift as REQUIRES: optimized_stdlib

@swift-ci please smoke test and merge


Where can I find the original issues?

For example, https://code.google.com/p/android-test-kit/issues/detail?id=136

That's also the issue I'm looking for!

Everything was moved to b.android.com under Test-Support-Libraries
component:
bugs:
https://code.google.com/p/android/issues/list?can=2&q=label%3AComponent-Test-Support-Libraries label%3AType-Defect
features:
https://code.google.com/p/android/issues/list?can=2&q=label%3AComponent-Test-Support-Libraries+label%3AType-Enhancement&colspec=ID+Type+Status+Owner+Summary+Stars&cells=tiles
On Tue, Nov 24, 2015 at 8:36 AM, Eugenio Marletti<EMAIL_ADDRESS>wrote:

That's also the issue I'm looking for!
—
Reply to this email directly or view it on GitHub
https://github.com/google/android-testing-support-library/issues/9#issuecomment-159328282
.

But I remember that the issue I was referring to stated the following solution to some problem
configurations.all {
        resolutionStrategy.force 'com.android.support:support-annotations:22.2.1'
}

But I can't find any issue related to this topic.

This issue was fixed in the later version of the ATSL. Unfortunately,
old-fixed issues were lost during the migration. If you believe this issue
still exists please open a new bug under the new component in b.androd.com.
Thank you!
On Wed, Nov 25, 2015 at 11:48 PM, Guang Chen<EMAIL_ADDRESS>wrote:

But I remember that the issue I was referring to stated the following
solution to some problem
configurations.all {
resolutionStrategy.force 'com.android.support:support-annotations:22.2.1'
}
But I can't find any issue related to this topic.
—
Reply to this email directly or view it on GitHub
https://github.com/google/android-testing-support-library/issues/9#issuecomment-159839164
.

I'll close this as it's not an issue on the ATSL page (please use the mailing list).


it is still works?

subj

If you asking if library works. Yes it works.

Please note that Microsoft is phasing out Skype desktop API and your application is most likely going to stop to work with the future versions of Skype.


Support for parameters?

Is it possible to filter a URL based on a parameter it contains? Similar to how iOS 13 and later does?

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

ID: c7e251da-3cab-4aa0-2915-21189cf71bef
Version Independent ID: b244b311-a0e5-185d-df82-1dadf3fe6416
Content: Enable apps for websites using app URI handlers - UWP applications
Content Source: windows-apps-src/launch-resume/web-to-app-linking.md
Product: uwp
Technology: processes-and-threading
GitHub Login: @lastnameholiu
Microsoft Alias: alholiu

I don't believe so. This is our docs page and it doesn't mention it.
https://docs.microsoft.com/en-us/windows/uwp/launch-resume/launch-default-app
I would suggest you go to the Q&A Forum and ask your question again there.
-john


Typo "can ot"

There is a typo at the end of the documentation for Bitlocker Network Unlock. It should read "can not" but instead reads "can ot".
"recovery key to unlock the computer if it can ot be connected to the network."

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

ID: 6af3b9fa-46d2-0696-7c81-78c54b910e0f
Version Independent ID: 446e417c-6630-9673-dfa6-757511acde0c
Content: BitLocker Network Unlock FAQ (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/bitlocker/bitlocker-network-unlock-faq.yml
Product: w10
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@e0i, This issue #9750  can be closed safely now  . This issue has been solved


Make notification reporting more resilient

Why?
We had a customer report with the following stack trace:
Fatal Exception: java.lang.IllegalStateException: bundle.getString(BUNDLE_INSTANCE_ID_KEY) must not be null
       at com.pusher.pushnotifications.reporting.ReportingJobService$Companion.fromBundle(ReportingJobService.java:71)
       at com.pusher.pushnotifications.reporting.ReportingJobService.onStartJob(ReportingJobService.java:100)
       at com.firebase.jobdispatcher.JobService$2.run(JobService.java:164)
       at android.os.Handler.handleCallback(Handler.java:873)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:201)
       at android.app.ActivityThread.main(ActivityThread.java:6810)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

I'm not sure when this can happen, but these operations are best-effort, so we should fail silently if something is occasionally wrong for some reason.

@marekoid as discussed in person: the assumption on where the null pointer was, was correct but I've added a test to test it explicitly. With regards to the overly-defensive code, I've remove the extraneous return null for cases we don't expect and added the global try .. catch().

Closing this one out as we've decided to keep #98.


about the data imgsize

Sorry, I don’t understand very well. Why are the LR and HR images the same size?  How can I get a small LR in the real world?

Sorry, I don’t understand very well. Why are the LR and HR images the same size?  How can I get a small LR in the real world?

Similar dataset construction methods could be adopted. But you may need to modify the registration algorithm. Or you can try directly downsample the current LR.

Sorry, I don’t understand very well. Why are the LR and HR images the same size?  How can I get a small LR in the real world?

Similar dataset construction methods could be adopted. But you may need to modify the registration algorithm. Or you can try directly downsample the current LR.

Logically speaking, the size of the LR obtained by shooting should be small. Did you upsample it or downsample the HR? Why do you do that?

Sorry, I don’t understand very well. Why are the LR and HR images the same size?  How can I get a small LR in the real world?

Similar dataset construction methods could be adopted. But you may need to modify the registration algorithm. Or you can try directly downsample the current LR.

Logically speaking, the size of the LR obtained by shooting should be small. Did you upsample it or downsample the HR? Why do you do that?

Yes, traditionally super-resolution will increase pixels, in our case, maybe it is more closer to "digital zooming". The LR and HR have the same size because we adopt the registration algorithm in RealSR.

Sorry, I don’t understand very well. Why are the LR and HR images the same size?  How can I get a small LR in the real world?

Similar dataset construction methods could be adopted. But you may need to modify the registration algorithm. Or you can try directly downsample the current LR.

Logically speaking, the size of the LR obtained by shooting should be small. Did you upsample it or downsample the HR? Why do you do that?

Yes, traditionally super-resolution will increase pixels, in our case, maybe it is more closer to "digital zooming". The LR and HR have the same size because we adopt the registration algorithm in RealSR.

If registration is not performed, shouldn’t it be closer to the actual situation if the part corresponding to the HR in the captured LR image (large field of view) is directly cropped as an LR image? Do you still have the original data?

Sorry, I don’t understand very well. Why are the LR and HR images the same size?  How can I get a small LR in the real world?

Similar dataset construction methods could be adopted. But you may need to modify the registration algorithm. Or you can try directly downsample the current LR.

Logically speaking, the size of the LR obtained by shooting should be small. Did you upsample it or downsample the HR? Why do you do that?

Yes, traditionally super-resolution will increase pixels, in our case, maybe it is more closer to "digital zooming". The LR and HR have the same size because we adopt the registration algorithm in RealSR.

If registration is not performed, shouldn’t it be closer to the actual situation if the part corresponding to the HR in the captured LR image (large field of view) is directly cropped as an LR image? Do you still have the original data?

Maybe. But with more serious misalignment problem. Yes I have the original data and maybe I will provide them later.

Ok,thank you for reply


Weight Import Bug

I believe there might be a bug within pynetbox. When doing an import with a device that has the weight object defined, specifically with 2 decimal places, I keep experiencing the following error: {"weight":["A valid number is required."]}. I currently hold the belief that this error is directly related to either be a pynetbox issue or an upstream NetBox issue, but I am leaning towards pynetbox. I have already verified that the Weight model in NetBox is a DecimalField (with decimal_places=2).
I haven't confirmed or denied this, but @jsenecal and I tackled a seemingly similar issue in the devicetype-library when validating weight objects. You can reference this PR for more information but essentially we needed to add parse_float=decimal.Decimal to our json.loads() statement and create a custom loader (i.e. Loader=DecimalSafeLoader - see tests/yaml_loader.py in the devicetype-library for reference).
Here is some sample JSON of the data we are passing into the pynetbox dcim.device_types.create() function (the YAML can be found here): {'manufacturer': {'name': 'Datto', 'slug': 'datto'}, 'model': 'AP440', 'slug': 'datto-ap440', 'part_number': 'AP440', 'u_height': 0, 'is_full_depth': False, 'comments': '[Datto Access Points](https://www.datto.com/product-assets/wifi/AP840_840E_Datasheet_US.pdf)', 'weight': [{'value': 1.19, 'unit': 'lb'}], 'power-ports': [{'name': 'DC', 'type': 'dc-terminal', 'maximum_draw': 26}], 'interfaces': [{'name': 'Port 1', 'type': '1000base-t'}, {'name': 'Port 2', 'type': '1000base-t', 'poe_mode': 'pd', 'poe_type': 'type2-ieee802.3at'}, {'name': 'WiFi', 'type': 'ieee802.11ax'}]}
Please let me know if I can assist in any way or provide anymore information

We actually figure this issue out, so this can be ignored
See this discussion if you need more information


Azure - Added Stack Methods for list, exists, and delete

Added list_stack, stack_exist, and delete_stack to support Orchestration automation efforts for Shveta.  Cleaned up a few other returns while I was in there.
Thoroughly tested with these unit tests - http://pastebin.test.redhat.com/411048

Lint report for commit 3fb2ac097bafdd2aee9e397116fa034cb0725823:
mgmtsystem/azure.py:

:red_circle: Line 19:1: F401 'ActionTimedOutError' imported but unused
:red_circle: Line 174:9: N806 variable in function should be lowercase

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.
CFME QE Bot

Lint report for commit 63a37e72c26da0ccf74cea00988b17deae1d206d:
Everything seems all right from lint perspective :smile: .
Commit inspection report:
No commit flaws detected.
You have multiple commits in the PR. When you want your PR to be merged, please squash them. Do not squash them when working on the pull request as this allows to see the progress!
CFME QE Bot

Lint report for commit 574bed054060d0fdc685fe4411a5d7e1a7f13532:
mgmtsystem/azure.py:

:red_circle: Line 295:9: F841 local variable 'azure_data' is assigned to but never used

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.
You have multiple commits in the PR. When you want your PR to be merged, please squash them. Do not squash them when working on the pull request as this allows to see the progress!
CFME QE Bot

Lint report for commit c2398fe3a9c44da3abaa99481651d338a95ca341:
Everything seems all right from lint perspective :smile: .
Commit inspection report:
No commit flaws detected.
You have multiple commits in the PR. When you want your PR to be merged, please squash them. Do not squash them when working on the pull request as this allows to see the progress!
CFME QE Bot


fix(#2044): add disabled prop to datepicker

Before (the change)
Datepicker has no property disabled
After (the change)
Datepicker has the new property disabled
Make sure that you've checked the boxes below before you submit the PR

[x] I have read and followed the setup steps
[x] I have created necessary unit tests
[x] I have tested the functionality in both React and Angular.

Steps needed to test
React:
https://github.com/user-attachments/assets/70bbffdb-f0a3-4cbd-a5bd-2da5dbdb6421
import { GoAButton, GoADatePicker, GoAFormItem } from "@abgov/react-components";
import { useState } from "react";

export function Datepicker() {
  const [value, setValue] = useState<Date>(new Date(2024, 3, 26));
  const [disabled, setDisabled] = useState<boolean>(false);

  function onChange(name: string, value: Date) {
    console.log("onChange is triggered ", name, value);
    setValue(value);
  }

  function toggleDisabled() {
    setDisabled(!disabled);
  }

  return (
    <>
      <GoAButton mb="xl" onClick={toggleDisabled}>
        Toggle Disabled State
      </GoAButton>
      <GoAFormItem label="Item">
        <GoADatePicker
          onChange={onChange}
          name="item"
          value={value}
          disabled={disabled}
        ></GoADatePicker>
      </GoAFormItem>
    </>
  );
}

Angular:
https://github.com/user-attachments/assets/12e948d0-c6a1-43d7-8410-7231c8d551a6
<goa-button-group alignment="center" mb="xl">
  <goa-button (_click)="enableDatePicker()">Enable</goa-button>
  <goa-button (_click)="disableDatePicker()">Disable</goa-button>
</goa-button-group>

Angular form control

<goa-date-picker goaValue [formControl]="reactiveDate2FormCtrl"></goa-date-picker>

Event:

<goa-date-picker
  goaValue
  [formControl]="reactiveDate2FormCtrl"
  [attr.disabled]="disabled"
></goa-date-picker>

disabled = false;
reactiveDate2FormCtrl = new FormControl(new Date());
disableDatePicker() {
    this.reactiveDate2FormCtrl.disable();
    this.disabled = true;
  }

  enableDatePicker() {
    this.reactiveDate2FormCtrl.enable();
    this.disabled = false;
  }

I can't seem to disable the Date Picker in Angular using the provided code, nor any other combination of disabled and true

This issue is verified for react and angular

:tada: This PR is included in version 5.0.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.17.0-alpha.103 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-alpha.5 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


string false support

dont merge

Yes don't merge. (I merge)

https://github.com/Garlic-Team/GCommands/pull/15


Send output to local temporary file instead of standard output pane

Details
If there were a configurable option to send the output to a local temp file instead of,  or in addition to, the standard command pane, this would enable things like:

searching on the output (See also #75)
copy/paste output into another place
support for anything atom can do with a text file

See also

request for support for configurable output pane (#78)

I would recommend opening an issue with Atom to add search/copy support to all panes, since that seems to be the real blocker. There's no reason why Atom should not be able to treat any pane as text, which would remove the need for this option.

@lsegal Excellent, thanks for the lead.


[SDL 0202]-Supported Character Sets

Proposal: Supported Character Sets

This proposal introduces the ability for mobile apps to know what characters are supported by a head unit.

Review: https://github.com/smartdevicelink/sdl_evolution/issues/612
Steering Committee Decision:

The Steering Committee voted to fully accept this proposal on 2018-12-19. It was noted by the author that an OEM will support at least one of the character sets and if they support the entire UTF character set then they would implicitly support the other two as well.

Closed via https://github.com/smartdevicelink/rpc_spec/pull/265


Can't retrieve snippets data from REST API if URL rewriting is not working

Snippets plugin doesn't work in my site.
I can see the Snippet menu on the Manage page, but I cannot see the snippet option on the 'View issues' page. My issue seems like the https://github.com/mantisbt-plugins/Snippets/issues/23
I installed as below:

Snippets ver : 2.1.0  / Mantis BT ver : 2.9.0 / PHP ver : 7.1.12

Is there anything that I need to do?
  Try the fix in the PR:
https://mantisbt.org/bugs/view.php?id=23954

Hiya Thanks i have updated to 2.11 all working as expected


saving screenshot on osx get 1/2width&1/2height image

I modified the simple example to saving a screenshot on github.com, and get a 1/2width 1/2height image like:

The screenshot should be:

the code:
package main

import (
	"context"
	"io/ioutil"
	"log"

	"github.com/chromedp/cdproto/cdp"
	"github.com/chromedp/chromedp"
)

func main() {
	var err error

	// create context
	ctxt, cancel := context.WithCancel(context.Background())
	defer cancel()

	// create chrome instance
	c, err := chromedp.New(ctxt, chromedp.WithLog(log.Printf))
	if err != nil {
		log.Fatal(err)
	}

	// run task list
	url := `https://github.com/`
	sel := `div.col-md-7.text-center.text-md-left`
	pngFile := "screenshot.png"
	err = c.Run(ctxt, screenshot(url, sel, pngFile))
	if err != nil {
		log.Fatal(err)
	}

	// shutdown chrome
	err = c.Shutdown(ctxt)
	if err != nil {
		log.Fatal(err)
	}

	// wait for chrome to finish
	err = c.Wait()
	if err != nil {
		log.Fatal(err)
	}

	log.Printf("saved screenshot from `%s` (%s)", url, sel)
}

func screenshot(url, sel, file string) chromedp.Tasks {
	var buf []byte
	return chromedp.Tasks{
		chromedp.Navigate(url),
		chromedp.WaitVisible(sel, chromedp.ByQuery),
		chromedp.Screenshot(sel, &buf, chromedp.ByQuery),
		chromedp.ActionFunc(func(context.Context, cdp.Executor) error {
			return ioutil.WriteFile(file, buf, 0644)
		}),
	}
}

I am on macos 10.13.4 with Chrome Version 66.0.3359.181 (64-bit)
What's wrong? thx

Are you perhaps using a 4k (or other high density) display? If its exactly 1/2 in each direction, it sounds to me like a scaling issue. The fix to that would be to change the scaling in Chrome. You might want to look at the emulation domain, specifically the Emulation.setDeviceMetricsOverride call. Again, I'm only shooting in the dark here -- I don't really have an easy way to test this, as I don't have a Mac that's new-ish enough.
Also, keep in mind I'm only taking a stab in the dark as to what the problem is. Another way to test this hypothesis would be to go into the system settings and force a non-scaled UI.

Yes, my display is 2K(2560x1600).
I will try the Emulation.setDeviceMetricsOverride

How To Import Emulation For "Emulation.setDeviceMetricsOverride"

Hi, I stumbled on the same problem and managed to find a way, but it needs an update directly in chromedp. The trick is to use window.devicePixelRatio.
What I did locally is to patch this to get the DPI value from the browser (in js.go):
scrollJS = `(function(x, y) {
		window.scrollTo(x, y);
		return [window.scrollX, window.scrollY, window.devicePixelRatio];
	})(%d, %d)`

Then use it when cropping the PNG file returned by chrome (in query.go):
// crop to box model contents
cropped := imaging.Crop(img, image.Rect(
   (int(box.Margin[0])-pos[0])*pos[2], (int(box.Margin[1])-pos[1])*pos[2],
    (int(box.Margin[4])-pos[0])*pos[2], (int(box.Margin[5])-pos[1])*pos[2],
))

I will try when I find time to propose a PR. I don't have everything setup at the moment to properly run the tests.

@wuzuf are you still interested in sending a PR? To run the tests, all you need is having a somewhat recent version of Chrome installed. go test runs in about four seconds on my ultrabook. The PR should have a test as well.

Well, I don't have a Mac machine to test/debug this, and the issue seems to have stalled, so I'm closing for now. If anyone can reproduce this issue in master, even after using Emulation.setDeviceMetricsOverride, please open a new issue. Or even better, if you find a bug, send a PR.

@mvdan sorry for not following up on this comment. Actually, the tests are failing on OSX (as far as I remember, some tests with "keys", it seems chrome on osx has different behaviors when you use arrows to navigate into a dropdowns). So I gave up, as I could not find an easy way to make the tests pass.
Note that I suspect this will happen on any laptop with high density display, but won't know for sure. Good to keep this issue in your mind for future reference...

Yes, some of the input tests fail on Mac sort of by design, but we don't have access to a reliable Mac machine (like on CI) to test this on.
And actually, I can reproduce this on my 2560x1440 laptop (at 1.5x dpi, 144) with the following program on master:
// +build ignore

package main

import (
	"context"
	"io/ioutil"
	"log"

	"github.com/chromedp/chromedp"
)

func main() {
	ctx, cancel := chromedp.NewContext(context.Background(),
		chromedp.WithLogf(log.Printf))
	defer cancel()

	// run task list
	url := `https://github.com/`
	sel := `div.col-md-7.text-center.text-md-left`
	pngFile := "screenshot.png"
	if err := chromedp.Run(ctx, screenshot(url, sel, pngFile)); err != nil {
		log.Fatal(err)
	}

	log.Printf("saved screenshot from `%s` (%s)", url, sel)
}

func screenshot(url, sel, file string) chromedp.Action {
	var buf []byte
	return chromedp.Tasks{
		chromedp.Navigate(url),
		chromedp.WaitVisible(sel, chromedp.ByQuery),
		chromedp.Screenshot(sel, &buf, chromedp.ByQuery),
		chromedp.ActionFunc(func(context.Context) error {
			return ioutil.WriteFile(file, buf, 0644)
		}),
	}
}

It also errors out on master initially; I had to tweak some of the float math to get it to output the cropped screenshot.
I can now reproduce this on Linux, so at least the bug is verified and I can debug it.

Ok, this is now properly fixed. Please test it. I carefully wrote a test to verify that this works on my machine, so I'm pretty confident that the original issue is fixed.

I can confirm your test passes on my macbook. And your option to use directly chrome is of course great.
I had dropped what I was trying to do with chromedp, now it makes me willing to try again. Thanks for the fix!

I'm using chromedp.CaptureScreenshot() and it still has this issue.

@tmm1 if you share a way to reproduce your issue I can run it on my Mac to check.
On which OS/Go/chromedp versions are you?


Asyncio h11 (was #60)

this is a copy of #60 except rebased off of master and removes the commit from #62 so that this is only the change to h11. we can work off of this to drive h11 to completion without having the delayed import changes muddied in here... @denismakogon let me know if you have any preferences...

@denismakogon fixing this up... i'm gonna try to fix up some comments from #60 here today too... will hand off EOD

delayed import and h11 are separate features. that's fine, helps to communicate ;)

That’s why I wrote this twice in two different places: we need to merge code removal, then we need to merge delayed imports, then we replace aiohttp. That’s the most appropriate sequence of PR that need to be in master before making a release.

sounds good, didn't know which parts you have been working on, let me know if/which I can help with... it's not clear about breaking changes yet for either of these patches still too


Add L.setter

Codecov Report

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

@@          Coverage Diff          @@
##           master    #78   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         594    596    +2
=====================================
+ Hits          594    596    +2

Impacted Files
Coverage Δ

dist/partial.lenses.cjs.js
100% <0%> (ø)
: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 7866342...32d6619. Read the comment docs.


Handle literal string union complete pattern for JSX attribute snippets (<input type />)

There is well known pattern to workaround for https://github.com/microsoft/TypeScript/issues/29729 that is used in react on well known input type attribute:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/8ef783a008b722934e43c18669b33cf3b4e3be43/types/react/index.d.ts#L2199
in @types/react it is also being used on <a target> and role html attribute
@andrewbranch (probably stupid question) Since change is relatively small, do I still need to create standalone issue for this?

This looks good! Just run npx hereby runtests --tests 'Public API' and npx hereby baseline-accept and commit the result to update the baseline so tests pass.


approach/setting to control search space of a specific attribute

Is there any approach/setting to control the search space for value of some specific OP attributes?
For example, any approach to control kernel_size of Conv2d to be in range [1, 15]?
I tried to generate a model with conv2d and relu only, with max_nodes set to 100.
If the timeout_ms was set to 10000 (relativly small number) ms, the solver seems to find nothing, then model_gen failed with following errors.
If timeout_ms  set to 3000000 (a large number) ms, the entire model_gen process takes a very long time to generate a single model
  File "/venv/test/bin/nnsmith.model_gen", line 8, in <module>
    sys.exit(main())
  File "/venv/test/lib/python3.8/site-packages/hydra/main.py", line 90, in decorated_main
    _run_hydra(
  File "/venv/test/lib/python3.8/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
    _run_app(
  File "/venv/test/lib/python3.8/site-packages/hydra/_internal/utils.py", line 457, in _run_app
    run_and_report(
  File "/venv/test/lib/python3.8/site-packages/hydra/_internal/utils.py", line 222, in run_and_report
    raise ex
  File "/venv/test/lib/python3.8/site-packages/hydra/_internal/utils.py", line 219, in run_and_report
    return func()
  File "/venv/test/lib/python3.8/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
    lambda: hydra.run(
  File "/venv/test/lib/python3.8/site-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/venv/test/lib/python3.8/site-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/venv/test/lib/python3.8/site-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "/venv/test/lib/python3.8/site-packages/nnsmith/cli/model_gen.py", line 57, in main
    f"{len(gen.last_solution)} symbols and {len(gen.solver.assertions())} constraints."
TypeError: object of type 'NoneType' has no len()

For example, any approach to control kernel_size of Conv2d to be in range [1, 15]?

One ad-hoc way would be to add something like cons.append(nnsmith_le(kernel_h_size, 15)) around here https://github.com/ise-uiuc/nnsmith/blob/7b793ff0140392a6d79c4b9409520bac36509ae2/nnsmith/abstract/op.py#L1424

Recall that conv2d only accepts 4-dimension inputs. Because the graph generation is randomized in a way to start with a placeholder that has a random rank, as a result, it must be lucky enough to start with 4 to be able to generate conv2d.
This should be fixed by adding an extra argument for configuring the rank (length of its shape dimensions) of the starter placeholder (WIP).
For adding extra constraints, because we don't want to bother users by editing the source code, there is a way to systematically patch constraints at user level with the patch_requires decorator. See the TensorRT example:
https://github.com/ise-uiuc/nnsmith/blob/bdc2747a47cc0197f0bea0acc060bb8dde48228e/nnsmith/backends/tensorrt.py#L151
Probably something like:
@patch_requires(${THE_FACTORY_TYPE}$.system_name, "core.Pool2d")
def RulePool2d(self: AbsOpBase, _: List[AbsTensor]) -> List[Union[z3.BoolRef, bool]]:
    return [self.kernel_h_size <= 15, self.kernel_w_size <= 15]

Meanwhile for some good randomness of shapes, try to use other method="symbolic-cinit" in model_gen:
gen = model_gen(
    ...
    method: str = "symbolic-cinit", # or "concolic"
    ...
):

My apologies for the incomplete documentation and will be improving the doc soon (prob. next mon). For the rank issue there will be a patch soon and I will offer a colab example later today.
Meanwhile, for now please try to use the latest version with:
pip install "git+https://github.com/ise-uiuc/nnsmith@main#egg=nnsmith[torch,onnx]" --upgrade

This will provide a lot more features and possibly a better experience (in debugging etc.). Thanks!

Also, you might find the gist helpful: https://colab.research.google.com/drive/13LNQBvfpPFiaHWKnac6hxzvJY4LUAWWQ?usp=sharing

@jakc4103 You can try https://github.com/ise-uiuc/nnsmith/blob/main/doc/cli.md#add-extra-constraints with the latest nnsmith:
pip install "git+https://github.com/ise-uiuc/nnsmith@main#egg=nnsmith[torch,onnx]" --upgrade

Tks, this works.

Feel free to reopen if you still encounter any issues on this.


RHIROS-617 fixed default ordering to report date instead of name

Description
Fixed default ordering to report data instead of name
Jira: https://issues.redhat.com/browse/RHIROS-617
Demo
https://drive.google.com/file/d/1WT3QS8qr8olwu_lFTxKLz0iNGoINcVqG/view?usp=sharing

Thank you & congrats @PreetiW on 1st code contribution to backend repository :+1:
Thank you @r14chandra  for review!


Logging: Agreement Log

Description
With the EDC legally binding contracts are initiated by the negotiation process.
Impact

Additional information

[ ] I'm willing to contribute to this feature

Won't do in PI11

Hi @stephanbcbauer , I see two options here for the issue, either I close it, because I do not see it fit for further processing or you spend some effort in describing a bit the intention of the issue, so that we have a chance to understand the requirement. Would be nice, if you could indicate, which way to go! Thanks!

@lgblaumeiser this was an old issue. I was just the creator, ;) The information was provided by somebody else. Let's close this issue.


Support freeze for unmanaged objects to avoid: Unmanaged objects cannot be frozen

Goals

When an object is newly created, it is unmanaged and cannot make as freeze/frozen

After that object is saved into Realm Database, it becomes managed object can not thread-safe anymore so it cannot be used in another thread or Realm will throw an exception: Unmanaged objects cannot be frozen

In the previous Realm version, we often create/map JSON to RealmObject then pass to another thread. If we want to save them to the database, we have to create deep-copy by using extension Unmanaged function in this link https://github.com/realm/realm-cocoa/issues/5859

Manual create deep-copy is not as efficient as Realm built-in freeze/frozen.

api
  .rx.requestData()
  .mapObject(ResponseData.self)
  .do(onNext: { response in {
      RealmManager().save(response.deepCopy()) /// We have to make a here, often in `func save()` of RealmManager
  })
  .observeOn(SomeBackgroundScheduler)
  .subscribeNext { response in
      print(response.data)
  }

Expected Results
- Support to create freeze/frozen objects from the unmanaged objects.
Version of Realm and Tooling

Realm framework version: 5.2.0
Realm Object Server version: ?
Xcode version: 11.5
iOS/OSX version:
Dependency manager + version: Cocoapods

What would you expect freezing an unmanaged object to do?

@tgoyne I think when freezing an unmanaged object, the function will return a copy of object with a different reference address. Changing the original object (update, save to Realm) will no affect the copy one.


CSI 2.13 Release Checklist

IBM Storage Scale CSI Driver GA release Checklist

[x]  CSI snap works on Vanila k8s
[x]  Verify GitHub links are working - Shrutika
[x]  Verify IBM docs links are working - Shrutika
[x]  Pause dev checkin once stop-ship phase starts - All
[x]  Create Golden Master images on quay (Atleast 1 week before GA) - Hemalatha
[x]  Regression Complete - Saurabh
[x]  Realworld test complete
[x]  Check images for Vulnerabilities(Driver, Operator, sidecars)
[x]  IBM Docs Content Verification (1 week before GA) - All
[x]  Create git release tag (draft) with release content (1 week before GA)- Hemalatha
[x]  Merge dev into master (on GA date) - Hemalatha
[x]  Push multi arch images to quay (on GA date) - Hemalatha
[x]  Publish git tag (on GA date) - Hemalatha
[x]  Verify the images and yaml from release branch are correct - CLI install/Upgrade (on GA date) - Saurabh
[x]  Update driver listing https://kubernetes-csi.github.io/docs/drivers.html - Not Required

Done


Unable to retrieve system instance. Aborting with error -1012

I have a windows console application written in C using visual studio 2013. the application reference all the needed Spinnaker libraries.
Within Visual Studio I can retrieve system instance and extract Frame from all cameras connected. The problem happens when i try to deploy the application via Installshield. The executable return the above error when calling the spinSystemGetInstance function.
Can someone help me on this matter?

This is the repo for a ROS driver on linux.  I think you need to get help from the folks at FLIR.


feat: v4beta1 application support and proto sync

BREAKING CHANGE: In addition to the v4beta client features, this change also removes support for any string template paths relating to projectPath and companyPath, it now supports tenantPath and companyOldPath instead.

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:e3c054a2fb85a12481c722af616c7fb6f1d02d862248385eecbec3e4240ebd1e
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/cloud/talent/artman_talent_v4beta1.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/js/talent-v4beta1.
.eslintignore
.eslintrc.yml
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.jsdoc.js
.kokoro/common.cfg
.kokoro/continuous/node10/common.cfg
.kokoro/continuous/node10/docs.cfg
.kokoro/continuous/node10/lint.cfg
.kokoro/continuous/node10/samples-test.cfg
.kokoro/continuous/node10/system-test-grpcjs.cfg
.kokoro/continuous/node10/system-test.cfg
.kokoro/continuous/node10/test.cfg
.kokoro/continuous/node11/common.cfg
.kokoro/continuous/node11/test.cfg
.kokoro/continuous/node6/common.cfg
.kokoro/continuous/node6/test.cfg
.kokoro/continuous/node8/common.cfg
.kokoro/continuous/node8/test.cfg
.kokoro/docs.sh
.kokoro/lint.sh
.kokoro/presubmit/node10/common.cfg
.kokoro/presubmit/node10/docs.cfg
.kokoro/presubmit/node10/lint.cfg
.kokoro/presubmit/node10/samples-test.cfg
.kokoro/presubmit/node10/system-test-grpcjs.cfg
.kokoro/presubmit/node10/system-test.cfg
.kokoro/presubmit/node10/test.cfg
.kokoro/presubmit/node11/common.cfg
.kokoro/presubmit/node11/test.cfg
.kokoro/presubmit/node6/common.cfg
.kokoro/presubmit/node6/test.cfg
.kokoro/presubmit/node8/common.cfg
.kokoro/presubmit/node8/test.cfg
.kokoro/presubmit/windows/common.cfg
.kokoro/presubmit/windows/test.cfg
.kokoro/publish.sh
.kokoro/release/publish.cfg
.kokoro/samples-test.sh
.kokoro/system-test.sh
.kokoro/test.bat
.kokoro/test.sh
.kokoro/trampoline.sh
.nycrc
.prettierignore
.prettierrc
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
Skipping: README.md
codecov.yaml
renovate.json
synthtool > Replaced 'https:\\/\\/cloud\\.google\\.com[\\s\\*]*http:\\/\\/(.*)[\\s\\*]*\\)' in src/v4beta1/doc/google/protobuf/doc_timestamp.js.
synthtool > Replaced 'toISOString\\]' in src/v4beta1/doc/google/protobuf/doc_timestamp.js.
synthtool > Replaced '"https:\\/\\/www\\.google\\.com"' in src/v4beta1/doc/google/cloud/talent/v4beta1/doc_company.js.

><EMAIL_ADDRESS>install /tmpfs/src/git/autosynth/working_repo/node_modules/grpc
> node-pre-gyp install --fallback-to-build --library=static_library

node-pre-gyp WARN Using needle for node-pre-gyp https download
[grpc] Success: "/tmpfs/src/git/autosynth/working_repo/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node" is installed via remote

><EMAIL_ADDRESS>postinstall /tmpfs/src/git/autosynth/working_repo/node_modules/protobufjs
> node scripts/postinstall

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1107 packages from 1304 contributors and audited 6725 packages in 23.809s
found 3 vulnerabilities (1 low, 2 moderate)
  run `npm audit fix` to fix them, or `npm audit` for details

><EMAIL_ADDRESS>fix /tmpfs/src/git/autosynth/working_repo
> eslint --fix '**/*.js'

synthtool > Cleaned up 2 temporary directories.
synthtool > Wrote metadata to synth.metadata.

The doc failure here is because it's looking for a link that has yet to be committed to master. I'm pretty ignorant to Kokoro but it seems like we shouldn't be testing against master, but the branch being PR'd instead?
Aside from that, this is one hefty PR - it includes new features, breaking changes and what looks like some analytics code? I've updated the PR overview to include a mention of the breaking changes, so whoever merges should make sure it (or something similar) is included in the extended message.

The link I see failing - [404] https://github.com/googleapis/googleapis/blob/master/google/cloud/talent/v4beta1/resume_service.proto
is at the googleapis/googleapis repo. Since this generation is based off of it, we need to understand why it's missing there.

I see the problem now. Some files actually got removed since this generation:
	deleted:    protos/google/cloud/talent/v4beta1/resume_service.proto
	deleted:    src/v4beta1/doc/google/cloud/talent/v4beta1/doc_resume_service.js
	deleted:    src/v4beta1/resume_service_client.js
	deleted:    src/v4beta1/resume_service_client_config.json

But neither synthtool/gapic remove files that are not suppose to be there, we didn't catch that.
I had to rm -rf protos src/v4beta1 and run synthtool locally to see that they were removed.


[BUG]: Wrong type returned when using 'leftJoin' on a subquery using a 'mapWith'

What version of drizzle-orm are you using?
0.28.6
What version of drizzle-kit are you using?
No response
Describe the Bug
The following code reproduces the unexpected result:
import { eq, sql } from "drizzle-orm";
import {
  datetime,
  int,
  mysqlTable,
  serial,
  varchar,
} from "drizzle-orm/mysql-core";
import { db } from "~/server/db";

const usersTable = mysqlTable("users", {
  id: serial("id"),
  name: varchar("name", { length: 255 }),
});

const userEventsTable = mysqlTable("user_events", {
  id: serial("id"),
  userId: int("user_id").notNull(),
  event: varchar("event", { length: 255 }).notNull(),
  timestamp: datetime("timestamp").notNull(),
});

const lastEventTimestamps = db
  .select({
    userId: userEventsTable.userId,
    lastEventTimestamp: sql`MAX(${userEventsTable.timestamp})`
      .mapWith(userEventsTable.timestamp)
      .as("last_event_timestamp"),
  })
  .from(userEventsTable)
  .groupBy(userEventsTable.userId)
  .as("last_event_timestamps");

const [example] = await db
  .select({
    id: usersTable.id,
    name: usersTable.name,
    lastEventUserId: lastEventTimestamps.userId,
    lastEventTimestamp: lastEventTimestamps.lastEventTimestamp,
  })
  .from(usersTable)
  .leftJoin(lastEventTimestamps, eq(usersTable.id, lastEventTimestamps.userId));

if (example) {
  const unexpected = example;

  const expected = example as {
    id: number;
    name: string | null;
    lastEventUserId: number | null;
    lastEventTimestamp: Date | null;
  };
}

The typing of unexpected should match that of expected because it using a leftJoin. The issue seems to arise when using mapWith. The prop lastEventTimestamp does not have the possible type of null from the leftJoin like lastEventUserId does.
Thank you for any insight into this issue.
Expected behavior
The expected typing:

The returned typing:

Environment & setup
No response

From my understanding about left joins, left is "give me the left side and maybe the right side columns".
So this results seems expected.

The problem is that the return type of mapWith will dictate the type of that column.
TS will infer the return type of (value: any) => new Date(value) as a Date, even if value is null.
One workaround would be to do
.mapWith((value: any) => {
  if (value === null) return null;
  return new Date(value)
}


[Feature Request]: Support deleting data from the graph

Is your feature request related to a problem? Please describe.
In order to create a living knowledge base we need to be able to remove data that becomes outdated or that has been requested to be deleted
Describe the solution you'd like
Remove a document from the inputs folder and the associated data is removed from the graph and communities are rebuilt
Additional context
No response

yeah，good question

Consolidating index update requests with #741

This is a feature I need also. Rebuilding the graph after removing a document is not ideal.


https://uniqueten.net

Domain
https://uniqueten.net
Link
https://uniqueten.net/?link=KXNyT5
Version
0.0.0
What browsers are you seeing the problem on?
Brave
What OS are you seeing the problem on?
Windows
(Optional) Anything else?
No response
Code of Conduct

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

this is just leading to a rickroll


ISPSystem BillManager - list of api endpoints for hostings penetration tests

Source?

Source?

Parsed by me from that docs page https://docs.ispsystem.com/billmanager/developer-section/billmanager-api

So?

Lately things are moving slowly here.

Thanks for the pull request (and sorry for the delay!)


Allow non-image files in the gallery

I have a need for adding files that aren't images or videos to a gallery, specifically for pdfs and other media assets that may not be preview-able in a browser.  I'm wondering what the best way to go about this would be (I'm willing to make the modifications myself).
One option would be to make a plugin to handle "arbitrary" file types, and add a signal to hook into the file processing loop in Album.__init__().  This seems better than making a global class, as it should affect fewer people.
Thoughts @saimn?

A plugin with a new signal seems a good idea :+1:


basic check failed

I am writing a  program  to generate dynamic queries based on the input user given for a search. There the user select the field and defines the condition.So I cannot use parametarised queries. So I used your library
And am checking the user input field with SqlSafeUtil.isSqlInjectionSafe("my-string-value")
I have verified some condition such as TABLE,UPDATE ,DELETE etc in that util. all are working fine.
But one basic check "OR 1=1" fails and it return true status. Any solution?

okay. I shall check and get back with a solution soon

@shibinraj  can you show me what it is the string value that you are actually passing in to SqlSafeUtil.isSqlInjectionSafe()?
Then I can clearly know what's happening here.

no worries! understood the issue

@shibinraj. I have fixed it now  :-)
malicious data of the nature as below will not go through now.
                " OR false ",
                " OR true ",
                " and true ",
                " OR equals true ",
                " OR not equals true ",
                " OR equals false ",
                " and equals false ",
                " OR 1=1",
                " and 1=1",
                " OR column1=COLUMN1",
                " OR column1 = COLUMN1",
                " OR column1!=COLUMN1",
                " OR column1<>COLUMN1",
                " OR colu_mn1=COL_UMN1",
                " OR 'A'='A'",
                " OR '1afA'='2fadfA'",
                " OR 1=1 OR 2=2",
                " OR 1=1 and 2=2",
                " and 1=1 and 2=2",
                " and 1=1 or 2=2",

Thank you for the wonderful input.
This makes the library more efficient :-)

Feel free to use the latest version.
Feel free to let me know if you have anymore suggestions, issues or inputs
<dependency>
   <groupId>com.github.rkpunjal.sqlsafe</groupId>
   <artifactId>sql-injection-safe</artifactId>
   <version>1.0.1</version>
</dependency>

The files downloaded as in the following name in my maven repository.
sql-injection-safe-1.0.1.jar.lastUpdated
sql-injection-safe-1.0.1.pom.lastUpdated
I resolved it by changing the name.
Thank you for your update

I see that the jar is properly available in the nexus repository.
Anyway I shall check again. Thanks

But the import also showing error. I tried as follows
import com.github.rkpunjal.sqlsafe.SQLInjectionSafe;
import com.github.rkpunjal.sqlsafe.SqlSafeUtil;
the bold part showing the error
And I verified the downloaded jar  sql-injection-safe-1.0.1.jar .Its only having 1kb
but the version 1.0.0 have 7kb

Should be available now. Could you check now ? and let me know ...

remember to cleanup your old jars that you obtained by renaming ...

I have verified the Library. Now its working with the string " ' ' OR 1=1"  and all with you listed above.
But the string like UPDATE, DELETE etc which were working before showing error now. It return true while checking.  You missed something?

That's strange, because the unit-tests verify that and they pass.
Can you send me an example of your usage that is failing

the keyword UPDATE, DELETE etc I checked are failing

            "select adf from abc",
            "insert into abcd",
            "update abcd",
            "delete from abcd",
            "upsert abcd",
            "call abcd",
            "rollback ",
            "create table abc",
            "drop table",
            "drop view",
            "alter table abc",
            "truncate table abc",
            "desc abc",

these and variations of these are still being called as bad data.

only INSERT
or UPDATE
are not termed as malicious data

It were returning false before.
The statement 'select id' is also valid . If I put 'select id from' then it return false. Is it ok?

'select id' will be considered unsafe
so
SqlSafeUtil.isSqlInjectionSafe("select id")
will return false
and only INSERT, or only UPDATE, with nothing before and after that doesn't effect the data or db in any way. So it is considered as a safe data.
eg
insert into myTable(column1) values('INSERT');
This is a valid value and will does not result into sql injection of any kind.

still let me know if you have any concerns

'select id' is returning true for me. and if it is like 'select id from' it will return false

Okay, got your point. That's fixable, I shall fix it. Will msg soon.

Fixed this now.
Use the Latest :
<dependency>
  <groupId>com.github.rkpunjal.sqlsafe</groupId>
  <artifactId>sql-injection-safe</artifactId>
  <version>1.0.2</version>
</dependency>

Earlier 'select id from ...' and similar were considered malicious.
and 'select xx' was considered.
Hence created a new issue for this : https://github.com/rkpunjal/sql-injection-safe/issues/2
fixed it under that.
data like this will considered as malicious now
"select id",
"select 'abc'",
and
SqlSafeUtil.isSqlInjectionSafe("select id") shall return false now


Add announcement banner with link to blog

Ref:

It will be hidden on scroll.

actually, one more update - just a sec!


[SPARK-25348][SQL] Data source for binary files

What changes were proposed in this pull request?
Implement binary file data source in Spark.
Schema:

status (following Hadoop FileStatus):
** path: StringType
** modification_time: Timestamp
** length: LongType, size limit: 2GB
content: BinaryType

Options:

pathFilterRegex: only include files with path matching the regex pattern
[TODO] maxBytesPerPartition: The max total file size for each partition unless the partition only contains one file

How was this patch tested?
Unit test added.
Please review http://spark.apache.org/contributing.html before opening a pull request.

Test build #104531 has started for PR 24354 at commit 42d1fc9.

@mengxr
Discussion:

Change option name pathFilterRegex ? The hadoop glob do not support full regex syntax.
Figure out a proper way to implement option maxBytesPerPartition ? Current datasource will automatically determine the partition number but do not providing related interface to control it.
The option pathFilterRegex do we need to specify the full path filter ? Because in the spark.read.format(...).load(path) we has already specify the directory path, so the pathFilterRegex we could only specify the last part of the full path.

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

Test build #104533 has started for PR 24354 at commit 373af0f.

Test build #104534 has started for PR 24354 at commit a7aed42.

Merged build finished. Test PASSed.

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

Test build #104531 has finished for PR 24354 at commit 42d1fc9.

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

Merged build finished. Test PASSed.

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

Test build #104533 has finished for PR 24354 at commit 373af0f.

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

Merged build finished. Test FAILed.

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

Jenkins, retest this please.

Test build #104538 has started for PR 24354 at commit a7aed42.

Merged build finished. Test PASSed.

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

Test build #104534 has finished for PR 24354 at commit a7aed42.

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

Merged build finished. Test PASSed.

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

Test build #104538 has finished for PR 24354 at commit a7aed42.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #104556 has started for PR 24354 at commit 55a6858.

@cloud-fan @gatorsmile I think this PR is almost ready to merge. Could you make a pass?

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

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

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

Test build #104557 has started for PR 24354 at commit c3d4411.

Test build #104556 has finished for PR 24354 at commit 55a6858.

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

Merged build finished. Test PASSed.

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

Test build #104557 has finished for PR 24354 at commit c3d4411.

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

Merged build finished. Test PASSed.

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

I think we should follow avro and move it into the external directory.

@WeichenXu123, can you clarify why we need this source in the PR description? What's benefit over binaryFiles?

@HyukjinKwon We want to add it to Spark because it doesn't have any external dependencies like Avro / Parquet / ORC. The main use case is to ETL binary files like images.

Merged build finished. Test PASSed.

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

Test build #104600 has started for PR 24354 at commit b711773.

Merged build finished. Test PASSed.

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

Test build #104608 has started for PR 24354 at commit dda654a.

Test build #104600 has finished for PR 24354 at commit b711773.

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

Merged build finished. Test PASSed.

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

Test build #104608 has finished for PR 24354 at commit dda654a.

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

Merged build finished. Test PASSed.

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

https://github.com/apache/spark/pull/24354#issuecomment-483347794
Yup, this is fine to me. Wanted to make sure on our plan so that we don't go forth and back next time for new data source.

@WeichenXu123, can you update PR description to address https://github.com/apache/spark/pull/24354#issuecomment-482935464? Also, the schema looks not matched with the actual proposal.

@HyukjinKwon Done. Thanks!

Merged build finished. Test PASSed.

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

Test build #104613 has started for PR 24354 at commit aab4dcd.

Merged build finished. Test PASSed.

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

Test build #104614 has started for PR 24354 at commit 2b1780f.

Test build #104614 has finished for PR 24354 at commit 2b1780f.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #104613 has finished for PR 24354 at commit aab4dcd.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #104618 has started for PR 24354 at commit 2b1780f.

Test build #104618 has finished for PR 24354 at commit 2b1780f.

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

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

Test build #104634 has started for PR 24354 at commit 46a07e3.

@WeichenXu123 I sent you a PR at https://github.com/WeichenXu123/spark/pull/6 to address @HyukjinKwon 's comment on the docs.

Merged build finished. Test PASSed.

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

Test build #104637 has started for PR 24354 at commit dd8e8c6.

Test build #104634 has finished for PR 24354 at commit 46a07e3.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class BinaryFileFormat extends FileFormat with DataSourceRegister
class BinaryFileSourceOptions(

Merged build finished. Test PASSed.

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

Thanks, @WeichenXu123 and @mengxr for bearing with me. I'm okay with this.

LGTM. Merged into master. I created two follow-up tasks:

filter push down: SPARK-27473
user guide: SPARK-27472

Test build #104637 has finished for PR 24354 at commit dd8e8c6.

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

Merged build finished. Test PASSed.

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


Update Jira Supported Version 9.7.0

Hii Dhivya,
As per the your request I have verified SSO plugin compatibility with Jira 9.7.0 and also update the admin document.
Thanks & Regards,
Sagar Patil

@dhivyagana

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Upgrade-Banner inconsistency may be?

Upgrade-Banner says "This feature is currently available by invitation only." but it's not clear the feature it is refering to. Also, it points to a survey that is not active anymore.

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

ID: afebec12-9838-906e-1c0a-a435b9be3777
Version Independent ID: dec9bdde-ac60-4c13-72b5-b3709f6b7089
Content: Upgrade Dynamics AX 2012 to Dynamics 365 for Finance and Operations - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/migration-upgrade/upgrade-overview-2012.md
Service: dynamics-ax-platform
GitHub Login: @tariqbell
Microsoft Alias: tabell

Fixed, thanks!


Signs don´t translate jobs.

Signs doesn't translator jobs.

CONFIG SECTION:
*** FILE: generalConfig.yml ***
locale-language: es
*** FILE: jobs/hunter.yml ***
Hunter:
fullname: Cazador
shortname: H

Jobs version: <IP_ADDRESS>
Server Type (Spigot/Paper/etc): Spigot
Server Version (using /ver): 1.16.5

17005f2823e00245a621ffae88bd39b8fd8772a9


channel mapping grid pos

useful to have easy access to grid position (row,col) as well as absolute position (x,y) for the channel mappings. Maybe an optional output?

could add options to the load_chmap function to optionally return col, row instead of x, y:
return aopy.data.map_acq2pos(signal_path, layout, xpos_name='topdown_col', ypos_name='topdown_row')


Listing versions of a Blob

[Enter feedback here]
I understand how I can list blobs and get a blob with .NET, however I couldn't find any info about listing the past versions or snapshots made of a given blob?
Is there any way to do this via the .NET library, or maybe the REST API?
Thanks :)

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

ID: 49364b8c-01b5-5180-7537-c221c79d5b3d
Version Independent ID: 95ec5f30-8c53-b349-3b3c-71109ae84741
Content: List blobs with .NET - Azure Storage
Content Source: articles/storage/blobs/storage-blobs-list.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

@henkyfen In the REST API you can use List Blobs with include=versions. I am assigning this issue to the content author to consider adding a .net example for this.

@henkyfen - Thanks for your feedback!
I have added an example that shows how to list blob versions:
https://docs.microsoft.com/azure/storage/blobs/versioning-enable?#list-blob-versions
#please-close


Config not being saved into file

Hey there,
I'm using the 1.5.7 version of your mod, and it works fine so far.
The only thing I noticed is that the config is not being persisted.
Upon starting the game I have to set the sorting options and general options again.
I've checked my Documents\Mount and Blade II Bannerlord\Configs path, but there's no Mods folder or a PartyScreenEnhancements.xml.
In the log files I also couldn't find anything like PSE Config Load Exception.

Quick followup as I found out how to "fix" the problem:
You have to manually create the Mods folder.
I only had ModLogs and ModSettings maybe created by other mods.

Thanks for the report!
The issue is due to the new logging functionality I added in the latest version. The Directory.Create() call was being done after the logging initialization (which tries to create a file in the mod dir, which in your case wouldn't exist yet and thus throw an exception, canceling the latter Directory.Create() call).
Apoligies for the negligence, thankfully those exceptions are caught so should at worst be a minor annoyance.
I'll push a fix for it in a bit and it will be included in the next version.


Ensure optional subject in artifact manifest

Server-side issue: https://github.com/oras-project/distribution/issues/9

Closing as confirmed that subject can be null. (See https://github.com/oras-project/oras-go/blob/main/pack.go#L174 and https://github.com/oras-project/oras-go/blob/main/content/graph.go#L82-L84)


Update for RHEL7 STIG V3R1 Released 24 October 2020

V3R1 Release Notes:
Should these each have separate issues?

DISA migrated the Red Hat Enterprise Linux 7 STIG to a new content management system.  The new content management system renumbered all Groups (V-numbers) and Rules (SV-numbers).
With the new Group and Rule numbers, DISA incremented the version number from V2R8 to V3R1.
RHEL-07-010340 - Updated check content and finding statement to require documented authorized use of "NOPASSWD" or "!authenticate".
RHEL-07-020210, RHEL-07-020220, RHEL-07030000 - Downgraded to a CAT II.
RHEL-07-021031 - Added requirement to check that world-writable directories are owned by root, sys, bin, or an application account.
RHEL-07-021340 - Fixed typo in check text finding statement from "and" to "or".
RHEL-07-021350 - Updated check and fix text to verify existence of a key file for FIPS compliance.
RHEL-07-030210, RHEL-07-030211, RHEL-07030320, RHEL-07-030321 - Updated check text to allow for additional methods of audit log off-load.
RHEL-07-040730 - Generalized overall requirement to cover any graphical display managers.
RHEL-07-910055 - Added requirement to protect audit information.

N/A No Ansible changes - RHEL-07-020030, RHEL-07-020040 - Updated check text example output.
N/A No Ansible changes:  - RHEL-07-020111 - Added not applicable statement to the check text.
N/A No Ansible changes - - RHEL-07-010010 - Fixed typos in the check text command.
N/A No Ansible changes - - RHEL-07-021030 - Updated vulnerability discussion, check, and fix to elaborate possible group owners.

Thanks for the summary.  Usually we do checklists in the single issue per update, and check them off as they get done.

Thanks for the summary.  Usually we do checklists in the single issue per update, and check them off as they get done.

This response leaves me uncertain of the project position. Is the intent of the project owners to move the baseline forward to
RHEL7 STIG V3R1 Released 24 October 2020 ?
If so, how are you planning to manage that evolution? I have cycles I can devote to providing updates/fixes/changes if they are desired.

This response leaves me uncertain of the project position. Is the intent of the project owners to move the baseline forward to
RHEL7 STIG V3R1 Released 24 October 2020 ?
If so, how are you planning to manage that evolution? I have cycles I can devote to providing updates/fixes/changes if they are desired.

Hello,
I wanted to reach out and let you know that this issue will be closed on 2/23 (if everything stays on track). We have re-worked the role and want to start with a fresh issues list with this latest version. There was a post in the Ansible-Lockdown google group (https://groups.google.com/g/ansible-lockdown) with the details of the changes that are coming. Please checkout the thread titled RHEL 7 CIS and STIG Changes for all of the details, I also have the message pasted at below.
Please as you use the latest version open issue tickets as you find them, it is the best way for us to improve the role for everyone. Thank you for being part of the community and providing awareness of problems or advice on improvement. Reporting is a huge part of improving this project.
-George
Hello,
Thank you to everyone in the Ansible-Lockdown community who has contributed to RHEL7 STIG/CIS. Our team at MindPoint Group has been working with the entirety of the Ansible-Lockdown project, and we have some significant updates for both RHEL 7 STIG and CIS. With these updates, some larger changes have been made. I have these changes/updates outlined below.
Testing:

CI/CD - We have implemented some automated testing pipelines to test pull requests into the devel and main branches. With the current workflow, the community will PR into the devel branch (never the main branch) for review by the administrators. When your PR is created, the first check will remain the DCO check. The second check is a functional testing pipeline that will automatically perform a functional test of the branch the PR is initiated from. Once both tests pass, someone from the Administrator Team will review the changes and merge them into the devel branch. From there, an additional review is completed before the devel branch is merged into the main branch. Only the Admin Team will perform PRs/merges into the main branch. There is also an automated pipeline for PRs from devel to main. Please do not edit the .github/workflows files since those are used as part of the pipeline.

Compliance Checking – MindPoint Group has been working to create our own compliance audit scan tool. The tool uses a goss framework executable to run custom checks that we have created. The goal is to provide a more thorough check for control compliance and decrease the number of false positives/negatives. For example, it will check the configuration file related to the control and as well as checking if that configuration is active. With a smarter scan, we can hopefully identify attempts to trick scanners as well (for example stacking a parameter in a config file where the first instance is enabled and second disabled. Most audit tools search for the first instance but the application might look for the last instance of the parameter, thus making the scanning tool think it's enabled). In testing, we have found that our audit scan runs significantly faster than other audit tools, reducing audit times. Our audit tool and profiles will have their own repositories in the Ansible-Lockdown org, but within the remediation role there will be an integrated way to incorporate the audit. Keep an eye out for the audit tools as they are released. We plan on developing a goss audit profile for each current remediation role. Going forward, we plan to release a remediation role and goss audit tool profile simultaneously.

Role Updates:

RHEL 7 STIG/CIS – We have re-written much of the RHEL 7 STIG and CIS roles to increase clarity and readability and address some functionality items. We performed these updates while creating our goss testing framework for each of these roles. We plan on pushing our update to the devel and main branches. We will move the current devel and master branches to a devel_stable_ and master_stable_ branch in the respective repositories. Accordingly, community members who rely on the current version can still use that version going forward; this process will not remove what is currently there. The latest versions of the roles have also been updated to comply with the latest benchmarks.
Role Architecture – All roles will change with regard to the structure in the tasks folder. Taking CIS as an example, there will be a folder per section and yaml files for each sub-section. For example control 1.2.1 in CIS will be located in RHEL7-CIS/tasks/section_1/cis_1.2.x.yml. The cis_1.2.x.yml file will contain all controls related to section 1.2.x. This will hopefully make updates to roles a bit easier with less risk. This matches the architecture of our audit tool, creating consistency across remediation and audit platforms. The end goal is to repeat this architecture (the best we can) on STIG roles, but we are starting with CIS.
Existing PRs and Issues – With all of these changes comes the task of cleaning up existing PR’s and issues. Our plan is to close all of the existing PR’s and issues because of the re-work. Our team is growing and should be able to stay on top of the new issues and PRs as they come in.

Again, I would like to thank the community for your involvement in this project. The input and work from the community has contributed significantly to the success of this project. Please keep an eye out for these changes, which will be rolling out in the coming weeks.

Hello,
I wanted to reach out and let you know that this issue is being closed. We have re-worked the role and want to start with a fresh issues list with this latest version. There was a post in the Ansible-Lockdown google group (https://groups.google.com/g/ansible-lockdown) with the details of the changes that are coming. Please checkout the thread titled RHEL 7 CIS and STIG Changes for all of the details, I also have the message pasted at below.
Please as you use the latest version and open issue tickets as you find them, it is the best way for us to improve the role for everyone. Thank you for being part of the community and providing awareness of problems or advice on improvement. Reporting is a huge part of improving this project.

Hello,
Thank you to everyone in the Ansible-Lockdown community who has contributed to RHEL7 STIG/CIS. Our team at MindPoint Group has been working with the entirety of the Ansible-Lockdown project, and we have some significant updates for both RHEL 7 STIG and CIS. With these updates, some larger changes have been made. I have these changes/updates outlined below.
Testing:

CI/CD - We have implemented some automated testing pipelines to test pull requests into the devel and main branches. With the current workflow, the community will PR into the devel branch (never the main branch) for review by the administrators. When your PR is created, the first check will remain the DCO check. The second check is a functional testing pipeline that will automatically perform a functional test of the branch the PR is initiated from. Once both tests pass, someone from the Administrator Team will review the changes and merge them into the devel branch. From there, an additional review is completed before the devel branch is merged into the main branch. Only the Admin Team will perform PRs/merges into the main branch. There is also an automated pipeline for PRs from devel to main. Please do not edit the .github/workflows files since those are used as part of the pipeline.
Compliance Checking – MindPoint Group has been working to create our own compliance audit scan tool. The tool uses a goss framework executable to run custom checks that we have created. The goal is to provide a more thorough check for control compliance and decrease the number of false positives/negatives. For example, it will check the configuration file related to the control and as well as checking if that configuration is active. With a smarter scan, we can hopefully identify attempts to trick scanners as well (for example stacking a parameter in a config file where the first instance is enabled and second disabled. Most audit tools search for the first instance but the application might look for the last instance of the parameter, thus making the scanning tool think it's enabled). In testing, we have found that our audit scan runs significantly faster than other audit tools, reducing audit times. Our audit tool and profiles will have their own repositories in the Ansible-Lockdown org, but within the remediation role there will be an integrated way to incorporate the audit. Keep an eye out for the audit tools as they are released. We plan on developing a goss audit profile for each current remediation role. Going forward, we plan to release a remediation role and goss audit tool profile simultaneously.
Role Updates:
RHEL 7 STIG/CIS – We have re-written much of the RHEL 7 STIG and CIS roles to increase clarity and readability and address some functionality items. We performed these updates while creating our goss testing framework for each of these roles. We plan on pushing our update to the devel and main branches. We will move the current devel and master branches to a devel_stable_ and master_stable_ branch in the respective repositories. Accordingly, community members who rely on the current version can still use that version going forward; this process will not remove what is currently there. The latest versions of the roles have also been updated to comply with the latest benchmarks.
Role Architecture – All roles will change with regard to the structure in the tasks folder. Taking CIS as an example, there will be a folder per section and yaml files for each sub-section. For example control 1.2.1 in CIS will be located in RHEL7-CIS/tasks/section_1/cis_1.2.x.yml. The cis_1.2.x.yml file will contain all controls related to section 1.2.x. This will hopefully make updates to roles a bit easier with less risk. This matches the architecture of our audit tool, creating consistency across remediation and audit platforms. The end goal is to repeat this architecture (the best we can) on STIG roles, but we are starting with CIS.
Existing PRs and Issues – With all of these changes comes the task of cleaning up existing PR’s and issues. Our plan is to close all of the existing PR’s and issues because of the re-work. Our team is growing and should be able to stay on top of the new issues and PRs as they come in.
Again, I would like to thank the community for your involvement in this project. The input and work from the community has contributed significantly to the success of this project. Please keep an eye out for these changes, which will be rolling out in the coming weeks


Repo name sometimes contains organisation name

For some reason some responses for the name will contain the Org in the Repo name. For example Jamian/releasy instead of just releasy.

I've also added a fix for this issue in my pull request #1.
I'm checking if there is a slash in the repo name and then removing everything before it:
repo_name = repo['name'] if '/' not in repo['name'] else repo['name'].split('/')[1]


Automatically open autocomplete by passing latitude and longtitude

Is there a way to pass latitude and longtitude to the geocomplete input (get the lat and lng from HTML5 geolocation) and automatically open the suggestions dropdown?

Did you find a solution ? I am getting the same issue. I don't know how to deal with it.


Fix php version & improve dev structure

Hi, there's an issue where you can't install via composer if the PHP version is lower than 8.3.8, idk if that's intended or not.
I've added >=8.1.0 <8.4.0" as the required version to match the K4 php requirement.
Also, I've added some well-to-have config files :)

Hi @bogdancondorachi,
thank you for the input.
Of course I was not aware of all the improvements, will merge it.
Problem right now is, I don't have PHP 8.1.x installed.
Only 8.0.x and 8.3.8 - and that's the reason I have set requirements to PHP 8.3.8 :)
I can install PHP 8.1.0 next weekend to test, or... do you confirm it works with 8.1.0 ?
Then i'll merge asap (problably tomorrow).
Greetings

@swiegmann
Compatibility should be no problem between this versions as there's no braking changes happening between minor versions.
This way you allowe to install this plugin on any setup with versions between >=8.1 & <8.4 without restricting it to a specific version like 8.3.8


No datapoints found for container_cpu_usage_seconds_total

What did you do?
helm repo add coreos https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/
helm install coreos/prometheus-operator --name prometheus-operator --namespace monitoring
helm install coreos/kube-prometheus --name kube-prometheus.yaml --namespace monitoring

kubectl port-forward -n monitoring prometheus-kube-prometheus-0 9090
kubectl port-forward $(kubectl get  pods --selector=app=kube-prometheus-grafana -n  monitoring --output=jsonpath="{.items..metada.name}") -n monitoring  3000

type the query from Prometheus
container_cpu_usage_seconds_total{image!="",namespace="monitoring"}

What did you expect to see?
able to find container_cpu_usage_seconds_total from the dropdown, and the corresponding graph
What did you see instead? Under which circumstances?
No datapoints found.

Could you make sure that the kubelets are being successfully scraped? You can check this in the /targets page of the Prometheus UI.

Thanks, kubelets return 401, it should be the similar case as https://github.com/coreos/prometheus-operator/issues/976

Yes that was my suspicion :slightly_smiling_face:. We have some troubleshooting docs for this here: https://github.com/coreos/prometheus-operator/tree/master/contrib/kube-prometheus#troubleshooting
Let us know if that helps! :slightly_smiling_face:


Bring system test plugin inline with json schema plugin

Apply back lessons learned from json schema plugin to this system test plugin

renamed systemTest configuration to systemTestExecutor, as they'll later be systemTestComponent and systemTestExtension.
make use of @CartesianTest.MethodFactory to remove duplication in test code.

Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage remained the same at 97.917% when pulling c0497c09dadf0a222bd671913cd2130464751b27 on update into 8f7a4f6ff5804bf1f4a1503d60b9999f8f132c2a on main.


How to change the camera model from "SIMPLE_RADIAL" to "PINHOLE"?

How can i reconstruct one sfm model by hinpole in the holc.reconstruction?

model = reconstruction.main(..., image_options=dict(camera_model='PINHOLE'))

or via CLI:
python -m hloc.reconstruction [...] --image_options camera_model='"PINHOLE"'

See https://github.com/cvg/Hierarchical-Localization/pull/210.

Thinks a lot


Bring Data in SCLF into sync with the version in the overlay

@swift-ci please test

CC: @phausler

Typo in commit message (alining -> aligning) if you can amend the commit message.

@ianpartridge I corrected it ..
@parkera  Please review

@swift-ci please test

Can we get a review from someone appropriate - @phausler @parkera ?

@saiHemak this is just copied from the overlay, no additional changes?

@ianpartridge  ikesyo's changes were brought in to Swift Overlay recently. Initially the overlay had count changes .Hence ,initially when the PR was raised the latest master of Overlay had Count changes which caused the confusion.

@ianpartridge a day ago some more changes seems to be added to Data.swift am picking up those too ..

@swift-ci please test

@swift-ci please test

@parkera looks good to me, your or @phausler 's OK would be welcome.


Missing LICENSE

We are unable to use this in our corporate environment unless there's a license.
Fixed by #31

Done!


Add a bunch more UNDEFINED_CONSTANTS for startup.

This should avoid these getting included globally in future.
I found this list from a combination of https://github.com/Homebrew/brew/pull/17707/files, looking at the Gemfile and just looking around myself.

Thanks for review @carlocab!


start/close streams in parallel on new worker metadata

Previously, StreamingEngineClient would start and close streams after getting new worker metadata synchronously (close 1 stream at time, open 1 stream at a time).
Make this happen in parallel and run async only blocking when needed.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @scwhittle

Hey @m-trieu, can you resolve some of the merge conflicts then tag Sam again?


MSI X399 SLI Plus

would be nice if you could add this board.
msi-rgb 0 0 0 --print-current
Bank 12 (d0...100):
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
e0 00 00 00 00 00 00 00 ff ff 11 00 04 34 01 40
00 00 00 00 ff ff ff ff 00 00 00 00 00 00 19 02
Bank 09 (20...40):
d3 52 ff 00 00 00 40 03 00 ff 58 01 11 00 00 13
0f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 0b (60...70):
0a 20 0a 40 00 00 ff ff ff ff ff ff ff ff ff ff

If you need any specific output to help, feel free to answer her :)

Mystic Light seems to be very different from the RGB control implemented here, so without direct access to hardware I won’t be able to do anything here.

if you live near germany (hamburg) I could give you access to it :D

Alas.

so what exactly has to be done to get the required information for you?
I would help as much as possible

Short of implementing the functionality yourself, probably nothing.
I’m most likely not buying MSI hardware ever again, so unless I’m donated some with "Mystic Light" support specifically for work on this tool, I’ll never get to implementing this support.