Use python 3.10 in CI

The current CI build is failing because it uses python 3.9, which is not supported anymore. I changed the workflow settings to run with python 3.10, which should fix the issue.

I had to clean the notebooks. The main edits are in the workflow files for deployment and testing. The current build is now failing due to the issue in #18.


Discrepancy in property attachedElements of Track object of RoomEvent TrackSubscribed and TrackUnsubscribed

Describe the bug
This might be a conscious design decission (not storing any kind of state locally). But just in case I'm going to expose what I expected to find and what I found when setting the handlers for the TrackSubscribed and TrackUnsubscribed Room events.
What I'm expecting
I hoped that after calling Track.attach inside the TrackSubscribed handler, the Track object would store the information about the attached HTML elements not only in that specific variable, but also across events.
What happens instead
When handling event TrackUnsubscribed for the same Trackentity, the object passed to the event's handler has its attachedElements array empty.

As I said, this could be a simple decission not to store any state locally and leave full responsibility for state management to the application. But if livekit-client handled it internally, in many cases the code could be greatly simplified.

Reproduction
Join two different participants to the same room with this code:
var room = new LivekitClient.Room();

room.on(LivekitClient.RoomEvent.TrackSubscribed, (track) => {
	track.attach();
	console.log(`TrackSubscribed: showing attached elements of track ${track.sid} (${track.attachedElements})`);
});

room.on(LivekitClient.RoomEvent.TrackUnsubscribed, (track) => {
	console.log(`TrackUnsubscribed: showing attached elements of track ${track.sid} (${track.attachedElements})`);
});

await room.connect(livekitUrl, accessToken);
room.localParticipant.setMicrophoneEnabled(true);
room.localParticipant.setCameraEnabled(true)

This will log the following on the browser's console:

Logs
No response
System Info
- livekit-client package (1.10.0) being used in a plain JS application
- Google Chrome Version 114.0.5735.133 (Official Build) (64-bit)

Severity
annoyance
Additional Information
No response

It does retain attachedElements across events. However, what you are seeing here is the SDK automatically detaching from all attached elements upon unsubscribe.
When the track is unsubscribed, the attachment is removed automatically.


No results showing up

I followed the instructions in README.MD and the installation went fine. The app also serves fine, but when I try to run a check on a site, nothing seems to happen. What's the expected result of clicking that button? (I tried all settings in the Crawl dropdown.)
I do get this warning when running ng serve, but I don't think that's the problem:

Your global Angular CLI version (1.7.4) is greater than your local
version (1.2.1). The local Angular CLI version is used.

Update: I figured out I had to run the Node.js server seperately on port 3000. Works fine now!


Authentication

Is your feature request related to a problem? Please describe.
Somewhat yes. Consider the following REST resource:
GET, POST: /articles
In this case, you need to be authenticated to post an article. However to get all the articles, you can and don't have to be authenticated. If you are not, you will receive only the public articles. If you authenticate, you will also receive those, that you have permission to view.
Using Kotlinx RPC, I would imagine that you would create an ArticleService, that would have the getAll and post methods. However how do you handle the authentication? What I have understood is that when you use the Ktor server implementation, you can protect the entire route, however, that has many downsides:

The above scenario is not possible.
You cannot have more services under one route, where some need auth and some don't (this maybe is not that of a downside)
You cannot get the authentication details inside the RPC method. (or I am not aware how?)
If the authentication is done using the RPC itself, then it is done in the middle of the WebSocket connection, so you would have to remake the initial websocket request, which doesn't make sense. The primary use-case of RPC seems to be Web SPA, where single connection is iconic.

Describe the solution you'd like
I am not entirely sure how this library is implemented, so keep that in mind please.
Add a feature, similiar to http headers. Each call, would apart from what service is being called and what are the arguments also be able to carry additional data, that could contain the authentication information.
This would also be a helpful addition overall, that you could pass additional context/state data. I am not entirely sure, whether the authentication should be part of this additional data feature, or it should be handled seperately. Handling it seperately might have an adventage, where some transport implementation can have specific custom ways of handling authentication.
Describe alternatives you've considered
I have already described above.
Additional context
I have read all the issues related to authentication, however to my understanding the provided solutions do not solve above problems.

Could this be fixed with: https://github.com/Kotlin/kotlinx-rpc/issues/150 ?
I am not a contributor, this is just my opnion

It depends on the posibilities of the plugins. But yes, if the plugins would be able to modify the actual request, then it should be possible to make an Authentication plugin. And actually I think making it an extension plugin is a great idea, similiar to Ktor's.

Hi, @tomhula! Thank you for the feature request. We are thinking about protocol enhancements, and we'll take this into consideration during the design. Either it would be done by plugins, or by a separate feature - I don't know yet


Extremely high/negative gas resistance readings

I've been getting some pretty whacky gas resistance readings from one of the BME680 sensors using this library. The values I've logged have spiked as high as 285204105.924075 and as low as -24795831.931635 which is pretty far outside the expected range as I understand it.
Here are a bunch of graphs at increasing levels of detail to illustrate the trends:

Another sensor elsewhere in the house running the exact same code is returning more sensible values:

For reference this is the code I'm running: https://github.com/davea/rpi-mqtt-sensors/blob/master/main.py

That's weird. I'm assuming that it's not a bug in the software library though.
Have you double checked your wiring/soldering? Might be a defective sensor as well.

This is possibly related: https://forums.pimoroni.com/t/bme680-breakout-negative-ohms-on-gas-sensor/6500
I would expect the negative readings are a result of an overflow.
Looking at the datasheet, the gas calculation is defined as:
var1 = (1340.0 + 5.0 * range_switching_error) * const_array1[gas_range];
gas_res = var1 * const_array2[gas_range] / (gas_r - 512.0 + var1);

With const_array1 and const_array2 being the following tables:

In the code, these are defined as the following, which is the result of shifting up the decimal numbers by enough to be kinda precise (shifted up 31? places for array1 and 9 for array2):
https://github.com/pimoroni/bme680/blob/288daed781604c5581b117b4c91ca567404f9fa8/library/bme680/constants.py#L215-L224
At this point the calculation becomes difficult to follow, but presumably it's correcting the 31 place shift up on const_array1
https://github.com/BoschSensortec/BME680_driver/blob/494b3bb26b026dcc26059e512bb71b60eb364376/bme680.c#L923-L937
Notably it seems to perform all operations as int64_t, before casting the result to uint32_t. Which may be where our bug is introduced. Take the linked forum post results by way of example and cast each number to a uint32_t:
Casting to uint32_t:
131858.0 => 131858
129573.0 => 129573
129573.0 => 129573
128828.0 => 128828
127546.0 => 127546
127365.0 => 127365
124883.0 => 124883
122999.0 => 122999
123848.0 => 123848
122328.0 => 122328
123678.0 => 123678
120359.0 => 120359
120037.0 => 120037
119398.0 => 119398
120198.0 => 120198
118923.0 => 118923
118766.0 => 118766
118766.0 => 118766
118296.0 => 118296
110979.0 => 110979
-1425780.0 =><PHONE_NUMBER>
1382577.0 => 1382577
556403.0 => 556403
414773.0 => 414773
348282.0 => 348282
314655.0 => 314655
292468.0 => 292468
298203.0 => 298203
323582.0 => 323582
353682.0 => 353682
377066.0 => 377066
418578.0 => 418578
495924.0 => 495924
495924.0 => 495924
592533.0 => 592533
608334.0 => 608334
724207.0 => 724207
800439.0 => 800439
950521.0 => 950521
1061047.0 => 1061047
1200659.0 => 1200659
1267362.0 => 1267362
1382577.0 => 1382577
1629466.0 => 1629466
3258935.0 => 3258935
3509623.0 => 3509623
3509623.0 => 3509623
4147738.0 => 4147738
11406336.0 => 11406336
-11406162.0 =><PHONE_NUMBER>
-7604127.0 =><PHONE_NUMBER>
-3802073.0 =><PHONE_NUMBER>
-2683818.0 =><PHONE_NUMBER>
-2172616.0 =><PHONE_NUMBER>
-1520832.0 =><PHONE_NUMBER>
-1267360.0 =><PHONE_NUMBER>
-1036931.0 =><PHONE_NUMBER>
-1112804.0 =><PHONE_NUMBER>
-1061046.0 =><PHONE_NUMBER>
-950520.0 =><PHONE_NUMBER>
-877403.0 =><PHONE_NUMBER>
-829545.0 =><PHONE_NUMBER>
-786637.0 =><PHONE_NUMBER>
-747950.0 =><PHONE_NUMBER>
-661232.0 =><PHONE_NUMBER>
-712890.0 =><PHONE_NUMBER>
-773305.0 =><PHONE_NUMBER>
-651785.0 =><PHONE_NUMBER>
-600329.0 =><PHONE_NUMBER>
-592532.0 =><PHONE_NUMBER>
110432.0 => 110432
110841.0 => 110841
111948.0 => 111948
114814.0 => 114814
114520.0 => 114520
115404.0 => 115404
114961.0 => 114961

Ah... well that's one problem solved, perhaps, but this doesn't explain the high spikes!?

Hi! I have just got a BME680 and have seen these spikes. I think the problem is in line 328 of bme680/constants.py.
It is now:
self.range_sw_err = (sw_error * RSERROR_MSK) // 16
and should be:
self.range_sw_err = (sw_error & RSERROR_MSK) // 16
At least my results of calc_gas_res are much more consistent now!!

@lowflyerUK ... is there a GitHub facepalm emote?
🤦♂
Yup!
Thank you!

Aha! Thanks for tracking this down 👍 I've updated to 1.0.4 on both my devices and will see how it goes.


Updating documentation for new datetime format

Description
This PR updates documentation for new datetime format rfc_3339_lenient
Issues Resolved
Closes https://github.com/opensearch-project/documentation-website/issues/6308
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks, @CaptainDredge ! Did you mean to link this to issue https://github.com/opensearch-project/documentation-website/issues/6308? Is the content ready for doc review?

Thanks, @CaptainDredge ! Did you mean to link this to issue https://github.com/opensearch-project/documentation-website/issues/6308? Is the content ready for doc review?

Thanks @hdhalter I've linked to the right issue. The content is ready for review but I'm not able to figure out what exact formatting is required for CI to go green. Is there any automated linter for the docs?

Moving to done, we should update Vale rules so that an emdash isn't always required.

Endash is required in text but this is literal strings so they should be in code format. Let me make some suggestions.


Graceful sidecar support

Changes
TL;DR Tekton Pipelines now gracefully start and stop with injected sidecars running alongside TaskRun pods.
Long Version :-
TaskRun pods can have sidecars injected by Admission Controllers. This is common practice with Istio where a proxy sidecar is injected into pods so that they can be included as part of a service mesh. Unfortunately there is no built-in Kubernetes mechanism to set the lifetime of a sidecar container to match that of the pod's "primary" container. In practice this means that pods injected with sidecars will not stop until both the primary and all sidecar containers are stopped.
Prior to this commit any non-istio injected sidecars would cause a TaskRun pod to run forever, even when all Step containers of a Task had completed.  Istio injection was also disabled completely on TR pods. This commit introduces mechanisms to start and stop sidecars gracefully meaning that a) Step containers wait until all sidecars are in a ready state before starting and b) Sidecar containers are stopped when a TaskRun's Step containers are done.  Additionally, the annotation that prevented Istio sidecar injection has been removed.  Istio now adds sidecars to TaskRun pods as expected.
No end-to-end tests have been added as part of this PR because doing so would require Istio to be enabled on the CI cluster (or a dummy Admission Controller / Mutating Webhook thing to be written just for injecting containers into test Pods). The Istio requirement would put an undue burden on those users running tests in non-GKE environments. It's currently planned for a follow-up PR to introduce a) user-defined sidecars and b) a Tekton-injected sidecar that performs logging. Once that work is complete it will be much simpler to e2e test this sidecar code.
For reference, see the POC PR that was originally created here: https://github.com/tektoncd/pipeline/pull/728
For the design proposal and associated discussion around the original POC please see https://github.com/tektoncd/pipeline/issues/727
For the remaining work, test coverage, code organization, etc, see https://github.com/tektoncd/pipeline/issues/926
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

Release Notes
Sidecar containers injected by, for example, Istio, will now gracefully start up and shutdown in tandem with a Task Steps' containers.

/ok-to-test

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

Hm, from the integration tests:
I0531 14:26:40.473] 2019/05/31 14:26:40 main.go:761: --gcp-project is missing, trying to fetch a project from boskos.
I0531 14:26:40.474] (for local runs please set --gcp-project to your dev project)
I0531 14:26:40.474] 2019/05/31 14:26:40 main.go:773: provider gke, will acquire project type gke-project from boskos
I0531 14:26:40.484] 2019/05/31 14:26:40 main.go:312: Something went wrong: failed to prepare test environment: --provider=gke boskos failed to acquire project: resource not found

This looks suspiciously like a configuration or platform issue.

/test all

/retest

Yeah I'm in favor of that if you can make it work, but defer to @bobcatfish and also @vdemeester in case they have concerns given our existing test infra.  How would this work if someone is trying to run e2e tests locally or on a non-GKE Kubernetes provider?

Istio/sdecar related  tests could be skipped if there is no Istio namespace.

Having to install istio just for the e2e tests seems a bit much (and heavy) I feel. Discussed a bit with @bobcatfish and @sbwsg and we fell we can defer the e2e a bit (until we work on logging sidecar and thus using this as e2e tests for sidecars).

/retest

Hey @dicarlo2 I think we're pretty close to having your sidecar PR mergeable here. If you've got some time would you mind reviewing our updates to your work and verifying that the documentation and code comments we've added are accurate and gel with your intentions?  Cheers!

/retest

LGTM, sorry for the delayed response!

Thanks @dicarlo2 !  I've modified the cla label on this PR to indicate that everything is good.

/meow space

would you mind adding an issue to the backlog about adding support to TaskRuns to add sidecars directly?

I've added an issue to capture the user-specified sidecars feature: https://github.com/tektoncd/pipeline/issues/980

@bobcatfish @vdemeester thanks for taking a look so far.  It's a big PR so I appreciate the :eyes:! I believe I've tackled all the remaining issues that were left outstanding from yesterday's and today's reviews. Please take a look when you can.  Cheers!

/hold
Once reviews are done I want to squash before merging.

/retest

/hold cancel
I've squashed all the commits together.

Thanks for squashing the commits @sbwsg !!
Interestingly https://github.com/tektoncd/pipeline/pull/963 adds a status pkg but in a different location than this PR 🤔  I think we might want to combine them together but for now I'm happy to merge this :D
Thanks for the awesome work @sbwsg @joseblas @dicarlo2 !!

/lgtm

@sbwsg arf, needs a rebase :pray:

@bobcatfish @vdemeester I've rebased on master and moved my taskrun/status changes into the status pkg so we only have one.

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

ಠ_ಠ
main.go:312: Something went wrong: failed to prepare test environment: --provider=gke boskos failed to acquire project: resource not found

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

:raised_hands:

awesome work!


[CARBONDATA-2381] Improve compaction performance by filling batch result in columnar format and performing IO at blocklet level

Problem: Compaction performance is slow as compared to data load
Analysis:

During compaction result filling is done in row format. Due to this as the number of columns increases the dimension and measure data filling time increases. This happens because in row filling we are not able to take advantage of OS cacheable buffers as we continuously read data for next column.
As compaction uses a page level reader flow wherein both IO and uncompression is done at page level, the IO and uncompression time increases in this model.

Solution:

Implement a columnar format filling data structure for compaction process for filling dimension and measure data.
Perform IO at blocklet level and uncompression at page level.

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4145/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4150/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5329/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4176/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4491/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5348/

I think we need these changes in case of DictionaryBasedResultCollector also, as when number of column is more than 100 it goes to dictionarybasedresult collector, it will improve the query performance when number of projection columns is more than 100

@kumarvishal09 ...I agree with you that we need these changes in DictionaryBasedResultCollector also to improve the query performance when number of columns are greater than 100.
As this PR is specifically for compaction performance fix, I will raise a separate PR for this. I have raised a sub jira task under same jira to track the issue.
https://issues.apache.org/jira/browse/CARBONDATA-2405

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4252/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4558/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4265/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5432/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4289/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5454/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5464/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4575/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4301/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4310/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5477/

retest sdv please

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4625/

LGTM


Adding SPARQL Update

Relates to https://github.com/CLARIAH/grlc/issues/377 and https://github.com/CLARIAH/grlc/pull/384#issuecomment-1378638201

Hey @GenEars I think this PR, similar to #390, we might need to create a new branch with only the relevant changes. I am leaving this as a draft PR until a new branch has been created. Does that sound ok to you?

Hello @c-martinez. Yes, a new branch of the "dev_sparql_update" kind seems to make the merge easier.

Great, I will do that :-)

@GenEars -- am I right to think that the main change is in swagger.py lines 318-320?

Hello @c-martinez, yes lines 318-320 are key for the Swagger, but we also have to consider handling the query method (i.e. GET vs POST) in lines 97-102 (utils.py) and lines 215-219 (utils.py) as #+ method: POST is involved in graph update queries.

Right, yes that should also be taken into account. Is there a restriction that updates should always be sent via POST method?
Also,  do you have by any chance a query we could use for testing in the test repo?

Hi @GenEars! I've created #400, which (I think) incorporates the relevant changes of this PR.
I will close this PR, and if you could have a look at #400 and let me know if you think it is ok, that would be fantastic!


[Feature Request] Toggle to allow downed tokens to retain vision

My players get downed occasionally, but while unconscious they can't see anything at all. While this makes sense from a realism perspective, it would be nice to have a toggle in the options to make it so that players can still see the game when unconscious.

You could make the same argument about the blinded condition that it shouldn't take away vision: a player's token might be blinded all combat long and doesn't get to enjoy it. Or every combat might be taking place in complete darkness and a player without darkvision wouldn't be able to see anything either regardless of conditions.
I thought about this and I think the solution is Observer permission. If you give your players Observer permission of each other a blinded/unconscious/dead/... player can still enjoy the combat from the perceptive of their party members. Though I can see that having Observer permission can also enable metagaming as each players access to more information than they should. I was thinking perhaps we need something like temporary Observer permissions so that the GM can temporarily make a player a spectator while their unconscious or otherwise lost all their senses and it's unlikely that they'll regain them next round. But I'm not sure yet how exactly this would be implemented to make this easily manageable by the GM. Also not sure if with would be part of Vision 5e or a separate module.

Is it possible to just have options for all 3 of those? (lighter darkvision, blinded, unconscious). Personally only the blinded/unconscious bother my players but I can understand all three.

If you'd like, dev, I could open up a PR just adding a settings toggle for unconscious affecting _canDetect and auto-enabling blinded. And perhaps also a toggle for blinded actually blinding the player.

I made a change in 2.1.0 that might work well to solve this issue:

Now, while a player does have any owned nonhidden tokens with vision that are defeated (dead), petrified, or unconscious in the current scene, tokens with vision owned by other players become a source of vision for this player if they have limited permission over the token's actor. This behavior aims to prevent players from missing out on all the fun if their character dies, is knocked unconscious, or is petrified, which are all conditions that make the token not perceive anything and are likely to affect the character more than one round of combat.

Let me know if you have any thoughts on this behavior.

Sounds perfect to me - I'll get rid of my PR

Does this work in DND 3.1?
On Sun, May 26, 2024, 2:26 PM dev7355608 @.***> wrote:

I made a change in 2.1.0 that might work well to solve this issue:
Now, while a player does have any owned nonhidden tokens with vision that
are defeated (dead), petrified, or unconscious in the current
scene, tokens with vision owned by other players become a source of vision
for this player if they have limited permission over the token's actor.
This behavior aims to prevent players from missing out on all the fun if
their character dies, is knocked unconscious, or is petrified, which are
all conditions that make the token not perceive anything and are likely to
affect the character more than one round of combat.
Let me know if you have any thoughts on this behavior.
—
Reply to this email directly, view it on GitHub
https://github.com/dev7355608/vision-5e/issues/80#issuecomment-2132317755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQYWEX2Y23CVPYDLP6PZFDZEISN5AVCNFSM6AAAAABIFZXZLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGMYTONZVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Vision 5e 2.0.0+ is V12 only (and therefore dnd5e 3.2.0+).

Closing as completed.


Create PrivateEncryptedChannel.php

This is just another requirement for the use of Pusher's private encrypted channels.

Please include this change in your other PR.


ModuleRegistryKt is defined multiple times in Multi-Module project

recently, I decided to migrate from v1 to v2, but whenever I try to build an application module always get this error:
 Type _generated._ramcosta._composedestinations._moduleregistry.LiveLiterals$_ModuleRegistryKt is defined multiple times: .../build/.transforms/63279b7aaff76c785cd8429898cf01da/transformed/debug/debug_dex/_generated/_ramcosta/_composedestinations/_moduleregistry/LiveLiterals$_ModuleRegistryKt.dex, .../build/.transforms/aaa2c3593294b38efdcc69153b86f08f/transformed/debug/debug_dex/_generated/_ramcosta/_composedestinations/_moduleregistry/LiveLiterals$_ModuleRegistryKt.dex
and this is a Gradle configuration for both affected library module
{
   namespace = "id.kesia.feature.home"

    ksp {
        arg("compose-destinations.codeGenPackageName","id.feature.home")

    }
 }

 {
 namespace = "id.kesia.feature.profile"
    ksp {
        arg("compose-destinations.codeGenPackageName","id.feature.profile")

    }
   }

Can you help me about what caused this issue?
I use
Version v2.0.0-alpha02
Android studio Iguana
Compose 1.6.3

Hi @nazarabd3005 ! 👋
Thank you so much for both taking the time to try v2 and to leave very important feedback 🙏
I understand the issue, I am just wondering why this doesn't happen in the projects I tried it in. I guess it may be due to dex related configurations or maybe I have to make a release build to have this happen 🤔
In any case, I will make it so these files are generated with different names!
I'll let you know when I release a new version with the fix!
Btw, how did migration go? Was it easy? Was the migration guide helpful? Thank you again!

Hi @raamcosta
You're welcome! I appreciate your thoroughness in troubleshooting.
Regarding the migration, it went smoothly overall. The migration guide was indeed helpful in navigating the process. Thanks for checking in!

Glad to hear.
New version is building, should be up in like 30min or so.
Version: 2.0.0-alpha03

Artifacts are up! Please let me know if this is fixed :)

Hi @raamcosta
already downloaded the update and it fixed the issue 👍 ,
Thanks for the update


Can the slack notification show git tag, commit author, and commit message?

Hey @IgorGov ,
Here is what you can do:

Add the following step to get all the information related to your Github context

steps:
  - run: echo "${{ toJson(github) }}"

Then you can use reference the github object properties:

github.event.head_commit.author.name
github.event.head_commit.message

as
steps:
  - uses: ravsamhq/notify-slack-action@v1
    if: always()
    with:
      ...
      message_format: '{emoji} ${{ github.event.head_commit.author.name }} ${{ github.event.head_commit.message }}'
    env:
      SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

Let me know if this helps you.

I am closing this issue for now. But feel free to reopen if this is not solved yet.

Thanks @ravgeetdhillon, your answer was very helpful!
Do you think it is worth adding to the README?

[ ] Add to README


Please close all issues due to audio overlap escalation.

This is a bit too much, just please address it.

Yup.
And the temp fix guide I posted is pushed back like 3 pages b/c people are just blindly submitting the same reports over and over instead of commenting/participating in the posts that are already up.
Imagine pushing a temporary solution back to a place where others can no longer find it.
Good intentions with negative consequences.
Link to temporary solution:
❗Temp Fix To Current v5.4/v5.5 problem❗ - Downgrade to v5.3 [Text and video instructions]
Doing this makes YouTube useable until 5.6 comes out and (hopefully) fixes everything.
Some people are saying "Downgrade to 3.8, instead!"
I've been downgraded to 5.3 since 5.4 was released and it has worked flawlessly for me.
Win10 using the current version of Chrome.
Problems some people have mentioned:

"Didn't work for me":
Did you verify the script is downgraded to 5.3?
Did it get updated back to 5.4 or 5.5? Clicking the update button or having auto-update turned on?
"Double audio is still playing.":
You're definitely still on 5.4 or 5.5 b/c that's when that specific bug started happening. Downgrade to 5.3.
"Short ads are playing at the beginning":
Some people have reported this. I, too, have had this happen with other versions of RAT. It's not specific to this version. I don't think they know what causes this b/c it's been around for a while now.
On a good note, it does stop happening.
Refreshing the page helps (I haven't had this bug happen to me for months).

made an account just to say that GroggyOtter's comment has worked for about 24hrs for me :)

Sneezing out a jellyfish.


Contact / explore further opportunities to collaborate

https://covidsafe.cs.washington.edu.  NOW --> https://commoncircle.us
Email<EMAIL_ADDRESS>as well as
MIT

Who's working on automated detection of contact tracing apps?

Follow up with:

Duke
Oxford
MIT (to make data our data more robust)


community: Bug Fix, in Neo4j VectorStore when having multiple indexes the sort is not working and the store that returned is random

Bug fix: when having multiple indexes the sort is not working and the store that returned is random.
The following small fix resolves the issue.

cc @tomasonjo

@ehude looks ok. Can you please add a test

@tomasonjo thanks for the info.
I've added the relevant test, let me know if that is ok.

You need to create two indexes, but then use from_existing_index and check if it picked the correct one :)

make more sense indeed :)
fixed and pushed.

Awesome, thank you!

Glad I could help :)
BTW, any idea when is the next release or where I can update on upcoming released?

@ehude can you check the lint error, so that we can get this in? Thanks

@tomasonjo Sure, will fix it tomorrow

@tomasonjo
Pushed a fix and tested locally with make lint_package.
Please let me know if need to run anything else to check.

1 file would be reformatted, 599 files already formatted

seems like formatting is missing. If you run make format, it should be fixed.

done

Thanks @ehude . @baskaryan LGTM!

Can you move it from unit tests to integration tests, and then it should pass all checks :)

Thanks
Done :)


MODEXPS-1::Create mod-data-export-spring and mod-data-export-worker m…

…odules basing on the PoC
Clean up REST API.

Purpose

Approach

TODOS and Open Questions

Learning

Pre-Merge Checklist:
Before merging this PR, please go through the following list and take appropriate actions.

Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] Were any API paths or methods changed, added or removed?
[ ] Were there any schema changes?
[ ] Did any of the interface versions change?
[ ] Were permissions changed, added, or removed?
[ ] Are there new interface dependencies?
[ ] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

INFO: api-schema-lint: Using api-schema-lint version: 1.0.2
INFO: api-schema-lint: Assessing schema files (https://dev.folio.org/guides/describe-schema/)
INFO: api-schema-lint: Found 8 JSON schema files under directory 'src/main/resources/swagger.api'
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/common/error.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/common/metadata.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/common/parameter.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/common/parameters.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/exportConfig.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/exportConfigCollection.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/job.json: Missing top-level "description".
ERROR: api-schema-lint: src/main/resources/swagger.api/schemas/jobCollection.json: Missing top-level "description".
ERROR: api-schema-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiSchemaLintReport.


Registry controller: Parallel execution of actions leads to lost updates

This issue was recently discovered in the way the controller executes actions.
An example of the dependency relationship between resources is as follows:
- pattern: apis/-/versions/-/specs/-/artifacts/conformance-receipt
   receipt: true
   dependencies:
     - pattern: $resource.spec
     - pattern: artifacts/apihub-styleguide
   action: registry compute conformance $resource.spec
- pattern: apis/-/versions/-/specs/-/artifacts/score-receipt
   dependencies:
      - pattern: $resource.spec
      - pattern: artifacts/conformance-apihub-styleguide
   action: registry compute score $resource.spec

In the above definition, the controller reads these dependencies, fetches all the resources in the form of a snapshot of the state of the registry.
Consider the case where:

the conformance-report was computed for the first time in the last run.
there has been a spec update since the last run.

In the current run:

The controller will notice that there is a spec update and hence it will generate the action for compute conformance report.
Since the score artifact doesn't exist yet, it will also generate an action to compute the score.
Now, both the above actions will be submitted to a task queue to be run in parallel.
Depending on when the task queue delegates this action to the workers for execution, there is a scenario where:

the score command fetches the artifact to be processed for score computation. After this fetch happens, the conformance command gets executed in parallel and updates the conformance report.
Then the score gets computed using the old copy and uploaded to the registry.
The next time the controller runs and compares the timestamps of the conformance report and the score, it will see that the score was generated after the conformance report and hence the controller will conclude that the score is already up-to-date.

In this whole scenario we lost an update to the conformance report and the score will remain outdated unless there is one more update to the conformance report in the future.

Solution:

Modify the timestamp condition used by the controller to determine if an update is needed or not.
The current condition simply checks if the resource was generated after it's dependencies. This condition can be modified to include a threshold:

resources should be at least N seconds newer than their dependencies, where N is the maximum time to compute the resource.

There are few options to what N should be in the updated condition:
resources should be at least N seconds newer than their dependencies, where N is the maximum time to compute the resource.

If we want to implement the most ideal solution, N will be the max time taken by the corresponding action which is generating the resource. Example, for score artifacts, N will be the max time taken to execute a score command. For this we will have to keep track of the execution time of the score command. The way the controller logic works is in two steps:

first it determines what actions it needs to take
then execute them
Since the information of max_execution_time is needed in step1 and it can be derived only in step2, it is not possible to keep track of max_execution_time locally. This means we will have to store this information somewhere in the registry. One optimization can be to store the max_execution_time across all the actions that the controller is executing and store only one common threshold. One issue to think about is how to handle very large max_execution_time thresholds which includes deadline_exceeded retries.

While option 1 is a possible solution, the idea of storing an artifact in the registry for the controller's internal details feels a little uncomfortable. Another option is to explore if we can set a pre-decided value as a common threshold in the controller.

For this, I did some analysis on how this particular case reproduces.

This issue mainly happens when the controller generates very few actions for transitive dependencies, like generating update actions for conformance, score and scorecard for only one spec. Here since there are very few actions, the controller executes them very close to each other and hence the lost updates.
This problem will not happen with multiple or bulk specs because the controller will first submit all the actions for conformance in the queue, then the score and then the scorecards. Since the workers pick up the actions from the top of the queue, there is very little probability of overlap.

This tells us that we need a fix for the case where the number of actions in the controller are very less, which implies that the registry is not busy and hence the execution of actions in the controller should be quick and not delayed due to timeouts. Hence, we do't need a solution which works for all the cases but which solves overlap of this short execution time. This tells me that it should be possible to come up with a reasonable threshold to be preset in the controller's timestamp condition.
From my experiments so far, a threshold of 2 seconds works for such scenarios. I was able to reproduce this issue with only a single spec update and fixed it by setting a threshold of 2 seconds in the controller's timestamp condition. Thus, the updated condition can be stated as follows:

resources should be at least N seconds newer than their dependencies, where N is 2 secconds.


Separated BigDecimal math from output

This at least partly addresses the issue in #13. Ironically, it produces the exact same output as #13, so you can look there to see what changes this brings.

On further study, your work cleans up a small mess I left.  However, after I merge, I am going to temporarily use the BD invocation at line 227 because it does make a difference in some outputs at the 15th or 16th decimal place (when I diff the whole output folder) ... this wa the first pass at using BigDecimal to try to get at the rounding errors before the subsequent full-blown BD study was done, so I need to tread carefully.  Ultimately, this level of precision is not important, but it is in the short run for showing we can reproduce results.  Anyway, good job cleaning up.


Docker support

WIP! Still figuring out how to implement this :)
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

Almost ready to merge this, however the 'docker' module seems to have a problem depending on the Ansible version...


disallow-host-path: simplify CEL expressions

See https://github.com/kyverno/policies/issues/1058

picking up this one

/assign @epasham

Policy is updated and tested. Ready to submit pull request

PR submitted-> https://github.com/kyverno/policies/pull/1129


Cleanup no_std

Depends: #37

Needs to be rebased.

@jakelang do we still need this PR? Can you explain what each of the new lines do? (cfg_attr, lang_items).

I don't think we need it necessarily, this is probably outdated since you guys have worked in the same direction on this further than I have.

On lang_items: https://doc.rust-lang.org/unstable-book/language-features/lang-items.html


Excellent idea

Giving Project a task Pane is a great idea
Didier
Project and Power BI certified consultant
+33682465535

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a52c1541-5247-c530-c627-2789f5792719
Version Independent ID: 5bab04a0-b84e-0f0c-01e1-5d8bb69029ef
Content: Build your first Project task pane add-in - Office Add-ins
Content Source: docs/quickstarts/project-quickstart.md
Product: project
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Thanks @Didierma92! We're glad you like the feature.
Just so you know, Project uses the Common API model and has fewer APIs than Excel or Outlook. If you need more functionality for your add-in, please request new features on UserVoice. There, you can create and upvote feature requests for Office Add-ins.

Thanks @Didierma92! We're glad you like the feature.
Just so you know, Project uses the Common API model and has fewer APIs than Excel or Outlook. If you need more functionality for your add-in, please request new features on UserVoice. There, you can create and upvote feature requests for Office Add-ins.


Force PHPUnit to run via Composer

Hello,
Thanks for an awesome plugin.
Is it possible to add setting to force PHPUnit to run via composer?

How do you mean force?
Currently composer support is enabled by default. If a Composer installed PHPUnit is found it is used, otherwise a fallback is used. The fallback is to just run the command phpunit which assumes PHPUnit is on your system path, if it's not on your system path then it fails normally.
By force, do you mean not to use any fallback and just fail straight away if no Composer installed PHPUnit is found?

Thanks for your reply.
I was having problems getting it work on my Windows 10 system as I had PHPUnit installed globally with composer. So I was setting composer to true but it was trying to run vendor/bin/phpunit and I wanted to force the global composer. But playing around with it a little I finally figured out that composer setting = local composer package so it's working like a charm now ☺


Bug: Fix UI Alignments for Project Cards

What happened?
The GitHub Link button and More button shifts upwards when the description is of single line. This creates a bad UI impression.
The above can be fixed by fixing the position of both Buttons with respect to the project card.
Below image shows the misalignment of Buttons in one of the cards
Add screenshots

What browsers are you seeing the problem on?
Firefox, Chrome, Safari
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

yeah, we need to fix this problem. assigned to you

Completed. Thanks for your contributions 🎉 ❤


Weird English string while test results not available

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is not already reported in another issue

Describe the bug
The "Result not" is probably a string wrapping and cutting off.

Expected behaviour
A coherent phrase in place of "Result Not"
Steps to reproduce the issue

Open app
Click the "Add test" (Cannot recall what the option to insert data was called in English)
See screen above

Technical details

iOS Version: 14.0.1
Device: iPhone 11

Possible Fix
Change language string to something short and concise? Maybe "Not available"? Maybe increase the size on the text element to allow for more space?
Additional context

Thanks for reporting.
This has been fixed already in the latest version of the code and will be solved in the next release.


Gradio Web Demo

easy to use web demo for SimCSE on gradio hub

Hi AK, thanks for the pull request. The demo looks great!


Update ammonite-compiler, ammonite-repl, ... to 2.3.8-54-a1dec1cf

Updates

com.lihaoyi:ammonite-compiler
com.lihaoyi:ammonite-repl
com.lihaoyi:ammonite-repl-api

from 2.3.8-36-1cce53f3 to 2.3.8-54-a1dec1cf.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi" } ]

labels: library-update, semver-pre-release

Superseded by #777.


Add 'Locaweb and Moip' into README 'Apps/Websites'.

I'm adding 2 great brazilian websites that are using vuejs in their products.

Could you show me where they using it?

I could not detect it there, like in #987


Move pipeline.expandAnchor into common assemble package [phab:D645]

Created by schroederc at 2015-12-11 21:26:42:

zarko accepted this revision at 2015-12-11 21:28:20

schroederc closed via commit 054c2e7f5815415e8ebd05d1ea070a93f61485da at 2015-12-11 21:29:19


Annotate entry points inside HLSL source code

Hello !
Currently to compile a shader one needs to specify both the entry point and the shader stage to the compiler:

if myshader.hlsl contains several entry points (typical use case: one fore VS, one for PS), then the file must be compiled several times. The redundant work is not a lot for tiny shaders but for big, auto-generated shaders this overhead can become non-negligible
more importantly, this means that a shader source file is not sufficient in itself, to be compiled we also need to store somewhere a list of (entry_point, shader_stage), requiring the shader author to manually fill it. Not having such a structure means creating a coupling between shader creation and shader compilation.

I think it is better to directly specify the entry points inside the HLSL source. The best solution I see is to add an attribute to the entry points like that: [entry("<stage>")] (or any variation deemed more pleasant obviously).
// some HLSL code...
[entry("vertex")]
float4 simple_projection(float4 pos : SV_Position) : SV_Position
{
    // ...
}
// more code...
[entry("pixel")]
float4 nice_color(float4 pos : SV_Position): SV_Target
{
    // ...
}

The compiler API would be something like Compile(filename, shader_model, options) returning an array of (bytecode, entry_name, shader_stage). This can be done in a backward-compatible fashion. The results for a source with N entry points is N bytecode objects, as if the compiler was called N times.
I really want this and I can try to implement it if you want.

We won't be doing this in DXC, but this scenario is worth considering for Clang, so transferring to hlsl-specs to track future features for shader compilation.


Backend code

Great project!! Where can I find your backend code?

Thank you:)
You can access it in server folder.


Update BASE_VERSION to 1.13-2022-09-22T19-02-51

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.13
63e71f111d9d4bcd7ee8004d0dc890d426f4c80d
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Select multiple lines with ALT+CLICK+Scroll?

Awesome ALT+CLICK to create multiple cursors, but how to select multiple lines quickly?
Like IDEA i can select multiple lines by hold ALT+CLICK and Scroll.
Scroll when hold ALT+CLICK is NOT select contents, it's just create cursors step by step.
Case below, batch replace the char 'g' to y
var (
	keg1 = 0x0001
	keg2 = 0x0002
	keg3 = 0x0003
	keg4 = 0x0004
)

vscode

idea

You can use Ctr+Alt+Down/Up arrow to have multi cursor on consecutive lines
Is that what you are looking for?

Awesome!  Thanks @ramya-rao-a

Happy Coding!


Fix svm runtime (replaces #91, #33)

float degree_;

This should be an int.

Refers to: onnxruntime/core/providers/cpu/ml/svmclassifier.h:64 in 1ffd453. [](commit_id = 1ffd453f90f3b8bfba08d4f967ad55937549492f, deletion_comment = False)

Z->template MutableData<float>()[write_index] = score;

I would put this out of the loop

Refers to: onnxruntime/core/providers/cpu/ml/ml_common.h:336 in 615f8fd. [](commit_id = 615f8fd2272cf3debe8f2f2d1f1289a479d57f8e, deletion_comment = False)

quick ping to revive PR -- this fix is needed to recover libSVM conversion in onnxmltools.

@wschin, could you review again? Some libsvm converter capabilities need the changes made in this PR.


Which calibrator catalogue to use?

If we are to provide calibration standards to the users for selection we need to discuss what to use and where this goes.
We need to have a standard calibrator catalogue (for L-band).

Which catalogues do we have?
Last I know Tony was supposed to generate observatory guaranteed calibrator lists to be added to the katconfig/users/catalogue repository, but there are bunches of branches and an outdated master?

Shall we use katsdpcatalogues? This is not advised since things is used by many users.

Can commissioning follow this up and make a decision, implementation will rely on it. It does not have to be permanent, but need to be documented .

There is at least 2 places where catalogues sit for imaging (you mention them above) and at least 3 where the targets are specified for beamforming (that I know of).

katsdpcatalogues,
katconfig,
on PTUSE,

PTUSE is not in our discretion to worry about. I know it will be a problem when PTUSE will be used in open time observations (as a service instrument) and users might want to specify a target to observe (and fold) and the ephemeris will not be there. This will make observation to fail. MeerTIME is working on a solution now.
In general it is a bit of a mission to orient yourself in branches etc. I would say that standard list of observatory supported targets should be done via katconfig. I think katsdpcatalogues should be used as experimental/testing/commissioning bucket. I might be wrong and commissioning will assume that katsdpcatalogues should be the place to put catalogues from external users... @spassmoor any thoughts?

I think the choice of calibrator should be made by the person submitting the observation config file and there should not be any catalogue files in the system.

We need to have a standard calibrator catalogue (for L-band)
This would be needed for the OPT or PMT  but not for this scripting project. Since the expert/astronomer would have chosen the calibrator then put it into the config file.

Yes it appears I have confused the issue with my comment. The CAM helper tool to suggest calibrators would be :
import katpoint import numpy as np ant = katpoint.Antenna('ant1, -30:42:39.8, 21:26:38.0, 1035.0') # the MeerKAT reference point ant.ref_observer.horizon = '20:00:00' # horizon set to 20 degrees cat = katpoint.Catalogue(file('/var/kat/katsdpcatalogues/bpcals.csv'),antenna=ant) target = katpoint.Target('0252-712,radec gaincal,02:52:46.157,-71:04:35.28') # Add in target  for pot_cal in cat.iterfilter(dist_limit_deg=[1.,15.],proximity_targets=target,antenna=ant) :     print "%s, is %4.4f Degrees from %s "%(target.name ,np.degrees(target.separation(pot_cal,antenna=ant)),pot_cal.name)

We should get Tony to make some order in katsdpcatalogues before we merge anything to katconfig. Besides, katconfig also has gazillion branches last time I checked...

Some CAM operational notes which might help your decision:

katconfig repo:

There is only one copy of this checked out, on our so-called "head node".  The catalogues are available in observations via kat.sources (a katpoint catalogue).
On site we always keep this on the karoo branch
There is a cron job that automatically updates it (git pull) every 15 min or so.
The git hash of this repo is part of the "config label" that is recorded (and can be chosen) when activating a subarray.  Note that once the subarray is activated, all observations in that subarray build will use the same config label (the instruction set gets a --config-label argument).  I.e. even if the cron job updates the repo while the subarray is active, this will not change what is used for the observations.  Only on the next subarray activation will the new changes come in.

katsdpscripts repo:

there are many copies of this checked out, but the one on the obs node is that one that will be used.
this runs on the master branch.
it is not updated automatically.
changes here will be available immediately the next time an observation tries to read one of the files.

With advice from Sharmila a move has started to get the guaranteed calibrators into katconfig
Jira: https://skaafrica.atlassian.net/browse/SR-1354
Pull request: https://github.com/ska-sa/katconfig/pull/780

Closing this issue, follow in the katconfig pull request


build: use pipefail to not shadow command errors

As we use a function after the commands to format the output, if the first command of the pipe (ex. apt) fails, the second will not, and bash will consider the pipeline successful, not failing the script.

Hi @egeukac,
Thank you so much for your Pull Request!
Best regards,
Carlos Fagiani Junior


ftp-settings.sh: No such file or directory in endOfNight.sh

https://github.com/thomasjacquin/allsky/blob/4731c84a5e83c2b4171153f962519216a05c33e5/scripts/endOfNight.sh#L24
pi@allsky:~/allsky/scripts $ ./endOfNight.sh
./endOfNight.sh: line 24: /home/pi/allsky/ftp-settings.sh: No such file or directory
endOfNight.sh: ===== Generating Keogram
wrong path should be
source "${ALLSKY_SCRIPTS}/ftp-settings.sh"
as in other scripts, imho ;-)

Hi @Chr1sw1e
Actually, the ftp-settings.sh has moved to allsky/config.  It appears likely that your scripts are out of date compared to the rest of your allsky contents.
I would recommend performing a git pull inside of your allsky folder, then move your scripts/ftp-settings.sh config data into the new config/ftp-settings.sh -- NOTE: some of the variable names may have changed, so a manual config would be recommended.
Let us know how this turns out.

Hi,
git pull too much errors..
I deleted the directory and cloned and installed all again, now no more error..
Thanks alot !!!


[Bug] superset add dataset by a view table of doris error

Search before asking

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

Version
1.2.3
What's Wrong?
在doris上创建一个表，又创建了一个view
然后在superset上执行add dataset，普通表可以添加成功，但是添加view的时候，报错

错误信息

在mysql上创建类似的普通表和view，在superset上添加，是没有问题的
What You Expected?
添加view作为dataset成功
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Is this fixed now?


Fix minor typo

I think this edit captures the intended meaning.
Happened to see it while I was browsing the docs.

Thanks! I’m knee deep in updating the docs and I appreciate this.


Feature request: make this plugin work with HTML canvas

This plugin does not work for me when i enable HTML canvas via  <script>L_PREFER_CANVAS = true;</script>.
It would be great if it did.
Don't know how hard this feature would be to implement.

Thanks for suggesting!
I'm sorry but it is almost impossible to implement with the current code, which relies on SVG text glyph features.
It should probably be a different project...


Make pal_io.c build on iOS.

Please, upstream the change

https://github.com/dotnet/corefx/pull/33102


Swal migration

Issue Number #252

Describe the changes you've made
Changed all the alert() messages in all html files to alert using SweetAlert
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Additional context (OPTIONAL)
NA
Test plan (OPTIONAL)
NA
Checklist

[ ] I have added my name in the contributors list at the end of README.md file.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] The title of my pull request is a short description of the requested changes.
[x] Open Source Program names- LGM-SOC

@princeprag would you like to work on this issue?
If yes, ping me there to assign you.


Brew dumper: add missing dependency

Fixes a bug introduced by #834. That PR added the use of an ActiveSupport method (String#exclude?), then added a dependency on it in the spec helper but not in the actual code. This led to runtime undefined method errors when calling brew bundle install.
Error: undefined method `exclude?' for "libtermkey":String
Please report this bug:
  https://github.com/Homebrew/homebrew-bundle/issues
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_dumper.rb:192:in `block in sort!'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_dumper.rb:191:in `sort!'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_dumper.rb:191:in `sort!'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_dumper.rb:21:in `formulae'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_dumper.rb:52:in `formula_names'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_installer.rb:138:in `installed_formulae'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_installer.rb:121:in `formula_installed?'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_installer.rb:166:in `installed?'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_installer.rb:36:in `install_change_state!'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_installer.rb:27:in `run'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/brew_installer.rb:12:in `install'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/installer.rb:35:in `block in install'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/installer.rb:11:in `each'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/installer.rb:11:in `install'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/commands/install.rb:10:in `run'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/cmd/bundle.rb:94:in `bundle'
/usr/local/Homebrew/Library/Homebrew/brew.rb:119:in `<main>'

/cc @MikeMcQuaid

@mistydemeo This isn't necessary. It's included in global.rb which is included before any of the Homebrew/bundle code is run in the latest tag: https://github.com/Homebrew/brew/blob/1d5e354cc2ff048bd7161d95b3fa7f91dc9dd081/Library/Homebrew/global.rb#L30-L31

Confirmed locally too. Opening a PR to revert.


Enable reqwest TLS feature in client lib

Currently TLS connections to the LN GW appear to work using mint-client-cli but not the fluttermint android app. I'm not sure why mint-client-cli works, we need to explicitly add TLS support imo and this PR does it (maybe some other dep activates it accidentally?).

Codecov Report

Merging #558 (60ada2d) into master (770cae0) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #558   +/-   ##
=======================================
  Coverage   72.67%   72.67%
=======================================
  Files          83       83
  Lines       10999    10999
=======================================
+ Hits         7993     7994    +1
+ Misses       3006     3005    -1

Impacted Files
Coverage Δ

fedimint/src/lib.rs
82.03% <0.00%> (+0.33%)
:arrow_up:

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


Here is a solution to automate "Azure Policy - Export compliance report to CSV

Here is a solution to automate "Azure Policy - Export compliance report to CSV" https://dileepveldi.medium.com/export-azure-policy-compliance-report-20608de4c049

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4ff59c65-dffd-a9d3-e02c-25c688322d91
Version Independent ID: 001249ab-2a55-e8ee-7d3c-e3cb7f4afd24
Content: Export Azure Policy resources - Azure Policy
Content Source: articles/governance/policy/how-to/export-resources.md
Service: azure-policy
GitHub Login: @timwarner-msft
Microsoft Alias: timwarner

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Hi @dilv0055! I'll make sure the Azure Policy engineering team sees your post. I'll also promote on my personal Twitter feed. Thanks! -Tim

#please-close


GITHUB_SHA is incorrectly documented or not functioning properly

What article on docs.github.com is affected?
https://docs.github.com/en/actions/reference/environment-variables
And possibly: https://docs.github.com/en/actions (for a clearer issue link).
What part(s) of the article would you like to see updated?
Either:

It is incorrect about the GITHUB_SHA variable being (supposed to be) that of the commit, and fails to say what the proper environment variable is for the SHA hash of the commit; or
The GITHUB_SHA environment variable is not being set correctly (and where to put in an issue for this is inadequately documented).

Additional information
I am attempting to do a test seed that will be consistent across various CI tests, including different architectures at Github and between Github and Travis. The only variable identifiable to enable this is the SHA of the commit (treated as a hex number and modulo an appropriate number to keep it within the range of the seed variable). On Travis, this is working properly with the TRAVIS_COMMIT variable, as can be seen at https://travis-ci.org/github/CleverRaven/Cataclysm-DDA/jobs/762182900#L1246. However, using the GITHUB_SHA environment variable, it is not working for Github, as can be seen at https://github.com/CleverRaven/Cataclysm-DDA/pull/47791/checks?check_run_id=2069095563#step:10:585 - compare to both the commit ID at the top of the page and the identical one used by Travis.
(The build script in use can be seen at https://github.com/actual-nh/Cataclysm-DDA/blob/weariness_order/build-scripts/build.sh, BTW.)

Thanks so much for opening an issue @actual-nh! I think this would be best resolved by our wonderful support team ✨ After you chat with them, if there are any docs updates needed, feel free to comment in this issue and let us know!

@janiceilene: None of the support team categories seem appropriate; which would you advise?

Hm, I'd try https://github.community/search?q=actions

@janiceilene: That's not the support team, sorry.

I'm sorry @actual-nh, I don't think I understood your question then. Could you clarify or add a screenshot?


[QUESTION] Actual size looks big because of the system snapshot

Question
Even though the volume is normally 2gb in size, there is a snapshot created by the system with a size of 11.8gb. I don't know what this snapshot does and because of that, actual size looks big. What is the reason of it?
Environment:

Longhorn version: : 1.1.2
Kubernetes version: v1.21.4+rke2r3
Node config

OS type and version: ubuntu 20.04
CPU per node: 12, Ryzen 5600
Memory per node: 64 gb
Disk type: 2x 512 nvme
Network bandwidth and latency between the nodes: 1gbps,  0.2 ms

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): baremetal

Additional context

Typically, a system snapshot will be created when one of the following cases happens:

the volume is expanded
there is a rebuilding
the volume is restored from a backup

Notice that Longhorn is a block-layer storage vendor. All Longhorn volumes don't understand the concept of the filesystem. When the filesystem inside a volume writes some data to a file then removes the file, the volume itself won't release the space used by the file after the deletion. This leads to a common confusion that there is nothing in the filesystem but the snapshot or volume head takes lots of space. Besides, a snapshot can hold the historical data which may be already removed now. It's another refactor of the snapshot being unexpectedly huge.

Hi @shuo-wu !
I don't need this snapshot. And this snapshot, takes up 5 times more space than volume's own size. What is the reason of it? Why the system use more space? Is there anyway to delete this?

As I mentioned above, when the workload/application/users remove a file from the filesystem, the underlying Longhorn volume won't release the sectors that were consumed by the file since it doesn't understand anything about filesystem. As a result, even if there is nothing in the filesystem of a volume, the volume's actual size still takes a portion of space.
For more explanation about volume size, you can refer to this article: https://longhorn.io/docs/1.2.2/volumes-and-nodes/volume-size/
Notice that the snapshot is right behind the volume head, there is no way to delete it immediately. But Longhorn can clean it up once there is a newer snapshot created.

@gricuk This volume shrinking feature is already tracked in https://github.com/longhorn/longhorn/issues/836.

Hi @shuo-wu create a new snapshot don't remove the first or clean up it is added to the first, i have the same issu the size in the volume si 24gb and longhorn see 95gb, they are a snapshot but a can't remove it, so they are no solution ?

@chris93111 Do you mean the snapshot that directly stands behind the volume head (, which is also considered as the parent of the volume head)? That snapshot cannot be removed, it's by design.

You can check this doc for more details about the volume size explanation: https://longhorn.io/docs/1.2.4/volumes-and-nodes/volume-size/
As for the snapshot that directly stands behind the volume head, there is an improvement in v1.3.0: https://github.com/longhorn/longhorn/issues/3613


fix(worker): disable shared storage by default

Leaving this enabled adds a pretty serious performance hit on at least
some systems. And it is not typically used by containers out of the box.
That is, most of the time it is used, usage is already manually
configured by the script author. So it makes sense to go with
performance as the default metric.

Is there documentation we need to update, or are all the examples good to go? I'm pretty sure there must be at least one example that demonstrates shared storage so we should go through and add this in.

@bacongobbler good catch. I just found and fixed the related docs, too.


Set up responsive chromatic tests

Updated to latest storybook
Removed extraneous storybook imports
Set global viewports for chromatic
Set custom chromatic viewports for grid-col component

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged

Deploy preview for govuk-react processing.
Building with commit 9805ed6c862a440f553d5422d16dbb92f07cd6bc
https://app.netlify.com/sites/govuk-react/deploys/5c7411e2405fee00088de370

Codecov Report

Merging #568 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #568      +/-   ##
==========================================
+ Coverage    99.6%   99.65%   +0.04%
==========================================
  Files          89       89
  Lines         510      584      +74
  Branches       49       58       +9
==========================================
+ Hits          508      582      +74
  Misses          2        2

Impacted Files
Coverage Δ

components/input/src/index.js
100% <0%> (ø)
:arrow_up:

components/checkbox/src/index.js
100% <0%> (ø)
:arrow_up:

components/document-footer-metadata/src/index.js
100% <0%> (ø)
:arrow_up:

components/date-field/src/index.js
100% <0%> (ø)
:arrow_up:

components/select/src/index.js
100% <0%> (ø)
:arrow_up:

components/search-box/src/index.js
100% <0%> (ø)
:arrow_up:

components/radio/src/index.js
100% <0%> (ø)
:arrow_up:

components/label/src/index.js
100% <0%> (ø)
:arrow_up:

components/back-link/src/index.js
100% <0%> (ø)
:arrow_up:

components/supporting-header/src/index.js
100% <0%> (ø)
:arrow_up:

... and 12 more

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 00ae2bb...9805ed6. Read the comment docs.


Explain None/null convention in column.eq docstring

After running into the same issue as described in #1306 I thought I'd add to the docstring explaining that the .eq method follows SQL semantics, not Rust semantics when it comes to None.

Thanks for the update. However the CI errors look valid and need to be resolved before merging this.

@weiznich the doc builds fail when a limited set of features are included because the docs now reference sqlite-specific and pg-specific functions in the shared codebase.
I can try to solve this, but it is not clear to me why the docs are being built with features disabled. Shouldn't docs always reflect all features? If you agree I will de-parametrize the features from the doc build. Otherwise I would love a suggestion on how to solve this, I expected #[cfg(doc)] to do the trick but apparently that does not work with features.

I would prefer allowing to keep that documentation backend specific as not all users build diesel with all backends enabled and that will lead to dead links otherwise. See here for examples of conditional documentation:
https://github.com/diesel-rs/diesel/blob/cb185429d1ed8550f25615e84c14534692da8bda/diesel/src/backend.rs#L145

Sorry if this is an open door, but any reason why Diesel doesn't use cached environments? Seems a bit of a waste of expensive runner minutes to re-install three databases, N times over for each push to a branch with an open PR

@weiznich I've pushed a change that resolves the failed trybuild on my local machine but I don't know if you want this fix to be in this PR, because the problem seems unrelated to my change

Sorry if this is an open door, but any reason why Diesel doesn't use cached environments? Seems a bit of a waste of expensive runner minutes to re-install three databases, N times over for each push to a branch with an open PR

Installing the database takes normally less than 1 minute, while compiling and running all tests takes normally at least 10 minutes. So yes having some cached environment would likely help a bit here, but it will not bring any great speedup, especially as runner minutes are "free" for open source projects. The hard truth here is that nobody put the time in to fix this correctly. At least I have been happy that it works at all and does not require much maintenance. That all written: We would likely accept PR's improving our CI setup.

I've pushed a change that resolves the failed trybuild on my local machine but I don't know if you want this fix to be in this PR, because the problem seems unrelated to my change

These build failures are surprising as they do not happen on other branches. Anyway it's fine to include this fix here.


Beakerlib tests need at least beakerlib-1.28

TestResults state indicator was introduced in this version and it is
used to validate test result.

Goal is to have fail in prepare phase, e.g.
No match for argument: beakerlib >= 1.23

stderr (2/2 lines)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: Unable to find a match: beakerlib >= 1.23

Failed to run command 'ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null root@IP rpm -q --whatprovides "rsync" "beakerlib >= 1.23" || dnf install -y "rsync" "beakerlib >= 1.23"'.

Instead of error in execution
No result or state found in '/var/tmp/tmt/run-026/..../TestResults'.

sounds reasonable to me to fail the prepare

Test /tests/execute/old failed:
out: :: [ 14:00:32 ] :: [  BEGIN   ] :: Running 'rlCheckMakefileRequires 2>&1 | tee output'
out: :: [ 14:00:32 ] :: [ WARNING  ] :: requirement '1.23' not satisfied
out: :: [ 14:00:32 ] :: [   LOG    ] :: package 'beakerlib-1.26-1.fc33.noarch'   covers requirement 'beakerlib'
out: :: [ 14:00:32 ] :: [   LOG    ] :: package 'did-0.17-2.fc33.noarch'         covers requirement 'did'
out: :: [ 14:00:32 ] :: [   LOG    ] :: package 'tree-1.8.0-5.fc33.x86_64'       covers requirement 'tree'
out: :: [ 14:00:32 ] :: [   FAIL   ] :: Command 'rlCheckMakefileRequires 2>&1 | tee output' (Expected 0, got 1)

Seems the versioned require is not properly handled by rlCheckMakefileRequires.

Good catch. Investigation and slowly filing beakerlib issue.

This PR needs to wait on Beakerlib (and require newer version). Thank you Dalibor for working on Beakerlib fix.

@lukaszachy BTW, now there is issue, that this causes cyclic trouble. whenever you add there had to be at least requires version 1.23, this  NVR requirements will implemented inside version 1.27, so without version 1.27 you are not able to check it an fail early :-)

@jscotka And that I meant by (and require newer version). I'd wait on exact version, we are just assuming it be right in the next version.

@jscotka And that I meant by (and require newer version). I'd wait on exact version, we are just assuming it be right in the next version.

Ah yep, thanks.

The fresh beakerlib-1.27 which contains the fix is in the release pipeline.

On second thought - tmt doesn't need beakerlib-1.27. We require 1.23 to parse the result.

Ok, so I kept the beakerlib-1.23 in the requires. Rebased, ready to merge when tests pass.

Apparently there's a need to fix also rlAssertRequired() which was not covered..

Apparently there's a need to fix also rlAssertRequired() which was not covered..

So... do you propose to use 1.27 instead?

What I'm saying is that I need to release another beakerlib update, so this will be fully covered in 1.28 at earliest.

@psss @sopos Should I modify check for TESTRESULT_STATE to work with older beakerlib versions as well (read: Allow this value to be missing?)

I think it is not crucial at least not at this point. It may be interesting information in connection to export of the results to the Report Portal.

Ok, I see, so until then /tests/execute/old would be failing. Let's wait for beakerlib-1.28 then. @sopos, do you plan a new beakerlib release within a week or so?

more likely 2-3 weeks

Ok, updated the require and commit comment. If needed we can move this to 1.6.

it make much more sense to postpone it to 1.6

The fresh beakerlib-1.28 is in the testing repos. We should be able to merge this soon.


Child|Array style types seem to cause type incompatibility

Here is the code to reproduce this issue with 0.15.0 installed as flow-bin from npm:
/* @flow */

type VirtualElement = Thunk|VirtualNode;
type Child = VirtualElement;
type Children = Array<Child>;

class Thunk {}
class VirtualNode {
  children: Child|Children;
  constructor(type, children/*:Children*/) {
    this.children = children.length === 1 ? children[0] :
                    children;
  }
}

I see following errors
/Users/gozala/Projects/reflex/src/core.js: Library type error:
/Users/gozala/Projects/reflex/src/core.js: inconsistent use of library definitions
/Users/gozala/Projects/reflex/src/core.js:5:17,28: array type
This type is incompatible with
/Users/gozala/Projects/reflex/src/core.js:3:23,39: union type

Found 1 error

Turns out inlining types joined into Child union resolves the issue, here is a code that does not fail:
/* @flow */

type VirtualElement = Thunk|VirtualNode;
type Child = VirtualElement;
type Children = Array<Child>;

class Thunk {}
class VirtualNode {
  children: Children|Thunk|VirtualNode;
  constructor(type, children/*:Children*/) {
    this.children = children.length === 1 ? children[0] :
                    children;
  }
}

Sounds like #582. Linking the issues together so we can check/close them all when a fix arrives.

This is still failing after the fix for #582.

OK... so I was able to come up with a simple repro here, and it looks like a bug. @bhosmer, you'll probably like this one.
Fails:
/* @flow */
type T = A|B;
class U {};
declare var children: U;
(children: T|U);
class A {};
class B {};

test.js:5
  5: (children: T|U);
      ^^^^^^^^ U. This type is incompatible with
  5: (children: T|U);
                ^ union: A | B

Passes: (I just moved A and B higher in the source)
/* @flow */
type T = A|B;
class U {};
declare var children: U;
class A {};
class B {};
(children: T|U);

Note this is totally non specific to classes. You can change A, B, and U to whatever (number, string, boolean) and get the same error.

To save me creating a new issue I'm wondering if the error I'm encountering is caused by the issue seen here?
// decl
declare class Fixture {
  title: string;
  component: any;
  props?: Object;
  children?: Array<Object|string>|string;
  expect?: {[key:string]: Array<Function>}
}

// usage
export const a: Fixture = {
  title: 'title',
  component: 'component',
  children: 'Test Child'
};

decl/Fixture.js:9
  9:   children?: Array<Object|string>|string;
                  ^^^^^^^^^^^^^^^^^^^^ array type. This type is incompatible with
 17:   children: 'Test Child'
                 ^^^^^^^^^^^^ string

Ps. Unrelated but is {[key:string]: Array<Function>} a valid type? I'm trying to describe a map with values of the type Array<Function>.

@Gozala, @samwgoldman: Both of your examples will be fixed in an upcoming release.
@Chrisui: you seem to be exploiting an unrelated bug in your example, which has been fixed in an unrelated way: objects cannot be typed as class instances.

@Chrisui see also #1922, where I tried to fix your follow up example but ran into another bug


Port new Asakusa DSL compiler components from Asakusa on Spark.

The following classes are for new Asakusa DSL compiler framework, and does not depend on Asakusa on Spark project:

AsakusafwCompilerExtension - Gradle convention for the compiler framework
AsakusaCompileTask  - Gradle task for the compiler framework

test this please

BUILD SUCCESS.

LGTM.

BUILD SUCCESS.


Refactor: query-redactor is not optional anymore

Description
Refactor: query-redactor is not optional anymore
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

/lgtm

/approve

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"
/override "Red Hat Konflux / ols-e2e-tests-rosa / lightspeed-service"


Allow autocomplete

First, thank you for implementing this package.
I use ntl everyday.
Do you have any plan to support autocomplete?
https://github.com/mokkabonna/inquirer-autocomplete-prompt#readme

Hi @ruyadorno, do you have any progress for this issue?
I am really looking for it.

hi @kpman, I'm still concentrating efforts on ipt v2 in which I want to reuse here, I'm sorry for the long wait but I don't have a lot of time these days (classic open source dev 😬sorry again). I rather keep my focus and once done over there, implement it the right way here 😄
in the meantime - if you're really eager to have it, I'd be open to merge a PR here that just implements inquirer-autocomplete-prompt the same way it's done on ipt: https://github.com/ruyadorno/ipt/pull/15/files if you're willing to give it a try 😉

hi @kpman, just wanted to keep you posted, I have some good news as the rewrite of the API in ipt is mostly done now https://github.com/ruyadorno/ipt/pull/26


[Request] linux-cachyos-rt-bore

Link to the package upstream website/repository
[linux-cachyos-rt-bore] https://github.com/CachyOS/linux-cachyos/tree/master/linux-cachyos-rt-bore
Utility this package has for you
ability to use sched-ext with a realtime kernel
Do you consider the package(s) to be useful for every Chaotic-Nyx user?
YES!
Do you consider the package to be useful for feature testing/preview?

[X] Yes

Are you sure the package isn't available upstream already?

[X] Yes

Does the package's license allow redistributing it?
YES!
Have you searched the issues to ensure this request is unique?

[X] YES!

Have you read the README to ensure this package is not banned?

[X] YES!

More information
No response

Won't add new kernels right now because of https://github.com/chaotic-cx/nyx/issues/882#issuecomment-2384074490


Making sense of the values

Hello!
I have been using this lib for quite a while to get my aquaponics installation automated. Can you tell a little bit more in the docs about the values? I found that I have to multiply ds/M * 640 to get PPM values. But I'm wondering what the ea and ecb values stand for. Thanks for sharing this!

@kingflurkel good question, unfortunately I'm not that familiar with the values myself.
The "EC" is for soil "Electrical Conductivity", I have no idea about ea.
Maybe @Parrot-Developers or @JeromeBouvard know the answers?
Where did you read about the formula to convert to PPM? Would that be useful to have in the library?

@kingflurkel any updates on this?

Somewhat, EC value between 700 and 1500 is okay, I found that out.
I'm trying to get 2 flower powers to work now with your lib. Keep you posted.

@kingflurkel ok, I'm going to close this issue them. As:

EC value between 700 and 1500 is okay

Is the best answer we're going to get, unless Parrot or a biologist steps in.


SaintCoinach.CMD - allexd does not translate all key correctly

Steps to reproduce:

Open SaintCoinach.CMD
Run lang de (any language would be fine)
run allexd

Example using Action data
Actual result: Values for translated keys e.g.  ActionCategory are not translated properly (it prefers the specified language from step 2 instead of the file specific languages for Action.en.csv, Action.fr.csv, Action.ja.csv
Expected result: All values are translated depending on the file language and in case no specific language can be used e.g. AchievmentTarget.csv it uses the specified language.

this would be a potential fix, but i think it could be done better: https://github.com/Akurosia/SaintCoinach/commit/c66d949edf99fd6d852309147171df82d156e794


feat: support new hybriddh crypto primitive

feat: support new hybriddh crypto primitive
inspired by Tink's Hybrid crypto, this change introduces hybriddh package
for ECDH-ES crypto primitives needed for JWE Anoncrypt operations.
This change is a first crypto patch introducing new key types and new primitives.
A second change is coming up to update HKDF key derivation with ConcatKDF one that
follows JWA's key agreement using ECDH-ES:
https://tools.ietf.org/html/rfc7518#section-4.6.
A third change will then follow to update the primitives logic to suit fields needed
in a JWE envelope (ciphertext, tag, iv, derivedKEK for recipients, etc).
closes #1469
Signed-off-by: Baha Shaaban<EMAIL_ADDRESS>

I assume a replacement PR is coming.


How to test user authentication from LDAP in Unit Testing

Laravel Version: 5.6
Adldap2-Laravel Version: ^5.1
PHP Version: 7.1
LDAP Type: ActiveDirectory

Description:
I have an application where all my users are expected to authenticate through LDAP. However, there's little documentation on how to test or mock these types of users.
The complicating issue is that my User model does not have a password field, as I'm not syncing or storing that attribute.
How should I approach writing unit tests that validate whether a user can login, without using actual credentials in my test?

Hi @stevebauman , I really appreciate this snippet. Unfortunately I'm getting an error when attempting to use this with 'username' in the credentials:
My setup:

php 7.3.12
laravel 6.6.2
adldap2/adldap2-laravel ^6.0

My code:
`
protected function makeLdapUser(array $attributes = [])
{
$provider = config('ldap_auth.connection');
return Adldap::getProvider($provider)->make()->user($attributes);
}
/** @test **/
public function test_ldap_authentication_works()
{
    $credentials = ['username' => 'jdoe', 'password' => '12345'];

    $user = $this->makeLdapUser([
        'samaccountname'		=> ['jdoe'],
        'objectguid'            => [ $this->faker->uuid() ],
        'cn'                    => ['John Doe'],
        'mail'					=><EMAIL_ADDRESS>    ]);

    Resolver::shouldReceive('byCredentials')->once()->andReturn($user)
        ->shouldReceive('authenticate')->once()->andReturn(true);

    $response = $this->post(route('login'), $credentials)
	        	->assertRedirect(route('home'));

    $this->assertInstanceOf(User::class, Auth::user());
}`

The response:
Mockery\Exception\BadMethodCallException: Received Mockery_2_Adldap_Laravel_Resolvers_UserResolver::getLdapDiscoveryAttribute(), but no expectations were specified
If I switch to email credentials, the 500 status code goes away but the user is not authenticated. Once I switch to username (the same as my actual implementation) I get the exception.
I do have some sync_attributes in my ldap_auth. I've tried including them without any luck.
Hopefully I'm missing something obvious??

Hi @michaelhume,
The above example is out of date now, you will have to use this:
<?php

namespace Tests\Feature;

use App\User;
use Tests\TestCase;
use Adldap\Laravel\Facades\Adldap;
use Adldap\Laravel\Facades\Resolver;
use Illuminate\Support\Facades\Auth;
use Illuminate\Foundation\Testing\WithFaker;

class AuthTest extends TestCase
{
    use WithFaker;

    /**
     * Returns a new LDAP user model.
     *
     * @param array $attributes
     *
     * @return \Adldap\Models\User
     */
    protected function makeLdapUser(array $attributes = [])
    {
        $provider = config('ldap_auth.connection');

        return Adldap::getProvider($provider)->make()->user($attributes);
    }

    /**
     * A basic test example.
     *
     * @return void
     */
    public function test_ldap_authentication_works()
    {
        $credentials = ['email' =><EMAIL_ADDRESS>'password' => '12345'];

        $user = $this->makeLdapUser([
            'objectguid'            => [$this->faker->uuid],
            'cn'                    => ['John Doe'],
            'userprincipalname'     =><EMAIL_ADDRESS>        ]);

        Resolver::shouldReceive('byCredentials')->once()->with($credentials)->andReturn($user)
            ->shouldReceive('getDatabaseIdColumn')->twice()->andReturn('objectguid')
            ->shouldReceive('getDatabaseUsernameColumn')->once()->andReturn('email')
            ->shouldReceive('getLdapDiscoveryAttribute')->once()->andReturn('userprincipalname')
            ->shouldReceive('authenticate')->once()->andReturn(true);

        $this->post(route('login'), $credentials)->assertRedirect('/dashboard');

        $this->assertInstanceOf(User::class, Auth::user());
    }
}

Let me know if this works for you :smile:

A bit more info: my ldap_auth contains
`
'identifiers' => [
    'ldap' => [

        'locate_users_by' => 'samaccountname',

        'bind_users_by' => 'distinguishedname',

    ],

`

Ok, with that config, swap the authentication test with this:
/**
    * A basic test example.
    *
    * @return void
    */
public function test_ldap_authentication_works()
{
    $credentials = ['email' =><EMAIL_ADDRESS>'password' => '12345'];

    $user = $this->makeLdapUser([
        'objectguid'        => [$this->faker->uuid],
        'cn'                => ['John Doe'],
        'samaccountname'    => ['jdoe'],
    ]);

    Resolver::shouldReceive('byCredentials')->once()->with($credentials)->andReturn($user)
        ->shouldReceive('getDatabaseIdColumn')->twice()->andReturn('objectguid')
        ->shouldReceive('getDatabaseUsernameColumn')->once()->andReturn('username')
        ->shouldReceive('getLdapDiscoveryAttribute')->once()->andReturn('samaccountname')
        ->shouldReceive('authenticate')->once()->andReturn(true);

    // Modify this line to assert your home page redirection:
    $this->post(route('login'), $credentials)->assertRedirect('/dashboard');

    $this->assertInstanceOf(User::class, Auth::user());
}

Can you check if that works for you?

Holy that was fast!
That got me on the right path, after a few tweaks... this worked:
`$credentials = ['username' => 'jdoe', 'password' => '12345'];
    $user = $this->makeLdapUser([
        'samaccountname'		=> ['jdoe'],
        'objectguid'            => [ $this->faker->uuid() ],
        'cn'                    => ['John Doe'],
        'mail'					=><EMAIL_ADDRESS>        'userprincipalname'     => ['jdoe'],

    ]);

    Resolver::shouldReceive('byCredentials')->once()->with($credentials)->andReturn($user)
        ->shouldReceive('getDatabaseIdColumn')->twice()->andReturn('guid')
        ->shouldReceive('getDatabaseUsernameColumn')->once()->andReturn('email')
        ->shouldReceive('getLdapDiscoveryAttribute')->once()->andReturn('userprincipalname')
        ->shouldReceive('authenticate')->once()->andReturn(true);

`

Awesome @michaelhume! Really glad you're up and running. Let me know if you run into anything else.

Thank you!
For feedback, this also worked - I had to add a few fields to satisfy DB integrity constraints.
`
$credentials = ['username' => 'jdoe', 'password' => '12345'];
$user = $this->makeLdapUser([
    'objectguid'        => [$this->faker->uuid],
    'cn'                => ['John Doe'],
    'samaccountname'    => ['jdoe'],
    'mail'					=><EMAIL_ADDRESS>]);

Resolver::shouldReceive('byCredentials')->once()->with($credentials)->andReturn($user)
    ->shouldReceive('getDatabaseIdColumn')->twice()->andReturn('guid')
    ->shouldReceive('getDatabaseUsernameColumn')->once()->andReturn('username')
    ->shouldReceive('getLdapDiscoveryAttribute')->once()->andReturn('samaccountname')
    ->shouldReceive('authenticate')->once()->andReturn(true);

`
Outstanding!!!

One more issue @stevebauman ,
When attempting to make new users in multiple using:
$ldap_user = Adldap::getProvider(config('ldap_auth.connection'))->make()->user($user_attributes);
tests it I'm getting
Illuminate\Contracts\Container\BindingResolutionException: Target class [config] does not exist.

 ( stack trace )

Caused by
ReflectionException: Class config does not exist

for each subsequent test using the snippet


Brining in standard README sections and removing merge cruft.

Signed-off-by: Jeremiah C. Foster<EMAIL_ADDRESS>

Closes #2