Legal Issues with application

Hey there Mytherin.
First, I have to say this project is amazing. I love the work you put into this, and I am learning quite a lot from reading your implementation.
I am a vice leader in a major guild, and I really wish to spread word of your tool here, but I have some concerns:

Why is there a AutoHotKey built into your app? AutoHotKey could easily be used to write bots (although simple ones), or have manasitting players. You went so far to show that your app is within legal bounds, and then you added this aspect to it.
What is the point of 'pathfinding' database? It this a tool to mark a path from point A to B, or walk it? Pathfinding is one of the keystones for creating a bot, and I worry this might be used to create bots (when combined with AutoHotKey and read mana/hp values).

Is it OK if I fork your work, remove the AutoHotKey part, and link that to my guild members? I will not touch the index page, so it still shows it is your project (and has the donation button).
If there is any other way to contact you aside from questions here, I would love to know about it.
Again, thanks for some amazing work!

The AutoHotkey integration is there to make remapping hotkeys easier for players and to provide the overlay that makes remapped hotkeys easier to use. AutoHotkey is completely legal, and has been confirmed by CipSoft to be legal, AS LONG AS you only ever do a 1:1 mapping (i.e. pressing one key combination maps to one other key combination) without any delays or loops or timers.
AutoHotkey can be used to make bots, but that's up to the players'  themselves. If a player uses AutoHotkey to make a bot, they are violating the rules. That has nothing to do with Tibialyzer or the legality of Tibialyzer.
The pathfinding database is used for marking paths from point A to B and showing the route to players. Currently it's used for showing directions to NPCs and to Hunting Places, although I would like to extend it to also show guides for quests. So it would tell you where to walk, and display the exact route you need to walk, during each step of the quest. Kind of like quest helper addons in World of Warcraft if you are familiar with those.
You could use the pathfinding as a basis to make a bot, but then if you wanted to create a bot there are Tibia Bots on Github already. If you want to make a Tibia bot you would be way better off cloning an existing Tibia bot rather than starting from Tibialyzer. It's not like pathfinding is particularly difficult, either.
And absolutely, feel free to fork the source code, and modify it in whatever way you want.

Thanks for the reply!
I know its all too easy to find code for tibia bots, but its one thing to look it up yourself, and another for me to link guildies with something that might draw them in :p
I understand your explanations, and accept them completely.
Thanks again for an amazing project!


build: turn off debug-info

it's mostly useless anyway, but could be overriden if needed. OTOH, it improves the build times and reduces the artifact sizes significantly which is very important in our case.

Current dependencies on/for this PR:

main

PR #140   👈

This stack of pull requests is managed by Graphite.


floyd algoritm java

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

not able to merge  pull request checks failed


📦 NEW: Add an option to sort data (#3) via @smitp

...

Thank you, @smitp — I'm adding a couple more new features and releasing the new CLI in a few.

Done. Check out https://github.com/ahmadawais/corona-cli/blob/master/changelog.md#release-210


test-branch/execute-job/wrong-commit-sha-on-pr/24938bc0-0c1c-4794-a3b5-d89b8cd161f4

PR for testing 6abb678b0dc469e8f73c7abccd97259a03f3aa9b

/canonical/self-hosted-runners/run-workflows 931ad21dd9ace68aaa0a7d341e94de96ad93fa6b


Cleanup of tests, solve duplicate panic handler error

Currently panic-halt and panic-semihosting collides during testing, generating this version dependent output in the output:
 error: duplicate lang item in crate `panic_halt` (which `$CRATE` depends on): `panic_impl`.
Error:   |
  = note: the lang item is first defined in crate `std` (which `$CRATE` depends on)
  = note: first definition in `std` loaded from /usr/share/rust/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-e12de7683a34c500.rlib
  = note: second definition in `panic_halt` loaded from $DIR/target/tests/target/x86_64-unknown-linux-gnu/debug/deps/libpanic_halt-f6dc7d4a3dd7a21d.rmeta

What is worse, the checksum changes with each new release of Rust causing testv7 and testv6 to break. Additionally, the path is the path found in the GHA build environment, making it overly cumbersome to use the TRYBUILD=overwrite variable because you most likely do not have your rust installation in /usr/share.
By removing panic-halt this conflict goes away.
Since there are no multi-core tests "single" in the path makes less sense. Rename to "tests".

Looks good, but not sure where the default panic handler comes from. Should that not be included instead?

Should have marked that initial work as a draft, wanted a go with the CI.
Should be updated and targeting the right branch now, to reduce merge-chaos for later.


[Bitwarden] [Feature] Add backup of persistant data

Sometime persistant data goes wrong and some people prefered having a backup on the same persistant volume.
Skeen has a nice solution for this, which is relatively easy to use:
https://github.com/Skeen/helm-bitwarden_rs/blob/master/charts/bitwarden/values.yaml

The idea of the chart is to expose the upstream features into a K8S deployment. I would not add a separate scheduler for backup unless it was officially supported by the upstream project.

@sgissi It is supported, the implementation like SKEEN does just copies the persistant data as a way of providing a backup. Which is certainly supported with sqlite and such.

Coming back to this lingering issue. I'll add a generic sidecar support, with this the users can choose an image that suits them to access the data.

Awesome :)

And finally, generic sidecar is now supported on all charts. Please reopen if you have issues using it.


Editing the .mustache files or translation files

First of al great tool you created! I downloaded this Github repository to test it on our local server.
I have only one question about changing the texts. I did the following steps:

First edited the translations files in etc/local, but when i visit the local client with my browser nothing changed.
Second I edited the text directly in the .mustache files, by replacing the i18n translation tags with plain text.
Both steps do not result in any changes because the browser keeps showing the old text.
Even after I flushed the Redis Cache, restarted the Thin Client and the server.

I seems that the .mustache files are being build by another process, can someone shed some light how i can make my changes visible in the browser?

Did you get this figured out?

I have same issue. How to rebuild templates/ clear cache?

There is no caching other than what thin is doing internally. If you edit the mustache files you should see the changes after restarting the process.
Is it possible you have multiple thin processes running?


pip3 install problem

My board is pynq-z2.
And, I tried to pip3 install git+https://github.com/Xilinx/QNN-MO-PYNQ.git,
but there was no any response after cloning.
Collecting git+https://github.com/Xilinx/QNN-MO-PYNQ.git
Cloning https://github.com/Xilinx/QNN-MO-PYNQ.git to /tmp/pip-bl5011_8-build
I had  waited for about 20min.
By the way, I could ping github.com.

You can try to first clone the repository on the board, then move to the folder and use the command pip3 install ./. The installation process is quite slow, and in the non-verbose mode not many information is given to the user about the status. You can try to execute pip3 with the flag -v to increase verbosity and check the installation status.


x/tools/gopls: deep completion misranked

See below screenshot. I expect &bytes.Buffer{} to be the first candidate, but for some reason packages are winning.

@muirdm: This is with gopls at master (and the deep completion CL), I assume?
/cc @heschik @dandua98

This is with gopls at master (and the deep completion CL), I assume?

Yes, master at e94ab72881893c257f5cecf9e0ed1b9d5c72f6e7. I've been noticing it for a while, though.

Was not able to reproduce on master, strange. Seemed to be ordered as expected for me.

It seems my editor has suddenly started changing the order of candidates for some reason 😠 . Sorry!


InputExampleRightCornerLabeled.js does not allow hex colors

Feature Request
use hex colors in InputExampleRightCornerLabeled.js
Problem description
I have an issue when wanting label to be #ff7675 color instead of "warning danger red"
Proposed solution
make use of hex color pallete

vs

Use style or follow our theming guide. We use predefined color palette from SUI.


TargetedEstimation benchmark

This benchmark can be included in the TargetedEstimation.jl repo:

[x] Define a UKBB-like task
[x] Define a set of typical estimation strategies
[x] Proceed to the run
[ ] Output the figures in the targene documentation runtime page with corresponding TargetedEstimation.jl version.

This is partly addressed by https://github.com/orgs/TARGENE/projects/1?pane=issue&itemId=18975135


closes #181 unlock via enter key

from master

@jhlx  which style do you prefer?
https://github.com/project-serum/spl-token-wallet/pull/182/commits/fb4b5e3110e10d425fd6a8d5919661bf22530465

I think the current PR looks fine. If you wanted to move the function out of the jsx, you could define it similarly to how the submit function is define (call it, say, handleKeyDown) then pass it in like so: onKeyDown={handleKeyDown}.

the current PR looks fine

then let's leave it as is...


Translate tasks/debug-application-cluster/debug-pod-replication-controller/ into Korean

This is a Feature Request

What would you like to be added

Translate tasks/debug-application-cluster/debug-pod-replication-controller/ into Korean.
Why is this needed
There is no documents with tasks/debug-application-cluster/debug-pod-replication-controller/ into Korean .
Comments

https://kubernetes.io/docs/tasks/debug-application-cluster/debug-pod-replication-controller/

/language ko
/assign

/close


Correct MM Derived Report for Holdings Statements Indexes for naming consistency

Ensure that the id and hrid have instance/item/holdings in front of these and the names use the property names. If the property name has camel, the name in the column will be that name all lower case and using underscore to separate words.
Link to report

Duplicate


Please fix UI of the app and Add Good ICON

So I'm using this app from Very beginning and personally i loved it sooo much. Thanks to you DEV ❤
I had some recommendations to improve the app.

Please fix it's UI ( ADD MATERIAL YOU UI ) AND ARRANGE WELL BUTTONS AND SETTING BUTTONS.
ADD AN OPTION TO SHOW OR CHECK UPDATE AND ALSO TO UPDATE WITHIN THE APP.

THANK YOU

Please fix it's UI ( ADD MATERIAL YOU UI )

Ok I will try making a newer design.

Do you have any suggestion how the icon itself should look like? I came up with this one because I was struggling to make one that represents the idea of "AntiSplit"/merging APKs

ADD AN OPTION TO SHOW OR CHECK UPDATE AND ALSO TO UPDATE WITHIN THE APP.

I already added it.

Yeah sure i can send you the icons with monet one
Here's my own recommendation but I can send your more i would need time to design them but i personally loved this one. There's no pressure if you don't like it i can create other for you.
This one is ( if you think this one need some changes like color and all lemme know )
https://uploadrar.com/s1p9prxsrrdd

@AbdurazaaqMohammed Maybe this icon style can works for your app.
P.S: Don't directly use this image, because it's broken in multiple parts due to low resolution and wrong cuts.

@AbdurazaaqMohammed Maybe this icon style can works for your app.
P.S: Don't directly use this image, because it's broken in multiple parts due to low resolution and wrong cuts.

This icon style can also appear better with total white elements and a colored background, like this

Yeah sure i can send you the icons with monet one
Here's my own recommendation but I can send your more i would need time to design them but i personally loved this one. There's no pressure if you don't like it i can create other for you.
This one is ( if you think this one need some changes like color and all lemme know )
https://uploadrar.com/s1p9prxsrrdd

Try to replicate mine too (if you want) with/without monet. 👍

@AbdurazaaqMohammed
With the help of a friend I make a simple logo: a broken - by jagged line - android logo (which resembles a bundle package) with a patch and the word APK printed above (which represent the goal of your app).
Give it a look and try it. 👍👍👍
P.S: One image with transparency, one with a white background and another with red one:

AntiSplit-M 4.zip
AntiSplit-M 3.zip
AntiSplit-M 2.zip
I have attached 3 more lemme know if you need more.

One thing you said is practically true about updates because it'll consume battery more, And i think that should be optional because this app is only for converting files to APK and i also thought it's not good idea adding update option. My intention for asking for update was because the app is in development and some changes are keep coming and i wanted to explore with each change and i had no idea when it's updates are releasing i manually had to check that's why i asked for adding update option.
But now i think it's better not to add update coz it'll run in foreground for checking updates and will drain battery. It has only one task and that's enough just add your github release page inside app so that user can easily navigate to release page and can download from there. This would be much better instead adding update option.

0xrxL suggestion is kind of what I had in mind (full sized android logo with a medical bandage aid), except that misaligned patch and especially the APK text inside, which kind of bothers me and I think it's unnecessary, but since I can't do anything better, I guess it's ok-ish (for now).
Hiaashuu - AntiSplit-M 2.zip is what I like more tho, mainly because it's "shiny" (not literally) and modern/fancy (sorry 0xrxL).

0xrxL suggestion is kind of what I had in mind (for full sized android logo with a medical bandage aid in the middle that seems to stitch together both parts across the jagged line), except that misaligned patch and especially the APK text inside, which kind of bothers me and I think it's unnecessary, but since I can't do anything better, I guess it's ok-ish (for now).
Hiaashuu - AntiSplit-M 2.zip is what I like more tho, mainly because it's "shiny" (not literally) and modern/fancy (sorry 0xrxL).
Material You ? > no thank you, it will probably need a library, most likely the compatibility with old OS vers. won't be the same and the size will increase, let's keep it simple as is - custom interface with a few more minor UI/UX improvements.
Hiaashuu IDK why you had to type in all caps in the OP (it's considered as shouting).

Don't worry xD, mine was just a proposal. In any case, if material you will not be , a better scalable and adjusted UI will it be for sure (toggle descriptions inside setting menu are too near, and difficulty understandable).

Yeah, about that - I suggested the following elsewhere:
Add grid lines to the settings, because currently it's a bit hard to tell right away which toggle for which setting it is, because on some the description is on multiple lines in ENg.

So today i found in a telegram group that someone has implemented some of the recommendations i was asking for in AntiSplit.

But I'm still waiting for your release. ❤ Hope to explore it soon.

...but they didn't even made it available for DL, just screenshots.

New brand design

Main screen
Settings
Dialog
Processing
Result

I went with this icon

I can see your effort Dev.  Now it's looking amazing. Tho for icon you opted for that one, that's fine. But yeah it's Great now, hope you release it soon.
And thank you for listing. ✨

I can see your effort Dev. Now it's looking amazing. Tho for icon you opted for that one, that's fine. But yeah it's Great now.
And thank you for listening ✨

Try to make the monet version of the icon. Should be easier enough, due to the absence of particular gradients.

@AbdurazaaqMohammed
Please also add a theme picker/switcher (like the mod in the SS, which btw I've DLed and installed as well out of curiosity), because currently in 2.0 can't be changed independently from the system, I guess also on A.5>9, there it's probably stuck to white with that purple accent, which I'm not a fan of, because there's no sys theme toggle (NightMode).

I have added theme switcher (light/dark/black) in the latest release

I have added theme switcher (light/dark/black) in the latest release

Add a material searchbar too, for the apps selector.

I have added theme switcher (light/dark/black) in the latest release

There's also a problem on settings. The titlebar with name settings it's too near to the toggle descriptions, while the close button is more distant and, therefore, also more readable.

Done both

Done both

Other two bugs found:

Console output is covered by the three below buttons.

Progress loading bar is too near to the apps selection button above.

Console output is covered by the three below buttons.

I kind of did it that way on purpose, otherwise there is a big empty space with only the buttons and it looks weird

Progress loading bar is too near to the apps selection button above.

Fixed

Remove the broken merged file, once the user click on the cancel merging button.

I tried to do it, it might not work without storage permission.

For the moment I can't see any new bug. 👍

If you can, please consider the
following:
One an update is DLed, there's a notification, but the app doesn't prompt to install just DLed update, it might do now, since I just allowed its install permission, but if it doesn't, it will be nice if it does.
On A.10 with Lite/White sys theme, the app is now dark/black by default (not a clean install and I'm OK with it not being in Lite), some might prefer the Ui to adapt to the sys, so a 4th Follow System or only "System" theme option is probably good to have.
I'm not a fan of the overflow buttons, especially when they get in the way hiding things behind, text in this case, so consider making them vertical instead of horizontal, to retract to a single button or a botto mergin, even tho you don't like how it looks, I suspect swiping up won't make the text visible and the buttons below it, like forcefully adding a bottom mergin (I like how 1DM handles this, or at least it used to when there are many DL tasks and the add overflow gets in the way - you can swipe up and it will go below the last task, not covering anything, but it doesn't do it by default, so it's an adaptable/dynamic mergin).

Once an update is DLed, there's a notification, but the app doesn't prompt to install the just DLed update, it might do now, since I just allowed its install permission, but if it doesn't, it will be nice if it does.

I actually hate this behavior in apps like Apktool M, because often I want to update the app, but I also want to do something else and don't want to wait for it to finish downloading and installing, so I want the notification so I can install it whenever I want

On A.10 with Light/White sys theme, the app is now dark/black by default (not a clean install and I'm OK with it not being in Light), some might prefer the Ui to adapt to the sys, so a 4th "Follow System" or only "System" theme option is probably good to have.

I added this option and made it check light/dark mode at first launch

I'm not a fan of the overflow buttons, especially when they get in the way hiding things behind, text in this case, so consider making them vertical instead of horizontal, to retract to a single button or a bottom margin/padding, even tho you don't like how it looks, I suspect currently swiping up won't make the text visible and the buttons below it, like forcefully adding a bottom margin/padding (I like how 1DM handles this, or at least it used to when there are many DL tasks and the add overflow gets in the way - you can swipe up and it will go below the last task, not covering anything, but it doesn't do it by default, so it's an adaptable/dynamic margin/padding).

Now you can swipe down the floating buttons

Thanks.
I prefer if the settings dialog didn't close upon changing the theme, which but flashes for a second (A.10) on launch before going dark, but I thing this is a global problem of Material 3 and some add a splash screen to avoid this (NextPlayer for example does the same), but I hate splash screens.
Other than that, I think you can close this or leave it open for a few more days.

Thanks.
I prefer if the settings dialog didn't close upon changing the theme, which btw flashes for a second (A.10) on launch before going dark, but I think this is a global problem of Material 3 and some add a splash screen to handle this (NextPlayer for example does the same), but I hate splash screens.
Other than that, I think you can close this or leave it open for a few more days.

Thanks. I prefer if the settings dialog didn't close upon changing the theme, which btw flashes for a second (A.10) on launch before going dark, but I think this is a global problem of Material 3 and some add a splash screen to handle this (NextPlayer for example does the same), but I hate splash screens.

Yeah, need to reload the activity to update the theme

I don't have many bundles installed, so the focus on the search bar now is kind of annoying as it brings the KB, if it makes sense to you and others, I would like if it wasn't focused on the input field.
TiA.

@AbdurazaaqMohammed Can you move this to the center of window/panel?
It will be better imho

@AbdurazaaqMohammed Can you move this to the center of window/panel?

Done in latest release

I don't have many bundles installed and I can locate what I need to AntiSplit in a matter of seconds from the short list, without having to search for the app, so the focus on the search bar now is kind of annoying as it automatically brings the KB, if it makes sense to you and others, I would like if it wasn't focused on the input field upon launching the apps picker.

I tried to do it, it doesn't work on my device, this is a famous problem with Android not consistently being able to show/hide keyboard programmatically, the problem is that the way the material search bar works you need to click on it to show the view at all, when you click it it opens the keyboard

I mentioned this elsewhere (you know where), but if you can - please add a sorting option to the installed picker dialog - I prefer them sorted not alphabetically, but latest updated (not latest newly installed - it's diff., they will still be on top) on top, just like how "My APK" shows them.

Added

The NavBar for me stays white with the app's dark/black themes (Samsung with A.10).

I tried to fix it, I can't test it because on non Samsung devices the nav bar is transparent by default, and I don't have a Samsung phone to test it

From the changelog: "Try to not show keyboard on opening installed apps list" > Unfortunately it's the same, no change.
Once you close the dialog (installed apps picker), the sorting goes from descending to ascending and stays with reversed (wrong) order, so everytime I have to sort it again.
NavBar > it looks the same to me, no change there too. You can test with BrowserStack on real devices, they say that if you register as a developer, you should have unlimited access, uazo, the maintainer of Cromite uses it and says the same thing.
I should've also mentioned that the Status Bar is transparent/invisible for some reason with the dark & black theme (like it is in immersive mode - it isn't), unless a dialog is opened, which is strange, as it seems changing the focus from the main ui, changes the status bar, but it wouldn't.
Installing this v.2.0.3 changed the theme back to Light Mode for some odd reason.

From the changelog: "Try to not show keyboard on opening installed apps list" > Unfortunately it's the same, no change.
Once you close the dialog (installed apps picker), the sorting goes from descending to ascending and stays with reversed (wrong) order, so everytime I have to sort it again.
NavBar > it looks the same to me, no change there too. You can test with BrowserStack on real devices, they say that if you register as a developer, you should have unlimited access, uazo, the maintainer of Cromite uses it and says the same thing.
I should've also mentioned that the Status Bar's text & icons are transparent/invisible for some reason with the dark & black themes (like it is in immersive mode - it isn't), unless a dialog is opened, which is strange, as it seems changing the focus from the main ui, changes the status bar, but it shouldn't.
Installing this v.2.0.3 changed the theme back to Light Mode for some odd reason.

One thing you said is practically true about updates because it'll consume battery more, And i think that should be optional because this app is only for converting files to APK and i also thought it's not good idea adding update option. My intention for asking for update was because the app is in development and some changes are keep coming and i wanted to explore with each change and i had no idea when it's updates are releasing i manually had to check that's why i asked for adding update option.
But now i think it's better not to add update coz it'll run in foreground for checking updates and will drain battery. It has only one task and that's enough just add your github release page inside app so that user can easily navigate to release page and can download from there. This would be much better instead adding update option.

this is for @Hiaashuu, not sure if you already know but you can use an app called Obtainium which helped to let you know if there's a new update from any releases on GitHub and install it for you

Here are some recommendations: ( if you wish you can implement )

Only button would be far better than adding them inside a Card and you can bring buttons at the center of Screen instead at top for easy access.
Add a fixed height dialog box for logs when pressed merge, and logs should be auto scrolled to the end of each steps.
You should remove keyboard opening at start of Selecting installed apps.
I noticed in update dialog texts are not aligned well add margins.
For theme select some other icon for dark and Black icon and why have you added setting button there ?

One thing you said is practically true about updates because it'll consume battery more, And i think that should be optional because this app is only for converting files to APK and i also thought it's not good idea adding update option. My intention for asking for update was because the app is in development and some changes are keep coming and i wanted to explore with each change and i had no idea when it's updates are releasing i manually had to check that's why i asked for adding update option.
But now i think it's better not to add update coz it'll run in foreground for checking updates and will drain battery. It has only one task and that's enough just add your github release page inside app so that user can easily navigate to release page and can download from there. This would be much better instead adding update option.

this is for @Hiaashuu, not sure if you already know but you can use an app called Obtainium which helped to let you know if there's a new update from any releases on GitHub and install it for you

Thank you for letting me know. I tested the app it doesn't auto detect open source and shows updates, i had to manually add them. For that i think would be better i manually check in GitHub for one or two apps i use blackhole and Antisplit these two apps and both has update check added so i don't think it would be helpful. But thank you for info.

Only button would be far better than adding them inside a Card and you can bring buttons at the center of Screen instead at top for easy access.
Add a fixed height dialog box for logs when pressed merge, and logs should be auto scrolled to the end of each steps.

These are subjective and I think constantly updating the log in a dialog will be bad for performance

You should remove keyboard opening at start of Selecting installed apps.

I literally try every way to hide keyboard after setup the material search and it doesn't work, I just went back to the old EditText way, it doesn't show keyboard automatically now and looks better anyway

I noticed in update dialog texts are not aligned well add margins.

Fixed in latest release

For theme select some other icon for dark and Black icon and why have you added setting button there ?

It's system theme, I change the icons to these, maybe it makes more sense

The EditText way looking better is subjective, but at least fixes the KB annoyance.
The rest of my reports are still valid and annoying, it seems like the Material redesign introduced many issues, solved basically nothing, that's why I was against it, I hope you keep supporting the 1.x vers. and release new updates with some of the new things, like sorting (but after you fix it to work as it should).

Guys, please refrain quoting the whole comments if it's not necessary, as it males this mega thread at this point unnecessarily long, with all of those images, videos and whatnot, if I could, I would've edited your comments if you don't want to, to place them under details (expandable), so it doesn't take so much scrolls to reach the end and it won't load the assets every time when opening this issue ticket (good for performance and data).

The EditText way looking better is subjective, but at least fixes the KB annoyance.
The rest of my reports are still valid and annoying, it seems like the Material redesign introduced many issues, solved basically nothing, that's why I was against it, I hope you keep supporting the 1.x vers. and release new updates with some of the new things, like sorting (but after you fix it to work as it should).

I understand your concern but right now it's initial and can be fixed bugs and other things slowly he's trying his best and the best part is he responds.
Tha actual function of AntiSplit, for which it is designed is working well and other things can be fixed with upcoming updates.
For material design didn't you like it ?
As per my opinion it looks great and you must have heard "With Great Power, Comes Great Responsibilities" 😅   it's initial, i hope he'll fix everything slowly.

Once you close the dialog (installed apps picker), the sorting goes from descending to ascending and stays with reversed (wrong) order, so everytime I have to sort it again.

Sorry I did not see this earlier, I missed it, now I fixed it

NavBar > it looks the same to me, no change there too. You can test with BrowserStack on real devices, they say that if you register as a developer, you should have unlimited access, uazo, the maintainer of Cromite uses it and says the same thing.

It should be fixed now

I should've also mentioned that the Status Bar's text & icons are transparent/invisible for some reason with the dark & black themes (like it is in immersive mode - it isn't), unless a dialog is opened, which is strange, as it seems changing the focus from the main ui, changes the status bar, but it shouldn't.

I have hidden the status bar on Samsung devices

The rest of my reports are still valid and annoying, it seems like the Material redesign introduced many issues, solved basically nothing, that's why I was against it, I hope you keep supporting the 1.x vers. and release new updates with some of the new things, like sorting (but after you fix it to work as it should).

Yes I just posted new release

"It should be fixed now"
-> Kind of, it still looks better when a dialog is opened and in the Mod. There is another issue about this.
"I have hidden the status bar on Samsung devices"
-> I hate this (in MT's editor(s) too), I want to always see the Status Bar (unless an immersive mode is really necessary, like when a video is in full-screen mode, or with a game, if for nothing else, at least to know when an update is DLed, currently no notifications, nothing, they show up if a dialog is opened and in the Mod, please if you can check despite the obfuscation how they do it there. There is another issue about this too.
"Yes I just posted new release"
-> Thanks. Maybe I should go back to v1.x and leave the bugs finding/reporting and whatnot to others for now...

BrowserStack give me 25 minutes free for apps, anyway I test this fixed in official Samsung emulator, I put back the status bar

BrowserStack give me 25 minutes free for apps, anyway I test this fixed in official Samsung emulator, I put back the status bar

Another two things for you:

Set a center style text for changelog panel in the app, when a new of new version is available.
Apply a selection around the button of the current used theme (I selected one of the four available, but I don't know which). If possible, do the same for the language.
Use a material you toggles design (like Google on last Android version).
Instead to add more space between a setting and another, on settings page, add a line divider like on apps list. It's more easier to manage and will prevent  eventual problems on different DPI resolutions.
You don't need to use a "fullscreen" searchbar for apps list, take a look to this for example: it's a smooth rectangle (like the current one) but it use the material style.

@0xrxL Thanks for the suggestions. I did the first four.

If possible, do the same for the language.

The currently selected language should be highlighted by bold text.

You don't need to use a "fullscreen" searchbar for apps list, take a look to this for example: it's a smooth rectangle (like the current one) but it use the material style and can include more buttons (like voice input or reorder by name/date).

I can try to add voice button if you want, but I don't see the point in using the material searchbar (I don't think voice input is built in to it), it doesn't look special and it has to the open the keyboard to be used which others seem to be infuriated by

I can try to add voice button if you want, but I don't see the point in using the material searchbar (I don't think voice input is built in to it), it doesn't look special and it has to open the keyboard to be used which others seem to be infuriated by

Nah...it's not a matter of voice input or else, it's just to make a more material app. As you have seen, there are precise color shades that are part of the material theme, and that make the app more pleasing to the eye (like LibreTube for example).

LibreTube doesnt use material searchbar lol

Anyway that material searchbar look like it been the same since 2015, I aint dealing with that keyboard opening nonsense again, even though no one should care about it, as you can use the app list with the keyboard open..

LibreTube doesnt use material searchbar lol

Anyway that material searchbar look like it been the same since 2015, I aint dealing with that keyboard opening nonsense again, even though no one should care about it, as you can use the app list with the keyboard open..

May bad... I got confused with Revanced Manager 😅

The StatusBar is visible only with the Light theme.
The NavBar is reverted to how it was unfortunately - White with all the themes, while instead just the color of the buttons should've been changed somehow from the prev. ver. (White with Dark/Black theme ¦ Black with Light theme) and being transparent, it seems the Samsung Emulator doesn't reflect the reality with older OS vers.
The toggle switches are now unnecessarily huge, most of Google's decisions and design changes are terrible. Thank you 0xrxL for this suggestion in making them worse. IDK why you keeps making unnecessarily quotes, especially when you are  replying right below/after the comment you are responding to, this as I explained makes the page unnecessarily long and takes more time to scroll.

most of Google's decisions and design changes/choices are terrible. Thank you 0xrxL for this suggestion in making them worse. IDK why you keep making unnecessary quotes, especially when you are replying right below/after the comment you are responding to, this as I explained here before makes the page unnecessarily long and takes more time to load & scroll in a browser.

I quoted to clarify to whom and to which part of the comment I was responding, otherwise reducing the length would not have made anyone understand anything (speaking online is different from speaking in real life).
Anyway, if the current toggle size represent a problem for you, the solution could be to copy the one adopted by Samsung.

makes the page unnecessarily long and takes more time to load & scroll in a browser.

On mobile GitHub has a button to skip to bottom and on PC you have scroll bar, I don't know why you are complaining.

The toggle switches are now unnecessarily huge

It looks the same size for me.

The StatusBar is visible only with the Light theme.

The NavBar is reverted to how it was unfortunately - White with all the themes, while instead just the color of the buttons should've been changed somehow from the prev. ver. (White with Dark/Black theme ¦ Black with Light theme as Kuddus73 have shown) and being transparent, it seems the Samsung Emulator doesn't reflect the reality with older OS vers.

I can't do any more for this, I wasted hours yesterday trying anything I could think of to fix this and now seems I don't have a way to test it on devices which actually have the problem.

Replying in order of my previous comment, instead of the response (wrong) order, which I will appreciate if being followed, because it kind of confuses me otherwise. TiA.
The new unnecessary big toggles are on: 720x1560 with 320 DPI, but NVM - leave them, if you don't have time or aren't interested.
Nav/Status Bars: Maybe you will figure them out in future when you gather some more coding experience, but if there's something I can help with, other than screenshots - don't hesitate to let me know ;)
BTW, the 2 look OK with the Mod, but not with this and the StatusBar with the Light theme is not as it should on S23 Ultra with A.14 either.
GH mobile site doesn't have jump buttons, never had and it's broken since Wed. 11th, but only when I'm logged in, it looks OK when I don't, I have a scrollbar tho (not fixed and always on), but it it's not intended to be dragged with a finger, maybe with a mouse and the loading of assets always have to be done anyway, linking the comments of which the quoting of the whole, when it's not even a direct reply to the text from there is unnecessary, as it won't help anyone, but it will look like I'm nagging or like I'm a conflict person, even tho I'm correct, so drop this part, let's not digg into it - it's pointless.
The search field's layout gets broken on the right with the black theme when you input anything, it's the same in landscape, so probably not a DPI thing and only on my end.

@AbdurazaaqMohammed thanks, the app has improved a lot with version 2.0.7. 👍
Anyway...about language picker I have an idea: once a language is selected, instead to set its text to bold, you can keep the button selected as in the following screen:

Yeah, better highlighted or a green checkmark infront for example. Even tho I use it in Eng, the above suggestion for the lang. picker makes sense
I was surprised to find out that the new changes regarding the update check dialog prompt are being done on server-side (?), without having to update they were centered when I checked and before upd. to v2.0.7, but I found out that with the Dark Theme the update check dialog prompt had no borders (auto update check is Off for me), don't know if it's now fixes, will know when there's a new ver.

Yeah, better highlighted or a green checkmark infront for example.

Yeah...a checkmark is a good alternative solution.

Is the search field broken with the Back Theme for you too when you type anything ?

Yeah...searchbar is partially broken

I put checkmark in the language dialog.
I don't know what is causing this searchbar issue, because it shouldn't be a color problem, it looks like the X button is displaying over the border, but then it should have been happening in the other themes

I put checkmark in the language dialog.
I don't know what is causing this searchbar issue, because it shouldn't be a color problem, it looks like the X button is displaying over the border, but then it should have been happening in the other themes

Hi.
Did you find a solution for searchbar bug?

The Nav/Status bars are now ok with the Dark/Black themes on Sammy with A.10, with the Light one the icons/text are still invisible because they are white on white, but I don't care, since I'm using and will use the Dark/Black (mostly Dark), so unless someone else complains - leave it as is currently ;)
Consider:
Dialog borders for the Black Theme (Light & Dark ones don't necessarily need them as it's pretty obvious where the pop-ups like the Settings and App picker, etc. begin and end).
Search by a package name (it doesn't necessarily needs to be displayed, with or without versions).

BTW I don't want to create an issue ticket for something so minor, so I'm mentioning it here, but you can ignore it if you want - NP:
The screenshots height/width in the column in the ReadMe seem inconsistent, especially the last "Result" one, which displays as the smallest, even tho their original sizes/rez. are very similar with only a few pixels difference (I haven't checked them all), which shouldn't matter that much, but yet they show up as inconsistent for me, you might want to adjust the thumbnails custom re/size.

Seems (apart from @drogga minor fixes requests) this will be the last thing to implement, before closing this thread/issue.

The Nav/Status bars are now ok with the Dark/Black themes on Sammy with A.10, with the Light one the status bar icons/text are still invisible because they are white on white, but I don't care, since I'm using and will use the Dark/Black (mostly Dark), so unless someone else complains - leave it as is currently ;)

maybe fixed now

Consider: Dialog borders for the Black Theme (Light & Dark ones don't necessarily need them as it's pretty obvious where the pop-ups like the Settings and App picker, etc. begin and end).

I added it, now the dialog takes up the entire screen for some reason and I couldn't fix it, this is the only way I got it to work

Search by a package name (it doesn't necessarily needs to be displayed, with or without versions).

Added

Now the Status Bar is purple and the Nav Bar always white, please revert those changes.
Yes, the dialogs are now full-screen only with the Black theme, but I don't mind it being like this for now.
The Changelog/What's New in the app when checked for updates said only "add", which is strange and GitHub didn't notify me for the latest update for some reason and I'm "watching" the releases, which is odd.
The Clear & Sort button are getting over a long text (P.N. for example) or a text is getting over them in the search bar, since now they are inside it, instead of outside.

Now the Status Bar is purple and the Nav Bar always white, please revert those changes.

Ok https://github.com/AbdurazaaqMohammed/AntiSplit-M/releases/download/2.1.0/AntiSplit-M.v2.1.0.apk

The Changelog/What's New in the app when checked for updates said only "add", which is strange and GitHub didn't notify me for the latest update for some reason and I'm "watching" the releases, which is odd.

I put link in the changelog, maybe it messed up something

The Clear & Sort button are getting over a long text (P.N. for example) or a text is getting over them in the search bar, since now they are inside it, instead of outside.

should be fixed


rename functions

I think the prefix should be xmap_, e.g. xmap_validate(), rather than validate_xmap() where the first argument is an xmap.

Subsequently, the first argument of xmap_apply(xmap = ..., data = ...) while another function say apply_xmap(data = ..., xmap = ...) can have it other way around.

"apply" still questionable though and I don't recommend it as R has a suite of apply functions (tapply, sapply, apply) that is not related to this

maybe xmap_join() or xmap_merge()

offer two functions for applying transformation (data first, xmap first versions)

generics that will form part of a user workflow should follow the xmap_ prefix convention (e.g. xmap_validate()).
validation functions currently named using a suffix convention validate_xmap_df()

[ ] fix inconsistency with x argument where it sometimes refers to an xmap (i.e. in xmap_validate()), or a data.frame-like object as_xmap_df()


SteamGridDB doesn't launch games when using Powershell V2

Describe the bug
SteamGridDB doesn't launch games if the target PC has Powershell V2. No games launch if the user has this version of powershell, because there is an error in the LauncherAutoClose.ps1 script on line 17, character 71.
To Reproduce

Run SteamGridDB on a computer with Powershell v2 (verify by launching powershell and running $PSVersionTable.PSVersion.Major)
Import games (eg from Epic Store)
Edit game's launch options in steam to remove -windowstyle hidden and add -noexit

The following error should show "You must provide a value expression on the right hand side of the '-' operator”
Expected behavior
Steamgrid DB Manager should state somewhere that an updated version of Powershell is required, which should really only impact Windows 7 users who have an older powershell.
Operating System

Windows 7

Installed Launchers

Epic Games Launcher
Uplay
Battle.net
GOG

Screenshots
Powershell v2:

Powershell v5

Log
N/A
Additional context
I was pointed in this direction by this stack overflow post: https://stackoverflow.com/questions/16149772/cmd-call-to-powershell-you-must-provide-a-value-expression-on-the-right-hand-si
An updated powershell can be found here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=54616
Thanks!

Unfortunately, we do not support Windows 7, as Microsoft ended support for Windows 7 on January 14, 2020. If anybody can reproduce this issue on a later version of Windows, please open a new issue.

Unfortunately, we do not support Windows 7, as Microsoft ended support for Windows 7 on January 14, 2020. If anybody can reproduce this issue on a later version of Windows, please open a new issue.


Terraform recipe request - handling credentials

What should we add to our content collections?
How do our customers handle secrets, certificates, etc within Aiven Terraform Provider? For example, they might need to pass some keys/tokens/credentials within a Kafka connector config. But having this in plaintext is not ideal. A good practice would be either file path or as an environment variable.
The goal of this recipe would be to:

Create a new recipe showing an example of handling secrets within Terraform (focus on 3rd party services like Google Cloud Storage and GCS sink connector). Some learning is required about how Kafka handles secrets and how that is handled in Terraform.
Do a clean-up of existing recipes if they are handling secrets.

This content will be better served as a blog so closing this issue.


Slight changes to the Brazilian Portugese translations

Changed 'geradores' back to 'spawners' as it is usually not translated and sounds a bit off when it is.
Added translation to the description and info about the 'Altar of the seas'.

cc: @t0piy as the original author

sorry about that :P

It's not really a credit thing, I just try to pull in previous lang authors for comment on changes to the file
Usually they don't respond, lol

ah, I see

I translated "Spawners" as "Geradores" because that's how it is translated into Brazilian Portuguese in the Java version of Minecraft (The word "Spawner" and neither its plural is mentioned in PT-BR). Also I didn't translate the Altar of the Sea related stuff because the content is no longer present in the mod

Thank you for taking the time to explain it to me. I'm just doing a project that requires translation and thought that the altar of the seas was something that was still in the mod. As for the rest of the explanation I will keep that in mind when doing future works. Much appreciated.

Thank you for taking the time to explain it to me. I'm just doing a project that requires translation and thought that the altar of the seas was something that was still in the mod. As for the rest of the explanation I will keep that in mind when doing future works. Much appreciated.

Always glad to help!
A tip that can help with the translation: in the official PT-BR translation of Minecraft Java Edition, the name of the items has only the first word starting with a capital letter.  In Brazilian Portuguese language, it is up to the author whether he wants only the first word starting with a capital letter or the whole sentence, which is a little different from what happens with EN-US. Basically it is more interesting that you translate "Gerador de porco lendário" than "Gerador de Porco Lendário", because that way the translation is more reliable in relation to Minecraft Java Edition


sfdx force:auth:web:login not working (also via VSCode extensions) but sfdx auth:web:login is working

Summary
After running sfdx force:auth:web:login command and entering username and password, the confirmation does not appear where the CLI has successfully authorised. Instead, an OAuth error appears on the screen.
This is the same behaviour when using the VSCode Extensions using the VSCode UI.
Steps To Reproduce:
Repository to reproduce: Not applicable
NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

Run command: sfdx force:auth:web:login --setalias MyOrgAlias --instanceurl https://test.salesforce.com --setdefaultusername
Enter Username and Password on the browser
The screen waits for a response and tries to log you in
Refresh browser screen and you will get an OAuth error.

Try above steps using the sfdx auth:web:login command and there are no issues.
Expected result
SFDX via VSCode extensions will be authorised into the target org.
Actual result
OAuth error received if using the sfdx force:auth:web:login command
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
$ sfdx --version
sfdx-cli/7.86.3 win32-x64 node-v14.15.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
$ sfdx plugins --core
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.5 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-diff 0.0.6
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.5 (core)
analytics 1.12.1 (core)
auth 1.4.7 (core)
config 1.2.4 (core)
etcopydata 0.5.7
generator 1.1.5 (core)
salesforcedx 50.16.1 (core)
├─ schema 1.0.3 (core)
├─ limits 1.0.3 (core)
├─ user 1.0.11 (core)
├─ custom-metadata 1.0.11 (core)
├─ apex 0.1.4 (core)
├─ templates 50.4.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ salesforce-alm 50.16.1 (core)
sfdx-cli 7.86.3 (core)
sfdx-git-delta 4.2.0
telemetry 1.0.1 (core)
OS and version: Windows 10 Enterprise

I can also confirm the issue, downgrading to 7.26.0 solves it.

Same problem for multiple members of my team after updating from 7.85 to 7.88, except that no version of the command line seems to resolve it.
Ticket in with support, but in the meantime I will attempt to downgrade. I would like to see if I can find something less drastic than 7.26.0 from a year ago.

I have the issue, it keeps loading in Ubuntu

sfdx-cli/7.85.1-2fb9e41053 linux-x64 node-v12.18.3

Visual Code:

Version: 1.53.2
Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4
Date: 2021-02-11T11:48:44.518Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-66-generic snap

hmm... No level of downgrading or even fully uninstalling and reinstalling and older version from NPM has been able to change the behavior for us.

No level of downgrading or even fully uninstalling and reinstalling an older version from NPM has been able to change the behavior for us.

Really? Not even the oldy but goody 7.26.3? Truth be told I did not put too much effort on finding the most recent working version, but 7.26.3 really came through for me.

Also my lone mac user updated to 7.88 and has seen no problem.

Yeah, my mac user colleagues also don't seem to be affected.
I can also confirm that 7.88.4 does not solve it for me.
$ sfdx --version
sfdx-cli/7.88.4 linux-x64 node-v15.9.0

$ sfdx plugins --core
@oclif/plugin-autocomplete 0.3.0 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.5 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/lwc-dev-server 2.10.0
├─ @oclif/plugin-help 2.2.3
└─ @oclif/plugin-update 1.3.9
@salesforce/sfdx-diff 0.0.6
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.7 (core)
auth 1.4.8 (core)
config 1.2.5 (core)
dependencies-cli 2.0.1
generator 1.1.5 (core)
salesforcedx 51.0.4 (core)
├─ limits 1.0.4 (core)
├─ schema 1.0.4 (core)
├─ user 1.1.2 (core)
├─ custom-metadata 1.0.11 (core)
├─ apex 0.1.4 (core)
├─ templates 51.2.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ salesforce-alm 51.0.2 (core)
sfdx-cli 7.88.4 (core)
telemetry 1.1.1 (core)

Also, I just realized the original reporter claims the cli does work for him, I just want to state for the record: it does not for me. I don't believe this to be related to VSCode at all, but to sfdx-cli itself.

hmm... No level of downgrading or even fully uninstalling and reinstalling an older version from NPM has been able to change the behavior for us.
Frankly the "downgrade" procedure I read didn't seem to work. Telling it to install the plugin of a particular version would seem to work, but then if you did "sfdx -v" it would still just say 7.88.4.

BTW, as per https://github.com/forcedotcom/salesforcedx-vscode/issues/2931#issuecomment-784843086 maybe try downgrading the salesforcedx plugin directly.

Really? Not even the oldy but goody 7.26.3? Truth be told I did not put too much effort on finding the most recent working version, but 7.26.3 really came through for me.

@dhbahr Well, we have had some other troubles with various versions that I didn't want to re-experience, so I was loathe to go back too far. Now that you mention it though, I don't think that I actually tested 7.26.3, because I thought it was downgrading when it was not. I'll try it over again using NPM to downgrade when I can.
I did uninstall completely and install 7.85.1 (which is where I was before the update that caused the failure) from NPM in order to get the version I wanted. It did not seem to improve things at all.
Still happening now:
We can't authorize you because of an OAuth error. For more information, contact your Salesforce administrator.
OAUTH_APPROVAL_ERROR_GENERIC : An unexpected error has occured during authentication. Please try again.

Hoping to eventually hear something helpful from support.
Since we're sharing:
sfdx -v
 »   Warning: sfdx-cli update available from 7.85.1 to 7.88.4.
sfdx-cli/7.85.1 win32-x64 node-v12.18.2

sfdx plugins --core
 »   Warning: sfdx-cli update available from 7.85.1 to 7.88.4.
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.5 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.5 (core)
analytics 1.12.1 (core)
auth 1.4.6 (core)
config 1.2.3 (core)
generator 1.1.5 (core)
salesforcedx 50.15.0 (core)
├─ limits 1.0.3 (core)
├─ schema 1.0.3 (core)
├─ user 1.0.9 (core)
├─ apex 0.1.4 (core)
├─ custom-metadata 1.0.11 (core)
├─ templates 50.4.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ salesforce-alm 50.15.0 (core)
sfdx-cli 7.85.1 (core)
texei-sfdx-plugin 1.9.3

No such luck. Downgraded to 7.26.0 (that's all that was available for 7.26 on NPM), but still the very same result.

Hey @torynet a couple of remarks:
First, we seemingly have different issues. In my case I don't get any oauth errors, the orgs simply don't receive a response from the localhost server listening on 1717. That being said, downgrading the salesforcedx plugin to 50.1.0 (sfdx plugins:install<EMAIL_ADDRESS>took care of my issue, without downgrading the sfdx-cli at all, maybe something worth trying?
Also I saw now you are using node 12, could you try upgrading to 14?
Best

Same issue for me.
Ubuntu 20.10 Linux 5.10.2-surface, sfdx 7.82.1-0
The browser redirect to localhost never completes. With trace debugging the last message i get in the log is:
socket connection initialized from <IP_ADDRESS>
repeated a few times but never does anything.
Downgrading to 7.26 worked.

Not to tell you what to do or anything, but I feel downgrading the salesforcedx plugin is a better approach, leaves you less outdated, @kresho .

@dhbahr We got the same "localhost never responds / white screen forever" sort of response initially, prior to downgrading, but while it's doing that if you refresh the page, you will then get an oauth error.
Since downgrading it seems to skip that phase and go right to the oauth error.
I'll reinstall up to current again and see if I can get it to downgrade the plugin. Hopefully that will do something now.
I suppose I can upgrade node... I didn't pay attention to that. I told just told NPM to update. I'll try that as well though.
Thanks for the advice.

@torynet yeah, as I mentioned a couple of comments ago, it strikes me we are experiencing 2 different bugs (albeit having the same negative impact). Hope reinstalling works for you.

this worked for me:
downgrade sfdx-cli: npm install<EMAIL_ADDRESS>--global
downgrade salesforcedx plugin: sfdx plugins:install<EMAIL_ADDRESS>downgrade auth plugin: sfdx plugins:install<EMAIL_ADDRESS>

@alanmangalindan I was really hopeful that your very precise procedure would work for me. Thanks for posting it.
Unfortunately, it did not. No change.
sfdx -v
»   Warning: sfdx-cli update available from 7.86.3 to 7.88.4.
sfdx-cli/7.86.3 win32-x64 node-v14.16.0
sfdx plugins --core
»   Warning: sfdx-cli update available from 7.86.3 to 7.88.4.
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.10.0 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/analytics 0.23.0
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.5 (core)
analytics 1.12.1 (core)
auth 1.4.7 (1.4.7)
config 1.2.4 (core)
generator 1.1.5 (core)
mo-dx-plugin 0.3.2
salesforcedx 50.13.1 (50.13.1)
├─ user 1.0.4
├─ schema 1.0.3
├─ limits 1.0.2
├─ salesforce-alm 50.13.1
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7
├─ templates 50.4.0
├─ custom-metadata 1.0.11
└─ apex 0.1.4
sfdx-cli 7.86.3 (core)
telemetry 1.0.1 (core)
texei-sfdx-plugin 1.9.3
@dhbahr No, I'm fairly certain we are experiencing the same bug. I'm just seeing some slightly different behavior at various times, based on changes I have made to try and troubleshoot. If I take everything back to the latest and "greatest", revoke my oauth connected app user, and try again, I see the same problems as I originally did, which are exactly as you describe.
We do seem to have some differences though. Because the things that are working for you all, are not for me.

@dhbahr No, I'm fairly certain we are experiencing the same bug. I'm just seeing some slightly different behavior at various times, based on changes I have made to try and troubleshoot. If I take everything back to the latest and "greatest", revoke my oauth connected app user, and try again, I see the same problems as I originally did, which are exactly as you describe.

I see, a pain in the a**e no doubt.

I can also confirm the newest 7.89.2 release still presents the same issue for me.

This is really a bit unfortunate as authorising an org should be the easy part in using dx.
Maybe a couple of other options would be to try out other previous stable versions like 7.82.1, or to use the sfdx auth:jwt:grant command, which I haven’t encountered a problem with. But that means going through the pain of setting up a connected app and generating a certificate, like what a cicd set up will use.


Examples Missing Array Index

Some of the examples are missing the array index on the "Licenses" property
Get-MsolUser | Where-Object {$.isLicensed -eq $true -and $.Licenses.ServiceStatus[4].ProvisioningStatus -eq "Disabled"}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f403603f-e17b-8b5b-cbd8-8e4c6f4e1728
Version Independent ID: a93a3de1-25d3-4f7a-3e3e-3a6f25f88b75
Content: View account license and service details with Office 365 PowerShell
Content Source: Enterprise/powershell/view-account-license-and-service-details-with-office-365-powershell.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@danmyhre The "long version" section with the incorrect examples has been removed. Thanks for letting us know.

Oh, it looks like this is the same issue I just reported, I apologize. Still there's not a correction of how that should be.
My query is the same as mentioned by @danmyhre but I'm using:
Get-MsolUser -All | where {$.isLicensed -eq $true -and $.Licenses[8].ServiceStatus[6].ProvisioningStatus -eq "Success"}
This is the result I get:
Cannot index into a null array.
At line:1 char:28

... ll | where {$_.isLicensed -eq $true -and $_Licenses[8].ServicesStatus ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : NullArray


Get Published Version of Runbook

Pull the Code from the ISE add-on

This isn't required,  we can sync runbooks with a status of published or edit.  If the status of a runbook is still new,  we wouldn't sync the runbook into scsm.


certain presubmit targets not scheduled

For example on this run, the following did not run (probably more, I did not exhaustively cross-reference with .ci.yaml):

Linux tool_integration_tests_*_4
Linux tool_tests_commands
Linux tool_tests_general

Where the mac and windows versions appear to have run. The runIf fields are the same.
For the PR https://github.com/flutter/flutter/pull/121549, this same issue lead to the PR getting reverted in https://github.com/flutter/flutter/pull/122037 because of a test target that failed post-submit but didn't run presubmit.

cc @yusuf-goog infra on-call. provisionally prioritizing this p1, as it has already broken the tree once.

This seems due to https://github.com/flutter/flutter/issues/122116, which has been fixed. Please help report if any new instances.

Not sure if this is related, but my PR has a couple pre-submit tests that have been stuck for over a day https://github.com/flutter/flutter/pull/121903

Not sure if this is related, but my PR has a couple pre-submit tests that have been stuck for over a day https://github.com/flutter/flutter/pull/121903

It is.

To unblock your PR, I reset those two tasks. They should be good now.

For reference, here is how to reset those tasks: go/flutter-luci-playbook#manually-trigger-try-pre-submit-builds

Okay awesome, thanks @keyonghan!

Seems no new instances. Presumably this is resolved with https://github.com/flutter/flutter/issues/122116 fixed.
Please reopen if same issue repros.


Low Accuracy

Thank you for this excellent example. Great idea. I have found the accuracy of the model quite low for me (~20%) and incorrect letters are often suggested. I decided to create a new model with your huge dataset in the NVIDIA DIGITS program using AlexNet. Accuracy jumped to 100% in just the first few epochs of training. I will try and adjust your code to use the Caffe model that DIGITS creates.

how do you do this?

how do you do this?

The tutorial on DIGITS is very good. Take a look at the Digits section of "Two Days to a Demo" on this page: https://github.com/dusty-nv/jetson-inference/blob/master/README.md#two-days-to-a-demo-digits

Thank you for this excellent example. Great idea. I have found the accuracy of the model quite low for me (~20%) and incorrect letters are often suggested. I decided to create a new model with your huge dataset in the NVIDIA DIGITS program using AlexNet. Accuracy jumped to 100% in just the first few epochs of training. I will try and adjust your code to use the Caffe model that DIGITS creates.

Hi could you please guide me how to get the accuracy graphs for the loicmarie's model?please provide me the code.

@ChamiJ NVIDIA DIGITS creates those graphs https://developer.nvidia.com/digits


Posthooks are not executed

When adding a post-hook to an incremental stream model (doesn't matter if it references a source or another model), the post-hook doesn't get executed.
Pre-hooks get executed just fine.
code example for testing:

{{ config(
    materialized='incremental_stream',
    pre_hook='CREATE TABLE prehook_works AS SELECT TRUE AS column_1;',
    post_hook='CREATE TABLE posthook_works AS SELECT TRUE AS column_1;'
    ) }}

SELECT *

FROM {{ incr_stream.stream_ref('r__accounts') }}

I can see that the code for the materialization has two lines for pre-hooks, but just one for post-hooks (inside_transaction=True is missing): https://github.com/arnoN7/dbt-incremental-stream/blob/master/macros/materializations/incremental_stream.sql#L148

post_hook and pre_hook should work now. You were right about the line missing for post-hooks

thank you for the swift fix!


Remote control feature to integrate cucumber

From<EMAIL_ADDRESS>on August 07, 2012 03:47:57
Would like to have robotium integrated with cucumber
Original issue: http://code.google.com/p/robotium/issues/detail?id=302

From<EMAIL_ADDRESS>on August 07, 2012 04:42:42
Remote control is being beta tested and will be released soon. I will update the website when it is ready.
Status: Invalid


DataGrid rows are getting mixed up when scrolling

My View looks like this
    <Grid RowDefinitions="Auto,*">
        <Label Grid.Row="0" Content="{Binding Greeting}" />
        <DataGrid
            Grid.Row="1"
            Items="{Binding Rows}"
            VerticalScrollBarVisibility="Visible"
            RowBackground="#EEEEEE">
            <DataGrid.Columns>
                <DataGridTextColumn Width="auto" Header="Index" Binding="{Binding Index, Mode=OneTime}" />
                <DataGridTextColumn Width="auto" Header="Name" Binding="{Binding Name, Mode=OneTime}" />
                <DataGridTextColumn Width="auto" Header="Value" Binding="{Binding Value, Mode=OneTime}" />
            </DataGrid.Columns>
        </DataGrid>
    </Grid>

Where Rows is an ObservableCollection of Row objects. The index should go from 1 to 200 but when scrolling, rows are getting mixed up (see the attached screen recording; https://youtu.be/iXFgCA1w0t8).
Desktop (please complete the following information):

OS: Windows
Version 22H2

It is a known container recycling issue,turn off recycling or change binding mode to OneWay.

@workgroupengineering Thanks a lot, changing the binding mode to OneWay solved the issue. But I don't understand what do you mean by "turn off recycling", how do I do that?

Not sure if it's an issue, as this behavior seems to be "expected" with OneTime bindings. I would even add validation to disallow users to use OneTime in here.
In short, "OneTime" will do exactly what it should - get values to the container one time. But since containers (cells) are reused in the datagrid instead of creating a new one for each row, it won't work properly, it needs to be dynamic OneWay.


uneval not handling space between tag and form

I believe #_ (cat) and #_(cat) should be equivalent but currently only the latter currently works.

The latest releases can handle these cases.
(z/sexpr (z/of-string "#'   #_    ignore-this  var-symbol"))
;; => (var var-symbol)

Artifact Coordinates
[rewrite-clj "0.4.3"]


npm install error

npm ERR! fetch failed http://registry.cnpmjs.org/esprima-fb/download/esprima-fb-3001.1.0-dev-harmony-fb.tgz

Just pushed some updated. LMK if you are still getting issue & what version of node/npm you are running. Thanks.


Implement the Center pivot point for rectangle

Description
Currently, we can set the pivot point only for Square shapes. We need this feature also on Rectangle
How to do this ?
The file to modify is : https://github.com/grzi/scion/blob/main/src/core/components/shapes/rectangle.rs
The square with working center pivot point is here : https://github.com/grzi/scion/blob/main/src/core/components/shapes/square.rs

Hello 👋🏿 could I be assigned this issue

Hello @Antonio-Bennett, of course, give it a try :)

Hey @grzi I just submitted https://github.com/grzi/scion/pull/198 let me know if I need to change anything at all :)


New version: Hecke v0.6.6

Registering package: Hecke
Repository: https://github.com/thofma/Hecke.jl
Created by: @thofma
Version: v0.6.6
Commit: f62b87dc2917ed30bebd431a2e15ac72491f69c2
Reviewed by: @thofma
Reference: https://github.com/thofma/Hecke.jl/commit/f62b87dc2917ed30bebd431a2e15ac72491f69c2#commitcomment-35625856

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: AbstractAlgebra, Requires
A patch release is not allowed to narrow the supported range of Julia versions

If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: Requires
A patch release is not allowed to narrow the supported range of Julia versions

If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

A patch release is not allowed to narrow the supported range of Julia versions

If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]


Test against ceph pacific release

If my info is correct, and it probably isn't, some time soon (March), ceph pacific will be released. Once there are ceph container images built for pacific we should start testing with them.

https://github.com/ceph/ceph-container/releases/tag/v6.0.0rc1
In theory we should be able to start testing against pacific. I am not going to jump on this right away due to other higher priority tasks, but others are welcome to if there's interest.

Running the CI tests on pacific currently fails. I filed the following issue with ceph:
https://tracker.ceph.com/issues/49873


State machine configuration in seata-go Saga

This is a subtask under the #618
Description:
In Java, users configure the state machine using spring.xml or by building a StateMachineConfig through code. In seata-go, we aim to provide users with a non-code approach to define state machine configurations, mirroring the implementation patterns observed in other Go projects.
The State Machine Configuration module has dependencies on various sub-modules. The development of specific functionalities will be incrementally added to the configuration as needed. For example, if the State Machine Configuration depends on ExpressionFactoryManager, the related methods need not be implemented initially. They can be added later when working on the expression part.
Implementation Details:
1. State Machine Configuration Interface:

Introduce a StateMachineConfig interface that defines the contract for configuring the state machine.

2. Default Implementation:

Provide a default implementation, DefaultStateMachineConfig, that serves as a baseline configuration with sensible defaults.

3. Non-Code Configuration:

Develop a mechanism allowing users to define state machine configurations without writing code. This could be through configuration files or any other non-code approach.

4. Incremental Functionality:

Recognize that the State Machine Configuration relies on various functionalities, and these functionalities can be added progressively. For instance, if the configuration later requires ExpressionFactoryManager, the corresponding initialization code can be added when working on the expression module.

Next Steps:

Interface Definition:

Define the StateMachineConfig interface outlining the methods required for configuring the state machine.

Default Implementation:

Implement DefaultStateMachineConfig as a default configuration with sensible defaults.

Non-Code Configuration:

Implement a mechanism for users to define state machine configurations without writing code.

Incremental Functionality:

Adopt an incremental approach to add functionalities to the configuration module as needed.

By implementing these steps, we can provide users with a flexible and user-friendly way to configure the state machine in seata-go, following non-code configuration patterns observed in other Go projects.

assign me


Expression type '()' is ambiguous without more context.

I'm currently trying to upload video using a multipartform.
XCode 8, Swift 3
 Alamofire.upload(
      multipartFormData: {  (multipartFormData) in
         multipartFormData.append(videoData, withName: "video", fileName: "video.mp4", mimeType: "application/octet-stream")
         },
         to: urlYoutube,
         encodingCompletion: { (result) in
               switch result {
                    case .success(let upload, _, _):
                        upload.responseJSON { response in
                            debugPrint(response)
                        }
                    case .failure(let encodingError):
                        print(encodingError)
                    }
            })

I'm getting this error -> "Expression type '()' is ambiguous without more context."
Not sure what I'm doing wrong here. Please advise.

how did u fix it?


Broken link to iGibson Stanford 2D-3D-S dataset

Hello,
I would like to use the Stanford 2D-3D-S dataset in iGibson. The link for the iGibson 2D-3D-S dataset that I received after submitting the end-user agreement was invalid. The link specified in the email I received is at the directory gibsonchallenge/2d3ds_for_igibson.zip, but this yielded a NoSuchKey error. The link to the older Gibson 2D-3D-S dataset remains valid however. Can I check if the iGibson 2D-3D-S dataset has been removed for some reason, and if it can be made available again?
Thanks!

We are working on restoring the access

@joelloo Thanks for letting us know.
We have restored the dataset at this URL location: https://storage.googleapis.com/gibsonchallenge/2d3ds_for_igibson.zip
Once you unzip it, you will see a folder called 2d3ds_v3 that contains the data.
Feel free to re-open the issue if this doesn't work. Thanks!


FAQ on TAC

I think the FSQ page should have a FAQ:
How does the OCA Ontology relate to the ontology being developed by the Threat Actor Context (TAC) Technical Committee?

The TAC is focused on the threat actor component of the overall effort.  The larger project will focus on the cybersecurity detect and response components and leave the threat actor modeling to TAC.  Ideally, we are both following BFO/CCO in order to maintain interoperability.


Update iterm2-nightly to 3.1.20170519

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Nightlies should remain latest, as otherwise they’re always outdated. I think we have that documented somewhere (if not, there was at least a discussion).


Support for node-fetch

OpenAPI version
2 and/or 3?
3
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
This looks like a great solution to a problem we have been facing. However, we use node-fetch exclusively in our code and tests. Do you have any plans to support node-fetch?
Describe the solution you'd like
A clear and concise description of what you want to happen.
Support for node-fetch
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Are you going to resolve the issue?

Hi @rmclaughlin-nelnet, thanks for raising this! 😃
I've been meaning to support node-fetch for a while as it's pretty popular.
What's the error you get when passing a node-fetch response to the toSatisfyApiSpec assertion?
I expect the solution will just be:

add a test block for node-fetch responses here
make a NodeFetchResponse class, similar to the AxiosResponseClass
ensure our ResponseFactory can distinguish node-fetch responses from responses of other request packages.

I'll do this when I have time, if you want it sooner you're welcome to make a pull request

Thanks, also which version of node-fetch are you using? Looks like most people are on 2.6.5, presumably because 3.0.0 is ES-Module only

Ah, sorry I miswrote the first solution, you need the status field so that we parse the response as a SuperAgent response, rather than a RequestPromise response (hence why it expected _json)
This should work when a response header specifies the content type is json. If the content type is text instead, use this:
describe('test', () => {
  it('passes', async () => {
    const rawResponse = await fetch('endpoint');
    const text = await rawResponse.text();
    const res = {
      req: {
        path: rawResponse.url,
        method: 'GET',
      },
      status: rawResponse.status,
      body: {},
      text,
    };
    expect(res).to.satisfyApiSpec;
  });
});

Ok, I got it to work with a few tweaks
const rawResponse = await fetch('endpoint');
const body = await rawResponse.json();
const res = {
  req: {
    path: rawResponse.url,
    method: 'GET',
  },
  status: rawResponse.status,
  body,
};
expect(res).toSatisfyApiSpec();

It looks like body is the correct property to fill in, not text
You were using expect(res).to.satisfyApiSpec; but I had to use expect(res).toSatisfyApiSpec();
It looks like it does not validate that a property does or does not exist, only that, if it exists, it is the correct type, is that correct? I tried breaking the test by removing/changing the names of properties in the swagger file, but the test kept passing. It was only when I changed the type (from string to number) that I was able to get the test to fail.

Thanks! In answer to your points:

ah yes I think adding text is unnecessary
good spot, my example was for the chai plugin, whereas you're using jest.
would you mind pasting the relevant part of your swagger file? To fail tests by removing/changing the names of properties in the swagger file, I think your response schema should have additionalProperties: false and/or required properties


[UPDATE] Onboarding - Pairing view

After feedback from JP we updated all pairing views to be cleaner and less packed.
Please verify that pairing views match on all flows:

[x] Onboarding

QA done.


Add support for multi-param OSC sequences

@vapier wrote:

i don't think this correctly handles chaining to following OSC sequences.

That's correct. It doesn't handle chaining at all. It also doesn't handle color names.
Since this was my first PR, I was trying not to rewrite, but to just add a little on top of what was there and learn how things work -- I even reused the color parser that was written for OSC 4, though it won't support color names, meaning you can only set RGB values, and not just reuse colors from your base 16 for foreground and background.
The structure of the OSC handler in the State Machine seems designed on the assumption that they are single-valued (meaning one value per escape sequence), which makes chaining basically impossible.
Basically, still to do:

[ ] Rewrite the ActionOscDispatch to support chains of values
[ ] Make OSC 4 support setting the whole color palette at once
[ ] Make OSC 10, 11, 12 support setting all of them at once
[ ] Add support for lookups ("?") to output the current value #3718
[ ] Add support for resetting colors (OSC 104..119) #3719
[ ] Rewrite the color parser to include x11 color names more formats #3715
[x] Support setting colors above index 16 #3717 (maybe #313?)
Those things are definitely needed, but didn't seem necessary for a first pass.

Somewhere along the way someone will need to decide if we're going to do special colors for  bold/italic/underline/blink/reverse ... and which window properties should be settable by OSC 3 😉 @oising?
Originally posted by @Jaykul in https://github.com/microsoft/terminal/pull/891#issuecomment-494667974

@zadjii-msft That's a fun one alright. I'm looking for something a bit simpler at first to cut my teeth on, as the last time I wrote C++, MFC was the big shiny thing.
With respect to OSC 3, if it's window properties like pixel size, text area size, window titles, icons etc, then I think the right approach is to do what xterm does. The have some flags that this light up a number of CSI sequences for querying and setting window properties (focus, maximize, fullscreen, report text area size in cols/rows, report window size in pixels, etc.) These came from dtterm, and the X guys added some more. Some of them are probably going to be problematic (abuse) to enable out of the box, so there is a blacklist (disallowedWindowOps) and the feature flag itself is allowWindowOps.
Drop the following into your ~/.Xdefaults and fire up xterm and try echo -e "\e[18t" to get the visible textarea in rows/columns, for example.
*VT100.allowWindowOps: true
*VT100.allowTitleOps: true
*VT100.allowFontOps: true

So... I was trying to work on the multi-param OSC issue. Funny that I can not find any documentation indicating that there is support for multi-param OSC sequences. Not in http://www.xfree86.org/4.5.0/ctlseqs.html. Not in anywhere google can lead me.
Am I missing something or just I'm bad at google..

The xterm docs you linked mention that OSC 4 takes multiple parameters, and it can take an arbitrarily long list of pairs of parameters as a shorthand for repeating the OSC 4 call:

Any number of c name pairs may be given.

OSC 10 through OSC 17 also can take multiple parameters, but in this case, it's a shorthand for calling each of OSC 10-17 in turn.

One or more parameters is expected for P t . Each succesive parameter changes the next color in the list. The value of P s tells the starting point in the list.

The quoted text in the issue description was specifically referring to these behaviours of OSC 4 and OSC 10-17, but out of context, it appears to be talking about generically chaining different OSC commands, the way CSI commands can be.
mintty's extensive set of OSC commands includes a few multi-param commands such as OSC 8, and OSC 1337, which are both pretty-specific in how they're parsed. OSC I (i.e. icon) seems to use a comma in its parameter as a separator, and OSC 1337 uses : to separate its final parameter.
Another example, hterm documents OSC 4, OSC 52 and OSC 777 as multiparam.
We actually have OSC 52 implemented already via #5823, although a quick glance at the implementation shows no attempt to generically handle multi-parameter OSC sequences.
A challenge for a generic OSC parameter parser is that some OSC commands are allowed to have ; in their final parameter, e.g. OSC 0, or OSC 8.
After looking at the above, it makes sense to me that there's no generic multi-parameter OSC handling, each OSC sequence is specific in its parameter formats. They don't always use ; as a parameter separator, and you can't blindly split by ; to get an arbitrary list of parameters, except in specific cases like OSC 4 and OSC 10-17 which are defined that way.

Thanks @TBBle for the thorough and detailed writeup. I’m sure it will help us towards a better implementation.

I happened across this code, which is where (or least part of where) the assumptions about OSC commands being all-numeric will need to be unwound. Happily, it doesn't embed any assumption about the data after the first ;, so we don't have any issues with the "multi-param" OSC commands.

Another note: For \e]10;green;white\e\\, GNOME Terminal(VTE) actually ignores the second parameter. Only the foreground is working.
Xterm will faithfully make both parameter working on foreground and background respectively .

Yeah, setting the 10+ range was rarely supported in the terminals I tested - only XTerm and Kitty could set both the OSC 10+ range and the OSC 4 range. A couple more (including VTE) could set the OSC 4 range, but not OSC 10+. And Alacritty could handle OSC 10 but not OSC 4. This is not something I'd want to rely on if I were writing an app.

that function just wants to be refactored. ^_^

yeah we have some debt here. they're all written like that :(

Pinging for updating the issue description now that #7578 is merged.


defaultProps cause enum types to not be checked properly

I have found that if I have defaultProps on a component that has an enum prop typing, then flow will not properly throw an error if the usage of that component is wrong.
Example with issue documented at this tryflow
The example shown SHOULD have an error on the usage of Test and Test2, however only Test2 errors as it does not have defaultProps defined.

I believe it's because it's evaluating the type property to be string, not 'foo' | 'bar' | 'baz'.
If you explicitly type defaultProps, it should check property. Example here

Ah, that makes sense. It seems defaultProp should infer it's type from the props type definition though?

You need to specify types for defaultProps explicitly, it's a common developer confusion.
Look at https://github.com/facebook/flow/issues/4462

Above comments are true for Flow < 0.52, the situation is even clearer in Flow 0.53 so Im going to close this. Feel free to object if you still have a related issue in Flow 0.53.


[BUG] QR code symbol recognition issue

Issue: Problem with QR code reading
Problem description
During the scanning of a QR code, the software is reading the symbol "[" instead of "{", and the symbol ";" instead of ":", causing an incorrect reading and malfunctioning of the application.
Steps to reproduce the problem

Scan the QR code with the application.
Verify the reading of the symbol "[" instead of "{" and the symbol ";" instead of ":".
Observe the malfunction of the application.

Expected behavior
The software should correctly read the symbols "{" and ":", and function properly during the scanning of the QR code.
Current behavior
The software is reading the symbol "[" instead of "{", and the symbol ";" instead of ":", during the scanning of the QR code, causing a malfunction of the application.
Possible solution
Modify the code that handles the QR code reading to correctly recognize the symbols "{" and ":" and read them accurately.

Issue: QR code reading issue with special character combinations
Problem description
The QR code reading software was not recognizing the correct special character combinations, resulting in the incorrect reading of the "{" symbol as "[" and the ":" symbol as ";". This caused the application to malfunction during the scanning of the QR code.
Steps to reproduce the problem

Scan the QR code with the application.
Observe the incorrect reading of the symbols "{" as "[" and ":" as ";".
Notice the malfunction of the application.

Expected behavior
The software should correctly read the symbols "{" and ":" by recognizing their respective special character combinations, and function properly during the scanning of the QR code.
Current behavior
The software was not recognizing the special character combinations of "{" and ":" during the scanning of the QR code, resulting in the incorrect reading of the symbols and causing the application to malfunction.
Solution
The issue was resolved by updating the QR code reading function to properly recognize and interpret special character combinations. Specifically, the function was modified to handle the special character combinations of "{" and ":" accurately, which prevented the application from malfunctioning during the scanning of the QR code.

Hello FrenkyDema, when I read a qrcode, if there is a  ('cs') character in the qrcode, it deletes it and brings the missing code.


Feat/header component v2

This PR implements #319
Parameter:

firstElement: JSX.Element takes any element and is restricted to conform to component layout

There is a known bug where the text "BotAnik Space" does not work with light theme, see #333

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: