Data representation using brython

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #5827

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Hello @ahmadmardeni1, @hectorkambow, I would like to review this article.

Okay @ayodele96, you can reduce the data to the minimum amount possible. Also, make sure you go through all the conversations and implement all the requested changes.
Thanks

@Bravinsimiyu you can review the content now. i've implemented all the requested changes

Plagiarism check done

@Bravinsimiyu what's the update on the article sir

Hello @ayodele96, I waiting for the plagiarism check to be done. Now that your article has passed the test, let me finish up with the tech review.

@Bravinsimiyu done with the commits

Hello @srishilesh, @ahmadmardeni1. This article is ready for final review.
cc @hectorkambow

Hello @ayodele96
Good work!
On a quick glance at the markdown formatting, it looks good. I've suggested a few more minor changes. Please make sure to address them.
@Bravinsimiyu It would be great if you can ping the author to add the front matter and peer-reviewer contributions (PRC) line or you can just add it as a new comment, I can add that for you.
Also, once the author is done with the changes, please make sure to perform a grammar check and a code check. You can also suggest if the author can add more content.
I feel a step-by-step implementation of the python code snippets would definitely help (like explaining different attributes), instead of just stating those attributes. What do you think?
Thanks.

@srishilesh, Let the author first implement the suggested changes. Then I will go through the updated article and see if there is a need for the author to add more content ( Adding more explanations to the code snippets and attributes)
Also, could you add the front matter and PRL
Thanks

Hello @ayodele96, Please take note of the suggestions made by @srishilesh. Please go through all the comments and implement them accordingly. The suggestions will format your article to make it easy to read and follow.

@Bravinsimiyu i have implemented all the requested changes

@Bravinsimiyu done

@Bravinsimiyu
We are over extending ourselves wayyy to much on this review. This is a perfect candidate pull request to cloes - we do not provide revisions services. If the PR is not ready to be published, then it should be closed.

@section-engineering-education/content-moderator-team
We need to be making sure our test reviewers are being helped out with PRs like these.

@Bravinsimiyu
We are over extending ourselves wayyy to much on this review. This is a perfect candidate pull request to cloes - we do not provide revisions services. If the PR is not ready to be published, then it should be closed.
We should reference our resources pages - give some pointers and close any pull request that requires this much heavy lifting.

@hectorkambow
I totally agree on that.
As I had mentioned in one of my comments earlier, I feel the code snippets could have had better explanation. It lacks explanation about the attributes that have been used for plot charts.
@Bravinsimiyu Please consider closing this PR, if the required changes are not made by the author in this revision.

@Bravinsimiyu @hectorkambow @srishilesh, please don't close it yet. I will go through it thoroughly within the week and make the necessary changes to the article.

Hello @ayodele96.
When writing an article, ensure that you re-read it in the reader's POV. This will help you understand what they would really want or gain from your article. Ensure that it answers all your questions as the reader before submitting it.
The steps should be clear - I feel a step-by-step implementation of the python code snippets would definitely help (like explaining different attributes), even a beginner would understand when something does not go well on their part. The results can be shown in clear screenshots /images and short videos/ GIFs.
Kindly go through the article thoroughly- the whole article- before pushing the changes. Take your time while making the changes.
Therefore, this PR will be closed temporarily to allow you to work on the suggested changes outside the queue. This will allow other ready articles to be reviewed and published without delays. When you finish working on the changes, open a new PR with the word 'duplicate' at the beginning of the topic.
If you have any issues with the step-by-step implementation, you can check out this PR. Ensure your format your article neatly and indent your code blocks correctly.
Ping me on the new PR. Thanks. 🚀

Hello @srishilesh, @hectorkambow, could you close this PR

@Bravinsimiyu @hectorkambow @srishilesh, please don't close it yet. I will go through it thoroughly within the week and make the necessary changes to the article.

No worries all edits and revisions should happen outside of the queue (or backlog of articles).
Only polished and ready to publish articles should be in the queue 👍
Please review our resources docs - and re-submit the pull request when it is ready to be published.


Feature Request: command to check if nickname is online in IRC/Discord

Since we can't actually see who's on the other side of the bridge unless they talk, would it be possible to ping a user from the other end and have the bot give you a status check? Thanks.

I'll close this issue for now, as commands still seem out of scope of what the bot currently does, and I'm not implementing new features. Thanks for the interest!


No Update on Connection

After Install, No Log Update containing PoE control, as well as no buttons added for remote control. Unable to see any errors or why the plugin is failing.

@SaavageBueno Did you restart homebridge?


chore: remove docker run

Comment the docker run, generally I used to build the image only.

Closing as stale. Please rebase and reopen if you'd like to incorporate this change.


Drag and Drop feature!

Hi,
Do you have any ETA when the drag and drop feature will be implemented, or if you can guide me a little bit, I can send the PR?
Thanks.

Hi @azhard4int, (and any interested vue-cal user to be part of this awesome project!)
Thanks for your interest.
The drag and drop feature is already started in the drag-and-drop branch, but left aside for now for a matter of priority in the feature requests order and because of the difficulty of adapting all the code to work well with this feature and vice-versa.
If you want to help on that, I appreciate it, would be awesome.
You can start by looking at the index.vue file in the drag-and-drop branch.
In the onMouseMove() function, there is a case if (dragAnEvent._eid) which should handle the event move at cursor coords.
I have placed a couple of Todo lines to explain what to do in the code from there.
At the moment, I represented the move of the event on a floating blue div which is placed at cursor coords while you drag an event and then removed in onMouseUp().
You will best see this blue div on the Edit, delete and create event example, the editable-events option needs to be true to allow drag and drop. (start dragging an event)
So after you get familiar with the codebase, I suggest that you continue on that path and pretend the blue floatting div would be an event mirror while you drag and then on mouseUp, the event mirror disappears and the actual event is moved (so date is changed). You also need to prevent the delete button to show up.
This is the very first satisfying step.
When you complete this that's great, let's do a last code cleanup and a first PR and talk about next steps.
If you want an overview of the milestones to integrate it fully, here it is:

Once this is done, the next step will be to try to move the event directly in the onMouseMove() function (there will be an option to have an event mirror or not), but I am afraid it might be too slow, so we could need some refactoring.
The third step will be to make it work with split cells, that's very straightforward.
The fourth step I would say is to make it work with multiple-day events. That will probably be more tricky because of event segments (1 per day), but when we reach this stage we should discuss it.

Let me know if you need any help at any stage. It's important you get a good understanding of the codebase.
Thanks for any effort you do!

Thank you for the detailed comment, I could not get back to you earlier due to our office relocation.
I'll start playing around in the coming weekend and see how it goes.

Hi @azhard4int,
Myself too I am quite busy at the moment and I regret to have to leave vue-cal unattended for so long haha.
But I am very excited about this feature and plan to get back to vue-cal very soon.
Anyway, don't hesitate to ask anything or get in touch by email if you prefer, you can get my email address in the package.json.
Cheers.

We are looking to move over our calendar plugin to vue-cal and having drag n drop is a must. Please keep us updated! :)

Hello Antoni. I am also looking forward to seeing this feature happening. I guess because all other calendars providing the same, but I have to admit, I like your calendar the best so I would like to donate more (you had a first from me a while ago) when it is ready, as I feel, if you worked for it you should get something in return for it, a pizza does not come from anything either 😁, but for me it is worth more than a pizza 😉😎

Hi @Nice2Work,
Thanks for the feedback and enthusiasm! I appreciated your previous donation, thanks for that too!
Let me give you a little bit of context, I'd like to share about the current state of Vue Cal's project.
I split my spare time with other projects, but on Vue Cal I currently have 2 big features I am working on: recurring events, and drag and drop.
I started the recurring event first and got a quick result, so I was confident to get it done fast.
...Until I started to integrate multiple day events and events count on year and years views. And I haven't even started to integrate the overlaps on events repetitions yet. 😞
Now that Vue Cal's codebase is quite big, everything I add must be very performant, and so far this is not, so I am not ready to release it in a near future.
I previously left the drag and drop feature seeing it's not going to be performant enough.
But I recently came back on it with a fresh mind and a new idea, I did the basics and it's rather promising, but it will most likely not work on mobile for the first few releases.
I still believe this is the way to go though, it's way more performant than the universal way.
Now seeing that a bunch of Vue Cal users are waiting for the drag and drop, I'll try to focus on that until we can see the first results. 😉

Im waiting as well for drag and drop and would be happy to make a sizeable donation to make it work :-)

Thank you @bjensen and supporters!  :)
I made some good progress these last few days.
But to be clear touch devices won't be supported straight away, not only mobiles - that's what I meant.

The important things I remain to do are:

handle dropping an event half in the day range
handle splits (splitting days)
fire DOM event on event drop
test on Edge
write documentation

Won't be in the first release:

dragging multiple-day events
dragging all-day events
touch support
snap to the closest time step in the timeline

I'll give some updates here soon!

Exciting news fellas, I am planning a pre-release end of next week!
This will be the opportunity for all to test the new feature and let me know your feedbacks.
I will create a Codepen so everybody can easily play with it.
If it is satisfying as the first stones of this feature I will do a release the following week!

Updated To do:

Modularize the drag and drop feature (load on demand)
handle dropping an event, half in the day range
styles fine-tuning
acceptance tests with all the other features
write documentation

@antoniandre thank you!

The first drag & drop on Vue Cal is now officially pre-released!  🎉🎉
Check out the documentation and examples:
https://antoniandre.github.io/vue-cal/#ex--edit-delete-create-events
https://antoniandre.github.io/vue-cal/#ex--drag-and-drop-in-details
https://codepen.io/antoniandre/pen/qBdmdoV
And also check the release notes: https://antoniandre.github.io/vue-cal/#release-notes
To install the alpha version on your machine and test it on your project:
npm i --S vue-cal@alpha

Please let me know all your feedbacks, it will help me to correct things, move on and release a stable version.
Thanks for your support!

@antoniandre great job! I hope I get the opportunity to try it out soon :)

Looks very promissing. I will try it out very soon as well. Is there support so that I can drag and drop something from somewhere else and drop it into a weekly calendar?
My usecase is that we have a list of courses for students, so they would be somewhere else on the screen. The day is divided into sections for example 8am to 10am, 11am to 2 pm and then a user should be able to pick Math from the list and then drop it at the 8am-10am section and the event should expand to fill the entire 8am to 10am section. Im hoping I will be able to this with these drag and drop functionalities you have implemented here.
I checked out the drag and drop things in your examples and they look good :-)

Thanks for your feedback @bjensen.
Dropping an external node is not supported right now but it shouldn't be too hard to develop and I will make it accept an HTML5 draggable DOM node.
I will work on that next after I release the stable version.
I just wait for a few other feedbacks first. :)

@antoniandre beers on us if you're ever in Sydney :)

Donated as promissed. Cant wait till you get around https://github.com/antoniandre/vue-cal/issues/174#issuecomment-593861869 :-)

Thank you @bjensen, very appreciated! :)
I am working on this feature at the moment and should release it soon.

More details about where I'm at

I have handled the drag and drop from external event to Vue Cal and I am now handling drag and drop between 2 Vue Cal instances.

After that I need to do some calculation when dropping an external event into Vue Cal to subtract the cursor position from the top of the event so that it lands exactly where you drop it.

Then I will release in the alpha and will prepare to release the stable version (still not on touch devices though).

Thanks everybody for your feedbacks on drag and drop and for trying the alpha!
This is very helpful to make it more stable and awesome! 😉

Hi @bjensen,
I have finished the external events drag & drop into Vue Cal and released in the alpha.
Please refer to this example: https://antoniandre.github.io/vue-cal/#ex--external-events-drag-and-drop
npm i --S vue-cal@alpha
Hope it helps! Let me know your feedbacks before I release the V3 stable.
I will release the V3 stable version end of next week!

Hi fellas,
I released the V3 yesterday: https://antoniandre.github.io/vue-cal/#release-notes.
The priorities have changed nowadays and I hope everybody's fine in this tough time.
But if that release can still help some users I'll be glad.
Cheer up fellas, this is not the end of the world yet! :rocket::rocket:

@bjensen, I hope the external events dragging was what you were looking for!
@ Everybody, I hope you enjoy the drag and drop feature!
I did put the touch device support in my backlog, but will start that later.
Closing the issue now!

I know this comes as a very late reply, but I had a break of programming as I was kind of ‘overworked and burned out’ I hope you are doing well and yes I tried the new things, and they are working as promised.
I looked at many things regarding calendars and one thing that always jumps out is how outlook (on the phone or online) has a very nice way of showing things and interact (I guess those guys are doing their job), especially how they ‘change times’ on an event, or how they show your events when you picked a date on the online version, is remarkable.
I hope you are doing well and healthy – Ronald Stevens
From: Antoni<EMAIL_ADDRESS>Sent: Thursday, March 12, 2020 6:28 PM
To: antoniandre/vue-cal<EMAIL_ADDRESS>Cc: Ronald Stevens<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [antoniandre/vue-cal] Drag and Drop feature! (#174)
Hi @bjensen https://github.com/bjensen ,
I have finished the external events drag & drop into Vue Cal and released in the alpha.
Please refer to this example: https://antoniandre.github.io/vue-cal/#ex--external-events-drag-and-drop
npm i --S vue-cal@alpha
Hope it helps! Let me know your feedbacks before I release the V3 stable.
I will release the V3 stable version end of next week!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/antoniandre/vue-cal/issues/174#issuecomment-598459977 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKP7SURFSKLDCX23AEA26BLRHFOXLANCNFSM4IXBOFEQ .  https://github.com/notifications/beacon/AKP7SUR7VVFCEOBOPO5GTJ3RHFOXLA5CNFSM4IXBOFE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOV4MSI.gif


"dotnet.exe vstest.console.dll testDllName.dll" always return with exitcode 1

Description
"dotnet.exe vstest.console.dll testDllName.dll" always return with exit-code 1
Steps to reproduce
run a .net core test with vstest.console runner.
Expected behavior
The process should exit with exit-code 0

What is the impact of this behaviour?

I tried with latest build and the behavior is as follows:
1) If all test pass "dotnet vstest.console testdll" will return 0.
2) If at least one  test fail"dotnet vstest.console testdll" will return 1.

and the above two behavior is expected.


C# [Signal] not exposed as GDScript Signal, kind of a bug.

Godot version
4.0.beta16.mono
System information
N/A
Issue description
[Signal] public delegate void SGEventHandler();
func a(): pass

func _run() -> void:
	var inst = load("res://CSharpSignalNotExposedAsGDScriptSignal/new_script.cs").new()
	inst.connect("SG", a) # This workds.
	inst.SG # deosn't work. Not a bug, but can it return a Signal ?
	inst.SGEventHandler # deosn't work.

Overall I think Signal is way better than using String. Also what about get_signal_connection_list() C# equivalent?
Had no time to check, I stayed up late today for a long time, I need to hurry to bed...
Steps to reproduce
N/A
Minimal reproduction project
godot.4.0.beta15.bugs.0.zip

Duplicate of https://github.com/godotengine/godot/issues/71348
Should be fixed by https://github.com/godotengine/godot/pull/71356 which will be part of beta 17.


F #3859: Monitor daemon HA

Force pushed new commit:

Address Vlasta's comment, vip.sh arguments are "leader/follower interface ip [interface ip ...]
squash all commits into one


Save Lottie Feature Support

Expose svg -> lottie
Expose enough of the drawing implementations that Godot Engine and V-Sekai can turn internal vector paths to lottie.

NOTE: Lottie is faster than SVG in thorvg even with a single frame image.

@fire does this works for you? https://lottiefiles.com/svg-to-lottie

I took a svg from the lottie site.

The limit makes it hard to use lottiefiles.

I see, for now, you can remove the unnecessary exisiting files in your workspace first. :-)

@fire please have a look, this is the most eaiest method so far:
https://lottie.new  -> drag&drop a svg -> export -> save -> download lottie json
https://github.com/thorvg/thorvg/assets/3711518/e4ea6547-5bf6-4d32-89e6-69fbb609bc46

Is there a way to do this programmatically? I want to generate Lottie json from svg file.

@iamtekeste No official(public) one yet afaik.

I will keep an eye out for new releases then!


Update Checkout Layout and JS behaviour

Expected behavior

I am trying to update this behavior in CornerStone templates.  I already created the issue but they told me to ask a question here.
https://github.com/bigcommerce/cornerstone/issues/2142
At the moment I can see the JS error in the console when there is no coupon available it.
Actual behavior
It shows the JS error log.
Steps to reproduce behavior
Add the items into cart and proceed to checkout page, and click 'Coupon/Gift Certificate' link.

I checked the template/pages/checkout.html but it has this code.
{{{ checkout.checkout_content }}}

How can I update the {{{ checkout.checkout_content }}}  and where is it?

any update on this?

Hey @skydev2020 is this still an issue? Also if I understand correctly the issue is the error console logs?


[Rust] Investigate if we can replace planus::ToOwned with TryInto

Our ToOwned trait maps each type to a single owned type, while TryInto has multiple possible outputs. Perhaps we can at least use the TryInto in our definition?

CC: #41


Configure Azure Pipelines

This configuration builds the application & produces  builds for both Debug and Release Configurations.

done


Normal Map doesn't flip properly with flip_h and flip_v in Sprite2D

Godot version
4.0 beta 10
System information
Windows 10, Vulkan Renderer
Issue description
In 2D scenes with sprites, when the sprite's flip_h and/or flip_v property is enabled, the normal map is flipped with the image, causing lighting to be reversed. While this does technically make sense, in a game where You have a bunch of sprites that flip and use normal maps, the only solution is to generate normal maps for both facing directions.

Ultimately the fix is simple: Invert the red channel in normal maps on horizontally flipped sprites, and invert the green channel on vertically flipped sprites.
Steps to reproduce

Create a Sprite2D
Add a Diffuse Texture and Normal Map
Add a 2D Light to the scene
Enable flip_h and/or flip_v on the Sprite2D

Minimal reproduction project
Normal not flipped.zip

Hi, I would Like to work on this issue.
I am quite new to contribute in Godot, but I have basic knowledge of OpenGL graphics and also Normal maps.
@Chaosus Can you please provide me with some tips on where to start for this issue ?

I guess you could look at scene/2d/sprite_2d.cpp first. Then it would lead you to canvas_item stuff. I'm not sure if it's an easy issue to fix.

Okay thanks for guiding. I will try and notify in 2-3 days if I will be able to do it or not.


Use cluster from https://github.com/giantswarm/cluster/pull/90

What this PR does / why we need it
Testing the cluster fairness fixes (https://github.com/giantswarm/cluster/pull/90) with cluster-aws

/run cluster-test-suites

Upgrades are still failing, will need more investigation.

In the upgraded control plane node, seems like the substitution is not done:
ip-10-0-84-150 ~ # cat /etc/kubernetes/manifests/kube-apiserver.yaml  | grep infl
    - --max-mutating-requests-inflight=${MAX_MUTATING_REQUESTS_INFLIGHT}
    - --max-requests-inflight=${MAX_REQUESTS_INFLIGHT}

But the setup-apiserver-environment.sh script run (the env file it generates is there, and it is called from /etc/kubeadm.sh:
ip-10-0-84-150 ~ # cat /etc/apiserver-environment
MAX_REQUESTS_INFLIGHT=266
MAX_MUTATING_REQUESTS_INFLIGHT=133
CPU_LIMIT=2550m
MEMORY_LIMIT=22Gi
CPU_REQUEST=1133m
MEMORY_REQUEST=15Gi
ip-10-0-84-150 ~ # cat /etc/kubeadm.sh
#!/bin/bash
set -e

envsubst < /etc/kubeadm.yml > /etc/kubeadm.yml.tmp
mv /etc/kubeadm.yml.tmp /etc/kubeadm.yml
echo "---" >> /etc/kubeadm.yml
cat /etc/kubelet-configuration.yaml >> /etc/kubeadm.yml
/opt/bin/setup-apiserver-environment.sh

kubeadm join --config /etc/kubeadm.yml
mkdir -p /run/cluster-api && echo success > /run/cluster-api/bootstrap-success.complete
mv /etc/kubeadm.yml /tmp/

In /tmp/kubeadm.yml I don't see the fairness options:
ip-10-0-84-150 ~ # cat /tmp/kubeadm.yml
---
apiVersion: kubeadm.k8s.io/v1beta3
controlPlane:
  localAPIEndpoint:
    bindPort: 6443
discovery:
  bootstrapToken:
    apiServerEndpoint: t-6hm6c3dmssj6zaisz0-apiserver-242077897.eu-west-2.elb.amazonaws.com:443
    caCertHashes:
    - sha256:71a5bd8684062618c6b3e13bad11b4883fd0a9ff352443e980884cc2a32bfe47
    token: aimy7g.75wo3kayhcpj83k7
kind: JoinConfiguration
nodeRegistration:
  imagePullPolicy: IfNotPresent
  kubeletExtraArgs:
    cloud-provider: external
    feature-gates: CronJobTimeZone=true
    node-ip: <IP_ADDRESS>
  name: ip-10-0-84-150.eu-west-2.compute.internal
  taints: null
---
apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
shutdownGracePeriod: 300s
shutdownGracePeriodCriticalPods: 60s
kernelMemcgNotification: true
evictionSoft:
  memory.available: "500Mi"
evictionHard:
  memory.available: "200Mi"
  imagefs.available: "15%"
evictionSoftGracePeriod:
  memory.available: "5s"
evictionMaxPodGracePeriod: 60
kubeReserved:
  cpu: 350m
  memory: 1280Mi
  ephemeral-storage: 1024Mi
kubeReservedCgroup: /kubereserved.slice
protectKernelDefaults: true
systemReserved:
  cpu: 250m
  memory: 384Mi
systemReservedCgroup: /system.slice
tlsCipherSuites:
- TLS_AES_128_GCM_SHA256
- TLS_AES_256_GCM_SHA384
- TLS_CHACHA20_POLY1305_SHA256
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_AES_256_GCM_SHA384
serializeImagePulls: false
streamingConnectionIdleTimeout: 1h
allowedUnsafeSysctls:
- "net.*"

And the two sed commands at the end of the script would've changed the settings if they were in /etc/kubeadm.yml:
ip-10-0-84-150 ~ # cat /opt/bin/setup-apiserver-environment.sh
#!/bin/bash
env_file="/etc/apiserver-environment"
[..]
# update /etc/kubeadm.yml with fairness values in case they are there
sed -i -e "s/max-requests-inflight:.*/max-requests-inflight: \"${max_requests_inflight}\"/" /etc/kubeadm.yml
sed -i -e "s/max-mutating-requests-inflight:.*/max-mutating-requests-inflight: \"${max_mutating_requests_inflight}\"/" /etc/kubeadm.yml

So I'm not sure where these settings are read during the upgrade process, or if during upgrades /etc/kubeadm.sh is not used at all.

/run cluster-test-suites

Timeout in the removal, all tests are ok!


[cherry-pick 2.1]  import,etc: implement a speed limit for tikv-importer (#4412)

What have you changed? (mandatory)
Cherry-picks #4412 to release-2.1 (needed for users with low network bandwidth).
What are the type of the changes? (mandatory)

New feature (change which adds functionality)

How has this PR been tested? (mandatory)
Cherry-picked from master
Does this PR affect documentation (docs) or release note? (mandatory)
No? The release note would be part of Importer.
Does this PR affect tidb-ansible update? (mandatory)
Yes, will be filed later.
Refer to a related PR or issue link (optional)
#4412.
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

/test
thread 'raftstore_cases::test_snap::test_server_concurrent_snap' panicked at 'called `Result::unwrap()` on an `Err` value: Other(StringError("[components/test_raftstore/cluster.rs:263]: can\'t get leader of region 1"))', libcore/result.rs:945:5

PTAL @Connor1996

LGTM


Use the new telemetry event conventions

Hey @whatyouhide,
This PR isn't ready to be merged yet since I wanted to get your feedback on it first. I've been working on adding APM support around redix. As part of that work I thought I would update the telemetry events based on the proposed convention: https://github.com/beam-telemetry/telemetry/issues/57. That convention isn't formalized so this might be premature. But I wanted to get the discussion started. My implementation would be a breaking change so I'm not sure how you'd like to handle that. An obvious solution is to continue to emit the old events alongside the new ones and users can adopt the new ones as needed.
Let me know what you think. If this seems like something you'd like to add I can work on finishing this up.

Hey @keathley, yeah, this all sounds great. We can release a breaking version, I don't think that's a problem :)

Sounds good. I'll get this cleaned up then. I need to figure out what the expectations are for errors that don't actually raise an exception. I believe that we're actually supposed to return a normal "stop" event. Which, seems pedantically correct, but also not altogether useful.

@keathley honestly I'm so happy there's a convention around this that I don't even care what the convention is 😄 Let's just do whatever The Convention™ ends up being. :)

Ok, this should be g2g now.

Thank you @keathley! 💟 I will update the docs and then in a bit I'll release a new breaking version. Are we fairly settled on these conventions? I'd love to avoid having to break stuff again.

I think at this point the convention is pretty well set. The only thing that would change is any additional metadata we'd want to emit with the events. But that would be a redix specific decision at this point.


ServiceBusTrigger: Could not load file or assembly 'Microsoft.Azure.ServiceBus'

Any thoughts on what might be causing this exception ?
Exception during runtime resolution of assembly 'Microsoft.Azure.ServiceBus, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7e34167dcc6d6d8c': 'System.InvalidCastException: [A]System.AppDomain cannot be cast to [B]System.AppDomain. Type A originates from 'System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' in the context 'Default' at location 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.0.0\System.Private.CoreLib.dll'. Type B originates from 'System.Runtime.Extensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' in the context 'Default' at location 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.0.0\System.Runtime.Extensions.dll'.
I have created a class library with .net Standard 2.0 and added 2 azure functions one for httpTrigger & other for serviceBusTrigger.
httpTrigger is working as expected however serviceBusTrigger is crashing with below error
ServiceBusTrigger.cs :
using Microsoft.Azure.ServiceBus;
namespace TriggerCore
{
public static class SBTrigger
{
static SBTrigger()
{
}
public static void Run(Message message)
{
}
}
}
function.json :
{
"bindings": [
{
"type": "serviceBusTrigger",
"queueName": "myqueue",
"accessRights": "manage",
"name": "message"
}
],
"disabled": false,
"scriptFile": "../TriggerCore.dll",
"entryPoint": "TriggerCore.SBTrigger.Run"
}
Microsoft.Azure.ServiceBus version 1.0.0
NetStandard.Library version 2.0.0

The new .NET Core runtime doesn't yet support ServiceBus trigger. See https://github.com/Azure/azure-webjobs-sdk/issues/1329

Cross post from https://github.com/Azure/azure-webjobs-sdk-script/issues/2014


Project Velocity visualization not showing all of the repos selected

When I search the Quay org, only about 50% of the repos appear on the plot.

when rendering quay/quayctl and containers/podman it's obviously the case that the graph knows about both datapoints, but podman isn't being rendered.

Not sure if I am fully following what is happening here, can you describe the problem further? One thing to note is that it seems like there has been more repos added to the org after our initial collection so they were not in augur. I triggered collection on them now so they should be in, confirming with @sgoggins that thatll mean they get added to the quay repo group as well

Update: There are a few things happening here

some projects arent collected on (triggered collection and talking with @sgoggins on collection delays)
some projects had 1 or more issue or pr actions as nan which was making the whole weighted set nan (pr in for that fix)
some did not have any issue or pr actions so they will not be plotted


Option to disable from Settings Editor

The current workaround is to disable in the Extension Manager

Another way is to set the thickness as 0 in the respective editor type (code cell, markdown cell, etc.). I think this should be good enough for most people.
Explicitly adding an on/off option would probably require substantial changes to the code. I can re-open if there is enough demand for this.


param: added retries on param fetch

on busy buses we will lose packets on SLCAN. This allows for up to 5
retries before we timeout the param fetch

looks like it retries 5 times over 1/2 a sec ( 0.1*5) ..?   if this works in-practice, it seems like an ok compromise. as the link gets more-an-more lossy, is this going to result in retries-spam as lots of things retrying fill the network more and make it worse for everyone...?

looks like it retries 5 times over 1/2 a sec ( 0.1*5) ..? if this works in-practice, it seems like an ok compromise

it does work in practice, and it is making my life much easier with 4 peripherals doing ESC telem on the bus. Otherwise I had to set ESC_BM and SRV_BM to 0 to fetch params


ensure that kbld.k14s.io/images annotations is deterministically ordered

to avoid unnecessary annotation changes

@cppforlife: I have a bit of time and I'm looking to contribute to more OS projects. Any objections if I have a go at this? It might also pair up with #18 quite well.

@jbrunton sounds good! it's all yours.

@cppforlife: Thanks for the merging the PR! Can this issue be closed now too?

@jbrunton i typically close all in-progress issues once they are included in a release. im planning to cut a new kbld version wed/thurs, so ill close it then.

included in https://github.com/k14s/kbld/releases/tag/v0.24.0


MAINT: Update deps

Separate dep updates and boilerplate _1 stuff from #168 and #173, and also make sure the installers build with the current stack

Ubuntu 18.04 keeps encountering an internal error, so I'm going to take this opportunity to try to switch 18.04, 20.40 -> 20.04, 22.04

@hoechenberger feel free to squash+merge without requirements being met, then we can change the requirements (remove 18.04 test, add 22.04 test)

FYI the 9.2.6 VTK thing we can probably undo once https://github.com/conda-forge/mayavi-feedstock/pull/73 is merged. We could wait to see and push that change here if we want...

Oh so VTK was the culprit! 🤦♀
Thanks for figuring that out!

Thanks @larsoner
Now let's iterate from here :)


Revert 1 dnm tx #664

@dnmTX by deleting your branch before the PR has been merged you closed the branch. Please restore the branch until it has been merged!

@funilrys  i think i got it but i'm not sure that it's needed.There are 3 identical commits here.


Cannot compile on Ubuntu 18.04

dave@bionic:~/tifig/build$ cmake ..
-- The C compiler identification is GNU 7.3.0
-- The CXX compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'libavcodec'
--   Found libavcodec, version 57.107.100
-- Checking for module 'libavutil'
--   Found libavutil, version 55.78.100
-- Checking for module 'libswscale'
--   Found libswscale, version 4.8.100
-- Checking for module 'vips-cpp'
--   Found vips-cpp, version 8.7.0
CMake Error at CMakeLists.txt:56 (add_subdirectory):
  The source directory

    /home/dave/tifig/lib/heif

  does not contain a CMakeLists.txt file.

CMake Error at CMakeLists.txt:57 (add_subdirectory):
  The source directory

    /home/dave/tifig/lib/cxxopts

  does not contain a CMakeLists.txt file.

-- Configuring incomplete, errors occurred!
See also "/home/dave/tifig/build/CMakeFiles/CMakeOutput.log".

Hi @phpdave11, maybe I can help you there: Have you checked out the submodules before building?
git submodule update --init


update API.md

There are some changes that haven't documented

Solved by https://graz.strange.love


Layered docker image

https://spring.io/blog/2020/01/27/creating-docker-images-with-spring-boot-2-3-0-m1

https://github.com/jonashackt/spring-boot-buildpack

https://spring.io/guides/topicals/spring-boot-docker/


Consider using a better maintained shellscript grammar

Please search existing issues to avoid creating duplicates.

Duplicate of locked https://github.com/microsoft/vscode/issues/40956 , which redirected the discussion to https://github.com/atom/language-shellscript/issues/100 , where I was told it's no longer their problem:

VSCode is still using the old TextMate grammar, which the Atom team no longer maintains as we have moved many grammars (including this one) over to Tree-sitter.

·

Also please test using the latest insiders build to make sure your issue has not already been fixed:

Can't do that right now, maybe next week. In case it was really fixed, please consider this issue as a request to annotate the locked thread with updated info.

VSCode Version: 1.36.1
OS Version: Ubuntu 16.04 LTS (xenial)

Steps to Reproduce:

Create a bash file moo.sh:

#!/bin/bash
nl <(sed -nre 's!^\s+!!p' <<'  __FOO__'
  ########################
  ## Dummy Message      ##
  ########################
  __FOO__
  )
echo bar

Compare with my screenshot.
Run it and observe that bash considers "echo" a command of its own.
Unident __FOO__ to see the flipside of this bug: VSCode now thinks everything is ok.
Run again, see that in reality, unindenting broke it:

./moo.sh: line 2: unexpected EOF while looking for matching `)'
./moo.sh: line 9: syntax error: unexpected end of file

Does this issue occur when all extensions are disabled?: Yes

Leaving open to check on if we decided to update the old shell script grammar.

Probably the same issue here. I have an intended Heredoc whose delimiter isn't recognized correctly because of indentation. Although I'm using the <<- syntax as stated in man bash

If the redirection operator is <<-, then all leading tab characters are stripped from input lines and the line containing delimiter. This allows here-documents within shell scripts to be indented in a natural fashion.

if true; then
    cat <<-'EOF' > /tmp/file
        # My script here
    EOF
fi

Which version of bash would I need to have your syntax accepted? For comparison, here's what my bash expects.

Sorry for my wrong gist a moment ago. I then noticed it's limited to tabs.

I have found that it seems to break with the standard EOF too:
echo "here is some $SYNTAX coloring"
cat << EOF > myfile.txt
multiple line
output into
a file
EOF
echo "here is some more $SYNTAX coloring"

As you can see, this works on Github itself. While it works here, this breaks in VSCode:

Related: https://github.com/microsoft/vscode/issues/102958 (Wrong syntax highlighting when using . in regex inside HEREDOC)

Hi,
Please consider that type of code too (var=` ... )
#!/bin/sh
if [ -d "$directory" ]
    then
# syntax broken after
        mount_script=`/usr/bin/osascript <<EOF
            tell application "Finder"
            activate
            mount volume "smb://$myshare"
            end tell
            EOF`
    else
        echo blah
fi
echo another code here
exit 0

The script is running but it's a pain to working on it (the real one counts ~400 lines). The only fix I found (during script editing only) is to move "EOF`" at the very begin of the line AND remove the ending "`" char.
#!/bin/sh
if [ -d "$directory" ]
    then
        mount_script=`/usr/bin/osascript <<EOF
            tell application "Finder"
            activate
            mount volume "smb://$myshare"
            end tell
EOF
    else
        echo blah
fi
echo another code here
exit 0

Despite the coloration is broken, VSCODE  is correctly find  the <<EOF .... EOF delimiters as it highlights the both when I select one.
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:30:02.420Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz (4 x 2200)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 3

Memory (System)
8.00GB (0.08GB free)

Process Argv
--crash-reporter-id 81a3ae87-315d-47fd-b117-7193c28612c0

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

xml
Dot
2.5.1

shell-format
fox
7.0.1

bash-extension-pack
liz
0.0.4

shellman
Rem
4.9.0

bash-debug
rog
0.3.9

shebang-snippets
rpi
0.1.4

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221877
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30211402
wsl2prompt:30224612
vstry914:30244301
pythonvsdeb440:30242242
unusedpromptcf:30224611
folderexplorercf:30224615
openfilemenu:30224647
pythonvsded773:30236629
pythonvspyt600:30241727

Hi,
Please consider that type of code too (var=` ... )
#!/bin/sh
if [ -d "$directory" ]
    then
# syntax broken after
        mount_script=`/usr/bin/osascript <<EOF
            tell application "Finder"
            activate
            mount volume "smb://$myshare"
            end tell
            EOF`
    else
        echo blah
fi
echo another code here
exit 0

The script is running but it's a pain to working on it (the real one counts ~400 lines). The only fix I found (during script editing only) is to move "EOF`" at the very begin of the line AND remove the ending "`" char.
#!/bin/sh
if [ -d "$directory" ]
    then
        mount_script=`/usr/bin/osascript <<EOF
            tell application "Finder"
            activate
            mount volume "smb://$myshare"
            end tell
EOF
    else
        echo blah
fi
echo another code here
exit 0

Despite the coloration is broken, VSCODE  is correctly find  the <<EOF .... EOF delimiters as it highlights the both when I select one.
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:30:02.420Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz (4 x 2200)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 3

Memory (System)
8.00GB (0.08GB free)

Process Argv
--crash-reporter-id 81a3ae87-315d-47fd-b117-7193c28612c0

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

xml
Dot
2.5.1

shell-format
fox
7.0.1

bash-extension-pack
liz
0.0.4

shellman
Rem
4.9.0

bash-debug
rog
0.3.9

shebang-snippets
rpi
0.1.4

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221877
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30211402
wsl2prompt:30224612
vstry914:30244301
pythonvsdeb440:30242242
unusedpromptcf:30224611
folderexplorercf:30224615
openfilemenu:30224647
pythonvsded773:30236629
pythonvspyt600:30241727

In this script $variable1 and $variable2 should have the same color as other variables. And /filename should have the same color as it would in echo text > $variable/filename. Currently it all has the same color as the body of the HEREDOC.
cat <<- HEREDOC > $variable1/filename
  text="some=$variable2"
HEREDOC

One more to add to the list of issues with bash syntax highlighting:

Code:
header <wine-pca.txt -a pc1,pc2 |
	paste -d, - <(xsv select type wine-scaled.csv) |
	tee wine-pca.csv | csvlook

All codes after this command lose syntax highlighting (shown as the same color as comments).

Another more current example:

Version: 1.68.0
Commit: 4af164ea3a06f701fe3e89a2bcbb421d2026b68f
Date: 2022-06-08T11:49:57.055Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-117-generic

That seems an issue with the select in the string, it seems to (wrongly) mess things up.
It happens even here in github:
function get_source() {
    if [[ -z ${RTM_TPL_SOURCE-} ]]
    then
        RTM_TPL_SOURCE="$(a select b c)"
        export RTM_TPL_SOURCE
    fi
    verbose_print "RTM source: ${RTM_TPL_SOURCE}"
}

@alexr00 not sure if this helps or is noise, but it appears the only bash language server implementation points to the tree-sitter grammar for bash.
That grammar repository does appear to be maintained, but there would appear to be some setup required to test if that resolves the issues reported here.
Its not clear to me what additional VSCode setup would be required.

Is there a reason why variables with and without curly braces are not treated the same? (see screenshot from v1.70.2, using the Dark+ color scheme)

@alexr00 over the last week (in response to this) I cleaned up the better shell syntax and stablized it.
@people-on-this-thread please do install/test the extension. It should ready for VS Code insiders, but it'd be nice to get some feedback to confirm there are no regressions. There's known bugs, but currently no known regressions.
https://github.com/microsoft/vscode/issues/156054 is already fixed
https://github.com/microsoft/vscode/issues/152327 is already fixed
https://github.com/microsoft/vscode/issues/166905 is already fixed
https://github.com/microsoft/vscode/issues/139913 is already fixed (hi @lilyball 👋 , good to see you outside nix)
https://github.com/microsoft/vscode/issues/147293 is already fixed
The select issue mentioned a few comments above is fixed
https://github.com/microsoft/vscode/issues/147673 is not
https://github.com/microsoft/vscode/issues/77675 (code example at top of this issue) is not

The new grammar has been in VS Code insiders for 3 weeks with no issues reported. Closing as fixed!


animatedStyle might be null, causing crash

I updated to react-navigation 3 and have a crash. Don't know exactly the situation that causes this, but the bug is clear in the code.
Here it creates a style variable that might be false: https://github.com/react-navigation/react-navigation-stack/blob/master/src/views/StackView/StackViewLayout.js#L810-L818
It then passes it down to the Card component as the animatedStyle prop: https://github.com/react-navigation/react-navigation-stack/blob/master/src/views/StackView/StackViewLayout.js#L836
In Card, it assumes animatedStyle is an object and destructures it: https://github.com/react-navigation/react-navigation-stack/blob/master/src/views/StackView/StackViewCard.js#L45-L49
Locally I fixed by making it default to an empty object, not sure what you want to do.

This seems like a fairly major issue? Or is screenInterpolator usually not null? I'm not sure why it is in my case, but I have a fairly complex setup. Has anyone read my issue above? I can open a PR, should be a quick fix just tell me which side to do it on (default to empty object where it uses screenInterpolator?)

hey @jlongster! ah the beauties of working in an untyped codebase sometimes :P thanks for the investigation, will fix this for you shortly

used the same fix you made locally and released 3.0.4. it is indeed valid for screenInterpolator to be null but that is usually not the case, I hadn't considered that but I can see not why you might want to do it.

Awesome, thanks!


New version: Geany.Geany version 1.38.0

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114487&drop=dogfoodAlpha

Close with reason: Duplicate of PR 113802;


[5.9] Remove Mandrill and SparkPost mail drivers

We're removing these drivers because we feel that general interest in these is declining and these aren't used by any of Laravel's core services themselves. We're encouraging the community to release packages for these if there's any interest in continued use of them.

Ok, why not. But from what I see of Illuminate\Mail\TransportManager the list of available drivers is hard coded and there is no method to register new ones. How do you recommend someone makes a package to add extra drivers then? Extend the TransportManager class?

@CyrilMazur: it extends Illuminate\Support\Manager which basically allows you to extend with any driver you wish to create.

@driesvints  ok thanks found it https://github.com/laravel/framework/blob/5.8/src/Illuminate/Support/Manager.php#L87-L89
This would deserve to be mentioned in the doc, apparently it was long time ago (https://laravel.com/docs/5.0/extending) and then deleted 😶

@cyrilmazur feel free to send in a pr!

MailGun is not a transparent service. They banned their service for some countries like Iran. Sad to hear that you have removed SparkPost which is more transparent and dedicated to FOSS principle.

This is disappointing. None of the mail services are actually used by the framework, why not remove them all? Stick them in a @laravelmail type repo and open that up for PRs?
I'm not a fan of installing a 40 line 8 star github package to my app, we'll likely have to make a mandrill plugin on our own to avoid this. Community drivers dont often get the scrutiny official drivers do, dont update as fast, get patched with security fixes, etc.
I also wonder how you measured that interest was declining in these drivers? We're not sending analytics back to Laravel are we?
Thanks.


SAK-30251 syllabus add item was not posting content.

Bug seems to have been introduced in SAK-29988
/CC: @bjones86 @willkara

+1, thanks @ottenhoff for the quick fix

Awesome, nice catch.


[release-1.7] Avoid duplicate HTTP headers for istio-proxy probe requests

This is an automated cherry-pick of #28537

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio_release-1.7
bef266d43c39681375b845a36187b004dfb7741f
link
/test integ-multicluster-k8s-tests_istio_release-1.7

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

/retest

Added a release note, fixes https://github.com/istio/istio/issues/28466

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

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
fd93b390a23ee5578a10d7869b74468e451fda91
link
/test unit-tests_istio_release-1.7

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

/retest

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

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
fd93b390a23ee5578a10d7869b74468e451fda91
link
/test unit-tests_istio_release-1.7

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

/retest

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio_release-1.7
fd93b390a23ee5578a10d7869b74468e451fda91
link
/test integ-telemetry-k8s-tests_istio_release-1.7

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

/retest


Set capability from CLI with dot inside (jenkins.nodeName)

Hi there!
I'm trying to pass jenkins.nodeName capability from CLI , I need it to specify Selenium Node from
https://wiki.jenkins.io/display/JENKINS/Selenium+Plugin
protractor  --capabilities.jenkins.nodeName=JenkinsMacbook gives me capability
 capabilities:     { browserName: 'chrome',      jenkins: { nodeName: 'Jenkins-Macbook' },      count: 1 },
But I would like to get something that I can achieve in protractor.conf.js by
  capabilities: {     browserName: 'chrome',     "jenkins.nodeName":'JenkinsMacbook'   },
what gives me correctly
capabilities:     { browserName: 'chrome',      'jenkins.nodeName': 'Jenkins-Macbook',      count: 1 },

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow
(use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!


Delayed::Job failure: Event 'mark_aged_out' cannot transition from 'delivered'

bundle exec bin/rails console
puts Delayed::Job.where('failed_at IS NULL').last.last_error
...
Event 'mark_aged_out' cannot transition from 'delivered' ...

Possible race condition? Something is trying to mark a delivered ScheduledMessage as aged_out? The logic in deliver_and_save_if_possible might need a reversal, to check too_old_to_deliver first instead of falling through the delivery?

Looks like these failures are transitory, it went away while I looked at it. Heisenbug!

That's the thing I've seen before. We just don't want to mark a delivered message as aged_out? Is there a way a message could be scheduled for delivery more than once?

https://github.com/uwmadison-chm/hedonometer/blob/9e23b13c634f4c35db50ae69085fe43a238212d4/app/models/scheduled_message.rb#L83
I think that's getting called on a ScheduledMessage that's already delivered, somehow... so maybe that logic should just return if delivered? at the top?

Yes, that would be good.
Wow, that elsif not self.schedule_day.participant.active? is not my most shining line of code


Dependabot PR description lists updates for packages that aren't allowed

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
nuget
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
https://github.com/newrelic/newrelic-dotnet-agent/blob/main/.github/dependabot.yml#L28 -- refer to the the nuget-tests group starting at line 28
Updated dependency
No response
What you expected to see, versus what you actually saw
Observed behavor
We have an allow list that permits a small subset of Nuget packages to be updated.
On multiple occasions recently, the description in the PR created by Dependabot lists one or more "disallowed" packages as being included in the update, even though there are no changes to the actual manifest (.csproj) files for the disallowed packages.
Specific packages shown in the description include System.Net.Http, System.Collections.Immutable,
The PR itself updated exactly what it should have, based on the allow list; the issue is in the PR description itself.
Expected behavior
Disallowed packages should not appear in the description of Dependabot PRs
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Recent Dependabot PRs exhibiting this behavior:
https://github.com/newrelic/newrelic-dotnet-agent/pull/2746
https://github.com/newrelic/newrelic-dotnet-agent/pull/2780
Both of these list System.Net.Http and Sytem.Collections.Immutable in the description, but there (correctly) not updated in the PR.
https://github.com/newrelic/newrelic-dotnet-agent/pull/2702 -- this one listed a whole bunch of packages in the description, but the only package actually updated was Microsoft.NET.Test.Sdk, which is on the allow list.
Smallest manifest that reproduces the issue
No response

Thanks for filing the issue.  It'll require some investigation to see exactly what happened because the allow list in the dependabot.yml file should have prevented the System.Net.Http, etc. packages from even being attempted.


Python Function App show only 6 operations

What is the maximum number of operations a Python function app using a Linux consumption plan can have? We deployed a function app last friday that has 37 operations. But only 6 are shown in the Azure Portal for the function app in question. We do see output for all 37 operations in Application Insights though.
I can't find any information about this in the documentation.

This is a stale issue, feel free to open a new issue if you run into it again.


Fix the bottom part of the website

The recent changes that some one tried to copy a chatbot and scroll animation from some other place has messed up the bottom of the website.
I would like to fix that

I would fix it like it previously was

@Anupkjha2601 Please assign this issue as it is quite important


Implementation of BoxBound function of message API

Implement unimplemented BoxBound function.

This issue has been resolved in v1.4.6.


Allow configuring kubetruth through CloudTruth parameters/templates

Make it easier to change its behavior at runtime without having to reinstall the helm chart

Using CRDs instead


Kofta: Display dates according to the users 'cultural convention'

Reading American dates is very confusing, they should be displayed according to the language the website is beeing accessed in.

Additionally automatically switching between 12H and 24H format would be helpful.

Issure #600 nice number lbh


add conduit version check for new polytopal support

Description
Resolves CI Compilation issue by adding a guard for new conduit features.

[x] Bug fix
[ ] New feature
[ ] Documentation update
[ ] Other

How Has This Been Tested?
Compiled on my mac, will test in CI.
Checklist:

[x] I have followed the style guidelines of this project.~~
[x] I have performed a self-review of my own code.~~
[x] I have commented my code where applicable.~~
- [ ] I have updated the release notes.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added debugging support to my changes.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] I have confirmed new and existing unit tests pass locally with my changes.
- [ ] I have added new baselines for any new tests to the repo.
[x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~
[x] I have assigned reviewers (see VisIt's PR procedures for more information).~~

Oh, I didn't have ignore whitespace checked. Anyone know a way to make that default?

re: whitespace, they are indented, so I expect them to all change whitespace.
Not sure how to change settings in github.

Note: we also need this on the RC.


Font renders weird

Issue Type: Bug
After updating to the latest insiders release, this is how the font (blackfont) looks:

VS Code version: Code - Insiders 1.29.0-insider<PHONE_NUMBER>96bc1f36c83d70f208b7fd85afc86b, 2018-10-15T05:17:12.673Z)
OS version: Windows_NT ia32 10.0.18252

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4590S CPU @ 3.00GHz (4 x 2993)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.93GB (7.78GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

gitkit
alb
0.1.1

Bookmarks
ale
9.1.0

vscode-database
baj
1.5.2

vscode-intelephense-client
bme
0.8.8

gitignore
cod
0.5.0

bracket-pair-colorizer
Coe
1.0.60

vscode-eslint
dba
1.6.0

xml
Dot
2.3.2

gitlens
eam
8.5.6

php-debug
fel
1.12.6

auto-rename-tag
for
0.0.15

mediawiki
jak
2.1.0

php-cs-fixer
jun
0.1.85

vscode-scss
mrm
0.6.2

cpptools
ms-
0.19.0

debugger-for-chrome
msj
4.10.2

php-docblocker
nei
1.6.0

vscode-icons
rob
7.27.0

Align
ste
0.2.0

html-css-class-completion
Zig
1.17.1

(1 theme extensions excluded)

I cannot get this to reproduce in this build.  What theme are you using?

Visual studio dark
On Mon, Oct 15, 2018 at 3:51 PM Scott Craig<EMAIL_ADDRESS>wrote:

I cannot get this to reproduce in this build. What theme are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/60965#issuecomment-429858189,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0H6Ic7hgZqHidhVtatQbYOJaKLlDziks5ulJLOgaJpZM4XcNa-
.

Can you share your settings.json file?

This is still not fixed. I reduced it to this settings.json:
{     "editor.fontFamily": "source code pro",     "editor.fontSize": 15 }


feat: update identity payout address

Allow Masternode/Evonode Identities to update their payout address using opened Wallet(s)

Summary by CodeRabbit
Release Notes

New Features

Introduced a new screen for updating payout addresses within the identities section.
Added a button labeled "Update Payout Address" in the identities table to access the new functionality.
Enhanced task management capabilities to process ProRegUpdate transactions.

Bug Fixes

Improved handling and display of error messages related to payout address updates.

Documentation

Updated module structure to include the new update_identity_payout_address module for better organization.

The button is way too big 😄

This will only work for MNs that have their owner key in Dash Core (vs DMT) and in the specific wallet they connect to DET, correct?

This will only work for MNs that have their owner key in Dash Core (vs DMT) and in the specific wallet they connect to DET, correct?

@thephez Correct!


Can't find file VOC2012/ImageSets/Segmentation/list/train_aug.txt

Seems the code tried to find file VOC2012/ImageSets/Segmentation/list/train_aug.txt. But I can't find this file in my VOC2012 trainval or test set. Should I download it elsewhere?
Traceback (most recent call last):   File "./script.py", line 60, in <module>     seed_train(control, conf)   File "src/seed/train.py", line 152, in main     solver = load_solver(control, control_token, conf)   File "src/seed/train.py", line 141, in load_solver     solver = caffe.SGDSolver(solverproto)   File "lib/caffetools/datalayers.py", line 22, in setup     self.batch_loader = BatchLoader_PASCAL(params)   File "lib/caffetools/datalayers.py", line 57, in __init__     self.pascal_split)   File "lib/pascaltools/io.py", line 32, in get_pascal_indexlist     pascal_tmp_list = [line.rstrip('\n') for line in open(pascal_list_file)] IOError: [Errno 2] No such file or directory: '/disk2/zhangyu/data/VOCdevkit/VOC2012/ImageSets/Segmentation/list/train_aug.txt'

Hi, thanks for finding this out.
train_aug.txt is basically from the following link
http://home.bharathh.info/pubs/codes/SBD/download.html
It's a standard training set for many Pascal semantic segmentors.
I've updated the repository so that you only need to run the updated version of download.sh -- it should download train_aug.txt and put it in the correct location (you should specify the PASCALROOT in the script though).
Let me know if there are further problems.


tensorflow-gpu: Could not load dynamic library 'libcudart.so.10.1'

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

import tensorflow as tf
print("Num GPUs Available: ", len(tf.config.experimental.list_physical_devices('GPU')))

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ArchLinux 64bits
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): tensorflow-gpu 2.2.0rc4
Python version: 3.8.2
CUDA/cuDNN version: 10.2.89-5 (from Archlinux repo)

Describe the problem
TensorFlow doesn't use my GPU because there is a bug while trying to load "libcudart.so.10.1". My system has libcudart.so.10.2 installed
All the other libraries load fine since they look for libcu***.so.10 and not 10.1
Source code / logs
Python 3.8.2 (default, Apr  8 2020, 14:31:25)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
>>> print("Num GPUs Available: ", len(tf.config.experimental.list_physical_devices('GPU')))
2020-05-03 22:17:42.422067: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-05-03 22:17:42.471297: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-05-03 22:17:42.472040: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:09:00.0 name: GeForce GTX 1080 Ti computeCapability: 6.1
coreClock: 1.683GHz coreCount: 28 deviceMemorySize: 10.91GiB deviceMemoryBandwidth: 451.17GiB/s
2020-05-03 22:17:42.472169: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcudart.so.10.1'; dlerror: libcudart.so.10.1: cannot open shared object file: No such file or directory
2020-05-03 22:17:42.473728: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2020-05-03 22:17:42.475267: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2020-05-03 22:17:42.475499: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2020-05-03 22:17:42.477078: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2020-05-03 22:17:42.478053: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2020-05-03 22:17:42.481446: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-05-03 22:17:42.481478: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1598] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
Num GPUs Available:  0

Here is the CUDA lib I have installed:
/opt/cuda/doc/man/man7/libcudart.7
/opt/cuda/doc/man/man7/libcudart.so.7
/opt/cuda/targets/x86_64-linux/lib/libcudart.so
/opt/cuda/targets/x86_64-linux/lib/libcudart.so.10
/opt/cuda/targets/x86_64-linux/lib/libcudart.so.10.2
/opt/cuda/targets/x86_64-linux/lib/libcudart.so.10.2.89
/opt/cuda/targets/x86_64-linux/lib/libcudart_static.a

@gillouche
To use CUDA 10.2 with Tensorflow 2.2. Please build the Tensorflow from source.
Follow the instructions mentioned here. And also take a look at this comment.Thanks!

Hi @ravikyram
will the next release of tensorflow-gpu on pypi support CUDA 10.2 ? If so, I guess that I can wait a little bit. I wanted to have everything installed properly in a virtual environment (requirements.txt) so I don't want to build it myself.
The python tensorflow cuda package on Arch repository is 2.2.0rc3-2 which shouldn't be compatible either with the CUDA 10.2 version installed from Arch repository. I'll try tonight, maybe they did something to fix the compatibility issue.
Thanks for your help.

Okay I tried and Archlinux does indeed fix the issue with the package tensorflow-cuda. I'll keep using that and not tensorflow-gpu with pip. Thanks!

It seems that libcudart 10.1 and 10.2 are compatible. I was able to hack this on Ubuntu 20.04 by providing a symlink as mentioned by others and run tensorflow 2.2 with libcudart 10.2 (without building from source, just the symlink from a fake library). This may help:
https://github.com/tensorflow/tensorflow/issues/38194#issuecomment-629801937

meet this problem when using tensorflow2.2 with cuda10.2. Solved by ln -s
sudo ln -s /usr/local/cuda-10.2/targets/x86_64-linux/lib/libcudart.so.10.2 /usr/lib/x86_64-linux-gnu/libcudart.so.10.1

"sudo ln -s /usr/local/cuda-10.2/targets/x86_64-linux/lib/libcudart.so.10.2 /usr/lib/x86_64-linux-gnu/libcudart.so.10.1"
It works. Thank you stdcoutzyx.

sudo ln -s /usr/local/cuda-10.2/targets/x86_64-linux/lib/libcudart.so.10.2 /usr/lib/x86_64-linux-gnu/libcudart.so.10.1
didn't work

sudo ln -s /opt/cuda/targets/x86_64-linux/lib/libcudart.so.10.2 /usr/lib/libcudart.so.10.1
worked for me.

I'm having this message with cuda 11 installed. As I know cuda 11 should be backward compatible with everything using cuda 10. Does it have any negative effects? It also shows "Ignore above cudart dlerror if you do not have a GPU set up on your machine."

I'm having this message with cuda 11 installed. As I know cuda 11 should be backward compatible with everything using cuda 10. Does it have any negative effects? It also shows "Ignore above cudart dlerror if you do not have a GPU set up on your machine."

I am facing the same problem. Even Cuda 11 successfully working but tensorflow 2.3 looking cuda 10.1

I'm having this message with cuda 11 installed. As I know cuda 11 should be backward compatible with everything using cuda 10. Does it have any negative effects? It also shows "Ignore above cudart dlerror if you do not have a GPU set up on your machine."

I am facing the same problem. Even Cuda 11 successfully working but tensorflow 2.3 looking cuda 10.1

Same Here. Pytorch is working fine with GPU's. But getting errors with tensorflow.

I'm having this message with cuda 11 installed. As I know cuda 11 should be backward compatible with everything using cuda 10. Does it have any negative effects? It also shows "Ignore above cudart dlerror if you do not have a GPU set up on your machine."

I am facing the same problem. Even Cuda 11 successfully working but tensorflow 2.3 looking cuda 10.1

Same problem and I solved it by uninstall tensorflow 2.3, and install tensorflow-gpu 2.0.0.
Before that, I tried to add path of cuda 11, and also use latest tf-nightly-gpu but they didn't work.

meet this problem when using tensorflow2.2 with cuda10.2. Solved by ln -s
sudo ln -s /usr/local/cuda-10.2/targets/x86_64-linux/lib/libcudart.so.10.2 /usr/lib/x86_64-linux-gnu/libcudart.so.10.1

thank you, this works for me (tensorflow2.2 with cuda10.2)

If you are using conda to manage your envs, just specify the cuda env when installing tensorflow. This way you can keep cuda 11 installed, and still run tf with an old cuda version.
conda install tensorflow-gpu cudatoolkit=10.1

Okay I tried and Archlinux does indeed fix the issue with the package tensorflow-cuda. I'll keep using that and not tensorflow-gpu with pip. Thanks!

how do you make to do python find tensorflow-cuda? I installed that metapkg but python says that there is no tensorflow installed

Okay I tried and Archlinux does indeed fix the issue with the package tensorflow-cuda. I'll keep using that and not tensorflow-gpu with pip. Thanks!

how do you make to do python find tensorflow-cuda? I installed that metapkg but python says that there is no tensorflow installed

Are you using the python3 interpreter or another version installed from AUR (python3.6, python3.7, ...) ? You also have the package python-tensorflow-cuda. I am not sure about the differences between all the tensorflow packages in arch repo.

Okay I tried and Archlinux does indeed fix the issue with the package tensorflow-cuda. I'll keep using that and not tensorflow-gpu with pip. Thanks!

how do you make to do python find tensorflow-cuda? I installed that metapkg but python says that there is no tensorflow installed

Are you using the python3 interpreter or another version installed from AUR (python3.6, python3.7, ...) ? You also have the package python-tensorflow-cuda. I am not sure about the differences between all the tensorflow packages in arch repo.

I'm using tensorflow-cuda and python3, the ofictal rep version and python doesn't detect tensorflow.

Okay I tried and Archlinux does indeed fix the issue with the package tensorflow-cuda. I'll keep using that and not tensorflow-gpu with pip. Thanks!

how do you make to do python find tensorflow-cuda? I installed that metapkg but python says that there is no tensorflow installed

Are you using the python3 interpreter or another version installed from AUR (python3.6, python3.7, ...) ? You also have the package python-tensorflow-cuda. I am not sure about the differences between all the tensorflow packages in arch repo.

I'm using tensorflow-cuda and python3, the ofictal rep version and python doesn't detect tensorflow.

I tried python-tensorflow-cuda and the other problem is no more but now I have a memory problem with a really tiny NN and little data with a 3070 when that NN was trained first by a 970, I understand nothing :(

ln -s /usr/local/cuda-11.0/targets/x86_64-linux/lib/libcudart.so.11.0.221 /usr/lib/x86_64-linux-gnu/libcudart.so.10.1

currently it is working, I'm using the arch tensorflow pkg

If you are using conda to manage your envs, just specify the cuda env when installing tensorflow. This way you can keep cuda 11 installed, and still run tf with an old cuda version.
conda install tensorflow-gpu cudatoolkit=10.1

Thx, this works for me. CUDA 11.0 + python 3.8

i have same issue,  @ioannist try this  conda install tensorflow-gpu cudatoolkit=10.1
but still same issue

conda install tensorflow-gpu cudatoolkit=10.1

Thanks!

sudo ln -s /opt/cuda/targets/x86_64-linux/lib/libcudart.so.10.2 /usr/lib/libcudart.so.10.1
worked for me.

It worked for me


Add new Haskell linter

This PR adds a new Haskell linter (based on GHC). As such, it can take advantage
of the pre-existing HandleGHCFormat function. Also, we update the docs.

Add stack-build linter for Haskell
The stack-build linter works better than the other two linters when you're
working with an entire Haskell project. It builds the project entirely and
reports any errors.
The other two Haskell GHC linters only work on single files, which can
result in spurious errors (for example, not being able to find imports).

Document all available Haskell linters

After looking at it a little longer, I realized that the stack-ghc-mod linter is actually more in line with what I was going for:

uses stack to correctly resolve project dependencies
just checks the file, instead of actually building the whole thing like stack-build does.

That being said, I think it's valuable to have both. stack-ghc-mod requires an extra dependency (ghc-mod). stack-build has the nice side effect of also building your project (you can imagine that people might want to build their project on save). And above all, keeping stack-build has minimal maintenance cost, because it re-uses HandleGHCFormat.
TL;DR: stack-ghc-mod is more of what I wanted, but stack-build is still fine to add the new stack-build linter.

Will this generate binary files? That may surprise and annoy people.

Yes, this will. My reasoning why it wasn't a huge deal was that

Stack's "big idea" is reproducible builds. Running stack build is as close to idempotent as you can get.
ALE is async. Even if the code generation takes a long time, at least it's not blocking the UI.
stack-build provides a nice alternative to stack-ghc and stack-ghc-mod in that it requires no external dev tools and works with an entire project.

Unfortunately, there's no support with stack to just typecheck: commercialhaskell/stack#977.
What do you think? Is it annoying enough that we shouldn't include it? Could we make it opt-in as opposed to on by default?

Should be ready for round 2, thanks!

I will summon Haskell users who have commented before.
@wizzup @azure-satellite @parsonsmatt @jwoudenberg @WhiteAbeLincoln @habibalamin Does anyone mind if a Haskell linter generates binary files?

As long as it's stored in an OS-provided tempfolder, cleaned up ASAP, and is space-efficient (depending on the program being linted), I wouldn't mind too much. However, I also don't know if I should mind.
However, I'm not sure how a project-level linter would work when embedded in a text editor. Is it necessary to have? What can it do that a file-level linter can't?

Actually, forget about storing it in a tempfolder. If it just builds the project in the same location stack build normally does, it shouldn't be an issue. I just don't want any stray copies of the built project laying around, but if it's building where I'm building, I'm okay with it.

If it builds into the regular build directory, which it should do, then it'll probably be fine.

I don't have any objections, but someone more knowledgeable than me may is where I'll leave it. I'm happy with this PR being merged.

I'll merge this, and let people try it.

Cheers! :beers:

This looks great to me! Running build is pretty typical. The only suggestion I would make is using --fast to build without optimizations, which is about twice as fast on my work project.

@jez Do you want to try using --fast? Sounds like a good idea.

Good idea. Added in #754.


Adding example for creating service accounts for VM instances

Planning to use on this page:
https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances

@betsy-lichtenberg
Thanks for the PR! 🚀
Unfortunately it looks like some of our CI checks failed. See the Contributing Guide for details.

⚠check_whitespace
Failed whitespace check. More details below.

Checking for trailing whitespace
./compute/service_account_for_instances/main.tf:12: * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
Error: Trailing whitespace found in the lines above.
Checking for missing newline at end of file

@betsy-lichtenberg
Thanks for the PR! 🚀✅ Lint checks have passed.

@betsy-lichtenberg
Thanks for the PR! 🚀✅ Lint checks have passed.

@betsy-lichtenberg
Thanks for the PR! 🚀✅ Lint checks have passed.

@betsy-lichtenberg
Thanks for the PR! 🚀✅ Lint checks have passed.

This LGTM at a high level, but maybe someone from @rsamborski's team should review.

Ace gave it an LGTM offline, so I'm merging this.


General Improvements

When doing a brief review of the current version of the software I noticed the following which should be the source of future work and may need their own issues in future:

[X] The software crashes if you don't pick a file on the load inputs dialog.
[X] The software crashes if there isn't a "results" directory in the directroy from which you load the input file. This is not robust so checking needs to be added an the user informed that they need to create the directory or else the software can try create it itself.
[x] The output directory path is availble in various places in the GUI but can readily be changed by typing in the text box. These ought to be read-only with one file-picker driven interface to chose the output directory.
[ ] I can edit the text boxes on the Inputs tab and run validation again by pressing the validate button and it passes -- changing the textbox should trigger an event to update the settings object so validation will then fail. Otherwise, I suggest making the textboxes read-only so they are just there to show the contents of the file read in rather than allowing people to edit the values in the GUI.
[ ] The docker image builds and runs but there are no instructions for how to connect a display to the container when it is running so these need to be added and test.
[ ] I'm not convinced the Select Directory button on the input tab is necessary as the parameter is essentially specified with the Load Input button.

@AdinaRahim I've fixed a couple of these on the stablisation branch. @S-Hunt perhaps you can have a play with the software this afternoon in the meeting and we can expand on this list as a sort of User Acceptance Testing?

When doing a brief review of the current version of the software I noticed the following which should be the source of future work and may need their own issues in future:

[x]  The software crashes if you don't pick a file on the load inputs dialog.
[x]  The software crashes if there isn't a "results" directory in the directroy from which you load the input file. This is not robust so checking needs to be added an the user informed that they need to create the directory or else the software can try create it itself.
[x]  The output directory path is availble in various places in the GUI but can readily be changed by typing in the text box. These ought to be read-only with one file-picker driven interface to chose the output directory.
[ ]  I can edit the text boxes on the Inputs tab and run validation again by pressing the validate button and it passes -- changing the textbox should trigger an event to update the settings object so validation will then fail. Otherwise, I suggest making the textboxes read-only so they are just there to show the contents of the file read in rather than allowing people to edit the values in the GUI.
[ ]  The docker image builds and runs but there are no instructions for how to connect a display to the container when it is running so these need to be added and test.
[ ]  I'm not convinced the Select Directory button on the input tab is necessary as the parameter is essentially specified with the Load Input button.

The execution cycle as specified by Simon is like enter data->save input/create input file->load inputs to cpf. There is logic in @aharwood2 point but looking at the workflow user can edit loaded file details/ create custom input file and save that file back and then load on CPF for execution. It is not real-time passing of things to setting class from GUI Widgets. I have written functionality only for Input tab widgets so whenever textbox is edited send that info directly to setting class by initializing settings class variable against that textbox. But there are Datatype specification issues for variables e.g., the variable related to ranges and peaks is only one named fit_orders that is initialized as None (fit_orders = None) it is only designed in loading perspective in settings class. But actually this variable is a storeroom where we are dumping nested dictionaries and within nested dictionaries nested lists and within nested list again we have nested dictionaries. So whenever I try to set value to this variable it gives list out of index and object not subscriptable error due to NoneType and the variables inside it are not specified in actual don't exist. Similar is the case for variables used behind output_tab from settings class.
In this context widgets mentioned in point 4 and point 6 as quoted above need to be there as if user want to write custom input file so they can specify their data directory using it, edit existing loaded input files and create custom ones it will protect them from editing details in .py input files. To put it simple, widgets are there to create custom input file instead of passing data directly to settings class and perform at realtime, I don't know either it make sense or not


Cannot claim my rewards from sale { sale_id: 83 }

@mikedotexe @zavodil @skyward-dev Guys please help me resolve this issue

Me too :(


android: targetSdkVersion to 33, this time handling new notifs permission

Tested on an emulated Android Pixel XL running Android 13, and on the office Android device (Samsung Galaxy S9 running Android 9).
Screen recording of the "rationale" modal coming soon.
Fixes: #5753

Here's a screen recording of the "rationale" modal. To make it appear, I went to the system settings for Zulip and disabled notifications, and then I restarted the app. When /register finished, the rationale modal and then the permissions request appeared:

I tapped "Allow". Then I repeated the sequence: disable notifications in system settings and restart the app. The rationale and permissions prompt appeared again, and I tapped "Allow" again. I repeated the sequence two more times with the same result. I guess it makes sense that it always gave me the rationale and the prompt: if someone grants the permission and then immediately goes and revokes it, it seems like they might want an explanation of how the permission will be used, to help them decide.
If I tapped "Don't allow" instead of "Allow", the rationale and prompt did not appear on the next startup. Which is good. (In that case it would be more clearly spammy if it did.)

Thanks for taking care of this! This implementation looks good to me.
I also tested on my Android 13 phone, in order to see specifically the experience on upgrading an existing install (that had already had notification permission). The result was:

Immediately on starting the app, I got a notification prompt. (Not our rationale text, just the system dialog box.)
I said "allow".
I tested notifications, and they worked.

Merging.

Immediately on starting the app, I got a notification prompt. (Not our rationale text, just the system dialog box.)

Interesting! That's not actually what I would expect. I'd expect that notifications would "just work" in your case, without the prompt showing up, because you should have been "pre-granted" as described in the doc:

To minimize disruptions associated with the notification permission, the system automatically pre-grants the permission to all eligible apps when the user upgrades their device to Android 13 or higher. In other words, these apps can continue to send notifications to users, and users don't see a runtime permission prompt.

—Er, actually, reading that again, it's about upgrading to Android 13, which isn't what you did… 🤷


[fix] improve pattern matching

Issue 724 complains about an unterminated string.
While investigating I bumped upon the following patterns in extract.py
r";ytplayer.config\s*=\s*({.?});",
r";ytplayer.config\s=\s*({.+?});ytplayer",
This seems odd to me. If the first pattern does not match, then the
second won't mach either.
The unterminated string suggests that perhaps the first match is too
short as *? is non-greedy matching.
Of course if this happens or not depends on the actual html ouput that
is sent by youtube.
As a test I decided to remove the first pattern, since the config string
I got back had ;ytplayer after it. Keeping the + seems ok, as an empty
string does not seem a valid result.
Without the patch about 1 out of 5 downloads failed for me.
With the patch about 150 downloads have been done, all successful.
pytest passes
pep8 is not run as only a line in an array is removed
Closes: #724

This looks to have done it for me as well. Oddly though there is some inconsistency in the error-outs. I'm now at about 15/15 passes whereas It was more like 10/15 before. Thanks!

See #733 for a more complete fix

can anyone send me the updated config_pattern list for extract.py

Closing this PR, as https://github.com/nficano/pytube/pull/800 accomplishes the same thing, but even more concisely.


@conda-forge-admin, please add user @drbixx

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @drbixx in conda-forge/which-feedstock#3.


Error Locating Target

Hello,
I upgraded the trainer and audio diffusion to the latest releases. I am now getting this error when trying to run experiments:
[2022-10-19 09:47:41,538][main][INFO] - Instantiating model <main.module_base.Model>.
Error executing job with overrides: ['exp=base_youtube_l_3.yaml']
Error locating target 'audio_diffusion_pytorch.VDistribution', see chained exception above.
full_key: model.model.diffusion_sigma_distribution
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
I deleted the conda environment and reinstalled all of the requirements from scratch, and I am still getting the above. Any help would be appreciated.
Thanks,
MP

You have to use audio_diffusion_pytorch.VKDistribution instead, I still have to delete those old experiments that are not up to date

The old experiments have been archived and the new updated, you should be able to run the current version.

Seems to be working now! Thank you!
[2022-10-19 12:41:18,081][main][INFO] - Logging hyperparameters!
[2022-10-19 12:41:18,122][main][INFO] - Starting training.
┏━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┓
┃   ┃ Name                ┃ Type                ┃ Params ┃
┡━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━┩
│ 0 │ model               │ AudioDiffusionModel │  640 M │
│ 1 │ model.unet          │ UNet1d              │  640 M │
│ 2 │ model.diffusion     │ VDiffusion          │  640 M │
│ 3 │ model_ema           │ EMA                 │  1.3 B │
│ 4 │ model_ema.ema_model │ AudioDiffusionModel │  640 M │
└───┴─────────────────────┴─────────────────────┴────────┘
Trainable params: 640 M
Non-trainable params: 640 M
Total params: 1.3 B
Total estimated model params size (MB): 5.1 K


Fix transformation scripts

Fix the following warnings:
[main] WARN  c.h.x.t.LoggingTransformErrorListener - [warn] Transformation warning (net.sf.saxon.trans.XPathException: A function that computes atomic values should use xsl:sequence rather than xsl:value-of)
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
SXWN9026: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at xsl:for-each on line 2083 column 78
SXWN9009: An empty xsl:for-each instruction has no effect

that should be fixed upstream and the AWV no longer maintains ZUGFeRD 1 :-(

Only the first commit is related to ZUGFeRD_1p0_c1p0_s1p0.xslt. The second one is related to XR_30.
Please, specify what the upstream is, so that I could address pull requests against it.

Pull requests have been filed against upstream projects:

https://github.com/OpenPEPPOL/peppol-bis-invoice-3/pull/166
https://github.com/itplr-kosit/xrechnung-schematron/pull/34


RadioButtonEditor missing options in constructor in Editors.ts

@volkanceylan in Editors.ts the constructor of RadioButtonEditor is missing of options.

Thanks @Estrusco


GATKSparkTool: first step towards unifying handling of standard tool inputs in Spark

-Created a new base class for Spark tools, GATKSparkTool, that centrally manages
and validates standard tool inputs (reads, reference, and intervals). This allows
us to enforce consistency across tools, delete duplicated boilerplate code from tools
to load inputs, and perform standard kinds of validation (eg., sequence dictionary
validation) in one place.
-Tools that don't fit into the pattern established by GATKSparkTool can still extend
SparkCommandLineProgram directly.
-This is just a first step -- there is still much work to be done to unify our data source
classes and transparently handle inputs from different sources (GCS, hdfs, files), but
having inputs centrally managed should make the remaining tasks much easier.

For @lbergelson or @akiezun to review (whoever is available).

@droazen Looks good.  I'm so glad to see that repetitive loading code gone.  Just a few minor comments.  Feel free to merge when tests pass.  (providing that they do pass... I think you've changed the behavior of a few tools to now pull in unmapped reads, which is an improvement, but it's possible the tests are assuming that unmapped reads are ignored)

I'm hoping we can eliminate this code duplication with GATKTool in the future.


Ml flow support #1759

📝 Description

Provide a clear summary of the changes and the issue that has been addressed.
🛠 Fixes #1759

✨ Changes
Select what type of change your PR is:

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🔨 Refactor (non-breaking change which refactors the code base)
[X] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] 📚 Documentation update
[ ] 🔒 Security update

✅ Checklist
Before you submit your pull request, please make sure you have completed the following steps:

[ ] 📋 I have summarized my changes in the CHANGELOG and followed the guidelines for my type of change (skip for minor changes, documentation updates, and test enhancements).
[X] 📚 I have made the necessary updates to the documentation (if applicable).
[ ] 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).

For more information about code review checklists, see the Code Review Checklist.

Hello, I just saw another PR for the same Issue.
I wish to enter GSoC for the following projects:

Add time-series anomaly detection support to Anomalib.
AnomalyGPT: Integrating Vision Language Models (VLMs) in Anomalib for zero- and few-shot anomaly detection.

Could you refer me to more complicated issues/bugs/tasks closely related to this project? (or assign me  :) )

@Bepitic, would it be ok if we close this PR since it is a duplicate of https://github.com/openvinotoolkit/anomalib/pull/1847? Thanks a lot for your contribution, and apologies for the inconvenience :/

Yes, no worries, @samet-akcay.
I just want to help.

Thanks, much appreciated. Let us know if you are interested in any of the issues


Self avoiding walk

Adding images for example sketches.

I have edited the index.json file.  (I misspelled recursion in the image file so I misspelled in the index.json file but I can fix that if it bothers you.

I have edited the index.json file. (I misspelled recursion in the image file so I misspelled in the index.json file but I can fix that if it bothers you.

Wonderful! I might fix it someday if I come across while doing other updates but let it not stop us now from merging!!!

Not sure why this one is stuck on the checks, starting it over!


Improve Github repository security

This PR updates our CI setup according to the secure software development best practices
recommended by the Open Source Security Foundation (OpenSSF).
The overall goal is to strengthen the (supply chain) security posture.
The following changes are included:

Pin the Github Action dependencies to hash.
When developing a CI workflow, it's common to version-pin dependencies (i.e. actions/checkout@v4). However, version tags are mutable, so a malicious attacker could overwrite a version tag to point to a malicious or vulnerable commit instead.
Pinning workflow dependencies by hash ensures the dependency is immutable and its behavior is guaranteed.
https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies

Set the default permission for CI workflows to only be able to read from the repository (scope: contents).
A compromised action will not be able to modify the repo or even steal secrets since all other permission-scopes are implicit set to "none", i.e. not permitted.
https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

Add a dependabot which will perform weekly checks of the Github actions used in CI.
When a newer version is found a pull request is opened to suggest a lift.
https://github.com/ossf/scorecard/blob/main/docs/checks.md#dependency-update-tool

For future reference, additional Github guidelines and info about permissions.

Excellent and very timely wrt. xz ...

Yes, xz is somewhat an eye-opener..for me atleast.
These changes seems to improve OpenSSF scorecard from Aggregate score: 4.2 / 10 to Aggregate score: 6.5 / 10 (using public data), quite ok.

@bjosv Prophetic, look at the date:
https://www.youtube.com/watch?v=9qljpi5jiMQ&t=875s

Wow :) Thanks for the link, I didn't know the history with Azure Pipelines. So that's the reason for some weirdness..