ToggleButton: In light and lightest themes, on hover, text color is same as background color in HCM

🐛 Bug Report
When the theme is set to light/lightest, and in High Contrast Mode, text color is changing to background color (becomes invisible) on mouse hover.
🤔 Expected Behavior
On hover, text should still have the same 'ButtonText' color and only the border color should change to Highlight.
😯 Current Behavior
Text color is changing to background color on hover and therefore becomes invisible.
https://user-images.githubusercontent.com/16927765/218563436-5dd27590-0887-4443-8f2f-242c8771cdb7.mov
💻 Example
Issue can be observed on Storybook and react-spectrum docs
🌍 Your Environment
If react-spectrum team needs access to https://assistivlabs.com/ to test WHCM, please let Adobe Accessibility team know. We can get you access.

Software
Version(s)

react-spectrum

Browser
Edge 109

Operating System
Windows

🧢 Your Company/Team

🕷 Tracking Issue (optional)

@dineshy87 thank you for letting us know about https://assistivlabs.com/. Definitely interested in learning more, seems like a handy tool, should I reach out to you or the accessibility team directly?

This issue originates from ActionButton component and is therefore seen wherever ActionButton is used. (Like ToggleButton, ActionGroup etc)


Adding Glue GetPartitions MaxResults

Fixes #2996
Adding default value of Glue GetPartitions MaxResults (128). Let me know if this works.

Thanks for your contribution. Could you fix the build failure?
[ERROR] /home/runner/work/presto/presto/presto-hive/src/main/java/io/prestosql/plugin/hive/metastore/glue/GlueHiveMetastore.java:[668,29] cannot find symbol
  symbol:   method withMaxResults(int)
  location: class com.amazonaws.services.glue.model.GetPartitionRequest

I will open a new pull request


[Examples] The example name does not get used

The examples specify name using the NAME property, but it does not seem to get used, and the name is based on the module name instead.
Repro:

change the name

rebuild / reload the example and observe the name is not changed:

@kungfooman for visibility

Hey @mvaligursky, thank you for raising the issue!
I contemplated a bit and I'm not what the best action here is.
When I rewrote the examples I noticed some irregularities in the naming convention, for example:
https://github.com/playcanvas/engine/blob/2bf47b09493675b41f596b8d7cfecc790e35aa54/examples/src/examples/graphics/area-lights.tsx#L4-L7
https://github.com/playcanvas/engine/blob/2bf47b09493675b41f596b8d7cfecc790e35aa54/examples/src/examples/graphics/clustered-area-lights.tsx#L6-L9

Some classes share the same name causing potential confusion or bundler Example$123 issues
Only static NAME property is changing the name

So it made sense to simply use the "real" class name to keep it easy and be on the safe side and it also creates ESM class name alignment.
But I can also see the pattern here, that this is maybe what you want:

Name: Clustered Area Lights -> class AreaLights?
Name: Reflection Box -> class BoxExample?

So I pretty much see four options:

Keep static NAME as it is, maybe someone requires it for something
Remove static NAME altogether as a leftover/relic from old build system
Display static NAME, but don't make it act like a slug
Display static NAME and make it act like a slug aswell

I tend to (2) since it's less code that could go wrong, whereas (3) and (4) add more code and a bigger generated example-data.mjs which also could lead to naming conflicts if we just copy/paste an example and forget to update static NAME :thinking:


Improve help forms

Fixes https://github.com/newsboat/newsboat/issues/1139.

Coverage increased (+0.05%) to 57.89% when pulling c20726a7895442cdd54e5333a6c7cded0c9746d1 on dennisschagt:bugfix/issue-1139 into 2914d48791625cadaf8acc266388afa13572ad20 on newsboat:master.

Resulting help in podboat:

Resulting help in newsboat:


Cant build react native from box in XCode: 'event2/event-config.h' file not found

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Try to build clear image on iOS using XCode (Version 12.4 (12D4e)).
React Native version:
"react-native": "0.63.4", also try 0.63.3
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Create an app using npx: npx react-native init mob4 --template react-native-template-typescript
Install pods: cd ios && pod install
Open XCode and press Build

Expected Results
Normal stub app
Snack, code example, screenshot, or link to a repository:

Exact same for me

same from my side:
ios/Pods/Headers/Public/libevent/event.h:44:10: 'event2/event-config.h' file not found

#include <event2/event-config.h>

Same for me

same for me. this morning, it was ok. but this evening, after "pod install" on an existing project, I had this line : "removing cocoalibevent" and build failed...

Same for me. I needed to enable google maps on iOS, I run pod install and I can't build anymore.

Same here for me

Same for me too

Not even reverting to legacy build system or re-installing pods worked for me

Experiencing this exact error on our end.

For me I could get around it by:

remove ios/Pods
cd ios && pod repo update
sudo gem install cocoapods
npx pod-install

By disabling Flipper in my Podfile it's worked !

Disabling Flipper works like a charm.
Go to ios/Podfile
And comment this lines:
`
Enables Flipper.

Note that if you have use_frameworks! enabled, Flipper will not work and
you should disable these next few lines.
use_flipper!
post_install do |installer|
flipper_post_install(installer)
end
`
Then remove Pods and re-install them

Hi all, I think all you are all doing for now is just deactivating Flipper... But what if you need it? I am trying a few things atm but it seems a lot of Flipper pod files include event.h from libevent. Its header files say that event.h from v1 is deprecated since libevent 2.0. We need to use include <event2/event.h> in all the Flipper dependencies using the libevent it seems. I will see if this may work and update here.

The update is indeed needed to re-activate Flipper, if you do not require it then disable it, if you require it you will have to wait for the update

Yes, that's the probably the best for now indeed

Exact same for me :/

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

Thanks, Michael! That was exactly the issue (:

Thanks! @michaelgmcd ! That's work for me.

@michaelgmcd that worked for me too!
If you're using configurations, this is what I did
use_flipper!({ 'Flipper-Folly' => '2.3.0' }, configurations: ['Debug', 'Staging'])

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

working, thanks!

Changing the iOS version under Deployment Info to 12.1 worked for me. Disabling Flipper (removing it from Podfile and from AppDelegate.m) works too.

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

thanks, You did me a big favor!

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

o great working thanks man.

i'm facing library not found for -lPods-AppName error after updating "Flipper-Folly" pod-spec. Can anyone help me in resolving this please?

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

Thank you @michaelgmcd

I confirm the same problem as well. It is annoying how RN breaks every once in a while and small hacks like this are needed.
Thank you @michaelgmcd !

Thanks for the help!

I am using bare expo and none of the above is working for me.. where would i put this use_flipper command - anywhere in my podfile seems to break it

regardless of the way you are registering the flipper
either
def add_flipper_pods!(versions = {})
  versions['Flipper'] ||= '~> 0.37.0'
  versions['DoubleConversion'] ||= '1.1.7'
  versions['Flipper-Folly'] ||= '~> **2.3.0'**

or
use_flipper!({ 'Flipper-Folly' => '**2.3.0**' })

regardless of the way you are registering the flipper-folly just force this version 2.3.0
either
def add_flipper_pods!(versions = {})
  versions['Flipper-Folly'] ||= '~> 2.3.0'

or
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

regardless of the way you are registering the flipper-folly just force this version 2.3.0
either
def add_flipper_pods!(versions = {})
  versions['Flipper-Folly'] ||= '~> 2.3.0'

or
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

I'm getting the below when I try

def add_flipper_pods!(versions = {})
  versions['Flipper-Folly'] ||= '~> 2.3.0'

[!] CocoaPods could not find compatible versions for pod "Flipper-Folly":
  In Podfile:
    Flipper-Folly (~> 2.3.0)

    FlipperKit/FBCxxFollyDynamicConvert (~> 0.33.1) was resolved to 0.33.1, which depends on
      Flipper-Folly (~> 2.1)

    FlipperKit/FlipperKitNetworkPlugin (~> 0.33.1) was resolved to 0.33.1, which depends on
      FlipperKit/Core (= 0.33.1) was resolved to 0.33.1, which depends on
        Flipper (~> 0.33.1) was resolved to 0.33.1, which depends on
          Flipper-RSocket (~> 1.0) was resolved to 1.3.0, which depends on
            Flipper-Folly (~> 2.5)

Specs satisfying the `Flipper-Folly (~> 2.3.0), Flipper-Folly (~> 2.1), Flipper-Folly (~> 2.5)` dependency were found, but they required a higher minimum deployment target.

In PodFile comment out:
  use_flipper!
  post_install do |installer|
    flipper_post_install(installer)
  end

Save. Then pod deintegrate and pod install.
Worked for me. If you need to use Flipper, people are having success in changing versions above.

Mi solución fue dentro de la carpeta ios del proyecto ejecutar:
*Pod update.
Este removió la librería que al parecer genera problemas y procedí a compilar.

In PodFile comment out:
  use_flipper!
  post_install do |installer|
    flipper_post_install(installer)
  end

Save. Then pod deintegrate and pod install.
Worked for me. If you need to use Flipper, people are having success in changing versions above.

Finally! It worked for me thank you!!

Finally, I found the solution! https://stackoverflow.com/a/66071245
use_flipper!({ 'Flipper' => '0.74.0' })

I followed this https://fbflipper.com/docs/getting-started/react-native/, and it worked like a charm

[Solved] ‘event2/event-config.h’ file not found in React-Native

upgrading flipper to v0.74.0 fixed this issue for me
use_flipper!('Flipper' => '0.74.0')

[Solved] ‘event2/event-config.h’ file not found in React-Native

fixed this issue for me
add_flipper_pods!('Flipper' => '0.74.0')

fixed this issue for me
add_flipper_pods!('Flipper' => '0.74.0')

fixed this issue for me
add_flipper_pods!('Flipper' => '0.74.0')

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

That worked like a charm . Thanks.

I have facing this issue couple of day ,I got the solution
remove the flipper from pod file or comment out
use_flipper!
post_install do |installer|
flipper_post_install(installer)
end
again pod install
its working .

this works for me, but then after i add any packages to my project i face this problem all over again!

any suggestions?

specifically after installing react-native-vector-icons

@sotomaque
Update your ios/Podfile to target the specific version. Not in the lockfile but the actual Podfile.
versions['Flipper-Folly'] ||= '2.3'
Then run from main directory
npx pod-install --repos-update && npm run start -- --reset-cache
Then clean and rebuild from xcode.

go to your project folder
open the ios folder
open Podfile
comment these lines:

use_flipper!
post_install do |installer|
  flipper_post_install(installer)
end

go to the ios folder in the terminal and type pod update

return to your project folder and type react-native start

open a new terminal and type react-native run-ios

that's it :)
example below:

thanks @Jorge-Luis-Rangel-Peralta you helped a lot

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

Awesome, thanks!

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

This fix worked for me. Thanks!

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

This fix worked for me. Thanks!

Also, remove Pods/ & Podfile.locl, then run npx pod-install

For Apple Silicon users,
simply install libevent then add CPLUS_INCLUDE_PATH=/usr/local/ before the start command.(if your homebrew is installed in x86_64 prefix) will solve this problem.

upgrading flipper to v0.74.0 fixed this issue for me
use_flipper!('Flipper' => '0.74.0')

this is also somehow related to cocoapods version. cocoapods version 1.10.1 + seems to solve most problems while lower versions install flipper dependencies incorrectly

This works for me!

This breaks the env setup here for me btw

Should read setup from flipper here and update to new version could fix this issue: https://fbflipper.com/docs/getting-started/react-native-ios

For Apple Silicon (M1 Chips):
This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })
This fix worked for me. Thanks!
Also, remove Pods/ & Podfile.lock, then run npx pod-install

use_flipper!({ 'Flipper-Folly' => '2.3.0' })

Thanks @michaelgmcd, that worked fine!

upgrading flipper to v0.74.0 fixed this issue for me
use_flipper!('Flipper' => '0.74.0')

this is also somehow related to cocoapods version. cocoapods version 1.10.1 + seems to solve most problems while lower versions install flipper dependencies incorrectly

0.75.1 is out now with some additional libevent fixes, and pinning to that in the Podfile worked, while letting the npx react-native init figure out the right/latest version wasn't pulling a newer version for the Podfile and I was stuck with 0.58 or whatever was baked into an old version of the template.

Upgrading flipper to v0.78.0 worked for me (react-native 0.62.2)

In my case, I solved this by upgrading Flipper to v0.78.0

Made this change on ios/Podfile
use_flipper!({'Flipper' => '0.78.0'})
Make sure installed pods are up-to-date
pod repo update
pod cd ios && pod install && cd ..
Re-run application
npx react-native run-ios

in my case, i also solved this problem by upgrading Flipper to v0.78.0

cd ios/Podfile
replace use_flipper! by use_flipper!({'Flipper' => '0.78.0'}) then pod install ,yarn ios ,it works!

Upgrading Flipper to v0.78.0 fixed my case too :+1:

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

After upgraded from 0.62.2 to 0.63.4, I got this issue. Fixed by upgrading Flipper-Folly to 2.3.0 in ios/Podfile. Thank you 🙏

Just update flipper is work.
use_flipper!({'Flipper' => '0.79.0'})

use_flipper!({'Flipper' => '0.78.0'}) did work, but also updating Ruby to latest (3.0.0p0 (2020-12-25 revision 95aff21468)) and updating cocoapods made it so I didn't have to continue to repeat these above steps. Something to consider if your Ruby version is fairly old (mine was running on a 2019 build)

All attempts of change to use_flipper!({'Flipper' => '*.*.*'}) did not work for me. It always fail the build with the same error https://github.com/facebook/react-native/issues/31181#issuecomment-801802805

It worked for me.
My environment is:
"react": "16.13.1",
"react-native": "0.63.2",
Update this change on ios/Podfile
use_flipper!({'Flipper' => '0.79.0'})
Make sure installed pods are up-to-date
pod repo update
cd ios && pod install && cd ..

And build it through Xcode -> Product -> Build

For me I could get around it by:

remove ios/Pods
cd ios && pod repo update
sudo gem install cocoapods
npx pod-install

this is not working

It worked for me.
My environment is:
"react": "16.13.1",
"react-native": "0.63.2",
Xcode: "12.4"
Update this change on ios/Podfile
use_flipper!({'Flipper' => '0.79.0'})
Make sure installed pods are up-to-date
pod repo update
cd ios && pod install && cd ..

And build it through Xcode -> Product -> Build

this idea is working for me

[Solved] ‘event2/event-config.h’ file not found in React-Native

I was able to fix this by updating all npm packages to their latest build with 'yarn upgrade --latest' and deleting the pods folder and reinstalling.
use_flipper! worked just fine after that.

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

Hi, i am getting this issue while trying to update flipper-folly inside Podfile
[!] CocoaPods could not find compatible versions for pod "Flipper-Folly":
In Podfile:
Flipper-Folly (= 2.3.0)
FlipperKit/Core (~> 0.75.1) was resolved to 0.75.1, which depends on
  Flipper (~> 0.75.1) was resolved to 0.75.1, which depends on
    Flipper-Folly (~> 2.5)

Specs satisfying the Flipper-Folly (= 2.3.0), Flipper-Folly (~> 2.5) dependency were found, but they required a higher minimum deployment target.
XCode: 12.5
React-Native: 0.64.0

This issue is caused by an update to the "Flipper-Folly" pod-spec. If you'd like to keep Flipper enabled, you can override the version in your Podfile:
use_flipper!({ 'Flipper-Folly' => '2.3.0' })

Hi, i am getting this issue while trying to update flipper-folly inside Podfile
[!] CocoaPods could not find compatible versions for pod "Flipper-Folly":
In Podfile:
Flipper-Folly (= 2.3.0)
FlipperKit/Core (~> 0.75.1) was resolved to 0.75.1, which depends on
  Flipper (~> 0.75.1) was resolved to 0.75.1, which depends on
    Flipper-Folly (~> 2.5)

Specs satisfying the Flipper-Folly (= 2.3.0), Flipper-Folly (~> 2.5) dependency were found, but they required a higher minimum deployment target.
XCode: 12.5
React-Native: 0.64.0

same here

Using latest versions works for me
use_flipper!({'Flipper' => '0.91.1', 'Flipper-Folly' => '2.6.7', 'Flipper-RSocket' => '1.4.3'})

Using latest versions works for me
use_flipper!({'Flipper' => '0.91.1', 'Flipper-Folly' => '2.6.7', 'Flipper-RSocket' => '1.4.3'})

it's work for me

It worked for me with the latest flipper
use_flipper!({ 'Flipper' => '0.95.1', 'Flipper-Folly' => '2.6.7', 'Flipper-RSocket' => '1.4.3'  })

I meet this issue on 0.63.4 , and I fix it by setting up 'System header search path'  on some targets : FlipperKit, Flipper, Fliiper-Folly with value: "$(PODS_ROOT)/libevent/include" no-recursive
Another method you could upgrade to 0.64

Choose to use ReactNative you'd better master iOS/Android native development, cause RN is not stable at least development environment.

It worked for me.
use_flipper!({ 'Flipper' => '0.122.0' })
pod install --repo-update


Update PT-BR Language + Fix quotation mark missing

Hello Moffein, I fixed a startup error where a quote was missing in one of the items in PT-BR. I also translated an Acrid ability that I ended up forgetting and improve some other things. However, I noticed some small errors that are beyond my ability to fix, so I'm passing them on:
The following skills are not translating:
CROCO_UTILITY_DESCRIPTION_RISKYMOD
CROCO_UTILITY_ALT1_DESCRIPTION_RISKYMOD
CROCO_SECONDARY_ALT_DESCRIPTION_RISKYMOD
MAGE_PRIMARY_LIGHTNING_DESCRIPTION_RISKYMOD
MAGE_PRIMARY_FIRE_DESCRIPTION_RISKYMOD
The following skills are not appearing in PT-BR:
MAGE_SPECIAL_SITHLIGHTNING_NAME_RISKYMOD
MAGE_UTILITY_FIRE_NAME_RISKYMOD
idk if you prefer me to create an 'Issue' or just leave everything here, as I did hahahaha

Seems like the issue was caused by a formatting error in Survivors.txt, fixed it on my end.
For future reference, I recommend pasting the text into https://jsonlint.com/ to validate the formatting.
No need to click the "Validate JSON" button (it will fail and say Invalid JSON), just make sure the colors look right and you're good to go.

Hi, wasn't sure how to contact you, but if you're still looking to translate RoR2 mods, SS2 Unofficial recently got language support.
https://github.com/Moffein/Starstorm2Unofficial/tree/main/Starstorm 2/Starstorm2Release/plugins/ChirrLover-Starstorm2Unofficial/language

Hey, I've been a bit busy with college and everything, so I haven't been using GitHub for months hahahaha. I'll try to translate your mods sap. If you need to contact me more easily, you can reach me on Discord. My username is "kauzoka" with a profile picture of Ryan Gosling as Ken, just in case you need to know lol.


JSDocs?

It would be really nice if every redis command provided a description inside vs code.
If i knew how to do this, I would definitely send a PR.
Example:

PS: I don't know why this is marked as a bug even though i selected feature request.

Since the library is made in typescript its not pratical to do comments like that specially because typescript was made to avoid this.
I would rly recommend getting used to ts types bcz they serve as documentation in a lot of cases

ah, i got it. I personally think it looks cleaner in the non ts way, but ill try. thanks.


auro-datepicker: Addressing the CSS parts inside the date picker.

Describe the bug
auro-datepicker does not have CSS parts to modify the style, in the same way that it is currently in auro input and other auro components.
Expected behavior
Allow to modify the style of auro-datepicker the same way it is available for other auro components CSS parts.
Screenshots
E.g. Auro input

The proposed solution is good.
Exit Criteria
This issue can be closed once there is a demonstratable option for end users to customize the look of the baseline element via CSS Parts.


Snake demo ci build fails silently on the last step

It's to do with a bin compat problem between os-lib 0.7.8 and 0.8.0, but I'm not clear where the problem is coming from - a cache?!? - and I can't replicate locally.

Have upgraded workflow to use Mill 0.10.0. Hopefully that will do the trick...

This appears to have been fixed by https://github.com/PurpleKingdomGames/indigo/commit/a65e12f77200edac6d27734ff77a7df11e6455b4


Is there a way to get that other fake tree-of-thoughts repo taken down?

Sorry if this isn't the place to post his inquiry, but I had, at first, given up on your process while thinking this spamming troll was you guys. Obviously, it's auto-generated fake code that doesn't really work, but has a toxic effect on your reputation.
https://github.com/kyegomez/tree-of-thoughts
I feel so sickened that this fraud is willing to make so many fooled by him that didn't catch on lose faith in your research, robbing you of countless citations to your credits and potential future breakthroughs just for some github stars. Can I post a reward somewhere for whomever shuts it down or something?

it's not fake, it's an implementation. Nowhere did i say it's the original implementation of tree of thoughts.
And, no it cannot be taken down this is open source. And i'm not robbing anybody of anything. I provided an repository when there was no code or anything.

Hi, I'll add "official implementation" into the description and link to other implementations later in readme. @kyegomez it would be nice if you can also link to ours in your repo to explain? thanks!

@jakderrida thanks for making this concern public, I was also quite confused by the "more popular" repo.
The entire description in @kyegomez's gives off weird vibes/hype, as if it's the culmination of @kyegomez's life's work.
It's important to clarify the distinction between the original research and its implementations to avoid confusion. Giving explicit credit and clearly stating that a repository is an implementation rather than the original research is just a good practice.

Obviously, it's auto-generated fake code that doesn't really work

I cannot assert whether it's a fraud, but it certainly feels overly-enthusiastic.
In situations like these, it's always beneficial to provide clear and accurate information to avoid any misunderstandings or misinterpretations.

And, no it cannot be taken down this is open source. And i'm not robbing anybody of anything.

I kindly suggest making the necessary updates in @kyegomez's repository to make the distinction more explicit. It's not just about a project being Open Source. Clear communication within the open-source community are equally crucial for maintaining transparency and promoting proper attribution, because these are the core principles behind Open Source.
Linking to this repository would suffice to clear this apparent confusion.

Can anyone suggest what I can do? E.g. https://docs.github.com/en/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice ?

Given the radically rude and unbelievable responses in https://github.com/kyegomez/tree-of-thoughts/issues/54 https://github.com/kyegomez/tree-of-thoughts/issues/55 https://github.com/kyegomez/tree-of-thoughts/issues/56 I have no choice but to report to Github for abuse and repo takedown. Stay tuned.
I explained the situation on twitter: https://twitter.com/ShunyuYao12/status/1663946702754021383 thanks if you can spread the words and clarify about the right code for ToT

Rude?

Hi Shunyu
Sorry to see you having to deal with this. I just want to pass on my congratulations for your incredible work - you’re inspiring many people around the world, including some of us way down under.
I hope this situation with the other implementation can be resolved and it is labelled more appropriately to avoid creating such obvious confusion.
keep up the great work my friend.

Hi, I'll add "official implementation" into the description and link to other implementations later in readme. @kyegomez it would be nice if you can also link to ours in your repo to explain? thanks!

Thank you so much. I know the paper should have been sufficient. However, I suppose I got overly excited to think it was done early and that was followed by abject disappointment, followed by a notification from Reddit mods that the other one wasn't by the researcher. Don't get me wrong. I was certainly excited to try it again, as was everyone I notified that the repo I posted was not the one from the paper. It really is an incredibly novel solution that I've found numerous uses for already.
Much appreciation,
Tom

It is only a "real issue" because people like you give it attention. Your
attention is valuable and one way you can resolve the problem is to stop
paying any of your valuable attention to things that you cannot control. I
do understand your concern and can empathize, but it is important to
acknowledge that there are a diverse set of people with a diverse set of
beliefs and the best you can do is challenge others without trying to
impress your beliefs upon them. It seems as though this has been done
already, and there are more meaningful ways to spend your attention.
On Wed, May 31, 2023 at 11:28 AM Shunyu Yao @.***>
wrote:

I raised an issue at kyegomez/tree-of-thoughts#54
https://github.com/kyegomez/tree-of-thoughts/issues/54 but closed by
@kyegomez https://github.com/kyegomez without any resolving. I think
this might be a real issue now.
—
Reply to this email directly, view it on GitHub
https://github.com/ysymyth/tree-of-thought-llm/issues/17#issuecomment-1570548040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC6X2TVMVYU2JM3HRROEWDXI5WSRANCNFSM6AAAAAAYRLMM2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Well, I only regret bringing it up because I failed to consider that the maker of this repo might reach out to the other "coder" not realizing he's a troll that would definitely respond as trolls do. As for bringing it up at all; it was a genuine inquiry regarding what can be done about someone that obviously auto-generated crap that was embarrassingly and obviously intended to mislead others into thinking it was by the actual hard-working researchers. Why do I think that's a problem? Good question. It hurts their reputation and jeopardizes the ability for their work to get what I believe is proper credit. It's one thing if the other repo was of the same quality as this one and posted free of any ill intent. However, that's definitely not the case. Also, to another comment saying they can't speak to whether it was autogenerated, please go to the first rendition of their repo and ask yourself if human-made code is typically filled with fake repos that literally don't exist. That's something only generative AI does. Usually because the package exists in another language and it just hallucinates that it exists with the one you're using.


Rounded TextField with label

Steps to Reproduce

Hi,
I created a customized textfield with a label but it's focused state does not render properly.
Here is the example code:
https://gist.github.com/leonardodavila/3ef131e7cbe2f445b088aa7d7a098331
Screenshots:

Thanks for reporting this!  I can reproduce it, and it doesn't seem to be a regression as it happens at least back to the end of 2018.
When the border radius is too much for the size of the input, the ends overshoot like in the screenshot above.  Instead, it should top out at a circular end and not increase the radius anymore, which is the behavior when there is no label.  Even when the border radius is more reasonable, the part of the border near the label is weirdly missing (see screenshot below).  That should be fixed too.

@leonardodavila To work around this in the meantime, try lowering the border radius.  You might be able to get something that looks acceptable.  The other option is to remove the label.  I know neither workaround is ideal, so hopefully we can get this fixed!

Hey justin,
Thanks for the help, i lowered the border radius but it was just like yours. And i can't remove this component because is part of my company's design system. So, i'll have to find someway to do it. But thanks for the help.

Hi @leonardodavila
I wasn't able to reproduce this issue using your sample code

Code Sample
// Flutter code sample for material.AppBar.actions.1

// This sample shows adding an action to an [AppBar] that opens a shopping cart.

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

/// This Widget is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Volanty';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      theme: ThemeData(
          fontFamily: 'SourceSansPro',
          appBarTheme: AppBarTheme(color: const Color(0xFF2F4F98))),
      debugShowCheckedModeBanner: false,
      home: MyStatelessWidget(),
    );
  }
}

/// This is the stateless widget that the main application instantiates.
class MyStatelessWidget extends StatelessWidget {
  String value = "";

  TextEditingController controller = TextEditingController();
  MyStatelessWidget({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      drawer: Drawer(
        child: ListView(
          // Important: Remove any padding from the ListView.
          padding: EdgeInsets.zero,
          children: <Widget>[
            DrawerHeader(
              child: Text('Drawer Header'),
              decoration: BoxDecoration(
                color: Colors.blue,
              ),
            ),
            ListTile(
              title: Text('Item 1'),
              onTap: () {
                // Update the state of the app
                // ...
                // Then close the drawer
                Navigator.pop(context);
              },
            ),
            ListTile(
              title: Text('Item 2'),
              onTap: () {
                // Update the state of the app
                // ...
                // Then close the drawer
                Navigator.pop(context);
              },
            ),
          ],
        ),
      ),
      appBar: AppBar(
        title: Text('Volanty'),
        actions: <Widget>[
          IconButton(
            icon: Icon(Icons.search),
            tooltip: 'Buscar veículo',
            onPressed: () {
              // Implement navigation to shopping cart page here...
              print("OI");
            },
          ),
        ],
      ),
      body: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: [
          Center(
              child: Container(
                  width: 300,
                  child: TextField(
                    decoration: new InputDecoration(
                        border: new OutlineInputBorder(
                          borderRadius: const BorderRadius.all(
                            const Radius.circular(50.0),
                          ),
                        ),
                        filled: true,
                        labelText: "Email ID",
                        labelStyle: TextStyle(
                          color: Colors.grey,
                        ),
                        fillColor: Colors.white70),
                  )))
        ],
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel dev, v1.18.0, on Mac OS X 10.15.4 19E266, locale en-GB)
    • Flutter version 1.18.0 at /Users/taha/Code/flutter_dev
    • Framework revision 8f7327f83a (2 days ago), 2020-04-06 22:11:01 -0400
    • Engine revision 49891e0653
    • Dart version 2.8.0 (build 2.8.0-dev.20.0 1210d27678)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.9.1
[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.0.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
[✓] VS Code (version 1.44.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1
[✓] Connected device (3 available)
    • macOS      • macOS      • darwin-x64     • Mac OS X 10.15.4 19E266
    • Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.92
    • Web Server • web-server • web-javascript • Flutter Tools
• No issues found!
taha@Tahas-MacBook-Pro AndroidStudioProjects % flutterd doctor -v
[✓] Flutter (Channel dev, v1.18.0, on Mac OS X 10.15.4 19E266, locale en-GB)
    • Flutter version 1.18.0 at /Users/taha/Code/flutter_dev
    • Framework revision 8f7327f83a (2 days ago), 2020-04-06 22:11:01 -0400
    • Engine revision 49891e0653
    • Dart version 2.8.0 (build 2.8.0-dev.20.0 1210d27678)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.9.1
[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.0.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
[✓] VS Code (version 1.44.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1
[✓] Connected device (5 available)
    • SM M305F      • 32003c30dc19668f          • android-arm64  • Android 10
      (API 29)
    • Taha’s iPhone • 00008020-001059882212002E • ios            • iOS 13.4.1
    • macOS         • macOS                     • darwin-x64     • Mac OS X
      10.15.4 19E266
    • Chrome        • chrome                    • web-javascript • Google Chrome
      81.0.4044.92
    • Web Server    • web-server                • web-javascript • Flutter Tools
• No issues found!

if you're still experiencing this issue, please comment below and i will reopen it
Thank you


1.6.3 seems to stop reporting data

Description
Upgrading from 1.6.2 to 1.6.3 completely stopped the reporting of data.
Expected behavior
Data should be reported as before.
Actual behavior
The analytics dashboard reports 0 active people and 0 events in real time.
Environment
Run this command in the project folder and fill in their results:
npm ls vue-gtag:
Then, specify:

Operating system: MacOS 10.15.5
Browser and version: Chrome 83.0.4103.97

I think that I know why. there was this complain of an extra hit on load all the time so I removed it from the bootstrap, but then I saw that the library method $gatg.pageview is using gtag page_view event which doesn't send the ID on hit.
I will look into it asap
thanks for the feedback

I have to admit: gtag.js documentation is still quite mysterious sometimes. they could have done a better job. especially for SPA

:tada: This issue has been resolved in version 1.6.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Hasn't this issue recurred with recent versions including vue-gtag 1.9.1?
I found out that https://www.google-analytics.com/j/collect?v=1&_... does not get loaded with the version 1.9.1 while specifying the version to 1.6.4 in the package.json allows the collect script to be loaded.
The collect script seems to be necessary for the Google Analytics Realtime report to work.

@MatteoGabriele
Hasn't this issue recurred with recent versions including vue-gtag 1.9.1?
I found out that https://www.google-analytics.com/j/collect?v=1&_... does not get loaded with the version 1.9.1 while specifying the version to 1.6.4 in the package.json allows the collect script to be loaded.
The collect script seems to be necessary for the Google Analytics Realtime report to work.

@shumiyao I'm not sure about that script there, but there's nothing indicating the need to load a second script while bootstrapping gtag.js

@MatteoGabriele
We do not need to load the "collect" script at all. It is loaded automatically when we load https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXX-XX
The access to collect script is not requested when I use the latest of 1.9.1 but it works when I specify the vue-gtag version of 1.6.4. Can it be related to vue-gtag?

still not quite sure, but 6 new version have been published after 1.6.4, can you identify after which one this stops working for you, then will be easier to identify a possible cause of this malfunctioning

Sure. I will try by this evening.

thanks a lot for you help @shumiyao
really appreciated

@MatteoGabriele
I compared outputs between 1.64 and all other 5 versions. All the version after 1.7.0 do not seem to work with the Google Analytics.
The only differences I could find were whether 2&l=dataLayer is included in the url (www.googletagmanager.com/gtag/js?) or not:

@shumiyao but the &l={DATALAYER_NAME} is supported by the official documentation https://developers.google.com/gtagjs/devguide/datalayer#rename

@MatteoGabriele
That was the only difference I could find between different versions. Any chance that we could suppress the DATALAYER_NAME?

I will have a look later. Thanks for your debugging

@MatteoGabriele
I did not do anything at all. Thank you for your attention and your time. Have a nice day!


Update cache and setup-python Actions

Attempting to resolve or at least reproduce the PySpark install error in checks on #241.
https://github.com/broadinstitute/gnomad_methods/pull/241/checks?check_run_id=929532907

The release notes for the two updated actions can be found in their repositories:
https://github.com/actions/setup-python/releases
https://github.com/actions/cache/releases
Updating those actions was partly just to see if the PySpark installation error was reproducible on another PR. The actual fix for the issue is the second commit that installs the wheel package.
The error message for PySpark installation in checks on #241 and this PR included error: invalid command 'bdist_wheel' and the wheel package contains "A setuptools extension for building wheels that provides the bdist_wheel setuptools command."


Copy+Paste: Clicking "Stop Sharing" will trigger disconnect error before getter starts getting.

As soon as the getter pastes the URL from the sharer, the sharer will see the "Stop Sharing" button.
Even if the getter has not started proxying, if the sharer clicks "Stop Sharing," the getter will see:

This is confusing because the user's proxy settings are not set and they are browsing on their local connection.
I think instead they should see this screen:

Except maybe we can change the first sentence to "Your one-time connection session has ended."

Closing as copy+paste has been deprecated.


Modal openModalV2() gives me a slot error

I am trying to create several modal objects for different pieces of data. Whenever I use the openModalV2() command I get the error <ModalV2> received an unexpected slot "default".
I'm calling the command like so and want to embed a svelte component called PlayerBox. Any ideas what I'm doing wrong here?
 openModalV2(player)}>{player.name}
 <ModalV2 let:payload let:close>

 {payload}
 <button class="close" on:click={close}>×</button>
<PlayerBox player={player} />

</ModalV2>

The way I got it to work without errors was sending the component I wanted to open and its properties as the payload and not trying to put anything between the <ModalV2> tags. In fact I used <ModalV2 /> as a self-closing tag.

 openModalV2(PlayerBox, {player: player})}>

In this setup <ModalV2 /> opens a component called "PlayerBox", which needs a property called "player."


How to support the development?

This time, not a bug report or a feature request, but a question about the project: are you open to donations, or is there any "standard" way to support the project and its development/developer, if not financially? :)
Side-question: I see some commits still being done upstream (emmylua) - any plan to cherry-pick those (at least what's still doable of course)

At this time I'm not really taking donations for this project in particular. If it gets more popular I suppose I could setup Github sponsorship.
For now the best way to contribute is via code contributions. If it's anything other than a small bug fix then opening an issue and having a discussion first would be best.

Side-question: I see some commits still being done upstream (emmylua) - any plan to cherry-pick those (at least what's still doable of course)

The code-base has certainly diverged much more than I ever intended. So it's unlikely upstream patches will apply cleanly. If you come across a commit that specifically addresses some pain point your bumping up against, please open an issue here referring to EmmyLua commit and I'll take a look at what needs to be done.

At this time I'm not really taking donations for this project in particular. If it gets more popular I suppose I could setup Github sponsorship.
For now the best way to contribute is via code contributions. If it's anything other than a small bug fix then opening an issue and having a discussion first would be best.

Side-question: I see some commits still being done upstream (emmylua) - any plan to cherry-pick those (at least what's still doable of course)

The code-base has certainly diverged much more than I ever intended. So it's unlikely upstream patches will apply cleanly. If you come across a commit that specifically addresses some pain point your bumping up against, please open an issue here referring to EmmyLua commit and I'll take a look at what needs to be done.

 I was actually approved for Github Sponsors all the way back when it was in closed beta. Fortunately, according to the banner on my profile, I'm actually still eligible for Github's Sponsors Matching Fund. So, if received in the next 12 months, Github will match the first $5000. Not too shabby.
Closed by https://github.com/Benjamin-Dobell/IntelliJ-Luanalysis/commit/1c2c9cb85b8abce0fd576162e1cde470e797be36


Add a new "check" for new "needs-copy-editing" label in main astropy repo

We (@kelle @eteq @lglattly) have just added a new label to the main astropy repo: "needs-copy-editing". This label indicates that a given pull request touches the documentation and needs to be reviewed by @lglattly. The bot should check for the combination of "docs" and "needs-copy-editing" and fail a check if both are set on a pull request. This also means that, when applying the docs label to a pull request, we should also add the "needs-copy-editing" label. @lglattly will then remove the label after reviewing.
If possible, we should also have the bot request a review from @lglattly.

We've copyedited the copyedit label (F2F) and have figured out copyedit (verb) is one word. The label is "needs-copyediting".

For anyone interested in tackling this, this just involves writing a small plugin similar to https://github.com/astropy/astropy-bot/blob/master/astropy_bot/changelog_checker.py (but much much shorter)

Cool, thanks! I'll give it a try.

@adrn , API is at https://github.com/OpenAstronomy/baldrick . FYI. 🤖

While we are at this, maybe auto assign @adrn for review of PRs from @lglattly ?
p.s. I think this is a subset of #65 and maybe also a subset of a bigger question of enabling a feature like https://help.github.com/en/articles/about-code-owners


Change IPHONEOS_DEPLOYMENT_TARGET in project template to 8.0

My Xcode (7.3) is adding IPHONEOS_DEPLOYMENT_TARGET = 8.0; to line 348 to match the version on line 329. I wonder if we should add it there, too.


DruidViewMacro: Remove unused escalator field.

It isn't used.

Should DruidViewMacroFactory also be updated to remove the escalator argument?

@kfaraz Good point; I removed that as well.


Auto-Generate Unique Indexes

The Problem
Currently (as outlined in the README) there is no unique indexes on redirects.token nor user.name. The README mentions that you should add these after creating the db (which happens automatically the first time the app is run).
It seems to me that this should happen automatically.
The Solution
Adding the indexes by getting a hold of the ColumnMap during mapForDatabase. This is only used during creation, meaning there is no kind of validation. For this particular case, I'm ok with that.

ping @Karlhungus

I'm incredibly jealous of your golang knowledge.


cannot access local variable 'settings' where it is not associated with a value

Describe the bug
When attempting to add OctopusEnergy account, it shows the following error
cannot access local variable 'settings' where it is not associated with a value
However i can see my meter MPAN number if I am to manually add an entity, so assuming the connection to fuel vendor is successful.
Reproduction steps
Add integration, fill in API key and Account Number
Expected behaviour
There is no error message and integration is set up
Tariff Code
No response
Integration Version
v8.3.0
Home Assistant Version
2023.9.3
Fresh Install?
Fresh install
Home Assistant Logs
Unexpected error fetching intelligent_settings data: cannot access local variable 'settings' where it is not associated with a value
Traceback (most recent call last):
File "/lsiopy/lib/python3.11/site-packages/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/lsiopy/lib/python3.11/site-packages/homeassistant/helpers/update_coordinator.py", line 246, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/octopus_energy/coordinators/intelligent_settings.py", line 51, in async_update_intelligent_settings_data
if settings is not None:
^^^^^^^^
UnboundLocalError: cannot access local variable 'settings' where it is not associated with a value

I believe this was an issue on the develop branch (which is noted to be in flux and unstable), not on the latest release based on the line number. However it will be fixed for the next release.

thanks @BottlecapDave  you are indeed correct. i had thought i used the release but actually the develop branch.


Improve Github Actions

This is an attempt to remove some of the manual work required to prep releases and make the output in the actions tab on GitHub a little easier to follow:

[x] Remove if statements from the tests.yml workflow
[x] Add a new workflow file that can trigger the building and pushing of a gem to RubyGems and GitHub Packages when a tag is specified. This should be a gated (manual) task.

Example of it working and pushing to RubyGems.


Develop Initial User Journey Designs

Define a list of user journeys, and prioritize 2-3 to product low-fidelity designs.
See sub-tasks for details

📆 November status: on schedule

https://www.figma.com/file/wzRO1Hr3bkykHVxOpVLQSX/User-Journeys?node-id=25%3A2

📆 December status: on schedule

📆 January status: journeys continue to evolve and be built and present to WMWG. delayed on sprint to ensure we cover a sufficient number of journeys before moving on to higher fidelity designs


readme: add Communication section in readme

Signed-off-by: Calvin Weng<EMAIL_ADDRESS>
What have you changed? (mandatory)

Added Communication section in readme as suggested by Siddon

What are the type of the changes? (mandatory)

Improvement

Anything else to add？

Awesome awesome stuff @dcalvin 🥇 LGTM


Does it not make sense to use memo and PureComponent

This is really helpful with a project im working on lately. Thanks for it. Im just wondering doesn't it make sense to wrap functional components with memo and extend class components from PureComponent? That what I have been manually doing with the output. I could work on a PR if everyone agrees to this.

Sure, that would be nice.
Maybe add a new checkbox which will toggle memo/PureComponent?

Added here.


NO MERGE: Codesee tests

Just testing this thing... but I need to open a PR for it to trigger

Not necessary right now. I have enough with this for some tests.

Not deleting the branch though, in case we need some updating while testing


Enable Unified Mode

Remove delivery and move to calling RSpec directly via a reusable workflow
Update tested platforms
Enable unified_mode and require Chef >= 15.3
Start nagios service

Released as: 11.0.0


Blog 6.2.2 loading up the event viewer with get_item exceptions

I have this running on DNN 7.4.2.
I'm currently seeing error being written to the event log very often.  About 100 times over the past 10 hours alone.
Anyone else running into this, or know what the cause might be?  I'd be willing to put in a PR if someone could point me in the right direction.
2/18/2016 1:23:51 PMGeneral Exception    AbsoluteURL DefaultDataProvider DotNetNuke.Data.SqlDataProvider DotNetNuke
AbsoluteURL:
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:f748505e-66c1-433b-b888-1e5f588af61a
AssemblyVersion:
PortalId:-1
UserId:-1
TabId:-1
RawUrl:
Referrer:
UserAgent:
ExceptionHash:Sw4jmWcaIHQ6SIgZu2hzPg==
Message:NrComments
StackTrace:
at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
at System.Data.SqlClient.SqlDataReader.get_Item(String name)
at DotNetNuke.Modules.Blog.Entities.Posts.PostInfo.Fill(IDataReader dr)
at DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)
InnerMessage:
InnerStackTrace:
Source:System.Data
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:
Server Name: [REMOVED]

Still an issue.

This must be unique to my instance since there's not been any activity on this issue.  I was getting sometimes hundreds of this same exception every few minutes.  I don't why it's happening, but if I replace this line below:
NrComments = Convert.ToInt32(Null.SetNull(dr.Item("NrComments"), NrComments))
With this, the error goes away.
Try
    NrComments = Convert.ToInt32(Null.SetNull(dr.Item("NrComments"), NrComments))
Catch
    NrComments = 0
End Try

I'd submit this as a PR, but I'm not running on DNN 8 and am unsure of which brand to participate in.

I'll move NrComments to the view so it appears in all results


Can delete more than one profiles at one time

aiidalab-launch profiles delete now only accept one profile a time to delete. -a for delete all maybe too much but at least I can put more profiles to delete at once.

Here is how I did in order to remove the volumes created with the container, I first stop the container and remove the container, which also should be managed by aiidalab-launch profiles remove
docker volume rm $(docker volume ls -qf dangling=true)

I am quite conflicted about this feature. It seems like an unnecessary complication and potentially dangerous, given that the workaround is to use a simple BASH loop or xargs. Also since we renamed the subcommand from profiles to profile it also seems confusing in that sense.
For example this oneliner would delete all profiles including the volumes (after #172 is merged)
aiidalab-launch profile list | awk '{print $1}' | xargs -n 1 aiidalab-launch profile delete --purge --yes


Updated ImageCache utility

Improved ImageCache to avoid accessing environment warnings.
There was a warning "Accessing Environment's value outside of being installed on a View. This will always read the default value and will not update." I have changed property wrapper @Environment to custom @Injected to avoid warnings. More details about injected described here: https://www.avanderlee.com/swift/dependency-injection/

Good job 👍🏻


JSON Patch spec compliance

Correct me if I'm wrong, but it seems to me that the modify middleware expects request body in a different form than the one described in the extension specification.
The example from the spec (there is no object wrapping the op array):
[
  { "op": "replace", "path": "/src", "value": "http://example.com/hamster.png" }
]

The way modify expects it:
{
  "data": [
    { "op": "replace", "path": "/attributes/src", "value": "http://example.com/hamster.png" }
  ]
}

As far as I understood, prefixing modified field's path with "/attributes" shouldn't be required, as attributes and relationships cannot have identically named fields. Extension spec also mentions that the request URL and operation's path combined must form a valid path to a collection or a (sub)resource.

@hkosiacki You're right. This will be fixed in next version


When can we expect Strapi 5 support?

Can you confirm the target date for the plugin update to support Strapi 5?

We are targeting mid October 2024

October has ended today....

We are still working on porting, it's not that easy with such complex functionality ;) next weeks should give us first beta

thanks

Thanks

It has been just released in version 3.0.0-beta.0. Keep in mind it's early beta and the migration was HUGE so might be still a bit buggy - but we're working on it daily to fix and improve the quality :)


ImportError: No module named derived_object_msgs.msg

Hello，everyone
I download the prebuilded  version of Carla ,and I completed to  Install the CARLA Python API according to the guide(https://github.com/carla-simulator/ros-bridge),runnning this:
python -c 'import carla;print("Success")' ,Show success message without any error.
But when I run:
roslaunch carla_ros_bridge client.launch
there is the following error:
ImportError: No module named derived_object_msgs.msg
How can I solve this problem?

Hi,
you need to install the derived-object-sensor package for ROS, e.g. something like
ˋˋˋ
apt-get install ros-kinetic-derived-object-sensor-msgs
ˋˋˋ

@fabianoboril
Thanks！

Hi guys, I'm having the same problem here. Did you guys find a solution? Thanks..

The solution is listed above and therefore the issue is closed.
Did you install those:
apt-get install ros-kinetic-derived-object-sensor-msgs

if you Unable to locate package ros-kinetic-derived-object-sensor-msgs, try this
apt-get install ros-kinetic-derived-object-msgs

in foxy, it is sudo apt install ros-foxy-derived-object-msgs


set specimin repository path as environment variable

Professor, substitute of PR: https://github.com/tahiat/specimin-evaluation/pull/14
Thanks for the suggestion.


Question: how can I ensure the app is running in process?

Hi, I've read the blog post about preview1 and I decided to give it a try, so I installed everything and created a web api project, configured in IIS and fired up wrk (installed in the same machine via WSL) to have a look at the perf.
The blog post says your findings are that in process delivers up to 4.4x request throughput, but my numbers are a bit different i.e. the numbers are almost identical to the out of process ones so I would like to be sure I'm not missing something.
The api I used for the test is the ValuesController GET method generated by the template which returns a fixed "value" string.
What I find strange is that while performing the in process tests, I still saw a dotnet.exe process.
If you are interested in the numbers, you can find them here

You can check for server variables, those are only supported in-proc.
https://github.com/aspnet/IISIntegration/blob/810c4bcb0a29fb5f273a0c2b26b37e4ee431d05c/samples/NativeIISSample/Startup.cs#L67-L72

From those perf numbers and the fact that dotnet.exe is starting, my guess is you are still running of of process. Can you confirm inside of your published application that the hostingModel="inprocess" is set?

What's in the gist under "IIS ANCM 2.1 preview1 hosting in process" have hostingModel="inprocess" and "IIS ANCM 2.1 preview1 hosting out of process" doesn't have the hostingModel attribute at all

You can also specify the hostingModel="outofprocess" to work with out of process. If no hostingModel is specified, we default to outofprocess. This is for backwards compatibility with older web.config files.
@BillHiebert I think we should default to having the hostingModel="outofprocess" for generated web.config files rather than it being empty. Thoughts?

That would fail on hosts with outdated schemas.

I will look into this tomorrow morning.
Do you think it's reasonable to expect a noticeable improvements when running in-process?

Yes. If you don't see noticeable gains, we need to investigate why.

Great, because I'm experimenting perf to replace an old WCF service with a brand new shiny asp.net core web api :)
So I started measuring perf of the old WCF vs the new asp.net core web api and turned out that asp.net core hosted in Kestrel outperforms WCF hosted in IIS Express (+1139%) but when hosted in IIS, asp.net core is actually slower (don't remember now how much slower, but if you are interested I can get back on this) than WCF and the latency is higher

That's odd, you shouldn't get that much variation between IIS and IIS Express.

I'll get back with more numbers tomorrow, btw @Tratcher what do you think about a ~5 times drop from Kestrel to IIS out of process?

Looks like context.GetIISServerVariable is not available in my version of Microsoft.AspNetCore.Server.IISIntegration. it's a bit strange because I can see the extension method on the repo but definitely not in my dll (checked with ILSpy).
The project file looks like this:
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.0-preview1-final" />
    <PackageReference Include="Microsoft.AspNetCore.Hosting" Version="2.1.0-preview1-final" />
    <PackageReference Include="Microsoft.AspNetCore.Server.IISIntegration" Version="2.1.0-preview1-final" />
  </ItemGroup>

Any idea of what am I missing?

@ilmax Do you test with IIS or IISExpress/VS? For IIS, could you please check whether aspnetcorerh.dll exists under %windir%/system32/inetsrv folder?

@pan-wang I'm not able to make the code compile because the method context.GetIISServerVariable is not available

@ilmax sorry, I just realized GetIISServerVariable wasn't added until preview2 https://github.com/aspnet/IISIntegration/pull/562

Try checking the current name of the running process: https://stackoverflow.com/questions/616584/how-do-i-get-the-name-of-the-current-executable-in-c
If it is w3wp or iisexpress, you are running inprocess.

ok, will re-try to run the benchmark tomorrow. One last question: do the dotnet.exe process should be up & running when hostingModel is in-process?

dotnet.exe process should be up & running when hostingModel is in-process?
No, it shouldn't be present.

Thanks, so the numbers make sense because when I was measuring perf with hostingmodel in-process, dotnet.exe was running, this means it wasn't running in-process and explains why I got almost same results.

@ilmax Do you test with IIS or IISExpress/VS? For IIS, could you please check whether aspnetcorerh.dll exists under %windir%/system32/inetsrv folder?

@pan-wang  No, looks like it's not here! I've just have aspnetcore.dll

Ok, sorted it out, it was an install issue. I've updated the gist with real numbers and looks like the inprocess version on my machine is 342% faster on my machine

That's much more expected. I think our tests were running on beefier hardware. IIRC we saw ~30k req/sec for out of process, and 135k req/sec for in proc.

Great! Thank you guys for your help!

Great! Thank you guys for your help!


Recording audio from user variable naming

What's changed, or what was fixed?

Fixed incorrect variable naming;
Updated deprecated variable initialization in code snippets

Fixes: #8332
Target Live Date: YYYY-MM-DD

[ ] This has been reviewed and approved by (NAME)
[ ] I have run npm test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

CC: @petele

@petele could you please give me permission to close issues? I have found many issues that have been fixed but are still open. If I was able to close them it would be easier for people to track what has been done.


coursier: 1.0.0 -> 1.0.1

Motivation for this change
minor update.
There is 1.0.2 already, but it does not work for me (fails with Exception in thread "main" java.lang.BootstrapMethodError: call site initialization exception)

I think the 1.0.2 issue has been recognized:  coursier/coursier@2cb42444cdbd6ad2a50f963378ff27259a4fb1a7


no manifest of the corresponding platform

What happen?
拉取sealer-apps相关的镜像失败，目前拉取redis，mysql，prometheus-stack都失败了，也尝试先sealer login到 registry.cn-qingdao.aliyuncs.com，错误没变。
Relevant log output?
sealer pull registry.cn-qingdao.aliyuncs.com/sealer-apps/prometheus-stack:v2.28.1
Start to Pull Image registry.cn-qingdao.aliyuncs.com/sealer-apps/prometheus-stack:v2.28.1
Error: get digest error: get digest from manifest list error: no manifest of the corresponding platform
Usage:
  sealer pull [flags]

Examples:
sealer pull registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8

Flags:
  -h, --help              help for pull
      --platform string   set cloud image platform

Global Flags:
      --config string   config file (default is $HOME/.sealer.json)
  -d, --debug           turn on debug mode
      --hide-path       hide the log path
      --hide-time       hide the log time

get digest error: get digest from manifest list error: no manifest of the corresponding platform

What you expected to happen?
拉取成功。
How to reproduce it (as minimally and precisely as possible)?
sealer pull registry.cn-qingdao.aliyuncs.com/sealer-apps/prometheus-stack:v2.28.1

Anything else we need to know?
No response
What is the version of Sealer you using?
{"gitVersion":"v0.8.5","gitCommit":"f9c3d99","buildDate":"2022-04-28 14:16:58","goVersion":"go1.16.15","compiler":"gc","platform":"linux/amd64"}
What is your OS environment?
NAME="CentOS Linux" VERSION="8 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Linux 8 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/"  CENTOS_MANTISBT_PROJECT="CentOS-8" CENTOS_MANTISBT_PROJECT_VERSION="8" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="8"
What is the Kernel version?
Linux VM-12-9-centos 4.18.0-348.7.1.el8_5.x86_64 #1 SMP Wed Dec 22 13:25:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Other environment you want to tell us?

Cloud provider or hardware configuration:
Install tools:
Others:

@djwangyi , sealer official cloud image have not been updated since 0.6.1 , We recommend rebuilding one based on the corresponding kubefile using the latest sealer version.


Configure Cargo.toml

I've changed the README file a bit.

Merging to see how it looks on the homepage.


我觉得这篇文章特别好

感谢作者，还开源了。
首先这篇文章解决了两个主要问题：

ViT 如何用到大分辨率上，这个问题不解决，不管多强的 LLM 估计都够呛
LLM 如何进行和视觉模型联合从而发挥两者的优势

相比于现阶段大家都一股脑的多模态拉成序列丢到 LLM 中进行自回归来说，本文做法明显是更可取的(这里不是说无脑 MLLM 就一定不行，只是说现阶段还存在很多问题)
LLM 天生就适合做识别任务，这算是他的强项，但是在没有提供高分辨率情况下区域理解或者提取啥的可能就不是他的强项了，此时就需要互补。 在现实应用中有不少人会对 CV 的识别结果再次经过 MLLM 进行概念纠正，也是这个思路，不过本文做成了一个端到端方案。
本方案相比于目前主流的开放词汇检测OVD 来说，我觉得是一个非常好的思路，至少在思路上是秒杀 OVD 的，因为 OVD 要构建词汇表，这注定应用范围很有限，但是也有一定应用场景，因为本文算法即可以做 OVD 也可以做没有词汇表的概念识别，我觉得这个思路是我最喜欢的。
至于性能上好像没有和 OVD 拉开差距，原因可能有几点：

是否有更好的 ViT 应用于高分辨率方案，目前的做法只是引入一个全局位置编码，是否是足够的呢？
LLM 性能限制，目前的 LLM 是固定的，是否能适应新的序列向量输入呢？但是全部打开肯定也是不合理的，因为训练的概念太少了，还不足以训练 LLM
训练数据的概念太少了，只有几个公开的数据集，所覆盖的概念太少了。对于这种训练任务，应该可以采用大量模拟数据，重点是要尽可能覆盖更多的视觉概念，最好是短语，而不是一个一个单词。
评测不够充足，这个算法的最大价值是识别 anything，如果只是在 coco 等特定数据集上进行测试其实有点不公平，感觉可以主打 zero-shot，特别是在评测上引入 zero-shot，这样可以更全面的评测这个模型

我觉得第三点和第四点最重要，特别是现在大模型大数据时代来说，在大数据加持下模型结构本身的性能差异应该不大。
当然目前方案对于每一个 mask 都要运行一遍 LLM，推理成本是蛮高的。
以上只是我个人的拙见，目前代码还没有细看，等有了更多的体会再来更新。也欢迎大家在这里交流！！！
再次感谢作者

Thanks a lot for you highly acknowledgment to our work and sharing your thoughts!
Regarding your questions/comments:

We adopt a simple strategy to adapt the CLIP-ViT to high-resolution image in a sliding-windows manner, with a global positional embedding to compensate the missing location information. This is an efficient and effective solution, especially considering that the CLIP-ViT is frozen . I believe that could be better solutions especially if we may train/fine-tune the CLIP-ViT at high-resolution, which however, typically requires large-scale dataset and computations.

Similar to 1, Fine-tuning/LORA fine-tuning LLM could require more data or computations, while this project aims at a preliminary  exploration in the open-ended visual recognition. But they are expected to give a performance boost.

3 and 4. Yes we also find that existing datasets are kind of limited, though we have adopted most existing segmentation datasets especially with large vocabularies to ensure the diversity in the training targets. Besides, we have tried our best to evaluate the model in our own way (the reported ACC and NIV) or well-established benchmarks (closed-vocab and open-vocab). We also considered using text similarity or CLIP score as an open-ended measurement yet found text alone is not reliable without image context and CLIP score is not distinguishable. A better benchmark designed for the open-ended recognition purpose is definitely much more helpful.

We explored to predict multiple mask in a single forwarding process in the early stage of this project. As a result, we found the model suffers from predicting in order for multiple masks, and tend to repeat when there any too many masks (potentially due to that the LLM is frozen and thus easier to repeat). Therefore we adopt single mask manner at the final design. Actually it may not be as slow as expected, as the image feature can be cached and shared (already implemented in our code-base), and the LLM part also has a similar computational costs considering that the sequence length of predicting all masks together or one-by-one are similar (but this may require we apply kv cache to the instructions as well, which is not implemented yet). So the real not avoidable costs comes from the multiple forwarding of the MaskQFormer, which may not be that larger compared to other component. But still, we totally agree that the inference speed can be further improved no matter though design level or implementation level.

Thanks again for your comments, and please let us know if you have any questions :)

Thank you very much for your patient response. I think you did a great job. It would be even better to add a zero-shot evaluation, and the evaluation should include category names and REC phrases to highlight the strengths of LLM and the algorithm's generalization. The NIV metric in the paper does indeed have some reference value.


SQL error during installation

Hi!
I try to intsall athe package to my laravel page but got the next erro during the installation:

> Migrating: 2019_09_15_000010_create_tenants_table
>
>    Illuminate\Database\QueryException
>
>   SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'json null) default character set utf8 collate 'utf8_unicode_ci'' at line 1 (SQL: create table `tenants` (`id` varchar(191) not null, `created_at` timestamp null, `updated_at` timestamp null, `data` json null) default character set utf8 collate 'utf8_unicode_ci')
>
>   at E:\ebrepo\Ebnyilvantarto\vendor\laravel\framework\src\Illuminate\Database\Connection.php:678
>     674▕         // If an exception occurs when attempting to run a query, we'll format the error
>     675▕         // message to include the bindings with SQL, which will make this exception a
>     676▕         // lot more helpful to the developer instead of just the database's errors.
>     677▕         catch (Exception $e) {
>   ➜ 678▕             throw new QueryException(
>     679▕                 $query, $this->prepareBindings($bindings), $e
>     680▕             );
>     681▕         }
>     682▕
>
>   1   E:\ebrepo\Ebnyilvantarto\vendor\doctrine\dbal\lib\Doctrine\DBAL\Driver\PDO\Exception.php:18
>       Doctrine\DBAL\Driver\PDO\Exception::("SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'json null) default character set utf8 collate 'utf8_unicode_ci'' at line 1")
>
>   2   E:\ebrepo\Ebnyilvantarto\vendor\doctrine\dbal\lib\Doctrine\DBAL\Driver\PDOConnection.php:83
>       Doctrine\DBAL\Driver\PDO\Exception::new(Object(PDOException))
>

My configuration is:
        "php": "^7.3|^8.0",
        "coreui/coreui": "3.2.0",
        "fideloper/proxy": "^4.4",
        "fruitcake/laravel-cors": "^2.0",
        "guzzlehttp/guzzle": "^7.0.1",
        "jeroennoten/laravel-adminlte": "^3.5",
        "laravel/framework": "^8.12",
        "laravel/jetstream": "^1.6",
        "laravel/sanctum": "^2.6",
        "laravel/tinker": "^2.5",
        "laravel/ui": "^3.1",
        "livewire/livewire": "^2.0",
        "stancl/tenancy": "^3.4"

Thank you in advance!
Virag

Actual behavior
..
Expected behavior
..

Information

hyn/multi-tenant version:
laravel version:
database driver and version:
webserver software and version:
php version:

tenancy.php config

webserver.php config

Error log

You didn't post your database driver and version details.
Seems like perhaps you're using a very old MySQL version, or other database engine, that doesn't support JSON fields?

You didn't post your database driver and version details.
Seems like perhaps you're using a very old MySQL version, or other database engine, that doesn't support JSON fields?

Hi!
I changed the tenant migration file, and the default charset null solved the problem

class CreateTenantsTable extends Migration

public function up(): void
{
    Schema::create('tenants', function (Blueprint $table) {
        $table->string('id')->primary();

        // your custom columns may go here

        $table->timestamps();
        $table->json('data')->charset(null)->nullable();
    });
}

/**
 * Reverse the migrations.
 *
 * @return void
 */
public function down(): void
{
    Schema::dropIfExists('tenants');
}

}

Hi!
I changed the tenant migration file, and the default charset null solved the problem

class CreateTenantsTable extends Migration

public function up(): void
{
    Schema::create('tenants', function (Blueprint $table) {
        $table->string('id')->primary();

        // your custom columns may go here

        $table->timestamps();
        $table->json('data')->charset(null)->nullable();
    });
}

/**
 * Reverse the migrations.
 *
 * @return void
 */
public function down(): void
{
    Schema::dropIfExists('tenants');
}

}

That feels like a "bandage" instead of a proper "fix".  Be careful about using that in production.

That feels like a "bandage" instead of a proper "fix".  Be careful about using that in production.

Ok, tank you, I will investigate it later.

Ok, tank you, I will investigate it later.

Tip: If you feel this issue is resolved, please click "Close" below to make things easier for the github project owner!

Tip: If you feel this issue is resolved, please click "Close" below to make things easier for the github project owner!


Recommended patterns for menus and dialogs

Copied from https://github.com/react-navigation/react-navigation/issues/1315
The preferred pattern for handling dialogs and menus don't seem to have been discussed yet.
Menus that open from a  menu button are a fairly common pattern.
I can see 2 possible ways they might be implemented:

As part of params: Menu is part of a scene's children, headerRight uses setParams to set a param indicating the menu is open and that param is passed to whatever prop on the menu indicates it is open. Closing the menu is another setParams. One would have to either use <Modal /> or manually register a BackAndroid (now BackHandler) to handle the Android "back button closes menu instead of navigating backwards" pattern.
As a navigator: Menus are implemented as a part of a MenuNavigator (or maybe a ModalNavigator), the navigator is used in place of the screen for a route in your {Stack,Drawer,Tab}Navigator and accepts one route that is the normal screen and other routes are menus. Menus are opened using navigator.navigate('MenuName') and exited using navigator.goBack().

Dialogs are another modal type to consider (given the drawer is already considered a navigator).
Drawers make less sense as part of props but there are still 2-3 patterns I can think of for them:

A DialogNavigator: Just like the MenuNavigator/ModalNavigator I described a DialogNavigator would be used in place of a normal screen and allow navigator.navigate to open a specific dialog from the associated screen.
A top-level DialogNavigator: Instead of taking place of a deeper screen, the DialogNavigator would be top-level like the DrawerNavigator is. This would allow it to easily sit on top of everything else and put dialogs on top. Dialogs would become global, which could be a pro or a con depending on the app.
As part of StackNavigator: Instead of a whole separate navigator StackNavigator would be modified to support modals (routes that can have no headers of their own, are drawn transparently over top of the other screens, and have a separate transition type). From the nesting and navigation perspectives this is a little simpler. There is no extra nesting of navigators that could make navigation.navigate calls more complex in any scenario, opening a dialog by navigating to it is simple, and closing a dialog via navigator.goBack() is built-in. Also this would already handle full-screen dialogs pretty well and handle the tablet+mobile environment where a route may be a full-screen dialog with a header in the stack route on mobile but be a dialog on a tablet without a header.

Full-screen dialogs themselves are probably a separate more precise discussion.

As I'm developing an app more and more using React Navigation I'm strongly leaning towards modals (menus and dialogs) being something StackNavigator supports.

Handling menus and dialogs as part of params is insufficient. There are a variety of reasons one may want these separate, shared, or otherwise not polluting routes. And these grow as apps get bigger.
Because of my need for a Drawer, screens above the drawer, and a modal StackNavigator for full-screen dialogs I already have a terribly deep and convoluted route tree. And I can say for certain that having separate navigators to handle different types of routes just makes things more complicated than they need to be.

So rather than dialogs and modals being a separate navigator I think it's better for StackNavigator to be able to handle the key points of dialogs/menus/modals/overlays:

Routes that show the previous route in the stack below them.
Overlay routes that don't affect the header, and.
Routes that have a different transition style.

I really think we should be careful about adding a million features to StackNavigator.. its already getting out of hand. I have more details on my thoughts here:
https://github.com/react-navigation/rfcs/issues/15


zm option

@doutriaux1 we currently have option in parameter files to save interpolated model clims as netcdf files.   We should add a companion option to save model 12month zonal means to netcdf files (pre-interpolation).    These could be in a single file as (12, latitude).

@jservonnat awesome we can now assign work to you! Awesome! Don't worry about this one though, I was just testing.

@doutriaux1  In addition to having option in paramater file to save zonal means, it would be good also to save  area average 12 month time series for each region metrics are calculated for

@gleckler1 and I just had a chat about this, it's better to keep it as a separate process.


Integrate StructureMap  extraction support

Update patient-registraiton.json to use StructureMap
Update datacapture dependency to 0.2.6-alpha-02
Enable syncing of StructureMap
Update extraction to save bundle of Resources
Refactor business logic to QuestionnaireViewModel

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #307
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Release | Other)
Checklist

[x] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

@ekigamba is this a duplicate of  PR 412 ? If so should it be closed?


Fine-tuning Colab Guide

Hello, I’m super excited about this model. Do you have a step-by-step tutorial on how to fine-tune this model on my custom input-output audio pairs?

Appreciate your interest! Let me create a colab example, will share it here

Sure! Ping me when you are done!

Not exactly colab notebook, but this is code https://gist.github.com/skirdey/4c90202ee4aa753a0184f4366953b60a that was used for training, you can copy paste and with minor tweaks it should work.

Oh, my! Thank you so much.
Could you please explain how to use it and what my dataset should look like? Also, can I begin with your model instead of starting from scratch?
And, is 1xA100 is sufficient enough, and how long would it take to train?

1xA100 should be more than enough! And for the code it goes like this
train.py
train_example.py (you run it as accelerate launch train_example.py)
forward function goes into model next to the sample function
if you have these files and try accelerate launch, it should start fine tuning. For your own dataset you can provide just clean audio and use built in degradations, or come up with your own degradations.


Form.Input not honouring autoCapitalize prop

Steps

Use Form.Input component with autoCapitalize="none".

Expected Result
It should be render an input element with the autocapitalize="none" attribute.
Actual Result
It omits the autocapitalize attribute.
Version
0.64.8
Testcase
Fork this to show the issue: http://codepen.io/anon/pen/wgRxMZ

The fix here is extremely simple, the prop just needs to be added to whitelist of HTML input props:
https://github.com/Semantic-Org/Semantic-UI-React/blob/master/src/elements/Input/Input.js#L20
Great way to get a first contribution :)