Move 'planned process' to a more general ontology, and simplify definition

Ontologies such as ENVO and AGRO are using 'planned process'. These are not biomedical ontologies so it's odd to import OBI modules from a non-biomedical ontology. Indeed planned processes are not specific to investigations even. Bank robberies, programming, releasing an ontology, executions of business plans, trips to the shop are all planned processes.
Arguably ravens, non-human primates and jumping spiders carry out planned processes, and planned process should be in the realm of NBO. However, from what I can understand of the recursive chain of definitions, these would be excluded as there is arguably no "concretization of a plan"; in which case a name like "execution of plan" might be a better primary label for this class.
Can we seed a new high level ontology of human social behaviors for classes such as 'planned process'? Alternatively/additionally, include new OBI-specific classes in OBI such as "investigation process". This would have a straightforward OWL definition: process and part-of some investigation.
Also, if we were to make the move, can we simplify the definition? The definition itself is relatively straightforward and corresponds to an unambiguous OWL axiom. However, the elements of the definition are not intuitive, and recursively expanding these leads to strangeness. This is important because I'm not entirely sure that current usages of the class in external ontologies fit the definition. Having simpler easier to understand definitions lead to more consistent usage.
This is what I mean:

planned process: A processual entity that realizes a plan which is the concretization of a plan specification

plan specification: A directive information entity with action specifications and objective specifications as parts that, when concretized, is realized in a process in which the bearer tries to achieve the objectives by taking the actions specified

directive information entity: An information content entity whose concretizations indicate to their bearer how to realize them in a process is this correct?
action specifications : A directive information entity that describes an action the bearer will take is this correct? surely it is not the bearer of the IE that takes the action??

From a formal perspective I think there are some issues here (perhaps with my understanding). The talk of bearer is confusing, as the bearer of the plan does not take actions, does it?
Many of these have comments and editors notes indicating issues from almost a decade ago, and also open tickets from 2011 such as https://github.com/information-artifact-ontology/IAO/issues/112
I would argue that a less formal but simpler definition is better than a formal and incomplete/uninterpretable definition, and will lead to more consistency in usage.

+1 for this. I think this is ready to bud off into a more general, small, and relatively static module.

From a formal perspective I think there are some issues here (perhaps with my understanding). The talk of bearer is confusing, as the bearer of the plan does not take actions, does it?
[...]
I would argue that a less formal but simpler definition is better than a formal and incomplete/uninterpretable definition, and will lead to more consistency in usage.

I would agree here, especially as our user base now includes people in the policy realm. They're not going to wade through dense wording. We could include elucidations or similar to be very specific.

+1
And yes the "bearer" language is unnecessarily restrictive. I think there
are some aspects of this where my experience with the document act ontology
might be useful. So, I am more than willing to contribute to getting the
static module Pier Luigi talks about off the ground.
On Mon, May 14, 2018 at 10:14 AM, Pier Luigi Buttigieg <
<EMAIL_ADDRESS>wrote:

+1 for this. I think this is ready to bud off into a more general, small,
and relatively static module.
From a formal perspective I think there are some issues here (perhaps with
my understanding). The talk of bearer is confusing, as the bearer of the
plan does not take actions, does it?
[...]
I would argue that a less formal but simpler definition is better than a
formal and incomplete/uninterpretable definition, and will lead to more
consistency in usage.
I would agree here, especially as our user base now includes people in the
policy realm. They're not going to wade through dense wording. We could
include elucidations or similar to be very specific.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-388853998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIvhrgTVBGKoh7JCvAExBO55L4SQGJ6Aks5tyZ9igaJpZM4T96vT
.

I have strong reservations about this. OBI has been burned previously by
moving 'information' out into IAO with the same argument that it is
general. That led to other people being involved, and subsequent paralysis
of IAO development, as apparent from the plenty of decade old open tickets
that are now hard to fix.
Action specification is indeed wrong; it should be:
action specifications : A directive information entity that when
concretized as a plan describes an action that the bearer of the plan
should take in order to achieve the objective of the plan.
One of the problems with these definitions has been the reluctance of Barry
to ever talk about the concretizations (plans in peoples heads). That led
to the arcane language.
I am in favor of a BFO extension with high level classes utilized
throughout OBO foundry ontologies, which should include planned process,
information etc. That would ensure that there will also be an active
developer community. I am skeptical about moving this into any kind of
specialized 'human act' ontology for the above reasons.

Bjoern

On Mon, May 14, 2018 at 8:28 AM, Mathias Brochhausen <
<EMAIL_ADDRESS>wrote:

+1
And yes the "bearer" language is unnecessarily restrictive. I think there
are some aspects of this where my experience with the document act ontology
might be useful. So, I am more than willing to contribute to getting the
static module Pier Luigi talks about off the ground.
On Mon, May 14, 2018 at 10:14 AM, Pier Luigi Buttigieg <
<EMAIL_ADDRESS>wrote:

+1 for this. I think this is ready to bud off into a more general, small,
and relatively static module.
From a formal perspective I think there are some issues here (perhaps
with
my understanding). The talk of bearer is confusing, as the bearer of the
plan does not take actions, does it?
[...]
I would argue that a less formal but simpler definition is better than a
formal and incomplete/uninterpretable definition, and will lead to more
consistency in usage.
I would agree here, especially as our user base now includes people in
the
policy realm. They're not going to wade through dense wording. We could
include elucidations or similar to be very specific.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-388853998,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AIvhrgTVBGKoh7JCvAExBO55L4SQGJ6Aks5tyZ9igaJpZM4T96vT>

.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-388859085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANN9InN5UblOwqSU0TTO-X7hrhJhqer6ks5tyaKvgaJpZM4T96vT
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

I sympathize fully with some of the issues of budding off and then the budded ontology becoming stale. Perhaps @pbuttigieg could share some success stories here to encourage? Maybe there are best practices for budding off?

I am in favor of a BFO extension with high level classes utilized throughout OBO foundry ontologies

would this not end up with precisely the problems you outline? In theory budding off into an independent component will allow an uncoupled release process and less obstacles overall. Or perhaps by extension you mean an independent ontology that directly subclasses BFO classes - this is pretty much what I had in mind.
Modularization is hard...

Yes, I meant an independent ontology that directly subclasses BFO. Which
would be relatively small, should be imported by most OBO foundry
ontologies, packaged with relationships and domain / range definitions...
Other terms in OBI such as 'organism' come to mind that should live there.
I had worked on my dream version of that of and on; maybe we can discuss in
one of the upcoming OBO operations calls?

Bjoern

On Mon, May 14, 2018 at 9:17 AM, Chris Mungall<EMAIL_ADDRESS>wrote:

I sympathize fully with some of the issues of budding off and then the
budded ontology becoming stale. Perhaps @pbuttigieg
https://github.com/pbuttigieg could share some success stories here to
encourage? Maybe there are best practices for budding off?
I am in favor of a BFO extension with high level classes utilized
throughout OBO foundry ontologies
would this not end up with precisely the problems you outline? In theory
budding off into an independent component will allow an uncoupled release
process and less obstacles overall. Or perhaps by extension you mean an
independent ontology that directly subclasses BFO classes - this is pretty
much what I had in mind.
Modularization is hard...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-388875690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANN9IuqSHmv4-AaTxRePKBcCMz9ZHVOaks5tya4ygaJpZM4T96vT
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

@bpeters42

I have strong reservations about this. OBI has been burned previously by
moving 'information' out into IAO with the same argument that it is
general. That led to other people being involved, and subsequent paralysis
of IAO development, as apparent from the plenty of decade old open tickets
that are now hard to fix.

It's a shame that this is currently stuck, but the idea behind it was good I think. IAO is of central importance across the board

One of the problems with these definitions has been the reluctance of Barry
to ever talk about the concretizations (plans in peoples heads). That led
to the arcane language.

I appreciate that some of the upper level material can take time to finalise, but in the meantime, we have a lot of users that want to talk about protocols and plans. That part shouldn't be complicated - they just need a class to declare that they have a protocol archived somewhere.

I am in favor of a BFO extension with high level classes utilized
throughout OBO foundry ontologies, which should include planned process,
information etc. That would ensure that there will also be an active
developer community. I am skeptical about moving this into any kind of
specialized 'human act' ontology for the above reasons.

Yes, a small, extensible ontology for this to broker between BFO and applications would work. This could be pulled in for human acts etc.
@cmungall @bpeters42

I sympathize fully with some of the issues of budding off and then the budded ontology becoming stale/paralyzed. Perhaps @pbuttigieg could share some success stories here to encourage? Maybe there are best practices for budding off?

We've spun off a few ontologies from ENVO (AGRO, FOODON, SDGIO) to motivated communities with an implementation/application mindset. There are some teething issues, but the amount of work that gets done this way (benefiting from practitioner insight and networks) is much more than we could have handled alone. The likelihood that the content will be used is increased too. Best practices would include:

Be sure that the scope and mission of the spin-off ontology (SpO) is very clear and fits well with that of the source ontology (SrcO) and the OBO Library in general. Watch for mission creep.
Use the ontology starter kit to standardise the spin-up so that maintenance and fixes are understandable to many, not just the team involved
The SrcO should help the SpO handle any new BFO alignment early, so people can get busy working in their domain-specific comfort zone.
The SrcO team should maintain a mentorship role for the SpO team (if needed), detecting issues early (there will be a bunch) until SpO starts running smoothly.
The whole team should ensure that SpO follows the OBO principles, especially when it comes to importing existing content and staying within scope.
The SrcO team should help SpO choose which imports to use, and also ping the leads of any potentially stale/unmaintained ontologies in the import list to check if they are active. If not, then I think the obo-discuss list should be notified and a new development team assembled.

As noted, there will be some teething issues here, but it's worth it in the long run. Interestingly, the SpOs often start creating content that's not in the library yet and that should, itself, bud-off into a small module (like the planned processes). If this is encouraged, I think it will enrich the whole library.

There seem to be two orthogonal issues discussed in this thread:

What Chris originally raised, namely "Ontologies such as ENVO and AGRO
are using 'planned process'. These are not biomedical ontologies so it's
odd to import OBI modules from a non-biomedical ontology. Indeed planned
processes are not specific to investigations even.... "

Pier Luigi (and Matthias) mentioned in response, saying: " we have a
lot of users that want to talk about protocols and plans....", and
outlining how these should be subclassed with things not in OBI scope.

So issue 1) is 'OBI shouldn't be the source for general terms re-used by
ontologies outside OBI scope', while issue 2) is 'many people want to use
terms currently in OBI'.
Both can be addressed by creating a new mid-layer ontology that includes a
few classes and relations (including 'planned process') which are commonly
re-used
My objection was to Chris initial suggestion of making all OBI terms in the
planned process domain a subclass of 'investigation process'. We went down
that route before: Should OBI not have a class for e.g. DNA extraction
because the same process could also be part of a manufacturing protocol?
What about temperature measurements which are routinely performed in cars?
What processes are really unique to an investigation? I suspect none that
aren't in OBI yet, which means we can stop OBI development, and instead
focus on spinning out a few hundred-thousand 'SpOs' /s
Seriously: Yes, there is a need for high-level coordination for the (few)
classes that are highly re-used across OBO foundry ontologies, and doing
that right could form a much better (and easier to understand) basis for
coordinated ontology development. I would be happy to contribute to that,
and I am sure the rest of the OBI community will be as well. And I am
excited about all ontology efforts that want to subclass the plan
specification etc. terms. I am much less excited if they want to subsume
OBI terms, and risk another IAO disaster of loosing control of terms that
we took decades to define.

Bjoern

to some new application ontology of 'human acts' that Chris referred to,
which would suffer the same problems we had with IAO.
It seems to me the real point here is that we have classes subclassing BFO
that should ideally be re-used across OBO ontologies. I am all in favor of
pulling out a few terms from OBI for that purpose. With the understanding
that modifications of these terms would be
My point is that OBI is fundamentally dependent on the current definitions
of planned processes (and the connected definitions of plans, plan
specifications, information content entities etc.),  and how they can be
made compatible with BFO. That was a multi-year fight, but the outcome is
actually quite awesome, and the fact that others want to subclass these
terms
. If other developers find the OBI modeling useful, and want to re-use it
for non investigation processes, that is awesome, and we want to encourage
it. But not in the way that IAO was developed, where we ceased control of
key terms.
On Tue, May 15, 2018 at 6:22 AM, Pier Luigi Buttigieg <
<EMAIL_ADDRESS>wrote:

PS: The same logic would apply to the service branch: it should probably
live in a small module. See SDG-InterfaceOntology/sdgio#110
https://github.com/SDG-InterfaceOntology/sdgio/issues/110
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-389164480,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANN9InpNoeGhvF_C8MZlHMWGvwEN1Qu_ks5tytaZgaJpZM4T96vT
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

Hi,
as soon as Bjoern brought up IAO I re-considered my initial enthusiasm for
the proposal of a new ontology, but didn't put that in writing, since I was
traveling.
I agree with Bjoern's suggestions in his e-mail directly below.
Best,
Mathias
On Tue, May 15, 2018 at 11:58 PM, bpeters42<EMAIL_ADDRESS>wrote:

There seem to be two orthogonal issues discussed in this thread:

What Chris originally raised, namely "Ontologies such as ENVO and AGRO
are using 'planned process'. These are not biomedical ontologies so it's
odd to import OBI modules from a non-biomedical ontology. Indeed planned
processes are not specific to investigations even.... "

Pier Luigi (and Matthias) mentioned in response, saying: " we have a
lot of users that want to talk about protocols and plans....", and
outlining how these should be subclassed with things not in OBI scope.

So issue 1) is 'OBI shouldn't be the source for general terms re-used by
ontologies outside OBI scope', while issue 2) is 'many people want to use
terms currently in OBI'.
Both can be addressed by creating a new mid-layer ontology that includes a
few classes and relations (including 'planned process') which are commonly
re-used
My objection was to Chris initial suggestion of making all OBI terms in the
planned process domain a subclass of 'investigation process'. We went down
that route before: Should OBI not have a class for e.g. DNA extraction
because the same process could also be part of a manufacturing protocol?
What about temperature measurements which are routinely performed in cars?
What processes are really unique to an investigation? I suspect none that
aren't in OBI yet, which means we can stop OBI development, and instead
focus on spinning out a few hundred-thousand 'SpOs' /s
Seriously: Yes, there is a need for high-level coordination for the (few)
classes that are highly re-used across OBO foundry ontologies, and doing
that right could form a much better (and easier to understand) basis for
coordinated ontology development. I would be happy to contribute to that,
and I am sure the rest of the OBI community will be as well. And I am
excited about all ontology efforts that want to subclass the plan
specification etc. terms. I am much less excited if they want to subsume
OBI terms, and risk another IAO disaster of loosing control of terms that
we took decades to define.

Bjoern

to some new application ontology of 'human acts' that Chris referred to,
which would suffer the same problems we had with IAO.
It seems to me the real point here is that we have classes subclassing BFO
that should ideally be re-used across OBO ontologies. I am all in favor of
pulling out a few terms from OBI for that purpose. With the understanding
that modifications of these terms would be
My point is that OBI is fundamentally dependent on the current definitions
of planned processes (and the connected definitions of plans, plan
specifications, information content entities etc.), and how they can be
made compatible with BFO. That was a multi-year fight, but the outcome is
actually quite awesome, and the fact that others want to subclass these
terms
. If other developers find the OBI modeling useful, and want to re-use it
for non investigation processes, that is awesome, and we want to encourage
it. But not in the way that IAO was developed, where we ceased control of
key terms.
On Tue, May 15, 2018 at 6:22 AM, Pier Luigi Buttigieg <
<EMAIL_ADDRESS>wrote:

PS: The same logic would apply to the service branch: it should probably
live in a small module. See SDG-InterfaceOntology/sdgio#110
https://github.com/SDG-InterfaceOntology/sdgio/issues/110
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-389164480,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANN9InpNoeGhvF_
C8MZlHMWGvwEN1Qu_ks5tytaZgaJpZM4T96vT>
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
https://maps.google.com/?q=9420+Athena+Circle+
La+Jolla,+CA+92037,+USA&entry=gmail&source=g
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/929#issuecomment-389386967,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIvhrtm3kXBcro8CVZ2Vyv_0MElGpPg2ks5ty6PRgaJpZM4T96vT
.

Being resolved in Experimental OBO Core - https://github.com/OBOFoundry/Experimental-OBO-Core


install.sh: Add wget fallback if curl isn't available

Reportedly, some systems don't have curl but wget. With this patch,
install.sh will use wget instead of curl if the latter is not available
on the target system.
Change-Id: I0bc78feec6d8e1dbf7fbef7c2e10833b79bdbbdc
Signed-off-by: Joakim Roubert<EMAIL_ADDRESS>

I like this, busybox doesn't have curl so this helps.  But busybox also doesn't have systemd/openrc either so....

I like this, busybox doesn't have curl so this helps.

Thanks! Me and @erikwilson discussed the curl + wget thing in https://github.com/rancher/k3s/pull/747, so I thought I'd might come up with this suggestion.

But busybox also doesn't have systemd/openrc either so....

I guess we have a suggestion for another future PR right there!

Thanks @joakimr-axis!


Add CI configuration

Fixes #13

I have enabled Travis on my fork to test this and it works fine. @mar9000 could you enable Travis for this repo?

I'll do it

I've also enabled Travis on this repository.


Default key-binding added (ALT+Q), available everywhere.

I decided to add a default key binding for SO search. I hope you find it useful as well.
Best Regards,
Norbert

Thnx!


Default or custom sort not working.

I want to fetch records and it works fine, but I want to sort it with a particular column.
so I tried this in my schema -
protected $defaultSort = '-createdAt';
but this is not sorting the records, I also tried with other column names, no luck.
in my controller index function
if I use
 $spaces = $spaces->where('user_id', $user->id);
 $spaces = $spaces->sort('createdAt');

error attached below is received.  (where condition works fine, only sort is triggering that error).
I do not want to handle sort from the url like GET /spaces?sort=-createdAt HTTP/1.1 .
Please guide.

That exception message doesn't help. If you look down the stack trace, you'll find that exception is caused by a previous exception. Can you provide details of the first exception in the stack trace, not the last?

Please see here.

Hi, Does this help?

Do you mean this?
this
$this->encodeOptions
returns 0

No.
I need to see the entire stack trace of the exception. You've only provided part of it.
If you go to the Laravel log in the /storage/logs directory, you should see the exception in the log. But as I have already stated, I don't need just the first exception: the exception you have provided has previous exceptions - and I need to see all of those previous exceptions.
Please provide the entire stack trace - not as an image, as a copy and paste of the stack trace from the Laravel log.
Otherwise there is no way for me to help you, and I'll have to close the issue.

I don't fully understand why you are sorting in the controller action like that. The $defaultSort property on the schema is working, and fully tested so I know for sure that it works.
If you were putting a $defaultSort property on your schema AND then sorting in the controller action, then obviously the controller action sort will override what the schema has sorted by.

Firstly, why are you using a custom index action? Why aren't you using the one provided by this package? If it is so you can filter  by the current user, you should not need to do that yourself if you correctly follow the guidance in the Authorization chapter, particularly around using an indexQuery() hook:
https://laraveljsonapi.io/docs/1.0/requests/authorization.html#index-filtering
Secondly, on the schema (and as explained in the docs) the default sort uses the JSON:API field names, not the model column names.
Are you 100% sure it shouldn't be:
protected $defaultSort = '-createdAt';

I.e. createdAt not created_at??
Also as already mentioned, if you're using a custom index action and sorting after the schema has done its work, then that will override what is on your schema.
Please:

Remove your custom index action and use the one provided by this package.
Ensure that the JSON:API field name is correct on the schema $defaultSort, i.e. createdAt or created_at.
Make sure that when you send the HTTP request, you do not have a value for the sort parameter. The default sort is only used if the sort parameter is not present in the request. I.e. a ?sort= would prevent the default sort from being applied.

This issue is taking up a lot of my time, so I need to be clear: default sorting does work, and the tests prove this is case. It's tested extensively in the laravel-json-api/eloquent package and I've just pushed a test to the laravel-json-api/laravel package that proves it's working there. It is also working in the large production application that I'm using the package in.
At the moment therefore I have no reason to suspect there's a problem with this package, and you need to look carefully at what you're doing in your application that could be causing the problem. I can't help you with that - because I can't debug what's going on in your application.

I understand, but the defaultSort do not work for me, which is why I had to use the custom function.
for the custom query I can use which you referred from the documentation, but for the default sort,
I tried with "-createdAt", "-id", "-created_at",  and it is not working for me.
I have also removed the index function and used Package's use Actions\FetchMany; and schema has now
protected $defaultSort = '-createdAt';
results are currently showing in ascending order, which is not right.
Let me know what info I need to provide further to quickly wrap this up.
Regards.

Can you confirm you're on the latest version of the package?
So the $defaultSort property must be -created_at.
Can you confirm that it sorts by the correct order if you send the following request:
/api/v1/spaces?sort=-created_at

Can you also provide a copy & paste of the whole schema class?

Can you also be clear about what you mean when you say "it is not working for me".
When you have $defaultSort property set, do you get an exception? Or does it just return the values unsorted?

Hi, It returns values unsorted, I do not receive error.
My Schema file.
<?php

namespace App\JsonApi\V1\Spaces;

use App\Models\Space;
use LaravelJsonApi\Eloquent\Schema;
use LaravelJsonApi\Eloquent\Fields\ID;
use LaravelJsonApi\Eloquent\Fields\Str;
use LaravelJsonApi\Eloquent\Fields\Attribute;
use LaravelJsonApi\Eloquent\Fields\DateTime;
use LaravelJsonApi\Eloquent\Filters\WhereIdIn;
use LaravelJsonApi\Eloquent\Fields\SoftDelete;
use LaravelJsonApi\Eloquent\Contracts\Paginator;
use LaravelJsonApi\Eloquent\Fields\Relations\HasOne;
use LaravelJsonApi\Eloquent\Pagination\PagePagination;
use LaravelJsonApi\Eloquent\Fields\Relations\BelongsTo;

class SpaceSchema extends Schema
{
    protected $defaultSort = '-createdAt';
    /**
     * The model the schema corresponds to.
     *
     * @var string
     */
    public static string $model = Space::class;

    /**
     * Get the resource fields.
     *
     * @return array
     */
    public function fields(): array
    {
        return [
            ID::make(),
            Str::make('name'),
            Str::make('subdomain'),
            Str::make('logo'),
            Str::make('icon'),
            DateTime::make('created_at')->sortable()->readOnly(),
            DateTime::make('updated_at')->sortable()->readOnly(),
            BelongsTo::make('user_id')->type('users'),
            Str::make('password_current')->hidden(),
            SoftDelete::make('deleted_at'),
            HasOne::make('team_id')->type('teams'),
        ];
    }

    /**
     * Get the resource filters.
     *
     * @return array
     */
    public function filters(): array
    {
        return [
            WhereIdIn::make($this)
        ];
    }

    /**
     * Get the resource paginator.
     *
     * @return Paginator|null
     */
    public function pagination(): ?Paginator
    {
        return PagePagination::make();
    }
}

With
/api/v1/spaces?sort=-created_at

It works fine.
but with
/api/v1/spaces (with $defaultSort in schema)
it does not give desired results.
Attached is my package version info -

Your schema $defaultSort property should be -created_at.... the copy & paste shows it's -createdAt. Though there's something weird there as you should be getting an exception when using an invalid sort name.
Your image of the request with sort=-created_at does not show the resources in the correct order, i.e. that is not working either.
I strongly suspect you've got an old version of the package. Plus run:
composer show laravel-json-api/laravel

And copy & paste the output here.

Or try fixing it as follows:
composer require laravel-json-api/laravel:^1.0.0-beta.4 --no-update
composer up laravel-json-api/*

And then let me know whether it works or not.

composer require laravel-json-api/laravel:^1.0.0-beta.4 --no-update
composer up laravel-json-api/*

this solved the issue.


Bugfix create collection with options

Adding a fix for #1734 .
I might come up with a pull request for json schema's:
https://docs.mongodb.com/manual/reference/operator/query/jsonSchema/#op._S_jsonSchema
@jenssegers would you like to have this feature?

@deviouspk, when i recreate new PR from this PR, i lost some changes

Closing in favor of https://github.com/jenssegers/laravel-mongodb/pull/1953


Text is truncated

Sorry to say that the issue I previously reported has re-occurred.  See image.
It seems to happen more often when my system is under heavy load.  I'm on an 8th gen intel laptop and running android studio is almost too much for it.

Sorry for the late response.
I updated to the newer version in v2.0.0 by replacing the Timer with TickerProvider.

That's working perfectly now.  Thank you.


Doesn't work with mariadb

I've followed the guide, copy-pasting as I go with the only difference being a different database software, mariadb.
I get the error: ER_NO_SUCH_TABLE: Table 'strapi.accounts' doesn't exist

Turns out synchronize wasn't on.

@sebasptsch Can you also write a little bit about what you did? It might help someone else who is also facing the same issue.

Initially when I setup the authentication from the blog post on the Strapi Blog I copied how the postgresql server url was set out but I wasn't sure whether sync was database dependant so I removed it. Because of this nextauth was unable to create a new table in the Strapi database and therefore errored every time to use it. To fix it I added sync back after seeing it in the next-auth documentation where it describes it's purpose as creating new tables to enter the auth data within. This allowed the next-auth to create the table and therefore resolve the error I was having.

@sebasptsch Thank you.


Changing temp threshold  on only one host?

Hi,
I was wondering if its possible to change the threshold only for one Host? i tried checking on triggers to change but couldn't find the option
Thank you

Disks or cpus? Linux or Windows?

thanks for the reply, only CPUs

Host -> Macros -> Inherited -> Change

thanks for the reply, i went to that section but did not see anything of mini IPMI temps

Means template is not assigned to the host.

i checked and it is assigned

Then template is not up to date:
https://github.com/nobodysu/zabbix-mini-IPMI/blob/master/Template_mini-IPMI_v2.xml

thanks for the reply, i tried updating the template by adding and i get this

after checking it did make the changes thank you

quick question forgot to mention if i would want to do the same for the disk temp?

Right now it's in the file: https://github.com/nobodysu/zabbix-mini-IPMI/blob/master/mini_ipmi_smartctl.py#L32
Will be moved to macro someday.

Thanks for the reply, so this would apply to all hosts if changing the .py? possible to change on the template for all hosts

On every host there is a copy of mini_ipmi_smartctl.py with separate thresholds. Therefore, it's all per-host and cannot be changed through template, yet.
However, I advice you to think twice before changing disk thresholds because it's based on Goggle research: http://www.buildcomputers.net/hdd-temperature.html

Thank you again, your right ill keep that in mind


Observer register Issue

Hello,
I have just integrated your library.
When I alloc first time, it works proper. Then I change root view controller of window for logout.
Then I again login and change root view controller to the SJSegmentedViewController.
It says
"An instance 0x7fa0e38b5600 of class UICollectionView was deallocated while key value observers were still registered with it."
I have collection view in my class So I have implemeted as per your doc to observer the scrolling
extension HomeVC: SJSegmentedViewControllerViewSource {
func viewForSegmentControllerToObserveContentOffsetChange(controller: UIViewController,
                                                          index: Int) -> UIView {
    return self.clcView
}

Let me know the solution because I am in hurry.
Thanks.

@kishanraiyani03 ,
We have pushed a new version (1.1.0) of SJSegmentedScrollView to CocoaPods. Please verify.

It works.
Thanks.


Multiselect doesn't work on MacOS

Latest version 1.1.11 doesn't correctly recognize command button click. The bug was fixed by downgrading to 1.1.10. What is odd is that if I use current state of the repo by copy/paste of core package, then it works. This means that it is not as much for the change of the code, as much as how the bundler(in my case CreateReactApp) is using the new version.
As additional info, it happens on ControlledTreeEnvironment component.
It is very much re-occurrence of https://github.com/lukasbach/react-complex-tree/issues/80

Since I don't have a mac, I can't really test or verify this, I don't see any reasons in the code why this would degrade between 1.1.10 and 1.1.11. I'm happy for anyone with a mac who could test this and maybe see where in the code this click gets lost. Note that, in the code, pretty much all that happens is
export const isControlKey = (e: React.MouseEvent<any, any>) =>
  e.ctrlKey ||
  (navigator.platform.toUpperCase().indexOf('MAC') >= 0 && e.metaKey);

within an onClick event, otherwise the logic should be the same for windows and mac, and it seems to work under Windows, so maybe someone with a mac could already verify or report whether there is something not working with this snippet.

@lukasbach @selfrefactor on my mac it works correctly, I checked on my project locally and also checked in the storybook https://rct.lukasbach.com/storybook/?path=/story/core-basic-examples--actions, cmd + click works and also cmd+shift+click works, I don't see any problems

thank you for the information. I will have access to Mac next week, so I will test it personally to assure that this weird issue is gone. I will write again once I know more.

Thanks both of you for your investigation, interested to see if it works for you @selfrefactor.

I will close the issue, as I was unable to test it and I don't want to be reason for holding the issue open.


Safari iOS does support clipboard read

https://caniuse.com/async-clipboard treats Safari iOS support as partial with the note "Supports writing to clipboard but not reading." This was added in https://github.com/Fyrd/caniuse/commit/be0e5093a419a89f2918be50d0e2d2b94112394d and I can't find any discussion related to it.
In some testing I find that Safari iOS does support reading from the clipboard, i.e. pasting into the web site. The commit message of https://github.com/WebKit/WebKit/commit/a1d6921df0793765bf78a1876b83ba7f453b0052 explains how it works:

In order to make it possible for web pages to programmatically paste without opening the door to privacy and
security issues, we make paste commands triggered from bindings present platform UI on iOS, in the form of a
callout bar with the single option to paste. This UI is dismissed upon any user interaction; furthermore, any
user interaction short of explicitly triggering the "Paste" action subsequently prevents the page from executing
the paste (and causes execCommand to return false). However, if the paste action is chosen by the user, we
instead follow through with the programmatic paste command.

That was about document.execCommand('Paste') at the time, but testing navigator.clipboard.readText() I saw the same callout bar, so I think the same rules are used there.
I don't know which version of Safari introduced this or exactly what the rules are. @whsieh @rniwa from that WebKit review might know more.
Ideally the note should say what developers needs to know. Mentioning the callout bar would make sense, I think.

Yes, that's accurate — async clipboard's readText() and read() APIs are supported by default in Safari on iOS since iOS 13.4 and macOS 10.15.3, and still behave in the same way on the latest versions of iOS/macOS.
These same clipboard access rules apply to document.execCommand("paste") as well.

Have made the appropriate updates to reflect iOS support & Safari's behavior here. Thanks!


geoparquet table used by Hive or other components

Expected behavior
we can use sedona's GIS function to generate geometry type
then df.write.format("geoparquet").saveAsTable(xxx) or spark.sql("create table xx as ")
then we can print actual schema both in spark / hive / impala
Actual behavior
then we can print actual schema only in spark , but SequenceFile in hms and Array type in hive / impala
Settings
Sedona version = 1.4.0
Apache Spark version = 3.2.2
API type = Pure SQL & spark-shell
Scala version = 2.12
JRE version = 1.8
Environment = Ambari+apache community components

As far as I know, Hive and Impala do not natively support geometry types or the GeoParquet specification, so the best thing they can do is to read the geometry column in the GeoParquet file as its physical type, which is BINARY type. Users have to decode the binary value as WKB manually. I think Apache Sedona can hardly help improve this situation.

As far as I know, Hive and Impala do not natively support geometry types or the GeoParquet specification, so the best thing they can do is to read the geometry column in the GeoParquet file as its physical type, which is BINARY type. Users have to decode the binary value as WKB manually. I think Apache Sedona can hardly help improve this situation.

@Kontinuation
Even though Hive / Impala donot support geometry type , but they should support other types in geoparquet file .
Actually , we execute "show create table xxx " in Hive / Impala , the file format is SequenceFile rather then Parquet , and the column is just an ARRAY , and could not be accessed by any query .

Even though Hive / Impala donot support geometry type , but they should support other types in geoparquet file .
Actually , we execute "show create table xxx " in Hive / Impala , the file format is SequenceFile rather then Parquet , and the column is just an ARRAY , and could not be accessed by any query .

It is strange that Hive did not treat GeoParquet files as Parquet files. I'll set up a Hive metastore and try reproducing this problem.

Even though Hive / Impala donot support geometry type , but they should support other types in geoparquet file .
Actually , we execute "show create table xxx " in Hive / Impala , the file format is SequenceFile rather then Parquet , and the column is just an ARRAY , and could not be accessed by any query .

It is strange that Hive did not treat GeoParquet files as Parquet files. I'll set up a Hive metastore and try reproducing this problem.

spark's datasource table could not be accessed by other query engines , not only geoparquet , csv either.


Official support for Google Translate on Pub Dev

Hi I searched for the official Google Translate pub dev pkg, but didn't find one. Are there any plans by Google to support it? I will need it for chat. Thanks.

Hi @andesappal,
Although there's no Flutter's official plugin for Google translate, there's a 3rd party plugin that you may try.
Please note that this is not an endorsement for this plugin but just to let you know that there exists a plugin. See if it works per your need.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


'rover landingzone list' command error

In the case where no storage accounts can be found at a particular level, rover will crash with:
vscode@b268f68883df:/tf/rover$ rover landingzone list -level level0

<snip>

@calling process_actions
@calling get_storage_id
@calling list_deployed_landingzones
ERROR: argument --ids: expected at least one argument

TRY THIS:
az storage account show --ids /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/pr
oviders/Microsoft.Storage/storageAccounts/{StorageAccount}
Show properties for a storage account by resource ID.

az storage account show --resource-group MyResourceGroup --name MyStorageAccount
Show properties for a storage account using an account name and resource group.

https://docs.microsoft.com/en-US/cli/azure/storage/account#az_storage_account_show
Read more about the command in reference docs
Error on or near line 278; exiting with status 1
Error on or near line 278; exiting with status 1

@calling clean_up_variables
cleanup variables
clean_up backend_files

closing as fixed in 2111 stable rover


Java enums do not have UNDEFINED.

This means that adding new enum values will break older clients
Already know how to handle in Java enums and plan to submit a changeset in the near future.

Awesome. BTW: java models were contributed by kenny. If you are doing real work on java - would you be interested in providing your own standalone generator?

We have a different Java generator written. I need to merge it back
upstream.
On Jan 15, 2016 4:31 PM, "Michael Bryzek"<EMAIL_ADDRESS>wrote:

Awesome. BTW: java models were contributed by kenny. If you are doing real
work on java - would you be interested in providing your own standalone
generator?
—
Reply to this email directly or view it on GitHub
https://github.com/mbryzek/apidoc/issues/388#issuecomment-172098962.

This ticket should be moved to apidoc-generator


Move test classes to proper package

This PR is just for moving the InterledgerAddress test to the org.interledger package, and renaming HelperHandlerTest to InterledgerPacketHandlerTest.

Codecov Report

Merging #47 into development will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             development      #47   +/-   ##
==============================================
  Coverage          56.55%   56.55%
  Complexity           157      157
==============================================
  Files                 56       56
  Lines               1015     1015
  Branches              98       98
==============================================
  Hits                 574      574
  Misses               391      391
  Partials              50       50

Continue to review full report at Codecov.

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


Delete location /api section from default.conf

This location is essentially unreachable in our deployment.

Nevermind - I didn't pull changes.


Package.swift: update IBM-Swift to Kitura

The BlueSocket and BlueSSLService repositories are now part of the Kitura community organization.  Package.swift should be updated.

Released in v1.4.4.


Modifier keys being held when a window loses and regains focus aren't detected by InputState::consume_key

Describe the bug

In my desktop application, I respond to user commands entered via keystrokes with modifiers. Sometimes, this handling causes the egui window to temporarily lose, and quickly regain, focus. (In particular, I look for Ctrl+Delete and respond by executing a Windows IFileOperation shell command, which causes focus to shift to explorer.exe briefly.) When the window regains focus, if the user wants to perform the same action, they could reasonably still be holding Ctrl and expect that pressing delete would repeat the action. However, InputState::consume_key(Modifiers::CTRL, Key::Delete) returns false (in this state, InputState::consume_key(Modifiers::NONE, Key::Delete) returns true instead).
The user instead has to release Ctrl and re-press it before InputState::consume_key(Modifiers::CTRL, Key::Delete) will return true.
To Reproduce
Steps to reproduce the behavior:

With an egui desktop application in focus, press and don't release Ctrl.
Switch focus to a different app (perhaps by using the mouse), while still holding Ctrl.
Switch focus back to the egui application, while still holding Ctrl.
While still holding Ctrl, press some other keyboard input. The key combination isn't correctly detected by InputState::consume_key, which instead detects it as though Ctrl were not being held.

Expected behavior

Modifier key hold states aren't affected by application focus changes.
Additional information
This doesn't reproduce unless you are holding the modifier with the egui app in focus before switching away from it. If you begin holding the modifier key with some other app in focus, and then switch to the egui app, InputState::consume_key works as expected.
If this is hard to reproduce I can try to put together a minimal example that demonstrates this behavior.
Desktop (please complete the following information):

OS: Windows 10
Version: 22H2

I was hoping that #2933 would fix this, but no such luck; I can still repro on egui 0.22.

Sounds like https://github.com/emilk/egui/pull/2933 does the opposite - it intentionally clears the modifier keys when eframe gains focus. This is because otherwise you have the problem of holding down a modifier, loosing focus, releasing the modifier, and then when switching back to the eframe app, eframe still things the modifier is being held. This is a classic "stuck modifiers" problem. Fixing this would likely require a deep dive into the winit internals on all platforms, and even then I wouldn't count on some key events not being lost.


Add Latvian and Estonian resources

Thanks @andrisll 👍
I was wondering when someone would fill in the obvious empty spot! 😆

Yes, it had to be filled :)
I found a bug though: https://github.com/osmlab/osm-community-index/pull/501


How to flip orientation of a Composite?

Hi Everyone!
I'm working on a 2D side scrolling car game using a car composite.
When the player presses the left or right arrow keys, the car needs to flip around to point in the correct direction.
Can anyone suggest the best (simplest!) way to do this?
Thanks!

Probably just flip the sprite and then invert the controls?

@liabru My custom car composite isn't symmetrical. It looks a bit like this:
http://piqnt.com/planck.js/Car
So I would at least need at least flip the body around.
Also, I'd like to maintain the car's momentum when it changes direction, so that, for example, if it's travelling to the left, and then flips to the right, it still maintains it's current speed.
There might be a few different systems at play here, but the first thing I would need to do is invert the orientation of the composite, which I haven't yet figured out how to do.

You could try scaling the body like this Body.scale(body, -1, 1) but be aware this might have a few issues see #443?

@liabru Amazing, that just works! Thank you! 😄
Here's the code I'm using that does the trick:
  let carBody = car.bodies[0],
      leftWheel = car.bodies[1],
      rightWheel = car.bodies[2];

  Body.scale(carBody, -1, 1);
  carBodySprite.scale.x = -carBodySprite.scale.x;
  Body.setAngularVelocity(leftWheel, -leftWheel.angularVelocity);
  Body.setAngularVelocity(rightWheel, -rightWheel.angularVelocity);
  carPower = -carPower;

It's a very natural looking effect.

@liabru Oh no!
More testing uncovered an unexpected side-effect.
My car starts off life like this:

If it hits a wall, its rotation changes as it bumps against the wall surface.
But, if the user inverts the car's orientation by pressing the the "left" button at the same time as its rotation changes, the car body's current rotation is locked into the composite:

Eventually, if its scale changes enough times while it's rotating, the car looks something like this:

So my next question is:
"Is there a way to normalize the rotation of the body to 0 Radians before scaling it?"
(It seems Body.rotate is only used to set a relative angle - how could I set an absolute angle? Or, and am I just thinking about the problem in the wrong way?)

@liabru Solved!
I used setAngle to set the carBody to 0 Radians before inverting the scale:
Body.setAngle(carBody, 0);
Body.scale(carBody, -1, 1);

@liabru @kittykatattack I'm trying to utilize this technique by I ran into some issues - I have a composite which consists of a torso, a "hand" and a constraint between them. My problem is that the constraint is not being flipped at all (its position doesn't change). Any ideas how I could achieve that?
I use following code for my flipping:
Matter.Composite.scale(this.body, -1, 1, this.torso.position, true);


Add tutorials for OpenCV Tracker and Multitracker

This pull request needs #300 and #329 , it contains tutorials for using OpenCV Tracker and MultiTracker
There are 3 tutorials on this pull request:

Introduction to OpenCV Tracker and roiSelector GUI
Using custom function for TrackerKCF
Using MultiTracker class

Very nice job, @kurnianggoro! I proofread the tutorials. They are pretty good, just some minor typos.

Did you get it to compile nicely and without problems locally? If so, what was the cmake flag you had to use?

@iglesias  you should download plantuml.jar, and then use flag
-DBUILD_DOCS=ON -DPLANTUML_JAR=/home/kurnianggoro/plantuml.jar
change the last parameter with the plantuml.jar path

@iglesias I just realized that I pushed the update in wrong place, pushed the update in optimization.

No worries, good that you updated it here already.

@vpisarev moved to #353


[webview_flutter] Remove dependency on flutter.dev and google.com

No CHANGELOG change: refactoring tests

I'm loathe to be a bottleneck so I'm going to let you run with this. :-)


where to donwload AT Firmware 2.0 for ESP32 (but with included MQTT)

i downloaded ready AT Firmware for ESP32 v2.0 but there not included MQTT commands.
where i can download variant that include MQTT as part of AT Commands.
regards,
VALONI

@valoni The released AT firmware does not contain MQTT features.
user can use MQTT by compiling AT SDK, following by README.md

If you're not interested in compiling。You could provide me your module type, I will provide a AT fireware according your module, here.

i have an ESP32s module (ESP32-WROOM-32 [with default 4 Mb flash , 540 kb sram])
or exactly ESP32-DevKitC

Im interested too. Anyway consider release them with MQTT and BT, or create another releases where those are enabled by default. That would help for plenty of people, including me. Thanks.

@valoni Please download the bin from address 0x0, it will work on ESP32-WROOM-32.
target.zip

@valoni @kurta999 As the issues 284 said, https://github.com/espressif/esp-at/issues/284, We have a guidance about AT connect to AWS, but it is written in Chinese.
You also could take a look at AT commands
In fact, MQTT based on TLS depend on certificates, So it is recommended that you compile AT firmware according to README.md

Im interested too. Anyway consider release them with MQTT and BT, or create another releases where those are enabled by default. That would help for plenty of people, including me. Thanks.

I'm too

@valoni @kurta999 As the issues 284 said, #284, We have a guidance about AT connect to AWS, but it is written in Chinese.
You also could take a look at AT commands
In fact, MQTT based on TLS depend on certificates, So it is recommended that you compile AT firmware according to README.md

can i use MQTT Based on TLS with this bin file that you provided to me

@valoni @kurta999 As the issues 284 said, #284, We have a guidance about AT connect to AWS, but it is written in Chinese.
You also could take a look at AT commands
In fact, MQTT based on TLS depend on certificates, So it is recommended that you compile AT firmware according to README.md

@ustccw thank you for compile bin file
butt can i use MQTT Based on TLS with this bin file that you provided to us

If there is no a certificates auth, it can works on TLS, otherwise, user has to compile the AT firmware.

now i was able to compile via ubuntu 1806 ova (with vmware) ,
thanks a lot for help .


Create website header

should reference pic in #design channel
header should disappear when scrolling down, reappear scrolling up (see Hack the North website)
should have banner for logo on left, links on right
one prominent link on right highlighted
styling not required

Pretty much completed - all styling looks to be ok on all device sizes and types, but the only thing keeping me from moving it to Bug Fixes is that the right side of the header is empty on mobile. Need to figure out what to put there if we don't yet have an 'Apply' button.

Issue resolved - placed a 'Contact' button there for now that will direct users to contact<EMAIL_ADDRESS>although this resulted in the spacing for the tablet view being too crowded so I had to remove the links on tablet and place them in the bottom menu.


Get label images for evaluation

Hi Fisher
Thanks for that great repository! Could you still tell me, how to convert the color images to label images, where each pixel has an ID that represents the ground truth label? Is there already a script? Thanks in advance!
Best
Timo

Which dataset are you talking about?

I am talking about cityscapes dataset.

The CityScapes team provides scripts that can parse the label images and convert the labels: https://github.com/mcordts/cityscapesScripts

What is the best way to convert the CamVid dataset output to single channel results (same issue, different dataset)?


add @NotNull and @Nullable annotations

in a lot of places it gets extremely confusing whether the variable you're working with can be null or not. adding annotations like these would remove a lot of mental workload trying to figure out if something can ever be null

resolved with #81


Stuck installing cobol-plus-pack

VSCode Version: 1.45.1
OS Version: Windows 10

Steps to Reproduce:

Have cobol-plus-pack in your Sync Settings:

  {
    "metadata": {
      "id": "c9307bf1-5817-4295-a866-501e9e21b2f0",
      "publisherId": "bitlang.cobol-plus-pack",
      "publisherDisplayName": "bitlang"
    },
    "name": "cobol-plus-pack",
    "publisher": "bitlang",
    "version": "1.0.5"
  }

As long as this block is there, then Sync Settings tries indefinitely to install this extension. Worse, the extension doesn't show up in the VSCode plugin list. It's hidden. You have to manually cut it out of the Sync Settings data to work around.

Does this issue occur when all extensions are disabled?: No

Seems you are using Settings Sync extension for this, so please file an issue against https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync
FYI VS Code supports sync out of the box which is a preview feature and is available only in insiders - https://code.visualstudio.com/docs/editor/settings-sync


[Bug]: Puppeteer doesn't capture some OOPIF requests (Flaky)

Bug description
The following script will exit 1 if there were some missing Network.requestWillBeSent events:
https://gist.github.com/adamraine/e9ae2e811bde239db24a47535008e228
On my computer the script exits 1 most of the time. Other machines have a hard time reproducing the described result. I have reproduced it on a Linux cloudtop as well.
The script needs waitForDebuggerOnStart: true so it has time to enable network instrumentation before the OOPIF starts loading. The problem is that setting waitForDebuggerOnStart: true in this script doesn't affect anything because puppeteer sets waitForDebuggerOnStart: false (See log)
@paulirish and I developed a "fix" that prevents this script from exiting 1, but unsure how it would affect the rest of puppeteer. It's also possible that this "fix" just makes the script fail less often:
https://github.com/puppeteer/puppeteer/compare/main...adamraine:wait-for-debugger-on-attach
Puppeteer version
14.3.0
Node.js version
14.18.2
npm version
8.4.0
What operating system are you seeing the problem on?
macOS
Relevant log output
https://gist.github.com/adamraine/5b06ee25b09c815dee73962255c76dc1

I think this is essentially the same as https://github.com/puppeteer/puppeteer/issues/7990 Coincidentally I started working on refactoring Puppeteer yesterday. One problem is that Firefox does not seem to support waitForDebuggerOnStart so a backward compatible solution is needed. Also, it's a bigger refactoring since setting waitForDebuggerOnStart in existing places would not ensure that the target configuration is race-free as far as I can tell.


re-export Data.Monoid.<> when available

I don't think many programs break if <> changes from Doc -> Doc -> Doc to Monoid m => m -> m -> m, since everything else in the library has type Doc. The fixity is the same between the two versions.
This change will save people from having to write hiding ((<>))

please migrate to https://github.com/ekmett/ansi-wl-pprint/issues


DOC: Contact us

What's wrong with the existing documentation
the doc is not inlined
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

please add Gssoc and respective level label by assigning me

Please assign this issue to me


FixtureConfiguration: Allow a mix of given events and commands

I have a test case where I need to be able to have one given event followed by one given command.
I thought of the following semantic:
fixture.given(event1)
          .and()
          .givenCommands(command1)
          .when(command2)
          .expectSuccessfulHandlerExecution()

Would it be ok?

Looks good. I suppose the and() would allow different types of chaining?
You can also include the and in the method name:
given(events)
.andGivenCommands(cmd)
.andGiven(events)
.when(......)

Looks good. I suppose the and() would allow different types of chaining?
You can also include the and in the method name:
given(events)
.andGivenCommands(cmd)
.andGiven(events)
.when(......)

Yes it is also an option, but it would require to add all of these and prefixed method to the TestExecutor.
Having an and() method requires only the executor to return the stored FixtureConfiguration.

Yes it is also an option, but it would require to add all of these and prefixed method to the TestExecutor.
Having an and() method requires only the executor to return the stored FixtureConfiguration.


GUVNOR-2582 : Verification & Validation: Document range checks and single hit [fixes]

@manstis Would you mind reviewing and possibly also merging?
Thanks.

+1 to merge (but will wait for Jenkins...)


Run acceptance tests on Debian 8

Looks like it fails on the redis service

Looks like it fails on the redis service

Fixed


test: Try pinning a lower version in go.mod

Fixes #N/A
Description
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.05%) to 77.915%

Files with Coverage Reduction
New Missed Lines
%

pkg/scheduling/requirements.go
2
97.98%

pkg/controllers/disruption/expiration.go
2
89.66%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
8266

Relevant Lines:
10609

💛  - Coveralls

Closing since this was just to validate that this works with our vulnchecks.


When "onClick" to close the menu is inserted, the menu does not scroll properly.

Hi. I want to scroll to the id.
When it is at the top of the page, it works correctly, but if it is in the middle of the page or press the same link twice, it jumps to the top of the page.
Removing the onClick event will do the expected scrolling.
import { Link as Scroll } from 'react-scroll'; .... <Scroll onClick={() => setOpen(false)} smooth={true} to={item.to} duration={600} offset={-30}>{item.name}</Scroll>

Do you a have a codepen/plunkr to demonstrate the issue?


Organ text and modal overlap in android/iphone

When an organ is clicked and the heading are expanded > The name of the left corner overlaps the grey window having the details about the organ.

I have resolved this issue.

This issue is resolved.


Host: Improve the visibility of tags filter in dark mode

Tags filter text is not visible in dark mode

Hello :) @sadanandpai
I was going through this website and saw this issue, would love to contribute to this,
please assign this to me.

@replyre The selection is not clear. I mean which one is selected is not visible due to bad UX. can we also improve that by giving a color to the selected filter option.

hello @sadanandpai, I have used the theme colors to improve visibility. If you want, I can make it a lighter color.
Or if you are talking about some other filter, please share a screenshot.

@replyre setting the selected one with blue color and text in white would be clear I feel

okay I will do it.


[DUOS-443][risk=no] Part 2 of updating vulnerable researcher APIs

Addresses
https://broadinstitute.atlassian.net/browse/DUOS-443
This PR only addresses the PUT call in ResearcherResource. Other vulnerable endpoints will be addressed in follow-on PRs.
UI PR also required: https://github.com/DataBiosphere/duos-ui/pull/226
See also, these related PRs:

https://github.com/DataBiosphere/consent/pull/397
https://github.com/DataBiosphere/duos-ui/pull/225

Changes

Use AuthUser instead of using a url parameter to determine the ID of the user to update properties for. The previous approach allowed for any researcher user to update a different researcher user's properties.
Updated the resource so any user role can update their own profile.
Changing the interface to use AuthUser required some additional minor changes to the NIH service as well.

Coverage increased (+0.4%) to 59.436% when pulling 2d4a623aa4d9f1cda798cf6ed4c0be844be11b9a on DUOS-443_part_2 into e10e2be8b44cca3d1cf63c975a0e86bffbab1e82 on DUOS-443_part_1.


Improve documentation

The documentation could be improved by:

Reviewing the language e clearness
Adding live examples (maybe links to codesandbox)

For instance, I just realized the explanation of the shouldDraw parameter of the addLayer method is not very clear. What it does is running a draw cycle in the engine once the layer's promise is resolved.


How to make screenshot? [No API docs on that]

Please send some time searching the code. https://github.com/amir20/phantomjs-node/search?utf8=✓&q=render
All the methods mirror phantomjs so there is no point to duplicate every single API page.


Engine: propagate trait generics arguments

~This PR requires #698.~
This PR propagates trait generics arguments throughout the engine.
On the F* output:

now the calls to methods will always be method #self_type #trait_generic_arg1 ... #trait_generic_argN #Typeclasses.solve #method_generic_type1 ... #method_generic_typeM method_generic_const1 ... method_generic_constI meth_arg1 ... meth_argJ
traits and inductive (enums/structs) should have all their argument explicit

Todo:

[x] use the information in the F* backend
[x] propagate the information in the proof libs

When undrafted, this PR should fix #719

I think this should work, maybe there are a few things in the library we need to fix, but we will discover those by running hax on various things.
@mamonet can you try this branch on ml-kem?
If you run in anything suspicious related to implcits or something similar, tell me directly!

@W95Psp this doesn't build with the same issue as in the visitor PR
# File "utils/generate_visitors/errors.ml", line 27, characters 29-35:
# 27 |     | UnsupportedCoreType of string
#                                   ^^^^^^

Ah, yes, thanks @franziskuskiefer, will rebase this PR with generate-visitors to propagate that change

This PR seems to be solving the issue. I went through the instances that I'm aware of, and all of them verified successfully. However, I got one undesired change here https://github.com/cryspen/libcrux/blob/dev_ml_kem_lax/libcrux-ml-kem/proofs/fstar/extraction/Libcrux_ml_kem.Polynomial.fsti#L35-L37
This create an error Expected type Type   but t_PolynomialRingElement v_Vector   has type i1: Vector.Traits.t_Operations v_Vector -> Type0 in references of t_PolynomialRingElement
Here is the original type https://github.com/cryspen/libcrux/blob/main/libcrux-ml-kem/proofs/fstar/extraction/Libcrux_ml_kem.Polynomial.fsti#L35-L37

Fantastic!
Thanks for your feedback! I see what it is, give me 10-15 minutes I will push a fix!

@mamonet, I pushed a commit, can you tell me if that's fixing that regression? :smiley:

Of course, just 2 minutes to report back

The fix gets t_PolynomialRingElement back to what it is, I think this PR is a good shape now.

Ah, that's great news!
I'm gonna rebase the PR to main, and then we can merge it! :partying_face:


Hough transform fails to detect lines under certain angles

I noticed that when a line points under a certain range of angles (between 90° and 135° when measured from the top of the x-axis), the imageproc's implementation of the Hough transform won't detect it.
To give an example, consider those two images:

The first one should result in the almost exact same set of lines as the second one, just with negated angles. Interestingly, that's not the case. Those are my results:

Code:
extern crate imageproc;
extern crate image;

fn main() {
    let args: Vec<String> = std::env::args().collect();
    assert_eq!(args.len(), 2, "Usage: <progname> <edges image>");

    let edges = match image::open(&args[1]).unwrap() {
        image::DynamicImage::ImageRgb8(img) => img,
        _ => panic!("Passed file should be RGB")
    };

    let grayscale = image::GrayImage::from_fn(edges.width(), edges.height(), |x, y| {
        let px = edges.get_pixel(x, y);
        let r = px.data[0] as f64;
        let g = px.data[1] as f64;
        let b = px.data[2] as f64;

        image::Luma{ data: [(0.299 * r*r + 0.587 * g*g + 0.114 * b*b).sqrt() as u8] }
    });

    let vote_threshold = 180;
    let lines = imageproc::hough::detect_lines(&grayscale, imageproc::hough::LineDetectionOptions {
        vote_threshold,
        suppression_radius: 0
    });

    imageproc::hough::draw_polar_lines(
        &edges,
        &lines,
        image::Rgb {
            data: [255, 0, 255]
        }
    ).save("res.png").unwrap();
}

I've looked into the implementation of detect_lines and managed to get it to work:
/// Detects lines in a binary input image using the Hough transform.
///
/// Points are considered to be in the foreground (and thus vote for lines)
/// if their intensity is non-zero.
///
/// See ./examples/hough.rs for example usage.
pub fn detect_lines(image: &GrayImage, options: LineDetectionOptions) -> Vec<PolarLine> {
    let (width, height) = image.dimensions();

    // The maximum possible radius is the diagonal of the image.
    let rmax = ((width * width + height * height) as f64).sqrt() as i32;

    // Measure angles in degrees, and use bins of width 1 pixel and height 1 degree.
    let mut acc: ImageBuffer<Luma<u32>, Vec<u32>> = ImageBuffer::new(rmax as u32, 360u32);

    let cos_lut: Vec<f32> = (0..360u32).map(|m| degrees_to_radians(m).cos()).collect();
    let sin_lut: Vec<f32> = (0..360u32).map(|m| degrees_to_radians(m).sin()).collect();

    for y in 0..height {
        for x in 0..width {
            let p = unsafe { image.unsafe_get_pixel(x, y)[0] };

            if p > 0 {
                for m in 0..360u32 {
                    let fy = y as f32;
                    let fx = x as f32;

                    let r = unsafe {
                        (fx * *cos_lut.get_unchecked(m as usize) +
                             fy * *sin_lut.get_unchecked(m as usize)) as i32
                    };

                    if r < rmax && r >= 0 {
                        unsafe {
                            let vote_incr = acc.unsafe_get_pixel(r as u32, m)[0] + 1;
                            acc.unsafe_put_pixel(r as u32, m, Luma([vote_incr]));
                        }
                    }
                }
            }
        }
    }

    let acc_sup = suppress_non_maximum(&acc, options.suppression_radius);

    let mut lines = Vec::new();

    for m in 0..acc_sup.height() {
        for r in 0..acc_sup.width() {
            let votes = unsafe { acc_sup.unsafe_get_pixel(r, m)[0] };
            if votes >= options.vote_threshold {
                let line = PolarLine {
                    r: r as f32,
                    angle_in_degrees: m,
                };
                lines.push(line);
            }
        }
    }

    lines
}

The only thing I did was to replace every occurrence of 180 with 360.
It's likely a suboptimal solution (completely outside of my area of expertise, so I don't really know), but I guess it might help a little.

You are right, looks broken and I might have spotted where in the code:
https://github.com/PistonDevelopers/imageproc/blob/master/src/hough.rs#L59-L62
Here we calculate the displacement-to-line by the dot product of the point and the line normal. However, that might be negative. In fact, only half of all lines (in a 90° angle) will have positive displacements for all image pixels.
Hence, the comparison should take into account the other possibility in sign:
https://github.com/PistonDevelopers/imageproc/blob/b8296fc3a3f77bf76ded4de7a0fbe42a2969cd09/src/hough.rs#L64
Probably, the temporary hough transformed image should extend from -rmax to rmax in the x direction. The problem with the immediate fix by just extending to 360° is that non-maximum suppression doesn't work properly for the same line with inverted normal.
Additional critique of the code: Why so many unsafes? Replace for m in 0..180u32 with for (m, clut, slut) in cos_lut.iter().zip(sin_lut.iter()).enumerate() for example. And all of the multiplications on integers need to occur instead after casting to floating values, else overflows can potentially ruin your day. And then suddenly the unsafe at https://github.com/PistonDevelopers/imageproc/blob/b8296fc3a3f77bf76ded4de7a0fbe42a2969cd09/src/hough.rs#L66 actually leads to corruption.

cc @theotherphil

Thanks. I've made some changes in to address this, but I'll not merge until I've done a bit more cleaning up and testing.

@kamirr I've just published 0.17 with a fix. Please try it and confirm (or deny!) that this has fixed the problem.

Everything's ok, my program works flawlessly after the update.


Group application workflow

Not intended to be merged.

Good job - I think you've thought everything through. :+1: to implement.

Implemented in #871.

@chrismedrela close if possible


Cranelift: load.f32x2 unimplemented on x86_64

Thanks for filing an issue! Please fill out the TODOs below.
.clif Test Case
function u0:0(f32x2) -> f32x2 system_v {
    ss0 = explicit_slot 16
    ss1 = explicit_slot 16
    sig0 = (f32) -> f32 system_v
    fn0 = u0:1 sig0 ; "cosf"

block0(v0: f32x2):
    stack_store v0, ss1

; _0 = simd_fcos::<f32x2>(move _1)
    v1 = stack_load.f32 ss1
    v2 = call fn0(v1) ; lib_call cosf
    stack_store v2, ss0
    v3 = stack_load.f32 ss1+4
    v4 = call fn0(v3) ; lib_call cosf
    stack_store v4, ss0+4

    v5 = stack_load.f32x2 ss0
    return v5
}

Steps to Reproduce

Compile on x86_64

Expected Results
Compiles
Actual Results
thread '<unnamed>' panicked at /home/bjorn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cranelift-codegen-0.105.2/src/machinst/lower.rs:766:21:
should be implemented in ISLE: inst = `v5 = load.f32x2 notrap v11`, type = `Some(types::F32X2)`
stack backtrace:
   0: rust_begin_unwind
             at /rustc/46b180ec2452d388c5d9c14009442e2e0beb01d7/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_fmt
             at /rustc/46b180ec2452d388c5d9c14009442e2e0beb01d7/library/core/src/panicking.rs:72:14
   2: cranelift_codegen::machinst::compile::compile
   3: <cranelift_codegen::isa::x64::X64Backend as cranelift_codegen::isa::TargetIsa>::compile_function
   4: cranelift_codegen::context::Context::compile_stencil
   5: cranelift_codegen::context::Context::compile_and_emit
   6: <cranelift_object::backend::ObjectModule as cranelift_module::module::Module>::define_function_with_control_plane
   7: cranelift_module::module::Module::define_function
   8: rustc_codegen_cranelift::base::compile_fn

Versions and Environment
Cranelift version or commit: Cranelift 1.105.2
Operating system: N/A
Architecture: x86_64
Extra Info
Anything else you'd like to add?

I haven't checked if store.f32x2 works. load.f32x2 does work on AArch64.

Thanks for reporting! I suspect you'll find a bunch more holes with "narrow SIMD" (64-bit vectors) on x86 -- this mostly exists only on aarch64 for now. As with other missing implementations, we'd be happy to take a PR from anyone and this could make a decent starter issue.


Fix flaky tests

The HTTPS get needs to be a part of the promise chain. Otherwise
it may not happen until we're executing another test, at which
point the cell would not be in the correct state and jasmine would
print out an error for the unrelated test.

Thanks guys


Jobs don't run message transformers

Contact Details
No response
Version
8.x (develop, pre-release), 8.x
On which operating system(s) are you experiencing the issue?
Windows
Using which broker(s) did you encounter the issue?
RabbitMQ, In-Memory
What are the steps required to reproduce the issue?
using MassTransit;
using MassTransit.MessageData;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using System;
using System.Reflection;
using System.Threading;
using System.Threading.Tasks;

namespace ThreeDSpaces.WorkerTest
{
    public class Program
    {
        public static async Task Main(string[] args)
        {
            await CreateHostBuilder(args).Build().RunAsync();
        }

        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureServices((hostContext, services) =>
                {
                    services.AddHostedService<Worker>();

                    services.AddMassTransit(x =>
                    {
                        x.SetKebabCaseEndpointNameFormatter();
                        x.AddDelayedMessageScheduler();

                        // By default, sagas are in-memory, but should be changed to a durable
                        // saga repository.
                        x.SetInMemorySagaRepositoryProvider();
                        x.SetJobConsumerOptions();
                        x.AddJobSagaStateMachines(options => options.FinalizeCompleted = false);

                        var entryAssembly = Assembly.GetEntryAssembly();

                        x.AddConsumers(entryAssembly);
                        x.AddSagaStateMachines(entryAssembly);
                        x.AddSagas(entryAssembly);
                        x.AddActivities(entryAssembly);

                        x.UsingInMemory((context, cfg) =>
                        {
                            cfg.ConfigureEndpoints(context);
                            cfg.UseDelayedMessageScheduler();
                            cfg.UseMessageData(new InMemoryMessageDataRepository());
                        });

                        MessageDataDefaults.Threshold = 1;

                    });
                });
    }

    public record TestMessage
    {
        public MessageData<string> TestData { get; init; }
    }

    public class TestConsumer : IConsumer<TestMessage>
    {
        public async Task Consume(ConsumeContext<TestMessage> context)
        {
            Console.WriteLine(await context.Message.TestData.Value);
        }
    }

    public class TestJob : IJobConsumer<TestMessage>
    {
        public async Task Run(JobContext<TestMessage> context)
        {
            Console.WriteLine(await context.Job.TestData.Value);
        }
    }

    public class Worker : BackgroundService
    {
        readonly IServiceScopeFactory _scopeFactory;

        public Worker(IServiceScopeFactory scopeFactory)
        {
            _scopeFactory = scopeFactory;
        }

        protected override async Task ExecuteAsync(CancellationToken stoppingToken)
        {
            await using var scope = _scopeFactory.CreateAsyncScope();
            var publishEndpoint = scope.ServiceProvider.GetRequiredService<IPublishEndpoint>();
            await publishEndpoint.Publish<TestMessage>(new
            {
                TestData = "Hello World"
            });
            //_hostApplicationLifetime.StopApplication();
        }
    }
}

What is the expected behavior?
Both TestConsumer and TestJob should output Hello World
What actually happened?
TestJob throws an error, TestConsumer outputs Hello World
Related log output, including any exceptions
info: MassTransit[0]
      Configured endpoint test, Consumer: Test.TestConsumer
info: MassTransit[0]
      Configured endpoint test-job, Consumer: Test.TestJob
info: MassTransit[0]
      Configured endpoint job-type, Saga: MassTransit.JobTypeSaga, State Machine: MassTransit.JobTypeStateMachine
info: MassTransit[0]
      Configured endpoint job, Saga: MassTransit.JobSaga, State Machine: MassTransit.JobStateMachine
info: MassTransit[0]
      Configured endpoint job-attempt, Saga: MassTransit.JobAttemptSaga, State Machine: MassTransit.JobAttemptStateMachine
info: MassTransit[0]
      Job Service started: loopback://localhost/instance-6dcyyyn7yrybmbyzbdp4ifq4gb
info: MassTransit[0]
      Bus started: loopback://localhost/
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: C:\Test
Hello World
fail: MassTransit.ReceiveTransport[0]
      R-FAULT loopback://localhost/test-job f0d80000-5d01-0015-70a2-08dbaa95dfe7 Test.TestMessage Test.TestJob(00:00:00.4031921)
      MassTransit.ExceptionInfoException: The message data was not loaded: urn:file:none:1sipsnbe51zf4yyimwy9bsyyyy
         at MassTransit.MessageData.Values.DeserializedMessageData`1.get_Value() in /_/src/MassTransit/MessageData/Values/DeserializedMessageData.cs:line 33
         at Test.TestJob.Run(JobContext`1 context) in C:\Test\Program.cs:line 75
         at MassTransit.Middleware.JobConsumerMessageFilter`2.RunJob(PipeContext context, IJobConsumer`1 jobConsumer) in /_/src/MassTransit/Middleware/JobConsumerMessageFilter.cs:line 51

Link to repository that demonstrates/reproduces the issue
No response

Since job consumers are not consumed, this might not be an easy fix. I personally don't have time to work on it in the near future.

Is there a work-around I can use in the mean time?
Maybe a way to trigger the message initialization process manually?

Eventually I may address this, but it isn't on any near-term radar, closing.


TypeError: 'in ' requires string as left operand, not tuple

This issue is probably related to #47 and #50 but mine can be consistently reproduced.
Steps to Reproduce the Exception

Create a new file ~/file.css
Make sure ~/.stylelintrc doesn't exists
Copy and paste code from "Code Snippet To Reproduce The Bug"
Wait until SublimeLinter-stylelint flags the errors
Delete the entire content of the file Cmd + A -> Delete
The exception panel automatically appears

Code Snippet To Reproduce The Bug
html,body,div,span,h1,h2,h3,h4,h5,h6,p,blockquote,pre,a,code,em,img,strong,tt,b,u,i,dl,dt,dd,ol,ul,li,table,tbody,tfoot,thead,tr,th,td {
    margin:0;
    padding:0;
    border:0
    font-size: 100%;
    font: inherit;
}

Errors Generated By The Linter
file.css:
1:1  error  stylelint: Error  Stylelint crashed: No configuration provided for /file.css

Full Copy of the Exception
SublimeLinter: #51468 stylelint github.css ERROR:

 Linter crashed.

Traceback (most recent call last):
  File "/SublimeLinter/lint/backend.py", line 97, in execute_lint_task
    errors = linter.lint(code, view_has_changed, settings) or []
  File "/SublimeLinter/lint/linter.py", line 797, in lint
    output = self.run(cmd, code)
  File "/SublimeLinter/lint/linter.py", line 1139, in run
    return self.communicate(cmd, code)
  File "/SublimeLinter-stylelint/linter.py", line 111, in communicate
    if fileext and not fileext[1:] in self.syntax:
TypeError: 'in <string>' requires string as left operand, not tuple

Same with my issues.

@cixtor
I had the EXACT same problem.  I went back to the README and noticed that my package.json did not include postcss allthough the readme said to inlcude.
After installing in my project npm install postcss or yarn add postcss It worked again.  I really hope this helps for you too!

Thank you @rfearing I don't do JavaScript development but your solution will surely help other people.
I wanted to report this issue more as a way to warn the maintainer that there is an edge case in the code that is not being taken care of, and instead is forcing the linter to miserably crash without any hint to the user. These non-handled exceptions should be gracefully handled to offer recovery during the analysis of the code.


Graphic with incorrect service name capitalization

Minor issue, the image from this link has Twinmaker and Sitewise instead of TwinMaker / SiteWise.

Thanks for raising this, we've updated the image with this PR: https://github.com/aws-samples/aws-iot-twinmaker-samples/pull/47


Create polymorphism.md file which contain polymorphism in document form

Description 📜
In this file i deeply explained the topic polymorphism with good code snippets and with point to point explanation , i also explained the types polymorphism and explained that in simple English language.
Issue no. closed :- #835

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Pranshu321  In this PR itself , update readme... Not a separate one

@Pranshu321 In this PR itself , update readme... Not a separate one

Sir I only update the polymorphism.md file not make another pull request.

@Pranshu321 In this PR itself , update readme... Not a separate one

Sir can u merge this file, it is correct now and also update the readme file.

@gunjan-g This is the Original one...
@Pranshu321  No readme has not been updated... Update in THIS Pr's branch

@Pranshu321 No, readme has not been updated... Update in THIS Pr's branch... No separate PR

Sir now i add the readme file updation commit with this PR only now you can merge this branch

@Pranshu321 Do you even look at the directory structure like ever?
Next time seh correct folder choose karna ... i fixed merge conflicts & path for you...
Observe the changes & carry them out next time...
Awesome work on the content though :octocat: :heart:


Micro-interaction of favorite does not work when navigationBar is Rail instead of Bottom

Overview
Please close if this is what you intended 🙇
I think it would be better to have animation even for Rail's NavigationBar.

Bottom
Rail

I'll try it :raised_back_of_hand:

Thanks! Assigned 👍


Twigstats install issues in a conda environment with admixtools2 as well

Dear Leo
I am trying to install admixtools2 and twigstats in the same conda environment with R4.1.3
I have first installed admixtools2 and when installing twigstats, I encountered the following problems
Problem 1
library(remotes)
install_github("leospeidel/twigstats")
This github channel does not respond in this way, but remotes::install_github is functional since  it was working for admixtools2
Is there a transient issue with this github procedure
Problem2
I could have this procedure working
install.packages('twigstats', repos = c('https://leospeidel.r-universe.dev', 'https://cloud.r-project.org'))
but compilation failed at the following steps. Any idea of the solution to this issue?
Thanks
Thierry Grange
x86_64-conda-linux-gnu-c++ -std=gnu++14 -I"/home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/include" -DNDEBUG -I/usr/include -I'/home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/testthat/include' -I'/home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/Rcpp/include' -I'/home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/RcppArmadillo/include' -DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /home/paleogenomique/miniconda3/envs/admix2twigstat/include -I/home/paleogenomique/miniconda3/envs/admix2twigstat/include -Wl,-rpath-link,/home/paleogenomique/miniconda3/envs/admix2twigstat/lib   -fpic  -fvisibility-inlines-hidden -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /home/paleogenomique/miniconda3/envs/admix2twigstat/include -fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/r-base-split_1694680471204/work=/usr/local/src/conda/r-base-4.1.3 -fdebug-prefix-map=/home/paleogenomique/miniconda3/envs/admix2twigstat=/usr/local/src/conda-prefix  -c RcppExports.cpp -o RcppExports.o
In file included from /usr/include/features.h:392,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/gcc/x86_64-conda-linux-gnu/14.2.0/include/c++/x86_64-conda-linux-gnu/bits/os_defines.h:39,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/gcc/x86_64-conda-linux-gnu/14.2.0/include/c++/x86_64-conda-linux-gnu/bits/c++config.h:680,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/gcc/x86_64-conda-linux-gnu/14.2.0/include/c++/bits/requires_hosted.h:31,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/gcc/x86_64-conda-linux-gnu/14.2.0/include/c++/cmath:41,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/Rcpp/include/Rcpp/platform/compiler.h:103,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/Rcpp/include/Rcpp/r/headers.h:62,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/Rcpp/include/RcppCommon.h:30,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/RcppArmadillo/include/RcppArmadillo/interface/RcppArmadilloForward.h:25,
from /home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/library/RcppArmadillo/include/RcppArmadillo.h:29,
from RcppExports.cpp:4:
/usr/include/features-time64.h:21:10: fatal error: bits/timesize.h: No such file or directory
21 | #include <bits/timesize.h>
|          ^~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [/home/paleogenomique/miniconda3/envs/admix2twigstat/lib/R/etc/Makeconf:177: RcppExports.o] Error 1
ERROR: compilation failed for package ‘twigstats’

Dear Thierry,
Thank you for raising this issue and sorry for the delayed reply - was moving country the past month or so!
I was able to replicate this (I think), and noticed that I had a Makevars file under src (not sure when this crept in) that meant the conda and system paths got mixed up leading to the error. Deleted the file and it now installs fine using conda for me.
And it works for me using both

remotes and install_github("leospeidel/twigstats")
install.packages('twigstats', repos = c('https://leospeidel.r-universe.dev/', 'https://cloud.r-project.org/'))

Hope this fixes it, please let me know if problems persist!


Postgres end-to-end tests - Fix VulnScanWithGraphQLTest GraphQL queries

Description
With the re-design of the dackbox graph for the postgres migration, some graphQL queries in the end-to-end tests need to be adapted.
Here, the focus is on the VulnScanWithGraphQLTest.groovy test file.
In order to make debugging easier, additional logs were added to the GraphQL service, and a minor framework adjustment was also introduced (add a function to tell whether the current run is a Postgres run or not).
Checklist

[ ] Investigated and inspected CI test results
- [ ] Unit test and regression tests added
- [ ] Evaluated and added CHANGELOG entry if required
- [ ] Determined and documented upgrade steps
- [ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Test code fixes, CI run should be sufficient.

/test all

/test ui-unit-tests


Please update to version 1.20.1

Do you know of any open source 1.20 compatible mods that add a custom world type to the create world screen?  They have changed the way it works and I'm having trouble working out how to do it.  An example would help a lot.

Do you know of any open source 1.20 compatible mods that add a custom world type to the create world screen? They have changed the way it works and I'm having trouble working out how to do it. An example would help a lot.

OK, I will pay attention on it, if I have any news, how should I inform you as soon as possible. How can I contact you? Just on GitHub or other way?

It's all good, I've found one.  I've had to completely rework the way it detects the world type.  I should have a 1.20.1 version out in 3 or 4 days time.  There is still some work to be done with the bedrock structures as they aren't spawning when using next_bedrock.

It's all good, I've found one. I've had to completely rework the way it detects the world type. I should have a 1.20.1 version out in 3 or 4 days time. There is still some work to be done with the bedrock structures as they aren't spawning when using next_bedrock.

Amazing! Congratulations on this discovery. I will expect it

How can I use this mod in a muliplayer server? I need to crack seed in a server.

This mod finds seeds for a new world.  It doesn't crack seeds of existing worlds/servers.  Thats reverse seed finding or seed cracking.

Hum...do you know of any way to crack the seed? I really need it.

It's not what I do.  If the server owner doesn't want to give you the seed, its probably because they don't people having an unfair advantage over others.

It's not about gaining an advantage over other players. The server owner is me, I just want to test any way to cheat and try to banned.

If you are the server owner then just type /seed and it will give you the seed.

I know it, I mean is I put myself in the role of an ordinary player. I am testing how ordinary players get seeds by cheating. I want to prevent this behavior, such as changing seeds regularly and deleting chunks.

Thank you so much

If you want to prevent people from cheating by reversing the seed, see if you can find a mod that changes all the salt/hash values for the structures and ores.  Then even if they manage to get the seed nothing will be where chunk base says it is.

If you want to prevent people from cheating by reversing the seed, see if you can find a mod that changes all the salt/hash values for the structures and ores. Then even if they manage to get the seed nothing will be where chunk base says it is.

Very thank you! I will try it right now!


Bind ocelot to TAG instead of HEAD of omega branch

We are about to do some huge work on ocelot, this means that if this projectify keeps up with a branch it will use the incomplete work we commit on that branch.
Can you bind the clone of the repo to a tag instead of the HEAD of the omega branch.
This is the tag:
https://github.com/Crosscheck/Ocelot/releases/tag/v.0.1.3.om

Hey Robbie,
I think Klaas has closed this issue with a pull request on 19-06. He parses the latest release information from Github, and then reads out the "latest_tag". This most likely contains something "v0.1.3.nd" where "nd" gets stripped / replaced by "om". These ensures we are using the Omega Branch of Ocelot.
The rest is OK.

Is this issue still actual?

No, can be closed


ttnn.cos_bw operation fails with low PCC on Grayskull

ttnn.cos_bw operation fails with low PCC on Grayskull. On WH operation works fine.
Steps to reproduce
You can reproduce this error with sweep test tests/sweep_framework/sweeps/eltwise/unary_backward/cos_bw.py. To run:
python3 tests/sweep_framework/runner.py --elastic cloud --module-name eltwise.unary_backward.cos_bw

Results can be found on elastic cloud as explained here: https://github.com/tenstorrent/tt-metal/tree/main/tests/sweep_framework

@nemanjagrujic , I'm closing this issue as I understand we will be focusing all efforts going forward on WH and BH work.


standalone/intellisense

Re #10152
The intellisense includes glue/integration code for hooking up lsp and jupyter server auto complete. I found that the component is well isolated and no one else depends on it thus I moved this into standalone.
The PR proves that the layering is correct, no files in platform/notebooks/kernels/interactive-window/webviews are modified after moving intellisense folder.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for feature-requests.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

I'm not sure about this change. All of the root level things could go under standalone? We could move kernels there too. I thought the high level directories where the high level components? Maybe I'm arguing for removing the 'standalone' folder then. As every subdirectory under there could be a root level folder.

Codecov Report

Merging #10550 (e5ee1f1) into main (923275a) will decrease coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #10550   +/-   ##
======================================
- Coverage     71%      71%   -1%
======================================
  Files        472      472
  Lines      27987    27987
  Branches    4689     4689
======================================
- Hits       19959    19920   -39
- Misses      6168     6190   +22
- Partials    1860     1877   +17

Impacted Files
Coverage Δ

src/extension.node.ts
76% <ø> (-1%)
:arrow_down:

src/standalone/intellisense/conversion.ts
100% <ø> (ø)

src/standalone/intellisense/diagnosticsProvider.ts
82% <100%> (ø)

...intellisense/fileBasedCancellationStrategy.node.ts
70% <100%> (ø)

...andalone/intellisense/intellisenseProvider.node.ts
83% <100%> (ø)

src/standalone/intellisense/languageServer.node.ts
64% <100%> (ø)

...c/standalone/intellisense/logReplayService.node.ts
10% <100%> (ø)

...one/intellisense/notebookPythonPathService.node.ts
45% <100%> (ø)

...one/intellisense/pythonKernelCompletionProvider.ts
77% <100%> (ø)

...ense/pythonKernelCompletionProviderRegistration.ts
89% <100%> (ø)

... and 18 more

I'm not sure about this change. All of the root level things could go under standalone? We could move kernels there too. I thought the high level directories where the high level components

@rchiodo if we try to move kernels into standalone, then notebooks and interactive-window would depend on standalone, and at the same time, standalone depends on notebooks, which is a circular dependency. While where we move intellisense wouldn't introduce any layer dependencies change.
If there is another component that depends on intellisense, then we should keep it as a top component. Currently it seems we don't have any, this the major difference between intellisense with the rest of the top components and it's the Yes/No question I will ask myself where to contribute a new component. Does this make sense to you?

I'm with Rich on this, personally don't see much value for standalone anymore.
Feels rather unnecessary to move yet again into another standalone directory, when these components are already in their own root level directories.

So you're saying standalone components can't depend upon each other. That's what makes them different? So Kernels isn't standalone because other standalone components depend upon it.
Sure that's fine. Maybe we can put that in an eslint rule too somehow.

I'm with Rich on this, personally don't see much value for standalone anymore.

@DonJayamanne I'm interested in alternatives from your perspective. if we don't have a standalone, what's the recommended approach for managing folder structures for features like api, export-command, etc.

ur perspective. if we don't have a standalone, what's the

Can we not have an eslint rule for these, feels better than moving folders up a level.

Can we not have an eslint rule for these

what eslint rule are you referring to here?

As we discussed in today's stand up, we would document the rules of where to contribute