Support for KBDLLHOOKSTRUCT information data

Hi,
Is the library support the keyboard information about the source of the key press, i.e this information?
https://learn.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-kbdllhookstruct

Hi! Thanks for asking!
SharpHook supports most of the information provided in KBDLLHOOKSTRUCT in its keyboard events:

vkCode - available in the KeyboardEventData.RawCode field, although you should use KeyboardEventData.KeyCode instead as it's the same on all platforms whereas RawCode is platform-dependent.
scanCode - not available and you don't really need it unless you're doing some super low-level stuff.
flags - partially available:

LLKHF_EXTENDED - not available.
LLKHF_LOWER_IL_INJECTED - not available.
LLKHF_INJECTED - available as part of the UioHookEvent.Reserved field, or the HookEventArgs.IsEventSimulated property.
LLKHF_ALTDOWN - available indirectly through the UioHookEvent.Mask field.
LLKHF_UP - available implicitly based on the event type.

time - not available if you need Windows-specific message time, but the Unix timestamp is available in the UioHookEvent.Time field or the HookEventArgs.EventTime property.
dwExtraInfo - not available.

If you need information on the source of the key press as in whether it's injected or real, then you have the IsEventSimulated property. If you want to know the source of the key press as in the keyboard on which it was actually pressed, then this information is not available unfortunately.


Updates to standalone templates

Standalone report updates:

Status tooltips (failures, skip reasons, etc.)
Using constellation name, if defined, as column header

(The default payload encoding seems to have been included as well...)

This is probably easier for you to resolve than for me.


[Backport 2.x][Tiered Caching] Clear up disk cache(ehcache) files during node shutdown

Description
Backport https://github.com/opensearch-project/OpenSearch/pull/12734
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
~[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)~
~[ ] Public documentation issue/PR created~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@andrross @msfroh Need help on this one.

@reta Can you help with this one?


chore: build and test IT - naive approach

Closing as done in https://github.com/googleapis/google-cloud-java/pull/8062


feat: add created by in tasks and results proto

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

C++ does not redefine Task and Result objects.


Serial validation for grab requests

Add serial validation for grab requests.
Grab requests handled:

xdg-shell move,resize
wl-shell move,resize

Xwayland shell events cannot be validated because there is no serial information.
We thought serial validation was necessary for setting selections, but the the protocol doesn't specify how to validate these serials and Weston does no serial validation, so we won't do any validation of those after all.
fixes #511

This does slightly change the behavior of grabs in a way that is more restrictive, but more in line with the text of the protocol.
You cannot start an interactive drag when more than one button is pressed on the pointer or there is more than one touch point down on the touch device.

Thanks!


Handled missing packages in AudioGenerator.py

Thank you for pull request! but could u indent it by 4 spaces? thank you

Done!

oh ur already in the server?

oh ur already in the server?

Yeah, I'm chad#1082


Fast typing drops characters in editor

From<EMAIL_ADDRESS>on 2014-03-03T01:15:51Z
Spyder 2.2.4
Python 2.7.5 |Anaconda 1.8.0 (x86_64)| (default, Oct 24 2013, 07:02:20)
[GCC 4.0.1 (Apple Inc. build 5493)] on darwin
Mac OS X 10.7.5 (Lion)
What steps will reproduce the problem?
Fast typing in the editor causes characters to drop at random.  The result is that I waste a lot of time with manual editing and back-tracking to insert dropped characters.  I don't run into this with other text editors.
Example:  typing "asdf " (with space) quickly and repeatedly yields:
asdf asdf asdfasdf asdf asdfsdf asdfsdf asdf asdf asdf sdfasdfasdf
Disabling all code introspection/analysis does not seem to help.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1747

From contrebasse on 2014-03-07T08:38:59Z
Maybe it is related ? https://bitbucket.org/iep-project/iep/issue/247/lost-key-hits

From ccordoba12 on 2014-03-10T10:59:34Z
Thanks contrebasse. Anaconda on Mac is using a quite old version of PySide and (almost certainly) this is what is causing the issue.
Let's hope Continuum guys update it in its next version.
Status: WontFix


ARROW-17406: [C++] Failing to build the C++ Lib with tests

Ref: https://issues.apache.org/jira/browse/ARROW-17406
Pin boost-cpp to a version which doesn't raise warning.

We can use C++14 by specifying -DCMAKE_CXX_STANDARD=14.

@kou Do other parts of the library support c++14?
(Also are you suggesting to add this flag to the build snippet on the webpage that walks through the build process?)

Yes. We have CI jobs for C++14 and C++ 17.
If our documents miss it, could you update our documents?

Sure. Will look into that. Thanks @kou !

@kou Can we get this merged quickly to resolve CI failures?

Which CI failures are you thinking? There are many CI failures for now (oh...) but it seems that there are no CI failures related to this.

Sorry, I mean that merging this PR allows to fix AppVeyor, so we should do it quickly.

Ah, I see. But this is not a real fix. This is just a workaround.
I'll take a look at the CI failure tomorrow. Please wait for a while. If you can't wait, you can merge this.

Unblocking AppVeyor would be nice. As for the real fix, there is now some hope that we move to C++17 soon.

Besides updating the doc, nothing actionable on for me right? Thanks :)
cc: @pitrou @kou

Continuous discussion about AppVeyor failure: https://github.com/apache/arrow/pull/13903
(I think that we can fix the AppVeyor failure by removing CI jobs on AppVeyor instead of merging this change.)


Custom ImagePullPolicy and ImagePullSecrets

Which problem is this PR solving?
Following this https://github.com/jaegertracing/jaeger-operator/issues/1768
I have implemented a way to use custom ImagePullPolicy and ImagePullSecrets on the Jaeger components, allowing to customize it a bit more.
It's a feature I needed and it is a very minor and harmless change so I hope you approve :)
Short description of the changes
This is quite simple really.
I've added both corev1-defined objects to the JaegerCommonSpec and then handled it within the util.Merge function
And then I have added the policy and secrets from JaegerCommonSpec to the relevant containers being set up.
If any of them is not set, Kubernetes default is taken.
Following any other JaegerCommonSpec properties, those defined under Jaeger.Spec.JaegerCommonSpec are overwritten by the internal ones (Jaeger.Spec.Agent.JaegerCommonSpec,Jaeger.Spec.AllInOne.JaegerCommonSpec, etc.)
CRD Changes:

All deployment modes now have imagePullPolicy and imagePullSecrets fields, including the Jaeger object itself
Agent mode has already had this property before. This has been changed within the Go program to Jaeger.Spec.Agent.JaegerCommonSpec.ImagePullSecrets instead of Jaeger.Spec.Agent.ImagePullSecrets and is being handled. Kubernetes-wise nothing has changed.

Test cases have been added and relevant tests updated. Also tested manually on a minikube environment.

Hey @edenkoveshi, thanks for your contribution! ImagePullSecrets are already handled in https://github.com/jaegertracing/jaeger-operator/pull/1740. What you think about placing your ImagePullPolicy changes on top of this?

Funny I've missed it.
I guess it can be added quite easily, I'll see to it later today


Connection to the db fails

The server has already started:
➜  debug git:✗ ./terrier
[2020-06-20 22:34:23.598] [network_logger] [info] Listening on port 15721
But when try to connect to the server, fails get:
➜  bin  psql --host=localhost --port=15721
psql: error: could not connect to server: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Any suggestion about how to figure out what's the problem?

You have to specify -d terrier to connect to the default database.

➜  bin git:(master) ✗ psql --host=localhost --port=15721 -d terrier
psql: error: could not connect to server: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The same result. Something to initialize?

You have to specify -d terrier to connect to the default database.

➜ bin git:(master) ✗ psql --host=localhost --port=15721 -d terrier
psql: error: could not connect to server: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The same result. Something to initialize?

Without seeing a Wireshark trace I couldn't say for sure.

Seems refused after send 8 bytes: 00 00 00 08 04 d2 16 30

Unable to reproduce locally.


Incorrect display of oldest changes

Environment
Host
GROWI on GROWI.cloud

item
version

OS
---

GROWI
4.2.3

node.js
x.y.z

npm
x.y.z

Using Docker
yes/no

Using growi-docker-compose
yes/no

(Accessing https://{GROWI_HOST}/admin helps you to fill in above versions)
Client

item
version

OS
windows 10

browser
Google Chrome 86.0.4240.198

How to reproduce? (再現手順)

Update a page over 20 times.
Display history view.
Scroll down to the page's oldest changes.

What happens? (症状)

In the oldest changes, the entire page content appears to have been added

What is the expected result? (期待される動作)

Diffs from the previous revision are displayed correctly.

Note

Thank you for reporting the Issue.
The modified version will be released in v4.2.4.
Please wait for the next release


Composite ops set 1

To remove the following ops from tt_eager

[x] pow
[x] power_fp
[x] rad2deg
[x] selu
[x] sinh
[x] softsign
[x] std_hw
[x] subalpha
[x] swish
[x] tanhshrink
[x] threshold
[x] trunc
[x] var_hw
[x] where
[x] xlogy

merged #10824


Fix undefined values to be assumed as null values

Problem:
When sending an graphql query that contains the only required values all undefined values in the query get replaced by null in the default sql query mutation builder. This makes the definition of default values when creating a table useless cause the default value is never
applied to the database.
Solution:
This fix makes sure that only defined values in the graphQL mutation get translated to the
appropriate postgres type and the default pg query builder has a chance to use default instead of null.
The current unit tests do not cover this scenario. I need some generell help how to add such a scenario in postgraphql.
I will also try to improve the query generation in the insertLoader by only including columns defined in the graphql mutation.

In PgCollection we use the keyword default to insert not null but the default value for the column:
https://github.com/calebmer/postgraphql/blob/a88a9836722c5d42c7cae93fe901c095d7c704f6/src/postgres/inventory/collection/PgCollection.ts#L154
Where are you getting this issue?

Example following schema:
create table test (
  id serial primary key,
  name text not null,
  created_at timestamp default now()
)

Now I use your default generated mutation.
mutation createTest($input: TestInput!) {
  createTest(input: $input) {
    test {
      id
      name
      createdAt
    }
  }
}

with following input
{
  input: {
    name: 'Test'
  }
}

The resulting query will look like (just an example).
with __local_0__ as ( insert into "public"."test" ("id", "name", "created_at") values (default, $1, default) returning * ) select row_to_json(__local_0__) as object from __local_0__

The id get correctly replaced by default I think cause it is a serial type. But the created_at value gets replaced by null which is not intended by my query. I never set it to null. Cause you internally choose a nullable type instead of simply ignoring it. Which makes default types useless. This is what my fix prevents by removing them from the values that should be handled.
The resulting query after my fix is:
with __local_0__ as ( insert into "public"."test" ("id", "name", "created_at") values (default, $1, null) returning * ) select row_to_json(__local_0__) as object from __local_0__

cause I removed it from the fields variable.

I updated my comment to hopefully clarify the problem. If it is intended behaviour how can I then force to use the default value defined in my schema via the graphql query?
Thanks for your help and thanks for this project!

Ahhhh, I see - thanks for expanding. So if I understand you right, you're saying:
"When an insert takes place (createTest), if you omit a nullable field from the $input variable then the value of that field will automatically be set to null (rather than left as undefined as would be the case for a non-nullable field); thus the "use default value if undefined" logic does not fire, preventing the default value from being used and causing null to be stored instead"

Yes :)

@mlegenhausen Yes, the advantage is we can bundle a lot of inserts together with varying inputs and execute via one SQL statement with multiple VALUES().
@calebmer I'm not sure where the change should be made to handle this; is the issue coming from graphql-js or from us?

When an insert takes place mutation createTest($input: TestInput!) {...}, if you omit a nullable field from the $input variable then the value of that field will automatically be set to null (rather than left as undefined as would be the case for a non-nullable field); thus the "sql.query`default` if undefined" logic does not fire, preventing the default value from being used and causing null to be stored instead.

I have not verified this issue myself.

@benjie I bet it’s us. There is some coercion going on, so I wouldn’t be surprised if we switched undefined to null somewhere 😊
@mlegenhausen we just merged: https://github.com/calebmer/postgraphql/pull/367 which contains a fix you mention in your OP that you wanted to make. Would this fix part of the issue?

@calebmer it sounds like the same problem, I will evaluate the changes and give you feedback today.

@calebmer it does not solve the issue. Now the query from my given example looks like
with __local_0__ as ( insert into "public"."test" ("name", "created_at") values ($1, null) returning * ) select row_to_json(__local_0__) as object from __local_0__

The default values where removed but still all undefined values in my mutation parameter gets replaced by null.

Ok in some conditions I get the default type working when combining not null and default in my column definition. But it seems impossible to defined a column with default and null allowed (currently not a use case for me). My updated table looks like this
create type state as enum (
  'draft',
  'released'
);

create table test (
  id serial primary key,
  state state not null default 'draft',
  name text not null,
  created_at timestamp not null default now()
)

created_at does not work as expected. But when I now apply the same principal on state I got the following error back via graphiql.
{
  "data": {
    "createTest": null
  },
  "errors": [
    {
      "message": "Input value must be an enum variant.",
      "locations": [
        {
          "line": 16,
          "column": 3
        }
      ],
      "path": [
        "createTest"
      ]
    }
  ]
}

This seems more of a graphql bug which is not in the scope of this pull request.
To sum up what this pull request does: It allows the definition of columns that have a default value and allow null by not falling not back to a null when the column/key was not explicitly set to null via the graphql mutation.

I’m going to have to think some more on whether or not this change will not have far reaching impacts. My initial intuition is that it would break some [isTypeOf](https://github.com/calebmer/postgraphql/blob/6cf9ac7d1b28440523d6938e0c993d007f0169ed/src/interface/type/BasicObjectType.ts#L51-L65 or https://github.com/calebmer/postgraphql/blob/6cf9ac7d1b28440523d6938e0c993d007f0169ed/src/postgres/inventory/type/PgClassType.ts#L65-L67) checks that currently exist, but I do want to either remove isTypeOf or find a way to allow much looser objects.
An alternative implementation which likely has less far reaching impacts would be to get nulls instead returning defaults here: https://github.com/calebmer/postgraphql/blob/6cf9ac7d1b28440523d6938e0c993d007f0169ed/src/postgres/inventory/collection/PgCollection.ts#L166. On second thought that wouldn’t work because a null is different from undefined from a GraphQL perspective, so that wouldn’t work 😣
Do you know why the tests are failing?

@mlegenhausen I think the enum fail might be because for some reason PostGraphQL uppercases the enum values; so you need to provide them in uppercase? If this isn't the issue just dismiss this comment, but it caught me out when I started.

@calebmer the last thought was mine too. The problem seems complex and I think is out of my current knowledge about postgraphql. I will investigate the test errors.
@benjie Same error even when I switch all my enum values to uppercase. I will open a separate issue for this one.

So I just ran into this issue, from the default enum scenario, but also from another not discussed — restricted insert permissions. I have something like the following:
create table test (
  id serial primary key,
  name text not null,
  deleted_at timestamp
);
grant insert ("name") on table "test" to "example_user";

The problem is that the insert query generated by postgraphql attempts to insert null into deleted_at:
insert into "public"."test" ("name", "deleted_at") values ($1, null) returning *

I thought about it a bit more, and decided it's fine to allow insert to include a deleted_at value. But regardless it was a bit of a gotcha.
So I'm still stuck with the Input value must be an enum variant. error, and for the moment need to just pass through the correct value. What's the latest thinking on this issue? Is there anything I can do to help move this issue forward?

This might already be addressed in v4: https://github.com/postgraphql/graphql-build/blob/7165585cea78c3f1f8192841de4199fdc3db4f2b/packages/graphql-build-pg/src/plugins/PgMutationCreatePlugin.js#L152-L178
One issue with the above code, however, is if you have a default on a nullable column but you want to explicitly set it to null the above code ignores that and just uses the default.

(Sorry that prettier messes up the formatting of ternaries inside of template literals, I've not had a chance to look at that yet - I'll probably just move the ternaries outside.)

Interesting! It sounds like I should dive in and play around with v4 :smile:. Will report back when I've had some time to look into it.

Does anyone know where we are on this issue currently?

I'm closing this because I believe it's fixed in v4; but please check and if it isn't raise an issue ASAP so we can fix it before release 👍


lomiri.qtmir: init at unstable-2023-02-23

Description of changes
Working towards #99090.
QtMir (AFAICT) is a Qt Platform Abstraction (QPA) plugin to make Qt a compositor for Mir (as in, the non-Wayland platform). It is used by Lomiri itself to start & communicate with Mir for graphics & desktop interactions.
QtMir only supports Mir 1.x officially. Mir 1.x can be packaged, but it has some problems. Upstream is aiming to convert QtMir from Mir 1.x (a Mir-only server) and MirAL to Mir 2.x (a Wayland compositor framework) and Miroil. We're going to do the same thing Debian has done in their Lomiri effort and package an upstream branch with the Mir 2.x migration instead of going with the regular QtMir. I have thus opted to change the pname and add some comments about this situation.
Upstream tests have not been made Mir 2.x compatible yet, so there's sadly no testing for this. Launching the qtmir-demo-client on top of my Miriway session (I assume any Wayland compositor will do) works, as does the entire Lomiri ecosystem on my WIP branch.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

No PR dependencies anymore, but need to cleanup & upstream patches.


invalid code

When inserting the code from steps 4-5 into the custom canvas, the webchat stops from loading

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

ID: 68d60dd9-05e9-9c78-7d7b-53b26a92af06
Version Independent ID: 282e50ba-61cf-6574-94ad-4dcf82b71a72
Content: Configure single sign-on - Power Virtual Agents
Content Source: power-virtual-agents/configure-sso.md
Service: dynamics-365-ai
GitHub Login: @iaanw
Microsoft Alias: iawilt

Thanks for your questions! The best place for product troubleshooting - is the Power Virtual Agents forum at https://powerusers.microsoft.com/t5/Forums/ct-p/pva_forums - if you repost your questions there an engineer, PM, or someone with a similar issue/solution should be able to help you.

Thanks for your questions! The best place for product troubleshooting - is the Power Virtual Agents forum at https://powerusers.microsoft.com/t5/Forums/ct-p/pva_forums - if you repost your questions there an engineer, PM, or someone with a similar issue/solution should be able to help you.


Add support for Abosom.org

Further to our discussion in discord.abosom.org, we would be delighted to have our coin added to the list of supported projects for these forks of Electrum moving forward.
Abosom is a Dash codebase fork which includes DIP003 and Proof of stake. Our full codebase can be found here
We are looking forward to working with you guys in the future.
Danke
Zenyatta

@ahmedbodi do you think It would be useful to add our scope of work document here?
It may inform other projects of what is required for electrum, why its needed and the sort of timescale for implementation.
What are your thoughts?

This has been done and we are testing with the most recent release.

Closed by #32


How to definition RequestProvider?

No definition or class found or resolvable for "Yiisoft\RequestProvider\RequestProviderInterface" while building "Yiisoft\RequestProvider\RequestProviderInterface".

Do your app based on one of Yii3 application templates (yiisoft/app or yiisoft/app-api)?
Configuration here: https://github.com/yiisoft/request-provider/blob/master/config/di-web.php. It's should use automatically.

Do your app based on one of Yii3 application templates (yiisoft/app or yiisoft/app-api)?
Configuration here: https://github.com/yiisoft/request-provider/blob/master/config/di-web.php. It's should use automatically.

Yes！
In config/common/params.php
[
'middlewares' => [
        RequestCatcherMiddleware::class,
        ErrorCatcher::class,
//        Subfolder::class,
//        Locale::class,
        Router::class,
    ],
...
]

In config/web/di/application.php
RequestProviderInterface::class => [
            'class' => RequestProvider::class,
            'reset' => function () {
                /** @var RequestProvider $this */
                $this->request = null;
            },
        ],

final class EditPostRequest extends AbstractInput implements RulesProviderInterface
{

    #[RouteArgument('id')]
    private ?int $id = null;

    #[Body('title')]
    private string $title;
}

But can't get body value.

config/web/params.php
return [
    'yiisoft/input-http' => [
        'requestInputParametersResolver' => [
            'throwInputValidationException' => true,
        ],
    ],
];

No exception output.

What format of POST request body? Json?

Yes, It's POST method, and content-type is JSNO

You should parse JSON before it. Try use https://github.com/yiisoft/request-body-parser

It's this? Already exists.
<?php

declare(strict_types=1);

use App\Middleware\ExceptionMiddleware;
use Yiisoft\Config\Config;
use Yiisoft\DataResponse\Middleware\FormatDataResponse;
use Yiisoft\Request\Body\RequestBodyParser;
use Yiisoft\Router\FastRoute\UrlGenerator;
use Yiisoft\Router\Group;
use Yiisoft\Router\RouteCollection;
use Yiisoft\Router\RouteCollectionInterface;
use Yiisoft\Router\RouteCollectorInterface;
use Yiisoft\Router\UrlGeneratorInterface;

/**
 * @var Config $config
 * @var array $params
 */

return [
    UrlGeneratorInterface::class => [
        'class' => UrlGenerator::class,
        'setEncodeRaw()' => [$params['yiisoft/router-fastroute']['encodeRaw']],
        'setDefaultArgument()' => ['_language', 'en'],
        'reset' => function () {
            $this->defaultArguments = ['_language', 'en'];
        },
    ],

    RouteCollectionInterface::class => static function (RouteCollectorInterface $collector) use ($config) {
        $collector
            ->middleware(FormatDataResponse::class)
            ->middleware(ExceptionMiddleware::class)
            ->middleware(RequestBodyParser::class)
//            ->addGroup(
//                Group::create('/{_language}')->routes(...$config->get('app-routes')),
//            )
            ->addGroup(
                Group::create()->routes(...$config->get('app-routes')),
            );

        return new RouteCollection($collector);
    },
];

Check that your POST request contains content type header with value "application/json".

->middleware(RequestBodyParser::class)

This modifies the original request, so Request Catcher holds unactual object. You should refresh it with pasting RequestCatcherMiddleware after ->middleware(RequestBodyParser::class)

It's ok, Thank you so much.


Add promotion for renewing your tax credits

Trello card
Description
Here I have replaced the Driving licence counterpart promotion with the Renew your tax credits.
This takes up the second position amongst the already exiting department promotions.
This change is mainly (Cosmetic) html tags, text and image replacements.
Before

After

Think we can remove homepage/counterpart-driving-licence.jpg now...
Also if we optimise the image we'll get a good saving on 175kb.

@nickcolley thanks for helping out with the image optimisation

Looks good to me.


perlPackages.AnyEventI3: 0.17 -> 0.19

Description of changes

Fixes crash in perlPackages.Apppapersway
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)

[x] nixosTests.i3wm

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/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 319815 run on x86_64-linux 1

48 packages built:

autotiling
autotiling.dist
flashfocus
flashfocus.dist
i3
i3-balance-workspace
i3-balance-workspace.dist
i3-layout-manager
i3-resurrect
i3-resurrect.dist
i3-rounded
i3-rounded.debug
i3-swallow
i3-swallow.dist
i3-wk-switch
i3.debug
i3a
i3a.dist
i3altlayout
i3altlayout.dist
kitti3
kitti3.dist
nwg-displays
nwg-displays.dist
nwg-panel
nwg-panel.dist
nwg-wrapper
nwg-wrapper.dist
perl536Packages.AnyEventI3
perl536Packages.AnyEventI3.devdoc
perl536Packages.Apppapersway
perl536Packages.Apppapersway.devdoc
perl538Packages.AnyEventI3
perl538Packages.AnyEventI3.devdoc
perl538Packages.Apppapersway
perl538Packages.Apppapersway.devdoc
polybarFull
powerline (python311Packages.powerline)
powerline.dist (python311Packages.powerline.dist)
python311Packages.i3ipc
python311Packages.i3ipc.dist
python311Packages.py3status
python311Packages.py3status.dist
raiseorlaunch
raiseorlaunch.dist
sway-assign-cgroups
sway-contrib.inactive-windows-transparency
xkb-switch-i3

I don't see any breaking change in https://metacpan.org/release/MSTPLBG/AnyEvent-I3-0.19/source/Changes so let's backport


Support inherited collections

It would be great if you would support inherited collections:

A type is an array if it is not a dictionary and somwhere in the hierarchy IEnumerable is implemented.

A type is an dictionary if somewhere in the hierarchy IDictionary OR IDictionary<,> OR IReadOnlyDictionary<,> is implemented. This would make custom collections and immutable collections easier.

I had 2 use cases where it was necessary to override this method: https://github.com/RicoSuter/NJsonSchema/blob/master/src/NJsonSchema/Generation/DefaultReflectionService.cs#L328

Can you propose a change of the DefaultReflectionService?

I would like but I cannot find .NET Framework 4 developer pack. I think there should be an extension method like GetInterfaces and then we can just check that:
Isarray
type.GetInterfaces().Contains(typeof(IEnumerable))

IsDictionary
type.GetInterfaces().Any(x => x == typeof(IDictionary) || (x.IsGeneric && x.GetGenericType() == typeof(IReadOnlyDictionary<,>))

or so.


Health, supress bleed through of Showmenus when displaying barcharts

And Toucher: Debugging default = false

Thanks!


added graphs to Project card

Description
This PR adds graphs to the project card component
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

closing as there are breaking changes in v1 release


op-test.common.OpTestUtil:try_sendcontrol:WARNING:OpTestSystem recovered from temporary issue, but the command output is unavailable, raised Exception CommandFailed

When I'm trying to install latest kernel on my lpar using op-test, I can see below error messages.
sh -x ./arch/powerpc/boot/install.sh "5.11.0-rc6+" vmlinux System.map "/boot"

set -e
'[' -x /root/bin/installkernel ']'
'[' -x /sbin/installkernel ']'
exec /sbin/installkernel 5.11.0-rc6+ vmlinux System.map /boot
2021-02-02 21:02:46,258:op-test.common.OpTestUtil:try_sendcontrol:WARNING:OpTestSystem detected something, working on recovery
^C^C^M~.
2021-02-02 21:03:03,007:op-test.common.OpTestUtil:try_recover:WARNING:OpTestSystem detected something, working on recovery
command-line line 0: Unsupported option "afstokenpassing"^M
Activate the web console with: systemctl enable --now cockpit.socket

This system is not registered to Red Hat Insights. See https://cloud.redhat.com/
To register this system, run: insights-client --register
Last login: Tue Feb  2 11:01:28 2021 from <IP_ADDRESS>^M
[root@ci-upstream1 ~]# which bash && exec bash --norc --noprofile
PS1=[console-expect]#
which bash && exec bash --norc --noprofile
/usr/bin/bash
bash-4.4# PS1=[console-expect]#
[console-expect]#which stty && stty cols 300;which stty && stty rows 30
which stty && stty cols 300;which stty && stty rows 30
/usr/bin/stty
/usr/bin/stty
[console-expect]#export LANG=C
export LANG=C
[console-expect]#
[console-expect]#
date
which whoami && whoami
[console-expect]#date
Tue Feb  2 21:03:06 EST 2021
[console-expect]#which whoami && whoami
/usr/bin/whoami
root
[console-expect]#echo $?
echo $?
0
[console-expect]#^C^C
2021-02-02 21:03:10,480:op-test.common.OpTestUtil:try_recover:WARNING:OpTestSystem recovered from temporary issue, continuing
2021-02-02 21:03:10,480:op-test.common.OpTestUtil:try_sendcontrol:WARNING:OpTestSystem recovered from temporary issue, but the command output is unavailable, raised Exception CommandFailed but continuing
[console-expect]#ERROR (36117.043s)
======================================================================
ERROR [36117.043s]: runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel)
Traceback (most recent call last):
File "/var/lib/jenkins/workspace/op-test/testcases/InstallUpstreamKernel.py", line 117, in runTest
onlinecpus, timeout=self.host_cmd_timeout)
File "/var/lib/jenkins/workspace/op-test/common/OpTestSSH.py", line 225, in run_command
return self.util.run_command(self, command, timeout, retry)
File "/var/lib/jenkins/workspace/op-test/common/OpTestUtil.py", line 1616, in run_command
raise cf
File "/var/lib/jenkins/workspace/op-test/common/OpTestUtil.py", line 1611, in run_command
output = self.try_command(term_obj, command, timeout)
File "/var/lib/jenkins/workspace/op-test/common/OpTestUtil.py", line 1679, in try_command
output_list, echo_rc = self.try_sendcontrol(term_obj, command)
File "/var/lib/jenkins/workspace/op-test/common/OpTestUtil.py", line 1148, in try_sendcontrol
" but the command output is unavailable", -1)
common.Exceptions.CommandFailed: Command 'make -j 41 -s && make modules && make modules_install && make install' exited with '-1'.
Output
run_command TIMEOUT in try_sendcontrol, we recovered the prompt, but the command output is unavailable
2021-02-02 21:03:12,486:op-test::INFO:Exit with Result errors="1" and failures="0"
2021-02-02 21:03:12,486:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2021-02-02 21:03:12,487:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /var/lib/jenkins/workspace/op-test/test-reports/test-run-20210202110017/debug
2021-02-02 21:03:12,487:op-test.common.OpTestUtil:dump_versions:INFO:
OpTestSystem Firmware Versions Tested
(if flashed things like skiboot.lid, may not be accurate)
Firmware Versions Unavailable

@vijaykumarpuliyala  Are you using upstream code and code with localfix?

is is VM or NV?

@harihare It is Power9 ZZ lpar.

@vijaykumarpuliyala Are you using upstream code and code with localfix?

I'm running op-test job from my Jenkins.

As per the issue. it is the issue with the kernel config file or some missing packages that is why the Make is failed. Nothing to do with the framework. Hence closing the issue.
Please feel free to reopen the issue if you feel issue with the framework.


Most of the -Bookings* parameters are missing descriptions

Please fill in the descriptions of the -Bookings* related parameters so that we can know what they do.

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

ID: 23add0a6-bb9c-15d2-a6eb-351ae0564522
Version Independent ID: 8056b3ee-4fab-3a5c-935b-a9d0e9ad82a4
Content: Set-OrganizationConfig (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-OrganizationConfig.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

Hi @webash, thank you for your feedback.
I'm trying to get more information about these parameters. Please give me some days.

Hey @dariomws - any update? :)

My apologies @webash. I still don't have any update. I´ll keep you posted once we have it.

Seeking clarification from the product team. Responsible party identified, and I'm waiting for more information.

@chrisda do you have any updates? Thanks!

@chrisda Any update?

All of the Bookings parameters are now described.
Thanks for the feedback.
Closing


Subplayer Showing Loading Dependency no idea why

Hi Team ,
I am trying to use this awesome sublayer for my subtitle editing .I am facing issues with integration. it is showing error on uploading video. this error is coming as popup with "Loading Dependency" and doesn't close.

It may be due to the network, because it needs to load a 20M ffmpeg to process the video. This file comes from: https://unpkg.com/<EMAIL_ADDRESS>


[ANSIENG-3838] | use python3 in kafka_connectors.py (#19)

Description
This PR adds the capability to run connector module with python 3 instead of python 2
Fixes # (issue)
Type of change

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

How Has This Been Tested?
Semaphore Job Link
Checklist:

[ ] Any variable/code changes have been validated to be backwards compatible (doesn't break upgrade)
[x] I have added tests that prove my fix is effective or that my feature works
[ ] If required, I have ensured the changes can be discovered by cp-ansible discovery codebase
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

I think we should test this for all the scenarios which sets up connectors.
This would include scenarios like archive-plain-rhel-fips, broker-scale-up, connect-scale-up, kerberos-rhel, ksql-scale-up, multi-ksql-connect-rhel etc

I think we should test this for all the scenarios which sets up connectors. This would include scenarios like archive-plain-rhel-fips, broker-scale-up, connect-scale-up, kerberos-rhel, ksql-scale-up, multi-ksql-connect-rhel etc

The pipeline link has all tests triggered.

I think we should test this for all the scenarios which sets up connectors. This would include scenarios like archive-plain-rhel-fips, broker-scale-up, connect-scale-up, kerberos-rhel, ksql-scale-up, multi-ksql-connect-rhel etc

The pipeline link has all tests triggered.

The link was pointing to the retry failed scenarios section there I saw only 4 of the tests. On checking the complete run I found that all the tests were ran 😅.


docs: Refactor Auto-generated Class/Method Documentation

Consolidates all Classes/Methods into one "API Reference" page.
Fixes #236 🦕

No longer needed https://cloud.google.com/python/docs/reference/documentai-toolbox/latest/summary_overview


Drop additional fields in service update requests

Service update should ignore links and supplierName fields since they're present in the GET response. This is what PUT /services/... does right now.

Looks good, tests pass. I'll wait for travis to catch up and then :+1:


error when importing mpathic

I am running using Docker, with Dockerfile
FROM ubuntu:18.04
RUN apt-get upgrade
RUN apt-get update
RUN apt-get install -y gcc
RUN apt-get install -y libblas-dev liblapack-dev
RUN apt-get install -y gfortran
RUN apt-get install -y python-pip
RUN apt-get install -y git
RUN pip install ipython numpy
RUN pip install mpathic==0.5
also tried mpathic==0.6 both generate the same error
I get the following error:

import mpathic as mpa
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/mpathic/init.py", line 64, in
from mpathic.src.simulate_sort import SimulateSort
File "/usr/local/lib/python2.7/dist-packages/mpathic/src/simulate_sort.py", line 11, in
from mpathic.src import Models
File "/usr/local/lib/python2.7/dist-packages/mpathic/src/Models.py", line 20, in
from mpathic.src import fast
File "init.pxd", line 872, in init fast
ValueError: numpy.ufunc has the wrong size, try recompiling. Expected 192, got 216

Hi jurquiza,
from your error message, it may be that you have multiple copies of numpy installed or one of your packages (e.g. scipy) is complied against a newer version of numpy than the one you have on your machine, e.g. see https://github.com/scipy/scipy/issues/3448 or https://stackoverflow.com/questions/53904157/numpy-ufunc-has-the-wrong-size-try-recompiling-even-with-the-latest-pandas-and
If you could read into these issues and check your package versions, that would be great. I just did a fresh install of mpathic on google colab and it imported okay for me:

It may also be that because I have not updated the mpathic dependency package versions in the setup.py in quite a while, that may be causing this issue with docker. If you could first look into the links I posted (and the links inside them) and see if you can resolve the issue, that would be great. Alternatively, I could do another release in a few days with updated package dependency versions and that would likely solve the issue.
-Ammar

Progress
User needs to install BLAS a lapack through apt-get install
The user has to pin down numpy==1.14.2 if the user does not pin down to this version then there are problems with the dependencies installed (I didn't went very deep into this issue)
Then run the container in bash mode,
run
apt-get install python-tk
then commit the new docker image. This is because python tk requires input from the user for installation

Great! you can use numpy 1.14.2 for as a temporary solution. I will update the mpathic dependencies soon with the next release. Please report back if you encounter any other issues.
Best,
-Ammar


Communication routines testing

Fixes #205

utACK 24733c0fbdbf13b79294b9450f4cff71b067bdee -- light review: code looks good but i didn't try to think about edgecases it would be nice to have covered. But it's been waiting for too long.
OTOH it's pretty complete already and is a strong 12% unit test coverage increase on control.rs. Great work!

I should have been more careful, this broke master.


fixed the security hotspots from the sunar postsubmit

Signed-off-by: myan<EMAIL_ADDRESS>Risk message: Scratch images run as root by default. Make sure it is safe here.

/cc @morvencao


Import Fixes

Import unique names.

Completed the UI fixes, changes made according to the new data model.
Please always use the sample file format while uploading the files.


Error when enabling AMQTT and Home assistant support

Hi
When enabling the following items
#define HTTP_OTA             .
#define ENABLE_AMQTT
//#define ENABLE_MQTT
#define ENABLE_HOMEASSISTANT
#define ENABLE_BUTTON
#define MQTT_HOME_ASSISTANT_SUPPORT
i get the following error.
In file included from C:\Users\adrian\Desktop\mclighting\McLighting-master\Arduino\McLighting\McLighting.ino:218:0:
sketch\request_handlers.h: In function 'void onMqttConnect(bool)':
request_handlers.h:1036: error: 'class ArduinoJson::JsonObject' has no member named 'measureJson'
char buffer[json.measureJson() + 1];
^
request_handlers.h:1037: error: 'buffer' was not declared in this scope
serializeJson(json, buffer, sizeof(buffer));
exit status 1
'class ArduinoJson::JsonObject' has no member named 'measureJson'
i have tried different versions of arduiniojson but the error persists
Any ideas

Please install ArduinoJSON 6.0.1-beta

Already have that installed, tried a few different versions, the erro ronly appears when enabling
#define MQTT_HOME_ASSISTANT_SUPPORT

Thanks for pointing that out, I'll fix this, measureJson was changed in ArduinoJSON 6.x.x

@aidbish I have pushed the fix, but all that is change json.measureJson() to measureJson(json)

Thanks, now the Wiki link should reflect this requirement. Yesterday's McLighting merge brought the requirement up to the latest ArduinoJSON release.


Error when init in Xamarin.iOS AppDelegate class

When I init the plugin in a Xamarin.Forms iOS project I get the following error:
Error MT0034: Cannot include both 'monotouch.dll' and 'Xamarin.iOS.dll' in the same Xamarin.iOS project - 'monotouch.dll' is referenced explicitly, while 'Xamarin.iOS.dll' is referenced by 'Toasts.Forms.Plugin.iOS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. (MT0034) (MyProjectName)
Initilization like:
            public override bool FinishedLaunching (UIApplication app, NSDictionary options)
	{
		Forms.Init ();

		ToastNotificatorImplementation.Init ();

		window = new UIWindow (UIScreen.MainScreen.Bounds);

		...
		return true;
	}

How could I solve this?
I am using Xamarin.Forms 1.3.0 (stable)
PS. thanks for sharing this awesome plugin

I have the same issue, I want to use this plugin so bad but I have nullpointer on Android and this on iOS. Can confirm bug.

Let me take a look, I tested it on a sample with Unified API.

I'm getting an error on initialization on iOS:
Xamarin.Forms.Init();//platform specific init
ToastNotificatorImplementation.Init(); //you can pass additional parameters here
I already added using Toasts.Forms.Plugins;
There is no namespace Toasts.Forms.Plugins.iOS
Am I missing something to add into specific platform? if yes what is? or is this a bug?
Thanks in advance, great work!

@vhugogarcia You must add the nuget DLL of this plugin into both your IOS and Android projects. If you are only making an IOS app, you must add the DLL into your IOS project. Nuget should handle that for you.

@Zeraceee Thanks for your faster responder.
Actually, I added them on iOS and Android projects as well. See screenshots:
DLLs: http://i59.tinypic.com/15hyf6o.png
Autocomplete: http://i57.tinypic.com/ricj0n.png
Note: I'm using Xamarin.Forms 1.3.1 Unified API (Final release) - iOS and Android projects.

@vhugogarcia  I just updated to Xamarin.Forms 1.3.1 and migrated my project to an unified project and now I also experience the same issue.  It does not recognise the required namespace anymore.

@vhugogarcia
On latest build, getting same issue (1.3.1). I hope the author can update, if not, I will fork and rebuild for you guys.

@Zeraceee, @stefan89, @vhugogarcia sorry guys, I'll try to manage with these issues once I be home (in a day or two).

Thanks @Zeraceee and @EgorBo

Awesome plugin. You have an idea on when you get this working for 1.3.1?

@EgorBo any updates?

@EgorBo did you already solved the issue?

@EgorBo I'm also getting the "Cannot include both 'monotouch.dll' and 'Xamarin.iOS.dll' in the same Xamarin.iOS project" issue = do you have any updates?

Turns out this is using the new unified API, and it's using new features of the API, so it can not easily be pulled back.
http://developer.xamarin.com/guides/cross-platform/macios/updating_ios_apps/

Even in plugin version 1.0.8 it does not work in iOS.
Still can't find ToastNotificatorImplementation.Init();

Fixed in <IP_ADDRESS>


🐛 Enable 0.x with negative margins @ v4

I set it as below, but no negative margin was added.
$spacers: (0\.5: ($spacer * .125));
After investigating, it seems that 0 \ .5 is also evaluated as 0.
So I changed it to string comparison.
HTML example: <img class="mt-n0.5">

Is this needed in main for v5 as well?

Maybe not.
I think v5 doesn't use this mixin.


Wait for db to be ready

Start once the db port is open.

I'm a bit in doubt about this fix because I feel it makes the container a bit more fragile.
For instance; What happens when the DB doesn't respond? Then this container will be stuck in a loop instead of failing to start. If I would monitor my docker containers for failures than this won't be noticed.
You can of course add a limit on number of retries, but that makes it even more fragile.
Can you explain when you exactly need this?

Yeah, I guess it's not the proper place and the base image should not enforce to wait.
I'm closing this PR as it's probably not a feature all users would like


Discussion Thread

Discuss the Responsive Framework here ⬇
Feel free to leave your thought on the features, API, and functionality. Or use this to start a discussion and share what's on your mind.

Hi,Your library is very well designed,So can you tell/suggest us that is it working fine with the device preview library, can be used to test the different size screen.

I tested with FlutterDevicePreview a few months ago. There was a major release and I haven't tested with the latest yet.
If you give it a try, let me know how it works!

Very good combo 👍  :
          MaterialApp(
            locale: DevicePreview.of(context).locale,
            debugShowCheckedModeBanner: false,
            title: 'Title',
            theme: themeService.getTheme(),
            darkTheme: themeService.getThemeDark(),
            themeMode:
                MediaQuery.of(context).platformBrightness == Brightness.dark
                    ? ThemeMode.dark
                    : ThemeMode.light,
            builder: (BuildContext context, Widget widget) =>
                DevicePreview.appBuilder(
              context,
              MediaQuery(
                data: MediaQuery.of(context).copyWith(textScaleFactor: 1.0),
                child: ResponsiveWrapper.builder(MainView()),
                  maxWidth: 2460,
                  minWidth: 480,
                  defaultScale: true,
                  breakpoints: <ResponsiveBreakpoint>[
                    const ResponsiveBreakpoint.resize(480, name: MOBILE),
                    const ResponsiveBreakpoint.autoScale(600, name: TABLET),
                    const ResponsiveBreakpoint.autoScale(1000,
                        name: TABLET, scaleFactor: 1.2),
                    const ResponsiveBreakpoint.resize(1200, name: DESKTOP),
                    const ResponsiveBreakpoint.autoScale(2460, name: '4K'),
                  ],
                  background: Container(color: const Color(0xFFF5F5F5)),
                ),
              ),
            ),
          ),

You should give it a try.

Glad to hear it works!
Thanks for sharing your results.

First of all thank Thank you very much this library. MInd blowing and beneficial framework for all of us. Hats off to you!!! You library help to my production app and reduce lots of boilerplates code

Hi, does this plugin help with scaling between devices of similar screen sizes eg two mobile phones with different sizes/aspect ratios, by default on flutter, a view on the target device can display just fine but on a smaller device, you could get RenderFlex errors.

Also, amazing presentation of this package, one of the best I've seen. I gave it a like before I even read through the whole readme.

Until I can resolve the TextForm keyboard focus issue and the SafeArea issue, I cannot recommend using this library on Mobile. Yes, the scaling will adjust for smaller devices but there are framework level interactions that are not accounted for such as Overlays, TextFields, and SafeAreas.
The ResponsiveFramework works almost perfectly for Flutter Websites.
Thanks for the kind words!

@bounty1342, the returning MediaQuery that you use, what is it purpose? Does it change the MediaQuery parameters?

@gcostaapps it's to fix the MediaQuery for the whole app. In this case textScaleFactor is overridden.

@bounty1342 that's great! Maybe that could be a fix for #17, because these libs generally take the MediaQuery parameters to calculate positions.

Closing and migrating to https://github.com/Codelessly/ResponsiveFramework/discussions/35

Hi I like the concept of scaling but I can't understand the scaling mechanism so lets try this one
ResponsiveBreakpoint.autoScale(
              260,
              name: MOBILE,
              scaleFactor: 0.5,
            ), //260-450=scale from 260 or 450?
            ResponsiveBreakpoint.resize(450, name: MOBILE), //450-800=resize
            ResponsiveBreakpoint.autoScale(
              800,
              name: TABLET,
            ),

the scaleFactor is calculated from the 260 version or 450 version?
Because it looks like the scale fits always the bottom version but the first breakpoint is 260 so it probably means that 0-260 is resize (by default) BUT the website with 259px width looks different then 260 so I am little bit confused because can't definitely say where the concrete layout comes in.

Good question! You've got the basic understanding down but there's a bit of special behavior with how the 0 - X breakpoint works.
It doesn't makes sense to have a breakpoint scale from 0 so the first breakpoint actually inherits down.
To get the 0-260 to autoscale, the parameter you're missing is defaultScale = true.
For a bird's eye view of the behavior at each breakpoint segment, set debugLog = true to print out a visualization of the behaviors!


Run bcdedit /set hypervisorschedulertyupe root

Description
According to the email from: Alexander Grest<EMAIL_ADDRESS>[Hyper-V hypervisor scheduler types | Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types)

You could try to enable the root scheduler (bcdedit /set hypervisorschedulertyupe root) and see if it improves emulator launch, but please note that you lose isolation guarantees between SMT threads.

Related issue:
https://github.com/actions/runner-images-internal/issues/4786
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run windows2019,windows2022


CB-18059 Environment delete with cascading == false && forced == true…

… leaves behind orphan DL/DH clusters and experiences

If cascading == false:

Checks for attached resources are always executed, irrespective of the forced flag. (The same applies to the checks for child environments, there is no change in that respect.)
updateEnvironmentDeletionType() and environmentJobService.unschedule() are only invoked if there are no child environments nor any resources attached to the environment.

Enhance error messages thrown for the aforementioned validations.
Some code cleanup.
Testing:

Manual testing in local CB.
Added new UT and updated existing ones.

Swagger errors:
CB_VERSION=2.60.0-b77 CB_TARGET_BRANCH=CB-2.60.0 ./scripts/swagger-check.sh
Fri Aug  5 21:03:10 UTC 2022
Swagger check

Determine previous version number based on current version (which is 2.60.0 from input 2.60.0-b77),
where major version number is: 2, minor: 60, patch: 0
...
Target branch for swagger check: CB-2.60.0
Downloading cloudbreak 2.60.0-b77 swagger definition, if possible https://cloudbreak-swagger.s3.eu-central-1.amazonaws.com/swagger-2.60.0-b77.json
change is compatible
2.59.0-b74
Downloading cloudbreak 2.59.0-b74 swagger definition, if possible https://cloudbreak-swagger.s3.eu-central-1.amazonaws.com/swagger-2.59.0-b74.json

================ COMPATIBILITY BREAKS in cloudbreak ================
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/Images" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/images)
  warnings.warn(
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/ImageStackDetails" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/images/properties/base-images/items/properties/stack-details)
  warnings.warn(
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/StackRepoDetails" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/images/properties/base-images/items/properties/stack-details/properties/repo)
  warnings.warn(
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/Versions" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/versions)
  warnings.warn(
ERROR rules:
	[MIS-E001] Delete Endpoint: Endpoint(http_verb=<HTTPVerb.GET: 'get'>, path='/v4/{workspaceId}/image_catalogs/image/type/{type}/provider/{provider}/runtime/{runtime}', operation=Operation(getImageFromDefaultWithRuntime)) (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E001.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/stacks/internal/post/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v1/distrox/crn/{crn}/get/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/internal/get/responses/200/schema/properties/responses/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/internal/post/parameters/2/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/internal/post/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/stacks/{name}/cluster/put/parameters/2/schema/properties/hostgroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//autoscale/stack/crn/{crn}/get/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v1/distrox/post/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//autoscale/stack/crn/{crn}/{userId}/cluster/put/parameters/2/schema/properties/hostgroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/stacks/crn/{crn}/get/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/stacks/post/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/get/responses/200/schema/properties/responses/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/delete/responses/200/schema/properties/responses/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/post/parameters/1/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/post/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/name/{name}/get/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/name/{name}/delete/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v1/distrox/name/{name}/get/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/{name}/request/get/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/crn/{crn}/get/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/crn/{crn}/delete/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v1/distrox/internal/post/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/recipes/name/{name}/internal/get/responses/200/schema/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//v4/{workspaceId}/stacks/{name}/get/responses/200/schema/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
===============================================================================

Downloading freeipa 2.60.0-b77 swagger definition, if possible https://freeipa-swagger.s3.us-east-2.amazonaws.com/swagger-2.60.0-b77.json
change is compatible
2.59.0-b74
Downloading freeipa 2.59.0-b74 swagger definition, if possible https://freeipa-swagger.s3.us-east-2.amazonaws.com/swagger-2.59.0-b74.json
change is compatible
Downloading environment 2.60.0-b77 swagger definition, if possible https://environment-swagger.s3.us-east-2.amazonaws.com/swagger-2.60.0-b77.json
change is compatible
2.59.0-b74
Downloading environment 2.59.0-b74 swagger definition, if possible https://environment-swagger.s3.us-east-2.amazonaws.com/swagger-2.59.0-b74.json
change is compatible
Downloading datalake 2.60.0-b77 swagger definition, if possible https://datalake-swagger.s3.us-east-2.amazonaws.com/swagger-2.60.0-b77.json
change is compatible
2.59.0-b74
Downloading datalake 2.59.0-b74 swagger definition, if possible https://datalake-swagger.s3.us-east-2.amazonaws.com/swagger-2.59.0-b74.json

================ COMPATIBILITY BREAKS in datalake ================
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/Images" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/images)
  warnings.warn(
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/ImageStackDetails" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/images/properties/base-images/items/properties/stack-details)
  warnings.warn(
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/StackRepoDetails" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/images/properties/base-images/items/properties/stack-details/properties/repo)
  warnings.warn(
/usr/lib/python3.8/site-packages/swagger_spec_validator/validator20.py:49: SwaggerValidationWarning: Found "$ref: #/definitions/Versions" with siblings that will be overwritten. See https://stackoverflow.com/a/48114924 for more information. (path #/definitions/CloudbreakImageCatalogV3/properties/versions)
  warnings.warn(
ERROR rules:
	[MIS-E002] Changed type: #/paths//sdx/{name}/detail/get/responses/200/schema/properties/stackV4Response/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
	[MIS-E002] Changed type: #/paths//sdx/crn/{clusterCrn}/detail/get/responses/200/schema/properties/stackV4Response/properties/instanceGroups/items/properties/recipes/items/properties (documentation: https://swagger-spec-compatibility.readthedocs.io/en/latest/rules/MIS-E002.html)
===============================================================================

Downloading redbeams 2.60.0-b77 swagger definition, if possible https://redbeams-swagger.s3.us-east-2.amazonaws.com/swagger-2.60.0-b77.json
change is compatible
2.59.0-b74
Downloading redbeams 2.59.0-b74 swagger definition, if possible https://redbeams-swagger.s3.us-east-2.amazonaws.com/swagger-2.59.0-b74.json
change is compatible

Incompatible changes:
- cloudbreak:2.59.0-b74
- datalake:2.59.0-b74
make: *** [swagger-compare] Error 1
Build step 'Conditional steps (multiple)' marked build as failure

These have nothing to do with my changes.

don't care with swagger diff.. it diffs with 2.59 by some reason, the 2.60 diff looks fine


New release for pyfolio

It looks like enough has changed on pyfolio to merit v0.8.0 (with risk and performance attribution, I think we might even want to call it v1.0.0!)
We are also seeing an increasing number of users running into bugs that have already been patched: upping the version would make it easier to diagnose errors (both ours, and open source users).
To-do:

[ ] Performance attribution tear sheet #417 (still WIP, will definitely want to wait for this)
[ ] Resolve any dependency issues with zipline/alphalens/empyrical
[ ] Do we want to outsource Fama-French functionality from pyfolio to empyrical? #56 on empyrical (Answer: yes. PR waiting: #416)
[ ] Do we want to include returns decomposition from alphalens into pyfolio? #183 on alphalens

@twiecki @gusgordon @richafrank @Jstauth thoughts? If this sounds good I'll organize a milestone :)
New features

Risk tear sheet: added a new tear sheet to analyze risk exposures to common factors, sector, market cap and illiquidity (#391)
Simple tear sheet: added a new tear sheet that presents only the most important plots in the full tear sheet, for a quick general overview of a portfolio's performance (#389)
Volatility plot: added a rolling annual volatility plot in the returns tear sheet (#390)

Bugfixes

Fixed bug regarding Yahoo API and pandas data reader (#395)
Removed information_ratio to remain compatible with empyrical
Fama-French rolling multivariate regression bug fix (#406)

Maintenance

Updated and improved jupyter notebook documentation (#411)

Yes, should absolutely cut a new release! Want to do a PR that updates the version number?

I'll draft a release and organize a milestone so we know what PRs to wait for and what not to. A milestone will be better than an issue :)

I just remembered @twiecki I had drafted a new release announcement on github, but since my access has been revoked I assume its lost. You can just use my comment above to draft a new one.

Nothing should get lost. It's either on a branch you pushed or on a local branch of yours. Where did you keep it?

As a draft release: click "10 releases" on the info bar on the pyfolio github home page.

@twiecki @gusgordon once @vikram-narayan's perf attributions are done we can cut a new version of pyfolio

We can probably already do that now given the changes and refactorings we have.

If you think that would be a good idea! 🎉

@eigenfoo Want to do a PR with the release announcements and version bump to 0.8.0?

Will do!

Hi, isn't the changes of requirements breaking the requirements of zipline 1.1.1
zipline 1.1.1 : pandas==0.18.1
pyfolio 0.8.0: pandas>=0.19.0
zipline 1.1.1: empyrical==0.2.2
pyfolio 0.8.0: empyrical>=0.3.2
Source:
Pyfolio: https://github.com/quantopian/pyfolio/blob/v0.8.0/setup.py
Zipline: https://github.com/quantopian/zipline/blob/1.1.1/etc/requirements.txt
you may say: you don't need ZL with pyfolio.
Yes but when I'm trying to open a zipline result pickle file, if I don't have ZL Pyfolio is not able to unserialize the ZL Objects.
Am I doing something wrong?
Any suggestion?

@bonesmccoy Hm, that's indeed a pickle (no pun intended). The empyrical version mismatch should be fixed easily, the pandas one might be more tricky. CC @richafrank

We can probalby make pyfolio pandas 0.18.1 compat without too much effort (if it isn't already).

Yup, we'll be fixing the pandas issue soon, unless you get to it first.
zipline doesn't read the reqs.txt literally and actually supports empyrical>=2.2, so I don't think that's an issue here, unless you specifically want to use empyrical<0.3.2.

Closed by #552


Semantic mesh optimization - split by objectID and cull

Motivation and Context
Previously, semantic meshes were loaded in as a single mesh, making them impossible to cull. This PR leverages the spatial locality of ObjectIDs to split the single mesh into multiple different meshes by object ID, calculate AAbbs, and enables culling on this semantic mesh. See below for a visualization of how this works:

Full benchmarks are currently being ran.
Some example scene A/B tests benchmarking culling on semantic only, and overall rgbd + semantic:
Scene 1:

 ================ Performance (FPS) NPROC=1 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       286.1 /803.2  ( 180.8%) 212.9 /440.6  ( 106.9%)
256 x 256       279.3 /763.5  ( 173.4%) 210.8 /399.2  (  89.4%)
512 x 512       257.0 /613.7  ( 138.8%) 178.9 /291.2  (  62.8%)
 ==============================================================================
 ================ Performance (FPS) NPROC=3 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       374.0 /1479.2 ( 295.5%) 292.2 /786.5  ( 169.1%)
256 x 256       369.6 /1439.2 ( 289.4%) 285.9 /739.8  ( 158.8%)
512 x 512       344.6 /1355.1 ( 293.2%) 270.9 /649.2  ( 139.7%)
 ==============================================================================
 ================ Performance (FPS) NPROC=5 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       379.3 /1575.9 ( 315.5%) 310.5 /909.9  ( 193.0%)
256 x 256       376.5 /1534.8 ( 307.6%) 305.4 /860.3  ( 181.7%)
512 x 512       376.2 /1535.6 ( 308.2%) 297.5 /802.2  ( 169.7%)
 ==============================================================================

Scene 2:

 ================ Performance (FPS) NPROC=1 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       1664.5/2583.4 (  55.2%) 609.7 /769.7  (  26.2%)
256 x 256       1496.5/2296.9 (  53.5%) 564.4 /627.5  (  11.2%)
512 x 512       1022.6/1395.7 (  36.5%) 375.1 /409.7  (   9.2%)
 ==============================================================================
 ================ Performance (FPS) NPROC=3 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       3183.8/6393.6 ( 100.8%) 1154.9/1585.3 (  37.3%)
256 x 256       2998.3/5621.4 (  87.5%) 1080.6/1441.8 (  33.4%)
512 x 512       2895.1/3816.0 (  31.8%) 917.0 /1143.8 (  24.7%)
 ==============================================================================
 ================ Performance (FPS) NPROC=5 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       3108.0/7136.9 ( 129.6%) 1330.7/1868.2 (  40.4%)
256 x 256       2961.8/6342.3 ( 114.1%) 1247.3/1754.1 (  40.6%)
512 x 512       3153.1/5989.5 (  90.0%) 1151.9/1564.9 (  35.9%)
 ==============================================================================

Scene 3:

 ================ Performance (FPS) NPROC=1 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       463.2 /1231.5 ( 165.9%) 309.2 /528.5  (  70.9%)
256 x 256       441.8 /1094.6 ( 147.8%) 290.1 /493.6  (  70.1%)
512 x 512       392.5 /863.5  ( 120.0%) 239.3 /350.6  (  46.5%)
 ==============================================================================
 ================ Performance (FPS) NPROC=3 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       626.2 /2256.7 ( 260.4%) 458.3 /1101.9 ( 140.4%)
256 x 256       619.1 /2135.9 ( 245.0%) 444.1 /1020.1 ( 129.7%)
512 x 512       613.0 /1870.8 ( 205.2%) 407.3 /836.6  ( 105.4%)
 ==============================================================================
 ================ Performance (FPS) NPROC=5 ===================================
Resolution      semantic_only                   rgbd_semantic
128 x 128       625.6 /2540.6 ( 306.1%) 492.4 /1310.6 ( 166.2%)
256 x 256       618.6 /2428.8 ( 292.6%) 478.1 /1244.7 ( 160.3%)
512 x 512       621.3 /2314.1 ( 272.5%) 456.4 /1145.1 ( 150.9%)
 ==============================================================================

How Has This Been Tested

Visual tests using viewer to make sure bounding boxes are calculated correctly
Benchmarks on most scenes
Existing tests pass

Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Wow. Look at this:
256 x 256       369.6 /1439.2 ( 289.4%) 285.9 /739.8  ( 158.8%)
The speedup is almost 4x for this semantic scene!
@dhruvbatra

This is awesome! Great work @matthewjmay!
I think I know which dataset these benchmarks are on. Have you thought about also testing on MP3D and Gibson?

I think I know which dataset these benchmarks are on. Have you thought about also testing on MP3D and Gibson?
I believe the results are from MP3D dataset.
As I advised, Matthew is now running the AB tests on all MP3D models since last Fri.

@dhruvbatra @bigbike Confirming these benchmarks are on the MP3D dataset.

That's great, thank you!

This is great! Two high-level ideas before I deep-dive into the code:

Instead of populating one separate std::vector for each attribute / each object ID, what about taking the previous state (with per-vertex object ID) and sorting the index buffer in a way that each object ID is in a consecutive set of indices? That way the whole mesh could still be a single uploaded index and vertex buffer like before, but you could be drawing just parts of it -- in other words, there still being one GL::Mesh, but with multiple GL::MeshViews on it, each having a different index range. And then all views that survive culling can be put in an array and drawn in a single call using GL::MeshView::draw() (you'll need to get mosra/magnum@4f0170ace4c3ccbaf2a94da5559f58d0359c2a79 that I pushed just now for this, the version currently in habitat has doesn't have this particular overload yet)
(Mutually incompatible with the above but) if each mesh has a single object ID, we wouldn't need the per-vertex object ID anymore, and thus the whole GenericInstancedShader and everything related to it could be dropped, right? Unless I missed something, of course.

@mosra, That's great! I was actually thinking of something like your first point while implementing this (a simpler version where individual GL::Meshs share a GL::Buffer backing), but the MeshView should work even better. I'll incorporate it in a later PR once that branch is merged in.
I thought about the single uniform object ID per drawable as well, but decided that it wasn't a good idea to constrain us to this design yet. For one, I can't toggle this feature on/off easily for A/B testing (this won't matter once this design is approved/merged), and also I didn't want to constrain us into this 1-1 mapping between ID and drawable, since @bigbike is working on some other scene partitioning models.

Any blocks on this? Looks like it might be ready to go. @bigbike ?


Add edit on GitHub button

done https://github.com/PhilipMay/May.la/commit/62eaff9f9c48a912a11cf025cc08986b697f962c


Images render size is difficult to read

mkdocs renders images on a scale which makes it difficult to read embedded text.

Stack Overflow Link


Removing an undeployed stack results in errors from agent

Issue
Removing an undeployed stack results in errors from agent
Context
This happens because docker compose is invoked to act in a working directory that doesn’t exist (because the stack never got deployed in the first place).
Expected behaviour
Removing an undeployed stack results in successful from agent

PR -> https://github.com/portainer/agent/pull/623


Possibility of automating retrieval of cookie: csrftoken in graphql

Would it be possible to use leetcode username and password in a kept-secret config file and automate the process of retrieving cookie: csrftoken from  ?

I don't think that's possible because logging in with a username and password requires solving a Cloudflare captcha.
I'm considering implementing automatic cookie detection from the system's default browser, but I can't guarantee that it will happen.

hey im not able to signin through cookie in mac.It's telling the csrf token format is bad but this is the token in graphl header
csrftoken=sRfS3NQ5frYJr2NvhRylb10GAQLfBV8Ey6j0Hx4CKu3sOARohePvaNxX5KAY16zC; expires=Sun, 16 Nov 2025 08:23:42 GMT; Max-Age=31449600; Path=/; SameSite=Lax; Secure can someone tell me how to get around this

Are you sure you are logged in on leetcode.com?

I was having issues with this too. It seems like the cookie format leetcode is using now is different than what's shown in the demo video. You have to copy the whole cookie value from the request header including INGRESSCOOKIE, LEETCODE_SESSION etc...


Thrift Identifier should read TTwitter headers if available

In the case where the TTwitter protocol is being used, the Thrift identifier could read a destination from a request header.

"This is really annoying to do because of the finagle code is structured."


feat: add support for semantic release using conventional commits

Using code from jx v2:

https://github.com/jenkins-x/jx/blob/master/pkg/cmd/step/step_next_version.go
https://github.com/jenkins-x/jx/blob/master/pkg/semrel/semrel.go

this change adds a new flag -semantic-release which use conventional commits to parse the commits since the last tag in order to calculate the next tag
fixes #54

Hi @vbehar. Thanks for your PR.
I'm waiting for a jenkins-x-plugins or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Hi @vbehar. Thanks for your PR.
I'm waiting for a jenkins-x-plugins or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @jstrachan

/assign @jstrachan

/ok-to-test
/lgtm

/ok-to-test
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Help using map with react-redux boilerplate

Hi everyone,
Im trying to use this package with react-redux boilerplate https://github.com/erikras/react-redux-universal-hot-example, however I get an error like this:
Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. Please check the code for the undefined component.
On that repository I read an issue suggesting that, the map rendering should be made only on client side, so I added a state variable to modify on componentDidMount but the error persist. I made a gist with the example: https://github.com/OkuraSt/example-maps
The map component name is AsyncMap and it is added on Home.js. I hope someone could give a hint.
Thanks for your time

Link to https://github.com/OkuraSt/example-maps is dead.

Sorry for the late response,
I was able to make the map appear by setting the height and witdh to a number of pixels. My problem now is to resize to 100% height after the map has loaded, I was seeing this post, https://github.com/tomchentw/react-google-maps/issues/161 where you indicate new functionality with the triggerEvent but the error I get on my code is that "react-google-maps/libs/utils" is not found.
Could you help me with some directions on how to do this?
Thanks in advance for your time.

Please update your version of react-google-maps. https://github.com/tomchentw/react-google-maps/blob/v4.10.3/lib/utils/index.js


APP will be reject because it blocks status bar.

I've been reject twice because of following reason:
After further review, we notice that your app does not comply with the Apple iOS Human Interface Guidelines.

Specifically, we noticed that your app provides an overlay that partially or totally blocks the status bar.

So, using it carefully.

How often are you obscuring the status bar? Could you show screenshots of your app? We can talk privately if you wish.
Apps have been overlaying the statusbar for some time now, for example Mailbox. Bad :apple:

Only 0.5 sec, this is my UI looks like:

are there any toasts for failure to login? Sadly the app reviews can be a bit random, you can change your alerts or try submission again.

Poke @cruffenach

Same problem here, just got rejected by :apple: !

Sorry to hear that @summerblue, all I can suggest is to reduce the the time toasts are on screen, and reduce how often you trigger them - consider other ways to show certain messages.
Sadly reviews are just not consistent.

Yep, My solution is find a way to remove the toasts while App is in review.
Bad :apple:
@Ashton-W You are awesome! :+1:


ProgressLocation.Notification progress incrementing is incorrect

Env
Version: 1.42.0-insider
Commit: cba31b819ea99836daf51cee56299348e9c6d20b
Date: 2020-01-08T05:35:29.477Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 18.7.0

Steps to Reproduce:

check https://github.com/microsoft/vscode-extension-samples/tree/master/progress-sample

the progress is completed on 50%

check withProgress docs

value will be summed up and reflected as overall progress until 100% is reached (a value of e.g. 10 accounts for 10% of work done).

a correct example of 10% * 10 steps iteration
return vscode.window.withProgress({
        location: vscode.ProgressLocation.Notification,
        title: msg,
        cancellable: true
    }, async (progress, token) => {
        for (let i = 1; i <= 10; i++) {
            await new Promise((resolve) => {
                setTimeout(() => {
                    progress.report({ increment: (10 * i) / 5 })
                    resolve()
                }, 1000)
            })
        }

        return new Promise((resolve) => {
            resolve()
        })
    })

without the / 5

progress will complete in 5 steps
notification will remain visible for 10 seconds

@ctf0 I do not follow, this works fine for me:
export function activate(context: ExtensionContext) {
	context.subscriptions.push(commands.registerCommand('extension.startTask', () => {
		return window.withProgress({
			location: ProgressLocation.Notification,
			title: 'Hello World',
			cancellable: true
		}, async (progress, token) => {
			for (let i = 1; i <= 10; i++) {
				await new Promise((resolve) => {
					setTimeout(() => {
						progress.report({ increment: 10 });
						resolve();
					}, 1000);
				});
			}

			return new Promise((resolve) => {
				resolve();
			});
		});
	}));
}

Each iteration, 10% of work is done. What is different?

:scream:  wow, that worked, i dont know why using 10 * i gave the same result as the sample gif :sob:
i apologize for the inconvenience but it took me about 2hrs or so to get it work correctly, thats why i  opened the ticket.
thanx again for ur help.


Tópicos Setembro/2023

https://utxo.live/oracle/

https://lexe.app/

https://bolt.fun/tournaments/legends-of-lightning-vol2/overview?ref=nobsbitcoin.com

https://twitter.com/River/status/1704138775994265982

https://www.nobsbitcoin.com/zeus-v0-8-0-alpha-opened-to-waitlist-subscribers/

https://zerosync.org/demo/

https://ambosstech.medium.com/businesses-meet-hydro-your-new-best-friend-for-lightning-network-payments-d9fb90016e67

https://github.com/thesimplekid/cashu-lnurl

https://www.nobsbitcoin.com/paxos-identified-as-fat-finger-entity-in-20-btc-fee-mistake/

https://bitcoinmagazine.com/technical/op-checkseparatesig-and-actuaries-fixing-multiparty-channel-factories

https://github.com/tee8z/doppler

https://github.com/bitcoin/bips/pull/1489

https://gist.github.com/instagibbs/1d02d0251640c250ceea1c66665ec163

https://twitter.com/jamesob/status/1704869752470921302

https://obscuravpn.io/


Match Char with char constant in F#

Fixes https://github.com/FStarLang/FStar/issues/2647

Thanks!


Use (more) authoritative MIME types so that embedded .woff and .ttf don't raise warnings in WebKit Web Inspector

In recent versions of WebKit, .woff fonts transferred with type font/woff (and .ttf fonts transferred with type font/truetype) raise warnings like the following in Web Inspector:
https://img.skitch.com/20120222-rcfx7t37cew21119cjq6mqjkqs.png
This "bug" is documented in Chromium's issue tracker:
http://code.google.com/p/chromium/issues/detail?id=70283
But per the WOFF file format, application/x-font-woff is the appropriate type here. (Same for application/x-font-ttf; in general, font/* is not a valid MIME type, but I haven't touched font/opentype because WebKit treats that as a valid MIME type for some reason.

Ugh. I loathe mime-type wankery, especially after the powers that be have said to stop using x- prefixes.
However, after looking at that WebKit ticket, things look very unresolved. Are you sure this won't just consign us to warnings in other browsers down the road?

More fun here.
Either way, whichever mime type you choose now, it's going to be incorrect because there's no "correct" way. I would give a +1 for this pull though, especially for the WOFF format, font/woff is an imaginary type that has no chance of becoming the standard.
Do we need a way to specify the mime type mapping in Jammit? Maybe use http://rubygems.org/gems/mime-types?

I'm definitely not sure that this will be impervious to future browser warnings; I'm just making a best guess about the direction browser MIME type standards are heading, but it's still pretty unresolved, as you say.
Maybe allowing custom user-defined MIME type mappings is the way to go? That seems a bit too configuration-heavy though.


How to add multiple release assets

As the title, there is no clear documentation on how to add several files in the release. Attempt to do something like **\*.(exe|dll) simply fails with Illegal character in path.

The task uses a PowerShell module that ships with the VSTS Task SDK. AFAIK there's no official documentation for that module, but here is a good blog post that explains how it works:
https://blogs.infosupport.com/tfs2015-build-tasks-the-wildcard-format-explained/
Let me know if that helps


RFC: Refactor getAllPreflightChecks/getPreflightChecks

The implementation of these methods is currently a bit complicated, with the list of tests being manually generated by appending the 'right' tests depending on various parameters.
This PR tries to make this a bit easier, by adding labels to each Check instance in order to explicitly define when it should be used.
I tagged this as RFC to get feedback on this approach, maybe thet current way will be considered simpler, maybe this needs to be approached differently, ...
Proposed changes
There should be no user-visible changes, exactly the same preflight as before should be run by crc setup/crc cleanup/crc start.

/retest

/lgtm


Wrapping ActiveRecord test causes it to fail (no records found)

I created a script to demonstrate this behavior:
#!/usr/bin/env ruby

begin
  require "bundler/inline"
rescue LoadError => e
  $stderr.puts "Bundler version 1.10 or later is required.  Please update your bundler"
  raise e
end

gemfile(true) do
  source "https://rubygems.org"
  gem "activerecord", "<IP_ADDRESS>"
  gem "mysql2", "0.4.5"
  gem "database_cleaner", "1.5.3"
  gem "rspec", "3.5.0"
end

require "active_record"
require "rspec"
require "rspec/autorun"
require "database_cleaner"

ActiveRecord::Base.establish_connection(
  adapter: "mysql2",
  username: "root",
  password: "password",
  host: "localhost",
  database: "ft_test"
)
ActiveRecord::Base.connection.recreate_database "ft_test"

ActiveRecord::Schema.define do
  create_table :widgets, force: true do |t|
    t.string "description", limit: 255
  end

  add_index "widgets", ["description"], name: "widgets_description_fts", type: :fulltext
end

class Widget < ActiveRecord::Base
  def self.text_search(query)
    where("MATCH(description) AGAINST(:query)", query: query)
  end

  def self.like_search(query)
    where("description like ?", "%#{query}%")
  end
end

RSpec.configure do |config|
  config.default_formatter = "doc"
  config.before(:suite) do
    DatabaseCleaner.clean_with(:truncation)
  end
  config.before(:each) do
    DatabaseCleaner.strategy = :transaction
  end
end

RSpec.describe Widget, type: :model do
  describe ".text_search" do
    after(:all) { Widget.delete_all }
    it "fails when cleaning with start/clean" do
      DatabaseCleaner.start

      text_search_test

      DatabaseCleaner.clean
    end

    it "fails when cleaning with block" do
      DatabaseCleaner.cleaning do
        text_search_test
      end
    end

    it "succeeds with manual cleaning (fails at random, unless it is first or the only test run)" do
      Widget.delete_all

      text_search_test

      Widget.delete_all
    end
  end

  describe ".like_search" do
    it "succeeds when cleaning with start/clean" do
      DatabaseCleaner.start

      like_search_test

      DatabaseCleaner.clean
    end

    it "succeeds when cleaning with block" do
      DatabaseCleaner.cleaning do
        like_search_test
      end
    end

    it "succeeds with manual cleaning" do
      Widget.delete_all

      like_search_test

      Widget.delete_all
    end
  end

  private

  def create_widgets
    Widget.create()
    match = Widget.create(description: "The quick brown fox jumps over the lazy dog")
    Widget.create()

    match
  end

  def text_search_test
    match = create_widgets
    expect(Widget.text_search("fox")).to contain_exactly match
  end

  def like_search_test
    match = create_widgets
    expect(Widget.like_search("fox")).to contain_exactly match
  end
end

Expected output:
Fetching gem metadata from https://rubygems.org/..........
Fetching version metadata from https://rubygems.org/.
Resolving dependencies...
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.10.1
Using thread_safe 0.3.5
Using builder 3.2.2
Using arel 6.0.4
Using database_cleaner 1.5.3
Using diff-lcs 1.2.5
Using mysql2 0.4.5
Using rspec-support 3.5.0
Using bundler 1.13.7
Using tzinfo 1.2.2
Using rspec-core 3.5.4
Using rspec-expectations 3.5.0
Using rspec-mocks 3.5.0
Using activesupport <IP_ADDRESS>
Using rspec 3.5.0
Using activemodel <IP_ADDRESS>
Using activerecord <IP_ADDRESS>
-- create_table(:widgets, {:force=>true})
   -> 0.0701s
-- add_index("widgets", ["description"], {:name=>"widgets_description_fts", :type=>:fulltext})
   -> 0.4454s

Randomized with seed 46507

Widget
  .text_search
    succeeds with manual cleaning (fails at random, unless it is first or the only test run)
    fails when cleaning with start/clean (FAILED - 1)
    fails when cleaning with block (FAILED - 2)
  .like_search
    succeeds when cleaning with block
    succeeds when cleaning with start/clean
    succeeds with manual cleaning

Failures:

  1) Widget.text_search fails when cleaning with start/clean
     Failure/Error: expect(Widget.text_search("fox")).to contain_exactly match

       expected collection contained:  [#<Widget id: 5, description: "The quick brown fox jumps over the lazy dog">]
       actual collection contained:    []
       the missing elements were:      [#<Widget id: 5, description: "The quick brown fox jumps over the lazy dog">]
     # ./mysql2_full_text_issue.rb:122:in `text_search_test'
     # ./mysql2_full_text_issue.rb:66:in `block (3 levels) in <main>'

  2) Widget.text_search fails when cleaning with block
     Failure/Error: expect(Widget.text_search("fox")).to contain_exactly match

       expected collection contained:  [#<Widget id: 8, description: "The quick brown fox jumps over the lazy dog">]
       actual collection contained:    []
       the missing elements were:      [#<Widget id: 8, description: "The quick brown fox jumps over the lazy dog">]
     # ./mysql2_full_text_issue.rb:122:in `text_search_test'
     # ./mysql2_full_text_issue.rb:73:in `block (4 levels) in <main>'
     # ./mysql2_full_text_issue.rb:72:in `block (3 levels) in <main>'

Finished in 0.68526 seconds (files took 1.07 seconds to load)
6 examples, 2 failures

Failed examples:

rspec ./mysql2_full_text_issue.rb:63 # Widget.text_search fails when cleaning with start/clean
rspec ./mysql2_full_text_issue.rb:71 # Widget.text_search fails when cleaning with block

Randomized with seed 46507

I've temporarily sidestepped this issue but selectively disabling database cleaner on specs in which this error is present:
#  spec/support/database_cleaner.rb
RSpec.configure do |config|
  # ...
  config.before(:each) do
    DatabaseCleaner.start unless manually_cleaned?
  end

  config.append_after(:each) do
    DatabaseCleaner.clean unless manually_cleaned?
  end

  def manually_cleaned?
    self.class.metadata[:manually_cleaned]
  end
end

Then to skip automatic cleaning in a spec:
RSpec.describe Widget, manually_cleaned: true do
  # ...
end


pin package version

...
Hi thanks for making this good tool free available!
Due to some of the dependency packages change, newly installed cell2location encountered error. Such as numba (0.57.1).
After pin numb==0.56.4, cell2location import sucessfully.
If it is possible, pin the package version would be great. Or provide your working conda env yml. So use can verify the package version.
Thank you very much for consideration.

Thanks for this suggestion. Let's see if this numba issue resolves itself within a few days/weeks - it could be a temporary problem.


Support running benchmarks on a local repository

Changes:

split the code into bin/ and lib/ directories (to make room for making each more complicated);
add support for passing a path to a local Git repository;
restructure the Cmdliner DSL into more modular components (i.e. Source, Docker_config).
restructure utils.ml slightly and add an interface

Please let me know what you think of it :slightly_smiling_face:

Example local pipeline:

This is so much cleaner and modular, thank you for the refactoring! I added a commit with two very tiny corrections. :)

I added a commit with two very tiny corrections. :)

Thanks :tada: