No more Page Title displayed (using fully UI configured system)

Using the Custom Component on 3 instances, I notice the instance which is completely UI configured not showing the set page title in the Fav icons options, but simply showing Home Assistant. The tab names in Safari and Chrome are correct.
UI mode instance:

Yaml mode:

this is in config_entries, which seems indentical to the other 2 systems:
            {
                "entry_id": "a9redactreda0",
                "version": 1,
                "domain": "favicon",
                "title": "",
                "data": {
                    "title": "Ha Z-Wave",
                    "icon_path": "/local/favicons/"
                },
                "options": {
                    "title": "Ha Z-Wave",
                    "icon_path": "/local/favicons/"
                },
                "system_options": {
                    "disable_new_entities": false
                },
                "source": "user",
                "connection_class": "unknown",
                "unique_id": null
            },

all run Home Assistant OS 2021.2.2, offending Z-Wave instance runs in Beta mode, but no beta is loaded momentarily though its supervisor is 2 steps ahead: supervisor-2021.02.8
thanks for having a look

yes!
version 10.3 fixed it, thanks!


bump helm and k8s deps to latest stable releases

@elenz97 Requesting review on this and a new release if possible

Thanks very much! Appreciated, as always :)


⚠ Jenkins Plugins Artifactory has degraded performance

In 14151fa, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1263 ms

Resolved: Jenkins Plugins Artifactory performance has improved in a675fec after 19 minutes.


HTTP bans on refactor

Commit; 0aacabf943f6e02024777b16c9f373bb02894e10
I seem to still be running into HTTP bans on refactor.
Below is a log from the point of booting Shoko, until the point of the ban.
For this test I had an empty DB that I let Shoko Server identify some random files from, to then lookup show/episode/etc information. Some files had been already imported when this log starts.
LOG:
https://gist.github.com/CtrlAltDefeat94/8207904532524e53ca2bc57a640c540a
Note, please ignore the H rated results, this is a dummy db for the purpose of getting the HTTP ban, given that my own queue is empty/not doing much per day

After filtering your log I do not see any requests that are exceeding the limit rate, please make sure you don't have some other software like Plex or your main server (you mentioned this one was for testing) didn't query anidb at the same time.
From the log provided I see no issues with the limiter.

What I think happened is the anti-leech protection kicked in as you requested a lot of items sequentially which is somewhat unnatural behavior I guess. I remember anidb mods mentioning they have something of the sort.

I am 100% certain that there was nothing else calling AniDB at the time of this testing.
The calls being sequential could be a very valid reason. I've had bans before for this reason when I did API things myself...
The fact that they are sequentially here is because I did not randomize file info that I put in the DB(I 'hacked' files I do not have into this DB for the sake of having a queue to run)
I've experienced bans on my own DB which did not have this order, so I've made a dummy db with a randomized order this time to try again and see if I'll get banned

Closing for now, feel free to reopen.

I've been running nearly nonstop for the past few days and I haven't gotten a single ban \o/

@CtrlAltDefeat94 Is there an easy way I can do this to my current DB? I've been getting banned almost daily.

By 'do this', what do you mean? If you mean upgrade to the latest commit, you can, but I wouldn't recommend it unless you are familiar with SQL, and be are prepared for desktop to be half working at best.

@da3dsoul I was thinking it was query or something he had developed to randomize the data in the tables. My current DB is fairly large and I experience bans almost daily. I'm decent with SQL but I haven't looked at the structure of Shoko enough to mess around on my own.

Well that's fine. We can help by telling you where things are, or how they are used, but teaching someone how to set up DB managers, test data with queries, etc is annoying.
No refactor just has a few fixes that have been nice and stable for bans.

@Remnence I added(or hacked really) files in a random order into my dummy database for testing purposes. Not sure how it could be done with an existing queue though


Fire events without action name

Dispatching jobs that have action names and those without is functioning correctly, but there is an issue with firing events. Only events with the action name are being fired, such as 'github-webhooks::issues.created', whereas 'github-webhooks::issues' is not.
I created a simple solution to this problem and added a test case that covers firing these events.

Thanks!


add hadoop-misc4 to spark deploy list

@airhorns @angelini
cc @kmtaylor-github
deploy spark to hadoop-misc4. https://github.com/shopify/dataops/issues/127

doit


opt out of auto ignore list

Is your feature request related to a problem? Please describe.
The code as is auto ignores older can't update devices like ios 10...but i want to show the banner anways on my site.  I'd like a way to opt out of the auto ignore functionality.
Describe the solution you'd like
add a new config settings skip_auto_ignore defaults to false, and can be set to true.
alternatively it could be specific to the no_device_update stuff. so it could be show_if_no_updates defaults to false can be set to true.
Additional context
maybe it'd be better to allow it to even more specific auto ignores, like there's clear blocks of old win, ipad, etc. you could opt out of them individually with some {} structure.

Hi. I definitely want to enable this. However then, a different message is needed, as it is then just an information that the site may not work properly, without a call to action. I will implement this soon.

In my case a different message isnt necessary.  Though the sites messaging could be more specific.  In general my message is “your old browser sucks, go update it”

But if the user cannot update a different message might be better suited:
Please note, this page might not work properly in your browser. Good Luck!
:)

I get what youve been saying, but still To me the distinction isnt necessary in the banner.  It makes sense on the update site to say your os is old and theres no better options. The banner should alert theres a problem. The upgrade site seems the better place to explain the problem and solutions


Language-tool LSP support

Do you have any plans to support LanguageTool?

Configurations are user-contributed -- PR welcome!

Happy to accept a PR.


security/acme-client: Add IPv64.net support

Adds support for IPv64.net DNS-01 ACME challenge API added to latest upstream acme.sh.
https://ipv64.net/
see acmesh-official/acme.sh#4420

@fraenki Resolved the conflict. Let me know if there are any changes required

Merged, thanks!


Update quickjs

quickjs has been updated on 2024/01/13 to support ES2023 completely, so it is time to update the wrapper as well.
Thanks for your effects.

I will update recently

Updated to the quickjs latest version. You can try using version 2.1.0.


fix for require -> requireAMD for non-CommonJS folks

Quick fix for require vs requireAMD in the shared/app.js

[ ] need to deal with the callback functions for requireAMD

Coverage remained the same at 82.89% when pulling d36d9575c0b16ecac3112d6697545423e909e7d7 on require-amd-clientrouter into a450430844e970ff37ab0d35dd9004f9fda59613 on master.


Improve code documentation

The code I've been writing has barely any comments. Would be good to add more for future developers

@antoinepetty as the person most likely to be able to add such documentation, would you be able to pick this up? It would be great to do this before the next round of development happens on the simulator.

I'll see what I can do. Last time I went to look at this it seemed like most of the documentation already existed or was obvious


Added normalized config ORTEncoder

What does this PR do?
Add missing normalised config in the ORTEncoder class.
The issue leads to error in when exporting model using the ORTModelForSeq2SeqLM class.
Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


scanner-v4-matcher exceeds memory limit and is killed

I've enabled scanner v4 in in stackrox 4.4.x.  In at least 4.4.2 and 4.4.3 I've seen the indexer fail when consuming more than the  5Gi memory limit.  Editing the deployment and increasing the memory limit to 6 allows it complete indexing.
This is observed in a test environment running on k3s 1.29.5+k3s1.  As this is test, k3s is not running constantly.  I don't know if this is a contributing factor.
These are the helm flags I used for scanner v4
--set scannerV4.indexer.autoscaling.disable=true --set scannerV4.indexer.replicas=1
--set scannerV4.matcher.autoscaling.disable=true --set scannerV4.matcher.replicas=1
--set scannerV4.disable=false

Example of it exceeding 5GB of ram
$ kubectl top pod -n stackrox -l app=scanner-v4-matcher --sort-by=cpu
NAME                                 CPU(cores)   MEMORY(bytes)
scanner-v4-matcher-5c5c55fc6-j9bv6   1965m        5501Mi

This is a series of items in the pod logs at the time
{"level":"info","host":"scanner-v4-matcher-5c5c55fc6-j9bv6","component":"libvuln/OfflineImporter","updater":"RHEL7-openstack-8-including-unpatched","ref":"4740f873-0037-4695-b9f4-dffe0deeaad9","vuln_count":6708,"enrichment_count":0,"time":"2024-06-14T15:22:45Z","message":"update imported"}
{"level":"info","host":"scanner-v4-matcher-5c5c55fc6-j9bv6","component":"libvuln/OfflineImporter","updater":"RHEL9-openshift-4.14","ref":"64d9e8e2-59e6-413b-a0e9-f0dfcdced3c5","vuln_count":432,"enrichment_count":0,"time":"2024-06-14T15:22:45Z","message":"update imported"}
{"level":"info","host":"scanner-v4-matcher-5c5c55fc6-j9bv6","component":"libvuln/OfflineImporter","updater":"RHEL7-jboss-ws-5","ref":"0d1461ca-25af-4d2f-b4a1-1c253ee24e15","vuln_count":4656,"enrichment_count":0,"time":"2024-06-14T15:22:45Z","message":"update imported"}
{"level":"info","host":"scanner-v4-matcher-5c5c55fc6-j9bv6","component":"libvuln/OfflineImporter","updater":"RHEL6-rhel-6.1-eus","ref":"049b18de-5822-4898-b993-b6e18cc3807d","vuln_count":2830,"enrichment_count":0,"time":"2024-06-14T15:22:46Z","message":"update imported"}
{"level":"info","host":"scanner-v4-matcher-5c5c55fc6-j9bv6","component":"libvuln/OfflineImporter","updater":"RHEL9-openstack-17.1","ref":"0f81cc9c-979b-4c56-94e0-2397de472b4a","vuln_count":56,"enrichment_count":0,"time":"2024-06-14T15:22:46Z","message":"update imported"}

This is a known issue with the Matcher, and it one of the main reasons why it was originally deployed in Tech Preview. There has been work to resolve this, and we have found the memory usage is now in the order of 100s of MB instead of GB these days. However, as mentioned, this is for the Matcher.
Can you tell us more about the Indexer? You sent over the logs for the Matcher, so I'm wondering if you meant Matcher instead of Indexer. If not, then I'm wondering if you can tell us more about the images you scanned (size, perhaps number of images)

I'm sorry, I very much meant the matcher.  I'll update the issue to correct that.  This is a clean install of k3s which has these images in kube-system
docker.io/rancher/mirrored-coredns-coredns:1.10.1
docker.io/rancher/mirrored-library-traefik:2.10.7
docker.io/rancher/local-path-provisioner:v0.0.26
docker.io/rancher/klipper-lb:v0.4.7
docker.io/rancher/mirrored-metrics-server:v0.7.0
it has the images from stackrox 4.4.2, now inactive, and the images used by 4.4.3

@ghoff has this been resolved? The Scanner V4 matcher's current request/limit is 500MB/2GB https://github.com/stackrox/stackrox/blob/4.5.5/image/templates/helm/stackrox-central/internal/defaults.yaml.htpl#L262


Literal expression editor body has small hitbox in BKM

Describe the bug
In an empty literal expression editor of BKM, I need to select the first line to get keyboard focus

Steps to reproduce

Open a literal expression editor
Click around in the function body
If you do not hit the first line, Keyboard focus is lost/not achieved

Expected behavior
I can click anywhere and the cursor gets positioned at the end of the file
Environment

Version: 5.24.0-rc.0, v5.28.0
Operating System: Windows 10 amd64
Plugins:
Execution Platform: DMN - Camunda 8

Additional context
The cursor also suggests that I can click anywhere to edit
SUPPORT-23549
Follow-up of https://github.com/camunda/camunda-modeler/issues/4342

As this is a follow-up to a proclaimed fix I'm moving this to ready.

Fixed upstream via https://github.com/bpmn-io/dmn-js/pull/905.

@jarekdanielak Let's release + integrate the fix for this.


Third party modules order

I have noticed the alphabet order serves no purpose.
I suggest the order to be based on repo popularity. Or to be in categories (ex: web development, database, cli etc...).
For example the number of GitHub stars.

popularity is not feasible to do, due to the github api limit

Currently yes. Once we have metrics based on downloads counts (which is planned) we can do this.

Is it feasible to use github actions to call the github API to get the numbaer of stars and update to database.json?
Scheduled events: schedule
“Scheduled workflows run on the latest commit on the default or base branch. The shortest interval you can run scheduled workflows is once every 5 minutes.”

No, because this would still have the same rate limit issues as described in https://github.com/denoland/deno_website2/issues/461#issuecomment-629640278

I don't know how feasible this would be but I think the ability to sort by multiple different metrics would be nice. E.g. alphabetical, number of downloads, last updated, Github issues/stars/PRs/watches (I know you ae saying the last one won't be possible but I think it's worth mentioning).

This was fixed in https://github.com/denoland/deno_website2/pull/1403. Read more about it at https://deno.land/posts/registry2


feat: Support wildcard in Allow Networks MONET-2345

Ticket
We already support wildcard in allow networks Cloudflare. This PR allows users using this feature while creating an app and enables using wildcard domains in the contentful-app-manifest.json file.
We use tldts package to parse the url and regexes to validate ip4 and ip6 formatted ip addresses.

Closing this PR because we decided to use a regex to validate the networks.


exception occured pigpio (LLI)

context: control applied with high voltage, and limit of rail is reached. When stopping LLI and trying to reintialise it, the following is shown in console(see joint screen).
workaround: reboot raspberry

@francofusco problem of pigpio?

also :
Calibrating pendulum terminate called after throwing an instance of 'pendule_pi::Pendule::CalibrationFailed'   what():  Pendulum calibration failed! Reason: the angle encoder is at a non-zero position
stops from calibrating pendulum, we should add the suggestion to wait a bit and relaunch script

For the first issue: if I recall correctly, you should normally be able to halt the LLI by pressing a switch and relaunching it without having to reboot the RPi. However, sometimes you get the "pigpio init" error as you mentioned. Unfortunately I am not sure if there's a specific event triggering that and, at least as of today, rebooting is the only fix I am aware of...

also :
`Calibrating pendulum
terminate called after throwing an instance of 'pendule_pi::Pendule::CalibrationFailed'
what():  Pendulum calibration failed! Reason: the angle encoder is at a non-zero position
`
stops from calibrating pendulum, we should add the suggestion to wait a bit and relaunch script

This seems a bit unusual, I should dig into the code. Usually I get the "pendulum is moving" error instead.
But yeah, I should definitely document it properly - perhaps adding to the error message the suggested solution of waiting a little bit before launching again the LLI.


Projects Search Bar UI fix

The search bar on the projects screen seems a bit too high. It should have equal space above and below it. Right now, there is a lot more space below than above.

fixed as part of #1659


Bumps juno version to v12

Bumps version to v12

Looks good, should we get this in before other PRs so they have to rebase on top, since it's minor?


Read-only feature

Some libraries like Photoview work with a read-only photo library, which is pretty important to someone like me where all uploading, editing and restructuring is done by other means.

I like the concept. Are there other names for this type of implementation?
It sounds like this feature might be related to #6

I like the concept. Are there other names for this type of implementation? It sounds like this feature might be related to #6

Ahh yeah, definitely very much related. Could be a simple "No / Preserves Structure / Support Read-Only Access" trinary state in the overview.


feat(GroupTheory/OrderOfElement): If a ≤ g • a, then g • a = a

This PR adds a few lemmas about group actions on partial orders.

bors r+


board: arm: acsip_s76s: add AcSIP S76S support

The AcSIP S76S is a STM32L073+SX1276+PA SoC which
supports LoRa communications.
Signed-off-by: Dean Weiten<EMAIL_ADDRESS>

Was curious about the .csv files, is that purely for the docs and making the pin mgmt easier to describe?

Was curious about the .csv files, is that purely for the docs and making the pin mgmt easier to describe?

Thanks for this contribution!
I'm only commenting the form now but SiP porting as a board is unusual. On other hand I don't think we have a policy in place for SiP/modules definition.
My first idea would tend to assimilate SiP to a SoC and have a "real board" ported here, such as this one.
Then, if idea is to enable modules/SiP definitions, I'd rather put them in a new dedicated dts/modules section or boards/modules. But to me a zephyr target should remain a real board. @nashif, @MaureenHelm, @galak any opinion ?

Thanks for this contribution!
I'm only commenting the form now but SiP porting as a board is unusual. On other hand I don't think we have a policy in place for SiP/modules definition.
My first idea would tend to assimilate SiP to a SoC and have a "real board" ported here, such as this one.
Then, if idea is to enable modules/SiP definitions, I'd rather put them in a new dedicated dts/modules section or boards/modules. But to me a zephyr target should remain a real board. @nashif, @MaureenHelm, @galak any opinion ?

Was curious about the .csv files, is that purely for the docs and making the pin mgmt easier to describe?

Hi!
I tried to reply to the comment E-mail, but I'm not sure that it worked, so I will reprise my answer here... and I've changed my tack, (spoiler alert) I will get rid of the CSV files.  It might take me a bit, they are ugly...
Yes, I created spreadsheets for my own use, and figured they might help someone else, so I CSV'd them and put them in the doc.  I guess it's a bit atypical.
I was trying to avoid the extra work of reformatting them into RST tables, taking the easy way out by just creating CSVs and side-loading them into the CSV.
The CSVs might be ugly (weird export from LibreOffice), but when imported into a spreadsheet, they make up what I think is a nice table that can be used to plan the embedded design.
For this chip, many of the underlying processor (STM32L073RZ) pins are not brought out to the chip pins, and I was finding it difficult to figure out what 'L073 resources I had access to, and which ones I did not.  So, I created the spreadsheet with all the main and alternate pin assignments, then split it into three parts, so I could do a "find" and see which section things were in, instead of constantly hunting for, and often missing, things on the overall chip's datasheet.
This is actually my first tentative foray into open source contribution, so I'm not quite sure what I'm doing.  I mean, I've been doing embedded and real-time software for almost 40 years, but never contributed to this kind of project.
Well, after struggling with the "documentation github workflow", it doesn't like my CSVs.  I will fold them into the index.rst and resubmit.  It might take a bit of work, but I will be back :-)
Dean.

Was curious about the .csv files, is that purely for the docs and making the pin mgmt easier to describe?

Hi!
I tried to reply to the comment E-mail, but I'm not sure that it worked, so I will reprise my answer here... and I've changed my tack, (spoiler alert) I will get rid of the CSV files.  It might take me a bit, they are ugly...
Yes, I created spreadsheets for my own use, and figured they might help someone else, so I CSV'd them and put them in the doc.  I guess it's a bit atypical.
I was trying to avoid the extra work of reformatting them into RST tables, taking the easy way out by just creating CSVs and side-loading them into the CSV.
The CSVs might be ugly (weird export from LibreOffice), but when imported into a spreadsheet, they make up what I think is a nice table that can be used to plan the embedded design.
For this chip, many of the underlying processor (STM32L073RZ) pins are not brought out to the chip pins, and I was finding it difficult to figure out what 'L073 resources I had access to, and which ones I did not.  So, I created the spreadsheet with all the main and alternate pin assignments, then split it into three parts, so I could do a "find" and see which section things were in, instead of constantly hunting for, and often missing, things on the overall chip's datasheet.
This is actually my first tentative foray into open source contribution, so I'm not quite sure what I'm doing.  I mean, I've been doing embedded and real-time software for almost 40 years, but never contributed to this kind of project.
Well, after struggling with the "documentation github workflow", it doesn't like my CSVs.  I will fold them into the index.rst and resubmit.  It might take a bit of work, but I will be back :-)
Dean.

Thanks for this contribution!
I'm only commenting the form now but SiP porting as a board is unusual. On other hand I don't think we have a policy in place for SiP/modules definition.
My first idea would tend to assimilate SiP to a SoC and have a "real board" ported here, such as this one.
Then, if idea is to enable modules/SiP definitions, I'd rather put them in a new dedicated dts/modules section or boards/modules. But to me a zephyr target should remain a real board. @nashif, @MaureenHelm, @galak any opinion ?

Hi,
Again, per previous comment, I tried to submit my response in an E-mail, but I'm not sure that it worked, so I'll try here.
This is my first contribution to an open source project in my 40 year career...  and I'm a bit bewildered, trying to be careful.
Anyway, I struggled with that same question.  The challenge is, supporting it as an SoC seems to be a much more complex endeavour.  If I could just move the files from one tree to the other, I'd be happy to do so.
Yes, the Ronoth LoDev board that you cite is the development system, and I'd be happy to put it in the "boards" section if there's a way to get this part into the "soc" section without killing myself.  Especially, as I say, this is my first effort in open source :-)
Dean.

Thanks for this contribution!
I'm only commenting the form now but SiP porting as a board is unusual. On other hand I don't think we have a policy in place for SiP/modules definition.
My first idea would tend to assimilate SiP to a SoC and have a "real board" ported here, such as this one.
Then, if idea is to enable modules/SiP definitions, I'd rather put them in a new dedicated dts/modules section or boards/modules. But to me a zephyr target should remain a real board. @nashif, @MaureenHelm, @galak any opinion ?

Hi,
Again, per previous comment, I tried to submit my response in an E-mail, but I'm not sure that it worked, so I'll try here.
This is my first contribution to an open source project in my 40 year career...  and I'm a bit bewildered, trying to be careful.
Anyway, I struggled with that same question.  The challenge is, supporting it as an SoC seems to be a much more complex endeavour.  If I could just move the files from one tree to the other, I'd be happy to do so.
Yes, the Ronoth LoDev board that you cite is the development system, and I'd be happy to put it in the "boards" section if there's a way to get this part into the "soc" section without killing myself.  Especially, as I say, this is my first effort in open source :-)
Dean.

Hi there,
Well, my branch has passed the automated checks.
I found a Python script to convert my CSV to an RST table, but it choked on my table because it had embedded newlines in the cells (argh, that's why I didn't want to manually convert them)... so I hacked it and made it work.  So no more CSVs.
The question of whether this is appropriate to merge as a "board" instead of something else is a propos.  I seek some guidance on this issue.  Is there an easy way to drop this structure into another, more appropriate place?  It didn't seem so, from my brief look... at least not in the "soc" area, where I figured it might go.
The point here is, that the S76S contains an STMicro STM32L073RZ processor, a Semtech SX1276 LoRa transceiver, and a power amplifier.  I didn't see an appropriate, "easy", way, to indicate this integration.
Please advise if there's a better way to do it :-)
Dean.

Hi there,
Well, my branch has passed the automated checks.
I found a Python script to convert my CSV to an RST table, but it choked on my table because it had embedded newlines in the cells (argh, that's why I didn't want to manually convert them)... so I hacked it and made it work.  So no more CSVs.
The question of whether this is appropriate to merge as a "board" instead of something else is a propos.  I seek some guidance on this issue.  Is there an easy way to drop this structure into another, more appropriate place?  It didn't seem so, from my brief look... at least not in the "soc" area, where I figured it might go.
The point here is, that the S76S contains an STMicro STM32L073RZ processor, a Semtech SX1276 LoRa transceiver, and a power amplifier.  I didn't see an appropriate, "easy", way, to indicate this integration.
Please advise if there's a better way to do it :-)
Dean.

Hi there,
Well, my branch has passed the automated checks.
I found a Python script to convert my CSV to an RST table, but it choked on my table because it had embedded newlines in the cells (argh, that's why I didn't want to manually convert them)... so I hacked it and made it work. So no more CSVs.
The question of whether this is appropriate to merge as a "board" instead of something else is a propos. I seek some guidance on this issue. Is there an easy way to drop this structure into another, more appropriate place? It didn't seem so, from my brief look... at least not in the "soc" area, where I figured it might go.
The point here is, that the S76S contains an STMicro STM32L073RZ processor, a Semtech SX1276 LoRa transceiver, and a power amplifier. I didn't see an appropriate, "easy", way, to indicate this integration.
Please advise if there's a better way to do it :-)
Dean.

I'd say maybe a mix here between a full SoC and board port makes sense.  The main thing I'm thinking is that we introduce the "SIP" .dtsi in dts/arm/acsip/... than defines the common SIP bits and that gets used in the board dts.
We can see over time if it makes sense to refactor some the 'Kconfig' logic out of the board if we end up having multiple boards for the same SIP or we have a number of different SIPs that have support in Zephyr.

Hi there,
Well, my branch has passed the automated checks.
I found a Python script to convert my CSV to an RST table, but it choked on my table because it had embedded newlines in the cells (argh, that's why I didn't want to manually convert them)... so I hacked it and made it work. So no more CSVs.
The question of whether this is appropriate to merge as a "board" instead of something else is a propos. I seek some guidance on this issue. Is there an easy way to drop this structure into another, more appropriate place? It didn't seem so, from my brief look... at least not in the "soc" area, where I figured it might go.
The point here is, that the S76S contains an STMicro STM32L073RZ processor, a Semtech SX1276 LoRa transceiver, and a power amplifier. I didn't see an appropriate, "easy", way, to indicate this integration.
Please advise if there's a better way to do it :-)
Dean.

I'd say maybe a mix here between a full SoC and board port makes sense.  The main thing I'm thinking is that we introduce the "SIP" .dtsi in dts/arm/acsip/... than defines the common SIP bits and that gets used in the board dts.
We can see over time if it makes sense to refactor some the 'Kconfig' logic out of the board if we end up having multiple boards for the same SIP or we have a number of different SIPs that have support in Zephyr.

I am looking into splitting this up appropriately such that the AcSIP S76S "chip" SiP is supported by a dts/arm dtsi file, and then the Ronoth LoDev "board" in the board/arm section builds on top of that.

I am looking into splitting this up appropriately such that the AcSIP S76S "chip" SiP is supported by a dts/arm dtsi file, and then the Ronoth LoDev "board" in the board/arm section builds on top of that.

Now I need some assistance, please.  I seems that the compliance check wants a code owner for selected files.  What do I do?  I do not have commit privilege on the repository, but the comment seems to say that I need it.  I'm not sure I want it yet :-)

Now I need some assistance, please.  I seems that the compliance check wants a code owner for selected files.  What do I do?  I do not have commit privilege on the repository, but the comment seems to say that I need it.  I'm not sure I want it yet :-)

Now I need some assistance, please.  I seems that the compliance check wants a code owner for selected files.  What do I do?

You need to add yourself to the codeowners file for the new files (see compliance check message) in your commit in this PR.

Now I need some assistance, please.  I seems that the compliance check wants a code owner for selected files.  What do I do?

You need to add yourself to the codeowners file for the new files (see compliance check message) in your commit in this PR.

Now I need some assistance, please.  I seems that the compliance check wants a code owner for selected files.  What do I do?

You need to add yourself to the codeowners file for the new files (see compliance check message) in your commit in this PR.

Should I add myself to the codeowners for the other (new) files in my commit?

Now I need some assistance, please.  I seems that the compliance check wants a code owner for selected files.  What do I do?

You need to add yourself to the codeowners file for the new files (see compliance check message) in your commit in this PR.

Should I add myself to the codeowners for the other (new) files in my commit?

I hope that my submission is structured correctly.  Let me know if I need to break it up, restructure, move things etc.  I am using this to generate test code for the Ronoth LoDev, and it seems to work :-)

Hi, it has been some time without feedback.  Is there something else I should be doing?

Hi, it has been some time without feedback. Is there something else I should be doing?

Mostly people are busy working on bugs as we try and get the 2.5 release out this week.

Hi, it has been some time without feedback. Is there something else I should be doing?

Mostly people are busy working on bugs as we try and get the 2.5 release out this week.

Ah yes, no worries, I will chill and wait then.  Thanks!

Is there something else I should do to fix this pull request, or promote its adoption?  This is my first time contributing, and I'd like to know if there is something wrong with the request.

Is there something else I should do to fix this pull request, or promote its adoption? This is my first time contributing, and I'd like to know if there is something wrong with the request.

@NorthernDean You're doing good, we just need some more time to review. Part of the problem is that this is a new type of board and it requires discussion and agreement to happen, which is taking more time. Please bear with us.

Is there something else I should do to fix this pull request, or promote its adoption? This is my first time contributing, and I'd like to know if there is something wrong with the request.

@NorthernDean You're doing good, we just need some more time to review. Part of the problem is that this is a new type of board and it requires discussion and agreement to happen, which is taking more time. Thanks for bearing with us.

Oh OK, no worries, if this is something new (a bit surprised but that is so cool!), then I'll not worry about it.  As time goes by, I might want to contribute in other ways :-)

I'm wondering if we should really add this board/SIP to the dac, adc and mem_protect unit tests. As the underlying SOC is the same as the Nucleo L073RZ and the "normal" STM32L073RZ is probably more common, adding it to the unit tests will mainly increase CI compile time, but not really improve the test coverage.
So I would suggest to only add the board definitions and keep the unit tests as they are. What do others think?

As long as it doesn't affect use of the definitions, then that would be a good idea.  What portion of the definition drives the unit tests?
What do other similar SoCs do?  Surely this isn't the first :-)  I was trying to re-use existing way of doing things, did I miss something?

This looks generally fine.
Only request from my part would be to split dts and board parts in 2 distinct commits.
There are other points of attention, like references to Mbed developments or .rst under dts/ which are unusual and I'll let these to @galak and @MaureenHelm

Hi, I was wondering about that myself.  I will split them up and submit them separately, thanks.

@NorthernDean You can have multiple commits in one PR. So you can just push your 2 commits here they will be added on top of master at PR merge.

@NorthernDean You can have multiple commits in one PR. So you can just push your 2 commits here they will be added on top of master at PR merge.

@erwango Thank you, I was not familiar with the ability to stack commits inside a single PR.  I'll do that.

OK I hope I've done things correctly.  You will of course let me know :-)

@NorthernDean I rebased this to fix the merge conflicts.


Add instructions on how to interface the library in a Zig project.

Hello, there! I've been wanting to write a WebSocket server in Zig, and this project seems wonderful. However, the only thing blocking me from building amazing things is my not knowing how to use this library from my own Zig project, which I initialised using zig build-exe. Could you help me?

If you're asking how to actually add the library to your project then...
Two or so months ago, the developed branch of Zig (0.11.0-dev..) added a built-in package manager. It's relatively cumbersome to use right now, but it works. https://medium.com/@edlyuu/zig-package-manager-wtf-is-zon-df5ecbafcc54  is maybe the best end-to-end guide I've seen.
In short, you'd create a build.zig.zon file in the root, and it'll contain something like:
.{
	.name = "your-app-name",
	.version = "0.0.0",
	.dependencies = .{
		.websocket = .{
			.url = "https://github.com/karlseguin/websocket.zig/archive/fda94dbf012783553209d384b56549dbe0367105.tar.gz",
			.hash = "1220a436e7e2e498447d79057194e84c9f7158a8c796dbe721dbe14bb1de5f25c92f"
		}
	}
}

That archive is the latest version of websocket.zig. There's no great way to get the hash right now, as far as I know, aside from putting in the wrong one and letting Zig tell you what it should be. The above hash is wrong, when you try to run, it should complain about it and tell you what the right one is, just copy and paste the right one over the wrong value above.
Now in your build.zig, you can grab this dependency and add the module to your project, something like:
const websocket = b.dependency("websocket", .{
  .target = target,
  .optimize = optimize,
});
const exe = b.addExecutable(.{
  .name = "your-app",
  .root_source_file = .{ .path = "src/main.zig" },
  .target = target,
  .optimize = optimize,
});
exec.addModule("websocket", websocket.module("websocket"));
...

If you have other steps, like one created from b.addTest then you also addModule(....) on that step.
Once that's done, you can @import("websocket") in your project as shown in the readme.

Thanks; that's working like a charm! Though, zls seems to be oblivious to the dependency, which makes it hard to discover the library's features. I'd really appreciate some documentation (or a build step to generate them)!

I guess zls might not work because it the library largely works by being given a handler which takes over processing the request, so aside from the initial call to listen and the ability write to the client, there isn't much else.
There's the autobahn.zig file, in the root of the repo, which is a working example (the actual code that's used to test the implementation against the autobahn test framework). That, and the readme, are pretty complete documentation.


Client doesn't build, "use of deprecated item" errors in client/lib/src/block_position.rs

https://travis-ci.org/bfops/playform/builds/106366468#L1315
/home/travis/build/bfops/playform/client/lib/src/block_position.rs:18:7: 18:49 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:18   use std::collections::hash_state::DefaultState;                                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:20:58: 20:81 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:20   pub type T<V> = std::collections::HashMap<super::T, V, DefaultState<FnvHasher>>;                                                                                ^~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:23:5: 23:47 error: use of deprecated item: renamed to with_hasher, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:23     std::collections::HashMap::with_hash_state(Default::default())                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:30:7: 30:49 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:30   use std::collections::hash_state::DefaultState;                                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:32:52: 32:75 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:32   pub type T = std::collections::HashSet<super::T, DefaultState<FnvHasher>>;                                                                                ^~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:36:5: 36:47 error: use of deprecated item: renamed to with_hasher, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:36     std::collections::HashSet::with_hash_state(Default::default())                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:48:9: 48:51 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:48     use std::collections::hash_state::DefaultState;                                                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:50:54: 50:77 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:50     pub type T = std::collections::HashSet<super::T, DefaultState<FnvHasher>>;                                                                                ^~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:53:7: 53:49 error: use of deprecated item: renamed to with_hasher, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:53       std::collections::HashSet::with_hash_state(Default::default())                                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:60:9: 60:51 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:60     use std::collections::hash_state::DefaultState;                                                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:62:60: 62:83 error: use of deprecated item: support moved to std::hash, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:62     pub type T<V> = std::collections::HashMap<super::T, V, DefaultState<FnvHasher>>;                                                                                ^~~~~~~~~~~~~~~~~~~~~~~ /home/travis/build/bfops/playform/client/lib/src/block_position.rs:65:7: 65:49 error: use of deprecated item: renamed to with_hasher, #[deny(deprecated)] on by default /home/travis/build/bfops/playform/client/lib/src/block_position.rs:65       std::collections::HashMap::with_hash_state(Default::default())                                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: aborting due to 12 previous errors Could not compile client-lib.

Wow, that was fast! Fixed by:
https://github.com/bfops/playform/commit/ee8f4af8c8a783f80e8a701852ab943b049e17f0
Thanks!

Awesome, thanks for the report :)


SJSON search documentation

Add SJSON search ("_search" keyword) documentation to this wiki post
see: https://discord.com/channels/667753182608359424/667757899111596071/982896736299274311

Some suggestions for content on that page:
Add _search as a sequence keyword with description like:

"_search" Searches for any containers which match all the given matching conditions, and merges the provided updates to all matching containers.

Add subheadings under Mirroring Structure heading to make it clearer to identify what each codeblock is for, e.g.

Sample input file
Merging changes to a sequence by index number
Merging changes to a sequence by search terms
Appending to a sequence
Replacing a sequence
Deleting a key

Under the new subheading regarding search terms, content such as:
Merging changes to a sequence by search terms
As an alternative to explicitly specifying the list index to update a container at, you can also search for containers which match a set of conditions. This search feature will merge your replacement values to all containers in the list which match all your search terms.
The format of using this search is as follows:
Sequence = [
    "_search", [
        { TargetKey = "target_value" }
        { TargetKey = "replacement_value" }
        ...
    ]
]

The keys for both the target_value and replacement_value can be the same or different. The target_value and replacement_value containers may also both contain multiple key-value pairs, e.g.
Sequence = [
    "_search", [
        {
            Name = "WeaponThrow"
            FullyAutomatic = true
        }
        {
            FullyAutomatic = false
            Control = "Attack2"
            MinChargeToFire = 1.0
            LoseControlOnRelease = true
            SwapOnFire = "_delete"
        }
    ]
]

To perform multiple searches at the same level, add further pairs of match conditions and replacement values, e.g.
Sequence = [
    "_search", [
        { TargetKey = "target_value" }
        { TargetKey = "replacement_value" }
        { OtherTargetKey = "another_target_value" }
        { OtherTargetReplacement = "another_replacement_value" }
    ]
]

To make the same change as the previous example where a container was updated using an explicit index number, to change the value at MyKey to "newvalue", this is the corresponding merge sjson which identifies the container to update by finding containers where OtherKey = 45
{
  Sequence = [
    "_search"
    [
        { OtherKey = 45 }
        { MyKey = "newvalue" }
    ]
  ]
}


iBug: Blacklist orientalecowoodsltd.com

iBug requests the blacklist of the website orientalecowoodsltd.com. See the Metasmoke search here and the Stack Exchange search here.

orientalecowoodsltd.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Coverage remained the same at 65.608% when pulling 9bf0bc2fc485ec0b86492ec06893a80581d1f817 on auto-blacklist-1513254307.2913508 into 281358ca732a0b96909368c3b0a5e11ba0f863fc on master.

!!/approve

!!/approve


[stable/kapacitor] Supply kapacitor.conf via ConfigMap/values.yaml

Added support to generate a kapacitor.conf from values.yaml.
By default the config generated will mirror the default config Kapacitor uses. See generated with this chart vs the default kapacitor config.
The only difference between the YAML and the TOML is using a kapacitor key to contain the top-level config options, which need to be pulled out separately due to TOML being order-sensitive.
Without this, Kapacitor isn't very useful because you can't use the alerts without enabling a notification in the config.

@jagregory You can enable the notifications through the API or through our dashboarding tool Chronograf. Relying on a config file breaks the latter functionality so I've implemented it in the ENV you see.
Another note on this approach, I've just submitted a PR to kubernetes/helm that adds a toToml template function that might make this code cleaner.

@jackzampolin can we close this out?

@viglesiasce Yup!


explore: add description

added description to the explore page, as well as modified the title to make it consistent with the rest of public pages
CR @javierarce
off topic: I spotted a search view in the explore folder, what is that used for?

retest this please

:+1:

retest this please


Investigate adding Maven enforcer bans on certain logging dependencies

We used to have the following in the root POM:
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-enforcer-plugin</artifactId>
                <version>${maven-enforcer-plugin.version}</version>
                <executions>
                    <execution>
                        <id>enforce</id>
                        <configuration>
                            <rules>
                                <dependencyConvergence />
                                <bannedDependencies>
                                    <excludes>
                                        <!-- As recommended from slf4j guide, exclude commons-logging -->
                                        <exclude>commons-logging:commons-logging</exclude>
                                        <!-- Ensure only the slf4j binding for logback is on the classpath -->
                                        <exclude>log4j:log4j</exclude>
                                        <!-- This should not exist as it will force slf4j calls to be delegated to JUL -->
                                        <exclude>org.slf4j:slf4j-jdk14</exclude>
                                        <!-- This should not exist as it will force slf4j calls to be delegated to log4j -->
                                        <exclude>org.slf4j:slf4j-log4j12</exclude>
                                    </excludes>
                                </bannedDependencies>
                                <requireMavenVersion>
                                    <version>3.3.9</version>
                                </requireMavenVersion>
                            </rules>
                        </configuration>
                        <goals>
                            <goal>enforce</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

This told Maven Enforcer to ban several logging frameworks for reasons described in the SLF4J Bridging legacy APIs page and  StackOverflowError due to things like having both jcl-over-slf4j.jar AND slf4j-jcl.jar on the class path.
kiwi's parent POM does not have these, I think because they use the SLF4J API but don't enforce a specific logging back-end such as Logback or Log4J2. However, as elucidation is a Dropwizard service, it uses Logback as the logging provider, and therefore we do not want any other logging providers on the classpath.
So, does it make sense to add these back in to elucidation? I don't think it makes sense to add these bans to kiwi-parent, but it might make sense to add them here in elucidation.

Also see this gist which is similar but has slightly different syntax, e.g. it uses just commons-logging while we used (in the original POM) commons-logging:commons-logging.
If we choose to add these back, we should test this (functionally) by adding the enforcer bans, and then adding each banned dependency to the POM individually and making sure that Maven Enforcer enforces and fails the build until they are removed.


audit: enforce https://*.sourceforge.io/ homepages

Ref: https://sourceforge.net/blog/introducing-https-for-project-websites/

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

I tested the new condition/suggestion in a minimised test source.

This is not a problem and you did great work.
Here is my suggestion to your contribution:
# ...
elsif (homepage.include?("sf.net") || homepage.include?("sourceforge.net"))
  assert_match "#{homepage} should be `https://foo.sourceforge.io/`", fa.problems.first
else
# ...

Unfortunately, I had not yet the chance to run the tests to verify this approach. But the idea here is to catch the homepages that include the domains sf.net and sourceforge.net and to assert the problem statement.

Thank you @maveonair, that looks very good. I've updated the patch. Let's hope it passes.

@vszakats You are welcome. Thank you for your contribution  👍 .

According to the documentation, only new projects will use https by default, existing ones have to switch to https manually.
This means that https://*.sourceforge.io will still redirect to http://*.sourceforge.net for those that haven't switched to https.

@reitermarkus, Yes, I'm aware. Anyhow it's best to use the secure entry point by default and let the rest be sorted out by the pages themselves. Any redirection (to an insecure page) will be performed in the browser, so it will be visible to the user.

Is there anything that needs to be done in this PR to merit a merge?

Commits squashed.

CI failure - unrelated:
error: RPC failed; curl 56 SSLRead() return error -36
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Error: Failure while executing: git clone https://github.com/Homebrew/homebrew-core /Users/travis/build/Homebrew/brew/Library/Taps/homebrew/homebrew-core -q

Required test passed.


Github plugin visibility change

Description
Addressed discrepancy between docs and code in plugin visibility to users, update the documentation that we will be using GitHub topics to search for plugins that are not on PyPI, also added a description that this may be deprecated in the future in favor of the PyPI classifier
Added a toggle that by default hide plugins only from Github in favor of PyPI releases, user can unhide the plugins from Github if needed
Type of change

New feature (non-breaking change which adds functionality)
Documentation

References
some of the backgrounds are discussed in https://github.com/napari/napari-plugin-engine/issues/16
How has this been tested?
Manually tested the interface
Final checklist:

[X] My PR is the minimum possible work for the desired functionality
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works

Failure seem to be a problem with the coverage package that crashed when combining report.
Someone with rights could restart CI.

Failure seem to be a problem with the coverage package that crashed when combining report.
Someone with rights could restart CI.

I think right now all/ most of our windows tests are failing right now, independent of this PR - I have tried rerunning, but we should also see if there's anything we can do to fix the current windows CI fail

Failure seem to be a problem with the coverage package that crashed when combining report.
Someone with rights could restart CI.

I think right now all/ most of our windows tests are failing right now, independent of this PR - I have tried rerunning, but we should also see if there's anything we can do to fix the current windows CI fail

i took a crack at that this weekend and couldn't repeat it locally on a windows box unfortunately :/  annoying.  need to take another look soo

Huh, all tests are passing! The CI gods are looking favorably upon us right now! @tlambert03 anything else you'd like to see from this PR before merge/ any refinement to the language in the docs. I worry "we could deprecate github repo matching in the future" might be a little unsettling for people to read as phrased.

may I get an approval to merge in this? github would not allow me to merge, unless anything else we want to address?

I would love to remove the github reference all together! I did not propose this because I don't know what impact it would have both on the current installations and future proofness, the rationale is more on the future proofness if someone would not be releasing to pypi at all

I'd be totally ok with moving github visibility altogether!

Sounds like all three of us are in agreement that removing the github visibility entirely is now fine.
Maybe just remove the Qt changes and leave the _search_github=False in this PR @ziyangczi. We can make a followup PR to remove the code entirely later if we want (I'm also ok dropping the code entirely now too, it's not too hard to add back in).

gonna drop the github code instead


Limit testnet deployments to 2 days.

@despiegk  requested the max expirary date for deployments on testnet would be 2 days. To make sure ppl don't reserve for weeks / months so other ppl can deploy stuff as well.

demos are limited for 3 hours, do you mean for 3bot expiration?

The demos are limited yes, but he spoke about other stuff that you reserve with the 3Bot admin panel. For exampe an ubuntu

there's no expiration for solution or Apps, we invented that for Apps as we create a pool for each and tied the expected expiration  to the CUs and SUs in the pool we create per app. (and the estimate isn't guaranteed if there is no actual consumption of the pool resources via the workloads. That being said, we can't fix the deployment of e.g ubuntu, k8s, minio to 2 days, as the pool resources used by each of them are different without having an upper limit for pool creation/extension, which will definitely affect too many parts of the code


Laravel 9.x

Bumps dependencies to support Laravel 9.
I updated the target PHP version for Psalm because it was causing errors to be thrown (PHP 8.1 Enums are used for the transform / caster). Tests are still being run for PHP 8 and PHP 8.1.
The GitHub actions now run on push. This allows tests and static analysis to run for forks as well.
I also added and upgraded PHP-CS-Fixer as a development dependency which was referenced, but not installed. This is more consistent with other Spatie packages.
Note that this requires #76, which could be closed in favor of this pull request if merged.

Again, very nice, thanks!

No problem. Happy to help!


Web.xml with servlet markup not working

It is working now locally it was surely something else.
Still this error when calling API
SEVERE: Unable to instrument com.google.cloud.solutions.mobilepushnotification.DeviceRegistration. Security restrictions may not be entirely emulated.
java.lang.ArrayIndexOutOfBoundsException: 137
Still request are sent to power-... from API explorer


general comment

I created a gitter for more dynamic help.
Join the chat: https://gitter.im/AlexaDevelopers/Lobby

Thanks @marath007 !


Cannot upgrade or rollback apps using --force option with helm v3

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Create a catalog using helm v3. I used https://argoproj.github.io/argo-helm
Deploy an app using that catalog. I chose argo-cd, version 1.8.5
Upgrade that app and choose the force option. I upgraded version to 1.8.6

Result:
Fails with:
Failed to install app argo-cd. manifest_sorter.go:192: info: skipping unknown hook: "crd-install" manifest_sorter.go:192: info: skipping unknown hook: "crd-install" Error: UPGRADE FAILED: failed to replace object: Service "argo-cd-argocd-application-controller" is invalid: spec.clusterIP: Invalid value: "": field is immutable && failed to replace object: Service "argo-cd-argocd-dex-server" is invalid: spec.clusterIP: Invalid value: "": field is immutable && failed to replace object: Service "argo-cd-argocd-redis" is invalid: spec.clusterIP: Invalid value: "": field is immutable && failed to replace object: Service "argo-cd-argocd-repo-server" is invalid: spec.clusterIP: Invalid value: "": field is immutable && failed to replace object: Service "argo-cd-argocd-server" is invalid: spec.clusterIP: Invalid value: "": field is immutable

Other details that may be helpful:
This workflow works if NOT selecting the force option.
This workflow also works using the same helm repo but choosing helm v2 instead.
Environment information
single node install master-2377-head Rancher version 75d3dc825

Note this also applies for rollback as well

I am able to use the --force option with helm 3 with different helm charts (I used just argo from that same catalog, instead of the argo-cd one), so it seems the failure is chart specific.
This failure is due to how Helm 3 handles merge patches now, it sees spec.clusterIP empty from the initial deploy and tries to set it that way for the next deploy which fails. Since this is the expected helm 3 behavior, it would need to be a change the chart as explained in the helm issue linked below.
https://github.com/helm/helm/issues/6378#issuecomment-557746499

Confirmed with @rancher-max it's no longer an issue.


"Parameter types cannot be optional" error when parentheses used around parameters

Summary
I cannot map a step using Cucumber Expressions when I have parentheses around a parameter. The parenthesis is already escaped.
Expected Behavior
Given a feature:
# language: en

Feature: Parenthesis
  Scenario: Parenthesis arount a param
    Given an int is inside parenthesis like this (1)

and a step definition:
Given('an int is inside parenthesis like this \({int})') do |int|
  pending # Write code here that turns the phrase above into concrete actions
end

When i run cucumber
Then it should succeed
Current Behavior
It fails with the message:
Parameter types cannot be optional: an int is inside parenthesis like this \({int}) (Cucumber::CucumberExpressions::CucumberExpressionError)

Parameter types cannot be optional: an int is inside parenthesis like this \({int}) (Cucumber::CucumberExpressions::CucumberExpressionError)
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-expressions-6.0.1/lib/cucumber/cucumber_expressions/cucumber_expression.rb:101:in `check_no_parameter_type'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-expressions-6.0.1/lib/cucumber/cucumber_expressions/cucumber_expression.rb:54:in `block in process_optional'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-expressions-6.0.1/lib/cucumber/cucumber_expressions/cucumber_expression.rb:52:in `gsub'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-expressions-6.0.1/lib/cucumber/cucumber_expressions/cucumber_expression.rb:52:in `process_optional'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-expressions-6.0.1/lib/cucumber/cucumber_expressions/cucumber_expression.rb:24:in `initialize'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/registry_and_more.rb:154:in `new'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/registry_and_more.rb:154:in `create_expression'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/step_definition.rb:30:in `new'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/registry_and_more.rb:83:in `register_rb_step_definition'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/dsl.rb:31:in `register_rb_step_definition'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/dsl.rb:133:in `register_rb_step_definition'
/Users/peagha/Code/me/exemplos_livro/data_table/features/step_definitions/parenthesis.rb:3:in `<top (required)>'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/registry_and_more.rb:107:in `load'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/glue/registry_and_more.rb:107:in `load_code_file'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/runtime/support_code.rb:144:in `load_file'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/runtime/support_code.rb:85:in `block in load_files!'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/runtime/support_code.rb:84:in `each'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/runtime/support_code.rb:84:in `load_files!'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/runtime.rb:272:in `load_step_definitions'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/runtime.rb:68:in `run!'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/lib/cucumber/cli/main.rb:34:in `execute!'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/cucumber-3.1.2/bin/cucumber:9:in `<top (required)>'
/Users/peagha/.rbenv/versions/2.5.3/bin/cucumber:23:in `load'
/Users/peagha/.rbenv/versions/2.5.3/bin/cucumber:23:in `<top (required)>'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/cli/exec.rb:74:in `load'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/cli/exec.rb:74:in `kernel_load'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/cli/exec.rb:28:in `run'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/cli.rb:463:in `exec'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/cli.rb:27:in `dispatch'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/cli.rb:18:in `start'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/exe/bundle:30:in `block in <top (required)>'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/Users/peagha/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/bundler-1.17.1/exe/bundle:22:in `<top (required)>'
/Users/peagha/.rbenv/versions/2.5.3/bin/bundle:23:in `load'
/Users/peagha/.rbenv/versions/2.5.3/bin/bundle:23:in `<main>'

Possible Solution
It seems to be related to the regexes used to validate the expression.
Steps to Reproduce (for bugs)
The code above should be enough. If you need more info (maybe a Github repo) just tell me and I create one.
Context & Motivation
I'm updating a book that talks about Cucumber and RSpec. The regex examples are being replaced with Cucumber expressions, and I stepped into this problem when updating one of the examples of the book.
Your Environment

Version used: Cucumber 3.1.2 (fails with 4.0.0.rc.1 as well)
Operating System and version: macOS High Sierra
Ruby 2.5.3

It seems as though you're having 2 conflicting statements (Optional stuff inside bracket literals and a parameter-type)
A workaround (albeit not fixing the issue), would be to create a custom parameter type that has enforced brackets. i.e. /\(\d+\)/ and call it something like bracketed_number
Then you could say Given('an int is inside parenthesis like this {bracketed_number}') do |int|

@luke-hill thanks for your answer!
I don't know if I got something wrong, but I expected that by escaping the parentheses I wouldn't have it interpreted as optional; I don't mean to use the "optional" feature at all.
If the parentheses are escaped, what makes sense to me is for them to work just like any literal text. Do you see this scenario as an issue or Cucumber is behaving as expected?

So I've spent a bit of time diving into the expressions stuff, and know a bit how it works. I think more-often than not these are edge cases which are either uncovered or conflicting.
So with this, the example shows using brackets to wrap some form of "regular" regex. However you're using a cuke-exp (Pre-defined), inside the brackets. Which are 2 different items, which could conflict.
I'll have a little play around and see if we can get the two playing nicely together.

So I can see where it is failing. But I've managed to get a simple runthrough working.
Also for some reason the master branch is tracking version 6.2.1 but on rubygems only version 6.0.1 is released. Can you try hitting master, as there was some commits in recently which look at this issue (By commit msg)

I ended up creating a repo for reproducing the error: https://github.com/peagha/cucumber_parameter_issue
@luke-hill I don't know if I understood you; is this issue solved in the master branch? I've checked the latest commits, but didn't find anything related to this issue.

As an update @peagha this is being worked on, but has raised a few more gremlins. Items are in PR / review phase at the moment

@peagha This has been fixed for all bindings. A release will be forthcoming


Question regarding texture array size

Hello!
I enjoyed reading your "Using Arrays of Textures in Vulkan Shaders" blog post. It cleared up a few things I'd been wondering about during my attempt to educate myself about Vulkan having only known OpenGL 3.3.
One thing I'm curious about: Do you happen to know what parts of the Vulkan spec might indicate sensible maximum values for the sizes of texture arrays? I'd like to size my arrays based on reported device capabilities.

To answer my own question years later: The relevant device limit is maxPerStageDescriptorSampledImages, which is 8388606 on my AMD RADV NAVI10 workstation.

Sorry I missed this years ago, glad you found the answer though :)

No problem. I get enough GitHub notifications to miss a few dozen here and there. :smile:


Teleconference tool tips for HPC/CSE users and teams

Lets create a curated content article that takes the form of a table with tools across the top and features down the left side kinda sorta like below (only here as an example, not to suggest only these topics. This table is constructed so that feature headings link to descriptive sections below table (I am not sure I've got the markdown correct for that here but if not will resolve shortly) and that yes/no/partial links to best resource for that product's explanation/training of that feature. The features listed are just a start informed from today's meeting notes

Feature
Zoom
WebEx
BlueJeans
MS Teams
other 2

Breakout Rooms
👍
:fist_left:
:+1:
:+1:

Voting
Yes
Yes
Partial
Yes

App Sharing

multiple displays

shared whiteboard

shared annotations

recording

chat

blockout background

test meetings

not-compatible-with

raise hand

requires client download

Breakout Rooms
This is a feature that makes it possible for a single meeting to be broken into sub-meetings among smaller groups of participants and, after a period of time, re-joined back into the single large meeting.
Voting or Polling
This is a feature that allows the host to ask participants a question and have then anonymously vote their responses.
Screen Sharing
This is a feature that allows the host/presenter to share everything on his/her screen with all the participants. All teleconference tools support this feature. However, a number of tools also support variations of this feature for different needs. These are described below.
App Sharing
App (or Application) sharing is like Screen Sharing except that the window(s) of only a single application (e.g. PowerPoint or Word) is shared.  The host/presenter is not forced to share their whole screen but can select only the window(s) from a specific application to share. This can be useful in cases where the host/presenter tends to have a lot of windows open and they want to keep the participants from accidentally seeing the contents of those other windows. When you have a choice, using application-specific sharing is a best practice.
Shared Annotations
This is similar to but not quite the same thing as Screen Sharing. Shared annotations allows the presenter/host to draw annotations on top of whatever content is being displayed in the main window so that all other participants can see it.
Shared Whiteboard
This is similar to but not quite the same thing as Shared Annotations. A shared whiteboard is a separate drawing area, like a whiteboard in an office, where all participants can doodle content and paste images they captured locally.

Ok, so in the markdown, above, I am using the correct GitHub Flavored Markdown (GFMD) syntax for the links from the feature headings in the table to the level 3 headings in the text below. If you just cut-n-paste the raw markdown text into our wiki pages (as markdown), it works correctly. I think that GiHub issues don't fully support all of GFMD.
So, what do people think of this structure? The table is nice and concise highlighting the key features many of us need for using the tools for our needs.
We could break the table into a few different sections; one about the tools and features, another about the use cases that @jd-moulton and @maherou suggested.

I edited the above comment to use a row of github emojis instead of the text Yes or No. A challenge is that there is nothing indicating that those emojis are actually links to something else until you hover over them. So, probably not the best idea.

If this is intended for BSSw.io, I would not assume the emojis are available.  I don't think BSSw supports GFMD exactly.  And the style sheets used on BSSw are sometimes very different in how things are styled.  I suggest some experiments on the preview site before you get creative.

I suggest some experiments on the preview site before you get creative.

Thanks for the reminder 😢

Moved to #499


Feature: reset to branch and log by branch

Feature: reset to branch and log by branch  …
added two commands

git: reset to branch
git: log by branch

We may want to consolidate the git: reset... commands into a single command soon, with an intermediate prompt for reset type.  But this is good for now.  Thanks!

Thanks for merging this.


Case study for tvOS focus.

Adding a new case study app for tvOS-specific features, and the first case study I included was how to control focus programmatically on tvOS.

I just pushed some hacky stuff to get iOS 13 building: https://github.com/pointfreeco/swift-composable-architecture/pull/226/commits/edabc760e00c633c05884f79d8445caab28dad6e
not sure if it's the right way to do this


create trivial plugin

What does this PR do?
Adds a trivial plugin that enables testing of plugin output other than IQ data. It outputs a wav file.
Also fixed a bug with spelling of an env var in the plugins api.
Made handling of plugin output dependent on the mime type returned. If not 32bit IQ, it stores the file on disk. At present, only audio/wav is handled.
The new plugin has some notes about how to write a plugin.
All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you successfully ran tests with your changes locally? Including container validation.
[x] Have you lint your code locally prior to submission?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you labelled this PR correctly? E.G. major, milestone, breaking, breaking-change, minor, feature, enhancement, patch, fix, chore, refactor etc

Changes to Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your core changes, as applicable?

I agree, that refactoring this code would add a lot of value.


Interaction between Mockery and Larastan

Larastan Version: 2.1.3
--level used: 8

Description
Larastan has a weird interaction with Mockery and https://github.com/phpstan/phpstan-mockery where it thinks the Expects type is an eloquent model, due to the use of the method name with to register method argument expectations (i think).
It causes lots of these false positives as a result:
  53     Relation 'route' is not found in PHPStan\Mockery\Type\Expects model.

I'm not sure how to create a pull request for that as i would need to install the phpstan/phpstan-mockery package to create a reproducible test case, probably not something that you want shipped by default.
However i forked larastan and did the following to recreate:

composer require phpstan/phpstan-mockery
add the following lines to the ./extension.neon

includes:
  - ./vendor/phpstan/phpstan-mockery/extension.neon

add the following lines to the ./tests/Rules/Data/relation-existence-rules.php

$mock = \Mockery::mock(\StdClass::class);

$mock->expects('foo')->with('bar');

php vendor/bin/phpunit tests/Rules/RelationExistenceRuleTest.php

PHPUnit 9.5.19 #StandWithUkraine

Runtime:       PHP 8.1.3

F                                                                   1 / 1 (100%)

Time: 00:01.251, Memory: 88.00 MB

There was 1 failure:

1) Tests\Rules\RelationExistenceRuleTest::testRule
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
 50: Relation 'foo' is not found in App\User model.
 51: Relation 'foo' is not found in App\User model.
 52: Relation 'foo' is not found in App\User model.
+56: Relation 'bar' is not found in PHPStan\Mockery\Type\Expects model.

Here you go Bred! #1205
PR-s are free.

i've had a look but unfortunately i don't understand phpstans type system well enough yet and i don't have a lot of time to spare at the moment
it seems this block in the ModelRuleHelper:
        if ((new ObjectType(Builder::class))->isSuperTypeOf($type)->no() &&
            (new ObjectType(EloquentBuilder::class))->isSuperTypeOf($type)->no() &&
            (new ObjectType(Relation::class))->isSuperTypeOf($type)->no() &&
            (new ObjectType(Model::class))->isSuperTypeOf($type)->no()
        ) {
            return null;
        }

is being passed over for the Expects type, using describe() to show the value reveals they are all maybe in that case, so PHPStan doesn't have enough information to assert that it's not the correct type
I've tried other approaches such as:

replacing isSuperTypeOf with  $type->getReflectionClass()->isSubclassOf(Builder::class) etc. but that breaks the current test cases and so is a no go
using $type->getReferencedClasses() but this list seems to be incomplete in some cases and causes tests to fail

if i get time i will try and look at this again but dunno when that will be

Anyone can jump in :)

        if ((new ObjectType(Builder::class))->isSuperTypeOf($type)->no() &&
            (new ObjectType(EloquentBuilder::class))->isSuperTypeOf($type)->no() &&
            (new ObjectType(Relation::class))->isSuperTypeOf($type)->no() &&
            (new ObjectType(Model::class))->isSuperTypeOf($type)->no()
        ) {
            return null;
        }

@mad-briller Can you try to change all those ->no calls to ->yes and negate the conditions? Like ! (new ObjectType(Builder::class))->isSuperTypeOf($type)->yes().
If that fixes your issue please send a PR with those changes.

Haha amazing, that did fix it and all the tests pass too, so simple and i couldn't see it. Thank you @canvural


Press Page: Add

Need to have a press page added for Journalists, media outlets, bloggers and our own clippings.
watermarked pictures with caption explanations e.g. mike speaking etc.
ref: leonie's new design. press.jpg.
how/who to contact for quotes, followups, interviews with Mike. etc.

Issues go stale after 60d of inactivity.


Trouble with test/pony/httpget/httpget.pony

I have compiled test/pony/httpget/httpget.pony, and ./httpget works fairly well. E.g. this works as expected:
./httpget http://rosettacode.org/wiki/Rosetta_Code
However, this doesn't:
./httpget http://rosettacode.org/wiki/Category:Pony
I get "Failed: GET http://rosettacode.org%2Fwiki%2FCategory/wiki/Category%3APony"
I suspect it's the ":" before "Pony".
Is this a bug, or is it just bad use of colon?

Nice catch! Fixed.


[CCXDEV-13089] Add a metric to count rapid recommendations archives by version

Description
This way we will be able to tell how many archives are using v1.1.0 and how many v2.0.0, for example, in order to monitor the canary rollout from Grafana.
Type of change

New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing steps
Not yet
Checklist

[ ] pre-commit run -a passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Attention: Patch coverage is 85.71429% with 2 lines in your changes missing coverage. Please review.

Project coverage is 85.86%. Comparing base (bf47b1f) to head (830293b).
Report is 12 commits behind head on main.

Files with missing lines
Patch %
Lines

ccx_messaging/watchers/stats_watcher.py
85.71%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #252      +/-   ##
==========================================
+ Coverage   85.78%   85.86%   +0.08%
==========================================
  Files          28       28
  Lines        1182     1196      +14
==========================================
+ Hits         1014     1027      +13
- Misses        168      169       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


String escape conversion can create accidental octal literal

TypeScript Version:  2.4.1
Code
"use strict"
console.log(`\x001`);

Playground link
Expected behavior:
Produces code that prints a null character followed by 1.
Actual behavior:
Produces this code:
"use strict";
console.log("\01");

This crashes because \01 is an octal literal, which isn't allowed in strict mode.
Note that this TypeScript code fails in a similar way:
console.log(`\u00001`);

Context:
This came up when converting the decaffeinate test suite to TypeScript, and the test case was based on a test from the CoffeeScript test suite. The CoffeeScript test suite has lots of edge cases like this, so I don't necessarily think this bug is likely to come up in real production code, but still would be good to fix. I was able to work around the issue (diff), so it's not blocking me, but CoffeeScript and Babel handle this sort of thing, so would be good if TypeScript did as well.

Sorry for the delay, thanks for reporting!


Support additional mutate expression types

It seems some mutate value expressions are not supported with this error being thrown from Operations.java#mutate:
A property container can only be mutated by a map, or a parameter or property pointing to a map.

Refer to the added test cases for the new expression support added by this PR.  I'm not sure if there are other expression types that should also be considered (or if it might actually be better to just accept any Expression and allow the query to fail at runtime?).

Great contribution, thank you!
You are maybe right with the expression. Might change in the future if another need comes up. Just waiting for the build to become green.


backintime-common: 1.1.12 -> 1.1.24

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
ran /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin/backintime -h got 0 exit code
ran /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin/backintime --help got 0 exit code
ran /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin/backintime -v and found version 1.1.24
ran /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin/backintime --version and found version 1.1.24
found 1.1.24 with grep in /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24

Success on x86_64-linux (full log)
Attempted: backintime-common
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24
gzipping man pages under /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin
patching script interpreter paths in /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24
/nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin/.backintime-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/sh"
/nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24/bin/backintime-askpass: interpreter directive changed from "/bin/sh" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24...
/nix/store/8dj6mrs62z7z7d42v0jwcwz7k46i927i-backintime-common-1.1.24

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: backintime-common
No log is available.

Success on aarch64-linux (full log)
Attempted: backintime-common
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24
gzipping man pages under /nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24/share/man/
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24/bin
patching script interpreter paths in /nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24
/nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24/bin/.backintime-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/sh"
/nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24/bin/backintime-askpass: interpreter directive changed from "/bin/sh" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24...
/nix/store/yavmyqbfivvh3sv7m89v5iq8a9sab988-backintime-common-1.1.24


Update wordlist

by China Digital times
https://docs.google.com/spreadsheets/d/1UTP9MU80r_N5WPhQ5-4AjM0ebW1eMxyDlRe_vaYy9IM/edit#gid=0
words from 2017/2018

excellent -- how much work to integrate these?

Just did a quick check, words from 2014-08-01 are not integrated in our current list, merging new words to the list should be pretty quick.

Please check: https://github.com/dhowe/ChinaEye/pull/80


Update dots alignment

I've noticed that every time i use slick (awesome plugin) the dots bar is not correctly aligned with the slider; figured out that a simple "left: 0;" will solve this problem!
Thanks for this awesome plugin!

What do you mean by the dots aren't aligned? Can you create a fiddle demonstrating the issue you are trying to resolve?

I'm working on the fiddle to demostrate the issue! I will link it here as soon as i can;
Thanks for your reply.

Hi! I've done some fiddles, but the issue seems to not appear, here you can see what I'm talking about (I've encountered this problem in many project before, maybe I'm doing something wrong)
Thanks for the support!


DisableGestures on specific pages

I have a menu on a navbar that when you click it, it opens the side menu. And you can also open it by swiping on the left just like in the example.
But I want that the gesture (swiping left) on some pages just pops() the stack and it goes back. To do this I would have to disable the gestures on the SideMenu. Any ideas on how I can achieve this on certain views?

Hm, sounds like a nice feature!

I think this is too specific to put into the project as a feature. I think this needs to be handle by you, @JoaoCnh. However, I want to see your implementation as well. Would you please create a simple code.

I'm going to export gesture hooks, @alinz :wink:

@Kureev do you know of anybody who has successfully achieved the behavior that @JoaoCnh described? I'd also like to disable swiping on certain pages

@ilanasufrin I have done it. There are so many ways to achieve this behavioural. Here are the two most common ones:
1: Without out any 3rd library:

create a method call disableGesture in a component which wraps SideMenu.
pass that function all the way down to all children.
if any of those children wanted to disable gesture, they call the function.
disableGesture is as follows:

disableGesture(value) {
   this.setState({
      gesture: value
   });
}

and  in your render function you just pass the state.gesture to gesture props.
2: second approach is a lot cleaner and I hope you have used it in your current app. if you don't, please start using flux like framework such as redux or reflux. You have to separate all business logic from UI as much as possible to make everything simpler.
If you need an example, I can make one for you.
Cheers.

@alinz Thx I'll definitely try this today and give some feedback

btw, I've investigated this a little bit more and can say that if we're talking about Navigator, then we can't override default behavior

@alinz you're right, I ended up doing it with a state that I set based on the component
disableGestures={this.state.menuShouldNotOpen}

@ilanasufrin nice! :+1:

@Kureev I think this ticket can be closed now!

use react native simple events.. simple solution

@akshaysinghi this approach is not my favourite because once it's been used, the traceability of event will be lost. What I mean is once the application becomes very large, it becomes very hard to find who's firing that event.
what I usually do is either encapsulate that event inside that component and I don't leak it out side or use flux-like system such as redux to maintain my actions.


Suggestion box incorrectly offset with translate animated container

When displaying monaco editor in a container that is slided into screen via translate animation, the suggestion box is offset incorrectly by (width of screen - width of container). Disabling the fixedOverflowWidgets option is not something we can do, as the suggestion box would be cut at editor length.

monaco-editor version: 0.30.0
Browser: Chrome Version 90.0.4430.93
OS: Ubuntu
Playground code that reproduces the issue:
const container = document.createElement("div");
container.className = "container";

const monacoElement = document.createElement("div");
monacoElement.className = "monaco";

container.appendChild(monacoElement);
document.body.appendChild(container);
monaco.editor.create(monacoElement, {
    language: 'javascript',
    fixedOverflowWidgets: true,
});

.container {
    width: 550px; /* increase/decrease to see offset change */
    height: 100vh;
    display: block;
    position: fixed;
    right: 0;
    bottom: 0;
    top: 0;
    border: 1px solid black;
    transform: translateX(100%);
    animation: translateAnimation 1s cubic-bezier(0.19, 1, 0.22, 1) both;
}

.monaco {
    width: 100%;
    height: 300px;
}

@keyframes translateAnimation {
    0% {
        transform: translateX(100%);
    } 100% {
        transform: translateX(0);
    }
}

Here's much simpler example:

monaco.editor.create(document.getElementById('container'), {
	value: "function hello() {\n\talert('Hello world!');\n}",
	language: 'javascript',
    fixedOverflowWidgets: true
});

And then try to hover or type something

@alexdima Do you have any estimations on how much time can the fix take? It's quite a critical issue for us as we're trying to render the editor inside a draggable panel. Maybe I can help with the PR if you give me some guidance and keywords?

@mifopen a PR would be most welcome. Depending on the setting fixedOverflowWidgets or the option of the content widget to allowEditorOverflow, here is the code responsible for positioning content widgets.

@promeris @alexdima Fixed elements inside transformed parents are positioned relatively to those transformed parents and not the body. http://meyerweb.com/eric/thoughts/2011/09/12/un-fixing-fixed-elements-with-css-transforms
You can find dozens of issues and questions on the web regarding this.
I don't think it'd be pragmatic to try to detect this case inside vscode (what if we have nested transforms 😬).
For me the fix is eventually the following:
...
    fixedOverflowWidgets: true,
    overflowWidgetsDomNode: document.getElementById('monaco-editor-overflow-widgets-root')!,
...

        ...

It looks like a legal way to escape transformed subtree. Anyway if you want your widgets to be fixed it doesn't matter where exactly in DOM they will be rooted (if the root is not transformed 😅).

Thanks for the information! They are super helpful.
However, I found another issue with the overflow widget: the document details panel is not ported under the given overflow widget element

Please use the following playground link for reproduction.

type fun on the keyboard
click on the > at the end of the auto-completion entry
found the doc details panel is under the red overlay

link

https://microsoft.github.io/monaco-editor/playground.html?source=v0.44.0#XQAAAALrAQAAAAAAAABBqQkHQ5NjdzmO6ObloP9xmco32Ozz4i7pNjj5tnnl_C2HstXj9Aq8RCnj9VWChsLAuxk3WXbM1XzM873zdu9e6mjsn1ihzJoM7Y_mqTh3hc86qbHa9YJ2h0YsmohXK5oIaP0BkzfX9j9RCqCQx14N5qGHeULEMy7c2gxgCzwFZetRhoKfx6bkhnoq7I_Qoe9gzmoQZZRh9hJEJAJgGqa6CuKUiui-VQxavt79Yk-2C7jcGWlFxgf6jD6pCCKy9BCqXNs3uyUsfNyScs_OXYnQeJ7QNVRuRMiLs1yzcpQYsnUT91jIaNDxv12dN6KCnVbyacaRpaMM2fiY8ifXWat18ffqLbjznasSipjBfLxMCsdOYomfpleaKnz0A8CNA87uif7Xl4LNhe-cfegPS3oU5ehp-SxqR6f1Sj8DQV0___f7tM4

Could anybody help to fix it?

@xloc this has been recently improved via https://github.com/microsoft/vscode/pull/198730 . Could you please try with the latest editor nightly version?

Sorry, how can I access the latest version? I tried the latest version on the playground site though, which is 0.46.0-dev-20231214. The problem is still there.
playground-link

Sorry about that, we're having a hiccup with the nightly build, the 0.46.0-dev-20231214 doesn't contain that change.

no problem at all. Thanks for your support! I can take a look later.
BTW, do you know typically how long a bug will take to be merged into the stable version? or where can I get this kind of info?

BTW, do you know typically how long a bug will take to be merged into the stable version? or where can I get this kind of info?

We typically release a new editor version at the same time with a vscode release.

For anyone facing that issue on older monaco-editor versions:
I managed to workaround this issue by removing all properties that lead to new stacking context.
We show monaco editor inside a popup which has an enter animation with opacity so I'm removing will-change and animation-name on animationend event

Issue seems to persist in 0.47.0. Any updates?


Multiple Forms in one Template and other questions

Hi,
Thanks for this awesome editor!

I  want to use this editor to provide a form with 4 fields that lets users add title, description, another description and lets them chose an item from a dropdown list.
I want to give them the same form twice, once without data (when they wont to add a new entry) and once with predefined data (when they want to edit an existing entry)
How to do this? The documentation does not explain.
specifically: how to start a form without data? with multiple fields? and a fixed hight?

 I cant grab it, its too quick.

and in general. when the official docs say: link

HTML

Set a specific height to the WYSIWYG HTML editor using the height option. If the text inside is longer, then the rich text editor will get a vertical scrollbar.

JAVASCRIPT

how would i translate this into meteor?

Hi,
The froala-reactive is a simple wrapper over the actual FE editor, providing some basic reactivity integration with the Meteor framework.

I think this is a wider question about how to use Meteor, rather than a specific issue with this package.  I suggest you start with some of the excellent tutorials out there. The Discover Meteor book is well worth purchasing too.  You may also want to check out the donchess:autoform-froala package. That is an alternative wrapper package to this one. Never used it myself, but might help you with integrating with the autoform package eco-system, which makes form handling in Meteor very easy.

I have seen this behaviour also. I have disabled the quick insert plugin in my own application for now. I think this is a core issue with FE rather than this wrapper package.

Did you follow the README for this package? You can set any of the FE options when you initialise the template.
e.g:

<template name="myTemplate">
{{> froalaReactive getFEContext}}
</template>

Template.myTemplate.helpers(function () {
  getFEContext: function () {
    return {
      height: 300
    }
  });

Closing


Multiple accounts Web login

Rewritten InstagramLoginWebView to allow for multiple accounts to log in without cache and cookie conflicts #27.
I tried to keep everything as close as possible to what is used to be, while greatly reducing the amount of code, but support for less than iOS 11 had to be dropped (I feel like it's not a big issue, though, since once can simply rely on Siwa instead, and iOS 10 is not that popular anymore), as well as preloaders, which are quite an easy addition though (and I feel like they should be left to the developers implementing the library of their own accord).
(Bonus: no more WKCookieWebView 🎉)

Thanks for this update, a lot of users using this library with iOS 10.0 and higher compatibility.
If we simply remove support for iOS 10.0 in web login, they may face a problem and needs a lot of work to handle login via Siwa, most people prefer to use web login instead of native login.
So I suggest to keep the older version for iOS 10.0 and add this update for iOS 11.0 and higher.

I actually might have an iOS 10 compatible fix 😊
I'm working on it as soon as I have the time.

Sounds good, I think we should wait for this fix to merge both PR.
There is a possibility for users to update the library and causes issue for their app.
Thanks.

So… apparently the version already on master doesn't work on iOS 10, because httpOnly cookies (specifically session_id in our case) are already not caught by WKCookieWebView, so if somebody was to actually try it on iOS 10 the login would always either fail or fallback to already cached session_id, thus not actually changing account.
I feel like, since it doesn't work already, actually hiding the deceleration behind a @available(iOS 11, *) check might be a big improvement, avoiding users hours of trying to figure out why it's not working just to then find out it simply could not on their iOS 10 device.


Fragment parsed incorrectly is multiple # characters

The fragment is parsed incorrectly if it includes a # character.  This causes part of the fragment to be included in the path.  Example:
$ ./faup -o json "http://penlakes.typepad.com/the_personal_blog_of_tom_/#tp_blog_of_tom_/#tp"
{
"scheme": "http",
"credential": "",
"subdomain": "penlakes",
"domain": "typepad.com",
"domain_without_tld": "typepad",
"host": "penlakes.typepad.com",
"tld": "com",
"port": "",
"resource_path": "/the_personal_blog_of_tom_/#tp_blog_of_tom_/",
"query_string": "",
"fragment": "#tp",
"url_type": "mozilla_tld"
}

Thanks for reporting this, I will have a look ASAP