Swift compiler errors

I get these strange errors after installing the package.

Does anyone know what the issue is? I could install it perfectly on another newer project.
Kind regards,
Frank

This is the first time I'm encountering this error 😅
Could you post what RN version you're using, and your Xcode version? I'll try making a fresh project to reproduce.
This a long shot, but maybe it's related to 1.1.2 Xcode Build Error (Undefined symbol)?
In the meantime, I'm gonna do some debugging... 😔

This is the first time I'm encountering this error 😅
Could you post what RN version you're using, and your Xcode version? I'll try making a fresh project to reproduce.
This a long shot, but maybe it's related to 1.1.2 Xcode Build Error (Undefined symbol)?
In the meantime, I'm gonna do some debugging... 😔

I'm on:
react-native-cli: 2.0.1
react-native: 0.61.5
and XCode 11.5
Clean build + Cleared derivedData.
Maybe it has something to do with that: https://stackoverflow.com/questions/40040570/swift-compiler-error-on-pods
I will try out tomorrow thank you for your help.

I'm on:
react-native-cli: 2.0.1
react-native: 0.61.5
and XCode 11.5
Clean build + Cleared derivedData.
Maybe it has something to do with that: https://stackoverflow.com/questions/40040570/swift-compiler-error-on-pods
I will try out tomorrow thank you for your help.

Forgot to post before I went to sleep 😴, but I tried installing the library on a fresh RN app:

Created new RN project (the latest ver. is: 0.63.4)
Tried to run the app but got: Undefined symbol: (extension in UIKit)

Followed 1.1.2 Xcode Build Error (Undefined symbol) , added an empty swift file, did a clean build, and ran the app

I couldn't reproduce the error you got 😔

I've just read your reply, and I think that it might have something to do with RN 0.61.5 + Xcode 11.5?
My current problem is that I only have 4gb's of space left, so I can't download Xcode 11 right now 😭
But looking at the error again, it seems like Xcode is can't find UIMenu in UIKit (so it's the same error as "undefined symbol" but with a different message...)
So it could have something to do with Library Search Paths build setting again, but I am not sure. Have you tried creating a fresh RN project and following 1.1.2 Xcode Build Error (Undefined symbol) ?
For now I'm going to try installing the library on react-native: 0.61.5 😅

Forgot to post before I went to sleep 😴, but I tried installing the library on a fresh RN app:

Created new RN project (the latest ver. is: 0.63.4)
Tried to run the app but got: Undefined symbol: (extension in UIKit)

Followed 1.1.2 Xcode Build Error (Undefined symbol) , added an empty swift file, did a clean build, and ran the app

I couldn't reproduce the error you got 😔

I've just read your reply, and I think that it might have something to do with RN 0.61.5 + Xcode 11.5?
My current problem is that I only have 4gb's of space left, so I can't download Xcode 11 right now 😭
But looking at the error again, it seems like Xcode is can't find UIMenu in UIKit (so it's the same error as "undefined symbol" but with a different message...)
So it could have something to do with Library Search Paths build setting again, but I am not sure. Have you tried creating a fresh RN project and following 1.1.2 Xcode Build Error (Undefined symbol) ?
For now I'm going to try installing the library on react-native: 0.61.5 😅

Hello, forgot to post this before I fell asleep last night 😴
I created a fresh RN project (the latest ver. is 0.63.4) to try and reproduce the error:

Ran: npx react-native init contextMenuTest6v0634
Made sure that it builds/runs
Installed the library: yarn add react-native-ios-context-menu and cd ios && pod install
Tried to build the app and encountered this error:

Followed 1.1.2 Xcode Build Error (Undefined symbol), added an empty swift file, did a clean build, and run the app

Couldn't reproduce the error 😔

Gonna try again with RN 0.61.5 later...

Hello, forgot to post this before I fell asleep last night 😴
I created a fresh RN project (the latest ver. is 0.63.4) to try and reproduce the error:

Ran: npx react-native init contextMenuTest6v0634
Made sure that it builds/runs
Installed the library: yarn add react-native-ios-context-menu and cd ios && pod install
Tried to build the app and encountered this error:

Followed 1.1.2 Xcode Build Error (Undefined symbol), added an empty swift file, did a clean build, and run the app

Couldn't reproduce the error 😔

Gonna try again with RN 0.61.5 later...

So maybe the problem is with Xcode 11.5 and  RN 0.63.4 ? I don't have enough space to install another version of Xcode haha, so I'm going to use github actions:

Ran: npx react-native init contextMenuTest7v0615  --version 0.61.5

Made sure that it runs/builds, and then published the repo to github

Made a github action that builds the app using Xcode 11.5

Did a test run and triggered the github action to make sure it works

Installed react-native-ios-context-menu on the test project (commit link):

Installed the library: yarn add react-native-ios-context-menu
Bumped the test project's deployment target from iOS 9.0 -> iOS 10.0 to fix the pod error: [!] CocoaPods could not find compatible versions for pod "react-native-ios-context-menu": [...] but they required a higher minimum deployment.
Followed 1.1.1 Xcode Build Error (Swift) to fix the pod error: [!] Unable to determine Swift version for the following pods: "react-native-ios-context-menu" does not specify a Swift version and none of the targets ("contextMenuTest7v0615") integrating it have the "SWIFT_VERSION" attribute set. [...]
Followed 1.1.3 Cocoapods Static Libraries Error to fix pod error: The Swift pod "react-native-ios-context-menu" depends upon "React-Core", which does not define modules.  [...]
Ran pod install

Tried building the app locally on Xcode and encountered no errors so far:

Triggered the github build action to test if it still builds on Xcode 11.5

So maybe the problem is with Xcode 11.5 and  RN 0.63.4 ? I don't have enough space to install another version of Xcode haha, so I'm going to use github actions:

Ran: npx react-native init contextMenuTest7v0615  --version 0.61.5

Made sure that it runs/builds, and then published the repo to github

Made a github action that builds the app using Xcode 11.5

Did a test run and triggered the github action to make sure it works

Installed react-native-ios-context-menu on the test project (commit link):

Installed the library: yarn add react-native-ios-context-menu
Bumped the test project's deployment target from iOS 9.0 -> iOS 10.0 to fix the pod error: [!] CocoaPods could not find compatible versions for pod "react-native-ios-context-menu": [...] but they required a higher minimum deployment.
Followed 1.1.1 Xcode Build Error (Swift) to fix the pod error: [!] Unable to determine Swift version for the following pods: "react-native-ios-context-menu" does not specify a Swift version and none of the targets ("contextMenuTest7v0615") integrating it have the "SWIFT_VERSION" attribute set. [...]
Followed 1.1.3 Cocoapods Static Libraries Error to fix pod error: The Swift pod "react-native-ios-context-menu" depends upon "React-Core", which does not define modules.  [...]
Ran pod install

Tried building the app locally on Xcode and encountered no errors so far:

Triggered the github build action to test if it still builds on Xcode 11.5

I finally was able to reproduce your error 😅
The github action failed to build the project with the following error:

Link to full logs

The next step is to figure out what went wrong 😅

I finally was able to reproduce your error 😅
The github action failed to build the project with the following error:

Link to full logs

The next step is to figure out what went wrong 😅

I've found the solution, but you aren't going to like it 😔
(skip to the end if you don't want to see the explanation haha)

I finally was able to build the test app using Xcode 11.5 using this GH action (here's a link to the build output).
In the build errors, I have noticed that Xcode was complaining about the iOS-14 specific API's of UIMenu (so at the very least, Xcode was aware that UIKit.UIMenu exists, just not the iOS 14 version of it).
That's why there were only errors regarding RCTContextMenuButton because it was using the context menu API's for UIButton that were introduced in iOS 14.

It turns out that it was problem with the Xcode Swift toolchain. In the Build App w/ Swift 5.3 GH action, it's using the swift 5.3 toolchain.
Swift 5.3 is important because that's the version of swift that was released with iOS 14 (this is also the reason why the same app builds on Xcode 12, but fails to build on Xcode 11. Xcode 12 is using a newer version of swift).
In other words, certain framework features (such as UIKit.UIMenu) are tied to a the version of swift that Xcode is using (any mismatch causes the build to fail, presumably because the newer API's aren't declared in the headers).

So the steps to fix this are the same as before:

Ran: npx react-native init contextMenuTest7v0615  --version 0.61.5

Made sure that it runs/builds, and then published the repo to github

Made a github action that builds the app using Xcode 11.5

Did a test run and triggered the github action to make sure it works

Installed react-native-ios-context-menu on the test project (commit link):

Installed the library: yarn add react-native-ios-context-menu
Bumped the test project's deployment target from iOS 9.0 -> iOS 10.0 to fix the pod error: [!] CocoaPods could not find compatible versions for pod "react-native-ios-context-menu": [...] but they required a higher minimum deployment.
Followed 1.1.1 Xcode Build Error (Swift) to fix the pod error: [!] Unable to determine Swift version for the following pods: "react-native-ios-context-menu" does not specify a Swift version and none of the targets ("contextMenuTest7v0615") integrating it have the "SWIFT_VERSION" attribute set. [...]
Followed 1.1.3 Cocoapods Static Libraries Error to fix pod error: The Swift pod "react-native-ios-context-menu" depends upon "React-Core", which does not define modules.  [...]
Ran pod install

Tried building the app locally on Xcode and encountered no errors so far:

But if you are using Xcode 11, you have to change the swift version that Xcode is using to at least: Swift 5.3

Based on this article, it's quite a lengthy process...
You can either A: upgrade to Xcode 12, B: change your Xcode's toolchain that uses swift 5.3, or C: just use a different library (honestly, this is not worth all the hassle 😔)

I'm sorry I could't find a better solution, but this is something that is out of my abilities. The problem is with the version of Xcode you are using (and the fact that this library is using iOS 14 specific API's... ☹)

I'm going to take a nap haha hope you find a solution that you are happy with, best of luck! ✨

I've found the solution, but you aren't going to like it 😔
(skip to the end if you don't want to see the explanation haha)

I finally was able to build the test app using Xcode 11.5 using this GH action (here's a link to the build output).
In the build errors, I have noticed that Xcode was complaining about the iOS-14 specific API's of UIMenu (so at the very least, Xcode was aware that UIKit.UIMenu exists, just not the iOS 14 version of it).
That's why there were only errors regarding RCTContextMenuButton because it was using the context menu API's for UIButton that were introduced in iOS 14.

It turns out that it was problem with the Xcode Swift toolchain. In the Build App w/ Swift 5.3 GH action, it's using the swift 5.3 toolchain.
Swift 5.3 is important because that's the version of swift that was released with iOS 14 (this is also the reason why the same app builds on Xcode 12, but fails to build on Xcode 11. Xcode 12 is using a newer version of swift).
In other words, certain framework features (such as UIKit.UIMenu) are tied to a the version of swift that Xcode is using (any mismatch causes the build to fail, presumably because the newer API's aren't declared in the headers).

So the steps to fix this are the same as before:

Ran: npx react-native init contextMenuTest7v0615  --version 0.61.5

Made sure that it runs/builds, and then published the repo to github

Made a github action that builds the app using Xcode 11.5

Did a test run and triggered the github action to make sure it works

Installed react-native-ios-context-menu on the test project (commit link):

Installed the library: yarn add react-native-ios-context-menu
Bumped the test project's deployment target from iOS 9.0 -> iOS 10.0 to fix the pod error: [!] CocoaPods could not find compatible versions for pod "react-native-ios-context-menu": [...] but they required a higher minimum deployment.
Followed 1.1.1 Xcode Build Error (Swift) to fix the pod error: [!] Unable to determine Swift version for the following pods: "react-native-ios-context-menu" does not specify a Swift version and none of the targets ("contextMenuTest7v0615") integrating it have the "SWIFT_VERSION" attribute set. [...]
Followed 1.1.3 Cocoapods Static Libraries Error to fix pod error: The Swift pod "react-native-ios-context-menu" depends upon "React-Core", which does not define modules.  [...]
Ran pod install

Tried building the app locally on Xcode and encountered no errors so far:

But if you are using Xcode 11, you have to change the swift version that Xcode is using to at least: Swift 5.3

Based on this article, it's quite a lengthy process...
You can either A: upgrade to Xcode 12, B: change your Xcode's toolchain that uses swift 5.3, or C: just use a different library (honestly, this is not worth all the hassle 😔)

I'm sorry I could't find a better solution, but this is something that is out of my abilities. The problem is with the version of Xcode you are using (and the fact that this library is using iOS 14 specific API's... ☹)

I'm going to take a nap haha hope you find a solution that you are happy with, best of luck! ✨

Thank you for your awesome work so far 😀 Your solution is a bit confusing to me because on another project it works using the same XCode version. Maybe I can specify in my project which version of Swift to use? (maybe the project uses an older swift version because I have another pod in it which also uses swift)

Thank you for your awesome work so far 😀 Your solution is a bit confusing to me because on another project it works using the same XCode version. Maybe I can specify in my project which version of Swift to use? (maybe the project uses an older swift version because I have another pod in it which also uses swift)

I'm sorry, this library is a mess haha 😔 (I'll take a look at this later, and do some more tests)

At the mean time, what did you do, and what errors did you encounter? I don't mind if you just paste the entire error/logs + build settings haha (it'll help with debugging). I'll follow along step by step and I'll try to reproduce the errors 😅

This would be a lot easier it i could install Xcode 11 (but I only have 4GB's of space left 🤣)

I'm sorry, this library is a mess haha 😔 (I'll take a look at this later, and do some more tests)

At the mean time, what did you do, and what errors did you encounter? I don't mind if you just paste the entire error/logs + build settings haha (it'll help with debugging). I'll follow along step by step and I'll try to reproduce the errors 😅

This would be a lot easier it i could install Xcode 11 (but I only have 4GB's of space left 🤣)

Nooo this library is really good. I described what I did in the comment above, I have not logs :/
When was the last version that used Swift 5.0 instead of Swift 5.3? I need ContextButton :(

Nooo this library is really good. I described what I did in the comment above, I have not logs :/
When was the last version that used Swift 5.0 instead of Swift 5.3? I need ContextButton :(

Here's what I've found after some testing haha

For Xcode 11.5 it uses: Apple Swift version 5.2.4 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)
For Xcode 12.3 it uses: Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)

I'm a noob at Xcode but I can't figure how to make this work... I'm afraid that I'll end up breaking something if i mess with the build settings haha
It looks like the simplest solution is to just upgrade to Xcode 12.3. I didn't want to update, but I've been using it for a while and it's pretty good!

In the meantime, I'm going to try and set the podspec for this library to: s.swift_version = '5.3' and try to install it using Xcode 11.5

Here's what I've found after some testing haha

For Xcode 11.5 it uses: Apple Swift version 5.2.4 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)
For Xcode 12.3 it uses: Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)

I'm a noob at Xcode but I can't figure how to make this work... I'm afraid that I'll end up breaking something if i mess with the build settings haha
It looks like the simplest solution is to just upgrade to Xcode 12.3. I didn't want to update, but I've been using it for a while and it's pretty good!

In the meantime, I'm going to try and set the podspec for this library to: s.swift_version = '5.3' and try to install it using Xcode 11.5


Publish to hex.pm

Hi,
I was hoping you could publish this library to Hex. (https://hex.pm)
Thanks!

@aberman Thanks for your proposal. I will do it until this weekend.

@aberman You can find this in hex.pm link: https://hex.pm/packages/hashids_erlang
Because of hashids-elixir port, this library's name is 'hashids_erlang'.

Awesome!  Thank you!


Support presigned URL signature "UNSIGNED-PAYLOAD" and expose EncodeURI

As discussed in https://github.com/aws/aws-iot-device-sdk-embedded-C/issues/1887 I have made changes to an existing demo http_demo_s3_download to generate a presigned URL instead of directly downloading the file.
I'm planning, if the changes to the submodules are accepted, to then generate a new demo called http_demo_s3_presigned_url or something like that.
You can see/test my work at https://github.com/giuspen/aws-iot-device-sdk-embedded-C/tree/GP_http_demo_s3_download_test_signature (only generate presigned URL) or https://github.com/giuspen/aws-iot-device-sdk-embedded-C/tree/GP_http_demo_s3_download_test_signature2 (download and also generate presigned URL)
Exact same requirements of original demo http_demo_s3_download
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

Hello @giuspen, Thank you for raising the PR! We will be looking further into this issue as soon as we can, thank you for your patience!

/bot run formatting

I see that there are unit tests errors but that doesn't seem to be related to my change.
Can anybody help me reviewing this?

@giuspen, Thanks for the PR. We will look into the unit test failures and update.

I wanted to run the unit tests myself and possibly add one unit test myself to not waste your time and patience but the instructions in https://github.com/aws/SigV4-for-AWS-IoT-embedded-sdk/blob/main/README.md#building-unit-tests don't work for me, I get instead
penoneg@cinnamon:~/git/SigV4-for-AWS-IoT-embedded-sdk/build$ ctest
Test project /home/penoneg/git/SigV4-for-AWS-IoT-embedded-sdk/build
    Start 1: sigv4_utest
1/1 Test #1: sigv4_utest ......................Child aborted***Exception:   0.00 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.01 sec

The following tests FAILED:
	  1 - sigv4_utest (Child aborted)
Errors while running CTest

@giuspen,
Can you try the following script to build and run the unit tests:
cmake -S test -B build/ -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_UNIT_TESTS=ON -DCMAKE_C_FLAGS='--coverage -Wall -Wextra -DNDEBUG -DLOGGING_LEVEL_DEBUG=1'
make -C build/ all
cd build/ && ctest -E system --output-on-failure --verbose

Thanks @tony-josi-aws I could run the unit tests with your command, I did check that my implementation didn't fail existing unit tests and I also added a unit test to protect the presigned URL

@giuspen, it seems that your changes have increased the memory consumption of the library a bit. It is causing the memory-statistics check to fail. Would you mind updating the size_table.md like so:
  --- docs/doxygen/include/size_table.md	2023-11-22 20:54:32.891598188 +0000
  +++ size_table.html	2023-11-22 20:54:59.319864025 +0000
  @@ -10,5 +10,5 @@

           sigv4.c
  -        5.2K
  +        5.3K
           4.4K

  @@ -20,5 +20,5 @@

           Total estimates
  -        5.6K
  +        5.7K
           4.7K

I shall look at the failing memory safety proofs in the meanwhile.
thanks,
aniruddha

sure thanks for reviewing @AniruddhaKanhere

@giuspen, thanks for updating the code.
I found the issue with memory safety proofs. We are using mocks to simplify and test implementation of functions. To that end, we have to define the stub of the function we intend to mock out.
The mock of generateCanonicalQuery here is missing the newly added const bool doubleEncodeEqualsInParmsValues, parameter. Can you add it please? You just need to add the parameter to that definition - it will not be used at all - and that is perfectly fine!
I think that should fix the failing check :)
Thanks again,
Aniruddha

Thanks @AniruddhaKanhere , I noticed that in the same file that you pointed out there is also the stub for encodeURI() but that was renamed in my PR as it is now no longer private but exposed to the API. I wonder if I should remove that stub as no longer needed or rename it

Thanks @AniruddhaKanhere , I noticed that in the same file that you pointed out there is also the stub for encodeURI() but that was renamed in my PR as it is now no longer private but exposed to the API. I wonder if I should remove that stub as no longer needed or rename it

Ah! Yes, I overlooked that. Thank you for catching it.
I think we should also rename the stub for encodeURI() to the new API that you have created.

I suspect the stubs are just for private stuff while for the public API there's no need. I have removed completely the encodeURI() for now, would it be possible to try and run the CI and see how it behaves?

If you are sure though I will restore and rename... let me know

Those stubs work in a different way. I think we should rename them.
Those stubs are there so that CBMC does not need to compute everything all at once. Because, if CBMC were to try and prove all the functions in the call graph to be memory safe, it would take exponentially long time and quite a bit more RAM. These stubs reduce the computation that the CBMC SAT solver has to do.
Will keep an eye on the result though :)
Thank you for making that change.

Thanks @AniruddhaKanhere I'm going to restore and rename the encodeURI() stub

Is there any chance that my work will be merged in?
This will allow me to proceed submitting a new demo for the generation of a presigned URL to download a file from an S3 bucket.

Hi @giuspen, could you help in fixing the failing CBMC proofs?

Hi Tony, 100%, only thing it is not clear that CI error but maybe I can restore the private function name that I suspect the check is looking for and have the public function just call the private one. I'll give that a try this evening Europe time and push so we'll see if that makes the CI happy

/bot run formatting

Approving to trigger proof_ci.

I'm puzzled but I will try to run the test locally and possibly extract more info, the log of the error is not helping :(

Hi @giuspen,
Thanks for updating the PR. Could you please apply this attached patch and update the PR again?
It should fix the failing CBMC proof.
0001-Fix-CBMC-proof-for-SigV4_GenerateHTTPAuthorization.patch

Hi @tony-josi-aws thanks for the help, I applied your patch


English dictionary stem words are different from the example

My problem started when I tried replicating the example in the readme:
class BoringTweet < ActiveRecord::Base
  include PgSearch::Model
  pg_search_scope :kinda_matching,
                  against: :text,
                  using: {
                    tsearch: {dictionary: "english"}
                  }
  pg_search_scope :literally_matching,
                  against: :text,
                  using: {
                    tsearch: {dictionary: "simple"}
                  }
end

sleepy = BoringTweet.create! text: "I snoozed my alarm for fourteen hours today. I bet I can beat that tomorrow! #sleepy"
sleeping = BoringTweet.create! text: "You know what I like? Sleeping. That's what. #enjoyment"
sleeper = BoringTweet.create! text: "Have you seen Woody Allen's movie entitled Sleeper? Me neither. #boycott"

BoringTweet.kinda_matching("sleeping") # => [sleepy, sleeping, sleeper]
BoringTweet.literally_matching("sleeping") # => [sleeping]

When I tried this doing a 'kinda_matching' search for 'sleeping' would only return the 'sleeping' record. Looking into it, it looks like the stems for sleepy, sleeping and sleeper are different:
select to_tsvector('sleepy');
=> 'sleepi':1

select to_tsvector('sleeping');
=> 'sleep':1

select to_tsvector('sleeper');
=>  'sleeper':1

Are there different versions of the 'english' catalog perhaps?
I'm running PostgreSQL 14.4 on aarch64-apple-darwin20.6.0, compiled by Apple clang version 12.0.5 (clang-1<IP_ADDRESS>), 64-bit

Interesting! I wrote these examples over a decade ago and haven't thought to keep checking them. I'm going to see what I can find out.

Indeed, I also get the same results. I'll update the examples!

Fixed!

Thanks! Happy it wasn't just me!


Invalid Syntax

How can I fix this error?

install requirements in the README, use brain pls also shown in the youtube video


Multi-Model Release

This PR integrates code which updates the Community Notes ranking algorithm to support multiple models.  The update includes the Expansion and Coverage models which were launched as part of the multi-model update.

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


Could not find com.raizlabs.android.DBFlow:dbflow-processor:3.0.0-beta1

I have included
dependencies {
    classpath 'com.android.tools.build:gradle:1.5.0'
    classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'

    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

in top level gradle and
apply plugin: 'com.neenbedankt.android-apt'

in app level and
 apt 'com.raizlabs.android.DBFlow:dbflow-processor:3.0.0-beta1'
compile "com.raizlabs.android.DBFlow:dbflow-core:3.0.0-beta1"
compile "com.raizlabs.android.DBFlow:dbflow:3.0.0-beta1"

in dependencies.

Fixed in this PR : https://github.com/Raizlabs/DBFlow/pull/508

@mirecalu I have try this but not work.

merged in #508


support setting image pull policy

support setting image pull policy with spec.imagePullPolicy, more info: https://kubernetes.io/docs/concepts/containers/images/#updating-images
default pull policy is PullIfNotPresent
yaml example:
apiVersion: doris.selectdb.com/v1
kind: DorisCluster
...
spec:
  feSpec:
  image: iregistry.baidu-int.com/doris-rdw/rdw_doris_fe:v1.0.5
  imagePullPolicy: Always
..

Hi, I am sorry for not approving your PR. imagePullPolicy set to 'IfNotPresent' is the best for Doris, because Doris's image is big, if always pulling from the remote repository will take much times than from local when restarted.


Performance bottleneck caused by getComputedTextLength

If there are a lot of matches in a sunburst, getComputedTextLength gets called a lot. Each call forces a relayout. But this is not necesairy because the pie pieces are too small to even see the name.

Not display the name on small pieces could be a solution here
Original issue by @beardhatcode on Wed Apr 11 2018 at 14:35.
Closed by @beardhatcode on Wed Apr 11 2018 at 15:27.

wrong repo
Original comment by @beardhatcode on Wed Apr 11 2018 at 15:27.


Compiling warning

Hi, thanks for this excellent project, it helps me much.
But when I use it to gen a JWT-token, there is a warning,  this private member is unused, could you fix this warning? Thanks.
3rdparty/jwt-cpp/include/jwt-cpp/jwt.h:1177:20: warning: private field 'md' is not used [-Wunused-private-field]
                        const EVP_MD* (*md)();
                                        ^

It's fixed in master  😄
#136

Thanks.


Attach Swift binaries to GitHub releases.

This PR adds a new release script for Swift that attaches the XCFramework to GitHub releases instead of committing to keep the dependency size down. There's a new repo here for us to start fresh.
Still a WIP, need to figure out the following

[ ] Push rights from the workflow on this repo to the package repo.
[ ] API rights from the workflow on this repo to create the release on the package repo.
[ ] Update the release workflow to cd && swift run release --version x.y.z.
[ ] Find out if running release_ios.sh without a TAG value is needed anywhere?

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

Project coverage is 89.64%. Comparing base (a1942c7) to head (9b9544f).

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #954      +/-   ##
============================================
+ Coverage     86.23%   89.64%   +3.41%
============================================
  Files           168       86      -82
  Lines         19293    15499    -3794
  Branches       1077        0    -1077
============================================
- Hits          16637    13894    -2743
+ Misses         2329     1605     -724
+ Partials        327        0     -327

Flag
Coverage Δ

uitests
?

uitests-android
?

unittests
89.64% <ø> (+4.08%)
:arrow_up:

unittests-android
?

unittests-ios
?

unittests-rust
89.64% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Permission Error

host = Host() if not host.exists("hostname"):     host.add("hostname", "port")
File ### "C:\Users\nishansa\lib\site-packages\hostsman.py", line 131, in _keep_history
copyfile(self.hostFile, backup_file)
File "C:\Users\nishansa\AppData\Local\Programs\Python\Python38\lib\shutil.py", line 261, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
PermissionError: [Errno 13] Permission denied: 'c:\windows\system32\drivers\etc\hosts-2022.07.21_16-07-01-266977'

your current user may not have the permission to add files to the folder in system32, try to run the command in administrator mode


normatrix don't like too long header

Describe the bug
detect an error when header have more than one line of description.

To Reproduce
have a header with a two line description. or a header that is 7 line len.
Expected behavior
don't detect an error
Desktop (please complete the following information):

OS: linux mint

Additional context
vs code

yes, normatrix check if the string is very equal to the header with 5 line
I don't know if it can be a coding style error to have an header with 2 line or more comments

Fix with latest push


Update to support latest subscription-transport-ws (0.8.2)

Any updates on this?

@Urigo ??

@Urigo can we please get this merged ? Thanks in advance

@DxCx you might want to update the dependencies on graphql and subscription-transport-ws before this get merged.

im not sure when uri will merge, versions might progress even further..

Ya I hear you, I was kinda hopeful that somehow @Urigo would resurface this time around. He tweeted last week so at least he seems well.

@stubailo is there anything you can do from an org perspective to reach out to @Urigo and resolve the situation plz ?

well, its here for almost a year, not gonna happen i guess..


Merit List

Panellists grade candidates and display the results at both the shortlisting and selection stages. These results are currently stored off platform on a spreadsheet.
We need a single source of truth when it comes to candidate grades and a way to reduce errors during data entry and processing.
We need to explore what is technically possible on the platform and whether a simple upload of the existing spreadsheet onto the platform will be suitable, or whether it is possible to have panel members enter grades directly onto the platform via a newly created UI workflow.
We have merit list at different stages of the exercise;
[ ]Merit list at sift day- shortlisting
[ ]Merit list at selection days
[ ] Ability to create many panels e.g panel 1,2 , 3
[ ] daily score sheet Template
[ ] Merit list Template
[ ] Report Template
[ ] Moderation control Template
[ ] Moderate 10% to 12% of candidates per exercises.
[ ] Large exercise with more panellist moderate 30% of candidates.
Example form two panels.
[ ] Daily score sheet for panellist - consist of Panel Chair, Judicial member and independent member used the daily score sheet.
[ ] The panel chair is responsible to update the daily score sheet.
[ ] Panel chair write the report at the end of sift.
[ ] Panel chair should only access their candidates details
[ ] Panel chair to have moderation Control Template for moderation day
[ ] Panel chair to update the moderation control template
[ ] Create access for Assign commissioner
[ ] Panellist to only have access to their daily score sheet.
[ ] Panellist cannot access each other daily score sheet
[ ] Panellist should be generated a link to access only the candidates that they will be sifting/shortlisting on the day.
[ ] Ability to lock the daily score sheet at the end of the day.
[ ] Panellist cannot update the daily score sheet once scores have been entered on previous day.
Moderation
[ ]Candidate for moderation are identified by the Teams, Panels, range of grades, background, solicitors, barristers, BAME, Females. The Selection exercise teams agrees with policy on moderation.
[ ] Create a sheet for each of the candidates that follows in the above categories with their original grades.
[ ] Panel 1 and Panel 2 are allocated each other candidates moderation sheets each with their reports like peer review.
[ ] Panel meets with the original candidates panel to decide on candidates grades.
[ ] Panel makes changes on the moderation control sheet.
[ ]  Ability to reflected the changes on the moderation control  sheets to appear on the overall Merit list.
"EPIC - Merit list
panellists:

create panellists app
collection of daily scores for sift and selection day
collection of scenario scores
present scenario responses
admin:
manage panellists
configure panels
live merit list report
configure scenario panels
update live merit list report with scenarios
scenario report & update application status"

"EPIC - Merit list
panellists:

support for ranking
support for calibration
support for moderation
admin:
support for ranking
support for calibration
support for moderation"

Links to the templates https://drive.google.com/drive/folders/1p7vtfwDXtgMqKmL2vj7v32vQrKnyZ0FJ

@warrensearle  - What is the update with this work? Why is it blocked?

Closing as this has been superseded by #1861


Simplest generic function doesn't work, because "too complex"?

"typescript": "5.2.2"
"json-schema-to-ts": "^2.9.2"

I was trying to come up with a way to describe GPT functions, along with the name and description:
export type GPTFunction = {
  name: string;
  description?: string;
  parameters: { type: "object" } & JSONSchema;
};

export type Return<T extends GPTFunction> = FromSchema<T["parameters"]>;

export const SetImprovedDescription = {
  name: "set_improved_description",
  description: "Set improved description",
  parameters: {
    type: "object",
    properties: {
      description: { type: "string" },
      explanation_for_changes: { type: "string" },
    },
    required: ["description"],
    additionalProperties: false,
  },
} as const satisfies GPTFunction;

But then this doesn't work:
function call_gpt<T extends GPTFunction>(
  schema: T,
  system: string,
  user: string
): null | Return<T> {
  return null;
}

const a = call_gpt(SetImprovedDescription, "system", "user");

It errors out with:
Type instantiation is excessively deep and possibly infinite.ts(2589)
Expression produces a union type that is too complex to represent.ts(2590)

Most weirdly, while it does error out, it actually still correctly infers the type!

I also tried simplifying the function declaration. Avoiding my types (Return and GPTFunction), and replacing them with their applications directly doesn't change the error.
This works, but it's not what I need unfortunately:
export function call_gpt2<T extends JSONSchema>(
  schema: T,
  system: string,
  user: string
): null | FromSchema<T> {
  return null;
}

const b = call_gpt2(SetImprovedDescription["parameters"], "system", "user");

Another attempt that doesn't work, and it's actually quite a simple thing:
function make_gpt_caller<T extends JSONSchema>(
  name: string,
  description: string,
  // parameters: Narrow<T> // tried both ways
  parameters: T
): (system: string, user: string) => FromSchema<T> {
  return (system: string, user: string) => {
    return null as any;
  };
}

No custom types, very simple generic... still I get, even without ever calling this, for "return":
Type instantiation is excessively deep and possibly infinite.ts(2589)
Expression produces a union type that is too complex to represent.ts(2590)

What do I miss? Did I misconfigure something, or is there a different ways to use generics here?

FAQ added: https://github.com/ThomasAribart/json-schema-to-ts/blob/main/documentation/FAQs/applying-from-schema-on-generics.md
Cheers !


bug: JetBrains Cody doesn't work on Windows ARM64

Cody Version
Build of 2d4b31a7bd8f201d02ed1a8df8dd763805bb519a which is 6.0.3
IDE Information
IntelliJ IDEA 2024.1.2 (Community Edition)
Build #IC-241.17011.79, built on May 21, 2024
Runtime version: 17.0.11+1-b1207.24 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 4
Registry:
ide.experimental.ui=true
Non-Bundled Plugins:
com.sourcegraph.jetbrains (6.0-localbuild)
Kotlin: 241.17011.79-IJ
Describe the bug
On Windows on ARM64, nothing works. Running commands gives Cody Context Filters error messages. And the logs contain this:
2024-05-31 03:02:39,457 [  15008]   WARN - #com.sourcegraph.cody.agent.CodyAgent - Unable to start Cody agent
com.sourcegraph.cody.agent.CodyAgentException: Node binary not found at path C:\Users\Dominic Cooney\AppData\Roaming\JetBrains\IdeaIC2024.1\plugins\Sourcegraph\agent\node-win-arm64.exe
2024-05-31 03:02:39,544 [  15095]   WARN - #com.sourcegraph.cody.agent.CodyAgent - Failed to execute call to agent
java.util.concurrent.ExecutionException: com.sourcegraph.cody.agent.CodyAgentException: Failed to start Cody agent
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
        ...

There is, indeed, no node-win-arm64.exe binary at that path.
Expected behavior
Expect Cody to work on Windows arm64
Additional context
No response

There are Windows ARM64 node binaries (here, for example) but they're not in the archive we download from GitHub.

I believe we can just run the x86 Node binary on ARM64 Windows computers.

Good point, also an option.


GW 0.23 doesn't seem to be working on an F1 bluepill.

I'm using a Windows 10 machine, just fyi!
I tried updating as normal, but the upd file wouldn't flash. Just sat there forever.
When I end tasked the gw.exe it said:
** FATAL ERROR:
unpack requires a buffer of 2 bytes
So, I manually flashed the .hex files. (To two different F1 bluepills, the F1 'Blackpill' from RobotDYN and a generic F1 Bluepill)
Both bluepills look similar. (I'm using an F1 PCB board, too, with resistors soldered on, which worked fine up to yesterday, so I assume it's not that)
Todays disk dump:

Previous disk dump, same drive, same disk:

I tried dumping the same disk with all 3 drives I use, using 2 different bluepills.
Same results, more or less.
If I dump a Kryoflux image, (rather than a SPC) trying to open it in HxC tools crashes the program.
The images are .scp files, generated from Aufit.
https://mega.nz/file/xDADXIzR#H7W3lEER-TjPUMbk1o2peaxI63JwrWUa1hZRAbpp2pY
Disk images:
Previous disk dump: CaptainDynamo_Codemasters_Disk1of1_AtariST_Dump1.scp
Then, drive 1(worst drive), 2, 3 and drive 3 with bluepill 2.
Drive 1 and 2 are PC drives, drive 3 is a Teac FD-235F Amiga 500 drive.
Dumps created using:
gw read CaptainDynamo_DefaultsDrive3_Bluepill2.scp
etc for each dump (ie read with defaults)
~
I initially tried:
read --tracks="c=0-83:h=0-1:step=1" --revs=5 CaptainDynamo_Codemasters_Disk1Of1_AtariST_Dump1.scp
But that gave really weird looking results.
~
Also, --revs=3 produces images with 4 revolutions, in previous versions it produced images with 3.

I can't reproduce the error on update. Maybe it's just a rare blip. It should not be necessary to reprogram from HEX as the bootloader should not get overwritten. You could have tried reconnecting the Blue Pill and retry the command.
The problem with SCP/KF files and HxC seems to be a bug in HxC. It doesn't like stream files that don't start at the index mark. If I force index-cueing in the generated files then they load into HxC just fine. If I don't, my SCP output looks rather like yours. And my KF files fail to load (rather than crashing) but it's surely the same issue you've seen.

I can't reproduce the error on update. Maybe it's just a rare blip. It should not be necessary to reprogram from HEX as the bootloader should not get overwritten. You could have tried reconnecting the Blue Pill and retry the command.
The problem with SCP/KF files and HxC seems to be a bug in HxC. It doesn't like stream files that don't start at the index mark. If I force index-cueing in the generated files then they load into HxC just fine. If I don't, my SCP output looks rather like yours. And my KF files fail to load (rather than crashing) but it's surely the same issue you've seen.

Yeah, not too worried about the update.
It happened once before on one of the devices, but I couldn't reproduce it since then.
Just said I'd mention it.
If it's a bug in HxC that doesn't like starting at the index mark, then most of the other programs that use .scp images are the same way.
The .scp files from 0.23 won't load in an emulator, either.
Not the Amiga ones, or Atari ST ones.
Neither Aufit nor HxC can produce working .adf / .st / .stx files from the images too.
So, they're not much use as they are presently.
(I can't test in a real machine at the moment)
Maybe index-cuing should be the new default?

Yeah, not too worried about the update.
It happened once before on one of the devices, but I couldn't reproduce it since then.
Just said I'd mention it.
If it's a bug in HxC that doesn't like starting at the index mark, then most of the other programs that use .scp images are the same way.
The .scp files from 0.23 won't load in an emulator, either.
Not the Amiga ones, or Atari ST ones.
Neither Aufit nor HxC can produce working .adf / .st / .stx files from the images too.
So, they're not much use as they are presently.
(I can't test in a real machine at the moment)
Maybe index-cuing should be the new default?

Let me do a quick test build for you to try.

Let me do a quick test build for you to try.

Please try the following build. No need to update the firmware, just run the new host tools. KF and SCP images are index-cued:
https://nightly.link/keirf/Greaseweazle/actions/artifacts/35243779.zip

Please try the following build. No need to update the firmware, just run the new host tools. KF and SCP images are index-cued:
https://nightly.link/keirf/Greaseweazle/actions/artifacts/35243779.zip

Yeah.
Seem to be fine.
Dumped with:
read --tracks="c=0-83:h=0-1:step=1" --revs=5 "CaptainDynamo_Codemasters_Disk1Of1_AtariST_Dump1.scp"

Yeah.
Seem to be fine.
Dumped with:
read --tracks="c=0-83:h=0-1:step=1" --revs=5 "CaptainDynamo_Codemasters_Disk1Of1_AtariST_Dump1.scp"

Great thanks. Can you try KF too. And also SCP in your emulator and aufit when you have a chance?

Great thanks. Can you try KF too. And also SCP in your emulator and aufit when you have a chance?

Both the Atari and Amiga images (.scp and .stx/.adf etc) work in emulators, too.
(SteemSSE and WinUAE, both latest stable, and latest betas)
HxC seems to be able to load and process them, too.
And, the KryoFlux dump:

Also looks perfect in HxC and can export fine. So.
All looks good.

Both the Atari and Amiga images (.scp and .stx/.adf etc) work in emulators, too.
(SteemSSE and WinUAE, both latest stable, and latest betas)
HxC seems to be able to load and process them, too.
And, the KryoFlux dump:

Also looks perfect in HxC and can export fine. So.
All looks good.

Excellent thanks

Excellent thanks