Extending Array prototype throws an "You stumbled upon a bug" error

I'm trying to extend Array prototype and import ts file somewhere in my project. Doing so, however, throws the following error:
> dev
> npm run server

> server
> ts-node -r tsconfig-paths/register ./server

Server running at http://localhost:3000
Error<EMAIL_ADDRESS>You stumbled upon a bug in vite-plugin-ssr's source code. Reach out at https://github.com/brillout/vite-plugin-ssr/issues/new or https://discord.com/invite/qTq92FQzKb and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Do not hesitate to reach out as it makes vite-plugin-ssr more robust.
    at addString (/Users/alex/Developer/gated-art-web/node_modules/vite-plugin-ssr/dist/cjs/node/html/renderHtml.js:141:28)
    at renderTemplate (/Users/alex/Developer/gated-art-web/node_modules/vite-plugin-ssr/dist/cjs/node/html/renderHtml.js:151:9)
    at renderHtml (/Users/alex/Developer/gated-art-web/node_modules/vite-plugin-ssr/dist/cjs/node/html/renderHtml.js:37:24)
    at executeRenderHook (/Users/alex/Developer/gated-art-web/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:567:58)
    at async renderPage (/Users/alex/Developer/gated-art-web/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:89:30)
    at async renderPageWithoutThrowing (/Users/alex/Developer/gated-art-web/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:131:16)
    at async /Users/alex/Developer/gated-art-web/server/index.ts:42:25

My array extension code is as follows:
export { }

declare global {

  interface Array<T> {
    compactMap<E>(callback: (t: T) => E | null): Array<E>
  }

}

if (!Array.prototype.compactMap) {

  Array.prototype.compactMap = function<T, E>(callback: (t: T) => E | null): Array<E> {
    // eslint-disable-next-line @typescript-eslint/no-non-null-assertion
    return this.map(callback).filter(x => !!x).map(x => x!)
  }

}

Also made a bare bones project to reproduce the issue: https://github.com/akolov/vite-ssr-array-prototype-bug
Is there anything I'm doing wrong?

I'm using unmodified project created via npm init vite-plugin-ssr@latest.
And escapeInject template is also unmodified:
const documentHtml = escapeInject`<!DOCTYPE html>

        <meta charset="UTF-8" />
        <link rel="icon" href="${logoUrl}" />
        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
        <meta name="description" content="${desc}" />
        <title>${title}</title>

${dangerouslySkipEscape(appHtml)}

    `

I can't reproduce.
Publish a reproduction and I'll have a look at it.

Reproduction project is here https://github.com/akolov/vite-ssr-array-prototype-bug.git
Can reproduce every time, maybe something is odd about my environment. Not sure so any guidance would be greatly appreciated!
➜  vite-ssr-array-prototype-bug git:(main) npm run dev

> dev
> npm run server

> server
> ts-node ./server

Server running at http://localhost:3000
Error<EMAIL_ADDRESS>You stumbled upon a bug in vite-plugin-ssr's source code. Reach out at https://github.com/brillout/vite-plugin-ssr/issues/new or https://discord.com/invite/qTq92FQzKb and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Do not hesitate to reach out as it makes vite-plugin-ssr more robust.
    at addString (/Users/alex/Developer/vite-ssr-array-prototype-bug/node_modules/vite-plugin-ssr/dist/cjs/node/html/renderHtml.js:141:28)
    at renderTemplate (/Users/alex/Developer/vite-ssr-array-prototype-bug/node_modules/vite-plugin-ssr/dist/cjs/node/html/renderHtml.js:151:9)
    at renderHtml (/Users/alex/Developer/vite-ssr-array-prototype-bug/node_modules/vite-plugin-ssr/dist/cjs/node/html/renderHtml.js:37:24)
    at executeRenderHook (/Users/alex/Developer/vite-ssr-array-prototype-bug/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:567:58)
    at async renderPage (/Users/alex/Developer/vite-ssr-array-prototype-bug/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:89:30)
    at async renderPageWithoutThrowing (/Users/alex/Developer/vite-ssr-array-prototype-bug/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:131:16)
    at async /Users/alex/Developer/vite-ssr-array-prototype-bug/server/index.ts:33:25
^C⏎
➜  vite-ssr-array-prototype-bug git:(main) node --version
v16.14.0

I could reproduce.
This is quite weird indeed. I will dig.

Make your Array extension non-enumerable, that'll fix it.

This indeed has worked. Thank you for helping!


Feature request: supporting MDX for Components within blog markdown files

New to Astro here, and have tried to follow along some of the guides but weren't able to get this going. It seems that post.js is also a specific helper outside of the Astro files.
Would be glad to see an update to the theme with both .md and .mdx supported if that's something you ever get around to :-)

Pinging back here as I managed to get it working.
If you're interested in landing a PR, I'm happy to send one over.

That's awesome, I'll check it out!


fix(TDI-38924): Correct processing schema keys in snowflake components

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-38924
What is the new behavior?
Schema column key now works correct.
It allows manual keys for UPDATE and DELETE output operations.
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:

Was fixed nearly simultaneously with me in https://jira.talendforge.org/browse/TDI-38821

Pull request test result: success :star:


Including encoding information in text is error-prone

When libsass outputs UTF-8 characters outside of the ASCII range, it prefixes its output with encoding information. Depending on the level of compression, this is either in the form of @charset "UTF-8" or a Byte-Order Mark. For the unwary (me), the BOM inclusion can cause problems.
As an example, naively concatenating CSS causes styling bugs:
> let sass = "h1:before {\n    content: \"\9660\";\n}\n\n"
> let opts = def { sassOutputStyle = SassStyleCompressed }
> compileString sass opts >>= \(Right x) -> print @String (x ++ x)
"\65279h1:before{content:\"\9660\"}\n\65279h1:before{content:\"\9660\"}\n"
> --                                 ^ pesky BOM ends up in the middle of CSS

According to https://github.com/sass/sass/issues/1395 this is not configurable; it's the up to the CSS concatenater to handle this correctly. Fine. But we're using Haskell, we have expressive types, and I think we can be more user-friendly.
In my opinion, encoding information does not belong in text (e.g. in String, Text). Not only is the in-memory encoding an implementation detail, but the encoding only matters when converting to a Bytestring, or when performing IO. Having encoding information in-line is therefore error-prone and inconsistent (a BOM gets automatically converted -- obviously @charset "UTF-8" does not).
For backwards compatibility, I think it's better not to change any existing behaviour. But a new instance of SassResult could be added that's equivalent to (Bool, String). This would strip encoding information from the String if needed, and indicate whether it had done so. Using this new feature would make CSS concatenation straightforward.
If this sounds sensible, I'm willing to implement it (or something similar, suggestions are welcome).

I'll look at it some more tomorrow evening (and will post my thoughts here) but your solution seems good and I would welcome the change.

I've looked at the problem and I agree with you - this needs to be solved.
Regarding your solution - do we really need the flag? I think that introducing newtype that's equivalent to String/ByteString with stripped BOM or @charset "UTF-8" would be a cleaner solution. Also, if the flag would be helpful, I would rather encode it in the types themselves (i.e. use Either String StringWoBOM or sth like that).

do we really need the flag?

To flesh out my initial idea, consider:
data EncodingStripped a = EncodingStripped Bool a

instance Monoid a => Monoid (EncodingStripped a) where
  EncodingStripped a b `mappend` EncodingStripped c d = EncodingStripped (a || c) (b <> d)
  mempty = EncodingStripped False mempty

Then a user concatenating the CSS from several Sass files can tell if the result is ASCII encodable without having to do redundant work. If they don't care, this has a slight advantage over
data EncodingStripped a = AsciiEncodable a | NotAsciiEncodable a

in that they only need to match against one pattern (EncodingStripped _ t) rather than two.
But now that I think about it, I'm not sure the Monoid instance would be useful. If you're concatenating CSS, you probably have only a single Sass file that everything is imported into, and so any other CSS is from a different source.
For my purpose, I need to unconditionally remove the encoding information. So I think I'll implement it the way you suggest — if a different interface is desired, it will be easy to adapt.

Ah, I completely have missed that the flag would indicate whether the string is ASCII or not (and that the BOM-stripping indicator is just a side effect). Still, I think that this wouldn't be that useful - you either don't care about encoding, BOMs etc. (and use the first version), or just use UTF-8 (because something will eventually force you to it) and want the BOM stripped (and thus have the Monoid instance for free).


Unable to select user's response {acPollChoices}

Not able to select user's response {acPollChoices} from adaptive card via dynamic content or expressions within flow.

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

ID: bf788f3b-9ad6-3c79-689d-5f36c1ab292f
Version Independent ID: d8a78d1d-7f90-7fb1-b0f6-8ae6518031f1
Content: Create flows that post adaptive cards to Microsoft Teams - Power Automate
Content Source: articles/create-adaptive-cards.md
Service: flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@MSFTMan

Hi @RaisinBread42 . Thanks for submitting docs feedback. This doesn't look to be a documentation issue, so I will close this, but I suggest you post your question on the Power Automate Community forums I hope this helps.


VFS stat_sync free on nullptr

The POSIX stat test fails on res = stat("file666", ...);. The free on nullptr happens during throw unwinding. The bug is in VFS::stat_sync throw Err_not_found(...).
<vm>                 [x] stat() of folder that does not exist fails
num_outputs after increment:  3
<vm>
<vm> >>>> !!! CPU 0 EXCEPTION !!! <<<<
<vm> Page Fault (14)   EIP  0x18eb05   CODE 0x2
<vm> Page not present, trying to access 0x18
<vm> Page write failed.

 It's shown itself in many services and it crashes when C++ is calling free on something, such as during unwinding or even a std::vector destructor.

Haven't had this happen in a while (phew), closing this. Not happened since musl change.


App Store -- Presentation Issue

Hey, I just wanted to give an FYI regarding a minor, but confusing issue with your app in the App Store; I just read about your app on the web, and went to install it from the App Store, but when I searched for it by name, I got results for other RSS readers. Then, when I finally found it, the App Store displayed a little message at the top: "Not compatible with this device." I'm running Ventura 13.0.1 on an M1 Mini. Fortunately, I was able to download and install your app from your website, but I assume you would consider this situation to be sub-optimal, as it could deter people from using your app. I've attached some screenshots. Please let me know if you have any questions.
Thanks!

The macOS app is not available via the Mac App Store. The version you are seeing there is the iOS version, which we have flagged as not compatible with macOS.


export write-logging command for powershell

If this is something we want, we should make corresponding changes here once this is in.
Fixes #395

LGTM - @vtbassmatt says he's moved docs to another area so we do not need to make the corresponding docs change you referenced above


Add support for [no-]options

It's common pattern to use boolean options like --[no-]paginate. They are missing in docopt. Does it have any reasons not to include such functionality or it's just not yet implemented?

Using --sth=yes is an arbitrary interface and needs 'magic' values (yes and no). It also takes almost double to type.


Update Readme.md

Purpose

Upto date readme.

Goals

Upto date docs.

Approach

Update README.md

Codecov Report

Merging #221 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #221   +/-   ##
=========================================
  Coverage     62.47%   62.47%
  Complexity      119      119
=========================================
  Files            13       13
  Lines           597      597
  Branches         56       56
=========================================
  Hits            373      373
  Misses          196      196
  Partials         28       28

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7cd4f7...24027ec. Read the comment docs.


docs(utils-js): Improve docs for Util components page

Rephrase sentences and change structure for several blocks.

Codecov Report

Merging #226 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #226   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     20
  Lines         379    379
=====================================
  Hits          379    379

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 21df19a...963bd1a. Read the comment docs.


Authentication Fails in example app

@bibash28 please, update your .env file with the following config, be aware you need to use your own infura api key for making it work.
ENV_POLYGON_MUMBAI={"blockchain": "polygon", "network": "mumbai", "web3Url": "https://polygon-mumbai.infura.io/v3/", "web3RdpUrl": "wss://polygon-mumbai.infura.io/v3/", "web3ApiKey": "YOUR_INFURA_API_KEY", "idStateContract": "0x134B1BE34911E39A8397ec6289782989729807a4", "pushUrl": "https://push-staging.polygonid.com/api/v1"}


operator/eni: fix panic if metrics are not enabled

Fix the following panic in the operator if metrics are not enabled:
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8d9eac]

goroutine 1 [running]:
github.com/cilium/cilium/vendor/github.com/prometheus/client_golang/prometheus.(*Registry).Register(0x0, 0x2288ba0, 0xc00000e880, 0x0, 0x0)
        /go/src/github.com/cilium/cilium/vendor/github.com/prometheus/client_golang/prometheus/registry.go:276 +0x15c
github.com/cilium/cilium/vendor/github.com/prometheus/client_golang/prometheus.(*Registry).MustRegister(0x0, 0xc00055c648, 0x1, 0x1)
        /go/src/github.com/cilium/cilium/vendor/github.com/prometheus/client_golang/prometheus/registry.go:390 +0x76
github.com/cilium/cilium/pkg/aws/eni/metrics.NewPrometheusMetrics(0x1f1353b, 0xf, 0x0, 0x1)
        /go/src/github.com/cilium/cilium/pkg/aws/eni/metrics/metrics.go:109 +0xb39
main.startENIAllocator(0x4034000000000000, 0x4, 0x10, 0x4)
        /go/src/github.com/cilium/cilium/operator/eni.go:116 +0x5bb
main.runOperator(0x3946ee0)
        /go/src/github.com/cilium/cilium/operator/main.go:221 +0x154e
main.glob..func1(0x3946ee0, 0xc0004342d0, 0x0, 0x3)
        /go/src/github.com/cilium/cilium/operator/main.go:51 +0x2b
github.com/cilium/cilium/vendor/github.com/spf13/cobra.(*Command).execute(0x3946ee0, 0xc00003a090, 0x3, 0x3, 0x3946ee0, 0xc00003a090)
        /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:766 +0x2ae
github.com/cilium/cilium/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x3946ee0, 0x0, 0x0, 0x0)
        /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:850 +0x2fc
github.com/cilium/cilium/vendor/github.com/spf13/cobra.(*Command).Execute(...)
        /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:800
main.main()
        /go/src/github.com/cilium/cilium/operator/main.go:90 +0x1f0

If metrics are not enabled, provide an empty type which implements interfaces
needed by the ENI and EC2 subsystems within Cilium.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

test-me-please

Coverage increased (+0.05%) to 44.211% when pulling 51dc2263d58cf8e3caf7d2231494cb459a1f7577 on pr/ianvernon/fix-metrics-eni-operator into 8905ec5c54788c861f1a4653ccb3d7d44eed6d60 on master.


Marine clothes

About the PR
Adds clothes for the marines. Litteraly the title.

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

Ready to review.


cant use MIME type/subtype when something is set for MIME type/

i am trying to make onepath open glow on markdown files and nano on other text files. i did this with the following code:
$XONTRIB_ONEPATH_ACTIONS['text/'] = 'nano'
$XONTRIB_ONEPATH_ACTIONS['text/markdown'] = 'glow'

but it always opens nano, even on markdown files.
$XONTRIB_ONEPATH_ACTIONS['*.md'] = 'glow' is also ignored
the examples from the readme:
$XONTRIB_ONEPATH_ACTIONS['*.log'] = 'tail'           # tail for text type *.log files
$XONTRIB_ONEPATH_ACTIONS['text/plain.txt'] = 'less'  # less for plain text *.txt files

do not work, when paired with $XONTRIB_ONEPATH_ACTIONS['text/'] = 'nano' files with .log extenstion and plain files with txt extention still open nano...
this means you cant do anything with text/type as text/ is set by default.

Note that the $XONTRIB_ONEPATH_ACTIONS list has order and also types have order. The order is the priority.

oh, oke. didn't know that. that was the problem. thanks!


LibTiff Vulnerabilities and Dependencies

PyProj has tiff dependencies, which are not fully supported by the latest version of tiff, 4.6.0.
Essentially Tiff removed support for many features due to security vulnerabilities and lack of developer support: (http://www.simplesystems.org/libtiff/)
"Starting with libtiff v4.6.0, the source code for most TIFF tools (except tiffinfo, tiffdump, tiffcp and tiffset) was discontinued, due to the lack of contributors able to address reported security issues. tiff2ps and tiff2pdf source code has been moved in a unsupported category, no longer built by default, but are still part of the the source distribution. Other retired utilities are in a archive/ directory, only available in the libtiff git repository. Issues related to unsupported and archived tools will no longer be accepted in the libtiff bug tracker."
But in order to use PyProj, you need an old (vulnerable) version of Tiff, exposed to the following CVEs:
CVE-2023-41175
CVE-2023-40745
CVE-2015-7313
Please see below for an example:
/app # python
Python 3.11.6 (main, Oct  4 2023, 06:22:18) [GCC 12.2.1 20220924] on linux
Type "help", "copyright", "credits" or "license" for more information.

import pyproj
print(pyproj.version)
3.6.1
exit()
/app # apk list | grep tiff
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.18/main: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.18/community: No such file or directory
tiff-4.5.1-r0 x86_64 {tiff} (libtiff) [installed]
/app # echo "@edge https://dl-cdn.alpinelinux.org/alpine/edge/main" >> /etc/apk/repositories
/app # apk add --no-cache "tiff@edge"
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
(1/1) Upgrading tiff@edge (4.5.1-r0 -> 4.6.0-r0)
OK: 183 MiB in 68 packages
/app # apk list --installed | grep tiff
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.18/main: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.18/community: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/edge/main: No such file or directory
tiff-4.6.0-r0 x86_64 {tiff} (libtiff) [installed]
/app # python
Python 3.11.6 (main, Oct  4 2023, 06:22:18) [GCC 12.2.1 20220924] on linux
Type "help", "copyright", "credits" or "license" for more information.
import pyproj
Traceback (most recent call last):
File "", line 1, in
File "/venv/lib/python3.11/site-packages/pyproj/init.py", line 33, in
import pyproj.network
File "/venv/lib/python3.11/site-packages/pyproj/network.py", line 10, in
from pyproj._network import (  # noqa: F401 pylint: disable=unused-import
ImportError: Error relocating /usr/lib/libtiff.so.6: jpeg12_write_raw_data: symbol not found

Could you please provide the information for how you actually installed pyproj? And if you have the PROJ C/C++ library installed separately?
As far as I can tell pyproj does not depend on libtiff directly at all, but our PROJ C/C++ library dependency does depend on libtiff:
https://github.com/OSGeo/PROJ
The traceback from python reaching into C/C++ code (the _network.pyx and the binary .so version of it) are hiding the fact that this symbol not being found is part of a different dependence. At least I think so.

It's a little complicated because I'm trying to build everything on Alpine for a production environment.
It's extremely possible that the error comes from PROJ, and I only see it when I try "import pyproj" and it starts the traceback.
It's a multistage build but essentially I install all the build time dependencies, the pip install all the python packages (including pyproj) into a virtual environment. Then I install runtime dependencies (including proj 9.2.1) in a new image, and copy over the venv.
So it sounds like the issues is tiff 4.6 breaks proj 9.2.1 breaks pyproj. I'm trying proj 9.3.0 to see if that repairs the chain, but having issues getting it to install over other dependencies. Honestly might just have to mitigate the vulnerabilities at the application level and wait for the dependency graph to catch up.

When you install the build dependencies and runtime dependencies how are you doing that? Are you building them from source? Or installing from a package manager? I would assume that running proj or similar command line tool from PROJ would trigger a similar error. That would at least cut out the pyproj part of the equation.
For building pyproj, are you pip installing from source or from PyPI? If PyPI, is it using a wheel on PyPI or is it downloading the .tar.gz source tarball and building from that?

I think you are correct that this is not a pyproj issue- think that it likely lies at the alpine level, ensuring that the dependency graph is well-coordinated. Going to close this issue.


Panda grid scans: Panda needs to keep fast shutter open during entire scan

The panda currently triggers the eiger and tells the fast shutter to open at the same time. The fast shutter isn't that fast, so we end up having nothing show up on the detector. Like the regular fast grid scan, we should make sure the fast shutter opens at the beginning of the scan and closes at the end - and also closes if there are any errors.
A sensible solution would be to open the shutter when the panda receives its first physical signal from the PPMAC (this signal indicates the scan is beginning). In Hyperion we should calculate the expected number of rows for the scan, and this corresponds to the expected number of physical triggers that go to the panda. Then, use the panda's inbuilt counter to keep track of the number of physical triggers. Once it reaches the expected number, close the fast shutter.
Acceptance Criteria

Hyperion correctly calculates the expected number of triggers (expected number of rows) and configures the panda to wait for the counter to get to this value in setup_panda.py

In setup_panda.py, make sure the fast-shutter is closed during the tidy-up

The panda is configured (via the web-gui) to send a high trigger to the fast shutter, and keeps this signal high while the counter value is between 1 and its expected number

The updated panda configuration is saved to a yaml file, and replaces the old one. (This yaml file should be added to the daq-config git repo)

Unit tests for all the new hyperion logic

Better solution discussed with @DominicOram : OUTA1 on panda's sequencer table is high while the smargon is travelling through each row, then goes low upon Y change. If connect the OUTA1 signal to the fast shutter (TTLOUT2) then the shutter will open during each row and shut during each direction change, and hyperion doesn't need to know anything about it.
We should still close the shutter during Hyperion's tidy-up plan though.

Closing in favour of https://github.com/DiamondLightSource/hyperion/issues/1116, which solves this issue


what can I do?could not be initialised

When I Accessory Simulations for garagedoor.There are some 'Yellow Words':
[eWeLink] [车库门] could not be initialised as Cannot read property 'context' of undefined at new deviceGarageOne (/homebridge/node_modules/homebridge-ewelink/lib/device/simulation/garage-one.js:51:80).
Just like this:

This is the setup:

And if I delete the Sensor,then restart ,it works.
So what shall I do ? Thx a lot.

Do you get that message in the log everytime you restart homebridge? or just the first time after adding the sensor to the config?

I've checked it out.Every time the message appears.

Is this the sensor that you are using for the garage?

maybe I found the key,I didn't use my main account,and I use the Id on the sensor,not the ewelink ID in the photo.

how can I remove the existing accessory from the cache?

how can I remove the existing accessory from the cache?

In the homebridge settings you can use the remove single accessory from cache setting

I solved that question.But there is a new one.

It keep reading...

Check in the eWeLink app if the device is shown as 'offline'.
The online/offline state of any device is reported by eWeLink to the plugin.

The device in app is ok.  But the garagedoor keep reading ,never stop.

Can you physically open/close the garage door to activate the sensor and see if any messages appear in the homebridge log?

There is no message in log. I am going to try vertion 6.6.0

Also this issue. I think the switch can' tread the sensor's state.

The issue seems to be that the plugin isn’t receiving any status updates from ewelink.
can you restart your router so the dw2 has to reconnect to the internet?
Once the plugin receives these status updates, it updates the garage door accessory accordingly.
If the plugin doesn’t receive these updates then the garage door accessory won’t change from its previous state.

I tried , but doesn't work. Anyway, thank you so much.

The log entries that need to be appearing are
receiving update……. from the 2377f6 device.
But there don’t seem to be any in your logs.
The fact that ewelink is marking the device as “offline” must have something to do with this.
Does the contact sensor accessory appear in your Home app?

Yes, in fact there is always the contact sensor in my homekit, whatever I choose hide or not hide the sensor. And the state of the sensor will change to open if the garagedoor is open.

I create a new account,and these device again. Now, it can read the sensor's state. But my switch still spin. The DW2's name is 'sensor'.

From your latest logs it’s doesn’t look like the switch has been setup as a garage simulation, please verify your config, as the logs should include that the switch is setup as a garage

can you turn on debug logging again and restart the plugin and show me the logs?

I think maybe the sensor's state isn't '1',so the switch keeps reading for the '1' state?

Did you also update your config with the correct id of the sensor?
Can you show me your ewelink config again? (remove phone number + password!)

I have just published another beta, v6.7.1-beta.2
It might take a few minutes for it to appear available in the homebridge-ui but please update and let me know if it has fixed anything.

Ok,I will update and try. thank you for your time.

Thank you so much.It works perfectly.The state is correct , the sensor can hide now. Thank you for your time.

Excellent 👍 got there in the end!


Fixed index error on deps parsing

Added additional check that list is not empty
Close #6

Perfect! Thank you


Feature request

Hi, I saw this and wondered if the following would be possible:
Bluetooth-capable version
Create a new version that includes a Bluetooth transceiver so wireless headphones are compatible. I guess that you will also require a small LCD to list the Bluetooth devices that have been detected. I don't see why this could not work with factory models.
Game audio capable (moded-xbox only)
The OG Xbox communicator only plays party chat audio. However, could the BIOS or OS be configured to route game audio to the controller? It would be great to listen to both party and game audio via headphones. I'm not sure if it is possible at a hardware level, but for example, the game Manhunt played some in-game sound effects through the communicator. So, I guess that it should be possible (it might require lowering the audio quality).
Thanks for your excellent work!

Closing as not really an issue and out of the scope of this project.
I'm sure it is all possible. Maybe you or someone else could give it a shot


feat: adds support for track_latest

what

Adds track_latest and bumps provider version to v5.37.0 accordingly.

why

Allow users to make the task definitions track always the latest one if track_latest is set to true.

references

Closes https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/issues/221
See original addition of this argument to the provider here: https://github.com/hashicorp/terraform-provider-aws/pull/30154

/terratest

/terratest

/terratest

/terratest

Reverted TF bump due to community concerns (see also the Slack thread).


Use region as facility instead of zones

How to categorize this PR?

/kind bug
/priority normal
What this PR does / why we need it:
Equinix Metal doesn't have the notion of availability zones as other cloud providers do. While likely possible technically, spanning a k8s cluster across multiple geographical regions is usually discouraged in the k8s community. Therefore, use the specified region as the only value passed in the "facility" field of all worker pools.
Without this change, deploying a shoot using the following cloud profile and shoot manifests fails:
---
apiVersion: core.gardener.cloud/v1beta1
kind: CloudProfile
metadata:
  name: packet-flatcar
spec:
  type: packet
  kubernetes:
    versions:
    - version: 1.19.3
    - version: 1.18.12
  machineImages:
  - name: flatcar
    versions:
    - version: 0.0.0-stable
  machineTypes:
  - name: t1.small
    cpu: "4"
    gpu: "0"
    memory: 8Gi
    usable: true
  volumeTypes:
  - name: storage_1
    class: standard
    usable: true
  - name: storage_2
    class: performance
    usable: true
  regions:
  - name: ams1
  providerConfig:
    apiVersion: packet.provider.extensions.gardener.cloud/v1alpha1
    kind: CloudProfileConfig
    machineImages:
    - name: flatcar
      versions:
      - version: 0.0.0-stable
        id: flatcar_stable

---
apiVersion: core.gardener.cloud/v1alpha1
kind: Shoot
metadata:
  name: my-em-cluster
  namespace: garden
spec:
  seedName: aws
  cloudProfileName: packet-flatcar
  region: ams1
  secretBindingName: core-packet
  provider:
    type: packet
    infrastructureConfig:
      apiVersion: packet.provider.extensions.gardener.cloud/v1alpha1
      kind: InfrastructureConfig
    controlPlaneConfig:
      apiVersion: packet.provider.extensions.gardener.cloud/v1alpha1
      kind: ControlPlaneConfig
    workers:
    - name: worker-xoluy
      machine:
        type: t1.small
      minimum: 2
      maximum: 2
  networking:
    nodes: <IP_ADDRESS>/25
    type: calico
  kubernetes:
    version: 1.18.12
  maintenance:
    autoUpdate:
      kubernetesVersion: true
      machineImageVersion: true
  addons:
    kubernetes-dashboard:
      enabled: true
    nginx-ingress:
      enabled: true

    Description:  task "Waiting until shoot worker nodes have been reconciled" failed: Error while waiting for Worker shoot--garden--my-em-cluster/my-em-cluster to become ready: extension encountered error during reconciliation: Error reconciling worker: failed to deploy the machine classes: failed to apply manifests: 1 error occurred: could not read object: error 'error converting YAML to JSON: yaml: line 24: could not find expected ':'' decoding manifest:
---
# Source: machineclass/templates/machineclass.yaml

---
apiVersion: v1
kind: Secret
metadata:
  name: shoot--garden--my-em-cluster-worker-xoluy-89d7d
  namespace: shoot--garden--my-em-cluster
  labels:
    gardener.cloud/purpose: machineclass

type: Opaque
data:
  userData: REDACTED
  apiToken: REDACTED
---
apiVersion: machine.sapcloud.io/v1alpha1
kind: PacketMachineClass
metadata:
  name: shoot--garden--my-em-cluster-worker-xoluy-89d7d
  namespace: shoot--garden--my-em-cluster
spec:
  projectID: REDACTED
  OS: flatcar_stable
  billingCycle: hourly
  machineType: t1.small
  sshKeys:
    - REDACTED

  secretRef:
    name: shoot--garden--my-em-cluster-worker-xoluy-89d7d
    namespace: shoot--garden--my-em-cluster
  tags:
    - kubernetes.io/cluster/shoot--garden--my-em-cluster
    - kubernetes.io/role/node

  facility:
  null

Release note:

Packet facility is now handled correctly.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you @johananl for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.


Update PopUp descriptions

Is your feature request related to a problem? Please describe.
Pop-ups are difficult for general users to understand, and formatting is inconsistent
Describe the solution you'd like
Implement a consistent format for the pop-up information so each contains:

a description of the setting
the default value

This should be combined with a restructuring of the menus for better UX that leads to users having a better understanding of when each setting is utilized by Trio. The restructuring work is already in progress by @polscm32 and @dnzxy (PR not yet submitted)

hey 👋 - silence for 30 days 🤐 ... anybody? triage is required!


lazyLoad is showing html validator error

Element img is missing required attribute src.
img class="lazyOwl" data-src="http://xys/19/WrestleJump.jpg" alt="Wrestle Jump "

Not planning on fixing this.


#2: support stacked icons

fixes #2
I think it'd be better to change the background color to transparent as most users want that way.

Thanks for the PR. I have a few issues with style and functionality. Things that should be changed:

deselecting the stacked icon should remove the icon
ability to select the icon that you want to edit
maybe add a list of icons that is clickable so you can stack multiple
use the same style for the new text as the rest of the application uses

If you don't have time I will try to look into it this or next week
Cheers!

Regarding 2), although it's good have multiple I think 2 is just enough for this. The current flow is simple, select 1st icon if stacked, second select is the stacked one. It's consistent with the idea of click and change from the beginning.
Agreed with 1 and 3, i can make changes.

made 1) and 3), please review

Thanks for the updates. I think in 1) the frame should immediately redraw once the deselection takes place. And when you select the second icon again the same icon should reappear.

I fixed the deselection issue

And when you select the second icon again the same icon should reappear.
Not sure what you mean?

So I did some refining. Please take a look if this works for you.
PS: I was on an old computer and I think the old git version messed up the commit (files changed shows everything).

Thanks. LGTM


[Suggestion] Show history, how wait times change during the day

Perhaps you could show history, how waiting time changes during the day? It could help planning the trip to store

Hello,
it might be useful to keep a history of at least two weeks, in order to make the comparison and try to make a prediction on future times.
It's not a simple thing, but it's definitely a good idea.
I'll see how to implement it, looking for an efficient way to do it.
Thanks

Perhaps an API for specific locations would be a good intermediate solution.
That way a user could just pull the data for the place they're interested in at different times of the day, and then store (and analyze) it themselves.


Add Roadmap to Introduction doc

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2238
Originally created by @DouweM on 2020-08-12 15:59:50

With links to milestone / issue boards and "Accepting Merge Requests"?

View 3 previous comments from the original issue on GitLab


Allow changing slashing rules without changing the ENS usernames address

There is a lot of discussion on what are the best rules for invalid usernames. To avoid problems when this rules needs to be changed, they need to be well thought and the contract designed to have this piece portable.

Fixed by #103


Unable to create new app registration with SignInAudience

I am trying to use the New-AzureADApplication command to register a new application in my B2C directory and from the documentation (New-AzureADApplication) it appears that I can pass in a value to the -SignInAudience parameter but I've got an error saying that the parameter is read only.   Please help.

Connect-AzureAD -Tenant MyB2CTenant.onmicrosoft.com
new-azureadapplication -DisplayName testb2c -SignInAudience AzureADandPersonalMicrosoftAccount -IdentifierUris @("api://testb2c")
new-azureadapplication : Error occurred while executing NewApplication
Code: Request_BadRequest
Message: Property 'signInAudience' is read-only and cannot be set.
RequestId: 06d0b6ba-6cdb-4818-a802-6f3e651c106a
DateTimeStamp: Sun, 17 Jan 2021 00:54:27 GMT
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
At line:1 char:8
+  $app = new-azureadapplication -DisplayName testb2c -SignInAudience Az ...
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+   CategoryInfo          : NotSpecified: (:) [New-AzureADApplication], ApiException
+  FullyQualifiedErrorId : Microsoft.Open.AzureAD16.Client.ApiException,Microsoft.Open.AzureAD16.PowerShell.NewAppl
ication

My environment:

The directory is an Azure AD B2C directory
I am trying to register an application for sign-in using user flow (hence the SignInAudience)

@midway500
I have opened a work item for this so that engineering can take a look and possibly address this. Unfortunately, these examples are coded in the source and generated automatically, so any updates would get overwritten once we update this again. We need to get engineering to change this in the code. At this point, I am going to go ahead and close this issue and will post any update I have here. Thanks!
Bill

@midway500
I have opened a work item for this so that engineering can take a look and possibly address this. Unfortunately, these examples are coded in the source and generated automatically, so any updates would get overwritten once we update this again. We need to get engineering to change this in the code. At this point, I am going to go ahead and close this issue and will post any update I have here. Thanks!
Bill


logarithmic gamma function

#3408
I implemented logarithmic gamma(lgamma) function. (along with digamma and polygamma)
As mentioned in this issue, I have not implemented effective calculation for with gpu.

digamma and polygamma don't exist in numpy and `math. Therefore I implemented like this for now.
Should I implement numerical calculation of digamma like scipy?
Or is there any good solution?

Could you make the tests being skipped when scipy is not available, and add a test to check if an appropriate error is raised on such environments? The skip can be done with @chainer.testing.with_requires('scipy'): https://github.com/chainer/chainer/blob/master/chainer/testing/helper.py#L20-L46.

Should I implement numerical calculation of digamma like scipy?
I think it's good to provide such a simple CUDA implementation.

I implemented digamma and polygamma with gpu.
However, this implementation is same as cupyx.special.digamma and cupyx.special.polygamma. cupy/cupy#1232
So I want to use cupyx.special.digamma and cupyx.special.polygamma directly.
Can I do?

I'm amazed by your coding speed! Of course, it's better to avoid duplication with cupy, so it's totally fine to use cupy functions for digamma/polygamma.

cupy/cupy#1232 has been merged. Could you fix the GPU code to use them?

Jenkins CI test (for commit 69782cc1c473f543d7996e9edace70e676e26db8) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 6fe2979433995f4354dbac90c584370f5e1c650a) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Enhanced 3D Design for User Engagement and Attraction #135

To boost user engagement and make the interface more appealing, I’ve incorporated a 3D look into the design. This visual enhancement adds depth and a modern touch, making the overall experience more immersive and interactive. As the main contributor to this feature, I’ve ensured that the 3D elements are seamlessly integrated, providing a captivating look without compromising functionality. This approach not only elevates the aesthetics but also enhances user interaction, making the platform stand out
Uploading Collect your GamingTools - Google Chrome 2024-10-06 19-42-17.mp4…

level?

To boost user engagement and make the interface more appealing, I’ve incorporated a 3D look into the design. This visual enhancement adds depth and a modern touch, making the overall experience more immersive and interactive. As the main contributor to this feature, I’ve ensured that the 3D elements are seamlessly integrated, providing a captivating look without compromising functionality. This approach not only elevates the aesthetics but also enhances user interaction, making the platform stand out
Uploading Collect your GamingTools - Google Chrome 2024-10-06 19-42-17.mp4…

@Ek-ta-bharti I reviewed the code and noticed that several important lines in the HTML file were removed. It’s crucial to ensure that no key functionalities are affected before submitting a PR.
Please double-check the changes before making a PR next time, and if you need help understanding any part of the code, feel free to ask!


[UI] Update ToC when nodesMap change

Summary

Restore node2children and buildNode2Children() in canvasSlice
Update ToC using node2children
Fix issue #503

Test

Thanks!


Cors Middleware error: Can't modify immutable headers.

What version of Hono are you using?
3.2.7
What runtime/platform is your app running on?
Clodflare Workers
What steps can reproduce the bug?
app.use('*', cors({ origin: '*' }))

What is the expected behavior?
Modify the response headers
What do you see instead?
Server Internal Error - Status Code 500
Log:
Trace: TypeError: Can't modify immutable headers.
Additional information
response headers cannot be modified
https://github.com/honojs/hono/blob/main/src/middleware/cors/index.ts#L36C18-L36C18

Hi @anarkrypto,
I can't reproduce the bug with only that information. Could you provide a minimal project or snippet to reproduce it?

Seems related to #1606.

I ran into this issue where I was proxying requests with a catch all route to a DurableObject; something like:
app.use("*", cors());
app.all("*", async (ctx) => {
  const id = ctx.env.MYOBJECT.idFromName("myobject1");
  const obj = ctx.env.MYOBJECT.get(id);
  return await obj.fetch(ctx.req.raw);
});

In the DurableObject I was also routing with another instance of Hono. Moving the app.use("*", cors()) to the instance used by the DurableObject seemed to correct this error for me.

I'm also seeing this issue when directly returning a response from a fetch call in the worker. The CORS middleware must be trying to modify headers of the response of the fetch which are immutable.

@nicksrandall
This is a Web API limitation. Please create a new Response object and return it as follows.
app.get('/', async (_c) => {
  const response = await fetch('https://example.com')
  const newResponse = new Response(response.body, response)
  return newResponse
})

Hi @yusukebe, would you agree that in this context the Proxy example is wrong? Because using exactly same thing I receive same Can't modify immutable headers.
Excerpt from URL: https://hono.dev/guides/examples#proxy
import { Hono } from 'hono'

const app = new Hono()

app.get('/posts/:filename{.+.png$}', (c) => {
  const referer = c.req.header('Referer')
  if (referer && !/^https:\/\/example.com/.test(referer)) {
    return c.text('Forbidden', 403)
  }
  return fetch(c.req.url)
})

app.get('*', (c) => {
  return fetch(c.req.url)
})

export default app

If you just return the Response retrieved by fetch to the user as is, there is no error. For example, Cloudflare has an example.
export default <ExportedHandler>{
  async fetch(request) {
    /**
     * Replace `remote` with the host you wish to send requests to
     */
    const remote = "https://example.com";

    return await fetch(remote, request);
  },
};

However, if you modify the header of the Response, you will get an error, so you need to clone it.

Alright, thanks to your response and this thread it has finally ticked that it's the middlewares (incl. cors) that I'm using that causes the error. Perhaps we should add a comment so for future tinkerers like me it'd be helpful :)

@flexchar Great!
cc: @sor4chi If possible, please consider documenting this matter!

Hi, @yusukebe
Let me see if I'm interpreting this correctly.
In summary, "If you use a middleware that rewrites headers like cors, you need to register a handler for proxy before that middleware is registered, or generate a new response object from the proxied response and return it"?

@sor4chi
This is about the following. That is, the Response retrieved by fetch can be returned, but if you modify the headers, you need to clone.
https://github.com/honojs/hono/issues/1572#issuecomment-1890910579

@yusukebe
Understood. I will write this annotation in the example document part of the proxy for now.

Thank you!!

Closing.


feat: versioned docs

The way versioned documents are supported on the site differs a bit from
Docusaurus' documentation:

Each doc change to a branch is build and publish separately.
The links to the versions are _blank to bypass react-router even
though the content is in the same server. The reason is that because
it is built at different steps it is not "found".

This is achieve thanks to electron-website-updater sending a
repository_dispatch event with 2 different types of actions for each
push event that happens in electron/electron that contains doc
changes. The 2 types of events are:

doc_changes_previous: Updates to branches that are not the latest
stable.
doc_changes: Updates to the latest stable branch.

The tasks to perform are almost identical:

Build the content of the payload in the right folder (vXX-x-y)
Publish the content to storage
Clean up any docs folder and git add versions-info.json in case
there is a new version to track
If the payload is for the latest, then update the source
(package.json, sidebars, docs, etc.) and upload to Crowdin
Push or PR to main if needed (push-main.yml will take care of
building and publishing /latest/)

Fix #118

Need to figure out what happens with the sidebars when we are publishing a previous version and there are "missing documents" 😓


Document the AWS Layer ARN for each release in the same way that the Node repo does

Expected Behavior
Node Lambda Layer Release Tag
Actual Behavior
Golang Lambda Layer Release Tag
Steps to Reproduce the Problem
I cannot figure out what ARN I should use for this repo.
Per Datadog's documentation, the format is
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-<RUNTIME>:<VERSION>

However, per the documentation here: https://docs.datadoghq.com/integrations/amazon_lambda/?tab=go#installing-and-using-the-datadog-layer, Go's RUNTIME value is: N/A.
Given that, for the life of me, I cannot figure out the format of a valid ARN for this repo.
Adding an example to either the Readme notes or each release   tag (a la the Node repo) would be a tremendous help.

Hi @pnldata3,
Thanks for the feedback! We should document this more explicitly. Since Go is a statically-linked language, you cannot dynamically link dependencies after compilation. This means that you need to include the Datadog Lambda package in your code at compile time and that we cannot distribute a Lambda Layer for it.
We're able to provide Lambda Layers for Python, Node, Ruby, etc. because they allow for dynamically-linked dependencies.

Ahhh... that makes sense.   Thanks for clarifying!


Unable to read home directory

Tried the following command in NPM but it does not work as expected on macOS.
# package.json

{
 "scripts": {
  "start": "env-cmd ~/some-secrets.env node ./dist/server",
 }
}

# Warning message shows an incorrect path to read the ENV file.

$ npm run start

WARNING:
      Could not find or read file at:
        /Users/my-mac/test-repo/Users/my-mac/some-secrets.env
      Trying to fallback to read:
        /Users/my-mac/test-repo/.env

I was literally just looking at the path resolving for env-cmd the other day, this is a good excuse to revisit it and fix it once and for all.
Just fyi, ~ is a bash specific character that nodejs does not resolve by default. Having said that, I use bash myself, so I want it to resolve to the home dir as well 😄
I have fixed it on this branch here: https://github.com/toddbluhm/env-cmd/pull/30 . But its late here so I am heading to bed and will run a deploy tomorrow. This will be a breaking change because of how it changes the pathing schema. See the PR for details on the changes. I will update the Readme with the new pathing schemas tomorrow.

@toddbluhm 👍 to the fix based on excuses! This package is going to be awesome once again! 🎉

This has been released on npm as version 7.0.0


rm UnPack dep

Purpose
closes #520

This PR is also updating julia to 1.9.4 in some of the manifest files. If the coupler is still at 1.9.3, I'd suggest regenerating the Manifest files.


a problem on publish with http request

when i do stress test with mine website, i use a iteration as follow to publish message:
/**
 * @file web-pub.php
 */

$client = new Mosquitto\Client(uniqid());
$client->connect('server.mosquitto', 1883, 60);
for($i = 0; $i < 1000; $i++) {
    $client->publish('/test/stress', 'message stress test '.$i);
}

and then I use  http_load to send 100 request to the server, If working properly, i will receive 100000 messages in test client, but, in actually, I only can receive about 70000 messages, about 30k messages is lost.
i guess the method Mosquitto\Client::publish created a thread to send message to the broker, and if the message inflight queue is long enough, the PHP process finished processing the request and then exit without waiting for the socket thread finishing work.
this will cause message lose in high concurrent server!

It doesn't create any threads, but in order to process the message queues, you need to call $client->loop() periodically to let the underlying library do what it needs to do. You could call it once every 10 message publishes or so, which would probably be enough (though I've not tested).


Release 2.5.0

Bump version
Add @AdamGleave  to the maintainer list

Closing because github handle it badly. Will reopen a clean one.


Add type definition for IBM Cloud specific ConfigurationOptions

This PR has been integrated into our upcoming node 1.4.1 release.
Thanks for the PR, unfortunately we can't use this PR due to the build release process we have in place.


Some Code Error In The Doc

I just found a very little problem in the document which is in the (PRO) Dead Cells, the Input Setup Section.
In "input setup task that prepares the level description"
levelDescription.AddCorridorConnection(connection, RoomTemplates.CorridorRoomTemplates.ToList(), corridorRoom);
It should be
levelDescription.AddCorridorConnection(connection, corridorRoom,RoomTemplates.CorridorRoomTemplates.ToList());

Thank you! I'll fix that.


Allow merging two Extensions maps

Motivation: https://github.com/tokio-rs/axum/issues/770
Prior art: The anymap crates allows this through map1.extend(map2.into_raw()) (AFAICT, haven't tested)

Seems like this isn't actually needed for that axum feature.

We're back to wanting this in axum 😄

tokio-rs/axum#950

I'll create a PR for this.


Suggestion: Support serialization of TypeScript class objects

It would be nice with out-of-the-box support for serialization of class objects, currently all class info is silently lost if storing/restoring a TypeScript object. For instance, integrate with https://www.npmjs.com/package/serializer.ts.

This would be pretty hard to do, as how would ionic-storage find out which class to use for deserialization? Also how it should react if something changes in the class definitions? This features sounds like a lot more like an userland feature.
A very basic implementation can be:
import { Storage } from '@ionic/storage';
import { deserialize } from "serializer.ts/Serializer";

export class CacheStorage {

  constructor(private storage: Storage) {

   }

  /**
   * Get the requested resource and cast it to the specified type.
   * @param key key identifying the requested resource
   * @param classType class of the requested resource
   * @returns Promise resolved with the value casted to the specified type
   */
  get<T>(key: string, classType: any): Promise<T> {
    return this.storage.get(key).then( value => {
      return deserialize<T>(classType, value);
    })
  }
}

As for which class to use, the caller could specify the class name to use by the deserializer and then cast a general object returned.
I still think such out of the box support would make sense with ionic2 - the framework is based on TypeScript so you should be able to store TypeScript objects without any hassle (such as installing typings, installing serializer.ts, writing custom code).

Some kind of ORM? Sounds interesting, not in the current scope or plans but will keep open to gather thoughts/opinions

I think ORM features are a bit overkill for something as conceptually simple as Ionic storage. Serialize to a blob and deserialize back again is sufficient, you don't care about the actual representation in storage. Just as how local storage (or Ionic storage) is typically used with JSON objects - with the addition of correctly marshalling class information so it can be cleanly used with TypeScript class instances.

Closing for now.


CNDB-11762: Remove StorageAttachedIndexQueryPlan#postProcessor

StorageAttachedIndexQueryPlan#postProcessor seems redundant because coordinator-side sorting+triming of ANN query results is already done in SelectStatement. If that's the case, we should remove it.
Checklist before you submit for review

[ ] Make sure there is a PR in the CNDB project updating the Converged Cassandra version
[ ] Use NoSpamLogger for log lines that may appear frequently in the logs
[ ] Verify test results on Butler
[ ] Test coverage for new/modified code is > 80%
[ ] Proper code formatting
[ ] Proper title for each commit staring with the project-issue number, like CNDB-1234
[ ] Each commit has a meaningful description
[ ] Each commit is not very long and contains related changes
[ ] Renames, moves and reformatting are in distinct commits

it looks like the whole postReconciliationProcessing -> postProcessor chain can be removed since the only remaining postProcessor is a no-op?

it looks like the whole postReconciliationProcessing -> postProcessor chain can be removed since the only remaining postProcessor is a no-op?

Probably yes, since I think we don't have 3rd party 2i implementations using it for sorting.
I suspect that in the long term sorting will be better placed at the same level as postReconciliationProcessing, in the org.apache.cassandra.db package, rather than embedded in CQL. But for now, we can remove it and keep using the CQL version of sorting, which seems more evolved (and faster!).

@michaeljmarshall will you have time to review this? It should be a nice performance improvement for coordinators.

The two test failures labeled as regressions are for detected leaks. I commented on https://github.com/riptano/cndb/issues/11910 with a reference to this PR. They are not related to this PR, so I am going to merge this now.

Thanks for reviewing and merging :). There wasn't a PR for adding this to CNDB yet, so I have created this one: https://github.com/riptano/cndb/pull/12076
That PR also includes CNDB-11950, for which I haven't found the matching PR bumping the CNDB version.


feat: Automate installation of required libraries.

Description
This commit automates the installation of the ollama, litellm, chromadb, and psycopg2 libraries when they are not found.

progresses: #1768

With this pull request, we have completed automating the installation of all dependencies in the mem0/* directory.
File changes:
mem0/embeddings/ollama.py
mem0/proxy/main.py
mem0/vector_stores/chroma.py
mem0/vector_stores/pgvector.py
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[x] Unit Test

Checklist:

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

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

@Dev-Khant With this pull request, we have completed automating the installation of all dependencies inside the mem0/* directory.

@Jai0401 Thanks for contribution. Much appreciated!


egressgw: init gatewayIP to <IP_ADDRESS>

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

Always init gatewayIP to <IP_ADDRESS> by default instead of the previous nil value. Before this commit the rules that didn't match any node where added in addMissingEgressRules and removed right after in removeUnusedEgressRules. The egressmap auto convert nil to <IP_ADDRESS> and removeUnusedEgressRules doesn't do anything to match nil and <IP_ADDRESS>.

/test

/test-1.26-net-next

/test-1.26-net-next

(looks like net-next is hitting https://github.com/cilium/cilium/issues/24667)

/mlh new-flake Cilium-PR-K8s-1.26-kernel-net-next

net-next failure looks like an unrelated flake, marking as ready

@jibi Note I don't think MLH managed to create the flake issue.

We're also missing an approving review.

We're also missing an approving review.

I thought I had already approved it


raftstore: Handle CheckCompact task from underlying engine

What is changed and how it works?

Issue Number: Close #xxx
What's Changed:
We use max_compact_index and max_compact_term to record the newest CompactLog index from Leader. It is monotonicly increased in-memory value. After the underlying engine reject a CompactLog cmd by pre_exec, the max_compact_index can still be updated.
We allow underlying engine scheduling a CheckCompact task, when executing the task, we will check if it is from underlying engine. If it is true, then we will try to compact to the compacted index reported by the engine. However, the compact index must not exceed recorded max_compact_index.
When write RaftApplyState, we must use the applied_index from the underlying engine, because the underlying engine may flush asyncly.

raftstore: Handle CheckCompact task from underlying engine

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
None

/test


2022 tree inventory

Updated diameters and status (live/dead standing/dead down) based on today's measurements.
Also a basic qa/qc script — much more to do here later — and fixes to date formatting of older data.

Awesome!


using ops to implement steps/make_fbank_pitch.sh

replace this cmd steps/make_fbank_pitch.sh --cmd run.pl --nj 2 --write_utt2num_frames true data/test exp/make_fbank/test fbank by ops
Originally posted by @zh794390558 in https://github.com/didi/delta/pull/52#issuecomment-524861103
ops:
https://github.com/didi/delta/tree/master/delta/layers/ops
feat:
https://github.com/didi/delta/tree/master/delta/data/feat
output:
put make_fbank_pitch.sh into delta/utils
reference:
https://github.com/espnet/espnet/tree/master/espnet/transform

To remove the kaldi dependency


Error on import

Getting an "Error: Sorry, the preset couldn't be imported as it seems to be in the wrong format." when I try to import. Running BTT version 2.531 (866) (latest version).

@aazlant all preset? Can you say exactly what you are doing?

Yup, all presets. I'm following instructions, either selecting Manage Presets -> Import, or double-clicking on a .bttpreset file, same result.

should be a .json file

Probably this is something related with you configuration or you BTT not the GitHub project, I tested her and worked.

This is on a brand new install. The only thing that I can think of is that I'm on a 2018 MPB.

Same problem here. It won't import it.

Guys I just test here, cloned again and import 3 presets. Work.
Is something local or with the new BTT, not about this project.

What version do you have it working with?
On Fri, Jul 27, 2018 at 12:21 PM Victor Canato<EMAIL_ADDRESS>wrote:

Guys I just test here, cloned again and import 3 presets. Work.
Is something local or with the new BTT, not about this project.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vas3k/btt-touchbar-presets/issues/36#issuecomment-408515413,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1wOpy00y_1J5H9Vj96EEdhWhHrDsXLks5uK2g5gaJpZM4VfAYf
.

it doesn't work for me too - i just installed BTT and tried to import presets (all of them), but I'm getting the same 'wrong format' error.

Haven't tried again, but importing was working for me on BTT v2.631 last Saturday (9/1).

Confirm: doesn't work with BTT v2.645


be_unprocessable_entity matcher not working with rack 3.1.x

Subject of the issue
Not sure where this fits, but I have an issue in a controller spec that should verify a 422 response.
it 'returns 422' do
  post :create, params: share_params
  expect(response).to be_unprocessable_entity
end

With rack 3.0.11 this works fine and via byebug found out that be_unprocessable_entity comes from rspec-expecations DSL
(byebug) be_unprocessable_entity
#<RSpec::Matchers::DSL::Matcher be_unprocessable_entity>
(byebug) method(:be_unprocessable_entity).source_location
["/Users/bruno.escherl/.asdf/installs/ruby/3.3.3/lib/ruby/gems/3.3.0/gems/rspec-expectations-3.13.1/lib/rspec/matchers/dsl.rb", 75]

Updating to rack 3.1.3 I get this error
Failure/Error: expect(response).to be_unprocessable_entity
       expected #<ActionDispatch::TestResponse:0x000000013573d530 @mon_data=#<Monitor:0x0000000135af03d0>, @mon_data_...equest POST "http://test.host/rest/activities/legacy/users/2322146568/activities.json" for <IP_ADDRESS>>> to respond to `unprocessable_entity?

and checked again and this time get
(byebug) be_unprocessable_entity
#<RSpec::Matchers::BuiltIn::BePredicate:0x00000001317d6130 @method_name=:be_unprocessable_entity, @args=[], @block=nil>
(byebug) method(:be_unprocessable_entity).source_location
nil

So somehow updating rack causes be_unprocessable_entity to be something different?
I can change the expectation to expect(response).to be_unprocessable which still works, but would be curious what is up there?
Your environment

Ruby version: 3.3.3
rspec-expectations version: 3.13.1
rails: <IP_ADDRESS>

Steps to reproduce

Expected behavior

Actual behavior

be_unprocessable_entity comes from rspec-expecations DSL

It’s a generic predicate matcher, and it delegates to the underlying object.
The failure you’re seeing is most certainly due to a change in the rack API. You can read more about this here. In a minor version update you may still see breaking changes like this.

Thanks, seems to have been this change: https://github.com/rack/rack/pull/2137. 422s were renamed from unprocessable_entity to unprocessable_content leading to the observed behavior.

@Aqualon What surprises me is how be_unprocessable_entity used to work. I can only see just the unprocessable? defined, and this hasn’t changed for a decade.
I was about to complain in that Rack PR that a predicate method has been removed/renamed, but I don’t see a clear trace where this happened.
Would you like to dig a bit deeper into this?
I don’t think that the Rack guys intended to break specs i a minor version except for printing a warning.

Maybe some metaprogramming in Rails that builds on too of Rack?

This is not the first time this happens, see Rails 4.2 notes. Was rack pinned in Rails back then?

I figured it out, the be_unprocessable_entity matcher was defined in our own codebase using
Rack::Utils::SYMBOL_TO_STATUS_CODE.each_pair do |symbol, status_code|
  RSpec::Matchers.define :"be_#{symbol}" do
    match do |actual|
      actual.present? && actual.code.to_s == status_code.to_s
    end
    failure_message do |actual|
      "expected response code to be #{status_code}, but was #{actual.code}"
    end
  end
end

and since Rack::Utils::SYMBOL_TO_STATUS_CODE now contains unprocessable_content: 422 instead of unprocessable_entity: 422, we don't get the matcher we used anymore.


Admin Tasks Error

Just uploaded the newest version and discovered this.

Hi @LisaJo48,
Thanks for reaching out to us. Can you please share a screenshot of Site contents page from the SharePoint site.
Thanks,
Sai.

Thanks @LisaJo48.
The site contents looks good. Can you please share a screenshot of the Config List.
Thanks.

Thanks for the screenshot. Can you please confirm if you are still seeing the error with Admin Tasks.
If you still see the issue please share a screenshot of Members List.
Thanks.

It is no longer there. May I ask a related question, now that the Admin Tasks is working? I read that we are able to change the labels for Region, Country, etc. but, now that I see it in the Admin Tasks, it appears as if we can only Show or Hide them. I don't want to hide them; I want to change them to titles that are more applicable to our company. Can I do that?

Hi @LisaJo48,
Yes, you can modify the display names of those fields in Member List. Please check this section in the wiki customize-member-list and let me know if you need more information.
Thanks.

Ah! I'm not a developer by trade. So, I can't simply change the name of the column in the Member List and have the display name in the UI change accordingly?

Ah! Thank you. I somehow overlooked that as I was reviewing the updates. Last question: Is it possible to reorder these fields in the UI? For example, I'd like to have Country be either the first column of the four or the last column.

Hi @LisaJo48,
I am afraid it's not possible to reorder the fields. You can either change display names or hide them.
Thanks.

Thanks for letting me know.


Implement RawPOSIX command line tool set

Description
RawPOSIX should have identical behaviors with native linux in syscall level, which make things like delete non-empty dir inside rmdir() shouldn’t be handled in RawPOSIX  because native linux also doesn’t support. But we need to provide a way that users can mange RawPOSIX file system without accessing the file system root.
Potential Solution
I think we can implement sth like a command line tool set to allow users manage rawposix-fs through command line, and that would be pretty straightforward because we only need shell scripts to add RAWPOSIX_ROOT to user command (ie: cp/rm etc)

That would be great for @Utkarsh272 to work on


Show a proper error message for "Error on first run"

https://github.com/ndbroadbent/icloud_photos_downloader#error-on-first-run
Instead of Bad Request (400), I want to show a better error message that tells the user to wait for 10 minutes before trying again. Only show this error message during the initial authentication and photo request (Not if we get a 400 error after downloading a few photos.)
Related: #83 (record/reply this HTTP request in a test)

Maybe later


VM02 Live Trading Run Report

The screen with layers refreshed, after the weekend:

Jason seems to be running, but Olivia seems to have stopped.
Olivia market seems to show a similar error as in VM01, this time at 2019-09-29T01:46:14.081Z:
Olivia-market.zip
Olivia daily stopped at 2019-09-29T07:26:03.222Z, no errors:
Olivia-daily-Loop.00002467.0000.txt
No errors were found on the rest of the processes...

Fix submitted for testing


Control notification settings from inside app

Hi, I was wondering if it is at all possible to control the notification settings from my app itself instead of calling openNotificationSettings and redirecting them to the settings app? I looked through the docs but I wasn't quite sure how that would work.
For example the user turns off event notifications, would i just delete the channel and just recreate it when they turn it back on?Also, I would probably be using timestamp triggers for events and users would be able to customize if they wanna enable only some timestamp triggers and not others so how would enabling and disabling that work?

Hi there! I am not aware of any system APIs to do this in android or ios. I just looked again and I may have missed something - happy to be wrong - but I just don't see any.
The whole point of the settings being in system settings is so that users have control and the app doesn't have control. Stops apps from being notification-abusive which is a serious problem.
The API is supposed to open it to the notification settings specific for your app at least, which should meet user expectations
In javascript it appears android has special handling and ios simply resolves without doing anything
https://github.com/invertase/notifee/blob/905f3c72381c29d5901462d50861e0d1aaa33a98/packages/react-native/src/NotifeeApiModule.ts#L505-L515
android
https://github.com/invertase/notifee/blob/905f3c72381c29d5901462d50861e0d1aaa33a98/packages/react-native/android/src/main/java/io/invertase/notifee/NotifeeApiModule.java#L234-L240
goes to
https://github.com/invertase/notifee/blob/905f3c72381c29d5901462d50861e0d1aaa33a98/android/src/main/java/app/notifee/core/Notifee.java#L436-L446
and should do what's expected depending on android version
It is possible that maybe on iOS this could be done instead: https://stackoverflow.com/a/61097213/9910298 - not sure why we are not doing that already there may be a good reason

@mikehardy How do other apps handle the in-app notification settings? Do you mean the underlying native APIs don't support it or specifically Notifee's API?

It's not terrible but personally whenever I get redirected out of the app to change the settings I find it kind of jarring haha. If it's not possible though it's not a big deal haha

Someone in a React Native discord just explained to me that those settings are probably controlled server side and it makes sense to me haha. Thanks for all the help and hope you have a nice weekend @mikehardy !


Does this support device control through cloud

As far as I can tell this library only supports device control on the local network and does not support passthrough control using the app server. Firstly is this correct or am I missing someone. Secondly if I was to add this and provide a PR would you be interested in adding this support?
My particular application does not allow for local control and so I require the passthrough. As far as I can see this is the closest library on GitHub in C# to support this capability it just does not provide the methods to talk to the app server.

The way this library works is by connecting to the cloud to get the mac address of the device and then ARP'ing that for the IP address on the local network. All requests are sent directly to the device from the application.
With that being said, if there is server control available through Tapo, which I would not be surprised as my phone allows me to change the lights state when I am not home, then it would need to be implemented. The starting point would be:

Find another library that implements this.
Find the Tapo API documentation.
Monitor the traffic from your phone app to the server when not on the same network.

I would not mind assisting with this if you have questions, but I don't need this functionality.

My understanding is that you can use the API server URL and send it the same messages you would send locally but wrap it in a passthrough packet. I am taking a look, if I get something working I will put up a PR. It will fit nicely into your library as its just another device protocol type.

The "secure passthrough" is part of the communication protocol that happens when sending to local devices. All messages are encrypted with public / private key and sent through the securePassthrough method. Just looking at the request body, it does not have the mac / IP or ID of the light, so, sending it to the AWS Tapo server it would not know what device to change. To login to the cloud use
POST https://eu-wap.tplinkcloud.com/
{     "method": "login",     "params": {         "appType": "Tapo_Android",         "cloudUserName": "<username>",         "cloudPassword": "<Password>",         "terminalUUID": "e01bf1ce-a068-4fbe-8e5d-8957d73e696f"     } }
Then take the token from result.token and use it to list devices with:
POST https://eu-wap.tplinkcloud.com/?token=<result.token>
{     "method": "getDeviceList" }
These are the only cloud methods I know but if you want to try sending it a secure passthrough you can.


[stable/ghost] Liveness probe with https protocol fails with reverse proxy redirecting to https

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST (I think)

Version of Helm and Kubernetes:
Helm:
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.0", GitCommit:"d325d2a9c179b33af1a024cdb5a4472b6288016a", GitTreeState:"clean"}

Kubernetes:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"archive", BuildDate:"2019-02-15T08:21:09Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Which chart: stable/ghost
What happened:
Running ghost behind reverse proxy that forces https redirect causes liveness probe to faile because of redirect loop.
What you expected to happen: Running release
How to reproduce it (as minimally and precisely as possible):
Setup minikube with ingress enabled and CoreDNS config edited to include hosts plugin mapping host.local to host ip
ghostHost: host.local
ghostProtocol: https
persistence:
  enabled: false
service:
  port: 443
ingress:
  enabled: true
  annotations:
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
  hosts:
  - name: host.local
    tls: true

Anything else we need to know:
A small workaround I used was to add:
{{- if eq .Values.ghostProtocol "https" }}
- name: X-Forwarded-Proto
  value: https
{{- end }}

to liveness and readiness probes httpHeaders in deployment.yaml
So this is either a feature request to support reverse proxies that redirect all traffic to https or if that is inteded use case, it is a bug report.

Hi,
Thanks for reporting. After performing several checks, I think that the solution you proposed is the way to make Ghost readiness probe work with HTTPS. I tried setting the scheme but that wouldn't work, as Ghost is serving using HTTP after all.


Adding Pufferfish Template

I made a Template for the Server Software Pufferfish. Maybe you want to add it in a further Version!
{
  "name": "minecraft-pufferfish",
  "display": "Pufferfish - Minecraft",
  "type": "minecraft-java",
  "install": [
    {
      "files": [
        "https://ci.pufferfish.host/job/Pufferfish-1.18/lastSuccessfulBuild/artifact/build/libs/pufferfish-paperclip-1.18.2-R0.1-SNAPSHOT-reobf.jar"
      ],
      "type": "download"
    },
    {
      "source": "pufferfish-*.jar",
      "target": "server.jar",
      "type": "move"
    },
    {
      "target": "server.properties",
      "text": "server-ip=${ip}\nserver-port=${port}\nmotd=${motd}",
      "type": "writefile"
    },
    {
      "target": "eula.txt",
      "text": "eula=${eula}",
      "type": "writefile"
    }
  ],
  "run": {
    "stop": "stop",
    "command": "${java} -Xmx${memory}M -Dlog4j2.formatMsgNoLookups=true -jar server.jar nogui",
    "workingDirectory": "",
    "pre": [],
    "post": [],
    "environmentVars": {}
  },
  "data": {
    "eula": {
      "type": "boolean",
      "desc": "Do you (or the server owner) agree to the Minecraft EULA?",
      "display": "EULA Agreement (true/false)",
      "required": true,
      "value": "false",
      "userEdit": true
    },
    "ip": {
      "type": "string",
      "desc": "What IP to bind the server to",
      "display": "IP",
      "required": true,
      "value": "<IP_ADDRESS>",
      "userEdit": true
    },
    "java": {
      "type": "string",
      "desc": "\"java\" for system standard, else direct path to java",
      "display": "path to java executable",
      "required": true,
      "value": "java",
      "userEdit": true
    },
    "memory": {
      "type": "integer",
      "desc": "How much memory in MB to allocate to the Java Heap",
      "display": "Memory (MB)",
      "required": true,
      "value": "1024"
    },
    "motd": {
      "type": "string",
      "desc": "This is the message that is displayed in the server list of the client, below the name. The MOTD does support color and formatting codes.",
      "display": "MOTD message of the day",
      "required": true,
      "value": "A Minecraft Pufferfish Server\\n\\u00A79 hosted on PufferPanel",
      "userEdit": true
    },
    "port": {
      "type": "integer",
      "desc": "What port to bind the server to",
      "display": "Port",
      "required": true,
      "value": "25565",
      "userEdit": true
    }
  },
  "supportedEnvironments": [
    {
      "type": "standard"
    }
  ]
}

Just a hint: You can create a pr to get it merged, then it will be automatically available on every pufferpanel, after merge, but you should maybe add an option to use other versions, like 1.17, beside the 1.18 version


Add routes to the net-iso bridge

Add route so that the nat64 router knows where to forward fd00:aaaa::/64 traffic.
Add route on the host to ensure nat64 IPv6 prefix is routed to the nat64 router.
Use forwarding mode "open" when using IPv6 - this turns off all the Libvirt firewalling that otherwise get's in the way.
Alos remove some of the options, we use env vars to drive it.

recheck

/approve

recheck

recheck

recheck

recheck

recheck

/lgtm


[BUG] Cannot disable Stat Overlay

Describe the bug
There appears to be no way to NOT have the stat overlay appear on tokens. There is no way to remove all the attributes. I can add a new one, leave it blank, and remove the existing two, but upon a reload, that will be reverted.
It doesn't seem to be possible not to have a stat overlay at all
Expected behavior
Allow me to remove all stat overlay attributes and not see any.
Desktop (please complete the following information):

OS: Windows 11
Browser: Latest Edge
FVTT Version 12.331
Module version 2.22.2

This doesn't work?


[5.7] New: Update incremental build hash to encode option arguments a…

Cherry-pick of https://github.com/apple/swift-driver/pull/1128 to release branch
Explanation: Before this change, changing the argument to an option which affects incremental builds, or the relative ordering of multiple options affecting incremental builds won't correctly rebuild all of the sources. Update the argsHash computation to take order and arguments into account.
Scope: Affects incremental builds after driver CLI arguments are changed manually or by a build system.
Risk: Low
Reviewers: @artemcm
Testing: Added unit test coverage to the incremental builds suite
Issue: rdar://96556787

@swift-ci please test

Thanks @nkcsgexi !


remove unnecessary mypy excludes

Codecov Report
Patch and project coverage have no change.

Comparison is base (d1d1602) 92.43% compared to head (a9358bf) 92.43%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #245   +/-   ##
=======================================
  Coverage   92.43%   92.43%
=======================================
  Files          23       23
  Lines         952      952
  Branches      222      222
=======================================
  Hits          880      880
  Misses         69       69
  Partials        3        3

Impacted Files
Coverage Δ

src/pymovements/utils/downloads.py
25.00% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


implement exclude-dir cli flag

This implements https://github.com/gruntwork-io/terragrunt/issues/355 by adding a -terragrunt-exclude-dir CLI flag.
It supports unix-style globs and will exclude all modules within or under the specified directories during execution.
Let me know if additional things need to be adjusted.

Thanks for your very valuable feedback. This is my first bigger MR using golang, so there is definitely a lot to learn. I'll go over it and let you know once I'm done.

I tried adding some integration tests, but they are not working yet as expected. Will take another look at it tomorrow.

Sounds good. Let me know if you need any help sorting it out. And thank you for the work you're putting into this PR!

Did some refactoring (see discussions) and added integration tests. Would be awesome if you can take another look!

Thanks! I'm a bit bogged down today, but I'll take a look tomorrow.

I just pushed another update, found an error while running tests.
Now I am stuck at an error with test: TestToRunningModulesTwoModulesWithDependenciesReverseOrder()
Is this test case correct?
runningModuleB has no dependencies, while moduleB has a dependency.
Is this correct, or should the dependencies of runningModuleB match for the test case?
moduleB := &TerraformModule{
		Path:              "b",
		Dependencies:      []*TerraformModule{moduleA},
		Config:            config.TerragruntConfig{},
		TerragruntOptions: mockOptions,
	}

	runningModuleB := &runningModule{
		Module:         moduleB,
		Status:         Waiting,
		Err:            nil,
		Dependencies:   map[string]*runningModule{},
		NotifyWhenDone: []*runningModule{runningModuleA},
	}

Thanks for giving a little bit more insight here, totally makes sense. With this information I found the issue and fixed it (see latest commit). I also successfully ran all tests now, including the ones requiring AWS credentials:
FAIL    github.com/msvechla/terragrunt/cli      9.053s
ok      github.com/msvechla/terragrunt/config   0.031s
ok      github.com/msvechla/terragrunt/configstack      0.027s
ok      github.com/msvechla/terragrunt/dynamodb 33.841s
?       github.com/msvechla/terragrunt/errors   [no test files]
?       github.com/msvechla/terragrunt/options  [no test files]
ok      github.com/msvechla/terragrunt/remote   0.025s
ok      github.com/msvechla/terragrunt/shell    6.551s
ok      github.com/msvechla/terragrunt/test     428.479s
?       github.com/msvechla/terragrunt/test/helpers     [no test files]
ok      github.com/msvechla/terragrunt/util     0.033s

The only issue I get is with TestCheckTerraformVersionMeetsConstraintGreaterDev:
--- FAIL: TestCheckTerraformVersionMeetsConstraintGreaterDev (0.00s)
    version_check_test.go:78:
                Error Trace:    version_check_test.go:78
                                                        version_check_test.go:17
                Error:          Expected nil, but got: &errors.Error{Err:cli.InvalidTerraformVersion{CurrentVersion:(*version.Version)(0xc00042a460), VersionConstraints:version.Constraints{(*version.Constraint)(0xc0003f0da0)}}, stack:[]uintptr{0x159f7b9, 0x15a71cd, 0x15a6bc8, 0x10f8f9f, 0x105dc11}, frames:[]errors.StackFrame(nil), prefix:""}
                Test:           TestCheckTerraformVersionMeetsConstraintGreaterDev
                Messages:       Expected Terraform version v0.9.4-dev to meet constraint >= v0.9.3, but got error: The currently installed version of Terraform (0.9.4-dev) is not compatible with the version Terragrunt requires (>= v0.9.3).

Does this mean I have to bump the terragrunt version as-well? Could you guide me on how to resolve this? Thanks again for your help.

Expected Terraform version v0.9.4-dev to meet constraint >= v0.9.3, but got error: The currently installed version of Terraform (0.9.4-dev) is not compatible with the version Terragrunt requires (>= v0.9.3).

Do you have a custom (i.e., locally-built) version of Terraform installed (0.9.4-dev)? If so, it looks like the version check we do doesn't take -dev into account. If you try it with an official release of Terraform in your PATH, it should work.

Actually this has nothing to do with the installed version. This test is simply checking hardcoded versions.
This is the entire test:
func TestCheckTerraformVersionMeetsConstraintGreaterDev(t *testing.T) {
	t.Parallel()
	testCheckTerraformVersionMeetsConstraint(t, "v0.9.4-dev", ">= v0.9.3", true)
}

Drilling a little bit down the function it actually mostly calls the https://github.com/hashicorp/go-version module. So it seems like an external module is tested here. Does this test work for you on master? Maybe something changed on the module end which breaks the check.

So it seems like an external module is tested here. Does this test work for you on master?

Yes, the tests passed on master just 14 hours ago. Is it possible you have a different version of go-version installed and something changed upstream?

Sorry for the confusion, I cleaned-up my local environment and ran dep ensure. Now all tests finished successfully.
(⎈ |:) ~/go/src/github.com/gruntwork-io/terragrunt   pr/563  go test -short ./...
?       github.com/gruntwork-io/terragrunt      [no test files]
?       github.com/gruntwork-io/terragrunt/aws_helper   [no test files]
ok      github.com/gruntwork-io/terragrunt/cli  10.085s
ok      github.com/gruntwork-io/terragrunt/config       0.022s
ok      github.com/gruntwork-io/terragrunt/configstack  0.026s
ok      github.com/gruntwork-io/terragrunt/dynamodb     43.642s
?       github.com/gruntwork-io/terragrunt/errors       [no test files]
?       github.com/gruntwork-io/terragrunt/options      [no test files]
ok      github.com/gruntwork-io/terragrunt/remote       0.019s
ok      github.com/gruntwork-io/terragrunt/shell        6.541s
ok      github.com/gruntwork-io/terragrunt/test 587.301s
?       github.com/gruntwork-io/terragrunt/test/helpers [no test files]
ok      github.com/gruntwork-io/terragrunt/util 0.032s

https://github.com/gruntwork-io/terragrunt/releases/tag/v0.16.11

Thanks so much for your help on this, it was an awesome experience 👍


Added two planning engines: "symk" and "symk-opt"

As part of the 1st sprint of the "Symbolic Search for Diverse Plans and Maximum Utility" project, we added two search engines to the UP that can be installed using the up-symk repo. Both engines can generate a single or multiple/all plans using the OneshotPlanner and AnytimePlanner interfaces. The two differ in that "symk-opt" has an optimality guarantee for both settings, generating a single or multiple/all optimal plans.
You can find a usage example here.
Let me know if you want any changes.
Best
David

@alvalentini Thanks, I added symk to the setup.py file.


SHA2 certificate signing support

OpenSSH 8.2 release has deprecated ssh-rsa  (https://www.openssh.com/txt/release-8.2) .  This PR is cherry picked from https://github.com/albertniderhofer/bless/commit/084cb1f84ad8e6900c53e2c54e367da0dfd81669 which supports SHA2 certificate signing.  We've made a minor bug correction to the original cherry picked commit where the public key should not have been changed.

I can't approve my own PR, but commenting +1 also as @meng-han and myself worked on this together.


Refused to execute JavaScript URL

Tell us where you are using Dejavu (Hosted web app, Chrome extension, Docker Image, Within appbase.io)
Chrome extension
What is the version of Dejavu that you are using?
1.6.1
Describe the issue that you are seeing, or the feature request :-), include any screenshots as necessary.
When trying to perform a query, it shows Refused to execute JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem: chrome-extension-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution.
Only default view is working
If your issue deals with accessing Elasticsearch cluster, share the necessary steps to replicate the behavior (the configuration.yml settings, where your ES cluster is hosted, any relevant logs).
If your issue deals with a UI issue, share with us a screenshot of the failing network request or the browser console log showing the error.

Dear @siddharthlatest,
I try just to update a doc using the interface but is not working, here is the error:
index.html#?input_state=XQAAAAJtBAAAAAAAAAA9iIqnY-B2BnTZGEQzY8iwkHG0t_gDNgV…40q9U3DyyHs0XAZQAC5BLQfT2veiDBFnGDfaWM0aHhgjGXsGzt___2qQkA&editable=true:1 Uncaught (in promise) SyntaxError: Unexpected token N in JSON at position 0
    at parse (<anonymous>)

Also it showed this error:
Refused to execute JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem: chrome-extension-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution.
Thanks and best regards,

@mohammedESSABRI Afaict, we don't use inline script blocks but still going to confirm this. Could it be possible that some other extension you have is trying to inject a script tag? One way to know for sure is for you to enable Dejavu to work in Incognito mode and try it there (see below screenshot, you can do this from your chrome://extensions page, click on Details button on the Dejavu extension)
I suspect that might be the case as I don't see this error (or haven't heard about it from any other user till now).

Closing this due to inactivity - also, dejavu (as chrome extension) can run in incognito mode starting 2.0.0.


Fix "int" not being allowed as parameter to itemGetter

Array keys can also be integers. This seems to be allowed by args\expects(args\arrayKey, $key);, but the docblock does not properly communicate it. This causes tools such as PHPStan to complain about it.

Thanks, merged!


Enable basic slides (reveal.js) settings. Allow display of slide_number and disable the vertical centering of slides

Purpose
For the slides based on reveal.js. Enable configuration to allow display of slide_number and disable the vertical centering of slides.

Thanks, I can see how having more slide options could be useful 👍
Now that you are proposing to increase the number of options for slides, it might be a good idea to place all slide specific options under their own front matter config section, such as slide:/slide_config:/slide_format:, to prevent possible namespace conflicts in the future and keep everything organised. Any thoughts?

Closing due to conflicts and lack of response. Happy to re-open if someone can upgrade to the latest Reveal JS and propose a solution to add slide design options as in my previous message.


Removed an invalid regexp escape "\a"

The bell character (\a) causes this test to fail when run against Windows artifactory servers.

The bell character (\a) causes this test to fail when run against Windows artifactory servers.

Thanks @steveonjava !


Add whether we're running in codespaces in startup telemetry

Closing as every telemetry event already has Properties["common.uikind"] and that value is "web" when the extension is running in Codespaces.

Closing as every telemetry event already has Properties["common.uikind"] and that value is "web" when the extension is running in Codespaces.