Fix Darwin passthru VM tests with remote builders

Is your feature request related to a problem? Please describe.
Since NixOS tests can run on Darwin since a few months, OfBorg is trying to run them, but these tests rely on native Linux builds, which should be performed by a remote (or local VM) builder.
Describe the solution you'd like
Ideally, all OfBorg nodes can delegate a few builds to each other node, but the remote build implementation does not currently support cyclic remote builder setups.
As an alternative, we could configure the OfBorg cluster in two layers, groups of machines, where the nodes in the top layer run the OfBorg evaluations, and the lower layer only performs builds.
The top layer would not receive remote build requests from other nodes in the top layer, and the lower layer only receives builds for the intended derivation system, making this setup acyclic.
If the top layer also performs builds for their native system, that also works, but is perhaps less effective at distributing work, as they can only be allowed to build locally evaluated derivations.
Describe alternatives you've considered
Make the passthru tests use cross compilation. I don't think this is desirable; see https://github.com/NixOS/nixpkgs/pull/317651#pullrequestreview-2102364647
Additional context
The docker-tools-cross VM test also has a multi-system derivation graph that requires remote builders to work. (Cross compile an image on one system, run on another)

This is @cole-h's territory I think.  (but I'm not sure this will get high enough relative priority)


fixfix in the scenario of recreating a table, the materialized view may assume that the data has not changed

snapshot of table,only compare tableName and version,when recerate table,and if the version remains unchanged 。
MV will assume that the data has not changed

run buildall

run cloud_p0


Using other MNI Spaces

Hello,
I am trying to use this software with fMRIPrep outputs in MNIPediatricAsym_cohort-1  space (T1w-aligned outputs are also available but not of interest). Here is how I run XCP_ABCD on HPC:
singularity run -e -B ${scratch}:/workdir -B ${bids_dir} $IMG ${fmriprep_dir} ${output_dir} participant --participant_label ${subject:4} -w /workdir -t Phon --lower-bpf 0.01 --upper-bpf 0.08 -p 36P -f 1 --smoothing 5
I get the following error after the pybids layout is made:
space not supported
Process Process-2:
Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/local/miniconda/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/miniconda/lib/python3.8/site-packages/xcp_abcd/cli/run.py", line 455, in build_workflow
    retval['workflow'] = init_xcpabcd_wf (
  File "/usr/local/miniconda/lib/python3.8/site-packages/xcp_abcd/workflow/base.py", line 147, in init_xcpabcd_wf
    single_bold_wf = init_single_bold_wf(
  File "/usr/local/miniconda/lib/python3.8/site-packages/xcp_abcd/workflow/base.py", line 380, in init_single_bold_wf
    bold_postproc_wf = init_boldpostprocess_wf(bold_file=bold_file,
  File "/usr/local/miniconda/lib/python3.8/site-packages/xcp_abcd/workflow/bold.py", line 243, in init_boldpostprocess_wf
    fcon_ts_wf = init_fcon_ts_wf(mem_gb=mem_gbx['timeseries'],mni_to_t1w=mni_to_t1w,
  File "/usr/local/miniconda/lib/python3.8/site-packages/xcp_abcd/workflow/connectivity.py", line 119, in init_fcon_ts_wf
    transformfile = get_transformfile(bold_file=bold_file, mni_to_t1w=mni_to_t1w,
  File "/usr/local/miniconda/lib/python3.8/site-packages/xcp_abcd/utils/utils.py", line 110, in get_transformfile
    return transformfile
UnboundLocalError: local variable 'transformfile' referenced before assignment

Do you have any guidance for how to proceed?
Thanks,
Steven

Hi @smeisler ,
we have not  release post-processing with MNIPediatricAsym_cohort-1 and MNIinfant  spaces that is why. We will release it soon


Update Start.ps1

Motivation and Context

Fixes this issue: https://github.com/microsoft/chat-copilot/issues/378
Description

Removed invalid "-command" argument.
Added "-noexit" argument to prevent the new pwsh window from closing if there is an error. This helps with debugging if there is an issue.
Added escaped double-quotes around the backend script path so that it does not fail when there is a space in the path to the script.

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

hi @samleegithub, thanks for this contribution!
there are currently 2 other PRs out with fixes to the Start.ps1 script (#383 & #385), both of which also address the usage of the pwsh command, which doesn't work on all machines. I will close your PR in favor of getting one of these merged, since I think it is a good time to fix the command as well.


Updated Lutris installation instructions to work with the EA App

Unfortunately only after already making my own fork and commit, I noticed there was already a pull request suggesting changes to the Lutrix/Origin section of the Wiki. Here's my take on the way the changes should be then.

No power currently and don't have Titanfall installed on my laptop to test this myself, maybe @CooldudePUGS could test these instructions and make sure they work?
LGTM otherwise though

maybe @CooldudePUGS could test these instructions and make sure they work?

doesn't this require owning the game through ea? also, my linux drive is still dying rn. quite horribly

No mention of wsocks override.

Yeah, I was under the impression these were the instructions for Origin/EA using Lutris. I guess someone could install the Steam version of Titanfall through Lutris instead of just Steam. Wouldn't the Steam instructions above work at that point? Just add the -northstar launch flag.

L

Launching NorthstarLauncher.exe doesn't make any sense.

Do you care to explain why? Either option of launching Northstar with Titanfall2.exe and a wsock32 launch arg redirect or just launching NorthstarLauncher.exe works just fine.

Because why change the executable when you can just use DLL override+launch option or run_northstar.txt 1.
Launching with NorthstarLauncher.exe also doesn't count the time played.
And anyway, this PR is a duplicate.

What's the state of this?

From what I understand, no one wants to make the change to the EA App because other people still want to use Origin. EA themselves doesn't support Origin anymore, and you need to do extra steps and work-arounds to get Origin to work. In my opinion, if the wiki isn't going to include those instructions on how to get Origin to work, then the instructions should be updated to the EA App version. Finally. I'm not sure if @stygia-dev was able to test out the instructions and verify they work on machines other than mine.
So, someone else should verify that the instructions are understandable and they work on your Linux machine. They work on my desktop and my Steam Deck.

I'm wondering if many months later if this is finally ready to be used.
The simplified instructions are instead the EA app on Lutris, duplicate its entry and use that to point to the  Northstar launcher. Add both of those as steam shortcuts if you need to launch them from gaming mode on the steam deck and then launch northstar after the EA app. Tada.

I'll poke some Linux people on the Northstar Discord on their opinions on this ^^

@ddotthomas we integrated the wiki into the NorthstarDocs and as such are in the process of deprecating this repo here. Feel free to re-open the PR against the new repo instead.
Otherwise, we'll probably close the remaining PRs against the wiki here in the coming days and then fully archive the repo.


Certificate revocation

ready currently reports a pass if a certificate is trusted. It could benefit from giving revocation information as well by reporting on:

OCSP stapling/must-staple, or a short certificate lifetime (Firefox ignores OCSP if the certificate lifetime is under 10 days).
CRLsets/CRLite/Let's Revoke information (similar to what testssl.sh supports).

In-depth TLS analysis may be out of scope and better suited for a tool like testssl.sh or Internet.nl, but a simple revocation check could work. At the very least: it could warn if OCSP stapling isn't set up for certificates with normal lifetimes (>10 days), and perhaps encourage them to use must-staple.

A check for OCSP stapling makes total sense to me.
A couple of notes from my quick investigation this morning.
getpeercert() doesn't return whether must-staple is enabled by the looks of things. It does return an OCSP value but that appears to be from the information access section.
Running the der file (from: getperrcert(binary_form=True)) through openssl (openssl x509 -in cert.der -inform der -text) does output the "<IP_ADDRESS>.4.1.11<IP_ADDRESS>" block.

Here's a cpython issue about adding support for extensions to the getpeercert function:
https://github.com/python/cpython/issues/64668
The suggestion there is to use pyasn1 or similar.

Okay, so the pyasn1 rabbit whole has ended up with a couple of other interesting libraries that we could use here.
asn1crypto lets you load DER files with the extensions. Then certvalidator wraps that with a bunch of (very appropriate) validation rules:
https://github.com/wbond/certvalidator/
If I implement something beyond simply checking for the "OCSP" value in the certificate than I expect that it would end up using this library.

Sounds good. How do you feel about checking for "must-staple"? Without OCSP Must-Staple, I don't think stapling is anything more than a privacy measure to reduce traffic leakage to CAs because failures are silently ignored.


Java 16.4 : Main thread

Description
Add audio, documentation, and video regarding the Main thread
Location of File to be added The files should be added inside the Main thread which will be inside Multithreaded Programming folder which will be inside of Java folder. If the folder is not present, create the folder with this exact name.

The documentation file can be in the .md/.py/.ipynb format.
Audio should be in .mp3 format and to be submitted through a Google drive link.
Video can be in any format and should be submitted through a Google Drive link.

Note:
You are required to comment with \assign CONTENT_TYPE, so that other content types can be created at the same time. Failing to comment in the above manner will lead to the removal of assignment from the issue even if the bot assigns. You are required to do a PR within 7 days otherwise you will be unassigned and others will be assigned. Issues will be assigned on a first come first serve basis.
Domain
Java_Domain
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[x]    I follow Contributing Guidelines & Code of conduct of this project.

\assign documentation

assign me @nandini7637

/assign documentation

/assign

/assign documentation

Thank you for assigning me

/assign audio

Assign audio please


cleanup warnings for ios starter app

Environment details:

XCode 7.3

Steps to reproduce the issue:

Run wsk sdk install iOS
Unzip Starter App
Use Cocoapods or Carthage to add OpenWhisk framework
Build Starter App

Provide the expected results and outputs:
Expect to have a clean install with no Warnings
Provide the actual results and outputs:
Build prints 2 warnings

FilterForecast.swift

OpenWhiskStarterApp/FilterForecast.swift:39:50: warning: conditional cast from '[String : AnyObject]' to '[String : AnyObject]' always succeeds
                if let forecast = forecasts[day] as? [String:AnyObject] {
                                                 ^

Utils.swift

OpenWhiskStarterApp/Utils.swift:46:46: warning: conditional cast from '[String : Any]' to '[String : Any]' always succeeds
            if let forecast = forecasts[day] as? [String:Any] {
                                             ^

FYI: @paulcastro @bjustin-ibm

@paulcastro is this still valid?
also can we move the starer app to its own repo to permit developers to just check that out without the extra baggage? this might require some dependence management for the cli since it installs the bundle via one of its install commands.

No, this isn't valid anymore.  I'll close.
We can migrate the starter app - yes, the location of the stater app zipfile may be affected by this.


[ios] Prevent redundant binary upload

We should implement some mechanisms to try and prevent redundant binary uploads:
https://github.com/expo/eas-cli/issues/115#issuecomment-738996478

we could try to query the app store apis before submitting to see if we've already submitted a build for that version/build number/version code.
as a last resort, we can handle the error message from fastlane and make it more well-formatted and easier to read

Related: https://github.com/expo/eas-cli/issues/892

This is super annoying.

@izakfilmalter FWIW you can use app version management - https://docs.expo.dev/build-reference/app-versions/

Ahh sweet! Will try it out @dsokal.

I'm closing the issue as the new "App version management" feature mostly fixes the issue.


feat(sizing): add viewport units and 1/3 and 2/3 width/height

fixes https://github.com/patternfly/patternfly-next/issues/1400

Deploy preview for pf-next ready!
Built with commit 40ce8b3f6a9e4c2aa43f0025a9ca6bb4b6430518
https://deploy-preview-1402--pf-next.netlify.com

@matthewcarleton I just added them, was curious what you thought :) "thirds" seem pretty common. Do you think they're common enough to add to the utility or is this getting towards creating a utility for too many widths?

@mcoker ya I think it's ok. I don't think it's bad to offer more. I guess we'll see if they are useful :)


Brightlayer UI Migration

Fixes PXBLUE-2496.

Changes proposed in this Pull Request:

Get demos as up to date as possible
Prepare to publish official @brightlayer-ui/chartjs v1.0.0

This is great!


cpp master example: minor improvements to usage text displayed (add missing commands and small typo fix)

There is also a typo in "unsolicited" too, and I think the sentence should be "performs an ad-hoc range scan". Sorry if I'm a bit late 😢

Thanks for the comment, didn't notice that ones before :) did a small pr more: #243


What day is it??

The date displayed by our DateStr component is a day behind our DateInput component.
I assume the issue is realted to UTC vs local time, and the fact that the DateInput does not have a time portion of the date-time, which is interpreted at midnight (UTC?).
All displayed/inputed dates and times should be local time.

Issue is due to UTC Vs local time. I have tried splitting the date and use  "new Date(yyyy, mm, dd)". It fixed the issue.


Enhance authz with URL targets and create new metadata authorization

Summary

Create a new metadata-specific authorization to allow a granter to restrict the authorization to a specific scope, session, or record and only for certain roles.
Enhance x/authz in our fork to allow MsgTypeURLs to have targets (i.e. <msg type url>#<target>).

Problem Definition
Currently, authorizations are too broad. They allow a granter to sign for the grantee for any update (of a message type), even if that grantee shouldn't be involved in the thing they're updating. They also allow the grantee to sign as any role that the granter fulfills.
We need a way to allow a granter to limit an authorization to a specific entity. Furthermore, we need a way to limit the authorization to specific roles.
It want to be able to say something like this, “I grant  permission to sign for me as a  on the session with id ”
Proposal
There are three parts to this:

A new authorizaiton
An update to the x/authz module in our SDK fork
An update to the metadata module's authz checking to identify and apply these restrictions.

New authorization
Create a new authorization that has a metadata address, list of roles, and optional number of uses.
An empty roles list is the same as having all roles in the list.
The MsgTypeURL() function on this authorization will return a value based on its metadata address. E.g., if it’s a record address, /provenance.metadata.v1.MsgWriteRecordRequest#<record address> would be returned.
The Accept function will only check the number of uses and decrement it if applicable. It doesn’t have enough info to do anything with the roles. And since it can’t be called via Exec, there isn’t any msg validation that can be done that isn’t already being done in the metadata module.
x/authz update
In the x/authz module, when using the MsgTypeURL for routing purposes, strip off any # and everything after it.
Authorizations are unique for a granter + grantee + MsgTypeURL. That MsgTypeURL must also be routable.
Effectively, this would allow authorizations to be granted differently for different specific scopes, sessions, etc.
Authorizations with a fragment would not be usable through the Exec endpoint though, since it wouldn’t know how to add the the fragment. However, due to the 1 signer and 1 grantee restriction of Exec, it’s already effectively unusable for the metadata module.
Updated metadata authz handling
Update our GetMessageTypeURLs function to take in a metadata address and also return values containing that address as a fragment. It doesn't need to be added to all existing return values, only on the ones that might be generated by a new authorization's MsgTypeURL().
For example, if the url /provenance.metadata.v1.MsgWriteRecordRequest is provided to the function, the following should be returned:

"/provenance.metadata.v1.MsgWriteRecordRequest"
"/provenance.metadata.v1.MsgWriteSessionRequest"
"/provenance.metadata.v1.MsgWriteRecordRequest#<address>"

Basically, any Write... urls it's returning, should also have the same entry with the fragment, regardless of the reason it's in the list.
When looking for authorizations to fill signatures, if an authorization is found that passes Accept:

If it's not one of these new ones, or it's a new one with an empty roles list, apply the appropriate signatures and save/delete it appropriately.
If it is one of these new ones, get the list of roles from it. The authorization is applicable if there is one or more party with the granter and one or more of the roles in the authorization. If it's applicable, apply the appropriate signatures and save/delete it appropriately. If it's not applicable, do not save/delete it, and keep looking for other authorizations.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Instead of this authorization have a count field, #1483 should be done so that this new authorization can be placed in one of those if a count is desired.


Patch 1 - Get-AzureADGroup vs Get-AzureADMSGroup

Updated doco for Get-AzureADGroup vs Get-AzureADMSGroup with regards to using AzureAD Graph vs MSGraph. This took me a little time to figure out until I see the comments on https://techcommunity.microsoft.com/t5/azure-active-directory-identity/new-enhancements-to-the-azuread-powershell-2-0-preview-manage/ba-p/245153 and realised I wasn't the first person to get confused.
1st Comment
2nd Comment
This may need to be done to all AD vs ADMS pages but at least this is start.
PS: Also, not sure why there are two merged PR's in Patch-1 which is what I folked when I pressed 'Edit' from docs.microsoft.com. I'm guessing there is a patch-1 branch on the actual repo that may need to be deleted.

Docs Build status updates of commit c273b86:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azureadps-2.0/toc.yml
:warning:Warning
View (azureadps-2.0)
Details

azureadps-1.0/toc.yml
:warning:Warning
View (azureadps-1.0)
Details

azureadps-2.0-preview/toc.yml
:warning:Warning
View (azureadps-2.0-preview)
Details

azureadps-2.0/AzureAD/Get-AzureADGroup.md
:white_check_mark:Succeeded
View (azureadps-2.0)

azureadps-2.0/AzureAD/Get-AzureADMSGroup.md
:white_check_mark:Succeeded
View (azureadps-2.0)

azureadps-2.0/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#administrative-units' in 'azureadps-2.0/AzureAD/index.yml'.
Line 26, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application-proxy-application-management' in 'azureadps-2.0/AzureAD/index.yml'.
Line 45, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application-proxy-connector-management' in 'azureadps-2.0/AzureAD/index.yml'.
Line 66, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#applications' in 'azureadps-2.0/AzureAD/index.yml'.
Line 109, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#azuread' in 'azureadps-2.0/AzureAD/index.yml'.
Line 210, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#certificate-authorities' in 'azureadps-2.0/AzureAD/index.yml'.
Line 221, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#connect-to-your-directory' in 'azureadps-2.0/AzureAD/index.yml'.
Line 228, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#contacts' in 'azureadps-2.0/AzureAD/index.yml', did you mean '#options'?
Line 247, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#contracts' in 'azureadps-2.0/AzureAD/index.yml'.
Line 252, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#deleted-objects' in 'azureadps-2.0/AzureAD/index.yml'.
Line 257, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devices' in 'azureadps-2.0/AzureAD/index.yml', did you mean '#options'?
Line 282, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory' in 'azureadps-2.0/AzureAD/index.yml'.
Line 291, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory-objects' in 'azureadps-2.0/AzureAD/index.yml'.
Line 296, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory-roles' in 'azureadps-2.0/AzureAD/index.yml'.
Line 325, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#domains' in 'azureadps-2.0/AzureAD/index.yml', did you mean '#options'?
Line 344, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#extension-properties' in 'azureadps-2.0/AzureAD/index.yml'.
Line 349, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#groups' in 'azureadps-2.0/AzureAD/index.yml'.
Line 404, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#oauth2' in 'azureadps-2.0/AzureAD/index.yml'.
Line 411, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policies' in 'azureadps-2.0/AzureAD/index.yml'.
Line 418, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#service-principals' in 'azureadps-2.0/AzureAD/index.yml'.
Line 465, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#users' in 'azureadps-2.0/AzureAD/index.yml'.

azureadps-1.0/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#msonline' in 'azureadps-1.0/MSOnline/index.yml'.

azureadps-2.0-preview/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#administrative-units' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 50, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 83, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application-proxy-application-management' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 102, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application-proxy-connector-management' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 123, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#applications' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 174, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#azureadpreview' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 251, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#certificate-authorities' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 262, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#connect-to-your-directory' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 271, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#contacts' in 'azureadps-2.0-preview/AzureAD/index.yml', did you mean '#options'?
Line 290, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#contracts' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 295, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#custom-security-attributes' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 316, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#deleted-objects' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 329, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devices' in 'azureadps-2.0-preview/AzureAD/index.yml', did you mean '#options'?
Line 354, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 363, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory-auditing' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 370, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory-objects' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 375, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory-roles' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 390, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#directory-settings' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 403, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#domains' in 'azureadps-2.0-preview/AzureAD/index.yml', did you mean '#options'?
Line 422, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#extension-properties' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 427, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#groups' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 482, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#identity-provider-management' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 493, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#oauth2' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 500, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#object-settings' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 511, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policies' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 528, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#privileged-role-management' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 551, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#role-management' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 568, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#service-principals' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 623, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#staged-rollout' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 638, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#trust-framework-policy-management' in 'azureadps-2.0-preview/AzureAD/index.yml'.
Line 649, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#users' in 'azureadps-2.0-preview/AzureAD/index.yml'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

While i'm not sure, I think those warnings are specifc to the merges that are on the public patch-1 branch. Hopefully this doesn't stop these changes being made.

Thanks @tlourey for your contribution.
@CelesteDG, this is good to go.

@CelesteDG is there any reason the common paramaters are not showing up on the live site or is it just a caching thing?
Get-AzureADMSGroup

Thanks @tlourey for your query. I notice this behavior across all cmdlets. Allow me to find out why it is that way.


arcanist: bring back php with curl and json

arcanist needs this these two extensions to work.
Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Apparently, php should already be a php containing the default packages, but patchShebangs picks the wrong php for some reason.

I added a comment in https://github.com/NixOS/nixpkgs/pull/83896/files#r405156130.


Add Arthera Mainnet for versions 1.3.0 and 1.4.1

From GitHub Pull Requests for Safe Deployments done on Arthera Mainnet at :
https://github.com/safe-global/safe-deployments/pull/395
https://github.com/safe-global/safe-deployments/pull/394
Even after updating our BlockScout to latest version you can only confirm the blocks by looking at https://explorer.arthera.net/address/0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7
I need this package update to deploy Safe-infrastructure Docker containers on Arthera Mainnet as I've done for Arthera Testnet.

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1206619560645738

Hello @mmv08 could you help to review this PR as you have reviewed the deployments PR ? I wait for the merge of this PR to decentralize the management of our system contracts with a Safe multi-signatures.

Sorry, I do not have GitHub permission to review PRs in this repository, as I only work on Contracts + TS/JS stuff

Hello, this small review is stuck for 2 weeks already, @Uxio0 could you help with that ?


#28 update documentation format to numpy doc format

Fixes #28

Codecov Report

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

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


Add wfc compat for 2 3 x

Overview
Add"IssuerSerialQuoteFormat" a variant of ""IssuerSerial" option to output a issuer name in a format that is compatiable with both Microsoft's WCF stack and Java.
This is achieved by using quotes to delimit unicode characters as opposed to a backslash.
This solves the :
The EncryptedKey clause was not wrapped with the required encryption token 'System.IdentityModel.Tokens.X509SecurityToken'
error seen in IIS and which dates back to at least 2007.
Example, minimal diff:
		ISSUER_SERIAL               OU=Sales,CN=J. Smith
		ISSUER_SERIAL_QUOTE_FORMAT  OU=Sales, CN=J. Smith

Example which prompted this change:
ISSUER_SERIAL:                 CN=Entrust Certification Authority - L1K,OU=(c) 2012 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US

ISSUER_SERIAL_QUOTE_FORMAT:    CN=Entrust Certification Authority - L1K, OU="(c) 2012 Entrust, Inc. - for authorized use only", OU=See www.entrust.net/legal-terms, O="Entrust, Inc.", C=US

Details
RFC 2253 seems to provide two approaches for escaping characters.
WCF seems to only support the use of using "".
Java seems to support both approaches using \ or using "".
This claim is supported by Unit tests by testing against all CA in Java's keystore used to test wss4j and also a fixed set of CA.
Misc
This PR also consolidates the two different SoapUtils into a single test class.
Testing
This  has mainly been tested under Java 8,and against both a test and production WCF system.

@coheigea  Sorry about noise, rebased change has been tested against two systems , (spring-ws) didn't require and update afterall since string was passed (Flexiable interface design!).

It Looks like the comment about handling exception was removed, or at least I don't see it now ?
The execute() method throws the same exception as the X509Principal.getName() so from an Exception prespective that has not changed. If you want to to still make a change or ad a test for this let me know.
All other comments have been addressed.

Also I just created a PR against spring-ws and was impressed that they have a webhook to check a CLA status and automates the process of signing it. Full process only took 1 minutes. Though I had filled one out for Apache 20 years ago when I was a committer, I downloaded a new one and the PDF is cubmersome.... I looked around to see if I could find the Pivotal CLA webhook code but was unsuccessfull.


New media_player platform for Russound devices using the RIO protocol

media_player platform for Russound devices using the RIO protocol
Auto discovers zones and sources
Handles media metadata from sources that support it
asyncio implementation
Push updates for any zone or source changes so no polling required.
Example entry for configuration.yaml (if applicable):
media_player:
  platform: russound_rio
  host: <IP_ADDRESS>
  name: Russound

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

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

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

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Hello @wickerwaka,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

9d6913dbbbb1741cc7ecc691e4f10b07af02bf9d - This commit has something that looks like an email address (mdonlon@riotgames.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hello @wickerwaka,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

7b3997437bd72185d3975f54c1330b9eaf17126a - This commit has something that looks like an email address (mdonlon@riotgames.com). Maybe try linking that to GitHub?.
9d6913dbbbb1741cc7ecc691e4f10b07af02bf9d - This commit has something that looks like an email address (mdonlon@riotgames.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Documentatio at https://github.com/home-assistant/home-assistant.github.io/pull/2969

I resolved the CLA issue with this PR, but it doesn't look like the bot removed the label.

Oh, this is good news.  Can't wait to try this out!


Maps are not iterable

sdk.core.map:13 states:

/// Maps, and their keys and values, can be iterated.

But Map doesn't implement any kind of iterable interface, and therefore cannot actually be iterated. Is this line in the dart file incorrect, or is it just phrased ambiguously?
It'd be nice if for(final entry in myMap){} was a valid construct in Dart without having to go through the .entries() method.
Dartpad for reference:
https://dartpad.dev/?id=53c3d8da81dde145b4986f05b3cfc028

Should perhaps be rewritten so say that Map entries, keys and values can be iterated.
The way to iterate entries is for (var entry in myMap.entries) {}.


failed to create container

I first started a Docker container with Core0:
docker run --privileged -d --name core -p 6379:6379 g8os/g8os-dev:1.0

then using js:
cl = j.clients.g8core.get("<IP_ADDRESS>")

flist = "https://hub.gig.tech/maxux/ubuntu1604.flist"
container_id = cl.container.create(flist, storage='ardb://hub.gig.tech:16379', host_network=True)

=> RuntimeError:
failed to create container "mount-root-plist(upnormal exit of filesystem mount at '/mnt/container-8')"

Yeah, the docker image is not uptodate. I strongly suggest that u use the initramfs image from https://github.com/g8os/initramfs

How come it's not up to date? That's 1.0,  it should work for that release. Please make sure the docker image is usable


Reuse Functional.cs for Transform

Hi,
Currently, TorchSharp.torchvision.transforms.functional has all the implementations of transforms from Pytorch. I find some transforms, e.g., Normalize, that have their own implementations in their respective files as well as in Functional.cs file.
Should I remove the implementations of such transforms from their respective files and call the implementations from Functional.cs instead?

Closed via #391


spectest: ensure compiled functions can outlive module

Tentative fix for #2039 for the compiler, not wazevo.
In linking.wast we have:

a module A that exports its memory and table
a module B that imports both

it initializes the (shared) memory, and
it initializes the (shared) table, setting entry zero to one of its functions
then it fails while running main

The test then verifies that initializing the memory and the table both succeeded before main failed. It does so by reading from the memory, and indirect calling the function in the table.
Both the memory and table are owned by A, so still exist. But the function, or rather the compiled code (and mmaped memory) for the function is/was owned by B and can be GCed, because we SetFinalizer on an object owned by B.
This change makes it so that the finalizer is set on the compiledCode rather than on the compiledModule. Since the resolved function import is a function, and that owns a compiledFunction, which owns the compiledCode, this should fix the issue.

The change looks good, do you want to merge this in independently of #2102 ?

I'd reviewed a previous version of that, and (I guess because the title was not updated) totally missed the progress.
Then went on and duplicate all the work. 🤦
Happy to shelve this. I guess there's only the test that I fixed, but @evacchi can easily fix it.

Everything is already in #2102.


Interfaces: dhcp6-creation-breakout-step2

Additions to Franco's changes. Moved script creation to interface_dhcpv6_prepare().
Removed call to interface_dhcpv6_prepare() from interface_dhcpv6_configure(), the conf and script creation needs to be called before we get there. Checkout L2644 onwards.

looking good... almost there :)

the part about the "deconfigure" should be done in interfaces.php, we cannot catch all corner cases in the backend
your first commit seemed better with only affecting dhcpv6 and track6, what made you change it? in dhcpv6 case we need to configure the same interface, in the track6 case we look up the tracked interface.

We need to be aware that if the user changes away from track6 on the LAN to ANY other setting then the dhcp6c*.conf is not changed unless we call a dhcp6 config change, I found that bit out whilst testing yesterday. The next stage of this is to use the modified dhcp6c which can use sigup to re-read the config.

yes, the "deconfigure" (it's a prepare() on the tracked if setting to be deleted) should be executed in interfaces.php, we can't always rewrite configs especially on unrelated actions later.

But unless you re-write the config and re-trigger dhcp6c, it will continue to put the tracked interface IP's on the LAN until you restart the WAN, at least that's what happened when I was testing.

@fichtner  - Your thoughts on my last comment?
I have some hours free this week ( at the moment ) so I can move on with this once this bit is sorted.

I want to pull in the other refactor right away, but discuss the other thing further... it seems the "track6" modelling seems a bit wrong as it cannot be cleaned up properly. Ideally the tracking should be set would be from the parent interface, which makes the config generation and cleanup easier... but with that being said we shouldn't worry too much about configuring after a cleanup and rather focus on the true use cases for setting track6 and reconfiguring it. all other code is bound to severe bitrot and ends up hogging cycles for unknown benefits.

So for now we can ignore the possibility of a problem if the conf file is not re-written during a LAN config change, and just issue a warning that WAN should be re-saved and applied?

Yes, one step at a time. I'm committing a modified commit that tries to retain what we have now.. there was a small mistake in it for rc.newwanip

OK, next step?

See 2f12b3d, we detach interface_dhcpv6_prepare() but need to prefix both calls of interface_dhcpv6_configure() now to retain the same behaviour.
With this base change it becomes easier to get the hardest step done to reload the respective tracking configuration with it.


Update teams-powershell-release-notes.md

Updated release notes to add the new features for 2.0.0 version

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


⚠ Bofrost.si has degraded performance

In 0001e5d, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 2577 ms

Resolved: Bofrost.si performance has improved in e4fc624.


Referencing request from response

The best situation is to provide fixed values but sometimes you need to reference a request in your response. In order to do this you can profit from the fromRequest() method that allows you to reference a bunch of elements from the HTTP request. You can use the following options:

fromRequest().url() - return the request URL
fromRequest().query(String key) - return the first query parameter with a given name
fromRequest().query(String key, int index) - return the nth query parameter with a given name
fromRequest().header(String key) - return the first header with a given name
fromRequest().header(String key, int index) - return the nth header with a given name
fromRequest().body() - return the full request body
fromRequest().body(String jsonPath) - return the element from the request that matches the JSON Path

Let’s take a look at the following contract
Contract contractDsl = Contract.make {
	request {
		method 'GET'
		url('/api/v1/xxxx') {
			queryParameters {
				parameter("foo", "bar")
				parameter("foo", "bar2")
			}
		}
		headers {
			header(authorization(), "secret")
			header(authorization(), "secret2")
		}
		body(foo: "bar", baz: 5)
	}
	response {
		status 200
		headers {
			header(authorization(), "foo ${fromRequest().header(authorization())} bar")
		}
		body(
				url: fromRequest().url(),
				param: fromRequest().query("foo"),
				paramIndex: fromRequest().query("foo", 1),
				authorization: fromRequest().header("Authorization"),
				authorization2: fromRequest().header("Authorization", 1),
				fullBody: fromRequest().body(),
				responseFoo: fromRequest().body('$.foo'),
				responseBaz: fromRequest().body('$.baz'),
				responseBaz2: "Bla bla ${fromRequest().body('$.foo')} bla bla"
		)
	}
}

Running a JUnit test generation will lead in creation of a test looking more or less like this
// given:
 MockMvcRequestSpecification request = given()
   .header("Authorization", "secret")
   .header("Authorization", "secret2")
   .body("{\"foo\":\"bar\",\"baz\":5}");

// when:
 ResponseOptions response = given().spec(request)
   .queryParam("foo","bar")
   .queryParam("foo","bar2")
   .get("/api/v1/xxxx");

// then:
 assertThat(response.statusCode()).isEqualTo(200);
 assertThat(response.header("Authorization")).isEqualTo("foo secret bar");
// and:
 DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
 assertThatJson(parsedJson).field("url").isEqualTo("/api/v1/xxxx");
 assertThatJson(parsedJson).field("fullBody").isEqualTo("{\"foo\":\"bar\",\"baz\":5}");
 assertThatJson(parsedJson).field("paramIndex").isEqualTo("bar2");
 assertThatJson(parsedJson).field("responseFoo").isEqualTo("bar");
 assertThatJson(parsedJson).field("authorization2").isEqualTo("secret2");
 assertThatJson(parsedJson).field("responseBaz").isEqualTo(5);
 assertThatJson(parsedJson).field("responseBaz2").isEqualTo("Bla bla bar bla bla");
 assertThatJson(parsedJson).field("param").isEqualTo("bar");
 assertThatJson(parsedJson).field("authorization").isEqualTo("secret");

As you can see elements from the request have been properly referenced in the response.
The generated WireMock stub will look more or less like this:
{
  "request" : {
    "urlPath" : "/api/v1/xxxx",
    "method" : "POST",
    "headers" : {
      "Authorization" : {
        "equalTo" : "secret2"
      }
    },
    "queryParameters" : {
      "foo" : {
        "equalTo" : "bar2"
      }
    },
    "bodyPatterns" : [ {
      "matchesJsonPath"<EMAIL_ADDRESS>== 5)]"
    }, {
      "matchesJsonPath"<EMAIL_ADDRESS>== 'bar')]"
    } ]
  },
  "response" : {
    "status" : 200,
    "body" : "{\"url\":\"{{{request.url}}}\",\"param\":\"{{{request.query.foo.[0]}}}\",\"paramIndex\":\"{{{request.query.foo.[1]}}}\",\"authorization\":\"{{{request.headers.Authorization.[0]}}}\",\"authorization2\":\"{{{request.headers.Authorization.[1]}}}\",\"fullBody\":\"{{{escapejsonbody}}}\",\"responseFoo\":\"{{{jsonpath this '$.foo'}}}\",\"responseBaz\":{{{jsonpath this '$.baz'}}} ,\"responseBaz2\":\"Bla bla {{{jsonpath this '$.foo'}}} bla bla\"}",
    "headers" : {
      "Authorization" : "{{{request.headers.Authorization.[0]}}}"
    },
    "transformers" : [ "response-template" ]
  }
}

So sending a request as the one presented in the request part of the contract will lead in sending the following response body
{
  "url" : "/api/v1/xxxx?foo=bar&foo=bar2",
  "param" : "bar",
  "paramIndex" : "bar2",
  "authorization" : "secret",
  "authorization2" : "secret2",
  "fullBody" : "{\"foo\":\"bar\",\"baz\":5}",
  "responseFoo" : "bar",
  "responseBaz" : 5,
  "responseBaz2" : "Bla bla bar bla bla"
}

IMPORTANT:
This feature will work only with WireMock having version greater or equal to 2.5.1. We’re using WireMock’s response-template response transformer. It’s using Handlebars to convert the Mustache {{{ }}} templates into proper values. Additionally we’re registering 2 helper functions. escapejsonbody - that escapes the request body in a format that can be embedded in a JSON. Another is jsonpath that for a given parameter knows how to find an object in the request body.
fixes #237

Looks good to me.
The only thing i can think of is that it would be nice if the response body had nicer formatting in the Wiremock stub, but that would probably be more realistic if it wasn't an escaped string.
  "body" : "{\"url\":\"{{{request.url}}}\",\"param\":\"{{{request.query.foo.[0]}}}\",\"paramIndex\":\"{{{request.query.foo.[1]}}}\",\"authorization\":\"{{{request.headers.Authorization.[0]}}}\",\"authorization2\":\"{{{request.headers.Authorization.[1]}}}\",\"fullBody\":\"{{{escapejsonbody}}}\",\"responseFoo\":\"{{{jsonpath this '$.foo'}}}\",\"responseBaz\":{{{jsonpath this '$.baz'}}} ,\"responseBaz2\":\"Bla bla {{{jsonpath this '$.foo'}}} bla bla\"}",

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7340f28). Click here to learn what that means.
The diff coverage is 68.23%.

@@            Coverage Diff            @@
##             master     #238   +/-   ##
=========================================
  Coverage          ?   58.73%
  Complexity        ?     1506
=========================================
  Files             ?      215
  Lines             ?     6339
  Branches          ?      835
=========================================
  Hits              ?     3723
  Misses            ?     2152
  Partials          ?      464

Impacted Files
Coverage Δ
Complexity Δ

...amework/cloud/contract/spec/internal/Common.groovy
31.81% <ø> (ø)
11 <0> (?)

...k/cloud/contract/verifier/util/ContentUtils.groovy
84.96% <ø> (ø)
52 <0> (?)

...ct/spec/internal/HandlebarsContractTemplate.groovy
0% <0%> (ø)
0 <0> (?)

...ework/cloud/contract/spec/internal/Response.groovy
28.2% <0%> (ø)
6 <0> (?)

...rk/cloud/contract/spec/internal/FromRequest.groovy
0% <0%> (ø)
0 <0> (?)

...ier/builder/SpockMessagingMethodBodyBuilder.groovy
57.44% <0%> (ø)
16 <1> (?)

...der/SpockMethodRequestProcessingBodyBuilder.groovy
79.31% <100%> (ø)
23 <1> (?)

...ract/verifier/util/JsonToJsonPathsConverter.groovy
75.77% <100%> (ø)
79 <1> (?)

...r/dsl/wiremock/WireMockResponseStubStrategy.groovy
85.71% <100%> (ø)
8 <1> (?)

...kMvcSpockMethodRequestProcessingBodyBuilder.groovy
92.85% <100%> (ø)
10 <2> (?)

... and 13 more

Continue to review full report at Codecov.

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

The only thing i can think of is that it would be nice if the response body had nicer formatting in the Wiremock stub, but that would probably be more realistic if it wasn't an escaped string.

No way to change this. We're using WireMock's API and this is how it stores data


Summary:

Moved jest-dom/extend-expect into a setup file (jest-setup.ts) that runs at the start of Jest
Swapped map for forEach where we were just iterating instead of returning values
Pulled options?.filter into a variable for static analysis and address rules-of-hooks warning
Swapped screen out for local render result container in all tests
Created a helper to get all rows within the body getBodyRows (Removes the invalid role attribute)
Created a helper to get a specific row within the body getRow which returns the element as baseElement and all the helpers of within.
Cleaned up an invalid typing {} to Record<string, unknown>
Fixed utils.spec.ts tests which were always passing due to the assignment operator
Import through index.ts file to ensure everything works
Renamed test-coverage to test:coverage to match the test:watch syntax

Codecov Report

Merging #30 (6bff165) into master (250a068) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage   97.70%   97.54%   -0.16%
==========================================
  Files           4        3       -1
  Lines         218      204      -14
  Branches       49       48       -1
==========================================
- Hits          213      199      -14
  Misses          5        5

Impacted Files
Coverage Δ

src/index.ts
100.00% <ø> (ø)

src/hooks.tsx
97.23% <100.00%> (ø)

src/utils.ts
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 250a068...6bff165. Read the comment docs.


Bug fix for line fluid inertia forces, and Wavekin 7 Ud_z

When lines compute the fluid inertia forces, they didn't include segment submergence in the calculation. It's possible that the code as written expects the volume array to take that into account, which does not currently happen. If you look at the section that computes the mass matrix for each node, it includes a correction for submergence along with the volume array. If we want to rewrite these so that the volume array is actually submerged volume, that's definitely possible. I don't know if there's an advantage one way or the other.
Additionally in the code for wavekin 7, which sums up component waves at all the nodes, there was a missing minus sign for the z component of the water acceleration. It looks like this issue is specific to this wave mode, it is not present in wave mode 2, which uses the same function to calculate those values as wave mode 3, so those probably both work correctly.
At some point I'll probably write some water velocity/acceleration unit tests for all the wave modes just to sanity check them, and make it easy to validate any future wave modes.
Update:
I've also gone ahead and fixed a relative minor issue with the wave kinematics (that I introduced along with wave stretching), where previously points out of the water were given zero velocity, and acceleration for their wave kinematics. This can cause issues in situations where a point is near the water surface, and the object itself has some amount of submergence. A good example would be a line modeling some sort of floating hose, what can float with its central axis out of the water. Now, points out of the water get the water kinematics at the waters surface below them, and have to do their own handling of submergence.

Most of this looks great. Good catch on adding the submergence fraction for fluid inertial loads on lines.
I don't think there was actually an issue with the wave stretching before. At least from a quick look, it seems like Wheeler stretching is being used, but the adjustment in this PR caps things at the free surface in the manner of "vertical stretching", which is a different method. I think not doing this capping was correct. Does it cause any problems?

With Wheeler stretching, a "stretched z" of 0 always refers to the instantaneous free surface. So if we first stretch, and then cap the stretched z to a value of 0, we always return the value at the free surface. And if we don't add a cap, we could end up returning values where the vertical scaling factor (like cosh(k * (z + h)) / sinh(kh)) is increasing the velocities and acceleration in a way that doesn't reflect what the object partially submerged would experience.
I might agree that in most cases this actually has a negligible effect, the thing with the bigger effect is removing the pos.z > surface_height check that would return zero velocity. If you think it's more correct without the stretched z capping, it's definitely an easy change.

@mattEhall would you change the stretched z capping or shall I proceed merging?

I merge this before https://github.com/FloatingArrayDesign/MoorDyn/issues/112 happens. Later on we can decide whether we go with the stretched z capping or not


Documentation for specifying slaves in the .yml is wrong.

The readme says to specify the slaves as a string:
slaves:
primary_slave:  slave_for_reads
slave_2:  slave_for_reporting
but the code is looking for a symbol so it doesn't use the slave:
def primary_slave_name
:primary_slave
end
The documentation should be changed to reflect this.
slaves:
:primary_slave:  slave_for_reads
:slave_2:  slave_for_reporting

Thanks, will fix shortly.

This is fixed in commit 330916dfa3e1d - you can specify either way now


chore: Fix pre-commit hooks for filenames with spaces, on Windows

Added double quote marks around {staged_files} within lefthook.yml file, as suggested by Clare Macrae.
Tested and confirmed to eliminate the pre-commit fatal error that I'd previously encountered when attempting to commit new and edited md files in the \docs directory.
How has this been tested?
Within this branch I created a new markdown file in \docs\Getting Started, then successfully performed a git commit without encountering the "pre-commit fatal error" that I'd experienced previously.
(I then reset that branch to the commit containing only the config file change and deleted the test-lefthook-config.md file -- so the branch that's the basis for this pull request contains only the config file change.)
Types of changes
Changes visible to users:

[x] None

Internal changes:

[x] Infrastructure  (I think that this is the most appropriate options)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My change has adequate Unit Test coverage.

Terms

[x] My contribution follow this project's contributing guide
[x] I agree to follow this project's Code of Conduct

Thanks!
In my initial review, all lines showed up as changed - so I reverted it to Unix EOLs and pushed.

Hi @therden,
Many thanks for this.
For your later changes, please could you check your settings in your Tasks repo and make sure that git is configured to use Unix EOLs? Thanks.
I had thought that someone had done that in the project config already, but it seems maybe not. Or maybe it wasn't configured for YAML?

Hi @claremacrae,
It looks like git provides two ways to control line endings.  The older way is via .gitconfig (which I've edited in my forked repo so that git uses Unix line endings in the files I edit, and then added to .gitignore); the newer way uses .gitattributes.
You're right that the Tasks repo's .gitattributes file contain a line for YAML files.
Scanning through the repo for file extensions, it appears that when the line

*.yml text eol=lf

is added to .gitattributes, you may also want to add

*.sh text eol=lf
*.txt text eol=lf

and possibly even

*.py text eol=lf

Hope this helps!


Uncaught TypeError: Cannot read property 'focus' of null

[Enter steps to reproduce below:]

...
...

Atom Version: 1.7.3
System: Ubuntu 16.04
Thrown From: platformio-ide-terminal package, v2.0.9
Stack Trace
Uncaught TypeError: Cannot read property 'focus' of null
At /home/cxy229/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:93

TypeError: Cannot read property 'focus' of null
    at /home/cxy229/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:93:23

Commands
     -9:35.6.0 application:add-project-folder (atom-text-editor.editor.is-focused)
     -9:16.3.0 tabs:close-all-tabs (li.texteditor.tab.sortable.active.right-clicked)
     -9:03.2.0 platformio-ide-terminal:toggle (atom-text-editor.editor.is-focused)

Config
{
  "core": {}
}

Installed Packages
# User
platformio-ide-terminal, v2.0.9

# Dev
No dev packages

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34239387-uncaught-typeerror-cannot-read-property-focus-of-null?utm_campaign=plugin&utm_content=tracker%2F31220268&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F31220268&utm_medium=issues&utm_source=github).

Same issue here. Worthwhile noting that this error is not limited to this package, its parent package (terminal-plus) also has a similar error (see issue #265).

My full details were:
Atom Version: 1.7.4
System: Ubuntu 16.04
Thrown From: platformio-ide-terminal package, v2.0.10
Stack Trace
Uncaught TypeError: Cannot read property 'focus' of null
At /home/fusion809/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:94

TypeError: Cannot read property 'focus' of null
    at /home/fusion809/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:94:23

Commands

Config
{
  "core": {
    "customFileTypes": {
      "source.ini": [
        ".buckconfig",
        ".flowconfig"
      ],
      "source.json": [
        ".arcconfig"
      ],
      "source.lisp": [
        ".emacs",
        ".spacemacs"
      ],
      "source.python": [
        "BUCK"
      ],
      "text.html.basic": [
        "ejs",
        "htm",
        "html",
        "kit",
        "shtml",
        "tmpl",
        "tpl",
        "xhtml"
      ]
    },
    "disabledPackages": [
      "language-markdown",
      "atom-beautify",
      "atomic-chrome",
      "build",
      "Hydrogen",
      "git-plus",
      "language-asciidoc"
    ],
    "projectHome": "/home/fusion809/GitHub/mine",
    "themes": [
      "fusion-ui",
      "dark-bint-syntax"
    ]
  }
}

Installed Packages
# User
dark-bint-syntax, v0.8.4
file-icons, v1.7.12
fusion-ui, v0.10.3
language-gfm2, v0.88.2
language-ini, v1.16.0
language-liquid, v0.5.1
language-lisp, v0.2.0
language-lua, v0.9.4
language-rpm-spec, v0.9.0
language-viml, v1.0.0
package-sync, v1.1.0
pigments, v0.26.3
platformio-ide-terminal, v2.0.10

# Dev
No dev packages

what triggers these errors? Anything, it seems, it does not seem to matter what I do, this error still pops up.

I believe this is about 2 (or more) monitors. This error pops up when I move my mouse pointer to the other monitor.

Na, I get this error and I've never even used two monitors. I'm working on a laptop.

A solution has been found it would seem. Back at the terminal-plus GitHub repo issue #270 has a solution and I'm gonna create a pull request to implement it.

still exists...
I've found it occurs when I have one atom window on my first and one on my second monitor and then close one of them...

+1

[Enter steps to reproduce below:]

...
...

Atom Version: 1.11.1
Electron Version: 0.37.8
System: Ubuntu 16.04.1
Thrown From: platformio-ide-terminal package, v2.2.0
Stack Trace
Uncaught TypeError: Cannot read property 'focus' of null
At /home/reza/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:102

TypeError: Cannot read property 'focus' of null
    at /home/reza/.atom/packages/platformio-ide-terminal/lib/status-bar.coffee:102:23

Commands
     -5:51.9.0 settings-view:open (ul.list-inline.tab-bar.inset-panel)
     -5:47.5.0 core:paste (atom-text-editor.editor.mini.is-focused)
     -5:46.4.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -3:47.4.0 settings-view:open (div.platformio-ide-terminal.status-bar)
     -3:43.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -3:04.2.0 tree-view:add-folder (div.header.list-item)
  3x -3:01.5.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -2:59.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -2:54.9.0 tree-view:add-folder (div.header.list-item)
  8x -2:53.3.0 core:backspace (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "ignoredNames": [
      ".git",
      ".hg",
      ".svn",
      ".DS_Store",
      "._*",
      "Thumbs.db",
      ".pioenvs",
      ".piolibdeps",
      ".clang_complete",
      ".gcc-flags.json"
    ]
  },
  "platformio-ide-terminal": {
    "core": {
      "autoRunCommand": "export PATH=/home/reza/.atom/packages/platformio-ide/penv/bin:/home/reza/.rbenv/plugins/ruby-build/bin:/home/reza/.rbenv/shims:/home/reza/.rbenv/bin:/home/reza/bin:/home/reza/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
    }
  }
}

Installed Packages
# User
atom-html-preview, v0.1.22 (active)
autocomplete-clang, v0.10.0 (active)
autocomplete-java, v1.2.5 (active)
autocomplete-ruby, v0.1.0 (active)
build, v0.65.0 (active)
busy, v0.7.0 (active)
file-icons, v1.7.22 (active)
git-plus, v5.18.0 (active)
java-importer, v1.4.1 (active)
javascript-snippets, v1.2.1 (active)
language-ini, v1.16.0 (active)
linter, v1.11.18 (active)
linter-gcc, v0.6.15 (active)
linter-javac, v1.9.4 (active)
linter-ruby, v1.2.2 (active)
platformio-ide-terminal, v2.2.0 (active)
run, v0.0.1 (active)
tool-bar, v1.0.1 (active)
wakatime, v6.0.10 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

I just got this error again with v2.2.1.

when I open 'platformio-atom-terminal', I will get this error once I switch to another monitor.
so I delete some lines in 'status-bar.coffee', and this error cannot show up again-.-

@zzploveyou could you share here which lines you have removed?

delete '@returnFocus.focus()' from below:
handleFocus = =>
      if @returnFocus
        setTimeout =>
          @returnFocus.focus()
          @returnFocus = null
        , 100

It does not influence of using this package.

PlatformIO IDE Terminal v2.2.2 is out. Please update.


update npm

In npm repository uploaded version 1.0.0. Please update to 1.2.0

Sorry about that.  It's updated!


Automate service cleanup

Consul does not unregister services with status "Critical" by itself, I have included a demo project that polls Consul and unregisters dead services.
This should be automated instead

Done


linked to Inbound Parse User Guide page

Cross linked between Inbound Parse API Reference and User Guide

Hello @eschallock,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team DX


Wrong return types for addEventListener in AppStateStatic and LinkingStatic

Description

Return types for addEventListener in both AppStateStatic and LinkingStatic are 'void'. However if I console.log the following code:
const appChangeListener = AppState.addEventListener('change', handleAppStateChange);
console.log(appChangeListener);

I see this in my console:

I believe the return type of  addEventListener should be NativeEventSubscription. This is how it is typed in BackHandlerStatic:

Version
0.68
Output of npx react-native info
System:
OS: macOS 11.5.2
CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
Memory: 41.42 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.17.5 - /usr/local/bin/node
Yarn: 1.22.17 - ~/.npm-global/bin/yarn
npm: 6.14.14 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /Users/matt/.gem/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
Android SDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7583922
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
Languages:
Java: 11.0.10 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.0 => 0.68.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

Compare output of AppState.addEventListener() to output type

Snack, code example, screenshot, or link to a repository
No response

I believe this is not linked to the react-native repository, but rather to https://github.com/DefinitelyTyped/DefinitelyTyped/, and the types have been updated in this PR: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/55659

I believe this is not linked to the react-native repository, but rather to DefinitelyTyped/DefinitelyTyped, and the types have been updated in this PR: DefinitelyTyped/DefinitelyTyped#55659

Thanks for the heads up @AntoineDoubovetzky
Closing, feel free to reopen @mattg95 if the issue persists


The product's image is adjusted when the user is trying to view any product.

Bagisto Version: Master
Steps To reproduce--
1. Log in as a customer.
2. Click on any configurable product.
3. Select the variant of the product.
4. Over the mouse on a mini image of the product.
Expected result: The product's image is adjusted when the user is trying to view any variant of the configurable product.
Actual result: The product's image should not be adjusted when the user is trying to view any variant of the configurable product.
. Please find the screens recording Here

@jitendra-webkul
Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.

@jitendra-webkul
I am reopening this issue. because i am getting the same issue if there are multiple image of any product,
Please find the screenshot Here

@jitendra-webkul
Now, this issue is fixed. so I am closing this issue.


https://github.com/lestrrat-go/libxml2/blob/master/clib/clib.go Package Build is failing with  "could not determine kind of name for C.free"

This happens after the last change has been made for this repo.
https://github.com/lestrrat-go/libxml2/commit/b65cd51053703d2b0eb6992c8a815430474578ed
Before that it was working as expected
Describe the bug
While downloading the below package
https://github.com/lestrrat-go/libxml2/blob/master/clib/clib.go
Getting the Error message as "could not determine kind of name for C.free"

To Reproduce / Expected behavior

I can't reproduce it. Just a guess but perhaps you are using an old Go version?

It fails with the same error with the latest GO version as well Go 1.22.4

Bummer. But I since I can't reproduce it, I can't do much. Please provide a reproducible scenario.

This happens after the last change has been made for this repo. b65cd51
Before that it was working as expected
Describe the bug While downloading the below package https://github.com/lestrrat-go/libxml2/blob/master/clib/clib.go Getting the Error message as "could not determine kind of name for C.free"
To Reproduce / Expected behavior

I also have a similar problem
How did I solve it?

Install required system packages
for Ubuntu
sudo apt install icu-devtools libicu-dev

for Docker
`FROM golang:alpine as builder
RUN apk update && apk add --update --no-cache
ca-certificates
gcc
musl-dev
libxml2
libxml2-dev
icu
icu-dev`

In command to build executable add special flag
CGO_CFLAGS="-I/usr/include/unicode"

That's all

Still, we are facing the same issue  :(
/go/pkg/mod/github.com/lestrrat/go-libxml2@v0.0.0-20180221004755-bb78334e2019/clib/clib.go:489:8: could not determine kind of name for C.free

@Priyankasoni037 as I already said, you need to isolate what it is that differs from the CI environment that produces your error. Otherwise I will never be able to do anything on this.


Fix racy joinSandbox behavior

The current lazy network sandbox initialization code has a race
in that if multiple go routines race to join the network the second
and subsequent go routines might try to use the sandbox before it is
fully initialized. Fix this by blocking the go routines in once.Do
calls and also take of care of rolling back properly in case of
error.
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

LGTM

@mrjana thanks for addressing the comment. LGTM.


cymem 2.0.7

Recipe directory diff between current master and this update:
diff --git a/recipe/meta.yaml b/recipe/meta.yaml
index 726f347..0b581c9 100644
--- a/recipe/meta.yaml
+++ b/recipe/meta.yaml
@@ -1,6 +1,6 @@
 {% set name = "cymem" %}
-{% set version = "2.0.6" %}
-{% set sha256sum = "169725b5816959d34de2545b33fee6a8021a6e08818794a426c5a4f981f17e5e" %}
+{% set version = "2.0.7" %}
+{% set sha256sum = "e6034badb5dd4e10344211c81f16505a55553a7164adc314c75bd80cf07e57a8" %}

 package:
   name: {{ name }}

Jira ticket: PKG-462 (cymem-2.0.6)
The upstream data:
Github releases:  https://github.com/explosion/cymem/releases
Diff between the latest and previous upstream releases
License: https://github.com/explosion/cymem/blob/master/LICENSE
Requirements:

setup.py:  https://github.com/explosion/cymem/blob/v2.0.7/setup.py
pyproject.toml:  https://github.com/explosion/cymem/blob/v2.0.7/pyproject.toml

Actions:

Notes:
*
Package's statistics

Priority D | effort: easy | Category: other_key_deps | subcategory:  | pkg_type: python
Outdated platfroms: 'linux-64', 'linux-aarch64', 'linux-ppc64le', 'osx-64', 'osx-arm64', 'win-64'
Latest version: 2.0.7
Release on PyPi:

version: 2.0.7
date: 2022-10-14T14:18:40

PyPi history
Popularity:

3 months downloads: 108607.0
All time:  1099624 downloads -  cymem  2.0.7  Manage calls to calloc/free through Cython

Other checks:

[x] https://github.com/explosion/cymem/tree/v2.0.7 exists

[x] https://github.com/explosion/cymem is present

[ ] Check the pinnings

[ ] Changelog url error:
https://github.com/explosion/cymem/tree/v2.0.7
200

[ ] Additional research
https://github.com/explosion/cymem/issues
200

[x] dev_url is present
https://github.com/explosion/cymem

[x] doc_url is present
https://github.com/explosion/cymem/blob/master/README.md

[ ] Verify that the build_number is correct

[x] has setuptools

[x] has wheel

[x] pip in test

[ ] Verify the test section

[ ] Verify if the package is architecture specific

[ ] Verify that private modules are not mentioned in the recipe For example: (_private_module)

[x] license_file: LICENSE is present

[x] License: MIT
[ ] License is spdx compliant

Check if the license identifier has correct name from the SPDX License List

Identifier

MIT

MIT-0

MIT-advertising

MIT-CMU

MIT-enna

MIT-feh

MIT-Modern-Variant

MIT-open-group

MITNFA

[x] license_family MIT is present

Links:

Anaconda Recipes feedstock
Update branch
conda-forge recipe
PyPI
Diff between upstream and feature branch
Diff between origin and feature branch
The last merged PRs

Updating the recipe:
If the recipe needs additional modification the update branch can be modified. Note that the PR diffs are not updated with these changes.
git clone -b 2.0.7 git@github.com:AnacondaRecipes/cymem-feedstock.git

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a09cbxgy_p/clone/recipe/meta.yaml:39: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
WARNING: /tmp/abs_a09cbxgy_p/clone/recipe/meta.yaml:51: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_a09cbxgy_p/clone/recipe/meta.yaml:51: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found


Azure Container Registry - Waiting for an agent...

For Deploy Run Container App Service (https://docs.microsoft.com/en-us/learn/modules/deploy-run-container-app-service), exercise "Build and store an image by using Azure Container Registry" I get stuck waiting when uploading the image to the registry, I have tried several times without luck.
dhanjel@Azure:~$ cd mslearn-deploy-run-container-app-service/ dhanjel@Azure:~/mslearn-deploy-run-container-app-service$ az acr build --registry registrydhanjel --image webimage . Packing source code into tar to upload... Excluding '.git' based on default ignore rules Excluding '.gitignore' based on default ignore rules Uploading archived source code from '/tmp/build_archive_5469ea6d36b84ec1b65b71ea4fd7dbc6.tar.gz'... Sending context (691.287 KiB) to registry: registrydhanjel... Queued a build with ID: cd5 Waiting for an agent...
Registry name is correct as far as I can see:

@yunyunyunyun to follow-up with the correct owner for this report.

Still experiencing an infinite "Waiting for an agent..." ):

I am experiencing the same issue. Any ideas?

We've been seeing this issue occur again today (2024-01-22) and have opened a case with Microsoft<PHONE_NUMBER>010490).
As far as I can tell, it appears to be an issue on the Microsoft side for resource allocation of ACR builds.

i have the same problem

Same here

Am experiencing the same problem. Based on recent comments, it seems to be a problem on Azure's side.


Request: Allow runspaces to access "shared" pre-loaded modules.

I understand that it is possible to Share variables and Objects between PowerShell runspaces.
I also understand that it is possible to pre-load modules with InitialSessionState, however this still results with having to wait for modules to load as each runspaces is created.
Runspaces are great, but when working with larger modules that take a few seconds to load into memory this starts to create significant resource costs, negating a lot of their potential benefit. For example, if I want to create 100s of runspace instances over a few minutes to undertake multi-threaded procedures due to certain triggers... having to import modules for every instance reduces the potential value of using runspaces.
To get around this, would it be possible to pre-load "shared" module(s) which are accessible to all runspaces, so there is no need to load required modules every time we kick off a new runspaces instance.

Modules is loaded in their own context so I believe it is possible to share them. Interesting whether they thread-safed?

It is not possible to share variables between runspaces as they are not thread-safe.
InitialSessionState doesn't pre-load modules. It takes a list of modules to load when the runspace is opened.
Ultimately, modules can only be loaded into a runspace and everything in a module is tied to that runspace. In other words, the minimum context for a module is the runspace.


Fix typos in readme

one more try to fix two typos if that is OK, also remove trailing white space.

broke my fork so closing for now.


Multi-lang: lang-switcher on Grav 1.7b not working as expected...

Regular pages, not flex.  It can be observed with grav-learn repo using the versions for languages.

Fixed in 8ac3451fbccb1f5d2223525bb3c922776ac98fbf (accidentally wrong commit message)


Make wire protocol more efficient.

The selling point of using a schema registry is to reduce the bytes in flight, so that we can send data as efficient as possible as in large mass data throughput system every byte really counts, also to avoid the schema or meta data dwarfing the real data we want to send.
Currently wire protocol uses up 12 bytes for just identifying the schema of the data, when in fact in we have a unique 8 byte (int64 - java long) id available to us (SchemaVersionStorable id).
This could even be reduced just to 4 byte (int32 - java int) to reduce further by using one protocol id byte to send if the id < Int.Max (and just using 4 bytes) and another protocol id to send if the id > Int.Max (and then using 8 bytes)
Current:
(protocolId = 0x1)
        byteArrayOutputStream.write(new byte[]{0x1});

        // 8 bytes : schema metadata Id
        // 4 bytes : schema version
        byteArrayOutputStream.write(ByteBuffer.allocate(12)
                                            .putLong(schemaIdVersion.getSchemaMetadataId())
                                            .putInt(schemaIdVersion.getVersion()).array());

Proposed:
(protocolId = 0x1, or 0x2)
if (SchemaVersionStorable.id < Int.max) {
        byteArrayOutputStream.write(new byte[]{0x1});

        // 4 bytes : schema version id (as int)
        byteArrayOutputStream.write(ByteBuffer.allocate(4)
                                            .putInt( (int) SchemaVersionStorable.id).array());
} else {
        byteArrayOutputStream.write(new byte[]{0x2});

        // 8 bytes : schema version id (as long)
        byteArrayOutputStream.write(ByteBuffer.allocate(8)
                                            .putLong( SchemaVersionStorable.id).array());
}

Saving 8 bytes!!!! when the id < Max.Int which in reality is unlikely to reach this man, but still we cater for incase.

@michaelandrepearce Thanks for bringing this issue. It was discussed earlier among ourselves before making this repo public and there was an internal JIRA filed.
Custom protocol support is added to allow users have their own protocol and they do not necessarily use the default when it does not suit their needs.
Long can be avoided as it does not make much sense in reality for this usecase. Integer gives ~4.2billion numbers and 2,147,483,648 positive ids which means 21+ million schemas with 100 versions, very unlikely to reach this limit. We can even have logic to wrap to negative ids but that may be unnecessary.

Agreed long can be avoided :) this is what this proposes.
But as the id in the schema repo is long, we should cater for it at least in the eventuality of something crazy occurring. We obviously avoid it in the serialisation by having it kept as an int if the number is of int scale, which obviously we hope it always should be.

@satishd we agreed to align this then? and also benefit from the confluent protocol interop?

@satishd we agreed to align this then? and also benefit from the confluent protocol interop?

@michaelandrepearce Right, we can have new protocol to address these issues.

The other benefit of this, is mixing in with my other issue re compatibility with the confluent protocol ;) , i think really we want to make migration away as easy and as smooth as possible right? As in less barriers to entry increase the uptake (which I'm sure we want)

Right, we would like to have smooth and easy way to integrate current applications using confluent schema registry. Current protocol versioning support allows to support that, you may have observed  the current protocolid is 1 and confluent ser/des have version as 0 which we can accommodate to accept confluent related ser/des without any conflicts.

@michaelandrepearce I can pick this up if you have not already started working on this issue.

@satishd Was awaiting the merge of the other PR, then went on long weekend leave. Was planning to do it this week. But if you wish to pick up happy for you to do so.

@michaelandrepearce I will pickup this and raise PR soon.

@satishd great thanks, will look forward to review. Can you ping me/@ sign me when pr is raised

@michaelandrepearce Sure, I will do that.

@satishd how did you progress on this?

@michaelandrepearce I was working on other issue about cleaning up APIs. It seems you are waiting for this change, I will make the respective changes today.

@satishd yes we are.
Also obviously awaiting the next tag which would include this and all the confluent compatibility bits to be in a release version, when do we think we'd be spinning another release? end of this month?

@michaelandrepearce I have added 0.3.1 as next minor milestone. You can tag any issues you would need with that milestone. We can decide the target date based on the pending issues.
cc @harshach

@satishd it seems i don't have the ability / permissions to add labels or select a milestone on issues.

@michaelandrepearce Added you to the list. Please let me know whether you are able to add labels/milestones on issues etc.

#150 addressed this issue.

@satishd thanks, i am now able to, have done so.


Reuse of the ViewHolder class name

Use CostomViewHolder instead of ViewHolder for custom View Holder.
https://github.com/googlesamples/android-RecyclerView/blob/master/Application/src/main/java/com/example/android/recyclerview/CustomAdapter.java#L39

Sure, though it doesn't seem like a big problem. A pull request would be welcome.
Did you notice this while using any particular static code checker?

I made this suggestion to Arthur in the office the other day. I was referencing snippets of the sample when writing something up and the reuse of the ViewHolder class name doubled the explanation length. Referencing CustomViewHolder as a class would have been much more concise and I believe it makes the snippets more readable when viewed in isolation. Just a suggestion.


OpenCV was not built with OpenGL support

Which means imshow can't display a GpuMat without a download. Fix is to track down opengl dev packages in ubuntu's repos and add them to the apt-get install stanza.

Hi, can you please elaborate a bit on the proposed fix? It's not clear to me at all, what should I do in such a case. Is this before running the script or after?

Hi, can you please elaborate a bit on the proposed fix? It's not clear to me at all, what should I do in such a case. Is this before running the script or after?

So, in order to directly imshow a GpuMat without downloading it to a Mat, you need to build OpenCV with OpenGL support or you get this error:
... Library was built without OpenGL support ...

Generally this means tracking down some blablabla-dev package in Canonical's apt repositories and making sure it's installed before build.
To answer your question, you could either install such a package before running the script or add it somewhere in this list here:
https://github.com/mdegans/nano_build_opencv/blob/0832a850f33a64e3c14de065ed205db863b25f0e/build_opencv.sh#L64
it's likely these packages:
https://askubuntu.com/questions/306703/compile-opengl-program-missing-gl-gl-h#comment1952106_866868
So just adding mesa-common-dev, libglu1-mesa-dev, freeglut3-dev, libglfw3-dev and libgles2-mesa-dev will probably fix it. I don't know exactly which if those OpenCV actually requires. Possibly just the first. Possibly all of them. You can test and see. I haven't had time to recently or to look into exactly what cmake is expecting.
If it works, you should see:
--     OpenGL support:              YES

If you do, and get a GpuMat displaying directly in imshow feel free to submit a PR closing this issue out.

OK, will try that and submit a PR if that works.
One more question though... Can I just rerun the script after installing the packages, do I somehow have to uninstall it first (I have already built opencv).


librealsense2: 2.44.0-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository librealsense2 to 2.44.0-1:

upstream repository: https://github.com/IntelRealSense/librealsense.git
release repository: https://github.com/IntelRealSense/librealsense2-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.10.7
previous version for package: 2.42.0-1

Closing and reopening to try to get the jobs to rerun.

I'm going to leave this one for @tfoote to look at, since it involves the remaining regressions on Kinetic.

#29242 depends on this one. Please try to merge it or else remove #29242 as it will fail building looking for version 2.44 of librealsense2.

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-final-kinetic-sync/19805/6


produce figures showing ∆ANPP by species

Let's prepare figures like current figure 2 for each species. On the colorbar, include both absolute change (Mg ha-1 yr-1) and % change (relative to that species' ANPP)-- they will scale linearly. Also, add % change to the all-species colorbar.

Modification: rather than sorting by species, sort by climate variable. Tentatively, I'd like to replace the second panel in previous Fig. 1 with ∆ANPP (by species) for the full time period.

Back to this, I'm now not sure which of the arrangements described above we'll want to show. I'd like to see how the results look before deciding. Please make draft plots in whichever arrangement is easiest (saving the matrix of underlying values), and we will go from there.

@teixeirak, I think I am a bit confused with this and might wait until we can talk in person.

@teixeirak, is this what you were thinking ?

Newest figure looks like this:

Looks great in general! Could you please make a few minor changes?:

could you please put the max value back to +0.65 on this one?
Scale on % response needs to be multiplied by 100.
Add label on i): ANPP (Mg ha-1 yr-1)

Oh yes, thanks for catching that, I forgot to update the legend.
I pushed the fixed version.


Why?Can't I try it anymore?

Doesn't it really work? Actually I am searching for such a tool like this. Is there anything like Faitagram? Please inform me. Can't I try this tool for once? I wanna try to see if it really works or not. It will be really a pleasure to me if I find such a tool.

A lot of Instagram Bruteforce Tools have been patched because instagram doesn't pass the "Password" in the ajax request, they only pass the "Username" and "Encrypted Password"

Well. Would you like to suggest me some tools please?

Well. Would you like to suggest me some tools please?

+1


Fix github workflow to use Containerfile

We changed the file but did not update the workflow.

/retest

/override rdoproject.org/github-check


Add indicator constraint support in from_docplex_mp translator

Summary
Adds support of indicator constraints in from_docplex_mp.
This implementation is based on #151.
Fixes #13
Closes #151
Details and comments

I merged #170 and resolved conflicts


Is there a way to zero-copy tch-rs::Tensor as candle_core::Tensor?

I am working on some project that started as tch-rs, and would like to know if there is any way to convert a tch-rs::Tensor as a candle_core::Tensor? preferably zero-copy?

I don't think there is anything no-copy possible at the moment, you would have to extract the whole content of the tch tensor and then create a new candle tensor with Tensor::from_vec.

Thank you for taking the time to reply.
Yeah that's what I thought... I did try to extract everything one by one,  but honestly it was much faster to save the tch::Tensor to disk  first and then load the candle_core::Tensor using mmap. But I was wondering if I there was another more "graceful" and efficient solution.


DatArchive.download('/') returns before the archive is completely available to Beaker

Paul: Thank you for Beaker. I've put together an experimental version of the Hotglue site-building tool to run on top of the DatArchive API (hotglue-dat), and tried it out with other people at the our networks conference this weekend. Here some issues I encountered (in this and following bug) - hope you find those helpful.

let fork = await DatArchive.fork(url);
await fork.download('/');
window.location = fork.url;

It appears that download returns before the entirety of the site is available to Beaker, since the navigating to the URL is reproducibly showing a directory listing (with some files missing), rather than the content of index.html. This is at least on Beaker 0.8.8 (haven't tested other versions).
(Currently working around this by delaying redirect by two seconds, but I am not sure if this would reliably work with larger archives.)

Previously reported in https://github.com/beakerbrowser/beaker/issues/1275


Add support for badges on top TabFolder bar

Problem description
At the moment the Tab badge is only shown on a TabFolder with tabBarLocation set to 'bottom'. At least on Android the material design guidelines allow to have a top badge as well.

Expected behavior
Display badges on the top TabFolder bar.
Environment

Tabris.js version: 3.4

Code snippet
import {contentView, Tab, TabFolder, TextView} from 'tabris';

contentView.append(
  <TabFolder stretch>
    <Tab title='Cart' badge={5}>
      <TextView center text='Content of Tab Cart'/>
    </Tab>
  </TabFolder>
);

After further research it turned out that the iOS platform does not support the top badge. We could therefore implement it as an Android only feature.

Implemented for the 3.5 release via the native platform and https://github.com/eclipsesource/tabris-js/commit/2262b6ce83f056de0663b6e46a52536537f9f03d


Remove conda dependency for sh installation

Follow-up of #12
Remove conda dependency for sh installation

Great! Thanks!


fix: Collection variable viewer

Due to changes in https://github.com/usebruno/bruno/pull/650 collection variables would be passed as an object but were expected to be an array. Collection variables are now converted to an array.
Fixes: #1940

Also, we should later remove the Show secret variable values button for Collection.

I tested locally this bugfix it works, could it be merged please ?

Merged!
Thank you @Its-treason !
This will go out in the 1.13.0 release. Please subscribe to Discord announcement channel to stay notified on the releases.


Specify Notify delivery method

This was removed as part of the Rails 7 upgrade. It was discussed
a little here:
https://github.com/alphagov/support-api/pull/628#discussion_r832024631
In retrospect, this has caused emails to fail to be sent. Related
Zendesk tickets:

https://govuk.zendesk.com/agent/tickets/4932239
https://govuk.zendesk.com/agent/tickets/4931891
https://govuk.zendesk.com/agent/tickets/4927683

Confirmed this works on Integration, by building the branch to Integration and setting my email as one that can have emails sent to it by Notify on Integration. Tried exporting CSV with my branch and with the latest release, only my branch sent an email.