Add dependency information about pure Android projects

As a colleague added the core dependency to our "pure Kotlin Android" project (the Kotlin Multiplatform plugin was not applied) and nothing happend, we thought it make sense to document it a bit better 🙃
The core dependency makes only sense in the common "target" in multiplatform projects.
I also fixed some grammatical stuff in the first section 🤓 .

Thanks for the pull request. Could you please explain what you mean by "nothing happend'?
I also use Reveal in an Android, non-multiplatform Project and it's working just fine with the reveal-core dependency.

For example I also use cache4k in the mentioned project and I didn't have to explicitly use the -android artifact. Can you please check if you're using the newest versions of Gradle, Kotlin and AGP and if you can still reproduce it then?

Hey,
Sure, I can explain what I mean by that 🙃.
Alright, the following night not be true, but this is how I understand kotlin multiplatform dependencies:
If you publish a KMP library, then all the defined targets gets the name of the target as classifier.
Together with that, a root publication will also be created. This is just an empty jar file. But the published module file has so called variants that points to the correct location for the given variant name. These will be resolved in case a gradle plugin request it.
Here is the module file I'm talking about for your root project:
https://repo1.maven.org/maven2/com/svenjacobs/reveal/reveal-core/3.0.0/reveal-core-3.0.0.module
If these assumptions are true, than it make sense that a non KMP project that requests your -core dependency (without any classifier) will "not work". As the requested jar file contains literally nothing. It is just there to fulfill the requirements of the maven repository.
This means, in case a non KMP project consumes the root project dependency, gradle resolves everything just fine and succeed "on sync". But you can't use any classes or anything from the project as the jar file doesn't contain anything...
Does this make sense? 🤔
On the other side, in case a KMP project consumes the root publication, then the KMP gradle plugin requests from gradle (build tool) the respective variants based on the defined targets and so gradle will download each dependency for the declared targets (with the correct classifiers).
Your mentioned library module file can be found here:
https://repo1.maven.org/maven2/io/github/reactivecircus/cache4k/cache4k/0.11.0/cache4k-0.11.0.module
(just for reference)
While roughly scanning your module file and the one from cache4k on my phone I can't find anything why it works with the cache4k but not with your library. Maybe I have to digg deeper into this when Iam back on a monitor.
To finally answer your question:
We are using always the latest and greatest 😉.
Kotlin 1.9.10
Gradle 8.3
It could be possible, that not only the KMP plugin can resolve those variants but also the Kotlin android plugin. That might be the reason why it works for you. Our project might be to complex as we have our own gradle plugin in our android libraries that afterward apply the Kotlin android plugin. Maybe the setup is not 100% correct so that this works out of the box.
Just another reference:
The docs about the publishing process of a KMP lib:
https://kotlinlang.org/docs/multiplatform-publish-lib.html#structure-of-publications

Hello Stefan,
thanks for your detailed answer.

If these assumptions are true, than it make sense that a non KMP project that requests your -core dependency (without any classifier) will "not work". As the requested jar file contains literally nothing. It is just there to fulfill the requirements of the maven repository. This means, in case a non KMP project consumes the root project dependency, gradle resolves everything just fine and succeed "on sync". But you can't use any classes or anything from the project as the jar file doesn't contain anything...

I understand your assumptions but they are not correct 😉 As I mentioned in a previous comment, I have a pure Android project where I can just use reveal-core. The mentioned cache4k dependency also works just fine.
The library module file that you mentioned contains references to all platform artifacts. The attributes describe the different platforms / targets and are either used by Gradle, the Kotlin Gradle plugin or the Android Gradle plugin to fetch the correct artifact for Android. That is my assumption 😉 but I don't really know which of these build "components" is actually responsible for it. I asked this on Slack but didn't get a definite answer.

Our project might be to complex as we have our own gradle plugin in our android libraries that afterward apply the Kotlin android plugin. Maybe the setup is not 100% correct so that this works out of the box.

Please understand that I don't want to add instructions to the README that are not necessary for 99% of developers. There might be something wrong with your project setup but I'm pretty sure that the current README instructions are correct.

I understand your assumptions but they are not correct

I guess this is the case 😭
I just tested it again and now everything works as expected 😕 🤷
In the meantime I also found the variant model [Gradle docs] and the dependencyInsights Gradle task [Gradle docs]. So it just run the following in two different projects:
./gradlew -q dependencyInsight --dependency reveal-core --configuration releaseRuntimeClasspath

The output is identical:
com.svenjacobs.reveal:reveal-core:3.0.0
  Variant releaseRuntimeElements-published:
    | Attribute Name                                  | Provided     | Requested    |
    |-------------------------------------------------|--------------|--------------|
    | org.gradle.category                             | library      |              |
    | org.gradle.status                               | release      |              |
    | org.gradle.usage                                | java-runtime | java-runtime |
    | org.jetbrains.kotlin.platform.type              | androidJvm   | androidJvm   |
    | com.android.build.api.attributes.AgpVersionAttr |              | 8.1.1        |
    | com.android.build.api.attributes.BuildTypeAttr  |              | release      |
    | org.gradle.jvm.environment                      |              | android      |

com.svenjacobs.reveal:reveal-core:3.0.0
\--- releaseRuntimeClasspath

com.svenjacobs.reveal:reveal-core-android:3.0.0
  Variant releaseRuntimeElements-published:
    | Attribute Name                                  | Provided     | Requested    |
    |-------------------------------------------------|--------------|--------------|
    | org.gradle.category                             | library      |              |
    | org.gradle.status                               | release      |              |
    | org.gradle.usage                                | java-runtime | java-runtime |
    | org.jetbrains.kotlin.platform.type              | androidJvm   | androidJvm   |
    | com.android.build.api.attributes.AgpVersionAttr |              | 8.1.1        |
    | com.android.build.api.attributes.BuildTypeAttr  |              | release      |
    | org.gradle.jvm.environment                      |              | android      |

com.svenjacobs.reveal:reveal-core-android:3.0.0
\--- com.svenjacobs.reveal:reveal-core:3.0.0
     \--- releaseRuntimeClasspath

So my new understanding is now:
Plugins and Gradle itselfs requests some information (variant attributes) which variant of the dependency to pick.
In case the dependency provides a variants list and this list contains a variant that "nearly" matches the requested criteria; it will pick it.
As you (reveal) provides on publishing a variant with the attribute org.jetbrains.kotlin.platform.type=androidJvm which matches with the requested attribute , Gradle will pick the -android version and therefore download the correct version.

Please understand that I don't want to add instructions to the README that are not necessary for 99% of developers. There might be something wrong with your project setup but I'm pretty sure that the current README instructions are correct.

Of course, this makes absolutely sense. Especially because others (in this case the Kotlin Pluin, AGP and Gradle itself) has the responibility to

publish it correctly
consume it correctly

However, thanks for this fast feedback and the constructive feedback 👍


fix: include useAngleUpdater in core-only bundle

:tada: This PR is included in version 1.1.7 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.7 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


fix: set default torchserve model store uri to v1

Context
Same as in https://github.com/kserve/kserve/pull/2635. Without v1 or v2 specified, the example results in the same issue as in https://github.com/kserve/kserve/issues/2631.
Proposed Changes

Use v1 version as default for the transformer example.

/lgtm
/approve


[$500] Send money - Enter keypress on amount page triggers pay with expensify popup and displays in corner

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697205384875589
Action Performed:

Open the app
Click on green plus and click send money
Select USD as currency, enter any amount and click Next
Select any user
Open amount page
Click enter and observe that pay with expensify popup is open in top left corner

Expected Result:
App should not trigger pay with expensify popup on enter keypress on amount page
Actual Result:
App triggers pay with expensify popup on enter keypress on amount page and displays it in top left corner
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/9e25b703-4bc8-435d-95cc-24666b7cb3fd
https://github.com/Expensify/App/assets/93399543/85f7db87-084c-4528-9906-e4ebdce4f9c4
https://github.com/Expensify/App/assets/93399543/06b84bea-3fd8-40b0-a929-6c17cf8299a5

MacOS: Desktop

https://github.com/Expensify/App/assets/93399543/95fa4790-3527-4432-ba70-b9219da5f024

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01620c1716cd0baeb7
Upwork Job ID:<PHONE_NUMBER>531128320
Last Price Increase: 2023-10-14

Proposal
Please re-state the problem that we are trying to solve in this issue.
Enter keypress on amount page triggers the pay with expensify popup which is present in the prev page
What is the root cause of that problem?
user goes to confimation list then to the amount page then back to the confirmation...
on back from the amount page, the confirmation page opens the same ref
What changes do you think we should make in order to solve the problem?
enforce fallback route when going back from the amount page so that it respwans the confirmation list page ,,, the same as we are doing in the other request money pages .
https://github.com/Expensify/App/blob/2c9c303199ef53f91d586c1fa35acb75b42afd1b/src/pages/iou/steps/NewRequestAmountPage.js#L145
to
Navigation.goBack(
  ROUTES.MONEY_REQUEST_CONFIRMATION.getRoute(iouType, reportID),
  true
);

POC
https://github.com/Expensify/App/assets/59809993/6ee8d09f-dac5-4ea5-b610-7eb5eab534cd

Okay, closing as dupe: https://github.com/Expensify/App/issues/29051


Update Octicons to v10.0.0

Summary

GitHub has recently released some new snazzy octicons, and would love to see them in Atom!
Motivation

To look more cutting edge 😍
Describe alternatives you've considered

Additional context

I would like to work on this as part of Hactoberfest and to start my experience on open source. Can you please provide more details on the local setting and what to achieve on this?

Hey @gopipofficial the best place to start would be https://github.com/atom/atom/blob/0f2975930e506785c05068a1c57934160e094e10/static/variables/octicon-mixins.less#L36-L48
However looking at the direction that github took to deliver octicons as svg rather than icon fonts, working on this would require a rework on how atom uses the icons.
Apologies I miss labeled this issue. If you are still willing to proceed working on this issue let me know.

I'll try my level best to achieve this before to start I'm having local setup issue working on it. Please give me sometime.

hi @gopipofficial  are you working on this ?

Yes, @pavan5555 ill be working on it. Unfortunately, I'm facing an atom local setup issue. Once I fixed that ill start working on it.

@sadick254 I regret to say this, I'm still facing an issue with the local setup. I've opened one issue for getting help on that.

Hi, @gopipofficial . Are you still working on this?

you please proceed with the issue. I just got the setup steps and going to implement it @sadick254  thanks for your response.

@Moe82 my local environment setup issue was fixed with the help of @sadick254  and now I started looking into the issue.

@sadick254 thanks for your input on setting up the local env. now its up and wanted to fix this issue. the issue is to change all the icons in the Atom from font icon to new octicons respectively right ???

Thats correct @gopipofficial

Thanks, I'm starting with the changes.

Wow that was so help help full for me thnaks for sharing such a valuable information i use these tips on my website SolankiGaming! and I am able to generate a lot of traffic.

Thanks for sharing this. This information will definitely help us. We Explain Computer and Technology on HowToGeek.

It's very informative. I really appreciate your works for the newbies. I follow these on my Blog HindiDigit

i would like to work on it plz explain what exactly i have to do

Thank you very much for sharing this valuable information I use these tips on my website industrialsafetyguide . And I appreciate your work.

Hey if this issue is still open I would like to work on it.

Thank you so much for this article. it was very informative. i really hope you continue making great content like this. i will definently follow these tips on my blog: Gadgetsglam

此 XML 檔似乎沒有任何與它相關的樣式資訊。文檔樹如下所示。
<rss xmlns：a10="http://www.w3.org/2005/Atom"版本="2.0">

米格羅索夫特支援 - Lync 電話版
米格羅索夫特支援
2021微軟
圖， 2021年05月06日 12：51：09 Z

https://support.microsoft.com/en-us/topic/description-of-the-cumulative-update-for-lync-2010-phone-edition-for-hp-4110-and-hp-4120-november-2011-daa89744-1e8a-809b-5a83-681226bd1c28

說明Lync 2010電話版的累計更新，HP 4110和HP 4120：2011年11月

描述 Lync 2010 電話版 HP 4110 和 HP 4120 的 2011 年 11 月累計更新。

弗里， 2020年04月10日 05：23：08 Z
2021-01-26T02：22：42Z

https://support.microsoft.com/en-us/topic/descript...

Is this issue still open I'd like to contribute?

@cloudguruab this won't be easy. Octicons quit using fonts and went with svgs. But you can try if you want to.

@UziTech I will give it a go

I found 2 resource in case it helps:
https://docs.brainstormforce.com/how-to-convert-svg-file-into-a-font-icon/
https://stackoverflow.com/questions/13278707/how-to-convert-svg-files-to-a-font/

@ThatXliner Thank you!

@BIGBANGDEVTRON

@sadick254 @UziTech Good job and thanks!!!
I hope those octicons...

Would performance have a hit if we instead replaced the spans with SVGs?

Hey @UziTech @sadick254 @ThatXliner,
I want to work on this issue, I know it's hard but I will persevere to make this update

@parrthpanchal go ahead 👍

I am facing problem while setting up atom locally for development. How can I resolve this error?

Looks like it is an error in https://github.com/atom/atom/blob/978843584aaeb25e25fbe53693bb9d227b4bfed1/script/lib/spawn-sync.js#L17
If you delete ${result.args.join(' ')} locally it should not throw an error.

If you delete ${result.args.join(' ')} locally it should not throw an error.

@UziTech Do you mean i should do something like this or I have misunderstood what you are trying to say?

ENOUGHT CLEAR ?

@parrthpanchal yes

@parrthpanchal yes

@UziTech  I tried that but still I am getting the same erroneous response!!

@metafusion3D no need to yell or make legal threats, just click the unsubscribe button under Notifications!

I wish if the update would come for WordPress so that I can use it on my site https://www.shoutmeback.com/

I think this is very informative. so I will use it on my blog https://gamerofficials.com/

Wow that was so help help full for me thnaks for sharing such a valuable information i use these tips on my website RehanousRehanous ! and I am able to generate a lot of traffic.

Wow that was helped me thank you for sharing mda

I am facing a problem while setting up atom locally for development. How can I resolve this error?

You must have git installed on your system.
Now, go to the folder where you want to have your Atom editor and then press right-click and then select the option Git bash Here. Now, fork the atom repo and then use the command git clone git@github.com:your-username/atom.git and replace your-username with your Github Username. Now, just do cd atom and after that, run script/bootstrap It worked for me.

go [through~glass^fGod1f+^ocus^9](

)

What is still needed to be done can I resume working if needed here?

Will respond soon Amen?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Harsh Ranjan Dwivedi @.>
Sent: Tuesday, May 3, 2022 3:01:56 PM
To: atom/atom @.>
Cc: HEIS7777777 @.>; Comment @.>
Subject: Re: [atom/atom] Update Octicons to v10.0.0 (#21049)
What is still needed to be done can I resume working if needed here?
—
Reply to this email directly, view it on GitHubhttps://github.com/atom/atom/issues/21049#issuecomment-1116527479, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYK7MTTML4IPCGSM2MP7EDTVIGA3JANCNFSM4OSV6ITA.
You are receiving this because you commented.Message ID: @.***>

https://faqwiki.us

Hey @johnletey , I would like to work on this as part of Hacktoberfest. Can you please assign this to me?

Sa


Support the distinction between Perdurants and Endurants

=================================
CHANGE REQUEST UNDER CONSTRUCTION
=================================
Background

A distinction that is often used in ontology engineering is that between things that simply are, denoted in philosophy as endurants, and things that happen over time, denoted perdurants.
Endurants / continuants
(taken from wikipedia, formal ontology )
Also known as continuants, or in some cases as "substance", endurants are those entities that can be observed-perceived as a complete concept, at no matter which given snapshot of time. Were we to freeze time we would still be able to perceive/conceive the entire endurant.
Examples include material objects (such as an apple or a human), and abstract "fiat" objects (such as an organization, or the border of a country).
Examples of the former are persons, furniture and other objects; examples of the latter are meetings, football matches,
Perdurants / occurrents
(taken from wikipedia, formal ontology )
Also known as occurrents, accidents or happenings, perdurants are those entities for which only a part exists if we look at them at any given snapshot in time. When we freeze time we can only see a part of the perdurant. Perdurants are often what we know as processes, for example: "running". If we freeze time then we only see a part of the running, without any previous knowledge one might not even be able to determine the actual process as being a process of running. Other examples include an activation, a kiss, or a procedure.
Requirements

Requirement 1
The ability in the standard to make a distinction between things that are and things that happen in time.
Requirement 2
Show that the resulting ontology remains coherent and consistent
Risk / Benefit analysis
Benefits
The requested distinction reflects an intuitive separation that is generally being applied by data models and recognised by applications that use or generate data. IT therefore makes sense to include such distinction in the ontology in order to closely match the intended meaning of the data. This improves the support to interoperability between applications that exchange data in accordance to UCO.
It does not enforce adopters to change their data model to recognise this distinction. Only when an application is using the distinction it can map those data elements to the appropriate category. This improves the accuracy of the intended meaning of data.
Risks

Competencies demonstrated

Competency 1

Competency Question 1.1
Result 1.1
Competency Question 1.2

Result 1.2
Solution suggestion

(Practical disclaimer on this comment: I am not a memory analyst.)
I think one of the complexities this pair of classes will introduce to UCO will specifically pertain to running processes and similar: observable:Process, observable:ProcessThread, and their subclasses.  I think in other foundational ontologies these would be Perdurantss (a.k.a. Occurrents), but in some conditions a Process (/Thread) can be frozen in time and analyzed, e.g. in some debuggers (such as gdb) or in paused virtual machines.  In these cases, they're effectively Endurantss (a.k.a. Continuants) - we've frozen time, and everything about the object is contained in that time-slice.  But trying to make an observable:Image of a running Process on a non-virtual, hypervisor-less device feels very much like the Process is a Perdurant - the imager likely cares a lot about what the Process has done before, and might do after, that Image is taken.
In a similar vein, though, I look forward to the clarity this class-pair will bring to observable:OperatingSystem.  UCO is currently loose in its treatment of this class, not specifying whether an instance of an OperatingSystem is something that is running or not, i.e. akin to a Process or not.  I've been wanting to propose OperatingSystemProcess as a class, knowing it should be  a subclass of Process, but not knowing if it should or could also be a subclass of OperatingSystem.

From discussion with @plbt5 : Another motivation for endurants vs perdurants is observable:MessageThread, whose state evolves with time.

(C/o remembering something when I was writing this comment...)
Separation of Endurants from Perdurants will help UCO describe the general "lifespan" of endurants, and give us the opportunity to decide whether they should handle their relationships to general time intervals differently.
Let's take flight human flight as an example.  Let's take a made-up person named Charlie, born in 1950, passed in 1990.  40-year life span.  Born after the Wright Brothers' flight (1903-12-17), but alive when humanity achieved the first human-on-the-moon landing (1969-07-20).  There are a few time relationships in there.
As pure time intervals, the event on 1903-12-17 "takes place before the event" on 1969-07-20.
kb:e-1903-12-17 ex:before kb:e-1969-07-20 .

If perdurants relate to time by specializing time intervals ...
drafting:Perdurant rdfs:subClassOf ex:TemporalInterval .

... then we can say, "The event of the first Wright Brothers' flight took place before the moon landing."
kb:WrightBrothersFlight ex:before kb:MoonLanding1 .

Now, let's take Charlie.  Born 1950, passed 1990; let's say Jan 1 00:00 UTC on both ends.  Charlie, as a human, has a "lifespan" that happens to have both ends defined.  We can define Sam's lifespan as an event, and from UCO's core:startTime and core:endTime being English-defined (as current in 1.2.0) as "The (initial|ending) time of a time range", we can define Charlie's lifespan here:
kb:Charlie
    a uco-identity:Person ;
    .
kb:CharlieLifespan
    core:startTime "1950-01-01T00:00Z" ;
    core:endTime "1950-01-01T00:00Z" ;
    .

How does kb:Charlie relate to kb:CharlieLifespan?
In other foundational ontologies, kb:Charlie is an endurant, and kb:CharlieLifespan a perdurant.  If we didn't do this, and treated kb:Charlie as appropriate to bear core:startTime, then we accidentally induce kb:Charlie becoming a time range.  Then it's appropriate by UCO's model to say:

The Wright Brothers' Flight took place before Charlie.

...which, seems ok...

The Moon Landing took place during Charlie.

...aaaaand, we have a problem.
The English hints that we should relate Charlie to Charlie's lifespan if we're going to relate Charlie to events, temporally:

The Wright Brothers' Flight took place before Charlie's lifespan.
The Moon Landing took place during Charlie's lifespan.

So, I suggest we consider this as further motivation for introducing endurants and perdurants to UCO.  Endurants should relate to time intervals as separated graph nodes.  Perdurants can specialize time intervals, or instead relate to them in their own way like perdurants.[^1]  My personal preference is that perdurants do specialize time intervals, but that specific decision is probably out of scope of this proposal.  For this proposal, I think it's fine to confirm the time separation on endurants.
Also, I did not realize that core:startTime and core:endTime already have their English written as though UCO has defined time ranges.  There is no time range class at the moment, and those two properties seem to only have constraints defined on core:Relationship at present.
[^1]: I recall there's a paragraph somewhere in OWL-Time or a supplement to it that says either way is appropriate when modeling time vs. other classes; that OWL-TIme is written to not force an adopter to go either way; and that the paragraph seemed applicable in time modeling outside of OWL-Time.  I can't find the paragraph at the moment, though.

PR #559 is posted implementing this proposal, and testing seems to show no conflicts against current CASE examples.

An update on risks of the perdurants-vs-endurants proposal:
CASE Issue 138 proposes changing case-investigation:Investigation to become a subclass of uco-core:Event, instead of how it is currently a subclass of uco-core:ContextualCompilation.
We should confirm as part of this proposal whether uco-core:Compilation and its subclasses are endurants.  @plbt5 ?
If so, we would have to consider if we're comfortable with what would need to change with data like this:
# (Today.)
kb:Investigation-1
    a case-investigation:Investigation ;
    uco-core:object
        kb:Device-1 ,
        kb:InvestigativeAction-1 ,
        kb:ProvenanceRecord-1
        ;
    .

It looks like that would become:
# (Assuming merging UCO Issue 544 and CASE Issue 138.)
kb:Investigation-1
    a case-investigation:Investigation ;
    uco-core:hasParticipant
        kb:Device-1 ,
        kb:ProvenanceRecord-1
        ;
    .
kb:InvestigativeAction-1
    uco-core:isPerdurantProperPartOf
        kb:Investigation-1
        ;
    .

@plbt5 - I didn't realize we had this asymmetry in the properties currently encoded in #559 .  This looks to me like a suggestion for adding inverse properties.

@ajnelson-nist I've considered whether it was necessary to include the InverseFunctionalProperty attribute to uco-core:hasParticipant, but decided that was too restrictive. At the same time, I overlooked the [owl:inverseOf](http://www.w3.org/TR/2004/REC-owl-semantics-20040210/#owl_inverseOf) attribute. Indeed, gUFO does not include an owl:inverseOf of its gufo:participatedIn, while funny enough we've defined its inverse as our uco-core:hasParticipant.
I don't see any objection to include the inverse, hence we can add
uco-core:participatesIn owl:inverseOf uco-core:hasParticipant .

to the solution of #559.

Thank you.  Let's talk through adding that tomorrow.
Meanwhile, this proposal is currently set as a UCO 2.0.0, backwards-incompatible proposal.  Are there parts of this proposal that you think could be added as part of UCO 1.x.0 (maybe even 1.3.0), such as the disjoint classes core:Endurant and core:Perdurant with no further subclassing, and the new properties?  This would make the divide available for new classes to use them along the way to UCO 2.0.0, while not impacting current classes.

Yes, that would make sense, wouldn't it? One can then start to use the distinction between Ps and Es, get used to it so to speak.
However....

It might result in intuitive incoherence, or cognitive dissonance, when combining the E/P distinction with classes that will become their subclasses with the UCO 2.0.0 release, but until then are just classes that exist aside to E/P. I'm not sure how helpful this will be for getting an understanding of the E/P distinction, because such illogical constructer are deemed to happen.
It will also produce a larger pile of refactoring issues, created by 1, to be performed after UCO 2.0.0

IMO we can pursue this suggestion, as long as we make crystal clear that their use should be minimised to test and evaluation scenarios only.

I'm not sure I follow why putting in E-P without subclassing now would cause a larger pile of refactoring issues?  Do you mean, larger than what's currently in #559, which targets 2.0.0?
Alternative, for discussion and/or pursuit:
Let's say, instead, that we take PR #559 and clone it to apply against the current develop, changing the E-P disjointedness shape to only raise a sh:Warning-level validation result.  This follows the deprecation pattern I've used on other proposals that deprecated something for removal in 2.0.0.
That could cause a lot of validation noise against current user data.  The prerelease review (validating all CASE examples) for #559 has finished against 2.0.0 without raising any problems, so maybe not.
Would you prefer either, or neither, be tried before 2.0.0?  We unfortunately can't try both at the same time, because putting in E-P disjointedness as a sh:Violation means we can't make current classes subclasses and be backwards-compatible.

Hmmm... Now its me that is not sure I follow your arguments. Let's talk about that tomorrow.

@plbt5 , I see an interesting suggestion from the property name isPerdurantProperPartOf - particularly, the "proper" word.    Does this mean UCO would also need an "isPerdurantImproperPartOf" property?  If we were discussing sets (or classes), we would be deciding where we would use the symbol ⊂ ("proper subset of") vs. the symbol ⊆ ("proper subset of or equal to").
I think isPerdurantImproperPartOf would be part of a sub-property hierarchy:
core:isPerdurantPartOf
    a owl:ObjectProperty ;
    rdfs:domain core:Perdurant ;
    rdfs:range core:Perdurant ;
    .

core:isPerdurantImproperPartOf
    a owl:ObjectProperty ;
    owl:propertyDisjointWith core:isPerdurantProperPartOf ;
    rdfs:subPropertyOf core:isPerdurantImproperPartOf ;
    .

core:isPerdurantProperPartOf
    a owl:ObjectProperty ;
    owl:propertyDisjointWith core:isPerdurantImproperPartOf ;
    rdfs:subPropertyOf core:isPerdurantImproperPartOf ;
    .

The rationale I see for that hierarchy is that a perdurant P1 being a proper part of another P2 implies that there exists some other portion of P2 that is outside of P1.  This is a stronger statement than just being a part.
P1 being an improper part of P2 is as strong a statement as being a proper part.  Though, I'm not sure what "improper" parthood would mean for certain pairings of UCO classes.  (And I do think these are questions special to UCO, not generic to foundational ontologies.  For instance, UCO has already decided that Activitys and Events are disjoint.)

Event E1 improper-part-of event E2: These are the same event?
Event E1 improper-part-of activity A1: The event is scoped entirely, expansively, to the activity, yet is not the activity (per disjointedness)?
Activity A1 improper-part-of activity A2: These are the same activity?
Activity A1 improper-part-of event E1: The activity is scoped entirely, expansively, to the event, yet is not the event (per disjointedness)?

...Having worked through that matrix of Perdurant's two current subclasses, I'm not sure improper perdurant-parthood is definable except for when the perdurants are the same class, and even then maybe only for core:Events.  This is writable in OWL without too much trouble, but does this mesh with expected use cases for Event mixing with Activity?
Regardless of the outcome for improper-parthood, I think proper-parthood looks safer to adopt today.  If the property hierarchy around proper-parthood is introduced later, I believe any existing assertions around proper-parthood would remain semantically consistent.

Thanks to the kind community member who pointed out an oddity in my subproperty hierarchy above.  I had a copy-paste error, now corrected.

I am sure I will have many more comments to provide once I have a chance to hear this proposal verbally presented on the OC call, have time to dig deeper into its written detail above, and discuss the topic in more depth on one or more targeted working calls but I wanted to make a quick comment now on a fundamental issue I see at the very start of the proposal.
I would disagree with the definitions used here for endurant and perdurant.
The proposal defines endurants as:

Also known as continuants, or in some cases as "substance", endurants are those entities that can be observed-perceived as a complete concept, at no matter which given snapshot of time. Were we to freeze time we would still be able to perceive/conceive the entire endurant.

I have not seen endurant defined in terms of inherent perceptual/conceptual completeness. If this were true then I would assert that pretty much everything in CDO/UCO would not fall into this bucket because evolution of understanding of UcoObjects is a fundamental basis of almost all cyber application domains. Very rarely do you have complete perception/conception of any object until its final version.
The most common definition I have seen of endurants are that they are concepts that can be defined independent of time. In other words, while your perception or understanding of it may change over time as you look at it from different angles, it is what it is and did not change over time unless some outside force acted on it to change it.

Examples include material objects (such as an apple or a human), and abstract "fiat" objects (such as an organization, or the border of a country).

These are excellent examples of "concepts that can be defined independent of time". They are not excellent examples of entities "that can be observed-perceived as a complete concept, at no matter which given snapshot of time". With almost all of these things we may observe-perceive them differently at different points in time. The nature of what they are may not change over time but our observation-perception of them does. This is the fundamental basis of duck-typing.
The proposal defines perdurants as:

Also known as occurrents, accidents or happenings, perdurants are those entities for which only a part exists if we look at them at any given snapshot in time. When we freeze time we can only see a part of the perdurant. Perdurants are often what we know as processes, for example: "running". If we freeze time then we only see a part of the running, without any previous knowledge one might not even be able to determine the actual process as being a process of running. Other examples include an activation, a kiss, a procedure, meetings, or a football match.

Again, I have not seen perdurant defined in terms of how much we can see of them or exists at any point in time. The most common definition I have seen of perdurants are that they are concepts that must be defined dependent on time. This is because they are inherently temporal in nature. Most typically they are something that occurs or happens across time but they can also be things than occur or happen only at a specific point in time. For the latter, it is still a perdurant (temporally dependent) even though we can see its entirety if we observed at the point in time that it occurred.
If we are going to discuss the concepts of endurants and perdurants we need to be very careful in how we define them and not imbue them with additional inappropriate context that is likely to cause increased confusion or misunderstanding.

@sbarnum is right in his observation that the proposal suffers from definitions on the proposed new concepts. This is a sloppy practice for which I do apologise. It will be corrected before bringing this into a requirements discussion at the OC.

I came across something when reviewing two foundational ontologies and Qualities (under proposal in Issue 535).
BFO has this class hierarchy, excerpted down to include endurant, perdurant, quality, and the endurant class that would be a direct superclass of uco-identity:Person:

owl:Thing

entity

continuant (= this proposal's "endurant")

independent continuant

material entity

object (= parent class of UCO's Person)

specifically dependent continuant

quality

occurrent (= this proposal's "perdurant")

gUFO has this class hierarchy, similarly excerpted:

owl:Thing

Individual

ConcreteIndividual
Endurant (= this proposal's "endurant")

Aspect

Intrinsic Aspect

Quality

Object (= parent class of UCO's Person)

Event (= this proposal's "perdurant")

The current state of this proposal has core:Endurant as a subclass of core:UcoObject.  However, from two foundational ontologies, endurants are seen to encompass qualities, and I think UCO would consider a quality an "inherent characterization thing" (which in BFO might be a specifically dependent continuant, and in gUFO an aspect or possibly intrinsic aspect; but, this detail is not necessarily part of this proposal).
I think this subclassing ...
core:Endurant rdfs:subClassOf core:UcoObject .

... needs to be this instead:
core:Endurant rdfs:subClassOf core:UcoThing .

I haven't yet given thought to whether perdurant should also move out from under UcoObject, aside from hierarchical symmetry with endurant.

I do support the change, and I advise (from an ontological perspective) to introduce a Quality class as another subclass of core:Endurant.


--skipold false argument doesn't work

The first time I run the command, I get expected output...
[root@host ~]# centos-package-cron --output stdout --skipold false
oading mirror speeds from cached hostfile
 * base: ftp.heanet.ie
 * epel: s3-mirror-eu-west-1.fedoraproject.org
 * extras: ftp.heanet.ie
 * remi-safe: remi.check-update.co.uk
 * updates: ftp.heanet.ie
The following security advisories exist for installed packages:

Advisory ID: CESA-2016--0370
(snip)

However, if I run it another time with --skipold false set, it doesn't give me any security advisories output:
[root@host ~]# centos-package-cron --output stdout --skipold false
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.heanet.ie
 * epel: s3-mirror-eu-west-1.fedoraproject.org
 * extras: ftp.heanet.ie
 * remi-safe: remi.check-update.co.uk
 * updates: ftp.heanet.ie
[root@host ~]#

If I manually delete the sqllite database and run again, the advisory output returns.
[root@host ~]# mv /var/lib/centos-package-cron/already_annoyed.sqlite /var/lib/centos-package-cron/already_annoyed.sqlite.old```

I'm guessing the boolean/argparse logic is not working there. I'll take a look when I get a chance.

According to a comment on this thread https://github.com/spotify/luigi/issues/193 "BooleanParameters work as False unless the switch is set in which case they are True"

I've got a fix on the way for this one too

Fixed in master, will crank out a new release with this soon


Minimal containers

https://github.com/pachyderm/pachyderm/issues/75

$ docker images
REPOSITORY           TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
pachyderm/pfsshard   latest              92ad6a776b36        4 minutes ago       10.31 MB
pachyderm/pfs        latest              8b3c1537a93f        4 minutes ago       634.9 MB
pachyderm/pfspfsd    latest              b1cd5e08a1c0        8 minutes ago       9.817 MB


Fix/7.7/update abstraction

Manual backport of #4706

InvalidSearchApi tests always returns 400 now on latest-7 will follow up in a new PR since that change requires porting to other branches too.


Option for size-specific icons

If I understand the new icon implementation correctly we're always just using the default 24x24 asset/svg and scaling it when using them at different sizes within the UI. This approach "breaks" the stroke width which isn't just scaled down from 24x24 and  in some cases we're actually using different assets for 24x24 vs. 16x16.
Suggestion:

Optionally be able to provide svg code for multiple sizes within the icon file itself
If no specific svg code for other sizes is provided, fall back to 24x24 asset and scale it (ideally, with a set stroke width of 1.5 for 16x16 / 2.5 for 32x32 though)

Happy to collaborate on this and provide assets where necessary!

@fabric-8 ok, I didn't understand that from the original issue description. Should we just always provide what we need rather than having fallbacks? I'd prefer to avoid needing conditionals and things just for a simple icon. From other references, is it typ to need so much code arnd icons? This is the ref storybook I used, and it simply has a size prop in the code and does just adjust the height/width of one svg:
https://main--64b56e737c0aeefed9d5e675.chromatic.com/?path=/docs/introduction--docs
https://github.com/storybookjs/icons

Sorry, I have spoken about this with @kyranjamie earlier, should have been more explicit about this in the issue.
The implementation was just an idea from my end I imagined to be a nice approach, we can def. leave out the entire fallback/conditional part. But being able to have size-specific svg code would be great. If that's too much effort for now let me know and I'll try to adjust the icons in question in a way that makes them scale / work a bit better.
Straight-up scaling is a bit gnarly as the stroke width values you'll end up with are going to be quite random and off-(pixel)grid

Straight-up scaling is a bit gnarly as the stroke width values you'll end up with are going to be quite random and off-(pixel)grid

Ok, np, I'll move fwd and refactor it with your requests here. I didn't realize it was discussed already! Sorry for not doing it correctly the first time through. Should be quicker now though with the new icons setup already. 👍

Awesome! If you need a helping hand doing the grunt work and getting the svg code for the 16 versions in please let me know, happy to help out!


"An error occurred while handling accessories"

Environment: macOS Mojave 10.14.6, Sony Bravia XBR65X850E (2017, 65")
Values in json edited for privacy
config.json:
`	"platforms": [
	{
		"platform": "config",
		"name": "Config",
		"port": 8080,
		"sudo": false
	},

	{
		"platform": "BraviaOSPlatform",
		"tvs": [{
			"name": "TV",
			"ip": "IP address",
			"mac": "mac with uppercase letters",
			"port": 80,
                            "wol":true,
			"psk": "key",
			"extraInputs": false,
			"cecInputs": true

		}]
	}
]

}
`
Not sure what's going on. The TV has constant access to the internet. I'm trying to set this up even while having the TV do some activity with the Internet. Authentication is set to "Normal and Pre-Shared Key", IP Control is enabled, Remote Start is enabled. How can I solve this?

Try v3.0.7 pls


Fix #41

Coverage increased (+0.2%) to 81.35% when pulling 5c0ead2073ba724ed611e46357e409636de94a9a on alpert:master into 971d57fbac9ecc80e78e0accdfc743b7f964dd59 on ajvb:master.

Coverage increased (+0.2%) to 81.35% when pulling 6215c394bd6b2efaebb21da82e23fab357172653 on alpert:master into 971d57fbac9ecc80e78e0accdfc743b7f964dd59 on ajvb:master.

Hi. I just updated request acording to your comments. Can you check please?

Coverage remained the same at 81.172% when pulling 0cd82dd22b0cdc1846dcedb28d368bcb8b4f8bfa on alpert:master into 971d57fbac9ecc80e78e0accdfc743b7f964dd59 on ajvb:master.

Done.

Coverage increased (+0.2%) to 81.35% when pulling 909cb9e56262f9e3265935c1dec1ae656e25e49d on alpert:master into 971d57fbac9ecc80e78e0accdfc743b7f964dd59 on ajvb:master.

@alpert Sorry for the delay.
I am a big fan of this, and it looks really solid, but there are no tests and there is no storage of the JobStat structs associated with a Job. Any possibility those two things could be added?
Let me know if you need any help with either of those.

Would definitely be nice to have postgres support, but still waiting for an update on JobStat and more tests.


Open a silent incident

Feature Description
Add an option in the modal of the /hellper_incident command so that an incident  is opened silently.
A silent incident is characterized by having a private channel and not notifying the main channel of incident when it opens.
Problem
There are some incidents that the entire organization should not be to know, for example, security incidents. That said, in such cases it is necessary to carry out the entire process of opening the incident manually, including its insertion in the databases.

@NFavareto this PR will be merged? If not, we can close it? We are working in repository maintence and we need a return here.


Changes related to the issues #61 and #62 plus 2 new build parameters to control the success conditions in CI tools

First I kept robymathew/ApexUnit@12fc46c solution of the issue #62  and #61 over mine and merged it with the solution of similar ones provided in the 2.6.8 release.
Then I solved the reporting issues introduced by those fixes as the computations where chunked in several calls and batches but not reconciled when having more than 200 tests (2075 tests methods in my case 🥇).
Finally I have added a time based report directory and two new optional parameters to fine tune the build outcomes when the scripts are in a Continuous integration cycle when for instance you are only interested in the reports but don't want to block the build chain.
//TODO : parametrize the time based report directory in order to keep the evolution seamless for current users

@eSh3m4 can you please resolve the conflicts and have your changes pass the travis CI?
I have assigned @dragon0556 to help you with code review

@eSh3m4 Can you please work on conflicts. It seems that, you have old .travis.yml file. Due to this travis CI is failing. I would be greate if you merge latest master into your branch and remove the conflicts.

Hi - Not quite sure of the direction regarding build results, I am reopening the PR and let you decide :)
Thank you all for this powerful tool!


MSID: 88247 Version: 2 DOI: 10.1101/2<IP_ADDRESS>3187

MSID: 88247
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>3187
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88247
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3187

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/88247v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>3187
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/88247/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Issues in structure


Webpack

Add webpack as module bundler

Codecov Report

Merging #2 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #2   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      9    +1
  Lines          42     40    -2
=====================================
- Hits           42     40    -2

Impacted Files
Coverage Δ

src/shapes/conectorShape.js
100% <100%> (ø)

src/components/RealTimeChannel.js
100% <100%> (ø)
:arrow_up:

src/shapes/channelShape.js
100% <100%> (ø)

src/components/RealTimeProvider.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update application-gateway-create-url-route-arm-ps.md

PowerShell cmdlet is incorrect.
There is not difine variable. ($appgwName, $rgname)

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

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@ShuheiUda : Thanks for your contribution to the Azure documentation! The author, @joaoma, has been notified to review your proposed change.

@sign-off

Thank you for catching that, @ShuheiUda . I approved the merge.


Remove float32_t typedef

float32_t is removed from latest embedded-common

Replace use of float32_t types with float
Update embedded-common

Check the following:

[ ] Breaking changes marked in commit message
[x] Changelog updated
[x] Code style cleaned (ran make style-fix)
[ ] Tested on actual hardware

@abrauchli Apparently the internal CI failed. Otherwise looks good.

the tests used the removed float32_t .. retriggered


Add logo in html

Description of the bug:
i want add logo to code HTML

Custom Pre-loader

Hi @Jimmy-glitch-10,
The CSS for #preloader img is already in place. To add a logo to your HTML code for the pre-loader, you need to insert an  img  element inside the  "div id="preloader"  section.
Include the below section to your code :

=> Make sure to replace "path/to/your/logo.png" with the actual path to your logo image file.


AWS Session Token is ignored in Wrangler Session

Reproduction steps:
Create Wrangler Session like this:
    sts_client = boto3.client('sts')
    assume_resp = sts_client.assume_role(RoleArn=some_role,
                                         RoleSessionName=str(uuid.uuid4()),
                                         DurationSeconds=3600)
    role_credentials = assume_resp['Credentials']

    boto_session = boto3.session.Session(aws_access_key_id=role_credentials['AccessKeyId'],
                                         aws_secret_access_key=role_credentials['SecretAccessKey'],
                                         aws_session_token=role_credentials['SessionToken'])

    role_session = awswrangler.Session(aws_access_key_id=role_credentials['AccessKeyId'],
                                            aws_secret_access_key=role_credentials['SecretAccessKey'],
                                            aws_session_token=role_credentials['SessionToken'])

and then make some request to AWS with it.
Expected result: request goes through
Actual result: exception from boto client
"botocore.exceptions.ClientError: An error occurred (InvalidClientTokenId) when calling the GetCallerIdentity operation: The security token included in the request is invalid."

PR to fix it will follow. Basically the issue is with _load_new_boto3_session not respecting aws_session_token at all

Thank you @alexanderromanov! Good catch!


Make sure describe/bind analysis errors result in sys.jobs_log entries

Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please


Just need one .editorconfig file

move .editorconfig files to repo root
also move SalesforceResultCreator to ...Internal namespace

nit: add a few trailing newlines to files

@dougbu,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Correct use of NeighbourhoodProcessing

Hello,
First of all, thank you for sharing this Python package, it's extremely useful! At the Meteorological Service of Catalonia we built a probability blending scheme based on Improver tools (neighbourhood, blending and calibration). Now, we're trying to simplify the code and I came across the lead_times parameter (I don't remember if it was available in previous versions) in the NeighbourhoodProcessing class. I have a doubt regarding how to properly use this class.
square_nbhood = NeighbourhoodProcessing(neighbourhood_method='square',
                                        radii=nbhood_sizes,
                                        lead_times=list(cube.coord('forecast_period').points.data))

where
nbhood_sizes = [1000, 2000, 3000, 4000, 5000, 6000]
lead_times = [1, 2, 3, 4, 5, 6]

When I call square_nbhood.process(cube) where cube is <iris 'Cube' of probability_of_precipitation_amount_above_threshold / (1) (time: 6; projection_y_coordinate: 688; projection_x_coordinate: 688)> , I get the following error:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/nowcasting/.conda/envs/lup/lib/python3.10/site-packages/improver/nbhood/nbhood.py", line 376, in process
    check_radius_against_distance(cube, self.radius)
  File "/home/nowcasting/.conda/envs/lup/lib/python3.10/site-packages/improver/nbhood/nbhood.py", line 72, in check_radius_against_distance
    if radius > max_allowed:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

If I call square_nbhood.process(cube) using:
for cube_slice in cube.slices([cube.coord(axis="y"), cube.coord(axis="x")]):
    square_nbhood.process(cube_slice)

Everything seems fine. So my doubt is, the correct way to implement NeighbourhoodProcessing with multiple lead_times is the second one? Because, if I check the source code for BaseNeighbourhoodProcessing (lines 389-395 of improver.improver.nbhood.nbhood.py) it already does the slicing I do before calling square_nbhood.process(cube), so I don't see why I have to previously slice the cube.
result_slices = CubeList()
for cube_slice in cube.slices([cube.coord(axis="y"), cube.coord(axis="x")]):
    cube_slice.data = self._calculate_neighbourhood(
        cube_slice.data, mask_cube_data
    )
    result_slices.append(cube_slice)
neighbourhood_averaged_cube = result_slices.merge_cube()

I hope I've explained myself well, please let me know if I didn't. Thank you very much!

Hi Enric,
Apologies for the slow response, but we've had a long weekend here in the UK for Easter. You've hit upon an issue that we don't encounter because of the way we use IMPROVER, but it remains something that it would be nice to correct.
The issue
Our processing using IMPROVER always uses files that contain a single validity time, i.e. there is not a leading time coordinate on the cubes. Most plugins will handle the case of multiple times in a single file, but it seems that neighbourhood processing is not amongst them, with this line being the reason, along with a lack of later handling.
The _find_radii function is calculating the radius to use for the cube's lead-time. For example, we might set up the plugin like this:
square_nbhood = NeighbourhoodProcessing(
    neighbourhood_method='square',
    radii=[10000, 20000],  # Units of metres
    lead_times=[0, 10]  # Units of hours
)

and then provide a cube with a lead-time of 5 hours (T+5). This function will calculate that the radius to use for neighbourhood processing should be 15000m, assuming a linear change in radius with lead-time.
In the case where a cube is provided with multiple times, as in your example, this function will return multiple radii that correspond to each of the relevant lead-times. For example:
cube lead-times: 0, 5, 10
returned radii: 10000, 15000, 20000

The plugin currently then assigns this to self.radius, our use of the singular "radius" here showing our assumption that this will be a single value. When a check is made that the radius is not too large it assumes a single value and it falls over with the error you are seeing.
The immediate solution
The immediate workaround for your case is to slice over the time coordinate, calling the neighbourhooding plugin for each slice, and then recombine the data into a single cube. This is essentially what you've shown above, slicing over the x-y coordinates outside the plugin. Note that the slicing that already exists within the plugin (which you highlight) is to handle multiple threshold values assuming there is a single time; the x-y slices are effectively slicing over a threshold coordinate.
A variation on your own solution is this:
square_nbhood = NeighbourhoodProcessing(
    neighbourhood_method='square',
    radii=[10000, 20000],  # Units of metres
    lead_times=[0, 10]  # Units of hours
)

result_slices = CubeList()
for cube_slice in cube.slices_over("time"):
    result_slices.append(
        square_nbhood.process(cube_slice)
    )
neighbourhood_averaged_cube = result_slices.merge_cube()

A better solution
This issue ought to be resolved to allow the neighbourhood plugin to handle multiple times. I've created the following issue for this to be done, though it is not high-priority work for us. If you felt it was something you could do, we always welcome contributions, but otherwise it will be done at some unknown future date.
https://github.com/metoppv/improver/issues/1894
I hope that's helpful and describes why you are seeing this issue. Let me know if you have any further questions, and if not, please close this issue.
Regards,
Ben

Hi Ben,
No worries at all! We also had a long weekend here in Catalonia.
Thank you very much for all your explanations and your rapid response, it was very helpful. It's clear now for me how to use the current NeighbourhoodProcessing class and I'll adopt the immediate solution you propose. However, I'll also try to provide a solution for multi-time cubes, I don't know if I'll manage to do it, we'll see.
Thank you again,
Regards,
Enric


SWARM-1220: Support propertiesFile loading from classpath/URL.

Motivation
In certain maven setups, the properties file resides in a different module than the swarm application/plugin.
Those setups need to make extra effort so that properties file can be used as a regular file path by the plugin(s).
Modifications
Extend PropertiesUtil.loadProperties(String) to load from (in that order):

a regular file path (unchanged)
the classpath via thread context classloader
a URL

Result
A propertiesFile can now be alternatively be loaded:

from a plugin dependency -> classpath resource
from a jar:file-URL
a "remote" URL/server

The same applies to environmentFile as it is processed in the same way as propertiesFile.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you created a JIRA and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

okay to test

I see the builds failed. I will fix this checkstyle violation tomorrow.

Rebased and fixed checkstyle violation.


[SPARK-36409][SQL][TESTS] Splitting test cases from datetime.sql

What changes were proposed in this pull request?

Split the test cases related to timestamp_ntz or timestamp_ltz functions from datetime.sql.
Add end-to-end tests for type constructor with timestamp_ntz and timestamp_ltz

Why are the changes needed?

Reduce the number of lines in datetime.sql from 300 to 200. It has a lot of test cases and will continue increasing.
The test cases related to timestamp_ntz or timestamp_ltz don't need to run again in datetime_legacy.sql. The refactor reduces unnecessary test runs.
Add end-to-end tests for new type constructors.

Does this PR introduce any user-facing change?

No
How was this patch tested?

Pass CI tests

Test build #142026 has started for PR 33633 at commit 66d5006.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46537/

Test build #142030 has started for PR 33633 at commit bb6a50e.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46541/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46541/

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

Test build #142030 has finished for PR 33633 at commit bb6a50e.

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

Test build #142036 has started for PR 33633 at commit a5b74fd.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46548/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46548/

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

@cloud-fan pinged me offline that he is working on a better test split. Let's don't merge this one for now.

Test build #142026 has finished for PR 33633 at commit 66d5006.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #142036 has finished for PR 33633 at commit a5b74fd.

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

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

As @cloud-fan opens https://github.com/apache/spark/pull/33640, I am closing this one.


Re-ordering local docs directories based on dependency order.

See #2444, in particular https://github.com/GoogleCloudPlatform/google-cloud-python/pull/2444#issuecomment-249918422

w00t! https://readthedocs.org/projects/google-cloud-python/builds/4447940/

Good news: The dependencies of our local packages are fixed
Bad news: The google-gax conflict is still hurting us


[WIP] Cleanup Part 2 - Rewrite

This is the follow up PR to https://github.com/kubereboot/kured/pull/990 .
It tackles deeper changes to help on the long term rewrite.
It opens the door to the following:

Use different locks in the future
Move the state to annotations
Move internal deps to internal

I need to reimplement this from scratch, please ignore my changes from now, until I mention this is ready for review (and [WIP] flag will be removed)


Opaque retry errors make debugging difficult

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I am trying to use object_store to write to the three major cloud provider storage solutions; when the put request fails (or, I assume, any other request), it enters a retry loop that looks like the following (with debug logs enabled):
2024-06-20T16:02:04.415522Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.12.5/src/connect.rs:497: starting new connection: https://s3.us-east-1.amazonaws.com/
2024-06-20T16:02:04.415898Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-util-0.1.5/src/client/legacy/connect/dns.rs:122: resolving host="s3.us-east-1.amazonaws.com"
2024-06-20T16:02:04.449611Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-util-0.1.5/src/client/legacy/connect/http.rs:631: connecting to <IP_ADDRESS>:443
2024-06-20T16:02:04.529885Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-util-0.1.5/src/client/legacy/connect/http.rs:634: connected to <IP_ADDRESS>:443
2024-06-20T16:02:04.616961Z  INFO /build/.build/cargo/git/checkouts/arrow-rs-d677d14273e07e8b/49d128d/object_store/src/client/retry.rs:331: Encountered transport error backing off for 0.1 seconds, retry 1 of 10: error sending request for url (https://s3.us-east-1.amazonaws.com/XXXXX)
2024-06-20T16:02:04.718218Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.12.5/src/connect.rs:497: starting new connection: https://s3.us-east-1.amazonaws.com/
2024-06-20T16:02:04.718742Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-util-0.1.5/src/client/legacy/connect/dns.rs:122: resolving host="s3.us-east-1.amazonaws.com"
2024-06-20T16:02:04.723407Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-util-0.1.5/src/client/legacy/connect/http.rs:631: connecting to <IP_ADDRESS>:443
2024-06-20T16:02:04.803010Z DEBUG /build/.build/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-util-0.1.5/src/client/legacy/connect/http.rs:634: connected to <IP_ADDRESS>:443
2024-06-20T16:02:04.891240Z  INFO /build/.build/cargo/git/checkouts/arrow-rs-d677d14273e07e8b/49d128d/object_store/src/client/retry.rs:331: Encountered transport error backing off for 0.15082853 seconds, retry 2 of 10: error sending request for url (https://s3.us-east-1.amazonaws.com/XXXXX)
...

There's no indication in there as to what actually went wrong or how to fix it.  The only way I was able to get the needed information was by hacking my own fork of object_store that printed out the raw error message, and then I discovered that the Docker container I was running in didn't have the needed certificates installed.
Describe the solution you'd like
Users shouldn't have to fork and patch the repo to discover why their requests are failing.  Can we add more logging output around retries?
Additional context
I'm happy to submit a PR for this but I've seem some (I think related) issues that have been closed or suggest that the current behaviour is as expected, so wanted to submit the issue first and make sure that folks agree about the proposed fix.
Related links: https://github.com/apache/arrow-rs/issues/5345, https://github.com/apache/arrow-rs/issues/5607, https://github.com/apache/arrow-rs/issues/5013

I believe the error will be returned once the max retries is exceeded

Oh, uh, apologies.  I'm not really sure what got interpreted as pejorative in there but it definitely wasn't intended!
Anyways, the only error I get back when max retries is exceeded is
Generic S3 error: Error after 10 retries in 3.848121029s, max_retries:10, retry_timeout:180s, source:error sending request for url (https://s3.us-east-1.amazonaws.com/XXXXX)

The information I needed to troubleshoot was the fact that there was an invalid certificate.  This is what I got out of printing e.source():
Some(hyper_util::client::legacy::Error(Connect, Custom { kind: Other, error: Custom { kind: InvalidData, error: InvalidCertificate(UnknownIssuer) } }))

Oh, uh, apologies. I'm not really sure what got interpreted as pejorative in there but it definitely wasn't intended!

I was referring to "Users shouldn't have to fork and patch the repo to discover why their requests are failing".

This is what I got out of printing e.source():

Generally it is considered best practice to either include an error as a source or include it in the display implementation. In this case reqwest/hyper is choosing the former option. To display an error you should walk the source chain and print them. If you use something like anyhow it will automatically do this for you when you call the debug implementation.
Now we blur this a little in some places for ergonomics reasons, but in general we want to leave it up to the caller to decide the level of verbosity they want.

The information I needed to troubleshoot was the fact that there was an invalid certificate

Did you try enabling more verbose logging? Hyper is quite chatty at the debug and trace levels and I would have expected it to provide further context on this? Perhaps we just need to better document how to get more verbose logging information out of tracing?

I was referring to "Users shouldn't have to fork and patch the repo to discover why their requests are failing".

Sorry again -- was not intending this to be pejorative.

Generally it is considered best practice to either include an error as a source or include it in the display implementation.

So a (very simplified) version of my code looks like this:
async fn do_stuff() -> anyhow::Result<()> {
  let path = "s3://my-bucket/foo/bar
  let (store, path) = AmazonS3Builder::from_env().with_url(path).build()?;
  let data = store.get(&path).await?;
  // do stuff with data
}

#[tokio::main]
async fn main() -> anyhow::Result<()> {
  do_stuff().await?;
}

Is your suggestion here that instead of falling back to the try operator (?) I should instead parse the error that is returned from store.get?

Did you try enabling more verbose logging?

Yes, the logs that I included in the original comment are with DEBUG logging enabled.  I guess I didn't specifically try bumping it to trace level, but I think what I expect as a user is that if there is an explicit error, there is (hopefully) enough information in the error logs to understand what caused the error.

Ok so I'm a dumbass.
After a bunch more investigation, I discovered that what I thought was happening (that I posted above) is not actually what was happening, there was another lib sitting inbetween that was swallowing the anyhow:: chain.  This wasn't at all obvious to me (in part because I didn't understand about the anyhow chain behaviour), but this doesn't seem like an issue with object_store.
Very sorry to waste your time on this, I will close the issue :(


[refactor] #4167: asset subcommand in CLI to be consistent

Description
In asset subcommand in the CLI operations like mint, burn, get, transfer had register. I refactored the subcommand to follow the suggestions in #4167.
Linked issue

Closes #4167

Use cases
Register
./iroha_client_cli asset  --definition-id="tea#looking_glass" --value-type=Quantity

Mint
./iroha_client_cli asset mint --asset-id="tea##mad_hatter@looking_glass" --quantity="100"

Burn
./iroha_client_cli asset burn --asset-id="tea##mad_hatter@looking_glass" --quantity="10"

Get
./iroha_client_cli asset get --asset-id="tea##mad_hatter@looking_glass"

Transfer
./iroha_client_cli asset transfer --to="white_rabbit@looking_glass" --asset-id="tea##mad_hatter@looking_glass" --quantity="5"

Checklist

[X] I've read CONTRIBUTING.md
[X] I've used the standard signed-off commit format (or will squash just before merging)
[X] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

Need to make CI pass fine

Need to make CI pass fine

Yes, sure for that I would contact Alex when gets better.

Seems like the help section for the commands in #4167 should also be updated to reflect removal of 'from' parameters

yes, i will do that


Change owner: When owner changes original depositor should no longer be able to see or modify the item

The original depositor (or other previous owners) should no longer see the item on their dashboard or be able to perform any actions with the item, and they should no longer receive any email notifications about the item.
@justinlittman asked me to separate this piece out from #2312
I have also made a ticket to add the user to the depositor list for the collection (#2329). And to have the collection manager notified about the ownership change and the addition of the new person to the collection (#2331).

@amyehodge I believe this may be done already. Do you want to test that this is the case?

@jcoyne This is good and can be closed.


can i install with npm?

can i install with npm?
I like this, can I install my project with npm?

No, not yet.. haven't had time to finish the project and add it to npm :/

How do I add to my project?

I need to separate the component from the example project and upload it to npm, all you need is this folder: https://github.com/Cristian006/electron-titlebar/tree/master/app/components/TitleBar

@omerfeyyaz take a look at my fork:
https://github.com/lazorfuzz/electron-titlebar/
It's the same project except converted to an importable react library. For now, just git clone it, add it to your project folder, and import it relatively. I made a pull request to @Cristian006 so he can eventually publish it to npm.

@omerfeyyaz you can now install it from npm 👍
npm install frameless-titlebar


⚠ Bofrost.fr has degraded performance

In adaef62, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1162 ms

Resolved: Bofrost.fr performance has improved in 09dab88 after 13 minutes.


Improve the typing for scalars

Goal

Improve the general typing of custom scalars

Changes

Create a new NexusGenScalars for all scalar types
Remove scalars from NexusGenRootTypes (might be a breaking change, need review)
Use the NexusGenScalars for all non specified (base GraphQL) scalars in input and output types
Add rootTyping parameter to asNexusMethod to allow the user to specify it, otherwise it will fallback to the backingTypeMap

References
Fixes #469

Content looks good to me. It's def. a breaking change if anyone was referencing a scalar type from core.GetGen<'rootTypes'>. What I'm not 100% sure right now though is if there's any part of the internal typings that are expecting the scalar types to be in the rootTypes. Maybe @tgriesser has better insights here?

AFAIK, the root arg of resolvers is typed using the rootTypes, but it doesn't make sense to me that a scalar would ever appear as a root/parent value in a resolver, which makes me think the PR is fine!

Agreed!
LGTM
I think we should merge this and get it into today's release which already includes one breaking change.


A synchronization problem and ICE networking error

Hi
When I am running Yahoo LDA on my hadoop cluster, I found the following problems:

permission denied for executable contained in jar package

To resolve this issue, I added chmod 755 $LDALibs/* at Formatter.sh and LDA.sh

synchronization problem of global/lda.dict.dump
I've found that before the process 0 finished writing global/lda.dict.dump if other processes tried to run the following script:

${HADOOP_CMD} dfs -get ${mapred_output_dir}/global/lda.dict.dump lda.dict.dump.global
it cannot download the file and whole process is going crashed. So, I put the synchronization code such as wait_for 60 ${mapred_output_dir}/global/lda.dict.dump.

The critical problem of multi-machine of Yahoo LDA

Finally, I got the following problem, this is not related with running script, so how can I recover this situation?
1020 03:57:06.626588 20423 Merge_Topic_Counts.cpp:103] Initializing global dictionary from lda.dict.dump.global
W1020 03:57:11.659412 20423 Merge_Topic_Counts.cpp:105] global dictionary Initialized
terminate called after throwing an instance of 'Ice::ConnectionLostException'
what():  TcpTransceiver.cpp:248: Ice::ConnectionLostException:
connection lost: Connection reset by peer
Should I modify LDA.sh script to check the error code of each module execution and repeat unless the error code is success?
Thank you!

On Friday 21 October 2011 03:23 AM, metacret wrote:

Hi
When I am running Yahoo LDA on my hadoop cluster, I found the following problems:

permission denied for executable contained in jar package

To resolve this issue, I added chmod 755 $LDALibs/* at Formatter.sh and LDA.sh

cool!

synchronization problem of global/lda.dict.dump
I've found that before the process 0 finished writing global/lda.dict.dump if other processes tried to run the following script:

${HADOOP_CMD} dfs -get ${mapred_output_dir}/global/lda.dict.dump lda.dict.dump.global

I dunno why you say that other processes try to get the global
dictionary before its written. There is already a
wait_for_all 60 ${synch_dir}"/global_dict";
that takes care of it.

it cannot download the file and whole process is going crashed. So, I put the synchronization code such as wait_for 60 ${mapred_output_dir}/global/lda.dict.dump.

The critical problem of multi-machine of Yahoo LDA

Finally, I got the following problem, this is not related with running script, so how can I recover this situation?
1020 03:57:06.626588 20423 Merge_Topic_Counts.cpp:103] Initializing global dictionary from lda.dict.dump.global
W1020 03:57:11.659412 20423 Merge_Topic_Counts.cpp:105] global dictionary Initialized
terminate called after throwing an instance of 'Ice::ConnectionLostException'
what():  TcpTransceiver.cpp:248: Ice::ConnectionLostException:
connection lost: Connection reset by peer

This is more of a hadoop problem. Connection can be lost due to many
reasons beyond the control of LDA. So its only the checkpointing &
restart mechanism that will take care of these. You need to worry about
these. LDA is confiured to automatically restart from the last
checkpointed iteartion.
Thanks,
--Shravan
PS: Sorry for the late response. Was really busy with some other stuff

Should I modify LDA.sh script to check the error code of each module execution and repeat unless the error code is success?
Thank you!


Redraw plot after click event?

Hello.
Firstly, this plugin is great! I'm trying to mimic the "data link" feature that's available in the native grafana time series panel. My thought is that when a user clicks on a data point, a dynamic annotation can be built based on where the user clicked and then displayed on the graph.
I'm able to get the annotation to show up on the first click, but then subsequent clicks do not update the location of the annotation in the graph.
Any thoughts on how to accomplish this? Here is the JS in the OnClick input box. I'm on version 1.7.0
var point = data.points[0];

var xValue = point.x;
var yValue = point.y;

var url = "https://example.com/details?x=" + xValue + "&y=" + yValue;
var info = "Value at " + xValue + ": " + yValue;
function dateStringToEpoch(dateString) {
    // Convert the date string to a Date object
    var dateObj = new Date(dateString);

    // Get the time in milliseconds, then convert to seconds (UNIX epoch)
    return Math.floor(dateObj.getTime());
}
var annotation = {
x: dateStringToEpoch(xValue),
y: yValue,
xref: 'x',
yref: 'y',
text: "More info", // Clickable link
showarrow: true,
arrowhead: 2,
ax: xValue,
ay: yValue
};

parameters.layout.annotations = [annotation]

Interesting, let me look at this! There are new event handlers for version 1.8.0 that should provide the location of every click. Not sure if that will help, but I'll try now.

It seems like the library would have pass the "graph id" in conjunction with the relayout plotly method? This is a snippit from the Plotly docs:
// update only values within nested objects
var update = {
    title: 'some new title', // updates the title
    'xaxis.range': [0, 5],   // updates the xaxis range
    'yaxis.range[1]': 15     // updates the end of the yaxis range
};
Plotly.relayout(graphDiv, update)

https://plotly.com/javascript/plotlyjs-function-reference/

Ah no the issue is that changes to the options from the onclick don't stick. I'm working on fixing this such that the data, layout, config can be modified by the onclick script.


Chapter 3 - Build System has incorrect optimization flags.

The text underneath the table of build modes on https://ziglearn.org/chapter-3/ specify a few command line flags for how to set optimizations (eg.)

These may be enabled in zig run and zig test with the arguments -O ReleaseSafe, -O ReleaseSmall and -O ReleaseFast.

However the actual compiler optimization flags directly from the compiler help text are these flags:
-Drelease-safe=[bool]        Optimizations on and safety on
-Drelease-fast=[bool]        Optimizations on and safety off
-Drelease-small=[bool]       Size optimizations on and safety off

Did the flags change recently?

If you look at https://ziglang.org/documentation/0.9.1/#Build-Mode, you will see that -Drelease-<mode> is for changing the release modes when compiling with build.zig/zig build.
$ zig build --help
<omitted
  -Drelease-safe=[bool]        Optimizations on and safety on
  -Drelease-fast=[bool]        Optimizations on and safety off
  -Drelease-small=[bool]       Size optimizations on and safety off
<omitted>

For zig build-exe, build-lib, build-obj, and run, -O Release<Mode> is correct.
$ zig run --help
<omitted>
  -O [mode]                 Choose what to optimize for
    Debug                   (default) Optimizations off, safety on
    ReleaseFast             Optimizations on, safety off
    ReleaseSafe             Optimizations on, safety on
    ReleaseSmall            Optimize for small binary, safety off
<omitted>


CI/DOC: do not overwrite index.html in bluesky/bluesky.github.io

Context: https://github.com/bluesky/hklpy/pull/36#issuecomment-700314184.
This is resolved via the environment variable DOCTR_VERSIONS_MENU_WRITE_INDEX_HTML=false (see https://goerz.github.io/doctr_versions_menu/v0.3.0/command.html#customizing-index-html for details). I tested the generation of the docs branch locally, and with this setting the index.html is not updated.
attn @klauer @danielballan @prjemian

@mrakitin nice find - would you mind applying what you've learned to caproto CI, when you get a chance?

Thanks for merging, @danielballan!


Payment reminders not being sent if type is delay and attached after attendance

There is a #TODO in attendEvent.
The Julebord event was created, people signed up and then afterwards the payment object was attached. Since the payment type was set to delay, no payment relations were created due to the if payment part of the conditional, thus no reminders will be sent out and noone will be unattended.

This is outdated.


Already initialized constant Psych::Visitors::ToRuby::SHOVEL

Seeing this when I run specs:
/Users/dberger/Repositories/manageiq-djberg96/gems/pending/util/extensions/miq-yaml.rb:9: warning: already initialized constant Psych::Visitors::ToRuby::SHOVEL

/Users/dberger/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/psych-2.0.16/lib/psych/visitors/to_ruby.rb:333: warning: previous definition of SHOVEL was here

@miq-bot assign @jrafanie


Rock Band Touring Website

Title and Issue number

Title :
Rock Band Touring Website
Issue No. : #511
Code Stack : html, css, js
Close #511

Video (mandatory)

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have updated the projectData.json file for my contribution
[X] I have added the img of my project in the assets/img section

Additional context (Mandatory )
Are you contributing under any Open-source programme?

codepeak

@aindree-2005 please add your project in the project.json file and upload a pic of your project in the assests folder

@shruti-sen2004 Sorry about that. I have fixed it


fix(Navbar): Fixes #463 by ensuring that the default role is now empty

fix(Navbar): Fixes #463 by ensuring that the default role is now empty for nav elements.

The default is now not set; however, we could adjust this based on the tag. For example if the tag is nav and the role is navigation then it's dropped. That could be the other alternative that way ... div elements get the role attribute.
@eddywashere  Thoughts?

ping @eddywashere


[Scenario] The Coven of Antoine Manor (DomeAcolyte)

What kind of mission do you want to add (mark with an X, e.g. [X] Descent)?

[X] Mansions of Madness
[ ] Descent

What expansions does the scenario require?

[ ] Conversion Kit (CK)
[ ] First Edition (MoM1E) - Also Recurring Nightmares
[ ] Fatal Alchemy (FA) - Also Suppressed Memories
[ ] Call of the Wild (CotW) - Also Suppressed Memories
[ ] Beyond the Threshold (BtT)
[ ] Streets of Arkham (SoA)
[ ] Sunctum of Twilight (SoT)
[ ] Horrific Journeys (HJ)
[ ] Path of the Serpent (PotS)

What expansions can the scenario optionally use?

[ ] Conversion Kit (CK)
[ ] First Edition (MoM1E) - Also Recurring Nightmares
[ ] Fatal Alchemy (FA) - Also Suppressed Memories
[ ] Call of the Wild (CotW) - Also Suppressed Memories
[ ] Beyond the Threshold (BtT)
[ ] Streets of Arkham (SoA)
[ ] Sunctum of Twilight (SoT)
[ ] Horrific Journeys (HJ)
[ ] Path of the Serpent (PotS)

Please enter the GitHub Url to your scenario here
https://github.com/vidimus/DomeAcolyte/tree/main/Lost_chronicles_04

Another scenario from DomeAcolyte (https://www.twitch.tv/domeacolyte)
(Description from the creator discord channel):
The Coven of Antoine Manor is a game of deductive reasoning, in which you're kidnapped by a witch, and must identify your foe, amongst fellow captives. The game changes each time, giving room for replay, and it only uses base game components, so it's great for playing it!

added to manifest and statistics sheet

Thanks, @antontimmermans!


coverity 1199998 : return code not handled

Address issue with TSHttpHdrUrlGet()

clang format failed! https://ci.trafficserver.apache.org/job/clang-format-github/408/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/419/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/404/

FreeBSD11 build failed! https://ci.trafficserver.apache.org/job/freebsd-github/2102/

Linux build failed! https://ci.trafficserver.apache.org/job/linux-github/1996/

Intel CC build failed! https://ci.trafficserver.apache.org/job/icc-github/531/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/664/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/458/

should be fixed

clang format failed! https://ci.trafficserver.apache.org/job/clang-format-github/448/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/571/

[approve ci]

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/445/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/462/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/2037/

clang format failed! https://ci.trafficserver.apache.org/job/clang-format-github/452/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/575/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/449/

FreeBSD11 build failed! https://ci.trafficserver.apache.org/job/freebsd-github/2141/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/702/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/2041/

FreeBSD11 build failed! https://ci.trafficserver.apache.org/job/freebsd-github/2145/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/706/


Update azure-template.md

Summarize the change in the pull request title
Describe your change, specifically why you think it's needed.
Fixes #Issue_Number (if necessary)

@raghuke : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

#sign-off
Once merged, this should be live with the next daily publishing process. Right now that should be tomorrow (Tuesday, 19 March) around 11:00 Pacific time. No further action needed from you.
p.s. As a Microsoft FTE, in the future, please use sccmdocs-pr repo. Use the same process, just after you click Edit on the article, switch the URL to sccmdocs -pr.

After re-build, we'll merge this PR.

FYI, @raghuke  ,
As @aczechowski mentioned: Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
Here's some links to more details about how to do that:

Read about authors working in the public repo for more information.

If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.


Enable GitHub Service Hook for Packagist

I don't know if you have enabled it, but it is very recommended so it is updated when you push instead of one time per day (from https://packagist.org/about).
To activate the hook, you can do the following (from https://packagist.org/profile/):

GitHub Service Hook
Enabling the Packagist service hook ensures that your package will always be updated instantly when you push to GitHub. To do so you can go to your GitHub repository, click the "Settings" button, then "Webhooks & Services". Add a "Packagist" service, and configure it with your API token (see above), plus your Packagist username. Check the "Active" box and submit the form. You can then hit the "Test Service" button to trigger it and check if Packagist removes the warning about the package not being auto-updated.

I'm saying this because your last update (93d8eb7) still doesn't appear in packagist.

I think this can be closed as it seems to be updating ok

I think that isn't updated after a push again. Maybe you need to revise the hook or the GitHub Service for Packagist.

hi @PhoneixS , sorry for delay answer, i would appreciate if you can manage to contribute with some fixes, I'm out of time to contribute actively for current package.


Need Support port for puma

It'll be the best solution if support option -p #{port}

@duykhoa Yeah, who can add feature HTTP listening? And where to log?


[Bug]: ValueError Gram matrix in 401k example

Describe the bug
https://docs.doubleml.org/stable/examples/py_double_ml_pension.html
example shows ValueError in PLR model
ValueError Gram matrix passed in via 'precompute' parameter did not pass validation when a single element was checked - please check that it was computed properly. For element (4,5) we computed 3375.771728515625 but the user-supplied value was 3375.773193359375.
Minimum reproducible code snippet
https://docs.doubleml.org/stable/examples/py_double_ml_pension.html
Initialize learners
Cs = 0.0001*np.logspace(0, 4, 10)
lasso = make_pipeline(StandardScaler(), LassoCV(cv=5, max_iter=10000))
lasso_class = make_pipeline(StandardScaler(),
LogisticRegressionCV(cv=5, penalty='l1', solver='liblinear',
Cs = Cs, max_iter=1000))
np.random.seed(123)
Initialize DoubleMLPLR model
dml_plr_lasso = dml.DoubleMLPLR(data_dml_base,
ml_g = lasso,
ml_m = lasso_class,
n_folds = 3)
try:
dml_plr_lasso.fit(store_predictions=True)
except ValueError as ve:
print('ignore exception ValueError', ve)
Expected Result
no ValueError
Actual Result
ValueError Gram matrix passed in via 'precompute' parameter did not pass validation when a single element was checked - please check that it was computed properly. For element (4,5) we computed 3375.771728515625 but the user-supplied value was 3375.773193359375.
Versions
Linux-5.13.0-30-generic-x86_64-with-glibc2.29
Python 3.8.10 (default, Nov 26 2021, 20:14:08)
[GCC 9.3.0]
DoubleML 1.0 -> pip list says DoubleML 0.4.1
Scikit-Learn 1.0

Thanks for your bug report. This is not a bug in DoubleML but in scikit-learn introduced in version 1.0.0 and not yet fixed. For further information see https://github.com/DoubleML/doubleml-docs/issues/45#issuecomment-930172645, https://github.com/scikit-learn/scikit-learn/issues/21997 and https://github.com/scikit-learn/scikit-learn/pull/22059.
As a temporary fix you can either downgrade to scikit-learn in version < 1.0.0 or you adapt the datatype in the pandas DataFrame in the following way (it then doesn't matter what scikit-learn version you use):
import numpy as np

import doubleml as dml
from doubleml.datasets import fetch_401K
from sklearn.linear_model import LassoCV, LogisticRegressionCV
from sklearn.preprocessing import StandardScaler
from sklearn.pipeline import make_pipeline

data = fetch_401K(return_type='DataFrame')

# HERE: Change of datatypes
data = data.astype({'nifa': 'float64', 'net_tfa': 'float64', 'tw': 'float64', 'inc': 'float64'})

features_base = ['age', 'inc', 'educ', 'fsize', 'marr',
                 'twoearn', 'db', 'pira', 'hown']
data_dml_base = dml.DoubleMLData(data,
                                 y_col='net_tfa',
                                 d_cols='e401',
                                 x_cols=features_base)

Cs = 0.0001*np.logspace(0, 4, 10)
lasso = make_pipeline(StandardScaler(), LassoCV(cv=5, max_iter=10000))
lasso_class = make_pipeline(StandardScaler(),
LogisticRegressionCV(cv=5, penalty='l1', solver='liblinear',
Cs = Cs, max_iter=1000))

np.random.seed(123)
dml_plr_lasso = dml.DoubleMLPLR(data_dml_base,
ml_g = lasso,
ml_m = lasso_class,
n_folds = 3)
dml_plr_lasso.fit(store_predictions=True)

Btw, thanks for the "DoubleML 1.0 -> pip list says DoubleML 0.4.1" hint. This was in fact caused by a small bug in our issues template, see https://github.com/DoubleML/doubleml-for-py/commit/db6be27fa79837d2f5b3bf53f58f5d252d6d3895.

Hi Malte,
thanks for clarification. I was not able to detect this a scikit-learn error.
i applied your workaround and it works.
Thanks

No Worries, that is often not so easy to identify. Thanks again for the report which hopefully helps other users facing the same issue.


Provide test data set

To compare senzing's model and libpostal's original model side-by-side, we made two Dockerfiles (in one of which we installed the senzing model and in the other we installed the default model). We then mounted ~100,000 addresses and a test script to parse addresses in each container and found the output results produced by each were identical.
I expect this merely reflects a configuration error in how we built libpostal and/or installed pypostal. However, there seems to be no simple way to validate the installation explicitly and confirm which data directory and model is being used, as far as I can tell.
One way to confirm or deny that the senzing model is indeed being used as expected in the container would be to use the reference data cited in your README.
Please kindly include in the repository the data set of 12950 addresses that was used to test and verify the model. If this test set was available, the expected difference in results between the senzing model and the original libpostal model could be positively confirmed or denied and aid in our ability to troubleshoot the model configuration on our end.

Thank you for the data and thanks for the suggestion. We plan to make the test data set (or subset of it) available in the future. We included customer data in it and we will need to groom the set before it can be made available.
Here are a few addresses you can use to verify the installed model:
wankengasse 10, 2560 berndorf sankt veit an der triesting at
banco de las garzas 885, las grutas 8521
30000 26th avenue south, federal way 98003
19190 old state highway 120, groveland 95321
RR 2 Box 152
They will parse differently between the models.
Here is the Senzing data model parsing:
`> wankengasse 10, 2560 berndorf sankt veit an der triesting at
Result:
{
"road": "wankengasse",
"house_number": "10",
"postcode": "2560",
"suburb": "berndorf",
"city": "sankt veit an der triesting",
"country": "at"
}

banco de las garzas 885, las grutas 8521

Result:
{
"road": "banco de las garzas",
"house_number": "885",
"city": "las grutas",
"postcode": "8521"
}

30000 26th avenue south, federal way 98003

Result:
{
"house_number": "30000",
"road": "26th avenue south",
"city": "federal way",
"postcode": "98003"
}

19190 old state highway 120, groveland 95321

Result:
{
"house_number": "19190",
"road": "old state highway 120",
"city": "groveland",
"postcode": "95321"
}

RR 2 Box 152

Result:
{
"road": "rr 2",
"house_number": "box 152"
}`
And here you have the libpostal-out-of-the-box model parsing:
`> wankengasse 10, 2560 berndorf sankt veit an der triesting at
Result:
{
"road": "wankengasse",
"house_number": "10",
"postcode": "2560",
"city": "berndorf sankt veit an der triesting",
"country": "at"
}

banco de las garzas 885, las grutas 8521

Result:
{
"house": "banco de las",
"road": "garzas",
"house_number": "885",
"road": "las grutas",
"postcode": "8521"
}

30000 26th avenue south, federal way 98003

Result:
{
"house_number": "30000",
"road": "26th avenue south federal way",
"postcode": "98003"
}

19190 old state highway 120, groveland 95321

Result:
{
"house_number": "19190",
"road": "old state highway 120 groveland",
"postcode": "95321"
}

RR 2 Box 152

Result:
{
"road": "rr 2 box",
"house_number": "152"
}`
I hope this helps.

We provided the test data in the latest release:
https://github.com/Senzing/libpostal-data/blob/main/files/tests/v1.1.0/test_data.csv