Update extraction workflow to immediately push new items to STAC api

OpenEO devs are working on a backend feature in export_workspace that would automatically take care of this:
https://github.com/Open-EO/openeo-geopyspark-driver/issues/867


DOC: Improved documentation for numpy.frombuffer

Part of https://github.com/google/jax/issues/21461

Doc test failure fixed.

The error is due to jaxlib 0.4.32 being yanked. If you rebase on the updated main branch, then tests should pass. Thanks!

rebased from the updated main branch.

@jakevdp
Description modified and link added.


When I use the line tool to draw a box, I can only get 3 sides to draw. Clicking on the first point to close the box deletes the last line.

Please show a GIF or explain in clear steps what I need to do in the demo to reproduce the issue (and what the issue is)

Thanks Colin, that's the expected behaviour right now. Clicking on any existing marker will finish drawing.
From your post I assume you expect that clicking on an existing marker will draw the last line as well before finishing?
This would be a breaking change to existing functionality. I won't fix this for now but if more people would like to change this behaviour, upvote this issue.
If you expect a different functionality entirely, let's continue the conversation in here.

I know it is the "expected behavior", but it is bad design.

I also would love to see this change.

I would find this useful if this was possible as a toggle. in my main project it would not suit, but in a side project it is exactly what i want, so maybe being able to pass an option when enabling draw.
I think as a way around it I might use the polygon, make the working layer have no fill, then on completion getLatLngs(), remove layer and create a new polyline layer.


move unnecessary requirements for API to new dependency group; fix dockerfile

@THOR300 i'm hoping we'll archive this repo asap and take down gst1 so maybe not worth it :D


How to pass side-by-side-show-both display?

In docs, https://difftastic.wilfred.me.uk/git.html, we can use difftastic as difftool. How make difftastic to pass --display side-by-side-show-both argument?

Set DFT_DISPLAY=side-by-side-show-both in your .bashrc :)


Make FillMode and StrokeMode components

Opening for discussion. IMO, this change feels pretty good in action.
Fixes #162

I like the fact that it significantly simplifies its usage, especially on the dynamic_shape example. It also looks more idiomatic, from Bevy's perspective.

What do you think about Fill and Stroke vs FillMode and StrokeMode

What do you think about Fill and Stroke vs FillMode and StrokeMode

Just had the same thoughts about it. Now that they are components, Fill and Stroke seem more appropriate.

This currently makes spawning shapes at non-default transforms, or spawning invisible shapes a bit less ergonomic:
// Probably the best way
commands.spawn((
    ShapeBundle {
        transform: Transform::from_xyz(100., 0., 0.),
        ..GeometryBuilder::build_as(&line)
    },
    StrokeMode::new(Color::BLACK, 10.0),
));

// Spawn-and-insert would probably not be considered bevy best-practice
commands
    .spawn((
        GeometryBuilder::build_as(&line),
        StrokeMode::new(Color::BLACK, 10.0),
    ))
    .insert(Visibility::Hidden);

Maybe GeometryBuilder should return a Path rather than a ShapeBundle. (Seems like PathBuilder already works this way?)
commands.spawn((
    ShapeBundle {
        path: GeometryBuilder::build_as(&line),
        transform: Transform::from_xyz(100., 0., 0.),
    },
    StrokeMode::new(Color::BLACK, 10.0),
));

Let me know what you think.

I agree, I think it's better to let users build their own bundles instead of giving them a pre-made one that needs to be edited after.

I took the liberty to make path.rs slightly more visually interesting and include a custom transform so there's at least one of those in the examples.

LGTM!
I originally created the path example as a “test”, since it broke once without notice, so I'm glad that now it displays something more appealing than a line.


how to render the dragon?

https://github.com/SinMDM/SinMDM/blob/main/assets/dragon.png

Hello,
We use Blender for rendering. Download the Wyvern-Fly.fbx from here and follow
the instructions provided for Adding texture in Blender
 Note that if the mesh is not in the same orientation as the skeleton, rotate it to match before doing step 4.

Use the link and download the folder, Wyvern-Fly.fbx is the fbx file of the flying dragon.

Owner

thank you very much for your quick and helpful reply!!!

Use the link and download the folder, Wyvern-Fly.fbx is the fbx file of the flying dragon.

thank you very much for your quick and helpful reply !!!


Make FrameworkExtensions public

Trying to create a ISerializerExtension as per #196 and in accordance to the test for the same issue.
The problem is  the test makes usage of IServiceRepository.RegisterWithDependencies<TFrom, TTo>() which lives in the static class FrameworkExtensions - and that is internal.
Could this class be made public? :)

Good point. :)  We basically have everything sealed and are unsealing things on a case-by-case basis.  I've gone ahead and done this and will push 2.1.8 soon.

Closing this now as this has been deployed.  Please let me know if you have any further questions/requests around this and I will take a look into it.


bugs in numpy array resize for a numba object

from numba import jit,int64,float64,jitclass
import numpy as np
spec_data = [
  ('H', float64[:])
]

@jitclass(spec_data)
class Data(object):
  def __init__(self):
    pass

data = Data()
data.H = np.ones(5)
print 'data.H\t',data.H
data.H.resize(10)
print 'data.H\t',data.H

this will output:
data.H	[ 1.  1.  1.  1.  1.]
data.H	[  1.72723371e-077  -2.68678326e+154   1.00000000e+000   1.00000000e+000
1.00000000e+000]
but other times, it will output:
data.H	[ 1.  1.  1.  1.  1.]
data.H	[ 1.  1.  1.  1.  1.]
I guess: numpy has a memory operation on data.H (a ndarray), but numba object did not receive the change.
Can this be fixed? This would be important if user want to manipulate memory allocation of numpy array in numba object.

anyone would like to deal with this issue?

I believe this is an invalid use of @jitclass. http://numba.pydata.org/numba-doc/dev/user/jitclass.html#the-decorator-jitclass suggests

The definition of the class requires at least a __init__ method for initializing each defined fields. Uninitialized fields contains garbage data. Methods and properties (getters and setters only) can be defined. They will be automatically compiled.

but the class above does not initialize the H field, it just has pass.
Further:

The data of a jitclass instance is allocated on the heap as a C-compatible structure so that any compiled functions can have direct access to the underlying data, bypassing the interpreter.

which would explain why a resize or an assignment would be invalid, essentially it's a fixed size block.


Implement: Convolution for probability distributions

Hi!
I would like to propose an extension of this crate with implementation of Convolution of probability distributions for all distributions which supports this operation.
Within my project I already have such implementation based on following traits applied to several distributions:
trait IdenticalConvolutions {
    type Multiplier;
    type Distribution;

    /// The convolution/sum of two independent identically distributed random variables.
    fn identical_convolutions(&self, times: Self::Multiplier) -> Result<Self::Distribution>;
}

trait ConvolutionWith<D> {
    type Distribution;

    /// The convolution/sum of two independent random variables.
    fn convolution_with(&self, other: D) -> Result<Self::Distribution>;
}

Examples of implementations:
impl IdenticalConvolutions for Gamma {
    type Multiplier = f64;
    type Distribution = Gamma;

    fn identical_convolutions(&self, times: f64) -> Result<Gamma> {
        if times <= 0.0 {
            return Err(Model("The multiplier must be greater than zero!".to_string()));
        };

        Gamma::new(self.shape() * times, self.rate()).into()
    }
}

impl ConvolutionWith<Gamma> for Gamma {
    type Distribution = Gamma;

    fn convolution_with(&self, other: Gamma) -> Result<Gamma> {
        if self.rate() != other.rate() {
            return Err(Model(
                "Convolution of two Gamma distributions requires that both have the same rate/scale parameter!"
                    .to_string(),
            ));
        };

        Gamma::new(self.shape() + other.shape(), self.rate()).into()
    }
}

It seems to me that these traits are general enough to cover all available cases. Your thoughts?
I can contribute into this, but only after somebody put a placeholder/example.

I've looked at this request occasionally and been unsure how to approach it. On one hand, this allows users of the crate to rely on closed form convolutions without looking them up elsewhere and choose the appropriate parameters for a different distribution.
It effectively offers a dynamic dispatch option for the sentiment below,

I want to create a distribution that is described by the sum of N random variables.
I accept that the returned distribution is not of the same family as any of the given distributions, but I want it to work like a distribution.

Since all our (discrete|continuous) distribution structs in the distribution module impl the same set of traits, it would be nice to have some kind of supertrait that expresses "this type has this whole API for its respective support".

I've recently been thinking about a similar sentiment for another convenience which would behave as an optimization.
Some distribution (families) are special cases of more general distributions, it would be useful if the constructor for distribution A could return distribution B which is an optimized special case of A.
A trivial example might be zero width Uniform, zero width Triangle, and zero width Gaussian, all of these converge to a Dirac distribution. More usefully might be StudentsT distribution which can be the Cauchy or the Normal distribution depending on DOF.
Now I'm not 100% sure these are the same problem, but from the lens of traits/interfaces, they appear to be at least up to how they're constructed, new as it stands won't cut it.

@YeungOnion You can create a new repository branch specifically for this topic, and when I have time, I will prepare an implementation to this branch for all the respective distributions. Then we can discuss something more tangible.
Such features are useful within my current project, which is centered around stochastic process modeling. However, I only use a few distributions from this crate. I just think that contributing such functionality might be helpful for someone else.
Possible toy use case: Observing a frog jumping. As a modeling distribution we can take Gamma one as a frog never jumping on negative distance and a distance itself is a real number. Using convolutions, we can ask: what distance is covered by 3 jumps, or what would be the probability that 4.2 meters is covered by 3 jumps.

I opened a branch feat-convolution

I put it behind a nightly feature so we can experiment with it and still keep releasing the less unstable stuff, will likely use this in other areas as well
I defined the traits

made associated types and generics just like ops::Add for ConvolveWith
trying out different names to get your input there too (wiki on power convolution)
regarding the multiplier, I chose something that may not implement float and did it as a generic instead (from the power convolution wiki I have the understanding that non whole number folding is something beyond my understanding)


Fix navigation rail with long labels misplaced highlights

Description
This PR fixes an issue related to InkWell highlights being misplaced for navigation rail destinations with long labels.

Before:

https://github.com/flutter/flutter/assets/840911/a64bb55f-ed17-43b4-a67c-e1ae057264cf

After:

https://github.com/flutter/flutter/assets/840911/1ac9ae45-b752-4b17-9953-6c1baae170ac
Related Issue
Fixes https://github.com/flutter/flutter/issues/128005
Tests
Adds 1 test.

@feinstein Because the vertical offset is always used. I considered replacing the indicatorOffset by two variables, indicatorOffsetX and indicatorOffsetY but this was LESS readable.

Ok, makes sense. Thanks for the contribution.


InitAPI+ShutdownAPI+InitAPI crashes

Describe the bug
I have a test suite where each test calls Aws::InitAPI, then executes a test and finally calls Aws::ShutdownAPI. The second test then crashes in Aws::InitAPI. This problem started occurring when upgrading aws-sdk-cpp from version 1.8.186 to 1.9.352.
This looks similar to #2102, but that issue is closed and I don't quite understand what the reporter's solution mentioned in https://github.com/aws/aws-sdk-cpp/issues/2102#issuecomment-1254440532 would be.
Expected Behavior
A second Aws::InitAPI does not crash after Aws::InitAPI + Aws::ShutdownAPI.
Current Behavior
A second Aws::InitAPI crashes after Aws::InitAPI + Aws::ShutdownAPI.
Reproduction Steps
Compile and run the following program, linking against aws-sdk-cpp 1.9.352:
#include <aws/core/Aws.h>

int main()
{
  Aws::SDKOptions options;

  Aws::InitAPI(options);
  Aws::ShutdownAPI(options);

  Aws::InitAPI(options); // line 10
  Aws::ShutdownAPI(options);
}

The program will crash at line 10.
GDB backtrace:
(gdb) bt
#0  0x00007ffff791166f in s2n_x509_trust_store_wipe (store=0x118) at crt/aws-crt-cpp/crt/s2n/tls/s2n_x509_validator.c:135
#1  0x00007ffff78e0988 in s2n_config_cleanup (config=0x0) at crt/aws-crt-cpp/crt/s2n/tls/s2n_config.c:125
#2  0x00007ffff78e1373 in s2n_config_free (config=0x0) at crt/aws-crt-cpp/crt/s2n/tls/s2n_config.c:360
#3  0x00007ffff78bfa84 in s_s2n_ctx_destroy (s2n_ctx=0x82ba20) at crt/aws-crt-cpp/crt/aws-c-io/source/s2n/s2n_tls_channel_handler.c:1292
#4  0x00007ffff78c0bd1 in s_tls_ctx_new (alloc=0x7ffff7dd1620 <Aws::get_aws_allocator()::wrapper>, options=0x7fffffffbb68, mode=S2N_CLIENT) at crt/aws-crt-cpp/crt/aws-c-io/source/s2n/s2n_tls_channel_handler.c:1613
#5  0x00007ffff78c0c3c in aws_tls_client_ctx_new (alloc=0x7ffff7dd1620 <Aws::get_aws_allocator()::wrapper>, options=0x7fffffffbb68) at crt/aws-crt-cpp/crt/aws-c-io/source/s2n/s2n_tls_channel_handler.c:1625
#6  0x00007ffff783b758 in Aws::Crt::Io::TlsContext::TlsContext (this=0x7fffffffbcd0, options=..., mode=Aws::Crt::Io::TlsMode::CLIENT, allocator=0x7ffff7dd1620 <Aws::get_aws_allocator()::wrapper>) at crt/aws-crt-cpp/source/io/TlsOptions.cpp:423
#7  0x00007ffff773ebe2 in Aws::InitAPI (options=...) at aws-cpp-sdk-core/source/Aws.cpp:79
#8  0x0000000000400a2a in main () at reproduce.cpp:10

Valgrind output:
==176222== Memcheck, a memory error detector
==176222== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==176222== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==176222== Command: ./reproduce
==176222==
==176222== Invalid read of size 8
==176222==    at 0x52E166F: s2n_x509_trust_store_wipe (s2n_x509_validator.c:135)
==176222==    by 0x52B0987: s2n_config_cleanup (s2n_config.c:125)
==176222==    by 0x52B1372: s2n_config_free (s2n_config.c:360)
==176222==    by 0x528FA83: s_s2n_ctx_destroy (s2n_tls_channel_handler.c:1292)
==176222==    by 0x5290BD0: s_tls_ctx_new (s2n_tls_channel_handler.c:1613)
==176222==    by 0x5290C3B: aws_tls_client_ctx_new (s2n_tls_channel_handler.c:1625)
==176222==    by 0x520B757: Aws::Crt::Io::TlsContext::TlsContext(Aws::Crt::Io::TlsContextOptions&, Aws::Crt::Io::TlsMode, aws_allocator*) (TlsOptions.cpp:423)
==176222==    by 0x510EBE1: Aws::InitAPI(Aws::SDKOptions const&) (Aws.cpp:79)
==176222==    by 0x400A29: main (reproduce.cpp:10)
==176222==  Address 0x118 is not stack'd, malloc'd or (recently) free'd
==176222==
==176222==
==176222== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==176222==  Access not within mapped region at address 0x118
==176222==    at 0x52E166F: s2n_x509_trust_store_wipe (s2n_x509_validator.c:135)
==176222==    by 0x52B0987: s2n_config_cleanup (s2n_config.c:125)
==176222==    by 0x52B1372: s2n_config_free (s2n_config.c:360)
==176222==    by 0x528FA83: s_s2n_ctx_destroy (s2n_tls_channel_handler.c:1292)
==176222==    by 0x5290BD0: s_tls_ctx_new (s2n_tls_channel_handler.c:1613)
==176222==    by 0x5290C3B: aws_tls_client_ctx_new (s2n_tls_channel_handler.c:1625)
==176222==    by 0x520B757: Aws::Crt::Io::TlsContext::TlsContext(Aws::Crt::Io::TlsContextOptions&, Aws::Crt::Io::TlsMode, aws_allocator*) (TlsOptions.cpp:423)
==176222==    by 0x510EBE1: Aws::InitAPI(Aws::SDKOptions const&) (Aws.cpp:79)
==176222==    by 0x400A29: main (reproduce.cpp:10)

Possible Solution
From the backtrace, it seems incorrect for s_s2n_ctx_destroy (frame #3) to pass a null config to s2n_config_free, given that s2n_config_free doesn't perform a null check. But how come the config is null and the init code path is calling cleanup functions?
As far as I can tell, this is what happens:

The first Aws::InitAPI calls Aws::InitializeCrt → Aws::New<Aws::Crt::ApiHandle> → Aws::Crt::ApiHandle::ApiHandle → Aws::Crt::s_initApi → aws_mqtt_library_init → aws_io_library_init → aws_tls_init_static_state → s2n_disable_atexit, which sets atexit_cleanup = false.
aws_tls_init_static_state then calls s2n_init, which sets initialized = true.
The first Aws::ShutdownAPI calls Aws::CleanupCrt → Aws::Delete<Aws::Crt::ApiHandle> → Aws::Crt::ApiHandle::~ApiHandle → aws_s3_library_clean_up → aws_http_library_clean_up → aws_io_library_clean_up → aws_tls_clean_up_static_state → s2n_cleanup. initialized is still true and atexit_cleanup is still false.
The second Aws::InitAPI calls Aws::InitializeCrt → Aws::Crt::ApiHandle::ApiHandle → Aws::Crt::s_initApi → aws_mqtt_library_init → aws_io_library_init → aws_tls_init_static_state → s2n_disable_atexit, which fails since initialized is true.
aws_tls_init_static_state sets s_s2n_initialized_externally = true and therefore doesn't call s2n_init.
Aws::InitAPI → Aws::Crt::Io::TlsContext::TlsContext → aws_tls_client_ctx_new → s_tls_ctx_new → s2n_config_new fails since s2n_init hasn't been called.
s_s2n_ctx_destroy is called due to the above failure.
s2n_config_free is not prepared for freeing a half-initialized s2n_ctx.

I haven't verified this, but from code inspection I think that the regression might have been introduced in https://github.com/awslabs/aws-c-io/commit/4e462a0687d00d18cfdece3cd7a427d8a9b2e13d since before that change the return value of s2n_disable_atexit did not affect whether aws_tls_init_static_state calls s2n_init.
To me it looks like the problem is that Aws::ShutdownAPI doesn't fully clean up the s2n state, so the fix I came up with is to let s2n_cleanup_atexit_impl reset initialized and atexit_cleanup to their original values:
--- a/crt/aws-crt-cpp/crt/s2n/utils/s2n_init.c
+++ b/crt/aws-crt-cpp/crt/s2n/utils/s2n_init.c
@@ -88,6 +88,9 @@ static bool s2n_cleanup_atexit_impl(void)
     /* the configs need to be wiped before resetting the memory callbacks */
     s2n_wipe_static_configs();

+    initialized = false;
+    atexit_cleanup = true;
+
     return s2n_result_is_ok(s2n_rand_cleanup_thread()) &&
            s2n_result_is_ok(s2n_rand_cleanup()) &&
            s2n_result_is_ok(s2n_locking_cleanup()) &&

Additional Information/Context
No response
AWS CPP SDK version used
1.9.352
Compiler and Version used
gcc (GCC) 8.3.1 20190311 (Red Hat 8.3.1-3)
Operating System and version
CentOS 7.9.2009

Got the very same problem, was just going to open an issue
Same backtraces, same conclusions on investigation: problem is initialized is true in s2n_init.c at the moment of re-initialization. Didn't try to fix it though

Trying to reproduce this, but I'm not seeing any crash on Mac. @EgorkaZ which OS and SDK version are you seeing this on?

OS: Ubuntu 20.04
SDK: 1.9.342
Can try it on Mac. AFAIR the code, it should reproduce there too. @jmklix

We have fixed some memory leaks and changed the build process since this was opened. Can you confirm if you are still seeing this crash?

We have fixed some memory leaks and changed the build process since this was opened. Can you confirm if you are still seeing this crash?

I see no crash with version 1.10.49.


Update python autogenerated client code to be in sync

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

 Thanks!

Just for the history - in sync with what? Is this a particular released version of the API that we can state here, so anyone looking at the commit can cross-reference?

This change updates python SDK GCP client API in sync with the current Google internal definition. This is similar to other update API changes done to this folder.

I understand. Can you put the version (not "current" but the number) in the commit description?

Oh, do you mean it does not have a release / version number at the moment?

Right. This is to enable end-to-end testing and we don't have a release number yet.

Run Python PostCommit

It seems "This change updates python SDK GCP client API in sync with the current Google internal definition." is a good commit message and PR description. Both of these are important for historical context.

Updated commit message. PTAL, thanks!

Kenn, can you take another look? Thanks.

I just realize I can squash and merge rather than work through how you should fix up the commit history. LGTM!


Not able to embed YouTube link

I am using medium-editor-insert-plugin in my platform When I have trying to add youtube video on the editor.
It is showing video link in the editor instead of iFrame then I have tried same think on your demo page http://linkesch.com/medium-editor-insert-plugin/ and facing the same problem there as well

Sorry my fault


Hard-coded timeout is too short in search request on PEPS

Bug description
When a search request is done, there is an hard-coded timeout in "request" library. This timeout is 5 seconds and sometimes (depending on the charge) PEPS needs more time to initiate the http connection. So an error occurs.
Currently, the errors occurs statistically every 100 requests on PEPS.
Bug correction proposal: Allow changing this 5 seconds timeout to an higher value with a parameter
Python line in the script that generate error
When executing a large number of search request on PEPS like that:
products_ipage, estimated_total_number = dag.search(page=1, items_per_page=200,raise_errors =True, **search_criteria)

Output
Skipping error while searching for peps QueryStringSearch instance:
Traceback (most recent call last):
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/connectionpool.py", line 466, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/connectionpool.py", line 461, in _make_request
    httplib_response = conn.getresponse()
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/http/client.py", line 1347, in getresponse
    response.begin()
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/http/client.py", line 307, in begin
    version, status, reason = self._read_status()
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/http/client.py", line 268, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/socket.py", line 669, in readinto
    return self._sock.recv_into(b)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/ssl.py", line 1241, in recv_into
    return self.read(nbytes, buffer)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/ssl.py", line 1099, in read
    return self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/connectionpool.py", line 798, in urlopen
    retries = retries.increment(
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/util/retry.py", line 550, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/packages/six.py", line 770, in reraise
    raise value
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/connectionpool.py", line 714, in urlopen
    httplib_response = self._make_request(
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/connectionpool.py", line 468, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/urllib3/connectionpool.py", line 357, in _raise_timeout
    raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='peps.cnes.fr', port=443): Read timed out. (read timeout=5)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/eodag/plugins/search/qssearch.py", line 961, in _request
    response = requests.get(
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/requests/api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/work/scratch/env/koleckt/.conda/envs/dev-py3.8/lib/python3.8/site-packages/requests/adapters.py", line 532, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='peps.cnes.fr', port=443): Read timed out. (read timeout=5)

Environment:

EODAG version: latest

Additional context
Data provider is PEPS.

Hello @koleckt , and thanks for submitting this issue. Such a feature is already available on the develop branch and will be available with the next stable version.
See https://github.com/CS-SI/eodag/pull/841
This timeout can be set in your ~/.config/eodag/eodag.yml (peps.search.timeout), or using environment variable:
os.environ["EODAG__PEPS__SEARCH__TIMEOUT"] = "10"


[DO NOT MERGE] Event recording modification in anticipation of modifications to LOAs for some RPs

This change should not affect current behaviour.
This change amends Policy to allow it to make a better decision about which of the LoAs in an RPs config should be reported as minimum, and which as required (in Verify, believed to mean 'preferred'). This is not expected to change the behaviour for any current RPs.
It removes the assumption that the list of LoAs is ordered, in anticipation of changes being planned to permit some services to make a request with a different ordering in order to satisfy different behaviours.
The key changes are in:

//hub/policy/domain/controller/EidasCountrySelectedStateController.java
//hub/policy/domain/controller/IdpSelectedStateController.java

In each, instead of assigning the first level in the list to minimum, and the last to required, the lowest and highest are assigned respectively.

Planning complete and we're working on a different PR for the hub changes.


Reverse Script

Is there a way to revert back after using this script ?

No, at the moment.
I will try to make it in the near future.

First steps in new version!

Hello im trying to undo all the tweaks but I cant manage to do that. Any steps on how I can reverse the tweaks?

How to undo this?


Updated to .NET Standard

Thanks for your library :-)

Hi again,
Yesterday I run out of time and couldn't run tests on my macOS —we could move such to xUnit in a future too.
Today I confirm everything keeps working after moving to .NET Standard: all tests keep green and the solution builds just fine —did this on Windows with VS 2017.
The project's ready for building in Release and uploading a new version to NuGet, would it be possible you make such please? We'd like to consume such in
https://github.com/Microsoft/TailwindTraders-Mobile
which will for sure give some visilibity of the work you're doing :-)
Thanks again,
—Marcos

Thanks! I will publish new version tomorrow.

Ping, please :-)


auth.config storage with localForage

Steps to reproduce
(First please check that this issue is not already solved as described
here)

[x] Tell us what broke. The more detailed the better.
[ ] If you can, please create a simple example that reproduces the issue and link to a gist, jsbin, repo, etc.

Trying to configure feathers-client with authentication storage fails. The docs suggest using appropriate storage items for localStorage and one of those suggestions is using localForage. However, the localForage is asynchronous and the Storage object for it returns promises. Is there any example on interfacing localForage with the authentication-client
Expected behavior
import feathers from '@feathersjs/feathers'
import socketio from '@feathersjs/socketio-client'
import auth from '@feathersjs/authentication-client'
import io from 'socket.io-client'
import localForage from "localforage";

const feathersClient = feathers()
  .configure(socketio(socket))
  .configure(auth({ storage: localForage })) // should work?

and the localForage interface
interface LocalForageDbMethodsCore {
    getItem<T>(key: string, callback?: (err: any, value: T) => void): Promise<T>;

    setItem<T>(key: string, value: T, callback?: (err: any, value: T) => void): Promise<T>;

    removeItem(key: string, callback?: (err: any) => void): Promise<void>;

    clear(callback?: (err: any) => void): Promise<void>;

    length(callback?: (err: any, numberOfKeys: number) => void): Promise<number>;

    key(keyIndex: number, callback?: (err: any, key: string) => void): Promise<string>;

    keys(callback?: (err: any, keys: string[]) => void): Promise<string[]>;

    iterate<T, U>(iteratee: (value: T, key: string, iterationNumber: number) => U,
            callback?: (err: any, result: U) => void): Promise<U>;
}

Actual behavior
Argument of type '{ storage: LocalForage; }' is not assignable to parameter of type 'FeathersAuthClientConfig'.
  Types of property 'storage' are incompatible.
    Type 'LocalForage' is not assignable to type 'Storage'.
      Types of property 'length' are incompatible.
        Type '(callback?: ((err: any, numberOfKeys: number) => void) | undefined) => Promise<number>' is not assignable to type 'number'.
     9 | const feathersClient = feathers()
    10 |   .configure(socketio(socket))
  > 11 |   .configure(auth({ storage: localForage }))

System configuration
Typescript 3.0.1
Windows 10 - 64 bit
Module versions (especially the part that's not working):
"dependencies": {
    "@feathersjs/authentication-client": "^1.0.2",
    "@feathersjs/feathers": "^3.1.7",
    "@feathersjs/socketio-client": "^1.1.0",
    "@types/feathersjs__authentication-client": "^1.0.4",
    "@types/feathersjs__feathers": "^3.0.4",
    "@types/feathersjs__socketio-client": "^1.0.1",
<EMAIL_ADDRESS>"^1.4.32",
    "axios": "^0.18.0",
    "feathers-vuex": "^1.4.8",
    "localforage": "^1.7.2",
    "register-service-worker": "^1.0.0",
    "socket.io-client": "^2.1.1",
    "vue": "^2.5.17",
    "vue-class-component": "^6.0.0",
    "vue-property-decorator": "^7.0.0",
    "vue-router": "^3.0.1",
    "vuelidate": "^0.7.4",
    "vuex": "^3.0.1"
  },

NodeJS version:
npm -v > 5.6.0

Ignore the typings. It will work with an asynchronous storage.

All typings have been fixed in Feathers v4 authentication. Please see the migration guide for more information. Closing this issue in order to archive this repository. Related issues can be opened at the new code location in the Feathers main repository.


Revert "Explicitly skip PyPy on Windows"

This should work now that the following has been resolved: https://github.com/conda-forge/scipy-feedstock/issues/249
This reverts commit dd273ced3a9eea7693e48b4058c1988bc35abeaa.

Checklist

[X] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

This is in contradiction to #60. We may still want to drop PyPy, but short-term I'd just like to check to see if https://github.com/conda-forge/scipy-feedstock/issues/249 has been resolved from our side.


How to getAccessToken with resource or get id_token ?

I've followed this guide (http://www.redbaronofazure.com/?p=7566) to add a few custom claims to azure AD policy and i'm trying to get the onpremisessamaccountname . How can I specify resource when trying to get access token OR how do I get the id_token with the access_token ?

Please open an issue on https://github.com/thenetworg/oauth2-azure. They'll be able to help you much better than we can. Cheers!


Changes needed for TestNG to work for OpenJDK tests

With Jigsaw, some tests need to be executed with only java.base module present. Some of the OpenJDK tests use TestNG.
This change includes minimal fixes to allow those tests to work.

I have reverted the un-intentional changes. My apologies.
I do, however, see that now JDK tests are failing with java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException - as of now I do not know the reason.
My hack applied to some older version of TestNG worked fine.

:+1: For the PR. Could you just update the CHANGES file to warn about the api change?
About your issue, are you running the tests with IntelliJ? Someone else has the same problem: http://stackoverflow.com/questions/36443730/java-lang-noclassdeffounderror-though-testng-is-not-imported

on java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException:
I have, for now, added jcommander classes into the testng.jar which lives in the <jtreg.home>/lib. OpenJDK tests work for me right now. That is a separate issue.
no - I am not running with IDEA.
The only way I know to reproduce the original problem is to run some of the OpenJDK tests such as:
<jtreg.home>/bin/jtreg -jdk:<jdk9.home> -javaoptions:"-limitmods java.base,java.management" java/util/concurrent/ConcurrentHashMap/ConcurrentAssociateTest.java
if I run that without my hack, it is failing with
java.lang.NoClassDefFoundError: org/xml/sax/SAXException
I will look into changing the CHANGES
I was not aware of that before.

Ok, maybe a dependency issue.
Ok
Yes

This ClassNotFoundException is weird, I verified that JCommander is listed as a compile dependency in both build.gradle and Build.kt.

I have updated the repo with an extra line in CHANGES.txt. Did that on Fri, I think.
What would happen next?
Shura

On Apr 6, 2016, at 6:18 AM, Julien Herr<EMAIL_ADDRESS>wrote:
Ok, maybe a dependency issue.
Ok
Yes
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/cbeust/testng/pull/1018#issuecomment-206366496

:+1:
Next step: waiting @cbeust approval and the merge :)

Looks like we're down to just the removal of initLogger. Since this builds, I'm guessing TestNG doesn't use it and since it's in internals, I guess we're fine.
Merging!

Next step for you @shurymury: use the TestNG SNAPSHOT to confirm you no longer need your custom version.


Unify typography and color names between code and figma

body8 in our code is body4 in Figma
Are there other examples of this?

We have a design system for this now and professor is cleaning up figma


🚀 Feature: Ingest groups from Azure Entra ID based on a common parent group

🔖 Feature description
Using the microsoftGraphOrg provider, we want to ingest groups into Backstage based on their membership in one or multiple parent groups in Azure Entra ID. We don't want to explicitly specify the groups we want to ingest in the Backstage config.
🎤 Context
We have a rather big Azure Entra ID organization, with 100k+ groups. Obviously, we don't want to ingest them all.
However, we want to ingest some specific groups that belong to teams that should be part of the Backstage catalog.
Now, currently the way how we ingest groups is by adding their ids directly in the group.filter option of the provider config:
catalog:
  providers:
      microsoftGraphOrg:
        default:
          ...
          group:
            filter: "id in ('6725ea28-2b5c-4bf8-b553-7bc09463a490', '52bc345a-80b2-4371-bfb8-456a2eb423ad')"

This approach has at least two down-sides:

It does not scale: While this works for 2, 3 groups, with 10+ groups this quickly becomes unmanagable.
It requires a restart of our service/container, to make sure an update to the config is taking effect. This is cumbersome and a lot of overhead for just adding one more group to our catalog.

✌ Possible Implementation
Two ideas:
(1) Add a new config option, analog to the existing userGroupMember, e.g. groupGroupMember (which probably needs a better name 😏), to ingest groups which are members of the groups matching the specified filter/search.
(2) Alternatively, the existing userGroupMember property could change its semantics and not only ingest users but also groups (e.g. by being able to specify the type of objects to ingest, defaulting to user)
Are we missing a way how to fulfill our requirement with today's Backstage features and config?
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Happy to provide/collaborate on a PR here. Curious about your thoughts if such a feature makes sense for Backstage and what would the most suitable way to implement this

I just created a PR with a rather minimalistic change that would enable our use-case: https://github.com/backstage/backstage/pull/23048


[WIP][FNDJEN-1571] Use scripts directly from CJD

The install-plugins.sh script is now part of the official CJD Docker image.
@oleg-nenashev
NOTE: still in progress, do not merge.

still in progress


upgraded minio to pass security scans

Ticket Link #714
Description

updated minio to pass security scans

Reminders:

[x] Be mindful of impacts of changing Major/Minor/Patch versions of each elixir app

[x] If updating patch version, are you sure there are no chart changes required to maintain functionality? If so, you should bump minor version instead.
- [] If updating Major or Minor versions , did you update the sauron chart configuration?
- [ ] If changing elixir code in an "app", did you update the relevant version
in mix.exs?
- [ ] If altering an API endpoint, was the relevant postman collection updated?
- [ ] If a new version of smart_city is being used (new fields on a struct), were the relevant postman collections updated?


Dont install dev requirements in runtime mode

For the runtime container, installing the dev requirements list results in some dep mismatches.
It's ok for building, but for runtime let's just leave these off and let the user install what they want anyway.

retest Ubuntu-CPU please
retest Ubuntu-GPU-multi please
retest Ubuntu-GPU-single please
retest code-check please
retest gpu-non-pip-multi please
retest cpu-pycpp please
retest gpu-pycpp please


Support logging tracing span enter/exit

I would find it useful to get a msg when we enter/exit a span. Would you accept a PR that logs this info when under the feature trace?

Can you elaborate a bit, please? Shouldn't this be up to the code under test?

Nevermind, I think this is already possible. I didn't understand env_logger

Actually a change is needed to this library to allow users to log span events.
Suppose a user asks for trace events with RUST_LOG=trace.
With this change we get span events that look like this:
Mar 21 18:48:48.417  INFO open{self=DeviceNode { id: 2 }}: evdi::device_node: new
Mar 21 18:48:48.418  INFO open{self=DeviceNode { id: 2 }}: evdi::device_node: enter
Mar 21 18:48:48.418  INFO open{self=DeviceNode { id: 2 }}:status{self=DeviceNode { id: 2 }}: evdi::device_node: new
Mar 21 18:48:48.418  INFO open{self=DeviceNode { id: 2 }}:status{self=DeviceNode { id: 2 }}: evdi::device_node: enter
Mar 21 18:48:48.418  INFO open{self=DeviceNode { id: 2 }}:status{self=DeviceNode { id: 2 }}: evdi::device_node: exit
Mar 21 18:48:48.418  INFO open{self=DeviceNode { id: 2 }}:status{self=DeviceNode { id: 2 }}: evdi::device_node: close time.busy=73.4µs time.idle=113µs
Mar 21 18:48:48.422  INFO open{self=DeviceNode { id: 2 }}: evdi::device_node: exit
Mar 21 18:48:48.422  INFO open{self=DeviceNode { id: 2 }}: evdi::device_node: close time.busy=4.22ms time.idle=122µs

Without this change they would get the current span context as part of the log lines for events, but not span events.
         let subscriber = ::tracing_subscriber::FmtSubscriber::builder()
+            .with_span_events(tracing_subscriber::fmt::format::FmtSpan::FULL)
             .with_env_filter(::tracing_subscriber::EnvFilter::from_default_env())
             .finish();

I'm not sure if the filter should be FULL, or if this should be configurable.

Hm, interesting. I wasn't even aware of this functionality. Seems to be purely a policy decision. That being said, I am not opposed to it on the grounds that #[test] is meant for reasonably small tests and there having a bit more information is presumably helpful and not generating too much noise. Also, the timing information seems nice. I agree that ideally that would be configurable, but I am not sure there is a good way to go about that. So what you propose seems like a sensible default.

This feels a little hacky, but it might be nice to read the filter from an environment variable. Playing around with this in a fork, I've found myself wanting different filters when debugging different sorts of issues.


Random photo endpoint

I have implemented the random photo endpoint as mentioned in issue #17. I have added tests and also manually tested the endpoint in an app.
I'd just like to clarify if featured=true is the correct way of requesting featured images in the query string? I'm not exactly sure how to check if the image I was getting back was featured but assumed because the downloads were high!
If there are any changes you want made just let me know, I'm happy to help!

Hi @DannyWeeks,
Thanks a lot for your contribution.
For the featured=true, you're right. It's the good way to retrieve the featured image.
I think it could be interesting to pass an array to the 'random', instead of multiple parameters. I think it will be a lot easier to only pass specific parameters to the method.
So, to retrieve a random photo of coffee we could do Photo.random([‘query’ => ‘coffee’) instead of Photo.random(null,null,'', ‘coffee').
What do you think?
Everything else looks perfect. :smile:
Thanks again!

Yeah, using an array is a much more intuitive way of filtering the random photos! I will make the necessary changes now.
In my manual testing I seem to always be given the photo with the id of 71cd1rWqO8M when requesting a featured image, any ideas why this might be happening?

@DannyWeeks Yeah that looks like an API bug. I'll get a fix in place.

Hey @dechuck I've updated to use the array, I wasn't 100% sure how to explain it in the readme. Let me know what you think! :)

Hey @DannyWeeks,
Everything looks good to me. I will merge it into master and update the tag.
Again, thanks a lot for your contribution, it's really appreciated.

No worries @dechuck, glad I could help!


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

\Python\Python37\lib\site-packages\visualkeras\layered.py", line 65, in layered_view
for index, layer in enumerate(model.layers):
AttributeError: 'str' object has no attribute 'layers'

You need to pass a valid keras model to visualkeras, not a string.


Add 1.16 conformance job

This commit adds 1.16 e2e conformance job and removes 1.13 e2e
conformace job

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Depends on : https://github.com/theopenlab/openlab-zuul-jobs/pull/676
Release note:

/retest

/test cloud-provider-openstack-acceptance-test-csi-cinder

/test cloud-provider-openstack-acceptance-test-csi-cinder

/test cloud-provider-openstack-acceptance-test-flexvolume-cinder

/test cloud-provider-openstack-acceptance-test-keystone-authentication-authorization

/test cloud-provider-openstack-acceptance-test-k8s-cinder

/assign @adisky

/approve
/lgtm


Modulesync

we should re-run this now that we have slightly more sensible rubocops :)

In the words of @igalic
\o/

Well done team!


kprobes: matchArgs improvements (for fd/file)

In kprobes, we support matchArgs selector for fd and file types with Equal, Prefix, and Postfix operators.
This PR first introduces unit-tests for all of these cases. These tests show an issue in the case of Postfix operator and we also fix this issue.
Currently, matchArgs for fd/file types support up to 2 values. This PR also increases this number for newer kernels (5.3+) to 8. It keeps that to 2 for older kernels.
Finally, we also update unit-tests to check these.
ps. Tested locally on 4.19, 5.4, 5.10, and 5.13.
Signed-off-by: Anastasios Papagiannis<EMAIL_ADDRESS>

I'm getting tests fails (I ran on latest upstream, then I tried on 5.4 with similar results)
out.test.5.4.txt
5.4:
--- PASS: TestKprobeMatchArgsFileEqual (13.53s)
--- PASS: TestKprobeMatchArgsFilePostfix (14.33s)
--- PASS: TestKprobeMatchArgsFilePrefix (18.18s)
--- FAIL: TestKprobeMatchArgsFdEqual (82.54s)
--- FAIL: TestKprobeMatchArgsFdPostfix (76.45s)
--- FAIL: TestKprobeMatchArgsFdPrefix (81.63s)

5.19:
--- PASS: TestKprobeMatchArgsFileEqual (8.66s)
--- PASS: TestKprobeMatchArgsFilePostfix (10.43s)
--- PASS: TestKprobeMatchArgsFilePrefix (11.79s)
--- FAIL: TestKprobeMatchArgsFdEqual (67.11s)
--- FAIL: TestKprobeMatchArgsFdPostfix (61.51s)
--- PASS: TestKprobeMatchArgsFdPrefix (19.03s)

@olsajiri I haven't tested them on 5.19.
On 5.4.182 both with:
CGO_LDFLAGS=-L$(realpath ./lib) go test -gcflags="" -c ./pkg/sensors/tracing/ -o go-tests/sensor-tracing.test
time sudo TETRAGON_LIB=$(realpath ./bpf/objs/)  CGO_LDFLAGS=-L$(realpath ./lib) LD_LIBRARY_PATH=$(realpath ./lib) ./go-tests/sensor-tracing.test

and
sudo TETRAGON_LIB=$(realpath ./bpf/objs/) LD_LIBRARY_PATH=$(realpath ./lib) /usr/local/go/bin/go test -p 1 -parallel 1 -gcflags="" -timeout 20m -failfast -cover ./pkg/sensors/...

I cannot see any issues. Even in the case of these that run successfully in your case i.e.
--- PASS: TestKprobeMatchArgsFileEqual (13.53s)
they seem to be very slow:
$ time sudo TETRAGON_LIB=$(realpath ./bpf/objs/)  CGO_LDFLAGS=-L$(realpath ./lib) LD_LIBRARY_PATH=$(realpath ./lib) ./go-tests/sensor-tracing.test -test.run TestKprobeMatchArgsFileEqual &> /dev/null

real	0m2.920s
user	0m2.434s
sys	0m1.500s

(on a gcloud VM with 4 vCPUs and 16GB DRAM).
Maybe a race? I will check further...

I used 4 CPUs with 8GB, after adding another 8GB it's much faster, but still failing, I'll try to debug that

Always the same tests are failing?

Always the same tests are failing?

yes


kdiff3 lacks icons/themes

Issue description
kdiff3 comes without access to kde icons
Steps to reproduce
nix-shell '<nixpkgs>' --pure -p pkgs.kde4.kdiff3.out
kdiff3

opens the window with icons missing
Technical details
$ nixos-version
16.09beta235.49c43db (Flounder)
$ nix-env --version
nix-env (Nix) 1.11.4
$ nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"16.09beta235.49c43db"

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
Nix version: (run nix-env --version)
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)

this is still an issue in unstable, any fix in sight?

ever since i enabled plasma5 this works out, so i think there are system path elements missing for kdiff3 on its own

cc @ttuegel

This looks to be fixed.


MTSRE-259 | integrate status reporting the hard way

Implementation details
main.go runs a central heartbeat reporter loop whose purpose is to periodically report the heartbeat which the addon intends to report. This central heartbeat reporter loop is setup via the following way
https://github.com/openshift/reference-addon/blob/ecfb850b2f8c10a603b8b3000aa3a3f0b11ef4f2/cmd/reference-addon-manager/main.go#L98-L107
https://github.com/openshift/reference-addon/blob/ecfb850b2f8c10a603b8b3000aa3a3f0b11ef4f2/internal/addoninstancesdk/sdk.go#L53

ReconcilerWithHeartbeat is just an interface which can be implemented by a Reconciler struct which happens to have some additional methods required for heartbeat reporting to happen. More on ReconcilerWithHeartbeat later :)

With every iteration of the heartbeat reporter loop, latest heartbeat is reported concurrently
https://github.com/openshift/reference-addon/blob/ecfb850b2f8c10a603b8b3000aa3a3f0b11ef4f2/internal/addoninstancesdk/sdk.go#L79-L111

btw, a heartbeat is a metav1.Condition object only.

ReconcilerWithHeartbeat is essentially any Reconciler struct which implements some additional methods which are required for by the heartbeat reporter.
https://github.com/openshift/reference-addon/blob/ecfb850b2f8c10a603b8b3000aa3a3f0b11ef4f2/internal/addoninstancesdk/sdk.go#L25-L31
From the perspective of ReferenceAddonReconciler
The ReferenceAddonReconciler implements the ReconcilerWithHeartbeat by having the following methods:
https://github.com/openshift/reference-addon/blob/ecfb850b2f8c10a603b8b3000aa3a3f0b11ef4f2/internal/controllers/reference_addon_controller.go#L57-L74
And various sections of Reference Addon's codebase can use the addoninstancesdk.SetAndSendHeartbeat(..., heartbeat) function to report the heartbeat which is supposed to be reported. For example, if there's a section in the codebase that spots an error which correlates to the addon being unhealthy, then, that section of codebase can use addoninstancesdk.SetAndSendHeartbeat(r, someUnhealthyHeartbeat) to do so.
For example:
https://github.com/openshift/reference-addon/blob/ecfb850b2f8c10a603b8b3000aa3a3f0b11ef4f2/internal/controllers/reference_addon_controller.go#L43-L52

/retest

Todo: if the current approach of heartbeat reporting (r.latestHeartbeat, r.GetLatestHeartbeat(), r.SetLatestHeartbeat()) gets approved, then we can proceed with adding concurrency safety to ReferenceAddonReconciler.latestHeartbeat via mutex

/hold

closing in favor of #8 and #9


Duration object of moment.duration(stringISO) with wrong days value

The object moment.duration('P59D') returns differents values.

Correct value: 59

Use .asDays() to get the total number of days.  The .days() method is the number of days not fitting into .years() and .months()

You could also use .as('days').


Background (wallpaper) not working on some Win11 devices

Majority of computer will run this script and it works 100%, but lately some Windows 11 devices (not sure if touchscreen might be a factor) fail to setup background image on the user's desktop. When I look at log files it is all reported as successful. Any ideas or suggestions? THANK YOU.

There's something odd going on in Windows -- it seems to be timing-dependent.  I will run it on the same machine/VM 10 times in a row and one of them will not display the background.

Mike, I am impressed by how quickly you respond. THANK YOU.
I haven't noticed any issues with Windows 10 devices. This happens only on new devices that come with Windows 11 (pre-installed). I am not sure if touchscreen might be a factor for the issue.
Ilhan
Ilhan Ramic
DWS Platform Engineer
Digital Workplace Services (DWS)
Tel.<PHONE_NUMBER>
[Pearson]
Learn more at pearson.comhttp://www.pearson.com/

From: Michael Niehaus @.>
Sent: Friday, March 8, 2024 2:32 PM
To: mtniehaus/AutopilotBranding @.>
Cc: Ilhan Ramic @.>; Author @.>
Subject: Re: [mtniehaus/AutopilotBranding] Background (wallpaper) not working on some Win11 devices (Issue #10)
There's something odd going on in Windows -- it seems to be timing-dependent. I will run it on the same machine/VM 10 times in a row and one of them will not display the background.
—
Reply to this email directly, view it on GitHubhttps://github.com/mtniehaus/AutopilotBranding/issues/10#issuecomment-1986288585, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWSXDR6LFZX4JMQHGTL3AVDYXIG6DAVCNFSM6AAAAABENHCHW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWGI4DQNJYGU.
You are receiving this because you authored the thread.Message ID: @.***>

I have noticed the same thing... I am testing Autopilot with a USB stick I made using the Surface Deployment Accelerator and a 23H2 WIM which was patched to February 2024. I deployed the branding script as a blocking app in the ESP.
I noticed that the DefaultUser InstallTheme value was reset sometime before the machine and user portions of enrollment. I also tried setting the "DefaultUser\Control Panel\Wallpaper" value and it was also reset to the normal img0 wallpaper. This behavior is very consistent with self-deployment.

Hello @mtniehaus,
I think I have an explanation for this behaviour. Analysing the issue with a brand new Lenovo device with preinstalled Windows 11 23H2, I found that the image was prepared using the sysprep method. This also includes some activities after the enrolment, which are configured using unattended install. You can locate, for example, unattended.xml under C:\Windows\Panther\ as well as in the Microsoft Documentation here.

As a follow-up to my post earlier today, I have implemented the following solution in my version of a similar branding script. Please consider incorporating it into yours as well. I am not creating a pull request, as I haven't had the option to test it properly.
Add function somewhere in your script. The purpose of the function is to check existence of particular value in registry
function Test-RegistryValue {     param (         [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Path,         [parameter(Mandatory = $true)][ValidateNotNullOrEmpty()]$Value     )     try {         Get-ItemProperty -Path $Path -ErrorAction Stop | Select-Object -ExpandProperty $Value -ErrorAction Stop | Out-Null         return $true     }     catch {         return $false     } }
and then delete properties from OEMs within your script where setup Theme:
`    # Remove OEM Theme and background if present
$HKLMThemePath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes"
if (Test-RegistryValue -Path $HKLMThemePath -Value 'BrandIcon') {
Remove-ItemProperty -Path $HKLMThemePath -Name 'BrandIcon'  -Force
}
if (Test-RegistryValue -Path $HKLMThemePath -Value 'DesktopBackground') {
    Remove-ItemProperty -Path $HKLMThemePath -Name 'DesktopBackground'  -Force
}

if (Test-RegistryValue -Path $HKLMThemePath -Value 'ThemeName') {
    Remove-ItemProperty -Path $HKLMThemePath -Name 'ThemeName'  -Force
}

if (Test-RegistryValue -Path $HKLMThemePath -Value 'NoThemeInstall') {
    Remove-ItemProperty -Path $HKLMThemePath -Name 'NoThemeInstall'  -Force
}`

Has anyone tested this to see if it works?

No. I did not have chance to test it.
Thank you,
Ilhan
Ilhan Ramic
DWS Platform Engineer
Digital Workplace Services (DWS)
Tel.<PHONE_NUMBER>
[Pearson]
Learn more at pearson.comhttp://www.pearson.com/

From: ehiusb @.>
Sent: Friday, September 13, 2024 5:13 PM
To: mtniehaus/AutopilotBranding @.>
Cc: Ilhan Ramic @.>; Author @.>
Subject: Re: [mtniehaus/AutopilotBranding] Background (wallpaper) not working on some Win11 devices (Issue #10)
Has anyone tested this to see if it works?
—
Reply to this email directly, view it on GitHubhttps://github.com/mtniehaus/AutopilotBranding/issues/10#issuecomment-2350230590, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWSXDR3DCSNJ6G6GR6C5HQLZWNIONAVCNFSM6AAAAABENHCHW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQGIZTANJZGA.
You are receiving this because you authored the thread.Message ID: @.***>

I am running into this issue as well. I was having weird behavior with the theme in general and almost scrapped using those settings entirely, but then I discovered that the Windows 10 theme configuration differs from the Windows 11 configuration in regards to how Dark Mode is set.
The Autopilot.theme file that is included in the script is missing at least one setting for Dark Mode. It only has SystemMode=Dark and should have:
SystemMode=Dark AppMode=Dark

@kcyberman17
I use this to disable Spotlight, and it's working well so far for me.
# Disable Windows Spotlight features
$spotlightPath = "HKLM:\TempUser\Software\Policies\Microsoft\Windows\CloudContent"
New-ItemProperty -Path $spotlightPath -Name "DisableWindowsSpotlightFeatures" -Value 1 -PropertyType DWord -Force

But disabling that didn't fix my issue. Even though my theme was selected as the default, a different picture was selected, and I ended up setting the default picture to the default profile.
# Add Wallpaper settings
$desktopPath = "HKLM:\TempUser\Control Panel\Desktop"
New-ItemProperty -Path $desktopPath -Name "WallPaper" -Value "c:\windows\web\wallpaper\MYPICTURE.png" -PropertyType String -Force
New-ItemProperty -Path $desktopPath -Name "WallpaperStyle" -Value "0" -PropertyType String -Force

Note. I did WallpaperStyle to 0 because I wanted to be in the Center.
Note2. Disabling Spotlight with policy in Intune helped me with an in-place upgrade from 23H2 to 24H2 to not change the picture and keep it as it is, so make sure you set that up as well.

The changes to disable Spotlight have been merged, closing this.  If there are still issues, then it's likely a different cause so someone can open a new issue.


Where is this python script？

Hello，i want to know where can find this script？

Hi,
Unfortunately, I wasn't able to find this script since this research was done many years ago. As far as I remember that was a simple script to look for call from specific libraries e.g. ADVAPI32. You can achieve the same functionality by doing cat your_log | grep ADVAPI32 on Linux.


requirements could not be resolved / 4.4.1 / php_codesniffer 3.0.0RC3

Problem 1
- felixfbecker/language-server v4.4.1 requires squizlabs/php_codesniffer 3.0.0RC3 -> satisfiable by squizlabs/php_codesniffer[3.0.0RC3] but these conflict with your requirements or minimum-stability.
- felixfbecker/language-server v4.4.0 requires squizlabs/php_codesniffer 3.0.0RC3 -> satisfiable by squizlabs/php_codesniffer[3.0.0RC3] but these conflict with your requirements or minimum-stability.
- Installation request for felixfbecker/language-server ^4.4 -> satisfiable by felixfbecker/language-server[v4.4.0, v4.4.1].
Installation failed, reverting ./composer.json to its original content.

The error message is pretty clear - the dependencies could be resolved, but conflict with your requirements or minimum-stability. You need to lower you minium-stability.
This is the second result if google your error message: http://webtips.krajee.com/setting-composer-minimum-stability-application/

Ok I have to be more specific, the mentioned error message appears after a clean install of composer (without setting anything) and using the provided install command (from this projects readme)

composer require felixfbecker/language-server

and executing that without creating anything else with composer.

Did you try one of the options in the linked blog post?

If I execute
composer config minimum-stability dev and then use composer require felixfbecker/language-server it works, but I don't see what the consequences of this setting now are.
Anyway it would be good if the provided installation command would work out of the box.

The consequences are that composer will now install dependencies of a lower stability. I would recommend you to set preferStable: true as explained in the blog post (3), that way it will still use stable versions if available. CodeSniffer will go away soon anyway.


Fix godoc badge.

Coverage decreased (-0.01%) to 36.462% when pulling d1bc112f241dff6508a07bff38c083f7c6c04b19 on pires:fix_godoc_badge into 43f0fa5c0be7a3d0e20a66a88b67de49b57c2337 on mesos:master.


⚠ Fetchers has degraded performance

In 14b3ef9, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 352 ms

Resolved: Fetchers performance has improved in 83ffbb0.


update simianfacter for flatten facter3 hash of facts

case statement, for whatever reason facter2/puppet3's 'facts' verb
behavior doesn't match 4's... but it works!

Updated to reflect requested change

Does this look acceptable?


Routing doesn't seem to work for when doing single e.g need /account/

My controller name is AccountsController, I would like the user to navigate to /account and do the index action.
I tried,
MvcRouter::public_connect('', array('controller' => 'documentation_nodes', 'action' => 'index'));
and is doesn't seem to work, I've done de-activating, activating and saved permalinks. Nothing. Thanks in advance.

I want to replicate WooCommerce account pages.


docs: add mdx storybook formatting for Button

pull this one and let me know what ya think!
pretty slick imo and easy to use since it's just standard markdown + a few tags for the stories

No notes - very sick!!!


Include MTU adjustment checks in remote VLAN examples

Expected Behavior
The MTU value of the interface in NSC should not be bigger than the MTU value set on base interface
Current Behavior
MTU is not checked currently. Some failures are slipping through the CI
Failure Information (for bugs)
Some failures are slipping through the CI. The sub-interface now don't inherit the MTU from the host interface in vpp. That caused failure in MTU adjustment.
Related PRs
networkservicemesh/deployments-k8s/pull/7739
networkservicemesh/sdk-vpp/pull/656
networkservicemesh/sdk-ovs/pull/203

Seems like done


Force Topmost property to true for media window when running in windowed mode

When running in windowed mode, other windows can inadvertently cover part of the media window, and this typically results in the content being partially blocked for remote viewers.
To prevent content from being obscured by other windows partially covering the media window, force the Topmost property of the window to true.
An alternative would be to make the Topmost property configurable (similar to the main window).
Care would still need to be taken by users so that the main window doesn't get dragged over the media window if both have the Topmost property set to true.

I agree this should be optional. On a single screen it could become an annoyance, otherwise.
Alternatively, is it possible to add an option for the media window’s stay on top property to be activated only during media playback?

@strawberry-sundae Your suggestion:

Alternatively, is it possible to add an option for the media window’s stay on top property to be activated only during media playback?

I love it! It is feasible to implement, this would be a huge assistance.

Alternatively, is it possible to add an option for the media window’s stay on top property to be activated only during media playback?

@strawberry-sundae Hi. Can you elaborate on this please? It could be argued that whenever the media window is open then it is "playing" media - even if it's just an image or the black backdrop.

During our meetings, I keep OnlyM (with permanent backdrop enabled) open behind my ZOOM window. When it is time to display media, I tell ZOOM to share the OnlyM media window. Once the empty media window is being shared, I begin video playback.
Having the media window always open enables this distraction-free method of sharing media.
During most of the meeting, enabling stay-on-top would make the media window a nuisance. But once I press the play button in OnlyM’s main window, I definitely don’t want something unexpected to cover the media window. So it would make sense to then enable stay-on-top until playback of the current media item ceases.

Did my previous comment make sense?

@strawberry-sundae yes, I understand the requirement. In OnlyM, media is being rendered whenever an image, video, etc is "playing". Does this also include the "Permanent Backdrop" or the "Black Screen"? In some cases users may want "stay on top" enabled in different situations. The latest release provides a "stay on top" option for the media window. In Zoom you can set up what you need by deselecting the permanent backdrop, then showing an image in the OnlyM media window and selecting it as Zoom's share. Now whenever you play media it will be shared and whenever you stop media it will pause the share.

Closing now. I don't think I will be making further changes to this feature. @strawberry-sundae thanks for your help.


first optimistic stab at a wsl github run

I give up for now. something is going wrong and running pypy just hangs (maybe it pops up a dialog box or something?). will try to debug on my local wsl laptop at some point.


2D Representation isn't working

Whenever I use a serie to make a 2D representation, following the example, I get almost half the serie that works, then the other half is just noise (like on old tvs).
Here's the view for the images that don't compute
I don't know where it comes from, as it works on the OSIRIX desktop viewer.
It's the same on the example where I load dicom files with those series.
Is there something I'm missing ?
Thanks.

Can you share the data with us by any chance?
The strange this is that half works..

Yes, I used this one from the OSIRIX samples, both on my code and the online example.
It's quite heavy.
As I just tried, it seems that with only 200 images from COLONIX, it works, so I guess it could be a memory problem (blobs being flushed and all).

Yes the problem is the following:
This dataset contains 512 x 512 x 889 = 233 046 016 voxels.
Currently AMI on passes the first 4096 * 4096 * 7 = 117 440 512 voxels to the shader.
That explains that roughly the first half looks fine and the second half doesn't.
The only reason for limiting the number of voxels was to make it working on a wider range of devices but it should be better handled. There is no perfect solutions and there are pros and cons for all:

Pass all voxels -> requires high-end graphic card
Pass only interesting packages of voxels -> can only look at the data in acquisition direction
Create several stackHelpers for each data subset -> not sure how that will look like at intersection points

So I think the best solution really depends on what you want to achieve: 2D, 3D, which orientation, which target device, etc.
Last thought is that AMI could actually already handle this dataset:
To pass data to the shaders, it packs the voxel intensities into a [rgba] texture (8 bits per channel). This OSIRIX dataset is 16 bits grayscale, meaning that [rg] could contain 1 voxel intensity and [ba] another one.
This way we can pass 2 times more voxels to the shaders than we currently do.
That would be very to have that in AMI, if you are interested I can help you get through the code and point you to the right direction as I do not know when I'll be able to fix it.

My use of the library is pretty specific.
I want to only process CT scan in sagittal view and to be able to point probes.
To be honest, I don't understand everything about voxels. I would like to help but I don't think I'm able to.
Basically what could be implemented in AMI is a way to configure the way series are shown, to be able to tweak the graphics when instanciating the library ?

FYI - working on it, still got couple of issues to resolve

Awesome ! Thank you very much.

Note - it also seems that it tries to create too many textures.

FYI - some good progress but still more cleanup/testing to do:

Please give it a try at https://fnndsc.github.io/ami/#viewers_dicom2D and let us know if it works as expected!
(you might need to clean up your cache or try in an anonymous tab)
It is not on master yet but you can access it in the #dev branch -
Cheers!


"Offline" mode

Keep pages data in localstorage
invalidate the cache via a manifest when site is updated.

Ref https://github.com/MoOx/statinamic/pull/151#issuecomment-184595116

This may help https://github.com/NekR/offline-plugin

Here is the plan:

[x] Appcache
[ ] Service worker
[ ] Don't download a data file twice. Keep it in localStorage.

service worker and/or app cache are supposed to handle the download right?

With service worker, we can control how browser download file. Appcache only kicks in whem offline

It seems that the "offline" plugin might helps indeed. Did you take a look to it?

I tried offline plugin. Not useful in ourcase since it only can index assets emited from webpack

We emit json via webpack, so are you sure that's not relevant?

We have assets file that will be copied with fs, index.html file generated by url-to-html , and "offline plugin" doesn't have a fallback option for service worker

Maybe assets in the assets folder should be "optional" (cached when downloaded?)
For the index.html we can probably make an exception.
Just asking that to see if we can integrate serviceworker easily.

Why all the troubles ? Just write a service worker logic and put it in.

"Just write", ok then :)

fyi, I'm working on service worker. A json file will never be downloaded twice.

A json file will never be downloaded twice

Haha. Appcache is doing this for us. JSON files was loaded from cache already. No don't see the benefits of writing SW anymore.
Compare browsers compatiable : appcache and sw

appcache is brutal and cache "all the things". sw is a smarter method that will allow you to cache only things already request. For big sites, appcache make no sense (too long to cache everything) and sw will make much more sense.

The simplest sw tutorial ever.
https://remysharp.com/2016/03/22/the-copy--paste-guide-to-your-first-service-worker
Will take a look at this in the next few days


Add support for custom build pipeline

Hi, I'm working on milvus-operator deployment in a private cloud environment. To fit our environment, I need to re-edit the milvus dependency helm charts (etcd, minio, pulsar, etc.) and re-build the image.
To re-build the image, I must customize the Dockerfile and Makefile, and then run make docker-build. It's not an elegant way, and it would be very hard to track the latest milvus-operator release with the pipeline. Could you please add the support for custom build in your Makefile? It would be easily to accomplish by adding something like make docker-build-with-helmcharts {Path}. Thank you.

Yes, it’s a reasonable feature. Would you like to launch a PR yourself?

@yuzs2 The version of the dependency charts are maintained in another repo, you can see the history there https://github.com/zilliztech/milvus-helm/commits/master/charts/milvus/charts. Usually we only change them when there're some vulnerability issues or other necessary optimizations. Considering about the stability, the changes will be small, and compatible with previous versions.


add apns-collapse-id header to support notification management on iOS10

@jchambers this PR is compared against master as requested

Thanks! This looks good. I'm hesitant to include it in v0.8, but expect to merge it soon.

@jchambers You are very welcome and thank you for this project. I think it's worth to include it . It is pretty safe and one can start testing and using it with iOS10 development. Anyway please drop a message once it is merged so I can update my project.

@123avi I'm really sorry for the trouble, but would you mind rebasing this against master and resolving comments so we can merge it?
Thanks!

hi @jchambers , I am not sure that I got you. it is already done

I am not sure that I got you. it is already done

So we have a couple things we need to work out here.

Sayeth Github, "this branch is out-of-date with the base branch." This means that some jerk (ahem) went and merged other things into master, and now we need this branch to be rebased onto master so it "sees" the latest changes.
The commit history for this branch is a little wacky, and includes a bunch of commits that aren't really part of The Point™ here.

To resolve both issues, I recommend:

Make sure you have a current copy of master locally.
Use interactive rebasing (git rebase -i master on your branch) to make sure everything is current and to squash everything down to (in this case) just one commit. If you're new to rebasing, I'd recommend reading up on it a bit first.

Please give a shout if you have questions or need help. Looking forward to getting this in play!

@jchambers Hi - Done. LMK if there is anything else I can assist.

@123avi There are still 22 commits in this branch's commit history. Did you actually git rebase?

yes, I did that . there were some duplicate commits for some reason, I dropped some of the duplicates, and some are not related, i.e gpg plugin etc'

Okay—I think we still need to find some way to make the commit history less noisy before we merge this, though. Do you have a good idea for how to move forward, or would you like help?

@123avi I hope you don't mind me stepping on toes, but I went ahead and did the rebasing/squashing in #367. I'll close this for now and will merge #367 as soon as I can update the docs.


DefferedParsingException while using XML mapper in SI Tooling

Description
While using XML mapper in SI Tooling, the editor shows DefferedParsingException and doesn't allow running the Siddhi app. But in SI worker, the same Siddhi app works fine.

Steps to Reproduce
Create a Siddhi app and add the following Stream definition with the XML source mapper.
@Source(type = 'http', receiver.url='http://localhost:8006/productionStream', basic.auth.enabled='false',
    @map(type='xml'))
define stream SweetProductionStream (name string, amount double);

Affected Component
SI
Version
4.2.0-alpha
Environment Details (with versions)
SI Tooling 4.2.0-alpha
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

This was fixed by https://github.com/wso2/streaming-integrator-tooling/pull/226


apply data restrictions for derived cureves

data after EE for each series variable has the same valid_date/fcst_lead combinations but can have more than one record with the same valid_date/fcst_lead (if boolMulti = FALSE - the warning will be printed).
Calculating differences on this data doesn't make sense because we can't insure the order.
If this kind of data is detected before the calculation of the derived curve - aboard the calculation with the error message
Was discovered during #101 implementation and will be included to the same branch

scorecard test use cases were changed to comply with these restrictions


Add S,C,B to haskell annotator, update annotated images

s - Message 18
c - Message 19
b - Message 20

These are coherent with the generic symbol numbers.
See

15da603c
2c4223b
2c4223

Also includes #47

#47 should invalidate/update some of decoded messages, didn't manage to compile annotate.hs locally yet to verify which ones are affected

I have a PR incoming for i and isnil incorrectly getting interpreted as operators; they're entirely new symbols.


Error when running test_ACGAN

System information
Red Hat Enterprise 7.4
Describe the current behavior
I am interested in saving the generator of a gan to onnx format. I have sampled the code from applications/test_keras_applications.py for ACGAN. When I run the code, the code fails as below:

Traceback (most recent call last):
File "/lib/python3.6/site-packages/tensorflow/python/framework/importer.py", line 427, in import_graph_def
graph._c_graph, serialized, options)  # pylint: disable=protected-access
tensorflow.python.framework.errors_impl.InvalidArgumentError: Node 'sequential_1/batch_normalization_1/cond/FusedBatchNormV3/Switch_1' expects to be colocated with unknown node 'batch_normalization_1/gamma'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "test-acgan.py", line 35, in
onnx_model = keras2onnx.convert_keras(keras_model, keras_model.name)
File "/lib/python3.6/site-packages/keras2onnx/main.py", line 92, in convert_keras
parse_graph(topology, sess.graph, target_opset, output_names)
File "/lib/python3.6/site-packages/keras2onnx/parser.py", line 497, in parse_graph
return _parse_graph_scope(graph, keras_op_table, topo, top_level, output_names)
File "/lib/python3.6/site-packages/keras2onnx/parser.py", line 473, in _parse_graph_scope
_convert_general_scope(nodes, varset)
File "/lib/python3.6/site-packages/keras2onnx/parser.py", line 204, in _convert_general_scope
subgraph, replacement = create_subgraph(sess.graph, node_list, sess, operator.full_name)
File "/lib/python3.6/site-packages/keras2onnx/subgraph.py", line 132, in create_subgraph
tf.import_graph_def(output_graph_def, name=im_scope)
File "/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "/lib/python3.6/site-packages/tensorflow/python/framework/importer.py", line 431, in import_graph_def
raise ValueError(str(e))
ValueError: Node 'sequential_1/batch_normalization_1/cond/FusedBatchNormV3/Switch_1' expects to be colocated with unknown node 'batch_normalization_1/gamma'

Code to reproduce the issue
import os
import sys
import onnx
import unittest
import keras2onnx
import numpy as np
from keras2onnx.proto import keras, is_tf_keras
from distutils.version import StrictVersion

latent_dim = 100
num_classes = 10
channels = 1
model = keras.models.Sequential()
model.add(keras.layers.Dense(128 * 7 * 7, activation="relu", input_dim=latent_dim))
model.add(keras.layers.Reshape((7, 7, 128)))
model.add(keras.layers.BatchNormalization(momentum=0.8))
model.add(keras.layers.UpSampling2D())
model.add(keras.layers.Conv2D(128, kernel_size=3, padding="same"))
model.add(keras.layers.Activation("relu"))
model.add(keras.layers.BatchNormalization(momentum=0.8))
model.add(keras.layers.UpSampling2D())
model.add(keras.layers.Conv2D(64, kernel_size=3, padding="same"))
model.add(keras.layers.Activation("relu"))
model.add(keras.layers.BatchNormalization(momentum=0.8))
model.add(keras.layers.Conv2D(channels, kernel_size=3, padding='same'))
model.add(keras.layers.Activation("tanh"))

noise = keras.layers.Input(shape=(latent_dim,))
label = keras.layers.Input(shape=(1,), dtype='int32')
label_embedding = keras.layers.Flatten()(keras.layers.Embedding(num_classes, 100)(label))

model_input = keras.layers.multiply([noise, label_embedding])
img = model(model_input)

keras_model = keras.models.Model([noise, label], img)
x = np.random.rand(1, 100).astype(np.float32)
y = np.random.rand(1, 1).astype(np.int32)

expected = keras_model.predict([x, y])
onnx_model = keras2onnx.convert_keras(keras_model, keras_model.name)

Describe the expected behaviour
As this code forms a part of the unit testing which is passing, I am curious to know why it fails when running in isolation (@denfromufa)
Thanks for your advice on this.

Did you use the pypi keras2onnx? Can you pull latest keras2onnx master instead and try? We have some fixes recently.

Indeed I did install from pypi. I've installed direct from master and it working nicely. Thanks fro getting back to me so quickly and for the advice.


Compute proeminent colors in each media

Useful for picking colors from images in ortfo/gui

No need, ortfo/gui can call ExtractColors from its backend, and that way media that was added in between db builds can have its colors extracted too.


feat: clone the registry archive and minor fixes

[x] feat: add enter key for search functionality
[x] feat: sort packages by the order of their versions
[x] feat: add registry archive functionality
[x] feat: user can login by username or email and password
[x] feat: added docs for the env variables
[x] fix: minor bug fixes

Thanks and Regards,
Henil
CC: @awvwgk @arteevraina @minhqdao @perazz

LGTM @henilp105

Sure, will patch it.


TypeError: Cannot read property 'split' of undefined

Introduction
This issue seems to be similar to #2131 and #1785. From what I have observed, it only occurs when I run react-scripts start. However, when I execute eslint src/*, the error does not occur. This may or may not be important to debugging this error.
Details
eslint-plugin-react version: ^7.24.0
Exact error message received after running react-scripts start:
[Error - 1:52:26 a.m.] ESLint stack trace:
[Error - 1:52:26 a.m.] TypeError: Cannot read property 'split' of undefined
Occurred while linting C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\src\common\components\Copyright.tsx:3
    at checkDependencyDeclaration (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint-plugin-import\lib\rules\no-extraneous-dependencies.js:133:40)
    at reportIfMissing (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint-plugin-import\lib\rules\no-extraneous-dependencies.js:187:38)
    at commonjs (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint-plugin-import\lib\rules\no-extraneous-dependencies.js:264:7)
    at checkSourceValue (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint-module-utils\moduleVisitor.js:29:5)
    at checkSource (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint-module-utils\moduleVisitor.js:34:5)
    at C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint\lib\linter\safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint\lib\linter\safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint\lib\linter\node-event-generator.js:293:26)
    at NodeEventGenerator.applySelectors (C:\Users\mahmi\Documents\GitHub\patient-self-service-portal\node_modules\eslint\lib\linter\node-event-generator.js:322:22)

Source code producing error:
import * as React from 'react';
import { Link, Typography } from '@material-ui/core';
import { SxProps } from '@material-ui/system/styleFunctionSx/styleFunctionSx';

export type CopyrightProps = {
  sx: SxProps;
};

const Copyright: React.FunctionComponent<CopyrightProps> = ({ sx }) => (
  <Typography variant="body2" color="text.secondary" align="center" sx={sx}>
    {'Copyright © '}
    <Link color="inherit" href="/">
      Affinity Patient Portal
    </Link>
    {` ${new Date().getFullYear()}.`}
  </Typography>
);

export default Copyright;

This is caused by eslint-plugin-import.
Occurred while linting C:\Users\<x>\patient-self-service-portal\src\common\components\Copyright.tsx:3
    at checkDependencyDeclaration (C:\<x>\node_modules\eslint-plugin-import\lib\rules\no-extraneous-dependencies.js:133:40)
                                                       ^^^^^^^^^^^^^^^^^^^^

See https://github.com/import-js/eslint-plugin-import/issues/2120.

@AriPerkkio Somehow, this error disappeared after fixing the issue in mui-org/material-ui#27564. I have not tried it out with your proposed solution. I am going to close this for now since the issue is gone but feel free to reopen if necessary.


Support request: unexpected new analyzer failure when no relevant change was made

Hi - I've got a new analyser failure on https://github.com/Smaug123/fsharp-prattparser/pull/9 which is a change completely unrelated to the analysers. I can't reproduce it locally on macOS. The failing run is https://github.com/Smaug123/fsharp-prattparser/actions/runs/8123334984/job/22203652378?pr=9#step:4:1 and the preceding successful run (two weeks ago) was https://github.com/Smaug123/fsharp-prattparser/actions/runs/7965613558/job/21745483323 .
Do your eyes see what might be going wrong here? The .NET SDK and fsharp-analyzers are both binary-identical between the two runs (as validated by Nix); I haven't validated that the version of G-Research.FSharp.Analyzers is binary-identical.

Hi Patrick, thanks for reaching out!
I was able to run the analyzers locally on my Windows machine.
One thing I'm not entirely sure is if we support wildcards in --analyzers-path ./.analyzerpackages/g-research.fsharp.analyzers/*/
https://github.com/ionide/FSharp.Analyzers.SDK/blob/0719b7296843dc552e68bf6143d565227f2c1b33/src/FSharp.Analyzers.Cli/Program.fs#L543-L554
The aborted output text does make me wonder if type-checking succeeded:
https://github.com/ionide/FSharp.Analyzers.SDK/blob/25ab689f9285a81ff1c782e9ac62abed0eab785c/src/FSharp.Analyzers.SDK/FSharp.Analyzers.SDK.fs#L252
I don't quite see any good reason it shouldn't. Would you mind re-running that build sometime? I'm curious if the behaviour is consistent or not.

The wildcard should be interpreted by the shell, and the analysers should never even see it. (I'll verify that when I get home.) The error is consistent in the sense that I have several open PRs on that repo, all failing in the same way.
Actually now you mention it I can boot my Macbook into NixOS and get a testing environment that's pretty close to what the Action is running. I'll do that tonight.

Yeah, I'm confident the * was interpreted by the shell as a glob and was expanded before fsharp-analyzers got to see it:

Loading analyzers from /home/runner/work/fsharp-prattparser/fsharp-prattparser/.analyzerpackages/g-research.fsharp.analyzers/0.9.3/

Huh. When I added the .NET SDK to $PATH before running the analysers, it worked. I have no idea what changed underneath me, because it used to work fine without that, but that seems to reliably fix the problem. (Before that fix, the analysers reliably failed.)

Hmm, this could explain why the design time build failed and thus type-checking no longer worked.
I'm happy you found a solution. Was running out of ideas 😌.


:bug: Set fsGroup for non-OpenShift clusters

On EKS and probably other kubernetes variants the PostgreSQL pods run as user 26. Without setting the fsGroup the storage is mounted 755 owned by root:root so postgres can't write and fails to start with a permission denied.
26 comes from the Dockerfile the image is built with https://github.com/sclorg/postgresql-container/blob/master/12/Dockerfile.centos7#L88

@fbladilo correct.


Request: An ability to "Blacklist" devices

Hey, thanks a bunch for this plugin!
Something I'd like to see added is an option to have a black list or a white list to either not show (black list) or show only (whitelist) Specific devices...
This is to kill "duplicates" problem with supported homekit bulbs showing up twice (using this plugin and yeelight official int.)
thank you.

Hello! Any updates on this?

As of 2.4.0 you can ignore a light by setting blacklist to true, e.g.:
{
  "bridge": {
    "name": "Raspberry Pi"
  },
  "accessories": [{}],
  "platforms": [
    {
      "platform": "yeelight",
      "name": "Yeelight",
      "defaultValue": {
        "aed78s": {
          "blacklist": true
        }
      }
    }
  ]
}


vps

can i run in vps server?
and how?

Just modify the bot variable with your token.
Now run npm install then npm start.
And the visit localhost:5000


Mark SE-0449 as implemented in Swift 6.0.

Marks SE-0449 as implemented in Swift 6.0.

It’s not picked to 6.0 right? so I think this may need to wait for upcoming release from main eventually once that happens.
or don’t say which version it’s on?

Swift 6.1 has been announced.

Fixed, thanks!

Should the upcoming feature be moved to the next language mode?
-UPCOMING_FEATURE(GlobalActorInferenceCutoff, 0449, 6)

 // Swift 7
 UPCOMING_FEATURE(ExistentialAny, 335, 7)
 UPCOMING_FEATURE(InternalImportsByDefault, 409, 7)
 UPCOMING_FEATURE(MemberImportVisibility, 444, 7)
+UPCOMING_FEATURE(GlobalActorInferenceCutoff, 449, 7)

(Also, the SENumber of a few upcoming features is in octal, but it probably doesn't matter.)

If there are no source-breaking changes, there should be no upcoming feature flag at all.

It looks like the implementation was updated to make it an upcoming feature flag enabled by default in Swift 6 language mode. Should it be updated to remove the flag? If so, we can merge this as-is. Otherwise, we should update this to mention the flag, since evolution proposals that add upcoming features should keep those references for documentation purposes.
If nothing in the proposal is source-breaking (I don't recall any of it being such), then the flag should probably just be removed entirely as @xwu suggested, and then it will be on by default in 6.1.

Now that https://github.com/swiftlang/swift/pull/77227 has been merged, we can merge this to match. Thanks!


SELECT * behavior should be changed

Currently, if you do a SELECT * query it will do two things.

rewrite the * to have all field names from the measurement
insert a GROUP BY * at then end of the query, which will expand out to all tag keys

This is causing a bunch of confusion and bugs. Instead, SELECT * should select all field values AND it should insert the tag keys and values in the result set.
For example if you have the following data:
cpu,host=A,region=uswest value=23.2 123450
cpu,host=B,region=useast value=65.2 123450
cpu,host=A,region=uswest value=22.3 123460

And you do this query: SELECT * FROM cpu you should get in the result set a single series. The important bit in the response is this:
{
  "columns": ["time", "host", "region", "value"],
  "values": [
    [123450, "A", "uswest", 23.2],
    [123450, "B", "useast", 65.2],
    [123460, "A", "uswest", 22.3]
  ]
}

Note that time is always the first column and the other columns are sorted lexicographically.
The insertion of the tags into the result set will need to happen at the Mapper level since the reducer may or may not know about these.
Ideally, this work will also make it possible to do queries like this:
SELECT value, host from cpu
SELECT min(value), host from cpu

A little offtopic, but is it currently possible to return time as integer - like in your example?

It is, when you make the request add the query parameter epoch=true

Great news, thanks!

Additional notes:
SELECT value, host from foo group by host, region
then host should be included in the columns
any tag keys they have in the GROUP BY statement, shouldn’t be written into the columns in the case of the SELECT *
select * from foo group by *
No tags in the columns, only group by tags


Investigate issue with Ruby 3.1/3.2 and worker fibers

Describe the bug
Currently fiber-based workers hang in Ruby 3.1/3.2 but work in Ruby 3.3+. Initial investigation is showing that pushing to a Queue from a separate thread may not be waking up a fiber. As a (temporary?) workaround, we are only allowing Fiber-based workers in Ruby 3.3+.

You might've already looked into this, but any chance this is related to the introduction of M:N scheduling in 3.3? 🤔
https://bugs.ruby-lang.org/issues/19842

I do suspect it is related to that. Basically what we are finding pre-3.3 is that in some cases when we have one Ruby thread that pushes to a queue, a fiber that is waiting on queue pop is not woken up. Due to how we need to use Rust, we need to be able to wake up fibers from another thread and queues were the logical way to do it. Note, this does not happen all the time. In many cases a queue push from another thread does resume a fiber waiting on queue pop.
Maybe it's something we are just not doing right, or maybe there's some other way to wake up a fiber from another thread. We may end up reworking our callback logic to not use queue from other thread, but instead do a captured_fiber_scheduler.fiber { queue.push } hoping that will fix it.
This is causing our fiber-based tests to not work in < 3.3. We need to do a lot more investigating here, but for now so we could get the activity worker PR out, we created this separate issue.

The other obvious question becomes, how important is pre-3.3 fiber support? 3.1 will be EOL'd in the spring and 3.2 a year after that. And of course threads work across all versions.


Feature gate update for release 1.10

This PR updates the feature gate doc to match release 1.10.

OK, folks, things are getting a bit confusing here. Can someone please clarify?

In 1.9, there's a feature named pvc-protection, which you enable with a feature gate. Is this correct?

pvc-protection is also the name of a finalizer. It's my understanding that this finalizer is available only in 1.10. Is this correct?

In 1.10, there's an admission controller named StorageObjectInUseProtection that's intended to do the same thing as pvc-protection in 1.9. Is this correct?

pvc-protection is alpha in 1.9, and StorageObjectInUseProtection is beta in 1.10. This also makes it look like it's the same feature, renamed. Is this correct? Is the underlying implementation changed? Because it looks as though you set pvc-protection differently in 1.9 than you do StorageObjectInUseProtection in 1.10. Is this correct?

Depending on answers to these questions, we need a rewrite of several related docs for 1.10. I'll try to collate them today (Wednesday, March 14).

@Bradamant3 The alpha feature "PVCProtection" has been promoted to a beta and it has been renamed to "StorageObjectInUseProtection". This is about feature gate setting.
The feature is implemented using admission controllers and finalizers:

The name of the admission controller has been changed from "PVCProtection" in 1.9 to
"StorageObjectInUseProtection" in 1.10.

"pv-protection" and "pvc-protection" are names of finalizers attached to PV/PVC objects when the feature is in action.

/assign

/approve
@tengqm based on what else I've seen of 1.10 features and docs, this looks good to me on the technical side, too. Do you think we need a separate tech review? If not, go ahead and add an /lgtm and we can merge without. If so, could you please suggest reviewers?

/lgtm

/lgtm


Redacted Mode - Tap to open profile

Tap to open profile - on Ios skin the username isnt redacted, when redacted mode is on

Fixed pending release


F1 socre is zero when using run_ner.py and run_re to fine tuning bert model

When I use run.ner.py and run_re.py scripts, i got F1 score and precision are zero for ner model and re model, I think the problem lies in the format of the training data generated by generate_data right? how do you overcome that?

Can you share some more details about the steps you performed and a sample output?

I followed the steps you have done, first I generated the data by the script generate_data.py for each IE task, and then I trained the model biobert. At the end of the training I get a file test_result.txt with a score F1 of zero, the same for the file eval_results.txt :
test_result.txt
eval_loss = 0.6333050968019458
eval_precision = 0.0
eval_recall = 0.0
eval_f1 = 0.0

eval_results.txt:
eval_loss = 0.6656930069956515
eval_precision = 0.0
eval_recall = 0.0
eval_f1 = 0.0
epoch = 3.0

The biobert model for NER assigns only the tag "O" for the tokens in the file test_predictions.txt
The same for the biobert model for relationship extraction, after generating the data and fine tuning the model biobert for RE, I get a test_result.txt file with an F1 score of zero, the same for the eval_results_ehr-re.txt file :
test_results.txt:
f1 score = 0.0
recall = 0.0
precision = 0.0
specificity = 1.0

eval_results_ehr-re.txt
eval_loss = 0.5521418023042465
eval_acc = 0.7598763697667884
eval_f1 = 0.0
eval_acc_and_f1 = 0.3799381848833942
epoch = 3.0

I guess the problem relies in data format train.txt train.tsv .. generated by data_generate.py ?

I was having issue with GCP, problem solved thanks!

Hi @ayoubharn I am having the same issue in AzureML - how exactly did you resolve it please? Thank you!


Navbar update based on userlogin

Added conditional rendering in the navigation bar template.

Unsigned users will only see Login, Sign up, and Discover icons.
Signed-in users will see Logout, Discover, Profile, and Settings icons.
Added user object in pins route rendering

Video for tested routes https://www.loom.com/share/e50a3e5f02cc496d84629ec2ea8f3ee2

The functionality looks like its working well! Can you add a tooltip to the logout button?


Remove unused argument

What does this PR do?
Remove an unused argument in compute_loss_ort() from Trainer class.
@JingyaHuang (I can not add reviewers so I ping you!)
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Closing as corrected in https://github.com/huggingface/optimum/pull/189/

Sorry, I did not see this.