text:
Cannot build on iOS

As the title states, i cannot build my app using your library on iOS.
Ich do not use the lib on iOS at all, i just need it for android and cannot exclude it from iOS build.
Environment:

MacOS 10.15.7
Flutter 1.22.4
XCode 12.1
lib version 0.0.5+2

It throws the following error:
awesome_notifications-0.0.5+2/ios/Classes/lib/SwiftAwesomeNotificationsPlugin.swift:104:17: error: parameter of 'messaging(:didReceiveRegistrationToken:)' has different optionality than required by protocol 'MessagingDelegate'
public func messaging( messaging: Messaging, didReceiveRegistrationToken fcmToken: String) {
^
?
FirebaseMessaging.MessagingDelegate:2:19: note: requirement 'messaging(:didReceiveRegistrationToken:)' declared here
optional func messaging( messaging: Messaging, didReceiveRegistrationToken fcmToken: String?)
Suggesting the parameter must be optional. I made it optional and unwrapped inside your swift plugin and the build succeeded. Maybe you can give more insight.

Hey there.
Is this just a specific problem for me or does anyone else run into this.

I was unable to reproduce your error. What steps did you take to create your iOS app?
Try modifying the messaging method below in your local code:
https://github.com/rafaelsetragni/awesome_notifications/blob/b3e4da96f0302fef43f4c801d819dad044021332/ios/Classes/lib/SwiftAwesomeNotificationsPlugin.swift#L97

Hi. Thanks for your answer.
I was just normally building my app via "flutter build ios" and the error occured.
I already did modify the following code:
https://github.com/rafaelsetragni/awesome_notifications/blob/b3e4da96f0302fef43f4c801d819dad044021332/ios/Classes/lib/SwiftAwesomeNotificationsPlugin.swift#L104
public func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String) {
        print("Firebase registration token: \(fcmToken)")

        let dataDict:[String: String] = ["token": fcmToken]
        NotificationCenter.default.post(name: Notification.Name("FCMToken"), object: nil, userInfo: dataDict)
        // TODO: If necessary send token to application server.
        // Note: This callback is fired at each app startup and whenever a new token is generated.
}

to the following
public func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) {
        if let unwrapped = fcmToken {
            print("Firebase registration token: \(unwrapped)")
            let dataDict:[String: String] = ["token": unwrapped]
            NotificationCenter.default.post(name: Notification.Name("FCMToken"), object: nil, userInfo: dataDict)
            // TODO: If necessary send token to application server.
            // Note: This callback is fired at each app startup and whenever a new token is generated.
        }
}

But I just don't know why I had to do this.

You are rigth. My messaging method is deprecated, thats why you couldnt compile the final version in your app. I gonna update it.
Did you use another firebase services in your app? What version are they?

You are rigth. My messaging method is deprecated, thats why you couldnt compile the final version in your app. I gonna update it.
Did you use another firebase services in your app? What version are they?

I use FirebaseMessaging 7.1.0. That is the version installed by cocoapods.

Better! Do you wanna do a fork and send me this fix? Your name will be included as this project contributor.

Does this mean you experience the same problem after updating to the above version?
If so, I gladly provide the fix. Just don't want to break it for somebody else.

Im did not experienced this issue. For me, when i applyied your changes, XCode complains about the override operation not being possible due the messaging methos be different.
But send me your fork. This way i can merge your source and see every change that you did in your source and figure out whats goin on.

In fact, im merged your changes into my local files, and the messaging firebase method that you sent always complain about the override operation not being possible. In this way, i could not reproduce your error.
But in think im figuring out whats going on. You said that youre using FirebaseMessaging 7.1.0, but you want to say firebase_messaging: ^7.1.0 instead?
This plugin is not necessary to send push notifications using awesome_notifications. All that you need is inside the plugin and you only need to follow the steps extrictely inside Using Firebase Services (Optional) topic. Is not necessary to use any other plugin or implement any kotlin or java extra script.
Maybe firebase_messaging version is conflicting with my awesome_notifications firebase library, because firebase_messaging is using another library version, that overides mine.

Bingo! That was exactely what happened!

After update my libraries with pod update, i got your error!
On the newer Firebase version, the firebase team did a lot of changes, including change the method messaging without keep a deprecated version. So, all the sources bellow 7.1.0 will break. And they also changed a lot of things on Android sdk, as to deprecate the entire FirebaseInstance iil.
You got the newer firebase version after install a firebase plugin or update your pod files. Thats why you have those issues.
All the others awesome_notification developers gonna face the same after update the firebase package. So your change is totaly legit.
The problem that i facing is how to keep both methods working on same time to not injure the olders projects.
Can you cancel the current pull request to master branch and send the same pull request to update-firebase-sdk branch instead? Theres a lot changes to do on Android side as well.

Yeah that is exactly what I was hoping was not happening.
But now that we now the problem it is maybe fixable.
If you need anything else from me, don't hesitate to ask. Thanks for your effort :)

Ive merged your pull request and included a suport for older versions, as the code bellow. This way, both library versions are compatible with the core code being reusable:

    // For Firebase Messaging versions older than 7.0
    // https://github.com/rafaelsetragni/awesome_notifications/issues/39
    public func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String) {

        didReceiveRegistrationToken(messaging, fcmToken: fcmToken)
    }

    public func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) {

        if let unwrapped = fcmToken {
            didReceiveRegistrationToken(messaging, fcmToken: unwrapped)
        }
    }

    private func didReceiveRegistrationToken(_ messaging: Messaging, fcmToken: String){

        print("Firebase registration token: \(fcmToken)")
        let dataDict:[String: String] = ["token": fcmToken]
        NotificationCenter.default.post(name: Notification.Name("FCMToken"), object: nil, userInfo: dataDict)
    }

authors: derBeukatt rafaelsetragni


text:
Error with extra step in 0.7.0-beta.2

I'm trying to compile my app in IOS but I was having MissingImplementationException in AwesomeNotification.initialize.
I then noticed that this plugin as a beta version and in that, it requires a extra step for the IOS platform. However, I keep getting errors.
If I copy the following lines:
SwiftAwesomeNotificationsPlugin.setPluginRegistrantCallback { registry in
    SwiftAwesomeNotificationsPlugin.register(
      with: registry.registrar(forPlugin: "io.flutter.plugins.awesomenotifications.AwesomeNotificationsPlugin")!)
    FLTSharedPreferencesPlugin.register(
      with: registry.registrar(forPlugin: "io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin")!)
}

To AppDelegate.swift, the I get:
.../ios/Runner/AppDelegate.swift:11:5: error: cannot find 'SwiftAwesomeNotificationsPlugin' in scope
But according to the plugin guide: "And you can check how to correctly call each plugin opening the file GeneratedPluginRegistrant.m". And in my GeratedPluginRegistrant.m, I cannot find SwiftAwesomeNotificationsPlugin. But I do find AwesomeNotificationsPlugin.
So I rewrite the code to:
AwesomeNotificationsPlugin.setPluginRegistrantCallback { registry in
    AwesomeNotificationsPlugin.register(
      with: registry.registrar(forPlugin: "io.flutter.plugins.awesomenotifications.AwesomeNotificationsPlugin")!)
    FLTSharedPreferencesPlugin.register(
      with: registry.registrar(forPlugin: "io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin")!)
}

But I just get the same error, but updated:
.../ios/Runner/AppDelegate.swift:11:5: error: cannot find 'AwesomeNotificationsPlugin' in scope
Am I missing an import?

Fix
import shared_preferences_ios
import flutter_background_service_ios

Does above fix solved your problem? @TimeLord2010

It did. But I had to make some changes after:
import UIKit
import Flutter
import awesome_notifications
import shared_preferences_ios
import flutter_background_service_ios

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
  override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
  ) -> Bool {
    GeneratedPluginRegistrant.register(with: self)
    FlutterBackgroundServicePlugin.setPluginRegistrantCallback { registry in
        GeneratedPluginRegistrant.register(with: registry)
    }
    SwiftAwesomeNotificationsPlugin.setPluginRegistrantCallback { registry in
      SwiftAwesomeNotificationsPlugin.register(
        with: registry.registrar(forPlugin: "io.flutter.plugins.awesomenotifications.AwesomeNotificationsPlugin")!)
      FLTSharedPreferencesPlugin.register(
        with: registry.registrar(forPlugin: "io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin")!)
    }
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
  }
}

hi, suddenly out of nowhere, i can't build my apps on ios anymore, i suspect because of this step. here is the error logs

Swift Compiler Error (Xcode): Cannot find 'FLTSharedPreferencesPlugin' in scope
/Users/hazbiy/Data/Kerja/Freelance/Project/Risearrow/Flutter/ios/Runner/AppDelegate.swift:17:12

Encountered error while building for device.

I think it's because i remove shared preferences on my main package because i moved it on my secondary packages, and when i check on pubscpec.lock, i can't find any line stating that shared_preferences_ios is installed (meanwhile all other shared_preferences is installed, even for web and linux). does it mean i need to manually include it in my apps? i thought it would be included by the awesome notification package

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Transaction list fixes

Thank you for submitting this pull request :)
Fixes #1510
Short description
Definition of Done

[x] Steps to manually test the change have been documented
[x] Acceptance criteria are met
[x] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)
https://github.com/raiden-network/light-client/issues/1510

I thought that's how it was supposed to look? So all borders should be round?

I thought that's how it was supposed to look? So all borders should be round?

I think you might be right. The icon Sash gave me actually looks like that. I just viewed it in Illustrator.

Oh ok, it was a bit confusing to fix it because I didn't have access to the design
Thanks for the review 🙏

source: gharchive/pull-request

authors: nephix taleldayekh

repo: raiden-network/light-client

license: MIT


text:
Parallel execution of tests pytest -n 8 leaves partial gas measurement

Currently, when tests are run in parallel, gas measurements happen concurrently, and the resulting gas measurement file is corrupt.
Typically the corrupt file contains only a part of the measurements
{
    "SecretRegistry.registerSecret": 45757,
    "TokenNetwork.closeChannel": 111236,
    "TokenNetwork.openChannel": 97555,
    "TokenNetwork.setTotalDeposit": 44509,
    "TokenNetwork.settleChannel": 123338,
    "TokenNetwork.unlock 1 locks": 32128,
    "TokenNetwork.unlock 6 locks": 66029,
    "TokenNetwork.updateNonClosingBalanceProof": 93752
}

This issue keeps track of, at least, detecting this in the CI and block merge with incomplete gas measurements.

This was fixed in 12961bea391e74aacd9f1193bfd08d7a74d349e2

repo: raiden-network/raiden-contracts


text:
HDD Temperature Not Functioning

In the below screenshots you can see that the correct values are selected and that it is displaying temperature values.  However in Rainmeter the temperatures are not updating at all and seem to be stuck. The D: Storage is showing the temp for my C Drive, updating the values in SMV does not seem to do anything either.
Modern Gadgets Version: 1.4.1
HWInfo64 Version: 6.000-3620
https://i.imgur.com/YjHD1Pv.png
https://i.imgur.com/vwkFtTc.png
https://i.imgur.com/GDEQ63O.png

From the screenshots you sent me, it appears that you configured the values for the A: and B: disks, rather than C: and D:. Go back to the SMV and configure the temperatures for Disks C: and D:, and everything should work.

Yup, that seemed to work!  My bad I figured drive A and B were just going in order but it is the letter assigned to it.  Makes sense now that I'm thinking about it.

authors: XiCynx raiguard

repo: raiguard/ModernGadgets

license: mit

license_source: bigquery


text:
Heartbeat improvement

Hi @dhh,
From the server side, there's heartbeat sending from the server to all clients every 3 seconds. And I think this is a bit excessive and it may cause performance issue when dealing with finance or heavy load on the WebSocket.
From the client side, connection_monitor is sending the subscribe message every 4-8 seconds, this would increase the server load especially when all of the clients sending the subscribe message at the same time.
The heartbeat and connection_monitor are similar to reintroduce the asynchronous notification polling which WebSocket try to resolve. I reckon it could be improved by using socket.onclose event and socket.readyState for the reconnection instead of checking the stale connection.
socket.onclose = function() {
    consumer.connection.reopen() if socket.readyState === 3;
}

connection_monitor is sending the subscribe message every 4-8 seconds

Because your users change pages every 4-8 seconds?

We've found that those callbacks were not reliable across all situations
and browsers. The only reliable method we've found has been using a
heartbeat.
How is a heartbeat every 3s per connection a performance problem in your
case?
On Thu, Aug 6, 2015 at 7:48 PM, Javan Makhmali notifications@github.com
wrote:

connection_monitor is sending the subscribe message every 4-8 seconds
Because your users change pages every 4-8 seconds?
—
Reply to this email directly or view it on GitHub
https://github.com/rails/actioncable/issues/55#issuecomment-128457052.

Hi @javan,
not sure whether it's a bug or not. But if you

Clone the actioncable-exmaple and https://github.com/leckylao/em-websocket-example
Change actioncable-example/app/assets/javascripts/channels/index.coffee to point to ws://localhost:3001
Run actioncable-example/ rails s as client and run em-websocket-example/ ruby app.rb as server

Then you will see "Received: {"command":"subscribe","identifier":"{"channel":"CommentsChannel"}"}" every 4-8 seconds, which I think it's due to connection_monitor that reopening the connection.

Thanks @dhh for the explanation.

How is a heartbeat every 3s per connection a performance problem in your case?

Some metrics I found:

https://mrotaru.wordpress.com/2013/06/20/12-million-concurrent-connections-with-migratorydata-websocket-server/

In this benchmark scenario, MigratoryData scales up to 12 million concurrent users from a single Dell PowerEdge R610 server while pushing up to 1.015 Gbps live data (each user receives a 512-byte message every minute).
Result in 12m, Average latency 268 milliseconds, Maximum latency 2024 milliseconds, Network Utilization 1.015 Gbps.

http://colobu.com/2015/05/22/implement-C1000K-servers-by-spray-netty-undertow-and-node-js/ Sorry about it's in Chinese, opens in Chrome should translate it.

Netty Server - To all 1.2 million per minute websocket send a message, the message content for the current time server. Send display single-threaded send, the server sends finished about 1.2 million total time 15 seconds.
Spray Server - To all 1.2 million per minute websocket send a message, the message content for the current time server. High CPU usage, send quickly, bandwidth of up to 46M. After a mass takes about 8 seconds.
Undertow - To all 1.2 million per minute websocket send a message, the message content for the current time server. Mass takes about 15 seconds to play again.

Heartbeat would create similar load to the server and the bandwidth, which I think it would cause a performance issue on large concurrent connections.

I think you're going to be disappointed if you actually try to do any Ruby
work in these channels and expect that level of performance :). The
heartbeat is just a single piece of text data that requires nothing to
generate. Actual apps will be doing actual things in these channels that
are far slower than what a heartbeat overhead will be.
In any case, I haven't found it to be optional. If you can't reliably tell
when the connection has been cut, then the app might be fast, but it won't
work well.
On Thu, Aug 6, 2015 at 7:58 PM, Lecky Lao notifications@github.com wrote:

Thanks @dhh https://github.com/dhh for the explanation.
How is a heartbeat every 3s per connection a performance problem in your
case?
Some metrics I found:

https://mrotaru.wordpress.com/2013/06/20/12-million-concurrent-connections-with-migratorydata-websocket-server/
In this benchmark scenario, MigratoryData scales up to 12 million
concurrent users from a single Dell PowerEdge R610 server while pushing up
to 1.015 Gbps live data (each user receives a 512-byte message every
minute).
Result in 12m, Average latency 268 milliseconds, Maximum latency 2024
milliseconds, Network Utilization 1.015 Gbps.

http://colobu.com/2015/05/22/implement-C1000K-servers-by-spray-netty-undertow-and-node-js/
Sorry about it's in Chinese, opens in Chrome should translate it.
Netty Server - To all 1.2 million per minute websocket send a message,
the message content for the current time server. Send display
single-threaded send, the server sends finished about 1.2 million total
time 15 seconds.
Spray Server - To all 1.2 million per minute websocket send a message,
the message content for the current time server. High CPU usage, send
quickly, bandwidth of up to 46M. After a mass takes about 8 seconds.
Undertow - To all 1.2 million per minute websocket send a message, the
message content for the current time server. Mass takes about 15 seconds to
play again.
Heartbeat would create similar load to the server and the bandwidth, which
I think it would cause a performance issue on large concurrent connections.
—
Reply to this email directly or view it on GitHub
https://github.com/rails/actioncable/issues/55#issuecomment-128551949.

I think you're going to be disappointed if you actually try to do any Ruby
work in these channels and expect that level of performance :)

Nah, those just some metrics I found that can better show the impact. Another thought, I don't think they implements something like heartbeat but can still achieve stability on that level :blush:

The heartbeat is just a single piece of text data that requires nothing to
generate. Actual apps will be doing actual things in these channels that
are far slower than what a heartbeat overhead will be.

Most of the case WebSocket are being use as notification which only happens when it occurs. In this case, I think heartbeat is generating more traffics than the actual jobs.

In any case, I haven't found it to be optional. If you can't reliably tell
when the connection has been cut, then the app might be fast, but it won't
work well.

In this case, how about moving heartbeat and connection_monitor into an optional configuration. So that it doesn't enable by default. If people facing trouble with the connection then they can enable it.

Optimizing for correctness out the box over peak performance seems like a better trade-off to me. If someone actually hits a point in a real application where heartbeat traffic proves to be an issue, we can consider offering a way to turn off heartbeats. Thanks for your consideration and I look forward to hearing about your Action Cable deployment!

On Aug 9, 2015, at 18:00, Lecky Lao notifications@github.com wrote:
I think you're going to be disappointed if you actually try to do any Ruby
work in these channels and expect that level of performance :)
Nah, those just some metrics I found that can better show the impact. Another thought, I don't think they implements something like heartbeat but can still achieve stability on that level
The heartbeat is just a single piece of text data that requires nothing to
generate. Actual apps will be doing actual things in these channels that
are far slower than what a heartbeat overhead will be.
Most of the case WebSocket are being use as notification which only happens when it occurs. In this case, I think heartbeat is generating more traffics than the actual jobs.
In any case, I haven't found it to be optional. If you can't reliably tell
when the connection has been cut, then the app might be fast, but it won't
work well.
In this case, how about moving heartbeat and connection_monitor into an optional configuration. So that it doesn't enable by default. If people facing trouble with the connection then they can enable it.
—
Reply to this email directly or view it on GitHub.

We've found that those callbacks were not reliable across all situations and browsers

In order to further understand the issue, could you provide an example/demo or explain more about the issue please? How is it not reliable? Thank you.
http://caniuse.com/#search=websocket shows WebScoket is now 87.23% support that maybe the issue should be and has been resolved natively.

This was in testing across a variety of browsers, restore situations, and
mobile scenarios. Don't have a test suite available for reproduction. Would
be nice to have, but it's unlikely that we're going to invest any time into
this, given that we have a working solution. All this testing was done in
the last 3-4 months, though. Feel free to work on such a suite if you'd
like to advance this.
On Sunday, August 9, 2015, Lecky Lao notifications@github.com wrote:

We've found that those callbacks were not reliable across all situations
and browsers
In order to further understand the issue, could you provide an
example/demo or explain more about the issue please? How is it not
reliable? Thank you.
http://caniuse.com/#search=websocket shows WebScoket is now 87.23%
support that maybe the issue should be and has been resolved natively.
—
Reply to this email directly or view it on GitHub
https://github.com/rails/actioncable/issues/55#issuecomment-129262433.

authors: dhh javan leckylao

repo: rails/actioncable


text:
Double request

Hi!
I have a strange problem: when i navigate by clicking link between some pages turbolinks processed double request (FF,Safari, Сhrome). It occur only on two pages.

When i tried debug I found strange behavior: method processResponse() return valid doc inside them but to doc variable inside fetchReplacement() method was assigned 'undefined'

When I remove //=reuire all my scripts this problem still exists.
When I remove //=require turbolinks problem solved
Please fix this broblem. I have no clue why processResponse() return 'undefined' when inside this metod doc is valid.

Solved.
It cause because this two page has different templates with different assets.
When add  data-no-turbolink to link problem is gone.

repo: rails/turbolinks


text:
[bug] wallet_addEthereumChain or useSwitchChain on Rainbow Wallet not working

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
2.0.0
wagmi Version
2.5.6
Current Behavior
I already add a custom chain to getDefaultConfig

When I used switchChain from useSwitchChain wagmi for Rainbow wallet to switch to this chain, error occured like this:

When I used switchChain for other wallets like MetaMask, it worked, but rainbow didn't

When I tried using wallet_addEthereumChain to add this chain to Rainbow wallet, though I approved the addition of this chain, the error occured. I checked Rainbow wallet networks, this custom chain is already added but error showed:

Expected Behavior
When I used switchChain from useSwitchChain wagmi for Rainbow wallet to switch to a custom chain, it should add the custom chain to RainBow wallet and switch to it
If I use wallet_addEthereumChain, Rainbow wallet should add the chain and not show any error
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

@kingnight153 Could you please tell what chain you're switching to ?
Also would be super helpful if you can show your RainbowKit and Wagmi configuration setup 🙏

Here is the chain info: https://chainlist.org/?search=carbon

Yeah so that's an unsupported network from rainbow wallet. We work on improving the custom network so hopefully should be fixed soon. What you can do now is add the network manually and try to switch to the chain.

@kingnight153 Thanks for reporting. Bumping this to our browser-extension repo to further investigate

authors: DanielSinclair KosmosKey kingnight153

repo: rainbow-me/rainbowkit


text:
🛑 RiotSkin4CN-Download is down

In bac859d, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in f5d1eb9.


text:
Canvas upon player control

The slideshow-recorder.js plugin puts a new canvas ontop of the player control of reveal.js. The plugin has to be updated if reveal.js changes the way of drawing the player control.

Redesigned plugin to use default audio player and not auto sliding (commit 8b5fa5dc12)


text:
🛑 Raju Prasad is down

In 7bc3934, Raju Prasad (https://www.rajuprasad.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Raju Prasad is back up in 5635478 after 11 minutes.

repo: rajuprasad-dev/upptime-monitor


text:
without method doesn't use equals like it says in the documentation

I'm on version 0.21.
While I'm trying to use without function to remove exact strings from a strings array, some items are being removed (mistakenly?) due to usage of flip+contains methods.
Example:
R.without("ab", ["a","ab"])
// output: []

I would expect that the output would be ["a"] because it's a completely different item (although it is being contained by "ab" string)
You can run this code here

You have a type error:
without('ab', ['a', 'ab']);
// ! TypeError: Invalid value
//
//   without :: Array a -> Array a -> Array a
//              ^^^^^^^
//                 1
//
//   1)  "ab" :: String
//
//   The value at position 1 is not a member of ‘Array a’.

Correct usage:
without(['ab'], ['a', 'ab']);
// => ['a']

See #1912.

authors: davidchambers portons

repo: ramda/ramda


text:
#1417: Added dispatchables to docstrings

See #1417
Right now it is undocumented behaviour for some functions that they actually dispatch to a method. This PR adds a sentence to the docstrings that this dispatching is happening.

:deciduous_tree:

Can a native English speaker explain why not:

Dispatches to the takeWhile method of the second argument, if present

Can a native English speaker explain why not:

Dispatches to the takeWhile method of the second argument, if present

I like your version better, @raine! What do you think, @branneman?

Updated!

One of my commits snuck into your branch. Could you remove it?

Yeah, the squashing went wrong somehow. Gimme a minute.

Ugh. Think it's ok now. Is it?

Looks good! Merging.

authors: branneman davidchambers raine


text:
feat: add lowerFirst string

Converts the first character of a string to lowercase.

IMHO: It looks too specific to add this to the library.

IMHO: It looks too specific to add this to the library.

Agreed.  I think this comment on another recent PR is relevant:
https://github.com/ramda/ramda/pull/3488#issuecomment-2335287734

authors: CrossEye nhannt201 yurkimus


text:
Add packages

Adding packages while I tried to get OdroidC2 working locally. Sadly I don't get eth0 after boot (altought, I can see u-boot trying to get an IP )  so I cannot test upgrades, resets and the full cOS featureset. I'm suspecting kernel, but requires quite some time to experiment.  This change adds firmware packages, firmware and dtbs to the example image
Another approach would be to test with the u-boot and old kernel, but would be suboptimal to release with those ( for the records, here is a spec that build the Odroid kernel https://github.com/rancher-sandbox/cOS-toolkit/commit/c31ebbd1ac151883b49a74fbf90955c38841eb3f).
Also, this PR adds packages to the toolchain image in order to run the arm image script successfully. For reference, that's where I was experimenting with : https://github.com/mudler/cos-embedded-images/

shouldn't affect CI, and OdroidC2 images are built only on master.. merging!

repo: rancher-sandbox/cOS-toolkit


text:
default service_event for ipsec to up if global flag is true

https://github.com/rancher/rancher/issues/14668

LGTM. TF is unrelated

repo: rancher/cattle


text:
Bug fixes

Cleanup instance from planner on its removal

When instance with missing dependencies gets removed up by deployment planner, we should remove it from the planner's list of instances. Otherwise it would participate in further deployment, and further down will hit the timeout waiting for this instance to hit valid state (Running/Stopped, etc)

Don't schedule service config.update on service in updating-active/activating state. Reconcile process invoked by update/activate operation, can result in some instances being stopped/destroyed. And stop/destroy processes have config.upgrade hooks resulting in subsequent reconcile requests.

At the end of every activate/update process, we double check that the reconcile have been finished successfully, and if not - the process gets rescheduled.
This 2 fixes above are supposed to fix the bugs related to service reconcile slowness, like:
https://github.com/rancher/rancher/issues/2044

Validate service selector on instance.restore

https://github.com/rancher/rancher/issues/2338

I feel like you need better PR titles.  More uplifting like "Vast improvement in functional correctness"

@ibuildthecloud :) will improve the naming in the future PRs


text:
Unable to Deactivate multiple Cluster Drivers and Node Drivers

Setup

Rancher version: v2.7-head (5df9701)
Browser type & version: Firefox

Describe the bug

Nothing happens when attempting to deactivate Cluster Drivers or Node Drivers.
To Reproduce

The issue applies to both Cluster Drivers and Node Drivers

Navigate to Cluster Management => Drivers => Cluster/Node Drivers
Select all active drivers
Click Deactivate

Result
Nothing happens, no error in console.
Expected Result

Confirmation dialog is shown, positive selection results in Cluster/Node drivers becoming deactivated.
Additional context

This looks to be an issue with the confirmation dialog.
This only happens when attempting to delete multiple cluster/node drivers.
Holding ctrl before to skip the confirmation dialog while clicking delete will perform the action as expected.

@rak-phillip, can you update this ticket to include both Cluster Drivers and Node Drivers so that they are both fixed and tested?

@jameson-mcghee I updated to call out both cluster & node drivers

During testing on v2.7-head (Commit ID: e54432e) I was able to verify that the confirmation prompt is now being generated when attempting to Deactivate multiple Cluster Drivers or Node Drivers, and users are able to successfully Deactivate multiple Cluster Drivers or Node Drivers. Therefore I am closing this ticket as Done.
v2.7-head (Commit ID: e54432e):
Cluster Drivers:

Node Drivers:

authors: jameson-mcghee rak-phillip

repo: rancher/dashboard


text:
Remaining shell items for Elemental in 2.7.0

Adds the remaining shell changes, which are completely isolated from any reference to Elemental, in 2.7.0

Codecov Report
Base: 36.86% // Head: 36.87% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (ef6a419) compared to base (316889a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #7168   +/-   ##
=======================================
  Coverage   36.86%   36.87%
=======================================
  Files         986      986
  Lines       17633    17633
  Branches     4541     4541
=======================================
+ Hits         6501     6502    +1
+ Misses      11132    11131    -1

Flag
Coverage Δ

e2e
47.41% <ø> (+<0.01%)
:arrow_up:

merged
36.87% <ø> (+<0.01%)
:arrow_up:

unit
5.21% <ø> (ø)

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

Impacted Files
Coverage Δ

shell/components/GrowlManager.vue
0.00% <ø> (ø)

shell/components/Import.vue
0.00% <ø> (ø)

shell/components/form/MatchExpressions.vue
100.00% <ø> (ø)

shell/detail/provisioning.cattle.io.cluster.vue
0.00% <ø> (ø)

...dit/provisioning.cattle.io.cluster/MachinePool.vue
0.00% <ø> (ø)

shell/plugins/steve/steve-class.js
33.33% <0.00%> (-16.67%)
:arrow_down:

shell/utils/socket.js
48.52% <0.00%> (-12.75%)
:arrow_down:

shell/store/growl.js
23.33% <0.00%> (-3.34%)
:arrow_down:

shell/plugins/steve/subscribe.js
65.93% <0.00%> (-1.93%)
:arrow_down:

shell/models/provisioning.cattle.io.cluster.js
63.72% <0.00%> (-0.32%)
:arrow_down:

... and 9 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


text:
Missing fields when create a storageClass

rancher/server:master 03/14
allowVolumeExpansion and parameters of storageClass are not populated in rancher API.
UI sent the allowVolumeExpansion and parameters to backend for creating a storageClass.
But rancher server doesn't populate them.

The name is the ID so it's not going to be updateable.  Disable the field in edit

parameters is present in lastet master.
I can't see allowVolumeExpansion field in the UI, and @loganhz found the code related to allowVolumeExpansion is commented. @vincent99  do we still need this field?

As far as I remember volume expansion is alpha and off by default and there's no obvious way to tell if it's on to show the option, so I commented it out.

Version - 2.0 master 3/29
Verified fixed

Are there plans to add this option?

authors: loganhz vincent99 walkafwalka zionwu

repo: rancher/rancher


text:
Unable to add Ingress when removing second rule

Rancher versions: 2.0
Steps to Reproduce:
Add Ingress
Fill out all fields for first rule (Request Host, Path, Target, Port)
Add second rule.
Remove second rule.
Click Save.
Other information:
For some reason this only occurs if there is any information in the path field. If that value is empty, I am unable to save new rule after performing the listed steps.
Results:

Unable to save new rule. Error message states port is still required.

Version - 2.0 master 4/11
Verified fixed

authors: adingilloRancher tfiduccia


text:
The port that I exposed was also able to visit at the beginning

Rancher versions:
rancher/rancher:v2.0.8
rancher/rancher-agent:v2.0.8
**Docker version: **
Client:
Version:      17.03.2-ce
API version:  1.27
Go version:   go1.7.5
Git commit:   f5ec1e2
Built:        Tue Jun 27 02:21:36 2017
OS/Arch:      linux/amd64
Server:
Version:      17.03.2-ce
API version:  1.27 (minimum version 1.12)
Go version:   go1.7.5
Git commit:   f5ec1e2
Built:        Tue Jun 27 02:21:36 2017
OS/Arch:      linux/amd64
Experimental: false
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
3.10.0-514.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
VirtualBox
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:

The port that I exposed was also able to visit at the beginning.  All other namespace are normal.

Might be the same as https://github.com/rancher/rancher/issues/15372 ?
When you can access your port after you have deleted the network policy in your namespace, then it is the same issue, I guess.

Then how can we solve this problem? Our situation is the same.

Can you try it in 2.1.1, please?
If you can reproduce it, can you provide the reproduce steps and the logs, please?

authors: PeterZhai00 loganhz sebastiansirch


text:
Ensure Rancher system pods are not killed by kubelet eviction manager

What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Steps to reproduce (least amount of steps as possible):
Starve the free space in the root filesystem on a node that runs system-level pods (e.g. ingress-controller, pipeline jenkins or minio, prometheus, etc) by allocating disk space until kubelet's hard eviction threshold is crossed (by default nodefs.available<10%).
E.g. Create a large file with $ dd bs=1M if=/dev/zero of=/bigfile.tmp count=...
Result:
System-level pods are evicted/killed even before user pods (e.g. nginx-ingress-controller, Pipeline's Minio or Jenkins) resulting in service disruption (ingress) or data loss (pipeline build logs).
Warning   Evicted Container nginx-ingress-controller was using 252Ki, which exceeds its request of 0.
The node was low on resource: ephemeral-storage.
Killing container with id docker://nginx-ingress-controller:Need to kill Pod nginx-ingress-controller-r7q7s.156f4e7f716145fe

Reason:  Kubelet might evict a pod from its node when the node’s ephemeral storage is exhausted. Since these system-level pods have no resource requests/limit specified for ephemeral storage they are targeted first for eviction.
Expected Result:
System-level pods should never be killed/evicted by kubelet when resources are starved on a node or at least they should be selected for eviction with lower priority than user pods.

The kubelet ranks Pods for eviction first by whether or not their usage of the starved resource exceeds requests, then by Priority, and then by the consumption of the starved compute resource relative to the Pods’ scheduling requests.
(...)
Guaranteed pods and Burstable pods whose usage is beneath requests are evicted last. Guaranteed Pods are guaranteed only when requests and limits are specified for all the containers and they are equal. Such pods are guaranteed to never be evicted because of another Pod’s resource consumption.
source

In general, it is strongly recommended that DaemonSet not create BestEffort Pods to avoid being identified as a candidate Pod for eviction. Instead DaemonSet should ideally launch Guaranteed Pods.
source

Solutions that should be explored to address this:

Configure the pods of system-level services such as they are assigned a QOS class of Guaranteed and thus "guaranteed to never be evicted because of another Pod’s resource consumption." This would imho require to specify the following requests/limits for the pods:

spec.containers[].resources.limits.memory
spec.containers[].resources.requests.memory
spec.containers[].resources.limits.ephemeral-storage
spec.containers[].resources.requests.ephemeral-storage

Mark these pods as critical so they are protected from eviction: https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/

Environment information

Rancher version 2.1.3
Kubernetes version v1.11.3

Is there any update on this? I think I'm having the same issue.
I'm getting such error for the cattle-system pods

The node was low on resource: ephemeral-storage. Container nginx-ingress-controller was using 56Ki, which exceeds its request of 0.
The node was low on resource: ephemeral-storage. Container agent was using 60Ki, which exceeds its request of 0.


text:
[RFE] vSphere node driver - Need option to set 'numCoresPerSocket' in node template

What kind of request is this:
Feature request
Description
As of now, we can set the number of CPUs while defining the node template
But in some cases, the Cores Per Socket needs to be tuned (details are in the below blog post)
https://blogs.vmware.com/performance/2017/03/virtual-machine-vcpu-and-vnuma-rightsizing-rules-of-thumb.html
The go library provided by VMware has the option to change this parameter.
govc vm.change -vm master-01 -e cpuid.coresPerSocket=1

gz#14317

Hello,
I also have the same need.
Strange that few people are interested in this subject which would allow a better use of virtualization.
Someone would have a tip?

authors: Eric-TAS ansilh


text:
Import cluster command - Bug when more than first apply

Rancher Server Setup

Rancher version: 2.6.1
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): EKS 1.20

Information about the Cluster

Kubernetes version: EKS version 1.21
Cluster Type (Local/Downstream): downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): imported
NB It's a simple Generic cluster import and not managed type EKS import

Describe the bug

The cluster import command cannot be applied more than one time. So no more idempotent as should be as a kubernetes deployment.
To Reproduce

Step 1) EKS Cluster creation OK
Step 2) Rancher Cluster creation using Generic Cluster Type OK
Step 3) Execute the import command : OK
kubectl apply -f https://rancher-instance.com/v3/import/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj.yaml
and the imported cluster is well configured in Rancher
Step 4) Re-execute the import command: NOK
kubectl apply -f https://rancher-instance.com/v3/import/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj.yaml
clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver unchanged
clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master unchanged
namespace/cattle-system unchanged
serviceaccount/cattle unchanged
clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding unchanged
secret/cattle-credentials-2735ae9 unchanged
clusterrole.rbac.authorization.k8s.io/cattle-admin unchanged
deployment.apps/cattle-cluster-agent configured
service/cattle-cluster-agent unchanged

If the import command is applied a second time, the imported cluster is active, but can't explore anymore the cluster within Rancher:

As seen in previous command the cattle-cluster-agent is reconfigured and perhaps this is what causing the problem. But here we have a problem as the import command is not idempotent.
Result
Impossible to explore the cluster anymore
Expected Result

The cluster should stay accessible via Rancher

Still valid

Still valid


text:
[BUG] rancher-monitoring ignoreNamespaceSelectors has wrong default value

The value of prometheus.prometheusSpec.ignoreNamespaceSelectors was set to "true" by accident during an old rebase. This diverges from upstream's default behavior seemingly for no special reason so it must be changed back to "false".
Additional context
SURE-9374

The bug related to the accidental setting of prometheus.prometheusSpec.ignoreNamespaceSelectors to true has been verified as resolved. After conducting tests on an RKE2 cluster, I can confirm that the value has been correctly reverted to false, aligning with upstream defaults.
Details:

Rancher Version: v2.10-head
Cluster Version: v1.31.3-rc1+rke2r1
Monitoring Chart Version: 105.1.1-rc.1+up61.3.2

The attached screenshot verifies the corrected configuration. The cluster and monitoring behavior are now consistent with the expected standards, ensuring no deviations from the upstream specifications.

authors: deepakpunia-suse jbiers


text:
Enhancement Support CPU Quota and CPU period from compose/UI

Cattle doesn't support cpu_quota and cpu_period from compose. We need to add these to our launch configs.
It looks like libcompose is already able to support CPUQuota, it doesn't make it to the host though.

Closing in favor of the PRs that will allow us to support the missing cattle fields:
Cattle Changes: https://github.com/rancher/rancher/issues/4708
Rancher-compose: https://github.com/rancher/rancher/issues/6280
Exporting yml: https://github.com/rancher/rancher/issues/6281
UI: https://github.com/rancher/rancher/issues/6282

authors: cloudnautique deniseschannon


text:
Port etcd-operator to Rancher

Port CoreOS etcd-operator to Rancher orchestration platform. This will enable fully autonomous etcd clusters that self-heal, even in disaster situations such as majority member failure.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.

authors: LLParse loganhz


text:
EC2 tag UI issues

Rancher versions: v1.6.8-rc5
Results:

[x] Rename Tags (EC2) to EC2 Tags

[x] Add more space between Tags section and IAM Profile sections

[x] Make the Tags section full width like Labels is below it

[x] Should not allow comma in the EC2 Tag sections (no commas in Tag or Value sections)

Version - v1.6.8-rc6
Verified fixed


text:
Support self-signed server CA chain on Windows

Problem:
Consider only the CA chain with only one CA
Solution:
Split multiple CAs from $SSL_CERT_DIR\serverca, then import one by one
Issue:
https://github.com/rancher/rancher/issues/20436

LGTM

authors: loganhz thxCode


text:
Make impersonation service account more resilient

Currently, the impersonation path checks for the existence of a matching
impersonation clusterrole on the downstream cluster and then assumes
there is an impersonation service account to go with it. If for some
reason there was an interruption in between creating the clusterrole and
creating the service account, the service account won't exist and
further requests will be perpetually stuck. This change ensures that
won't happen by checking for a Not Found error when retrieving the
service account, and continuing to create the needed resources in such
an event. This also fixes an unclear error message to clarify that the
missing resource is the service account, not the secret, and to
distinguish it from another similar error message.
https://github.com/rancher/rancher/issues/34824

The function checks the role first, if the role does not exist then this whole section is skipped https://github.com/rancher/rancher/pull/34861/files#diff-fe913e39db39d26629ffb0d1e83c60678ce415c81af03283120afeec3233f011R57-R63


text:
large numbers in yaml output are showing up in scientific notation

Steps:

rio run -n tstk1/tservice1 --memory-limit 150m nginx
rio inspect --format yaml tstk1/tservice1

Results:  Notice that all large numbers are in scientific notations (for instance memoryLimitBytes is 1.572864e+08) instead of regular numbers.

no longer valid

repo: rancher/rio


text:
Fixing various style bugs

Added a new container-flex and col-flex to replace the weird multi stat container on hosts, vms, and container details pages. Flex works much better as it gives us a full height column with out a lot of hackery.

@westlywright Can you do the same on the service view?  Or whatever view this is http://localhost:8000/apps/1e16/services/1s121/containers

@ibuildthecloud taken care of

I'm not sure I see how flexbox is an improvement...

vs old:

authors: ibuildthecloud vincent99 westlywright

repo: rancher/ui


text:
[UI][Private Registry] When adding credential , there is no email format validation done for the email field.

Version - V013.0
There should be some basic email format validation check done when entering email for in Credential creation in "Add Registry" and "Add Credential" page.

The field is called "email" but the registry can do whatever it wants with it and Docker does not require to actually be an email.
It's marked required in the API so you have to enter something in it now, but I don't want to get into does-it-look-like-a-valid-email when that isn't even a requirement from Docker.

v0.17.0
Verified fixed

authors: sangeethah tfiduccia vincent99

repo: rancherio/rancher


text:
Deleting and restoring a service's container loses association with service

v0.16.0
Steps:

Create a Environment
Add a service
Go to Container page
Delete and restore service container
Go back to Service page

Results:
Service container no longer shows up.  If I delete and restore from service page, it stays.  If I delete from service page, but restore from container, it's removed.
Expected:
Should stay until purged.

Even when we attempt to delete and restore from service page, the container is removed from the service. Notice that when you refresh , the service does not have this container associated with it anymore.
Removing UI tag from this bug , since it reproduces from both the container view and service view.

v0.18.1
Verified fixed

authors: sangeethah tfiduccia


text:
Update Dependencies via Dependable

Update Dependencies via Dependable
Dependency updates

Gem
Previous Version
New Version
Source
Diff

byebug
9.0.6
9.1.0
deivid-rodriguez/byebug
view

Hi randalldrjr/roth I need to contact to discuss something important for
you about your platform
please contact to me at cnanita@peerbanks.org
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Aug 22, 2017 at 9:15 AM, Randall Reed, Jr. <notifications@github.com

wrote:

Update Dependencies via Dependable
Dependency updates
Gem Previous Version New Version Source Diff
byebug 9.0.6 9.1.0 deivid-rodriguez/byebug
https://github.com/deivid-rodriguez/byebug view
https://github.com/deivid-rodriguez/byebug/compare/v9.0.6...v9.1.0
You can view, comment on, or merge this pull request online at:
https://github.com/randallreedjr/roth_ira/pull/17
Commit Summary

Update Dependencies via Dependable

File Changes

M Gemfile.lock
https://github.com/randallreedjr/roth_ira/pull/17/files#diff-0 (2)

Patch Links:

https://github.com/randallreedjr/roth_ira/pull/17.patch
https://github.com/randallreedjr/roth_ira/pull/17.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/randallreedjr/roth_ira/pull/17, or mute the thread
https://github.com/notifications/unsubscribe-auth/AcIHEoOiIkImA8O3r5WzPCugwQiODiATks5satSAgaJpZM4O-ml_
.

--
PeerBanks Corporation
382 NE 191ST STSuite: 88441Miami, FL 33179

authors: peerbanks randallreedjr


text:
Run tests in multiple threads

I've been using a multithreaded test runner I wrote for a while, and I was trying to see if there was any way to use this with, or maybe contribute it to this library. My runner runs each test case in its own thread; I get very nice speedups with it, and it can also be used to uncover some race conditions by allowing test cases to access shared state in a test class. I was poking around in here and found this comment in RandomizedRunner.runSuite:
// NOTE: this effectively means we can't run concurrent randomized runners.
final UncaughtExceptionHandler previous = Thread.getDefaultUncaughtExceptionHandler();

Does this mean it doesn't (and can't) run tests in multiple threads?  I'm not sure where the restriction takes effect: is it global, per-suite, per-class or per-case?

Hi Michael. The reason we don't do multi-threaded parallel test execution is very simple: the JVM doesn't allow full sandboxing of tests and our primary goal is full reproducibility from a single seed. Think of the globals that can be conflicting -- thread management (as you quoted), security policies, system properties, class loading order (and static initializers). For very simple tests that don't interact with the environment parallel execution is great, but anything beyond that is a problem.
A half-baked solution to this is implemented in the ANT runner for randomized testing -- it splits the set of test suites into multiple JVMs (load-balancing tests execution between them). This requires multiple JVMs to start (overhead), but if you have many test suites, the concurrency is quite all right.
In short: it is possible to run tests in parallel within a single JVM, but there are deep-rooted potential more problems with it, so it won't be implemented as part of this project.

I understand the concern about repeatability. It's certainly true that you cannot guarantee a failure will be reproducible in the face of multi-threading in the general case. However I think that's also true of tests which themselves spawn multiple threads, so in some sense this is an impossibly high standard.
In addition to the perf gain for simpler tests, I've found the multithreaded test runner to be useful in cases where I explicitly want to test some supposedly thread-safe class by running tasks that call its methods from multiple threads. In such a case I'm not sure how one could ever guarantee reproducibility though?
Anyway, I still think this could be useful as a selectable option, say by annotating the test class in cases where the test writer explicitly want to enable it.

Tests that fork multiple threads are non-reproducible if they don't have a state. But still -- if something fails you at least get a chance to repeat the same test execution (with the same randomization seed), even if you re-run it multiple times just to see whether the failure is intermittent or permanent for a given seed. Randomized runner tries to ensure every thread forked from the same test has the same initial randomization seed, so it's not really dumb -- it does its best.
bq. I've found the multithreaded test runner to be useful in cases where I explicitly want to test some supposedly thread-safe class by running tasks that call its methods from multiple threads.
I think a better design here would be to create a single test, then fork a number (randomized!) of threads and pound your business logic from those threads (but still within a single test!).
Believe me I've been down the route of trying to come up with a clean multithreaded separation of tests within a single JVM, but it quickly hits a showstopper -- be it system property-dependent initialization of something (which many third-party libraries use), a race condition on a singleton somewhere, configured once... you name it.
bq. Anyway, I still think this could be useful as a selectable option, say by annotating the test class in cases where the test writer explicitly want to enable it.
Useful -- maybe. But misleading -- for sure. I bet people would abuse this and then be stuck at how to reproduce a particular problem. If you're looking for difficult-to-reproduce issues even in the current setup, look at Apache Solr tests -- they are notorious for failing on one machine, but not on another...
The better you can isolate a single test run, the easier it is to debug. If you're unhappy about it -- please go ahead and fork the project or create your own runner! I bet somebody wrote something like this already (scan JUnit's mailing list).

Yeah, OK. I do have my own runner already. It's not very complicated to write. I'm working in a project that is borrowing LuceneTestCase so trying to find a way to adapt to that. Perhaps we'll just use this runner in some classes and LuceneTestCase in others. Anyway, thanks for the thoughtful response.

You're welcome!

authors: dweiss msokolov

repo: randomizedtesting/randomizedtesting


text:
Search for tooltip in the grid (maybe even NBT)

I was trying to find a location to put a feature request, but haven't been able to find a place.  Hope this is OK to put here.
I think it would be nice to be able to search NBT data, so when you're looking for say, an enchanted book, you could search for the enchant you want, and it will find them in the system :)

Can't you just do #efficiency to find for example efficiency enchanted tools?

Holy crap that works :)  I didn't realize!!! Thanks!

authors: DigitalSketch raoulvdberge

repo: raoulvdberge/refinedstorage


text:
Autocrafting .. craft with oredict

Issue description:
When i request to craft 64 sticky pistons .. I have the oredictionary for the pattren.
What happens:
it craft only one sticky pistion and continue with the crafting without giving the result
What you expected to happen:
i expect to have 64 sticky pistons in my RS System.. but what happend is i have only one.
Steps to reproduce:

make the pattren for it with oredict
request it from RS System
Wholla ... only one sticky piston is crafted
...

Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge:Latest
Refined Storage:Latest

Does this issue occur on a server? [yes/no]
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

related to #766 , which has been fixed in dev.


text:
Multiple question / MissionBio Tapestri Data

Hello,
Thank you for this tool !
I'm really interested but i'm struggling to understand how do you obtain the variant reads counts matrix ?  My guess is that you paired VAF variants with total reads counts of his amplicons ? If so won't it be biased by non-uniformity of the reads coverage of the so-called amplicon ? if it has been compute with an other method would it be possible to share it ?
You seem to also recommend to add the the clustering (with or without the mutation matrix ?) what is the mutation matrix in tapestri ? are you refering to the genotype matrix (where in each cell/barcode. 0: is wildtype, 1: one allele is alternate, 2: both alleles are alternate, 3: Missing genotype) ?
Also i'm not sure to understand what is the command argument -k and what it is doing ? maximum number of losses for an SNV is a bit vague.
Also would it be possible to provide a conda yaml environment or even a singularity / docker ? it would greatly simplify the use of your tools !
I'm aware it is a lot of questions, so thank you in advance for your time and kindness

Hello,
Thank you for your interest in using this tool and sorry for the late response.

Variant read count matrix -- yes, you are correct. This matrix contains the number of variant reads for each mutation in each cell. You can generate this matrix by multiplying the VAF with the total read counts (reference reads + variant reads) for each mutation.
Mutation matrix -- I have defined the mutation matrix in the paper (I updated the README to contain a link to the paper). Mutation matrix has entry of 0 if the mutation is abset, 1 if it is present and -1 if there is no information about the mutation in that cell.
-k arugment --Yes, this is the number of losses for a SNV in the phylogeny. More information can be found in the paper I have linked in the README (https://www.biorxiv.org/content/10.1101/2023.01.05.522408v1.abstract)
conda yaml -- Thank you for the suggestion. I will work upload a yaml file to use this tool in the next few days. The package requirement for ConDoR are very simple. We only need numpy, pandas, networkx and gurobipy.

repo: raphael-group/constrained-Dollo


text:
Loader v2

Loader was not showing on the V2
Also, I changed the behavior to show from the start of submission, rather than later for showing real time feedback.

Thanks @dipta007 for your contribution! Great work! I will build a new version.


text:
encoding.explode:true not working for schema properties

Hi Team,
I have several api endpoints that allow for a parameter to be specified multiple times. See example of one below.
{
    "openapi": "3.0.1",
    "info": {
        "title": "TEST",
        "version": "1.0.0"
    },
    "servers": [{
        "url": "http://localhost:8080/api/",
        "description": "TEST"
    }],
    "paths": {
        "/deleteImage": {
            "post": {
                "tags": ["Images"],
                "summary": "Delete Image",
                "description": "The delete image service deletes the specified image.  Multiple imageName parameters can be specified to delete multiple images.",
                "operationId": "deleteImage",
                "requestBody": {
                    "content": {
                        "application/x-www-form-urlencoded": {
                            "schema": {
                                "$ref": "#/components/schemas/DeleteImageRequest"
                            },
                            "encoding": {
                                "imageName": {
                                    "explode": true
                                }
                            }
                        },
                        "multipart/form-data": {
                            "schema": {
                                "$ref": "#/components/schemas/DeleteImageRequest"
                            },
                            "encoding": {
                                "imageName": {
                                    "explode": true
                                }
                            }
                        }
                    }
                },
                "responses": {
                    "200": {
                        "description": "Request succeeded"
                    }
                }
            }
        }
    },
    "components": {
        "schemas": {
            "DeleteImageRequest": {
                "required": ["accessKey", "imageName"],
                "type": "object",
                "properties": {
                    "accessKey": {
                        "type": "string",
                        "description": "Your unique access key that you can find on the Account page in the Cloud Console."
                    },
                    "imageName": {
                        "minItems": 1,
                        "type": "array",
                        "items": {
                            "type": "string",
                            "description": "The name of the image. This parameter can be specified multiple times to delete multiple files.",
                            "example": "/MyImageFolder/MyImage.png"
                        }
                    }
                },
                "description": "Delete Image Request Model"
            }
        }
    }
}

In RapiDoc the explode:true property seems to be ignored and the imageName parameter is interpreted as a single parameter with comma delimitated values and an erroneous leading delimitator. If I test the example spec above from RapiDoc I get the following raw request bodies:
Multipart:
------WebKitFormBoundaryXXVgV2Xnct1AW3tT
Content-Disposition: form-data; name="accessKey"

XXX
------WebKitFormBoundaryXXVgV2Xnct1AW3tT
Content-Disposition: form-data; name="imageName"

,abc.png,def.jpg
------WebKitFormBoundaryXXVgV2Xnct1AW3tT--

Form Data:
accessKey=XXX&imageName=,abc.png,def.jpg

The example api above works correctly in Swagger UI though.
I also note that Parameters with explode:true seem to work fine in RapiDoc.

We have run into this problem as well. And the way I read the OpenAPI documentation it is supposed to explode arrays by default, without even requiring an explode:true setting:

Form fields can contain primitives values, arrays and objects. By default, arrays are serialized as array_name=value1&array_name=value2 and objects as prop1=value1&prop2=value2, but you can use other serialization strategies as defined by the OpenAPI 3.0 Specification.

But we are happy to supply the setting, we just need it to be supported.

authors: Rauert brunchboy

repo: rapi-doc/RapiDoc


text:
bytes_stored is broken when --nodes are passed

When you pass nodes the search for bytes_stored is broken.
/Users/athompson/code/personal/elasticsearch-drain/lib/elasticsearch/drain/cli.rb:80:in `block in remove_nodes': undefined method `bytes_stored' for nil:NilClass (NoMethodError)
    from /Users/athompson/code/personal/elasticsearch-drain/lib/elasticsearch/drain/cli.rb:78:in `each'
    from /Users/athompson/code/personal/elasticsearch-drain/lib/elasticsearch/drain/cli.rb:78:in `remove_nodes'
    from /Users/athompson/code/personal/elasticsearch-drain/lib/elasticsearch/drain/cli.rb:33:in `asg'
    from /Users/athompson/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
    from /Users/athompson/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
    from /Users/athompson/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
    from /Users/athompson/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
    from bin/drain:3:in `<main>'

This feature was introduced in #18

This is fixed by #23.


text:
Fix skbuild arguments in build.sh

The previous method was incorrect and did not work as expected, for example specifying -g would not result in a Cython debug build.

To be entirely honest, I'm not always sure about those build tools either, this time I borrowed from cuDF. In any case, I've tested this to be working currently, so I'm gonna go ahead and merged it as is. Thanks @wence- !

/merge

repo: rapidsai/ucxx


text:
Fix parsing of IPv4 address in SOCKS4A

According to the protocol a domain is used instead of an IPv4 address if the address is 0.0.0.x with x non-zero.
Since (0x00000000 & 0x000000ff) == 0x00000000 the IP address 0.0.0.0 was considered to be a domain as well, so we need to check if not only the first 3 octets are zero but if the last octet is non-zero as well.
I'm not sure if any client sets 0.0.0.0 as IP address. I didn't see a real life issue with this, but nonetheless let's try to be true to the specification.

Good find - thanks.

authors: blochbergermax raptorswing

repo: raptorswing/Qt-Socks-Server


text:
zInvokeClient+208 when no MI Row selected and Registry set to send FormObject

Describe the bug
When the registry setting, 'Include FormObject for sections without a current row selected' is set to 'Y' multiple iteration FormObjects are sent in the ScriptLink payload with no CurrentRow. After sending the ScriptLink request, myAvatar shows the error 'zInvokeClient+208' when processing the response. - Reported by Compass Health.
To Reproduce
Steps to reproduce the behavior:

Set the Registry Setting 'Include FormObject for sections without a current row selected' to 'Y'
Open a myAvatar form with existing multiple iteration content and a ScriptLink call configured.
Trigger ScriptLink call without selecting a row in the multiple iteration table.
Error 'zInvokeClient+208' appears to user and shows in logging.

Expected behavior
Either no error should occur or a message provided by the ScriptLink API. THe 'zInvokeClient+208' should not occur.
Screenshots

Example Code
In this example, no modifications are made to the incoming OptionObject2015, so no error message should be displayed.
    public class ParentGuardian : ICommand
    {
        private OptionObject2015 _optionObject2015;
        private string _parameter;
        public ParentGuardian(OptionObject2015 optionObject2015, string parameter)
        {
            _optionObject2015 = optionObject2015;
            _parameter = parameter;
        }
        public OptionObject2015 Execute()
        {
            return _optionObject2015.ToReturnOptionObject();
        }
    }

This issue is caused by a missing null check when cloning the FormObject. This will be corrected in the next release.


text:
Feature request: pioasm: multiple programs

Let's say I want to use the PIO for something UART-like. Now obviously this requires a send program and a receive program. I want to pack both into one PIO device because they're both small enough.
My problem is that there seems to be no clean way to do that: pioasm doesn't tell me how long the first program is, thus I have no way to set the .offset for the second program correctly.

Have a look at some of the examples in https://github.com/raspberrypi/pico-examples/tree/master/pio/
https://github.com/raspberrypi/pico-examples/tree/master/pio/ir_nec/nec_transmit_library is an example that uses multiple PIO programs (and there might be others if you dig around? :man_shrugging: )

And I've not tried it myself, but you might want to look at https://github.com/harrywalsh/pico-hw_and_pio-uart-gridge/tree/HW_and_pio_uarts

authors: lurch smurfix

repo: raspberrypi/pico-sdk


text:
enforce that resulting binaries dont have arm opcodes, fixes #50

the original fault, is that the arm-none-gcc on my host was built with multi-lib disabled
as a result, it could generate thumb binaries at compile time, but the crtbegin.o and the newlib libc.a had been pre-built in arm32 mode only
pico-sdk would silently link the arm32 variants, and then the code would just fault out at runtime, and only SWD could reveal why
this pr will cause the build to fail if such arm32 opcodes wind up in the binary, forcing you to fix the tooling before you can flash the pico

if we're going to do anything here, we should check in elf2uf2 (which should be able to tell the difference... it already checks a lot of things)...

@kilograham should i just throw in some c code and have cmake compile it the same way it does the other host utils?

ah, elf2uf2 does sound like a good place to add the check

yup add something here https://github.com/raspberrypi/pico-sdk/blob/master/tools/elf2uf2/main.cpp#L92

@kilograham is that a new git repo?, or do you just mean a new PR against the elf2uf2 file?

I suspect the latter. (as you can see above, elf2uf2 is maintained in this repo)

yes in this repo, but this PR seems a bit obsolete

authors: cleverca22 kilograham lurch


text:
🛑 NJU Mirror (mirrors.nju.edu.cn) is down

In 578b6ef, NJU Mirror (mirrors.nju.edu.cn) (https://mirrors.nju.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NJU Mirror (mirrors.nju.edu.cn) is back up in a5c68ab.

repo: raspbian-addons/status


text:
CLN update to v24.02

Testing the RECKLESS CLN UPDATE option on Raspiblitz v0.11.0 rc3 + the backup plugin patch in #4446
Got a warning from poetry, but otherwise looking good:
Cloning into 'lightning'...
remote: Enumerating objects: 139424, done.
remote: Counting objects: 100% (18553/18553), done.
remote: Compressing objects: 100% (1446/1446), done.
remote: Total 139424 (delta 17579), reused 17165 (delta 17101), pack-reused 120871
Receiving objects: 100% (139424/139424), 97.20 MiB | 1.23 MiB/s, done.
Resolving deltas: 100% (91450/91450), done.
Updating files: 100% (27334/27334), done.
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is re
commended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is re
commended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Warning: The current project could not be installed: No file/folder found for package cln-meta-project
If you do not want to install the current project use --no-root.
If you want to use Poetry only for dependency management but not for packaging, you can set the operating mode to "non-package" in your pypr
oject.toml file.
In a future version of Poetry this warning will become an error!
2024-03-07 17:17:20,872 [DEBUG] Primitive[path=Getinfo.id, required=True, type=pubkey]
2024-03-07 17:17:20,873 [DEBUG] Primitive[path=Getinfo.alias, required=True, type=string]

Should be ok for v0.11.0
Then could ship the next raspiblitz release with the CLN v24.02 from start.

At the moment in dev CLN version is ...
https://github.com/raspiblitz/raspiblitz/blob/4687506d12f958bbba03b05bcb54b0a4ec432596/home.admin/config.scripts/cl.install.sh#L5
.. closing issue.

authors: openoms rootzoll

repo: raspiblitz/raspiblitz


text:
Bitcoin Core install issues

Describe the issue
I'm at the installation step of Bitcoin client, have downloaded the latest Bitcoin Core binary along with the hash and signatures.  Reference checksum was ok, and signature check said there were good signatures, but with warnings.  I went ahead and extracted and installed Bitcoin Core anyway, but it fails the version check.  Not sure if I should try to proceed with Steps 2a and following.
Location in guide
https://raspibolt.org/guide/bitcoin/bitcoin-client.html
Screenshots
Here's are some of the signature warnings:

Here's the error when I tried to check the version after installing:

I tried to change to the bitcoin-23.0/bin/ directory where I can clearly see the file "bitcoind" listed (as shown in the screenshot) but it came back with the same error "no such file or directory"
Environment

Hardware platform: Raspberry Pi 4
Operating system: Raspberry Pi OS 64bit Lite
Version: Debian GNU/Linux 11 (bullseye)

Any suggestions for how to resolve the issues I reported?  Can I safely ignore the warnings on the signatures and assume the bitcoin core client I downloaded is safe to use?  And why doesn't the version check work?  If it's a simple noob error, please advise - I don't know linux well enough to troubleshoot it myself.

I installed btc core 23.0 yesterday on my raspi and it worked.
Why did you use the arm-linux version and not the suggested version from the guide?
$ tar -xvf bitcoin-23.0-aarch64-linux-gnu.tar.gz
I dont know if that is a problem but maybe you can try that version instead

@zynos I was going by the instruction in the guide to download the latest version in case there had been an update, as it says here:

But looking at it again, I see the latest version is in fact 23.0, so I'll retry it like you did.  Thanks for the suggestion!

@zynos I went ahead and took your suggestion and just downloaded the version listed in the guide, and when I checked the signatures, got similar warnings as last time.

But I went ahead and installed the bitcoin core client and this time it worked as expected, so will close this issue.  Still not sure if those warnings should be heeded though - makes this noob a bit uncertain.  If they're not important, I feel like the guide should mention that they can be safely ignored.

authors: kwikslvr zynos

repo: raspibolt/raspibolt


text:
Update vue-events version

I fixed a bug in vue-events that was introduced in Vue 2.2.x, just updating this projects dependency.
https://github.com/cklmercer/vue-events/issues/8

@cklmercer Thanks, really appreciated. :)

authors: cklmercer ratiw


text:
Documentation links to lessons are outdated

That page and I believe all other pages referencing lessons contain outdated links, as lessons moved from blob/master to wiki.
Please, fix.

Sorry for that. Those pages will soon be replaced when v2.0 is released (currently in beta). The document for the v2.0-beta is available here.

authors: RomanDavlyatshin ratiw


text:
sendfile is not supported on SSL

Right now I just FFI out to file:sendfile for both TCP and SSL sockets.  However, sendfile does not work with SSL.
I'll need to scope this per-transport, and probably have some default implementation for SSL.  Currently, ThousandIsland just does a file:pread and ssl:send... is it worth trying to do something a little less memory intensive?  Not sure how likely this situation is.  Maybe just add the basic one and see what people think.

Whoops, this should be on mist.

repo: rawhat/glisten


text:
[CI] TestAutoscalingRayService is flaky

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ci
What happened + What you expected to happen
https://buildkite.com/ray-project/ray-ecosystem-ci-kuberay-ci/builds/5672#0193c1f9-ac0c-4a19-88eb-aee9aa146f14/3769
Reproduction script
https://buildkite.com/ray-project/ray-ecosystem-ci-kuberay-ci/builds/5672#0193c1f9-ac0c-4a19-88eb-aee9aa146f14/3769
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Let's temporarily not address this issue, as I ran it many times on Buildkite and my local machine but couldn't reproduce the error. This is the PR where I tried running it 10 times: https://github.com/ray-project/kuberay/pull/2682

repo: ray-project/kuberay


text:
[Feature] Add CI tests for Helm charts

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Test Helm configuration in the CI.
The Helm charts are very easy to break.
We could take a look at testing strategies used by similar projects; no need to innovate.

This is actually a duplicate of https://github.com/ray-project/kuberay/issues/184.


text:
[Autoscaler] Match autoscaler image to Ray head image for Ray >= 2.0.0

Why are these changes needed?

This PR updates the logic that selects a default autoscaler image.
For Ray versions at least 2.0.0, use the same image for the autoscaler as for the Ray container.
This eliminates the possibility of autoscaler/Ray incompatibility and reduces docker pull time.
For earlier Ray versions, use rayproject/ray:2.0.0 to guarantee up-to-date autoscaler functionality.
As of the Ray 2.0.0 branch cut earlier today, an image tagged rayproject/ray:2.0.0 exists on Dockerhub.
Until the official Ray release in two weeks, this image is unofficial and its actual contents are a moving target -- but I think we can live with the inconsistency in the short term. (I'm open to other opinions on this choice.)
Related issue number

Closes https://github.com/ray-project/kuberay/issues/360
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

so rayproject/ray:2.0.0 will be overridden once  the office image is out?

/cc @akanso to take a look

so rayproject/ray:2.0.0 will be overridden once the office image is out?

rayproject/ray:2.0.0 is updated each time we push to the Ray 2.0.0 release branch
The "official image is out" after the last commit is made to the release branch and we announce the release.
Maybe not the best way of doing things but that's the way it is at the moment.

#424 is merged to help improve test stability. You can rebase the change to see if nightly version pass

Let's merge this one and it's time to cut rc.0 release. If other reviewers have further feedback, feel free to leave it here.

authors: DmitriGekhtman Jeffwan


text:
xgboost_ray fails on Python 3.8 on macOS

In Python 3.8 on macOS, multiprocessing uses a spawn strategy instead of a fork strategy for process creation. This change is no longer compatible with our subclassed RabitTracker that uses a process internally rather than a thread and causes xgboost_ray training to fail.
Works fine using the xgboost built in RabitTracker
Python 3.8.6 (default, Nov 20 2020, 18:29:40)
[Clang 12.0.0 (clang-1200.0.32.27)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ray
>>> from ray.services import get_node_ip_address
>>> import xgboost
>>> from xgboost import RabitTracker
>>> node_ip = get_node_ip_address()
>>> rabit_tracker = RabitTracker(hostIP=node_ip, nslave=2)
>>> rabit_tracker.start(nslave=2)

Fails using xgboost_ray internal _RabitTracker
Python 3.8.6 (default, Nov 20 2020, 18:29:40)
[Clang 12.0.0 (clang-1200.0.32.27)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ray
>>> from ray.services import get_node_ip_address
>>> from xgboost_ray.main import _RabitTracker
>>> node_ip = get_node_ip_address()
>>> rabit_tracker = _RabitTracker(hostIP=node_ip, nslave=2)
>>> rabit_tracker.start(nslave=2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/amog/dev/xgboost_ray/xgboost_ray/main.py", line 106, in start
    self.thread.start()
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 47, in _launch
    reduction.dump(process_obj, fp)
  File "/usr/local/Cellar/python@3.8/3.8.6_2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object '_RabitTracker.start.<locals>.run'

Once we fix this we should include 3.8 and macOS tests in the CI and make another release.
cc @krfricke

Current master with ray 1.2.0 works fine for me:
> python
Python 3.8.6 (default, Apr 14 2021, 14:07:57)
[Clang 12.0.0 (clang-1200.0.32.2)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ray
>>> from ray.services import get_node_ip_address
>>> from xgboost_ray.main import _RabitTracker
>>> node_ip = get_node_ip_address()
>>> rabit_tracker = _RabitTracker(hostIP=node_ip, nslave=2)
>>> rabit_tracker.start(nslave=2)
>>> del rabit_tracker
>>>
 > python ../../xgboost_ray/examples/simple.py
File descriptor limit 2560 is too low for production servers and may result in connection errors. At least 8192 is recommended. --- Fix with 'ulimit -n 8192'
2021-04-14 14:11:37,731	INFO services.py:1264 -- View the Ray dashboard at http://127.0.0.1:8265
2021-04-14 14:11:39,656	INFO main.py:817 -- [RayXGBoost] Created 4 new actors (4 total actors). Waiting until actors are ready for training.
2021-04-14 14:11:40,582	INFO main.py:860 -- [RayXGBoost] Starting XGBoost training.
(pid=89787) [14:11:40] task [xgboost.ray]:4598953872 got new rank 3
(pid=89777) [14:11:40] task [xgboost.ray]:4556349584 got new rank 2
(pid=89790) [14:11:40] task [xgboost.ray]:4554084240 got new rank 0
(pid=89782) [14:11:40] task [xgboost.ray]:4535186576 got new rank 1
2021-04-14 14:11:41,440	INFO main.py:1304 -- [RayXGBoost] Finished XGBoost training on training data with total N=143 in 1.84 seconds (0.85 pure XGBoost training time).
Final validation error: 0.0210
 > python --version
Python 3.8.6
 > uname -a
Darwin Kais-MacBook-Pro.local 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64 x86_64

@amogkam could you check if it works for you, too, and close the issue if it does?

Ah seems this was fixed in #42 and we only left this issue open. Closing this for now then.

authors: amogkam krfricke


text:
[URL Unshortener] Unable to Expand URL from https://is.gd

Extension
https://www.raycast.com/SebDanielsson/url-unshortener
Description
URL Unshortener is showing error when expanding URL from https://is.gd.
System: Raycast 1.68.1 on macOS 14.3.1
Example URL: https://is.gd/putPEo

Steps To Reproduce
Tried different URL from https://is.gd same result
Current Behaviour
No response
Expected Behaviour
No response

I just tried unshortening https://is.gd/putPEo with Raycast 1.68.1 running on macOS 14.3.1 and didn't get any error messages. Do you still have this issue?

It works, wondering if it's also possible to expand/clean URL like this, I use www.expandurl.net to get the canonical URL.
https://redirect.viglink.com/?key=0ab71bd42c2ca312a536dac167978a13&u=https%3A%2F%2Fwww.amazon.com%2FApple-MU8F2AM-A-Pencil-Generation%2Fdp%2FB07K1WWBJK%2F%3Ftag%3Dtoysb-20&type=ap&loc=https%3A%2F%2F9to5toys.com%2F2024%2F02%2F17%2Fapple-pencil-2-drops-to-to-79-at-amazon-its-second-best-price-reg-129%2F&ref=https%3A%2F%2F9to5toys.com%2F

Sorry for the late reply!
I'm not sure how to implement that functionality as sometimes the parameters are used to redirect the user to the final page. Preferably I would like to avoid depending on an online service. PRs are welcome of course😉

authors: alwinsamson sebdanielsson

repo: raycast/extensions


text:
[Extension Bug] Home Assistant extension can't connect to web-socket

Extension – Home Assistant

Author: @tonka3000

Description
Extension can't connect to Home Assistant Websocket API.
I have tried manually connecting to the Websocket API using Websocket Extension and I have managed successfully connect to it where this extension seems not to.
I wanted to see logs of what is going on, but thanks to https://github.com/raycast/extensions/issues/1224 I did not manage.
Maybe it is incompatible with the latest Home Assistant version? I have noticed that you are not running the latest home-assistant-js-websocket package.
Raycast version
Version: 1.31.0
Home Assistant info

version
core-2022.3.6

installation_type
Home Assistant Core

dev
false

hassio
false

docker
false

user
homeassistant

virtualenv
true

python_version
3.9.2

os_name
Linux

os_version
5.4.182

arch
armv7l

timezone
Europe/Prague

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Lovelace

dashboards
1

resources
0

mode
auto-gen

Hey @AuHau ,
I have also the latest version of HA (2022.3.7) and it works for me.
Do you have a trailing whitespace in your url e.g. https://myhainstance.org/. If yes: Remove it (https://myhainstance.org) and try again.
If this does not work maybe you need to upgrade to 2022.3.7.

Hmmm, nothing traling.
I have no idea what has changed but today it works as expected 😅 Most probably it is then problem on my Home Assistant deployment, so closing this. Thanks for the ideas!

@AuHau Great to hear that it works now. Let me know if you miss something from home assistant in the exension.