Failed to write arsc

Hi,
I am using axml to rewrite arsc file, and pxb.android.arsc.ArscWriter#main as entry, while it throws an exception, the input arsc can be found in attachment  [attachment](url
resources.arsc.zip
)
Exception in thread "main" java.lang.RuntimeException
	at pxb.android.arsc.ArscParser.readPackage(ArscParser.java:256)
	at pxb.android.arsc.ArscParser.parse(ArscParser.java:142)
	at pxb.android.arsc.ArscWriter.main(ArscWriter.java:95)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)

Is there any idea why this happens?
Looking forward your reply, thank you.

This process failed at the read/parse part, and I have opened a PR to fix it: #9
I am not sure if the writer part works or not, but this should at least give you a different error

Since this lib appears to be dead, we have forked it and made our changes here

@DiamondMiner88 axml is not dead. There's just not much happening, since it's a small library, most bugs have long been sorted out, and the use case is too small to have many new features. If you have improvements, please open a pull request. Btw, we did a new release in August with bugfixes...

Well, #12 hasn't been fully fixed like Ven said

He closed his own merge request, so I can't merge that. Further, nobody provided a proper example why my fix for #12 isn't sufficient. I might have missed something, that's all fine, but then please provide a proper explanation of what the problem still is, or - even better - open a merge request and propose a proper fix.
We're running mass analyses including instrumentation with lots of APK writing and reading for paper evaluations in my lab, and we don't see things breaking left and right. That doesn't mean that no bug is possible, but if there was something breaking left and right, we would have fixed it already. If there is a corner case that you can reproduce, please contribute.


Problem with php version and chmod

There was little problems using the package with php in version 7.1+ and MacOS

pls, merge this pull guys :P


Upgrading to GraalVM 21.0.2

Pull Request Description
Upgrades to latest GraalVM 21.0.2
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

All code has been tested:

[ ] Unit tests continue to pass

A License check is failing. I know how to fix that. Let me push some commits...

I am struggling to see what is wrong with the license configuration. When I run enso/gatherLicenses locally, it generates a different number of warnings than on the CI. How can I reproduce https://github.com/enso-org/enso/actions/runs/7694191923/job/20964475421?pr=8883#step:10:1471 locally?
Please help @radeusgd

I am struggling to see what is wrong with the license configuration. When I run enso/gatherLicenses locally, it generates a different number of warnings than on the CI. How can I reproduce enso-org/enso/actions/runs/7694191923/job/20964475421?pr=8883#step:10:1471 locally?
Please help @radeusgd

 GitHub**Upgrading to GraalVM 21.0.2 · enso-org/enso@41b7efc**Hybrid visual and textual functional programming. Contribute to enso-org/enso development by creating an account on GitHub.

CI does not run gatherLicenses at all. It only runs verifyLicensePackages which just checks if the hashcode of the dependency config and the reports are the same as the one written in the committed report-state file. The warnings count is also written to that file - so that the CI knows if it should be failing - but the count of warnings is generated only locally and has to be committed. Maybe the differing amount of warnings is from a previous run of the tool by Jaroslav? Anyway, you should just try to update the config locally to have 0 warnings and then you can commit the 'fixed' report state and you should be able to get this to pass.

Anyway, you should just try to update the config locally to have 0 warnings

How does one "update the config"? Is there a command to invoke to generate the update? I am dreaming about sbt gatherLicenses to update all the license file on disk. Then I just review the changes and integrated them.

Thanks a lot for finishing and merging this PR.


Create GraphQL model for Notes Data API

As a funder I want to have a description of all APIs in the BT space. Specifically, I want a model of the API for Project Notes Data that will be exposed by Platform.Bible to extension developers. This model must be written in GraphQL.
Only needs to be done for publicly available APIs (aka ones that can be consumed by an extension)
Write documentation using GraphQL for the Project Notes Data API.
Talk to Michael Marshall for more details.

Tom linked Paratext 9 Plugins' IProjectNote related to this

From a quick search, GraphQL is a query language for describing how to get data from an API (like SQL). Why would we want to constrain our design to that specific query language? I feel like this is a step backwards from how we've designed our data access via actual method calls.

I am fine if we use GraphQL, but "This model must be written in GaphQL" should not be part of a use case description, and should not be a technical requirement given to the developers unless it is the only option.  The developers on the project should decide the technology used.  Perhaps GraphQL is the best technology, but in Scrum this should be left to the developers to decide how it is implemented since they are closest to the technical solution.  They can receive feedback from stakeholders, product owner(s), and others outside the team, but it is there responsibility to determine the best way to do that.
For example, if we are interfacing with an external system, and the only way to communicate with that system is via a certain protocol we should say that, but when there are multiple options to solve a problem then the developers should determine how to do that.


Add arrests stops with/without driver being arrested

Branched off #280
What's changed:

Added chart + api views to display counts of drivers who have been stopped vs stopped and then arrested.

Preview:

Closing in favor of https://github.com/caktus/Traffic-Stops/pull/286


merge instead of defaultsDeep in oneOf

fised in https://github.com/drom/resch/commit/ade08ded0fb1efa2db0f3ddebbdc5b4dbd15418c


11.0 fix porting

temporary PR for testing

it was fixed here: https://github.com/it-projects-llc/pos-addons/pull/624


Add support for txt

Add support for txt in {{ext}}. We'd like to use subject.txt without any substitution.

@zdila Have you any luck here?  Not sure if you forked this yet and there's a pull request you were going to make.  Thank you! ✨

Released v2.4.1 to NPM, thanks for your pull request @homerjam!


Fix: Update custom vision url

Azure Custom Vision REST API endpoint was updated and the old one was deprecated. Updating to current version

don't forget to link the issue!

@PIC123 - After you rebase w/ the updated pipeline changes your tests should pass.


Cleanup scripts

Thanks for your effort, the code base looks much cleaner now, and I've also learned something new about C#!


connectNulls feature for radar chart

What problem does this feature solve?
option = {
title: {
text: 'Basic Radar Chart'
},
legend: {
data: ['Allocated Budget', 'Actual Spending']
},
radar: {
// shape: 'circle',
indicator: [
{ name: 'Sales', max: 6500 },
{ name: 'Administration', max: 16000 },
{ name: 'Information Technology', max: 30000 },
{ name: 'Customer Support', max: 38000 },
{ name: 'Development', max: 52000 },
{ name: 'Marketing', max: 25000 }
]
},
series: [
{
name: 'Budget vs spending',
type: 'radar',
connectNulls: true,
data: [
{
value: [4200, 3000, null, 35000, null, 18000],
name: 'Allocated Budget'
},
{
value: [5000, 14000, 28000, 26000, 42000, 21000],
name: 'Actual Spending'
}
]
}
]
};
when connectNulls is enabled values are not connected

What does the proposed API look like?
when connectNulls is enabled , it should work

hii any updates ??

Hi, This is something we are also looking for the solution. Any suggestions/ workaround in this regard would be much appreciated.

any progress?


Add off-by-default timeout functionality to javasrc dependency fetching

Recently, a ticket was created for an issue where analyzing a java project with javasrc ran into the hour timeout and, from the logs, it looks like most of this time was spent fetching maven dependencies. Since we rely on external tools to fetch dependencies there's likely not much we can do to speed that up, but we should have a way of preventing this from timing out the full analysis. This PR adds timeout functionality to ExternalCommand and the GradleDependencyFetcher which is disabled by default, but with either a command line flag or an envvar to enable timeouts. I think the best approach would be to set a default timeout in SL and to have customers override that with the envvar option on a per-project basis (if necessary). I've included logs from some test runs below to demonstrate the usage of this feature.
For maven, the timeout applies to the whole mvn command and works as expected. For gradle, it's a bit trickier since we use a single init script for all the tasks (so fetching dependencies would have a separate timeout for each subproject). To keep the total timeout at the time specified, I opted to just divide the total timeout by the number of subprojects, which could be problematic for projects with many subprojects where one or a few of these have many more dependencies than the other. Solutions to this would be to use separate init scripts for each task and count down the timeout for each created script, or to figure out some way of managing the timeout outside of the gradle api calls.
It's also worth noting that results will generally be bad if dependency fetching is interrupted, but that's arguably still better than no results.
Test Logs
Maven
no timeout
./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies test-projects/shiftleft-java-demo

[INFO ] No timeout set for dependency fetching
[INFO ] got 63 Maven dependencies

1ms timeout
./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies ~/code/test-projects/shiftleft-java-demo --fetch-dependencies-timeout 1ms

[INFO ] Using dependency fetching timeout from --fetch-dependencies-timeout flag: 1ms
[WARN ] Command timed out after timeout of 1ms: mvn --fail-never -B dependency:build-classpath -DincludeScope=compile -Dorg.slf4j.simpleLogger.defaultLogLevel=info -Dorg.slf4j.simpleLogger.logFile=System.out
[WARN ] Retrieval of compile class path via maven return with error.
The compile class path may be missing or partial.
Results will suffer from poor type information.
To fix this issue, please ensure that the below command can be executed successfully from the project root directory:
mvn MAVEN_CLI_OPTS --fail-never -B dependency:build-classpath -DincludeScope=compile -Dorg.slf4j.simpleLogger.defaultLogLevel=info -Dorg.slf4j.simpleLogger.logFile=System.out

[DEBUG] Full maven error output:
Process exited with code 1. Output:

[INFO ] got 0 Maven dependencies

1min timeout
./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies ~/code/test-projects/shiftleft-java-demo --fetch-dependencies-timeout 1min

[INFO ] Using dependency fetching timeout from --fetch-dependencies-timeout flag: 60000ms
[INFO ] got 63 Maven dependencies

1ms timeout envvar override
JAVASRC_FETCH_DEPENDENCIES_TIMEOUT=1ms ./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies ~/code/test-projects/shiftleft-java-demo --fetch-dependencies-timeout 1min

[INFO ] Using dependency fetching timeout from envvar: 1ms
[WARN ] Command timed out after timeout of 1ms: mvn --fail-never -B dependency:build-classpath -DincludeScope=compile -Dorg.slf4j.simpleLogger.defaultLogLevel=info -Dorg.slf4j.simpleLogger.logFile=System.out
[WARN ] Retrieval of compile class path via maven return with error.
The compile class path may be missing or partial.
Results will suffer from poor type information.
To fix this issue, please ensure that the below command can be executed successfully from the project root directory:
mvn MAVEN_CLI_OPTS --fail-never -B dependency:build-classpath -DincludeScope=compile -Dorg.slf4j.simpleLogger.defaultLogLevel=info -Dorg.slf4j.simpleLogger.logFile=System.out

[DEBUG] Full maven error output:
Process exited with code 1. Output:

[INFO ] got 0 Maven dependencies

Gradle
no timeout
./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies test-projects/Slide

[INFO ] No timeout set for dependency fetching
...
[INFO ] Task app:x2cpgCopyDeps_oe5TBq1x resolved `124` dependency files.

1ms timeout
./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies test-projects/Slide --fetch-dependencies-timeout 1ms

[INFO ] Using dependency fetching timeout from --fetch-dependencies-timeout flag: 1ms
...
[DEBUG] Total timeout of 1ms set and 1 subprojects found, so setting dependency fetching timeout per project to 1ms
...
[WARN ] Caught exception while executing Gradle task: Could not execute build using connection to Gradle distribution 'https://services.gradle.org/distributions/gradle-7.3.3-all.zip'.
[DEBUG] Gradle task execution stdout:

> Task :app:x2cpgCopyDeps_OltRFM8q_androidDeps FAILED
Requesting stop of task ':app:x2cpgCopyDeps_OltRFM8q_androidDeps' as it has exceeded its configured timeout of 1ms.
1 actionable task: 1 executed

[DEBUG] Gradle task execution stderr:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:x2cpgCopyDeps_OltRFM8q_androidDeps'.
> Timeout has been exceeded

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

1min timeout
./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies test-projects/Slide --fetch-dependencies-timeout 1min

[INFO ] Using dependency fetching timeout from --fetch-dependencies-timeout flag: 60000ms
...
[DEBUG] Total timeout of 60000ms set and 1 subprojects found, so setting dependency fetching timeout per project to 60000ms
...
[INFO ] Task app:x2cpgCopyDeps_RhS6Govu resolved `124` dependency files.

1ms timeout envvar override
JAVASRC_FETCH_DEPENDENCIES_TIMEOUT=1ms ./joern-cli/frontends/javasrc2cpg/javasrc2cpg --fetch-dependencies test-projects/Slide --fetch-dependencies-timeout 1min

[INFO ] Using dependency fetching timeout from envvar: 1ms
...
[DEBUG] Total timeout of 1ms set and 1 subprojects found, so setting dependency fetching timeout per project to 1ms
...
[DEBUG] Gradle task execution stdout:

> Task :app:x2cpgCopyDeps_7kGDBb1H_androidDeps FAILED
Requesting stop of task ':app:x2cpgCopyDeps_7kGDBb1H_androidDeps' as it has exceeded its configured timeout of 1ms.
1 actionable task: 1 executed

[DEBUG] Gradle task execution stderr:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:x2cpgCopyDeps_7kGDBb1H_androidDeps'.
> Timeout has been exceeded

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s

It's also worth noting that results will generally be bad if dependency fetching is interrupted, but that's arguably still better than no results.

In practice I find the results are not just bad but almost useless. I'd personally prefer a hard error in such a case instead of just papering over the problem and pretending everything is fine.
If it is opt-in, maybe it's fine. But even then - I do not think anyone who fully grasps the consequences of creating a CPG without dependencies would actually want to opt-in to that.

But even then - I do not think anyone who fully grasps the consequences of creating a CPG without dependencies would actually want to opt-in to that.

This is a good point, so I'm going to close this. If this functionality is deemed to be useful enough at some point, we can always re-introduce it.

I am with @maltek on this one. If anybody has the dependencies fetching active, then it is a hard error if that fails. With that being said, we dont even need a timeout since the only thing left than would be to exit with failure.
What we should do if that is not already the case. Is add a log message which states that we start the external dependency resolving and that this could take a long time.


Correctly save modified files

Closes #604

Current coverage is 51.55% (diff: 50.00%)

Merging #691 into master will increase coverage by 0.22%

@@             master       #691   diff @@
==========================================
  Files            95         95
  Lines          7477       7478     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           3838       3855    +17
+ Misses         3090       3071    -19
- Partials        549        552     +3

Powered by Codecov. Last update dbdfed6...3fcbb4a


Fixes #68 and fixes #44 - Fixup README based on markdown lint rules and code based on flake8

Line length of 120 for Python and markdown
Moved flake8 and vscode settings to the top level

#44 kind of got rolled up into this. There wasn't that many issues with that one though almost all line too long. A few I'm creating new issues for that need to be reviewed.

No problem, I'm taking all commits and just want to get this in fast as it might conflict though there's no functionality changes here.

Okay I think I got everything now!


Blink Video Doorbell Support

Describe the bug
Related to https://github.com/home-assistant/core/issues/58662
Blink recently introduced video doorbells.  After installation of hardware and activation on my existing Blink local system, the Video Doorbell does not appear in Home Assistant.  No errors were logged by the home assistant integration.
To Reproduce
Steps to reproduce the behavior:

Install video doorbell hardware.
Follow instruction in Blink Home Monitor to add to existing setup.
Once added, reload and re-install Blink Integration in Home Assistant.
Other Blink cameras appear normally (including Mini) but Video doorbell is not recognized at all.

Expected behavior
Would expect the video doorbell to appear with functionality similar to other Blink cameras.
Home Assistant version (if applicable): 2021.10.6
Log Output/Additional Information
If using home-assistant, please paste the output of the log showing your error below.  If not, please include any additional useful information.
Integration logged no errors.

@fronzbot Seems to be the same API endpoint, just a different child object in the response.
I can grab the API endpoints and sample responses for you.  Just let me know what you need!

Any update on this?  I would also be happy to try and help with anything since I have the device as well, although I am very much a novice with home assistant/programming.

I have sample API responses and endpoints.  I'm not too keen on python, but I could take a crack at a PR @fronzbot if it would be helpful.  May need some help smoothing it over, but I'm happy to give it a shot if it would help.

I'm also interested in adding support for this camera. It should be relatively straightforward to add if @funkybunch has the responses and endpoints. I'm guessing the child object would at least differ in that the doorbell doesn't report temperature like the other cameras. What can we do to help move this along?

@justinmbrock hows your Python?  I'll be available to work on this more tomorrow but I could use some help since my Python is beginner level at best.

My Python is beginner level as well but as a new Blink Doorbell owner, I'd love to get this working. So how can we proceed?

Hey guys, sorry it took me until now to reply, I've had a rough few days. My python is decent enough for an amateur and I'm willing to take a crack at it. @funkybunch, think you can toss the info you have into a repo? I can review those docs from @fronzbot tonight to get up to speed then see what I can make of it tomorrow morning.

@justinmbrock yup for sure.  Let me redact them once I get home and then I'll toss them in a gist and post the link here.

@justinmbrock Here are the sample API responses.  The first one is the config API endpoint.  The 2nd is the homescreen which is already queried by blinkpy in api.py.
Config URL:
{base_url}/api/v1/accounts/{account_id}/networks/{network_id}/doorbells/{camera_id}/config.json
Take picture:
{self.sync.urls.base_url}/api/v1/accounts/{self.sync.blink.account_id}/networks/{self.network_id}/lotus/{self.camera_id}/thumbnail
Liveview:
{self.sync.urls.base_url}/api/v1/accounts/{self.sync.blink.account_id}/networks/{self.network_id}/lotus/{self.camera_id}/liveview
Homescreen:
https://github.com/fronzbot/blinkpy/blob/43f048cf1320e47a66be5ff82b83c17c247c9dab/blinkpy/api.py#L148.

Thank you @fronzbot & @magicalyak!  What would be the next step to moving this to general availability in Home Assistant?

Okay cool, sounds relatively straight forward.  I can take a crack at that unless @magicalyak beats me to it.  @fronzbot mind if I tag you in for code review to make sure I'm on the right track?

Looked through the integration code and it looks like it pulls in camera entities as returned by blinkpy regardless of type.  Tested it locally by just bumping the version and sure enough it worked.
PR on home-assistant/core is up: https://github.com/home-assistant/core/pull/61538

Cool, yeah I signed the CLA.  Hopefully it gets approved soon!

@funkybunch did it get approved? Did it get pushed in one of the recent releases? I'm not seeing my doorbell.

Beta Homeassistant works for me. I can see mine.
Sent from my iPhone

On Dec 26, 2021, at 1:17 PM, ryborg @.***> wrote:

@funkybunch did it get approved? Did it get pushed in one of the recent releases? I'm not seeing my doorbell.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Thanks. I'll try beta.

Yes @ryborg it had been merged into dev.
Thanks for the heads up @magicalyak.  I had been keeping an eye on the rc branch which did not have the changes yet.
The Home Assistant maintainers aren't doing a January major release, and there have been a number of minor releases to come out since https://github.com/home-assistant/core/pull/61538 was merged into dev.  So my assumption is they are waiting for the next major release in February to release this for general availability.  Seems like the beta release channel is the way to go for now.

I'm already on beta. I'll check my logs. I guess I could check to see which blink container is running, or would it all be running in core?

Core.
Sent from my iPhone

On Dec 26, 2021, at 1:54 PM, ryborg @.***> wrote:

I'm already on beta. I'll check my logs. I guess I could check to see which blink container is running, or would it all be running in core?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

I'm just getting messages that I'm on latest supervisor and core after
updating. I tried this from the terminal, but there was no output. It did
execute though. I can try running it from a script?
blink.refresh(force=True)
On Sun., Dec. 26, 2021, 2:08 p.m. Tom Gamull, @.***>
wrote:

Core.
Sent from my iPhone

On Dec 26, 2021, at 1:54 PM, ryborg @.***> wrote:

I'm already on beta. I'll check my logs. I guess I could check to see
which blink container is running, or would it all be running in core?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

—
Reply to this email directly, view it on GitHub
https://github.com/fronzbot/blinkpy/issues/514#issuecomment-1001228819,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYBFIR7SYFLJ4DQWHCRDQ3US5RZLANCNFSM5HENJ4FQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@magicalyak are you running the dev channel by chance?  Looks like dev is separate from beta.
https://www.home-assistant.io/common-tasks/os/#run-a-development-version

Sorry, my screenshot didn't attach.

@ryborg I switched to the dev release channel and that made my doorbell show up (docs in my post above).
https://github.com/fronzbot/blinkpy/issues/514#issuecomment-1001230307

Thanks. Confirmed working in Dev, but not present in Beta.
On Sun., Dec. 26, 2021, 2:37 p.m. Mark Adkins, @.***>
wrote:

@ryborg https://github.com/ryborg I switched to the dev release channel
and that made my doorbell show up (docs in my post above).
#514 (comment)
https://github.com/fronzbot/blinkpy/issues/514#issuecomment-1001230307
—
Reply to this email directly, view it on GitHub
https://github.com/fronzbot/blinkpy/issues/514#issuecomment-1001231572,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYBFIQQQLOE6YOM66H4DRDUS5VIFANCNFSM5HENJ4FQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I am sorry. Dev not beta
Sent from my iPhone

On Dec 26, 2021, at 2:24 PM, Mark Adkins @.***> wrote:

@magicalyak are you running the dev channel by chance? Looks like dev is separate from beta.
https://www.home-assistant.io/common-tasks/os/#run-a-development-version
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Thanks. I missed this.
On Sun., Dec. 26, 2021, 1:36 p.m. Mark Adkins, @.***>
wrote:

Yes @ryborg https://github.com/ryborg it had been merged into dev.
Thanks for the heads up @magicalyak https://github.com/magicalyak. I
had been keeping an eye on the rc
https://github.com/home-assistant/core/tree/rc/homeassistant/components/blink
branch which did not have the changes yet.
The Home Assistant maintainers aren't doing a January major release, and
there have been a number of minor releases to come out since
home-assistant/core#61538
https://github.com/home-assistant/core/pull/61538 was merged into dev.
So my assumption is they are waiting for the next major release in February
to release this for general availability. Seems like the beta release
channel is the way to go for now.
—
Reply to this email directly, view it on GitHub
https://github.com/fronzbot/blinkpy/issues/514#issuecomment-1001225905,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYBFIWO7VFABM26T5UBEB3US5OEHANCNFSM5HENJ4FQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

It is supported alright, but nothing is triggered when the doorbell is pressed. Is this by design?

I don’t think we figured out that trigger yet. It wasn’t obvious to me and my limited python skills. I think it’s a great opportunity for someone though as the doorbell trigger makes a lot of sense.
Sent from my iPhone

On Apr 4, 2022, at 8:08 PM, iLyas Bakouch @.***> wrote:

It is supported alright, but nothing is triggered when the doorbell is pressed. Is this by design?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

pressed

Is somebody working on this topic? Recognize pressed doorbell and to handle this event in blinkpy or home assistant?  Thank you very much

I think no. I'm using IOBroker instead of home assistant. There is a non
free alexa plugin (adapter). This plugin can be used in an alexa routine.
The alexa routine is triggered by the ring button and a datapoint in
iobroker is changed. A iobroker script is triggered by the value change of
the datapoint. There might be other methods, but you have to programming
you own alexa skill and lamba function in AWS.
Am Fr., 2. Dez. 2022 um 07:20 Uhr schrieb thfranke @.***

:

pressed
Is somebody working on this topic? Recognize pressed doorbell and to
handle this event in blinkpy or home assistant? Thank you very much
—
Reply to this email directly, view it on GitHub
https://github.com/fronzbot/blinkpy/issues/514#issuecomment-1334812839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADD5Q2D7HZ5CGJ22OWIXMD3WLGIKNANCNFSM5HENJ4FQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I gave up on this. I use the following solution:

created an input boolean helper in HA
set input helper to sync to alexa
create Alexa routine to set it to true
create an automation in HA to turn it back to false

I abandoned Blink altogether and moved to Amcrest.  All local system, no Amazon middleman, and better HA support (including streaming video feeds).


hot fix of smoke tests broken due to merge issue

fixes issue https://github.com/itlab-vision/dl-benchmark/issues/287
please, make sure smoke tests run and passed before merge (run approval may be required)
please, review @valentina-kustikova @a-sidorova

fixes issue #287
please, make sure smoke tests run and passed before merge (run approval may be required) please, review @valentina-kustikova @a-sidorova

@nberezina, теперь все ок.


Syslog logging with RFC5424 support

Current syslog logging subsystem support UDP only.
UDP is very bad protocol for logging. Black holes in journal if we have unstable network, what is common after on site power supply cycle (off/on).
Please add support for: meta sequenceId and meta sysUpTime.
This will not improve the completeness of the logs, but it will ensure that there are holes in the log.
More in RFC: https://www.rfc-editor.org/rfc/rfc5424.html#section-7.3
We have defined timeQuality in RFC too. It will be nice to possibility of mark logs with tzKnown and isSynced.
https://www.rfc-editor.org/rfc/rfc5424.html#section-7.1
Support for:

origin software
origin swVersion
will be valuable feature too.

@jukkar as you've added that backend maybe you could comment?

Thanks for the info @psztoch. Supporting TCP logging has not been a priority but lets see if I could dedicate some time for it. I will probably also convert the net_context API usage there to BSD sockets at the same time.

UDP is very bad protocol for logging. Black holes in journal if we have unstable network, what is common after on site power supply cycle (off/on).

BTW, using TCP is not perfect either. If there are lot of prints and slow network and/or too few network buffers, we might run of network buffers during send and be forced to drop packets, but that is pretty much business as usual.

Syslog over TCP is described here https://www.rfc-editor.org/rfc/rfc6587

Initial step here https://github.com/zephyrproject-rtos/zephyr/pull/68301 where the current syslog backend is converted to use BSD socket API

@psztoch please take a look if #68307 would work for you. I did not implement any additional fields to the message at this point, this is just to make TCP work with the syslog.

Support for TCP is big step forward, because zephyr device has TCP confirmation about log delivery.
A temporary network problem will cause the packet to be retransmitted.
The certainty of log completeness will increase by up to 10 times.
Unfortunately, there will always be a grain of uncertainty as to whether we have everything. Didn't the buffer overflow and we lost something...
Adding sequenceId dispels these doubts.
In my opinion, adding additional metadata to syslog and TCP support is equally valuable and necessary.

FYI @psztoch, I added structured data support to the latest version of #68307


Updating prose version to fix double backslash bug

This PR fixes #13819

Pull Request Test Coverage Report for Build 580344174

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.305%

Totals

Change from base Build 580019514:
0.0%

Covered Lines:
24992

Relevant Lines:
52893

💛  - Coveralls


WIP: docs: add documentation for cue and rego

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>Co-authored-by: Furkan Türkal<EMAIL_ADDRESS>
Summary

This PR will add documentation for cue and rego
Ticket Link

Fixes #868
Release Note

Docs: add documentation for cue and rego

@dlorenc what do you think about the @lukehinds comment above, do we move this documentation to the sigstore website, if so, I can close this one and start another PR for the sigstore website.

I think we need to do a big bulk move at some point, moving just this over won't really help. It's fine to get this in somewhere so it's at least documented as we figure out how to get these rendered on the main website.
Do we have an issue for migrating everything?

please port changes here (depending on which lands first) https://github.com/sigstore/sigstore-website/pull/67


[artifactory/ansible] TLSv1.1 is deprecated.

https://github.com/jfrog/JFrog-Cloud-Installers/blob/75b3c0cb03d6379d61ab45d4f3c25ce45519bcc4/Ansible/ansible_collections/jfrog/platform/roles/artifactory_nginx_ssl/templates/artifactory.conf.j2#L12
Reference: Strong crypto defaults in RHEL 8 and deprecation of weak crypto algorithms

Documentation needs an update as well:
https://jfrog.com/help/r/jfrog-artifactory-documentation/configuring-nginx

Closed via https://github.com/jfrog/JFrog-Cloud-Installers/pull/292


BUG Style mismatch for contact form

Describe the bug
Style is mismatch for contact form
Expected behavior

we should remove the curve border
Screenshots (Mandatory)

border is curve

Additional Context (Mandatory )
Are you contributing under any open-source program ?

jwoc

@AftabMankapure Sorry to close this issue . You can raise this issue gain but only after the successful completion of the previous PR


Server reload bundle fix

@robwise let me know if I have this right.  Was pretty straight forward, just had to make sure not to include the 'extra stuff'.

@rstudner Awesome! This all looks good to me besides there being still one linter thingy:
Offenses:
lib/react_on_rails/configuration.rb:39:45: C: Avoid multi-line ?: (the ternary operator); use if/unless instead.
      self.reload_server_js_every_request = reload_server_js_every_request.nil? ?
                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Haha on the last failure.  "line too long."  "don't break up line".  haha

Yeah lol, with the ternary operator it's too long for the line length, and then they don't want you to use multi-line ternary operators, so we should go with an if-else

@rstudner are we going to put those tests in with this fix? or afterwards?
cc: @robwise

@justin808 It's on his fork so maybe just merge it and I will make another PR for its tests?


mellowplayer: mark broken on darwin

Description of changes
Fails when building tests because Carbon is not found, even though the framework is installed.
Since the project is not maintained, mark it as broken instead of debugging.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

A quick hack for the framework errors is
  postPatch = ''
    sed -i "31,32d" cmake/Macros.cmake
  '';
  env.NIX_LDFLAGS = lib.optionalString stdenv.isDarwin "-framework Carbon -framework Cocoa";

However, other errors exist, so LGTM.


Use with npm

Hi,
I've installed both Leaflet and Proj4Leaflet in my npm project, but I'm having trouble figuring out how to use Proj4Leaflet in this set up.
In previous versions, I'd import Leaflet (as L), then import the CRS object from Proj4Leaflet and use it directly, but that doesn't seem to work now.
The error I'm getting is shown in the screenshot below:

Can anyone tell me the correct way of using Leaflet and Proj4Leaflet in my npm project so I no longer get these errors? I'm currently bundling everything together with Webpack, so I'd rather not have to add extra script tags to the page unless absolutely necessary as the intention is to create one JS file that contains all of my map stuff.
Thanks,
Dylan

Hi Dylan,
thanks for taking the time to reporting this issue.
I can't say for certain what's going on without seeing some running code, but Proj4Leaflet is designed to work with NPM/Browserify/Webpack, so in theory what you're trying to do in the code should work.
I haven't personally used the latest release with NPM/Browserify, so it might be that some error have snuck in there. The first thing I would try is to step through Proj4Leaflet's UMD wrapper, to check that it's actually requiring Leaflet properly. In particular, you could check with a debugger what happens around this line: https://github.com/kartena/Proj4Leaflet/blob/master/src/proj4leaflet.js#L8
From the error above, it looks like Leaflet's namespace L might not be properly intialized for Proj4Leaflet.

Hi,
I think actually it's something I'm doing wrong. I'm using Jest to run some tests, and as part of that I'm mocking Leaflet, which of course results in Proj4Leaflet not being able to extend it properly as it's not being mocked correctly.
Thanks for your help though! I'll close this issue now as I'm pretty convinced it's not being caused by a problem in Proj4Leaflet itself.


ImportError: cannot import name 'urlopen' in python3.6.0

Traceback (most recent call last):
  File "draw_plot.py", line 4, in <module>
    import matplotlib as plt
  File "/path/to/.alexpy3/lib/python3.6/site-packages/matplotlib/__init__.py", line 129, in <module>
    from six.moves.urllib.request import urlopen
ImportError: cannot import name 'urlopen'

My six version is 1.10.0
I tried manually import it in ipython, it works well.
but when I ran it as a script, i got the above import error
-> import matplotlib as plt
(Pdb) import sys
(Pdb) for s in sys.path: print(s)
/myhome/Documents/programs/python
/usr/local/Cellar/python3/3.6.0_1/Frameworks/Python.framework/Versions/3.6/lib/python36.zip
/usr/local/Cellar/python3/3.6.0_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6
/usr/local/Cellar/python3/3.6.0_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload
/myhome/.alexpy3/lib/python3.6/site-packages
(Pdb) import six.moves.urllib.request
(Pdb) import six.moves.urllib.request as p
(Pdb) dir(p)
['AbstractBasicAuthHandler', 'AbstractDigestAuthHandler', 'BaseHandler', 'CacheFTPHandler', 'FTPHandler', 'FancyURLopener', 'FileHandler', 'HTTPBasicAuthHandler', 'HTTPCookieProcessor', 'HTTPDefaultErrorHandler', 'HTTPDigestAuthHandler', 'HTTPErrorProcessor', 'HTTPHandler', 'HTTPPasswordMgr', 'HTTPPasswordMgrWithDefaultRealm', 'HTTPRedirectHandler', 'HTTPSHandler', 'OpenerDirector', 'ProxyBasicAuthHandler', 'ProxyDigestAuthHandler', 'ProxyHandler', 'Request', 'URLopener', 'UnknownHandler', '__doc__', '__name__', 'build_opener', 'getproxies', 'install_opener', 'pathname2url', 'proxy_bypass', 'url2pathname', 'urlcleanup', 'urlopen', 'urlretrieve']
(Pdb) print(p.urlopen)
*** AttributeError: module 'six.moves.urllib.request' has no attribute 'urlopen'

what is wired is that dir(p) reports that it has urlopen in it, but when you access it, it says no attribute 'urlopen'

After some trying, it came out that it is matplotlib that pollute my six environment.
as a matplotlib new comer, I did the following, which is wrong
import matplotlib as plt

this made the above import error. But I still can not find the root cause for this error.
When I use the following import as is written in the matplotlib.__init__.
import matplotlib.pyplot as plt

everything comes back.
I will open another issue for matplotlib for this, as this confuses not-so-careful beginners like me.


i2c unnecessarily takes ownership of Clocks?

The i2c constructor takes ownership of the Clocks struct
https://github.com/stm32-rs/stm32f3xx-hal/blob/0ad1ca6a44e3be0e73f02f41705a41d054d9e931/src/i2c.rs#L109-L115
but only requires the frequency of pclk1.
https://github.com/stm32-rs/stm32f3xx-hal/blob/0ad1ca6a44e3be0e73f02f41705a41d054d9e931/src/i2c.rs#L136
Hertz is copyable, so is there some reason for taking ownership of the Clocks or is this simply an oversight?

Never mind. If I would just read the fine manual, I would see that Clocks also implements Copy and not bother anyone.


az arcdata has mixed up shortened parameters

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az arcdata dc create
Extension Name: arcdata. Version: 0.0.2.
same applies to az sql mi-arc create
Errors:
This command has been ported from azdata arc dc create
The old command used -ns for namespace and -s for subscription
The new command uses -s for namespace and no shortened parameter for subscription
I assume, this is by mistake :)
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az arcdata dc create

Expected Behavior
the shortened parameters should be in line with other commands as well as previous azdata commands
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.26.1

Extensions:
account 0.2.1
arcdata 0.0.2
storage-preview 0.7.4
subscription 0.1.4

Additional Context

route to service team

Thanks for reporting this @bweissman.  It will be fixed in the next release of the extension.  @yonzhan - please close.
The --namespace parameter will be renamed to --k8s-namespace/-k.


Include burnt results in lines, to support Py ash and canisters.

A line's products are the recipe products plus the burnt result of any
fuel. This reveals the burnt result created by any line you already
have, so that you know to handle it. In the matrix solver you can
process the byproduct as usual (e.g. refilling fluid canisters).
What burnt result will be produced depends on the recipe, the machine,
and the fuel. This does not any recipes which fill demand for the
burnt result (e.g. you need ash, we don't suggest burning coal to make
steam in a boiler). This is pretty wonky, but it's an improvement from
not having ash show up at all. You can fake it by adding a one steam
as an output from your factory, and the extra steam will turn into
a byproduct. Or you can paste the ash-producing line you want in from
another factory and the solver will use it.

When I use this branch Factorio locks up for ~8s when I open the gui.

When I use this branch Factorio locks up for ~8s when I open the gui.

When I use this branch Factorio locks up for ~8s when I open the gui.

@ThoreMehr The delay doesn't happen for me when I load your save. If it's still happening, you could try to get a stack trace. It's a bit of trouble to get it set up if you haven't already. Install VSCode and FMTK, run Factorio in debug mode, load the save (this takes a lot longer than outside of debug, that's normal, it took six minutes for me), hit the pause button in VSCode during the 8s delay.

Hello, sorry for only having a look at this now. I really appreciate the contribution. Unfortunately (and I don't blame you for this, the solver code is ass), your solution is quite complicated in approach, so I won't merge it. Nonetheless the next version will have this feature following my own implementation. Thanks again!

Oh you're totally right about the craft per second thing, big whoopsie. Will address that in a future version as well.


Big Sur / M1 Mac support

Trying to install the toolchain using homebrew on a m1 mac results in:
eosio.cdt: The intel architecture is required for this software.
Error: An unsatisfied requirement failed this build.

Alternatively trying to install it using a separate brew install that's run under rosetta 2 results in:
Error: An exception occurred within a child process:
  RuntimeError: Error, only supporting binary packages at this time

And finally building from source results in:
ld: framework not found Foundation

Thank you for reaching out! Unfortunately, EOSIO has never officially supported the ARM architecture.
Formal M1 support would not only require a working build targeting ARM, but also M1 support by all of our test infrastructure and an M1-based buildfleet to be built out. In particular, Anka (a docker-like type 2 hypervisor we use for macOS in our CI system) in a key vendor who has yet to add ARM/M1 support.
We are paying close attention to the adoption of ARM in PCs and datacenters by Apple, OEMs, chipmakers, and cloud providers.

The ld: framework not found Foundation error is related with #1005

Duplicate of https://github.com/EOSIO/eos/issues/9849


Unable to compile on Android32 and Android64 platforms

Unable to compile on Android32 and Android64 platforms. I am using this code on Delphi 11.3 Patch 1 (Alexandria). Here's the errors for Android64:
`[DCC Error] UMultiDemo.pas(586): E2250 There is no overloaded version of 'RequestPermissions' that can be called with these arguments
[DCC Error] UMultiDemo.pas(669): E2250 There is no overloaded version of 'Create' that can be called with these arguments
[DCC Error] UMultiDemo.pas(733): E2250 There is no overloaded version of 'Create' that can be called with these arguments
[DCC Error] UMultiDemo.pas(743): E2250 There is no overloaded version of 'Queue' that can be called with these arguments
[DCC Fatal Error] MultiDemo.dpr(6): F2063 Could not compile used unit 'UMultiDemo.pas'`

There have been lots of changes for Android requirements since we first posted this, needs to be updated, sorry.


What is the repository license?

Hello @EvZissel , what's the library license , please?
Thanks!

MIT license. Thank you for pointing my attention to this!


Upgrade lottie-ios dependency

Description
Updating lottie-ios and lottie-react-native is currently not possible. Pod install gives lottie-react-native (from `../node_modules/lottie-react-native`) was resolved to 3.1.1, which depends on lottie-ios (~> 3.0.3)
Steps to Reproduce

Update lottie-ios to 3.1.3 and lottie-react-native to 3.1.1
Run pod install
You get error of incompatible versions.

Expected behavior: [What you expected to happen]
Succesfully update dependencies.
Actual behavior: [What actually happened]
Error of incompatible versions.
Versions
lottie-ios to 3.1.3 and lottie-react-native to 3.1.1

Hey, folks. 3.0.3 Is 6 months old and misses tons of fixes and optimisations. Even worse - where is no npm release for compatible 3.0.7 of lottie-ios.

@zinoviev what does that mean ?
@emilioicai is using lottie ios 3.1.3 not 3.0.3


Example of training the boolean pipeline

Goal: provide an example in the /examples/ directory that shows how to train the boolean pipeline, with an approximate replication of the leaderboard submission.
Without this example, the existing models may fall into disuse as MRC modeling progresses.
(1) example of training query type classifier
(2) example of training evidence classifier
(3) scripts to extract training examples of 1,2 from Tydi
(4) training of score normalizer, based on building an MRC model on 4/5 of the Tydi training data, decoding on the 1/5, and training the score normalizer on the system output of the 1/5.
This does not exactly replicate the leaderboard, which had
(1) MRC trained from NQ and Tydi via distillation, synthetic data
(2) SN trained on part of the dev set
(3) evidence classifier incorporating BoolQ with expanded context from the wikipedia and system output
But close enough that a clear explanation of these differences will document our leaderboard submission, and allow the pipeline to be updated to future MRC models as necessary.

Sara has a trainer for query type classifier.
I have modifications that make it run with the evidence classifier.
Next step is to sync up these two versions.


Retry with output stream

When getting OutputSream, FileSystemException sometimes occurs.
So, now this retries either when getting OutputSream.
It's just enhancements, so i wrote no tests.

oh https://github.com/civitaspo/embulk-output-sftp/pull/17 looks better than this, so close this.


ApiException inheritance is causing This error class already inherits from another class error on valid patterns

I'm facing an issue on a spec, and I do believe that kiota behavior is inconsistent in this valid case, but I'm struggling to:

pin-point the root cause of the problem
figure out what should be the expected encoding

I reduced the issue and you can test the current behavior with slight variations of it, the command to be issued is always (using kiota compiled locally from main):
kiota  generate --openapi openapi.yaml --language Java

The original spec contains this pattern:
openapi: 3.0.3
info:
  title: Kafka Instance API
  version: 0.13.0-SNAPSHOT
paths:
  /api/v1/topics:
    get:
      summary: Retrieves a list of topics
      operationId: getTopics
      responses:
        "423":
          description: Example.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      allOf:
      - $ref: '#/components/schemas/ObjectReference'
      - description: General error response
        type: object
        properties:
          code:
            format: int32
            type: integer
    ObjectReference:
      type: object
      properties:
        id:
          description: Unique identifier.
          type: string

and the error message is:
This error class already inherits from another class. Update the description to remove that inheritance.

It took me quite a while to understand why I should update a "description", but this is not important.
This is happening because an error response is generated to extend ApiException.
Inheritance in error model classes should be allowed as they are generic models, in case multiple inheritance is forbidden(like in Java) there are a few viable options:

expand all the fields of the parent into the child
turn ApiException into an interface that holds(and returns) the value of the Exception instead of being a full class itself
more variations 🙂

Trying to figure out how to fix this is where the story started to be obscure for me.
the following spec(duplicating one of the allOf):
openapi: 3.0.3
info:
  title: Kafka Instance API
  version: 0.13.0-SNAPSHOT
paths:
  /api/v1/topics:
    get:
      summary: Retrieves a list of topics
      operationId: getTopics
      responses:
        "423":
          description: Example.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      allOf:
      - description: General error response
        type: object
        properties:
          code:
            format: int32
            type: integer
      - $ref: '#/components/schemas/ObjectReference'
      - description: General error response
        type: object
        properties:
          code:
            format: int32
            type: integer
    ObjectReference:
      type: object
      properties:
        id:
          description: Unique identifier.
          type: string

Surprisingly doesn't throw the error above, the generation succeeds but inheritance from ObjectReference is skipped without even throwing a warning message.
The most worrying fact to note here is that the generation looks to be not idempotent with respect to the order of the definitions(happy to be proven wrong!).
Last(from my experiments) but not least, this spec:
openapi: 3.0.3
info:
  title: Kafka Instance API
  version: 0.13.0-SNAPSHOT
paths:
  /api/v1/topics:
    get:
      summary: Retrieves a list of topics
      operationId: getTopics
      responses:
        "423":
          description: Example.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      allOf:
      - $ref: '#/components/schemas/ObjectReference'
    ObjectReference:
      type: object
      properties:
        id:
          description: Unique identifier.
          type: string

In this case (with "single inheritance") the generation succeeds but Error is going to extend only ObjectReference and not ApiException.
Thanks a lot for powering through this long bug description and I appreciate feedback on this analysis 🙂

Hi @andreaTP,
Thanks for the deep analysis, it outlines a few opiniated decisions we've had to make during design and implementation.
On inheritance
allOf is technically not describing inheritance in JSON schema, it's a kind of composition. But most descriptions out there use it as a way to describe an inheritance structure with allOf one ref and one inline schema. I've chatted with @Relequestual and @jdesrosiers about that and the consensus was that there needs to be additional structures for IDL (inheritance, interfaces, etc...), it's most likely going to be in a JSON schema vocab outside of the core vocab and it could sit in OpenAPI vocab, but would be more beneficiary to the community if it were something of its own.
Some work was started here but the person leading the efforts had to drop and they are now looking for a new leader. While I have some JSON schema understanding, and some community-foo, I don't think I have enough experience to lead a standardization effort, but I'll be happy to help once somebody steps up.
Once the vocab IDL is out, OpenAPI needs to adopt it, and there will be a migration lag from existing descriptions out there. So we made a couple of opiniated decisions. The main part of the code dealing with inheritance is here. It roughly translates to "the current inline schema is the current class, the current ref schema is the parent class, walk the dependency tree recursively". I don't believe order of the inline and referenced schemas have an impact, but I might be wrong, and adding unit tests (if we're missing some) might be beneficial to ensure that order doesn't impact things.
It is possible that because of that recursive approach, we're kind of giving up on other allOf entries, and I agree a warning should show up. The best thing to do is probably to implement a validation rule for the time being.
On exceptions
We're making generated error types inherit our generic APIException type for the following reasons:

Consumers can write "catch all" clauses using that parent type, or drill down to errors that are specific to an endpoint as they choose.
The request adapter needs to use an exception type when no error types are described or when no payload is returned, we might as well use one we know.

Because most languages don't support multiple parents inheritance, we've made the choice to throw the towel when we encounter an error type description that inherits from something else. At the very least there should be a validation rule (see previous paragraph). At best we could improve that logic by just flattening the schema before we project it.
I hope that answers your questions, as always we'll be more than happy to see pull requests coming our way. The exception thing is probably much easier to fix as a first stop gap than the inheritance aspect (we iterated multiple times on that).

Thanks a lot for the detailed answer, as always @baywet !
From what I'm hearing, I'm almost convinced that the most "correct" behavior would be to directly inline the referenced object's fields instead of using inheritance, at least for errors that are already extending ApiException (if not always ...).
A detail to be taken into consideration with this approach is that we will be unable to emit code for recursive models(or we should somehow limit the maximum depth), I'm not sure about the current behavior in this case.
Assuming an agreement on this direction, the last example that I provided needs to be classified as a bug(maybe it can even be fixed before GA?).
Regarding the implementation, my little knowledge of the codebase would make this task a bit challenging for me but I can give it a shot if no one else has cycles to spare in the mid-term.

On the errors inheriting something else and being squashed instead of the generation returning an error, this is probably an enhancement more than a bug. When we started looking at the error experience, this is a limitation we set in the requirements and we wanted to see if there was any demand before making further investments. You request here makes for 1 customer/partner demand, which is probably not enough to prioritize it yet (pending our other ongoing discussions).
On inheritance. If we have non-deterministic behaviour (order), that's probably a bug that needs fixing before GA.
If we are dropping oneOf entries, that's probably a validation rule that needs to be implemented to detail the limitations of the generation logic to the client, I don't think that needs to be done before GA though.

Generate the whole inheritance tree from the description, make the greatest grand parent class inherit from API exception.

This sounds like a super interesting idea, the downside is that we would need to have duplicated hierarchies for errors and models.
Moving the conversation about the bug to a separate issue.

Do you mean in the case where a model is a parent of an error and is used as a property/response type of a successful response?

Correct.

this is one of the reasons why we originally decided to throw instead of making an opiniated choice here. Cross checking all references will take a while, especially on large descriptions. Maybe it'd be better to flatten things since it's semantically closer to what allOf means anyway?
I think this is the kind of things where experimenting and having more community feedback would help make a clear cut decision.

Maybe it'd be better to flatten things since it's semantically closer to what allOf means anyway?

I start to be convinced that this would be the way to go.
I might try to experiment with this, but happy to hear more opinions, should we open a more precise "Discussion" to track this one?

I don't think there will be a lot of people with opinions on this, and the ones who had opinions on our side already expressed it. I'd rather have you experiment in this avenue and share your findings here when you have a bit of time to focus on this if you don't mind?

Agreed @baywet .
For the records, I just found this piece of docs regarding REF_AS_PARENT_IN_ALLOF which is basically what we are discussing here.

I keep hitting this issue:
https://api.openshift.com/api/connector_mgmt/v1/openapi
given how frequent it is to find this "unsupported" signature I'll try to draft a proposal for solving it.


Database FKs are not deleted on panel update

FKs such as those related with plugins are not deleted when the columns are dropped, so the panel will fail calls.

https://git.io/vDCO9


Add a winch handler

This patch adds a signal handler for the winch. Now, era can redraw contents of a timer and raindrops if the terminal window size is changed.
This movie is a demonstration of such a situation.
https://user-images.githubusercontent.com/12132068/162604510-31213502-e423-45f8-ac04-90377694f3fc.mp4
I'm new to JS/TS, so maybe there are some odd codes. Could you please review them? Thank you.

Looks amazing!
But, the thing is I'm not familiar with OOP, which you are using in this PR I think. It may be a little bit too complicated for this simple tui app. I think there will be another way to deal with the window size in simpler or "scripting" way.

Thank you for your review.
I don't know what is a "scripting" way you said. Does it mean a procedural way? However, I can understand that my way is probably too much complicated with OOP styles such as classes in this situation. So I remove them, is this good?

Sorry for the vague expression: Yes, I meant procedural by 'scripting'.
Thank you for the refactoring. I tested your code, but it seems not to work on my environment (Linux, i3 window manager. Please see the gif). Could you tell me your environment?

This is my environment.

OS: Linux
WM: Xmonad
Terminal: Alacritty
Editor: Vim

Sorry, my mistake. With catch_winch everything works fine! Thank you.

Thank you for merging.


Store Data Persistently

Right now data is synchronized from GitHub periodically into an in memory store.
In order to keep issue data beyond closed stage we'd need to introduce our own persistent data store.
Ideas

[ ] Define Store API
[ ] Allow implementation of different storage providers

Data is already dumped to the tmp/storedump.json file periodically.

We recently added a S3 store dump.

Local storage and S3 storage is available via the dump-store providers.


Validate the format of dates

The Schedule elements of a feed should have dates that are in the form YYYY-MM-DD; this PR adds a validation that checks their format.
Pivotal card

clj-time to the rescue!


Repository logging for NETSTANDARD14

The logging code for 1.4 has been #if out; because the logging factory interface has changed from .net standard 1.4 to 2.0.

Net standard 2 is not really there.  Blocked on https://github.com/net-commons/common-logging/issues/148

@richardschneider netstandard2.0 is now up. Should we unblock?

.Net Standard 1.4 is no longer supported #99


remote.py replace requests lib with httplib and urllib

requests takes up to 300ms to import. By simply replacing it with httplib and urllib, we are free from this run time deficit.

Looks good.  Thanks, Kien!


Add algo type in add aggregatetuple

Currently, when using the following command, the type of the --algo-key option isn't specified:
substra add aggregatetuple --help

Maybe we could add this information in order to make this doc easier to understand?

What do you think about this @samlesu?

What do you think about this @samlesu?

Good idea :)


make_heap code object inequality at import time

In attempting to go through the introductory material for UMAP, I hit the following exception with import umap:
<code object <module> at ..., file "/path/to/keras/lib/python3.12/path/to/pynndescent/sparse_nndescent.py", line 1> != <code object make_heap at ..., file "/path/to/keras/lib/python3.12/path/to/pynndescent/utils.py", line 171>.
I'm at a loss on how to debug this.  Note that the venv here is called "keras".
WSL2
Python 3.12
scikit-learn 1.6
umap-learn 0.5.7
scipy 1.14.1
pynndescent 0.5.13
numpy 2.0.2
numba 0.60.0
keras 3.6.0

Note that I've since tried running this from a new venv without keras, and the same problem manifests.

I have never seen this before. I'll have to see if I can reproduce anything like it locally.

A member of our group reports that a very similar setup with Python 3.10 works as expected.


DOM lib doesn't have the concrete event signatures like the React synthetic event declared?

TypeScript Version:  2.7.0

Search Terms:
Code
declare const $input: HTMLInputElement

// Property 'value' does not exist on type 'EventTarget'
$input.onchange = e => { console.log(e.target.value) }

Expected behavior:
The e.target be inferred as HTMLInputElement instead of EventTarget.
The HTMLInputElement could be signatured as below or other proposals:
interface HTMLElement<E> extends Element {
    onchange: (this: E, ev: Event) => any;
}

interface HTMLInputElement extends HTMLElement<HTMLInputElement> {
}

Actual behavior:
Error Property 'value' does not exist on type 'EventTarget'
Playground Link:
Playground

I think this is the same issue as https://github.com/Microsoft/TypeScript/issues/299, the request to make Event interface generic with its target as the argument.


Notification when someone follows you

It feels like a bit of asymmetry at the moment.
If I follow someone, they will not know I follow them.
If that someone follows me, they will know I had already followed them, yet I will not know we are friends (unless I specifically look them up in friends list).

Not a bad idea; it's pretty easy to implement.

This would come with a new state on the notification then I hope so it is easy to separate out from the rest? It will require some handling of the UI because I'm not sure what will happen if you get an unexpected notification type.

yeah, not that the existing code pays any attention to the state currently - but yes, it'd be a new notification type.

Speaking of which, there should be a default icon for an unknown type (if there isn't already).

What would the notification say?  "You also have 2 notifications unknown to the UI relating to xxx classified as yyy"

What would happen now if a notification with an unknown type was added?
I basically just mean have a generic notification for types we don't know yet. That way if we decide to add some new notifications without a UI, we still see them, instead of sitting there wondering "why don't I see my notification"?

At the moment the notification code doesn't particularly care at all about notification type, it infers the type from the fields (note/node) and whether there is a mention in the content. So e.g. a notification for "x subscribed to you" would probably appear as "a new user was posted"

Sorry, I inferred from the discussions that there was a type field in notification that suggested the origin of the notification, and that was being used to decide how to display it.

there is a type field, it is not being used at the moment :) This will probably need to change.

Yes it could clean up the code a lot. I was just eager to catch mentions and friends' activities from start.


Forge class trying to create UNSIGNED integer fields in Postgresql

$this->forge->addField('last_activity' => array(
			'type' => 'INT',
			'constraint' => 10,
			'unsigned' => true,
			'default' => 0,
            'null' => false,
		));

pg_query(): Query failed: ERROR:  syntax error at or near "UNSIGNED"
LINE 5:  "last_activity" INT UNSIGNED DEFAULT 0 NOT NULL,

Fixed by PR #731


ESP32-S3 build in windows and docker does not recognise ESP_EXT1_WAKEUP_ANY_LOW (IDFGH-11115)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
ESP-IDF v5.1
Operating System used.
Windows
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
Expected behaviour is to build with ESP_EXT1_WAKEUP_ANY_LOW
What is the actual behavior?
Build with ESP_EXT1_WAKEUP_ALL_LOW but not with ESP_EXT1_WAKEUP_ANY_LOW
Steps to reproduce.
We have two machines and one cloud docker.
ON windows machine we have to replace ESP_EXT1_WAKEUP_ANY_LOW with ESP_EXT1_WAKEUP_ALL_LOW to build
ON docker we also have to replace ESP_EXT1_WAKEUP_ANY_LOW with ESP_EXT1_WAKEUP_ALL_LOW to build
ON MacOS we build with ESP_EXT1_WAKEUP_ANY_LOW and it build as expected
Windows is ESP-IDF v5.1.
Docker is https://hub.docker.com/layers/espressif/idf/release-v5.1/images/sha256-8c4fbd6821489d37e99a25f2fcac728f40e8165944137812f5b4110f6aa23fd9?context=explore
Build or installation Logs.
In file included from C:/Espressif/frameworks/esp-idf-v5.1-2/components/esp_hw_support/include/esp_sleep.h:10,
                 from C:/x/x.espFirmware5/x/main/include/app_main.h:6,
                 from C:/x/x.espFirmware5/x/main/app_main.c:1:
C:/x/x.espFirmware5/x/main/app_main.c:625:73: error: 'ESP_EXT1_WAKEUP_ANY_LOW' undeclared (first use in this function); did you mean 'ESP_EXT1_WAKEUP_ALL_LOW'?
  625 |     ESP_ERROR_CHECK(esp_sleep_enable_ext1_wakeup(ext_wakeup_pin_1_mask, ESP_EXT1_WAKEUP_ANY_LOW));
      |                                                                         ^~~~~~~~~~~~~~~~~~~~~~~
C:/Espressif/frameworks/esp-idf-v5.1-2/components/esp_common/include/esp_err.h:117:30: note: in definition of macro 'ESP_ERROR_CHECK'
  117 |         esp_err_t err_rc_ = (x);                                        \
      |                              ^
C:/x/x.espFirmware5/xApp/main/app_main.c:625:73: note: each undeclared identifier is reported only once for each function it appears in
  625 |     ESP_ERROR_CHECK(esp_sleep_enable_ext1_wakeup(ext_wakeup_pin_1_mask, ESP_EXT1_WAKEUP_ANY_LOW));
      |                                                                         ^~~~~~~~~~~~~~~~~~~~~~~
C:/Espressif/frameworks/esp-idf-v5.1-2/components/esp_common/include/esp_err.h:117:30: note: in definition of macro 'ESP_ERROR_CHECK'
  117 |         esp_err_t err_rc_ = (x);                                        \
      |                              ^
[107/108] Generating binary image from built executableesptool.py v4.7.dev1
Creating esp32s3 image...
Merged 1 ELF section
Successfully created esp32s3 image.
Generated C:/x/x.espFirmware5/x/build/bootloader/bootloader.bin
[108/108] cmd.exe /C "cd /D C:\x\x.espFirmware5\fl...are.espFirmware5/x/build/bootloader/bootloader.bin"Bootloader binary size 0x51f0 bytes. 0x2e10 bytes (36%) free.
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the C:\x\x.espFirmware5\x\build\log\idf_py_stderr_output_50708 and C:\x\x.espFirmware5\x\build\log\idf_py_stdout_output_50708

More Information.
No response

@ttkkhhaann In release/v5.1 branch, ESP_EXT1_WAKEUP_ANY_LOW was added in commit b27e57db7bf6dc810f3603e19045c93afdc428e4, with follow-up changes in badef66538ec6deb494687c9a14eeab883eadb83 and 5859b8323285fefed8a0ebdb479ca46aa864a8f4. These commits are not part of v5.1 release tag. They are included in v5.1.1 bugfix release.
I think the issue you are seeing is due to the fact that you aren't running IDF v5.1.1 (or a more recent version or release/v5.1 branch) on all of the platforms. To troubleshoot this, please run git describe command in ESP-IDF directory on all 3 platforms, and post the results here.

Hi @igrr
git describe on Windows machine  where id doest build with ESP_EXT1_WAKEUP_ANY_LOW
git describe
v5.1
git describe at MAC where  it does build with ESP_EXT1_WAKEUP_ANY_LOW
v5.1.1-305-g697e3e8eac
cannot figure out how to run git describe on docker image
but the build results in pipeline show
[2/2] idf (5.1.1) and it doesnt build due to same error

@igrr
I have changed the docker to the latest v5.1.1 and it is working now. The only issue remaining is how to fix it on windows,
I have reinstaleed 5..1.1 on windows but it doesn't build. I cannot find any instructions on how to update windows to latest branch . git status inside windows says its not on any branch. I used windows installer for this
thanks

@ttkkhhaann You need to make sure that you are downloading the correct docker image for your selected version of ESP-IDF.
The docker image you've linked above is for the ESP-IDF release/v5.1 branch which is progressively updated over multiple bugfix releases.
If you are using ESP-IDF v5.1.1 (i.e., git checkout tags/v5.1.1 on your MAC), then you should download the v5.1.1 docker image on your corresponding windows PC.
Hope the pointers above resolves your issue.


do not use matrix for node versions in tests action

do not run tests on different node versions (unnecessary)

I re-ran the checks as they succeeded, but didn't report for whatever reason.

Ohh..it's waiting for the old matrix checks to complete, something got out of hand here. We'll probably need the repo admin to merge it manually (cc @MSevey).


when  I run  uv  pip  sync requirements.txt   , the  environment  is  not be  updated

win11

but   pyproject.toml

So,  I  think this command   of  uv add -r requirements.txt   can  instead it  .

Yeah I think you're looking for uv add here as you mentioned above.


RuntimeError: Error compiling objects for extension

could you please help me with this problem？
I was using CUDA=10.2, pytorch and torchvision accordingly
I got this error when I install the mmaction while running  ./compile.sh
BTW, it seems CUDA is not properly detected since 'No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda''
THX
Traceback (most recent call last):   File "setup.py", line 84, in <module>     cmdclass={'build_ext': BuildExtension})   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/setuptools/__init__.py", line 165, in setup     return distutils.core.setup(**attrs)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/core.py", line 148, in setup     dist.run_commands()   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/dist.py", line 966, in run_commands     self.run_command(cmd)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/dist.py", line 985, in run_command     cmd_obj.run()   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run     _build_ext.run(self)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/command/build_ext.py", line 340, in run     self.build_extensions()   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 603, in build_extensions     build_ext.build_extensions(self)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/command/build_ext.py", line 449, in build_extensions     self._build_extensions_serial()   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/command/build_ext.py", line 474, in _build_extensions_serial     self.build_extension(ext)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 208, in build_extension     _build_ext.build_extension(self, ext)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/distutils/command/build_ext.py", line 534, in build_extension     depends=ext.depends)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 437, in unix_wrap_ninja_compile     with_cuda=with_cuda)   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1163, in _write_ninja_file_and_compile_objects     error_prefix='Error compiling objects for extension')   File "/home/user/anaconda3/envs/mmaction-new/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1436, in _run_ninja_build     raise RuntimeError(message) RuntimeError: Error compiling objects for extension

Hello, I have the same question. Could you tell me if you have sovled it?


Handle running out of quota / rate limit

Allstar aggressively caches and saves the cache between runs, however it is still running out of quota on orgs with a large number of small repositories. For some reason the cache is not helping avoid this from run to run. We'll need to figure out what is going on with the cache, and probably implement a proper rate limit delay to pick up where we left off.

For some reason the cache is not helping avoid this from run to run.

I looked into this and traced it down to because of the ordering of the transports. The httpcache transport uses the request headers to determine whether or not to return the cached responses, and because the httpcache transport is run first, this is ALWAYS different.
Specifically, what happens is that the httpcache transport records the original request headers as new headers prefixed with X-Varied-HEADER_KEY headers on the response. However, this happens after the RoundTrip function happens, which means that when httpcache records the request headers, it includes the Authorization token from the underlying GH transport. Well this doesn't match the next time the cache lookup happens because the request checking happens BEFORE calling RoundTrip on the underlying transport, which means the request header is missing the Authorization token.
Once I reordered the transports, I was able to observe the cache being utilized much more.

Awesome, thanks for this! I'll try it out and see

The above along with #197 seems to have helped here a lot, closing for now.


Feature - Add a check for dependency review action

Is your feature request related to a problem? Please describe.
The dependency review action lets you proactively block pull requests that introduce dependencies with known vulnerabilities.
GitHub introduced https://github.com/actions/dependency-review-action https://github.blog/2022-04-06-prevent-introduction-known-vulnerabilities-into-your-code/

@ossf/scorecard-maintainers Thoughts about including this in our checks. Either include it part of Dependency check or Vulnerability check.

@azeemshaikh38 / @laurentsimon FYI...
Didn't realize @azeemshaikh38 and @laurentsimon  weren't in the @ossf/scorecard-admins or @ossf/scorecard-maintainers  groups.

list of dependency-related checks we can put in a single check:

[ ] https://github.com/ossf/scorecard/issues/1371
[ ] https://github.com/ossf/scorecard/issues/413
[ ] https://github.com/ossf/scorecard/issues/1508
[ ] https://github.com/ossf/scorecard/issues/874


[FEA]Add tests for reading and writing to delta on Databricks

Is your feature request related to a problem? Please describe.
We need more integration tests to test the reading and writing of delta files on Databricks to make sure plugin working properly with it.
for instance #1197

We probably should do this for open source delta as well. It is just a jar that we download and add as a plugin like our own.

Adding a list of other issues related to Delta testing:

[ ] https://github.com/NVIDIA/spark-rapids/issues/5977
[ ] https://github.com/NVIDIA/spark-rapids/issues/5978
[ ] https://github.com/NVIDIA/spark-rapids/issues/5966


Add distributed lock API support

Describe the proposal
Add methods for distributed lock API.
Main Issue: https://github.com/dapr/dapr/issues/3549

@tmacam this might be a good issue for you to tackle to learn about the Python SDK

This is a gRPC - the code will likely go here:
https://github.com/dapr/python-sdk/blob/master/dapr/clients/grpc/client.py
Unit tests are in /tests
Examples folder acts as both example and integration tests (see Readme.md raw source for how this is done in each example)


Show better force push diff

By default, GitHub will use ... for diff here. Using ... for the comparison will only show the new commit (see image for a better explanation).
Example (...): https://github.com/robertcoopercode/proof-of-concept/compare/5c9a40314c69179021150069eb565fd9095abc3b...12e73d1d9b815e11b39bb89b58470cb616f0ad44
Example (..): https://github.com/robertcoopercode/proof-of-concept/compare/5c9a40314c69179021150069eb565fd9095abc3b..12e73d1d9b815e11b39bb89b58470cb616f0ad44
The second is more likely what you'd want for a force push.
You could also use regex for this to be more foolproof, but I figured just a simple replacement would be sufficient as you can't have a repo, commit hash, or account/org name containing ....

Thanks for your interest


Added a useful link

Have added a useful resource about the array in python from the scaler topics in the reference section.

Awesome thanks @Vaishnaviamirayada !


local variable 'num_classes' referenced before assignment

https://github.com/anosorae/IRRA/blob/6caff747d664965432d7c090f2522f38b76e71ca/datasets/build.py#L170

We have already fixed this issue, please ensure you are running the up-to-date version of code.


Can't perform bulk delete due to 'Cannot find field _selectExpression on type Enumerator' exception

Trying simple bulk delete on my model:
await _context.Availabilities.Where(av => av.HotelId == request.HotelId
                                          && av.Date > expectedHorizonDate).BatchDeleteAsync(cancellationToken)

with EF Core 3.1, MSSQL 2019 server.
this code fails with exception
System.InvalidOperationException : Cannot find field _selectExpression on type Enumerator
   at EFCore.BulkExtensions.IQueryableExtensions.ToSql[TEntity](IQueryable`1 query)
   at EFCore.BulkExtensions.BatchUtil.GetBatchSql[T](IQueryable`1 query, DbContext context, Boolean isUpdate)
   at EFCore.BulkExtensions.BatchUtil.GetSqlDelete[T](IQueryable`1 query, DbContext context)
   at EFCore.BulkExtensions.IQueryableBatchExtensions.BatchDeleteAsync[T](IQueryable`1 query, CancellationToken cancellationToken)

This is directly related to the 3.1 .NET Core update. This works fine in EF Core 3.0, but tanks (with the error above) when I upgrade EF Core to 3.1.

its the same on BulkUpdate as well..

same with SQLite

Same problematics on my side

NuGet 3.1.0 published


Small fixes to the Web Share Target API article

What's changed, or what was fixed?
In the Registering as a Share Target with the Web Share Target API article,

Removed extra "you" in a sentence.
Added missing commas.
Replaced a comma with a period when starting a new sentence.

CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/


[Gssoc'21 ]Enhancing the social media icons in footer

Is your feature request related to a problem? Please describe.
I would like to add some cool and good looking social media icons in footer I had already done this .
It is looking like this now.

@vigneshshettyin kindly assign me this issue so I can create a PR

Okay. Assigning to you @arpit456jain

@vigneshshettyin kindly review my PR


Use Ecto.embedded_dump/2

Simplifies Code by using functionality maintained by Ecto

PS: If that PR is accepted, I'll send another one for Ecto.embeded_load/3

Looks amazing. I'll work on the library in the coming days. Busy on something else now for a little while. Get back to you soon.

@mathieuprog Any updates?

Sorry for the delay. This is an amazing PR. Can I just know what this is for?
def embed_as(_other, _params), do: :self
Commenting it out will make the tests still pass. If we can't think of any failing test, we shouldn't have this function clause I think.

@mathieuprog I seem to have copied that from somewhere. I've removed the second clause.

I would leave the pattern matching to json like you did before. More explicit.

@mathieuprog We'll have to take any atom as a parameter. I can leave two clauses that both return :dump (one for json, one for _) or one clause like it is now.

(Default is :self)

What other atom than :json is possible to receive for this library? It will always be :json as to my understanding. That's why all the tests pass using only :json. Try to remove the other clause and it works.

@mathieuprog Not really. The user can call Ecto.embedded_dump on any schema he has which includes a field using this library.
For example one could write an XML export of a schema using this functionality.
Ecto internally uses it to serialize embed JSON fields with format set to json.

Thanks. So the last commit is correct: we should always let our custom dump be called. Not use :self otherwise nested polymorphic embeds won't work. Did I get this right?

I think that's correct :+1:

embed_as is still a little obscure to me, and that's why I missed this huge improvement in the code...
You mentioned somewhere you will fix something else? load?

@mathieuprog I'll probably do a PR for load as well. Might take some time though until I find some free time.


About this, how can I use it？

I downloaded the benchmark file, but I don't know how I should use it. Could you please tell me? Thanks!
“We provide an out-of-the-box evaluation toolbox for the VPS task, which is written in Python style. You can just run it to generate the evaluation results on your custom approach. Or you can directly download the complete VPS benchmark including prediction map of each competitor at download link: OneDrive / Baidu Drive (Password: 2t1l, Size: 5.45G).”

Please download these segmentation results, and use this toolbox to evaluate them.

I mean I had download the file named "Benchmark", how can  I use it?

I mean this "Or you can directly download the complete VPS benchmark including prediction map of each competitor at download link: OneDrive / Baidu Drive (Password: 2t1l, Size: 5.45G).”" how can I get the prediction map of each competitor in the file named  "Benchmark".

Thank you！problem Sloved！


After 'conda install -c fastai nbdev', an error "‘HTMLExporter’ object has no attribute ‘template_path’" occurred.

converting: /mnt/c/Users/drago/Documents/jupyter/young/00_core.ipynb
‘HTMLExporter’ object has no attribute ‘template_path’
‘HTMLExporter’ object has no attribute ‘template_path’

as mentioned in https://forums.fast.ai/t/htmlexporter-object-has-no-attribute-template-path/80775
That's because the Anaconda's default nbdev version is 0.2.40
' pip3 install -U nbdev' fixed that.
Looking in indexes: http://mirrors.aliyun.com/pypi/simple/
Collecting nbdev

...

Installing collected packages: nbconvert, nbdev
  Attempting uninstall: nbconvert
    Found existing installation: nbconvert 6.0.7
    Uninstalling nbconvert-6.0.7:
      Successfully uninstalled nbconvert-6.0.7
  Attempting uninstall: nbdev
    Found existing installation: nbdev 0.2.40
    Uninstalling nbdev-0.2.40:
      Successfully uninstalled nbdev-0.2.40

...

Successfully installed nbconvert-6.0.7 nbdev-1.1.12
(base) ➜  young git:(master) ✗ nbdev_build_lib
Converted 00_core.ipynb.
Converted index.ipynb.
(base) ➜  young git:(master) ✗ nbdev_build_docs
converting: /mnt/c/Users/drago/Documents/jupyter/young/00_core.ipynb
converting: /mnt/c/Users/drago/Documents/jupyter/young/index.ipynb
converting /mnt/c/Users/drago/Documents/jupyter/young/index.ipynb to README.md
(base) ➜  young git:(master) ✗

When I run 'pip3 install nbdev', it not worked on ubuntu20.04 under wsl2. So I install nbdev by install anaconda first, then use 'conda install -c fastai nbdev', it succeed. and then because of default nbdev version is 0.2.40 in conda, an error "'HTMLExporter' object has no attribute 'template_path'" occured. But 'pip3 install -U nbdev' fixed that.
Strongly suggest everyone should run 'pip3 install -U nbdev' after install nbdev by anaconda.

Thanks for reporting this issue

Thanks for reporting this issue

You are welcome.

We fixed this issue yesterday by bumping the Anaconda release to the latest version


boards: arm: Add adafruit_itsybitsy_nrf52840 board

Adds support for the Adafruit ItsyBitsy nRF52840 Express.
This board ships with the UF2 bootloader, so the device has been set up so that Zephyr applications are flashed the same way that other (Adafruit) firmware is flashed with the UF2 bootloader.
This has been tested locally, and the button, blinky and led_apa102 samples run without problems.
Signed-off-by: Embla Flatlandsmo<EMAIL_ADDRESS>

@Embla-Flatlandsmo can you please address the review comments? Thanks!

@nordicjim @anangl Had some issues after updating the documentation to refer to the cdc-acm console and the logging sample. Thanks for being patient and helping me out so much! 😻


[Doc] 3.1-add-col-mode-partial-update

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

@mergify backport branch-3.1


make safe safer

case_ ∷ ∀ a. Variant () → a
Variant () + case_ is like Void + absurd
Either Void a ~ a ~ Either (Variant ()) a

Sorry, I missed this PR. GH doesn't necessarily subscribe you to your own repos, and I had already made this change on master. Thanks for the contribution, though!


Global commit list

It would be nice to be able to see a commit list, but for all repos at once.

Thanks for the suggestion, but I'm not personally enthusiastic about this - it could be incredibly slow if you had more than a tiny number of repos.
Out of interest, what's the use case?

We have several smaller repos and it would be useful to see the latest commits in one place.
(We also have Redmine where I've configured it to show commits in the "projects changes list", so to have it in Bonobo is really just "nice to have".)


Do not run mapper/cx_direction if check_map/check_direction set in property set

The default transpiler set(s) include CheckMap, but only to determine whether or not to apply the DenseLayout pass.
It should be possible to condition the mapper pass on the value of property_set['is_swap_mapped'] . Likewise for CheckCnotDirection and CheckDirection.
This should give a compile time speed up without changing the generated circuits. Should be implemented after extraction of layout modification from mapper passes.

I will start working on this after https://github.com/Qiskit/qiskit-terra/pull/2316 gets merged or rejected, because they overlap.

#2316 merged... removing on hold

I think #2852 fixes this issue.

This is fixed by #2852 and #2883 .

#2852 and #2883 still pending... I'm reopening this.


Rails view helpers

There are a number of Rails view helpers which we will need to support in some way or another.
The helpers that produce strings should be fine to just include. But helpers that product markup will need to be handled carefully. I expect most of these could be shipped in the form of a small standard library or components for Rails.
In particular, we may need our own form component.

I’m closing this in favour of opening issues for the specific view helpers that are required.


[TEST] Playing around with fixed dipole orientation in a discrete source space

Trying to see what it takes to perform MxNE using a source space that consists of two dipoles with fixed orientation. Currently, MNE doesn't support forward models with fixed orientation that are not of type 'surface'. In this PR I'm disabling these checks and see what happens.
Here is some example code that creates such a forward model and attempts to perform MxNE source estimation with it:
import mne
import numpy as np
import matplotlib.pyplot as plt

# Read phantom data
data_path = mne.datasets.brainstorm.bst_phantom_elekta.data_path(verbose=True)
raw = mne.io.read_raw_fif(f'{data_path}/kojak_all_200nAm_pp_no_chpi_no_ms_raw.fif')
events = mne.find_events(raw, 'STI201')

# Extract evoked data for 2 dipoles
epochs = mne.Epochs(raw, events, [1, 17], tmin=-0.1, tmax=0.1, baseline=(-0.1, -0.05))
evoked_dip1 = epochs['1'].average()
evoked_dip2 = epochs['17'].average()

# Create an evoked with both dipole active at the same time
evoked = evoked_dip1.copy()
evoked.data += evoked_dip2.data

# Fit two dipoles
cov = mne.compute_covariance(epochs, tmax=-0.05)
bem = mne.make_sphere_model(r0=[0, 0, 0], head_radius=0.08)
dip1, _ = mne.fit_dipole(evoked_dip1.copy().crop(0.035, 0.035), cov, bem)
dip2, _ = mne.fit_dipole(evoked_dip2.copy().crop(0.035, 0.035), cov, bem)

# Collect the dipoles in a single `Dipole` object
dips = mne.Dipole(
    times=np.hstack((dip1.times, dip2.times)),
    pos=np.vstack((dip1.pos, dip2.pos)),
    ori=np.vstack((dip1.ori, dip2.ori)),
    amplitude=np.hstack((dip1.amplitude, dip2.amplitude)),
    gof=np.hstack((dip1.gof, dip2.gof)),
    name=None,
    conf=None,
    khi2=np.hstack((dip1.khi2, dip2.khi2)),
    nfree=dip1.nfree,
)

# Compute dipole timecourses using MxNE
fwd, _ = mne.make_forward_dipole(dips, bem, evoked.info)
stc = mne.inverse_sparse.mixed_norm(evoked, fwd, cov)

# Plot the timecourses
plt.plot(evoked.times, stc.data.T)

Currently, MNE doesn't support forward models with fixed orientation that are not of type 'surface'.

This works for me:
>>> import mne
>>> info = mne.io.read_info(mne.datasets.sample.data_path() / 'MEG' / 'sample' / 'sample_audvis_raw.fif')
>>> src = mne.setup_volume_source_space(pos=dict(rr=[[0, 0, 0.055]], nn=[[1, 0, 0]]))
>>> bem = mne.make_sphere_model(info=info)
>>> fwd = mne.make_forward_solution(info, src=src, bem=bem, trans=None)
>>> fwd_fixed = mne.convert_forward_solution(fwd, force_fixed=True)
>>> fwd_fixed['sol']['data'].shape
(366, 1)
>>> fwd['sol']['data'].shape
(366, 3)

But indeed with depth weighting, loose etc. maybe we do need to change our checks to be in ('surface', 'discrete') rather than == 'surface'. I think it's okay to shift to fixed ori for surf and discrete, but not volume.

Ah, I needed to clarify better: constructing a volume or discrete forward model with fixed dipole orientations is no problem at all. It's when you attempt to use it to perform source modeling. the forward._prepare_forward function has a series of checks.

What makes volume special in this regard?

When doing force_fixed=True:

For a surface src, things are fine (it means use the surface normal).
For a discrete src, I think we can assume we're in an expert use case and trust they set their normals properly (and suffer the consequences if they did not)
For volume src, 99%+ of the time it's going to be a mistake. The volume normals in setup_volume_source_space are just +Z. If you really want this, you should make a discrete source space with these normals.

note that with so few dipoles mne.inverse_sparse.mixed_norm should be used with alpha almost set to 0.

In that case, would plain MNE also work here? What is the added benefit of the sparse solver?

(@larsoner recommended MxNE in the forum thread)

you will get a set of dipoles instances with MxNE code

Message ID: @.***>

With explained variance per dipole (though you could figure it out for MNE the same way I think). Otherwise, assuming you use a very small lambda2 for MNE, the total exp var should be similar. Would make a nice little unit test!

Would make a nice little unit test!

A test that passes:
import mne
import numpy as np
import matplotlib.pyplot as plt

# Read phantom data
data_path = mne.datasets.brainstorm.bst_phantom_elekta.data_path(verbose=True)
raw = mne.io.read_raw_fif(f'{data_path}/kojak_all_200nAm_pp_no_chpi_no_ms_raw.fif')
events = mne.find_events(raw, 'STI201')

# Extract evoked data for 2 dipoles
epochs = mne.Epochs(raw, events, [1, 17], tmin=-0.1, tmax=0.1, baseline=(-0.1, -0.05))
evoked_dip1 = epochs['1'].average()
evoked_dip2 = epochs['17'].average()

# Create an evoked with both dipole active at the same time
evoked = mne.combine_evoked([evoked_dip1, evoked_dip2], [1, 1])

# Fit two dipoles
cov = mne.compute_covariance(epochs, tmax=-0.05)
bem = mne.make_sphere_model(r0=[0, 0, 0], head_radius=0.08)
dip1, _ = mne.fit_dipole(evoked_dip1.copy().crop(0.035, 0.035), cov, bem)
dip2, _ = mne.fit_dipole(evoked_dip2.copy().crop(0.035, 0.035), cov, bem)

# Collect the dipoles in a single `Dipole` object
dips = mne.Dipole(
    times=np.hstack((dip1.times, dip2.times)),
    pos=np.vstack((dip1.pos, dip2.pos)),
    ori=np.vstack((dip1.ori, dip2.ori)),
    amplitude=np.hstack((dip1.amplitude, dip2.amplitude)),
    gof=np.hstack((dip1.gof, dip2.gof)),
    name=None,
    conf=None,
    khi2=np.hstack((dip1.khi2, dip2.khi2)),
    nfree=dip1.nfree,
)

# Compute dipole timecourses using MxNE
fwd, _ = mne.make_forward_dipole(dips, bem, evoked.info)
inv = mne.minimum_norm.make_inverse_operator(evoked.info, fwd, cov, fixed=True, depth=0)
stc_mxne = mne.inverse_sparse.mixed_norm(evoked, fwd, cov)
stc_mne = mne.minimum_norm.apply_inverse(evoked, inv, method='MNE')

# Plot the timecourses
plt.plot(evoked.times, stc_mxne.data.T)
plt.plot(evoked.times, stc_mne.data.T)

pretty reassuring ! thx @wmvanvliet for the code snippet

Closing in favor of 10464


Pointer offset in onTap.

How about pass pointer Offset to onTap like onDoubleTap?

@MrNektom
Thank you for the good idea 👍
I will try it.


Update repository after transfer

See https://github.com/senzing-garage/garage-roadmap/issues/3

Pull requests:

https://github.com/senzing-garage/knowledge-base/pull/70