Added a search filter and removed the scroll from type selection during Register Backend

What type of PR is this?
/kind enhancement
What this PR does / why we need it:
This PR fixes the scroll visible in the type selection during backend registration.
Additionally this PR also adds a search filter for the type selection dropdown to make it easier for the user to select the backend type.
Which issue(s) this PR fixes:
Fixes #583
Test Report Added?:
/kind TESTED
Test Report:

Special notes for your reviewer:

Q: Will adding a "Vendor" dropdown to select the Vendor and then the Storage entity [Object, Block, File etc.] make  the list more organized,, instead of showing all the Backends in one long list.

Will adding a "Vendor" dropdown to select the Vendor and then the Storage entity [Object, Block, File etc.] make the list more organized,, instead of showing all the Backends in one long list.

@rajat-soda
This works when all the vendors have multiple solutions. But some may not have any except object storage.
In which case we add an extra select step. just to select the one. I think the search works best since it is enhancing current dropdown. For now we can go with this but if all vendors that we support have multiple backend types then we can add the vendor dropdown.

ok .lets add the vendor drop down , when we have sufficient data from majority of the vendors.

LGTM

ok .lets add the vendor drop down , when we have sufficient data from majority of the vendors.

@rajat-soda @PravinRanjan10
For this we will also need to revisit the way we have classified the types of backends,
The only way to distinguish vendors is by matching the type string of each backend.
It would be beneficial if the types API returns a list based on the vendor and the supported backends for each. This way the user will get a classification even in the API response and not the Dashboard alone.

ok .lets add the vendor drop down , when we have sufficient data from majority of the vendors.

@rajat-soda @PravinRanjan10
For this we will also need to revisit the way we have classified the types of backends,
The only way to distinguish vendors is by matching the type string of each backend.
It would be beneficial if the types API returns a list based on the vendor and the supported backends for each. This way the user will get a classification even in the API response and not the Dashboard alone.
Something like:
{
    "backends": {
        "aws" : [
            {
            "label" : "aws-s3",
            "type" : "object"
            },
            {
            "label" : "aws-file",
            "type" : "file"
            },
            {
            "label" : "aws-block",
            "type" : "block"
            }
        ],
        "azure" : [
            {
            "label" : "azure-blob",
            "type" : "object"
            },
            {
            "label" : "azure-file",
            "type" : "file"
            }
        ],
        "gcp" : [
            {
            "label" : "gcp-s3",
            "type" : "object"
            },
            {
            "label" : "gcp-file",
            "type" : "file"
            }
        ]
    }
}

Yes, makes sense


Add a truncate function to template

Add a function to the templates that can truncate strings at a certain length

Closing because this can be done with the built-in printf template function.


Suggestions for Mobs

MISSING FOLLOWING
Pillager - rides ravager(this may be particularly difficult but Ravage&Cabbage can probably help, if you've heard of it)
Illusioner - creates copies of itself
Ravager - roar attack, by default rams and breaks foilage
Shulker - when ability used shoots bullet
Vindicator - same as pillager
Zombie + Skeleton Horse - Jump like horse
Endermite - Teleport
Silverfish - burrow into blocks
Vex - Fly and pass through blocks(maybe don't make player take damage though)
Panda(baby) - Create a slime ball :)
(Brown)Mooshroom - mushroom stew/milk
Goat - charge forward
Charged Creeper - More damage than normal creeper
Improvements
Wither Skeleton - fire resistance
Fox - jumps higher
Iron Golem - Holds flower
Bee - can enter a hive to hide?(minor)
Cat/Ocelot - Scares creepers
Enderman - shift + right click to pick up/put down a block
Also maybe add some convenience enchantments e.g.:
Water Protection
Speed of Flight
Molten Strider(from depth strider)

Please don't take it as an issue, it's just a suggestion.


Resolved CDN issue that was distorting whole WebPage

Description
Done some changes in the CSS part of STYLEBOX (CARD SECTION) and placed the CDN at right location.
Removed the precode that come with Bootstrap that was creating distortion too.
Fixes #264

[x] Bug fix (non-breaking change which fixes an issue)

Explain the Testing instructions
Test Configuration:

Operating system: Win 10
Version: Chrome Browser
Text-editors used: VS code

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@arpit456jain @VidhiBhatt01   Successfylly Resolved


RFP - Lyrics Finder

https://www.mediahuman.com/lyrics-finder/
MediaHuman Lyrics Finder is a free software application, which can help you find and add missing lyrics (song text) to all songs in your music library. It's a safe operation because the app doesn't overwrite lyrics you've already had.
Very easy to use: simply drag&drop some tracks from your favorite music player (e.g. iTunes) and MediaHuman Lyrics Finder will do the rest.
MediaHuman Lyrics Finder will give you access to over a million different lyrics collected from various sources on the Internet.

So I took some time to learn how to make chocolatey packages. I uploaded the corresponding package here https://chocolatey.org/packages/lyricsfinder/1.4.4 . It is waiting for review. I am now looking for maintainers. I uploaded sources here https://github.com/valentind44/chocolatey-packages/tree/master/manual .

@AdmiringWorm
I do wish to continue maintaining the package. I thought it was better if more than one person maintain a package, in case one of the maintainers is not available and the package needs an update.
But I don't mind if I'm the only one maintaining this package. I'll try to make an automatic update script with AU when I have time.

@valentind44 in that case, I would suggest adding a comment on the package page (in the disqus comment section) that you're looking for co-maintainers.
This issue will be closed when the package is approved (or when we notice it), so the a request for adding additional maintainers would be lost here.


Labeling FeatureCollection

Discussed in https://github.com/giswqs/geemap/discussions/814

Originally posted by bismarksr17 December 13, 2021
Hello, I would like to know how I can label the FeatureCollection in GeeMap, something similar to the image in the link!
IMG
References:

https://python-visualization.github.io/folium/modules.html#folium.features.DivIcon
https://ipyleaflet.readthedocs.io/en/latest/api_reference/divicon.html
https://github.com/jupyter-widgets/ipyleaflet/issues/798#issuecomment-992932515

import folium
from folium.features import DivIcon
m = folium.Map([34.0302, -118.2352], zoom_start=13)
folium.map.Marker(
    [34.0302, -118.2352],
    icon=DivIcon(
        icon_size=(150,36),
        icon_anchor=(0,0),
        html='
Test
',
        )
    ).add_to(m)
m

This feature has been implemented. See notebook example https://geemap.org/notebooks/89_add_labels

What Ipyleaflet version are you using?
Having this error when using version '0.13.3'
AttributeError: module 'ipyleaflet' has no attribute 'DivIcon'

pip install ipyleaflet==0.14.0


Allow Images to Appear as Modals (popup/dialog)

Describe the feature you'd like
I received a request from a client to have the ability to save images as modal images (Here's a reference: https://www.w3schools.com/howto/howto_css_modal_images.asp) so that they appear as dialog/popup/float images in the text.
Describe the benefits this would bring to existing BookStack users
This is purely aesthetic
Can the goal of this request already be achieved via other means?
Possibly if I hack the backend code and add the necessary JavaScript, perhaps in a child theme would be safer, but ultimately not realistically
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?
6 months to 1 year
Additional context
This is a low level change request to consider for future versions.

Thanks for the request @kenswampy, but I feel the fundamental request here is already covered by #464 so I'm therefore going to close this off as a duplicate.


Add character: Darth Vader

Hero Description
Trained by Palpatine he become master of the Knights of the Dark Side of the Force.

Concept Art

Inspiration
Darth Vader is a Star Wars character

Moves
Idle
Kyle stands in a attack position and his saber is always flickering
[STICK] Walk
Kyle never run, he just walk
[LEFT] The Force Awakens
Kyle attacks with his saber with 3 variations.
Note:

In code, choose randomically between the 3 animations.

[MIDDLE] The Empire Strikes Back
Animation: Kyle throws the saber that make a arc in his front, and come back to his hand.

[RIGHT] The Last Jedi
Kyle uses the force to paralise an enemy
Animation: Kyle raise the hand ahead and close his hand as he is smashing something.
Effect Animation: Some particle to draw the force power
Note:

If the enemy are in the same place of the effect animation, he (enemy) gets stuned.

[E] TAUNT
Kyle remove out his helmet
Cast animation: Kyle remove his helmet with the 2 hands (one in each side of the helmet), and put under his arm.
Idle animation: Kyle stands breathing with the helmet under his arm
Note: The cast animation begins to play if the player continues to hold the "E" button.
[SPACE] The Rise of Skywalker
Kyles deflect all the attacks coming from the enemies
Animation: Kyle stands his arm up in a defense pose with some variation each time that he deflect an attack.
Var_1: Different defense position
Var_2: Different defense position
Var_3: Different defense position

Note:

In code, choose randomically between the 3 deflect animation animations.

[SHIFT] Feel the Force
Kyle use the force and becomes a levitate.

This skill makes he faster, while is levitating

Animation: Kyle step harder, as if is trying to jump after a run. After that, he perform a little jump, and than he levitate for a moment.
Obs:
Increase the moviment speed while kyle is levitating.
Tasks

[ ] Idle
[ ] Walk
[ ] Hurt
[ ] [LEFT] The Force Awakens_ var 1
[ ] [LEFT] The Force Awakens_ var 2
[ ] [LEFT] The Force Awakens_ var 3
[ ] [MIDDLE] The Empire Strikes Back_ cast animation
[ ] [RIGHT] The Last Jedi _cast animation
[ ] [RIGHT] The Last Jedi _effect animation
[ ] [E] Taunt_cast animation
[ ] [E] Taunt_idle
[ ] [SPACE] The Rise of Skywalker_ var 1
[ ] [SPACE] The Rise of Skywalker_ var 2
[ ] [SPACE] The Rise of Skywalker_ var 3
[ ] [SHIFT] Feel the Force

Approved for work!

I help in the character gameplay design

wip_01
hours worked: 5 hours and 55 minutes
today i worked on the darth vader model

tposed
posed

@MaisaMilena @MaiaVictor
I changed the vader briefing considerably with the help of @chanceone126

wip_02
hours worked: 10 hours and 30 minutes

walk cycle animation
idle animation

wip_03
hours worked: 16 hours
today i made some animation reference as:

[LEFT] The Force Awakens defense poses
[SPACE] Rogue One animation reference
[Q] The Phantom Menace trow animation reference
[Q] The Phantom Menace return animation reference
[RIGHT] The Rise of Skywalker animation reference

[HURT]

with light saber
without light saber

[WALKCYCLE]

without light saber

[IDLE]

without light saber

[Q] The Phantom Menace

saber twisting
saber return (unfinished)

[RIGHT] The Rise of Skywalker

effect animation

wip_04
hours worked: 21 hours and 40 minutes
[RIGHT] The Rise of Skywalker

the rise of skywalker cast animation (unfinished)

[Q] The Phantom Menace

the phantom manace cast animation
saber spining (remake)
saber return (finished)

[LEFT] The Force Awakens

var 1
var 2
var 3

wip_05
hours worked: 25 hours 50 minutes
[MIDDLE] The Empire Strikes Back

animation
animation without saber

[RIGHT] The Rise of Skywalker

cast animation
cast animation without saber

[SPACE] Rogue One

animation (unfinished)

wip_05
hours worked: 28 hours and 15 minutes
[SPACE] Rogue One

i think that was finishished, what do you think?
@MaisaMilena


Make the port the client proxy proxies to configurable

This is based on #345, so that one needs to go in first.
Otherwise it does what it says on the tin.

Works.


Replace env variable CUSTOM_HEADER with SENTRY_HEADER

Extracted from https://github.com/getsentry/sentry-javascript-bundler-plugins/pull/103#discussion_r1019575661:
The customHeader option can also be set via the CUSTOM_HEADER env variable. This env variable's name is inconsistent as we don't prefix it with SENTRY_ like with all other env variables. Sentry CLI v1 expects exactly this header.  Sentry CLI v2 expects the SENTRY_HEADER env variable (see changelog) which replaces CUSTOM_HEADER.
To already be ahead of a breaking change when upgrading to CLI v2, we can default the JSDoc of the bundler plugin to SENTRY_HEADER and internally, when converting to internal options, set the customHeader variable to the env variables' value:
customHeader: userOptions.customHeader ?? process.env["SENTRY_HEADER"] ?? process.env["CUSTOM_HEADER"]

Interestingly, SENTRY_HEADER isn't documented in the CLI configuration docs.

makes sense to me! Avoiding a breaking change that is easily avoidable makes sense to me. I can take care of this!


Update boards to BETA state

@agherzan

Will redo this once you merge the move of meta-resin to v1.1.1

LGTM


Add support for Postgres as OpenMetadata store

OpenMetadata currently only supports MySQL as the database service for metadata storage. Many organizations standardize on using Postgres as the database service of choice. Many users have requested adding support for Postgres.
Tasks and PRs related to this epic:

#3952
#4541
#4551
#4573
#4508

Cool. Does this also include lineage/usage connector for postgres?

Thanks @ulixius9 for putting the docs together https://docs.open-metadata.org/data-lineage/usage-workflow-through-query-logs @suparna-bhattacharya please refer to that to run the Postgres or any other database usage/lineage parsing


Compatibility with Enhanced Edition (Trilogy)/EE(T)?

@evancauteren @RamosPabloA
Greetings!  Thankee for releasing this mod!
How compatible is this with BG2EE and EET (the Enhanced Edition Trilogy)?
May we get EET compatibility?
Thankee!

Hi @Endarire! Yes, it should be compatible. There were some quests that had chapter conditionals, but those were changed to make it adaptable to EET without affecting those who have BG2 EE, nor affecting the story itself. You should not have any problems playing it in EET.


[shaped-scripts] Support FX

The basic support is there now. I have grand plans for more, but that's another project entirely,


Drag/drop always expands non-hovered nodes when use_html5:true

When using drag/drop while use_html5 is true, nodes that you hover-over are expanded, even if you hover-off of them before the open_timeout time has elapsed.
I would expect the nodes to not be expanded if you hover-off before the open_timeout time has elapsed.
Version 3.3.2
Codepen: http://codepen.io/jarstelfox/pen/LbxxdY

That was quick, thanks!


[BUG] ?edit does not show the toolbar login in 4.1rc4

Description
I can only login with /admin/, adding ?edit to any url does not bring up to cms toolbar with login form.
Steps to reproduce
add ?edit to any cms url.
Expected behaviour
Toolbar with login form shown.
Actual behaviour
Nothing.
Additional information (CMS/Python/Django versions)
cms 4.1rc4
Do you want to help fix this issue?

[ ] Yes, I want to help fix this issue and I will join #workgroup-pr-review on Slack to confirm with the community that a PR is welcome.
[x] No, I only want to report the issue.

@benzkji The toolbar appears with ?toolbar_on as of version 4.

THX!
So we teached our clients to use ?edit for ages...and...suddenly...they have to learn the underscore? Why change something so short and easy to understand? I vote to make it configurable!
Or are there reasons I don't see?

ha, it already is, right?
CMS_TOOLBAR_URL__ENABLE

It is. The reason is that the edit endpoint is not reached by logging in through the toolbar - unlike in v3.

makes sense. thanks. I'll probably change it to "?login" then ;-)


[SPARK-24879][SQL] Fix NPE in Hive partition pruning filter pushdown

What changes were proposed in this pull request?
We get a NPE when we have a filter on a partition column of the form col in (x, null). This is due to the filter converter in HiveShim not handling nulls correctly. This patch fixes this bug while still pushing down as much of the partition pruning predicates as possible, by filtering out nulls from any in predicate. Since Hive only supports very simple partition pruning filters, this change should preserve correctness.
How was this patch tested?
Unit tests, manual tests

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Can one of the admins verify this patch?

Test this please

add to whitelist

Test build #93369 has started for PR 21832 at commit ce86fbe.

Test build #93369 has finished for PR 21832 at commit ce86fbe.

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

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

Merged build finished. Test PASSed.

LGTM
Thanks! Merged to master


Replaced {...a,...b} with Object.assign

Object.assign is 1.5 times faster than the object-destructuring syntax.

OK LETS DO IT


Run PyTorch unit tests in OSS CI

The torch_tests.py was taken from https://github.com/pytorch/pytorch/pull/70049, and I modified the skip list. I am running these tests in our NVIDIA CI, and I find that changes in torch.testing._internal.distributed.distributed_test might break this test. I think it is a good idea to maintain a copy of this file in the public torch_ucc repository so that we can get the signal of the status of these tests from the public OSS CI.

cc: @srinivas212 @bryanmr


fix path detection message when .julia folder isn't in ~

messages about what is going to be added to config files should be exactly what is going to be inserted. For cases where people's .julia folder isn't in their home directory, this message can be incorrect.

thanks!


cmake: support snippets scope for zephyr_get()

Fixes: #57139
Snippets introduces the possibility of defining DTC_OVERLAY_FILE and
CONFIG_OVERLAY in snippets.
Snippets must co-exist with existing infrastructure of DTC_OVERLAY_FILE
and OVERLAY_CONFIG, and a user specifying a snippet must be able to
specify extra files for adjusting the snippet. This means that if the
following is specified:
-DSNIPPET=some_snippet -DOVERLAY_CONFIG=extra.conf
then extra.conf may contain adjustments to the snippet.
Similar to sysbuild. Image a sysbuild controlled image default uses a
default snippet for building, by ensuring that any extra
-D<image>_OVERLAY_CONFIG=extra.conf arguments takes precedence over
the snippet we allow users to make adjustments if they need.
This commit introduces a snippets_target where snippet scoped variables
can be set and then zephyr_get() will take such snippet scoped
variables into consideration before returning.
Adjust calls to zephyr_get(DTC_OVERLAY_FILE) and
zephyr_get(OVERLAY_CONFIG) to use MERGE to ensure all scopes are
considered.
As DTC_OVERLAY_FILE is now taken from multiple scopes, remove the
set(DTC_OVERLAY_FILE CACHE ...) call as this call interferes with
the scope handling of zephyr_get().

NOTE the current CI failures happens because the use of a custom target, such as snippets_target, is not possible in script mode.
This means the use of snippets_target breaks the usage of package_helper used by twister for filtering.
Looking into a fix.

which ensures that the snippet overlays are processed after DTC_OVERLAY_FILE and OVERLAY_CONFIG.

and that is what I would argue that we don't want, because a user should be able to specify a common snippet and from there specify additional adjustments in a DTC_OVERLAY_FILEor more likely in anOVERLAY_CONFIG`.
If snippets takes precedence over OVERLAY_CONFIG, then user must completely abandon the specific snippet / create a custom snippet if adjustments are needed.

which ensures that the snippet overlays are processed after DTC_OVERLAY_FILE and OVERLAY_CONFIG.

and that is what I would argue that we don't want, because a user should be able to specify a common snippet and from there specify additional adjustments in a DTC_OVERLAY_FILE or more likely in an OVERLAY_CONFIG.
If snippets takes precedence over OVERLAY_CONFIG, then user must completely abandon the specific snippet / create a custom snippet if adjustments are needed.

There is no need for them to abandon the specific snippet; they just need to create an additional snippet with the extra configs to be applied on top of the existing snippet(s), which is not so much different from creating additional Kconfig and devicetree overlays.
Nevertheless, I can see that forcing users to use snippets for this purpose can be less than ideal.
What I need is to ensure that the prj.conf and app.overlay to get processed before the snippet overlays so that snippets can override the "application defaults" specified in those files.
For example, if app.overlay contains deleted-by-foo node, a snippet should be able to delete that deleted-by-foo node (which is part of the things that https://github.com/stephanosio/zephyr/commit/a21dcf66035b2cc303e3170184622d55b0d68cac tests).
That is currently not the case with the patches in this PR.

For example, if app.overlay contains deleted-by-foo node, a snippet should be able to delete that deleted-by-foo node (which is part of the things that stephanosio@a21dcf6 tests).

I agree with this.

If you read existing documentation, then applying DTC_OVERLAY_FILE will disable any automatic sourcing of overlay files.
See Set devicetree overlays.
This means that as soon that a snippet is used, and that snippet sets DTC_OVERLAY_FILE, then app.overlay is no longer sourced.
@stephanosio are you proposing to change that behavior ?
Because if you are, then that requires a more changes to our documentation as to when <board>.overlay / app.overlay are automatically sourced.
prj.conf (CONF_FILE) is a bit different, because prj.conf will only be replaced if CONF_FILE is specified, but snippets uses OVERLAY_CONFIG which is always used in combination with CONF_FILE and not replacing it.
prj.conf is always first in list, and therefore any OVERLAY_CONFIG will (regardless of scope) will have the ability to override settings in prj.conf
Ref: the initial configuration

(e.g. SNIPPET_DTC_OVERLAY_FILE and SNIPPET_OVERLAY_CONFIG) and they work independently of the DTC_OVERLAY_FILE and OVERLAY_CONFIG CMake variables
....
If we do that, snippets no longer need to comply with the documented behavioural characteristics of DTC_OVERLAY_FILE and OVERLAY_CONFIG (which is quite unnecessary, if I may add).

which give even more variations of how to configure the build system.
Also we need to careful describe how those settings behaves, and ensure they behave consistently.
The part I like wrt. current snippets implementation is that it works as an extension to current design and reuse same CMake variables names, meaning users are already custom to what those settings do.
Similar, it will be easier to allow other CMake variables to be set in snippets, in case we find need for that.
One thing, which has actually been raised before, we could consider, is to have a setting similar to OVERLAY_CONFIG.
Today we have:

CONF_FILE for config files

DTC_OVERLAY_FILE for dtc overlay, a setting which behavior is similar to CONF_FILE in the way it disable automatic sourcing.

CONFIG_OVERLAY for config files, where this setting is used in combination with CONF_FILE.

Devicetree overlays has no comparable setting to CONFIG_OVERLAY, so maybe it would be better to align how config files and overlay files works and can be specified.
This could be achieved by having a general setting for additional overlay files, similar to how we have CONFIG_OVERLAY for configs.
That would allow snippets to make use of such setting, and still ensure that what a snippet does can actually be done manually by hand.

This could be achieved by having a general setting for additional overlay files, similar to how we have CONFIG_OVERLAY for configs.
That would allow snippets to make use of such setting, and still ensure that what a snippet does can actually be done manually by hand.

The name OVERLAY_CONFIG sometimes causes confusion with DTC_OVERLAY_FILE, both in what they configure and how they behave.
Maybe a solution could be to deprecate OVERLAY_CONFIG and instead introduce EXTRA_CONF_FILE.
That way we could have:

DTC_OVERLAY_FILE, and EXTRA_DTC_OVERLAY_FILE
CONF_FILE, and EXTRA_CONF_FILE

which resembles what we have with ZEPHYR_MODULES, like

ZEPHYR_MODULES and ZEPHYR_EXTRA_MODULES (should then probably be renamed to EXTRA_ZEPHYR_MODULES.

this will bring more consistency to how build variables are named and used, as well as being more intuitive in how they behave.
<var-name> replaces any automatic / default assignment.
EXTRA_<var-name> extends <var-name> with extra configuration.

which give even more variations of how to configure the build system.

SNIPPET_DTC_OVERLAY_FILE and SNIPPET_OVERLAY_CONFIG (or whatever we decide to call them) will be internal to the build system, so introducing them should not result in any increased complexity from the user's perspective. From the build system's perspective, they provide more clarity since they establish a clear boundary between the snippet configs and the rest.

The part I like wrt. current snippets implementation is that it works as an extension to current design and reuse same CMake variables names, meaning users are already custom to what those settings do.

But that also results in conflicts with the existing infrastructure that utilise and modify these variables, as we have already seen.

Similar, it will be easier to allow other CMake variables to be set in snippets, in case we find need for that

But do we really want that behaviour? Doing so, once again, has a lot of potential for conflicts with the existing infrastructure and makes it difficult to clearly define and enforce the snippet-specific behaviours (e.g. some other module decides to touch the CMake variable and all hell breaks loose).
I am hoping to end up with something more self contained and well isolated from the rest of the build system parts so that I do not have worry about breaking something completely unrelated when I make changes to the snippet implementation (or vice versa); generally speaking, writing self contained modules and reducing the number of global variables that get both modified processed by multiple modules would be good practice (though, that does not seem to be a very common thing when it comes to CMake ....).

The name OVERLAY_CONFIG sometimes causes confusion with DTC_OVERLAY_FILE, both in what they configure and how they behave.
Maybe a solution could be to deprecate OVERLAY_CONFIG and instead introduce EXTRA_CONF_FILE.
That way we could have:

DTC_OVERLAY_FILE, and EXTRA_DTC_OVERLAY_FILE
CONF_FILE, and EXTRA_CONF_FILE

That does sound like a major improvement in terms of consistency, and I agree it would be good to implement that regardless of whether we decide to make the snippet implementation use them.
I still have concerns about the snippets directly modifying the global CMake variables though as mentioned in https://github.com/zephyrproject-rtos/zephyr/pull/57661#issuecomment-1542569796.

Also another open question is:

The part I like wrt. current snippets implementation is that it works as an extension to current design and reuse same CMake variables names, meaning users are already custom to what those settings do.

If we decide to go down this path, how would we go about the defconfig support (and even something like Kconfig.snippet if we ever decide it is necessary), which is not currently handled through any particular global CMake variables.
We could create an exception for defconfigs only and give it a special treatment; but, that would be an inconsistency.

should not result in any increased complexity from the user's perspective.

well, if we inside snippets call them OVERLAY_CONFIG, then they indicate they behave the same, which they suddenly may not do.
If we call them SNIPPETS_OVERLAY_CONFIG, then it's added complexity in their naming.

as we have already seen.

what we have seen is that we need a functionality similar to OVERLAY_CONFIG  but for devicetree overlays.
This is something we don't have today. If we were to provide such a feature only for snippets, then that would be introducing inconsistency in the form as yes, you can replace devicetree overlay from command line, but if you want to append to devicetree overlay you must create a snippet to do so.
Therefore such functionality should be available both for snippets but also generally.

But do we really want that behaviour?  Doing so, once again, has a lot of potential for conflicts with the existing infrastructure and makes it difficult to clearly define and enforce the snippet-specific behaviours

Do we want to create an infrastructure where such extensibility would not be possible ?
Notice how zephyr_get() allows us to control which scopes takes precedence, thus a CMake module which set FOO var in local scope will take lower precedence than the value defined in sysbuild, cache, or snippet scope.
With your current suggestion, you would end up in:

snippets before zephyr_get(), like:zephyr_get(FOO ...)
some_function(
  ${SNIPPETS_FOO}  # <-- Snippets version of FOO, not returned by zephyr_get in your proposal
  ${FOO}           # <-- The return result of zephyr_get(FOO)
)

snippets after zephyr_get(), like:zephyr_get(FOO ...)
some_function(
  ${FOO}           # <-- The return result of zephyr_get(FOO), not returned by zephyr_get in your proposal
  ${SNIPPETS_FOO}  # <-- Snippets version of FOO
)

This bears the risk that sometimes snippets var take precedence over the same var in other scopes, and sometimes it doesn't.
If the snippets var is scoped independently (as this PR proposes) then the value from snippets are part of zephyr_get() and we ensure that snippet defined values always takes the same precedence, compared to other scopes.

(e.g. some other module decides to touch the CMake variable and all hell breaks loose).

No other CMake module can touch the snippet variable, cause snippets variables and their values are scoped using a custom snippet target, and zephyr_get() controls which scopes takes precedence when returning the value(s).

and one more advantage with the zephyr_get() is that we can have a single location where order of precedence is described.

how would we go about the defconfig support (and even something like Kconfig.snippet if we ever decide it is necessary), which is not currently handled through any particular global CMake variables.

There is not necessarily a direct problem in certain functionality only available through snippets.
Just like Zephyr modules may provide extra information wrt. twister tests / samples available.
But we should of course careful consider if a functionality provided through snippets would make sense to have as a general functionality.
So for a defconfig / Kconfig.snippets we should definitely consider if such functionality should be more generally available.
An example where a more general functionality could make sense is Zephyr modules.
Currently all Zephyr modules Kconfigs are sourced through this:
https://github.com/zephyrproject-rtos/zephyr/blob/90d160e689a170a2324444660badcaf10c953e3b/Kconfig.zephyr#L37-L39
https://github.com/zephyrproject-rtos/zephyr/blob/7c228c90428f6635a2e3caed85c492677594746a/modules/Kconfig#L13
meaning all potential Zephyr module defconfigs are sourced as part of the Zephyr module's Kconfig.
But if we made the snippets defconfig more generic, then it could potentially be utilized by Zephyr modules, and that in return would allow us to split Zephyr modules defconfigs from rest of their Kconfig.
Currently our Zephyr module Kconfig tree would be very vulnerable if code snippets linked above would be moved around.

FTR I think the EXTRA_DTC_OVERLAY_FILE and EXTRA_CONF_FILE ideas make great sense and would be nice to get in before the release so we can move snippets over to them exclusively. Having snippet-specific versions of these variables seems unnecessary IMO as long as the order that snippets happen in is well defined (i.e. snippets append first, then CMake cache variables are appended on after would make sense to me).
Regarding Kconfigs/defconfigs, the reason I put the CMake variables under an append: was to be able to create sibling keys that would do things that have no direct CMake variables controlling them. Something like this:
name: foo
append:
  EXTRA_DTC_OVERLAY_FILE: my.overlay
defconfig: my_defconfig

Where we pick names like defconfig, etc. that should be reasonably self documenting about what their role is (and of course document them as well)
Thoughts?

FTR I think the EXTRA_DTC_OVERLAY_FILE and EXTRA_CONF_FILE ideas make great sense and would be nice to get in before the release so we can move snippets over to them exclusively. Having snippet-specific versions of these variables seems unnecessary IMO as long as the order that snippets happen in is well defined (i.e. snippets append first, then CMake cache variables are appended on after would make sense to me).

Based on https://github.com/zephyrproject-rtos/zephyr/pull/57661#issuecomment-1543501710, it sounds like at least the plan is to no longer allow modifying the global version of these variables in any module and only allow the scoped version for zephyr_get to be set -- if that is the plan and always going to be the case, then I have no problem with this approach; though, I still have my doubts about this policy being able to be consistently maintained, given that we have already seen the snippet implementation itself slip past that in spite of the zephyr_get infrastructure being already in place.
Anyway, it is the build system maintainer's call and I will make snippets use EXTRA_DTC_OVERLAY_FILE and EXTRA_CONF_FILE as discussed offline.

Regarding Kconfigs/defconfigs, the reason I put the CMake variables under an append: was to be able to create sibling keys that would do things that have no direct CMake variables controlling them. Something like this:
name: foo
append:
  EXTRA_DTC_OVERLAY_FILE: my.overlay
defconfig: my_defconfig

Where we pick names like defconfig, etc. that should be reasonably self documenting about what their role is (and of course document them as well)

While I see no technical problem with that, the first question that comes to my mind is: "Why are Kconfig overlays handled through a CMake variable under append while defconfigs are not? What makes Kconfig overlays (or defconfigs, depending on how you look at it) special?"
For example:
name: foo
append:
  I_AM_A_CMAKE_VAR: asdf
  ME_TOO: ghjk
  OVERLAY_CONFIG: my.conf
  YET_ANOTHER_CMAKE_VAR: zxcv
defconfig: my.defconfig

versus
name: foo
cmake_vars:
  I_AM_A_CMAKE_VAR: asdf
  YOU_GET_THE_IDEA: ghjk
config_overlays:
- a.conf
- b.conf
defconfigs:
- x.defconfig
- y.defconfig

I would say the latter looks more consistent and complete (as in that it does not expose the "under-the-hood" details like setting the CMake variables to specify the Kconfig overlays for the build system).

I would say the latter looks more consistent and complete (as in that it does not expose the "under-the-hood" details like setting the CMake variables to specify the Kconfig overlays for the build system).

The reason I didn't do it that way is because I think it is more self-documenting if the snippet file format explicitly mentions the build system variables that users are likely to be familiar with already.

Based on https://github.com/zephyrproject-rtos/zephyr/pull/57661#issuecomment-1543501710, it sounds like at least the plan is to no longer allow modifying the global version of these variables in any module and only allow the scoped version for zephyr_get to be set

Technically CMake doesn't have global scope variables, it has current scope and cache variables, but a variable set at the highest scope is available in all scopes below (although changes to the variable in child scopes will not affect (grand)-parent scopes).
(Though it is possible to adjust the immediate parent scope)
Current scope adjustment of variables will still be allowed, like here:
https://github.com/zephyrproject-rtos/zephyr/blob/2f718dd369e41a9ae50fb613ac29d8ce192da440/cmake/modules/zephyr_module.cmake#L81-L88
where Zephyr module defined settings are added in current scope, but settings added there will take lowest precedence.
We want the ability of defining the exact precedence for snippets, and therefore we need dedicated handling.
In case we wanted dedicated precedence handling of settings originating from Zephyr modules, then we should also create a dedicated scope for those.

@stephanosio and @mbolivar-nordic PR has been updated.
I added a new commit to support EXTRA_CONF_FILE and EXTRA_DTC_OVERLAY_FILE as #57994 has been merged.
For time being I kept support for DTC_OVERLAY_FILE and OVERLAY_CONFIG, but as the snippets feature is very new and has not yet been part of a release then I actually considered to remove support for DTC_OVERLAY_FILE  and OVERLAY_CONFIG completely in snippets and avoid any confusion and need of deprecation later.
Any thoughts / comments on this ?

For time being I kept support for DTC_OVERLAY_FILE and OVERLAY_CONFIG, but as the snippets feature is very new and has not yet been part of a release then I actually considered to remove support for DTC_OVERLAY_FILE and OVERLAY_CONFIG completely in snippets and avoid any confusion and need of deprecation later.
Any thoughts / comments on this ?

Discussed offline with @mbolivar-nordic and have removed support for DTC_OVERLAY_FILE and OVERLAY_CONFIG in snippets.


Add configuration support for system access control plugin

Is the Travis failure related? It says something about kerberos realms


Cardputer not starting

Hi,
I wonder why my previous issue has disappeared...
v.1.3 worked fine by copying OTA main bin and starting with M5Launcher
v.1.3.5 comes with black screen.
Any ideas?

I see, you're busy....reverting...?

I see, you're busy....reverting...?

it's called development


thermocycler: raise NotImplementedError when ramp_rate is passed to set_temperature()

We have yet to implement thermocycler ramp rate control using the api/ external commands (See #2953). The ramp rate right now is fixed in firmware and cannot be changed. The firmware ignores any SET_RAMP_RATE gcode calls. This should be reflected in the API (and docs) by making set_block_temperature raise a NotImplementedError when ramp_rate param is passed.

Moved to jira


Set working directory

Hello,
I am trying to find a way to set the work directory of the lua state so that calling do_file always looks in that specific directory and not the location of the executable.
What is the proper way of handling this?
Best,
Max

The working directory is the C working directory. That is, it is the working directory of the program. You need to use platform APIs to change this: sol2 doesn't have this. The C++ standard with std::filesystem does: https://en.cppreference.com/w/cpp/filesystem/current_path
Be warned that it changes it for the whole directory. There is no "changing it for the Lua State".


Manifest file is missing or unreadable. Could not load manifest.

Describe the bug
Followed steps, but got this error:
Error
Manifest file is missing or unreadable
Could not load manifest.

To Reproduce
Steps to reproduce the behavior:
Just follow steps to install
Expected behavior
Extension to be installed
Screenshots

Desktop (please complete the following information):

OS: Sonoma 14.5
Browser Chrome
Version  125.0.6422.142 (Official Build) (arm64)

@gonzaloamadio
I think you missed the last step....the chrome and firefox have their dedicated folder now.
Install manually

Download this repo as a ZIP file from GitHub.
Unzip the file and you should have a folder named medium-parser-extension-main.
In Chrome/Edge go to the extensions page (chrome://extensions or edge://extensions).
Enable Developer Mode by clicking the toggle button on the top right side of the browser.
Drag the chrome folder anywhere on the page to import it (do not delete the folder afterward).

Or you can just install from the dev store
https://chromewebstore.google.com/detail/medium-parser/bdkfodcnmgegolifeafnpbgjnjfohado
https://addons.mozilla.org/en-US/firefox/addon/medium-parser/

Ah nice, I drag the chrome folder and looks ok


Escape all the shell things!

https://twitter.com/asgrim/status/620474794685898752

:D

@asgrim: how about something like this?
https://github.com/asyncphp/doorman/blob/cff6addf82e98ec926cfb0d7e1c7d9b6fa53d2f4/src/Shell/BashShell.php#L19-L27
Uses:
https://github.com/asyncphp/doorman/blob/cff6addf82e98ec926cfb0d7e1c7d9b6fa53d2f4/src/Manager/ProcessManager.php#L145-L147
https://github.com/asyncphp/doorman/blob/cff6addf82e98ec926cfb0d7e1c7d9b6fa53d2f4/src/Manager/ProcessManager.php#L228-L230

That's the spirit! :)


WIP: auto detect and handle mixed mode endpoints (dns & IPs)

This PR is incomplete. It also has a small bugfix in workload instance handling that
should be split off into a separate PR.
The motivation for this PR is to automatically detect whether a service is
made up of all IPs, or all DNS or mix of both. If its a mix, the goal is to be able to
generate AggregateClusters for such services. If we pull this off, we will no longer need
the resolution field (except NONE), and we can fully allow a service entry with DNS select
k8s pods, and a k8s service select dns based workload entries.
The brute force way of accomplishing this is to iterate though all services, get their
InstancesByPort, check for homogeneity and setup the appropriate cluster. Not sure what
the performance impact of this will be but it is worth having a baseline to compare against.
I think we might have to do this in bits and pieces, and gradually evolve the system towards this goal.
cc @ramaraochavali, @howardjohn, @hzxuzhonghu
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@rshriram: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test release-notes_istio

gencheck_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test release-notes_istio

gencheck_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test gencheck_istio

lint_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test release-notes_istio

gencheck_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test gencheck_istio

lint_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test lint_istio

unit-tests_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test release-notes_istio

gencheck_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test gencheck_istio

lint_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test lint_istio

unit-tests_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
555b669c42b488a01e9226f2be818dc395cc239f
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Flex bison llvm implementation

New lexer and parser implementation using Flex/Bison and new AST structure with LLVM code generation

Thank you for your contribution!


Can this job be used for video classification？

I want to use it for multimodal video classification tasks. What should I do？

Hi, we released the model code in here. Full fine-tuning code on video classification will be released on the weekend.
If you mean the clip-style multimodal video classification tasks, it is beyond the scope of this paper.


Outline panel: method body after : is considered return type

For example, a function with no return type, only a :, leads to the outline panel displaying the entire method body as the return type of the method. This is a bit annoying / confusing while typing out code.

I think it's possible for the parser to tell that this isn't a typedef  return.
I'm fairly confident this didn't used to happen, however it does happen on the master branch.

You sure this worked before? As you say, it's already broken in the latest official release, but If this ever worked right, by looking at the repository history, it was like 2 years ago, so...
Yes, the parser could handle it, when we are in a type declaration and we have at least one bracket, if we find symbols like .;, or ( when not in a subtype, we can "stop" the parser. But it would be nice to see the Haxe parser logic completely separate from the other languages so it can be made cleaner, and I also have some additional ideas for the future.

I think your recent parser changes made the support for "anonymous" types a lot more loose which creates this situation.
That's why originally I was cancelling the type when finding ; for instance.
Another possibility would be to drop the type if there's a newline between : and the first {.

No, this already happened before my changes.

And lastly, I only changed ; when in generics, because you can have them in there in Haxe, but admittedly only in generic constraints, not any generic case.

Ah ok.
Yes it is technically valid syntax, but that's a syntax error we need to recover from it somehow.

Yes, I agree completely, but using new line to stop the parser wouldn't be the proper way, we add support for a wrong syntax case but break many valid syntax cases :P.
I'd love to see that parser separation, it will be helpful for everyone and will ease adding new cases.

We're talking mostly about the outline view, it wouldn't break so many cases in practice. Plus I really don't see how it could be really used in real life.

I'd say it's more serious than that. Of course it's not immediately visible because of the compiler service, but It means the model we have in memory is also wrong, so who knows how it may affect in some cases like refactoring, code generation, etc.
But yes, I'd mark this as low priority.

I'd say it's more problematic to use the function body as anonymous :)


Remove horizontal overflow and change layout of cards

Issue Type:

[x] Bug Report

Describe the bug

A clear and concise description of what the bug is.
There is horizontal scrolling which does not look good. Also, the cards are not centred and there is lot of wasted space.

Possible solution

Describe the solution you thought of.
I plan to use CSS Grid to create a dynamic grid system so that cards automatically arrange themselves without the use of media queries.

Screenshots

If applicable, add screenshots to help explain your problem.
.

I am a GSSOC 22 contributor. Please assign this issue to me

@Adhetya u have opened this issue in wrong repo

@DEEPALI-SUK, which repository should I create this issue in ?


where can I download AirSDK old version.

Hello,
I'm looking for Adobe AIR SDK old version, but the link page was closed. (Only 32.0 version is opened .)
http://airdownload.adobe.com/air/win/download/32.0/AdobeAIRSDK.zip (O)
http://airdownload.adobe.com/air/win/download/22.0/AdobeAIRSDK.zip (X)
I've googled for 2 days. There is no way to find a old version.
Please let me know how to get it. You can be my hero. :)
Thanks in advanced.
Kevin.

Probably a better question for the AIR discussion forum:
https://github.com/airsdk/Adobe-Runtime-Support/discussions
We don't have a license from Adobe to distribute old versions through this site.


Forward-port improvements in terraform-dev from version/5.5.x

In the master branch, terraform-dev is unusable because there is a problem with DNS. I fixed that in 5.5.x a while ago, just need to forward-port.

I'd like to review this PR, as I'm getting to know a lot more about terraform. However, without knowing where the changes came from (e.g. which PR or commit they were ported from) or why they were made, I don't know that I can give constructive feedback.
git cherry-pick -x will leave a paper trail of where a commit came from. This becomes increasingly important in an org with lots of ports.  Unfortunately, git tracks diffs/ports terribly compared to other VCS where diffs are first class citizens.

Improvements are splitted in a few PR requests. Let me provide a better description here instead of pointing to previsous PR without any description.


Cannot open procrastinate application in an async application

We have a fast-api ASGI web application and are trying to use procrastinate as our Postgres-based task/queue management system.
I attempt to App.open() our procrastinate app so that I can e.g. some_task.defer() - however I am getting an error that the event loop is already running (not terribly surprising since that's what fast-api runs on):
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
INFO:     Started reloader process [1] using watchgod
INFO:     Started server process [9]
INFO:     Waiting for application startup.
ERROR:    Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 526, in lifespan
    async for item in self.lifespan_context(app):
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 467, in default_lifespan
    await self.startup()
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 502, in startup
    await handler()
  File "/cloud-app/./app/main.py", line 43, in startup
    procrastinate_app.open()
  File "/usr/local/lib/python3.9/site-packages/procrastinate/app.py", line 330, in open
    self.connector.open(pool)
  File "/usr/local/lib/python3.9/site-packages/procrastinate/utils.py", line 118, in wrapper
    return sync_await(awaitable=awaitable)
  File "/usr/local/lib/python3.9/site-packages/procrastinate/utils.py", line 168, in sync_await
    return loop.run_until_complete(awaitable)
  File "uvloop/loop.pyx", line 1495, in uvloop.loop.Loop.run_until_complete
  File "uvloop/loop.pyx", line 1488, in uvloop.loop.Loop.run_until_complete
  File "uvloop/loop.pyx", line 1377, in uvloop.loop.Loop.run_forever
  File "uvloop/loop.pyx", line 511, in uvloop.loop.Loop._run
RuntimeError: this event loop is already running.

We have separate processes (containers) for fast-api vs. procrastinate workers, but our fast-api container does seem to need to call App.open() in order to defer tasks to the queue, to ultimately be picked up by the worker(s).
Is my understanding correct?
UPDATE: It seems like this may be what App.open_async() is for; trying this now.

@mecampbellsoup please read https://procrastinate.readthedocs.io/en/latest/howto/open_connection.html. I am going to close this, but feel free to reopen if you still have problems.

@elemoine yes, thank you! I got this sorted out for the most part.
Now I'm trying to figure out how to launch my worker process with the ability to run some arbitrary code (e.g. my task definitions depend on a separate DB connection/interface than what procrastinate itself uses, so I need to await database.connect() so that my task implementations can run).
Is there any way to combine the CLI invocation procrastinate worker --app=... with something like this:
from procrastinate import AiopgConnector, App

from app.settings import database, DATABASE_URL

app = App(
    connector=AiopgConnector(dsn=DATABASE_URL),
    import_paths=['app.reconciler'],
)

async def main():
    async with app.open_async():
        await database.connect()
        # Only needed if running the worker not via CLI invocation (just normal Python script)
        await app.run_worker_async(
            delete_jobs='successful',
        )

Also FYI I cannot reopen the issue (if you think that is necessary I will just open a new issue).

@elemoine https://github.com/peopledoc/procrastinate/issues/438 👍


[QUESTION] Granular Access?

Hi, Love Dashy!
I searched through the docs,,, I might be blind though. Is there a way to give granular access to users?
Such as some users see some "bookmarks" but not others?
Regards,
Lue-

Hey, thanks for your question, at the moment, no is not yet possible. But it's a good idea, so I will add it to the todo list. Just so I understand, you'd like it to be possible have some sections only visible to specific users, right? I think that should be pretty straigtforward :)

Hi,
If possible, individual "bookmarks" and sections?
I am personally used to how rmountjoy92/DashMachine (unmaintained now) worked.
See below where two users, two roles , two groups and two "bookmarks" are define.
Obviously if you can/want implement it, do it however you see fit!

Regards,
Lue-

Heya, I've implemented this in PR #171 :)

You under displayDaya for a given section, you can now use the following properties to control the sections visibility on a per-user basis.

hideForUsers - Section will be visible to all users, except for those specified in this list
showForUsers - Section will be hidden from all users, except for those specified in this list
hideForGuests - Section will be visible for logged in users, but not for guests

Examples

- name: Code Analysis & Monitoring
  icon: fas fa-code
  displayData:
    cols: 2
    hideForUsers: [alicia, bob]
  items:
    ...

- name: Deployment Pipelines
  icon: fas fa-rocket
  displayData:
    hideForGuests: true
  items:
    ...

Hope that helps :)


[KAOS-1344] Force icons download on any changes

I abandoned my idea with many layers (a single category - a single layer).
Now I just try to force icon downloading and processing on any data changes.
cc @Vandalko @roman-mazur
https://keyprprojects.atlassian.net/browse/KAOS-1344

But now sasha/dev branch is used in a project

in theory, any "good" changes should be returned back to original repo, but in reality, they are not very eager at merging any structural changes https://github.com/googlemaps/android-maps-utils/pulls/Vandalko


fix(connectivity_plus): Downgrade js version to work with Flutter 3.3.10

Description
Made the plugin use older js version as there were issues with compatibility for older Flutter versions as reported in #1960
Related Issues
Fixes #1960
Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

Yes, I also believe that we can relax constraints a bit. Suggest to not make any special changes now, but for moving forward keep an eye on new available dependencies and evaluate if changes/fixes in any of them worths bumping the min version that we allow to use in plugins.

What do you think about ignoring patch releases in dependabot.yml?
If it's a version >= 1.0.0, ignoring minor bumps could also make sense.

Looks cool. Yes, might be indeed useful for plugins. Thanks for sharing.


Use a smaller model to speed up the prediction time

Hello BLINK team,
I have tested the code and it works wonderfully. However, I am noticing that the tutorial only shows a large model and with massive entities.
config = {
"test_entities": None,
"test_mentions": None,
"interactive": False,
"top_k": 10,
"biencoder_model": models_path+"biencoder_wiki_large.bin",
"biencoder_config": models_path+"biencoder_wiki_large.json",
"entity_catalogue": models_path+"entity.jsonl",
"entity_encoding": models_path+"all_entities_large.t7",
"crossencoder_model": models_path+"crossencoder_wiki_large.bin",
"crossencoder_config": models_path+"crossencoder_wiki_large.json",
"fast": True, # set this to be true if speed is a concern
"output_path": "logs/" # logging directory
}
Is there a smaller pre-trained model on entity encoding that I can use to speed up the prediction? I am ok to sacrifice some performance. If it's not available, is there anything at all I could do to speed this up?
Thank you

I have created a repository for data generation and training of bi-encoder models (so far, only for entity-linking) based on the BLINK model. In it, you can choose which bert base model to use to make your evaluation faster :). As I remember using a bert-mini I could get R@64 of 84% on zeshel dataset.*
But no cross-encoder was implemented, so, you can make only faster the bi-encoder part.

@Giovani-Merlin Is that repo still active? The link is now dead.

If you have your own training data, it's not hard to modify the code slightly to use the latest and smaller HuggingFace BERT models (such as BERT mini or google/bert_uncased_L-8_H-512_A-8) for training biencoder.
You'll need to change how the base model is loaded (use HuggingFace's AutoModel and  AutoTokenizer classes) and how the tokenized input is fed to the model (input_ids, token_type_ids and attention_mask).


ARRAY module in UIUC K

Please add tests.

What should the semantics of makeArray(5, 0)[7] be? That is, should it return the default value 0, or some error term because 7 it outside the bounds of the array?

makeArray(5, 0)[7] and makeArray(5, 0)[7 <- 1][7] should both be zero. The idea behind ARRAY is that an efficient implementation backs an array as an actual array with a fixed length, so any element not explicitly assigned or outside the length of the array is always equal to the default value.

As @dwightguth pointed out I missed that we only support one test definition per directory, so making a subdirectory for the tests previously directly in test/builtins is a good idea before making test/builtins/array.


sql_lab had something bug?

in lab_sql tool ,the page will go wrong when i click run query.of course i use chinese.----SELECT *
FROM zhkt_valid_active
WHERE  city ='合肥市'----

Not sure if we saw the same problem, to me seem when using alt+enter it works, but clicking the query botton it gaves some connection refused error...

tks, @verydxz  the same problem and solved by your method.
is it a bug?

Notice: this issue has been closed because it has been inactive for 370 days. Feel free to comment and request for this issue to be reopened.


Vulnerability discovered in Lemur

Dear Lemur community,
On February 20, 2023, an independent researcher disclosed a vulnerability identified in Lemur’s codebase. At a high level, the vulnerability may result in certain Lemur configuration options being insecure.
Presently, we have no reason to believe that these vulnerabilities have been exploited.
We have already prepared the patches to fix this vulnerability, and will raise a PR to Lemur’s GitHub repository on the morning of Tuesday, February 28 2023 PST. On the same day, we will release a new version of Lemur (1.3.2) which will contain the patch. We recommend that all Lemur users upgrade immediately after version 1.3.2 has been released. Users may also need to update some configuration options for their Lemur deployments. We will disclose additional details regarding the vulnerabilities following the updated release of Lemur in the form of a GitHub security advisory.
Thanks,
Lemur Team

Resolved via 666d853

Link to https://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2023-001.md


codeunit 87 "Blanket Sales Order to Order" change OnBeforeInsertSalesOrderHeader

can the variable SalesQuoteHeader in OnBeforeInsertSalesOrderHeader made var?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Enable CancellationToken support and Split Storage client to Sync and Async.

CancellationToken:

Async and Sync clients:
async client

sync client

@tjprescott FYI

/azp run android - storage - ci


Fixed link to open.xamarin.com

The URL https://open.xamarin.com fails to open due to an invalid certificate, the HTTP URL is fine, so use that instead.

@migueldeicaza, is this known on your end?

@cartermp According to @akoeplinger (on gitter), it's not fixable right now.

That's correct, GitHub Pages (where the site is hosted) doesn't support SSL for custom domains yet.

Gotcha.  LGTM then.  Thanks!


IPedVariation ComponentType / PropType

Adjusted Ped.Style IPedVariation to contain reference to ComponentType / PropType for automated processing.
Added PedComponents ComponentType / PedProps PropType for ease.

Is there an issue with this one ?
Is there is another way of retrieving a relevant name reference for an IPedVariation ?
public IPedVariation[] GetAllVariations()

@Tanjitsu Sorry, but you have to resolve conflicts before we can merge this pull request.


Consistent "az storage account management-policy" FAILURE

Description
Command Name
az storage account management-policy create
Errors:
Parameter 'ManagementPolicySchema.rules' can not be None.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az storage account management-policy create --account-name MyStorageAcc --resource-group MyResourceGroup --policy .\policy.json

Expected Behavior
I expect it to parse the json and create the policy but it consistently fails. I even tried in the cloudshell cli in the portal and it does the exact same thing.
Environment Summary
Windows-10-10.0.22000-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.31.0 *

Extensions:
azure-devops 0.23.0
interactive 0.4.5

Additional Context
The json in the "policy.json" is as follows:
{
"id": "/subscriptions/some_GUID_Here/resourceGroups/MyResourceGroup/providers/Microsoft.Storage/storageAccounts/MyStorageAccount/managementPolicies/default",
"lastModifiedTime": "2022-06-06T15:07:53.922968+00:00",
"name": "DefaultManagementPolicy",
"resourceGroup": "MyResourceGroup",
"type": "Microsoft.Storage/storageAccounts/managementPolicies",
"policy": {
"rules": [
{
"definition": {
"actions": {
"baseBlob": {
"delete": {
"daysAfterLastAccessTimeGreaterThan": null,
"daysAfterModificationGreaterThan": 7.0
},
"enableAutoTierToHotFromCool": null,
"tierToArchive": null,
"tierToCool": null
},
"snapshot": null,
"version": null
},
"filters": {
"blobIndexMatch": null,
"blobTypes": [
"blockBlob"
],
"prefixMatch": [
"adxstudioportals/"
]
}
},
"enabled": true,
"name": "MyPolicyName",
"type": "Lifecycle"
}
]
}
}

storage

The policy format is wrong. See https://docs.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview#lifecycle-management-policy-definition


Switch to less-diverged branch of ECR scan plugin

Context
Update our ECS scanning Buildkite plugin to a version that's closer to upstream:
Depends on https://github.com/buildkite/ecr-scan-results-buildkite-plugin/pull/11

Switch to updated plugin (closer to upstream)
Change format of ignore list, because upstream's parallel implementation is slightly different to ours
Add fail-build-on-plugin-failure flag, to preserve our current plugin behaviour

Hi @duckalini , this looks fine to, but as I'm not expert, I'll wait for someone in Platform to review this first.
Otherwise, if you have trouble getting this review, let me know—I can then approve it so you can merge this in.


Add the ability to pipe stdin to GtNativeExternalProcessChild

Currently only stdout and stderr can be piped to the image.

Solved by https://github.com/feenkcom/gtoolkit/issues/3053


[YUNIKORN-1513] Adding Chinese translation of Development in CodeReady Containers

What is this PR for?
Adding Chinese translation of Development in CodeReady Containers
What type of PR is it?

[ ] - Bug Fix
[ ] - Improvement
[ ] - Feature
[x] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/YUNIKORN-1513/

How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

My pull request #309 in wrong place.
But pull request #310 document I put at i18n/zh-cn/docusaurus-plugin-content-docs/current/developer_guide/openshift_development.md.
It is in the docusaurus-plugin-content-docs/current
Could you review again?


Implement openebs charts in K8s charts repo

This issue tracks the implementation of openebs charts in https://github.com/kubernetes/charts/tree/master/stable
(a) core openebs as one chart -- enabling service accounts, m-apiserver, provisioner, crd, default sc and policies
(b) additional openebs charts for loading of customized policies and storage classes ?
Above charts just expose .. StorageClasses .. that can in turn be used by application charts (by pointing to a StorageClass)
One may refer to https://github.com/openebs/openebs/tree/master/k8s/demo for reference

It should definitely have these sanity tests configured as well:
https://github.com/kubernetes/helm/blob/master/docs/chart_tests.md

Raised a PR against kubernetes/charts. https://github.com/kubernetes/charts/pull/3879


Support for datetimeoffset?

Querying a table with a datetimeoffset field gives an error: 'Column type not supported'.
Also tested directly with :odbc, error persists:
{:ok, pid} = :odbc.connect(connect_string, [])
{:ok, #PID<0.221.0>}
:odbc.sql_query(pid, 'select date_in from test_table')
{:error, 'Column type not supported'}

Is it really :odbc.sql_query that does not support datetimeoffset?

Thanks for bringing this to our attention @fpauser. We will investigate further, but I would not be surprised if this column type is not supported by the Erlang ODBC library.
More about datetimeoffset:

Defines a date that is combined with a time of a day that has time zone awareness and is based on a 24-hour clock.

More info on the type on Microsoft Docs.

Seems like odbc-support for current sqlserver features is quite limited. Not being able to query datetimeoffset columns is a showstopper for me.

Yeah, the Erland ODBC application has very limited support for non-standard column types. You would need to either patch Erlang OTP or write your own driver to use instead of ODBC. The latter is what https://github.com/livehelpnow/tds tried but that project hasn't been maintained in a long time, which speaks to the complexity of the task.
We unfortunately have no plans to undertake either of these pieces of work but we'll gladly cooperate with anyone who is willing to do so.

I have opened up this issue on the Erlang/OTP bug board. Will try and fix it myself hopefully with a bit of guidance from the OTP maintainers.

C Data Type Struct for datetimeoffset: https://docs.microsoft.com/en-us/sql/relational-databases/native-client-odbc-date-time/data-type-support-for-odbc-date-and-time-improvements

hi, i just stumbled upon this issue. FIY, datetimeoffset not supported on python odbc driver either so it's probably not erlang specific :)


Hard to find new comments

Unread comments no longer appear at the top. If this is an intentional change it would be really nice to implement an alternate way to see new unread comments.

I think:

Highlight unread comments
Have a "sort by latest response" option

@aseckin I know you've explored this some, thoughts?

Currently in eng review: https://github.com/Metaculus/metaculus/pull/1232


Fix ldap filters

Category

Bugfix and feature

Overview

Fix ldap search filter attribute (Hardcoded even though env variable for it where already present, must have been forgotten)
Add ldap search extra arguments (for both user search and group search)
Add log points to better help the user understand which step is not working.

Issue Number

Discord report

New Vars

AUTH_LDAP_USERNAME_ATTRIBUTE : (Not new but actually implemented now) Attribute to designate the username
AUTH_LDAP_USER_MAIL_ATTRIBUTE : Attribute to designate email field (Email being obligatory, we need to be accomodating)
AUTH_LDAP_USERNAME_FILTER_EXTRA_ARG : Extra argument for the user search field
AUTH_LDAP_GROUP_FILTER_EXTRA_ARG : Extra argument for the user's groups field

lgtm, is documentation updated or ready for update?

https://github.com/homarr-labs/documentation/pull/70
It should have everything for this PR and #2023.
Latest of the latest commits are bugfixes/behavior improvements so I don't thinks there's a need to change it.
It also includes documentation for other ldap/oidc env var that were added in older PR's.


Addressing jsPsych references

We're trying to avoid plugins needing to reference jsPsych directly. This is being done by changing various things in plugin.info from objects to strings, and then having plugin.trial include jsPsych as an argument.
For instance, compare the original html-keyboard-response to the new one.
However, some plugins use 'jsPsych.gluginAPI.registerPreload' outside of the plugin.trial() function. We don't have a good work-around yet.

Put this on the wrong repo.


add MCP server badge

This PR adds a badge for the @kazuph/mcp-obsidian server listing in Glama MCP server directory.

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected
Confirm that there are no obvious security issues with dependencies of the server
Extract server characteristics such as tools, resources, prompts, and required parameters.

This badge helps your users to quickly asses that the MCP server is safe, server capabilities, and instructions for installing the server.

realized the project is missing a license
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
Would you mind adding one?
We will automatically pick up the change (we scan every repo every 6 hours)


Unavailable battery sensor

Is there an existing issue for this?

[X] I have searched both the existing open issues & recently closed issues and did not find a duplicate of this issue.

I have read about the Fleet API and understand I may need to use it

[X] I understand issues relating to read only commands will be auto closed if not using the Fleet API.

Version of the Tesla component
3.23.0
Version of the Tesla car software
2024.14.9
Model
Model 3
Current Behavior
Since several days the battery sensor is only occasionaly available.
I cannot say if it's linked to a version update.
Gaps found in history:

08/06/2024 from 09.21 to 14.06 CET
since 09/06/2024 10.35, but reappeard between 15.00.00 and 15.36.42

Expected Behavior
Battery sensor to appear and remain there.
Debug logs
2024-06-10 17:50:31.743 DEBUG (MainThread) [custom_components.tesla_custom.teslamate] Got car ID. VIN:LRW3XXXXXXXXXXXX7 TeslamateID: None
2024-06-10 17:50:31.998 DEBUG (MainThread) [teslajsonpy.connection] 200: {"response":{"id":XXXXXXXXXXXX,"user_id":XXXXXXXXXXXX,"vehicle_id":16XXXXXXXXXXXX42,"vin":"LRW3XXXXXXXXXXXX7","color":null,"access_type":"OWNER","granular_access":{"hide_private":false},"tokens":["XXXXXXXXXXXX","XXXXXXXXXXXX"],"state":"online","in_service":false,"id_s":"XXXXXXXXXXXX","calendar_enabled":true,"api_version":76,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"charge_state":{"battery_heater_on":false,"battery_level":64,"battery_range":216.57,"charge_amps":9,"charge_current_request":9,"charge_current_request_max":28,"charge_enable_request":false,"charge_energy_added":0.39,"charge_limit_soc":80,"charge_limit_soc_max":100,"charge_limit_soc_min":50,"charge_limit_soc_std":80,"charge_miles_added_ideal":1.5,"charge_miles_added_rated":1.5,"charge_port_cold_weather_mode":false,"charge_port_color":"\u003cinvalid\u003e","charge_port_door_open":true,"charge_port_latch":"Engaged","charge_rate":0.0,"charger_actual_current":0,"charger_phases":3,"charger_pilot_current":28,"charger_power":0,"charger_voltage":3,"charging_state":"Stopped","conn_charge_cable":"IEC","est_battery_range":228.9,"fast_charger_brand":"\u003cinvalid\u003e","fast_charger_present":false,"fast_charger_type":"ACSingleWireCAN","ideal_battery_range":216.57,"max_range_charge_counter":0,"minutes_to_full_charge":0,"not_enough_power_to_heat":null,"off_peak_charging_enabled":false,"off_peak_charging_times":"all_week","off_peak_hours_end_time":360,"preconditioning_enabled":false,"preconditioning_times":"all_week","scheduled_charging_mode":"Off","scheduled_charging_pending":false,"scheduled_charging_start_time":null,"scheduled_charging_start_time_app":0,"scheduled_departure_time":1714540500,"scheduled_departure_time_minutes":435,"supercharger_session_trip_planner":false,"time_to_full_charge":0.0,"timestamp":1718034631944,"trip_charging":false,"usable_battery_level":63,"user_charge_enable_request":false},"climate_state":{"allow_cabin_overheat_protection":true,"auto_seat_climate_left":true,"auto_seat_climate_right":true,"auto_steering_wheel_heat":true,"battery_heater":false,"battery_heater_no_power":null,"cabin_overheat_protection":"FanOnly","cabin_overheat_protection_actively_cooling":false,"climate_keeper_mode":"off","cop_activation_temperature":"High","defrost_mode":0,"driver_temp_setting":20.0,"fan_status":0,"hvac_auto_request":"On","inside_temp":19.8,"is_auto_conditioning_on":false,"is_climate_on":false,"is_front_defroster_on":false,"is_preconditioning":false,"is_rear_defroster_on":false,"left_temp_direction":0,"max_avail_temp":28.0,"min_avail_temp":15.0,"outside_temp":13.0,"passenger_temp_setting":20.0,"remote_heater_control_enabled":false,"right_temp_direction":0,"seat_fan_front_left":0,"seat_fan_front_right":0,"seat_heater_left":0,"seat_heater_rear_left":0,"seat_heater_rear_right":0,"seat_heater_right":0,"side_mirror_heaters":false,"steering_wheel_heat_level":0,"steering_wheel_heater":false,"supports_fan_only_cabin_overheat_protection":true,"timestamp":1718034631944,"wiper_blade_heater":false},"drive_state":{"gps_as_of":1718034101,"heading":184,"latitude":XXXXXXXXXXXX.032789,"longitude":XXXXXXXXXXXX.805321,"native_latitude":XXXXXXXXXXXX.032789,"native_location_supported":1,"native_longitude":XXXXXXXXXXXX.805321,"native_type":"wgs","power":0,"shift_state":"P","speed":0,"timestamp":1718034631944},"gui_settings":{"gui_24_hour_time":true,"gui_charge_rate_units":"km/hr","gui_distance_units":"km/hr","gui_range_display":"Rated","gui_temperature_units":"C","gui_tirepressure_units":"Bar","show_range_units":false,"timestamp":1718034631944},"vehicle_config":{"aux_park_lamps":"None","badge_version":1,"can_accept_navigation_requests":true,"can_actuate_trunks":true,"car_special_type":"base","car_type":"model3","charge_port_type":"CCS","cop_user_set_temp_supported":true,"dashcam_clip_save_supported":true,"default_charge_to_max":false,"driver_assist":"TeslaAP4","ece_restrictions":true,"efficiency_package":"XXXXXXXXXXXX","eu_vehicle":true,"exterior_color":"XXXXXXXXXXXX","exterior_trim":"Black","exterior_trim_override":"","has_air_suspension":false,"has_ludicrous_mode":false,"has_seat_cooling":true,"headlamp_type":"Global","interior_trim_type":"Black2","key_version":2,"motorized_charge_port":true,"paint_color_override":"0,3,80,0.9,0.01","performance_package":"Base","plg":true,"pws":true,"rear_drive_unit":"XXXXXXXXXXXX","rear_seat_heaters":1,"rear_seat_type":0,"rhd":false,"roof_color":"RoofColorGlass","seat_type":null,"sentry_preview_supported":false,"spoiler_type":"None","sun_roof_installed":null,"supports_qr_pairing":false,"third_row_seats":"None","timestamp":1718034631944,"trim_badging":"74d","use_range_badging":true,"utc_offset":7200,"webcam_selfie_supported":true,"webcam_supported":true,"wheel_type":"Glider18"},"vehicle_state":{"api_version":76,"autopark_state_v2":"unavailable","calendar_supported":true,"car_version":"2024.14.9 0b82f700aebe","center_display_state":0,"dashcam_clip_save_available":true,"dashcam_state":"Recording","df":0,"dr":0,"fd_window":0,"feature_bitmask":"XXXXXXXXXXXX,XXXXXXXXXXXX","fp_window":0,"ft":0,"is_user_present":false,"locked":true,"media_info":{"audio_volume":1.3333,"audio_volume_increment":0.333333,"audio_volume_max":10.333333,"media_playback_status":"Playing","now_playing_album":"","now_playing_artist":"","now_playing_duration":196000,"now_playing_elapsed":140000,"now_playing_source":"Spotify","now_playing_station":"","now_playing_title":""},"media_state":{"remote_control_enabled":true},"notifications_supported":true,"odometer":XXXXXXXXXXXX.441443,"parsed_calendar_supported":true,"pf":0,"pr":0,"rd_window":0,"remote_start":false,"remote_start_enabled":true,"remote_start_supported":true,"rp_window":0,"rt":0,"santa_mode":0,"sentry_mode":false,"sentry_mode_available":true,"service_mode":false,"service_mode_plus":false,"software_update":{"download_perc":0,"expected_duration_sec":2700,"install_perc":1,"status":"","version":" "},"speed_limit_mode":{"active":false,"current_limit_mph":85.0,"max_limit_mph":120,"min_limit_mph":50.0,"pin_code_set":false},"timestamp":1718034631944,"tpms_hard_warning_fl":false,"tpms_hard_warning_fr":false,"tpms_hard_warning_rl":false,"tpms_hard_warning_rr":false,"tpms_last_seen_pressure_time_fl":1717998007,"tpms_last_seen_pressure_time_fr":1717998007,"tpms_last_seen_pressure_time_rl":1717998006,"tpms_last_seen_pressure_time_rr":1717998006,"tpms_pressure_fl":2.85,"tpms_pressure_fr":2.85,"tpms_pressure_rl":2.9,"tpms_pressure_rr":2.875,"tpms_rcp_front_value":2.9,"tpms_rcp_rear_value":2.9,"tpms_soft_warning_fl":false,"tpms_soft_warning_fr":false,"tpms_soft_warning_rl":false,"tpms_soft_warning_rr":false,"valet_mode":false,"valet_pin_needed":false,"vehicle_name":"M3 Fred","vehicle_self_test_progress":0,"vehicle_self_test_requested":false,"webcam_available":false}}}
2024-06-10 17:50:31.999 DEBUG (MainThread) [custom_components.tesla_custom] Finished fetching tesla_custom data in 0.277 seconds (success: True)
2024-06-10 17:50:32.003 ERROR (MainThread) [homeassistant.components.sensor] tesla_custom: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 729, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1289, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 529, in async_update
    await self.coordinator.async_request_refresh()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 262, in async_request_refresh
    await self._debounced_refresh.async_call()
  File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 114, in async_call
    await task
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 288, in async_refresh
    await self._async_refresh(log_failures=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 411, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 165, in async_update_listeners
    update_callback()
  File "/config/custom_components/tesla_custom/base.py", line 79, in _handle_coordinator_update
    super()._handle_coordinator_update()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 491, in _handle_coordinator_update
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1000, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
    state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1061, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1006, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/select/__init__.py", line 148, in state
    current_option = self.current_option
                     ^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tesla_custom/select.py", line 243, in current_option
    AUTO_SEAT_ID_MAP[self._seat_name]
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'rear center'

Anything else?
The "battery_level":64 is the accurate value at that moment
The KeyError: 'rear center' sounds appropriate as the M3 has no heating in center rear seat.
Range still works during same period

@dandelionclock can you see if you can check for this too please? It may be handled by your new PR. Probably need a .get instead of an array access.

I thought it was related to the Fleet API, so I went through all the trouble of setting up the Fleet API proxy and connecting to it from the integration but unfortunately this didn't work. It is therefore probably not API related.

Rollback to v3.22.2 confirms this issue is new in v3.23.0.

Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?

Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?

The error started on June 8 and was still on-going since June 9, The rest of the graph just shows missing battery.
As @Sebazzz rolling back to v3.22.2 solved the issue: the sensor came back.
It was still active after re-updating to v3.23.0
I have kept debug on, will let you know when I notice it's back to unavailable

I'm on my mobile now; but I read something yesterday about an  unhandled task error. My guess is that the sensors are requested or processed in parallel and upon error Home Assistant cancels all executions - and with parallelism you don't always have the same code execute in the same order. I'm only guessing though.
Met vriendelijke groet,
Sebastiaan Dammann

Van: Fred @.>
Verzonden: Tuesday, June 11, 2024 6:01:35 AM
Aan: alandtse/tesla @.>
CC: Sebastiaan Dammann @.>; Mention @.>
Onderwerp: Re: [alandtse/tesla] Unavailable battery sensor (Issue #996)
Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?
The error started on June 8 and was still on-going since June 9, The rest of the graph just shows missing battery.
As @Sebazzzhttps://github.com/Sebazzz rolling back to v3.22.2 solved the issue: the sensor came back.
It was still active after re-updating to v3.23.0
I have kept debug on, will let you know when I notice it's back to unavailable
—
Reply to this email directly, view it on GitHubhttps://github.com/alandtse/tesla/issues/996#issuecomment-2159735925, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAK4FML7O33XKAAX7B7RRM3ZGZZB7AVCNFSM6AAAAABJCU2HXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZG4ZTKOJSGU.
You are receiving this because you were mentioned.Message ID: @.***>

Same problem here. Model 3 2024 (Software 2024.20.1). No battery SoC since version 3.23.0

Just updated to 3.23.0 this morning and lost battery as well. Happy to help with troubleshooting/testing.

Same problem. Battery entity is no longer being provided by the tesla_custom integration version 3.23.0

Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?

The error started on June 8 and was still on-going since June 9, The rest of the graph just shows missing battery. As @Sebazzz rolling back to v3.22.2 solved the issue: the sensor came back. It was still active after re-updating to v3.23.0 I have kept debug on, will let you know when I notice it's back to unavailable

not sure it does help anyhow, but giving the promised update: I even though I re-updated to v3.23 three days ago, my battery sensor has constantly been available so far, no new log to share

I removed the integration completely and reinstalled it (ver 3.23.0). Battery sensor still missing.
Model 3 2024 („Highland“ with Software 2024.20.1). Maybe only „Highland“ is affected ?

Sensor is working again. :)
Thank you


Radio Buttons with text cursors

Version 0.4.3 (0.4.3)

Radio Buttons with text cursors
Click 'Proposals'
Click first one
Hover over a radio option and cursor should be 'pointer'

no longer seems to be the case, now seeing "default" cursor. web3 standards say cursors should be set to auto for checkboxes so pointer is not required. closing unless someone else can report seeing text cursor again.


Creating multiple Opportunity Naming Settings records within the same clock minute throws an exception

Steps to reproduce:

Visit NPSP Settings tab
Via Donations > Opportunity Names click 'New Opportunity Name'
Save the record (quickly)
Click 'New Opportunity Name' again (quickly)
Save the record (quickly)

Expected result:
Two Opportunity Naming Settings records are created, with default settings.
Actual result:
When attempting to save the second record, a FIELD_INTEGRITY_EXCEPTION is thrown due to a naming collision of the custom setting.
Notes:
The issue seems to be because the settings are being named using a timestamp with minute resolution.  If you attempt to create and save two ONS records within the same clock minute, then they will end up with the same timestamp/name and the second one will not be able to be saved.
(screenshot of exception attached)

**lurch: add

Tracking W-010903


setStatusBarContentColor has no effect on iOS

setStatusBarContentColor has no effect on iOS. Status bar elements are painted into black no matter which setting is applied. On Android it works perfectly fine. BTW, setIsStatusBarsVisible works. On iOS side I'm using the WindowInsetsUIViewController.

Changed the iOS emulator and all works fine.


⚠ Avatar API Endpoint has degraded performance

In 10754d2, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 8276 ms

Resolved: Avatar API Endpoint performance has improved in ec83d71.


Enhancement to ajax component: Add option to pass query parameters to…

Enhancement to ajax component: Add option to pass query parameters to the ajax request. Particularly useful for components (search) in which query parameters are require for functionality.

Replaced via #484


CHANGE REQUEST: LayoutContainer shouldn't force content into a span-1 by default

When using the LayoutContainer component it forces all content by default into span-1's this requires us to always add a div overriding this.
<LayoutContainer>
  <div className="col-span-12">
    ...stuff...
  </div>
</LayoutContainer>

I don't believe this should be the default behavior of this component; but rather an optional one. (We also use our own grid system)

Will publish a new package shortly with some fixes. If there are any other concerns, feel free to open up a new issue. Thanks for your feedback


Glitchy Encoder

I'm finding the encoder glitchy. If turned too fast, it can reverse direction.
I'm using the specified encoder part.
I thought initially it was a hardware issue with my build (I've experienced similar behaviour with other builds, when I've forgotten to solder a capacitor related to the encoder), but a more experienced DIY builder friend noticed the same behaviour with their build.

Im also getting the same behavior...

On 20 Mar 2019, at 8:34 PM, alx<EMAIL_ADDRESS>wrote:
I'm finding the encoder glitchy. If turned too fast, it can reverse
direction.
I'm using the specified encoder part.
I thought initially it was a hardware issue with my build (I've experienced
similar behaviour with other builds, when I've forgotten to solder a
capacitor related to the encoder), but a more experienced DIY builder
friend noticed the same behaviour with their build.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/westlicht/performer/issues/4, or mute the thread
https://github.com/notifications/unsubscribe-auth/Ag5r1CqhfSaFcdCNvEARAJF7fLFTlRD-ks5vYgCvgaJpZM4b-2hx
.

I actually noticed that behaviour myself a few times, but it rarely bothered me. There are no caps to filter the encoder outputs but there is software debouncing. However, I guess the scan frequency might be too low for certain edge cases. I will investigate.

My impression is that it’s worse when scrolling through lists of items, then when adjusting values.
When calibrating the CV outputs last night, I resorted to using the Next/Previous buttons to move through the list of outputs because using the encoder was unreliable.
However, I don’t recall noticing any issues with the encoder while adjusting the offset values, even when rotating the encoder quite rapidly.

I'm afraid the encoder is still glitchy with 0.1.6. My immediate impression is that it's worse than before, in fact.
As well as reversing direction, now, the selection also sometimes continues to move after I've stopped rotating the encoder.
I will try and shoot a video showing the behaviour this evening.

I should add this is while scrolling through menus. I haven't tested setting individual values with the encoder.
Could it be that the encoder scan-rate is lower when scrolling menus than when setting values?

@toneburst that's odd. Also, you should use 0.1.7 which contains the fix. 0.1.6 did not change anything regarding the encoder. And no, there is no change in scan rate. For me, 0.1.7 works flawlessly now.

I'm really sorry, you're right. I downloaded the 0.1.6 version, thinking that was the most recent, because I hadn't refreshed the Releases page.
Very stupid, I do apologise.
The encoder does seem much better now, thank you. I'm going out now, but will test more thoroughly when I get home this evening.
Really looking forward to testing the MIDI slide behaviour with my MB33 303 clone.

@toneburst no problem, let me know about your findings. Always grateful for feedback!

It's definitely better, but still glitchy.

I guess I need a video. Not glitchy at all for me.

Above comment was me, signed in to my other GitHub account (in case you didn't realise.
I will try and made a video soon.


profile add profileTime

What type of PR is this：

[ ] enhancement

profile add profileTime
Problem Summary(Required) ：
the profile does not have profileTime; add it to profile

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.even seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Did you encounter any performance issue of profile? Why add this property in profile?

@even986025158 Need you to sign the CLA

@even986025158 Thanks for your contributions. Need you to sign the CLA.

when I click into Contributor License Agreement] it shows than You have agreed to the CLA for StarRocks/starrocks

Did you encounter any performance issue of profile? Why add this property in profile?

Because sometimes after the profile is turned on, some execution time will take longer than normal, so I need to see how much profileTime costs

run all

@even986025158 You need use the same email address in the commit as the one you login in GitHub. Please check it. Other the CLA can't pass

@even986025158 You need use the same email address in the commit as the one you login in GitHub. Please check it. Other the CLA can't pass

I have  add the other email in GitHub, can it ok now

@even986025158 You should change you git config to your github email and push it again. I think you can close this PR and create an new PR with the new commit.