iCAL SubCalendar Name Missing

G'day All,
we have about 20 regular event organisers. Each has been given their own sub-calendar with moderated access to manually resolve any scheduling clashes. When the combined calendar is exported using iCAL the events get titles such as:
SUMMARY:Regular Meeting
rather than the extended event title seen on the combined calendar featuring the sub-calendar name in brackets.
Can I correct this with a template change?
Thank You
Peter

I so wish I knew how to code. I am confident the problem is in iCalProvider.vb at lines 578 & 723.
The first references oEventRecurMaster.EventName & the latter oEvent.EventName.
The "EventName" part is wrong because it only returns the EventName field.
It needs to be a calculated object; an object with the same definition as "[event:title]": Event title and the sub calendar modulename when defined in settings.
Unfortunately, further is currently beyond my skill level. Can anyone please help fix this?
Thank You
Peter

Am I the only one using iCAL & SubCalendars? Should I be looking at alternate calendar management?

Is this still in the "too hard" basket?

It is still on the list to do. The conversion to C# had more (negative) side effects than expected. And since I am on holiday till end of nov, do not expect any change on this very soon.
Sorry.

WAAAHHHH!!!!!!!!
From: stale[bot]<EMAIL_ADDRESS>Sent: Tuesday, 4 February 2020 6:26 PM
To: DNNCommunity/DNN.Events<EMAIL_ADDRESS>Cc: Peter Casper<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DNNCommunity/DNN.Events] iCAL SubCalendar Name Missing (#45)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/DNNCommunity/DNN.Events/issues/45?email_source=notifications&email_token=AGBFMQV75OIDAECMU6TRSPLRBERDFA5CNFSM4C5QG3K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKWX3GI#issuecomment-581795225, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGBFMQX4OWX2347NUJA4NX3RBERDFANCNFSM4C5QG3KQ.

I understaand your "WAAAHHH"....
I am just trying to do some cleanup of issues...

You are also cleaning up all suggestions, have the suggestions been evaluated?
Franc Simari
https://momzey.com/ Momzey.com
978 375-7275
From: Ernst Peter Tamminga<EMAIL_ADDRESS>Sent: Tuesday, February 04, 2020 6:07 AM
To: DNNCommunity/DNN.Events<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [DNNCommunity/DNN.Events] iCAL SubCalendar Name Missing (#45)
I understaand your "WAAAHHH"....
I am just trying to do some cleanup of issues...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/DNNCommunity/DNN.Events/issues/45?email_source=notifications&email_token=AC3WHCXJCA22EODXRDZLWHDRBFD3VA5CNFSM4C5QG3K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKXG4UA#issuecomment-581856848 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AC3WHCX4LYNPOTXQZZR3YQTRBFD3VANCNFSM4C5QG3KQ .  https://github.com/notifications/beacon/AC3WHCTGWZ2APRIZTYUTMCDRBFD3VA5CNFSM4C5QG3K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKXG4UA.gif

@FrancSimari
Suggestions for enhancements have been inspected, but.... if there is no activity for 6 months (an arbitrary period I just set for the bot) and nobody is addressing the issue or create a PR, the suggestion might still be valid, but it will clutter the list of issues. It might well be that the issue is made by a person who moved away from the module to another solution and that the issue is no longer relevant.
Please note that the issue is not gone, it will just be marked as "closed" after 21 days after marked as stale.
If somebody enters a comment in the issue in a period of 21 days, while the issue is marked as "stale", it will start a new period of 180 days.
The stale bot principle is copied from DNNPlatform, although the DNNPlatform uses shorter periods to keep the list of DNNPlatform issues clean and actual.

I now have 23 sub-calendars with a 24th requested last week-end.
On the main calendar, the events are all easily recognizable with generic event names but unique identifiers from each sub menu (named after the organizing group) in brackets. The iCAL only shows the generic event names. The event organisers  would like to distribute their calendars & the combined calendar however they can currently only do it via screen dumps.

@PeterCasper I know you have made this request a long time ago.
I did spend quite some time trying to include this in the iCal some time ago, but the code was not made by me, quite old and not very clear. So, until now, no success with this request sofar. Sorry.
The request is still valid.

Bump?

I still have members requesting this.

I still have members requesting this.

Bump


ReferenceError: navigator is not defined

Bug report
Description / Observed Behavior
When building the app with NextJS in Jenkins, the build fails with the following error message:
ReferenceError: navigator is not defined
    at Object.641 (/app/node_modules/swr/dist/index.js:1:11816)
    at __webpack_require__ (/app/node_modules/swr/dist/index.js:1:154)
    at Object.516 (/app/node_modules/swr/dist/index.js:1:3661)
    at __webpack_require__ (/app/node_modules/swr/dist/index.js:1:154)
    at Object.325 (/app/node_modules/swr/dist/index.js:1:1394)
    at __webpack_require__ (/app/node_modules/swr/dist/index.js:1:154)
    at startup (/app/node_modules/swr/dist/index.js:1:291)
    at module.exports.202 (/app/node_modules/swr/dist/index.js:1:323)
    at Object.<anonymous> (/app/node_modules/swr/dist/index.js:1:333)
    at Module._compile (internal/modules/cjs/loader.js:959:30) {

Expected Behavior
The build should succeed
Repro Steps / Code Example
Or share your code snippet or a CodeSandbox link is also appreciated!
Additional Context
NextJS 9.1.5
SWR 0.2.3

@niamleeson how do you run the tests and what are the testing tools you're using? from the log I saw the module resolved the cjs build of swr so I think it's testing running inside Node.js instead of browser runtime.
did you try to use jsdom to polyfill browser runtime stuff like (window, navigator, etc.)? or probably try jest with jsdom env enabled to run the tests?

This was happening during development as well. I had to do the following in _app.jsx
import App, { Container } from 'next/app';
if (typeof global.navigator === 'undefined') global.navigator = {};
// const navigator = {};

class MyApp extends App {
    // ...
}

swr will access window.navigator in browser runtime only rather than the node.js or any server side. could you provide minial reproducible sample or code snippet for this issue? will be great helpful for us to identify the root cause.

I tried really hard to get a reproducible code, but it looked like it has something to do with the compilation process. I even got to a place where I commented out one component that didn't use useSWR and the next build would finish successfully. Then I would uncomment the component back and the build would fail with the navigator message.
However, I did manage to permanently fix it by using this module and specifying swr in it: https://github.com/wellcometrust/next-plugin-transpile-modules

I upgraded swr from 0.3.1 to 0.3.2 and it fixed the problem.

The problem seems to be still around in another form. Version 0.3.2 let me build successfully both locally and on Vercel but going to the page presents this runtime problem (from vercel log -f command).
2020-09-04T06:14:02.002Z      ef446b94-a2e0-4cae-9f81-5ce058068f0c    INFO    info  - Loaded env from .env.production
2020-09-04T06:14:03.486Z      ef446b94-a2e0-4cae-9f81-5ce058068f0c    ERROR   Unhandled error during request: ReferenceError: navigator is not defined
at Object.641 (/var/task/node_modules/swr/dist/index.js:1:11265)
at webpack_require (/var/task/node_modules/swr/dist/index.js:1:154)
at Object.516 (/var/task/node_modules/swr/dist/index.js:1:3693)
at webpack_require (/var/task/node_modules/swr/dist/index.js:1:154)
at Object.325 (/var/task/node_modules/swr/dist/index.js:1:1420)
at webpack_require (/var/task/node_modules/swr/dist/index.js:1:154)
at startup (/var/task/node_modules/swr/dist/index.js:1:291)
at module.exports.202 (/var/task/node_modules/swr/dist/index.js:1:323)
at Object. (/var/task/node_modules/swr/dist/index.js:1:333)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
2020-09-04T06:14:03.495Z      ef446b94-a2e0-4cae-9f81-5ce058068f0c    ERROR   Uncaught Exception      {"errorType":"ReferenceError","errorMessage":"navigator is not defined","stack":["ReferenceError: navigator is not defined","    at Object.641 (/var/task/node_modules/swr/dist/index.js:1:11265)","    at webpack_require (/var/task/node_modules/swr/dist/index.js:1:154)","    at Object.516 (/var/task/node_modules/swr/dist/index.js:1:3693)","    at webpack_require (/var/task/node_modules/swr/dist/index.js:1:154)","    at Object.325 (/var/task/node_modules/swr/dist/index.js:1:1420)","    at webpack_require (/var/task/node_modules/swr/dist/index.js:1:154)","    at startup (/var/task/node_modules/swr/dist/index.js:1:291)","    at module.exports.202 (/var/task/node_modules/swr/dist/index.js:1:323)","    at Object. (/var/task/node_modules/swr/dist/index.js:1:333)","    at Module._compile (internal/modules/cjs/loader.js:1138:30)"]}
Duration: 1613.03 ms  Billed Duration: 1700 ms        Memory Size: 1024 MB    Max Memory Used: 59 MB
Unknown application error occurred

I do get the same ReferenceError: navigator is not defined when trying to use SWR in an Ink app (https://github.com/vadimdemedes/ink)
(The SWR requests do succeed tho)
ReferenceError: navigator is not defined
    at Object.isOnline (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:1636)
    at Object.<anonymous> (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:10779)
    at step (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:3829)
    at Object.next (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:3114)
    at /home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:2799
    at new Promise (<anonymous>)
    at n (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:2547)
    at Timeout.r [as _onTimeout] (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:10575)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

Additional Context
nodejs: 14.15.1
swr: 0.4.0
react: 17.0.1
ink: 3.0.8
typescript: 4.1.3

I do get the same ReferenceError: navigator is not defined when trying to use SWR in an Ink app (https://github.com/vadimdemedes/ink)
(The SWR requests do succeed tho)
ReferenceError: navigator is not defined
    at Object.isOnline (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:1636)
    at Object.<anonymous> (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:10779)
    at step (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:3829)
    at Object.next (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:3114)
    at /home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:2799
    at new Promise (<anonymous>)
    at n (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:2547)
    at Timeout.r [as _onTimeout] (/home/me/dev/git/my-ink-cli-2/node_modules/swr/dist/index.js:1:10575)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

Additional Context
nodejs: 14.15.1
swr: 0.4.0
react: 17.0.1
ink: 3.0.8
typescript: 4.1.3

@lildata currently swr can only works very smoothly in browser runtime only (the time when I wrote this reply). the short unofficial work around could be:
useSWR(key, fetcher, {
  isOnline() { /* online detector for ink runtime */ },
  isDocumentVisible() { /* online detector for ink runtime */ },
})

making swr become more flexible for different runtime is still in progress :)

@lildata currently swr can only works very smoothly in browser runtime only (the time when I wrote this reply). the short unofficial work around could be:
useSWR(key, fetcher, {
  isOnline() { /* online detector for ink runtime */ },
  isDocumentVisible() { /* online detector for ink runtime */ },
})

making swr become more flexible for different runtime is still in progress :)

@huozhi Many thanks & my bad I just assumed node was supported...

@huozhi Many thanks & my bad I just assumed node was supported...

Closing as it's been made clear that SWR only supports a browser environment, for now, and better error handling has been added!

Closing as it's been made clear that SWR only supports a browser environment, for now, and better error handling has been added!

hmmm I don't know. My jest tests ran just fine with react-native 0.63.3 and now started to fail with 0.66.3
All of the sudden all swr related tests fail.


fix(39373): const {} = require import causes Debug Failure

Fixes #39373

Generally we use getNameOfDeclaration or something like that to avoid duplicating the diagnostic. It'll fill it in with something like (anonymous) or (default).

Actually, getHeritageClauseVisibilityError uses it
https://github.com/microsoft/TypeScript/blob/17022388bde8d37bd98ad98f8b3ed733ab7684f6/src/compiler/transformers/declarations/diagnostics.ts#L464
and it returns undefined for the case
export default class extends Foo {}

Based on the type definition, a name can be undefined, however, that case was not handled in getHeritageClauseVisibilityError.
https://github.com/microsoft/TypeScript/blob/17022388bde8d37bd98ad98f8b3ed733ab7684f6/src/compiler/types.ts#L2780-L2781
For that reason, TS crashes because it uses diagnostic messages with two arguments, however, receive only one.
https://github.com/microsoft/TypeScript/blob/17022388bde8d37bd98ad98f8b3ed733ab7684f6/src/compiler/transformers/declarations.ts#L141-L144
@DanielRosenwasser Do you propose to replace the missed name by creating Identifier with the(anonymous) name instead of using a new diagnostic message? I think we can do it, just need to create a new Identifier and change the logic to getting text because a new Identifier will not be present in the source file.
https://github.com/microsoft/TypeScript/blob/17022388bde8d37bd98ad98f8b3ed733ab7684f6/src/compiler/transformers/declarations.ts#L134-L136

Actually I think it's fine, especially since functions have the same diagnostic.

I actually realized that the test might need to be changed to use at least one .js file because of #39617...


Making save image work in all browsers

To start:

[ ] Safari
[ ] Edge

@elrumordelaluz: Probably related on #28.
Investigating, seems that the problem is that dom-to-image doesn't support Safari because:

it uses a stricter security model on  tag. Suggested workaround is to use toSvg and render on the server.`

https://github.com/niklasvh/html2canvas works in Edge.

https://github.com/dawnlabs/carbon/issues/245
OK thats closed that issue so what is the fix?
How can i use this editor ?

@tytower meanwhile this Issue is open, could you please use the App with Chrome or Firefox browsers?

Looks like is still not possible to type

"Does not accept any files or text in Palemoon browser"
I use Palemoon . I don't want to use other browsers Why is it doing this in Palemoon?

@tytower can you please share the user agent for "Pale Moon"?

It's not the world to download another browser and use it for just this site if you really want that image. You can even run it on localhost instead of pinging the deploy site.

@tytower The purpose of this issue was to track progress on browser support that the core team is working on and we're limiting our support commitment to major browsers. Sorry for the confusion here, I updated the issue title to better reflect this.
While we don't have the resources to support all alternative browsers, if you or anyone else are able to solve the problem I'd be happy to review a PR that fixes the app in Pale Moon!

I'm still having issues in Safari, the colours are not preserved and the text is just white, probably a problem inside the backend fallback for Safari. 😅

Problem still here. Cursor isn’t visible

It is strange because everything works using the same CodeMirror editor on following demo page:
https://codemirror.net/

Problem still here. Cursor isn’t visible in iOS Safari

It was incorrect. Carbon works on iOS safari, but cursor isn’t visible on iOS Chrome.


Train models in layer_runtime

Train models in layer_runtime module. Invocation similar to datasets:
 python -m layer.executables.layer_runtime --project=layer/layer-runtime-55 ./train_model

bors merge


Replace equal by allequal

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (4d85adf) 100.00% compared to head (fe852c1) 100.00%.

:exclamation: Current head fe852c1 differs from pull request most recent head 15538e0. Consider uploading reports for the commit 15538e0 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #524   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           24        24
  Lines         1846      1850    +4
  Branches       267       267
=========================================
+ Hits          1846      1850    +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


raw_eq intrinsic is not supported

This occurs for instance here, via the PartialEq impl for arrays of integers.

Here is a minimal testcase for this issue:
fn main() {
    let _ = [0] == [0];
}

outputs:
thread 'rustc' panicked at minimize/src/bb.rs:205:25:
unsupported Rust intrinsic `raw_eq`
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


Execute jar file directly without using ballerina jvm

Description:
When a jar file is given to run it gets executed from within the jvm created by ballerina command. This can be improved to run directly from the bash/bat file.
Steps to reproduce:
Affected Versions:
1.0.0

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/19157


Link to our Volunteer Info page in our README.md

Overview
Currently, our README links interested volunteers directly to the volunteer form, not to our volunteer info page (which contains the form).  We need the README to link to the Getting Involved volunteer info page instead, similar to how our CONTRIBUTING.md file does.
Action Items

[ ] Replace the text in the README.md under the Getting Involved section:
If you would like to help Bloom and receive special access to our organization and volunteer opportunities, please get in touch with us to express your interest in volunteering via this form."
with the following text:
"If you would like to help Chayn and receive special access to our organization and volunteer opportunities, please visit our Getting Involved page."
[ ] Make sure the above sentence contains a markdown link to our Getting Involved page: https://www.notion.so/chayn/Get-involved-423c067536f3426a88005de68f0cab19?pvs=4

Resources/Instructions

How to make Markdown Links

Hey @kyleecodes , can you assign me this issue.

Hey @FardeenCODEIIEST thank you for your interest! I'm keeping this issue open to others because only 1 no-code hacktober issue is allowed per person and you've already been assigned another no-code issue on this repo!

Ok @kyleecodes , no problem

Closed: https://github.com/chaynHQ/bloom-backend/commit/2992f43ec00c2a88fe01d7a5129e24d9ef0f5cf4


Create base device with read/write capabilities to named endpoints

We currently have a ButtplugDevice class in Core that is used for a combination of protocol and device handling. We should move the protocol handling to a base Protocol class, and the Buttplug Device should define generic Read/Write functions that writes to named endpoints (similar to what ButtplugBluetoothDevice does).

Done in 0.11.0


56 - Quotes Generator.

This extension generate new quotes every time we click the new quote button.

@kalashvasaniya Give proper numbering to the folder which you are adding.


Added civo cloud

Added civo cloud managed k3s cluster

@TheYkk can you please clarify if that is a free trial? or just a monthly discount? Do you need to pay to start using that credit?
I would like to add the requirements per cloud provider.. for example if a CC is required or not to make sure that we can classify the trial experiences better.

If your billing under $70 you don't need to pay anything.
You don't need to pay to start using that credit.
And you have to add your credit or visa card.

@TheYkk awesome! Let me add that


Split out prepare_patches and fetch_patches methods.

The new fetch_patches method wasn't exclusively fetching so shouldn't have been skipped when it was.
Fixes #7558.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Thanks for fixing this so quickly.


npm install react-native@latest installs v0.15 rc

Not sure if this is the new direction that you're going in but it seems to have deviated from the historical norm. @ide @brentvatne

This keeps happening https://github.com/facebook/react-native/issues/3546 - might be worth scripting it :P

Thanks... should be fixed now.


Implement the Runtime Cache

Summary
Given it's so crucial for performance when working with large amounts of data, a complete design for the IVC (#148) means that it's ready to be implemented. This task deals with the process of implementing the caching mechanism, dependency tracking and analysis, and eviction strategy.
Value
Recomputation after changes in large projects will be faster through a reduction in the average amount of computation that needs to be performed after a change.
Specification

Implement the design for caching, first implementing the actual value storage.
Then implement the dependency analysis and tracking.
Finally, implement the cache eviction strategy.

Acceptance Criteria & Test Cases

IVC has been implemented and results in meaningful performance improvements.
It also results in no regressions in the uncached general case performance.

Superseded by planning.


chore: enable new submission flow [DO NOT MERGE]

This PR resolves ONYX-952
Description
https://github.com/artsy/echo/pull/630

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 32c0edc33fc9428ff0e54097f76a318944d68dc3


How to deal with proposed obsoletions (or proposed changes) overall

Currently KGCL has a simple data model where each type represents a change or set or changes. A change object can be thought of as a proposition, and can have metadata added to this.
In some cases, ontologies may want to represent the proposition directly in the ontology without fully enacting the change. This is most prominent in the case of obsoletion, where we may want metadata about a proposed ontology to live in the ontology for a period such as a month or two months, where it is queryable. However, we can imagine this for any change type.
An additional challenge here is that the mechanism for representing propositions in an ontology is not as standardized as for example obsoletion (which is itself not as standardized as it could be). E.g in mondo things may go into a mondo-specific "obsoletion_subset".
Some options here:
One is to discourage the notion of storing propositions in the ontology. If you want to query for propositions (such as proposed obsoletions), then query the GitHub issue and PR repository. There is a clear separation of concerns here: the ontology represents the current state of things, and we use infrastructure intended for propositions to store propositions. However, this is not not an ideal solution, e.g. do we expect all ontology browsers to implement some complex ingest mechanism?
Another is to create a collection of shadow classes, e.g. ProposedObsoletion, ProposedNodeMove, ... This is fairly awkward though.
Another option is to add a flag to all classes such as "partial: bool". The actual changes applied to an apply agent would vary depending on the setting of this flag. We can even imagine having maturity levels etc.
The simplest option might be that if something is a proposition we simply insert the change object as KGCL triples into the ontology. The ontology simply stores its own change. This may encounter resistance as people might like continuing to use familiar mechanisms such as oio:subset, IAO IDs etc.
What will probably sit best with existing ontologies is if there is a way to customize how an apply command works on an ontology specific basis, perhaps making "partial" a parameter on the application function

The simplest option might be that if something is a proposition we simply insert the change object as KGCL triples into the ontology.

Trying to figure out how that would look like… Do you already have a clear idea in mind?
Would it be under the form of annotations on the class concerned by the change?
For example:
obsolete UBERON:1111111 with alternative UBERON:2222222, UBERON:3333333

would yield an annotation like this:
AnnotationAssertion(
  Annotation(kgcl:has_nondirect_replacement UBERON:2222222)
  Annotation(kgcl:has_nondirect_replacement UBERON:3333333)
  kgcl:NodeObsoletion UBERON:1111111 ????)

?

Trying to figure out how that would look like… Do you already have a clear idea in mind?

probably not!
The two options are

as string encoded KGCL syntax/DSL or json serialization (a bit ugh)
triples exactly as you clearly illustrated

I was thinking more like 2, but there are all kinds of issues here. We are "polluting" the ontology with individuals. We have implicit mapping of rdf predicates to APs and all the dangers that entails. It's quite unnatural from the POV of what we normally do in OBO ontologies. But it's very generic and can be used for any change type....

If we want to allow changes to be “proposed“ (rather than acted upon directly) on a case-by-case basis... we could have a maybe keyword in front of all KGCL commands?

I think this makes sense, but often the "maybe" will be implicit. E.g. the way I think the mondo editors want to work is that it's always a maybe, and there is an explicit state transition from maybe to actual

as string encoded KGCL syntax/DSL or json serialization (a bit ugh)

It would be very easy to add information about proposed changes in that form, but if the information is intended to be queryable (e.g. someone wants to know which terms are slated for obsoletion), that may not be the most practical. One would need to first extract the annotation (e.g. with SPARQL) and then to parse the KGCL to figure out what the change is (is it an obsoletion or any other kind of change).
If the idea is already set to store the information directly into the ontology/KG, I’d be inclined to go all the way and store it in a “native” form that can be manipulated/queried as any other contents in the ontology.

triples exactly as you clearly illustrated

So a change about an existing class is rendered as an annotation on the class. Likewise, a change about a relationship (e.g. kgcl:PredicateChange) can be rendered as an annotation on the axiom representing the relationship to be modified.
But I am unsure about a change that proposes to create a new class. Where would we store that (what would we be annotating)? Ideas:

Ontology-level annotations?
Have a “dummy” class in the ontology that represents nothing but is specifically intended to carry the annotations about proposed new classes?
Actually create the proposed new class, and then annotate it with the KGCL annotations (which would serve to mark the class as being “provisional”)?

the way I think the mondo editors want to work is that it's always a maybe, and there is an explicit state transition from maybe to actual

OK. I imagine something as follows:

All KGCL changes are rendered as annotations in the ontology. Each change contains, among other metadata, the date when the change was proposed.
If the editors later decide to reject a change, all they have to do is to remove the corresponding annotation.
Periodically (e.g. every month), we run a apply-pending command that iterates over the KGCL annotations in the ontology, and actually apply any change that has been proposed more than X weeks ago (changes that have been proposed less than X weeks are left as they are until the next run of the apply-pending command — or until they are manually removed).

I have a (very) rough, (very) experimental PoC in my wip/provisional-changes branch. It only supports NodeObsoletion for now (with or without replacement or alternatives).
This adds two new commands to my KGCL plugin for ROBOT:

partial-apply, which takes the same arguments as the normal apply command (e.g. --kgcl COMMAND to pass a single change directly from the command line, --kgcl-file FILENAME to read changes from a file) but simply stores the changes as annotations in the ontology;
apply-pending, which extracts the KGCL annotations from the input ontology, converts them back to KGCL objects, and then applies them to the ontology for good (and remove the annotations).

If we do end up storing the provisional changes as annotations, I’d suggest that we avoid using anonymous individual like in my example above. They cause at least two issues:

They are not rendered very nicely in Protégé:

More importantly, they cannot be stored in an OBO file (not even, surprisingly, in the owl-axioms header tag), which is obviously a problem for ontologies that uses this format as their edit format. Sure, this can be worked around by storing the provisional changes in a dedicated component in another format, but that’s not great.

Instead, I’d suggest something like this:
AnnotationAssertion(
  Annotation(kgcl:has_nondirect_replacement UBERON:2222222)
  kgcl:NodeObsoletion UBERON:1111111 "Proposed for obsoletion"^^xsd:string)

where the annotation value is a small, human-readable string.
This would make the provisional change nicer to visualise in Protégé:

and make it perfectly serialisable in the OBO format:
property_value: https://w3id.org/kgcl/NodeObsoletion "Proposed for obsoletion" xsd:string {https://w3id.org/kgcl/has_nondirect_replacement="UBERON:2222222"}

Or, we could have a dedicated annotation property (e.g. kgcl:PendingChange) and use the type of change (e.g. kgcl:NodeObsoletion, kgcl:NodeMove, etc.) as the annotation value, as in:
AnnotationAssertion(Annotation(kgcl:has_nondirect_replacement UBERON:2222222) kgcl:PendingChange UBERON:1111111 kgcl:NodeObsoletion)

I think this would make slightly more sense, and it would also make it slightly easier to later extract the annotations to apply the pending changes – just extract all the kgcl:PendingChange annotations, instead of extracting all the annotations with an IRI in the kgcl: namespace).

This is quite ingenious
Of course it’s not ideal having two mappings to rdf/owl but the lack of
quoting in rdf (sigh) makes the direct form impractical as you point out
We might want to have a different namespace for the AP translation just in
case anyone ever wants to combine?
The lack of uniformity between NewX and other changes on X is bothering me
a little. In some ways having all proposals be ontology annotations is more
balanced. But having it be on the about entity is more direct and visible.
But maybe having it on the ontology makes it easier to see all pending
changes in one place? Like the TODOs at the top of a file?
Curious what others think!
On Fri, Feb 9, 2024 at 4:02 AM Damien Goutte-Gattat <
@.***> wrote:

If we do end up storing the provisional changes as annotations, I’d
suggest that we avoid using anonymous individual like in my example above.
They cause at least two issues:

They are not rendered very nicely in Protégé:
Screenshot.2024-02-09.at.10.57.03.png (view on web)
https://github.com/INCATools/kgcl/assets/53821801/55dcdf49-8433-4bb3-ba31-00384db1315c
More importantly, they cannot be stored in an OBO file (not even,
surprisingly, in the owl-axioms header tag), which is obviously a
problem for ontologies that uses this format as their edit format. Sure,
this can be worked around by storing the provisional changes in a dedicated
component in another format, but that’s not great.
Instead, I’d suggest something like this:
AnnotationAssertion(
Annotation(kgcl:has_nondirect_replacement UBERON:2222222)
kgcl:NodeObsoletion UBERON:1111111 "Proposed for obsoletion"^^xsd:string)
where the annotation value is a small, human-readable string.
This would make the provisional change nicer to visualise in Protégé:
Screenshot.2024-02-09.at.11.33.53.png (view on web)
https://github.com/INCATools/kgcl/assets/53821801/f553aac3-1ab8-4d64-a6b3-7b4a7d16b03b
and make it perfectly serialisable in the OBO format:
property_value: https://w3id.org/kgcl/NodeObsoletion "Proposed for obsoletion" xsd:string {https://w3id.org/kgcl/has_nondirect_replacement="UBERON:2222222"}
—
Reply to this email directly, view it on GitHub
https://github.com/INCATools/kgcl/issues/49#issuecomment-1935807394, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOMHSY4P6DKELK2I2BDYSYF63AVCNFSM6AAAAABC4LFU72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVHAYDOMZZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

The lack of uniformity between NewX and other changes on X is bothering me
a little.

Me too.
One particular problem of class creation changes is that such changes would almost never occur in isolation. At the very least, a kgcl:ClassCreation change would be accompanied by a kgcl:PlaceUnder change to give the new class a position within the hierarchy, and most likely a whole bunch of other changes as well (e.g. a kgcl:NewTextDefinition to define the class, one or several kgcl:EdgeCreation to establish relationships, maybe some kgcl:NewSynonym, etc.).
I am reluctant to use ontology-level annotations to represent all those changes that pertain to a single (new) class. I am not even sure I have a clear idea of what that would look like.
For now, I think that actually creating the new class and then annotate it with all the other changes relevant for that class is the best option – but I am also curious of what other folks have to say.
An obvious problem of creating the new class immediately is that there is a risk that people start using the class, maybe because they don’t realise it is provisional. But that’s something that can be checked against in CI.

For clarity, the proposed storage methods envisioned so far are (assuming, for the example, that we want to store the change represented by obsolete EX:1234 with alternative EX:5678,EX:6789):
A. String annotation using the KGCL DSL serialisation format
AnnotationAssertion(
  Annotation(dcterms:date "2024-02-14"^^xsd:date)
  Annotation(dcterms:creator ORCID:1111-2222-3333-4444)
  kgcl:NodeObsoletion EX:1234 "obsolete EX:1234 with alternative EX:5678,6789")

Simple, but not great as it requires whoever wants to know what the change is to (re-)parse the KGCL change again.
B. Parameters stored in annotations, value is an individual
AnnotationAssertion(
  Annotation(dcterms:date "2024-02-14"^^xsd:date)
  Annotation(dcterms:creator ORCID:1111-2222-3333-4444)
  Annotation(kgcl:has_nondirect_replacement EX:5678)
  Annotation(kgcl:has_nondirect_replacement EX:6789)
  kgcl:NodeObsoletion EX:1234 _:x)

The use of an anonymous individual is annoying (it’s not displayed in an user-friendly manner in Protégé and cannot be serialised properly in the OBO flat file format).
C. Similar, but value is a human-readable string
AnnotationAssertion(
  Annotation(dcterms:date "2024-02-14"^^xsd:date)
  Annotation(dcterms:creator ORCID:1111-2222-3333-4444)
  Annotation(kgcl:has_nondirect_replacement EX:5678)
  Annotation(kgcl:has_nondirect_replacement EX:6789)
  kgcl:NodeObsoletion EX:1234 "Proposed for obsoletion")

Intended to address the issues with B (displayable nicely in Protégé, serialisable in OBO).
D. Value is the type of KGCL change
AnnotationAssertion(
  Annotation(dcterms:date "2024-02-14"^^xsd:date)
  Annotation(dcterms:creator ORCID:1111-2222-3333-4444)
  Annotation(kgcl:has_nondirect_replacement EX:5678)
  Annotation(kgcl:has_nondirect_replacement EX:6789)
  kgcl:PendingChange EX:1234 kgcl:NodeObsoletion)

Also reasonably user-friendly, slightly more developer-friendly (just one annotation property to look for when querying for pending changes in an ontology). That’s what is currently implemented in KGCL-Java.

I just finally got to read this proposal. This is extensive, and I think I like the general

direction. It seems like a complex system for something that we have not even managed to convince people of - clearly documenting intended changes. I think most ontologies will just continue to go ahead with the change (whether this is good or bad is a different story). I am against "proposed additions" from an SOP perspective, but can see "proposed reclassification" and "proposed obsoletion" to be potentially valuable.

I would advocate for system purely build around annotation properties, and avoid individuals, anonymous or otherwise. Some of our tools like SLME are pretty unreasonable when it comes to individuals (including even signature disjoint individuals). I dont know about anonymous individuals but my guess is we will have some OBO format issues with that.
FWIW, my favourite is D (assuming that kgcl:PendingChange and kgcl:NodeObsoletion are both APs):
AnnotationAssertion(
  Annotation(dcterms:date "2024-02-14"^^xsd:date)
  Annotation(dcterms:creator ORCID:1111-2222-3333-4444)
  Annotation(kgcl:has_nondirect_replacement EX:5678)
  Annotation(kgcl:has_nondirect_replacement EX:6789)
  kgcl:PendingChange EX:1234 kgcl:NodeObsoletion)

This allows me to SPARQL for all pending changes at once.

I dont know about anonymous individuals but my guess is we will have some OBO format issues with that.

Definitely. Though to be honest I don’t care that much about that. People who want to be able to use new features such as this one should be ready and willing to let go of old stuff like the OBO format (or be willing to invest the time to make the format evolve – and at the moment you say that, suddenly there’s nobody around anymore).
If we can store “provisional changes“ in such a way that they can be preserved in the OBO format, that’s good, but if we can’t, I’ll just shrug. “Yeah, it won’t work in OBO. What did you expect? We can’t keep retrofitting new stuff into an old format.”

FWIW, my favourite is D

Good, because that’s we currently have in KGCL-Java. :) Modulo two things:

the creator of a change is not recorded yet (no dcterms:creator annotation);
we record the date and time of change, instead of just the date (Annotation(dc:terms:date "2024-02-14T13:45:12Z"^^xsd:dateTime)) – that’s because xsd:date is not a built-in OWL2 datatype, only xsd:dateTime is, so it’s easier that way.

This allows me to SPARQL for all pending changes at once.

Yeap, that’s was the idea behind this form.
I also think it is shown nicely in Protégé:

and not badly in OBO format:
property_value: https://w3id.org/kgcl/PendingChange https://w3id.org/kgcl/NodeObsoletion {http://purl.org/dc/terms/date="2024-02-22T14:43:00Z", http://w3id.org/kgcl/has_direct_replacement="CL:0000029"}

I don't think OBO Format limitations are relevant for this. Regardless of
expressivity, can keep using OBO format (sorry), and just store these in a
separate imported .owl file, we have this pattern for a lot of ontologies.

Message ID: @.***>

Regardless of expressivity, can keep using OBO format (sorry), and just store these in a
separate imported .owl file

Right. I can add a --write-to option or similar to the apply command to write the new axioms to a separate file rather than merging them into the output ontology.

It seems we are tending towards (D) and it is quite a practical solution.
However, I want to fully articulate my original idea of a direct representation. Every instance in KGCL can be represented either is the KGCL DSL, or as a standard linkml serialization of the underlying data
Class: NodeRename
Command: rename GO:0005635 from 'nuclear envelope' to 'foo bar'
YAML:
id: CHANGE:001
type: NodeRename
old_value: nuclear envelope
new_value: foo bar
about_node: GO:0005635
about_node_representation: curie

Turtle:
@prefix CHANGE: <http://example.org/> .
@prefix GO: <http://purl.obolibrary.org/obo/GO_> .
@prefix kgcl: <http://w3id.org/kgcl/> .

CHANGE:001 kgcl:about_node GO:0005635 ;
    kgcl:about_node_representation "curie" ;
    kgcl:new_value "foo bar" ;
    kgcl:old_value "nuclear envelope" ;
    rdf:type kgcl:NodeRename .

I think the most elegant and long-term maintainable approach is to use this direct RDF form, augmented with standard vocabularies to represent things such as pending status (see for example https://www.w3.org/TR/vocab-dcat-3/#life-cycle). E.g
CHANGE:001 kgcl:about_node GO:0005635 ;
    kgcl:about_node_representation "curie" ;
    kgcl:new_value "foo bar" ;
    kgcl:old_value "nuclear envelope" ;
    rdf:type kgcl:NodeRename .
    pav:status ISO19115:pending .
    dcterms:creator orcid:...,
    dcterms:date ...,
    rdfs:seeAlso <github url for discussion>

It involves no new mappings, no new annotation properties. Semantically and entailment-wise it behaves entirely as expected. I can query for NodeChanges and get all asserted instances of subclasses of NodeChange. There is no need to develop new sparql queries to check for things such as accidental use of annotation properties. For example, if I accidentally make triples such as:
CHANGE:001 kgcl:about_node GO:0005635 ;
    kgcl:about_node_representation "curie" ;
    kgcl:new_value "foo bar" ;
    kgcl:new_value "foo baz" ;
    kgcl:old_value "nuclear envelope" ;
    rdf:type kgcl:NodeRename .

Then existing mechanisms will flag this.
The existing triples could be loaded into massive triplestore of all changes in all obo ontologies, with powerful querying over the direct representation, using the standard kgcl vocabulary.
While I think this is elegant, clean, the correct way to do it, and the approach with the best long term maintainability and minimal cognitive overhead, I also reluctantly accept that this way also has some short term downsides due to our OWL stacks making various assumptions about individuals, and how confused people get by punning in OWL. While I think these problems are solvable, I don't have an immediate answer to how to resource fixing them.
So I am likely to accept mapping all triples (including rdf:type) to annotation properties.  But I wanted to make sure the full proposal was given due consideration.

We are not tending towards anything.
I implemented (D) only for a small subset of changes (2 or 3, I don’t even remember), so that we can test how it works. It’s not set in stone.
For now, my main concern with this whole idea is that it seems to be nothing more than a discussion between the two of us. I have yet to see any hint that other people are interested, which gives me very little motivation to go any further, in any direction.

Just an aside for @gouttegd:

When ODK was created, no one cared and talked, now 100+ repos.
When SSSOM was created, some people were interested, no one talked. Now rolled out in many projects (many of the discussions there are still just between you and me! Remember https://github.com/mapping-commons/sssom/issues/328)

KGCL is a complex issue, and this particular feature here even more so; I would not expect any specific input until people notice how your proposal will affect their files and tools..

@gouttegd I know I speak for many when I express how grateful we are that you do so much work for KGCL, Uberon and other projects on your own time. I totally get wanting to get confirmation that something will be useful before pouring time into it. After all, if you're not paid for your work on a project, the main reward you get is when people use (and, even better, build on) what you've written.
I will also note that it's really hard to get feedback from people about ideas. I don't know how many times I asked potential users whether they wanted the UI to work this way or that way and got basically no response, and then when I pushed out a release, people were all like, "Oh, not THAT way." 🙄

I myself have almost zero use for KGCL. And certainly zero use at all for the “storing provisional changes in the ontology” feature. So without any hint that the feature is going to be useful for someone, I am unlikely to do anything more than what I did so far. I’d much rather spend my free time working on SSSOM, which I do use and for which I have (too many) ideas of things to improve.

@gouttegd I can't argue with that :) I see it the same, and I personally divide my time across things by the same measure! Too many construction sites, too few people to stem the tide.

you do so much work for KGCL, Uberon and other projects on your own time.

The work I do for Uberon and CL is on my paid time. :) Part of my remit is basically ”anything that can make cross-species scRNAseq studies easier to do”, so contributing to cross-species ontologies fits without a doubt.
(And I suppose I could argue that, because KGCL is being used on Uberon and CL, it could also be shoehorned into that remit, but I believe this is too far-fetched.)
Anyway, sorry for the off-topic. Back to KGCL provisional changes!


[BUG] [UI] Harvester extension not working

Describe the bug

The UI extension shows error when installed from a CI built package:

To Reproduce
Steps to reproduce the behavior:

Install Harvester v1.0.1
Click on a Harvester clusters

Additional context

The error's origin (see #36 ) is the pkg/harvester/models/harvester/schema.js file.
The bug can't be replicated running the extension locally, only by prod build installation.

Related issue https://github.com/rancher/dashboard/issues/12634


[Question] how to post file with pb (bash script)

I had tried -f option:
pb p -f filename.sh
But it throws error:
redundant arguments '--'

There should be some bug in pb script. Before the bug is fixed, you can use pb p filename.sh to post file.

There should be some bug in pb script. Before the bug is fixed, you can use pb p filename.sh to post file.

Thanks, it works. Will wait for the fir 👍👍


Allow Orderable models to be reordered from modeladmin's IndexView (Recreated)

Replaces PR #3065

I will keep this branch alive in my fork for reference, but am closing this PR due to it becoming stale. Will recreate at a later date.


Loading Issue

Hi All, so everytime I try to upgrade the software from HACS, I get the following error and have to roll back to the previous version I was on.  Can anyone help with this?
subaru
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/subaru/init.py", line 102, in async_setup_entry
vehicles[vin] = _get_vehicle_info(controller, vin)
File "/config/custom_components/subaru/init.py", line 220, in _get_vehicle_info
VEHICLE_API_GEN: controller.get_api_gen(vin),
File "/usr/local/lib/python3.10/site-packages/subarulink/controller.py", line 362, in get_api_gen
_LOGGER.debug("Getting vehicle API gen %s:%s", vin, result)
UnboundLocalError: local variable 'result' referenced before assignment

0.7.4 should fix that particular bug, although I'm curious as to why the subaru API is not reporting an API generation for this vehicle (the expected value of result in the traceback pasted above). Do you have an older vehicle on your account that doesn't have a starlink subscription?

Thank you!  Best news I've got all day on a fix for this.  And yes, I have 2 vehicles on my account.  My 2019 WRX does not have a starlink subscription, but my 2020 Ascent does have the subscription.  Hopefully that helps!


Unexpected server response (0) while retrieving PDF

I'm seeing this error after uploading PDFs to Amazon S3 w/ Paperclip. The PDF is there, and I'm able to access it fine by putting the URL into the address bar, but PDF.js just doesn't like it?
Unexpected server response (0) while retrieving PDF

also having the same problem, any solutions ?


pressing "Q" doesn't delete the item

when pressing Q on observers, item shouldn't drop(and it doesnt!), but it should get deleted from the inventory (and it doesn't)

Maybe this can be by a fail on your server, also provide a cardinal version using /cardinal -v on your server.

Had you checked the XML that states it should be removed?

what i mean is that it stays on the inventory, and it doesnt get deleted

what currently happens if your drop an item in observers?

@CaptainElliott Event is cancelled and nothing happens.

Will fix when I wake up

This seems to occurs again, hope it gets fixed.


Dockerise

Solved by https://github.com/ecss-soton/verify-bot/commit/c0ad498bfd6ce32f7b80d59c76c522846f5c26b4


find macaulay record numbers in any digital archive

https://www.macaulaylibrary.org/the-internet-bird-collection-the-macaulay-library/
https://search.macaulaylibrary.org/catalog
https://macaulaylibrary.org/asset/247284851
Specifically the ML numbers.
e.g., The Macaulay Librar at the Cornell Lab of Ornithology	ML22623131
Trying to cross-reference records in own records.

structure data available via https://macaulaylibrary.org/asset/247284851.json .
{
  "specimenUrl": "https://macaulaylibrary.org/asset/247284851",
  "obsTime": "8:00 AM",
  "illustratedChecklistUrl": "https://ebird.org/hotspot/L1497619/media",
  "searchByLocationUrl": "https://search.macaulaylibrary.org/catalog?searchField=hotspot&hotspotCode=L1497619",
  "recordist2Id": null,
  "obsDttmISO": "2020-04-26T08:00:00",
  "digitizeDt": null,
  "catalogDt": null,
  "primaryAgeSexCount": {
    "age": "adult",
    "sex": "male",
    "count": -1,
    "localizedString": "Adult Male",
    "localizedAgeString": "Adult",
    "localizedSexString": "Male"
  },
  "recordist2DisplayName": null,
  "userIsAssetOwner": false,
  "recordist2ProfileUrl": null,
  "mediaEditDt": null,
  "backgroundSubjectData": [],
  "catalogUserDisplayName": null,
  "digitizeUserDisplayName": null,
  "mediaEditUserDisplayName": null,
  "isInternalUser": false,
  "longitude": -123.1167,
  "latitude": 49.3426,
  "subjectData": [
    {
      "speciesCode": "btywar",
      "sciName": "Setophaga nigrescens",
      "comName": "Black-throated Gray Warbler",
      "ageSexCounts": [
        {
          "age": "adult",
          "sex": "male",
          "count": -1,
          "localizedString": "Adult Male",
          "localizedAgeString": "Adult",
          "localizedSexString": "Male"
        }
      ],
      "subjectTags": {
        "behaviors": [
          {
            "key": "flying_flight",
            "localizedString": "Flying"
          },
          {
            "key": "foraging_eating",
            "localizedString": "Foraging or Eating"
          },
          {
            "key": "vocalizing",
            "localizedString": "Vocalizing"
          }
        ]
      }
    }
  ],
  "previewUrl": "https://cdn.download.ams.birds.cornell.edu/api/v1/asset/247284851/",
  "largeUrl": "https://cdn.download.ams.birds.cornell.edu/api/v1/asset/247284851/1200",
  "mediaUrl": "https://cdn.download.ams.birds.cornell.edu/api/v1/asset/247284851/1200",
  "thumbnailUrl": "https://macaulaylibrary.org/static/blank-placeholder.png",
  "mediaWidth": 4000,
  "mediaFileSize": 10512,
  "mediaHeight": 2611,
  "licenseType": "Any Lab Use=eBird",
  "userId": "USER277011",
  "location": "Capilano Canyon, Metro Vancouver, British Columbia, Canada",
  "locationLine2": "Metro Vancouver, British Columbia, Canada",
  "captive": "",
  "mediaType": "Photo",
  "recorder": null,
  "source": "ebird",
  "userDisplayName": "mark daly",
  "assetState": "committed",
  "commonName": "Black-throated Gray Warbler",
  "sciName": "Setophaga nigrescens",
  "mediaDownloadUrl": "https://cdn.download.ams.birds.cornell.edu/api/v1/asset/",
  "eBirdChecklistId": "S71098987",
  "comments": "https://natureasart.photoshelter.com",
  "obsComments": null,
  "userProfileUrl": "https://ebird.org/profile/Mjc3MDEx",
  "ebirdSpeciesUrl": "https://ebird.org/species/btywar",
  "locationLine1": "Capilano Canyon",
  "collected": false,
  "eBirdChecklistUrl": "https://ebird.org/view/checklist/S71098987",
  "assetTags": null,
  "specimenIds": null,
  "assetRelateds": [],
  "homeArchive": null,
  "exifData": {
    "exposure_time": "1/125 sec",
    "f_number": "f/5.6",
    "focal_length": "400 mm",
    "iso": "800",
    "mime_type": "image/jpeg",
    "width": "4000 pixels",
    "create_dt": "2020:04:26 19:07:16",
    "model": "Canon EOS 90D",
    "shutter_speed": "1/124 sec",
    "make": "Canon",
    "height": "2611 pixels",
    "flash": "Flash did not fire"
  },
  "reportAs": "btywar",
  "ratingCount": "9",
  "width": 4000,
  "height": 2611,
  "valid": true,
  "speciesCode": "btywar",
  "rating": "4.888888888888889",
  "microphone": null,
  "obsDttm": "26 Apr 2020",
  "assetId": 247284851,
  "accessories": null
}

@jhpoelen -> the data I was trying to double check was in this:
"obsDttmISO": "2020-04-26T08:00:00",
That should be the date that the picture was taken.


[support] show-cf-memory-usage: Link to memory graph

What
Make it easier for people to know what they should compare the "memory
required" number against. I've previously run the script but not verified
whether we are meeting ADR017 because it was too much effort to look.
The link shows a sum of all cells by environment. I was going to hardcode it
to bosh-deployment:prod since that's the environment that we most often
add orgs and cells to, but the script can be used against any environment.
How to review

Checkout the branch
Run make show-cf-memory-usage
Click the link and verify that it shows useful information

Who can review
Not @dcarley

Closing while I rework.


Need to be able to capture Dev Tools Console to log file

CSS needs to be able to capture the Developer Tools Console output to a log file

@kburtram with the logging support as currently implemented we already have the logs being sent to log file for backend service. Should we continue to track this item for UI logs to files?

Closing based on previous improvements to logging support.


[MI-2602] Added the logic to DM the user if his email doesn't match with ServiceNow user

Added a new unit test to cover the new code

this issue is solved in PR https://github.com/Brightscout/mattermost-plugin-servicenow/pull/43


VS Code Suggestion dontt work when pressing ctrl+space

Type: Bug
it shows 3 weird suggestion, and i think it happened after i installed a deprecated html snippets extension by Mohamed Abusaid.
i reinstalled vs code, installed vscode insiders, delete all file related to vscode.
i tried everything but the problem still persist.
can someone help me plz.

VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz (6 x 3000)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.90GB (1.92GB free)

Process Argv
--crash-reporter-id ebd8c564-2875-49c5-8d88-37db88f1f076

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
3biah626:30602489
f6dab269:30613381
2i9eh265:30646982
showlangstatbar:30737416
0bi6i642:30823812
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofb:30804716
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv1:30821571

Please diagnose the root cause of the issue by running the command F1 > Help: Troubleshoot Issue and following the instructions. Once you have done that, please update the issue with the results.
Happy Coding!

I've run it and the problem is still here

@jriekenany solution? i didnt get an answer 2 weeks ago.

ftfcuisz

Works for me and million other users. Please try to extract a minimal reproducible case and setup up.

Try

F1 > Disable All Installed Extensions
F1 > Create Profile > EMPTY profile

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

#186120
I am also accustomed to using the 'ctrl+space' shortcut keys in my daily life, rather than 'enter' and the like.
Unfortunately, after a certain version update in May or June, the 'ctrl+space' custom shortcut settings in certain places no longer work, such as:
*In the command bar
*In the code suggestion column
If you still want these 'ctrl+space' shortcut settings to work, the only way currently is to download the old version of vscode and prohibit its updates.


Create unique key via REST API

I'm trying to create our CosmosDB configuration via scripts that call the REST API. To create collections I'm following the documentation here, however it doesn't mention anything about how to specify unique keys.
Is there currently an undocumented way to do this?

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

ID: f928ddcf-4a56-4e7b-4ac4-bc897975dbef
Version Independent ID: 4854ec57-dd3f-f894-10c2-b1ce5ea21fa1
Content: Define unique keys for an Azure Cosmos container
Content Source: articles/cosmos-db/how-to-define-unique-keys.md
Service: cosmos-db
GitHub Login: @ThomasWeiss
Microsoft Alias: thweiss

@ctoph13 Thank you for bringing this to our attention. The best course of action is to reach out to the Product Group directly at AskCosmosDB. In my investigation, Unique Keys are not exposed via the REST API as they augment the defined Partition Key for a given collection and are part of the service layer, not a specific collection property. @ThomasWeiss @SnehaGunda for awareness and additional input.

I reached out to AskCosmosDB as suggested and they provided me with a helpful answer:
using DocumentDB Studio you can click a collection to see the JSON that it's made up from. within this JSON is the uniqueKeyPolicy property that i needed to append to my JSON body within my request body on the REST API.
my old JSON body was:
{
	"id": "SomeCollection",
	"partitionKey": {
		"paths": ["/somePartitionKey"],
		"kind": "Hash"
	}
}

and my new, working JSON body is:
{
	"id": "SomeCollection",
	"partitionKey": {
		"paths": ["/somePartitionKey"],
		"kind": "Hash"
	},
	"uniqueKeyPolicy": {
		"uniqueKeys": [{
			"paths": ["/someCompositeUniqueKey1",
			"/someCompositeUniqueKey2"]
		}]
	}
}

thanks for the help!

@ctoph13 Thank you so much for following up and posting the solution, as it will be very helpful to those looking for the same or similar solution.

Could you please add this to the official document? This is especially relevant if you are using ARM templates to set the unique key policies and I havent found any kind of official documentation regarding that.

@florianeidner We're actually in the process of updating our ARM templates samples to include unique key policies, so this should land in the near future. Thanks!


Hello, I find a bug when i use softpool2d.

RuntimeError: input.is_contiguous() INTERNAL ASSERT FAILED at "/export/w/SoftPool/pytorch/CUDA/softpool_cuda.cpp":120, please report a bug to PyTorch. input must be a contiguous tensor

Hi @KeqiWangSXuniversity,
This question has been answered in previous issues #6  and #16.
It just means that the tensor that you're passing as an argument does not occupy a contiguous memory space. You can use .contiguous() alongside the function call, although most recent repo versions do internal checks.
Best,
Alex


Update AMI with JDK7

By having a robust universal installation method, our AMIs will be deprecated.  See #302.


Data Viewer window error

Good day,
In version 4.0 getting the Error, "Oops! Something went wrong". The error appears when you close the Data Viewer window but not all the time.
JWLManager v4.0.0
Windows-10-10.0.19045-SP0

Traceback (most recent call last):
  File "JWLManager.py", line 1871, in data_viewer
RuntimeError: Internal C++ object (DataViewer) already deleted.

Hopefully resolved by 5ffb643170491b37d7e82365f0db7a7aab6afe70 in v4.0.1
Please confirm.

Yes, it appears to be resolved. For reference, I believe the crash occurred for notes not linked to a publication.


Reintegration of the Blade Feather Icons package

Hi Dries,
This PR will reactivate the blade feather icons package that was being used on earlier Blade UI kit versions.
The benefit is that the users will have a higher set of icons to choose from, specifically from this feather icons ui kit that is amazing.
Let me know if there is anything missing.
Thank you,
Bruno

Thanks @brunocfalcao


Save state on localStorage

Related issues:
resolves https://github.com/dawnlabs/carbon/issues/26
Features:

Add setter of localStorage on componentDidUpdate
Sync layout props on componentDidMount

Hey @fernahh looks good but sorry we just closed this issue! Really appreciate the effort and video 👍


Output file blank in Pages (Mac) and Google Documents

Wonderful library. I don't know if this is really an issue of html-docx-js, but I've tried both online demo and node.js version. Works fine with Word Online and MS Word for Windows but I get a blank sheet when opening the generated file with Pages or Google Documents.
Is this perhaps using a different format than the standard one?

Unfortunately, the mechanism that we use is only supported by Microsoft Word at the moment. It is written in README.md, although we will make it more prominent and also mention incompatibility with Pages.


Core namespace

@mphammer  Thanks for the PR.
It looks good to me. The commit message of the first message core-secret files doesn't make sense though. Could you please change that to reflect the namespace changes or add a message explaining it.


"window.restoreWindows": "none" incorrect

Issue Type: Bug
Restore Windows

Never reopen a window. Always start with an empty one.

This is incorrect.
I had a hot session with unsaved changes in the past. It required other people, so I haven't gone back to that project in a long time.
After the latest update to 1.43.0, that session now launches whenever I run VS Code.
The window.restoreWindows setting is none, but instead of restoring none windows, it's restoring this old session.
But, because some of the files are still being edited (which I can't complete without other people (who are busy)), I don't want to work on this old project now. I'd like it to have the previous (seemingly intended) behavior of NOT opening any projects.
Hot Exit
Now, if "files.hotExit": "onExitAndWindowClose" instead of the default onExit, it goes back to the previous behavior. If I launch VS Code, even though a hot session exists, it doesn't restore it on launch.
So it seems that the capability to restore NONE windows sure exists. So why isn't restoreWindows=none always respected?
tl;dr
restoreWindows=none is only respected if a different setting is changed from default.
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:47:57.235Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4600M CPU @ 2.90GHz (4 x 2893)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (3.69GB free)

Process Argv

Screen Reader
no

VM
0%

Related to #92467


[FLINK-35044][state] Init flink-statebackend-forst module

What is the purpose of the change
A simple work to introduce a new module for ForStStateBackend, then several subsequent PR e.g. ForStFileSystem, Implementation of Async API, ForStStateBackend could be commited/reviewed in parallel based on it.
See FLIP-427 for more details.
Brief change log

Init flink-statebackend-forst module with necessary dependencies

Verifying this change
This change is a trivial work to introduce a new module without tests coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@flinkbot run azure


runc.v1 and runc.v2 are reparented to pid 1.

The actual runc.v1 and runc.v2 processes are spawned by shim start process (subreaper).
And after started, shim start exits, the actual shim process will be reparented to pid 1.
Is this what we want?
With runc.v1:
systemd─┬─NetworkManager─┬─dhclient
        │                ├─dnsmasq
        │                └─2*[{NetworkManager}]
...
        ├─containerd-shim─┬─pause
        │                 └─10*[{containerd-shim}]
...
        ├─sshd─┬─sshd───sshd───bash─┬─sudo───containerd───23*[{containerd}]

With shim v1:
systemd─┬─NetworkManager─┬─dhclient
        │                ├─dnsmasq
        │                └─2*[{NetworkManager}]
...
        ├─sshd─┬─sshd───sshd───bash─┬─sudo───containerd─┬─containerd-shim─┬─pause
        │      │                    │                   │                 └─9*[{containerd-shim}]
        │      │                    │                   └─23*[{containerd}]

/cc @crosbymichael

Yes, this is how it should work.  We want to decouple and reparent as shims should survive when containerd goes down.


UI: Add option to close Error toast manually along with auto disappear.

PR #171 merged - closing


Using Hapijs

Hey there!
Love this project, but just want to know, want do I need to change if I want to use Hapi rather than express? I would like to use hapijs universal routing.

Closing as Inactive for more than 3 months!


Add I18n support

Setup the ability to switch languages and let people contribute translations.
see: scout-app.io

Hi, I am a freelance translator since 11 years old. I have already translated an app in 9 languages and revised more than other 3 languages (Georgian and Greek).
I use Angular, PHP and JSON to translate quickly the sites into 9 languages and still studying Georgian and Greek to translate. I have already built my client's site in PHP and translated quickly, using PHP, into 9 languages.

@gusbemacbe
I've set up a Google Sheet for translation. I may still need to add some keys/text to it for translation. But it's a start.

https://docs.google.com/spreadsheets/d/1JeQuEyA4hFLI3sk3-heG-cG5eomFBUD5Co4i6H6YEAs/edit?usp=sharing

Work that needs to be done for this feature:

Update all strings and add any new keywords to the Google Sheet.
Google translate all keys for at least one language so we can test switching between English and it. Feel free to steal any relevant translations from Scout-App.
Create a cultures.js Node script that automates downloading a CSV version of the Google Sheet and converts it over to the JSON dictionary the app needs. (See Scout-App's cultures.js).
Add the above script to the package.json scripts section as cultures. So we can just run npm run cultures to update the dictionary file with the latest translations.
Update the dictionary.json using the automated script to have at least two translations.
Implement the vue-i18n library and hook up the dictionary. See this example.
Replace all strings of text with their keywords using vue-i18n.

We could use Transifex or another service and provide po/pot files.

@DanielRuf
I've looked into them (and others) previously. It's a good system, however the process to get open source status took too much effort and ultimately it just adds hurdles in the way of people that would volunteer to translate. Scout-App has been translated to 26 languages and I think it's because of the ease of access to being able to just do the translations in Google Sheets with as few barriers to entry as possible.
The downside is that each language only has one version of a string, meaning the translator has to make decisions about edge cases in their language. But I've never gotten any complaints about that before.
For now, I'd prefer to just use Google Sheets and a Node script to automate machine translations and converting to usable JSON for vue-i18n.

True. Is there a translation template which can be used?


Use krun bash script directly for kevm interpret

This uses the krun bash script directly instead of the low-level handling we were doing to invoke interpreter instead.

Remove kevm interpret --backend java ... support (can still use kevm run ... there).
Correct the way that --unparse and --no-unparse are handled (did not work before, now will default to --unparse for anything except kevm interpret command, and to --no-unparse for kevm interpret command).
Adjust kevm interpret to call krun bash runner script directly, instead of bypassing it an invoking interpreter.
Refactor resulting (now simpler) code for kevm interpret ....

Performance measurements:

Fastest tests on LLVM backend (before): 30ms
Introduced time on LLVM backend: +50ms
LLVM backend Test-suite overall slowdown (make test-conformance -j20 TEST_CONCRETE_BACKEND=llvm): 1.44X
Fastest tests on Haskell backend (before): 15s
Reduced time on Haskell backend: -7s
Haskell backend test-suite overall speedup (make test-vm -j12 TEST_CONCRETE_BACKEND=haskell): 0.48X

make test-vm TEST_CONCRETE_BACKEND=haskell --dry-run produces the following command which throws an error on my machine.
kevm interpret tests/ethereum-tests/LegacyTests/Constantinople/VMTests/vmBitwiseLogicOperation/sgt2.json  --backend haskell --mode VMTESTS --schedule DEFAULT --chainid 1

Created bug report: kore-exec.tar.gz
[Error] krun: Backend crashed during rewriting with exit code 1
[Error] Critical: Parse error
 (ParseError: ERROR: Unexpected end of file while parsing)

Adding -haskell-backend-arg --smt=none seems to work:
kevm interpret tests/ethereum-tests/LegacyTests/Constantinople/VMTests/vmBitwiseLogicOperation/sgt2.json  --backend haskell --mode VMTESTS --schedule DEFAULT --chainid 1 --haskell-backend-arg --smt=none

I'm going to fix @RaoulSchaffranek 's issue first, and yes, I want it working on your machine first. It should always work on your machine (all the downstream semantics should).
The issue you're having is you're executing the ./kevm script in the root of the repo, and you should be executing the installed one at .build/usr/bin/kevm instead.

@RaoulSchaffranek your issue with the haskell backend should be fixed now, at least it should error with this warning now:
<kevm>
  <k>
    project:EthereumSimulation ( { "sgt2" : { "_info" : { "comment" : "" , "filledwith" : "testeth 1.8.0-6+commit.c7ba3b69" , "lllcversion" : "Version: 0.5.14-develop.2019.11.27+commit.8f259595.Linux.g++" , "source" : "src/VMTestsFiller/vmBitwiseLogicOperation/sgt2Filler.js
on" , "sourceHash" : "bb81e3b79fbad22504061aa4955a2dd54b0a04669c75f126fd473015fd340d08" , .JSONs } , "callcreates" : [ .JSONs ] , "env" : { "currentCoinbase" : "0x2adc25665018aa1fe0e6bc666dac8fc2697ff9ba" , "currentDifficulty" : "0x020000" , "currentGasLimit" : "0x7ffffffff
fffffff" , "currentNumber" : "0x01" , "currentTimestamp" : "0x03e8" , .JSONs } , "exec" : { "address" : "0x0f572e5295c57f15886f9b263e2f6d2d6c7b5ec6" , "caller" : "0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b" , "code" : "0x60007ffffffffffffffffffffffffffffffffffffffffffffffff
fffffffffffffffff1360005500" , "data" : "0x" , "gas" : "0x0186a0" , "gasPrice" : "0x0c" , "origin" : "0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b" , "value" : "0x0b" , .JSONs } , "gas" : "0x01730c" , "logs" : "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d4934
7" , "out" : "0x" , "post" : { "0x0f572e5295c57f15886f9b263e2f6d2d6c7b5ec6" : { "balance" : "0xd3c21bcecceda1000000" , "code" : "0x60007fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff1360005500" , "nonce" : "0x00" , "storage" : { .JSONs } , .JSONs } , .JSO
Ns } , "pre" : { "0x0f572e5295c57f15886f9b263e2f6d2d6c7b5ec6" : { "balance" : "0xd3c21bcecceda1000000" , "code" : "0x60007fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff1360005500" , "nonce" : "0x00" , "storage" : { .JSONs } , .JSONs } , .JSONs } , .JSONs
} , .JSONs } ~> . ) ~> .
  </k>
  <exit-code>
    1
  </exit-code>
  <mode>
    VMTESTS
  </mode>
  <schedule>
    DEFAULT
  </schedule>
  <ethereum>
    <evm>
      <output>
        b""
      </output>
      <statusCode>
...

To get it to make further progress on the Haskell backend (not needed for LLVM backend), you need to apply this patch: https://github.com/runtimeverification/evm-semantics/issues/1291

Sounds good! Yes, that's how it's supposed to be. We don't include the driver.md on Haskell backend by default, because we don't care to include it in proofs (it's just for running general-state-tests conformance test-suite).

@ehildenb those instructions worked.
the evm-semantics repo could use a bit of a restructuring.
Having separate folders for /src and /scripts could make things look a lot more organized.


feat: Adapt to the current timezone.

Clear and concise description of the problem
When using the Valaxy VSCode plugin preview, I noticed that the article's time is in the UTC Time. It may be necessary to adapt it to the localization of the time zone.
Suggested solution
I believe you can solve it.
Alternative
No response
Additional context
No response
Validations

[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Yes, the default time zone is utc +0, so I use +8 manually
---
date: 2022-04-09 +8
---

---
date: 2023-04-09 08:00:00 +8
---

wow,that‘s a useful tip,it works.

Maybe we need add a config for timezone?

timezone had been added in siteConfig. Released in v0.14.32.


Euchre game setup bugs

Max score defaults to 100 instead of 10 - see https://github.com/johnameyer/cards-ts/blob/1e99dc7831a28e514344c527d670dd71a4260382/packages/euchre/src/game-setup.ts#L20, and the "end round early" functionality does nothing.

Resolved with #111


Added Test Framework

This is an attempt for standardization. We see different solutions for testing everywhere. We also see different naming everywhere. Some solutions even use dependencies (or why is there a node_modules ignore rule?). Most coding challenges out there are using a simple I/O approach, we should too. I think that we need to extend our contributor guides and also add some rules there:

Single file called solution.$ext (where $ext is the official extension of the programming language).
No dependencies except those included in the latest version of the language. (What about weird languages like C that have super inconsistent standard libraries across systems?)
No error handling, input is always valid and present.

The last point might be problematic because there are problems for which it would be great to have negative tests to ensure that people actually understood the problem, e.g. #113.

Looks great!
I really like that the test environment is language-agnostic similar to Google Code Jam and others.
Shall we add a note to CONTRIBUTING.md or the README.md that describes the test setup for newcomers?
Also, are you planning to add the test run to CI, perhaps with Github Actions?
This can of course be done in a separate commit.
Keep it up!

I thought about CI but this could take ages to complete.

Let's get your changes merged and create an issue to tackle CI later.


Testing documentation issue template

Documentation Related To Component:

No particular component, I'm just weird.
Please check those that apply

[x] typo
[ ] documentation doesn't exist
[ ] documentation needs clarification
[ ] error(s) in example
[ ] needs example

Description Of The Issue

I was just testing this

Wee!


Adds brooklyn-rest-client feature

@neykov can you take a look please?
Useful for any downstream projects that depend on brooklyn-rest-client and that want to run in Karaf.

@neykov thanks for the great comments! I'm made those changes and confirmed it works in a downstream project.
For the javax.annotation bundle, I now get version 1.2 already present in Karaf 4.0.4:
bundle:list -t 0 | grep -i annot
 27 | Active   | 100 | 2.4.5                    | Jackson-annotations
 33 | Active   |  80 | 2.4.5                    | Jackson-module-JAXB-annotations
 65 | Active   |  80 | 1.5.6                    | swagger-annotations
 69 | Active   |  10 | 1.2                      | javax.annotation API

Are you happy with merging this now?

Looks great, merging.


dataset training

Since the dataset is too large, if I want to use part of the dataset for training, where should I set it up?

For most simple case, hard code on mmdet3d.
https://github.com/open-mmlab/mmdetection3d/blob/f1107977dfd26155fc1f83779ee6535d2468f449/mmdet3d/datasets/custom_3d.py#L64C12-L64C12
for example, sub sample to 1/5.
From
self.data_infos = self.load_annotations(self.ann_file)
to
self.data_infos = self.load_annotations(self.ann_file)[::5]
For more reasonable way, check here:
https://github.com/fundamentalvision/BEVFormer/blob/32b65ffd2a85c35b5f74b753f23ef34f9a85a576/projects/mmdet3d_plugin/datasets/nuscenes_dataset_v2.py#L18
add line:
self.data_infos  = self.data_infos[::5]
maybe modify more variable
Or, construct a new dataset called nuscenes-subset

For most simple case, hard code on mmdet3d. https://github.com/open-mmlab/mmdetection3d/blob/f1107977dfd26155fc1f83779ee6535d2468f449/mmdet3d/datasets/custom_3d.py#L64C12-L64C12 for example, sub sample to 1/5. From self.data_infos = self.load_annotations(self.ann_file) to self.data_infos = self.load_annotations(self.ann_file)[::5]
For more reasonable way, check here:
https://github.com/fundamentalvision/BEVFormer/blob/32b65ffd2a85c35b5f74b753f23ef34f9a85a576/projects/mmdet3d_plugin/datasets/nuscenes_dataset_v2.py#L18
add line:
self.data_infos = self.data_infos[::5]
maybe modify more variable
Or, construct a new dataset called nuscenes-subset

Thank you for your suggestion. Now, when slicing the mini dataset, I will change the 64th line of BEVFormer/mmdeletion3d/mmdet3d/datasets/custom_1d. py from # self. data_infos=self. loaduannotations (self. annunfile) to
After self. data_infos=self. loadannotations (self. annunfile) [:: 5], the training time remains the same as before it was modified.
Meanwhile, if I am in line 26 of BEVFormer/projects/mmdet3d_plugin/datasets/nuscenes_dataset. py, that is, super()__ After init__ (* args, * * kwargs), add self. data_infos=self. data_infos [:: 5], and it is found that the training time has not changed. May I ask what is the reason for this

Looking forward to your answer


Substitue getters and setters are Lowercase

for example if your class has a substitued field called feature the getter and setter for the field is getfeature and setfeature, instead of getFeature/setFeature

Are you able to create a simple test case for this scenario? I vaguely remember that I only transfer the element info throughout the post processing so whatever XJC spits out as bean property name would be driven by whatever is configured in your binding context.

I seemingly fixed the issue: I created a pull request.


Promote release-service from staging to production

Included PRs:

https://github.com/redhat-appstudio/release-service/pull/380
https://github.com/redhat-appstudio/release-service/pull/385
https://github.com/redhat-appstudio/release-service/pull/381
https://github.com/redhat-appstudio/release-service/pull/313
https://github.com/redhat-appstudio/release-service/pull/379

/hold
so it doesn't merge before I am online, just in case

/retest-required

/unhold

/lgtm


regarding adopting the code to fit my own dataset

Hi aurora95,
Thanks for sharing the code.
I am planning to adopt your code to training my own data set. The training images are of size 500*700, and each of which is black-and-white, i.e., with only one single channel. What kind of modifications have to be made to make your code fitful for my data set? Thanks a lot.
Wenouyang

The changes wouldn't be too difficult, just try it and add minor fixes when 3 channels are expected but there is only one. If you don't want to spend time on those bugfixes the shortcut would be to simply repeat your 1 channel image 3 times, if RGB are all equal then you've still got a grayscale image.

Oh and the pretrained weight transfer from imagenet would likely not "just work" on a 1 channel image.


ARXML: always pretend to be version 4.0 for AR4

For some reason, all AR 4 revisions always use "http://autosar.org/schema/r4.0" as their XML namespace. To find out the exact AUTOSAR revision (i.e., 4.0, 4.1, 4.2, ...), the "xsi:schemaLocation" attribute of the root tag needs to be examined. Since this is pretty fragile (the used naming scheme has changed during the AR4 journey and with the latest naming scheme there seems to be no programmatic way to associate the value of schemaLocation with the AR revision), we pretend to always use AR 4.0. If incompatible changes between AR4 revisions are encountered in the future, it can be supported by implementing all posibilities and backtracking if necessary.
Andreas Lauser<EMAIL_ADDRESS>on behalf of MBition GmbH.
Provider Information

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 9 (88.89%)  changed or added relevant lines in 1 file are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.001%) to 92.959%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cantools/database/can/formats/arxml.py
8
9
88.89%

Files with Coverage Reduction
New Missed Lines
%

cantools/database/can/formats/arxml.py
8
93.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
5360

Relevant Lines:
5766

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 9 (88.89%)  changed or added relevant lines in 1 file are covered.
204 unchanged lines in 16 files lost coverage.
Overall coverage decreased (-0.2%) to 92.785%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cantools/database/can/formats/arxml.py
8
9
88.89%

Files with Coverage Reduction
New Missed Lines
%

cantools/database/diagnostics/database.py
1
93.62%

cantools/database/can/bus.py
3
81.25%

cantools/database/can/attribute.py
4
77.78%

cantools/database/can/formats/dbc.py
5
98.38%

cantools/database/can/node.py
6
76.0%

cantools/database/can/signal_group.py
6
72.0%

cantools/database/can/database.py
7
94.77%

cantools/database/can/formats/arxml.py
8
93.0%

cantools/database/diagnostics/did.py
8
75.0%

cantools/database/can/c_source.py
10
97.36%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5350

Relevant Lines:
5766

💛  - Coveralls

Maybe their strategy is to only bump the namespace on major?

possibly. I somehow doubt that there will ever be an AR5, though...

Should I "auto-merge" changes to arxml? I think you might be the most advanced user there :).

If you're happy with the code quality and coverage: sure...


Dynamic updating Card Title

I am programatically updating the Card Title, but this does not seem to impact the rendering of the Card Title? Any ideas?

I have added an example story to illustrate programmatic changes to lane and card titles. Would recommend using a library like immutability-helper to modify the data passed to the board.
Code here: https://github.com/rcdexta/react-trello/blob/master/stories/Realtime.story.js
Example here: http://rcdexta.me/react-trello/?selectedKind=React Trello&selectedStory=Realtime Events&full=0&down=0&left=1&panelRight=0
Pls pull version 1.22.1


Minor bugs and improvement requests

So whenever I watch any episode of any anime the status bar doesn't hide and you cannot hide it no matter what you do. Now it's not that much of a problem but it surely distract me. It would be great if this problem can be fixed also you cannot rotate the scree even if auto rotate is on. Hope you fix this too

Now another thing it would be great if the search tab and search section is updated. Few things that I face problems with are that I can't sort the search. If I'm searching by genre I would like to see the most popular or recently update or most rated shows so it would be great if there is sorting option and when you search any keyword the search results are in row it would be better if they are in table orientation like as in case of other platforms. (Also downloading or offline viewing feature would be great) Hope you would think about these things. And obviously thanks for what you are doing it's a great app but still requires changes.

No more features update for this app.
All suggestions will be considered for next app (external based source app)


Add warning when the node is editing a GSV that doesn not exists anymore.

Steps

create a VariableSwitch for variable X
create GSVDB node
edit the variable X in GSVDB
delete node VariableSwitch
-> the GSV is still displayed as edited in the GSVDB node

Find a way to warn that the GSV is edited but does not exist in the scene anymore.
Or even delete the edit automatically?

Implementation result on GSVDb v2.0.0-17.92


No web interface

Task List:

[X] Issue description provided
[X] Steps to reproduce provided
[ ] Stacktrace (if present) provided
[X] Screenshots (if UI related) provided
[X] Full description of the issue provided

Issue description
I have installed streams as instructed here But when I run the .war file it starts and when I try to connect to it, the page never loads. I have no tger services installed on the system. It's a fresh install of Raspbian Stretch.
Steps to Reproduce

Download and install openjdk-8-jdk
Download latest streama release via wget command.
Make it executable.
download the sample_application.yml as application.yml and place it in the same directory as the war file.
Run it by /.streama.war

Expected Behaviour
After running the .war file, web interface should be available.
Actual Behaviour
No web interface after running the .war file. But when I scanned the Pi with a network scanner, there's a service running on port 8080 but when I try to connect, the page never loads.

Environment Information

Operating System: Raspbian Stretch Lite
Streama version: 1.6.0 RC7
Custom streama build, describe customizations or provide link to fork (If Applicable): N/A
Container Version (If Applicable): N/A

Example Application / access to your live version
Not available

Also why does it require nearly 25 minutes just to start the server?

A raspberry pi is generally too low power to run Streama.
I've seen similar issues with it talking an very long time to start on other low power machines.
We generally recommend a modern CPU and 2gb ram.

@Jeronimo95 Is there any plans to support Raspberry pis in future? Because plex has changed its privacy policy, I wanted to switch to streama but ... :(

It's my understanding that grails (the framework Streama is built on) is too heavy for low end systems. If anyone has insight into this it would be appreciated.

System requirements should probably be posted in readme.md

Yeah I'm working on some new docs. System requirements will be more prominent.


Unify the name of the localization props

For instance
MobileWrapper.defaultProps = {
- okLabel: 'OK',
+ okText: 'OK',

to align with the names in https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/locale/index.js.

It was done already


v0.1.0

Tested most package functionalities. Decided to take docs out and improve README docs instead. v0.2.0 should work seamlessly with SymbolicRegression.

Release notes:
Interface updates and coverage tests
This version contains bug fixes and improvements to documentation. Most of SymbolicRegression.jl functionality now works out of the box. The next version v0.2.0 should work seamlessly with SymbolicRegression.jl through the LaSR extension.
Landing page: https://trishullab.github.io/lasr-web/

Error while trying to register: Version 0.0.1 already exists

Error while trying to register: Version 0.0.1 already exists

Registration pull request created: JuliaRegistries/General/115719
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" bd5f0c35a7b362becd083e6f42dae09b658e4deb
git push origin v0.1.0

Registration pull request updated: JuliaRegistries/General/115719
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 0e3c4da2458573bbac1a07f54702ec19c5f59f12
git push origin v0.1.0

Merged.


TextBox.WidthCentimeters only respected if RelativeWidthPercentage set to 0

See this code:
var textBox = document.AddTextBox("My text");
textBox.HeightCentimeters = myHeight;
textBox.WidthCentimeters = myWidth;

The height and width are not respected until I set the Percentages to 0:
textBox.RelativeWidthPercentage = 0;
textBox.RelativeHeightPercentage = 0;

This was not expected. How about clearing the percentage values if the corresponding Centimeters-value is set (and perhaps vice versa)?

Ye, probably should be done. From what I saw in openxml it was clearing it or ignoring (don't remember now), so this should be improved with added tests.


Deploy Databricks Job Not found

I installed the extension in Azure DevOps today, but not able to find the task to deploy jobs. It does have the options for deploying notebooks but not jobs.

Correct the Azure DevOps tools cannot support all methods because they just have too many options.
Instead add a PowerShell task and run something like:
Install-Module azure.databricks.cicd.tools -Scope CurrentUser -Force
Import-Module azure.databricks.cicd.tools
Add-DatabricksPythonJob -BearerToken $BearerToken -Region $Region -JobName "Job1" -SparkVersion "5.3.x-scala2.11" -NodeType "Standard_D3_v2" -MinNumberOfWorkers 2 -MaxNumberOfWorkers 2 -Timeout 100 -MaxRetries 3 -ScheduleCronExpression "0 15 22 ? * *" -Timezone "UTC" -PythonPath "/Shared/TestPython.py" -PythonParameters "val1", "val2" -Libraries '{"pypi":{package:"simplejson"}}', '{"jar": "DBFS:/mylibraries/test.jar"}

Full syntax https://github.com/DataThirstLtd/azure.databricks.cicd.tools/wiki


Include blocktime

Adaption and integration of the source code from cakedefi-review for blocktime evaluation

duplicate, issue resolved in the past


Update manifest.json

Version reported is still 0.7.3. Update to current 0.8.3

Thanks, I updated it with the later versions


Fix ABI break on sdf11

🦟 Bug fix
Summary
Similar to #605, but with additional changes for the sdf11 branch. The recently added members to sdf::ElementPrivate are
explicitlySetInFile, lineNumber, and xmlPath (https://github.com/osrf/sdformat/compare/sdformat11_11.1.0...sdformat11_11.2.0)
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] Code check passed (In source directory, run sh tools/code_check.sh)
[x] All tests passed (See
test coverage)
[x] While waiting for a review on your PR, please help review
another open pull request
to support the maintainers

Note to maintainers: Remember to use Squash-Merge

@osrf-jenkins run tests, you're good to go now

I enabled the DCO bot after this PR was open. Let's merge without that check for now, reopening the PR would trigger lots of builds.


[1854] Change Recommend for QTS button to say EYTS for early years

Context
The text on the recommended for QTS button is being changed form Recommend trainee for QTS to Recommend trainee for EYTS for all early year routes.
Screenshots

Guidance to review

Navigate to a non early year trainee with a status of TRN received and ensure that the green button at the top still says Recommend trainee for QTS
Navigate to a early year trainee with a status of TRN received and ensure that the green button at the top now says Recommend trainee for EYTS

 [S] EY - Change Recommend for QTS button to say EYTS


possible to have multiple model-types for a cell?

I'm wondering if there is a way to use different model-types for a collection-view cell.
I have two types: Book and Movie. Each type has a title, and an associated image.
What I'd like to do is use the same UICollectionViewCell (let's call it GenericCell) and register it so that a different type can be used, besides the one that is defined in the cell's ModelType.
Barring that, maybe a runtime transform?... so I could see "Oh the model is a Book, so transform it to a ImageTitle object". Then the ModelType and update routine would use ImageTitle even though the object from the data-source was actually a Book or Movie or whatever.

Hi!
In this case, i would suggest you use a protocol to define common properties, for example
protocol Content {
    var title: String { get }
}

extension Book: Content {}
extension Movie: Content {}

Another option is to create enum with state:
enum Content {
    case book(Book)
    case movie(Movie)

    var title: String {
        switch self {
            case .book(let book): return book.title
            case .movie(let movie): return movie.title
        }
    }
}

In both cases, conformance to ModelTransfer protocol would look like:
class GenericCell: UICollectionViewCell, ModelTransfer {
    func update(with model: Content) {
        titleLabel.text = model.title
    }
}

Currently, there are no plans to support multi-model cell types. Hope two provided options suit your task.


Support configuration of distance filter

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Feature
:arrow_heading_down: What is the current behavior?
Currently it is not possible to configure a minimum distance change before updates are send to the App.
:new: What is the new behavior (if this is a feature change)?
Allows the developer to configure a minimum distance in meters.
:boom: Does this PR introduce a breaking change?
Yes, the signature of the getPositionStream method changed, now accepting an instance of the LocationOptions class.
:bug: Recommendations for testing
Run the example app
:memo: Links to relevant issues/docs

Fixes #27

:thinking: Checklist before submitting

[x] All projects build
[x] Follows style guide lines (code style guide)
[x] Relevant documentation was updated
[x] Rebased onto current develop

Codecov Report

Merging #40 into develop will increase coverage by 5.52%.
The diff coverage is 61.11%.

@@             Coverage Diff             @@
##           develop      #40      +/-   ##
===========================================
+ Coverage    56.45%   61.97%   +5.52%
===========================================
  Files            4        6       +2
  Lines           62       71       +9
===========================================
+ Hits            35       44       +9
  Misses          27       27

Impacted Files
Coverage Δ

lib/utils/codec.dart
100% <100%> (ø)

lib/models/location_options.dart
100% <100%> (ø)

lib/geolocator.dart
57.14% <30%> (+2.14%)
: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 eeb5a3c...9aed2d8. Read the comment docs.


Link for mock.md corrected

Link for mock.md corrected

Coverage remained the same at 100.0% when pulling d436f37dbd7a16be5dfa17f8cef40e0b4a1463b2 on OwenBrotherwood:master into f6aa4057a22f1056c4f8bf96ee6185b50e22a3a6 on BigstickCarpet:master.

Thanks for catching that.