az command fails with "cannot import name 'ChallengeAuthenticationPolicy' from 'azure.core.pipeline.policies'"

One of the recent updates of one of the Azure SDK components broke the Azure CLI again.
I have not yet been able to localize the problem, but I am reporting it here through az feedback anyway in the hope to get some pointers to what could be the problem.
This issue shows with the packaged version of the Python Azure SDK and Azure CLI packages on openSUSE Tumbleweed. There might be a version mismatch of any of the component packages but I have not figured out yet which package is the culprit.
Describe the bug
Command Name
az login
Errors:
The command failed with an unexpected error. Here is the traceback:
cannot import name 'ChallengeAuthenticationPolicy' from 'azure.core.pipeline.policies' (/usr/lib/python3.8/site-packages/azure/core/pipeline/policies/__init__.py)
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/usr/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/usr/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/lib/python3.8/site-packages/azure/cli/command_modules/profile/custom.py", line 152, in login
    subscriptions = profile.find_subscriptions_on_login(
  File "/usr/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 201, in find_subscriptions_on_login
    subscriptions = subscription_finder.find_through_authorization_code_flow(
  File "/usr/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 917, in find_through_authorization_code_flow
    result = self._find_using_common_tenant(token_entry[_ACCESS_TOKEN], resource)
  File "/usr/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 961, in _find_using_common_tenant
    client = self._arm_client_factory(token_credential)
  File "/usr/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 871, in create_arm_client_factory
    client_type = self._get_subscription_client_class()
  File "/usr/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 1050, in _get_subscription_client_class
    from azure.cli.core.vendored_sdks.subscriptions import SubscriptionClient
  File "/usr/lib/python3.8/site-packages/azure/cli/core/vendored_sdks/subscriptions/__init__.py", line 9, in <module>
    from ._subscription_client import SubscriptionClient
  File "/usr/lib/python3.8/site-packages/azure/cli/core/vendored_sdks/subscriptions/_subscription_client.py", line 12, in <module>
    from azure.mgmt.core import ARMPipelineClient
  File "/usr/lib/python3.8/site-packages/azure/mgmt/core/__init__.py", line 29, in <module>
    from ._pipeline_client import ARMPipelineClient
  File "/usr/lib/python3.8/site-packages/azure/mgmt/core/_pipeline_client.py", line 32, in <module>
    from .policies import ARMAutoResourceProviderRegistrationPolicy, ARMHttpLoggingPolicy
  File "/usr/lib/python3.8/site-packages/azure/mgmt/core/policies/__init__.py", line 28, in <module>
    from ._authentication import ARMChallengeAuthenticationPolicy
  File "/usr/lib/python3.8/site-packages/azure/mgmt/core/policies/_authentication.py", line 32, in <module>
    from azure.core.pipeline.policies import ChallengeAuthenticationPolicy
ImportError: cannot import name 'ChallengeAuthenticationPolicy' from 'azure.core.pipeline.policies' (/usr/lib/python3.8/site-packages/azure/core/pipeline/policies/__init__.py)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az login

Expected Behavior
Environment Summary
Linux-5.12.0-2-default-x86_64-with-glibc2.2.5
Python 3.8.9
Installer: PIP

azure-cli 2.23.0

Additional Context

Is the issue resolved or not in latest version?


refactor(name): reduce unnecessary String allocation

This PR improve performance of escape and hyperlink functions of Name struct by reducing number of String allocation.

TODO

[x] Use cargo fmt
[ ] Add necessary tests
[ ] Add changelog entry
[ ] Update default config/theme in README (if applicable)
[ ] Update man page at lsd/doc/lsd.md (if applicable)

Codecov Report

Merging #676 (4622927) into master (2ffb59c) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #676      +/-   ##
==========================================
+ Coverage   88.32%   88.34%   +0.01%
==========================================
  Files          41       41
  Lines        4607     4606       -1
==========================================
  Hits         4069     4069
+ Misses        538      537       -1

Impacted Files
Coverage Δ

src/meta/name.rs
89.92% <100.00%> (+0.33%)
: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 2ffb59c...4622927. Read the comment docs.

Is it really making much of a difference? I was getting mostly mixed results with original version being better(within error margin).

Hmm. Maybe this changes doesn't significantly improve performance of the program. However, I'll try writing a benchmark to test performance render, escape and hyperlink functions of Name struct.
What do you think about Cow<str>? Do you have any concern about its complexity?

Do you have any concern about its complexity?

As long as it provides some perf improvement, I don't mind the added complexity.

I'm closing this PR for now. We can revisit it later if you think this could improve things here.


Update headspace-tutorial.md

Correct necessary SAML attributes

@rileysung-headspace : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jeevansd
Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Document updated as requested,
#please-close


pytest fixtures dimmed as unused import despite being used

Environment data

Pylance version: v2024.9.2
OS and version: Win10.0.19045 Build 19045
VSCode Version: 1.93.1
Python version (& distribution if applicable, e.g. Anaconda): 3.10.5, direct from Python.org

Code Snippet
Given these two files: tests.test_dependencies and tests.test_module
tests.test_dependencies
import pytest

@pytest.fixture(scope="function")
def fixture_function():
    yield 1

tests.test_module
from tests.test_dependencies import fixture_function

def test_number_one(fixture_function):
    assert fixture_function == 1

Repro Steps

Use VSCode's built-in Pylance
pip install pytest
Write above code in a module.
See fixture dimmed, depending on your theme.

Expected behavior

Actual behavior

Logs

N/A

Comments
I was initially hesitant on posting this after reading #1059 and #684, but I thought I'd post my own discussion here to get to the bottom of this, if that's welcome.
Is this dimming of the unused import something handled by pylint, and not an issue with pylance?
Is this also due to the way pytest calls fixtures which may perhaps be less than pythonic?
Any hints on where the root of this may lie? I'd be glad to look into this.

This is because Pyright (the underlying typechecker for Pyright) doesn't see this code as using the fixture:
def test_fixture_function(fixture_function):
    assert fixture_function == 1

From its point of view, the fixture_function parameter is just a named parameter, it is not actually using the import. That you have to import the fixture is really a function of how pytest works at runtime and can't currently be modeled by a static typechecker.
We do however add some dynamic capabilities to Pyright inside of Pylance and usage of fixtures is just something we haven't done yet.

Hmm, further digging, I realise this is exactly what conftest.py was made for! Using that means one does not need to perform such imports. Hope this helps anyone else stumbling upon this.
Regardless, the imports also work just fine even if they are declared as in my example above. They'll just be linted wrongly as above. I believe it could still be looked into...

if you want to keep the import, you need to write like from tests.test_dependencies import fixture_function as fixture_function
the grey out means the code will work without the import statement. you will get same behavior if you add import os. it won't break your code even if you have unnecessary import, but we are telling you that the code will still work even if you remove the import statement.


import/no-duplicates warn for duplicates imports from .d.ts file

I'm using date-fns and importing several helpers from the library:
import format from "date-fns/format";
import parseISO from "date-fns/parseISO";
import getUnixTime from "date-fns/getUnixTime";

With the rule import/no-duplicates enabled, I have this error:
'~/node_modules/date-fns/typings.d.ts' imported multiple times

I'm using the library properly and don't have duplicates so I guess it's a bug in the resolver no?

See https://github.com/benmosher/eslint-plugin-import/issues/1479


How to get type from react-vant?

which file can import this type?

https://3lang3.github.io/react-vant/#/zh-CN/list

thank u. I find a way to fixed it.


Automated Package Upgrade

:tada: This PR is included in version 5.0.328 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove default python kernel on the HYR-SENSE image

Make sure that the first choice for jupyter kernels is the hyr-sense environment.

We want to have to avoid having to open a new notebook and then select the HYR-SENSE kernel. e.g.


Fix race condition on pre-resolve actions

If a configuration is used in a task without being declared as an input,
there's a chance that the dependency actions are executed concurrently
by several threads.
This commit works around the problem by introducing locking around the
dependency actions.
Fixes #15120

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

OK, I've already cancelled the old build and triggered a new ReadyForMerge build for you.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

Fix reverted because it introduces a deadlock.


begin updating webhook documentation

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.9 Features: set Milestone to 1.9 and Base Branch to release-1.9
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: Please check the “Allow edits from maintainers” box (see image below) to
allow reviewers to fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.
NOTE: After opening the PR, please un-check and re-check the "Allow edits from maintainers" box. This is a temporary workaround to address a known issue with GitHub.

This change is

I don't think this is done yet but I want to get something out there.

PTAL

The find-and-replaces are going to make rebasing this a huge pain, so the faster we can commit this, the better. Happy to make further changes in follow-ups if this meets some minimum bar.

I think there's some comments I didn't see that github hid after one of my edits--will try to double check later.

Thanks for the comments, I will try to address them today.
On Fri, Dec 1, 2017 at 5:31 PM, Chao Xu<EMAIL_ADDRESS>wrote:

@caesarxuchao commented on this pull request.
Maybe we should document if each admission controller is mutating,
validating or both.
In docs/admin/admission-controllers.md
https://github.com/kubernetes/website/pull/6368#discussion_r154481103:

+Admission controllers may be "validating", "mutating", or both. Mutating
+controllers may modify the objects they admit; validating controllers may not.
+
+The admission control process proceeds in two phases. In the first phase,
+mutating admission controllers are run. In the second phase, validating
+admission controllers are run. Note again that some of the controllers are
+both. In both phases, the controllers are run in the order specified by the
+--admission-control flag of kube-apiserver.
+
+If any of the controllers in either phase reject the request, the entire
+request is rejected immediately and an error is returned to the end-user.
+
+Finally, in addition to sometimes mutating the object in question, admission
+controllers may sometimes have side effects, that is, mutate related
+resources as part of request processing. Incrementing quota usage is the
Clarifying that the quota admission is actually a validation webhook,
since it doesn't mutate the request itself.
In docs/admin/admission-controllers.md
https://github.com/kubernetes/website/pull/6368#discussion_r154481414:

be used to apply default resource requests to Pods that don't specify any; currently, the default LimitRanger
applies a 0.1 CPU requirement to all Pods in the default namespace.

See the limitRange design doc and the example of Limit Range for more details.
+### MutatingAdmissionWebhook (beta in 1.9)
+
+This admission controller calls any mutating webhooks which match the request. Matching
+webhooks are called in serial; each one may modify the object if it desires.
+
+This admission controller (as implied by the name) only runs in the mutating phase.
+
+If a webhook called by this has side effects (for example, decrementing quota) it
Quota is a validating plugin, to avoid confusion, use another example.
In docs/admin/admission-controllers.md
https://github.com/kubernetes/website/pull/6368#discussion_r154482595:

be used to apply default resource requests to Pods that don't specify any; currently, the default LimitRanger
applies a 0.1 CPU requirement to all Pods in the default namespace.

See the limitRange design doc and the example of Limit Range for more details.
+### MutatingAdmissionWebhook (beta in 1.9)
+
+This admission controller calls any mutating webhooks which match the request. Matching
+webhooks are called in serial; each one may modify the object if it desires.
+
+This admission controller (as implied by the name) only runs in the mutating phase.
+
+If a webhook called by this has side effects (for example, decrementing quota) it
+must have a reconcilation system, as it is not guaranteed that subsequent
+webhooks or validating admission controllers will permit the request to finish.
+
+If you disable the MutatingAdmissionWebhook, you must also disable the
+MutatingWebhookConfiguration object in the admissionregistration/v1beta1
+group/version via the --runtime-config flag (both are on by default in
+versions >= 1.9).
I would say it reversely: if you disable the API, you must disable the
admission controller.
In docs/admin/admission-controllers.md
https://github.com/kubernetes/website/pull/6368#discussion_r154482670:

+This admission controller (as implied by the name) only runs in the mutating phase.

+If a webhook called by this has side effects (for example, decrementing quota) it
+must have a reconcilation system, as it is not guaranteed that subsequent
+webhooks or validating admission controllers will permit the request to finish.
+
+If you disable the MutatingAdmissionWebhook, you must also disable the
+MutatingWebhookConfiguration object in the admissionregistration/v1beta1
+group/version via the --runtime-config flag (both are on by default in
+versions >= 1.9).
+
+#### Use caution when authoring and installing mutating webhooks
+

Users may be confused when the objects they try to create are different from

what they get back.

Setting originally unset fields is less confusing that overwriting fields set in

Duplicate
In docs/admin/admission-controllers.md
https://github.com/kubernetes/website/pull/6368#discussion_r154482782:

+If you disable the ValidatingAdmissionWebhook, you must also disable the
+ValidatingWebhookConfiguration object in the admissionregistration/v1beta1
+group/version via the --runtime-config flag (both are on by default in
+versions >= 1.9).
It's the reverse.
In docs/admin/admission-controllers.md
https://github.com/kubernetes/website/pull/6368#discussion_r154483324:

Yes.
-For Kubernetes >= 1.6.0, we strongly recommend running the following set of admission control plug-ins (order matters):
+For Kubernetes >= 1.9.0, we strongly recommend running the following set of admission controllers (order matters):
+
+```shell
+--admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,ValidatingAdmissionWebhook,ResourceQuota,DefaultTolerationSeconds,MutatingAdmissionWebhook
Leaving MutatingAdmissionWebhook at last might be confusing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/6368#pullrequestreview-80658946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglsDWCmqK2kdDU5go1eNcifPM4fe3ks5s8KiIgaJpZM4QiyDk
.

@lavalamp 👋 Sorry, this PR was merged prematurely. Please open a new PR and cherry-pick the commits, then continue working on the feedback from this PR in the new one.
/cc @tengqm

sigh :(

@lavalamp Sorry. 😞

@lavalamp 👋 Just a heads up that docs need to be complete by this Friday, 12/8. I'm happy to help with whatever I can; please let me know.

You could un-revert this PR? ;) ;)
More seriously I have three KubeCon sessions tomorrow and I am traveling
Friday.
What happens if it is not done on Friday?
On Wed, Dec 6, 2017 at 5:48 PM, Zach Corleissen<EMAIL_ADDRESS>wrote:

@lavalamp https://github.com/lavalamp 👋 Just a heads up that docs need
to be complete by this Friday, 12/8. I'm happy to help with whatever I can;
please let me know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/6368#issuecomment-349835609,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglrbJW5zKxsoLNhWht-zpOzW9tuEGks5s90PQgaJpZM4QiyDk
.

You could un-revert this PR? ;) ;)

More seriously I have three KubeCon sessions tomorrow and I am traveling Friday.

That's real.

What happens if it is not done on Friday?

Can you have it done by the end of Monday?
It's already in pretty good shape, so I can arrange to review your PR last before we freeze and merge.
Note: After opening the new PR, be sure to un-check and re-check the box allowing edits from maintainers. (It's a workaround for a broken GitHub UI component.) This will shorten the amount of back and forth considerably.
Does that work?

Yeah, my plan was to work on it Monday, although I just looked at my
calendar and, yikes. I will do my best to get something presentable
sometime monday.
On Wed, Dec 6, 2017 at 9:06 PM, Zach Corleissen<EMAIL_ADDRESS>wrote:

You could un-revert this PR? ;) ;)
[image: giphy 1]
https://user-images.githubusercontent.com/3210446/33699537-5d21fb56-dad9-11e7-9555-62ca69939468.gif
More seriously I have three KubeCon sessions tomorrow and I am traveling
Friday.
That's real.
What happens if it is not done on Friday?
Can you have it done by the end of Monday?
It's already in pretty good shape, so I can arrange to review your PR last
before we freeze and merge.
Note: After opening the new PR, be sure to un-check and re-check the
box allowing edits from maintainers. (It's a workaround for a broken GitHub
UI component.) This will shorten the amount of back and forth considerably.
Does that work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/6368#issuecomment-349864320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglmFPHG0p9Bg-ShIMPNWhDPx8-Q--ks5s93JUgaJpZM4QiyDk
.


Bundler update (BUNDLED WITH 2.0.2 issue)

https://bundler.io/blog/2019/05/14/solutions-for-cant-find-gem-bundler-with-executable-bundle.html
https://github.com/netlify/build-image/issues/296

Obsolete, bundler currently at 2.2.28


Please Update connectivity package to the lastest 2.0.2

One of our apps need connectivity 2.0.2 and the latest version of graphql-flutter uses 2.0.0 of connectivity.  Because of this, we have a dependency conflict issue.
Can this be upgraded to the latest version of connectivity ?

Shouldn't this not be an issue? Our version is ^2.0.0 which should be equivalent to >=2.0.0 <3.0.0


Fixed python3 bug

Fixed a bug in python3 where colorscale would not generate
str, unicode -> six.string_types

Hey Jack - I had some conflicts on PR - but this issue has been solved. Thank you for your help!


Update routing-tree to add tooltip that shows receiver configs on text mouseOver

This is a rather small change (read: hack) I am using on a local branch which I find useful when working with complex receiver configs. It shows a tooltip when hovering on top of the receiver name in the tree. This currently shows the raw yaml of the receiver config.
I'm far from a javascript expert, so I'll be the first to admit the code is probably not that great but possibly 'good enough' to be considered, hence why I'm opening this PR.
Additional ideas:

Add a checkbox to toggle showing receiver configs or not (disabled by defaul?)
Improve format and readability of the tooltip content since a complex recipient config can span many lines.

Implemented suggestions & rebased on top of master. I've tested locally with a few different configs and things look good.
I've sent this PR over a year ago so it took me some time to get back into it. I personally don't really need this change anymore, but I still think it's a nice addition.

Awesome, thank you! Ah sorry, I didn't even see that you first submitted this PR a year ago. I only noticed it when @roidelapluie assigned me a couple of days ago :)

:+1:


add support for fsd category (fan)

Can we get this done ASAP? need this to get my fan working

I just added the code in a 1 liner and it worked, but I have to keep patching it every time there's an update because this PR hasn't even been looked at.

Hello, I added the line as he wrote to add 'fsd' ceiling fan with light and it works!


Support dynamic keys

Hi,
I found yrr a few days ago and was amazed about the possibilities the tool has. Currently, I'm trying to transform our gitlab-ci.yml-files into something which can be reused better. In such file you often have a section like this ():
deploy:develop:
    script: ./bin/deploy/devlop.sh

deploy:staging:
    script: ./bin/deploy/staging.sh

deploy:productive:
    script: ./bin/deploy/productive.sh

This example is simplified but shows why I want to use a template for this file :). Therefore I create a values-file with the following content:
#@data/values
---
deployments:
    -   name: develop
        script: ./bin/deploy/develop.sh
    -   name: staging
        script:./bin/deploy/staging.sh
    -   name: productive
        script:./bin/deploy/productive.sh

My problem is that I have to set the key of the struct so I tried this:
#@ load("@ytt:data", "data")

#@ for deployment in data.values.deployments:
#@ "deploy:" + deployment.name + ":"
    script: #@ deployment.script
#@ end

Well, this do not work since I have to set the key (which is top level/root) dynamically. Does anybody have an idea of how to achieve dynamic keys based on values?

Hi @bosix, this is an interesting use case, thanks for sharing it.
You can achieve this by using template.replace() combined with a function. Here's an example.
Let us know if that's not what you're looking for.

Hi @pivotal-dean,
this is exactly what I was looking for. Thank you for your help.

@bosix here is another way, arguably more yaml-y: https://get-ytt.io/#example:example-text-template (see line config.yml:23)

@cppforlife thank you. I agree with you. In my case, I think your suggestion is cleaner and more readable.

Also trying something similar for creating Ansible inventory yaml on the fly.
The first approach suggested above works well enough
#@ load("@ytt:data", "data")
#@ load("@ytt:template", "template")

#@ def parse(deployment):
#@ key = "{}".format(deployment.ip)
#@ return {key: {"idrac_ip": "{{ inventory_hostname }}","catalog_xml": deployment.catalogXml}}
#@ end

all:
  hosts:
#@ for deployment in data.values.deployments:
    _: #@ template.replace(parse(deployment))

with values
#@data/values
---
deployments:
- ip: <IP_ADDRESS>
  catalogXml: "Catalog1.xml"
- ip: <IP_ADDRESS>
  catalogXml: "Catalog2.xml"

Based on the comment from @cppforlife I'm wondering is there a better way to do this more yaml-y? I took at a look at the suggested example https://get-ytt.io/#example:example-text-template (line config.yml:23) but couldn't correlate it to the desired result
all:
  hosts:
    <IP_ADDRESS>:
      idrac_ip: '{{ inventory_hostname }}'
      catalog_xml: Catalog1.xml
    <IP_ADDRESS>:
      idrac_ip: '{{ inventory_hostname }}'
      catalog_xml: Catalog2.xml

I created a new gist using the text templating https://carvel.dev/ytt/#gist:https://gist.github.com/joaopapereira/d2a2701c488f68d0ee4c91a618aadb11 that can solve what you are looking for without the function and using the text templating.
@matthewcosgrove does this help?

Yes that's much nicer, thanks @joaopapereira


Use protobuf for log persistence

This PR replaces bespoke string-based log persistence format with protobuf

Branch grew out of scope--closing in favor of making smaller changes separately

Superceded by #20


Implement custom geometry API

@mithi next I'll try to implement the API into bare-minimum-3d. I guess it should look like this:
renderScene(viewSettings, sceneSettings, sceneOptions, data3d, plugins)

@mithi I suppose we need a way to tell the DataRenderer.render() which projection method should be used. Currently this is determined by it's (hardcoded) type.
How about we instead ask if the data is shaped like a point or a line. Eg: does it have a property x or x0? The line case seems rather exotic to me. Did you plan other primitive types?
In order to make my triangles example work, all I needed to do was:
    render(data: Array<Data3dSpecs>): Array<Data2dSpecs> {
        console.debug(data)
        return data.map((element: Data3dSpecs) => {
            switch (element.type) {
-               case DataSpecType.polygon:
-               case DataSpecType.points:
-                   return this._projectPolygonOrPoints(element)
                case DataSpecType.lines:
                    return this._projectLines(element)
+               default:
+                   return this._projectPolygonOrPoints(element)
            }
        })
    }

What do you think? should _projectPolygonOrPoints be used as the default?

I think it is better to be more explicit with the types and to be more explicit on the algorithm that will be used based on the type.
Also I think it would be better, if DataRenderer is not modified at all inspired by the open-closed principle. The code might be easier to maintain if it's closed for modification but open for extension..
It might be better if the pseudo code could be something like this:

// plugin = {
//  Renderer: (The actual renderer)
//  types: (the types it can render)
// }

const renderScene = (
  viewSettings: ViewSettings,
  sceneSettings: SceneSettings,
  sceneOptions: SceneOptions,
  data3d: Array<Unknown>,
  plugins: Array<Unknown>
)  {

  // .... initial computations

  const bareMinimumDataRenderer = new DataRenderer(
    cube.range,
    dataXoffset,
    dataYoffset,
    dataZoffset,
    cube.wrtCameraMatrix,
    projectionConstant
  )

  const models = data.map((element: Data3dSpecs) => {
    if ([DataSpecType.polygon, DataScpecType.points].includes(element.type) {
      return bareMinimumDataRenderer._projectPolygonOrPoints(element)
    } else if (element.type === DataSpecType.lines) {
      return bareMinimumDataRenderer._projectLines(element)
    } else {
      // the bareMinimumDataRender does not know how to render this type of data
      // use one of your customRenderers here
      for ( plugin of plugins) {
        if(plugin.types.includes(element.type)) {
          return new plugin.Renderer(
            cube.range, dataXoffset, dataYoffset, dataZoffset, cube.wrtCameraMatrix, projectionConstant
          ).render(element)
        }
      }
    }
    // write an error here `unhandled datatype: ${element.type}`
  })

  // more code here....

  return {
    container,
    data: [...sceneData, ...models],
  }
}

I think it is better to be more explicit with the types and to be more explicit on the algorithm that will be used based on the type.
Also I think it would be better, if DataRenderer is not modified at all inspired by the open-closed principle. The code might be easier to maintain if it's closed for modification but open for extension..
It might be better if the pseudo code could be something like this:

// plugin = {
//  Renderer: (The actual renderer)
//  types: (the types it can render)
// }

const renderScene = (
  viewSettings: ViewSettings,
  sceneSettings: SceneSettings,
  sceneOptions: SceneOptions,
  data3d: Array<Unknown>,
  plugins: Array<Unknown>
)  {

  // .... initial computations

  const bareMinimumDataRenderer = new DataRenderer(
    cube.range,
    dataXoffset,
    dataYoffset,
    dataZoffset,
    cube.wrtCameraMatrix,
    projectionConstant
  )

  const models = data.map((element: unknown) => {
    if ([DataSpecType.polygon, DataScpecType.points, DataSpecType.lines].includes(element.type) {
      return bareMinimumDataRenderer.render([element])
    } else {
      // the bareMinimumDataRender does not know how to render this type of data
      // use one of your customRenderers here
      for ( plugin of plugins) {
        if(plugin.types.includes(element.type)) {
          return new plugin.Renderer(
            cube.range, dataXoffset, dataYoffset, dataZoffset, cube.wrtCameraMatrix, projectionConstant
          ).render(element)
        }
      }
    }
    // write an error here `unhandled datatype: ${element.type}`
  })

  // more code here....

  return {
    container,
    data: [...sceneData, ...models],
  }
}

I think it is better to be more explicit with the types and to be more explicit on the algorithm that will be used based on the type.
Also I think it would be better, if DataRenderer is not modified at all inspired by the open-closed principle. The code might be easier to maintain if it's closed for modification but open for extension..
It might be better if the pseudo code could be something like this:

// plugin = {
//  Renderer: (The actual renderer)
//  types: (an array of types it can render)
// }

const renderScene = (
  viewSettings: ViewSettings,
  sceneSettings: SceneSettings,
  sceneOptions: SceneOptions,
  data3d: Array<Unknown>,
  plugins: Array<Unknown>
)  {

  // .... initial computations

  const bareMinimumDataRenderer = new DataRenderer(/*...arguments...*/ )

  const models = data.map((element: Unknown) => {
    if ([DataSpecType.polygon, DataScpecType.points, DataSpecType.lines].includes(element.type) {
      // this could be optimized by adding the function:
      // bareMinimumDataRenderer.renderSingle(element)
      return bareMinimumDataRenderer.render([element])
    }

    // the bareMinimumDataRenderer does not know how to render this type of data
    // use one of your customRenderers here
    for (let plugin of plugins) {
      if(!plugin.types.includes(element.type)) {
        continue
      }
      return new plugin.Renderer(/*...arguments...*/).render(element)
    }
    // write an error here `unhandled datatype: ${element.type}`
  })

  // more code here....

  return { container, data: [...sceneData, ...models] }
}

Did you plan other primitive types?

I only planned one other type which is 3d circles.. see also: https://github.com/mithi/bare-minimum-3d/issues/6

@fuddl
If you also think that you need to reuse the the built DataRenderer, feel free to modify bare-minimum-3d to expose it
so that your custom plugin / data renderer could use it. ie modify
https://github.com/mithi/bare-minimum-3d/blob/master/src/index.ts
import { renderScene } from "./utils.js"
import DataRenderer from "./data-renderer"
export { DataRenderer }
export default renderScene

you are suggesting plug-ins should look like this?
const trianglesPlugin = {
  triangles: {
    types: ['points'],
    Renderer: (element, transforms) => {
      const { size, color, opacity, id } = element
      return element.x.map((x, i) => (
        <Triangle
          {...{
            x,
            y: element.y[i],
            size,
            color,
            opacity,
            id,
            i,
            transforms
          }}
          key={`${id}-${i}`}
        />
      ))
    }
  }
}

and their invocation should look like this?
const { container, data } = renderScene(
  viewSettings,
  sceneSettings,
  sceneOptions,
  [{
    id: 'my-trangle',
    type: 'triangles',
    opacity: 1.0,
    color: 'white',
    size: 2,
    x: [42],
    y: [23],
    z: [47],
  }],
  [trianglesPlugin]
)

you are suggesting plug-ins should look like this?

No.
renderScene converts 3d data to 2d data.
For example, this is the input
const dataInput3d = [{
        color: BODY_COLOR,
        opacity: 1.0,
        size: HEAD_SIZE,
        id: "head",
        type: DataSpecType.points,
        x: [0.0],
        y: [100.0],
        z: [100.0],
    }]

this would be the output

const dataOutput2d = [{
            color: "#FC427B",
            opacity: 1,
            size: 14,
            id: "head",
            type: "points",
            x: [-20.91252502759967],
            y: [-93.39172830586264],
            z: [100],
        }
]

And this 2d data is the one you feed to BareMinimum2d ie
const { container, dataOutput2d } = renderScene(
        viewSettings,
        sceneSettings,
        sceneOptions,
        dataInput3d
    )

<BareMinimum2d {...{container, data: dataOutput2d} />

You may ask,  if the data output is 2d why is there a z component?
This is the code pertaining to that:
https://github.com/mithi/bare-minimum-3d/blob/a4e4d488a8c938ba5b7901d4941551a9022ade2a/src/vector.ts#L26-L28
Where z is how far the point is from the "camera" / "projection plane" (if i implemented it correctly)

Source
The BareMinimum2d component completely ignores the z component when rendering.
I know it's a lot to take in, and it may take some time to understand. ..
But that's how it works...
It's alright if you think it's too much work to make it work... don't feel obligated to continue implementing this feature!


Interactive Color change in hairsegmentationgpu

Pull request - https://github.com/google/mediapipe/pull/3145
System information (Please provide as much relevant information as possible)

MediaPipe Solution (you are using): hairsegmentationgpu
Programming language : C++/Android Java
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state:
The node options provide a static color to Recolor calculator.
Will this change the current api? How?
An additional RGB_OUT label is added in input stream.
Who will benefit with this feature?
For any recolor calculator usage, the user can provide its own set of RGB values to recolor
Please specify the use cases for this feature:

AR apps - Live changes to face or other aspects of color
#18
Can be used in providing a base tutorial for other dynamic changes to calculators

Any Other info:
The implementation is done only on hairsegmentationgpu. Need to work on CPU approach.
#334

Hi @PrinceP , You can try doing it using this issues https://github.com/google/mediapipe/issues/420, https://github.com/google/mediapipe/issues/18


Btax output tooltips

[x] add constants.py and btax related tooltips
[x] add variable tooltips to btax output page
[x] fix industry table css
[ ] get addtional tooltip content for other controls
industry
asset
reform
baseline
change from reform
[ ] add groupings of output category

@brendancol looks good! Can you add the updated __mock_results.json to this PR or provide to me and @PeterDSteinberg ?

@talumbau @PeterDSteinberg I added two supporting files which I used as mock table_json for constructing the btax result table.  __mock_btax_result.json is the current version of table_json produced for the table, mock_btax_result.json is a modified version which contains major_grouping, summary_nc, and summary_n fields

@PeterDSteinberg I don't think you can get DEFAULT_ROW_GROUPINGS like you have in your PR until you merge the PR into master because the PR is set up with source branch as in your fork

LGTM. merging.


ServerBackendError renaming

This error can appear throughout the whole flow of any Repository-Backend involved process. In consequence, its name should be tied neither to the backend, nor to the repository.
We should be using a different name, for instance: JaymeError.

⚠ Watch out for documentation updates when renaming!

Renaming process checklist:

[ ] Every appearance in code is renamed
[ ] Every according file is renamed
[ ] Project builds successfully
[ ] Tests pass successfully
[ ] There's a deprecation/migration mechanism implemented in code
[ ] README is updated
[ ] CHANGELOG is updated


Add REM comments

@facebook / @mroch @int3 @gabelevi

I add some REM comments. :pencil2:
Yours,
Suriyaa Kudo :octocat:

Thanks for the contribution! Looks good to me!

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


HBASE-27433 DefaultMobStoreCompactor should delete MobStoreFile clean…

…ly when compaction is failed

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 24s
Docker mode activated.

@Apache9 , thank you for review, yes, if we crash before deleting the committed files, we may depend on the RSMobFileCleanerChore to archive them, and finally clean them.

OK, go for it!


Support dynamic generation of cacheKeyPrefix

It would be good to dynamically generate the cacheKeyPrefix based on the incoming request
The use case would be to set the cacheKeyPrefix to the tenantId for the incoming request so each tenant has its own namespace for the keys
For us the tenantId would either be in the header or as part of the JWT based on how the user is authenticated

@Tam2  makes sense, let me know if you are willing to contribute

@Tam2  have you considered passing options  to IdempotencyParams?
you can also refer this test case.
https://github.com/mahendraHegde/node-idempotency/blob/e6259d6713cc2a4091b9c3f5b80236a1bbf63bf4/packages/core/tests/e2e/idempotency.spec.ts#L70-L105
let me know if you have any doubts.


Pre-configured meetings

Contact Details
<EMAIL_ADDRESS>What benefits does the suggestion solve?
Instead of generating one simple meeting everytime you click the add-in button, we could provide X number of pre-configured meetings. These would be presented in a dropdown as per the standardised way in Outlook. This could be beneficial for those users that need more advanced configurations of their meetings.
Another solution could have been a configuration window (see #4), however, this could make every meeting unique which makes the experience for participants inconsistent. Pre-configuring a set of meeting types could eliminate this issue.
Feature suggestion description
For the user:
The normal user would only have to click on the add-in button and then receive X number of pre-configured meetings and these would be pasted to the appointment signature similarly to the current add-in.
For the admin:
The admin would need to do more work to get this to be fully functional. Our proposed solution is that the configuration would be done mostly in the config.json and manifest.xml files. This does obviously require more development time but in the long-run it is the most scalable and generic solution.
Alternative solutions
No response
Additional information
Note that this add-in would be configured in a separate manifest.xml file so that it does not interfere with the existing add-in.

The best way is to add this as a separate api. A simple service that could send out an array of meetings.
In the config add the api key and defined url.  Create a simple json file that could be served statically or through an engine that can be self developed.
This would be online with services around jitsi in general as the api for fetching phone numbers. Or the custom branding api.
It would add a minimal delay by fetching an external api

We are a simple call to an external Url in our patch to get phone numbers from a json Interface.

@small1 Is a separate API really necessary for this? You can change config by using a local config.json as part of the build folder. If you change the config file it will take affect directly on the add-in without the need to re-build it or make an external API call.

It is not necessary but it would declutter the config and make the static meetings completely configurable server side without even touching the code.  Old ones can be deleted or updated

maybe this could be made in two steps, step one via config.json/manifest.xml. Step 2 the API way

I have a solution for this that fetches the configuration depending on the users domain adress from a file server then presents predefined meetings from that organisation. The solution then builds on config.json being loaded from file server and stored in the session. It works as a mix of the above solutions. The main benefit for this is that the code is not changed depending on config.js.

@Philldomd I think this sounds like a good idea if there is built-in logic that could handle a default state that does not require predefined meetings. In some cases this plugin might be used in its barebone state, and in such a case it might be necessary to only have one default meeting configuration. 😊

@Ayko1595 I will take this into consideration while moving this part over.


How to prevent depending on tests and vendor directories

Hi! I'm having trouble getting my layer configuration to work. I'm trying to do two things: 1) keep my production code from accidentally using test classes, and 2) keep my domain layer from depending on vendor code.
And I'm having two problems: 1) Deptrac incorrectly counts it as a violation when a test class depends on a production class, and 2) it prints something like 600,000 violations in the vendor directory.
Here are the relevant portions of my directory structure:
.
├── src
│   ├── Domain
│   └── Infrastructure
├── tests
└── vendor

Here's my configuration file:

deptrac.yaml
parameters:

  paths:
    - ./src
    - ./tests
    - ./vendor

  layers:
    -
      name: Domain
      collectors:
        - type: directory
          regex: ./src/Domain/.*
    -
      name: Infrastructure
      collectors:
        - type: directory
          regex: ./src/Infrastructure/.*
    -
      name: Tests
      collectors:
        - type: directory
          regex: ./tests/.*
    -
      name: Vendor
      collectors:
        - type: directory
          regex: ./vendor/.*

  ruleset:

    Infrastructure:
      - Domain
      - Vendor

    Tests:
      - Domain
      - Infrastructure
      - Vendor

I've inserted three violations into src/Domain/Example.php: one dependency on each of the Infrastructure layer, the tests directory, and a vendor library. It correctly finds these violations, but it reports a ton of violations in tests and vendor that I don't want it to.
Here's a representative sample from the command output:

Output
----------- ---------------------------------------------------------------------------------------------
 Reason      Domain
----------- ---------------------------------------------------------------------------------------------
 Violation   Domain\Example must not depend on Tests\EndToEndTest (Tests)
             src/Domain/Example.php:37
 Violation   Domain\Example must not depend on Infrastructure\Filesystem (Infrastructure)
             src/Domain/Example.php:38
 Violation   Domain\Example must not depend on Prophecy\Argument (Vendor)
             src/Domain/Example.php:15
----------- ---------------------------------------------------------------------------------------------

----------- ---------------------------------------------------------------------------------------------
 Reason      Tests
----------- ---------------------------------------------------------------------------------------------
Violation   Tests\EndToEnd\EndToEndTest must not depend on Domain\Example (Domain)
            Tests\EndToEndTest::57 ->
            Domain\Example::5
            tests/EndToEndTest.php:5
Violation   Tests\EndToEnd\EndToEndTest must not depend on PHPUnit\Util\Test (Vendor)
            Tests\TestCase::13 ->
            PHPUnit\Framework\TestCase::26 ->
            PHPUnit\Util\Test::1044
----------- ---------------------------------------------------------------------------------------------

----------- ---------------------------------------------------------------------------------------------
 Reason      Vendor
----------- ---------------------------------------------------------------------------------------------
Violation   Tests\EndToEnd\EndToEndTest must not depend on Infrastructure\Example (Infrastructure)
            Tests\EndToEnd\EndToEndFunctionalTestCase::57 ->
            Infrastructure\Example::12
            tests/EndToEnd/EndToEndFunctionalTestCase.php:12
----------- ---------------------------------------------------------------------------------------------

I feel like I must misunderstand something fundamental. Thank you so much for any help!

Let me see what I can glean from the data provided. I will start from the provided output and work backward.
----------- ---------------------------------------------------------------------------------------------
 Reason      Tests
----------- ---------------------------------------------------------------------------------------------
Violation   Tests\EndToEnd\EndToEndTest must not depend on Domain\Example (Domain)
            Tests\EndToEndTest::57 ->
            Domain\Example::5
            tests/EndToEndTest.php:5
Violation   Tests\EndToEnd\EndToEndTest must not depend on PHPUnit\Util\Test (Vendor)
            Tests\TestCase::13 ->
            PHPUnit\Framework\TestCase::26 ->
            PHPUnit\Util\Test::1044
----------- ---------------------------------------------------------------------------------------------

implies that you do not allow dependencies from Tests to Domain nor Vendor in your rulesets.
----------- ---------------------------------------------------------------------------------------------
 Reason      Vendor
----------- ---------------------------------------------------------------------------------------------
Violation   Tests\EndToEnd\EndToEndTest must not depend on Infrastructure\Example (Infrastructure)
            Tests\EndToEnd\EndToEndFunctionalTestCase::57 ->
            Infrastructure\Example::12
            tests/EndToEnd/EndToEndFunctionalTestCase.php:12
----------- ---------------------------------------------------------------------------------------------

implies that class-like (class, interface, trait, enum) Tests\EndToEnd\EndToEndTest is part of the Vendor layer.
Both of those things seem like you did not expect them to be the case.
Looking at the relevant parts of the provided configuration :
parameters:
  layers:
    -
      name: Vendor
      collectors:
        - type: directory
          regex: ./vendor/.*

  ruleset:
    Tests:
      - Domain

I would not expect this behavior either.
For the second problem (Tests\EndToEnd\EndToEndTest being part of the Vendor layer) the debug process is easy. You can use the deptrac debug:layer Vendor command to see all the tokens that are part of the Vendor layer. You can keep tweaking your collector configuration until the output is as you expect it.
For the first problem, I am stumped. It should not be possible given the information you've provided on this issue. Is it possible that you have mistyped something when transcribing your configuration to this issue post?
Also from the output, it seems that Tests\EndToEnd\EndToEndTest is part of both the Tests and Vendor layers:
----------- ---------------------------------------------------------------------------------------------
 Reason      Tests
----------- ---------------------------------------------------------------------------------------------
Violation   Tests\EndToEnd\EndToEndTest must not depend on Domain\Example (Domain)
            Tests\EndToEndTest::57 ->
            Domain\Example::5
            tests/EndToEndTest.php:5
----------- ---------------------------------------------------------------------------------------------

----------- ---------------------------------------------------------------------------------------------
 Reason      Vendor
----------- ---------------------------------------------------------------------------------------------
Violation   Tests\EndToEnd\EndToEndTest must not depend on Infrastructure\Example (Infrastructure)
            Tests\EndToEnd\EndToEndFunctionalTestCase::57 ->
            Infrastructure\Example::12
            tests/EndToEnd/EndToEndFunctionalTestCase.php:12
----------- ---------------------------------------------------------------------------------------------

Did you get a warning about that? deptrac emits warning messages when a token is part of more than one layer.

https://github.com/qossmic/deptrac/pull/867 mentions the current solution for @internal in a situation like yours.

That's a good catch. That could be it. Can you try to run the dev-main branch of deptrac? It has better output for those sort of situations.

That's also what deptrac says on the main branch -> DependsOnInternalToken. @TravisCarden you should also update your detrac.yml (detrac.yaml will be loaded automatically ;-)), the key regex for the config of the directory layer is deprecated and will not work with the next release. The key is value now.
Your deptrac.yaml should look like this:
- name: Domain
  collectors:
    - type: directory
      value: ./src/Domain/*

Okay, great. I updated to qossmic/deptrac:dev-main, and (the new output is a nice improvement!) my @internal annotations are in fact causing failures, e.g.:
------------------------ -----------------------------------------------------------------------------------------------------------------
 Reason                   Tests
------------------------ -----------------------------------------------------------------------------------------------------------------
 DependsOnInternalToken   PhpTuf\ComposerStager\Tests\Core\BeginnerUnitTest must not depend on PhpTuf\ComposerStager\Domain\Core\Beginner
                          You are depending on a token that is internal to the layer and you are not part of that layer. (Domain)
                          tests/Core/BeginnerUnitTest.php:50

Is there a way to disable that behavior (DependsOnInternalToken)? My @internal annotations don't mean internal to a layer, they mean internal to my library--which is an API library that external clients are supposed to be able to depend directly on the Domain (API) layer but not the Infrastructure (internal) layer. It looks like that's the cause of most or all of thousands of violations from my vendor directory, too.

 We should do better. What you can do is to have a custom rule like this:
use Qossmic\Deptrac\Core\Ast\AstMap\ClassLike\ClassLikeReference;
use Qossmic\Deptrac\Contract\Analyser\ProcessEvent;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;

class DependsOnInternalTokenSkipper implements EventSubscriberInterface
{
    public static function getSubscribedEvents()
    {
        return [
            ProcessEvent::class => ['invoke', -1],
        ];
    }

    public function invoke(ProcessEvent $event): void
    {
        foreach ($event->dependentLayers as $dependentLayer => $_) {
            if ($event->dependerLayer !== $dependentLayer
                && $event->dependentReference instanceof ClassLikeReference
                && $event->dependentReference->isInternal
            ) {
                $event->stopPropagation();
            }
        }
    }

And then register it in your config file according to the documentation.
By the subscriber precedence, it will run right before the rule that causes the violations and will prevent it from running.

Thanks! That takes care of my @internal issue if I switch to deptrac:dev-main. However...
I don't think I could do that with deptrac-shim because I need to use its classes, right? (I don't want to pull in all of deptrac's dependencies, so I wouldn't want to switch away from the shim.)
Also, I still get some other errors I don't fully understand:
php ./vendor/qossmic/deptrac/deptrac.php --config-file=deptrac.yml
7279/7279 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

-------------------------- -------------------------------------------------------------------------------------------------------------------------------------------
 Reason                     API
-------------------------- -------------------------------------------------------------------------------------------------------------------------------------------
 DependsOnDisallowedLayer   Domain\Example must not depend on Stringable
                            You are depending on token that is a part of a layer that you are not allowed to depend on. (Vendor)
                            src/Domain/AnotherExample.php:2
 DependsOnDisallowedLayer   Domain\LogicException must not depend on JetBrains\PhpStorm\Internal\TentativeType
                            You are depending on token that is a part of a layer that you are not allowed to depend on. (Vendor)
                            LogicException::14 ->
                            Exception::13 ->
                            JetBrains\PhpStorm\Internal\TentativeType::393
                            vendor/jetbrains/phpstorm-stubs/Core/Core_c.php:393
-------------------------- -------------------------------------------------------------------------------------------------------------------------------------------

# Etc...

And of course, I don't want to actually scan the vendor directory for problems. I just want to forbid one of my layers from depending on it. (It takes a long time to scan and produces false positives as we've already seen.
@patrickkusebauch Re: "There is, but it is IMHO stupid. We should do better.", I've created a feature request to be "helpful". 😉 https://github.com/qossmic/deptrac/issues/1223

I ended up solving this for myself with a custom PHPCS sniff that just looks for use statements that aren't in my namespace. It's crude, but my needs are simple. Thanks for your help! 🙂 I'll let you decide whether to close this issue.


add vercel.json with mention installCommand

Description :
Vercel now uses npm install by default and we get this :

Thanks! It means we need to add it to every challenge?

Merging this 🚀 Thanks for the quick fix Shiv!


Problem with tensorflow serving

when I was creating the tensorflow serving model with frozen PB. I am getting an empty variable folder.  could you share the un-frozen graph file?
Please help me on this issue.

Which model are you referring to?
In the readme I have some directions on how to use the model checkpoints (which are available for mobilenetv1) to generate your own frozen graph.
In my experience using a frozen model from different TensorFlow models can be challenging. Its better to export using your own froze graph from checkpoints

Hi Victordibia,
I am using ssdlitemobilenetv2 model checkpoint. Below I mentioned the code for converting the model checkpoint to serving. But empty variable folder was generated.
import tensorflow as tf
SAVE_PATH = D:/handtracking-master/model-checkpoint/ssdlitemobilenetv2/'
MODEL_NAME = 'test'
VERSION = 5
SERVE_PATH = './serve/{}/{}'.format(MODEL_NAME, VERSION)
checkpoint = tf.train.latest_checkpoint(SAVE_PATH)
print(checkpoint)
tf.reset_default_graph()
with tf.Session() as sess:
saver = tf.train.import_meta_graph(checkpoint + '.meta')
graph = tf.get_default_graph()
sess.run(tf.global_variables_initializer())
inputs =  tf.saved_model.utils.build_tensor_info(graph.get_tensor_by_name('image_tensor:0'))
detection_boxes =  tf.saved_model.utils.build_tensor_info(graph.get_tensor_by_name('detection_boxes:0'))
detection_scores =  tf.saved_model.utils.build_tensor_info(graph.get_tensor_by_name('detection_scores:0'))
detection_classes =  tf.saved_model.utils.build_tensor_info(graph.get_tensor_by_name('detection_classes:0'))
num_detections =  tf.saved_model.utils.build_tensor_info(graph.get_tensor_by_name('num_detections:0'))
export_path =  './savedmodel/3'
builder = tf.saved_model.builder.SavedModelBuilder(export_path)

prediction_signature = (
  tf.saved_model.signature_def_utils.build_signature_def(
      inputs={'inputs': inputs},
      outputs={'output1': detection_boxes,'output2':detection_scores,'output3':detection_classes},
      method_name=tf.saved_model.signature_constants.PREDICT_METHOD_NAME))

builder.add_meta_graph_and_variables(
  sess, [tf.saved_model.tag_constants.SERVING],
  signature_def_map={
      tf.saved_model.signature_constants.DEFAULT_SERVING_SIGNATURE_DEF_KEY:
          prediction_signature
  },
  )
builder.save()


masonry: TextEditor add Action::TextChanged for backspace & delete

masonry::text::edit::TextEditor should emit an Action::TextChanged(...) also on Backspace and Delete if anything was deleted, so that e.g. xilem::view::textbox::Textbox receives this action. This is already implemented for Ctrl+Backspace and Ctrl+Delete.
The code changes are not elegant, but intended to be minimally invasive.
Local cargo test failed for the modified and an unmodified code, but sometimes with different errors—which I do not quite understand.
I apologize in advance for any mistakes on my part, I've never before worked on open source repos and did not find any guideline for your project.

The test failures is likely due to #233; we will be fixing that soon, but it's waiting on review for #475.


Spaceward/test extraenv

Add extraEnv for Helm

Summary by CodeRabbit

Chores

Improved deployment by setting an additional environment variable.
Updated the .dockerignore file for better file management.

@s4ase can we use --reuse-values instead of specifying the storyblok token? The other env vars would be overridden anyway
for reference, we are doing the same here: https://github.com/warden-protocol/wardenprotocol/blob/main/.github/workflows/deploy_testnet.yml#L56


chore: Make sass watcher compile every scss file

Updated the dev script in itwinui-css to run a custom node script instead of sass --watch directly.
This new script reads a list of all component folders and generates a correctly-formatted command to run through the sass cli. This command is then run through a node child_process.
Separately, chokidar is used to watch for additions/changes to the compiled css and postprocess it further using lightningcss. Previously we were doing this step in a vite plugin in the vite config for the backstop server, but it is now being done as part of the watch script so that it works throughout the monorepo (i.e. storybook, website, etc).
All of this means that changing a .scss file now results in hot reloading react components which rely on individual css imports (unlike our html test pages which rely on all.css). This also fixes #747 since all files (including global.css) are now built by the dev script.
https://user-images.githubusercontent.com/9084735/208550797-311a17fb-b74a-4055-987e-c8f84997f6cc.mov

Is this PR in addition to #861 ? Or we are going to close that one?

It replaces that one. I didn't close it because it's @rohan-kadkol's PR


Unable to submit emails

This page:
https://git-scm.com/community
encourages users to submit questions to<EMAIL_ADDRESS>However I've sent a simple text email twice and it just gets rejected. Please either correct the problem or remove the advice about using that email address.
Please....

Are you still having this issue?

Closing in lieu of response.


Issue#6 UAT Bug: "Store Locations" Cell

Related to #6.
Deciding that he wants to be very obstinate, Pat has said he wants the table to more closely match the spec he sent us and the "Store Locations" cell needs to be blank.
We will have to figure out how to empty that cell (or at least make it seem empty to sighted people, but still have text for screen readers), but keep it compliant with WebAIM accessibility standards.

@aggiewb The WebAIM standards say:

Table headers should never be empty. This is particularly of concern for the top-left cell of some tables

This link offers some suggested ways of making information apparent to screen readers, but not sighted individuals. Of note:

Using CSS to move hidden elements to a position off-screen is generally accepted as an accessible method of hiding content visually.

Perhaps we could put the text into that empty cell, but then absolutely position it with a left: -10000px as the site suggests?


Bug: Mocking a component declared in a module imported in a standalone component leads to a duplicate declaration exception

Description of the bug
When mocking a component. which is declared in a module that in turn is imported in a standalone component, this leads to duplicate declarations. (See example and error message below.)
An example of the bug
Here's a simple test reproducing this issue (also here on Stackblitz):
import { Component, NgModule } from '@angular/core';
import { TestBed } from '@angular/core/testing';
import { MockComponent, MockRender } from 'ng-mocks';

@Component({
  selector: 'my-component',
  template: '',
})
export class MyComponent {}

@NgModule({
  declarations: [MyComponent],
  exports: [MyComponent],
})
export class MyModule {}

@Component({
  selector: 'my-standalone-component',
  standalone: true,
  template: '',
  imports: [MyModule],
})
export class MyStandaloneComponent {}

beforeEach(async () => {
  await TestBed.configureTestingModule({
    imports: [MyStandaloneComponent],
    declarations: [MockComponent(MyComponent)],
  }).compileComponents();
});

it('creates MyStandaloneComponent', () => {
  expect(() => MockRender(MyStandaloneComponent)).not.toThrow();
});

For this test, Angular throws the following error message:

Type MockOfMyComponent is part of the declarations of 2 modules: DynamicTestModule and MockOfMyModule! Please consider moving MockOfMyComponent to a higher module that imports DynamicTestModule and MockOfMyModule. You can also create a new NgModule that exports and includes MockOfMyComponent then import that NgModule in DynamicTestModule and MockOfMyModule..

Expected vs actual behavior
Expected behavior: no error.
Current workaround
Importing the module in the testing module config prevents the error:
  await TestBed.configureTestingModule({
    imports: [MyStandaloneComponent, MyModule],
    declarations: [MockComponent(MyComponent)],
  }).compileComponents();

(see Stackblitz)
It would still be great if this could be fixed, as the workaround may not be immediately apparent to the growing number of Angular devs using standalone components.
The need to import whole modules into standalone-component is quite a common scenario for an existing code base, at it allows to convert higher-order components into standalone components, but also for code using third-party modules that have not yet been converted to standalone components.

Hi there,
it's not a bug, its a wrong definition of the testing module, you'll get the same error without ng-mocks: https://stackblitz.com/edit/github-gzlejl-qzrk9z?file=src%2Ftest.spec.ts,src%2Ftest.ts,src%2Fmain.ts
If you want to keep MyModule and to mock MyComponent only, you should use MockBuilder:
beforeEach(() => MockBuilder([MyStandaloneComponent, MyModule], MyComponent));


merge 4.6 change back to master

Pull Request Test Coverage Report for Build 86609

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

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder/Adapters/TestFlow.cs
1
72.45%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs
2
75.0%

Totals

Change from base Build 86287:
0.0%

Covered Lines:
5767

Relevant Lines:
7436

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


✅ Replace object field types with specialized ones

Methods that return fields with object types

[ ] GetPreferences
[ ] GetSocialProfile
[ ] GetUserSettings
[ ] GetUserSummary
[ ] GetWellnessSleepData
[x] GetWellnessHeartRates
[x] GetWellnessStepsData
[x] GetHydrationData
[x] GetBodyComposition
[x] GetPersonalRecord
[x] GetDeviceLastUsed
[ ] GetDeviceSettings
[ ] GetDevices
[ ] GetActivitySplitSummaries
[ ] GetActivityDetails
[ ] GetActivityExcerciseSets
[x] GetActivityWeather
[x] GetActivitySplits
[x] GetActivityHrInTimezones
[x] DownloadActivity
[ ] GetActivities
[ ] GetActivitiesByDate

Hi,
I've integrated some of the "peloton-garmin" code into my app (not pretty at all, I just needed it to work asap, I'll try to review the code this weekend).
The authentication, getActivities and download activity is working fine. If you need, I can send you the code (a bit messy).
Best regards
Jorge Gregório


Managing transparent cyphertext

Hi everyone.
Is there a way to manage a transparent cyphertext?
I try to explain the use case:
Using two omomorphic operations like sum and negate I pickup the value x which is a ciphertex and I'll do
x + (-x)
this operation results in a runtime exception : RuntimeError: result ciphertext is transparent
is there a way to catch this exception?

@CastreseRiccio if you already know that you are operating x + (-x), why operate at all? You could instead encode a vector of zeros and the result would be identical.
Now, in the event that you had some legitimate reason to do that operation (I'd be curious of it), you can follow #124 to manually disable that exception. If you just want to "catch the exception" in Python, you could do something like:
try:
    #... your code with x +(-x)
except RuntimeError as e:
    if str(e)=='result ciphertext is transparent':
        print('I caught it!')
    else:
        raise e

Thank you both for your answers. @ibarrond i did a little implementation of an homomorphic "equals" that use sum and negate. it works like picking two cyphertexts, make a copy of one, negate it and then sum the two, if the result decrypted will be a vector of zeros it means that the two are equals. It works until i tried to equal the same cyphertext, then it give me the error, which is fine i only wanted to know if you already predicted a way to intercept this error as you show in your answer.


[SPARK-31135][TESTS] Upgrdade docker-client version to 8.14.1

What changes were proposed in this pull request?
Upgrdade docker-client version.
Why are the changes needed?
docker-client what Spark uses is super old. Snippet from the project page:
Spotify no longer uses recent versions of this project internally.
The version of docker-client we're using is whatever helios has in its pom.xml. => 8.14.1

Does this PR introduce any user-facing change?
No.
How was this patch tested?
build/mvn -Pdocker-integration-tests -pl :spark-docker-integration-tests_2.12 -Dtest=none -DwildcardSuites=org.apache.spark.sql.jdbc.DB2IntegrationSuite test`
build/mvn -Pdocker-integration-tests -pl :spark-docker-integration-tests_2.12 -Dtest=none -DwildcardSuites=org.apache.spark.sql.jdbc.MsSqlServerIntegrationSuite test`
build/mvn -Pdocker-integration-tests -pl :spark-docker-integration-tests_2.12 -Dtest=none -DwildcardSuites=org.apache.spark.sql.jdbc.PostgresIntegrationSuite test`

cc @dongjoon-hyun since you know this area well.

Test build #119718 has started for PR 27892 at commit 55731a7.

Can one of the admins verify this patch?

Thank you for pinging me, @gaborgsomogyi . Shall we have a JIRA ID?

@dongjoon-hyun thought it can be minor. Sure, creating one...

Filed https://issues.apache.org/jira/browse/SPARK-31135

Thank you!

Test build #119722 has started for PR 27892 at commit 9dde9ed.

Test build #119718 has finished for PR 27892 at commit 55731a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119718/
Test PASSed.

Test build #119722 has finished for PR 27892 at commit 9dde9ed.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119722/
Test PASSed.

Seems OK if it's going to just affect tests and tests work.

Thanks @dongjoon-hyun @srowen taking care! Also double checked 3.0 branch and works fine.


python3Packages.libpcap: init at 1.11.0b7

Description of changes
Adds the libpcap python package.
Depends on ~#249520~ & #249527
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux (cross compiled from x86_64-linux)
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

8 packages failed to build:

python310Packages.libpcap
python310Packages.libpcap.dist
python310Packages.pkg-about
python310Packages.pkg-about.dist
python311Packages.libpcap
python311Packages.libpcap.dist
python311Packages.pkg-about
python311Packages.pkg-about.dist

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

4 packages built:

python310Packages.libpcap
python310Packages.libpcap.dist
python311Packages.libpcap
python311Packages.libpcap.dist

@ofborg build python311Packages.libpcap python311Packages.libpcap.passthru.tests


CMake: fix version comparison

Hi again,
On CentOS 7, with CMake 3.7.2, I get the following issue:
CMake Error at cmake/compilerOptions.cmake:93 (include):
include could not find load file:

CheckLinkerFlag
Call Stack (most recent call first):
CMakeLists.txt:30 (include)

CMake Error at cmake/compilerOptions.cmake:94 (check_linker_flag):
Unknown CMake command "check_linker_flag".
Call Stack (most recent call first):
CMakeLists.txt:30 (include)

Thanks for reporting and fixing.


[BUG] one buyer token can be only used in associated data plane

Describe the bug
stage buyer token can be used in production and vice versa.
Expected behavior
one buyer token can be only used in associated data plane
Screenshots
n/a
Additional context
n/a

I use prod x-kraken-key token in staging env, still can send out api and get response.

pass


[Adreno] Optimize reduction schedule

Extend reduction through rfactor for reduction of big numbers of elements. In other case use previous straightforward approach.
Inject reduction postops into main reduction kernel

cc @masahi


doc: markdown transition fixes

Description of changes
https://github.com/NixOS/nixpkgs/issues/175586#issuecomment-1368012288 reported problem for downstream users of the docs infra. changes to the option factories shouldn't be controversial, but the change to _module.args is different. not sure whether this is a good way to solve the problem, very much open to other ideas.
should probably be backported to 22.11 in the end
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

A possible alternative to adding more *MD variants would be to treat mdDoc as a generic Markdown marker:

mkPackageOption pkgs (mdDoc "foobar")
mkAliasOptionModule [ "old" ] (mdDoc [ "new" ]) or something (this is probably terrible)

Independently from this PR, we probably want to make _module.*'s visibility opt-in anyway: see https://github.com/NixOS/nixos-search/pull/528. Standalone NixOS module docs like https://nix-community.github.io/home-manager/nixos-options.html don't really need to include _module.args. In fact I think ideally _module.* options should be documented somewhere in the main NixOS manual rather than in the "configuration options" annex. But for now, maybe we can just use specialArgs._moduleVisible and set _module.*.visible based on that?

I think we should try to keep it simple for two reasons

the markdown transition is a temporary state of affairs
_module is added to every module, including all submodules, so doing anything extra there will have a sizable performance impact

Also simple is good.
I'd be ok with hiding _module.args docs unconditionally for now, and enable it later. (Sorry @infinisil)

We should probably mention mkAliasOptionModuleMD and mkPackageOptionMD in the error message in mergeJSON.py

https://github.com/NixOS/nixpkgs/actions/runs/3843384881/jobs/6545596726
Manual checks are failing since this was merged.


Math system is bad

Your script isnt following the rules of math so you can come up with wrong results!

The newest version of script should follow the "PEMDAS" rule, so keep updating to the newest version of this rep ;)


Move bot messages to a new channel

As a developer, I want GitHub Discord messages to be moved into a new channel so that we can more easily separate developer messages from bot messages.

Bot messages are now going to the #bot channel in our Discord group.


Extend DataNode filter method to other formats

Description
The filter method on the data node class does filter the data only when the expose type is dataframe. This should be extended for every possible data node

The technical requirement documentation (WIP): https://docs.google.com/document/d/1tQyMz0XHzjcwG88o3eNA1Pop1EsE-jL1c42jsapUSyU


[TEST] feat(actions): add Dependabot workflow

Let's give it a try. The steps after the first haven't been executed so.... I dunno if it works.


Change file deletion from srm to xrd for FNAL plugin

Overseeds #6849 based on @hufnagel comments.
Still needs to:

be tested
be reviewed, Dirk, have a look please
clean zillions of pylint complaints
backported to 1.0.17_wmagent branch

test this please

It works fine. I ran a few workflows both at CERN and at FNAL. I'll merge it tomorrow, once I create the wmagent branch PR.
@hufnagel still, you're welcomed to have a look

Looks ok in general, but you should change xrd to xrdfs. The xrd tool is deprecated.

The xrd piece came from Dave :-) Is xrdfs supposed to have exactly the same behavior, options, etc than xrd?

Dirk, I'm merging this one such that we can cut a new wmagent release.
I suggest we follow the xrdfs work in a different patch, probably CERN plugin needs to be updated too, right? Would you like to take care of it? :-D


meta-tegra for a custom carrier board

Hi,
I have a custom carrier board from Neousys https://www.neousys-tech.com/en/product/product-lines/in-vehicle-computing/nru-51v-nvidia-jetson-nx-fanless-computer based on Jetson Xavier NX. I want to create an image which can be flashed onto this carrier board with all the peripherals configured appropriately. I am working with the vendor to provide support for the files needed like the bootloader or the device tree but I am not sure how to go about modifying or creating a new recipe to include those changes and build a new image for this custom carrier board
Any suggestions or thoughts would be greatly appreciated.
Regards
Naman

You could start with this wiki page.


Doodler with Color options

Link for Demo here:
https://singhkartikey679.github.io/Doodler/

Community Contribution
Link to live project, video, or image:

Sharing

[ ] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
Twitter:

Please do not add this. I am uploading again.


allow Envoy to be supplied custom routes to add to its Express routes

Make Envoy properly extensible by allowing custom Express routes to be supplied to supplement or override existing routes. i.e a third-party app can pass Envoy

its static directory of files
its list of routes

and Envoy will add them to its routing list.

+1


Error message when you run the "w32tm /resync" command to synchronize Windows Server 2003 or Windows SBS to an external time source: "The computer did not resync because no time data was available"

You need to add a space here between the /config and /manualpeerlist
If you run the w32tm /config /syncfromflags:manual command or the w32tm /config/manualpeerlist:peerlist command to determine whether Windows is configured correctly, the commands complete successfully.

I have fixed the typo. Thank you for the feedback.


Issues with VISA

Hey, I think there is an error in your enumerations,
Mollie.Enumerations.CreditCardLabel "Via", shouldn't that be "Visa"


Cannot Install Atheris using PIP on Ubuntu, Alpine, ArchLinux and Windows

I've tried installing(and building from source) Atheris using pip on fresh installs of all of the platforms listed above and get one of 2 errors:

error: [Errno 2] No such file or directory: '/tmp/pip-install-hhn1h51j/atheris_b195119dd32f487a9665296255a04b99/setup_utils/find_libfuzzer.sh'(with different hashes)
error: [WinError 193] %1 is not a valid Win32 application

While I could take time to figure out these errors and find workarounds for them, why should I?

I haven't been able to repoduce this on Linux (Ubuntu), can you confirm this is the expected error message for all of the listed platforms? Were you installing Atheris inside a virtualenv or globally? Did you try on MAC?

same issue here, i was using venv, tried doing pip3 install --no-binary atheris atheris to build the latest source as well, doesnt work (I have MSVC installed)

Uh oh, if multiple people have this issue I'll have to try harder to repro. I'm travelling this week but will try to repro this week or next, as best I can.

Got the same last error here but when building the wheel for Windows. I know on PyPI it states atheris is installable on systems with Linux and MacOS but are there any plans to extend support to Windows?

Didn't realize that this package was only available for unix, but I second the request for windows support. Was hoping to use this to fuzz windows-only endpoints using protobuf, but it looks like I'll have to look elsewhere in the meantime

It seems thats there are lots of requirements for windows support. We are hoping that the useful fuzzing package can be coducted for Window code. Could you help to have the plan to extend to Windows? Thanks so much for developibg the package.


Remove StorageFullException!

@ctsims says StorageFullException is completely useless, so let's take it out
Cross-requested with:
https://github.com/dimagi/commcare/pull/149
https://github.com/dimagi/commcare-odk/pull/550

Ready to go again. What I realized is that StorageFullException extends RuntimeException, hence it doesn't ever need to be in throws method qualifiers, nor do you need statements that catch it and throw a new RuntimeException. So I'm remove such uses of StorageFullException but leaving the rest in.


[AMBARI-25325] : RetryUpgradeActionService not updating host_role_command in Transaction (backport to branch-2.7)

What changes were proposed in this pull request?
non-public method in the same instance with guice @Transactional doesn't initiate Transaction at the beginning of the method and tear down after execution of the method. The same is the case with RetryUpgradeActionService updating host_role_command entries during Rolling Upgrade for commands with HOLDING_* failed status. Created a new Singleton class to offload the responsibility of creating Transaction using AOP proxy so that Transaction is applied to retryHoldingCommandsInRequest()
How was this patch tested?
The patch was tested manually during Rolling Upgrade as well as with unit testing available in RetryUpgradeActionServiceTest. Verified Transactional behavior with/without some Exception to Rollback/Commit the ongoing Transaction for both - before/after applying the patch
This is a backport PR to branch-2.7 from PR: https://github.com/apache/ambari/pull/3032

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5350/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5351/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5353/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5377/
Test FAILed.
Test FAILured.

The patch contains changes related to ambari-server module and has nothing related to metrics module failures.
3909411 [INFO] Ambari Main <IP_ADDRESS>.0 .............................. SUCCESS [  5.802 s]
3909411 [INFO] Apache Ambari Project POM <IP_ADDRESS>.0 ................ SUCCESS [  0.120 s]
3909412 [INFO] Ambari Web <IP_ADDRESS>.0 ............................... SUCCESS [04:53 min]
3909412 [INFO] Ambari Views <IP_ADDRESS>.0 ............................. SUCCESS [  3.629 s]
3909412 [INFO] Ambari Admin View <IP_ADDRESS>.0 ........................ SUCCESS [02:10 min]
3909412 [INFO] ambari-utility <IP_ADDRESS>-SNAPSHOT .................... SUCCESS [ 12.335 s]
3909413 [INFO] ambari-metrics <IP_ADDRESS>.0 ........................... SUCCESS [  0.437 s]
3909413 [INFO] Ambari Metrics Common <IP_ADDRESS>.0 .................... SUCCESS [ 27.443 s]
3909413 [INFO] Ambari Metrics Hadoop Sink <IP_ADDRESS>.0 ............... SUCCESS [04:33 min]
3909414 [INFO] Ambari Metrics Flume Sink <IP_ADDRESS>.0 ................ SUCCESS [ 12.056 s]
3909414 [INFO] Ambari Metrics Kafka Sink <IP_ADDRESS>.0 ................ SUCCESS [ 10.568 s]
3909414 [INFO] Ambari Metrics Storm Sink <IP_ADDRESS>.0 ................ SUCCESS [  8.013 s]
3909414 [INFO] Ambari Metrics Storm Sink (Legacy) <IP_ADDRESS>.0 ....... SUCCESS [  6.552 s]
3909415 [INFO] Ambari Metrics Collector <IP_ADDRESS>.0 ................. FAILURE [17:05 min]
3909415 [INFO] Ambari Metrics Monitor <IP_ADDRESS>.0 ................... SUCCESS [  4.446 s]
3909415 [INFO] Ambari Metrics Grafana <IP_ADDRESS>.0 ................... SUCCESS [  2.837 s]
3909415 [INFO] Ambari Metrics Host Aggregator <IP_ADDRESS>.0 ........... SUCCESS [ 22.913 s]
3909415 [INFO] Ambari Metrics Assembly <IP_ADDRESS>.0 .................. SKIPPED
3909416 [INFO] Ambari Service Advisor <IP_ADDRESS>-SNAPSHOT ............ SUCCESS [  0.545 s]
3909416 [INFO] Ambari Server <IP_ADDRESS>.0 ............................ SUCCESS [27:01 min]
3909416 [INFO] Ambari Functional Tests <IP_ADDRESS>.0 .................. SUCCESS [  0.916 s]
3909416 [INFO] Ambari Agent <IP_ADDRESS>.0 ............................. SUCCESS [01:50 min]
3909416 [INFO] ambari-logsearch <IP_ADDRESS>.0 ......................... SUCCESS [  0.151 s]
3909416 [INFO] Ambari Logsearch Appender <IP_ADDRESS>.0 ................ SUCCESS [  0.527 s]
3909417 [INFO] Ambari Logsearch Config Api <IP_ADDRESS>.0 .............. SUCCESS [  1.018 s]
3909417 [INFO] Ambari Logsearch Config JSON <IP_ADDRESS>.0 ............. SUCCESS [  0.173 s]
3909417 [INFO] Ambari Logsearch Config Solr <IP_ADDRESS>.0 ............. SUCCESS [  0.782 s]
3909417 [INFO] Ambari Logsearch Config Zookeeper <IP_ADDRESS>.0 ........ SUCCESS [  0.165 s]
3909417 [INFO] Ambari Logsearch Config Local <IP_ADDRESS>.0 ............ SUCCESS [  0.125 s]
3909417 [INFO] Ambari Logsearch Log Feeder Plugin Api <IP_ADDRESS>.0 ... SUCCESS [  0.255 s]
3909418 [INFO] Ambari Logsearch Log Feeder Container Registry <IP_ADDRESS>.0 SUCCESS [  1.278 s]
3909418 [INFO] Ambari Logsearch Log Feeder <IP_ADDRESS>.0 .............. SUCCESS [ 15.358 s]
3909418 [INFO] Ambari Logsearch Web <IP_ADDRESS>.0 ..................... SUCCESS [03:08 min]
3909418 [INFO] Ambari Logsearch Server <IP_ADDRESS>.0 .................. SUCCESS [ 22.153 s]
3909418 [INFO] Ambari Logsearch Assembly <IP_ADDRESS>.0 ................ SUCCESS [  0.131 s]
3909419 [INFO] Ambari Logsearch Integration Test <IP_ADDRESS>.0 ........ SUCCESS [01:10 min]
3909419 [INFO] ambari-infra <IP_ADDRESS>.0 ............................. SUCCESS [  0.040 s]
3909419 [INFO] Ambari Infra Solr Client <IP_ADDRESS>.0 ................. SUCCESS [  6.125 s]
3909420 [INFO] Ambari Infra Solr Plugin <IP_ADDRESS>.0 ................. SUCCESS [  3.601 s]
3909420 [INFO] Ambari Infra Manager <IP_ADDRESS>.0 ..................... SUCCESS [ 15.070 s]
3909420 [INFO] Ambari Infra Assembly <IP_ADDRESS>.0 .................... SUCCESS [  0.168 s]
3909421 [INFO] Ambari Infra Manager Integration Tests <IP_ADDRESS>.0 ... SUCCESS [  4.616 s]
3909421 [INFO] ------------------------------------------------------------------------

Retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5391/
Test FAILed.
Test FAILured.

This should resolve branch-2.7 metric failures: https://github.com/apache/ambari/pull/3043

Retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5394/
Test PASSed.

This should resolve branch-2.7 metric failures: #3043

After merging the above patch, now everything is Green for this patch
@jonathan-hurley


Changed from deprecated PropTypes to prop-types package to support React 16.0.0

Hello,
I changed so this package have a dependency on the "prop-types" package instead of getting the PropTypes from React. It is deprecated since a while back and PropTypes is removed in the full version for React 16.
Please accept this PR. Thanks!

react-native-swiper should be also updated in order to work with react 16.0.0.

@mckn would you mind including in that PR a revert back to the original react-native-swiper instead of @FuYaoDe which is not being maintained and affected by the same PropTypes issue with React 16?

@FuYaoDe could we get this merged?

@mckn I still get an error using this patch, related to react-native-swiper, not you?

Need this being merged... Thanks

Any update? merge asap please

I need this too.

👍 - but this PR is not enough.. the react-native-swiper also needs to be upgraded. This fork doesn't work w/ the original react-native-swiper`

MERGE PLZ

MERGE PLEASE!


Update README.md

zsh is the default shell for mac now, so we should write the nvm config to that.

Duplicate of #2417. Duplicate of #2300.


Incorrect plan output

Describe the Bug:
In the Floortile domain, there are only two available colors: black and white. However, the planning output incorrectly includes black2 in the precondition and effect of an action, which is not a defined color in the domain specifications.

To Reproduce:
https://editor.planning.domains/#
Use BWFS to solve the problem
Expected Behavior:
The plan should only include the colors "black" and "white" as these are the only two defined in the domain.
Observed Behavior:
The action in the generated plan mistakenly includes black2 in its precondition and effect, suggesting an error in the planning editor adaptor.

Which problem ID is this from?

Which problem ID is this from?

https://editor.planning.domains/#read_session=enUY7oRSpJSorry for the wrong link, just updated the reproduce session link. The problem id is P01-4-3-2.


What are all the settings available to restrict admob to display ads which is "Designed for families"

Hi there,
i'm also interested in that feature but from what I see it's on the TODO section of the README file.
@sbugert can you help us out and create/include this feature as well in this package?
Thanks

This is part of targeting, which is currently not implemented. See https://github.com/sbugert/react-native-admob/pull/166 for a WIP


render not working

g_pd3dRenderTarget always false xd
https://github.com/bruhmoment21/cs2-sdk/blob/main/cs2cheat/src/hooks/platform/win32/directx11_hook.cpp#L266

what happens in CreateRenderTarget?

g_pd3dRenderTarget always false xd https://github.com/bruhmoment21/cs2-sdk/blob/main/cs2cheat/src/hooks/platform/win32/directx11_hook.cpp#L266

are you on windows 11?

10, 21H2

g_pd3dRenderTarget always false xd https://github.com/bruhmoment21/cs2-sdk/blob/main/cs2cheat/src/hooks/platform/win32/directx11_hook.cpp#L266

are you on windows 11?

10, 21H2

idk im getting the same error, im gonna change the hook library to minhook and see if it works

static void CreateRenderTarget(IDXGISwapChain* pSwapChain) {
    ID3D11Texture2D* pBackBuffer = NULL;
    auto hr = pSwapChain->GetBuffer(0, IID_PPV_ARGS(&pBackBuffer));
    LOG("pSwapChain->GetBuffer: %u\n", hr);
    if (pBackBuffer) {
        DXGI_SWAP_CHAIN_DESC sd;
        hr = pSwapChain->GetDesc(&sd);
        LOG("pSwapChain->GetDesc: %u\n", hr);

        D3D11_RENDER_TARGET_VIEW_DESC desc = {};
        desc.Format = static_cast<DXGI_FORMAT>(
            GetCorrectDXGIFormat(sd.BufferDesc.Format));
        desc.ViewDimension = D3D11_RTV_DIMENSION_TEXTURE2D;

        hr = g_pd3dDevice->CreateRenderTargetView(pBackBuffer, &desc,
                                                  &g_pd3dRenderTarget);
        LOG("g_pd3dDevice->CreateRenderTargetView: %u\n", hr);
        pBackBuffer->Release();
    }
}

i cannot reproduce. are your gpu drivers old? whats ur gpu?

fixed it https://github.com/bruhmoment21/cs2-sdk/commit/873cb0588ffee4893b3fb8e066677426223c0099
does not happen for me no more
open if still persists


[Feature Request][move-analyzer] ctrl click in vscode to goto definition

🚀 Feature Request
Currently move-analyzer doesn't support goto implementation / definition for both functions, structs, and modules in either move-stdlib or aptos-stdlib or user-defined modules. It prevents new users / developers to quickly navigate codebases, so this feature request asks for VScode support for goto implementation / definition
Motivation
Is your feature request related to a problem? Please describe.
It's a common feature for rust-analyzer or other modular compiler frontend. it's high priority since it directly impacts developer
s onboard experience and code exploration speed.
Pitch
Describe the solution you'd like
use package_name::module_name: ctrl click on module_name should go to the file where module is defined.
use package_name::module_name::{Self, ModuleMembers}, : ctrl click on Self should go to the file where module is defined. ctrl click on ModuleMembers should go to the line where the member (e.g. a function, struct, or constant) is defined.
module_name::function_name: ctrl click on function_name should go to the file where the function is defined under module_name.
module_name::struct_name: ctrl click on struct_name should go to the file where the struct is defined under module_name.
module_name::const: ctrl click on const should go to the file where the const is defined under module_name.
The list potentially goes longer.
It might be as simple as https://stackoverflow.com/questions/35427666/how-to-implement-go-to-definition-extension-in-vscode
Describe alternatives you've considered

Are you willing to open a pull request? (See CONTRIBUTING)
Yes, but think someone more familiar with codebase would be better suited.
Additional context

This is already a feature. What issues are you having?
cc @awelc

This is already a feature. What issues are you having?
cc @awelc

This is indeed already a feature, but there are limitations due to certain parts of the parse tree not being preserved at the level of intermediate representation used to compute use-def information.
In particular, imports are no longer available (and, as such, are not supported). You also cannot go to the module definition using module name. All the other examples provided should work (navigating to function/struct/const definitions using function/struct/const name).
Please not that your code has to build (no compiler errors) for this functionality to be available as the required information is obtained from the compiler's intermediate representation.

@code-eren - any more feedback on this?

The use case is not supported currently.
moduel A::m{
    use B::m::Somestruct;

    fun test(a: SomeStruct){}
}

the Somestruct in 2 line could not goto while the Somestruct in the function signature can goto.

The use case is not supported currently.
moduel A::m{
    use B::m::Somestruct;

    fun test(a: SomeStruct){}
}

the Somestruct in 2 line could not goto while the Somestruct in the function signature can goto.

This is a known limitations and one which, unfortunately, will not be lifted any time soon... The reason for it is that import statements are not preserved at the level of compiler IR that is used to construct use-def information (and modifying the compiler just to support this particular feature is a rather low priority right now). I am sorry I don't have better news. I hope that otherwise the advanced features of the VSCode plugin are working now.


Better default Scheduler settings

Description of problem
The default scheduler settings on a clean install are not good for development and not for production.
Description of solution
The default scheduler settings should be set for best practices for production so that new sites get the best setting for runtime. E.g. site export/import should be OFF, site crawler less frequent, ...
Of course, settings can be different for sites and purposes, but the default should be mainstream correct out-of-the-box.
Description of alternatives considered
Create documentation in the DNN.DOCS and/or improve the help labels so that host/admins can make the right decision.
Currently, there is no documentation,
Screenshots
Default settings on a clean install

Additional context
There is a reference on DNNSoftware.com:
http://www.dnnsoftware.com/Content/Dnn.Platform/Documentation/Using the Control%2[…]/Host Console/Schedule/List of Scheduler Tasks.html
Affected browser

[X] Chrome
[X] Firefox
[X] Safari
[X] Internet Explorer
[X] Edge

Nice issue!  Thanks for creating it, @EPTamminga!  :)

Still relevant.


ci: use extism from git instead of latest

@nilslice I see you just reverted a commit like this in this repo, but I think leaving it set to build from git is what we actually want since this is very likely to keep happening.

Yea I was trying to get a quicker failure short-circuit since the build from source is several minutes. Eventually we can improve that for sure though.