Split headers by week

I would like to be able to split up headers by week, and noticed in a comment that you were planning on doing this:
https://github.com/namespace-ee/react-calendar-timeline/blob/master/src/lib/utility/calendar.js#L41
I wanted to ask if this feature is still in your roadmap, when you think it'll be available, or if there's anything I can help with it.

I am currently evaluating if we can use this library in one of our projects. I'm currently trying to implement a week view as well as a three row header layout. The three row header layout is necessary for us too, in order to keep the UI context when weeks are used.
You can find my version at: https://github.com/dkarnutsch/react-calendar-timeline/tree/feature/weeks
With the three row header layout everything is working fine, when using the two row header layout I examine the same problems as mentioned in #130.
I'm available to help and we want to get this branch merged. We are open to rename or refactor the code. The current implementation would be breaking as I changed the naming of headerLabelGroupHeight to 'middleHeaderLabelHeight' and headerLabelHeight to bottomHeaderLabelHeight. Accordingly we have added topHeaderLabelHeight and a switch to choose between two or three row header layout (useThreeRowHeader). I'm open for better names, but group and label makes it hard to add a third layer, also because it is not used consequently. I can also provide backwards compatibility if that is something that is required.

No there is not.  If this is something that you need specifically for your project, you can always fork and publish your own version to npm.

Maybe together we can fix the bug, as I'm keen to help. We just need to clarify what the expected result should be.
Should weeks be optional or mandatory?
Also the timeSteps are kind of vague, which I will try to illustrate.
Starting at the smallest unit possible. We can see one hour and its minutes.

We can't zoom in any further and by clicking the hour we can zoom out. Everything is ok.
Now we have the day with its hours.

We can zoom in to see the hours and we can zoom out to see the week.
Now we have the week with its days.

We can zoom in to see the days and zoom out to see the month(?)

And this is actually where the problem is. We see the month as weeks. The top row should contain the month and the bottom row the weeks right? Also the situation would change if weeks are optional.

While digging into the code I found another interesting case:
When having a small window like:

I would expect that clicking the top header would result in zooming out, which is actually what is happening. But when clicking the bottom header I would either expect to zoom in to the minutes or not resulting in any change if the minutes can not be displayed due to lacking space. But it is also zooming out, which I think is wrong.

Is this feature likely to be merged anytime soon? I was looking at potential timelines which handle a by week basis and this looks very promising.

@RC1245 no one has updated this for a while now. #349 will make it easier to implement but I am afraid no one is working on this.
I will close the PR for inactivity. Please feel free to pick it up again and implement this


Ensure e2e tests run in production mode

References

Fixes a bug in e2e tests which was an accidental side effect of #2464
Also fixes an issue where statistics cannot be generated consistently for homepage e2e tests

Description
Currently, if you run yarn e2e locally (or in CI), the i18n files don't load properly.  This results in all the i18n labels being shown instead of the translated text.
This also is causing e2e test failures for the homepage-statistics.cy.ts on main and dspace-7_x because that e2e test selects fields using the translated i18n keys, e.g. it looks for a link named "Statistics" here https://github.com/DSpace/dspace-angular/blob/main/cypress/e2e/homepage-statistics.cy.ts#L8
The issue is that yarn e2e isn't specifying NODE_ENV=production.  That small change fixes things for i18n & gets e2e tests succeeding again.
Another issue was also found where statistics were not generated consistently, so they are now mocked/stubbed in a "fixture" file.
Instructions for Reviewers

Assuming e2e tests now succeed, then this fix is working.  Currently several PRs are seeing failures in the homepage-statistics.cy.ts e2e test which seems to be caused by this bug.  Specifically these two PRs show that failure on their latest builds: #2364 and #2597

Is this a race condition? Perhaps we can replace for an arbitrary wait time for waiting on an element to appear? I wouldn’t expect the accessibility checker to have to wait indefinitely but rather for the significant elements of the page. Perhaps a generic page loaded component could be used or an ngzone check or something like that.

@wwtamu : I don't believe the issue is a race condition (but I could always be wrong).  When I download the e2e test videos (which are generated automatically when failures occur), it shows that the Statistics page loads but has no statistical data in it.  The test that's failing requires statistical data (as that's what we are trying to run an accessibility check on -- the display statistical data itself).
I've not yet figured out why this isn't working in GitHub CI as it works locally when I run the test via yarn e2e.  So, I'm still debugging what is going on & I'm a little confused why this isn't working myself.

Couldn't hurt to create another branch merging in main. I am going to attempt that as an easy step.

I am not having any luck with these tests. However, I have found cloud.cypress.io to be helpful in showing possible integrations.

Today I finally had a chance to revisit this, and I've figured out the fix.  I'm going to close this PR as it's not a correct fix & has gotten messy with tests.
New PR coming soon which is already succeeding for me in GitHub CI (in my personal account) and locally.

Replaced by #2603


How can i improve the quality of video or photo captured by ARVideoKit

Hi, ARVideoKit is very useful to me.
I discover that the quality of photo/video i captured by using ARVideoKit is not the same what i see in the screen (downgraded in resolution i guess).
So i want to know
How can i improve the quality of video or photo captured by ARVideoKit?
Is there any ways to change the resolution?
Thanks a lot.

Currently I would suggest you to config your ARWorldTrackingConfiguration setting in the run time. It has several video settings including higher quality video. (And it also is supported to be configured in the run time.


[BUG] an exception occurred while running Bloxstrap

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[X] I did not answer truthfully to all the above checkboxes.

[x]  I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[x]  I am using the latest version of Bloxstrap.
[x]  I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
sawdsawdsawdsawdsa wdsa r
Bloxstrap Log
N/A sdkanwdsawd

Okay i actually dont know how i can help you unless you provide a log file, so that can give us further information on what is possibly the problem

sasdsasdfasdfdsdfgfsasdfdsdfghgADFDSASGFDSASDFSasasdfgfdsasdfgfdaqsdffgfdasfgfssdfdsasdfdsasdfdsadfdasdfdsasdf


December update: Most of standard objects are not available

In December update, most of standard objects cannot be referenced in extension.
For example, it is not possible to extend Customer table or Page, because they are not available in symbols.

This will happen if you're using the C/SIDE side by side feature and haven't run finsql command=generatesymbolreference. Is that your case?

No. I am using microsoft/dynamics-nav:devpreview-december docker image and i get this situation out of the box.
I have tried microsoft/dynamics-nav:devpreview-december-fingb it works fine.  Is this intended behavior?

I'm also unable to reference application objects - e.g. the Hello World generated by "Al! Go" does not compile.
I'm running the NAV2018 RTM DK version. Not using Docker.
I've ran the generatesymbolreference (takes about 5 minutes) twice, downloaded symbols, restarted visual studio code. Nothing seems to work for me.
I can reference system objects such as the Company table though.
The following is configured on the NST:

Allowed Extension Target Level: Internal
Enable Developer Service Endpoint
Enable loading application symbol references at server startup

Found solution to my problem on Twitter.
I had installed the latest AL Language extension from VS Code's extension manager.
Uninstalling that and then installing using the vsix file from the dvd solved my issue.


ENH: programmatic way to enable array API support

Is your feature request related to a problem? Please describe.
As of now, it is possible to enable array API support in scipy by setting the SCIPY_ARRAY_API=1 environment variable prior to importing scipy.
In scikit-learn we would like to enable array API support programmatically but this is not really possible because scikit-learn's array API support now relies on scipy's.
Would it be possible to enable array API support in scipy programmatically, after importing scipy?
Describe the solution you'd like.
I could be a "private" API function that would stay private as a long array API support stays private but ideally it would be a "semi official" way to do it so that scikit-learn can enable it when the users asks to able array API in scikit-learn.

I could be a "private" API function that would stay private as a long array API support stays private but ideally it would be a "semi official" way to do it so that scikit-learn can enable it when the users asks to able array API in scikit-learn.

I can send a PR for a "private" version of this soon. I'm not yet sure whether it makes sense to offer this more officially.


ESLint syntax checker ignores .eslintignore

When I open files ignored by my project's .eslintignore errors and warnings are still highlighted. These errors will not be reported by running eslint directly.
Disclaimer: I have very little understanding how how all the pieces of this project fit together.

Unless configured otherwise, syntastic runs eslint -f compact file.js and shows you whatever errors eslint produces.    If you get something else then eslint is not run the way you believe it is.  You can see what syntastic is doing in the debug logs (:h syntastic-config-debug).  You can change what syntastic is doing by setting the apropriate options (:h syntastic-config-makeprg).
If you don't want syntastic to run checks automatically then set passive mode (see :h :SyntasticToggleMode and :h 'syntastic_mode_map').  If you want syntastic to run checks automatically but skip certain files see :h 'syntastic_ignore_files'.  If you want syntastic to run checks but ignore certain errors see :h 'syntastic_quiet_messages'.

Right. This seems to be caused by a bad interplay between :autochdir and eslint's method of searching for .eslintignore (not traversing up the path). I'll open an issue with ESLint.
Thanks for the detailed response.

For anybody else interested in this issue, this is certainly not an issue with syntastic (it affects command line ESLint too).
I spoke to @ilyavolodin on Gitter regarding this issue. This is intentional behaviour of eslint as it has no way of determining 'project root' from a subdirectory. Previously this was supported (called "cascading" .npmignore), but was dropped due to a bad code complexity to usefulness ratio.


Update CACert & OpenSSL

What does this PR do?
Update the build images & omnibus software to update OpenSSL & CACert
Motivation
Fixing a security vulnerability in OpenSSL and keeping our CACert bundle up to date.
BARX-558
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Google Drive Business Issue (GSuite)

Bug description:
When try to add an GSuite account to Google Drive service, I receive the error attached. The system realizes the login and 2FA but, at main screen the Google Drive indicate the message "You're not connected", with try again button
Steps to reproduce:

Add Google Drive Service
Login at Google Drive with a GSuite account
Approve 2FA
See the error message

Expected behavior

Screenshots

Environment:

Operating System: Windows 10
Ferdi Version: 5.5.0
Server: Ferdi, Franz, Using with an account

I'm having trouble with 2 step verification with my Gsuite account.
When I try to log in using SMS 2 step, I receive the code but nothing happens when I confirm-it.
The device appears in my google account, but I can access Google Chat through Ferdi.
I was able only to login using it google backup codes.


Fix getext dep install

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1118d31). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             master        #3   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         2
  Lines             ?        17
  Branches          ?         0
==========================================
  Hits              ?        17
  Misses            ?         0
  Partials          ?         0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update version of actions/cache

It seems we depend on actions/cache indirectly through setup-r-dependencies and we are currently using v2 https://github.com/extendr/extendr/blob/7e41a09686066b11878e415eea8cb968c91399f2/.github/workflows/test.yml#L205-L216
I encountered an issue with this cache in my forked repo (e.g., this), so I found this issue https://github.com/actions/cache/issues/811.
From the discussion there I found out the latest version of actions/cache is 3.0.3 (released quite recently), so perhaps it is time to switch to the newer version for us?

This is invalid, I incorrectly interpreted this field as a version of actions/cache, not the version of cache itself. I am closing this issue, sorry for unnecessary noise.

I think you can send a pull request to update this line.
https://github.com/r-lib/actions/blob/9ea29bb8182371e811c469f947bc64ac054b557f/setup-r-dependencies/action.yaml#L61


SAAS-728 update link to onegini docs

IMHO we should archive this project rather than maintain it anyhow 😅  The implementation is already dated, we are not managing any dependencies and have 0 knowledge about the security of this proposal.

fine with me, just let me know how to do it ;)


After update to v1.4.0 "sudo: unknown uid<PHONE_NUMBER>: who are you?"

Describe the bug
i updated ddev to verison 1.4.0 it always displays this error sudo: unknown uid xxxxxxxxx: who are you?  when i  call ddev start.
ddev is installed with homebrew.
ddev show: Failed to start ddev: web container failed: log=, err=container exited, please use 'ddev logs -s web` to find out why it failed
ddev logs -s web =>
+ DDEV_PHP_VERSION=7.2
+ DDEV_WEBSERVER_TYPE=nginx-fpm
+ '[' -n htdocs ']'
+ export WEBSERVER_DOCROOT=/var/www/html/htdocs
+ WEBSERVER_DOCROOT=/var/www/html/htdocs
+ export NGINX_DOCROOT=/var/www/html/htdocs
+ NGINX_DOCROOT=/var/www/html/htdocs
+ '[' -f /mnt/ddev_config/nginx-site.conf ']'
+ '[' -f /mnt/ddev_config/apache/apache-site.conf ']'
+ '[' -n 7.2 ']'
+ update-alternatives --set php /usr/bin/php7.2
+ ln -sf /usr/sbin/php-fpm7.2 /usr/sbin/php-fpm
+ export PHP_INI=/etc/php/7.2/fpm/php.ini
+ PHP_INI=/etc/php/7.2/fpm/php.ini
+ '[' -d /mnt/ddev_config/php ']'
+ '[' typo3 = backdrop ']'
+ rm -f /etc/nginx/nginx-site.conf
+ '[' -f /etc/nginx/nginx-site-typo3.conf ']'
+ ln -s /etc/nginx/nginx-site-typo3.conf /etc/nginx/nginx-site.conf
+ rm -f /etc/apache2/apache-site.conf
+ '[' -f /etc/apache2/ddev_apache-typo3.conf ']'
+ ln -s -f /etc/apache2/apache-site-default.conf /etc/apache2/apache-site.conf
+ envsubst '$WEBSERVER_DOCROOT,$NGINX_DOCROOT'
+ envsubst '$WEBSERVER_DOCROOT'
++ id -u
++ id -g
+ printf '\nexport APACHE_RUN_USER=uid_1553427339\nexport APACHE_RUN_GROUP=gid_637725509\n'
+ '[' nginx-fpm = apache-cgi ']'
+ '[' nginx-fpm = apache-fpm ']'
+ '[' false '!=' true ']'
+ disable_xdebug
Disabled xdebug
+ ls /var/www/html
++ id -u
++ id -g
+ sudo chown -R<PHONE_NUMBER>:637725509 /mnt/composer_cache/
sudo: unknown uid<PHONE_NUMBER>: who are you?

Version and configuration information (please complete the following information):

Host computer OS and Version: macOS Mojave]
Docker version:

Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:21:31 2018
 OS/Arch:           darwin/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:29:02 2018
  OS/Arch:          linux/amd64
  Experimental:     true

ddev version :

dba           	drud/phpmyadmin:v1.4.0
router        	drud/ddev-router:v1.4.0
domain        	ddev.local
cli           	v1.4.0
web           	drud/ddev-webserver:v1.4.0
db            	drud/ddev-dbserver:v1.4.0
ddev-ssh-agent	drud/ddev-ssh-agent:v1.4.0
commit        	v1.4.0

No custom configurations

Additional context
Add any other context about the problem here. Thanks!

Thanks for your care in writing this very clear issue.
The problem is obviously sudo: unknown uid<PHONE_NUMBER>: who are you?<PHONE_NUMBER> is way outside the range of uids for Linux (and macOS).
Do you have any customization at all in your .ddev directory, like changes to the config.yaml or docker-compose.*.yaml? If so, please back those out for starters.
On your mac, what does id tell you?
Thanks!

I assume you're on macOS Mojave? It seems the range for UIDs on Mojave was somehow increased over the traditional. I'll have a workaround soon. We've always had to adapt on this problem with Windows, not sure why there's be a difference in v1.4.0.

Please try this temporary workaround, I think it will work for you.
Add a docker-compose.uid.yaml in your project .ddev directory with these contents:
version: '3.6'
services:
  web:
    user: "1001:1001"
  db:
    user: "1001:1001"

And then ddev start. That will make the containers run as 1001 instead of your outrageous Mojave uid :) We'll get this solved in v1.5.0 or sooner. I do with I knew how and when these huge UIDs started on macOS.

ohw wauww, thanks a lot it works now - and if you know the workaround, it's easy :-)  🥇

Reopening, we'll need to solve this.

The immediate problem here is https://github.com/drud/ddev/blob/e4726e05a277a4702556001f5e63ced058ce24e9/pkg/ddevapp/ddevapp.go#L846-L851
This stanza actually used to change the uid/gid if they were >60000, but no more; now (assuming this problem only occurred on Windows) we use an arbitrary UID only if the uid is non-numeric. See https://github.com/drud/ddev/blob/1893afc3dede578ec1de06473ff972ff225862a9/pkg/util/utils.go#L147-L168
Also, the message about running as root is incorrect and should have been gotten rid of.

For everyone affected by this bug, we have a fix for this in https://github.com/drud/ddev/pull/1285 and are considering a point release. Could you please test the version downloadable from https://circleci.com/gh/drud/ddev/6007#artifacts/containers/0 ? @shilgendorff and any others.

@rfay Tested: Confirmed I am now able to ddev start container and ddev ssh into the container. Once in the container id correctly returns uid=1000(uid_1000) gid=1000(gid_1000) groups=1000(gid_1000). Thank you very much for getting this issue resolved so quickly.

@shilgendorff I would recommend just doing a quick test within the download folder for this version:
Within the download folder execute ./ddev version to verify you are utilising that version of ddev.
From there create a new directory within that folder, for example:
mkdir ddev-fix-test

Change to this directory and setup a simple php container with ddev, start that container, then enter the container and run id to check if the container is using the correct uid:
cd ddev-fix-test
../ddev config --project-type php --php-version 7.1
../ddev start
../ddev ssh
id

Should print: uid=1000(uid_1000) gid=1000(gid_1000) groups=1000(gid_1000)
As for working with the fix, I would either swap back to 1.3.0 for now by doing the following:
brew list --versions ddev
brew switich ddev 1.3.0

or you could move the fix to your working directory and execute your ddev commands like above we did above for the test
for example:
./ddev config
./ddev start
./ddev sequelpro

etc.
Hope this helps.

We released v1.4.1 with this fix in it just now, https://github.com/drud/ddev/releases/tag/v1.4.1
If you use homebrew, you can brew upgrade ddev
Thanks all for your help.


Missing appRoles definition for manual application creation

Hey guys
There are two issues I discovered when implementing WAC in my lab, first is that the automatically generated Enterprise Application doesn't allow you to use the Application Proxy.
Second issue is that the documentation fails to mention that roles need to be defined in the application manifest json. I had to manually explore through the manifest of the auto-generated app to find the needed role definitions:
{ 			"allowedMemberTypes": [ 				"User" 			], 			"description": "Gateway administrators can modify gateway configurations.", 			"displayName": "Gateway Administrator", 			"id": "guid", 			"isEnabled": true, 			"lang": null, 			"origin": "Application", 			"value": "Admin" 		}, 		{ 			"allowedMemberTypes": [ 				"User" 			], 			"description": "Gateway users can access and use the gateway, but not configure the gateway.", 			"displayName": "Gateway User", 			"id": "guid", 			"isEnabled": true, 			"lang": null, 			"origin": "Application", 			"value": "User" 		},
Without those roles, WAC wouldn't work when Azure AD integration is enabled.
It would definitely be worth adding this in. I removed the guids because it seems those are not hard coded in WAC.
Thanks
Mateusz

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

ID: 374adde8-b1b0-d416-bae0-4d60b0a71a5a
Version Independent ID: 6473aeec-c2ed-b085-e7c9-a535b333f0ab
Content: Configuring Azure Integration
Content Source: WindowsServerDocs/manage/windows-admin-center/azure/azure-integration.md
Product: windows-server
Technology: manage
GitHub Login: @Haley-Rowland
Microsoft Alias: harowl

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


feat: seed all tags

do we want to use the old id's for the tags? This seems like a good idea to me.


enforcing clang-format?

I am not sure what formatting is used by unbound code base, and failed to find guidance, but I know that any time I do work on it, I have to disable auto-formatting in my editor or I get huge diffs which are mostly dealing with whitespaces.
I don't really mind what formatting is used, but I like not to have to care about and letting my text editor do it for me :)
I think clang-format is rather widely adopted, and would like to suggest it for unbound. But in the end, whatever is used as long as it is easy to find guidance as to what to use. Possibly with macros or whatever that allow easy discovery.
What do you think?

So the formatting used by Unbound (and also NSD by the way) is the formatting, per file or per piece of file that that author made.  And I am loath to change it, because I do not want to unsettle the code. So based on where you insert the code I would want it to fit in nice.  So this explains what the formatting is like today.  And also why I do not really want to change it to a programmatic output, I prefer the original formatting and code additions looking good to match it.
Probably the format tool if it only adjusted the code that is being added, not all the rest of it, would be less intrusive, and look nice. (autoindent and smartindent work fine for me, by the way).

Thanks @wcawijngaards , yeah unfortunately, tools a la clang-format work on the whole file AFAIK.
Yeah, the diffs when formatting is applied is a bit painful, typically one would want to get the whole repo formatted in 1 commit. It does mess the blame a bit too, but then from there on, it makes formatting a no-brainer.

autoindent and smartindent work fine for me, by the way

yeah, I typically disable auto-formatting when doing stuff on unbound code base and let the formatting happening. In any cases, thought it was worth suggesting clang-format.

I agree with closing the issue here, but as an FYI, after looking up documentation on clang-format, it can be toggled with comments (/* clang-format off */ and /* clang-format on */) and with commandline options for byteranges or -lines=<start line>:<end line>.  Just to expose the feature, it seems very feature-rich by the way, but I still don't want a project wide format-wipe.  This kind of thing works better if you have it enabled at project start and have check-in tests, for Unbound this is something I did with splint and later code analysis features, and that kept the number of code anomalies down, on a commit-by-commit effort.


Validation Processor: FieldContext Creation

The FieldContext instance create in the validate routine when a validation check fails reflects on the field name in the invoking class without caching. Although validation failures are exceptional cases, this can present a problem especially as an attack vector (e.g. server performance can be severely affected by thousands of bad requests since the time to process them may be significantly greater).
We should consider either removing the context altogether (least desirable), constructing a custom context with minimal/equivalent information or improving the existing context or its construction to remove the reflection. There is another option which is to weave into the code a pre-made private static final context for each field.

Completed with #35


Evaluation

Sorry to disturbing you again, but I got a question when doing evaluation.
During training process, I saved best-3 model according to the mae and rmse, and I used the one with rmse = 16.2453 and mae = 11.7919 to do the evaluation in the same dataset, I mean use the same dataset as the training. I load the model as using following code:
model = get_model(
backbone=args.model,
input_size=args.input_size,
reduction=args.reduction,
bins=bins,
anchor_points=anchor_points,
prompt_type=args.prompt_type,
num_vpt=args.num_vpt,
vpt_drop=args.vpt_drop,
deep_vpt=not args.shallow_vpt
)
state_dict = torch.load(args.weight_path, map_location=device)
state_dict = state_dict if "best" in os.path.basename(args.weight_path) else state_dict["model_state_dict"] model.load_state_dict(state_dict, strict=True)
model = model.to(device)
And run the evaluation.py to test it, but got mae = 605.7568 and rmse = 606.5157.
It seems that the weight is loaded incorrectly. Is there any problem in my code?
I using following args:
"--model", "clip_vit_b_16",
"--weight_path", "./checkpoints/rgbt/clip_vit_b_16_word_448_8_4_fine_1.0_dmcount/best_rmse_0.pth",
"--anchor_points", "average",
"--dataset", "mydataset",
"--truncation", "4",
"--device", "cuda:0"

Can you make sure that the model is trained with 224x224 and evaluated using the sliding window method with the same window size (i.e., 224x224)?

In sliding_window_predict function, you input 5 arguments, but the function only takes 4 arguments. The arguments should be model, image, window_size and stride, but you input argument named "strategy".

And, I only input model, image, window_size and stride, with training image size and window size both equal to 448, the test result still keep the same.

Hi,
The issue in test_nwpu.py has been fixed. Training and testing models on private datasets are not guaranteed to work properly. Thank you for your understanding.


[right-click-tray] Right clicking a settings bubble while another settings tray is open misbehaves

The settings tray moves, but is not updated.
https://github.com/DesModder/DesModder/assets/68391527/90e197e7-7d29-4ee7-956f-2e26837b1276
I probably should write more here but I'm tired and cant be bothered to do that sorry

ah, I realize now that the video doesnt really show the tray moving. oh well

Thanks for the report and the video though!


Default tab title too long

The default title for my powershell tabs is so long that (a) it is cut off and (b) the 'X' to close the tab is not displayed, for example:

Environment
Windows build number: Microsoft Windows [Version 10.0.18362.239]
Windows Terminal version (if applicable):  0.3.2171.0

Any other software? no

I did edit the settings to make two changes:  The point size for all fonts is now 12 instead of 10 and CMD is the default instead of powershell.
Steps to reproduce
Open a powershell tab in Windows Terminal
Expected behavior
At a minimum, I would expect the tab close control to remain visible or at least a click where the control belongs should close the tab.
Actual behavior
The long path appears to overwrite the close tab control and prevent any clicks from reaching the close tab control.

The TabView control template for the tab items, should ensure the close button gets priority as the control scales down.

@mdtauk that is an excellent thing to file over on microsoft/microsoft-ui-xaml./

In the mean time, override the title with tabTitle or change your shell configuration to set a better title.

#608

I don't really see the duplication as I was reporting that the close tab control was being overwritten by a long title, while #608 seems to be about configuring custom titles.  However, I can understand blaming something else, I do that all the time myself.  :-)
FWIW, If I add and remove more tabs, the tab with an over-long title will get 'fixed' to show the whole title and the close control.  I have been able to get a new tab to obscure the close control with much shorter tab titles, too, by adding tabs of different types -- it rarely takes more than one of two attempts, no matter which shell type I choose.  Oh well.  I tried.


Default to software rendering on Android Emulators

Android supports software rendering but it is currently opt-in (via the --enable-software-rendering engine flag).
Due to numerous rendering issues in emulated environments, we should consider switching to software rendering on emulators on Android. We already do this on iOS simulators.
So far, we have had issues around reliably detecting (at runtime) if the device is an emulator.
However, the tools can check if the ro.kernel.qemu property is set to 1 and have the tools automatically add the --enable-software-rendering flag. For users who have correctly configured their emulators to use the host GPU, this will probably cause a slowdown in rendering. However, software rendering is way more reliable and leads to fewer surprises. We can still allow (via the tools, as the default is always GPU rendering) the user to explicitly use GPU rendering.

FYI, detecting emulators can be tricky.  In case the ro.kernel.qemu check doesn't work, per @thomaswk:

ro.hardware will be "goldfish" or "ranchu" for "qemu" or qemu2 based emulators"

Making a mistake in detection of an emulator is probably not too risky because non tooling assisted launches will default to GPU rendering anyway. We should however make it clear that software rendering is being used.

FYI @741g (from Android Emulator) in case you or your team were curious to see this discussion go by.

What are the specific reasons for defaulting to software rendering on emulators?

I'm not very familiar with Android local development but will research how to determine what this property is set to when running with the flutter tool.
There've been a few ideas posted here, but for now I'm treating this issue as wanting to display the caveats/alternatives with the rendering modes the user has selected rather than altering the defaults.

unassigning; doctor license check taking longer than I thought to get right.

@gspencergoog has volunteered.

@Hixie my understanding is "hardware" rendering on iOS simulators isn't actually done in hardware.  The GL commands get rendered in software by the Simulator app.  Flutter is much faster when we just use Skia's software backend directly instead of bouncing through GL to have Simulator.app use a GL software backend. :)


Go Live [June 10]

Push to live

Docs Build status updates of commit cf15219:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/samples/virtual-assistant.md
:white_check_mark:Succeeded
View

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


Add sphinx.ext.linkcode

See this custom extension for how to resolve github urls
https://github.com/eventbrite/conformity/blob/master/conformity/sphinx_ext/linkcode.py

scanpydoc supports that to, and in a way that doesn’t break doc caching


Can not connect to Office 365 / Exchange Online with PowerShell

I can not connect to Office 365 / Exchange Online with PowerShell.
Apparently others can with the latest version of push, but it is not working for me on either macOS 10.12 or 10.13 with pwsh 6.0.0-rc
I get an error creating the New-PSSession. Depending on the exact syntax of the command I'm using, it either says New-PSSession : This parameter set requires WSMan, and no support WSMan client library was found, or PowerShell quits with an unhandled exception and abort trap 6.
Steps to reproduce
Install PowerShell 6.0.0-rc on macOS 10.12 or 10.13.
Use Get-Credential to get an Office 365 administrator credential and then use New-PSSession to create a new session.
[kai@blackmac ~]$ pwsh
PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/kai> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-rc
PSEdition                      Core
GitCommitId                    v6.0.0-rc
OS                             Darwin 16.7.0 Darwin Kernel Version 16.7.0: T...
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS /Users/kai> $UserCredential = Get-Credential

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>***********

PS /usr/local/microsoft> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
New-PSSession : This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system.
At line:1 char:12
+ $Session = New-PSSession -ConfigurationName Microsoft.Exchange -Conne ...
+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ResourceUnavailable: (:) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.PowerShell.Commands.NewPSSessionCommand

PS /Users/kai> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid -Credential $UserCredential -Authentication Basic -AllowRedirection

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Management.Automation.Remoting.PrioritySendDataCollection.Clear()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize()
Abort trap: 6
[kai@blackmac ~]$

You will note from the prompt in the last line above that it's dropped me back into the bash shell.
Expected behavior
It is expected that New-PSSession will work on macOS
Actual behavior
Depending on the precise syntax of the command, New-PSSession either returns an error message:
New-PSSession : This parameter set requires WSMan, and no supported WSMan client library was found
Or, New-PSSession has an unhandled exception and PowerShell quits with abort trap 6.
The differences in the syntax are with the ConnectionUri - whether or not there is a trailing slash on the uri seems to make the difference. With a trailing slash, I get the error about WSMan missing. Without the trailing slash, the PowerShell session aborts.
With trailing slash:
PS /Users/kai> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
New-PSSession : This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system.
At line:1 char:12
+ $Session = New-PSSession -ConfigurationName Microsoft.Exchange -Conne ...
+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ResourceUnavailable: (:) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.PowerShell.Commands.NewPSSessionCommand

Without trailing slash:
PS /Users/kai> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid -Credential $UserCredential -Authentication Basic -AllowRedirection

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Management.Automation.Remoting.PrioritySendDataCollection.Clear()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize()
Abort trap: 6

Environment data
PS /Users/kai> $PSVersionTable                                                                                Name                           Value
----                           -----
PSVersion                      6.0.0-rc
PSEdition                      Core
GitCommitId                    v6.0.0-rc
OS                             Darwin 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT ...
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This is working for me on 10.13.1.  Can you confirm that in $PSHome you have libpsrpclient.dylib?

PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/kai> cd $PSHome
PS /usr/local/microsoft/powershell/6.0.0-rc> ls -al *.dylib
-rw-r--r--  1 root  wheel    70224 31 Oct 17:27 System.Globalization.Native.dylib
-rw-r--r--  1 root  wheel    13484 31 Oct 17:27 System.IO.Compression.Native.dylib
-rw-r--r--  1 root  wheel    61460 31 Oct 17:27 System.Native.dylib
-rw-r--r--  1 root  wheel    16932 31 Oct 17:27 System.Net.Http.Native.dylib
-rw-r--r--  1 root  wheel    15132 31 Oct 17:27 System.Net.Security.Native.dylib
-rw-r--r--  1 root  wheel    46016 31 Oct 17:27 System.Security.Cryptography.Native.Apple.dylib
-rw-r--r--  1 root  wheel    75708 31 Oct 17:27 System.Security.Cryptography.Native.OpenSsl.dylib
-rw-r--r--  1 root  wheel  2571480 31 Oct 17:27 libclrjit.dylib
-rw-r--r--  1 root  wheel  6894904 31 Oct 17:27 libcoreclr.dylib
-rw-r--r--  1 root  wheel   883740 31 Oct 17:27 libdbgshim.dylib
-rw-r--r--  1 root  wheel   869664 31 Oct 17:27 libhostfxr.dylib
-rw-r--r--  1 root  wheel  1006336 31 Oct 17:27 libhostpolicy.dylib
-rw-r--r--  1 root  wheel   843792 14 Nov 11:37 libmi.dylib
-rw-r--r--  1 root  wheel  3081760 31 Oct 17:27 libmscordaccore.dylib
-rw-r--r--  1 root  wheel  2021168 31 Oct 17:27 libmscordbi.dylib
-rw-r--r--  1 root  wheel    20568  4 Nov 09:08 libpsl-native.dylib
-rw-r--r--  1 root  wheel   224784 15 Nov 07:39 libpsrpclient.dylib
-rw-r--r--  1 root  wheel   553360 31 Oct 17:27 libsos.dylib
PS /usr/local/microsoft/powershell/6.0.0-rc>

@kai-h you have the right library with the right file size and permissions.  Is DYLD_LIBRARY_PATH defined?  What is the output of $env:DYLD_LIBRARY_PATH?

It's undefined.
PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/kai> $env:DYLD_LIBRARY_PATH
PS /Users/kai>

What does [System.Environment]::Is64BitProcess return?

PS /Users/kai> [System.Environment]::Is64BitProcess
True

@kai-h try (in the terminal before starting pwsh):
export DYLD_LIBRARY_PATH=/usr/local/microsoft/powershell/6.0.0-rc:${DYLD_LIBRARY_PATH}
pwsh
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Thank you for your persistence with this. I'm still getting the same error though.
[kai@hobbes ~]$ export DYLD_LIBRARY_PATH=/usr/local/microsoft/powershell/6.0.0-rc:${DYLD_LIBRARY_PATH}
[kai@hobbes ~]$ pwsh
PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/kai> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>********

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Management.Automation.Remoting.PrioritySendDataCollection.Clear()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize()
Abort trap: 6
[kai@hobbes ~]$

I'd like to confirm that I can successfully connect to Office 365 from PowerShell hosted on an Azure Ubuntu virtual machine, using the exact same details as I'm trying on the Mac.
PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /home/kai>  $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-rc
PSEdition                      Core
GitCommitId                    v6.0.0-rc
OS                             Linux 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS /home/kai> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>********

PS /home/kai> Import-PSSession $Session
(at this point PowerShell starts loading remote modules etc and preparing the session)

What I'm going to do in order to remove any possible issues with me having tweaked something on my Mac that is conflicting with this is set up a clean install of macOS 10.12 and then a fresh install of PowerShell 6.0.0-rc and test if it works tonight.

It is dup #3606

Issue #3606 is kind-of a dup, but they also saw the error which I haven't seen occur in my testing.
New-PSSession : Unable to load DLL 'libpsrpclient':...

I have been able to reproduce this on a clean install of macOS 10.12.6 and a clean install of PowerShell 6.0.0-rc. Everything is with default settings, new admin account created on first boot and no settings changed for the Terminal app.
Last login: Thu Nov 30 08:11:57 on ttys000
Administrators-Mac-mini:~ admin$ pwsh
PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/admin> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-rc
PSEdition                      Core
GitCommitId                    v6.0.0-rc
OS                             Darwin 16.7.0 Darwin Kernel Version 16.7.0: T...
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS /Users/admin> $env:DYLD_LIBRARY_PATH
PS /Users/admin> [System.Environment]::Is64BitProcess
True
PS /Users/admin> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>*********

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Management.Automation.Remoting.PrioritySendDataCollection.Clear()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync()
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize()
Abort trap: 6
Administrators-Mac-mini:~ admin$

Here are the results on a clean 10.12.6 install
Last login: Thu Nov 30 08:48:11 on ttys000
Administrators-Mac-mini:~ admin$ pwsh
PowerShell v6.0.0-rc
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/admin> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>********

An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Management.Automation.Remoting.PrioritySendDataCollection.Clear() in /PowerShell/src/System.Management.Automation/engine/remoting/fanin/PriorityCollection.cs:line 158
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync() in /PowerShell/src/System.Management.Automation/engine/remoting/fanin/BaseTransportManager.cs:line 949
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync() in /PowerShell/src/System.Management.Automation/engine/remoting/fanin/WSManTransportManager.cs:line 1219
   at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize() in /PowerShell/src/System.Management.Automation/engine/remoting/fanin/BaseTransportManager.cs:line 998
Abort trap: 6
Administrators-Mac-mini:~ admin$

This could be related to the issues I was seeing that are documented on #4029
As it stands, PowerShell 6.0.0-rc requires the use of OpenSSL libraries installed by Homebrew

For help.
I had the same problem in a Debian 9 docker container. After read the comments above I saw thet there was some broken linkes libraries and it was because the system libraries are newer than expected. Then , i made some symbolic links and everything ran ok.
root@db70f6f67c51:/usr/lib/x86_64-linux-gnu# ldd /opt/microsoft/powershell/6.0.1/libmi.so
    _linux-vdso.so.1 (0x00007ffd4b7fd000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f86cb670000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f86cb46c000)
    libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007f86cb25e000)
    **libssl.so.1.0.0 =>  not found
    libcrypto.so.1.0.0 => not found**
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f86cac56000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f86cb88d000)
    libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007f86caa2e000)
    libcrypto.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 (0x00007f86ca5ca000)
    libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007f86ca3c4000)_

root@db70f6f67c51:/opt/microsoft/powershell/6.0.1# cd /usr/lib/x86_64-linux-gnu/
root@db70f6f67c51:/usr/lib/x86_64-linux-gnu# ln -s libssl.so.1.0.2 libssl.so.1.0.0
root@db70f6f67c51:/usr/lib/x86_64-linux-gnu# ls -l libssl*
-rw-r--r-- 1 root root 738444 Nov  2 11:29 libssl.a
lrwxrwxrwx 1 root root     13 Nov  2 11:29 libssl.so -> libssl.so.1.1
lrwxrwxrwx 1 root root     15 Feb 21 17:27 libssl.so.1.0.0 -> libssl.so.1.0.2
-rw-r--r-- 1 root root 431232 Dec 13 22:09 libssl.so.1.0.2
-rw-r--r-- 1 root root 442920 Nov  2 11:29 libssl.so.1.1
root@db70f6f67c51:/usr/lib/x86_64-linux-gnu# ln -s libcrypto.so.1.0.2 libcrypto.so.1.0.0
root@db70f6f67c51:/usr/lib/x86_64-linux-gnu# ldd /opt/microsoft/powershell/6.0.1/libmi.so
    _linux-vdso.so.1 (0x00007ffdde3b4000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4e51539000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4e51335000)
    libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007f4e51127000)
    libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f4e50ebe000)
    libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f4e50a5a000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4e506bb000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f4e51756000)
    libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007f4e50493000)
    libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007f4e5028d000)_

I was having a similar problem but for me the problem was with the -AllowRedirection Parameter.
Here is my output.

@SteveL-MSFT Should we consider this as unstable, as bad UX or as bad documented?

Is this something that's changed in the latest versions so that Basic auth doesn't work, or is it more than that? I'm happy to do some more testing if required.

On MacOS, I do see a regression in 6.0.1 with a consistent ERROR_WSMAN_INVALID_SELECTORS error. I don't see any issues in 6.0.0 and 6.0.2 and libpsrpclient hasn't changed across these releases.  The machine hasn't been upgraded to High Sierra yet so that might be contributing.

My testing was on a Mac that was recently upgraded from macOS 10.12 Sierra to 10.13 High Sierra. I also upgraded PowerShell from whatever version I had previously (likely to be 6.0.0 or 6.0.1) to the latest version 6.0.2. I also updated my MacPorts installation to the latest version and updated all of my ports. I have a symlink for PowerShell from where it expects to find the OpenSSL libraries as installed by Homebrew to where they are installed by MacPorts and this was all working prior to the upgrades for connecting to Office 365

I have powershell 6.0.2 installed.  I've installed MacPorts and created the OpenSSL pkg and installed that.  When I try to create $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionURI https://outlook.office365.com/powershell-liveid/ -Credential $O365Cred -Authenticatin Basic -Allowredirection, and I get the same error of New-PSSession : This parameter set requires WSMan, and no supported WSMan client library was found.
$Psversiontable
Name                           Value

PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Darwin 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:x...
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
What do I need to do to fix the issue of WSMan?

I am new to O365 and PS on Mac. I am facing the same error message here. Would appreciate any help I can get.
Name                           Value

PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Darwin 17.6.0 Darwin Kernel Version 17.6.0: Tue May  8 15:22:16 PDT 2018; root:xnu-4570.61.1~...
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
PS /Users/AdityaBhasin> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
New-PSSession : This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system.
At line:1 char:12

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -Conne ...

       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ResourceUnavailable: (:) [New-PSSession], PSRemotingTransportException
FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.PowerShell.Commands.NewPSSessionCommand

PS /Users/AdityaBhasin>
System Version:	macOS 10.13.5 (17F77)

WOW! Thank you so much @kai-h I went ahead to run command to update the open SSL with Homebrew and it now seems to work for me. I will update here if I face any new challenge.  Thanks again!

Installing PowerShell v6.0.4 on OSX 10.13.3 fixed the problem for me.
Install Link:
https://github.com/PowerShell/PowerShell/releases/download/v6.0.4/powershell-6.0.4-osx.10.12-x64.pkg

@kai-h Can you confirm?

Reopening this issue: version 6.1.0 on Mojave is resulting in the same issue when attempting to connect to Office 365.

This is also repro'ing for me with Mojave

This works for me with 6.0.4 on Mojave with OpenSSL libraries installed via MacPorts, NOT Homebrew.
[kai@blackmac ~]$ pwsh
PowerShell v6.0.4
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/kai> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.4
PSEdition                      Core
GitCommitId                    v6.0.4
OS                             Darwin 18.0.0 Darwin Kernel Version 18.0.0: Wed Aug 22 20:13:40 PDT 2018; root:xnu-4903.201.2~1/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS /Users/kai> office365.ps1

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>********

WARNING: The names of some imported commands from the module 'tmp_nlc54neg.nu0' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.                                                                                ModuleType Version    Name                                ExportedCommands                                                                                ---------- -------    ----                                ----------------                                                                                Script     1.0        tmp_nlc54neg.nu0                    {Add-AvailabilityAddressSpace, Add-DistributionGroupMember, Add-MailboxFolderPermission, Add-MailboxLocation...}

PS /Users/kai>

This also works for me when I've upgraded to 6.1.0 on Mojave.
To reiterate, I am using OpenSSH libraries from MacPorts and have linked them to the location that PowerShell expects to see them.
sudo ln -s /opt/local/lib /usr/local/opt/openssl/lib

Then, when I run pwsh
[kai@blackmac ~]$ pwsh
PowerShell 6.1.0
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/kai> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0
PSEdition                      Core
GitCommitId                    6.1.0
OS                             Darwin 18.0.0 Darwin Kernel Version 18.0.0: Wed Aug 22 20:13:40 PDT 2018; root:xnu-4903.201.2~1/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS /Users/kai> office365.ps1

PowerShell credential request
Enter your credentials.
User<EMAIL_ADDRESS>Password for user<EMAIL_ADDRESS>********

WARNING: The names of some imported commands from the module 'tmp_kllnlbam.5cg' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.                                                                                ModuleType Version    Name                                ExportedCommands                                                                                ---------- -------    ----                                ----------------                                                                                Script     1.0        tmp_kllnlbam.5cg                    {Add-AvailabilityAddressSpace, Add-DistributionGroupMember, Add-MailboxFolderPermission, Add-...

PS /Users/kai>

Using the MacPorts version of OpenSSL worked for me.

I'm reproducing this on Mojave with Macports OpenSSL:
Mac OS Mojave 10.14.5
Powershell 6.2.3
I installed powershell with homebrew
Name                           Value
----                           -----
PSVersion                      6.2.3
PSEdition                      Core
GitCommitId                    6.2.3
OS                             Darwin 18.6.0 Darwin Kernel Version 18.6.0: Thu…
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

I installed openssl using the MS doc instructions via MacPorts:
ws2784:~ travis.brackett$ port installed
The following ports are currently installed:
  openssl @1.1.1d_0 (active)
  zlib @1.2.11_0 (active)

I created the symlink:
sudo mkdir -p /usr/local/opt/openssl
sudo ln -s /opt/local/lib /usr/local/opt/openssl/lib

wsnnnn:~ travbrack$ ls -lha /usr/local/opt/openssl/lib/
total 14496
drwxr-xr-x  16 root  wheel   512B Nov 22 14:39 .
drwxr-xr-x  11 root  wheel   352B Nov 22 13:58 ..
-rw-r--r--   1 root  wheel     0B Oct 20 13:21 .turd_MacPorts
drwxr-xr-x   4 root  admin   128B Nov 22 14:39 engines-1.1
lrwxr-xr-x   1 root  wheel    14B Nov 22 14:28 lib -> /opt/local/lib
-rwxr-xr-x   1 root  admin   2.1M Sep 15 05:22 libcrypto.1.1.dylib
-rw-r--r--   1 root  admin   3.7M Sep 15 05:22 libcrypto.a
lrwxr-xr-x   1 root  admin    19B Sep 15 05:22 libcrypto.dylib -> libcrypto.1.1.dylib
-rwxr-xr-x   1 root  admin   479K Sep 15 05:22 libssl.1.1.dylib
-rw-r--r--   1 root  admin   704K Sep 15 05:22 libssl.a
lrwxr-xr-x   1 root  admin    16B Sep 15 05:22 libssl.dylib -> libssl.1.1.dylib
-rwxr-xr-x   1 root  admin    79K Oct  1  2018 libz.1.2.11.dylib
lrwxr-xr-x   1 root  admin    17B Oct  1  2018 libz.1.dylib -> libz.1.2.11.dylib
-rw-r--r--   1 root  admin    95K Oct  1  2018 libz.a
lrwxr-xr-x   1 root  admin    17B Oct  1  2018 libz.dylib -> libz.1.2.11.dylib
drwxr-xr-x   6 root  admin   192B Nov 22 14:39 pkgconfig
wsnnnn:~ travbrack$ ls -lha /usr/local/opt/openssl/lib
lrwxr-xr-x  1 root  admin    14B Nov 22 14:02 /usr/local/opt/openssl/lib -> /opt/local/lib

I restarted my terminal, and tried enter-pssession:
PS /Users/travbrack> enter-pssession computername
enter-pssession : This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system.
At line:1 char:1
+ enter-pssession computername
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidArgument: (computername:String) [Enter-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : CreateRemoteRunspaceFailed

Any assistance would be greatly appreciated

Commenting from #10600

I had the same issue, managed to solve it by linking an older openssl version from brew with brew switch openssl 1.0.2s

For me switching to openssl 1.0.2r worked as well. I had the openssl 1.1 installed through brew as default but they did not work

Hi guys,
regarding the openssl version, I forced brew to use ver 1.02 and this fixed my pwsh O365 issues. The commands I ran are ...
brew uninstall openssl;
brew uninstall openssl; (to ensure nothing was left lingering around)
brew install https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb
Credit : @kensoh
Thanks.

@leeharrison that worked for me running mojave with pwsh 6.0.4. I tried all previous suggestions and nothing else worked for me.

thanks @leeharrison I've also had this issue on High Sierra with pwsh 6.0.4 and your suggestion has fixed for me too.

Can we please ensure that PowerShell on macOS doesn't have a hard dependency on an older, and insecure, version of OpenSSL libraries? It is also bad practice to explicitly require that the library is installed by Homebrew with a hardcoded path.

Also see https://github.com/PowerShell/PowerShell/issues/11216#issuecomment-608221120

Hi guys,
regarding the openssl version, I forced brew to use ver 1.02 and this fixed my pwsh O365 issues. The commands I ran are ...
brew uninstall openssl;
brew uninstall openssl; (to ensure nothing was left lingering around)
brew install https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb
Credit : @kensoh
Thanks.

This is definitely well working !  Thank you.

Hi guys,
regarding the openssl version, I forced brew to use ver 1.02 and this fixed my pwsh O365 issues. The commands I ran are ...
brew uninstall openssl;
brew uninstall openssl; (to ensure nothing was left lingering around)
brew install https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb
Credit : @kensoh
Thanks.

This is working with Catalina 10.15.4

Hi guys,
regarding the openssl version, I forced brew to use ver 1.02 and this fixed my pwsh O365 issues. The commands I ran are ...
brew uninstall openssl;
brew uninstall openssl; (to ensure nothing was left lingering around)
brew install https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb
Credit : @kensoh
Thanks.

This is working with Catalina 10.15.4

How are you getting this to work without breaking other brew installed binaries?
Seems I can have either or when I tried it.
Either roll back openssl version, pwsh works but iperf3 breaks for example.

Can I please just put this out there that downgrading to an older, deprecated and therefore insecure version of OpenSSL is not a real solution.
Apple have already got a heap of different versions of the OpenSSL libraries installed on macOS.
Why does PowerShell on macOS have hardcoded paths to the libraries, instead of searching the system library path.
In the /usr/lib folder we have half a dozen different versions that are sitting there waiting to be used.
/usr/lib/libssl.0.9.8.dylib
/usr/lib/libssl.dylib
/usr/lib/libssl.35.dylib
/usr/lib/libssl.0.9.7.dylib
/usr/lib/libssl.43.dylib
/usr/lib/libssl.46.dylib
/usr/lib/libssl.44.dylib

Can I please just put this out there that downgrading to an older, deprecated and therefore insecure version of OpenSSL is not a real solution.
Apple have already got a heap of different versions of the OpenSSL libraries installed on macOS.
Why does PowerShell on macOS have hardcoded paths to the libraries, instead of searching the system library path.
In the /usr/lib folder we have half a dozen different versions that are sitting there waiting to be used.
/usr/lib/libssl.0.9.8.dylib
/usr/lib/libssl.dylib
/usr/lib/libssl.35.dylib
/usr/lib/libssl.0.9.7.dylib
/usr/lib/libssl.43.dylib
/usr/lib/libssl.46.dylib
/usr/lib/libssl.44.dylib

I hope you understand that those are older releases of OpenSSL. New release is v1.1.0 released August 25, 2016 -  Version 0.9.8 was released July 5, 2005. I ended up switching to Linux anyways since I can't deal with the implementation of OpenSSH on so many Windows servers and maintain them, but still looking forward on how kerberos will be supported for PSCore in future releases and if there is any care for it on macOS.

@mikeyjoel Please create new issue and describe remoting scenarios you want to work.

@mikeyjoel Please create new issue and describe remoting scenarios you want to work.

No need for me to create a new issue since an issue was already created: #3708
On RHEL/Centos or Debian/Ubuntu Distribution you'll need the following packages:
krb5-workstation
krb5-devel
gssntlmssp (requires epel-release to be installed beforehand)
powershell
Which are available by default for each Linux distribution. I'm bringing this up because its very common that you won't be just managing Office365 but also Windows Servers in your environment.

Can I please just put this out there that downgrading to an older, deprecated and therefore insecure version of OpenSSL is not a real solution.
Apple have already got a heap of different versions of the OpenSSL libraries installed on macOS.
Why does PowerShell on macOS have hardcoded paths to the libraries, instead of searching the system library path.
In the /usr/lib folder we have half a dozen different versions that are sitting there waiting to be used.
/usr/lib/libssl.0.9.8.dylib
/usr/lib/libssl.dylib
/usr/lib/libssl.35.dylib
/usr/lib/libssl.0.9.7.dylib
/usr/lib/libssl.43.dylib
/usr/lib/libssl.46.dylib
/usr/lib/libssl.44.dylib

I hope you understand that those are older releases of OpenSSL. New release is v1.1.0 released August 25, 2016 - Version 0.9.8 was released July 5, 2005. I ended up switching to Linux anyways since I can't deal with the implementation of OpenSSH on so many Windows servers and maintain them, but still looking forward on how kerberos will be supported for PSCore in future releases and if there is any care for it on macOS.

I am well aware that these are older OpenSSL libraries - however as pwsh currently only works with older libraries, they are already installed on macOS.

So I'm not sure where to share this but I've been recently playing around with OMI to try and get it working against a newer version of OpenSSL (1.1.0) as well as Kerberos auth (and hopefully NTLM as well) on a Mac. There are a few bugs that I've fixed up on a local build but it's definitely possible to get it working and I am planning on creating a blog post/guide on helping people do the same to get PSRemoting through WinRM on their non-Windows hosts.
I was wondering how interested the PowerShell team is in trying to incorporate those changes into their compiled build of OMI that they include in their release. I'm planning on trying to merge them into the OMI repo but I'm not optimistic they will actually make it in. The OpenSSL fix should also allow them to drop the requirement on OpenSSL 1.0.0 that they have documented in their install steps as it looks like it was only the PSRP client stuff that required those libraries.
This seemed to be the longest thread I could find on this problem so I thought it best to post here. Happy to create a new issue to compile the various problems and workarounds/fixes that I've found so we can document it properly for others wanting to try it out.

Hi guys,
regarding the openssl version, I forced brew to use ver 1.02 and this fixed my pwsh O365 issues. The commands I ran are ...
brew uninstall openssl;
brew uninstall openssl; (to ensure nothing was left lingering around)
brew install https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb
Credit : @kensoh
Thanks.

Found an easy and temporary workaround. Thanks to @kensoh and @leeharrison for pointing me into the right direction:
1.) Check if an old version isn't already installed
ls -al /usr/local/Cellar/openssl*
2.) Install old version (1.0.2t right now)
brew install https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb
3.) Switch to old version
brew switch openssl 1.0.2t
4.) Do Powershell shenanigans
5.) Switch back to new OpenSSL version (1.1.1g in my case, check Step 1. to find your version and Cellar Folder)
brew switch<EMAIL_ADDRESS>1.1.1g
Enjoy 😉

Why is this closed, it's still an issue. I was trying to execute: Enter-AzWebAppContainerPSSession but got the WSMan error and it seems this is an issue with PowerShell on Mac requiring OpenSSL 1.0.0 while I have 1.1.1g installed.

So I'm not sure where to share this but I've been recently playing around with OMI to try and get it working against a newer version of OpenSSL (1.1.0) as well as Kerberos auth (and hopefully NTLM as well) on a Mac. There are a few bugs that I've fixed up on a local build but it's definitely possible to get it working and I am planning on creating a blog post/guide on helping people do the same to get PSRemoting through WinRM on their non-Windows hosts.
I was wondering how interested the PowerShell team is in trying to incorporate those changes into their compiled build of OMI that they include in their release. I'm planning on trying to merge them into the OMI repo but I'm not optimistic they will actually make it in. The OpenSSL fix should also allow them to drop the requirement on OpenSSL 1.0.0 that they have documented in their install steps as it looks like it was only the PSRP client stuff that required those libraries.
This seemed to be the longest thread I could find on this problem so I thought it best to post here. Happy to create a new issue to compile the various problems and workarounds/fixes that I've found so we can document it properly for others wanting to try it out.

Hey @jborean93 whats the work around. I'm on Fedora 32 and this is annoying the bejesus out of me with the OpenSSL 1.0.0 requirement.

@alaurie if you aren't on macOS then you are somewhat in luck. The omi repo actually provides both an OpenSSL 1.0.0 and OpenSSL 1.1.0 universal package in their releases page. Just so I'm clear, this is in no way an official guide and merely something I run myself. Follow these instructions at your own risk and make sure you back up any files you replace.
Simply download the ssl_110.ulinux.x64.rpm package and either install or extract the RPM. Next you need to copy or symlink /opt/omi/lib/libmi.so to /opt/microsoft/powershell/7/libmi.so. From there you can verify that library it's linked to with ldd
# Before (what's included with PowerShell)
jborean:~/dev/$ ldd /opt/microsoft/powershell/7/libmi.so
ldd: warning: you do not have execution permission for `/opt/microsoft/powershell/7/libmi.so'
        linux-vdso.so.1 (0x00007ffff6fa8000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fc517d50000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fc517d49000)
        libpam.so.0 => /lib64/libpam.so.0 (0x00007fc517d37000)
        libssl.so.1.0.0 => /opt/microsoft/powershell/7/libssl.so.1.0.0 (0x00007fc517cc5000)
        libcrypto.so.1.0.0 => /opt/microsoft/powershell/7/libcrypto.so.1.0.0 (0x00007fc517a5a000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fc517890000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fc517f6b000)
        libaudit.so.1 => /lib64/libaudit.so.1 (0x00007fc517862000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fc517848000)
        libcap-ng.so.0 => /lib64/libcap-ng.so.0 (0x00007fc517840000)

# After (once you symlink libmi.so)
jborean:~/dev/$ ldd /opt/microsoft/powershell/7/libmi.so
        linux-vdso.so.1 (0x00007fffcffec000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fee443ed000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fee443e6000)
        libpam.so.0 => /lib64/libpam.so.0 (0x00007fee443d4000)
        libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007fee4433d000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007fee44050000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fee43e86000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fee44707000)
        libaudit.so.1 => /lib64/libaudit.so.1 (0x00007fee43e58000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fee43e3e000)
        libcap-ng.so.0 => /lib64/libcap-ng.so.0 (0x00007fee43e36000)

You can see that it's now linked to /lib64/libssl.so.1.1 and /lib64/libcrypto.so.1.1. I do not have any idea why the PowerShell package still uses the OpenSSL 1.0.0 universal package when the 1.1.0 is "officially" available. Maybe there was some issue in the past but a basic test works fine for me. In saying all this you will still probably come across a few issues with libmi like

Negotiate (Kerberos/NTLM) should work but I've found it only does so in very specific setups

I've actually changed the code on my own macOS build to fix some of the issues with GSSAPI auth in the OMI code
While you could theoretically build OMI yourself with those changes that's a lot more involved
Luckily O365/Exchange Online do not use Negotiate auth but just Basic auth so that's not a major problem

OMI does not offer any certificate validation over HTTPS

You need to ensure you add -SessionOption (New-PSSessionOption -SkipCACheck -SkipCNCheck) when you create your PSSession if you are willing to take that risk

For Debian based distros, the process will be similar you just need to be libmi from the .deb and not the .rpm. Also keep in mind the paths may be different. For those of you on macOS, I've found you always need to build omi yourself as there's no official package that's available. My own omi fork contains changes to the code that will allow you to build it on a newer macOS version. I've even got a small guide on how to do all that for macOS here.

@jborean93 You could open new issue in PowerShell-Docs repo - perhaps MSFT team will agree to add your investigations as unofficial/unsupported comment in PowerShell docs.

@iSazonov they could go one step further and actually bundle the libmi from the 1.1.0 OMI release so this whole process is unnecessary for the Linux distributions.
I'm reluctant to try and pursue this further officially because the common consensus is that WSMan on non-Windows is EOL. When trying to introduce changes into OMI officially to fix some problems when it came to building on macOS or general GSSAPI authentication problems I was effectively told no thanks. If someone from the PowerShell team is willing to investigate this further I'm happy to share the work I've done for macOS and look into updating the libmi version that is bundled with PowerShell.

@jborean93 I see they moved to OMI 1.6 https://github.com/PowerShell/MMI/blob/master/build.sh#L4 and I'd expect MMI 2.0 support OpenSSL 1.1.0.
PSRP package is still on OMI 1.5 but nuget package version 1.4 https://github.com/PowerShell/psl-omi-provider/blob/master/omi.version - it seems the OMI package support 1.1.0 but it is still linked to OpenSSL 1.0.0 - yes? and we should ask MSFT update to more new nuget package linked to OpenSSL 1.1.0 - yes?
(First OMI with OpenSSL 1.1.0 support is 1.4.0-6 https://github.com/microsoft/omi/releases/tag/v1.4.0-6)

It's getting late in the day for me so I'll have another look at it tomorrow. Just a few questions though:
Is MMI actually used for the native WSMan client. AFAIK the actual WSMan native dll is called through libpsrpclient on Unix. While MMI does actually use libmi through OMI it seems like that repo is used to create Microsoft.Management.Infrastructure.dll which is used by the various CIM components. Maybe they are still linked somehow but it seems like for Enter-PSSession it calls a method in libpsrpclient which then calls various methods in libmi. It seems like to make sure we get the newer binary for libmi we need to look at the build process and see how libmi is actually collected during the build process.
The psl-omi-provider AFAIK is the server plugin and is unrelated to any client based activities. I'm sure getting that working would be nice but honestly I think the client side is the most important part of this story.

we need to look at the build process and see how libmi is actually collected during the build process.

@PaulHigin Could you please explain how we get libmi in PowerShell distributive?

We do not support WinRM/OMI anymore.  I believe part of the reason is that OMI itself is no longer in support.  @TravisEz13 may be able to provide more information.

My question comes from the fact that there is already inconsistency - MMI was moved to new version some months ago but PSPR was not - and both reference libmi. I'd expect MSFT makes the minor update to PSPR package and close many questions about the issue.

@PaulHigin Could you please explain how we get libmi in PowerShell distributive? If it comes from PSPR package is its possible update the package to newer OMI version (to 1.5 or 1.6)?

You would have to ask the OMI team for this, and they have said they will not make changes or releases for PowerShell.

@TravisEz13 My ask about update OMI version in https://github.com/PowerShell/psl-omi-provider/blob/master/omi.version

@TravisEz13 the OMI team may not create any more releases for you but what’s stopping you from using one of the existing releases yourself. Seems like you currently do this for MMI so why is the WSMan client any different. Clearly you can use one of the newer releases that is compatible with OpenSSL 1.1.x and drop the requirement for OpenSSL 1.0.x which is outdated and probably insecure.
This whole setup may be deprecated but to me it’s clear that there’s still a use case for using WSMan. Why not try and have PowerShell be more useful on non-Windows platforms.

@jborean93 OMI is fundamentally broken.  If we move to 1.1, we will break distros that use 1.0.  It's a non-starter.

If we move to 1.1, we will break (segfault pwsh) distros that use 1.0

So only use libmi that is compiled against OpenSSL 1.1 for the distros that actually come with OpenSSL 1.1? Or better yet, have the OpenSSL 1.1 build as the default and just use existing OpenSSL 1.0 for the ones that don't have 1.1. Why should we hinder newer distro builds that can take advantage of newer libs. Hell even some of the more older distros that are supported by PowerShell offer both  OpenSSL libs.

OMI refuses to fix the fundamental issue that they don't load libraries correctly, causing segfaults.

While I totally understand not wanting to take on more work technically there's nothing stopping you from making the fixes yourself and compiling it specifically for PowerShell.
Also is the seg faults in relation to a known problem that's unrelated to OpenSSL or just a comment that trying to load it without the required libs will fail? If it's about the libs not being available then you already have that issue on newer distros that don't come with OpenSSL 1.0.x. Why should newer distros be hindered in the same way you are stating that older ones are hindered if the package is updated?

@jborean93 Your questions were answered in https://github.com/PowerShell/PowerShell/issues/5561#issuecomment-673652249

So only use libmi that is compiled against OpenSSL 1.1 for the distros that actually come with OpenSSL 1.1? Or better yet, have the OpenSSL 1.1 build as the default and just use existing OpenSSL 1.0 for the ones that don't have 1.1.

OMI refuses to fix the fundamental issue that they don't load libraries correctly, causing segfaults.

Just an FYI for anyone still interested in getting OMI working on Linux/macOS. I've just opened up my fork of the OMI repo which includes a wide range of fixes to get things working properly in PowerShell. You are more than welcome to have a look and play around with it if you wish. I've also written a blog post called Wacky WSMan on Linux to cover my journey in creating the fork and the various issues I came across.
Please bear in mind this is not affiliated with Microsoft or the PowerShell/OMI team in any way. The changes are my own and come with no warranty of guarantees of support. I'll try my best to help with any issues opened there if you are still having problems with the fork.

Today was the first time I was using PowerShell and I'm already disappointed.

Three years still a bug, and instead of Microsoft bringing a solution and update their dependencies, non-Microsoft people need to provide forks and workarounds.
Evidence of incapacity.

Still waiting for a fix...

Please re-open

Just to be sure I'm not missing something, I heard it was possible to run a Docker instance on macOS and spin up a PowerShell 7 core using mcr.microsoft.com/powershell — but when I tried that I hit the same roadblock. I believe this would only work for the Windows-based images, correct? So we're still stuck in the same boat ⛵

I've written up some instructions that work around these issues and are confirmed working with the latest version of PowerShell (I've tested with 7.1.0 Release) and any recent version of macOS (I've tested on macOS 11 Big Sur).
https://automatica.com.au/2020/12/installing-powershell-on-macos-for-remote-administration-of-microsoft-365/
Basically, install PowerShell via the pkg installer on GitHub. Then install MacPorts and with MacPorts install OpenSSL 1.0
sudo port install openssl10. Finally, symlink /opt/local/lib/openssl-1.0 to /usr/local/opt/openssl/lib
I am yet to test, but I believe this will NOT work on any of the new M1 arm64 architecture Macs as the PowerShell binaries are x86_64 yet the OpenSSL libraries installed by MacPorts will be arm64. I'm sure there is a way to specify that MacPorts installs the x86_64 version of a library on an arm64 machine, but I don't know how to.
Despite the fact that this works, it shouldn't need to be done.
PowerShell needs to work with up-to-date versions of OpenSSL. It should also NOT have hardcoded paths for support libraries. It should not require old, and known insecure, versions of third-party libraries.
All this is going to be a moot point in due course as the Mac version of PowerShell will not authenticate to MS365 with modern authentication, it only supports legacy authentication. I have been unable to get an answer about, or even find out who is responsible for, modern authentication in PowerShell on non-Windows platforms.

@kai-h That's a nice writeup and it's a noble effort, but honestly - if anyone has tenants left on 365 that DON'T use MFA then they're being foolish at best and negligent at worst. I strictly require it across the tenants I engage with. So not being able to connect with modern auth is a non-starter unfortunately.
I hope MS stops finger pointing and just finds a way to fix this. Is it really that much of an edge case to want to manage 365 from a Mac these days?

I hear you. I strongly advise my clients to use MFA for all of their user accounts, even if it is not turned on tenancy-wide.
It is frustrating that Microsoft have invested so much effort into making PowerShell work on non-Windows platforms, yet what is likely the most common use case, administering Office 365, Exchange Online and Azure, simply doesn't work out of the box, and can not work with Modern Authentication. So near, yet so far.
I'm sure there may be some other edge cases for using PowerShell on other platforms, and it's an excellent exercise in good coding practice to ensure that a big project like this works on other platforms, but in terms of actually using it, I can't see anyone administering a fleet of Macs, or Linux boxes, with PowerShell. It's here so we can talk to Office 365 and Azure.

@kai-h you shouldn't need to install the older OpenSSL if you use my fork. It's compiled against the newer OpenSSL version (1.1.x) distributed by Homebrew and I've been meaning to see if it will be possible to use the LibreSSL version that comes stock standard. I haven't actually tested it against Big Sur (or M1) but I would assume it would just need to be recompiled and that's it.

Thank you @jborean93, I'll have to give that a go. Why Microsoft can't do this is beyond me.
Do you know if it still searches for the OpenSSL library at a fixed path /usr/local/opt/openssl/lib, or does it use LD_LIBRARY_PATH to find the correct library?

Why Microsoft can't do this is beyond me.

I honestly can't blame them even if I wished the situation was better. The mi library was maintained by a separate team and is based on C so requires a completely different skill set to maintain and support. From experience the code there is quite complex and not something easy to maintain. Once that team dropped support for macOS or PowerShell then the PowerShell team had little choice. What would be nice is if the WSMan code could be implemented in pure .NET and maintained by them as a lot of the fundamental work is already in place in .NET but this is also not a trivial task to achieve. So in the end I decided to just fork the library and fix up the stuff I could. Things that I fixed with this fork

Compiled against OpenSSL 1.1.x on platforms that distribute this version
Fix up GSSAPI library calls on the various platforms

macOS can use Kerberos now, but NTLM only works over HTTPS
Other distributions should allow both Kerberos and NTLM (if the NTLM libs are present)

Can use your implicit Kerberos credential from kinit, no need to use -Credential on your connections if you already have a token
Fix up some of the message encryption bugs so it works on on-prem Exchange hosts over HTTP
Increase the password length limit to support modern auth
Will perform the CA and CN (CN if the version of OpenSSL supports it) verification checks when using HTTPS
Includes a slightly customised libpsrpclient to use an implicit -Authentication Negotiate to act like Windows
People are free to use it but it isn't affiliated with the PowerShell team in any way.

Do you know if it still searches for the OpenSSL library at a fixed path /usr/local/opt/openssl/lib, or does it use LD_LIBRARY_PATH to find the correct library?

Before I continue, all this is relevant only to macOS, for Linux this info does not apply.
It's still hardcoded to<EMAIL_ADDRESS>but it is at least for OpenSSL 1.1 and not 1.0. The main reason why it is hardcoded is because libssl and libcrypto are not in any of the default library paths for macOS /usr/lib, /usr/local/lib, or ~/.lib. When you have a dynamically linked lib with @rpath/lib.dylib on macOS it will search in those default paths or ones specified by LD_LIBRARY_PATH (strong caveats with this env var on macOS). So a user who uses this library and has OpenSSL 1.1.x installed from Homebrew will still fail to load the library leading to a poor user experience. By hardcoding the path to the version installed by Homebrew we can at least have a works out of the box situation as long as the dependencies have been met.
In saying all that, if you really want to rely on the environment or use a different path for your specific setup you can change them yourself. To do this you need to run install_name_tool -change <original path> <new path> <lib.dylib path>. For example here are the paths that my fork is set to by default
/usr/local/microsoft/powershell/7/libmi.dylib:
        /opt/omi/lib/libmi.dylib (compatibility version 0.0.0, current version 0.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1)
        /usr/lib/libpam.2.dylib (compatibility version 3.0.0, current version 3.0.0)
<EMAIL_ADDRESS>(compatibility version 1.1.0, current version 1.1.0)
<EMAIL_ADDRESS>(compatibility version 1.1.0, current version 1.1.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)

If I wanted to change the libssl and libcrypto library to scan from rpath I would run
install_name_tool -change \
<EMAIL_ADDRESS>\
    @rpath/libssl.1.1.dylib \
    /usr/local/microsoft/powershell/7/libmi.dylib

install_name_tool -change \
<EMAIL_ADDRESS>\
    @rpath/libcrypto.1.1.dylib \
    /usr/local/microsoft/powershell/7/libmi.dylib

You would need to run this as sudo and I highly recommend you make a backup of the libraries before you change them in case something breaks. You also want to make sure that the library you are linking to is actually compatible. You won't be able to use install_name_tool to change the libssl.1.0.dylib to use libssl.1.1.dylib as they are not API and ABI compatible.
I've been meaning to look into linking against the builtin LibreSSL libs that macOS ships with but I would be concerned it will start to lag behind just like the shipped OpenSSL version that Apple had before they swapped to LibreSSL. For now relying on a newer version from homebrew gives us a new library that continues to be updated by homebrew which follows what other Linux distributions offer.

Why Microsoft can't do this is beyond me.

This is an obsessive situation for the past few years, but this is a fact, possibly the result of internal political wars. :-)
It seems MSFT PowerShell team has decided to convert Remoting to a subsystem, which will open up the possibility of creating alternative Remoting implementations. If this happens, perhaps we will have time in next milestone to get a new implementation based on .Net WebSockets (?) that will work on all platforms without external dependencies.

Same issue.

So in the end, it's not possible to connect to exchange online via linux powershell if MFA is enable yet, right ?

As far as I know, no - not on a non-Windows platform.

With the one provided with PowerShell there's a good chance it won't work but it really depends on the distribution, i.e. macOS is very likely not to work. With my forked version you definitely can. It's one of the integration scenarios I test out when creating a new release https://github.com/jborean93/omi/blob/67fb46865b76ecd5d89a990fdedeb32cd219143f/libmi.tests.ps1#L470-L518.

@jborean93
So you think this script can be tweaked to connect via lin ?
https://o365reports.com/2019/10/05/connect-all-office-365-services-powershell/

According to this link, it seems like this should in fact be working as of today (unless I am misunderstanding the announcement). I installed the module fresh on MacOS and I'm getting the "no supported WSMan client library was found" error described in OP. Seems like this shouldn't require a workaround or a fork anymore since it's an officially supported scenario.


Servo: possible overlap in metric names during export

See https://github.com/Netflix/servo/issues/322 for a complete description and follow-up.
In short: the current naming scheme used to build metric names from Servo metric doesn't consider the runtime id assigned to the monitor.
The current naming strategy is inspired by Servo's GraphiteExporter - hence linking to the issue in project Servo and waiting for their advices.

Is this still an issue?

Closing for lack of feedback.


Tag associated with Fix for pavlo-v-chernykh/keystore-go library version

Is your feature request related to a problem? Please describe.

This request is related to the following PR: https://github.com/cert-manager/cert-manager/pull/5724. There was an upgrade to pavlo-v-chernykh/keystore-go which has been fixed on both release-1.10 and release-1.11 but there is currently no tag associated with this fix.
Describe the solution you'd like

I would like a tag cut with this latest fix for the library aforementioned.
/kind feature

1.10 is now out of support and 1.11 has had a release since this, so I think this can be closed. Thanks!


[v1.13] - remove tracking of backports with MLH

With the sunset of GH projects by GH [1], we will now create
organization-projects to track which PR is available on which release
after a CHANGELOG of a release is performed. Thus, we can also sunset
this feature from MLH.
[1] https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/
Signed-off-by: André Martins<EMAIL_ADDRESS>

/test-backport-1.13

/test-1.16-4.19


Create an interface to 'add new experiments'

This should provide a GUI front end to the python client. https://github.com/PecanProject/BETYdb-YABA/blob/master/client/client.py#L27
It should accept the fields:

Experiment Name
Start Date
End Date
Description
Design

And should be inserted into the experiments table in BETYdb using the API client

Yes @dlebauer , we can do it with tkinter a python library for GUI.
Can I try to work on that?

hey @dlebauer, I have just created a pull request addressing this issue. Please have a look at it and tell me if some other changes are required.

Thanks @yuvrajdalia - with the new spreadsheet based approach in this will not be required


No function variables show in schema

I just noticed there are no variable names in function output.
I'll look into it, but maybe @NathanRSmith you'd like to fix it in your spare time?

Do you mean field arguments?

http://facebook.github.io/graphql/#sec-Language.Arguments ?

Yes, exactly

I'll take a stab at it

Fields with a lot of args could get unwieldy, but I think this will suffice.

Great :) I've updated changelog and released it. Macroz/GraphQLviz prints field arguments on connections. https://camo.githubusercontent.com/b9c287bfac49bd0997ab7db748af18b7c00e6f66/68747470733a2f2f7261776769742e636f6d2f4d6163726f7a2f4772617068514c76697a2f6d61737465722f6578616d706c65732f646967697472616e7369742e737667

I like the current layout, but we could start having different renderers for different layouts after processing all the entities.

See #2 for multiple layouts.