[BUG] setuptools 71.0.3 vendored typeguard crash on Python 3.8: entry_points() got an unexpected keyword argument 'group'

setuptools version
71.0.3
Python version
3.8
OS
Linux (Ubuntu 20.04)
Additional environment information
No response
Description
The latest setuptools is still not working correctly on Python 3.8. In my case it crashes on Pytest initialization – see more information below.
It just used to work just fine two days ago with setuptools 70.3.0. It stopped working after the release 71.0.1 but that was yanked quickly. Unfortunately something is still not right in 71.0.3
Expected behavior
It just used to work just fine two days ago with setuptools 70.3.0.
How to Reproduce
I do not have exact or minimal reproduction steps yet but maybe the stacktace alone is sufficient for you to tell what the problem is. What I am doing is basically:

Use get-pip.py with on Python 3.8 (Ubuntu 20.04) to get pip. That also installs the latest setuptools.

Call pytest

Output
get-pip.py:
Installing pip in /tmp/venv...
Collecting pip
  Downloading pip-24.1.2-py3-none-any.whl.metadata (3.6 kB)
Collecting setuptools
  Downloading setuptools-71.0.3-py3-none-any.whl.metadata (6.5 kB)
Collecting wheel
  Downloading wheel-0.43.0-py3-none-any.whl.metadata (2.2 kB)
Downloading pip-24.1.2-py3-none-any.whl (1.8 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 9.9 MB/s eta 0:00:00
Downloading setuptools-71.0.3-py3-none-any.whl (2.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 24.2 MB/s eta 0:00:00
Downloading wheel-0.43.0-py3-none-any.whl (65 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 65.8/65.8 kB 6.3 MB/s eta 0:00:00
Installing collected packages: wheel, setuptools, pip
Successfully installed pip-24.1.2 setuptools-71.0.3 wheel-0.43.0

Then pytest:
(...)
  File "/tmp/venv/lib/python3.8/site-packages/_pytest/config/__init__.py", line 105, in main
    config = _prepareconfig(args, plugins)
  File "/tmp/venv/lib/python3.8/site-packages/_pytest/config/__init__.py", line 257, in _prepareconfig
    return pluginmanager.hook.pytest_cmdline_parse(
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/manager.py", line 84, in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/callers.py", line 203, in _multicall
    gen.send(outcome)
  File "/tmp/venv/lib/python3.8/site-packages/_pytest/helpconfig.py", line 90, in pytest_cmdline_parse
    config = outcome.get_result()
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/tmp/venv/lib/python3.8/site-packages/_pytest/config/__init__.py", line 836, in pytest_cmdline_parse
    self.parse(args)
  File "/tmp/venv/lib/python3.8/site-packages/_pytest/config/__init__.py", line 1044, in parse
    self._preparse(args, addopts=addopts)
  File "/tmp/venv/lib/python3.8/site-packages/_pytest/config/__init__.py", line 992, in _preparse
    self.pluginmanager.load_setuptools_entrypoints("pytest11")
  File "/tmp/venv/lib/python3.8/site-packages/pluggy/manager.py", line 299, in load_setuptools_entrypoints
    plugin = ep.load()
  File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 848, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmp/venv/lib/python3.8/site-packages/setuptools/_vendor/typeguard/__init__.py", line 48, in <module>
    load_plugins()
  File "/tmp/venv/lib/python3.8/site-packages/setuptools/_vendor/typeguard/_checkers.py", line 977, in load_plugins
    for ep in entry_points(group="typeguard.checker_lookup"):
TypeError: entry_points() got an unexpected keyword argument 'group'

It may not be actually an issue with setuptools. After looking a bit closed I think I know what the problem is – most likely this is because too old version of importlib_metadata is being installed as part of installing dependencies of the tests...

Yeah, apparently setuptools doesn't work correctly when too old importlib_metadata is installed together with it. I am not sure if this is expected that I was able to create such broken installation by just calling get-pip.py and then pip install -r requirements.txt but I'll close this bug as invalid anyway.


Matching IP Family for Outbound Listener

Title: Matching IP Family for Outbound Listener
Description:
To support dual stack in istio, for each service that has dual stack configured, two outbound listeners for the same port are created. One listener is with ipv6 wildcard with port and the other one is with ipv4 wildcard with port.
Here is what we expect:
client (ipv4 address ) -> ipv4 iptable redirect to 15001 -> envoy original dst at 15001 -> only match ipv4 wildcard <IP_ADDRESS>: listener
client (ipv6 address ) -> ipv6 iptable redirect to 15001 -> envoy original dst at 15001 -> only match ipv6 wildcard [::]: listener
However, in the connection_handler_impl.cc
it was not matching IP family type for the listener and target address.  Instead, it finds the first wildcard matching port from the listener list and it always returns that listener. This causes downstream client can use a different IP family listener from the original destination address. We think the code should match IP family and pick the corresponding wildcard listener based on the original destination IP family type.
ConnectionHandlerImpl::findActiveTcpListenerByAddress(const Network::Address::In
                    p.second.typed_listener_) &&
                p.second.listener_->listener() != nullptr &&
                p.first->type() == Network::Address::Type::Ip &&
-               p.first->ip()->port() == address.ip()->port() && p.first->ip()->isAnyAddress();
+               p.first->ip()->port() == address.ip()->port() && p.first->ip()->isAnyAddress() &&
+              ((p.first->ip()->ipv4() != nullptr && address.ip()->ipv4() != nullptr) ||
+               (p.first->ip()->ipv6() != nullptr && address.ip()->ipv6() != nullptr));
       });

With the above change, we tested with success of either IPv4 or IPv6 path.
kubectl exec -it -n test sleep-86786f67f4-s5bfm sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Defaulted container "sleep" out of: sleep, istio-proxy, istio-init (init)
/ # curl <IP_ADDRESS>:8090/headers
X-Request-Id: a6b06ffb-724b-4785-b490-039dbde0baee
X-B3-Spanid: c1d76544d090db82
Accept: */*
X-Envoy-Attempt-Count: 1
Content-Length: 0
X-Forwarded-Client-Cert: By=spiffe://cluster.local/ns/test/sa/simpleserver;Hash=01b9728bd23645e1afc39c96826cbec8b46c6427ac9b147b998935cdd2271adc;Subject="";URI=spiffe://cluster.local/ns/test/sa/sleep
X-B3-Traceid: 24c6d5522b6172d88f843df561d424d8
X-B3-Parentspanid: 8f843df561d424d8
X-B3-Sampled: 0
User-Agent: curl/7.76.1
X-Forwarded-Proto: http
remote addr: <IP_ADDRESS>:48372
host addr: <IP_ADDRESS>:8090
/ # curl simpleserver:8090/headers
X-Forwarded-Client-Cert: By=spiffe://cluster.local/ns/test/sa/simpleserver;Hash=01b9728bd23645e1afc39c96826cbec8b46c6427ac9b147b998935cdd2271adc;Subject="";URI=spiffe://cluster.local/ns/test/sa/sleep
X-B3-Spanid: ea96060aa7025f33
X-B3-Parentspanid: f5e7ec00645e238a
User-Agent: curl/7.76.1
Accept: */*
X-Forwarded-Proto: http
X-Request-Id: f6e2dcb1-664d-4f54-baa1-0d5ca615a562
X-Envoy-Attempt-Count: 1
Content-Length: 0
X-B3-Traceid: 872552dfa9f3c99bf5e7ec00645e238a
X-B3-Sampled: 0
remote addr: [::1]:58248
host addr: simpleserver:8090
ipv6 only server

This is important for us to enable dual mode support in Istio as we create routes/clusters based on whether IPv4 or IPv6 listener is picked.
Repro steps:

Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

Note: The Envoy_collect tool
gathers a tarball with debug logs, config and the following admin
endpoints: /stats, /clusters and /server_info. Please note if there are
privacy concerns, sanitize the data prior to sharing the tarball/pasting.
Attached the config_dump from istio.

Admin and Stats Output:

Include the admin output for the following endpoints: /stats,
/clusters, /routes, /server_info. For more information, refer to the
admin endpoint documentation.

Config:

Include the config used to configure Envoy.

Logs:

Envoy logs with added trace:

@nrjpoddar, @jacob-delgado

cc @howardjohn @mattklein123 @alyssawilk for inputs.

Good point. I can make the change.
BTW: Do you have a benchmark on the cost of the linear search? I have the feeling it hurts performance

We don't have a benchmark test on this.  It might be better to find the matching port listeners, then do a match on the ipaddress or wildcard with ip family.

Thanks @lambdai for your inputs. I was wondering about the linear search myself and I'm positive we can do better. However, I would like to get this bug fixed and tackle performance improvement separately if that's ok with you. Can we patch this in older versions of Envoy?

Great! @lambdai will you able to submit the fix in short order? We need this rather quickly as it blocks the dual-stack support in Istio. We would be happy to submit a patch too if you're busy.

This sounds reasonable to me. I might recommend putting this change behind a runtime flag though.

This sounds reasonable to me. I might recommend putting this change behind a runtime flag though.

Thanks Matt! Why do you suggest adding a runtime flag? I can’t think of situations where the current implementation of first wildcard match would be preferred instead of deterministic IP family wildcard match.

Thanks Matt! Why do you suggest adding a runtime flag? I can’t think of situations where the current implementation of first wildcard match would be preferred instead of deterministic IP family wildcard match.

I have no idea, but it strikes me as a change that could break someone. If you are sure this is impossible, we can proceed without it, but that seems risky to me as this is a behavior change to the matching.

Well, this falls into the category of users relying on incorrect existing behavior which is difficult to find out. At least in Istio, I know this won’t break anyone as we are still building out dual stack support. But since usage of Envoy is much broader, we can add a flag but make the new behavior default? I hope that’s acceptable.

Enabled by default is the default for runtime guards.

/backport


[BUG] Not a valid metric name when using statistics with brackets like 'PR(:10)'

Is there an existing issue for this?

[X] I have searched the existing issues

YACE version
0.61.2
Config file
discovery:
  jobs:
    - type: AWS/ELB
      regions:
        - eu-central-1
      period: 60
      length: 60
      dimensionNameRequirements:
        - AvailabilityZone
        - LoadBalancerName
      metrics:
        - name: Latency
          statistics: ["PR(:10)"]

Current Behavior
Shows error, like:
$ curl -s http://localhost:5000/metrics
An error has occurred while serving metrics:

4 error(s) occurred:
* "aws_elb_latency_pr(_10)" is not a valid metric name

Expected Behavior
Show metrics, like:
$ curl -s http://localhost:5000/metrics

aws_elb_latency_pr__10_{account_id="***...

Steps To Reproduce
No response
Anything else?
I've created the pull request - https://github.com/nerdswords/yet-another-cloudwatch-exporter/pull/1563
At least it works that way in my case.

licenses.md

$ curl -s http://localhost:5000/metrics
aws_elb_latency_pr__10_{account_id="***...

I'm closing this issue as the fix was accepted and merged.


Getting Forbidden 403 Error When Try Get Token

Hi, When i try to get token from 'https://android.clients.google.com' with correct user name and password server return 403 Error.
I am use link below code : https://github.com/kagasu/GooglePlayStoreApi/blob/master/GooglePlayStoreApi/GooglePlayStoreClient.cs
This problem happened two days ago. Where is the problem and how can it be resolved?

Everything similar to this project has died at same time.
this mean,  google decided reject old API, i think.
so, we have to re-implement new GetGoogleToken API.

What alternative should we use now? And where can I access to new Google Play APIs?

I'm released new version 1.0.3 now.
Please check again README.md

Thank you, but there is no better way to do it more professionally and automatically like before?

We have to get auth_token  from website at first time.
That website is complex, so i don't want to implement it.
If you want automatically get auth_token, write code your way using like Headless Chrome.
Also, GoogleToken looks like doesn't have expiry.
It is reusable.
First login
var token = "oauth2_4/...";
token = await client.GetGoogleToken(token);
// save token to "token.txt"
File.WriteAllText("token.txt", token);
await client.GetGoogleAuth(token);

Second login
// load token from "token.txt"
var token = File.ReadAllText("token.txt");
await client.GetGoogleAuth(token);

You may gain further insight from the analyses in this issue: https://github.com/NoMore201/googleplay-api/issues/98


Export of custom/non-SPDX license texts

Hey there,
is there a way to also export the license texts of the licenses associated with the components in the SPDX? In particular this refers to custom/non-SPDX license texts. Also license texts which have been modified compared to the template are relevant, e.g. an MIT with replaced placeholders. In the export I currently get a corresponding LicenseRef, but no extracted license texts. Is this somehow possible or planned to be added in future?
Thanks and regards
David Schumm<EMAIL_ADDRESS>on behalf of Daimler TSS GmbH.
Provider Information

Custom license text should be exported by default (see line 520 of process.py).
Licenses reported as SPDX standards are not exported with full license text currently.
If the script is not exporting custom license text then please raise a separate issue.


has_many :through with condition issue

Hello!
I am running into an issue whereI have a has_many :through relationship which has a condition on it.
class User < ActiveRecord::Base
  has_many :permissions
  has_many :applications, -> { where(permissions: { read: true }) }, :through => :permissions
end

class Api::UserResource < JSONAPI::Resource
  attribute :id

  key_type :uuid

  has_many :apps, :relation_name => :applications, :class_name => "Application"
end

In the Rails console using the ActiveRecord::Base class the application association works correctly and produces the following sql statement in the logs:
SELECT `applications`.* FROM `applications` INNER JOIN `permissions` ON `applications`.`uuid` = `permissions`.`application_id` WHERE `applications`.`deleted_at` IS NULL AND `permissions`.`user_id` = 'ea529c56-f274-11e4-3179-004a77f8b47f' AND `permissions`.`read` = 1

On the other hand when I am using the JSONAPI::Resource via an API endpoint I get the following in the log which obviously blows up:
SELECT `permissions`.* FROM `permissions` WHERE `permissions`.`read` = 1 AND `permissions`.`user_id` IN ('ea529c56-f274-11e4-3179-004a77f8b47f')

SELECT `applications`.* FROM `applications` WHERE `applications`.`deleted_at` IS NULL AND `permissions`.`read` = 1 AND `applications`.`uuid` IN ('ecc97fbf2be884557a17c46-01a5f6bc-088c-11e5-49c9-00712085a1eb', ...)

You will note, aside from this being two queries instead of one, the condition from the ActiveRecord::Base class is included in both statements despite the permissions table not being joined in on the second statement.
Is this type of association not supported? Am I just doing something wrong?
Thanks!

I guess a more accurate question, since I could rework my relationships to make this work, would be why is the JSONAPI::Resource making two queries instead of one with a join.

After some investigation it looks like this is more of an issue with the code base I am working in than an issue with this gem. The way the relationship is setup also does not work as an includes in pure ActiveModel usage. It only works if joins is also included.


Update protobuf-java to 3.18.1

Updates com.google.protobuf:protobuf-java from 3.17.3 to 3.18.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.protobuf", artifactId = "protobuf-java" } ]

labels: library-update, semver-minor

Superseded by #493.


code prettifying with prism.js?

I was planning on adding prism.js to my template and then wrap my code samples with  ~~~ .language-coffeescript to generate  but Techy is generating  - not quite sure where the extra lang- is coming from.
Then I noticed in the default theme prism.css and prism.js exist, does this mean you have already got prettified code snippets written in markdown, if so, what is the markdown syntax you are using?

Marked actually supports a 2nd method attribute that contains the language if supplied by the fenced block, check the commonmark docs at http://spec.commonmark.org/0.25/#example-109
So something like this might be possile:

marked.setOptions({
  highlight: function (code, language) {
    return Prism.highlight(code, Prism.languages[language]);
  }
});


e2e Cleanup - Tested Linted playbook

Signed-off-by: vijaysinghrawt1<EMAIL_ADDRESS>
What this PR does / why we need it:
Fix the ansible-lint errors in test-k8s-cassandra-pod playbook.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
@ksatchit please review this PR

Issue Type:
Resolving of ansible-lint errors in openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod
Ansible Version:
Ansible 2.5.0
Ansible Configuration:
None
Environment:
N/A
Expected Results:
Expect to have a file without ansible-lint error.
After resolving output
vijay@vijay-Satellite-C650:~/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod$ ansible-lint k8s-cassandra-pod-cleanup.yml
vijay@vijay-Satellite-C650:~/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod$
vijay@vijay-Satellite-C650:~/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod$ ansible-lint k8s-cassandra-pod-vars.yml
vijay@vijay-Satellite-C650:~/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod$
vijay@vijay-Satellite-C650:~/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod$ ansible-lint k8s-cassandra-pod.yml
vijay@vijay-Satellite-C650:~/openebs/e2e/ansible/playbooks/hyperconverged/test-k8s-cassandra-pod$


App tracking works on app store release but not on source code release

Hi
Using the source code for iOS from the website, the location does not update. However, if I use the app store release, it does. Does anyone know why this is, or what I am doing wrong? I'm probably doing something wrong (more likely, I'm very tired!)
Thanks

You can try to compile code from the latest tag:
https://github.com/tananaev/traccar-client-ios/releases/tag/v1.4

Tried using that code, still the issue occurs. It doesn't request access to the location if that helps? And in the status does not show any location failed or location sent...

It is the code that I used to build App Store version, so I don't understand how it's possible that App Store version works and your one doesn't.
App requests location in the following line, so you can try to put breakpoint and see if you it gets there:
https://github.com/tananaev/traccar-client-ios/blob/master/TraccarClient/ViewController.m#L93

Taken a look, still no changes and the breakpoints aren't really revealing anything. Were there any frameworks you added or something like that? I'm quite confused here as obviously it is the app store code, but the location dialog doesn't appear at all asking if I would like to allow the app to use the location?

I think it won't appear if you disable locations in the settings.

@tananaev tried with on and off, several devices and tried re-downloading code - definitely missing something on my end. Any suggestions as to things I could have missed myself?

Not sure what can go wrong there. The app is pretty simple. Maybe better to ask on StackOverflow because I'm not an iOS guru.

Can you let me know what version of Xcode you were using incase the frameworks are different?

I think I uses Xcode version 5. Don't remember minor version number.

@tananaev So glad you said that as that is what I suspected - I'll try with v5 and let you know as I think the location framework and syntax changed between 5 and 6 (or something like that...)

Compiling with Xcode 5.1.1 works and submits location.

I guess I need to update something if I want to release a new version. Thanks.


Clarify use of Valet Mode API

Add additional details to further explain the use of the Valet Mode API

Cleaned up a couple things. Thanks!


Add support for v3 and v5

Would it be possible to add support for generating v3 and v5 UUIDs? Code (PHP) can be found here:
http://jkingweb.ca/code/php/lib.uuid/

FYI, https://github.com/kelektiv/node-uuid/pull/188


Update to React v17.0.2

Description
⚠ Work in Progress

Updates to React v17.0.2
Fixes any Typescript Issues that arose in the update
I wanted to do MUI v5 and React 17 together but it was way too much to take on at once.

How to test

Test everything!
Check type changes I had to make

Good spot for us to run cypress tests


[Question] Can schema match the root nodes {"query" : "...", "operationName": ... ?

Before I go off and write Aeson FromJSON instances for the root nodes of the GraphQL specification (for POSTs with content type "application/json"), is there already a way to wrangle it out of the Object data type when writing the schema?
I want to follow the format given at GraphQL Post Request.
That is:
{
  "query": "...",
  "operationName": "...",
  "variables": { "myVariable": "someValue", ... }
}

where either operationName, namely, query or mutation, are nested under "query":.
Just making sure before I do it.

@sunwukonga https://github.com/jml/graphql-api/pull/128/files might be interesting. We haven't quite figured out yet what to do about the FromJSON for ConstScalar instance. As implemented in that PR it has some limitations, and because of that I'm a bit nervous about introducing a FromJSON instance that'll tie us down in what we can decode in the future.
I.e. I'd prefer a solution that's interpretJSONRequest and does the variable decoding based on the schema but I don't have a fully formed picture of what that would look like yet.
Does that make sense?

The schema may not be necessary, so long as I have all of the possibilities straight in my head. The only variable types we can get into the Query or Mutation Node are:
String        : A UTF‐8 character sequence.
ID            : a string, I presume the same as above, but not explicitly stated.
Enum          : a string, as above. (Often all-caps, but not sure this is 100% consistent).

Int           : A signed 32‐bit integer.
Float         : A signed double-precision floating-point value.

Boolean       : true or false.
Input Type    : Nested {}, making it easy to distinguish.

I considered Unions, but they don't go in any argument, which seems to be a condition for variable use. The problem: without context, there is ambiguity between the first three, and separately, between Int and Float.
However, with the QueryDocument, (particularly the selected operationName Node) we can distinguish instances of String and ID easily. Filtering down, all JSON strings that remain must be Enums. NB: no attempt is made to validate at this stage, i.e. search through the SchemaDocument for EnumTypeDefinition Name's that match our Enum input.
By the same mechanism, Int and Float can be easily distinguished from each other. And even scalar Date if it's implemented.
The good thing is that we will have access to the newly parsed QueryDocument and the operationName input by the time we are extracting values from variables, and I think we can use this information to correctly parse variables without leaving the block.
HC SVNT DRACONES -- These were my initial thoughts, you may cease reading. The first option is dodgey because it does what variables were instituted to avoid in the first place. String manipulation. It was also working under the assumption that the attoparsec parsing being done on the default value was doing the right thing [value :: Parser AST.Value](Line 136: Parser.hs), I think the matching for Enum should come before the matching for string, otherwise stringValue will gobble up anything that could be an Enum.
The second option below is much like @jml`s 3rd idea on the referenced PR. Really, I'm just leaving here for myself to read later. It can be safely ignored.
Possible solution 1:
What about inserting the variables into the query before we parse it? As we move down the structure from root, {query, operationName, variables} and BEFORE we start attoparsec-ing "query", we do a search and replace on the variables in the "query". Everything is then in it's context and gets parsed automatically without any further effort.
Under the assumption that we are already handling default variables properly. We can just insert the "variables" as default variables, i.e.
query HeroNameAndFriends($episode: Episode = "JEDI") {
  hero(episode: $episode) {
    name
    friends {
      name
    }
  }
}

over-writing existing defaults ^^^("JEDI" above), and appending everything else as a default value.
This would only need to be done for the incoming operationName (HeroNameAndFriends above ^^^) OR for the only operation name in the query, which ever it is. (What if there is no named operation? I don't know...)
A possible downside may be that it shifts the site of any errors encountered. It would not, for instance, tell you that your variable was bad, but rather that the field it had been inserted into was bad. Any error message would have to mention the dual possibilities. Mis-spelled variables might be haunting .
Possible Solution 2:
Add a new data type to:
 data ConstScalar
   = ConstInt Int32
   | ConstFloat Double
   | ConstBoolean Bool
   | ConstString String
   | ConstEnum Name
   | ConstWildCard String
   | ConstNull
   deriving (Eq, Ord, Show)

That is ConstWildCard Aeson.Value, which defers the real parsing until it is in it's proper context in the query.


bring back ignore in some form

Writing the heat_watcher test has made me realize that the ignore option is really nice for situations where you want to mock but not spy (in the heat_watcher example, I really don't want to be observing all of the calls to get_current_time) but this isn't possible at the moment.

I very much agree.
On Fri, Oct 23, 2015 at 2:31 PM, Erik<EMAIL_ADDRESS>wrote:

Writing the heat_watcher test has made me realize that the ignore option
is really nice for situations where you want to mock but not spy (in the
heat_watcher example, I really don't want to be observing all of the calls
to get_current_time) but this isn't possible at the moment.
—
Reply to this email directly or view it on GitHub
https://github.com/necula01/bond/issues/18.

This was added in commits f316761 (Python) and fe9dc80 (Java, Ruby) via the mock_only option on spy points.


Remove app restriction incorrect limitations/response

The following is not documented as a limitation or response:
When you send multiple API calls to remove app restriction for the same device, there are inconsistent results. It may depend on how much time has passed since you last issued the associated API call. Some duplicate calls returned the pending machine action instead of a new machine action and some duplicate calls returned HTTP 400 with the message "Action is already in progress".

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 70c49ba4-b953-8b93-6e2e-76eb68d26e4a
Version Independent ID: 32830f76-070c-f0cb-6cab-988ae8504731
Content: Remove app restriction API
Content Source: microsoft-365/security/defender-endpoint/unrestrict-code-execution.md
Product: m365-security
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@MastaDisasta Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5993
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @MastaDisasta Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Bumping up pom file hadoop version

Hadoop version was recently changed to 3.0.0-alpha4 while services-api and slider pom files were compiled against hadoop3.0.0-alpha3
This PR is bumping up hadoop version to avoid compilation issues.

Thanks @pgaref for the PR and it looks good to me. Would you file a issue as a sub-task of https://issues.apache.org/jira/browse/YARN-5079 ?

Sure @aajisaka , I just submitted a patch.

I've committed this to yarn-native-services branch. Would you close this PR?

Sure thanks!


Installation Issue

I seem to be having a issue with npm install.
root@BTCPayServerVM:/home/elementsprojects/nanopos# npm install
root@BTCPayServerVM:/home/elementsprojects/nanopos# npm start

<EMAIL_ADDRESS>start /home/elementsprojects/nanopos
./start.sh

npm ERR! weird error 1
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! not ok code 0
root@BTCPayServerVM:/home/elementsprojects/nanopos# npm install
root@BTCPayServerVM:/home/elementsprojects/nanopos# npm start

<EMAIL_ADDRESS>start /home/elementsprojects/nanopos
./start.sh

npm ERR! weird error 1
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! not ok code 0

Hi @JonnyMaK, this looks like it might be an error with your nodejs installation. Can you try running the two following commands from the nanopos directory and see if they work as expected?
$ node -e 'console.log("works")'
$ ./node_modules/.bin/babel-node -e 'console.log("works")'

If they do, can you please check and report your nodejs version too (via $ node -v)?

I figured it out. I needed to get curl to point at version 9
Then the install was fine.
There was also an issue with npm, so I reinstalled that with aptitude

Great! Glad to hear you worked this out.


python310Packages.{jaxtyping,equinox}: update

Description of changes
Update jaxtyping and equinox.
Things done

Built on platform(s)

[ ] 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
[ ] 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.

I have the following problem when building python310Packages.jaxtyping.passthru.tests:
Finished executing pythonRemoveTestsDir
running install tests
no Makefile or custom installCheckPhase, doing nothing
pythonCatchConflictsPhase
/nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  import pkg_resources
Found duplicated packages in closure for dependency 'jaxtyping':
  jaxtyping 0.2.23 (/nix/store/kmmqy0r284j5k7db70dinjxrx44kxmsq-python3.10-jaxtyping-0.2.23/lib/python3.10/site-packages)
  jaxtyping 0.2.23 (/nix/store/4l4jcgl3idx2hry5y5i72i16fhspdlir-python3.10-jaxtyping-0.2.23/lib/python3.10/site-packages)

Package duplicates found in closure, see above. Usually this happens if two packages depend on different version of the same dependency.

diff LGTM

Unfortunately, the tests of jaxtyping fail because of a collision between two "variation" of the jaxtyping` derivation ending in the python environment.
I don't get why it starts to pause a problem now...

Hmm quick thoughts:

Has anyone else packaged their own jaxtyping as a vendored part of a larger package?
Are there multiple instantiations of jaxtyping in the transitive closure of the test dependencies? This could happen by eg one depending on jaxlib with cudaSupport = true and another with cudaSupport = false.

It seems that it is the fault of equinox. Updating equinox alone breaks jaxtyping.tests.

The only change in the equinox derivation besides the version bump is the addition of optax in the nativeCheckInputs.
However, removing it (as well as the tests that depend on it) doesn't solve our duplication problem.

Haha it is actually broken on master as well !
You can then merge this PR @samuela: it doesn't worsen the situation.

roger that, done! thanks @GaetanLepage !


[Solved] text on image #09 by Greeshma c20084146 patch 3

[Solved] text on image #09 by Greeshma c20084146 patch 3 #851
Greeshma-C20084146:Greeshma-C20084146-patch-3

Heartfelt Thanks for Your Contribution to Our Open Source Project!
            Dear @Greeshma-C20084146,

            I trust this message finds you in good health and high spirits. I am reaching out with a heart full of gratitude for your recent contribution to our open source project. Your dedication has not only elevated the functionality of our project but has also exemplified the collaborative spirit that lies at the core of thriving open source communities.

            A heartfelt congratulations are in order for your exceptional work! Your commitment and expertise have played a pivotal role in the success of our project, and we consider ourselves truly fortunate to count you among our community members.

            I must extend my sincere apologies for the delay in responding to your pull request. Your patience and understanding during this time are immensely appreciated. As our project continues to grow, we acknowledge the imperative need to enhance the quality and response time for contributions. To address this, we've kickstarted a call for maintainers and reviewers who can help us uphold the high standards of our project and ensure swift responses to pull requests.

            Your involvement and insights would be invaluable in this initiative. If you, or someone you know, is interested in taking on a more active role in the project, please don't hesitate to reach out. We firmly believe that with a robust team of maintainers and reviewers, we can elevate both the quality of the project and the speed of our responses.

            On an exciting note, I am thrilled to share that we have activated the sponsorship button for our project. This development allows supporters like yourself to contribute to the sustainability and growth of the project. Your ongoing support, whether through code contributions or sponsorship, is genuinely appreciated.

            Once again, congratulations on your outstanding contribution, and thank you for being an indispensable part of our open source community. We eagerly anticipate your continued collaboration and shared success.

            Best regards,

            Ntem Kenyor K.
            Lead
            Kwickerhub


GMSH curved meshes support

Thanks to Daniel and everyone involved for bringing the wonderful GMSH mesh support to Trixi in https://github.com/trixi-framework/Trixi.jl/pull/1799!!
I am unable to get the current parser to handle a GMSH generated mesh with curved boundaries. Here is how I generate a curved mesh with GMSH (I only know how to do it with GUI at this moment). I tried this with NACA6412.geo available here and another one here

Open the .geo file in GMSH
Click Modules -> Mesh -> 2D (Generates the straight sided mesh)
Click Modules -> Mesh -> Set order 2 (curves the mesh boundary to be order 2. Higher is also possible)
File -> Export -> mesh_NACA6412.inp, making sure to tick "Save all elements" and "Save groups of nodes" (Exporting with these options ticked is the step I cannot do via command line)

If I skip step 2, the parser can handle it fine and I am able to run the available elixir https://github.com/trixi-framework/Trixi.jl/blob/main/examples/p4est_2d_dgsem/elixir_euler_NACA6412airfoil_mach2.jl. However, if I try to run same the elixir when I did the above step 2 to curve the mesh, I get a segmentation fault in the line that reads the mesh, i.e., mesh = P4estMesh{2}(mesh_file, polydeg = polydeg, boundary_symbols = boundary_symbols)
It starts with
[p4est] No elements or nodes found in mesh file.
[p4est] Failed to read /home2/arpit/repositories/cloned/Trixi.jl/examples/p4est_2d_dgsem/NACA6412_curved.inp: pass 1

Full error message
P4est segmentation fault
[p4est] No elements or nodes found in mesh file.
[p4est] Failed to read /home2/arpit/repositories/cloned/Trixi.jl/examples/p4est_2d_dgsem/NACA6412_curved.inp: pass 1

[595759] signal (11.1): Segmentation fault
in expression starting at /home2/arpit/repositories/cloned/Trixi.jl/examples/p4est_2d_dgsem/elixir_euler_NACA6412airfoil_mach2.jl:78
unsafe_load at ./pointer.jl:119 [inlined]
unsafe_load at /home2/arpit/.julia/packages/P4est/0rTeV/src/pointerwrappers.jl:86 [inlined]
getindex at /home2/arpit/.julia/packages/P4est/0rTeV/src/pointerwrappers.jl:82 [inlined]
getindex at /home2/arpit/.julia/packages/P4est/0rTeV/src/pointerwrappers.jl:82 [inlined]
p4est_mesh_from_standard_abaqus at /home2/arpit/repositories/cloned/Trixi.jl/src/meshes/p4est_mesh.jl:460
#_#279 at /home2/arpit/repositories/cloned/Trixi.jl/src/meshes/p4est_mesh.jl:376
P4estMesh at /home2/arpit/repositories/cloned/Trixi.jl/src/meshes/p4est_mesh.jl:353
unknown function (ip: 0x7f420e7c66a0)
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
do_call at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:126
eval_value at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:223
eval_stmt_value at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:174 [inlined]
eval_body at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:617
jl_interpret_toplevel_thunk at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:775
jl_toplevel_eval_flex at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:934
jl_toplevel_eval_flex at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:877
ijl_toplevel_eval_in at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:985
eval at ./boot.jl:385 [inlined]
include_string at ./loading.jl:2070
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
_include at ./loading.jl:2130
include at ./client.jl:489
unknown function (ip: 0x7f420e7b5b55)
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
do_call at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:126
eval_value at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:223
eval_stmt_value at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:174 [inlined]
eval_body at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:617
jl_interpret_toplevel_thunk at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/interpreter.c:775
jl_toplevel_eval_flex at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:934
jl_toplevel_eval_flex at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:877
jl_toplevel_eval_flex at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:877
jl_toplevel_eval_flex at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:877
ijl_toplevel_eval_in at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/toplevel.c:985
eval at ./boot.jl:385 [inlined]
eval_user_input at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:150
repl_backend_loop at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:246
#start_repl_backend#46 at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:231
start_repl_backend at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:228
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
#run_repl#59 at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:389
run_repl at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:375
jfptr_run_repl_91689.1 at /home2/arpit/.local/julia-1.10.0/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
#1013 at ./client.jl:432
jfptr_YY.1013_82677.1 at /home2/arpit/.local/julia-1.10.0/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
jl_f__call_latest at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/builtins.c:812
#invokelatest#2 at ./essentials.jl:887 [inlined]
invokelatest at ./essentials.jl:884 [inlined]
run_main_repl at ./client.jl:416
exec_options at ./client.jl:333
_start at ./client.jl:552
jfptr__start_82703.1 at /home2/arpit/.local/julia-1.10.0/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
true_main at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/jlapi.c:582
jl_repl_entrypoint at /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/jlapi.c:731
main at julia (unknown line)
__libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x4010b8)
Allocations: 25176877 (Pool: 25169453; Big: 7424); GC: 90
Segmentation fault

Note that the .geo file does have enough information to curve the mesh, see images in spoilers below. Here is gmsh showing a straight sided mesh

Straight sided GMSH mesh

The curved airfoil already indicates that it is possible to curve the mesh. And, by setting a high order with Set order 3, I get

 GMSH mesh of order 3

`HOHQ` generated meshes also give curved boundaries already.
Here is a gist with .inp file generated with curved boundaries - https://gist.githubusercontent.com/Arpit-Babbar/d9238c194b3e87574fdcbbd39fa59180/raw/6c985a65b58e5eda38630b6a8d3e54652293650a/NACA6412_curved.inp
Here is a gist with .inp file generated with straight sided boundaries - https://gist.githubusercontent.com/Arpit-Babbar/f4271dc9c57724bf62681c725aa16cd6/raw/e83e50d4f67ee1853f189d6b7269e8fb1cde5ab0/NACA6412.inp

Can you post the .inp file that gmsh generates are you curve it? It would be helpful to see what the curved ABAQUS file format looks like.
The issue is with the creation of the connectivity versus the curvature. The connectivity is handled by p4est which can only handle straight-sided elements, as discussed briefly here. The curving of the mesh is handled internally within Trixi. We just need to work out how to read this boundary point data into appropriate arrays in order to create the boundary interpolants and compute the metric terms.

Can you post the .inp file that gmsh generates are you curve it? It would be helpful to see what the curved ABAQUS file format looks like.

Here a gist with .inp file generated with curved boundaries - https://gist.githubusercontent.com/Arpit-Babbar/d9238c194b3e87574fdcbbd39fa59180/raw/6c985a65b58e5eda38630b6a8d3e54652293650a/NACA6412_curved.inp
Here is a gist with .inp file generated with straight sided boundaries - https://gist.githubusercontent.com/Arpit-Babbar/f4271dc9c57724bf62681c725aa16cd6/raw/e83e50d4f67ee1853f189d6b7269e8fb1cde5ab0/NACA6412.inp

The issue is with the creation of the connectivity versus the curvature. The connectivity is handled by p4est which can only handle straight-sided elements, as discussed briefly here. The curving of the mesh is handled internally within Trixi. We just need to work out how to read this boundary point data into appropriate arrays in order to create the boundary interpolants and compute the metric terms.

I see, thanks for sharing that!

This strategy of having p4est create and manage the connectivity and Trixi handle the curvature was the reason for the special .inp mesh file format for HOHQMesh, see here. Basically, all the curved boundary information is encoded as comments in the ABAQUS format such that the p4est parser ignores it and we can let Trixi handle everything curved boundary related.

We just need to work out how to read this boundary point data into appropriate arrays in order to create the boundary interpolants and compute the metric terms.

That would actually be a nice student project for which relatively little knowledge on math is required!


Update state render

In response to #84.
Summary
React warnings were emitted about an invalid state update. I think it is because there was a state update somewhere in the tree caused during the render method of <Translate />. <Translate /> called addDefaultTranslation() during the render phase and I think this was the source of the problem.
My suggested solution is to remove the call to addDefaultTranslation() from the render phase of Translate, and call it once on mount, and subsequently every time the id prop changes (#79).
Before

Translate mounts with state:

state = { hasAddedDefaultTranslation: false, lastKnownId: '' }

static getDerivedStateFromProps() runs to determine when the id prop changes. Whenever this prop changes, it resets the state.hasAddedDefaultTranslation flag.
render() is called and subsequently calls addDefaultTranslation(), which will decide what to do based on the current state.

After

componentDidMount() calls addDefaultTranslation().
componentDidUpdate() calls addDefaultTranslation() if the id prop has changed.
No calls to addDefaultTranslation() in the render phase.

Moving the Consumer
Previously, the render phase was called with the LocalizeContext.Consumer which provided the context object needed in addDefaultTranslation. Since this is not happening anymore, I have had to move the Context Consumer one level up, and pass context down as a Prop to Translate. This means the public-facing Translate component is no longer the original one, but the original one wrapped in LocalizeContext.Consumer. This way the entire WrappedTranslate (i.e. the original Translate) has access to context and we can successfully call addDefaultTranslation at any point in the life cycle. I'm not sure if this affects performance?
I don't know how to write an effective test for this... The particular error seems to be either not triggered or suppressed in some way in the current tests. However, the error is reproducible in the demo project, and it can be verified as gone with this change by building the demo project with the parent directory as the react-localize-redux dependency.

Thanks for all the detail it really helps. In terms of performance, I don't foresee any issues with the wrapper component.
A couple of small things:

I think the type definitions in index.d.ts and index.flow.js need to be updated for Translate to reflect this change. Let me know if you need help with that.
I wouldn't even bother exporting WrappedTranslate unless it's needed for testing purposes.
Now that you've removed getDerivedStateFromProps from Translate I think we can bump down the peerDependency in package.json back to react: 16.0.0.

So if the issue can't be captured in a test I'm guessing you've confirmed this fix solves the issue in the demo as you mentioned? I just want to confirm.

@ryandrewjohnson latest update:

I'm not sure if the definitions do need to be updated, since the new Translate component still accepts the same props and renders the same children as before. The only difference is that WrappedTranslate has an additional context prop, but since this component is private, I don't think any existing definitions need changing.

I've removed the export of WrappedTranslate and changed the peerDependency as suggested.

I have confirmed that the issue no longer presents itself via the demo project. Note that I tested this by setting the react-localize-redux dependency as my local copy in the demo, so even after this PR, the demo should continue to show the error, until it can point to a fixed version of react-localize-redux.

I think the flow type def is fine, but the typescript def in index.d.ts should probably be updated as it's no longer exporting a class.
Current:
export class Translate extends ReactComponent<TranslateProps> {}

It should now probably export a function similar to the withLocalize definition.

Good point. I typed it as a React.SFC since it is technically now a stateless functional component.

Great work on this one! I've merged it in for now, but will publish tomorrow when I have some time. Don't want to rush it at the end of the night as that's usually when I end up breaking something 😬


Function to test values

The idea: to make a function to check the types of values. For example, for the numbers, floating point numbers, or Boolean values.
This will improve the code of the programs significantly.

Also, it would be convenient to make some kind of modifier, if you need to execute the command from the administrator.

Add a similar function to retrieve data from the user.
def input() {
    @(read t);
    return t;
}

somevar = input();


Tweaked logging format to more closely match the default Tomcat standard

From: debug: 2016-08-03 10:48:40 [PRODUCT] Message: {}
To:[PRODUCT] [DEBUG] 2016-08-02T15:44:13.357Z Message

LGTM

This is a patch-release that has been applied to an older version, as such it won't be merged into master. A separate PR will be raised to apply the new logging format into the master branch.


[Fabric 1.14.4, IP 0.20 and before] Portals floating

I'm not entirely sure what vanilla would do here, but it's quite unsatisfying.

This is technically not floating but there is no block in front of the portal which IIRC is prevented by vanilla selection.

The first one is normal, I intentionally made portal sometimes generate above lava lake. But the second one is a bug.

The second one will probably not appear in 0.21

And it's still possible to generate the portal above lava lake


WIP: gpsbabel: Fix build with qt59

Motivation for this change
Fixes build with Qt 5.9, some tests fail.
@rycee Could you take a look?
See Qt  5.6 deprecation issue
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@rycee I have looked through the codebase a bit and noticed some fixes in upstream related to rounding issues (https://github.com/gpsbabel/gpsbabel/pull/146).
I think this may be related.

I tried applying these precision patches but they seem to rely on other commits. So I tried building gpsbabel master, which resulted in similar (but different) precision errors.
I also tried building with Qt 5.9 without any luck :-(
@GrahamcOfBorg build gpsbabel

Failure on aarch64-linux (full log)
Partial log (click to expand)
Running ./testo.d/wintec_tes.test
Running ./testo.d/xcsv.test
Running ./testo.d/xmap.test
Running ./testo.d/xmapwpt.test
Running ./testo.d/xol.test
Running UTF-8 BOM test
Running well-formed XML test
make: *** [Makefile:190: check] Error 15
builder for '/nix/store/xg7yikhg7c2snzzkbz0jxjq00pzmsp49-gpsbabel-1.5.4.drv' failed with exit code 2
error: build of '/nix/store/xg7yikhg7c2snzzkbz0jxjq00pzmsp49-gpsbabel-1.5.4.drv' failed

Failure on x86_64-linux (full log)
Partial log (click to expand)
Running ./testo.d/wintec_tes.test
Running ./testo.d/xcsv.test
Running ./testo.d/xmap.test
Running ./testo.d/xmapwpt.test
Running ./testo.d/xol.test
Running UTF-8 BOM test
Running well-formed XML test
make: *** [Makefile:190: check] Error 15
builder for ‘/nix/store/qy85vg1zsh4fdn4bhshjmbima50kpdm5-gpsbabel-1.5.4.drv’ failed with exit code 2
error: build of ‘/nix/store/qy85vg1zsh4fdn4bhshjmbima50kpdm5-gpsbabel-1.5.4.drv’ failed

@adisbladis Ok, since other distros don't seem to be too concerned about these failing tests, perhaps just disable the failing tests or disable the test suite all together?

I'm not feeling to good about these patches. Not sure what other subtle behaviour breaks.
I think we'll wait for upstream to make another release.


cvtPdfToJson step does not seem to be recognizing some hourly cells

The cvtPdfToJson step seems to be adding multiple instances of an hour, causing a data issue.
As an example the 03.27.2019 data for ATL shows 7 Pax for the Main Checkpoint at 01:00, and 16 Pax for the 02:00 hour. The TSAThroughputApp is instead creating two 01:00 nodes for the ATL Main Checkpoint instead of creating a 02:00 node.
This throws off the numbers. I'm unsure as to how many airports/rows this is affecting at this time. The result is an "undercount", since the cvtJsonToCsv step averages the two hours. In the example above the 01:00 hour would show up as (7 + 16) / 2 = 11.5

After researching this. It appears that the form-recognizer is not interpreting the column for 02:00. This issue is similar to the one I reported to microsoft for the 2.1 recognizer. But it also appears to occur in this version as well.
https://docs.microsoft.com/en-us/answers/questions/577259/form-recognizer-change-in-behavior-in-21-vs-20-rec.html


Separate suffix with colon in inline citation

Citing two authors inside the same parenthesis works very nicely.Tthey only need to be separated by a semicolon: [@Author1; @Author2]
Separating a suffix with a semicolon from the actual citation is not possible: [@Author1; see also fig. 1]
Is there a way to achieve this?

Yes, backslash-escape the semicolon.
[@Author1\; see also fig. 1]


Debian 10 installation of Azure Functions Core Tools v4

The documentation states that I should be able to install azure functions core tools v4 on Debian 10,
but I was able to do that for v3 only:
E: Unable to locate package azure-functions-core-tools-4

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b2646ad4-34b7-fc5e-dcc9-d53a061df394
Version Independent ID: bbff4fda-24e4-2b62-24b9-94cda5f53bed
Content: Work with Azure Functions Core Tools
Content Source: articles/azure-functions/functions-run-local.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hello @reflash - Thank you for your feedback! We will review and update as appropriate.

Getting the same error on multiple Debian and Ubuntu distros. Doesn't look like v4 tools are released to apt yet.

@reflash they've published v4 to apt 9h ago so you can try again.

@reflash , Are you still facing the error with latest V4?

@reflash , just wanted to check if you are still facing the issue with latest V4. Please let me know

@MughundhanRaveendran-MSFT just checked it now. Installation goes fine, thanks!

@reflash , Thanks for the update.


fix(toast): remove margin

Description
Removed unnecessary left margin on toast. It is not needed as gap is being used.
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Since this causes a visual change, I've put a first-child selector instead, so it only applies the margin if a button actually exists inside the element.


ActivatorUtilities factory NRE when argument default value is new Struct() expression

Hello.
Code below raise exception
(
third operation constructor call you may remove redirection and leave only Index action just refresh page two times
)

An unhandled exception occurred while processing the request.
NullReferenceException: Object reference not set to an instance of an object.
lambda_method(Closure , ServiceProvider )

namespace WebApplication1
{
	public class Startup
	{
		// This method gets called by the runtime. Use this method to add services to the container.
		// For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940
		public void ConfigureServices(IServiceCollection services)
		{
			services.AddMvc();
			services.AddTransient<IOperation, Operation>();
		}

		// This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
		public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
		{
			loggerFactory.AddConsole();

			if (env.IsDevelopment())
			{
				app.UseDeveloperExceptionPage();
			}

			app.UseMvcWithDefaultRoute();

			//app.Run(async (context) =>
			//{
			//	await context.Response.WriteAsync("Hello World!");
			//});
		}
	}

	public class HomeController : Controller
	{
		IOperation _operation;
		public HomeController(IOperation operation)
		{
			_operation = operation;
		}

		public async void Index2() => await ControllerContext.HttpContext.Response.WriteAsync(_operation.OperationId.ToString());

		public IActionResult Index1() => RedirectToAction("Index2", "Home");

		public IActionResult Index() => RedirectToAction("Index1", "Home");

	}

	public interface IOperation
	{
		Guid OperationId { get; }
	}

	public class Operation : IOperation
	{
		public Operation(Guid guid = new Guid()){		}
		//public Operation(int y = 0) { }  // this work

		public Guid OperationId => Guid.NewGuid();
	}

}

/cc @pakrym

Caused by https://github.com/dotnet/corefx/issues/11797

cc @rynowak - we would have the same issue in Mvc too.

https://stackoverflow.com/questions/22912021/exception-at-initialization-of-datetime


Backend/route to set username

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[x] Lint (yarn lint --check) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Closes #40
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Just needs conflict resolution for the lockfile


Add design note on GPIO node enhancements

The GPIO node provide an easy way to control hardware using Node-RED.
However, there are some cases where it is difficult to control certain types of hardware using current GPIO node.
Therefore, this proposal aims to extend the GPIO node to meet such requirements.

Another comment. When you select "advanced mode" - then presumably the existing pin selection UI would need to disappear - as selecting single pins is not valid anymore - and be replaced by what ? I think that would be simply too jarring for users. It is not as-if you can switch and have your existing settings carried forwards - and vice versa back again... it really is a different node.

Thank you for your review comment.
Sorry, I missed the first comment.

What happens if you have an existing (basic mode) node set to pin 7 and this send an array that includes pin 7 ?

The current assumption is that unexpected input will cause an error.

I still think that the whole advanced modes of operation of this proposal are very significantly different from the basic mode, and should be in a separate "professional" node rather than added to this one.

I understand your opinion.
Our users (and maybe other users) use the current GPIO node and are familiar with its specifications, so we would like to be able to extend current node or make upward compatible nodes.

It would also allow the node to be based on a different underlying library that may be more performant that the current pipe to python script, which would help PWM and also allow servo timing modes that the current node cannot support.

Yes. I think moving to a better library is one way to go.  However, as I mentioned before, RPi.GPIO can also be used on other platforms that we use, so it would be nice if we could make it selectable.

Another comment. When you select "advanced mode" - then presumably the existing pin selection UI would need to disappear - as selecting single pins is not valid anymore - and be replaced by what ? I think that would be simply too jarring for users. It is not as-if you can switch and have your existing settings carried forwards - and vice versa back again... it really is a different node.

As for the UI, you're right, I'm currently envisioning hiding the settings as seen on other nodes, or greying them out to make them unselectable.

Our users (and maybe other users) use the current GPIO node and are familiar with its specifications, so we would like to be able to extend current node or make upward compatible nodes.

My worry is that this is not a simple extension of the node - as soon as you turn on the advanced behaviour - it is

a) not longer compatible with the old modes
b) the new specification are nothing like the old ones so users would not be able to bring forwards their familiarity at all as they bear very little relationship with the old,
c) can't be a drop in upgrade as even the most basic msg.payload are now complex objects so previous nodes in the flow will also need to change,
d) removes the simple one node one pin relationship,
e) would require a complete different config ui and detailed instructions to get going - so it looks like a new node anyway.

To me it would be like having someone learn to drive a motor scooter then switching it for a large lorry - yes they both have wheels and go on the road, but the controls are different and a lot more complexity.
There should be no problem having both nodes installed if you really wanted to. We could certainly add a pointer to the more advanced node from the existing one if needed.


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

#368 a9c980f Thanks @threepointone! - update deps

<EMAIL_ADDRESS>Patch Changes

#365 5e73617 Thanks @jevakallio! - Only yield open hibernating connections to match non-hibernating behaviour + polyfill WebSocket status code on platform side

#368 a9c980f Thanks @threepointone! - update deps

<EMAIL_ADDRESS>Patch Changes

#365 5e73617 Thanks @jevakallio! - Only yield open hibernating connections to match non-hibernating behaviour + polyfill WebSocket status code on platform side

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Validate collected subdomains

Why has this PR been re-opened. Subfinder MUST NOT filter any of its domains.


Create .pre-commit-hooks.yaml

Allows to use Yamale as a pre-commit hook as follows:
    - repo: https://github.com/rsrdesarrollo/Yamale
      rev: 'c03ebfc703f557eb5af1b7ef895482b754ce0395'
      hooks:
        - id: yamale-schema-verify
          name: yamale-schema-verify
          files: 'data/.*'
          args: ["-s", "schemas/sample.yaml", "data"]

Note that it's a bit more idiomatic to have pass_filenames: true.
Then you can use --all-files as in pre-commit run [--all-files] yamale-schema-verify.
This is how my config is with your PR:
  - repo: https://github.com/23andMe/Yamale
    rev: ec646c5fab03929fb4ed1e9f6266d8dfaa5d1185  # Use SHA until 5.2.2 is released.
    hooks:
      - id: yamale-schema-verify
        alias: yamale-argocd-app
        files: apps/base
        pass_filenames: true
        types:
          - yaml
        exclude: (/kustomization.yaml$|values.yaml$|/manifests/|scaffolding/)
        args:
          - --no-strict
          - --schema
          - ci/yamale/argocd-application-schema.yaml

But now I realize that, at the time, pass_filenames: false was the only way, before https://github.com/23andMe/Yamale/pull/251 was merged.
Let me send a follow-up PR to incorporate it.


Straightforward CMake build doesn't work on Mac and no instructions available.

Why this matters: I want to submit PRs that make this project more consumable as a dependency of other CMake projects.  Without a baseline understanding of what is expected to work, I can't test my changes.
ArgumentParser version: the main branch
Swift version: swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-<IP_ADDRESS>.56 clang-15<IP_ADDRESS>.5)
Target: arm64-apple-macosx14.0
Checklist

[x] If possible, I've reproduced the issue using the main branch of this package
[x] I've searched for existing GitHub issues

Steps to Reproduce
cmake -GNinja -S . -B .cmake-build -DBUILD_TESTING=1 -DBUILD_EXAMPLES=1 &&
  cmake --build .cmake-build &&
  ctest -V --test-dir .cmake-build

Expected behavior
Successful build and test.
Actual behavior
/Users/dave/src/swift-project/swift-argument-parser/Sources/ArgumentParserTestHelpers/TestHelpers.swift:14:8: error: no such module 'XCTest'
import XCTest
       ^
/Users/dave/src/swift-project/swift-argument-parser/Sources/ArgumentParserTestHelpers/TestHelpers.swift:14:8: error: no such module 'XCTest'
import XCTest
       ^

As currently configured, SwiftPM is the supported tool for building and running tests on the Mac. If there's a way to expand CMake support, that would be great to see!

To be clear, this is not a request to make the straightforward cmake build work; it's a request that someone (like whoever added the CMake "support", such as it is) describe the circumstances under which they expect it to work. Without such a description, "expanding CMake support" as you put it —which is what I am ultimately trying to do—is impossible because I can't know if any given change is breaking something important. "CMake isn't officially supported" may be true enough but it doesn't begin to address the issue.

If there's a way to expand CMake support, that would be great to see!

@natecook1000 Maybe I should read this as, “whatever you, Dave, attest is improving CMake support, I'm likely to accept the PR unless it breaks our CI.”  If that's what you mean, I don't need to worry about who else might be relying on the current CMake configuration. Is that the right interpretation?

@natecook1000 Bump.  It would be really good to get some clarity on this matter.  I currently have 2 open issues and 2 open PRs related to CMake support.  I want to know if I'm wasting my time submitting these, or if there's some way to move them forward.  /cc @compnerd


Path Following Module Bug

I am trying to run CARLA, SUMO, Autoware universe together. I am using your bridge to connect carla and autoware universe. When I run carla and autoware the path following module works fine. But, once I introduce traffic from SUMO, the module starts to break apart (as can be seen in the image, the ego vehicle is on the off road, struck at the building)and the vehicle never reaches the goal position. Is there any resolution for this?

@prabanjanGITHUB could you help me reproduce the problem? Maybe there is a tutorial for CARLA + SUMO, which you are following?

https://carla.readthedocs.io/en/latest/adv_sumo/
I am following this.
First I ran carla, then Autoware, then the bridge. after that I use either of this commands "python run_synchronization.py examples/Town01.sumocfg  -tls-manager carla --sumo-gui" or  "python run_synchronization.py examples/Town01.sumocfg  -tls-manager sumo --sumo-gui"
with both sumo and carla as --tls-manager, the same issue persisted


Try StackEdit+, fixed some known bugs and added some new features.

Github: https://github.com/mafgwo/stackedit-plus

Nice!
Could you preserve the Git history from the original StackEdit?
It's nice for previous contributors and conveys important context to understand the code

Nice! Could you preserve the Git history from the original StackEdit? It's nice for previous contributors and conveys important context to understand the code

Thank you!
It's a good advice. All historical submission records have been added.


Is it possible to associate an existing setting with a Kirki control?

I would like to replace the default blog tagline/description field with a wysiwyg editor. I can easily replace the control or change its type using the Customizer API, but how would I achieve this with Kirki when the setting and control functions are tied to each other?

First you'll have to remove the control and then add it normally.
So something like this:
add_action( 'customize_register', function( $wp_customize ) {
	$wp_customize->remove_control( 'blogdescription' );
} );
Kirki::add_config( 'single_settings', array(
    'capability'    => 'edit_theme_options',
    'option_type'   => 'option',
) );
Kirki::add_field( 'single_settings', array(
	'settings' => 'blogdescription',
	............
	............
) );


puppet hostie can not run

Hi, this is my first time with Wechaty, but I have some problem need to help...
I follow the Wechaty Getting Started project, but I have wechat account problem so I can not login with Web protocol.
So I follow the "Wechaty Puppet Service Providers" guide, apply PuppetPaimon token and set environment variable.
But I got below problem.

Yep, it just retry again and again and again, so could you tell me there something I was wrong please?

Please check whether your TOKEN is in service by reading https://wechaty.js.org/docs/specifications/token#service-discovery
If it's out of service, please contact your Puppet Service Provider for support.


(ISO 6709) Annex styles: use "a2", "a3" instead of "Heading 2", "Heading 3"

Confirmed fixed. Thanks!


[FR] 0>app.h(341,5): Error  : 'INTERNAL_EXPERIMENTAL' is not defined, evaluates to 0 [-Werror,-Wundef]

i receiver this error when try build sdk from rider for project ue5, how can i fix it
0>app.h(320,5): Error  : 'INTERNAL_EXPERIMENTAL' is not defined, evaluates to 0 [-Werror,-Wundef]
0>#if INTERNAL_EXPERIMENTAL
0>    ^
0>app.h(341,5): Error  : 'INTERNAL_EXPERIMENTAL' is not defined, evaluates to 0 [-Werror,-Wundef]
0>#if INTERNAL_EXPERIMENTAL
0>    ^
0>app.h(353,5): Error  : 'INTERNAL_EXPERIMENTAL' is not defined, evaluates to 0 [-Werror,-Wundef]
0>#if INTERNAL_EXPERIMENTAL
0>    ^
0>app.h(382,5): Error  : 'INTERNAL_EXPERIMENTAL' is not defined, evaluates to 0 [-Werror,-Wundef]
0>#if INTERNAL_EXPERIMENTAL
0>    ^

As a workaround, if you can add a preprocessor definition INTERNAL_EXPERIMENTAL=0, that should fix this.

https://github.com/firebase/firebase-cpp-sdk/blob/f198c6f87e3d762cc3bfdac80a6b38541e5e8641/app/src/include/firebase/app.h#L320
https://github.com/firebase/firebase-cpp-sdk/blob/f198c6f87e3d762cc3bfdac80a6b38541e5e8641/app/src/include/firebase/app.h#L341
https://github.com/firebase/firebase-cpp-sdk/blob/f198c6f87e3d762cc3bfdac80a6b38541e5e8641/app/src/include/firebase/app.h#L353
https://github.com/firebase/firebase-cpp-sdk/blob/f198c6f87e3d762cc3bfdac80a6b38541e5e8641/app/src/include/firebase/app.h#L382

Those are all lines with
#if INTERNAL_EXPERIMENTAL

All prior uses of INTERNAL_EXPERIMENTAL in that file were:
#ifdef INTERNAL_EXPERIMENTAL

Either:

a default value needs to be defined and all of the #ifdef replaced with #if
-or-
all of the #if INTERNAL_EXPERIMENTAL need to be replaced with #if defined(INTERNAL_EXPERIMENTAL) && INTERNAL_EXPERIMENTAL


About issue of java.lang.reflect.InvocationTargetException

Hi thanks for the help in https://github.com/intuit/karate/issues/876 but can you tell more on why we should not use the feature files as feeder and the changes which you have told I made them but still getting the issue PFA stack trace -
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at io.gatling.mojo.MainWithArgsInFile.runMain(MainWithArgsInFile.java:50)
at io.gatling.mojo.MainWithArgsInFile.main(MainWithArgsInFile.java:33)
Caused by: java.lang.UnsupportedOperationException: There were no requests sent during the simulation, reports won't be generated
at io.gatling.charts.report.ReportsGenerator.generateFor(ReportsGenerator.scala:49)
at io.gatling.app.RunResultProcessor.generateReports(RunResultProcessor.scala:76)
at io.gatling.app.RunResultProcessor.processRunResult(RunResultProcessor.scala:55)
at io.gatling.app.Gatling$.start(Gatling.scala:82)
at io.gatling.app.Gatling$.fromArgs(Gatling.scala:47)
at io.gatling.app.Gatling$.main(Gatling.scala:39)
at io.gatling.app.Gatling.main(Gatling.scala)

@ajijshaikh read the error carefully and you will see the issue. get a simple test working first before you go into advanced topics like feeders which from a quick look at your code it is clear you have not understood. for the last time - please ask basic doubts on stack-overflow, thanks


Implement equivalence handling for Task

Tasks are equivalent when their Service and Facility are equal.
When we add Task that is already in the SchedulingPool, we set a flag that indicates that this Task should be imediately rescheduled when it is finished.
Also create this flag (eg. boolean reschedule on Task class).
(result of #7)

Turns out this was already implemented while adding a Task to SchedulingPool but outside of its methods and uses the existing boolean sourceUpdated attribute.


LICENSE

As a team member I want to have a License file to provide license information to other visitors to and users of the repo.

Readme created October 16th but duplicated December 12th due to issues in the original GitHub account.


Ansible: version bump for 2.6/2.7 and current 2.8

Motivation for this change
Version upgrade
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @joamaki @costrouc

@GrahamcOfBorg build ansible ansible-lint ansible_2_6 ansible_2_7 kargo python27Packages.ansible python27Packages.ansible-kernel python27Packages.ansible-lint python27Packages.ansible-runner python27Packages.pytest-ansible python37Packages.ansible-kernel python37Packages.ansible-runner python37Packages.pytest-ansible


Update Deploy.sol

Thanks for the PR. We've implemented the changes from #15, #16, #17 as a single PR #18, and added a bunch of other fixes.


GFM support by default?

That's great lib! Awesome work!
But I noticed that it miss few things like todo checkboxes.
Can you implement full GFM preset?

While doable, I don't have an immediate need for it. But I'd merge a PR that implements it


SciVis volume lighting?

I am using the SciVis renderer and I cannot get a volume to be affected by lighting. The documentation does not appear to specify whether this is possible. I have tried all of the options that I assumed might be related to this. Is this supported?

In another issue it was stated

all the "nice" looking volume renders on the ospray.org website are the "scivis" renderer with some fancy options turned on

What are these options?

volumes are only affected by lighting in a few ways.  If you create an isosurface or enable gradient shading on the volume, you will get some surface shading from lights.  If you enable shadows and/or AO on the renderer, the volume should cast shadows on other surfaces.

I somehow missed that parameter, thank you.
It appears that there is a bug with lighting for an unstructured volume. Below is the same volume loaded as a regular structured volume and as an unstructured volume. The black void appears on the +XYZ faces of the volume and does not correspond with the lighting direction. The same result appears with ambient occlusion and shadows both enabled and disabled.
Unstructured

Structured

The above examples are recorded with an ambient light and a directional light. The effect is less pronounced but still visible with ambient light only:

Does this artifact show up when gradient shading is disabled?

No

It would appear to be an edge case on the computeGradient function for unstructured grids.  @timrowley?

Are you using a release version of ospray, or the current devel tree?  What unstructured cell type are you using?  Thanks.

I am using the most recent release version and hexahedral cells.

Hi Stas,
You've found some of the rough edges in our scivis renderer. We've been working for a while on v2.0, which I hope addresses a number of the issues that you have found. In general, the users which have been leveraging our unstructured/AMR volumes haven't been using the more advanced lighting features in the scivis renderer, which explains why there's such a gap in features right now.
For this issue in particular, a number of the lighting features in the scivis renderer were added because the pathtracer never supported volumes. We have some initial support for volumes in the pathtracer in 2.0 already (on the devel branch), and will continue to improve it as time/versions march on. Part of 2.0 is using our upcoming new OpenVKL library, which gives us a more robust way to iterate over ray segments of interest on all volume types (which OSPRay did not do outside of structured volumes).
We are still a couple of weeks away from v2.0 being finished (and OpenVKL being released), but having a look at the API changes on devel may be useful for catching all of the improvements we are making moving forward. Please let us know if you have any questions about the new API changes, which we will also post documentation about when we make the official release.


Blacklist the bot account itself

I did notice that the bot is retweeting the same tweet again from the retweet of the bot. Blacklisting the bot twitter account would reduce the duplication or retweets coming from the bot itself.

Should this be done in another branch?

All the code that can be merged should go through as a pull request, a WIP is more than welcome :)
Since you have access to the repo, you can create branches within the repo and push in your changes and easily spawn up a pull request as well. I think this is more convenient that fork + pull request. And also convenient for the team to check to do a git pull and get all your changes to test our and review :)

duly noted :)

@Aniketh01 can this issue be closed now?
#60 solves this


update weave add-on to use patched images

What type of PR is this?
type::chore

What this PR does / why we need it:
Updates images for weave add-on versions 2.6.5 and 2.8.1. New images are patched for CVEs.
Which issue(s) this PR fixes:

Fixes #
SC-49336
Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

Fixes CVEs for weave 2.8.1 plugin

Does this PR require documentation?

NONE

you will need to add EXEC_IMAGE env var to pods like so https://github.com/replicatedhq/replicated-installer/blob/06a2cb9fc32731386e23afe87456b23386565610/install_scripts/templates/kubernetes/yml-generate.sh#L966-L967
can you find out if we have the ability to run airgap tests on pr from @laverya ? if so can you add? i would think we would have caught this without my review

@emosbaugh The env var and airgap test have been added now.


GoogleGlass TAP support

Is there a way that i can capture BeyondarObject when i TAP on GoogleGlass ?

What do you mean "capture"?

with Capture i mean to TAP the marker(POI/GEoPosition) Object and show details of it on another View/CardView

I suggest you to check how it is done here https://github.com/BeyondAR/beyondar/blob/master/android/BeyondAR_Framework/src/com/beyondar/android/fragment/BeyondarFragmentSupport.java
Check the touch events, they get the coordinates of the screen and them send them using mBeyondarGLSurface.getBeyondarObjectsOnScreenCoordinates

When you say touch events you are speaking in terms of GoogleGlass and not android device itself, right?

On Google glass a touch/click means the track pad


fix load binary id array error

Related issue: #2830
Like the issue says, Ecto 3.0 can't transform binary_id in an array to the printable string.
Reason
In Ecto 3.0, the type :binary_id is specially handled:

Through adapter.loaders, the type :binary_id has becomes to [Ecto.UUID, :bianry_id]
Then load twice for each Ecto.UUID and :binary_id

The result is correct because it calls the function Ecto.UUID.load/1 during the first load.  But {:array, :binary_id} is not specially handled. The function dump_binary/1 just returns what it receives.
Solution
Like Ecto 2.x, pattern match the {:array, :binary_id} and handle the value of each of the array.

Sorry, I did not see you were working on it. I have already pushed a fix to master. :)

delet


deps: use go 1.16

Goal
Update to use go 1.16

Hey @chenrui333.
Thanks for this. We will review as soon as priorities allow.

Hey @chenrui333, thanks for the PR - we're closing this in favour of #173 as it turns out bumping the version in go.mod isn't necessary.


Unable to specify provider region

When setting up lambda@edge I want the aws region to be us-east-1. I am not able to set that.
Has this problem been tackled in other modules? Would we have to explicitly pass it along like in the TF docs?

Nevermind you can pass a provider.


feature request : allow to provide a client_manager

So that we can use Redis or RabbitMQ to make socket.io work in a multi process context.
See https://python-socketio.readthedocs.io/en/latest/server.html?highlight=redis#using-a-message-queue

Hey @thomasleveil 👋
Thank  you for the feature request 🙏
I have seen previously that there is possibility of using Redis, RabbitMQ and other services with SocketIO but haven't dig any deeper into the use-cases and implementation.
I will read some docs and take a look on how could we implement this 🚀

Also interested in this. I'm not sure how it can be tied to app, since using a Manager replaces that argument socketio.AsyncServer(client_manager=socketio.AsyncRedisManager('redis://')) - so it seems mutually exclusive? But yeah, this feature would be a boon for scaling apps (multiple servers), as well as some features which appear only available on the JQ Managers, like sio.get_participants() to see a list of users in the room.

Hello. Any progress ?

Any Ideas @pyropy ??

Hey sorry folks, I really have a lot of going on my plate so I don't really have time to get feature requests going. I would appreciate any contributions from your side as that would help me greatly in maintaining this library.


Phoscon-GW: /lights/2: warning: using default colour gamut for unknown light model

Hi,
I installed the "MEGOS SMart Home LED Wand- und Deckelpanel" and I got the same problem as mentioned in
https://github.com/ebaauw/homebridge-hue/issues/850
it works but I got a warning. What can I do or which information do you need to cover this problem ?
Thanks
Bernhard
Log Messages

[27.2.2021, 11:44:36] [Conbee] Phoscon-GW: /lights/2: warning: using default colour gamut for unknown light model {"colorcapabilities":0,"ctmax":65279,"ctmin":0,"etag":"18fc60983b39e1e33450409970fffdbf","hascolor":true,"lastannounced":null,"lastseen":"2021-02-27T10:43Z","manufacturername":"_TZ3000_gb5gaeca","modelid":"TS0505B","name":"Küche - Extended color light 2","state":{"alert":"none","bri":102,"colormode":"ct","ct":250,"effect":"none","hue":43603,"on":false,"reachable":true,"sat":36,"xy":[0,0]},"swversion":null,"type":"Extended color light","uniqueid":"84:2e:14:ff:fe:0e:17:13-01"}
[27.2.2021, 11:44:36] [Conbee] Phoscon-GW: /sensors/2: warning: unknown ZHAPresence sensor {"config":{"battery":97,"duration":60,"enrolled":1,"on":true,"pending":[],"reachable":true},"ep":1,"etag":"d33898118f9200bd4f0258cc472dc233","lastseen":"2021-02-27T10:44Z","manufacturername":"SILVERCREST","modelid":"TY0202","name":"Motion Sensor Lidl","state":{"lastupdated":"2021-02-27T10:44:34.831","lowbattery":false,"presence":true,"tampered":true},"swversion":"2019.12.12","type":"ZHAPresence","uniqueid":"ec:1b:bd:ff:fe:ac:29:e7-01-0500"}

Debug Files

You could try and run ph probe on the light - maybe it reports the actual colour (rather than echoing the set colour), so we can determine what gamut it supports.  I wouldn't hold high hopes: it doesn't seem to expose Color Capabilities and the colour temperature range shows the default values.

I did this:
home@home-bridge-bs:~$ ph probe - v /lights/2
ph: localhost: request 1: GET /config
ph: warning: localhost: request 1: <IP_ADDRESS>:80: cannot connect: ECONNREFUSED
ph: error: localhost: not a Hue bridge nor deCONZ gateway

ph: error: localhost: not a Hue bridge nor deCONZ gateway

Just wrote up a FAQ entry for that.

Sorry I was very busy and now I tried:
ph -H 192.168.177.xy -u username probe /lights/2
192.168.177.xy = my phoscon server
but I got
api error 1: unauthorized user, so I'm confused what the username could be:
in you Interface it is
        "hosts": "192.168.177.xy",
        "users": {
            "00212EFFFF06xxxx": "8097E4yyyy"

Trying it with "8097E4yyyy" gives no reaction and propmt doesn't apear.
Thanks

It takes a couple of minutes.  You might add -v for feedback during the discovery: ph -H x.x.x.x -u xxx probe -v /lights/xx

Okay now it works, thanks. I got the following output (red, blue, green went on but didn't change):
ph probe: /lights/2: cool ... done
ph probe: /lights/2: warm ... done
ph probe: /lights/2: red ............................................................... timeout
ph probe: /lights/2: green ............................................................... timeout
ph probe: /lights/2: blue ............................................................... timeout
{
"manufacturername": "_TZ3000_gb5gaeca",
"modelid": "TS0505B",
"type": "Extended color light",
"bri": true,
"ct": {
"min": 153,
"max": 500
},
"xy": {
"r": [
0.9961,
0.0001
],
"g": [
0.0001,
0.9961
],
"b": [
0.0001,
0.0001
]
}
}

By the way: With the HUE Essentials App I can change all color, also with Homekit in the Home App.
Bernhard

So the light doesn’t report back the actual colour; using the default gamut is the only option.


Troubleshoot platform.sh integration test

Integration test is currently failing for Platform.sh, on macOS at least. It's related to a CLI authentication, when run from a script. I'm not sure if this affects end users.

[x] Set up a project and deploy it manually using platformsh config-only run.
[x] Repeat for automate-all run.
[x] Try integration test.
[ ] Delete relevant ssh files?

This no longer seems to be an issue.


TLS verification warnings write to stderr

I tested this and warnings no longer corrupt the file when I run
mitmdump -q -w /dev/stdout > out then mitmdump -n -r out
cc @mhils

Thanks!


Docs for basic tier and link updates

In this PR:

Trivial content updates (feel free to ignore -- will have to revisit content in April once the workflows are finalized)
File renames and related link updates
Navigation bar (partial) updates
Tab updates

The deploy preview failure is due to several broken links. Might be worth make linkcheck locally.


Update automated-release token in settings

See https://github.com/fregante/chrome-webstore-upload/blob/main/How to generate Google API keys.md
In https://github.com/hankxdev/one-click-extensions-manager/issues/90#issuecomment-1255840721
Log from https://github.com/hankxdev/one-click-extensions-manager/actions/runs/3110766643/jobs/5042297073
- Fetching token
{
Probably the provided refresh token is not valid. Try following the guide again
  "error": "invalid_grant",
https://github.com/fregante/chrome-webstore-upload/blob/main/How%20to%20generate%20Google%20API%20keys.md
  "error_description": "Bad Request"
}
{
  clientId: '***',
  refreshToken: '***'
}

@fregante I don't remember I removed your access from options. but let me create a new one.

{
  "error": {
    "code": 400,
    "message": "Publish condition not met: You must verify your contact email before you can publish any item. Begin the verification process on the Account tab.",
    "errors": [
      {
        "message": "Publish condition not met: You must verify your contact email before you can publish any item. Begin the verification process on the Account tab.",
        "domain": "chromewebstore.access",
        "reason": "badRequest"
      }
    ]
  }

keep getting this, however the email has been verified. will try later if there is no other issues.

I'll try uploading it manually, let's see what happens

I think it needed a privacy policy. It's now "pending"
I'll try triggering a new release later to see if the token works, and then I'll close this issue.
Side note: We were featured?! Since when?

Not sure when. it's been featured automatically,

It worked!


Add support for paramspec

Adds support for ParamSpec, to keep compat I've decided to only check the name as typing_extensions is not a normal dep, and someone else using the name seems unlikely, though a check for some attribute could be added if necessary

Not sure about the 3.7 check, as it's failing for me on main too

Not sure about the 3.7 check, as it's failing for me on main too, and type is something from stubs?

Indeed something changed between https://github.com/tox-dev/sphinx-autodoc-typehints/actions/runs/3043415433 and https://github.com/tox-dev/sphinx-autodoc-typehints/actions/runs/3051184692.
The type check failure is because of because of github.com/python/mypy/pull/13500 (see related github.com/python/mypy/issues/13627); waiting for mypy 0.980 release to fix that. I don't have currently the bandwith to look into this, so if you want this to land soon would be much apprecated if you can look into it and put in a fix PR.

Okay, for 3.7, it looks like the type_comment extra is not getting installed and type comments are skipped because of that.
The trailing ``s used here https://github.com/tox-dev/sphinx-autodoc-typehints/blob/ccc75d244d0f4452048f80fc73e39a34a4eefc00/tox.ini#L25 was dropped in ccc75d244d0f4452048f80fc73e39a34a4eefc00, but after removing it in tox.ini, it still is unable to find it unless the underscore is removed or changed to -, not sure if that's a bug somewhere or the intended behaviour.
Should I just change it to -?

Should I just change it to -?

Can give it a try to see if helps.


feat: port the Box layer into the reearth/core

Overview
What I've done
I have ported the Box layer into the reearth/core/features.
Also I have ported the clipping feature logic into Tileset component in the reearth/core/features.
What I haven't done
How I tested
Screenshot

Which point I want you to review particularly
Memo

I've added onLayerEdit to context.
feat: add onLayerEdit property to context

I've done refactor to move feature context.
fix: move feature context

I fixed the box layer event handling.
fix: box event handling


Add headers like Content-Security-Policy

Hey,
Thanks for this image, I'm really considering using it instead of nginx for my projects! Just one thing, how can you easily add headers like Content-Security-Policy, X-XSS-Protection, X-Content-Type-Options, etc... ?

Hi @AymericBethencourt, thanks for liking this project.
At the moment it is not possible to introduce custom middlewares but I will implement this feature so we ca easily cover this and other use cases.
Will get back to you ASAP,
Regards

Hi @AymericBethencourt, from v1.1.0 you have the chance to extend the server functionalities through middlewares. Please see:
https://github.com/jkyberneees/restana-static/releases/tag/v1.1.0
Regards


Error reporting: invalid metadata

When we accept invalid metadata from an application and pass it to the core, the core gives us an error. It would be helpful of us to scan over the metadata, determine what was invalid about it, and raise into the application an exception with informative detailed text about the metadata invalidity.

After issue 8814 and pull request 8995 what's left here is the debugging enhancement request "be more helpful to applications that make mistakes". A good thing to do, but not a priority and not something that has to be in any particular release.

The more I think about this... the less urgent it seems like a thing to need to do. There's also a relationship between this and issue 13782.
But I wouldn't yet say "no" to this or close the issue...

Hi @nathanielmanistaatgoogle I've ran into this problem, specifically with an integer value and key that contained an uppercase letter. What's the status of this issue and are there any blockers?

@alexkarim: I don't think there are any blockers; I think it's just not prioritized at the moment. It would take some (a day's worth?) thought and care and work, and I think everyone's just working on higher-priority things.


Make responsive/hi-fi mockup(s) for the core application interface

Make responsive/hi-fi mockup(s) for the core application interface. Wireframes for UX flows can be found here

Simple visual styling for mobile-first open source project (loosely based on tailwind default UI). Accounting for diverse usability & applications.
Built on that, specifically for the City of Seattle. Style guide here, and a (rough) example of usage here.

Make responsive/hi-fi mockup(s) for the core application interface. Wireframes for UX flows can be found here

Simple visual styling for mobile-first open source project (loosely based on tailwind default UI). Accounting for diverse usability & applications.

Built on that, specifically for the City of Seattle. Style guide here, and a (rough) example of usage here.

Still need more work here, moving to M5

I think Holly/Hans had a few good passes on this


Will it support zcu104?

Will it support zcu104?
Eli

No, zcu104 is not in the roadmap of supported devices. Kria KV260 on the other hand is being supported.