Fix actions by legacy cluster endpoints

Signed-off-by: Sruti Parthiban<EMAIL_ADDRESS>Is your feature request related to a problem? Please provide an existing Issue # , or describe.
https://github.com/opensearch-project/performance-analyzer/issues/20
Describe the solution you are proposing
Fix the actions performed by the legacy API.
[root@e2eba3ca732e opensearch]# curl localhost:9200/_opendistro/_performanceanalyzer/rca/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}'
{"currentPerformanceAnalyzerClusterState":1,"shardsPerCollection":0,"batchMetricsRetentionPeriodMinutes":7}[root@e2eba3ca732e opensearch]#
[root@e2eba3ca732e opensearch]#
[root@e2eba3ca732e opensearch]# curl -XGET http://localhost:9200/_opendistro/_performanceanalyzer/cluster/config
{"currentPerformanceAnalyzerClusterState":3,"shardsPerCollection":0,"batchMetricsRetentionPeriodMinutes":7}

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Check List

[x] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #21 (a6fabc7) into main (762286f) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

:exclamation: Current head a6fabc7 differs from pull request most recent head 9211665. Consider uploading reports for the commit 9211665 to get more accurate results

@@             Coverage Diff              @@
##               main      #21      +/-   ##
============================================
- Coverage     72.21%   72.13%   -0.09%
- Complexity      348      349       +1
============================================
  Files            44       44
  Lines          2473     2476       +3
  Branches        155      158       +3
============================================
  Hits           1786     1786
- Misses          584      585       +1
- Partials        103      105       +2

Impacted Files
Coverage Δ

...config/PerformanceAnalyzerClusterConfigAction.java
87.23% <100.00%> (+0.87%)
:arrow_up:

...ormanceanalyzer/writer/EventLogQueueProcessor.java
58.33% <0.00%> (-5.00%)
:arrow_down:

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 762286f...9211665. Read the comment docs.


Fetch available models from chatgpt before asking question

Closes #6
Fetches the available model names using ChatGPT API.
This ensures that the models available for the user are used. For ChatGPT plus subscribers the paid model is used, making availability better.

Thanks for opening this. Looks good to me, except could you store the model name in the browser cache instead of in a local variable?

@shobrook Yeah that sounds like a good idea! I already pushed the changes.
I have added it to the same cache as access token. This way if OpenAI pushes a new model (like happend today), that model will be used when the cache expires.

Hi @shobrook,
Any more changes needed?


Zoom to AWS S3

Hi mate
Are you interest in a Python gig?
I would like a tool that recieves the zoom webhook that a zoom cloud recording is ready, then uploads the file to AWS s3 and then sends an email notification that the file once the file has finished being uploaded.

Hi, thanks for the offer, but I'm not in that line of work at the moment.
Feel free to fork the project and reach out to someone on Fiverr.com for help.
Cheers.
RR

On 04/29/2021 3:05 AM Sky Richardson<EMAIL_ADDRESS>wrote:

Hi mate

Are you interest in a Python gig?

I would like a tool that recieves the zoom webhook that a zoom cloud recording is ready, then uploads the file to AWS s3 and then sends an email notification that the file once the file has finished being uploaded.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/ricardorodrigues-ca/zoom-recording-downloader/issues/12 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AIKBGCD6OMCK33PMLUF6JKDTLEALNANCNFSM43ZH4WYQ .

Thanks for getting back to me. Great project by the way.
On Fri, 30 Apr 2021 at 02:05, ricardorodrigues-ca @.***>
wrote:

Hi, thanks for the offer, but I'm not in that line of work at the moment.
Feel free to fork the project and reach out to someone on Fiverr.com for
help.
Cheers.
RR

On 04/29/2021 3:05 AM Sky Richardson @.***> wrote:
Hi mate
Are you interest in a Python gig?
I would like a tool that recieves the zoom webhook that a zoom cloud
recording is ready, then uploads the file to AWS s3 and then sends an email
notification that the file once the file has finished being uploaded.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ricardorodrigues-ca/zoom-recording-downloader/issues/12
, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIKBGCD6OMCK33PMLUF6JKDTLEALNANCNFSM43ZH4WYQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ricardorodrigues-ca/zoom-recording-downloader/issues/12#issuecomment-829367703,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2M4XEW74OCXUL4XHSAVDTLF7WHANCNFSM43ZH4WYQ
.


Use juju-bundle to simplify testing logic

juju-bundle is a bundle management plugin for juju maintained by @knkski.

a juju plugin is any executable binary in $PATH that has the name juju-*, you can call it as juju foo instead of juju-foo so they're called plugins, but really it's just a convenience bit of functionality, instead of being a plugin to juju itself

most of the kubeflow CI/CD uses it, because it handles stuff like filling in default resources. Here's a couple of examples:
https://github.com/canonical/kfp-operators/blob/master/.github/workflows/integrate.yaml#L65
https://github.com/canonical/kfp-operators/blob/master/.github/workflows/publish.yaml#L29-L32
https://github.com/canonical/bundle-kubeflow/blob/master/.github/workflows/publish.yaml#L34-L36

If you were to create a charms directory at the root of this repo and create a symlink inside for each charm with e.g. ln -s ../../prometheus-operator prometheus, you could run juju bundle deploy --build to have each charm built and deployed as part of the bundle. Does that meet your needs vs a bundle template? Otherwise, I'd be interesting in see if juju-bundle could be expanded to meet any extra needs.

I've updated the juju-bundle plugin to handle these four use cases:
juju bundle deploy                           # Don't build anything
juju bundle deploy --build                   # Build every app with a source
juju bundle deploy --build foo bar           # Build both `foo` and `bar` from their sources
juju bundle deploy --build foo bar=../bar    # Build `foo` from its source, and build `bar` with a source of `../bar`

it also has a few other features, e.g. instead of using {%- if testing %} to include the avalanche app, you can just include it and use juju bundle deploy --exclude avalanche when you don't want to include it

you could run juju bundle deploy -b /tmp/RANDOM/bundle.yaml --build alertmanager=../
the juju-bundle plugin would then go off and build alertmanager only, save an updated bundle.yaml to a tempfile
--- @knkski

So with juju-bundle the tests may looks like this:
Alertmanager integration tests:

alertmanager tox command downloads lma bundle
alertmanager tox command calls juju bundle deploy -b /path/to/lma/bundle.yaml --build alertmanager={toxinidir}
alertmanager tox command calls pytest on lma bundle (same as now)
lma test runs tests but does not build anything, only deploys the bundle

lma bundle integration tests:

lma bundle tox command calls juju bundle deploy -b /path/to/lma/bundle.yaml
lma bundle tox command calls pytest (same as now but do not build anything)

Juju bundle is deprecated and unmaintained, and we should look to replace it rather than adopt it. 😅


Lazily loading separate documents?

First of all, thank you for this project. I’ts awesome :)
This issue is more of a question than anything else: I see that when you select a page in the top bar (for instance Gallery, Resources, About...) the page loads without redirecting to other url; and perhaps showing a blinking Panel logo while the page loads.
My question is basically how is it done, because it looks and feels really slick! I have tried to look it up in the code but I’m unsure where it happens. Is it all part of the same Bokeh document? Or is there a Bokeh Document for each page? And in that case, how are you able to switch between documents without triggering a url redirect?
Thank you! I’m really interested in knowing how it works :)

Thanks for the nice feedback!
The basic answer is that I have

one document (a Template) with among other a main Column.that holds the active page (it self most often a Column).
a parameterized class page_service with an ObjectSelector parameter page that holds the active page and with the list of pages as objects.

When the user changes the active page via the select widget the function _update_main_container then replaces the content of the main container.
The functionality to change the page can be found here
    @param.depends("services.page_service.page", watch=True)
    def _update_main_container(self):
        with self.services.progress_service.mark_active(
            f"Loading {self.services.page_service.page.name}"
        ):
            if self.services.page_service.page.show_loading_page:
                self.main[:] = [self.loading_page_component.main]

            main_instance = self._application_page_instance.main
            main_instance.align = "center"
            main_instance.sizing_mode = "stretch_width"

            self.main[:] = [
                self._main_spacer,  # Trick to force main to stretch to full width of appContent
                main_instance,
            ]

Hope this guides you in the right direction. Feel free to ask more questions in order to get a good understanding.

Below I will write a little bit of my thoughts behind the design of awesome-panel.org and the vision for it.

My understanding of Panel is that

it can be a really, really powerful platform for building your product using all the power of Python and bringing it to your users very, very quickly.
It is in fact possible to use for both beginning domain experts like analysts, engineers, traders, data engineers and data scientists and for experienced software developers. There is something for everyone. And they can collaborate on a common Platform.

But it is not really, yet demonstrated that you can build a consistent, modern, secure and performant application in Panel and how.
So I've set out to explore and build this. Both for my own fun and need. But also to help colleagues and fellow Pythonistas.

One place I look for inspiration is in BI Tools like Power BI and Tableau. They are not nearly as powerful or flexible as Panel but using them it is very easy to develop something consistent and deploy it fast and securely.

Another thing I cant settle my mind on is really micro app versus (monolith) app platform. In some situations users would like to deploy apps as micro apps in one container for each app and maybe bind things together using reverse proxies etc.
In some situations users would like to avoid all the DevOps stuff and just have one application to deploy, monitor and maintain. But an application that is really a platform for building and deploying small apps.
I'm a little old fashion still so I tend to like the last solution. I fear ending up in container and devops hell.

I have been thinking a lot about whether to have one document and load pages lazily as currently done for awesome-panel.org or just use pn.serve to serve the pages at different urls that needs to be loaded.
The first is faster, more modern and can keep the state.
The second may give a simpler application and it's easier to have different layouts and styles.
I think eventually I will end up supporting both. Some pages will load dynamically and some pages will just link to another url.
For example I have a Material Designer application coming up where the user can select colors according to the Material color scheme and see how the existing Panel layouts, panes and widgets look in that theme (Dark theme yes :-)). I dont know yet if that will work out nicely working together with the rest of the pages. So maybe that will be served at a seperate url.
I also have an intention one day to show case other themes than Material on which awesome-panel.org is currently built. For example Golden or SAP UI 5 (yes SAP and Python - weird combination :-)). SAP has actually released the most comprehensive set of web components and they work really, really well with Panel.
I also have then intention one day to show case that you can build really, really nice looking dashboards and applications in Panel. Something that is just as nice as what people show case in Power BI, Panel or Dash. Those technologies focus on look and feel while Panel so far has focused on raw power and the underlying technology.
FYI. @philippjfr

@julioasotodv . My wish is actually that one day there is a general purpose application package for Panel. it could be the awesome-panel python package, it could be provided by Panel it self or maybe someone else.
Currently I am still learning and refactoring. But my intention is to polish, mature and document so that what I have built can be used by others.
But for that I would need someone who would like to use something like this and would be willing to guide how the api current feels and how it should feel.

@julioasotodv
One thing that is not yet in awesome-panel.org is a better use of the url. I would like to set the url parameter to ?page=home etc when navigating to home etc.
I would also like to be able to save more of the state (like slider values etc.) in the url parameters.
Philipp has developed the Location component for this use case. I just have not had the time to try it out and start using it yet. See https://github.com/holoviz/panel/pull/1150

Regarding data and dataframes I have to things I would like to integrate.
My applications often contain one or more dataframes of data. I would like some general application functionality that enables selecting from a list of dataframes and downloading.
That is really what the disabled download icon in the upper right indicates as an upcoming feature.

Similarly I would like some general application functionality for dataframes that enables the user to select, explore and pivot a dataframe. I believe I would use the PerspectiveViewer for this.
I believe the last functionality would be really, really powerful and something that BI tools do not provide today.

And finally I think what makes Panel so powerful is really param and reactive programming. When I look at Streamlit, Voila and Dash its either not possible or not really communicated.
So I would really, really like to understand and describe how to build larger applications using param and reactive programming. What is the Model-View-Controller (MVC) framework for Panel?
I'm experimenting with a Model-Service-Component-View model but have a feeling that might be too much for Panel and Panel users.

@MarcSkovMadsen - I truly think you should publish your vision as a part of the documentation and not here. Thanks for the amazing work!

@MarcSkovMadsen - I truly think you should publish your vision as a part of the documentation and not here. Thanks for the amazing work!

Thanks all. Will close this one as the original request has been answered.

Thanks all. Will close this one as the original request has been answered.


Helper line feature!!

Hello sir, I want to add helper line feature when drag node, can you give me some advice?
Where should I start, and what should I focus on?
Thanks, @wanglin2

You may need to modify /plugins/Drag.js


Update 404 link to Azure OpenAI reference

Points to 2024-12-15-preview (doesn't exist), should be 2024-02-15-preview like the rest of the links

@mrbullwinkle
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


General Question

I wanted to perform face verification, correct me if i'm wrong, but most of the recognition models are trained on a million images or so,
I was thinking if i could combine most of the open-source datasets like 1millionceleb, facesemore, lfw etc, and train the network, would that give me a better face embedding?
What do you think?
Thanks in advance.

Thank you for your question. Yes, surely you can if you have the name list of each database you want to merge, otherwise there may exist overlapping parts in your merged version, which may confuse your network during classifying these subjects.


Getting an error when installing the corresponding Gym environments

After installing Mujoco 2.1.0 (new open source package), I have set the .bashrc to
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/user/.mujoco/mujoco210/bin
(When I install mujoco-py it requested to set the path as this) but now the error message says:
You appear to be missing MuJoCo.  We expected to find the file here: /home/user/.mujoco/mjpro150
pip install gym[mujoco,robotics]
Requirement already satisfied: gym[mujoco,robotics] in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (0.15.7)
Requirement already satisfied: scipy in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from gym[mujoco,robotics]) (1.5.4)
Requirement already satisfied: numpy>=1.10.4 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from gym[mujoco,robotics]) (1.18.5)
Requirement already satisfied: six in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from gym[mujoco,robotics]) (1.16.0)
Requirement already satisfied: cloudpickle~=1.2.0 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from gym[mujoco,robotics]) (1.2.1)
Requirement already satisfied: pyglet<=1.5.0,>=1.4.0 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from gym[mujoco,robotics]) (1.5.0)
Collecting mujoco-py<2.0,>=1.50
  Using cached mujoco-py-<IP_ADDRESS>.tar.gz (120 kB)
  Preparing metadata (setup.py) ... done
Requirement already satisfied: imageio in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from gym[mujoco,robotics]) (2.10.4)
Requirement already satisfied: glfw>=1.4.0 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from mujoco-py<2.0,>=1.50->gym[mujoco,robotics]) (2.4.0)
Requirement already satisfied: Cython>=0.27.2 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from mujoco-py<2.0,>=1.50->gym[mujoco,robotics]) (0.29.24)
Requirement already satisfied: cffi>=1.10 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from mujoco-py<2.0,>=1.50->gym[mujoco,robotics]) (1.15.0)
Requirement already satisfied: lockfile>=0.12.2 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from mujoco-py<2.0,>=1.50->gym[mujoco,robotics]) (0.12.2)
Requirement already satisfied: pillow>=8.3.2 in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from imageio->gym[mujoco,robotics]) (8.4.0)
Requirement already satisfied: future in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from pyglet<=1.5.0,>=1.4.0->gym[mujoco,robotics]) (0.18.2)
Requirement already satisfied: pycparser in /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages (from cffi>=1.10->mujoco-py<2.0,>=1.50->gym[mujoco,robotics]) (2.21)
Building wheels for collected packages: mujoco-py
  Building wheel for mujoco-py (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /home/user/anaconda3/envs/spinningup/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py'"'"'; __file__='"'"'/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-4jr5y9f8
       cwd: /tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/
  Complete output (54 lines):
  running bdist_wheel
  running build

  You appear to be missing MuJoCo.  We expected to find the file here: /home/user/.mujoco/mjpro150

  This package only provides python bindings, the library must be installed separately.

  Please follow the instructions on the README to install MuJoCo

      https://github.com/openai/mujoco-py#install-mujoco

  Which can be downloaded from the website

      https://www.roboti.us/index.html

  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py", line 44, in <module>
      tests_require=read_requirements_file('requirements.dev.txt'),
    File "/home/user/.local/lib/python3.6/site-packages/setuptools/__init__.py", line 145, in setup
      return distutils.core.setup(**attrs)
    File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/dist.py", line 955, in run_commands
      self.run_command(cmd)
    File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/dist.py", line 974, in run_command
      cmd_obj.run()
    File "/home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/wheel/bdist_wheel.py", line 299, in run
      self.run_command('build')
    File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/dist.py", line 974, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py", line 28, in run
      import mujoco_py  # noqa: force build
    File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/mujoco_py/__init__.py", line 3, in <module>
      from mujoco_py.builder import cymj, ignore_mujoco_warnings, functions, MujocoException
    File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/mujoco_py/builder.py", line 502, in <module>
      mjpro_path, key_path = discover_mujoco()
    File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/mujoco_py/utils.py", line 93, in discover_mujoco
      raise Exception(message)
  Exception:
  You appear to be missing MuJoCo.  We expected to find the file here: /home/user/.mujoco/mjpro150

  This package only provides python bindings, the library must be installed separately.

  Please follow the instructions on the README to install MuJoCo

      https://github.com/openai/mujoco-py#install-mujoco

  Which can be downloaded from the website

      https://www.roboti.us/index.html

  ----------------------------------------
  ERROR: Failed building wheel for mujoco-py
  Running setup.py clean for mujoco-py
Failed to build mujoco-py
Installing collected packages: mujoco-py
  Attempting uninstall: mujoco-py
    Found existing installation: mujoco-py <IP_ADDRESS>
    Uninstalling mujoco-py-<IP_ADDRESS>:
      Successfully uninstalled mujoco-py-<IP_ADDRESS>
    Running setup.py install for mujoco-py ... error
    ERROR: Command errored out with exit status 1:
     command: /home/user/anaconda3/envs/spinningup/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py'"'"'; __file__='"'"'/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-7uj0wk9y/install-record.txt --single-version-externally-managed --compile --install-headers /home/user/anaconda3/envs/spinningup/include/python3.6m/mujoco-py
         cwd: /tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/
    Complete output (56 lines):
    running install
    running build

    You appear to be missing MuJoCo.  We expected to find the file here: /home/user/.mujoco/mjpro150

    This package only provides python bindings, the library must be installed separately.

    Please follow the instructions on the README to install MuJoCo

        https://github.com/openai/mujoco-py#install-mujoco

    Which can be downloaded from the website

        https://www.roboti.us/index.html

    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py", line 44, in <module>
        tests_require=read_requirements_file('requirements.dev.txt'),
      File "/home/user/.local/lib/python3.6/site-packages/setuptools/__init__.py", line 145, in setup
        return distutils.core.setup(**attrs)
      File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/dist.py", line 955, in run_commands
        self.run_command(cmd)
      File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/dist.py", line 974, in run_command
        cmd_obj.run()
      File "/home/user/.local/lib/python3.6/site-packages/setuptools/command/install.py", line 61, in run
        return orig.install.run(self)
      File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/command/install.py", line 545, in run
        self.run_command('build')
      File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/home/user/anaconda3/envs/spinningup/lib/python3.6/distutils/dist.py", line 974, in run_command
        cmd_obj.run()
      File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py", line 28, in run
        import mujoco_py  # noqa: force build
      File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/mujoco_py/__init__.py", line 3, in <module>
        from mujoco_py.builder import cymj, ignore_mujoco_warnings, functions, MujocoException
      File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/mujoco_py/builder.py", line 502, in <module>
        mjpro_path, key_path = discover_mujoco()
      File "/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/mujoco_py/utils.py", line 93, in discover_mujoco
        raise Exception(message)
    Exception:
    You appear to be missing MuJoCo.  We expected to find the file here: /home/user/.mujoco/mjpro150

    This package only provides python bindings, the library must be installed separately.

    Please follow the instructions on the README to install MuJoCo

        https://github.com/openai/mujoco-py#install-mujoco

    Which can be downloaded from the website

        https://www.roboti.us/index.html

    ----------------------------------------
  Rolling back uninstall of mujoco-py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py-<IP_ADDRESS>.dist-info/
   from /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/~ujoco_py-<IP_ADDRESS>.dist-info
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/__init__.py
   from /tmp/pip-uninstall-rdeaw6f9/__init__.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/__pycache__/
   from /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/~_pycache__
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/builder.py
   from /tmp/pip-uninstall-rdeaw6f9/builder.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/cymj.c
   from /tmp/pip-uninstall-rdeaw6f9/cymj.c
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/cymj.pyx
   from /tmp/pip-uninstall-rdeaw6f9/cymj.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/generated/__init__.py
   from /tmp/pip-uninstall-rdeaw6f9/generated/__init__.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/generated/__pycache__/
   from /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/generated/~_pycache__
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/generated/const.py
   from /tmp/pip-uninstall-rdeaw6f9/generated/const.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/generated/cymj_<IP_ADDRESS>_36_linuxgpuextensionbuilder_36.so
   from /tmp/pip-uninstall-rdeaw6f9/generated/cymj_<IP_ADDRESS>_36_linuxgpuextensionbuilder_36.so
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/generated/wrappers.pxi
   from /tmp/pip-uninstall-rdeaw6f9/generated/wrappers.pxi
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/gl/
   from /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/~l
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjbatchrenderer.pyx
   from /tmp/pip-uninstall-rdeaw6f9/mjbatchrenderer.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjpid.pyx
   from /tmp/pip-uninstall-rdeaw6f9/mjpid.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjrendercontext.pyx
   from /tmp/pip-uninstall-rdeaw6f9/mjrendercontext.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjrenderpool.py
   from /tmp/pip-uninstall-rdeaw6f9/mjrenderpool.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjsim.pyx
   from /tmp/pip-uninstall-rdeaw6f9/mjsim.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjsimstate.pyx
   from /tmp/pip-uninstall-rdeaw6f9/mjsimstate.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/mjviewer.py
   from /tmp/pip-uninstall-rdeaw6f9/mjviewer.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/modder.py
   from /tmp/pip-uninstall-rdeaw6f9/modder.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/opengl_context.pyx
   from /tmp/pip-uninstall-rdeaw6f9/opengl_context.pyx
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/pxd/
   from /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/~xd
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/tests/
   from /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/~ests
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/utils.py
   from /tmp/pip-uninstall-rdeaw6f9/utils.py
  Moving to /home/user/anaconda3/envs/spinningup/lib/python3.6/site-packages/mujoco_py/version.py
   from /tmp/pip-uninstall-rdeaw6f9/version.py
ERROR: Command errored out with exit status 1: /home/user/anaconda3/envs/spinningup/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py'"'"'; __file__='"'"'/tmp/pip-install-jvze_h7i/mujoco-py_35a193b81cbb4e02a16072099553e4b4/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-7uj0wk9y/install-record.txt --single-version-externally-managed --compile --install-headers /home/user/anaconda3/envs/spinningup/include/python3.6m/mujoco-py Check the logs for full command output.

I got the same error.

The issue #295  is related to this one.
You do not have to install gym[mujoco, robotics] .

Thanks a lot!


Various fixes

Fix issue with Overlay network plugin and some other problems with stopping the infrastructure.

Not quite ready to merge yet


dMarket Smart Contract

dMarket Smart Contract
Dynamic Market Smart Contract allows users to trade tokens with different pairs other than SWAP.HIVE (the original market contract). A global pair means every token is allowed to be traded for it, only Hive Engine team can create a global pair. There are two global pairs allowed by default (SWAP.BTC & BEE). More pairs can be added by users for 100 BEE per token in a pair. It allows tribes and other projects to allow tokens to be traded for their native tokens (ex. DEC:PAL, ORB:PAL, BEE:PAL, SWAP.DOGE:PAL, etc..).
Transactions are similar to the original market contract with the addition of a "pair" parameter.
Example: To buy BEE tokens for SWAP.BTC
{
    "contractName": "dmarket",
    "contractAction": "buy",
    "contractPayload": {
        "symbol": "BEE",
        "pair": "SWAP.BTC",
        "quantity": "150",
        "price": "0.00000912"
    }
}

Complete Documentation: [pending]

only Hive Engine team can create a global pair

Why not let the witnesses decide? If a majority of top witnesses(11/20 right now) are voting for a particular token to be global, then it should be.
I say this because right now we are too dependent on the engine team and I'd like to slowly start transitioning away from that wherever possible.

Yes, this is absolutely better fit. not very familiar with the witness contract yet, will have a peak. Perhaps a proposal kind-of system requiring vote between top 20 witnesses.


Ensure pybind11 finds the right Python interpreter

A change in the recent CMake policies prevents Pybind11 to use the Python interpreter given in scikit-decide's configure args via -DPYTHON_EXECUTABLE=/path/to/python-interpreter.
See pybind11's issue #4785 for more information.
This PR enforces Pybind11 to conform to cmake's CMP0148 policy and to use the python interpreter given to scikit-decide's configuration command line. This is critical since otherwise scikit-decide's build script might not create the wheel for the intended python version.

It happens to be a wrong configuration on my side. The default behaviour of pybind11 works like a charm whereas the line which this PR adds only make things more complex and it requires more work to actually work.


Compression in MjpegServer cannot be set programmatically

MjpegServer has an internal parameter "m_compression" which sets the JPEG compression. This parameter cannot be set anywhere via a program. The only method is to make an HTTP request to set it, which is not really feasible.
This parameter should be exposed for setting.

The compression setting can be different for every client.  Are you saying we should provide a way to set the default compression setting if the client doesn't specify it in HTTP parameters?

Yes. Right now, the Server sets it to 80, but there is no way to change that in the program. The client has to send an HTTP GET with the compression. If you just fetch the stream (ie just browse to "http://localhost:1181" for example), you will get the default compression, and could easily swamp your network pipe.
Also, settting the compression using the HTTP parameter is pretty obscure. I only found it by reading the C code. Is it documented?

All of the dashboards do it, and it's the approach used for the Axis camera as well.  But, no, it's not documented anywhere.
I agree it's a good feature, but I'll need to think about how to expose it.  Currently properties exist only on sources, not on sinks, so it means adding a whole infrastructure for sink properties.  Of course this may be useful in other ways though too.

Fixed in wpilibsuite/allwpilib#1229.


Blufi error on release v4.1 with git pull --rec update (IDFGH-4302)

Blufi is completed break in latest release v4.1 with updates pulled in git pull --rec.
Its simple hangs and doesnt reply to any blufi command.
Very eratic error in a stable release version.
Urgent feedback needed.

Could you describe in detail what kind of problems you have encountered.

same as latest report, some parts update in ble but the error on past ble problem on packet as of IDFGH-3893, so, the problem still happen.
I will close this as it is redundant.

as reported in sep 24,
@hb-kaertech @filzek @jimwhitfield
If it is urgent, can you make such modification temporarily? We are doing further analysis.
components/bt/host/bluedroid/btc/profile/esp/blufi/blufi_prf.c
esp_ble_get_cur_sendable_packets_num(blufi_env.conn_id) -> esp_ble_get_sendable_packets_num()
this fix temporary the problem.


DEV2-4344 add workspace tracing

Not sure I agree. It is easier for me to follow a trace of events


Properties with unsupported types marked with Ignore cause the parsing to fail.

Here's a sample:
@interface GenericObjectModel : JSONModel
@property (nonatomic, strong) NSString<Optional>* id;
@property (nonatomic, strong) NSString<Optional>* name;
@property (nonatomic, strong) NSString<Optional>* type;
@property (nonatomic, strong) Class<Ignore> classType;
@end

I would expect the classType to be ignored by JSONModel since it is marked with Ignore. However, instead the parsing fails because of the unsupported type.
The ignore should have precedence over the unsupported type check so complex models can be used in a compatible way.
Sample:
{
"name": "Joystick",
"id": "joystick_signaler",
"_class": "SomeClass"
}

Thanks - this does look like a bug. Will investigate at some point.

yes, that makes sense. @billinghamj I'll have a look

@J-Rojas making primitive types and structs Optional or Ignored must be done by overriding +(BOOL)propertyIsIgnored:(NSString *)propertyName and ...propertyIsOptional... Protocols can be used only on class properties with JSONModel. The runtime strips out the protocols defined on a struct so we can't even get this information.

@J-Rojas re: precedence - if you use Ignored with a class property (let's say a UIImage) the code works fine


fix: Add missing packages for local docker builds

After CGO go build flag is introduced for core services built, several Dockerfiles of core-services are missing some base build packages; hence this fix.
Fixes: #3901
Signed-off-by: Jim Wang<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x ] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

One can just try any make docker targets that are using CGO , like make docker_core_metadata on the console command line.  It should be built without any build error.
New Dependency Instructions (If applicable)

For what it's worth, what's been done so far fixes the build.

Codecov Report

Merging #3965 (df8d8e1) into main (e06225a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head df8d8e1 differs from pull request most recent head 2fd84e1. Consider uploading reports for the commit 2fd84e1 to get more accurate results

@@           Coverage Diff           @@
##             main    #3965   +/-   ##
=======================================
  Coverage   47.13%   47.13%
=======================================
  Files         113      113
  Lines        9820     9820
=======================================
  Hits         4629     4629
  Misses       4804     4804
  Partials      387      387

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 e06225a...2fd84e1. Read the comment docs.


policyautomation delete modal check

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

/lgtm


About the problem which I don't know how to  classify

Hi Asha, I'm sorry to bother you! I try the command: " python train.py --name today1 --dataroot ./datasets/train --n_domains 2 --niter 10 --niter_decay 10" But i have the following problem:
File "train.py", line 38, in
visualizer.plot_current_errors(epoch, float(epoch_iter)/dataset_size, opt, errors)
File "/home/chujian/ToDayGAN-master/util/visualizer.py", line 109, in plot_current_errors
win=self.display_id)
File "/home/chujian/anaconda3/lib/python3.6/site-packages/visdom/init.py", line 335, in wrapped_f
return f(*args, **kwargs)
File "/home/chujian/anaconda3/lib/python3.6/site-packages/visdom/init.py", line 1331, in line
assert Y.ndim == 1 or Y.ndim == 2, 'Y should have 1 or 2 dim'
AssertionError: Y should have 1 or 2 dim

I inherited the Visdom code from CycleGAN, which the project originally branched from a while ago.
But I never actually used it myself.
In fact, if you run that command you quoted, it should not use Visdom whatsoever, so unless you are setting --display_id yourself, this should not be a problem.
If you want visualization, then I have no idea what to debug since it's code I've never looked at.
Sorry about that mate.


Use addEventListener with proper delegates for any events rather than inline javascript/setAttribute("on*")

Fixes sites with more strict security requirements.

Thank you very much for this!


*: add Makefile and adjust test folder

Add Makefile to do build, format, test more easily.


[AIRFLOW-2389] Create a pinot db api hook

Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2389
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
create a dbapi hook to query pinot(https://github.com/linkedin/pinot)

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
yes

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3274   +/-   ##
=======================================
  Coverage   75.88%   75.88%
=======================================
  Files         197      197
  Lines       14699    14699
=======================================
  Hits        11155    11155
  Misses       3544     3544

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 3952e05...0f2e2ce. Read the comment docs.


Inline camera on some iPhone (6s & 5) picture is tilted

Hi,
On some of the iphone 6s and iphone 5, using the Inline Camera (even on Demo app) take a selfi landscape mode (home button on right side) is producing a tilted picture.
How to resolve this? Any help please.

adding to Ganesh comment above, when taking the photos in selfi landscape mode (home button on right side), the image is flipped upside down.  When we do the same selfi landscape but with home button on left hand side, no issue with image.

Fixed in develop. Thanks!!!


[8.x] Improvement in the normalize() method.

This isn't needed. Things are fine as they are. You're only wrapping native functions with an external dependency.

I agree with Dries. This just makes the code slightly slower for no benefit.


Asking help for METU-VisTIR benchmark and source code.

This is a fascinating piece of work. I am very interested in the data augmentation you mentioned. Could you please share the dataset link and code link?

We sincerely appreciate your interest in our work. After final revisions and organization, we aim to release the refined code and dataset in a couple of months.
Best


Replace SSH polling implementation

Currently, the ssh polling is done locally per instance of the dispatch-service. This leads to the service having a state that is lost if the service crashes (caused by bugs) or restarts ( caused by updates). This leads simulation runs to stop updating in their last recorded state.
Another problem that is caused by this approach is that the service makes many requests to the hpc cluster at the exact same time due to the cron jobs syncing up.
Both these issues can be solved by using a queue that is shared between the dispatch-service instances.  NestJS provides a wrapper for queues that would simplify much of the set up. https://docs.nestjs.com/techniques/queues
The kubernetes cluster has a redis-cluster already available.
A potential starting point would be to have the dispatch-api add new simulationRuns to a queue. The service can then consume these. This would solve many of the reliability issues we have been having. The dispatch service would then be able to add a repeating job to a monitoring queue. Finally, on completion, a third queue would handle the processing of the results and logs.
@gmarupilla  Would you be interested in getting started on this?

Yes, I'll work on this.

Done


STYLE: ImageHelper now doing '+=' and using C++11 std::integral_constant

Replaced old itk::Concept::Detail::UniqueType_bool within ImageHelper class definition by C++11 std::integral_constant<bool, B>, from <type_traits>.
Replaced expressions like 'x = x + a' by 'x += a', which might possibly be slightly faster.

@hjmjohnson The ITK.macOS error appears unrelated to my commit:

/Users/vsts/agent/2.142.1/work/1/s/Modules/Core/Common/include/itkImageHelper.h:52:27: error: variable has incomplete type 'class ITK_TEMPLATE_EXPORT'

https://dev.azure.com/itkrobotmacos/ITK.macOS/_build/results?buildId=430
What should be done about it?

@hjmjohnson wrote:

I think you need to include itkMacro.h in the file for inlcusion of ITK_TEMPLATE_EXPORT.

Ok, thanks, sounds reasonable. But then, do you know why it did actually compile on ITK.Linux and ITK.Windows?

@N-Dekker I can only guess that it is related to conditional header inclusion sequence for the other files.

@hjmjohnson Thanks, I will amend the commit.

@hjmjohnson Just added the one #include directive that you suggested, and amended my commit locally. Now I don't know how to get it onto GitHub anymore! I tried git review-push, of course, but it failed:
cedekker@2-lkeb-17-nde1 MINGW64 /f/X/Src/ITK (Small-improvements-ImageHelper)
$ git review-push
Pushing to origin
error: failed to push some refs to 'https://github.com/N-Dekker/ITK.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
To https://github.com/N-Dekker/ITK.git
!       HEAD:refs/heads/Small-improvements-ImageHelper  [rejected] (non-fast-forward)
Done

Do you have a suggestion?


Delete Operation in PostgreSQL is not Synced

(Apologies for the second issue in such a short time).
The delete operation doesn't work as expected; it doesn't sync with MeiliSearch. I'm using the debezium/postgres Docker image, which comes with the wal_level configured and wal2json installed.
I'm not seeing any logs or errors when performing delete operations.
On the wal2json GitHub page, it mentions:

wal2json is an output plugin for logical decoding. It means that the plugin has access to tuples produced by INSERT and UPDATE. Also, UPDATE/DELETE old row versions can be accessed depending on the configured replica identity.

I'm unsure about what they mean by "old row versions" and how to configure it to work with meilisync, if it's even possible.
By the way debzeium/postgres versions 12 and 14 have no other problems, but with version 15, meilisync throws an error mentioning something like "can't locate pg_wal," if I remember correctly.

I have the same problem, is anyone looking at this issue?

I also have this issue.

So I am

Going back to:

On the wal2json GitHub page, it mentions:

wal2json is an output plugin for logical decoding. It means that the plugin has access to tuples produced by INSERT and UPDATE. Also, UPDATE/DELETE old row versions can be accessed depending on the configured replica identity.

Configuring replica identity to FULL for a table doesn't fix this issue.


Restructure backend

Change hierarchical structure of backend

[ ] Members creating clubs (No longer 2 separate entities)
[ ] Clubs being audited by Administrator
[ ] Database change

More to come...

Updated GORM Library to v2

Supports customized joinTables with a many to many relation
The library is structured differently than v1 (additional changes need to be made)


[palmdb4] db, sOTU blacklist

Add a reason column, ENUM?

Merged to: https://github.com/serratus-bio/open-virome/issues/154


Remove TODO comment in EC code. Resolves #14396

Removes a comment only, no code changes.
Fixes #14396

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merged to master, thanks for this.


Questions on 5 features

This is awesome work here, for QA type solution.
I got one question on input of 5 features, especially for TF.
tf = [0.1 * math.log(wikiwords.N * wikiwords.freq(w.lower()) + 10) for w in d_dict['words']]
what's basic idea for this feature input to doc_rnn ??  Theory is ??

The intuition behind TF feature is to let the model ignore unimportant words (usually some frequent stop words such as "the", "a").
As to the formula you mention, it is somehow arbitrary. wikiwords.N * wikiwords.freq(w.lower() is the absolute frequency of word w, 0.1 * math.log is to avoid extremely large numbers, and + 10 is just to make sure math.log do not throw exceptions.
Other formulas might work as well.
Thank you.


feat/Added Blockly Plugins

Plugins Added:

Zoom To Fit: Place blocks, click button, all blocks should take up the screen now.
Workspace Search: Ctrl + F will highlight blocks with those letters, will also pan the camera to those blocks.
Dark Mode: Will enable dark mode for the website, Blockly & CodeMirror.
Fixed Edges: Blocks will remain in the visible area, being pushed inside if placed outside the border.
Content Highlight: Focuses on blocks in the workspace by highlighting the area of blocks.

(Can remove any if unnecessary).
More plugins to look into, mainly for autocompletion:

Shadow Block Converter (Can be used for autocomplete - data, atoms)
Lexical Variables (Can be used for autocomplete - data, atoms)

Added a little change, but other than that LGTM


Weird edge condition with uneval forms

This is a strange one. If you have a uneval form with a newline in the middle of it, then trying to insert a value via a zipper produces a strange result:
(-> "#_(b c)" p/parse-string z/edn z/down z/down (z/insert-left 'a) z/root)
=> <forms: #_[:tag :list][:format-string "(%s)"][:wrap-length 2][:seq-fn #<seq$list_node$fn__14876 rewrite_clj.node.seq$list_node$fn__14876@a798224>][:children (<token: a> <whitespace: " "> <token: b> <whitespace: " "> <token: c>)]>

Note that an eval form works fine:
(-> "#=(b c)" p/parse-string z/edn z/down z/down (z/insert-left 'a) z/root)
=> <forms: #=(a b c)>

My guess is that there's some typo or small error in the uneval form zipper setup that's causing this problem.

Oddly there are two uneval-forms defined, one in rewrite-clj.node.reader-macro, and the other in rewrite-clj.node.uneval. Is one of those a hangover from a refactor?

Fix deployed in
[rewrite-clj "0.4.9"]


Port LR Schedulers

What this does
Port Cosine and Inverse Sqrt LR schedulers from diffusers and transformers libraries respectively.
(Also loosely related to Octo PR #209; Octo uses inverse_sqrt scheduler.)
How it was tested
Recorded values from the above libraries' functions and tested against them.

This change is

poetry lock out of  sync here, lazy to manually resolve conflicts lol so will reopen on a new branch


More sanity checks for compactor

Codecov Report

Merging #714 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #714      +/-   ##
============================================
+ Coverage     65.48%   65.48%   +<.01%
- Complexity     3745     3747       +2
============================================
  Files           327      327
  Lines         25029    25033       +4
  Branches       3140     3141       +1
============================================
+ Hits          16389    16392       +3
- Misses         7757     7759       +2
+ Partials        883      882       -1

Impacted Files
Coverage Δ
Complexity Δ

...ava/com.github.ambry.store/BlobStoreCompactor.java
93.36% <100%> (+0.06%)
118 <0> (+2)
:arrow_up:

.../main/java/com.github.ambry.store/HardDeleter.java
80% <0%> (-1.94%)
41% <0%> (-1%)

...ava/com.github.ambry.router/NonBlockingRouter.java
81.66% <0%> (-0.84%)
34% <0%> (ø)

...ain/java/com.github.ambry.router/PutOperation.java
89.9% <0%> (-0.23%)
69% <0%> (-1%)

.../src/main/java/com.github.ambry.store/Journal.java
91.37% <0%> (+1.72%)
20% <0%> (+1%)
:arrow_up:

...github.ambry.rest/AsyncRequestResponseHandler.java
90.81% <0%> (+2.29%)
23% <0%> (ø)
:arrow_down:

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 9ac8437...76064c5. Read the comment docs.


Update web dependencies.

Notably upgrades past some major version boundaries.

jest-environment-jsdom-sixteen is to allow updating jsdom before create-react-app does (they're not sure about the change of default since it could break existing tests)
prettier 2.0 changed some default settings and removed the ones we had that became redundant
Found several libraries in package.json that aren't referenced in code. @tacigar Can you confirm the removals are OK? In particular, I found rc-slider and react-table in the CSS but not in JS so pretty sure they're not used but please confirm.

Doesn't update

date-io, pinned by material-ui/pickers
@types/jest, jest version not upgraded by create-react-app yet

Yes, no problem!
Thank you!

thanks a lot for taking the time on this. I know managing deps is usually
far trickier than numerical increments!


deleted useObjectState and useKeyValueState

I am certain this is not used anywhere

@Michiel87 can you confirm this is ok?


Code formatting & linting

This PR does some cleanups on the project code:

Adds the moveit clang-format config and formats all code according to it.
Tries to get closer to passing catkin_lint -W2. The remaining warnings are a result of the missing run dependencies for the rrbot demo, which we cannot easily get rid off without turning that into a seperate package.
Adds checks for both to the CI.

Are there any opinions on this? As these are mainly cosmetic changes i would go ahead and merge them soon otherwise.
Closes #39.

The force push fixed a problem i had in the ci config. It now uses two jobs:

One builds the project
One to run clang-format + catkin_lint

If anybody knows of a better way to do this, feel free to adjust this. For reference (and to save a few clicks), this is the ci output for catkin_lint warnings:
Running catkin_lint
catkin_lint /root/ros_ws
ros_control_boilerplate: rrbot_control/launch/rrbot_hardware.launch(10): warning: launch configuration needs run_depend on 'xacro'
ros_control_boilerplate: rrbot_control/launch/rrbot_hardware.launch(26): warning: launch configuration needs run_depend on 'robot_state_publisher'
ros_control_boilerplate: rrbot_control/launch/rrbot_simulation.launch(10): warning: launch configuration needs run_depend on 'xacro'
ros_control_boilerplate: rrbot_control/launch/rrbot_simulation.launch(26): warning: launch configuration needs run_depend on 'robot_state_publisher'
ros_control_boilerplate: rrbot_control/launch/rrbot_visualize.launch(5): warning: launch configuration needs run_depend on 'xacro'
ros_control_boilerplate: rrbot_control/launch/rrbot_visualize.launch(8): warning: launch configuration needs run_depend on 'rviz'
catkin_lint: checked 1 packages and found 6 problems
No catkin_lint issues reported.


Move $Server from GlobalVariables to Init plugin

This makes more sense to define in the connect plugin, and keep GlobalSettings as configuration of vCheck core only.
Will require modifying vCheck.ps1 (variable check part), globalVariables.ps1 (remove setting), and 00 Connection Plugin for vCenter.ps1 (Add setting).
This may cause a few Issues being logged as people upgrade vCheck.

This is a good idea. I don't have it on front of me at the moment, but I seem to recall that this is also printed at the top of the reports. If so, will the style.ps1 files also need changing?

Yeah it is in the header, but as long as we keep the $Server variable name we should be fine.

I'm just thinking though, if the objective is to eliminate dependencies between vCheck core and the plugins, this change won't really achieve all that much if the style.ps1 files still refer to that variable.
In my own personal use-case (which I admit is probably unusual), I don't use any of the provided plugins. Because I run essentially the same tests against multiple environments, I actually use the existing $server variable more as a "report title" so I can see which environment a report is for.

hmmmm good point... perhaps having an actual report title setting in global variables might be an idea.

That works for me. Then like you suggested, move $server into the connection plugin and display the new title variable on the report.
If you wanted to make sure that anyone upgrading didn't lose the server name from the report, you could always check to see if the new title variable is null in the connection plugin - if so, set it to $server. Or just make the new report title compulsory

I think no matter how we handle it it will break something for someone, but at least it is a simple fix (and really the worst it should do is just not display a heading).
We really need a more robust update mechanism to get around these issues... e.g. having vCheck update itself, and have a pre/post upgrade script to handle things like adding the title variable to globalvariables. Of course, this would be made a lot simpler with updated settings handling that does not rely on modifying plugin files... hmmmmm...

It has been a while since I last checked the vCheck code updates. But this one stands out because it breaks one of the most valuable features: the use of job files. And I felt like I needed to address this. By moving the vCenter server settings to the connection plugin means that I can no longer have a global variable that is set on a per job basis.
Let me give an example.
Right now I'm able to create 2 jobs targeted at different vCenter instances and using a different set of plugins like this:

Create a file called MyJob.xml and enter the location of the GlobalVariables file which can be named as MyJob_GlobalVariables.ps1. And in that ps1 file I can configure my vCenter instance of choice.
With minimal effort I can target another vCenter instance by creating another set of xml and ps1 files and using a different vCenter instance in the GlobalVariables file.

With the new setup I would need to create a different vCheck directory or copy the Init plugin a few times to target another server. And that seems less efficient. Or is there another way?

Well, the idea was to generalise vCheck so that only variables that relate to the generation of the report are in GlobalVariables. This means vCheck can be used for any reporting task, not specifically vSphere.
Of course, the second part of this change hasn't happened yet, which is the complete rewrite of the settings handling to get rid of the GlobalVariables file altogether... Issue #361 touches on this.


Implement the functionality of UpdateProfilePendingOwner

This PR implements the update_profile_pending_owner function.
The function updates the "pending owner" of a specific profile. The "pending owner" is someone who is set to become the new owner of the profile.
Fixes #9

@Akashneelesh I am done with the task, please take a look.

Hey @VictoriaAde , could you please resolve the merge conflicts.

Hey @VictoriaAde , could you please resolve the merge conflicts.

On it! I'm currently encountering crazy bugs, and fixing them atm.

Hi @Akashneelesh, I have fixed the conflicts and used the _is_owner_of_profile in my function to check for ownership.

good

@VictoriaAde The reward has been sent out. LFG


Week 18 - Group Review Ticket

GROUP VIEW AND FE HACKS
LYDIA:
OOP Hacks
Collegeboard Video Grades
ALEXA:
OOP Hacks
Collegeboard Video Grades
AVA:
OOP Hacks
Collegeboard Video Grades
SRI:
OOP Hacks
Collegeboard Video Grades

This is an amazing review ticket!
I looked at dob and classOf by Lydia and it is fantastic.  I saw she is missing part 2 which is personal blog, also Alexa, Sri did not have it either.  I found it in Ava's with swim, cheer, burpee.  That was hard to find and this part was supposed to be individual.
I looked at Sri's review ticket and it was amazing with check boxes on criteria.  This is a great illustration of how this should be done and setting up the table is probably not that hard after the first one.  Amazing!
Overall, this is one of my favorites!!!

LYDIA:
CPT Grading: +1
OOP Hacks: +1
Front End: +1
Total:3
ALEXA:
CPT Grading: +1
OOP Hacks: +1
Front End: +1
Total:3
AVA:
CPT Grading: +1
OOP Hacks: +1
Front End: +1
Total:3
SRI:
CPT Grading: +1
OOP Hacks: +1
Front End: +1
Total:3


mdl-data-table--selectable  doesnt show checkboxes with Angular

effect table with mdl-data-table--selectable  and angular binded list

Works with Chrome-
not work with IE11 and Mozilla

Please use StackOverflow for support. The core team can't support every technology combination that may be used.

it's not a question of support- It's a question of Fitting together. Angular does (like any spa Framework) a kind of late binding dom Manipulation. There must be a feature to update UI Rendering, regarding the JavaScript manipulated dom from MDL

It's a question of Fitting together

You can get semantic with the wording all you want, at the end of the day it is support. It is using MDL with technology that we don't directly support. StackOverflow already has some answers guiding people as to how to handle these situations, which is another reason to go there. You can see other questions that are related much more easily than searching out issue tracker. Then if you still don't find the help you need, you can ask a question there and people who understand the full stack you are using can help out.

I had the same problem and I solved it by calling this function componentHandler.upgradeAllRegistered();

+1 It will be great if this could be fixed.

I had the same problem. I finally resulted to using ng-repeat to include the checkboxes myself and use jQuery to wire up the logic of selecting all checkboxes when the master is selected and added the corresponding mdl classes.


Delayed tooltips stops the charm hover selection in Fiery Warpath

When delayed tooltips is turned on, you dont get this show

Should be fixed now, please reopen if not!


OCM-11364 | fix: Regression, HCP nodepool creation validation used for classic

Fix for issue customer faced after 1.2.45 released
Logic which checked # of min replicas for newly created machinepools was applied to both HCP and classic- though there is a difference between what is supported (when autoscaling is enabled)
for HCP, >0 min replicas
for classic, >=0 min replicas
This fix adds different logic paths in the validation + fixes unit tests

/lgtm
/approve


Setting "cmake.exportCompileCommandsFile": true does not work with CMake Presets

Brief Issue Summary
Setting "cmake.exportCompileCommandsFile": true does not work with CMake Presets.
Expected:

Set  "cmake.exportCompileCommandsFile": true
-DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=ON is added to the CMake configure call even when on the presets path

Platform and Versions

Operating System: Ubuntu
CMake Version: 3.20.2
VSCode Version: 1.55.0
CMake Tools Extension Version: 1.7.1
Compiler/Toolchain: GCC 9.3.0

Thank you for opening this report. You can specify this in the preset as well. I just verified that it works.
"cacheVariables": {
"CMAKE_EXPORT_COMPILE_COMMANDS": "ON"
}
@xisui-MSFT, I don't see any reason why presets wouldn't pick up from regular settings but I am not sure, please confirm if this behavior is by design or we should fix something in CMake Tools. Is the user supposed to define the above when wanting compile_commands.json or the usual setting we had should have effect even with presets on?

This is by design. All settings in settings.json that can be achieved via presets are ignored when using presets.

@andreeis Thanks for your reply.
@xisui-MSFT The reason I would like to see this picked up from the settings is, that I want to be able to set this globally in my user settings. Otherwise I would have to write an awful amount of cmake user presets, just to get the compile commands exported.

You can write a base preset like:
{
"name": "base",
"cacheVariables": {
"CMAKE_EXPORT_COMPILE_COMMANDS": "ON"
},
"hidden": true
}
And then in all presets you need this:
{
"name": "name",
"inherits": [
"base",
...
],
...
}

Also, each entry in cacheVariables is inherited independently. So you can write more cache vars in your base preset, and then overwrite any entry you need independently.

@xisui-MSFT While this would be possible, it would still need a complete rewrite of all presets as far as I understand.
Suppose this is my CMakePresets.json:
{
    "version": 2,
    "cmakeMinimumRequired": {
        "major": 3,
        "minor": 20,
        "patch": 0
    },
    "configurePresets": [
        {
            "name": "preset_a",
            "generator": "Ninja Multi-Config",
            "binaryDir": "${sourceDir}/build"
        },
        {
            "name": "preset_b",
            "inherits": "preset_a",
            "cacheVariables": {
                "CACHE_VARIABLE_B": "ON"
            }
        },
        {
            "name": "preset_c",
            "inherits": "preset_a",
            "cacheVariables": {
                "CACHE_VARIABLE_C": "ON"
            }
        }
    ],
    "buildPresets": [
        {
            "name": "preset_a_release",
            "configurePreset": "preset_a",
            "configuration": "Release"
        },
        {
            "name": "preset_a_debug",
            "configurePreset": "preset_a",
            "configuration": "Debug"
        },
        {
            "name": "preset_b_release",
            "configurePreset": "preset_b",
            "configuration": "Release"
        },
        {
            "name": "preset_b_debug",
            "configurePreset": "preset_b",
            "configuration": "Debug"
        },
        {
            "name": "preset_c_release",
            "configurePreset": "preset_c",
            "configuration": "Release"
        },
        {
            "name": "preset_c_debug",
            "configurePreset": "preset_c",
            "configuration": "Debug"
        }
    ],
    "testPresets": [
        {
            "name": "preset_a_debug_testing",
            "configurePreset": "preset_a"
        },
        {
            "name": "preset_b_debug_testing",
            "configurePreset": "preset_b"
        },
        {
            "name": "preset_c_debug_testing",
            "configurePreset": "preset_c"
        }
    ]
}

My CMakeUserPresets.json would look something like this:
{
    "version": 2,
    "cmakeMinimumRequired": {
        "major": 3,
        "minor": 20,
        "patch": 0
    },
    "configurePresets": [
        {
            "name": "base",
            "cacheVariables": {
                "CMAKE_EXPORT_COMPILE_COMMANDS": "ON"
            },
            "hidden": true
        },
        {
            "name": "preset_a_export",
            "inherits": [
                "base",
                "preset_a"
            ]
        },
        {
            "name": "preset_b_export",
            "inherits": [
                "base",
                "preset_b"
            ]
        },
        {
            "name": "preset_c_export",
            "inherits": [
                "base",
                "preset_c"
            ]
        }
    ],
    "buildPresets": [
        {
            "name": "preset_a_export_release",
            "configurePreset": "preset_a_export",
            "configuration": "Release"
        },
        {
            "name": "preset_a_export_debug",
            "configurePreset": "preset_a_export",
            "configuration": "Debug"
        },
        {
            "name": "preset_b_export_release",
            "configurePreset": "preset_b_export",
            "configuration": "Release"
        },
        {
            "name": "preset_b_export_debug",
            "configurePreset": "preset_b_export",
            "configuration": "Debug"
        },
        {
            "name": "preset_c_export_release",
            "configurePreset": "preset_c_export",
            "configuration": "Release"
        },
        {
            "name": "preset_c_export_debug",
            "configurePreset": "preset_c_export",
            "configuration": "Debug"
        }
    ],
    "testPresets": [
        {
            "name": "preset_a_export_debug_testing",
            "configurePreset": "preset_a_export"
        },
        {
            "name": "preset_b_export_debug_testing",
            "configurePreset": "preset_b_export"
        },
        {
            "name": "preset_c_export_debug_testing",
            "configurePreset": "preset_c_export"
        }
    ]
}

Which in extension brings me to https://github.com/microsoft/vscode-cmake-tools/issues/1836
Sorry for the wall of text.

As this setting relates more to the IDE and configures IDE features (eg compile commands being available to the IDE) I would think this should be controlled by the IDE's cmake.exportCompileCommandsFile setting. The setting would not be required for out-of IDE builds and as such should not be in the configurePresets. It also would avoid having to edit existing project's build settings just to get an IDE feature working.

I had the same issue last week. I am sad that the provided solution was not that intuitive... Using clangd or intellisense is an IDE related setting. Thus, I would expect those kind of settings that are not "build" related but rather "tooling" related, to pass through. On the other hand, I understand the hassle. Can we at least remove the "cmake.exportCompileCommandsFile" option if a cmake preset is detected? It is the default way to do cmake nowadays and it took me two days to understand what was going on. I think that @globberwops @mpusz and @bobbrow who reported this in the past will agree with the conditional removal of this setting

@Jason5480 From what I understand, extension settings can't be defined under a when clause, however, we could at the very least make a description change to cmake.exportCopmileCommandsFile setting to make sure that it's clear when it will and when it won't be used.
I'm not sure when we'll get to this, but since it's a simple request, I'll mark it as stale-exempt so that it doesn't get marked as stale again.

Thank you very much @gcampbell-msft ! A detailed description and a warning sign and that will highlight the fact that this setting don't work if CMake is used with presets, would be very useful for ppl who want to use clangd and export compile_comands.json file! If there are any questions on how I use that setting inside a devcontainer you can check the public repo of the glaze json serialize library. Thank you again for your time


azure encryption JWT playback

Hello,
I couldn't be more confused on how to add a JWT token to test if my stream works, I have literally tried everything and it still wouldn't accept my data.
So I tried to create a test JWT from an online token generator ( this one : https://irrte.ch/jwt-js-decode/ )
here is the JWT decoded 🥇

{
    "alg": "HS256",
    "typ": "JWT"
}
{

    "iss": "https://sts.windows.net/********-***-****-****-******d/",
    "aud": "*******-*****-****-****-********",
    "iat":<PHONE_NUMBER>,
    "exp":<PHONE_NUMBER>,
    "nbf":<PHONE_NUMBER>
}

"iss" is my .net/tenantID
"aud" is my ad app id
i generate this with my verification key and gives me A VERIFIED token
I then add the same exact data in my content key policy in azure portal token configuration with the same verification key
i generate a new streaming policy with the created token , i take it to the  Azure Media Player online , i set in the AES textfield "bearer=myverifiedtoken"
i paste my generated widevine DRM URL over dash with the player open on Chrome i press play and i get an error
0x20500006
Please ANYONE CAN HELP ME ??
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b987eca1-780c-472f-8ef0-30655cca953c
Version Independent ID: 58bbb9d5-9801-4439-654c-8c4f4074b500
Content: Configure a content key authorization policy by using the Azure portal
Content Source: articles/media-services/previous/media-services-portal-configure-content-key-auth-policy.md
Service: media-services
Sub-service: rest-v2
GitHub Login: @Juliako
Microsoft Alias: juliako

@AnassHmida Thanks for the feedback! We are currently investigating and will update you shortly.

@AnassHmida what region are your media services being deployed to?

Hey ryan!
They are deployed on west europe

@RyanHill-MSFT  Hey ryan, is there a clear link on what are the necessary claims to make the request work ?

@AnassHmida the error code you're getting means License acquire failed. You can use Fiddler or your browsers debugger to inspect the http response body and determine what's causing the error. Furthermore, the Key Delivery service includes the reason as well. You can enable logging through the Media Services blade in the portal. Navigate to Diagnostics settings section on the AMS account and click Add diagnostic setting. Create a name, check KeyDeliveryReqeusts, and choose a destination. Results will be in JSON format.

@RyanHill-MSFT Hey Ryan, Thank you for your help,
I found out it that I had to convert my JWT verification key in BASE 64 and add it to the restriction tab content key policy parameters, and I had to sign my JWT in plaintext, now everything works perfectly, thank you for everything


fix(costmodels): show measurement units in the select options

Closes COST 769
Before

Now

Codecov Report

Merging #1758 (a305d39) into master (872f98f) will increase coverage by 0.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1758      +/-   ##
==========================================
+ Coverage   77.06%   77.34%   +0.27%
==========================================
  Files         295      295
  Lines        4665     4665
  Branches      896      897       +1
==========================================
+ Hits         3595     3608      +13
+ Misses        970      958      -12
+ Partials      100       99       -1

Impacted Files
Coverage Δ

.../pages/costModels/components/rateForm/rateForm.tsx
100.00% <ø> (ø)

...ges/costModels/components/rateForm/useRateForm.tsx
93.45% <0.00%> (+12.14%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @dlabrecq


artifactory-push vs. artifactory-publisher

Hi,
First of all, thanks for your work! I appreciate the nice CLI tool, but I'm wondering what the advantage is of your module over the original artifactory-publisher module?
It seems like this module doesn't add any extra features to the original module?
Thanks in advance!

Well, it seems as if @evil-shrike just recently got "inspired" by my little wrapper and decided to adapt it for his artifactory-publisher: https://github.com/CrocInc/artifactory-publisher/commit/ea6a8571f2bef992e7dbe04d1e89fc9bba881329
As his adaption is pretty much identical there is no need to use artifactory-push anymore.

@Voles @beevelop that's right. I added notes into README https://github.com/CrocInc/artifactory-publisher/commit/457e01ac96ea503ab2f8b97b84cb7eb715ef2cf3

@beevelop @evil-shrike thanks for the quick responses! However, I think a separate CLI module would be a nice separation of concerns.
artifactory-publisher could contain all artifactory logic, while artifactory-push (I suggest renaming to artifactory-publisher-cli) could contain all logic for a CLI tool.
WDYT?

@Voles Actually having the same project acting as a library (for other Node.js projects) and as a command line tool is not quite uncommon.
So IMHO the best way forward would be to deprecate my artifactory-push implementation with a clear reference to artifactory-publisher. As CLI and library are very tightly coupled and the CLI implementation itself is just about 70 LOC, I would not recommend splitting them up – unless you, @Voles, think about additional features the CLI should support?
@evil-shrike Thanks for the credit. I will update this project with an official deprecation notice with the next release.


Error status guidelines alignment (API v0.2.0 post MWC)

The guideline for errors has been changed today and now status is an integer instead of a string:
https://github.com/camaraproject/WorkingGroups/issues/143
https://github.com/camaraproject/WorkingGroups/pull/145
This change will be included in this PR.

PR merged


stopped working with new apple tv

I have 3 apple tv 4k in my house. I just replaced one of them with the new apple tv 4k that supports thread. ever since adding that apple tv, the pico remotes no longer respond in homekit. the programming shows up, they show up in homebridge as being pressed, if I configure the button and say test action it works. but pushing any buttons on any picos no longer works.

If you can see the Pico activity in Homebridge the plugin is working.  I'd recommend unplugging the AppleTV that is the active hub until another AppleTV takes over.  You could also try restarting Homebridge.
I don't have a the new AppleTV 4k, but I can't see how that would cause Homebridge to stop working properly.


UPDATE: preload yaml

After an incident that was causing a failed CI pipeline on one of our production applications. We noticed there were some missed performance opportunities in the architecture of this class.
Previously we were essentially loading all translation files per source edit. These changes essentially preloads them and then works through the edits from there.

Hi @leonp1991,
Thanks for this issue, we're looking at it!

Previously we were essentially loading all translation files per source edit.

Actually, there is a reason for this. After each loop, one of the YAML files is updated with the new source text of the source edit. So we load them all again to have the latest version (not optimal, I agree...).
The reason is that If many source edits are related to the same key, we need the latest version of the YAML files to be able to have the correct condition if value == source_edit['old_text'].
I'm sure we can find a way to improve this code and we're looking at it. But I have a question : why do you have so many source edits in your request? Is the .translation_io file present on your CI? You need it with the correct timestamp to be able to sync "only" the last source edits.

Hi @MichaelHoste as far as I could tell It looks like the code always updates the in memory hash before writing to file. meaning if we continually use the in memory hash we will always be writing the latest version of the file. I have not looked at the test suite though, so Im not sure if there a case thats not tested that needs to be added.
As for why we have needed so many edits. We are transition a product from containing static text, to text that is dynamic based on a users configuration of the product. This has lead to bulk key updates.
If it counts for anything we have been using this fork since this PR was opened.

Hi @MichaelHoste as far as I could tell It looks like the code always updates the in memory hash before writing to file. meaning if we continually use the in memory hash we will always be writing the latest version of the file. I have not looked at the test suite though, so Im not sure if there a case thats not tested that needs to be added.

I noticed this and that's why consecutive source_edits on the same key still work well with your pull request (this was tested in the specs!).
But there is this untested part that doesn't work well with the pull request: https://github.com/translation/rails/blob/master/lib/translation_io/client/sync_operation/apply_yaml_source_edits_step.rb#L39
It's a tricky part that allows you to create a source_edit for a key that comes from a gem directory (will_paginate, devise, etc.). And instead of editing the YAML file inside the gem directory (bad!), it creates a new key on your source YAML file to override the one of the gem (good!).
This part still works with your pull request but only if there is only one source edit for the same "gem key" on a single sync. But we need to still make it work for several source edits.
Tomorrow, I'll add a test for this very specific case and I'll try to refactor this service to make it work with your changes.
Thanks for your help!

Thanks for that information @MichaelHoste. I appreciate you taking the time to explain that. Great news on the refactor. Look forward to it.

Hi @leonp1991,
I added the missing specs here: https://github.com/translation/rails/commit/5e67aaea02d19f6090afd03ff369bd1734f83081#diff-a2df255f94ce27d98252df949170957bR122
And I refactored the service so that the YAML loading is only triggered when needed (after adding a new YAML file that override a gem YAML). Here is the new code: https://github.com/translation/rails/blob/master/lib/translation_io/client/sync_operation/apply_yaml_source_edits_step.rb
If these changes seem ok to you, I'll bump the Gem version tomorrow.
Thanks again for your help!

Looks good, happy to be moving back from the fork. Thank-you.

Looks good, happy to be moving back from the fork. Thank-you.

You should be able to move back from the fork, using Version 1.21.
Thank you for your help with this!


Event Creation Error

When creating an event in the event manager, if you type the parameters in random order, it won't let you create the event. However, if you enter the information from left to right you can create the event.

When information is entered in random order

When information is entered in correct order

events on the website are no longer a thing


The current version requires changes in libstd

Due changes to Rust, we have to revise the mutex interface. A pull request is already created (rust-lang/rust#77610) and we have to wait for the review.

I close this issue because rust-lang/rust#77610 is merged.


Move DEFAULT_PAGE_LIMIT to a config

Here we use DEFAULT_PAGE_LIMIT as a constant:
https://github.com/ref-finance/ref-sdk/blob/e15fae08e53098e6839589dc5da976049315491a/src/pool.ts
It would be really helpful to add it as a config variable. So we can reduce amount of requests with a custom value, for example 500 | 1000 in limit.

Thanks for this suggestion, we are to add more variables into configuration, such as node urls, as well as DEFAULT_PAGE_LIMIT you mentioned.

https://github.com/ref-finance/ref-sdk/pull/7

Hi @NotEternal ,  we add on option perPage for fetchAllPools function on 1.1.5 version https://github.com/ref-finance/ref-sdk/pull/7


Change sort logic for autofill credentials

Task/Issue URL: https://app.asana.com/0/488551667048375/1203892213154874/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2817   👈

This comment was auto-generated by Graphite.


Range error in for-loop of StoryState.trimWhitespaceFromFunctionEnd()

outputStream.count == 1, but outputStream.count - 1 == 0, thus resulting in a range error where the starting value is 1 and the  ending value of the range is 0.
See line 1074
Repro:
In Ink story, use a function in your story, call it via a choice and watch the values of functionStartPoint and outputStream.count equal each other, resulting in a) range error after outputStream.count - 1 or b) index out of range error on next line (hit by removing the minus one operation on outputStream.count).

I have tried to identify where the whitespace is in the ink file that is causing this method to be called, yet, I have been unable to, despite removing all whitespaces in the function signature and as many whitespaces as I can in the Ink file in general. Still, no avail.


It's not possible to cleanly add an application-specific port.h

I'm rolling my own leveldb::Env implementation which I assumed would be completely independent of the leveldb source, but my Env will need snappy and CRC32 checks and the headers for these two things are defined in port/port_stdcxx.h included by port/port.h (which is a private header):
// Include the appropriate platform specific file below.  If you are
// porting to a new platform, see "port_example.h" for documentation
// of what the new port_<platform>.h file must provide.
#if defined(LEVELDB_PLATFORM_POSIX) || defined(LEVELDB_PLATFORM_WINDOWS)
#include "port/port_stdcxx.h"
#elif defined(LEVELDB_PLATFORM_CHROMIUM)
#include "port/port_chromium.h"
#endif

Of course I can ensure I have snappy and CRC32 on my side, but ideally both my application and leveldb would use the same entry points for this functionality without me having to ensure leveldb is configured (regarding snappy and crc32c) exactly the same way my application is.
For Chrome, the problem was "solved" by hardcoding an ifdef on LEVELDB_PLATFORM_CHROMIUM in port.h.
I have two proposed solutions/questions:

Can snappy and CRC32 calls become virtual calls on leveldb::Env?
Should port.h check a build flag (e.g. LEVELDB_PLATFORM_CUSTOM) and include a custom application-provided header?

Interestingly, port_example.h contains this comment:
// TODO(jorlow): Many of these belong more in the environment class rather than
//               here. We should try moving them and see if it affects perf.

We have no concrete plans for adding virtual calls to Env for snappy and crc32c. This still seems like the right long-term plan, but we'd need a transition period, which is most likely default implementations that call into the port versions. This is quite a bit of running to stay in the same place. :smile: In other words, this requires quite a bit of work for very little benefit.

I'd be more tempted to follow the googletest approach, which introduces a custom directory and asks embedders to manipulate the include path so that #includes resolve to a custom directory under their control.

@philix In the short term, you could #define LEVELDB_PLATFORM_CHROMIUM for the LevelDB compilation units, and create a port/chromium.h somewhere on your include path.

@pwnall Thanks for sharing how you see the situation from your side.
I created a port/port_chromium.h and it works. It helped that I already had a custom CMakeLists.txt


Bug: Issue with pagination control, rows per page, on Table and Datagrid

Issue:
Looks like this issue was introduced in v4.3.0. Everything is working as intended in v4.2.0
Table pagination: https://react-magma.cengage.com/version/4.3.0/api/table/#pagination
The table pagination starts at 10 rows per page. If you change that to a different value using the select, the number of rows shown updates correctly, but the select still shows as 10 selected.
https://github.com/cengage/react-magma/assets/24397282/babfa1c0-a366-4015-9dbd-13eb9183f813
Datagrid: https://react-magma.cengage.com/version/4.3.0/api/datagrid/
The way this is showing on Datagrid is slightly different. On the very first example in the documentation, the pagination is set to 10 rows per page, but all 25 rows in the example are already showing by default. If you change the value to 20 or some other value, the table itself updates correctly, but the select in the pagination remains set at 10, just like the regular table component.

PR https://github.com/cengage/react-magma/pull/1159 introduced this bug when we changed NativeSelect.

This ticket correctly addresses the first issue. However, the weirdness with our DataGrid example noted above has not been addressed.

Confirmed Datagrid issue has been addressed ✅


AMDDefineDependencyParserPlugin processItem simplification

This PR introduces small refactor to processItem function in AMDDefineDependencyParserPlugin. Currently with each invoke of  processItem the returned value has been checked and when result was missing processContext has been called. To simplify code and avoid additional checks processContext has been moved inside processItem.
I'm also not sure if boolean returns from processItem and processContext are still needed but I leave them for now. Also it seems that return of processContext was never used in current code. If you can confirm or deny this I can prepare suitable update to this PR.
What kind of change does this PR introduce?
Small refactor/code cleanup.
Did you add tests for your changes?
No.
Does this PR introduce a breaking change?
No.

@sokra Can I get any feedback on that PR?
Also label 'PR: tests-needed' seems invalid, because no logic changes has been made and coverage should stay as the same as before.

Also label PR: tests-needed seems invalid, because no logic changes has been made and coverage should stay as the same as before.

You touched code that is not tested:

Thank you for the feedback. I will work on that.


TRG-Check Pipeline Issues

Is your support request related to a problem? Please describe.
Failing trg-checks in pipeline.
Pipeline Run

Docker File which fails
Helm Chart which is unable to render

Describe the solution you'd like
Due to a correct configuration I expect the pipeline to be successful.
Additional context
Already talked to @SebastianBezold regarding my issues.

As i already suspected, our current implementation of the non root user check does not resolve the variable references used in USER  ${UID}:${GID}. It's currently seen as invalid user. I'll see, if we can improve the check to also resolve that and then have it as valid user.
The Dockerfile is following the TRGs correctly. The automation itself is the issue here.

The Chart rendering fails with following error:
"traceability-foss/charts/frontend/templates/deployment.yaml" at <.Values.imagePullSecret.dockerconfigjson>: nil pointer evaluating interface {}.dockerconfigjson
Running helm template on the Chart directly works as expected. I'll check if there is a know issue or newer version of the helm library we use

Yes, it is a known, reported issue: https://github.com/helm/helm/issues/12385

Ah cool thanks for pointing out. Didn't know that it is even reported by you 😁

Hi @ds-mwesener, apologies for late response, it seems the latest fix to quality check tool covers your case. I tested it on the provided forked repo and on the original at tractus-x, both went through. Please try run it again and let us know the result.
cc: @FaGru3n

Hey @ds-mwesener! Does the trg check show correct results now? If yes, I would close this issue.

If your fine with the result i would close this issue.

Hi @almadigabor / @FaGru3n we still have issues with the pipeline:

moved to our backlog to plan it properly


clone - adding option to choose an endpoint prefix.

Untested.

Update: I got it to run with gevent==1.1.0. Currently trying to figure out how to get around the /-escaped characters (e.g. https://pokeapi.co/api/v2/language/ has values like https:\/\/pokeapi.co\/api\/v2\/language\/2\/).

Updated description with the test I ran.


Move failed DNS requests behind those of other apps, but keep interna…

…l ordering
@mpolden please review.

Last commit has NSD release the NSQ lock while dispatching, to avoid hogging the RP lock. Since only NSD should remove from the queue, and only one NSD should run at a time (locked on maintainer level), the assumption that the queue has only been prepended or appended to should hold. I think logging a warning, and doing a best-effort amendment when this assumption fails, is OK.

Last commit has NSD release the NSQ lock while dispatching, to avoid hogging the RP lock. Since only NSD should remove from the queue, and only one NSD should run at a time (locked on maintainer level), the assumption that the queue has only been prepended or appended to, should hold. I think logging a warning, and doing a best-effort amendment when this assumption fails, is OK.

I don't think this is worth the extra complexity and assumptions about other locks. Current locking semantics has worked fine for years. If there is lock contention due to a bug in the dispatching process it's better if everything blows up rather than to keep pushing more things onto the queue. Deployments don't work anyway if we can't do DNS updates in a timely manner.

The problem is that not just deployment are stalled, but all modifications to application metadata are blocked, once a deployment is attempted, fails and blocks due to this, because the application lock is also held while holding the routing policies lock. I think it's worthwhile to avoid this complete deadlocking. We could look for all places where we take both locks, and see if we can eliminate them, instead/as well.

Ah, the NSQ lock is also taken directly other places, while hold application locks. Not sure how hard it is to remove all those, or if it's feasible at all.


Republishing library to Maven Central?

So there's no need to add one more repository to project

I will consider this when I have time, thanks

Do you need help with it? For now we concider or re-publish library in our private repo, or help with publishing to maven central


Added slonik guide to docs

Added a guide on how to start using SafeQL with Slonik 😃

This is great! Thanks 🙏


Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON

Describe the Bug
1.2.840.113619.2.409.65140653520588628040.1720486207.12687.0.json

Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON
Steps to Reproduce
Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON
The current behavior
Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON
The expected behavior
Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON
OS
windows 10
Node version
18.16.1
Browser
chrome 125

I can't access your files from here http://<IP_ADDRESS>:8100/dicom/jr/1.2.840.113619.2.409.65140653520588628040.1720486207.12687.3.dcm
Can you make that publicly available? Also, your JSON is not compliant with our schema. Can you generate it with our generator?
https://docs.ohif.org/configuration/dataSources/dicom-json