Major refactor of kube-aws tool

kube-aws can now generate all assets/templates. We can now distribute just the binary.

No S3 intermediary. All assets are compressed on kube-aws up and sent directly to cloudformation api.

kube-aws render generates a reproducible cluster asset pack which contains tls assets and all templates

Much simpler templating pipeline. Single templating phase on kube-aws up.

New validate command to validate user-data and stack json

Replace confusing cloudformation parameters kube-aws up --update, which will update the cloudformation stack.

Unit tests for all config modules

Replace godeps with glide!

Pretty much everything has changed. To try it out for yourself, check out the new readme
We aren't hosting the pre-compiled binary yet, so you'll have to compile it yourself. Once you have the binary, there is no dependency on the project tree. The design goal here is to be able to distribute "just the binary" when we release.

Here's the working list of things that should be sorted out before we roll this up into a major release. The goal is to offer a "production ready solution" for provisioning a coreos kubernetes cluster. These are the major functionality blockers that I can think of.

[ ] Use AWS KMS to secure TLS assets. Provision/specify KMS key, and have kube-aws encrypt TLS assets, and nodes decrypt them using the API. The cloudformation will no longer contain un-encrypted TLS secrets! (Shout out to @mfburnett for this idea)

[ ] Support multiple controller/etcd instances (HA control plane)

[ ] EBS volume attachment for controller(s). Update procedure will detach EBS volume from old controller instance and reattach to new controller instance. This will preserve cluster state in the event the controller(s) are updated and replaced as a result of cloudformation update.

[ ] Secure etcd peer/client connections with TLS

[ ] Route53 integration for APIServerEndpoint. Automatically create hosted-zone and/or A record for controller EIP on kube-aws up

[ ] Put controller(s) into AutoscalingGroup

[ ] Set up controller and worker AutoscalingGroups to recover from ec2 instance failures

Would you be able to break out the godeps updates into a separate commit(s) to make reviewing a bit easier?

great idea.

@aaronlevy I've addressed the "isolated" issues on the PR so far with this batch of commits. @ericchiang is going to help figure out a better templating/buffer approach for this PR.
He requested that we review these commits, squash it up and break out 3 discrete commits

Go Code
Vendored Deps
Docs

Then the discussion can continue

@ericchiang added some commits building on what you've got. the tool works now and is feature complete with where it was.
cc\ @aaronlevy

@colhom it might be best to squash these commits now. They're a little unreadable ATM (I know I'm partially responsible for this).

@aaronlevy, commits split up and rebased on master.

Should we be committing multi-node/aws/pkg/config/templates.go or can we have that generated during the build process?

Ugh and this is saying all my comments are out of date :(
Is there any reason to keep the original commit if it's basically thrown away? I'll start commenting on the last commit .. but this is difficult to review

Closing in favor of https://github.com/coreos/coreos-kubernetes/pull/315.
Same code, just cleaned up a bit to make review easier.

I lied, this was moved to: https://github.com/coreos/coreos-kubernetes/pull/316


Attempted import error: 'OperationTypeNode' is not exported from 'graphql' (imported as 'OperationTypeNode').

next-js dev build fails with the following:
Attempted import error: 'OperationTypeNode' is not exported from 'graphql' (imported as 'OperationTypeNode').

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./lib/apollo-provider.tsx

// lib/apollo-provider.js
'use client'

import { ApolloLink, HttpLink } from '@apollo/client'
import {
  NextSSRApolloClient,
  ApolloNextAppProvider,
  NextSSRInMemoryCache,
  SSRMultipartLink,
} from '@apollo/experimental-nextjs-app-support/ssr'

function makeClient() {
  const httpLink = new HttpLink({
    uri: 'http://localhost:3000/api/graphql',
  })

  return new NextSSRApolloClient({
    cache: new NextSSRInMemoryCache(),
    link:
      typeof window === 'undefined'
        ? ApolloLink.from([
            new SSRMultipartLink({
              stripDefer: true,
            }),
            httpLink,
          ])
        : httpLink,
  })
}

export function ApolloWrapper({ children }: React.PropsWithChildren) {
  return (
    <ApolloNextAppProvider makeClient={makeClient}>
      {children}
    </ApolloNextAppProvider>
  )
}

"dependencies": {
    "@apollo/client": "^3.8.0-rc.0",
    "@apollo/experimental-nextjs-app-support": "^0.0.0-commit-473354a",
    "graphql": "^15.8.0",
    "next": "13.4.6",
    "react": "18.2.0"
}

Yeah, this is an unexpected import that somehow made it into the current Apollo Client RC - will be fixed over there. In the meantime, please use graphql 16, that one has that export.

FYI, the PR is open to fix this here: https://github.com/apollographql/apollo-client/pull/11071. This will go out in the next rc release.

@bridgeclimbs v3.8.0-rc.1 was just released that fixes this issue. Please upgrade to that version to get this fix. Let us know if you need anything else!


STORM-3097: Remove storm-druid

This is the follow on to  #2706 which deprecates storm-druid for 1.x releases.

Remember https://github.com/apache/storm/blob/master/docs/storm-druid.md and any links in the other docs referring to druid. +1 otherwise.

Thanks @srdo I removed storm-druid.md and removed the link form index.md (which was the only one I could find)

Thanks, +1 again

My bad. I should have closed #2704 instead of this. Will merge this.

Closed in 0eb6b5116f251e17b6f14a61cebfadfc286faa59


Fix possibly reading uninitialised variables due to continue

repeat
    continue
    local a = 1
until a > 0

This code is now treated like a > 0 refers to a global called 'a'.

Could consider a warning for this in 0.9.0


ERROR in app.android.js from UglifyJs Unexpected token: name (Feedback)

Hi first of all thank you for the plugin , i am trying to use the plugin in nativescript-vue but i get this error when compiling .
ERROR in app.android.js from UglifyJs
Unexpected token: name (Feedback)

Steps to reproduce the issue
1 - installing the plugin via npm
2 - adding the plugin
import { Feedback } from 'nativescript-feedback'

3 - adding vue prototype
Vue.prototype.$feedback = new Feedback();

Env
    "nativescript-vue": "^1.2.0",
    "tns-core-modules": "3.4.1",
     "nativescript-feedback": "^1.2.0",

hi, sadly i facing the some issue here (with the ns-vue)
any workaround on it guys?
env:
"tns-core-modules": "~3.4.1",
"nativescript-vue": "^1.3.1",
"nativescript-feedback": "^1.3.9",

I'm using it like this without issues in a Vue project: https://github.com/EddyVerbruggen/footplr/blob/master/app/utils/feedback-util.ts

Hi Eddy, i found the problem was the uglify.js used in ns-vue version 1.3.1 not supporting the es6 things. Running on debug mode will not trigger any error, but hitting build did.
My workaround is put try-catch block inside the web pack-config that handle plugin, and there its. Your plugin works as charms.
*some advices are highly appreciated
Last, thank you @EddyVerbruggen for such a great plugin 🎉🎉


Incompatible with Nimble

Is it a mod compatibility issue?
Yes
If it's a mod compatibility issue, please provide the link(s) to the incompatible mod(s)
https://modrinth.com/mod/nimble
Minecraft version
1.20
Describe the issue
Incompatible with Nimble 4.2.0 with shader activated

I only see sky from nether.
I only see white from overworld.
Still works with 1st person.

btw I changed the Nimble in jar file to be depends >=1.20.0 of mc version

Does this issue occur in 1.20.1?


Planning create a fork use crystal-lang (Done!)

Hi, Crystal version's procodile is available, please check release page
The main advantage over current ruby version is:

precompiled static binary available directly for linux/MacOS.
less memory footprint.
speed, although, This benefit may not be obvious.

Hi,  the Crystal fork of  procodile 1.0.20 1 is there.
it feature completed now, anyone want to try it, can download mac/linux binary directly from there.
Thanks

The Crystal fork released v.1.0.25, except the --proxy feature(consider this feature not so useful anyway), all have been done, even more robust.
deployment is more easier too, just a static portable binary file, copy and use it.


When ESP32_RTC_CLK_SRC_INT_8MD256=y , wakeup from deep sleep time wrong (IDFGH-7938)

I'm using the sntp example .
When by menuconfig, I set :
CONFIG_RTC_CLK_SRC = Internal 150KHz , it's working and the cpu is waked up after 10 s
CONFIG_RTC_CLK_SRC = Internal 8MHz, it's working but  the cpu is waked up after about 3 min
Did I missing anything ?

I used ESP32-C3-MINI-1.
And the time printed when waked up is the first time + 10s.
Not the correct time.
Ex. Start time  15:00:00
Waked up time 15:03:05 but printed time is 15:00:10 .

Which esp-idf version are you using? (git describe --tags)

I'm using the esp-idf  of
v5.0-dev-4379-g36f49f361c

Which esp-idf version are you using? (git describe --tags)

v5.0-dev-4379-g36f49f361c

Confirm the same issue on v5.1-dev-224-g4d14c2ef2d with ESP32-C3-MINI-1.

@KonstantinKondrashov Any update?

I just encountered this issue myself in my attempts to test how much drift there is in deep-sleep with 8MHz RTC-clock. It's clear that the time to spend in sleep is calculated wrong with the 8MHz-clock.

Hi all, the fix is under review.

Hi all, the fix is under review.

Any update?

@AxelLin I assume they were referring to the pull-request that's been sitting around for half a year now with zero activity. I don't see anything else relevant there, nor does @lennyJL seem to be associated with Espressif anyways, so I doubt they have any insider information on some non-public pull-requests.

Hi @WereCatf. I am working in Espressif. And we have an internal gitlab MR for this issue. The MR contains more, still need some time to merge and sync to github. If you really need this fix now(for esp32c3), can you please try to change:
out_config->dbg_atten_slp = atten_deep_sleep;

to:
#define RTC_CNTL_DBG_ATTEN_DEEPSLEEP_NODROP   0
out_config->dbg_atten_slp = !(sleep_flags & RTC_SLEEP_PD_INT_8M) ? RTC_CNTL_DBG_ATTEN_DEEPSLEEP_NODROP : atten_deep_sleep;

This part of the code is in components/esp_hw_support/port/esp32c3/rtc_sleep.c, and in function rtc_sleep_get_default_config. I think the fix is similar for other chips. And note that this may not be the final fix.

@lennyJL Ok, I stand corrected. I only went by what was on your profile, which did not mention any association with Espressif.
That said, it is nice to get a clarification on what's going on. Appreciated.

Hi @WereCatf. I am working in Espressif. And we have an internal gitlab MR for this issue. The MR contains more, still need some time to merge and sync to github.

@lennyJL
It seems does not make sense that you need more than 1 month to merge and sync to github.

Sorry @AxelLin, the related MR was not provided by me. Currently, you can use the temporary fix for your project.

Sorry @AxelLin, the related MR was not provided by me. Currently, you can use the temporary fix for your project.

Any chance to contact related people for handling the MR?

@KonstantinKondrashov any update?
This initial issue was "the deep sleep mode doesn't work when CONFIG_ESP32_RTC_CLK_SRC_INT_8MD256", which was reported a year ago (https://github.com/espressif/esp-idf/issues/8007).
It still does not work well due to the wrong wakeup time (this issue). This is not a pleasent experience.

@AxelLin I asked the responsible for this issue person to get in touch here. Probably he can provide a patch here. (There is an MR in our internal repo, but it is still under review).

@AxelLin I asked the responsible for this issue person to get in touch here. Probably he can provide a patch here. (There is an MR in our internal repo, but it is still under review).

The fix is under review since Oct 19 (https://github.com/espressif/esp-idf/issues/9455#issuecomment-1284026549).
This makes me wonder what is the reasonable time for review.
I cannot tell if it's forgotten or something wrong or blocked for some reason if it takes such long time.
People are waitting for the bug fix for stable trees, which will take even more time.

Hi @cssword @WereCatf @AxelLin ,
Sorry for bad experience...
We noticed this issue, but the reviewing and testing work is a bit above our expectation. The issue is an analog issue, where there is a trade-off between power consumption and the functionalities of each part of hardware. Moreover, the behavior is different on different chips, so we need to do testing on plenty of chips...
As an alternative, I will give you a patch on v5.0-dev-4379-g36f49f361c with the latest parameter we are trying, to see if it solves your problem. But please understand that we still need some time to do more testing before it can be merged, and there  may also be some changes in the merged version.

@ginkgm Well, I wouldn't mind trying the patch out. Tacking on an external crystal to existing PCBs that were designed without a crystal there is pretty much a no-go and the 32768Hz internal oscillator is too imprecise to be even remotely useful.

https://github.com/espressif/esp-idf/issues/6687#issuecomment-1316769420

oh , sorry, I ignored the chip you are using is ESP32-C3.
The condition there is more complex, because we are having a big refactoring (similar to S3), splitting power modes into smaller ones, to optimize the power consumption in different use cases. https://github.com/espressif/esp-idf/blob/master/components/esp_hw_support/port/esp32s3/rtc_sleep.c#L77
To fix your issue quickly. May I know whether you are using ADC or Temp sensor in deep sleep mode? (via ULP)

@ginkgm I actually use ESP32 and ESP32-S2; it was another commenter who uses C3.

Hi @cssword @WereCatf @AxelLin ,
Sorry for bad experience...
We noticed this issue, but the reviewing and testing work is a bit above our expectation. The issue is an analog issue, where there is a trade-off between power consumption and the functionalities of each part of hardware. Moreover, the behavior is different on different chips, so we need to do testing on plenty of chips...

@ginkgm
How is the status now?
Could you list which chips are tested with fixes, which chips still need fix?

Hi @AxelLin ,
I think all existing chips need further adjustment. Among them ESP32 have already some progress:
ESP32:

Target Branch
Merged
Supported
Last N.A.

release/v5.0
null
null
v5.0

release/v4.4
e1e9e10
null
v4.4.4

release/v4.3
null
null
v4.3.4

master
84a6c6f
v5.1
null

Sorry again, but there is still no progress for other chips. And I don't expect this to happen in a short time..

@ginkgm This is marked as "Resolution: Done", does that mean it's fixed for all chips?

Hi @AxelLin ,
I think all existing chips need further adjustment. Among them ESP32 have already some progress:
Sorry again, but there is still no progress for other chips. And I don't expect this to happen in a short time..

@ginkgm
It has been a while since your last reply. Any update for other chips? (There is an issue reported for ESP32S3 in above link)


Fixing logic error

Fix issue found by OpenBMC on latest version of gcc.

I agree @edtanous, I think the length should be a parameter to the constructor. I will check and change it. Thanks for pointing it out


VS Code's highlighting suddenly changed.

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

VS Code Version: 1.75.1
OS Version: Windows_NT x64 10.0.19045

Steps to Reproduce:
I'm not sure. I don't change anything.
Current Condition:
So if you check properly, the commented code block was using the same color as the non-commented block.
This could annoy and probably cause unwanted attraction while coding. Moreover, some variables color changed as well.
I was not able to distinguish some things because the color changed.
I am using WSL2.

Expected Condition:
Well, I will update once I have an old file of my code. But I do know it's so different.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.81.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Nevermind, it was caused by an extension Javascript and TypeScript Nightly. I guess it was an overlapping issue. I thought I wanted to fix them by installing the right extensions, but idk, turns out that extensions caused another problem.


quiche: update QUICHE DEPS

Signed-off-by: Renjie Tang<EMAIL_ADDRESS>

/assign @RyanTheOptimist

/assign @alyssawilk

Hm, looks like CI needs a look?
/wait

Hm, looks like CI needs a look?
/wait

Ah! @RenjieTang this is the result of a QUICHE change I landed:
Execution platform: @rbe_ubuntu_clang_libcxx//config:platform
source/extensions/filters/http/alternate_protocols_cache/filter.cc:58:71: error: no member named 'max_age' in 'spdy::SpdyAltSvcWireFormat::AlternativeService'
          time_source_.monotonicTime() + std::chrono::seconds(alt_svc.max_age);

You'll need to change max_age to max_age_seconds.
@alyssawilk, if this PR lands before https://github.com/envoyproxy/envoy/pull/18189 then you'll need to make the corresponding change there too.

@alyssawilk, if this PR lands before #18189 then you'll need to make the corresponding change there too.

Ah! That just landed. So @RenjieTang you'll need to to a merge, and make the another max_age => max_age_seconds change.

/lgtm deps

/retest

/retest

@moderation can you re-approve for deps

/lgtm deps


chore: dc-jenkins-go to 0.0.1

chore: Promote dc-jenkins-go to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Remove UI folder

We've decided to remove UI for now, and wrap everything into one helpers folder.

I've just removed the UI message handler for now.


The function page.screenshot  can't capture a full web page which height is more than 4500(approximately)

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.12.2+  (the previous version is ok)
Platform / OS version: OS X macOS Mojave 10.14.6
URLs (if applicable):
Node.js version: 10.15.1

What steps will reproduce the problem?
Please include code that reproduces the issue.
1.Find a page which height is more than 5000.(Just suppose its height is 10000)
2.page.goto(url)
3.page.screenshot({ path: 'example.png', clip: { x: 0, y: 0, width: 750, height: 10000 } });
What is the expected result?
The example.png should be  the correct screenshot of the full  page.
(In the previous version of 1.12.2, it is)

What happens instead?
The example.png is not entire.The part over 4500(approximately) shows blank.

I met the same problem

+1


node-red - node name with accented characters not displayed correctly - lead to deployment issue

Current Behavior
I recently did the upgrade to node-red 4.
I live in belgium and I have a lot of node name containing accented characters. Those nodes are not displayed correctly (encoding issue ?) and that leads to an issue when I do the deployment (homekit bridge).
Previous version 2 did not have this issue.
Expected Behavior
node name containing accented characters are displayed correctly
Steps To Reproduce
create a node with accented character, deploy it.
when you then do a refresh of the page, the name is not displayed correctly
Example flow
paste your flow here

Environment

Node-RED version: nodered/node-red:latest-22
Node.js version:
npm version:
Platform/OS: docker
Browser: Chrome / Safari

Can you export an example node that demonstrates the issue and share the JSON here?

sure herefater an export performed from the node-red dashboard - you can see the encoding issue
[{"id":"d9721bad.3ca858","type":"subflow","name":"OH State changed","info":"","category":"","in":[],"out":[{"x":920,"y":140,"wires":[{"id":"bd1ad28e.739b1","port":0}]}],"env":[],"meta":{},"color":"#DDAA99"},{"id":"9023a5d0.72dc28","type":"switch","z":"d9721bad.3ca858","name":"OnOff","property":"payload.type","propertyType":"msg","rules":[{"t":"eq","v":"OnOff","vt":"str"},{"t":"eq","v":"Percent","vt":"str"}],"checkall":"true","repair":false,"outputs":2,"x":530,"y":100,"wires":[["bd1ad28e.739b1"],[]]},{"id":"6a2150b7.39ff5","type":"switch","z":"d9721bad.3ca858","name":"ItemStateChangedEvent","property":"type","propertyType":"msg","rules":[{"t":"eq","v":"ItemStateChangedEvent","vt":"str"}],"checkall":"true","repair":false,"outputs":1,"x":330,"y":60,"wires":[["9023a5d0.72dc28"]]},{"id":"bd1ad28e.739b1","type":"switch","z":"d9721bad.3ca858","name":"StateChanged","property":"payload.value","propertyType":"msg","rules":[{"t":"neq","v":"payload.oldValue","vt":"msg"}],"checkall":"true","repair":false,"outputs":1,"x":760,"y":140,"wires":[["b18bbc81740885fb"]]},{"id":"d3f0397d70df8d01","type":"openhab2-events2","z":"d9721bad.3ca858","name":"","controller":"b3a23998cda0088c","itemname":"","x":130,"y":400,"wires":[["6a2150b7.39ff5"]]},{"id":"b18bbc81740885fb","type":"debug","z":"d9721bad.3ca858","name":"OH 'switch' event occured","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":1020,"y":200,"wires":[]},{"id":"b3a23998cda0088c","type":"openhab2-controller2","z":"d9721bad.3ca858","name":"CMLK-V3","protocol":"http","host":"<IP_ADDRESS>","port":"8080","path":"","username":"","password":"","ohversion":"v3","token":""},{"id":"584796d7.0845f8","type":"subflow","name":"OH Switch state changed","info":"","category":"","in":[],"out":[{"x":680,"y":120,"wires":[{"id":"981e0a66.4e4218","port":0}]},{"x":680,"y":180,"wires":[{"id":"c015303b.46f5d","port":0}]}],"env":[],"color":"#DDAA99"},{"id":"52c0e850.d0d888","type":"subflow:d9721bad.3ca858","z":"584796d7.0845f8","name":"","env":[],"x":140,"y":60,"wires":[["c015303b.46f5d"]]},{"id":"c015303b.46f5d","type":"change","z":"584796d7.0845f8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"payload.value","tot":"msg"},{"t":"set","p":"topic","pt":"msg","to":"$split(msg.topic, "/", 4)[2]","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":340,"y":80,"wires":[["981e0a66.4e4218"]]},{"id":"981e0a66.4e4218","type":"function","z":"584796d7.0845f8","name":"OH2HK_switch","func":"if (msg.payload == "ON") {\n    msg.payload = {\n        "On": true\n    };\n} else {\n    msg.payload = {\n        "On": false\n    };\n}\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","x":540,"y":100,"wires":[[]],"info":"openhab2-in"},{"id":"fae402b9.436ba","type":"tab","label":"exterior switch","disabled":false,"info":""},{"id":"5eda0fb.a8131f","type":"homekit-service","z":"fae402b9.436ba","isParent":true,"hostType":"0","bridge":"de31e0ee.c7354","accessoryId":"","parentService":"","name":"Entr�e","serviceName":"Lightbulb","topic":"","filter":false,"manufacturer":"NRCHKB","model":"1.2.0","serialNo":"Default Serial Number","firmwareRev":"1.2.0","hardwareRev":"1.2.0","softwareRev":"1.2.0","cameraConfigVideoProcessor":"ffmpeg","cameraConfigSource":"","cameraConfigStillImageSource":"","cameraConfigMaxStreams":2,"cameraConfigMaxWidth":1280,"cameraConfigMaxHeight":720,"cameraConfigMaxFPS":10,"cameraConfigMaxBitrate":300,"cameraConfigVideoCodec":"libx264","cameraConfigAudioCodec":"libfdk_aac","cameraConfigAudio":false,"cameraConfigPacketSize":1316,"cameraConfigVerticalFlip":false,"cameraConfigHorizontalFlip":false,"cameraConfigMapVideo":"0:0","cameraConfigMapAudio":"0:1","cameraConfigVideoFilter":"scale=1280:720","cameraConfigAdditionalCommandLine":"-tune zerolatency","cameraConfigDebug":false,"cameraConfigSnapshotOutput":"disabled","cameraConfigInterfaceName":"","characteristicProperties":"{}","waitForSetupMsg":false,"outputs":2,"x":510,"y":40,"wires":[["b5fe1e6f.f9086"],[]],"icon":"node-red/light.svg"},{"id":"b84cd1ad.5ca6b","type":"homekit-service","z":"fae402b9.436ba","isParent":true,"bridge":"de31e0ee.c7354","parentService":"","name":"Terrasse","serviceName":"Lightbulb","topic":"","filter":false,"manufacturer":"NRCHKB","model":"1.2.0","serialNo":"Default Serial Number","firmwareRev":"1.2.0","hardwareRev":"1.2.0","softwareRev":"1.2.0","cameraConfigVideoProcessor":"ffmpeg","cameraConfigSource":"","cameraConfigStillImageSource":"","cameraConfigMaxStreams":2,"cameraConfigMaxWidth":1280,"cameraConfigMaxHeight":720,"cameraConfigMaxFPS":10,"cameraConfigMaxBitrate":300,"cameraConfigVideoCodec":"libx264","cameraConfigAudioCodec":"libfdk_aac","cameraConfigAudio":false,"cameraConfigPacketSize":1316,"cameraConfigVerticalFlip":false,"cameraConfigHorizontalFlip":false,"cameraConfigMapVideo":"0:0","cameraConfigMapAudio":"0:1","cameraConfigVideoFilter":"scale=1280:720","cameraConfigAdditionalCommandLine":"-tune zerolatency","cameraConfigDebug":false,"cameraConfigSnapshotOutput":"disabled","cameraConfigInterfaceName":"","characteristicProperties":"{}","waitForSetupMsg":false,"outputs":2,"x":540,"y":160,"wires":[["5bd51563.fa0abc"],[]],"icon":"node-red/light.svg"},{"id":"b5fe1e6f.f9086","type":"function","z":"fae402b9.436ba","name":"HK2OH_switch","func":"if (msg.hap.context !== undefined ) {\n    if(msg.payload.On === false) {\n        msg.payload = "OFF";\n    }\n    else {\n        if(msg.payload.On === true) {\n            msg.payload = "ON";\n        }\n    }\n    return msg;\n}","outputs":1,"noerr":0,"initialize":"","finalize":"","x":800,"y":40,"wires":[["276d6183.09239e"]]},{"id":"5bd51563.fa0abc","type":"function","z":"fae402b9.436ba","name":"HK2OH_switch","func":"if (msg.hap.context !== undefined ) {\n    if(msg.payload.On === false) {\n        msg.payload = "OFF";\n    }\n    else {\n        if(msg.payload.On === true) {\n            msg.payload = "ON";\n        }\n    }\n    return msg;\n}","outputs":1,"noerr":0,"initialize":"","finalize":"","x":800,"y":160,"wires":[["6faa6766.45e828"]]},{"id":"276d6183.09239e","type":"openhab2-out","z":"fae402b9.436ba","name":"","controller":"cc6a2e2f.c5c25","itemname":"light_entryway_ext","topic":"ItemCommand","payload":"","x":1030,"y":40,"wires":[[]],"icon":"node-red/light.svg"},{"id":"6faa6766.45e828","type":"openhab2-out","z":"fae402b9.436ba","name":"","controller":"cc6a2e2f.c5c25","itemname":"light_terrace","topic":"ItemCommand","payload":"","x":1010,"y":160,"wires":[[]],"icon":"node-red/light.svg"},{"id":"1fa627f57d6d1e7b","type":"homekit-service","z":"fae402b9.436ba","isParent":true,"hostType":"0","bridge":"de31e0ee.c7354","accessoryId":"","parentService":"","name":"Ext�rieur buanderie","serviceName":"Lightbulb","topic":"","filter":false,"manufacturer":"NRCHKB","model":"1.2.0","serialNo":"Default Serial Number","firmwareRev":"1.2.0","hardwareRev":"1.2.0","softwareRev":"1.2.0","cameraConfigVideoProcessor":"ffmpeg","cameraConfigSource":"","cameraConfigStillImageSource":"","cameraConfigMaxStreams":2,"cameraConfigMaxWidth":1280,"cameraConfigMaxHeight":720,"cameraConfigMaxFPS":10,"cameraConfigMaxBitrate":300,"cameraConfigVideoCodec":"libx264","cameraConfigAudioCodec":"libfdk_aac","cameraConfigAudio":false,"cameraConfigPacketSize":1316,"cameraConfigVerticalFlip":false,"cameraConfigHorizontalFlip":false,"cameraConfigMapVideo":"0:0","cameraConfigMapAudio":"0:1","cameraConfigVideoFilter":"scale=1280:720","cameraConfigAdditionalCommandLine":"-tune zerolatency","cameraConfigDebug":false,"cameraConfigSnapshotOutput":"disabled","cameraConfigInterfaceName":"","characteristicProperties":"{}","waitForSetupMsg":false,"outputs":2,"x":550,"y":100,"wires":[["aa3e2acac02e89b9"],[]],"icon":"node-red/light.svg"},{"id":"aa3e2acac02e89b9","type":"function","z":"fae402b9.436ba","name":"HK2OH_switch","func":"if (msg.hap.context !== undefined ) {\n    if(msg.payload.On === false) {\n        msg.payload = "OFF";\n    }\n    else {\n        if(msg.payload.On === true) {\n            msg.payload = "ON";\n        }\n    }\n    return msg;\n}","outputs":1,"noerr":0,"initialize":"","finalize":"","x":800,"y":100,"wires":[["ab2cd2bcff21c715"]]},{"id":"ab2cd2bcff21c715","type":"openhab2-out","z":"fae402b9.436ba","name":"","controller":"cc6a2e2f.c5c25","itemname":"light_laundry_ext","topic":"ItemCommand","payload":"","x":1030,"y":100,"wires":[[]],"icon":"node-red/light.svg"},{"id":"a3487e04a8e7ea29","type":"link in","z":"fae402b9.436ba","name":"li_light_laundry_ext","links":[],"x":915,"y":140,"wires":[["ab2cd2bcff21c715"]]},{"id":"c45c78a5d7bf678b","type":"switch","z":"fae402b9.436ba","name":"EXT Switch","property":"topic","propertyType":"msg","rules":[{"t":"eq","v":"light_entryway_ext","vt":"str"},{"t":"eq","v":"light_laundry_ext","vt":"str"},{"t":"eq","v":"light_terrace","vt":"str"}],"checkall":"false","repair":false,"outputs":3,"x":330,"y":120,"wires":[["5eda0fb.a8131f"],["1fa627f57d6d1e7b"],["b84cd1ad.5ca6b"]]},{"id":"7bd0933656c9f423","type":"subflow:584796d7.0845f8","z":"fae402b9.436ba","name":"","env":[],"x":110,"y":40,"wires":[["c45c78a5d7bf678b"],[]]},{"id":"de31e0ee.c7354","type":"homekit-bridge","bridgeName":"CMLK Node-red","pinCode":"111-11-111","port":"","allowInsecureRequest":false,"manufacturer":"NRCHKB","model":"1.2.0","serialNo":"Default Serial Number","firmwareRev":"1.2.0","hardwareRev":"1.2.0","softwareRev":"1.2.0","customMdnsConfig":false,"mdnsMulticast":true,"mdnsInterface":"","mdnsPort":"","mdnsIp":"","mdnsTtl":"","mdnsLoopback":true,"mdnsReuseAddr":true,"allowMessagePassthrough":true},{"id":"cc6a2e2f.c5c25","type":"openhab2-controller","name":"CMLK","protocol":"http","host":"<IP_ADDRESS>","port":"8080","path":"","username":"","password":""}]
Hereafter an extract from the flows.json (located on ny NAS), no encoding issue
{
"id": "1fa627f57d6d1e7b",
"type": "homekit-service",
"z": "fae402b9.436ba",
"isParent": true,
"hostType": "0",
"bridge": "de31e0ee.c7354",
"accessoryId": "",
"parentService": "",
"name": "Extérieur buanderie",
"serviceName": "Lightbulb",
"topic": "",
"filter": false,
"manufacturer": "NRCHKB",
"model": "1.2.0",
"serialNo": "Default Serial Number",
"firmwareRev": "1.2.0",
"hardwareRev": "1.2.0",
"softwareRev": "1.2.0",
"cameraConfigVideoProcessor": "ffmpeg",
"cameraConfigSource": "",
"cameraConfigStillImageSource": "",
"cameraConfigMaxStreams": 2,
"cameraConfigMaxWidth": 1280,
"cameraConfigMaxHeight": 720,
"cameraConfigMaxFPS": 10,
"cameraConfigMaxBitrate": 300,
"cameraConfigVideoCodec": "libx264",
"cameraConfigAudioCodec": "libfdk_aac",
"cameraConfigAudio": false,
"cameraConfigPacketSize": 1316,
"cameraConfigVerticalFlip": false,
"cameraConfigHorizontalFlip": false,
"cameraConfigMapVideo": "0:0",
"cameraConfigMapAudio": "0:1",
"cameraConfigVideoFilter": "scale=1280:720",
"cameraConfigAdditionalCommandLine": "-tune zerolatency",
"cameraConfigDebug": false,
"cameraConfigSnapshotOutput": "disabled",
"cameraConfigInterfaceName": "",
"characteristicProperties": "{}",
"waitForSetupMsg": false,
"outputs": 2,
"x": 550,
"y": 100,
"wires": [
[
"aa3e2acac02e89b9"
],
[]
],
"icon": "node-red/light.svg"
}

I don't have this problem. I use an AZERTY keyboard.
Maybe you use a Swiss QWERTZ keyboard?
Example with some characters (my keyboard):
[
    {
        "id": "3b4e2f6ded81ed2e",
        "type": "inject",
        "z": "15cdbf1d258ebb57",
        "name": "éèê-aà-ç-ù",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "topic",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 240,
        "y": 600,
        "wires": [
            []
        ]
    }
]

I am using an azerty keyboard.
in the file flows.json : "Extérieur buanderie" is correctly encoded however the dashboard shows

I had no issue with the previous of the docker image

it is coming from the back-end. If i do a get on http://<IP_ADDRESS>:1880/flows?_=1725978802740 I can see that the result already contains the encoding issue

from inside docker container the file encoding is correct
black-pearl:/data$ file -bi flows.json
application/json; charset=utf-8
black-pearl:/data$

seems to be an issue with Node.js 22 - I had it running with 4.0.2-20 (Docker / everything was fine) but after switching to 4.0.2-22 (Docker) I had a similar issue with German Umlauts

I've just tested with Node 22 (both in docker image and running locally) and the accented characters appear fine. There must be some other factor we're overlooking here.

for me it appeared first after I reloaded the editor / dashboard

do not know whether it can help to investigate or not
1/ 12/sept 13:45 : I fixed the encdoding issue in the name
2/ 12/sept 13:46 : deploy the changes
3/ 12/sept 13:47 : refresh the dashboard - names are still displayed correctly
4/ 12/sept 13:49 : restart docker container
5/ 12/sept 13:51 : refresh the dashboard - names are still displayed correctly
6/ 12/sept 14:05 : refresh the dashboard - names no more displayed correctly !!!!

I updated to 4.0.3-22 a few minutes ago and until now everything looks fine again

I did the upgrade this morning and indeed until now the problem is gone

Odd - not sure what cause this, or caused it to start working again in the 4.0.3 rebuild. Given no other reports of this behaviour have been reported, I'm going to close off.


Repos split

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Closes ZKF-1164

@keriat I'm OK with the concept of splitting the repos. What exactly do you want me to review?

@keriat I'm OK with the concept of splitting the repos. What exactly do you want me to review?

Linting rules, deps etc

:tada: This PR is included in version 2.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[BUG] Redirect to tests site isn't working at harvesterhci.io

Describe the bug

When you go to https://harvesterhci.io/tests You get a 404 error
To Reproduce
Steps to reproduce the behavior:

Navigate to https://harvesterhci.io/tests
Expected behavior

You should get the tests site
Support bundle

N/A
Environment:

Harvester ISO version: N/A
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):N/A

Additional context
Add any other context about the problem here.
The tests are still available at https://harvester.github.io/tests/ . This seems to be an issue with the redirect at https://harvesterhci.io

probably need to config the https://github.com/harvester/tests/blob/main/docs/config.toml#L1 to use harvesterhci.io/tests/

We have updated the README with correct url


Can I submit SQL in batches when editing data?Similar to mysql when the insert SQL statement is insert...values (),(),();

Can I submit SQL in batches when editing data?Similar to mysql when the insert SQL statement is insert...values (),(),();

Hello @huage0524
Could you please provide more info about your request?
What is your case? What do you want to do?

When I insert data like this, the data is multiple times insert into tb values ();insert into tab values(),(),();

When I insert data like this, the data is multiple times insert into tb values ();insert into tab values(),(),();

In the data edit box, paste the data directly.If data is inserted multiple times in the background of the database, can you insert batch data once?

We are using batches for data inserting. On the JAVA level.
And it is faster than one-row VALUES, yes.
Also, you can use multi-values insert in the data transfer (you can find more info in our documentation: https://github.com/dbeaver/dbeaver/wiki/Data-migration#step-5-data-load-settings)
And you can create and export SQL files with multiple-insert statements (https://github.com/dbeaver/dbeaver/wiki/Data-transfer#export-data)

Ok. Thanks very much.


SQL prints generated SQL

I think it's brilliant that the PRQL mode of the CLI dumps the generated SQL query.
Makes troubleshooting and sanity checks super easy.
Don't think we need to print the generated SQL after a query in SQL mode, though.

Hmm good call, I'll mark this as a bug


/home/nitin/anaconda3/envs/automlgluon/lib/python3.6/site-packages/sklearn/metrics/classification.py:2174: RuntimeWarning: divide by zero encountered in log   loss = -(transformed_labels * np.log(y_pred)).sum(axis=1)

I am using autogluon to help me a binary classification problem. It is an unbalanced dataset (90:10) and the neural network breaks down in training and never recovers. I guess a reinitialization once this has been encountered would help?
/home/nitin/anaconda3/envs/automlgluon/lib/python3.6/site-packages/sklearn/metrics/classification.py:2174: RuntimeWarning: divide by zero encountered in log
  loss = -(transformed_labels * np.log(y_pred)).sum(axis=1)
/home/nitin/anaconda3/envs/automlgluon/lib/python3.6/site-packages/sklearn/metrics/classification.py:2174: RuntimeWarning: divide by zero encountered in log
  loss = -(transformed_labels * np.log(y_pred)).sum(axis=1)
/home/nitin/anaconda3/envs/automlgluon/lib/python3.6/site-packages/sklearn/metrics/classification.py:2174: RuntimeWarning: divide by zero encountered in log
  loss = -(transformed_labels * np.log(y_pred)).sum(axis=1)
/home/nitin/anaconda3/envs/automlgluon/lib/python3.6/site-packages/sklearn/metrics/classification.py:2174: RuntimeWarning: divide by zero encountered in log
  loss = -(transformed_labels * np.log(y_pred)).sum(axis=1)
/home/nitin/anaconda3/envs/automlgluon/lib/python3.6/site-packages/sklearn/metrics/classification.py:2174: RuntimeWarning: divide by zero encountered in log

The task is fitting all the other models just fine and hitting an 'auc' of 0.74+ but neural network has issues (dead relus, inf encountered and now wont recover? just guesses) but i guess reinitialization once the weights have been bastardized irrevocably would help

Thanks for submitting an issue!
We are aware that the NN can at times break down as you say. We have a PR in progress that hopes to deal with at least part of the problem: #339 .
@jwmueller Can you take ownership of this issue and see to resolving this problem in the next release? I think it affects quite a few datasets.

Yep I already have a much better fix than the one in the PR but it's currently entangled with a bunch of other code. Will try to update the PR shortly

I have seen this issue in writing my own neural networks based pipeline (it was couple of years back though). I did a few things in trying to solve it and they helped (all in tensorflow) :

Gradient clipping
Batchnorm as the first layer
Weights normalization (You have batchnorm with dropout. I have read that they dont work well together). If anyway you have batchnorm then keeping gamma frozen at 1 and beta frozen at 0 for first few epochs might help
Reinitializing the network altogether when nan was encounter in loss
Leaky ReLU for first few epoch and then ReLU. Also, SELU was great at not letting the network bastardize to even 6-7 layers of depths.
Deep feed forward netowrks with dense connections (densenet style) with SELU (since SELU can handle depth) never got the issue. But, you are going for speed as well and SELU is going to need at least 100 neurons in hidden layers for fixed point theorem to kick in plus huge network .. so.. I dont know .. just putting down what i had tried

Also, with me it did happen that the network broke down at times but i didnt see it break down with every initialization but that is happening here. I dropped around 100 features using null importance and still the neural network is breaking on every initialization.

The issue is much simpler, when you specify eval_metric='roc_auc', the NN is actually internally checking the per-epoch validation log-loss metric for early stopping. Near initialization, the NN often predicts class-probabilities == 0 by pure chance which causes 'divide by zero'.  If you simply change your eval_metric to accuracy, you'll get better 'roc_auc' from the NN as it will avoid this issue because it'll check the per-epoch validation accuracy rather than log-loss (despite no change to its architecture/initialization/training updates).

Alternatively, you can also set stopping_metric='roc_auc' to fix it.

@jwmueller  - "Near initialization, the NN often predicts class-probabilities == 0 by pure chance".. Maybe you wanted to say 'hard classes' and not 'class-probabilities'. Outoput of softmax wont be zero.

I do not think this is a case of pure chance but a case of imbalanced data. NN is getting so many samples with 0 as the label that it initially learns to predict all 0s. Plus it is happening on every initialization. Also, for accuracy you would have to set a threshold which even if you would be setting equal to proportion of 1s., the network would have to be very unlucky to predict all probabilities below threshold to have all labels are 0. For these reasons I guess the network is just learning to predict very low probabilities for each sample
How this translates to a 'division by zero' beats me. Can you please shed some light on it?
This imbalanced classes is the sole reason i dont want to use accuracy as 'eval_metric'. My rule based class_predicton = 0 has 90% accuracy to begin with.

Fixed in: https://github.com/awslabs/autogluon/pull/481


Openfast with Visualstudio

Dear all,
i hope you would help me
i am trying to compile OpenFast with visual Studio (v2019 11.19) as described in the Instruction. it seems to be, that FAST is incompatible with this Version of Visual studio. however, i don't know which version of VS should be compatible. the instruction says VS2019 is okay. I have installed Openfast v3.2
what should i do to fix it?

Dear @SaeedHAMB,
See a similar question asked and answered in the following issue: https://github.com/OpenFAST/openfast/issues/328#issuecomment-642902611.
Best regards,


Allow package to be invoked as python -m bumpversion

PEP 338 defines a spec allowing modules and packages to be executed without an entry script. This simple module makes python -m bumpversion execute bumpversion.

Thanks for finding this. Apparently, I originally made the pull request against my own repo. :/

Thx.

Any chance you would be able to make a PyPI release with this change?


Algorithm hangs during cloud initialization

Expected Behavior

No algorithm deployment hangs

Actual Behavior

Seems that in some cases Python algorithms hang during deployment

2019-08-05T14:43:01.9127210Z TRACE:: Engine.Main(): LEAN ALGORITHMIC TRADING ENGINE v<IP_ADDRESS>.6130 Mode: DEBUG (64bit)
2019-08-05T14:43:01.9128940Z TRACE:: Engine.Main(): Started 2:43 PM
2019-08-05T14:43:02.0623970Z TRACE:: Config.Get(): Configuration key not found. Key: email-smtp-host - Using default value: smtp.sendgrid.net
2019-08-05T14:43:02.0624880Z TRACE:: Config.Get(): Configuration key not found. Key: email-smtp-username - Using default value:
2019-08-05T14:43:02.0625190Z TRACE:: Config.Get(): Configuration key not found. Key: email-smtp-password - Using default value:
2019-08-05T14:43:02.0625460Z TRACE:: Config.Get(): Configuration key not found. Key: twilio-account-sid - Using default value:
2019-08-05T14:43:02.0625690Z TRACE:: Config.Get(): Configuration key not found. Key: twilio-account-token - Using default value:
2019-08-05T14:43:02.0625910Z TRACE:: Config.Get(): Configuration key not found. Key: twilio-account-phone - Using default value:
2019-08-05T14:43:02.0838780Z TRACE:: Messaging.Cloud.Initialize(): Complete
2019-08-05T14:43:02.0839900Z TRACE:: MessagingCloud.HasSubscribers: True
2019-08-05T14:43:02.0850580Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-accesskey - Using default value:
2019-08-05T14:43:02.0850820Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-secretkey - Using default value:
2019-08-05T14:43:02.0850970Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-userid - Using default value:
2019-08-05T14:43:02.0851110Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-bucketname - Using default value:
2019-08-05T14:43:02.0858320Z TRACE:: Cloud.NodeCloudProvider(): Set provider to: SelfHosted
2019-08-05T14:43:02.1153660Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-accesskey - Using default value:
2019-08-05T14:43:02.1154030Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-secretkey - Using default value:
2019-08-05T14:43:02.1154170Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-userid - Using default value:
2019-08-05T14:43:02.1154300Z TRACE:: Config.Get(): Configuration key not found. Key: amazon-bucketname - Using default value:
2019-08-05T14:43:02.1446140Z TRACE:: Cloud.NodeCloudProvider(): Set provider to: SelfHosted
2019-08-05T14:43:02.1446800Z TRACE:: Cloud.Initialized: Unknown Storage:AmazonWebServices
2019-08-05T14:43:02.1477430Z TRACE:: JobQueueCloud.GetAlgorithmJob(): Parsing Backtest Node Packet
2019-08-05T14:43:02.2610060Z TRACE:: Cloud.GetAlgorithmLocation(): File count: 1
2019-08-05T14:43:02.2610680Z TRACE:: JobQueueCloud.NextJob(): Received job: eb42b724faa81e3b046b39e62396b0fb
2019-08-05T14:43:02.2879440Z TRACE:: CloudBacktestingManager.StateCheck(): Starting state check.

Potential Solution

Next line which should be logged is 2019-08-05T15:01:15.6442510Z TRACE:: AlgorithmPythonWrapper(): Python version 3.6.8 |Anaconda, Inc.| (default, Dec 30 2018, 01:25:33)  [GCC 7.3.0]: Importing python module main, could be related to some failure to start python

Reproducing the Problem

Python algorithm, intermittently

System Information

Happens in cloud deployments

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Algorithm hangs during Python initialization
It's rare but seen this happen locally on windows too


Adding Agnostic Tools Notebook to WIP

Adding Agnostic Tools Notebook to WIP folder for presentation to PGE/SCE and for preliminary review.
Must switch to using agnostic branch in climakitae in order to work properly.

Extraneous commits also added accidentally.


[Draft for Discussion] Samples of different ACR APIs for transfer from ACR to storage

There are two rough proposed APIs here:

Low-Level: The addition of DPG methods to the ACR Blob Client API
High-Level: The addition of high level convenience methods to the Blob Client API

The low-level approach allows users to pull down chunks and interleave those downloads with other actions, like upload -- for our customer scenario, that would mean they could be downloading an artifact while simultaneously uploading it to blob storage.  See usage sample here: TransferInChunks
The high-level approach provides more convenience by abstracting the details of the download, but would require downloading the entire artifact prior to beginning upload to storage.  See usage sample here: TransferArtifactAsync

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Containers.ContainerRegistry

Some thoughts:

[ ] We should move high-level APIs to the high-level clients
[ ] Experiment with HLC convenience methods for "missing methods" instead of DPG methods
[ ] Strawman proposal for models in blob APIs

Closing as we have decided on an API to target for Zinc.


Inefficient Usages of Java Collections

Hi,
We find that the List allocated at line 85 in the function isExclusionConfigFile is only used to check whether an element is stored in the container. The method contains of a list runs in linear time complexity. We notice that the exclusionFileList is maintained in the HashMap exclusionMap, which maps a string object to an object.
To achieve the same functionality, maybe a HashSet can provide a more efficient implementation. We can just construct a HashSet and maintain it in the HashMap exclusionMap. When we invoke the function isExclusionConfigFile, we only need to take amortized O(1) time to maintain the map and invoke the contains method of HashSet.
We discovered this inefficient usage of containers by our tool Ditto. The patch is submitted. Could you please check and accept it? We have tested the patch on our PC. The patched program works well. Of course, it would be better to change EXCLUSION_CONFIG_FILE_LIST to EXCLUSION_CONFIG_FILE_Set. Anyway, the name does not affect the performance anymore.
Bests
Ditto

For any use case that container more data elements in the list, it would make sense to convert the list to set to speed up the contain calculation, however, in the case of exclusive list, we only have about 4 elements in the list. It takes more time to convert it to set than walking through the 4 elements. Also, it makes the logic harder for other developers to understand. I think we shouldn't take the performance optimization as the number of elements is too small. What do you think?

Steve, I generally agree with you. I refined the patch and removed unnecessary construction of HashSet objects. The set is only constructed one time, so the concern you mentioned above would not exist.
We detected this inefficient usage by a static analyzer and do not analyze the number of elements maintained in the list in the actual use. When the size of the list is small, the transformation will not bring much difference.
Anyway, we discovered this usage and recommended avoiding it in the design. For example, the type of exclusionMap can be restricted to HashMap<String, HashSet> rather than HashMap<String, Collection> if possible. Programmers tend to declare the type of containers in a rough way. However, it would be better for performance improvement when we consider how the container objects are utilized in the program. The same functionality can be achieved by other container types and interfaces. Of course, the patch might degrade the cleanness of the code.

Similarly, we also find other two cases of inefficient usages of List, which can be replaced by HashSet objects. Meanwhile, two ArrayList can be replaced by LinkedList. The two ArrayList objects are inserted before iterations, while multiple memory reallocation might occur when the size of the list exceeds its capacity. We recommend replacing it with a LinkedList.


Use remark-variables for custom frontmatter variable substitution

Summary

Use remark-variables for frontmatter variable substitution instead of Nunjucks

Details

Nunjucks if useful for a lot of things but we are only using it do frontmatter variable substitution in the note body.
We should use remark-variables instead

Tasks

[ ] Remove calls to nunjucks.renderString()

This happens in two places:

DendronEngineV2._renderNote()

To render a note

NoteRefsV2.convertNoteRefHelperAST()

To render a note reference

[ ] Add plugin remark-variables to processors and add the fm object to the processor's .data

Examples can be found here

[ ] Add tests
[ ] Update documents on variable substitution.

Lookup

page for remark plugin

https://github.com/mrzmmr/remark-variables

example in dendron codebase

where the plugin is set

https://github.com/dendronhq/dendron/blob/c07c6724419ba506198a316e5b8aa4ab06b74ab7/packages/engine-server/src/markdown/utils.ts#L402

where the fm object is passed to the processor

https://github.com/dendronhq/dendron/blob/c07c6724419ba506198a316e5b8aa4ab06b74ab7/packages/engine-server/src/markdown/utils.ts#L382

current docs on variable substitution

https://wiki.dendron.so/notes/ba97866b-889f-4ac6-86e7-bb2d97f6e376/#frontmatter-variable-substitution

where note rendering is tested

https://github.com/dendronhq/dendron/blob/0282c1703643995b6675ee6ee64ca7c7b7500fd2/packages/engine-test-utils/src/presets/engine-server/render.ts

where note reference rendering is tested

https://github.com/dendronhq/dendron/blob/0282c1703643995b6675ee6ee64ca7c7b7500fd2/packages/engine-test-utils/src/presets/engine-server/note-refs.ts

where nunjucks is currently used

https://github.com/dendronhq/dendron/blob/c07c6724419ba506198a316e5b8aa4ab06b74ab7/packages/engine-server/src/markdown/remark/noteRefsV2.ts#L780
https://github.com/dendronhq/dendron/blob/0282c1703643995b6675ee6ee64ca7c7b7500fd2/packages/engine-server/src/enginev2.ts#L569
https://github.com/dendronhq/dendron/blob/16b0e5c59e3ee11530199b5c9a11a58f05e14a93/packages/dendron-11ty/libs/shortcodes.js#L129

This issue from a year ago would suggest that remark-variables is going to stop working.
Would you consider an alternative and switch from nunjucks to etl?

This has been shipped! 🥳


set path for language cookie

Coverage remained the same at 50.695% when pulling 49d07ff581529221648fe8b9e7475c4c40458dc3 on reasonerjt:dev into 74714fe74aca333d6c9b3293cd91eb53fd7840fb on vmware:dev.


Fix issue 620

Fixes issue https://github.com/duo-labs/cloudmapper/issues/620 by adding the deprecated policy to the list of bad policies

LGTM, though I do prefer keeping the PRs to the specific issue at hand


Build hangs when using :global selector in css module with apostrophes

System Info
Mac OS 13.6, Node 18, rspack 0.5.0
Details
While converting an old webpack project to rspack, I found a line of code that would hang the build process. Specifically:
// some.module.css
:global('something') { ... }
I wasn't able to find if using apostrophes has any special meaning in this case or if it was a mistake when writing the code. Regardless, I would expect that the build either fails or ignores it instead of being stuck.
Reproduce link
https://github.com/martinkadlec0/rspack-global-bug/
Reproduce Steps
Clone repo
Run: npm run build
Or just add the :global('something') to any css module.

Bump

bump

Seems to be fixed in 0.7 👍


Fmpeg Non-zero exit status

Hello there,
thank you for sharing your programm.
I encountered an error while downloading specific Videos from BBB. This error occurs reproducible to a subset of videos from a lecture series.
PS C:\Users\fooUser> bbb-dl -f DisSimMas_SS2022_... https://....
Output directory for the final video is: C:\Users\fooUser
Directory for the temporary files is: C:\Users\fooUser\AppData\Local\bbb-dl\281cb87d5e05162b6dba3672b7507976
Downloading meta information
metadata.xml is already present
shapes.svg is already present
Downloading webcams / deskshare
cursor.xml is already present
panzooms.xml is already present
captions.json is already present
deskshare.xml is already present
Downloading events.xml...
presentation_text.json is already present
slides_new.xml is already present
Downloading notes.html...
Downloading polls.json...
Downloading external_videos.json...
video/webcams.webm is already present
Downloading video/webcams.mp4...
Downloading deskshare/deskshare.webm...
Downloading deskshare/deskshare.mp4...
notes.html could not be downloaded: 404 Not Found
video/webcams.mp4 could not be downloaded: 404 Not Found
events.xml could not be downloaded: 404 Not Found
external_videos.json could not be downloaded: 404 Not Found
polls.json could not be downloaded: 404 Not Found
deskshare/deskshare.webm could not be downloaded: 404 Not Found
deskshare/deskshare.mp4 could not be downloaded: 404 Not Found
Downloading slides
presentation/e537a2074b7e59c4ab45016011204e518249f90d-1657810862982/slide-1.png is already present
presentation/8614337cf2b16e3c93843d8b44031769f3ead9f4-1657810523966/slide-1.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-1.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-2.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-3.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-4.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-5.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-6.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-7.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-8.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-9.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-10.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-11.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-12.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-13.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-14.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-15.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-16.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-17.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-18.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-19.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-20.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-21.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-22.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-23.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-24.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-25.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-26.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-27.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-28.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-29.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-30.png is already present
presentation/1e7a58a106274a61647104478274a4c46f240dba-1657810578592/slide-31.png is already present
Recording title: DisSimMas_SS2022
Recording date: 2022-07-14T16-53-33
Recording duration: 30:36
No desk was shared in this session
Start capturing frames...
Output directory for frames is: C:\Users\fooUser\AppData\Local\bbb-dl\281cb87d5e05162b6dba3672b7507976\frames
Initialization takes a few seconds...

Done: 00000 / 04509 Frames | 000 / 001 Parts \
Partition already finished: 0 to 1:02:23

Frames capturing is finished and took: 37.
Start creating slideshow...
Slideshow does already exist! Skipping rendering!
Try to detect freeze in video/webcams.webm...
Frame: 27540 FPS: 763.0 Size: 0 Time: 30:35 Bitrate: 0.0 Speed: 50.8x -
Command finished
Detection of freeze finished and took: 37
Webcam is empty, webcam will not be added to the final presentation
Mux final slideshow
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\fooUser\AppData\Roaming\Python\Python311\Scripts\bbb-dl.exe\__main__.py", line 7, in <module>
  File "C:\Users\fooUser\AppData\Roaming\Python\Python311\site-packages\bbb_dl\main.py", line 1465, in main
    bbb_dl.run()
  File "C:\Users\fooUser\AppData\Roaming\Python\Python311\site-packages\bbb_dl\main.py", line 265, in run
    result_path = self.final_mux(slideshow_path, webcams_path, webcams_rel_path, metadata)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\fooUser\AppData\Roaming\Python\Python311\site-packages\bbb_dl\main.py", line 1115, in final_mux
    asyncio.run(
  File "C:\Python311\Lib\asyncio\runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\asyncio\runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\asyncio\base_events.py", line 650, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "C:\Users\fooUser\AppData\Roaming\Python\Python311\site-packages\bbb_dl\ffmpeg.py", line 313, in add_audio_to_slideshow
    await ffmpeg.execute()
  File "C:\Users\fooUser\AppData\Roaming\Python\Python311\site-packages\ffmpeg\asyncio\ffmpeg.py", line 141, in execute
    raise FFmpegError(f"Non-zero exit status {self._process.returncode}")
ffmpeg.ffmpeg.FFmpegError: Non-zero exit status 1

Windows 11 x64
Python 3.11.0
ffmpeg version 6.0-full_build-www.gyan.dev (Installed with winget)

Please provide the verbose log.
And if possible send me the lecture URL (via mail?)

fix is released


Add juju-crashdump functionality

install juju-crashdump
upload any juju-crashdumps to GitHub artifact

This feature depends on these changes in pytest-operator and here is an example of how it works together.

@r-f-g nothing it jumping out here as scary.  I checked on the @actions/glob and @actions/artifact NPMs and they seem reasoned.  I'm curious as to why the tests are failing though.

@r-f-g nothing it jumping out here as scary. I checked on the @actions/glob and @actions/artifact NPMs and they seem reasoned. I'm curious as to why the tests are failing though.

The test on vSphere failing due missing credentials. It's ok, because any of my PR should not have access to credentials.
The test on microstack failing due this issue.

Watch checks run here

I'd ask @addyess for an extra approval before merging. @r-f-g is there an example CI run where this is tested already?

Yes, I created this charm and you can look at actions runs, e.g. this.


Syntax highlighting in editors

Tree-sitter? See also #185 (https://www.reddit.com/r/ProgrammingLanguages/comments/t4c8ms/what_parsing_techniques_do_you_use_to_support_a/hyxj3a8/).

If #156 happens this mightn't be necessary.


Version 3.2.2

On rubygems, the latest version is 3.2.2, released a few weeks ago.
However, the version number on the default branch in this repository says 3.2.1. And the readme only mentions up to 3.2.1.
What is the explanation for this? I'm a little worried there may have been a security breach.

https://github.com/CanCanCommunity/cancancan/releases/tag/3.2.2


Html dependency is slow with large images.

I was running into a weird issue with my editor where I pasted a large image (src set to a very large base64 string) and when I changed my selection the editor would freeze. It would get stuck in this loop in the html dependency. I'm pretty sure it's because of this condition of the while loop. I would submit a pull request but it looks like it hasn't been updated in 8 years...
https://github.com/max-mapper/commonjs-html-prettyprinter/blob/0717eb216ebcc67399ca3c0406e5c03a77f7e761/lib/html.js#L340
Not familiar with what it could be replaced with that is fast, but it necessary to call it on every selection change? Could there be an option to disable it or could it be done some other way? I was thinking maybe as a slice and using it's toJSON. That is after all what one would have access to if writing an editor.

Hey @AlansCodeLog , thanks for the report. I was away last week so didn't have a chance to look into this.
My first idea is to debounce the HTML generation and/or put it inside a worker so that the main UI thread won't jank. I'll see when I have time to do a first proto.

No problem.
I don't think debouncing will work as it will just delay the freezing. Maybe conversion could be defered until the user views the history step in the tab.
Using a webworker will help, but it will probably need to be terminated if it runs too long, and some alternative shown.

Okay I made a fix with version 1.1.8, can you try it locally and see whether it works? I just decided to truncate the src tags, seemed the easiest solution for now.
I'll later publish an extension update

Simplest solution is sometimes the best! :smile:
Works well, no more freezing or interfering with editor performance, and opening selection history entries is fast now. The doc diffs are now the slower entries, but I think that's to be expected. It's all usable now at least.
Thank you!


basehub: don't declare singleuser.cmd - its z2jh's default

Its a breaking change for z2jh to change this, so if it changes we'll be
well aware about it from changelogs when upgrading.
I mainly want to remove the now outdated comment, but I also appreciate
not re-specifying defaults in general as that makes it easier to
overview and trust whats declared in basehub's default values are actual
changes from the default.

Outdated because we now use the vuln-patch script


Ticketit needs upgrade, admin should login and visit ticketit install route

I have gone through all threads on this topic to no positive result. I would like to solve this or if I could revert and re-install the package?

Sorry, it's not clear what you are asking. What error message do you get? What laravel and tiicketit versions are you on?

I got; "Ticketit needs upgrade, admin should login and visit ticketit install route " error
using laravel 5.4 and the latest version of ticketit.

@learnhard Have you tried to do as the message says?

I dont know how... So I thought i could re-install it,  I tried to delete and the require line from the composer.json file and ran composer update, but got this error:
`Writing lock file
Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postUpdate
php artisan optimize
[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'Kordy\Ticketit\TicketitServiceProvider' not found
Script php artisan optimize handling the post-update-cmd event returned with error code 1`

Then tried re-installing ticketit and got `Writing lock file
Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postUpdate
php artisan optimize
[Illuminate\Database\QueryException]
SQLSTATE[HY000] [2002] No connection could be made because the target machine actively refused it.
(SQL: select * from information_schema.tables where table_schema = blog and table_name = migrations)
[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[HY000] [2002] No connection could be made because the target machine actively refused it.
[PDOException]
SQLSTATE[HY000] [2002] No connection could be made because the target machine actively refused it.
Script php artisan optimize handling the post-update-cmd event returned with error code 1
Installation failed, reverting ./composer.json to its original content.`
error

I'm really confused here. Hope you can help sort things out for me. Thanks

how do I do this ?
"@learnhard Have you tried to do as the message says?" @thekordy @balping @kebian @c0h1b4 @mandrakecr

how do I do this ?
"@learnhard Have you tried to do as the message says?" @thekordy @balping @kebian @c0h1b4 @mandrakecr

how do I do this ?
"@learnhard Have you tried to do as the message says?" @thekordy @balping @kebian @c0h1b4 @mandrakecr

When you remove your ticketit folder from vendor, don't forget to remove Kordy\Ticketit\TicketitServiceProvider::class, line from config/app.php. after that try re-installing ticketit.
and Is your MySQL server is running or recheck your MySQL database credentials?


How do I read the Critical Alarm KPI?

Type of issue

[ ] Bug
[ ] New feature
[x] Improvement

Description
Should the title use singular or plural, "Alarm" or "Alarms" ?
I'm not sure how to interpret this box

probably we need more data to give an idea, or some more points of reference

I discussed this with @CaitlinEsworthy before. The idea is that this shows at least 4 data points per each time. For example: if it's last hour, it should show 4 15 min points. If it is 1 day, 4 6 hours points, and so on so forth. Does that make sense @timlaverty ?

I think that Swetha was going to make the changes. @swetha571  do you have any questions or concerns?

@hegate This makes sense if the data exists; i.e. if there are minimum 4 critical alarms within the last hour.  When a solution is initially deployed, and shortly after, this data won't exist.  Do you want to show "No Data" until it has 4 points in the specified timeframe?  ...or start showing data @ 3 points?
IIUC this is showing the trend of critical alarms for the timeframe in question.  I wonder if a bar chart would better represent this (and wouldn't look odd w/ less data).  Thoughts?

@timlaverty I would vote for showing 3 points and then 4. That was the original intent @CaitlinEsworthy chime in if you disagree.

Swetha, please make the following changes:

When there are < 3 points of data for this control show "No Data".
When there are >= 3 points show the 3 points in a line graph.

nice to have: on mouse over "No Data" show a tooltip "this chart will show the KPI when there are at least 3 alarms"

Updated Comps.


Traffic measurement terminology

Clarify and decide on terminology eg: occupance, density, count, volume..

In my experience this is what we have from trafic counting sensors (equipments) :
4 periodicity available :

by minute
by 6 minutes
hourly
daily

2 categories :

light vehicule
heavy vehicule (bus, truck, etc..)

2 zones :

By lane
Aggregated by direction

5 mesures :

Vehicule flow rate (average of amount of vehicule by minutes for periodicity)
Vehicule speed (average of vehicule speed by periodicity)
Occupancy (a ofverage occupancy in percentage for the periodicity)
Vehicule flow rate for light vehicules only (average amount of light vehicule by minutes for periodicity)
Percentage of heavy vehicules (average of heavy vehicule / amount of total vehicules for periodicity)

Our software handling theses datas can compute new data from these raw datas or even calculate alarms (congestion, trafic slow, etc..)


docs: Attempt to flesh out the different release responsibilities

Signed-off-by: Ryan Hamilton<EMAIL_ADDRESS>docs: Attempt to flesh out the different release responsibilitiesRisk Level:
Testing: N/A
Docs Changes: RELEASES.md
Release Notes: N/A
Platform Specific Features: N/A

/assign @mattklein123

I have a few questions which I've noted as "TODO" in the doc. Hopefully we can sort them out :)

couple of general points re release/patches
i think its important that we keep the stable branch CI working. If we dont it makes it harder to land patches and see actual breakages etc. It also makes it harder to backport anything as every PR requires a senior maintainer to push past breakages.
~related to this point. As release managers are not maintainers they generally cant land PRs - so even with a non-broken release branch, PRs need still to be assigned/reviewed.
Im wondering if it is worth having a rotation for a "release maintainer" that shadows the release manager, and can land PRs etc
Ideally we need to also account for non-security-patch releases on supported branches - if for no other reason than so we can address eg container issues in a timely fashion.
I think it would be a good thing to make it easier to land/test/release on the stable branches, outside of sec patches, and encouraging more bug-fix backports
wrt to the first point - i think we can/should add some scheduled CI to make sure the stable branches are passing

Another issue i want to flag is around release versioning
Historically we had a ~bitrot issue where version histories contained links to removed code that was causing docs builds to fail (and a ton of workarounds to make links point to vaguely relevant current code)
As a result, i added a "intersphinx mappings" which allows us to point to specific versions in version histories, so the links should theoretically remain correct - they are essentially permalinked
This also however, complexifies the release process for a few reasons

we cant link to historical docs until they have been published
we want the current version history - ie the current changelog - to point to the current doctree now but use version links in the future
the mappings in docs/conf.py need to be maintained

all in all, it means that quite specific sets of steps are required for releasing either from main or from a release branch, and that the steps have to be done in roughly the correct order.
some of this can most likely be automated, but one difficulty is automating updating ref links in the version history file as its not easily parsable/editable programatically
i will try to figure out a smoother workflow and automate what i can. For now im going to manually clean up the version histories on main and current stable branches, and i guess take responsibility for making any preparations before releases, and cleaning up after
related (#20961  #20963 )

Another issue i want to flag is around release versioning
Historically we had a ~bitrot issue where version histories contained links to removed code that was causing docs builds to fail (and a ton of workarounds to make links point to vaguely relevant current code)
As a result, i added "intersphinx mappings" which allows us to point to specific published versions in version histories, so the links should theoretically remain correct - they are essentially permalinked
This also however, complexifies the release process for a few reasons

we cant link to historical docs until they have been published
we want the current version history - ie the current changelog - to point to the current doctree now but use version links in the future
the mappings in docs/conf.py need to be maintained

all in all, it means that quite specific sets of steps are required for releasing either from main or from a release branch, and that the steps have to be done in roughly the correct order.
some of this can most likely be automated, but one difficulty is automating updating ref links in the version history file as its not easily parsable/editable programatically
i will try to figure out a smoother workflow and automate what i can. For now im going to manually clean up the version histories on main and current stable branches, and i guess take responsibility for making any preparations before releases, and cleaning up after
related (#20961 #20963 #20965 )

Sounds great. It'd be great to write this up when you get this worked out (which I assume is already your plan :>)

~related to this point. As release managers are not maintainers they generally cant land PRs - so even with a non-broken release branch, PRs need still to be assigned/reviewed.
Im wondering if it is worth having a rotation for a "release maintainer" that shadows the release manager, and can land PRs etc

I think we can probably use the on-call maintainer for this role. WDYT?

/assign @alyssawilk

Release steps
Posting some notes and steps i have taken re release
Release, versions and version mappings
we always want/need the current.rst to point to the "current" docs (for any branch)
on current main 1.23 is not yet published -  likewise in a release branch, the repo doesnt have the .inv file/link for mapping that minor version, so links in all of the patch version eg v1.19.x version histories should only point to the docs for that release (or lesser versions where required)
Steps required
using the release branch that i have just worked on (v1.19.4), these are ~the steps i had to take
before release (on release branch):

Edit current.rst - "Pending" -> "date"
Edit VERSION(.txt) to remove -dev

after release (on release branch):

Copy current.rst -> docs/root/version_history/v1.19.4.rst
Add 1.19.4 to TOC in docs/root/version_history/version_history.rst
Blank current.rst and edit - "date" -> "Pending"
Edit VERSION(.txt) to readd -dev and increment version

after release (on main if release branch is not main, or has newer branches)

Copy the added v1.19.4.rst file into main version_histories editing all ref:s to use v1.19: prefix
Update version_history.rst TOC
Update intersphinx_mapping in  docs/conf.py (if necessary)
Sync .inv files (i have code to do this locally which i will publish asap - cf https://github.com/envoyproxy/pytooling/issues/462)

(to be comprehensive we may wish to do ^^ step on all newer release branches not just main)
after release (on envoy-website)

Edit _data/versions.yaml to include 1.19.4 (in the case of new releases/EOL etc we may wish to cycle stable/archived here at this point)

regarding editing the ref: links the only time they need to be edited is when a release has been cut (and published) and only when copying the version history files into the newer (release) branch (ie main)
almost certainly a bunch of this can be automated altho there are some issues, eg:

editing the rst is non-trivial programatically
if we dont human edit/cycle versions etc then we need some "source of authority" as to what are the current stable versions etc

re "release maintainer" mho is that it would be better working on same cycle as release for a few reasons

provides the release maintainer (who may not know expectations, or how to do things) someone to ping
requires more of a release-cycle focus

releases tend to be planned across weeks/months rather than a week
backporting a single patch often takes longer than a week

just my 2p tho - i think anything we can do to make it clearer/easier to contribute is a good thing
we may also want to make more use of milestones for tracking (patch) releases and related tickets/blockers/etc

re release process im experimenting with some CI which will at least flag some of the issues - like the reason one we had with a -dev release (#21022 )
as i work on it ill try and figure out any autofix/mate opportunities

So these are examples of the PRs required before/after a patch release:
Close the release branch (make non-dev, fix version and update current)
https://github.com/envoyproxy/envoy/pull/20824
Update version_history/inventory on main
https://github.com/envoyproxy/envoy/pull/21035
Update website docs versions
https://github.com/envoyproxy/envoy-website/pull/253
Re-open the release branch (make dev)
https://github.com/envoyproxy/envoy/pull/21037

this is not exactly the same as a main branch release but the principles are

@mattklein123 Are you good with this merging and we can continue to iterate?


feat(trading): merge deal ticket stores

Related issues 🔗
Closes #4451
Technical 👨🔧
Merge three zustand stores into one. Change flow of data in deal ticket, use store as side effect.

As discussed, it would be good if the hierarchy within the store state should be markets -> type -> fields
I think that would be cleaner in the code but also give us separated persistance between the different order types in the deal ticket


DOC: solve_discrete_lyapunov equation puts transpose in wrong place

The equation in the docs says A' X A - X = -Q when it should really be A X A' - X = -Q. This makes it not only consistent with the literature, but also matches the computed result:
from scipy.linalg import solve_discrete_lyapunov

a = np.asarray([[1, 0.5], [1, 0]])
q = np.asarray([[1, 0], [0, 1]])

x = solve_discrete_lyapunov(a, q)
print np.allclose(np.dot(a.T, np.dot(x, a)) - x, -q)
print np.allclose(np.dot(a, np.dot(x, a.T)) - x, -q)

The first line (which uses the currently documented equation) prints False, while the second (which puts the transpose in the correct place) prints True.

gh-5781


Refactor login logo usage

Description
This change uses the imagery exposed by OSD for the login screen.
Issues Resolved
#1529
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

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

@AMoo-Miki Can you address the failing unit tests?

● Login page › handle submit event › submit click event

TypeError: Cannot read properties of undefined (reading 'logos')

  260 |           size="fullWidth"
  261 |           alt=""
> 262 |           url={props.config.ui.basicauth.login.brandimage || props.chrome.logos.OpenSearch.url}
      |                                                                           ^
  263 |         />
  264 |       )}
  265 |       <EuiSpacer size="s" />

@AMoo-Miki Do you want to get this in for 2.10? The window is closing in pretty fast

@peternied This is blocked by https://github.com/opensearch-project/security/pull/3278
Once the security PR is merged I will re-run the CI

Issue from the security plugin has been merged into main [1], I've retriggered the integration tests.

[1] https://github.com/opensearch-project/security/pull/3278


docs(contributing.md): updated the vscode extension name for containers

This commit updates the Remote-containers extension by changing its name to Dev Containers. Additionally, it improves the workflow by replacing the old process of cloning the repository and reopening it in a dev container with a new process of directly cloning the repository link into a dev container. The previous workflow resulted in a file permission issue where all the tracked files appeared to change when running the "git status" command, even though they hadn't. This was due to overwritten file permissions.
What is it?

[ ] Feature / enhancement
[ ] Bug
[X] Docs / tests

Description
Update the name of Remote-Container extension to the new Dev Containers and changed the workflow, because the workflow proposed here result in many file changes due to permissions on my windows machine.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Hi @camunoz2 👋
Thanks a lot that you took the time to create this PR 🙏
I just have a question regarding the changed wording since i am still getting the prompt to open my forked repo as dev container. so imo we should keep this info in the message and add the direct open via github fork as a second option. What do you think?

Hi @camunoz2 👋
Thanks a lot that you took the time to create this PR 🙏
I just have a question regarding the changed wording since i am still getting the prompt to open my forked repo as dev container. so imo we should keep this info in the message and add the direct open via github fork as a second option. What do you think?

Hi! Yeah, that would be great 👌

Great! Do you want to adjust the wording in that case? So that both (the overlay and open fork from github directly) are reflected? That would be very nice 🙏  And thanks again!


⚠ Bofrost.fr has degraded performance

In b49b3ed, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 3169 ms

Resolved: Bofrost.fr performance has improved in f439c3a.


AttributeError: 'str' object has no attribute 'grad_fn'

when i try to create visualizations of PyTorch execution graphs and traces,I met this issue.
`from graphviz import Digraph
import torch
from torch.autograd import Variable
def make_dot(vars, params = None):
    """ Produces Graphviz representation of PyTorch autograd graph
    Blue nodes are the Variables that require grad, orange are Tensors
    saved for backward in torch.autograd.Function
    Args:
        var: output Variable
        params: dict of (name, Variable) to add names to node that
            require grad (TODO: make optional)
    """
    if params is not None:
        assert isinstance(params.values()[0], Variable)
        param_map = {id(v): k for k, v in params.items()}

    node_attr = dict(style='filled',
                     shape='box',
                     align='left',
                     fontsize='12',
                     ranksep='0.1',
                     height='0.2')
    dot = Digraph(node_attr=node_attr, graph_attr=dict(size="12,12"))
    seen = set()

    def size_to_str(size):
        return '('+(', ').join(['%d' % v for v in size])+')'

    def add_nodes(var):
        if var not in seen:
            if torch.is_tensor(var):
                dot.node(str(id(var)), size_to_str(var.size()), fillcolor='orange')
            elif hasattr(var, 'variable'):
                u = var.variable
                name = param_map[id(u)] if params is not None else ''
                node_name = '%s\n %s' % (name, size_to_str(u.size()))
                dot.node(str(id(var)), node_name, fillcolor='lightblue')
            else:
                dot.node(str(id(var)), str(type(var).__name__))
            seen.add(var)
            if hasattr(var, 'next_functions'):
                for u in var.next_functions:
                    if u[0] is not None:
                        dot.edge(str(id(u[0])), str(id(var)))
                        add_nodes(u[0])
            if hasattr(var, 'saved_tensors'):
                for t in var.saved_tensors:
                    dot.edge(str(id(t)), str(id(var)))
                    add_nodes(t)
    for var in vars:
        add_nodes(var.grad_fn)
    return dot

from torch.autograd import Variable
from yolact import Yolact

if __name__ == '__main__':
    from datetime import datetime
    t0 = datetime.now()
    x = Variable(torch.ones(1,3,550,550))
    model = Yolact()
    output0 = model(x)
    t1 = datetime.now()
    print('taking {} secondes'.format(t1 - t0))
    g = make_dot((output0))
    g.view()`

Traceback (most recent call last):   File "D:/interest/yolact/Net_visiable.py", line 71, in <module>     g = make_dot((output0))   File "D:/interest/yolact/Net_visiable.py", line 53, in make_dot     add_nodes(var.grad_fn) AttributeError: 'str' object has no attribute 'grad_fn'
How to solve this problem?

This is not the place to ask for help debugging somebody else's code.
Nevertheless, the error message points to
for var in vars:
    add_nodes(var.grad_fn)

and says that var doesn't have a grad_fn. If you check why that is, you'd notice that vars (the output of Yolact) is a dictionary and not a tuple or list as the loop expects (when vars is a dictionary this loops over the keys and not the values). Thus, to fix it you should loop over the values by changing the loop to
for var in vars.values():
    add_nodes(var.grad_fn)

This is not the place to ask for help debugging somebody else's code.
Nevertheless, the error message points to
for var in vars:
    add_nodes(var.grad_fn)

and says that var doesn't have a grad_fn. If you check why that is, you'd notice that vars (the output of Yolact) is a dictionary and not a tuple or list as the loop expects (when vars is a dictionary this loops over the keys and not the values). Thus, to fix it you should loop over the values by changing the loop to
for var in vars.values():
    add_nodes(var.grad_fn)

Thank you very much,I am sorry to ask about this question there, but I didn't find a button to remove this issue, could you please help to remove it.

It's fine, I can just close it. I'll keep this up because it might help somebody in the future.


sprintfix: 适配部分 DB 无法采取字符串查询 (fixed #206)

Codecov Report

Merging #226 (d3f2563) into v1.0.20-rc (3e0174e) will not change coverage.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           v1.0.20-rc     #226   +/-   ##
===========================================
  Coverage       53.55%   53.55%
===========================================
  Files             182      182
  Lines            8975     8975
===========================================
  Hits             4807     4807
  Misses           4168     4168

Impacted Files
Coverage Δ

apps/gsekit/job/handlers.py
37.41% <0.00%> (ø)

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


Migrations under "test/support" not detected

Environment

Elixir version (elixir -v):

Erlang/OTP 21 [erts-10.1.1] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe] [dtrace]

Elixir 1.7.4 (compiled with Erlang/OTP 21)

Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): Postgres 11
Ecto version (mix deps): 3.0.0
Database adapter and version (mix deps): Postgrex 0.14.0
Operating system: MacOS 10.14.1

Current behavior
I'm migrating a library from ecto 2.2 to ecto 3.0.
The library contains a test Repo under test/support/repo.ex and associated migrations under test/support/migrations/*.exs.
I've configured the priv: option for the repo accordingly for the test Mix config:
config :my_lib, MyLib.Test.Repo,
  database: "my_lib_test",
  username: "postgres",
  password: "postgres",
  priv: "test/support"

Running MIX_ENV=test mix ecto.migrations produces:
Repo: MyLib.Test.Repo

  Status    Migration ID    Migration Name
--------------------------------------------------

Similarly, MIX_ENV=test mix ecto.migrate does not apply any migrations:
mix ecto.migrate

21:30:12.472 [debug] QUERY OK source="schema_migrations" db=1.0ms
SELECT s0."version"::bigint FROM "schema_migrations" AS s0 FOR UPDATE []

21:30:12.474 [info]  Already up

Expected behavior
The migration scripts in the test/support/migrations directory should be applied.
I believe this behaviour is due to the migrations path being initially validated relative to the mix project: https://github.com/elixir-ecto/ecto_sql/blob/master/lib/mix/ecto_sql.ex#L92
Then later re-evaluated relative to the Application.app_dir: https://github.com/elixir-ecto/ecto_sql/blob/master/lib/ecto/migrator.ex#L36 which evaluates to _build/test/lib/my_lib/test/support/migrations.  As this directory doesn't exist, no migrations are found.
If the new behaviour is intended, then any advice on managing a test-only repository and migrations for a library, such that the migrations are not included in the final hex package would be appreciated.
Thanks

Can you please provide a simple app that reproduces this? It will make it
much easier to fix the bug. Thank you!
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

I think I got a fix, can you please try master out? Thank!


Fix Ruby xDS Interop

https://github.com/grpc/grpc/pull/28665 upgraded the Ruby image but didn't fix up all of the references. This PR uses the updated reference.

Manual run


Discount calculator

This calculator calculates discount  and the final pay amount with discount percentage and bill amount as input .
Please assign this issue to me under JWOC

@S-ishita Go for it.


Parsing keys with spaces fails.

(. lib/json.bash; echo '{"files": {"first.txt": "Test", "second file": "Test" }}' | JSON.load )

This seems to be fixed already:
$ (. lib/json.bash; echo '{"files": {"first.txt": "Test", "second file": "Test" }}' | JSON.load )
/files/first.txt	"Test"
/files/second file	"Test"


Support is distinct from

SQL has an operator that is a null aware equality check. It could be interesting to build this as an operator or method on expression objects so that we can compare option types and have null == null

what should we call this?

identical


Feature request: sysvar access to the __2nd_jump_table

Can you insert a static sysvar to the __2nd_jump_table? That way ppl would have access to the vectors to change IRQ handlers
I have coded GPIO serial access for my hexload utility, but that currently needs to use a static address from the MOS 1.02 build. It would be great if programs could just retrieve the 2nd_jump_table and access it cleanly from MOS 1.0x onwards.
Access to _set_vector would be ever better, but it's not much code to copy over if we have just the sysvar. Thnx!

Marking as 'Won't Do' as it duplicates the functionality fixed in this card.
https://github.com/breakintoprogram/agon-mos/issues/33


Remove __all__ from mws.py

The upstream didn't have an __all__, it was a bad idea of me to add this in. I thought it made things cleaner but actually some applications might import things like MWS which is not listed in __all__. I actually have an application I developed some years back which does this.

This is covered by the current version of develop branch: there is no __all__ in the module. Instead, there are specific objects referred to by __all__ in the __init__.py modules within mws and apis directories:
https://github.com/python-amazon-mws/python-amazon-mws/blob/ebeb61c83779577c0e33bd20cee30fb60424c9ec/mws/apis/__init__.py#L1-L29
https://github.com/python-amazon-mws/python-amazon-mws/blob/ebeb61c83779577c0e33bd20cee30fb60424c9ec/mws/__init__.py#L1-L24

Nice one, looks like you have it covered!


[#226] Update to manage secrets with Github Environments for Staging and Production

Close #226

What happened 👀

Remove unnecessary token when checking out in bump_version workflow.
Fix: exporting multi-lines env files using quote "".
Convert some secrets to variables.
Move some secrets to the Environments config.

Insight 📝

To echo a multi-line variable in GitHub Actions, use quote "" https://stackoverflow.com/a/22101842/2100084 ✅
ENV_PRODUCTION and ENV_STAGING have been moved to the Environments ✅
FIREBASE_ANDROID_APP_ID_PRODUCTION, FIREBASE_ANDROID_APP_ID_STAGING, FIREBASE_IOS_APP_ID_PRODUCTION, and FIREBASE_IOS_APP_ID_STAGING have been converted to variables and moved to the Environments ✅
ANDROID_SIGNING_PROPERTIES_BASE64 is now become ANDROID_SIGNING_PROPERTIES without base64 encoded by using a multi-line variable ✅

Proof Of Work 📹

The bump_version workflow works properly without token to check out https://github.com/nimblehq/flutter-templates/actions/runs/5746348294/job/15575671352 👉  https://github.com/nimblehq/flutter-templates/pull/264 ✅

Updated secrets & variables management by using Environment

The app can read secrets properly from .env

We may need to check and update writing multiple lines later. Look good so far 👍

@doannimble It has been verified to work properly with this .env structure https://github.com/nimblehq/flutter-templates/blob/develop/sample/.env.sample ✅

Nice @luongvo . Actually, it can write and read, but it may be incorrect. Have you tried to print out SECRET and REST_API_ENDPOINT (on app) to check (with the build made by github action)?.

@doannimble Yes, the last build can not run to show the staging name with a black screen https://github.com/nimblehq/flutter-templates/blob/b2851fdae0687015c2fb1ca95f2d8b3205df1a17/sample/lib/main.dart#L117-L123


Cannot go to other page when using response-resource.

Summary of problem or feature request
Datatables cannot render the pagination when using response-resource. It only get the first result and no way to go to another page.
Code snippet of problem
$collections = SomeModel::paginate(10);

return Datatables::of(
  SomeResource::collection($collections)
)->toJson();

System details

Operating System All OS
PHP Version 7.3.9
Laravel Version: 5.5.45
Laravel-Datatables Version: 8.13.5

I would like to bump this as well.  I am also seeing the same issue.  Using the response-resource only returns the first 10 results and complete ignores everything else  and the pagination buttons are disabled.


Bump to version 0.39.1

Signed-off-by: Paul Mooring<EMAIL_ADDRESS>Description
Habitat version bump
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

This was resolved with #66 and #67


feat: make it possible to deactivate CR validation

Fixes #354

I know it's a bit late for this... but do we ever need to validate the CRD? Users would find out it's not there when they try to create CRs, with a standard K8s error message. The operator can totally ignore if the CRD exists it only cares about getting events about CRs.

The error message you get is quite cryptic, which is why I added the functionality in the first place. @daniellavoie also added additional validation to pick up on missing implements Namespaced as well since these two things are common "beginners" mistakes.

The methods/fields are renamed in #361 to address potential confusion on validation scope.


”Sânpaul” is listed in the drop-down menu

Description:
"Sânpaul" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Sânpaul" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Sânpaul, MUREȘ".


[Parameter Request] report 1094 "Job Transfer to Sales Invoice"

Could you please change the scope to protected of the following variables?
    var
        Job: Record Job;
        SalesHeader: Record "Sales Header";
        NewInvoice: Boolean;
        PostingDate: Date;
        InvoicePostingDate: Date;
        Done: Boolean;
//+New
protected  var
        NewInvoice: Boolean;
        InvoiceNo: Code[20];
//-New

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


RollAll initiative button does not work

Attempting to roll initiative using the "Roll All" button results in errors.

note: this only doesn't work when the source actor is deleted but their token is left on screen.

This was fixed at some point :)