text:
Adding Future Dates in Reportings Total Sales, there in calender filter when we add future date, in console we can see 500 Internal Server Error.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.0.0
Issue Description
When we check the Reporting Section, in total sales when we view all, and there when we add  furture date, we can see that the shimmer effect is appearing. When we check the console, there we can see 500 Internal Server Error is appearing. When we click on the error we can see the exceptional error is appearing.
Preconditions

Admin should be logged in.
Sales should be done.
Invoice and Shipment should be done.

Steps to reproduce

Go to Admin -> Reportings -> Total Sales -> View all -> Check the Date Filter.
Click on From Date -> Add Future Date -> Shimmer Effects appears
Open Console
See error 500 Internal Server.
Click on the error we can see exception is appearing.

Expected Result
There should be no error in the console.
Actual Result
Currently we can see tha the errors are appearing. Please check the video for reference.
Video
https://github.com/bagisto/bagisto/assets/92721837/0a346384-6de3-42fd-ba16-ff5e810d93c7
Screenshots
Please check the error screenshot here
Additional context
No response

@suraj-webkul
Checked and Found that the issue in total sales calander filter future dates issue has been fixed.
Please check the video for reference.
Video
https://github.com/bagisto/bagisto/assets/92721837/794dff3c-8eaa-403a-9440-aa15322f5d93

Checked and Found that the issue has been fixed. Hence I am closing the issue.
PR Link - https://github.com/bagisto/bagisto/pull/8985


text:
Address State Fixed #5501

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/5501
Info

Maybe for other countries states can use space alphabets and numbers (rarely). I am not sure but I just reverted to the previous one.

@devansh-webkul
it is working fine

source: gharchive/pull-request

authors: Sanjaybhattwebkul devansh-webkul

repo: bagisto/bagisto

license: MIT

license_type: permissive

license_source: github-api


text:
Disabling/enabling text inputs programatically marks them as "aria-invalid"

vee-validate: 2.2.8
vue: 2.6.10

I have a form which has a computed property (formIsValid) informing a user whether every field in the form is valid.
The form contains a custom component. In the custom component are two inputs (foo and bar). When a user types something into foo, I would like to disable bar and vice versa.
The user has to enter something into either foo or bar for the form to be valid.
To this end, I have set up a dynamic v-validate rule to ensure that the input fields are only marked as required if they are not disabled.
The problem:
Initially, both fields have the following attributes: aria-required="true" and aria-invalid="false"
The first time a user types something into either foo or bar, the aria-required attribute of the other field is updated to false, but its aria-invalid attribute is set to true. This means that the formIsvalid computed property in the parent is still showing the form as invalid.
What I would have expected
I would have expected that the first time a user types something into either foo or bar, the other field's aria-required attribute is updated to false and that the aria-invalid attribute remains false. This would presumably set the formIsvalid computed property in the parent to true.
Please note: If the user deletes their initial input, then re-enters a value into the other field, things then work as expected.
CodePen demo: https://codesandbox.io/s/vue-template-f5qpy
Am I missing something obvious? How can I make the formIsValid computed property update to true, the minute a user enters anything into either input?

lol, sorry.

I actually ended up solving this by creating two copies of the same field, one is required and the other not and switching between them using v-if. I saw this recommended here.
I'd still be interested to know if this is the correct way to go about things though.

I pushed a fix in 63247ca to address that problem, it had a bigger underlying issue that was causing this one. Thanks for reporting this!

No worries. Thanks for the quick turn around!

source: gharchive/issue

authors: jameshibbard logaretm

repo: baianat/vee-validate

license: mit

license_source: bigquery


text:
中文的Wifi名称会显示乱码无法破解

中文的Wifi名称会显示乱码无法破解

已修复

已修复

repo: baihengaead/wifi-crack-tool


text:
Adding tokens not working in 'Create a Pool' when returning to a partially created pool

Describe the bug
When tapping the 'Add tokens' button, empty rows are being created. This was happening for a 'saved pool' that was started a while back but not completed.
To Reproduce
Steps to reproduce the behavior:

Go to 'Create a pool'
Start creating a pool.
Leave the Create a Pool interface
Go back to Create a Pool
Try adding new tokens

Loom:
https://www.loom.com/share/887e448e2fa54daaaca77049a59da97a
Browser console errors:
instrument.js:109 TypeError: Cannot read properties of null (reading 'insertBefore')
    at insert (runtime-dom.esm-bundler.js:10:16)
    at T (runtime-core.esm-bundler.js:4148:9)
    at _ (runtime-core.esm-bundler.js:4068:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4797:21)
    at L (runtime-core.esm-bundler.js:4680:17)
    at C (runtime-core.esm-bundler.js:4385:17)
    at y (runtime-core.esm-bundler.js:3984:17)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at C (runtime-core.esm-bundler.js:4385:17)
    at y (runtime-core.esm-bundler.js:3984:17)
    at k (runtime-core.esm-bundler.js:4305:13)
    at O (runtime-core.esm-bundler.js:4213:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at E.c [as fn] (runtime-core.esm-bundler.js:4606:17)
    at E.run (reactivity.esm-bundler.js:160:29)
    at N (runtime-core.esm-bundler.js:4467:26)
    at j (runtime-core.esm-bundler.js:4400:13)
    at y (runtime-core.esm-bundler.js:3991:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at C (runtime-core.esm-bundler.js:4385:17)
    at y (runtime-core.esm-bundler.js:3984:17)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at E.c [as fn] (runtime-core.esm-bundler.js:4606:17)
    at E.run (reactivity.esm-bundler.js:160:29)
    at Qa (runtime-core.esm-bundler.js:6990:36)
    at Oi (runtime-core.esm-bundler.js:7221:17)
    at async G (ChooseWeights.vue:236:13)
(anonymous) @ instrument.js:109
ni @ runtime-core.esm-bundler.js:7061
ti @ runtime-core.esm-bundler.js:7039
Qa @ runtime-core.esm-bundler.js:6993
Oi @ runtime-core.esm-bundler.js:7221
Promise.then (async)
vi @ runtime-core.esm-bundler.js:7120
wi @ runtime-core.esm-bundler.js:7142
_i @ runtime-core.esm-bundler.js:7145
y @ runtime-core.esm-bundler.js:7410
B @ reactivity.esm-bundler.js:358
D @ reactivity.esm-bundler.js:331
(anonymous) @ reactivity.esm-bundler.js:475
S @ usePoolCreation.ts:259
H @ ChooseWeights.vue:254
Qa @ runtime-core.esm-bundler.js:6990
ei @ runtime-core.esm-bundler.js:6999
n @ runtime-dom.esm-bundler.js:347
r @ helpers.js:73
instrument.js:109 TypeError: Cannot read properties of null (reading 'emitsOptions')
    at Et (runtime-core.esm-bundler.js:958:29)
    at N (runtime-core.esm-bundler.js:4446:13)
    at j (runtime-core.esm-bundler.js:4400:13)
    at y (runtime-core.esm-bundler.js:3991:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at C (runtime-core.esm-bundler.js:4385:17)
    at y (runtime-core.esm-bundler.js:3984:17)
    at k (runtime-core.esm-bundler.js:4305:13)
    at O (runtime-core.esm-bundler.js:4213:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at E.c [as fn] (runtime-core.esm-bundler.js:4606:17)
    at E.run (reactivity.esm-bundler.js:160:29)
    at N (runtime-core.esm-bundler.js:4467:26)
    at j (runtime-core.esm-bundler.js:4400:13)
    at y (runtime-core.esm-bundler.js:3991:21)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at C (runtime-core.esm-bundler.js:4385:17)
    at y (runtime-core.esm-bundler.js:3984:17)
    at U (runtime-core.esm-bundler.js:4761:17)
    at L (runtime-core.esm-bundler.js:4704:21)
    at O (runtime-core.esm-bundler.js:4220:13)
    at _ (runtime-core.esm-bundler.js:4071:13)
    at y (runtime-core.esm-bundler.js:3988:21)
    at E.c [as fn] (runtime-core.esm-bundler.js:4606:17)
    at E.run (reactivity.esm-bundler.js:160:29)
    at Qa (runtime-core.esm-bundler.js:6990:36)
    at Oi (runtime-core.esm-bundler.js:7221:17)
(anonymous) @ instrument.js:109
ni @ runtime-core.esm-bundler.js:7061
ti @ runtime-core.esm-bundler.js:7039
Qa @ runtime-core.esm-bundler.js:6993
Oi @ runtime-core.esm-bundler.js:7221
Promise.then (async)
vi @ runtime-core.esm-bundler.js:7120
wi @ runtime-core.esm-bundler.js:7142
_i @ runtime-core.esm-bundler.js:7145
y @ runtime-core.esm-bundler.js:7410
B @ reactivity.esm-bundler.js:358
D @ reactivity.esm-bundler.js:331
(anonymous) @ reactivity.esm-bundler.js:475
(anonymous) @ ChooseWeights.vue:293
Y @ ChooseWeights.vue:292
H @ ChooseWeights.vue:256
await in H (async)
Qa @ runtime-core.esm-bundler.js:6990
ei @ runtime-core.esm-bundler.js:6999
n @ runtime-dom.esm-bundler.js:347
r @ helpers.js:73

Hi! Just to add to this report, because I've been having this issue for a few days now and finally nailed down a consistent reproduction, I can confirm that this happens as well when returning to the first step after initially adding tokens.
https://user-images.githubusercontent.com/3876078/174514194-f99c5cc8-fb37-41fe-9e56-0b8e4a90e841.mov
1- Go to Pool Creation, add two tokens.
2- Move to the next step.
3- Return to the first step by pressing on Back on the steps breadcrumb
4- Add a new token, notice the empty row.

This bug couldn't recreate in the local dev environment (still remain in the live release). In the local dev environment, there is a vue warn which provides during adding tokens. This might be the issue (refer to the image).

@garethfuller

Cleaning up old issues, please reopen if applicable

authors: eduardopelitti mikemcdonald nayane95 pkattera


text:
Issues from Doc-Templater

Hey everyone, we're moving these issues to the main Sails repo for greater exposure to the community. Although we're not able to transfer the actual posts since they are from a different org, we've made screen-captures of them instead to follow-up with here in Sails. Hope these help out and feel free to add any further developments - Thanks!

For the first issue: we've decided for the foreseeable future, documenting standalone use of doc-templater, an internal tool we use for compiling our docs, isn't going to be a priority. You're welcome to look at the source code and use it however you want, as it is open source.
For the second issue: sounds like the README for this internal tool was out of date, and probably still is, but as mentioned above I don't think we'll be able to spend any time working on updating that documentation.

repo: balderdashy/sails


text:
Destroy with "lower than" parameter.

Hello,
I'm trying to use the destroy method with a lower than in the request, and I can't make it to work.
Although, the find method returns some content with the exact same parameters.
Cars.find({userId: params.userId, accessDate: { '<=': new Date() }}, function (err, found) {
    console.log(found); //Returns an array with multiple entries.
});

Cars.destroy({userId: params.userId, accessDate: { '<=': new Date() }}); //Does nothing, the entries are not destroyed.

This is the content in my database returned by the first request:
[ { userId: '563c1c37be1ed48e7f8c6ada',
    accessDate: '2015-11-07T21:36:13.169Z',
    id: '563e60bd19667c52bd831182' },
  { userId: '563c1c37be1ed48e7f8c6ada',
    accessDate: '2015-11-10T05:04:01.850Z',
    id: '56416cb140112987ce6ec049' },
  { userId: '563c1c37be1ed48e7f8c6ada',
    accessDate: '2015-11-12T03:59:36.519Z',
    id: '5644009851503b42e589ecf1' } ]

Am I wrong somewhere?
Thanks.

Which adapter are you using?  Are you on the latest version of waterline and your adapter?

I am using the sails-mongo adapter. My version of waterline is 0.10.26, the latest one.

I just found the reason why. If I add a callback function to the destroy method, it destroys the content. Otherwise, it doesn't.
This doesn't work:
Cars.destroy({userId: params.userId, accessDate: { '<=': new Date() }});

But this works:
Cars.destroy({userId: params.userId, accessDate: { '<=': new Date() }}, function () {});

You don't have to do anything with the callback but our queries are chainable. This allows you to do stuff like so:
var method = Cars.destroy()
.where({ userId: params.userId });

method.exec();

So if you don't care about the result just tack on an .exec() to run the query.

authors: alexismangin devinivy particlebanana

repo: balderdashy/waterline


text:
Suggestion: Comments inside of the event browser

I think it would be useful to add custom labels/comments to the event browser list using the API to better notate what is going on. Especially when you have many draw calls.

Yes this is available as standard in all graphics APIs.
In OpenGL the extension you're after is KHR_debug which provides functions to do a single marker line as you've put above:
glDebugMessageInsert(GL_DEBUG_SOURCE_APPLICATION, GL_DEBUG_TYPE_MARKER, 0,
                     GL_DEBUG_SEVERITY_NOTIFICATION, -1, "World geometry stencil pass");

Or else you could define nested marker regions - similar to the auto-generated ones "Colour Pass #N":
glPushDebugGroup(GL_DEBUG_SOURCE_APPLICATION, 0, -1, "Stencil pass");

glDrawArrays(...);
glDrawArrays(...);
glDrawArrays(...);

glPopDebugGroup();

For more information see the documentation page about annotating your frame.

authors: baldurk sbarisic

repo: baldurk/renderdoc


text:
Document how dashes interact with buried asset names

This took me FOREVER to find so wanted to PR this even if you dont want to accept this, just so this note is searchable. ;)
If you keep seeing "Hello, world!" printed in your logs instead of your app running, you may have edited  the Dockerfile maybe changing your rust app name, and maybe it has a dash in it. Cargo under the hood rewrites some names but not all it seems...

Thanks fro this! I included this note in another PR via this commit.

authors: jacobrosenthal zrzka


text:
Few base images updates

This PR contains the following changes:

Set Alpine Linux 3.14 as the latest tag.
Update QEMU to v6.0.0-balena1.
Add Golang v1.17.

@balena-ci I self-certify!

repo: balena-io/contracts


text:
Container pushing related tests timeout on RPi0

https://jenkins.dev.resin.io/job/leviathan-raspberry-pi/674/console
and more instances of it.

https://github.com/balena-os/leviathan/issues/414

Update: The container tests on the rpi0 were timing out consistently. After a recent major investigation into container healthcheck tests timing out, we have found a potential reason behind these timeouts.
Some PRs slipped through automated meta-balena testing when Jenkins was building master instead of branches for almost a week. Those same PRs appeared to pass some manual testing as well since the symptoms aren't obvious. We identified this when we saw an increase in the number of balena engine systemd watchdog failures on Rpi0.
We narrowed it down to this PR: https://github.com/balena-os/meta-balena/pull/2175 and the work to restore this is in progress https://github.com/balena-os/meta-balena/pull/2245 More updates on the thread below.
This is a step in the right direction to make sure tests are more resilient and don't flake out for RPi0 due to how resource constrained that specific device is. The issue can be closed if we no longer see consistent test failures from RPi0 related to container tests.
Thread: https://www.flowdock.com/app/rulemotion/p-testbot/threads/0Sqx0v6bu1HRKUvu3XbYQMHveA4
cc: @rcooke-warwick

repo: balena-os/leviathan


text:
Add support for python3.4 and python3.5

This patch is to support python3.4 and python3.5 in pqueue.
or following error will be thrown:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: invalid
start byte
to reproduce it, simply run:
python3.4 runtest.py

@balena Could you please help to review this patch?

repo: balena/python-pqueue


text:
String template expression not Working for Union Types

Description:
Consider the following code:
public type Foo int|float|decimal|string|boolean;

public function main() {
    Foo foo = 4;
    string s = string`${foo}`;
}

This results in a compilation error: incompatible types: expected '(int|float|decimal|string|boolean)', found '(int|float|decimal|string|boolean)'
But using ${foo.toString()} works.

Related spec issue: https://github.com/ballerina-platform/ballerina-spec/issues/795

Fixed in #29733, merged to master in #29934.

authors: MaryamZi ThisaruGuruge

repo: ballerina-platform/ballerina-lang


text:
Compiler crashes for io:println(transactional); with NPE when there's no transaction-stmt

Description:
Following code crashes when the transaction-stmt is commented out.
public function main() returns error? {
    io:println(transactional);

    // transaction {
    //     io:println("Stage1 completed");
    //     io:println("Stage2 completed");
    //     io:println(transactional);
    //     check commit;
    // }
}

stacktrace  (click to expand)
java.lang.NullPointerException
        at org.wso2.ballerinalang.compiler.desugar.TransactionDesugar.getInternalTransactionModuleInvokableSymbol(TransactionDesugar.java:669)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:7303)
        at org.wso2.ballerinalang.compiler.tree.expressions.BLangTransactionalExpr.accept(BLangTransactionalExpr.java:38)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExpr(Desugar.java:8039)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:6958)
        at org.wso2.ballerinalang.compiler.tree.expressions.BLangTypeConversionExpr.accept(BLangTypeConversionExpr.java:72)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExpr(Desugar.java:8039)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:6958)
        at org.wso2.ballerinalang.compiler.tree.expressions.BLangTypeConversionExpr.accept(BLangTypeConversionExpr.java:72)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExpr(Desugar.java:8039)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExprs(Desugar.java:8079)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:5712)
        at org.wso2.ballerinalang.compiler.tree.expressions.BLangListConstructorExpr$BLangArrayLiteral.accept(BLangListConstructorExpr.java:89)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExpr(Desugar.java:8039)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExprs(Desugar.java:8079)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteInvocation(Desugar.java:6285)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:6225)
        at org.wso2.ballerinalang.compiler.tree.expressions.BLangInvocation.accept(BLangInvocation.java:117)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteExpr(Desugar.java:8039)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:3324)
        at org.wso2.ballerinalang.compiler.tree.statements.BLangExpressionStmt.accept(BLangExpressionStmt.java:47)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewrite(Desugar.java:8014)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewrite(Desugar.java:8055)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewriteStmt(Desugar.java:8065)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:1266)
        at org.wso2.ballerinalang.compiler.tree.BLangBlockFunctionBody.accept(BLangBlockFunctionBody.java:57)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewrite(Desugar.java:8014)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:1311)
        at org.wso2.ballerinalang.compiler.tree.BLangFunction.accept(BLangFunction.java:73)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewrite(Desugar.java:8014)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewrite(Desugar.java:8072)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.visit(Desugar.java:804)
        at org.wso2.ballerinalang.compiler.tree.BLangPackage.accept(BLangPackage.java:165)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.rewrite(Desugar.java:8014)
        at org.wso2.ballerinalang.compiler.desugar.Desugar.perform(Desugar.java:454)
        at io.ballerina.projects.internal.CompilerPhaseRunner.desugar(CompilerPhaseRunner.java:232)
        at io.ballerina.projects.internal.CompilerPhaseRunner.performBirGenPhases(CompilerPhaseRunner.java:150)
        at io.ballerina.projects.ModuleContext.generateCodeInternal(ModuleContext.java:397)
        at io.ballerina.projects.ModuleCompilationState$4.generatePlatformSpecificCode(ModuleCompilationState.java:132)
        at io.ballerina.projects.ModuleContext.generatePlatformSpecificCode(ModuleContext.java:333)
        at io.ballerina.projects.JBallerinaBackend.performCodeGen(JBallerinaBackend.java:157)
        at io.ballerina.projects.JBallerinaBackend.<init>(JBallerinaBackend.java:141)
        at io.ballerina.projects.JBallerinaBackend.lambda$from$0(JBallerinaBackend.java:115)
        at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1133)
        at io.ballerina.projects.PackageCompilation.getCompilerBackend(PackageCompilation.java:150)
        at io.ballerina.projects.JBallerinaBackend.from(JBallerinaBackend.java:114)
        at io.ballerina.cli.task.CompileTask.execute(CompileTask.java:65)
        at io.ballerina.cli.TaskExecutor.executeTasks(TaskExecutor.java:40)
        at io.ballerina.cli.cmd.BuildCommand.execute(BuildCommand.java:302)
        at java.base/java.util.Optional.ifPresent(Optional.java:183)
        at io.ballerina.cli.launcher.Main.main(Main.java:58)

fixed with https://github.com/ballerina-platform/ballerina-lang/pull/35627

authors: gimantha lochana-chathura


text:
[New Feature]: Introduce on Type formating language feature to LS

Description
Format code when typing. The format request textDocument/onTypeFormatting  is trigger by special characters like {, }, ;
Refer https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_onTypeFormatting

+1

Sample use case,
function getJsonProperty(json|error data) returns json|error? => <cursor>

or
function getJsonProperty(json|error data) returns json|error? => <cursor> data is error ? data.message() : data.'worker;

When we press enter at the cursor position above,

current behavior,

function getJsonProperty(json|error data) returns json|error? =>
data is error ? data.message() : data.'worker;

expected behavior,

function getJsonProperty(json|error data) returns json|error? =>
    data is error ? data.message() : data.'worker;

In coding styles, we encourage using expression-bodied functions over block-function-body whenever possible. Therefore, I expect this to be a quite frequent scenario.

We are closing this issue due to inactivity. If you need further assistance or have additional input, feel free to reopen it. Thank you for helping us maintain a relevant and focused issue list!

authors: IMS94 anupama-pathirage lochana-chathura malinthar


text:
Latest Ballerina packages do not get pulled when there is an older version of package

Description:
The Ballerina packages which are pulled from Ballerina Central get invalidated when a new Ballerina version is installed. But the latest versions of the packages do not get pulled automatically when the code which uses the packages, is built with a latest Ballerina version.
Steps to reproduce:
There should be an older version of package which is compatible with Ballerina older version. Then install the latest version of Ballerina. When trying to build a code sample which uses the pulled package, the following error will occur.
Compiling source
package:0.0.0
ballerina: format error: ballerina: unsupported program file version 18

Please refer an real use case which is given under "Related issues" secion.
Related Issues
https://stackoverflow.com/questions/51359780/error-in-fetching-updates-for-ballerina-central-packages

This issue is fixed with #9887, hence closing this issue.


text:
Fix path issues when building an executable for a single bal file

Purpose

This PR will fix the path issues when building a single bal file. It will always build the executable (balx) in the current directory of the user

Allow building a bal file by giving the absolute path : ballerina build a/b/c/foo.bal
Allow building a bal file by giving the path from the current directory: ballerina build c/foo.bal

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

@Kishanthan added test cases with c7daf15

@Kishanthan added a test case to capture the failing scenario with bcc605d

Will merge once build passes.


text:
Fix closures not working inside query Actions and Expressions

Purpose
$subject
Fixes #41450
Fixes #39760
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@LakshanWeerasinghe, please resolve the conflicts.

authors: KavinduZoysa LakshanWeerasinghe


text:
Update centralized workflows to support latest Ballerina gradle plugin imrpovements

Description:

$subject

Related to: #166

With this change we need to update the plugin version in all of the connector repositories. Following is a list of repositories we need to bump the gradle plugin version:

[ ] Amazon DynamoDB
[ ] Amazon DynamoDB Streams
[ ] Amazon Marketplace Metering
[ ] Amazon Marketplace Entitlement
[ ] Amazon Redshift
[ ] Amazon SNS
[ ] Asana
[ ] Azure Service Bus
[ ] Candid
[ ] Confluent Avro Serdes
[ ] Confluent Schema Registry
[ ] Dayforce
[ ] Discord
[ ] DocuSign eSignature
[ ] DocuSign Click
[ ] DocuSign Admin
[ ] Github
[ ] Gmail
[ ] Google Calendar
[ ] GuideWire InsuranceNow
[ ] MongoDB
[ ] Redis
[ ] Salesforce
[ ] Slack
[ ] Snowflake
[ ] Twilio
[ ] Twitter
[ ] Zendesk

Along with the gradle-plugin version update we need to enable the example builds of the connector repositories.

The initial development for this task is complete; however, it must be put on hold until the completion of the SL Update 11 release. This is due to anticipated challenges, including the migration from Java 17 to Java 21.
Initial developments has been completed with following PRs:

https://github.com/ballerina-platform/ballerina-library/pull/7449
https://github.com/ballerina-platform/module-ballerinax-azure-service-bus/pull/243
https://github.com/ballerina-platform/module-ballerinax-redis/pull/244
https://github.com/ballerina-platform/module-ballerinax-stripe/pull/16

repo: ballerina-platform/ballerina-library


text:
🐛 fix(tabs):  position indicator line stretches with content

Current Behavior
Currently the decorative line under or next to the tab navigation stretches with the content height / width.

Expected Behavior
Per design it should only cover the length of the navigation items
Steps to Reproduce
Default tabs usage
Version
13.2.1
Browsers
No response
Device
No response
Code Reproduction URL
No response
Additional Information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

will be done by #879

repo: baloise/design-system


text:
app启动第一次进入相册，点击返回相册列表有几秒钟卡顿。是否可以直接进入相册选择列表。

提bug前必看
请先回答下列三个问题，否则不允处理，谢谢配合。
1、我最新的Demo是否有这个bug？【如果Demo没问题，请升级新版】
答：是
2、你用的是什么版本？升级到最新版后是否正常？
答：3.09
3、是否有改动过我库内部的代码？【如有，请告诉我你改了什么】
答：否
bug内容描述
警告是在非主线程修改了ui
Main Thread Checker: UI API called on a background thread: -[UIViewController navigationController]
我如何复现这个bug？
截图
其它说明
xcode11 ios13

升级到3.2.5试试

repo: banchichen/TZImagePickerController


text:
pair sample query

this query will expose all unique pools where the order of token0 and token1 is determined based on token address ascending.
important to note, the output of this query will not indicate the base and quote tokens correctly as they do not represent actual strategies with their base and quote asset indication.
{
  pairs (first:3)
  { id
  }
}

@pingustar do we still need this?

repo: bancorprotocol/carbon-subgraph


text:
Carbon strategies are duplicated from events

Bug Description
When a Strategy updated event occurs, the strategy is duplicated in the system due to having a different CID from the original strategy. This occurs due to using different inputs to generate the CID.
On startup: Bot called add_pool_info when processing pool data for Carbon Strategies. This resulted in creating a CID using exchange name, strat id, and fee:
f"{pool_info['exchange_name']} {pool_info['strategy_id']} {pool_info['fee']}

However, when updating from a Strategy Updated event, the bot called the get_pool_cid function to get a CID. This function used only exchange name & strat id to generate the CID.
args["exchange_name"] + " "+ str(args["strategy_id"]

This resulted in creating a new pool for the updated strategy, while retaining the original pool with now-stale data.
To fix this, the exact same inputs must be used to generate the CID - ideally only a single function should exist to generate the CID.
Severity (High/Medium/Low)
High
Steps to Reproduce
Run bot with Carbon enabled & read_only=False. Wait for Carbon trade event. See Strategy duplicated with different CID.
Expected Behavior
Only a single instance of each Carbon strategy should exist in pool data.
Actual Behavior
Up to two instances of each Carbon strategy can exist in pool data.
Impact Analysis (to be filled by contributors)

Automated Tests: Are there existing tests covering this? Do we need new tests?
Will discuss.

Risks: Potential areas affected by this bug and its probable fix
Low risk. Need to ensure only a single CID-generation function is called.

Performance: Is this bug affecting performance?
No

Monitoring: Does this affect any current monitoring? Any new alerts needed?
No

Logging: Any changes required in logging?
No

Documentation: Updates needed in documentation?
No

I'm seeing this in at least 3 places in the code:

Module pools / Class PoolManager / Function pool_descr_from_info
Module pools / Class PoolManager / Function add_pool_info
Module utils / Global Function get_cid_base

In addition to that, it appears as if somebody has implemented one way of constructing CIDs specifically for carbon v1 forks, and another way of constructing CIDs for all other cases.
This seems to be with some sort of specific intention, so just changing it without finding out the exact reason behind this is pretty risky and not necessarily a small straightforward change.

I'm seeing this in at least 3 places in the code:

Module pools / Class PoolManager / Function pool_descr_from_info
Module pools / Class PoolManager / Function add_pool_info
Module utils / Global Function get_cid_base

In addition to that, it appears as if somebody has implemented one way of constructing CIDs specifically for carbon v1 forks, and another way of constructing CIDs for all other cases.
This seems to be with some sort of specific intention, so just changing it without finding out the exact reason behind this is pretty risky and not necessarily a small straightforward change.

The issue was that Carbon pool CIDs were constructed one way on startup, and a different way on Strategy Update. It's OK That it's constructed differently from other pool types, it just must be consistent.

repo: bancorprotocol/fastlane-bot


text:
[BUG] Key error with custom variables when event is set at ON_EPOCH_END

Describe the bug
Impossible to complete the event self.fire(Event.ON_EPOCH_END) in Trainer object. The key is not found in self._custom_variable. "Normal" behaviour since this line is called before the user-defined _on_epoch_end() where a value is attributed to the dictionary key. Same would happen for events sets ON_EPOCH_BEGIN in main.py.
To Reproduce
Steps to reproduce the behavior:

Have defined a custom variable in main.py :

.with_event_handler(PlotCustomVariables(visdom_logger, "D(G(X) | X", PlotType.LINE_PLOT,
                                                    params={"opts": {"title": "Loss D(G(X) | X"}},
                                                    every=1), Event.ON_EPOCH_END) \

Execute whole validation process.
Have this variable computed in method _on_epoch_end.
Key Error : "D(G(X) | X" not found.

Expected behavior
User defined _on_epoch_end should be called to assign the variable in custom_variables dictionary before calling self.fire(Event.ON_EPOCH_END) of Trainer object.
** Solution **
Call the following instructions in this order :
    def _on_epoch_begin(self):
        self._reset_model_trainers()
        self.on_epoch_begin()
        self.fire(Event.ON_EPOCH_BEGIN)

    def _on_epoch_end(self):
        self.scheduler_step()
        self.on_epoch_end()
        self.fire(Event.ON_EPOCH_END)

This way, a value set to the dictionary key in custom_variable can be called in user_defined _on_epoch_end() method, and then the event is fired.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Linux Ubuntu 18.04.2 LTS
Python 3.7.4
CUDA 10.1 / cuDNN 7.3.1
NVIDIA GeForce RTX 2080 8 GB

See PR#56

repo: banctilrobitaille/kerosene


text:
🛑 MXN Blast On-ramps is down

In 14fc501, MXN Blast On-ramps ($QUOTE_ENDPOINT) was down:

HTTP code: 503
Response time: 2386 ms

Resolved: MXN Blast On-ramps is back up in 62d774c after 22 minutes.

repo: bandohq/upptime-monitor


text:
New fillup should store current datetime

from method aCar.AddFillUp(odometer, liters).
It creates a new Fillup object, please make sure that object has propperty Date and store current date/time (DateTime.Now)

issue close by siwat

license: unlicense


text:
Feature/ga

📝 PR Summary

온보딩 과정 UI 버그 fix
GA 연동

환경변수 추가되었습니다. 슬랙 확인 부탁드립니다.

전역 API 에러처리 시스템 추가

사용법은 화해 기술블로그 래퍼런스 참고 부탁드립니다.
래퍼런스를 따르긴 했지만 완전히 동일하게 구현하지는 않았습니다. 훅 사용방법은 동일합니다.
구경 하시라고 영상 첨부합니다.

https://user-images.githubusercontent.com/83692797/194716362-b444bafd-5913-41d0-bebc-ccea5f3ed58d.mov
🌲 Working Branch

feature/ga
🌲 TODOs

Related Issues

resolves: https://www.notion.so/bankidz/1-3-d81011bc32c94f139c5125597aab95a7?p=53e396dd8afc4808b5c0a1a563fa8a59&pm=s

깃헙액션 시크릿도 수정할게유

repo: bankidz/bankidz-client


text:
zap 3crv to yearn vault

Solid work, I'll iterate a bit more on this to expand on tests and come up with how it better integrates in the UI.

Appreciate it. My knowledge of brownie is a bit noobish right now

authors: banteg listonjesse

repo: banteg/ape-tax


text:
小程序抓包成功但问题是小程序不支持全部智能设备

app上添加了四个空调但是小程序中没有这四个设备  询问智家客服说是小程序开发不完整 能否请大佬做一个app的token 目前小程序token登录后显示没有实体

2024-09-22 19:50:08.321 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration haier which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-22 19:50:08.322 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-22 19:50:08.323 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_miot which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-22 20:20:40.803 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Haier - 15666317026 for haier
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/init.py", line 34, in async_setup_entry
devices = await client.get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/core/client.py", line 121, in get_devices
self._assert_response_successful(content)
File "/config/custom_components/haier/core/client.py", line 400, in _assert_response_successful
raise HaierClientException('接口返回异常: ' + resp['retInfo'])
custom_components.haier.core.client.HaierClientException: 接口返回异常: Token不是由此应用创建，未通过token验证
2024-09-22 20:21:36.919 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Haier: 15666317026 for haier
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/init.py", line 34, in async_setup_entry
devices = await client.get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/core/client.py", line 121, in get_devices
self._assert_response_successful(content)
File "/config/custom_components/haier/core/client.py", line 400, in _assert_response_successful
raise HaierClientException('接口返回异常: ' + resp['retInfo'])
custom_components.haier.core.client.HaierClientException: 接口返回异常: Token不是由此应用创建，未通过token验证
2024-09-22 20:21:41.428 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Haier: 15666317026 for haier
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/init.py", line 34, in async_setup_entry
devices = await client.get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/core/client.py", line 121, in get_devices
self._assert_response_successful(content)
File "/config/custom_components/haier/core/client.py", line 400, in _assert_response_successful
raise HaierClientException('接口返回异常: ' + resp['retInfo'])
custom_components.haier.core.client.HaierClientException: 接口返回异常: Token不是由此应用创建，未通过token验证
2024-09-22 20:32:44.523 WARNING (MainThread) [custom_components.haier.config_flow] 接口返回异常: 授权异常或失败
2024-09-22 20:33:00.374 WARNING (MainThread) [custom_components.haier.config_flow] 接口返回异常: 授权异常或失败
2024-09-22 20:40:49.799 WARNING (MainThread) [custom_components.haier.config_flow] 接口返回异常: 授权异常或失败
2024-09-22 20:41:16.299 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Haier - 15666317026 for haier
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/init.py", line 34, in async_setup_entry
devices = await client.get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/core/client.py", line 121, in get_devices
self._assert_response_successful(content)
File "/config/custom_components/haier/core/client.py", line 400, in _assert_response_successful
raise HaierClientException('接口返回异常: ' + resp['retInfo'])
custom_components.haier.core.client.HaierClientException: 接口返回异常: Token不是由此应用创建，未通过token验证
2024-09-22 20:41:24.814 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Haier - 15666317026 for haier
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/init.py", line 34, in async_setup_entry
devices = await client.get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/core/client.py", line 121, in get_devices
self._assert_response_successful(content)
File "/config/custom_components/haier/core/client.py", line 400, in _assert_response_successful
raise HaierClientException('接口返回异常: ' + resp['retInfo'])
custom_components.haier.core.client.HaierClientException: 接口返回异常: Token不是由此应用创建，未通过token验证
2024-09-22 20:56:04.480 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Haier - 15666317026 for haier
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/init.py", line 34, in async_setup_entry
devices = await client.get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/haier/core/client.py", line 121, in get_devices
self._assert_response_successful(content)
File "/config/custom_components/haier/core/client.py", line 400, in _assert_response_successful
raise HaierClientException('接口返回异常: ' + resp['retInfo'])
custom_components.haier.core.client.HaierClientException: 接口返回异常: Token不是由此应用创建，未通过token验证

卡萨帝中央空调LVIP-RFTS71CXS-D(YH)

已解决


text:
webhook: Kubernetes secret not being mutated on creation/update

Describe the bug:
A Kubernetes secret is created, when viewing secret or mounting it as a file it just has vault path as the string and not the referenced secret in Vault.  When creating the secret, the vault-secrets-webhook pod prints this error
time="2021-09-21T15:26:14Z" level=error msg="Admission review request failed" app=vault-secrets-webhook dry-run=false error="failed to create vault client: timeout [10s] during waiting for Vault token" kind=v1/Secret name=vault-test-secret ns=kaniko op=update path=/secrets request-id=1e14b8aa-3897-4999-855e-e19de76cfbaa webhook-id=vault-secrets-secret webhook-kind=mutating wh-version=v1beta1
The same secret path and vault annotations work fine for deployments in same namespace and get the secret as an environment variable.
Expected behaviour:

Secret gets created
Contents of secret data are replaced with secret contents from vault

Steps to reproduce the bug:

Create secret
Use kubectl to inspect contents of secret

Additional context:
Add any other context about the problem here.
Environment details:

Kubernetes version: 1.19
Cloud-provider/provisioner: EKS
bank-vaults version: 1.14.1
Install method: Helm

/kind bug
kind: Secret
metadata:
  name: vault-test-secret
  namespace: test
  annotations:
    vault.security.banzaicloud.io/vault-addr: "https://vault.vault:8200"
    vault.security.banzaicloud.io/vault-skip-verify: "true"
    vault.security.banzaicloud.io/vault-path: "kubernetes"
    vault.security.banzaicloud.io/vault-role: "default"
data:
  TEST_KEY: dmF1bHQ6c2VjcmV0L2RhdGEvYWNjb3VudHMvYXdzI0FXU19TRUNSRVRfQUNDRVNTX0tFWQ==
type: Opaque

The same issue for me, only after changing helm chart version for vault-secrets-webhook from 1.13.2 to 1.14.1

I am experiencing the same thing, no secret mutation with webhook 1.14.1.  Referencing same secret with envFrom from a pod with webhook annotation works correctly

Hi, I'm trying to reproduce the use-cases and errors, but I think we are having at least two different kind of issues here on this thread.
First of all, when mutating Secrets, by default the webhook's Kubernetes ServiceAccount is used to authenticate against Vault, this SA has to be configured to be able to use the Kubernetes Auth method in Vault and has to have a proper role assigned to it, which allows to read the given paths referenced in the Secret.
In the example of @wmene, where the vault.security.banzaicloud.io/vault-serviceaccount: default annotation is on the Secret, there has to be a SA secret named default in the same namespace as vsecret which has access to Vault on the given paths.
And of course, of something has been working in 1.13.x and not working in 1.14.x that is an issue. Could you please help me with more details, regarding how the Vault authentication is configured and in which namespace the webhook is running, under which ServiceAccount.?

As I understand the original issue from @tabossert, I did the following.

Installed the operator and Vault with cr.yaml to the default namespace.
Installed the webhook into the vswh namespace.
Created the following Secret:

apiVersion: v1
kind: Secret
metadata:
  name: vault-test-secret
  namespace: test
  annotations:
    vault.security.banzaicloud.io/vault-addr: "https://vault.default:8200"
    vault.security.banzaicloud.io/vault-skip-verify: "true"
    vault.security.banzaicloud.io/vault-path: "kubernetes"
    vault.security.banzaicloud.io/vault-role: "default"
data:
  TEST_KEY: dmF1bHQ6c2VjcmV0L2RhdGEvYWNjb3VudHMvYXdzI0FXU19TRUNSRVRfQUNDRVNTX0tFWQ==
type: Opaque

The secret got mutated and TEST_KEY=s3cr3t, which is the expected result, did I get the scenario wrong?

@bonifaido Thanks for looking into this, I installed the webhook into the vault-infra namespace along with operator, I have bound service account names set to "*" and bound service account namespaces to include test namespace.  Would any of those cause this not to function?
Thanks

Trevor

Ok I set bound service account namespaces to "*" also and it worked, so I think I must have been confused on how that section works and will read up on it more, sorry for the confusion.
Thanks

Trevor

Hi, I'm trying to reproduce the use-cases and errors, but I think we are having at least two different kind of issues here on this thread.
First of all, when mutating Secrets, by default the webhook's Kubernetes ServiceAccount is used to authenticate against Vault, this SA has to be configured to be able to use the Kubernetes Auth method in Vault and has to have a proper role assigned to it, which allows to read the given paths referenced in the Secret.

The webhook is running in the vault-infra namespace.  It is using the vault-secrets-webhook Service Account.  The Kubernetes auth method in Vault assigns the default role to this ServiceAccount
$ vault read auth/my-kube-path/role/default
Key                                 Value
---                                 -----
bound_service_account_names         [default vault-secrets-webook ]
bound_service_account_namespaces    [*]
...
token_policies                      [read_kv]
...

The read_kv policy allows read from the vault path

In the example of @wmene, where the vault.security.banzaicloud.io/vault-serviceaccount: default annotation is on the Secret, there has to be a SA secret named default in the same namespace as vsecret which has access to Vault on the given paths.

vsecret is in our default namespace.  Yes, there is a SA secret with the annotation kubernetes.io/service-account.name: default in that same namespace.
For what it's worth, in the vault-infra namespace, there are SA secrets for default and vault-secrets-webook.
To reiterate, referencing the secret from a Pod works correctly, so configuration between Kubernetes Service Accounts and Vault roles works in that context.

And of course, of something has been working in 1.13.x and not working in 1.14.x that is an issue. Could you please help me with more details, regarding how the Vault authentication is configured and in which namespace the webhook is running, under which ServiceAccount.?

Actually, mutating stand-alone Secrets has never worked for us.  Sorry if that wasn't clear.

If I remove the annotation vault.security.banzaicloud.io/vault-serviceaccount: default from vsecret, the error is different in the webhook logs: service account name not authorized
time="2021-09-24T19:51:14Z" level=error msg="failed to request new Vault token" app=vault-secrets-webhook err="Error making API request.\n\nURL: PUT https://my-external.vault/v1/auth/my-vault-path/login\nCode: 500. Errors:\n\n* service account name not authorized"
time="2021-09-24T19:51:15Z" level=error msg="Admission review request failed" app=vault-secrets-webhook dry-run=false error="failed to create vault client: timeout [45s] during waiting for Vault token" kind=v1/Secret name=vsecret ns=default op=create path=/secrets request-id=b281744f-2686-428b-b173-b6e0241557f0 webhook-id=vault-secrets-secret webhook-kind=mutating wh-version=v1beta1

authors: adamdrozdz bonifaido tabossert wmene

repo: banzaicloud/bank-vaults


text:
Fix helm chart template names

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
fixes #383

License
Apache 2.0

What's in this PR?
Removes "-operator" in various spots in the Helm chart.
Why?
When this Helm chart is installed, the StatefulSet, Service, and RBAC resources
have their name as 'istio-operator-operator'. This fixes that so it's just 'istio-operator'.
Additional context
N/A
Checklist

[x] Implementation tested

 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.

 All committers have signed the CLA.

@Laci21 Apologies for the delay! I was waiting for my company to approve my request to sign the CLA.

authors: CLAassistant claassistantio rdeusser

repo: banzaicloud/istio-operator


text:
字段自动填充使用strictInsertFill函数抛出type mismatch的问题

当前使用版本(必填,否则不予处理)
3.3.0
该问题是如何引起的？(确定最新版也有问题再提!!!)
字段自动填充功能，实现MetaObjectHandler接口，
使用strictInsertFill(MetaObject metaObject, String fieldName, Class fieldType, Supplier fieldVal)函数导致的
重现步骤(如果有就写完整)
MetaObjectHandler{
default  MetaObjectHandler strictInsertFill(MetaObject metaObject, String fieldName, Class fieldType, Supplier fieldVal) {
return this.strictInsertFill(this.findTableInfo(metaObject), metaObject, Collections.singletonList(StrictFill.of(fieldName, fieldType, fieldVal)));
}
}
strictInsertFill函数内部调用了StrictFill.of(fieldName, fieldType, fieldVal)
StrictFill{
public static StrictFill of(String fieldName, Class fieldType, Object fieldVal) {
        return new StrictFill(fieldName, fieldType, () -> {
            return fieldVal;
        });
    }
  // !!!!!!!!!Supplier fieldVal!!!!!!!!!!!!这个方法进入不了，导致调用了上面那个of函数
<======现在这个版本的
    public static StrictFill of(String fieldName, Class fieldType, Supplier fieldVal) {
return new StrictFill(fieldName, fieldType, fieldVal);
}
=======>应该修复为
public static  StrictFill of(String fieldName, Class<?> fieldType, Supplier fieldVal) {
return new StrictFill(fieldName, fieldType, fieldVal);
}
}
报错信息
type mismatch

你怎么用的?

用最新版

最新版3.3.2的一样的问题
------------------ 原始邮件 ------------------
发件人: "miemieYaho"<notifications@github.com>;
发送时间: 2020年6月11日(星期四) 中午12:01
收件人: "baomidou/mybatis-plus"<mybatis-plus@noreply.github.com>;
抄送: "。"<976951401@qq.com>; "Author"<author@noreply.github.com>;
主题: Re: [baomidou/mybatis-plus] 字段自动填充使用strictInsertFill函数抛出type mismatch的问题 (#2595)
用最新版
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

你可以找到这2个函数
com.baomidou.mybatisplus.core.handlers.MetaObjectHandler#strictInsertFill(org.apache.ibatis.reflection.MetaObject, java.lang.String, java.lang.Class<T>, java.lang.Object)
com.baomidou.mybatisplus.core.handlers.MetaObjectHandler#strictInsertFill(org.apache.ibatis.reflection.MetaObject, java.lang.String, java.lang.Class<T>, java.util.function.Supplier<T>)
它2都调用了com.baomidou.mybatisplus.core.handlers.StrictFill#of(java.lang.String, java.lang.Class<?>, java.lang.Object)这个方法
而不是com.baomidou.mybatisplus.core.handlers.StrictFill#of(java.lang.String, java.lang.Class<?>, java.util.function.Supplier<java.lang.Object>)
但关键是java.util.function.Supplier<java.lang.Object> ！！！<Object>的泛型，就算我是StrictFill.of("name", String.class, ()-> "小明"),但调用的还是StrictFill#of(java.lang.String, java.lang.Class<?>, java.lang.Object)
------------------ 原始邮件 ------------------
发件人: "miemieYaho"<notifications@github.com>;
发送时间: 2020年6月11日(星期四) 中午12:01
收件人: "baomidou/mybatis-plus"<mybatis-plus@noreply.github.com>;
抄送: "。"<976951401@qq.com>; "Author"<author@noreply.github.com>;
主题: Re: [baomidou/mybatis-plus] 字段自动填充使用strictInsertFill函数抛出type mismatch的问题 (#2595)
用最新版
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

所有com.baomidou.mybatisplus.core.handlers.StrictFill#of(java.lang.String, java.lang.Class<?>, java.util.function.Supplier<java.lang.Object>)应该修改为<T> StrictFill of(String fieldName, Class<?> fieldType, Supplier<T> fieldVal) {才能够被正确调用
------------------ 原始邮件 ------------------
发件人: "miemieYaho"<notifications@github.com>;
发送时间: 2020年6月11日(星期四) 中午12:01
收件人: "baomidou/mybatis-plus"<mybatis-plus@noreply.github.com>;
抄送: "。"<976951401@qq.com>; "Author"<author@noreply.github.com>;
主题: Re: [baomidou/mybatis-plus] 字段自动填充使用strictInsertFill函数抛出type mismatch的问题 (#2595)
用最新版
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

那用 3.3.3.3-SNAPSHOT 仓库地址 https://oss.sonatype.org/content/repositories/snapshots/
入参里 Supplier 和 Class 进行了位置互调

ok

authors: JbfGod miemieYaho

repo: baomidou/mybatis-plus


text:
updateById Support Dynamic Field Strategy

updateById Support Dynamic Field Strategy

These methods have been supported

SQL SCRIPT
`

`

sql script
<script> <bind name="always" value="st == null or st == @com.baomidou.mybatisplus.annotation.FieldStrategy@IGNORED  or st == @com.baomidou.mybatisplus.annotation.FieldStrategy@ALWAYS"/> <bind name="notNull" value="st == @com.baomidou.mybatisplus.annotation.FieldStrategy@NOT_NULL"/> <bind name="notEmpty" value="st == @com.baomidou.mybatisplus.annotation.FieldStrategy@NOT_EMPTY"/> UPDATE sample_user <set> <if test="always or (notNull and et['username'] != null) or (notEmpty and et['username'] != null and et['username'] != '')">username=#{et.username},</if> <if test="always or (notNull and et['password'] != null) or (notEmpty and et['password'] != null and et['password'] != '')">password=#{et.password},</if> </set> WHERE id=#{et.id}  </script>

怎么说？考虑吗？


text:
Laravel-cors not working in laravel 5.4 with Angular2 . withcredentials : true

Hi I am using barryvdh/laravel-cors in Laravel 5.4 with angular 2 as front end
and i configured the cors manually
``
  'supportsCredentials' => false,
    'allowedOrigins' => ['*'],
    'allowedHeaders' => ['*'],
    'allowedMethods' => ['*'],
    'exposedHeaders' => [],
    'maxAge' => 0,
```
and it is working fine.

Now I am using to add a http only cookie in my project and i want to add that cookie from angular2 requests to authenticate.
so, to do that I am adding  withCredentials: true to the request from angular 2,

Now the server throwing cors related errors in console with 200 status.

and this repeats even i changed
  'supportsCredentials' => false,

to '

  'supportsCredentials' => true,

Please let me know where I am missing?
```

I am facing same issue with vue js from last week, @barryvdh please help

Can anyone please invetigate my repo? https://github.com/swapnil-chaudhari/sanskar

not work with vue.js

searched the whole github it seems no one can unravel this mystery

Can you try again with https://github.com/barryvdh/laravel-cors/releases/tag/v0.10.1 ?
Please re-open this issue when the problem still persists.

authors: barryvdh chinna-magapu holyzhuo hussainwali74 swapnil-chaudhari swapnil-chaudhari-1811

repo: barryvdh/laravel-cors


text:
Psaml phpdoc bug

Versions:

ide-helper Version: 2.10.0
Lumen Version: 8
PHP Version: 7.4

Description:
this
    /**
     * @param class-string<T> $className
     * @param null|string $driver
     * @return T
     * @noinspection all
     */
    public function instance( $className, $driver = null ){

turns into:
         * @param \SteveMoretz\Tools\Utils\MultiDrivers\Managers\class-string<T> $className
         * @param null|string $driver
         * @return \SteveMoretz\Tools\Utils\MultiDrivers\Managers\T
         * @noinspection all
         * @static
         */

(In case you are not familiar T is for generic, so it must not be namespaced)
how can I stop this from happening?

@mfn The change was actually reverted and is pending some test fixes here. I believe it is also the cause of #1401

authors: Jefemy Stevemoretz

repo: barryvdh/laravel-ide-helper


text:
Does this not support Redis autocomplete?

Does this not support Redis autocomplete? I tried Cache, it can autocomplete, but not for Redis.

Gotta give us more info: what kind of autocompletion do you want? Both Redis and Predis are visible within Laravel app, in PhpStorm 10 (due to a Metadata-file related bug, this package can't shine in PS 2016 for the moment, until Jetbrains fixes the issue). I just tested, they work fine, if you have imported them correctly.

For example, when I type Cache::, it will show :

While when I type Redis:: there is no tips:

Nope. Check your namespacing. It should be \Redis if you are namespacing:

@shehi It does not work:

Does the Redis class exist in the generate ide_helper file?

@barryvdh No, I searched for it, but find nothing.

And does the Predis\Client class exists?
See this check here: https://github.com/barryvdh/laravel-ide-helper/blob/e97ed532f09e290b91ff7713b785ed7ab11d0812/src/Generator.php#L188-L191
Does removing that check help?

@barryvdh No, that file does not contain anything about [Redis] or [Predis]

No I meant in your own application. See the referenced lines.

If I remove that line, it will return
[Symfony\Component\Debug\Exception\FatalThrowableError]
  Fatal error: Class 'Predis\Client' not found

Try Invalidating your PhpStorm cache and reindexing.

You are not using IDEA IntelliJ with PHP plugins, are you?

@shehi  Do you mean this?

I'm using phpStorm 2106.1

Okkk, please don't :) Revert back to 10.x as we have standing bug in 2016.*. See #340 . I'd say close this task until it's fixed, but I will let @barryvdh decide that.

But can you use the Redis class at all then? Don't you need the Predis Client installed to be able to use that?
That is why the check is there.

https://laravel.com/docs/5.2/redis

Before using Redis with Laravel, you will need to install the predis/predis package (~1.0) via Composer.

Just to be 100% sure, you did required the predis package?

@barryvdh @shehi Sorry for that, I just missed to install predis/predis. Thanks for helping me.

as  @dvikas said it's work for me.
i change use Illuminate\Support\Facades\Redis;  to use Redis;
thanks for your help @dvikas


text:
[PROPOSAL] Add more tests to the library

I don't know how others feel, but many of my projects depend on this library.
Eventually I would like to contribute, give back something to this great idea of the author and the community. My PR https://github.com/barryvdh/laravel-ide-helper/pull/859 was merged and I really wanted to write a test, but I realized: there is nothing (ok, 2 tests…) but also no infrastructure for running these kind of tests (Laravel framework setup, models to test, etc;) 😢
Laravel packages whose functionality depends on the Laravel framework cannot easily be tested just with PHPUnit alone and usually require https://github.com/orchestral/testbench
So what I did in this PR

(chore: moved tests into a dedicated Tests namespace)
removed phpunit and added orchestral/testbench (which itselds depends on PHPUnit…)
picked one small piece of code and wrote a test for it, to get things kickstarted
reworked travis and

removed actual running unit tests on very old PHP/Laravel versions (see below)
only run phpcs in one combination (usually the latest)

Immediate issues I encountered

According to the composer.json version constraints, this library supports VERY OLD versions of Laravel
composer could not resolve any combination for orchestral/testbanch for the older Laravel versions, I got multi-page of package resolution errors
I could not find a sane way to keep the old tests, depending on PHPUnit_Framework_TestCase, working with the supported versions of orchestral because it depends on newer phpunit version now aliasing PHPUnit_Framework_TestCase to PHPUnit\Framework\Testcase anymore

Since I could not find a solution to this, I simply decided to:

remove running the tests for these old versions/combinations
but keep the old versions in travis because they still run composer install and ensure the combination itself works

What does this mean?

I think eventually at some point the version constraints should be cleaned up and non supported versions probably be dropped. But I don't want to make this call and not in this PR
I hope to make it easier for others to not just contribute features but also add tests for them

I certainly offer to add more tests to bring them up to speed, but before investing more time I would first like this approach to be approved, I hope this is understandable 😄

I think we can bump the minimum version to laravel 5.5 (and the php version that supports that), or higher if that makes it easier.

And nice work :)
Should I merge this or should we bump the versions and simplify it a bit?

Merge is fine, I'll follow up with your suggestions!

authors: barryvdh mfn


text:
Use 'RR' when a prunable vclock is replicated

There may be some situations whereby a vector clock grows beyond the prescribed limits on the source cluster - in particular following read repair.
In these cases the new object needs to be replicated but with the same resulting vector clock (assuming no siblings).  If the same vector clock does not result on the sink - any full-sync operation may continuously detect the  delta, but not be able to resolve it (as the sink vnodes prune each time).
The 'rr' option will, on riak_kv_vnode, ensure pruning is bypassed so that we avoid pruning on a sink, if we have not pruned on a source.  The 'rr' option is only used when the clock is prunable (as otherwise the delta could occur in the reverse direction).
The 'rr' option also blocks some sibling constraint checks (e.g. maximum number of siblings.  However, as the most likely cause of it being applied is 'rr' on the src side - this is still generally a win for replication consistency.

https://github.com/basho/riak_test/pull/1379


text:
panelOLS.predict()  Help wanted

Hi Kevin,
As I've built a fixed-effect regression model for panel data, I want to use the panelOLS.predict() method to predict dependent variable values for different dataframes. I tried passing in 5 columns in a list as the input parameters, but it raised a ValueError.
I have three dataframes with the same column attributes:
df10 represents data of year 2010.

df16 represents data of year 2016.

df is a multi-level index dataframe contains both year 2010 and 2016 data. This df is used to build the fixed_effect model.

Codes:
Creating multi-level index to define the entities and the time periods
df10['YEAR'] = df10['YEAR'].astype(int)
df16['YEAR'] = df16['YEAR'].astype(int)
df = df10.append(df16, ignore_index=True)
df = df.set_index(['ID', 'YEAR'])
df = df.sort_index()

Building the fixed-effect model.
Both dependent and independent variables are dataframe columns.
mod_entity= "PanelOLS.from_formula("INRIX_VOL \
                       ~ CHAMP_VOL \
                       + TNC_VOL\
                       + AVG_DUR_MAJOR_ARTERIALS \
                       + AVG_DUR_MINOR_ARTERIALS \
                       + BASE_INRIX_VOL_PRESIDIO \
                       + EntityEffects",
             data = df)
res_entity = mod_entity.fit(cov_type='clustered', `cluster_entity=True)

Failed Attempt 1:
res_entity.predict(df[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])
Failed Attempt 2:
exog_vars = ['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']
exog = sm.add_constant(df10[exog_vars])
res_entity.predict(exog)

I read the documentation of panelOLS.predict(), but I still don't understand how to use the parameters. Please advise!

I can't run enough of the example to make is useful.  Here is a very plain example showing predict.
import numpy as np
import pandas as pd
from linearmodels import PanelOLS

year = np.arange(2010, 2020)
obs_id = np.arange(100)
index = pd.MultiIndex.from_product([obs_id, year], names=["id", "year"])
df = pd.DataFrame(index=index, columns=["y", "x"])
df = df.reset_index()

rg = np.random.default_rng(0)
x = rg.standard_normal(df.shape[0])
e = rg.standard_normal(df.shape[0])
y = x + e + df.id
df["y"] = y
df["x"] = x
df = df.set_index(["id", "year"])
mod = PanelOLS(df.y, df[["x"]], entity_effects=True)
res = mod.fit()
print(res.summary)

in_sample_fit = res.predict(df[["x"]])

new_df = pd.DataFrame(rg.standard_normal((300, 1)))
res.predict(new_df)

res_entity.predict(df[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])

looks like it should work. What error do you see with this?

One thing I notice is the df just have a 2-level multiindex or it is reshaped. What does df with this subsampling look like?

res_entity.predict(df[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])

looks like it should work. What error do you see with this?

Hi Kevin, this command does work, and it returns a desired dataframe. However, I want to predict the values for df10 and df16, and also a counterfactual case for df16 with some dummy variables being 0.
We I try
res_entity.predict(df10[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])
or res_entity.predict(df16[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])
A ValueError shows up:

ValueError: matmul: Input operand 1 has a mismatch in its core dimension 0, with gufunc signature (n?,k),(k,m?)->(n?,m?) (size 5 is different from 1)

Can you show the index of the data frame you are using?
On Thu, Dec 10, 2020, 19:23 Fitzroy notifications@github.com wrote:

res_entity.predict(df[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])
looks like it should work. What error do you see with this?
Hi Kevin, this command does work, and it returns a desired dataframe.
However, I want to predict the values for df10 and df16, and also a
counterfactual case for df16 with some dummy variables being 0.
We I try
res_entity.predict(df10[['CHAMP_VOL', 'TNC_VOL',
'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS',
'BASE_INRIX_VOL_PRESIDIO']])
or res_entity.predict(df16[['CHAMP_VOL', 'TNC_VOL',
'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS',
'BASE_INRIX_VOL_PRESIDIO']])
A ValueError shows up:
ValueError: matmul: Input operand 1 has a mismatch in its core dimension
0, with gufunc signature (n?,k),(k,m?)->(n?,m?) (size 5 is different from 1)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bashtage/linearmodels/issues/292#issuecomment-742740247,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKTSRM7CMVYOCPJ3AOKARDSUENZTANCNFSM4USTY3IA
.

One thing I notice is the df just have a 2-level multiindex or it is reshaped. What does df with this subsampling look like?
I'm pretty sure this is the problem.

I generated df by appending df16 to df10, and set a 2-level multiindex (id, year) to represent each entity. The subsampling df looks like this:

What are the indices of df10 and df16?  Are they the same as df?
Also, what do you get when you run

from linearmodels.panel.data import PanelData
panel = PanelData(df10[['CHAMP_VOL', 'TNC_VOL', 'AVG_DUR_MAJOR_ARTERIALS', 'AVG_DUR_MINOR_ARTERIALS', 'BASE_INRIX_VOL_PRESIDIO']])
print(panel.shape)
print(panel.dataframe.head())

Kevin, thank you for your further explanations! I figured out the problem, as my df10 and df16 only have one single index instead of   a multi-index. I really appreciate your time!

authors: bashtage machenyufitz

repo: bashtage/linearmodels

license: NCSA


text:
Please test the beta release: V0.12.0

Dear soundfile community,
Find attached a beta release of the next version of soundfile, with

libsndfile v1.2.0
manylinux binary wheel
improved libsndfile discovery

I would be grateful if you could test the wheels on the platform of your choice, and report back if they work, or if there are any issues.
soundfile-0.12.0.wheels.zip

Hrm, I just gave this a spin in a fresh conda environment, and it does not appear to be working.  I think it's pulling my libsndfile from the operating system and not the wheel:
libsndfile1/jammy,now 1.0.31-2build1 amd64 [installed]
  Library for reading/writing audio files

libsndfile1-dev/jammy,now 1.0.31-2build1 amd64 [installed]
  Development files for libsndfile; a library for reading/writing audio files

→  which pip
/home/bmcfee/miniconda/envs/sndfile-testing/bin/pip
 🐍 sndfile-testing  ~/sndfiletest 
 →  pip install ./soundfile-0.12.0-py2.py3-none-manylinux_2_31_x86_64.whl
Processing ./soundfile-0.12.0-py2.py3-none-manylinux_2_31_x86_64.whl
Requirement already satisfied: cffi>=1.0 in /home/bmcfee/miniconda/envs/sndfile-testing/lib/python3.9/site-packages (from soundfile==0.12.0) (1.14.6)
Requirement already satisfied: pycparser in /home/bmcfee/miniconda/envs/sndfile-testing/lib/python3.9/site-packages (from cffi>=1.0->soundfile==0.12.0) (2.21)
Installing collected packages: soundfile
Successfully installed soundfile-0.12.0
 🐍 sndfile-testing  ~/sndfiletest 
 →  cd
 🐍 sndfile-testing  ~ 
 →  python
Python 3.9.0 | packaged by conda-forge | (default, Nov 26 2020, 07:57:39)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import soundfile
>>> soundfile.__libsndfile_version__
'1.0.31'
>>> soundfile.__version__
'0.11.0'
>>> soundfile.__file__
'/home/bmcfee/miniconda/envs/sndfile-testing/lib/python3.9/site-packages/soundfile.py'
>>>

@bmcfee thank you for testing the library.
It seems that soundfile is picking up your system's libsndfile. If you have libsndfile installed on your system, soundfile will always try that first, before trying to load its own. You should see the soundfile-provided libsndfile if you uninstall/mask the system's libsndfile.
But you did find a bug regardless, I forgot to update the __version__. I'll fix that right away.

To test it, I added a line after 149 with _libname = None
https://github.com/bastibe/python-soundfile/blob/77444fea53086dc3b581815ae8c59eab9b2a6a5d/soundfile.py#L149-L151
Doing this, it loads the provided libsndfile and the version is 1.2.0
>>> import soundfile
>>> soundfile.__libsndfile_version__
'1.2.0'
>>>

I also tested loading an MP3 with librosa.load() and soundfile.read() and this worked both times.

It seems that soundfile is picking up your system's libsndfile. If you have libsndfile installed on your system, soundfile will always try that first, before trying to load its own. You should see the soundfile-provided libsndfile if you uninstall/mask the system's libsndfile.

Imo this should be reversed. Messing with the system installed packages does not seem like a good plan.

@Barabazs thank you for testing the lib!

Imo this should be reversed. Messing with the system installed packages does not seem like a good plan.

I understand and perhaps even agree with that. However, let's discuss this in a separate issue. Please open an issue to collect opinions on the load order.

It seems that soundfile is picking up your system's libsndfile. If you have libsndfile installed on your system, soundfile will always try that first, before trying to load its own. You should see the soundfile-provided libsndfile if you uninstall/mask the system's libsndfile.

Right, that's exactly what's happening.  It's maybe worth noting that this does not happen with the conda build, likely because conda environments will prioritize the local env's LD_LIBARARY_PATH above the operating system.  This seems sane to me, under the principle of going from most specific to least specific search path, but that's just my take.
That said, it's probably a good idea if all distributions of the package were consistent in this behavior (and across platforms - i've only tested linux), just to cut down on the possibility of unpredictable bugs down the road.

After thinking about the problem some more, I think I have come around to this point of view as well. We should indeed prioritize our packaged libsndfile over the system-provided one, especially on linux, where the system's libsndfile is likely outdated. (It really doesn't matter much on Windows or macOS, since there's unlikely to be a system libsndfile anyway).
As such, I have updated the wheels to first look for the packaged libsndfile, and only fall back to the system libsndfile if the packaged one is unavailable or incompatible.
Please do test this again to make sure I didn't break anything in doing so! (The link to the wheels in the initial post of this PR has been updated)

I gave this a spin, and hit some snags.
The first problem was my fault - I cloned the repo and switched to this branch without pulling in the submodule for the data files.  The build script still ran successfully, but the wheels did not include the .so files and that tripped me up. I didn't see anything about submodules / pull --recurse in the contributing guidelines, so you might want to add a note there.
After fixing the submodule, I rebuilt the packages, and it looks like it should work for most platforms, but the linux build is still missing the .so file (obvious from the file sizes, confirmed by checking with unzip):
 🐍 sndfile-testing   v0.12.0 +  ~/src/python-soundfile 
 →  ls -l dist
total 4220
-rw-rw-r-- 1 bmcfee bmcfee   23681 Feb  9 07:03 soundfile-0.12.0-py2.py3-none-any.whl
-rw-rw-r-- 1 bmcfee bmcfee 1212695 Feb  9 07:03 soundfile-0.12.0-py2.py3-none-macosx_10_9_x86_64.whl
-rw-rw-r-- 1 bmcfee bmcfee 1094038 Feb  9 07:03 soundfile-0.12.0-py2.py3-none-macosx_11_0_arm64.whl
-rw-rw-r-- 1 bmcfee bmcfee   33034 Feb  9 07:03 soundfile-0.12.0-py2.py3-none-manylinux_2_31_x86_64.whl
-rw-rw-r-- 1 bmcfee bmcfee  887094 Feb  9 07:03 soundfile-0.12.0-py2.py3-none-win32.whl
-rw-rw-r-- 1 bmcfee bmcfee 1007969 Feb  9 07:03 soundfile-0.12.0-py2.py3-none-win_amd64.whl
-rw-rw-r-- 1 bmcfee bmcfee   42426 Feb  9 07:03 soundfile-0.12.0.tar.gz

Contrast with the wheel archive @bastibe posted at the beginning of this PR:
 🐍 sndfile-testing  ~/sndfiletest 
 →  ls -l
total 5264
-rw-rw-r-- 1 bmcfee bmcfee 1212764 Feb  6 10:39 soundfile-0.12.0-py2.py3-none-macosx_10_9_x86_64.whl
-rw-rw-r-- 1 bmcfee bmcfee 1075436 Feb  6 10:39 soundfile-0.12.0-py2.py3-none-macosx_11_0_arm64.whl
-rw-rw-r-- 1 bmcfee bmcfee 1174205 Feb  6 10:39 soundfile-0.12.0-py2.py3-none-manylinux_2_31_x86_64.whl
-rw-rw-r-- 1 bmcfee bmcfee  887692 Feb  6 10:39 soundfile-0.12.0-py2.py3-none-win32.whl
-rw-rw-r-- 1 bmcfee bmcfee 1008568 Feb  6 10:39 soundfile-0.12.0-py2.py3-none-win_amd64.whl

Again, the wheel builds without failure, but now it fails to import:
>>> import soundfile
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'soundfile'
>>> import soundfile
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/bmcfee/miniconda/envs/sndfile-testing/lib/python3.9/site-packages/soundfile.py", line 162, in <module>
    _path = _os.path.dirname(_soundfile_data.__file__)
  File "/home/bmcfee/miniconda/envs/sndfile-testing/lib/python3.9/posixpath.py", line 152, in dirname
    p = os.fspath(p)
TypeError: expected str, bytes or os.PathLike object, not NoneType

Looks like the problem is that the _soundfile_data submodule does not actually have the linux_x86_64.so binary, at least not for the version hash used in this branch.  Switching the submodule over to the master branch fixes this, and now it works:
>>> import soundfile as sf
>>> sf.__version__
'0.12.0'
>>> sf.__libsndfile_version__
'1.2.0'

Summary: I expect most of my problems here are due to my unfamiliarity with the repo structure and build process for this package, but the end result does appear to work as expected.

I must have botched the linux wheel somehow. Thank you for catching that! I'll try to post fixed wheels later today.

Great, LIS it's probably PEBKAC on my side :grin:
But it might not hurt to make the build script a little more sensitive to missing object files if they really need to be there.

I've added some documentation on the wheel build process, and fixed your TypeError.

authors: Barabazs bastibe bmcfee

repo: bastibe/python-soundfile


text:
Nlevel examples

I added two example scripts for three-level atoms. While I was at it, I noticed that many of the .jl examples still had using quantumoptics instead of QuantumOptics, so I changed that as well. @bastikr please review and merge.

Coverage remained the same at 0.0% when pulling c35db8c332f80f4fc2b501f57c00407ab8481252 on david-pl:nlevel-example into 0016e90dad6b54da4760e97f92d025c092fb8b42 on bastikr:master.

authors: coveralls david-pl


text:
Add New News Ticker Design

Add new responsive new ticker designs based on bootstrap library and please follow the points stated in Contributing.md .
Happy hacking !!

Hello!
How does a moving ticker like this look?  :)

Hello!
How does a moving ticker like this look? :)

This looks good , but a personal suggestion you could have made the background of news ticker black instead of medium red .
Happy coding and keep contributing :heart:

Ohh, apologies for that  :(
I will surely keep it in mind from now on.
Should I change the color of the container?


text:
attempt to improve performance of pages with many modals

On my laptop it isn't very slow either way, so it would be interesting for me to know if it makes a difference on your machine

Great solution!
Old code

With change from PR

nice! :)

authors: saemideluxe wipascal

repo: basxsoftwareassociation/bread


text:
Theming: Set default transition type via theme xml

Hello team. Would it be possible to implement the ability to set the type of transition (fade, instant, etc) from system list to games list via theme xml?
I don't know if it will be very difficult to implement, but I think it would be very positive for the UX in some cases.
Thanks!

Done.
See this commit :
https://github.com/batocera-linux/batocera-emulationstation/commit/254b289e2d18b9da6ef2f2c6e9811bed03806bef

Thanks for your work! :)

authors: fabricecaruso pajarorrojo


text:
Write Part - 3 Step - 7 & unit test

Implement Step07Controller and write all unit tests. Verify the display name of the test conforms to the pattern of "Part X Step Y". Follow the standardize naming, comments, etc. to be consistent.

Same as Part 01 Step 16(#21)


text:
Python hierarchy and mixing

In this PR we present the draft version of our work, implementing

the python hierarchy;
the python mixing;
generalized structure for states and hypers;
hierarchy and mixing 'switchers';
new structure of directories and corresponding CMake files.

*The documentation and styling of the code are not yet done.
We would like to mention that we did try using the 'make opaque' technique to pass by reference between c++ and python, but that surprisingly didn't improve the performance.
To build the library:
$ mkdir build
$ ./make_.sh

To run an example using the python implementations:
$ python3 docs/examples/test_run.py
We would like to hear your comments, questions and advice to improve the code before the final PR (we will need to open one in bayesmix too, since there are minor modifications also there).

Thanks a lot for the work!
The PR at the moment is too big, you should split it up in smaller chunks so that I can review them separately. Let's start with the part about the Python hierarchy, since I'm already familiar with that.
On a side note, I think that the most critical part will be the overall build system. I noticed some weir stuff:

stan math is included in a submodule, but that's already in the bayesmix submodule... please keep only the bayesmix one
there are copy-pasted cmakelists files around, it makes life harder for me to figure out what's going on.

In the end, we must be able to build this as one or two python packages (cf #14)
Please let me know when the PR is ready for a first round of review

Hi. We followed your request and opened a new PR with only the python hierarchy. We also removed the lib/math from submodules (we had added it at some point because of tbb problems but fortunately it is not needed anymore). About the CMake stuff, we followed the "if it's working, don't touch it" rule :). We would like to hear a more in depth comment about that to understand what should be changed.
How would you like us to proceed with the python mixing PR? Should we open a new one without the hierarchy, or we should wait untill this one is merged?
Also, we're starting to work on the report and to not create a clutter in the last days, we would like to send each chapter when it's ready for the review, if you don't mind :)

authors: mberaha taguhiM

repo: bayesmix-dev/pybmix


text:
Add reference

Description of issue
A clear and concise description of the perceived problem/missing content.
In page 197, TPE (j. bergstra et al.) in density ratio estimation part, it refered 73-75. But it would be nice that it contains the latest paper, "A General Recipe for Likelihood-free Bayesian Optimization" [J. Song et al.]. This paper proved that the density ratio is Probaibility of Improvement not Expected Improvement.
Proposed resolution
A clear and concise description of what you'd like to see.
Add this in footnote 74: "J. Song et al., proved that it is the probability of improvement"
Additional context
Add any other context or screenshots about the feature request here.
Additional context
Add any other context or screenshots about the feature request here.

See https://github.com/bayesoptbook/bayesoptbook.github.io/issues/10.

right. The paper that I mentioned is (almost) same with the paper mentioned in the thread (NeurIPS workshop paper). The authors are the same. Thank you for reply!

To the best of my knowledge this result first appeared in early November 2021 in the issue linked by @georgedeath, and was added to the book in mid-November of that year. That predates the workshop paper by 4-6 weeks. Song, et al. discovered the same fact contemporaneously, and they in fact acknowledged this in the 2022 paper, citing the book.

authors: bayesoptbook euphoria0-0 georgedeath


text:
bazel test fails on 11.0.19 with ClassNotFoundException: allow when setting up SecurityManager

I am debugging a weird issue where test execution fails with:
Error occurred during initialization of VM
java.lang.Error: Could not create SecurityManager
	at java.lang.System.initPhase3(java.base@11.0.19/System.java:2065)
Caused by: java.lang.ClassNotFoundException: allow
	at jdk.internal.loader.BuiltinClassLoader.loadClass(java.base@11.0.19/BuiltinClassLoader.java:581)
	at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(java.base@11.0.19/ClassLoaders.java:178)
	at java.lang.ClassLoader.loadClass(java.base@11.0.19/ClassLoader.java:522)
	at java.lang.Class.forName0(java.base@11.0.19/Native Method)
	at java.lang.Class.forName(java.base@11.0.19/Class.java:398)
	at java.lang.System.initPhase3(java.base@11.0.19/System.java:2050)

The flag is added by JUnit5 macros.
https://github.com/bazel-contrib/rules_jvm/blob/25eaad37a4df4708fed207480158348cede52838/java/private/junit5.bzl#L97
I inspected the runfiles tree and liballow.jar as well as the allow.class is on the classpath. Yet the JVM (Azul 11.0.19) is failing to load the SecurityManager.
Discussion at https://bazelbuild.slack.com/archives/CDCE4DFAP/p1693898959307139
A possible workaround is:
bazel test //test_target --test_env="JVM_FLAGS=--version -Djava.lang.SecurityManager=default"

For some reasone --test_env="JVM_FLAGS=-Djava.lang.SecurityManager=default" did not work. I had to use --test_env="JVM_FLAGS=--version -Djava.lang.SecurityManager=default".

This seems to be a MacOS specific problem. The MacOS 13.5.x update series seems to have change the Max Open File handles implementation significantly.
I needed to add -XX:-MaxFDLimit on the test JVM for those tests with many files and long classpaths. On the command line the workaround is: add/set --test_env="JVM_FLAGS=--version -XX:-MaxFDLimit".


text:
Long filepath issue on Windows

A TODO for this was introduced in #48
https://github.com/bazel-contrib/rules_ruby/pull/48/files#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR48
Try removing the exclusion and see if there's a way to fix it.

Related to https://github.com/jruby/jruby/issues/3995#issuecomment-2558240341

It looks like an upstream issue, can be worked around on CI by using really short output_base like D:/b:
https://github.com/bazel-contrib/rules_ruby/blob/0a2d57b805640d9c4d141bec45dcefea3df39b44/.github/workflows/ci.yml#L67-L68


text:
Add long long support for OSQP

This is needed so that osqp-cpp can build on Bazel and #2134 can be merged.
The author has added some comments, concerns about enabling DLONG. Please let me know what else is to be done.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (osqp-cpp) have been updated in this PR. Please review the changes.

repo: bazelbuild/bazel-central-registry


text:
Open .BUILD files in bazel-build-mode

My work uses this convention where we put the build files for third-party vendored libs into a single directory that has a bunch of files named things like nameofdep.BUILD. I've seen this convention used in other bazel repos as well, notably this is the same convention that Envoy uses: https://github.com/envoyproxy/envoy/tree/master/bazel/external
The way I've implemented this (by pushing another item to the auto-mode-alist) probably isn't right, it would be better to update the rx expression on the line above. But I don't really grok how to use rx, so if you want to close this PR and update the rx expression that would also make me happy.

Thanks for the contribution, this makes sense.
To write this as rx expression, you'd probably use something like:
(rx (or "/BUILD" "/BUILD.bazel" ".BUILD") eos)

authors: eklitzke phst

repo: bazelbuild/emacs-bazel-mode


text:
Java: sources not viewable for junit

I was able to reproduce this using the java-maven project in the examples repo: https://github.com/bazelbuild/examples/tree/5547cbe71a77c237ab78be0803726102f230e1a5/java-maven
IntelliJ Info:
IntelliJ IDEA 2019.1.3 (Ultimate Edition)
Build #IU-191.7479.19, built on May 27, 2019
JRE: 1.8.0_202-release-1483-b58 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6

Bazel plugin info:
Running locally built latest master branch: e82fa3e2419e0f7bd2d251545dd7402be3c49b77
Bazel version: 0.25.0
Steps taken:

Open file com/example/myproject/TestApp.java
Command-click (or equivalent modifier to view source) on the assertEquals text on line 14.

Expected Behavior:
IntelliJ should navigate to full source code.
Actual behavior:
IntelliJ navigates to decompiled .class file:

That example using maven_jar does not download source jars (we should update that..). maven_jar is deprecated, please use rules_jvm_external to manage your third party dependencies instead. I've submitted a PR to update it: https://github.com/bazelbuild/examples/pull/107

Looks like it's working :)

Thanks @jin !

authors: drichelson jin

repo: bazelbuild/intellij


text:
Update rules_python to 0.28.0

for WORKSPACE dependencies. MODULE.bazel already uses this version.

All the jobs seem to be mistakenly showing as queued, where in fact they have run successfully (I can see it in the Actions tab). Merging the PR.

authors: mering stefanbucur


text:
Reproducible RPM build host and build time

If you want to control the RPM Build host metadata, use _buildhost in your RPM spec
If you want to control the Build time metadata, the SOURCE_DATE_EPOCH environment variable must be declared within the context of running rpmbuild.
PR is forthcoming with support for SOURCE_DATE_EPOCH
For context, see:

https://reproducible-builds.org/docs/source-date-epoch/
https://wiki.yoctoproject.org/wiki/Reproducible_Builds

Related to https://github.com/bazelbuild/rules_pkg/issues/105

Closing.  The build time part is done.  The rest should be addressed in #53

If you want to control the RPM Build host metadata, use _buildhost in your RPM spec

how to do ? please show a sample .spec ,thank you very much!

authors: aiuto mmikitka wxlg1117


text:
Reorganize the source tree

WORKSPACE moves up one level

this makes //:pkg.bzl effectively //pkg:pkg.bzl
put forwarders in place at top level to not break anyone

tests moves up one level
toolchains moves up one level
examples/**/BUILD do not change to the new rule locations

this is explicitly to provide some proof that the forwarders work
new examples should use the proper paths to .bzl files
near the 1.x release we can clean the current ones up

Fixes: #104

I'll take a deeper look shortly, but one quick thing that comes to mind is that while this won't break anyone using the release archive, it will break people directly cloning the git repo.  Is this intentional?  Seems fine to me.

I am fine with that. I don't think it will break that many people, because
they old workspace is still around,
On Wed, Nov 3, 2021 at 11:37 AM Andrew Psaltis @.***>
wrote:

I'll take a deeper look shortly, but one quick thing that comes to mind is
that while this won't break anyone using the release archive, it will break
people directly cloning the git repo. Is this intentional? Seems fine to me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/443#issuecomment-959477776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHFRFIW35DTLP4CGV4DUKFQNPANCNFSM5GOZZNQQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I am fine with that. I don't think it will break that many people, because
they old workspace is still around,

That's fine, but looking at https://github.com/aiuto/rules_pkg/tree/reroot/pkg, the old WORKSPACE seems to be missing.

I am at $ rpmbuild --version
RPM version 4.16.1.2
I fail with
File
"/usr/local/google/home/aiuto/.cache/bazel/_bazel_aiuto/307c3de820d1750f8c959c1b06ff6c18/sandbox/linux-sandbox/251/execroot/rules_pkg/bazel-out/k8-fastbuild/bin/tests/rpm/source_date_epoch/source_date_epoch_from_file.runfiles/rules_pkg/tests/rpm/source_date_epoch/rpm_contents_vs_manifest_test.py",
line 100, in test_buildtime_set
self.assertEqual(actual_epoch, EXPECTED_EPOCH)
AssertionError: '1635968773' != '1616472000'

1635968773

1616472000

On Wed, Nov 3, 2021 at 3:41 PM Andrew Psaltis @.***>
wrote:

@.**** commented on this pull request.
In tests/rpm/source_date_epoch/BUILD
https://github.com/bazelbuild/rules_pkg/pull/443#discussion_r742274241:

@._pkg//pkg:mappings.bzl", "pkg_filegroup", "pkg_files")
@._pkg//pkg:rpm.bzl", "pkg_rpm")

Huh. I thought that they would be skipped, given what I have here:
https://github.com/bazelbuild/rules_pkg/blob/main/pkg/tests/rpm/source_date_epoch/rpm_contents_vs_manifest_test.py#L57-L64
That change may simply not be working, though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/443#discussion_r742274241,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHHHB24OXPYAAXHB4JTUKGNADANCNFSM5GOZZNQQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

authors: aiuto nacl


text:
Improve classpath manifest file construction

Description
Improve classpath manifest file construction
Motivation
See: https://github.com/bazelbuild/bazel/pull/9314

Great work! Thanks for upstreaming this also!

authors: anchlovi johnynek


text:
Multiple instances of netbox-sync collides

I have two completely isolated networks, no connectivity between the two of them. I attempted to run two copies of netbox-sync, and used different source names in each instance.
The problem, though - is each instance is marking the other instances items as orphaned.
I can understand the logic in this, but could it be a setting? e.g. "orphan_missing_sources=false"

Figured this out. I needed to use the same config in both places, and just disable the corresponding sources. Worked like a charm!

repo: bb-Ricardo/netbox-sync


text:
on_send not called for when blocks with multiple conditionals

For this code
case foo
when 1, 2
  raise bar(3)
end

on_send will not be called for bar(3). For this code
case foo
when 1
  raise bar(2)
end

it is called

What does ruby-parse output in either case?

@alexdowad for the first one
(case
  (send nil :foo)
  (when
    (int 1)
    (int 2)
    (send nil :raise
      (send nil :bar
        (int 3)))) nil)

for the second one
(case
  (send nil :foo)
  (when
    (int 1)
    (send nil :raise
      (send nil :bar
        (int 2)))) nil)

Aha. Nice catch.

I have a fix.

Do you have some "real life" code which you encountered this problem on? Would be good for a test case.

My real-life example boiled down pretty well to this test code. It just had longer variable names.

Hmm. That code doesn't cause an offense either way... but, whatever.

Sorry, I was building a Cop internally to remove all the ,) from the codebase, and the on_send wasn't being called. Not sure if you have other cops, but maybe the multiline comma one won't have inserted a , into a when block with two args.
Here was my cop if it matters.
  class WeirdComma < RuboCop::Cop::Cop

    MSG = 'Stop doing a weird comma'.freeze

    def on_send(node)
      _receiver, _method_name, *args = *node
      check(node, args)
    end

    private

    def check(node, elements)
      right_paren = node.loc.end
      return unless right_paren

      comma = right_paren.begin_pos - 1
      range = Parser::Source::Range.new(node.source_range.source_buffer, comma, comma + 1)
      return unless range.source == ','

      add_offense(range, range, MSG)
    end

    def autocorrect(range)
      lambda do |corrector|
        corrector.remove(range)
      end
    end
  end

authors: alexdowad ptarjan

repo: bbatsov/rubocop


text:
🛑 wiki.bbon.kr is down

In 1c06798, wiki.bbon.kr (https://wiki.bbon.kr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: wiki.bbon.kr is back up in 74cdadf.

repo: bbonkr/uptime


text:
Add support for SMTP pipelining

https://tools.ietf.org/html/rfc2920
For our email sending, we have noticed that the latency is being dominated by the outgoing SMTP send. We are currently using the simple-java-mail library, but are considering evaluating https://github.com/HubSpot/NioSmtpClient so that we can optimize the SMTP connection by taking advantage of it's pipelining feature.

Interesting, I had never heard of pipelining before...
That said, have you looked into using Simple Java Mail's batch-module? With it you get a connection pool with reusable Transport connections that don't close. Even having a pool of one connection that doesn't close can double your performance as up to half of the time spent on sending an email is simply opening up a Transport connection.

At first glance, as Simple Java Mail builds upon Jakarta Mail (previously JavaMail), it seems impossible to configure support at this level. Simple Java Mail doesn't handle the actually server commands such as EHLO and Jakarta Mail has no support for pipelining, and looking around a bit, it doesn't seem to be on the radar either. I'll do a bit more research, but I'm afraid I'll have to wait for Jakarta to make a move here.

That should be fine, we are going to try tuning our connection pool size and lifecycle and see where that gets us.

Any update on your performance?

We haven't had the capacity to fix it yet. I've changed teams as well. I'll let them know they can follow up here if necessary.

In that case I'll close the issue until further notice. But looking forward to your performance update.

If you know more by now, I'm still curious as to your findings.

I haven't worked on the announcements team for almost two years and have left the company as well. I'd refer you to Zubair Khan who is the current lead on the team, but i don't see him on LinkedIn and have no way to contact him otherwise.

repo: bbottema/simple-java-mail