trace_callMany does not return proper stateDiff

Describe the bug
Calling trace_callMany on reth does not return the proper stateDiffs. While accounts are returned correctly, account storage changes are empty in the response payload.
I am using erigon as a baseline.
Steps to reproduce
Payload:
{
    "jsonrpc": "2.0",
    "method": "trace_callMany",
    "params": [
        [
            [
                {
                    "from": "0xdc975a9bb00f4c030e4eb3268f68e4b8d0fa0362",
                    "to": "0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc",
                    "data": "0x022c0d9f000000000000000000000000000000000000000000000000000000007bf8a21d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000001a2d11cb90d1de13bb81ee7b772a08ac234a8058000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000001200624000000000000000000000000000000000000000000000000000000004de400000000000000000000000000000000000000000000000000adcebdd8c272aa00000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000005200000000000000000000000000000000000000000000000000000000000000000000000000000000000000087870bca3f3fd6335c3f4ce8392d69350b4fa4e2000000000000000000000000ff9b90914e248339ab0a50bf4798ef8b012eac79000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb48000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"
                },
                [
                    "stateDiff"
                ]
            ]
        ],
        "0x10704E9"
    ],
    "id": "1"
}

Erigon Response:
{
    "jsonrpc": "2.0",
    "id": "1",
    "result": [
        {
            "output": "0x",
            "stateDiff": {
                "0x4d5f47fa6a74757f35c14fd3a6ef8e3c9bc514e8": {
                    "balance": "=",
                    "code": "=",
                    "nonce": "=",
                    "storage": {
                        "0x0000000000000000000000000000000000000000000000000000000000000036": {
                            "*": {
                                "from": "0x00000000000000000000000000000000000000000000371095f444c2acbea985",
                                "to": "0x0000000000000000000000000000000000000000000037108577c8900d78169b"
                            }
                        },
                        "0x14a553e31736f19e3e380cf55bfb2f82dfd6d880cd07235affb68d8d3e0cac4d": {
                            "*": {
                                "from": "0x00000000033f808ab803c644db6894fd00000000000000074aaaa690defb3082",
                                "to": "0x00000000033fcccd35cdedc8f004086d00000000000000074abed827c6055382"
                            }
                        },
                        "0xe176be41876e8715e34c4f929fe8a3d58a234f652e01ebcb9fd2e60ad65a5071": {
                            "*": {
                                "from": "0x00000000033f60dc595cbad82ad23abf00000000000000004330f0ea9a15277c",
                                "to": "0x00000000033fcccd35cdedc8f004086d000000000000000032a0432113c47192"
                            }
                        }
                    }
                },
                "0x72e95b8931767c79ba4eee721354d6e99a61d004": {
                    "balance": "=",
                    "code": "=",
                    "nonce": "=",
                    "storage": {
                        "0x000000000000000000000000000000000000000000000000000000000000003a": {
                            "*": {
                                "from": "0x00000000000000000000000000000000000000000000000000006c1ce9f927b1",
                                "to": "0x00000000000000000000000000000000000000000000000000006c1c6f136637"
                            }
                        },
                        "0xe491d6f1bcb6404629cb0e97fa7316b6d33388ed1b5cbff0d91541cfaf2c8f49": {
                            "*": {
                                "from": "0x0000000003411476a977a6f025464469000000000000000000000000f5d1ce16",
                                "to": "0x0000000003426857adec5b53eb2fcf580000000000000000000000007aec0c9c"
                            }
                        }
                    }
                },
                "0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2": {
                    "balance": "=",
                    "code": "=",
                    "nonce": "=",
                    "storage": {
                        "0xed960c71bd5fa1333658850f076b35ec5565086b606556c3dd36a916b43ddf21": {
                            "*": {
                                "from": "0x000000000015239501f0305aa108dc6800000000033fc3f6f310893e50ae2bdb",
                                "to": "0x0000000000152364f2cdc66988b272c000000000033fc3f6f310893e50ae2bdb"
                            }
                        },
                        "0xed960c71bd5fa1333658850f076b35ec5565086b606556c3dd36a916b43ddf22": {
                            "*": {
                                "from": "0x00000000001d62a19165fb8b4d5ed0830000000003426857adec5b53eb2fcf58",
                                "to": "0x00000000001d62802a0a7c8d7d8cfac80000000003426857adec5b53eb2fcf58"
                            }
                        },
                        "0xed960c71bd5fa1333658850f076b35ec5565086b606556c3dd36a916b43ddf23": {
                            "*": {
                                "from": "0x000000000000000000000300645ce4cb00000000002d083da090c5dadbabda10",
                                "to": "0x000000000000000000000300645ce4cb00000000002d083973a555fb21b19f59"
                            }
                        },
                        "0xf81d8d79f42adb4c73cc3aa0c78e25d3343882d0313c0b80ece3d3a103ef1ec0": {
                            "*": {
                                "from": "0x0000000000109b2be236be057c3d444600000000033fccb64e79b1ee99b20daf",
                                "to": "0x0000000000109b35271d7e414848240d00000000033fcccd35cdedc8f004086d"
                            }
                        },
                        "0xf81d8d79f42adb4c73cc3aa0c78e25d3343882d0313c0b80ece3d3a103ef1ec1": {
                            "*": {
                                "from": "0x00000000002026163e4dfcb035736b6a0000000003443d92040355dbeb352d0f",
                                "to": "0x000000000020261de41847d9f20a4f260000000003443dbe97c6715825941b72"
                            }
                        },
                        "0xf81d8d79f42adb4c73cc3aa0c78e25d3343882d0313c0b80ece3d3a103ef1ec2": {
                            "*": {
                                "from": "0x000000000000000000000000645ce23700000000005161c67fcd26ea78797e8a",
                                "to": "0x000000000000000000000000645ce4cb00000000005161ce8ca217b8169196ae"
                            }
                        },
                        "0xf81d8d79f42adb4c73cc3aa0c78e25d3343882d0313c0b80ece3d3a103ef1ec7": {
                            "*": {
                                "from": "0x000000000000000000000000000000000000000000000000e4bed2db3ac40517",
                                "to": "0x000000000000000000000000000000000000000000000000e503533610a1922c"
                            }
                        }
                    }
                },
                "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": {
                    "balance": "=",
                    "code": "=",
                    "nonce": "=",
                    "storage": {
                        "0x28c0947f463362aab09a2d7896ccc847fb7e52633a16b978fb2caf3db1a9b8f8": {
                            "*": {
                                "from": "0x00000000000000000000000000000000000000000000000000001b4a3771cfb9",
                                "to": "0x00000000000000000000000000000000000000000000000000001b49bb792d9c"
                            }
                        },
                        "0x368c3f5f03e5634b3e4381c9c3caac98f4d254c7027fd14b53436c90d060fef4": {
                            "*": {
                                "from": "0x00000000000000000000000000000000000000000000000000001b6211f2581b",
                                "to": "0x00000000000000000000000000000000000000000000000000001b628deafa38"
                            }
                        },
                        "0xd5f747b0763f52aa2da52d75f573e98d9c227849393c76903862705476c0463a": {
                            "*": {
                                "from": "0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffdf219f38b",
                                "to": "0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffd7621516e"
                            }
                        }
                    }
                },
                "0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc": {
                    "balance": "=",
                    "code": "=",
                    "nonce": "=",
                    "storage": {
                        "0x0000000000000000000000000000000000000000000000000000000000000008": {
                            "*": {
                                "from": "0x645ce49b00000000037b829f0ce1522cfd3f00000000000000001b4a3771cfb9",
                                "to": "0x645ce4cb00000000037b927d6d120fecc61e00000000000000001b49bb792d9c"
                            }
                        },
                        "0x0000000000000000000000000000000000000000000000000000000000000009": {
                            "*": {
                                "from": "0x00000000000000000000016a909af1b60ecc390961770d01800bd2eb97fc7124",
                                "to": "0x00000000000000000000016a90a111c8057815d1444a6c1c0bc0f1db5532c5a4"
                            }
                        },
                        "0x000000000000000000000000000000000000000000000000000000000000000a": {
                            "*": {
                                "from": "0x0000000000000000000000000000000000002d4534d614a875024f7f3304699e",
                                "to": "0x0000000000000000000000000000000000002d45364e3a250a4371500366e92e"
                            }
                        }
                    }
                },
                "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": {
                    "balance": {
                        "*": {
                            "from": "0x2ee002944e5be99985e28",
                            "to": "0x2ee00293dc1e947d73a8b"
                        }
                    },
                    "code": "=",
                    "nonce": "=",
                    "storage": {
                        "0x3afb575d989d656a39ee0690da12b019915f3bd8709cc522e681b8dd04237970": {
                            "*": {
                                "from": "0x00000000000000000000000000000000000000000000000017071b01c1e028e7",
                                "to": "0x00000000000000000000000000000000000000000000000017b5a4ed1d16e057"
                            }
                        },
                        "0xb064600732a82908427d092d333e607598a6238a59aeb45e1288cb0bac7161cf": {
                            "*": {
                                "from": "0x0000000000000000000000000000000000000000000015b966f8f28f3472e6cb",
                                "to": "0x0000000000000000000000000000000000000000000015b95664e49dc9bb42df"
                            }
                        },
                        "0xb374801ace2c02f5db0425ab5920a2b7ed1d5a00abbcd395fda7530ba1d666c0": {
                            "*": {
                                "from": "0x00000000000000000000000000000000000000000000037b829f0ce1522cfd3f",
                                "to": "0x00000000000000000000000000000000000000000000037b927d6d120fecc61e"
                            }
                        }
                    }
                },
                "0xdc975a9bb00f4c030e4eb3268f68e4b8d0fa0362": {
                    "balance": {
                        "*": {
                            "from": "0xbdd144befdb0b9e",
                            "to": "0x4916dc2c698215cb"
                        }
                    },
                    "code": "=",
                    "nonce": {
                        "*": {
                            "from": "0x5",
                            "to": "0x6"
                        }
                    },
                    "storage": {}
                },
                "0xffee087852cb4898e6c3532e776e68bc68b1143b": {
                    "balance": {
                        "*": {
                            "from": "0x588500f3424d93d62c",
                            "to": "0x58850817179f54f9c9"
                        }
                    },
                    "code": "=",
                    "nonce": "=",
                    "storage": {}
                }
            },
            "trace": [],
            "vmTrace": null
        }
    ]
}

Reth Response
{
    "jsonrpc": "2.0",
    "result": [
        {
            "output": "0x",
            "trace": null,
            "vmTrace": null,
            "stateDiff": {
                "0x102633152313c81cd80419b6ecf66d14ad68949a": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x15c5620dffac7c7366eed66c20ad222ddbb1ed57": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x1a2d11cb90d1de13bb81ee7b772a08ac234a8058": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x2f39d218133afab8f2b819b1066c7e434ad94e9e": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x3e7d1eab13ad0104d2750b8863b489d65364e32d": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x4d5f47fa6a74757f35c14fd3a6ef8e3c9bc514e8": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x53f57eaad604307889d87b747fc67ea9de430b01": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x54586be62e3c3580375ae3723c145253060ca0c2": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x5f4ec3df9cbd43714fe2740f5e3616155c5b8419": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x6df1c1e379bc5a00a7b4c6e67a203333772f45a8": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x72e95b8931767c79ba4eee721354d6e99a61d004": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x789190466e21a8b78b8027866cbbdc151542a26c": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x7effd7b47bfd17e52fb7559d3f924201b9dbff3d": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x8164cc65827dcfe994ab23944cbc90e0aa80bfcb": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x822fa72df1f229c3900f5ad6c3fa2c424d691622": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x8fffffd4afb6115b954bd326cbe7b4ba576818f6": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0x98c23e9d8f34fefb1b7bd6a91b7ff122f4e16f5c": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xa2327a938febf5fec13bacfb16ae10ecbc4cbdcf": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xa964273552c1dba201f5f000215f5bd5576e8f93": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xac725cb59d16c81061bdea61041a8a5e73da9ec6": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xb0fe3d292f4bd50de902ba5bdf120ad66e9d7a39": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": {
                    "balance": {
                        "*": {
                            "from": "0x2ee002944e5be99985e28",
                            "to": "0x2ee00293dc1e947d73a8b"
                        }
                    },
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xd6293edbb2e5e0687a79f01becd51a778d59d1c5": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xdc975a9bb00f4c030e4eb3268f68e4b8d0fa0362": {
                    "balance": "=",
                    "nonce": {
                        "*": {
                            "from": "0x5",
                            "to": "0x6"
                        }
                    },
                    "code": "=",
                    "storage": {}
                },
                "0xe175de51f29d822b86e46a9a61246ec90631210d": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xe62b71cf983019bff55bc83b48601ce8419650cc": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xe7b67f44ea304dd7f6d215b13686637ff64cd2b2": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xea51d7853eefb32b6ee06b1c12e6dcca88be0ffe": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xf1cd4193bbc1ad4a23e833170f49d60f3d35a621": {
                    "balance": "=",
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                },
                "0xffee087852cb4898e6c3532e776e68bc68b1143b": {
                    "balance": {
                        "*": {
                            "from": "0x588500f3424d93d62c",
                            "to": "0x58850817179f54f9c9"
                        }
                    },
                    "nonce": "=",
                    "code": "=",
                    "storage": {}
                }
            }
        }
    ],
    "id": "1"
}

Node logs
No response
Platform(s)
No response
What version/commit are you on?
Reth Version: 0.1.0-alpha.1 Commit SHA: 2126c01a Build Timestamp: 2023-07-01T20:41:23.896265890Z Build Features:
What database version are you on?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

hmm, I think the way we currently track storage changes just doesn't work properly.
that the sender's balance also remains unchanged is a bit weird, is likely because gas price is 0 by default in call

Right, so i added gas and gas price as well, and still same result:
"gas": "0xf4240",
"maxPriorityFeePerGas": "0x00",
"maxFeePerGas": "0x174876e800"

This is the original transaction im using as a reference:
https://etherscan.io/tx/0x724b42054de556d9d392d045cc9997931d47c8016ab144928507fd7f9b61cb8b

Thx folks we're investigating / fixing this week

https://github.com/paradigmxyz/reth/pull/3549

feel free to open a separate issue for the balance diffs


[Feature] Wanted to pull req this Models DALL-E-2 [Beta]

Show case :

This based of communication AI
example how it work :
DALL-E-2 & gpt-3.5-turbo-0613 (tbh this model can read object such as image)
they are communication each other then gpt-3.5-turbo-0613 explaining to us
The best Machine Learning

Additional Note for DALL-E-2 [Beta] [Experimental] Not Ready Yet :

Network Search

Live Test : https://preview.chatgpt.btz.sh/

#2904


App in production mode (downloaded from store) does not receive push notifications

Hello!
Our application is subscribing to a topic "/topics/news" to receive push notifications from this topic.
Everything works just fine in development mode, but when the user install the app from the App Store it does not work.
However, push notifications sent from the console via "segment" DO WORK even in production mode
In summary: When the app is installed from store, push notifications for topics does not work
Code for topic subscription
AppDelegate.m
#pragma mark - PushNotifications

-(void)application:(UIApplication *)application didRegisterUserNotificationSettings:(UIUserNotificationSettings *)notificationSettings{
    [[FIRMessaging messaging] subscribeToTopic:@"/news"];
    [[FIRMessaging messaging] subscribeToTopic:@"/topics/news"];
}

-(void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken{
    [[FIRMessaging messaging] subscribeToTopic:@"/news"];
    [[FIRMessaging messaging] subscribeToTopic:@"/topics/news"];
}

For this issue, I am sure that your Production Certificate which was uploaded to firebase console is not Correct, Generate a new certificate SSL for production, and Upload it again to Firebase's Cloud Messaging pane. This will resolve your issue for sure. Cheers

Closing due to inactivity, feel free to reopen if you've tried the solution listed above and are still running into this issue.


CocoaPods / Carthage support

Does team consider CocoaPods / Carthage support? I can make PR

Sure, why not. But I think we should wait until we tag a version of this (will do soon after Swift 5 gets released).
Does Carthage / CocoaPods have a way of taking the version number from the SwiftPM tags? In SwiftNIO we just build everything with a script so we don't need to check lots of podspecs into our repo.

@weissi

Does Carthage / CocoaPods have a way of taking the version number from the SwiftPM tags?

I don't think that this's supported. So I think SwiftNIO similar scripts is the best option.

@weissi

Does Carthage / CocoaPods have a way of taking the version number from the SwiftPM tags?

I don't think that this's supported. So I think SwiftNIO similar scripts is the best option.

Cool, I'll add a script for CocoaPods when we've tagged a version. It will be much simpler than the SwiftNIO one because we only got one module here so we don't need to figure out the dependencies between the modules.

@weissi thanks!

Any status on this? 🚀

bump. Now 1.0.0 released, time for cocoapods?

@shuoli84 / @larryonoff does #54 look about right?

@weissi please see my feedback in PR #54 .

the Logging pod is now live: https://cocoapods.org/pods/Logging

@weissi is Carthage support something that you are open to adding? We're currently transitioning all our CocoaPods dependencies to Carthage so are hesitant to add new CocoaPods-only deps 😬

Xcode 11 supports Swift Package Manager now, is that an option?

Unfortunately, we are actively shipping this app and I don't think that you can submit Xcode 11 compiled apps to the app store until it exits beta.
The next problem is that many of our dependencies don't currently support SwiftPM so we'll probably have to stick with Carthage for a while more, and I would prefer not to mix too many package managers into the mix. The long term goal for is probably CocoaPods -> Carthage -> SwiftPM though, but until we have moved all pods to Carthage I would prefer it not to bring in SwiftPM.
That being said though, long term I 100% think that SwiftPM will solve all of these problems, and I understand if you don't want to support Carthage in the meantime. I would be very happy if you did though ❤

@LinusU I have had someone using NIO with Carthage and it wasn't an issue so I know it works without doing any changes to NIO itself. Let me get some more info for you.

@weissi I (and I would assume many others) would be interested in a way to use swift-log thru carthage. Do you have any more info on this or a short example to point to?
That would be highly appreciated.

@weissi   Can you update pod spec to 1.5.2, and push it to the trunk.
Further run the scrip to do this automatically when release a new version？

@ktoso / @tomerd / @Lukasa is Cocoapods still supported? I thought that's gone now?

No, you’re right — we don’t support it. Haven’t for a long time I think.


Dedicated URL for data

This would allow independent builds so that updates to the website would be faster.
Need to considering caching / cachebusting considerations.

Can't quite do this. GitHub pages does have CORS set to access-control-allow-origin = * but not for the OPTIONS method. Firefox and Safari use OPTIONS to preflight some xhr requests and fail. Chrome works, but Chrome as a requirement is not acceptable.
Did change workflow on website to just pull the DB files from db.gmrs.app and rescheduled the weekly website build process to run 1 hour later than the DB build process. While this still does have to copy the files from the site, build them into the artifact, and deploy them to GitHub Pages, it does save a lot of time over downloading flat files from the FCC and parsing them into the the DB. New process merged in #18
Might revisit using the site directly in the future if GitHub Pages changes the CORS headers served for OPTIONS method.


Add information about 2019 meeting

Information about the May 2019 meeting should be added to the meetings page.

Done.


Linked services do not get populated properly when you edit a container

Rancher versions:
rancher/server: 1.5.10
rancher/agent: 1.2.2
If you edit a container directly in the UI that has linked services (whether in the same stack or others) it will not populate the dropdowns.

Container links are to a specific container instance.  If you're linking to an instance created by a service and that service is upgraded, a healthcheck fails, or any other condition that causes that container to be replaced, it's no longer the same container and that link is now to nowhere.
You're talking about stack and service though, so container links don't even make any sense.
What's happening is:

You create service A with scale=3
3 containers for stack-A-1 (1i42), stack-A-2 (1i43), stack-A-3 (1i44)
You create service B with scale=1 and link to A
A container is created for stack-B-1, it has a single instance link to one of the three A containers (randomly?)
A is upgraded, so 1i42/43/44 is deleted and replaced with new ones
B now has an instanceLink pointed at 1i42, which no longer exists
On edit no instance matches 1i42, so nothing is selected in the dropdown

@alena1108 why are service links even creating instanceLinks?

Fair enough @vincent99, it seemed like a bug, if not so be it, just trying to report inconsistencies. I though this was like the service dropdowns in the catalog not populating back to their configured values on update or change.

It is a bug, but I think the bug is that instance links show up at all...

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


Feature to disable/prevent popover from opening

Bug, feature request, or proposal:
Feature request.
What is the expected behaviour?
Expected to disable popover from showing based on some conditions, for example, if editing is disabled.
[mdePopoverDisabled]="true/false"
What is the current behaviour?
Currently I am using onPopoverOpen method to pass some data from view like this:

{{item.name}}

In some cases I don't want popover to be shown, for example, when edit mode is disabled. To achieve my goal I use very ugly and blinking hack:
showDetails(item: Item) {
    if (!this.editMode) {
        this.trigger.closePopover();
    }
    ...
}

What are the steps to reproduce?
Provide a working example using StackBlitz (or similar) to reproduce the problem.
StackBlitz Template: https://stackblitz.com/fork/mde-popover
What is the use-case or motivation for changing an existing behaviour?
There might be some cases where popover must be disabled (not shown) on click or hover, but in other cases it should be fully functional based on some conditions.
Which versions of Angular, Material-Extended, OS, TypeScript, browsers are affected?
Other Comments

@6matko
Thanks for the feature request.
I agree this should be added ASAP. I can see so many use cases for this. I think it should also work using [disabled] to work with the native disabled attribute. This would then work with the button disabled etc.
Do you think that sound reasonable?

Yes, it would be really reasonable. In my current case I don't use button, so [disabled] property might not work, but in button cases it would be great solution. Additionally in my personal case I run into a problem with arrow (I don't need an arrow). Maybe similar feature can be added also to disable arrow, for example, arrowWidth = 0?

@6matko
I will add that today, I've just seen that the latest @angular/cdk was released last night so I will upgrade for compatibility with that too. So this feature will only work with the latest @angular/cdk, I hope that won't be a problem.
If you want disabled like features on custom elements you need to add accessibility attributes and the correct styles yourself to accomplish the same effect as native elements. I will leave that to the developers, I can add examples of the correct accessibility setup to use on none native elements.
Hmm I will look into that, I remember that you can use the [mdePopoverOverlapTrigger] which actually by default is set to true and then you use offset if you want it to offset. What happens when you use arrow width 0? I can't remember but in theory that should work unless it has a problem with the math part when using that, I would need to test that to see what the problem is.
If `[arrowWidth]="0" doesn't work then please create an issue with an example using StackBlitz and I will look into that once I've published it to work with the latest CDK.

@6matko
I just had a think about this and how disabled works on other elements, it just uses CSS pointer-events: none; I'm not sure if this should actually be added to the logic and instead if you apply the attribute [disabled] and have the following CSS it will be disabled.
CSS
[disabled] {
  pointer-events: none;
}

/*
 * This prevents it from being disabled when it has the disabled attribute with a value of false.
 */
[disabled="false"] {
  pointer-events: initial;
}

HTML

Hover Popover

I've also added the correct accessibility attributes to the trigger element. Let me know how you get on using that method. I will add to documentation soon.

@joejordanbrown Yes, the disabled property is working and fits my current use case, thank you! :)
I will play around with [arrowWidth]="0" more and if it wont help create a new issue, as you said.


RAM is increasing while doing batches via API and workers

Bug Description
Hello,
I am doing calls via API,
Server was using 7.3GB of RAM
now it is using 8.33GB of RAM
Seems like there still is a leak in 1.1 version
Seems like issue was also in the past.
Reproduction
Just running API calls.
Installation was made via pip installation.
SQLite db.
Running 6 workers.
Expected behavior
RAM should not increase drastically while running API calls.
Who can help?
No response
Operating System
Ubuntu 22.04
Langflow Version
1.1
Python Version
None
Screenshot
No response
Flow File
No response

RAM usage grew to 19GB of RAM, abnormal


Merge prTesting_202006251926 branch to master branch

Docs Build status updates of commit a54b9b6:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

split/updateTestCon.md
:warning:Warning

Details

split/updateTestCon.md

Line 0: [Warning-h1-not-first] Markdown content is not allowed before H1.
Line 1: [Suggestion-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning around July 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


chore: update iaas

The manual fix for allowed addresses is included?

The manual fix for allowed addresses is included?

Yes


Fuzz with foundry custom setup is not targeting all the targetContracts

Hi, i am trying some onchain fuzzing with a custom test, and I think ityfuzz is not working as intended.
My goal is to use ityFuzz to see if this Platypus exploit could have been found.
One of the contracts to fuzz, PlatypusPool = 0x4658EA7e9960D6158a261104aAA160cC953bb6ba is not getting fuzzed for some reason. However if i run it with ityfuzz evm -t 0x4658EA7e9960D6158a261104aAA160cC953bb6ba,0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7 -f -c AVALANCHE --onchain-block-number 36346397 --onchain-etherscan-api-key <SNOWTRACE_API_KEY> the contract gets targeted and the correct functions are called, like swap().
Here is the test, I am running it with ityfuzz evm -m OnchainTest -k <SNOWTRACE_API_KEY> -- forge build
// SPDX-License-Identifier: UNLICENSED
pragma solidity 0.8.23;

import {Test} from "forge-std/Test.sol";
import {console} from "forge-std/console.sol";

interface IERC20 {
    function approve(address spender, uint256 value) external returns (bool);
    function transfer(address to, uint256 value) external returns (bool);
    function transferFrom(address from, address to, uint256 value) external returns (bool);
    function withdraw(uint256 wad) external;
    function deposit(uint256 wad) external returns (bool);
}

// ityfuzz evm -m OnchainTest -k <ETHERSCAN_API_KEY> -- forge build
// ityfuzz evm -t 0x4658EA7e9960D6158a261104aAA160cC953bb6ba,0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7 -f -c AVALANCHE --onchain-block-number 36346397 --onchain-etherscan-api-key <ETHERSCAN_API_KEY>

contract OnchainTest is Test {
    address WAVAX = 0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7;
    address SAVAX = 0x2b2C81e08f1Af8835a78Bb2A90AE924ACE0eA4bE;
    address PlatypusPool = 0x4658EA7e9960D6158a261104aAA160cC953bb6ba;

    uint256 oldBalance;

    address caller;

    function setUp() public {
        vm.createSelectFork("https://rpc.ankr.com/avalanche", 36_346_397);

        targetContract(WAVAX);
        targetContract(PlatypusPool);

        vm.deal(address(this), 2000000 ether);

        oldBalance = address(this).balance;

        IERC20(WAVAX).approve(PlatypusPool, type(uint256).max);
        IERC20(SAVAX).approve(PlatypusPool, type(uint256).max);
    }

    function invariant_1() public {
        assertLe(address(this).balance, oldBalance);
    }
}

The command ityfuzz evm -m OnchainTest -k <SNOWTRACE_API_KEY> -- forge build conducts Offchain tests, requiring the target contracts to be local. Here's a quick rundown of how this command operates:

-k <SNOWTRACE_API_KEY> is optional, only necessary when Onchain flashloans are involved.
forge build is used to compile the targets, producing offchain_artifacts.
ityfuzz picks up the offchain_artifacts and deploys them on the local evm.
Start fuzzing.

Check out this example for reference: https://github.com/fuzzland/ityfuzz/blob/master/tests/evm_manual/foundry1/test/Counter.t.sol

I was trying to replicate how it was done for the StaxExploit test.
So what command would I use to fuzz onchain, if possible?

Shall be fixed with #469

After #469 ittyfuzz now picks up the target contracts abi and fuzzes as intended. Thank you @shouc


chore: rename deps

:tada: This PR is included in version 4.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Direct Line] Timeout 500: ECONNECTION timeout with some load with new state API implemented

Bot Info

SDK Platform: Node.js (8.9.0)
SDK Version: 1.13.1
Azure SDK Version (for table storage): 3.0.4
Active Channels: Direct Line
Deployment Environment: Auzure Bot Service (only channel registration and web app)
Bot id: a71cd44f-daf0-4b69-be5f-2ba5273df740
All servers published on EU West

Issue Description
Since the moment we started using the bot framework we have had random issues where the messages and the conversation requests returns 500 errors. We are about to go to production with the current bot and we did a load test to see how good or bad the bot can behave in different loads.
Here I will comment the findings to see if they can help to understand where the bottleneck is. Basically our setup is:

We have an azure server with the bot built with botbuilder in nodejs
The storage we are using is tablestorage. It works properly as I checked the messages with Storage Explorer

Code Example
To build our clients, we have created in our server requests to send info to directline. Those requests to the bot are:

/bot/messages -> The bot runs under this url
/bot/message -> Sends a certain message to the bot. Attached the code.

BotHttpRequest.use(BOT_URL)
            .url(`/conversations/${message.conversationId}/activities`)
            .method('POST')
            .headers({
                Authorization: `Bearer ${directLineToken}`
            })
            .body({
                text: message.message,
                type: message.messageType,
                from: {
                    id: currentUser.registrationId,
                    name: currentUser.name
                }
            })
            .retries(3)
            .send()
            .then(function (response) {
                return response.data
            })

/bot/convesation -> Starts a new conversation with the bot. The code is as follows:

BotHttpRequest.use(BOT_URL)
            .url('/conversations')
            .method('POST')
            .headers({
                Authorization: `Bearer ${directLineAuth}`
            })
            .send()
            .then(function (response) {
                return response.data
            })
            .then((data) => {
              // Send empty message so the conversationUpdate is triggered on the bot and adds the current user.
              // Otherwise, the current user will not be in the conversation and the greetings will not be triggered.
              const message = new BotMessageRequest({
                message: "",
                conversationId: data.conversationId,
                messageType: "message"
              })
              return this.sendMessage(message, currentUser, `BotConnector ${data.token}`).then(() => {
                return data
              })
            })

All this code works for small amount of requests but as long as it grows a bit (not too much), it just gets broken.
Issues
With this setup we did a test with a middle size machine from azure and this are the findings (test done with jmeter, 300 users, 5 requests per user):

64.81% of requests OK vs 35.19% KO
100% of the errors where error 500
The response time per message is around 16s
Most of the errors are ECONNECTION Timeout 15000ms (we also tried to increase the timeout with the same result, which means this error is sent internally from your backend)
The total amount of requests done where 4262

Some errors we have seen in the server:
Error 1
ActivityId: 47bb6c41-0000-0000-0000-000000000000, Request URI: /apps/63e70998-1c00-470e-8093-b4ef0dac16b1/services/be412ef7-0aa4-462c-90cc-2ae92aeb435e/partitions/7b23a94a-4102-4a9e-9333-ee80a73e77fe/replicas/131556435222707878p/, RequestStats: , SDK: Microsoft.Azure.Documents.Common/<IP_ADDRESS>
    at Function.MongoError.create (D:\home\site\wwwroot\future-street\node_modules\mongodb-core\lib\error.js:31:11)
    at D:\home\site\wwwroot\future-street\node_modules\mongodb-core\lib\connection\pool.js:497:72
    at authenticateStragglers (D:\home\site\wwwroot\future-street\node_modules\mongodb-core\lib\connection\pool.js:443:16)
    at Connection.messageHandler (D:\home\site\wwwroot\future-street\node_modules\mongodb-core\lib\connection\pool.js:477:5)
    at TLSSocket.<anonymous> (D:\home\site\wwwroot\future-street\node_modules\mongodb-core\lib\connection\connection.js:331:22)
    at ZoneDelegate.invokeTask (D:\home\site\wwwroot\future-street\node_modules\zone.js\dist\zone-node.js:275:35)
    at Zone.runTask (D:\home\site\wwwroot\future-street\node_modules\zone.js\dist\zone-node.js:151:47)
    at TLSSocket.ZoneTask.invoke (D:\home\site\wwwroot\future-street\node_modules\zone.js\dist\zone-node.js:345:33)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at TLSSocket.Readable.push (_stream_readable.js:208:10)
    at TLSWrap.onread (net.js:594:20)

Error 2
Error: connect ETIMEDOUT <IP_ADDRESS>:443
    at AppInsightsAsyncCorrelatedErrorWrapper.ZoneAwareError (D:\home\site\wwwroot\future-street\node_modules\zone.js\dist\zone-node.js:811:33)
    at new AppInsightsAsyncCorrelatedErrorWrapper (D:\home\site\wwwroot\future-street\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:172:18)
    at Object._errnoException (util.js:1024:11)
    at _exceptionWithHostPort (util.js:1046:20)

(We also did a test disabling the bot insights correlation with no change on this)
In the report attached you will also see create anonymous and login, those are calls for our and those doesn't have any impact on the test.
Please let us know a way to reduce those numbers since those are not acceptable for a production ready bot.
Thanks for the support and best regards.
Bot performance test results.zip

More logs of what happens in the server with load:

2 observations about the data in the last post:

Direct Line received a message for conversation B8ccwE73neT8Jz5M9Dv5Ei from the client at 2018-02-01T09:50:18.255, tried to post it to the bot and got an HTTP 500.

You mentioned that increasing the CPU on the bot server helped. It may be that the server is still overloaded and cannot process the requests. Traffic to the bot is very bursty.

The InternalServerError for the 2018-02-01T09:51:01.773Z post. Direct Line received that post and processed it fine. It was not Direct Line that returned the "timeout of 1ms exceeded" error. 1ms?! That's a bit optimistic.

Both cases look to be issues on the bot side. I suggest looking at scaling up or our your bot and tracking down who's setting that 1ms timeout.
You're right about the 15 second timeout: that is the time allowed for bot to respond to a message. If the bot is busy and cannot respond then Direct Line will time out the request.

We are experiencing exactly the same Connect ETIMEDOUT <IP_ADDRESS>:443 error under high load. Bot is running in Web App Bot/App service environment. Interesting thing regarding @vincec-msft last post is that CPU load is constantly under 10%, so it seems like a problem on side of directline.botframework.com service. What logs should we provide to support the solution?

Are you on the latest BotBuilder release?
(v3.14 https://www.npmjs.com/package/botbuilder)
We have the following recommendations:

Use the AgentKeepAlive NPM package https://www.npmjs.com/package/agentkeepalive to ensure re-use of the SSL Connections.
Tune the MaxSockets parameter of the AgentKeepAlive to be at least 160 to match the number of SNAT port.

Note: If you have set IISNode nodeProcessCountPerApplication="0" to use all CPU’s for the Node Process then you will need to adjust the MaxSockets accordingly.
So on a 4 CPU instance size (P4) you will have 4 Node Processes so MaxSockets will need to be set to 40 .
References
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-outbound-connections
https://blogs.msdn.microsoft.com/mast/2015/07/13/azure-snat/
Please let us know if this resolves the issue for you?

Thank you very much for these clues, Eric. We will try them out as soon as possible and let you know it it resolved the issue.

We did some performance testing with agentkeepalive set into https.globalAgent (because lack of way to inject custom agent into the ChatConnector class of botbuilder package responsible for failed requests) with MaxSocket set regarding your recommendation.
And it looks it helped! No ETIMEDOUT errors anymore even during double request per second rate than before. I just hope that the reason is not just some error in performance testing process. Thank you very much for your help, @EricDahlvang .

I actually just provided the code @vincec-msft gave me, so he deserves your thanks.
We've also provided a blog post describing the workaround: https://blog.botframework.com/2018/03/05/fix-snat-exhaustion-node-js-bots/
I'm glad this has been resolved.  Closing the issue.

We are also testing the global agent thing. Maybe using the global helps.

@dvorakjan Could you please share the code snippet you used to configure the keepaliveagent module with the botframework.

@vamzz1 Of course, here you are.
const HttpAgent = require('agentkeepalive')
const HttpsAgent = require('agentkeepalive').HttpsAgent

// enable request keepalive to reuse connections and set sockets count to match the number of SNAT port
const nodeProcesses = process.env.NodeProcesses || 1
const maxSockets = 160 / nodeProcessCount
http.globalAgent = new HttpAgent({ maxSockets })
https.globalAgent = new HttpsAgent({ maxSockets })


add parallel/regularized ALS estimation

@matbuechner I've made some changes which do the following:

Add parallel estimation for the factors
Add regularized estimation for the Gammas

There are a couple of key points to note:

The elastic net estimation for Gamma is easiest when we work off the original panel.  As a result, I've kept a copy of that in the IPCARegressor class.  Currently, I'm using the panel for all Gamma estimation variants.
However, after I put this together, I realized that that breaks the p-values.  It may make the most sense to carry around a copy of both the full panel and the portfolios, though you may have some ideas for an easy way to just keep one.  I'm going to experiment with this further.

Currently, I've split the ALS procedure for PSF cases from the base case (which cuts down on the if statements).  That said, I'm rethinking whether this is the right choice, and will likely rejoin these to clean things up.

To handle the elastic net, I'm currently using sklearn's implementation:
https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.ElasticNet.html
This obviously adds another dependency but if there is going to be regularized estimation at all this seems unavoidable.

Overall, let me know if you have any thoughts.
Further things I'd like to do before this is merged:

[x] Add some formal tests for the regularized estimation
[x] Determine how best to handle the portfolio/panel data
[x] Rejoin PSF/base ALS functions

@lbybee, thanks for adding those features!
Regarding your points:

I am happy to carry around a copy of both panel and portfolios. It may not be memory efficient, but I appreciate the need for access to both.
I am in favour of keeping both PSF and base case together if possible. If there is another way to cut down on the if-statements, do let me know.
Adding sklearn as an additional dependency is fine by me.

Ok, this should be ready, couple of quick comments before I merge:

I changed the variable P to Panel to help distinguish it from the scalar variables (T, K, etc.)
Since the bootstrap requires the portfolio inputs while the regularized estimation requires the panel, currently, you can't fit the bootstrap to the results of a regularized run.  This technically should be possible but it'll require a little more thought (also doesn't seem like a super high priority).


adapt to new mittagstisch layout

something must have changed. is the closedDays-thing even still needed?

Please do not merge this. While it may work for the current week, it will break in the next week, if the "Wochenangebot" is introduced again. See here for a comparison on how the usual page looks like.
I will rework the Mittagstisch scraping in a robust way that can handle both cases. I'll open a new PR for that.


Calls to dice_roll are very slow

Hi, I was using thing library and was getting quite slow speeds so I checked the source code and it seems like you are creating a cached_generator for every call to dice_roll here:
https://github.com/identex/quantumrand/blob/0baaf1b94f74ae5b860a263d880f344d032879e0/quantumrand/__init__.py#L148
Forgive me if I am wrong but isn't that doing the opposite of what its supposed to, slowing down instead of speeding up further calls?

Hi @sujaldev, thanks for raising this issue.
This was meant to fetch a seed from ANU's server and use that seed locally multiple times. However, it appears to be an oversight on my end. I see your PR and will review and potentially merge soon.

This is being uploaded to PyPi now.


Suggestion:Unlimited Output From Power Outputs

Right now the max output seems to be capped at 1,000,000 rf/t per power tap but i think it would be nice if it can output an unlimited amount so you just use one and not have to fill up all of the walls of to get max output that reactor and/or turbine is creating.

with some more testing it seems that the whole reactor is capped at 10,000,00 rf/t output so after adding 10 power taps adding more is useless

well my 32x48x32 reactor only output a little iver 1,000,000 rf so i have no worry's about this.

Im plating with rotarycraft as my the main mod for automation and ore processing and the magneostatic engines consume almost 200,000 rf/t and i'll need quite a few of these as RF is easier to transport the shaft power. So I turned up my production in my config and thats when i learned about the cap

well 50 per reactor doesn't sound to bad. also the only way to fix this is by increasing the max power the reactor can hold to over 10,000,000 before that id flushed out and having 10 ports in not that many. if it was 100 that would be a problem.


visual tree

Is there a way to visualize the behavior tree or create a new tree with nodes etc?

Unfortunately no. Something like that would be nice to have though!

Is there a way to visualize the behavior tree or create a new tree with nodes etc?

Unfortunately no. Something like that would be very useful to have though!

Is there a way to visualize the behavior tree or create a new tree with nodes etc?

Unfortunately no. Something like that would be very useful to have though!

if you have time to do that, we can develop it as a template together.
I use both UniTask and DI (zenject or vcontainer) in my projects as default and it will be such a good solution to work with visual graphs, behavior trees etc. I don't have enough time to develop such a system alone.


 For any project related communication, please write a comment under the issue that you are working on e.g. if you have a problem with a task in week 1, you would write a comment in the issue under week 1 and similar for all other weeks.
Please @ me when you need me to attend to something so that I can get a notification and I will do the same.
Please make sure that everybody in your team and the mentor has accepted the git invite and are added to the project.
Good Luck

Hi @mmhashatsi just some clarity on the timeline, is week 1 until Sunday?
And some clarity on the task for week one, is it just to redeploy our cluster and read-up/prep for tasks for the following weeks?
Regards

Hey @DCSpear,
Yes week 1 would be until Sunday 27th and the task for the week is to redeploy the cluster using the Selection Round Content and prep as you said


Rename the repository to std

The maintainers are considering to rename the repository from deno_std to std. Let us know if you have any concerns.

done


Including an image in Octopress 3

I've been having difficulty including a picture in a post using Octopress 3. I've looked into some of the available plugins, and they are all written for Octopress 2. I've also tried using Liquid tags, a la
 {% img {{root_url}} /images/image.png 'alt' %}, and other variations like linking to the diagram directly.
I have not been able to embed an image in a post using Octopress 3 once. Any help would be much appreciated.

Something like {% img right /assets/images/travis-ci1.png Where to put the key. %} should work.

That worked, thanks! I'm not sure why that particular path worked. I tried something like
{% img left /source/images/image.png 'diagram' %}, and that didn't work. Does it have to be the path you wrote, or did I just type something wrong?

It shouldn't need to be that path, you might have just mistyped something.

That is definitely the dumbest thing I've done all day. Thanks! (and I've discovered I can't type)


TypeError: expected str, bytes or os.PathLike object, not NoneType

Unable to install pemja on raspberry pi, tried with python 3.7 and 3.9
Steps to reproduce:
$ virtualenv -p /usr/bin/python3.9 venv3.9
$ source venv3.9/bin/activate
$ python --version
Python 3.9.0
$ pip --version
pip 22.1.1 from /home/pi/venv3.9/lib/python3.9/site-packages/pip (python 3.9)

$ pip install pemja

Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pemja
  Downloading pemja-0.1.5.tar.gz (32 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-iqprsatx/pemja_afa58ffaf082492bb729b5377e1491da/setup.py", line 185, in <module>
          include_dirs=get_java_include() + ['src/main/c/pemja/core/include'] + get_numpy_include(),
        File "/tmp/pip-install-iqprsatx/pemja_afa58ffaf082492bb729b5377e1491da/setup.py", line 112, in get_java_include
          inc = os.path.join(get_java_home(), inc_name)
        File "/home/pi/venv3.9/lib/python3.9/posixpath.py", line 76, in join
          a = os.fspath(a)
      TypeError: expected str, bytes or os.PathLike object, not NoneType
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

Same error here, someone resolved this?

on window platform same error as is, but install successful on macos platform

@alexzhu0592 Could you share how you resolved it on macOS?

@alexzhu0592 Could you share how you resolved it on macOS?

no errors on macos,  just install by normal way like pip install pemja

@alexzhu0592 Could you share how you resolved it on macOS?

Maybe you can check your jdk version or python version which doc suggests

What's the os and hardware? m1 chip?

Seems to be an issue with how environment variable JAVA_HOME is set on some machines (i.e. I'm using a M1 chip + Linux).
The below command worked for me:
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-arm64

Okay so i did alot of testing with @jamesalford and it seems this is an error because of python 3.10.
If you install with python3.9 pemja installs fine.
it has nothing to do with java_home being set or not, but its a python issue

well，I met the issue in Python3.7，and because the source code of pemja set to fine 'JAVA_HOME', so I set 'JAVA_HOME' to solve the problem. Then install pemja successfully.


Implement a RedisMutex

Same as Memcache(d) but with Redis instead :)

Same as Memcache(d)

So it will be phpredis and Predis I guess. Also I will go this way then: http://redis.io/topics/distlock

Sweet :)

You have it now in version 0.3


The lane detection model is the multi-label and multi-task problem?

The lane detection model is the multi-label and multi-task problem?
And I really want to know what the probmaps  means

@FrancisGee The lane detection model has two branches. The problem could be viewed as a multi-task problem.
The last convolution layer of the model would output feature maps of 5 channels. When the 5 channels go through a softmax layer, they form the probmaps. Because for each pixel location, the values of the 5 channels indicate the probability that the pixel belongs to the 5 categories (background, lane marking 1-4).

@OneMondy

SCNN is added between fc7 and fc8 in Fig.5.
Interpx8 means enlarge the featuremap by 8 times (along height and width dimensions) with bilinear interpolation.
Yes, it's correct.


Call to undefined function Xiaoler\Blade\Concerns\tap()

I use version 5.4.1, get this error when use @stack @push @endpush, i fount this might be cause by miss of tap function in helper functions?

fixed.


Feat/format map

Description
This PR adds use of prettier to format generated map. PR also updates application code formatting to match default prettier config.
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have updated the documentation accordingly. For updating Oclif commands documentation use oclif-dev.
[ ] I have read the CONTRIBUTING document.
[ ] I haven't repeated the code. (DRY)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Ok, I will move map formatting.

Moved to engine: https://github.com/superfaceai/edgar-engine/pull/318
I would still like to merge formatting of application code.


Showcase page

Great project with a nice README and a samples! :clap: :clap: Would it be possible to add a simple web using GH pages with the live samples (as in the GIFs you tweet)? That would be very helpful for users to get a quick grasp of Fable.Reaction benefits.
Also, please don't forget to add a link to your project in awesome-fable so it's easier for other people to find it :)

Thanks @alfonsogarciacaro . Reaction started as a playground project to see if it would be possible to join the Elm-architecture with observables, and things are getting quite interesting so it looks like its turning into a real project. Still a bit confused about naming, if the project should be called Fable.Reaction or Elmish.Reaction and if the nuget should perhaps be called Fable.Elmish.Reaction. Decided to go for Elmish event-loop instead of rolling my own just a day ago, so the dust haven't settled yet. But it's a good idea to add a GH-page to show the demos (live) and better explain how things work.

Indeed, this is a very promising projects. I've had issues myself when reacting to event streams in Elmish projects, so it would be awesome if you could combine both projects! About the name, Fable.Elmish changed it to Elmish when it started to be applied in other platforms (Xamarin, WPF). If you want to fuse it with Elmish and it can potentially be applied to other platform, Elmish.Reaction is a good candidate (as you say, the nuget can keep the Fable prefix) :+1:

There's actually been some progress to this issue 😄 I've been struggling with finding the right tooling and hosting for the docs, but after working on RxPY for a few months I've decided to move the docs to Sphinx and Read The Docs, which also makes it easier to add custom Css and Js. Still some work left to make things look good, but consider this a first POC:
https://fablereaction.readthedocs.io/en/latest/fable.elmish/demo.html


[solidjs-pod] tech-debt in auth flow

The current setup as implemented in #734 works, but could use some love.

The usage for createResource is a little verbose, it would be nice if we didn't need to wrap in additional try-catch statements, as well as being able to drop the return empty promise.
The user makes a round-trip to the signin page, should we show that it's currently authenticating there? (very fast users might click the button)
Setting the auth token is tightly coupled with the signing page. These should be separated.

I believe this ticket has already been taken care of, with the refactoring we have done the last time.


[Firebase 11] Audit FIAM API tests for potential improvement opportunities

Description
See todos in https://github.com/firebase/firebase-ios-sdk/blob/main/FirebaseInAppMessaging/Swift/Tests/Unit/FirebaseInAppMessaging_APIBuildTests.swift
Reproducing the issue
No response
Firebase SDK Version
10.24
Xcode Version
15.2
Installation Method
Swift Package Manager
Firebase Product(s)
In-App Messaging
Targeted Platforms
All
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Merged #13089


Using the generated code for Xamarin.iOS

Hi,
Thank you for this work. I want to know if it's possible to use the generated interop code for Xamarin.iOS with the builded Library .a?

@abdelkader27 I have not done the work for iOS at this point, but I don't see why this wouldn't work there as well. I do take contributions ;-)

See issue: https://github.com/dotMorten/AllJoynDotNet/issues/4

I'm trying to compile the source code for Xamarin.Android but there's some errors:

QStatus is not found

some casting error like comparaison of int and intptr

Is there Something to do with that?
thanks.


Achievement: Dashboard UI Update & Bug Fixes 2

Description
Follow up of https://github.com/source-academy/cadet-frontend/pull/1419
Tested: Chrome v84, Edge v84, Firefox v79

Pull Request Test Coverage Report for Build 7002

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 34.152%

Totals

Change from base Build 6986:
0.01%

Covered Lines:
2341

Relevant Lines:
6375

💛  - Coveralls


Bug: Problems with QueryBuilder when run multiple queries one by one

I have several tables:

hotel - contains hotels
hotel_translation - contains multilingual fields of hotels (many-to-one to hotel)
hotel_photo - contains photos of hotels (many-to-one to hotel)
hotel_photo_translation - contains multilingual descriptions of photos (many-to-one to hotel_photo)

First I generate query to get all hotels with their translations on one language (id_lan = 1):
$hotels = $this->builder('hotel h')
    ->select('h.id_hotel, ht.name', false)
    ->from('hotel_translation ht')
    ->where('h.active', 'true', false)
    ->where('ht.id_hotel', 'h.id_hotel', false)
    ->where('ht.id_lan', 1, false)
    ->get()
    ->getResult();

The query is:
SELECT h.id_hotel, ht.name
FROM "hotel" "h", "hotel_translation" "ht"
WHERE h.active = true
AND ht.id_hotel = h.id_hotel
AND ht.id_lan = 1

That's OK!
After that I want to handle the result with foreach and get photos of each hotel with translation:
$photos = $this->builder('hotel_photo hp')
    ->select('hp.photo_path, hpt.description', false)
    ->from('hotel_photo_translation hpt')
    ->where('hp.id_hotel', 1, false)
    ->where('hpt.id_hotel_photo', 'hp.id_hotel_photo', false)
    ->where('hpt.id_lan', 1, false)
    ->get()
    ->getResult();

But it generates wrong query:
SELECT hp.photo_path, hpt.description
FROM "hotel" "h", "hotel_translation" "ht", "hotel_photo_translation" "hpt"
WHERE hp.id_hotel = 1
AND hpt.id_hotel_photo = hp.id_hotel_photo
AND hpt.id_lan = 1

instead of what I expect:
SELECT hp.photo_path, hpt.description
FROM "hotel_photo" "hp", "hotel_photo_translation" "hpt"
WHERE hp.id_hotel = 1
AND hpt.id_hotel_photo = hp.id_hotel_photo
AND hpt.id_lan = 1

The problem is that when I initialize builder() in the second time with other table, this table is ignore (hotel_photo in my case) and in the second query are presents all tables from the first query (hotel and hotel_translation in my case).
It's a critical issue. Or maybe I'm doing something wrong?

I think it’s not very convenient to specify one table in initialization of builder() and the others in from() method. It would be clearer to call builder() without parameters and to specify all tables in from() (I mean situation with several tables in FROM clause). At least to have such an opportunity (now when trying to call builder() without parameter, an error is raised).

Also I found that $QBFrom property of class \CodeIgniter\Database\BaseBuilder is never resets. I guess its should be added to resetSelect() method of this class.

Partially it's a bug related to resetting from part of the query.
But you also assume that the builder method in Model works differently than it actually does. You should use this method with a parameter only once because every other call will return a shared instance.
So your second query should look like this:
$photos = $this->builder()
    ->select('hp.photo_path, hpt.description', false)
    ->from('hotel_photo hp, hotel_photo_translation hpt', true)
    ...

@michalsn thank you for your reply.
Your answer showed me to find a solution - set true as the second parameter to from method (always?). Its force overwrite QBFrom.
But still, it is somehow inconvenient - in the first query should specify the table in the builder(), but in the second one - not. Model may not be tied to one entity/table, but may be common to several tables - in this case there is no "main" table that needs to be specified when initializing the builder().

Besides if set true as the second parameter to from() in the first query then query failed - missing FROM-clause entry for table "h" (hotel).
So it’s really complicated - when you need to set the table in builder() and do not set true infrom()and when you need to do the opposite.

Regarding the second parameter in from() method - use it only when you need it. In your case, it will be only the second call. It's not really complicated, you just have to take some time to realize what is happening under the hood.
I think that builder() method was created to make life easier for developers - in many cases. You can call is a shortcut? When things become more complex as in your case, I would recommend using a new instance of BaseBuilder every time. In your model you can call it like this:
$builder = $this->db->table('my_table1');
...
$builder = $this->db->table('my_table2');

That should make it easief for you.

Thank you very much. This is really what I wanted.


Appointment

Tuesday, 13:00
@jarrodmillman

It looks like you haven't made any progress this week.  I am getting worried that you won't have much accomplished by the end of the semester, if you don't start working on your project soon.  Also if you don't have any preliminary results when we meet on Tuesday, it will be difficult to provide you with useful feedback.
Remember the project is 55% of your grade.
Please review the grading criteria:
http://www.jarrodmillman.com/rcsds/notes/rubric.pdf
As well as my comments from lecture 22:
http://www.jarrodmillman.com/rcsds/lectures/day22.html


Automate Redshift cluster creation

Automate Redshift cluster creation step in example dag of operator RedshiftPauseClusterOperatorAsync and RedshiftSQLOperatorAsync. Currently, the cluster creation and cluster deletion manual i.e both examples assume that there is already a Redshift cluster running in AWS and once the example dag execution is complete someone will manually delete it or it will keep running so it makes sense to add the first task in DAG to create cluster and last task to delete it. Currently, we do not have any operator to create a redshift cluster and delete it so for time being we can use BashOperator or PythonOperator. This change will make both DAGs running in more automated way
Acceptance Criteria:

[x] example dag for RedshiftPauseClusterOperatorAsync operator should be self-sufficient
[ ] example dag for RedshiftSQLOperatorAsync operator should be self-sufficient

example_async_redshift_cluster_management is now running standalone but for example_async_redshift_sql getting permission issue
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1334, in _run_raw_task
    self._execute_task_with_callbacks(context)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1460, in _execute_task_with_callbacks
    result = self._execute_task(context, self.task)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1516, in _execute_task
    result = execute_callable(context=context)
  File "/usr/local/lib/python3.9/site-packages/astronomer/providers/amazon/aws/operators/redshift_sql.py", line 51, in execute_complete
    raise AirflowException(msg)
airflow.exceptions.AirflowException: Error: CREATE OR REPLACE FUNCTION janky_sleep (x float) RETURNS bool IMMUTABLE as $$
                from time import sleep
                sleep(x)
                return True
            $$ LANGUAGE plpythonu; query Failed due to, ERROR: permission denied for language plpythonu

To create UDF in plpythonu (Python) language and run it require a special privilege because it is not a trusted language for this use case. run select * from pg_language in query console to list language and check trusted or not.So using plpgsql procedure and looping 500k times to delay.  https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_FUNCTION.html .

Can you please update on the status for RedshiftSQLOperatorAsync


St. Louis County - Letter to Mayors and City Councillors

Elected officials of St. Louis County:
I am [YOUR NAME], a resident of [CITY]. I demand the defunding and disbanding of St. Louis County police departments. I hold you accountable as county representatives to advocate for the reallocation of funding towards opening social worker positions and de-escalation and mental health support training programs. St. Louis County must stop increasing the annual police budget and instead invest in community-led measures to put an end to the systemically racist policing forces which have targeted, brutalized, and contributed to the oppression of people of color, especially Black people in our communities and country.
According to a recent KBIA article, Chief of Police Mary Barton has said that officers are already required to report when fellow officers don’t follow department policy on things like use of force, and will limit inappropriate jokes among officers. However, these have proven time and time again to be ineffective approaches to changing the “culture”' of policing while not addressing the system in which policing itself is couched. In the same interview, Barton said “...I think to say that there’s systemic racism in the police department is overly broad and probably not accurate.” From its origins as a body which oversaw runaway enslaved peoples and now incarcerates Black people en masse, the police are a racist body which have not strayed far from this history. The racist inherent in this system is undeniable, and Barton’s claim is frankly absurd and indeed shameful for a representative of the department responsible for the murder of Michael Brown. I ask that city councillors and local mayors stand in firm opposition to Mayor Barton and make immediate change to our policing system.
As a constituent, I cannot rely on the SLCPD to self-evaluate. I can never forget Michael Brown, who was murdered by later acquitted Ferguson police officer Darren Wilson 2014, recharging the nationwide conversation on police brutality. Since 2014, police departments have continued to fail their community and show no sign of reform despite the efforts Barton claims the department has made. Florissant officer Joshua Smith brutally ran down a suspect, a Black man, with his car, for a crime he did not commit. Joshua Smith was sued for shooting a man in 2015 for shooting another man in 2013, which internal investigations ruled a “suicide” and Abayomi “Alan” Afolabi’s family contests. Smith has merely been fired from his position after spending several days on review with pay, without guarantee by systems in place that he will be rehired by another department. In March 2020, Marvia Gray, a 68 year old Black woman, was falsely accused of stealing at a Des Peres Sam’s Club. Four officers permanently injured her while giving her 43-year-old son, Derek, a concussion and three shattered teeth. No disciplinary action has been taken against these officers, who after beating Marvia and her son, still pursued charges for resisting arrest for the crime she did not commit.
There are countless more examples of wrongful death and brutalization of Black people in this county. It is not the job of police to try, convict, kill (or attempt to kill) suspects who have not been processed through the judicial system; yet time and time again, St. Louis County officers overstep the line of their responsibilities and terrorize with impunity. As we have seen, these are nationwide phenomena, and no amount of proposed reform will redress the senseless violence police officers are allowed to enact with impunity on defenseless citizens, many of them people of color.
The St. Louis County Police Department’s budget of $143 million this year has grown by 45% since 2014, an unreasonable amount in comparison to the $4.4 million budgeted for human services $1.3 million afforded to public housing initiatives. According to public records, in 2020, the only federal, state, or miscellaneous funds planned for mental health are through the police department. Direct taxpayer dollars towards helping your constituents. Shift money away from the police and towards areas of education, public housing, and healthcare which deserve attention and address the systemic issues behind crime as a survival tactic. I urge you to find sustainable solutions that work for the taxpayers of the St. Louis County community to build a better police-free future.
Sincerely,
[YOUR NAME]

Hi @mcgoetzke! Thanks for your interest in adding St. Louis County to the site. Would you mind replying here with email addresses of the government officials you'd like to receive this message?
Thank you!

For sure.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Reviewing now

Some minor edits below:

Send to<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Message:
Dear Elected officials of St. Louis County,
I am [YOUR NAME], a resident of [CITY]. I demand the defunding of St. Louis County police departments. I hold you accountable as county representatives to advocate for the reallocation of funding towards resources that are more effective at promoting a safe and equitable community, such as opening social worker positions and de-escalation and mental health support training programs. St. Louis County must stop increasing the annual police budget and instead invest in community-led measures to put an end to the systemically racist policing forces which have targeted, brutalized, and contributed to the oppression of people of color, especially Black people in our communities and country.
According to a recent KBIA article, Chief of Police Mary Barton has said that officers are already required to report when fellow officers don’t follow department policy on things like use of force, and will limit inappropriate jokes among officers. However, these have proven time and time again to be ineffective approaches to changing the “culture”' of policing while not addressing the system in which policing itself is couched. In the same interview, Barton said “...I think to say that there’s systemic racism in the police department is overly broad and probably not accurate.” From its origins as a body which oversaw runaway enslaved peoples and now incarcerates Black people en masse, the police are a racist body which have not strayed far from this history. The racism inherent in this system is undeniable, and Barton’s claim is frankly absurd and indeed shameful for a representative of the department responsible for the murder of Michael Brown. I ask that city councillors and local mayors stand in firm opposition to Mayor Barton and make immediate change to our policing system.
As a constituent, I cannot rely on the SLCPD to self-evaluate. I can never forget Michael Brown, who was murdered by later acquitted Ferguson police officer Darren Wilson 2014, recharging the nationwide conversation on police brutality. Since 2014, police departments have continued to fail their community and show no sign of reform despite the efforts Barton claims the department has made. Florissant officer Joshua Smith brutally ran down a Black man with his car, for a crime he did not commit. Joshua Smith was sued for shooting a man in 2015 for shooting another man in 2013, which internal investigations ruled a “suicide” and Abayomi “Alan” Afolabi’s family contests. Smith has merely been fired from his position after spending several days on review with pay, without guarantee by systems in place that he will be rehired by another department. In March 2020, Marvia Gray, a 68 year old Black woman, was falsely accused of stealing at a Des Peres Sam’s Club. Four officers permanently injured her while giving her 43-year-old son, Derek, a concussion and three shattered teeth. No disciplinary action has been taken against these officers, who after beating Marvia and her son, still pursued charges for resisting arrest for the crime she did not commit.
There are countless more examples of wrongful death and brutalization of Black people in this county. It is not the job of police to try, convict, kill, or attempt to kill suspects who have not been processed through the judicial system; yet time and time again, St. Louis County officers overstep the line of their responsibilities and terrorize with impunity. As we have seen, these are nationwide phenomena, and no amount of proposed reform will redress the senseless violence police officers are allowed to enact with impunity on defenseless citizens, many of them Black, Indigenous, or  People of Color.
The St. Louis County Police Department’s budget of $143 million this year has grown by 45% since 2014, an unreasonable amount in comparison to the $4.4 million budgeted for Human Services $1.3 million afforded to Public Housing Initiatives. According to public records, in 2020, the only federal, state, or miscellaneous funds planned for mental health are through the police department. Direct taxpayer dollars towards helping your constituents. Shift money away from the police and towards areas of education, public housing, and healthcare which deserve attention and address the systemic issues behind crime as a survival tactic. I urge you to find sustainable solutions that work for the taxpayers of the St. Louis County community to build a better police-free future.
Sincerely,
[YOUR NAME]
[YOUR ADDRESS]
[YOUR EMAIL]
[YOUR PHONE NUMBER]

on it


Skip vulnerability reports that are marked as "withdrawn"

The OSV format supports the withdrawn field, which indicates that a report has been withdrawn and is no longer valid.
pip-audit should respect that field and ignore any reports that contain it, so long as the field's timestamp is not after the current time.

This applies immediately to the OSV service backend, but may also apply to PyPI's vulnerability DB (which serves a functional subset of the OSV schema). I'll need to check what PyPI's updated does when a entry is marked as withdrawn.

(I identified this as part of looking into https://github.com/pytest-dev/py/issues/287 -- we "correctly" report this spam vulnerability at the moment because it isn't marked as withdrawn yet, but we should skip it if/when it's correctly withdrawn.)

https://github.com/pypa/pip-audit/pull/386 looks good to me but I think we should probably extend support for this to PyPI as well -- shall we create a separate issue for tracking that?

Yeah, I think so -- I can create that in a moment.

#388 is the continuation of this, for PyPI's vulnerability service.


update addressBook with entries by chainId

previously the address book was only keyed by address, so a user was only allowed to have one entry per address regardless of network

Codecov Report

Merging #152 into develop will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           develop   #152   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files           21     21
  Lines         1432   1435    +3
  Branches       192    193    +1
======================================
+ Hits          1432   1435    +3

Impacted Files
Coverage Δ

src/user/AddressBookController.ts
100% <100%> (ø)
: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 77071fd...55183b9. Read the comment docs.


[Feature] Upload file to DockerHub Description

It would be awesome if you could push a file like the README of the repo to the DockerHub description automatically.

You mean to here https://hub.docker.com/r/banzaicloud/drone-kaniko ?

Yes.

Sorry @annProg what it this program for exactly? :)

Sorry @annProg what it this program for exactly? :)

Update repo description(default use README.md) in Harbor. It is similar to DockerHub Description.for reference only

Screenshot in harbor


SUBSTRING and REGEXP_EXTRACT don't work with multi-value columns

I have a column (let's call it cities) containing multi multiple strings each, for example
["amsterdam", "berlin", "barcelona#prague"]
I need to split elements by '#' while still having a flat map, and then get the substring of the first n (let's say n=4) for each value.
The first step is done by
STRING_TO_MV(MV_TO_STRING(cities, '#'), '#'):
["amst", "berl", "barc", "prag"]
But in contrast to what the documentation says, SUBSTRING cannot be applied to the result:
SUBSTRING(STRING_TO_MV(MV_TO_STRING(cities, '#'), '#'), 1, 4):
[Lja (short of [Ljava.lang.String;@<hash>)
The result is the same for REGEXP_EXTRACT.
Affected Version
In 0.16.1, the result is as above
In 0.18.1, the method is also not applied to each value, but to the toString() of the array: ["am

Probably related to #8733

CONCAT and other String methods also seem not to work with multi-valued columns


[PostgrestClient] When building a query, should the return type only be async throws if we add .execute()?

Feature request
Is your feature request related to a problem? Please describe.
I'm building a reusable query builder for my application and I was wondering if it was necessary for SupabaseClient.PostgrestClient.PostgrestQueryBuilder to be async and throws without execute being called.
eg.)
This is a compile error because it doesn't precede with try await:
supabase.database.from("some_table")
Describe the solution you'd like
To me it makes sense if the response doesn't become async or throws until we actually execute the command. Otherwise, we're just storing the query in a var, which doesn't require async at least
eg.)
var query = supabase.database.from("some_table")
then
let response = try await query.execute().data
Additional context
Not sure if this breaks other parks of the SDK or if this is necessary so I apologize if that's the case!

Hey @ssadel thanks for this, that happens because PostgrestClient is an actor, so you need the async to get access to it.
I will change that so the async isn't needed, as it is a better interface.
Thanks!

makes sense! thanks!


Update deprecated versions of actions used

Update versions of actions used to fix several warnings (Node.js, deprecated versions etc.):

Update actions/upload-artifact to v4
Update actions/checkout to v4
Update badgerhobbs/terraform-state to v2
Update hashicorp/setup-terraform to v3

CI tests will fail until the PR is accepted and a v2 release is prepared. Downstream CI tests pass OK: https://github.com/AlexGidarakos/terraform-state/actions

Thanks for this PR, just one comment before happy to merge in.
Please correct me if I'm wrong, but I don't believe these are breaking changes, so the version can just be bumped to v1.1 instead of v2

Following Semantic Versioning, this is true. But due to the limited amount of testing, I'd feel better if these changes weren't automatically forced upon everyone already using badgerhobbs/terraform-state@v1.

Following Semantic Versioning, this is true. But due to the limited amount of testing, I'd feel better if these changes weren't automatically forced upon everyone already using badgerhobbs/terraform-state@v1.

Ok, the only other change then will be updating from v1 to v2 in the readme.

Updated expired access token, all actions passing.


Update Row-Level TTL docs to note full support

Fixes DOC-4756
Summary of changes:

Update 'Batch Delete Data with Row-Level TTL' page to note:

You can now do per-row TTL using ttl_expiration_expression, so we mention that and give examples, describe how it's validated

Remove at least the resolved limitations from the TTL docs and the 'Known Limitations' page

Remove uses of ttl_automatic_column which is no longer used in v22.2+

Update 'WITH storage_parameter' page to use new output / TTL params

Update 'RESET storage_parameter' page to use new output / TTL params

Update included table of storage parameters to remove duplication of TTL params, instead linking to the canonical location on the TTL docs page

This change is

@rafiss added you as reviewer alongside @ecwall b/c of https://github.com/cockroachdb/cockroach/pull/86269
let me know if you would rather not be added tho!
Pretty sure I caught most of the changes from reading PRs and playing with the DB but ... entirely possible I missed something.  Please let me know if so.  Also happy to make any other updates re: clarity, etc.  Thanks!

thanks @rmloveland ! two points before doing a deeper review:

@ecwall : are you planning to separate out the metrics name change in https://github.com/cockroachdb/cockroach/pull/89392/ and backport that to v22.2.0? (I think we should.) If so, then we can document that here too.
I noticed that we don't document the TTL metrics dashboard in the DB Console currently. I think we should add docs for that now.

thanks @rmloveland ! two points before doing a deeper review:

@ecwall : are you planning to separate out the metrics name change in ttl: Remove ttl_range_concurrency config cockroach#89392 and backport that to v22.2.0? (I think we should.) If so, then we can document that here too.
I noticed that we don't document the TTL metrics dashboard in the DB Console currently. I think we should add docs for that now.

Yeah it looks like some of the metrics are not working properly in the db console so I’m fixing that also.

Rafi Shamim @.***> writes:

thanks @rmloveland ! two points before doing a deeper review:

thanks Rafi!  Took a shot at addressing these points

@ecwall : are you planning to separate out the metrics name change
in cockroachdb/cockroach#89392 and backport that to v22.2.0? (I
think we should.) If so, then we can document that here too.

Updated in latest push to remove the TTL range concurrency thing

I noticed that we don't document the TTL metrics dashboard in the DB
Console currently. I think we should add docs for that now.

Ah ok, missed that.  Added a DB Console page on TTL dashboard!

Evan Wall @.***> writes:

Yeah it looks like some of the metrics are not working properly in the
db console so I’m fixing that also.

OK that explains why some of the charts are blank in this docs PR
despite me doing a bunch of TTL stuff to the DB.
(re: the blank charts, i'd like to update the screenshots in another PR

I'm under some time pressure to get a bunch of other things done
before the v22.2.0 release next month)

but with the other updates I just made this is RFAL now

per convo with @dikshant : I will update this PR to state that ttl_expiration_expression is preferred over ttl_expire_after starting with v22.2 for the following reasons:

if you add ttl_expire_after it will cause a full table rewrite.  you can't use this with an existing timestamp column
whereas ttl_expiration_expression can say "please expire based on this updated_at col that already exists" etc

@rafiss and @ecwall this has been updated with your feedback and the comment from @dikshant and should be RFAL


When embedding yt-dlp and setting ignoreerrors to True, it is desired to capture relevant error messages programmatically rather than just printing them to stderr.

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Requirements Explanation
When embedding yt-dlp for playlist URLs, to prevent the entire process from stopping due to an error in one of the videos, ignoreerrors is typically set to True. Even if an error occurs, the download continues for the next video, and any error messages for videos that could not be captured successfully are only printed directly to stderr.
from yt_dlp import YoutubeDL

URLS = ['https://www.youtube.com/watch?v=XXX&list=YYY']

ydl_opts = { "ignoreerrors": True }

with YoutubeDL(ydl_opts) as ydl:
    ydl.download(URLS)

I seem to be unable to find relevant error messages for failures during the download process in the ydl variable. It would be really helpful if there were a functionality similar to ydl.get_error_messages (This method does not exist; it is hypothetical).
Preliminary Solution
Before the development of this feature, I successfully achieved the functionality I needed using the built-in function redirect_stderr in Python 3.5. If anyone here is interested in this feature, I'll provide the code below for reference.
from yt_dlp import YoutubeDL
import io
from contextlib import redirect_stderr

URLS = ['https://www.youtube.com/watch?v=XXX&list=YYY']

ydl_opts = { "ignoreerrors": True }

with redirect_stderr(io.StringIO()) as errStrIO:
    with YoutubeDL(ydl_opts) as ydl:
        ydl.download(URLS)
errMsg = errStrIO.getvalue()

print(errMsg)

Below is an example content printed by errMsg.
WARNING: [youtube:tab] Incomplete yt initial data received. Retrying (1/3)...
WARNING: [youtube:tab] YouTube said: INFO - 4 unavailable videos are hidden
ERROR: [youtube] IOmNWXXXXX: Private video. Sign in if you've been granted access to this video
ERROR: [youtube] S3yVyXXXXX: Video unavailable. This video contains content from SME, who has blocked it in your country on copyright grounds
ERROR: [youtube] y0rxpXXXXX: Video unavailable. This video contains content from Molebeat, who has blocked it in your country on copyright grounds
ERROR: [youtube] FRivqXXXXX: Video unavailable. This video contains content from SME, who has blocked it in your country on copyright grounds

For detailed information about redirect_stderr, you can refer to contextlib.redirect_stderr(new_target)
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

Review the logger example in the documentation.

Thank you, dirkf, for reminding me of the logger example in the documentation. Using a logger is indeed a better and more flexible approach than redirect_stderr. Therefore, I have closed the Feature request. Thank you.

I noticed that the original logger in yt-dlp displays the progress bar on the same line, with the progress percentage dynamically updating. However, after switching to my custom logger, when displaying the progress bar, each update of the progress percentage prints out on a new line, as shown below:
[download]   0.0% of    3.41MiB at  583.84KiB/s ETA 00:05
[download]   0.1% of    3.41MiB at    1.08MiB/s ETA 00:03
[download]   0.2% of    3.41MiB at    1.38MiB/s ETA 00:02
[download]   0.4% of    3.41MiB at    2.96MiB/s ETA 00:01
[download]   0.9% of    3.41MiB at    5.08MiB/s ETA 00:00
[download]   1.8% of    3.41MiB at    8.84MiB/s ETA 00:00
[download]   3.6% of    3.41MiB at    7.91MiB/s ETA 00:00
[download]   7.3% of    3.41MiB at   10.20MiB/s ETA 00:00
[download]  14.7% of    3.41MiB at   11.18MiB/s ETA 00:00
[download]  29.3% of    3.41MiB at   11.69MiB/s ETA 00:00
[download]  58.7% of    3.41MiB at   13.60MiB/s ETA 00:00
[download] 100.0% of    3.41MiB at   13.39MiB/s ETA 00:00

How can I handle making the progress bar display in a single line like the original, or how can I change only the content of the error method without affecting info and warning? Thank you.

Currently, my Logger is like the following. Since I only intend to capture the content of error, I inherited from Logger and only modified the content of error:
errMsgs = []

class CaptureLogger(logging.Logger):
    def __init__(self):
        super().__init__("ydl", level=logging.DEBUG)
        ch = logging.StreamHandler()
        ch.setLevel(logging.DEBUG)
        super().addHandler(ch)
    def error(self, msg):
        super().error(msg)
        errMsgs.append(msg)

ydl_opts = {
    "logger": CaptureLogger(),
    "ignoreerrors": True
}

logging.Logger isn't respecting \r instead of \n at end of progress lines. Define your own info that behaves correctly


Add missing HL7 artefacts from the codegen tool

Purpose

$Subject

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update stats exit reports to match Jan 2023 YJIT

We're significantly out of date.
This needs testing on real data, to make sure both old and new stats render reasonably, and that all fields are included where available.

Closing stale PR