OSError: Index size is not a multiple of vector size. Ensure you are opening using the same metric you used to create the index.: No error (0)

Index size is not a multiple of vector size. Ensure you are opening using the same metric you used to create the index.: No error (0)
Traceback (most recent call last):
File "C:\CelebDetector\test.py", line 4, in
celeb_detector.celeb_recognition(img_path)
File "C:\CelebDetector\venv\lib\site-packages\celeb_detector\celeb_recognition.py", line 37, in celeb_recognition
pred, img_out = get_celeb_prediction(img, ann_filepath, celeb_mapping_path)
File "C:\CelebDetector\venv\lib\site-packages\celeb_detector\celeb_utils.py", line 85, in get_celeb_prediction
_ = ann_index.load(ann_filepath)
OSError: Index size is not a multiple of vector size. Ensure you are opening using the same metric you used to create the index.: No error (0)

Hi,
Sorry for the late reply.
What ann_file are you using?

i am directly installing celeb-detector using pip and getting same error

You are unable to install celeb-detector using pip?
Which device are you trying it on?

I have the same issue,  I trained successfully and created an ann_file,   but celeb_recognition.py fails to read it.   The offending line is as reported
File "C:\CelebDetector\venv\lib\site-packages\celeb_detector\celeb_utils.py", line 85, in get_celeb_prediction
_ = ann_index.load(ann_filepath)

Running under python 3.7      All requirements successfully installed.  Check my MTCNN installation separately and that's working fine.   Appreciate any insight.


auth: relax authentication requirement when hosting on <IP_ADDRESS>

Alternative to #297. Allows EL clients to expose an unauthenticated Engine API when the host is <IP_ADDRESS>.

For the single-machine setup, it is doubtful whether JWT secret adds any signficant security: from a technical point of view, a socket bound to localhost cannot accept "outside" connections meaning that the only difference is the "filesystem" security - ie processes running as a different user may be thwarted by the additional token exchange, but we have to weigh this against the complexity and failure modes that having a file introduces. The alternative here is that we simply allow connecting without JWT as long as the socket is bound to localhost which achieves the "simple single-machine setup" with less of a hurdle (notably, the engine api is already sitting on a separate port from the "user-level" JSON-RPC interface, so the two live in different "security domains"). --@arnetheduck

--
Currently, if a user wanted casually run a EL and CL on the same host without the aid of any virtualization, it is required that the user specify the --jwt-secret flag for at least one client. Example:
$ geth --sepolia

$ lighthouse beacon --network sepolia --execution-jwt $HOME/.ethereum/sepolia/geth/jwtsecret

I think this is both unnecessary and confusing behavior for users. Ideally, the user should be able to, in any order, bring up an EL and CL and they communicate by default.
The preferred behavior would be:
$ geth --sepolia

$ lighthouse beacon --network sepolia

Another variant is to use a fixed jwt-secret in this scenario. Then the caller still needs to be able to set a custom header, which might raise the bar a bit more.
Then we don't have to worry about webpages doing some sneaky cross-domain POST and bypassing the preflight headers and stuff. I think. Not 100% sure though.


[QUERY] Documenting SymmetricSecurityKey size requirements

Library name and version
Microsoft.IdentityModel.Tokens 6.25.1
Query/Question
A customer for dotnet/runtime reported an issue with HMACSHA256 that turned out to be a non-issue, and just some uncertainty around the required key size for SymmetricSecurityKey. They were attempting to use a 96-bit key, where instead, there is a 128-bit minimum.
As far as I can tell, these key size requirements for SymmetricSecurityKey are not documented. Is this intentional? If not, do we think it makes sense to document them?
Environment
No response

This issue has been transferred to the repository where the Microsoft.IdentityModel.Tokens library is maintained as #1995.


Party map pin

Added the ability to have a custom map pin
Added the ability to change the map pin size

Your branch needs rebased
https://github.com/runelite/plugin-hub?tab=readme-ov-file#updating-a-plugin


add runner for starting a Diem node with custom genesis modules #9026 (139) AB#8771

add runner for starting a Diem node with custom genesis modules #9026
Motivation
This PR adds a folder that contains what you need to start a Diem node locally with a custom genesis module set, along with
some sample Move code and a sample application sending transactions to the local validator node you just started.
Test Plan

CI/CD tests are covered
cargo test --package shuffle-custom-move-code --test move_unit_test -- move_unit_tests --exact --nocapture

[move-package] Add support for documentation and ABI generation and building of Move Model. #9030
Motivation
Builds on #8775 to add documentation and ABI generation to the package system. Additionally, in preparation for hooking up the Move Prover with packages, model building for a whole package is added. Only look at the top commit.
It is important to note that because the Move Model requires source files, at this time we cannot support renaming of named addresses in packages where you need to build a Move Model for a package and all of its dependencies. In the future we will want to support this, however this will most likely require support from the source language or compiler (to either support renaming at expansion, or in generation of interface files).
Related PR

#8775

Test Plan

CI/CD tests are covered
cargo test --package move-package --test test_runner

[Forge] Add forge LBT in ci-test #9039
Motivation
[Forge] Add forge LBT in ci-test
Related PR

#9039

Test Plan

CI/CD tests are covered

[move] Remove Move IR type inference #9040
Motivation
Simplify the Move IR language and compiler by eliminating the need to keep track of the types of expressions.
For the most part, this requires no change to the language, except for one aspect: when struct fields are borrowed, the user must now explicitly specify which struct type is being accessed. This is because, for example, a simple field identifier f may refer to different fields in any number of different structs S1, S2, etc.
What's in this pull request?
The file count is large because this includes test changes -- the *.mvir files. You can look at them to see what the new field access syntax in Move IR looks like: s.S::f, where s is a struct instance, S is its type, and f is the name of the field being accessed.
The rest of the changes, in the *.rs files are almost exclusively just deleting the InferredType enum.
Test Plan

CI/CD tests are covered
cargo test --package compiler --lib -- unit_tests::function_tests::compile_module_with_functions --exact --nocapture

[diem-framework] Port ValidatorConfig and ValidatorOperatorConfig to unit tests #9131
Motivation
Port ValidatorConfig and ValidatorOperatorConfig to unit tests - Ported testing for the ValidatorConfig and ValidatorOperatorConfig tests to be unit tests.
Test Plan

CI/CD tests are covered
language/diem-framework/tests/ValidatorConfigTests.move

[2chain] switch to use 2-chain in Genesis module #9132
Motivation
Starting from this commit, new genesis would be initialized with two_chain = true that enables 2-chain consensus protocol by default.
Test Plan

CI/CD tests are covered

[cluster-test] Update image tag for -M/--master #9141
Motivation
[cluster-test] Update image tag for -M/--master
Related PR

#9141

Test Plan

CI/CD tests are covered

[forge] disable logtonull #9158
Motivation
In this PR we stop overriding the logging config from forge itself, and instead rely on the config provided by the initial helm install by Terraform
Test:

./scripts/fgi/run --pr 9158

Test Plan

CI/CD tests are covered

[decoupled-execution] buffer manager execution phase logic #9126
Motivation

[decoupled-execution] buffer manager execution phase logic
This PR deals with
refactor buffer items.
execution phase logic.
remove the buffer diagram as the current design is extremely simple.

Test Plan

CI/CD tests are covered
cargo test --package consensus --lib -- experimental::tests::execution_phase_tests --nocapture

[State Sync] Add a new EventSubscriptionService and tests #9117
Motivation
This PR adds a new on-chain event subscription service to state sync (EventSubscriptionService). Using this service, other components can subscribe to on-chain events and be notified about on-chain reconfigurations. This service differs from the existing on-chain publishing (already provided by state sync) in the following ways:

The service will support arbitrary event subscriptions (not just reconfiguration events!). This is required by future work streams (e.g., the on-chain networking identity work).
The service will not require reconfiguration subscribers to subscribe to individual on-chain configurations, but instead receive all configs when a reconfiguration event occurs. This is because: (i) subscribing to individual configs only adds code complexity, but doesn't provide any tangible benefits (e.g., performance or resource usage). Reconfigurations are fairly infrequent and subscribers tend to just pull out the data they want anyway; (ii) there are actually bugs in our code today where subscribers subscribe to individual configs, but on reconfiguration notifications, access configs they didn't subscribe to (!!). This is because the code already returns all configurations to subscribers anyway; and (iii) there doesn't currently appear to be any requirements for this functionality. If we wish to have this functionality, we can always extend this service to provide it in the future.
The service will better encapsulate the relationships between subscribers and notifications, and not leak implementation details and abstractions. Moreover, the service will be better tested! Right now, there's minimal testing for the on-chain publishing support.
Notes:

Half of this PR is just unit tests (so it hopefully shouldn't be that scary! 😄)
This PR is comprised of two commits: (i) the new service itself; (ii) unit tests.
Test Plan

CI/CD tests are covered
cargo test --package event-notifications --lib -- tests::test_all_configs_returned --exact --nocapture

[State Sync] Don't panic on failures to read on-chain configs. #9130
Motivation
There was recently a bug uncovered in some of our legacy code where state sync will panic if it's unable to fetch the value of a config on-chain (see here: #9121). This PR fixes the bug as described in the issue: essentially just log an error on a missing config and expect the reconfiguration subscribers to handle the missing configs. As such, the PR offers two commits:
Add a new unit test to ensure that state sync doesn't panic when configs are missing on-chain (both at startup and during a reconfiguration event).
Fix the original bug in the code.
Note: This code is all going to be cleaned-up, refactored and improved as part of state sync v2 (e.g., I already have an outstanding PR to move all of this code into a single component: #9117). As a result, I've focussed just on fixing the bug in this PR and not handling any of the tech-debt surrounding the issue. This tech-debt will be cleaned up in state sync v2 (including adding tests to the reconfiguration subscribers to ensure they appropriately handle missing on-chain configs).
Test Plan

CI/CD tests are covered
cargo test --package state-sync-v1 --test integration_tests -- test_basic_catch_up --exact --nocapture

json-rpc: implement missing MockDB methods to fix fuzzer #9128
Motivation
Continuous fuzzing discovered a panic in the json-rpc fuzzer where one of the fuzzers managed to discover get_accumulator_consistency_proof and called it. The fuzzer, however, uses a MockDB rather than a real DiemDB. The MockDB didn't have get_accumulator_consistency_proof implemented and so the fuzz test panicked with unimplemented!(). This means the fuzz panic is a false positive, but something we should fix nonetheless so it can discover more useful stuff.
To fix the problem, this PR back-fills all of the missing DB methods called by the json-rpc service with dummy implementations so the fuzzer won't panic if it discovers other methods. We also add the rest of the json-rpc methods (except get_resources) to the test_method_fuzzer test so we can surface these unimplemented!() panics sooner in CI.
Test Plan
CI/CD Test were covered

[consensus] make the optionally compiled code more obvious #9135
Motivation
[consensus] make the optionally compiled code more obvious.
Related PR
https://github.com/diem/diem/tree/main/developers.diem.com
Test Plan
CI/CD tests were performed

/canary

:boom: Tests timed-out

/canary

Closing this PR as it has technical issue


Setting minimumSystemVersion for macOS not possible

Describe the bug
As documented here we should be able to specify minimumSystemVersion for MacOS builds:
https://github.com/JetBrains/compose-multiplatform/tree/master/tutorials/Native_distributions_and_local_execution).
This is not possible and I get an "Unresolved reference: minimumSystemVersion" error when building projects.
I would like to set minimum version to 12.0.0. I can add custom plist key with extraKeysRawXml, but then I get an error when trying to upload to testflight:
Asset validation failed (90264)
Invalid product archive. The lowest minimum system version in the product definition property list, 10.13, must equal the LSMinimumSystemVersion value, 12.0.0. (ID: 4db7c056-bd2c-413a-b469-f0cc5022e2e1)

It seems the gradle plugin code, if we were allowed to specify minimumSystemVersion, would actully set the info.plist correctly and also set the product-def.plist correctly. As seen on lines 499-514 here:
https://github.com/JetBrains/compose-multiplatform/blob/master/gradle-plugins/compose/src/main/kotlin/org/jetbrains/compose/desktop/application/tasks/AbstractJPackageTask.kt
Affected platforms

macOS

Versions

Kotlin version: 1.9.22
Compose Multiplatform version: 1.6.1
OS version(s)* (required for Desktop and iOS issues): All
OS architecture (x86 or arm64): x86/arm64
Device (model or simulator for iOS issues): N/A
JDK (for desktop issues): jbrsdk-21.0.2-osx-aarch64-b346.3

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

Add compose.desktop.application.nativeDistributions.macOS.minimumSystemVersion key to build.gradle.kts file for jvm project
Sync project
See error (error also visible in IDE as compile error)

Expected behavior
That we can set minimumSystemVersion as documented.

The minimumSystemVersion property is available since compose 1.6.10 only:
https://github.com/JetBrains/compose-multiplatform/commit/e1aff758c0d6c9b2547542a934b643cf25c8f1b1

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Files with external http:// uri refererences can't be procesed with gltf-pipeline

I'm trying to convert some old glTF 1.1 files to glTF 2.0.
While that works in general, it seems that external references throw up gltf-pipeline:

Here's an example:
https://storage.googleapis.com/assets.icosa.gallery/63208108939333337/63210051195686758/GLTF/sketch.gltf
https://storage.googleapis.com/assets.icosa.gallery/63208108939333337/63210051195686758/GLTF/sketch.bin
To reproduce:

download the two files above
run gltf-pipeline -i sketch.gltf -o sketch.glb
note the exception being thrown

Expected
External references are kept as external references
Additional Context
While the issue here is happening during glTF 1.1 -> glTF 2.0 conversion, I believe this also affects general use with glTF 2.0.

To add some detail - this is (as far as I know) specifically a Tilt Brush thing. But there's a fair number of Tilt Brush GLTF v1 files out in the wild.
Is there any reason gltf-pipeline shouldn't treat file references as opaque unless requested to handle them?

Here's a glTF file without the tiltbrush extension(s) that has the same issue:
needle_godot_plush_ref.gltf.zip


⚠ Samsung has degraded performance

In 19bf6a2, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2597 ms

Resolved: Samsung performance has improved in 7708ba0.


Connectathon 13 financial track

Rebase issues; made a new Pull Request with the contents of this one that is correct.


Schema update

Remove duration requirement if the data isn't available, and default it to 90 minutes (or something sensible) in the calendar
Change age-restriction to camelCase; ageRestriction
Version the schema

Changed age-restriction to certification to match the movie DB API
Doesn't seem to be a way to version the schema


bump version and switch from uuid to elixir_uuid

uuid was renamed to elixir_uuid. Those that have other dependencies which have switched to the new naming can run into issues with dependency checks.

@ueberauth/core can we merge this please?


Build Fails withUndefined symbols for architecture x86_64  MacOS HighSierra.

What platform/OS are you using?
MacOS 10.13.4
What compiler are you using? what version?
Apple LLVM version 9.1.0 (clang-9<IP_ADDRESS>)
What's your CMake arguments?
-DBUILD_ONLY="s3;sqs;sns;lambda;kinesis"
Can you provide a TRACE level log? (sanitize any sensitive information)

Could you provide the error messages?

Please provide the output from cmake and the output from your compiler. What are the undefined symbols?

You can close this issue.  I've not been able to recreate the error.  It's building fine currently.


MAINT: optimize.minimize: revert gh-11712 to fix macos_arm64_test

Reference issue
gh-11649
gh-11712
What does this implement/fix?
macos_arm64_test has a failure in main:
FAILED scipy/optimize/tests/test_minimize_constrained.py::test_gh11649 - UserWarning: delta_grad == 0.0. Check if the approximated function is linear. If the function is linear better results can be obtained by defining the Hessian as zero instead of using quasi-Newton approximations.

This was just a warning, but it exposed a bug introduced in gh-11712. This PR reverts gh-11712 but leaves the test (and strengthens it), xfailing it with strict=True. The original issue, gh-11649, has been re-opened, and the xfail mark can be removed when it is resolved.
Additional information
@dpoerio I know you are not able to merge this, but would you review it since you're familiar with the issue? I think that will help another maintainer.

LGTM as a stop-gap. When this is merged, please list it in gh-17278


Error at E17

NullReferenceException
UnityEngine.Texture.get_width () (at /Users/builduser/buildslave/unity/build/Runtime/Export/Texture.bindings.cs:30)

Fixed


chore: add compressed-size-action

Overview

Add the 'compressed-size-action' to check the size of the dist folder in packages.
PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.28%. Comparing base (c1b88cf) to head (f8884e6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1124   +/-   ##
=======================================
  Coverage   78.28%   78.28%
=======================================
  Files          59       59
  Lines         654      654
  Branches      132      132
=======================================
  Hits          512      512
  Misses        132      132
  Partials       10       10

Components
Coverage Δ

@suspensive/utils
47.16% <ø> (ø)

@suspensive/react
96.88% <ø> (ø)

@suspensive/react-query
67.66% <ø> (ø)

@suspensive/react-query-4
0.00% <ø> (ø)

@suspensive/react-query-5
0.00% <ø> (ø)

@suspensive/jotai
0.00% <ø> (ø)

@suspensive/cache
98.16% <ø> (ø)

@suspensive/react-image
80.39% <ø> (ø)

@kangju2000 could you make this action check only cjs, js, mjs please?


[Bug]  502 errors streaming from data.source.coop

Reading source.coop directly from the AWS endpoint (with duckdb) is fast and reliable:
import ibis
from ibis import _
con = ibis.duckdb.connect()

query=   f'''
CREATE OR REPLACE SECRET secret1 (
    TYPE S3,
    ENDPOINT 's3.us-west-2.amazonaws.com',
    URL_STYLE 'path'

);
'''

con.raw_sql(query)

gbif = con.read_parquet("s3://us-west-2.opendata.source.coop/cboettig/gbif/2024-10-01/**")
gbif.count().execute()

succeeds and shows:
Wall time: 19.2 s
2891218873

Reading the same data from the same bucket using  the data.source.coop endpoint is slower and usually results in a 502 error.  (occasionally a 404 error, which does not happen in the above case reading identical data bucket)

con = ibis.duckdb.connect()

query=   f'''
CREATE OR REPLACE SECRET secret1 (
    TYPE S3,
    ENDPOINT 'data.source.coop',
    URL_STYLE 'path'

);
'''

con.raw_sql(query)
gbif = con.read_parquet("s3://cboettig/gbif/2024-10-01/**")
gbif.count().execute()

throws:
HTTPException: HTTP Error: HTTP GET error on 'https://data.source.coop/cboettig/gbif/2024-10-01/000303.parquet' (HTTP 502)

after taking significantly longer to run.  (502 error does not always occur on the same parquet file).
(Note that mirroring this bucket to another S3-based system (e.g. CEPH, MINIO) on an alternative endpoint, and querying that with the identical code as above works fine).

As discussed over the slack, controlling the number of parallel threads from duckdb query seems to help.
As far as providing a more scalable service, I will discuss with @ecov-user and @jedsundwall and let you know.

The response from the api call is much faster and without any errors. @cboettig Do we need to keep this issue open?

nope I think this is all resolved now! Big thanks!


Changed the css for why choose us from internal to external css and a…

changed the styling from internal to external css and also changed the color of button from blue to purple.

Thanks @Vyom-26 for making the required changes. We will merge it soon 🤩


Provide functions to pretty print the ast to string

Gives an alternative to printing to stdout. I think this could also be achieved without a new function by moving the responsibility of flush to the caller.

Super useful. Thanks!

I think we are on the same page - but maybe not. This just pushes all responsibility for formatter management on whoever is using the pretty printer. If you meant that you like having the explicit calls to return strings but that the logic should be moved down to the ReasonFormatter module then we can do it that way too.

@yunxing I'll let you merge this one

Hmm, I actually don't think this should be part of the API. The original API is already pretty generic so whoever uses it can implement the toString method by themselves.
If we really don't want to ask the caller to flush, maybe we can build a more generic API here:
let string_of_formatter (f: (Format.formatter -> 'a -> 'b)) x =
  ignore (flush_str_formatter ());
  f str_formatter x;
  flush_str_formatter ()

Then you / the caller can implement the same thing using:
let signature_string comments x =
   string_of_formatter (signature comments) x

without copying all the code.

That makes sense! I'll look into doing that.

FYI, there is Format.asprintf which does exactly what you want

@bobzhang that's pretty sweet. I didn't realize that function existed so I'm not sure how necessary this helper is now. It's nice that Reason is providing this function so you don't have to think about the underlying formatter, but it isn't strictly necessary.
I tried getting it so the signature looks more like string_of_formatter ?comments ~f ~ast but I don't really understand how the types in Format work, so I wasn't able to get it running correctly.

The diff looks good to me. Let's get this merged.


Browser Tracker: setUserId() generating some sort of hash instead of using the supplied string

Describe the bug
I'm using the free trial of snowplow via try-snowplow.com to scaffold a PoC for a project. When setting up the client side javascript/tracker, I'm attempting to use the setUserId() function to provide a custom string from our business-defined logic. As per the docs, my string is passed as a parameter to the function, however this does not match what I see for the event in postgres.
The following result in a NULL field value in postgres:

Removing the setUserId() function completely on the client-side
setUserId(undefined);
setUserId('');
setUserId(null);

However, as soon a single character is passed as the string value, I start to get the generated value in postgres:

setUserId('h'); results in 9920fe00cf732e9535164dc652fc99e4457495a1
 setUserId('foo'); results in 3dff8f971d37e31173016101db0b2551de168f41
setUserId('123wedf-cjsfs'); results in  e4a5087fad4cdc03be1bea9b587c5cca43251e18

To Reproduce
import { newTracker, trackPageView, setUserId } from '@snowplow/browser-tracker';

newTracker('sp-browser-tracker', 'https://XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.app.try-snowplow.com', {
  appId: 'sample-app',
  cookieSameSite: 'Lax',
  plugins: [],
});

setUserId('user-123');
trackPageView({ title: 'Sample Page' });

Expected behavior
I would expect that using setUserId('user-123'); would result in user-123 in the user_id field for the event data. However, when I trigger events, I get some sort of auto-generated value or hash instead of my string, such as 6e6e802665fe4d994202789b338a533c888b9c32.
Screenshots
How the user_id gets added to the event in postgres:

Desktop (please complete the following information):

OS: MacOS 10.15.7
Browser: Chrome
Version: 93.0.4577.82 (Official Build) (x86_64)

Additional context
PostgreSQL 13.4
@snowplow/browser-tracker: 3.1.4

Hi @Scott-Fischer
This is because the Try Snowplow pipelines have the PII Enrichment enabled for the User Identifier fields. This hashes the User fields, such as user_id. With your own full Snowplow pipeline, you could disable this but thats not possible in a Try Snowplow pipeline since it's a trial that Snowplow host.
The following fields will be hashed:
user_id
user_ipaddress
domain_userid
network_userid
domain_sessionid

If you validate the event thats being sent using the Snowplow Inspector then you should see the tracker is sending it as expected, its just being hashed as part of the Try Snowplow pipeline.

@paulboocock - thanks for the clarification!
I realized that the automatically collected PII was hashed such as user_ipaddress and domain_userid but I did not realize that this also extended to the manually collected user_id.
Do you think it's worth adding a small line to the doc indicating that the provided string value will be hashed if the PII enrichment is enabled? If so, I'd happy to do this if you're accepting community PRs.

We are accepting of community PRs however, the PII Enrichment is very configurable, you don't have to hash user_id with it however we have chosen to with Try Snowplow to hash any potential PII on the hosted Snowplow version.
We have added some text to the Try Snowplow experience though during the tracker setup, to make it clear that fields are being hashed. That should roll out today I think.


⚠ Bofrost.lu has degraded performance

In 46de0ac, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1367 ms

Resolved: Bofrost.lu performance has improved in 63b46b4 after 20 minutes.


Terraform section layout and getting-started

What changed, and why it matters
This PR brings in the following changes:

Terraform section layout including HowTo, Reference, and a Getting Started page.
Removing old getting started from the landing page.
Adding a new getting-started page.
Moving the only HowTo article under a HowTo section.

Changes via latest commits:

Brought instructions block before the code block so that the audience understands what the code blocks will do.
Edited section titles based on feedback.
code/literal formatted couple of variables.
Clarified admin level access for API auth token.
Added further instructions so that the audience can be confident with terraform destroy.
Further reference for those who'd like to setup a more complex Terraform project.

Still a bit unclear:

What explanation to add on the Terraform project itself?
If the modified text for admin level access for auth token will suffice
If it's appropriate to use BYOTF - Bring Your Own Terraform Script

@lornajane thanks for your last review and looking forward to this round of review.

Changes via https://github.com/aiven/devportal/pull/646/commits/66ee4ca0d0c00d6e7c8efe0cdb6eefddfb6872ec:

Fixes based on @lornajane's last review.
Adding a newline to the docs/platform/concepts/tls-ssl-certificates.rst file which was causing a warning during build

I marked other comments as resolved but left one open which I'm not quite sure about.
Lorna has scheduled a 30mins call for March 22, 2022 to go over rebasing this branch with main (and resolving the conflicts).

Thanks @lornajane for the help with rebase. I added a few more changes to fix the indentation issue and section title (based on your previous comments).
Currently, on the landing page, we have a shortcut to 'Reference' and 'Cookbook'. Is that Ok? Since we only have 'Cookbook' under the 'Reference' section, I wonder if having both is redundant. Another way to think is we might have non-cookbook content under the 'Reference' section in the future so it might make sense to keep both.
Looking forward to your thoughts on this and any other change that this PR might need.

I pushed some small changes, @dewan-ahmed take a quick look that I haven't done anything awful and then we'll merge if you're happy?

Thanks @lornajane
The guide reads much better after your edits.
I have one small question about the phrase "show off" but other than that, I'm very happy. Thanks again.


Godot cannot create folder in "new project" dialog if there are invalid characters in the name and doesn't scrub input for folders

Tested versions

Found in v4.2.1.stable.official, likely reproducible in other versions

System information
Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - integrated Intel(R) HD Graphics 530 (Intel Corporation; <IP_ADDRESS>1) - Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 Threads)
Issue description
If you attempt to create a project with the name having invalid folder characters in the name and press "Create folder", then it will say "cannot create folder". If you manually make a folder without special characters(or temporarily change the name of the project, create the folder, then change the name back), then everything functions normally. What I would expect is for Godot to do some input scrubbing and remove/replace invalid characters in the name,
Steps to reproduce

Attempt to create a project.
Name it something with an invalid character(such as a question mark ? in it).
Press "Create folder".

Minimal reproduction project (MRP)
N/A

What should the expected behaviour be?
Either the wrong characters be removed from the filename or godot saying tha the change is not possible right?

I think that the characters being replaced with underscores(like GitHub)
would work well
On Thu, Apr 25, 2024, 11:02 AM Borges-IST-2003 @.***>
wrote:

What should the expected behaviour be?
Either the wrong characters be removed from the filename or godot saying
tha the change is not possible right?
—
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/90026#issuecomment-2077645333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATOOUFW2BG4LAPP5ZMARF3DY7ESJRAVCNFSM6AAAAABFO6LHT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGY2DKMZTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Cannot find module ../aot/angular2App/app/app.module.ngfactory

When I run "Run - Production" task I get this error

D:\Projects\Libs\Angular2WebpackVisualStudio\Angular2WebpackVisualStudio\src\Angular2WebpackVisualStudio> cmd /c SET NODE_ENV=production&& webpack -p --color
@@@@@@@@@ USING PRODUCTION @@@@@@@@@@@@@@@
clean-webpack-plugin: D:\Projects\Libs\Angular2WebpackVisualStudio\Angular2WebpackVisualStudio\src\Angular2WebpackVisualStudio\wwwroot\dist has been removed.
clean-webpack-plugin: D:\Projects\Libs\Angular2WebpackVisualStudio\Angular2WebpackVisualStudio\src\Angular2WebpackVisualStudio\wwwroot\fonts has been removed.
clean-webpack-plugin: D:\Projects\Libs\Angular2WebpackVisualStudio\Angular2WebpackVisualStudio\src\Angular2WebpackVisualStudio\wwwroot\assets has been removed.
Hash: 4f2f41544c1ee0ba4915
Version: webpack 2.1.0-beta.27
Time: 23676ms
+ 556 hidden modules

ERROR in ./angular2App/main-aot.ts
Module not found: Error: Can't resolve '../aot/angular2App/app/app.module.ngfactory' in 'D:\Projects\Libs\Angular2WebpackVisualStudio\Angular2WebpackVisualStudio\src\Angular2WebpackVisualStudio\angular2App'
@ ./angular2App/main-aot.ts 5:0-81
ERROR in [default] D:\Projects\Libs\Angular2WebpackVisualStudio\Angular2WebpackVisualStudio\src\Angular2WebpackVisualStudio\angular2App\main-aot.ts:7:35
Cannot find module '../aot/angular2App/app/app.module.ngfactory'.
Child html-webpack-plugin for "index.html":
+ 1 hidden modules
Process terminated with code 2.

Can someone help me? "Run - Development" currently works but I had problems with node-sass

Hi @Jeky11
try building the production build from the command line

npm install
npm run buildProduction

If the production build is successful, a aot folder will be created. You need the latest version of node and npm.
Greetings Damien

Thank you very much. It helped. I used Webpack task runner


Rickroll link in Readme doesn't work

https://github.com/leachim6/hello-world/commit/a5deb778ac9756b63bd3fd4ba7c71bea1d854890


Fontaine does not process fonts attached via Fontsource

🐛 The bug
When attaching fonts via Fontsource (4k stars on Github), a fallback font is added to font-family, but @font-face is not created for it.
🛠 To reproduce
https://stackblitz.com/edit/github-xyllwv?file=index.css
🌈 Expected behaviour
The Roboto font in the demo should have a fallback font, but it doesn't.
ℹ Additional context
https://github.com/Serator/fontaine-with-fontsource - additional example with SvelteKit.

want to add that this issue also seemingly applies to all fonts that get imported through npm packages
in my case, i'm importing fonts like this https://github.com/EmeraldSnorlax/website/blob/ef0378d1a5ed69c45577e70ccbc986f9c23dbd2c/src/routes/%2Blayout.svelte and fontaine doesnt see them at all


Polling Provider error

Bot cannot gather informations. Server is online and informations are provided by different other services.
PLAYER_COUNT_PROVIDER = steam-query
GAME_TYPE = dayz
GAME_QUERY_PORT = 2305
GAME_IP = MY-IPV4-SERVERADDRESS
Starting Discord Bot...
Logged in as ***bot#8811!
App setup done...
PollingProvider errored, retrying in 4 seconds for max 15 tries (1. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 6 seconds for max 15 tries (2. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 8 seconds for max 15 tries (3. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 10 seconds for max 15 tries (4. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 12 seconds for max 15 tries (5. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 14 seconds for max 15 tries (6. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 16 seconds for max 15 tries (7. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 18 seconds for max 15 tries (8. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 20 seconds for max 15 tries (9. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 22 seconds for max 15 tries (10. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 24 seconds for max 15 tries (11. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 26 seconds for max 15 tries (12. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 28 seconds for max 15 tries (13. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 30 seconds for max 15 tries (14. try). Error: Failed all 2 attempts
PollingProvider errored, retrying in 32 seconds for max 15 tries (15. try). Error: Failed all 2 attempts

Hi 👋 Sorry for not coming back to you any sooner. Could you please provide the server IP address you try to set the bot up for? :)


Categorical slot don't set option for values not explicitly defined

What problem are you trying to solve?
When writing stories around categorical slots, I don't want to have to write stories for the default value __other__ as well as stories for slot not set. Also don't want to deal with __other__ value in stories when it should never happen for my use case.
What's your suggested solution?
Provide an option for categorical slots that will not change the slot value when there is an attempt to set the slot to a value that isn't explicitly defined.
Examples (if relevant)
No response
Is anything blocking this from being implemented? (if relevant)
No response
Definition of Done
No response

Closing as a duplicate of #8755

I don't think this is a duplicate - #8755 is about representation of the __other__ value in stories that come from interactive learning, this one is about changing the underlying behaviour of categorical slots.

@rgstephens Does @melindaloubser1 's suggestion of using a custom slot suffice for this issue for the time being? (priortizing research's inbox for the next sprint)

I agree with @melindaloubser1 that this is not a duplicate and the customers original request but I also don't think it's a high priority since this can be addressed via slot validation.


useMutation doesn't work with async/await

urql version & exchanges:
version: 2.2.0
exchanges: [
dedupExchange,
cache,
errorExchange({
onError: (error: CombinedError) => {
// eslint-disable-next-line no-console
console.error('URQL ERROR', error);
},
}),
fetchExchange,
],
Steps to reproduce
  const onSubmit = async (data: PreregisterInput) => {
    await inviteWorkerToCompany({
      companyId,
      userToInvite: data,
    });

    if (inviteWorkerToCompanyResult.error) {
      toast.error(t('userAccount.inviteFailed'), {
        position: 'bottom-center',
      });
      console.error(inviteWorkerToCompanyResult.error);
    } else {
      toast.success(t('userAccount.inviteSuccess'), {
        position: 'bottom-center',
      });
      refetch?.({ requestPolicy: 'cache-and-network' });
      closeTopModal();
    }
  };

In the example above inviteWorkerToCompanyResult.error is undefined even tough in console I'm getting error. Transforming the code above to use promise chain resolves the issue and in
await inviteWorkerToCompany({
      companyId,
      userToInvite: data,
    }).then(result => { console.log(result) })

result.error has the error inside of it

Expected behavior
inviteWorkerToCompanyResult should have the same output as result in promise chain
Actual behavior
inviteWorkerToCompanyResult has the same result as result in promise chain

This is expected in React, the outer-closure will still be the one from the previous state, instead doing
    const result = await inviteWorkerToCompany({
      companyId,
      userToInvite: data,
    });

   if (result.error)

will work

@JoviDeCroock Thank you for your quick reply. One question. What is the purpose of in my case inviteWorkerToCompanyResult ? Seems quite useless

in your case it's useless yes but you can also handle these cases differently, i.e. use an effect to react to errors, ... in which it becomes part of the reactive cycle which isn't subject to this outer-closure issue as it is part of the render closure.


spec "architecture" command in App.build throws error when not using "x86_64"

At this point, the issue appears to be pyinstaller related:
https://github.com/machawk1/wail/issues/513
I switched from universal2 to x86_64 and it worked, and in switching back to universal2 the issue was gone. Not sure why this happens at this point. I also did not get this error in VSCode, only in PyCharm.

I switched back to the version of python that is installed with Xcode, located in /usr/bin/python3 (3.8) and it seems to work fine.


Ensure self-hosted runners have nix installed

We've learned that we can't run rooty things which means we can't installed needed binaries if they're missing. If only there was a package manager that we could use within another linux os ... ;).
If we had nix installed then we'd be able to re-work the CI to make use of it and then the self-hosted build runner would get much more use.
Expected Behaviour
Ability to use binaries not currently installed (or at at different versions) on the self-hosted build runners.
Current Behaviour
Can't build boots on the self hosted runner due to missing binaries.
Possible Solution
Ensure nix is available to the CI jobs.

looks like this is done


Update setup.py and requirements.txt to show correct dependencies

Python 3 is required in setup.py as of PR #152 .
I'm not sure how module dependencies should be handled. Why do they need to be listed in a setup.py or requirements.txt when there are obvious dependencies from the "import" statement?

This is complicated by readthedocs. On one hand we'd like to require the dependencies when installing; but on the other hand we don't want readthedocs to install all of the mocked dependencies. How do we do this right for both cases?


check on mobile and other platforms

Check the site looks good enough on safari, firefox, chrome, edge and mobile versions thereof

Some things do seem a bit wonky on my phone (Android 5, Icecat ~= Firefox)

h1 titles not centered?
small gap between title and header bar


Unify imports of hera.workflows and hera.workflows.models

Pull Request Checklist

[x] Fixes #800
[ ] Tests added
[x] Documentation/examples added
[ ] Good commit messages and/or PR title

It's challenging to know when to use from hera.workflows or from hera.workflows.models. This PR unifies the imports of the two into hera.workflows so that users can import both.
Questions for reviewers
Is this the right approach?

+1 to everything Elliot said. I'm not sold on this idea either and Hera classes behave very differently to normal generated pydantic classes. I feel like this will put us into a hole wrt backwards incompatible changes.

I do agree that mixing pydantic models with hera.workflows classes can cause some issues , such as compatibility breaks down the road in case a new hera class with the same name is implemented in the workflows folder.
However the problem still remains that there is no direct way to know which Argo object is available through a hera tailored class and which is only available as a pydantic model (or even just as an Enum). Since hera's proposal is to be an intuitive and easy to use yaml manifest replacement, ideally I'd like to be able to import and use any object in the yaml syntax in one unified way.

... create actual Hera classes for all the models that we think should have our syntactic sugar/helper functions (which could be all of them, could be some of them).

Even if there is no syntactic sugar or helper to add, could it be for all of them? An idea here, maybe you could extend the current PR to generate dummy classes for the autogen_modules.

Closing for now, let's discuss in the maintainers meeting. Maybe there's a world in which we autogen Hera classes "prepared" for syntactic sugar


CSP-803, Streaming is preview,fix sersion for SMM,SR

Added "PREVIEW" label to the streaming clusters
Fixed SMM (1.0.0 -> 2.1.0)and SR (4.0.0 -> 0.8.1) versions, from

Testing:
Checked out the changes manually on the UI.
Closes CSP-803

@akatona84 I added you just to check the version numbers.

Reopening on the rc-2.16 branch


Migration to new CDS-Beta API personal access token (for ERA5) tosses a ValueError

Since its September already, the CDS used for querying ERA5 will migrate to CDS-Beta (Please see this forum and the new CDS-Beta interface).
It requires updating the API credentials on the .cdsapirc file. However, upon updating the credentials and trying it on a new conda environment with Spy (SounderPy) ver. 3.0.4, it tosses an error message (most likely related to xarray package).
ValueError: found the following matches with the input file in xarray's IO backends: ['h5netcdf']. But their dependencies may not be installed, see:
https://docs.xarray.dev/en/stable/user-guide/io.html

Is there a way to resolve this issue? Btw, all dependencies were downloaded for the xarray, so as for Spy. So, its quite strange that it tosses an error message.

This issue has been resolved and updates have been made to SounderPy's get_model_data() function to accommodate the new CDS API update.
This fix will be implemented in the next release of SounderPy. Thus, I will close this issue.
For other readers, if you come across this issue because ERA5 data access is not working for you, note that you must update your ERA5 CDSAPI account and API access keys to the new CDSAPI Beta.


[Feature request] Update getStorybook for RN installation

Work summary
Depending on whether you are installing storybook inside CRNA or as a standalone app you get different result. This flow should be unified, so initial experience for the user would be easier.
I think default case should be that RN Storybook starts with onDeviceUI set to true and it should try to connect to the server, but if it fails it should start gracefully with disableWebsockets set to true.
The documentation should be updated to explain how to use storybook after the update (it would probably be same or very similiar to current storybook for crna installation).
Who to contact
You can contact me or anyone from contributors in slack.

Sorry if this isn't the right place. Feel free to delete this comment if it's irrelevant.
I needed this feature with Storybooks 3.4 so I implemented it with fetch in the App.js component:
App.js
import React, { Component } from "react";
import { getStorybookUI, configure } from "@storybook/react-native";
import { loadStories } from "./storybook/storyLoader";

configure(() => {
  loadStories();
}, module);

const storybookWebUIPort = 7007;
const metroPort = 8081;

// react-native hot module loader must take in a Class - https://github.com/facebook/react-native/issues/10991
// https://github.com/storybooks/storybook/issues/2081
// eslint-disable-next-line react/prefer-stateless-function
class StorybookUIHMRRoot extends Component {
  constructor() {
    super();
    // Inital port has to be null to prevent a 'websocket: connection error'
    this.state = {
      port: null
    };
  }

  componentWillMount() {
    // Check if storybook native web ui is running
    fetch(`http://localhost:${storybookWebUIPort}`).then((result) => {
      let port = metroPort;

      // if the storybook native web ui is up then use it
      if (result.status === 200) {
        port = storybookWebUIPort;
      }
      this.setState({
        port
      });
    }).catch((err) => {
      this.setState({
        port: metroPort
      });
      console.log(`StorybookNative Web UI is not running. It provides a web ui to navigate and focus on stories. To use it run 'yarn storybook-ui', open http://localhost:${storybookWebUIPort} and reload the app.`);
    });
  }
  render() {
    if (!this.state.port) {
      return null;
    }

    const StorybookUIRoot = getStorybookUI({ port: this.state.port, onDeviceUI: true });
    return <StorybookUIRoot />;
  }
}

export default StorybookUIHMRRoot;

Hey @willgriffiths. You are more or less correct. If you were using storybook v4 alpha version you can pass in disableWebsockets prop as true instead of using the port.
I am going to add this feature inside the getStorybookUI method itself so users wouldn't have to do anything about it.
Additional thing about this task is I want to make sure that default setup for storybook for all users would be same. Since now it is a little bit different (on expo you add component yourself, on rn standalone example it creates you a separate screen). We will use expo example as a default and explain how to enable it in most popular setups (expo, rn standlone, react native navigation).

#3903 will solve this.
It will simply not throw red screen anymore and display onDeviceUI by default.


comby: 1.7.0 -> 1.7.1

Description of changes
Release notes on GitHub

Fixes JSON output of -json-lines which previously emitted double-escaped values like \n instead of \n

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 175210 run on x86_64-linux 1

1 package built:

comby


supported nickname

支持 nickname
修改以 realname 从 config 取值
修改对 Tea 的引用版本为 0.0.6
修改对应的单元测试

Codecov Report

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

@@          Coverage Diff          @@
##           master    #93   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          73     73
  Branches       13     13
=====================================
  Hits           73     73

Continue to review full report at Codecov.

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


Refactor default theme

First of all, good work! This navigation is beautiful and really works out of the box with WordPress and our ultra minimal and modern air-light theme.
I'd like very much to contribute with my first issue. I noticed theme default base is really hard to understand because it contains

Too much nesting
Too specific selectors
Too much overrides with specificity, :not and !important that should be avoided
Unnecessary & and > in wrong places, they should be after { not before
Duplicate selectors

Stylelint with our pretty reasonable standards causes 631 errors. Had to put in stylelint-disable sh-waqar/declaration-use-variable, no-descending-specificity, selector-max-combinators, selector-max-pseudo-class, selector-max-class, selector-max-compound-selectors, selector-max-specificity, declaration-no-important, max-nesting-depth, no-duplicate-selectors for now.
For example selectors of this next secenario should be in one line because in-between there's no specifications, it's also way too specific:

So my suggestion is to simplify default theme structure by refactoring it completely. This would ensure people should have easy time creating their own themes. I personally had to do overrides because this overkill at the moment.
I used to nest too much in my past as well so I'm not blaiming anyone, we've all been there. I can gladly help in some point in the future, but right now I don't have enough time for anything else to bring this to your attention.

The problem is that the menu has many features and subnav possibilities and options, which are targeted by these very specific complex selectors. I understand you, at one time I've completely lost it and didn't know what is what anymore (I still don't) :D
The problem with these out of the box solutions that (try to) fit all situations is that there are just too many variations that could happen that we have to cover. I tried refactoring it once and this is what I've ended up with. I had to have opened like 10 tabs for all different situations to test against, it wasn't fun at all :D
I'm open for suggestions about the workflow.

Haha I understand your pain, I've been there myself as well. I may have some thoughts to this later...


bugfix on Number

Closes #29
Closes #30

I found one more bug while I was playing around: https://github.com/internet2-org/rust-aluvm/issues/32
will fix it in a follow-up PR

fixed #32
ready for review

Codecov Report

Merging #31 (e0de173) into master (3b16ef8) will increase coverage by 2.9%.
The diff coverage is 95.3%.

@@           Coverage Diff            @@
##           master     #31     +/-   ##
========================================
+ Coverage     9.3%   12.2%   +2.9%
========================================
  Files          18      18
  Lines        3770    3833     +63
========================================
+ Hits          350     468    +118
+ Misses       3420    3365     -55

Impacted Files
Coverage Δ

src/data/arithm.rs
17.9% <94.4%> (+17.9%)
:arrow_up:

src/data/number.rs
35.0% <100.0%> (+9.0%)
:arrow_up:

src/data/byte_str.rs
2.9% <0.0%> (+<0.1%)
:arrow_up:

Continue to review full report at Codecov.

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


Make charts expandable/collapsable

suggestion from @agstn

Functional Test: charts are now able to be expanded and collapsed
Pass


Create hello.txt

Please do not send pull requests to this docker/docker-ce repository.
We do, however, take contributions gladly.
See https://github.com/docker/docker-ce/blob/master/CONTRIBUTING.md
Thanks!

OK


[Feature request]: Doorlock T8520

Describe the solution you'd like
If we could get T8520 added for support that would be amazing :D
Thank you!

The integration is almost complete. Still a little patience...
Closed since already requested here: #89


Unable to extend DBContext table models using partial class with custom Properties

In MVC Core 2.1, extending a DBContext table model using another partial class causes an exception when attempting to load data from the database. This works in ASP.NET MVC Entity Framework.
In MVC Core 2.1 with a DBContext model, add another partial class with a new property
Run code to select all records from the database for this model
An exception is raised - System.Data.SqlClient.SqlException: 'Invalid column name 'ColumnName'
From a design perspective having used ASP.NET MVC I was expecting to be able to extend the class with my own properties that would be ignored by DBContext. I assume that EF6 as used in ASP.NET MVC keeps a separate store of information which it then uses to generate the C# code for the table data model. In working wit the database, only the defined columns are associated
I assume that MVC Core DBContext works differently, simply outputting the complete model from which all interaction with the database are performed. My adding additional properties, even to the partial class breaks this design. Seems a bit pointless creating partial classes for the Models in this case

@pixelda Partial classes are combined into a single class at compile time. There is no difference in the runtime class generated when compared to adding properties to a non-partial class. That is, partials are source code syntactic sugar.
DbContext typically works in the same way here between EF6 and EF Core when using code mappings. That is, if a new property is added to a class, then that property will be included in the model by-convention. If you were previously using a database-first workflow with an EDMX file to manage your database, then adding properties to entity types might have resulted in them being ignored by default.
To explicitly ignore properties when using code mappings, use either [NotMapped] or .Ignore in the fluent API. See https://docs.microsoft.com/en-us/ef/core/modeling/included-properties

@ajcvickers - Yes, it is always Database First for me. Forgot about the NotMapped. Thanks


Golie blyadi 3

Song Name
Golie blyadi 3
Artist Name
Detishlux
Source
Youtube
Youtube Link
https://youtu.be/rI7L7jXc6Dk?si=bNruk1x06s2sGuA8
Direct File Link
No response
Song ID
433947
Start Offset [ms]
No response
Extra
No response

reject
popular songs like "NK fracture" are too inconvenient to be replaced by smth unrelated and are therefore usually rejected.
Note that you can still use the song yourself, but it won't be public


Incorrect SFileInfoNameHash1 & SFileInfoNameHash2 being returned

Related to #311
Protected map Lusin2Rpg1.28.w3x
There are many fake files, I exclude them by doing a try/catch around my extraction logic & checking for a 0-byte file after extraction.
There are many pseudo filenames for real files that return the same hash values (which are also wrong).
These are real valid files that can be extracted & opened.
One Example:
File00024483.blp
SFileInfoHashIndex = 18
SFileInfoNameHash1 =<PHONE_NUMBER>
SFileInfoNameHash2 =<PHONE_NUMBER>
File00005745.mp3
SFileInfoHashIndex = 20
SFileInfoNameHash1 =<PHONE_NUMBER>
SFileInfoNameHash2 =<PHONE_NUMBER>
The correct listfile names for these are:
File00024483.blp = ReplaceableTextures\CommandButtons\BTNHaboss79.blp
File00005745.mp3 = war3mapImported\KoruneF.mp3
If I calculate the hash for these file names, I believe they should be:
ReplaceableTextures\CommandButtons\BTNHaboss79.blp
SFileInfoNameHash1 =<PHONE_NUMBER>
SFileInfoNameHash2 =<PHONE_NUMBER>
war3mapImported\KoruneF.mp3
SFileInfoNameHash1 = 556665874
SFileInfoNameHash2 = 476359262
Notes:
SFileOpenFileEx, SFileExtractFile, & SFileHasFile all work fine on both the psuedo file name & real listfile name
When I use the real listfile name, the hashIndex changes. Even though the hashindex changes, the actual file contents are the same regardless of extraction with PseudoFileName or real list file name.

Some of the fake entries can be resolved using an external list files, and will successfully extract, but the binary data is garbage.
For example:
(PC)WorldEditMenu.html
I'm researching this more to see if I can fix it on my end with some Deep File Verification. Maybe not StormLib's job to handle this scenario.

What you see is a fundamental problem of opening file by pseudo-name.
Unlike classic file open (FileName --> NameHash+HashTableIndex --> BlockIndex --> FileData), opening by pseudo-name goes directly into BlockIndex. Yes. The number in the name ("File00024483.blp" --> 24483) is the decimal block index. The extension is provided only when StormLib is able to determine it by file content, but it's generally ignored by SFileOpenFileEx.
Now we opened a file by block index, where to take that damn hash index?
When a file is opened by pseudo-name, StormLib tries to determine the hash index by searching which hash entry points to block table entry whose index is given in the pseudo name. This generally works well, except the case when MPQ has cross-linked files (multiple files names pointing to the same file data).
Cross-linked files may be legal (why could a file data have multiple names, right?) or malformed (MPQ protectors slowing down MPQ opens).
Now I guess that the best (or "least-worst", if you want) way to fix it is to not return any hash entry when those two conditions are met:

A file is open by pseudo-name
Multiple hash table entries pointing to that block entry.

Thanks for the explanation. I don't think this is a bug in StormLib, nor should StormLib handle it any better/differently, so I'm closing it.
I've been able to work around the issue by coding my own custom filename & hash verification methods. It's pretty complicated & WC3 specific. I'm basically regex scanning all extracted file contents for filenames & checking against SFileHasFile.
In my case if there are 2 hash entries pointing to 1 block I'd prefer to get ALL the possible hashes for a fileIndex, rather than 1st or none. But, there's no reason to make a breaking change to the StormLib API based on my specific use case & corrupted map. I can workaround the problem.
Thanks for the help!

I made the fix described above in this PR: https://github.com/ladislav-zezula/StormLib/pull/316
Callers of SFileGetFileInfo(hFile, SFileInfoNameHash1, ...) must test the result of the call.


Switch mode to geofencing in gui

Is it possible to switch with the gui to geofencing? I can only switch from home to away and back.

But apart from my question. Great work :-)

sadly no, without building a custom frontend card, we are stuck with existing options. Disarmed, armed home, armed away. For the rest, you can use service calls.

for my case, I use HA geofencing to change from home to away and vice versa.  Use this for simplisafe and eufy.  That way I do not use the eufy app geofencing.  Would that work for you?

I activate this addon in my HA. Now I activate "away" at 18:00 and then activate "geofencing"

for my case, I use HA geofencing to change from home to away and vice versa. Use this for simplisafe and eufy. That way I do not use the eufy app geofencing. Would that work for you?

I activate this addon in my HA. Now I activate "away" at 18:00 and then activate "geofencing"  at 9:00 in the morning. This works for my use-case.
@MechEng70 : How do you do that? Can you explain your automation?

Here are my automations:
For setting it to away mode when both are not home:
alias: SentryEye - Set Away
description: ''
trigger:
  - entity_id: group.occupancy
    platform: state
    to: not_home
condition: []
action:
  - data:
      mode: armed_away
    service: aarlo.alarm_set_mode
    entity_id: alarm_control_panel.aarlo_sentryeye
  - delay:
      hours: 0
      minutes: 0
      seconds: 15
      milliseconds: 0
  - service: alarm_control_panel.alarm_arm_away
    target:
      entity_id: alarm_control_panel.sentryeye
mode: single

For setting to home mode when both are home:
alias: SentryEye - Set Home
description: ''
trigger:
  - entity_id: group.occupancy
    platform: state
    to: home
condition: []
action:
  - service: alarm_control_panel.alarm_arm_home
    target:
      entity_id: alarm_control_panel.sentryeye
mode: single

Set to away mode when the house is set to secure from google (this uses a variable from my ISY hub):
alias: SentryEye - Night Time
description: ''
trigger:
  - entity_id: sensor.s_securehome
    platform: state
    from: '0'
    to: '1'
condition: []
action:
  - service: alarm_control_panel.alarm_arm_away
    target:
      entity_id: alarm_control_panel.sentryeye
mode: single

This resets the system to home mode at 5am.  I am looking to change this to when my phone alarm is dismissed and I am home:
alias: SentryEye - Early Morning Reset
description: ''
trigger:
  - platform: time
    at: '05:00:00'
condition:
  - condition: state
    entity_id: group.occupancy
    state: home
action:
  - service: alarm_control_panel.alarm_arm_home
    target:
      entity_id: alarm_control_panel.sentryeye
mode: single

@MechEng70 So ...in the night you only arm the system from 1 to 5? Have I understood this correct? And otherwise you use the away state of your two mobile devices?

@r77s not quite.  The 1 you are probably looking at is a state variable that changes based on Googles interaction with my ISY hub.  Basically the way it works is that my SO or I say "Ok Google Good night" and the routine changes a state variable in the ISY from 0 to 1 and the HA catches that change.  The HA automation then is triggered to switch it to away mode for the night.
You are correct that the state of the mobile devices controls the other automations.

@MechEng70 ah ok. You arm the system with a voice command. That's a good idea.


Add more LLMs integrations

Description
At the current date, the only available integration for OpenAI's Large Language Model (LLM) is with ChatGPT. However, it would be highly beneficial to expand this integration to other platforms such as Azure or OLLAMA. This expansion would allow users to leverage the capabilities of LLM in a wider range of applications and environments, enhancing flexibility and accessibility.
Proposed Solution
Integrate OpenAI's LLM with Azure and/or OLLAMA to enable users to utilize the model within these platforms seamlessly. This integration could involve developing APIs, SDKs, or plugins that facilitate easy integration and interaction with LLM.
Expected Benefits

Enhanced Accessibility: Users will have the flexibility to access LLM through multiple platforms, catering to diverse needs and preferences.
Improved Workflow Integration: Integration with Azure and OLLAMA will streamline workflows for developers and researchers, allowing them to leverage LLM within their existing environments.
Expanded User Base: By integrating with popular platforms like Azure and OLLAMA, OpenAI can reach a broader audience, fostering greater adoption and utilization of LLM.

Community Feedback
Please share your thoughts and feedback on this proposed integration. Your input will help us prioritize and shape the development of this feature.

My suggestion is to allow setting base_url in OpenAI and make the make the model Into<String> as ollama supports Open AI Compatibility. keep_alive is another feature you probably want to add since ollama can use that to detect when to unload the model.

@prabirshrestha
Some Options

Maybe we can add the keep alive to the llmoption? src/language_models/options.rs.
Crate another with_keep_alive in the self builder of opens ai
Copy the open ai implementation to another struct Ollama and add the keep alive in the self builder

What are your thoughts 😄

I don't have a strong opinion for now. Probably worth seeing what other open api compatibility APIs adds to such as https://edgen.co. I'm ok on waiting for this as I'm not in rush to use this feature. I'm also waiting for the embedding api to support compatibility and see where it makes sense.


os-ddclient needs forced update interval setting

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] When the request is meant for an existing plugin, I've added its name to the title.

Is your feature request related to a problem? Please describe.
Our dynamic dns (dy.fi) provider expires the domain name "lease" in 7 days if it's not force updated before that. Currently there seems not to be any setting for os-ddclient to make that happen and my dns leases just expire.
Describe the solution you'd like
In the ddclient account settings (or global settings if per account is impossible) have "force update interval" field that takes time interval as input, either just seconds, or number and dropdown to choose unit (secs, hours, days), and when time is due, fire the ddns update link unconditionally.
Describe alternatives you've considered
I don't think there exist much alternatives for this. Forced update is needed by plenty providers so they don't hold abandonded domain names indefinitely.
Additional context
I know similar ticket is https://github.com/opnsense/plugins/issues/2862 by someone else but it was deemed not following template so I decided to make proper one, and also slightly different take, time is factor on mine.

I'll plus one this. The setting does exist as the client will update at 25 days if there has not been an IP change. See here for where the settings exist in the upstream.

ddclient 1.8 which is available on latest opnsense has now this on changelog:

Add a force action available via cron

but at cron in web-ui such option still isn't available on the list, and I think there is no "parameter" to give, as https://github.com/opnsense/plugins/blob/stable/22.1/dns/ddclient/src/opnsense/service/conf/actions.d/actions_ddclient.conf lists force as separate action from restart.
So it seems we're nearly there, but last step is missing (actual defined cron job).

System: ->Settings:-> Cron [+]

I see that option, but it doesn't force update anything, neither does applying parameter "force" there.. One can restart the service as many times as one wants to, but it only says "no need to" in logs. There is indeed new "force" directive in mentioned link that defines ddclient daemon "options", but it is separate from restart :)

If „ddclient -force“ doesn’t do what you expect I’m not sure what we can do about it.

Manually running ddclient -force withing ssh-conole works, so far I haven't managed to make same happen within web-ui, be it stupid PEBKAC or not.
root@router:~ # ddclient -verbose
SUCCESS:  <xxx>.dy.fi: skipped: IP address was already set to <y.y.y.y>.
root@router:~ # ddclient -verbose -force
INFO:     forcing update of <xxx>.dy.fi.
INFO:     setting IP address to <y.y.y.y> for <xxx>.dy.fi
UPDATE:   updating <xxx>.dy.fi
CONNECT:  www.dy.fi
CONNECTED:  using SSL
SENDING:  GET /nic/update?system=dyndns&hostname=<xxx>.dy.fi&myip=<y.y.y.y> HTTP/1.0
SENDING:   Host: www.dy.fi
SENDING:   Authorization: Basic <pw>
SENDING:   User-Agent: ddclient/3.9.1
SENDING:   Connection: close
SENDING:
SENDING:
RECEIVE:  HTTP/1.1 200 OK
RECEIVE:  Server: nginx/1.10.3 (Ubuntu)
RECEIVE:  Date: Sat, 09 Jul 2022 21:30:47 GMT
RECEIVE:  Content-Type: text/plain;charset=UTF-8
RECEIVE:  Connection: close
RECEIVE:  Last-Modified: Sat, 09 Jul 2022 21:30:47 GMT
RECEIVE:  Cache-Control: no-cache
RECEIVE:  Pragma: no-cache
RECEIVE:
RECEIVE:  good <y.y.y.y>
SUCCESS:  updating <xxx>.dy.fi: good: IP address set to <y.y.y.y>

Forgotten apply in cron GUI. If you run „configctl ddclient force“ and it works that would show it‘s the cron setup, otherwise another issue.
the no update message probably comes from the other ddclient running in the background.

Tried to setup cron job for ddclient with force option, which didn't work, but I noticed that it will set following line to cron job for nobody:
59	13	*	*	*	/usr/local/sbin/configctl -d ddclient restart force
So, I think the restart parameter is run first and force will be omitted. Should there be another option in the web UI for setting custom parameters?

Indeed me neither have gotten this to work from WebUI :/

The cron job is "Force ddclient update". It's not so complicated really.

OK, I see. Definitely it would be simple, if that cron job would be available. At least in my system it is not:

Type | opnsense |
-- | -- | --
  | Version | 22.7.6 |
  | Architecture | amd64 |
  | Flavour | OpenSSL |
  | Commit | 2eef9015b |
  | Mirror | https://pkg.opnsense.org/FreeBSD:13:amd64/22.7 |
  | Repositories | OPNsense |
  | Updated on | Fri Oct 14 19:58:35 EEST 2022

Fair enough, typo then https://github.com/opnsense/plugins/commit/0fff7f0581c


Feature request: skip if compressed content is larger than original

Add something like:
if (size >= oldSize) {
  return
}

at:
https://github.com/vbenjs/vite-plugin-compression/blob/077eff37f45f12896326d687aa0e08f99b2b7a07/packages/core/src/index.ts#L99
To avoid deleting the original file if it will be skipped because of compressed size being larger, move these lines:
https://github.com/vbenjs/vite-plugin-compression/blob/077eff37f45f12896326d687aa0e08f99b2b7a07/packages/core/src/index.ts#L89-L91
after the suggested check code above.
See #36 for fix.

I think you can try vite-plugin-compression2.  I had to reimplement a version :(

Thanks for the tip! Does vite-plugin-compression2 support the option to skip the compressed version if it is larger than or equal the original version?

@vHeemstra  Of course. size check
By the way. vite-plugin-compression2 has full unit test and e2e test. And it is consistent with the experience of the webpack version

I switched to your updated package! It is indeed faster. :)
It works great, but I'm missing the ability to log the processed files (as this original package does).
I just made a PR adding the feature to skip compression if the compressed file size is larger than (or equal to) to original file size.

@vHeemstra  Ok. i will review your code


Contact section added

I have added a section for contact details which includes our slack, discord and GitHub links. This PR aims at closing #18

The section looks like this

let's make this draft PR as if we merge #17  this won't be relevant anymore

A similar kind of layout could be used in the footer.

@NidhiKJha review required

@NidhiKJha Sure, I will make the changes to the PR. Thank you !

@NidhiKJha I have made the suggested changes :)

Awesome! Thanks :)


How to update Torrents List?

As well as it does not give more than 30 Search Result.

When you scroll to the bottom, it will automatically fetch for the next page.


terrascan: 1.18.2 -> 1.18.3

Diff: https://github.com/accurics/terrascan/compare/refs/tags/v1.18.2...v1.18.3
Changelog: https://github.com/tenable/terrascan/blob/v1.18.3/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 248671 run on x86_64-linux 1

1 package built:

terrascan


Add version to a txt file for github and assetstore

Currently I do not know which version of Mirror I am getting from github or the Asset Store. I would like to add the version number to my Insight addon.

Asset store version is always the version from the day that it says on the asset store (the one from 1st of each month).
As for Github version, if you click on releases then you can see a version number: https://github.com/vis2k/Mirror/releases

Can we get a simple text file though. It seems excessive to go manually look up by date. Never done that for anything else

Ideally we should have it put the version number in the AssemblyInfo. That would mean just one needs to hover over the DLL and it'll say "1.0." or "0.".
If you enable "Show Debug Messages" you will get a line saying "Mirror version Current"... maybe we could make that reflect the build number?

Since the builds are done by a robot. What is the painless to integrate with the automation?

that is a good point,  the version is in the dlls,   right click on any dll and see the information in it.


QT plugins directories not copied to VisIt install plugins directory

Describe the bug
I did a make install -j 2 after building VisIt and when I tried to run VisIt, I received an error Qt: Warning: Could not find the Qt platform plugin "xcb" in "" . I did an export QT_DEBUG_PLUGINS=1 to get more information and discovered the QFactoryLoader was looking specifically in the VisIt install plugins directory (and I believe 1 or 2 others) for the xcb stuff. Once I copied the directories in the QT plugins directory to the VisIt plugins directory that was created after doing the make install everything worked.
I don't remember this being an issue with earlier VisIt releases. I checked an old VisIt install and don't see anything QT related in the plugins directory.
TP library build command:
build_visit --build-mode Debug --makeflags -j16 --no-thirdparty --no-visit --cmake --python --vtk --qt --qwt --boost --mpich --adios --adios2 --advio --boxlib --cfitsio --conduit --gdal --h5part --hdf5 --cgns --netcdf --mfem --silo --szip --icet --zlib --xdmf --tbb --thirdparty-path /home/kgriffin/VisIt/third_party/3.3.0

VisIt build command:
cmake -DCMAKE_BUILD_TYPE=Debug -DVISIT_INSTALL_THIRD_PARTY=ON -DVISIT_BUILD_ALL_PLUGINS=ON -DCMAKE_INSTALL_PREFIX=/usr/local/visit ../src

Desktop

OS and version: Ubuntu 20.04.5
VisIt Version: 3.3.0 and 3.3.1

Additional Info: The QT plugins directories (platforms and xcbglintegrations) get copied to linux-x86_64/lib/qtplugins during make install. The QFactoryLoader is expecting them in linux-x86_64/plugins.

@griffen28 what it the contents of qt.conf in linux-x86_64/bin?

Here's what's in the qt.conf file:
[Paths]
Plugins=../lib/qtplugins

I think the issue is on my end. This was working correctly in 3.1.4 the same setup for QT. Not sure what got messed up.

Another thing to check would be any environment variables related to QT.


Listening to shoutcast audio - Title from stream

Is it possible to automatic MetadataTitle setting from stream when source is radio stream with metadata included?

This would be better asked on the code repository than the docs. That repo is https://github.com/CommunityToolkit/Maui


Implemented some code to handle multiple peripherals

Code to make it possible to launch two different services from the list activity. Please review @jyasskin @scheib

LGTM


(wip): Poc common error handler for apollo link in liikunta

Description
Looks like I finally nailed all the problems with the error pages.

First off, the ErrorBoundary was in a wrong place. Because ErrorBoundary component still needs to show header and footer sections, it needs to be inside the ApolloProvider and CMS Provider, not the outmost part of the _app.
500.tsx didnt work, it always failes to getStaticProps. The reason is a bug in nextjs when middleware.ts is implemented. There was an actually an open issue for that: https://github.com/vercel/next.js/issues/38762
Fortunately this problem can be fixed by simply not using the nextjs autosupported 500-page at all. If the page doesnt exist, then nextjs uses  _error.tsx instead.
So _error.tsx needed to be implemented due to 2) but also because client-side errors (ie. graphql network errors) always defaults to it on nextjs. Next open issue was that the translations were broken on _error page: https://github.com/i18next/next-i18next/issues/1020
There is no fix for that either, so only thing to do was to instantly redirect to some different page, so it will always redirect now to the error.tsx which mimics the original 500 page.

Wohoo, everything works now correctly!
how to test:

start script to run the apollo server locally yarn docker:graphql-router:hobbies:serve from root of the monorepo
run yarn build-fast under app/sports-helsinki
run yarn start
go to: http://localhost:3000 and browse around
stop the apollo server
browse some more
-> error.tsx page should pop up

Issues
Closes
DEV-XXX:
Related
Testing
Automated tests
Manual testing
Screenshots
Additional notes

EVENTS GRAPHQL PROXY is deployed to platta: https://events-graphql-proxy-pr233.dev.hel.ninja :rocket::rocket::rocket:

VENUE GRAPHQL PROXY is deployed to platta: https://venue-graphql-proxy-pr233.dev.hel.ninja :rocket::rocket::rocket:


fix(selectors): handle when there are a unique selector

Hello :)
Some time we can edit chrome generated selectors, that's means, the result of the selectors in the json file is a Array<string> instead of Array<Array<string>>
More about selector types in replay repo
Example in a video:
https://github.com/cypress-io/cypress-chrome-recorder/assets/8685132/6721e734-6a79-4708-8664-022e576c3de0

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

@jennifer-shehane Hi,
Is there any news for this?


sift installation issue Ubuntu 20.04 on AWS EC2

AWS EC2 base image ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220419
EC2 m5.xlarge 100GB EBS
Steps followed for SIFT installation https://github.com/teamdfir/sift-cli#installation
After execution of all the steps I receive this at the end of sudo sift install
`sudo sift install

<EMAIL_ADDRESS>sift-version: notinstalled

mode: desktop
Installing and configuring SaltStack properly ...
downloading v2022.01.22

downloading sift-saltstack-v2022.01.22.tar.gz.asc
downloading sift-saltstack-v2022.01.22.tar.gz.sha256
downloading sift-saltstack-v2022.01.22.tar.gz.sha256.asc
downloading sift-saltstack-v2022.01.22.tar.gz
validating file sift-saltstack-v2022.01.22.tar.gz
validating signature for sift-saltstack-v2022.01.22.tar.gz.sha256
extracting update sift-saltstack-v2022.01.22.tar.gz
performing update v2022.01.22
Log file: /var/cache/sift/cli/v2022.01.22/saltstack.log

Running: /etc/sift-version
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/sift-cli/sift-cli.js:556:23)
at ChildProcess.emit (events.js:400:28)
at maybeClose (internal/child_process.js:1058:16)
at Socket. (internal/child_process.js:443:11)
at Socket.emit (events.js:400:28)
at Pipe. (net.js:686:12)`

Ran sudo apt-get update
Hit:1 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 https://download.docker.com/linux/ubuntu focal InRelease
Hit:5 https://repo.saltproject.io/py3/ubuntu/20.04/amd64/3004 focal InRelease
Get:6 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:7 http://ppa.launchpad.net/gift/stable/ubuntu focal InRelease [18.0 kB]
Hit:8 http://archive.ubuntu.com/ubuntu focal InRelease
Get:9 http://archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:10 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease
Hit:11 http://ppa.launchpad.net/sift/stable/ubuntu focal InRelease
Fetched 246 kB in 1s (231 kB/s)
Reading package lists... Done
Ran sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
If I try running sudo sift install below is what I get

<EMAIL_ADDRESS>sift-version: v2022.01.22

mode: desktop
SIFT already installed, please use the update or upgrade command

If I try running sudo sift update

<EMAIL_ADDRESS>sift-version: v2022.01.22

mode: desktop
downloading v2022.01.22

Goes through updates and then at the end...
>> Running: /etc/sift-version Update returned exit code not zero Error: Update returned exit code not zero     at ChildProcess.<anonymous> (/snapshot/sift-cli/sift-cli.js:556:23)     at ChildProcess.emit (events.js:400:28)     at maybeClose (internal/child_process.js:1058:16)     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
What is the issue here? Anything in specific that can give me a clean install would be very helpful. Thanks.

Hi @abanerjee-svmk can you provide the saltstack.log file, it may contain some useful information to resolve the issue. As well, there is already a SIFT AMI on the AWS cloud, so you might find that useful as well.

Thank you. Will take a look at the AMI. Attaching log.
saltstack.log

We ended up using the SIFT AMI. Thank you.


Migrate datetime chooser init script to Stimulus w-date

Avoid all need for Telepath widgets for datetimepicker, remove all inline script usage, replace with a single Stimulus controller 'w-date'
Refines 'soft' focus approach (which just did not focus on datetimepicker at all) with a DOM event / preventDefault approach so that we can use similar functionality without needing the overhead of a Telepath instance for just this behaviour. Add unit tests for this new Telepath widget behaviour
Ensure that Block variants use the same HTML (which will now include autocomplete off)
Ensure that options cannot override core functionality (hideCurrent, change event dispatch)
Split out date compare into own util (with tests)
Add unit test functionality to cover all datetimepicker usage scenarios
Remove the need for a dedicated datetimepicker JS import
Support existing wagtailConfig global usage
Fix console error when running widget unit tests (global scrollTo not provided by JSDom)
Find another test case to check the media inheritance approach as no longer needed for Admin date widgets
Fixes #10260

Implementation & testing notes

Tested on Safari 16 (a very small flash of the widget shows in Safari), Firefox 101, Chrome 111. Tested with macOS voiceover on all browsers.
The soft focus approach works better than before with making the actual date picker the 'next' keyboard focusable target and correctly reads the context of the container to screen readers.

This is now ready for review.

Rebased with upgrade considerations moved to 5.1 release notes.

Fixed up the additional failing tests - should be good now.

Rebased

This has not had a review yet but I have been thinking about the previous approach and found a much simpler solution for the 'soft' focus for use in the date picker.
This now avoids any <100ms flash of the datepicker being open in Safari and overall is a cleaner solution in the code.
I also reverted the removal of the soft focus call as this is a documented approach. I have opted to NOT document the new Custom Event dispatching as it will be for default widgets only and is not something that can be easily implemented at the top level usage of calling focus.
Would love to see this get a review when someone has a chance, I feel this is a more accessible/secure, simpler and hopefully more maintainable solution. Of course happy to take feedback and push back on the implementation.

no problems, I knew that was coming at some but but still assumed we would want the basics in place to hook in the JS changes/reduction when it came.
I do think there would be a desire from those working with Wagtail to opt for custom date widgets and assumed we would likely want to support that in some basic way.
If we are close to implementing the new approach, sounds good. If we feel it's still a release or two away, I would like to suggest we do review this PR for merging as it is one of the largest sources of inline script tags.
Happy with whatever we do here. Feel free to close this PR if it's not something we want to merge at this time though.

@laymonage & @thibaudcolas - a proposal for a different tact for date pickers, would love your thoughts.

move ahead with this PR, I can review and revise based on the cancelled feedback.
I add a new setting, something like wagtail_legacy_date_fields, this will be set to True for 5.1 with release notes about this config, ready to change the default to False in a future release.
I adjust the JS to load Async, dynamic require, only if the controller loads on a page and the legacy approach is true.

This gives us the benefits of being able to pull out critical path inline scripts, gives us time to confirm the native field approach and also paves the way for being closer to removing insert_editor_js.
We can set this config to False in bakerydemo, Guide site and maybe the Wagtail website. Plus gives some in the community to trial the approach.
If we realise we do need some JS, we have the Controller scaffold to build on. If we simply want to make it easier to BYO date widgets, we can change the controller to be a basic skeleton.
I'm probably a bit biased, having worked on this for a while, but do want to push a bit on giving us all time to fully move away from the xdsoft code but also give us a nice win for CSP, JS loading and accessibility options.

Rebased/resolved conflicts.

@lb- Thibaud and I have gone back and forth on this a few times, and I think we were still leaning towards completely replacing the inputs to the native browser inputs and making sure that we iron out any issues before merging, as opposed to having the old one as fallback in case there are issues with the new implementation. Even without a fallback, reviewing this PR is quite non-trivial and since we're going to replace it soon anyway, we feel it'd be better to focus our time on the new implementation instead.
It does sound a bit too optimistic to think that we'll be able to cover any issues before the change is released, though. That said, we still have the option to release bug fixes, so I think some friction in there is worth compared to maintaining two different implementations plus the code to handle the switch between the two.
I'm planning to pick the new implementation up in 5.2, and in the mean time I think you could hold off from continuing any work on this PR. Sorry we didn't get to review this, but hopefully the change is for the better.

@laymonage thank you, I'm more than happy to align with this direction. Thanks for getting back to me on this.
I'll close this PR and the related isssue and add some notes where needed.

Closing as per comment above, we will not be taking this approach for the date pickers.


Check if a service has already been restarted (Fixes #1338)

Thanks @codeswhite and Nissar @funilrys.
Merging!

@codeswhite and Nissar @funilrys, along with @XhmikosR, the great work you've done recently on code prompts me to make the latest a "minor" release, as opposed to a "patch" release.
Therefore we are now at Release 2.70 from Release 2.6.29.
THANK YOU!


Cannot build latest Extlib - unimplemented methods, has a dependency changed?

See screenshot. It's wanting to implement abstract method CommonDataSource.getParentLogger(). I'm using "maven install" in command line in extlib/lwp folder.
Is CommonDataSource in the m2 repository, and has it changed recently? It sounds like Maven is picking up a different version of that class.

Are you building against Java 7 possibly?

Thanks, Brian, that was exactly the reason. I had a more recent version of Java installed for other work.
The problem with building in Eclipse looks to be the version of m2e plugin doesn't come embedded with Java 6 any more, which is why I was getting a message about UnsupportedClassVersionError. The solution was on StackOverflow, as ever http://stackoverflow.com/questions/31163198/compile-maven-projects-with-jdk-1-6-in-eclipse-mars.


[Proposal] Collapsible pp details design

Relates to: #71, #116

I think it could be improved a bit more...

have you tried having it be [number] + aim instead of aim + [number]?
ie:
89.09 aim
69.04 speed
87.92 accuracy

maybe it works/looks better?

idk if you've been waiting for a response from me or something else, but I definitely think the second one looks better


Location and description of import_map.json

.vscode/import_map.json is used in deno.json as well as .vscode/settings.json.
If deno.json uses it, I thought it was fine to place it in root.
Even if not, I felt that the following notations should be eliminated.
  "scopes": {
    "THIS FILE EXISTS ONLY FOR VSCODE! IT IS NOT USED AT RUNTIME": {}
  },

https://github.com/denoland/fresh/blob/main/.vscode/import_map.json#L2-L4

Closing as we removed it in the Fresh 2 codebase.


how do I connect a non-xiaomi BLE device?

I have a nordic thingy52, which has a lot of sensors and transmits their values via BLE, in addition there is a built-in microphone and speaker, I would like to connect it to HA, via Xiaomi Gateway3, is it possible?
https://www.nordicsemi.com/Software-and-tools/Prototyping-platforms/Nordic-Thingy-52

Third party Bluetooth don't surprised. It's technically very difficult

а это поможет?
https://github.com/wlgrd/thingy52_homeassistant

There are no such utilities on the hub. There is a completely different architecture

жаль, железка очень мощная, можно ее использовать как сенсоры, подключить к ней исполнительные устройства (есть 4 мосфета), да еще и общаться через нее с умным домом голосом...

а gateway3 какие данные по BLE видит? по идее он должен сканировать эфир и спариваться со всеми из белого списка и считывать GATT характеристики.

Я не специалист по BLE. И на данный момент вся логика спрятана внутри ПО от Xiaomi. Что там происходит - понять трудно

@AlexxIT many thanks for this great project.
I have a question related to the discussion here:
I understand that it is difficult to add a support for a third-party BLE device; however, is there a chance that what I'm looking for might be easier? I want to control a Switchbot device via BLE using the Xiaomi Gateway 3. It doesn't require pairing, as I understand, and it's as easy as in here: https://github.com/cagnulein/switchbot_press
Do you think it is possible? I'll be happy to contribute and code it myself, if needed, but first I wanted to get your opinion.
Thanks again!

@AlexxIT many thanks for this great project.
I have a question related to the discussion here:
I understand that it is difficult to add a support for a third-party BLE device; however, is there a chance that what I'm looking for might be easier? I want to control a Switchbot device via BLE using the Xiaomi Gateway 3. It doesn't require pairing, as I understand, and it's as easy as in here: https://github.com/cagnulein/switchbot_press
Do you think it is possible? I'll be happy to contribute and code it myself, if needed, but first I wanted to get your opinion.
Thanks again!

@alonl previously you need disable default Xiaomi Bluetooth utility on gateway for free access to BT chip. Then write your own code for MIPS arch to handle work with chip.
I think better to find other solutions to handle third party Bluetooth devices.

@alonl previously you need disable default Xiaomi Bluetooth utility on gateway for free access to BT chip. Then write your own code for MIPS arch to handle work with chip.
I think better to find other solutions to handle third party Bluetooth devices.


Chrome/Safari can't handle jQuery in State.data

When asigning a jQuery object to State.data via
History.pushState({my_oject: $('body')}, "title", "http://url.com");

Chrome/Safari throw "TypeError: Converting circular structure to JSON" exception. Firefox processes the request just fine (if you've implemented my fix in issue #93).
This happens because History.getStateString invokes JSON.stringify(cleanedState). I understand this is only used in History.getIdByState help identify unique states.

This is still happening for me using the jquery html4+html5 bundle. Though I'm not sure the native history API lets you store anything beyond a string as a key/value in the state object in any case.

I use native version (with Prototype.js) -- \balupton-history.js-40489d1.zip\balupton-history.js-40489d1\scripts\bundled\html4+html5\native.history.js.
I've got "Converting circular structure to JSON'' error in Chrome (v17) for my site.
I've got "Out of memory" error in IE8.
It works fine in Firefox (v8).


交互可能存在问题

Description
当我测试数据库连接,无论成功还是失败都是跳转页面,导致看不到错误信息
Steps to reproduce

docker 日志

ILLA Builder Version
最新
Browser
No response
Operating System

[ ] macOS
[X] Windows
[ ] Linux

Additional Information
No response

It`s an internal server error in the docker logs. We have fixed it by pushing a new illa builder docker image. Maybe, u should deploy a new one after removing the old one.

It`s an internal server error in the docker logs. We have fixed it by pushing a new illa builder docker image. Maybe, u should deploy a new one after removing the old one.

有另外一个小问题，如果不输入端口号，点击测试连接会重定向到500页面，点击创建资源会提示输入端口号。

It's a display error; we'll fix it as soon as possible.

It is already fixed in v1.1.1.


Passing text to default slots

Hey all, so I have a very simple component with a default slot, like so:
<template>
	<button>
		<slot></slot>
	</button>
</template>

And would use like so:
<app-button>My Button</app-button>

How can I test that the My Button text passed to the component's default slot is rendering correctly?
I have the below unit test currently, which is working only because I've wrapped the My Button testing text in a span element, as otherwise I'm getting a Component template requires a root element, rather than just text. error.
import { mount } from 'vue-test-utils'
import appButton from '@/components/app-button/app-button'

describe('app-button.vue', () => {
	it('values passed to slots should render correctly', () => {
		const wrapper = mount(appButton, {
			slots: {
				default: 'My Button'
			}
		})
		expect(wrapper.find('span').text()).toBe('My Button')
	})
})

How would I modify this so I can simply just test that <app-button>My Button</app-button> works, without having to wrap My Button string in a span? I apologize if this seems a stupid question, but I've read the docs and can't quite find a way to cover this very simple case. Thanks.

There actually isn't a way to do this right now. Perhaps we should think about adding it to the slots API. What do people think?

In that case, I look forward to seeing this implemented. Passing text to slots is quite a common use case, especially with simple, dumb components. 😃

This has been added and will be released in the next beta version 🙂

Released in 1.0.0-beta.7 🙌

we need to add this to docs

I will add document about this within 3 days.