module 'itk' has no attribute 'BinShrinkImageFilter'

When displaying large images I get the error bellow. I can set size_limit_2d large enough to avoid downsampling as a workaround.
This is from a relatively bare docker container. I installed with pip install itkwidgets. To my knowledge no other packages requires itk. import itk;itk.Version.GetITKVersion() yields 4.13.0.
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-26-4c0603b3ae2d> in <module>
----> 1 view(pixels,annotations=False, ui_collapsed=True, cmap=cm.grayscale)

/usr/local/lib/python3.6/dist-packages/itkwidgets/widget_viewer.py in view(image, ui_collapsed, annotations, interpolation, cmap, mode, shadow, slicing_planes, gradient_opacity, **kwargs)
    436             annotations=annotations, interpolation=interpolation, cmap=cmap,
    437             mode=mode, shadow=shadow, slicing_planes=slicing_planes,
--> 438             gradient_opacity=gradient_opacity, **kwargs)
    439     return viewer

/usr/local/lib/python3.6/dist-packages/itkwidgets/widget_viewer.py in __init__(self, **kwargs)
    225             self.extractor = itk.ExtractImageFilter.New(self.image)
    226             self.extractor.InPlaceOn()
--> 227             self.shrinker = itk.BinShrinkImageFilter.New(self.extractor)
    228         self._update_rendered_image()
    229         if self._downsampling:

/usr/local/lib/python3.6/dist-packages/itkLazy.py in __getattribute__(self, attr)
     38
     39     def __getattribute__(self, attr):
---> 40         value = types.ModuleType.__getattribute__(self, attr)
     41         if value is not_loaded:
     42             module = self.__belong_lazy_attributes[attr]

AttributeError: module 'itk' has no attribute 'BinShrinkImageFilter'

Hi @jpambrun ,
I could not reproduce locally with Linux / Python 3.6 / a virtualenv. Is there a Dockerfile with the installation that can reproduce the problem?

yep, the files are here:
https://github.com/jpambrun/ml-docker
The jupyterlab	image is based on base/Dockerfile.
The image needs to be larger than 1024x1024 by default to require downsmapling.
I also install these packages, but I don't think it matters:
cloudpickle==0.6.1
google-cloud-storage==1.13.0
lz4==2.1.2
matplotlib==3.0.2
numpy==1.15.4
pandas==0.23.4
Pillow==5.3.0
pydicom==1.2.1
pymongo==3.7.2
scikit-learn==0.20.1
scipy==1.1.0
tensorboard==1.12.0
tensorflow==1.12.0
zstandard==0.10.2
psycopg2-binary
--extra-index-url https://pypi.anaconda.org/clinicalgraphics/simple
CharPyLS==1.0.3

Probably because itk-core in setup.py is not enough.

@jpambrun great catch! :eagle: Would you mind creating a PR to add itk-filtering to setup.py?


[core][misc] improve free_finished_seq_groups

free_finished_seq_groups is in the critical path, because the engine calls it after every model step.
the main branch searchs for all the requests to find finished requests, while new finished requests should only appear in running queue.
this simple optimization, turns out to be important, when we process large amount of offline batch inference, e.g. when users give 100k prompts to the LLM engine. In this case, we are iterating all 100k data at every step.
I have heard users complaining that sending the whole dataset to LLM is slow, and he has to chunk the data into small batches (25 requests each) to make it fast. This PR might fix it.
Some micro benchmark to demonstrate the benefit when number of prompts are long and the model becomes small (thus overhead in scheduler becomes significant):
Note: main branch is commit https://github.com/vllm-project/vllm/commit/925de97e05dd4709fcd80691cb37da5e582c22e8
$ python benchmarks/benchmark_throughput.py --output-len 16 --input 16 --model facebook/opt-125m --num-prompts 10000

# main branch:
Throughput: 577.63 requests/s, 18484.31 tokens/s

# this PR:
Throughput: 674.46 requests/s, 21582.66 tokens/s

$ python benchmarks/benchmark_throughput.py --output-len 16 --input 16 --model facebook/opt-125m --num-prompts 100000

# main branch:
Throughput: 211.18 requests/s, 6757.85 tokens/s

# this PR:
Throughput: 522.91 requests/s, 16733.13 tokens/s

Conclusion:
When I increase the number of prompts from  10k to 100k, the main branch is slowed down by almost 3x. Improving the free_finished_seq_groups helps a lot, the slow down is about 40%. Apparently there are some other factors, but I think this might be the largest factor in processing with large datasets.

Here is the flamechart of the main branch, with 100k prompts. It becomes clear that free_finished_seq_groups is the major source of overhead.

Here is the flame chart of this PR, with various number of prompts:
10k prompts:

100k prompts:

500k prompts:

Even after this PR, there is still a slow down factor that is proportional to the number of waiting requests. The flamechat points to:
https://github.com/vllm-project/vllm/blob/fad5576c58864a6c2cf528f67e60e03a949b3dac/vllm/core/scheduler.py#L680
which is indeed very inefficient.

@youkaichao I think you must rebase to pass the failing Examples Test
[2024-07-29T19:01:27Z] python3: can't open file '/vllm-workspace/examples/llava_example.py': [Errno 2] No such file or directory

@youkaichao I think you must rebase to pass the failing Examples Test
[2024-07-29T19:01:27Z] python3: can't open file '/vllm-workspace/examples/llava_example.py': [Errno 2] No such file or directory

If there's no more comments, I will force-merge to avoid one additional ci cost :)

@youkaichao I think we need to understand the code before getting this PR merged.

LGTM. Please take your time. I think the scheduler logic is quite unclear though. Might have lots of bugs there.

@WoosukKwon please feel free to take this PR if you want some modifications!


Version 4.0.4 fails Typescript builds

When compiling, Typescript emits this error:
../../node_modules/express-winston/index.d.ts(33,2): error TS1036: Statements are not allowed in ambient contexts.
This is due to a bug in this commit:
https://github.com/bithavoc/express-winston/commit/a02930b1d80a56fefcf158feafe729ea1ecc9f2c
line 33 should not have a semi colon.
I reproduced this and checked the fix. by cloning this repo and running npx typescript.
I am opening a PR to fix this.
Also, is it possible to ask to add a Typescript compile check to your CI process? I'm not familiar with it, but I would be glad to help if needed.

@PeledYuval please submit the PR and I'll merge right away.
We need a robust typescript testing for our type declaration. sorry about that.

Hey, this is the relevant PR:
https://github.com/bithavoc/express-winston/pull/249

Thanks for spotting and fixing this so quickly, it was a minor version so it should not break anything hehe.
<EMAIL_ADDRESS>

@bithavoc My builds are green again :) Thank you for quickly responding and merging!


PagingInfo always Null

Hi,
Just tried PagingInfo, but it's always null.
Am I using it the wrong way ?
var service = new CardService();
var result = service.All();

var pagingInfo = result.PagingInfo;

Here, pagingInfo is always null

Just took and look and found the bug will put up a fix for that. Thanks for letting me know

Bug is fixed and also uploaded new Nuget package


Migrate prop documentation from MDX to JSON files

Before

After
https://github.com/primer/react/actions/runs/3848412337

Strange, the before image says that "2 of 84 MDX files have corresponding JSON files", but the after image says that "45 of 68 MDX files have corresponding JSON files".

Merge conflicts are getting a bit messy on this PR so I'm going to start with a clean PR https://github.com/primer/react/pull/2791


Handle SSH_MSG_CHANNEL_EXTENDED_DATA msg type

See RFC, search SSH_MSG_CHANNEL_EXTENDED_DATA
Fix https://github.com/microsoft/dev-tunnels-ssh/issues/68

Published to npm as version 3.11.24.


Validate pre-release kubeVersions in helm chart

Fixes https://github.com/external-secrets/external-secrets/issues/142
Tested against EKS cluster with gitVersion of v1.17.17-eks-c5067d

/approve

/merge


Ajust to NFC Reader working in new and olds SDKs

Made an adjustment to work in the Delphi 12 version, with NFC reading for Androids from SDKs prior to 31.
Example reading below:
Android 14 and 9

Your proposed change:

Has too much repeated code
Does not cater for Delphi 11.3 when SDK >= 31

I've committed a change now that caters for Delphi 11.3 and for SDK < 31


2

This PR solves #2 . Required sections were added to the README file.

@rultor merge this PR please

@rultor merge this PR please

@maxgoryunov OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge this PR please

@maxgoryunov Done! FYI, the full log is here (took me 2min)


Add other unrelated materials to the appendix

I can't seem to figure out how to add tables and etc. to my appendix while also using apxproof to add some proofs to the appendix. If I add an explicit \appendix to my .tex file, then the proofs that were automatically sent to the appendix will restart the appendix counter...

\begin{toappendix} and \end{toappendix} around the material you want sent to the appendix can be used for that purpose, and this allows keeping this extra material where it naturally fits within the paper. Let me know if this works for you.

\begin{toappendix} and \end{toappendix} around the material you want sent to the appendix can be used for that purpose, and this allows keeping this extra material where it naturally fits within the paper. Let me know if this works for you.

Thanks for your reply. It works in the sense that it adds things to the appendix, but it triggers a funny bug: the things enclosed with \begin{toappendix} \end{toappendix} get appended to the end of the appendix, but apxproof generates an extra (empty) section of proofs corresponding to the section that preceded my \begin{toappendix} code.
This is my TeX:
% ...
\input{rtt_data}
\input{concl}                   % Conclusions section.
\begin{toappendix}
    \input{heuristic_results}
\end{toappendix}

and that produces the following:

If I move the \begin{toappendix} up, so that the code looks like
% ...
\input{rtt_data}
\begin{toappendix}
    \input{heuristic_results}
\end{toappendix}
\input{concl}                   % Conclusions section.

then the output becomes

Neither section 4 nor 5 have any apxproof-related environments/commands.

This is working as expected, I think. Since the figures are part of a section in the text, a section title for this section appears in the appendix – it looks weird in this case because it is floating material, but it it were non-floating material (say, text), it would be desired to have a corresponding section in the appendix. There is a way to tell apxproof not to produce a section title for a specific section, that has appendix material. Just add \nosectionappendix after the corresponding '\section' command. Does this work for you? If not, if you provide a minimal complete example I can check it out.

I managed to fix my issue with one usage of \nosectionappendix, so thanks for that, but I don't think things are working as expected.
I created a minimal working example project on Overleaf: https://www.overleaf.com/3853347783qbqygjfzjywh
You can view and edit.
The project contains the main file with the following code:
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage{apxproof} % Defer proofs to the appendix.

\begin{document}

\input{section}
\input{dummy_section}

\begin{toappendix}
    \input{tables}
\end{toappendix}

\end{document}

Each of the inputted files has a \section and a line of text:
% section.tex
\section{Section refers to tables}

I like tables. I have a table in \ref{sec:tables}

% dummy_section.tex
\section{Dummy section}

This has nothing relevant.

% tables.tex
\section{My tables}
\label{sec:tables}

\begin{table}[]
    \centering
    \begin{tabular}{c|c}
        1 & 2
    \end{tabular}
    \caption{Caption}
    \label{tab:my_table}
\end{table}

This produces the following PDF:

I don't see a reason why there should be an (empty) appendix section for the dummy section, as it contains nothing relevant. As we move the \begin{toappendix}\input{tables}\end{toappendix} around, the (empty) appendix section that gets created changes.

Thanks. This is indeed not normal. Weirdly enough, the problem doesn't happen if the content of the tables.tex file is copied into the main.tex file instead of being \inputed. I will investigate this.

Good luck.
Just to be clear, I was able to work around this, so this issue doesn't affect me directly any more; feel free to close this issue (and open one specifically for the bug) if you want.

This required a somewhat ad-hoc fix, to detect a \section at the beginning of a file that is loaded with \input, but I have implemented this in bd56db3, and I am releasing v1.2.2 today that incorporates this fix.


updates

fix google sheets auth
fixed bug that was breaking on submit button click
changed UI boxes to white boxes with badges for easier color changes (accessibility issues with color choices)
made minor changes to legend to reflect the badges in the box UI, and added some tooltips for legend badges
Removed most model 2 code for simplicity

I renamed the app_dashboard.R file as app.R file to denote that its the main one we want to publish. This might be helpful because now your changes for model implementation are in the app_dashboard.R file and my changes to the UI components are in the app.R file.
We'll need to manually bring them over but I don't think we'll have weird merge issues. I can zoom call if the new layout is disorienting.

Sounds good! Do we want to drop in your UI functions into this commit on dev or move the updates from this commit to your commit on main? I'm thinking it might be easier to edit this commit since your updates are more modular, but happy to help with either!

I don't know if I know what you mean when you say "drop in your ui functions into this commit"? In the sense of how to do this, like manually copy over, or PR into dev...


Related entities not correctly populated in latest version

The newest update (v0.5.1) has introduced a bug which causes related entities not being populated at all. For instance, if we have [Group] 1 --> * [User], the users property is not populated in the final group object.
Seems to be related to the new browsers property added to package.json since removing this line restores the correct behaviour.

🤔 I don't see how the package.json could affect the behavior of the library . How are you importing it?

It's not very difficult to reproduce. The following sample code shows what's happening:
import { schema } from 'normalizr';
import { denormalize } from 'denormalizr';

const user = new schema.Entity('user', {
  group: group
});
const group = new schema.Entity('group', {
  users: [user],
});

const entity = { id: 1, name: 'Lars', group: 1 };
const entities = {
  user: {
    1: { id: 1, name: 'Lars', group: 1 },
  },
  group: {
    1: { id: 1, name: 'Test', users: [1] },
  },
};

const result = denormalize(entity, entities, group);

// If we use<EMAIL_ADDRESS>(no browser field in package.json)
console.log(result)  // { id: 1, name: 'Test', users: [{ id: 1, name: 'Lars', group: [circular]}] };

// if we use<EMAIL_ADDRESS>(browser field in package.json)
console.log(result)  // { id: 1, name: 'Test', users: [{}] };

// If we manually remove browser field from<EMAIL_ADDRESS>package.json
 console.log(result)  // { id: 1, name: 'Test', users: [{ id: 1, name: 'Lars', group: [circular]}] };

I'm using webpack to bundle the library, so probably it's related to webpack using the browser field instead of the main field.

I'm using webpack to bundle the library, so probably it's related to webpack using the browser field instead of the main field.

Interesting, thanks, this should be the reason. Are you using webpack 1?

Yes<EMAIL_ADDRESS>to be more precise.

@larsbs this should be fixed in v0.5.2! Thanks for the report, really appreciated 👍
Please reopen if not working as expected.


lines and graphs are not shown!

I am running the following codes and it seems manim has an issue with lines and graphs illustrations.
class CreateLine(Scene):
    def construct(self):
         start=(0,0,0)
         end=(4,0,0)
         line=Line(start, end)
         self.play(ShowCreation(line))

class PlotSin(Scene):
    def construct(self):
        axes = Axes((-3, 10), (-1, 8),
                 axis_config={
                     "stroke_color": GREY_A,
                     "stroke_width": 2,
                     "fill_opacity": 1,
                }
        )
        axes.add_coordinate_labels()

        self.play(Write(axes, lag_ratio=0.01, run_time=1))

        # Axes.get_graph will return the graph of a function
        sin_graph = axes.get_graph(
            lambda x: 2 * math.sin(x),
            color=BLUE,
        )

        sin_label = axes.get_graph_label(sin_graph, "\\sin(x)")

        self.play(
            ShowCreation(sin_graph),
            FadeIn(sin_label, RIGHT),
        )

I should mention that I have OpenGL V4.6 installed on my laptop and my graphic renderer is Intel(R) UHD.

I bet this is the same reason as #1456 issue

Which is also the same as #1455

I'm having the same issue. But i realize that the problem only happen in Windows. Running on Anaconda or Windows directly. In linux there is no problem.

Check this related issue on the CE: https://github.com/ManimCommunity/manim/issues/1240
It happens the same to me with both 3b1b edition and CE edition.
For me it is a problem with Intel GPU.
Can you check if on linux you are using Intel or another graphics cards?

I'm having the same issue. But i realize that the problem only happen in Windows. Running on Anaconda or Windows directly. In linux there is no problem.

Can you try python -m moderngl in both cases? Can you try installing mesa to see if it makes it work on Windows?

Check this related issue on the CE: ManimCommunity/manim#1240
It happens the same to me with both 3b1b edition and CE edition.
For me it is a problem with Intel GPU.
Can you check if on linux you are using Intel or another graphics cards?

I'm using Windows and Fedora on the same computer.
GPU: Intel UHD Graphics 620
And i've installed manim using pip in both systems

I'm having the same issue. But i realize that the problem only happen in Windows. Running on Anaconda or Windows directly. In linux there is no problem.

Can you try python -m moderngl in both cases? Can you try installing mesa to see if it makes it work on Windows?

moderngl output:
On windows
moderngl 5.6.4
vendor: Intel
renderer: Intel(R) UHD Graphics 620
version: 3.3.0 - Build <IP_ADDRESS>66
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr  6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330
On linux
moderngl 5.6.4
vendor: Intel
renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
version: 4.6 (Core Profile) Mesa 20.3.5
python: 3.9.2 (default, Feb 20 2021, 00:00:00)
[GCC 10.2.1 20201125 (Red Hat 10.2.1-9)]
platform: linux
code: 460
MESA is installed already

I'm having the same issue. But i realize that the problem only happen in Windows. Running on Anaconda or Windows directly. In linux there is no problem.

Can you try python -m moderngl in both cases? Can you try installing mesa to see if it makes it work on Windows?

moderngl output:
On windows
moderngl 5.6.4
vendor: Intel
renderer: Intel(R) UHD Graphics 620
version: 3.3.0 - Build <IP_ADDRESS>66
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330
On linux
moderngl 5.6.4
vendor: Intel
renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
version: 4.6 (Core Profile) Mesa 20.3.5
python: 3.9.2 (default, Feb 20 2021, 00:00:00)
[GCC 10.2.1 20201125 (Red Hat 10.2.1-9)]
platform: linux
code: 460
MESA is already installed on windows. i tried to reinstall, but dont works anyway

MESA doesn't seem to be correctly installed on Windows.

Having the same issue...
moderngl 5.6.4
vendor: Intel
renderer: Intel(R) HD Graphics 620
version: 3.3.0 - Build <IP_ADDRESS>54
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr  6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

Having the same issue...
moderngl 5.6.4
vendor: Intel
renderer: Intel(R) HD Graphics 620
version: 3.3.0 - Build <IP_ADDRESS>54
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

Lines, circle, square, etc. Can't be shown on the screen

Hi, I've solved this problem. Please change your graphics processor. I changed my graphics processor and everything becomes fine.
vendor: NVIDIA Corporation
renderer: GeForce 940MX/PCIe/SSE2
version: 3.3.0 NVIDIA 461.40
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr  6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

Having the same issue...
moderngl 5.6.4
vendor: Intel
renderer: Intel(R) HD Graphics 620
version: 3.3.0 - Build <IP_ADDRESS>54
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

Lines, circle, square, etc. Can't be shown on the screen

same here.

Hi, I've solved this problem. Please change your graphics processor. I changed my graphics processor and everything becomes fine.
vendor: NVIDIA Corporation
renderer: GeForce 940MX/PCIe/SSE2
version: 3.3.0 NVIDIA 461.40
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

is this your new processor or old one??

Hi, I've solved this problem. Please change your graphics processor. I changed my graphics processor and everything becomes fine.
vendor: NVIDIA Corporation
renderer: GeForce 940MX/PCIe/SSE2
version: 3.3.0 NVIDIA 461.40
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

is this your new processor or old one??

This is my new one. I've written my solution here. Please check it out.

Hi, I've solved this problem. Please change your graphics processor. I changed my graphics processor and everything becomes fine.
vendor: NVIDIA Corporation
renderer: GeForce 940MX/PCIe/SSE2
version: 3.3.0 NVIDIA 461.40
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

is this your new processor or old one??

This is my new one. I've written my solution here. Please check it out.

I do most of my work on my laptop.Unfortunately, my laptop doesnt come with dedicated Graphics  and I guess I have to change my system. 🥺

Hi, I've solved this problem. Please change your graphics processor. I changed my graphics processor and everything becomes fine.
vendor: NVIDIA Corporation
renderer: GeForce 940MX/PCIe/SSE2
version: 3.3.0 NVIDIA 461.40
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

is this your new processor or old one??

This is my new one. I've written my solution here. Please check it out.

I do most of my work on my laptop.Unfortunately, my laptop doesnt come with dedicated Graphics and I guess I have to change my system. 🥺

You can try the community edition of manin, which does not use opengl yet: https://docs.manim.community/en/stable/
You can do mostly the same things, but the code you will write will be slight different (not compatible, overall, with 3b1b code).

Hi, I've solved this problem. Please change your graphics processor. I changed my graphics processor and everything becomes fine.
vendor: NVIDIA Corporation
renderer: GeForce 940MX/PCIe/SSE2
version: 3.3.0 NVIDIA 461.40
python: 3.9.4 (tags/v3.9.4:1f2e308, Apr 6 2021, 13:40:21) [MSC v.1928 64 bit (AMD64)]
platform: win32
code: 330

is this your new processor or old one??

This is my new one. I've written my solution here. Please check it out.

I do most of my work on my laptop.Unfortunately, my laptop doesnt come with dedicated Graphics and I guess I have to change my system. 🥺

You can try the community edition of manin, which does not use opengl yet: https://docs.manim.community/en/stable/
You can do mostly the same things, but the code you will write will be slight different (not compatible, overall, with 3b1b code).

I did it and only line 1-16 are rendered. there is an error.

I resolved this issue by installing mesa! thanks a lot


MySQL Connection Lost

Not sure how this isn't an issue for a larger group of people, but here is our experience:

Jobs are running successfully
MySQL connection is temporarily lost, or unavailable to the worker
Worker does not attempt to re-establish connection, and is thus an orphaned process not working off any jobs
Devs have to manually restart delayed job workers any time this happens

We've tried added some ensure_db_connection logic throughout this gem and the delayed_job_active_record gem, but to no avail.  Slight modification of this (https://github.com/bracken/delayed_job/commit/b73a7e561b89fc09ae77bb9c1cfc680062867e19)
Anyone else suffering from this insidious bug?

I'm experiencing this too. Seems like using MySQL with Delayed Job is really wonky. The handler value that is going into the database is incredibly long in my case.

I'm experiencing this as well and it's killing us. We have very long jobs and if the mysql connection dies the record stays locked and in limbo. Right now we're writing a sweeper to go through the db and delete jobs that have been running longer than a certain time.
Could do with a fix here!

+1

FWIW, we are facing a similar issue with Postgres when apt auto-upgrades and thus stops/starts Postgres on our production server.


Implement method filter

Returns a new sparray containing all elements of the calling sparray for which the provided filtering ˋfilterFnˋ returns true.

done


FR: async feed_iterable

Know that the current feed iterable method is theoretically non-blocking up until resource exhaustion wrt to the underlying queue, would be helpful to just have a native awaitable implementation.

Closed by #770


FIX: Hook to event instead of model callback to make sure we auto-join users

Is it really more sure? Can't a user be made active by other means?

Is it really more sure? Can't a user be made active by other means?

This is the only point where activation happens outside of creation AFAIK. All the other places assume email is valid when creating.

Is it really more sure? Can't a user be made active by other means?

This is the only point where activation happens outside of creation AFAIK. All the other places assume email is valid when creating.
The problem with the previous callback is that it wasn't running when using save! instead of update!

Ok, honestly I'm not fan of having to trigger an event ourselves, if implementation changes we might not cache it in the test. OK yo merge this, but if you can think of a better test that would be great 🙌

Ok, honestly I'm not fan of having to trigger an event ourselves, if implementation changes we might not cache it in the test. OK to merge this, but if you can think of a better test that would be great 🙌

Yes, that's a good suggestion. Thanks! I added a test that calls the account activation controller 👌


Offline Google docs extraction + minor cleanup

Added missing requirement (simplekml) too.

Icons for file/folder added too. And if the file is available offline , a link to the extracted file (in green).


Add support for speed control feature

Hi there! I'm using this integration through the Home Assistant, but I guess the fastest way to notify would be to write here too :)
I just opened a discussion on the Home Assistant feature forum here
https://community.home-assistant.io/t/slide-curtains-add-slide-speed-control-into-integration/270819
Here is the quote:

Here is the new feature that is added which will be awesome to control from Home Assistant.
https://support.slide.store/article/336-slide-speed-setting
Scenarios would be, for morning alert open super slowly not to make any noise, and right after that set it back to 100% speed. Otherwise keeping it at 10% speed all the time would make it much unusable :) Or setting it to 10% before the sleep is annoying etc. :)

Will be awesome if this will be supported by this integration or the official one as it's exactly what was missing in my case to make it 100% perfect curtains :)
Thanks! Although I see that their Open API doc is missing info on how to achieve that, I guess it's possible to intercept somehow and see what exact parameters are being sent to the server or just ask them through the mail :) Unfortunately being a developer I completely have no clue about Python to contribute :) Hopefully, it will be a quick addition and soon it will be there in HA  :)

Sorry voor de late reply, maar ik de publieke API lijkt hier geen call voor te hebben. Maar ik vraag het voor de zekerheid na bij het support team van slide.store.

@RIP21  i checked with slide support, but this option is not possible via the API. You can use the Slide App to configure this (same applies for local API, you need to switch back to the cloud to configure it).

The Cloud API is closing and the local API still does not have this option (and will never get it either). So you need to use the new local App to configure this with your slide.

@ualex73 am I right that this integration can work with local API just fine, so once Slide Cloud is closed down we still will be able to use it in HA just fine?

Yes, the local api will work with this integration.

Now on local mode and it seems like speed changing doesn't work for local mode. Does it work for you? Nor does this integration now supports it maybe?


[CET-9978] Error when viewing Bird's Eye Report in Backstage

Change description
CET-9978 Error when viewing Bird's Eye Report in Backstage
Bird's Eye Report trowed an error when attempting to display heatmap with archived entity.
Type of change

[x] Bug fix (fixes an issue)
[ ] New feature (adds functionality)
[ ] Improvement (improves codebase without changing functionality)

Checklists
Development

[ ] The changelog has been updated as appropriate
[ ] Lint rules pass locally
[ ] Application changes have been tested thoroughly
[ ] Automated tests covering modified code pass

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

Code review

[ ] Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
[ ] "Ready for review" label attached and reviewers assigned
[ ] Changes have been reviewed by at least one other contributor
[ ] Pull request linked to task tracker where applicable

Could you maybe extract it to some utils and write some unit tests?


Wrike: Extract project name and issue number

Please remember the Contributing Guidelines :heart:
:star2: What does this PR do?
This adds further information to the description (wrike issue number) as well as the project name (folder / project name) to the toggle button integration.

Thank you for the feedback. I made the changes you suggested - the button in the pop-up looks equally misaligned, so I added the margin generally.

I tried my best to update the branch!


Introduce base_controller_class config option

Motivation:
It would be nice to use a specific controller from my application as the Solid Errors base controller, the same way that Mission Control Jobs does. For example, if MyAdminController handles all of my authentication, it would be nice to simply tell Solid Errors to inherit from that controller.
Details:
This PR adds a new base_controller_class config option to accomplish this.
Please let me know if this is something you'd be willing to add, and if there any other aspects you'd like me to include or change.
And thank you for Solid Errors! Today I upgraded our production app to use Solid Errors ✌🏼

Excellent! In particular I wasn't sure if you'd prefer a method for reading this value, so let me know if you'd want that change.

@fractaledmind are there any changes you'd like me to make on this?


trace policy: only call match if candidate isn't string

This change makes it so that String.prototype.match is only called in FilterPolicy for RegExp objects. It shouldn't be called for strings -- consider if we wanted to ignore '/' but not anything else.

Hi @kjin. What's the status of this? If this isn't ready to land, let's close this pull-request.


Use "wslview" instead of "xdg-open" in WSL

In WSL there is wslview instead of xdg-open.
We can change it by setting it in ui.browser, but I think it can be the default choice for WSL.

thanks!


Action buttons do not receive correct styling without isExpressive prop

What package(s) are you using?

[X] Cloud & Cognitive
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description

Describe in detail the issue you're having.
In the latest Carbon version, our action buttons (SidePanel, Tearsheets) need the isExpressive prop added otherwise they do not receive the full width that is expected. Instead, they get a max-width applied which breaks the design in multiple components.

Is this issue related to a specific component?
SidePanel
CreateTearsheet
Tearsheet
What did you expect to happen? What happened instead? What would you like to
see changed?
Action buttons should not get a max width applied to them.
What browser are you working in?
Chrome
What version of the @carbon/ibm-cloud-cognitive packge are you using?
Latest

Steps to reproduce the issue

Go to storybook
Look at CreateTearsheet action buttons

https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/841


License for Hub repository

Should we add a license field for the Hub repository, maybe in the admin.json file?

So I think the license is actually specified by each team for their specific model output data: https://github.com/Infectious-Disease-Modeling-Hubs/hubTemplate/blob/main/hub-config/model-metadata-schema.json
But it raises an interesting question regarding what does that mean about data at the hub level

I support adding a license field to the admin.json config file that would cover any hub-specific code/workflows/setup, and perhaps would serve as a default license for any models that do not specify a license. We could make it clear in the documentation how/where this license applies.

I suggest coordinating a schema update and documentation update to solve this issue.


ROX-13943: Hide "sourced" autogenerated image integrations behind a feature flag

Description
This change adds a feature flag around the changes introduced in https://github.com/stackrox/stackrox/pull/2572.
Checklist

[x] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
[x] Evaluated and added CHANGELOG entry if required
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed
Given:
config.json:
{"<IP_ADDRESS>:5000":{"username":"serviceaccount","password":"<some-password>"}}

create-kubernetes-secrets.sh:
#!/bin/bash
for i in {1..5000}
do
    kubectl create secret docker-registry some-secret-$i --from-file=.dockerconfigjson=config.json
done

Create a Kubernetes/OpenShift cluster
Create a ton of dockerconfigjson secrets via create-kubernetes-secrets.sh
Deploy ACS/StackRox 3.73.0
Observe within the UI that a lot of image integration are being added and reconciled

After a while, restart central by killing the pod

kubectl delete pod -l app=central -n stackrox

Observe within the logs that central's log output is stuck

kubectl logs -l app=central -n stackrox
...
imageintegration/datastore: 2022/12/15 01:02:08.913010 datastore_impl.go:124: Info: [STARTUP] Found **1764** Image Integrations to be indexed
imageintegration/datastore: 2022/12/15 01:02:08.976003 datastore_impl.go:132: Info: [STARTUP] Successfully indexed 1764 Image Integrations
rbac/k8srole/datastore: 2022/12/15 01:02:09.789312 datastore_impl.go:63: Info: [STARTUP] Successfully indexed 753 roles
rbac/k8srolebinding/datastore: 2022/12/15 01:02:09.845649 datastore_impl.go:38: Info: [STARTUP] Indexing rolebindings
rbac/k8srolebinding/datastore: 2022/12/15 01:02:10.046431 datastore_impl.go:62: Info: [STARTUP] Successfully indexed 1135 rolebindings
policy/store/boltdb: 2022/12/15 01:02:10.190252 store.go:139: Info: Loaded 0 new default Policies
cve/fetcher: 2022/12/15 01:02:10.255639 manager_impl.go:55: Info: successfully copied preloaded CVE Istio files to persistent volume: "/var/lib/stackrox/cve/istio"
cve/fetcher: 2022/12/15 01:02:10.255774 orchestrator.go:62: Info: Found 2 clusters to scan for orchestrator vulnerabilities.
cve/fetcher: 2022/12/15 01:02:10.257331 orchestrator.go:237: Info: Successfully fetched 0 Kubernetes CVEs
cve/fetcher: 2022/12/15 01:02:10.257424 orchestrator.go:70: Error: failed to reconcile orchestrator OpenShift CVEs: no orchestrator scanners are integrated
cve/fetcher: 2022/12/15 01:02:10.272806 istio.go:51: Info: successfully fetched 23 istio CVEs
vulnerabilityrequest/datastore: 2022/12/15 01:02:10.299980 datastore_impl.go:52: Info: [STARTUP] Found 0 vulnerability requests to index
vulnerabilityrequest/datastore: 2022/12/15 01:02:10.300061 datastore_impl.go:66: Info: [STARTUP] Successfully indexed all vulnerability requests

(optional): Set the log level to debug and observe a continuous stream of logs from pkg/registries/docker

kubectl set env -n stackrox deploy/central LOGLEVEL=Debug

kubectl logs -l app=central -n stackrox
...
cve/fetcher: 2022/12/15 01:03:32.219524 orchestrator.go:62: Info: Found 2 clusters to scan for orchestrator vulnerabilities.
cve/fetcher: 2022/12/15 01:03:32.221184 orchestrator.go:237: Info: Successfully fetched 0 Kubernetes CVEs
cve/fetcher: 2022/12/15 01:03:32.221281 orchestrator.go:70: Error: failed to reconcile orchestrator OpenShift CVEs: no orchestrator scanners are integrated
cve/fetcher: 2022/12/15 01:03:32.237856 istio.go:51: Info: successfully fetched 23 istio CVEs
vulnerabilityrequest/datastore: 2022/12/15 01:03:32.263665 datastore_impl.go:52: Info: [STARTUP] Found 0 vulnerability requests to index
vulnerabilityrequest/datastore: 2022/12/15 01:03:32.263751 datastore_impl.go:66: Info: [STARTUP] Successfully indexed all vulnerability requests
pkg/registries/docker: 2022/12/15 01:03:32.317643 docker.go:107: Debug: could not update repo list for integration Autogenerated https://<IP_ADDRESS>:5000 for cluster production from openshift-kube-controller-manager/builder-dockercfg-nrwvn: Get "https://<IP_ADDRESS>:5000/v2/_catalog": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"authentication required\",\"detail\":[{\"Type\":\"registry\",\"Class\":\"\",\"Name\":\"catalog\",\"Action\":\"*\"}]}]}\n")
pkg/registries/docker: 2022/12/15 01:03:32.381961 docker.go:107: Debug: could not update repo list for integration Autogenerated https://image-registry.openshift-image-registry.svc:5000 for cluster nakul from openshift-kube-scheduler-operator/builder-dockercfg-xshn9: Get "https://image-registry.openshift-image-registry.svc:5000/v2/_catalog": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"authentication required\",\"detail\":[{\"Type\":\"registry\",\"Class\":\"\",\"Name\":\"catalog\",\"Action\":\"*\"}]}]}\n")
pkg/registries/docker: 2022/12/15 01:03:32.418928 docker.go:107: Debug: could not update repo list for integration Autogenerated https://image-registry.openshift-image-registry.svc.cluster.local:5000 for cluster nakul from openshift-infra/image-trigger-controller-dockercfg-746lr: Get "https://image-registry.openshift-image-registry.svc.cluster.local:5000/v2/_catalog": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"authentication required\",\"detail\":[{\"Type\":\"registry\",\"Class\":\"\",\"Name\":\"catalog\",\"Action\":\"*\"}]}]}\n")
pkg/registries/docker: 2022/12/15 01:03:37.420360 docker.go:107: Debug: could not update repo list for integration Autogenerated https://<IP_ADDRESS>:5000 for cluster nakul from openshift-infra/node-bootstrapper-dockercfg-hzlp8: Get "https://<IP_ADDRESS>:5000/v2/_catalog": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
pkg/registries/docker: 2022/12/15 01:03:37.475001 docker.go:107: Debug: could not update repo list for integration Autogenerated https://image-registry.openshift-image-registry.svc:5000 for cluster nakul from openshift-kube-scheduler/builder-dockercfg-l6g7x: Get "https://image-registry.openshift-image-registry.svc:5000/v2/_catalog": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"authentication required\",\"detail\":[{\"Type\":\"registry\",\"Class\":\"\",\"Name\":\"catalog\",\"Action\":\"*\"}]}]}\n")
pkg/registries/docker: 2022/12/15 01:03:37.497478 docker.go:107: Debug: could not update repo list for integration Autogenerated https://image-registry.openshift-image-registry.svc:5000 for cluster nakul from openshift-network-diagnostics/deployer-dockercfg-87g6x: Get "https://image-registry.openshift-image-registry.svc:5000/v2/_catalog": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"authentication required\",\"detail\":[{\"Type\":\"registry\",\"Class\":\"\",\"Name\":\"catalog\",\"Action\":\"*\"}]}]}\n")

Bump the version of sensor and central by changing the image name to the tag of this PR

kubectl set image -n stackrox deploy/central central=quay.io/stackrox-io/main:.73.x-235-g53652ca213

kubectl set image -n stackrox deploy/sensor sensor=quay.io/stackrox-io/main:.73.x-235-g53652ca213

Observe within the logs that central log isn't stuck and the number of indexed image integration has lowered drastically (compared to the 1764 from 3.73.0)

kubectl logs -l app=central -n stackrox
...
alert/datastore: 2022/12/15 01:55:14.990503 datastore_impl.go:429: Info: [STARTUP] Successfully indexed all out of sync alerts
imageintegration/datastore: 2022/12/15 01:55:15.018256 datastore_impl.go:125: Info: [STARTUP] Found **18** Image Integrations to be indexed
imageintegration/datastore: 2022/12/15 01:55:15.020582 datastore_impl.go:133: Info: [STARTUP] Successfully indexed 18 Image Integrations
...
secret/datastore: 2022/12/15 01:55:15.489349 datastore_impl.go:34: Info: [STARTUP] Indexing secrets
secret/datastore: 2022/12/15 01:55:15.761372 datastore_impl.go:50: Info: [STARTUP] Successfully indexed secrets
serviceaccount/datastore: 2022/12/15 01:55:15.898567 datastore_impl.go:35: Info: [STARTUP] Indexing service accounts
serviceaccount/datastore: 2022/12/15 01:55:15.982337 datastore_impl.go:57: Info: [STARTUP] Successfully indexed 717 service accounts
rbac/k8srole/datastore: 2022/12/15 01:55:15.982444 datastore_impl.go:39: Info: [STARTUP] Indexing roles
rbac/k8srole/datastore: 2022/12/15 01:55:16.150993 datastore_impl.go:63: Info: [STARTUP] Successfully indexed 753 roles
rbac/k8srolebinding/datastore: 2022/12/15 01:55:16.227863 datastore_impl.go:38: Info: [STARTUP] Indexing rolebindings
rbac/k8srolebinding/datastore: 2022/12/15 01:55:16.475709 datastore_impl.go:62: Info: [STARTUP] Successfully indexed 1135 rolebindings
policy/store/boltdb: 2022/12/15 01:55:16.696793 store.go:139: Info: Loaded 0 new default Policies
cve/fetcher: 2022/12/15 01:55:16.782266 manager_impl.go:55: Info: successfully copied preloaded CVE Istio files to persistent volume: "/var/lib/stackrox/cve/istio"
cve/fetcher: 2022/12/15 01:55:16.782399 orchestrator.go:62: Info: Found 2 clusters to scan for orchestrator vulnerabilities.
cve/fetcher: 2022/12/15 01:55:16.785945 orchestrator.go:250: Info: Successfully fetched 0 Kubernetes CVEs
cve/fetcher: 2022/12/15 01:55:16.786064 orchestrator.go:70: Error: failed to reconcile orchestrator OpenShift CVEs: no orchestrator scanners are integrated
cve/fetcher: 2022/12/15 01:55:16.787697 orchestrator.go:250: Info: Successfully fetched 0 Istio CVEs
vulnerabilityrequest/datastore: 2022/12/15 01:55:16.816730 datastore_impl.go:52: Info: [STARTUP] Found 0 vulnerability requests to index
vulnerabilityrequest/datastore: 2022/12/15 01:55:16.816815 datastore_impl.go:66: Info: [STARTUP] Successfully indexed all vulnerability requests
cve/fetcher: 2022/12/15 01:55:17.233920 orchestrator.go:62: Info: Found 2 clusters to scan for orchestrator vulnerabilities.
cve/fetcher: 2022/12/15 01:55:17.234629 orchestrator.go:250: Info: Successfully fetched 0 Kubernetes CVEs
cve/fetcher: 2022/12/15 01:55:17.253700 orchestrator.go:250: Info: Successfully fetched 0 OpenShift CVEs
cve/fetcher: 2022/12/15 01:55:17.254408 orchestrator.go:250: Info: Successfully fetched 0 Istio CVEs
detection/lifecycle: 2022/12/15 01:55:24.911478 singleton.go:41: Info: Injecting 84 policies into detectors.
detection/lifecycle: 2022/12/15 01:55:24.947495 singleton.go:46: Info: Done injecting policies.
reportconfigurations/datastore: 2022/12/15 01:55:24.947729 datastore_impl.go:40: Info: [STARTUP] Indexing report configurations
reportconfigurations/datastore: 2022/12/15 01:55:24.947794 datastore_impl.go:56: Info: [STARTUP] Successfully indexed report configurations
detection/lifecycle: 2022/12/15 01:55:25.005708 manager_impl.go:123: Info: Cleaning up 36 processes as a part of building process filter
detection/lifecycle: 2022/12/15 01:55:25.012346 manager_impl.go:127: Info: Successfully cleaned up those 36 processes
pruning: 2022/12/15 01:55:25.129198 pruning.go:141: Info: [Pruning] Starting a garbage collection cycle
cve/suppress: 2022/12/15 01:55:25.130005 reprocessor.go:120: Info: Successfully unsuppressed 0 CVEs
reprocessor: 2022/12/15 01:55:25.130068 reprocessor.go:272: Info: Found 12 nodes to scan
vulnerabilityrequest/manager/requestmgr: 2022/12/15 01:55:25.130438 manager_impl.go:506: Info: [STARTUP] Successfully cached all vulnerability requests
pruning: 2022/12/15 01:55:25.131074 pruning.go:501: Info: [Image pruning] Found 0 image search results
pkg/grpc: 2022/12/15 01:55:25.131063 server.go:216: Info: Launching backend gRPC listener
pkg/grpc: 2022/12/15 01:55:25.138359 server.go:371: Info: TLS-enabled multiplexed HTTP/gRPC server listening on [::]:8443
pruning: 2022/12/15 01:55:25.150599 pruning.go:357: Info: [Process pruning] Found 0 orphaned processes
pruning: 2022/12/15 01:55:25.151322 pruning.go:418: Info: [Process baseline pruning] Removed 0 process baselines
pruning: 2022/12/15 01:55:25.179487 pruning.go:449: Info: [Alert pruning] Found 0 orphaned alerts
pruning: 2022/12/15 01:55:25.184207 pruning.go:221: Info: [Pruning] Found no orphaned pods...
pruning: 2022/12/15 01:55:25.185965 pruning.go:241: Info: [Pruning] Found no orphaned service accounts...
pruning: 2022/12/15 01:55:25.187909 pruning.go:241: Info: [Pruning] Found no orphaned K8S roles...
pruning: 2022/12/15 01:55:25.191358 pruning.go:241: Info: [Pruning] Found no orphaned K8S role bindings...
pruning: 2022/12/15 01:55:25.207575 pruning.go:774: Info: [Risk pruning] Removing 0 deployment risks
pruning: 2022/12/15 01:55:25.208638 pruning.go:787: Info: [Risk pruning] Removing 0 image risks
pruning: 2022/12/15 01:55:25.223243 pruning.go:800: Info: [Risk pruning] Removing 0 image component risks
pruning: 2022/12/15 01:55:25.237008 pruning.go:813: Info: [Risk pruning] Removing 0 node risks
pruning: 2022/12/15 01:55:25.249212 pruning.go:537: Info: [Cluster Pruning] pruning is disabled.
pruning: 2022/12/15 01:55:25.249316 pruning.go:158: Info: [Pruning] Finished garbage collection cycle
networkgraph/entity/gatherer: 2022/12/15 01:55:25.322093 load_bundled.go:52: Info: Successfully loaded 28389 external networks
networkgraph/entity/gatherer: 2022/12/15 01:55:25.370469 load_bundled.go:64: Info: Found 28389 external networks in DB. Successfully stored 0/28389 new external networks
reprocessor: 2022/12/15 01:55:26.450142 reprocessor.go:301: Info: Successfully reprocessed 12/12 nodes
reprocessor: 2022/12/15 01:55:26.450307 reprocessor.go:272: Info: Found 0 watched images to scan
reprocessor: 2022/12/15 01:55:26.450334 reprocessor.go:301: Info: Successfully reprocessed 0/0 w

Observe also within the UI that the number of integrations has lowered and stays stable

@dhaus67 @RTann, help me understand this. The behavior change for auto-generated image integrations was released in 3.73.0. Therefore, until Central gRPC listeners are ready and start receiving messages from Sensor, Central DB should not have had many image integrations because Central is beginning to receive messages from Sensor past the readiness probe.
Is the above understanding correct?
If yes, then,

If the observation was strictly made during the first time Central was being upgraded to 3.73.0, then I do not think we have covered everything.
If otherwise, then we have covered everything.

@dhaus67 @RTann, help me understand this. The behavior change for auto-generated image integrations was released in 3.73.0. Therefore, until Central gRPC listeners are ready and start receiving messages from Sensor, Central DB should not have had many image integrations because Central is beginning to receive messages from Sensor past the readiness probe.
Is the above understanding correct? If yes, then,

If the observation was strictly made during the first time Central was being upgraded to 3.73.0, then I do not think we have covered everything.
If otherwise, then we have covered everything.

I agree with your assessment. I am not sure if the cases we found were created after Central had already restarted due to some reason or if this was the first 3.73.0 upgrade attempt.

@dhaus67 @RTann, help me understand this. The behavior change for auto-generated image integrations was released in 3.73.0. Therefore, until Central gRPC listeners are ready and start receiving messages from Sensor, Central DB should not have had many image integrations because Central is beginning to receive messages from Sensor past the readiness probe.
Is the above understanding correct? If yes, then,

If the observation was strictly made during the first time Central was being upgraded to 3.73.0, then I do not think we have covered everything.
If otherwise, then we have covered everything.

I agree with your assessment. I am not sure if the cases we found were created after Central had already restarted due to some reason or if this was the first 3.73.0 upgrade attempt.

Okay, let's run by that theory.


drivers: Format pointer through "%p" for kthread_create

Summary
Impact
code refactor
Testing
ci

@pkarashchenko could you merge this patch?


[std.range.chain] Use static assert instead of complex constraint

We can give more precise errors then. chain is actually mentioned in this paper (thanks @ibuclaw):
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2429r0.pdf

chain(Ranges...)(Ranges rs)
with Ranges = (int[], int)
must satisfy the following constraint:
 allSatisfy!(isInputRange, staticMap!(Unqual, Ranges))
This error narrowed down which constraint in the conjunction failed (i.e. it wasn't the length check or the
common type check), but it didn't tell us which argument failed the constraint, and it didn't tell us why, or
what we can do about it.

Now we get:
test.d(10): Error: static assert:  `int` is not an input range
test.d(792):        instantiated from here: `chain!(int, int[])`

I've included a constraint that at least one argument is an input range. This is to reduce the chance of breaking code that uses an overload of chain defined elsewhere.

@nrtel Keep in mind that there are downsides to converting template constraints to static asserts, see: https://github.com/dlang/phobos/pull/8745#pullrequestreview-1415895793
I'm saying that this specific PR is problematic (I haven't had the chance to review it), but I'm mentioning this for your information.

@PetarKirov I am trying to avoid breaking anyone's code unnecessarily, which is why e.g. I made chain require at least one input range, in case there are functions called chain in other imported modules.
The other point is that removing constraints means the generic type requirements are undocumented. One solution to this would be to make in contract blocks appear in the documentation and put the static assert code inside one. Perhaps the documentation could show them collapsed by default, or collapsible at least, to save space.

@PetarKirov It seems to me like the kind code that broke in the linked PR—where a user relies on overload resolution to choose between a Phobos function and their own version of the same symbol—could just as easily have been broken by merely adding a new overload of equal, without touching the existing one.
Unless we want to adopt a blanket policy of never adding new overloads to existing Phobos functions (do we?), I think we must conclude that we do not, in general, guarantee backward compatibility for this kind of usage.
Now, maybe equal is particularly high-risk in this regard, so it's worth blocking changes to it while still allowing them elsewhere. But is the same true for chain, choose, and chooseAmong? I don't have a good answer here; it's hard to decide where to draw the line.


Crash in location manager

Current coverage is 64.79%

Merging #155 into release/2.5.1 will increase coverage by +0.03% as of f09187f

@@            release/2.5.1    #155   diff @@
=============================================
  Files                  48      48
  Stmts                2523    2531     +8
  Branches                0       0
  Methods                 0
=============================================
+ Hit                  1634    1640     +6
  Partial                 0       0
- Missed                889     891     +2

Review entire Coverage Diff as of f09187f

Powered by Codecov. Updated on successful CI builds.

Current coverage is 64.79%

Merging #155 into release/2.5.1 will increase coverage by +0.03% as of f09187f

@@            release/2.5.1    #155   diff @@
=============================================
  Files                  48      48
  Stmts                2523    2531     +8
  Branches                0       0
  Methods                 0
=============================================
+ Hit                  1634    1640     +6
  Partial                 0       0
- Missed                889     891     +2

Review entire Coverage Diff as of f09187f

Powered by Codecov. Updated on successful CI builds.


No xrate function available

As said in the Grafana issue, xrate function doesn't exists when I compile your fork.
go get github.com/free/prometheus
git checkout xrate_v2.2.1
make build

Looking at the version output, it's the right version:
# ./prometheus --version
prometheus, version 2.2.1 (branch: xrate_v2.2.1, revision: f3e781a5af599a76edbf1c2f61a4a57ce48b371d)

When trying to run xrate function, I get the error unknown function:
rate(node_cpu{instance="host"}[60s])
Error executing query: parse error at char 6: unknown function with name "xrate"

How are you running the query? I tried by going to localhost:9090 and running the query there.
Regardless, I just figured out how to build binaries for the full range of platforms that Prometheus supports (just do promu crossbuild) and I'll make a proper release with what are (at least for me) working binaries.

I was running my queries the same way you did. Weird:)
Anyway, I downloaded your release and it's working now, yeey. Off to check some graphs with the new function.
Thanks for the help


Cannot Reference Custom Blockchain Data Location (datadir)

There is no option to access android internal storage to back up my synced data in the event of an 'boating' accident. When I set datadir=/storage/emulated/0/bitcoin and start daemon in stops almost immediately. Please enable access to external storage.

The reason for that is because the reference for only the Blockchain data as far as tx's has not been created yet. But hopefully will be coming soon. Also one of the biggest problems when it comes to making it android accessible is the memory and storage space needed. In the current structure it is basically a second way to access your already downloaded Bitcoin core using the rpcport function to connect with your core on the computer and calling simple functions. But even then unless you have the correct local server connection with ssl connection for server verification it is a little bit of a hassle.


Cannot access a disposed object

When I send Http Request from one function and try to process Response in the next function, I get an error:

Cannot access a disposed object.
Object name: 'System.Net.Http.StreamContent'.
Example:
procedure TestProcedure();
    var
        Response: HttpResponseMessage;
        ResponseText: Text;
        URL: Text;
        BodyText: Text;
    begin
        URL := 'https://postman-echo.com/post';
        BodyText := 'testtest';

        SendRequest(URL,BodyText,Response);
        Response.Content.ReadAs(ResponseText);
        Message(ResponseText);
    end;

    local procedure SendRequest(URL:Text;var BodyText: Text;var Response: HttpResponseMessage);
    var
        Client: HttpClient;
        Content: HttpContent;
    begin
        Content.WriteFrom(BodyText);
        Client.Post(URL,Content,Response);
    end;

Looks like HttpResponseMessage is disposed automatically in the end of my 'SendRequest' function.
Is it possible to process Response only in the same function where request was sent?

Which versions(extension version, server version) are you using?


[BUG] In interactive server mode, subscribing to too many attributes at once will cause a timeout

Reproduction steps

Connect the Matter device to the Matter network of the Matter gateway
Use command on Matter gateway : chip-tool interactive server --port 9003 --iface null
Connect websocket and send commad: any subscribe-by-id 0xFFFFFFFF 0xFFFFFFFF 0 10 1001 3

Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
910be1fcff2211e7ea65bee4fa62fea564909ea5
Platform
raspi
Platform Version(s)
No response
Type
Common Cluster Logic
Anything else?
No response

[1692671855.030156][19508:19525] CHIP:DMG: Subscription established with SubscriptionID = 0x82a63660 MinInterval = 0s MaxInterval = 10s Peer = 03:00000000000003E9
[1692671855.030219][19508:19525] CHIP:DMG: MoveToState ReadClient[0x56a93ee0]: Moving to [Subscripti]
[1692671855.034258][19508:19525] CHIP:DMG: Refresh LivenessCheckTime for 14224 milliseconds with SubscriptionId = 0x82a63660 Peer = 03:00000000000003E9
[1692671883.836392][19508:19525] CHIP:EM: <<< [E:33391i S:10527 M:73228097 (Ack:66671197)] (S) Msg TX to 3:00000000000003E9 [5F10] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1692671883.836532][19508:19525] CHIP:IN: (S) Sending msg 73228097 on secure session with LSID: 10527
[1692671883.836759][19508:19525] CHIP:EM: Flushed pending ack for MessageCounter:66671197 on exchange 33391i
[1692671883.837077][19508:19525] CHIP:IN: Received a duplicate message with MessageCounter:66671197 on exchange 33391i
[1692671883.837169][19508:19525] CHIP:EM: >>> [E:33391i S:10527 M:66671197 (Ack:73228096)] (S) Msg RX from 3:00000000000003E9 [5F10] --- Type 0001:04 (IM:SubscribeResponse)
[1692671883.837259][19508:19525] CHIP:EM: Generating StandaloneAck via exchange: 33391i
[1692671883.837311][19508:19525] CHIP:EM: Forcing tx of solitary ack for duplicate MessageCounter:66671197 on exchange 33391i
[1692671883.837494][19508:19525] CHIP:EM: <<< [E:33391i S:10527 M:73228098 (Ack:66671197)] (S) Msg TX to 3:00000000000003E9 [5F10] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1692671883.837600][19508:19525] CHIP:IN: (S) Sending msg 73228098 on secure session with LSID: 10527
[1692671883.838084][19508:19525] CHIP:IN: Received a duplicate message with MessageCounter:66671197 on exchange 33391i
[1692671883.838180][19508:19525] CHIP:EM: >>> [E:33391i S:10527 M:66671197 (Ack:73228096)] (S) Msg RX from 3:00000000000003E9 [5F10] --- Type 0001:04 (IM:SubscribeResponse)
[1692671883.838256][19508:19525] CHIP:EM: Generating StandaloneAck via exchange: 33391i
[1692671883.838959][19508:19525] CHIP:EM: Forcing tx of solitary ack for duplicate MessageCounter:66671197 on exchange 33391i
[1692671883.839406][19508:19525] CHIP:EM: <<< [E:33391i S:10527 M:73228099 (Ack:66671197)] (S) Msg TX to 3:00000000000003E9 [5F10] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1692671883.839924][19508:19525] CHIP:IN: (S) Sending msg 73228099 on secure session with LSID: 10527
[1692671883.840625][19508:19525] CHIP:IN: Received a duplicate message with MessageCounter:66671197 on exchange 33391i
[1692671883.841546][19508:19525] CHIP:EM: >>> [E:33391i S:10527 M:66671197 (Ack:73228096)] (S) Msg RX from 3:00000000000003E9 [5F10] --- Type 0001:04 (IM:SubscribeResponse)
[1692671883.841955][19508:19525] CHIP:EM: Generating StandaloneAck via exchange: 33391i
[1692671883.842321][19508:19525] CHIP:EM: Forcing tx of solitary ack for duplicate MessageCounter:66671197 on exchange 33391i
[1692671883.842728][19508:19525] CHIP:EM: <<< [E:33391i S:10527 M:73228100 (Ack:66671197)] (S) Msg TX to 3:00000000000003E9 [5F10] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1692671883.843211][19508:19525] CHIP:IN: (S) Sending msg 73228100 on secure session with LSID: 10527
[1692671883.844275][19508:19525] CHIP:IN: Received a duplicate message with MessageCounter:66671197 on exchange 33391i
[1692671883.844864][19508:19525] CHIP:EM: >>> [E:33391i S:10527 M:66671197 (Ack:73228096)] (S) Msg RX from 3:00000000000003E9 [5F10] --- Type 0001:04 (IM:SubscribeResponse)
[1692671883.847825][19508:19525] CHIP:EM: Generating StandaloneAck via exchange: 33391i
[1692671883.847871][19508:19508] CHIP:TOO: LWS_CALLBACK_SERVER_WRITEABLE
[1692671883.848206][19508:19525] CHIP:EM: Forcing tx of solitary ack for duplicate MessageCounter:66671197 on exchange 33391i
[1692671883.849243][19508:19525] CHIP:EM: <<< [E:33391i S:10527 M:73228101 (Ack:66671197)] (S) Msg TX to 3:00000000000003E9 [5F10] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1692671883.849831][19508:19525] CHIP:IN: (S) Sending msg 73228101 on secure session with LSID: 10527
[1692671884.814399][19508:19508] CHIP:TOO: LWS_CALLBACK_SERVER_WRITEABLE
[1692671898.073875][19508:19525] CHIP:DMG: Subscription Liveness timeout with SubscriptionID = 0x82a63660, Peer = 03:00000000000003E9
[1692671898.073982][19508:19525] CHIP:IN: SecureSession[0x56a43f10]: MarkAsDefunct Type:2 LSID:10527
[1692671898.074028][19508:19525] CHIP:SC: SecureSession[0x56a43f10]: Moving from state 'kActive' --> 'kDefunct'
[1692671898.074066][19508:19525] CHIP:DMG: MoveToState ReadClient[0x56a93ee0]: Moving to [      Idle]
[1692671898.074115][19508:19525] CHIP:TOO: Error: ../chip/examples/chip-tool/third_party/connectedhomeip/src/app/ReadClient.cpp:894: CHIP Error 0x00000032: Timeout
[1692671898.074174][19508:19525] CHIP:TOO: Run command failure: ../chip/examples/chip-tool/third_party/connectedhomeip/src/app/ReadClient.cpp:894: CHIP Error 0x00000032: Timeout

@changzhe-github Hard to say why you are never getting a report without seeing the server log, but something is definitely up with your connectivity.  Observe all the retransmits of the SubscribeResponse message, which suggests the other side is not getting the acks....
I strongly suggest attaching (not pasting) logs from both sides of the interaction so we can try to figure out what the server is seeing/doing here.


Progress not working in version 17.0.0 and higher

Hi guys!
I've implemented a download function in my react native project using the latest version of react-native-blob-util, but the progress callback was never being called
I got to make it work out by downgrading the library version to 16.4.0, but the latest version really doesn't work. I want to be able to use the latest versions, can you help me? 🙌

Hi, thanks for using the lib and your report.
Do you have the problems on Android or iOS?
Could you provide a small code snippet of what you're doing?

I've tested on iOS! Didn't get to test it on android
Heres the code snippet:
  export const downloadTask = (data: IDownloadTaskProps): ITaskObservable => {
    const {
      fs: { dirs },
      config,
    } = RNFetchBlob;
    const rootDir = dirs[Platform.OS === 'ios' ? 'DocumentDir' : 'DownloadDir'];
    const path = `${rootDir}/${DIR_NAME}/${data?.fileName}`;

    return new Observable((observer) => {
      const downloadProgress = (received: number, total: number) => {
        const progress = Math.round((received / total) * TOTAL_PERCENT);
        observer.next({
          status: DOWNLOAD_IN_PROGRESS_STATUS,
          progress,
          taskId: data.taskId,
          contentData: undefined,
        });
      };
      try {
        const response = config({
          ...(data.configOptions ?? DEFAULT_CONFIG),
          path,
        }).fetch(data.fetchMethod, data.fileUrl);

        response
          .progress(downloadProgress)
          .then((res) => {
            observer.next({
              status: COMPLETED_DOWNLOAD_STATUS,
              progress: COMPLETED_DOWNLOAD_PROGRESS,
              taskId: data?.taskId,
              contentData: res,
            });
            observer.complete();
          })
          .catch((err) => {
            observer.error(`Error while trying to download: ${err}`);
          });
      } catch (error) {
        observer.error(`Error while trying to write file: ${error}`);
      }
    });
};

Same issue here on iOS v 17.3

Do you get the status and headers of the request set correctly?
It might be related to this issue: https://github.com/RonRadtke/react-native-blob-util/issues/236
So maybe you can try my feature-branch as well and see if that solves your problems with the progress.


updated docker to 1.6.2

@dpausp Why did you close this PR?

oops, I accidentally deleted my branch. Restored and reopened now

/nix/store/bnlcsbw7nhd21vw4xssnxwi9y7h2asjj-coreutils-8.23/bin/mkdir: cannot create directory '/nix/store/2jdv58jrmc9ggf83bh09jw848qcj672k-systemd-217/lib/systemd/system': Permission denied

The build failure is not caused by my change, it's a problem in lxc (same as in #8151). It builds fine on my NixOS machine but fails on other systems like debian in the travis build.  I'll try to provide a fix for lxc next week.

We have docker 1.8 already, closing this.


Int overflow on 32bit architectures

I expected (perhaps wrongly) that Yojson would use an underlying int64 to parse json integer values into.
The following code fails on 32bit architectures (ARM/x86/ppc32) but passes on 64bit:
utop # Yojson.Basic.from_string {|
{"id":<PHONE_NUMBER>}
|};;
Exception: Yojson.Json_error "Line 2, bytes 6-17:\nInt overflow '1670148491'".

The underlying issue is the use of max_int and min_int when parsing integer values at
https://github.com/ocaml-community/yojson/blob/b743857a28f02af68bcfadb515df0b21a9c6eb06/lib/read.mll#L81-L82
Slightly longer stacktrace showing the path from Yojson.Basic.from_string to the error
[exception] Yojson.Json_error("Line 1, bytes 6-17:\nInt overflow '1670148491'")
            Raised at Yojson.json_error in file "common.ml", line 5, characters 19-39
            Called from Yojson.Basic.read_json in file "lib/read.ml" (inlined), line 1025, characters 3-39
            Called from Yojson.Basic.__ocaml_lex_read_json_rec in file "lib/read.mll", line 238, characters 41-59
            Called from Yojson.Basic.read_json in file "lib/read.ml" (inlined), line 1025, characters 3-39
            Called from Yojson.Basic.__ocaml_lex_read_json_rec in file "lib/read.mll", line 258, characters 28-46
            Called from Yojson.Basic.read_json in file "lib/read.ml" (inlined), line 1025, characters 3-39
            Called from Yojson.Basic.from_lexbuf in file "lib/read.mll", line 1109, characters 8-26
            Called from Yojson.Basic.from_string in file "lib/read.mll", line 1122, characters 6-26
            Called from Dune__exe__Test.Make.test.(fun) in file "test/test.ml", line 55, characters 55-68
            Called from Alcotest_engine__Core.Make.protect_test.(fun) in file "src/alcotest-engine/core.ml", line 180, characters 17-23
            Called from Alcotest_engine__Monad.Identity.catch in file "src/alcotest-engine/monad.ml", line 24, characters 31-35

Before I start on making the change, would a PR fixing this issue be welcome?

I think this is because you're using Basic which doesn't include the  `Intlit variant, so even if it could parse a number that exceeds the signed int31 range that OCaml supports on 32-bits, there is still no way to represent it in the output in the Basic.t type.
Note that Yojson.Safe.from_string should work and give you an `` Intlit "1670148491" (lacking a 32-bit system at hand I can't test), on 64-bits this works: Yojson.Safe.from_string "4611686018427387904"


[Model Deprecation]: io.catenax.single_level_usage_as_planned/1.0.0 /SingleLevelUsageAsPlanned

Update Reason
Deprecation due to an updated model version: SingleLevelBomAsBuilt 1.1.0
MS1 Criteria

[ ] The model that should be deprecated exists and is not deprecated already
[ ] The respective model does not affect existing use cases (aspect is either used in higher versions or replaced by a different aspect)
[ ] A shared aspect, which will be deprecated, is not used by any released aspect model

modeling_team


need it as a synchronous answer and not callback/promise

Is this possible?

You can use callbacks or promises, whichever you prefer.  See the docs for more info

are you aware of any other code library that does it synch?


remove empty data

When using the Statamic Eloquent driver, empty data comes in as empty strings, which can cause problems on fields that are expecting an array.
If the data is "empty" don't include it.

Thanks!

Thanks!


Banner stars fix

hey @jsaleigh not sure why these circleci checks still keep failing :( let me know if you know what I need to do

@jeanmw there's something going on with Sauce Labs, i need to dig in and figure it out

Besides the tests, the code looks good.  We especially need those tests for this particular PR though, so I have to wait to merge it.

@jsaleigh no worries thanks for checking it out - let me know if I can help

@jeanmw I manually ran the tests, it all looks good. We just need device testing now.  Merging to master.


Update report

Codecov Report

Merging #1553 (2e3788b) into master (edda64a) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1553      +/-   ##
==========================================
+ Coverage   98.50%   98.62%   +0.11%
==========================================
  Files          91       91
  Lines        7215     7325     +110
  Branches     1253     1258       +5
==========================================
+ Hits         7107     7224     +117
+ Misses         66       62       -4
+ Partials       42       39       -3

Impacted Files
Coverage Δ

src/schemathesis/cli/__init__.py
99.20% <100.00%> (+<0.01%)
:arrow_up:

src/schemathesis/cli/context.py
100.00% <100.00%> (ø)

src/schemathesis/cli/output/default.py
99.42% <100.00%> (+0.61%)
:arrow_up:

src/schemathesis/service/__init__.py
100.00% <100.00%> (ø)

src/schemathesis/service/ci.py
100.00% <100.00%> (ø)

src/schemathesis/service/events.py
100.00% <100.00%> (ø)

src/schemathesis/service/report.py
100.00% <100.00%> (ø)

src/schemathesis/_compat.py
58.06% <0.00%> (-6.46%)
:arrow_down:

src/schemathesis/cli/cassettes.py
98.87% <0.00%> (-1.13%)
:arrow_down:

src/schemathesis/utils.py
96.82% <0.00%> (-0.80%)
:arrow_down:

... and 30 more

Continue to review full report at Codecov.

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


Is it Possible to Support the on_click Argument for st.download_button?

What I require is to trigger a function when the user clicks on st.download_button.
The implementation would be like this:
st.download_button(
label='title',
data=virtual_workbook,
file_name=f"BEPChecker_by_turboIFC {timestamp}.xlsx",
mime=report_workbook.mime_type,
on_click=save_download_event
)
If anyone has an idea on how to accomplish this, feel free to reply.

See here https://github.com/PaleNeutron/streamlit-ext/issues/8


Removing channels

I have a question. What would be a valid condition for removing a channel from the list?

If it's your channel and you no longer want it on the list. Or if it was deleted.


Amplify CLI Plugin Scan Failed

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Which Category is your question related to?
Amplify CLI Plugin scan failed.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
~/D/4/taskmaster   notifications ±  amplify -v
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)
~/D/4/taskmaster   notifications ± 
What AWS Services are you utilizing?
Provide additional details e.g. code snippets
I uninstalled and reinstalled Amplify CLI. Keep getting the same errors over and over.
~/D/4/taskmaster   notifications ±  amplify -v
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)
~/D/4/taskmaster   notifications ± 

Hello @martinpapacodes What OS are you installing the CLI on?

macOS Mojave
Version 10.14.6

Interesting to see the error is from a ts file. It should
How did you install the Amplify CLI?

@martinpapacodes I've seen this error when using Node version < 10.x
What's the node version you're using?

I'm having the same issue as OP.
Node version: 12.16.1
NPM version: 6.13.14
yarn version: 1.22.0
OS: Windows 10 Home, Version 1809, OS Build 17763.1039
I installed the amplify cli in my root directory C:\npm install -g @aws-amplify/cli
I successfully got to the post-install.js, "Successfully installed the Amplify CLI...Javascript Getting Started...". Anytime I run an amplify command, I receive the same error as OP. This includes amplify init, amplify -v, etc. This is the same error whether I run them in the root directory or my project directory.
I've tried reinstalling node, npm, yarn, webstorm, and amplify, and have also deleted and re-cloned my project from github. The set-up has worked for other members of my team without issue, but does not work on my environment, although it was working roughly 2 months ago when we began the project. Error started last week when we re-visited the project (I did have to pull it from master this time around.)
Willing to provide any other information necessary to assist with troubleshooting :)

Is there any movement on this? We're having the same issue also.

I have been having same exact problem.  I was using amplify cli fine without issue, then suddenly started to receive this error with every amplify command.  I have tried uninstalling and reinstalling node, npm, amplify but end up with
amplify configure
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)
➜  healthisland git:(develop) amplify -v
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)

Hey guys, could you'll please install the latest version of the CLI - 4.14.1 and see if you're having this issue. As a a part of the latest release we clear the esm cache for the amplify CLI which I suspect is causing this issue.

Hi @kaustavghosh06 .  unfortunately that didnt do it for me.  Here is my output:

Successfully installed the Amplify CLI
Javascript Getting Started - https://aws-amplify.github.io/docs/js/start
Android Getting Started - https://aws-amplify.github.io/docs/android/start
iOS Getting Started - https://aws-amplify.github.io/docs/ios/start

<EMAIL_ADDRESS>updated 1 package in 30.37s
➜  healthisland git:(develop) ✗ amplify configure
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)
➜  healthisland git:(develop) ✗ amplify -v
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)

Steps I took:
C:\ npm -g uninstall @aws-amplify/cli
successfully uninstalled, then
C:\ npm -g install<EMAIL_ADDRESS>reached post install screen (successfully installed the amplify cli, JavaScript getting started...)
C:\ amplify -v
Result: plugin scan failed (same error as before)
C:\mydirectory\myproject
Result: plugin scan failed (same error as before)
No changes with 4.14.1

This issue is blocking some of our new developers from onboarding onto our Amplify-based project.
Any update on this issue?

I've tried on different node versions and different CLI versions and I couldn't reproduce.
Could you please go to this line of the code  /usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11, and insert one line of code to help us to diagnose?
    print.error(JSON.stringify(e));

The exact spot for me was a little different than mentioned, but I think I found the right place for the print statement: (was line 121 for me). It produced the read out:
C:\>amplify -v Scanning for plugins... Plugin scan failed. {"errno":-4048,"code":"EPERM","syscall":"open","path":"C:\\Users\\adamo\\.amplify\\plugins.json"} Plugin scan failed. Error: Plugin scan failed.     at scan (C:\Users\adamo\AppData\Roaming\npm\node_modules\@aws-amplify\cli\src\plugin-manager.ts:138:4)

It seems the CLI does not have the permission to open an essential file resided in ~/.amplify/plugins.json.
This can be caused by reasons like, the file is open by some other program, or you didn't grant the CLI permission to access it.
You can remove that file (which will be regenerated by the CLI upon scan), and then run amplify plugin scan with admin right.

That seems to have solved the problem. @UnleashedMind

@UnleashedMind this worked for me as well.  Thank you.
On Wed, Mar 11, 2020 at 1:29 PM Montana<EMAIL_ADDRESS>wrote:

That seems to have solved the problem. @UnleashedMind
https://github.com/UnleashedMind
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/3560#issuecomment-597930285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE7S7UVEWYPGDS7HZ5MNOTTRHANEZANCNFSM4LAPRFHQ
.

Looks like its the same issue for everyone on this thread. Please let us know if @UnleashedMind's workaround didn't work for you and we'll re-open the thread.

Unfortunately it started again just days after following @UnleashedMind
workaround.  The original problem seems to still need to be addressed.
On Wed, Mar 11, 2020 at 3:11 PM Kaustav Ghosh<EMAIL_ADDRESS>wrote:

Closed #3560 https://github.com/aws-amplify/amplify-cli/issues/3560.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/3560#event-3121064471,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE7S7UXVCUCVXV3H3VHFTCLRHAZDPANCNFSM4LAPRFHQ
.

cp ~/.amplify/plugins.json ~/Desktop
sudo rm -rdf ~/.amplify
mkdir ~/.amplify
touch ~/.amplify/plugins.json

Finally, we need copy entity (not file) ~/Desktop/plugins.json to ~/.amplify/plugins.json
That works for me

Or, simply
sudo chown -R <user> ~/.amplify


Pass backend properties in a sane manner.

What is the expected enhancement?
Currently the backend properties are a nightmare to parse through.  Basically one has to go through nested lists of items to find what one is looking for.  For example, finding the readout_error on all the qubits requires:
readout_errors = []
for qubit in backend.properties().qubits:
    for item in qubit:
        if item.name == 'readout_error':
            readout_errors.append(item.value)

This is not an ideal way to do things.
The interface should be changed so that it is easier to extract the data needed.  For example it is easy to recast the above to look something like:
[qubit['readout_error'].value for qubit in backend.properties().qubits]

where qubit here is an object representing the qubit (As opposed to a list):
backend.properties().qubits[0]

Qubit 0
    T1 60.507043 us
    T2 119.551747 us
    anharmonicity -0.318653 GHz
    frequency 5.269249 GHz
    prob_meas0_prep1 0.0124
    prob_meas1_prep0 0.0044
    readout_error 0.0084
    readout_length 732.444444 ns

with items accessible in a logic manner, e.g.
backend.properties().qubits[0].T1.calibration_time

datetime.datetime(2021, 9, 14, 9, 43, 12, tzinfo=tzlocal())

Because this is a new package we have the opportunity to do things better this time around.

FYI, there are a couple of other easy ways to do this today, using the readout_error method in the BackendProperties class.

Using range and len

props = backend.properties()
readout_errors = [props.readout_error(i) for i in range(len(props.qubits))]
readout_errors

Using enumerate

props = backend.properties()
readout_errors = [props.readout_error(i) for i, qubit in enumerate(props.qubits)]
readout_errors

But I agree that this can be simplified as proposed in this issue.

That is true because someone does the for-loop behind the scenes for you.

BTW, qiskit_ibm uses the BackendProperties class from terra.
https://github.com/Qiskit-Partners/qiskit-ibm/blob/16d60753b00d9f1a82ed0c5f2f709f174b21caa7/qiskit_ibm/ibm_backend.py#L456
Is terra the right place to fix this then? @mtreinish @jyu00

As someone who had to parse through the properties file, I agree it can use some improvement. But as @rathishcholarajan pointed out, the structure of the backend properties is defined by BackendProperties in qiskit-terra. So instead of making any extra convenience methods IBMQ only, I think it makes more sense for them to go into BackendProperties.

My goal is for backend properties and backend configuration to disappear from the user facing backend api. It shouldn't have ever been a user facing class, it started as just an marshmallow object model of the iqx wire protocol for the properties data and the API is basically a 1:1 mapping with the json format. I've proposed dropping it from BackendV2 (which is still wip here: https://github.com/Qiskit/qiskit-terra/pull/5885 ) although for backwards compat you'll probably need to keep it around for a while in qiskit-ibm.

@mtreinish it's nice to decouple the user interface from the backend api!
@nonhermitian I think we can close this issue since it makes more sense to add/make the user interface changes you want in BackendV2?

Yeah I am good with that.


Examples or Reasons for usage of Distance Based on Arc Cosine for Similiarity in USE Paper

Dear TF Hub Team,
USE paper  Section 5 has a interesting paragraph on evaluation where authors use Arc Cosine (Cos Inverse) whose range is 0 to Pi in radians instead of plain cosine distance with range 0 to 2.
". For the pairwise semantic similarity task, we directly assess
the similarity of the sentence embedding produced by our two encoders. As shown Eq. 1, we
first compute the cosine similarity of the two sentence embedding and then use arccos to convert
the cosine similarity into an angular distance.
We find that using a similarity based on angular distance
performs better on average than raw cosine similarity.
"
This is interesting at the same time vague without giving much clarity on pressing reason for the usage of same when we have simple 1-cosine similarity (Clipped at -1 and 1) giving cosine distance in the range 0 to 2.
Can we get empirical evidences,examples or intuitions in addition to the statement above ("We find that using a similarity based on angular distance performs better on average than raw cosine similarity.") that made authors to use 1 - arccos(cosine similarity)/pi instead of 1- cosine similarity? What do we mean by perform here? Against what parameters the performance was better? Do we have a reasoning for this improvement in performance?
This question is important as many downstream tasks use USE for semantic similarity and if there is strong empirical evidence to use the 1-arccos instead of 1-cosine_similiarity, then it will be highly beneficial for consumers to use the same in their applications.

Answering my own query. It appears to be because at small angles plain cosine distance may not provide a good separation. Beautifully explained [here ].  What happens because of this is if there are two sentences both are highly similar to given sentence, but for some reason intuitively one is little more similar to another, plain cosine distance will not be able to give clear separation distance scores, while arccosine based distance can do it. (https://math.stackexchange.com/questions/2874940/cosine-similarity-vs-angular-distance). This information helps a lot to use arccos based distance as objective rather than plain similiarity in siamese finetuning task I am working on. Thanks for

Closing the issue as it has been resolved. Thanks!


get_helm.sh doesn't work

Right now I have downloaded get_helm.sh, and while I use the exact arguments it suggests, it claims they are inalid:
[root@contcicd] 13:00 ~ 1# ./get_helm.sh --version v2.9.1
curl: (35) Peer reports incompatible or unsupported protocol version.
Cannot determine v2.9.1 tag.
Failed to install helm with the arguments provided: --version v2.9.1
Accepted cli arguments are:
        [--help|-h ] ->> prints this help
        [--version|-v <desired_version>] . When not defined it defaults to latest
        e.g. --version v2.4.0  or -v latest
        For support, go to https://github.com/kubernetes/helm.
[root@contcicd] 13:01 ~ 1# ./get_helm.sh --version latest
curl: (35) Peer reports incompatible or unsupported protocol version.
Cannot determine latest tag.
Failed to install helm with the arguments provided: --version latest
Accepted cli arguments are:
        [--help|-h ] ->> prints this help
        [--version|-v <desired_version>] . When not defined it defaults to latest
        e.g. --version v2.4.0  or -v latest
        For support, go to https://github.com/kubernetes/helm.
[root@contcicd] 13:10 ~ 1# ./get_helm.sh -v latest
curl: (35) Peer reports incompatible or unsupported protocol version.
Cannot determine latest tag.
Failed to install helm with the arguments provided: -v latest
Accepted cli arguments are:
        [--help|-h ] ->> prints this help
        [--version|-v <desired_version>] . When not defined it defaults to latest
        e.g. --version v2.4.0  or -v latest
        For support, go to https://github.com/kubernetes/helm.

Output of helm version:
Does not matter, but the installed is 2.8.0
Output of kubectl version:
Doesn't matter, but:
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:23:29Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS

I just tried this on my local machine and it worked perfectly.
What OS are you using, which version and which version of curl and openssl are you using?

Os Linux, Ubuntu 18.04.
$ curl --version
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

$ openssl version
OpenSSL 1.1.0g  2 Nov 2017

This looks more like the attributes handling issue FWICT.

I just tried it right now on a new box and I have no issues, that's why I think there's something else going on.
vagrant@vagrant:~$ uname -a
Linux vagrant 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
vagrant@vagrant:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"
vagrant@vagrant:~$ curl --version
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL
vagrant@vagrant:~$ curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6740  100  6740    0     0  21329      0 --:--:-- --:--:-- --:--:-- 21329
vagrant@vagrant:~$ chmod 700 get_helm.sh
vagrant@vagrant:~$ ./get_helm.sh --version v2.9.1
Downloading https://kubernetes-helm.storage.googleapis.com/helm-v2.9.1-linux-amd64.tar.gz
Preparing to install into /usr/local/bin
helm installed into /usr/local/bin/helm
Run 'helm init' to configure helm.
vagrant@vagrant:~$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

@OndraZizka you may want to make sure that your ca-certificates package is up to date and you're able to use TLS 1.2
https://githubengineering.com/crypto-removal-notice/
Github deprecated older protocols and the curl error that you're seeing is indicative of a TLS protocol issue.
> docker run -it ubuntu:18.04 /bin/bash
Unable to find image 'ubuntu:18.04' locally
18.04: Pulling from library/ubuntu
a48c500ed24e: Pull complete
1e1de00ff7e1: Pull complete
0330ca45a200: Pull complete
471db38bcfbf: Pull complete
0b4aba487617: Pull complete
Digest: sha256:c8c275751219dadad8fa56b3ac41ca6cb22219ff117ca98fe82b42f24e1ba64e
Status: Downloaded newer image for ubuntu:18.04
root@0f0169786072:/# apt-get update
...
Reading package lists... Done
root@0f0169786072:/# apt install curl
...
done.
root@0f0169786072:/# apt list installed ca-certificates
Listing... Done
ca-certificates/bionic,now 20180409 all [installed,automatic]
root@0f0169786072:/# curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6740  100  6740    0     0  36630      0 --:--:-- --:--:-- --:--:-- 36630
root@0f0169786072:/# chmod 700 get_helm.sh
root@0f0169786072:/# ./get_helm.sh
Downloading https://kubernetes-helm.storage.googleapis.com/helm-v2.9.1-linux-amd64.tar.gz
Preparing to install into /usr/local/bin
helm installed into /usr/local/bin/helm
Run 'helm init' to configure helm.

Closing as working. I just tested it and it works. @jgleonard has the right idea.

Wouldn't it be great if Helm didn't say Accepted cli arguments are: if nothing is wrong with the arguments?

And instead it could say what's really wrong.


use of undeclared type or module parity_scale_codec

use parity_scale_codec::{Encode, Decode};

gives me the following error
use of undeclared type or module `parity_scale_codec`

even if i use the older version
use parity_codec::{Encode, Decode};

Did you added it to your Cargo.toml?

no

Than you have your bug.

in some parts of substrate, parity_scale_codec is imported simply as codec


Theocracy flag

Why does the theocracy flag have the Unitarian logo on it? (AKA the flaming margarita). Say what you will about Unitarians, they are unlikely to establish a theocracy, how about something with a cross?

After a long back and forth it was decided that a simplified version of their flag was the best way to represent a non-denominational religious government, if you have a better idea for a symbol of religious rule that doesn't specially associate with a particular religion like the cross does to christianity, I'm open to changing it.

How about this bad boy https://en.wikipedia.org/wiki/Eye_of_Providence

Not a bad idea, I'll try making a flag out of it when I have free time

You could always differentiate between major types of theocracy, such as Catholic Integralism or Islamism. Questions like 'How many Gods are there?' and 'Is the Pope the leader of the Christian world?' would do well. Most theocracies tend to be pretty specific on beliefs.

Having specific theocracries seems kind of unnecessary since it would just be a test of the user's religion.


[DCOS-52831] Add Grafana dashboard to C* project with README

What changes are proposed in this PR?
Resolves DCOS-53276
add the Grafana dashboard as a file inside the Cassandra project.
The idea here is that we want users to be able to deploy their Cassandra cluster (or clusters) and right after easily deploy the monitoring service so they can properly track metrics.
How were these changes tested?
Manually testing

The 1.13 dashboard looks good. Please do the same w/ 1.12 and rebase this branch w/ master

@samvantran should we be merging it with master or keep a separate branch for dashboard/alerts , as finally we have to merge this code into grafana-dashboards repo.

should we be merging it with master or keep a separate branch for dashboard/alerts , as finally we have to merge this code into grafana-dashboards repo.

Good point @viivek46. Okay let's close this PR and create a new one to point to a branch specific to dashboards-and-alerts similar to what we did in Kafka: https://github.com/mesosphere/dcos-kafka-service/pull/418

closing this PR and creating new PR pointing to "cassandra-dashboards-and-alerts" branch

@samvantran  new PR : https://github.com/mesosphere/dcos-commons/pull/3075


Bug: XMLHttpRequest doesn't work with https

After some troubleshooting I've found that connections made using https never gets a response.
Can you fix this?
Thanks!

What version of python are you using?

2.7.9

This is a known issuse with python 2.7.8 and 2.7.9. We do not yet have a fix.

Oh I see.

It seems that ssl works with gevent/requests using this fork for gevent.
Just need to install cython as well:
pip install -U cython git+git://github.com/NextThought/gevent@8ac8febedfbb3afa5af9080af2c2f5b8d0283770#egg=gevent

Of course this is not the solution, but while we are waiting for gevent to update...

Fixed.


Debian 11 raise an error

During execution convert WHL package on Debian package raises an next error:
Traceback (most recent call last):
  File "~/log_functions/.venv/bin/wheel2deb", line 5, in <module>
    from wheel2deb import main
  File "~/log_functions/.venv/lib/python3.9/site-packages/wheel2deb.py", line 12, in <module>
    from _wheel2deb.debian import SourcePackage
  File "~/log_functions/.venv/lib/python3.9/site-packages/_wheel2deb/debian.py", line 10, in <module>
    from .depends import suggest_name, search_python_deps, normalize_package_version
  File "~/log_functions/.venv/lib/python3.9/site-packages/_wheel2deb/depends.py", line 5, in <module>
    from .apt import search_packages
  File "~/log_functions/.venv/lib/python3.9/site-packages/_wheel2deb/apt.py", line 2, in <module>
    import apt
ModuleNotFoundError: No module named 'apt'

I check python3-apt is installed but outside an virtual environment.
How to avoid to use apt package module?

When initiating your virtual enviroment use --system-site-packages. This makes the system packages available inside the Virtual enviroment. Thats how i fixed this error. see also https://stackoverflow.com/questions/12079607/make-virtualenv-inherit-specific-packages-from-your-global-site-packages

It turns out that building Debian packages is only possible on a Debain compatible distribution? In general, of course, this is not such a big problem, but perhaps not using apt could allow more distributions to be supported? And why is the apt module needed in principle, so I understand that dpkg-deb is enough to organize the Debain package?

I'm not a developer of wheel2deb or not associated with its maintainers, just someone who had the same problem with virtual environments last week or so ;)
With a quick look over the code base, i think the apt module is used to search for valid package names. The deb generation itself only needs dpkg-deb.

Make sure you are running the latest release. python3-apt is no longer a dependency.


skim: correctly name default options

skim uses the SKIM_DEFAULT_OPTIONS environment variable rather than SKIM_DEFAULT_OPTS.
The other (_OPTS) environment variables are still correct however as they seem to have a different naming convention.

Thanks! Rebased to master in 734128930f3721bc45fc085ab132b225a8bc5981.


Add files upload on a talk proposal

The idea is to have pictures to be used to communicate about a talk when it is scheduled.
That could be 1 or 2 pictures for example, no need to have more.

Done in 742aec627051da7fd1c615f6e6aa09cd613e4208


Update pretraining.py

fix eval file path

fix eval file path

The next two instances of "train_file_dir" should also be changed to "validation_file_dir".