LTO deprected setAlignment warning

I got this warning when building in fuzzbench
afl-llvm-lto-instrumentation.so.cc:381:18: warning: 'setAlignment' is deprecated: Please use `void setAlignment(MaybeAlign Align)` [-Wdeprecated-declarations]
    AFLFinalLoc->setAlignment(4);
                 ^
/usr/local/include/llvm/IR/GlobalObject.h:81:3: note: 'setAlignment' has been explicitly marked deprecated here
  LLVM_ATTRIBUTE_DEPRECATED(void setAlignment(unsigned Align),
  ^
/usr/local/include/llvm/Support/Compiler.h:296:23: note: expanded from macro 'LLVM_ATTRIBUTE_DEPRECATED'
  decl __attribute__((deprecated(message)))
                      ^
1 warning generated.

Got also [!] WARNING: Mistyped AFL environment variable: AFL_LLVM_INSTRIM_SKIPSINGLEBLOCK=1
That is wrong, I coped the env var from the Reame

There is also AFL_QUIET so this warning should not be here anyway

fuzzbench align warning: which llvm version is that?
mistyped env var warning:
this might be because you use a specific checkout? because in trunk:
$ grep AFL_LLVM_INSTRIM_SKIPSINGLEBLOCK include/*.h
envs.h:    "AFL_LLVM_INSTRIM_LOOPHEAD", "AFL_LLVM_INSTRIM_SKIPSINGLEBLOCK",

I agree on the warning -> afl_quiet, just added that.

idk which LLVM version is, it is the OSS-Fuzz docker.
fuzzbench wants a specific checkout, I updated it now to the latest commit in master.

Probably is LLVM 8 I guess

That might be llvm 8. In the current state lto only builds with 9+ because the SplitEdge function produces bugs on older llvm versions


[Feature]: Add back the OCaml Kernel

What's missing?
The new version (Flake rewrite) does not feature anymore the OCaml Kernel, that I added (#162).
I would like to continue using this project with the OCaml kernel for jupyter.
Possible solution
It should only be a rewrite of the old merged solution. I will try myself to make it work and submit a PR by the end of the week.
Alternatives
No particular alternative.
Additional context
Feature was previously implemented by GH-163, closing GH-162.

Hey @fusetim
Sorry about the OCaml kernel being removed. I tried to port what you had done into the new architecture, but I could never get it working. I created a new branch as a starting point so you don't have to start from scratch. Let me know if you get it working.
https://github.com/tweag/jupyterWith/tree/feature/add-ocaml-kernel

I just noticed that I don't have the postInstall that you did. I wonder if that is the root cause of it not working.

I'm getting the following error but I'm not sure what package to add to provide the missing binary.
[I 2022-10-27 13:48:24.159 ServerApp] AsyncIOLoopKernelRestarter: restarting kernel (1/5), new random ports
Fatal error: cannot load shared library dlllwt_unix_stubs
Reason: dlllwt_unix_stubs.so: cannot open shared object file: No such file or directory

Thank you, I will take a look at that.

PR is up in #336.
Got some help from @thufschmitt to fix some runtime dependencies of the kernel. It is pretty hacky. If you know of a better way to fix it, feel free to suggest changes.
Fixes (re: hacks) were committed in https://github.com/tweag/jupyterWith/pull/336/commits/0346fe9f59940a874f2ed4da5259686cb98de5b0


Fix small discrepancy between closure example and output.

The example function prints 'this function has been called ' .. calls .. 'times', but the example output is shown as if the function just prints calls. Changed so that the output matches the code.

Thank you!


[Beta] iOS Overlay Doesn't Dismiss

Add overlay on iOS and when the preview comes up it doesn't go away.

Investigating further it doesn't look like it can be removed easily without looping into notifier and looks like it was supposed to always stay there from the apple api.

Closing as this seems to be expected and going to keep it kind of as a hidden feature


Can't login at captcha url generated by carelink_carepartner_api_login.py

I'm in the US, I have an active partner account. We also tried using the primary Connect account but couldn't login. While running the script I'm sent to resolve the captcha login at this url:
https://mdtlogin-ocl.medtronic.com/mmcl/auth/oauth/v2/authorize/login?action=display&sessionID=e2565272-660f-4d52-b29b-9101d4a69702&sessionData=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.ew0KICAgICJzZXNzaW9uIjogew0KICAgICAgICAic2Vzc2lvbklEIjoiZTI1NjUyNzItNjYwZi00ZDUyLWIyOWItOTEwMWQ0YTY5NzAyIiwNCiAgICAgICAgImV4cCI6MTcyOTIzMTAwMywNCiAgICAgICAgImN1cnJlbnRfdXNlcm5hbWUiOiIiLA0KICAgICAgICAiY3VycmVudF91c2VyX2NvbnNlbnQiOiJub25lIiwNCiAgICAgICAgImN1cnJlbnRfdXNlcl9yb2xlIjoiIiwNCiAgICAgICAgImN1cnJlbnRfdXNlcl9hY3IiOiIwIiwNCiAgICAgICAgImN1cnJlbnRfdXNlcl9hdXRoVGltZSI6IjAiLA0KICAgICAgICAiY3VycmVudF91c2VyX2F0dHJpYnV0ZXMiOiIiLA0KICAgICAgICAic2FsdCI6IiIsDQogICAgICAgICJ0aGlyZF9wYXJ0eV9zc29fdG9rZW4iOiIiLA0KICAgICAgICAidGhpcmRfcGFydHlfc3NvX3Rva2VuX3R5cGUiOiIiDQogICAgfSwNCiAgICAicmVxdWVzdF9jb25zZW50Ijogew0KICAgICAgICAiY2xpZW50X25hbWUiOiJNQUcrQXV0aG9yaXphdGlvbitTZXJ2ZXIiLA0KICAgICAgICAic2NvcGVfdmVyaWZpZWQiOiJvcGVuaWQrcHJvZmlsZStlbWFpbCIsDQogICAgICAgICJyZXNvdXJjZV92ZXJpZmllZCI6Imh0dHBzJTNBJTJGJTJGbWR0c3RzLW9jbC5tZWR0cm9uaWMuY29tJTJGKiINCiAgICB9LA0KICAgICJyZXF1ZXN0X3BhcmFtZXRlcnMiOiB7DQogICAgICAgICJkaXNwbGF5IjoibG9jYWwiLA0KICAgICAgICAicHJvbXB0IjoibG9naW4rY29uc2VudCIsDQogICAgICAgICJpZF90b2tlbl9oaW50IjoiIiwNCiAgICAgICAgImxvZ2luX2hpbnQiOiIiLA0KICAgICAgICAiYWNyX3ZhbHVlcyI6IiIsDQogICAgICAgICJhY3JfdmFsdWVzX2Vzc2VudGlhbCI6IiIsDQogICAgICAgICJjbGllbnRfaWQiOiJjNzE2YWMzNS1hZTViLTQ4NzAtYmZhMS01NTMwYzY1OTUyZjkiLA0KICAgICAgICAibm9uY2UiOiIiLA0KICAgICAgICAic2NvcGUiOiJvcGVuaWQrcHJvZmlsZStlbWFpbCIsDQogICAgICAgICJyZXNvdXJjZSI6IiIsDQogICAgICAgICJtYXhfYWdlIjogIiINCiAgICB9DQp9.TUzRjXgMv8oeL_TxabvvoUqLLvLhYfqg3AgLgeWwTKo&locale=&countrycode=
I can, however, login here which is a slightly different base url that comes up when web searching "carelink login"
https://mdtlogin.medtronic.com/mmcl/auth/oauth/v2/authorize/login?action=display&sessionID=a84472de-e942-4796-b0ec-a982aa2ca840&sessionData=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.ew0KICAgICJzZXNzaW9uIjogew0KICAgICAgICAic2Vzc2lvbklEIjoiYTg0NDcyZGUtZTk0Mi00Nzk2LWIwZWMtYTk4MmFhMmNhODQwIiwNCiAgICAgICAgImV4cCI6MTcyOTIzMDc1OSwNCiAgICAgICAgImN1cnJlbnRfdXNlcm5hbWUiOiIiLA0KICAgICAgICAiY3VycmVudF91c2VyX2NvbnNlbnQiOiJub25lIiwNCiAgICAgICAgImN1cnJlbnRfdXNlcl9yb2xlIjoiIiwNCiAgICAgICAgImN1cnJlbnRfdXNlcl9hY3IiOiIwIiwNCiAgICAgICAgImN1cnJlbnRfdXNlcl9hdXRoVGltZSI6IjAiLA0KICAgICAgICAiY3VycmVudF91c2VyX2F0dHJpYnV0ZXMiOiIiLA0KICAgICAgICAic2FsdCI6IiIsDQogICAgICAgICJ0aGlyZF9wYXJ0eV9zc29fdG9rZW4iOiIiLA0KICAgICAgICAidGhpcmRfcGFydHlfc3NvX3Rva2VuX3R5cGUiOiIiDQogICAgfSwNCiAgICAicmVxdWVzdF9jb25zZW50Ijogew0KICAgICAgICAiY2xpZW50X25hbWUiOiJPQ0wtd2ViYXBwLVVTIiwNCiAgICAgICAgInNjb3BlX3ZlcmlmaWVkIjoib3BlbmlkK3Byb2ZpbGUrcm9sZXMiLA0KICAgICAgICAicmVzb3VyY2VfdmVyaWZpZWQiOiJodHRwcyUzQSUyRiUyRm1kdHN0cy5tZWR0cm9uaWMuY29tJTJGKiINCiAgICB9LA0KICAgICJyZXF1ZXN0X3BhcmFtZXRlcnMiOiB7DQogICAgICAgICJkaXNwbGF5IjoicGFnZSIsDQogICAgICAgICJwcm9tcHQiOiJsb2dpbitjb25zZW50IiwNCiAgICAgICAgImlkX3Rva2VuX2hpbnQiOiIiLA0KICAgICAgICAibG9naW5faGludCI6IiIsDQogICAgICAgICJhY3JfdmFsdWVzIjoiIiwNCiAgICAgICAgImFjcl92YWx1ZXNfZXNzZW50aWFsIjoiIiwNCiAgICAgICAgImNsaWVudF9pZCI6IjhmNDFhZjYyLWU3OTItNDQ4MS04ZDRjLWFlODQyMzE5ODQzZSIsDQogICAgICAgICJub25jZSI6IiIsDQogICAgICAgICJzY29wZSI6Im9wZW5pZCtwcm9maWxlK3JvbGVzIiwNCiAgICAgICAgInJlc291cmNlIjoiIiwNCiAgICAgICAgIm1heF9hZ2UiOiAiIg0KICAgIH0NCn0.Ajpii_2iRRQH9xX_hukP-QelMn2LPcNcPXUpQ9Jv0RQ&locale=en&countrycode=us
Maybe also worth noting that I tried the "Forgot Username" button through the captcha url but medtronic couldn't find an account with my username. I used that same username to login successfully via the url I found from my web search.
i also tried adding locale=en&countrycode=us to the captcha url since the landing page does seem specific to US and non-US and I still couldn't login.
Any help would be really great! I used this integration in the past to automate lights in my bedroom so I don't have to check my phone in the middle of the night if I'm worried about my partner. We really appreciate this work.

Same issue here.  It stopped working, seemed to have an expired token, and I cannot obtain new credentials via the script for the same reasons..
When I set is_us_region=True
The code provides this as the sso_url and the site does not exist
https://carelink.minimed.com/configs/v1/sso_cp_us_v6.json

I fixed this issue in a new pre-release. Anyone who can test this and confirm it is working?

Been running 24 hours and have maintained a connection. Forced a reload just now and still continuing to work and see logindata.json updated with expected timestamps.
Within the last 24 hours though, I do have 3 warnings that came up in logs. But they don't seem to have an impact as far as I can tell.

Detected blocking call to open with args ('custom_components/carelink/logindata.json', 'r') inside the event loop by custom integration 'carelink' at custom_components/carelink/api.py, line 412: token_data = json.loads(open(filename, "r").read()) (offender: /config/custom_components/carelink/api.py, line 412: token_data = json.loads(open(filename, "r").read()))
Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x14cdfd9839b0>,) inside the event loop by custom integration 'carelink' at custom_components/carelink/api.py, line 107: self._async_client = httpx.AsyncClient() (offender: /usr/local/lib/python3.13/site-packages/httpx/_config.py, line 149: context.load_verify_locations(cafile=cafile))
Detected blocking call to open with args ('custom_components/carelink/logindata.json', 'w') inside the event loop by custom integration 'carelink' at custom_components/carelink/api.py, line 404: with open(filename, 'w') as f: (offender: /config/custom_components/carelink/api.py, line 404: with open(filename, 'w') as f:)

Thought I'd report back in that it's been a couple days now and still running fine on the pre-release. Still have the same 3 warnings above, but again don't seem to have any impact as far as I can tell.

I'd love to be helpful and test the pre-release, especially since you all are kindly working on this issue. Alas, I spent about 90 minutes trying to fugre out how to interact with pre-release in my live environment and could not.
So sorry, I'm still learning how to be an active contributor. Once again, really appreciate this tool and the attention it receives!


Generate importance of all tunables and plots after the experiment

Signed-off-by: kusumachalasani<EMAIL_ADDRESS>Description:
Generate the importance of all tunables and plots after the experiment

Importance:
Generates the importance of tunables as json object after the experiment is complete in the log.

Plots:
Generates plots for tunables_importance, slice, optimization_history, and parallel_coordinate for all the tunables after the experiment completes. The plots are saved as cache in hpo in a directory called plots. For each experiment, it creates a folder inside the plots directory and the plots are saved. The plots can be accessed through the URL mentioned in the log output.
Note: contour plots are not generated as the plot hangs if there are more no.of tunables (like 31 tunables + 100 trial data). If using specific tunables to plot it works better - which is not part of this PR.

Output log for tunables importance:
2022-08-11 14:23:12 - INFO - bayes_optuna.optuna_hpo - TUNABLES IMPORTANCE:: {"AlwaysCompileLoopMethods": 0.09762756150924591, "NewRatio": 0.09609736984665643, "LoopUnrollLimit": 0.06821235138922051, "quarkus.datasource.jdbc.max-size": 0.06175839188432575, "MaxInlineLevel": 0.06056210175969281, "InlineSmallCode": 0.05529313793541708, "UseLoopPredicate": 0.04728835010604096, "gc": 0.04130452837904353, "UseTypeSpeculation": 0.033559474268803305, "UseSuperWord": 0.033559474268803305, "TieredCompilation": 0.033559474268803305, "ConcGCThreads": 0.033559474268803305, "CompileThreshold": 0.033559474268803305, "UseStringDeduplication": 0.03123606387490296, "quarkus.thread-pool.core-threads": 0.029428657114650543, "LoopUnrollMin": 0.02704307149816188, "BackgroundCompilation": 0.02316494684041285, "DoEscapeAnalysis": 0.02215576942018082, "UseInlineCaches": 0.020227845996300484, "quarkus.thread-pool.queue-size": 0.020021679071818167, "cpuRequest": 0.01969618295808506, "MinInliningThreshold": 0.01794144233135183, "AllowVectorizeOnDemand": 0.016779737134401652, "quarkus.datasource.jdbc.min-size": 0.01677973713440165, "MinSurvivorRatio": 0.015500279660071833, "TieredStopAtLevel": 0.0143658516862977, "StackTraceInThrowable": 0.014156677732970836, "nettyBufferCheck": 0.013548212063203832, "CompileThresholdScaling": 0.0020126813291282603, "FreqInlineSize": 9.329552540950751e-31, "memoryRequest": 5.685448766253697e-31, "quarkus.http.io-threads": 0.0, "AlwaysTenure": 0.0, "AlwaysPreTouch": 0.0, "AllowParallelDefineClass": 0.0}
Output log for plots information:
2022-08-17 12:34:51 - INFO - bayes_optuna.optuna_hpo - ACCESS tunable_importance CHART AT <REST_SERVICE_URL>/plot?experiment_name=experiment_tfb-qrh991&type=tunable_importance
2022-08-17 12:34:51 - INFO - bayes_optuna.optuna_hpo - ACCESS optimization_history CHART AT <REST_SERVICE_URL>/plot?experiment_name=experiment_tfb-qrh991&type=optimization_history
2022-08-17 12:34:52 - INFO - bayes_optuna.optuna_hpo - ACCESS slice CHART AT <REST_SERVICE_URL>/plot?experiment_name=experiment_tfb-qrh991&type=slice
2022-08-17 12:34:52 - INFO - bayes_optuna.optuna_hpo - ACCESS parallel_coordinate CHART AT <REST_SERVICE_URL>/plot?experiment_name=experiment_tfb-qrh991&type=parallel_coordinate

@kusumachalasani - Can you update the API design doc.

@kusumachalasani - Can you update the API design doc.

Done.

@kusumachalasani - Is there a default assumed for plot type?

@kusumachalasani - Is there a default assumed for plot type?

Yes, the default is tunables_importance.


bump Go version to latest UBI toolset (1.20.10)

Description
bump Go version to 1.20.
Also fixes golangci-lint issue no files to analyze in https://github.com/RedHatInsights/insights-results-smart-proxy/pull/1237
Fixes # (issue)
Type of change
Please delete options that are not relevant.

Bump-up dependent library (no changes in the code)

Testing steps
builidng both images
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.86%.  Consider uploading reports for the commit 8ebcd26 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1238   +/-   ##
=======================================
  Coverage   70.86%   70.86%
=======================================
  Files          25       25
  Lines        3964     3964
=======================================
  Hits         2809     2809
  Misses        871      871
  Partials      284      284

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Support for the experimental syntax 'decorators-legacy' isn't currently enabled

I recently created app with typescript by this article, and I have error when trying to apply decorator to a method
error screenshots: https://prnt.sc/l4nors, http://prntscr.com/l4np8r
tsconfig: https://pastebin.com/UsczCQ70

I got the same problem

@super918180 I fixed this issue with following steps:

Install @babel/plugin-proposal-decorators
Change .babelrc https://pastebin.com/QdddctRN

But I'm not sure that it is right way.

if you are using latest rn,the rn-cli.config.js should be like this
module.exports = {     transformer: {         babelTransformerPath: require.resolve('react-native-typescript-transformer'),     }, };
you can follow the metro-bundler document
https://facebook.github.io/metro/docs/en/configuration

if you are using latest rn,the rn-cli.config.js should be like this
module.exports = { transformer: { babelTransformerPath: require.resolve('react-native-typescript-transformer'), }, };
you can follow the metro-bundler document
https://facebook.github.io/metro/docs/en/configuration

It's work for me!

still bug decorators-legacy' isn't currently enabled

@andrey-shostik thanks! Could you please explain how your solution works?

@andrey-shostik I tried your solution. But it is different from the previous version.
export function Property(...args) {
    let len = args.length;
    if (len !== 2 && len !== 3) {
        throw new Error("@Property only supports on function and variable.");
    }
    ...
}

It works well in the the previous version, but got this error after updating.

Installing these two plugins and updating babel.config.js seems to be working for me:
  "plugins": [
    ["@babel/plugin-proposal-decorators", { "legacy": true }],
    ["@babel/plugin-proposal-class-properties", { "loose" : true }]
  ]

Error: Support for the experimental syntax 'decorators' isn't currently enabled
Issue: I'm currently experiencing an issue with Babel when trying to use decorators in my JavaScript code. I've followed the official Babel documentation and created a .babelrc.json file with the necessary configuration, but I'm still getting the error
hers is .babelrc.json
{
"presets": ["@babel/preset-env", "@babel/preset-react"],
"plugins": [
"@babel/plugin-transform-runtime",
["@babel/plugin-proposal-decorators", { "legacy": true }],
["@babel/plugin-proposal-class-properties"]
]
}
resolve this


How about setting HISTTIMEFORMAT by default

We always export HISTTIMEFORMAT="%y/%m/%d T " in ~/.zshrc after install oh-my-zsh. It's generally used so how about setting this by default?

It seems that zsh doesn't support HISTTIMEFORMAT yet.
I should close this with won't fix :smiley:

History time is stored in zsh by default you only need ativate the output for that in your .zshrc, there is even a commet telling what to do:

Uncomment the following line if you want to change the command execution time
stamp shown in the history command output.
The optional three formats: "mm/dd/yyyy"|"dd.mm.yyyy"|"yyyy-mm-dd"

Thanks @MyChaOS87 for telling me about that :smiley:

add one line HIST_STAMPS="yyyy-mm-dd" to file .zshrc, then source ~/.zshrc.

Sorry @Gnodiah it doesn't work for me :-(

@tobegit3hub Sorry I forgot to tell you I use oh-my-zsh, maybe you can try alias history='fc -il 1'

It works like a charm. Thanks @Gnodiah very much :smile:

@gnodiah Thanks for your advice, It works.


Allow configure custom certificates to collector

In the agent (sidecar mode) we allow user to set their custom TLS configuration, if we detect that the user set the flat reporter.tls.enable=true, we skip the automatic configuration.
That logic is not present on the collector, or in the agent in daemonset mode.  This PR fixs it.
Also added a couple of tests.
Signed-off-by: Ruben Vargas<EMAIL_ADDRESS>

@kevinearls would you mind reviewing this?


chore(azure-iot-device): ConnectionLockStage -> AutoCompleteStage

ConnectionLockStage was mostly unnecessary due to how the ReconnectStage works, so it was removed.
However, the functionality within it that auto-completed operations based on connection state was spun off into a new stage, since that logic is still quite necessary.

Gonna put this one on ice for now - development here discovered a bug blocking these changes, will implement a series of fixes in different PRs.


Loading not-public files from GCS bucket

I've my bag files over a Google bucket and webviz can load the files perfectly using allUsers with Storage Legacy Bucket Reader and Storage Legacy Object Reader permissions (Public to internet). But using allAuthenticatedUsers it fails showing the message: Error initializing player. Error: Fetching remote file failed.
Is anyway to make it work using allAuthenticatedUsers permissions ?. To reach the hosted webviz server actually is needed to be authenticated.

Hi @Klaudioz, you could set up the webviz server which can have full access to GCS bucket via a service account, and have the webviz client request a signed URL from the server which will bypass the auth issue you just mentioned. It's also more secure.

Thank you @vidaaudrey . Is any tutorial or documentation to do it ?. I've tried to deploy a webviz server in my kubernetes cluster, but it's not so easy like to do it with webviz.

Unfortunately we don't have any tutorial yet.  If you have a node express app set up, we could help review the code.  You could start by manually generating signed URL through gsutil and test if it works for you. Then set a simple server with the endpoint to generate signed urls that allows http://localhost:8080 to access. And finally you could modify the server code to server the static webviz files if needed.

Thanks for your answer. One thing I did was mounting the GCS bucket with bag files over the webviz container using gcsfuse. Is any way to make webviz able to read the mounted files ?. I couldn't find any way to set or configure the way that webviz runs.

I'm not sure how gcsfuse would work. If you can find some js client code to read the gcsfuse bag data, you could modify the PlayerManager code to build the player by using BagDataProvider or you create create your own data providers as well should you need some special data handling. BagDataProvider is easier to get started since it accepts either a local file path or a remote URL.

I'm not sure how gcsfuse would work. If you can find some js client code to read the gcsfuse bag data, you could modify the PlayerManager code to build the player by using BagDataProvider or you create create your own data providers as well should you need some special data handling. BagDataProvider is easier to get started since it accepts either a local file path or a remote URL.


added "--no-hidden" option to ignore all hidden files

Note! I've only tested it on Linux (Debian/Centos), don't know, if it will work on Solaris/*BSD

My preference is to not add exceptions, but find a way to handle this ignore option in the standard way.
To that effect, can you check out https://github.com/thehunmonkgroup/nagios-plugin-file-ages-in-dirs/tree/ignore-globs and see if that adjustment solves your issue without breaking existing functionality?
you should be able to do:
./check_file_ages_in_dirs --dirs /somedir -I ".* someotherignore"

hi @thehunmonkgroup,
yes you're right, I've actually tried the ignore option, but saw it doesn't work with globing, so hacked this "fast and dirty" solution. Anyway, your new script works as expected, I'll close this pull request. Thanks for fast response!
Best,
Stan


Use two sliding panel together ( sliding down and sliding up in same page)

I want to use 2 instance of this library in one page. one for sliding down ( currently using ) and one for sliding up ( needed ).
the problem is i should put sliding panel layout as parent in xml.
how can i use both together ?

I'm also trying to implement multiple sliding panels on a same page. I've defined a second sliding panel inside the content layout of my first panel. So far the second panel display is fine but it seems touch events are intercepted by the first one. Furthermore, the architecture can become really ugly when implementing more than 2 panels. Any thoughts ?

any solutions?


Unable to connect to pool "test"

I configured local indy network on AWS(not using docker) following the latest guide in indy-node.
I successfully cloned and built indy-cli-rs.

git clone https://github.com/hyperledger/indy-cli-rs
sudo apt-get install -y cmake cargo
cargo build (in indy-cli-rs directory)
cargo run (in indy-cli-rs directory)

I created "test" pool on my local network then

indy-cli-rs> pool create test gen_txn_file=/var/lib/indy/sandbox/pool_transactions_genesis)

Then I tried to connect pool, "Unable to connect pool test" error occurs.

indy-cli-rs> pool connect test

I couldn't find any error log or message except for "Unable to connect pool test"
How can I resolve it? Are there any references or error messages that I am able to find out?
Here's my pool_transactions_genesis file
{"reqSignature":{},"txn":{"data":{"data":{"alias":"Node1","blskey":"4N8aUNHSgjQVgkpm8nhNEfDf6txHznoYREg9kirmJrkivgL4oSEimFF6nsQ6M41QvhM2Z33nves5vfSn9n1UwNFJBYtWVnHYMATn76vLuL3zU88KyeAYcHfsih3He6UHcXDxcaecHVz6jhCYz1P2UZn2bDVruL5wXpehgBfBaLKm3Ba","blskey_pop":"RahHYiCvoNCtPTrVtP7nMC5eTYrsUA8WjXbdhNc8debh1agE9bGiJxWBXYNFbnJXoXhWFMvyqhqhRoq737YQemH5ik9oL7R4NTTCz2LEZhkgLJzB3QRQqJyBNyv7acbdHrAT8nQ9UkLbaVL9NBpnWXBTw4LEMePaSHEw66RzPNdAX1","client_ip":"<IP_ADDRESS>","client_port":9702,"node_ip":"<IP_ADDRESS>","node_port":9701,"services":["VALIDATOR"]},"dest":"Gw6pDLhcBcoQesN72qfotTgFa7cbuqZpkX3Xo6pLhPhv"},"metadata":{"from":"Th7MpTaRZVRYnPiabds81Y"},"type":"0"},"txnMetadata":{"seqNo":1,"txnId":"fea82e10e894419fe2bea7d96296a6d46f50f93f9eeda954ec461b2ed2950b62"},"ver":"1"}
{"reqSignature":{},"txn":{"data":{"data":{"alias":"Node2","blskey":"37rAPpXVoxzKhz7d9gkUe52XuXryuLXoM6P6LbWDB7LSbG62Lsb33sfG7zqS8TK1MXwuCHj1FKNzVpsnafmqLG1vXN88rt38mNFs9TENzm4QHdBzsvCuoBnPH7rpYYDo9DZNJePaDvRvqJKByCabubJz3XXKbEeshzpz4Ma5QYpJqjk","blskey_pop":"Qr658mWZ2YC8JXGXwMDQTzuZCWF7NK9EwxphGmcBvCh6ybUuLxbG65nsX4JvD4SPNtkJ2w9ug1yLTj6fgmuDg41TgECXjLCij3RMsV8CwewBVgVN67wsA45DFWvqvLtu4rjNnE9JbdFTc1Z4WCPA3Xan44K1HoHAq9EVeaRYs8zoF5","client_ip":"<IP_ADDRESS>","client_port":9704,"node_ip":"<IP_ADDRESS>","node_port":9703,"services":["VALIDATOR"]},"dest":"8ECVSk179mjsjKRLWiQtssMLgp6EPhWXtaYyStWPSGAb"},"metadata":{"from":"EbP4aYNeTHL6q385GuVpRV"},"type":"0"},"txnMetadata":{"seqNo":2,"txnId":"1ac8aece2a18ced660fef8694b61aac3af08ba875ce3026a160acbc3a3af35fc"},"ver":"1"}
{"reqSignature":{},"txn":{"data":{"data":{"alias":"Node3","blskey":"3WFpdbg7C5cnLYZwFZevJqhubkFALBfCBBok15GdrKMUhUjGsk3jV6QKj6MZgEubF7oqCafxNdkm7eswgA4sdKTRc82tLGzZBd6vNqU8dupzup6uYUf32KTHTPQbuUM8Yk4QFXjEf2Usu2TJcNkdgpyeUSX42u5LqdDDpNSWUK5deC5","blskey_pop":"QwDeb2CkNSx6r8QC8vGQK3GRv7Yndn84TGNijX8YXHPiagXajyfTjoR87rXUu4G4QLk2cF8NNyqWiYMus1623dELWwx57rLCFqGh7N4ZRbGDRP4fnVcaKg1BcUxQ866Ven4gw8y4N56S5HzxXNBZtLYmhGHvDtk6PFkFwCvxYrNYjh","client_ip":"<IP_ADDRESS>","client_port":9706,"node_ip":"<IP_ADDRESS>","node_port":9705,"services":["VALIDATOR"]},"dest":"DKVxG2fXXTU8yT5N7hGEbXB3dfdAnYv1JczDUHpmDxya"},"metadata":{"from":"4cU41vWW82ArfxJxHkzXPG"},"type":"0"},"txnMetadata":{"seqNo":3,"txnId":"7e9f355dffa78ed24668f0e0e369fd8c224076571c51e2ea8be5f26479edebe4"},"ver":"1"}
{"reqSignature":{},"txn":{"data":{"data":{"alias":"Node4","blskey":"2zN3bHM1m4rLz54MJHYSwvqzPchYp8jkHswveCLAEJVcX6Mm1wHQD1SkPYMzUDTZvWvhuE6VNAkK3KxVeEmsanSmvjVkReDeBEMxeDaayjcZjFGPydyey1qxBHmTvAnBKoPydvuTAqx5f7YNNRAdeLmUi99gERUU7TD8KfAa6MpQ9bw","blskey_pop":"RPLagxaR5xdimFzwmzYnz4ZhWtYQEj8iR5ZU53T2gitPCyCHQneUn2Huc4oeLd2B2HzkGnjAff4hWTJT6C7qHYB1Mv2wU5iHHGFWkhnTX9WsEAbunJCV2qcaXScKj4tTfvdDKfLiVuU2av6hbsMztirRze7LvYBkRHV3tGwyCptsrP","client_ip":"<IP_ADDRESS>","client_port":9708,"node_ip":"<IP_ADDRESS>","node_port":9707,"services":["VALIDATOR"]},"dest":"4PS3EDQ3dW1tci1Bp6543CfuuebjFrg36kLAUcskGfaA"},"metadata":{"from":"TWwCRQRZ2ZHMJFn9TzLp7W"},"type":"0"},"txnMetadata":{"seqNo":4,"txnId":"aa5e817d7cc626170eca175822029339a444eb0ee8f0bd20d3b0b76e566fb008"},"ver":"1"}
~
Version
Ubuntu = 20.04
Indy-node = 1.13.2
Indy-plenum = 1.131
Indy-cli-rs = 0.1.0

Where in relation to the nodes is the indy-cli instance?
Are you able to use nc from that location to ensure the node's client ports are open?
Are you able to connect to an existing network, Sovrin, BCovrin, or Indicio, using the indy-cli?
What is the state of the nodes/network?

sudo validator-info
sudo validator-info -v for more details
What steps/instructions did you follow for the installation and setup?

Things to verify:
cat /etc/indy/indy_config.py
- Ensure network configuration is correct.
cat /etc/indy/indy.env
- Verify node alias and IPs
cat /var/lib/indy/net3/domain_transactions_genesis
- Verify the correct content.
cat /var/lib/indy/net3/pool_transactions_genesis
- Verify the correct content.

Logs:
sudo systemctl status indy-node
sudo journalctl -u indy-node
sudo journalctl -u indy-node-control
/var/log/indy/<networkname>/<validator_alias>.log
/var/log/indy/node_control.log

If you determine you can connect to an existing network using the indy-cli, then this is not an indy-cli issue and I can transfer the issue to hyperledger/indy-node.  So, please start there.

Thank you for letting me know the exact point I have to check.
I check it out all of your suggestions.
It's the matter of IP setting.
Appreciate it.

To confirm.  The issue was with your indy-node configuration.  Correct?

Closing this as resolved.  Please reopen if this is not the case.


Add direct two-level hints table access.

This one is probably safe to merge, but I'd like some tests before I do so.
Do you have any ideas on getting clang/ld to emit a two-level namespace hints lookup table?
cc @UniqMartin

This one is probably safe to merge, but I'd like some tests before I do so.

I'd say “not quite” as you can infer from my code comments, as not all of them are purely stylistic.

Do you have any ideas on getting clang/ld to emit a two-level namespace hints lookup table?

I'd have to check what older versions are doing and whether I can dig up an ancient binary that uses this load command, but the linker bundled with Xcode 7.3.1 simply ignores the -twolevel_namespace_hints flag and the dynamic linker (dyld) on OS X 10.11 equally ignores the LC_TWOLEVEL_HINTS load command.

I'd say “not quite” as you can infer from my code comments, as not all of them are purely stylistic.

Definitely spoke too soon :smile:

I'd have to check what older versions are doing and whether I can dig up an ancient binary that uses this load command, but the linker bundled with Xcode 7.3.1 simply ignores the -twolevel_namespace_hints flag and the dynamic linker (dyld) on OS X 10.11 equally ignores the LC_TWOLEVEL_HINTS load command.

Yep, this is what I gathered while (trying to) make tests.


Use getLayout instead of baselayout

@chcn @gpang

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6470/
Test PASSed.

@gpang test added and improved tests

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6496/
Test PASSed.

@gpang PTAL thanks

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.1 please


Cookie data missing

Cookie data goes missing after updating app version.

Too vague, provide more info and re-open if you still struggle with this.


Added functionality to redirect to authors profile on Repo Card

https://buganizer.corp.google.com/issues/250524498
Added router-link component to the Large Repo Card in order to have similar functionality across Products (Repos and Blogs):

On clicking the author logo for repos it redirects to the authors profile - this was already implemented for blogs in earlier

One file changed: LargeRepoCard.vue

Thank you @mijaz18 . I tested on our dev environment seems to be working it.


Plugin version 4.0 - MockObject/Rule/InvocationOrder.php on line 27

Updating to version 4.0 caused my website to go offline. Disabling plugins and re-enabling them, I hit the following for the CloudFlare plugin.
Error message in WordPress

Parse error: syntax error, unexpected ':', expecting ';' or '{' in /{root}/{Web_Dir}/public_html/wp-content/plugins/cloudflare/vendor/phpunit/phpunit/src/Framework/MockObject/Rule/InvocationOrder.php on line 27

Inside the referenced file, I have the line;

public function getInvocationCount(): int

Which I assume is causing the issue

See #368

To confirm we've got the fix covered, what version of PHP and WordPress versions are you running?

🤞 fixed in #359

To confirm we've got the fix covered, what version of PHP and WordPress versions are you running?

PHP version: 5.6
WordPress: 4.9.16

@saintdle thanks for the update. unfortunately, you're running on an older version of PHP which we don't support anymore. you'll most likely need to stay on an older version of the plugin now. we've made the nessecary changes to the plugin to prevent breaking these installations however to continue benefiting from this plugin, i'd recommend upgrading your version of PHP and wordpress.


HDDS-1920. Place ozone.om.address config key default value in ozone-site.xml

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
94
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
625
trunk passed

+1
compile
391
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1884
branch has no errors when building and testing our client artifacts.

+1
javadoc
168
trunk passed

_ Patch Compile Tests _

+1
mvninstall
614
the patch passed

+1
compile
394
the patch passed

+1
javac
394
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
751
patch has no errors when building and testing our client artifacts.

+1
javadoc
172
the patch passed

_ Other Tests _

+1
unit
356
hadoop-hdds in the patch passed.

-1
unit
2066
hadoop-ozone in the patch failed.

+1
asflicense
41
The patch does not generate ASF License warnings.

6715

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.ozone.om.TestScmSafeMode

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.hdds.scm.pipeline.TestPipelineStateManager

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1237

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux a311d6461542 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3cc0ace

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/1/testReport/

Max. process+thread count
4682 (vs. ulimit of 5500)

modules
C: hadoop-hdds/common U: hadoop-hdds/common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/1/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
81
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
622
trunk passed

+1
compile
414
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1895
branch has no errors when building and testing our client artifacts.

+1
javadoc
177
trunk passed

_ Patch Compile Tests _

+1
mvninstall
557
the patch passed

+1
compile
365
the patch passed

+1
javac
365
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
735
patch has no errors when building and testing our client artifacts.

+1
javadoc
168
the patch passed

_ Other Tests _

+1
unit
364
hadoop-hdds in the patch passed.

-1
unit
230
hadoop-ozone in the patch failed.

+1
asflicense
36
The patch does not generate ASF License warnings.

4781

Reason
Tests

Failed junit tests
hadoop.ozone.om.request.s3.multipart.TestS3InitiateMultipartUploadRequest

hadoop.ozone.om.request.file.TestOMFileCreateRequest

hadoop.ozone.om.response.bucket.TestOMBucketCreateResponse

hadoop.ozone.om.request.volume.TestOMVolumeSetQuotaRequest

hadoop.ozone.om.request.key.TestOMKeyCommitRequest

hadoop.ozone.om.request.volume.TestOMVolumeSetOwnerRequest

hadoop.ozone.om.request.key.TestOMAllocateBlockRequest

hadoop.ozone.om.request.s3.multipart.TestS3MultipartUploadCompleteRequest

hadoop.ozone.om.request.s3.multipart.TestS3MultipartUploadAbortRequest

hadoop.ozone.om.TestS3BucketManager

hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse

hadoop.ozone.om.response.volume.TestOMVolumeSetQuotaResponse

hadoop.ozone.om.request.bucket.TestOMBucketSetPropertyRequest

hadoop.ozone.om.request.bucket.TestOMBucketCreateRequest

hadoop.ozone.om.request.s3.multipart.TestS3MultipartUploadCommitPartRequest

hadoop.ozone.om.response.volume.TestOMVolumeCreateResponse

hadoop.ozone.om.TestBucketManagerImpl

hadoop.ozone.om.request.file.TestOMDirectoryCreateRequest

hadoop.ozone.om.response.bucket.TestOMBucketSetPropertyResponse

hadoop.ozone.om.request.key.TestOMKeyCreateRequest

hadoop.ozone.om.request.volume.TestOMVolumeCreateRequest

hadoop.ozone.om.response.volume.TestOMVolumeSetOwnerResponse

hadoop.ozone.om.request.s3.bucket.TestS3BucketCreateRequest

hadoop.ozone.om.TestKeyDeletingService

hadoop.ozone.om.response.s3.bucket.TestS3BucketCreateResponse

hadoop.ozone.om.request.volume.TestOMVolumeDeleteRequest

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1237

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 3023c048fb18 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 00b5a27

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/2/testReport/

Max. process+thread count
1366 (vs. ulimit of 5500)

modules
C: hadoop-hdds/common U: hadoop-hdds/common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1237/2/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

/label ozone

/retest


Documentation (WIP)

WORK IN PROGRESS, DO NOT MERGE YET
I wrote initial drafts for both coding conventions and best practices.
More content, improvements and comments are more than welcome!

@nordsoftware/developers let's collaborate and write the best possible documentation.

Declare a component's initial state as a standalone instance variable even when a constructor is present:
Do

class Foo extends Component {
state = {isLoading: false}
}
class Foo extends Component {
state = {isKeyboardOpen: false}
constructor(props) {
super(props)
Keyboard.addListener('keyboardDidShow', () => {
  this.setState({isKeyboardOpen: true})
})

}
}

Do NOT do

class Foo extends Component {
constructor(props) {
super(props)
this.state = {isLoading: false}

}
}
class Foo extends Component {
constructor(props) {
super(props)
this.state = {isKeyboardOpen: false}

Keyboard.addListener('keyboardDidShow', () => {
  this.setState({isKeyboardOpen: true})
})

}
}

@crisu83, one thing (which I'm always trying to find): What goes where, and why it should be placed there. A.k.a folder / component-structure and where to put my-new-awesome-component-which-does-this-and-that?

I'd like to have more meat to the why sections - why do things as recommended here?
As an example: "The spread syntax is also a better way to both copy and concatenate arrays and objects."
Why is that? Might be trivial for daily JS coders, but as an ~comprehensive~ guide, this needs improvement imo.

My 5 cents is (also) WHY's for each example + maybe consider change "DO"and "DO NOT DO" to "good/bad practice"?

I agree with some of the comments above, that more why's are needed to really understand the benefit of doing it one way over the other. Also a bit more complex examples wouldn't be bad either. A practical example would be the await vs Promise, where deeply nested Promise handling gets really hard to read. Understanding the why's also gets easier if the examples show real benefits, instead of just syntax differences.
Otherwise, the coding conventions are pretty good, and I'm happy to see that most of those can and should be applied on the server side as well.

More whys = more wise :)

I've updated the documentation to reflect the comments so far and I also have some notes about future improvements. I think we're ready to merge this now, let's continue working on this documentation in named branches.


SWIFT_VERSION '5.0' is unsupported, supported versions are: 3.0, 4.0, 4.2. (in target 'InputMask')

My build keeps failing with this error:
SWIFT_VERSION '5.0' is unsupported, supported versions are: 3.0, 4.0, 4.2. (in target 'InputMask')

Xcode: 10.1
react-native: 0.59.8
react-native-text-input-mask:  ^1.0.1
Thank you

@hbaseline 	I'm not sure but this is probably related to your Xcode version:
https://swift.org/blog/swift-5-released/
https://developer.apple.com/documentation/xcode_release_notes/xcode_10_2_release_notes/swift_5_release_notes_for_xcode_10_2?language=objc

Upgrading Xcode to 10.2.1 solved the issue. Thank you

I downgraded library to 0.9.0 to get it work on xcode 10.1

I downgraded library to 0.9.0 to get it work on xcode 10.1

I was really happy when I read this comment but it keeps giving the same error.


Having to verify with Okta twice

Using this config:
[default]
username = MY_EMAIL
base-url = MY_OKTA_URL
duration = 3600
app-link = MY_OKTA_URL
role = arn:aws:iam::MY_AWS_UID:role:role/MY_AWS_ROLE

This is the debug output (sanitized):
REMMACD2ZWGTDY:aws ahjr$ okta-awscli --profile default --force --debug
DEBUG - Setting AWS role to arn:aws:iam::MY_AWS_UID:role/MY_AWS_ROLE
INFO - STS credentials are valid. Nothing to do.
INFO - Force option selected,                 getting new credentials anyway.
INFO - Authenticating to: MY_OKTA_URL
INFO - Authenticating as: MY_EMAIL
Enter password:
INFO - App Link set as: https://MY_OKTA_URL
Registered MFA factors:
1: Okta Verify - Push
2: Okta Verify
Please select the MFA factor: 1
INFO - Performing secondary authentication using: OKTA
DEBUG - [SOME_PII_SO_SNIPPED]
Waiting for push verification...
Multi-factor Authentication required.
Pick a factor:
[ 0 ] Okta Verify App: SmartPhone_IPhone: iPhone
[ 1 ] token:software:totp( OKTA ) : MY_EMAIL
Selection: 0
INFO - Okta Verify push sent...
INFO - Using predefined role: arn:aws:iam::MY_AWS_UID:role/MY_AWS_ROLE
INFO - Authenticating to: MY_OKTA_URL
DEBUG - Requesting a duration of 3600 seconds
INFO - Session token expires on: 2020-05-01 04:04:41+00:00
INFO - Temporary credentials written to profile: default
INFO - Invoke using: aws --profile default <service> <command>

Adding factor = OKTA to the config doesn't make a difference - I just don't get this part:
Registered MFA factors:
1: Okta Verify - Push
2: Okta Verify
Please select the MFA factor: 1

I still get 2 push notifications that I have to acknowledge.
Is there a config I'm missing?

This is because the Okta app that you're accessing is also enforcing MFA, along with the base org, so you're being prompted for each step.
There are some improvements to be had around the output to the user being clearer here, but the behavior is expected for this Okta configuration.

Thanks for this clarification @jmhale! I don't suppose it's possible to avoid needing to pick the factor the second time by re-using the factor setting in the config? (currently that appears to apply to the first choice only)


test-webui makefile target failing locally

Running  make test-webui locally fails with the following:
"Get codecov token": ERROR: (gcloud.secrets.versions.access) PERMISSION_DENIED: Permission 'secretmanager.versions.access' denied for resource 'projects/sixtor-0526/secrets/codecov-token/versions/latest' (or it may not exist).

This seems to be due to adding code coverage to the webui test in recent changes. It seems to expect a secret that exists in the project used by GitHub but not necessarily in the local developer's project.

Fixed in #106


{ BUG } Learn More Button on Windows Download Page is Broken

Bug Description
The "Learn More" button on the page located at: https://www.redotengine.org/download/windows is pointing to https://docs-latest.redotengine.org/about/introduction#about-redot-engine instead of https://docs.redotengine.org/en/latest/about/introduction#about-redot-engine which seems to be the correct URL.
Steps to Reproduce

Visit redotengine.org on a Windows computer.
Click the "Download" button located in the Hero at the top of the page.
Scroll to almost the bottom of the page, look for the heading "What is Redot Engine?"
Click the "Learn More ->" button.

Expected behavior
The introduction page in the latest version of the docs should be loaded.
Additional Details
Sorry my first submission is so lame. I'm just getting around to checking out Redot and noticed it while I was browsing. :)
Thx to the devs for all the hard work. The page looks absolutely amazing.
Operating System
Windows 11 - Release Channel - Current

The old website will no longer be updated; a new version will be released by the end of the year.

This is the repository for the new website; we will take this into account when implementing the download page.

This is the repository for the new website; we will take this into account when implementing the download page.


Get back when longPress on Windows button, open Shortcut Guide

Description of the new feature / enhancement
It is not new feature but it is cool feature. New "Open Shortcut Guide: Win + Shift + G" types is terrible.
Scenario when this would be used?
All time except selected "Disabled for Apps" list apps are running.
Supporting information
No response

Duplicate if #11963


Add support for custom options

This PR adds an Option data type. This allows the user to specify extra instances, pragmas, derivings, module replacements and imports.
It also improves the produced output: for our schemas, this program output invalid Haskell syntax: one issue was with case in do blocks and another was with let in do blocks. Both cases worked around now.
I make changes to types of the main entry points, generate and generateModules but if we really wanted to keep somewhat of a backwards compatibility, it's easy to simply add generateOpt and generateModulesOpt functions and define generate and generateModules in terms of them, simply supplying defaultOptions.
It'd be great if this could be release on Hackage soon. For us it means we no longer have to edit the generated modules by hand to make them work.
Thanks

Hey! Thanks for your contributions! I think it's fine to add extra options to generate and generateModules. Could you please document your changes in the changelog? I'm going release these changes as version 0.4 on Hackage when that's done.
Would you be interested in taking over maintainership of this package? I have lost my initial motivation for writing this package. In the last two years, I've only done some minor releases to keep up with new versions of the dependencies. You, on the other hand, are actually using the library (at work I guess) and now you probably know more about how this library works than I do.

Could you please document your changes in the changelog? I'm going release these changes as version 0.4 on Hackage when that's done.

Sure, tomorrow morning I'll add to the PR.

Would you be interested in taking over maintainership of this package? …

Sure, I could do it. My Hackage user name is MateuszKowalczyk. Pop me into maintainers and I'll see what I can do for it.

You, on the other hand, are actually using the library (at work I guess) and now you probably know more about how this library works than I do.

I doubt it, at least not yet :)

Added the changelog commit. Sorry it took so long, shifted focus to something else for a while.
I saw that you added me to this repo. If you don't mind, if I take over maintainership I would prefer to point from cabal file into my own checkout. It'd be great if you could add me to the maintainer group on Hackage too.
Thanks

I've added you to the maintainers group on Hackage. You can now release version 0.4. You can link to your own github repository if you want to.
(There's also the possibility to transfer this whole repository with all it's issues and the whole history of pull requests to your account. This will make Fuuzetsu/aeson-schema the central repository instead of just a fork. You'd have to delete your fork before a transfer is possible.)

OK, I was going to just ask github to remove fork status on my repo but didn't know you could transfer, I'll look into it, thanks.

Just want to say that I popped <IP_ADDRESS> on Hackage with a minor change (repo link) and will be disjoining the repo now. Thanks.

Can you please also take over ownership of aeson-schema in Stackage?

https://github.com/fpco/stackage/pull/780


Aggregations on date values return also a key 'value_as_string'

Hi Breadon. First of all: nice software: I had an itch, and I found it.
I have 2 problems, one is covered by #41, the other is that the resultset returns a value_as_string for a timestamp:
{
    "size": 0,
    "query": {
            "query_string": {
                "query": "somefield:somevalue"
            }
    },
    "aggs": {
        "max_timestamp": { "max": { "field": "Timestamp" } }
    }
}

This returns
{
....
    "hits": {
        "total": {
            "value": 10000,
            "relation": "gte"
        },
        "max_score": null,
        "hits": []
    },
    "aggregations": {
        "max_timestamp": {
            "value":<PHONE_NUMBER>019.0,
            "value_as_string": "2019-07-24T09:32:14.019Z"
        }
    }
}

I can easily find the line in parse_agg() that can skip this. I can't tell of find references to why this "value_as_string" is included, ES6 and 7 both return this extra field.
Can I change my query to not return that 'value_as_string' or is this a bug in the exporter?

Ah, this is the default for a date mapped field. I was too quick to name the issue. Renaming it.

I tried the extended_stats aggregation, and got this back (es6):
{
    "_shards": {
        "failed": 0,
        "skipped": 0,
        "successful": 4,
        "total": 4
    },
    "aggregations": {
        "ext": {
            "avg":<PHONE_NUMBER>666.1763,
            "avg_as_string": "2019-07-24 09:31:32.666",
            "count": 10604,
            "max":<PHONE_NUMBER>440.0,
            "max_as_string": "2019-07-24 10:54:10.440",
            "min":<PHONE_NUMBER>081.0,
            "min_as_string": "2019-07-24 08:15:38.081",
            "std_deviation": 2623278.6152724377,
            "std_deviation_as_string": "1970-01-01 00:43:43.278",
            "std_deviation_bounds": {
                "lower":<PHONE_NUMBER>108.9458,
                "upper":<PHONE_NUMBER>223.4067
            },
            "std_deviation_bounds_as_string": {
                "lower": "2019-07-24 08:04:06.108",
                "upper": "2019-07-24 10:58:59.223"
            },
            "sum": 1.6584239185032132e+16,
            "sum_as_string": "527503-08-15 18:57:12.132",
            "sum_of_squares": 2.593709820323737e+28,
            "sum_of_squares_as_string": "292278994-08-17 07:12:55.807",
            "variance":<PHONE_NUMBER>345.678,
            "variance_as_string": "2188-01-26 00:58:13.345"
        }
    },
    "hits": {
        "hits": [],
        "max_score": 0.0,
        "total": 10604
    },
    "timed_out": false,
    "took": 29
}

I'll add a testcase for this, and a possible fix.

Fixed in 0.5.2


Avoid adding "editor.tokenColorCustomizations" to settings

When editing an ASN1 file, the plugin always adds the following to my global settings.json file:
  "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": [
                    "asn1.keywords"
                ],
                "settings": {
                    "foreground": "#C586C0"
                }
            },
            ...

Is there any way to avoid this? The syntax highlighting color scheme does look good, but there sure must be a better way to provide defaults for this.

sorry. wrong ASN1 plugin :flushed:


no run cell commands at all after updating to  2020.11.0

Version: 1.51.1 (user setup)
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:34:32.027Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041
extension: 2020.11.0 (11 November 2020) v2020.11.358366026

I'm getting the following error when using my shortcut to run a current cell
command 'python.datascience.runcurrentcell' not found

I also tried to use right click menu

It didn't work either
And there is no any run cell commands at all:

I had to downgrade to v2020.10.332292344, version before that won't work either.

Even after downgrade to v2020.10.332292344, some UI seems to be broken as well. I don't use code lens and for some reason, it showed up and the color at the bottom is also way darker than before.


[e2e]: go workflow_dispatch main tagname-noldflags slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7650538592
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.workflow_dispatch.main.tagname-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.workflow_dispatch.main.tagname-noldflags.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Jan 25 06:09:13 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7664569489
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.workflow_dispatch.main.tagname-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.workflow_dispatch.main.tagname-noldflags.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Jan 26 06:10:59 UTC 2024
Tests are passing now. Closing this issue.


Component flickering nonstop NextJS

Tried using the typescript example and the component just flickers on the screen
see below

Issue is not seen on version
"react-datasheet-grid": "^4.5.0",
Issue is seen on version
4.6.0 and above
Version used in gif (latest)
"react-datasheet-grid": "^4.10.3",
Warning seen in terminal output:

Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client. See https://reactjs.org/link/uselayouteffect-ssr for common fixes.
at C:\Dev\eot\node_modules\react-datasheet-grid\dist\columns\checkboxColumn.js:44:51
at KeyComponent (C:\Dev\eot\node_modules\react-datasheet-grid\dist\columns\keyColumn.js:40:66)
at div
at Cell (C:\Dev\eot\node_modules\react-datasheet-grid\dist\components\Cell.js:9:17)
at div
at div
at div
at Grid (C:\Dev\eot\node_modules\react-datasheet-grid\dist\components\Grid.js:35:17)
at div
at C:\Dev\eot\node_modules\react-datasheet-grid\dist\components\DataSheetGrid.js:63:83
at C:\Dev\eot\node_modules\react-datasheet-grid\dist\components\StaticDataSheetGrid.js:22:11
at DataGrid (webpack-internal:///./src/features/dashboard/DataGrid.tsx:19:76)
at Home
at main
at div
at Layout (webpack-internal:///./src/components/layout/Layout.tsx:21:19)
at SessionProvider (C:\Dev\eot\node_modules\next-auth\react\index.js:453:24)
at MyApp (webpack-internal:///./src/pages/_app.tsx:19:18)
at Hydrate (file:///C:/Dev/eot/node_modules/@tanstack/react-query/build/lib/Hydrate.mjs:22:3)
at QueryClientProvider (file:///C:/Dev/eot/node_modules/@tanstack/react-query/build/lib/QueryClientProvider.mjs:40:3)
at TRPCProvider (file:///C:/Dev/eot/node_modules/@trpc/react-query/dist/createHooksInternal-de11647d.mjs:172:17)
at WithTRPC (webpack-internal:///./node_modules/@trpc/next/dist/index.mjs:47:83)
at StyleRegistry (C:\Dev\eot\node_modules\styled-jsx\dist\index\index.js:449:36)
at PathnameContextProviderAdapter (C:\Dev\eot\node_modules\next\dist\shared\lib\router\adapters.js:60:11)
at AppContainer (C:\Dev\eot\node_modules\next\dist\server\render.js:290:29)
at AppContainerWithIsomorphicFiberStructure (C:\Dev\eot\node_modules\next\dist\server\render.js:326:57)
at div
at Body (C:\Dev\eot\node_modules\next\dist\server\render.js:613:21)

Code used:
import { useState } from "react";
import type { Column } from "react-datasheet-grid";
import {
  checkboxColumn,
  DataSheetGrid,
  keyColumn,
  textColumn,
} from "react-datasheet-grid";
import "react-datasheet-grid/dist/style.css";

// Define your row type anywhere
type Row = {
  active: boolean;
  firstName: string | null;
  lastName: string | null;
};

function DataGrid() {
  // Type your data (not DSG specific)
  const [data, setData] = useState<Row[]>([
    { active: true, firstName: "Elon", lastName: "Musk" },
    { active: false, firstName: "Jeff", lastName: "Bezos" },
  ]);

  // Type your columns to get type checks in your IDE
  const columns: Column<Row>[] = [
    {
      ...keyColumn<Row, "active">("active", checkboxColumn),
      title: "Active",
    },
    {
      ...keyColumn<Row, "firstName">("firstName", textColumn),
      title: "First name",
    },
    {
      ...keyColumn<Row, "lastName">("lastName", textColumn),
      title: "Last name",
    },
  ];

  return <DataSheetGrid value={data} onChange={setData} columns={columns} />;
}

export default DataGrid;

Project build using T3 stack
Package.json file
{
  "name": "eot",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "build": "next build",
    "dev": "next dev",
    "postinstall": "prisma generate",
    "lint": "next lint",
    "start": "next start"
  },
  "dependencies": {
    "@headlessui/react": "^1.7.7",
    "@heroicons/react": "^2.0.13",
    "@next-auth/prisma-adapter": "^1.0.5",
    "@prisma/client": "^4.9.0",
    "@tanstack/react-query": "^4.16.0",
    "@tanstack/react-table": "^8.7.9",
    "@trpc/client": "^10.0.0",
    "@trpc/next": "^10.0.0",
    "@trpc/react-query": "^10.0.0",
    "@trpc/server": "^10.0.0",
    "@types/react-text-truncate": "^0.14.1",
    "next": "13.1.1",
    "next-auth": "^4.18.3",
    "react": "18.2.0",
    "react-datasheet-grid": "^4.10.3",
    "react-datasheet-grid-nextjs": "^4.4.9",
    "react-dom": "18.2.0",
    "react-text-truncate": "^0.19.0",
    "superjson": "1.9.1",
    "zod": "^3.18.0"
  },
  "devDependencies": {
    "@types/node": "^18.0.0",
    "@types/prettier": "^2.7.2",
    "@types/react": "^18.0.14",
    "@types/react-dom": "^18.0.5",
    "@typescript-eslint/eslint-plugin": "^5.33.0",
    "@typescript-eslint/parser": "^5.33.0",
    "autoprefixer": "^10.4.7",
    "eslint": "^8.26.0",
    "eslint-config-next": "13.1.1",
    "postcss": "^8.4.14",
    "prettier": "^2.8.1",
    "prettier-plugin-tailwindcss": "^0.2.1",
    "prisma": "^4.9.0",
    "tailwindcss": "^3.2.0",
    "typescript": "^4.8.4"
  },
  "ct3aMetadata": {
    "initVersion": "6.11.5"
  }
}

Defining fully all the column tables that are needed for my sheet stopped the flickering.

Defining fully all the column tables that are needed for my sheet stopped the flickering.

@vozmarkov what exactly did you do? I am experiencing the exact same issue.

Defining fully all the column tables that are needed for my sheet stopped the flickering.

@vozmarkov what exactly did you do? I am experiencing the exact same issue.

For my case, the flex: 1 was causing the layout recalculation loop, and the w-full overflow:hidden didn't solve the problem.
The solution was to wrap the component with the following div:

Defining fully all the column tables that are needed for my sheet stopped the flickering.

@vozmarkov what exactly did you do? I am experiencing the exact same issue.

For my case, the flex: 1 was causing the layout recalculation loop, and the w-full overflow:hidden didn't solve the problem.
The solution was to wrap the component with the following div:

  <DataSheetGrid...

I haven't been in that part of the code for long time but here is a snippet of my code.
It looks like I used dynamic grid with parent div set to h-80vh
  {isLoading && <Spinner containerClass="h-[80vh]" />}

    {!isLoading && (
      <DynamicDataSheetGrid
        height={height && height - 200}
        value={data}
        columns={columns}
        headerRowHeight={50}
        rowHeight={50}


AddressBar doesn't reflect state during time travel

Nice work getting this out! I'm excited to see this moving forward :)
I noticed that when running the example that the address bar doesn't track the changes to router state. I know this is still early but wanted to create an issue to track it.

Thanks! Should be fixed by https://github.com/acdlite/redux-react-router/commit/ca4225de1c5a656488ad761cf339932e72d4bd01


.on() with .subscribe() callback is not firing

Bug report
Describe the bug
Building a simple chat app with creat-react-app (React 18), supabase, chakra-ui, and react-query. I have a subscription that is definitely working as I can see the WS connection and incoming payload in the Chrome network tab, however my logic contained within the event callback is never fired. I'll include some code snippets below:
Here is my mutation logic:
const add: MessageStorage["add"] = async (messageNew) => {
  const { data, error } = await client
    .from<Message>("messages")
    .insert(messageNew)
    .single()
  if (!data) throw new Error(error.message)
  return data
}

export function useAddMessage() {
  const {
    mutate: addMessage,
    isLoading,
    error,
  } = useMutation<Message, unknown, Omit<Message, "id" | "createdAt">>(
    (partialMessage) => messageStorage.add(partialMessage),
  )
  return { addMessage, isLoading, error }
}

Here is my subscription:
export function useMessagesSubscription() {
  const queryClient = useQueryClient()

  const onEventChange = useCallback(
    (message: SupabaseRealtimePayload<Message>) => {
      console.log(message)

      queryClient.setQueryData<Message[]>(MessageQueryKeys.getAll, (prev = []) => [
        ...prev,
        message.new,
      ])
    },
    [queryClient],
  )

  useEffect(() => {
    const subscription = client
      .from<Message>("messages")
      .on("INSERT", onEventChange)
      .subscribe()

    return () => {
      client.removeSubscription(subscription)
    }
  }, [queryClient, onEventChange])
}

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
This repo is unfortunately private so recreating is understandably annoying but might be achieved via the following:

Create a react app with create-react-app and v18
npm i react-query @supabase/supabase-js @chakra-ui/react @emotion/react @emotion/styled framer-motion
Make sure you are running the latest stable release of supabase-js (v1.36.5)
Create a Supabase project
Add a table
Enable realtime Database -> Replication -> Turn on realtime for the given table.
Follow the steps for creating a Supabase client.
Copy and paste the above useEffect and replace table name with your table.
Listen to "INSERT" events
See if the callback is invoked after adding a row via the Supabase GUI.

Expected behavior
I would expect that when a new message is added that the callback within the .on() method would be invoked. Am I totally crazy, is this just a me problem? I've scoured the web only to find many people with the exact same solutions but not encountering the same problem.
Screenshots
https://user-images.githubusercontent.com/46500734/187945199-08ac76c0-eca0-4514-b996-1e4745883786.mov
System information

OS: macOS
Browser: Chrome
Version of supabase-js: 1.36.5
Version of Node.js: 16

If making my repo public helps expedite things, I'm happy to do so. Just let me know.

Actually I figured it out and am going to close this! I'm using React 18 with Strict Mode. My cleanup function was getting invoked and prematurely closing my subscription.

It appears this issue has been fixed in v2, so I look forward to that upgrade path :)

@thispastwinter yep, want to confirm that i fixed it in v2!


Updates for v3.4.0

Description

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 7388e990221cf563c26f8dbc3f6860284bd61e99
https://deploy-preview-2341--calico.netlify.com

Deploy preview for calico ready!
Built with commit 3195292cf96037d3ee5767c5edb7d09eef820378
https://deploy-preview-2341--calico.netlify.com

I've checked the netlify build and I think this down what I'm expecting (no updates to the drop-down list or site map yet) so I'm gonna merge this one.


Feature request needs.json reading

I have the usecase that several Sphinx projects are used to describe various parts of one software (we distinct between common parts & specific parts). All projects use the sphinxcontrib-needs extension. Now I want to be able to link needs in one project to needs in other projects.
Implementation proposal
The writing of needs.json was implemented in version 0.1.30.
This file could be made available for import into other projects. It would then be available in the Sphinx model and could be referenced like any other need. I'd use a new directive which I could add anywhere in the Sphinx project. I as use have to care about refreshing the needs.json file whenever a project gets updated. Ideally the directive would support not only local file locations but also HTTP URLs.

Great request.
I suggest a directive like .. needimport::
A usage incl. some options could look like:
.. needimport:: my_external_needs.json
   :version: 2
   :hide: false
   :filter: any filter rule (equal to needfilter directive)

Where:

version specifies the needs of a specific version to import. Default: Last found version
hide: specifies, if all imported needs shall get the hide-flag. Default: false
filter specifies a filter, which imports matched needs only

The idea of supporting HTTP-locations is also very nice.
So a project could simply make its needs.json file public and other sphinx-projects don't have the need to copy this file to a local folder. Would make it much easier to keep things in sync.


Fast FullSubNet m=infinity

Thank you very much for your excellent work and I'm replicating the results from your paper(Fast FullSubNet). I have reproduced the result of m= 2,8, but when m=infinity was reproduced, I could not get the result described in your paper for the moment. If it's all right with you, I hope you could provide me the model structure with m=infinity about the sub-model is removed. Thank you very much for your help and i am looking forward to your reply!

Thanks for your attention.
Please refer to the implementation below. If you run this model, you may find its performance is similar to $m=8$.
import torch
import torch.nn as nn
import torchaudio as audio
from torch.nn import functional
from torchinfo import summary

from audio_zen.model.base_model import BaseModel
from audio_zen.model.module.sequence_model import SequenceModel

class Model(BaseModel):
    def __init__(
        self,
        look_ahead,
        shrink_size,
        sequence_model,
        encoder_input_size,
        num_mels,
        noisy_input_num_neighbors,
        encoder_output_num_neighbors,
        norm_type="offline_laplace_norm",
        weight_init=False,
    ):
        """
        Simply FullSubNet.

        Notes:
            In this model, the encoder and bottleneck are corresponding to the fullband model and subband model, respectively.
        """
        super().__init__()
        assert sequence_model in (
            "GRU",
            "LSTM",
        ), f"{self.__class__.__name__} only support GRU and LSTM."

        # Encoder
        self.encoder = nn.Sequential(
            SequenceModel(
                input_size=64,
                hidden_size=384,
                output_size=0,
                num_layers=1,
                bidirectional=False,
                sequence_model=sequence_model,
                output_activate_function=None,
            ),
            SequenceModel(
                input_size=384,
                hidden_size=257,
                output_size=64,
                num_layers=1,
                bidirectional=False,
                sequence_model=sequence_model,
                output_activate_function="ReLU",
            ),
        )

        # Mel filterbank
        self.mel_scale = audio.transforms.MelScale(
            n_mels=num_mels,
            sample_rate=16000,
            f_min=0,
            f_max=8000,
            n_stft=encoder_input_size,
        )

        self.decoder_lstm = nn.Sequential(
            SequenceModel(
                input_size=64,
                hidden_size=512,
                output_size=0,
                num_layers=1,
                bidirectional=False,
                sequence_model=sequence_model,
                output_activate_function=None,
            ),
            SequenceModel(
                input_size=512,
                hidden_size=512,
                output_size=257 * 2,
                num_layers=1,
                bidirectional=False,
                sequence_model=sequence_model,
                output_activate_function=None,
            ),
        )

        self.look_ahead = look_ahead
        self.norm = self.norm_wrapper(norm_type)
        self.num_mels = num_mels
        self.noisy_input_num_neighbors = noisy_input_num_neighbors
        self.enc_output_num_neighbors = encoder_output_num_neighbors
        self.shrink_size = shrink_size

        if weight_init:
            self.apply(self.weight_init)

    @staticmethod
    def pad_length(tensor, win_length):
        """Pad the length of the tensor to be divisible by the win_length.
        Args:
            tensor: [*, T].
            win_length: window length.
        Returns:
            Padded tensor with the shape of [*, T_pad].
        """
        seq_len = tensor.shape[-1]
        remainder = seq_len % win_length

        pad_size = win_length - remainder if remainder > 0 else 0

        if pad_size > 0:
            tensor = torch.cat(
                (
                    tensor,
                    torch.zeros([*(tensor.shape[:-1]), pad_size], device=tensor.device),
                ),
                dim=-1,
            )

        return tensor, pad_size

    @staticmethod
    def unfold_time(input, kernel_size, stride):
        """Unfold (like sliding window) input tensor along the time axis.

        Shapes:
            input: [B, C, F, T]. PyTorch only support 4-D (image-like) tensor.
            kernel_size: Tuple with two values
            stride: Tuple with two values
            return: [B, C, kernel_size_1, kernel_size_2, N]
        """
        batch_size, num_channels, num_freqs, num_frames = input.shape

        # [B, C * prod(kernel_size), N]
        output = torch.nn.functional.unfold(input, kernel_size=kernel_size, stride=stride)
        num_blocks = output.shape[-1]

        # [B, C, kernel_size[0], kernel_size[1], N]
        output = output.reshape(batch_size, num_channels, *kernel_size, num_blocks)

        return output

    @staticmethod
    def time_fold(input, kernel_size, stride, output_size):
        """Fold (like sliding window) input tensor along the time axis.
        Shapes:
            input: [B, C, kernel_size[0], kernel_size[1], N]
            kernel_size: Tuple with two values
            stride: Tuple with two values
            output_size: Tuple of the spatial shape, e.g., (num_freqs, num_frames)
            return: [B, C, F, T]
        """
        batch_size, num_channels, ks_1, ks_2, num_blocks = input.shape
        input = input.reshape(batch_size, -1, num_blocks)  # [B, C * prod(kernel_size), N]

        output = torch.nn.functional.fold(
            input, kernel_size=kernel_size, stride=stride, output_size=output_size
        )  # [B, C, F, T]

        return output

    # fmt: off
    def forward(self, mix_mag):
        """
        Args:
            mix_mag: noisy magnitude spectrogram

        Returns:
            The real part and imag part of the enhanced spectrogram

        Shapes:
            noisy_mag: [B, 1, F, T]
            return: [B, 2, F, T]
        """
        assert mix_mag.dim() == 4
        mix_mag = functional.pad(mix_mag, [0, self.look_ahead])  # Pad the look ahead
        batch_size, num_channels, num_freqs, num_frames = mix_mag.size()
        assert num_channels == 1, f"{self.__class__.__name__} takes a mag feature as inputs."

        # Mel filtering
        mix_mel_mag = self.mel_scale(mix_mag)  # [B, C, F_mel, T]
        _, _, num_freqs_mel, _ = mix_mel_mag.shape

        # Encoder - Fullband Model
        enc_input = self.norm(mix_mel_mag).reshape(batch_size, -1, num_frames)
        enc_output = self.encoder(enc_input).reshape(batch_size, num_channels, -1, num_frames)  # [B, C, F, T]

        dec_input = enc_output.reshape(batch_size, -1, num_frames)
        decoder_lstm_output = self.decoder_lstm(dec_input)  # [B * C, F * 2, T]

        # Decoder - Fullband Linear Model
        dec_output = decoder_lstm_output.reshape(batch_size, 2, num_freqs, num_frames)

        # Output
        output = dec_output[:, :, :, self.look_ahead:]

        return output

if __name__ == "__main__":
    with torch.no_grad():
        noisy_mag = torch.rand(1, 1, 257, 63)
        model = Model(
            look_ahead=2,
            shrink_size=16,
            sequence_model="LSTM",
            encoder_input_size=257,
            num_mels=64,
            noisy_input_num_neighbors=5,
            encoder_output_num_neighbors=0,
        )
        output = model(noisy_mag)
        print(summary(model, (1, 1, 257, 63), device="cpu"))


Adds Selecting data section

This pull request adds a new section to exercises-doobie which explains how to select data from database.
@raulraja @dialelo Could you review when you have a chance? Thanks!

Other than the minor comment LGTM! Must fix the merge conflicts too.


Customizable "create new" for internationalization-friendliness

I'd like to add this feature for making it possible to internationalize the prompt for creating a new tag.
This widget is great, I'm hoping to make it available to the 🌍 .

Thanks for the contribution! Will release it and update it later today!


Fetch word and role from server

Game logic is being readjusted as time goes. Update commits will follow.


MAP cites isRepresentationOf, but that's not used in the MAP

https://github.com/sul-dlss-labs/taco/blob/d2ebc277a25ed68ccc7682282c8d45b7f435fbcf/maps/Collection.json#L168
Is this correct?

Yes, it is. IsRepresentationOf is a working field for pointing to RWOs.


jpeg corrupted, feature instead of bug. What about AVI?

I have been thinking about this https://github.com/ArduCAM/Arduino/issues/80 and I have decided to treat it as a feature instead of a bug. I have had trail cameras stolen before and there is a risk that my current project will be as well. If it is ever stolen I rather the thief not get anything usable. If all the camera takes is corrupted images most thieves would not bother to figure out why.
With that premise I am happy to treat the images that come off of the card as something akin to raw images that need post processing. I can figure out how to open a hex editor and change them one by one. To automate it I am thinking of having the camera save the files with a different extension then once in the computer, run a script to fix all of the pictures and change the extension to JPEG. I am on windows and I am fairly sure Autoit can do it just fine.
Thank you @aldobranti and @ArduCAM between your posts I should be able to figure out a script to fix the JPEGs.
I would like to be able to fix the AVIs as well. Any thoughts on what I should be looking for in the code on those?
Thanks.

Regards the avi files. There's likely some crap at the first bytes as the fifo wakes up in a mess. Compare with a good one ?
Sent from my BlackBerry® smartphone
-----Original Message-----
From: brandan<EMAIL_ADDRESS>Date: Fri, 09 Dec 2016 22:38:15
To<EMAIL_ADDRESS>Reply-To: ArduCAM/Arduino<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: [ArduCAM/Arduino] jpeg corrupted, feature instead of bug. What about
AVI? (#115)
I have been thinking about this https://github.com/ArduCAM/Arduino/issues/80 and I have decided to treat it as a feature instead of a bug. I have had trail cameras stolen before and there is a risk that my current project will be as well. If it is ever stolen I rather the thief not get anything usable. If all the camera takes is corrupted images most thieves would not bother to figure out why.
With that premise I am happy to treat the images that come off of the card as something akin to raw images that need post processing. I can figure out how to open a hex editor and change them one by one. To automate it I am thinking of having the camera save the files with a different extension then once in the computer, run a script to fix all of the pictures and change the extension to JPEG. I am on windows and I am fairly sure Autoit can do it just fine.
Thank you @aldobranti and @ArduCAM between your posts I should be able to figure out a script to fix the JPEGs.
I would like to be able to fix the AVIs as well. Any thoughts on what I should be looking for in the code on those?
Thanks.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/ArduCAM/Arduino/issues/115

@aldobranti, We have update the demo sketch and fix the dummy bytes before the JPEG marker FF D8.
https://github.com/ArduCAM/Arduino/tree/master/ArduCAM/examples/Shield_V2/ArduCAM_Video2SD


Error: No input network found in stdin.

I have already run  npm install -g transit-map and install the package.
But when I run  transit-map , there's an error as follow.
Error: No input network found in stdin.
So, what's the problem with my package? Could you please help me solve this problem?

You have to download a (transit) network as an input. E.g. the subways of Berlin from the examples folder of this repository.
Save the JSON on your computer and pipe it into transit-map:
npm install -g transit-map
wget https://raw.githubusercontent.com/juliuste/transit-map/master/examples/bvg.input.json
cat bvg.input.json | transit-map

{
  "nodes":
    [
      {
        "id": "900000096101",
        "label": "S+U Wittenau",
        "metadata": {
          "x": 537.043,
          "y":<PHONE_NUMBER>999999
        }

How do x and y correspond to latitude and longitude?

As far as I remember, you can use any projection to compute x/y from longitude/latitude. transit-map assumes they are already projected in a reasonable way, it only "cares" about the visual alignment of the stops, not about the "underlying" geographic location. You can of course use longitude/latitude directly as x/y, but the transit map will look distorted, depending on place on earth you're using transit-map for.

The scale will be completely ignored, but note that the optimizer restricts the angle for edges in the generated map to those closest to the angle of a line segment in the original map. So while the length will be ignored, the angles (which can correlate with the length of edges) are considered.

Please re-open if there are any remaining questions.

You have to download a (transit) network as an input. E.g. the subways of Berlin from the examples folder of this repository.
Save the JSON on your computer and pipe it into transit-map:
npm install -g transit-map
wget https://raw.githubusercontent.com/juliuste/transit-map/master/examples/bvg.input.json
cat bvg.input.json | transit-map

For further explanations on how to run transit-map, run:
transit-map --help

Dear all,
By running the abovementioned code in Windows Powershell, I still get this error (Error: No input network found in stdin in main [reference to appdata\npm\transit-map]) and I don't know why. Even if I save the example bvg.input.json-file in a dedicaded folder where I run the last command. Could it be related with the installation of Gurobi and AMPL? I downloaded the new packages, but it took me a great effort. Looking forward to the solution.
Kind regards,
Floor

@PanaderoCF Please provide the whole log of the commands that you have run, including their output.


Always showing Last provider state: preparing, iOS 16.1

Hi, shamanec. I'm grateful for your wonderful job.
I'm deploying and playing this project. My device is iPhone12 iOS16.1 (Dev mode on). WebDriverAgent app was installed into device and the sign was approved. But the web manager page is alway showing "Last provider state: preparing, t", and reinstalling the WebDriverAgent app automatically again and again. Could you help me? thx

Hey @defchen have you checked the provider logs either in the UI or in the provider.log file in its folder? Make sure you run it with --log-level=debug flag and provide me with the errors that you find :)

yep, found error logs.
{"event":"webdriveragent_xcodebuild","level":"debug","msg":"startWdaWithXcodebuild: Starting WebDriverAgent with command [xcodebuild -project WebDriverAgent.xcodeproj -scheme WebDriverAgentRunner -destination platform=iOS,id=00008101-001C2150116A0022 -derivedDataPath ./build test-without-building]","time":"2024-07-18T09:49:31+07:00"}
{"event":"ios_device_setup","level":"debug","msg":"goIOSForward: Forwarding port with command [ios forward 60676 9500 --udid=00008101-001C2150116A0022]","time":"2024-07-18T09:49:31+07:00"}
{"event":"ios_device_setup","level":"debug","msg":"goIOSForward: Forwarding port with command [ios forward 60677 9100 --udid=00008101-001C2150116A0022]","time":"2024-07-18T09:49:31+07:00"}
{"event":"ios_device_setup","level":"info","msg":"Successfully started WebDriverAgent for device 00008101-001C2150116A0022 forwarded on port 60675","time":"2024-07-18T09:49:36+07:00"}
{"event":"ios_device_setup","level":"debug","msg":"updateWebDriverAgent: Updating WebDriverAgent session and mjpeg stream settings for device 00008101-001C2150116A0022","time":"2024-07-18T09:49:36+07:00"}
{"event":"device_setup","level":"debug","msg":"Starting Appium on device 00008101-001C2150116A0022 with command [appium -p 60718 --log-timestamp --session-override --log-no-colors --default-capabilities {\"appium:udid\":\"00008101-001C2150116A0022\",\"appium:mjpegServerPort\":\"60677\",\"appium:clearSystemFiles\":\"false\",\"appium:webDriverAgentUrl\":\"http://localhost:60675\",\"appium:preventWDAAttachments\":\"true\",\"appium:simpleIsVisibleCheck\":\"false\",\"appium:wdaLocalPort\":\"60675\",\"appium:automationName\":\"XCUITest\",\"platformName\":\"iOS\",\"appium:deviceName\":\"iPhone\",\"appium:wdaLaunchTimeout\":\"120000\",\"appium:wdaConnectionTimeout\":\"240000\"}]","time":"2024-07-18T09:49:36+07:00"}
{"event":"device_setup","level":"info","msg":"Starting Selenium grid node for device 00008101-001C2150116A0022 with command [java -jar ./test/selenium.jar node --host <IP_ADDRESS> --config ./test/00008101-001C2150116A0022.toml --grid-url http://<IP_ADDRESS>:4444]","time":"2024-07-18T09:49:41+07:00"}
{"event":"provider","level":"info","msg":"Resetting LocalDevice for device 00008101-001C2150116A0022 after error. Cancelling context, setting ProviderState to init, Healthy to false and updating the DB","time":"2024-07-18T10:52:42+07:00"}
{"event":"ios_device_setup","level":"error","msg":"goIOSForward: Error waiting ios forward to finish for device 00008101-001C2150116A0022 - signal: killed","time":"2024-07-18T10:52:42+07:00"}
{"event":"ios_device_setup","level":"error","msg":"goIOSForward: Error waiting ios forward to finish for device 00008101-001C2150116A0022 - signal: killed","time":"2024-07-18T10:52:42+07:00"}
{"event":"ios_device_setup","level":"error","msg":"goIOSForward: Error waiting ios forward to finish for device 00008101-001C2150116A0022 - signal: killed","time":"2024-07-18T10:52:42+07:00"}
{"event":"device_setup","level":"error","msg":"startAppium: Error waiting for [appium -p 60718 --log-timestamp --session-override --log-no-colors --default-capabilities {\"appium:udid\":\"00008101-001C2150116A0022\",\"appium:mjpegServerPort\":\"60677\",\"appium:clearSystemFiles\":\"false\",\"appium:webDriverAgentUrl\":\"http://localhost:60675\",\"appium:preventWDAAttachments\":\"true\",\"appium:simpleIsVisibleCheck\":\"false\",\"appium:wdaLocalPort\":\"60675\",\"appium:automationName\":\"XCUITest\",\"platformName\":\"iOS\",\"appium:deviceName\":\"iPhone\",\"appium:wdaLaunchTimeout\":\"120000\",\"appium:wdaConnectionTimeout\":\"240000\"}] command to finish, it errored out or device 00008101-001C2150116A0022 was disconnected - signal: killed","time":"2024-07-18T10:52:42+07:00"}
{"event":"device_setup","level":"error","msg":"Error waiting for Selenium Grid node command to finish, it errored out or device 00008101-001C2150116A0022 was disconnected - signal: killed","time":"2024-07-18T10:52:42+07:00"}

WebDriverAgent seems to start successfully - it fails either with Appium or the Selenium Grid node commands. It's a bit hard to catch Appium errors because the command does not exit when a problem is found. I would suggest you first try to disable using Selenium Grid and try without it. If it still fails then you can find the respective device logs file and search through the Appium logs there - there might be an error displayed

I fixed errors above. I can connect devices. but new issue comes when I click any position on the screen mirror. It seems
it occurs on error positions.
{"ts":1721310207935,"msg":"--\u003e POST /session/1e6415c3-0d8b-49b8-8506-a25c6caa937f/actions {"actions":[{"type":"pointer","id":"finger1","parameters":{"pointerType":"touch"},"actions":[{"type":"pointerMove","duration":0,"x":66.0111706148408,"y":790.4407461155726,"button":0},{"type":"pointerDown","duration":0,"button":0},{"type":"pause","duration":10,"button":0},{"type":"pointerUp","duration":0,"button":0}]}]}","appium_ts":"2024-07-18 13:43:27:935","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310207938,"msg":"Calling AppiumDriver.performActions() with args: [[{"type":"pointer","id":"finger1","parameters":{"pointerType":"touch"},"actions":[{"type":"pointerMove","duration":0,"x":66.0111706148408,"y":790.4407461155726,"button":0},{"type":"pointerDown","duration":0,"button":0},{"type":"pause","duration":10,"button":0},{"type":"pointerUp","duration":0,"button":0}]}],"1e6415c3-0d8b-49b8-8506-a25c6caa937f"]","appium_ts":"2024-07-18 13:43:27:938","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310207938,"msg":"Executing command 'performActions'","appium_ts":"2024-07-18 13:43:27:938","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310207939,"msg":"Received the following W3C actions: [","appium_ts":"2024-07-18 13:43:27:938","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310207939,"msg":"Preprocessed actions: [","appium_ts":"2024-07-18 13:43:27:938","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310207949,"msg":"Matched '/actions' to command name 'performActions'","appium_ts":"2024-07-18 13:43:27:949","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310207950,"msg":"Proxying [POST /actions","appium_ts":"2024-07-18 13:43:27:950","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310208122,"msg":"Got response with status 500: {"value":{"error":"unknown error","message":"Invalid parameter not satisfying: point.x != INFINITY \u0026\u0026 point.y != INFINITY","traceback":"(\n\t0   CoreFoundation                      0x00000001a7761e94 5CDC5D9A-E506-3740-B64E-BB30867B4F1B + 40596\n\t1   libobjc.A.dylib                     0x00000001a0a8b8d8 objc_exception_throw + 60\n\t2   Foundation                          0x00000001a2079b4c C431ACB6-FE04-3D28-B677-4DE6E1C7D81F + 5528396\n\t3   XCUIAutomation                      0x0000000102b8e494 -[XCPointerEventPath initForTouchAtPoint:offset:","appium_ts":"2024-07-18 13:43:28:122","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310208123,"msg":"Matched W3C error code 'unknown error' to UnknownError","appium_ts":"2024-07-18 13:43:28:122","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310208127,"msg":"Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: Invalid parameter not satisfying: point.x != INFINITY \u0026\u0026 point.y != INFINITY","appium_ts":"2024-07-18 13:43:28:127","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}
{"ts":1721310208128,"msg":"\u003c-- POST /session/1e6415c3-0d8b-49b8-8506-a25c6caa937f/actions 500 193 ms - 1190 ","appium_ts":"2024-07-18 13:43:28:128","log_type":"1e6415c3","session_id":"1e6415c3-0d8b-49b8-8506-a25c6caa937f"}

Please add a comment with the Appium problem you encountered and close the issue :)

It works by using custom WDA from your fork repo.

@defchen can you please let me know how have you fixed reinstalling the WebDriverAgent app automatically again and again
https://github.com/shamanec/GADS/issues/109#issue-2415072639
kindly let me know the steps as I'm also facing the same issue


use Logger.warning

Resolves https://github.com/botsquad/graceful_stop/issues/5
As you are already testing against 1.14 in the CI, I figured it was okay to update the required elixir version (Logger.warning/1 was introduced in 1.11 and Logger.warn is deprecated in 1.15).
I also updated the VERSION file, just in case anyone runs this on an older Elixir version.

Woo! Looking forward to the new version being pushed to hex!
Thank you :heart:


Source orientations in get_point_spread()/get_cross_talk()

Describe the new feature or enhancement
get_point_spread()/get_cross_talk() can currently only deal with fixed orientations, even though the resolution matrix can be of dimension (n_orient_inv * n_dipoles, n_orient_fwd * n_dipoles). This is undesirable (one may be interested in PSFs/CTFs for different source orientations), and this is currently not dealt with properly. I would like to propose an additional option 'vector' for those functions in order to solve this.
Describe your proposed implementation
The new API could look a bit like this. It's a bit hairy to describe the different combinations of n_orientations for forward solution and inverse operator and their consequencies for PSFs and CTFs. The default options will hopefully be easy to interpret.
def _get_psf_ctf(resmat, src, idx, func, mode, n_comp, norm, return_pca_vars,
                 vector=False, verbose=None):
    """Get point-spread (PSFs) or cross-talk (CTFs) functions.

    Parameters
    ----------
    resmat : array, shape (n_orient_inv * n_dipoles, n_orient_fwd * n_dipoles)
        Forward Operator.
    src : Source Space
        Source space used to compute resolution matrix.
    %(pctf_idx)s
    func : str ('psf' | 'ctf')
        Whether to produce PSFs or CTFs. Defaults to psf.
    %(pctf_mode)s
    %(pctf_n_comp)s
    %(pctf_norm)s
    %(pctf_return_pca_vars)s
    vector: Bool
        Whether to return PSF/CTF as vector source estimate (3 values per
        location) or source esimate object (1 intensity value per location).
        Only allowed to be True if corresponding dimension of resolution matrix
        is 3 * n_dipoles.
    %(verbose)s

    Returns
    -------
    stcs : instance of SourceEstimate | list of instances of SourceEstimate
    PSFs or CTFs as STC objects.
    All PSFs/CTFs will be returned as successive samples in STC objects,
    in the order they are specified in idx. STCs for different labels will
    be returned as a list.
    If resmat was computed with n_orient_inv==3 for CTFs or n_orient_fwd for
    PSFs then 3 functions per vertex will be returned as successive samples
    (i.e. one function per orientation).
    If vector=False (default) and resmat was computed with n_orient_inv==3 for
    PSFs or n_orient_fwd for CTFs, then the three values per vertex will be
    combined into one intensity value per vertex in a SourceEstimate object.
    If vector=True, PSFs or CTFs with 3 values per vertex (one per orientation)
    will be returned in a VectorSourceEstimate object.
    %(pctf_pca_vars)s

Additional comments
There could be a separate example to illustrate this option, or I could add something to the existing one (but it would probably require a few figures).

no objection

@olafhauk do you want help here? It would be good if we could take care of not just https://github.com/mne-tools/mne-python/issues/8620 (and the related #10187) but also https://github.com/mne-tools/mne-python/issues/8737


[BUG] rgba is limited from :style in yuck

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
Is there a reason why rgba() behaves differently between cscc and yuck?
This works fine:
.music-player {
    background: rgba(#FF0000, 0.4);
}

This for some reason doesn't:
(box :class "music-player"
     :style "background: rgba(#FF0000, 0.4);"

It works fine without the opacity though:
(box :class "music-player"
     :style "background: #FF0000;"

To clarify what I am trying to do.
I have a var music-player-album-color in yuck and I want to make the music player widget have a dynamic color AND be semi-transparent. I can get to having either one of those but not both.
I have even tried setting a new scss variable from yuck but it seems anything set there operates on a different scope than what I write in scss so couldn't get this working as a workaround.
Is there a bug in how rgba() in handled from yuck or is this a limitation that is easy to overcome?
Reproducing the issue
Add the following to any widget
     :style "background: rgba(#FF0000, 0.4);"

Expected behaviour
the widget should get colored accordingly (40% transparent red)
Additional context
No response

Thanks @ovalkonia for the explanation, it is very informative.
I didn't want to use :css property as that would require me to specify the class again and I am not a fan of needless duplication.
For the time being I just changed my script that sets eww variable to output color in the 255, 0, 0 format instead of #FF0000 one and it is working for me with the :style propery. I would like to still use the hex format though with :style if possible.
Will give :css a try though when I get the chance to see if I'd like that.

I don't think you are actually required to specify the class again with the :css property. Take a look at the code that handles both :css and :style properties:

Here the only thing that differs between those two is the argument in the load_from_data method call. So :style "background: rgba($FF0000, 0.4);" would result in the argument being literally "* { background: rgba($FF0000, 0.4); }", with literal asterisk. If you want the :css property to behave the exact same way :style does but with SCSS support, just put it in the brackets here "* {  }". That's why :style "background: rgba($FF0000, 0.4);" and :css "* { background: rgba($FF0000, 0.4); }" should work exactly the same, just with the SCSS support.
Well, it's still not as clean as with the :style property, you have to repeat this * {  } pattern, but still not as bad as typing out you class name over and over again. It's up you what to use, but here's a possible way to do it

Ah I see, I expected * to apply to all widgets so I never tried it. Will give it a go shortly.

yeap, I updated my script to output hex colors again and with this I don't see any difference, meaning I am happy:
                ;; :style "background: rgba(${music-album-cover-color}, 0.6);"
                :css "* { background: rgba(${music-album-cover-color}, 0.6); }"

Awesome! I have no idea why the :style property doesn't compile the data into CSS using the grass crate as :css does. Vanilla CSS would work just fine either way. I will make a pull request, in case it wasn't intentional, and we'll see


The Windows (aka Super) Key isn't Emitted to WSLG

Environment
Windows build number: 10.0.22000.0
Your Distribution version: 20.04
Your WSLg version: 1.0.26

Steps to reproduce

Open a GUI which is supposed to respond to the Windows Key (such as QEMU or virt-manager)
Press the Windows Key
Notice, that Windows responds to the key rather than the GUI displayed using wslg

WSL logs:

pulseaudio.log
weston.log
versions.txt

Expected behavior
wslg should allow me to set whether the Win key should be redirected to wslg or the OS for individual windows.
Actual behavior
The Win key is always redirected to Windows.

Are there any updates on this?

A number of Linux gui applications are affected by this, emacs being one of them.  I'll happily take any work-around, too like reconfiguring the windows host, maybe adding some magic "super-key-prefix" on the windows side.

@froh, I have a workaround using AutoHotKey but it does not exhibit my ideal workflow. You can check it out on the AutoHotKey board forums here.