tui-journal: 0.8.2 -> 0.8.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AmmarAbouZor/tui-journal/releases.
meta.description for tui-journal is: Your journal app if you live in a terminal
meta.homepage for tui-journal is: https://github.com/AmmarAbouZor/tui-journal
meta.changelog for tui-journal is: https://github.com/AmmarAbouZor/tui-journal/blob/v0.8.3/CHANGELOG.ron
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.3 with grep in /nix/store/3imdz11511px53cmnqqvgx7l1bhd3y01-tui-journal-0.8.3
found 0.8.3 in filename of file in /nix/store/3imdz11511px53cmnqqvgx7l1bhd3y01-tui-journal-0.8.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

tui-journal

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3imdz11511px53cmnqqvgx7l1bhd3y01-tui-journal-0.8.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tui-journal https://github.com/r-ryantm/nixpkgs/archive/d04e207c02a2ff4d0c3f848ff06d321955de9f02.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d04e207c02a2ff4d0c3f848ff06d321955de9f02#tui-journal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3imdz11511px53cmnqqvgx7l1bhd3y01-tui-journal-0.8.3
ls -la /nix/store/3imdz11511px53cmnqqvgx7l1bhd3y01-tui-journal-0.8.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

tui-journal

Maintainer pings
cc @figsoda for testing.

Result of nixpkgs-review pr 307486 run on x86_64-linux 1

1 package built:

tui-journal


feat(openebs_plugin): adding binary and initial implementation

This PR introduces a new unified plugin binary for managing OpenEBS cluster. Users will be able to interface all engines that gets installed via OpenEBS umbrella helm chart.

I see some formatting errors here Should we add rust fmt and clippy before merging this? CC @Abhinandan-Purkait

Yes, definitely. Let's please have proper CI before anything. :-;


tooling for lua back button

stack with max length
push: push and truncate old entries if over max length
pop: return pop or null
serialize to string
deserialize from string
we can only store strings?
I presume the way to do this is an array accessed as a list
we can assume the values are ascii and will not have commas
we can assume the string is under the max length, whatever that is
include whatever is proper for basic unit testing - something that can be run as a one-liner from a centos box
this can be a lua file that can be included

or, kluge instead of serializing an array into a string, just have 3 variables
push: not full? write to highest empty variable, full? move 2nd to 1st, 3rd to 2nd, then write to 3rd
pop: read and null highest empty variable


Add NosqlBench insertmany test

What this PR does:
Add Insertmany NoSQL Bench test
Which issue(s) this PR fixes:
Fixes this ticket
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed: DataStax CLA

overrode branch protection rules to close as no files were changed that would trigger CI workflows.


feat: Add channel priority to solve task and expose to python solve

There are use cases where disabling strict channel priority is important and so should have functionality in rattler such that it can be disabled. So I added it as a field of the SolveTask and exposed it as a new parameter (that existed before but was deleted) in py-rattler.

@ruben-arts here is my PR that we discussed earlier today, let me know what you think

@baszalmstra It does look like conda has three options: strict, flexible and disabled https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-channels.html#strict-channel-priority and they default to flexible. Rattler via resolvo is defaulting to strict. I can add an enum but maybe with only two values, strict and disabled for now? And flexible could be added later if needed?
And I see there is a flag for strict priority for libsolv that micromamba uses but I'm a bit ignorant to how this would be translated to this code.

Sounds good! Maybe wolf can help with the libsolv side.

@baszalmstra @wolfv Sorry for the repeated pings, this is just a fairly important change for our workflows.
If we can't resolve why libsolv isn't behaving expectedly with strict channel priority, I can just throw if someone specifies strict when using libsolv? And strict handling could be added later

@BenjaminLowry I made a PR against your branch here: https://github.com/BenjaminLowry/rattler/pull/1 It shows how we could set the priority for libsolv.
Libsolv has a priority and a subpriority integer value. The higher priority should win. We would also need a map or count down the channels and I haven't yet investigated how to do that with the structures at hand.

@wolfv Thanks for the PR, I added logic to assign repo priority values where it's determined by the order of the repodatas passed in where the channel with the first repodata is given the highest priority and it descends from there. This is pre-computed so we don't have to do some arbitrary highest priority value and so if you have 5 channels the first will be given 5 and the last will be given 1 and 0 is still available for lowest priority use.
This is now behaving as expected for libsolv with strict and disabled priority, does this implementation seem reasonable? Let me know if I'm not following specific rust-isms as well

@baszalmstra I'm assuming you also want @wolfv to give a +1? Or is this good to go

Yeah since @wolfv has a bunch of open comments I was waiting for his approval as well. 😄
Wolf if you are reading this, can you merge if you are happy with this?

@baszalmstra Thanks for already working on a release! I saw that py-rattler was bumped to 0.4.0 yesterday, will we be able to ship this change in a new release of py-rattler soon?

Sure! I can make another release in the next few days.

py-rattler 0.5.0 is on pypi which includes your changes.


Attempting to send SOL crashes app

Describe the bug
Entering an amount or otherwise trying to send SOL causes the Helium Wallet app to crash.
To Reproduce

In an account with sufficient SOL, go to the token balances screen.
Click on SOL token balance to open up SOL activity page (which does not display any activity, but that is another issue).
Press Send.
Fill in a valid Solana address. [Also note that this page does not display the SOL balance, it displays MOBILE balance.]
Click on Enter SOL Amount -> crash.

Reproduced on iPhone 14 Pro, iOS 16.4.1

An Android user reported being allowed to send SOL but receiving this error and failure when trying to do so.

Oops, resolved in 2.0.6, was on wrong version. confirmed working in 2.0.6. Will open up separate issue for Android error message


[CSS]: .NET Aspire GitHub Repository link should be under references

Article title
N/A
Article URL
N/A
Description
As of this moment, under the troubleshooting section, there is a link to the .NET Aspire GitHub repository. This link would be better placed under either Reference or resources - I can understand the logic behind putting it under troubleshooting, nonetheless I see this more as reference material than rather troubleshooting material.

We usually reserve References for API docs or things that serve as reference material. We do have the .NET Aspire Repository linked to on the Hub page and in the TOC under the Resources node. I'm going to close this:


Use stdlib fallible alllocation primitives

Rust 1.57 stabilized stdlib fallible allocation, so it would be beneficial to replace the relevant code in this crate to use the stdlib where possible. I still think there's a lot of value in the distinct fallible collection types, however, since the stdlib collections require calling the fallible reserve functions appropriately to avoid infallible allocations.

Done in #24

Awesome! Thanks @kornelski


openssf: shared google drive

need a shared google drive that is owned by the pyrsia gmail account and shared access to the pyrsia google group (as editor)

Google Drive: https://drive.google.com/drive/folders/1O4t9020qhNbI7uyB5LacaVWeTV_bZfUm


Added SubscriptionValidator class and unit tests. Add validation of n…

…ew and updates of subscription before subscription is written to Database.
Now its ok to do the review and merge if the code changes is +1.
Good starting point is to review the unit test class and see if I validate test all situations. I have maybe missed some situation/usage of how each parameter is used.
This implementation works with EI Frontend and if a parameter fails in the validation, user is informed via a popup window in EI Frontend.
If you think we cover all situations in thes unit tests and in the validator class. Then give a review comments, example "Looks good." / "+1".
I will improve Javadoc etc. in next commit and if you feedback, I will take car of those at same time.
And after next commit we can merge this change.

Removed the validation of Repeat flag in the Subscription object, since it will always be boolean and there is nothing to test.


Set containerd LimitNOFILE to recommended value

Description of changes:
The service unit in AL2 currently sets LimitNOFILE=infinity on containerd. This is known to cause issues, and the recommendation is to set it explicitly to LimitNOFILE=1024:524288 on systems using systemd older that v240.
More info: https://github.com/containerd/containerd/pull/8924
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.to replicate. -->
See this guide for recommended testing for PRs. Some tests may not apply. Completing tests and providing additional validation steps are not required, but it is recommended and may reduce review time and time to merge.

/ci

FYI, this AMI release caused issues in production for my eks cluster.
[2023-12-22 03:31:18.128][198][critical][assert] [external/envoy/source/common/network/socket_interface_impl.cc:72] assert failure: SOCKET_VALID(result.return_value_). Details: socket(2) failed, got error: Too many open files

Can we revert this PR? And is there a higher number or setting we can use for the default soft limit?
opened case with AWS, case ID<PHONE_NUMBER>01444

This also caused issues in production for our EKS cluster running envoy.
Very unlucky this was released the day before the christmas break.

+1 Same for my clusters

+1 here. The karpenter controller updated to the new ami and we crashed.
Failed to resolve '<url>': No file descriptors available (after 0ms in state CONNECT, 2 identical error(s) suppressed)

Yes, this resulted in a major production outage :(

Same same, Merry Xmas 🎅

The limit basically went from "infinity" to 1,024 with "infinity" looking to be 1,048,576 (aka 1024*1024) ... at least from what we saw. This seems a rather risky change to make without forewarning.

The limit basically went from "infinity" to 1,024

The soft limit. This is standard outside of containers (where it's been incorrectly set to infinity). Software that requires anything more than the soft limit is meant to request to raise that (with the hard limit as the ceiling).

This seems a rather risky change to make without forewarning.

All this change has done has exposed that software is incorrectly relying on bad settings in the first place. It would be better to identify what software that is and to have it correctly fix the problem at their end.
infinity had resulted in many bug reports over the years, and a very slow process in getting the change to fix it approved/upstreamed. I extensively researched the topic to justify the change as the correct approach. The only part of my contribution that was dismissed was keeping an explicit config with contextual comment for awareness as a form of documentation, with removal 12-24 months later.

Context
In the meantime, you would be advised to workaround that by setting a higher soft limit, but I would highly discourage infinity. infinity can resolve to approx 1 million (2^20), or worse over a billion (2^30) depending on the host system.
Notably with the 2^30 scenario is when other software that expects a sane soft limit (such as daemons), regress heavily in performance (a task that would complete in less than a second, can stall for 10 minutes.. or more than an hour).

Fedora's  DNF package manager was a good example of this IIRC.
rsyslog, postsrsd, fail2ban are all examples of software that was negatively impacted by infinity.
Some databases have had many reports of consuming excessive amounts of memory during init triggering OOM.

The soft limit is meant to be low, only raised for processes that are aware they need it and explicitly request to raise it. Please respect that.
Github Actions has a hard limit of 65,536 (2^16) on their CI runners for example. The limits apply per-process, 2^16 may be too low of a hard-limit for larger production deployments (with databases), but it's more likely you're encountering software that hits the 1024 soft limit and doesn't attempt to raise the hard-limit at all, which is an easy bottleneck to hit (implies the software is only ever really deployed within a containerized environment, otherwise that'd have been fixed promptly).

Workaround
If you must raise it as a workaround, do not use infinity. 524288 (2^19) should easily satisfy the majority of software (enough to run 65k busybox containers with 200GiB+ memory).
The cases where that is insufficient are generally documented by the software and workload dependent.
For Envoy, there is this 2019 issue regarding limits. That is a demonstration of where you'll need a sufficient hard limit. This 2022 issue also requests for Envoy to raise the soft limit, but the maintainers dismiss the request.

All this change has done has exposed that software is incorrectly relying on bad settings in the first place. It would be better to identify what software that is and to have it correctly fix the problem at their end.

I disagree with your assessment here. This may be true for the soft limit change, but this recommendation also changed the hard limit, which caused applications that legitimately request a higher ulimit than the new hard cap to fail. That is the failure mode that our workload encountered as a result of the AMI update.
Raising the hard limit therefore isn't just a "workaround" as there are plenty of legitimate use cases where software may need more than 500k FDs. It would be better to recommend a higher hard cap - sure infinity is not ok at this stage, but why recommend 2^19 instead of 2^20 for example?

TL;DR:

My contribution to prefer the defaults 1024:524288 still seems valid, but I can understand it not being appropriate with the deployments you work with.
You should have more flexibility with the hard-limit, most of the regressions that infinity caused were due to the soft limit not being 1024 AFAIK. But software will raise the soft-limit to the hard-limit implicitly, any regression will scale with that increase.
524288 seemed appropriate for workstations and CI.

I don't have expertise in large deployments to advise an appropriate hard-limit.

Try 2^24? (16.77 million, only a 32x increase much less than 2048x)

Prior to infinity the limit was set to 2^20  (only because it was more than enough) to removing a few hundred containers (probably due to an implicit 1024 soft limit), not for any specific process needs within a container. The context for raising to infinity was lacking and seemed misunderstood.

In the collapsed section below, I would like to highlight an interest in knowing what use-cases are demanding more than 500k FDs per process.

If the process can spawn child processes that can delegate the workloads creating all those FDs, they'd each have their own limit which does not contribute to parent process usage.
What is the software doing where that requires all FDs managed by a single process? Especially at scale where I thought load balancing multiple instances was a common practice?
Could you share what sort of peak FD usage you're seeing for a process?
If these are open-source projects like Envoy, could you cite them please?

Original response (verbose)

which caused applications that legitimately request a higher ulimit than the new hard cap to fail. That is the failure mode that our workload encountered as a result of the AMI update.

Yes, sorry about that.
I was not aware that you were unable to set a limit higher than the AMI LimitNOFILE hard limit, that's not applicable from my contribution which did the opposite (removed LimitNOFILE from service configs, where you can configure a higher hard-limit like it was before via a systemd drop-in override).
I don't have access to such environments, only what I could find online in discussions / reports and software docs.

I don't recall finding anything that needed more than systemd default hard-limit of  524288 / 2^19, and had extensive research coverage documented for anything I was aware of.
With Envoy, there isn't any documentation on the subject only a few issues where the Debian hard-limit of 2^20 was not sufficient and maintainers advice to set the soft limit to max 🤷♂

Out of curiosity, is the software that raises the soft-limit to the hard-limit public? Does it document that requirement or is it specific to the scale of your deployment needs?
Does your software actually use more than 2^19 FDs per process, or was the problem that you had an explicit hard-limit set like 2^20 where only that failure is the issue and it could have functioned fine with 2^19? (I only say this since sometimes configuration is parroted, especially when the values are sourced as "works for me")

It would be better to recommend a higher hard cap - sure infinity is not ok at this stage, but why recommend 2^19 instead of 2^20 for example?

The other main motivation behind choosing 524288 was for consistency outside of containerized environments.
You'd have to raise the hard-limit there, so the assumption was businesses would have the talent with expertise to more easily identify this configuration need and handle it (vs the many individuals affected by the bugs infinity caused).
It's a bit problematic when software that runs fine out of a container behaves in weird unexpected ways in a container environment due to defaults biased to enterprise.
Doubling this hard limit did not seem worthwhile to match the traditional hard-limit of 2^20 (that existed prior to systemd v240 normalizing one, IIRC it was not as consistent prior, but 2^20 was a bound set by the kernel but not the default hard-limit)
It's been years with 524288 being adequate (it was not chosen arbitrarily).

If it were a more common issue encountered, there would be a larger push to raise it? (Over a year since the change, the author notes how there was little pushback received from the reduced hard limit)
The only time that doesn't seem to be the case is with enterprise deployments, and 2^20 is not necessarily enough in that context (according to an Envoy report) nor yours it seems? Aligning with systemds hard-limit seemed like an appropriate decision?

Raising the hard limit therefore isn't just a "workaround" as there are plenty of legitimate use cases where software may need more than 500k FDs.

I'd appreciate you sharing some of those use cases?

The limits are per process (child processes have their own limit, they don't contribute to the parents FD limit usage), thus software that can scale horizontally via multiple processes to split the FD usage is better than a monolithic process amassing FDs.

My "workaround" advice refers to raising the soft-limit to 2^19 as an example for software like Envoy that won't raise it.

There is no workaround suggestion regarding the hard-limit, which I state is possible but should be obvious when you need it.
The "workaround" phrasing was more oriented towards reverting the soft limit. Since the diff from this PR is only additive, I don't know what the limit was prior? 🤷♂ (looks like it's eagerly applying the change arriving in containerd v2?)
Thus in future, the AMI may add a similar config override but instead prefer LimitNOFILE=42 (where 42 is whatever soft limit with implicit hard limit is deemed appropriate).

Otherwise the 1024 soft limit is still likely to cause some problems it seems until affected processes raise it internally.
Meanwhile the more you increment the soft limit from 2^19 to 2^30 the more that regression scales on affected software, additionally anything using select() implicitly will be fun to troubleshoot.

I have no real opinion with the AMI configuration here, other than discouraging infinity.

Those contributing such a change here should hopefully understand the context of what limits would be appropriate. It's not a fun topic, so I can understand why the change to Docker / containerd may be followed.
This is not an area I work in, but those that do could help contribute what the highest FD usage for a process they observe is?
Some software implicitly raises the soft-limit to the hard-limit, and it has been observed with MySQL and JDK allocating memory equivalent to the limit (524288 4MB vs 2^30 8GB).

MongoDB documents 64k, Kafka documents 100k (as a minimum).

Since I doubt anyone wants to guess a sufficient value that turns out to be too low once deployed, I would assume many would set a value that seems high enough (with typical advice online being 2^20 or infinity).
Tuning the value down could be done, but if raising it high enough doesn't cause any problems I don't really see anyone investing the time (if there is no clear benefits from doing so).

The approach systemd took involved finding what an appropriate hard limit would be with a variety of software and feedback cycles IIRC. Initially it was going to be 2^18, possibly less. I recall Google Earth needed around 300k, and was one of the reasons the limit was raised to 2^19 before official release of v240.
For Docker and containerd, since they no longer set LimitNOFILE they just go with what is configured as default by systemd.

When that's not sufficient and you need a higher hard-limit, I believe you could still set that beyond 524288 per service as an override.

The change with the AMI here apparently sets a ceiling, which prevented your own config to exceed that.
On Docker and Containerd, I think I recall this not being the case and that I could have a container run with a higher limit than the one I set for dockerd / containerd processes.

The system-wide default could also be adjusted. I have very little AWS experience, but assume somewhere it would be possible to support your own override for the hard-limit when you need that, which shouldn't be blocked like you experienced? (if not perhaps that's a relevant feature request)


feat(bigquery): add support for query cost estimate

SUMMARY
The ability to know in advance how many bytes a query will process is important when using BigQuery.
This PR adds the ability to estimate query cost to BigQuery integration as well as other DB systems such as postgres and presto.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
before:

after:

TESTING INSTRUCTIONS

Enable feature flag ESTIMATE_QUERY_COST
Check ADVANCED > SQL Lab > Enable query cost estimation in the edit dialog in the BigQuery database connection

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

@betodealmeida Hello, I've fixed the points you pointed out, could you please review?

@betodealmeida @villebro I've been waiting for a review for about 3 weeks since last update, I'd love to get some feedback on whether something is wrong with my PR or reviewers are busy.
If reviewers are busy, It's no problem and I'll wait as long as needed. This is my first OSS commit, so I would like your advice if there is anything that is not good.

@kzosabe I'm really sorry for having dropped the ball on this PR 🙁 As you may have seen a later PR #21325 added this feature. I'd still love to get the humanize logic from this PR in, so if you're still open to working on this I promise to do my best to see this through without delay.

@kzosabe any interest in rebasing and following through on making this more about the humanize logic as @villebro suggested? If not, we should close this out. Thanks in either case, we appreciate the contribution!

I'm assuming that since @kzosabe hasn't responded, we missed the boat on that humanize logic. Thanks for the PR nonetheless, and we hope we see more of you around here. I'll close this, but feel free to re-open if you want to pick this back up!


Parse tile tree id and content id strings back to arguments used to create them

This builds on top of #1742 as I realized that won't be enough for a round-trip. I intentionally kept TileOptions.fromTreeIdAndContentId because sometimes it's useful just to see what TileOptions were used without wasting resources on additional parsing.

@Mergifyio update


Bug Fix #1449

Pull request checklist

[Yes] This fixes issue #1449
[Yes] All tests pass. Demo project builds and runs.
[ No merge conflicts] I have resolved any merge conflicts.
[YES] I have squashed my commits into 1 commit.
[Yes] I have followed the coding style, and reviewed the contributing guidelines. Confirmation: ____

What's in this pull request?

...

It doesn't seem like you can change the height of the inputToolbar using the documented property preferredDefaultHeight since it is used to configure the height constraint in viewDidLoad.
In order to fix the bug I added the line of code:
self.toolbarHeightConstraint.constant = self.inputToolbar.preferredDefaultHeight;
In the method:
viewWillAppear, and now the view load with the correct constraints.

Hey @GuyKahlon — this looked good, what's the reason for closing?

I don't know, I got a message some unit tests are failed, I send you a new pull request.


Allow Icons as rightElements in inputs, Fixes #1803

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[X] Caught up with develop branch as of last change.
[X] Added CHANGELOG entry, or determined not required.
[X] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[NR] Updated doc comments / prop-types, or determined not required.
[NR] Reviewed and tested on Mobile, or determined not required.
[NR] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Thanks Don!  Tom -- can you review and merge?

Hi - I looked at this for a while on the plane as I had been curious what was going on.
See https://github.com/xh/hoist-react/commit/7251f2152c5f0b7eb06483dfb0ebef3ebc8b4c71 for an alternate approach - it led me down a bit of a rabbit hole with how elements are sized and ultimately this bit of code in the BP input that sets up the padding added directly to the input element - https://github.com/palantir/blueprint/blob/0c7c2090fcf0e3e65ee5ab434d623df53912e9ee/packages/core/src/components/forms/inputGroup.tsx#L158

Thanks for this Don! Looks good, and solves the issue. :)
However, I think it would be better to take Anselm's alternative mentioned above - the change is more minimal, doesn't require our inputs to check the type of element passed and gets to the root of the issue w.r.t. BP's sizing calculations (and supports any width for icon, should we want to).
I'll close this in favour of that PR, make a couple of tweaks there and merge.


fix frontend financial year calculation and pdf financial dates display

 [QAE16IMP] Data misalignment between online dates and downloaded copy

@dreamfall seems specs failing https://circleci.com/gh/bitzesty/qae/1726

:+1:


Get the actual character velocity

Question and/or Comment
Hi,
I'm currently working with the "CharacterComponent".
You can set the desired velocity with the "SetVelocity" function.
But is there a way to get the actual velocity?
E.g. if you run into a wall, the character will stop. So, I need the actual velocity to create the reaction and slow the animation down or anything like that..
thx,
abgenullt

The PR has been merged in, looks like that's what you were looking for, I'll close this one off then.


impossible to make width:100% in style css

.iti {
width: 100%;
}

@rinaharry Please describe your issue fully. I hope @wnabil 's comment is solved your issue.

@rinaharry Please describe your issue fully. I hope @wnabil 's comment is solved your issue.


Add support for symengine (WIP)

Closes #70

Codecov Report

Merging #87 into devel will decrease coverage by 1.24%.
The diff coverage is 56.38%.

@@            Coverage Diff            @@
##           devel      #87      +/-   ##
=========================================
- Coverage   88.8%   87.55%   -1.25%
=========================================
  Files          8        9       +1
  Lines       2385     2451      +66
  Branches     542      551       +9
=========================================
+ Hits        2118     2146      +28
- Misses       166      197      +31
- Partials     101      108       +7

Impacted Files
Coverage Δ

optlang/expression_parsing.py
76.31% <40%> (-2.86%)
:arrow_down:

optlang/symbolics.py
52.05% <52.05%> (ø)

optlang/interface.py
90.04% <80%> (-0.14%)
:arrow_down:

optlang/glpk_interface.py
85.49% <83.33%> (-0.06%)
:arrow_down:

Continue to review full report at Codecov.

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

Awesome :+1:


[feature] Allow Raspberry Pi to run changedetection.io also

Version and OS
Raspberry Pi 4 model B, Raspbian, running Docker.
Is your feature request related to a problem? Please describe.
I have a raspberry pi 4 at my disposal and I'm very frustrated when playwright just does not work with ARM.
Describe the solution you'd like
I would like to somehow change it so that Raspberry Pi can do the step browser like with playwright/browserless one.

Hi, no, sorry, this is an issue with playwright which is unrelated to our project, we only scrape the data from it


TypeScript Support

main.ts
import Vue2TouchEvents from 'vue2-touch-events';
^
Could not find a declaration file for module 'vue2-touch-events'.

Fast and dirty. May be useful for someone.
@jerrybendy You can close this issue.
Anyway it would be nice to have full Typescript support.
Thanks.
remove .txt extension
TouchEvents.ts.txt

I'm not familier with TypeScript. Could you add a PR about all your changes?

My changes are not backward compatible.
I wrap you vueTouchEvents object according Vue.js-Plugins with TypeScript
And it could not be used from vanilla JavaScript any more.
Besides of that I used type  for fast solution, what is not good for production. So I got completely  separate file and maintain 2 files (.ts and .js) with the same functionality, in my opinion, is not good idea.
Right solution is to create types file (.d.ts)
I'll try to find a time and generate .d.ts ( tsc --declaration fileName.ts ) compatible with your .js but not manually. Or maybe someone will be faster than me.


New issues on draft and guide

[x] For the server.xml file, regarding line The servlet-3.1 feature is also needed for running the application, as well as other items which are described in the XML comments. It’s recommended to have the explanation in the guide instead of in the comments. There are couple reasons, one to keep the code clean, and second, our guides are meant to be conversational focus, not so technical focus to have user to follow the code.
New: Replace the original hello.Application class with the following code: => It’s recommended to include the full path of the hello.Application class, ie, src/main/java/hello/Application.java. Some user may not be able to find that file (I think that’s the one) by reading hello.Application class.

[x] Got this error after working the guide on the start directory and run the mvn liberty:start-server command. Error in the console.log:

[ERROR   ] CWWKG0014E: The configuration parser detected an XML syntax error while parsing the root of the configuration and the referenced configuration documents. Error: The processing instruction target matching "[xX][mM][lL]" is not allowed. File: file:/Users/evelinec/OLG/testing/draft-guide-springboot-mvc/start/target/liberty/wlp/usr/servers/MVCServer/server.xml Line: 3 Column: 6
[WARNING ] CWWKF0009W: The server has not been configured to install any features.
[AUDIT   ] CWWKF0011I: The server MVCServer is ready to run a smarter planet.

[x] I think the duration of this guide doesn't need 30 minutes. 15 - 20 minutes is good.

Regarding the XML syntax error, are you sure you copied the server.xml properly? Log says that it is complaining about line 3, which in the original source is
<application context-root="/"
        location="guide-spring-boot-mvc.war"></application>

I figured out the problem about the xml syntax error. Basically, the problem is if the xml file starts with empty lines. In working through this guide, somehow, when copy the snippets of code or classes to create a file, there's always 2 empty line added at the beginning of the file. While looking at the readme.adoc, there're couple problems and some suggestions to fix:

Most of the code snippets were pasted directly on the readme.adoc, which is not good.
Try to use include with tags to include code snippets.

Example from the CDI-intro guide: https://raw.githubusercontent.com/OpenLiberty/guide-cdi-intro/master/README.adoc::
[source, Java]
include::finish/src/main/java/io/openliberty/guides/inventory/InventoryResource.java[tags=**;!copyright]

Try to use source with type to identify the type of file included. Example:

[source,xml,indent=0, role="no_copy"]
include::finish/pom.xml[tag=bootstrap]

FYI, I still see hello.Application path being used in the 8/30's draft.

Talked to @chyt to address the other 3 pasted code snippets in the readme.

Resolved.


Home and Events: Tag when Metro makes a change to an event

We will look at the "updated_at" (also "created_at") field for an event. If Metro updates the event within, say, two weeks of the meeting, then the event will get a tag or bold font or something to indicate that the event has been modified.
@shrayshray Can you let us know the time boundaries for this, e.g., two weeks before an event? or keep the tag for 72 hours after an event gets updated?

After an agenda is final (i.e., the PDF is available), if there are any changes to it, it should be highlighted in some way and display the text "Updated" next to the date/time.

@shrayshray
Did we reach a consensus on when an event should be highlighted (e.g., if a change is made one, two, three weeks before a meeting)?
Also: Moving this to June issues.

@reginafcompton Yes -- it should be highlighted if there is a change to the date or time, or if the meeting is cancelled, after the Agenda is final/PDF is available.

To accomplish this we need to do the following:

add an "updated_at" field in the EventDocument in django-councilmatic: https://github.com/datamade/django-councilmatic
in the event detail view, add a comparison between the EventDocument updated_at and the Event updated_at

@shrayshray - we are wrapping up this issue, today. Here's a screenshot of what to expect, when an event gets updated, after the agenda has been added.

Quick clarification: This updated tag will only appear for upcoming events, not past events. Is that right?

Perfect, thank you!


MSYS2 issues in GitHub project are disabled

The MSYS2 website says "file issues on GitHub", however https://github.com/msys2/msys2 has issues disabled. Where is one supposed to file MSYS2 issues?

Here or https://github.com/alexpux/mingw-packages

@jtanx if MSYS2-packages is indeed the correct place to file MSYS2 bug reports unrelated to packages, then the website needs to be updated. Well, it needs to be update either way.

From https://github.com/msys2/msys2:

Issues must to be posted into MINGW or MSYS2 packages repositories ONLY.

From http://www.msys2.org/

file issues on GitHub https://github.com/msys2/msys2/issues

From msys2 repo it looks like the project is dead with issue tracker closed. That comment in the end of README doesn't really help.
Published a PR with better directions for future users with similar issues.

Agree. Website should point here or at least not mislead anyone following the link. explicitly pointing people to a nonexistent issues page is unhelpful, even if it's just to see who reads the instructions and who doesn't. Need a new strategy.

Reporting issue is now easier. First, search the package here https://packages.msys2.org/search and click on the appropriate one. Click on the "Report Issue" link which will automatically redirect to issues page.


none: reformat after #16248

see #16263

if you can ign fmt revs, and pls help double check, thx.

test failure try to be fixed at #16267


Inconsistent extension schema format

There are inconsistencies in how the schemas inherit other requirements, e.g. an Item schema not inheriting the Item schema as a requirement.
For example, in EO, there is a allOf ref to Item, as well as internal definitions:
https://github.com/radiantearth/stac-spec/blob/master/extensions/eo/json-schema/schema.json#L6
In the label extension, we don't have that same allOf structure:
https://github.com/radiantearth/stac-spec/blob/master/extensions/label/schema.json
We've seen that this means a validation against a label item schema can be incorrect, as it does not also validate that it is an Item.

I'd also recommend that as part of this, we maintain consistency in the extensions of placement for and naming of the schema file. To follow the schemas of the core objects, extensions should:

Place their schema in a folder under the extension called json_schema
Be named with the extension and the object the are extending, e.g.: eo-item.json, label-item.json

The reason for the inconsistencies is simple. We don't have anybody who is the main instance to maintain the JSON schemas and people writing extensions do the schema often just as a side project without really knowing what they are doing as we also don't have any guidelines for that. So yes, fully agreeing with you. PRs are welcome.

Great, thanks @m-mohr. My colleague @simonkassel fixed a few of these in the branch he mentioned in #618, and we are planning on fixing the rest as well.

@lossyrob One thing I forgot: Please check back with @jbants regarding the restructuring. I think he renamed all extension schema files to schema.json at some point so that it works better with STAC validator. Not sure how much the validator relies on the structure.

I'm all for this, along with any sort of documentation/guidelines.  What I've done in the past when writing an extension is use another extension's schema as a template, fiddle with it a bit to generate some sort of Frankenstein schema that doesn't work, then @m-mohr goes and fixes it.

Yeah, JSON Schema can be tricky at times. I'm usually using https://www.jsonschemavalidator.net/ to check the schemas against the examples when writing them.

With https://github.com/radiantearth/stac-spec/issues/623 it should make ensuring extension schemas are correct as a necessary part of merging PRs.
@jbants I had some ideas on how to implement that, and want to touch base about the schema filenames. Will you be at the sprint? Maybe something we can hammer out in DC.

@lossyrob Yup, I'll be there. Lets chat then.

The original issue has been fixed in issue #828.

And the other issue is tracked in #835


Blank notebook editor after trying to open Jupyter notebook for the second time

]

VSCode Version: 1.52.1
OS Version: Ubuntu 20.04.1 LTS (Windows Subsytem for Linux)
Windows 10 pro Version 10.0.19042 Build 19042

Several times if I put the computer into sleep mode and then re-activated it and tried to open a jupyter notebook. The issue occurred. I restarted my computer and the problem was resolved.

Close it and put the computer to sleep
Wait for several hours, start the computer again and try to repeat steps 1 and 2.
Notebook editor is blank and shows nothing

Does this issue occur when all extensions are disabled?: Yes/No (have to start Python extension)

/extPython


Golden EAK shows as invalid despite being valid

Describe the bug
A volunteer (Landkreis Kulmbach, EAK) activated its GOLDEN card by scanning an activation code.
The "Ausweisen"-Tab shows their golden card including their name, but below, there is the following error message:
"Ihre Karte ist ungültig. Sie wurde entweder widerrufen oder auf einem anderen Gerät aktiviert."
On a different device (without some specific security setting) activating the card worked without problems.
Unclear:

Did the error message show directly after scanning the Ausweisen Tab
What kind of seurity setting is activated?

To Reproduce
TODO: Describe steps to reproduce the behavior.
Expected behavior
There should not be an error message, but instead a QR Code after succesfully activating the code.
Smartphone:

Device: ?
OS: Android
Version ?

@michael-markl can we get the device and platform version? specific android version?


doc: add rakoff token

Description
Adding Rakoff Token from Terra Classic. Thank you for review.
Humbly,
Till
Adding Assets
If adding a new asset, please ensure the following:

[x] Asset is registered to the Cosmos Chain Registry.
[x] Add asset to bottom of zone_assets.json.

[x] chain_name and base_denom are provided and use values exactly as defined at the Chain Registry.
[x] path is provided, and the IBC channel referenced is registered at the Chain Registry (unless native to Osmosis).
[x] osmosis_verified is set to false
[x] listing_date_time_utc is specified and accurate
[x] Optional: transfer_methods, peg_mechanism, override_properties, canonical, categories, where necessary (see README for details).

Thanks for doing the quick updates 👍👌


cdc: Implement Endpoint and enable it in cmd/server

What have you changed?
This PR migrates Endpoint part from overvenus:tikv/cdc to master. This part defines thwo CDC requests are processed.
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

Unit test
Integration test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

CI failed


updated quotereply newlines from 1 to 2

Fixes: <!-- Issue link, or clear description.-->

Screenshots and screen captures:
 Went off previous pull request to make changes to quoted replies padding (https://github.com/zulip/zulip/pull/23614)
Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Closing in favor of https://github.com/zulip/zulip/pull/23614, which this seems to duplicate without explanation.


Enabling a disabled WebJob resulted in the WebJob starting

after 5 seconds it was stopped and started again.
This is due to 2 things that were fixed in this change:

Enable job deleted the disable.job file but also started the job, deleting the file causes the job to restart after 5 seconds.
Fix is to not start the job and have the file change detection do it.

Enable / Disable job causes file change twice, once after creating or deleting the disable.job and a second time it seems the directory of the job is changed but this only happens after the job refreshes which causes it to refresh again.
I could pinpoint exactly why this happens but "change" file notification on the job directory is not important and so we will ignore it.

Also added log line for when WebJob files update causes WebJob refresh.
Fixes #1549

Looks good.


Adding support for android intents

anime dl naruto --play android -c 1 -p animefreak despite being 1 episode long (movie), still waits for input

Unless we do some checks to see how many episodes are in the show that may be a little difficult to fix as the current logic only looks for if an -e argument is applied and what it's contents are

Works, merging


Kirki does not load assets in customizer on develop version.

Issue description:
Kirki isn't loading any of its assets in the customer for the controls.
Version used:
Latest develop version
Using theme_mods or options?
Whatever the _s theme is using... I believe theme_mods
Code to reproduce the issue (config + field(s))
This is what I'm using:

Blank WP install
_s theme provided by you https://github.com/aristath/_s
Only plugin active is Kirki

Yes just tried few mins ago, same issue.

@bawright @UsmanShahzad Can you please try this again?
Please do a git clone --recursive however, because a lot of the assets were moved to a separate repository so you may not be getting them if you already had kirki cloned locally and did a git pull

It's working, thanks @aristath
New version loads at least 50% faster btw, nice job!


Feat/staging deploy

What does this PR do?

Add docker build scripts to support staging deploy

How should this be manually tested?

Please include the steps to be done inorder to setup and test this PR.
Ensure any data required has been exported via yarn scripts strapi export

What are the relevant github issues?
Screenshots

Merge into #135


Fix variable name so it reaches reproducer-variables

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/lgtm


chore: add stryker

Coverage increased (+2.4%) to 83.529% when pulling ea1cf0a69e4f60ac8445cc2f52037998d13b2bb8 on chore/stryker into c91e7dc39924d992b7b7ec546d7fad8a02bc4180 on master.


Correctly handle default for Request params

I was having issues where the signature calculated was incorrect for GET methods that didn't have params (e.g. pusher.users_info(channel))
I discovered the reason is that the default params is being reused, and the second call to the method still has the auth_signature from the last call present (which causes this call to have an incorrectly calculated signature).

Thanks @martynsmith


Android: Add support for requesting authentication for actions on Android 12 notifications

I would like to suggest adding support for requesting authentication for actions on Android 12 notifications through the .setAuthenticationRequired(true) method. This feature would add an extra layer of security to android notifications by requiring user authentication before allowing any actions to be taken.
Unlike iOS, this will have to be configured at the global notification level, not the action level.
It would be used in this way:
notifee.displayNotification({
    ...,
    android: {
      ...,
      authenticationRequired: true
    },
  });

What would you think of this addition?

Love the suggestion. Would be a great enhancement. 😎

Can't we leave the issue open?
Even if there are no immediate plans, it's still an interesting addition. I might even try to take care of it, despite my lack of Kotlin / Java / Android skills.


Feature request (Auto-download enabled only for favorite devices)

Is your feature request related to a problem? Please describe.
I want to enable auto-download feature but since there are no notifications, I'm afraid I'll received unexpected files when on a public network and not know about it.
Describe the solution you'd like
One of the solutions I can think of is enabling auto-download only for favorite devices so that the auto-download works only for my own devices.
Describe alternatives you've considered
No response
Additional context
No response

This is part of the next release (1.16.0) https://github.com/localsend/localsend/blob/main/app/assets/CHANGELOG.md


Bump<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Description of the change

Bump<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation or Development tools (readme, specs, tests, code formatting)

Links

Jira issue number: (PUT IT HERE)
Process.st launch checklist: (PUT IT HERE)

Checklists
Development

[ ] Prettier was run (if applicable)
[ ] The behaviour changes in the pull request are covered by specs
[ ] All tests related to the changed code pass in development

Paperwork

[ ] This pull request has a descriptive title and information useful to a reviewer
[ ] This pull request has a Jira number
[ ] This pull request has a Process.st launch checklist

Code review

[ ] Changes have been reviewed by at least one other engineer
[ ] Security impacts of this change have been considered

changelog update and ready for 🚀


How to make it work in a HOC.

In my app, I have some routes to protect... so the best way I found to do this was to make a HOC component (I'm using NextJs btw).
  const withAuth = (Component: React.ComponentType & NextComponentType) => {
    const Auth = () => {
      const router = useRouter();
      const token = useSelector<ApplicationState, string>(
        state => state.auth.token,
      );

      if (!token) {
        router.push('/login');
      }

      return <Component />;
    };

    // Copy getInitial props so it will run as well
    if (Component.getInitialProps) {
      Auth.getInitialProps = Component.getInitialProps;
    }

    return Auth;
  };

  export default withAuth;

With this HOC, I surround some pages like so...
const Dashboard: React.FC = () => {
  const router = useRouter();
  const { t } = useTranslation('dashboard');

  return (

      <Link locale="en-US" href={router.pathname}>
        Change to english
      </Link>
      <Link locale="pt-BR" href={router.pathname}>
        Change to portuguese
      </Link>

{t('hello')}

  );
};

export default withAuth(Dashboard);

My problem is that when I do this, the page isn't compiled with the translations, so I believe something is missing in my HOC(I know this because the translation works when I remove the withAuth() in the page). Can someone help me on this please.

OK guys, I found a correction for this problem.
my _app.tsx was like this and the translation wasn't working
...
export default function MyApp({ Component, pageProps }) {
  const router = useRouter();

  const noLayout = ['/login', '/logout', '/forget-password'];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
}

I don't know why, but I changed this component to look like this
...
import { AppProps } from 'next/app';

const MyApp: React.FC<AppProps> = ({ Component, pageProps }) => {
  const router = useRouter();

  const noLayout = ['/login', '/logout', '/forget-password'];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
};

export default MyApp;

Just typescripting the function, the translation worked again. I have no idea of why this happened and why it is fixed. LOL

OK guys, I found a correction for this problem.
my _app.tsx was like this and the translation wasn't working
...
export default function MyApp({ Component, pageProps }) {
  const router = useRouter();

  const noLayout = ['/login', '/logout', '/forget-password'];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
}

This is transpiled by next-translate 1.0.2 to:
import __i18nConfig from "@next-translate-root/i18n";
import __appWithI18n from "next-translate/appWithI18n";

const __Page_Next_Translate__ = function MyApp({ Component, pageProps }) {
  const router = useRouter();

  const noLayout = ["/login", "/logout", "/forget-password"];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
};

export default __appWithI18n(__Page_Next_Translate__, {
  ...__i18nConfig,
  isLoader: true,
  skipInitialProps: false,
  loadLocaleFrom: (l, n) =>
    import(\`@next-translate-root/locales/${l}/${n}`).then((m) => m.default),
});

I don't know why, but I changed this component to look like this
...
import { AppProps } from 'next/app';

const MyApp: React.FC<AppProps> = ({ Component, pageProps }) => {
  const router = useRouter();

  const noLayout = ['/login', '/logout', '/forget-password'];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
};

export default MyApp;

Just typescripting the function, the translation worked again. I have no idea of why this happened and why it is fixed. LOL

And this is transpiled to:
import __i18nConfig from "@next-translate-root/i18n";
import __appWithI18n from "next-translate/appWithI18n";

import { AppProps } from "next/app";

const MyApp: React.FC<AppProps> = ({ Component, pageProps }) => {
  const router = useRouter();

  const noLayout = ["/login", "/logout", "/forget-password"];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
};

const __Page_Next_Translate__ = MyApp;

export default __appWithI18n(__Page_Next_Translate__, {
  ...__i18nConfig,
  isLoader: true,
  skipInitialProps: false,
  loadLocaleFrom: (l, n) =>
    import(`@next-translate-root/locales/${l}/${n}`).then((m) => m.default),
});

@mateus-schultz Apparently, I don't see any problems during transpilation.... What version of next-translate do you use?

@aralroca , Thanks for your reply.
This is the version:
"dependencies": {
"next": "10.0.4",
"next-translate": "^1.0.2",
"react": "17.0.1",
"react-dom": "17.0.1",
}

it really works!

OK guys, I found a correction for this problem.
my _app.tsx was like this and the translation wasn't working
...
export default function MyApp({ Component, pageProps }) {
  const router = useRouter();

  const noLayout = ['/login', '/logout', '/forget-password'];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
}

I don't know why, but I changed this component to look like this
...
import { AppProps } from 'next/app';

const MyApp: React.FC<AppProps> = ({ Component, pageProps }) => {
  const router = useRouter();

  const noLayout = ['/login', '/logout', '/forget-password'];

  return (
    <Provider store={store}>
      <PersistGate persistor={persistor}>
        {noLayout.includes(router.pathname) ? (
          <Component {...pageProps} />
        ) : (
          <Layout>
            <Component {...pageProps} />
          </Layout>
        )}
      </PersistGate>
    </Provider>
  );
};

export default MyApp;

Just typescripting the function, the translation worked again. I have no idea of why this happened and why it is fixed. LOL


Issues with saliency map for 1d input

I have a fully connected network with 1d input of size 35 and generates 1d output of size 50. I wanted to compute the saliency map for given inputs for this network. However, the output of the visualize_saliency(... ) function is just returning me an array of size 3 (instead for size 35 i.e. my input size).
#my model structure
M1.summary()

Layer (type)                 Output Shape              Param #

input_2 (InputLayer)         (None, 35)                0

dense_37 (Dense)             (None, 64)                2304

activation_25 (Activation)   (None, 64)                0

dense_38 (Dense)             (None, 100)               6500

activation_26 (Activation)   (None, 100)               0

dense_39 (Dense)             (None, 50)                5050

Total params: 13,854
Trainable params: 13,854
Non-trainable params: 0

layer_idx = utils.find_layer_idx(M1, 'dense_39')
sm1 = visualize_saliency(M1, layer_idx, seed_input=new_seed_input, filter_indices=None)  #new_seed_input is of shape (1,35)
print sm1

[0 0 127]

Not sure where is the problem. Any help would be really appreciated. Thanks!

I updated my keras-vis version to the latest version. The output of the visualize_saliency( ) is now just a single scalar value instead of the vector of size 35 (which is the size of my input vector). @keisen is this the expected outcome for the api call I made (above)

@keisen I don't think the problem has been solved yet.
With an input vector of size 35 the expected dimension of the saliency map is 35 as well. But currently, it is returning just a single scalar value.
On inspecting the visualize_saliency_with_losses( ) function I saw that the last two lines are
grads = np.max(grads, axis=channel_idx)     return utils.normalize(grads)[0]
before updating grads, its dimension was (1,35), which actually matches with my input vector dimension.

@subhashis , Thanks!
I created the PR #137 to fix this issue.
So please make sure of what there is no your problem in this PR.

PullRequest

https://github.com/raghakot/keras-vis/pull/137

Source

https://github.com/keisen/keras-vis
branch: issues/#135

Sorry, I forgot to mention one thing.

Usage

visualize_saliency_with_losses(input_tensor, losses, seed_input, keepdims=True)


Display property getting dropped in IE10

I am using Material UI and its buttons become invisible on IE10. This is because they have lost their inline-block display property. It is present in the styles property but disappears when prepareStyles is applied to it.
I think this is because the flexboxIE plugin has a similar loop to that addressed in other browsers in  #65: if I understand the code correctly, the properties variable has display in it so it is replaced, but altProperties has no entry for display so it is replaced with nothing.
(When I say IE10 I actually mean IE11/Edge in its IE10-emulation mode running on Windows 8.1.)

Hey @pdc. This has already been fixed as you can see here:
https://github.com/rofrischmann/inline-style-prefixer/blob/master/test/prefixer-test.js#L337
I assume material-ui did not update the prefixer yet. You might ask them to do :)

Thanks for the quick response! You're right, Material UI is still using 0.6.6...


Support for anti-join based reader support for Hive ACID tables in Spark

Currently, ACID reader is currently using Hive ORC Acid readers shaded to read the Hive ACID tables. We can definitely improve the performance if we move to native readers to read those tables. Especially in the case of Parquet, Spark’s native Parquet readers are optimized and we don't want to miss on that. Another reason is that we need to convert every row from Hive Structure to Internal Row which might add penalty too.
Following are the 2 important objectives for this exercise:
Performance: Figure out a performant way of using the native Spark readers.
Maintainability: Not make changes to Spark readers for Hive ACID. We would not like to make any changes to Spark readers or keep a fork of it which needs to be maintained later.
One of the solutions we are planning to evaluate is to use anti-join between base_files + delta files (let’s call it base relation) and on the delete_delta files (let’s call it delete relation). AntiJoin of base and delta relations on (rowId, bucket, transactionIds) can give us the result to read i.e.,
AnitJoin(base, delete)
However, Sort Merge Join can lead to extra shuffle that might cause a performance issue. If delete relation is more than the broadcast threshold then that can lead to SMJ. To ensure Broadcast to happen more frequently is to split the base and delete relations by bucket id and doing anti-join corresponding to the bucket Ids i.e.,
AntiJoin(base, delete) = Union(AntiJoin(base_bucket_1, delete_bucket_1), AntiJoin(base_bucket_2, delete_bucket_2), … AntiJoin(base_bucket_n, delete_bucket_n))
This way joins are getting split and making sure the broadcast joins come into play here.

Couple of issues here:

One of the issues specific to ORC is that the reader currently understands the ACID format. So if we  just do this:

spark.read.format("orc").load(".../warehouse/acidtbl/delta_0000002_0000002_0000/bucket_00000")
following exception is thrown in SchemaEvolution:
if (this.readerIncluded != null && this.readerIncluded.length + this.readerColumnOffset != this.readerSchema.getMaximumId() + 1) {
throw new IllegalArgumentException("Include vector the wrong length: " + this.readerSchema.toJson() + " with include length " + this.readerIncluded.length);
}
This means delta files are not even accessible to normal readers where it can read it like a normal ORC files with normal row ids.

What should be done when rowId has not been determined for base files yet ?


How can I see the cloud_result and edge_result in the joint inference experiment?

What happened:
when I execute "ffmpeg -re -i /data/video/video.mp4 -vcodec libx264 -f rtsp rtsp://localhost/video",that is to say the last step in the document, the ouputdir " /joint_inference/output" is empty? why
What you expected to happen:
What will it be like? Output picture or execute " ffplay rtsp://localhost/video", It can be recognized by video?
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Sedna Version
Kubeedge : v1.9.1
Kubernetes : v1.21.3
sedna : v0.4.3
```console
$ kubectl get -n sedna deploy gm -o jsonpath='{.spec.template.spec.containers[0].image}'
# paste output here
$ kubectl get -n sedna ds lc -o jsonpath='{.spec.template.spec.containers[0].image}'
paste output here

</details>

<details><summary>Kubernets Version</summary>

```console
$ kubectl version
# paste output here

KubeEdge Version
$ cloudcore --version
# paste output here

$ edgecore --version
# paste output here

CloudSide Environment:
Hardware configuration
$ lscpu
# paste output here

OS
$ cat /etc/os-release
# paste output here

Kernel
$ uname -a
# paste output here

Others

EdgeSide Environment:
Hardware configuration
$ lscpu
# paste output here

OS
$ cat /etc/os-release
# paste output here

Kernel
$ uname -a
# paste output here

Others

pod"edge-x4161" there is no events and no logs.
the "cloud-8tmpv" has no logs, but events:

It seems that both inference workers run errors, would  you mind providing some details?

似乎两个推理工作者都运行错误，您介意提供一些细节吗？
Thank you. The previous problem has been solved. Now, edge is okay, but the master has a problem:

[2022-03-23 12:41:05,321] base.py(79) [INFO] - Start sedna server over http://<IP_ADDRESS>:5000
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/usr/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.6/dist-packages/uvicorn/server.py", line 69, in run
return asyncio.get_event_loop().run_until_complete(self.serve(sockets=sockets))
File "/usr/lib/python3.6/asyncio/events.py", line 694, in get_event_loop
return get_event_loop_policy().get_event_loop()
File "/usr/lib/python3.6/asyncio/events.py", line 602, in get_event_loop
% threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'Thread-1'.

I use images from dockerhub:
docker pull kubeedge/sedna-example-joint-inference-helmet-detection-big:v0.4.0

Seems to have found the solution on #289 , and this issue should be closed.

看来您已经在#289上找到了解决方案，应该关闭此问题。
thank you very much


Error in generated PlantUML

Error found in diagram erd
ERROR
5
Syntax Error?
Some diagram description contains errors

The generated source is
@startuml

hide circle
skinparam linetype ortho

"**butane_migrations**" {
# ""name"": //""text"" <color:goldenrod>(PK) </color><color:DarkRed>(NN) </color> //
---
}

@enduml

Unfortunately not.
The table DDL for one of the tables, the one mentioned above, is
CREATE TABLE IF NOT EXISTS butane_migrations (
"name" TEXT NOT NULL PRIMARY KEY
);

Thanks @jayvdb
This is enough for reproduce. I will fix

I suspect the problem is that because there are no relationships between entities, plantuml doesnt detect the type of diagram, and fails.
The mermaid diagram shows each table separately.  i.e. disconnected.

I've added all the relationships, and the mermaid diagram looks well connected.  The plantuml is still failing to render.

The plantuml is still failing to render.

I've found at least one reason Plantuml has failed. It now required the "class" keyword.
Fixing...

@jayvdb could you try this fix?
https://github.com/kurotych/sqlant/pull/24/files#diff-d94002e7bd41ac4a55adfe026b3b0b387c251b5fe1d2857e9aa7cd58f0276212

I will release version 0.3 today

New version is released https://crates.io/crates/sqlant


Cron schedule pattern no longer supports pattern for year

The upstream pattern matching no longer recognizes year. Removing it from the example pattern in the README.

This is due to this issue: https://github.com/Hexagon/croner-rust/issues/2
I think the best approach is to add this feature to the croner library instead of removing the documentation here.
I acutally had plans to do that but time is always the stopper.

Good point!
Adding this little Part of documentation is indeed irrelevant.
Also there should be no Breaking Changes once croner adds support for years.
So upadting the documentation would indeed be a good thing.
Just wanted to point out that they is a way to Add support.

Hi @porkbrain
Thank you for the PR. I deeply appreciate it.


Why many example figures do not show up on the shapely user manual page

I am reading https://shapely.readthedocs.io/en/stable/manual.html.
For example, the linestrings figure shows up, but most others don't, e.g. in the linearrings section, only a link for downloading source code appears.
I wonder if it's a bug? If not, I would be interested in improving the doc.

I have been wondering the same. About a month ago it was showing fine and then the next day most figures were not displayed anymore.

Could be due to the build process, some images may not have been generated properly.
e.g. this figure exists
https://shapely.readthedocs.io/en/stable/_images/linestring.png
But those don't
https://shapely.readthedocs.io/en/stable/_images/linearring.png
https://shapely.readthedocs.io/en/stable/_images/multipolygon.png
The owner @sgillies  may have a better idea.

Thanks for pointing this out! The doc builds are indeed broken: https://readthedocs.org/projects/shapely/builds/. And it looks like the last "passed" builds were incomplete (missing images). We'll try to get this sorted out soon.

I've restored the builds and made "latest" the default. We won't fix the builds for the 1.6 branch, which will soon not be supported.