Typo in quiz on page /04-fode-2.ipynb

In the first question of the last quiz, I believe there is a ",_" missing when getting the meshgrid. The correct code would be:
a = np.linspace(0, 5, 2)
b = np.linspace(5, 10, 3)
c = np.linspace(10, 15, 5)
A, _ , _ = np.meshgrid(a, b, c)

hopefully fixed this one.


Sort the JSON keys when logging a request

Otherwise, we get non-deterministic ordering of keys, which makes it harder to compare requests

@swift-ci Please test


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210715094404547 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210715094404547 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.73%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26222

Relevant Lines:
55694

💛  - Coveralls


[FEA] Dressipi example using post-padding instead of pre-padding

🚀 Feature request
In example notebook Dressipi session-based next item prediction, in the preprocessing step it's using post-padding nvt.ops.ListSlice(-SESSIONS_MAX_LENGTH, pad=True) to contruct the sequence features, but pre-padding seems to make more sense for preprocessing session-based transaction data. I looked into the source code of ListSlice and found out that there is actually no pre-padding in the current implementation. There's an existing issue tracking this feature, but hasn't been updated for 5 month: https://github.com/NVIDIA-Merlin/NVTabular/issues/1552.
With Merlin-models getting ready for sequential/session-based models, it's pretty crucial to pair it with Nvtabular to preprocess sequential data and feed into the models. I think pre-padding is way more common in sequential data preprocessing than post-padding, so it would be great if this issue can be prioritized to match with Merlin-models' awesome development. Thanks!

@zhiruiwang thanks for reporting that. We will look into that, and get back to you.

Hi @zhiruiwang
Merlin Models expects sequence features to not be padded. The reason is that Merlin Models makes usage of tf.RaggedTensor to represent sequences, which allow for having different sequence lengths for different examples.
So we should not use nvt.ops.ListSlice(..., pad=True) when preparing data to be used with Merlin Models.
@rnyak has already updated the Dressipi example in this commit to not use padding in ListSlice.
Does that address your FEA? Can we close this ticket?

Yes! I was looking into the new Dressipi notebook diff and was wondering why padding got removed. This explanation is very clear. We can close this ticket


Add syntax colors for diff additions/deletions.

Bug/issue #, if applicable: #712
Summary
Maps the appropriate colors for the "addition" and "deletion" syntax nodes when highlighting code listings of language "diff" or "patch".
Before:

After:

Resolves #712
Testing
Example code listing:
diff --git a/1.txt b/2.txt
index de98044..6372083 100644
--- a/1.txt
+++ b/2.txt
@@ -1,3 +1,3 @@
 a
-b
 c
+d

Steps:

Copy the contents of the example diff from above to a fenced code block with language "diff" in the markdown (or use any other example diff).
Verify that the lines starting with "+" are now in green
Verify that the lines starting with "-" are now in red

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests (CSS-only change)
[X] Ran npm test, and it succeeded
[X] Updated documentation if necessary

\cc @ethan-kusters

@swift-ci test


Custom container registry

By default, the registry.k8s.io container registry is used for all the components.
An override should be available for the kube-apiserver, kube-scheduler, and kube-controller-manager components.

Hello @prometherion, I can pick this up. Do you already have a design in mind?
We could add something under spec.controlPlane or maybe even spec.controlPlane.deployment. We can add an object like
imageOverrides:
  registry: mycustomregistry.com/k8s
  apiServerImage: myapiserver-custom-build-v1.24
  controllerManagerImage: cm:v1.24
  schedulerImage: sched-v1.24-xxx

and the full image path would be mycustomregistry.com/k8s/{myapiserver-custom-build-v1.24,cm:v1.24,sched-v1.24-xxx}
Otherwise we can create something like
type ControlPlaneRegistry struct {
	Registry string
	APIServerImage string
	ControllerManagerImage string
	Scheduler string
	// Available only if Kamaji is running using Kine as backing storage.
	Kine string
}

One caveat with this approach is that kubernetesSpec.Version is not coupled with the image anymore, while at the moment we build it with
podSpec.Containers[index].Image = fmt.Sprintf("registry.k8s.io/kube-apiserver:%s", tenantControlPlane.Spec.Kubernetes.Version)

and there might be side effects to this.
What do you think?

One caveat with this approach is that kubernetesSpec.Version is not coupled with the image anymore, while at the moment we build it with

kubernetesSpec.Version is the parameter Kamaji is using to build the logic for the upgrades, such as blocking the non-linear upgrades (e.g.: 1.24 to 1.26) or preventing unsupported versions (e.g.: 1.28 not yet released).
Rather, what we could think of is something as the following struct:
type ControlPlaneRegistry struct {
  // Default to registry.k8s.io
  Registry string
  // Optional
  TagSuffix string

  APIServerImage string
  ControllerManagerImage string
  Scheduler string
}

Please, note the TagSuffix struct member: this could be helpful to use bleeding edge versions, or maybe support in the future additional distros as the k3s one.

Ok, it makes sense.
I'll try to get to it soon.

@maruina honestly I'm not so convinced about the placement of the controlPlaneRegistry struct.
Shouldn't it be in spec.kubernetes, rather? 🤔
I'm eager for your take on it.

If it's something impacting only the Control Plane deployment, I think it's in the right place.
Otherwise, if we want to specify the other components images as well - kine, konnectivity, etc - it might make sense to move it under TenantControlPlaneSpec.
Another option could be to add just the registry under TenantControlPlaneSpec and have something like
type ImagesOverride struct {
	APIServer         string `json:"apiServer,omitempty"`
	ControllerManager string `json:"controllerManager,omitempty"`
	Scheduler         string `json:"scheduler,omitempty"`
}

under the deploymentSpec.

Otherwise, if we want to specify the other components images as well - kine, konnectivity, etc - it might make sense to move it under TenantControlPlaneSpec.

The add-ons are already managing their own image overrides.

If it's something impacting only the Control Plane deployment, I think it's in the right place.

You're right 👍🏻


Max load average

Add -l N option to limit the load average.
This is similar to GNU make -l/--load-average option.  It limits the number of job started if the load average exceed the given value.  It can be very useful when running ninja on a continuous integration server where we want to use parallelism as much as possible without overloading the server.

@lilydjwg See https://github.com/ninja-build/ninja/pull/1399


Exception while creating a package which contains a LiveCopy

When creating a package for a Page which must include LiveCopies, one may encounter an exception. The exception is due to the page has a corrupted live copy. That is, the path to the live copy contains a node without its jcr:content subnode, or else the live copy itself misses its jcr:content.
Package build may fail without any notification.
Expected result:

Package build does not fail, and a valid package is created (however the "broken" live copies together with the subsequent live copies of the previous are skipped from the package)
An alert is displayed to the user with the error message. The error message says in which path the problem  occurred first. We have a single error message for every page that failed. If there are many messages, the alert popup must have scroll.

RangeIterator relationships = liveRelationshipManager.getLiveRelationships(resource, null, null);

Example of exaption: javax.jcr.ItemNotFoundException: No content resource for resource at path /content/hpe/base/blueprint/regression/components/global-header-nav-4-0/global-nav-4-0-no-jcr-content


Tuya: fix negative temperatures for some devices

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.709%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
6839

Relevant Lines:
8170

💛  - Coveralls

Codecov Report
Base: 83.73% // Head: 83.70% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (ec2503a) compared to base (84d02be).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #2176      +/-   ##
==========================================
- Coverage   83.73%   83.70%   -0.04%
==========================================
  Files         257      257
  Lines        8216     8170      -46
==========================================
- Hits         6880     6839      -41
+ Misses       1336     1331       -5

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0601_siren.py
93.96% <ø> (ø)

zhaquirks/xbee/__init__.py
94.81% <0.00%> (ø)

zhaquirks/xbee/types.py
93.75% <0.00%> (+2.26%)
:arrow_up:

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

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


Circular reference error when serializing custom passthrough class

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I have an edge case that i swear is an actual problem and not just esoteric bughunting.
To support multiple array backends from a single NDArray type in numpydantic, I use it as an abstract passthrough class that validates the data but then returns one of potentially multiple types (numpy ndarray, dask array, proxy to an hdf5 array, etc., more info in docs).
This works, including roundtrip json serialization, except when the type is specified on the __pydantic_extra__ field like __pydantic_extra__: dict[str, NDArray] . Then pydantic seems to lose the connection between the object that's passed through and the NDArray object, and attempts to serialize the object directly (rather than using the serialization schema created by NDArray.__get_pydantic_core_schema__ ).
I have been trying to work around this by giving __pydantic_serializer__ declarations to the passed through types, but i have been running up against a consistent problem with the recursion checker:
pydantic_core._pydantic_core.PydanticSerializationError: Error serializing to JSON: ValueError: Circular reference detected (id repeated)

I've dug around in that code a bit, and it seems like it's a very tight check whether or not an id has been seen before, but I can't really tell here where it might have been repeated. I'm not sure what a fix here looks like because i can't tell if this is a bug or i'm doing something wrong.
I fully acknowledge this is a relatively offroad, nonstandard usages of maybe not fully finished APIs, so apologize in advance.  If it does look like a bug to y'all, i would be happy to help with a patch, as i am always looking for more reasons to learn more about bilingual rust/python projects <3.
Below is a MWE that reproduces the error so you don't have to dig through all the numpydantic code :)
edit1: More info - i can't set a python debugger in the serialization function, so i assume (?) this happens before we actually reach it and try and call it
edit2: it appears as if it's not limited to extra fields, and it happens for any passthrough class like this, MWE updated to show that and the other pair of cases for when the serialization function is defined on the validating class and why it is necessary to declare the serialization function on the passed through class in the first place
Example Code
When the serializer is on the passed-through class:
from pydantic import BaseModel, ConfigDict
from pydantic_core import SchemaSerializer, core_schema

def jsonize(x):
    return [1,2,3]

def passthrough(x):
    return x

class SerializableClass:

    __pydantic_serializer__ = SchemaSerializer(
        core_schema.plain_serializer_function_ser_schema(
            jsonize, when_used="json"
        )
    )

class AnnotationClass:

    def __get_pydantic_core_schema__(self, *args):
        return core_schema.no_info_plain_validator_function(
            passthrough
        )

class MyModel(BaseModel):
    real_field: AnnotationClass | None = None
    __pydantic_extra__: dict[str, AnnotationClass]

    model_config = ConfigDict(extra="allow")

# Fails - Circular reference
instance = MyModel(real_field=SerializableClass())
instance.model_dump_json()

# Fails - Circular Reference
instance = MyModel(extra_field=SerializableClass())
instance.model_dump_json()

When the serializer is on the validation class:
from pydantic import BaseModel, ConfigDict
from pydantic_core import SchemaSerializer, core_schema

def jsonize(x):
    return [1,2,3]

def passthrough(x):
    return x

class SerializableClass:
    pass

class AnnotationClass:

    def __get_pydantic_core_schema__(self, *args):
        return core_schema.no_info_plain_validator_function(
            passthrough,
            serialization=core_schema.plain_serializer_function_ser_schema(
                jsonize, when_used="json"
            )
        )

class MyModel(BaseModel):
    a: AnnotationClass | None = None
    __pydantic_extra__: dict[str, AnnotationClass]

    model_config = ConfigDict(extra="allow")

# Succeeds:
a = MyModel(real_field=SerializableClass())
a.model_dump_json()

# Fails - unable to serialize unknown type
instance = MyModel(extra_field=SerializableClass())
instance.model_dump_json()

Python, Pydantic & OS Version
pydantic version: 2.9.2
        pydantic-core version: 2.23.4
          pydantic-core build: profile=release pgo=false
                 install path: /Users/jonny/git/p2p-ld/numpydantic/.venv/lib/python3.12/site-packages/pydantic
               python version: 3.12.6 (main, Oct  2 2024, 16:53:48) [Clang 15.0.0 (clang-15<IP_ADDRESS>.5)]
                     platform: macOS-14.3.1-x86_64-i386-64bit
             related packages: mypy-1.11.2 pydantic-settings-2.5.2 typing_extensions-4.12.2
                       commit: unknown

I couldn't get the instructions for debugging working, but i have managed to get my own extremely janky print-statements-as-debugger thing happening, and as far as I can tell we are double-tapping the recursion guard for extra fields?
For the above models, if I insert some print statements at the start of the Extra::recursion_guard method like this:
// ...
    ) -> PyResult<RecursionGuard<'x, &'y Self>> {
        println!("-----------");
        println!("value: {:#?}", value);
        println!("backtrace: {}", Backtrace::force_capture());
        RecursionGuard::new(self, value.as_ptr() as usize, def_ref_id).map_err(|e| match e {
// ...

then I get the following traceback:

expand/collapse traceback
-----------
value: <__main__.SerializableClass object at 0x1049ef140>
backtrace:    0: std::backtrace_rs::backtrace::libunwind::trace
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
   1: std::backtrace_rs::backtrace::trace_unsynchronized
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2: std::backtrace::Backtrace::create
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/backtrace.rs:331:13
   3: std::backtrace::Backtrace::force_capture
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/backtrace.rs:312:9
   4: _pydantic_core::serializers::extra::Extra::recursion_guard
             at ./src/serializers/extra.rs:196:35
   5: _pydantic_core::serializers::infer::infer_serialize_known
             at ./src/serializers/infer.rs:365:27
   6: <_pydantic_core::serializers::infer::SerializeInfer as serde::ser::Serialize>::serialize
             at ./src/serializers/infer.rs:335:9
   7: <_pydantic_core::serializers::ser::Compound<W,F> as serde::ser::SerializeMap>::serialize_value
             at ./src/serializers/ser.rs:569:22
   8: serde::ser::SerializeMap::serialize_entry
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/serde-1.0.210/src/ser/mod.rs:1817:9
   9: <_pydantic_core::serializers::fields::GeneralFieldsSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/fields.rs:453:21
  10: <_pydantic_core::serializers::shared::CombinedSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/shared.rs:261:1
  11: <_pydantic_core::serializers::type_serializers::model::ModelSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/type_serializers/model.rs:242:13
  12: <_pydantic_core::serializers::shared::CombinedSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/shared.rs:261:1
  13: <_pydantic_core::serializers::shared::PydanticSerializer as serde::ser::Serialize>::serialize
             at ./src/serializers/shared.rs:337:9
  14: _pydantic_core::serializers::shared::to_json_bytes
             at ./src/serializers/shared.rs:365:13
  15: _pydantic_core::serializers::SchemaSerializer::to_json
             at ./src/serializers/mod.rs:199:21
  16: _pydantic_core::serializers::SchemaSerializer::__pymethod_to_json__
             at ./src/serializers/mod.rs:87:1
  17: pyo3::impl_::trampoline::fastcall_with_keywords::{{closure}}
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:44:29
  18: pyo3::impl_::trampoline::trampoline::{{closure}}
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:188:54
  19: std::panicking::try::do_call
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:557:40
  20: ___rust_try
  21: std::panicking::try
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:521:19
  22: std::panic::catch_unwind
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panic.rs:350:14
  23: pyo3::impl_::trampoline::trampoline
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:188:9
  24: pyo3::impl_::trampoline::fastcall_with_keywords
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:44:13
  25: _pydantic_core::serializers::<impl pyo3::impl_::pyclass::PyMethods<_pydantic_core::serializers::SchemaSerializer> for pyo3::impl_::pyclass::PyClassImplCollector<_pydantic_core::serializers::SchemaSerializer>>::py_methods::ITEMS::trampoline
             at ./src/serializers/mod.rs:87:1
  26: _method_vectorcall_FASTCALL_KEYWORDS
  27: _PyObject_Vectorcall
  28: __PyEval_EvalFrameDefault
  29: _PyEval_EvalCode
  30: _run_mod
  31: _pyrun_file
  32: __PyRun_SimpleFileObject
  33: __PyRun_AnyFileObject
  34: _pymain_run_file_obj
  35: _pymain_run_file
  36: _Py_RunMain
  37: _pymain_main
  38: _Py_BytesMain
  39: <unknown>

-----------
value: <__main__.SerializableClass object at 0x1049ef140>
backtrace:    0: std::backtrace_rs::backtrace::libunwind::trace
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
   1: std::backtrace_rs::backtrace::trace_unsynchronized
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2: std::backtrace::Backtrace::create
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/backtrace.rs:331:13
   3: std::backtrace::Backtrace::force_capture
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/backtrace.rs:312:9
   4: _pydantic_core::serializers::extra::Extra::recursion_guard
             at ./src/serializers/extra.rs:196:35
   5: _pydantic_core::serializers::infer::infer_serialize_known
             at ./src/serializers/infer.rs:365:27
   6: _pydantic_core::serializers::infer::infer_serialize
             at ./src/serializers/infer.rs:346:5
   7: <_pydantic_core::serializers::type_serializers::any::AnySerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/type_serializers/any.rs:64:9
   8: <_pydantic_core::serializers::shared::CombinedSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/shared.rs:261:1
   9: <_pydantic_core::serializers::shared::PydanticSerializer as serde::ser::Serialize>::serialize
             at ./src/serializers/shared.rs:337:9
  10: _pydantic_core::serializers::infer::infer_serialize_known
             at ./src/serializers/infer.rs:513:13
  11: <_pydantic_core::serializers::infer::SerializeInfer as serde::ser::Serialize>::serialize
             at ./src/serializers/infer.rs:335:9
  12: <_pydantic_core::serializers::ser::Compound<W,F> as serde::ser::SerializeMap>::serialize_value
             at ./src/serializers/ser.rs:569:22
  13: serde::ser::SerializeMap::serialize_entry
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/serde-1.0.210/src/ser/mod.rs:1817:9
  14: <_pydantic_core::serializers::fields::GeneralFieldsSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/fields.rs:453:21
  15: <_pydantic_core::serializers::shared::CombinedSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/shared.rs:261:1
  16: <_pydantic_core::serializers::type_serializers::model::ModelSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/type_serializers/model.rs:242:13
  17: <_pydantic_core::serializers::shared::CombinedSerializer as _pydantic_core::serializers::shared::TypeSerializer>::serde_serialize
             at ./src/serializers/shared.rs:261:1
  18: <_pydantic_core::serializers::shared::PydanticSerializer as serde::ser::Serialize>::serialize
             at ./src/serializers/shared.rs:337:9
  19: _pydantic_core::serializers::shared::to_json_bytes
             at ./src/serializers/shared.rs:365:13
  20: _pydantic_core::serializers::SchemaSerializer::to_json
             at ./src/serializers/mod.rs:199:21
  21: _pydantic_core::serializers::SchemaSerializer::__pymethod_to_json__
             at ./src/serializers/mod.rs:87:1
  22: pyo3::impl_::trampoline::fastcall_with_keywords::{{closure}}
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:44:29
  23: pyo3::impl_::trampoline::trampoline::{{closure}}
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:188:54
  24: std::panicking::try::do_call
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:557:40
  25: ___rust_try
  26: std::panicking::try
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:521:19
  27: std::panic::catch_unwind
             at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panic.rs:350:14
  28: pyo3::impl_::trampoline::trampoline
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:188:9
  29: pyo3::impl_::trampoline::fastcall_with_keywords
             at /Users/jonny/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.22.3/src/impl_/trampoline.rs:44:13
  30: _pydantic_core::serializers::<impl pyo3::impl_::pyclass::PyMethods<_pydantic_core::serializers::SchemaSerializer> for pyo3::impl_::pyclass::PyClassImplCollector<_pydantic_core::serializers::SchemaSerializer>>::py_methods::ITEMS::trampoline
             at ./src/serializers/mod.rs:87:1
  31: _method_vectorcall_FASTCALL_KEYWORDS
  32: _PyObject_Vectorcall
  33: __PyEval_EvalFrameDefault
  34: _PyEval_EvalCode
  35: _run_mod
  36: _pyrun_file
  37: __PyRun_SimpleFileObject
  38: __PyRun_AnyFileObject
  39: _pymain_run_file_obj
  40: _pymain_run_file
  41: _Py_RunMain
  42: _pymain_main
  43: _Py_BytesMain
  44: <unknown>

Traceback (most recent call last):
  File "/Users/jonny/git/pydantic-core/test.py", line 43, in <module>
    instance.model_dump_json()
  File "/Users/jonny/git/pydantic/pydantic/main.py", line 471, in model_dump_json
    return self.__pydantic_serializer__.to_json(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pydantic_core._pydantic_core.PydanticSerializationError: Error serializing to JSON: ValueError: Circular reference detected (id repeated)

So we correctly arrive at the infer serialization method, here: https://github.com/pydantic/pydantic-core/blob/92a259ea10113e0d41dea5b14dc8745e3bf671ef/src/serializers/infer.rs#L356
Then we make a recursion guard, which triggers inserting the id of the value into the extra's recursion state, and also causes the first print of the traceback: https://github.com/pydantic/pydantic-core/blob/92a259ea10113e0d41dea5b14dc8745e3bf671ef/src/serializers/infer.rs#L365
Then we continue and also correctly match against ObType::PydanticSerializable, and that seems to start the serialization process over again, where now through the AnySerializer we repeat the same infer loop and land back at serializers/infer.rs#L365, instantiating the recursion guard again with the same object twice.
So this leads me to suspect that the passthrough part is irrelevant, and in fact any object that has a __pydantic_serializer__ in __pydantic_extra__ will fail.
I confirmed this with this MWE
from pydantic import BaseModel, ConfigDict
from pydantic_core import SchemaSerializer, core_schema

def jsonize(x):
    return [1,2,3]

class SerializableClass:

    __pydantic_serializer__ = SchemaSerializer(
        core_schema.plain_serializer_function_ser_schema(
            jsonize, when_used="json"
        )
    )

    @classmethod
    def __get_pydantic_core_schema__(self, *args):
        return core_schema.any_schema()

class MyModel(BaseModel):
    real_field: SerializableClass | None = None
    __pydantic_extra__: dict[str, SerializableClass]

    model_config = ConfigDict(extra="allow")

# Fails - Circular reference
instance = MyModel(real_field=SerializableClass())
instance.model_dump_json()

# Fails - Circular Reference
instance = MyModel(extra_field=SerializableClass())
instance.model_dump_json()

Interestingly, that also fails when instantiating the model without having any actual extra field (the real_field case above) - it seems as if having an annotation like __pydantic_extra__: dict[str, SerializableClass] is enough to trigger the behavior, which is somewhat surprising to me, because my expectation would be that if i didn't pass any extra values that that annotation would be unused (i.e., being an "extra" field, i would expect the value in the dict to always implicitly be Optional[T]).
As in the initial set of examples, if i instead declare the serializer function in __get_pydantic_core_schema__, i am back to getting "Unable to serialize unknown type: <SerializableClass>" on the second case where it is supplied as extra_field despite SerializableClass having a pydantic core schema.
class SerializableClass:

    def __get_pydantic_core_schema__(self, *args):
        return core_schema.any_schema(serialization=core_schema.plain_serializer_function_ser_schema(
            jsonize, when_used="json"
        ))

oh holy hell. just after posting that, I went back and read complete_model_class again and see that the whole core schema is passed to SchemaSerializer.
With this, now the real_field case works, but the extra_field is still giving Unable to serialize unknown type: <class '__main__.SerializableClass'>
from pydantic import BaseModel, ConfigDict
from pydantic_core import SchemaSerializer, core_schema

def jsonize(*args, **kwargs):
    return [1,2,3]

class SerializableClass:
    @classmethod
    def __get_pydantic_core_schema__(self, *args):
        return core_schema.any_schema(
            serialization=core_schema.plain_serializer_function_ser_schema(
                jsonize, when_used="json"
            )
        )

class MyModel(BaseModel):
    real_field: SerializableClass | None = None
    __pydantic_extra__: dict[str, SerializableClass]

    model_config = ConfigDict(extra="allow")

# Succeeds!
instance = MyModel(real_field=SerializableClass())
instance.model_dump_json()

# Fails - Unable to serialize unknown type
instance = MyModel(extra_field=SerializableClass())
instance.model_dump_json()

And if I do this then both cases work:
from pydantic import BaseModel, ConfigDict
from pydantic_core import SchemaSerializer, core_schema

def jsonize(*args, **kwargs):
    return [1,2,3]

class SerializableClass:

    __pydantic_serializer__ = SchemaSerializer(
        core_schema.any_schema(
            serialization=core_schema.plain_serializer_function_ser_schema(
                jsonize, when_used="json"
            )
        )
    )

    @classmethod
    def __get_pydantic_core_schema__(self, *args):
        return core_schema.any_schema(
            serialization=core_schema.plain_serializer_function_ser_schema(
            jsonize, when_used="json"
            )
        )

class MyModel(BaseModel):
    real_field: SerializableClass | None = None
    __pydantic_extra__: dict[str, SerializableClass]

    model_config = ConfigDict(extra="allow")

# Succeeds!
instance = MyModel(real_field=SerializableClass())
instance.model_dump_json()

# Succeeds!
instance = MyModel(extra_field=SerializableClass())
instance.model_dump_json()

And returning to the passthrough example from OP, this works for both:
from pydantic import BaseModel, ConfigDict, TypeAdapter
from pydantic_core import SchemaSerializer, core_schema, SchemaValidator

def jsonize(x):
    return [1,2,3]

def passthrough(x):
    return x

class SerializableClass:
    __pydantic_serializer__ = SchemaSerializer(
        core_schema.any_schema(
            serialization=core_schema.plain_serializer_function_ser_schema(
                jsonize, when_used="json"
            )
        )
    )

class AnnotationClass:

    @classmethod
    def __get_pydantic_core_schema__(self, *args):
        return core_schema.no_info_plain_validator_function(
            passthrough,
            serialization=core_schema.plain_serializer_function_ser_schema(
                 jsonize, when_used="json"
             )
        )

class MyModel(BaseModel):
    real_field: AnnotationClass | None = None
    __pydantic_extra__: dict[str, AnnotationClass]

    model_config = ConfigDict(extra="allow")

# Works!
instance = MyModel(real_field=SerializableClass())
instance.model_dump_json()

# Works!
instance = MyModel(extra_field=SerializableClass())
instance.model_dump_json()

And i'm seeing this is also some of what TypeAdapter does, though I can't use TypeAdapters here I don't think because i'm wrapping eg. a numpy array and it needs to behave exactly like a numpy array.
OK sorry for making a mess here - I think the actual bug is just that objects with __get_pydantic_core_schema__  when used as an annotation in __pydantic_extra__ don't have their serializers correctly evaluated as they are when used as regular fields - so i need to additionally define __pydantic_serializer__ manually rather than having pydantic evaluate it when it's defined in __get_pydantic_core_schema__


setup a test account on mailgun

currently, we don't send out email when running in development and testing. Setup a new subdomain like sandbox.opencollective.com and enable emails in development as well.

testcollective.opencollective.com is setup. thanks @xdamman.


Update README.md

Codecov Report

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

@@           Coverage Diff           @@
##           master     #287   +/-   ##
=======================================
  Coverage   65.09%   65.09%
=======================================
  Files          15       15
  Lines       33520    33520
  Branches      140      140
=======================================
  Hits        21820    21820
  Misses      11622    11622
  Partials       78       78

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 2421c70...a3ce66a. Read the comment docs.


silly question

Hi Guys,
It's everything working fine.. However, I cannot find the HTML content stored on SOLR... what would be the best way to access the HTML content of the crawled webpages?
All the best,
Vinicius

you can  find fields in solr as raw_text and extracted text where statua:Fetched.I think this is what you are looking.

Hi  @ravituduru thank you very much. However, it only provides "extracted_text", which is raw text, instead of HTML... Is there a way to enable the extraction of HTML as well? Thank you in advance...


Error using processors with Nifi 1.12.0 - Possible refactoring needed

Captured from issue reported in slack

So I reverted to an older version of nifi and that solved the pathing issue. Now I’m getting regular SSLHandshake errors, which I’m guessing is due to my actual certification configuration.
...
anyone know why I might be getting into this error when running the GetOidForPath processor:
java.lang.NoClassDefFoundError: org/apache/nifi/ssl/SSLContextService$ClientAuth
    at > com.deciphernow.greymatter.data.nifi.properties.CommonProperties.$anonfun$parseSSLContext$2(CommonProperties.scala:40)

The import statement in CommonProperties is: import org.apache.nifi.ssl.SSLContextService.ClientAuth
I looked at the docs for nifi 1.12.0 and it looks like ClientAuth is under the SSLContextFactory class, not SSLContextService. Were these processors built under an earlier version of nifi perhaps?

Release Notes for Apache NiFi 1.12.0 are here
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.12.0
Version 1.12.0
Version 1.12.0 of Apache NiFi is a feature, stability, and security related release
Release Date: August 18, 2020
Highlights of the 1.12.0 release include:

By very popular demand you can now empty all queues in a given process group with a single request!
New processor to write scripted record transforms live in the flow
Expose a REST Endpoint for easy metric scraping by Prometheus
Ability to specify group level flow file concurrency - for instance run a single flow file end to end before running another for  traditional job handling
Improved several capabilities related to Azure service interaction
Improved AMQP and MQTT support as well as JMS improvements
Support for latest Kafka 2.6 clients

A full list of issues that were resolved can be found at: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346778

As of writing this comment, there is a newer version 1.12.1 that was released 2020-09-28.

Not going to be as easy as I had hoped. NiFi 1.12.1 bans org.json:json https://github.com/apache/nifi/blob/rel/nifi-1.12.1/pom.xml#L628 which we use. Refactor will be needed.

Looking a little deeper, I think this is going to take several days of effort, but probably less than a week. The org.json library was buried deep into the BuildPermissions and GetPolicies processors as well as their tests.

Looks like the latest release is 1.12.1. I am going to dev against that since we want it to be the most current.


there are many strange problems

I didn't make any changes, just ran the install.sh, and I got the following error about the version of the package:
ERROR: Could not find a version that satisfies the requirement matplotlib (from versions: none)
ERROR: No matching distribution found for matplotlib
ERROR: Could not find a version that satisfies the requirement plotly==5.9.0 (from versions: none)
ERROR: No matching distribution found for plotly==5.9.0
ERROR: Could not find a version that satisfies the requirement jupyterlab>=3 (from versions: none)
ERROR: No matching distribution found for jupyterlab>=3
ERROR: Could not find a version that satisfies the requirement ipywidgets>=7.5 (from versions: none)
ERROR: No matching distribution found for ipywidgets>=7.5
I don't understand, why do install.sh packages required in it have inexplicable version problems? who can teach me, pls, i really do not know what happend

and there is a more stange problems about torch!??
ERROR: Could not find a version that satisfies the requirement torch==2.2.0 (from versions: none)
ERROR: No matching distribution found for torch==2.2.0
why? i didn't edit the 'install.sh'

Likely related to your other issue #83, please reinstall as instructed in #83 and let us know how it goes

Following my answer in #85, I am closing this issue which I assume should be fixed once you follow instructions from #85 and #83


Delete some unnecessary overrides from JKCodeBuilder

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#22  👈
#21
#20
#19
#18
#17
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ermattt and the rest of your teammates on  Graphite


Alluxio FileSystem client static resource management

Summary
There are FileSystem bound resources that do not scale well under concurrent access.
Each file system holds:

EventLoop instance for use by any channel in the system
Alluxio RPC client pools

BlockWorkerClient pool
FileSystemMaster/BlockMaster pools

There are two concerns:

Resource Leak: If FileSystem is not closed, system resources (fd) held by EvetLoop  and some RPC threads will be leaked.
Concurrency: FileSystem level integration will end up every channel having its own event-loop, and will introduce coordination overhead to the whole JVM process. Additionally, being configured per user-conf, reducing the total count of pooled RPC clients will introduce a fairness problem and possible starvation to the critical operations.

Alluxio static resource management should provide JVM level pools for mentioned resources.
Urgency
To efficiently work with applications that do FileSystem level access

@ggezer is this fixed now? If so, can we link the PR(s)?

Partly. Client pools need to go through a similar procedure as connections did.

Will close it for now and reconsider resource management during redesign


The --check-only option enforces wrapping, which is not mentioned by the help text

Clone https://github.com/mozilla/treeherder (revision 1c00ccf for reproducibility)
pip install -r requirements/common.txt -r requirements/dev.txt
isort --check-only treeherder/webapp/api/urls.py

Expected:
No errors shown - since all imports are correctly sorted, and isort --help says:
  -c, --check-only      Checks the file for unsorted imports and prints them
                        to the command line without modifying the file.

Actual:
~/treeherder $ isort --check-only treeherder/webapp/api/urls.py
ERROR: /home/vagrant/treeherder/treeherder/webapp/api/urls.py Imports are incorrectly sorted.

Presumably since the wrapping is being changed:
~/treeherder $ isort --diff treeherder/webapp/api/urls.py
--- /home/vagrant/treeherder/treeherder/webapp/api/urls.py:before       2015-08-10 18:12:02.451898
+++ /home/vagrant/treeherder/treeherder/webapp/api/urls.py:after        2015-08-10 18:31:24.116318
@@ -6,8 +6,9 @@
 from rest_framework import routers

 from treeherder.webapp.api import (artifact, bug, job_log_url, jobs, logslice,
-                                   note, performance_artifact, performance_data,
-                                   projects, refdata, resultset)
+                                   note, performance_artifact,
+                                   performance_data, projects, refdata,
+                                   resultset)

 # router for views that are bound to a project
 # i.e. all those views that don't involve reference data

The help text should either be adjusted to say something like:
Checks the file for unsorted imports or mis-wrapped imports
...or else --check-only should only show errors if the actual order was wrong. (The latter would probably be more useful for me personally, but I understand it may be more surprising for other people. Perhaps a separate --dont-change-wrapping option might help, which could be used for --check-only plus all of the other modes? My use-case is running check-only mode on Travis to ensure people don't regress the import order, but I'm not too fussed about the wrapping style).
Using isort 4.0.0 with Python 2.7.10 on Ubuntu 14.04.
Many thanks :-)

Hi @edmorley,
Thanks for the feedback! The truth is, the check option is very simple: it essentially runs isort internally, and if there is any change (wrapping, order, space before comma, double entering import) between running isort on the file with your given settings and if there is no change it succeeds otherwise, it fails. I would be open too a more robust implementation for check, but do not have the time currently to do it myself, so in the meantime I will simply update the docs.
Thanks!
~Timothy

Fixed in version 4.1.0
Thanks!
~Timothy

Thank you :-)


_coffee no longer compiles non-Streamline CS files

Hey Bruno. I am working through an upgrade from node 0.10.x → 4.2.x. After upgrading to<EMAIL_ADDRESS>I noticed that _coffee no longer compiles non-Streamline CS files.
> ls
test.coffee

> _coffee --compile test.coffee
> ls
test.coffee
               ^^^
               expected test.js

As expected, the CoffeeScript CLI works just fine.
> coffee --compile test.coffee
> ls
test.coffee    test.js

While this issue is minor and easy to fix, it caught me off guard. Any reason to not revert this behavior? If you leave it as-is, would you be willing to document this changes as part of the 1.x overhaul?

+1: it'd be nice to have the old behavior back, but I can imagine it's not feasible since the whole pipeline changed (to Babel). =)

@aseemk @gscottolson This should be possible (and sorry for the regression). The compilation process is driven by streamline's CLI rather than by babel. So I should be able to fix it.
Anyway, CoffeeScript is not handled as a babel plugin :disappointed: so streamline has to handle it in a special way.


checkov: 3.2.251 -> 3.2.253

Diff: https://github.com/bridgecrewio/checkov/compare/refs/tags/3.2.251...3.2.253
Changelog: https://github.com/bridgecrewio/checkov/releases/tag/3.2.253
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

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

2 packages built:

checkov
checkov.dist


Armstrong Number in java

I want to contribute to this.

sure 👍

I want to contribute to this.

Closing this as already merged with commit cf4f31c.


Support for pinned esm.sh modules?

Hi 👋.
Firstly, thanks so much for making this awesome tool! This may not be something in your power to address, but I thought I'd create a ticket since there doesn't yet seem to be one on the topic of version pinning within the ESM CDN.
So for context, I recently discovered that the latest version of ESM (v96) has a regression that breaks support for the graphql module, which I've just now reported here:

https://github.com/ije/esm.sh/issues/437

I can fix the tests by pinning the version back to v95 (achieved by adding a ?pin=v95 suffix to the ESModule URL) however, but doing this causes my build to fail with the following error:
panicked at 'dnt bug - Could not find mapping for types code specifier<EMAIL_ADDRESS>rs-lib\src\mappings.rs:97:9

Any thoughts / suggestions here would be very much appreciated?

Thank you so much for fixing this ❤


Weather Unsynced

So the issue me and my friend ran into it when we were testing mods, we tried the late join, and on the standard world, his game was showing normal conditions with no weather. where when i joined, my side was flooding. he could hear when i was under water but would be standing right beside me and have no issues and sounded normal.
I don't really have a step my step to reproduce, it just happened when i joined his world after he had landed.
Just looking to see if you're able to get the weather of the world to sync up, perhaps its a seed issue?
sadly i didn't take any screen shots.
nest regards, Neko

Do you both have the mod installed or just the host?

Hi, I'm also experiencing this issue. After an hour of testing I'm 100% that it's late company causing the issue.  IT's also in situations where it wouldn't really make sense for late company to like really kick in since I've been testing with one other person who is joining before the lobby is started.
It's making the mod unusable since we'll arrive at a flooded March and every player in the lobby has the map at full flood levels. Which now that I think about it, I guess I wouldn't describe it as the weather being unsynced, more so just wrong.
Bless, hope you can get this worked out.

Yeah, this also happens with rainy weather, where quick sand is not in the same position for host and client even if both have the mod. Happens in Online and LAN.

Happens to me aswell, I had no weather and my teammates had lightning, and when I did a solo game, it had fog instead of stormy

Same here, here is a video to show the issue :
https://streamable.com/vdnvkl


Unable to grab Netflix account, due to duplicate/error. Index: 1

What do i do?
.
.
.
Finished grabbing 1 Netflix accounts.
Saving the results to /home/kali/Desktop/SpotifyAccounts
Unable to grab Netflix account, due to duplicate/error. Index: 1
Retrying...
Finished grabbing 1 Netflix accounts.
Saving the results to /home/kali/Desktop/SpotifyAccounts
Unable to grab Netflix account, due to duplicate/error. Index: 1
Retrying...
Finished grabbing 1 Netflix accounts.
Saving the results to /home/kali/Desktop/SpotifyAccounts
Unable to grab Netflix account, due to duplicate/error. Index: 1
Retrying...
Finished grabbing 1 Netflix accounts.
Saving the results to /home/kali/Desktop/SpotifyAccounts
Unable to grab Netflix account, due to duplicate/error. Index: 1
Retrying...
Exception in PromiseRejectCallback:
/root/opengen-bot/index.js:47
return Grab(account_type)
RangeError: Maximum call stack size exceeded
(node:4163) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at console.value.
.
.
.

Hello @giorgarasSOS, please make sure openbot-gen has the permission to write files.

Hello @giorgarasSOS, please make sure openbot-gen has the permission to write files.

How do I do that?

Author

You can give it a permission by running node in sudo or by using chmod. For example:
sudo node index.js

chmod +x index.js

Author

You can give it a permission by running node in sudo or by using chmod. For example:
sudo node index.js

chmod +x index.js

Oooo yes yes thank you so much man

Author

You can give it a permission by running node in sudo or by using chmod. For example:
sudo node index.js

chmod +x index.js

Oooo yes yes thank you so much man

If that resolves your problem please close the issue. :D

Author

You can give it a permission by running node in sudo or by using chmod. For example:
sudo node index.js

chmod +x index.js

Oooo yes yes thank you so much man

If that resolves your problem please close the issue. :D

Another thing more of a question really... is where the file is stored right?


Alarmo frontend fail to build

Alarmo Version
v1.9.9
HA Version
2023.5.2
Bug description
Not able to build from head due to incompatible library versions and lint errors.
The fix is not very difficult, need to update a few dependency versions and couple of small changes in the code to fix the lint issues
Steps to reproduce

Clone Alarmo repository
cd .\custom_components\alarmo\frontend\
npm install --save-dev
npm run build

Relevant log output
No response

npm install -save-dev
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/rollup
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@rollup/plugin-commonjs
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!

I believe I’m having the same error, although I’m using HA Supervisor. I have Alarmo 1.9.9, HA 2023.5.3, Supervisor 2023.04.1 and HA OS 10.1. Alarmo Front


Bugfix for En_getaveragepatternvalue() and Return MISSING initial setting from EN_getlinkvalue()

Fixes a bug where 0 was not considered to be a valid pattern index.

Thank you @jamesuber. Now you can move to two characters bug fixes :)

Since I introduced this bug myself, clearly I am near the limits of my capacity already!
Jim Uber, Ph.D.
Director, Drinking Water Network Optimization
Xylem - Digital Solutions
<EMAIL_ADDRESS>M:<PHONE_NUMBER>

From: Elad Salomons @.>
Sent: Wednesday, September 8, 2021 1:55:30 PM
To: OpenWaterAnalytics/EPANET @.>
Cc: Uber, James - Xylem @.>; Mention @.>
Subject: Re: [OpenWaterAnalytics/EPANET] Bugfix for En_getaveragepatternvalue() (#649)
Thank you @jamesuberhttps://github.com/jamesuber. Now you can move to two characters bug fixes :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OpenWaterAnalytics/EPANET/pull/649#issuecomment-915448688, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASMACLRY5GWE5UDUF5N3VLUA6PRFANCNFSM5DVBBB7A.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@eladsal @samhatchett I pushed another commit to my dev branch fork, and noticed that this is now combined with this pull request. That's OK with me, but I thought it might be confusing, and in any case the second commit (return MISSING as initial valve setting) has not been reviewed. Let me know if I should revert and create a new branch and separate pull request.
As it is this PR would close #652 and #655

Thanks, @jamesuber .
Any additional comments before we merge?


⚠ T:Riza Api has degraded performance

In 1f8605e, T:Riza Api (https://infra.triza.dev/api) experienced degraded performance:

HTTP code: 200
Response time: 1756 ms

Resolved: T:Riza Api performance has improved in a6eedf6.


require('sharp') throws error in linux alpine docker

Did you see the documentation relating to installation?
Yes
Have you ensured the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime?
Yes.
Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
Yes
If you are installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
yes
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
Tried this no change
What is the complete output of running npm install --verbose sharp? Have you checked this output for useful error messages?
Yes I have checked it, here it is, install seems successful:
/usr/src/app # npm install --unsafe-perm --ignore-scripts=false --verbose sharp
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   '/usr/local/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'install',
npm verb cli   '--unsafe-perm',
npm verb cli   '--ignore-scripts=false',
npm verb cli   '--verbose',
npm verb cli   'sharp'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb npm-session b07c924bdeddf93d
npm http fetch GET 304 https://registry.npmjs.org/sharp 251ms (from cache)
npm timing stage:loadCurrentTree Completed in 829ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 5ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 102ms
npm http fetch GET 304 https://registry.npmjs.org/semver 70ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/array-flatten 127ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/fsevents 54ms (from cache)
npm WARN deprecated<EMAIL_ADDRESS>Please update to v 2.2.x
npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 488ms
npm timing stage:loadIdealTree Completed in 672ms
npm timing stage:generateActionsToTake Completed in 29ms
npm verb correctMkdir /root/.npm/_locks correctMkdir not in flight; initializing
npm verb lock using /root/.npm/_locks/staging-af89dff005e44f9e.lock for /usr/src/app/node_modules/.staging
npm timing action:extract Completed in 90ms
npm timing action:finalize Completed in 16ms
npm timing action:refresh-package-json Completed in 15ms
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm timing action:preinstall Completed in 4ms
npm info linkStuff<EMAIL_ADDRESS>npm info linkStuff<EMAIL_ADDRESS>npm verb linkBins [
npm verb linkBins   { semver: 'bin/semver.js' },
npm verb linkBins   '/usr/src/app/node_modules/sharp/node_modules/.bin',
npm verb linkBins   false
npm verb linkBins ]
npm info linkStuff<EMAIL_ADDRESS>npm timing action:build Completed in 10ms
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /usr/src/app/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

info sharp Using cached /root/.npm/_libvips/libvips-8.10.5-linuxmusl-x64.tar.br
prebuild-install info begin Prebuild-install version 6.0.0
prebuild-install info looking for cached prebuild @ /root/.npm/_prebuilds/f6dade-sharp-v0.27.0-napi-v3-linuxmusl-x64.tar.gz
prebuild-install info found cached prebuild
prebuild-install info unpacking @ /root/.npm/_prebuilds/f6dade-sharp-v0.27.0-napi-v3-linuxmusl-x64.tar.gz
prebuild-install info unpack resolved to /usr/src/app/node_modules/sharp/build/Release/sharp.node
prebuild-install info install Successfully installed prebuilt binary!
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/sharp/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /usr/src/app/node_modules/sharp
npm timing audit submit Completed in 379ms
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 379ms
npm timing audit body Completed in 1ms
npm timing action:install Completed in 2446ms
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm timing action:postinstall Completed in 2ms
npm verb unlock done using /root/.npm/_locks/staging-af89dff005e44f9e.lock for /usr/src/app/node_modules/.staging
npm timing stage:executeActions Completed in 2608ms
npm timing stage:rollbackFailedOptional Completed in 0ms
npm timing stage:runTopLevelLifecycles Completed in 4222ms
npm verb saving [ { name: 'sharp', spec: '^0.27.0', save: 'dependencies' } ]
npm verb shrinkwrap skipping write for package.json because there were no changes.
npm info lifecycle undefined~preshrinkwrap: undefined
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm notice created a lockfile as package-lock.json. You should commit this file.
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   linux
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 3 packages from 69 contributors and audited 265 packages in 4.372s

What is the output of running npx envinfo --binaries --system?
  System:
    OS: Linux 4.19 Alpine Linux
    CPU: (4) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 272.79 MB / 1.94 GB
    Container: Yes
    Shell: 1.30.1 - /bin/ash
  Binaries:
    Node: 14.15.1 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.8 - /usr/local/bin/npm

The error message is the below, it happens when I try to const sharp = require('sharp'):

/usr/src/app/node_modules/sharp/lib/constructor.js:34

throw new Error(error);

^

Error:

Something went wrong installing the "sharp" module

Error relocating /usr/src/app/node_modules/sharp/build/Release/../../vendor/8.10.5/lib/libvips.so.42: _ZNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found

- Remove the "node_modules/sharp" directory then run

"npm install --ignore-scripts=false --verbose" and look for errors

- Consult the installation documentation at https://sharp.pixelplumbing.com/install

- Search for this error at https://github.com/lovell/sharp/issues

at Object.<anonymous> (/usr/src/app/node_modules/sharp/lib/constructor.js:34:9)

at Module._compile (internal/modules/cjs/loader.js:1063:30)

at Module._extensions..js (internal/modules/cjs/loader.js:1092:10)

at Object.require.extensions.<computed> [as .js] (/usr/src/app/node_modules/ts-node/src/index.ts:1045:43)

at Module.load (internal/modules/cjs/loader.js:928:32)

at Function.Module._load (internal/modules/cjs/loader.js:769:14)

at Module.require (internal/modules/cjs/loader.js:952:19)

at require (internal/modules/cjs/helpers.js:88:18)

at Object.<anonymous> (/usr/src/app/node_modules/sharp/lib/index.js:3:15)

at Module._compile (internal/modules/cjs/loader.js:1063:30)

Any ideas what might go wrong? The docker image is node:14.15.1-alpine3.10

The docker image is node:14.15.1-alpine3.10

Alpine 3.10 provides musl 1.1.22 but the musl-based prebuilt binaries require 1.1.24+
https://sharp.pixelplumbing.com/install#prebuilt-binaries

@lovell thank you! works with alpine3.12


Deprecate our fork of base as the patches have finally made it.

I think I've also simplified the instructions a bit.  Or at least made it so that I won't make the same errors again.
@IanLewis PTAL
@hegemonic PTAL
@waprin FYI

I'm going to merge as I've already killed the temp fork.  Please submit feedback / changes and I'll fix.

Gave it a once over.
LGTM


docs: fix Nvidia casing to be consistent across different places

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg eval

@SomeoneSerge wdyt? However, without an automated check this will happen again. Not a big deal though.

However, without an automated check this will happen again. Not a big deal though.

You mean a general automated spellcheck for docs and comments?


<IP_ADDRESS>:0 causes exception

require("request")("http://<IP_ADDRESS>:0");

events.js:141
      throw er; // Unhandled 'error' event
            ^
Error: connect EADDRNOTAVAIL <IP_ADDRESS> - Local (<IP_ADDRESS>:54620)
    at Object.exports._errnoException (util.js:843:11)
    at exports._exceptionWithHostPort (util.js:866:20)
    at connect (net.js:824:14)
    at lookupAndConnect (net.js:917:5)
    at Socket.connect (net.js:886:5)
    at Agent.exports.connect.exports.createConnection (net.js:61:35)
    at Agent.createSocket (_http_agent.js:177:16)
    at Agent.addRequest (_http_agent.js:147:23)
    at new ClientRequest (_http_client.js:132:16)
    at Object.exports.request (http.js:30:10)

What does it mean to connect to the port 0?
0 can be used to bind to a random available port but it does not make sense to use it to connect…

Makes perfect sense in a test suite

@stevenvachon would you mind explaining your use-case for connecting to port 0 in a test suite?
This one appears to be a difference in behavior between Node.js and Io.js - node v0.10.32 returns a ECONNREFUSED error to the callback while io.js v1.4.3 throws a RangeError. I believe that Io.js' behavior is more accurate as trying to connect to 0 does sound like a programmer's error.

Oops, I misunderstood the question.  I forget now why I'd ran that line of code, but it's at least evident at this point that the result is inconsistent than that of previous node.js versions. However, it's an io.js issue.
If anyone is curious, serving on port 0 is a standard way of connecting to any port that the OS has available, often a high number. This is perfect for a test suite as 80 or 3000 are often not available and sniffing for such is faulty.
var server = http.createServer();
server.listen(0, host, function() {
	port = server.address().port;
});

Clarifying here as well: the issue here is that this error is thrown, while all other errors are asynchronously passed to the callback function.

Fixed in v2.72 https://github.com/request/request/pull/2164


Ensure .dmg is codesigned and the notarization is stapled

This isn't urgent, but it's polish we should eventually apply.
I don’t think we can do this with the electron-build system, but I may be wrong. If we can't then the notarytool that Apple provide will make this easy.

this has been implemented partially in dev builds:

dev uses notary tool
and stapled

todo: dmg output doesnt look nice ui wise.

this is done. latest @electron/notarize is using notarytool and stapling it pre-dmg build in the electron-builder


Digest::Digest is deprecated

Use of OpenSSL::Digest::Digest has been discouraged since Ruby 1.8.7 and generates a deprecation warning on Ruby 2.1.x
See: https://github.com/ruby/ruby/blob/ruby_1_8_7/ext/openssl/lib/openssl/digest.rb#L51 and https://github.com/ruby/ruby/pull/446
This would necessitate a bigger version bump in the next release, as this would make the gem backwards-incompatible with clients that pass Digest::Digest instead of just Digest.

Any updates on this?

Sorry for the +1, but +1. This is absolutely essential for this gem to continue to be useful.

Hmm, seems like this repository is dead. Does anyone have a recommendation of an alternative PBKDF2 implementation? I've been looking at Armor but it doesn't support specifying a key length afaik.

I guess I will close this after 4+ years: I think back in my old company when I raised this we ended up just publishing an internal gem with the fixes -- no idea if they have migrated to something else in the years since.


error in controller for adding model attribute

creating a blog controller, a blog model , /priv/init/lee_blog_util.erl ; every is ok.
now,  i change the first line " -module(blog, [Id, Title, Createtime, Source,  Body]). " of blog model to this:
-module(blog, [Id, Title, Createtime, Source, Uid, Body]).
and i add blog again( submit add blog form) , the error.log is reported :
2014-12-11 21:31:57.963 [error] <0.334.0>@boss_web_controller_handle_request:handle_request:30 Unhandled Error: error:badarg. Stacktrace: [{erlang,iolist_size,[{bad_type,{blog,"blog-6","dd",{{2014,12,11},{21,31,57}},"dd",3,"dd"}}],[]},{mochicow_request,respond,2,[{file,"src/mochicow_request.erl"},{line,401}]},{boss_web_controller_handle_request,handle_request,3,[{file,"src/boss/boss_web_controller_handle_request.erl"},{line,26}]},{mochicow_upgrade,upgrade,4,[{file,"src/mochicow_upgrade.erl"},{line,72}]},{cowboy_protocol,execute,4,[{file,"src/cowboy_protocol.erl"},{line,529}]}]

is that problem has been solved? please reopen issue if not


KIC 2.0: ensure deploy scripts equivalent to those under deploy/

For KIC 2.0 we need to ensure our new deploy scripts (now handled by kubebuilder) including our kustomize builds are equivalent to the previous build scripts.
Acceptance Criteria:

[ ] ensure whether feature parity with the previous kustomize configs exists for v2
[ ] document any backwards incompatible changes we must make in the CHANGELOG.md

@mflendrich to identify and resolve the overlap between this and https://github.com/Kong/kubernetes-ingress-controller/issues/1464 and https://github.com/Kong/charts/issues/391

superseded by #1256 for KIC 2.0.


BLD,ENH,REF,DOC: Image namedtuple, get_image_metadata, PEP8, RST, setup.py, get-image-size CLI entry_point

Still TODO:

[ ] file_path or file_obj
[ ] cookiecutter overlay (tox.ini, travis.yml, HISTORY, ...)

Thanks!
On Oct 20, 2015 6:39 AM, "Paulo Scardine"<EMAIL_ADDRESS>wrote:

Merged #6 https://github.com/scardine/image_size/pull/6.
—
Reply to this email directly or view it on GitHub
https://github.com/scardine/image_size/pull/6#event-440224750.


Propagate verification results to the pipeline

This makes the easily viewable on the test report

/test jvm-build-service-in-repo-apicurio-e2e

/test jvm-build-service-in-repo-apicurio-e2e

@dwalluck FYI


Documentation/op-guide: add job="etcd" label matcher to Grafana dashboard

Prometheus that scrapes etcd might also scrape other things, so we should specifically ask for etcd metrics, especially when dealing with generic metrics like process_resident_memory_bytes.

Codecov Report

Merging #9410 into master will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9410      +/-   ##
==========================================
+ Coverage   72.43%   72.59%   +0.15%
==========================================
  Files         362      362
  Lines       30793    30793
==========================================
+ Hits        22305    22353      +48
+ Misses       6859     6817      -42
+ Partials     1629     1623       -6

Impacted Files
Coverage Δ

proxy/grpcproxy/register.go
69.44% <0%> (-13.89%)
:arrow_down:

etcdserver/v2_server.go
80.76% <0%> (-3.85%)
:arrow_down:

proxy/grpcproxy/watch.go
87.57% <0%> (-3.11%)
:arrow_down:

integration/bridge.go
71.75% <0%> (-2.3%)
:arrow_down:

lease/leasehttp/http.go
58.08% <0%> (-1.48%)
:arrow_down:

etcdserver/cluster_util.go
76.64% <0%> (-1.46%)
:arrow_down:

etcdctl/ctlv3/command/printer_simple.go
72.72% <0%> (-1.4%)
:arrow_down:

clientv3/op.go
72.56% <0%> (-1.33%)
:arrow_down:

etcdserver/v3_server.go
77.89% <0%> (-1.29%)
:arrow_down:

clientv3/watch.go
95.09% <0%> (-0.74%)
:arrow_down:

... and 16 more

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 4704232...8084501. Read the comment docs.

LGTM. Thanks for contribution!
ref. https://prometheus.io/docs/concepts/jobs_instances/


PHP: bump to PHP 5.6

Why?

PHP 5.4 and 5.5 may contain unfixed security issues as they're not supported for over ye year now

majority of PHP world bumping to PHP 7.1

upcoming PHP 7.2 in few days

we could add PHP 7.0/7.1 typehints via coding standards] more easily in the future

as measured on Packagist - 67 % people are on PHP 7.0+ and growing

What do you think?

I'll reopen again with synced fork, sorry


fix(ca9): Fix for ca9_p and ca9_u

Fix #623
CA9 is down, but we have these nice rss feeds for the last 100 opinions now.
We should be able to do a full crawl to get the missed opinions

@mlissner if we do - I havent been defaulting to it- I assume something like that would be done automatically in the processing of the names the same way dates are normalized.

Could you double check? I don't think it's automatic because the process isn't perfect. Our titlecase function is good, but I think we only use it when needed because sometimes it makes mistakes.

Oh no you are totally right.  My mistake.  I think we should just add it to the normalization process.  now.  instead of doing it for every case name every time yes?

No, it shouldn't be done to every case, because it's not perfect.


Landing page2

Add to README, point to CLOCtools, use README in readthedocs index.rst

Needs material from Nathan first


Update the publisher interface to point to the new guide location

Depends on: https://github.com/alphagov/govspeak-preview/pull/18
https://trello.com/c/ppqXaGPk/122-create-a-govspeak-component-for-buttons

Will hold off merging until after the freeze, so if someone has an emergency deployment they don't have to figure out if this change is going to block them 😄


fix(runner): fix parallel testing db name duplication

Complement for https://github.com/risinglightdb/sqllogictest-rs/pull/194.

Oh. forget to bump version in this PR


Big Size Images makes computer slow

I am not sure if this is a library issue or machine issue (tried it on 2 powerful computers with different OS windows + ubuntu but same result).
Anyways, the first try with a simple images 600x400, size around 100kb-250kb and the detecting faces result was just after 7sec which is a lot for me since I am going to detect thousands of faces.

Using sizes like 500-999kb takes 1-2min to detect the faces
Over 1MB, huge problems computer get slower and for an image 2-3MB the computer stopped working.

Well, I know I can resize the image before detecting the face, I just wanted to know this issue where is coming from, is it normal or just me ... note this only detecting fr.FaceDetector() I didn't even start to recognize faces

Hi,
You might want to have a look at: boosting-performance.

@justadudewhohacks

Simply install openblas (sudo apt-get install libopenblas-dev) before building dlib / installing the package.

How can I do it since I have already built the dlib without installing libopenlabs-dev, shall I remove it and resintall again ?

Did you build dlib manually or via the auto build when npm installing this package?
If you are using the auto build, I would do npm uninstall face-recognition && npm install face-recognition.
If you are using a manual build you also have to rebuild dlib before reinstalling the package.

To be honest I think most of the taks are rather CPU intensive regardless of using OpenBLAS or not. On my Macbook Pro I get the following results with this script:
const detector = fr.FaceDetector()
const faceRectangles = detector.locateFaces(image)

256 x 256px about 200ms
512 x 512px about 800ms
1024 x 1024px about 2000ms

Which all are a way to slow for any realtime application. If you still want to go ahead there's several ways to improve the speed which I have found:

Accept the fact that for the realtime part of your application you will use downscaled versions of the original image. You can store the original image for later use.
Create a smaller copy of the image (e.g. 128px) then use locateFaces. Then use locateFaces on the larger image only on the area's where an face has been found.
Use a haarclassifier (either from opencv or from this library), then use locateFaces on the larger image only on this area. The haarclassifier is much faster (about 200ms on 1024x1024) on my device.

// Please note that this detector will only detect frontal faces!
let detectorOpenCV = new cv.CascadeClassifier(cv.HAAR_FRONTALFACE_DEFAULT);

let imageGray = imageCvMat.bgrToGray()
let detect = detectorOpenCV.detectMultiScale(imageGray)
// Also please note that there's an async variant for these functions!

@Zwimber Regarding option 3 where could I find the haarclassifier from this library? I intend to use the face detection for a webcam stream which requires lower latency.

@Zwimber Regarding option 3, where can I find the haarclassifier from this library? I need low latency because I want to try it out with a webcam stream.

The CascadeClassifier comes from opencv4nodejs. You can find some examples here, how to use face-recognition.js with opencv4nodejs.


Add Capacity Check For All Fixed Drives (Rather Than Only C:)

A capacity check should be added for all fixed drives (HDD or SSD) on the user's machine, rather than only checking the C drive. For the time being, only drives of DriveType "Fixed" should be checked.

Implemented a capacity check for all drives of type "Fixed".


pull request for e2e test at 01/10/2017 17:45:06

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


Proof-of-concept experiment

Use Git Theta to track a model with multiple updates to it. Also, collect stats about storage and data transfer.

Commit the full (pre-trained) model
Commit a parameter efficient method tuned version (add/delete/modify a single parameter)
Commit a sparse update (sparse update of the embedding table?)
Make a branch
Commit an update on the branch
Commit a dense update on the original branch
Merge the two branches together.

Depends on https://github.com/r-three/git-theta/issues/146

Note: We should probably train all models in a different step, copy them into the tracked repo, and then commit. This will allow us to run any timing experiments multiple times.
Note: The timing data for git-theta and git-lfs should all be done on the same hardware

Basic plan:

start from T0-3B checkpoint
First commit: LoRA training on CB
Make a branch, RTE dense training
On main branch, do ANLI training
Merge the branch in via parameter-averaging merges (hopefully boosting RTE and CB)
delete sentinel tokens from T0's vocabulary matrix using custom Update plugin (LFS will create a new copy)

Each training step should take maybe an hour. We do few-shot training in each case, which does produce gains, comparing the following tables:

I'd also expect some positive interference, based on this:

We need to implement some code that adds from the LoRA adapter values from the T-Few codebase back into the checkpoint (so that git-theta can reconstruct it via an SVD).

Cost stats can mainly be done post-hoc.


Volume size incorrect

Steps to reproduce:

Create a volume, with size<PHONE_NUMBER>00000000Gi
The volume is in NotReady state, check the size in the list
Edit it as form, check the size on the edit page
Click the volume name, navigate to its detail page

Result:
The size is not displaying<PHONE_NUMBER>00000000Gi on the detail page, list page, and edit page. A decimal size like 0.1 will also lead to the same output

Suggestion:
A maximum limit should be added to the volume size

The size of the vm's volume must be integer and between 1 and 999999.

Another case. @DaiYuzeng

If the length of the size value is longer than 20, the value will be converted to exponential.
We should remove the unit of UnitInput component.

https://github.com/rancher/harvester-ui/blob/5ab2e1cb1c260891aab63c9ef21335e24bcd278a/utils/units.js#L64
the max safe integer in javascript is (2 ** 53 -1) =<PHONE_NUMBER>740991
UnitInput will convert the value from String to Number, so you will come across the bug if you input a huge size.


[go_router] [navigator 2.0] declarative version of showModalBottomSheet is missing

Use case
When using GoRouter or another navigator 2.0 implementation which is inherently declarative it is difficult to reproduce the showModalBottomSheet behaviour.
I would expect to be able to push a bottomSheet onto the page stack of the router instead of adding it to the [Navigator]
Thats what is causing this issue: https://github.com/flutter/flutter/issues/100933
When trying to recreate the modal behaviour in a CustomTransitionPage in GoRouter we have this issue blocking us:
https://github.com/flutter/flutter/issues/102289
Proposal

We should have access to _ModalBottomSheetRoute and or the underlying classes.

We should consider adding adding documentation to gorouter.dev on how to use BottomSheets with GoRouter to avoid problems like https://github.com/flutter/flutter/issues/100933

Further reading
There are community solutions like simple_cupertino_modal_route.dart but it would be more consistent to have access to the already existing navigator 1 version, especially for anybody considering to transition to Navigator 2.0
There is an open SO question on this as well: https://stackoverflow.com/questions/70478220/how-do-i-declaratively-push-bottomsheet-with-navigator-2-0

linked issue for you first proposal point: https://github.com/flutter/flutter/issues/87352

Still no solution?
I have a task-tracker app. On user going through deeplink like "/tasks/42" I should open a bottom sheet for a task 42, but it currently seems not possible.


Validator: Rev2 of NV mesh shaders extension allows LocalSize and LocalSizeId

Forked from https://github.com/KhronosGroup/glslang/issues/1522
Revision 2 of http://htmlpreview.github.io/?https://github.com/KhronosGroup/SPIRV-Registry/blob/master/extensions/NV/SPV_NV_mesh_shader.html adds LocalSize  and LocalSizeId in mesh shaders.
Validator needs to be relaxed to match

Correction: Rev2 enables TaskNV shaders to use LocalSize and LocalSizeId


[Iluvatar] Add readme for llama-13b

 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.tianyuzhou668 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM


option for consume of fuel + leave the empty bucket [Feature request]

Hi, it would be a very useful feature to have an option to change the amount of fuel consumed per second in the config file and the empty bucket should stay in the engine when using lava buckets or any bucket with fuel.
Also an option to include other fuels and be able to see how many fuel is remaining in the engines from the ship inventory and when you dismount the ship you should stay in the same position so you dont fall if you do it in mid air
Thanks for the awesome mod, i hope that you can add some of this features!

I think a config option for fuel consumption would be useful too, the current rate seems way too high to me.

Has been added.


doc(version) Some initial work on documentation for 0.21

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>#306

Some simplification of the documentation Table of Content: Guides first, and Tutorials consolidated under a single Section
Moved around some of the material in Introduction

"lawyer/business/developer" now in main overview
Distinguishes intro material on "smart legal contract" v "templates"
Move online tour to Introduction
better outline for the documentation

Full revision to "markdown text" guide with CiceroMark & TemplateMark for Cicero 0.21

New CiceroMark section for contract text
Fully revised TemplateMark Section with new documentation for optional blocks and join blocks
Distinguishes "inline blocks" from "container blocks" following commonmark spec

Full review / fixes to tutorials

Tested with cicero 0.21

Looks great. A few nit picks.

The ulist and olist examples do not obviously follow the layout for a container block described above, which people may find confusing:
https://deploy-preview-309--accordproject-docs.netlify.app/docs/next/markup-templatemark.html#unordered-lists

I think it would be good to point out that the contents of formulas are not parsed: https://deploy-preview-309--accordproject-docs.netlify.app/docs/next/markup-templatemark.html#ergo-formulas

So, they allow the template developer to generate arbitrary (soon!) markdown text from other contract and clause variables. They therefore cannot be used to set a template model variable during parsing.

Once this is merged I will add a reference for the new decorators.
I'd love to also be cheeky and ask for a snippet of Ergo that shows how to process a request and conditionally emit an obligation .... I can never remember how to do that! :-)
Perhaps we could add a sample clause to this to summarise how to bringdifferent capabilities together: processing a request to return a response, using an enforce, printing and emitting a conditional obligation?
https://deploy-preview-309--accordproject-docs.netlify.app/docs/logic-stmt.html#emitting-obligations

It looks like there is a lot of redundant stuff that has been copy/pasted from the 0.13->0.20 migration guide to the 0.20->0.21 guide. Is there another doc somewhere?
Also, presumable we should create a new Docusaurus release to make this available by default?

Looks amazing. Couple of nit picks - also looks like a log file was accidentally added.

Fixed.

The ulist and olist examples do not obviously follow the layout for a container block described above, which people may find confusing:
https://deploy-preview-309--accordproject-docs.netlify.app/docs/next/markup-templatemark.html#unordered-lists

Good catch! Would indeed be really confusing. Fixed.

I think it would be good to point out that the contents of formulas are not parsed: https://deploy-preview-309--accordproject-docs.netlify.app/docs/next/markup-templatemark.html#ergo-formulas
Formulas allow the template developer to generate arbitrary (soon!) markdown text from other contract and clause variables. They therefore cannot be used to set a template model variable during parsing.

Fixed. Thanks for the suggested text.

It looks like there is a lot of redundant stuff that has been copy/pasted from the 0.13->0.20 migration guide to the 0.20->0.21 guide. Is there another doc somewhere?

Thanks. Yes I was still in the middle of it. Should look better now.

Also, presumable we should create a new Docusaurus release to make this available by default?

Agreed! I'll merge after a second round of review and then tag.

@dselman @mttrbrts All comments should now have been addressed.

Once this is merged I will add a reference for the new decorators.
I'd love to also be cheeky and ask for a snippet of Ergo that shows how to process a request and conditionally emit an obligation .... I can never remember how to do that! :-)
Perhaps we could add a sample clause to this to summarise how to bring different capabilities together: processing a request to return a response, using an enforce, printing, and emitting a conditional obligation?
https://deploy-preview-309--accordproject-docs.netlify.app/docs/logic-stmt.html#emitting-obligations

Once this is merged I will add a reference for the new decorators.
I'd love to also be cheeky and ask for a snippet of Ergo that shows how to process a request and conditionally emit an obligation .... I can never remember how to do that! :-)
Perhaps we could add a sample clause to this to summarise how to bring different capabilities together: processing a request to return a response, using an enforce, printing, and emitting a conditional obligation?
https://deploy-preview-309--accordproject-docs.netlify.app/docs/logic-stmt.html#emitting-obligations

Opened a new issue to track things like this: https://github.com/accordproject/techdocs/issues/310


1657392 Add descriptions for SEO (2 of 3)

Add descriptions for SEO
For anyone that GitHub notifies, this is for 1657392.
You're welcome but not required, according to KhairunJ's guidance, to review these proposed meta descriptions. I'll leave this PR open for 48 hours and address any feedback. After that, we'll sign off for merge. Thanks!
Please keep in mind our 100-160 char length for descriptions.
Fixes #1657392 (2 of 3)

@BillWagner - these three are a different user story from the ones you've been looking at today. Please merge when you get a chance.

@BillWagner - should I reach out to @adegeo to merge these? Or should this repo always go to you? Still not clear on how dotnet works -


Update rest of dependencies

This also adds the missing version numbers.

Great. Thanks, specially for the missing version numbers.
FYI, to update to the latest version automatically, I'm using https://github.com/hayd/deno-udd, but it doesn't work with https://jspm.dev urls.


feat(project): typescript support

update to babel 6
maybe jspm17 ready
add lint-md task, remove unused doc task

Big one... I'll take my time for this tonight!

same as the others. only difference is the component. i'll recheck the d.ts with that

rechecked. d.ts should be fine. the build task differs slightly from the others. i dunno why, but the other way fails

I can't test this thoroughly right now... But it looks good at first glance. So I'll give you a :+1: trusting you tested this, and trusting the unit tests. :)

the code hasn't changed (basically). so no problems tobe expected


May 4 - Securely testing and deploying your application

Event Information

Category
Details

Stream Date
May 4

Stream Time
4pm PT

Title
Securely testing and deploying your application

Description
Even after writing secure code, it is essential for having a process to thoroughly test your application. In this session, we’ll cover the strategies to test your code, application, and any integrations with your application such as with databases and external services. Then, we’ll cover solutions to deploy your application once you have completed testing to have the confidence your application will hold up against threats once it’s out in the wild. This is another crucial part of the Application Security process to ensure your software will maintain confidentiality, integrity, and availability. Join Meaghan Lewis to explore how to best test and deploy your code.

Speaker
---------

SharePoint ID
13210

SharePoint Status
---------

Additional Resources:

Event Checklist
10 Weeks Prior

[ ] Title & Description Finalized
[ ] Tracking Links/Short links
[ ] Published
[ ] Calendar Invite

@meaghanlewis - What do you think about this?
Even after writing secure code, it is essential to have a process to thoroughly test your application. In this session with Meaghan Lewis, Senior Program Manager, we’ll cover the strategies to test your code, application, and any integrations with your application such as with databases and external services. Then, we’ll cover solutions to deploy your application once you have completed testing. This will give you the confidence that your application will hold up against threats once it’s out in the wild. This is another crucial part of the Application Security process to ensure your software will maintain confidentiality, integrity, and availability.

This looks good to go @mebaumb


spin the demos out to a dedicated repository

Would it be possible to move all the demos to a dedicated repository?
This way it would be possible to install the main library as a transportable package and the demos as local package, without moving them to testing and production.

good point! i will split demos from the rest and make a separated branch or repo.

The repository is now split up into two repositories and the demos are separated:
https://github.com/oblomov-dev

Thanks, that was fast! :)
I added a quick comment in the community thread for this week challenge.

thanks for adding a comment, i close this issue now.


Add beta watermark to documentation files

Because we'll be publishing a beta site with some documentation still under review, we want to add an @ana value (I would propose "beta") to put on all documentation that is still under review. We then want that ana value to trigger a beta watermark.
This one is fairly urgent, as we want to release LEMDO Beta on May 7.
Once we have the value, I'll add it to all of our documentation files (excluding the ones that are completely done).

I've made a start on this, but for some reason the @ana values are being lost in the build process for most documents, and I'm not sure why. Once that's solved, the solution (add 'draft' to @ana) will work.

Working as of rev 17480. Close if no further tweaks required.

Looks great!


Test failure: BuildIncremental_SimpleMvc_PersistsTargetInputFile

This test fails occasionally with the following error:
Assert.Equal() Failure
Expected: FileThumbPrint { Hash = "2IHpM77CVXJiLyOQKZyWNaRVLJw=", LastWriteTimeUtc = 2018-08-08T10:20:36.0000000Z }
Actual:   FileThumbPrint { Hash = "2IHpM77CVXJiLyOQKZyWNaRVLJw=", LastWriteTimeUtc = 2018-08-08T10:20:44.0000000Z }
   at Microsoft.AspNetCore.Razor.Design.IntegrationTests.BuildIncrementalismTest.<BuildIncremental_SimpleMvc_PersistsTargetInputFile>d__1.MoveNext() in /_/test/Microsoft.AspNetCore.Razor.Design.Test/IntegrationTests/BuildIncrementalismTest.cs:line 66
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
CC @Eilon,@muratg,@mkArtakMSFT
This issue was made automatically. If there is a problem contact @ryanbrandenburg.

Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact @ryanbrandenburg.

Looks like the failure is in 2.1.x. In 2.2 and later, we skipped the test on xplat (See https://github.com/aspnet/Razor/issues/2219 for details). Are we fine porting the skip in to 2.1.x?

BuildIncremental_SimpleMvc_PersistsTargetInputFile failed with about the same error.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.

BuildIncremental_SimpleMvc_PersistsTargetInputFile failed with about the same error on 2.1.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

BuildIncremental_SimpleMvc_PersistsTargetInputFile failed with about the same error on 2.1.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

BuildIncremental_SimpleMvc_PersistsTargetInputFile failed with about the same error on 2.1.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

d0c7d81336c3c5f2914241bbaa8ac764028fc72c


añadir enlaces informativos

Corregir mayúscula titulo y añadir enlaces.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Thanks for this pull request (PR).
Unfortunately, we are closing this PR, because you apparently deleted the repo in which this PR originated.
If you still want to make a contribution, feel free to submit another PR.
Thank you


Added Explosion Resistance to SecBelts

About the PR

Added 10% explosion resistance to secbelts, and by extension, seccarriers.
Why / Balance

Currently, if security wishes to carry around grenades (e.g. tear gas), they are optimally stored in backpacks due to their innate 10% explosion resistance. I believe that secbelts (and seccarriers) should also have a base 10% explosion resistance so it is no longer a trap carrying around grenades in the secbelt/seccarrier.
Technical details

Added ContentsExplosionResistanceBase to ClothingBeltSecurity and set an appropriate damageCoefficient.
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl: Vexerot

tweak: secbelts and seccarriers now provide 10% reduced explosion damage to contents

I agree with this.  The recent committed PR (can't find it) that removed tear gas and flashbangs from default loadouts and replaced them with holobarrier and sec radio was a roundabout way of achieving this.
Teargas is too niche and used more for crew abuse than actual combat, and removing it from the default loadout was good, however secbelts should be able to safely store flashbangs and the default loadout should include one flashbang.