Theme migration progress

Themes need to be updated to support new UI and Spicetify and branch v2 has been created in this repository for the purpose.
Here I will list all the themes and the update progress, tagging maintainers of the existing who are able and want to contribute. As some themes in this repository are very similar they can be merged into a single updated theme with multiple color schemes. Please refer to the README in the new branch for all the information

[x] Default (from Adapta-Nokto, Ark-Dark, Ark-Green, Blueballs, DeepCoral, Discord, Dobbo, Flatten, Gruvbox-Gold, Kaapi, Matcha, Midnight-Light, NightOwl, Phosphoria, Vaporwave, YoutubeDark)
[x] Sleek (from BIB-Green, Black, BladeRunner, Challenger-Deep, Cherry, DanDrumStoneNew, Dark, Dracula, Elementary, Gradianto, JarvisBot, Material-Ocean, MoonChild, Night, NightMoon, Nord, NoSleep, OneDarkish, Otto, OutrunDark, OldSchoolSenn, Pop-Dark, Twasi, SolarizedDark, Sweet, Tidal, TrekyGoldenrod, TychoAwake, WintergatanBlueprint)
[ ] BurntSienna (from BurntSienna, @pjaspinski)
[x] Dribbblish (from Dribbblish, @khanhas)
[x] DribbblishDynamic (from DribbblishDynamic, @JulienMaille)
[x] Onepunch (from Onepunch, @okarin001)
[ ] ShadowCustom (from ShadowCustom, @CallMeVorex)
[ ] Spicy (from Spicy)

Please mention the people who contributed to color schemes and themes in each theme README.

Will start working on them.

Made a better sheet for current themers for easy upgrade.
¯\__(ツ)_/¯ = Colors that need testing with other colors
[Sheet]
New
text                         = main_fg
subtext                   = secondary_fg
main                       = main_bg
sidebar                   = sidebar_and_player_bg
player                     = sidebar_and_player_bg
card                        = ¯\_ (ツ) /¯ color of card
shadow                   = cover_overlay_and_shadow
selected-row           = ¯\_ (ツ) /¯ color of the selected song
button                     = ¯\_ (ツ) /¯ confusion when placing old colors
button-active          = pressing_button_fg
button-disabled      = slider_bg
tab-active                = selected_button
notification              = ¯\_ (ツ) /¯ haven't seen any change
notification-error     = ¯\_ (ツ) /¯
misc                         = ¯\_ _(ツ)__/¯
Correct if wrong.
Some colors may not be correct but it works for some dual tone themes.

Can users help in updating the themes?

I guess it depends if the previous maintainers want to update their themes on their own. Let us wait some time to see if they get to reply.
Of the above-listed themes, Spicy has no real maintainer, as I pushed in when creating the repository, taking it from Spectrum chat, so feel free to update it and open a PR.

Sorry but porting DribblishDynamic is out of my league :(

@Milo123459 there isn't for sure about v2 (as far as I know) but it would be very nice to have something like that as well in the repository

It would be a good idea if some one could list out css commands to edit the interface in an easy way in the repository.

it's done. I have commented on my user.css, as much as I could. So, if anyone needs any reference for the new UI can check that.

Sorry but porting DribblishDynamic is out of my league :(

I opened #377 about that, if anyone wants to contribute

@RootBurner In the sceond screenshot, how did you get rid of the new gradient?

I haven't come across gradients. I only made edits in the color.ini file. The only edit I did in the css files were the play button appearing white as default.

It seems it happens after v2.0 upgrade. Thanks for the reply.

Bug: Aritim-Dark & Arc-Dark are broken

^ Happened again. It seems to be broken and can't apply themes.

Ark Dark Base

Does anyone plan on porting black? If not I could probably try and figure out the colors by myself, but not quite sure how I would port the user.css

Does anyone plan on porting black? If not I could probably try and figure out the colors by myself, but not quite sure how I would port the user.css

There a Pull request (#370 ) for merging a theme on which we could push the Black color scheme. It will soon be merged

@khanhas do you plan to update Dribbblish to v2?

@morpheusthewhite I do but I'm currently busy with uni right now. Maybe 2,3 weeks later

Would love to have Flatten ported to v2. Or I guess I could look into it myself.
Sleek BIB works great so far though :D

@morpheusthewhite I do but I'm currently busy with uni right now. Maybe 2,3 weeks later

I like how @khanhas always under-promise and over-deliver!
I was able to "patch" dribbblish into dribbblish-dynamic with just on additional js file, still wondering how to distribute this. I think the "light/dark" switch could merde with the original dribbblish.

@morpheusthewhite would you accept adding v2 themes as submodules (and update them when a clean release is ready) rather than as code itself?
A preview of dribbblish-dynamic is available here: https://github.com/JulienMaille/dribbblish-dynamic-theme

@morpheusthewhite would you accept adding v2 themes as submodules (and update them when a clean release is ready) rather than as code itself?

I'm not sure using a submodule is a good idea because probably many users, especially on Windows, just download the zip file of this repository

You can push it once it is ready directly on Dribbblish since khanhas agreed

@morpheusthewhite @khanhas i would enjoy some feedback on the latest commit with color transitions (a frequent request) does it lag on your system?

@JulienMaille it works great for me, I used the previous version last night too and now the transitions are much better. Awesome work! Honestly from everyone making this migration happen quick, but this was the theme I used so thanks.

I could use some feedback on the bash script, calling all linux users!
curl -fsSL https://raw.githubusercontent.com/JulienMaille/dribbblish-dynamic-theme/master/install.sh | sh

@morpheusthewhite I do but I'm currently busy with uni right now. Maybe 2,3 weeks later

I like how @khanhas always under-promise and over-deliver!
I was able to "patch" dribbblish into dribbblish-dynamic with just on additional js file, still wondering how to distribute this. I think the "light/dark" switch could merge with the original dribbblish.

Does Dribbblish V2 support the "light/dark" switch by default? or must one install the version from your repo to get that feature?

Currently you need to install the version from my repos.

@JulienMaille
I Installed the one from your repo (from the script), but i had an issue where I could not read some of the text because of the background color. I noticed that playing songs seemed to place the album artwork as the background of the window, however the colors would not change according to the song played. I got a screenshot, but, since I tested this on a Linux Live USB, I forgot to save it when I rebooted to test @morpheusthewhite's version. :s
I can create an issue in your repo if you would like.
I was able to test what I wanted though: the toggle. I would love to be able to switch between two static color_schemes on the non dynamic Dribbblish.

@morpheusthewhite
I also tested the version from this repo on a live environment. And I was able to install the latest version of spicetify (v 2.2.5) and spotify, (1.1.55) but nothing happened to my Spotify. It had the default look on even though I had the Dribbblish theme on. I copied and pasted the install instructions from the README file, so IDK what the problem could have been.
Please let me know if you would like me to open an issue with you.
I have the latest Spotify version installed (<IP_ADDRESS>8.gf9a83c60).  Mine is from Spotify's Debian repo, but I also checked that the Flathub version is the same.
README from Dribbblish lists: "Make sure you are using spicetify v2 and Spotify v1.1.58 or later." Is that a typo or Linux is not yet supported bc 1.1.58 is not out for it yet?

I have the latest Spotify version installed (<IP_ADDRESS>8.gf9a83c60). Mine is from Spotify's Debian repo, but I also checked that the Flathub version is the same.
README from Dribbblish lists: "Make sure you are using spicetify v2 and Spotify v1.1.58 or later." Is that a typo or Linux is not yet supported bc 1.1.58 is not out for it yet?

I actually had the same issue a few days ago on MacOS and basically what needs to happen is that uninstall both Spotify and Spicetify entirely and then reinstall the programs again. After you reinstall make sure to copy over everything from the Zip File and then retry the entire process again of copy and pasting the code and it should work.

what needs to happen is that uninstall both Spotify and Spicetify entirely and then reinstall the programs again.

Did you have a clean install before? I booted into a live Ubuntu USB and fresh installed everything to test it. I will wait a week or so and try again

So is anyone working on the Nord theme at the moment?

@Tuuuukka as of plans it will be just a colour scheme for the Sleek theme

We will switch branch in a week, I think now most of the people are using the new Spotify UI

Just updated the branches.
v2 is now named master
If you have a local clone, you can update it by running:
git branch -m v2 master
git fetch origin
git branch -u origin/master master
git remote set-head origin -a


use only JSON types

Discussion in https://github.com/rsmp-nordic/rsmp_sxl_traffic_lights/issues/133

done


Persian (fa_IR) Locale added successfully

Hi mate,
I created fa.json file and translated to my fluent language. Please accept this pull request.
Thank you alot <3
Best wishes

Ahhh, Sorry but I forgot to add new  tag for Persian language in Statusbar.vue,
Please do it by yourself.
Thanks

thanks, it is merged and published.
It is also live on our demo site : vuefinder.ozdemir.be


Feature request: Customize error messages on SchemaValidationError exception

Use case
I’m using the function “validate” from aws_lambda_powertools.utilities.validation to validate my JSON Schemas. The problem is that I’m not able to customize the error message whenever a schema is not valid (it’s encapsulated).

Solution/User Experience
My idea would be to have an attribute into the schema property like “errorMessage” which would contain the custom message. When handling the exception SchemaValidationError we can check if this attribute exists in the property and assign it to SchemaValidationError.validation_message.

I don’t know if it would be enough or if it’s also necessary to change the code of fastjsonschema library. Maybe it must know the key “errorMessage” in that approach?
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (Python) Tenets
[X] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

Oi @gamaleonardo, tudo bem?
Thank you for opening this! Have you considered catching the exception yourself and re-throwing it with your own message? I'm a little unsure about adding such a customization to a library.
Example:
from aws_lambda_powertools.utilities.validation import SchemaValidationError, validate

def lambda_handler(event) -> dict:
    try:
        validate(event=event, schema={})
        return {"body": "validated", "statusCode": 200}
    except SchemaValidationError as exception:
        return {"body": f"error validating {exception.path}: {exception.validation_message}", "statusCode": 400}

Opa @gamaleonardo!
If I understand correctly, you're trying to create a custom error message for each property to make it easier to return it to whoever invokes this API, right? I would say based on this line:
return {"message": e.schema["errorMessage"]}, http.client.BAD_REQUEST
If this is correct, I have a few considerations:
1 - Our validation utility supports Official JSON Schema and in the official definition the errorMessage field does not exist. What you can do is create a new field called properties and add this custom field inside it, like this:
"properties": {
     "propertyName": {
          "title": "The type",
          "type": "string",
          "properties": {
	        "errorMessage": {
	          "type": "string"
	        },
     }
}

2 - We use fastjsonschema in our validation utility, and the API definition for a JsonSchemaException does not support any fields other than message, path, type, definition, rule, and rule_definition. Reference here: https://horejsek.github.io/python-fastjsonschema/#api
3 - The fastjsonschema.validate does not fail validation per field, it validates the entire schema and returns an error if validation fails. So even if we had a way to access the errorMessage property, I don't see a good design/DX for implementing this as we don't know exactly which field failed.
4 - Is not useful for you to catch the error as @rubenfonseca suggested?
I don't think we will be able to support this at the moment, but I think you can open an RFC telling us your need and we can discuss how to implement this, or even change the library we use. This will have to be done via RFC as there will possibly be breaking changes and we are extremely careful with that.
Thanks so much for opening this up, it might be an interesting use case for more users as well.
Em tempo, saudades da terra boa da Bahia :)

Hi @gamaleonardo let us know if you still need assistance with this issue, otherwise we would be happy to close it!
Adding "revisit-in-3-months" tag

Obrigado @gamaleonardo!


[Fullscreen Marquee Desktop] Gradient H1 different layout for JP

Treat JP h1 with gradient text differently in CSS due to reserved child tags empty space.
Test URLs:

Before: https://main--express--adobecom.hlx.page/jp/express/create/video/tiktok?lighthouse=on
After: https://jp-fullscreen-marquee-fix--express--adobecom.hlx.page/jp/express/create/video/tiktok?lighthouse=on

Codecov Report

Merging #187 (9990bc6) into main (880ac80) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #187   +/-   ##
=======================================
  Coverage   35.48%   35.48%
=======================================
  Files          27       27
  Lines        9463     9463
=======================================
  Hits         3358     3358
  Misses       6105     6105

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Bug]: SaaS Integrations are missing on new deployments (Airtable, Twilio, HubSpot)

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When raising an instance either in docker-compose or in DigitalOcean, the Airtable, Twilio, HubSpot data sources do not appear.
Logs
Performance log

Steps To Reproduce

If you have an active docker instance of Appsmith clear all the cache and update it to the latest version.
Once the version of the instance is updated and the cache is cleared, execute the instance.
Navigate to Data source and notice that the following API data sources Airtable, Twilio, HubSpot are not listed.
Create an instance from Appsmith's DigitalOcean marketplace and notice that the data sources don't appear  Airtable, Twilio, HubSpot.

Public Sample App
No response
Issue video log
No response
Version
Self-hosted 1.8.8
Self-hosted 1.8.6
 Front conversations

Appsmith Cloud seems to be working as expected. Tested some existing queries/apps and all of them work fine (HubSpot).

Added a link to the logs on the description.

We conducted an investigation where we found the following information.
We make a query to the Mongo database that has the plugins. It does not contain Airtable, Twilio, HubSpot.

We reviewed the relevant logs and found the following error in
cs.appsmuith.com
download the logs here

@rohan-arthur @sumitsum can we fix this asap?

@felix-appsmith was this working before? If it's a regression, we can even mark it is critical

@rohan-arthur Yes this worked before

Potentially fixed in #18440 , will close the issue after confirming that this is reflected in the Docker image after promoting to master.

@nidhi-nair closing it because it seems to be working on our end.
@felix-appsmith could you please re-verify?

It works well.

@Nikhil-Nandagopal
This bug was solved before, but it broke again, it presents the same behavior, this problem is related to this other one.
https://github.com/appsmithorg/appsmith/issues/18211

Current version where is the problem: 1.9.5 Self-Hosted

@sbalaji1192 @nidhi-nair why does this keep breaking?

@sribalajig Please check the above comment.

This user is being affected by this problem

It was solved


Cannot disable alarm through HA control panel or automation

Alarmo Version
v1.10.1
HA Version
2024.6.1
Bug description
When disarming the alarm through the Home Assistant control panel (more info dialog of the alarm entity) or when disarming through an automation. I get this error.
When disarming through the alarmo frontend card, no error and i can disarm
Steps to reproduce
Arm the alarm, then disarm through HA control panel
Or automation:
device_id: some-id domain: alarm_control_panel entity_id: alarm_control_panel.alarmo type: disarm code: "blaat"
Relevant log output
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py", line 207, in async_handle_alarm_disarm
    await self.async_alarm_disarm(self.code_or_default_code(code))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given

I don’t accept bug reports for older version of alarmo.


Issue with AngularJS 1.5 Uglifying

Webpack version - 4.6.0
Uglifyjs webpack plugin -  1.2.5
AngularJS - 1.5.0
While bundling angularjs project with webpack uglify we are facing issue with dependency injections ( default module like $location and custom service are unable to register. )
I have created a demo app with all the setup that shown error and can be access from ng6-starter repo.
I have also attached an screenshot of error msg.

@pratoshpro looks like bug in unligy, can you try https://github.com/webpack-contrib/uglifyjs-webpack-plugin/pull/293 branch?

@evilebottnawi - Do you have any sample code for integration of @fabiosantoscode/uglify-es with webpack 4.

@pratoshpro what?

#293  did not work for me have any other sample code with webpack 4.

@pratoshpro it looks like your code is missing explicit DI annotations, thus the error function($stateProvider, $urlRouterProvider) is not using explicit annotation and cannot be invoked in strict mode
You either need to provide explicit annotations (see here) or use something like babel-plugin-angularjs-annotate to auto-annotate your DI.


[Bug] Too many wireless conectors and advanced inscribers.

I have a small ME network with 6 wireless connectors and 4 advanced inscribers. I first noticed when I installed Player API for Galacticraft and Extra Utilities portal compatibility. After removing Player API from the server the number of Wireless Connectors went for about 50 to about 16. Then I removed Player API from my client, this fixed the Wireless Connectors but I saw 12 Advanced Inscribers. Simply replacing the Advanced Inscribers fixed them.
This caused a major power drain that stopped everything from working. I tried to replicate the bug by reinstalling Player API and got 6 Wireless Connectors and 7 Advanced Inscribers. It seams like when I leave the area and come back the numbers change. I used the network tool to get all these numbers.
I'm using lots of different mods, so I've included a list of all the jars.
Mods.txt

I'm closing this issue as part of a spring cleaning of my issue trackers from old stuff.
If you believe it's a bug that is still relevant in Minecraft 1.12 - Feel free to reopen it.


to_csv(header=True) produces error:

According to the latest doc header parameter can be

boolean or list of string, default True

However, the following code
import pandas as pd
pd.read_csv('test.csv', header=True)

Produces this error:

TypeError: Passing a bool to header is invalid. Use header=None for no header or header=int or list-like of ints to specify the row(s) making up the column names.

Not sure what is expected behaviour but the code and the doc don't seem to agree with each other?
INSTALLED VERSIONS
commit: None
python: 2.7.10.final.0
python-bits: 64
OS: Linux
OS-release: 2.6.18-238.9.1.el5
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US
pandas: 0.17.1

Your code uses pd.read_csv, but the documentation you quoted is from DataFrame.to_csv.

Yes I take it back - sorry for confusion - just realised myself.


Expand Blazor logging and diagnostics

This is part of https://github.com/aspnet/AspNetCore/issues/10472
Ensure developers can trace all the major things that happen in a server-side Blazor application (e.g., circuits starting/ending) with a special focus on all incoming calls from the client (event notifications, JSInterop calls, renderbatch ACKs).

[ ] Outbound JS interop calls (.NET to JS)

[ ] Call sent
[ ] Reply received (with successful result or exception)
[ ] Cancelled due to timeout
To avoid noise, we should distinguish framework-originated calls from application-originated calls. This might be achieved by having a separate InternalInvokeAsync on RemoteJSRuntime that only the framework calls and is not on the IJSRuntime interface.

[ ] Inbound JS interop calls (JS to .NET)

[ ] Call received
[ ] Reply sent (with successful result or exception)
To avoid noise, we should distinguish framework-originated calls from application-originated calls.

[ ] Incoming UI event notifications
[ ] Rendering

[ ] Instantiating a component
[ ] Disposing a component
[ ] Rendering a component
[ ] Sending a render batch to the client
[ ] Receiving acknowledgement of a render batch from the client

[ ] Circuits

[ ] Circuit created
[ ] Circuit connected
[ ] Circuit disconnected
[ ] Circuit disposed
[ ] Unhandled exception

[ ] Routing

[ ] Navigation occurred, whether to a matching @page component or if no match was found

This assumes it's possible to do such fine-grained logging without any meaningful perf cost (at least, when the logging level is such that the messages are being skipped). If this does turn out to have a meaningful perf cost, we wouldn't want to do all the per-component parts under "rendering".

@javiercn and I have discussed this. Similar to https://github.com/aspnet/AspNetCore/issues/11791, he's going to deal with logging for JS interop. I'm going to deal with it for other areas.

@rynowak Do you have a view on which parts of this should be handled using ILogger versus DiagnosticSource or System.Diagnostics.Trace? It's not something I have a lot of history with.
It would be convenient to use ILogger only, since it's unclear DiagnosticSource is a recommended pattern (looks like SignalR doesn't use it at all), and System.Diagnostics.DiagnosticSource can't immediately be referenced by a netstandard2.0 project due to not being in the shared framework.
Unless there are reasons, I expect to follow the same patterns for this as in the SignalR code.

diagnostics source is a lower level construct I believe, for way lower level tracing. ILogger afaik is good enough.

Let's just do ILogger for now. ILogger is always useful because it doesn't require any special tools to see the output. DiagnosticSource is only useful when someone is writing a tool to process the data.

The non-JS-interop parts of this are now done, so I'm unassigning myself and leaving the JS interop bits with @javiercn.

Closing this as the changes have been included in https://github.com/aspnet/AspNetCore/pull/12250 which will be merged with the rest of the dependencies


remove appVersion from chart.yaml

In terms of removing the App Version...  Generally with an upstream chart, what consumers expect is that the chart has been tested with the defined version of the package specified.  When you have just one "main" container, using AppVersion as the default when values.image.tag (or equivalent) isn't specified is the "standard" behavior.
It allows one to inspect the chart with helm inspect/show, as in
sauer@fabulinus:~$ helm -n cert-manager list
NAME        	NAMESPACE   	REVISION	UPDATED                                	STATUS  	CHART               	APP VERSION
cert-manager	cert-manager	7       	2023-11-05 21:55:33.770327854 -0600 CST	deployed	cert-manager-v1.13.1	v1.13.1

Creating a release every time the helm'd application image is released allows situations like mine, where helm charts are automatically deployed from a repo via a tool like Argo-CD or flux, and the chart is updated using a tool like Renovate to open PRs against the CD tool's source repo.  A new chart traditionally means an updated app, often with no other changes to the chart other than the AppVersion - and any changes necessary to accommodate the new version of the app, if any.

For an example I'm familiar with: I (SRE/release/whatever, not developer) inherited a monorepo at Determined where the helm chart lives alongside the application.  I don't like it, but it's not worth changing yet.
It's not the perfect example (I definitely have some cleanup to do to that workflow), but what I do to publish helm releases there is use a machine account to check out the helm branch (github pages) and update it when there's a new release published in the main repo - which will include a helm chart as an artifact.  The actual publishing process I use is less important than the fact that I'm using the release.published trigger (as well as a workflow_dispatch trigger to allow manual publishing of a specific version for whatever reason).
It should be pretty trivial to similarly on-release trigger a workflow in the separate helm repo by directly calling a dispatch action in the helm repo which checks the current / a specified version of the upstream digger package and if it's not already published, update the chart, test, and publish.
I don't really have a great solution for easing matrix testing of a helm chart with common variations of values files, though it's on my list of things to someday figure out better.

Many thanks @dannysauer ! Clearly much that I have missed about workflows of helm consumers. Will then do the recommendation of using appversion as the default when tag is not specified and setting up rennovate


RMT API requires unique bytes (IDFGH-5605)

Environment

Development Kit:      [none]
Module or chip used:  [ESP32-WROOM-32]
IDF version: v4.2.1-141-g1e3638390
Build System:         [idf.py]
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2020r3) 8.4.0
Operating System:     [macOS]
Using an IDE?: [No]
Power Supply:         [USB]

Problem Description
I'm facing a strange issue today and drilled down to pretty much except my own implementation.
The goal is to send three bytes to a single WS2812B and the code is pretty much based on the example code given by Expressive ("led_strip").
I noticed that sometimes if I send a colour value the LED flashes briefly in the correct colour, but gets cleared immediately. After some digging it turned out that it will always happen if either color value is equal to any other one. Meaning two or more identical bytes.
To patch the problem for now I make sure that the values are unique by altering the least significant two bits.
In theory I don't see how the RMT driver could be responsible for the problem, but I completely fail to find another possibility. I spoke to three different developers today (neither is fluent in the ESP SDK though) and none of us could come to a conclusion other than "the API is at fault".
I did take two measurements using a logic analyser, but that didn't bring me to any conclusion, as the waveform looks fine. I'll try to come up with more thoughtful data that makes it easier to spot and may edit in the next days.
Expected Behaviour
Solid colour displayed until a new value is sent
Actual Behaviour
A brief flash in the correct colour, LED gets cleared immediately
Steps to reproduce

Setup the smallest viable program based on the RMT API / "led_strip" example code
Send a single colour value with two or three bytes being equal (e.g. white)
Send a single colour value with only unique bytes

Measurements
Top trace is the erroneous one, the bottom one is sent using my patch (see code below)

Code to reproduce this issue
https://gist.github.com/julian-weinert/b5fc9b939d4035e27866bf8726c35459
Other items if possible
elf file
sdkconfig

Sorry for the confusion. For some absolutely bizarre reason my wiring decodes the bytes and injects faults when ever I send two identical bytes. At some point I sent the signal to a different LED, that worked.
Then putting this LED into circuit lets the fault appear again, but only if I send any byte duplicate.
Meaning if red & green, red & blue or green & blue are equal it breaks.
That's why I came to the conclusion "API".


[Snyk] Upgrade @react-native/babel-preset from 0.73.21 to 0.74.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @react-native/babel-preset from 0.73.21 to 0.74.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 132 versions ahead of your current version.
The recommended version was released 5 months ago, on 2023-10-11.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Solved by #20


"language" parameter for openai stt

Is your feature request related to a problem? Please describe.
when i use openai as an stt engine and i try to speak in english it kind of works but shows the text in random exotic languages instead of english.
Describe the solution you'd like
a way to set a specific language for the openai stt engine.
i see from openai api reference that in addition to the required field "model" it is possible to pass optional "language" field:
https://platform.openai.com/docs/api-reference/audio/createTranscription
in source code i found where stt config is being built:
https://github.com/open-webui/open-webui/blob/main/backend/open_webui/apps/audio/main.py
can we add an optional "language" parameter.
Additional context
https://github.com/open-webui/open-webui/blob/main/backend/open_webui/apps/audio/main.py
https://platform.openai.com/docs/api-reference/audio/createTranscription

or i may be wrong... i hardcoded a different "language" field on my machine and i saw no effect in language detection... what helped is when i also added field "prompt":"english language". so, we may need not just one addition input "language" but two - "language" and "prompt".


release fails sometimes

it fails when bindmounts disappeared (e.g. by reboot)
thread 'main' panicked at 'umount failed: EINVAL', src/hog.rs:73:34
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: hosthog::hog::release_ssh
   4: hosthog::main

improved error handling 2dab6315


[dashboard] can't build

QueryClientProvider should be replaced with RoochProvider
should use getRoochNodeUrl to get the DevNetwork
useMutation call outside of QueryClientProvider

Ref https://github.com/rooch-network/rooch/issues/2052


Test webhooks

This issue create for test webhooks

Hello! Thank you for creating the issue! We will review it shortly.

Update issue comment

Update again


Set up Tkey object, add description for w3a method flow

This #PR commits already included in #PR 20, which successfully merged.


PR MD template

Create pull requests template in markdown. Is this correct @JustinCast?

@JustinCast does this mean: Create pull requests template in markdown?

@ldrojas yep


Waves example seems to be broken

The waves example shown in the README seems to be broken: This is the result I see running it on both Firefox and Chrome:

The other examples work fine, just thought you'd want to know that the waves example seems to be down.

This is a bug related to CodeSandbox where React spring (which is used in Drei) tends to fail. I’ve seen it multiple times across multiple boxes.
Can you try forking the example and updating the dependencies?

Sorry for the late reply, I built locally and was able to run the example just fine. I'm afraid I don't have much experience with CodeSandbox, so I'm not sure how to help there. I just did the normal install, nothing needed to be updated (I have no changes to the package.json). Let me know if there's anything else I can do to help!

Thank you’d or your investigation! This seems like problem in react-spring. I will update the dependencies to see if that fixes it, if not then this can’t be fixed here.


Add travis

[ ] Add encrypted API key (@ewindisch)
[ ] Deploy only on tagged releases? ❓

Yes, lets only deploy tagged releases... unless we can set versions on npm and have a "trunk" version as well?

Closing, as we're using Circle CI


Update train_and_evaluate_using_ray.md

evaluation.csv was not found because the actual directory changed during the run.
-> Added Get the current working directory and add it to csv_filename.

Changed to os.path.join

Thanks!


Update protobuf-java to 3.17.0

Updates com.google.protobuf:protobuf-java from 3.15.8 to 3.17.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.protobuf", artifactId = "protobuf-java" } ]

labels: library-update, semver-minor

Superseded by #939.


Extension - Do not show watch-only account on History (All account mode)

Describe the bug
Do not show watch-only account on Transaction History

Version test: http://<IP_ADDRESS>:8900/s/egWaXHcJ6exPWrA
Validation passed.

Show account watch only on History

Current account
All account

Install/ Upgrade version

Check the automation of retrieving online transaction history for different types of accounts


scrollbar misplacement by width of scrollbar

Current behavior:
Scrollbars are incorrectly positioned left or above of where they should be, so that they are not at the right side edge of the panes (for y scrollbars), or bottom edge of panes (for x scrollbars). The displacement is equal to the width of the scrollbar. This leaves a gap between the scrollbar and the divider or edge of the window and means the scrollbar removes twice as much useful space as it should.
This affects the latest release (v1.5.9) and was introduced by commit 7eeb3a59bdc77685bfaaa12323645439059ce500 (PR #303).
Expected behavior:
There should be no gap.
Codepen example:
https://codepen.io/mjwright/pen/oGvrGY
Load the codepen and you will see there are gaps between the scrollbars and the dividers.
This codepen isn't entirely representative of what I see in the field in my own application, but it's close enough. This codepen is actually identical to https://codepen.io/wolframhempel/pen/b8d8f23d4354d58f6a53f96a3e83753d except that I have modified it to load the latest releastr of Golden Layout (v1.5.9).

Please try replacing the _$setSize function by the following:
_$setSize: function( width, height ) {
	if( width !== this.width || height !== this.height ) {
		this.width = width;
		this.height = height;
		this._contentElement.outerWidth( width )
		     .outerHeight( height );
		this.emit( 'resize' );
	}
}

@PerBothner That works well, much better, why don't you do a pull request.


Update _missing_translations_fr.json

Here we go again.
Meaning changes:

solution: changed meaning a bit, you can google translate for literal translation changes
packagers: "emballeur" has a more irl vibe (eg packing w cardboard), "empaqueteurs" is ok-ish, maybe a bit too french but keeping "packagers" feels too english so would say that's the best choice

Thanks!


Power issues with NU7026 (includes tests.zip)

Testing samsungctl with a UE55NU7026. Windows 10 python 3.7.2 32bit.

master does not power on the TV consistently. Once paired, all operations work right (used via library or command line).
develop branch does not detect the TV via command line already read #106

Ran RUN_ME.py, which detected and paired with the TV. Including
tests.zip
I'm specially interested in the power-on quagmire. A iOS app SamRemote does power on consistently.
Any ideas or things to try?

Moved to #106


s3 encryption-policy - use custom policy

Can we define a custom bucket policy to enforce?  I want to only allow upload encryption with a specific key id but deny use of the master/generic key.

Not at the moment, but that sounds reasonable, it looks like aws added support for key Id in policies mid last year.
http://docs.aws.amazon.com/AmazonS3/latest/dev/amazon-s3-policy-keys.html#object-keys-in-amazon-s3-policies

@kapilt any progress on this one?  Any thoughts? thanks....

@willjgillen We are intending on adding RSN an add-bucket-policy-statement (or some such name) action to allow bucket policy statements to be added to a bucket.


not working with patch 3

it does not work on patch 3

i think you installed it incorrectly

skill issue?

No it is working now


Fix Purview Readme issues

Fix issue https://github.com/Azure/azure-sdk-for-python/issues/19012
@jameszliao-msft , @mikekistler , @lmazuel and @jongio for notification.

@jameszliao-msft , @mikekistler , @lmazuel Could you please review this PR?

/azp run python - purview - ci

@mikekistler  Could you please help merge this PR?

@lmazuel  Please help review this PR. If there is no problem, please help merge this PR.


In  in GroupEdit/handleSubmit function - Fixing edit group fetch + utilizing unused variable

Love the blogs and tutorials!
As discussed in blog article comments, the put fetch was not hitting the correct endpoint so we just changed the address it hits there.
It looks like csrftoken was extracted from state in handleSubmit function, but was not used causing a warning in console. Referred to this variable and warning goes away.
(it looks like in a previous PR https://github.com/oktadeveloper/okta-spring-boot-react-crud-example/pull/11 this was added, so i guess its up to you if you want to delete the variable and refer to state directly, or refer to the variable)

If the free tee shirt offer still stands, happy to discuss!

Thanks for the fix @fatcatdog! Yes, the t-shirt offer still stands. Please send me an email to<EMAIL_ADDRESS>with your address and shirt size. You can also send a DM to @mraible on Twitter.


select component showing "Selecione..." helper text below the label when it should be hidden

In GitLab by @victoragcosta on Feb 16, 2022, 18:11

mentioned in commit b988b3f7302bbbbb36500e6cf863c8af76f8fc44


Lambda update behaviour

Is there a best practice to update the Lambda functions that already has been deployed?
Or do I need to make a new deploy?
I want some of the new features in sharp.js that has been added but I still want to use my existing distribution created from my first deploy.

@WeAreHaus to update the Lambda function only, you can use either build-s3-dist.sh script or npm run build in the image-handler directory to create a zip file. Then, you can upload the zip file to the Lambda function directly at the AWS Lambda console. It will only update your Lambda source code.


[Feature] Distributed Tools

Issue

Closes #637 and #1420
Change

Added tools via argument
Example:

Assistant assistant = AiServices.builder(Assistant.class)
                .streamingChatLanguageModel(streamingChatLanguageModel)
                .chatMemoryProvider(memoryId -> getChatMemory(memoryId))
                .build();

assistant.chat("What is 2+2?", calculatorTool);

assistant.chat("What is the weather in Milan?", weatherTool);

Added tool provider to select matching tools
Example:

ToolProviderResult bookingResult = new ToolProviderResult();
ToolExecutor executor =new BookingExecutor();
ToolSpecification specification = ToolSpecification.builder()
                .name("get_booking_details")
                .description("Returns booking details")
                .addParameter("bookingNumber", type("string"))
                .build();

bookingResult.add(specification, executor);

Assistant assistant = AiServices.builder(Assistant.class)
                .chatLanguageModel(chatLanguageModel)
                .toolsToolProvider((ToolProviderRequest request) -> {
                    if (request.getUserMessage().singleText().contains("booking")) {
                        return bookingResult;
                    }
                    return null;
                })
                .build();

General checklist

[x] There are no breaking changes
[x] I have added unit and integration tests for my change
[x] I have manually run all the unit and integration tests in the module I have added/changed, and they are all green
[x] I have manually run all the unit and integration tests in the core and main modules, and they are all green [I don't have access to MistralAI, but every test is green for OpenAI]

[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)
[ ] I have added/updated Spring Boot starter(s) (if applicable)

I have also noticed that you've implemented an ability to specify a tool inside the AI service method. Would you mind to exclude this from the current PR (I am not yet sure about this exact implementation)?

Yea sure. What implementation we are talking about exactly?
Are we talking about using tools like this:
assistant.chat("When does my booking 123-456 starts?", tools);

@MiggiV2 yes, exactly!

@MiggiV2 how is it going? Don't want to rush you, but do you have an estimate? I am asking because I plann to do a release tomorrow...

So. In my last changes, I don't override any context attributes anymore. Instead, new attributes were added with setters.
Should be it from my side. Excited to hear your feedback 😄

Just synced with main ⬆


Introduce the concept of capabilities

Capabilities are a new first-class concept in Gradle, living along variants. They can be used to model
components which "provide the same capability". For example, two different implementations of the same
API can provide the same capability, but it's illegal to have both on the dependency graph: the user
must choose between one of the two.
This commit introduces the ability to declare capabilities at the variant level, for now only using
component metadata rules. Capabilities participate in conflict resolution: as soon as we find that two
modules in the graph provide the same capability, we fail. There's currently no way to prefer one over
the other (this is going to be implemented in a subsequent commit). This means that if such a conflict
occurs, the user must select the right module appropriately using component selection rules or module
metadata rules.

@bigdaz This is ready for a more complete review.

Thanks for the initial review, @bigdaz . I have fixed all your comments, I think. Note that I understand the PR contains a lot of things. I strongly suggest to take a look at it commit by commit, as I try to make each commit self-contained. Of course this is not the case for "review fixes" commits, which are updating existing code, but even for them I keep them contained.

I think you could have kept the scope smaller and delivered this functionality in multiple PRs. But the main issue was that it got late and I didn't allow enough time to do a complete review. My bad.

I could, but it would have been a big burden, as I would probably have created a PR per commit. I don't think it would have been particularly helpful there (also knowing that there was a previous implementation). So yes, timing wasn't right, as usual.

@bigdaz I have removed the "add implicit capability for each module" from this PR, and will do this as a separate PR.

Thanks, I will merge the PR and polish code in a follow-up.


Add support of SelectItem in ONNX-Chainer

This Pull Request addresses #8449. The implementation encodes an equivalent of the following NumPy snippet:
row_idxs = np.nonzero(np.ones(t.shape))[0]
n_cols = x.shape[1]
idxs = row_idxs * n_cols + t
output = np.ravel(x)[idxs]

I could have used Range to create row_idxs, but found that some of other ONNX conversion tools out there have not supported it yet. So I settled on the sequence of ConstantOfShape followed by NonZero to create the indices.
I'm not sure if I correctly used support decorator. Among the ops used in the implementation, ConstantOfShape is the newest one introduced in opset 9, and some ops have been updated in opset 11. So I set the argument to the decorator as (9, 11). It will be great if you can take a look at it.

@tkanmae Do you have special reason not to use GatherElements added from opset11? select_item could be repesented as GatherElements(Transpose(x), Unsqueeze(t)) (+ Squeeze) maybe.

@disktnk The reason I did not use GatherElements is that CoreML 3.0 does not support it. Thanks for the comments above. I will make changes as you suggested, hopefully in a few days.

CoreML 3.0 does not support it

I see. We'll make another PR to use GatherElement when opset_version >= 11, and this alternative logic is remained to support under opset_version < 11 environnment. thx

@disktnk

We'll make another PR to use GatherElement when opset_version >= 11, and this alternative logic is remained to support under opset_version < 11 environnment.

Got it.
I fix the bug in testing select_item() conversion as you suggested, though I set opset_version to [1, 2, 3, 4, 5, 6, 7, 8] because ConstantOfShape is available from opset 9. I confirmed that the test passes on my machine.

Jenkins, test this please!

Jenkins CI test (for commit 12376f535eac8a8bcc6b16d9a1ab4565a9a5298b, target branch master) succeeded!

thx! The travis fail is unrelated to this PR, so merge this manually. (The error has already resolved by another PR).

Jenkins CI test (for commit 12376f535eac8a8bcc6b16d9a1ab4565a9a5298b, target branch master) succeeded!


Kotlin version upgrade fix issue #9

Upgraded Kotlin version from 1.2.7 to 1.3.0 since Android Gradle only supports Kotlin from version 1.3.0.

This version passes on debug, but it crashes on release
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:dynamicProfileRuntimeClasspath'.
   > Could not resolve project :pinch_zoom_image.
     Required by:
         project :app
      > java.lang.NullPointerException (no error message)

The error mentioned above was due to Gradle version on gradle/wrapper/gradle-wrapper.properties that was:
distributionUrl=https://services.gradle.org/distributions/gradle-4.10.1-all.zip
and I've change to:
distributionUrl=https://services.gradle.org/distributions/gradle-4.10.2-all.zip


Autopromote initial defaults to fluent defaults on fluent creation.

The problem class currently contains an initial default parameter that can be set in the constructor.
This is essentially useful to support some classes of problems (especially in PDDL), however it has several shortcomings:

it can only be set at problem creation, which means it can only be used for primitive types.
it is redundent with the fluent defaults. To know whether a given fluent has a default value, one would to check into two places.

This PR essentially, keeps the initial defaults construct as it is useful in a few contexts but modifies its usage.
However it changes its usage: whenever a new fluent is created with no explicit default, we check in the initial default whether this type has a global default and if so we associate it with the fluent.
This does not change any behavior but ensures that the default values are stored in a single place.

Apart the very minor comment, I think this PR is good and solves the issue in #112.
@mikand what do you think?

LGTM! @alvalentini merge at will! :smile:

Codecov Report

Merging #138 (cdf2aff) into master (684d73d) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #138      +/-   ##
==========================================
+ Coverage   93.25%   93.27%   +0.01%
==========================================
  Files          83       83
  Lines       10173    10170       -3
==========================================
- Hits         9487     9486       -1
+ Misses        686      684       -2

Impacted Files
Coverage Δ

unified_planning/model/problem.py
85.42% <100.00%> (+0.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Moon River by A$AP Ferg unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> A$AP-Ferg-Moon-River

done


Add cdevents twitter account

Signed-off-by: Andrea Frittoli<EMAIL_ADDRESS>Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Does it follow the guidelines for new entries?
[ ] Have you added an SVG to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow logo guidelines?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post a link for you to preview your changes. Have you confirmed that they are correct and then added a comment to the PR saying "LGTM"?

LGTM. Andrea, sorry for missing to add the Twitter account before.


Proposal to fold accessibility meeting into frontends weekly meeting

Problem

There is not enough activity/bandwidth within the Jupyter accessibility community to make effective use of the current twice-monthly meeting blocks.
Proposed Solution

Merge accessibility meetings into frontends meetings:

Rebrand the existing weekly Wednesday Jupyter Frontends meeting to a Jupyter Frontends and Accessibility meeting.
Remove the existing alternating Thursdays accessibility meeting from the Jupyter Community Calendar.
Advertise that accessibility topics are welcome in all of the combined meetings but members of the accessibility subproject will make a particular effort to attend the first meeting of each calendar month.

While most accessibility meeting regulars are already also frontends meeting regulars, prioritizing this way should reduce the burden on accessibility contributors who prefer not to attend all four/five calls per month.

Additional context

This proposal has broad support from the accessibility community; see consensus-gathering at https://github.com/jupyter/accessibility/issues/148.
Unlike the recent merging of the lab and notebook subprojects into frontends, accessibility and frontends would continue to exist as two distinct subprojects.  This proposal is inspired by the combination of the server and kernels meetings.

Copying in my thoughts from https://github.com/jupyter/accessibility/issues/148#issuecomment-2168884746:
I am personally enthusiastic about this proposal.
As an accessibility council member, I expect our efforts would benefit enormously from the additional attention and expertise of the frontends community. Products owned by frontends represent a significant proportion of the accessibility improvements urgently needed across Jupyter. Sustaining meeting momentum would cease to be a concern. We would likely catch the attention of potential contributors who wouldn't otherwise know there was an accessibility effort to join.
As a frontends council member, I see only upsides to combining the two meetings. Accessibility should be a key consideration in any changes that impact lab and notebook users. Accessibility pitfalls may get caught earlier in design/implementation discussions, saving effort at the review stage. Frontends contributors who want to get more engaged in accessibility can get involved without an extra meeting to attend (especially valuable for folks in time zones where typical Jupyter meeting times are inconvenient).

@ohrely Thank you for opening this! We consistently get at least 10 attendees at most of our frontends meetings, and we rarely need the full hour, so I think that adding accessibility topics will be good for the group. Accessibility should be thought of as a core feature, not a special interest, in Jupyter front-end apps.

Should we start a vote on this?

By the way, I don't actually know how to call a vote in this repo, so I will leave that to someone else :D
I just left my last comment as a gentle nudge because don't want this to be left in limbo for too long :)

I'd like to give folks until Monday to comment on the proposal.  I'll open votes in both team compasses then if no objections are raised.

@ohrely Now that we've moved forward with this change, should this issue be closed, and should the a11y meeting on Thursdays be deleted from the shared Google Calendar? I have permissions to do both.

@JasonWeill, yes please update the Google Calendar when you get a chance! The old meeting is still showing up on the calendar for today, but it shouldn't. Here's my more detailed request on Discourse, which might be helpful:
I tried to see if I have access to the calendar account in Google, but it seems that I do not. Could someone with access to the calendar make the following two changes?

Delete the bi-weekly Thursday “Jupyter Accessibility Meeting”, starting with and including the meeting scheduled for today, July 11 and all subsequent
Retitle the weekly Wednesday “JupyterLab and Notebook frontends meeting” to “Jupyter Frontends and Accessibility”, starting with and including July 17 and all subsequent

@gabalafou Thank you for clarifying! Both of these are done. Closing this issue, as it appears that all work is done.


[Request] Retina-quality screenshots

Well done for a great lib.
Any chance of a retina-quality capture?

The lib is use a real browser with selenium and capture posts' node screenshot. Post width is 598px (by X / Twitter) and its not changing with resolution increasing. So, custom css code is required to increase screenshot quality but it can disrupt some features. CSS's scale feature can be used. I'm gonna try it.

Ah thanks for the clarification. Not a big issue, just thought maybe there was an easy fix. Thanks for looking into it.


What is the purpose of load_masked_position_encoding? What impact will it have on the outcome?

https://github.com/DQiaole/ZITS_inpainting/blob/main/single_image_test.py#L132

provide position information about the mask region. For the impact, plz refer to our paper.

provide position information about the mask region. For the impact, plz refer to our paper.

Thank you very much for your reply


Provide an alpine 3.19 based image

Thank you for taking the time to help improve Corretto.
If your request concerns a security vulnerability then please report it by email to<EMAIL_ADDRESS>instead of here.
(You can find more information regarding security issues at https://aws.amazon.com/security/vulnerability-reporting/.)
If your proposal is specific to Corretto docker images,
then you are in the right place.
Please proceed with the following.
Is your feature request related to a problem?
No, it's an enhancement
Describe a solution you would like
Alpine 3.19 has been released, it would be great to have Corretto docker images based on this new version so that downstream projects can benefit from the upgrades included in this new version of Alpine Linux.
Describe alternatives you have considered
Maintain our own, doesn't benefit the community.
Additional context
There are some know DNS resolution issues with 3.18 that is solved with 3.19

Hi, thanks for reaching out about this and for the PR. We won't publish these images to Dockerhub until our testing and verification process is complete, but we encourage you to build them and test your applications now if you're planning to move to alpine 3.19.  Assuming no blocking bugs are found these should be available on Dockerhub shortly after the 2024-01-16 patch release.

@benty-amzn  it's not related to this issue but... do we have plans to generate the docker tags for the latest java versions e.g <IP_ADDRESS>.1 and, <IP_ADDRESS>.1?

@benty-amzn it's not related to this issue but... do we have plans to generate the docker tags for the latest java versions e.g <IP_ADDRESS>.1 and, <IP_ADDRESS>.1?

Yes, those should go out today.

Those updates are on #192.
Resolving this since the alpine 3.19 PR is merged and should be available shortly, along with the new releases.


Error while registering broker with connector

I was trying to setup the testbed and followed the example guides.
at the following steps I am getting the error while trying to register the broker at the connector.
as per example are given here: https://github.com/International-Data-Spaces-Association/IDS-testbed/blob/master/PreparingPreconfiguredSetup.md#guide-for-preparing-and-validating-the-preconfigured-setup
Register Connector A at MetaData Broker: POST /api/ids/connector/update
At the Swagger UI of Connector A insert the following recipient url for message POST /api/ids/connector/update:

https://broker-reverseproxy/infrastructure

I am receiving message: "Unable to retrieve valid DAT".
I have followed the following guideline also, but doesn't help:  https://international-data-spaces-association.github.io/DataspaceConnector/CommunicationGuide/v6/IdsEcosystem/Broker

Please, can you provide a guide or a simple example where we can successfully create the following scenarios:
create a resource, offer, rules, catalogues, contracts,  policies  and both connector can consume or receive data including registering metadata broker.
It would be very helpful if we can have a simple producer-consumer working example at one place with basic connector example which can demonstrate the dataspace capabilities (basic functionalities such as creating offer, rules, policy, resource, registering, negotiating  and consuming). Too many documents complicate the process and confuse the users which one they should follow as a starting point.
Thank you for the help in advance!

Hello @raj-ritu17,
Please follow the IDSA Reference Testbed Installation guide detailed here.
There it is detailed the hardware requirements and in a few commands how to deploy the preconfigured testbed.
When you have the testbed deployed please use the postman collection, there it is detailed a simple example which you just need to execute with Postman tool (DSC provider offers data, DSC’s are registered at the MDB and it is performed a contract negotiation).

Hi @raj-ritu17,
I hope that the proposed solution has helped you and that your problem has been solved.
Therefore, as there has been no reply form your side, I am closing this issue. If for any reason you still have the error, do not hesitate to reopen this issue and provide more information on the error.


Feature request: add an option to clean outDir on transpilation

Scenario: As a user, I would like to clean compilerOptions.outDir before transpiling. It is fairly understandable that it is not the default behavior since removing user data goes beyond the scope of a compiler responsibility. However, many users would find this very convenient during development process, notably:

when --watch mode on
to systematically avoid "dead leaves", i.e. obsolete sources and definitions

Such a compiler option could be labeled autoCleanOutDir and have boolean type.
Related issues: #13722

Duplicate of https://github.com/Microsoft/TypeScript/issues/16057

I close in favor of #16057


Refactor the if/else clause for sorting paged list

First time contributing... I think the call is a bit duplicated.  So I extracted the variable and removed the else clause.

@Thanonchai issue #92 created for you


Create a post test survey

Crate a survey for the prototype testing

The survey is available at:  https://insights.hotjar.com/s?siteId=284832&surveyId=13542


Improve Start Script Generation for Windows

adds an @echo off in front of all windows scripts and adds a pause statement after if auto restart is disabled. This is because people on windows tend to double click the start.bat instead of opening a terminal and running the script from there, which causes the terminal to close when the server stops without giving the user the option to look at e.g. crash logs, i have noticed a lot of people on the discord server just saying "my server stops without any crash log" because of this exact reason.

As a suggestion/question, would it make sense to put the pause statement behind a toggle that by default is turned on?

i didn't look into the component too much but as it looks to me that would require moving stuff around a lot so we can have different toggles for windows and linux. since i am very sure 90+% windows folks are gonna double click it i don't see much reason to have a toggle here.

I guess that's fair. I don't use the script generator anyway, and also didn't expect that much more work for a toggle so you have my approval (not that you need it, anyway)

i know this is technically completely out of scope for this pr (but opening a pr for this small thing is eeh) but shouldn't we have the gen add "nogui" instead of "--nogui" that way it will also work on older versions

i know this is technically completely out of scope for this pr (but opening a pr for this small thing is eeh) but shouldn't we have the gen add "nogui" instead of "--nogui" that way it doesn't crash on older versions

Yes, we should. Feel free to add that to this PR if you would like, and I will rename the commit on merge


Code completion bug, variable or function starting with '_'

Problem Description
Completing '_' or '__', no expected candidates
Completing '_test'  '_v'  '__test'  '__v', no candidates appear

However, the same operation is normal in spyder 3.3.6

Code
class TestClass(object):
    def __init__(self):
        self.var = None
        self._var = None
        self.__var = None
        self.___var = None
    def main(self):
        self._
    def testFunc(self):
        pass
    def _testFunc(self):
        pass
    def __testFunc(self):
        pass
    def ___testFunc(self):
        pass

Versions

Spyder version: 4.0.0b5
Python version: 3.7.3
Qt version: 5.9.6
PyQt version: 5.9.2
Operating System name/version: win7

There is something strange happening here.
I get completions for _ but it lists the triple ones first. With double underscore I get only the triples and with the triple underscores I get no completions.

I cannot reproduce this with the latest Spyder 4.1.2

Closing


[Question] Expo compatibility

Hello - first of all, thanks for the awesome library, I'm using it in multiple projects and it's always worked very reliably for me. I scoured the repo for information on Expo support and noticed that it's suggested to eject from Expo to use this library. While this makes perfect sense, with the advent of Expo dev clients and Expo config plugins, it's been increasingly possible to use previously-incompatible libraries with Expo managed workflow. Is that something you think this project and the ecosystem would benefit from? A similar library - react-native-mmkv - has implemented a way to automate the setup of the library in a way that it makes it compatible with Expo - see https://github.com/mrousavy/react-native-mmkv/commit/d0c6f016d6eaca47e7f517413c64d658ba09fbc9
Is that something that would possible here as well?
Thanks in advance!

@fobos531 give it a try with an expo project:
install from master:
 https://github.com/ammarahm-ed/react-native-mmkv-storage.git

then run expo prebuild

Thank you for the prompt response! I'm currently a bit busy with real-life stuff but I'll try it as soon as possible

install from master:
 https://github.com/ammarahm-ed/react-native-mmkv-storage.git

then run expo prebuild

Hello @ammarahm-ed ,
we tried in our project and seems working fine, thank you for your work!
Is there any plan to publish this version to npm?

@Wyctus i think the version on npm already published. The master branch is for next release.

@ammarahm-ed
Thank you, it works perfectly!
Could you please update the docs, so everybody can know about this great improvement?

@Wyctus  I have updated the docs.

Thank you very much!


[CLOSED] Add Platform Settings

 Issue by aravinve
Friday Feb 11, 2022 at 01:47 GMT
Originally opened as https://github.com/neel1996/mimock/issues/26

To add a table platform settings holding master data for the mimock platform.
Based on the master table configuration the platform functionalities are enabled/disabled.
Configuration should be allowed to modify only for admin scoped user.
Add separate endpoint and resource path to handle this functionality.
Tentative Colums include: (TODO)

isCategoryExecutionEnabled
isStepsExecutionEnabled
isExportImportEnabled
isFlushRecycleBinCronEnabled

Use case:
Mimock platform will be self hosted by users in the build pipeline as per their needs and wants targeting different environments.
Platform settings provide the flexibility in extending the mimock platform for different types of users. Based on the settings configured by the admin they are allowed to fine tune the functionalities.
Examples:

Most users will not require category execution in pipeline. So I want to disable that function.
Some users have compliance not to flush the deleted mocks via cron.

 Comment by aravinve
Friday Mar 11, 2022 at 03:21 GMT

Completed.


Add titleDefault and titleTemplate

Hi there 👋🏻
This PR adds titleDefault and titleTemplate fields that mostly match the functionality of its inspiration, next-seo. These are two fields that I found myself trying to reach for when using astro-seo but realized they weren't available. I saw the line about "feature-parity with Next SEO" mentioned in the README.md, so I figured I'd open a PR for these two fields.
PR Includes:

[x] titleTemplate
[x] titleDefault
[x] Tests
[x] Updated README.md

An example use-case for these fields would be using the <SEO /> component within a <Layout> while getting the page title via props, like so:
<!-- contact.astro -- titleTemplate example, becomes "Contact - Website Name" -->
<Layout title="Contact">
    <!--  [...] page content -->
</Layout>

<!-- about.astro - titleDefault example, forgot to provide a title, fallback to "Website Name - Cool Tagline" -->
<Layout>
   <!-- [...] page content -->
</Layout>

<!-- layout.astro -->
<html lang="en">
   <head>
      <SEO
         charset="UTF-8"
         title={title}
         titleTemplate="%s - Website Name"
         titleDefault="Website Name - Cool Tagline"
      />
   </head>
<!-- [...] -->

One minor side note: I went with titleDefault instead of defaultTitle to keep it consistent with the other title prop names. Another option could be titleFallback, or defaultTitle would be fine as well.

@reaganchisholm Oh wow, I love this! Thank you for adding this and sorry for the delay in getting this merged. Will build a new version with this in it today. 👍


HAProxy: can't specify IPv6 addresses as  Listen Address in frontend

This can be solved by just adding a colon to frontends.bind <mask> in HAProxy.xml:
<mask>/^((([0-9a-zA-Z._\-\*:]+:[0-9]+(-[0-9]+)?)([,]){0,1}))*/u</mask>
I don't know if someone needs a more complete regex including unix domain sockets:
<mask>/^((((ipv4@)?([0-9.]+|\*)?(ipv6@)?([0-9a-f:]*|\*)?):[0-9]+(-[0-9]+)?|(unix@)?/[^ ]+),?)*/u</mask>
Alex

@ghostwheel42 thanks for your report and the suggested fix!

The fix can be tested by running the following CLI command:
opnsense-patch -c plugins ac38144462d35a47b1b2b34ab8fcf1964c5a6746


Glitch on large text_input

I wrote a little socket chat app w/ Mint tea, and for the most part it works great, but when the text input gets large enough to wrap around to the next line I get this rendering glitch:

It seems like it's duplicating the last rendered line every few frames maybe?
I'm using the "latest version of riot" branch on Mac, with kitty for my terminal and Fish shell, if that's helpful.

I'm facing the same issue.
let sentence =
  {|No description, website, or topics provided. Add a README with an overview of your project. The answer is nuanced. The language specification does not stipulate what order the components of pairs should be evaluated in. Nor did our semantics exactly determine the order.|}

let initial_model =
  {
    cursor_idx = 0;
    characters = string_to_characters sentence;
    text = Text_input.make (sentence ^ "\n") ~cursor ();
    output = paint Fg sentence;
    quitting = false;
  }

Rendering issue when typing anything:
https://github.com/leostera/minttea/assets/53475167/68f7860e-2eaf-4109-a119-a4f9f946f090


[Feature Request] ProjectM visualizer integrated as random backgrounds.

As of now, the options for backgrounds consist of lua scripted bg animations, prerendered background videos, song-specific supplied background videos, static background images, or none. ProjectM is an open source visualizer based on the legacy of milkdrop, a famous visualizer that originally came bundled with winamp. Allowing for a huge amount of user-created visualization presets, it would be very nice to have a dynamically rendered background visualization to go along with songs instead of having to settle for out of sync random background videos, the smaller pool of lua bganimations, or the static background images.
https://github.com/projectM-visualizer/projectm
Source code is above, there are already standalone packages for multiple OSes.
Describe alternatives you've considered
For the past few years I've MacGuyver'd a way of making this work involving Milkdrop/ProjectM, OBS, and Stepmania Supplying a prerendered video of a specific color and having that be the only video in the randomMovies folder allowed me to control the background color without manually removing song bg images. Then using the chromakey filter in OBS and adding the visualizer as a lower layer, and further setting that visualizer to use the loopback audio input, I was able to achieve the proof of concept.
The problems with this are numerous, however. First, the music is always slightly ahead of the visualization since it uses the audio loopback. Therefore the visualizer response is never completely in sync with the audio. Furthermore, since it relies on chroma-key, whatever color is specified ends up having a bleed effect. For example, depending on the noteskin selection, some notes end up with the identified alpha and show the visualizer through them. It also makes it extremely difficult to balance the contrast and brightness of the note field with the background. Since it uses OBS, it exponentially increases ram and processing requirements in order to properly display the full output. It also requires a lot of finagling to tab through if someone accidentally uses the mouse on the OBS projector for displaying.
Having the ProjectM integrated would resolve most if not all of these issues.
Additional context
I would be happy to provide images or videos of the proof of concept to show what I am suggesting. Thank you very much for your consideration.

At some point I was actually suggesting either this or trying to modernize the old Winamp AVS code to work into it.


xread returns nothing

Redis 6.0.3
Python: 3.8.2
aioredis: 1.3.1
Nothing is returned by xread in aioredis. redis-cli returns the stream properly.
import asyncio
import aioredis

loop = asyncio.get_event_loop()

async def main():
    stream = 'chennai'
    fields = {
        'foo': 'bar'
    }

    redis = await aioredis.create_redis('redis://localhost', loop=loop)
    await redis.xadd(stream, fields)
    result = await redis.xread([stream])
    print(result)
    redis.close()
    await redis.wait_closed()

loop.create_task(main())

You need to pass latest_ids argument.
result = await redis.xread([stream], latest_ids=['0000000000000-0'])

Also use asyncio.run(main()) (python 3.7+) instead of explicitly creating a loop.

You need to pass latest_ids argument.
result = await redis.xread([stream], latest_ids=['0000000000000-0'])

That's weird. I thought I had tried that. Anyway, It's working. Thanks.

Also use asyncio.run(main()) (python 3.7+) instead of explicitly creating a loop.
That's just because I'm testing in a jupyter notebook. Can't use run.

Sorry for re-opening. Why doesn't $ work? I'm trying to draw parallels between the Redis tutorial and this library so I know what I'm doing.


Groups Cluster: AddGroup bugfix.

Problem
TC-G-2.2 fails due to an error in the AddGroup implementation. In src/app/clusters/groups-server/groups-server.cpp, the expression:
while (it->Next(entry) && !found)

Causes the entry to change before exiting the loop, so the value of entry is no longer the matching entry. Instead, the expression should be:
while (!found && it->Next(entry))

Change overview
Loop changed to correct the error, and make the logic clearer.
Testing
Groups, and Group Key Management tests executed correctly.

Accepted for master: high value fix for groups (fixing illegal memory access)


Status on Update for Changes in upcoming DNScrypt 2.0.29?

..like anonymous dns, logging improvements etc?

I will try to publish an update as soon as possible.

v0.6.6 doesn't seem pick up the update to 0.6.9 automatically?

@user8446 yes I have not updated the update.yml. I am working on 0.6.9.

Maybe someone wants to try 0.6.9 (preview with Anonymized DNS):
https://simplednscrypt.blob.core.windows.net/deploy/SimpleDnsCrypt/bin/x64/SimpleDNSCrypt_x64.zip

Ok now running 0.6.9 however I won't be able to test the Anonymized DNS since we need the logging and content filtering

Thanks for updating!


Mayor of Bartlett, TN

@jamesturk Are these PRs good to go? I want to be sure before I do any more.

looking good, it'd be OK to group them if you're doing a few at once, one muni per commit would be ideal still, but a few in one PR wouldn't be tough to review.  whatever's easiest


Added --disable-proxy

Version increase in setup.py will be taken up in another PR
Added --disable-proxy to go from a proxy scenario to a non proxy scenario
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

connectedk8s

@fengzhou-msft , review is done from the connectedk8s side. It is ready for checking in if you don't have any further reviews


NetworkInputStream

@alexanderkjall  thanks for merging the other PR.   So that I don't get too much divergence, I've raised the PR with the NetworkInputStream for you to get an idea of where I'm going with this.
There are test failures on this branch, however, as per other PR...   raising early for you to see the changes and where they are to avoid too much merge conflicts down the line...   once I can get it working.
One thing I believe I have wrong is the Portal / Query relationship.  I think the objects need to be the other way round.  Query is submitted and associated to a potential portal.   Once the query is undertaken more than 5 times (following pgjdbc), then can start naming the portal to associate.
Interesting is that (as per @davecramer on #19 ), is portal created:

for re-using the query and avoiding reparsing (prepared statements)
for cursors (note clear on how this works...  but assuming the creation of a cursor requires naming or something along these lines)

For first above an LRU cache would be ok.  For the second, LRU cache could create some "interesting" hard to reproduce errors.  For each, I'm thinking would need to manage separately.   However, for now prepared statements are my interest for performance.

Nice, I will read through it, but one thing regarding portals. I now realize that it's not mandatory to give the portals names.
But regarding named portals, those are state in the connection, and I think the server can deallocate them if it runs out of resources or by some other rule, so we need to determine what should happen if we try to use a named portal that no longer exist on the server end. I think we have two options

retry the statement/transaction.
propagate the error to the user.

Both have drawbacks, with 1 it means that statements might be executed in the wrong order and with 2 it exposes the user to something that should be the responsibility of the connection library.
This needs to be investigated further, maybe it's enough to set a upper limit on the number of named portals per connection.

2 it exposes the user to something that should be the responsibility of the connection library

So you're thinking of automatically creating named portals for the user? I think named portal (i.e. named statement) features are for the user to opt-in to if they are reusing things. Then the error is theirs since they created it.

@alexanderkjall   I'm not sure of this, however, I'm wondering if the database sends a notification if it is deallocating a portal.  But I'm guessing if we following patterns in pgjdbc (i.e. the create portal only after 5 queries) this would be a good start.  I don't believe we need to "reinvent the wheel" for this driver.  For me, we are just creating a new driver that takes all the pgjdbc patterns except opens up:

asynchronous calls
pipelining of queries, made possibly by asynchronous calls

Hence, for me, I'm going to fix the Portal/Query to follow pgjdbc as a starting point (to re-use all their experience).  Then once we have working (and deployed in a few applications for "real-world" use) we can then look for enhancements.

The server does not de-allocate Portals, nor does it send any message saying it did de-allocate them

Aha, my misstake, I based it on that I got the message "prepared statement "q" does not exist" from this test https://github.com/pgjdbc/pgsql2/blob/bd92a7d0272fdaaa23b1311a92dc53a65698c688/src/test/java/org/postgresql/sql2/SelectDataTypesTest.java#L321 .
But after closer inspection of the network packets it turns out that something produces broken Bind packages. Lets track that issue in another thread, here; https://github.com/pgjdbc/pgsql2/issues/24

Ok, I tried to merge in the latest of master into this branch and found some significant changes to the NetworkOutputStream...  seems to have a lot of synchronized around the write buffer (so much so I'm thinking it would significantly degrade performance...   synchronize on each get of buffer is a lot of overhead at this level of performance).
The idea I was trying to achieve:

application runs with its own threads
application requests a submission of the network level
this submission works in producer/consumer fashion with separate consumer thread (in other words, the application threads can continue working without having to handle network details)
NioLoop thread is responsible for translating the submission into buffer data to send over the line.  It is also responsible for reading in that data and parsing back onto the submission (as this is single threaded, there is no synchronizing required for it)

Basically, the NioLoop does very little in the way of synchronizing its state, as it runs on a single thread (so no memory synchronizing is necessary).  It is only when this thread interacts with other threads (application thread submitting a submission or registered response handler is invoked on another thread) does there need to be any synchronizing

@sagenschneider I would also like to reduce the amount of synchronization, and I also discovered that the code still have a race condition even after I added the synchronization, sometimes the READ / WRITE registration happens in the wrong order, so one the selector gets a read only registration while there still is bytes to be written, debugging that right now.
The problem that led me to add the synchronization was in usage of the getCurrentBuffer function, sometimes a buffer could end up being used by both the query producing thread and the network thread, and that caused memory corruption and incorrect packaged being written to the network.
One way to reduce the synchronization would be to have a ConcurrentLinkedQueue as a handover point between the threads, and the query producing thread puts buffers that it's finished with on it, and the network thread pulls from it when it needs more data to write to the network.

Thought about this a bit more, and one way to do this would be to move the written buffers to the queue that the network thread reads when flush() is called, that way we shouldn't need any synchronization on writes. And if flush also wakes up the selector i think we can get around that other race condition.

Possibly, though I would like to keep the network thread without too much synchronizing internally.
Question:  can we make the submissions effectively immutable?
Ideally, I would be thinking:

Submission submission = new Submission(...)  // is immutable with final fields so no threading issues
submit(submission) is therefore able to put onto concurrent queue for network thread to pull off
network thread is free to run internally without synchronize
on results for submission, the network thread locks on the submission to make changes to the submission (e.g. loading of rows to referenced mutable result with possible result handlers - changes to this mutable, such as registering result handler, is via same lock)

The result is there is no "course grained" lock slowing down performance.  The only lock is within each submission on results.  As this is less likely to change frequently, there should be little lock contention causing slow down.
Note: if we start putting locks in the network layer, they typically end up being course grained locking.  As many threads will contend over the locks (network thread will contend with application threads submitting), this will show up as noticeable slow down.

I would be thinking:

application threads to submit to network thread (immutable submissions on concurrent queue, so no heavy synchronization overheads)
network internal buffers queues to be LinkedList (no concurrency required as same thread)
network thread results (add rows) to synchronize on the submission to load the results (fine grained locking that will least likely cause lock contention - most expensive costs to logs)

That sounds like working plan, only thing I can think about that would be tricky is that a submission can have futures as parameters.
How the results of the queries are supplied to the user is really out of scope for this issue but I think the best thing might be to have a ExecutorPool since the callback is a function that is supplied by the user.

Isn't that over complicating things a bit? Wouldn't it be enough to check if the future is completed with isDone() on the future, and if that is false just not pull anything from the queue of submissions?

It's a complicated way of saying, don't submit anything to the network queue unless it is ready for execution.
For me, there could be multiple "parallel" execution trees by the same client.   I would not assumed that there is any relationship between each branch of this execution tree (think of it like promise tree).  As each node is resolved, it can then submit it's "immutable network submission".
I would not queue one submission behind another submission due to future resolution.  This could:

starve a tree from being executed while a long running query is running
potential for starvation, as the future could be waiting on the next query submitted to the network

Basically, what I'm saying is that the network layer only receives "immutable submissions" that ready for execution.   If it contains a future that needs resolution, this should be handled at the higher layers.

Note: also we want to avoid "polling"...  once the final future is resolved for the node then the submission is sent to the network.   Otherwise, we end up having to poll the head of the queue waiting for isDone() to return true.

I don't think we can start reordering queries that the user send, that could severely break the users application.
Imagine two update queries that operate on the same rows, if we reorder them then a completely different result would be produced.

You can always ask on the http://mail.openjdk.java.net/pipermail/jdbc-spec-discuss/ list, I might have understood the api wrong :)

The latest version of the API have a comment section that specifically mentions this use case, let me quote:
 Not all {@link Operation}s need to be executed in the order submitted. The
 most common example is a mass insert. The order in which the records are
 inserted doesn’t matter. A parallel {@link OperationGroup} gives the
 implementation the freedom to execute the {@link Operation}s in any order. If
 some of the {@link Operation}s have
 {@link java.util.concurrent.CompletionStage} parameters this can be
 especially valuable.</p>


Not working on latest CN apk 1.36.0

The script managed to choose the correct battle and support. When the level is loaded, it seems it does not take a snapshot or cast any skills. I've tried new and old version of lua apks and scripts. Seems like there is some changes in the game apk itself.
Update: Running normally on my 8.1 phone. Failure encounted when using NOX V<IP_ADDRESS>.

Please post a screenshot of the battle screen.

it seems nothing change but the script didn't work

Hi, Xianbei233
CN Server was update UI, please update those image :
image_CN\battle.png
image_CN\result.png

@TW-Raino you could have opened a pull request, you know. :triumph:

so far so good, but it still too slow. the gap time between recognition to get choice, battle to battle is too long. I want to know where i can define and modify the value. i think the script can get 30% faster at least

AnkuLua's default click() method has a small delay.
You can try to use this "(BETA) Fast click and touch" option in AnkuLua's settings.