Shall responder skip the mutual authentication if requester does not have the capability?

In the implementation of libspdm, responder sets the value of mut_auth_requested of the key exchange response according to the capability of requester and responder:
https://github.com/DMTF/libspdm/blob/04baaa92bc59e03aa528988edd46bfc15ce01e2b/library/spdm_responder_lib/libspdm_rsp_key_exchange.c#L386-L399
If responder or requester does not have such capability, responder will skip the mutual authentication and run the rest of the process and finally establish the secure session, which may not be safe.
I tried the spdm-emu to run a responder with argument --mut_auth DIGESTS and a requester without MUT_AUTH capability using below commands. The result shows they skip the mutual authentication and successfully running to the end.
./spdm_responder_emu --trans PCI_DOE --mut_auth DIGESTS --req_asym ECDSA_P384 --basic_mut_auth NO

./spdm_requester_emu --trans PCI_DOE --req_asym ECDSA_P384 --exe_conn DIGEST,CERT,CHAL --exe_session KEY_EX,PSK,KEY_UPDATE,HEARTBEAT,DIGEST,CERT --cap CERT,CHAL,ENCRYPT,MAC,KEY_EX,PSK,HBEAT,KEY_UPD,HANDSHAKE_IN_CLEAR

My thought is that responder should end the conversation and return an error message to requester if responder wants to verify the requester but requester does not support the mut_auth capability.

Good point.
I think we need to distinguish capability from enabling.

If Responder just wants to support capability, then it should allow the requester not supporting mut_auth.
If responder wants to enforce the mut_auth enabling state, then it should reject the requester not supporting mut_auth.

Right, the Integrator may need to be in the loop to determine if mutual authentication is needed. In particular, MutAuthRequested may be conditional based on the Requester's OpaqueData. There may also be a case where the Responder requires mutual authentication, but it's just for logging purposes and does not restrict what the Requester can do.


AVR Yamaha Node shows "connected" but receives no data

I have a Yamaha RX-V673 and have just started using these nodes. The Put and Get nodes work fine but the AVR Yamaha (upnp listener) node has no output even though it says connected. I'm using the standard 8080 port.
Is there anything I can do to test why this isn't working?
The Yamaha AV Controller Android app works fine as does the webserver at the devices IP address.

I have the same issue.
my flow:
[{"id":"c4690ebfd1177b32","type":"AVR-Yamaha-in","z":"4d695019c4a5e342","device":"d8060c90c11265a2","name":"WZ","devdesc":false,"x":150,"y":440,"wires":[["1ca8b601aa02e169","691bada931f47058"]]},{"id":"1ca8b601aa02e169","type":"debug","z":"4d695019c4a5e342","name":"debug 2","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":520,"y":440,"wires":[]},{"id":"691bada931f47058","type":"debug","z":"4d695019c4a5e342","name":"debug 3","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"topic","targetType":"msg","statusVal":"","statusType":"auto","x":520,"y":480,"wires":[]},{"id":"d8060c90c11265a2","type":"avr-yamaha","name":"Wohnzimmer","address":"<IP_ADDRESS>","port":"","debug":false}]

Same Yamaha RX-V673 (firmware version 1.98),  same issue here. How to debug? Issue for RX-V673 only or also other types?

OK, the node has output after setting topic System.Misc.Event.Notice On
see https://github.com/krauskopf/node-red-contrib-avr-yamaha/issues/13#issuecomment-490211291


Log StartupTimeoutLimit failure to response

Fixes https://github.com/aspnet/AspNetCore/issues/10383 (at least the diagnostics part of it).

Conflict :(

Failures will be fixed by https://github.com/aspnet/AspNetCore/pull/10695


fileName or filename?

In the readme, the example shows passing a json object with property fileName, but other examples show filename. Which is correct?

Yes, filename.


Adjusted some xeno pull speeds

About the PR

Adjusted the xeno pull speeds based on what we had and what was defined in CM-13 and what the current Queen pull speed is.
Boiler now has the default pull speed of 0.75 (not sure where the 0.5 was from)
Warrior now pulls slightly slower (0.58, since the value in CM was 2 and for Queen is was 3)
Runner now pulls slightly faster (0.80, the value in CM was -0.5)
Why / Balance

CM-13 parity
Technical details

no
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

fix: Fixed some xeno pull speeds. Runner pulls faster, boiler pulls the same as most xenos, and warrior pulls a little slower then they used to.

Changed them again. Did tests in cm-13 comparing the darg speed of runner and warrior with the normal xeno pull speed and pull mult vs any changes their castes made and came out to about 0.86 speed for runner and 0.56 for warrior.


ndarray indexing issues

I am new to mxnet. I just installed mxnet 1.0.0 and python 3.5 on a Ubuntu 14.04 machine with CUDA 8.0 and cudnn 7.0.5.
My code is given below. I am trying to store image data in an ndarray. (see https://github.com/ypwhs/DogBreed_gluon/blob/master/get_features_v3.ipynb for the original code) -
X_224 = nd.zeros((n, 3, 224, 224))
X_299 = nd.zeros((n, 3, 299, 299))
mean = np.array([0.485, 0.456, 0.406])
std = np.array([0.229, 0.224, 0.225])
for i, (fname, breed) in tqdm(df.iterrows(), total=n):
img = cv2.imread('data/train/%s.jpg' % fname)
img_224 = ((cv2.resize(img, (224, 224))[:, :, ::-1] / 255.0 - mean) / std).transpose((2, 0, 1))
img_299 = ((cv2.resize(img, (299, 299))[:, :, ::-1] / 255.0 - mean) / std).transpose((2, 0, 1))
X_224[i] = nd.array(img_224) <-- I get error in this line
X_299[i] = nd.array(img_299)

ValueError: Indexing NDArray with index=0 and type=class 'numpy.int64' is not supported.

Issue is that isinstance is not working as expected by the code and returns false in python3. Workaround is to force the type of i to be int instead of numpy.int64.  I think this should also be fixed on the mxnet side. The problem is that we are calling isinstance with int and in the check isinstance(np.int64, int) is not reliable. Please see: https://github.com/apache/incubator-mxnet/blob/master/python/mxnet/ndarray/ndarray.py#L2039. The suggested fix is to check with np.integer for numpy data types. WDYT @reminisce ?

@reminisce

@reminisce I wasnt able to reproduce the issue for python 2. The int type changed in python3 and not related to numpy classes

@anirudh2290 Have you tried the following?
Python 2.7.14 |Anaconda custom (64-bit)| (default, Oct  5 2017, 02:28:52)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import mxnet as mx
/Users/jwum/anaconda2/lib/python2.7/site-packages/h5py/__init__.py:34: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
/Users/jwum/anaconda2/lib/python2.7/site-packages/mxnet-1.1.0-py2.7.egg/mxnet/optimizer.py:136: UserWarning: WARNING: New optimizer mxnet.optimizer.NAG is overriding existing optimizer mxnet.optimizer.NAG
  Optimizer.opt_registry[name].__name__))
imp/Users/jwum/anaconda2/lib/python2.7/site-packages/urllib3/contrib/pyopenssl.py:46: DeprecationWarning: OpenSSL.rand is deprecated - you should use os.urandom instead
  import OpenSSL.SSL
>>> import numpy as np
>>> a = np.array([0], dtype='int32')
>>> b = mx.nd.array(a)
>>> b[a[0]]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/jwum/anaconda2/lib/python2.7/site-packages/mxnet-1.1.0-py2.7.egg/mxnet/ndarray/ndarray.py", line 504, in __getitem__
    % (str(key), str(type(key))))
ValueError: Indexing NDArray with index=0 and type=<type 'numpy.int32'> is not supported

@reminisce away from laptop. Will give that a try. Tried with np.int64

@reminisce verified that it works for np.int64 on python2, doesn't work for np.int32. For python3, it doesnt work for either np.int32 or np.int64. This is probably because in python2, the int is 64 bit because of python build on my machine and isinstance check passed for np.int64. In python3 since int is changed and is not related to np.int32 or np.int64,  it fail isinstance checks for both np.int32 and np.int64.

@ashishlal related pr merged. can this be closed ?

https://github.com/apache/incubator-mxnet/pull/10434 fixes this


some online hosts do not get updated by scan.go

assuming i understand this correctly...
hostTree.All() returns a list of hosts sorted by weight
threadedScan() cuts off after 200 online hosts
now that the list is sorted by weight and the host list is well over 200, low ranked hosts never have their configuration updated by a scan - it seems only an announce can do so at this point.

It also randomly queries ones outside of the top 200, so eventually you will get updated. But if you want to be certain that you are rescanned by the network quickly, the only way to do so is to re-announce.


Add grepText to the Prelude

During my scripting, I missed a function that could grep a Shell Text and so I wrote one ;)
I added an internal helper grepWith that is parameterized over an additional function wich converts to Text and used that one from both grep and grepText.

I'll merge this as soon as CI passes

We could also add a grepFilePath :: Pattern a -> Shell FilePath -> Shell FilePath which would be just onFiles . grepText but I don't know whether it is worth to make that more visible or if users should just write the version with onFiles

Yeah, I would recommend using onFiles for the FilePath case

I can push a new release to Hackage if you have no other pending changes

You are really super fast, I appreciate that.  Let's wait one or two days, I might find more stuff to add and I don't mind having it defined inside my script for now ;)

You are really super fast, I appreciate that.  Let's wait one or two days, I might find more stuff to add and I don't mind having it defined inside my script for now ;)

You are really super fast, I appreciate that.  Let's wait one or two days, I might find more stuff to add and I don't mind having it defined inside my script for now ;)

You are really super fast, I appreciate that.  Let's wait one or two days, I might find more stuff to add and I don't mind having it defined inside my script for now ;)


Merge to dev: Fix gaps in final commit for #258 (c9ab0b4ede)

#275
register DefaultWebHookMetadataProvider in DI
register IWebHookFilterMetadata implementations in DI
fix parameter reversal and overuse of Resources.VerifyMethod_BadMethod
add first functional tests

part of #180
add functional test infrastructure
update DropboxCoreReceiver to meet new requirements e.g. add test-only secret key

nits:

correct names of resources
let VS remove a few UTF8 BOMs

FYI only. Will merge once CI checks succeed.


Getting a warn message  at build time

I am getting an warning message as follows when I do activator dist. I am using play 2.5 (JavaPlay) , tuplejump: 0.9.0 and scala 2.11.
[warn]   Found intransitive dependency (com.tuplejump:play-yeoman_2.11:0.9.0) while publishMavenStyle is true, but Maven repositories do not support intransitive dependencies. Use exclusions instead so transitive dependencies will be correctly excluded in dependent projects.

Any updates on this issue?


Add ZK annotation

Adding in information about the source of the Pedersen commitments for the ZK proofs.

@jot2re I think @JamesSmartCell's language is a bit off here, can you correct it?
He wrote:

    // Verify Proof Of Knowledge
    // forming a zk meta-proof that the two Pedersen commitments represent the same data
    // this verifies the integrity of the data; the actual data can be optionally revealed by the attestation holder
    // See:
    // Commitment1: https://github.com/TokenScript/attestation/blob/main/src/main/java/org/tokenscript/attestation/IdentifierAttestation.java
    // Commitment2: https://github.com/TokenScript/attestation/blob/main/src/main/java/org/devcon/ticket/Ticket.java

I enhanced the comments both in Solidity and Java


Move case-insensitive string definition to foundation

Moves our case-insensitive string type, formerly known as CIName, out of frontend and into foundation where it can be used elsewhere (in preparation for needing it in the new api package).

Hrm, one of the integration builds timed out compiling qscript. Looks like we are right on the edge of the 10m timeout mark. Once @nicflores's S3 work is done we'll only have to compile everything once, so I'm thinking we can wait until that work lands before considering adding back in travis_wait.

appveyor got as far as passing all the tests but then just didn't output a success. Twice. So I'm just going to merge this.


Read fabricDNS from stack config

The provider uses the DEFANG_FABRIC env var as the fabric endpoint to deploy to (defaults to fabric-prod1.defang.dev:443). We should support defang:fabricDNS stack config setting, in addition to the env var. The env var should always override the value stored in stack config.

Only we use FABRIC_DNS internally, so not important.


support exporting TLS secrets in mock

No one really requested this, and I'm not sure if it's worth it, but I like to use wireshark for troubleshooting.
This can be used like this: https://wiki.wireshark.org/TLS#using-the-pre-master-secret
I'm using the vitup binary directly though, using this feature with docker may require some extra configuration, in order to be able to extract the file from the container (setting up a volume?) to provide it to wireshark.
What follows is just the commit message, just leaving it here again since it adds a bit more info.

This can be done by setting the environment variable SSLKEYLOGFILE as
supported by rustls and other common tls implementations.

This is disabled by default in rustls, since of course it can become a
vulnerability to log session secrets, but it's useful for
troubleshooting since it can be used in wireshark (as long as you
capture the handshake, I think), and the mock is used for testing
purposes only anyway.

Unfortunately, warp doesn't expose the setting to configure this on the
inner rustls, and from what I gathered from some discussions in the
repo, I don't think it's intended, since they offer warp::service for
these kind of things, so I used that directly with hyper. This is a bit
more involved, but I don't think it's overly complex, and I didn't find
an easier way anyway.

Hey @enzoc4, if i understand correctly one of the problem is that we need to provide cert files as arguments to vitup, and it could be problematic for docker env. I bumped into same problem when removing http endpoint in vitup (as it is not used anymore by android impl of voting app). I wanted https certs (server.key and ca.crt) to be treated as project resources and automatically available in the code without passing it through command line. I learnt that this is possible using simple: https://doc.rust-lang.org/std/macro.include_str.html, like below:
   server_crt_content: include_str!("../../resources/tls/server.crt").to_string(),
   server_key_content: include_str!("../../resources/tls/server.key").to_string(),

Looking at your changes it can be useful. But  I don't really know if when wireshark is introduced in this picture, before or after you run vitup. If after, then we can just dump this file into local deployment folder (and , if used from docker, just map internal docker fs to host folder, which gives access to that file from host).
Agree that vitup mock is used purely for testing and we are keeping self-signed certs in repo, so we shouldn't care about secrets leakage

Looking at your changes it can be useful. But I don't really know if when wireshark is introduced in this picture, before or after you run vitup. If after, then we can just dump this file into local deployment folder (and , if used from docker, just map internal docker fs to host folder, which gives access to that file from host).

You need to run it before to capture the whole thing. Not necessarily before running vitup, just running it before the first app request is fine, but it may be easier to just capture everything since the app does requests in the background.
If you don't have the file yet you can still save the packet capture, and decrypt it later when you get it. But if the file is available from the start then you can look at the traffic while you try things, so it's a bit nicer. So ideally it would have to be a in a directory available from the host.

Agree that vitup mock is used purely for testing and we are keeping self-signed certs in repo, so we shouldn't care about secrets leakage

And it's still opt-in, since you need to set the environment variable to a valid directory path.

if i understand correctly one of the problem is that we need to provide cert files as arguments to vitup, and it could be problematic for docker env. I bumped into same problem when removing http endpoint in vitup (as it is not used anymore by android impl of voting app). I wanted https certs (server.key and ca.crt) to be treated as project resources and automatically available in the code without passing it through command line. I learnt that this is possible using simple: https://doc.rust-lang.org/std/macro.include_str.html, like below:

I don't understand this part, actually. I don't think I changed the behavior of this. We can certainly inline the certs in the binary if you want, but I'm not sure how is that related to this.

I don't understand this part, actually. I don't think I changed the behavior of this. We can certainly inline the certs in the binary if you want, but I'm not sure how is that related to this.

Oh yes, sorry, I became too greedy and wanted to also wanted to get rid of those input files:
https://github.com/input-output-hk/vit-testing/pull/174/files#diff-92440869a19ac9b45f7bd18ff9e8d2efad530ed50f4c154808b3c7e66f9de10eR459
So my remark was not related to change. I just haven't fully understand wireshark sniffing procedure. After you explained it in next comment, it was clear that it should not be in the scope of those changes. It was just unrelated note. Sorry for confuson

I mean, I don't mind changing that here, I was just not sure what was the problem, since warp was also reading them from the fs.
But I think your point is that with this change it's now possible to avoid reading them, since warp requires a path, but now we don't have that restriction anymore.
I don't mind changing the file read for include_str! if you want (or maybe include_bytes!, actually). It would still need to be parsed at runtime, of course, but if the problem is only having to pass a path through the cli then it should be enough.

Yes, exactly that was my point. I think, let's do it in other pr. We can also refactor migration scripts for vit-servicing-station there

Rebased with newest main

Thanks @enzoc4 for this change!


Move as much as possible into i18n keys

The language switcher is hidden away for now to keep the text translation separate from the integration of keys. (b7ad6dcd8d612055f1dc28b71eda5030c5c49375)
This makes sure that this code can be merged without a proper look at the translations, and that a follow up PR + review, (with little to no code and mostly alterations to the json files) can happen before showing the LanguageSwitcher component.
For pages with a large amount of text I have moved that to a i18n namespace: documentation
For text where translations require React components inbetween I have used the <Trans> component or for basic html strings I use the dangerouslySetInnerHTML={{__html: t('key')}}

@tberm @giuliamml
The PR is ready to be merged IMO,
Translated content improvements for translations can be submitted at https://crowdin.com/project/the-clothing-loop
And dutch translations can be set live at a later date.


Calendar pipe: wrap setTimeout with outsideAngularApp

wrap setTimeout with outsideAngularApp
make initTimer to be not static anymore
#132

Done :)

Sorry, one more fix. Return a timer from runOutsideAngular method to assign it to the CalendarPipe.timer

thanks, looks good!

released as 1.3.3


feat: add support for persistent recursive watches

Why is this needed?
ZooKeeper 3.6.0 added support for persistent, and persistent recursive watches.  This adds the corresponding support to the Kazoo client class.
Does this PR introduce any breaking change?
No breaking changes.

It looks like the test failures are not related to this change.

Hi! Why not merge this?

Hi! Whose approval is need? 🤔

Hello,
Approval from @python-zk/maintainers is needed. Will try to take a look by end of the week.
Can somebody that already tried the feature can confirm it is working as expected?

Hello,
Approval from @python-zk/maintainers is needed. Will try to take a look by end of the week.
Can somebody that already tried the feature can confirm it is working as expected?

While awaiting review/merge we in the Zuul project have vendored a copy[1] of this and used it successfully in production for about nine months (though it does look like our vendored copy omits the ability to remove watches since we never do so, so we'll have to rely on the tests for that).  Thanks for taking a look.  :)
[1] https://opendev.org/zuul/nodepool/src/branch/master/nodepool/zk/vendor

@jeffwidman @ceache @a-ungurianu this one is now ready to be reviewed
@jeblair I made some small changes, mostly based on my previous review, please let me now if you see anything wrong

@jeffwidman @ceache @a-ungurianu this one is now ready to be reviewed @jeblair I made some small changes, mostly based on my previous review, please let me now if you see anything wrong

The changes LGTM, thanks!  And sorry I wasn't able to address those myself in a timely manner.

Thank you @jeblair
@jeffwidman @ceache @a-ungurianu gentle bump!


Building only changed dependant projects

Our scenario is as:
https://github.com/eh-ciellos/Contoso-App2/
We have three projects on the same repo. No other project on other repo is being used as a dependency.
App2 project is the dependency project for App2.it and App2.dk.
So, if App2 has a new change, we should have a full build.
Suppose there are changes in the App2.it, then we need to build App2.it and use the existing latest build for App2 as a dependency.
Our end goal is to have only the changed project built on CICD action if project is not App2. Else all three projects should be built starting from App2(dependency).
 The Pull Request Build action will get triggered and only build this project App2.it.
As soon as I merge the Pull Request to the "main" branch, CICD gets triggered and starts building App2, App2dk, and App2.it, which were not subject to any new committed change.
I believe this is the issue.
Wanted scenario: When I merge the Pull Request to the "main" branch, CICD gets triggered and starts building App2.it only. It must re-use existing latest artifacts for any dependant projects.
What can make us achieve the wanted scenario?
Do you have any suggestions/solutions regarding this issue?
The forked repos to showcase this issue are as below:
https://github.com/eh-ciellos/Contoso-App2
https://github.com/eh-ciellos/AL-Go
https://github.com/eh-ciellos/AL-Go-Actions

For multi-project repositories, the CI/CD pipeline always produces full builds, which can be used for releasing etc. there are many reasons why I really don't want to go away from this.
One being this example:

You checkin a bug in w1 - then that build fails.
Now you checkin a feature in dk - that build uses the latest good w1 build and succeeds.
Now you release - but the source of w1 in the repo is not the same as the app build.

The suggested work mechanism is to have an open Pull Request while finalizing your feature and fixing code review issues. You will have multiple PR builds (which are incremental) and then only one complete build when you merge.
I do see that if you check-in many tiny features this process might not be the best.
You can achieve what you want by splitting your projects into multiple repositories - you could trigger a build in the depending repo when a build in the dependent repo is done.
This isn't supported out-of-the-box in AL-Go for GitHub, but can be achieved by adding a workflow to the depending repository, which gets triggered after successful builds.

If you are worried about the timing, we are working on making builds much faster and splitting test execution from building, so that your workflows will finish much faster.
You can try to add these properties to .github/AL-Go-Settings.json:
useCompilerFolder: true
doNotPublishApps: true
then building will become much faster - but tests are no longer running.
We are working on that part.

You can actually do one more thing - it will still build all projects, but if you instead of useProjectDependencies in .github/AL-Go-Settings.json, then create an appDependencyProbingPaths structure in the .AL-Go/settings.json for each project (like https://github.com/BusinessCentralApps/include) then it will not use nested apps building, but instead build all apps in parallel.

Suppose we opted for splitting our projects into multiple repositories. We ended up with three repositories: App2, App2.it and App2.dk. We made a change to App2.dk, which will use the latest artifact from App2.
What is the purpose of building App2 when the build in App2.dk is done?
Going back to our need for 1 repository with multiple projects.
We are not so worried about timing than having all the projects in one repo for better readability and ease of use on developer side.
This scenario expects App2.dk and App2.it to be built whenever App2 gets a change merged but not the opposite.
However, if a bug was checked in App2 we are not merging the PR until it gets build successfully in the PR. So App2.dk will use the latest artifact and code too since we did not merge it.
Based on this what strategy can we use to have all our projects in one repository?

What is the purpose of building App2 when the build in App2.dk is done?

You would not set it up to build App2 when App2.dk is built - it would be the other way around.
Also, in a setup like this, the code in App2.it and App2.dk is typically very limited and many countries will use w1 (from main repo).
But... - back to having things in one repo - with AL-Go, you would have to live with the system building all projects on commit.
It is a cornerstone in AL-Go to have every CI/CD build being a complete build. I don't see a good way of creating partial commit builds with AL-Go for GitHub.
Sorry.

Both fullBuildPattern and alwaysBuildAllProjects refers to the PullRequest build - not CI/CD (yes, I know documentation is wrong, will fix that).
CI/CD will always produce full builds.


Add PTZ support to Foscam camera component

Description
This PR extends the current foscam component to support PTZ through a service (like the onvif component).
I also took this opportunity to update the module for using the async API.
Pull request with documentation for home-assistant.io: home-assistant/home-assistant.io#10625
Demo

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox.
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @skgsergio,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Addresed all issues and re-tested. Not sure the procedure here, should I squash?

Moved al initialization to async_setup_platform now __init__ doesn't contain logic.
Moved constants to const.
I saw the motion detection logic wasn't ok so I fixed it too in this commit.
Addressed the rest of the comments.

Can be merged when build passes.

Thank you for your contribution thus far! 🎖 One final thing: Since this is a significant contribution, we would appreciate you'd added yourself to the list of code owners for this integration. ❤
Please, add your GitHub username to the manifest.json of this integration.
For more information about "code owners", see: Architecture Decision Record 0008: Code owners.

Done 👍 and thank everyone for the project and the awesome help with the PR (next time I'll have the guidelines more clear 😂)

Well, the opposite is the case: Thank you sir! 🎉


Updated: postman-canary 7.3.5-canary04

Newer version of postman-canary (7.11.0-canary01) is now available in master.


Synthesis failed for java-iot

Hello! Autosynth couldn't regenerate java-iot. :broken_heart:
Here's the output from running synth.py:
oud/iot/v1/RegistryName.java.
2020-07-12 17:39:11,928 synthtool [INFO] > Replaced '/\\*\n \\* Copyright \\d{4} Google LLC\n \\*\n \\* Licensed under the Apache License, Version 2.0 \\(the "License"\\); you may not use this file except\n \\* in compliance with the License. You may obtain a copy of the License at\n \\*\n \\* http://www.apache.org/licenses/LICENSE-2.0\n \\*\n \\* Unless required by applicable law or agreed to in writing, software distributed under the License\n \\* is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express\n \\* or implied. See the License for the specific language governing permissions and limitations under\n \\* the License.\n \\*/\n' in /tmpfs/tmp/tmpt1bnhwzj/google-cloud-iot-v1-java/proto-google-cloud-iot-v1-java/src/main/java/com/google/cloud/iot/v1/DeviceName.java.
2020-07-12 17:39:11,931 synthtool [INFO] > Replaced '^package (.*);' in /tmpfs/tmp/tmpt1bnhwzj/google-cloud-iot-v1-java/grpc-google-cloud-iot-v1-java/src/main/java/com/google/cloud/iot/v1/DeviceManagerGrpc.java.
2020-07-12 17:39:11,957 synthtool [WARNING] > No files in sources [PosixPath('/tmpfs/tmp/tmpt1bnhwzj/google-cloud-iot-v1-java/gapic-google-cloud-iot-v1-java/samples/src')] were copied. Does the source contain files?
2020-07-12 17:39:11,957 synthtool [WARNING] > No files in sources [PosixPath('/tmpfs/tmp/tmpt1bnhwzj/google-cloud-iot-v1-java/gapic-google-cloud-iot-v1-java/samples/resources')] were copied. Does the source contain files?
2020-07-12 17:39:11,957 synthtool [WARNING] > No files in sources [PosixPath('/tmpfs/tmp/tmpt1bnhwzj/google-cloud-iot-v1-java/gapic-google-cloud-iot-v1-java/samples/src/**/*.manifest.yaml')] were copied. Does the source contain files?
2020-07-12 17:39:11,958 synthtool [INFO] > Running java formatter on 12 files
2020-07-12 17:39:15,125 synthtool [INFO] > Running java formatter on 1 files
2020-07-12 17:39:17,683 synthtool [INFO] > Running java formatter on 88 files
2020-07-12 17:39:26,222 synthtool [INFO] > Running java formatter on 0 files
2020-07-12 17:39:26,607 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
.github/CODEOWNERS
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.github/trusted-contribution.yml
.github/workflows/ci.yaml
.kokoro/build.bat
.kokoro/build.sh
.kokoro/coerce_logs.sh
.kokoro/common.cfg
.kokoro/common.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/dependencies.cfg
.kokoro/continuous/integration.cfg
.kokoro/continuous/java11.cfg
.kokoro/continuous/java7.cfg
.kokoro/continuous/java8-osx.cfg
.kokoro/continuous/java8-win.cfg
.kokoro/continuous/java8.cfg
.kokoro/continuous/lint.cfg
.kokoro/continuous/propose_release.cfg
.kokoro/continuous/samples.cfg
.kokoro/dependencies.sh
.kokoro/linkage-monitor.sh
.kokoro/nightly/common.cfg
.kokoro/nightly/dependencies.cfg
.kokoro/nightly/integration.cfg
.kokoro/nightly/java11.cfg
.kokoro/nightly/java7.cfg
.kokoro/nightly/java8-osx.cfg
.kokoro/nightly/java8-win.cfg
.kokoro/nightly/java8.cfg
.kokoro/nightly/lint.cfg
.kokoro/nightly/samples.cfg
.kokoro/populate-secrets.sh
.kokoro/presubmit/clirr.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/dependencies.cfg
.kokoro/presubmit/integration.cfg
.kokoro/presubmit/java11.cfg
.kokoro/presubmit/java7.cfg
.kokoro/presubmit/java8-osx.cfg
.kokoro/presubmit/java8-win.cfg
.kokoro/presubmit/java8.cfg
.kokoro/presubmit/linkage-monitor.cfg
.kokoro/presubmit/lint.cfg
.kokoro/presubmit/samples.cfg
.kokoro/release/bump_snapshot.cfg
.kokoro/release/common.cfg
.kokoro/release/common.sh
.kokoro/release/drop.cfg
.kokoro/release/drop.sh
.kokoro/release/promote.cfg
.kokoro/release/promote.sh
.kokoro/release/publish_javadoc.cfg
.kokoro/release/publish_javadoc.sh
.kokoro/release/snapshot.cfg
.kokoro/release/snapshot.sh
.kokoro/release/stage.cfg
.kokoro/release/stage.sh
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
codecov.yaml
java.header
license-checks.xml
renovate.json
samples/install-without-bom/pom.xml
samples/pom.xml
samples/snapshot/pom.xml
samples/snippets/pom.xml
2020-07-12 17:39:26,769 synthtool [DEBUG] > existing pom file found (samples/pom.xml) - keeping the existing
2020-07-12 17:39:26,769 synthtool [DEBUG] > existing pom file found (samples/snippets/pom.xml) - keeping the existing
2020-07-12 17:39:26,769 synthtool [DEBUG] > existing pom file found (samples/install-without-bom/pom.xml) - keeping the existing
2020-07-12 17:39:26,770 synthtool [DEBUG] > existing pom file found (samples/snapshot/pom.xml) - keeping the existing
2020-07-12 17:39:26,770 synthtool [DEBUG] > Wrote metadata to synth.metadata.
2020-07-12 17:39:26,827 autosynth [INFO] > Changed files:
2020-07-12 17:39:26,827 autosynth [INFO] > M synth.metadata
2020-07-12 17:39:26,827 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 7948d18 ci(java): run dependency test on Java 8 and 11 (#185)
2020-07-12 17:39:26,834 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-07-12 17:39:26,840 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 677, in urlopen
    chunked=chunked,
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 426, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 421, in _make_request
    httplib_response = conn.getresponse()
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/http/client.py", line 1346, in getresponse
    response.begin()
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/http/client.py", line 307, in begin
    version, status, reason = self._read_status()
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/http/client.py", line 276, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 725, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/util/retry.py", line 403, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/packages/six.py", line 734, in reraise
    raise value.with_traceback(tb)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 677, in urlopen
    chunked=chunked,
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 426, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/urllib3/connectionpool.py", line 421, in _make_request
    httplib_response = conn.getresponse()
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/http/client.py", line 1346, in getresponse
    response.begin()
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/http/client.py", line 307, in begin
    version, status, reason = self._read_status()
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/http/client.py", line 276, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 657, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 506, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 637, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 364, in synthesize_loop
    if change_pusher.check_if_pr_already_exists(fork.branch):
  File "/tmpfs/src/github/synthtool/autosynth/change_pusher.py", line 117, in check_if_pr_already_exists
    prs = self._gh.list_pull_requests(repo, state="open", head=f"{owner}:{branch}")
  File "/tmpfs/src/github/synthtool/autosynth/github.py", line 60, in list_pull_requests
    response = self.session.get(url, params=kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/requests/sessions.py", line 543, in get
    return self.request('GET', url, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/requests/sessions.py", line 530, in request
    resp = self.send(prep, **send_kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/requests/sessions.py", line 643, in send
    r = adapter.send(request, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/requests/adapters.py", line 498, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Deliberately  trigger CI workflows based on what files were changed

Which issue does this PR close?
Closes https://github.com/apache/arrow-rs/issues/2149
This is the final part of the CI workflow I have planned under the aegis of that https://github.com/apache/arrow-rs/issues/2149 😓
Rationale for this change
Right now we run almost all CI checks for all PRs even those that make no code changes (changes to README, etc) or changes to some other crate (e.g. change in arrow-flight can't affect parquet yet we run all the parquet checks anyways)
This increases PR times in two ways: 1 more checks need to complete and 2.  we consume many github action builder minutes on useless tests, which increases the time spent waiting for a builder on the queue.
Of course, there is a real possibility that this change may miss running a CI check that causes master to fail -- but I think the improved PR speed and test specificity will make up for any such mishaps. We can also always go back to running all the tests on all PRs
What changes are included in this PR?
The basic idea is to run all tests on pushes to master (to keep master green) but only run the individual workflows on PRs that change files that could affect them.
Are there any user-facing changes?
No

Codecov Report

Merging #2213 (340a7be) into master (bc493d9) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2213   +/-   ##
=======================================
  Coverage   82.56%   82.57%
=======================================
  Files         239      239
  Lines       62269    62269
=======================================
+ Hits        51415    51417    +2
+ Misses      10854    10852    -2

Impacted Files
Coverage Δ

parquet/src/encodings/encoding.rs
93.62% <0.00%> (+0.19%)
:arrow_up:

...rquet/src/arrow/record_reader/definition_levels.rs
89.02% <0.00%> (+0.42%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.

🚀


Using forEach instead of map as its return value is not being used

Using forEach instead of map as its return value is not being used

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.50%. Comparing base (13484d0) to head (fc3114e).
Report is 64 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1341      +/-   ##
==========================================
- Coverage   36.81%   36.50%   -0.31%
==========================================
  Files         158      159       +1
  Lines        2548     2586      +38
  Branches      599      605       +6
==========================================
+ Hits          938      944       +6
- Misses       1428     1460      +32
  Partials      182      182

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


creating linked service and authorization

Customers requested docs to reflect proper authorization by author might be other than the ones given to the identity, but to create pipeline they were not aware that the author needs access. This note is to reflect this concept.

Learn Build status updates of commit 606e0f6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/data-factory/concepts-linked-services.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@dcstwh

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

Note: images can't be hosted outside of the repo. To move forward, the image will need to be moved into the correct folder in the repo. the alt text is also not in compliance with the accessibility guidelines.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for your commitment to the documentation!  This change is implemented and merged now and should be published in the next 24 hours.  #please-close


Presentation: Fix NestedContentField copy constructor

We didn't update child fields' parent pointer after cloning them...

@mergifyio backport release/4.x


support crypto primitives for no_std

This adds a new compiler feature with_crypto to

substrate-primitives
substrate-application-crypto

Why
The upstream logic knows only two use cases:

within a std environment -> use crypto primitives like sr25519::Pair
within wasm, a no_std environment with the goal of yielding lightweight binaries -> use host calls for crypto primitives

As we use substrate-primitives within an SGX enclave to sign extrinsics, we're actually adding a third use case:

within a no_std environment but needing crypto primitives -> no solution so far.

So far, we just patched cargo dependencies to our own fork of these substrate crates, but this is hard to maintain and we think others might benefit from our generalization.
CI
In order to make sure we can test this new feature automatically, we wrote a minimal crate:
https://github.com/scs/test-no-std/tree/substrate-primitives
unfortunately, the linker still fails, but as long as there is no duplicate lang itemerror, the build is to be considered a success.
TODO
This PR isn't fully functional yet. The two crates build, but the node doesn't. Before I put more effort into this I'd like to ask you if this PR has a chance to get merged into master.

Is rand appearing here?  We've reached rand 0.7 by now?
As I've noted before https://github.com/w3f/schnorrkel/issues/31#issuecomment-520213230 I think rand_os activates std before 0.2.1, so before rand 0.7.  We avoid OsRng, ThreadRng, etc. on chain, but require roughly OsRng for substraTEE, etc.
We'll want RngCore5As4 from https://github.com/w3f/schnorrkel/commit/8150ef6333df6238d8d861aec74bf7ccd87119aa if we want both ed25519-dalek and rand_core 0.5 (rand 0.7).  Are cargo features an issue?  I think not..

@burdges: What we need for substraTEE are: signing & verifying and hashing. For random we use Intel SGX features.
This also means we're not actually using Schnorrkel ourselves within the enclave, because - in contrast to ed25519 - sr25519 seems to require random for deriving a keypair from a seed. So we want to verify sr25519 signatures, but for signing we use an ed25519 pair.
I'm not sure I understand your remarks. no_std works for us in the enclave with sr25519 and ed25519. However, because of a cargo bug, we still need to patch to avoid duplicate lang item std:
[patch.crates-io]
ed25519-dalek = { git = "https://github.com/scs/ed25519-dalek.git", branch = "no_std_sgx"}

added CI comments ^^^^

sr25519 seems to require random for deriving a keypair from a seed.

We do not require randomness when expanding a keypair from a seed:
https://docs.rs/schnorrkel/0.1.1/src/schnorrkel/keys.rs.html#114
We do use randomness when doing HDKD in https://docs.rs/schnorrkel/0.1.1/src/schnorrkel/derive.rs.html#177 which I should probably replace with a t.witness_bytes call so that you can replace thread_rng  using attach_rng.  I tried to write the code more semantically once upon a time, but this'll make more sense now I think.  Thanks!

@burdges: thanks for your helpful hints. This means we actually might use sr25519 keys for our enclave.
However: I consider this off-topic for this PR.

@bkchr, @kianenigma: This PR just got flagged "in progress". While it's true that it is not ready for merging/review, I'd like to ask you for a statement if you are willing to accept our added use case and the approach of this PR

yeah; looks reasonable to me.

@brenzi you need to update the Cargo.lock and commit that. (Just run cargo build for a moment)

It appears to me that cargo doesn't forward features correctly:
error[E0412]: cannot find type `Pair` in module `app`
  --> core/finality-grandpa/primitives/src/lib.rs:38:31
   |
38 | pub type AuthorityPair = app::Pair;
   |                               ^^^^ not found in `app`
help: possible candidates are found in other modules, you can import them into scope
   |
25 | use app_crypto::Pair;
   |
25 | use app_crypto::ed25519::Pair;
   |
25 | use app_crypto::sr25519::Pair;
   |
25 | use sr_primitives::testing::sr25519::Pair;
   |

error[E0277]: the trait bound `app::Signature: std::hash::Hash` is not satisfied
  --> core/finality-grandpa/primitives/src/lib.rs:33:2
   |
33 |     app_crypto!(ed25519, GRANDPA);
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::hash::Hash` is not implemented for `app::Signature`
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

@bkchr: do you have a clue?

oops, sorry, that was too quick. The following still fails:
cargo build -p substrate-primitives --no-default-features --features full_crypto

I'd suggest to include this line in CI. How should I proceed to do that?

oops, sorry, that was too quick. The following still fails:
cargo build -p substrate-primitives --no-default-features --features full_crypto

I'd suggest to include this line in CI. How should I proceed to do that?

Are you familiar with gitlab ci? You just need to edit .gitlabci.yml. I would propose you copy the srml-staking test and modify for your needs.

@bkchr It seems I broke the CI script:
Running with gitlab-runner 12.4.1 (05161b14)
  on ci2-docker 8a60f15c
Using Docker executor with image parity/rust-builder:latest ...
ERROR: Preparation failed: Error response from daemon: Conflict. The container name "/runner-8a60f15c-project-145-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8" is already in use by container "81f69a0237714f11351d20325b818d3400aa19476e4057b1d43bcaefcfbe0075". You have to remove (or rename) that container to be able to reuse that name. (cache_container.go:97:0s)
Will be retried in 3s ...

but why and how?

@bkchr: It seems that my new CI test is not run:
https://github.com/paritytech/substrate/blob/536d6c3df57c6f4f53f7ecb0b968a541a1735eee/.gitlab-ci.yml#L274

I'll have to put this on wait because it seem's the latest version causes no_std collisions when testing against https://github.com/scs/test-no-std/tree/substrate-primitives.
I'll revert once that's fixed

the last commit fixes it. My only remaining question is if my new CI test is actually running.

could we include building https://github.com/scs/test-no-std/tree/substrate-primitives in CI as well? It's a minimal crate that checks for no_std collisions. Maybe you already have means to test such things for wasm? Better ways?

Ty!

@bkchr thanks for your patience and support too.


Update JobType Cache and Assignment Endpoint to use inlineCallbacks

This PR reworks the internal cache for jobtypes.  The main goals of this PR are to:

Convert to inlineCallbacks
Improve caching behavior, especially between cached and uncached modes.
Fix a few subtle bugs in the jobtype cache.
Update the assignment endpoint to use the new  inlineCallbacks to match the new cache implementation

Work in progress.

Coverage increased (+0.48%) to 75.17% when pulling 42287964e1e302ed40ae65eddebb032fee94c87c on ilc_jobtype_cache into 7fbcfa3faeba5e775460e99f86874ea109561969 on master.

Coverage increased (+0.85%) to 75.54% when pulling 3efcbdd223565d1681ee8a23e5ad47d3a2bd0bfd on ilc_jobtype_cache into 7fbcfa3faeba5e775460e99f86874ea109561969 on master.

Coverage increased (+0.85%) to 75.54% when pulling 15414145c19575f1ec5e56eae1b5938577b4242b on ilc_jobtype_cache into 7fbcfa3faeba5e775460e99f86874ea109561969 on master.

Coverage increased (+1.17%) to 75.86% when pulling 3a9765913eb311e55fef34c21f0bc0b15db5318e on ilc_jobtype_cache into 7fbcfa3faeba5e775460e99f86874ea109561969 on master.

Coverage increased (+1.4%) to 76.09% when pulling 124a4bc469b74d47dfebc46f131f4b82522b51b3 on ilc_jobtype_cache into 7fbcfa3faeba5e775460e99f86874ea109561969 on master.

Coverage increased (+1.4%) to 76.13% when pulling 65141f0b5dd2d4b61fadbec2a4c2ede8b3971379 on ilc_jobtype_cache into 16f2dfd99e5894efb32dd1753c439ca8758ce1c7 on master.

Coverage increased (+1.4%) to 76.13% when pulling 65141f0b5dd2d4b61fadbec2a4c2ede8b3971379 on ilc_jobtype_cache into 16f2dfd99e5894efb32dd1753c439ca8758ce1c7 on master.

Coverage increased (+1.4%) to 76.13% when pulling 7f9b891ea18110ae2a0a16e9e3e86d0f1e700a8e on ilc_jobtype_cache into 16f2dfd99e5894efb32dd1753c439ca8758ce1c7 on master.

Coverage increased (+1.4%) to 76.13% when pulling 7f9b891ea18110ae2a0a16e9e3e86d0f1e700a8e on ilc_jobtype_cache into 16f2dfd99e5894efb32dd1753c439ca8758ce1c7 on master.

Coverage increased (+1.4%) to 76.12% when pulling e40131a7f82383d705356460a9a0a6401d51fbd0 on ilc_jobtype_cache into d7399ec3aaeeb1a0f13b3c7478cbfdf9f9d4bdbe on master.

Coverage increased (+1.73%) to 76.45% when pulling d3cd51b70c90ea037adf9565efdb526a2ef50cf5 on ilc_jobtype_cache into d7399ec3aaeeb1a0f13b3c7478cbfdf9f9d4bdbe on master.

Coverage increased (+1.73%) to 76.45% when pulling 2b59991815197c4ae70585abd0ff581cf5de4cb8 on ilc_jobtype_cache into f0bfe17535d1297495b7bd261b56be3a3d0f694c on master.

Coverage increased (+1.72%) to 76.55% when pulling 9b8559a6eaf2c35b2b784910d8d8312cbaa29fdd on ilc_jobtype_cache into 5ac3facf9e13ae3d7a8c7d96ab856dc142262922 on master.

Coverage increased (+1.72%) to 76.55% when pulling 9b8559a6eaf2c35b2b784910d8d8312cbaa29fdd on ilc_jobtype_cache into 5ac3facf9e13ae3d7a8c7d96ab856dc142262922 on master.

Coverage increased (+1.72%) to 76.22% when pulling 9317e78c9b2329e1e1157659f3aa192150570430 on ilc_jobtype_cache into 8ae18f662658b777f8487e67d46127809ef44d12 on master.

Coverage increased (+1.72%) to 76.22% when pulling 9317e78c9b2329e1e1157659f3aa192150570430 on ilc_jobtype_cache into 8ae18f662658b777f8487e67d46127809ef44d12 on master.

Coverage increased (+1.72%) to 76.22% when pulling 9317e78c9b2329e1e1157659f3aa192150570430 on ilc_jobtype_cache into 8ae18f662658b777f8487e67d46127809ef44d12 on master.

Coverage increased (+1.62%) to 77.78% when pulling d1f04e1bc0b27355ecee21b71ba1a7c6ef8401b9 on ilc_jobtype_cache into 18898f1178deb2be52a3fcb587c0d0a6f36ea236 on master.

Coverage increased (+1.78%) to 77.94% when pulling a133a01b474360b8002d9d4e3aa6e6fd099d3846 on ilc_jobtype_cache into 606c36600da25a8350b3dca9be34833f4400b1e7 on master.

Coverage increased (+1.78%) to 77.94% when pulling 3e5310c05b8c9cb4ced0695dcf90da274b683b99 on ilc_jobtype_cache into 606c36600da25a8350b3dca9be34833f4400b1e7 on master.

Coverage increased (+1.78%) to 77.94% when pulling 8a2ad7878974287691b2fcbbd7e9df9d75cce996 on ilc_jobtype_cache into 606c36600da25a8350b3dca9be34833f4400b1e7 on master.

Coverage increased (+1.98%) to 78.14% when pulling<PHONE_NUMBER>9f90809b15b8c983a6354e4bf9f0ea on ilc_jobtype_cache into 606c36600da25a8350b3dca9be34833f4400b1e7 on master.

Coverage increased (+1.98%) to 78.14% when pulling<PHONE_NUMBER>9f90809b15b8c983a6354e4bf9f0ea on ilc_jobtype_cache into 606c36600da25a8350b3dca9be34833f4400b1e7 on master.

@guidow, PTAL.  It's going to need some additional testing but I think this is ready for a review.

This branch will fail to load a jobtype with the following error:
2015-04-07 14:40:24 DEBUG    - HTTPChannel,4,<IP_ADDRESS> - "<IP_ADDRESS>" - - [07/Apr/2015:12:40:23 +0000] "POST /api/v1/assign HTTP/1.1" 202 50 "-" "PyFarm/1.0 (master)"
2015-04-07 14:40:24 INFO     - pf.agent.http.assign - Accepted assignment e62aab4b-6c40-46f3-916a-f267687b0100: {u'job': {u'ram_max': None, u'title': u'Massive test 36', u'ram': 32, u'batch': 5, u'cpus': 1, u'environ': {}, u'user': u'guido', u'id': 36, u'data': {u'output': u'/tmp/stift_####.exr', u'scene_file': u'/home/guido/stift_aniex43_finish.blend'}, u'by': 1.0, u'ram_warning': None}, u'tasks': [{u'frame': 141.0, u'attempt': 2, u'id': 17641}, {u'frame': 142.0, u'attempt': 2, u'id': 17642}, {u'frame': 143.0, u'attempt': 2, u'id': 17643}, {u'frame': 144.0, u'attempt': 2, u'id': 17644}, {u'frame': 145.0, u'attempt': 2, u'id': 17645}], 'id': UUID('e62aab4b-6c40-46f3-916a-f267687b0100'), u'jobtype': {u'version': 10, u'name': u'Render With Blender'}}
2015-04-07 14:40:24 INFO     - pf.jobtypes.core - Downloading http://<IP_ADDRESS>:5000/api/v1/jobtypes/Render With Blender/versions/10
2015-04-07 14:40:24 DEBUG    - HTTPChannel,4,<IP_ADDRESS> - Starting factory <twisted.web.client._HTTP11ClientFactory instance at 0x7f8cf75ddbd8>
2015-04-07 14:40:24 ERROR    - pf.agent.http.client - GET http://<IP_ADDRESS>:5000/api/v1/jobtypes/Render With Blender/versions/10 has failed (uid: e698d333ee50):
Traceback (most recent call last):
Failure: twisted.web._newclient.ResponseFailed: [<twisted.python.failure.Failure <class 'twisted.web._newclient.ParseError'>>]

2015-04-07 14:40:24 ERROR    - pf.jobtypes.core - Error while attempting to download 'http://<IP_ADDRESS>:5000/api/v1/jobtypes/Render With Blender/versions/10': [<twisted.python.failure.Failure <class 'twisted.web._newclient.ParseError'>>]
2015-04-07 14:40:24 ERROR    - pf.agent.http.assign - Loading jobtype for assignment e62aab4b-6c40-46f3-916a-f267687b0100 failed, removing.
2015-04-07 14:40:24 DEBUG    - pf.agent.http.assign - Got traceback
2015-04-07 14:40:24 ERROR    - pf.agent.http.assign - Traceback (most recent call last):
Failure: twisted.web._newclient.ResponseFailed: [<twisted.python.failure.Failure <class 'twisted.web._newclient.ParseError'>>]

2015-04-07 14:40:24 DEBUG    - pf.agent.http.assign - Marking tasks in assignment as failed

Meanwhile on the master, I see this error message:
2015-04-07 14:40:24 ERROR    - werkzeug        - <IP_ADDRESS> - - [07/Apr/2015 14:40:24] code 400, message Bad request syntax ('GET /api/v1/jobtypes/Render With Blender/versions/10 HTTP/1.1')

Would you mind explaining a bit more how this PR actually improves things? What I am seeing here is mostly redoing things that were already working and had most of their bugs ironed out already in a slightly different way that introduces new bugs...

The main improvements that this PR is trying to make are a few things:

Finer grained threading.  Before we were sending larger portions of code into treads when we really only needed to thread a couple of operations to eliminate potential points where the reactor could be blocked.
Locks around portions of the code where we're interacting with the cache.  Before it was possible to update the cache and before we 'check' it again.
Fixed cached/uncached behaviors.  "Disabled caching" didn't actually exist before because it wouldn't always retrieve the updated job type and it would still cache the module on every call which is not a behavior you'd expect when something is uncached.
A few other minor improvements mainly focused on reducing the number of different methods we need to implement JobType.load (which makes it easier to understand) and improving testability.
Conversion to inlineCallbacks.  This improves on the readability quite a bit and also simplifies the flow some.  It's also less prone to swallowing errors in unexpected ways.

Functionally speaking there are not a great deal of differences here that should break anything, most of this was focused on improving what we already have and eliminating bugs we would have eventually hit.  But obviously there's something I've missed here (sorry, again).  It probably has to do with the way the tests were written and/or how the request is made to the master so I'll looking into this deeper from that perspective before another review.

Coverage increased (+1.99%) to 77.4% when pulling a35c16be9f64aede4153919450205114397a838a on ilc_jobtype_cache into db108e52341a3ec6b086f9c3b74e003444a28239 on master.

@guidow, I know this has some merge conflicts and some things that need to be updated.  If I can get this in working order again would you mind having another look?

I'm going to go ahead and abandon this:

It's a rather large PR, it should be broken down more.
Let's get better test coverage first.
There's a lot of little changes which conflict with this and because it's new code it will be easier to introduce subtle bugs.


Fix/api token

Hey @alyssais,
First of all, thank you for this tool!
Unfortunately, I've encountered several issues while trying to setup it:

api_token was unbound in configure script, so it failed to complete
in the humans script you are using access_token instead of api_token

So these two commits address these issues.
Let me know if I missed anything and it's not a bug, but a problem in my usage :smiley_cat:

Thanks for the fix! One question — when you run ./configure, does the generated config.sh file include the API token?

When you run configure on non-private repository it includes access_token='' at the end of file. But it doesn't write passed token for private repositories. And it didn't before my changes. I am going to fix that in separate PR, but tomorrow 😸

Sure, yeah, that's what I was thinking. i_api_token's value needs to be assigned to api_token after it's configured.

Hey, @alyssais
After my latest commit it sets access token in config.sh file.

I no longer actively use this project so it's difficult for me to properly confirm it works, but if you say it does, that's good enough for me!

😸 😈
Thanks for merging!


CLI - Do not redirect log messages to the console

As a temporary workaround one can run the cli like that:
cargo run 2>> stderr.log

And in another terminal see the logs using tail -f stderr.log

Fixed by #344?

Fixed by #343


Shifter: Games: Tools for decouple deform and control rig

From @miquelcampos on October 13, 2017 5:25
-export import jnt connections
-Decouple for easy FBX export of deformation joints and geometry
Copied from original issue: mgear-dev/mgear#64

This issue was moved to mgear-dev/shifter#6


Refactor and use ORM for grapher inserts

Problem
We're going to change our MySQL schema as part of new data architecture. Current grapher code that interacts with MySQL was copied from importers repo and uses raw SQL queries. That is not bad by itself, but given the changes ahead it makes sense to clean it up and try to simplify it and typecheck with ORM.
Solution
Rewrite db_utils.py and grapher_import.py with SQLModel ORM and see whether it improves code readability and speed.

Cool! I'm all for the type-checking, and an ORM will probably make for better code, though you might end up just escaping it for the performance critical parts.

though you might end up just escaping it for the performance critical parts.

That's the plan for data_values, luckily other MySQL interactions are not bottlenecks (moreover I've profiled it already and it's only 10% slower).


Added flower-shop-project

I have designed the frontend part of the ecommerce flower shop website.

I have added. Thank you @Ayeshashaik759 . Happy Hactoberfest   2022

Give Star if you think it will help you .

Star given already 😊


Fix testcase

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #903 (38d6673) into master (66e779c) will increase coverage by 0.24%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #903      +/-   ##
============================================
+ Coverage     76.23%   76.47%   +0.24%
- Complexity     1852     1862      +10
============================================
  Files           307      308       +1
  Lines          6972     6976       +4
  Branches        791      791
============================================
+ Hits           5315     5335      +20
+ Misses         1252     1236      -16
  Partials        405      405

Impacted Files
Coverage Δ
Complexity Δ

.../dromara/soul/client/common/utils/OkHttpTools.java
94.28% <100.00%> (ø)
7.00 <2.00> (ø)

...pringcloud/SoulSpringCloudClientConfiguration.java
100.00% <0.00%> (ø)
4.00% <0.00%> (?%)

...che/dubbo/ApacheDubboServiceBeanPostProcessor.java
83.58% <0.00%> (+4.47%)
13.00% <0.00%> (+2.00%)

...ba/dubbo/AlibabaDubboServiceBeanPostProcessor.java
83.58% <0.00%> (+4.47%)
13.00% <0.00%> (+2.00%)

...soul/client/sofa/SofaServiceBeanPostProcessor.java
37.09% <0.00%> (+16.12%)
7.00% <0.00%> (+2.00%)

Continue to review full report at Codecov.

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


available_ips() returns only partial list

available_ips method does not return full list of devices that are available in the prefix but just a subset (the maximum value it returns is 50 ip address):

print(x)
[<IP_ADDRESS>/24, <IP_ADDRESS>/25, <IP_ADDRESS>/24, <IP_ADDRESS>/23, <IP_ADDRESS>/24, <IP_ADDRESS>/24, <IP_ADDRESS>/25, <IP_ADDRESS>/24]
type(x[0])
<class 'pynetbox.models.ipam.Prefixes'>
print(len(x[0].available_ips.list()))
50

It works very well for prefix lenght from /31 to /27 but when the number of available IPs is larger then 50 you won't get that information.
How we can deal with this issue? How can I display complete list?

This is because NetBox only returns the amount PAGINATE_COUNT is set to. You can have a look a more detailed explanation if you pull up the endpoint in a browser (/api/ipam/prefixes/:id/available-ips/).


Support for markup in drag element

Item 1

Item 2

Item 3

Item 4

Item 5

Item 6

We want to display more information within the drag element (the example is simple; In reality there will be a img and some additional spans/labels).
Everything is working fine but i get a DOMException in vue-draggable.js@662 with the message: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.
So i wrapped the code in try catch and everything meets my expectations, but i think this should not be the general solution.
I would love to help with this Feature Request but need some input how it should be done?
I could imagine something like going upword in the dom until i find a li ?

@ThomasKlessen Thanks for opening issue... You are right, try-catch isn't good solution for this. This must be handled by library itself. I will try to fix this as soon as possible and publish new version to npm. I will add some tests later, so this situation will be covered.

@ThomasKlessen This issue should be fixed with v1.0.6.
Please let us know whether you are still facing the problem. 😄

solved issue 🚀


Support views in migrations

The idea is to introduce functions called view/1 and view/2 such that:
create view(:my_view, from(u in "users", where: u.type == :student))
drop view(:my_view)

create requires a query to be given to the view, drop does not.
We will also introduce a create_or_replace/1 function, similar to create/1, but mean to be used with views.

Definitely want that, I have a few view's in my system right now but I setup and tear them down via SQL.

Will be keeping an eye on this. The frontend to one of our biggest apps relies fairly heavily on views, would be very nice to manage them natively

What about materialized views?

@joshuataylor we can support a :materialized option in view/3 or a materialized_view/2 function as well. I will need to study the behaviour in different databases before deciding which one works best.

can i work on this one?

Yes, please!

I was just thinking about introducing it by myself. What would be useful with this one is:

triggers
functions

As it would allow us to create additional things that would be useful with views.

We should carefully consider if we're able in any way to provide something more usable than execute(SQL).
I'm not sure I can imagine providing something more than
create function("""
some sql
""")

and I'm not sure I see advantage over
execute """
CREATE FUNCTION some sql
"""

@michalmuskala there is one: autocreate down method for rollbacks. However there is only a little (if any) advantage of doing that. Maybe except allowing to reference function types using Ecto.Type.type/0 which would be handy.

Hi, I want to start contributing to Ecto (and Elixir in general) and I was about to suggest this feature. Is anyone working on it? Is it still in discussion? I am new to open source projects so forgive me if I don't understand part of the workflow on this. Thanks!

I don't think there is someone working on it right now. If you want to start contributing on this area, maybe #1832 is a better starting point, for you to get acquainted with the codebase. :)

@josevalim Nice, I will try that. Tks

We have stepped down from this feature because using Ecto.Query to generate views had unwarranted side-effects. A discussion of other approaches, which could be encapsulated in helpers that will be part of future Ecto versions, can be found in #1805.

Sooo, currently the only way is still execute()? I've already used the from() syntax to create my 20 queries, any way to put those into the execution string?

@KristerV you can use Repo.to_sql to get those queries as SQL statements. But it is probably best if you still pass them as strings.

Yeah I realized, that your migrations need to be static (and not connected to any schemas or anything), so best is raw strings anyway. For future lurkers :)


Variant of ResetPasswordConfirm that validates a token

Idea for an enhancement: it would be great to have an endpoint where a token could be checked for validity, without submitting a new password.
This would fit into the SPA architecture by allowing the app to present an error page instead of a password-reset form if the page is loaded with an invalid token. Otherwise the user has to try submitting the password change request before getting a rejection.
This might be done with an additional param on ResetPasswordConfirm, or a separate view altogether.

This would definately improve UX!
If anyone is up, I'll accept a merge request for this. It basically only means to adapt the code here to allow the token to be verified without a password:
https://github.com/anx-ckreuzberger/django-rest-passwordreset/blob/7118d430d4b21f78a23530c88a33390c9b6a4f95/django_rest_passwordreset/views.py#L26-L47

Thanks to the help of @Hall-Erik and MR #60 we just released this feature on PyPi in version 1.1.0rc3.
You should be able install and test it using
pip install django-rest-passwordreset==1.1.0rc3

Looks/works great. Thank you!

Hey guys! Is this issue still open?


TAKES 1 POSITIONAL ARGUMENT BUT TWO WERE GIVEN

Using tweepy version 4.6.0
`access_token = "######"
access_token_secret = "######"
API_KEY = "#######"
API_SECRET_KEY = "######"
bearer_token = "#######"
import tweepy
client = tweepy.Client(
bearer_token=bearer_token,
consumer_key=API_KEY,
consumer_secret=API_SECRET_KEY,
access_token=access_token,
access_token_secret=access_token_secret,
)
client.create_tweet("testing")`
There seem to be an issue with the create_tweet() function, it returns
TypeError:  get_users()  takes 1 positional argument but 2 were given. The  get_user() `  function returns same too

Client.create_tweet, Client.get_users, and Client.get_user do not accept any positional arguments. The 1 positional argument being referred to in the error is self.
You likely want to pass "testing" as the text kwarg instead.
For code block usage, see https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.


Fix most of the issues picked up by SwiftLint

This is great, thanks!

@swift-ci please smoke test


Documentation:  Add example to filter_extreme for pre-filtering the input dataset

Please select a category the issue is focused on?
Function Documentation
Let us know where something needs a refresh or put your idea here!
Add example to filter_extreme for pre-filtering the input dataset

Hi, is this request require adding example of the ex dataset before filtering first/last?

The issue was created to address the following tester feedback.

Passed, but one comment. I felt having one more argument like 'filter' would allow to get the extreme observations within the filtering conditions.

The admiral team decided not to add a filter parameter as the input dataset can be easily restricted by calling filter() before filter_extreme(). An example should be added to demonstrate it. Something like
ex %>%
  filter(<a condition>) %>%
  filter_extreme(...)


feat: added desc

checklist: http://www.apache.org/foundation/marks/pmcs#checklist

[x] Desc on the homepage;
[x] Check ASF Links at homepage's bottom.;
[x] Check all titles are Apache APISIX;

close #72

@moonming Please help to check http://www.apache.org/foundation/marks/pmcs#metadata

ping @LiteSun


NTR for volumetric flow rate unit

Hi UO team!
I'was wondering if some additional terms could be added under volumetric flow rate unit?
Here is the ROBOT table with the requested fields if that is useful. Let me know if you don't think these terms should go here/anything doesn't make sense.

Preferred term label
Synonyms
Textual definition
Suggested parent term

cubic meter per second
m^3/s
A volumetric flow rate unit which is the measure of the volume of one cubic meter of matter crosses a given surface during the period of time equal to one second.
volumetric flow rate unit

cubic meter per minute
m^3/min
A volumetric flow rate unit which is the measure of the volume of one cubic meter of matter crosses a given surface during the period of time equal to one minute.
volumetric flow rate unit

cubic meter per hour
m^3/h
A volumetric flow rate unit which is the measure of the volume of one cubic meter of matter crosses a given surface during the period of time equal to one hour.
volumetric flow rate unit

liter per second
L/s
A volumetric flow rate unit which is the measure of the volume of one liter of matter crosses a given surface during the period of time equal to one second.
volumetric flow rate unit

liter per minute
L/min
A volumetric flow rate unit which is the measure of the volume of one liter of matter crosses a given surface during the period of time equal to one minute.
volumetric flow rate unit

liter per hour
L/h
A volumetric flow rate unit which is the measure of the volume of one liter of matter crosses a given surface during the period of time equal to one hour.
volumetric flow rate unit

liter per day
L/day
A volumetric flow rate unit which is the measure of the volume of one liter of matter crosses a given surface during the period of time equal to one day.
volumetric flow rate unit

million gallons per day
MGD
A volumetric flow rate unit which is the measure of the volume of one million gallons of matter crosses a given surface during the period of time equal to one day.
volumetric flow rate unit

Thanks so much!

Hi all, just wondering if these are appropriate for UO or if I should request elsewhere?


Incremental steps to netnative support

Changes necessary to make the very basic UWP app work in Release mode (after .NET Native mangles it).
Will still require a patch to Relinq (https://github.com/re-motion/Relinq/pull/6)
Makes significant progress on #623

How does this effect perf? Does it make the benchmarks we have significantly slower?

Also, have we considered cross-compiling so we only do this for UWP apps? Since perf is a priority it seems counter-productive to on the one hand be trying to improve perf, while with the other hand removing code that was specifically added to help with perf.

I suspect perf will be worse. I can actually test the numbers to see how much.
We are not currently set up to cross compile to UWP. @bricelam would know better how we could set that up.
Alternatively, we could catch the runtime exception thrown only on .NET Native and then invoke this slower path which preserves the original path for all other cases.

I think we should discuss after seeing how much it affects our current benchmarks.

To my surprise, this actually improves perf:
        [Benchmark(Iterations =10)]
        public void ConstructGetterSource(IMetricCollector collector)
        {
            var entityType = new EntityType(typeof(Poco), new Model());
            var prop = entityType.AddProperty("Id", typeof(int));
            for (var i = 0; i < 100000; i++)
            {
                var source = new ClrPropertyGetterSource();
                var setter = new ClrPropertySetterSource();
                collector.StartCollection();
                source.GetAccessor(prop);
                setter.GetAccessor(prop);
                collector.StopCollection();
            }
        }

Code
TimeElapsedAverage
TimeElapsed95

Original
2266
2383

With changes in this PR
1840
1889

@natemcmaster That looks good--what is the impact on our existing benchmarks?

@ajcvickers The changes to existing perf benchmarks was hardly significant. I had to run 100,000 iterations to get numbers I could believe were significantly different.

Just checking that you got those numbers on a release build and not a debug one (since that is the perf we care about)

Good point. Those were Debug. I'll re-run on release mode.

@natemcmaster I misunderstood the code when I looked at it last night. I see now that it doesn't change the cached delegate path, and hence I'm not surprised that the overall benchmark numbers are okay.
I can say :shipit: for those code changes. The "implies" stuff and how it is supposed to work is a mystery to me, so somebody who knows about that should look.

@ajcvickers Good to know.
Everyone else, there is gonna be a whole lot more awful "implies" stuff, so brace yourselves. This stuff exists only to trick ILC (the .NET Native compilation step) to keep metadata about generic methods and types we use at run time.

@natemcmaster :shipit:

Merged with https://github.com/aspnet/EntityFramework/commit/c35ce4d3632331d14ff8a3ab8ac59c54a660a535


Bullets appear in tasks lists

Describe the bug
When tasks lists are created, the checkboxes are preceded by bullets (see  screenshot in vanilla HTML+CSS attached using Safari WebKit)

Indeed, the code is

Expected Behavior
It would be nice to add a custom class for the <ul> or <li>elements so that the bullet can be removed.
Relevant log output
No response
Environment
I have written a RapidWeaver stack which basically gives ParsedownExtended the markdown code that has been input in the GUI. The PHP code is
<?php
	$Extra = new ParsedownExtended([
    "math" => true,
    "toc" => true,
    "typographer" => true,
    "sup" => true,
    "sub" => true

]);
	echo $Extra->text('%html%');
?>

where %html% is a macro that is replaced by the actual markdown code upon publishing the website.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I could update the script so you can add a class or a id to the list. By default ParsedownExtended doesn't add any styles


libcairo2 package request

Could you please add the libcairo2 package to Nanobox pkgsrc?
https://packages.ubuntu.com/search?keywords=libcairo2

I think the libraries in ubuntu's libcairo2 package are in the pkgsrc cairo package. Can you try using that?

Oh great, it looks like that will work. Thanks for the help!


Improve shard hash function to use 128 bit mutiply with xor

This is a new implementation of calc_shard that uses a state word in Domain plus an xor and a multiply to compute shards with a better distribution.
This prevents adding a dependency and produces quite good hashes compared to AHash and std's DefaultHasher:
I wrote a simulation program that calculates the quality of the spread for each algorithm based on real pointer values from the allocator. The full code is available here: https://github.com/TroyNeubauer/hash_test/blob/master/src/main.rs

 Here is an example run of the simulation:
Shard distributions from the last run
Pointer Hash
i=0:      129  XXXXXXXXXXXXXXXXXXXXXXXXX
i=1:      137  XXXXXXXXXXXXXXXXXXXXXXXXXXX
i=2:      186  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
i=3:      134  XXXXXXXXXXXXXXXXXXXXXXXXXX
i=4:      117  XXXXXXXXXXXXXXXXXXXXXXX
i=5:       80  XXXXXXXXXXXXXXXX
i=6:      110  XXXXXXXXXXXXXXXXXXXXXX
i=7:      107  XXXXXXXXXXXXXXXXXXXXX
Multiply Hash
i=0:      119  XXXXXXXXXXXXXXXXXXXXXXX
i=1:      145  XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
i=2:      117  XXXXXXXXXXXXXXXXXXXXXXX
i=3:      110  XXXXXXXXXXXXXXXXXXXXXX
i=4:      122  XXXXXXXXXXXXXXXXXXXXXXXX
i=5:      138  XXXXXXXXXXXXXXXXXXXXXXXXXXX
i=6:      135  XXXXXXXXXXXXXXXXXXXXXXXXXXX
i=7:      114  XXXXXXXXXXXXXXXXXXXXXX
Standard Hash
i=0:      125  XXXXXXXXXXXXXXXXXXXXXXXXX
i=1:      124  XXXXXXXXXXXXXXXXXXXXXXXX
i=2:      115  XXXXXXXXXXXXXXXXXXXXXXX
i=3:      135  XXXXXXXXXXXXXXXXXXXXXXXXXXX
i=4:      111  XXXXXXXXXXXXXXXXXXXXXX
i=5:      140  XXXXXXXXXXXXXXXXXXXXXXXXXXXX
i=6:      121  XXXXXXXXXXXXXXXXXXXXXXXX
i=7:      129  XXXXXXXXXXXXXXXXXXXXXXXXX
AHash
i=0:      131  XXXXXXXXXXXXXXXXXXXXXXXXXX
i=1:      109  XXXXXXXXXXXXXXXXXXXXX
i=2:      145  XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
i=3:      129  XXXXXXXXXXXXXXXXXXXXXXXXX
i=4:      127  XXXXXXXXXXXXXXXXXXXXXXXXX
i=5:      114  XXXXXXXXXXXXXXXXXXXXXX
i=6:      132  XXXXXXXXXXXXXXXXXXXXXXXXXX
i=7:      113  XXXXXXXXXXXXXXXXXXXXXX
Completed 10000 trials of 1000 inner runs
Average Standard Deviation by Algorithm:
Pointer Hash        : 2.4528438410815996
Multiply Hash       : 0.9047987100495352
Standard Hash       : 0.9037171038177603
AHash               : 0.904421036085782

This implementation is on par with hashing from the standard library and AHash for this use case. I couldn't find a _MOCK_SIZE_ or number of runs that lead to a > 10% standard deviation difference between Multiply Hash and the others.
Interestingly, the pointer hash works decently well for being so simple lol.The simulation also allocates unrelated objects to simulate a user allocating objects other than hazard pointers.
These results look promising but should be taken with a grain of salt for using pointer values from my machine and for general weirdness for using pointer values as entropy.
Also the efficiency is quite good. On x86 LLVM produces a single mul instruction (64 bit inputs, 128 bit outputs) and is just 5 instructions total: https://godbolt.org/z/o1n15dncd
Linking the point in stream where you discuss this for reference: https://youtu.be/tGn0mQF0804?t=11883

Thanks for digging so deep into this! Interestingly, I wonder whether this change is worth it in its current form because it doesn't improve the distribution that much (or rather, it's not that bad to begin with) and it introduces reads and writes to a single shared (and thus contended) memory location for all retires.
I wonder how well this would do if you used a thread local instead? I feel like that might give most of the benefit without the cost. What do you think?

I was so entrenched in looking at the distributions that I forgot factor in the cost of the state variable! I'll update this to have a feature for pointer hashing vs multiply hashing, and one for no_std. I think you mentioned doing benchmarks in the next stream, so maybe you could benchmark the performance differences in the next stream and then we reevaluate this PR at that point?

Would you mind separating the no_std change out into its own PR? Will make it a little easier to review each change individually, and I suspect that one will be much less contentious! Also keep in mind that we'll want a CI entry for that to make sure we're actually no_std. Something like https://github.com/jonhoo/flurry/blob/250ac876f79aa49190360bae4f7d3c5fc3ca33c5/azure-pipelines.yml#L32-L42 should do it!

I think it makes a lot of sense to subject the change in this PR to an eventual benchmark suite before merging — that's a great idea! Some of the tests in folly are benchmarks I believe, so we should be able to take advantage of those (maybe even run them through criterion).

Codecov Report

Merging #8 (b914550) into main (39264b4) will decrease coverage by 1.90%.
The diff coverage is 64.86%.

@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
- Coverage   82.85%   80.94%   -1.91%
==========================================
  Files           7        7
  Lines         414      425      +11
==========================================
+ Hits          343      344       +1
- Misses         71       81      +10

Impacted Files
Coverage Δ

src/deleter.rs
66.66% <0.00%> (ø)

src/object.rs
75.00% <ø> (ø)

src/domain.rs
76.38% <62.50%> (-2.68%)
:arrow_down:

src/holder.rs
74.19% <100.00%> (ø)

src/lib.rs
100.00% <100.00%> (ø)

src/record.rs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Closing for #12 #11


Typo in vioif error message

There is a typo in HermitCore at:
https://github.com/hermitcore/libhermit/blob/423cb0e80e4b81122fb088fdbc5bb385d9232933/drivers/net/vioif.c#L368

+1
I will fix it.

Fix it in branch devel


fix: Force roslyn generation for xamarin targets

This will improve memory consumption on CI, as there will not be an Uno.SourceGenerationTasks process running in the background,
Description of Change

Bugs Fixed

Fixes #

API Changes
None.

Behavioral Changes
None.

Required skia PR
None.

PR Checklist

[ ] Has tests (if omitted, state reason in description)
[ ] Rebased on top of main at time of PR
[ ] Merged related skia PRs
[ ] Changes adhere to coding standard
[ ] Updated documentation

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp

/azp run SkiaSharp


Update login.html

Analysis of the Code
This is an HTML file for a login page template using Bootstrap and Font Awesome, part of a "SB Admin 2" UI theme. The code is well-structured but has some potential areas for improvement. Here are the issues identified:
Issues Identified:
1.Accessibility Concerns:
The placeholder attributes in the email and password fields serve as labels but placeholders should not replace proper labels. This can affect screen readers and usability for users with disabilities.
2.Hardcoded Links:
The links for the login buttons (e.g., "Login with Google" and "Login with Facebook") are hardcoded to index.html. If this is meant to be a template, it’s better to replace these with meaningful URLs or ensure dynamic linking for functionality.
3.Potential Redundancy in CSS and JS Inclusions:
The JavaScript libraries like jquery-easing.min.js and bootstrap.bundle.min.js are included at the bottom of the file. While this is a good practice for performance, there might be redundant dependencies if they are included elsewhere in the project (for example, in the main layout template).
4.Security Issues:
The form does not include any basic security features like validation or preventing form submission to incorrect pages. There is also no mention of CSRF protection, which is a concern when working with forms.
5.Optimization of Resources:
The use of external libraries like Font Awesome and Google Fonts can lead to performance issues due to multiple HTTP requests. It’s often better to bundle critical assets locally or use asynchronous loading for better page performance.
6.Use of  tags for submit buttons:
The login and OAuth buttons are using  tags with href="index.html", which is not ideal for form submission. These should be replaced with proper  elements or should submit the form programmatically with JavaScript, rather than redirecting users via links.

您好，您的邮件我已经收到，我会尽快回复！  谢谢！

Hello,Thank you for your reply but i am little of confused because i have
made alot of pull request but none of them are been merge, if you can tell
me something it would be a very helpful.
Thank you!!
On Fri, Oct 4, 2024 at 7:14 PM CgwZzz @.***> wrote:

您好，您的邮件我已经收到，我会尽快回复！  谢谢！
—
Reply to this email directly, view it on GitHub
https://github.com/StartBootstrap/startbootstrap-sb-admin-2/pull/480#issuecomment-2393741486,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFABTY2A5SRUEWJKSCQCQ53ZZ2LSPAVCNFSM6AAAAABPL5NAFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTG42DCNBYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


An error is reported when running the demo, and other models also fail to load

When I run the demo command, my command is as follows: python3 scripts/example.py --ckpt=./2M.ckpt --device=cuda --partition=placement_generalization --task=visual_manipulation
Error after running: pybullet build time: May 20 2022 19:45:31
[INFO] 17 tasks loaded
Traceback (most recent call last):
File "/data/code/VIMA-code/scripts/example.py", line 506, in
main(arg)
File "/data/anaconda3/envs/VIMA/lib/python3.9/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/data/code/VIMA-code/scripts/example.py", line 84, in main
policy = create_policy_from_ckpt(cfg.ckpt, cfg.device)
File "/data/code/VIMA-code/vima/init.py", line 11, in create_policy_from_ckpt
policy_instance.load_state_dict(
File "/data/anaconda3/envs/VIMA/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1604, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for VIMAPolicy:
Unexpected key(s) in state_dict: "xattn_gpt.h.0.attn.bias"
I tried to replace other ckpt files, and the same error was reported, all of which failed to load the model.
I refer to other people's methods to solve it successfully: https://github.com/vimalabs/VIMA/issues/20#issue-1822380410

Feel free to refer to this clarification. Thanks for your interest.


Add Walkable Meta(Value) Pandoc instances

I implemented the following instances, allowing ToJSONFilter to work with Meta and MetaValue, as suggested in #95.

Walkable Meta Pandoc
Walkable MetaValue Pandoc

Notes:

The Walkable Meta Pandoc instance does not need to recurse because Meta is only used in Pandoc.  There is no [Meta] instance because there is only a single Meta value.
The Walkable MetaValue Pandoc instance makes use of new Walkable MetaValue Meta and Walkable MetaValue MetaValue instances.  These instance implementations map over containers directly; there is no [MetaValue] instance because MetaValue is also used as Meta and MetaMap map values.

Please let me know if there are any issues or formatting inconsistencies that you would like me to correct.  You are of course welcome to fix such things yourself if doing so requires less of your time.
Thank you!

Looks good, thanks!


Class 'CloudFlare\IpRewrite' not found

Plugins version: 3.0.6
Hosting: Heroku
The plugin works fine, but when I execute wp user list (wp-cli.org), I get the following error:

Hey,
Thanks for reporting this!  Does switching
require_once 'vendor/autoload.php';

to
require __DIR__ . '/vendor/autoload.php';

in cloudflare.loader.php fix your issue?
Thanks,
John

Yes, it does.

Awesome!  Thanks again for reporting this, we'll make sure it gets in the next release.


test: Fix to remove previous failing tests from Git Comment history

Description

This PR updates the ci-test.yml file to empty the failed_spec_ci folder which still holds the previoulsy (or attempt-1) failures & hence prints the attempt-1 failures also in the attempt-2 git comment in PRs.

Type of change

ci-test.yml file update

Checklist:
QA activity:

[X] Added Test Plan Approved label after reviewing all changes

/ci-merge-check


Synchronous semaphore-isolated command timeouts

After updating to the last hystrix version I found that synchronous semaphore-isolated commands are affected by the hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds property.
Is there a way to disable timeout for such commands if it's not a bug?

@vitalatron - This is indeed a new feature of Hystrix 1.4.x.
There's not a specific setting to disable the timeout, though of course you can set the timeout value as arbitrarily high as you'd like.
There are already settings per-command representing boolean enabled flags for other Hystrix features (request log, request cache, circuit-breaker, fallback), so I think it makes sense to add a flag for timeout as well.
I'll update the title of the issue to add this flag and then use it in command invocation.

Added in #742


Displaying findings twice in report

Currently in the sechub report if the filepath and the path from stack are equal the finding is displayed twice. Attached is the screenshot. Highlighted on the screenshot are the repeated findings.

Data sink and entry point are same in this situation.
The HTML report shows up a reduced form / variant were not full call stack is available (like in JSON report format) and shows up always first and last callstack entry ( so entry point and data sink).
So you would prefer to see only one entry in this case ?

Hello,
to improve the UX in such cases I thought it would be better if the entry would only be shown once, hence the issue :)

Gadzhi Abdurazakov<EMAIL_ADDRESS>Daimler TSS GmbH, imprint


Azure Pipeline Test Failures Not Detailed in Pipeline Test Tab

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: VSTest@2

Environment

Server - Azure Pipelines

Issue Description
Running Azure Pipeline to execute automation tests using VSTEST@2 task a test failure was encountered and the pipeline was marked with a warning. When looking at the details of the executed Test job, the failed test is captured and the failed count is shown in Total tests/Failed counts. However, in the pipeline 'Test' tab the 'Total' and 'Failed' test counts do not include the failed test. Please see screenshots attached.
So when we try to report on the test run using the TestManagementHttpClient to access the results, the failed test is not included.

did you solved this problem bro.If yes pls tell me how?


[Bug]: Home Assistant doesn't update device tracker as it should

What happened?
I have two cell phones on my WiFi network.  I can see that OpnSense sees them and they are marked in the DHCP leases as "active".  I can also disable cellular network access and use WiFi data only, so I know I am on the WiFi network.  However, the device tracker status on Home Assistant shows not_home.
If I manually reload the OpnSense HA integration, the status is updated correctly, but only temporarily.
hass-opnsense Version
0.3.6
OPNsense Firmware
OPNsense 24.7.6-amd64
Home Assistant Version
2024.10.3
Relevant logs
No response
Additional Details
No response

Fixed in 0.3.7


Update dependencies, Upgrade to Jest 25.x

Supports Jest 25.x as well as updates all other dependencies.

Fixes #11


Initial pass of loading config object

Okay I think I understand what you are doing now. :+1:

:+1:


Which permissions are required by --overwrite=false?

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
AzcopyVersion  10.26.0
Which platform are you using? (ex: Windows, Mac, Linux)
OS-Environment  windows
OS-Architecture  amd64
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy copy "<my file>" "<my sas>" --recursive=false --blob-tags=<redacted> --overwrite=false
Here are the relevant SAS fields:
se=2024-08-14T16%3A56%3A03Z
&sig=-REDACTED-
&ske=2024-08-14T16%3A56%3A03Z
&skoid=-REDACTED-
&sks=b
&skt=2024-08-08T10%3A50%3A03Z
&sktid=-REDACTED-
&skv=2024-05-04
&sp=wt
&sr=c
&st=2024-08-08T10%3A50%3A03Z
&sv=2024-05-04

This is using a user-delegated SAS.
What problem was encountered?
That exact command returns:
RESPONSE 403: 403 This request is not authorized to perform this operation using this permission.
ERROR CODE: AuthorizationPermissionMismatch

However, if I remove the --overwrite=false option, it works.
According to the docs^1, the default value for overwrite is true. This means there is some permission(s) which my SAS URL doesn't have, which are required by overwrite=false, and not required by overwrite=true.
I haven't been able to find any indication of what those missing permissions may be.

The behavior I'm trying to achieve with azcopy (and work with that same SAS) is a Blob PUT with the If-None-Match header set to * as described in the docs here: https://learn.microsoft.com/en-us/rest/api/storageservices/specifying-conditional-headers-for-blob-service-operations

When you use --overwrite=false, AzCopy checks whether the blob exists before writing. If the blob does not exist, the operation would require the c (Create) permission to create a new blob. Without the c permission, the operation cannot create a new blob, which can result in a 403 AuthorizationPermissionMismatch error.

With just Write (w) and Read (t) permissions, you cannot achieve the If-None-Match behavior because the creation of a new blob under the If-None-Match: * condition requires the Create (c) permission. Therefore, you would need to obtain a SAS token that also includes the Create (c) permission to use If-None-Match successfully in your azcopy operation.

Offline conversation -
[tevoinea]: after talking with my team I think we're going to stick with the API call instead of trying to move this functionality to azcopy