Changing ratio for create_validation_set

Describe the bug
Good evening. I have a small newbie question when using the library.
Whenever we use custom dataset (or simply mvtec),
create_validation_set
is set True which the test set is divided into 50/50 for validation and test set respectively. Is there any way to change this ratio?
For example, if I have 1,000 test images, I want to use 300 for validation and 700 for test images.
Also, if I reduce the split ratio of 0.2 to lets say 0.05 (5%) , will this small percetange work as well for splitting normal set for test set?
Thank you in advanced.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Hardware and Software Configuration

OS: [Ubuntu, OD] Ubuntu
NVIDIA Driver Version [470.57.02]
CUDA Version [e.g. 11.4] 10.2
CUDNN Version [e.g. v11.4.120]
OpenVINO Version [Optional e.g. v2021.4.2]

Additional context

Add any other context about the problem here.

Currently, it is not possible to change the val/test split ratio from the default value of 0.5. However, we are currently working on a major refactor of the datamodules, so we could consider adding a configurable parameter for your use case. We will investigate the possibility and post any updates here.

Currently, it is not possible to change the val/test split ratio from the default value of 0.5. However, we are currently working on a major refactor of the datamodules, so we could consider adding a configurable parameter for your use case. We will investigate the possibility and post any updates here.

Thank you for your effort :) !

Currently, it is not possible to change the val/test split ratio from the default value of 0.5. However, we are currently working on a major refactor of the datamodules, so we could consider adding a configurable parameter for your use case. We will investigate the possibility and post any updates here.

Thank you for your effort 👍

Merged to feature branch in https://github.com/openvinotoolkit/anomalib/pull/760


[MessagingExtensions][Updatedcodesamplelinks][2785]

Docs Build status updates of commit d3c6bbb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/add-authentication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c3e4904:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/add-authentication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Wajeed-msft - kindly review the PR.
Thank you.

Docs Build status updates of commit 26ceb64:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/add-authentication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fb22f3b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/task-modules-and-cards/task-modules/task-modules-tabs.md
:warning:Warning
View
Details

msteams-platform/messaging-extensions/how-to/add-authentication.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/what-are-task-modules.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/task-modules/task-modules-tabs.md

Line 35, Column 32: [Warning-bookmark-not-found] Cannot find bookmark '#task-module-samples' in 'task-modules-and-cards/what-are-task-modules.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7b37788:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/add-authentication.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/task-modules/task-modules-tabs.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/what-are-task-modules.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 853cd1e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/how-to/add-authentication.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/task-modules/task-modules-tabs.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/what-are-task-modules.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


add more values to color type

This is great, but i think we should wrap them in a Color module

This is great


enable system metrics collection for uperf

Defaults to false

LGTM! verified with: https://github.com/cloud-bulldozer/benchmark-operator/blob/master/e2e/uperf/uperf.yaml

@mohit-sheth do we actually need this?, we have thanos metrics...

matching the timestamp can be a hassle, it is defaulted to false so maybe we only run it during readouts


Failed to open normal output file logs/nmap-2022-03-16_22:29:18 for writing

i get this error when use nmap

https://github.com/fsociety-team/fsociety use the new version


x86

I have a Windows 10 x64 Preview machine running Visual Studio 2015.  When I git clone the corefxlab project, I am able to compile a 64bit version of the console application and it works perfectly including nuget grabbing all necessary files.  If I set application to compile as x86, the application compiles but close immediately.  Would you expect that this would work with x86?

This whole area moved to https://github.com/dotnet/cli


How to use gdb for debug in apollo?

Can you provide a tutorial/example how to use gdb to debug in apollo? the log file method is helpful but not convenient enough for debugging (eg debug memory leak..)
For example: can you show how to debug planning module use gdb?
Thank you all.

Apollo is made up some submodules. These modules are built in bazel-bin/modules// .  You could use gdb to debug them. For example, You want to debug perception, you could use command as following.
gdb bazel-bin/modules/perception/perception
You could try this method. And please feel free to let me know if you have any other problem.

@muleisheng thanks for the input.. @lesun90 Please let me know if you try it.. Even I am looking for the same approach ..

Hi
perception may need some input params, for example, some configuration data (or files). I will check this issue by reviewing code. If any progress , I will let you know.

I suggest search for some tutorials on gdb for details.

Here is steps for debugging perception.

use following command to start debug perception
gdb bazel-bin/modules/perception/perception
set args for perception by using 'set args', here is a sample.
set args --flagfile=/apollo/modules/perception/conf/perception_lowcost.conf --stderrthreshold=3 --use_navigation_mode

You could try this method. It may solve your issue

Hi,
I have tried this method but when I go into gdb bazel-bin/modules/perception/perception.
set args --flagfile=/apollo/modules/perception/conf/perception_lowcost.conf --stderrthreshold=3 --use_navigation_mode
It is still not work.
The error message is can not open shared object file.
Thank you.

@muleisheng @fanghaos2014
Hi fang, have you done with that issue, debugging the perception module ?
I also want to debug the perception module with VScode. And I wonder the above problem was that user have to feed some required data for running perception module like playing ROS bag.
Can anyone give me some guide? Thanks.


[Layout] Combining flexWrap: 'wrap', flexDirection: 'row' causes React to fail silently.

Observe: https://rnplay.org/apps/5v2yRQ

@vjeux: want to write a quick error checker for this?

This appears to only be an issue if a child view is wider than the containing view

@jtremback is this still happening?
@ide @brentvatne always suspicious seeing the wrap/row combo since it's now fixed.

...the wrap/row combo since it's now fixed.

I think so too. Closing for now.


Improve Wal locking on BSD

Fix #203 using POSIX advisory locks.

This should resolve the remaining blocker mentioned in https://github.com/superseriousbusiness/gotosocial/issues/1753#issuecomment-2473443572 to use this driver on FreeBSD (and make it a good default choice on NetBSD, illumos, DragonFly…)


Request retry failure

We were uploading a BOSH release and got this error message:
Uploading release file:
  Performing request POST 'https://<IP_ADDRESS>:25555/releases?':
    Performing POST request:
      Post https://<IP_ADDRESS>:25555/releases?: read /Users/pivotal/.bosh/tmp/bosh-platform-disk-TarballCompressor-CompressSpecificFilesInDir037061428: bad file descriptor

After some digging, we found out that the issue was with our authentication token getting expired too quickly.
However, the error was too cryptic. It seems that the AdjustableClient retries the request if the response error code was 401. https://github.com/cloudfoundry/bosh-cli/blob/475d68ac4a964d383c86e21448773016e1ed061a/director/adjustable_client.go#L42-L49
But the repeated request contains a file descriptor which can not be used after the first request is finished.
It would be nice to have more descriptive error and update the retry mechanism to detect if a file handle is used in the request.

I have a similar problem. Is there a work around available?

@naruraghavan Check that you logged in to given BOSH environment. I.e. run bosh  releases.

Closing and re-opening to trigger a github story

Hello,
It looks like we have not responded to this in a reasonable time, and unfortunately a year has passed. Given this, we are going to close the issue, but please feel  free to re-open the issue. In doing so, a new Pivotal Tracker story will be generated, and we can revisit this.
Thanks again for submitting this, and apologies for closing without a proper resolution at this moment.
BOSH Systems Team - @aashah @luan @jaresty


Vector-Sort

Hackerrank problem link
https://www.hackerrank.com/challenges/vector-sort/problem?isFullScreen=true
Issue Checklist

[ ] If you have previously contributed to this repo, you declare that you have not made a pull request for more than one issue in this repo till now.
[✓ ] Your forked repo is up-to-date with the the origin remote.
[ ✓] Have you checked that the hackerrank problem you are raising is not already present in the repo?
[ ✓] Have you checked that the hackerrank problem you are raising is not raised by or assigned to another contributor?

Hacktoberfest Contributor

[ ✓] Are you a Hacktoberfest Contributor?

Any other Changes?
If you are raising an issue with some more changes, please provide the details here.

Hey @ManashAnand This hackerrank problem is already added to the repo. You may please take another problem.

Hello sir, can u assign me this issue. I would love to grab this opportunity.


scene.set_spectra_to_match taking to long

Hi @pmelchior , I ran a profiler on the scene_spectra_to_match function and as you can see, the interpolation function (in the resampling renderer) is taking most of the time (3 calls per rendering operation)

37 seconds overall
This can be reduced to 6.3 seconds by jitting the resample_obs function in interpolate.py
@partial(jax.jit, static_argnums=(1,2,3,4))
def resample_ops(kimage, shape_in, shape_out, res_in, res_out, interpolant=Quintic()):

Interpolating images is indeed expensive, so should we jit this function in the code?

I also noticed that this function takes long. Until now, we have only jitted the inner loops of the sampling and the fitting functions because jit usually works best when it sees large code blocks. But it might be a good idea to jit (some part of) the renderer. The most high-level function would be Observation.render Can you try if this helps?


Implement Metrics server.

Very simple http server. This PR does not include code for fetching metrics or tests, which are implemented in subsequent PRs.

Off, using git town has done a number on this poor git history


Cargo Clippy makes some good reccomendations

If you run cargo clippy it seems to make some good recommendations. Things like:
1.You multiply 0*4 in many lines. The answer would be 0. It might be faster to replace these.
2. You multiply items by 1, you don't need the 1.
3. You do some masking with a 0 (answer is only 0)
4. Some passing of small items might be faster if one does not use a reference.

Yes, I've looked at the clippy warnings. Most of them refer to code blocks like this:
loadu(inputs[0].add(block_offset + 0 * 4 * DEGREE)),
loadu(inputs[1].add(block_offset + 0 * 4 * DEGREE)),
loadu(inputs[2].add(block_offset + 0 * 4 * DEGREE)),
loadu(inputs[3].add(block_offset + 0 * 4 * DEGREE)),
loadu(inputs[0].add(block_offset + 1 * 4 * DEGREE)),
loadu(inputs[1].add(block_offset + 1 * 4 * DEGREE)),
loadu(inputs[2].add(block_offset + 1 * 4 * DEGREE)),
loadu(inputs[3].add(block_offset + 1 * 4 * DEGREE)),
loadu(inputs[0].add(block_offset + 2 * 4 * DEGREE)),
loadu(inputs[1].add(block_offset + 2 * 4 * DEGREE)),
loadu(inputs[2].add(block_offset + 2 * 4 * DEGREE)),
loadu(inputs[3].add(block_offset + 2 * 4 * DEGREE)),
loadu(inputs[0].add(block_offset + 3 * 4 * DEGREE)),
loadu(inputs[1].add(block_offset + 3 * 4 * DEGREE)),
loadu(inputs[2].add(block_offset + 3 * 4 * DEGREE)),
loadu(inputs[3].add(block_offset + 3 * 4 * DEGREE)),

Inlining these sorts of things, rather than hoping that the compiler will unroll a loop, is often important for performance. Once you write it out inline, the version that keeps the 0 * ... and 1 * ... is a lot easier to read, because it all lines up, and you can see the pattern more clearly.

I have a question about this. I've seen that src/portable makes heavy use of manual/explicit loop unrolling, even for small loops that just use 4/6/8 iterations. Is there still a benefit to doing this nowadays? If so, I recommend suing this crate


Ref ticket 117404629.

Enabled the pending test, and added clarifying comments regarding the cause of the crash to the involved parts of the code.
The comments are future maintainers to know about the dependency between the two places and of having to keep them in sync.

Hmm, looks like the test is failing on travis?

That is weird. I ran ginkgo -p cf/terminal here before making the PR, and the newly enabled test succeeded, as did all the others.
And running CF_HOME=$(pwd)/fixtures ginkgo -r -randomizeAllSpecs ... Fail here too.
Reducing to CF_HOME=$(pwd)/fixtures ginkgo -r cf/terminal . Fail. Second try later on OK.
Reducing to ginkgo -r cf/terminal . Fail. Second try later on OK.
Changing to ginkgo -p cf/terminal . OK. After this trying the others above again, and its ok.
This feels like some race in the tests, maybe ?
I will investigate more.

A bit more proof of the non-determinism, a copy of my terminal. I ran cf/terminal with -race active, thinking that it may be a race condition somewhere. While nothing is reported we clearly have an issue, with the first run succeeding the run immediately after reporting a test fail.
andreask@akucloud:~/Local/Go/src/github.com/cloudfoundry/cli> ginkgo -race cf/terminal
Running Suite: Terminal Suite
=============================
Random Seed:<PHONE_NUMBER>
Will run 77 of 77 specs

•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
Ran 77 of 77 Specs in 0.383 seconds
SUCCESS! -- 77 Passed | 0 Failed | 0 Pending | 0 Skipped PASS

Ginkgo ran 1 suite in 17.344730763s
Test Suite Passed

andreask@akucloud:~/Local/Go/src/github.com/cloudfoundry/cli> ginkgo -race cf/terminal
Running Suite: Terminal Suite
=============================
Random Seed:<PHONE_NUMBER>
Will run 77 of 77 specs

••
------------------------------
• Failure [0.002 seconds]
Table
/home/andreask/Local/Go/src/github.com/cloudfoundry/cli/cf/terminal/table_test.go:270
  REGRESSION: #117404629, having a space in one of the middle headers
  /home/andreask/Local/Go/src/github.com/cloudfoundry/cli/cf/terminal/table_test.go:59
    prints the table with the extra whitespace from the header stripped [It]
    /home/andreask/Local/Go/src/github.com/cloudfoundry/cli/cf/terminal/table_test.go:58

    expected to find "[watashi   no   atama!]" in actual:
    'watashi   no    atama!
    '

    /home/andreask/Local/Go/src/github.com/cloudfoundry/cli/cf/terminal/table_test.go:57
------------------------------
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Summarizing 1 Failure:

[Fail] Table REGRESSION: #117404629, having a space in one of the middle headers [It] prints the table with the extra whitespace from the header stripped
/home/andreask/Local/Go/src/github.com/cloudfoundry/cli/cf/terminal/table_test.go:57

Ran 77 of 77 Specs in 0.362 seconds
FAIL! -- 76 Passed | 1 Failed | 0 Pending | 0 Skipped --- FAIL: TestTerminal (0.51s)
FAIL

Ginkgo ran 1 suite in 3.196051409s
Test Suite Failed

Looking more closely at the failure it seems that for this case a space we expected to get trimmed, is not, causing the generation of 4 spaces between the columns instead of the expected 3. Unclear is, for now, why this happens only intermittently.

I think I see the issue, although not yet why it is intermittent.
printCellValue puts the value into the output buffer as is, including possible trailing spaces (which may be hidden inside of colorization too). It then computes the padding based on the visible size, which excludes the trailing space(s) (And sees them due to Decolorize).
I have to look into the ordering of trimming and transforms in all places, it looks like.
I am unhappy that I let this slip through.
OTOH, the non-determinism of the test result was unexpected.
Will make it difficult to asses if my changes are a proper fix or not.

Updated the PR with new fix (additional trimming before transform).
This passed the full testsuite a 100 times without fail, making me believe that I actually caught it now.

@andreas-kupries thanks for the fix


The latest vintage and the first CAPI release - versions of apps and components

Towards https://github.com/giantswarm/roadmap/issues/3057
User Story
As a Giant Swarm engineer, I want to know which are the versions of apps and components in the latest vintage release and in the first CAPI release, so that I can know what app and component versions my team has to test and support for vintage to CAPA migration.
Acceptance Criteria

Given my team owns an app which is a part of the vintage and/or CAPI release, when my team plans the development and the support of that app, then we have to know which versions of the app we have to support and maintain for the vintage to CAPA migration.
Given my team owns an app which is a part of the vintage and/or CAPI release, when my team releases a new patch/minor/major version of the app (patch to the version in the latest vintage release), then we have to know without any doubt if we can and if we have to create a new latest vintage release and if we can and if we have to create a new first CAPI release and if we have to re-test the migration from the new vintage release to the new first CAPI release.

Dependencies

[ ] TBA

Tasks

[ ] Define which app and component (e.g. Kubernetes, OS) versions we have in the latest vintage release.
[ ] Define which app and component (e.g. Kubernetes, OS) versions we have in the first CAPI release.
[ ] Define if we can create new vintage patch and minor releases (newer than v20.0.0), and if we should, then which types of changes we want to deliver in newer releases and which new versions of apps and components (e.g. only patches, or patches and minors) should be included in those new releases.
[ ] If we will be creating new vintage releases, then define if we will have to create also new CAPI releases with the same changes we made in the newer vintage releases. E.g. if new vintage release delivers a new patch version of app Foo, define if we have to create a new CAPI release that delivers that new patch version of the app Foo.

This story does not cover what to do when we release a new minor or major version of an app. I will try to cover that in another story.

Suggestion

Versions of all apps and components have to be the same in the latest vintage release and in the first CAPA release.
If we create a new latest vintage release where we include a new patch version of an app Foo, we also have to create a new first CAPA release where we include that new patch version of the app Foo.

If we want to do this (IMO we really have to, otherwise vintage to CAPA migration is too unpredictable and not reliable, as it can break with any new app version), we should decide what are the desired app versions for the last vintage release and first CAPA release:

Compare the app versions in the current latest vintage AWS release to app versions in the latest CAPA (ATM cluster-aws and default-apps-aws, in a few days cluster-aws and cluster chart).
For every app we pick the newer version of the above two as the desired app version.
We check with teams that own default apps if they need to release a newer patch or even a minor and if they need that very soon (e.g. this or next week). If the answer is yes, then this is our desired app version.

cc @yulianedyalkova @alex-dabija
cc @giantswarm/team-turtles @giantswarm/team-phoenix for general awareness about the topic here

I think we can close this issue because v25 is released and we already migrated a cluster.

Well, this on its own wouldn't cover the acceptance criteria. But I think we have everything in the releases, right @nprokopic ?

This has been a moving target and it has already changed few times.
Now when I take a look at the above tasks, which are just questions for which we should have answers, I think we mostly have the answers.

Define which app and component (e.g. Kubernetes, OS) versions we have in the latest vintage release.

Kubernetes version 1.25.x
Flatcar version 3815.2.x
When it comes to app versions, we are updating those only to fix bugs.

Define which app and component (e.g. Kubernetes, OS) versions we have in the first CAPI release.

The latest vintage and the first CAPI release should always be in sync as much as possible. Keeping app versions identical has shown to be not really possible, at least until now, as we had more than few cases where some app needed a newer version in v25 compared to v20.

Define if we can create new vintage patch and minor releases (newer than v20.0.0), and if we should, then which types of changes we want to deliver in newer releases and which new versions of apps and components (e.g. only patches, or patches and minors) should be included in those new releases.

As written above, we are updating vintage v20 release only to fix bugs.

If we will be creating new vintage releases, then define if we will have to create also new CAPI releases with the same changes we made in the newer vintage releases. E.g. if new vintage release delivers a new patch version of app Foo, define if we have to create a new CAPI release that delivers that new patch version of the app Foo.

App and component versions that are released in vintage as a v20 patch/minor release, should also be released in CAPI as a v25 release.

I think we can verify some of the above in the releases repo CI (at least to some extent), by checking app and component versions across different releases. Will create follow-up issues for Turtles, as we have already talked about release tests in the releases repo.


Issue with the Await and

Hi there,
Thanks alot for the library, this is just what I needed for my project. I fairly new to  APIs and I am trying to build an app that retrieves data from HassIO API. I have all the HassIO setup ready and I tried to retrieve data from the API using Python and it worked. However, I need to write my app using C#. I have installed your library and I tried to copy your code into an empty console program but I am getting these 2 errors that I didn't understand.
using System;
using HADotNet;
using HADotNet.Core;
namespace HASIO_API
{
class MainClass
{
    public static void Main(string[] args)
    {
        string toekn = "xxxxxxxx";
        string url = "http://hassio.local:8123";

        ClientFactory.Initialize(url, toekn);

        var entityClient = ClientFactory.GetClient<EntityClient>();

First Error The type or namespace name 'EntityClient' could not be found (are you missing a using directive or an assembly reference?)
        var filteredEntityList = await entityClient.GetEntities("sun.sun");

second error The 'await' operator can only be used within an async method. Consider marking this method with the 'async' modifier and changing its return type to 'Task'
        Console.WriteLine(filteredEntityList);

    }

}

}
Thanks alot

This isn't an issue with this library but i'll help you out.

import the Clients namespace at the top of your class using HADotNet.Core.Clients;
There's a couple ways you can handle this.  I'd suggest you look at the following microsoft documention:  https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/

Hi Mark,
I am very sorry about that. I spent the last night trying to figure it out and I realized that the there isn’t an issue with the library. I will delete that issue. I my programming skills are basic and limited to frontend development. This is the first time I work with APIs backend development. I am using your library for my PhD thesis. One small suggestion, you might want to have more documentation. Also it would be very good if you could add a couple of examples.
Best regards,
Lorans
From: Ryan Markle<EMAIL_ADDRESS>Reply-To: qJake/HADotNet<EMAIL_ADDRESS>Date: Saturday, February 15, 2020 at 8:06 AM
To: qJake/HADotNet<EMAIL_ADDRESS>Cc: Lorans Alabood<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [qJake/HADotNet] Issue with the Await and  (#2)
This isn't an issue with this library but i'll help you out.

import the Clients namespace at the top of your class using HADotNet.Core.Clients;
There's a couple ways you can handle this. I'd suggest you look at the following microsoft documention: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/qJake/HADotNet/issues/2?email_source=notifications&email_token=AJCZ5DCEUFHXKMM6QLLYNATRDAAHTA5CNFSM4KVOZLIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL3MTXA#issuecomment-586598876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJCZ5DHWDYDH642AGXC3QOTRDAAHTANCNFSM4KVOZLIA.

@rmarkle Thank you for helping out. For some reason I am not receiving notifications about issues in this repo, so I missed this! Strange. 🤔
@loransAlabood I think that's a great idea, I will make a note to add additional documentation and a possible example project for newcomers such as yourself. Thanks!


Testing

...I think we should talk about testing, since in my experience that has been instrumental in ensuring that all the components integrate well with each other.
Originally posted by @ahshabbir in https://github.com/UTDNebula/nebula-api/pull/98#pullrequestreview-1062798704
Initial discussions begin here:
https://github.com/UTDNebula/nebula-api/discussions/101

Has anyone tried sending requests?

A seemingly useful resource for tackling this:
https://medium.com/rate-engineering/go-test-your-code-an-introduction-to-effective-testing-in-go-6e4f66f2c259

Do we still want a blackbox integration test for the container? I'd imagine its not worth the dev time, since it would involve the following:

Spin up a mongo instance
Load it with data
(build?) and spin up a api container
Use dockertest to orchestrate everything and hit the endpoints, check the results

In addition, dockertest is really heavy duty, it takes a lot of resources and it only works with a docker daemon. I think instead we should close this issue and include this as the focus for the API redesign.

I'd agree that a more lightweight approach is desired, and I think doing testing as planned in the API redesign is for the best.
That being said, I'd like to keep using this issue as the basis for testing discussion so that we have past context to work with.

Closing this as not planned for now, will reference in a future testing issue.


youtube-dl URL open error

youtube-dl very rarely throws a timeout error when trying to open a URL.
We could try wrapping this in a try/except, but that seems real hacky

Should also consider a max try amount in the try-except sequence


Update request about your code

The code you provided has been immensely beneficial to my studies, and I sincerely hope that you will continue to provide updates.

Maybe later. I am quite busy at the moment.


chocolatey package should use batch file redirects rather than modify the path variable

The chocolatey package could use this improvement, and it will be easier once some work-in-progress in chocolatey are done.  Reference: https://github.com/marcelklehr/nodist/pull/23

@marcelklehr Should the chocately package be phased out in favor of the NSIS installer?

Yep, chocolatey support was removed for now, see https://github.com/marcelklehr/nodist/issues/112


Fix auto merge conflict 5799

File name Spark33XShims.scala in branch-22.06 is Spark330PlusShims.scala in branch-22.08
No conflicts other than above. Fixes https://github.com/NVIDIA/spark-rapids/pull/5799
NOTE: This needs to be committed with a merge commit, not squashed!

build


Plex not getting notified/updated

Hi, everything was working flawless tull I recently noticed that my plex server gets nor notified when the TV Show/episode got converted.
Sonarr is calling the script and everything gets converted but the plex library gets not updated any longer.
I'm on the latest plex and sonar version and also updated your script to the latest version but it's just not working any longer.
Any ideas ?

Not a fix... but as workaround u can try and have Sonarr push an update to Plex :)?

What program are you having notify plex to refresh?
Sent from my iPhone

On Aug 5, 2016, at 17:26, Moreno Sint Hill<EMAIL_ADDRESS>wrote:
Not a fix... but as workaround u can try and have Sonarr push an update to Plex :)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Same here. Sonarr is no longer notifying Plex to update. Neither is CouchPotato. Was working like a charm a couple of weeks ago.

For me it's working again.
What I did is in the .initial file of mp4_automaton in the plex section, I updated the token with a new one and it started to work again.

Make sure all your info is updated. Also to avoid plex scanning mid conversion you can set up the Automator script to do the notification instead by configuring autoProcess.ini
Sent from my iPhone

On Aug 8, 2016, at 22:38, make92<EMAIL_ADDRESS>wrote:
For me it's working again.
What I did is in the .initial file of mp4_automaton in the plex section, I updated the token with a new one and it started to work again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Create adili0505

You created a file called
content/authors/adili0505

but we need to create
content/authors/adili0505/_index.md

Can you give it another go? It should be almost exactly as you did before but instead of typing adilil0505 in the filename box you'll type adili0505/_index.md. When you type the / github should know that `adili0505 should be a folder (not a file).

I think we closed this with #68 so I'll mark this as closed. Let me know if that isn't the case.


Add flags to control Disk_Size & unattended-up

Introduction
Issues:
During internal use of PICO for teaching purposes, two
issues often popped up:

Something kept breaking down (auth for example), due to
background updates
Students often used vs-code servers, which in a class of 90,
ate up the 10GB default disk space

proposed Fixes:
These changes implement:

"DISK_SIZE": An environment variable with value of the form
XGB with X being a numberic value, to control max disk size.
"disable-unattended-upgrades": A Flag in the anisble config to
uninstall unattended-upgrades, preventing unwanted updates on
private deployments.

Testing
I tested the deployment on Windows 10 deployment, backed with VirtualBox.
A. DISK_SIZE
In order to try out the disk resize utility, Try

bash: DISK_SIZE=20GB vagrant up
powershell:  $env:DISK_SIZE = "20GB"; vagrant up

The expected behaviour should be different disk size for the SHELL VM:
vagrant ssh shell
>> df -h

Result:
vagrant@picoCTF-shell-dev:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            985M     0  985M   0% /dev
tmpfs           200M  724K  199M   1% /run
/dev/sda1   19.4G  5.5G   13.9G  71% /
tmpfs           997M     0  997M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           997M     0  997M   0% /sys/fs/cgroup
tmpfs           200M     0  200M   0% /run/user/1000
picoCTF         238G  102G  137G  43% /picoCTF

B. unattended upgrades
The second change disables unattended upgrades. This feature is a bit more work to activate. (False Default)
Change infra_local/inventory.yml (see diff) to True. This should uninstall the unattended-upgrades.
Command:
sudo apt-get remove unattended-upgrades
In the result we see it's uninstalled.
vagrant@picoCTF-shell-dev:~$ sudo apt-get remove unattended-upgrades
/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py:12: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  from cryptography import x509
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'unattended-upgrades' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

FYI the semicolon in:

bash: DISK_SIZE=20GB; vagrant up

is likely a typo. (It breaks the command line into two "simple commands" in the terminology of bash. The variable assignment in the first command is not exported and therefore the second command cannot see it.)

FYI the semicolon in:

bash: DISK_SIZE=20GB; vagrant up

is likely a typo. (It breaks the command line into two "simple commands" in the terminology of bash. The variable assignment in the first command is not exported and therefore the second command cannot see it.)

Noted and fixed in the testing setup above.
Let me know in case I misunderstood it.

Noted and fixed in the testing setup above.
Let me know in case I misunderstood it.

Yes, this updated 2-line Bash example would work just fine. In the example, there are two simple commands and the first one sets an exported environment variable DISK_SIZE for all future child processes, which includes vagrant in the second command, but also all subsequent commands in the same shell environment (until DISK_SIZE gets unexported). This also means the Bash example achieves the same effect as the PowerShell example.

An alternative Bash-specific way to not change the shell environment for subsequent child processes is to use one simple command:
DISK_SIZE=20GB vagrant up
This syntax is explained in https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Environment:

The environment for any simple command or function may be augmented temporarily by prefixing it with parameter assignments, as described in Shell Parameters. These assignment statements affect only the environment seen by that command.

I don't know how to simply achieve the same effect in the current PowerShell.

Yes, this updated 2-line Bash example would work just fine. In the example, there are two simple commands and the first one sets an exported environment variable DISK_SIZE for all future child processes, which includes vagrant in the second command, but also all subsequent commands in the same shell environment (until DISK_SIZE gets unexported). This also means the Bash example achieves the same effect as the PowerShell example.

An alternative Bash-specific way to not change the shell environment for subsequent child processes is to use one simple command:
DISK_SIZE=20GB vagrant up
This syntax is explained in https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Environment:

The environment for any simple command or function may be augmented temporarily by prefixing it with parameter assignments, as described in Shell Parameters. These assignment statements affect only the environment seen by that command.

I don't know how to simply achieve the same effect in the current PowerShell.

Cool, updated and verified that it works.
Please let me know in case you would wanna change anything else in the actual patch. Also, where should I update the ReadMe?

Cool, updated and verified that it works.
Please let me know in case you would wanna change anything else in the actual patch. Also, where should I update the ReadMe?

@pranayga
Documenting DISK_SIZE could be done alongside the other Vagrantfile config variables here.
For disable_unattended_upgrades, I think the note in the Ansible inventory files is fine and in line with the existing options.

@pranayga
Documenting DISK_SIZE could be done alongside the other Vagrantfile config variables here.
For disable_unattended_upgrades, I think the note in the Ansible inventory files is fine and in line with the existing options.


[backport] Enforce input data is not object. (#6927)

Check for object data type.
Allow strided arrays with greater underlying buffer size.

Codecov Report

Merging #6938 (1bd7cf4) into release_1.4.0 (96f8843) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@                Coverage Diff                @@
##           release_1.4.0    #6938      +/-   ##
=================================================
+ Coverage          81.80%   81.83%   +0.03%
=================================================
  Files                 13       13
  Lines               3852     3859       +7
=================================================
+ Hits                3151     3158       +7
  Misses               701      701

Impacted Files
Coverage Δ

python-package/xgboost/core.py
82.63% <100.00%> (+0.01%)
:arrow_up:

python-package/xgboost/data.py
63.23% <100.00%> (+0.46%)
:arrow_up:

Continue to review full report at Codecov.

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


Feature Request: ARM Emulator

Most of CE apps are ARM.

Most of CE apps are ARM.

Hi! How are you?
Any progress on CE apps are ARM? Do you have some UWP prototypes of WCECL? =)
Best,
Andrey aka MediaExplorer

Most of CE apps are ARM.

Hi! How are you? Any progress on CE apps are ARM? Do you have some UWP prototypes of WCECL? =) Best, Andrey aka MediaExplorer

Glory to Ukraine! I'm good, thanks for asking.
I believe there won't be any further progress on this product since it's almost pointless nowadays.

SH-4 emulation could possibly allow CE-based Dreamcast games to run natively on Win32 too, which would be an absolutely cursed sight


Support array and left/right access via references

There are a few things going on here:

The members of AdditiveShare are made private again. This reduces the number of things that will need to be updated for vectorization.
Some vectorized AdditiveShares will be large, creating a need for access to the contents by reference in addition to by value.
Lays some groundwork for supporting simultaneous horizontal and vertical vectorization using BitDecomposed<AdditiveShare<T>>, where T is a Boolean array or similar bit vector type.

In cases where there is both horizontal and vertical vectorization, my plan is that the vertical (across records) is the inner vectorization, and the horizontal (vector-type values within one record) is the outer. My plan is that values of this sort will be stored in BitDecomposed<AdditiveShare<BitVec>>. (The most likely candidate for BitVec is a Boolean array, although for vertical vectorization, it should rarely be necessary to access individual elements of the vector, and disallowing such access except through special pack/unpack primitives may catch some bugs.)

I am going to remove the BorrowReplicated and ArrayAccessReplicated changes from this PR, because it seems like they're not important for the near-term vectorization changes -- if the only type of array element indexed within AdditiveShare is a single bit, then there may be small or even negative performance benefit of accessing by reference. It may be needed eventually, but I'll defer adding the code until the need is clear.


Rendering of USA map using geoAlbersUsa not as expected.

I've really enjoyed playing with this library - fills a much needed gap in javascript cartography!
I ran into an issue making a map of the US. I have geojson of US states from the US Census (https://www.census.gov/geographies/mapping-files/time-series/geo/carto-boundary-file.html; converted from shapefile to geojson using mapshaper). When I try to make a state map using bertin.js, I get this: https://observablehq.com/d/c5d2bf78b1e0534e
The most interesting thing about the rendering is that one state at a time will be stroked white, and you can trigger a change in the displayed state by mousing out of the cell.
I'm not sure what is causing this - maybe the Alaska and Hawaii inset in the AlbersUSA projection break things somehow?

The shapes are not in the winding order that D3 expects; try this import:
import {normalizeWindingInPlace} from "@fil/normalize-winding"
then call
cb_2021_us_state_500k = FileAttachment("cb_2021_us_state_500k.json").json().then(normalizeWindingInPlace)

Thanks, Fil! That was it. I thought I had checked the winding order when converting in mapshaper, but I guess not!


Missing argument in doc for Docker SSH passthrough

Gitea version (or commit ref):
Git version: 1.14.6
Operating system: Host Arch, Gitea in Docker

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Description
I reinstalled Gitea on a new Arch host in a Docker. I also transferred my Docker volume to the new container.
I followed the instructions here https://docs.gitea.io/en-us/install-with-docker/#ssh-container-passthrough to set the SSH passthrough, and I think the shell script that goes in /app/gitea/gitea on the host is missing something.
If I used ssh -p 2222 -o StrictHostKeyChecking=no<EMAIL_ADDRESS>"SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@" as advised, I was getting errors like this:
ssh: connect to host MY_HOST port 2222: Connection refused
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists

I fetched back my previous config and it add a -i /home/git/.ssh/id_rsa argument added:  ssh -i /home/git/.ssh/id_rsa -p 2222 -o StrictHostKeyChecking=no<EMAIL_ADDRESS>"SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@"
Is it normal? If yes, I should maybe do a simple PR to fix the doc? Thanks!

The doc has been updated recently

Thank you, have a nice day!


[BUG]: trying to migrate into neon

What version of drizzle-orm are you using?
0.27.2
What version of drizzle-kit are you using?
0.19.12
Describe the Bug
some kind of issue converting into sql:
jakey@mnymkr:~/itys$ sudo npm run generate

><EMAIL_ADDRESS>generate
> drizzle-kit generate:pg

drizzle-kit: v0.19.12
drizzle-orm: v0.27.2

No config path provided, using default 'drizzle.config.ts'
Reading config file '/home/jakey/itys/drizzle.config.ts'
3 tables
form_data 8 columns 0 indexes 0 fks
proponents 6 columns 0 indexes 1 fks
proponents_to_forms 2 columns 0 indexes 2 fks

[✓] Your SQL migration file ➜ src/lib/db/neon/drizzle/0000_noisy_pete_wisdom.sql 🚀
jakey@mnymkr:~/itys$ sudo npm run migrate

><EMAIL_ADDRESS>migrate
> tsx ./src/lib/db/neon/migrate.ts

{
  severity_local: 'NOTICE',
  severity: 'NOTICE',
  code: '42P06',
  message: 'schema "drizzle" already exists, skipping',
  file: 'schemacmds.c',
  line: '131',
  routine: 'CreateSchemaCommand'
}
{
  severity_local: 'NOTICE',
  severity: 'NOTICE',
  code: '42P07',
  message: 'relation "__drizzle_migrations" already exists, skipping',
  file: 'parse_utilcmd.c',
  line: '207',
  routine: 'transformCreateStmt'
}
PostgresError: syntax error at or near "`"
    at ErrorResponse (file:///home/jakey/itys/node_modules/postgres/src/connection.js:771:26)
    at handle (file:///home/jakey/itys/node_modules/postgres/src/connection.js:473:6)
    at TLSSocket.data (file:///home/jakey/itys/node_modules/postgres/src/connection.js:314:9)
    at TLSSocket.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:343:12)
    at readableAddChunk (node:internal/streams/readable:316:9)
    at Readable.push (node:internal/streams/readable:253:10)
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)

however, sql is good there is no backtick in here:
CREATE TABLE IF NOT EXISTS "form_data" (
	"id" serial PRIMARY KEY NOT NULL,
	"date_option" text NOT NULL,
	"timezone" text NOT NULL,
	"utc_time" timestamp NOT NULL,
	"local_time" text NOT NULL,
	"title" text NOT NULL,
	"tag" text,
	"created_at" timestamp with time zone DEFAULT now() NOT NULL
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "proponents" (
	"id" serial PRIMARY KEY NOT NULL,
	"form_id" integer,
	"team" text NOT NULL,
	"name" text NOT NULL,
	"email" text NOT NULL,
	"created_at" timestamp with time zone DEFAULT now() NOT NULL
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "proponents_to_forms" (
	"proponent_id" integer NOT NULL,
	"form_id" integer NOT NULL,
	CONSTRAINT proponents_to_forms_proponent_id_form_id PRIMARY KEY("proponent_id","form_id")
);
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "proponents" ADD CONSTRAINT "proponents_form_id_form_data_id_fk" FOREIGN KEY ("form_id") REFERENCES "form_data"("id") ON DELETE cascade ON UPDATE cascade;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "proponents_to_forms" ADD CONSTRAINT "proponents_to_forms_proponent_id_proponents_id_fk" FOREIGN KEY ("proponent_id") REFERENCES "proponents"("id") ON DELETE no action ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "proponents_to_forms" ADD CONSTRAINT "proponents_to_forms_form_id_form_data_id_fk" FOREIGN KEY ("form_id") REFERENCES "form_data"("id") ON DELETE no action ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

Expected behavior
i am hoping that it will create the tables in neon...
Environment & setup
wsl2:
{
	"name": "itys",
	"version": "0.0.1",
	"private": true,
	"scripts": {
		"dev": "vite dev",
		"build": "vite build",
		"preview": "vite preview",
		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
		"generate": "drizzle-kit generate:pg",
		"migrate": "tsx ./src/lib/db/neon/migrate.ts"
	},
	"devDependencies": {
		"@sveltejs/adapter-auto": "^2.0.0",
		"@sveltejs/adapter-cloudflare": "^2.3.2",
		"@sveltejs/kit": "^1.20.4",
		"@types/better-sqlite3": "^7.6.4",
		"drizzle-kit": "^0.19.12",
		"sass": "^1.64.2",
		"svelte": "^4.0.5",
		"svelte-check": "^3.4.3",
		"svelte-preprocess": "^5.0.4",
		"tslib": "^2.4.1",
		"typescript": "^5.0.0",
		"vite": "^4.4.2"
	},
	"type": "module",
	"dependencies": {
		"@neondatabase/serverless": "^0.5.6",
		"better-sqlite3": "^8.5.0",
		"dotenv": "^16.3.1",
		"drizzle-orm": "^0.27.2",
		"itty-router": "^4.0.14",
		"postgres": "^3.3.2",
		"tsx": "^3.12.7"
	}
}

I had the same exact error as your. I used npx drizzle-kit push:pg --config=./drizzle/config.ts which resolved the issue. Also, append ?sslmode=require to your database URL, if you haven't already.

@avnav0 I had the same exact error as your. I used npx drizzle-kit push:pg --config=./drizzle/config.ts which resolved the issue. Also, append ?sslmode=require to your database URL, if you haven't already.

just saw this :/
i ended up just going with turso to keep it moving...

It should work as expected in latest, if you see this issue, feel free to reopen this ticket


Dragging a tab out of the window produces closes all tabs and opens the dragged tab again.

Description
Dragging a tab out of the window produces closes all tabs and opens the dragged tab again.
Steps To Reproduce
Open multiple tabs. Drag and drop one of them out of the window's rectangle
Expected behavior
It would be expected to detach that tab and open (without reloading if possible).
Files Version
<IP_ADDRESS>
Windows Version
Windows 11 10.0.22000.434
Relevant Assets/Logs
2022-01-22 13:42:08.5200|INFO|OnActivated|App activated by CommandLineLaunch
2022-01-22 13:42:57.3686|INFO|OnActivated|App activated by Protocol
2022-01-22 13:42:58.7958|INFO|GetDrivesAsync|Drive added: C:, Fixed
2022-01-22 13:43:00.9626|INFO|IsRunningOnArm|Running on ARM: False
2022-01-22 13:45:29.2769|INFO|OnActivated|App activated by Protocol
2022-01-22 13:45:30.8237|INFO|GetDrivesAsync|Drive added: C:, Fixed

Same as #7246


Feat: add Spanish localization

Translated UI labels and messages

Hello, I have just introduced a tool to sort the JSON keys and check secondary language locales against the primary (en), in order to detect missing keys, and remove redundant / unused keys.
I will merge your PR as-is into a "staging" PR branch, then apply the sorting + checks, then create a new PR against master.

Follow-up PR: https://github.com/daisy/ace-gui/pull/64


Correct note

closes https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/3977
It seems this is the correct note for MM for file shares, taken from https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/public/migration/mm-fileshare-copy-to-migrations.md

@JoanneHendrickson
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@JoanneHendrickson
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@JoanneHendrickson
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Enable ClientCli to read partition's high-watermark

To validate if cluster can recovery from chaos environment, we need a way to validate cluster before and after torture.
Currently, it is achievable by using --high-watermark on ClientCli.Validate command.
Consider single partition scenario, this is how we do it.

we run validate command with a totally 100 transactions
torture service nodes
run validate command with a totally 100 transactions, with --high-watermark=99, which indicates client is expecting 100+100=200 callbacks

Obviously, this is not ideally. First, we need to calculate cumulated transactions in the past every time we want to use --high-watermark. Second, if validation failed in the middle, we cannot tell what's the current high watermark (for the next run).
Talked to Chris Riccomini, as an alternative, we can read "current high watermark" (server one, not storage one) from server or metrics. This way, validate command would always work without asking user for current high watermark.
Now, the question is, how ClientCli suppose to know "current high watermark".
We can add a HighWaterMarkRequest to allow WaltzClient retrieve currently high watermark (committed) of given partition, which simplifies the implementation of ClientCli.Validate.

PR merged!


Update %Z specifier with known issue

There is a known issue in the Universal C Runtime %Z specifier that it is unlikely we will be able to change for application compatibility (the issue has existed since 2015).  Instead of %Z -> ANSI_STRING and %wZ -> UNICODE_STRING, the specifier acts like the %S specifier and expects the "opposite" type of string from the API used.

Kimberly Terlap,Otis Chaunceyjr hacked my phone,emails,they have my drivers
license,birth certificate,social security card,consealed weapons permit,all
my credit cards,fir the past 4 years and have been using it,they are
subscribed to this and all threads relating to gifthub,using this yo hack
Mt phone, I have changed phones ,phone numbers,emails,to no email. Police
no help,if you can suggest anything yo make it stop,please help me.
On Mon, Jan 23, 2023, 2:27 PM learn-build-service-prod[bot] <
@.***> wrote:

Learn Build status updates of commit 38231c6
https://github.com/amyw-msft/cpp-docs/commits/38231c66d279779e4f924ca48bfe3323bf073f51
:
✅ Validation status: passed
File Status Preview URL Details
docs/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions.md
https://github.com/amyw-msft/cpp-docs/blob/patch-18/docs/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions.md
✅Succeeded
For more details, please refer to the build report
https://buildapi.docs.microsoft.com/Output/PullRequest/813c26e3-f1ed-5796-cab4-24adc659812f/202301231924456929-4381/BuildReport?accessString=22a8623d60eb08bec2893e7a8de8c104acac3fbd944c61ddd29ae84fcad6ed0a
.
Note: Broken links written as relative paths are included in the above
build report. For broken links written as absolute paths or external URLs,
see the broken link report
https://ops.microsoft.com/#/repos/813c26e3-f1ed-5796-cab4-24adc659812f?tabName=brokenlinks
.
For any questions, please:

Try searching the learn.microsoft.com contributor guides
https://review.learn.microsoft.com/en-us/help/?branch=main
Post your question in the Learn support channel
https://teams.microsoft.com/l/channel/19%3A7ecffca1166a4a3986fed528cf0870ee%40thread.skype/General?groupId=de9ddba4-2574-4830-87ed-41668c07a1ca&tenantId=72f98bf-86f1-41af-91ab-2d7cd011db47

—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/cpp-docs/pull/4381#issuecomment-1400866165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMGSYQAHIBFVWIMIATB33YTWT3LTTANCNFSM6AAAAAAUEHDFS4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@TylerMSFT

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

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

#sign-off


Reddit: publish comments and votes, backfeed replies

This is one of my biggest silos still.

oh wow, interesting! :+1:

if anyone's interested in tackling this, i've written up comprehensive instructions on how to add a new silo to bridgy. feel free to jump in!

mentioned on irc today by @sknebel and @gkbrk.

API docs. looks like you can post, search for links, fetch comments etc, but the Reddit terminology is a bit confusing since i don't use it.

@stedn soft launched this tonight! so cool! example: https://brid.gy/reddit/bonkerfield


New Synapse Southeast Asia Gateway IP

I found this new IP which which our Southeast Asia Azure Synapse Analytics Workspace worker is resolving to:
REDACTED.southeastasia1-a.worker.database.windows.net
<IP_ADDRESS>
If this is part of a larger range, then please update the article accordingly.

@k8s42 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

The southeastasia1-a.worker.database.windows.net IP address is for the back-end SQL Server where your database is located. This is used when the Connection Policy is set to Redirection as outlined here https://docs.microsoft.com/en-us/azure/azure-sql/database/connectivity-architecture#connection-policy

#please-close


Replace incorporated net.ricecode components

As a developer of HSC I would like to get use the Java String Similarity library and drop the incorporated version of it from my source (as it meanwhile became publicly available on Maven Central).

Hi @ascheman, I would like to discuss and work on this enhancement. Let me know

Thanks a lot, @Prankurtiwari, please add the library as new dependency and drop the overtaken classes. I hope it is not much more than this?
Are you on (the Hacktoberfest) Discord? You can reach out to me (gerdaschemann) so we could have a chat if you run into problems (or if you need any other support).

Thanks for quick response @aschema. I will look into the project a

Thanks a lot, @Prankurtiwari, please add the library as new dependency and drop the overtaken classes. I hope it is not much more than this?

Are you on (the Hacktoberfest) Discord? You can reach out to me (gerdaschemann) so we could have a chat if you run into problems (or if you need any other support).

Thanks a lot, @Prankurtiwari, please add the library as new dependency and drop the overtaken classes. I hope it is not much more than this?
Are you on (the Hacktoberfest) Discord? You can reach out to me (gerdaschemann) so we could have a chat if you run into problems (or if you need any other support).

Thanks @ascheman for the quick response. I will try to resolve this issue and raise the PR.
Yes i am on the discord Hacktoberfest server. I have sent you the request and pinged you on discord. I will let you know if I need any assistance. Thanks :)

Change PR : https://github.com/aim42/htmlSanityCheck/pull/351/files
Please review


Change excluded_territories.json To .toml

For the scope of this PR, please refer to issue #148 .

In get_ensemble.R, we should consider adding a command line argument for --base_hub_path to use here:
exclude_territories_path <- fs::path(
  base_hub_path,
  "auxiliary-data",
  "excluded_territories.toml"
)
if (fs::file_exists(exclude_territories_path)) {
  exclude_territories_toml <- RcppTOML::parseTOML(exclude_territories_path)
  excluded_locations <- exclude_territories_toml$locations
} else {
  stop("TOML file not found: ", exclude_territories_path)
}

In get_ensemble.R, we should consider adding a command line argument for --base_hub_path to use here:

Sounds good to me! After you add it, please also change it accordingly here https://github.com/CDCgov/covid19-forecast-hub/blob/d5a6f7dd7e2b9f1ec6824d23c0de44f46e9d4cb8/.github/workflows/create_ensemble.yaml#L42

Not sure if this is correct (i.e. using $(pwd) for the directory):
- name: generate ensemble
  run: |
    TODAY=$(date +'%Y-%m-%d')
    REF_DATE=$(date -d "$TODAY + 2 days" +'%Y-%m-%d')
    Rscript src/code/get_ensemble.R --reference-date "$REF_DATE" --base_hub_path "$(pwd)"

Tagging DHM: @dylanhmorris

Not sure if this is correct (i.e. using $(pwd) for the directory):
- name: generate ensemble
  run: |
    TODAY=$(date +'%Y-%m-%d')
    REF_DATE=$(date -d "$TODAY + 2 days" +'%Y-%m-%d')
    Rscript src/code/get_ensemble.R --reference-date "$REF_DATE" --base_hub_path "$(pwd)"

Tagging DHM: @dylanhmorris

GH Actions runs from the root of the repository, so you can just do "." . But $(pwd) should also work, do we need parenthesis around it though?

I think . is clearer. Notice that src/code/get_ensemble.R is a path too, so that same line of code already assumes our working dir is the repo root.

so that same line of code already assumes our working dir is the repo root.

This is why I used $(pwd).
Re: https://github.com/CDCgov/covid19-forecast-hub/pull/159#issuecomment-2536926312
I will use "."


Jenkins Container Agent support for on-premise Jenkins master???

We use this instruction and the Jenkins Container Agent seems to work in ACI using the Jenkins on Azure.
However, in real life scenarios, user can have Jenkins master on-premise, and the container needs to have connection to on-premise and need to be able to work with Jenkins master on premise.
Do you have additional instructions for Jenkins Container Agent for Jenkins master on premise???
Additional references:

Same post here: https://social.msdn.microsoft.com/Forums/en-US/e618a674-777f-4c8a-99cb-7d4fcb876f5c/jenkins-container-agent-for-jenkins-master-onpremise?forum=AzureContainerServices
Will work off that.


Are transitive imports supported?

hello 👋🏼
I am trying to generate code from the OpenTelemetry protobuf definitions.
When configuring a subset of protobuf files to be processed, I encounter a "File not found" error from protoc.
I guess this is because there is no way to specify the "--proto-path=" option in the protoc command run on generation?
That option seems to be needed to resolve imports.
For completeness, my build config is below.
I have a submodule in the proto-src/ directory, and with/without absolute paths, the import in https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/resource/v1/resource.proto#L19 is not resolved.
    const protoc_step = protobuf.RunProtocStep.create(b, protobuf_dep.builder, target, .{
        // Output directory for the generated zig files
        .destination_directory = b.path("src/model"),
        .source_files = &.{
            // Add more protobuf definitions as the API grows
            b.pathJoin(&.{ wd, "proto-src/opentelemetry/proto/common/v1/common.proto" }),
            b.pathJoin(&.{ wd, "proto-src/opentelemetry/proto/resource/v1/resource.proto" }),
            b.pathJoin(&.{ wd, "proto-src/opentelemetry/proto/metrics/v1/metrics.proto" }),
        },
        .include_directories = &.{
            // Don't forget to add the relevant folder here as well
            b.pathJoin(&.{ wd, "proto-src/opentelemetry/proto/common/v1" }),
            b.pathJoin(&.{ wd, "proto-src/opentelemetry/proto/resource/v1" }),
            b.pathJoin(&.{ wd, "proto-src/opentelemetry/proto/metrics/v1" }),
        },
    });

WDYT? Thanks 🙏🏼

Maybe I'm also confused, apparently -I is equivalent to --proto_path, but when running protoc externally with the added flag it fails anyway 🤷🏼

Hello @inge4pres, thank you for your issue.
Using another generator with protoc, do you manage to generate the thing you'd like to to have using zig-protobuf ? Which flags were necessary for it?
We have an include_directory option in RunProtocStep, that should use the -I flag in the background.
If you have small project strapped of anything unnecessary that reproduces the problem, it'd give us more way to help you.
Thanks again.

Also, with the verbose flag, you should be able to see the exact protoc command used by RunProtocStep

Hey @Arwalk thanks for the hint, the verbose is not adding any more useful information to the already printed output.
Though I guess since it's failing to build even when calling protoc directly, it's not an issue in this library but a problem in how protoc expects includes...
I will close this issue and post back once I find the solution to the protoc error 👍🏼

I confirm the problem is not in zig-protobuf, rather in how include_directories should be used when imports are declared in protobuf files.
protoc requires that imports are expressed as relative paths to --proto_path (or -I).
For reference, the solution for me was to use include_directories as follows:
        .include_directories = &.{
            "proto-src/",
        },

In the end, relative paths are working just fine, and there's no need to use absolute paths by adding the build working directory.

Thank you for your analysis and your time. I really appreciate it.


Enable XLA on TensorFlow ROCm port

PR to enable XLA on TensorFlow ROCm port

@parallelo I've revised the PR which contains logic to make XLA for ROCm built properly. Since XLA is disabled by default when we configure TensorFlow build, I'm wondering how to change that in ci_build?

Good question.  Not totally certain yet, but it seems like this line would be a likely candidate:  https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/blob/develop-upstream/tensorflow/tools/ci_build/xla/linux/rocm/run_py3.sh#L32

Looks like as long as "--config=xla" is set at build time ( https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/blob/develop-upstream/tensorflow/tools/ci_build/xla/linux/rocm/run_py3.sh#L41 ) we should be fine?

@parallelo I'd like reproduce the build error reported by CI locally. Could you let me now if tensorflow/tools/ci_build/xla/linux/run_py3.sh the script I should execute?

Currently, CI is running this command from the base of tensorflow-upstream:
tensorflow/tools/ci_build/ci_build.sh ROCM ./tensorflow/tools/ci_build/linux/rocm/run_py3_core.sh

The ci_build.sh command builds a ROCm docker image, starts the container and runs the provided script.  The run_py3_core.sh script kicks of a tensorflow build and run unit tests.
We have not tried with the tensorflow/tools/ci_build/xla/linux/run_py3.sh script yet.  Perhaps its use of --config=xla would help, but not certain yet.

In xla/linux/run_py3.sh, we might also need an updated configure command to enable XLA.

CI log shows:
ERROR: /var/lib/jenkins/workspace/tensorflow-upstream-unit-tests/bazel-ci_build-cache/.cache/bazel/_bazel_jenkins/eab0d61a99b6696edb3d2aff87b585e8/external/llvm/BUILD:446:1: Traceback (most recent call last):
	File "/var/lib/jenkins/workspace/tensorflow-upstream-unit-tests/bazel-ci_build-cache/.cache/bazel/_bazel_jenkins/eab0d61a99b6696edb3d2aff87b585e8/external/llvm/BUILD", line 447
		gentbl(name = (target["lower_name"] + "..."), <4 more arguments>)
	File "/var/lib/jenkins/workspace/tensorflow-upstream-unit-tests/bazel-ci_build-cache/.cache/bazel/_bazel_jenkins/eab0d61a99b6696edb3d2aff87b585e8/external/org_tensorflow/third_party/llvm/llvm.bzl", line 32, in gentbl
		native.genrule(name = ("%s_%s_genrule" % (name,...)), <5 more arguments>)
genrule rule 'amdgpu_target_gen__gen_tgt_intrinsic_genrule' in package '' conflicts with existing genrule rule, defined at /var/lib/jenkins/workspace/tensorflow-upstream-unit-tests/bazel-ci_build-cache/.cache/bazel/_bazel_jenkins/eab0d61a99b6696edb3d2aff87b585e8/external/llvm/BUILD:447:5

I did solve this in my local repository but turns out I inadvertently changed offending bazel script INSIDE bazel cache instead of the original source repository. I've just amended the PR.

test log shows:
2018-06-07 15:10:46.927359: F tensorflow/compiler/tf2xla/xla_op_registry.cc:264] Check failed: it != registry.backends_.end() Unknown backend XLA_GPU_JIT

let me look into it.


Image: support transparency

Hi!
I wonder if it is possible to plot a second int[,] 2D array over a heatmap, with Alpha opacity, and RGB color?
So this second "heatmap" is actually not a heatmap, but a fixed color overlay, where there are some NULL values where we want total transparency (full view of the underlaying real heatmap), and fixed values representing the RBG color.
I understand that, I could somehow hack together the heatmap's colorbar in a way, so when I clip the int[,] finite values they get the required color, but then this will affect the real heatmap too.
Maybe someone can bring up some workaround? Maybe a new Plottable type could be useful, like a limited heatmap? Or a special Heatmap with fixed color? --> Plot.AddFixColorMap(boolArray, double alpha, double red, double blue, double green);
Where bool[,] boolArray is a bool matrix, with False values at positions where we want total transparency, and the given opacity alpha level and color at the True values to render?
I also consider to create a special Bitmap, and plot it over the heatmap, but this might not be the best approach? -->
https://learn.microsoft.com/en-us/dotnet/desktop/winforms/advanced/how-to-use-a-color-matrix-to-set-alpha-values-in-images?view=netframeworkdesktop-4.8
Thanks for any suggestions! :)

I'll merge #2313 into this issue and track progress here:
Add an Alpha = 1.0 property to the Image plot type.

https://scottplot.net/cookbook/4.1/#image

This may also allow overlaying a semitransparent image above a heatmap which may help @bukkideme in #2277

Somewhere along the line this feature was added
double?[,] values = {
    { 1, 7, 4, 5 },
    { 9, 3, 2, 4 },
    { 1, 4, 5, 8 },
    { 7, 2, 4, 2 }
};

double?[,] opacities = {
    { 1, 1, 1, 1 },
    { 1, 0, 1, 0 },
    { 1, .75, .5, 0 },
    { 1, .8, .6, .4 }
};

var hm = plt.AddHeatmap(values);
hm.Update(values, opacity: opacities);

I added it to the changelog because I don't think it was properly reported or documented in the cookbook previously ecb40cc6b753d00e94fddade03420cb994168e34


macOS dings when key is pressed

Steps to Reproduce

Run flutter create ding_bug.
Update the files as follows: ... (this is the sample in the LogicalKeyboardKey docs)

main.dart
/// Flutter code sample for LogicalKeyboardKey

// This example shows how to detect if the user has selected the logical "Q"
// key.

import 'package:flutter/material.dart';

import 'package:flutter/foundation.dart';
import 'package:flutter/services.dart';

void main() => runApp(MyApp());

/// This is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: MyStatefulWidget(),
      ),
    );
  }
}

/// This is the stateful widget that the main application instantiates.
class MyStatefulWidget extends StatefulWidget {
  MyStatefulWidget({Key key}) : super(key: key);

  @override
  _MyStatefulWidgetState createState() => _MyStatefulWidgetState();
}

/// This is the private State class that goes with MyStatefulWidget.
class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  // The node used to request the keyboard focus.
  final FocusNode _focusNode = FocusNode();
// The message to display.
  String _message;

// Focus nodes need to be disposed.
  @override
  void dispose() {
    _focusNode.dispose();
    super.dispose();
  }

// Handles the key events from the RawKeyboardListener and update the
// _message.
  void _handleKeyEvent(RawKeyEvent event) {
    setState(() {
      if (event.logicalKey == LogicalKeyboardKey.keyQ) {
        _message = 'Pressed the "Q" key!';
      } else {
        if (kReleaseMode) {
          _message =
              'Not a Q: Key label is "${event.logicalKey.keyLabel ?? '<none>'}"';
        } else {
          // This will only print useful information in debug mode.
          _message = 'Not a Q: Pressed ${event.logicalKey.debugName}';
        }
      }
    });
  }

  @override
  Widget build(BuildContext context) {
    final TextTheme textTheme = Theme.of(context).textTheme;
    return Container(
      color: Colors.white,
      alignment: Alignment.center,
      child: DefaultTextStyle(
        style: textTheme.headline4,
        child: RawKeyboardListener(
          focusNode: _focusNode,
          onKey: _handleKeyEvent,
          child: AnimatedBuilder(
            animation: _focusNode,
            builder: (BuildContext context, Widget child) {
              if (!_focusNode.hasFocus) {
                return GestureDetector(
                  onTap: () {
                    FocusScope.of(context).requestFocus(_focusNode);
                  },
                  child: const Text('Tap to focus'),
                );
              }
              return Text(_message ?? 'Press a key');
            },
          ),
        ),
      ),
    );
  }
}

3. Tap and press 'Q'
Expected results: it saying 'Press the Q key'
Actual results: same as expected, but with a alert sound on MacOs

I was able to reproduce.  This sounds more like a proposal since the current API is expected to work as it is.

flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-2.0.pre.448, on Mac OS X 10.15.7 19H114 darwin-x64, locale en)
    • Flutter version 1.26.0-2.0.pre.448 at /Users/pedromassango/Code/flutter_master
    • Framework revision eeb7c261f2 (3 hours ago), 2021-01-20 23:04:03 -0500
    • Engine revision dde6b7e8ea
    • Dart version 2.12.0 (build 2.12.0-246.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 52.2.5
    • Dart plugin version 203.6912

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.7 19H114 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 87.0.4280.141

! Doctor found issues in 1 category.

I was able to reproduce.  This sounds more like a proposal since the current API is expected to work as it is.

flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-2.0.pre.448, on Mac OS X 10.15.7 19H114 darwin-x64, locale en)
    • Flutter version 1.26.0-2.0.pre.448 at /Users/pedromassango/Code/flutter_master
    • Framework revision eeb7c261f2 (3 hours ago), 2021-01-20 23:04:03 -0500
    • Engine revision dde6b7e8ea
    • Dart version 2.12.0 (build 2.12.0-246.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 52.2.5
    • Dart plugin version 203.6912

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.7 19H114 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 87.0.4280.141

! Doctor found issues in 1 category.

/cc @gspencergoog
I forgot when we implemented passing keyDown events to the next responder that by default keyDowns that propagate all the way to the top of the hierarchy without being handled will beep.
Options:

Require Flutter apps that don't want to beep to claim to handle all keyDown events
Make the default behavior to not pass keyDown/keyUp (but still performKeyEquivalent:; I think that will work), and have an API that can be used to enable event propagation for add-to-app.

/cc @gspencergoog
I forgot when we implemented passing keyDown events to the next responder that by default keyDowns that propagate all the way to the top of the hierarchy without being handled will beep.
Options:

Require Flutter apps that don't want to beep to claim to handle all keyDown events
Make the default behavior to not pass keyDown/keyUp (but still performKeyEquivalent:; I think that will work), and have an API that can be used to enable event propagation for add-to-app.

If there's any way to enable developers (even in non-add-to-app scenarios) to say "I can't handle this" about a key, and have the system beep, that would be ideal. Failing that, it's ok if we just have a way to manually do the beep (honoring all the relevant settings in the sounds control panel, of course). That's basically what we do with haptic feedback on mobile platforms -- we have an API to reproduce the effect.

If there's any way to enable developers (even in non-add-to-app scenarios) to say "I can't handle this" about a key, and have the system beep, that would be ideal. Failing that, it's ok if we just have a way to manually do the beep (honoring all the relevant settings in the sounds control panel, of course). That's basically what we do with haptic feedback on mobile platforms -- we have an API to reproduce the effect.

If there's any way to enable developers (even in non-add-to-app scenarios) to say "I can't handle this" about a key, and have the system beep, that would be ideal.

There is: the (as of recently) current behavior. The description of this issues was for some reason reversed during triage; I've now restored the original.
The problem is that if a view accepts focus (as FlutterView does), any keyDown that the view (i.e., the application, from the perspective of a non-add-to-app Flutter developer) doesn't explicitly say it handles will beep. We need to decide whether we actually want that behavior.

If there's any way to enable developers (even in non-add-to-app scenarios) to say "I can't handle this" about a key, and have the system beep, that would be ideal.

There is: the (as of recently) current behavior. The description of this issues was for some reason reversed during triage; I've now restored the original.
The problem is that if a view accepts focus (as FlutterView does), any keyDown that the view (i.e., the application, from the perspective of a non-add-to-app Flutter developer) doesn't explicitly say it handles will beep. We need to decide whether we actually want that behavior.

Seems like reasonable behaviour if we document how to say that we did handle it. On macOS that seems to be the way things are intended to work, right?

Seems like reasonable behaviour if we document how to say that we did handle it. On macOS that seems to be the way things are intended to work, right?

On macOS that seems to be the way things are intended to work, right?

I thought it was only for views that declared that they accepted focus, but I tested a hello-world macOS app and it does indeed beep on every keypress with just a stock NSView, so yes, this is WAI. Based on that, closing.
@treeplate If you want to avoid beeping for keys you should use the FocusNode's onKey, to actually handle the event (i.e., return true), rather than just listening for the existence of the event.

On macOS that seems to be the way things are intended to work, right?

I thought it was only for views that declared that they accepted focus, but I tested a hello-world macOS app and it does indeed beep on every keypress with just a stock NSView, so yes, this is WAI. Based on that, closing.
@treeplate If you want to avoid beeping for keys you should use the FocusNode's onKey, to actually handle the event (i.e., return true), rather than just listening for the existence of the event.

@treeplate Handling the key with the FocusNode.onKey is easiest when done with a Focus widget:
Widget build(BuildContext context) {
  return Focus(
    onKey: (FocusNode node, RawKeyEvent event) => true,
	child: ...
  );
}

That will manage the focus node for you (inserting and removing it as necessary).

@treeplate Handling the key with the FocusNode.onKey is easiest when done with a Focus widget:
Widget build(BuildContext context) {
  return Focus(
    onKey: (FocusNode node, RawKeyEvent event) => true,
	child: ...
  );
}

That will manage the focus node for you (inserting and removing it as necessary).

We should update the docs for LogicalKeyboardKey to answer that, since if I understand the OP correctly they literally just copied that example.

We should update the docs for LogicalKeyboardKey to answer that, since if I understand the OP correctly they literally just copied that example.

(Reopening per my last comment.)

This issue also seems to prevent use of KeyboardListener and RawKeyboardListener when targetting macOS, as their onKey: argument takes void Function(FocusNode, RawKeyEvent)? rather than KeyEventResult Function(FocusNode, RawKeyEvent)? and so cannot return KeyEventResult.handled.

No, it doesn't prevent them from being used, but that's also not their intended purpose. The widgets KeyboardListener and RawKeyboardListener are purely listeners: they don't handle keys, they just tell you about the events.
If you want to handle keys, you should use a Focus widget with an onKey handler, as I mentioned above, although with the current version of the API, instead of returning true, you'd return KeyEventResult.handled. If all you want to do is prevent the "ding", you can place the Focus widget above the MaterialApp or CupertinoApp in you application (basically, very near the runApp, above any other handlers).

Yes, I am now using a Focus widget in that way thanks to the discussion above.
I'd not really registered that they are "Listeners" rather than "Handlers", thanks for clearing that up. It's unfortunate that the KeyboardListener docs don't call that out and point readers to the very comprehensive Focus docs.

That's excellent news, thanks for your replies here too!

Using Focus widget to prevent a beep sound is not suitable solution if we are using text input like TextFiled widget.
because TextField widget it not working if we return KeyEventResult.handled in onKeyEvent callback.
If you are using text input, such as the TextFiled widget, using the Focus widget to prevent beeps is not an appropriate solution.
This is because the TextField widget does not work when KeyEventResult.handled is returned in onKeyEvent callback.
Is there any other solution?

@cjng96 Please file a new issue for the TextField issue you are describing so that we can triage it separately, ideally with a small sample app that reproduces the problem.

@treeplate Handling the key with the FocusNode.onKey is easiest when done with a Focus widget:
Widget build(BuildContext context) {
  return Focus(
    onKey: (FocusNode node, RawKeyEvent event) => true,
	child: ...
  );
}

That will manage the focus node for you (inserting and removing it as necessary).

Hey, this has been open for a while. I guess this has been forgotten a bit.
I am replying to the comment and updating the solution since the API has changed.
You have to return KeyEventResult now instead of a boolean.
Focus(
    onKey: (focus, onKey) => KeyEventResult.handled,
)

The proposed solution handling the key with the FocusNode.onKey with a Focus widget does not work. The system sound still occurs.


feature idea: decentralized block explorer

spike: TrueBlocks

Hi guys. I found you through some weird tweet somewhere. Love that the first visit to your GitHub, I find this. I work on TrueBlocks. Love to learn more about your project. I'll look for a discussion link and and join you there.

Thanks for reaching out @tjayrush. Actually, we met briefly at ETHDenver this year while searching for teams 😎 We don't have a public telegram/discord server set up yet, but we'll get that started soon.
I've barely had a chance to take a look at TrueBlocks, but saw the recent release announcement and thought a block explorer would make a ton of sense within Grid. Look forward to learning more about the project and discussing an integration.


Enable DROP COLUMN at sql feature (F033) resource file

retest this pls
unrelated maven surfire issue

retest this please


GEOMESA-2642,GEOMESA-2562 Upgrade to GeoTools 21.1 and GeoServer 2.15.1

Updated dependency versions and performed slight refactoring to account for new GeoTools packages.
Signed-off-by: Josh Fix<EMAIL_ADDRESS>

@joshfix I pushed some changes to your branch to clean up the poms a little and to add the cqs list. I'm going to open CQs with Eclipse for the new jars - we'll have to wait for approval, then we can merge. thanks again for getting it working!

force pushed to fix the merge

@jnh5y could you ping the pmc for:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20102
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20103
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20105
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20114 (hasn't ticked over to pmc status yet, but should in the next hour or so)
Thanks!

@jnh5y could you ping the pmc for:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20102
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20103
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20105
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20114
edit: all are in pmc status now ~(hasn't ticked over to pmc status yet, but should in the next hour or so)~
Thanks!

I've emailed the PMC.  Should take a few days, etc, etc.

Is there any special coordination that needs to occur with this PR if I also want to submit a PR for updating the geoserver plugin to the same versions?  Or can that be handled completely independently?

@joshfix there's no official coordination needed - feel free to put up a corresponding PR against geomesa-geoserver, which builds against this snapshot. We won't be able to merge it until this PR is merged, but we can review/comment/test in the meantime. Generally, with transitive PRs, I just add a comment back to the original so that people are aware. Thanks,

@jnh5y any last objections or should i push the button?