[operations] Implement process_voluntary_exit

https://github.com/lambdaclass/lambda_ethereum_consensus/blob/dd0a0523e6be2a21fa3f6a96d4466926307d236c/docs/specs/beacon-chain.md?plain=1#L2899-L2917
See Spec tests format: https://github.com/ethereum/consensus-specs/tree/dev/tests/formats/operations
Acceptance criteria:

Run corresponding spec tests

Can I take this?


Expose JwtExpiration as environment variable via configMap

Expose JwtExpiration as environment variable via configMap
Add JwtExpiration as a number of minutes to configmap and env var via Kabanero Document

@davco01a @brutif We should have a conversation about where this belongs in the Kabanero document.  The things we've added so far were directly related to our interaction with Github, and so they were in a Github: section of the Kabanero document.  How do we explain to the user what this is?  I am guessing they are not going to know what JwtExpiration is or how it affects what they are doing.  I'm assuming that this is the amount of time that a user's session with the CLI will remain until they have to log in again.  Do you have a recommendation as to how we can add this to the Kabanero document in a way that the user will understand?

KabaneroCLILoginExpiration may be a better name

Agree that this is broader than just github, but documenting shouldn't be too hard, we just have to find a suitable spot in the Kabanero document

@kaczyns @davco01a can you point me to the document please?

@brutif the document @davco01a is referring to is the Kabanero CRD:
https://raw.githubusercontent.com/kabanero-io/kabanero-operator/master/deploy/crds/kabanero_kabanero_crd.yaml
There are several spec: sections - the section that has properties: and then github: is the one we are referring to.  There is a cliServices: section that was recently added, maybe that's where this goes.  Something like spec.cliServices.sessionExpirationMinutes maybe....

@kaczyns thanks.  I was looking at https://github.com/kabanero-io/docs/blob/master/ref/general/installing-kabanero-foundation.adoc and not seeing anything about editing any kind of config file, which might still be a gap. Whatever you and @davco01a think is a good name is fine, adding detection of the environment variable to the app is trivial once we know it's name.

cliServices.sessionExpirationMinutes sounds good to me

we'll need to get this into into:  https://github.com/kabanero-io/docs/issues/66

directly into env var is fine

closing, resolved by https://github.com/kabanero-io/kabanero-operator/pull/213


 Please add your planning poker estimate with Zenhub @saravanpa-aot @tiagograf-AOT @djnunez-aot @VineetBala-AOT

Scan to Notify API to finish


If forceUrl = 1 can't login get redirected to auth page

The issue is that when I turn on forceUrl = 1, Authentication and Registration does not work.
If I turn it off, language switching does not work.
In a video, you can see my issue in more details.
Here I made a video, sorry that handheld.
https://www.youtube.com/watch?v=9cAoE_sRvPI
[Stabilized video]
https://www.youtube.com/watch?v=h__GyP4FAP8
Please let me know where could be my problem.
Thanks

Look at the RainLab.Translate plugin, I believe the forceUrl thing was a workaround for session handling on build 420+ if I remember correctly.
Try taking a stab at digging into what forceUrl on the RainLab.Translate plugin component is doing to the RainLab.User plugin yourself and keep us updated on your progress. Good luck!

Closing as it has been over a month since any activity on this occurred and we are trying to figure out what issues are still relevant. If this is still something that you would like to see through to fruition please respond and we can get the ball rolling.


Delete expired non-active sessions

Due to a bug fixed in https://github.com/vespa-engine/vespa/pull/13338
we ended up with sessions that are in state ACTIVATED in zookeeper,
but that was not the latest active session.  These would not be
cleaned up, the changes here will delete these sessions (if they are
expired and not the current active session for an application).
Also deletes a test that was covered by tests in ApplicationRepositoryTest.

This could potentially be a lot of data and there may be a need to partition the deletion like was done with the old sessions flag?

Yes, that might be a good idea, I'll look into it

@hakonhall please take a look


Allow parameters with * to accept zero or more arguments

Closes #633
Hi @casey, I'd appreciate any comments you have to make on my implementation.
I personally think we should try to come up with a name to separate variadics prefixed by * and +. I think this will make both the code and documentation clearer to understand. You'll see that I've referred to them as "zero or more" and "one or more" as I couldn't think of a better way to summarize the cardinalities!

Oh yeah, I also wanted to add some color about some of the things I try to keep in mind when thinking about a change like this. I don't think they're issues in this case, but they're good to keep in mind.
The first is that there are a relatively small number of ascii symbols, making each one kind of precious. Whenever a new one is added to Just, I try to think about whether or not it's the best use of that character, or some other use or meaning might be more appropriate. In this case, I think * is totally appropriate, since it has a well established meaning that users are likely to understand.
The second is to try to think about potential conflicts or ambiguities in the grammar, current or future. There is actually an ambiguity in the grammar with +, since it can be ambiguous whether or not a + is introducing a new, variadic argument, or if it's a concatenation:
foo a=b + c

There are other reasons why this doesn't work, namely that you can't have a required argument after one with a default, but ignoring that for a second, it's ambiguous whether the user means foo a=b +c or foo a=b+c.
With * variadics, I don't think there are any conflicts now, but it's good to think about if there could be conflicts in the future. I think it's okay though, since any other reasonable usage of * that I can think of wouldn't introduce a conflict.

Oh, almost forgot, * should be added to GRAMMAR.md, probably like so:
recipe        : '@'? NAME parameter* variadic? ':' dependency* body?

parameter     : NAME
              | NAME '=' value

variadic      : '*' parameter
              | '+' parameter

Also, unless it's part of your workflow, you don't need to force-push the branch. You can just push new diffs, and I'll squash and merge at the end.

I keep forgetting things >_< It would also be good to add a test in parser.rs, see the recipe_variadic test. It should test that it produces a + instead of a * when + is given.

Wow, I really appreciate all the comments. Thanks!
It's really useful to have some insight into some of your thoughts behind introducing changes like this to Just.

You bet!
I think allowing default values for * args is probably desirable. I agree that it's technically redundant, but I expect that users will be surprised that they can't give a * a default value.
Also, I just thought of this, I think that prefix should return Option<&'static str>. It simplifies a couple of the call sites, since they can do:
if let Some(prefix) = kind.prefix() {
  // use prefix
}

Instead of having to call is_variadic. Also, I noticed that the "" prefix for singular arguments is never actually used.

It's funny you mention that about prefix, I actually thought of doing that but reasoned that the explicit variadic check was a little clearer. This was before the method was renamed to prefix though which definitely helps with clarity.

Merged! Thanks for doing this, it's a great addition!


[Autocomplete] 'ref' does not exist in ListboxProps in TypeScript

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/listboxprops-ref-bn67hk?file=/src/Autocomplete.tsx
Current behavior 😯
I'm trying to provide a ref to ListProps in an Autocomplete. In general, it seems to work, but the following error message appears:

Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

It's not just a matter of a missing type. If you provide a custom ref to ListboxProps, it'll overwrite the one used internally by useAutocomplete.
I can't think of a good reason not to allow providing an own ref, so we can fix it and sync the ref provided in ListboxProps with the one returned from useAutocomplete.

@ZeeshanTamboli VS Code show error when trying to add a ref into the ListboxProps

but the code were working without any issue
"@mui/material": "5.10.11",

Please open a new issue and link a reproduction so we can see the error ourselves.


vdk-cicd: during a scheduled run publish_artifacts and release shouldn't run

Why
We want to be able to run scheduled jobs.
But as part of the scheduled jobs we want to skip publish_artifact jobs and also release jobs.
This change should not have any impact on the pipeline and I will start running the scheduled jobs once we see the pipeline is still green for merge triggered builds.
In the future I might extract the rule into a shared abstract job. But that will be a later PR
What
Add a guard on all publish_artifact jobs and also release jobs so that they won't run if it is triggered by a scheduled operation.
I also upgraded helm if we are testing everything we should try upgrade that too. The hope here is that it fixes https://github.com/vmware/versatile-data-kit/issues/1252.
How has this been tested
Not much, mostly visual inspection.
closes https://github.com/vmware/versatile-data-kit/issues/1254

Please assign the https://github.com/vmware/versatile-data-kit/issues/1254 to yourself. And linked it in teh ticket.

could explain in the PR description what are the changes expected? for example, I am wondering why the vdk-heartbeat publish/release stages are handled, and the vdk-control-cli are not?

Fixed

for convenience, you can also link the gitlab schedule created, to save time (I went to find it on my own)

for convenience, you can also link the gitlab schedule created, to save time (I went to find it on my own)

the schedule is not actually created yet.
that schedule you are looking at it for a branch and it does a pretty bad job of testing it.
I will create the schedule when I know I have not introduced regressions in the current builds.

Still don't understand why some gitlab ci yaml files are changed, and some are not.....for example https://github.com/vmware/versatile-data-kit/blob/main/projects/vdk-control-cli/.gitlab-ci.yml#L86 ?

It is changed, but I only changed it after you pointed it out.
Do you see other examples where I am not doing it?

Is it possible to configure the rule to be "opt-in" - run on schedule only the jobs marked as such.
Instead of opt-out as it's now (excluding jobs) ?
With opt-in , it's easier to start with smaller set of jobs and add more incrementally until we are happy

Is it possible to configure the rule to be "opt-in" - run on schedule only the jobs marked as such. Instead of opt-out as it's now (excluding jobs) ?
With opt-in , it's easier to start with smaller set of jobs and add more incrementally until we are happy

IMO opt out is better so we are testing more by default.
I think the problem with current setup with both my solution and your suggested solution is that it touches soo many lines of code.
I think we should try make an abstract job for each stage. all jobs in that stage should extend it.
That way it is super easy to skip an entire stage.
However I only want to try that after I have identified all the edge cases etc..
Let me know what you think?

Is it possible to configure the rule to be "opt-in" - run on schedule only the jobs marked as such. Instead of opt-out as it's now (excluding jobs) ?
With opt-in , it's easier to start with smaller set of jobs and add more incrementally until we are happy

IMO opt out is better so we are testing more by default.
I think the problem with current setup with both my solution and your suggested solution is that it touches soo many lines of code. I think we should try make an abstract job for each stage. all jobs in that stage should extend it. That way it is super easy to skip an entire stage.
However I only want to try that after I have identified all the edge cases etc..
Let me know what you think?

With opt-out if we add a new component/plugin build job, it would be automatically included in the scheduled nightly build. Which is a good thing.
But if we add a new release job then it would be automatically included which is not what we want.
But if we can extend a stage, as you suggest, then we can opt out "release" stage. Unless somebody releases in the wrong stages, there's no problem with wrong jobs being included.
So I like this..
OK. Let's go with the proposed plan. First let's identify the  what jobs need to be included and what not.
Then we can refactor to support inheriting abstract job for each stage. Which would likely be useful for other purposes as well.


[Python][C++] Transient issue with PyGILState_Release with S3

Describe the bug, including details regarding any error messages, version, and platform.
Since updating from pyarrow==12.0.0 to pyarrow=14.0.1, I have transient issues with some of my python jobs.
I have simple ETL jobs, they load a few parquet files from s3, manipulate the data with a mix of pyarrow and pandas, and save one parquet file to s3.
Since updating to pyarrow==14.0.1, some of my jobs (something like 1 out of a 1000) are failing. Here are the symptoms:

I see this message in stderr:

Fatal Python error: PyGILState_Release: auto-releasing thread-state, but no thread-state for this thread
Python runtime state: finalizing (tstate=0x000056046142faa0)

My job orchestrator (aws batch) report a return code of 139 which stands for :

139 – Occurs when a segmentation fault is experienced. Likely, the application tried to access a memory region which it not available, or there is an unset or invalid environment variable.

From looking at the full log and the expected side effect of my job (aka the s3 file that is saved), it looks like the job is sucesfull

So it pretty much looks like the job fails while releasing resources after it's done running.
I can't create a reproducible example, simply because the error is transient. Also I can't really isolate which update is causing the issue. I was updating fsspec and s3fs at the same time as I was updating pyarrow. But I'm not sure they use PyGILState_Release.
I looked at relevant issues and code in the repo, but couldn't find any relevant change. It could be related to this https://github.com/apache/arrow/issues/38626 but I doubt it (I don't use atexit.register).
Component(s)
Python

cc @jorisvandenbossche @pitrou
I remember there were some issues with S3 finalization on C++ but I am not sure if this could be related.

@0x26res Which Python version are you using?

@pitrou I'm using 3.10.13 (more specifically I'm running it on a docker image built from python:3.10.13-slim-bullseye)

Is it possible for you to check with a more recent Python version such as 3.12.1?

We have plans to migrate to 3.11, which should happen in the coming weeks. 3.12 isn't possible at the moment (because of pytorch).
Also given the issue is transient, and I have to run a lot of jobs before it happens, it's hard to pin point. But I can keep you updated as I upgrade dependencies, if I see the issue disappear.
In your opinion, could it be because of fsspec or s3fs (do these library use PyGILState_Release)?

Is the code in question doing something similar to the reproducer in https://github.com/apache/arrow/issues/36980? That could be another potential cause of segfault in acquiring the GIL after interpreter shutdown.

In your opinion, could it be because of fsspec or s3fs (do these library use PyGILState_Release)?

Well, this is the Apache Arrow issue tracker, so you'll probably won't find people with the specific knowledge you're asking for. The fsspec and s3fs projects are not related to us, and they have dedicated issue trackers where you can ask that question.
I'm also going to point out that Arrow (and PyArrow) comes with its own S3 filesystem wrapper, but you're using a third-party one here. Of course, there can be legitimate reasons to that, but it also complicates the picture quite a bit.

I haven't had the issue since updating to 14.0.2 (though it's hard to be 100% sure that the issue is gone).
I'll close the issue, thanks for your help/suggestions.


Add reverse order option

I've added the --reverse-order option.
This option for the index command to reverse gist index order.
Thank you!

nice work, thanks @AsaiToshiya


This is a simple script to start the bot.

Anyone on windows who has the dependencies and node.js installed can run this and the bot will start. As long as this batch file is in the bots root directory it will start the bot. If the /src folder is renamed the batch file will not run

Oh, this looks good, thanks! Can you change it so it instead cd's into the dir and runs npm start instead? That's the way I recommend starting the bot in the README nowadays.

@Dragory fixed it could you also checkout my other pull request?

If you would like I can add an option to pick a color for the text
ex. Enter G into the command prompt and the color would be green

Maybe the start-up script should run npm install every time you start the bot? Since if all packages are installed, it's just a quick check and shouldn't really slow down the start-up. This would then technically do what #21 does as well.

Okay all add the install check

@Dragory its ready let me know if I should add color.

Since you wanted me to use npm start instead of the src/index.js I cant clear the console messages during npm or rename the console to Modmailbot Console.

@Dragory In case you forgot!

Hey, haven't forgotten! Just busy with something right now. I'll get back to this ASAP.

Okay @Dragory

Any chance of getting one of these made for Mac?

@Ragnarok345 http://www.tldp.org/LDP/abs/html/dosbatch.html
Though really there's no need to script this stuff; it's not like it automagically restarts the bot if it crashes, it just saves you a couple commands.
I'd recommend instead just checking for updates occasionally, and running the bot in a tmux session so you can detach and close the window, but still get back to it later (you'll need homebrew to install tmux https://brew.sh/ )

@sporkwitch Thanks for the answer, though I never saw it until now. Is there a way to make this bot auto-restart if it goes down in Terminal for Mac?


AGP 8.3.0 and newer crash: IllegalAccessError: Illegal class access: 'androidx.media3.session.MediaSessionStub' attempting to access 'com.google.common.util.concurrent.ImmediateFuture'

Version
Media3 1.3.1
More version details
No response
Devices that reproduce the issue
Device independent
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Not tested
Reproduction steps

Update to Android Gradle plugin 8.3.0 or newer (lates stable version tested 8.4.1)
Build release with enabled R8/Proguard
Run

Expected result
Same as before Android Gradle plugin 8.3.0
Actual result
java.lang.IllegalAccessError: Illegal class access: 'androidx.media3.session.MediaSessionStub' attempting to access 'com.google.common.util.concurrent.ImmediateFuture' (declaration of 'androidx.media3.session.MediaSessionStub' appears in /data/app/~~C7jbUjGUUAag6n0y-f9nBw==/com.sample.app-Y_Ap45lP0wrXLHxbDEeR_Q==/base.apk)
at androidx.media3.session.MediaSessionStub.R(MediaSessionStub.java:1)
at androidx.media3.session.S.f(R8$$SyntheticClass:10)
at androidx.media3.session.I0.run(R8$$SyntheticClass:11)
at androidx.media3.session.b.run(R8$$SyntheticClass:282)
at androidx.media3.session.e.run(R8$$SyntheticClass:222)
at androidx.media3.common.util.Util.Q(Util.java:26)
at androidx.media3.session.ConnectedControllersManager.b(ConnectedControllersManager.java:70)
at androidx.media3.session.ConnectedControllersManager.c(ConnectedControllersManager.java:30)
at androidx.media3.session.e.run(R8$$SyntheticClass:28)
at androidx.media3.common.util.Util.Q(Util.java:26)
at androidx.media3.session.MediaSessionStub.T1(MediaSessionStub.java:46)
at androidx.media3.session.G.handleMessage(R8$$SyntheticClass:45)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8177)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)
Media
Related Stack overflow thread created by another dev:
https://stackoverflow.com/questions/78102596/android-media3-gradle-8-4-agp-8-3-0
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

At first glance this looks like an R8 bug. We don't reference the com.google.common.util.concurrent.ImmediateFuture class directly anywhere in our source code. However we do regularly invoke Futures.immediateFuture which instantiates an ImmediateFuture internally. My guess is that R8 has in-lined this Futures.immediateFuture() method in a way that it looks like the app is directly trying to invoke the ImmediateFuture constructor (which is package private).

I disagree with your analysis. The lines you linked are where we invoke the public Futures.immediateFuture method. Since this is public, this shouldn't throw an IllegalAccessError which is:

Thrown if an application attempts to access or modify a field, or to call a method that it does not have access to.

The error is complaining about interacting directly with the com.google.common.util.concurrent.ImmediateFuture class which is package private, so if accessed directly from an app would cause IllegalAccessError.

We are already using AGP 8.3.2 on the main branch: https://github.com/androidx/media/blob/1640becddd1b84d5be0d815e6f87b8454b5870c4/build.gradle#L20
I have tried to repro this issue in the session demo app by hacking MediaSessionStub to invoke Futures.immediateFuture "more often" by changing the conditions you linked to this:
if (true || sessionImpl.isReleased()) {
  return Futures.immediateFuture(
      new SessionResult(SessionResult.RESULT_ERROR_SESSION_DISCONNECTED));
}

But I don't see the crash even with the release variant of the demo app (and the invocation does complete, because I added a log line just after it). Playback no longer works with this hack, but that's kind of expected - the key thing is there's no crash or IllegalAccessError.
I also logged the R8 version to be sure, and it seems to match the problematic version reported on Stack Overflow:
8.3.37 (build 3ccc501316db4344828180e7152a4adb97522bf8 from go/r8bot (luci-r8-custom-ci-focal-17-2jq9))

Are you able to repro locally? The stack overflow post reports that they are not.
If you are, please can you provide us an Android Studio project we can build to reproduce the problen locally?

I also tried the same hack to repro on 1.3.1 in the session demo app (after bumping the AGP version), and was unable to see the IllegalAccessError crash.

Hello Ian,
thank you very much for trying to solve the problem. You are right, I can't reproduce it in Media3 Demo App (main branch), but I can reproduce it locally in our project.
We don't use directly the mentoied com.google.common.util.concurrent.ImmediateFuture class. Just Futures.immediateFuture() in the MediaLibraryService.MediaLibrarySession.Callback.
The only other usage from the com.google.common.util.concurrent package is com.google.common.util.concurrent.ListenableFuture in our MediaBrowserConnector and MediaControllerProvider with Kotlin coroutines guava library.
I will try to investigate this usages in more detail and let you know.

This R8 bug from 2022 (fixed) looks very similar to my in-lining hypothesis:

https://issuetracker.google.com/243955191 java.lang.IllegalAccessError with R8 3.3.75

But I haven't found any other evidence or reports of a regression on this.

I can reproduce it locally in our project.

Can you provide the exact deobfuscated call-stack when it occurs? (i.e. where are we in MediaSessionStub?)

This is the best I have from many attempts to Re-trace obfuscated local call-stack:
java.lang.IllegalAccessError: Illegal class access: 'androidx.media3.session.MediaSessionStub' attempting to access 'com.google.common.util.concurrent.ImmediateFuture' (declaration of 'androidx.media3.session.MediaSessionStub' appears in /data/app/~~zKXg8nwD0a_CezwCu2anrA==/com.sample.app.prepro-kBJiCxhrlY9BO_w6UuK14w==/base.apk)
at androidx.media3.session.MediaSessionStub.R(SourceFile:1)
at androidx.media3.session.MediaControllerStub$$ExternalSyntheticLambda7.f(SourceFile:10)
at androidx.media3.session.MediaSessionStub$$ExternalSyntheticLambda78.androidx.media3.session.MediaSessionStub.lambda$queueSessionTaskWithPlayerCommandForControllerInfo$13(SourceFile:11)
at androidx.media3.session.ConnectedControllersManager$$ExternalSyntheticLambda1.androidx.media3.session.ConnectedControllersManager.lambda$flushCommandQueue$2(SourceFile:282)
                                                                               run
at androidx.media3.session.MediaBrowser$Builder$$ExternalSyntheticLambda0.androidx.media3.session.MediaSessionImpl.lambda$callWithControllerForCurrentRequestSet$3(SourceFile:222)
                                                                        run
at androidx.media3.common.util.Util.postOrRun(SourceFile:26)
at androidx.media3.session.ConnectedControllersManager.flushCommandQueue(SourceFile:70)
at androidx.media3.session.ConnectedControllersManager.flushCommandQueue(SourceFile:30)
at androidx.media3.session.MediaBrowser$Builder$$ExternalSyntheticLambda0.androidx.media3.session.MediaSessionStub.lambda$flushCommandQueue$64(SourceFile:28)
                                                                        run
at androidx.media3.common.util.Util.postOrRun(SourceFile:26)
at androidx.media3.session.MediaSessionStub.flushCommandQueue(SourceFile:46)
at androidx.media3.session.MediaControllerImplBase$FlushCommandQueueHandler$$ExternalSyntheticLambda0.androidx.media3.session.MediaControllerImplBase$FlushCommandQueueHandler.flushCommandQueue(SourceFile:45)
                                                                                androidx.media3.session.MediaControllerImplBase$FlushCommandQueueHandler.handleMessage
                                                                                handleMessage
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8177)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)

This R8 bug from 2022 (fixed) looks very similar to my in-lining hypothesis:

https://issuetracker.google.com/243955191 java.lang.IllegalAccessError with R8 3.3.75

But I haven't found any other evidence or reports of a regression on this.

So I'll probably start an issue for R8 directly in the Google issue tracker, right?

Yeah I think reporting to R8 makes sense: https://r8.googlesource.com/r8#getting-help

https://issuetracker.google.com/issues/345248270


[WIP] Michelson style adaptive blocking

relates to #444

Coverage decreased (-1.6%) to 71.528% when pulling 56cc90f3a3bf3db97ffc4ad40c96d6187173cc2d on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage decreased (-1.2%) to 71.928% when pulling 9be1469605e668e1474b6bed1f847bf737bcd787 on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+0.8%) to 73.926% when pulling b9a4a570831171ca315c431d263981735f80cb2c on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+0.9%) to 74.076% when pulling b9a4a570831171ca315c431d263981735f80cb2c on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+0.9%) to 74.076% when pulling 6882f70d6422b1148153fade376808c1320884ec on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+0.9%) to 74.076% when pulling 2ab69a622af85290e1004957454ad08d697f658f on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+1.3%) to 74.448% when pulling da7a8c93e7e4ac5b660458fb2a0af90d96219cdf on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+1.2%) to 74.373% when pulling 14c6b9535b46aa2dc8240fd6ac8cbe6f09b594df on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+1.3%) to 74.41% when pulling 23dcc90a7e5f99e5d1bd907be80c3edf284f56df on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage decreased (-0.3%) to 72.885% when pulling c1d5d3b144e16c7abc16127520eecb598a9190bf on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage decreased (-0.2%) to 72.921% when pulling 6dd398906c85999bbfb19b5d3b63f7a16cb1189b on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+0.01%) to 73.17% when pulling 4e61aa9a75488ab4a4fe126696b29ec755e3a7b4 on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.

Coverage increased (+0.5%) to 73.629% when pulling 5f3fdf0622bd7f82fd385a663d90e4b1e82b6f26 on michelson into 947ce1b48c70278e3f570ee55212432786468998 on master.


Install/update a package with drag&drop

This PR adds an Install/Update Packages button to the Add Functionality page, this button opens a dialog with a drop zone :

PS : Feel free to comment if you have any suggestion or improvement for this feature.

Here are some screenshots of the different steps and states possible when uploading a file :

When a request is done, the .dz-preview is updated to highlight its status :

You can then hover the element to show the response message, if there is an error :

If the installation (or the update) was successful :

The user can upload any packages with this feature, even if it is not approved by PRB, right?
IMO, c5 core should not include this type of insecure feature. It should be an add-on and should be marked as Bleeding Edge.

To consider everyone needs, what about adding a configuration key to enable/disable this feature?

Good idea @mlocati 👍
Should we enable this feature by default or not ?

To upload a package to packages directly, the attacker should get the SSH/FTP connection. This feature makes much easier to do the same thing. WordPress is one of the most attacked CMS. In my point of view, many attacks are started with uploading malicious plugin.

I'm proud of concrete5 doesn't have this type of vulnerable feature (upload and unzip via the dashboard, editing PHP files on the dashboard ). We can implement unzip function easy, but we didn't.

Thanks for all your hard work @marvinde - but I agree with @hissy and others on this. This was actually something we used to have in very early builds and then removed for reasons stated here. We have consciously avoided adding this feature.
Thanks again for the work, but this isn’t something we can add.

@aembler I'm glad to hear your opinion. thanks.
@marvinde Your work is interesting. I'll buy it if this package is released on the marketplace.

@a3020 Users cannot install the marketplace item marked as Bleeding Edge via the dashboard. The only administrator who has enough knowledge can install and use it by their own responsibility.

However, PRB might not pass this type of add-on. Sorry. I'm not a PRB member, so I don't know enough about that.

The difference between external addon install being in a package and it being baked into the core is that in a package:

A site owner decides if they want it,
The package can be uninstalled and the functionality removed. For example, it can be used during development and removed when a site goes live.

Installing an addon, whether marketplace or external, is never without some risk of breaking a site or introducing malicious code. That risk exists whether an addon is installed manually or automatically. In some ways automatic installation is safer because it eliminates user error. In some ways automatic installation is more dangerous because less capable users can install without fully understanding what they are doing.
Personally, I think drag and drop makes it a little too easy to make a mistake and drag/drop the wrong thing and brick a site. That is why I didn't implement drag-drop-install in package magic. https://www.concrete5.org/marketplace/addons/package-magic/
From a PRB point of view, an addon that implements package upload/install, with or without drag and drop, is not precluded from approval, but it does have to demonstrate reasonable safeguards to prevent the drag-drop-brick scenario. It would also need to stay clear of implementing a competing marketplace.
From the town hall yesterday, @mnakalay made a point about the core being better structured to support integration of other package sources (but not to actually provide such integration). I fully agree with that objective.


fixed broken config file for circleci

Fixed broken config
deleted unnecessary file

What's happening with this one?


Failed to lookup address information: Name does not resolve

OS version: Linux / Debian 10 "Buster"
Editor: vim
Editor version: 8.1
Programming language: Rust
TabNine extension version: 2.9.2

Logs:
[2021-01-11][19:21:15][TabNine][INFO] Port 38843 was provided. Emulating YCMD.
[2021-01-11][19:21:15][lunar_transport::controller][INFO] Creating lunar client...
[2021-01-11][19:21:15][frontend::ycmd_emulation][INFO] Listening at <IP_ADDRESS>:38843
[2021-01-11][19:21:15][lunar_local::bridge][INFO] TabNine Local communication thread started.
[2021-01-11][19:21:15][lunar_local::bridge][INFO] Loading model...
[2021-01-11][19:21:15][lunar_transport::controller][INFO] TabNine Cloud is disabled, communication thread is sleeping until configuration change...
[2021-01-11][19:21:15][lunar_local::locker][INFO] Trying to lock: "/tmp/model.lock"
[2021-01-11][19:21:15][lunar_local::locker][INFO] Lock acquired, performing the inner action
[2021-01-11][19:21:15][lunar_local::downloader][INFO] Starting download (last_failure=None).
[2021-01-11][19:21:15][lunar_local::downloader][INFO] Tried to find cached metadata but got 'No such file or directory (os error 2)', so downloading it instead...
[2021-01-11][19:21:15][updater][INFO] Making API request to https://api.tabnine.com/model_metadata/v1
[2021-01-11][19:21:15][lunar_local::downloader][ERROR] https://api.tabnine.com/model_metadata/v1: error trying to connect: failed to lookup address information: Name does not resolve
Issue Details:
TabNine fail to connect to tabnine.com so can't register or anything else. I did expect issues with http proxy (both upper and lower case https_proxy are defined) running within a corporate environment but failing on name resolution is much less expected.
Impact is mostly that I can't register (nor download anything of course).
Being a Rust developer, please tell me if there's any lib/framework I could locally to help investigate.

Hi
This sounds like some firewall or corporate DNS that is blocking the request.
Can you ask your IT to check that?

Hi
This sounds like some firewall or corporate DNS that is blocking the request.
Can you ask your IT to check that?

Hi, thanks for the feedback.
The thing is that https://api.tabnine.com/ is not filtered by the proxy. If it was I would also expect some sort of "contents blocked" (or any such retrieval error) but much less a name resolution issue.
Failing at using the proxy seems a plausible reason for not being able to resolve. This might just boil down to assessing whether proxy env (or any other conf) are taken into consideration but I can't find straightforward way to find that information out of the logs (I've tried usual http{s}_proxy upper and lower case without success).
Is there any info/doc about how proxy details are to be passed in?
Thanks a lot,
Seb

Hi, thanks for the feedback.
The thing is that https://api.tabnine.com/ is not filtered by the proxy. If it was I would also expect some sort of "contents blocked" (or any such retrieval error) but much less a name resolution issue.
Failing at using the proxy seems a plausible reason for not being able to resolve. This might just boil down to assessing whether proxy env (or any other conf) are taken into consideration but I can't find straightforward way to find that information out of the logs (I've tried usual http{s}_proxy upper and lower case without success).
Is there any info/doc about how proxy details are to be passed in?
Thanks a lot,
Seb

@spaolacci Tabnine will use HTTP_PROXY and HTTPS_PROXY environment variables if present.
Remember that Tabnine is run by your editor, so these environment variables need to be defined in such a way that the editor you are using will see them.
But I think you are right that if you fail to resolve api.tabnine.com then it will not help.
What happens if you run
curl https://api.tabnine.com
Do you still get the "Failed to resolve" error?

@spaolacci Tabnine will use HTTP_PROXY and HTTPS_PROXY environment variables if present.
Remember that Tabnine is run by your editor, so these environment variables need to be defined in such a way that the editor you are using will see them.
But I think you are right that if you fail to resolve api.tabnine.com then it will not help.

Hi,
Just to confirm curl and others standard tools have no issue at reaching the url (incl. this very browser).
As a (sort of) more precise check, I've verified that both vim (:!env) and TabNine proceses (outer and inner variants through /proc/$pid/environ) were having the two HTTP_PROXY and HTTPS_PROXY environment variables defined. I didn't manage to find anything suspicious here.
strace-ing the process in command line did show 1) access to environment variables 2) attempts at reaching my DNS (after opening /etc/hosts and /etc/resolv.conf confirming proxy info was just not taken into consideration).
It happens that issue was in the way the HTTPS_PROXY variable was populated. Replacing HTTPS_PROXY=myproxy:8080 by HTTPS_PROXY=http://myproxy:8080 (mind leading http://) did the trick. This is not that usual but here it is.
Everything is fine now, I managed to upgrade to 3.34-9 and register :).
Thanks a lot for your help.
Seb

Hi,
Just to confirm curl and others standard tools have no issue at reaching the url (incl. this very browser).
As a (sort of) more precise check, I've verified that both vim (:!env) and TabNine proceses (outer and inner variants through /proc/$pid/environ) were having the two HTTP_PROXY and HTTPS_PROXY environment variables defined. I didn't manage to find anything suspicious here.
strace-ing the process in command line did show 1) access to environment variables 2) attempts at reaching my DNS (after opening /etc/hosts and /etc/resolv.conf confirming proxy info was just not taken into consideration).
It happens that issue was in the way the HTTPS_PROXY variable was populated. Replacing HTTPS_PROXY=myproxy:8080 by HTTPS_PROXY=http://myproxy:8080 (mind leading http://) did the trick. This is not that usual but here it is.
Everything is fine now, I managed to upgrade to 3.34-9 and register :).
Thanks a lot for your help.
Seb


[intel-mkl] Add feature(s) to support installation of both ilp64 and lp64 versions of MKL

Is your feature request related to a problem? Please describe.
Currently the intel-mkl port install only "ilp64" version of MKL. There are projects which require the "lp64" version which can't use intel-mkl without modifications.
Is there a particular reason why the intel-mkl port install only a small subset of ML versions available in packages downloaded from Intel? The main issue I would see is that some of the libraries are rather large and will significantly increase the install size.
Proposed solution
The simplest solution would be to just install all versions of MKL provided by the packages downloaded from Intel. Alternatively the different versions could be gated using features like "ilp64" and "lp64".
Describe alternatives you've considered
One may either install a stand-alone MKL outside of vcpkg. Alternatively one can modify the the project code and build scripts to support the "ilp64" interface.
Additional context
No response

Is there a particular reason why the intel-mkl port install only a small subset of ML versions available in packages downloaded from Intel?

Because you can only link one consistently. Allowing to select one of them requires the options PR. If you want to switch just provide an overlay and change the one line in the portfile which decides between ILP and LP version.

I'm not sure I follow...
The ilp64 and lp64 interfaces have different libraries and you can select one or the other to link. I can select one or the other using CMake find_package(BLAS/LAPACK) by setting the relevant BLA_SIZEOF_INTEGER and BLA_VENDOR variables

The ilp64 and lp64 interfaces have different libraries

different libs but same symbols.

Yes, but any project that already uses oneAPI needs to select which version of the installed MKL libs to link against. Is there a particular reason not to use already existing build tooling to handle this issue?

Yes, but any project that already uses oneAPI needs to select which version of the installed MKL libs to link against.

Be aware that the MSbuild integration links *.lib. vcpkg does not allow to install libs with conflicting symbols due to that.

For example the FindBLAS/FindLAPACK in CMake allow making this selection on the fly

vcpkg BLAS/LAPACK cannot allow that. There can only be one true implementation. (ODR)


It´s only writing the filename.ext on file manager, not the full path.

Hi!
Im trying to use PyAutoIt to select a file and hit "open", but it is not writing the full path to the file, just the fila nema and extension, and because by default the file manager doesn't start in the directory the file is in, i get an error saying the file doesn't exist.
Can someone help ?
handle = "[CLASS:#32770; TITLE:Open]" autoit.win_wait(handle, 60) autoit.control_set_text(handle, "Edit1", 'C:\\codigos\\TCBot\\LastIdeaCropped.png') autoit.control_click(handle, "Button1")

Does the open box start with anything in the Edit1 field when it opens or is it blank at first?


support arrays in function call schema

this PR

updates oaiParams to include the items property in arrays to match  openAI's function call schema requirements (fixes issue #124)
updates  oaiParams  to omit optional fields from the required section of the generated openAI function call schema
adds unit tests for oaiParams

 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.

hi! thanks for the fix, especially for the unit tests, we really need to add a full suite of those sooner rather than later ^^;
i've enabled CI tests for you, please check that it all passes fine, and if you could revert the package.json and CHANGELOG changes -- we have a bot handle our versioning for us.

hi! thanks for the fix, especially for the unit tests, we really need to add a full suite of those sooner rather than later ^^; i've enabled CI tests for you, please check that it all passes fine, and if you could revert the package.json and CHANGELOG changes -- we have a bot handle our versioning for us. additionally since this involves minor changes could you please point this to v0.4.0 instead of main?

Yes, I'll revert the package.json and changelog changes. I'll also point to the v0.4.0 branch instead


Update SV_Simulator.cpp

remove unused FORMAT fields from SNP records

This should fix https://github.com/fritzsedlazeck/SURVIVOR/issues/189


Verify input support for lists in objectives/components/pipelines/automl

We should verify if list inputs work for objectives/components/pipelines/automl.
Originally from https://github.com/alteryx/evalml/pull/1450#discussion_r528741774
I believe lists may work because _convert_to_woodwork_structure handles the list data type, but in objectives, we call _standardize_input_type which doesn't.

@angela97lin @dsherry Does this mean that we want to make sure components work if we pass in lists to fit_transform() or predict_proba()? Having our objectives makes sense, but I'm not sure if this means that for all class functions, if we can accept pd/ww data structures, we'd want to also be able to accept lists and numpy arrays?

@angela97lin @dsherry Does this mean that we want to make sure components work if we pass in lists to fit_transform() or predict_proba()? Having our objectives makes sense, but I'm not sure if this means that for all class functions, if we can accept pd/ww data structures, we'd want to also be able to accept lists and numpy arrays?


Update brusselator.md

Alex,
There is a typos
At line 137 & line 146, the position of the variable time, here described using the indices (k),  should be at the 3rd position as in solu = sol[u(x, y, t)] and in solv = sol[v(x, y, t)] I  had also to remove the plots directory  at line 139 &  line 148 and left only the just created gif file.  This way the example runs perfectly.
Naceur

Thanks!


Comfort features for different play speeds

Double buffer video unless running very slowly (where you would want to see individual scanlines render)
Disable audio when running very fast or very slow

Codecov Report

Merging #24 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
- Coverage   94.44%   94.44%   -0.01%
==========================================
  Files          42       42
  Lines        5279     5276       -3
==========================================
- Hits         4986     4983       -3
  Misses        293      293

Impacted Files
Coverage Δ

src/emulator/io/mod.rs
97.05% <100%> (-0.24%)
:arrow_down:

Continue to review full report at Codecov.

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


cmd/internal/obj/arm64: use movz and movk to load large constants

Get rid of the pool by using movz/movk to load constants.
Replaces 4ad/go#140.

Too late for Go 1.5.


[Update Request]: MinIO Clinet

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
MinIO.Client
Package Version
2024.10.02
Please describe the changes you would like to see
There is a new release (RELEASE.2024-10-02T08-27-28Z) available.
Download Page Url: https://dl.min.io/client/mc/release/windows-amd64/archive/mc.RELEASE.2024-10-02T08-27-28Z

[!TIP]
Modify your very first comment of the pull request will help associating that pull request to this issue.
Only #number is accepted for linking pull request with the issue. Other formats are not supported.
  Checklist for Pull Requests

  * [x]  Have you signed the [Contributor License Agreement](https://cla.opensource.microsoft.com/microsoft/winget-pkgs)?
- * [x]  Resolve [[Update Request]: MinIO Clinet #178578](https://github.com/microsoft/winget-pkgs/issues/178578)
+ * [x]  Resolve #178578

@Dragon1573
Thank you so much for sharing this helpful tip! I really appreciate your input and will definitely be applying it moving forward.


Test array of raw values with unmappable element

Is that the same thing? What I'm testing here is:
given an array of strings ["valid1", "valid2", "invalid"]
mapper will map to an array of enums [.valid1, .valid1]

Ah you are using that. I thought the context here was hoping that this wasn't the behavior.

Yeah, I wanted a test around this behavior (which is current) so that if this assumption breaks we hear about it.
I've got an array of strings coming down from the backend that map to an enum:
enum Foo: String {
  case one
  case two
}

If already deployed clients with this definition of Foo start receiving a third string (say we've made a backend change and are sending down ["one", "two", "three"]), I want to ensure that the already deployed client still maps to [.one, .two] and not [].

Yep definitely. The test you edited here does cover this case since optionalFrom is implemented as try? from

Yeah it's super close. Maybe close enough (if you think it is I'll cancel this no sweat). The only difference in setup is that the new test does not expect an optional. Implementation-wise I'm sure this doesn't make a difference, but from a caller's perspective there could be a subtle difference in behavior between asking for thing: [Foo] = try map.from(...) and thing: [Foo]? = map.optionalFrom(...). Figured a test would make this explicit

Yep sounds good!


number literal evaluation is wrong

There are edge cases in number literal evaluation (NumberSource.value) that are still wrong. For example, it'll just panic if given too large of an exponent in a decimal literal. I will have to study the spec and real implementations.

For the sake of example, I've runned esprit against all the latest versions of CDNjs libs and such occurences cause esprit to panic:
18446744073709551616
0x8000000000000000
1208925819614629174706176
0x10000000000000000

I'm not sure why someone uses verbatim numbers which can't be represented correctly in JS anyway, but in the worst case this should be a parsing error, and in the best, we should try and simulate engine behaviour by manually parsing into f64 digit by digit.

Fixed the decimal integer cases, radix one still persists and f64::from_str_radix was removed from Rust core and has to be simulated.

Should be fixed for radix integer cases too now.


docs: Use Argo Events sources

Signed-off-by: Derek Wang<EMAIL_ADDRESS>Closes: #90

Would it be possible to directly connect to the NATS Streaming? That way an outage in a pipeline would be tolerated.

Would it be possible to directly connect to the NATS Streaming? That way an outage in a pipeline would be tolerated.

That also works with a filter. I can add it to the doc.

I think we need to provide robust solutions.


Add link to Tracing UI (e.g. Otel) in trace logs

e.g. via some kind of callback: getTracingUiUrl = (spanId, traceId) => 'https://jaeger....'

Will mark this as superseded by https://github.com/Effect-TS/effect/issues/1363


document giraph version; juju2 updates

To make it easier for users to know what version of giraph will be installed
by this charm, call it out in the metadata and READMe.md
Since the release of bigtop-1.2, all bigtop charms require juju2. Remove
references to juju < 2 from the README.

@panagiotisl FYI, the apache-bigtop-base layer was updated to support bigtop-1.2:
https://github.com/juju-solutions/layer-apache-bigtop-base/commit/8f5f8f3191164843ed7c7de60fed3869b4f6843a
The next time you build the giraph charm, it will automatically be configured to use this new release.  If you'd like to update the charmstore with this new support, the steps are as follows:
$ cd bigtop-packages/src/charm/giraph/layer-giraph
$ charm build -r --no-local-layers --series xenial
...
build: Destination charm directory: /home/ubuntu/charms/xenial/giraph
...
$ cd /home/ubuntu/charms/xenial/giraph
$ charm proof
$ charm push `pwd` ~panagiotisl/giraph
...
<charmstore url>
...
$ charm release --channel candidate cs:~panagiotisl/giraph-<#>

I forgot to mention the reason this is important...
All other bigtop charms are now using bigtop-1.2.  Because giraph is a subordinate charm, it would be incompatible with the current bigtop charms -- basically it would try to install from the bigtop-1.1 repo while the principal charm is now only configured for bigtop-1.2.

@kwmonroe It seems that I cannot release the built charm, I get an:
ERROR cannot release charm or bundle: unauthorized: access denied for user "panagiotisl"
Maybe it has something to do with the fact that the charm is promulgated. Also, should I make a merge request of the new code to bigtop?


Error during test.

Arguments [ 'testJson' ]
TEST JSON
TOTAL TIME: 50.31 s
(node:10810) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/sweb/tmp/javascript-serialization-benchmark/src/tmp/plot.json'
    at Object.openSync (fs.js:465:3)
    at Object.writeFileSync (fs.js:1416:35)
    at loadPlotData (/sweb/tmp/javascript-serialization-benchmark/src/utils/helper.ts:130:8)
    at savePlotData (/sweb/tmp/javascript-serialization-benchmark/src/utils/helper.ts:136:16)
    at Object.<anonymous> (/sweb/tmp/javascript-serialization-benchmark/src/utils/helper.ts:67:3)
    at Generator.next (<anonymous>)
    at fulfilled (/sweb/tmp/javascript-serialization-benchmark/src/utils/helper.ts:5:58)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:10810) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10810) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

$ python3 plot.py
plot.py:188: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if i < len(baseline_y_values) and baseline_y_values[i] is not 0:
Matplotlib is building the font cache; this may take a moment.
Traceback (most recent call last):
  File "plot.py", line 135, in <module>
    with open(INPUT_FILE) as json_file:
FileNotFoundError: [Errno 2] No such file or directory: 'tmp/plot.json'

Fixed and improved.
https://github.com/Adelost/javascript-serialization-benchmark/pull/3


Implement a link from session info redirect to room

Hi @lcduong this feature does not work smoothly yet. In the test room of @odkhang here the "Join" button disappears during the page loading: https://video-dev.eventyay.com/schedule/talks/RAFUSN

Ok, I think I found the issue. It seems like you are using the exact room name as an identifier. Expected would be that you use the "eventyay-talk"-ID (formerly Pretalx-ID).


metadata content-disposition support

Description
I am unable to set content-disposition metadata using aws pipeline. I can submit the change request but unable to push my changes to this repo. Can someone please add this support or give me necessary permissions to create a pull request?
github account<EMAIL_ADDRESS>Steps to Reproduce

[First Step]
[Second Step]
[and so on...]


Adding contributor's name in Readme file

I would like to work on this issue. Kindly assign this to me under LGM SOC.

Can I work on this issue?


select.ts limit,start fix

Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
Obvious possibility of having the query fail
What does this change do?
Fixes the limit parameter check that erroneously looks at start
What is your testing strategy?
obviously passing start parameter will also trigger limit which can be undefined
Is this related to any issues?
not seen
Have you read the Contributing Guidelines?

[x] I have read the Contributing Guidelines

Ha! Thanks 😄
I had it done locally but was working on some other changes before pushing again

Couldn't resist the edit in place option, as I noticed it wasn't yet forked in my github 🤣


no_std will not compile

Hello,
Excited to try out your lib on embedded, but having some trouble compiling. it seems num-traits still uses std, even if default-features is set to false:
~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/num-traits-0.2.19/src/lib.rs:23:1    | 23 | extern crate std;    | ^^^^^^^^^^^^^^^^^ can't find crate    |    = note: the thumbv7m-none-eabi target may not support the standard library

Hi! I think the problem is numeric-array, which is bringing in num-traits with the std feature enabled. I opened an issue there.

Hi, I looked into it a bit more and came to the same conclusion. Thank you for looking into this so quickly!

Hello again,
I've successfully compiled fundsp targeting "thumbv7m-none-eabi" (stm32f103 cortex M3). This is an 32-bit MCU, so I had to make some alterations to  not use 64-bit types for targets that doesn't support those. Perhaps not the cleanest solution, and perhaps you do not have the intention of supporting such hardware. But if you do, feel free to take a look at my fork, specifically this commit. I would be happy to change it to align it to your architecture/structure.

Thanks for your work. I tried to test no_std by building a project but I see now I should have used an embedded target to catch these issues.
I don't understand the need to redefine 64-bit integers and floating point. Aren't those emulated on 32-bit targets..? If they were to be redefined, then we would also need 32-bit versions of funutd and all the hashing algorithms in fundsp.

You are correct in that u64 and f64 can be emulated. The main issue I encountered was that core::sync::atomicU64 does not exist on embedded. When I changed atomicU64 to atomicU32, the compiler complained about expecting u32,f32,i32 but got u64,f64,i64 etc. this propagated throughout the entire code base. So what I did was basically make sure that if the target does not support 64 bit types, use 32bit instead. I also made sure the 32-bit function was called from other crates where possible. I cut some corner in some places, where the 64-bit types are used (emulated).
my reasoning was that, if you for some reason would like to support 16-bit MCUs or to avoid emulation since it could bring a performance penalty, the only thing that would need to be done is to add another condition in the target-width module.

Okay, I see. Then as a first step I'm going to make AtomicU64 optional or remove it altogether. Also add the missing wide flag to disable default features. Then only the lack of an official new numeric-array version would prevent it from supporting 32-bit targets, right?
The next steps would be to see how much the use of 64-bit operations can be reduced, and maybe introduce some feature(s) to that end. Supporting 16-bit sounds crazy, though, I just think FunDSP may be too slow and memory hungry to work well there.

I removed 64-bit atomics and added the missing wide flag.


60 min timer resets when a new chunk loads.

Hello, I've been running around a lot and noticed, that every time a new chunk loads that I run by the timer just resets back to 60min.
It also reset when I entered a quest cutscene.

Good call, checking it out shortly. I think I know the cause.

To clarify as well, it looks like the 5 minute timer was being reset. Should be fixed in https://github.com/zmanowar/random-event-analytics/commit/f73db5c913bb2eb2fa3b744dffb795e08dfee9ad


Fold playspace transform into hand mesh.

Overview
See similar PR for XR SDK  https://github.com/microsoft/MixedRealityToolkit-Unity/pull/7708
Changes

Fixes: #9873  .

Verification

This optional section is a place where you can detail the specific type of verification
you want from reviewers. For example, if you want reviewers to checkout the PR locally
and validate the functionality of specific scenarios, provide instructions
on the specific scenarios and what you want verified.
If there are specific areas of concern or question feel free to highlight them here so
that reviewers can watch out for those issues.
As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

Closing in favor of https://github.com/microsoft/MixedRealityToolkit-Unity/pull/9875, which will make its way into main via the daily sync merges.


SqlPackage universal authentication to Azure SQL fails with error "You can't sign in here with a personal account. Use your work or school account instead"

SqlPackage or DacFx Version: <IP_ADDRESS>
.NET Framework (Windows-only) or .NET Core: 8.0.200
Environment (local platform and source/target platforms): Windows 11/Azure

Steps to Reproduce:

Publish DAC package to Azure SQL using universal authentication with command:

dotnet tool run sqlPackage /Action:Publish /SourceFile:XXX.dacpac /tsn:XXX.database.windows.net /tdn:XXX /tec:True /ua /tid:XXX.onmicrosoft.com

Observe browser window with authentication request is opened.

Input valid login<EMAIL_ADDRESS>and press "Next".

Observed behavior:
Error message "You can't sign in here with a personal account. Use your work or school account instead."

All inputs are valid and checked many times in different ways.
For instance, for sqlcmd universal authentication with the same inputs works as expected:
sqlcmd -S XXX.database.windows.net -d XXX -U<EMAIL_ADDRESS>-G -I

Did this occur in prior versions?  If not - which version(s) did it work in?
It did not work in different way: browser window with authentication request was not opened and some error was reported.
(DacFx/SqlPackage/SSMS/Azure Data Studio): SqlPackage

If you enter the command for universal auth without the tenant Id, do you still get the error message for "You can't sign in here with a personal account. Use your work or school account instead."?
dotnet tool run sqlPackage /Action:Publish /SourceFile:XXX.dacpac /tsn:XXX.database.windows.net /tdn:XXX /tec:True /ua

Sure, double-checked it again.
Of course, I have exhausted all possible workarounds before taking on the work to fill this bug report.


Cannot sort/order addColumn that is COUNT or SUM

Summary of problem or feature request

I am using Eloquent as a data source and server-side processing.
I'm essentially pulling the User model into the datatable, but there are a few additional columns.
One column is a COUNT of a relation (i.e. Users have Sales, I'm returning a count of sales):
addColumn('num_sales', function($row){
                return $row->sales()->count();
            })

Another column is a SUM of Sales's 'amount' column:
addColumn('total_amount', function($row){
                return $row->sales()->sum('amount');
            })

The datatable is rendering fine and the JSON response is like this:
      {
         "id":"1",
         "first_name":"ABC",
         "last_name":"123",
<EMAIL_ADDRESS>         "agreed_terms":0,
         "name":"ABC 123",
         "num_sales":"2",
         "total_amount":"0",
      },

All columns sort other than num_sales and total_amount. Are you able to identify why the COUNT or SUM columns will not sort?
I'm on Laravel 5.4. Please let me know if I can offer any additional information.

For count, you can use Laravel's withCount('relation'). However, you need to manually add the SQL for SUM since it's not yet supported by Laravel.

i'm using sql count and it's working well :
\DB::raw('count(distinct client_id) as nb_client')

'nb_client' => [
                'data' => 'nb_client'
            ],

For count, you can use Laravel's withCount('relation'). However, you need to manually add the SQL for SUM since it's not yet supported by Laravel.

Can you give an example of the SQL needed to sort columns that have been added? These added columns are sums of the relation. I've been stuck on this for awhile.

@realcheese it depends on your data. One quick example
$data = DB::table("click")
	    ->select(DB::raw("SUM(numberofclick) as count"))
	    ->orderBy("created_at")
	    ->groupBy(DB::raw("year(created_at)"))

If you are counting / sum from relations, you then need to do some join statements. The key here is as long as it works on the SQL level, it should work with dataTables. There are cases that it is better to use join statements than relying on eager loading. But all depends on the situation. Thanks!

@yajra The join statements definitely did the trick. I was so intent on using eager loading that I didn't use the query builder. Thanks for the help!


CardPlatform moving to certified connectors

Please check the following conditions for your PR.

[x] apiDefinition.swagger.json is validated using paconn validate command.
[x] apiProperties.json has a valid brand color. Invalid brand colors are #007ee5 and #ffffff.

@st0014 Can you please let us why you have added another connector's file in your PR. Also can you please make sure that your local repo is updated with the remote repo.

@st0014 Can you please let us why you have added another connector's file in your PR. Also can you please make sure that your local repo is updated with the remote repo.

I originally placed the files in the wrong directory - I by mistake place them in the custom-connectors directory rather than certified-connectors, so I have moved them.
Also I'm not an expert with github - how do I update my local repo with the remote repo?
Thanks


[Bug] rbpf-tests attempt to run non-test generated interface move files

After running rbpf-tests once, a second run will fail with errors like:
thread 'run_test::entry-point04-build/generated_interface_files/mv_interfaces/00959839231632418319/0x0000000000000000000000000000000000000000000000000000000000000001/bit_vector.move' panicked at 'called `Result::unwrap()` on an `Err` value: "Loading executable failed: InvalidAccountData"', language/tools/move-mv-llvm-compiler/tests/rbpf-tests.rs:320:6
test run_test::entry-point04-build/generated_interface_files/mv_interfaces/00959839231632418319/0x0000000000000000000000000000000000000000000000000000000000000001/bit_vector.move ... FAILED

This is because of an interaction between the test_harness macro and tests that compile the stdlib: compiling the standard library generates "interface files" that have a .move extension, and they are generated under subdirectories of the rbpf-tests directory.
The test_harness regex looks like:
datatest_stable::harness!(run_test, TEST_DIR, r"rbpf-tests/[a-z0-9-_/]*\.move$");

This regex allows tests to be located in subdirs, so it pickes up the generated files and fails them.

The regex allows subdirectories since commit 5fe4195b64, which adds tests that are contained in subdirectiories.
The easiest solution at the moment is probably just to create a more complicated regex that rejects paths containing something like -build/.

Why don't we have a clean-up before running so each run will be like the first run?

Why don't we have a clean-up before running so each run will be like the first run?

The primary difficulty is that the test_harness macro is responsible for both discovering tests and generating the main function, so there is no opportunity to run custom code prior to the test harness.

I'm finding that it is actually hard to write a regex that says "allow all strings except one's that contain '-build/'". This isn't something the Rust regex engine can do in an obvious way.

We can possibly have the tests that link to the stdlib clean up after themselves to delete the .move interface files, though that feels pretty ugly to me.

Maybe regex is good for now, but if the starting positions for different runs are not the same it will always remain a legit source of suspicion.

Maybe regex is good for now, but if the starting positions for different runs are not the same it will always remain a legit source of suspicion.

Good point. It looks like each individual test does clean up their build directories prior to doing their individual builds, so the tests shouldn't be building into dirty build directories; but there is no single step to clean up all build directories at once.

For CI checks this shouldn't matter, because they always run in a  new clone of the repository.

For CI checks this shouldn't matter, because they always run in a new clone of the repository.

For CI indeed, but before CI we do a local test run and it may come out misleadingly correct.


Replication should work with NAT

At the moment, replication is based on Akka Remoting which doesn't support NAT (see also this discussion).

Akka 2.4 will have some support for NAT. Not sure if we should wait or switch to Finagle anyway for replication. /cc @volkerstampa.

The plan seems to be that akka 2.4 is released in April, so I think it would be ok to check this out first before switching to Finagle. However there is also this potential problem about quarantined remote systems!?!

However there is also this potential problem about quarantined remote systems!?!

Good point. This is actually my biggest concern and a good reason to think about (and actually implement) alternatives. Anyway, I'll keep the akka-remote based replication code on a branch so we can try it later with Akka 2.4.

NAT is supported with Akka 2.4 which was tested with a modified configuration on branch wip-50-nat-support. Also, according to this post there's no system message traffic between remote actor systems by default, unless remote deployment or remote death watch is used. Eventuate doesn't use either, so quarantining shouldn't be an issue. I therefore propose to use Akka 2.4 as soon as it is released (and not Finagle).

Sounds reasonable to me.

another way maybe implement a p2p(ICE) transport like udt/quic.
but I think just akka 2.4 would be OK.


Look forward to your open source code

Thanks for your attention.
The code will be open source no later than the start time of BMVC2021 conference. I hope I can finish it in two weeks.


Does not load

Tried your theme on my site and this URL is 404ing:
/++theme++plonetheme.clean_blog/js/bundle-compiled.js?version=2015-05-28 00%3A00%3A00.000003
This other URL too:
/++theme++plonetheme.clean_blog/css/clean-blog-bundle-compiled.css?version=2015-05-28 00%3A00%3A00.000003
I fail to see what is wrong, but it certainly does not work.  Restarting the Zope server does not change anything either.  As a result of this breakage, the site appears mostly unstyled.

I couldn't reproduce it on my machine so closing it for now. Will open if someone else can do that.


Signal Kind

In ophyd there is the concept of attribute kind https://nsls-ii.github.io/ophyd/signals.html?highlight=kind#kind
This is quite useful when looking at data, separating signals into stuff that's really important and other stuff that is just useful for context. Differentiating normal and hinted signals is also useful for plotting
Is this also planned for ophyd-async, or is there another method for differentiating signals?

When designing ophyd-async, we tried to separate the interface to the underlying Devices from the logic that would use them as much as possible. I class "what to put in read() and read_configuration()" and "what to put in hints" as logic rather than interface, so didn't attach anything like kind to signals.
To answer "what to put in read() and read_configuration()", I made StandardReadable with:
https://github.com/bluesky/ophyd-async/blob/f1b4aba227ee6b568718c170ced6378a744abf99/src/ophyd_async/core/standard_readable.py#L23-L38
which is used like this:
https://github.com/bluesky/ophyd-async/blob/f1b4aba227ee6b568718c170ced6378a744abf99/src/ophyd_async/epics/demo/__init__.py#L31-L43
I didn't however provide any helpers in StandardReadable to help with hints. You can always make the hints property yourself:
class Sensor(StandardReadable):
    ...
    @property
    def hints(self):
        return {"fields": [self.value.name]}

However, it occurs to me that we could add this to StandardReadable.set_readable_signals too, although the set of uncached and hinted may overlap. Maybe we need to change the signature to:
     def set_readable_signals(
         self,
         config: Sequence[SignalR] = (),
         read: Sequence[SignalR] | Dict[SignalR, SignalReadOptions] = (),   # Sequence means use default values of SignalReadOptions
     ):

where SignalReadOptions might be:
@dataclass
class SignalReadOptions:
    cached: True
    hinted: False

# For convenience
HINTED = SignalReadOptions(hinted=True)
UNCACHED = SignalReadOptions(cached=False)
UNCACHED_HINTED = SignalReadOptions(cached=False, hinted=True)

So the example would become:
class Sensor(StandardReadable):
    def __init__(self, prefix: str, name="") -> None:
        self.value = epics_signal_r(float, prefix + "Value")
        self.mode = epics_signal_rw(EnergyMode, prefix + "Mode")
        self.set_readable_signals(
            config=[self.mode],
            read={self.value: HINTED},
        )

What do you reckon?

I like this solution you propose:
class Sensor(StandardReadable):
    def __init__(self, prefix: str, name="") -> None:
        self.value = epics_signal_r(float, prefix + "Value")
        self.mode = epics_signal_rw(EnergyMode, prefix + "Mode")
        self.set_readable_signals(
            config=[self.mode],
            read={self.value: HINTED},
        )

@danielballan @tacaswell any thoughts on this?

Completed in https://github.com/bluesky/ophyd-async/issues/223


Update ical.js #1631

Fixed Bug with more than one calendar.
simply copied over the newer updated file from vendor as discussed in the  forum. #1631

Please send your pull requests the develop branch.
Don't forget to add the change to CHANGELOG.md.

Note: Sometimes the development moves very fast. It is highly
recommended that you update your branch of develop before creating a
pull request to send us your changes. This makes everyone's lives
easier (including yours) and helps us out on the development team.
Thanks!

Does the pull request solve a related issue?
If so, can you reference the issue?
What does the pull request accomplish? Use a list if needed.
If it includes major visual changes please add screenshots.

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


[Requirement Machine] Diagnose redundant requirements.

Plumb source location info through the rewrite system by storing the structural requirements used to derive explicit rules, and store the structural requirement ID in the rule itself. Structural requirement IDs are propagated from redundant rules to their replacements via RewriteSystem::propagateRedundantRequirementIDs after homotopy reduction. RewriteSystem::getRedundantRequirements computes the set of redundant requirement diagnostics to be emitted from RequirementSignatureRequestRQM and  InferredGenericSignatureRequestRQM.
This change does not (yet) emit notes to show where a requirement is made redundant.
Resolves: rdar://88135415

@swift-ci please smoke test

@swift-ci please smoke test Linux

@swift-ci please smoke test Linux

@swift-ci please smoke test Linux

@swift-ci please smoke test Linux


Wthit Compatibility

Describe the bug
Crashes when placing any drawer.
Link to log: https://pastebin.com/mUsPA6hg
To Reproduce
Load a world and place any drawer.
Expected behavior
Place the drawer and not crash to menu.
Setup
Minecraft: 1.16.5
WTHIT: 2.10.4
Fabric Loader: 0.11.6
Fabric API: 0.35.1

Additional context
Using Hwyla allows simple drawers to work as expected without crashing.

Fixed in latest Wthit version


Better error messages

It is very tedious for me to type concise and descriptive messages while writing important features, so i have left comments by every throw statement for someone to write something better. If someone wants to take this on, feel free.

To search, search for the comment
// #1


multiple upload file

its possible tu upload multiple file at sametime llike selected 5 picture at same time and sending to telegram without forloop or etc

For upload multiple files at the same time maybe you can use the sendMediaGroup method and send up to 10 files in 1 message, in other case you still need to send one by one with a loop and a little wait for don't have too many request problems


Adds 'Direct / None' referrer when no referrer is present

resolves #1223

Though this PR enters Direct / None in the databse when no referrer is avialable. This is not reflected in the dashboard. I tried to find what is wrong, but wasn't successful.

Hello Rohan :) Interesting you went that way.
I think we shouldn't touch the database, it would grow it unnecessarily => that info is already present (pageviews with blank referrer).

I am looking at a way to do this on the frontend instead of the backend. I'll let you know of my results.

This is not an ideal solution. I would rather it all be handled by the frontend.

This has been solved on the front end. #1283

@Maxime-J @njfdev @mikecao Yeah, I would agree doing this front end would be a better choice.


Catch individual token reverts during withdrawal

A malicious user could theoretically create a token contract that throws if one calls withdraw to leave Erdstall with a holding in that token. The current implementation would then just revert, indefinitely locking all funds in the user's exit proof. No good.
I propose to surround each holder.transfer call with a try/catch so that this cannot happen.
Additionally, each failed transfer could emit a new TransferFailed event so that the dApp can be made aware of the fact that some withdrawals failed.
Open question is whether we want to let the withdraw call revert if all holder.transfer calls reverted.

After we've done this, we should revert here


[Bug/Question] non_retryable_error_types seems not working

What are you really trying to do?
I'm testing the behavior of RetryPolicy for an activity, esp the non retryable case
Describe the bug
The code I used for testing as following:
Workflow:
from datetime import timedelta

from temporalio import workflow

with workflow.unsafe.imports_passed_through():
    from salestech_be.temporal.activities import (
        say_hello,
    )
    from temporalio.common import RetryPolicy

@workflow.defn
class SayHello:
    @workflow.run
    async def run(self, name: str) -> str:

        return await workflow.execute_activity(
            say_hello, name, start_to_close_timeout=timedelta(seconds=5),
            retry_policy=RetryPolicy(
                maximum_interval=timedelta(seconds=1),
                non_retryable_error_types=["MY_CUSTOM_ERROR_TYPE"],
                maximum_attempts=2,
            )
        )

Activity
from temporalio import activity
from temporalio.exceptions import ApplicationError

@activity.defn
async def say_hello(name: str) -> str:
    raise ApplicationError(
            message="test",
            details={"reason": "test"},
            type="MY_CUSTOM_ERROR_TYPE",
            non_retryable=True,
        )
    return f"Hello, {name}!"

I also tried different combinations of params when raise the error, none of them works.
Test Script:
await client.start_workflow(
    SayHello.run,
    "test_say_hello",
    id=f"test_say_hello_{uuid4()}",
    task_queue=DEFAULT_TASK_QUEUE,
    id_reuse_policy=WorkflowIDReusePolicy.ALLOW_DUPLICATE_FAILED_ONLY,
)

Based on the docs I read, what I expected is this activity should not be retried, and there will be a Activity Task Failed record in the Event history with something like non-retryable error content.
but in fact, the activity is still being retried and fail on a start_to_close timeout eventually, can I ask some help for understanding this? is it a bug, or I misunderstood something? much appreciate!
Minimal Reproduction
see above
Environment/Versions

OS and processor: m2 macbook pro 15.1
Temporal Version:  1.25.0 and SDK version 1.8.0
Are you using Docker or Kubernetes or building Temporal from source? using Docker

Additional context

thanks, @cretz, yep I find the 'details' errors as well, but things don't change if i removed the details field. And I'm pretty sure I did register the activity and had a working running.
Are you able to reproduce this your side? it should not be two complicated to reproduce, I've confirmed with one of my team and he claims he faces the same issue.
We both use MacOs with M2 chips, not sure if this matters. just fyi.

oh sorry, i missed this line:

Changing your code to remove message= and details=, the workflow properly fails bubbling out the activity failure.

let me try again.

@cretz  After hours debugging, I can confirm this not working issue is due to conflict of our custom logger built on loguru, haven't have a clue on how to solve it, but find the cause now. thanks!

@yitian-reevo I am wondering did you solve the issue? we are having same issues and also using loguru and it's not clear at all form the first sight at least where does exactly the issue lie, so I'd really appreciate your insight 🙏

@yitian-reevo I assume an activity now cancels right away when you raise ApplicationError(type="MY_CUSTOM_ERROR_TYPE") and it does not wait start_to_close_timeout?

@barbatus that's correct, exceptions listed in non_retryable_error param will terminate the acitivity immediately.
I would suggest you setup a tempory pure Temporl env (e.g in a dokcer) to test how it behaves, then you can have a clear view on this feature.


yii select2 extension, how to display the selected value in update view?

This is not an issue, just a query which i have been trying to solve.
i am stuck at a point, please solve this mystery, I am using select2 extension fortunately it is a searchable drop down, like when i start typing, it loads the stored data from my business table. Just a query how can i show my selected business in update view, I am currently in address view, where there are four fields, sector, city, business, street. I am getting business name using select2 extension, it is working but when i update an address, every stored field's data comes up, except the business. HERE is my code of address/views/_form

beginWidget('bootstrap.widgets.BsActiveForm', array(
    'id'=>'address-form',
    // Please note: When you enable ajax validation, make sure the corresponding
    // controller action is handling ajax validation correctly.
    // There is a call to performAjaxValidation() commented in generated controller code.
    // See class documentation of CActiveForm for details on this.
    'enableAjaxValidation'=>false,
)); ?>

Fields with * are required.

<?php echo $form->errorSummary($model); ?>

    <?php echo $form->textFieldControlGroup($model,'street_number',array('size'=>45,'maxlength'=>45)); ?>
    <?php echo $form->error($model,'street_number'); ?>

    <?php echo $form->labelEx($model,'business_id'); ?>
     <?php

$this->widget('ext.select2.ESelect2',array(
'name'=>'Address[business_id]',
'data'=>CHtml::listData(Business::model()->findAll(), 'id', 'business_name'), //the whole available list
'htmlOptions'=>array(
'placeholder'=>' search business name?',
//'options'=>$options, //the selected values
//'multiple'=>'multiple',
'style'=>'width:530px',
),
));
?>

    <?php echo $form->textFieldControlGroup($model,'sector',array('size'=>45,'maxlength'=>45)); ?>
    <?php echo $form->error($model,'sector'); ?>

    <?php echo $form->textFieldControlGroup($model,'city',array('size'=>45,'maxlength'=>45)); ?>
    <?php echo $form->error($model,'city'); ?>

    <?php echo BsHtml::submitButton($model->isNewRecord ? 'Create' : 'Save'); ?>

endWidget(); ?>

This question is right but closed without giving the right answer.

@ErSKS This was closed and marked as inappropriate for the following reasons:

Readme states:

For questions on working with Backbone or general discussions: https://groups.google.com/forum/#!forum/backbonejs, http://stackoverflow.com/questions/tagged/backbone.js, or https://gitter.im/jashkenas/backbone

Contributing doc states:

Do not use tickets to ask for help with (debugging) your application. Ask on the mailing list, in the IRC channel (#documentcloud on Freenode), or if you understand your specific problem, on StackOverflow.


HARD: Math unit error checking

Proper formulation of inductive definition checking, Math unit errors: Definition type vs usage of is or =
Comment from Sami: the current math type system does not type check the right hand side of any definition. Something wasn't working quite right with it, but it might be very hard to fix it. All Definition are assuming that there is no body due to type checking issues.

@rhit-csse-projects/t17-2425
As of 27 Sept 2024, please ignore this issue
We'll come back to it at a later date


stat .//values.yaml: no such file or directory

I use https://distro.eks.amazonaws.com/users/install/kops/ guide create eks-d , but get error "stat ./cluster01.example.com/values.yaml: no such file or directory"
What happened:
✔ AWS_REGION=us-east-1
✔ AWS CLI authenticated
✔ KOPS_STATE_STORE=s3://kops-eks-d
✔ KOPS_CLUSTER_NAME=cluster01.example.com
Using kOps state store: s3://kops-eks-d
Creating ./cluster01.example.com/aws-iam-authenticator.yaml
Creating cluster01.example.com.yaml
stat ./cluster01.example.com/values.yaml: no such file or directory
kops version
Version 1.20.2

I found solution , you need execute "./create_values_yaml.sh" before ./create_configuration.sh, it's work for me


Fix possible failures

Purpose
This PR fixes few possible failures of BString migration. This is an extended PR for https://github.com/ballerina-platform/module-ballerina-socket/pull/5

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master      #6   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          19      19
  Lines         866     866
  Branches       70      70
======================================
  Misses        866     866

Impacted Files
Coverage Δ

...lang/stdlib/socket/endpoint/tcp/ClientActions.java
0.00% <0.00%> (ø)

...lang/stdlib/socket/endpoint/tcp/ServerActions.java
0.00% <0.00%> (ø)

...lang/stdlib/socket/endpoint/udp/ClientActions.java
0.00% <ø> (ø)

...alang/stdlib/socket/testutils/MockServerUtils.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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