Form ID - Not correctly placed?

Challenge Set the ID of an Element has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

<form id="cat-photo-app">
<form action="/submit-cat-photo">
  <input type="radio" name="indoor-outdoor" checked> Indoor
  <input type="radio" name="indoor-outdoor"> Outdoor
  <input type="checkbox" name="personality" checked> Loving
  <input type="checkbox" name="personality"> Lazy
  <input type="checkbox" name="personality"> Energetic
  <input type="text" placeholder="cat photo URL" required>
  <button type="submit">Submit</button>
</form>

@jdavis1990 Your code is incorrect, you've given the wrong ID to the form element -

Give your form element the id cat-photo-form

Please visit the help room for assistance with this, if you're still stuck.

@jdavis1990 as @Manish-Giri has pointed out, your code is incorrect. If you get stuck or have questions with a challenge in the future, please first ask questions to the Help Room. Happy coding!

+1


[FEATURE]: Annotation & Collaboration support for visualizations

On the event of spikes or anomalies, users can add insights (e.g “spike in metrics here is due to ....), so the team can collaborate and comment to resolve the issue.
Some examples of this collaboration

User A on the Dev-ops team notices a spike in the traffic volume on a web page in their Operations Panel. They add a comment to that effect to the panel “Traffic peak beyond nominal bounds due to launch of new product. Expected”. another person on the team who is not aware of the launch, reads the note and downgrades the alert level.

User B on the dev-ops team gets alerted on a spike in latency on a microservice, investigates the incident which has not subsided. Makes a comment on the panel - “lets watch it closely over the next couple of days”. The next day there is again a spike at a different time, another team mate enters another comment “repeat of the incident, no outage”. Team member C adds a note “indexing notices in the database at the time”. Then at the team standup the next day, the team reviews the comment thread and decides to investigate why there is reindexing occurring at that time and fixes the issue.

As per the requirement, Contents on the page will need to be responsive to comediate the space taken by the push-over but as per discussion with @anirudha it should be popover.

Screenshots of implementation:

Hi @mengweieric, as discussed, here are the list of APIs required to complete the collaboration. Also mentioned sample JSON request/response formats with required fields.


openvino sample code - openvino-cons-app doesn't discovery the services and then get notification from openvino-prod-app succesffuly.

Hi Team,
I'm trying to onboard the openvino sample code to the OpenNESS cluster.
But, I'm failed to start the object inferences.
It seems that the openvino-cons-app doesn't discovery the services and then get notification(setting the inference algorithms) from the openvino-prod-app. So, it can't start the inference task once they get video packets from the client simulation side. I attach these two APPs's logs and hope some one can help me on this. Is there anything I should check in advance?
Producer APP:
[root@cn01 ~]# kubectl logs -f openvino-prod-app-787bf68fdc-79jqf
go: finding github.com/pkg/errors v0.9.1
go: downloading github.com/pkg/errors v0.9.1
go: extracting github.com/pkg/errors v0.9.1
2021/02/08 06:21:23 OpenVINO Producer Application Started
2021/02/08 06:21:23 Create Encrypted client
2021/02/08 06:21:23 Loading certificate and key
2021/02/08 06:21:23 &http.Client{Transport:(*http.Transport)(0xc000120280), CheckRedirect:(func(*http.Request, []*http.Request) error)(nil), Jar:http.CookieJar(nil), Timeout:0}
2021/02/08 06:21:23 Service-activation request failed: Post https://eaa.openness:443/services: dial tcp <IP_ADDRESS>:443: connect: connection refused
2021/02/08 06:21:23 Service-activation request failed: Post https://eaa.openness:443/notifications: dial tcp <IP_ADDRESS>:443: connect: connection refused
2021/02/08 06:21:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:22:23 Service-activation request failed: Post https://eaa.openness:443/notifications: dial tcp <IP_ADDRESS>:443: connect: connection refused
2021/02/08 06:22:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:23:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:24:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:25:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:26:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:27:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:28:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:29:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:30:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:31:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:32:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:33:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/08 06:34:23 Inference settings: {vehicle-detection-adas-0002 CPU}
2021/02/08 06:35:23 Inference settings: {pedestrian-detection-adas-0002 CPU}
Consumer APP:
[root@cn01 openvino]# kubectl logs -f openvino-cons-app-6744f45755-hqppx
[setupvars.sh] OpenVINO environment initialized
go: downloading github.com/gorilla/websocket v1.4.2
2021/02/08 06:24:47 OpenVINO Consumer Started
2021/02/08 06:24:47 Create Encrypted client
2021/02/08 06:24:47 Loading certificate and key
2021/02/08 06:24:47 &http.Client{Transport:(*http.Transport)(0xc000190280), CheckRedirect:(func(*http.Request, []*http.Request) error)(nil), Jar:http.CookieJar(nil), Timeout:0}
2021/02/08 06:24:47 Establish websocket Started
2021/02/08 06:24:47 WebSocket establishment successful
2021/02/08 06:24:47 Service Discovery Started

Hi @adtrytech, could you check if the EAA is running in the cluster please? Looking at the output from the producer app, it is failing to connect to the EAA during the Service creation stage.

Hi cjnolan,
The EAA is running in the openness namespace. The error seems caused by rebooting the OpenNESS cluster.
After start the consumer app, the EAA logs some status as below and should it subscribe the ns_openvino, right?
(After tracing the logs, it shows "Added Subscriber for a topic: ns_default")
[watermill] 2021/02/09 00:55:56.305002 subscriber.go:139:       level=INFO  msg="Subscribing to Kafka topic" consumer_group=EAA_294e5390-8c95-4acc-99cd-710695a1a89f kafka_consumer_uuid=CcwFe5zSYpwJCpuFx52xWA provider=kafka subscriber_uuid=TT3rz9tw45Jatr9K8NcdQL topic=client_openvino.consumer
[watermill] 2021/02/09 00:55:56.305025 subscriber.go:210:       level=INFO  msg="Starting consuming" consumer_group=EAA_294e5390-8c95-4acc-99cd-710695a1a89f kafka_consumer_uuid=CcwFe5zSYpwJCpuFx52xWA provider=kafka subscriber_uuid=TT3rz9tw45Jatr9K8NcdQL topic=client_openvino.consumer
<134>Feb  9 00:55:56 eaa[1]: [eaa] Added Subscriber for a topic: client_openvino.consumer
<134>Feb  9 00:55:56 eaa[1]: [eaa] handleClientUpdates() starts
[watermill] 2021/02/09 00:55:56.339074 subscriber.go:139:       level=INFO  msg="Subscribing to Kafka topic" consumer_group=EAA_294e5390-8c95-4acc-99cd-710695a1a89f kafka_consumer_uuid=4AUTZXtmUEsCP5bbaZYWJ9 provider=kafka subscriber_uuid=Fov2brfa2n5AaiL4jJ3K75 topic=ns_default
[watermill] 2021/02/09 00:55:56.339100 subscriber.go:210:       level=INFO  msg="Starting consuming" consumer_group=EAA_294e5390-8c95-4acc-99cd-710695a1a89f kafka_consumer_uuid=4AUTZXtmUEsCP5bbaZYWJ9 provider=kafka subscriber_uuid=Fov2brfa2n5AaiL4jJ3K75 topic=ns_default
<134>Feb  9 00:55:56 eaa[1]: [eaa] Added Subscriber for a topic: ns_default
<134>Feb  9 00:55:56 eaa[1]: [eaa] Added Publisher for a topic: client_openvino.consumer
<134>Feb  9 00:55:56 eaa[1]: [eaa] handleNotificationUpdates() starts

Hi cjnolan,
I try to re-create the prod and cons apps and provide the logs as below. In this test, the prod send out the notification but the cons never receive them. There is also some strange error message in the EAA. Hope these information can help to clarify the issue. Thank you again!
// Prod app
[root@cn01 openvino]# kubectl logs -f openvino-prod-app-787bf68fdc-nwr94
go: finding github.com/pkg/errors v0.9.1
go: downloading github.com/pkg/errors v0.9.1
go: extracting github.com/pkg/errors v0.9.1
2021/02/09 01:02:17 OpenVINO Producer Application Started
2021/02/09 01:02:17 Create Encrypted client
2021/02/09 01:02:17 Loading certificate and key
2021/02/09 01:02:17 &http.Client{Transport:(*http.Transport)(0xc00010c280), CheckRedirect:(func(*http.Request, []*http.Request) error)(nil), Jar:http.CookieJar(nil), Timeout:0}
2021/02/09 01:02:17 Service-activation request sent to the server
2021/02/09 01:02:17 Inference settings: {pedestrian-detection-adas-0002 CPU}
2021/02/09 01:03:17 Inference settings: {vehicle-detection-adas-0002 CPU}
// EAA
<134>Feb  9 00:59:44 eaa[1]: [eaa] Heartbeat
<134>Feb  9 01:00:44 eaa[1]: [eaa] Heartbeat
<134>Feb  9 01:01:44 eaa[1]: [eaa] Heartbeat
<134>Feb  9 01:02:17 eaa[1]: [eaa] Successfully added 'openvino:producer' service
<134>Feb  9 01:02:44 eaa[1]: [eaa] Heartbeat
<134>Feb  9 01:02:57 eaa[1]: [eaa] Failed to send close message to old connection
<134>Feb  9 01:02:57 eaa[1]: [eaa] Failed to close previous websocket connection
<134>Feb  9 01:03:44 eaa[1]: [eaa] Heartbeat
// Cons app
[setupvars.sh] OpenVINO environment initialized
go: downloading github.com/gorilla/websocket v1.4.2
2021/02/09 01:02:57 OpenVINO Consumer Started
2021/02/09 01:02:57 Create Encrypted client
2021/02/09 01:02:57 Loading certificate and key
2021/02/09 01:02:57 &http.Client{Transport:(*http.Transport)(0xc000190280), CheckRedirect:(func(*http.Request, []*http.Request) error)(nil), Jar:http.CookieJar(nil), Timeout:0}
2021/02/09 01:02:57 Establish websocket Started
2021/02/09 01:02:57 WebSocket establishment successful
2021/02/09 01:02:57 Service Discovery Started
2021/02/09 01:02:57 Subscribed to notification: openvino-inference 1.0.0
2021/02/09 01:02:57 Subscribed to notification: terminate 1.0.0

Does the openvino prod and cons APP need the "analytics-ffmpeg" and "analytics-gstreamer" pods?

Hi @adtrytech, it looks like the EAA failed to remove the old websocket connection to the previous consumer deployment. This is preventing a new connection with the new consumer application deployment. Could you try redeploying the EAA then deploy the sample application pods?

Hi cjnolan,
Thanks for your advice.
Following your instruction(I restarted the cluster), I can launch the sample application successfully. But, it seems not always OK for my. Sometimes, I still got failed in deploying the sample applications.
Is there any way to clear the registered service in the EAA?
Thank you!

Hi @adtrytech,
The sample application is configured to remove the service in the EAA using the EAA API once both applications have completed. If both sample applications run without issue and complete, then the EAA should be cleared before the application pods are stopped.

Hi cjnolan,
Thanks again.
I have one more question about how to terminate the sample applications correctly. Delete the pods directly? or other methods?
Regards.

Hi @adtrytech,
If the sample pods are allowed to run the application to completion without failure or the pod being deleted manually while running, then both the producer and consumer pods will send calls to the EAA to remove the service entries in its list before the application exits and the pods stop.

Hi cjnolan
Thanks for your detailed information. So far, I have no more question of this topic. Thank you!


Getting this error code when trying to stake UST via a ledger Nano S

Error ID: 978663d564ba4d1e99ccb39a4477ca88

@hugelynx I have the same issue. What adjustments did you need to make?

I didn't make any changes.
Don't really understand how this can be modified by the end user.
On Wed, 12 May 2021, 11:02 Alex, @.***> wrote:

@hugelynx https://github.com/hugelynx I have the same issue. What
adjustments did you need to make?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Anchor-Protocol/anchor-web-app/issues/104#issuecomment-839644237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT7WJATPJPYCBDSJH3JOQMDTNJG23ANCNFSM44LOG42Q
.

Oh, odd. TerraStation was not initiating a request to my Ledger, but now it is. Thanks.


?slowmode is but an illusion

It appears that the ?slowmode function does not actually set slowmode on the channel (see ModeratorExtension.kt)
This should probably be fixed as soon as possible, to help moderators do their job :)

Illusion: 100

We are all slowmode.


Apicast Deploy on namespace different from 3Scale API Manager doesn't work

Hi,
I'm trying to deploy a apicast on an different namespace from the apimanager.
When deploying using the template all I had to do was configure the BACKEND_ENDPOINT_OVERRIDE variable in the deploymentconfig for it to work.
Is there a way to do the same configuration on the apicast deployed using the operator?
I had no luck make this to work.
I'm using CRC 4.3 and 3Scale 2.8
the cr used to create the apicast
---
apiVersion: apps.3scale.net/v1alpha1
kind: APIcast
metadata:
  name: apicast-user1-tenant
spec:
  deploymentEnvironment: staging
  logLevel: debug
  adminPortalCredentialsRef:
    name: 3scaleportal

the 3scaleportal secret:
oc create secret generic 3scaleportal<EMAIL_ADDRESS>

Hi @raffamendes,
At the moment we don't provide the ability to overwrite that value.
It's probably a good idea to allow the user to overwrite it using the operator too.
We'll take a look at it and evaluate it and come back to you with an answer.

Hi @miguelsorianod,
thanks for the response!! I will be looking forward to this.
I'd be happy to help if this ends up as a good-first-issue
Regards.

Hi @eguzki the issue that I'm having is that the routes that I create for my backends only work after I configure this variable with the route for the backend-listener, I keep getting a 404, I'll try to attach some screenshots and some curl tests to this issue.

any update on this?


Add autowiring alias for LoggerInterface

Fixes https://github.com/symfony/symfony/pull/21517#issuecomment-277216071

@stof fixed, thanks

the next nice thing would be to not register the autowiring type when not required (prevents a deprecation)

@nicolas-grekas done

hmm checking the kernel version doesn't work since it doesn't guarantee the DI version. Any clue?

@nicolas-grekas done

:+1:

Merging then assuming it's fine.. I haven't looked in details.


Set force_destroy: false for IAM users

Otherwise you get output like this:
~ aws_iam_user.raylu
    force_destroy: "" => "false"

Coverage remained the same at 100.0% when pulling d5eab7c44ec59d025c76708b794d68850d13584c on stripe:iamu-force_destroy into 9fb0d724c69253257241f59a2beaf7e5219304a6 on dtan4:master.

Could you update the test iam_user_spec.rb too?

Coverage remained the same at 100.0% when pulling af90499e8852e68986343c259a2a6a6ac3e1a286 on stripe:iamu-force_destroy into 9fb0d724c69253257241f59a2beaf7e5219304a6 on dtan4:master.

Sorry, didn't see the test failure. Amended with a fix!

LGTM 👍 Thanks ❗


positive pixel offset not working in v2.6.0

Any positive offsets returned the same image as for 0 offset. Therefore, Doppler images of Ha failed. and the following ImageMath script return a totally black image:
[outputs]
ha_diff = img(0)-img(1)

Did you get a warning in the logs? This can happen if distorsion correction requires pixels which are outside of your cropping window, typically if the line is not centered.

I did see the error in the log for v2.6.0. However, the same ser ran fine
in v2.5.3, with the expected Doppler related images generated.
On Sat, Jul 6, 2024, 3:05 PM Cédric Champeau @.***>
wrote:

Did you get a warning in the logs? This can happen if distorsion
correction requires pixels which are outside of your cropping window,
typically if the line is not centered.
—
Reply to this email directly, view it on GitHub
https://github.com/melix/astro4j/issues/344#issuecomment-2211985614, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BGFJTAW6QB6UNXWFBCRKPXDZLBS37AVCNFSM6AAAAABKOYKTO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRHE4DKNRRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is an intentional change, which I actually made following another bug report from you : https://github.com/melix/astro4j/issues/334
Before, this would lead to artifacts. So even if you could generate a Doppler image, it wasn't correct in the sense that some pixels had wrong values.

OK. I will expand the capture window. Thanks for this fun project.

Sure. However I'm puzzled because seeing the image you posted, a pixel shift of 1 should work. There may be a bug in the computation of the limits 🤔

I can share my ser file if needed. I do agree that my capture window should suffice for the doppler calculations.

FWIW, I considered my older bug report a user error. I should have just used the other side of the spectrum to generate the continuum image to avoid the banding issue. Thus prefer to use the older logic to get back the Doppler images with my existing crop window size.

Yes, sharing the file would help, thank you!

ser file can be found here:
https://drive.google.com/drive/folders/1bPu2zbTwpMz3wPl3JlbdscZ21U1SeoAG?usp=sharing

Thanks for the file. I understand what's going on here : basically the issue is that the solar limb detection failed, so the whole width is used, and as such, a positive offset is indeed forbidden. I'll check what I can do.

I just confirmed this, in batch processing 2.6.0 didn't produce the positive offsets, from the enumeration. I gave it 1;2;3;4; etc.

Have you tried the 2.6.1 dev version?

2.6.0 is the latest I tried, with the best results so far from 2.5.0


op-node: calldata - reset pipeline on err

Overview
This PR implements sentinel error handling when an error is encountered during da retrieval process.
This allows temporary da errors to be retried by signaling a pipeline reset.
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

testing out on this branch at 4617fbf49cbae6629ae7447dde39f9a402932c44 with this guidance, I was able to stop the node, see errors similar to:
WARN [06-06|17:58:04.377] unable to retrieve data from da          origin=0e2085..27f227:9131334 err="Get \"http://localhost:26659/namespaced_data/00000000000000000000000000000000000000f92140012837778721be/height/37852\": dial tcp [::1]:26659: connect: connection refused"

Then, I restarted the node, and the safe and latest height remain within around 10-20 blocks of each other:
root@jcs-optimism:~/optimism# cast block latest --rpc-url http://localhost:9545 --field number
2736
root@jcs-optimism:~/optimism# cast block safe --rpc-url http://localhost:9545 --field number
2720

Full logs:
logs-144.log

Tested that temporary da errors don't block safe / finalized progress. Wasn't able to test against a live testnet due to a reorg issue.


add DZURLRoute .  Universal route engine for iOS app, it can handle URLScheme between applications and page route between UIViewController.

add DZURLRoute .  Universal route engine for iOS app, it can handle URLScheme between applications and page route between UIViewController.
Project URL
https://github.com/yishuiliunian/DZURLRoute
Category
App Routing
Description
Universal route engine for iOS app, it can handle URLScheme between applications and page route between UIViewController.
Why it should be included to awesome-ios (optional)
Checklist

[x ] Only one project/change is in this pull request
[ x ] Addition in chronological order (bottom of category)
[ x ] Supports iOS 9 / tvOS 10 or later
[x  ] Supports Swift 4 or later
[x  ] Has a commit from less than 2 years ago
[ x ] Has a clear README in English

          2 Warnings

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

1360
301
https://moltin.com/ios-ecommerce-sdk/ redirects tohttp://moltin.com/swift-ecommerce-sdk/

  Generated by :no_entry_sign: Danger


Have official documentation on how to integrate pagefind into meta-frameworks like Next.js, Nuxt, SvelteKit, etc.

Currently, there's not much out there in terms of documentation on integrating pagefind with these popular JavaScript meta-frameworks.
There is issue #327 that I wrote, but that is more of an ugly hack that relies on the framework somehow building successfully in the dev environment and then moving the built pagefind files to the static directory so that the pagefind library can be found when building for production, which I think most would not want to rely on.

Agreed.
I'm likely not the best person to write this documentation; I'm not a heavy user of the current framework landscape, and I'd be likely to miss a lot of idioms when putting sites together. It's also a hard thing to document, as the easy integrations aren't particularly nice, as #327 covers.

A brief aside on improving the experience more generally
I have some hope that the NodeJS API can be of use to the framework-based site generators — possibly by hooking deeper into the internals and generating the Pagefind index alongside the build. (ex: Lume). Since this couples tightly with a given framework, though, it isn't something I would have time to maintain as an official plugin. Tt would require someone with a vested interest to build and maintain it.
In the same vein, if there are any improvements that can be made to the CLI or the Node API to better integrate into these systems, this is the kind of generic feature implementation I'm happy to take on 🙂

In terms of just improving the documentation, there are two paths:

The Resources page of pagefind.app is overdue for a zhuzh up — if others are putting in effort to write up guides, I like linking off to their sites where possible 🙂
Official docs do bring with them some weight and confidence — If anyone is keen to contribute official documentation for any tooling, get in touch — either in this issue or open a PR with some initial changes. I'm happy to help review (and as an inexperienced user of these types of tooling, am likely a useful test dummy)!.

@hankertrix I hope that helps set the scene a little, even though I don't have any immediate contributions to offer myself 😅

I'm likely not the best person to write this documentation; I'm not a heavy user of the current framework landscape, and I'd be likely to miss a lot of idioms when putting sites together. It's also a hard thing to document, as the easy integrations aren't particularly nice, as https://github.com/CloudCannon/pagefind/issues/327 covers.

I see, no worries! Hopefully, there will be more people willing to write documentation when they figure out how to make pagefind work with the framework they are using. I'll continue to hack around and figure out a saner way to build Sveltekit sites with pagefind. Currently, the @vite-ignore comment is looking quite promising for successfully building Sveltekit even if the pagefind path isn't found, but I haven't tested it yet. I'm also still not very sure if the @ts-expect-error comment is needed along with the @vite-ignore comment.

I have some hope that the NodeJS API can be of use to the framework-based site generators — possibly by hooking deeper into the internals and generating the Pagefind index alongside the build. (ex: Lume).

I'm hoping this will eventually happen as pagefind gets increasingly popular (man it has come a long way since I started using it), and people will make Vite or Webpack plugins for it.

If anyone is keen to contribute official documentation for any tooling, get in touch — either in this issue or open a PR with some initial changes.

I would be happy to write official documentation for SvelteKit once I figure out a way that doesn't require you to build the entire site in the development environment to generate the pagefind bundle to get it to build properly in the production environment. However, using pagefind's highlighting script is still non-trivial and would most likely be non-trivial for most of these JavaScript meta-frameworks as almost all of them do server-side rendering (SSR) by default. Having the highlighting script work on every page would necessarily mean changing your entire application to be entirely client-side rendered (CSR), or a single-page application (SPA), which is far from ideal for mostly static sites since you lose out on static-site generation (SSG). Or you could write a handler to handle the highlighting query parameters when requesting from the page from the server, but that would mean giving up static-site generation (SSG) for every single page as well, even if everything else is statically generated, which isn't worth it.

Just a FYI @hankertrix I made a vite-plugin for pagefind that all handles this for you, you can simply install the plugin and use:
// @ts-expect-error - Pagefind will be present at runtime
const pagefind = await import('/pagefind/pagefind.js');

The ts expect error is still required because the LSP doesn't see the file being present but that's just a type error, both during development and build pagefind is present.
More info: https://github.com/Hugos68/vite-plugin-pagefind

Just a FYI @hankertrix I made a vite-plugin for pagefind that all handles this for you, you can simply install the plugin and use:
// @ts-expect-error - Pagefind will be present at runtime
const pagefind = await import('/pagefind/pagefind.js');

The plugin will handle running and managing pagefind for you so no need to run it manually after build or anything like that, all is done automatically. The ts expect error is still required because the LSP doesn't see the file being present but that's just a type error, both during development and build pagefind is present.
More info: Hugos68/vite-plugin-pagefind

Awesome work, tried it and perfectly working. One question though, in order for pagefind to work with static build site, I have to npm run dev && npm run build && npm run preview. Is there any way to avoid npm run dev part?

Very glad to hear! I am currently updating it pretty often and polishing the API, be sure to be on the latest version since there were some bugs in the version from yesterday.


where in (subquery), postgres

#218 postgres step.

Actually, no worries, I am on this. :D

Indeed, this PR and #218 are done with eda1939 :)


Expand testing

Once most design become a bit more stable more tests should be added.
Also look at the following testing frameworks:

https://github.com/burntsushi/quickcheck,
https://github.com/AltSysrq/proptest, and
https://github.com/llogiq/mutagen.

Not doing this right now.


Update beamer to 3.3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Okay, this is strange. The appcast alternates between two different values.
brew cask _appcast_checkpoint --calculate https://beamer-app.com/beamer3-appcast.xml
31537c790c764cc32149084d83e140c05ac965b419af154cda8674084cf01993

brew cask _appcast_checkpoint --calculate https://beamer-app.com/beamer3-appcast.xml
766f15866691fd2c6329a2888fbde950f14a1357c083a52e2406948840e7e761

Looks like the appcast hasn't been updated to show 3.3. I'll close this for now and do a new PR tomorrow.


Intersecting an entirely-optional object type with an empty mapped object type sometimes changes its behavior

Bug Report
Under some circumstances, TypeScript treats { [K in never]: any } & { foo?: number } differently than {} & { foo?: number }.  However, this does not occur with { [K in never]: any } & { foo: number }.
🔎 Search Terms
empty mapped object type, intersection with optional object, K in never
🕗 Version & Regression Information
Tested on 4.0.5, 4.1.5, 4.2.0-beta, and the current nightly
⏯ Playground Link
Playground link
💻 Code
type AreAllStringsTs<T> = string extends T ? true : false;
type Test1 = AreAllStringsTs<{ foo?: number }>;                         // expected: false, actual: false
type Test2 = AreAllStringsTs<{ foo: number }>;                          // expected: false, actual: false
type Test3 = AreAllStringsTs<string | number>;                          // expected: true,  actual: true
type Test4 = AreAllStringsTs<{ [K in never]: any } & { foo?: number }>; // expected: false, actual: true  <-- FAIL
type Test5 = AreAllStringsTs<{ [K in never]: any } & { foo: number }>;  // expected: false, actual: false

🙁 Actual behavior
Test4 is true.
🙂 Expected behavior
Test4 is false.
Potential Workaround
If you have a mapped object type in which the type expression for the keys might reduce to never, add a conditional check to see if the keys set is empty.  For example, I encountered this when working with a type that would make all keys of an object that could take on the value undefined optional:
type Optionalize<T> =
    { [K in RequiredKeys<T>]: T[K] }
    & { [K in NonRequiredKeys<T>]?: T[K] };

Adding a check for never made the behavior consistent with what I was expecting when every field of the input type accepted undefined:
type Optionalize<T> =
    (RequiredKeys<T> extends never ? {} : { [K in RequiredKeys<T>]: T[K] })
    & { [K in NonRequiredKeys<T>]?: T[K]; };

This is easier to analyze in the expression space since we can read the error message:
type AreAllStringsTs<T> = string extends T ? true : false;
type Type1 = { foo?: number };
type Test1 = AreAllStringsTs<Type1>;                         // expected: false, actual: false
type Type2 = { foo: number };
type Test2 = AreAllStringsTs<Type2>;                          // expected: false, actual: false
type Type3 = string | number;
type Test3 = AreAllStringsTs<Type3>;                          // expected: true,  actual: true
type Type4 = { [K in never]: unknown } & { foo?: number };
type Test4 = AreAllStringsTs<Type4>; // expected: false, actual: true  <-- FAIL
type Type5 = { [K in never]: any } & { foo: number };
type Test5 = AreAllStringsTs<Type5>;

type Sub = { [K in never]: unknown } & { foo?: number };

declare let t1: Type1, t2: Type2, t3: Type3, t4: Type4, t5: Type5;
declare let s: string;
t1 = s;
t2 = s;
t3 = s;
t4 = s; // <- correspondent
t5 = s;

The assignment into { foo?: number } is illegal because the target is a weak type (one with only optional properties) and we don't want all-optional properties to act like any for the purposes of assignment.
However, when a weak type appears in an intersection, it would be absurd to prevent assignments into the intersection because one arm of it was weak -- this is counterproductive. So an assignment to {} & { n?: unknown } is always going to be legal because of this.

So an assignment to {} & { n?: unknown } is always going to be legal because of this.

I'm a bit confused about this statement because it seems like in most(?) cases {} & T collapses to T immediately.  In fact, adding this example as a case seems to disagree due to the eager simplification:
type Type6 = {} & { foo?: number }; // seems like this gets immediately simplified to { foo?: number | undefined }
type Test6 = AreAllStringsTs<Type6>;

declare let t6: Type6;
declare let s: string;
t6 = s; // Type 'string' has no properties in common with type '{ foo?: number | undefined; }'.

In my particular case, I ran into a problem because I had the Optionalize type from my first comment defined like this:
type Optionalize<T> = { [K in RequiredKeys<T>]: T[K] } & { [K in NonRequiredKeys<T>]?: T[K] };

My expectation was that it would behave like the Type6 example in the event that RequiredKeys<T> is never, so it would just get simplified to { [K in NonRequiredKeys<T>]?: T[K] }.  However, since the {} derived from { [K in never]: any } isn't simplified out of the expression, it produces a different output than I was expecting.
So perhaps the real issue is that {} and { [K in never]: any } exhibit different patterns around simplification, unless there's a reason why having differing simplification behavior here is also desirable.

I can't promise that it won't break something else and ultimately not be fixable, but a more eager simplification here as you propose does seem reasonable.


:esp.rtc_slow_get_binary() crash when mem unset

if one calls :esp.rtc_slow_get_binary() immediately on start (eg. no rtc mem set) atomvm crashes:
AtomVM init.
I (651) sys: Loaded BEAM partition main.avm at address 0x250000 (size=1048576 bytes)
Starting application...
CRASH
======
pid: <0.1.0>

Stacktrace:
Unable to allocate space for module paths.  Returning raw stacktrace.
{1,0,0,0,[{4,367}],error}

cp: #CP<module: 0, label: 34, offset: 0>

x[0]: error
x[1]: badarg
x[2]: {1,0,0,0,[{4,367}],error}

Stack
------

#CP<module: 0, label: 34, offset: 0>

functions works after setting the memory to something :esp.rtc_slow_set_binary(<<"some binary data">>)
NB: You may need to poweroff/unplug to unset rtc_slow_mem, and get back to the crash.

ok, I'll make a doc PR.

That being said, it does make for slightly more complicated code on the users part. This a perfect case for the use of maybe.

That being said, it does make for slightly more complicated code on the users part. This a perfect case for the use of maybe.

Yeah, but in elixir land with doesn't handle a raise - so it's gets verbose.
But I should just have read the docs here: https://www.atomvm.net/doc/main/apidocs/erlang/eavmlib/esp.html#rtc-slow-get-binary-0
So PR with a small improvement to Programmers Guide, these are also just primitives, one should totally wrap them and serialize/deserialize etc etc.


Netbird not working with keycloak

Describe the problem
Hello, fresh netbird with Keycloak install is not working. Thanks for any help.
To Reproduce
Just follow the documentation for a new installation of netbird with keycloak.
Expected behavior
To work.
Are you using NetBird Cloud?
self-hosted
NetBird version
0.27.10
Keycloak version
24.0.2
Logs
2024-06-11T08:39:48Z ERRO management/server/http/middleware/auth_middleware.go:88: Error when validating JWT claims: unable to get https://kcl.XXX.cz/realms/netbird/users/count?, statusCode 404 2024-06-11T08:39:48Z ERRO management/server/http/util/util.go:80: got a handler error: token invalid 2024-06-11T08:39:48Z ERRO management/server/telemetry/http_api_metrics.go:181: HTTP response 9299963: GET /api/users status 401
management.json
{     "Stuns": [         {             "Proto": "udp",             "URI": "stun:netbird.xxx.cz:3478",             "Username": "",             "Password": ""         }     ],     "TURNConfig": {         "TimeBasedCredentials": false,         "CredentialsTTL": "12h0m0s",         "Secret": "secret",         "Turns": [             {                 "Proto": "udp",                 "URI": "turn:netbird.xxx.cz:3478",                 "Username": "self",                 "Password": "XXX"             }         ]     },     "Signal": {         "Proto": "http",         "URI": "netbird.xxx.cz:10000",         "Username": "",         "Password": ""     },     "Datadir": "/var/lib/netbird/",     "DataStoreEncryptionKey": "XXX",     "HttpConfig": {         "LetsEncryptDomain": "",         "CertFile": "/etc/letsencrypt/live/netbird.xxx.cz/fullchain.pem",         "CertKey": "/etc/letsencrypt/live/netbird.xxx.cz/privkey.pem",         "AuthAudience": "netbird-client",         "AuthIssuer": "https://kcl.xxx.cz/realms/netbird",         "AuthUserIDClaim": "",         "AuthKeysLocation": "https://kcl.xxx.cz/realms/netbird/protocol/openid-connect/certs",         "OIDCConfigEndpoint": "https://kcl.xxx.cz/realms/netbird/.well-known/openid-configuration",         "IdpSignKeyRefreshEnabled": false     },     "IdpManagerConfig": {         "ManagerType": "keycloak",         "ClientConfig": {             "Issuer": "https://kcl.xxx.cz/realms/netbird",             "TokenEndpoint": "https://kcl.xxx.cz/realms/netbird/protocol/openid-connect/token",             "ClientID": "netbird-backend",             "ClientSecret": "XXX",             "GrantType": "client_credentials"         },         "ExtraConfig": {             "AdminEndpoint": "https://kcl.xxx.cz/realms/netbird"         },         "Auth0ClientCredentials": null,         "AzureClientCredentials": null,         "KeycloakClientCredentials": null,         "ZitadelClientCredentials": null     },     "DeviceAuthorizationFlow": {         "Provider": "none",         "ProviderConfig": {             "ClientID": "",             "ClientSecret": "",             "Domain": "",             "Audience": "netbird-client",             "TokenEndpoint": "https://kcl.xxx.cz/realms/netbird/protocol/openid-connect/token",             "DeviceAuthEndpoint": "https://kcl.xxx.cz/realms/netbird/protocol/openid-connect/auth/device",             "AuthorizationEndpoint": "",             "Scope": "openid",             "UseIDToken": false,             "RedirectURLs": null         }     },     "PKCEAuthorizationFlow": {         "ProviderConfig": {             "ClientID": "netbird-client",             "ClientSecret": "",             "Domain": "",             "Audience": "netbird-client",             "TokenEndpoint": "https://kcl.xxx.cz/realms/netbird/protocol/openid-connect/token",             "DeviceAuthEndpoint": "",             "AuthorizationEndpoint": "https://kcl.xxx.cz/realms/netbird/protocol/openid-connect/auth",             "Scope": "openid profile email offline_access api",             "UseIDToken": false,             "RedirectURLs": [                 "http://localhost:53000"             ]         }     },     "StoreConfig": {         "Engine": "sqlite"     },     "ReverseProxy": {         "TrustedHTTPProxies": [],         "TrustedHTTPProxiesCount": 0,         "TrustedPeers": [             "<IP_ADDRESS>/0"         ]     } }

So, the problem was in AdminEndpoint. The right one is: https://kcl.xxx.cz/admin/realms/netbird
But after that another problem occured. When i log in with any account, i get to /peers and can not do anything.
2024-06-13T07:14:15Z INFO management/server/account.go:1374: refreshing cache for account cpjv74ae7hsc73cdg9s0 2024-06-13T07:14:16Z WARN management/server/account.go:1247: user c1017785-7ee5-4d2d-97ce-cc487b850419 not found in IDP 2024-06-13T07:14:16Z WARN management/server/account.go:1381: cache for account cpjv74ae7hsc73cdg9s0 reached maximum refresh attempts (2)

So, i have deleted everything and started from scratch with latest version and it is now working :smile:

Closing.


Update example

This update makes the readme consistent with the example in /demo/app.js

hi @mjsgreen01 thanks for pointing this out. Fix has been added here 62fb3d489ab6981e63977e0cc5186e55f3089b0c. Function signature was incorrect and has been fixed and the docs and examples updated.


Please Correct the Link

Hello, kindly correct the homelink and resubmit the plugin to the Kanboard Plugins directory.
https://github.com/ipunkt/KanboardCommentActions/blob/f7394fac5939765ff000fa05bdcbcce9661a38a4/Plugin.php#L77
The correct link should be https://github.com/ipunkt/KanboardCommentActions

"ipunkt Business Solutions OHG" does no longer exist.
AFAIK:

Bastian Rang now is  "Senior Product and Solution Architect", collaboration Factory AG, Ludwigsburg, Deutschland
Robert Kummer now has his own " Robert Kummer IT"and also works at iu

14 days is long enough to wait for an answer... I dont have time to go deep into looking at companies or chasing them up on the other side of the world.  I believe in circumstances like this, such plugins should be shown in the directory as 'archived' or unmaintained... but the Kanboard developer is not so open to such changes.


⚠ SceneTime has degraded performance

In 9f26482, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1330 ms

Resolved: SceneTime performance has improved in 219cb9f after 2 minutes.


Update to rust-1.34.1

rustfmt output changed so this PR will have to reformat everything as well :upside_down_face:


♻ Refactor: Build OAS

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 92.00000% with 8 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/django_oasis/core.py
89.83%
6 Missing :warning:

src/django_oasis/parameter/parameters.py
90.90%
1 Missing :warning:

src/django_oasis_schema/schemas.py
96.15%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/django_oasis/auth.py
89.79% <100.00%> (+3.52%)
:arrow_up:

src/django_oasis/common/_model2schema.py
92.24% <ø> (ø)

src/django_oasis/pagination.py
96.22% <100.00%> (ø)

src/django_oasis/parameter/parameters.py
89.40% <90.90%> (-0.43%)
:arrow_down:

src/django_oasis_schema/schemas.py
95.82% <96.15%> (+1.79%)
:arrow_up:

src/django_oasis/core.py
88.69% <89.83%> (+1.48%)
:arrow_up:

... and 2 files with indirect coverage changes

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Support for highcharts-more.js

Thanks for the work on this, super useful library.
Quick question however, is there support for highcharts-more? I can't seem to get any of the charts provided there working with this.

Glad you like it! How are you importing highcharts-more into your code?
It should be something like
import Highcharts from 'highcharts';
require('highcharts/highcharts-more')(Highcharts);

Yeah that was my approach. Apologies, should have clarified in my initial question that I'm receiving an error that the type of series is unsupported (solidgauge)

Highcharts error #17: www.highcharts.com/errors/17

This is with Chart prop type = solidgauge and Series type = solidgauge.

Ah you also need the solid-gauge module that series, see here.
So... (I think)
import Highcharts from 'highcharts';
require('highcharts/highcharts-more')(Highcharts);
require('highcharts/modules/solid-gauge')(Highcharts);

Running into an issue with the hard coded values for expected chart and series types.

proxyConsole.js:56 Warning: Failed prop type: Invalid prop type of value solidgauge supplied to Chart, expected one of ["area","arearange","areaspline","areasplinerange","bar","boxplot","bubble","candlestick","column","columnrange","errorbar","flags","funnel","line","ohlc","pie","polygon","pyramid","scatter","spline","treemap","waterfall"].

proxyConsole.js:56 Warning: Failed prop type: Invalid prop type of value solidgauge supplied to Series, expected one of ["area","arearange","areaspline","areasplinerange","bar","boxplot","bubble","candlestick","column","columnrange","errorbar","flags","funnel","line","ohlc","pie","polygon","pyramid","scatter","spline","treemap","waterfall"].

Ah, I haven't added support for gauges yet, but maybe that prop type validation is too restrictive. Does it work despite the warning?

It doesn't. Seems like it fails to generate the yAxis.

highcharts.js:10 Uncaught Error: Highcharts error #18: www.highcharts.com/errors/18

Would you be able to paste the code you're seeing this error with?
I was hoping it would work similar to the Funnel example, which has no axes. https://whawker.github.io/react-jsx-highcharts/examples/Funnel/index.html

P.s. just pushed a commit which removes the prop type validation for series type

Thanks for the update. I'm not seeing the errors anymore though it still is not rendering the gauge. In all examples I've seen of the solid-gauge it utilizes a pane object to set up the tracks for the gauge. Are props passed down through the HighchartsChart component?
`import React from 'react';
import Highcharts from 'highcharts';
import {
HighchartsChart,
Chart,
Legend,
Title,
XAxis,
YAxis,
Tooltip,
PlotLine,
Series
} from 'react-jsx-highcharts';
require('highcharts/highcharts-more')(Highcharts);
require('highcharts/modules/solid-gauge')(Highcharts);
const CubeChart = props => {
const { config, yAxis } = props;
const plotOptions = {
	solidgauge: {
		dataLabels: {
			enabled: false
		},
		linecap: 'round',
		rounded: true
	}
};

const data = [
	{
		color: Highcharts.getOptions().colors[0],
		radius: '112%',
		innerRadius: '88%',
		y: 80
	}
];

return (
	<HighchartsChart plotOptions={plotOptions}>
		<Chart
			type="solidgauge"
			backgroundColor={config.chart && config.chart.backgroundColor}
		/>
		<YAxis min="0" max="100" lineWidth="0" tickPositions={[]}>
			<Series
				id="gauge-test"
				name="gauge-test"
				data={data}
				type="solidgauge"
			/>
		</YAxis>
	</HighchartsChart>
);

};
export default CubeChart;`

So this isn't your code, but it's an example of a Gauge chart, it's a little hacky though as I've never really tried to properly support it. It might give you something to work from though?
A few notes

<XAxis > seems to be required for gauges
Chart type needs to be provided on chart initialisation (see <HighchartsChart chart={{ type: 'solidgauge' }} rather than on <Chart /> component)
P.s. Remember to give your <YAxis /> an id prop and pass integers as prop={1} rather than as strings prop="1"

import React, { Component } from 'react';
import Highcharts from 'highcharts';
import {
  HighchartsChart, Series, XAxis, YAxis
} from 'react-jsx-highcharts';

require('highcharts/highcharts-more')(Highcharts);
require('highcharts/modules/solid-gauge')(Highcharts);

class GaugeChart extends Component {

  render() {
    const plotOptions = {
      solidgauge: {
        dataLabels: {
          y: 5,
          borderWidth: 0,
          useHTML: true
        }
      }
    };

    const paneOptions = {
      center: ['50%', '85%'],
      size: '140%',
      startAngle: -90,
      endAngle: 90,
      background: {
        backgroundColor: (Highcharts.theme && Highcharts.theme.background2) || '#EEE',
        innerRadius: '60%',
        outerRadius: '100%',
        shape: 'arc'
      }
    };

    return (
      <div className="app">
        <HighchartsChart chart={{ type: 'solidgauge' }} plotOptions={plotOptions} pane={paneOptions}>
          <XAxis />

          <YAxis
            id="myAxis"
            min={0}
            max={200}
            lineWidth={0}
            minorTickInterval={null}
            tickAmount={2}
            labels={{ y: 16 }}>

            <Series
              id="gauge-test"
              name="gauge-test"
              data={[80]}
              type="solidgauge" />
          </YAxis>
        </HighchartsChart>
      </div>
    );
  }
}

export default GaugeChart;

Sweet, this works. Thanks for providing the example!


small-centered medium-centered

I upgraded from v6.0.6 to v6.1.1.   small-centered and medium-centered classes stopped working. I am using gulp. I added the classes to the bottom of my app.scss file:
.small-centered {
float: none;
margin-left: auto;
margin-right: auto; }
.medium-centered {
float: none;
margin-left: auto;
margin-right: auto; }
The classes started working again in my project.  However, my app.css file now shows the classes, along with their css declarations, twice.  Once at line 722 and 927 and once at the end.  Any idea why this happened?

Can you post a code sample illustrating how they don't work?

            This box should be centered?

The .callout class adds its own margin, which is overriding margin needed to center the column.
I'd recommend putting .callout inside .column—sometimes when you mix components, weird things can happen.

Thank you!  I did what you recommended and that fixed the issue.  The callout classes are after the centered classes in the app.css file.  It did not occur to me that the css cascade might be the culprit. You're the best!


Broken link in readme

Link for documentation at http://github.differential.io/meteor-billing/ does not exist

It does not. Where can I get a link to the documentation?


feat: parse CSV data using File Picker Widget

Description
This feature helps to parse csv data to JSON which is usable on the platform.
This uses papaparse
 to parse csv.
Why I chose Papaparse

Still maintained and Highest weekly downloads
Auto detect delimiter in csv
Stream large files
Header row support

Fixes #15747
Type of change

New feature (non-breaking change which adds functionality)
This change requires a documentation update

How Has This Been Tested?

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@aswathkk I made some further improvements to the helperText

/ok-to-test sha=c5627c3

@Tooluloope If I have the file-type as CSV and I upload an image file, do we show any error in that upload modal itself?
Also do we auto select Allowed File Type to Text or change the options to only have Text?
cc: @dilippitchika

If I have the file-type as CSV and I upload an image file, do we show any error in that upload modal itself?
Right now we don't show any error. The data is parsed as an empty array

@ashit-rath

/ok-to-test sha=da60a3f

Ok just thinking this through
When users select all/any as the types supported in the filepicker and user selects array in file type.

We can append the following sentence to the helper text. "All non csv filetypes will have an empty value."
We can't show any error here for user because the developer for some reason is allowing this.

When user selects other filetypes which don't contain csv

We can hide the option for array
If the user then goes ahead and changes the filetype to contain csv, we now have to show the csv option again. Revalidation needs to happen here, which is an open issue on fe-coders.
The options can come from JS as well, so it's hard to have this dependency.
This is too much work for such a small item

I think we should just add the following in the helper text "All non csv filetypes will have an empty value." along with the current helper text for the field. @ashit-rath @Tooluloope

Also do we auto select Allowed File Type to Text or change the options to only have Text?
@ashit-rath did not understand this

@dilippitchika Makes sense to add additional message to helper text.

Also do we auto select Allowed File Type to Text or change the options to only have Text?

When user selects Data Format as CSV, we could just auto select the correct file types for them (text, csv) or we could only show the appropriate options and hide image/video etc.

The options can come from JS as well, so it's hard to have this dependency.

When we have a binding in the fileTypes, the value is stored as allowedFileTypes. Options are just for the dropdown and does not have any relevance with the JS binding.

/ok-to-test sha=51d1cdc

/ok-to-test sha=2171a8a

Tested this PR and LGTM

Tested with uploading large csv files via File picker and display on table widget
Tested value in csv file with comma, new line, double quotes
Tested uploading of non-csv files should show empty value
Tested File picker widget by uploading files of all supported data formats


⚠ SolarOscp has degraded performance

In 15c3cb0, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 192 ms

Resolved: SolarOscp performance has improved in a49f0ba after 10 minutes.


stardoc has no html output support

https://skydoc.bazel.build/docs/getting_started_stardoc.html is supposedly a replacement for skydoc, but it has no support for outputting a whole html site - the only output format is "markdown" - which is mostly html, but has no css or navigation elements or index page.  For stardoc to be usable as a replacement for skydoc, some replacement for the html output would be ideal.

I'm also searching for a way to embedded data from bazel-rules into websites, or better to show it inside a sphinx-project with rst-support in the docstrings.
Even it will be a new approach for @dgoldstein0, using sphinx would give you all the feature you need (e.g. create a whole website around the bazel rules).
And stardoc could focus on providing a focused API documentation.
However, I started a small discussion for this topic on the bazel-discuss mailing list.
Feel free to take part: https://groups.google.com/forum/?nomobile=true#!topic/bazel-discuss/YgbIWmgsDuY

Stardoc now supports custom output format as well as proto output format (for integration into your own custom renderer, if that's what you'd like)
Please feel free to re-open if you had something else in mind, or file another FR for something more specific.


Fix componentWillReceiveProps is deprecated

Why adding scrollEventThrottle={16} in this PR ?

Hi @phil-r, Can you marge this PR? Thanks!


Consumes wildcard not working

Problem statement
I would like an endpoint to accept any Content-Type, but it seems the checking of it doesn't take the wildcard into account.
Please remove the sections that don't apply
Swagger specification
---
  swagger: "2.0"
  info:
    description: "Show wildcard accept not working"
    version: "1.0.0"
    title: "Acceptable"
    contact:
      email<EMAIL_ADDRESS>  basePath: "/"
  schemes:
    - "http"
  consumes:
    - "application/json"
  produces:
    - "application/json"
  paths:
    /{filename}:
      put:
        summary: "Put Resource"
        consumes:
          - "*/*"
        description: "Enpoint to upload a resource"
        operationId: "putter"
        parameters:
        - name: filename
          in: path
          description: The unique filename of the resource being uploaded
          required: true
          type: string
          minLength: 1
        - name: content
          in: body
          description: The contents of the file being uploaded
          required: true
          schema:
            type: string
            format: binary
        - name: contentType
          in: header
          description: What Content-Type should be reported when retrieving
          required: true
          default: application/octet-stream
          type: string
        responses:
          201:
            description: successfully uploaded resource

Steps to reproduce
$ curl -X PUT -H "Content-Type: incorrect/jif" --data-binary @zombie.gif http://<IP_ADDRESS>:8000/zombie_02.gif
{"code":415,"message":"unsupported media type \"incorrect/jif\", only [*/*] are allowed"}

After a little bit of spelunking, I believe the problem is here: https://github.com/go-openapi/runtime/blob/master/middleware/validation.go#L65 in validateContentType(...).

It looks for 0-length allowed, and passes if there's none, but that's not this case.
It looks for an error parsing the media type, but that's not a problem: https://play.golang.org/p/HOUa8VmcGZ
It does a case-insensitive search in a slice, but that won't help us: incorrect/jif vs */*
It then fails with no match

On Slack @casualjim said

we use a proper mimetype library to match

... But I'm not seeing that in this case.
Environment
swagger version:
$ swagger version
dev

go version:
$ go version
go version go1.8 darwin/amd64

OS: macOS

it's not accounting for wildcards.
It should probably use a variant of: https://github.com/go-openapi/runtime/blob/master/middleware/negotiate.go#L46


Swift example app does not run

The Swift example here does not run for me: https://github.com/grpc/grpc/tree/master/src/objective-c/examples/SwiftSample
Running:
$ git clone https://github.com/grpc/grpc.git
$ cd grpc
$ git submodule update --init
$ cd src/objective-c/examples/SwiftSample
$ pod install

.. and then running the application on the simulator or a physical phone through xcode results in 999+ errors which look like this:

I stumbled upon this in an attempt to debug and handle the exact same set of errors in a personal swift app. Oddly enough, in my personal app the failure to run only occurs on a physical device -  when running through the simulator I am able to make connections/requests to my grpc server.
For context:
$ protoc --version
libprotoc 3.0.0

$ brew install --without-libgrpc grpc
Warning: grpc/grpc/grpc-0.13.0 already installed

Xcode is v 7.3
This is likely related to #4027

Another note that could help, the RouteGuideClient in the examples (which is objc based) runs for me on the simulator and physical device

Hey, I had the issues as well in my projects. I don't know where they are coming from, but I 'fixed' it by cleaning the project and making a pod install with version 0.39 like 'pod 0.39 install'

This issue looks like it might be fixed. If you are still experiencing this issue, please re-open the issue with information on how to reproduce.


Share manager HA

Which issue(s) this PR fixes:
This PR is part of https://github.com/longhorn/longhorn/issues/6205 - Share manager HA.  It creates the Lease, checks it, and takes action to delete the share-manager pod if it is stale and replace it with one on a different node.
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context
I am marking this PR as a draft because it is not complete.  It needs to make the detachment and re-attachment to the new pod happen before the old pod's node goes notReady.

Should we start reviewing or should we wait for the PR to be mark as ready for review? @james-munson

Update:
Currently, there are 2 remaining challenges:

Get the volume detachment faster. Right now, it is taking 30-60s to detect and detach the volume from the down node. This challenge is difficult because we need to figureout very code flow to detect and skip waiting for engine/replica deletion if a RWX volume is delinquent.
We need to make sure that one broken RWX doesn't make Longhorn to evict all other RWX on the same node

We are making progress on challenges 1. Will update soon

Update:
The POC for challenge 1 at the comment is working now

Get the volume detachment faster. Right now, it is taking 30-60s to detect and detach the volume from the down node. This challenge is difficult because we need to figureout very code flow to detect and skip waiting for engine/replica deletion if a RWX volume is delinquent.

Screencast from 07-12-2024 12:26:30 PM.webm
The remaining challenge is:

We need to make sure that one broken RWX doesn't make Longhorn to evict all other RWX on the same node and fine tune the implementation

FYI: I discussed with @james-munson to draw the state machine of the lease CR. This might help to speed up your review process

I would suggest consolidating the commits.

After reviewing the PRs, the overall flow seems logical, however, there's room for improvement

Error handling: Errors are not checked and properly handled.
Lease check monitor: lack of recover mechanism
share manager's spec field is updated in an improper controller (share manager controller)

Update:

Consolidated the commits
Fixed the bug that new share manager pod became running -> completed -> running again in short period of time. It is due to reaching out to a dead recovery backend https://github.com/longhorn/longhorn-manager/pull/2811/commits/d5ed7daa4f4a07c8ad16ab3b13a7e038df25539c

Updated the PR with some refinement and error handling https://github.com/longhorn/longhorn-manager/pull/2811/commits/945c67091ea1be0767dcadd4e840a8fd1488fff1

Updated the PR with code refinement: remove the logic to remember and add node affinity https://github.com/longhorn/longhorn-manager/pull/2811/commits/d113644d7f9cc1a9b20a0e5d8fb154dd5d09c1b3

Updated the PR with code refinement: refactor ownership transfer for volume/engine/replica https://github.com/longhorn/longhorn-manager/pull/2811/commits/16564ba57b2183d5cd7ca80444cc63822d6e47af

Updated the PR with code refinement: refactor engine/replica controller to try to delete the engine/replica once before skipping the deletion https://github.com/longhorn/longhorn-manager/pull/2811/commits/cb44dcf9ba7530f6613d0933a6f6146734eaa358

Update
With the latest commits from @james-munson and me, this is a demo about the whole flow.
Next step, we will focus on addressing PR review comments from @derekbit and @ejweber
Screencast from 07-21-2024 04:40:48 PM.webm

Still looking for a concrete reason to add a PodInformer to the engine controller

I am going to remove it now as mentioned at https://github.com/longhorn/longhorn-manager/pull/2811#discussion_r1687063286

switch to a PodInformer from a ShareManagerInformer in the volume controller. Most of our controllers only sync on Longhorn CR related events.

This one might be needed as the volume controller need to wakeup quickly and switch the ownership of volume CR to same node as the node of new RWX pod

This one might be needed as the volume controller need to wakeup quickly and switch the ownership of volume CR to same node as the node of new RWX pod

So the flow is:

All share manager controllers detect the lease is stale and enqueue the share manager.
Interim share manager controller takes over.
Interim share manager controller marks the lease delinquent.
Interim share manager controller updates sharemanager.status.state = error.
https://github.com/longhorn/longhorn-manager/blob/a8e56abf69b62b4479584571fb9ada6a293b39f8/controller/share_manager_controller.go#L863-L866
Interim share manager controller cleans up share manage pod.
https://github.com/longhorn/longhorn-manager/blob/a8e56abf69b62b4479584571fb9ada6a293b39f8/controller/share_manager_controller.go#L810-L811

So it looks like the pod and share manager updates will both trigger a volume reconcile simultaneously.

Either would work as an informer, so long as we just drive the ownership off of the pod's node.  We don't want everybody changing to the interim owner of the SM only to change again once the pod is scheduled.

Either would work as an informer, so long as we just drive the ownership off of the pod's node. We don't want everybody changing to the interim owner of the SM only to change again once the pod is scheduled.

This makes sense to me. My main concern is that this PR explicitly switches the volume controller to monitoring pods for requeues instead of share managers. But the share manager controller is already monitoring share manager pods and updating share manager state. (So far) I don't see the reason why the volume controller has to as well now, instead of just being triggered by share manager state as always.

At this moment, I think the last item to get LGTM from @ejweber is the setting name change https://github.com/longhorn/longhorn/pull/8804#discussion_r1685847744
@james-munson is helping with that

Does the feature need to handle upgrade? Will a running RWX volume remain functional after upgrading the longhorn-system without any detachment?
ref: https://github.com/longhorn/longhorn-manager/pull/2811#issuecomment-2233329808
@derekbit Yes, a running RWX volume will remain functional after upgrading the longhorn-system without any detachment

Lease check monitor: lack of recover mechanism

Ref: https://github.com/longhorn/longhorn-manager/pull/2811#discussion_r1681040134
Can you give more details on how disk monitor recover? From a quick reading, I don't quite to get it yet @derekbit

Can we check if we need the swap or keep it as the pervious order?
if err = c.syncShareManagerPod(sm); err != nil {
return err
}
if err = c.syncShareManagerVolume(sm); err != nil {
return err
}

I just swap the order. The result is somehow volume detach/attach is much slower maybe due to have to make multiple sync loops. I think we can keep the current order. I will continue to investigate after the PR is merged.

TODO: I'm thinking we can make lease_lifetime, lease_check_period and so on as global settings in the future. This change would allow some use cases to tolerate longer delinquent intervals.

Maybe a new github ticket for this? @derekbit @james-munson

make lease_lifetime, lease_check_period and so on as global settings in the future. This change would allow some use cases to tolerate longer delinquent intervals.

Let's track it in  https://github.com/longhorn/longhorn/issues/9062

My testing matches @PhanLe1010.  With the sync order swapped, we time out trying to do mount operations in the volume sync, before ever dealing with the staleness of the pod, which I saw get up to more than 20 seconds overdue.  With that, any time gain is lost, so I think the order needs to stay as it is.  FWIW, in the e2e tests that I ran, it did not appear to affect normal RWO behavior.

@mergify backport v1.7.x


[SuperEditor] Fix text insertion when the caret sits at a horizontal rule (Resolves #1187)

[SuperEditor] Fix text insertion when the caret sits at a horizontal rule. Resolves #1187
Typing text when a horizontal rule node has selection, introduces empty text nodes in the document. The issue is that we are inserting a new paragraph but not updating the insertion position before trying to insert the text.
This PR changes _insertPlainText to consider the end position of the new node to insert the text.
https://github.com/superlistapp/super_editor/assets/7597082/df5f983a-5e18-427c-861d-c22713b9a7ee

@angelosilvestre was this always broken, or did it break recently? If it broke recently, do you know why?

@matthew-carroll I think it was always broken.

@angelosilvestre can you go back a ways and check? I'd be surprised if this was missed.

@matthew-carroll It was working before indeed.
After running git bisect it seems it was broken after 5c8de5de565b9377cbc2e5cba89837f36473766a

@angelosilvestre can you see where/why it broke? This PR adds information to a high level public API that we weren't passing before. I'm not convinced that this PR gets to the root cause of the issue. Can you take a deeper a look?

@matthew-carroll I took a deeper look. When this was working, the code was like this:
// Here the selection sits at the horizontal rule.
final extentNodePosition = composer.selection!.extent.nodePosition;
if (extentNodePosition is UpstreamDownstreamNodePosition) {
    editorOpsLog.fine("The selected position is an UpstreamDownstreamPosition. Inserting new paragraph first.");
    insertBlockLevelNewline();
 }

// After inserting the block level new line, the selection sits at the newly created paragraph.
// So when we access composer.selection!.extent.nodeId we are accessing the paragraph node id.
final extentNode = editor.document.getNodeById(composer.selection!.extent.nodeId)!;
if (extentNode is! TextNode) {
   return false;
}

With the new code:
// Here the selection sits at the horizontal rule.
final extentNodePosition = insertionPosition.nodePosition;
if (extentNodePosition is UpstreamDownstreamNodePosition) {
  editorOpsLog.fine("The selected position is an UpstreamDownstreamPosition. Inserting new paragraph first.");
  commonOps.insertBlockLevelNewline();
 }

// Even though we created a new paragraph node, we are still trying to insert the text in the horizontal rule, because we are using the same insertionPosition.
final extentNode = document.getNodeById(insertionPosition.nodeId)!;
if (extentNode is! TextNode || extentNodePosition is! TextNodePosition) {
   return false;
}

I was able to update the PR to avoid adding information to the public API.


Feature ips list

whois -h whois.radb.net -- '-i origin AS1449' | grep -Eo "([0-9.]+){4}/[0-9]+" | ./mapcidr -silent | wc -l
    4352

whois -h whois.radb.net -- '-i origin AS1449' | grep -Eo "([0-9.]+){4}/[0-9]+" | ./mapcidr -silent -aggregate | ./mapcidr -silent | wc -l
    4096

Correct behavior, in the first command the <IP_ADDRESS>/24 is already included in <IP_ADDRESS>/21 and the additional 256 ips are counted twice
<IP_ADDRESS>/21
<IP_ADDRESS>/24
<IP_ADDRESS>/22
<IP_ADDRESS>/24
<IP_ADDRESS>/24
<IP_ADDRESS>/24
<IP_ADDRESS>/24

in the second command the redundant ips are removed 4352-256 => 4096


the application is not showing mac addresses list after re-build it

Hi,
I've tried to clone this project, unzip the library, and try to build the project.
after that, I got my APK (without any changes only 1 import
import android.database.Cursor
inside PhonecallReceiver.kt class as it gives build error without that.
now after installing the APK on the device, it's not showing any Mac addresses on the list even when the watch is connected over Bluetooth.

check this


feat:add redis binder invoke of del&get

Signed-off-by: x-shadow-man<EMAIL_ADDRESS>Description
Corrections for pr #2186
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #2068
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#2901

Modified #2186 as per your suggestion  PTAL @ItalyPaleAle  thx

/ok-to-test

hi, @berndverst   Can this pr be merged?

hi, @berndverst Can this pr be merged?

Yes, looks good to me! Will merge.

@x-shadow-man @wxbty please create a docs PR against the 1.10 to update the supported operations for this binding.

hi, @berndverst Can this pr be merged?

Yes, looks good to me! Will merge.

I cannot merge, because I don't have permission to update your PR / branch! Can you give me permission so I can keep the PR in sync with Master?

git push git@github.com:x-shadow-man/components-contrib.git --force
Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 8 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.08 KiB | 1.08 MiB/s, done.
Total 6 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
To github.com:x-shadow-man/components-contrib.git
 ! [remote rejected]   feat-redis-dg -> feat-redis-dg (permission denied)
error: failed to push some refs to 'github.com:x-shadow-man/components-contrib.git'

git push git@github.com:x-shadow-man/components-contrib.git --force
Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 8 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.08 KiB | 1.08 MiB/s, done.
Total 6 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
To github.com:x-shadow-man/components-contrib.git
 ! [remote rejected]   feat-redis-dg -> feat-redis-dg (permission denied)
error: failed to push some refs to 'github.com:x-shadow-man/components-contrib.git'

done

@x-shadow-man @wxbty please create a docs PR against the 1.10 to update the supported operations for this binding.

please see dapr/docs#2901

** ItalyPaleAle ** approved these changes

@ItalyPaleAle   sorry，misoperation of “requested a review again”


Not compiling due to future-util-0.3.5 dependency error

Hello there,
I've just wanted to start to use this crate in some tool that I'm developing and when I added the crate to Cargo.toml and I haven't modified any source my tests stop compiling.
The error that I've got is
error[E0432]: unresolved import `futures_core::core_reexport`
  --> /home/ivan/persistent/rust/cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.5/src/lib.rs:51:9
   |
51 | pub use futures_core::core_reexport;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `core_reexport` in the root

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
error: could not compile `futures-util`

I'm using the last Rust stable release 1.48.0.
I've got it run my tests without error adding explicitly the futures-util dependency but to the last published release 0.3.8.
I'm a newbie in Rust, so I'm not sure what's going but, perhaps, the solution is just only bumping the dependency.
Thank you very much for your attention.

Have you tried just running cargo update without adding any new dependency to your Cargo.toml?

Have you tried just running cargo update without adding any new dependency to your Cargo.toml?

No, but I will do it and I will report.

I've removed the futures-util dependency that I added yesterday to Cargo.toml for solving the issue temporarily and then I've run cargo clean and then again cargo test and it's worked.
I've seen that when doing cargo test the futures-util: 0.3.8 dependency has been installed so basically it has installed the last published version automatically.
Thank you for your help.


Current tests are failing

By the way do you plan do make a new release?

@jengeb v0.0.6 has been released 3 days ago.
We're currently planning to release v1.0.0 (#155) which will be compatible with ol > v3.5.

@juristr Thanks for your reply and the info!

Just released v0.0.7 containing a minor bugfix when using the "text" style.


when will you support 'chinese'?

What do you mean by support?

You can now set language in the document. The server already supports chinese.


codecov new uploader

bash script will be deprecated
download new binary uploader and perform integrity checks

LGTM (by the way, I haven't looked at the all details, I assume these are standard instructions from codecov.io)

Indeed, all working without any change. For the old shasum checks I had to fiddle around :/


Statistics not visible on Rinkeby Marketplace

I just checked the Rinkeby marketplace to prepare a product presentation of the Data Market and ran into some inconvenience.
The statistics do not show up after I created a new pool and made a transaction.
This is kind of a downer when doing the onboarding and product presentations.
https://market.oceanprotocol.com/asset/did:op:279659A4Dea23A0a2a18b417A99A7bcFbA9cE576

Best
Kai

Pool transactions and "Remove liquidity" button are also not available.

Seems to be an issue only with new pools, for old pools I get the statistics and remove liquidity option.
See https://market.oceanprotocol.com/asset/did:op:83c92519f4A791DdF3f8ae0C6912ED3D05953349

Just tried with a new pool to reproduce the error: https://market.oceanprotocol.com/asset/did:op:9C91bc4146A6f78cdBc8A399F56e606F94412323
Looks like I am getting errors from the subgraph here:
{"data":{"pool":null}}`

thanks for the report, our Graph nodes in Rinkeby indeed stopped indexing for whatever reason. We manually restarted that indexing and Graph data should start to show up also for newer data sets again.

Thanks a lot @kremalicious , I am feeling MUCH better now.


4.10.0 not available via yarn

When trying to install bower (which uses parse-asn1, and transitively, asn1.js), the install tries to pull in asn1.js 4.10.0, which doesn't exist. There's a GitHub release, but no yarn version, apparently. Forcing 4.9.2 does work.
The error I'm getting is:
yarn install v1.2.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/asn1.js/-/asn1.js-4.10.0.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/jenkins/workspace/rs_aa-web-tng_jenkins_build-PDLIB2YYFPZ3HKD27EE26S7JKYWCT2YIOP46OX7JC4W7ITGSUOKA/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
script returned exit code 1

Same here with npm. It report that the version 4.10.0 is exist but tarball cannot be downloaded:
curl -I https://registry.npmjs.org/asn1.js/-/asn1.js-4.10.0.tgz
HTTP/1.1 404 Not Found

Would be nice to bump the version to 4.10.1 and republish it, so the packages that has asn1.js dependency with caret will work with no problems. E.g. ^4.0.0 ➞ 4.10.1 instead of the current corrupted 4.10.0.

I solved the issue by removing my yarn.lock and node_modules, ran yarn cache clean, and then reran yarn install. That gave me a reference to asn1.js 4.9.2 in yarn.lock, instead of 4.10.0.
I think there must have been a 4.10.0 version at some point, which made it into the yarn.lock file, which made the builds want to re-use it. Looks like it doesn't exist any more.
Hope that helps.

Sorry to cause problems, but 4.10.0 was unpublished due to incompatibility with webpack/browserify. You must have been caught between publishing and unpublishing, so the yarn lock file has this non-existent version. Sorry again.
Closing as there is nothing actionable on my end.

Hello @indutny
I'd just like to point out a quote from semver specification, found under the question "What do I do if I accidentally release a backwards incompatible change as a minor version?":

Even under this circumstance, it is unacceptable to modify versioned releases.

According to the answer, it's best to restore the compatibility and release a new minor version. It could have saved people who got "caught between publishing and unpublishing" some confused looks at failed builds and half hours of googling and fixing missing dependency of a dependency of a dependency of a dependency.
 I just wanted to point this out in case such unfortunate thing happens ever again.


CLOUD-55044 Eliminate redundancy at flow state confugarion

@bbihari plz review

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2330/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2331/


Validate compatibility

As a developer, I want a light-weight way to check that I’m able to connect to my MarkLogic cluster (network, authentication) and that my client has been certified to work against the version of the Server to which I’m connecting. (Imagine a UI ETL application implementing a “Test Connection” screen.)
As a Support Engineer, I want to quick way to verify compatibility between a client and a server.
Closely related to #653.

The main challenge I see is that we may validate an old client version to work against a new server version that didn't exist when the old client version was released.  And vice-versa.  So I wonder if we'd need the compatibility matrix stored in both and a client-server version combination is compatible if either the server or client says it is.

We can validate the lower bound and report the Server version. The dependency tracking should only be one direction, from client to server.

Do we know the expected compatibility yet, particularly of MLSDK with ML X.y where X<9?

DMSDK requires new server-side functionality and thus will only work against MarkLogic 9. The 4.0 version of the Java Client will run against an 8 version of MarkLogic, but only for the capabilities available in 8, allowing you to upgrade the clients and server independently.

Implemented by DatabaseClient.checkConnection().  See:
https://docs.marklogic.com/javadoc/client/com/marklogic/client/DatabaseClient.html#checkConnection--
and
https://docs.marklogic.com/javadoc/client/com/marklogic/client/DatabaseClient.ConnectionResult.html


program opens and closes immediately

I know my problem is probably something very stupid as i dont have a lot of knowledge about programming and such so you dont have to bother
after i installed python and pip installed discum i tried to open programm but theres always a problem.. first when i tested with idle the problem was that it didnt detect discum.. tried to reinstall it but for some reason i cant check with idle anymore.. any fix for that?

like idle won't open at all ?

the option to edit with idle is gone is what im trying to say

uh well try to reinstall python completely

deleted python from control panel and reinstalled but still no idle option.. maybe im missing a step

https://stackoverflow.com/questions/29179631/edit-with-idle-option-missing-from-context-menu
i found a stack overflow link to get edit with idle back try that
and the as for the original question at hand of why discum might be missing is that if your using python3 or python
pip installs for one while pip3 install for python3

Yeah that worked perfectly..
issue with discum seems to be resolved too after some trial and error.. i will take the rest from here
thanks a lot for the help!


Use same resource for related tasks but only where possible

Hi there!
In the example we have

First remove the old resource to task assignments
green_paint -= Alice|Bob
green_post -= Alice|Bob
red_paint -= Alice|Bob
red_post -= Alice|Bob
Add new shared ones
green_resource = Alice|Bob
green_paint += green_resource
green_post += green_resource
red_resource = Alice|Bob
red_paint += red_resource
red_post += red_resource
run(S)

Is it possible to say that the same resource should manage related tasks but only where possible (i.e. make this a little more lax).
For example. Alice would ideally postprocess the bike she also painted but is willing to postprocess the bike that Bob painted if necessary.

Basically this needs to be a sort of lax ALTMULT that will schedule a set of tasks to the same resource unless that constraint makes no solution possible.

Did you ever implement a solution for this? I'm encountering the exact same issue I'd like to resolve.

sorry for the late answer: This is currently not possible, you either have to use the same resource or any assignment is allowed. There is the idea to make any constraint "soft" with some cost, but that would be quite some effort.
One way to deal with this problem is to use a small heuristic on top: iteratively add more constraints until no more solution is found. This of course requires that you have some natural order of your constraints (in this case same resource requirements), but maybe there is some natural hierarchy which ones are more important than other ones?


AaC Developer Docs Updates - ZSH Command Inclusions & Profiling AaC Package Updates

Closes #435, #464
Updated the MarkDown for the developer guide for AaC. Within this PR includes the following changes:

Updated the formatting the of the doc to better match up with the various MarkDown linters
Updated some syntaxing that was there to further the emphasis of dependencies and requirements
Updated the docs to include commands (Tested the commands) for ZSH and differentiated between the commands that could be used with Bash-Shell and Z-Shell structures.

Let me know if there is anything else required for this PR.

Again let me know if there is anything else that may need to be changed. My main focus has been on the main document and testing the bash commands against a zsh env and made the necessary changes after.

@Coffee2Bits made those changes and the ones you made make sense to me. I went ahead and added them and some other tweaks for continuity with the new recent changes


Header set X-Frame-Options "DENY" breaks some of panel-bar actions

In my .htaccess, I'm using some of html5boilerplate's anti-clickjacking and the default options doesn't allow some redirects like the one on "Edit" button.
https://github.com/h5bp/html5boilerplate.com/blob/master/src/.htaccess#L190
One has to change the default value of X-Frame-Options header from DENY to SAMEORIGIN in order for it to work.
Lots of security implications thou... since this might not be the best setting for everyone as described on html5boilerplate's source.

Probably not much that I can change from my side. But I will try if I could detect this and then simply let the links work as links instead of trying to load them in the iframe.

Leaving this here for me: https://blog.whitehatsec.com/x-frame-options-xfo-detection-from-javascript/

Good solution for that problem. Use direct links to the panel if iframe is blocked. Or what do you think about it @rhawbert ?

Hi @jenstornell, I'm not a security expert was just trying to follow some good practices...
It'd be ideal, in the user experience point of view, if @distantnative managed to make it work in every case/configuration/server... but I do agree that there're too many variables (servers, hosting companies, etc.).
I believe a progressive enhancement approach would be a better fit thou... I mean, make it work without the bells and whistles.. then improve it to the ones that are technically able to get the improvements.

If there are so many variables to consider an easy way would be a config value.
panelbar-iframe: true / false

It'd be ideal, in the user experience point of view, if @distantnative managed to make it work in every case/configuration/server...

Totally agree. But since the X-Frame-Options are prohibiting exactly what I'm trying to do, it won't be possible if not set (at least) to SAMEORIGIN

Ok, sounds good to me.

Added the progressive enhancement workaround to the develop branch.


Research the possibility of using buildkit

For now user might use buildkit with werf's dockerfile builder.


X11 copy/paste not supported ?  (firefox)

While copy/paste using Ctrl-C/Ctrl-V works, the commonly used X11 paste method (select + middle click) doesn't work.

Seems to work with Chromium 63, issue is ith Firefox (tested with 58.0.1)

Closing in favor of #30


Tests based on pytest are not executed as part of PR build

Description of the bug
This seems like a regression error. Generation of coverage report by pytest has a dependency on module pytest-cov and this module is currently missing. Installing this module should allow running the pytests.
Steps to reproduce the bug:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Additional information
Add any other context about the problem here such as screenshots, software versions, and browser information.

This has been fixed.


#4: getSubmitters can no longer return null

Gedcom.getSubmitters() now returns Collections.<Submitter>emptyList() instead of null.

1.10.0 has been released with this fix.


Dependency Conflict with React Native 0.74.5

Steps to Reproduce:

Initialize a React Native project using version 0.74.5.

Run the following command to install react-native-crisp-chat-sdk:
npm install --save react-native-crisp-chat-sdk

The installation fails with a dependency resolution error.

Expected Behavior: The SDK should support the latest stable version of React Native (0.74.5), allowing it to be installed without dependency conflicts.
Actual Behavior: The installation fails with the following error:
npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error Found<EMAIL_ADDRESS>npm error Could not resolve dependency:  npm error peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>Environment:

React Native Version: 0.74.5
react-native-crisp-chat-sdk Version: 0.14.4

Same here

Issue should be fixed with our latest release


Rebuild against new Scalafix version

I received the following warning when using these rules
[info] Loading external rule(s) built against an old version of Scalafix (0.9.33).
[info] This might not be a problem, but in case you run into unexpected behavior, you
[info] should try a more recent version of the rules(s) if available. If that does
[info] not help, request the rule(s) maintainer to build against Scalafix 0.10.4
[info] or later, and downgrade Scalafix to 0.9.x (x>=33) for the time being.

@michaelmior
Thank you!
We have released version 3.0.1 and hope you will try it.
If you have any further comments, please do not hesitate to raise an issue!
https://github.com/pixiv/scalafix-pixiv-rule/releases/tag/v3.0.1

@Javakky-pxv Thanks! That seems to have removed the warning.


Support running openj9 functional native in AdoptOpenJDK

Supporting running openj9 functional native test as testimages are supported in AdoptOpenJDK 11+ builds.
Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

Issue as:
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Advanced/591/
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Advanced/593/
Fix:
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Advanced/592/
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Advanced/595/

Note currently this change only export whatever openj9 naming the libpath, e.g. NATIVE_TEST_LIBS. Renaming it as OPENJ9_TESTLIB_PATH may be more clear as we do have hotspot testlibs, which will need to update the name in openj9 test makefile along with other miscellaneous changes. Open to discuss.


[CH] Compatibility with collect_list

Describe the bug
ClickHouse has reverted the pr 48593, we need to make a change outside ClickHouse to achieve the compatibility.

collect_set may also need to achieve the compatibility.


CircuitInstruction qarg type changed without communication

Environment

Qiskit version: main
Python version:
Operating system:

What is happening?
CircuitInstruction qarg type is suddenly changed.

This can cause problem in unittest if one is testing instruction qubits without typecast.
How can we reproduce the issue?
See above screenshot
What should happen?
Data type must be preserved, or change must be mentioned in the release note
Any suggestions?
No response

Can you test data[0].qubits? Hopefully the type of that is still tuple. Even so, we should fix this.
Fwiw, treated CircuitInstruction as a 3-tuple with list elements (rather than using the attribute accessors) is a legacy backwards-compatible behaviour that comes with a runtime penalty. It was added during the switch of the type of the circuit data 2 years ago. We probably should have deprecated and removed it for 1.0, but forgot.
Either way, the type shouldn't have changed while it is supported,band we can get that fixed.


Testing using envs

How does testing work?
The current specs in test_spack.py won't be correct after the transition
Workflow

pass spec to script
fetch repo based on spec
find spec.yaml
setup env based on spec.yaml
install
test

I had an idea how to think about these tests. What we're trying to test is just like testing any other function that has too many degrees of freedom to test them all.
Assume we implemented def sin(double) -> double. We can't test this function for all possible inputs, because that's 2^64 tests. So we can either test some handpicked values or do some fuzzing. But which values do we pick by hand? Ideally some relevant cases and some edge cases. I don't think we would automatically follow the values our customers use and only test that (they could be using it with only values between -2Pi and 2Pi, or +-2Pi around Pi10^13, or only epsilon tiny values around zero).
In our case we try to test a function def install_package_X(bool has_aes, int version, ...). Now if we test what's in the spec.yaml in the master at the time of testing and master changes, we don't test the old case anymore and we could unknowingly break everyone who hasn't merged their master yet.
I think we should handpick some relevant cases and add/remove cases manually - same as versions in packages.
Also, isn't copying the spec from a version into the tests waaaay simpler than implementing the automatism? Also you get a nice centralized overview of what's being testet, ergo the contract of spack-c2sm.

Yes you are right. That makes a lot of sense.
So in principal we would continue how we do it right now.
Question:
How do we want to define the spec of the tests?
As we did so far using icon@master%nvhcp gpu=60 ...
or through environments like
spack:
    specs:
        - cosmo<EMAIL_ADDRESS>cosmo_target=cpu ~cppdycore +eccodes
        -<EMAIL_ADDRESS>        -<EMAIL_ADDRESS>+fortran
        - libgrib1@22-01-2020
    concretizer:
        unify: true

The latter is a bit more robust in my view, also because we test the environments workflow too.
An we anyway to move towards spec.yaml

I see two options for this:

Create environments in spack-c2sm for the packages and use them in the tests.
Inline everything in the environment in a test. Makes for a long command but it totally legal.

Since Spack is still version zero dot something, testing the environments is maybe not such a bad idea. If we find bugs the users and spack devs will thank us. But generally I think it's not the responsibility of spack-c2sm to test that spack's environments work correctly.
I'm fine with both options.

Implemented in spack v<IP_ADDRESS>


getPayload should be tree-shaked from client dist

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal
Inside my component file, when I export the getPayload function, it should be tree-shaked from the client code dist files.
Also, to tree-shake everything that is only used by the getPayload functions (such as backend libraries).
Motivation
to reduce the bundle size and to remove, and not expose code that runs on the backend.
Example
I managed to create a workaround that actually works in here:
https://github.com/greenpress/greenpress/blob/dynamic-front-ssr/apps/front-ssr/views/index.vue
Note: it's not tree-shaking the sdk import that is only used by the getPayload.
As you can see, I wrapped the original getPayload with a conditional import.meta.env.SSR.
I also passed true as a value to the useHydration hook in order to make it call the payload even though I don't have the original function.

@davidmeirlevy I was gonna work on a little something for this but @egoist beat me to it.
https://github.com/egoist/vite-plugin-remove-exports
Maybe we could give it a shot using it.

I'll look into it and send a demonstration.


Unify client options

struct BlobContainerClientOptions

Why do we have multiple ClientOptions types?  In other languages we just have BlobClientOptions that we take with BlobServiceClient, BlobContainerClient, BlobClient, BlockBlobClient, ..., etc.

blob service done.


Exclude dist in tsconfig / Generic type for record

Build fails because dist directory is not exclude from compilation (and d.ts declarations files are typescript files)

Generic type in actionCreatorsFor is usefull for typescript users.
I exposed your "types" in index file to be able to use them to type some variables in user code. In addition I added a simple "Record" interface with all default constants used in reducers. Record interface can't be used in internal code because constants are configurable.

Thanks


[feature] Keyboard shortcuts

Hi,
Playing with Dockit.
The UI is pretty neat!
I found it really useful to get a bunch of connections and being able to switch between them.
:+1: :star:
Do you plan to implement keyboard shortcuts?
There are the one of Kibana, like ctrl+enter that fire the underline request, which should be very common for instance.

thanks for your feedback, yes definitely, I will definitely add it, I just wanna post DocKit to the end user as soon as possible to get enough feedback to improve it from the real user requirement, this is the good case then, I will work on it

Feature
Shortcut
Description
State

General editing
Ctrl/Cmd + I
Auto indent current request.

General editing
Ctrl + Space
Open Autocomplete (even if not typing).

General editing
Ctrl/Cmd + Enter
Submit request.

General editing
Ctrl/Cmd + Up/Down
Jump to the previous/next request start or end.

General editing
Ctrl/Cmd + Alt + L
Collapse/expand current scope.

General editing
Ctrl/Cmd + Option + 0
Collapse all scopes but the current one. Expand by adding a shift.

Autocomplete
Down arrow
Switch focus to autocomplete menu. Use arrows to further select a term.
:white_check_mark:

Autocomplete
Enter/Tab
Select the currently selected or the top most term in autocomplete menu.
:white_check_mark:

Autocomplete
Esc
Close autocomplete menu.
:white_check_mark:

the base shortcuts listed above has been added to the latest version, can download and have a try, I will close this issue, well comes to raise issues if you find any other stuffs not working as expected or features you want 😄

Excellent !


provide a function while changing the month picker

As I am using this package and it's perfect for my flutter app design wise. So while loading a page with current date and month, an api call is working ng on onDateChange() function. But on changing the month, it remains the same as the api is already called. So it would be better to add a function while changing the month too.

Thank you for your feedback. I will provide this feature as soon as possible.


GH-39978: [C++][Parquet] Expand BYTE_STREAM_SPLIT to support FIXED_LEN_BYTE_ARRAY, INT32 and INT64

What changes are included in this PR?
Implement the format addition described in https://issues.apache.org/jira/browse/PARQUET-2414 .
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes (additional types supported for Parquet encoding).

Closes: #39978

@github-actions crossbow submit -g cpp

The i386 test failure is related.

Sorry for being late because I'm on my Spring Festival Vocation previously, this general LGTM, just some minor comments. And do we have benchmark data changing here?

@github-actions crossbow submit -g cpp

@ursabot please benchmark

@github-actions crossbow submit -g cpp

The regressions above are because I made data generation more realistic and therefore less trivially compressible:
https://github.com/apache/arrow/pull/40094/files#diff-e0338b1864949c8001485874b6249a5a756c83c9671e4a31ee523289035487e5R171

Also, I've generated a test file here: https://github.com/apache/parquet-testing/pull/46

@github-actions crossbow submit -g cpp

@github-actions crossbow submit test-ubuntu-24.04-cpp-gcc-14

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g cpp


Adding application metrics

Fixes issue #876
Adding some metrics to eventnative application

✅ app start / shutdown / running_time - its ok to bw used instead of start / shutdown
✅ unit initialization (destination, source, api_key, etc) success | error
✅  new unit created (destination, source, api_key, etc) success | error not needed
unit test connection (destination, source) success | error
task_executor.go: source(collection) sync run success | error | cancel | stale?
uploader.go: file processed (break by destination & table ) success | error
configurator backend auth status success | login_failed | error
open API endpoint statuses http codes - enable gin metrics for configurator (copy code from server)
✅ mail send status success | error
✅ slack notification send status success | error
✅ replay status success | error