[Feature] Tremor migration

Description
Replace echarts with tremor
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

How Has This Been Tested?

[X] Existing unit tests
[X] Visual comparison with existing app

Checklist:

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have update the CHANGELOG
[X] New and existing unit tests pass locally with my changes

Hi @dmytro-tinybird,
There are some issues compared to the current UI that we need to adjust before moving forward. From the Vercel Preview:

There are some incorrect spacing between some modules.

Here we are defaulting to system fonts and it should be using Inter.

Some list values are using bold font weight and they shouldn't, and titles are using semi-bold and should be using regular.

Top Devices chart is using incorrect colors/shades

List items are not clickable urls

The top chart has some extra padding and flashes from time to time

There are some legends that should be hidden

There are other styling things that are not as designed. I think it looks ok to add borders to the modules, but let's make sure the styles are consistent with other elements like the dropdown.

Also I couldn't check all edge cases, but for example the No data is not using the correct design.

Thanks! Let me know if I can help better.

@kukukaka I believe @dmytro-tinybird has addressed all of your concerns

Hey, it looks way better. Good work!
@xavijam, @raqyuste  could we take a look at the code to merge?
Some minor comments from my side @dmytro-tinybird.

I think there are some issues here with the tr-h-full and the h-full that make the distance between the title and these charts is too big.

Is there a way to reduce the number of items/granularity/format in this cases on the first chart so it doesn't look so crowded?

Can we avoid showing those background lines in this specific chart?

taking a look! 👀

@raqyuste would you might taking another look to see if the changes have addressed your concerns 🙏 ?

The look and feel is a bit different, right?

@kukukaka since you're the original designer of the dashboard, are you ok with these changes?

The look and feel will be slightly different, but that is kinda the nature of why we are adopting Tremor, as we like Tremor's design; we're adopting it across all of our starter kit efforts & working closely with the Tremor project.
As we're happy with the code, I'm going to merge & we can iterate upon the project from there

The look and feel is a bit different, right?

Cards now have a border, charts have different colors, line width in the first chart, etc.
@kukukaka since you're the original designer of the dashboard, are you ok with these changes?

I was planning to do a last review this afternoon. I'll open it in a different issue.


Handle informative data between square brackets in calendar summaries

This patch allows to have summaries like [SALLT Triage] Sylvestre Ledru in calendars.

Coverage increased (+0.1%) to 24.986% when pulling 7bdb22883c226a466fc5a2dc78f0ce9a62f62c2c on calixteman:summary_cal into 110b191ec3ef4d54df6a9b0227f0ad46e15a2735 on mozilla:master.

What do you do when the format isn't found?

What do you do when the format isn't found?

Just get the summary at it is. If we cannot get a name in phonebook using the info we've then a mail is sent to the fallback to say "Hey we didn't find this guy in phonebook...". This case happened in real life, fallback pinged me and then he fixed his summaries.


feedback

the app is running fine. My transaction went quite fast according to my expectations. web animation, UI, UX is very comfortable to look at...can't wait to see the next development!!!😃 0x49e3560B295A61B4d1C2a86d1EA2aA2bf5d73613

@suneoyadi Thank you for your testing and we hope to continue delivering high quality features and improvements!


Finite variable width slider slides always fill the display area

Fixes #1334
I've added some logic to snap the right side of the last slide to the right side of the scrolling window.

This is nice @diegopamio! Please consider the case when there are few items in the carousel. I can see a bug in this case where the few items (in this case just 2) get aligned to the right instead of left as they are supposed to!
See GIF:

@cgadam done, now it doesn't snap to the right if the width of all the available images is less than the width of the container.

What is the status of this PR? @diegopamio

Yeah I agree with @precompiled! This needs to be resolved too :/

Will it be merged?

Will it be merged one day ? 🙏

I'm having little to nothing free time for this, If anyone can help on @precompiled request, or if we can do it separately, I can collaborate.

I've finally switched to swiper. Thanks !

@diegopamio, Hi! I faced the same problem that this PR solves, and wouldn't mind to finish your job. Could you add me to collaborators of the fork so I could add commits here?


Is this support 'deferred loading' ?

When using Flutter Web, all the translations go into main.dart.js, making this file very big. So the web app loads very slowly the first time user opens it. But most users will only use one (two at most) translations.
Is Slang support deferred loading? making each translation into separate  files, only loading them if needed

Flutter has this feature but it seems that we cannot check if this is loaded yet.
Only loadLibrary is not enough as all translation access is non-async so there needs to be a mechanism to fallback to the base translations.

We can just load the  and  together, (if target locale === base locale, then only need to load one locale file). If the user switches to another locale, just load that file.

yes, but what should String a = t.myTranslation return? This getter is not a future.

the < base locale > is always loaded, just use the < base locale >'s tranlation. after other tranlsation's is downloaded,  reload the correct translations. Is that ok?

Thinking about this again, I think that this is technically possible. But don't expect this feature soon as I don't have much time for this.

Added in 4.0.0-dev.1


Tabs

When doing the "Over 9000" tutorial on conditionals, I discovered that indenting the second line with spaces (or keeping on the same line in the first place) has no problems, but not indenting at all or indenting with tabs return the errors
[1 of 1] Compiling Main                ( Main.elm )
Parse error at (line 2, column 1):
unexpected "e"
expecting newline or spaces

and
[1 of 1] Compiling Main                ( Main.elm )
Parse error at (line 2, column 1):
unexpected "\t"
expecting newline or spaces

respectively.
On an unrelated note, the "'" (apostrophe) gets rendered as "'".

yeah, this i find confusing as well, especially since i'm in emacs elm-mode and it is doing my indenting for me, and it is inserting tabs. oy veh.

These are both working as intended, but certainly the error messages could use work!
I've created https://github.com/evancz/error-message-catalog/issues/14 and https://github.com/evancz/error-message-catalog/issues/15 in the Error Message Catalog repo to track these, so future versions of the compiler can better explain what's going on. Let's move further discussion there.
Thanks for reporting this!


Improve scheme browse page

#173
This now takes magicfoo.geojson as input -- the previous input files will not work. And the tooltips are formatted better.

Thanks for the review! Merging, then I'll update the email with inspectors with the new input file

Great, I'll do a live demo today that will benefit from this!


azd help improvements

Should we group the commands by task?

Yes!

@savannahostrowski As we discussed earlier, let's make the #663 issue an Epic and this issue a task within the epic (I'm not sure how to do that myself).

Moving this to November (later half of the month)

Update 10/25/2022

Begin work on this week of 11/14

New command azd config is available since release azure-dev-cli_0.4.0-beta.1. Please make sure you include azd config in your exploration.

Proposed --help templates I shared today on the demo.
General Help (azd --help)

Command Help (azd [command] --help)

Update 01/16/2022

Finalized designs for 12 different azd help experiences
Presented to team on azd Demo playback
Detailed feedback provided by @savannahostrowski, @gkulin, @ellismg and Crystal Barragan
Ready for implementation discussions (cc: @rajeshkamal5050 , @savannahostrowski)

Overview of new designs
Prototype featuring the proposed azd help and azd <command> --help designs can be found here. Use < and > arrows to toggle through pages.
Summary of changes and features

Overhauled the layout, hierarchy and visual design of both general and command specific help to be more scannable, and to align with the design language we are establishing for the rest of the CLI (consistency).
Commands regrouped to more accurately reflect the jobs a user can complete using the CLI.
Reworked individual descriptions for commands, flags and global flags to be more clear.
Reworked intro descriptions to be more succinct (introduced bullet point format).
Introduced an examples section for most commands to aid in understanding.
Introduced new convenience commands/flags: docs, --docs, upgrade. Needs team approval.

Links to individual help experiences:

azd help
azd up --help
azd down --help
azd init --help
azd provision --help
azd deploy --help
azd env --help
azd config --help
azd restore --help
azd pipeline --help
azd monitor --help
azd template --help

Any feedback on the design is still gladly accepted!

@rajeshkamal5050 This is ready for implementation in 0.7. Please let @Austinauth Austin know if anything else is needed!

@savannahostrowski @Austinauth

Some comments
•	Grouping description changes
•	Moved deploy into the 2nd bucket
•	Put monitor, test and release together
•	Moved login/logout onto the first bucket. For downloading/initializing and developing apps localy. We need authentication.

Setup, configure and develop your app
-- config
-- init
-- restore
-- template
-- login
-- logout
Manage azure resources and app deployments
-- deploy
-- down
-- env
-- infra
-- up
Monitor, test and release your app
-- monitor
-- pipeline
About, help and upgrade
-- docs
-- help
-- upgrade
-- version

@savannahostrowski are you good with Rajesh proposed tweaks? I don't have any issues.

@rajeshkamal5050 I spoke with @savannahostrowski regarding the suggested changes.
We're mostly good on them except:

Setup, configure and develop your app
Setup and configure are a little redundant, will just use configure for now if that's okay?

I should have the prototype updated by the time you read this message.

@Austinauth sounds good.


Cookie warning at top of page cannot be dismissed, is very large

Steps to reproduce

Navigate to https://blogs.windows.com/
Observe cookie warning at top of page

Impact

Warning pushes content on the page further below the fold, increasing difficultly in reading the page / finding the information I need
Generally looks broken, decreasing customer confidence in Microsoft

Screenshot

Cannot reproduce this morning, closed as fixed.


Let's Encrypt Plugin leftover cron job

Installed Let's Encrypt Plugin to tinker and only browsed through the different setup sequences including automation.
After removing plugin, found an enabled job to renew certificates still exists from System, Settings, Cron.  This particular job cannot be deleted regardless of how I try from the GUI.
While the job can be disabled, would like the ability to remove it completely.
OPNsense 19.1.4 amd64 nano

The plugin should take care of removal. Being able to remove from cron directly could leave the plugin to believe it still there (and not being able to add it again).


[Partners Website] Wrong copyright year in footer

I didn't find a Repo where I could do a PR for fixing this.
Therefor I do a Bug Report here:
https://partners.laravel.com has Copyright ©2011–2021 Laravel LLC in the footer.
It should probably be Copyright ©2011–2022 Laravel LLC

Thanks. Will get that fixed 👍


hour() executed error

Steps to reproduce the behavior (Required)

select hour('9999-03-31 24:00:00')

Expected behavior (Required)
NULL
Real behavior (Required)
0
StarRocks version (Required)
+------------------------+
| current_version()      |
+------------------------+
| QA_TEST_MASTER f6f6228 |
+------------------------+

This calculation is correct， we will trans '9999-03-31 24:00:00' to， 9999-03-31 00:00:00'，so it make correct


net: sockets: socketpair: fix socketpair coverity issues

I have no permissions to access the actual errors on coverity.com (error 401), but please let me know if this helps.
Fixes #25793
Fixes #25788
Fixes #25780
Fixes #25737
Fixes #25731
Fixes #25736
Fixes #25727
Fixes #25797

Should be good now. Does Coverity mention when a problem is fixed on GitHub? I'll keep an eye on it in any case.

@jukkar - should be good to go

@pfalcon, @jukkar, @tbursztyka, @carlescufi - should be good to go

Thanks! waiting for the reviewers above to approve

Some of the associations between changes and Coverity IDs don't make sense. Other comments need changes too; I think the ones that are optional note that.

Well, my primary attention is to the changes outside tests/ and samples/. Changes to those can be treated in more or less lax way, but for changes to the system functional code, would be nice to have clear and detailed commit messages.

Some of the associations between changes and Coverity IDs don't make sense. Other comments need changes too; I think the ones that are optional note that.

Well, my primary attention is to the changes outside tests/ and samples/. Changes to those can be treated in more or less lax way, but for changes to the system functional code, would be nice to have clear and detailed commit messages.

@pabigot, @pfalcon - I believe most of your concerns should be addressed. If there is anything else, please let me know.


Cheater Found Announcement Timer.

As much as I love the auto-announce feature, I do think it is a wee bit too fast. Some players have been quite vocal that they didn't care for the spammy messages. SO! I was wondering if there was some way for there to be a sort of slider to set the timings for when these messages went out? Without going right into the code and changing it myself. I'm not sure if I'm the only one who has had this issue, so here I am. Seems like a QOL sort of thing. Cheers!

Duplicate of #70 with a related pull of #187


Create backup weather API named Tomorrow

Made Tomorrow Weather API call and functionalities for use.

Also, doesn't look like the pre-commits applied. You could apply black manually by typing "black/src/methods/tomorrow_api.py" in the terminal. If not no worries, I might make another PR to join my weather api into the same script you made


Roll Flutter Engine from 58193a3b6ef1 to ed5a2fef08bc (4 revisions)

https://github.com/flutter/engine/compare/58193a3b6ef1...ed5a2fef08bc
2022-05-13<EMAIL_ADDRESS>Roll Skia from f6e31bf1dcfb to 69fecd6c2d85 (1 revision) (flutter/engine#33322)
2022-05-13<EMAIL_ADDRESS>Roll Skia from 1e43dce386c9 to f6e31bf1dcfb (6 revisions) (flutter/engine#33320)
2022-05-13<EMAIL_ADDRESS>[web] Migrate Flutter Web DOM usage to JS static interop - 12. (flutter/engine#33241)
2022-05-13<EMAIL_ADDRESS>Roll dart sdk to 7b24ff4d92e2d2136020fc5bedadfe7025861510 (flutter/engine#33309)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Closing to trigger a roll using the commit with the revert.

Commit queue failed; closing this roll.


Produce a valid rack response on interaction post error

The third element of a rack return value should respond to #each, but in the error scenario it was returning a plain string, rather than an array.
I was getting an error adding one of my interactions, but the error message I saw was:
RuntimeError: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

  <TITLE>Internal Server Error</TITLE>

Internal Server Error

    undefined method `each' for #<String:0x007f8e62ae5b58>

    <ADDRESS>
     WEBrick/1.3.1 (Ruby/2.1.5/2014-11-13) at
     localhost:3077
    </ADDRESS>

with this change, I now see:
RuntimeError: An interaction with same description ("PUT new entry") and
provider state ("an empty content register") but a different request
path, response status and response body has already been used. Please
use a different description or provider state.

which is much more helpful :-)
Also added a corresponding unit test

Thank you kindly!

Released 0.5.5.

:+1: great :-)


play-incident-master not showing up, inactive?

Hi,
The play-incident-master doesn't seem to be working - not showing up even on the list, unlike the other options which are showing in the list when listing the options inserting "/"
Thanks!

Hi,
The play-incident-master doesn't seem to be working - not showing up even on the list, unlike the other options which are showing in the list when listing the options inserting "/"
Thanks!

This is very much a project in alpha right now.
We're tracking it and working on it!

@simeononsecurity Thanks, just testing it out and reporting on anything that is not working, happy to contribute.

@simeononsecurity Thanks, just testing it out and reporting on anything that is not working, happy to contribute.

We're going to be updating it again tonight. Not sure if the fix for that issue will be in there.
But we'd love to have you contribute if you're capable. All our contributors communicate on this discord server if interested
https://discord.gg/62VDYJK2XU


GW-55: Develop landing image in events page

Refactored out the home landing image into a shared component
Created the events page
Created a landing image for events page
Add the footer in the events page

And rename landing-image folder under event page folder to components

And fyi, the develop branch isn't the same as the master branch. This is why I just want us to have one branch only for development.


Names in groups are black

I've tried to modify the css myself but I don't know enough. The names next to the phone number in groups is pure black color, unreadable against a dark background.

Hi!
Thanks for making this issue but I'm unable to reproduce it on my end. I went through groups, searched through all panes and found nothing like that. Could you upload a screenshot of it? Of course, mask/change the sensitive content.
Another thing worth knowing is the version of WhatsApp web you're running. The current version I have is 0.3.1846. You can find that information in settings > help.

https://paste.xinu.at/lHBMA/ here's a screenshot, you can see the last numbers of the phone number in appropriate color, and then the guy's name "Marce" being unreadable.
Should point out that this only happens with non-contacts: people who are my contacts instead show up with their names that I've manually inputted, with the color that the phone number would usually show up; the unreadable names belong to people in the group who are not in my contacts.
Version 0.3.1846, same as yours.

Same version here: 0.3.1846 With the same issue:
I just gotta stress that we're talking about names of people in groups who are NOT contacts of ours, their names are their whatsapp handlers, this is what's showing in black.
Normal contact names show just fine.
My screenshot: https://i.imgur.com/JhyzD1y.png (zoom in to see the black contact name, circled in green)

._3Ye_R._1wjpf._1OmDL here
Good think you told me about it @vednoc because @indeedwatson was extremely unclear with his issue on my theme.

@RaitaroH Well forgive me, most of the people in the group are not in my contacts, it took me a while to even notice that added contacts show up fine.


Add methods to apply helper functions to Experiment

So far the data normalization and transformation functions are applied to DataFrame objects and should be applicable to Experiment objects as well. This includes logtransform, normtransform and decorrelate. The description should be updated accordingly, the feature names should be kept and the selectedFeatures should stay consistent.

The existing helper functions can all be applied on Experiment objects as of<PHONE_NUMBER>213c7690237503f10e73bf0c9389ed


Which version supports local filesystem as store + build support

Hello, I am working on single node installation and I would like to build from source and use local filesystem as store. I managed to build and run the database but apparently the file storage engine is no longer supported.
So my question is - which version should I use in this case?
I also tried building what is in branches v4dev and v3 as it seems like there is still the local filesystem support, but I was unable to build. There are some package dependencies I don't have, and I am not sure, how to systematically obtain them (namely for example go-bindata-assetfs - is there a way how to systematically obtain them instead of manual resolution?)
Thanks a lot for help

Even for a single node installation, we now recommend ceph as it provides a robust way to spread data across multiple hard drives with redundancy.
If you are looking for something easier than that, take a look at https://github.com/BTrDB/smartgridstore/tree/master/devmachine which is a set of scripts for running BTrDB on a single machine easily. It uses ceph still, but backed by a directory of files. By default the environment file uses ephemeral storage so that it runs on Mac, but if you set that to false, the data should persist across container restarts.
There have been so many features added to v4 that I would not recommend using v3 anymore, but if you do want to use v3 let me know and I can go and make sure all the dependencies it uses reference existing repositories. I noticed something bad happened to go-bindata-assetfs at one point so I would have to find a replacement.

Thanks for suggestions! It seems I will try to setup Ceph after all and use
the most recent version.
You mentioned that a big set of features have been added since the v3. I am
particularly interested in the time partitionend tree concept you are
using. Are there any major changes in it, the TS data abstraction or the
underlying data storage logic which have been added since publishing the
usenix paper and thus are not mentioned in it please?


Application does not start on Windows 10 pro 64 bits

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
When running the application on Windows 10 Pro 64 bits I get the following behavior, a prompt window opens for a few seconds, and then it closes, as shown in the video below
https://github.com/iced-rs/iced/assets/14854891/ea883e0c-ec51-4670-85cc-d0e5b2edecf3
My development environment

Compiled using cargo build --release --target x86_64-pc-windows-gnu
My Cargo.toml
[package]
name = "costv"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
iced = { version = "0.12.1", features = ["lazy"] }
iced_core = "0.12.3"

[profile.release]
strip = true

What is the expected behavior?
This is the expected behavior

Version
crates.io release
Operating System
Windows
Do you have any log output?
No response

Could you run the application with the RUST_LOG=debug environment variable set and copy/paste the logs here? Would help us know what's going on.


Analytics URL in Publisher Portal needs to change

Description:
It seems the analytics icon which is shown below navigates the user to the old analytics portal URL(https://analytics.choreo.dev/setup).

This needs to change to the Insights page of the Choreo Console(https://console.choreo.dev/insights)
Steps to reproduce:
As shown in the above screenshot
Affected Product Version:
APIM 4.0
APIM 4.x

With the recent changes in Choreo end, it seems the url (https://console.choreo.dev/insights) will not be supported anymore. Hence we can point to the URL to the Choreo console homepage (https://console.choreo.dev)

Reopening this issue as we still need to fix it for APIM 4.0.

@ashera96 we have done further improvements from Choreo end and now users can directly navigate to the insights page with console.choreo.dev/insights URL. Therefore can we also update the fix with this URL please.

Reopening again as we still need to fix this for APIM 4.0.

closing since this is fixed in master.


Management of non-package registry dependencies

Summary
Most of this projects dependencies are explicitly tracked[^1], either through the package*.json files or GitHub workflow files. However, not all dependencies are.
Not having dependency versions tracked accurately in version control can have negative consequence, ranging from contributor accessibility to reproducibility issues to security concerns.
This issue aims to list, categorize, and where possible find solutions (or more likely compromises) to the negative consequences of not having dependency versions explicitly tracked.

Note: Feel free to comment on this issue if you think this list is incomplete or if you have any suggestions for improvements.

List

[x] act is a system dependency with no explicit version specified.

Impacts: Minor, unless an old version or new major version is used act will probably work just fine.
Solutions: Defining a minimum version could be helpful but is not known at the moment.
Resolution: Not considered a problem at the moment.

[ ] CI workflows (GitHub Actions) use -latest images

Impacts: Workflows might have different results tomorrow compared to today due to a new image being used, for example due to changes in system dependencies.
Solutions: Don't use -latest images.
Resolution: #420

[ ] CodeQL packs: see #195
[x] Docker is a system dependency with no explicit version specified.

Impacts: Minor, unless an old version or new major version is used Docker will probably work just fine.
Solutions: Defining a minimum version could be helpful but is not known at the moment.
Resolution: Not considered a problem at the moment.

[ ] EditorConfig is a system dependency with no explicit version specified.

Impacts: Minor, unless an old version or new major version is used Docker will probably work just fine. Also, it's impacts are not automatically/continuously enforced.
Solutions: Defining a minimum version could be helpful but is not known at the moment. It's impacts could be automatically enforced.
Resolution: Consider automatically enforcing it's impact.

[x] git is a system dependency with no explicit version specified.

Impacts: Minor, unless an old version or new major version is used Docker will probably work just fine.
Solutions: Defining a minimum version could be helpful but is not known at the moment.
Resolution: Not considered a problem at the moment.

[ ] hadolint is pinned but not kept up-to-date automatically. Plus, the version used is hard to parse for humans.

Impacts: This project is likely to stay on an outdated version and thus not get the full benefits of the tool.
Solutions: Find a way to keep it up-to-date.
Resolution: none yet

[ ] ShellCheck is a system dependency with no explicit version specified.

Impacts: Linting with ShellCheck might find violations locally due to a different version being used.
Solutions: Specify what version is used and find a way to keep it up-to-date.
Resolution: none yet

Considerations
Not having a version specified may result in non-reproducibility. This may manifest itself in a couple different ways, for example through the "it works on my machine" scenario.
On the flip-side of not having a version specified is that specifying an exact version might lead to the dependency not being kept up-to-date and missing out on beneficial new features. If releases are infrequent this might be manageable, but otherwise automation (like Dependabot for npm) would be necessary.
For some dependencies, specifying a minimum version is fine. Examples include git or Docker. This is because these tools are generally backwards compatible and are unlikely to "complaint" about something that an older version was okay with.
For other dependencies, specifying a minimum version isn't fine because it's output might meaningfully change in newer version. Examples include static analysis tools. This is because a new version of a static analysis tool might be aware of a new problem and start complaining about it. While it's good that it complaints, it's not ideal that it's output changes without anything in this project having changed. Ideally, these kinds of tools are pinned (so at any point in time their results can be reproduced) and kept up-to-date through VCS-tracked version bumps (so we benefit from new features).[^2]
Definitions

System level dependency: a dependency that must be installed by the user outside the scope of the repository. Example, git.

[^1]: I'm considering the devcontainer configuration out of scope for this issue.
[^2]: Note that there's also tools whose output naturally changes over time, for example those that audit for known vulnerabilities. These are considered out of scope for this issue.

If #422 is merged, actionlint should be added to the list.


Specify that size property is in bytes

It's not clear from the documentation that size is in bytes, since it's only described as "an integer".

Currently failing because travisci is not configured correctly, it seems. See https://github.com/github/git-lfs/pull/181.

Nice catch, thanks for the contribution!


Keep timestamps from original stream

Hello!
I try to work on live streams and provide HA setup. Input is HLS/RTMP (currently HLS, because it's much easier for me).
Input config:
inputs:
  - name: https://host/hawe/test/playlist.m3u8
    media_type: video
    extra_input_args: -copyts

  - name: https://host/hawe/test/playlist.m3u8
    media_type: audio
    extra_input_args: -copyts

Pipeline config: pipeline_live_config.yaml
I've tried to add -copyts in multiple places in transcoder_node.py, it gets passed to ffmpeg, but does not work. I suspect timestamps get reset because of any of the other flags.
My goal is to run streamer on two different hosts with $Time$ in segment_template and be able to automatically failover between them. I already found, tried and have working synchronized keyframe cutting points, so that's no problem.

I tried to directly run packager (without my keyframe synchronizing code applied) and ffmpeg, but resulting streams result in decode error while playing :( With shaka-streamer everything works good, so for now I'm trying to go easier way.

Changing container to mpegts probably fixed one part of the issue (but caused new ones). Is it known problem with ffmpeg that it is ignoring copyts while outputting mp4 fragments?

I'm not planning to support this myself, but PRs are still welcome if you want to propose something.


Why is Gain and Whitebalance set to manual for software trigger?

In the example code that describes how to use the software trigger function the automatic gain and automatic whitebalance is set to false. The explanation seems to be that because the timing of image recording can change depending on the automatic function and therefore the trigger timing can be unexpected?
I understand that this is the case for auto exposure. But the other functions (like gain or whitebalance) are applied in the post-processing after the image has been recorded, so it should not take any effect on the actual image recording. So why are automatic gain and whitebalance set to false?
Moreover how does Highlight Reduction work? If automatic exposure is disabled is this done only through the gain in the postprocessing? What does Highligh Reduction actually do or where can I read about it?

Hello
if the automatics run, then they examine an image an set the values for the next image. If the light environment changes between the current and next image, then you may get wrong exposed images.
If the white balance automatic is done in software, as for the USB 2.0 , 23U, 23G camera series, then the image is indeed processed directly and you can use that with trigger.
If the white balance is done in hardware, then the amplifiers on the sensor are configured, so the next image is using these values.
However, if your trigger frequency not too low, then you can use automatics.
Stefan


Feature/49 add box shadow

Related Issues

https://github.com/lukepighetti/salomon_bottom_bar/issues/49

Context
This PR adds both SalomonItemDecoration as a global Decoration for each selected and unselected Items and also add boxShadow overrides for each item, so that users can control globally as seperatly the boxShadow.
I decided to create a controlled DataClass SalomonItemDecoration instead of Flutter's Decoration so users can't misuse the supported Decorations.
Example:
Global:
bottomNavigationBar: SalomonBottomBar(
          itemDecoration: SalomonItemDecoration(
            selectedBoxShadow: [
              BoxShadow(
                color: Colors.blue.withOpacity(.5),
                blurRadius: 25,
              ),
            ],
          ),
          ...

In each item:
items: [
            /// Home
            SalomonBottomBarItem(
              icon: Icon(Icons.home),
              title: Text("Home"),
              selectedColor: Colors.purple,
              selectedBoxShadow: [
                BoxShadow(
                  color: Colors.red.withOpacity(1),
                  blurRadius: 20,
                ),
              ],
            ),
          ...

@lukepighetti @imaNNeo please review this if you got time.

@lukepighetti


Added Univerdad de Málaga

@jujosa09 I am sorry, the domain uma.es is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


About Animation Character Dance

What a wonderful work!
I would like to ask if it is possible to change the subject to anime characters, and then use the driving video of real person dancing to make anime characters dance?
Thank you and look forward to your reply

Hi, @zcdliuwei, if you have the skeleton of the given character and the real person, and fine-tune the TS-Net on that character, I think it is possible.

Thank you for your reply
How to obtain the skeleton of an animation character? All I have seen are human skeleton extraction, but the extraction effect on animation characters is poor. Is there any reference material that can be recommended in this regard
In addition, we look forward to your training and fine-tuning code, as well as the pre training model
thanks again

Hi, @zcdliuwei, I just google it and find this WACV'22 paper may be related to your goal, Transfer Learning for Pose Estimation of Illustrated Characters.
Yeah, I have been working on the demo recently. Hopefully, I can release it next month.
Bests
Haomiao Ni

Thank you very much for your reply
I will take a look at this article and try to use your code to fine-tune animation characters！


amazon:effect Temp Fix for Translate Bug

When text contains amazon:effect tags, the AWS Translate service has a known bug that can cause it to mistranslate. This is a temp fix till the service is patched.

AWS translate team have fixed the bug so this can be closed


Critical Testing Instability | Dask Version

The first commit on this branch removes white space from the README.md: a no change change
this cascades a chain of CI testing failure ERRORs, of the form:
  File "/home/travis/miniconda/envs/test-environment/lib/python2.7/site-packages/Iris-2.0a0-py2.7-linux-x86_64.egg/iris/cube.py", line 2130, in __getitem__
    cube_data, keys)
  File "/home/travis/miniconda/envs/test-environment/lib/python2.7/site-packages/Iris-2.0a0-py2.7-linux-x86_64.egg/iris/util.py", line 690, in _slice_data_with_keys
    data = data[this_slice]
  File "/home/travis/miniconda/envs/test-environment/lib/python2.7/site-packages/dask/array/core.py", line 1222, in __getitem__
    index2 = normalize_index(index, self.shape)
  File "/home/travis/miniconda/envs/test-environment/lib/python2.7/site-packages/dask/array/slicing.py", line 762, in normalize_index
    raise IndexError("Too many indices for array")
IndexError: Too many indices for array

This does has not appeared on the last run of master testing, which was last run ~28 days prior to this run
This previous run was using dask 0.15.2
https://travis-ci.org/SciTools/iris/jobs/270360216#L1266
This run is using dask 0.15.3
I can reproduce this failure locally using dask 0.15.3
It is not clear to me that this minor version change is the trigger for the failure mode, it is just a potential clue
This is a blocker for incoming Pull Requests, and hence I consider it a significant and time critical issue

It appears this problem is introduced in other changes (i.e. subsequent to the "masked_array" PR) wrapped up in the 0.15.3 release.
However, it also seems to have been fixed in a subsequent commit (i.e. since 0.15.3 was cut).
It's the one-line code change here : https://github.com/dask/dask/pull/2719/files#diff-e37700c40af1928a965532126ff42d1eL754
I haven't yet checked what other effects the newer 0.15.3 release might have on the "dask_mask_array" feature branch.
Of course, if you are intending anything specifically dask-related, you need to be prepared for the ground to shift radically (again!) when we merge "dask_mask_array".
Hopefully, that will be sometime in the next 2-3 weeks.

@pp-mo thank you for the feedback
given that the bug looks like it might be fixed upstream, would you recommend pinning to dask 15.2 temporarily to enable testing to run, then adopting new dask once it is in a release?

@marqh thanks for pushing this.
We are going to be tidying up the remaining effort for Iris 2 over the next 2 weeks,
so this will need resolving.
In the meantime, I see that the Dask people have now cut a 0.15.4, so that probably fixes the problem (no need to pin). https://github.com/dask/dask/pull/2751
It's on conda-forge already, anyway : https://github.com/conda-forge/feedstocks/commit/b137940c6c73af794e8f5dafed4462a9538b77e3
Can you just give this a poke + just see if it now works ?
Of course, that might also introduce some other problem ..
It does seem they are moving rather quickly just now, though they seem to be mostly localised changes.
Also in the meantime, amusingly it seems you need to submit a CLA (!!)
( @pelson added a test hook a few weeks back to check all PR authors have a CLA in place )

@pp-mo  @marqh One of the Python 3.5 builds is erroring for an apparently different reason

I think it's this issue: https://github.com/cython/cython/issues/1880. I think what's happened is that netCDF4 has been compiled against Python >=3.5.2, which has the symbol _PyThreadState_UncheckedGet but our Travis build that's failing is running with Python 3.5.1, which doesn't define that symbol. The other 3.5 tests are using Python 3.5.4, probably because some package not specified in minimal-conda-requirements.txt is specifying that as a minimum.

#2774 recently merged ought to fix this.
@marqh can you please try rebasing this against the latest master ?
That is, make this into a real PR, or post the actual changes you are trying to move forward.

@marqh can you please try rebasing this against the latest master ?
That is, make this into a real PR, or post the actual changes you are trying to move forward.

@pp-mo this is not a real PR, it is a demonstration that a null PR failed testing
if this is no longer the case, I will close this PR (or you can)
looking at
https://github.com/SciTools/iris/pulls
at 12:26Z then no PRs are passing tests, so I'll hold off closing until i see tests passing.  If you see this and want to close this PR, you are welcome to

this is not a real PR, it is a demonstration that a null PR failed testing

Ok, I thought that must be what is meant.

looking at https://github.com/SciTools/iris/pulls at 12:26Z then no PRs are passing tests, so I'll hold off closing until i see tests passing

In that case I think it's no different from having all tests pass on the master commit d442b4, got from merging #2774
... which we do have, so I'll close this.


reorder of rows using drag and drop are breaking in latest version

Below doesnot work:
onDragStart={(e) => {
console.log("onDragStart");
DrageState.row = props.data.tableData.id;
}}
onDragEnter={(e) => {
e.preventDefault();
if (props.data.tableData.id !== DrageState.row) {
DrageState.dropIndex = props.data.tableData.id;
}
}}
onDragEnd={(e) => {
console.log(onDragEnd);
if (DrageState.dropIndex !== -1) {
this.reOrderRow(DrageState.row, DrageState.dropIndex);
}
DrageState.row = -1;
DrageState.dropIndex = -1;
}}
throws error
data-manager.js:358 Uncaught TypeError: Cannot read properties of undefined (reading 'id')
at data-manager.js:358
at Array.map ()
at DataManager.setData (data-manager.js:357)
at MaterialTable.setDataManagerFields (material-table.js:712)
at MaterialTable.componentDidUpdate (material-table.js:752)
at commitLifeCycles (react-dom.development.js:20684)
at commitLayoutEffects (react-dom.development.js:23426)
at HTMLUnknownElement.callCallback (react-dom.development.js:3945)
at Object.invokeGuardedCallbackDev (react-dom.development.js:3994)
at invokeGuardedCallback (react-dom.development.js:4056)
at commitRootImpl (react-dom.development.js:23151)
at unstable_runWithPriority (scheduler.development.js:468)
at runWithPriority$1 (react-dom.development.js:11276)
at commitRoot (react-dom.development.js:22990)
at performSyncWorkOnRoot (react-dom.development.js:22329)
at react-dom.development.js:11327
at unstable_runWithPriority (scheduler.development.js:468)
at runWithPriority$1 (react-dom.development.js:11276)
at flushSyncCallbackQueueImpl (react-dom.development.js:11322)
at flushSyncCallbackQueue (react-dom.development.js:11309)
at discreteUpdates$1 (react-dom.development.js:22420)
at discreteUpdates (react-dom.development.js:3756)
Help to get it work

Is this still a problem with the latest version?

Is this still a problem with the latest version?

yes still no fix for the mentioned issue
below are my versions
"@material-table/core": "^0.2.9",
"@mui/material": "^5.2.3",

It seems like you are mixing mui v4 and mui v5, Also I cannot reproduce the error for me. Can you check the sandbox and set the correct dependency?

Code Sandbox throws  error for muiv5 if using material table... its
mandatory to use material core v4 dependency...
But my original project has no depenendency on material ui core
On Fri, Dec 31, 2021, 11:40 PM Domino987 @.***> wrote:

It seems like you are mixing mui v4 and mui v5, Also I cannot reproduce
the error for me. Can you check the sandbox and set the correct dependency?
—
Reply to this email directly, view it on GitHub
https://github.com/material-table-core/core/issues/431#issuecomment-1003429468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKW26M35PT7UMHTKCHKZTTUTXWYPANCNFSM5J23B7QA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Code Sandbox throws  error for muiv5 if using material table... its
mandatory to use material core v4 dependency...
But my original project has no depenendency on material ui core
On Fri, Dec 31, 2021, 11:40 PM Domino987 @.***> wrote:

It seems like you are mixing mui v4 and mui v5, Also I cannot reproduce
the error for me. Can you check the sandbox and set the correct dependency?
—
Reply to this email directly, view it on GitHub
https://github.com/material-table-core/core/issues/431#issuecomment-1003429468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKW26M35PT7UMHTKCHKZTTUTXWYPANCNFSM5J23B7QA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

No you dontactually: https://material-table-core.com/docs/material-ui-v5.
Just install the next version aka 0.2.X

No you dontactually: https://material-table-core.com/docs/material-ui-v5.
Just install the next version aka 0.2.X

No you dont actually: https://material-table-core.com/docs/material-ui-v5. Just install the next version aka 0.2.X

please find below screenshot i have removed dependency

Below dependencies added in codeSandBox

Yes as I said above, if you use the Mui v5 version, you need to use the next version of material table. Which is currently 0.2.11. so if you select this version instead of 4.x.x, it should only be Mui v5.

Yes as I said above, if you use the Mui v5 version, you need to use the next version of material table. Which is currently 0.2.11. so if you select this version instead of 4.x.x, it should only be Mui v5.

Yes , i have changed it in CodeSandbox as mentioned,
"dependencies": {
"@emotion/react": "11.7.1",
"@emotion/styled": "11.6.0",
"@material-table/core": "0.2.11",
"@mui/icons-material": "5.2.5",
"@mui/material": "5.2.5",
"@mui/styles": "5.2.3",
}
But unable to reorder rows using the code , it was working in earlier versions
Please check out the link [https://codesandbox.io/s/confident-austin-poz9z?file=/src/CustomTable.js]

I cannot reproduce the error, It just does not do anything when reordering. Would you mind creating a video or a step by step guide to cause the error in the sandbox?

I cannot reproduce the error, It just does not do anything when reordering. Would you mind creating a video or a step-by-step guide to cause the error in the sandbox?

Re-order is not working in the below Sandbox link:
Uploading
screen-capture (1) (4).mp4…

I cannot reproduce the error, It just does not do anything when reordering. Would you mind creating a video or a step-by-step guide to cause the error in the sandbox?

Re-order is not working in the below Sandbox link: https://codesandbox.io/s/confident-austin-poz9z?file=/src/CustomTable.js
Uploading screen-capture (1) (4).mp4…

@Domino987  any update on this?

No not yet because this is such a complex demo with manipulating the internals of the table itself making it super hard to track what the error might be.
Can you pinpoint the problem or create a minimal demo where the error might be apparent?


Add laws for this type class

Maybe it's a good idea to add some laws so people can ensure their implementation somehow. I can think only of something like this:
liftBase . liftBase ≡ liftBase

But this might not even typecheck...

The obvious laws are the monad morphism ones required by MonadTrans:
liftBase . pure = pure
liftBase m >>= liftBase . f = liftBase (m >>= f)

With #19, I think your proposed law gets more useful.


flake: bump stable to 24.11

move stable from 24.05 to 24.11

Hurray! 24.11 has been released. https://nixos.org/blog/announcements/2024/nixos-2411/

I'm currently running COSMIC on 24.11 and it seems to be fine, no regressions from 24.05 that I can see

This still needs lockfile updates as requested, but I'll just manually push to this branch so that it can be ready for merge

CI broke so I spent the evening building and uploading closures to cachix, woo. All done now so I'm merging


Modified the phone number pattern to match right pattern for bn/BD loc…

Modified the phone number pattern to match up the right pattern for bn/BD .

added static::numerify()

No news for too long, closing.


feat: upgrading to Laminas Soap

I think we need to use Laminas because Zend is not going continuing.

@Gildus Thank you!

@Gildus Why is the composer.json file deleted in your PR ?!!


[identity] add support for app service 2019

Packages impacted by this PR
@azure/identity
Issues associated with this PR
Fixes https://github.com/Azure/azure-sdk-for-js/issues/20466
Describe the problem that is addressed by this PR

Adding back support for app service 2019

Design description -
https://github.com/Azure/azure-sdk-for-js/issues/20466#issuecomment-1048209305
Checklists

[x] Added impacted package name to the issue description
[ ] Added a changelog (if necessary)
[x] Add a test case ??

The tests are failing due to some error from dev-tools. Still investigating this.

Looks good from the Identity perspective.

@KarishmaGhiya when you add the MSI in the MSI list, add it before the 2017 entry. Then, you can mark this PR as fixed: https://github.com/Azure/azure-sdk-for-js/issues/20954


Feature request: "propagate_intra_route_tables_vgw"

I am utilizing intra_subnets as a part of a use-case where I am exposing AWS services to a private (non-internet connected) network connected to AWS via a virtual gateway interface (by way of direct connect private vif) and would like to be able to optionally propagate learned routes to intra_subnets.
Following from how this is done for private subnets, I think the following would work (assuming additional variable added):
resource "aws_vpn_gateway_route_propagation" "intra" {
  count = "${var.create_vpc && var.propagate_intra_route_tables_vgw && (var.enable_vpn_gateway || var.vpn_gateway_id != "") ? length(var.intra_subnets) : 0}"

  route_table_id = "${element(aws_route_table.intra.*.id, count.index)}"
  vpn_gateway_id = "${element(concat(aws_vpn_gateway.this.*.id, aws_vpn_gateway_attachment.this.*.vpn_gateway_id), count.index)}"
}

Put together a more complete commit in a branch here https://github.com/paullschock/terraform-aws-vpc/commit/2da6b56cc7e0e367c4775f6ea1cf62dc3afaf6d4

@antonbabenko , does this make sense to you given the "closed" nature of the intra subnets? i can open a PR if you are ok with it.

Yes, I think this is a valid case even for "closed" subnets as intra.
Please open PR only to the master branch. We need to stop adding new features for Terraform 0.11 users.

Will do
On Tue, Mar 24, 2020, 20:18 Anton Babenko<EMAIL_ADDRESS>wrote:

Yes, I think this is a valid case even for "closed" subnets as intra.
Please open PR only to the master branch. We need to stop adding new
features for Terraform 0.11 users.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/terraform-aws-modules/terraform-aws-vpc/issues/352#issuecomment-603424603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIA2W7TTUBC4GYTKSBNCOUTRJD2QJANCNFSM4JJRAHJA
.

v2.32.0 of this module has been just released.


Update README

The README hasn't been updated for 3 years, we need to review it and update it if needed.

The SDK requires now Python 3.8+, point this out in the README.


merge zoom and zoomgov labels

The packages installed by "zoom" and "zoomgov" are identical.
% md5 zoomgov.pkg
MD5 (zoomgov.pkg) = ec165a9501b71b446f5fe401507fe2e4
% md5 zoom.pkg
MD5 (zoom.pkg) = ec165a9501b71b446f5fe401507fe2e4

The installer may be the same, but if your organization falls under regulations to use Zoom for Government, you'll always want to use the vendor provided URL for the gov client. It can be as simple as the zoomgov label is ensuring the CDN used falls under applicable federal regulations. (Meets certain operational restrictions, is only operational in certain countries, etc.) I don't think these labels should be merged.

Agreed, our gov clients need to know they're using GovCloud, if in the future Zoom updates the zoomgov.pkg file and does treat it differently and we're still installing zoom.pkg for them they fall out of compliance.

Ah! Excellent points. I will now stfu and figure out how to actually solve my disambiguation problem, rather than hoping it will be fixed for me.
Rats.

@.***
Charles Mangin | Head Mac Nerd | N-able
email<EMAIL_ADDRESS>| website : www.n-able.comhttp://www.n-able.com/
http://www.n-able.com/
http://www.n-able.com/

From: isaacatmann @.>
Sent: Wednesday, February 9, 2022 11:55:20 AM
To: Installomator/Installomator @.>
Cc: Mangin, Charles @.>; Author @.>
Subject: Re: [Installomator/Installomator] merge zoom and zoomgov labels (Issue #411)
[EXTERNAL] This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Agreed, our gov clients need to know they're using GovCloud, if in the future Zoom updates the zoomgov.pkg file and does treat it differently and we're still installing zoom.pkg for them they fall out of compliance.
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FInstallomator%2FInstallomator%2Fissues%2F411%23issuecomment-1033978693&data=04|01|charles.mangin%40n-able.com|cb2857b72bb4447eff2b08d9ebecf624|6324f4fb86ee4493ba16c819a916b487|1|0|637800225262929526|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=jUmhxlh8yd8W98%2BII7qPaXvP31tHlsx2iuu01csSGV4%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW2XEMQ4ITQJWEPLZKISADLU2KL7RANCNFSM5N4DUZMA&data=04|01|charles.mangin%40n-able.com|cb2857b72bb4447eff2b08d9ebecf624|6324f4fb86ee4493ba16c819a916b487|1|0|637800225262929526|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=uEfHbwCM5k0cWAxXPmGQUAjEZ%2Fa28MEj5A4gfxBmq14%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|charles.mangin%40n-able.com|cb2857b72bb4447eff2b08d9ebecf624|6324f4fb86ee4493ba16c819a916b487|1|0|637800225262929526|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=eBqd8RtKJJ6ZoyYy6VZCn56Tr7HTxpv2USdFDxB8DXU%3D&reserved=0 or Androidhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|charles.mangin%40n-able.com|cb2857b72bb4447eff2b08d9ebecf624|6324f4fb86ee4493ba16c819a916b487|1|0|637800225262929526|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=ibKvkDLq3JpJsVcGikxyYLiQuuH2O7YqUcFh8KQEDws%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>


Bricked keyboard / Left half will not mount

Yesterday the Adv360Pro randomly disconnected and when I opened the bluetooth settings of my computer to ‘connect’ the device it went into a very common loop of ‘connecting’ and then failing which calls for flashing and re-adding firmwarez
When I connect the left half of the Adv360Pro to my Macbook and either key press Mod+Bootloader or double press the physical reset button with the 3 LEDs and backlights flash, however, nothing mounts. When I repeat this step with the right half it immediately mounts and the LEDs turn green.
This is very concerning as it’s bricked the keyboard. Any advice on how to get this board working again would be wonderful, thank you

If the keyboard is not booting you need to use the double press reset method to get into bootloader on the affected side. The mod key method only works when the side is booting into ZMK

Unfortunately i've tried rotating the cable as well as different cables but nothing mounts.

Sorry to hear that!
It's possible there is a hardware failure on the left side. Please submit a trouble ticket and we'll issue an RMA for a repair/replacement assuming we can't solve the problem remotely.
https://kinesis-ergo.com/support/contact-a-technician/


Added timeouts (delays) on serial port and mounting point

Description

Added timeouts (delays) on serial port and mounting point accesses in host_test and copy plugins to prevent serial/disk I/O errors when device remounts USB iface of interface chip.
Also some Freedom boards (KL25Z, KL46Z) can cause re-mounting issues when (experimental) parallel test execution is turn on option --parallel.
This implementation hopefully solves both problems.

Rationale
There was a problem with U-BLOX interface chip which is re-mounting and causing serial / mount point I/O when test suite is executed.
See here: http://developer.mbed.org/questions/6743/singletestpy-need-wait-between-end-of-co
Fix is adding pooling for serial port and mount point so we are only flashing and reading from serial when both are available (when accessing).
Usage:
$ singletest.py -i test_spec.json -M muts_all.json  --global-loops 3 -W

or (only when mbed-ls is installed)
$ singletest.py --auto --global-loops 3 -W

Note: Flags --global-loops 3 -W added to repeat failing tests up to 3 times.
Results:
Test summary:
+---------+------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result  | Target     | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK      | UBLOX_C027 | ARM       | DTCT_1      | Simple detect test                    |        0.58        |       10      |  1/1  |
| OK      | UBLOX_C027 | ARM       | EXAMPLE_1   | /dev/null                             |        3.5         |       20      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_10     | Hello World                           |        0.4         |       5       |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_11     | Ticker Int                            |       11.41        |       15      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_12     | C++                                   |        1.43        |       10      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_16     | RTC                                   |        4.62        |       20      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_2      | stdio                                 |        0.84        |       20      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_23     | Ticker Int us                         |       11.42        |       15      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_24     | Timeout Int us                        |       11.45        |       15      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_25     | Time us                               |       11.61        |       15      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_26     | Integer constant division             |        1.43        |       20      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_34     | Ticker Two callbacks                  |       11.43        |       15      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_A1     | Basic                                 |        1.41        |       20      |  1/1  |
| OK      | UBLOX_C027 | ARM       | MBED_A21    | Call function before main (mbed_main) |        1.48        |       20      |  1/1  |
| TIMEOUT | UBLOX_C027 | ARM       | MBED_A9     | Serial Echo at 115200                 |       40.41        |       20      |  0/3  |
| OK      | UBLOX_C027 | ARM       | MBED_BUSOUT | BusOut                                |        2.36        |       15      |  1/1  |
+---------+------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
Result: 15 OK / 1 TIMEOUT

Completed in 283.15 sec

(Experimental) Parallel tests for KL25Z and KL46Z fix:
This pull request should also fix parallel execution for few Freedom Boards (its interface chip also behaves in such a way it remounts USB devices after target reset / flashing).
Note: indeed this pull request fixes this issue, at least in configuration I've set up.
$ singletest.py --auto --parallel --global-loops 3 -W

MBEDLS: Detecting connected mbed-enabled devices...
MBEDLS: Detected KL46Z, port: COM40, mounted: E:
MBEDLS: Detected KL25Z, port: COM89, mounted: F:
Building library CMSIS (KL25Z, ARM)Building library CMSIS (KL46Z, ARM)

Building library MBED (KL46Z, ARM)
Building library MBED (KL25Z, ARM)
Building project DETECT (KL25Z, ARM)
Building project DETECT (KL46Z, ARM)
TargetTest::KL25Z::ARM::DTCT_1::Simple detect test [OK] in 0.51 of 10 sec
Building project DEV_NULL (KL25Z, ARM)
TargetTest::KL46Z::ARM::DTCT_1::Simple detect test [OK] in 0.48 of 10 sec
Building project DEV_NULL (KL46Z, ARM)
TargetTest::KL25Z::ARM::EXAMPLE_1::/dev/null [OK] in 3.50 of 20 sec
Building project I2C_MMA8451Q (KL25Z, ARM)
TargetTest::KL46Z::ARM::EXAMPLE_1::/dev/null [OK] in 3.52 of 20 sec
Building project I2C_MMA8451Q (KL46Z, ARM)
TargetTest::KL25Z::ARM::KL25Z_5::MMA8451Q accelerometer [OK] in 12.54 of 15 sec
Building project HELLO (KL25Z, ARM)
TargetTest::KL46Z::ARM::KL25Z_5::MMA8451Q accelerometer [FAIL] in 12.54 of 15 sec
TargetTest::KL25Z::ARM::MBED_10::Hello World [OK] in 0.39 of 5 sec
Building project TICKER (KL25Z, ARM)
TargetTest::KL46Z::ARM::KL25Z_5::MMA8451Q accelerometer [FAIL] in 12.55 of 15 sec
TargetTest::KL25Z::ARM::MBED_11::Ticker Int [OK] in 11.38 of 15 sec
Building project CPP (KL25Z, ARM)
TargetTest::KL25Z::ARM::MBED_12::C++ [OK] in 1.39 of 10 sec
Building project RTC (KL25Z, ARM)
TargetTest::KL46Z::ARM::KL25Z_5::MMA8451Q accelerometer [FAIL] in 12.55 of 15 sec
Building project HELLO (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_16::RTC [OK] in 4.59 of 20 sec
Building project STDIO (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_10::Hello World [OK] in 0.39 of 5 sec
Building project TICKER (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_2::stdio [OK] in 0.74 of 20 sec
Building project TICKER_2 (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_11::Ticker Int [OK] in 11.36 of 15 sec
Building project CPP (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_23::Ticker Int us [OK] in 11.36 of 15 sec
Building project TIMEOUT (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_12::C++ [OK] in 1.36 of 10 sec
Building project RTC (KL46Z, ARM)
TargetTest::KL46Z::ARM::MBED_16::RTC [OK] in 4.58 of 20 sec
Building project STDIO (KL46Z, ARM)
TargetTest::KL46Z::ARM::MBED_2::stdio [OK] in 0.79 of 20 sec
Building project TICKER_2 (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_24::Timeout Int us [FAIL] in 14.62 of 15 sec
TargetTest::KL46Z::ARM::MBED_23::Ticker Int us [OK] in 11.39 of 15 sec
Building project TIMEOUT (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_24::Timeout Int us [OK] in 11.59 of 15 sec
Building project TIME_US (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_24::Timeout Int us [OK] in 11.59 of 15 sec
Building project TIME_US (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_25::Time us [OK] in 11.38 of 15 sec
Building project DIV (KL25Z, ARM)
TargetTest::KL25Z::ARM::MBED_26::Integer constant division [OK] in 1.40 of 20 sec
Building project TICKER_3 (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_25::Time us [OK] in 11.39 of 15 sec
Building project DIV (KL46Z, ARM)
TargetTest::KL46Z::ARM::MBED_26::Integer constant division [OK] in 1.40 of 20 sec
Building project TICKER_3 (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_34::Ticker Two callbacks [OK] in 11.36 of 15 sec
Building project BASIC (KL25Z, ARM)
TargetTest::KL25Z::ARM::MBED_A1::Basic [OK] in 1.36 of 20 sec
Building project CALL_BEFORE_MAIN (KL25Z, ARM)
TargetTest::KL25Z::ARM::MBED_A21::Call function before main (mbed_main) [OK] in 1.44 of 20 sec
Building project ECHO (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_34::Ticker Two callbacks [OK] in 11.36 of 15 sec
Building project BASIC (KL46Z, ARM)
TargetTest::KL46Z::ARM::MBED_A1::Basic [OK] in 1.35 of 20 sec
Building project CALL_BEFORE_MAIN (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_A9::Serial Echo at 115200 [OK] in 6.34 of 20 sec
Building project BUS_OUT (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_A21::Call function before main (mbed_main) [OK] in 1.45 of 20 sec
Building project ECHO (KL46Z, ARM)
TargetTest::KL25Z::ARM::MBED_BUSOUT::BusOut [OK] in 2.30 of 15 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project BASIC (KL25Z, ARM)
TargetTest::KL46Z::ARM::MBED_A9::Serial Echo at 115200 [OK] in 6.34 of 20 sec
Building project BUS_OUT (KL46Z, ARM)
TargetTest::KL46Z::ARM::MBED_BUSOUT::BusOut [OK] in 2.32 of 15 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project BASIC (KL46Z, ARM)
TargetTest::KL25Z::ARM::RTOS_1::Basic thread [OK] in 11.37 of 15 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project MUTEX (KL25Z, ARM)
TargetTest::KL46Z::ARM::RTOS_1::Basic thread [OK] in 11.39 of 15 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project MUTEX (KL46Z, ARM)
TargetTest::KL25Z::ARM::RTOS_2::Mutex resource lock [OK] in 11.56 of 20 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project SEMAPHORE (KL25Z, ARM)
TargetTest::KL25Z::ARM::RTOS_3::Semaphore resource lock [OK] in 8.49 of 20 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project SIGNALS (KL25Z, ARM)
TargetTest::KL46Z::ARM::RTOS_2::Mutex resource lock [OK] in 11.49 of 20 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project SEMAPHORE (KL46Z, ARM)
TargetTest::KL25Z::ARM::RTOS_4::Signals messaging [OK] in 6.44 of 20 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project QUEUE (KL25Z, ARM)
TargetTest::KL46Z::ARM::RTOS_3::Semaphore resource lock [OK] in 8.49 of 20 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project SIGNALS (KL46Z, ARM)
TargetTest::KL25Z::ARM::RTOS_5::Queue messaging [OK] in 2.41 of 20 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project MAIL (KL25Z, ARM)
TargetTest::KL46Z::ARM::RTOS_4::Signals messaging [OK] in 6.45 of 20 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project QUEUE (KL46Z, ARM)
TargetTest::KL25Z::ARM::RTOS_6::Mail messaging [OK] in 2.41 of 20 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project TIMER (KL25Z, ARM)
TargetTest::KL46Z::ARM::RTOS_5::Queue messaging [OK] in 2.41 of 20 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project MAIL (KL46Z, ARM)
TargetTest::KL46Z::ARM::RTOS_6::Mail messaging [OK] in 2.40 of 20 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project TIMER (KL46Z, ARM)
TargetTest::KL25Z::ARM::RTOS_7::Timer [OK] in 11.37 of 15 sec
Building library RTX (KL25Z, ARM)
Building library RTOS (KL25Z, ARM)
Building project ISR (KL25Z, ARM)
TargetTest::KL25Z::ARM::RTOS_8::ISR (Queue) [OK] in 6.45 of 20 sec
TargetTest::KL46Z::ARM::RTOS_7::Timer [OK] in 11.37 of 15 sec
Building library RTX (KL46Z, ARM)
Building library RTOS (KL46Z, ARM)
Building project ISR (KL46Z, ARM)
TargetTest::KL46Z::ARM::RTOS_8::ISR (Queue) [OK] in 6.45 of 20 sec
Test summary:
+--------+--------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result | Target | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+--------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK     | KL25Z  | ARM       | DTCT_1      | Simple detect test                    |        0.51        |       10      |  1/1  |
| OK     | KL46Z  | ARM       | DTCT_1      | Simple detect test                    |        0.48        |       10      |  1/1  |
| OK     | KL25Z  | ARM       | EXAMPLE_1   | /dev/null                             |        3.5         |       20      |  1/1  |
| OK     | KL46Z  | ARM       | EXAMPLE_1   | /dev/null                             |        3.52        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | KL25Z_5     | MMA8451Q accelerometer                |       12.54        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_10     | Hello World                           |        0.39        |       5       |  1/1  |
| OK     | KL25Z  | ARM       | MBED_11     | Ticker Int                            |       11.38        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_12     | C++                                   |        1.39        |       10      |  1/1  |
| FAIL   | KL46Z  | ARM       | KL25Z_5     | MMA8451Q accelerometer                |       12.55        |       15      |  0/3  |
| OK     | KL25Z  | ARM       | MBED_16     | RTC                                   |        4.59        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_10     | Hello World                           |        0.39        |       5       |  1/1  |
| OK     | KL25Z  | ARM       | MBED_2      | stdio                                 |        0.74        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_11     | Ticker Int                            |       11.36        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_23     | Ticker Int us                         |       11.36        |       15      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_12     | C++                                   |        1.36        |       10      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_16     | RTC                                   |        4.58        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_2      | stdio                                 |        0.79        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_23     | Ticker Int us                         |       11.39        |       15      |  1/1  |
| FAIL   | KL25Z  | ARM       | MBED_24     | Timeout Int us                        |       11.59        |       15      |  1/2  |
| OK     | KL46Z  | ARM       | MBED_24     | Timeout Int us                        |       11.59        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_25     | Time us                               |       11.38        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_26     | Integer constant division             |        1.4         |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_25     | Time us                               |       11.39        |       15      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_26     | Integer constant division             |        1.4         |       20      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_34     | Ticker Two callbacks                  |       11.36        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_A1     | Basic                                 |        1.36        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_A21    | Call function before main (mbed_main) |        1.44        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_34     | Ticker Two callbacks                  |       11.36        |       15      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_A1     | Basic                                 |        1.35        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_A9     | Serial Echo at 115200                 |        6.34        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_A21    | Call function before main (mbed_main) |        1.45        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | MBED_BUSOUT | BusOut                                |        2.3         |       15      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_A9     | Serial Echo at 115200                 |        6.34        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | MBED_BUSOUT | BusOut                                |        2.32        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_1      | Basic thread                          |       11.37        |       15      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_1      | Basic thread                          |       11.39        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_2      | Mutex resource lock                   |       11.56        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_3      | Semaphore resource lock               |        8.49        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_2      | Mutex resource lock                   |       11.49        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_4      | Signals messaging                     |        6.44        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_3      | Semaphore resource lock               |        8.49        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_5      | Queue messaging                       |        2.41        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_4      | Signals messaging                     |        6.45        |       20      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_6      | Mail messaging                        |        2.41        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_5      | Queue messaging                       |        2.41        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_6      | Mail messaging                        |        2.4         |       20      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_7      | Timer                                 |       11.37        |       15      |  1/1  |
| OK     | KL25Z  | ARM       | RTOS_8      | ISR (Queue)                           |        6.45        |       20      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_7      | Timer                                 |       11.37        |       15      |  1/1  |
| OK     | KL46Z  | ARM       | RTOS_8      | ISR (Queue)                           |        6.45        |       20      |  1/1  |
+--------+--------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
Result: 2 FAIL / 48 OK

Completed in 342.10 sec

I can confirm that this Pull Request fixes the timing issue with the C027 board.


Remove args from stories

Changes
WIP
Removed args from stories.
Testing
Couple of images updated.
Docs
N/A

no need for "chunks" imo. everything can be done together.

Should be done.


Bug in uploading videos and creating of events on the Apple iphone

What is the bug?
POSSIBLE EVENT CREATION BUG:
While trying to create events this is the error detected
Error loading page
Domain: NSURLErrorDomain
Error Code: -1004
Description: Could not connect to the server.
This may be attributed to possible causes like server unavailability, network connection, DNS issues but I think this is highly unlikely the case as the frames for bounty and poll activities work clearly on the same device simultaneously so I suggest it should be checked for possible bugs or errors
VIDEO UPLOAD ERROR:
On the new update while trying to upload videos to the timeline it disappears after clicking the video to upload even when it was selected carefully. This is the case for the iPhone as I tried on another device and same reoccurrence was detected. The device been used is the iPhone 14 Pro Max so compatibility is not a problem
Thanks for looking into this and I hope it makes farcaster better.

@Rufusemmanuel This seems to be a Warpcast specific bug and not related to the farcaster protocol

Alright thank you let me report accordingly

Closing as this repository is for the Farcaster protocol, not Warpcast. Thanks for your understanding.

Understood sir🫡, thank you


filter does not work with the second parameter as var

I noticed that in filter, I can't use var (probably loses context to data), it would be nice if you could also use data from data. here is my example of use:
Data
{
    "locale": "pl",
    "locales": [
        {
            "name": "Israel",
            "code": "he",
            "flag": "🇮🇱",
            "iso": "he-IL",
            "dir": "rtl"
        },
        {
            "name": "українська",
            "code": "ue",
            "flag": "🇺🇦",
            "iso": "uk-UA",
            "dir": "ltr"
        },
        {
            "name": "Polski",
            "code": "pl",
            "flag": "🇵🇱",
            "iso": "pl-PL",
            "dir": "ltr"
        }
    ]
}

Valid JSON
{
    "filter": [
        {
            "var": "locales"
        },
        {
            "!==": [
                {
                    "var": "code"
                },
                "pl"
            ]
        }
    ]
}

Invalid JSON
{
    "filter": [
        {
            "var": "locales"
        },
        {
            "!==": [
                {
                    "var": "code"
                },
                {
                    "var": "locale"
                }
            ]
        }
    ]
}

in both cases I should receive:
[{"name":"Israel","code":"he","flag":"🇮🇱","iso":"he-IL","dir":"rtl"},{"name":"українська","code":"ue","flag":"🇺🇦","iso":"uk-UA","dir":"ltr"}]

maybe some additional operator? or maybe _.locale to get access the original data?

This is actually one of the reasons I forked json-logic-engine :)
This is the "handlebars" style Traversal capability.
const f = engine.build({
    filter: [
        { var:  'locales' },
        { '===': [{ var: 'code' }, { var: '../../locale' }] }
    ]
})

f(data) // [ { name: 'Polski', code: 'pl', flag: '🇵🇱', iso: 'pl-PL', dir: 'ltr' } ]

Works beautifully! Thank you! it would be useful to add a similar example in the documentation.
There is a small error in the Filter operator in the "Higher Order Operators" table. The instruction for this operator is filter not Filter.

I have anothier question @TotalTechGeek, I don't know if this is the expected result, but it looks like it is not:
{
    "get": [
        {
            "xs": "100",
            "sm": "99",
            "md": "60",
            "lg": "30",
            "xl": "12"
        },
        {
            "var": "context.root.$vuetify.breakpoint.name"
        }
    ]
}

{
    "context": {
        "root": {
            "$vuetify": {
                "breakpoint": {
                    "name": "xs"
                }
            }
        }
    }
}

result is null, but it should be: "100"

but it's already working properly:
{
    "get": [
        {
            "var": "values"
        },
        {
            "var": "context.root.$vuetify.breakpoint.name"
        }
    ]
}

{
    "values": {
        "xs": "100",
        "sm": "99",
        "md": "60",
        "lg": "30",
        "xl": "12"
    },
    "context": {
        "root": {
            "$vuetify": {
                "breakpoint": {
                    "name": "xs"
                }
            }
        }
    }
}

I think this is because when it is an object, the object key is taken and the method is looked for to execute, but if the method is not found, it gets null instead of the value that was set. maybe it will be a good idea to check whether it is an object, whether it has only one key and whether the key in the object is a registered method, if so, run it, if not, give the value of the object

Hi @tatarysh
What settings are you running the engine with? Have you added any methods (like xs)?
There are two main ways to solve this:
If you want to embed data in your logic without risking it running as a method, the recommended approach is to use preserve.
{
    "get": [{
            "preserve": {
                "xs": "100",
                "sm": "99",
                "md": "60",
                "lg": "30",
                "xl": "12"
            }
        },
        {
            "var": "context.root.$vuetify.breakpoint.name"
        }
    ]
}

preserve will guarantee that anything passed into it will not be invoked as a method. This also helps prevent ambiguity for situations where you might have xs or something registered as a method in the engine.
If you haven't added other methods to the engine (thus no ambiguity), it's possible to enable permissive mode on the Logic Engine, where an object that fails to be interpeted will be treated as data.

P.S. here is a link with an example of permissive mode: https://github.com/TotalTechGeek/json-logic-engine/issues/6#issuecomment-1494786753
Currently, permissive mode doesn't check if the object only has one key; it just checks if the first key it sees is a registered method.
I could see an argument for allowing logic to have a single key, though I still feel that preserve is the safest and least ambiguous way to embed data in your logic.
I may spend some time thinking about whether I want to allow some further customizability.

@tatarysh While I still stand by my preferences communicated above (preserve seems like a simple way to do this, and should be a good ecosystem standard), I've decided to implement a way for users to customize the behavior to their preferences.
class DataEngine extends LogicEngine {
  isData (logic, firstKey) {
    if (Object.keys(logic).length > 1) return true
    return !(firstKey in this.methods)
  }
}

As of the newly published v1.3.2, you can extend the LogicEngine to specify the isData behavior.
The implementation for isData there will:

Assume it is data if there is more than one key.
Assume it is data if it is one key, but does not match anything in the methods lookup.

Matching the behavior you desire :)


fix claim_search rpc and cli behaving differently

don't autopopulate order_by in the server, instead populate an empty list in the client (which is what cli already did)

@jackrobison does this need to be reviewed? plz request a review (or request from @lbryio/protocools if you're not sure whom to ask)

i reviewed this in slack, will copy/paste it here as well

@jackrobison after reflecting on this more, i think this PR should really just be to remove the default order_by, so just removing these two lines and fixing any tests that may fail expecting the default to be used (not sure if there are any tests that expect the default...):
https://github.com/lbryio/lbry-sdk/blob/0d08858dfb5178056fc1ad4c5afc3d4c1bfff511/lbry/wallet/server/db/reader.py#L421-L422

done in https://github.com/lbryio/lbry-sdk/pull/2810


package upgrade failure stops all following upgrades

I have 11 packages waiting to be upgraded.  My first one is throwing an exception and the whole process dies.  This means until I solve the problem with the first one all others will have to wait.
I will uninstall the offending package for now but this should be fixed.

windows 8.1
apm  0.123.0
npm  2.1.18
node 0.10.35
python 2.7.8
git 1.7.11.msysgit.1
visual studio 2013

Are you upgrading from within Atom or via apm on the command line?

command line


news: hexo-util 2.1.0 and hexo-fs 3.0.1

Check List
Please read and check followings before submitting a PR.

[ ] I want to publish my theme on Hexo official website.

[ ] I have read the theme publishing doc.
[ ] name is unique.
[ ] link URL is correct.
[ ] preview URL is correct.
[ ] preview URL web site is rendered correctly.
[ ] Add a screenshot to source/themes/screenshots.
[ ] Screenshot filename is same as value of name.
[ ] Screenshot size is 800 * 500.
[ ] Screenshot file format is png.

[ ] I want to publish my plugin on Hexo official website.

[ ] I have read the plugin publishing doc.
[ ] name is unique.
[ ] link URL is correct.

[x] Others (Update, fix, translation, etc...)

Languages:
[x] en English
[ ] ko Korean
[ ] pt-br Brazilian Portuguese
[ ] ru Russian
[ ] th Thai
[ ] zh-cn simplified Chinese
[ ] zh-tw traditional Chinese

Pending https://github.com/hexojs/hexo-util/pull/201

LGTM! Can be merged immediately after newer versions of those 2 plugins being released.


Training fail: EOFError: Ran out of input

Hi there,
i am getting an error after 1 iteration of training and I cannot figure out the reason.
Do you have any idea what is causing the error EOFError: Ran out of input ?
Thanks in advance!
The error looks like this:
Loading train data:   0%|                                                                                | 0/2732 [00:00<?, ?it/s] Traceback (most recent call last):   File "trainer.py", line 44, in <module>     train(0, args, args.checkpoint_path, hp, hp_str)   File "/opt/3tbdrive1/products/voicesurfer/02.VoiceTraining/univnet/utils/train.py", line 125, in train     for mel, audio in loader:   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/tqdm/std.py", line 1185, in __iter__     for obj in iterable:   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 521, in __next__     data = self._next_data()   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 1203, in _next_data     return self._process_data(data)   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 1229, in _process_data     data.reraise()   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/_utils.py", line 434, in reraise     raise exception EOFError: Caught EOFError in DataLoader worker process 0. Original Traceback (most recent call last):   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 287, in _worker_loop     data = fetcher.fetch(index)   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch     data = [self.dataset[idx] for idx in possibly_batched_index]   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 49, in <listcomp>     data = [self.dataset[idx] for idx in possibly_batched_index]   File "/opt/3tbdrive1/products/voicesurfer/02.VoiceTraining/univnet/datasets/dataloader.py", line 61, in __getitem__     return self.my_getitem(idx)   File "/opt/3tbdrive1/products/voicesurfer/02.VoiceTraining/univnet/datasets/dataloader.py", line 78, in my_getitem     mel = self.get_mel(wavpath)   File "/opt/3tbdrive1/products/voicesurfer/02.VoiceTraining/univnet/datasets/dataloader.py", line 96, in get_mel     mel = torch.load(melpath, map_location='cpu')   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/serialization.py", line 608, in load     return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)   File "/opt/3tbdrive1/products/voicesurfer/venv/lib/python3.6/site-packages/torch/serialization.py", line 777, in _legacy_load     magic_number = pickle_module.load(f, **pickle_load_args) EOFError: Ran out of input

It seems to be that you haven't prepared files, containing mel-spectrograms, but dataset trying to load it from disk.
In this line
https://github.com/mindslab-ai/univnet/blob/9bb2b54838bb6d7ce767131cc7b8b61198bc7558/datasets/dataloader.py#L100
Authors generating mel-spectrogram in runtime if loading fails, but it seems they have the wrong try-except statement.
Change this line to:
 except (FileNotFoundError, RuntimeError, TypeError, AssertionError, EOFError)
I think it should work.


Fix in pg_marginal for REVERT, RETURN, STOP

Due to wrong memory range for no_op deployment the program terminated prematurely.

Plus calldata is removed. I think we do not need calldata here.


⚠ Guya.moe Proxied has degraded performance

In 4a50a17, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 12917 ms

Resolved: Guya.moe Proxied performance has improved in 8cc28d8 after 19 hours, 57 minutes.


Can't update project

What happened?
While trying to update my actor project, I got this error:
❰marenz❙~/frequenz/fcr(git≠sdk-update)❱✘≻ cookiecutter gh:frequenz-floss/frequenz-repo-config-python --directory=cookiecutter  --replay --replay-file .cookiecutter-replay.json --overwrite-if-exists
You've downloaded /home/marenz/.cookiecutters/frequenz-repo-config-python before. Is it okay to delete and re-download it? [yes]:
Traceback (most recent call last):
  File "/usr/bin/cookiecutter", line 33, in <module>
    sys.exit(load_entry_point('cookiecutter==2.1.1', 'console_scripts', 'cookiecutter')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/cookiecutter/cli.py", line 194, in main
    cookiecutter(
  File "/usr/lib/python3.11/site-packages/cookiecutter/main.py", line 114, in cookiecutter
    result = generate_files(
             ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/cookiecutter/generate.py", line 373, in generate_files
    generate_file(
  File "/usr/lib/python3.11/site-packages/cookiecutter/generate.py", line 173, in generate_file
    tmpl = env.get_template(infile_fwd_slashes)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/jinja2/environment.py", line 1010, in get_template
    return self._load_template(name, globals)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/jinja2/environment.py", line 969, in _load_template
    template = self.loader.load(self, name, self.make_globals(globals))
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/jinja2/loaders.py", line 138, in load
    code = environment.compile(source, name, filename)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/jinja2/environment.py", line 768, in compile
    self.handle_exception(source=source_hint)
  File "/usr/lib/python3.11/site-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File ".github/labeler.yml", line 13, in template
    - "**/*.md"
  ^^^^^^^^^^^^^^
jinja2.exceptions.TemplateAssertionError: No filter named 'as_identifier'.
  File ".github/labeler.yml", line 13
    #   - "src/frequenz/{{cookiecutter.type}}/{{cookiecutter.name | as_identifier}}/module/**"

What did you expect instead?
no error.
Affected version(s)
No response
Affected part(s)
Cookiecutter template (part:cookiecutter)
Extra information
No response

Nevermind, reading release notes helps. But maybe it could be mentioned in the upgrade docu for this specific release

It is in the release notes for this specific release: https://github.com/frequenz-floss/frequenz-repo-config-python/releases/tag/v0.4.0
Do you mean somewhere else? BTW, I'll close as invalid.

I meant the upgrade guide could have had this specific note mentioned, but the mention should only exist in this particular version v0.4.0 and would be removed again in v0.5.0 from that guide

I meant the upgrade guide could have had this specific note mentioned, but the mention should only exist in this particular version v0.4.0 and would be removed again in v0.5.0 from that guide.
Or possibly replaced with new notes that are valid only for v0.5.0
That would be my ideal scenario I suppose :)

I see and agree that's much more convenient from the user's perspective, but it is quite annoying from the maintainers perspective.
What we could do instead is add a generic note to the migration instructions in the docs that mentions that you should check the Upgragind section on the release notes for the version(s) you want to upgrade to. I guess that could have a better balance, because also when upgrading if you are skipping versions (which is totally valid) you'll never have all the list of steps necessary if we reset the migration instructions in the docs on every release.

No, not the migration instructions, the upgrade instructions

Yeah, sorry, it is confusing that we have an upgrading section in the release notes and an upgrading instructions in the docs. I mean the upgrading instructions in the docs can mention the upgrading section in the release notes for the version you are upgrading to :)

So, would that be sufficient or at least better in you view?

Def. better

#103


Increase logo size and make it clickable everywhere

I cleaned up the CSS a just little more after https://github.com/openfarmcc/OpenFarm/pull/881

Coverage remained the same at 99.352% when pulling cdc9e5c4eed173b1f3cd31886dfe2220a5d4566e on nicholasedwards:master into c325531cfc6125a94b38dd8f357405befe8cabc2 on openfarmcc:master.


Configure default language for fenced code blocks

Context
When reformatting indented code blocks, I'd like to have an option to set the default language added to the fenced code block that mdformat creates.
I habe a lot of old documentation with indeded code blocks, and 99% of them are sh lang, which I manually need to add after reformatting.
Proposal
Add an option to the config file like:
fenced_lang = sh

Which will automatically use
```sh

instead of
```

when reformatting indented code blocks.
Tasks and updates
No response

Hey thanks for the issue!
I don't think this is a generally useful enough feature to be added. I think mdformat should be helpful to you anyways: run it to normalize all code blocks, and then it should be fairly trivial to come up with a sed script to add  the sh language tags.


tombstone soulbound compatibility on wearable

could it be possible to have support to apply the enchant from this mod
https://www.curseforge.com/minecraft/mc-mods/corail-tombstone
to apply to pokemon wearable so they dont go to the pc on death, mainly the watch and the backpack

Hmm, their mod is not open source, so I cannot easily see how they are actually applying that enchantment. this may need to be an issue made on their side to support mine

there are a few things I can try regarding how the stuff is sent to PC, but I cannot guarentee it will work, given their lack of being open source.


Refine player UI

UI should be responsive designed to match different window size
Mobile doesn't have to be supported currently

[x] space key to toggle play/pause
[x] left/right key to seek backward/forward
[x] key events should be captured in whole player element level
[x] control bar show up when mouse enter in the player
[x] control bar fade off when mouse leave the player
[x] when the player is paused there should be some hints like a paused overlay tint
[x] when the player continue playing from the paused status, the overlay tint should be removed
[x] the player width/height should have limit.  should not expand as much as possible

resolved in<PHONE_NUMBER>23f2a396b4976c08f1c5d3e62e5ea3 0919f0acef61e5ac3c7e1ca20e953f9cad3a8b69 2d883f11ab2ce818656d569583190a74ff92c96e


Parquet Encryption support

Is Parquet encryption supported or there are plans to support it?
-- and, of course, you deserve a big Thank You for creating this awesome library!

I believe I can.
However Parquet Modular Encryption is a bit more advanced than encrypting the whole file.
I am new to encrypted parquet. My new project deals with sensitive data and I am evaluating my options on Rust - which I am still a beginner - without reinventing the wells.
It looks like Apache Parquet has some encryption support. I want to try polars, perhaps I can mix both.
Thanks for your feedback!

Sorry, just figured this is a duplicate from:
https://github.com/jorgecarleitao/parquet2/issues/154
Closing it.


Don't defer SceneTreeEditor::_warning_changed signal connection

This was causing a crash because by the time the signal was received the object may already have been deleted.
All this method does is start a timer, so there's no need to defer it.

This was changed in #48242, I see no reason to defer it though.
CC @reduz maybe.

Thanks!


Remove text related to deprecated APIs being removed in V1.0.

Now that Atom is at V1.0 we no longer need to show a warning message regarding deprecated APIs being removed in the V1.0 release.

Thanks for this, totally forgot about this.


Userlog service not updating redis key if it doesn't exist

In the userlog service redis keys will not be updated if they do not exist. The problem is with catching an exception from the redis store at line: https://github.com/owncloud/ocis/blob/4354f5a84bff5f7196869946d9fca2d7e691b102/services/userlog/pkg/service/service.go#L249
The PR https://github.com/go-micro/plugins/pull/97 introduced the problem because the store.ErrNotFound was replaced with the redis error.

what is the user impact?

should be fixed in rc.3