[SPARK-31818][SQL] Fix pushing down filters with java.time.Instant values in ORC

What changes were proposed in this pull request?
Convert java.time.Instant to java.sql.Timestamp in pushed down filters to ORC datasource when Java 8 time API enabled.
Why are the changes needed?
The changes fix the exception raised while pushing date filters when spark.sql.datetime.java8API.enabled is set to true:
java.lang.IllegalArgumentException: Wrong value class java.time.Instant for TIMESTAMP.EQUALS leaf
 at org.apache.hadoop.hive.ql.io.sarg.SearchArgumentImpl$PredicateLeafImpl.checkLiteralType(SearchArgumentImpl.java:192)
 at org.apache.hadoop.hive.ql.io.sarg.SearchArgumentImpl$PredicateLeafImpl.<init>(SearchArgumentImpl.java:75)

Does this PR introduce any user-facing change?
Yes
How was this patch tested?
Added tests to OrcFilterSuite.

@cloud-fan @HyukjinKwon @dongjoon-hyun Please, review this PR. It is similar to https://github.com/apache/spark/pull/28261 but for timestamps.

Merged build finished. Test PASSed.

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

Test build #123084 has started for PR 28636 at commit 5290d96.

Test build #123086 has started for PR 28636 at commit e24fb31.

Merged build finished. Test PASSed.

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

Test build #123084 has finished for PR 28636 at commit 5290d96.

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

Merged build finished. Test PASSed.

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

jenkins, retest this, please

Test build #123093 has started for PR 28636 at commit e24fb31.

Merged build finished. Test PASSed.

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

Test build #123086 has finished for PR 28636 at commit e24fb31.

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

Merged build finished. Test PASSed.

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

Test build #123098 has started for PR 28636 at commit 2773ceb.

Merged build finished. Test PASSed.

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

Test build #123093 has finished for PR 28636 at commit e24fb31.

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

Merged build finished. Test PASSed.

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

Test build #123098 has finished for PR 28636 at commit 2773ceb.

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

Merged build finished. Test PASSed.

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

Merged to master/3.0. Thank you, @MaxGekk , @cloud-fan , @seanli-rallyhealth .


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-loadtestservice-loadtest
Module Details
Requested by the AZD team: https://github.com/Azure/Azure-Verified-Modules/issues/261
Needs module owner.
CC: @jongio
Do you want to be the owner of this module?
No
Module Owner's GitHub Username (handle)
No response
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

@mbilalamjad I am interested in taking ownership of this module.

Thanks @hannah-leland, double checking with @PmeshramPM offline, will update accordingly

Hi @LaurentLesle,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

Hi @LaurentLesle,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Requested @LaurentLesle to share an update here

Planning to start next week
On Tue, Mar 5, 2024 at 3:35 PM Bilal Amjad @.***> wrote:

Requested @LaurentLesle https://github.com/LaurentLesle to share an
update here
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/Azure-Verified-Modules/issues/339#issuecomment-1978125845
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABD4AEGHWLBANASGQK5MHCDYWVYTXBFKMF2HI4TJMJ2XIZLTTCBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2TSMBXG43TANBYHCSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRVHEZTMNJQHAZTSNFENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWVDKOJTGY2TGMJSGAZ2I3TBNVS2S2DBONPWYYLCMVWIFJLWMFWHKZNKGYYDIOJSGUZDONRQURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2UNRSGA4TSNZYHE3DDJDOMFWWLKLIMFZV63DBMJSWZLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOLYFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE3DMMBSGEYTKNZWQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRSGAYDSMZTHAZTKM4CUR2HS4DFUVWGCYTFNSSXMYLMOVS2UNJZGA3TONZQGQ4DRAVEOR4XAZNFNRQWEZLMUV3GC3DVMWVDKOJTGY2TAOBTHE2IFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2TSMZWGUZTCMRQGOBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGYYDIOJSGUZDONRQQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRWGIYDSOJXHA4TMMNHORZGSZ3HMVZKMY3SMVQXIZI
.
You are receiving this email because you were mentioned.
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
.

Development started

Pending approval and release to progress -> https://github.com/Azure/terraform-azurerm-naming/pull/121

@LaurentLesle Is there any progress on this issue so far?

Can you find a new owner?
On Tue, 2 Jul 2024 at 18:24, microsoft-github-policy-service[bot] <
@.***> wrote:

Important
@LaurentLesle https://github.com/LaurentLesle, this issue has not had
any activity in the last 3 weeks. Please feel free to reach out to the
AVM core team should you have any questions or need any help with the
development of this module.
Tip
To silence this notification, provide an update every 3 weeks on the
Module Proposal issue, or add the "Status: Long Term ⏳" label.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/Azure-Verified-Modules/issues/339#issuecomment-2202670604
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABD4AEGXZIADOWW6LQ6FDRLZKJ5WDBFKMF2HI4TJMJ2XIZLTTGBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2TSMBXG43DSNZXGSSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRVHEYDONZXGA2DQOFENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWVDKOJTGY2TAOBTHE2KI3TBNVS2S2DBONPWYYLCMVWIFJLWMFWHKZNKGU4TGNRVGMYTEMBTURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2UNRQGQ4TENJSG43DBJDOMFWWLKLIMFZV63DBMJSWZAVFOZQWY5LFVI3DEMBZHE3TQOJWGGSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44YQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJWGYYDEMJRGU3TNAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMBQHEZTGOBTGUZYFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2TSMBXG43DSNZXGSBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGU4TANZXG4YDIOBYQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRVHEZTMNJQHAZTSNECUR2HS4DFUVWGCYTFNSSXMYLMOVS2UNJZGM3DKMZRGIYDHAVEOR4XAZNFNRQWEZLMUV3GC3DVMWVDMMBUHEZDKMRXGYYIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI3DEMBZHE3TQOJWGGTXI4TJM5TWK4VGMNZGKYLUMU
.
You are receiving this email because you were mentioned.
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
.


It is not translatable using i18n

https://github.com/CircuitVerse/CircuitVerse/blob/59bf87ccb3f9cc19443e72af9084077c6334566f/app/views/lti/open_incv.html.erb#L17

@ayan-biswas0412 @pavanjoshi914 I will make new key in en.yml file for making it translatable.

so I go ahead?

should I go ahead?

yah sure you can do that

not translatable?  gives different meaning use proper context in issue title
Please go ahead


Latest release 3.3.1 fails to deploy to pypi

see job log: https://travis-ci.org/James1345/django-rest-knox/jobs/409780228
HTTPError: 400 Client Error: User 'xxx.xxx' does not have a verified primary email address. Please add a verified primary email before attempting to upload to PyPI. See https://pypi.org/help/#verified-email for more information.for more information. for url: https://upload.pypi.org/legacy/
Original author was informed by me.

ping @James1345

Feel free to drop him an email, you can find it here:
https://github.com/James1345/django-rest-knox/blob/master/setup.py#L28

Thing is he should have already received multiple email regarding this issue and did not respond to any of those (Pypi email confirmation, Github notifications...)

he does reply to personal emails relatively quick. People tend to filter away auto-emails into folders. At least I do :)

I sent an email.

@James1345 replied

PyPi seem to have changed something and I can't get back into my old account. I don't know why yet, but it seems to have completely lost my email address as one that's registered to an account.
I'm contacting PyPi support to see if I can get back into the account

Okay, email address verified, the builds should succeed now hopefully
On Thu, 30 Aug 2018 at 12:56, Raphaël Stefanini<EMAIL_ADDRESS>wrote:

@James1345 https://github.com/James1345 replied
PyPi seem to have changed something and I can't get back into my old
account. I don't know why yet, but it seems to have completely lost my
email address as one that's registered to an account.
I'm contacting PyPi support to see if I can get back into the account
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/James1345/django-rest-knox/issues/107#issuecomment-417293035,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkjesBjRF1EQFaaQM_zu7LxJkJMn3u_ks5uV9LhgaJpZM4VnxJj
.

Travis build went through but show Skipping a deployment with the pypi provider because this is not a tagged commit

Good spot. Need to force it to try a pypi deployment somehow...
On Tue, 4 Sep 2018 at 12:37, Raphaël Stefanini<EMAIL_ADDRESS>wrote:

Travis build went through but show Skipping a deployment with the pypi
provider because this is not a tagged commit
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/James1345/django-rest-knox/issues/107#issuecomment-418335006,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkjehun2Bc9OZlRzo4kVyGo-2j7rYx7ks5uXmYBgaJpZM4VnxJj
.

@James1345  any update on this?

ping

next release should force a deployment

just tagged master as 3.3.1, hopefully already on its way to pypi

Release failed :( @James1345
HTTPError: 403 Client Error: Invalid or non-existent authentication information. for url: https://upload.pypi.org/legacy/
django_rest_knox.egg-info/PKG-INFO already exists, no checkout
django_rest_knox.egg-info/SOURCES.txt already exists, no checkout
django_rest_knox.egg-info/dependency_links.txt already exists, no checkout
django_rest_knox.egg-info/requires.txt already exists, no checkout
django_rest_knox.egg-info/top_level.txt already exists, no checkout
Could not restore untracked files from stash entry
PyPI upload failed.
failed to deploy

https://travis-ci.org/James1345/django-rest-knox/jobs/434573815

@James1345 did you forget to update your password in .travis.yml after you recovered your account?

That's not impossible

Hey guys,
Would be nice to merge #109 with a successful pypi release 🎉
@James1345 would you have a bit of time to create a PR with the updated credentials?
Cheers 🤓

ping @James1345

I'll give it a poke this evening
On Tue, 9 Oct 2018, 07:42 belugame<EMAIL_ADDRESS>wrote:

ping @James1345 https://github.com/James1345
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/James1345/django-rest-knox/issues/107#issuecomment-428078222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkjeukaaNfVb4vUX-KcPZv9JagOHVpIks5ujEU3gaJpZM4VnxJj
.

@James1345 any chance we could see this moving forward or maybe you can delegate some permissions to @belugame ?

:exclamation:  We are unable to release since almost 3 months now, @James1345
At the moment the project sees a lot of valuable contributions from motivated coders new to the project, far more than in the past. It's a shame that we cannot thank them with regular releases to pypi. If you can't find the time for reestablishing the release workflow, I guess we have to republish it under a new name sadly. :-/

I did the thing. Is it still not working?

Oh I wasn't aware you did. Just made a new release. It failed sadly:
https://travis-ci.org/James1345/django-rest-knox/jobs/445302892
HTTPError: 403 Client Error: Invalid or non-existent authentication information. for url: https://upload.pypi.org/legacy/
django_rest_knox.egg-info/PKG-INFO already exists, no checkout
django_rest_knox.egg-info/SOURCES.txt already exists, no checkout
django_rest_knox.egg-info/dependency_links.txt already exists, no checkout
django_rest_knox.egg-info/requires.txt already exists, no checkout
django_rest_knox.egg-info/top_level.txt already exists, no checkout
Could not restore untracked files from stash entry
PyPI upload failed.
failed to deploy

On it right now, just reminding myself how travis works

Okay, I've re-reset the password. I'm doing a new release to try to make it deploy

@belugame it successfully deployed the first build, but then the others fail when it tries to deploy again with the other django versions... not sure of the solution yet

https://travis-ci.org/James1345/django-rest-knox/builds/445317311

Fixing it now with build stages

Going to leave it for tonight. It looks odd, but the deployment at least succeeds. I'll properly secure another new password some other day (leave this issue open so I remember)

It worked for the 2.7 config. The issue is that each config in the test
matrix is trying to deploy, which causes the file conflict.
Because we build a universal package, it should be fine to install 3.4.0
from pypi, we're just going to get this error every time we try to deploy
On Wed, 24 Oct 2018, 12:23 Jonathan Liuti<EMAIL_ADDRESS>wrote:

I don't believe it's related to the manifest.
The log says:
Uploading distributions to https://upload.pypi.org/legacy/
Uploading django_rest_knox-3.4.0-py3-none-any.whl
100%|██████████████████████████████████████| 19.0k/19.0k [00:01<00:00, 14.6kB/s]
Uploading django-rest-knox-3.4.0.tar.gz
100%|██████████████████████████████████████| 16.6k/16.6k [00:00<00:00, 44.1kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 400 Client Error: File already exists. See https://pypi.org/help/#file-name-reuse for url: https://upload.pypi.org/legacy/
And then reading on https://pypi.org/help/#file-name-reuse, it seems that
you cannot re-use the same filename twice - I guess to avoid replacing
releases with new content and force you to bump your version instead.
And I believe it has been like that for a long time:
https://travis-ci.org/James1345/django-rest-knox/builds/346312886
Do you know if it ever worked ?
Cheers
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/James1345/django-rest-knox/issues/107#issuecomment-432617470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkjerQT7kJTIp-xEAs5jvPQYPAnkEivks5uoE3HgaJpZM4VnxJj
.

This is precisely what I'm stating, yes.

Created #138 to follow up on this, that way we can close this as the main issue is fixed.

thank you @johnraz


Code Quality: Move App.Commands & App.Contexts to App.Data

Code Quality: Move App.Commands & App.Contexts to App.Data
Motivation & Context

Improved readability

WarningPlease do not review code lines that I did not changed. I cannot make more diff. If there're more codes that are preferred to change, I will do that and mark that PR as the final one for that stage.

PR Checklist

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Related #4180
[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[ ] Are there any other steps that were used to validate these changes?

Screenshots
None

FYI @Poker-sang it is failing again. I left a comment in https://github.com/files-community/Files/pull/12471 .

@d2dyno1


Add continuous integration on Travis

@allanlw should check this Dockerfile before this gets merged.
Fixes #40

PTAL I removed my flag check and renamed the nographic flag


#559 Address Retry ordering issues and refactor the logic

Thanks for your pull request.  Please review the following guidelines.

[x] Title includes issue id.
[x] Description of the change added.
[x] Commits are squashed.
[x] Tests added.
[x] Documentation added/updated.
[x] Also please review CONTRIBUTING.md.

Description:

Fixed ordering issue for retried elements.
Fixed not completing the stage until there is further demand from downstream.
A retried element with a lower retry time should be able to go to the head of the retry queue
Optimizations on method calls and map accesses.
Stream should complete when upstream completes. Should not require a new demand from downstream to complete (the tests were requiring an extra demand from sink).
Dropped Overflow strategy support as anything other than backpressure  does not make sense for Retry.  It is not really a buffer, any element in retryregistry is actually inflight, which we cannot drop.

Things to do:

Add test case for putting an element to the head of the queue when retry time is sooner than head's.
Go over onDownstreamFinish scenarios.

@akara

Cancelling the scheduler and just rely on the next onPull is a good strategy. But it needs proper documentation.

You mean documentation as in comments or in the actual user facing documentation.  Since it is implementation detail, I'd prefer it to be in the code.
Please see if the latest commit addresses your comments.


Tick labels incorrectly rendered

Hello,
I ran into an issue with tick labels not rendering correctly when using with bootstrap togglable tabs. it would render correctly on the first (active) pane but not on 2nd, 3rd, etc. Images below. The issue happens with both vanilla bootstrap  and ember bootstrap components.

can you produce in a twiddle? I have never seen this problem but then i've not used bootstrap togglable tabs in a while. My guess is that there is something odd happening with flexbox. Are you using Bootstrap 4?

I was checking this project and it looks really neat. On my computer the demo was buggy, though. Every time I clicked on the demo slider on the "Ticks" session, the slider would increase its size. I'm using Firefox 54 (64bits) for Ubuntu.
For Chrome, Version 59.0.3071.115 (Official Build) (64-bit), it works quite well

@rennomarcus any chance you could provide a short video or screenshot? Would be interested in seeing what you're seeing.

Sure. See if it makes sense the screenshot I took

Hi,
I too am facing the same issue.
Please see the snapshot.
The tick labels are not getting rendered properly.


Bug: Sprig Gallery doesn't correctly render game image

Same error observed in Breakout is appearing in all recent ones, no longer a one-off error

background isn't rendering

Yeah, I noticed that problem as well. The only solution I can think of is just getting images for the games with backgrounds. There might be some way to include the setBackground() function in the card though.

We can fix the thumbnail generation code.

And we have. Thanks for the prompt.


⚠ ClamAV has degraded performance

In 221a6d5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 234 ms

Resolved: ClamAV performance has improved in e1cd9e8 after 11 minutes.


Fix markdown content out of border & Empty table should not show

Need

markdown section log content should not overflow section borders
empty table should not show

Before

After

pdf:
2021-12-19_12-09-27_test.pdf

@idanizi-panw can you handle comments here ?

@Bars92 I did a fix that now compatible with previous versions. please approve 🙏

@idanizi-panw can you handle comments here ?

@meirwah yes. just uploaded new fixes

@idanizi-panw can we merge ?

@idanizi-panw can we merge ?

@meirwah merged


Do not use cytoscape global variable in cueUtilities.

Fix one more issue with usage of global 'cy' variable. Fixed it by getting cytoscape instance from the container.

Thanks for your contribution. :grinning: :


Fix Nexus shutdown order

Description
During graceful shutdown, make sure to:

disconnect any remaining connections
ensure the server stops receiving connections
give time for  "disconnected" handlers to execute before removing Redis resources

as discussed offline, let's work on rejecting the new connection requests instead of closing them after the graceful shutdown.


Cannot schedule player instances in transport (React)

Hey,
I'm not sure why I can't get this to work, have spent hours on this and can't seem to get it to work correctly.
I'm creating a DAW and trying to get the basics of the transport setup. It is just not playing anything.
Here's a link to the codesandbox with a minimal example

So i have updated the example, it seems that the Transport is somehow linked to the time the page is loaded, and adds this amount of time to the scheduling.
e.g.
Page loads.
10 seconds later the user presses "Start"
The Transport schedule everything +10 seconds.

Tone.js requires a user interaction to start and the transport time will start at this point (which is different to the audio context time, which will start on page load - i think).


nixos/tailscale: add extraUpFlags option

Description of changes

Things done

Built on platform(s)

[x] 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.11 Release Notes (or backporting 23.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

I feel like extraUpFlags is a better name than autoconnectOptions?

The PR Title also needs to be updated from autoconnectOptions to extraUpFlags.

Thanks for the reviews.
@drupol There are over 20 flags we can pass to tailscale up so I'm going to go with extraUpFlags.
@Kranzes Done, also changed pkgs.tailscale to cfg.package.


FR: Support multiple prices for a single feature, based on interval

What are you trying to do?
SaaS pricing often allows for a discount for longer billing terms.
Tier currently supports an interval for a plan's price.
Tier should support multiple intervals for a single plan, each with their own corresponding price.
How should we solve this?
Stripe supports multiple prices per product. This is different from multi-currency prices.
From Stripe docs:

Create multiple prices for a single product if you’re selling the same item at different price points. For example, if you offer a subscription tier at monthly and yearly rates, create one product for the tier and one price for the monthly rate and another for the yearly rate.

What is the impact of not solving this?
Annual pricing is very prevalent and often one of the first things vendors seem to want to do to adjust their pricing.
It is one of the first things you see recommended as you look at ways to improve pricing.
Anything else?
This should be implemented before #119 as it may impact the implementation of that feature.

In the recent past we discussed trying fancy things in pricing.json but ultimately kept ending up at: a) use a loop / list compressions to generate these b) do (a) in the WYSIWYG, or c) copy and paste a plan by hand and give it a new name like plan:pro:yearly@1.
It might be worth considering some syntax in the plan name that automatically implies the interval, but that might get tricky/confusing if the interval is set and and the interval in the name does not match, although we could make it an error to not name it correctly.
If we do go down the path, I would argue we lean in hard to it and require the interval be in the name and not imply any defaults.
However, it could be a slippery slope considering currency and thinking about it the same way.
I'd like to spend a little time with #119 before jumping into this. There may be a way that already exists as things are today and fixing #119 might be a documentation issue, that but a small additional change to tier. I'm just not familiar enough with it ATM to know how best to proceed here yet.
I'll this ticket updated as my research progresses.

Also: Do we automatically update the Title for the price as well? (e.g. Convert Pro (Monthly) - Temperature)

https://stripe.com/docs/billing/subscriptions/multiple-products#restrictions
Posting this as I think it adds ambiguity to the decision.


onNotificationRemoved() not fired when bubble visible

On the latest dev version, when a bubble is showing, onNotificationRemoved() will not fire until the bubble is removed. Not sure whether this is a bug or not. I tested this with the wechat decorator specifically.

I think that's the intented behavior in AOSP.
Nevolution just forwards the onNotificationRemoved() call.

I thought that might be the case!


Transcripomics heatmap doesn't work for host data

The heatmap for transcripomics genes doesn't work for host data.

@maovt is this the one you recently fixed?

yes


[Bug] When I submit a jar package using the spark engine, I cannot view the submission history

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-engineconnn-plugin
Steps to reproduce

Use the once mode, execute the spark engine, and submit the jar package

Expected behavior

I want to view the Spark Jar submission records through Linkis Console

Your environment

Linkis version used: 1.4.0
Environment name and version:

hdp-3.1.4
spark-3.2.1
scala-2.12.17

Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

The Linkis Console does not support viewing. You can view upload records through logs.

I just want to view the submission record, not the detailed log. Maybe this is not a bug, should I raise a feature issue again?

提供最新版DataSphereStudio全家桶安装服务。
包括（DataSphereStudio, Linkis, Exchangeis(Datax, Sqoop), Scriptis, Streamis(Flink), Visualis, DolphinScheduler)

另外包含 元数据，数据安全，数据质量，数据血缘。（这些都是DataSphereStudio不自带的服务）
包含hadoop集群搭建（hive, spark, flink, kafak, kylin）
提供上述所有系统二次定制开发服务
提供系统搭建运维疑难问题解决

添加备注，DSS大数据
持续为DataSphereStudio开源贡献力量


Keymaps overlays not working reliably

When enabling the "show only keys which are listed in the keymaps folder", carnac seems to only show the first keypress that happens once the application is launched, and doesn't show subsequent keypresses. Oddly enough, I found that if you click on the application window then carnac will show one more keypress in the overlay, but then not subsequent keypresses. It's almost like the app gets confused after the first keypress and somehow by clicking on the window it resets the state or something and the app then resumes normal behavior, but only for 1 keypress.

Disregard. I accidentally downloaded an old version of the app


0.1.17b3 rollup on MacOS

Great thanks for tonight's build. I've noticed a couple things thus far:

txt_overlay_format is implemented ideally, kudos!
the title_screen_map switch cannot seem to be triggered, though I think #154 was going to be rolled into this one?
disabling GPU acceleration - a necessity for me - seems to have a spooky and undesirable effect on the resulting filename (see #150, just updated)

For running on Apple Silicon try the following:

Download Apple Silicon ffmpeg from here: https://www.osxexperts.net/ffmpeg44arm.zip
You might need to sign after downloading (also see https://www.osxexperts.net/)

xattr -cr <pathtotheffmpegfile>
codesign -s - <pathtotheffmpegfile>

Now run tesla_dashcam providing parameter --ffmpeg with the full path/filename where you put the ffmpeg you just downloaded.

Not something I can test but hopefully with a native compiled ffmpeg it will work better. :-)

Okay, I've re-encoded the same clip on my M1 Mac Mini as described in #150 yesterday evening, once with --no-gpu, once with the ARM-compiled ffmpeg without --no-gpu, and once with both switches:
--no-gpu: 379.5MB, 11:05 duration, 5m 16s processing time
ARM ffmpeg : 1.23GB, 7661:04:24 duration, 2m 25s processing time
--no-gpu & ARM ffmpeg: 296.3MB, 11:05 duration, 3m 6s processing time
Visual quality between first and third clips appears identical. Smaller file size and a ~40%? reduction in processing time - very nice indeed!

So the ARM ffmpeg without --no-gpu currently does not work either correct?
But the ARM ffmpeg with --no-gpu works and runs faster. Running faster would make sense as it does not run in Rosetta at that time. Size reduction is a bit surprising but if clips appear identical then definitely bonus. :-)

That is correct - ARM ffmpeg only, without --no-gpu, produces the same "flip book"-style video that chokes VLC but can be viewed frame-by-frame in Quicktime - no motion. Both switches together appear ideal for M1 silicon (currently).
I moved to Monterey as soon as it was available, though I'm pretty sure I only noticed this "problem" since Monterey Beta 4 (build 21A5294g), which dropped on July 27. I see there is now a Beta 5 (build 21A5304g) dated today and am working on getting it, to see if this behavior can be replicated.

Hmmm, wondering then if it is using something inside the OS that has a bug in it. At least with the ARM ffmpeg and --no-gpu it runs faster and you get a viewable video. :-)
Going to leave this beta version around for a little bit but if no issues reported then I'll do a release for it.
I am unable right now to compile a Apple Silicon executable for it due to lack of a M1 Mac. :-(. Feel free to donate one, I won't refuse
But at least current executable with separate ffmpeg works.

Sure, I'd be happy to compile one if given instructions. I'd assume this would involve taking 0.1.17.b4 source and marrying it with the ARM ffmpeg to make a single executable?
Separately, the Apple update server is slammed tonight, but I have the Beta 5 update queued for overnight and...fingers crossed.

Do you have any experience with GitHub and Python?
To get a binary:

Download Python, you would want the universal2 installer: https://www.python.org/ftp/python/3.9.6/python-3.9.6-macos11.pkg (I run 3.8 but should work on 3.9.6, otherwise https://www.python.org/ftp/python/3.8.10/python-3.8.10-macos11.pkg)
Retrieve the source from GitHub (go to the Code page, select branch (in this case Dev) and under green code button select "Download Zip).
Unzip it (if downloaded with Safari it would also be unzipped)(i.e. /Users/rmyadsk/Download/tesla_dashcam-dev)
3.Retrieve ffmpeg and put in in Bundles/MacOS within the tesla_dashcam- folder (i.e./Users/rmyadsk/Download/tesla_dashcam-dev/Bundles/MacOS)
Create a Python virtual environment (python3 -m venv /Users/rmyadsk/Download/tesla_dashcam-dev/venv)
Activate the new environment: source /venv/bin/activate (i.e.: /Users/rmyadsk/Download/tesla_dashcam-dev/venv/bin/activate)
Download requirements: pip3 -r requirements.txt (i.e. pip3 -r /Users/rmyadsk/Download/tesla_dashcam-dev/requirements.txt)
Install setuptools and wheel: pip3 install setuptools wheel
Download pyinstaller: pip3 install pyinstaller
Run create_executable.bash (i.e. /Users/rmyadsk/Download/tesla_dashcam-dev/create_executable.bash)

And that should do it I think. Haven't tested these steps.

Okay, grabbed Python 3.9 and 0.1.17b4 via this link. There was no Bundles/MacOS folder in there so I created it and dropped in ffmpeg. Both Python commands completed without error, but pip3 isn't pleased. Believe that was to be "pip3 install -r requirements.txt" as -r alone produces "no such option" - chased my error back to an Xcode command line tools dependency error, so I'm diligently getting an ARM64-compatible Xcode and its tools currently - will let you know how far I get.

So, all good up to step number nine above, wherein there is no create_executable.bash:

rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % source venv/bin/activate
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % pip3 install -r requirements.txt
Requirement already satisfied: python-dateutil>=2.8.1 in ./venv/lib/python3.9/site-packages (from -r requirements.txt (line 1)) (2.8.2)
Requirement already satisfied: tzlocal==2.1 in ./venv/lib/python3.9/site-packages (from -r requirements.txt (line 2)) (2.1)
Requirement already satisfied: requests==2.24.0 in ./venv/lib/python3.9/site-packages (from -r requirements.txt (line 3)) (2.24.0)
Collecting psutil==5.7.2
Using cached psutil-5.7.2.tar.gz (460 kB)
Requirement already satisfied: staticmap==0.5.5 in ./venv/lib/python3.9/site-packages (from -r requirements.txt (line 5)) (0.5.5)
Requirement already satisfied: pytz in ./venv/lib/python3.9/site-packages (from tzlocal==2.1->-r requirements.txt (line 2)) (2021.1)
Requirement already satisfied: certifi>=2017.4.17 in ./venv/lib/python3.9/site-packages (from requests==2.24.0->-r requirements.txt (line 3)) (2021.5.30)
Requirement already satisfied: chardet<4,>=3.0.2 in ./venv/lib/python3.9/site-packages (from requests==2.24.0->-r requirements.txt (line 3)) (3.0.4)
Requirement already satisfied: idna<3,>=2.5 in ./venv/lib/python3.9/site-packages (from requests==2.24.0->-r requirements.txt (line 3)) (2.10)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in ./venv/lib/python3.9/site-packages (from requests==2.24.0->-r requirements.txt (line 3)) (1.25.11)
Requirement already satisfied: Pillow in ./venv/lib/python3.9/site-packages (from staticmap==0.5.5->-r requirements.txt (line 5)) (8.3.1)
Requirement already satisfied: six>=1.5 in ./venv/lib/python3.9/site-packages (from python-dateutil>=2.8.1->-r requirements.txt (line 1)) (1.16.0)
Using legacy 'setup.py install' for psutil, since package 'wheel' is not installed.
Installing collected packages: psutil
Running setup.py install for psutil ... done
Successfully installed psutil-5.7.2
WARNING: You are using pip version 21.1.3; however, version 21.2.4 is available.
You should consider upgrading via the '/Users/rmyadsk/Downloads/tesla_dashcam-0.1.17b4/venv/bin/python3.9 -m pip install --upgrade pip' command.
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % pip3 install setuptools wheel
Requirement already satisfied: setuptools in ./venv/lib/python3.9/site-packages (56.0.0)
Collecting wheel
Downloading wheel-0.37.0-py2.py3-none-any.whl (35 kB)
Installing collected packages: wheel
Successfully installed wheel-0.37.0
WARNING: You are using pip version 21.1.3; however, version 21.2.4 is available.
You should consider upgrading via the '/Users/rmyadsk/Downloads/tesla_dashcam-0.1.17b4/venv/bin/python3.9 -m pip install --upgrade pip' command.
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % pip3 install pyinstaller
Collecting pyinstaller
Downloading pyinstaller-4.5.1-py3-none-macosx_10_13_universal2.whl (1.6 MB)
|████████████████████████████████| 1.6 MB 4.4 MB/s
Collecting pyinstaller-hooks-contrib>=2020.6
Downloading pyinstaller_hooks_contrib-2021.2-py2.py3-none-any.whl (190 kB)
|████████████████████████████████| 190 kB 18.8 MB/s
Requirement already satisfied: setuptools in ./venv/lib/python3.9/site-packages (from pyinstaller) (56.0.0)
Collecting altgraph
Downloading altgraph-0.17-py2.py3-none-any.whl (21 kB)
Collecting macholib>=1.8
Downloading macholib-1.14-py2.py3-none-any.whl (37 kB)
Installing collected packages: altgraph, pyinstaller-hooks-contrib, macholib, pyinstaller
Successfully installed altgraph-0.17 macholib-1.14 pyinstaller-4.5.1 pyinstaller-hooks-contrib-2021.2
WARNING: You are using pip version 21.1.3; however, version 21.2.4 is available.
You should consider upgrading via the '/Users/rmyadsk/Downloads/tesla_dashcam-0.1.17b4/venv/bin/python3.9 -m pip install --upgrade pip' command.
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % ls
AUTHORS			LICENSE			RunPreferences.bash	tesla_dashcam
Bundles			Preference_Files	requirements.txt	venv
Dockerfile		README.rst		setup.py
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % pwd
/Users/rmyadsk/Downloads/tesla_dashcam-0.1.17b4
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-0.1.17b4 % cd tesla_dashcam
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam % ls
init.py		version.py		tesla_dashcam.ico	tesla_dashcam.png	tesla_dashcam.py

Did you download the zip file from GitHub from Dev branch? If you did it from the release 0.1.17b4 branch then it won't be included there.
It is here: https://github.com/ehendrix23/tesla_dashcam/blob/dev/create_executable.bash

A truly RTFM manual for me...I should have concentrated on the part that basically said "click the green button" to download the appropriate release.
Anyway, there is a tesla_dashcam_dev/Bundles/MacOS/tesla_dashcam exe where there was not one before, but it is not very useful:

rmyadsk@Ryans-Mac-Mini /Applications % ./tesla_dashcam -help
zsh: killed     ./tesla_dashcam -help

Here is how the build went:

(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev % ./create_executable.bash
299 INFO: PyInstaller: 4.5.1
299 INFO: Python: 3.9.6
308 INFO: Platform: macOS-12.0-arm64-arm-64bit
309 INFO: wrote /Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam.spec
311 INFO: UPX is not available.
311 INFO: Removing temporary files and cleaning cache in /Users/rmyadsk/Library/Application Support/pyinstaller
312 INFO: Extending PYTHONPATH with paths
['/Users/rmyadsk/Downloads/tesla_dashcam-dev',
'/Users/rmyadsk/Downloads/tesla_dashcam-dev']
406 INFO: checking Analysis
406 INFO: Building Analysis because Analysis-00.toc is non existent
406 INFO: Initializing module dependency graph...
407 INFO: Caching module graph hooks...
410 INFO: Analyzing base_library.zip ...
1477 INFO: Processing pre-find module path hook distutils from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'.
1477 INFO: distutils: retargeting to non-venv dir '/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9'
2762 INFO: Caching module dependency graph...
2822 INFO: running Analysis Analysis-00.toc
2826 INFO: Analyzing /Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam/tesla_dashcam.py
2954 INFO: Processing pre-safe import module hook urllib3.packages.six.moves from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_safe_import_module/hook-urllib3.packages.six.moves.py'.
3526 INFO: Processing pre-safe import module hook six.moves from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_safe_import_module/hook-six.moves.py'.
3997 INFO: Processing module hooks...
3998 INFO: Loading module hook 'hook-certifi.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
3999 INFO: Loading module hook 'hook-pkg_resources.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4173 INFO: Processing pre-safe import module hook win32com from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/pre_safe_import_module/hook-win32com.py'.
4187 WARNING: Hidden import "pkg_resources.py2_warn" not found!
4187 WARNING: Hidden import "pkg_resources.markers" not found!
4188 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4188 INFO: Loading module hook 'hook-pytz.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4220 INFO: Loading module hook 'hook-lib2to3.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4237 INFO: Loading module hook 'hook-_tkinter.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4458 INFO: checking Tree
4458 INFO: Building Tree because Tree-00.toc is non existent
4458 INFO: Building Tree Tree-00.toc
4466 INFO: checking Tree
4466 INFO: Building Tree because Tree-01.toc is non existent
4466 INFO: Building Tree Tree-01.toc
4498 INFO: checking Tree
4498 INFO: Building Tree because Tree-02.toc is non existent
4498 INFO: Building Tree Tree-02.toc
4499 INFO: Loading module hook 'hook-encodings.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4530 INFO: Loading module hook 'hook-PIL.ImageFilter.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4531 INFO: Loading module hook 'hook-distutils.util.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4532 INFO: Loading module hook 'hook-PIL.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4535 INFO: Loading module hook 'hook-PIL.Image.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4665 INFO: Loading module hook 'hook-pickle.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4666 INFO: Loading module hook 'hook-heapq.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4667 INFO: Loading module hook 'hook-difflib.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4667 INFO: Loading module hook 'hook-multiprocessing.util.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4668 INFO: Loading module hook 'hook-sysconfig.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4680 INFO: Loading module hook 'hook-xml.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4700 INFO: Loading module hook 'hook-distutils.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4700 INFO: Loading module hook 'hook-PIL.SpiderImagePlugin.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4711 INFO: Looking for ctypes DLLs
4719 WARNING: library user32 required via ctypes not found
4723 INFO: Analyzing run-time hooks ...
4725 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgutil.py'
4726 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py'
4727 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_inspect.py'
4728 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth__tkinter.py'
4728 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgres.py'
4730 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/rthooks/pyi_rth_certifi.py'
4734 INFO: Looking for dynamic libraries
4822 INFO: Looking for eggs
4822 INFO: Using Python library /Library/Frameworks/Python.framework/Versions/3.9/Python
4824 INFO: Warnings written to build/MacOS/tesla_dashcam/warn-tesla_dashcam.txt
4841 INFO: Graph cross-reference written to build/MacOS/tesla_dashcam/xref-tesla_dashcam.html
4858 INFO: Appending 'binaries' from .spec
4858 INFO: Appending 'datas' from .spec
4861 INFO: checking PYZ
4861 INFO: Building PYZ because PYZ-00.toc is non existent
4861 INFO: Building PYZ (ZlibArchive) build/MacOS/tesla_dashcam/PYZ-00.pyz
5200 INFO: Building PYZ (ZlibArchive) build/MacOS/tesla_dashcam/PYZ-00.pyz completed successfully.
5205 INFO: EXE target arch: arm64
5205 INFO: Code signing identity: None
5206 INFO: checking PKG
5206 INFO: Building PKG because PKG-00.toc is non existent
5206 INFO: Building PKG (CArchive) PKG-00.pkg
13509 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
13521 INFO: Bootloader /Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/bootloader/Darwin-64bit/run
13521 INFO: checking EXE
13521 INFO: Building EXE because EXE-00.toc is non existent
13521 INFO: Building EXE from EXE-00.toc
13521 INFO: Copying bootloader exe to bundles/MacOS/tesla_dashcam/tesla_dashcam
13521 INFO: Converting EXE to target arch (arm64)
13529 INFO: Removing signature(s) from EXE
13550 INFO: Fixing EXE for code signing bundles/MacOS/tesla_dashcam/tesla_dashcam
Traceback (most recent call last):
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/bin/pyinstaller", line 8, in
sys.exit(run())
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/main.py", line 126, in run
run_build(pyi_config, spec_file, **vars(args))
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/main.py", line 65, in run_build
PyInstaller.building.build_main.main(pyi_config, spec_file, **kwargs)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/build_main.py", line 815, in main
build(specfile, kw.get('distpath'), kw.get('workpath'), kw.get('clean_build'))
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/build_main.py", line 762, in build
exec(code, spec_namespace)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam.spec", line 23, in
exe = EXE(pyz,
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/api.py", line 524, in init
self.postinit()
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/datastruct.py", line 159, in postinit
self.assemble()
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/api.py", line 761, in assemble
osxutils.fix_exe_for_code_signing(self.name)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/utils/osx.py", line 211, in fix_exe_for_code_signing
assert linkedit_seg.fileoff + linkedit_seg.filesize ==
AssertionError: Sanity check failed!
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev [%]

K, made small changes to this.

Redownload the ZIP file from DEV branch.
Ensure your ffmpeg is located in bundles/MacOS/ffmpeg (the one for M1)
run bundles/MacOS/create_executable.bash

create_executable didn't like it in bundles/MacOS/, so I moved it:

(venv) rmyadsk@Ryans-Mac-Mini MacOS % ./create_executable.bash
Was unable to find tesla_dashcam/tesla_dashcam.py, run this from the folder where tesla_dashcam/tesla_dashcam.py is located within.
(venv) rmyadsk@Ryans-Mac-Mini MacOS % mv create_executable.bash ../../
(venv) rmyadsk@Ryans-Mac-Mini MacOS % ls
ffmpeg
(venv) rmyadsk@Ryans-Mac-Mini MacOS % cd ../..
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev % ls
AUTHORS			LICENSE			README.rst		bundles			requirements.txt	tesla_dashcam
Dockerfile		Preference_Files	RunPreferences.bash	create_executable.bash	setup.py		venv
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev % ./create_executable.bash
400 INFO: PyInstaller: 4.5.1
401 INFO: Python: 3.9.6
409 INFO: Platform: macOS-12.0-arm64-arm-64bit
409 INFO: wrote /Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam.spec
412 INFO: UPX is not available.
412 INFO: Removing temporary files and cleaning cache in /Users/rmyadsk/Library/Application Support/pyinstaller
421 INFO: Extending PYTHONPATH with paths
['/Users/rmyadsk/Downloads/tesla_dashcam-dev',
'/Users/rmyadsk/Downloads/tesla_dashcam-dev']
512 INFO: checking Analysis
512 INFO: Building Analysis because Analysis-00.toc is non existent
512 INFO: Initializing module dependency graph...
513 INFO: Caching module graph hooks...
516 INFO: Analyzing base_library.zip ...
1563 INFO: Processing pre-find module path hook distutils from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'.
1564 INFO: distutils: retargeting to non-venv dir '/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9'
2899 INFO: Caching module dependency graph...
2960 INFO: running Analysis Analysis-00.toc
2965 INFO: Analyzing /Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam/tesla_dashcam.py
3091 INFO: Processing pre-safe import module hook urllib3.packages.six.moves from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_safe_import_module/hook-urllib3.packages.six.moves.py'.
3680 INFO: Processing pre-safe import module hook six.moves from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_safe_import_module/hook-six.moves.py'.
4152 INFO: Processing module hooks...
4152 INFO: Loading module hook 'hook-certifi.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
4154 INFO: Loading module hook 'hook-pkg_resources.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4330 INFO: Processing pre-safe import module hook win32com from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/pre_safe_import_module/hook-win32com.py'.
4331 WARNING: Hidden import "pkg_resources.py2_warn" not found!
4331 WARNING: Hidden import "pkg_resources.markers" not found!
4332 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4332 INFO: Loading module hook 'hook-pytz.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4364 INFO: Loading module hook 'hook-lib2to3.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4379 INFO: Loading module hook 'hook-_tkinter.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4593 INFO: checking Tree
4593 INFO: Building Tree because Tree-00.toc is non existent
4593 INFO: Building Tree Tree-00.toc
4601 INFO: checking Tree
4601 INFO: Building Tree because Tree-01.toc is non existent
4601 INFO: Building Tree Tree-01.toc
4633 INFO: checking Tree
4633 INFO: Building Tree because Tree-02.toc is non existent
4633 INFO: Building Tree Tree-02.toc
4635 INFO: Loading module hook 'hook-encodings.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4665 INFO: Loading module hook 'hook-PIL.ImageFilter.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4667 INFO: Loading module hook 'hook-distutils.util.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4667 INFO: Loading module hook 'hook-PIL.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4671 INFO: Loading module hook 'hook-PIL.Image.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4809 INFO: Loading module hook 'hook-pickle.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4811 INFO: Loading module hook 'hook-heapq.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4812 INFO: Loading module hook 'hook-difflib.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4812 INFO: Loading module hook 'hook-multiprocessing.util.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4813 INFO: Loading module hook 'hook-sysconfig.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4817 INFO: Loading module hook 'hook-xml.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4837 INFO: Loading module hook 'hook-distutils.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4838 INFO: Loading module hook 'hook-PIL.SpiderImagePlugin.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4849 INFO: Looking for ctypes DLLs
4856 WARNING: library user32 required via ctypes not found
4861 INFO: Analyzing run-time hooks ...
4863 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgutil.py'
4864 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py'
4865 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_inspect.py'
4865 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth__tkinter.py'
4866 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgres.py'
4868 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/rthooks/pyi_rth_certifi.py'
4871 INFO: Looking for dynamic libraries
4979 INFO: Looking for eggs
4979 INFO: Using Python library /Library/Frameworks/Python.framework/Versions/3.9/Python
4981 INFO: Warnings written to build/MacOS/tesla_dashcam/warn-tesla_dashcam.txt
4999 INFO: Graph cross-reference written to build/MacOS/tesla_dashcam/xref-tesla_dashcam.html
5015 INFO: Appending 'binaries' from .spec
5015 INFO: Appending 'datas' from .spec
5019 INFO: checking PYZ
5019 INFO: Building PYZ because PYZ-00.toc is non existent
5019 INFO: Building PYZ (ZlibArchive) build/MacOS/tesla_dashcam/PYZ-00.pyz
5361 INFO: Building PYZ (ZlibArchive) build/MacOS/tesla_dashcam/PYZ-00.pyz completed successfully.
5366 INFO: EXE target arch: arm64
5366 INFO: Code signing identity: None
5367 INFO: checking PKG
5367 INFO: Building PKG because PKG-00.toc is non existent
5367 INFO: Building PKG (CArchive) PKG-00.pkg
12203 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
12215 INFO: Bootloader /Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/bootloader/Darwin-64bit/run
12215 INFO: checking EXE
12215 INFO: Building EXE because EXE-00.toc is non existent
12215 INFO: Building EXE from EXE-00.toc
12215 INFO: Copying bootloader exe to bundles/MacOS/tesla_dashcam/tesla_dashcam
12215 INFO: Converting EXE to target arch (arm64)
12222 INFO: Removing signature(s) from EXE
12245 INFO: Fixing EXE for code signing bundles/MacOS/tesla_dashcam/tesla_dashcam
Traceback (most recent call last):
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/bin/pyinstaller", line 8, in
sys.exit(run())
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/main.py", line 126, in run
run_build(pyi_config, spec_file, **vars(args))
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/main.py", line 65, in run_build
PyInstaller.building.build_main.main(pyi_config, spec_file, **kwargs)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/build_main.py", line 815, in main
build(specfile, kw.get('distpath'), kw.get('workpath'), kw.get('clean_build'))
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/build_main.py", line 762, in build
exec(code, spec_namespace)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam.spec", line 23, in
exe = EXE(pyz,
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/api.py", line 524, in init
self.postinit()
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/datastruct.py", line 159, in postinit
self.assemble()
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/api.py", line 761, in assemble
osxutils.fix_exe_for_code_signing(self.name)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/utils/osx.py", line 211, in fix_exe_for_code_signing
assert linkedit_seg.fileoff + linkedit_seg.filesize ==
AssertionError: Sanity check failed!
Failed to create executable.
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev %

Put create_executable.bash back where it was.
In your case you would then run it from folder tesla_dashcam-dev as:  ./bundles/MacOS/create_executable.bash
Not sure if that is causing the issue you're seeing. Apple silicon is still in early stages for a lot of code, including Python etc..

Yes, it seems to be getting tripped up at the same spot, something about code signing, or a fix for it, or something. I do note
Code signing identity: None
...if that might matter?

(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev % ./bundles/MacOS/create_executable.bash
35 INFO: PyInstaller: 4.5.1
35 INFO: Python: 3.9.6
43 INFO: Platform: macOS-12.0-arm64-arm-64bit
44 INFO: wrote /Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam.spec
45 INFO: UPX is not available.
46 INFO: Removing temporary files and cleaning cache in /Users/rmyadsk/Library/Application Support/pyinstaller
52 INFO: Extending PYTHONPATH with paths
['/Users/rmyadsk/Downloads/tesla_dashcam-dev',
'/Users/rmyadsk/Downloads/tesla_dashcam-dev']
125 INFO: checking Analysis
125 INFO: Building Analysis because Analysis-00.toc is non existent
125 INFO: Initializing module dependency graph...
126 INFO: Caching module graph hooks...
130 INFO: Analyzing base_library.zip ...
1178 INFO: Processing pre-find module path hook distutils from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'.
1178 INFO: distutils: retargeting to non-venv dir '/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9'
2501 INFO: Caching module dependency graph...
2561 INFO: running Analysis Analysis-00.toc
2568 INFO: Analyzing /Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam/tesla_dashcam.py
2694 INFO: Processing pre-safe import module hook urllib3.packages.six.moves from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_safe_import_module/hook-urllib3.packages.six.moves.py'.
3298 INFO: Processing pre-safe import module hook six.moves from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_safe_import_module/hook-six.moves.py'.
3775 INFO: Processing module hooks...
3775 INFO: Loading module hook 'hook-certifi.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
3777 INFO: Loading module hook 'hook-pkg_resources.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
3953 INFO: Processing pre-safe import module hook win32com from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/pre_safe_import_module/hook-win32com.py'.
3954 WARNING: Hidden import "pkg_resources.py2_warn" not found!
3954 WARNING: Hidden import "pkg_resources.markers" not found!
3955 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
3955 INFO: Loading module hook 'hook-pytz.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
3990 INFO: Loading module hook 'hook-lib2to3.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4003 INFO: Loading module hook 'hook-_tkinter.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4063 INFO: checking Tree
4063 INFO: Building Tree because Tree-00.toc is non existent
4063 INFO: Building Tree Tree-00.toc
4068 INFO: checking Tree
4068 INFO: Building Tree because Tree-01.toc is non existent
4068 INFO: Building Tree Tree-01.toc
4099 INFO: checking Tree
4099 INFO: Building Tree because Tree-02.toc is non existent
4099 INFO: Building Tree Tree-02.toc
4101 INFO: Loading module hook 'hook-encodings.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4130 INFO: Loading module hook 'hook-PIL.ImageFilter.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4132 INFO: Loading module hook 'hook-distutils.util.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4132 INFO: Loading module hook 'hook-PIL.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4136 INFO: Loading module hook 'hook-PIL.Image.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4277 INFO: Loading module hook 'hook-pickle.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4278 INFO: Loading module hook 'hook-heapq.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4279 INFO: Loading module hook 'hook-difflib.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4280 INFO: Loading module hook 'hook-multiprocessing.util.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4281 INFO: Loading module hook 'hook-sysconfig.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4284 INFO: Loading module hook 'hook-xml.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4305 INFO: Loading module hook 'hook-distutils.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4305 INFO: Loading module hook 'hook-PIL.SpiderImagePlugin.py' from '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
4316 INFO: Looking for ctypes DLLs
4325 WARNING: library user32 required via ctypes not found
4330 INFO: Analyzing run-time hooks ...
4332 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgutil.py'
4333 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py'
4334 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_inspect.py'
4335 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth__tkinter.py'
4335 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgres.py'
4337 INFO: Including run-time hook '/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/rthooks/pyi_rth_certifi.py'
4341 INFO: Looking for dynamic libraries
4455 INFO: Looking for eggs
4455 INFO: Using Python library /Library/Frameworks/Python.framework/Versions/3.9/Python
4458 INFO: Warnings written to build/MacOS/tesla_dashcam/warn-tesla_dashcam.txt
4475 INFO: Graph cross-reference written to build/MacOS/tesla_dashcam/xref-tesla_dashcam.html
4491 INFO: Appending 'binaries' from .spec
4492 INFO: Appending 'datas' from .spec
4492 INFO: checking PYZ
4492 INFO: Building PYZ because PYZ-00.toc is non existent
4493 INFO: Building PYZ (ZlibArchive) build/MacOS/tesla_dashcam/PYZ-00.pyz
4832 INFO: Building PYZ (ZlibArchive) build/MacOS/tesla_dashcam/PYZ-00.pyz completed successfully.
4837 INFO: EXE target arch: arm64
4837 INFO: Code signing identity: None
4838 INFO: checking PKG
4838 INFO: Building PKG because PKG-00.toc is non existent
4838 INFO: Building PKG (CArchive) PKG-00.pkg
11651 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
11662 INFO: Bootloader /Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/bootloader/Darwin-64bit/run
11662 INFO: checking EXE
11662 INFO: Building EXE because EXE-00.toc is non existent
11662 INFO: Building EXE from EXE-00.toc
11662 INFO: Copying bootloader exe to bundles/MacOS/tesla_dashcam/tesla_dashcam
11663 INFO: Converting EXE to target arch (arm64)
11673 INFO: Removing signature(s) from EXE
11714 INFO: Fixing EXE for code signing bundles/MacOS/tesla_dashcam/tesla_dashcam
Traceback (most recent call last):
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/bin/pyinstaller", line 8, in
sys.exit(run())
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/main.py", line 126, in run
run_build(pyi_config, spec_file, **vars(args))
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/main.py", line 65, in run_build
PyInstaller.building.build_main.main(pyi_config, spec_file, **kwargs)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/build_main.py", line 815, in main
build(specfile, kw.get('distpath'), kw.get('workpath'), kw.get('clean_build'))
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/build_main.py", line 762, in build
exec(code, spec_namespace)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/tesla_dashcam.spec", line 23, in
exe = EXE(pyz,
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/api.py", line 524, in init
self.postinit()
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/datastruct.py", line 159, in postinit
self.assemble()
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/building/api.py", line 761, in assemble
osxutils.fix_exe_for_code_signing(self.name)
File "/Users/rmyadsk/Downloads/tesla_dashcam-dev/venv/lib/python3.9/site-packages/PyInstaller/utils/osx.py", line 211, in fix_exe_for_code_signing
assert linkedit_seg.fileoff + linkedit_seg.filesize ==
AssertionError: Sanity check failed!
Failed to create executable.
(venv) rmyadsk@Ryans-Mac-Mini tesla_dashcam-dev %

Yeah, not sure what is going on. I'll need to google a bit more on this to see if I can found out why. Sadly enough I am unable to try it out here right now. :-(

Closing this issue. Original item this issue was opened for is now closed.


Can’t flash on 9FUSY31MF0

Hi all, just bought a YI 1080 home on Amazon ( with Firmware <IP_ADDRESS>A_201912270941 ).
With the 16GB SD formatted FAT32 I copied the file + 2 folders, switched off, inserted SD and switched on.
Yellow light flashes for few seconds then it becomes blue and flashing. Waited 30+ minutes and nothing happen.
In this condition the camera is not connected in my network. As soon as I remove the SD the Camera connect to the network with its original firmware.
Any clue?
Thanks a lot

Remove all files from sd and try again.
If doesn't work, try another card.

Thanks for your reply, I have tried with 2 different 16GB SdCards: Transcend and SanDisk and one try also with a 32GB SanDisk.
After having them formatted to FAT32 I copied these files:
Home_y20gam.stage
Factory/config.sh
Factory/factory_test.sh
Newhome/base/tools/extpkg.sh
What files do you suggest to remove?
I get same behavior with both SD Card ( both brand new ) so I thought it could be linked to a more recent model ( on the box it is reported Date: 2020.03 )
I have tried even earlier versions ( I read somewhere that flashing an earlier version and then upgrade via web interface has helped in some cases.. ) but there is no way unfortunately

The firmware version 8.2.0* means that the cam is compatible with the hack.
Are you sure the fw is not hacked?
How did you check it?

To be honest I’m no 100% sure:
I’m just sticking on these 2 behaviors:

while flashing the firmware after some yellow led flashing it switch tu blue led flashing and it won’t change its state ( no steady light ), so I am assuming the process did not complete
Right now I am trying to reach the web interface to its address:8080 but it’s not reachable ( while the device is listed in my router and the camera is available in its native app )

Any other thing I could do to check?

Web page is enough.

Same problem on 9FUSY310OZ.
Then tried to install 0.1.3 from SD-card. Worked very well (only a few minutes).
Then did a update via web page to 0.1.6, which succeeded.

The only difference between manual upgrade and online upgrade is that the first one doesn't backup/restore the config.
Both methods use the files on sd.
Probably an error copying the files.

Tried to do the same with 0.1.3 but this approach did not work on my end. Endless blue led flashing condition.
Still trying to find out a solution.

Try this procedure:
https://github.com/roleoroleo/yi-hack-Allwinner/wiki/Dump-your-backup-firmware-(SD-card)
to check if the startup hack works.

I believe it doesn’t work.
In the sd root I only find Factory folder I extracted with included config.sh and factory_test.sh files
Tried with 2 different SD cards.
I also thought my cam was faulty in the SD reader but if I include SD cards in normal mode the cam records motion triggered videos properly and I can see them on my pc.
I’m used to these kind of actions, I have a quite well integrate Home Assistant system .. so really I cannot understand why I can’t succeed with this...

Could you take a picture of your sd file system?
A Windows explorer is enough.

Here it is
https://ibb.co/5cjLTqK

Is thie the hack or the backup procedure?

Yes this is what I extracted from backup.tar.gz

Backup procedure

I don't know.
The only way to understand the problem is connect a serial interface.
But it's complicated.

I have a SH-U09 dongle, would it work for the scope? Any guide to follow to try to give some info?

Yes it works.
See the wiki.

@andriy7811 any joy?
I seem to be having a similar issue. As soon as I add the Factory folder the camera get unavailable even though it seems to boot fine (steady blue LED)
D:\>dir
 Volume in drive D has no label.
 Volume Serial Number is 0000-00C0

 Directory of D:\

06/07/2020  16:51    <DIR>          record
06/07/2020  16:46    <DIR>          log
07/05/2020  16:03    <DIR>          Factory
               0 File(s)              0 bytes
               3 Dir(s)  15.912.910.848 bytes free

D:\>cd Factory

D:\Factory>dir
 Volume in drive D has no label.
 Volume Serial Number is 0000-00C0

 Directory of D:\Factory

06/07/2020  17:52    <DIR>          .
06/07/2020  17:52    <DIR>          ..
07/05/2020  16:03               638 config.sh
03/05/2020  16:31                 0 factory_test.sh
               2 File(s)            638 bytes
               2 Dir(s)  15.912.910.848 bytes free

I had no luck with serial interface.
I gave up. Looking for a different camera to integrate in Home assistant...

Problems soldering the interface?


Remove "bad" staging environment?

Here's more:
When I try to browse the production url, it actually takes me to the pull request staging environment (which doesn't exist as you can see from the screenshot).

Staging Url: https://wonderful-coast-0c62a0e03-4.westeurope.azurestaticapps.net/
Actual Prod Url: https://wonderful-coast-0c62a0e03.azurestaticapps.net/
Originally posted by @christiandornetto in https://github.com/Azure/static-web-apps/issues/131#issuecomment-674889488

As per the title. I have a static web app that is deployed on azure. Today I had a pull request submitted which caused the build pipeline failed because of a simple error which I then corrected.
I then merged the pull request but this did not delete the staging environment previously created and now when I try to navigate to the production I get redirected to the "dead" staging environment which results in a 404.
Is there a way to restore previous deployments or delete environment using a console or similar?

Going to close this and we can use the earlier issue to track since they are caused by the same. Please see my most recent update in #131


homepage embed of app.tabby.sh fails because of deprecated X-Frame-Options header

Invalid X-Frame-Options header was found when loading “https://app.tabby.sh/demo”: “ALLOW-FROM https://tabby.sh/” is not a valid directive.

The loading of “https://app.tabby.sh/terminal” in a frame is denied by “X-Frame-Options“ directive set to “SAMEORIGIN“

Looking at MDN docs:

ALLOW-FROM=url Deprecated
This is an obsolete directive that no longer works in modern browsers. (Using it will give the same behavior as omitting the header.) Don't use it. The Content-Security-Policy HTTP header has a frame-ancestors directive which you can use instead.

Fixed, thanks!


Serialize/Deserialize protected _files_to_sync_used

A custom serialization/deserialization method has been introduced to save original value for CommonPackageConfig attribute _file_to_sync_used.
Fixes #1525

How about something like this instead? To me this seems easier to follow and understand.
It passes the unit test you've prepared, but I haven't tested it otherwise.

How about something like this instead? To me this seems easier to follow and understand.
It passes the unit test you've prepared, but I haven't tested it otherwise.

Nice, I have also ran all the other tests and they passed.
I think I can close this one.
Thanks!

Nice, I have also ran all the other tests and they passed. I think I can close this one. Thanks!

Well, thanks to you! It was your idea, after all :smiley:
I wonder, why you didn't choose this approach after all :thinking:

I was trying to save the inner state instead of recalculate it. But you are right the code is much simpler in this way.

recheck


[2103] bursaries new tiered bursary form

Context
For a trainee on the Early years (postgrad) route, we show them a different bursary choice form, listing the possible tiers available, plus an option for "Not applying for bursary"
Changes proposed in this pull request
Split the bursary section into two forms, one for tiered bursaries, applicable on the EY postgrad route, and the standard bursary form for all other routes where bursaries are applicable.
Guidance to review

For a draft trainee on the early years (postgrad) route, visit the funding section, and complete the initiative section, and press continue.
A tiered bursary form should be now seen, allowing the user to choose between tiers one, two, three, or do not apply
Select an option and expect to see the chosen tier in the confirmation page.

 Bursaries - new tiered bursary form

Works as expected for me - nice work 👍


Cannot log in on Mac OS X

First, make sure your issue is strictly related to the Electronic WeChat project. If it's a question or feature request, you can remove the template below.
Description
OS version 10.11.4 Beta(15E56a); after QR code scanning my WeChat app on iPhone will report success, but Electronic WeChat will stay at the confirm log in screen.
Specifications

Version of Electron (run $ electron --version): v0.0.0
I can't get version from that command. I used homebrew to install Electron following guide on this site:
http://macappstore.org/electron/
Version of Node.js (run $ node --version): v5.7.0
OS: <OS>
Architecture <ARCH>
Stack trace from the error message (if any)

<Stack trace here>

+1
#41

Fixed in #41.

Still have the same problem. I cloned the rep and compiled it on my machine as directed, but the problem is the same with the released version.

@HybridRbt 能否打开devTools看一下登录时的Network请求

@geeeeeeeeek 我不会用 devTools，有具体步骤吗？


Make the DWARF version emitted by the Swift compiler configurable.

Previously it was hardcoded to version 4 on all platforms.
This patch introduces new driver and frontend flags -dwarf-version=.
This PR includes https://github.com/apple/swift/pull/69255, due to a tiny dependency.

@swift-ci test with https://github.com/apple/swift-driver/pull/1467

test with https://github.com/apple/swift-driver/pull/1467
@swift-ci test

test with https://github.com/apple/swift-driver/pull/1467
@swift-ci test

test with https://github.com/apple/swift-driver/pull/1467
@swift-ci test

(There's an LLDB dependency that I didn't forsee so I'll put his on ice until after rebranch)

test with https://github.com/apple/swift-driver/pull/1467
test with https://github.com/apple/llvm-project/pull/7668
@swift-ci smoke test

test with https://github.com/apple/swift-driver/pull/1467
test with https://github.com/apple/llvm-project/pull/7668
@swift-ci test windows


feat: adding mp_gsubfile.sas - a SAS macro that uses Lua to perform a…

… full text find and replace of an entire file.  Not restricted by number of characters (only memory). Includes a test.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


git.blame.editorDecoration.enabled shows incorrect value for diff changes displayed in source control

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

Version: 1.96.0-insider (user setup)
Commit: 8d1d1373cd9b8408222b51958e9688827a9e27ce
Date: 2024-11-20T09:23:45.992Z
Electron: 32.2.5
ElectronBuildId: 10579404
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100
Steps to Reproduce:

Enable Git › Blame › Editor Decoration option - git.blame.editorDecoration.enabled
Open Source Control panel
Click on any commit

Newly added changes are displayed as Not Committed Yet:
Screenshot

In the left panel some of old lines also shows Not Committed Yet, but in right panel it's displayed correctly:
Screenshot

https://github.com/user-attachments/assets/7b531954-aeca-4b4c-b78e-a6ffed7c8c7f
By the way, thank you for adding this feature.

@AdamWr, thank you very much for trying out this new experimental feature. This is coming "hot of the presses" so we are working to addressing the bugs. Please continue to use the daily VS Code Insiders builds as we are pushing fixes every day.

@AdamWr, this issue should be fixed in the latest VS Code Insiders release.
Please give it a try and reopen the issue if the git blame decorators are not working as expected in the diff editor.

Please ignore my issue from previous comment, it seems to be duplicate of https://github.com/microsoft/vscode/issues/234800


bug<EMAIL_ADDRESS>ng build --prod include all compiler in final bundle

Versions
<!--
Output from: `ng --version`.
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan?  Normally this includes a stack trace and some more information. -->

angular/cli 1.7.3

angular/cli 6.0.0-beta5

Desired behavior

No compiler in final bundle when build with --prod
Mention any other details that might be useful (optional)

Hi, I'm seeing the same issue.

Angular CLI: 6.0.0-beta.5
Node: 9.5.0
OS: darwin x64
Angular: 6.0.0-beta.7
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
angular/cli: 6.0.0-beta.5
angular-devkit/build-optimizer: 0.4.5
angular-devkit/core: 0.4.5
angular-devkit/schematics: 0.4.5
ngtools/json-schema: 1.2.0
ngtools/webpack: 6.0.0-beta.5
schematics/angular: 0.4.5
schematics/package-update: 0.4.5
typescript: 2.6.2
webpack: 4.0.1

ng build --prod

chunk {main} main.js, main.js.map (main) 778 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 224 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 5.09 kB [entry] [rendered]
chunk {scripts} scripts.js, scripts.js.map (scripts) 293 kB  [rendered]
chunk {styles} styles.js, styles.js.map (styles) 424 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 5.27 MB [initial] [rendered]

But Running ng build --target=production seems to be good :

chunk {scripts} scripts.7919ccceb3b0018336c0.js (scripts) 288 kB  [rendered]
chunk {0} runtime.5f9d33fb31487f0fdbf1.js (runtime) 1.05 kB [entry] [rendered]
chunk {1} styles.3b9328888a1ada1ada41.css (styles) 313 kB [initial] [rendered]
chunk {2} polyfills.f0578259d90544bd90ad.js (polyfills) 59.1 kB [initial] [rendered]
chunk {3} main.37c0d0a04c33ab0e7152.js (main) 1.9 MB [initial] [rendered]

Yes.  In our refactoring of flags we removed the old parsing code and thus --prod was removed (as it was a weird alias case), and we forgot to put it back as a special flag. This will be addressed in the next beta.
For now you can use the long form --target=production.

It does not work for me
 #ng build --target=production
Project 'production' could not be found in workspace.
Error: Project 'production' could not be found in workspace.

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


feat(performance): reduce the number of files scanned after merge conflict

Context
The goal of this Merge Request is to improve the speed of the ggshield pre-commit scan when commiting after a merge conflict.
What has been done
I created a script gen_merge_commit.py (temporarily added at the repository root) that creates a repo with two branches (master and feature_branch) a merge commit (with or without commit depending on the options) giving the following commit graph:
*   17d3a27 (HEAD -> feature_branch) Merge branch 'master' into feature_branch
|\
| * db20e84 (master) Commit master n°2
| * 53a4cd0 Commit master n°1
| * a78f68d Commit master n°0
* | 9f5717c Commit feature branch
|/
* e1db622 Initial commit

I then experimented and with it:

Without conflict: our pre-commit does not seem to be called on merge
With conflict: I implemented a proof of concept way to limit the number of files scan: when ggshield pre-commit is called
- if MERGE_HEAD does not exists, we assume it is a regular commit and we should scan everything (current behavior)
- if MERGE_HEAD exists: we list the files about to be committed (git diff --staged --name-only), then compare the current shas of those files  (using the command git ls-files --staged <list_files_diff>) with the shas of HEAD and MERGE_HEAD (obtained via git ls-tree  <list_files_diff>), and if it differs from both, then the file has been modified and should be re-scanned...

I'm opening this PR as a draft as it is clearly not ready (no proper automated testing) but the general idea should be reviewed...

@agateau-gg  I started doing something because it looked convenient in my tests and possibly useful but maybe you won't like it: I added an option to ggshield install to install the hook with option.
For example, ggshield install -o --json will install  the following hook: ggshield secret scan pre-commit --json "$@".
But as it seems to fail on windows, I would like to check with you before debugging... :sweat:

@agateau-gg I started doing something because it looked convenient in my tests and possibly useful but maybe you won't like it: I added an option to ggshield install to install the hook with option.
For example, ggshield install -o --json will install the following hook: ggshield secret scan pre-commit --json "$@".
But as it seems to fail on windows, I would like to check with you before debugging... 😓

The idea sounds good, but it should be in a separate commit or maybe even in a separate PR.


Some systemd timers don't start until systemd restart

Describe the bug
I have set autoUpgrade.dates = "04:00", and also set WakeSystem to be true, but my laptop wakes up from suspend at 04:00, does nothing, and goes back to sleep (journal). I have overwritten its script, but the same thing happens for nix-gc so I doubt that's the cause. The timer doesn't fire even when I turn on my machine, it only fires when I run 'nixos-rebuild/switch-to-configuration switch', which reloads systemd services, I tried omitting WakeSystem and/or setting persistent to false, also rebooted my system several times, none of which fixed the issue.
Here is my config: nix-gc nixos-upgrade systemd. I don't know if bug is specific to my config.
This is the last auto upgrade that worked: https://github.com/figsoda/dotfiles/commit/a1b0df36811ddaf3195da7d6b208a9741bebc8bc, I skimmed through the nixpkgs diff (https://github.com/nixos/nixpkgs/compare/32096899af23d49010bd8cf6a91695888d9d9e73...db25c4da285c5989b39e4ce13dea651a88b7a9d4) but nothing in particular caught my eye. It could also because I have rebooted my machine after this commit and some things have changed, so the issue could have been introduced before 32096899af23d49010bd8cf6a91695888d9d9e73.
All my other systemd timers (fstrim, logrotate, and systemd-tmpfiles-clean) seems to be working fine atm, so It might be because of some incompatibility between the specific modules (system.autoUpgrade and nix.gc.automatic) and systemd
Expected behavior
nixos-upgrade.timer to fire at 04:00 and upgrade my system
Additional Context
I am using ROG Zephryus G14 with the nixos-hardware module
Notify maintainers
@NixOS/systemd
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.0.6, NixOS, 22.11 (Raccoon), 22.11.20221103.a2a7775`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - nixpkgs: `/nix/store/brqf6qdrsq5s3k0siv47wbgrgz1i9dxz-source`

All my other systemd timers (fstrim, logrotate, and systemd-tmpfiles-clean) seems to be working fine atm, so It might be because of some incompatibility between the specific modules (system.autoUpgrade and nix.gc.automatic) and systemd

I'm not entirely sure I understand what's the problem here. Some timers wake up your system when suspended, but then don't run, and some do? Or in general, you didn't see any timer recently run properly after being woken up by suspend?
If it's only some timers, I'd probably propose carefully inspecting the timer definitions, see if you can spot any difference.

nix-gc and nixos-upgrade doesnt run until I do a nixos-rebuild, WakeSystem wakes up the system at the specified time even though the timer doesn't trigger. There could be something wrong with their definitions, but I haven't changed my config and they used to be working before the commit I mentioned.

Can you check if this is https://github.com/NixOS/nixpkgs/pull/199618#issuecomment-1310224853, and if the backport fixed it for you as well?

I have 100 packages to build, since it's in master already, I will just wait for it to get into nixos-upgrade and see if that fixes the issue

seems to be working now


Login Doesn't Work

I'm trying to login, via admin.<mydomain.com>:8080 but continue to get an error. I believe it's because of a Cors restriction on my browser when trying to access/fetch api.<mydomain.com>/login_.
I'm able to get an OK returned from api.<mydomain.com>/ping but when I attempt to access /login_ it fails even when I try to access it straight from the browser.

Some additional thoughts, I've read a handful of the other issues. I can see the importance of keeping this separate from open-balena. In this line of thought, maybe we could include https://github.com/Rob--W/cors-anywhere as another container for open-balena-admin to ensure api requests aren't blocked browser side? I'm no expert, so I'm not sure if this will actually help or fix the issues I'm seeing.

Turns out it was the way docker was being installed on the server side. When installed via repo the problem went away.


CI: pin to Ubuntu 20.04.

CI is currently broken because ubuntu-latest moved to 22.04, which is missing at least one package (libclang1-9 used in our CI jobs) and may be causing other issues as well.
This PR pins us back to 20.04; separately we should look into upgrading when issues are resolved.

Could this be done for just the jobs that are failing on main? I think most of them should be compatible with ubuntu-latest

Sure, updated to pin just the doc build and wasi-nn job; let's see if that's enough...

D'oh, thanks, I'm not sure where ubuntu-main came from; updated.


Inject CSS in 'head' instead of 'head-footer'?

Is there a good reason why the preloader CSS is injected into the content-for 'head-footer' hook instead of the 'head' hook?
head-footer comes after vendor.css and frontend.css, and it seams that the preloader css is evaluated only after those two css files are fully loaded. That means the preloader does not appear immediately, but only after loading the other css files, which defeats the purpose of the preloader...
I tested it with the head hook, and it worked as expected then! Can file a PR if needed, though it's only a little change in index.js.

I guess you can ignore this issue, must had some local caching issues. The preloader gets displayed after all css is loaded in either way. You would probably have to inject the normal css asynchronously by JS in some way to prevent waiting for it to load. Closing this, sorry for the confusion!

yeah everything in the  won't be shown until everything in the  tag is fetched. (except for scripts with an async attribute).
You might be on to something. Oerhaps there could be JS in the  that adds the preloader... not sure the order of events in that case -worth trying!


⚠ Secret Website 1 has degraded performance

In 363cea8, Secret Website 1 ($SECRET_WEBSITE_1) experienced degraded performance:

HTTP code: 200
Response time: 2483 ms

Resolved: Secret Website 1 performance has improved in 35a6fa0.


CAN Rearchitecture

CAN rearchitecture notes
Linked firmware repo PR
The idea is to use the YAML file to define CAN messages and signals, and generate the rest (DBC file, C headers and source for managing message data structures) with cantools and python scripts, all based on the YAML description. All auto-generated files are put under can/generated. CANMsgMap is a std::unordered_map wrapper (very much like the LookupTable but it's not const), I was hoping this could be shared by FW and SW.

looked through this but it was hard to follow. please be the first to review your code! Id appreciate more detail around the CANMsgMap

sorry my bad, some parts of this PR are still a WIP, but I just left some comments to explain what each of the files do

Going to merge this PR so that we can continue development with the new CAN stuff


Missing completion of kubectl config set-context

What happened?
The kubectl config set-context command does not automatically complete the existing contexts.
What did you expect to happen?
The contexts are automatically listed when the tab is pressed.
How can we reproduce it (as minimally and precisely as possible)?
kubectl config set-context <TAB>
Anything else we need to know?
No response
Kubernetes version

$ kubectl version
# paste output here
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-18T02:34:11Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider

Kind

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

Closed by https://github.com/kubernetes/kubernetes/pull/106739
/close


Fix handling of streams waiting for concurrency

Failure scenario:
Under load, a stream is added to the "waiting for concurrency list" due to the load. The associated call times out (deadline_timer) and it's cancelled (UNREF destroy). However, the stream is still in the waiting for concurrency list, which is processed in maybe_start_processing, popping it after it's been destroyed. Trace:
CALL_STACK 0x6220004bfab8:0x6220004bf100   REF 1->2 chttp2
CALL_STACK 0x6220004bfab8:0x6220004bf100   REF 2->3 deadline_timer
CALL_STACK 0x6220004bfab8:0x6220004bf100   REF 3->4 completion
CALL_STACK 0x6220004bfab8:0x6220004bf100   REF 4->5 perform_stream_op
Added 0x6220004bfab8 to CONCURRENCY_LIST
CALL_STACK 0x6220004bfab8:0x6220004bf100 UNREF 5->4 perform_stream_op
CALL_STACK 0x6220004bfab8:0x6220004bf100   REF 4->5 perform_stream_op
CALL_STACK 0x6220004bfab8:0x6220004bf100 UNREF 5->4 deadline_timer
REMOVE STREAM 0x6220004bfab8 , id: 0
CALL_STACK 0x6220004bfab8:0x6220004bf100 UNREF 4->3 chttp2
CALL_STACK 0x6220004bfab8:0x6220004bf100 UNREF 3->2 perform_stream_op
CALL_STACK 0x6220004bfab8:0x6220004bf100 UNREF 2->1 completion
CALL_STACK 0x6220004bfab8:0x6220004bf100 UNREF 1->0 destroy
Popped 0x6220004bfab8 from CONCURRENCY_LIST
maybe_start processing 0x6220004bfab8
CALL_STACK 0x6220004bfab8:0x6220004bf100   REF 0->1 chttp2_writing:become

This change makes sure the waiting for concurrency list is purged when the stream is closed.

jenkins test this please