add ogl test formula (not a real formula)

this is intended to create an MVCE to investigate cegui build
failure in yosemite test environment
(see https://github.com/Homebrew/homebrew/pull/49724)
DO NOT MERGE

Closing this out since it was just a test PR, and I assume it's served its purpose.


Claiming namespace lnbits/Nostr

Package information

Package link: https://registry.platformio.org/libraries/lnbits/Nostr

Description
I am the lead developer and maintainer of this package.

Please create a PlatformIO Account and we will assign you as the owner of the lnbits organization. Thanks.

Done! Please check pio org list.


Dependabot downgrades npm dependency in unrelated upgrade PR

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
npm
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
https://github.com/maxmind/GeoIP2-node/pull/900/files#diff-053150b640a7ce75eff69d1a22cae7f0f94ad64ce9a855db544dda0929316519
dependabot.yml content
version: 2
updates:

package-ecosystem: npm
directory: "/"
schedule:
interval: daily
open-pull-requests-limit: 20
package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: daily

Updated dependency
@types/node from 20.2.5 to 20.3.1
What you expected to see, versus what you actually saw
Expected only @types/node to be upgraded in package-lock.json.
Instead, typescript was also downgraded from 5.1.3 to 5.0.4.
Interestingly, dependabot had just upgraded typescript from 5.0.4 to 5.1.3 9 days ago in this PR
Native package manager behavior
package-lock.json diff:
diff --git a/package-lock.json b/package-lock.json
index b4c5949..ce44d0b 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -17,7 +17,7 @@
         "@types/ip6addr": "^0.2.3",
         "@types/jest": "^29.2.0",
<EMAIL_ADDRESS>"^4.3.4",
-        "@types/node": "^20.0.0",
+        "@types/node": "^20.3.1",
         "@typescript-eslint/eslint-plugin": "^5.6.0",
         "@typescript-eslint/parser": "^5.6.0",
         "eslint": "^8.4.1",
@@ -1282,9 +1282,9 @@
       }
     },
     "node_modules/@types/node": {
-      "version": "20.2.5",
-      "resolved"<EMAIL_ADDRESS>-      "integrity": "sha512-JJulVEQXmiY9Px5axXHeYGLSjhkZEnD+MDPDGbCbIAbMslkKwmygtZFy1X6s/075Yo94sf8GuSlFfPzysQrWZQ==",
+      "version": "20.3.1",
+      "resolved"<EMAIL_ADDRESS>+      "integrity": "sha512-EhcH/wvidPy1WeML3TtYFGR83UzjxeWRen9V402T8aUGYsCHOmfoisV3ZSg03gAFIbLq8TnWOJ0f4cALtnSEUg
==",
       "dev": true
     },
     "node_modules/@types/prettier": {
@@ -7041,9 +7041,9 @@
       }
     },
     "@types/node": {
-      "version": "20.2.5",
-      "resolved"<EMAIL_ADDRESS>-      "integrity": "sha512-JJulVEQXmiY9Px5axXHeYGLSjhkZEnD+MDPDGbCbIAbMslkKwmygtZFy1X6s/075Yo94sf8GuSlFfPzysQrWZQ
==",
+      "version": "20.3.1",
+      "resolved"<EMAIL_ADDRESS>+      "integrity": "sha512-EhcH/wvidPy1WeML3TtYFGR83UzjxeWRen9V402T8aUGYsCHOmfoisV3ZSg03gAFIbLq8TnWOJ0f4cALtnSEUg
==",
       "dev": true
     },
     "@types/prettier": {

Images of the diff or a link to the PR, issue, or logs
PR: https://github.com/maxmind/GeoIP2-node/pull/900
Smallest manifest that reproduces the issue
No response

A @dependabot rebase after merging some other PRs seems to have fixed the issue, so the above repro links won't show the issue anymore.


CheckTester needs thinking through

See #3453 and #3464 for context. The situation is that we want to use CheckTester to run checks in a controlled and ergonomic way, but the arguments that we want to pass to CheckTester really depend on context and we want it to "work out" what it should do with the values we pass it:

Sometimes we want to pass the same arguments as the underlying test function.
Sometimes we want to pass a file name (README.md, or a font file name) and have that passed to the appropriate condition.
Sometimes we want to pass a file name (METADATA.pb) and have that synthesise additional conditions (font, fonts).
Often we want to pass a ttFont object and have it derive the remaining conditions.

Here's a good example from adobefonts_test.py:
https://github.com/googlefonts/fontbakery/blob/51389841fe5552b60b956b8c79a0f9eb7cd7bfb9/tests/profiles/adobefonts_test.py#L21-L30
On the first call we pass the filenames; on the second call we pass a list of ttFont objects.
That's a lot of magic. Good magic, perhaps, but it makes the implementation of CheckTester very fragile. And every time we support a new kind of file (say, README.md) we have to change the CheckTester class to route this file to the appropriate condition. CheckTester needs to have a lot of domain-specific knowledge - knowing what every object is and what to do with it. I think this is bad.
I am starting to think that the best way forward is to have CheckTester only handle filenames, just like the fontbakery command line. If you want to make a "bad" test file on the fly, just write it to a temp file. We should have a helper function for that. This would change e.g.:
https://github.com/googlefonts/fontbakery/blob/51389841fe5552b60b956b8c79a0f9eb7cd7bfb9/tests/profiles/dsig_test.py#L17-L25
to:
    font = TEST_FILE("cabin/Cabin-Regular.ttf")
    assert_results_contain(check(font),
                           WARN, 'found-DSIG',
                           'with a font containing a DSIG table...')

    # Then we remove the DSIG table and it should now PASS the check:
	ttFont = TTFont(font)
    del ttFont['DSIG']
    assert_PASS(check(write_temp_font(ttFont)),
                'with a good font...')

or even:
    font, ttFont = TEST_FILE("cabin/Cabin-Regular.ttf")
    assert_results_contain(check(font),
                           WARN, 'found-DSIG',
                           'with a font containing a DSIG table...')

    # Then we remove the DSIG table and it should now PASS the check:
    del ttFont['DSIG']
    assert_PASS(check(write_temp_font(ttFont)),
                'with a good font...')

Hardly any difference in code length and readability, but it means there doesn't need to be any magic at all in the CheckTester class.
@felipesanches, what do you think?

I think that this proposal is worse than the current state as it would unnecessarily save font files to disk.
But I agree that the current approach is still not good. The ideas below are still fresh, I have not thought much about it, so we'll have to think more carefully, but here's what I think could be done:
I've been thinking that perhaps one way to refactor this would be to annotate the assets that we pass to CheckTester. So, the TEST_FILE function would return an object with 2 fields: a type identifier and the actual data, which in this case would be a simple file path. We could have the same thing for any other kind of object. The "type identifier" should use the same naming of the conditions, so it would help in the process of dependency computation and/or injection. So, even though both README.md and a font file path and METADATA.pb and DESCRIPTION.en_us.html are all simple python strings containing a file path, they can be distinguished by this labelling mechanism, so there would be no guessing needed at all.

What’s wrong with saving font files to disk? Testing FontBakery is not a performance-critical operation. :-)
And you did want an API that mirrored the command line usage…

Well... the dict that we pass for overriding conditions is almost this. But it does not apply to the first argument we pass fo CheckTester. Maybe we could use the dict for everything, even for a simple font path or TTFont object. But then I dislike the idea of code-tests looking like this:  assert_results_contain(check(ttFont=ttFont), ...

And you did want an API that mirrored the command line usage…

My goal is to have an API that imitates command line usage, yes. But that does not mean I want to save files unnecessarily. Or that I would want to restrict code-tests to work exclusively with file paths. On the contrary, I think the imitation is good enough if kept at the semantic level:
A user would pass a file path on the command line, but our test suite can work with a fontTools TTFont object which is more versatile while still semantically equivalent to that hypothetical user file in order to describe the test-case scenarios.

Another idea I had is for the CheckTester class to offer a few methods. One is for following the underlying function arguments, one is for purely filenames, one is for handling condition overrides etc. That way if you want cleverness you have to “pay” for it.

how would that look like?

This is now done!


fix(nodejs): address import issues in lancedb npm module

Fixes #1496

Tests pass and this matches my knowledge to the extent I understand anything. I assume whatever integration test you are testing with is also working?

Indeed. Just re-ran it with these changes. I can install a local version of this.
Details

Create a local version
npm run build:release
npm run build-release
npm pack

Then you can use that package elsewhere. It runs successfully with type checking. However, I haven't figured out how to pack the native module yet, so it doesn't work at runtime 🤷


refactor(carousel): remove unneeded describe

All controller tests were inside the addSlide describe and that was incorrect.

Works for me


Limit concurrent shards loading to number of cores available

Required for all non-trivial PRs

[ ] Rebased/mergable
[ ] Tests pass

@corylanou Forgot to push this up w/ #6623

It might be uncommon, but this should probably be limited to the minimum of NumCPU and GOMAXPROCS. If someone has multiple cores, but manually sets GOMAXPROCS=1, then we'll have concurrent goroutines that will be fighting for a single active OS thread.

Maybe runtime.GOMAXPROCS(0) then?  Should default to NumCPU unless changed.

For Go 1.5+, yes, just checking the value of GOMAXPROCS should work.

LGTM 👍


Make GHCJS yield back to the browser more frequently, so that the user's typing does not lag

The default SCHED_QUANTUM in GHCJS is 25ms, and the default BUSY_YIELD time is 500ms, so background threads cause the UI to pause for about half a second at a time.  This patch sets both times to 5ms.

Didn't know you could tweak these, thanks!

This is live now; sorry for the delay.

Awesome, man; it looks great!
On Mon, May 18, 2015 at 12:46 PM, Ozan Sener<EMAIL_ADDRESS>wrote:

This is live now; sorry for the delay.
—
Reply to this email directly or view it on GitHub
https://github.com/osener/markup.rocks/pull/6#issuecomment-103123650.


[Report] Move background visualization of anatomical images up above the zoomed-in view of the brain

What would you like to see added in this software?
After many years evaluating T1w and T2w image quality with MRIQC, I often find myself jumping directly to the background visualization before anything else.
I'm now sure that the background should be looked at at the beginning of the assessment to maximize efficiency. Otherwise, you keep jumping back to the zoomed-in mosaic to see if defects are visible within the brain.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response

I like it! I think we should do the same for the functional report, that is move the standard-deviation before the average BOLD.


update from developer preview to early access

Hello,
is it possible to update the developer preview to early access?
I'm switched to the commit/release "v6.0.0+ea1" for both repositories, but the backend still say:
current version: 9999999-dev
Best regards,
DevertNEt

Could you please provide the contents of your composer.json file and the console output from running composer update?

Here is the output from the composer.json and composer update command.
shopware/platform
composer update
Cannot load Zend OPcache - it was already loaded
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files

cat composer.json
{
    "name": "shopware/platform",
    "description": "The Shopware e-commerce core",
    "type": "library",
    "keywords": [
        "framework",
        "shopware"
    ],
    "homepage": "https://www.shopware.com",
    "license": "MIT",
    "replace": {
        "shopware/core": "self.version",
        "shopware/storefront": "self.version",
        "shopware/administration": "self.version",
        "shopware/elasticsearch": "self.version"
    },
    "require": {
        "php": ">=7.2.0",
        "ext-dom": "*",
        "ext-fileinfo": "*",
        "ext-gd": "*",
        "ext-iconv": "*",
        "ext-intl": "*",
        "ext-json": "*",
        "ext-mbstring": "*",
        "ext-openssl": "*",
        "ext-pdo": "*",
        "ext-pdo_mysql": "*",
        "ext-simplexml": "*",
        "ext-xml": "*",
        "ext-zip": "*",
        "aws/aws-sdk-php": "3.100.3",
        "cocur/slugify": "3.2",
        "composer/composer": "1.8.6",
        "composer/semver": "1.5.0",
        "doctrine/annotations": "1.6.1",
        "doctrine/dbal": "2.9.2",
        "doctrine/inflector": "1.3.0",
        "dompdf/dompdf": "0.8.3",
        "elasticsearch/elasticsearch": "7.0.0",
        "enqueue/fs": "0.9.8",
        "erusev/parsedown-extra": "0.7.1",
        "google/cloud-storage": "1.12.2",
        "guzzlehttp/guzzle": "6.3.3",
        "jdorn/sql-formatter": "1.2.17",
        "lcobucci/jwt": "3.3.1",
        "league/flysystem": "1.0.52",
        "league/flysystem-aws-s3-v3": "1.0.23",
        "league/oauth2-server": "7.3.3",
        "marc1706/fast-image-size": "1.1.4",
        "nyholm/psr7": "1.1.0",
        "ongr/elasticsearch-dsl": "6.0.3",
        "psr/cache": "1.0.1",
        "psr/http-factory": "1.0.1",
        "psr/http-message": "1.0.1",
        "psr/log": "1.1.0",
        "scssphp/scssphp": "1.0.0",
        "sensio/framework-extra-bundle": "5.3.1",
        "sroze/messenger-enqueue-transport": "0.3.0",
        "superbalist/flysystem-google-storage": "7.2.1",
        "swiftmailer/swiftmailer": "6.2.1",
        "symfony/asset": "4.3.2",
        "symfony/cache": "4.3.2",
        "symfony/cache-contracts": "1.1.1",
        "symfony/config": "4.3.2",
        "symfony/console": "4.3.2",
        "symfony/debug-bundle": "4.3.2",
        "symfony/dependency-injection": "4.3.2",
        "symfony/dotenv": "4.3.2",
        "symfony/event-dispatcher": "4.3.2",
        "symfony/event-dispatcher-contracts": "1.1.1",
        "symfony/filesystem": "4.3.2",
        "symfony/finder": "4.3.2",
        "symfony/framework-bundle": "4.3.2",
        "symfony/http-foundation": "4.3.2",
        "symfony/http-kernel": "4.3.2",
        "symfony/messenger": "4.3.2",
        "symfony/monolog-bundle": "3.3.1",
        "symfony/options-resolver": "4.3.2",
        "symfony/polyfill-php73": "1.11.0",
        "symfony/property-access": "4.3.2",
        "symfony/property-info": "4.3.2",
        "symfony/psr-http-message-bridge": "1.2.0",
        "symfony/routing": "4.3.2",
        "symfony/serializer": "4.3.2",
        "symfony/service-contracts": "1.1.2",
        "symfony/swiftmailer-bundle": "3.2.7",
        "symfony/translation": "4.3.2",
        "symfony/translation-contracts": "1.1.2",
        "symfony/twig-bundle": "4.3.2",
        "symfony/validator": "4.3.2",
        "symfony/yaml": "4.3.2",
        "twig/extensions": "1.5.4",
        "twig/twig": "2.11.2",
        "voku/stop-words": "2.0.1"
    },
    "require-dev": {
        "ext-tokenizer": "*",
        "ext-xmlwriter": "*",
        "bheller/images-generator": "1.0.1",
        "fzaninotto/faker": "1.8.0",
        "johnkary/phpunit-speedtrap": "3.1.0",
        "kubawerlos/php-cs-fixer-custom-fixers": "1.13.0",
        "league/flysystem-memory": "1.0.2",
        "mbezhanov/faker-provider-collection": "1.2.1",
        "phpunit/phpunit": "8.2.1",
        "smalot/pdfparser": "0.14.0",
        "symfony/browser-kit": "4.3.2",
        "symfony/phpunit-bridge": "4.3.2",
        "symfony/stopwatch": "4.3.2",
        "symfony/var-dumper": "4.3.2",
        "symfony/web-profiler-bundle": "4.3.2"
    },
    "conflict": {
        "symfony/symfony": "*"
    },
    "autoload": {
        "psr-4": {
            "Shopware\\Administration\\": "src/Administration/",
            "Shopware\\Docs\\": "src/Docs/",
            "Shopware\\Storefront\\": "src/Storefront/",
            "Shopware\\Core\\": "src/Core/",
            "Shopware\\Elasticsearch\\": "src/Elasticsearch/"
        },
        "exclude-from-classmap": [
            "src/**/Test/"
        ]
    }
}

shopware/development
composer update
Cannot load Zend OPcache - it was already loaded
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating optimized autoload files
ocramius/package-versions:  Generating version class...
ocramius/package-versions: ...done generating version class
> ln -sf ../../bin/pre-commit vendor/shopware/platform/.git/hooks/pre-commit

cat composer.json
{
    "name": "shopware/development",
    "type": "project",
    "license": "MIT",
    "repositories": [
        {
            "type": "path",
            "url": "custom/plugins/*",
            "options": {
                "symlink": true
            }
        },
        {
            "type": "path",
            "url": "platform",
            "options": {
                "symlink": true
            }
        }
    ],
    "config": {
        "optimize-autoloader": true
    },
    "prefer-stable": true,
    "minimum-stability": "dev",
    "autoload": {
        "psr-4": {
            "Shopware\\Development\\": "src/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Shopware\\Development\\Test\\": "tests/"
        }
    },
    "require": {
        "php": "~7.2",
        "ocramius/package-versions": "1.4.0",
        "shopware/platform": "dev-master"
    },
    "scripts": {
        "post-update-cmd": [
            "ln -sf ../../bin/pre-commit vendor/shopware/platform/.git/hooks/pre-commit"
        ]
    },
    "require-dev": {
        "ext-tokenizer": "*",
        "ext-xmlwriter": "*",
        "bheller/images-generator": "1.0.1",
        "fzaninotto/faker": "1.8.0",
        "johnkary/phpunit-speedtrap": "3.1.0",
        "kubawerlos/php-cs-fixer-custom-fixers": "1.13.0",
        "league/flysystem-memory": "1.0.2",
        "mbezhanov/faker-provider-collection": "1.2.1",
        "phpunit/phpunit": "8.2.1",
        "smalot/pdfparser": "0.14.0",
        "symfony/browser-kit": "4.3.2",
        "symfony/phpunit-bridge": "4.3.2",
        "symfony/stopwatch": "4.3.2",
        "symfony/var-dumper": "4.3.2",
        "symfony/web-profiler-bundle": "4.3.2"
    }
}

Thank you! I see your problem in the composer.json file in the development template. The requirement there is set to "shopware/platform": "dev-master" which checks out the latest changes, a nightly status so to say. Please change this line to "shopware/platform": "6.0.0+ea1" and run composer update again. After that, it should have the code from the release and the administration should say the same. :-)

Now the backend shows the correct version :) Thank you!
Maybe you should set the default branch from the shopware/development repo to "6.0+ea".
Because in the installation doc is no hint to use a special release/branch:
https://docs.shopware.com/en/shopware-platform-en/getting-started/installation?category=shopware-platform-en/getting-started
It only says "git clone git@github.com:shopware/development.git".

hey @DevertNet
I've updated the docs according to your suggest. Thanks for the hint :+1:


Support for NLLB

Hello,
Do you plan to support NLLB model ?
Thanks !

Thanks for your reply.
Cool, it was merged today from their side actually, see here. That's why I asked, I should have put the link in the previous comment.

Hi there,
Is there any news regarding a timeline of the NLLB integration?
Thanks!

Also interested in NLLB integration with NMT

+1, would be interesting to try it out via EasyNMT


Bash completion should fall back to defaults after --

When using cargo run bin=something --, the cargo bash completion script still tries to complete cargo commands, and does not use normal file completion. Instead it should restore normal bash completion behaviour after the --, so you can complete file names as arguments to the something program.

the -- can refer to rustc options too

Even for cargo rustc, only cargo's options are available for tab completion after the --. I've re-enabled cargo's bash-completion temporarily, and confirmed that this issue still exists.

It would be even better if the bash completion could do normal file completion for non-option arguments in these cases (like simple cargo run <my-config-file>).


Partners listings table not showing correct verified value

The partners listings table is not showing the correct verified value. The value appears to be correct on the listing obj because it is showing appropriately on the public site and the listing form, just not in the partners table.

QA Notes: Edit a listing to be verified and ensure the value shows correctly in the partners listing table.

LGTM


optimize BinExport read_bytes performance

It appears that we're creating a new PE/ELFFILE object per function, when we should be creating these once per analysis. Commenting out extract_insn_bytes_features (the caller) resulted in a significant performance improvement. @mr-tz this is a good place to start investigating for a performance bump, starting by seeing if we can store the PE/ELFFile object once in the AnalysisContext.

please read thread started by @mike-hunhoff in https://github.com/mandiant/capa/pull/1950#discussion_r1571363044_

I've confirmed the performance is worse with byte extraction enabled:

around 40 functions/s without bytes
around 4 functions/s with bytes

According to IDA, 0x420A81is the largest function in mimikatz. Using the following to triage performance:
$ python scripts/show-features.py --format binexport2 --backend binexport2 tests/data/mimikatz.exe_.ghidra.BinExport --function 0x420A81

complete profile from py-spy:

I interpret the results above as: ~70% of runtime is spent evaluating rule matches, with around 9% of runtime spent on extracting instruction features.

binexport backend:
Executed in   89.98 secs    fish           external
   usr time   89.71 secs  522.00 micros   89.71 secs
   sys time    0.38 secs  370.00 micros    0.38 secs

vivisect backend:
________________________________________________________
Executed in  134.74 secs    fish           external
   usr time  133.54 secs  512.00 micros  133.54 secs
   sys time    1.02 secs  368.00 micros    1.02 secs


Update harbor-helm to 1.10.0

Signed-off-by: Joshua Mühlfort<EMAIL_ADDRESS>

Rudimentary CI integration tests work so far. I'd suggest merging this PR and closing the older PR's #18 and #19.


[web] All inserted widgets in editor (e.g. image) has been rebuilding constantly

Hello,
I would like to ask about whether it is a editor nature (and its internal limitation) or could be improved.
When I am entering new line by clicking enter (or pasting new image or other action) the inserted image (and every custom widget which I have inserted) is being rebuilt every time when such action appears.
It looks like every action which I mentioned (new line etc.) causes that the whole editor executes embedBuilder and create new instances of inserted widgets (i.e. image).
Do you see any chance which could improve this situation?

@rish07 do you know anything about it?

Fixed by https://github.com/singerdmx/flutter-quill/commit/54c3eb446e2b90ec0a977d29eb0f21e2752dd07f
Please reopen if it still exists

@singerdmx  I would like to reopen this issue, because it is still visible in 1.0.9 version. The video shows the blinking image when I am adding new line..
https://user-images.githubusercontent.com/54472480/111499225-0288a400-8743-11eb-8c75-961e5ddab50f.mp4

Hey @singerdmx, i am busy with my exams rn, will take a look after them.

hello @rish07
I know exams are more important than this plugin, but I am wondering if you had time to take a look at that :)
Or at least maybe you have some tip how "rendering" of inserted objects are done by this plugin - maybe it would help me to find the problematic part of the code.
PS. I think it might be not only relevant to Web, but this is only my suspicious.

@mordivgor I am not really sure why it's rebuilding it.


Updates v3

OPS Build status updates of commit d080241:
:clock10: Preparing: average preparing time is 50 sec(s)

OPS Build status updates of commit d080241:
:clock10: Incremental building: average incremental building time is 26 sec(s)

OPS Build status updates of commit d080241:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mrtk-porting-guide.md
:warning:Warning
View
Details

mixed-reality-docs/development.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrtk-porting-guide.md

[Warning] Author author:grbury cannot be recognized in GitHub.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


V1 Prototype Snapshot

Objective
Immutable code snapshot/reference of the 1st V1 prototype.
Origin Document
One of the goals in mid-February was to build a foundation for the V1 module integration. Since it was just a prototype, the team is aware of the following:

As V1 matures, the code will likely change quite a bit.
To submit the current prototype to mainline, it'll be split into a handful (i.e. ~5) of smaller PRs.
It is just a prototype, and there are a lot of missing gaps in the implementation.
A lot of the existing code paths may be unused and there is no guarantee that all the tests are passing.

In order to have a reference to which we can revert, the snapshot of the code, as of Feb 18th 2022 will be submitted into a separate directory which can eventually be completely removed.
Deliverables

All the code used for the V1 end-to-end block demo
Notes were taken during final integration meeting
Notes/instructions on how to test

Context
Note that the goal this issue is not a complete prototype, but rather a history of the first functional end-to-end block.
For example, the following will be done in subsequent iterations:

Removing unused code
Removing pre_p2p with p2p
Fixing the consensus testing framework.
Etc...

Creator: @olshansky
Co-Owners: @andrewnguyen22 @derrandz @luyzdeleon

Opened a PR here: https://github.com/pokt-network/pocket/pull/27


Update MINA SSHD version

Move the MINA SSHD library dependency to 2.12.0 from 2.10.0.
The 8.7.0 update to JGit and the underlying SSH implementation is not compatible with 2.10.0 of MINA SSHD, causing all SSH Git dependencies to result in build failures.
Fixes https://github.com/gradle/gradle/issues/28823

https://github.com/gradle/gradle/issues/28823
Context

Some background is in the linked issue. Previous versions of Gradle did not work with modern SSH protocols, which made it unable to use services like github.com for source dependencies. These shortcomings were addressed with plugins designed to specifically address this issue, but the release of 8.7.0 broke the entire JGit SSH subsystem, once again making SSH source dependencies unusable.
Contributor Checklist

[x] Review Contribution Guidelines.
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[x] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle merge


[Feature]: Add Support for Decimal Increments in Number-Card Buttons

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
Currently, the number-card buttons only support integer increments. This enhancement request proposes adding the option to allow decimal increments for these buttons.
Describe the solution you'd like
Add a configurable property to the number-card component, allowing users to define the increment value, including decimal values.
The default increment can remain at 1, but the user can specify other increments like 0.1, 0.5, etc.
Describe alternatives you've considered
No response
Additional context
In some applications, users may need to adjust values in decimal steps (e.g., 0.1, 0.5) rather than whole integers. Having decimal increment support would improve flexibility and usability in scenarios where precision is needed.
Example: This functionality would be particularly useful for adjusting temperature presets on a thermostat, where precise decimal increments allow for more accurate control.
Look at the image below. Using preset entities i can only increment temperature by 1.

It supports decimal increment. It should use the step attribute defined in your number entity.

The entities I need to control are part of a device that likely does not define the step attribute but does support it. Is it possible to add a property to force the step value directly from the card?

No, it should be fixed at the entity level, not the card level. If you device supported decimal increments, it must set it in attributes. You should be able to override the step using customize: in your configuration.yaml (documentation: https://www.home-assistant.io/integrations/homeassistant/#manual-customization)

ok, tnks,
btw i'm using versatile thermostat.


Unable to detect the QR code generated when confuguring passkey through my account

Describe the issue:

Unable to detect the QR code generated when confuguring passkey through my account
Tried to scan the QR code with various scanners , but couldn't detect the QR code
https://github.com/wso2/product-is/assets/40081059/e907bdf0-5fe6-44ed-8f4a-d06235640658

How to reproduce:

Login to the myaccount
Go to security
Try to configure passkey by phone or tablet option

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This QR code is generated from the browser and we don't have any control over it. On a side note this QR code supposed to be scanned on a device which supports FIDO passkeys (ideally a mobile phone with passkey support) and not from a regular QR code scanner.
Refer for device support matrix: https://passkeys.dev/device-support/#matrix

@ThaminduDilshan checked this on various QR code mobile applications ,on ios device.
Still couldnt reproduce it

@asekawa, you have to use the phone camera or a QR scanner for this to work.
However, there are some issues if you are using Samsung mobile devices with "Samsung Pass" application to store the passkey. If you use Google password manager to store the passkey, this is working fine. Hence closing the issue.


[BUG] Cannot write in GS

In Google Cloud Storage, I am able to read data from the bucket but I cannot write data.
At the beginning I loging: gcloud auth login --no-launch-browser
This is the testing program using gcsfs (btw, DEBUG is not showing anything)
import gcsfs
import os

DEBUG = os.environ.get('GCSFS_DEBUG', True)

fs = gcsfs.GCSFileSystem()
f = fs.open("merlin-datasets/test.txt", 'wb')
f.write(2*2**20 * b'a')
f.close()

I get an Insufficient Permission error
Traceback (most recent call last):
  File "test.py", line 11, in <module>
    f.close()
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/fsspec/spec.py", line 1483, in close
    self.flush(force=True)
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/fsspec/spec.py", line 1354, in flush
    self._initiate_upload()
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/gcsfs/core.py", line 1409, in _initiate_upload
    self.metadata,
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/fsspec/asyn.py", line 71, in sync
    raise exc.with_traceback(tb)
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/fsspec/asyn.py", line 55, in f
    result[0] = await future
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/gcsfs/core.py", line 1492, in initiate_upload
    headers={"X-Upload-Content-Type": content_type},
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/gcsfs/core.py", line 507, in _call
    self.validate_response(status, contents, json, path, headers)
  File "/opt/conda/envs/rapids/lib/python3.7/site-packages/gcsfs/core.py", line 1222, in validate_response
    raise IOError("Forbidden: %s\n%s" % (path, msg))
OSError: Forbidden: https://www.googleapis.com/upload/storage/v1/b/merlin-datasets/o
Insufficient Permission

I should have both reading and writing permissions, as I can see in the IAM policy.
(rapids) root@b737df9c8ee2:/# gsutil iam get gs://merlin-datasets
{
  "bindings": [
    {
      "members": [
        "projectEditor:merlin-295819",
        "projectOwner:merlin-295819",
<EMAIL_ADDRESS>      ],
      "role": "roles/storage.legacyBucketOwner"
    },
    {
      "members": [
        "projectViewer:merlin-295819"
      ],
      "role": "roles/storage.legacyBucketReader"
    },
    {
      "members": [
        "projectEditor:merlin-295819"
      ],
      "role": "roles/storage.legacyBucketWriter"
    },
    {
      "members": [
        "projectOwner:merlin-295819"
      ],
      "role": "roles/storage.legacyObjectOwner"
    },
    {
      "members": [
        "projectViewer:merlin-295819"
      ],
      "role": "roles/storage.legacyObjectReader"
    }
  ],
  "etag": "CAM="
}

What I find suprising is that I can actually upload a file to the bucket using gsutil
(rapids) root@b737df9c8ee2:/# gsutil cp test.py gs://merlin-datasets
Copying file://test.py [Content-Type=text/x-python]...
/ [1 files][  190.0 B/  190.0 B]
Operation completed over 1 objects/190.0 B.

Any idea about what it could be going on @quasiben @martindurant ?

@albert17 I would suggest moving this to the gcsfs repo if you think there is a bug.  Looking briefly, it looks like you need to include the project name in the GCSFileSystem call

gcsfs.GCSFileSystem(project='my-google-project')

I am not sure if there is bug, or I am not configuring properly GCP.
GCSFileSystem  seems to work without setting the project (it gets the one I am logged in), I am able to list the bucket.
fs = gcsfs.GCSFileSystem()
print(fs.ls('merlin-datasets'))

['merlin-datasets/crit_int_pq', 'merlin-datasets/test.py']

@ayushdg have you experienced any issues with writing to gcsfs?

It works. The problem is that the VM was not configures properly. It requires:
Cloud API access scopes
Allow full access to all Cloud APIs


Unable to change DynamoDB billing mode from On-demand to PROVISIONED when using GSI

What happened?
When updating a DynamoDB table with one or more global secondary indexes, changing billing_mode from PAY_PER_REQUEST to PROVISIONED, the change doesnot apply. The GSI index read & write capacity gets updated to the desired values in the Composite Resource but the values show up as "0" capacity in the Managed Resource which makes it fail due to invalid parameter.
Message:

failed: updating Amazon DynamoDB Table (crossplane-ups-adapter):
ValidationException: One or more parameter values were invalid: ProvisionedThroughput
must be specified for index: index-A,index-B\n\tstatus code:
400, request id: CA1UOUUVQFB1FFAOTUCVTLLF4NVV4KQNSO5AEMVJF66Q9ASUAAJG: "

How can we reproduce it?

Create a Dynamodb table with PAY_PER_REQUEST billing mode and global index (I have been using 2 GSI's).
Once created change the billing mode to PROVISIONED and assign read & write capacity to the table and GSI.

What environment did it happen in?

Crossplane Version: v1.13.2 and v1.14.4
Provider Version: v0.40.0 and v0.46.1
Kubernetes Version: v1.27.8
Kubernetes Distribution: EKS

Hi @7navyasa,
Could you please include manifests for the resource both before and after update, to make it easier for those of us not as familiar with dynamodb to reproduce it?

dynamodb.zip
Hi @mbbush, here are the manifest to reproduce the issue

Hi @7navyasa,
Thank you for raising this but I could not reproduce this issue with the provided information.

Applied following:

apiVersion: dynamodb.aws.upbound.io/v1beta1
kind: Table
metadata:
  name: example-ft
  annotations:
    meta.upbound.io/example-id: dynamodb/v1beta1/table
spec:
  forProvider:
    region: us-west-1
    attribute:
    - name: UserId
      type: S
    - name: UserName
      type: S
    - name: Pass
      type: B
    billingMode: PAY_PER_REQUEST
    globalSecondaryIndex:
    - hashKey: UserName
      name: UserNameIndex
      nonKeyAttributes:
      - UserId
      projectionType: INCLUDE
      rangeKey: Pass
    hashKey: UserId
    rangeKey: Pass
    tags:
      Environment: production
      Name: dynamodb-table-1

Then I can configure it successfully according to the following:

apiVersion: dynamodb.aws.upbound.io/v1beta1
kind: Table
metadata:
  name: example-ft
  annotations:
    meta.upbound.io/example-id: dynamodb/v1beta1/table
spec:
  forProvider:
    region: us-west-1
    attribute:
    - name: UserId
      type: S
    - name: UserName
      type: S
    - name: Pass
      type: B
    billingMode: PROVISIONED
    globalSecondaryIndex:
    - hashKey: UserName
      name: UserNameIndex
      nonKeyAttributes:
      - UserId
      projectionType: INCLUDE
      rangeKey: Pass
      readCapacity: 10
      writeCapacity: 10
    readCapacity: 20
    writeCapacity: 20
    hashKey: UserId
    rangeKey: Pass
    tags:
      Environment: production
      Name: dynamodb-table-1

Please try it with these examples and let us know if it works.


fix service name and trace agent variables and default values

@0xbaadf00d Friendly reminder :)

When can I expect the next release with this fix?


Add x/y pixel movement readouts to pixel translate tool

Use BGL to draw text showing how many pixels have been moved.
Implementation notes:

Get reference point from a selected vertex
On update, find new position of reference vertex
Calculate pixel distance moved

Might want to move pixel translation to its own python file.

Implemented


ENH: Improve coverage for itk::FastMarchingImageFilterBase.

Exercise basic object methods.
Test all Set/Get methods using the TEST_SET_GET_VALUE macro, and all
On/Off methods corresponding to boolean members usign the
TEST_SET_GET_BOOLEAN macro.
Use the TRY_EXPECT_NO_EXCEPTION macro to update the filter and save
tryping the try/catch blocks.
Prefer initialization over assignment in variables.
Use the itkNotUsed macro for test input arguments and hence avoid
casting argc and argv to void to avoid compiler warnings.
Remove printing the input (speed) image.
Remove the calls to the Get* methods corresponding to base class
members (specifically: m_SpeedConstant, m_TargetReachedValue, and
m_NormalizationFactor should be tested for itk::FastMarchingBase in
itkFastMarchingBaseTest.cxx; and m_StoppingValue and GetCollectPoints
should be tested for itk::FastMarchingImageFilter in
itkFastMarchingTest.cxx).
Start comments with capital letters.
Minor style changes (such as white spaces between operators and
arguments, improvement of type names and error messages).

@jhlegarreta This was almost 2 years old.  I hope I rebased properly.

Jon Hait... Gorroño
Uploaded patch set 1.Apr 25, 2017
Jon Haitz Legarreta Gorroño
Apr 25, 2017
↩
Patch Set 1:
(3 comments)
Modules/Filtering/FastMarching/test/itkFastMarchingImageFilterBaseTest.cxx
Line 72:
I guess we could get away if we removed this. I fear that an input image of all zeros is not the most appropriate to test this class.
Modules/Filtering/FastMarching/test/itkFastMarchingImageFilterRealTest1.cxx
Line 172:
Anybodody knows why "1.42"?
Looks like expected value is about/almost zero:
itk::Math::abs( outputValue ) > itk::NumericTraits< double >::epsilon() * 1.42
Modules/Filtering/FastMarching/test/itkFastMarchingImageFilterRealTest2.cxx
Line 190:
Again, same comment as for itkFastMarchingImageFilterRealTest1.cxx
Kitware Build Robot
Apr 25, 2017
↩
Patch Set 1: Verified-1
Build Failed: CDash filtered results: https://open.cdash.org/index.php?&project=Insight&filtercount=3&field1=buildname/string&compare1=63&value1=22311-1&field2=buildstarttime/date&compare2=83&value2=2015-03-01&field3=buildstarttime/date&compare3=84&value3=2029-01-01
Jon Haitz Legarreta Gorroño
Apr 25, 2017
↩
Patch Set 1:
On the other hand, I'm well aware that setting the output image properties in itkFastMarchingImageFilterBase.cxx is not really meaningful since no real computation/check is performed. Setting them in *RealTest1.cxx or *RealTest2.cxx seemed not be very cautious to me given that my understanding of such implications is limited/was confused about the funny way (the "1.42") the output values were being checked.
Otherwise, we could write the output image in itkFastMarchingImageFilterBase.cxx and check the MD5 hash, using and w/o using the output image properties (i.e. two tests). That may require some a deeper understanding concerning the trial points, etc. which I may not have.
An alternative would be setting such properties in *RealTest1.cxx or *RealTest2.cxx, and checking that the test still passes. If it passes, it would be a little bit hard to understand why such a change does not affect the result/may indicate a bug (?); if not, I ignore how hard it'd be adapting it to check the right values.
Matt McCormick
Apr 27, 2017
↩
Patch Set 1:
(3 comments)
Modules/Filtering/FastMarching/test/itkFastMarchingImageFilterBaseTest.cxx
Line 53:
Non-identity (default) spacing is nice to test.
Line 63:
A non-null origin (the default) is nice to check.
Line 72:
If we set some TrialPoints, run the filter, and get the output, it may be not the most interesting, but we could have something to check?

Accidently deleted/closed branch when the script for moving from Gerrit went haywire.

@thewtex @jhlegarreta This issue is almost 2 years old.  I spent some time today making this PR pass regression tests.  While I am certain that more work could be done, I would like to move this incremental better solution forward to remove it from the 2-year-old backlog.  I don't think there is much interest in pursuing this more aggressively at the moment.

@hjmjohnson thanks for caring about this. I'll have a look at the comments/what was left undone it during the next few days, do the appropriate changes if any, and give some feedback.

Rebased on master for now. Revision to come later next week.

@jhlegarreta Can this be pushed as is, and then your additions added once you find the time?  I'd hate for this 2-year-old PR to become stale again.

@hjmjohnson @thewtex Thanks for your patience. I went through the comments. It does not look complicated what is left to improve the robustness of the tests, but it requires some time. As Hans told me a few weeks ago, "Don't let perfection be the enemy of the good", so for the time being, I think it is reasonable to merge it as it is, given that checks are passing, and it is already an improvement and a step towards the right direction.
I've opened an issue (#599) to keep track of the pending tasks. As said, affordable to anyone in the community, useful for all.
Sorry for taking so long to review it.

@thewtex Now we just need someone to approve, and it can be merged!  Let's try to get this in before 2 years have passed 👍 .


ng e2e documentation, clarify [project] parameter requires -e2e suffix

Bug Report or Feature Request (mark with an x)
- [ x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [ x] devkit
- [ ] schematics

Versions
6.0.8
Will attach a PR shortly.

https://github.com/angular/angular-cli/pull/11534

The ng e2e command accept any project, but by default we use the same project name and add -e2e to it. There's nothing preventing you from renaming that project (or having a new one) with a different name.
Going to close this but I'll keep a note with the documentation team to see if it's something we want to explain.


Is it possible to fill the box from right to left?

Hi
It is a great package.
I have a request, but I need to fill box from  right to left. Is it possible to do that?
thanks

Hi @robertoltrocha, do you mean to set textDirection property to rtl, right? not possible yet.

Hi,
not inside the box.
focus first right box and go left box, go left box, go left box when tap a number.
sds

@robertoltrocha this should work
    return Directionality(
      textDirection: TextDirection.rtl,
      child: Pinput(),
    );

Closing the issue, feel free to reopen if provided solution doesn't work.


fix(navbar): fix pipeline history nav bar

selection should check for sub path matches if no direct match found and
use reverse order to avoid matching 'Codebases' first (or the first tab in
general when a more specific URL matches) fixes
https://github.com/fabric8io/fabric8-ui/issues/870

@jstrachan snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1548-fabric8-ui.int.rdu2c.fabric8.io


Cannot find where you keep your Bower packages.

I'm stuck after running grunt serve, i've got this :
>Running "wiredep:app" (wiredep) task > Cannot find where you keep your Bower packages.
Any solution ?

bower install in case anyone looks here


Technical Requirements - QA Processing

QA Process:
Engage in QA reviews before finalizing.
Address and resolve any issues, documenting your process.

Literally this github projects page


[Application] Update weights_converter

the num_layer parameter is set to be automatically through auto config when converting weights from pytorch format to nntrainer format.
Signed-off-by: Seungbaek Hong<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2564. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2564-202405031324350.31297898292542-9fa00fb57c616c48cd86830c793a0c78837cf4da/report/pylint_result.txt.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2564-202405031345490.71203804016113-a31c733650b852c18b11b1783f94f2cc88660bcf/report/pylint_result.txt.


Adding new languages

Looking to see if there's been any movement on instructions for adding new languages. I went through the entire extension and modified it for inclusion of a new language.  The debug run shows the existence of all required files and the parser the wasm file is based on correctly parses the files. However, no semantic highlighting is occurring.   The modified extension packages, registers to vscode correctly, and the activation and other events run at the correct time when opening and editing a file.
I have a feeling the wasm file is somehow to blame, but also need to make sure I integrated the language correctly.  Any documentation in this regard would be much appreciated. Thanks for the extension!

I'm also having trouble adding new languages.
I've managed to get rtx format detected and to load the tree-sitter-rtx module, but there's no highlighting.  I think I'm missing one piece of the puzzle still?
You can view my work on this to date and an example of rtx format.


Segfault on invalid parameter to VideoSystem::display_name

Repro case:
fn main() {
    let sdl_context = sdl2::init().unwrap();
    let video_subsystem = sdl_context.video().unwrap();
    video_subsystem.display_name(4);
}

Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x000007fefe7c5a01 in strlen () from C:\windows\system32\msvcrt.dll
(gdb) bt
#0  0x000007fefe7c5a01 in strlen () from C:\windows\system32\msvcrt.dll
#1  0x000000000048f90d in std::ffi::c_str::CStr::from_ptr::h5f267934d9820f79 ()
#2  0x0000000000440b6c in sdl2::sdl::VideoSubsystem::display_name (self=0x22f960, display_index=4)
    at (snip)\src/sdl2/video.rs:508
#3  0x000000000041447c in (snip)::main () at (snip)\src/main.rs:31
#4  0x00000000004bb3d9 in __rust_maybe_catch_panic ()
#5  0x00000000004b85ab in std::rt::lang_start::h9fb2fbde5fcf1da2 ()
#6  0x0000000000415c6b in main ()

Having a segfault is definitely not fine, but it's still the programmer's job to make sure that the display is available. I understand that you might make want this to panic instead, but it requires an additional check that the programmer might have already done.
So I either propose that we keep this as is in Release mode (to not have any overhead) and to add an additional check that panics if it fails in debug mode, to have easier debugging. What do you think ?

Rust is very specific about this: it's the job of the unsafe {} boundary to prevent things like segfaults and other memory errors, at all times. If you want to keep things low-cost, return Result and let the user switch on Ok/Err, rather than doing a pre-check before calling the method.


Bump Kubefirst API SDK version.

Description
This PR synchronizes the SDK from Kubefirst API Go into this project. We don't have a formal release tag yet, but this should serve as the testing grounds for it.
Several functions in the SDK were updated to now return errors, and some function names have changed. This PR ensures those changes are reflected here.
Related Issue(s)

Fixes #
How to test

Keeping this in draft until I can get some good testing going tomorrow.

Cluster came up after fixing import:
{"level":"info","time":"2024-09-19T13:45:37-04:00","message":"updated secret \"kubefirst-cluster-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:45:37-04:00","message":"updated secret \"kubefirst-cluster-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:45:37-04:00","message":"waiting for final sync wave Deployment to transition to Running"}
{"level":"info","time":"2024-09-19T13:48:23-04:00","message":"waiting on dns, tls certificates from letsencrypt and remaining sync waves.\n this may take up to 60 minutes but regularly completes in under 20 minutes"}
{"level":"info","time":"2024-09-19T13:48:23-04:00","message":"waiting for deployment \"crossplane-rbac-manager\" in namespace \"crossplane-system\" to be ready - this could take up to 3600 seconds"}
{"level":"info","time":"2024-09-19T13:48:33-04:00","message":"all pods in deployment \"crossplane-rbac-manager\" are ready"}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"created Secret kubefirst-initial-state in Namespace kubefirst"}
{"level":"warn","time":"2024-09-19T13:48:43-04:00","message":"no secret found: secrets \"kubefirst-service-patrickdap\" not found"}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"created Secret kubefirst-service-patrickdap in Namespace kubefirst"}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"updated secret \"kubefirst-service-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"service added: github"}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"updated secret \"kubefirst-service-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"service added: Vault"}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"updated secret \"kubefirst-service-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:48:43-04:00","message":"service added: Argo CD"}
{"level":"info","time":"2024-09-19T13:48:44-04:00","message":"updated secret \"kubefirst-service-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:48:44-04:00","message":"service added: Argo Workflows"}
{"level":"info","time":"2024-09-19T13:48:44-04:00","message":"updated secret \"kubefirst-service-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:48:44-04:00","message":"service added: Atlantis"}
{"level":"info","time":"2024-09-19T13:48:45-04:00","message":"updated secret \"kubefirst-service-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:48:45-04:00","message":"service added: Metaphor"}
{"level":"info","time":"2024-09-19T13:48:45-04:00","message":"waiting for kubefirst-api Deployment to transition to Running"}
{"level":"info","time":"2024-09-19T13:49:00-04:00","message":"waiting for deployment \"kubefirst-kubefirst-api\" in namespace \"kubefirst\" to be ready - this could take up to 300 seconds"}
{"level":"info","time":"2024-09-19T13:49:10-04:00","message":"all pods in deployment \"kubefirst-kubefirst-api\" are ready"}
{"level":"info","time":"2024-09-19T13:49:10-04:00","message":"waiting for final sync wave Deployment to transition to Running"}
{"level":"info","time":"2024-09-19T13:49:10-04:00","message":"waiting for deployment \"argocd-server\" in namespace \"argocd\" to be ready - this could take up to 3600 seconds"}
{"level":"info","time":"2024-09-19T13:49:10-04:00","message":"all pods in deployment \"argocd-server\" are ready"}
{"level":"info","time":"2024-09-19T13:49:10-04:00","message":"updated secret \"kubefirst-cluster-patrickdap\" in namespace \"kubefirst\""}
{"level":"info","time":"2024-09-19T13:49:10-04:00","message":"cluster creation complete"}


Add/update KV docs for subcommands

Need to update the namespace subcommands, and add documentation for using key and bulk commands

I think we can close this now? Unless we want to wait until the final docs are merged before closing this.

should have been closed by #503


Gitbook intergration

here is an example: https://reda-bx.gitbooks.io/react-bits/content, just create a gitbook account and link the repo there

This is great 🎉 👍 🥇
Really like where this is going 😄

Glad to help

@vasanthk shall we merge  😄?

@Reda-bx Can you update the READ ME etc. Is it  possible to get it up with a custom url ?

@vasanthk yeah I'll do that, can you create an account on gitbook.com and link this repo? ( I dont have access to do that).

@Reda-bx It's available here https://vasanthk.gitbooks.io/react-bits/content/
Any ways to customize the url?

@vasanthk awesome, can you put it in the repo description, so people can find it easily?

Would be great to allow PDF and book format exports. Thanks for the effort 😊


Fix SC: href missing

As seen here
pipenv run python -m warn.cli sc -l DEBUG
2022-12-01 12:07:35,306 - warn.runner - Scraping sc
2022-12-01 12:07:35,306 - warn.utils - Requesting https://scworks.org/employer/employer-programs/at-risk-of-closing/layoff-notification-reports
/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/urllib3/connectionpool.py:1045: InsecureRequestWarning: Unverified HTTPS request is being made to host 'scworks.org'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
  warnings.warn(
2022-12-01 12:07:35,451 - warn.utils - Response code: 404
2022-12-01 12:07:35,4[51](https://github.com/biglocalnews/warn-github-flow/actions/runs/3592410692/jobs/6048090125#step:4:54) - warn.cache - Writing to cache data/warn-scraper/cache/sc/source.html
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.9.15/x64/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/hostedtoolcache/Python/3.9.15/x64/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/warn/cli.py", line 79, in <module>
    main()
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/warn/cli.py", line 75, in main
    runner.scrape(scrape)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/warn/runner.py", line [52](https://github.com/biglocalnews/warn-github-flow/actions/runs/3592410692/jobs/6048090125#step:4:55), in scrape
    data_path = state_mod.scrape(self.data_dir, self.cache_dir)
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/warn/scrapers/sc.py", line [56](https://github.com/biglocalnews/warn-github-flow/actions/runs/3592410692/jobs/6048090125#step:4:59), in scrape
    a_href = a["href"]
  File "/home/runner/.local/share/virtualenvs/warn-github-flow-R1xICqqL/lib/python3.9/site-packages/bs4/element.py", line 1519, in __getitem__
    return self.attrs[key]
KeyError: 'href'
make: *** [Makefile:[71](https://github.com/biglocalnews/warn-github-flow/actions/runs/3592410692/jobs/6048090125#step:4:74): scrape] Error 1

Looks the URL we are pulling is now a 404
https://scworks.org/employer/employer-programs/at-risk-of-closing/layoff-notification-reports


Update callout widgets to default to no border

Summary
Updates the callout widgets to default to no border instead of the rounded rectangle style border.

Current dependencies on/for this PR:

main

PR #87

PR #88   👈

This comment was auto-generated by Graphite.

@lucillebenoit started a stack merge that includes this pull request via Graphite.

Graphite rebased this pull request as part of a merge.

@lucillebenoit merged this pull request with Graphite.


Flash of unstyled content / SSR styles not flushed to head in<EMAIL_ADDRESS>

Bug report
Describe the bug
Styles aren't flushed to the head anymore in<EMAIL_ADDRESS>(they're nowhere to be found in the source served by the server), resulting in server-side source first rendered without styles, and then a client-side re-render showing those styles again.
<EMAIL_ADDRESS>works great, and so does<EMAIL_ADDRESS><EMAIL_ADDRESS>and the latest canary<EMAIL_ADDRESS>do not
To Reproduce
I was able to reproduce this with a typical next app using styled jsx, and (if that's meaningful in the current situation), the following HOC:

See code
const asPage = (WrappedComponent, pageTitle) => (
  class extends React.Component {
    static async getInitialProps(context) { /* ... */ }

    render() {
      return (
        <div>
          <Head>
            <title>{pageTitle && `${pageTitle} – `}Unspent</title>
            {/* various meta and link tags */}
            <link rel="stylesheet" type="text/css" href="/static/icons/iconfont.css" />
          </Head>

          <SessionContext.Provider value={this.props.session}>
            <WrappedComponent {...this.props} />
          </SessionContext.Provider>

          <style jsx>{`:global(body) { /* some global styles */ }`}</style>
        </div>
      );
    }
  }
);

Expected behavior
Style tags to be flushed in the head on server-side render.

Could you create a minimal repository? There's a lot going on in your code, including context, getInitialProps, but you're creating a HOC, so I'd like to see the full usage 👍

Had the same bug.
I had styled-jsx listed as a dependency in my project (even the same version<EMAIL_ADDRESS>uses: ^3.0.3-canary.0), but removing it and reinstalling all dependencies fixed the issue for me.

Hmm, I reinstalled<EMAIL_ADDRESS>today (I dropped the styled-jsx dependency yesterday), and things seem to be working with no meaningful changes from yesterday's setup. I did make a small test case before this, and couldn't reproduce in it either, so like @bergold mentioned it might very well be an issue with fully resetting deps!
I'll close since fully dropping deps and reinstalling them seems to indeed fix the issue! I'm unsure why that wasn't enough yesterday though.

@pioul Would you be able to extrapolate the process to avoid this "bug"? I'm having this same behavior but having a hard time understanding what is happening that is causing it and what exactly I need to do. I just started trying to use the


hyprpaper: init

Add hyprpaper styling using stylix.image as wallpaper.

IMHO, it would be more structured to add this functionality under an options.stylix.targets.hyprland.wallpaper option, although we might change the wallpaper option name.

I agree, this should be combined with the hyprland module.
However, having a separate option for it would make it different to all other modules, which just use the stylix.image value directly.

I agree, this should be combined with the hyprland module.

Something like this?
in {
  options.stylix.targets = {
    hyprland.enable = config.lib.stylix.mkEnableTarget "Hyprland" true;
    hyprpaper.enable = config.lib.stylix.mkEnableTarget "Hyperpaper" true;
  };

  config.wayland.windowManager.hyprland.settings =
    lib.mkIf config.stylix.targets.hyprland.enable settings;

  config.services.hyprpaper.settings = lib.mkIf config.stylix.targets.hyprpaper.enable {
    preload = ["${config.stylix.image}"];
    wallpaper = [",${config.stylix.image}"];
  };
}

IMO, hyprpaper is less of a target itself, and more just the means of theming hyprland. So ideally they should use the same option to enable both.

Your seemingly unrelated flake.lock changes from eb44e01 are causing build errors in my Home Manager setup, and have been reverted in e722720 to resolve this issues.

Thanks, I inadvertently added these when trying to get a local version of the repo to work in my NixOS flake.

7887ca8 removes the preload statement in attempt to reduce the running memory usage. Take a look at the commit message for more details. However, this causes Hyprpaper not to set the wallpaper anymore, as it is not loaded into memory before setting it. I assume this requires patching an unload option to Home Manager or Hyprpaper such that wallpapers are unloaded right after setting them.
@edrobertsrayne could you resolve this preload issue?

As far as I can tell, this is the expected way that hyprpaper works. You need to manually load the image into memory and then apply it. You can't set a wallpaper without using preload unless I've missed something. See hyprpaper wiki

7887ca8 removes the preload statement in attempt to reduce the running memory usage. Take a look at the commit message for more details. However, this causes Hyprpaper not to set the wallpaper anymore, as it is not loaded into memory before setting it. I assume this requires patching an unload option to Home Manager or Hyprpaper such that wallpapers are unloaded right after setting them.
@edrobertsrayne could you resolve this preload issue?

As far as I can tell, this is the expected way that hyprpaper works. You need to manually load the image into memory and then apply it. You can't set a wallpaper without using preload unless I've missed something. See hyprpaper wiki

Indeed. However, I was thinking about unloading the image after setting it, as it will not be set again. This would reduce the running memory usage.

7887ca8 removes the preload statement in attempt to reduce the running memory usage. Take a look at the commit message for more details. However, this causes Hyprpaper not to set the wallpaper anymore, as it is not loaded into memory before setting it. I assume this requires patching an unload option to Home Manager or Hyprpaper such that wallpapers are unloaded right after setting them.
@edrobertsrayne could you resolve this preload issue?

As far as I can tell, this is the expected way that hyprpaper works. You need to manually load the image into memory and then apply it. You can't set a wallpaper without using preload unless I've missed something. See hyprpaper wiki

Indeed. However, I was thinking about unloading the image after setting it, as it will not be set again. This would reduce the running memory usage.

I'm not sure you can do that, or at least should. The image has got to be in memory somewhere to be displayed and looking through the wiki it seems like the important option is unload unused. The unload command is a runtime command rather than a configuration option.

7887ca8 removes the preload statement in attempt to reduce the running memory usage. Take a look at the commit message for more details. However, this causes Hyprpaper not to set the wallpaper anymore, as it is not loaded into memory before setting it. I assume this requires patching an unload option to Home Manager or Hyprpaper such that wallpapers are unloaded right after setting them.

I'm not sure you can do that, or at least should. The image has got to be in memory somewhere to be displayed and looking through the wiki it seems like the important option is unload unused. The unload command is a runtime command rather than a configuration option.

This should be addressed in a follow-up PR, if at all. Feel free to revert 7887ca8, so this feature can be merged.
I opened https://github.com/danth/stylix/issues/408, to investigate this issue further once I have more free time.

IMO, hyprpaper is less of a target itself, and more just the means of theming hyprland. So ideally they should use the same option to enable both.

This is wrong, hyprpaper works perfectly well as a standalone background service for all wlroots-based compositors. It should be a separate target.

This is wrong, hyprpaper works perfectly well as a standalone service for all wlroots-based compositors. It should be a separate target.

Depends whether we're only setting it up when it's already been enabled, or if we're also installing it by default. If we removed the services.hyprpaper.enable = true line then I would support it being separate.
On the other hand, enabling the service automatically is helpful for Hyprland users who expect the wallpaper to "just work".

Users who except things to just work will not be using nix and compositor IMO.
Either way, at least have it as a separate target, and enable that in the Hyprland one.

Me? This isn't my PR.

My bad. I pinged the wrong person.


Model Links are dead.

The links given in disco.py are not working anymore.
model_256_link = 'https://openaipublic.blob.core.windows.net/diffusion/jul-2021/256x256_diffusion_uncond.pt' (Works)
model_512_link = 'https://v-diffusion.s3.us-west-2.amazonaws.com/512x512_diffusion_uncond_finetune_008100.pt' (Nope)
model_secondary_link = 'https://v-diffusion.s3.us-west-2.amazonaws.com/secondary_model_imagenet_2.pth' (Nope)
model_256_link_fb = 'https://www.dropbox.com/s/9tqnqo930mpnpcn/256x256_diffusion_uncond.pt' (Works)
model_512_link_fb = 'https://huggingface.co/lowlevelware/512x512_diffusion_unconditional_ImageNet/resolve/main/512x512_diffusion_uncond_finetune_008100.pt' (Works)
model_secondary_link_fb = 'https://the-eye.eu/public/AI/models/v-diffusion/secondary_model_imagenet_2.pth'  (Works)
Problem is that the script always tries to access the links without the 'fb', therefore no download possible.

model_256_link = 'https://openaipublic.blob.core.windows.net/diffusion/jul-2021/256x256_diffusion_uncond.pt'
model_512_link = 'https://the-eye.eu/public/AI/models/512x512_diffusion_unconditional_ImageNet/512x512_diffusion_uncond_finetune_008100.pt'
model_secondary_link = 'https://v-diffusion.s3.us-west-2.amazonaws.com/secondary_model_imagenet_2.pth'
model_256_link_fb = 'https://www.dropbox.com/s/9tqnqo930mpnpcn/256x256_diffusion_uncond.pt'
model_512_link_fb = 'https://huggingface.co/lowlevelware/512x512_diffusion_unconditional_ImageNet/resolve/main/512x512_diffusion_uncond_finetune_008100.pt'
model_secondary_link_fb = 'https://the-eye.eu/public/AI/models/v-diffusion/secondary_model_imagenet_2.pth'
these work for me

Thanks for the updated links. @nielsfechtel yeah that should be fine


debug a failure that's only happening in travis

:construction: :construction: :construction: :construction: :construction: :construction:
This is only happening in travis so I'm putting some debug stuff in and making a PR to get a better idea what's going on.

ok, this can be repro'd locally by running bundle exec rspec spec/integration/recipes/resource_load_spec.rb spec/unit/provider_resolver_spec.rb

:+1:

:+1:

:+1: :+1: :+1: :+1: :+1: :+1: :balloon: :birthday:


nsc features for v0.0.4

Here is the list of desired deliverables for the next release of v0.0.4:

Migrate coupled entropy function and quad integrations into the master branch.
Conduct unit and existing tests on the prob and sample_n functions for both CoupledNormal and MultivariateCoupledNormal classes.
Update the nsc guide to include these additions.
Test nsc libs on Coupled VAE notebook, using the MultivariateCoupledNormal class in the reparameterization as well coupled kl_divergence and coupled_entropy in the loss function.

See the current production version here and the test version here.

nsc lib has migrated to v0.0.4.


Lindalu add tip

Learn Build status updates of commit 40f93b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/office-365-management-activity-api-reference.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Vulnerability roundup 85: archiver-3.2.0: 1 advisory [5.5]

search, files

[ ] CVE-2019-10743 CVSSv3=5.5 (nixos-20.03)

Scanned versions: nixos-20.03: a84b797b28e. May contain false positives.

3.2 is a dead-end tree.  There is no fix other than to move to 3.3.x series...

I think this is not worth the hassle for 20.03.


[Bug]: None of the examples for open source telephony work

Brief Description
The replit for an incoming call with chat gpt on the other end, does not work and says "application error" when you call the twilio number. The example telephony app, when downloaded and hosted, also produces errors and hangs up immediately
Why are there no straightforward examples that actually work? All I want to do is test out vocode self hosted telephony and it's been a nightmare so far to get working.
LLM
ChatGPT
Transcription Services
Deepgram
Synthesis Services
Microsoft Azure
Telephony Services
Twilio
Conversation Type and Platform
No response
Steps to Reproduce
Just try using the examples provided on a fresh machine
Expected Behavior
Should be able to call and have a conversation with the bot
Screenshots
No response

I've run in to this too, using Cartesia. Cartesia updated their api endpoints so that's one aspect of things not working.


updates cross-env to latest (from prior: August 2016 version)

This could use an update.  From looking at the release notes there are no changes that affect our use case.  It turns out this library has been officially abandoned: https://github.com/kentcdodds/cross-env/issues/257, but it can't hurt to be on a semi-recent version.
It's hard to reverse the clock now, but I'm nearly sure I hit a problem with cross-env once (in insomnia-app) and I wonder, now having learned how out of date it is, if this was the reason.

I'm curious what the tradeoffs would be if we remove TS_NODE_PROJECT and make the default base ES5/ESNext and module commonjs.
https://webpack.js.org/configuration/configuration-languages/#typescript


RAM LEAK

The problem
my HA ram before instaled your integration they have 60-65% ram usage, after instaled integration my HA ram usage is 85-95%, and crash HA, im try set time update to 30-60 and more don't solve my problem, optimize integration please, this integration so good and have one problem.
today my HA crash 15 times when im delete integration ha working on 100%
Your device model
RT-AC57U V3
Firmware type
Stock
Firmware version

Integration version with the issue

Method of the integration installation
HACS
What version and type of Home Assistant installation do you use

Is there anything useful in the logs?
No response
Diagnostics information
No response
Additional information
No response

Hello, @milandzuris,
Could you please specify the following:

Version of integration with a problem

Did this start with the last version of the integration? Did it work well before?

Version and type of installation of your HA

What hardware do you use and how do you monitor RAM usage

What configurations of the integration are you using?

How regularly do you poll the sensors? This is the Interval to update entities value which can be selected during the configuration.

Does the HA log show any errors from the integration?

Please, opening the issue, do not ignore the template, which does explicitly ask half of the questions from the above. This will help speed up any troubleshooting and bug fixing.

Hello,
Unfortunately, without the information I have asked for, I cannot help you with the issue. RAM leak was never reported before by other users and I have never observed it yet.
If you would like to add any more information, that would help with diagnosing and solving the issue, feel free to reopen this issue.


makezip improvements

Now that we know more about zips, there's much room for improvement:

It seems that LZMA compression at level 3 takes the same amount of time as uncompressed (probably due to overheads and usb3 bottlenecks) with a compression ratio of about 62%. LZMA has 6% better compression but takes about 50% more time.
File splitting needs to be reduced from 500 gigs to something more like 100 gigs, as more LTO tapes will be filled up this way
Looks like the logging of makezip within sipcreator has repetition and some minor errors (like two verifications, but saying status=finished
It's worth investigating if 7za actually does the Test at the end of the zipping process. There's a very long stall at the end of a large zipping process, perhaps this is a fixity check, or maybe it is generating the hashes? It's worth figuring this out by intentionally damaging files with a hex editor and also trying to analyse the source code.
the mediatrace/mediainfo and dfxml all seem to hang around outside the SIP folder - these should be deleted
the extra manifest files in the logs need to be deleted too.

@stephenmcconnachie curious to know about any compression experiments ye did. I'm going to write a blog on my benchmarking - using mac pro 12 threads with USB3 source, Pegasus Thunderbolt RAID destination, 1.6 TB 2K DCDM as input - it takes a similar amount of time (about 16 hours) to compress with LZMA level 3. Maybe this is because of usb3/150K files overhead etc - I usually get a flurry of files being zipped, then it stalls, possibly to gather the crc32 checksums?..
Here's some benchmarks with reel 2 of a DCDM (no easily compressed opening credits)
I found that when i tested with the whole DCDM, the compression ratios for LZMA were much better 14% better) than the single reel values here  - probably because of more instances of easily compressible data like closing and opening credits - fades to black etc.
I'm running further tests now on the speeds for uncompressed whole zips just to see how similar it is.

compression_type | compression_level | duration_seconds | source_folder_size | zip_file_size | compression_ratio
Copy | 1 | 0:06:57.940210 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 1.00002220420092
Copy | 3 | 0:06:27.893932 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 1.00002220420092
Copy | 5 | 0:05:59.902307 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 1.00002220420092
Copy | 7 | 0:05:05.365766 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 1.00002220420092
Deflate | 1 | 0:05:22.166162 |<PHONE_NUMBER>8 |<PHONE_NUMBER>7 | 0.898235257674187
Deflate | 3 | 0:04:42.248375 |<PHONE_NUMBER>8 |<PHONE_NUMBER>7 | 0.898235257674187
Deflate | 5 | 0:05:03.380526 |<PHONE_NUMBER>8 |<PHONE_NUMBER>1 | 0.892897324485478
Deflate | 7 | 0:08:05.586272 |<PHONE_NUMBER>8 |<PHONE_NUMBER>7 | 0.890056917152535
Deflate64 | 1 | 0:05:17.997120 |<PHONE_NUMBER>8 |<PHONE_NUMBER>3 | 0.881973700986054
Deflate64 | 3 | 0:05:03.372004 |<PHONE_NUMBER>8 |<PHONE_NUMBER>3 | 0.881973700986054
Deflate64 | 5 | 0:05:09.055852 |<PHONE_NUMBER>8 |<PHONE_NUMBER>9 | 0.874977830706975
Deflate64 | 7 | 0:09:01.028490 |<PHONE_NUMBER>8 |<PHONE_NUMBER>8 | 0.873061854433095
BZip2 | 1 | 0:13:45.623366 |<PHONE_NUMBER>8 |<PHONE_NUMBER>1 | 0.831841806714
BZip2 | 3 | 0:15:25.845792 |<PHONE_NUMBER>8 |<PHONE_NUMBER>9 | 0.768753624151936
BZip2 | 5 | 0:14:04.008644 |<PHONE_NUMBER>8 |<PHONE_NUMBER>6 | 0.750003511034618
BZip2 | 7 | 0:46:38.657094 |<PHONE_NUMBER>8 |<PHONE_NUMBER>5 | 0.749998710596105
LZMA | 1 | 0:13:59.295197 |<PHONE_NUMBER>8 |<PHONE_NUMBER>6 | 0.82644176737402
LZMA | 3 | 0:12:38.996991 |<PHONE_NUMBER>8 |<PHONE_NUMBER>8 | 0.76160912040124
LZMA | 5 | 0:18:08.816210 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 0.693232182529742
LZMA | 7 | 0:17:11.254498 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 0.693387876230014
PPMd | 1 | 0:16:43.967409 |<PHONE_NUMBER>8 |<PHONE_NUMBER>7 | 0.837715345994377
PPMd | 3 | 0:18:22.252274 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 0.783456475293493
PPMd | 5 | 0:20:37.762131 |<PHONE_NUMBER>8 |<PHONE_NUMBER>2 | 0.725873858896796
PPMd | 7 | 0:30:14.558052 |<PHONE_NUMBER>8 |<PHONE_NUMBER>0 | 0.663441313225568

To clarify - I would have expected more of a gap in zipping time between lzma level 3 and uncompressed - it's the uncompressed that does the stalling after about 800 megs or so are processed (probably some I/O overhead and bottlenecks due to image sequence silliness)

Hi Kieran, we've never actually used any compression method for our DCDMs (or DCP or DPX either) - we use TAR only, not ZIP. I'm interested in your tests for ZIP modelling though, for DCDM, as obviously the data storage overheads are huge...

Yeah, we defo don't do it for DCP. For large DCDMs, I keep seeing that the uncompressed 7za processes take longer than Defalte and even LZMA level 3. So approx 60% space saving for even less time than compressed. I think it all depends on the I/O and the >100k small files are definitely a factor here, but we are moving ahead with LZMA level 3 for DCDM now anyhow - until we figure out how to get rawcooked to play nice with the folder structure of DCDM - and the confusion that will arise from having audio stems..

Keep us posted, I’d love to learn how that ZIP workflow pans out
From: kieranjol<EMAIL_ADDRESS>Sent: 04 November 2019 09:36
To: kieranjol/IFIscripts<EMAIL_ADDRESS>Cc: Stephen McConnachie<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [kieranjol/IFIscripts] makezip improvements (#366)
Yeah, we defo don't do it for DCP. For large DCDMs, I keep seeing that the uncompressed 7za processes take longer than Defalte and even LZMA level 3. So approx 60% space saving for even less time than compressed. I think it all depends on the I/O and the >100k small files are definitely a factor here, but we are moving ahead with LZMA level 3 for DCDM now anyhow - until we figure out how to get rawcooked to play nice with the folder structure of DCDM - and the confusion that will arise from having audio stems..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://url4.mailanyone.net/v1/?m=1iRYmS-000146-4q&i=57e1b682&c=GfpOQLhUhSRJmqmbfB212NfWDOBZmYGZ5-C5onza3OHQ0x4j54cUFPwJr5bTsVt7HxVHNlE9Ieh-85mqjhlrlGrPMVeJO0rO7qLrPb1FLx7Gk5gB6yOA7NRvPx3qLkT7TzZoo2P1PQalOm8DmnZbY7oJAGS9latzCQp8a6BZiFk_ENt22upZ25sKbXumLjjO55JlKQncTEUH6WAGHDluLGCBDEuOKIlsbnRvuOX1xhnJgLXZe51Hnh9Ljcdu_GTFVAIT2KUbDYdSQk7F8nVq9oyNfgGMupd0sDJin97yfsb_2udrKRwFEaAkfVcXI5gKuqxYpXYpeKJE1lxNhbWnWKcF1jwnVezZV4EI5BnD6MQDBEhXfE1nNGA3Icj83GOrOkjrZiWOn07VEJbkJ3r6DUXiAR3PdMMhzmDzbLslYKwgXF9pe4LrUdRKFlkyk_XvQu8akZ9z5Qb-RuM5GNzPfPMn9RH-0ARVv4kIAzC7WV4, or unsubscribehttps://url4.mailanyone.net/v1/?m=1iRYmS-000146-4q&i=57e1b682&c=QJPfEU3FBg8Jwjg0OEfsuOLSbLMzrFjEEAZpnSVZV-mH3P1BkjIBa0RJ3dPTNDZIWy1S7_JcGY0WtJ0h7FL-Zrn2-zXq3YqpUMKvoQzKwc6_DbIyH0FMBJ0SxElhhnNh3zt18ueTC5PYK-uGgrTZw4g17ea80pqZAOmaM5UaOpRmHPrpNpwsmUNp55cQ1bhZvitn-A0ijkkxrpThFylkuyVWH5tqebnhPXXce3cjtIMOI5ImAhETRFIDJ4HG92yOYrK_c5ujsW3ll5NLuiPmJSia1Wv2EuHXGuxUQB0KUzuBv8a33PVnGzKvMS3WaRGS.
The British Film Institute is governed by Royal Charter and is a charity registered in England and Wales number 287780. The contents of this e-mail are confidential and may be legally privileged. If you are not the intended recipient, kindly notify the sender that you have received this message in error and immediately delete it. Unless you are the intended recipient, you may not forward this e-mail to anybody, nor make any use of its contents.

Most of these have been added. I need to add a -uncompressed option to both sipcreator and makezip, as there are some DCDMs that have terrible compression ratios and the maxed out CPUs and added verification time are simply not worth the hassle. It's totally worth it for the times when we get significant reductions in size though.


author fields not being parsed correctly

Steps to reproduce:

$ touch index.js (optional)
$ npm init (finish wizard, this step probably is a bit inconsistent based on your current npm config setup.)
$ normalize

Actual results:
  "author": {
    "name": "Peter deHaan<EMAIL_ADDRESS>(http://nodeexamples.com/)",
    "url": ""
  },

Expected results:
"author": {
  "name": "Peter deHaan",
  "url": "http://nodeexamples.com/",
  "email"<EMAIL_ADDRESS>},
...

The normalized author field is now the string version so it's not expanded into an object.


Request to add SEPP component.

Hi @herlesupreeth ,
Could you please add the newly released SEPP component to the existing open5gs docker image?
I'm trying to simulate two 5g networks and would like to play around to understand interconnect been two 5g networks.
Awaiting to hear from you!!
Thank You.

Hey @r00tb3 sure, i will add over the weekend

Hey @r00tb3 sure, i will add over the weekend

It would also be great if you could also upgrade to open5gs v2.6.6.

@r00tb3 I had a look at the Roaming Tutorial and from the looks of it the feature is maintained as a separate branch and not merged to main branch so I am bit reluctant to add that component to this repo for now since there might be some changes in future. Eitherway I will see what I can do. Will let you know when I add SEPP component.
@r00tb33 I have upgrade the open5gs to v2.6.6.

@r00tb3 I had a look at the Roaming Tutorial and from the looks of it the feature is maintained as a separate branch and not merged to main branch so I am bit reluctant to add that component to this repo for now since there might be some changes in future. Eitherway I will see what I can do. Will let you know when I add SEPP component.
@r00tb33 I have upgraded the open5gs to v2.6.6.

Hey,
Thanks for the response!!
Can you too create a separate branch with SEPP component in it?
OR
Share here what files do I need to edit in the current branch to make the SEPP component work?
I really want to playaround and understand the SEPP  component with 5G romaing scenario.
Awaiting to hear form you!!

Hey @r00tb33 , okay then, I will try to add over the weekend (or sooner if I have spare time) then as a separate branch

Hey @r00tb33 I have created a new branch https://github.com/herlesupreeth/docker_open5gs/tree/roaming to support roaming scenario. When you want to connect sepp of another PLMN you need to add entries here - https://github.com/herlesupreeth/docker_open5gs/blob/75bb5d1b21a5c016c5f505631a3ad7311b995ab9/sepp/sepp.yaml#L21C1-L25C48 and uncomment the lines here - https://github.com/herlesupreeth/docker_open5gs/blob/75bb5d1b21a5c016c5f505631a3ad7311b995ab9/sa-deploy.yaml#L350C1-L352C26

Hey @r00tb33 I have created a new branch https://github.com/herlesupreeth/docker_open5gs/tree/roaming to support roaming scenario. When you want to connect sepp of another PLMN you need to add entries here - https://github.com/herlesupreeth/docker_open5gs/blob/75bb5d1b21a5c016c5f505631a3ad7311b995ab9/sepp/sepp.yaml#L21C1-L25C48 and uncomment the lines here - https://github.com/herlesupreeth/docker_open5gs/blob/75bb5d1b21a5c016c5f505631a3ad7311b995ab9/sa-deploy.yaml#L350C1-L352C26

Thanks for the work!!
I'll test it and get back to you.


Significant delay in initialization for completion/navigation on open file

I use vscode with clangd extension for code completion and navigation, but when I open or reopen a file, it takes a very long time, about 30~60s, for clangd to initialize. The log of the clangd extension is like below:
I[11:32:54.655] <-- textDocument/hover(2699)
I[11:32:54.782] <-- $/cancelRequest
I[11:33:26.077] --> workspace/semanticTokens/refresh(53)
I[11:33:26.077] --> textDocument/clangd.fileStatus
I[11:33:26.080] <-- reply(53)
I[11:33:28.536] --> textDocument/publishDiagnostics
I[11:33:28.556] --> reply:textDocument/documentSymbol(2688) 56891 ms
I[11:33:28.562] --> reply:textDocument/documentHighlight(2689) 56896 ms
I[11:33:28.572] --> reply:textDocument/semanticTokens/full(2690) 56907 ms
I[11:33:28.574] --> reply:textDocument/codeAction(2691) 56909 ms, error: Task was cancelled.
I[11:33:28.574] --> reply:textDocument/documentLink(2692) 56907 ms
I[11:33:28.575] --> reply:textDocument/codeAction(2693) 56731 ms
I[11:33:28.578] --> reply:textDocument/inlayHint(2694) 56378 ms
I[11:33:28.578] --> reply:textDocument/hover(2695) 52978 ms, error: Task was cancelled.
I[11:33:28.578] --> reply:textDocument/hover(2696) 52579 ms, error: Task was cancelled.
I[11:33:28.578] --> reply:textDocument/hover(2697) 51494 ms, error: Task was cancelled.
I[11:33:28.578] --> reply:textDocument/definition(2698) 51394 ms
I[11:33:28.578] --> reply:textDocument/hover(2699) 33923 ms, error: Task was cancelled.
The extension arguments are:
"clangd.arguments": [
"--background-index",
"--clang-tidy",
"--completion-style=detailed",
"--header-insertion=never",
"-j=40",
"--pch-storage=memory"
],
additionally, CPU usage show in htop is low and seems like parallel setting has no effect.
Output of clangd --version:
clangd version 15.0.6
Features: linux
Platform: x86_64-unknown-linux-gnu
Editor/LSP plugin:
vscode/clangd extension
Operating system:
centos7 kernel 3.10.0-1160.el7.x86_64

A few questions to try to narrow the issue down:

Does this happen with all files? Or all files in a particular project? Or a specific file / files in a project?
How big (lnes of code) is the affected file? How long does it take to recompile the file when rebuilding after making a change to it?
Do you see one CPU core being used heavily during those 30-60 seconds? (It's expected that the -j setting does not make a difference when opening a single file. It mostly has an effect on background indexing which processes multiple files in parallel.)

It happens with almost all .cpp files and some headers in a particular project.
Affected files vary from 500 lines to 3000 lines, in the case of .cpp files, the recompile after making change takes about 2~3secs.
Yes.

the recompile after making change takes about 2~3secs

Are you using clang as your compiler, or something else?
A possible diagnostic step that might produce some interesting information would be to attach the debugger to the clangd process, interrupt it a few times during the 30-60s pause, and get stack traces to see what clangd is doing at that time.


Save button not working

On Click of Create Resource Button, the webpage generates a downloadable JSON file with all the parameters and its values. The fields that are not entered will not be generated in the output JSON file.


Problem in CRB = crb_general_det_1d(design, wavelength, doas, P_est, noise_var, snapshot_count)

Thanks a lot dear morriswmz for sharing these useful codes. I kept the following files in same directory:
crb_general_det_1d.m
design_array_1d.m
ex1_design_and_visualize.m
steering_matrix.m
ula_1d.m
1st I ran the following lines in the m file " ex1_design_and_visualize.m "
clear(); close all;
wavelength = 1; % normalized
d = wavelength / 2;
design_ula = design_array_1d('ula', 12, d);
it created a structure which was not accepted by the function " crb_general_det_1d.m ". Then I renamed the structured as design. Then I kept the following arguments as input to  " crb_general_det_1d.m " and ran it:
CRB = crb_general_det_1d(design, wavelength, [10 20], 1, 1,1)
It gave me the following output:
CRB =
0.0006    0.0003
0.0003    0.0023

Now what does it mean? As we know that CRB denotes the lowest bound to the unbiased estimator as I read from your site:
https://research.wmz.ninja/articles/2017/03/crbs-in-classical-doa-estimation-problems.html
But here these are 4 values. As I have supplied two angles i.e., [10 20], so I should get two lowest bounds: one for each angle but here I am getting two bounds for each angle. Why it is so? Further, if I want to make a plot for it i.e., CRB vs Runs, then how will I do that? My email address is<EMAIL_ADDRESS>Also share your email address please.
Regards,
Sadiq Akbar

The function returns the CRB matrix. When you have two sources the returned matrix is 2x2. See https://en.wikipedia.org/wiki/Cramér–Rao_bound#Multivariate_case for more details about the multivariate case of CRB. The CRB formulas in https://research.wmz.ninja/articles/2017/03/crbs-in-classical-doa-estimation-problems.html are also derived for multi-source scenarios.


purge causes unnecessary reloads

On RHEL 7 with puppet 4.10.11 and crayfishx-firewalld 3.4.0, I get this with purge_services and purge_ports enabled:
Notice: /Stage[main]/Firewalld/Firewalld_zone[public]/purge_services: current_value purgable, should be true
Notice: /Stage[main]/Firewalld/Firewalld_zone[public]/purge_ports: current_value purgable, should be true
Notice: /Stage[main]/Firewalld/Exec[firewalld::reload]: Would have triggered 'refresh' from 2 events
Notice: Class[Firewalld]: Would have triggered 'refresh' from 3 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events
The result is  rules are updated and firewalld reloaded on every run with no changes to the rules.  (Enabling purge_rich_rules or purge_direct_rules doesn't cause a reload however.)
Is that expected behaviour?
Thanks

I've encountered this same issue, I think (or at least something very similar), but it seems to be with "purge_direct_rules", if you also have a direct rule object defined. Every run, Puppet purges all of the direct rules, adds the ones that it just purged back, and reloads firewalld.

So it turns out in my case this was caused by having a direct rule with "-s ! my_ip". The ! seems to cause the "purge" functionality to go haywire. I refactored my rule layout to avoid "!" and was able to work around the issue. So there's still a bug here, but it's more subtle than I thought.


Use the latest libxml2, libxslt, libyaml, and openssl

libxml2:
A GIANT list of bugfixes and these CVEs:
CVE-2017-9050
CVE-2017-9049
CVE-2017-9048
CVE-2017-9047
CVE-2017-8872
CVE-2016-9318
https://www.cvedetails.com/vulnerability-list/vendor_id-1962/product_id-3311/Xmlsoft-Libxml2.html
libxslt:

Fixes bad memory handling and null derefs plus a GIANT list of bug

libyaml:

Fixed segfault in yaml_string_write_handler.
Fixed invalid simple key assertion.
Fixed error handling in some examples (thank to Mathias Svensson).
Removed obsolete VS project files.

openssl:
CVE-2017-3731 (OpenSSL advisory)  [Moderate severity] 26th January 2017:
If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k Reported by Robert Święcki of Google.
CVE-2017-3732 (OpenSSL advisory)  [Moderate severity] 26th January 2017:
There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem. Reported by OSS-Fuzz project.
CVE-2016-7055 (OpenSSL advisory)  [Low severity] 10th November 2016:
There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behaviour. Even then only clients that chose the curve will be affected.ctures using a callback which do not handle NULL value are affected. Reported by Publicly reported.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>Description
[Please describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussion that's relevant]
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

This isn't ready to merge as it  fails builds on Windows due to the libxslt patch not properly applying.

I rant this SHA through Jenkins and it passed so I think this is good to merge. We're still seeing unit test failures in Travis that keep this from going green.


Can´t connect my Helium wallet to Swap Utility

Describe the bug
When trying to use the Swap Utility, I can't connect to my helium Wallet.
I press Select Wallet, I select Helium Wallet wich appears as detected but then I don't have an Accept button, only Cancel.
Smartphone (please complete the following information):

Device: Oneplus 8T
OS: 13
App Version v2.1.0

This should be fixed in v2.2.0+


Delegate and datasource use in UIViewController Class

How can i get the delegate response in UiViewController class?
See my code here, I want to add cancel button on the top of the left corner. I am using BDFPostPhotoViewerController.swift file.
Here is my Image Tapped Function where i initialise the class, i want to show/hide cross button on corner  when image zoom or zoom out.

i tried to use like this but here is some error. See screenshot

Please help me. Thanks

@ErAshu You just need to implement the required methods from delegate and datasource. If you are not displaying multiple photos, then you don't need to conform DTPhotoViewerControllerDataSource. If you want to do some actions when zooming in or out on image, you can override these methods: willZoomOnPhoto(at index: Int) or didEndZoomingOnPhoto(at index: Int, atScale scale: CGFloat)

When i tried to implement delegate method, see the screenshot. An error occurred. How i can implement this? I am not displaying the multiple photos. I am using UIViewController class. Simple on image tap, a method will call and image will zoom. Its working as expecting but only cross / close icon not showing as expected.
Method is displaying in screenshot. You can see in screenshot above.

@ErAshu I just updated the library and sample project. Can you download and check it again? And please remember to pod update DTPhotoViewerController to get the latest version.

Thanks a lot Bro... Now its working fine.


Pre-generate value in NEW form/view for a String Field

Is it possible to generate or fetch a value for a string field? like pre-generated code (Reference Code)?

I got this default on PostgreSQL, but it is working with Saltcorn

Sorry, I got it, just used javascript.

It might be worth putting the JavaScript code you used here for others to see.