Error Running the HairFastGAN

Received this error:
(venv) G:\HairFastGAN>python main.py
No CUDA runtime is found, using CUDA_HOME='C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.8'
G:\HairFastGAN\venv\lib\site-packages\torch\utils\cpp_extension.py:358: UserWarning: Error checking compiler version for cl: [WinError 2] The system cannot find the file specified
warnings.warn(f'Error checking compiler version for {compiler}: {error}')
Traceback (most recent call last):
File "G:\HairFastGAN\main.py", line 9, in
from hair_swap import HairFast, get_parser
File "G:\HairFastGAN\hair_swap.py", line 13, in
from models.Alignment import Alignment
File "G:\HairFastGAN\models\Alignment.py", line 8, in
from models.Encoders import RotateModel
File "G:\HairFastGAN\models\Encoders.py", line 9, in
from models.Net import FeatureEncoderMult, IBasicBlock, conv1x1
File "G:\HairFastGAN\models\Net.py", line 9, in
from models.stylegan2.model import Generator
File "G:\HairFastGAN\models\stylegan2\model.py", line 11, in
from models.stylegan2.op import FusedLeakyReLU, fused_leaky_relu, upfirdn2d
File "G:\HairFastGAN\models\stylegan2\op_init_.py", line 1, in
from .fused_act import FusedLeakyReLU, fused_leaky_relu
File "G:\HairFastGAN\models\stylegan2\op\fused_act.py", line 10, in
fused = load(
File "G:\HairFastGAN\venv\lib\site-packages\torch\utils\cpp_extension.py", line 1284, in load
return _jit_compile(
File "G:\HairFastGAN\venv\lib\site-packages\torch\utils\cpp_extension.py", line 1508, in _jit_compile
_write_ninja_file_and_build_library(
File "G:\HairFastGAN\venv\lib\site-packages\torch\utils\cpp_extension.py", line 1610, in _write_ninja_file_and_build_library
_write_ninja_file_to_build_library(
File "G:\HairFastGAN\venv\lib\site-packages\torch\utils\cpp_extension.py", line 2014, in _write_ninja_file_to_build_library
cuda_flags = common_cflags + COMMON_NVCC_FLAGS + _get_cuda_arch_flags()
File "G:\HairFastGAN\venv\lib\site-packages\torch\utils\cpp_extension.py", line 1780, in _get_cuda_arch_flags
arch_list[-1] += '+PTX'
IndexError: list index out of range

You need to try
pip3 install torch=1.13.1 torchvision=0.14.1 --index-url https://download.pytorch.org/whl/cu118

好像还是不行

Try without specifying the version like below if someone gets stuck on this
pip3 install torch torchvision --index-url https://download.pytorch.org/whl/cu118

I didn't check for problems that could occur from the version mismatch (it will update PyTorch to 2.X.X), but at least I was able to run the demo.

Thank you for reporting this issue. I apologize for the inconvenience you're experiencing while trying to run the method.
Based on the error message you provided, it appears that there's a CUDA configuration problem on your Windows system, which is preventing the ninja build process from completing successfully.
To resolve this, I recommend using Windows Subsystem for Linux (WSL). This approach has been tested by our team and should help avoid environment-related issues. Here's a step-by-step guide to get you started:

Install WSL following the instructions at: https://learn.microsoft.com/en-us/windows/wsl/install

Once WSL is set up, install Python 3.10 within your WSL environment.

Use poetry to install all required packages. This will ensure a consistent and isolated environment for the project.

Try running the method again within this WSL environment.

If you encounter any difficulties with this process or if the error persists after following these steps, please don't hesitate to reach out. Provide details about any new errors or issues you face, and I'll be glad to assist you further.


chore(rust): fix no_std compilation due to ockam::node attribute

While working in #2213 I found that the compilation of no_std examples were failing due to problems with the ockam::node attribute

Current Behaviour
When doing:
cd implementations/rust/ockam/ockam_examples/example_projects/no_std/
cargo run --example hello --no-default-features --features="alloc, no_std"

I got the error:
error[E0308]: `?` operator has incompatible types
  --> examples/hello.rs:45:1
   |
45 | #[ockam::node]
   | ^^^^^^^^^^^^^^ expected enum `Result`, found `()`
   |
   = note: `?` operator cannot convert from `()` to `Result<(), ockam::Error>`
   = note:   expected enum `Result<(), ockam::Error>`
           found unit type `()`
   = note: this error originates in the attribute macro `ockam::node` (in Nightly builds, run with -Z macro-backtrace for more info)
help: try removing this `?`
   |
45 - #[ockam::node]
45 + #[ockam::node
   |
help: try using a variant of the expected enum
   |
45 | Ok(#[ockam::node])
   |

For more information about this error, try `rustc --explain E0308`.
error: could not compile `hello_ockam_no_std` due to previous error

The same happened when running the example with any of the feature flags corresponding to no_std
Proposed Changes
The reason for this is that the node attribute returns the result from Executor::execute and it either unwraps the result or attach a ? depending on the return type of main.
This works well for std where the return type of execute is Result<F::Output> where F::Output is the return type of main, so if the return type of main is Result<()> the return type of execute is Result<Result<()>> and applying the ? operator we get a Result<()>.
However, for no_std the return type of execute is Result<()> so applying the ? operator to Result<()> we get a () which doesn't match with the return type of a main Result<()>, so in the no_std case I simply changed it to let the attribute return the result from execute verbatim.
This also means that Ockam::node in no_std will only work with no return type or Result<()> but since there is a TODO for execute to be unified with the std case that'll be solved, there's also no option to make it compatible with any other return type since the execute function as is now consume any type returned from main by unwrapping it and returning Ok(())
Checks

[x] All commits in this Pull Request are signed.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor Licence Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the ockam-network/contributors repository. (Created PR: ockam-network/contributors#56 )

Merged in https://github.com/ockam-network/ockam/pull/2364
@conectado Thank you and congratulations on your first Ockam contribution! 🎉


Support for multiple apps / Clarification

Thanks for this awesome package.
I have the following scenario and was wondering if it's possible to implement it currently or if there is any plan to support it. Basically what I am looking for is a way to do either one of the following:

Reconfigure Push with a different configuration.
Support for multiple configurations.
Let each individual Meteor app handle their associated notifications based on the user.

I have the following setup:

Multiple Meteor apps running on the same server.
All connect to the same database.
Two separate mobile apps.
The apps must be able to send notifications to each other.
Each app represents a different type of user.

So basically something like this:

A site.
A mobile app for Android.
A mobile app for iOS.
B site.
B mobile app for Android.
B mobile app for iOS.
C site.

And I want to be able to do this:

A must be able to send notifications to A and B.
B must be able to send notifications to A and B.
C must be able to send notifications to A and B.

Currently I have this:

Server A is setup to handle notifications for app A.
Server B is setup to handle notifications for app B.

So I can send notifications A->A and B->B, but how to send A->B?
Ideally server A would create the notification and then server B would process it.

you could add an endpoint for the server communication
or
use the same collection for all apps for the push collections (app + notifications)

Thank you for your help.
I understand your first suggestion, but the second one I'm having trouble understanding how it would work.
Currently all apps use the same collection (they all share the same database) and each app is configured with different certificates.
If I need to send notifications to multiple devices from one of the apps, how would that work on your second suggestion?

ah ok, at the moment this package doesn't support multiple certificates so creating an endpoint might be the best option

Since all apps share the same database what I ended up doing was the following:

Created a job queue collection.
To send a notification insert a new document in the collection with an app ID and data for the notification.
Each app listens for changes on the collection and filters on app ID, sending the data to Push.send when it finds a new document.

In this way each app can have its own configuration and we communicate between apps so that the proper one sends the notification.


Small documentation changes

Change description
Updates and corrects some docs.  Small tweak to how docs are created.
What problem does this solve?
Alex...
Issue number: (if applicable)
Example usage
Additional details and screenshots
Checklist

[ ] I have added unit tests to cover my changes.
[ ] I have added documentation to cover my changes.
[ ] My changes have passed unit tests and have been tested E2E in an example project.

Pull Request Test Coverage Report for Build 501aee13577237bec33b497613e6ceb66bb7e954-PR-22

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 76.36%

Files with Coverage Reduction
New Missed Lines
%

lib/prom_ex/plugins/application.ex
1
88.57%

Totals

Change from base Build 492853a4e9f80524715762a6e671a3f207b1a9aa:
0.0%

Covered Lines:
365

Relevant Lines:
478

💛  - Coveralls

This is awesome!!! Thanks :)


KOGITO-736: Adding links to external editor

Adding links to external online editor.
This is how it looks like:

This feature in action:

This is really great! I think a better icon for this use would be the external link icon () since it takes you to a separate webpage.

Thank you, @kywalker-rh I changed the icon to arrow

Sometimes looks like there's some sort of cache on github DOM that does not allow the extension to work at first time a repo is rendered. I will rebase this PR and check the issue with more details

Hello @tiagobento  - thank you so much for your review. I made changes to the code and also effectively observed the files container for changes.
Thanks!

ops, added my changes to the last commit by mistake, but the changes are in https://github.com/kiegroup/kogito-tooling/pull/62/commits/76fc0774c82a3bfdd3cff0078e5d2088d92a68a4
would you please review?


HDInsight Job SDK 2.0.0 Pre-release changes

Can one of the admins verify this patch?

Hi @pattipaka, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (supattip). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci add to whitelist


Issue with multipart/form-data post and json.net deserializtion (using interfaces)

We use the aspnetcore 2.
We have configured JsonOptions in startup like this.
services.AddMvc().AddJsonOptions(options =>
            {
                options.SerializerSettings.ContractResolver = new DefaultContractResolver();
                options.SerializerSettings.Converters = new List<JsonConverter> {
                    new JsonDocumentConverter(),
                    new JsonDocumentMetaConverter(),
                    //new Bll.FileRecords.JsonDocumentMetaListConverter(),
                };
            });

public class JsonDocumentConverter : CustomCreationConverter<IDocument>
    {
        public override IDocument Create(Type objectType)
        {
            return new LocalDocument();
        }
    }
public class JsonDocumentMetaConverter : CustomCreationConverter<IDocumentMeta>
    {
        public override IDocumentMeta Create(Type objectType)
        {
            return new LocalDocumentMeta();
        }
    }

In our controller we have 2 methods

The first one is called PostUrlencoded in which we make a http post request with content-type : application/x-www-form-urlencoded.

[HttpPost("PostUrlencoded")]
public async Task<IActionResult> PostUrlencoded([FromBody]IDocument document)
{ /*...*/ }

2.. The second one is called PostΜultipart in which we make a http post request with content-type : multipart/form-data.
[HttpPost("PostΜultipart")]
public async Task<IActionResult> PostΜultipart([FromForm]IDocument document)
{ /*...*/ }

The first method works fine, and the deserialization works fine. In the second method deserialization fails.
The error is:
Model bound complex types must not be abstract or value types and must have a parameterless constructor.
That's because the JsonOptions isn't applied.
When we remove the jsonOptions from the startup.cs, we get the same error in both cases.

I was hoping this would have worked with either [FromForm] or automatically.
Is there any reason why it doesn't?
I can send multiple IFormFile in a similar way and they get picked up without problems, why doesn't this?
------WebKitFormBoundaryuBv1RMQSgoCHMWae
Content-Disposition: form-data; name="news"
Content-Type: application/json

{"title":"title1","text":"text1"}

public async Task<IActionResult> PostNews([FromForm]News news, IFormFile attachment = null, IFormFile image = null)
{
...
}

I guess I can just do something like this, but this feels REALLY clunky.
public async Task<IActionResult> PostNews(IFormFile news, IFormFile attachment = null, IFormFile image = null)
{
	if (news != null && news.ContentType == "application/json")
	{
		News newsObject = null;

		var js = new JsonSerializer();
		using (var ms = new MemoryStream())
		{
			await news.CopyToAsync(ms);
			ms.Seek(0, SeekOrigin.Begin);

			using (var sr = new StreamReader(ms))
			using (var jtr = new JsonTextReader(sr))
			{
				newsObject = js.Deserialize<News>(jtr);
			}
		}
	}
}

I knew someone else would say something about this. I expect more reactions.
It was pretty authoritarian the way this was closed.

Reopening this issue as there seems to be some customer interest in this being a first-class experience.
Will track this as part of the 3.0 milestone.

I guess what we are looking for is something similar to this https://stackoverflow.com/questions/41367602/upload-files-and-json-in-asp-net-core-web-api
Where we want the parameter in [FromBody] to be parsed using a jsonbinding/serialization.


tiff: does not consistently convert UTF-8 quotes to ASCII in docs

Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible-builds.org/ .
Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems.
Steps To Reproduce
nix-build '<nixpkgs>' -A tiff.doc --check --keep-failed

You can use diffoscope to analyze the differences in the output of the two builds.
To view the build log of the build that produced the artifact in the binary cache:
nix-store --read-log $(nix-instantiate '<nixpkgs>' -A tiff)

Additional context
it seems (https://reproducible.nixos.org/nixos-iso-gnome-runtime/diff/e0d89c3c9c4c52083c726a2c0bdcc6166e48c9b11f23d08c7aa544e585050917-5609f1850fa5ee67250ed23fd4ac56065e0f51e850e07f6b2460ba19973c9a42.html) the documentation generation is not consistent in whether it creates UTF-8 quotes (’) or regular ASCII ones (')

(this is not showing up in the latest report, may have been fixed or not reproducibly unreproducible)

I'm 90% sure this failure was caused by the html/man pages being built in parallel while sharing a sphinx doctree. My understanding is that one builder (html) uses the smartquotes transformation, the other (man) doesn't, and both builders try to write that result to the doctree in parallel, causing the nondeterminism. This was actually fixed by libtiff upstream in their cmake configuration, but we don't use that in nixpkgs because it doesn't support cross compile as well as the autotools configuration does (or at least that was the case two years ago).
This is a known issue with sphinx:
sphinx-doc/sphinx#3967
sphinx-doc/sphinx#4371
sphinx-doc/sphinx#2946
The only problem with that hypothesis is that I can't reproduce the bug. I also can't find anything that would have fixed this. Not in libtiff, not in sphinx, not in docutils. If it pops up again, I can report it upstream and send a patch.


DataSequence filter by list of values.

Description
No response

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/144


The get_transcript method is not working in production.

I'm using the get_transcript method in my Django app that I've deployed using pythonanywhere, but the method is raising the VideoUnavailable error, even though the same script is working fine locally.

I am not offhand sure what is going wrong for you, but it seems like it may be related to #60. Basically Youtube may be rate limiting pythonanywhere's IPs.

I see, I guess I'll have to choose a different hosting platform. Thanks, @danielcliu!


[BUG] tests fail with unicode-width 0.1.12 but not with 0.1.13 (should we support both in tests too?)

Describe the bug
tl;dr: some tests still fail for users that had old git clone and didn't cargo update after git pull, even though the lib works as intended.
But since the lib can handle control chars of either width 0 or 1, should I mod the currently failing tests to handle both width 0 or 1 ? and should I do it without introducing a build.rs ? or just do nothing and thus allow tests to catch when width is != 1 in the future ?

In this commit:
https://github.com/gyscos/cursive/commit/af7c3d7b5a5ce65ef90a12260a8f7c6477fa6c20
I see the intention was as you've mentioned:

I cherry-picked the last commit (just removed the \0 width test, so we're not tied to unicode-width 1.1.13)

in other words, you wanted it to work with either 0.1.12 or 0.1.13 (but also for tests to not fail as well), as you've mentioned here also:

The crash should now be fixed with the latest commit, which ignores \0 (when using unicode-width < 0.1.13), or replaces it with � (when using unicode-width >= 0.1.13).

however, with unicode-width 0.1.12, all control chars have width 0 (I've just tested) therefore this whole test(which already covers \0 as well) will fail:
https://github.com/gyscos/cursive/blob/332a6a4bff93f9b2d5e9540e9cc3af43e42e636e/cursive-core/src/utils/lines/spans/tests.rs#L32-L61
so not just the test for \0 that got removed in the aforementioned commit.
I'm not sure(unless add build.rs[^1]) how to conditionally make the test depend on 0.1.12 and check for width 0, and also if >=0.1.13 check for width 1, but the initial intent was that if the assumed width changes in a future unicode-width update, we should have tests fail, else we wouldn't know that bugs creep in due to width being different now (such as: sizes and shadows being off), even though the lib can current handle both widths: 0 or 1. Maybe given this, can mod the test for width being < 2 but there's the test below which might need some tweaking too(if build.rs introduction isn't wanted).
Alternatively, maybe it doesn't matter in this case that the cargo test will fail for users which just git pull-ed new changes(due to them having their own Cargo.lock locally, because it's in .gitignore), because, while this test fails, the lib does work as expected, and the user is in fact expected to cargo update anyway.
Additionally this test will fail too, for those users that didn't cargo update to get unicode-width 0.1.13: $ cargo test --example select_test -- --nocapture, in particular tests::control_chars_become_replacement_char and tests::nuls_become_replacement_char.
But again, all the mentioned tests only fail for users that didn't cargo update, not for anyone who did a fresh git clone for example. And we kinda want these tests to fail to catch future width changes, I'd think.
[^1]: without introducing a build.rs(which would set an expected width(based on unicode-width version, so it would be either 0 or 1) in a new .rs that we'd include!() and thus can use that in the test). I'd be happy to do it, if you'd just let me know that you want this.
To Reproduce

git clone
force use unicode-width 0.1.12

diff --git a/cursive/Cargo.toml b/cursive/Cargo.toml
index 3a26f0b..810edc0 100644
--- a/cursive/Cargo.toml
+++ b/cursive/Cargo.toml
@@ -19,7 +19,7 @@ cursive_core = { path = "../cursive-core", version= "0.3.0"}
 crossbeam-channel = "0.5"
 cfg-if = "1"
 unicode-segmentation = "1"
-unicode-width = "0.1"
+unicode-width = "=0.1.12"
 lazy_static = "1"
 libc = "0.2"
 maplit = { version = "1.0", optional = true }

cargo update
cargo test test_control_chars_have_width_1 -- --nocapture
cargo test --example select_test -- --nocapture

Expected behavior
for users with stale Cargo.lock, tests wouldn't fail.
Screenshots
N/A
Environment

Operating system used
Backend used: ncurses (the default one)
Current locale (run locale in a terminal)

LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=

Cursive version (from crates.io, from git, ...)
latest commit which currently is: https://github.com/gyscos/cursive/commit/332a6a4bff93f9b2d5e9540e9cc3af43e42e636e

Additional context
nits: I forgot to mention that in commit in code comments, it's unicode-width instead of unicode-segmentation(which is at 1.11.0 and has no effect on width, from what I can tell)

I'll make a proof-of-concept PR that shows how it would look like if the tests supported both widths (0 and 1) because the lib already does (and without needing a build.rs), it doesn't have to be merged, but it can be if this version of handling the issue is chosen.


Feature/income

What has changed and why?
Allowed the manual entry of income
Split the address / dependants / income into their own speech bubbles.
How to test this change
choose the "somewhere in between" option for income, then enter your income

[ ] has automated tests
[ ] at least one a reviewer ran the code
[ ] tested in small screen
[x] tested in Chrome
[x] tested in Firefox
[ ] tested in IE
[ ] tested in Safari
[ ] i18n
[ ] tested in screen reader/contrast <-- remove this if no UX change

i'm gonna merge this one becaue the feedback was address. hoping it's all ka pai


Can't change display mode because of Accents

Microsoft PowerToys version
0.70
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Quick Accent
Steps to reproduce

open Nvidia panel
change display mode from Nvidia card to integrated one

✔ Expected Behavior
The display mode should change
❌ Actual Behavior
I get an error message saying display mode can't be changed because of power toys accents

Other Software
No response

Reference : https://github.com/dotnet/wpf/issues/9286


ModuleNotFoundError: No module named 'folder_paths' during extension installation

I am encountering an error ModuleNotFoundError: No module named 'folder_paths'. I followed the installation instructions, but the issue persists.

UPD: Removing the extension and reinstalling it helped me, everything is fine.

Navigate to stable-diffusion-webui\extensions\a-person-mask-generator in a cmd window and run git pull then try again


Presort pairWiseElemsOfSameType argument

Sorting the argument to pairWiseElemsOfSameType should cut allocations and comparisons almost in half.
Fixes #nnnn
Scope:
Estimate:

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

/KEVM-perf-run

Here are the KEVM test results:
 Test                                           | ad020b3c9b870279f8ec036163246ec1987ae2b4-ghc8107 time | 874ca3461c907d23471f5d1b18d031a63f76d4be-ghc8107 time | (ad020b3c9b870279f8ec036163246ec1987ae2b4-ghc8107/874ca3461c907d23471f5d1b18d031a63f76d4be-ghc8107) time
------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------
 specs/mcd/vat-deny-diff-fail-rough-spec.k      | 379.88                                                | 523.14                                                | 0.7261536108880988
 specs/mcd/vow-flog-fail-rough-spec.k           | 314.92                                                | 403.46                                                | 0.7805482575720023
 specs/mcd/vow-fess-fail-rough-spec.k           | 367.45                                                | 459.38                                                | 0.7998824502590448
 erc20/ds/allowance-spec.k                      | 256.13                                                | 304.93                                                | 0.8399632702587478
 specs/mcd/vat-subui-pass-rough-spec.k          | 380.53                                                | 450.81                                                | 0.8441028371154145
 erc20/ds/balanceOf-spec.k                      | 181.98                                                | 214.46                                                | 0.8485498461251515
 specs/mcd/vat-subui-pass-spec.k                | 381.31                                                | 448.87                                                | 0.8494887161093412
 specs/mcd/dai-symbol-pass-spec.k               | 241.84                                                | 280.99                                                | 0.8606711982632834
 specs/mcd/flopper-cage-pass-spec.k             | 239.82                                                | 277.52                                                | 0.8641539348515422
 erc20/ds/approve-success-spec.k                | 431.04                                                | 498.53                                                | 0.8646219886466212
 specs/mcd/vat-mului-pass-spec.k                | 295.57                                                | 340.36                                                | 0.8684040427782348
 erc20/ds/transfer-failure-2-b-spec.k           | 263.39                                                | 302.98                                                | 0.8693313089972935
 specs/mcd/vat-addui-fail-rough-spec.k          | 289.64                                                | 332.26                                                | 0.8717269608138205
 specs/mcd/vat-subui-fail-rough-spec.k          | 297.37                                                | 337.54                                                | 0.8809918824435622
 erc20/ds/transfer-failure-1-c-spec.k           | 299.84                                                | 339.76                                                | 0.882505297857311
 erc20/ds/transferFrom-failure-2-c-spec.k       | 231.36                                                | 255.65                                                | 0.9049872873068648
 specs/mcd/end-subuu-pass-spec.k                | 137.22                                                | 151.58                                                | 0.9052645467739806
 specs/mcd/cat-exhaustiveness-spec.k            | 182.68                                                | 200.27                                                | 0.9121685724272233
 specs/mcd/cat-file-addr-pass-rough-spec.k      | 274.51                                                | 295.53                                                | 0.9288735492166617
 erc20/ds/transferFrom-failure-1-d-spec.k       | 347.23                                                | 364.96                                                | 0.9514193336256029
 specs/bihu/forwardToHotWallet-failure-1-spec.k | 259.48                                                | 272.46                                                | 0.9523599794465244
 specs/mcd/flipper-tau-pass-spec.k              | 377.49                                                | 395.36                                                | 0.9548006879805746
 specs/mcd/flipper-ttl-pass-spec.k              | 370.73                                                | 387.27                                                | 0.957290779043045
 specs/bihu/forwardToHotWallet-failure-2-spec.k | 368.87                                                | 381.99                                                | 0.9656535511400822
 TOTAL                                          | 7170.28                                               | 8220.06                                               | 0.8722904698992465

And here are the perf tests on our server:
perf-presort2.pdf
perf-presort.pdf
Unless I'm reading these all wrong, they look very good indeed. If the things I don't assume to be duplicate free in fact are, then we can improve those some. Even if they're not, we can still do so, with slightly more/messier code. That would seem well worth exploring given what we see here.

@F-WRunTime Do you believe the integration tests will run?


Update ktlint to 0.29.0

You will need to bump the version of Kotlinter as well and update the readme -- no worries, I can do that. Sorry about the delay.


storage: Unify front-end block APIs

This is a new proposed starting point for a unified set of front-end block APIs can that can work for virtio-blk, NVMe, and NVMe-oF. To be clear right up front, I'm not even certain that I agree with all of these decisions or approve of this set of APIs. But I think it's a good starting point.
What I tried to accomplish here was to unify the front-end APIs but keep the front-end/middle-end/back-end concept in the current OPI model. I've personally been arguing that we need to instead batch these APIs into fewer endpoints for atomicity reasons, but I think at least conceptually the front/middle/back concept is here to stay.
The most important concepts here are as follows:

I'm unifying not only exposing an NVMe or virtio-blk device to a host system, but also exposing an NVMe-oF device over the network (so the network is the front end bus).

I've introduced a generic "Device" which for NVMe is equivalent to a subsystem.

I've introduced the concept of an endpoint. For NVMe/PCIe, this is a controller at some BDF. For other types, it can be re-used and the controller is a more dynamic and short-lived thing.

The PCI stuff does not allow the endpoint to specify the BDF. It only lets you pick the PF/VF ids. The BDF is assigned by the OS PCI driver and we cannot pick it in these APIs.

Signed-off-by: Ben Walker<EMAIL_ADDRESS>

Hi @benlwalker
Few general questions:

trying to understand nvme-of frontend. We have a network-device that once reaches the DPU, the storage commands are lost, we just have tcp / rdma packets, how will the DPU be able to intercept and provide middle / end services ? Or do you see the DPU in this case terminating the connection and establishing another ? more details on the use case and flow would be great. thanks.
again, would be great for a more specific example - do you see other use cases that will define an endpoint other than controller bdf which are not nvme-of ?
thanks

Hi @benlwalker Few general questions:

trying to understand nvme-of frontend. We have a network-device that once reaches the DPU, the storage commands are lost, we just have tcp / rdma packets, how will the DPU be able to intercept and provide middle / end services ? Or do you see the DPU in this case terminating the connection and establishing another ? more details on the use case and flow would be great. thanks.
again, would be great for a more specific example - do you see other use cases that will define an endpoint other than controller bdf which are not nvme-of ?
thanks

I think the intent for TCP is to terminate NVMe/TCP connection from the Host and start and new one to the remote storage...
Whether it is useful for production or not - not for me to say, but it demonstrates the concept of having something in addition to PCIe well. not all vendors have to implement it... I would guess Virtio-blk will be added to this Device APIs...
I will let @benlwalker correct me if my understanding is wrong...

We've so far only discussed the use of an xPU to offload the initiator side. The TCP endpoint I have in this proposal is instead to offload the target side, where the front-end NVMe host is over the network and the backend storage is attached to the xPU or to the host server the xPU is attached to. I included it primarily to get everyone thinking about a broader set of use cases.

We've so far only discussed the use of an xPU to offload the initiator side. The TCP endpoint I have in this proposal is instead to offload the target side, where the front-end NVMe host is over the network and the backend storage is attached to the xPU or to the host server the xPU is attached to. I included it primarily to get everyone thinking about a broader set of use cases.

thanks for the clarification

@llabordehpe for some reason can't add you to reviewers list, so tagging you here. please review

Would the frontend APIs look same for what's needed on the initiator vs. target?

We've so far only discussed the use of an xPU to offload the initiator side. The TCP endpoint I have in this proposal is instead to offload the target side, where the front-end NVMe host is over the network and the backend storage is attached to the xPU or to the host server the xPU is attached to. I included it primarily to get everyone thinking about a broader set of use cases.

@benlwalker - I am curious if the changes you made were exclusively for Target side (or Initiator side as well)? Of course the endpoint object is not really there.


Sync without GCM

I have installed the app via F-Droid and found this in the FAQ: https://matrix.org/docs/guides/faq.html#i-installed-vector-via-f-droid-why-is-it-draining-my-battery
This seems to be true in that it really drains my battery. AFAIK many Android apps handle this differently in that they sync via an account. Android then manages the syncing without the app having to poll or use GCM.
I think this would be the alternative to GCM which doesn't drain the battery. I'm not an Android expert but noticed that many apps doing that. So maybe you could consider this? Thanks for the hard work and everything.

steckerhalter
Did you read how to reduce this battery draining ?
have a look in the settings page
-> you can reduce the sync heartbeat when the application is in background
-> you can add a delay between two syncs when the application is in background
-> you can disable the sync when the application is in background
you can also install MicroG to replace GCM (you will need to install the "standard" version).

@ylecollen no, is it described somewhere already? Thanks, I will probably look into using microG.

I digged a bit deeper into the drain and I think it probably wasn't much related to Riot really, sorry for the noise and thanks for the suggestions


tests: Enforce 100% URL coverage.

We now instrument URL coverage whenever you run the back end tests,
and if you run the full suite and fail to test all endpoints, we
exit with a non-zero exit code and report failures to you.
If you are running just a subset of the test suite, you'll still
be able to see var/url_coverage.txt, which has some useful info.

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

Looks great!  I'll just fix the mypy errors as I merge.

Also, this fixes #1441.

I made some tweaks to the output and merged this!  Thanks @showell!


Swift 3.1 compile errors

Hello, I use Swift 3.1 and xcode 8.3.3.
I do a manual install, by downloading from the Swift-3 branch and then dragging the folder into the project.
This gives me a total of 12 compile errors.
Am I doing something wrong, or is the swift3-branch not maintained?

It should still work in Swift 3.1. Can you paste the errors here?


Consider moving lbry.fund off of Github Pages

So we can have php & other functions, which could be useful in the submission process.

close not currently needed


Remove Gorm AutoMigrate

Description
Removes Gorm AutoMigrate from the project and replaces with a new base schema.sql to allow stepwise migrations to take over the previous responsibilities of AutoMigrate
Please also review the documentation that goes with this PR: https://github.com/SpecterOps/BloodHound/wiki/Application-Database-Migrations
Motivation and Context
Gorm's auto-migrations can cause random headaches due to how incomplete and buggy they can be. To remove this headache in the short term, this PR removes auto-migrations from BloodHound entirely. In the place of auto-migrations, we use a modified dump of the existing BloodHound schema as a new starting point for stepwise migrations. This ensures that new instances of BloodHound can start from a common base, while running additional stepwise migrations to catch up to existing instances.
The removal of auto-migrations means that creating new models or adding new fields/constraints to exisiting models now requires an intentional stepwise migration to function. This also means that there's only one path for app database migrations, which will reduce mental overhead of model changes (previously you needed to assert which aspects of a model change needed a stepwise migration and which would be handled automatically, as well as how these two migrations are ordered).
How Has This Been Tested?
Additional tests were added to both validate logic and act as a canary for broken production migrations
Types of changes

[x] Chore (a change that does not modify the application functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Documentation updates are needed, and have been made accordingly.
[x] I have added and/or updated tests to cover my changes.
[x] All new and existing tests passed.
[x] My changes include a database migration.

Blocking this as @irshadaj was unable to replicate getting a fresh database after a wipe. Was unable to replicate, but will be addressing any issues we find while debugging his local env before moving forward with this PR, as we want 100% replication rate.


IGListBindingSectionController object property should probably be public

I want my IGListBindingSectionController subclass to be able to implement IGListSupplementaryViewSource. To do that I need access to the section object. Given the fact that the object (the section model in my case) is a private property on IGListBindingSectionController, it can not contain this type of information any more (not accessible)
An option is to represent the supplementary view (a header in my case) as a cell with its own viewModel (what I am doing now) but I would still think this should be available. Thoughts?
IGListBindingSectionController implementation file:

Good point, it probably should.
Are we ok with it being id object (which will be Any in Swift) and letting callers check/cast the object? Not sure if we should try any fancy ObjC generics here.

Are we ok with it being id object (which will be Any in Swift) and letting callers check/cast the object? Not sure if we should try any fancy ObjC generics here.

No need for generics here in my eyes, but now that you mentioned it 🤔  It would be neat
Other than that, IGListBindingSectionController is sweeet :)
Maybe I can open a PR tomorrow?

@heumn all you!

If possible, lightweight ObjC generics would probably be nice


Migrate Keeping Pace

Ready for review.

Current coverage is 87.98%

Merging #476 into master will decrease coverage by -0.01% as of decd37e

@@            master    #476   diff @@
======================================
  Files          231     231
  Stmts        10410   10405     -5
  Branches         0       0
  Methods          0
======================================
- Hit           9160    9155     -5
  Partial          0       0
  Missed        1250    1250

Review entire Coverage Diff as of decd37e

Powered by Codecov. Updated on successful CI builds.

Looks great! So nice to have this harmonized! :+1:


Add initial filter support

We need to be able to run filters on datasets in the dataset viewer such as gaussian blurring, resampling, resizing,etc.
This enhancement covers adding an initial interface for that and implementing a filter to start as well as a way to activate them from the menu.

Delivered to master.
An interface IFilter.cs was added with just a Filter method. The filter returns a new Dataset after running. There may need to be a way to modify a Dataset in place in the future but this is fine for now. I added an initial GaussianBlur filter that just supports equally spaced data. There are some TODOs for adding dynamic spacing support and I will write separate issues for cleaning that up. A few automated tests would be good as well to make sure it is correct, I didn't test extensively yet since the goal was to get Filter support going. I also added a repeat last filter option in the menu.
A few things came to mind that should be written up as issues as well:

The ability to save modified datasets
A history of the changes made in a panel on the right. Clicking historical entries could bring that dataset back.
Dynamic spacing support to GaussianFilter
UI for options for filters (set sigma and kernel size or time window/time scale for example)
Resampling filter
Hotkeys for menu commands

Commit
commit 76890c5cea8fb5f95af20a478af716d9b44951ee
Author: Alex Hunt<EMAIL_ADDRESS>Date:   Thu Mar 24 22:02:51 2022 -0400
Issue28: Added the IFilter interface, a place to run them in the menu, a way to repeat the last filter, and an initial GaussianFilter to start off.

Testing

Tested when you open a dataset and click the Gaussian Blur button it blurs the curve.
Tested when you press Repeat Last with before running any filters, nothing happens.
Tested when you press Repeat Last after running the blur it runs the blur again on the new data.


Fix incorrect placement of Auto Embed

Problem
If there is text behind the current cursor position, Auto Embed Element will be inserted at the end of the editor when the following conditions are met:

EmbedConfig#parseUrl takes some time (such as 1 second)
Trigger embedding by clicking on the “Embed xxx” option instead of pressing the enter key

How to reproduce

Modify the code of YoutubeEmbedConfig#parseUrl to simulate longer execution time.export const YoutubeEmbedConfig: PlaygroundEmbedConfig = {
  ...
  parseUrl: async (url: string) => {
    await new Promise(resolve => setTimeout(resolve, 1000));
    ...
  ...
};

Type some text in editor and then try to embed a YouTube video before it

https://user-images.githubusercontent.com/24994263/227627537-786d251a-95c4-4e29-89b0-964f2dc2eb60.mov

Should it be just linkNode.replace(embedNode)

I think we don't know what the embedNode here is, and the logic of inserting embedNode is defined by activeEmbedConfig#insertNode


Diskspd testing against SSD and Microseconds

Hi, hope this is the correct place for raising this question. When using Diskspd against 4 SSD's (RAID 5 array) we are seeing higher than expected latency figures (see below), which are baffling us. However after some research it appears that some other users are saying when you use Diskspd against SSD's the figures are in Microseconds.   Please can someone confirm this is the case?
Thks Darren
%-ile |  Read (ms) | Write (ms) | Total (ms)
min |        N/A |      4.720 |      4.720

25th |        N/A |     18.149 |     18.149
50th |        N/A |     26.806 |     26.806
75th |        N/A |     47.153 |     47.153
90th |        N/A |     92.725 |     92.725
95th |        N/A |    143.233 |    143.233
99th |        N/A |    318.068 |    318.068
3-nines |        N/A |    864.756 |    864.756
4-nines |        N/A |   1580.786 |   1580.786
5-nines |        N/A |   2070.190 |   2070.190
6-nines |        N/A |   2418.533 |   2418.533
7-nines |        N/A |   2653.430 |   2653.430
8-nines |        N/A |   2653.430 |   2653.430
9-nines |        N/A |   2653.430 |   2653.430
max |        N/A |   2653.430 |   2653.430

The reporting is in milliseconds in all cases. The column headers are accurate. They would be “us” or similar if they were in microseconds.
Depending on the specific workload you are simulating and the adapter capability, RAID5 can have a very large IO multiplier associated with it.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: darrensmithcom<EMAIL_ADDRESS>Sent: Wednesday, October 25, 2017 1:02:26 AM
To: Microsoft/diskspd
Cc: Subscribed
Subject: [Microsoft/diskspd] Diskspd testing against SSD and Microseconds (#45)
Hi, hope this is the correct place for raising this question. When using Diskspd against 4 SSD's (RAID 5 array) we are seeing higher than expected latency figures (see below), which are baffling us. However after some research it appears that some other users are saying when you use Diskspd against SSD's the figures are in Microseconds. Please can someone confirm this is the case?
Thks Darren
%-ile | Read (ms) | Write (ms) | Total (ms)
min |        N/A |      4.720 |      4.720
25th | N/A | 18.149 | 18.149
50th | N/A | 26.806 | 26.806
75th | N/A | 47.153 | 47.153
90th | N/A | 92.725 | 92.725
95th | N/A | 143.233 | 143.233
99th | N/A | 318.068 | 318.068
3-nines | N/A | 864.756 | 864.756
4-nines | N/A | 1580.786 | 1580.786
5-nines | N/A | 2070.190 | 2070.190
6-nines | N/A | 2418.533 | 2418.533
7-nines | N/A | 2653.430 | 2653.430
8-nines | N/A | 2653.430 | 2653.430
9-nines | N/A | 2653.430 | 2653.430
max | N/A | 2653.430 | 2653.430
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/diskspd/issues/45, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIVpKaD68CAasbgi_PauymGGg5o830hNks5svusSgaJpZM4QFlpE.


nss_latest: 3.76.1 -> 3.78.0; firefox{,-bin}: 99.0.1 -> 100; firefox-esr: 91.8.0esr -> 91.9.0esr

https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_78.html
https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_77.html
https://www.mozilla.org/en-US/firefox/91.9.0/releasenotes/
https://www.mozilla.org/en-US/firefox/100.0/releasenotes/
Description of changes
Builds are queued, I'm going to sleep and will test in the morning.

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

As usual testing on x86_64-linux (sway, pipewire)

Webcam

Microphone

Screensharing (wlroots)

Audio/Video

WebGL

[x] 91.9.0esr

[x] 100.0

pkgs/development/libraries/nss/3_54_security_load.patch': No such file or directory

Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).
172 x86_64-darwin
1230 x86_64-linux

I assume the rebuild amount comes from the patch handling in the 3.77 update. That doesn't change the fact that this should go into master.

You reordered the patches, but that seems easy to fix.

Or at the very least move the comment that got on a wrong place due to that move.

Wow, yeah, the list is of course ordered. The 3.77 update came from @ajs124 and we both made the same mistake :hand:.

Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).

1 x86_64-darwin
13 x86_64-linux

https://www.mozilla.org/en-US/security/advisories/mfsa2022-16/
https://www.mozilla.org/en-US/security/advisories/mfsa2022-17/

Updated the commit messages with advisories and fixed CVEs.


Any progress/intent to release msodbcsql17 on Linux for ARM?

The Linux install page for the msodbcsql17 driver makes no mention of support for ARM despite Azure SQL Edge being promoted.
Is there an ARM release for Linux available anywhere? Is there any intent to make such a release?
I see there is an ARM release for Mac M1 in the homebrew repo, but despite searching I can find no sign of a Linux release.
This topic is touched upon in #14254 with no clear direction on what is to be expected here.

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

ID: 0fc3da20-7ab2-d20f-4d29-4664d3183b57
Version Independent ID: 986d25d9-5d2e-5154-39ea-3b683faf2264
Content: Install the Microsoft ODBC driver for SQL Server (Linux) - ODBC Driver for SQL Server
Content Source: docs/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server.md
Service: sql
Sub-service: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-davidengel

I'm specifically interested in being able to run PHP workloads on ARM talking to MSSQL. Cheers.

@johnmccabe -- John, thank you for your feedback.  Please consider these resources:

Supported features of Azure SQL Edge

SQL Server on Microsoft Q&A

DBA Stack Exchange

Stack Overflow

@David-Engel -- David, please look into this potential documentation issue.

ARM64 support was added to the msodbcsql18 package starting in 18.1:
https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/system-requirements?view=sql-server-ver16#operating-system-support
Regards,
David

There are no plans to backport ARM64 support to msodbcsql17. You should be able to use msodbcsql18.
Note: Encryption settings in msodbcsql18 now use secure default behaviors. It defaults encryption to true and will validate server certificates if they require encryption. Specify Encrypt=false to connect to non-encrypted servers and/or TrustServerCertificate=true if connecting to a server that requires encryption but has an expired or self-signed certificate.
Regards,
David
#please-close


update from upstream

chore(deps): update rui314/setup-mold digest to 6bebc01
chore(deps): update dependency @semantic-release/release-notes-generator to v13
chore(deps): update dependency semantic-release to v23.0.6
chore(deps): lock file maintenance
chore(deps): update returntocorp/semgrep docker tag to v1.66.1
chore: allow warnings in test
chore(deps): update node.js to >=20.12.0
chore: allow warnings in test
chore: set checks with new API
chore: fix ] typo

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
431

Relevant Lines:
995

💛  - Coveralls

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


Update quickstart docs with more examples, add config doc

The quickstart docs now include more examples of how to configure pods to have logs scraped. Additionally, there are some example KQL queries.
We now generate a config doc based on the config struct, which allows us to keep the doc and the config in sync and reuse the comments associated with the toml elements within source. To better support this, I've configured many of the global config options as omitempty in the struct to more easily control the serialized outputs we write to the markdown file.

@microsoft-github-policy-service rerun


Update to Maven 3.8.6 #660

closes #660

@gnodet is there a reason to hold back on releasing this? Would manual sanity testing help increase confidence?

Hey guys, someone with write access needs to merge this. I can't, so I guess this needs to be done by one of the maintainers?


fix app issues

You did it @sandeepmantha!
Thank you for signing the Anthem Opensource Software CLA.


Add trending/popular movies section from TMDB Api

Trending popular movies would be fetched from the server dynamically using TMDB api

I am ready to work on this issue under JWOC


[SPARK-18063][SQL] Failed to infer constraints over multiple aliases

What changes were proposed in this pull request?
The UnaryNode.getAliasedConstraints function fails to replace all expressions by their alias where constraints contains more than one expression to be replaced.
For example:
val tr = LocalRelation('a.int, 'b.string, 'c.int)
val multiAlias = tr.where('a === 'c + 10).select('a.as('x), 'c.as('y))
multiAlias.analyze.constraints

currently outputs:
ExpressionSet(Seq(
    IsNotNull(resolveColumn(multiAlias.analyze, "x")),
    IsNotNull(resolveColumn(multiAlias.analyze, "y"))
)

The constraint resolveColumn(multiAlias.analyze, "x") === resolveColumn(multiAlias.analyze, "y") + 10) is missing.
How was this patch tested?
Add new test cases in ConstraintPropagationSuite.

Test build #67379 has started for PR 15597 at commit 2fe728f.

Test build #67379 has finished for PR 15597 at commit 2fe728f.

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

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

Merged build finished. Test FAILed.

cc @sameeragarwal

Test build #67433 has started for PR 15597 at commit 32e0b36.

Test build #67433 has finished for PR 15597 at commit 32e0b36.

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

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

Merged build finished. Test PASSed.

@sameeragarwal I've addressed your comments! Thank you!

Test build #67504 has started for PR 15597 at commit 3f07493.

Test build #67504 has finished for PR 15597 at commit 3f07493.

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/67504/
Test PASSed.

LGTM, thanks!

Just to be extra safe, it'd be great to re-run the test suite on this once  https://github.com/apache/spark/pull/15319 is merged.

retest this please

Test build #67583 has started for PR 15597 at commit 3f07493.

Test build #67583 has finished for PR 15597 at commit 3f07493.

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/67583/
Test PASSed.

Merging this in master/branch-2.0.


HDDS-4770. Upgrade Ratis Thirdparty to 0.6.0

What changes were proposed in this pull request?
Upgrade ratis-thirdparty to recently released 0.6.0 as now 0.6.0-SNAPSHOT is gone from the repos.
https://issues.apache.org/jira/browse/HDDS-4770
How was this patch tested?
https://github.com/adoroszlai/hadoop-ozone/actions/runs/527176547

Thanks @elek for the review, @elek and @lokeshj1703 for Ratis snapshot.

Thanks @adoroszlai


[Feature]: Redis - Add support for JSON.GET

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
JSON.GET doesn't work today, because our redis client actually has its own list of commands that it supports. This command, being from an external module, is not on that list. We'll need to see if there's a way to extend the command pool for custom commands
Why should this be worked on?
User request

Could we also add support for setting/getting multiple fields with HSET/HGET?
Currently we can only set/get one field at a time, but HSET added support for multiple fields in v4.0 (2017). Also, HMSET was depreciated in v4.0, but in our Redis connector HMSET is still recognized as a valid command (and HSET fails when trying to set multiple fields). @sumitsum

Another user requested this feature.


Laravel composer fails on build a  Standalone Binary

What happened?
I am following this doc:
https://frankenphp.dev/docs/laravel/#laravel-apps-as-standalone-binaries
Step 1. AlI fine, but composer fails on:

Some guidance for fix this issue?.
Php(8.3)-com/xml is installed in my system. Laravel 10.x Ubuntu 22.04
Build Type
Standalone binary
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
dom
DOM/XML	enabled
DOM/XML API Version	20031129
libxml Version	2.12.5
HTML Support	enabled
XPath Support	enabled
XPointer Support	enabled
Schema Support	enabled
RelaxNG Support	enabled

Relevant log output
(base) ➜  api git:(master) ✗ docker build -t static-laravel-app -f static-build.Dockerfile .
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
            Install the buildx component to build images with BuildKit:
            https://docs.docker.com/go/buildx/

Sending build context to Docker daemon  102.3MB
Step 1/9 : FROM --platform=linux/amd64 dunglas/frankenphp:static-builder
 ---> 11e7a98160c7
Step 2/9 : WORKDIR /go/src/app/dist/app
 ---> Using cache
 ---> 676084ec258f
Step 3/9 : COPY . .
 ---> 74033c5fbd49
Step 4/9 : RUN rm -Rf tests/
 ---> Running in 8e1f09be30ea
Removing intermediate container 8e1f09be30ea
 ---> 987e36d340ce
Step 5/9 : RUN cp .env.example .env
 ---> Running in 96b4200ef2af
Removing intermediate container 96b4200ef2af
 ---> e604ff294251
Step 6/9 : RUN sed -i'' -e 's/^APP_ENV=.*/APP_ENV=production/' -e 's/^APP_DEBUG=.*/APP_DEBUG=false/' .env
 ---> Running in e61b38426d50
Removing intermediate container e61b38426d50
 ---> eb0c3abddf0a
Step 7/9 : RUN composer install --ignore-platform-reqs --no-dev -a
 ---> Running in 86f5ea23188c
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 0 installs, 0 updates, 40 removals

Please see https://github.com/dunglas/frankenphp/issues/693#issuecomment-2080756844


Cannot use "sha384": No such hash algorithm

when i run:
select basic_auth.sign('{"sub":"1234567890","name":"John Doe","admin":true}', 'secret', 'HS384')
output this:
 [22023] ERROR: Cannot use "sha384": No such hash algorithm
 Where: SQL function "algorithm_sign" statement 1
 SQL function "sign" statement 1

other hash algorithms are same.
This is my algorithm_sign function:
create function basic_auth.algorithm_sign(signables text, secret text, algorithm text) returns text
LANGUAGE SQL
AS $$
WITH
  alg AS (
    SELECT CASE
      WHEN algorithm = 'HS256' THEN 'sha256'
      WHEN algorithm = 'HS384' THEN 'sha384'
      WHEN algorithm = 'HS512' THEN 'sha512'
      ELSE '' END AS id)  -- hmac throws error
SELECT basic_auth.url_encode(basic_auth.hmac(signables, secret, alg.id)) FROM alg;
$$;

I'm not sure why you have 'basic_auth.hmac', it should just be 'hmac' unless you installed pgcypto into the same schema, I presume you did something like that since the function is being called.
@esmeetu try this:
select basic_auth.hmac('foo', 'secret', 'sha384');
You should get:
hmac
\x0edb7068ecbf4de2c47b8819fd534333379f208f989c51018d03ee1155e4c0740a418ec220d4260eabcb2d090b16de6e
If not, then it sounds like your pgcypto is not correctly installed.

Thanks for your reply!
Well, I install pgcypto in the same schema basic_auth.
Under your code, i still get the error: [22023] ERROR: Cannot use "sha384": No such hash algorithm
I reinstall pgcrypto and pgjwt, there is error as before. But the extension works fine a few days before, I don't know what's wrong.

Are you reinstall pgcrypto by a os package like apt or rpm or did you build it from source?  If you built it you might be missing some libraries.
After you reinstalled did you restart postgres?  'hmac' comes from pycrypto, so I'm not really an expert in building it, I installed it from an ubuntu package.

I use datagrip, enter this CREATE EXTENSION pgjwt CASCADE in my console. It has pgcrypto default, and i drop it, recreate it. As you say, i should try down the source code, and rebuild it.

@michelp I find the reason, It my fault thati forget that i updated my postgresql today.
After reboot the system, It works fine! But i am not clear why it fails, may be  pgcrypto has some changes.
Thanks you again. Good extention. :)


Add windows test to CI

Since we are busy increasing coverage...

Seems like I opened a huge can of worms. This should be revisited later.

@marcelm Are you testing this via the CI? (Given the quite large amount of WIP comments, that seems likely).
I find that MacOS and Linux are similar enough that this is usually successful, but for windows it is much quicker to boot up windows and test it there.
I do have a windows installation on my machine. I even have development environments set up there. (For python-isal I had to do quite some tedious work to get it to install, but in the end I got it to work).
Now I'd rather play games on that Windows install, but I don't mind debugging an hour in my spare time to get xopen to work on windows :slightly_smiling_face: .

@marcelm I did it! All tests succeed. Hurray!

Hi, thanks for picking this up!

Are you testing this via the CI?

Yes, I was, and this is indeed where the "wip" commits come from, but I switched to my Windows VM for the last couple of commits.
I’ll force-push a somewhat cleaner commit history.

It looks good to me. Unless you feel something should be added, it can be merged.


Get to know Fisherman and entry added to the index heads up

Nice theme @hasanozgan!
I added Lambda to the Fisherman registry for you.
fisher install lambda

In Fisherman, every plugin has meta data associated with like your username, plugin/theme description and variadic tags to help searching. Also, you don't need to create a PR directly in the Fisherman repo to add a new theme.
One last thing, Fisherman is aware of index updates and manages itself automatically and independently, so users don't need to update the framework to know about the new theme, in this case Lambda.
Related:

https://github.com/oh-my-fish/oh-my-fish/pull/234

https://github.com/oh-my-fish/oh-my-fish/pull/234

oh-my-fish/oh-my-fish#234

https://github.com/oh-my-fish/oh-my-fish/pull/234

@bucaran thank you.


feat(forge/test): testrunner block summary

Motivation
Resolves #1004
Print a summary including pass/fail count and duration after each test suite block.

Solution

runner.rs: Refactor map of test names/results to a SuiteResult struct that stores run duration and results.
test.rs: Format and print summary following each suite run.

Notes

I am pretty new to Rust, so all comments are very welcome. This is mostly compiler-driven development.
No ignored count yet.

Colored the ok/fail and moved duration according to this comment.


fix(features/passive-event-listeners): Can I Use reference

http://caniuse.com/#feat=passive-event-listener

Thanks!


Cant parametrize FLOAT value in query

What happened?
When i was trying to create query parameter as:
bigquery.ScalarQueryParameter("TESTPARAM", "FLOAT64", 2.15)

I have got 400 response:
"json: cannot unmarshal number into Go struct field QueryParameterValue.Value of type string"
Looks like "FLOAT/FLOAT64" value field is converted to float value (https://github.com/googleapis/python-bigquery/blob/62490325f64e5d66303d9218992e28ac5f21cb3f/google/cloud/bigquery/_helpers.py#L348), but bigquery-emulator api is not prepared for numeric values, but only strings.
What did you expect to happen?
Fix this to be able to set "FLOAT" parameter
How can we reproduce it (as minimally and precisely as possible)?
By using docker image and creating job:
POST http://localhost:9050/bigquery/v2/projects/test/jobs?prettyPrint=true
{"jobReference": {"jobId": "98ee9d11-548a-4a5f-b1c1-a8e7bfc48916", "projectId": "test"}, "configuration": {"query": {"queryParameters": [{"parameterType": {"type": "FLOAT64"}, "parameterValue": {"value": 2.15}, "name": "TESTPARAM"}], "useLegacySql": false, "query": "SELECT * FROM UNNEST(@TESTPARAM)", "parameterMode": "NAMED"}}}
Anything else we need to know?
docker image: bigquery-emulator:latest (version: 0.0.4)

@kurrenda
Passing Float64 to UNNEST seems odd, is this intended?
The error is not due to Float64, but because you are passing parameters to UNNEST in FROM clause. Currently, you cannot pass parameters to UNNEST used in the FROM clause. Please refer to the following issue:
https://github.com/goccy/bigquery-emulator/issues/234#issuecomment-1929153585
FLOAT64 should work as intended. Please refer to the following.
❯ bq --api http://<IP_ADDRESS>:9050 mk --project_id=test test_ds
Dataset 'test:test_ds' successfully created.

❯ bq --api http://<IP_ADDRESS>:9050 query --project_id=test "create table test_ds.abc (id string, value float64)"

❯ bq --api http://<IP_ADDRESS>:9050 query --project_id=test 'insert into test_ds.abc (id, value) VALUES ("a", 1.23), ("b", 2.46)'

❯ bq --api http://<IP_ADDRESS>:9050 query --project_id=test --parameter='TESTPARAM:FLOAT64:1.23' "select * from test_ds.abc where value = @TESTPARAM"
+----+-------+
| id | value |
+----+-------+
| a  |  1.23 |
+----+-------+

If my understanding is incorrect, I would appreciate it if you could inform me again, along with steps to reproduce the issue.

It's not related with UNNEST and its working fine in bq shell. The issue occurs with the HTTP API in preparing job (when i call e.g bigquery.query())
To simulate that run docker container and try make POST request (based on your example):
POST http://localhost:9050/bigquery/v2/projects/test/jobs?prettyPrint=true
{"jobReference": {"jobId": "98ee9d11-548a-4a5f-b1c1-a8e7bfc48911", "projectId": "test"}, "configuration": {"query": {"queryParameters": [{"parameterType": {"type": "FLOAT64"}, "parameterValue": {"value": 2.12}, "name": "TESTPARAM"}], "useLegacySql": false, "query": "select * from test_ds.abc where value = @TESTPARAM", "parameterMode": "NAMED"}}}
It works fine when i change parameter value to string manually - but  "parameterValue": {"value": 2.12} -> "parameterValue": {"value": "2.12"}
But this is not a workaround, because bigquery.cloud package changes it to float before request anyway

I Understood. Indeed, that aspect is not compatible with BigQuery. In the case of the emulator, not limited to float but also int, passing them as query parameters in their original types can lead to problems. This is reproducible with the Node.js BigQuery SDK as well. But in the case of Node.js, we have been able to avoid the problem by casting numbers to strings in advance.
I have one thing to clarify, when you mention "bq shell," what tool are you using to execute your queries? I cannot reproduce the same behavior with parameters alone, so if possible, could you share the commands you are executing?

"bq shell" i had in mind your example
bq --api http://<IP_ADDRESS>:9050 query --project_id=test --parameter='TESTPARAM:FLOAT64:1.23' "select * from test_ds.abc where value = @TESTPARAM" - it works fine (im just entering bq --api http://<IP_ADDRESS>:9050 shell and then quering)
HTTP POST with body which i posted above - not working
docker run -it -d -p 9050:9050 --platform linux/amd64 ghcr.io/goccy/bigquery-emulator:latest --project=test

bq --api http://<IP_ADDRESS>:9050 mk --project_id=test test_ds

bq --api http://<IP_ADDRESS>:9050 query --project_id=test "create table test_ds.abc (id string, value float64)"

bq --api http://<IP_ADDRESS>:9050 query --project_id=test 'insert into test_ds.abc (id, value) VALUES ("a", 1.23), ("b", 2.46)'

curl -H "Content-Type: application/json" -X POST -d '{"jobReference": {"jobId": "5", "projectId": "test"}, "configuration": {"query": {"queryParameters": [{"parameterType": {"type": "FLOAT64"}, "parameterValue": {"value": 1.23}, "name": "TESTPARAM"}], "useLegacySql": false, "query": "select * from test_ds.abc where value > @TESTPARAM", "parameterMode": "NAMED"}}}' "http://<IP_ADDRESS>:9050/bigquery/v2/projects/test/jobs?prettyPrint=true"

I see, you were using the Python SDK. Understood, thank you very much for clarifying.

Could u share this hack? Are you mocking those values?

I also hit this issue, when using python.
@ttiurani - Mind sharing what you did to bypass this issue?

@ttiurani - Mind sharing what you did to bypass this issue?

Instead of "float_column = @float_value" everywhere I have an integration-test-only hack:
if config.is_emulator:
"float_column = " + float_value
else:
"float_column = @float_value"
NB: this is obviously bad because it's an SQL injection vulnerability, so you have to be super sure "is_emulator" cannot be True anywhere except in controlled environments. Even though I am sure, I would very much want to get rid if this hack.

Thank you for sharing. I see, yeah that is something dangerous to have.


newsapi.newsapi_exception.NewsAPIException

While trying to run the following code snippet , which is actually a part of documentation :
all_articles = newsapi.get_everything(q='bitcoin',
                                      sources='bbc-news,the-verge',
                                      domains='bbc.co.uk,techcrunch.com',
                                      from_param='2017-12-01',
                                      to='2017-12-12',
                                      language='en',
                                      sort_by='relevancy',
                                      page=2)

I am getting this error again and again :
Traceback (most recent call last):
  File "news.py", line 16, in <module>
    page=2)
  File "C:\Python27\lib\site-packages\newsapi\newsapi_client.py", line 261, in get_everything
    raise NewsAPIException(r.json())
newsapi.newsapi_exception.NewsAPIException

Any suggestions on why this might be happening ?

I've tried to replicate this in Python 2.7.17 and 3.7.4 with the following results.
python3:
I started with Python 3 because I am more familiar with it. The snippet you've supplied works as expected with a caveat; are you using a free plan? If so, you will get the following exception:
Traceback (most recent call last):
  File "/home/daniel/Code/junkyard/newsapi_test.py", line 12, in <module>
    page=2)
  File "/home/daniel/.virtualenvs/scripts/lib/python3.7/site-packages/newsapi/newsapi_client.py", line 261, in get_everything
    raise NewsAPIException(r.json())
newsapi.newsapi_exception.NewsAPIException: {'status': 'error', 'code': 'parameterInvalid', 'message': 'You are trying to request results too far in the past. Your plan permits you to request articles as far back as 2019-09-26, but you have requested 2018-10-01. To extend this please upgrade to a paid plan.'}

Adjusting the from_param and to within the allowable date range returns as expected.
python2:
Running the same all_articles command returns the exception as detailed by @reshu-b7
Traceback (most recent call last):
  File "/home/daniel/Code/junkyard/newsapi_test.py", line 12, in <module>
    page=2)
  File "/home/daniel/.virtualenvs/py2/lib/python2.7/site-packages/newsapi/newsapi_client.py", line 261, in get_everything
    raise NewsAPIException(r.json())
newsapi.newsapi_exception.NewsAPIException

Again, adjusting the from_param and to parameters works as excepted.
For clarity, the snippet I used to get it working:
all_articles = newsapi.get_everything(q='bitcoin',
                       sources='bbc-news,the-verge',
                       domains='bbc.co.uk,techcrunch.com',
                       from_param='2019-10-01',
                       to='2019-10-12',
                       language='en',
                       sort_by='relevancy',
                       page=2)

Without doing much more investigation than that, I would suggest it is a case of the exception not raising as expected in Python 2 and leaving the user guessing as to the problem.
Hope that helps, or gets us looking at it.


trim file size down.

The app  size on osX is huge.
it could literally be 300% smaller.
The issue is in the electron framework where you don't preserve symlinks while packaging
https://github.com/atom/electron/issues/2003

Thanks. I saw that the OSX zip was much bigger but haven't had the time to dig into the problem. It does look like a simple case of zip not handling the symlinks and should be easy to fix.


fixed a few issues with the progress bars

disk usage bar didn't work on drives under a terabyte
disk usage percentage still printed when disabled
battery info option was inversed

Thanks for the fixes!


Added auto sizing to ParameterSetupDialogWithScanPreview.java

Hi Tomas,
this automatically sizes the ParameterSetupDialogWithScanPreview. It resizes a little bit more if you move the dialog afterwards, but it is still better than before.
Best
Steffen

Thanks, Steffen!


⚠ Processors has degraded performance

In 08a24ac, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 53 ms

Resolved: Processors performance has improved in 1a8436d.


NoBrainer support?

http://nobrainer.io/

PR?

Any news on this? I'd be great! 😄

No news. It probably will never be implemented by the core team. You are welcome to create a PR (something like this #1574).


APT whitelist request for exiftool

exiftool is a virtual package provided by libimage-exiftool-perlin Trusty.

Thanks a lot for your help @celeduc , works like a charm.


MdInkRipple error in disabled watcher

Steps to reproduce
Put a :disabled attribute on md-button and toggle it on and off. When putting disabled = true, everything is fine, md-ink-ripple is removed as per the code, however, putting :disabled to false will result in an error
TypeError: Cannot read property 'parentNode' of null

Which browser?
Chrome 55
What is expected?
for md-ink-ripple to append itself back to its initial parent (in this case, md-button)
What is actually happening?
Fails to attach it self back to its parent
This may be related to  #329  as well.
Looking through the code, the error is in the watcher of the disabled prop. When disabled is true, md-ink-ripple is destroyed, removed from parent. When switched to true, this.init() is executed, however at that point in time, this.$el is no longer attached to its parent, thus when calling getClosestPositionedParent() in the init() function, there is no parent on this.$el
Either in the watcher for disabled, this.$el should be reinserted into this.parentElement before calling init().
I wish I had time to setup a PR but I was able to investigate this much. Thanks again for your awesome work.

Related #343.

This was already reported in #313 and fixed in PR #317 (using pretty much your code.) It should make it into version 0.6.4.

Maybe im reading the code wrong in PR #317 but does that seem to only do a null check and not re insert the md-ink element back into its parent? If I disable the the button, then re-enable it, the watcher for disabled will call init() because disabled will be false, then this.getClosestPositionedParent() with the new PR will return false thus not re-enabling md-ink ?
Perhaps I am reading that PR wrong.

I will take a deep look into it. Thanks!

@marcosmoura
Currently in init, this.parentElement is always reset to this.getClosestPositionedParent(this.$el.parentNode). Perhaps this.parentElement should only be set if it is not null.
I would do a PR, but obviously my last solution didn't fully solve the problem. I want to make sure I fully understand what's going on here.

@korylprince Your solution solved the problem but it is neither in current master nor in 0.6.3
@marcosmoura Line 64 - 68 should be like
    const parent = element ? element.parentNode : undefined;

    if (!parent || parent.tagName.toLowerCase() === 'body') {
      return false;
    }

My development is (kind of) stopped depending on 0.7.0 publishing. Same problem here.

I was sick for those 13 days and I didn't have time to deal with so many issues. Sorry about that. I will fix that really soon.

We are very grateful for your work @marcosmoura, sorry if it looked like some pressure. Indeed, there are so many issues but you a fast developer, impressive.

No. It didn't look like that. Don't worry. Stay tuned. The new version will be delivered really soon. :)

I've fixed this (I think) in the above mentioned commit, if you want to pull it. I used, in part the code from @copitz. In testing, this seems to completely resolve the issue.


microwave ECS

About the PR
i apologize by way of ECS-ing awful systems no one wants to touch.
It's still pretty spaghetti, but it's better than before.
Closes #10065
Changelog

no cl no fun

the mythical no merge code pr

bungled words


WSA apps NOT scaling/spanning across multiple monitors.

Steps to reproduce

Open any WSA app
Try to resize it across your monitors
Alternatively use apps like Asus ScreenPad plus which basically resizes the app across monitors.

✔ Expected Behavior
The app should properly scale/span/resize across the monitors with the content being displayed across both of them just like what happens with any other native app on windows.
❌ Actual Behavior
What is happening is, the app either doesn't scale more than the monitor resolution and even if it can (using Asus Screenpad Plus), it scales and shows a blank panel on the secondary monitor. This used to work earlier, but after a few updates, it no longer works.
Other Software
The bug happens with any android app installed on WSA. I use Apple Music and Tachiyomi primarily installed using APK. I also use Asus Screenpad Plus which basically resizes the app to fill/span across multiple monitors.
Please specify the version of Windows Subsystem for Android
2210.40000.7.0

Hi, could you provide screenshots/video and details about your screen resolution? We'd like to understand exactly what's happening here.

https://user-images.githubusercontent.com/26793209/210750760-b4c44713-cc9c-46af-8917-95134a27ea9c.mp4
If you check the file above you'll know what I mean. The content on the 2nd display isn't being rendered at all. This didn't happen in earlier builds!

Thanks for feedback here, we're aware of this issue internally as well. Unfortunately, this is an Android limitation, Android itself doesn't support apps spanning multiple display devices. Addressing this issue is not on the immediate roadmap but we'll continue to evaluate going forward.

Hmm, not sure then why it was working in the earliest builds of WSA, but it's a much-needed feature as it opens whole new possibilities. Would be really looking forward to it.

Hmm, not sure then why it was working in the earliest builds of WSA, but it's a much-needed feature as it opens whole new possibilities. Would be really looking forward to it.

In the earliest of WSA builds from 2021 this did "work" due to WSA using a virtual display model to represent windows. These could be of arbitrary size but with that came numerous issues compromising compatibility, maintainability with upstream Android and performance, this the switch to the current free form windowing model.
We have in the past done a proof of concept on a fox but usage data shows that this scenario is extremely rare so it hasn't been prioritized.
If you could elaborate on the new possibilities you have in mind we will consider that in regards to prioritization.

In the earliest of WSA builds from 2021 this did "work" due to WSA using a virtual display model to represent windows. These could be of arbitrary size but with that came numerous issues compromising compatibility, maintainability with upstream Android and performance, this the switch to the current free form windowing model.

Thanks for the clarification! I guess that's why the maximum window size is dependent on the monitor size it is running on.

We have in the past done a proof of concept on a fox but usage data shows that this scenario is extremely rare so it hasn't been prioritized.
If you could elaborate on the new possibilities you have in mind we will consider that in regards to prioritization.

So, the MAJOR use case would be as an e-book/comic book reader in cases where you're using a stacked monitors layout or even dual-screen laptops like Zenbook Duo/Yoga Book 9i, which are becoming increasingly common as of late. Due to this, I was able to use my laptop as a Kindle of sorts for reading which was really nice and my main use case of WSA!
You can also take advantage of it while gaming on 2 side by side monitors, or just fill your multi-monitor setup for more display area thus greater immersion. People do these with windows apps every time.
Think of Surface Duo with 2 screens side by side. It does open a lot of possibilities.

If you could elaborate on the new possibilities you have in mind we will consider that in regards to prioritization.
Now that laptops/devices with two screens are becoming more coming, this feature would be awesome. I use a Lenovo Yoga Book 9i for example, and if I want to read a Kindle book or magazine across both screens, I need to use the Kindle Cloud Reader in my browser as I can stretch the browser across both screens. It would be so much more useful to be able to span native Android apps like Kindle and other magazine readers across the two screens.

Though I fear with WSA being deprecated (which is so disappointing - this is the top feature that has allowed me to travel with a single Windows touchscreen device - I'm not excited to have to start bringing a separate tablet again), I imagine any changes on this front are rather unlikely, hey :(

WSA being deprecated (which is so disappointing - this is the top feature

Exactly, this is so unfortunate. WSA has been one of the top 3 features of Windows for me in a long long time!!! It was so awesome and didn't have any of the headaches of other emulators.
I'm seriously hoping they can open-source it (99% sure they won't).


Wordcloud implodes with high numbers of words

The upper bound of fontScale's range is always 100, regardless of how many words are displayed or the size of the SVG canvas. This leads to intermittent collisions between words at high volumes (> 150). As a solution, I suggest setting the upper bound dynamically based on the ratio between the number of words and the SVG area size. This should allow the package to render large numbers of words without collisions by adjusting the fonts size dynamically. I will submit a Pull request if you are interested (and also if you are not).

Should be fixed to some extent for now.


show error message on bind

Version: 1.0.111
Platform: darwin 19.4.0
Plugins: clickable-links, quick-cmds, shell-selector
we see the message " safevalue must use properties binding " in menu
hotkey don't works

same problem

The plugin has been abandoned by its author and wasn't updated in a while.


Network Swagger (Public IP Addresses) Documentation Fix

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify - Bug fix swagger documentation on newest network swagger

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

As both dotnet SDK and another SDK were released for this version, so block this PR merge until SDK release owners approve this PR change.

No impact for dotnet track 2 as we group methods by the path not the operation group.

@tadelesh, @qiaozha, @msyyc ,  could you help to check the SDK breaking changes?

/azp run

@tadelesh, @qiaozha, @msyyc , could you help to check the SDK breaking changes?

Go breakings are from previous change and has already been released. I've rerun the CI and removed the wrong label.

approved for python breaking since it is not caused by this pr


Engine execution modes

Fixes Issue
This PR introduces a new feature, namely engine execution modes.
Description of Change
The change proposed introduces the concept of Execution Modes to the Engine with the following options:

Evidence Collection
Evidence Processing
Standalone (Default behaviour if no mode is specified)

Evidence Collection
The Engine skips the database and only executes Analyzers of the following phases  INITIAL, PRE_INFORMATION_COLLECTION, INFORMATION_COLLECTION, POST_INFORMATION_COLLECTION.
Evidence Processing
The Engine initialized the database and only executes Analyzers of the following phases  PRE_IDENTIFIER_ANALYSIS, IDENTIFIER_ANALYSIS, POST_IDENTIFIER_ANALYSIS, PRE_FINDING_ANALYSIS, FINDING_ANALYSIS, POST_FINDING_ANALYSIS, FINAL.
Standalone
The Engine behaves just like it today on master, initializing the database, execution all Analyzers of all the phases.
Have test cases been added to cover the new functionality?
yes

Can one of the admins verify this patch?

@jeremylong can you give an update if we can expect this PR to be merged and released soon?

@markrekveld at the latest the next release will be on July 23rd.

@jeremylong cool thanks for excepting and merging this PR.


Move anchors in screenshots and figure to right of heading

Can we do something to prevent the # getting orphaned on a new line?


chore: manifest validation RFC

Based on discussion https://github.com/cdk8s-team/cdk8s/discussions/936

@Chriscbr I love that you're still keeping an eye out and proving feedback! Hopefully i'll be able to return the favor soon :)


Home asisstant - ClimateEntityFeature

Version of the custom_component
0.3.0

Configuration
Using HACS
Describe the bug
I found this in my log:
Entity None (<class 'custom_components.intex_spa.climate.IntexSpaClimate'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature.

Thanks for reporting this, I will have a look at it.


rollback from PR#228

@royconst I'm taking the liberty of closing this PR so it doesn't confuse any onlookers lol


[clkmgr] clkmgr divider bypass during test mode.

hmm... i need to take a look at this one. our fpga does not like cascaded bufg's.
I'm personally more use to cg's not doing much in fpga anyways..but i'll need to remove some.

would be good get some input on whether this is the right way to go about this.
We have too many cascading bufg's, so i'm basically adding a parameter to remove it. It looks very hacky though.

Thanks @tjaychen for the PR. I don't see something fundamentally wrong with this but there are two things to be checked for the FPGA builds to keep working reliably:

Clock constraints: if we start to remove clock buffers and gates, Vivado is likely going to move around/optimize away parts. I am pretty sure the anchor points will be lost and the constraints can't be applied anymore. To prevent this, you need to define an intermediate output signal in the Xilinx specific primitives (prim_xilinx_clock_gating.sv, prim_xilinx_clock_mux2.sv) and assign a (* keep = "true" *)  attribute to those intermediate signals. Then the constraint must be changed to use this signal. I see that @msfschaffner did that for prim_xilinx_flop.sv and he put the attribute on the output port. Maybe that works, too. It should be checked by looking at the synthesis/implementation logs in Vivado.
We should make sure the last primitive in the path before the clock signal is distributed to the logic contains a real clock buffer/clock gate/clock mux. Otherwise, the clock signal won't be routed using dedicated clocking resources, resulting in potentially big skew. My recommendation is to make sure this is the case (you probably already did) and put a corresponding comment wherever a primitive is instantiated for which we disable the gate/buffer.

If we can't fulfill these points, I fear that the FPGA builds will stop working reliably sooner than later. We have been there already. It was blocking people, and caused a lot of pain to debug and fix.

hmmm... we need to think a bit about this.
So generally speaking the clock path on FPGA goes something like one of the three
root clk from pll (no clock bufg) -> directly to logic
root clk from pll (no clock bufg) -> clkmgr root clock gating (bufg) -> dividers (no bufg according to this PR) -> final clock gate (no bufg according to this PR)
root clk from pll (no clock bufg) -> clkmgr root clock gating (bufg) -> final clock gate (no bufg according to this PR)
So it sounds like for the first category we need to be careful and I should selectively add in bufg's for FPGA.
But what about the other two? There was a separate issue discussing clock dividers, and it seemed we all agreed to give it a try directly as logic, so I think this is still in-line with that.  The first case I probably should have another look.

@vogelpi
please have a look. I experimented with when exactly the tool starts complaining about cascading buffers.
I think this is okay ...for at least one variant of the FPGA. I haven't tried others.
In general though, I need to think a bit about the best way to structure this.
I've also added the buffers back so that the anchor point remains the same.


Numbers should not be shown as errors

Currently the digits 0 through 9 do not show as errors, but anything 10 or higher does. Either number highlighting as errors should show according to the rules for writing numbers ( http://www.grammarbook.com/numbers/numbers.asp ), or they shouldn't be highlighted at all.

It'd be nice to see this solved... though the odds of it seem low now

It's fixed in PR #34.  A fork with this and other changes is available on Github and NPM.


WIP Gain smoothing (do not merge)

This is an attempt to smooth gain solutions using the NIFTy library. It is still rather experimental because it will only parallelise with the processes scheduler and is only really meant for bandpass smoothing at this stage. There is still a bit of work before this will be ready to be used in anger

The v0.2.1-dev branch has been merged. This PR will need to be updated accordingly. Just shout if you need any help - I know it is irritating.

Did a little digging - I think that this branch changes the function signature of add_calibration_graph. This will need to be taken into account in the test fixtures.

mmm this will make quartical very hard to install - is it possible we can keep nifty as an optional dependency?

Yeah the signature has changed because I added the bypass_solver option. This is useful when smoothing and transferring gains because you don't have to crunch through all the vis data. I still need to modify the testing suite to account for this but at least I can pip install the branch again. @bennahugo I have just temporarily disabled 3.9 support because the dev branch of nifty I am depending on doesn't support it. I fully intent to support it before attempting to merge these changes


alsaUtils: 1.2.1 -> 1.2.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/alsa-utils/versions.
meta.description for alsaUtils is: "ALSA, the Advanced Linux Sound Architecture utils"
meta.homepage for alsaUtils is: "http://www.alsa-project.org/"

Quoted meta.homepage for RFC 45

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.2.2 with grep in /nix/store/wdabbyg5iyljcmjhid4bsyhdmbrrmyj5-alsa-utils-1.2.2

directory tree listing: https://gist.github.com/8dffecc84f4ff7d46913a93c5c55ada6

du listing: https://gist.github.com/9288a5c410b5a9197db4bda6aedceee8

Rebuild report (if merged into master) (click to expand)

40 total rebuild path(s)
12 package rebuild(s)
12 x86_64-linux rebuild(s)
12 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
12 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
MMA
alsaUtils
dwm-status
i3blocks-gaps
linuxband
mikutter
python27Packages.py3status
python37Packages.py3status
python38Packages.py3status
rakarrack
roon-server
solfege

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wdabbyg5iyljcmjhid4bsyhdmbrrmyj5-alsa-utils-1.2.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A alsaUtils https://github.com/r-ryantm/nixpkgs/archive/458a7772bcd4efa9ef20e8133d46929d8b374353.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wdabbyg5iyljcmjhid4bsyhdmbrrmyj5-alsa-utils-1.2.2
ls -la /nix/store/wdabbyg5iyljcmjhid4bsyhdmbrrmyj5-alsa-utils-1.2.2/bin

cc @AndersonTorres for testing.

@GrahamcOfBorg test mpd