Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.asda.android/lib-main/libgnustl_shared.so" is 32-bit instead of 64-bit

[x] I have reviewed the documentation
[x] I have searched existing issues
[x] I am using the latest React Native version

We are using ReactNative in our app. App is crashing with Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.asda.android/lib-main/libgnustl_shared.so" is 32-bit instead of 64-bit only on Sony-Xperia device(Xperia XA/Android 7). Its not happening on other devices
we have removed the 64 bit versions of api from apk by adding following things in build.gradle
android {
    compileSdkVersion 27
    buildToolsVersion '27.0.2'

    flavorDimensions "default"

    …….

   defaultConfig {
        ...
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }

    packagingOptions {
    ……
        exclude '/lib/mips64/**'
        exclude '/lib/arm64-v8a/**'
        exclude '/lib/x86_64/**'
    }

    …….
}

Environment
Scanning folders for symlinks in /Users/vn0zpn2/ern_workspace/asda-ern-miniapps/DMTMiniApp/node_modules (5ms)
Environment:
OS: macOS Sierra 10.12.6
Node: 9.3.0
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0
Its happening in production. We are using the Litho along with React native(version: 0.51.0)
build.gradle
Steps to Reproduce
App Launch.
Expected Behavior
Should not crash on app launch
Actual Behavior
Crashes with log below
Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.asda.android/lib-main/libgnustl_shared.so" is 32-bit instead of 64-bit
       at java.lang.Runtime.load0(Runtime.java:897)
       at java.lang.System.load(System.java:1505)
       at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:71)
       at com.facebook.soloader.DirectorySoSource.loadLibrary(DirectorySoSource.java:42)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:299)
       at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:65)
       at com.facebook.soloader.DirectorySoSource.loadLibrary(DirectorySoSource.java:42)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:299)
       at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:65)
       at com.facebook.soloader.DirectorySoSource.loadLibrary(DirectorySoSource.java:42)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:299)
       at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:65)
       at com.facebook.soloader.DirectorySoSource.loadLibrary(DirectorySoSource.java:42)
       at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:299)
       at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:247)
       at com.facebook.react.bridge.ReactBridge.staticInit(ReactBridge.java:20)
       at com.facebook.react.bridge.NativeMap.(NativeMap.java:21)
       at com.facebook.react.bridge.JSCJavaScriptExecutorFactory.create(JSCJavaScriptExecutorFactory.java:23)
       at com.facebook.react.ReactInstanceManager$4.run(ReactInstanceManager.java:928)
       at java.lang.Thread.run(Thread.java:761)

updated..

I have the same problem with Samsung s7 and s8

@mindhivefi Could you please provide an example?

It looks like this issue has gotten quite stale. With 64-bit now available in master, I am going to close this and request anybody running into something similar to please open a new issue.

Wow, ran into this just now and can't believe this was closed just 17 hours ago with no resolution.

I am sorry you ran into this issue with such poor timing. Please do open a new issue as advised.

Since I  forgot to post a solution for the problem:
One of my dependencies shipped their own libgnustl_shared.so which has overwritten the one provided by react-native. I resolved this by moving implementation "com.facebook.react:react-native:+" as high up as possible and tewaking the packagingOptions
HOWEVER I did not upgrade to the newest version with 64bit support yet so you might want to ditch the exclude everything 64bit related section.
app/build.gradle
...
android {
    ...
    packagingOptions {
        // exclude everything 64bit related
        exclude '/lib/mips64/**'
        exclude '/lib/arm64-v8a/**'
        exclude '/lib/x86_64/**'

        // com.thirdparty:spotify-player:24 ships their own .so files
        // we do not want those
        pickFirst '/lib/x86/libgnustl_shared.so'
        pickFirst '/lib/armeabi-v7a/libgnustl_shared.so'
    }
}

dependencies {
    ...
    implementation "com.facebook.react:react-native:+"
    ...
    implementation 'com.thirdparty:spotify-player:24'
}

Maybe this ca help someone. You should start by analysing your dependencies (e.g. if this causes the issue you are facing), before applying this fix.

defaultConfig {         ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'         packagingOptions {             exclude '/lib/mips64/**'             exclude '/lib/arm64-v8a/**'      } }
this worked for me

defaultConfig { ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64' packagingOptions { exclude '/lib/mips64/**' exclude '/lib/arm64-v8a/**' } }
this worked for me

Did it worked in play store?

yes it worked.

yes it worked.

just once, then failed again. sad!

yes it worked.

just once, then failed again. sad!

what is the error?

yes it worked.

just once, then failed again. sad!

what is the error?

Doesn't work anymore on Playstore :'(

yes it worked.

just once, then failed again. sad!

what is the error?

Doesn't work anymore on Playstore :'(

what is exact issue? is it uploading apk or running?

yes it worked.

just once, then failed again. sad!

what is the error?

Doesn't work anymore on Playstore :'(

what is exact issue? is it uploading apk or running?

It's running alright, but Playstore won't accept it because of the 64 bit issue.

i got the same error when running and uploading to playstore. and above code helped me. and my app now on live.

What is your RN version ??? @russelRajitha

0.55.2

Using RN 0.60.5 version.
If you guys are wondering why your app crashes if you download it from playstore, make the below changes
packagingOptions {
exclude '/lib/mips64/'
exclude '/lib/arm64-v8a/'
exclude '/lib/x86_64/**'
pickFirst '/lib/x86/libc++_shared.so' //In pickFirst, replace the library name with the library that is causing error.
pickFirst '/lib/armeabi-v7a/libc++_shared.so' In pickFirst, replace the library name with the library that is causing error.
}
REASON - We are excluding all 64 bit libraries so that OS will not have confusion of which library to pick.
If you do not know which library is causing the crash, upload your bundle in Firebase test lab and then check. It will tell you which library is throwing the error

I am using react-native version 56.0 I am able to build apk but when I try to upload in play store it doesn't work. what should i do
here is my build.gradlew
`    compileSdkVersion 27
buildToolsVersion '27.0.3'
defaultConfig {
applicationId "com.christenpro"
minSdkVersion 16
targetSdkVersion 27
versionCode 32
versionName "2.24"
    vectorDrawables.useSupportLibrary = true
    ndk {
        abiFilters "armeabi-v7a", "x86"
    }
    multiDexEnabled = true
   dexOptions {
       jumboMode true
        javaMaxHeapSize "4g"
   // preDexLibraries = false
}

configurations.all {
resolutionStrategy.eachDependency { DependencyResolveDetails details ->
if (details.getRequested().getGroup() == 'com.google.android.gms') {
details.useVersion('15.0.1')
}
}
}
}`

I am using react-native version 56.0 I am able to build apk but when I try to upload in play store it doesn't work. what should i do
here is my build.gradlew
` compileSdkVersion 27
buildToolsVersion '27.0.3'
defaultConfig {
applicationId "com.christenpro"
minSdkVersion 16
targetSdkVersion 27
versionCode 32
versionName "2.24"
    vectorDrawables.useSupportLibrary = true
    ndk {
        abiFilters "armeabi-v7a", "x86"
    }
    multiDexEnabled = true
   dexOptions {
       jumboMode true
        javaMaxHeapSize "4g"
   // preDexLibraries = false
}

configurations.all {
resolutionStrategy.eachDependency { DependencyResolveDetails details ->
if (details.getRequested().getGroup() == 'com.google.android.gms') {
details.useVersion('15.0.1')
}
}
}
}`

Our ultimate fix was to upgrade to 0.59 react-native version


Set up IAM Federated Access

We've previously discussed using IAM Federated Access. We've put together a sample implementation using Auth0.
We should record a decision in the ADR.

To be able to use the Auth0 GitHub integration we need to get an OAuth app setup that is owned by the organisation (ministryofjustice) with the appropriate callback URL.

@ewastempel kindly set us up an OAuth application in the ministryofjustice GitHub, so here's the pull request to tie it all together 👍🏼


Is it possible to add LED brightness support for the Aerox 3 wireless ?

Hi,
I can see that the Aerox 3 supports the --led-brightness option, but not the wireless option.
Do you think it could be added ?
I can build & test myself if you don't have the mouse
Thanks a lot for your work, it's really awesome :+1: !

Hello,
I had to remove this option to support dim timer without having to much development. You are already able to lower the brightness by setting a darker color.
For example:

FF0000 → red, full brightness
880000 → red, 50% brightness

Oh, I didn't think about that, thank you !


Write data failed

Hello!
My Influxdb version is 1.7.9.
When I was writing data to influxdb, the data could not be written because my disk was full. After I cleaned up other files unrelated to Influxdb, I still couldn't write to Influxdb. Still showing insufficient disk space. After I restarted Influxdb, the historical data was lost. How should I deal with this situation? I don't know what happened in the middle.
Looking forward to your reply! Thanks!

#9923


If a root is removed from the DOM and reinserted, should its observations remain intact?

If an observation root node is removed from the DOM and reinserted, and the ancestor/descendant relationship between the root and its targets remains intact, should the observations remain intact?  Currently, the spec (section 3.2.5) indicates that the observations will be deleted.

Resolved with #58


Is this project still relevant?

Thanks for your contribution, is this project still relevant though and useable?

I tested it and yes it works but returns only basic information


AzureBlobFileSystem._strip_protocol fails when using 'simplecache'

fsspec.AsyncFileSystem._get forwards a list of paths to adlfs.AzureBlobFileSystem._strip_protocol, but _strip_protocol is expecting a string. This happens when copying a file to simplecache (?).
How to reproduce:
import fsspec

f = fsspec.get_mapper(
    "simplecache::abfs://test/data",
    simplecache={
        "cache_storage": "/tmp/azure-cache",
    },
    abfs={"anon": False, "account_name": "somestorage"},
)

print(list(f.values()))

The following code seems to "fix" the problem in adlfs/spec.py@475:
    @classmethod
    def _strip_protocol(cls, path: str):
        ...
        if isinstance(path, list):
            return [cls._strip_protocol(p) for p in path]
        if not path.startswith(("abfs://", "az://", "abfss://")):
        ...

Would this make sense?
Related issue: https://github.com/fsspec/filesystem_spec/issues/794.

This is a duplicate of #333 and solved with PR #333. Can be closed and marked as resolved.


React-native 0.60.4 android release build issue - package is not a valid resource name

React Native version:

"dependencies": {
"@react-native-community/async-storage": "^1.6.1",
"@react-native-community/push-notification-ios": "^1.0.2",
"apollo-cache-inmemory": "^1.6.3",
"apollo-client": "^2.6.4",
"apollo-link": "^1.2.12",
"apollo-link-context": "^1.0.18",
"apollo-link-dedup": "^1.0.19",
"apollo-link-error": "^1.1.11",
"apollo-link-http": "^1.5.15",
"apollo-link-ws": "^1.0.18",
"apollo-utilities": "^1.3.2",
"bugsnag-react-native": "^2.22.5",
"emoji-utils": "^1.0.1",
"graphql": "^14.4.2",
"graphql-tag": "^2.10.1",
"just-debounce": "^1.0.0",
"just-throttle": "^1.1.0",
"lodash": "^4.17.15",
"lottie-ios": "^3.0.3",
"lottie-react-native": "^3.1.0",
"moment": "^2.24.0",
"moment-timezone": "^0.5.26",
"prop-types": "^15.7.2",
"react": "16.8.6",
"react-apollo": "2.1.9",
"react-countdown-now": "^2.1.1",
"react-moment": "^0.9.2",
"react-native": "0.60.4",
"react-native-android-keyboard-adjust": "^1.2.0",
"react-native-clear-app-cache": "^1.0.4",
"react-native-device-info": "^2.3.2",
"react-native-fast-image": "^7.0.2",
"react-native-firebase": "^5.5.6",
"react-native-gifted-chat": "^0.9.11",
"react-native-googleanalytics": "^1.0.0",
"react-native-image-picker": "^1.0.2",
"react-native-iphone-x-helper": "^1.2.1",
"react-native-linear-gradient": "^2.5.6",
"react-native-markdown-renderer": "^3.2.8",
"react-native-orientation-locker": "^1.1.6",
"react-native-permissions": "^1.2.0",
"react-native-phone-call": "^1.0.9",
"react-native-progress-bar-animated": "^1.0.6",
"react-native-push-notification": "^3.1.8",
"react-native-snap-carousel": "3.7.4",
"react-native-sound": "^0.11.0",
"react-native-table-component": "^1.2.0",
"react-native-uuid-generator": "^6.0.0",
"react-native-vector-icons": "^6.6.0",
"react-native-video": "^5.0.0",
"react-native-view-overflow": "^0.0.4",
"react-native-webview": "^6.9.0",
"react-navigation": "2.18.3",
"react-redux": "5.0.7",
"redux": "4.0.0",
"subscriptions-transport-ws": "^0.9.16",
"uniqueid": "^1.0.0",
"universal-cookie": "^4.0.2",
Steps To Reproduce
Issue while building android release version. react-native run-android --variant=release. IOS build works fine and so is android debug build
1.FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:mergeReleaseResources'.

~/rn60-new/git/MyApp/android/app/build/generated/res/react/release/raw/package.json: Error: package is not a valid resource name (reserved Java keyword)

Describe what you expected to happen:
Expect the android release to succeed.

@mailyokesh Its not a problem with react-native 0.60.4. Its because of some of your dependencies. Close this issue.


PowerShell Examples in Docs

Please add powershell examples to docs.
https://ntfy.sh/docs/publish/
e.g.
$message = "message"
$topic = "topic"
$messagePost = Invoke-WebRequest -Method Post -UseBasicParsing -UseDefaultCredentials -URI "ntfy.sh/$topic" -Body $message

Thanks for the ticket. I don't really have a Windows PC at hand. Could you create a pull request against https://github.com/binwiederhier/ntfy/blob/main/docs/publish.md with the examples? Most of them will likely be straight forward, given the example you gave, but I'd rather someone who can actually test it create the PR.

Please add powershell examples to docs.
https://ntfy.sh/docs/publish/
e.g.
$message = "message"
$topic = "topic"
$messagePost = Invoke-WebRequest -Method Post -UseBasicParsing -UseDefaultCredentials -URI "ntfy.sh/$topic" -Body $message

I have added this to the docs now for you it will be up once @binwiederhier has had chance to review the changes and merge the pull request.

This is done and will be in the next release. Thanks to @Joeharrison94.


add E2E test for signup

What is the feature?

Add selenium test for signup

What is the solution?

Add  unittest selenium in users/tests.py

Codecov Report

Merging #80 (253b707) into beta (cb2962e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             beta      #80   +/-   ##
=======================================
  Coverage   67.14%   67.14%
=======================================
  Files          24       24
  Lines         700      700
  Branches       83       83
=======================================
  Hits          470      470
  Misses        212      212
  Partials       18       18

Continue to review full report at Codecov.

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


SPIKE GitHub integration for backlog

To run:

create private github token
add a new file in root called .env and set GITHUB_TOKEN=

My thoughts are that this script could be run as part of a GitHub Travis
cron job every day/week.
Ideally we could have Travis commit the updated entry files to GitHub
but master is protected, so I'm not sure about this atm.
Would also need documentation, handling for if a contributor had not set their travis credentials up etc.

I suspect we will not continue this work but raised for people to look at, I have updated the list based on the output of this script over at: https://github.com/alphagov/govuk-design-system/compare/update-backlog-list?expand=1

You can preview this change here:
Built with commit 3acb2e66a012a66dc0db5c0df1f219de9092ac29
https://deploy-preview-1124--govuk-design-system-preview.netlify.com

Note that you could run this at build time instead of generating a new file which'd remove the need to have Travis commit files however:

contributors wouldnt be able to run this page without setting up credentials
we'd have to figure out to only run it in production or with a flag or some such, since it'd be slow for regular development
we'd likely blow our GitHub rate limit budget

You could continue to use octokit to create a pull request perhaps instead of committing to master:
https://octokit.github.io/rest.js/#octokit-routes-pulls-create


ClouDNS Support

Hello,
Do you think you could add support for ClouDNS API?
https://www.cloudns.net/wiki/article/41/
Thanks.

Hello,
Working on it now, will come in the next update.


Use caddy as the main server

I think Caddy could be used for the main part of the server. Gitea would listen on a different port on localhost, and Caddy would listen on the main port chosen by the user. This would allow us to do more complex things easier such as:

Automatic HTTPS with Let's Encrypt
Redirect HTTP to HTTPS
Gitea pages on a separate domain
Separate domain for raw files
Redirect old URLs
Set timeouts
Listen on multiple domains and IPs

Many of the issues listed above could be fixed very easily if we integrate Caddy into Gitea.

I will integrate Let's Encrypt with multiple domains and redirect HTTP to HTTPS.

As long as it's optional, I use nginx for everything on my server and would like to keep it how it is right now with Gitea behind nginx.

I think that it is not the role of gitea to handle all of specific frontend config. For exemple in gitea-infrastructure  we use traefik and we should let that choice to user for setting inside is own env. gitea should only offer a simple http interface maybe some additional sugary but we should keep it simple.

#1798 @lunny @tboerger @sapk @cez81 @geek1011 @lafriks @ethantkoenig @andreynering @DblK

What about http/2? (For which you would need a secure connection over https)

Just make gitea a caddy-plugin :trollface:

+1

@sapk  I see this more as an optional choice. Add it to the documentation, support it.
Especially Gitea Pages is very important to me and a fundamental benefit to Github.
They offer only support for Jekkyl, one of some hundred of static site generators.
Open source is all about easy access, otherwise is it just hypocrisy.
Caddy offers https for everyone, in a very simple way. This means a secure internet connection and easy webpages for everyone. I think this is a great idea.

We could describe how to use caddy and gitea side by side to work like github pages that not that difficult and everything needed is allready here. Just use the git plugin of caddy to pull changes and execute a command (hugo, jekyll or otherq) if needed.

Github pages work only with Jekkyl. Gitlab pages offer support for more. I am for IPFS anyway:
https://ipfs.io/

I agree on using nginx/http for the web server and configs

I'm very interested in this discussion... not so much because of caddy... but on what this discussion implies.
Is Gitea going to try to do it all... or is Gitea going to do one thing and rely on integration options for the non-core stuff...
Seems to me that a product like Gitea should focus on the core: git repo management, issues and wiki and rely on proper documentation and integration options for the other stuff. That would be my hope anyway.
Open source is about choice. Stuffing everything into Gitea, creating a big monolithic application in the process, would be horrible.

Closing as caddy in front of Gitea currently works.


Bundler breaks when using Psych 2.0.9 and Rubinius

Psych 2.0.9 added a feature where it dumps Hash instances with instance variables if any are present. For example:
require 'psych'

Psych.dump(:a => 10) # => "---\n:a: 10\n"

hash = {:a => 10}

hash.instance_variable_set(:@number, 20)

Psych.dump(hash) # => "--- !ruby/hash-with-ivars\nelements:\n  :a: 10\nivars:\n  :@number: 20\n"

On Rubinius the Hash class has a bunch of instance variables used for its internal state (since Hash is pure Ruby). This seems to result in .bundle/config files ending up with contents such as the following after a bundle install --deployment:
--- !ruby/hash-with-ivars
elements:
  BUNDLE_FROZEN: '1'
  BUNDLE_PATH: vendor/bundle
  BUNDLE_DISABLE_SHARED_GEMS: '1'
ivars:
  :@mask: 15
  :@entries: !ruby/object:Rubinius::Tuple {}
  :@capacity: 16
  :@max_entries: 12
  :@state: &1 !ruby/object:Hash::State
    compare_by_identity: false
    head: &3 !ruby/object:Hash::Bucket
      value: '1'
      next: &2 !ruby/object:Hash::Bucket
        value: vendor/bundle
        next: &4 !ruby/object:Hash::Bucket
          value: '1'
          key: BUNDLE_DISABLE_SHARED_GEMS
          key_hash:<PHONE_NUMBER>860004216
          link:
          state: *1
          previous: *2
        key: BUNDLE_PATH
        key_hash:<PHONE_NUMBER>124309747
        link:
        state: *1
        previous: *3
      key: BUNDLE_FROZEN
      key_hash:<PHONE_NUMBER>883449113
      link:
      state: *1
    tail: *4
  :@size: 3

This in turn causes problems such as the one described in https://github.com/rubinius/rubinius/issues/3284 (which I'm closing in favour of this issue).
The problem appears to be Bundler manually parsing YAML files, instead of just using YAML: https://github.com/bundler/bundler/blob/a2343c9eabf5403d8ffcbca4dea33d18a60fc157/lib/bundler/settings.rb#L158
See the following Psych issue for more info: https://github.com/tenderlove/psych/issues/216

This begs the question: why does Bundler parse YAML using regular expressions instead of Ruby's YAML library?

Worth mentioning: this will break on MRI as well given it were to store any instance variables in a Hash. It's not an issue in Rubinius, it just manifests there because we're (apparently) the only Ruby implementation that uses instance variables inside the Hash class.

Bundler parses YAML using regex because the configuration (and lockfile) must be known before bundler can activate any version of yam.

@YorickPeterse I'd be happy with a patch that dumps Bundler.settings as a YAML hash--it should never be written as a Ruby object. As @segiddins said, we cannot load any YAML parsing ruby code until after the config file has been parsed. And we can't use JSON because that's not present in Ruby 1.8.

@indirect Where exactly does Bundler currently dump the contents of .bundle/config? I tried searching for YAML.dump and such but I couldn't really figure it out.

If Bundler can't read YAML then it shouldn't use YAML for the config file format.
Would you accept a patch to not use YAML here?

@YorickPeterse In the Settings class.
@brixen what would "not use YAML" mean? If it outputs a file that can be parsed correctly by both the Bundler regex and YAML.load, probably.

@indirect Perhaps I'm having the dumb, but I can't seem to figure out where it actually writes the data to .bundle/config :/

@YorickPeterse haha, no worries. It's here: https://github.com/bundler/bundler/blob/master/lib/bundler/settings.rb#L140.

@brixen what would "not use YAML" mean? If it outputs a file that can be parsed correctly by both the Bundler regex and YAML.load, probably.

Perhaps it would make sense to serialize the settings as a hash, and then just #inspect it? Granted, loading could mean arbitrary execution, is someone mucked with .bundle/config.
I know I've been bitten by pseudo-YAML problems before, but I haven't had the time to report them. (I've had stuff like bundle config build.pg --with-pg-config=/path/to/pg_config create some really bizarre, unparsable stuff in .bundle/config, thus breaking bundler. Manually editing the .bundle/config has been my work around thus far).

There have been various bugs as Ruby and Psych have changed their output formats and quoting defaults. Right now, they should all be fixed.
That said, I'm open to serializing settings in a simpler way as long as it's compatible.
On Fri, Jan 16, 2015 at 4:00 PM, Charles Strahan<EMAIL_ADDRESS>wrote:

@brixen what would "not use YAML" mean? If it outputs a file that can be parsed correctly by both the Bundler regex and YAML.load, probably.
Perhaps it would make sense to serialize the settings as a hash, and then just #inspect it? Granted, loading could mean arbitrary execution, is someone mucked with .bundle/config.
I know I've been bitten by pseudo-YAML problems before, but I haven't had the time to report them. (I've had stuff like bundle config build.pg --with-pg-config=/path/to/pg_config create some really bizarre, unparsable stuff in .bundle/config, thus breaking bundler. Manually editing the .bundle/config has been my work around thus far).

Reply to this email directly or view it on GitHub:
https://github.com/bundler/bundler/issues/3348#issuecomment-70342257

Is there documentation for exactly what should be in the config file? I often see a mix of true or '1' and the keys don't appear to match all the env vars, etc.
Is the structure nested? If yes, that's significantly more difficult and perhaps YAML is the least of evils. If it is not nested, or could be modified to not be nested, a simple line format with a few simple types (strings and booleans, perhaps) would suffice.
If there's really no interest, I won't waste time on it. If there is, I'm happy to do a PR.

Right now the config file is used to store values set via bundle config, passed via CLI --flags, or set via BUNDLE_WHATEVER=stuff environment variables. The distinction between true and '1' shouldn't be relevant, since we just check if the settings are truthy, and the structure isn't nested.
I would definitely be happy to disconnect the settings writer from YAML, because it's been the source of a lot of issues over time, but it absolutely has to be compatible with the existing config file and parser.

@indirect thanks for the additional clarification.
If there are exact and comprehensive tests, I can certainly make it absolutely compatible with the existing config file and parser. :) However, since I doubt that ideal situation exists, if we did have a parser decoupled from YAML, at least it wouldn't break arbitrarily beyond our control and it wouldn't be tied to an enormous, difficult to replicate component. Further, I could easily run it on every config file I can find on GitHub as a one-off acceptance test.
Another question: I've often had my .bundle/config file rewritten by different versions of Bundler/YAML/Psych/who-knows-what, with changes to the config file, but without my changing any options. Is it acceptable to allow this behavior? If yes, I can make the parser "normalize" config files that are read which may make both future evolution and comprehensive tests easier.

We didn't write comprehensive tests up front, because we thought YAML was built in to every Ruby and we could just use it and never worry about it. That plan... did not work out. Right now we have a lot of tests that both write and read the config file in one test, but I would guess close to zero tests that deliberately try to parse specific files. Since you're not supposed to check the config file into your git repo, I imagine there also won't be that many on Github.
That said, YAML has caused us enough pain that I'd like to support removing the dependency, even if it causes some pain the the short term of having to fix edge cases quickly after releasing a new config serializer. I'm in favor of this. :+1:

@YorickPeterse I actually can't reproduce the issue with the code sample you gave in the issue description -- perhaps in a later update of psych (I'm now on 2.0.13) this behavior was reverted?

@segiddins It was resolved shortly after finding it, see https://github.com/tenderlove/psych/pull/218.


Multiple custom resource links to deployments

User report

It would be great If you can assign multiple featureflag configurations to a deployment like openfeature.dev/featureflagconfiguration: firstconfig, secondconfig

Needs evaluation on whether we would want to do this.

Relates to https://github.com/open-feature/open-feature-operator/issues/17


Move methods defined in chewy.rake out into separate file & class

We'd like to use the methods in chewy.rake but not the rake tasks. How would you feel about me opening a PR to move the functional elements out into a separate file and class?

Sure, probably it will be a module

See PR #204


Frontend with frameworks: Angular:Sharing data between parent and child components in Angular

Required Content

Sending data to a child component
Sending data to a parent component
Using @Input() and @Output() together

Link to get started: https://angular.io/guide/inputs-outputs
Rules to follow

Do NOT copy/paste
Do not push to the main branch
Specify the issue you are working on the PR
Do not remove previous content

I would like to work on this issue kindly assign it to me.

Sure @RIYANSHGARG Go ahead!

I have added the pull request please consider it.

I have added the pull request please consider it


Provide FormattableString overloads for format methods that special case the format arguments

As suggested by https://github.com/aspnet/Razor/issues/566#issuecomment-146580237 i'm suggesting to provide FormattableString overloads for methods which special case the arguments.
With C# 6 you can now safe yourself from writing MethodFormat("...", ...) as sugar for Method(String.Format(...)) since you can just write Method($"...").
But this also works when the arguments are special cased if you demand a "FormattableString" argument.
So in addition to
public TagHelperContent AppendFormat(string format, params object[] args)
{
    HtmlContentBuilderExtensions.AppendFormat(this, null, format, args);
    return this;
}

I suggest
public TagHelperContent AppendFormat(FormattableString formatString)
{
    HtmlContentBuilderExtensions.AppendFormat(this, null, formatString.Format, formatString.GetArguments());
    return this;
}

Then you can have
string unencodedText = "Hello, World!";
context.AppendFormat($"<blink>{unencodedText}</blink>")
//or even
context.AppendFormat($"<blink>{"Hello, World!"}</blink>")

Closing because we think this is low value and would be a breaking change for us to add it as an overload


Update Gems

This is in response to https://github.com/mide/mide.io/network/alert/Gemfile.lock/nokogiri/closed.


nc_perf/tst_gfs_data_1.c is not really working well

There is a benchmarking program/test that I added in a recent release, tst_gfs_data_1.c. It tests that netcdf-c can output data the way that the NOAA GFS model does it, i.e. with parallel I/O and zlib compression.
This test is working in that it will detect problems with writing this way, which is good.
But it's not really working well because I messed up the decompositions. I am using this same test in the CCR project and have discovered some problems, which I am fixing there. Then I will update the netcdf-c version of the test.

Thanks @edhartnett , appreciated as always!


Nebular stepper scss override

I need to override the nebular stepper, as we know that when the any step completed then the "checkmark" icon displayed but my use case is different I need the number will still remained not checkmark icon but color will change as same as icon (i.e. # ffffff).
Issue type
I'm submitting a ...  (check one with "x")

[ ] feature request

Issue description
need help in nebular stepper, as we know that when the any step completed then the "checkmark" icon displayed but my use case is different I need the number will remain but color will change as same as icon (i.e. # ffffff).
Current behavior:

Expected behavior:

Steps to reproduce:

Related code:
<nb-card ">

<nb-step [label]="labelOne">
<ng-template #labelOne>

<nb-step [label]="labelTwo">
<ng-template #labelTwo>

<nb-step [label]="labelThree">
<ng-template #labelThree>

<nb-step [label]="labelFour">
<ng-template #labelFour>

-->
Other information:
npm, node, OS, Browser
<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular

Thanks in Advance !!

hi @rakesh0692 !
Look like you need to modify the appearance of stepper's numbers. To do that - extend NbStepperComponent  and change its templates, it has no configurations 🙂. To change a color and background color, use customization of Nebular themes


Fix concurrency grouping to allow multiple parallel manual dispatches of a job.

Adds concurrency bits to a few workflows that did not have them but should.

Fixes concurrency grouping for "workflow_dispatch" to use the run
number (which is unique for each dispatch for a given (repo, workflow)
pair) so that a new manual dispatch does not cancel a
previously-running one.  This allows doing multiple manual dispatches
to try to reproduce intermittent issues.

Problem
Trying to manually dispatch multiple copies of a workflow ends up canceling all but the latest dispatch, since they all have the same sha.
Change overview
Use the run number as the grouping for the "workflow_dispatch" trigger.
Testing
Manually dispatches some workflows and they all ran.

For review purposes, most of this PR was generated with:
perl -pi -e "s/^    group: \\\${{ github.workflow }}-\\\${{ github.event_name == 'pull_request' && github.event.number \|\| github.sha }}/    group: \\\${{ github.workflow }}-\\\${{ (github.event_name == 'pull_request' && github.event.number) || (github.event_name == 'workflow_dispatch' && github.run_number) || github.sha }}/" .github/workflows/*

@msandstedt @saurabhst @andy31415 @mspang @jmartinez-silabs @LuDuda Please take a look?


Support multiple Jenkins instances in config file

This commit adds sections to the .jenkins-cli config file. The section
which should be used is specified with the -e or --environment. If no
environment is specified, the "DEFAULT" section is used.
Fixes #36

Hello @radomirbosak .
I have two suggestions:

Make error message more informative.
For example, running jenkins -e LOCAL will give me No such environment: LOCAL error. This looks a bit confusing. I would change it for something like LOCAL section in .jencins-cli settings file is not found

I think it is good practice to test cover new functionality. In this case TestCliFileUsing can be extended with new test case which tests that correct section is used when calling JenkinsCli.read_settings_from_file with respective environment.

Hey @LD250 , I changed the error message and added a unit test for the new functionality.
The third commit fixes a unclosed-file warning revealed by the unit tests:
$ python3 -m unittest discover tests/
/home/rbosak/repos/jenkins-cli-python/jenkins_cli/cli.py:129: ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/hupu/.jenkins-cli' mode='r' encoding='UTF-8'>
  config.readfp(open(filename, 'r'))

please take a look (PTAL)


Voiding items when interacting with Create's basin

LaserIO version
1.3.3
Minecraft Version
1.18.2
Forge Version
40.1.68
Modpack & Version
Encrypted 1.2
Do you have optifine installed?
No
Describe the issue
If you use a basic filter when inserting into a basin from Create, it will void 48 items at a time since the basin can only hold 16 at a time.
Steps to reproduce

Use an item card to pull from an inventory (drawer in my case) with at least a full stack.
Use another item card to insert into the basin.  The basin's capacity is 16 for the recipe.
With just a basic filter on the inserting card, it will pull 64 from the drawer, insert 16 into the basin, and void the other 48.
With a counting filter set to 16 on the inserting card, it will function correctly, and leave 48 in the drawer.

Expected behaviour
When using a basic filter, it should not void any excess items.  It should take what it requires and leave the rest.
Screenshots
No response
Log files
No response
Additional information
No response

I am able to duplicate this issue - and I know why its happening - however, I'm not sure if its because I'm doing something wrong, or create is. I need to investigate further and will update this as I find out.

So it turns out what create is doing is not great but I should also be checking for this kind of shenanigans :) So i added some extra checks in to prevent it. Current commit resolves this for extract mode but not stocking yet. That'll be a different kind of fix.


modal dialog doesn't fade out

//= require bootstrap/modal

I only require the modal.js, then fade in is ok, but fade out doesn't work, it just dismiss

//= require bootstrap/modal
// = require bootstrap/transition

@import "bootstrap-sprockets";
@import "bootstrap/variables";
@import "bootstrap/mixins";
@import "bootstrap/component-animations";
@import "bootstrap/modals";

ok, I find it can work with these files


fix: make "find references" multi-token mapping aware

Part of https://github.com/rust-analyzer/rust-analyzer/issues/10070
I was hoping that this would fix "find references" on salsa queries, but salsa emits multiple defs sharing the same span (the trait method, and an impl of that trait).

Can we add a test(ing infra)? As our proc macros are behind a trait, I think what we can do is write a fake impl of that trait, which doesn’t have to deal with dylibs and stuff.
Actually, do we already have such fake expanders? It feels very obvious that we should do this already for all kinds of tests, and, if we are not doing that, that seems like a broken window to me

Right, all the stuff dealing with multi-token mapping is also relevant for MBE, we don't need proc macros there. I do still plan on adding some general proc macro tests though.

bors r+


feat: allow injecting Picasso styles first

SP-2562
Description
We have an issue in Storybook that's coming from the fast that we use two styling libraries simultaneously. The issue is: styled-components library doesn't always destroy the style tags it created, even when components are unmounted. While Picasso works correctly and unmounts all of the style tags.
The issue appears when we render a new instance of Picasso (e.g. new storybook story), so it adds style tags back. But it appends them in the end of the <head> tag, so they appear after the ones related to styled-components. The order of styles changes and in some places it breaks the styling.
In this PR we allow to always add Picasso styles first, by using the same option provided by MUI framework:
https://v4.mui.com/styles/advanced/#injectfirst
How to test

Open some story
Add styles tag once you've rendered the component, you can use this snippet:

const iframe = document.querySelector('#storybook-preview-iframe').contentDocument
const style = iframe.createElement('style')
style.setAttribute('id', 'my-styles')
iframe.querySelector('head').appendChild(style)

Navigate to another story
Picasso styles should come before the style tag you've added

Development checks

[ ] Add changeset according to guidelines (if needed)
[ ] Read CONTRIBUTING.md and Component API principles
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure that all PR checks are green
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[ ] Self reviewed
[ ] Covered with tests

Breaking change

[ ] codemod is created and showcased in the changeset
[ ] test alpha package of Picasso in StaffPortal

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal/fx-codeowners you can see here: https://happo.io/a/675/p/1189/compare/f54293fcec8ff69852c696671b471b5a88a0fa90/27bd4b59441e9c50ecff45cbbaa3d11d30980963
that one styling issue was fixed.

Actually I think this is unrelated, we have small flakiness in happo for storybook. It was implemented just a few days ago and we are catching the bugs now 🙂
I approved the changes


Add better task setup

Add overloads to AddScheduledTask to provide options
Add extension method AddScheduledTaskOptions
Add auto register for SchedulerHostedService

+version: feature

The readme is not updated yet. This had to be done before merging!


lib/end: print a warning to run as root when permission denied

When a subcommand attempts to grab a lock due to permission denied or
end fails to delete something due to permission denied, a warning will
now be printed advising the user to run the command as root.
Example:
derek@proton ~/go/src/github.com/containers/build> ./bin/acbuild end
you'll need to run this as a user with appropriate privileges
end: remove .acbuild/currentaci/rootfs/var/www/localhost/htdocs: permission denied

Fixes https://github.com/containers/build/issues/284

One nitpick, please make it say ‘a user with appropriate privileges’ not ‘root’.

nitpick applied

@lucab this should be good to go if you want to give it another pass


chore(main): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2024-09-20)
Features

only require energy in dict to be returned & more tweaks (8d7041f)
reorganize and restructure for benchmark focus BREAKING (5fae9b1)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.2.0
:sunflower:


[stable/percona]: Resource and image overrides for initcontainer

Signed-off-by: Asmund Tokheim<EMAIL_ADDRESS>
Is this a new chart
No
What this PR does / why we need it:
Sets resources for percona init container so it can be used in namespaces with resource quotas. Also allows overriding init container image as most other charts do.
Which issue this PR fixes
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @davidkarlsen

:+1:

/ok-to-test

/lgtm


Feature/refactor layout #203

Description
Removed treatment of 'layout' attribute as a special case, instead looking for 'widget:flowgraph' tag
Testing instructions
Add a set up instructions describing how the reviewer should test the code

Review code
Check Travis build
Review changes to test coverage
npm test

Agile board tracking
connect to #203

Codecov Report

Merging #226 into version1 will decrease coverage by 0.38%.
The diff coverage is 78.37%.

@@             Coverage Diff             @@
##           version1    #226      +/-   ##
===========================================
- Coverage     95.48%   95.1%   -0.39%
===========================================
  Files            59      59
  Lines          1374    1388      +14
  Branches        211     215       +4
===========================================
+ Hits           1312    1320       +8
- Misses           55      59       +4
- Partials          7       9       +2

Impacted Files
Coverage Δ

src/malcolm/malcolmSocketHandler.js
100% <ø> (ø)
:arrow_up:

src/malcolm/malcolmHandlers/layoutHandler.js
100% <100%> (ø)
:arrow_up:

src/malcolm/reducer/attribute.reducer.js
95.18% <100%> (+0.05%)
:arrow_up:

src/malcolm/reducer/malcolmReducer.js
87.3% <50%> (-2.7%)
:arrow_down:

src/malcolm/middleware/malcolmRouting.js
88.88% <50%> (-11.12%)
:arrow_down:

src/malcolm/malcolmHandlers/attributeHandler.js
97.14% <87.5%> (+0.08%)
:arrow_up:

Continue to review full report at Codecov.

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


Chapters support in editor

Allow to view list of game chapters
Which chapter the current game state is in
Allow to change chapter to test script execution (debug hud perhaps)

Maybe this doesn't need to be a dedicated feature, since the chapter seems to be a game variable like any other (already visible and editable). Maybe I'm missing something?


Quest Definition and Setup

Quest Definition and Setup
Description: Develop a smart contract to enable an admin to create an "Event Quest" with specific parameters.
Depends on #19
Acceptance Criteria:

The contract must allow an admin to create a quest with the following parameters:

Event ID (unique identifier for the event)
Start and end dates
Number of required interactions (minimum three)
Reward details (either NFT or token)

Ensure that these parameters are stored securely in the contract.
Provide functions to access these parameters later.

Solidity Smart Contract:
// SPDX-License-Identifier: MIT

pragma solidity ^0.8.0;

contract EventAmbassadorQuest {

    address public admin;

    struct Quest {

        uint256 eventId;

        uint256 startDate;

        uint256 endDate;

        uint256 requiredInteractions;

        string rewardType; // "NFT" or "token"

    }

    mapping(uint256 => Quest) public quests;

    event QuestCreated(uint256 eventId, uint256 startDate, uint256 endDate, uint256 requiredInteractions, string rewardType);

    modifier onlyAdmin() {

        require(msg.sender == admin, "Only admin can perform this action");

        _;

    }

    constructor() {

        admin = msg.sender;

    }

    function createQuest(

        uint256 _eventId,

        uint256 _startDate,

        uint256 _endDate,

        uint256 _requiredInteractions,

        string memory _rewardType

    ) public onlyAdmin {

        require(_requiredInteractions >= 3, "Required interactions must be at least three");

        require(bytes(_rewardType).length > 0, "Reward type must be specified");

        quests[_eventId] = Quest({

            eventId: _eventId,

            startDate: _startDate,

            endDate: _endDate,

            requiredInteractions: _requiredInteractions,

            rewardType: _rewardType

        });

        emit QuestCreated(_eventId, _startDate, _endDate, _requiredInteractions, _rewardType);

    }

    function getQuest(uint256 _eventId) public view returns (Quest memory) {

        return quests[_eventId];

    }

}

Acceptance Criteria Validation:

[ ]  1. Quest Creation Function:

The createQuest function allows the admin to create a quest with the required parameters.
Validates that the number of required interactions is at least three.
Validates that the reward type is specified.

[ ] 2. Storage and Retrieval:

Quests are stored in the quests mapping with the eventId as the key.
The getQuest function allows retrieval of quest details by eventId.

[ ] 3. Admin Restriction:

The onlyAdmin modifier ensures that only the admin can create quests.

[ ] 4. Events:

The QuestCreated event is emitted upon the creation of a quest, providing transparency and a way to track quest creation.

This contract meets the specified requirements and ensures that the necessary parameters are both stored and retrievable, with appropriate validation and access control.

points: 1, 2, 3, 5, 8, 13, 21

Sponsor Creation worked well - confusion on whether or not I need to add in the Sponsor ID or if that will generate a number after submission.


(AzureCXP) Edits for MicrosoftDocs/azure-docs-powershell#1372

Referenced installation instructions for PowerShellGet

Docs Build status updates of commit a511edc:
:clock10: Full build: the average full build time is 24 min(s) 30 sec(s), this is based on the last 352 build(s) for this repository.

Docs Build status updates of commit a511edc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-conceptual/azps-3.8.0/install-az-ps.md
:warning:Warning
View (azps-3.8.0)
Details

docs-conceptual/azps-3.8.0/install-az-ps.md

Line 11: [Warning] Link 'https://docs.microsoft.com/en-us/powershell/scripting/gallery/installing-psget?view=powershell-7' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 5b664ec:
:clock10: Full build: the average full build time is 25 min(s) 9 sec(s), this is based on the last 354 build(s) for this repository.

Docs Build status updates of commit 5b664ec:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-3.8.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-3.8.0)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@mikefrobbins Noted, thank you for the edits and suggestions!


Could your sketch support iPad 12.9 template?

Agreed. This is a great resource, and thank you for creating it @jtholloran. All its missing is iPad support (and maybe tvOS, but mostly iPad) :)

Appreciate you attention on this. Thanks

We'd love that, too!

I think it is reasonable, since ipad screenshots are mandatory by apple as well

Yes pleaaaaase

???

A lot of people would appreciate it if you do this @jtholloran, as it's obligatory in the app store. and btw add a sponsor badge in your repo. Thanks.

Are iPad screenshots really required when submitting an app developed for iPhone only? Seems to be some confusion about that. I'm definitely confused since I haven't run into that issue. @alouanemed @cubissimo Can you point to some docs or explain further?
I'd like to add iPad support, but haven't had the time or personal need, since I primarily design iPhone apps — apps that are on the App Store and haven't had any developers come back saying they need iPad shots to submit.

Yes, I just submitted a new app yesterday and it is required to upload 3 screenshots for 2nd and 3rd gen iPad Pro each.
I spent a day looking for the 2nd generation iPad Pro mockup and generating iPad screenshots.
Thanks!

any updates?

This guy (https://vk.com/id144849788) added iPad and Watch devices, but it's in Russian. Maybe someone will be capable of merging his skins to this repo https://disk.yandex.ru/d/iZlsOBYqUW8RBg


nodeMCU does not output to the strip

Hi,
I set up the nodeMCU and python with anaconda on my PC. When I start the visualization.py it shows me an animation and the serial monitor tells me that it receives around 60FPS.
But the Strip does just stay white. When I restart it does not even turn on.
The Strip is connected to the RX port as described

same issue, could you solve it?

same problem here. found an fix?

same problem here. found an fix?

same issue, could you solve it?

I switched  to an other fork of this project https://github.com/not-matt/Systematic-LEDs works better than the original. he made a nice tutorial about it to. it also has way more features

Glad you like it!
On Thu, Oct 4, 2018, 7:44 AM RecLeKon<EMAIL_ADDRESS>wrote:

I switched to an other fork of this project
https://github.com/not-matt/Systematic-LEDs works better than the
original. he made a nice tutorial about it to. it also has way more features
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scottlawsonbc/audio-reactive-led-strip/issues/148#issuecomment-426903505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae5azHnVWMLRa5cWFPNM9p2tm5JsVphEks5uha5bgaJpZM4TxA14
.


Fix/model validation

Describe your changes
Model validation: add support for pd.Series as a datatype for X
Predict_proba functionality: for custom (non-Dummy) classifiers, we're going to allow users to "signal" to Lens that we should treat their predict and predict_proba functions as being sklearn-like. If the user adds a frameworks_like attribute (a list) to their custom classifier and pass that classifier as the model_like argument to ClassificationModel, we will check the contents of framework_like. If sklearn is in the attribute, we will take steps similar to existing framework checking and functionality updating. Note that multiple frameworks can be specified. For instance, a user might want to pass a pytorch model that supports both forward() (default pytorch behavior) and custom-implemented predict and predict_proba behavior a la sklearn. In this case, the user would set an attribute in their custom model frameworks_like = ['sklearn', 'pytorch']. Full pytorch support not yet implemented.
Issue ticket number and link
Zoom discussion
Known outstanding issues that are not fully accounted for
Full support of frameworks_like not yet implemented.
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I have built basic tests for new functionality (particularly new evaluators)
[ ] If new libraries have been added, I have checked that readthedocs API documentation is constructed correctly
[ ] Will this be part of a major product update? If yes, please write one phrase about this update.

Extra-mile Checklist

[ ] I have thought expansively about edge cases and written tests for them

@esherman-credo  I have this model that throws error on this branch.
The model is essentially an sklearn classification model that is wrapped to function based on a custom threshold (a very common scenario)
Is this PR envisioned to accommodate for it?
There is also this model which is a similar, but more complicated one, that is throwing the same error as well.
Feel free to run the notebooks for tests, etc. Thanks!


[Feature Request] Implement kotaemon to the AutoRAG run_web

Is your feature request related to a problem? Please describe.
kotaemon have a nice UI made with gradio for RAG
Why don't we implement it?
Describe the solution you'd like
Let's make kotaemon Runner or something like that.
https://github.com/Cinnamon/kotaemon/

This will resolve issue #493 and #635 as well

I already implement some of it as prototype at my repo.
https://github.com/vkehfdl1/AutoRAG-web-kotaemon


First NativeMenu item on Mac conflict between app name and header

Observed with 0.9.0-preview4, dotnetcore2.2 on Mac OS Mojave (10.14.6).
When application loads the first menu item is "dotnet". When I run a command from the menu like OpenFolderDialog.ShowAsync(...) and the dialog displays, the menu changes to match the header.
(If Application.Name is set, that is shown instead of "dotnet", but will still switch to whatever value is in the header as described below.)
Steps to reproduce
I started with dotnet new avalonia.mvvm and updated the generated code to reference 0.9.0-preview4 and fixed compiler errors due to that package update (such as adding using Avalonia.ReactiveUI to get UseReactiveUI extension).
Then added NativeMenu to MainWindow.xaml:
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:vm="clr-namespace:AvaloniaWorkshop.ViewModels;assembly=AvaloniaWorkshop"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
        x:Class="AvaloniaWorkshop.Views.MainWindow"
        Icon="/Assets/avalonia-logo.ico"
        Title="AvaloniaWorkshop">

    <Design.DataContext>
        <vm:MainWindowViewModel/>
    </Design.DataContext>

     <NativeMenu.Menu>
        <NativeMenu>
            <NativeMenuItem Header="SampleApplication">
                <NativeMenuItem.Menu>
                    <NativeMenu>
                        <NativeMenuItem Header="Quit" />
                    </NativeMenu>
                </NativeMenuItem.Menu>
            </NativeMenuItem>
            <NativeMenuItem Header="File">
                <NativeMenuItem.Menu>
                    <NativeMenu>
                        <NativeMenuItem Header="Open" Gesture="cmd+o" Command="{Binding OpenCommand}" />
                        <NativeMenuItemSeperator />
                        <NativeMenuItem Header="Quit" />
                    </NativeMenu>
                </NativeMenuItem.Menu>
            </NativeMenuItem>
        </NativeMenu>
    </NativeMenu.Menu>

    <TextBlock Text="{Binding Greeting}" HorizontalAlignment="Center" VerticalAlignment="Center"/>

</Window>

And updated MainViewModel.cs to add an OpenCommand:
using System;
using System.Reactive;
using System.Threading.Tasks;
using ReactiveUI;

namespace AvaloniaWorkshop.ViewModels
{
    public class MainWindowViewModel : ViewModelBase
    {
        public ReactiveCommand<Unit, string> OpenCommand { get; }

        public MainWindowViewModel(Func<Task<String>> openCommand) {
            OpenCommand = ReactiveCommand
                .CreateFromTask(openCommand, outputScheduler: RxApp.MainThreadScheduler);
        }

        public string Greeting => "Hello World!";
    }
}

Lastly, need to update Program.cs to inject command:
// In Program.cs:
private static void AppMain(Application app, string[] args)
{
    var window = new MainWindow();
    window.DataContext = new MainWindowViewModel(() => new OpenFolderDialog().ShowAsync(window));
    app.Run(window);
}

Now if I run the app, the menu displays with the first item "dotnet", and the second item "File". If I select File -> Open, the menu updates the first item to "SampleApplication" (to match the header). Once I close the folder picker, the first item reverts to "dotnet".

Adding the following to App.xaml fixes the renaming of the first item:
     <NativeMenu.Menu>
        <NativeMenu />
     </NativeMenu.Menu>

But when opening the folder picker, the native menu defined in MainWindow.xaml disappears.
This might be by-design as the primary window changes, in which case is there another way of binding commands in the menu to a view model?

This might be by-design as the primary window changes

Yes, this is basically the same as with Qt: menus are bound to windows and get removed on window deactivation. Which actually makes sense for modal dialogs, the app usually expect the thing to actually be modal.

Thanks for the info. 👍
Feel free to close this.


Use reset_num_produce!

Fixes the bug I mentioned in https://github.com/TuringLang/Turing.jl/issues/1115#issuecomment-586934847.

Thanks @devmotion for the fix!


Memory leak with circular reference in GDscript

Hi,
Godot reference counting mechanism doesn't support circular references. This is fine for simple construction (e.g. loading References) but given GDscript is build on this, you can write leaking program pretty easily:
func _ready():
	set_process(true)

class Leaker:
	var stuff = null
	var other = null
	func _init():
		# Dummy data to make the leak more visible
		self.stuff = []
		for x in range(1000):
			self.stuff.append(x)

	func connect(other):
		self.other = other

func _process(delta):
	var a = Leaker.new()
	var first = a
	for i in range(100):
		var b = Leaker.new()
		a.connect(b)
		a = b
	a.connect(first)  # Comment this line to remove the leak !

This is not a trouble for me (beside a circular dependency checker is complex to code and slow to run) but I think it's something users should be aware of.
I couldn't see any information about this behavior in the documentation so I think there should be a warning about this in GDscript more efficiently

I think there was something about this somewhere, but I can't remember
where.
I thought about making a circular reference checker, it shouldn't be that
difficult, but not that many users complained about it so far..
On Sat, Nov 5, 2016 at 5:32 AM, Emmanuel Leblond<EMAIL_ADDRESS>wrote:

Hi,
Godot reference counting mechanism doesn't support circular references.
This is fine for simple construction (e.g. loading References) but given
GDscript is build on this, you can write leaking program pretty easily:
func _ready():
set_process(true)
class Leaker:
var stuff = null
var other = null
func _init():
# Dummy data to make the leak more visible
self.stuff = []
for x in range(1000):
self.stuff.append(x)
func connect(other):
self.other = other
func _process(delta):
var a = Leaker.new()
var first = a
for i in range(100):
var b = Leaker.new()
a.connect(b)
a = b
a.connect(first)  # Comment this line to remove the leak !
This is not a trouble for me (beside a circular dependency checker is
complex to code and slow to run) but I think it's something users should be
aware of.
I couldn't see any information about this behavior in the documentation so
I think there should be a warning about this in GDscript more efficiently
http://docs.godotengine.org/en/stable/reference/gdscript_more_efficiently.html#pointers-referencing
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7038, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2z8V7M3ms4VZ2VriNfJfbZCoRNYCks5q7D8BgaJpZM4KqNGR
.

There's weakref() but not much info about it.

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

@Noshyaar  I've just reproduce the leak with Godot 3.0.2, so this issue is still valid

GDScript probably needs something to detect cycles and warn the user, but I don't think this is a bug.. rather an enhancement. If anyone wants to work on it, feel welcome.

Also, so far not happening for 3.1

I tried the reproduction code but it doesn't seem to leak.

I think you have to run it directly (not through the editor) so that the --verbose flag is honored, or enable verbose stdout in the project settings.
Here's the output for me running the project directly (truncated because it was spammy):
Godot Engine v3.4.beta.custom_build.cdbfa37f1 - https://godotengine.org
XInput: Refreshing devices.
XInput: No touch devices found.
Detecting GPUs, set DRI_PRIME in the environment to override GPU detection logic.
Found renderers:
Renderer 0: Mesa Intel(R) HD Graphics 630 (KBL GT2) with priority: 20
Renderer 1: AMD VEGAM (DRM 3.42.0, 5.14.9-desktop-3.mga9, LLVM 12.0.1) with priority: 30
Using renderer: AMD VEGAM (DRM 3.42.0, 5.14.9-desktop-3.mga9, LLVM 12.0.1)
Found discrete GPU, setting DRI_PRIME=1 to use it.
Note: Set DRI_PRIME=0 in the environment to disable Godot from using the discrete GPU.
Using GLES3 video driver
OpenGL ES 3.0 Renderer: AMD VEGAM (DRM 3.42.0, 5.14.9-desktop-3.mga9, LLVM 12.0.1)
OpenGL ES Batching: ON
	OPTIONS
	max_join_item_commands 16
	colored_vertex_format_threshold 0.25
	batch_buffer_size 16384
	light_scissor_area_threshold 1
	item_reordering_lookahead 4
	light_max_join_items 32
	single_rect_fallback False
	debug_flash False
	diagnose_frame False
PulseAudio: context other
PulseAudio: context other
PulseAudio: context other
PulseAudio: context ready
PulseAudio: Detecting channels for device: alsa_output.pci-0000_00_1f.3.analog-stereo
PulseAudio: detected 2 channels
PulseAudio: audio buffer frames: 512 calculated latency: 11ms
JoypadLinux: udev enabled and loaded successfully.

CORE API HASH:<PHONE_NUMBER>14722995
EDITOR API HASH:<PHONE_NUMBER>241295750
Loading resource: res://default_env.tres
Loaded builtin certs
Loading resource: res://Node2D.tscn
Loading resource: res://Node2D.gd
ERROR: Condition "_first != nullptr" is true.
   at: ~List (./core/self_list.h:108)
ERROR: Condition "_first != nullptr" is true.
   at: ~List (./core/self_list.h:108)
PulseAudio: context terminated
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object.cpp:2063)
Leaked instance: Reference:2093
Leaked instance: Reference:2035
Leaked instance: Reference:2121

... plenty more ...

Leaked instance: Reference:2092
Leaked instance: Reference:1976
Leaked instance: Reference:1713
Leaked instance: GDScript:1229 - Resource path:
Leaked instance: Reference:1698
Leaked instance: Reference:2213
Leaked instance: Reference:2003

... plenty more ...

Leaked instance: Reference:1997
Leaked instance: Reference:1490
Leaked instance: Reference:1316
Hint: Leaked instances typically happen when nodes are removed from the scene tree (with `remove_child()`) but not freed (with `free()` or `queue_free()`).
Orphan StringName: dconnect
Orphan StringName: Reference
Orphan StringName: other
Orphan StringName: GDScriptNativeClass
Orphan StringName: append
Orphan StringName: res://Node2D.gd
Orphan StringName: stuff
Orphan StringName: _init
Orphan StringName: GDScript
StringName: 9 unclaimed string names at exit.

Okay, I see the error with --verbose but not with verbose_stdout, which doesn't seem to be implemented on EditorRun (Another issue?).

Would be nice to test this again, after @adamscott's improvements 👀

@YuriSizov Unfortunately, I just tested and it still leaks. I'm investigating this.


Training and cpu inferencing

@Leedeng Hi there,

is sauvolanet able to inference using cpu-only
how to train sauvolanet

Hello,

how to train sauvolanet

I was able to build some wrappers and easy to use Configuration File for training the model.
Just play with the Config file and you're done.
Hope I can merge it with this Github later!
https://github.com/mohamadmansourx/SauvolaNet-Training

is sauvolanet able to inference using cpu-only

1- If you used my wrappers:
This can be done by simply setting use_gpu to False in the Config.yaml
2- If not:
I believe the easiest way is to set hide cuda devices before importing Tensorflow.
In other words, at the very beginning of your py file just write the below:
import os
os.environ['CUDA_VISIBLE_DEVICES']='-1' #This will hide Cuda devices from TF (incase you have GPU on your pc)
import tensorflow #tensorflow will now be running on your CPU only and you can load the model normally

@mohamadmansourX it seems that you have done an amazing job, thanks!!


Windows installer doesn't appear to work at all?

What is the issue?
After discovering that Ollama was not automatically updating, I ran the installer to upgrade it (per FAQ instructions). Now a 500 error is generated if I try to access it, and the only logs and config available don't show anything useful? Additionally, the ollama command is not available.

No additional info provided..
app.log
time=2024-11-01T01:44:12.158-06:00 level=INFO source=logging.go:50 msg="ollama app started"
time=2024-11-01T01:44:12.381-06:00 level=INFO source=store.go:96 msg="wrote store: C:\\Users\\username\\AppData\\Local\\Ollama\\config.json"
time=2024-11-01T01:44:12.395-06:00 level=INFO source=store.go:96 msg="wrote store: C:\\Users\\username\\AppData\\Local\\Ollama\\config.json"
time=2024-11-01T01:44:12.400-06:00 level=INFO source=server.go:176 msg="unable to connect to server"
time=2024-11-01T01:44:12.400-06:00 level=INFO source=server.go:135 msg="starting server..."
time=2024-11-01T01:44:12.715-06:00 level=INFO source=server.go:121 msg="started ollama server with pid 19228"
time=2024-11-01T01:44:12.715-06:00 level=INFO source=server.go:123 msg="ollama server logs C:\\Users\\username\\AppData\\Local\\Ollama\\server.log"

config.json
{"id":"833b6b29-adbe-422e-98ec-5c78824cc785","first-time-run":true}

server.log
Is an empty file.
OS
Windows
GPU
Nvidia
CPU
AMD
Ollama version
latest - I cannot say the exact version because it did not work

It seems that since I last looked at this project, the "Windows" version changed from using docker and WSL to run things to being its own thing separately? This perhaps explains why I wasn't getting updates, but it doesn't explain why the installer failed - since I had nothing else running at the time of install, and my previous install is working on an outdated version now that I've restarted it.
Would having multiple setups on the same machine like this be a reason the installer would fail? What is the difference under the hood now from how it worked before?

Switching from WSL to the Windows native desktop app might have some rough edges.  Please make sure to uninstall the WSL linux component, and since you seem to have gotten into a weird failure state, I'd suggest uninstalling the windows app as well, and then do a fresh install.  If that doesn't clear it up, let us know and we can further troubleshoot.

Considering I got the WSL setup updated and working again, I will not be trying those steps at this time. (I was hoping for a more specific path in where to find what went wrong.) I am certainly open to trying it in the future though - would it increase performance because I'm avoiding whatever overhead WSL introduces?
I assume it would be best to close this issue now and only revisit it if I have trouble while trying to follow those steps in the future. Thank you!
(Part of why I decided not to try uninstalling and reinstalling right now is because of how the installer just throws everything into random places without warning on C:/, although, it seems this was just patched in #6967? That makes me very happy to see, especially with how many closed issues exist complaining about that problem!)


Server stability in France

I'm having some stability issues with the server in France. I might need to resize it, or rebuild it from scratch.
This issue is to track any related notes to it.

@Tomatoide @TechComputerServiceDunkerque,
I'm going to have to setup a new server with more RAM. I think I can still keep the same ipv4 address, but the ipv6 will change unfortunately.

This is done now.
$ nslookup fr-dns1.bancuh.com
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Non-authoritative answer:
Name:	fr-dns1.bancuh.com
Address: <IP_ADDRESS>
Name:	fr-dns1.bancuh.com
Address: 2001:bc8:600:1810::1

ipv4 is the same. ipv6 had to change. I'll keep this ticket open for a day or so.

ipv6 looks the same as old one?

Hello, my adblock hosts stay the same?

ipv6 looks the same as old one?

Oops, I ran that command too early. I've updated that, and it should reflect the new IP.

Thank you, sorry I didn't see that you answered. I also changed my text.

Hello, my adblock hosts stay the same?
I saw thanks to Dns leak that you had put google back.
https://browserleaks.com/ip
It is also possible to change the Google dns on your server instead of this one? Thank you (a lot of french people don't
trust Google).
anycast.censurfridns.dk
<IP_ADDRESS>
2001:67c:28a4::
Anycast from multiple locations.
https://blog.uncensoreddns.org/

You are right. Thanks for catching that!
The servers that I setup has a default setting to use Google as forwarder. I have an override for that for the server in France. I forgot to add that back in when I recreated the server yesterday.
I'll update this now.

Thank you for your work

Hello, my adblock hosts stay the same?

Yes, all my servers use the same blocklist. Everytime we make an update to the list, each server should pull the latest version and restart.
Hopefully, with the added RAM, this France server will be able to auto-update as well, and not get stuck with the old list.

We will see ✌

Bancuh doesn't work well in connection sharing, for example when I share my data with my smartphone, I think I got the wrong dns, I didn't give you the right one
ns0.fdn.fr : <IP_ADDRESS> ou 2001:910:800::12
ns1.fdn.fr : <IP_ADDRESS> ou 2001:910:800::40

I don't have a network at all with the French dns, on the other hand with the singapore dns, everything is fine.

Bancuh doesn't work well in connection sharing, for example when I share my data with my smartphone, I think I got the wrong dns, I didn't give you the right one
ns0.fdn.fr : <IP_ADDRESS> ou 2001:910:800::12
ns1.fdn.fr : <IP_ADDRESS> ou 2001:910:800::40
Edit: 00h54 I'm still seeing cuts in the dns at the moment.

I don't have a network at all with the French dns, on the other hand with the singapore dns, everything is fine.
is it possible to have a secondary dns?

I've applied the new ip forwarders to the France DNS. That's the only thing that is different from the singapore dns servers. Let's try this ip change for now, maybe it will recover the service.
If the problem is significantly more when you use connection sharing, I suspect the problem is related to rate limit. I'm trying to relax the rate-limits for now here. Full file here.
Do try out these changes, and feedback to me.
If possible, I don't want to deploy another server in France, cause I'm working on a tight budget. I'll think about it though.

Thank you, everything works now

reminder to update bancuh website with updated dns 👍

Site to be unblocked
launches.appsflyer.com
fr.yahoo.com
7ba3f64df98de730df38846b54ecfbdf7f61f80f.cws.conviva.com
cws.conviva.com
app-measurement.com
measurement.com
Merci

Site to be unblocked
launches.appsflyer.com
fr.yahoo.com
7ba3f64df98de730df38846b54ecfbdf7f61f80f.cws.conviva.com
cws.conviva.com
app-measurement.com
measurement.com
Merci

Hi @TechComputerServiceDunkerque ,
From your list, it seems that some of the sites are dead. There's no need to whitelist them I think.
Some of the sites are actual user tracking services. I don't think we should whitelist them. When I try to visit them, my browser adblock extension throws all kinds of security warnings.
fr.yahoo.com, is a legitimate site. I checked just now and it is not blocked.

Site to be unblocked
launches.appsflyer.com
fr.yahoo.com
7ba3f64df98de730df38846b54ecfbdf7f61f80f.cws.conviva.com
cws.conviva.com
app-measurement.com
measurement.com
Merci

Hi @TechComputerServiceDunkerque ,
From your list, it seems that some of the sites are dead. There's no need to whitelist them I think.
Some of the sites are actual user tracking services. I don't think we should whitelist them. When I try to visit them, my browser adblock extension throws all kinds of security warnings.
fr.yahoo.com, is a legitimate site. I checked just now and it is not blocked.

Hi All. Thanks for your help in testing and ensuring the server in France work well.
Things seems to work fine, so I think we can close this issue. If you have other issues, please create a separate issue ticket.
Again, big thanks from me for your efforts!!!

Hi All. Thanks for your help in testing and ensuring the server in France work well.
Things seems to work fine, so I think we can close this issue. If you have other issues, please create a separate issue ticket.
Again, big thanks from me for your efforts!!!


I3dmToGltfConverter.cpp Wmaybe-unititialized Error

When I was building, I was getting a Wmaybe-uninitialized error. In the folder Desium3DTilesContent there's a file that is in the title above and at line 630 in the function CopyInstanceToBuffer that has three variables uninitialized. I replaced said functions with
void copyInstanceToBuffer(     const glm::dmat4& instanceTransform,     std::vector<std::byte>& bufferData,     size_t i) {   glm::dvec3 position(0.0);  // Initialize position with default values   glm::dvec3 scale(1.0);     // Initialize scale with default values   glm::dvec3 skew(0.0);   glm::dquat rotation;   glm::dvec4 perspective;   decompose(instanceTransform, scale, rotation, position, skew, perspective);   copyInstanceToBuffer(position, rotation, scale, bufferData, i); }
And the build compiled succesfully.

Hi,
Can you give some more details about the compilation environment? Were you compiling cesium-native as part of a Cesium plugin, or for an external project?
Depending on the compiler, and I'm assuming that this is gcc, -Wmaybe-uninitialized coupled with -Werror can give a lot of false positives, as it has in this case.

I'm on ubuntu 22.04 and gcc version 11.4.0

@MilesMena in general we can't guarantee that cesium-native compiles with extra warnings-as-errors enabled that we don't use ourselves. And I agree with Tim that there's no actual uninitialized usage here. So I'm going to close this issue.
I suggest you adjust your warning settings when building cesium-native.
Or, alternatively, consider opening a pull request that adds this warning to the set that we build with ourselves:
https://github.com/CesiumGS/cesium-native/blob/e0963bee920e0b70883ca698bb795b0757cf64db/CMakeLists.txt#L112
The PR should also fix any new warnings that pop up as a result. We'd likely be happy to merge such a PR.


What's the usage scenario of this tool?

Hi All,
As title suggested, I am wondering if this package can do the following:

Capture a stream of gRPC request and response through network packet capturing (assuming that the captured packets are purely from one gRPC connection between one server and one client).
Feed the stream into this trans-coder. Would this trans-coder actually produces the corresponding json request and response directly?
Or I need to extract the protocol buffer binary stream out of the gRPC stream and feed to this transcoder, which means that this transcoder does not handle the protocol metadata in gRPC?

This lib doesn't work on the IP packets.  It only works on L7 layer: Http body for JSON and gRPC data frames.


CurrencyConverter via Python

Description
Python Script that Automates Currency Conversion via use of https://fixer.io to get the access token that basically helps in conversion
Fixed #(issue_no)
#89
Type of change

[x] New feature (non-breaking change which adds functionality)

[ ] This change requires a documentation update

[x] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added screenshots(if any) that prove my fix is effective or that my feature works

@all-contributors please add vighneshdeepweb for code, doc

So is my PR will be counted for hacktoberfest 2020??

Yes sure


command line open start application -  open existing  instance if exist

I create simple command line for open my app (google calendar). Is there any argument for command line that will start existing instance of this app rather than starting another window?

Not sure if I fully understand your question.  But if you are trying to always use one instance of your app and not create a new instance every time you run it, try to rebuild your app using the --single-instance command line option.

thanks, that was what I wanted!


New version: Surrogates v1.1.2

Registering package: Surrogates
Repository: https://github.com/SciML/Surrogates.jl
Created by: @ludoro
Version: v1.1.2
Commit: 869c4a205e0206ea4e7bbbca19ce9eb9fe16ce4c
Git reference: master
Release notes:

Added AD-compatibility with Zygote and ForwardDiff for all possible surrogates.
Fixed minor bugs in radial basis and kriging that led to failure in speciale cases,
Added output explaining halting of optimization methods

Hello.
The travis PR actually passed, I just skipped the 1.1.0 because I messed up the release: I did not change the version in the Project.toml, could you merge this manually?
Thank you


Inconsistant Status calls using get_monitor_status

I drafted a quick and dirty python blob to test the ability to retrieve a monitor status but am getting very inconsistent results.
`import time
from uptime_kuma_api import UptimeKumaApi
from uptime_kuma_api.exceptions import UptimeKumaException
import argparse
UPTIME_KUMA_URL = 'http://<IP_ADDRESS>'
UPTIME_KUMA_USER = 'MYUSER'
UPTIME_KUMA_PASSWORD = 'MYPASSSWORD'
def poll_monitor_status(monitor_id):
api = UptimeKumaApi(UPTIME_KUMA_URL)
api.login(UPTIME_KUMA_USER, UPTIME_KUMA_PASSWORD)
try:
    monitor_status_response = api.get_monitor_status(monitor_id)
    monitor_status = monitor_status_response.name  # Correctly retrieve status
    print(f"Monitor ID {monitor_id} Status: {monitor_status}")

except UptimeKumaException as ex:
    print(f"An error occurred for monitor ID {monitor_id}: {ex}")

    # Detailed logging lines
    if hasattr(ex, 'response'):
        print("Error response content:", ex.response.content)
api.disconnect()
time.sleep(1)

if name == "main":
parser = argparse.ArgumentParser(description="Poll monitor status from Uptime Kuma API")
parser.add_argument("monitor_id", type=int, help="ID of the monitor to check")
args = parser.parse_args()
poll_monitor_status(args.monitor_id)

`
Below is me running the command a few times to show the inconsistency.
printer1@floorplan % python3 test.py 59 An error occurred for monitor ID 59: monitor does not exist printer1@floorplan % python3 test.py 59 An error occurred for monitor ID 59: monitor does not exist printer1@floorplan % python3 test.py 59 Monitor ID 59 Status: UP printer1@floorplan % python3 test.py 59 An error occurred for monitor ID 59: monitor does not exist
These commands were run within 5 seconds of each other, with no changes in network status , no changes of anything inside the script etc..
Any help troubleshooting would be greatly appreciated.

I am running into this as well.
Besides monitor does not exist I also get list indices must be integers or slices, not str.
Although, as a python novice, I am not 100% certain if this stems from my code or the underyling code

Line 542 has a very short sleep time that is called. If you increase that you get more results. I cant determine the order that the list gets populated.


resolve issues with atlassian semantic release

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => You can submit support request here, but we preffer to chat about it realtime at our [ngParty slack](https://ngparty.herokuapp.com/)

Current behavior
Current release is failing with errors as
info:    Executing getNpmConfig in packages/input
info:    Executing makeSrConfig in packages/input
info:    Executing pre in packages/input
ERR! commits The commit the last release of this package was derived from is not in the direct history of the "master" branch.
ERR! commits This means semantic-release can not extract the commits between now and then.
ERR! commits This is usually caused by force pushing, releasing from an unrelated branch, or using an already existing package name.
ERR! commits You can recover from this error by publishing manually or restoring the commit "499e2d7dac1cf1e9df96405244cddc78ee0382b9".
error:    message=Commit not in history, code=ENOTINHISTORY

and
info:    Executing getNpmConfig in packages/toggle
info:    Executing makeSrConfig in packages/toggle
info:    Executing pre in packages/toggle
ERR! commits The commit the last release of this package was derived from is not in the direct history of the "master" branch.
ERR! commits This means semantic-release can not extract the commits between now and then.
ERR! commits This is usually caused by force pushing, releasing from an unrelated branch, or using an already existing package name.
ERR! commits You can recover from this error by publishing manually or restoring the commit "9c105947cbfbfb18dfb7c08ab579527ae7b92a15".
error:    message=Commit not in history, code=ENOTINHISTORY

as you can see if you open line https://travis-ci.org/wc-catalogue/blaze-elements/jobs/204198870#L906
Expected behavior
lerna sematic release should work

I see two problems here

According to this issue semantic-release use npm gitHead which slightly undocumented property to determine which revision was used to publish particular npm package version. I we look for example at @blaze-elements/input we will get 1ec9488803ff8f1845b07a949908fde13bc84e63 which doesn't exists, I guess it wasn't properly pushed to master for some reason.

According to this code lerna-semantic-release is determining affected packages base on affect string in commit message which is used as standart in atlaskit repo.

Conclusion: Even if we fix first issue manually we still are not 100% sure it won't occur again as root cause is still yet to be discovered. Then we have to strictly use affect string which is in my opinion duplicate to scope. I have started investigate around custom solution from https://github.com/material-components/material-components-web/tree/master/scripts which is doing exactly what @Hotell proposed.

I will release manually following packages to resolve current issues
Malformed packages:

card
input
tag
toggle

all problematic packages were manually released

This seems to be still happening as seen in https://travis-ci.org/wc-catalogue/blaze-elements/builds/209739945#L905 for some strange reason tags are published, but appear in weird detached state which result command git branch --no-color --contains with empty output instead of master.
I will try to mirror approach of atlassian guys here and 🙏 for miracle, otherwise digging deep into git internals in inevitable 😂

After discussing with team I will prepare testing repo where we can test lerna-semantic-release functionality without risk of poisoning blaze-elements repo.

I'm very happy that everyone in the team reads my emails...
@davidrus @hopkins-tk


ENH: EMS with sklearn object?

@kaichogami there is a function mne.decoding.ems.compute_ems which could be implemented as an sklearn object to get a simple API.
Although the function looks awfully simple (it's a normalized differential response? Or I'm missing something).
@dengemann Do you have an opinion on this?

+1 for sklearn API object for EMS

Would be neat to have such an object. But priority is low at this point
On Mon, 18 Jul 2016 at 10:23, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

+1 for sklearn API object for EMS
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/3427#issuecomment-233266845,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fikRs0epqSOOO0c7y4tlqltd_-MX7ks5qWzf_gaJpZM4JOWa8
.

Do people use this much? (Just as an estimate for priorities.) My intuition would be like @dengemann 's

low priority I agree but maybe we should document it better to attract more
users of this...

Couldn't it be reconstructed by relying on e.g. sklearn's LOO cv? Building on standard tools rather than a custom implementation with a novel API?

yes probably...


Fixed Algolia build command

👋
This PR fixes the npm run algolia command for issue #37
Please review the layouts/list.algolia.json file. I reverted the file to how it originally was as your changes here seemed to be breaking it. To be honest, I'm not sure why you changed this file. Let me know if I'm missing on something that you did here.
The command hugo builds the list.algolia.json into the public folder and then npm run algolia uploads the generated search indices to Algolia from the public folder.

✅ By submitting this PR, I have verified the following

✅ Checked to see if a similar PR has already been opened 🤔
✅ Reviewed the contributing guidelines 🔍
✅ Added my name to the bottom of the list under the Credits section in the README.md with a link to my website or GitHub profile 👥

I changed that file because my editor was flagging errors but I think it's formatted fine now.
Thanks for making these changes, they LGTM! 👍

wonder if this works:
fixes #37

Yep. I've run the command and added it to the build command in our package.json. So now whenever the site rebuilds, it will update the listings on Algolia and our site.
A100 was one that was supposed to be removed and finally was due to this change.
Think Company was supposed to be added and finally was due to this change.


Ubuntu 16.04 x86_64

Platform: x86_64
OS version: Ubuntu 16.04
Branch: master
Preset: buildbot_linux_1604

@fiveze Email sent for additional information.

Can you also update "Current List of Platforms" in the README?

@shahmishal done. I've also specified Ubuntu version.

Job - https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-16.04/
Node - https://ci-external.swift.org/computer/ubuntu-16.04/
Thanks @fiveze!

@fiveze, Have you seen this issue?
https://bugs.swift.org/browse/SR-7688

This node is offline - https://ci-external.swift.org/computer/ubuntu-16.04/


Ensure Gauge ID is a String

If gauge ID is not actually a string then the upstream library freaks out. This adds a warning if it isn't a string and then casts it to one.
Fixes #42

Feel free to merge if you accept this.


[bug] Error after update to 0.3.1

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.3.1
Current Behavior
Show below error after update wage 0.3.1 and cause my application not able to start

Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

What bundler are you using? Can you provide a reproducible example.

what do you mean by which bundler? basically I just update to 0.3.1 and start my application and it show above error.

Are you using a tool, like Vite, Webpack, Parcel, Next.js, CRA, etc.?
A reproducible example will help us solve your issue faster and not waste time that could be spent on other things.

this is the error I'm facing now after did NPM UPDATE

Getting this in next with latest
react.development.js?dd75:1632 Uncaught TypeError: Cannot read properties of null (reading 'useEffect')
    at Object.useEffect (react.development.js?dd75:1632:1)
    at Provider (wagmi.esm.js?dce6:198:3)
    ```

Can you answer @tmm 's question? That will help solve your problem faster.

Are you using a tool, like Vite, Webpack, Parcel, Next.js, CRA, etc.?
A reproducible example will help us solve your issue faster and not waste time that could be spent on other things.

Im using Create React App.

@bryantoh – I don't seem to run into this issue when setting up a fresh Create React App project. Can you please upload a reproducible example? Thanks.

I created a new CRA project, and below is the error...

@tmm , @jxom , I tried to clean-install and using<EMAIL_ADDRESS>it show below warning:

when I started the application using "npm start", it throw below error. Hope it help.

Try upgrading your node version to 16

@bryantoh can you give @jxom and me access to the code or post a link to the source? Neither of us have been able to reproduce.

+1- also having this issue:
- react-scripts: 4.0.3 (Webpack 4)
- react: 17.0.2
- node: 14.18.1

Here's a minimal CRA example that works with wagmi. Check it out and compare the setup.
If you want us to look into the issue further, please provide a minimal example.

Here's a minimal CRA example that works with wagmi. Check it out and compare the setup.
If you want us to look into the issue further, please provide a minimal example.

I will give it a try. Did a quick comparison, I believe some dependencies are needed eg "buffer" and "events".

+1- also having this issue:
- react-scripts: 4.0.3 (Webpack 4)
- react: 17.0.2
- node: 14.18.1

Initially I was using the same setup, but having this issue. After upgrade node and react still same problem.

The issue is<EMAIL_ADDRESS>when I downgrade the minimal example that @tmm linked to version 4.0.3, I could reproduce the issue.

You may need to update to react-scripts@^5


USER_ID can not be empty

I'm using the version 2.0.0 of the Piwik SDK and trying to set the USER_ID of my Tracker as an empty String but it sets up automatically a random one.
This is my declaration:
public synchronized Tracker getInstance() {
    if (tracker == null) {
        TrackerConfig trackerConfig = new TrackerConfig("https://mywebpage.com", SITE_ID, "android-tracker");
        tracker = Piwik.getInstance(this).newTracker(trackerConfig);
    }
    tracker.setUserId("");
    tracker.getDefaultTrackMe().set(QueryParams.USER_ID, "");
    return tracker;
}

I've also tried to set it as empty inside the if condition but is not working either. Is there any way to do it?

Why are you trying to do that?
The documentation states:

User ID is any non-empty unique string identifying the user (such as an email address or an username).

You can either remove it, or set it to something, "nothing" is not supported:
https://github.com/matomo-org/piwik-sdk-android/blob/v2.0.0/piwik-sdk/src/main/java/org/piwik/sdk/TrackMe.java#L43

The reason is we have defined a non-logged users system which have an empty USER_ID. I guess we should define another system and set a standard USER_ID for those non-logged users.
You can close the issue then. Thank you very much!

Providing an empty user-id for all non-logged-in users, even it is accepted by the server, would aggregate all visits with empty "user id" as visits from the same user. So then in tracking you get many different logged-in users, but one huge "not-logged-in". I think this would make the statistics quite unusuable.
Being logged in or not should not change the user-id as it's still the same individual that might just have logged-in while using your app. It's more of a status, an attribute per user. I think I would do this via custom dimensions.
If you search for this, I'm sure this has come up before somewhere as this is not specific to apps and seems like something a lot of piwik/matomo users have thought about.


mount() does not preserve body when fetching through http server

A handler mounted with mount() gets an empty body when the handler is called by an HTTP request to the HTTP server (app.listen()).
I've tried the following combinations of calling a handler and only in the specific case that an HTTP request is handled by a mounted handler does this issue occur:

elysia handler
mounted handler

app.handle
✅
✅

app.fetch
✅
✅

http request
✅
❌

Here's a reproduction of this issue:
import { Elysia } from './src'

const handler = async (req: Request) => {
	return new Response(await req.text())
}

const app = new Elysia().mount('/mount', (req) => handler(req))

app.listen(3005)

const body = 'sucrose'

const options = {
	method: 'POST',
	body
}

const res = await fetch('http://localhost:3005/mount', options)
console.log(`Body: ${JSON.stringify(await res.text())}`)

app.stop()

Does anyone have an idea what could be going on?

Hi 👋
looks like it's a bug with Bun; the following doesn't work either:
const server = Bun.serve({
	port: 3005,
	async fetch(request) {
		const req = new Request(request) // this line breaks it
		return new Response(await req.text())
	}
})

const res = await fetch('http://localhost:3005', {
	method: 'POST',
	body: 'yay'
})

console.log(`Body: ${await res.text()}`)

server.stop()

Here is the position in the source code:
https://github.com/elysiajs/elysia/blob/2f732d799833953c8ff08f1a48b9ec58a14aa029/src/index.ts#L1714-L1717


dev-dependencies clean up

Organized dev-dependencies
Removed unused dev dependencies
Added some compilation conditionals to the turtle_teleop example to enable running cargo test on Windows

Codecov Report

Merging #162 (3b6d8fb) into master (c9a96f5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #162   +/-   ##
=======================================
  Coverage   70.39%   70.39%
=======================================
  Files          88       88
  Lines        8013     8013
=======================================
  Hits         5641     5641
  Misses       2372     2372

Continue to review full report at Codecov.

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


Support AAD authentication on NuGet.org

Based on current Microsoft ID recommendations:

It is highly recommended that all new services from Microsoft integrated with both Azure AD (work/school accounts) and MSA (personal accounts).

Right now, AAD only is used when admins log in.

Sounds the same as the planned 2FA work.
@shishirx34 , can we close as duplicate?

Yes duplicate of 2FA work.

What the duplicate issue?

https://github.com/NuGet/NuGetGallery/issues/3252


Installation issue

So I installed this, and... nothing. I thought a navigation was supposed to appear on left side of VS?
VS version: 2015 Enterprise Update 3.

Please try this new version that should fix compatibility
CodeNav_1.4.25_debug.vsix.zip

Oh, here it is! Thank you.