These three tests fail.

As I mention in my commit message I suggest using https://yaml-online-parser.appspot.com/ to validate the syntax.

I've updated #12 and those cases should work now

Michael,
This test failed:
env:
- A=A
- B=B
command:
- echo A=$A B=$B
# Test that only A or B is not empty
- if [[ "$A" == "" && "$B" == "B" || "$A" == "A" && "$B" == "" ]]; then

echo "OK" ; else echo "ERROR: Unexpected values for A=$A or B=$B"; fi
When I have two spaces after the dash to make it work:

if [[ ....  << fails
if [[ ...  << works

-- Wink
On Tue, Dec 1, 2015 at 1:21 AM Michael Contento<EMAIL_ADDRESS>wrote:

Closed #13 https://github.com/michaelcontento/circleci-matrix/pull/13.
—
Reply to this email directly or view it on GitHub
https://github.com/michaelcontento/circleci-matrix/pull/13#event-478711700
.

Here is the output note the missing "i" in the "if" statement and also the
second env variable "B" has a trailing line feed "\n":
$ ./src/circleci-matrix.sh --config tests-wink/test-env-vars.yml
circleci-matrix version: 0.2.0
circleci node total: 1
circleci node index: 0

Env: A=A
A=A B=
/tmp/circleci_matrix.4g4: line 4: syntax error near unexpected token then' /tmp/circleci_matrix.4g4: line 4: *f [[* "$A" == "" && "$B" == "B" || "$A"
== "A" && "$B" == "" ]]; then echo "OK" ; else echo "ERROR: Unexpected
values for A=$A or B=$B"; fi'

Env: B=B\n    <<<<<<<<<< The Trailing line feed
A= B=B
/tmp/circleci_matrix.ZES: line 5: syntax error near unexpected token then' /tmp/circleci_matrix.ZES: line 5: f [[ "$A" == "" && "$B" == "B" || "$A"
== "A" && "$B" == "" ]]; then echo "OK" ; else echo "ERROR: Unexpected
values for A=$A or B=$B"; fi'
ERROR: 2 command(s) failed
Oh and here
On Tue, Dec 1, 2015 at 8:10 AM Wink Saville<EMAIL_ADDRESS>wrote:

Michael,
This test failed:
env:
- A=A
- B=B
command:
- echo A=$A B=$B
# Test that only A or B is not empty
- if [[ "$A" == "" && "$B" == "B" || "$A" == "A" && "$B" == "" ]];

then echo "OK" ; else echo "ERROR: Unexpected values for A=$A or B=$B"; fi
When I have two spaces after the dash to make it work:

if [[ ....  << fails
if [[ ...  << works

-- Wink
On Tue, Dec 1, 2015 at 1:21 AM Michael Contento<EMAIL_ADDRESS>wrote:

Closed #13 https://github.com/michaelcontento/circleci-matrix/pull/13.
—
Reply to this email directly or view it on GitHub
https://github.com/michaelcontento/circleci-matrix/pull/13#event-478711700
.


How to implement a custom menu for selecting and dragging shapes from there to QGraphicsView for a graphic editor?

``I am trying to implement a graphic editor. As a canvas for drawing, I use QGraphicsScene together with QGraphicsView.
There was a problem with the implementation of the panel, which is essentially a menu of shapes, from where it would be possible to drag shapes to QGraphicsView. It is located outside of QGraphicsView.
I would also like this menu to be divided into several sections so that they can be opened and closed by a button.
Is there an example of implementing this custom shapes menu? Or maybe thoughts with which it can be implemented?
This gif is the example of how I would like it to work (I use drawio as an example):

My code:
`from PyQt5.QtWidgets import *
from PyQt5.QtGui import *
from PyQt5.QtCore import *
import sys
window class
class Window(QMainWindow):
def init(self):
super().init()
    wid = QWidget()
    self.setCentralWidget(wid)

    # setting title
    self.setWindowTitle("Paint with PyQt5")

    # setting geometry to main window
    self.setGeometry(100, 100, 800, 600)

    # Defining a scene rect of 400x200, with it's origin at 0,0.
    # If we don't set this on creation, we can set it later with .setSceneRect
    self.scene = QGraphicsScene(0, 0, 400, 200)

    # Set all items as moveable and selectable.
    for item in self.scene.items():
        item.setFlag(QGraphicsItem.ItemIsMovable)
        item.setFlag(QGraphicsItem.ItemIsSelectable)

    # Define our layout.
    vbox = QVBoxLayout()

    up = QPushButton("Rect")
    up.clicked.connect(self.add_rect)
    vbox.addWidget(up)

    down = QPushButton("Elips")
    down.clicked.connect(self.add_elips)
    vbox.addWidget(down)

    view = QGraphicsView(self.scene)
    view.setRenderHint(QPainter.Antialiasing)

    hbox = QHBoxLayout(self)
    hbox.addLayout(vbox)
    hbox.addWidget(view)

    wid.setLayout(hbox)

def add_rect(self):
    rect = QGraphicsRectItem(0, 0, 200, 50)
    rect.setPos(50, 20)
    rect.setFlag(QGraphicsItem.ItemIsMovable)
    rect.setFlag(QGraphicsItem.ItemIsSelectable)
    self.scene.addItem(rect)

def add_elips(self):
    ellipse = QGraphicsEllipseItem(0, 0, 100, 100)
    ellipse.setPos(75, 30)
    ellipse.setFlag(QGraphicsItem.ItemIsMovable)
    ellipse.setFlag(QGraphicsItem.ItemIsSelectable)
    self.scene.addItem(ellipse)

create pyqt5 app
App = QApplication(sys.argv)
create the instance of our Window
window = Window()
showing the window
window.show()
start the app
sys.exit(App.exec())`

Sorry for the belated answer. I've seen the issue you had brought up, but i've been busy lately.
Well, first things first

Menu of shapes

import sys
from PyQt5.QtWidgets import QApplication, QMainWindow, QGraphicsRectItem, \
    QGraphicsScene, QGraphicsView, QWidget, QGridLayout, QGraphicsEllipseItem, \
    QGraphicsPolygonItem, QGraphicsItem
from PyQt5.QtGui import QPolygonF
from PyQt5.QtCore import Qt, QPointF

class ShapeIcon(QGraphicsView):
    def __init__(self, graphics_item: QGraphicsItem):
        super().__init__()
        self.setScene(QGraphicsScene(self))
        self.setAlignment(Qt.AlignCenter)
        self.scene().addItem(graphics_item)
        self.setStyleSheet('QGraphicsView { border: 0 }')

class ShapeMenu(QWidget):
    def __init__(self):
        super().__init__()
        self.__initVal()
        self.__initUi()

    def __initVal(self):
        self.__rect = QGraphicsRectItem(0, 0, 40, 30)
        self.__ellipse = QGraphicsEllipseItem(0, 0, 40, 30)

        points = [
            QPointF(20, 0),
            QPointF(0, 20),
            QPointF(20, 40),
            QPointF(40, 20),
        ]
        self.__rhombus = QGraphicsPolygonItem(QPolygonF(points))

        points = [
            QPointF(0, 0),
            QPointF(-10, 30),
            QPointF(30, 30),
            QPointF(40, 0),
        ]
        self.__parallelogram = QGraphicsPolygonItem(QPolygonF(points))

    def __initUi(self):
        lay = QGridLayout()
        lay.setSpacing(0)

        shape_lst = [self.__rect,
                    self.__ellipse,
                    self.__rhombus,
                    self.__parallelogram]

        for i in range(len(shape_lst)):
            curShape = shape_lst[i]
            cellWidget = ShapeIcon(curShape)
            lay.addWidget(cellWidget, i // 3, i % 3)

        self.setLayout(lay)

class Window(QMainWindow):
    def __init__(self):
        super().__init__()
        self.__initUi()

    def __initUi(self):
        mainWidget = ShapeMenu()
        mainWidget.setFixedSize(mainWidget.sizeHint())
        self.setCentralWidget(mainWidget)

if __name__ == "__main__":
    app = QApplication(sys.argv)
    window = Window()
    window.show()
    sys.exit(app.exec_())

Result

There's a lot more things to go.

Drag the shape out of the window
Different section of the sidebar menus
Foldable menu

Correct me if i'm wrong
I think that the issues you brought up at my other repositories talk about the same thing. So let's just talk about it in here.
This is kinda challenging so i need to do this, step by step :) Hope you don't mind

This is the repo i've just made by this request
https://github.com/yjg30737/pyqt-grid-item-manager
You can keep track of that as well


[Bug]: Buying airtime with Equity bank  transaction redirects to check balance

Description
When buying airtime with Equity bank, the transaction redirects to check balance and completes with a balance update.
Steps to reproduce

Open the Stax app.
On the home screen click on the buy airtime icon.
On the “pay with” input field, select Equity Bank.
On the “recipient network” input field, select Safaricom.
Select "myself" as recipient
On the “Amount” input field, enter the amount you wish to buy and click continue.
Input your Equity bank PIN.
Observe the transaction.

Expected result
The recipient receives the airtime and sms confirmation. The transaction completes and updates bank balance.
Actual result
The transaction completes with a bank balance update and recipient does not receive airtime or sms confirmation
Link to screenshots/screen recordings
https://drive.google.com/file/d/1186ZP1OsyxqGhL8UsbilCp9W2O4hrbVO/view?usp=sharing
Suggested solution
No response
Device name
Redmi Note 9S
Android OS
11
App version
1.19.6
Config version
20230223000057
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this transaction?
Safaricom
Stax device ID or email address
<EMAIL_ADDRESS>

@jnjerin Can you try the transaction again and let me know the outcome?


Fixing broken link for orbit-db-demo-3.gif

What it says on the tin.

Thank you @ricardojmendez ❤


ci: use Flatcar LTS version in e2e tests

What problem does this PR solve?:
In DKP 2.5 DKP switched to supporting the Flatcar LTS version, switching the TF lookup vars to find the latest LTS version.
Removed source_ami as ami_filter_name takes precedence.
Which issue(s) does this PR fix?:

https://d2iq.atlassian.net/browse/D2IQ-97410

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Linter errors are unrelated and were fixed in https://github.com/mesosphere/konvoy-image-builder/pull/827


Any objection to converting the pretty printer to Reason?

I thought this would be difficult to self-host because of the challenges in building Reason from source, when you don't have an available Reason. But then I realized we can use a simple trick. The OCaml compiler (supposedly) supports loading files that are simply serialized ASTs. (The same output that -pp accepts, and the same output that refmt spits out by default).
So we can simply check in the serialized AST for reason_pprint_ast and friends. Our build scripts for Reason can simply disregard the actual .re files and only ever build the serialized AST files. The result is that it successfully builds a version of Reason that is a binary, even if Reason was not originally installed.

@jordwalke Interesting idea. If we are able to do that, I imagine we can even write parsers in reason as well (need to add a -pp option in Menhir first).

Stale, will keep it in ocaml for now


Allow supplying sources from the command line

Added parsing sources in command line feature #1 and updated command lines in yaml

@msfjarvis I think this will do the job

@msfjarvis your welcome 😁


Historic data for timeseries databases

The miflora poller provides the ability to read history data from our plant sensors. I wonder if it is possible to make use of this feature?
I feed my openhab2, and the data is persisted in an influxDB. It looks that it is not possible to store a different timestamp for a value. So it could be hard to store bulk history data. Maybe some of you know better?
When I used the default poll interval (5 min) the batteries got too low after about 8 to 10 weeks. Now I extended the poll interval to 3 hours, but I still like to see the more detailed data.

The primary use case of this daemon is to provide data to smart home systems. They wouldn't benefit from historic data but I get your point about a direct path into InfluxDB or similar. I am not sure if this is out of scope of the future of this software.

I see a use case also for historic data, as I use it in my openhab frontend.
I built a dashboard to monitor my plants. At the moment I query my sensors every 3 hours, and the resolution of data points is quite low.

It's not an option to have sensor queries more often, as I don't want to change batteries more often.
On the other hand I'm note sure if it would even be possible to add more data than the data we see during a query.

Your arguments are correct.
What I wanted to express: This kind of use case is not directly linked to the function of a smart home system. Of course you can pipe historic data to InfluxDB or any other kind of database or data store and then generate diagrams or insights from it - which is then presented in openHAB - but it's only tangentially relevant to the smart home system with its main task being automation of stuff

To add one more though here: Retrieving historic data from the sensors is not a bad idea but MQTT would be the wrong interface to transfer them to. I saw a fork of this project by someone who then exchanged MQTT by a direct InfluxDB link. That would be the way to go.

I saw a fork of this project by someone who then exchanged MQTT by a direct InfluxDB link.

@ThomDietrich Your project shows 83 forks. Do you have a link to the fork with the InfluxDB change?

Hey @NorbertHD,
maybe @michaelbeljaars can help: https://github.com/ThomDietrich/miflora-mqtt-daemon/issues/120

@NorbertHD I have just uploaded my fork of @ThomDietrich's script (https://github.com/michaelbeljaars/miflora-mqtt-daemon)
It has a section for InfluxDB in the config.ini. With current implementation it is not possible to use both MQTT and InfluxDB (not sure if that is even something you would want).
Additionally, when using Influxdb, the script also calculates and an average temperature for all the valid measurement and sends it to the measurement 'Average' in the database. I use this functionality to get an idea of the mean temperature in my apartment.
I still need to adjust the readme with all details, but be aware that on a RPi there have been problems with the bluetooth adapter. I have recently solved this by installing the latest version of Bluez (5.54) and installing the latest firmware (4.19.118-v7+) (See issue 120)

nice! :) thanks for sharing!

Thank you @michaelbeljaars for sharing!
I looked briefly through your code and it seems not to read the historic data. It reads one current dataset and sends it directly to the influxdb database in a loop. Right?
I have found a project on github that reads the historic data and sends it to an infuxdb database:
https://github.com/sergem155/miflora-influxdb

yes, it doesn't seem to query historic data, but that's a good start to add historic data. The underlying library already supports historic data.

Thank you @michaelbeljaars for sharing!
I looked briefly through your code and it seems not to read the historic data. It reads one current dataset and sends it directly to the influxdb database in a loop. Right?
I have found a project on github that reads the historic data and sends it to an infuxdb database:
https://github.com/sergem155/miflora-influxdb

Did you succeed in getting this to work reliably? I am confronted with many of these errors:
connection and/or query failed - unable to connect?
Also, does anyone know with which frequency the sensors store measurements (i.e. how many per hour)? The implementation of the project above seems to indicate that this is only done once per hour.


Expose configuration in FocusProvider to target colliders instead of rigid bodies

Overview
This PR addresses issue #5391.
Changes
This change introduces a configuration property in the Input System Settings in MRTK profiles - "FocusIndividualCompoundCollider". This configurable property is passed as a argument to the Raycast provider implementation and ultimately propagates to the TryGetPrioritizedPhysicsHit logic to determines, if the raycast hit result should pick individual colliders or the root rigidbody transform.
When the hit is determined, the profile property is again used to determine which gameobject to set as the rayast hit object .

Verification
Validation requested from @anuraag016  via product integration.
Created a local scene with a rigidbody and compound colliders and verified that the correct item is focused.
FocusIndividualCompoundCollider = false;

FocusIndividualCompoundCollider = true

;

@anuraag016, @naostranMS, @davidkline-ms - FYI

@wiwei, @keveleigh,
this has some API and profile changes. if we are going to take if for dev, we should strongly consider it for the stabilization branch. thoughts?

I really like the idea of this feature. I think developers would appreciate the greater power and there has been some feedback to for them to better control what gets focus, etc. Few problems I see though

FocusIndividualCompoundCollider is a mouthful and for most people doesn't really inform them of what it is
There is no documentation with this change to teach people or tests to verify correct functionality
The global value isn't really catch all. Basically could we think of a better approach that would allow hit.collider.gameobject and hit.transform.gameobject results? I could see developers wanting one in some scenarios of their app and the other for separate parts
I don't see any way to alter this behavior at runtime. It's set in the profile but I can't modify the FocusProvider functionality directly after instantiation
Also I feel like MixedRealityRaycaster.Raycast* functions may need a refactor in general. Especially MixedRealityRaycaster.RaycastBoxPhysicsStep is just insanely long in the parameter list

Adding this to the must fix for GA as it is both an interface API and profile breaking change.
@ritijain, can you please retarget this change to prerelease.2.0.0_stabilization in the next day so that we can test and validate?
thanks!

Adding this to the must fix for GA as it is both an interface API and profile breaking change.
@ritijain, can you please retarget this change to prerelease.2.0.0_stabilization in the next day so that we can test and validate?
thanks!

@davidkline-ms  - retargeted to pre-release. Validation pending.

this looks like it should work for #5391

/azp run

Change looks good - I can approve once Adam's nits get addressed
Yes, targetting at stabilization is good because this isn't something we want folks to absorb in a future release.

Change looks good - I can approve once Adam's nits get addressed
Yes, targetting at stabilization is good because this isn't something we want folks to absorb in a future release.

@wiwei - PR updated.

/azp run


Clarification Request:  How to get DLRS to work in Professional Edition Org?

Describe the bug
Per the Readme and the Wiki (and this blog post which is linked from the Readme), DLRS can be used in a Professional Edition org by:

Setting the Calculation Mode of a Rollup to "Process Builder"
Calling the apex action dlrs__RollupActionCalculate from a PB on the child object.

However, the option to call apex from a PB appears to be missing in Professional Edition; see screenshot below.  This issue was raised in #341 and #478.  Both issues are closed, but I do not see a definitive resolution in either ticket, aside from a suggestion to try scheduled calculation.
Can you clarify?

Is it possible to use DLRS in Profession Edition via Process Builder (not scheduled calc)?
If so, how is this accomplished?
If not, can the documentation make this clear?

To Reproduce
Steps to reproduce the behavior:

Install DLRS in a Professional Edition org
Create a rollup, set calc mode to "Process Builder"
Try to trigger the rollup from a process builder.  Fail to find option to call apex code from PB.

Expected behavior
It should be possible to configure DLRS to run in a PE org when a record is inserted or updated (vs via scheduled calc).
Screenshots

Hey @jclark-dot-org
I'm stuck at the same stage. Did you manage to do a scheduled calc at least? Can you clarify what these steps are?
Cheers

I tried reading most of the documentation but i was also not able to get this working on a professional edition environment. I mean there are options to run apex from managed packages in professional edition, but the way described here using process builder is not working for me as well.

That may not be available in PE orgs anymore it seems.  Can someone check if you can invoke apex from an After Save Flow? or Before Delete flow in PE?   Process Builder won't recalculate when a record is deleted unfortunately so I'd like to update the wiki to promote Flows instead.


is a Magician essentially the same as MultiZarrToZarr ?

As pointed out by @martindurant at this comment, (some of) the functionality of the Magician workflow might be possible to implement using MultiZarrToZarr.
We might want to investigate this and try to simplify code if possible.

@martindurant, is there a possibility to concatenate some variables along one set of coordinates and other variables along a different set of coordinates?
Say each grib message has one dimension values of size 10. Then there are variables a and b.

a has 5 messages and should be concatenated along time and
b has 15 messages and should be concatenated along time and level.

The resulting Dataset would have dims: {"time": 5, "level": 3, "values": 10}, but variable a would only be defined on dimensions (time, values), whereas b would be defined on (time, level, values) ?
I've seen identical_dims but identical_dims=["a"] would remove time and level from a...

I am not immediately sure if you'll succeed doing the different variables in the same go. I feel it should be possible, if the individual variables already declare which coordinates they depend on; but there is no test case this complicated.


Improve aria-labels for non initial letters

Add a "word X, letter Y of Z".

Also add the same to the initial letters, on top of also reading the definition.


Errors on boot VMI using Cirros container disk image

/kind bug
There is a bug with Cirros container-disk causing a 5 minutes delay on boot.
The workaround for it is using cloud-init with any arbitrary userData just to trigger cloud-init make the VMI boot normally.
Cirros container-disk is extensively used all around tests suite, enforces using that workaround making the code look awkward.
Creating cirros VMI and console to it during boot shows that there is a process that tries to connect to http://<IP_ADDRESS>/2009-04-04/instance-id before the system is ready:
https://paste.centos.org/view/3bc17091 (line 414)
That address is not available causing the process to repeat itself 20 times reaching to about 5 minutes delay.
The workaround of using cloudInit disk skips the described process (I am not sure why)
https://github.com/kubevirt/kubevirt/blob/master/tests/container_disk_test.go#L110
What happened:
Using cirros VMI's in tests suite will time out unless using cloudInit disk with any userData.
What you expected to happen:
Use cirros container-disk w/o workaround
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

The address is the default cloud-init server which is used to fetch the configuration instead of the mounted option.
On cloud that is the preferred option as it is centralizing the configuration management.
We could hide in the libvmi this workaround and use this option as the default for cirros.

The address is the default cloud-init server which is used to fetch the configuration instead of the mounted option.
On cloud that is the preferred option as it is centralizing the configuration management.
We could hide in the libvmi this workaround and use this option as the default for cirros.

https://github.com/kubevirt/kubevirt/pull/4035/commits/886fd42d7b0e80f42c2b57df747850599637cc1b#diff-310823e407ba19baac5e5e3ee718b6bbR56 would address what you're proposing, iiuc.
I'll watch this issue, closing it if/when the aforementioned PR gets merged.

886fd42#diff-310823e407ba19baac5e5e3ee718b6bbR56 would address what you're proposing, iiuc.

Actually we can use an empty cloud-init config just to trigger cloud-init no cloud to work inside the VM.
A proper solution would be editing the image with
echo 'DATASOURCE_LIST=\"nocloud\"' > /etc/cirros-init/config
this will skip that check on boot
https://serverfault.com/questions/646326/how-do-i-disable-the-metadata-lookup-at-cirros-boot

@ormergi , the workaround that @maiqueb mentioned is in place (you can change it to an empty script if it works, just send a PR).
I think that works and solves the issue raised here without asking to test user to know about it (embedded in the factory).
Can this issue be closed now?

@ormergi , the workaround that @maiqueb mentioned is in place (you can change it to an empty script if it works, just send a PR).
I think that works and solves the issue raised here without asking to test user to know about it (embedded in the factory).
Can this issue be closed now?

I think so; I don't think baking another set of images for cirros deserves the time it takes.
@ormergi , please close the issue if you're OK with the answer.

/close
This workaround is good enough for now, thanks.


Message with both icon and compact props does not become compact

Steps

Go to https://react.semantic-ui.com/collections/message#message-example-icon-prop
Give the Icon Message example a compact prop

Expected Result
The Message should become compact, like non-icon Message components
Actual Result
The Message stays fluid.
Version
0.75.1
Testcase
https://react.semantic-ui.com/collections/message#message-example-icon-prop
Add a compact prop and remove/add the icon prop to see how this affects the compact styling

Hi @hanshenrik, thanks for the report. Checking the markup that is generated, all of the correct class names are present for that combination of props ui compact icon message. This is actually an issue in the CSS, specifically because the icon message type is switching to display: flex in order to achieve that layout. You will see the same thing if you modify the markup in SUI core docs here: https://semantic-ui.com/collections/message.html#icon-message
I'd encourage you to open a CSS issue on the SUI core repository for this: https://github.com/Semantic-Org/Semantic-UI/issues

Thanks for the quick response.
The issue is addressed here: https://github.com/Semantic-Org/Semantic-UI/issues/4759

Fixed. See http://jsfiddle.net/95kzk6mr/2/


Resolve syncing conflicts from from-prod-live to live

Pull request opened by OPS to resolve syncing conflicts from from-prod-live to live.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\fbqo-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\k4mp-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\jfkm-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\hcoa-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\dcbk-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\l2rp-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\afuh-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\oc3d-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\f4hm-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\li3b-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\xiaz-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\izmp-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\p3ee-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\gtzl-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\3w03-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\mmrl-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\x2f3-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\hk2v-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\2gw0-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\a5sd-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\rrlm-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\tjrh-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

README.md
:white_check_mark:Succeeded

azuredmps-0.9.0/AzureRM.DeploymentManager/AzureRM.DeploymentManager.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerArtifactSource.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerRollout.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerService.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerServiceTopology.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerServiceUnit.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerStep.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/New-AzureRmDeploymentManagerArtifactSource.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/New-AzureRmDeploymentManagerService.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/New-AzureRmDeploymentManagerServiceTopology.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/New-AzureRmDeploymentManagerServiceUnit.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/New-AzureRmDeploymentManagerStep.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Remove-AzureRmDeploymentManagerArtifactSource.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Remove-AzureRmDeploymentManagerRollout.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Remove-AzureRmDeploymentManagerService.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Remove-AzureRmDeploymentManagerServiceTopology.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Remove-AzureRmDeploymentManagerServiceUnit.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Remove-AzureRmDeploymentManagerStep.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Restart-AzureRmDeploymentManagerRollout.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Set-AzureRmDeploymentManagerArtifactSource.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Set-AzureRmDeploymentManagerService.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Set-AzureRmDeploymentManagerServiceTopology.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Set-AzureRmDeploymentManagerServiceUnit.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Set-AzureRmDeploymentManagerStep.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azuredmps-0.9.0/AzureRM.DeploymentManager/Stop-AzureRmDeploymentManagerRollout.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

azurermps-2.3.0/Azure.Storage/Azure.Storage.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageBlob.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageBlobContent.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageBlobCopyState.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageCORSRule.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageContainer.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageContainerStoredAccessPolicy.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageFile.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageFileContent.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageFileCopyState.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageQueue.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageQueueStoredAccessPolicy.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageServiceLoggingProperty.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageServiceMetricsProperty.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageServiceProperty.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageShare.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageShareStoredAccessPolicy.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageTable.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/Get-AzureStorageTableStoredAccessPolicy.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/New-AzureStorageAccountSASToken.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/New-AzureStorageBlobSASToken.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

azurermps-2.3.0/Azure.Storage/New-AzureStorageContainer.md
:white_check_mark:Succeeded
View (azurermps-2.3.0)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\w0a2-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\huvy-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\w0ur-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\zmow-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/azure-docs-powershell, working directory: W:\kctm-s, target branch: live, target branch commit: 30335bf315f98958e5b7f2199ecd4ad27533db36, source branch: from-prod-live, source branch commit: .
Learn more: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Using tsec for authentication

An attempt to add JWT authentication, in essence what I am doing is following blindly example from:

https://jmcardon.github.io/tsec/docs/http4s/auth-jwt.html
https://gitter.im/tsecc/Lobby?at=5b83999c60f9ee7aa4986b61

Things I am not sure of:

Is it true that I need to use UserService as identity backingStorage for JWTAuthenticator?
Whether or not I need the token store as done now in AuthenticationService I introduced, this is blind example following.

I added dummy secure GET end point in user endpoints, to give an example how an endpoint requiring authentication looks like, but I did not touch the rest of the endpoint, with some test on how it behave when user accessed it with proper headers after logging (auth case) and when it does not provide required Auth headers.
I have no idea how to update functional tests since I can't really parse the python code :)

Somehow @zakpatterson's PR makes more sense :D I am on the verge of closing and forgetting about this.

Thanks @wibisono , I don't have a ton of experience on the auth side so admittedly this is one for experimentation.
I think the end state would be:

Support dual means of authentication (oauth2 and jwt)
A scala js application could use jwt / secure cookies to interact with the backend from a web application
Clients could directly access the backend using OAUTH2 (or similar).

Http4s does support multiple auth mechanisms.
tbf, I haven't revisited this in a while.  I know TSEC was under active development a while back and was changing too frequently for me to keep up with.
I also haven't dug into the scalajs app.  #93 exists as a starting point for a scala js application.  I would prefer to have everything in the same project.

I might see if @jmcardon or @rossabaker are around (may not be)

I think @jmcardon was trying to give tsec away. There are still PRs as recent as a day old, so there is still interest. Does it have a maintainer?

👋  @rossabaker , not sure about tsec.
Am curious if you had guidance / thoughts on ScalaJS + JWT combined with OATH2 for non UI authentication on http4s.  I would really like to make that happen, but haven't had a ton of time recently.

Let me ask on the http4s channel. I've (dirty secret) never done auth on http4s.

@rossabaker not giving it away, just considering archival until I could maintain it again. I found maintainers, so it's not going anywhere.
@paulcleary im not really supporting scalajs atm... So that may be an issue.

w.r.t tsec:

It is a lot more stable now, since 0.0.1-RC1 is out, no major changes will be made. Same wiht 0.1 of tsec.
OAuth support is really young but promising.
I'm not entirely out of the picture but my time is quite limited, so apologies if I cannot get to this for a while. I hope that with the more stable tsec, we've put out enough tools to be able to implement most things, if, at worst, from tsec-derived primitives.

Thanks @rossabaker and @jmcardon for chiming in!
I would love to put together a plan for this "major final piece" for the pet store.  Having a scalajs front end (maybe using Outwatch?), with secure cookie / JWT for authentication, as well as a direct REST api authentication would be the bees knees.
A lot of people have the problem (including myself) of needing both a UI as well as a REST api to be consumable by clients.
Any guidance, or people / resources I can check out for building this into the pet store would be much appreciated.

Also, found this with some googling might give some guidance? - https://github.com/eugengarkusha/http4s-scalajs

Also, found this with some googling might give some guidance? - https://github.com/eugengarkusha/http4s-scalajs

Scalajs is still foreign to me also, so I guess we'll wait for other scalajs native volunteer to do this :)

@wibisono me too.  We have some folks over here doing some stuff with it.  @RobertLemmons also has a PR up to start that effort.


Update composer.json

Developer(s): @alex-galych

Please confirm

[ ] No new OS components - or they have been approved by legal department

Documentation

[ ] Functional documentation provided or in progress?
[ ] Integration guide for projects provided or not needed?
[ ] Migration guides for all contained majors provided or not needed?

Release Table

Module
Release Type
Constraint Updates

Ratepay
patch

Release Notes
{skip}

Module Ratepay
Change log
Bugfixes

Increased spryker/oms version dependency to "^11.0.0".
Increased spryker/payment version dependency to "^5.0.0".
Increased spryker/sales version dependency to "^11.0.0".

Increased spryker/oms version dependency to "^11.0.0".

Please use the wording "allowed new"
since you dont increase, you only add a new version compatibility instead of dropping the others.

Always remove merged branches please.


⚠ 广电VRBT has degraded performance

In ccb437b, 广电VRBT (https://vrbt.10099.com.cn/#/home) experienced degraded performance:

HTTP code: 502
Response time: 8156 ms

Resolved: 广电VRBT performance has improved in f7ac823.


Dispatch error when using Vulkan backend on Intel integrated graphics

python taichi_ngp.py
[Taichi] version 1.4.1, llvm 15.0.1, commit e67c674e, win, python 3.9.13
[W 02/25/23 12:58:49.450 4244] [cuda_driver.cpp:taichi::lang::CUDADriverBase::load_lib@36] nvcuda.dll lib not found.
[Taichi] Starting on arch=vulkan
Loading model from ./npy_models/lego.npy
[E 02/25/23 12:58:49.785 4244] [runtime.cpp:taichi::lang::gfx::GfxRuntime::launch_kernel@519] Dispatch error : RhiResult(-3)

Traceback (most recent call last):
  File "C:\taichi\taichi-ngp-renderer\taichi_ngp.py", line 1177, in <module>
    main(args)
  File "C:\taichi\taichi-ngp-renderer\taichi_ngp.py", line 1147, in main
    ngp.load_model(npy_file)
  File "C:\taichi\taichi-ngp-renderer\taichi_ngp.py", line 358, in load_model
    self.hash_embedding.from_numpy(np_hash)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\util.py", line 310, in wrapped
    return func(*args, **kwargs)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\field.py", line 357, in from_numpy
    self._from_external_arr(arr)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\util.py", line 310, in wrapped
    return func(*args, **kwargs)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\field.py", line 347, in _from_external_arr
    ext_arr_to_tensor(arr, self)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\kernel_impl.py", line 974, in wrapped
    return primal(*args, **kwargs)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\kernel_impl.py", line 901, in __call__
    return self.runtime.compiled_functions[key](*args)
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\kernel_impl.py", line 826, in func__
    raise e from None
  File "C:\ProgramData\Anaconda3\lib\site-packages\taichi\lang\kernel_impl.py", line 823, in func__
    t_kernel(launch_ctx)
RuntimeError: [runtime.cpp:taichi::lang::gfx::GfxRuntime::launch_kernel@519] Dispatch error : RhiResult(-3)

GPU device properties from vulkaninfo:
Device Properties and Extensions:
=================================
GPU0:
VkPhysicalDeviceProperties:
---------------------------
        apiVersion        = 4206814 (1.3.222)
        driverVersion     = 1658142 (0x194d1e)
        vendorID          = 0x8086
        deviceID          = 0x46a8
        deviceType        = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
        deviceName        = Intel(R) Iris(R) Xe Graphics
        pipelineCacheUUID = 2c3f2a36-2b35-1837-273a-243423302101

Hi~ @victoriacity
I don't have an intel integrated GPU to test this issue, but according to the log messages, the error appears when from_numpy is called.
Could you write another script to test from_numpy? So we can make sure this is not a Taichi issue

I am having the same problem with Vulkan backend + AMD cards. The problem persists after isolating the hash embedding loading code from the rest of the script. It might be a Taichi problem.


Address field on Politicians page keeps resetting

Closed until we can reproduce

@travisbloom-cb @jimobrien-cb not sure if this is context for the original ticket but when unauthenticated on the /politicians page, I see the following:

Type in address to find rep
Click anywhere else on the page (or even on a politician in the table) and the address is reset

@axelmarko-cb closing. Lmk if you can reproduce.


$errors->has() returns true since framework upgrade to 5.2.40

Hi All,
Since i upgraded my L5 version from 5.2.35 to 5.2.40, the function to check if i have errors in my view doesn't work anymore. $errors->has() now returns true instead of false, if i change this to $errors->any() it returns false.
@if ($errors->has())

    @foreach ($errors->all() as $error)

{{ $error }}

    @endforeach

 @endif

Any ideas?
thx

It seems as though you aren't actually checking for a particular error. For example -  $errors->has('name')

https://laracasts.com/discuss/channels/laravel/errors-has-returns-true-since-framework-upgrade


Look at re-deprecating Session::recursivelyApply()

Session::recurisivelyApply() is currently deprecated
I've undeprecated it as part of this issue because the recommended migration to Session::recursivelyApplyChanges() has a different API
I've split off this card to look at re-deprecating this separately after the bulk of the deprecation changes have been made.
Acceptance criteria

Code pointing to Session::recurisivelyApply() is updated to use Session::recursivelyApplyChanges()
Session::recurisivelyApply() is deprecated

Notes

Because this is low priority, this doesn't have to happen in time for 5.0.0

Didn't make the cut for CMS5


Added range index support for queryable encryption

Note: The Range algorithm is experimental only.
It is not intended for public use.
It is subject to breaking changes.
JAVA-4625

Any idea what's causing the CI failures?

Thankfully, the build is much happier - rerunning the one task that failed.


Headers from S3 not mantained when requesting assets from CMS

Hello,
I'm using this plugin with the s3 adapter, and I noticed that when an asset is requested from the CMS, all the headers normally returned from S3 are stripped, for example when requesting a video file, we don't get the "Content-Type", "Accept-Ranges" etc. headers that are instead present when requesting the same asset directly from AWS.
I can easily avoid this problem by requesting the assets using the S3 url directly, but I wanted to be sure that is the expected behaviour and I'm not missing anything.

Hi @jmikrut, just added a PR https://github.com/payloadcms/plugin-cloud-storage/pull/21.
As I wrote on the PR description, I've added the header to S3 and Azure, but I couldn't find the header on GCS metadata object, it seems that is not returned at all, so I am not sure if we should handle it somehow or just skip it.

Hey @AlexPagnotta — this was just merged. Again, thank you for the PR and your patience!


warnings building Tensorflow 1.7 from source

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
no, just tensorflow 1.7.0
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
TensorFlow installed from (source or binary):
installed from source
TensorFlow version (use command below):
1.7.0
Python version:
3.6.5 (Anaconda)
Bazel version (if compiling from source):
0.11.1
GCC/Compiler version (if compiling from source):
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
CUDA/cuDNN version:
9.1 / 7.1.2
GPU model and memory:
GeForce GTX 980, 4GB
Exact command to reproduce:

source activate python36
./configure

Please specify the location of python. [Default is /home/hunterwolf/anaconda3/envs/python36/bin/python]:

Found possible Python library paths:
  /home/hunterwolf/anaconda3/envs/python36/lib/python3.6/site-packages
Please input the desired Python library path to use.  Default is [/home/hunterwolf/anaconda3/envs/python36/lib/python3.6/site-packages]

Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.

Please specify the CUDA SDK version you want to use, e.g. 7.0. [Leave empty to default to CUDA 9.0]: 9.1

Please specify the location where CUDA 9.1 toolkit is installed. Refer to README.md for more details. [Default is /usr/local/cuda]: /usr/local/cuda-9.1

Please specify the cuDNN version you want to use. [Leave empty to default to cuDNN 7.0]: 7.1.2

Please specify the location where cuDNN 7 library is installed. Refer to README.md for more details. [Default is /usr/local/cuda-9.1]:

Please specify a list of comma-separated Cuda compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus.
Please note that each additional compute capability significantly increases your build time and binary size. [Default is: 5.2]5.2

Please specify which gcc should be used by nvcc as the host compiler. [Default is /usr/bin/gcc]:

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native]:

bazel build --config=opt --config=cuda //tensorflow/tools/pip_package:build_pip_package

Describe the problem
following https://www.tensorflow.org/install/install_sources gide, I get a lot of warnings while building Tensorflow 1.7 from source. the process is completed anyway and the whl file created.
Source code / logs
WARNING:
/home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/protobuf_archive/WORKSPACE:1: Workspace name in /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/protobuf_archive/WORKSPACE (@com_google_protobuf) does not match the name given in the repository's definition (@protobuf_archive); this will cause a build error in future versions
WARNING: /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/WORKSPACE:1: Workspace name in /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/WORKSPACE (@com_github_grpc_grpc) does not match the name given in the repository's definition (@grpc); this will cause a build error in future versions
WARNING: /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/BUILD:1943:1: in srcs attribute of cc_library rule @grpc//:grpc_nanopb: please do not import '@grpc//third_party/nanopb:pb_common.c' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'grpc_generate_one_off_targets', the error might have been caused by the macro implementation in /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/bazel/grpc_build_system.bzl:172:12
WARNING: /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/BUILD:1943:1: in srcs attribute of cc_library rule @grpc//:grpc_nanopb: please do not import '@grpc//third_party/nanopb:pb_decode.c' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'grpc_generate_one_off_targets', the error might have been caused by the macro implementation in /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/bazel/grpc_build_system.bzl:172:12
WARNING: /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/BUILD:1943:1: in srcs attribute of cc_library rule @grpc//:grpc_nanopb: please do not import '@grpc//third_party/nanopb:pb_encode.c' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'grpc_generate_one_off_targets', the error might have been caused by the macro implementation in /home/hunterwolf/.cache/bazel/_bazel_hunterwolf/52c81ed9b047b1a3afd28a55294d981e/external/grpc/bazel/grpc_build_system.bzl:172:12
WARNING: /home/hunterwolf/tensorflow/tensorflow/contrib/learn/BUILD:17:1: in py_library rule //tensorflow/contrib/learn:learn: target '//tensorflow/contrib/learn:learn' depends on deprecated target '//tensorflow/contrib/session_bundle:exporter': No longer supported. Switch to SavedModel immediately.
WARNING: /home/hunterwolf/tensorflow/tensorflow/contrib/learn/BUILD:17:1: in py_library rule //tensorflow/contrib/learn:learn: target '//tensorflow/contrib/learn:learn' depends on deprecated target '//tensorflow/contrib/session_bundle:gc': No longer supported. Switch to SavedModel immediately.

What (eventually) I'm doing wrong?
First time building Tensorflow from code and first time using Bazel, sorry for the noob question :)

@Hunterwolf88  The options I can think of to address these warnings:

Make sure your version is the latest master 1.7.0.
Following the Bazel install guide: https://docs.bazel.build/versions/master/install-ubuntu.html
Make Bazel point at com_google_protobuf by default for cc/java_proto_library rules.
Please make sure these three options.

Nagging Assignee @tatianashp: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

thanks @jyu25utk I somehow did something wrong in step 3


Auto-close after space doesn't work on Android

On pressing space, autoclosing doesn't seem to work on Android on any keyboard. It seems this is an Android specific issue with detecting space keypresses as changing the code to, for example, key:';' instead of key:'Space' seems to fix the issue. Although it would be great for this to work properly.

Hi!
I am sorry, but this plugin does not work on mobile in general right now. It was a little beyond my knowledge. If there are any friends out there familiar with how codemirror works on android or any other mobile platform, please feel free to fork this repo and share with everyone :)

Having this work on android would be very useful to me. Hopefully someone who has a good understanding of android will come by and make this feature work. It seems like the issue may only need a minor change, judging by the fact other autocomplete keypresses work.


Adds givenCode to BDDAssumptions.

Adds givenCode to BDDAssumptions.
Improves BDDAssumptions documentation.
Check List:

Fixes #1636
Unit tests : YES
Javadoc with a code example (on API only) : YES

Integrated thanks @gmullerb! The only chang I made was to remove given(ThrowingCallable lambda) to only keep givenCode(ThrowingCallable lambda) as in Assumptions where there is no assumeThat(ThrowingCallable lambda)

My Pleasure!


switch README.md to WMF's class="wikiglyph wikiglyph-pencil" CSS

The example in README.md is
<i class="WikiFont-puzzle"></i> ...
but that doesn't match WMF's CSS naming class="wikiglyph wikiglyph-puzzle" or the practices recommended in https://www.mediawiki.org/wiki/Design/WikiFont#Using_WikiFont

Fixed!


Spatial awareness implementation

Overview
This PR introduces a functioning spatial awareness system (minus the ability to move the observer origin #2916).
This change provides an implementation for spatial meshes ONLY. Planar surface finding will come in a future PR.
Changes

Fixes: #1998.
Fixes: #2386.
Fixes: #2508.

Adding DNM while I fix a bug found by @keveleigh. I will also update the demo scene to move the observer with the user (#2916) as it will help prove the fix

bugs fixed, added isStationaryObserver, updated demo scene.  ready to review

if #2922 goes in first, this PR will need to be updated to the new namespace / toolkit component names

This isn't targeting the dev branch, so when that merge takes place it can be handled then.

Nope, just need to get time to review for you :)

looks like the status checker is working.... slowly


[Linux] call projfs directly, don't use intermediary projfs_vfsapi

👋  We've been developing libprojfs as a library which offers its own notifications and callbacks, and then built a VFS API on top of that which connects libprojfs to a .NET provider. The VFS API exports the PrjFS_* symbols used by PrjFSLib.Linux.Managed.
Right now, the VFS API lives in the same tree as libprojfs -- see projfs_vfsapi.h as of time of writing to see what it exposes.
We want to reduce the coupling of libprojfs to VFS for Git. I had first thought to simply pull the VFS API code into this repo and have a separate build step (with two .sos), but that's quite a lot of overhead for a thin wrapper. See https://github.com/github/libprojfs/issues/48 where I spike that out and @chrisd8088 lays out the land.
We resolved to try option #3. This PR retargets PrjFSLib.Linux.Managed -- it now consumes libprojfs directly. This removes a layer of callbacks and forwarding, simplifying the mental model significantly.
There's probably a whole bunch of style issues to be addressed here. (At the very least it's StyleCop clean.) Likewise, ProjFS.Linux/Scripts/GenerateConstants.sh is pretty hacky, but does only need to be run when projfs_notify.h changes.
There's a companion libprojfs PR at https://github.com/github/libprojfs/pull/53 which exposes a required entrypoint.

This PR has been rebased (as of the reset in #818).

Hi @jrbriggs -- would you be able to take a look at this PR in the next few days?
Getting this into features/linuxprototype would help us move along a bit.
One thing I suspect you'll flag is the use of some Mono classes.  If you would prefer to avoid any dependency on Mono, maybe we can look into using the NativeMethods technique I found in MacFileBasedLock.cs.
Let me know what you think and if you see any other issues in this PR.  Thanks very much, and have a great weekend!

@chrisd8088 I would prefer to avoid the mono dependency in the mac codebase, and since we're trying to fold linux and mac together in the POSIX layer, can we try pinvoking?
Thanks!
/cc @kivikakk

Hi @jrbriggs and @wilbaker!
I'm hoping you can take a look at this PR again and whether we could get it merged into features/linuxprototype, as that would help us simplify the number of outstanding interdependent branches we have on the go.  :-)
While I have removed the use of Mono in ProjFS.Linux itself, and also tuned up the original ProjFS.Linux/Scripts/GenerateConstants.sh in conjunction with that, you may notice that there's still a dependency on Mono in MirrorProvider -- but that already exists prior to this PR in the features/linuxprototype branch, so we're not adding Mono anywhere in this PR now beyond what's already in place (i.e., in the Linux MirrorProvider).

Now I did also manage to fully remove Mono from the MirrorProvider.Linux; see my vfs-api-nomono-wip branch for an initial version of that work.  However, this comes with significant caveats, so I don't want it to block this PR.  It was worth thinking about, though, because it relates to the issues with stat(2) calls which @kivikakk had, and will absolutely crop up again as we look at migrating the GVFS code proper, particularly the use of a call to stat(2) in GVFS.Platform.Mac/MacFileSystem.cs, and also pertains to @jrbriggs's question about native calls.
A. Issues with the stat(2) family
The immediate challenge (and again, this doesn't apply to this PR per se, but looking ahead a bit) is that GNU libc doesn't provide the stat(2) family of calls in its dynamic libc.so, because it's working around the many historical and architecture-dependent variations on the layout of fields in struct stat.  Instead, there's a small static libc_nonshared.a library with those calls, which are wrappers around the __xstat() functions in the dynamic library, and unfortunately the .NET runtime can't use that static library, so it can't P/Invoke things like lstat(2) directly.
Because the __xstat() workarounds are part of the Linux Standard Base spec, at least some alternate libc implementations like musl include it, but I don't think that's true for uClibc-ng, for instance.  Even if we assume the use of GNU libc or an ABI-compatible libc, we face the issue of variant struct stat layouts; my experimental WIP branch uses the one for x86-64 but there are others depending on the system architecture.
The Mono system gets around this by not trying to P/Invoke directly into libc; instead it builds a
libMonoPosixHelper.so library which wraps the various stat(2) syscalls and maps their stat structures to a standard C# structure.  I strongly suspect we will have to do something similar for Linux (if we're not using Mono itself), while you can probably stick with a hard-coded mapping on macOS where your system architecture is more nailed down.
B. Handling Unix filenames and UTF-8
The other thing Mono provides is a more comprehensive solution to the business of handling Unix filenames via its UnixEncoding and custom FileNameMarshaler, which is used to translate C# strings when passing filenames to something like open(2).  This is in contrast to the way it's done in GVFS.Platform.Mac/MacFileSystem.cs which relies, I believe, on the default CharSet.Ansi transform done by .NET.
That may work on macOS (although I'm not totally sure about that), but on Linux I suspect, even if we make the assumption that filenames are almost always encoded in UTF-8 (not an absolute given, alas), doing UTF-8 conversions inline (as I'm doing now in my vfs-api-nomono-wip test branch with a small GetBytesUTF8() helper) will get ugly fast.
So I think we may want to borrow some of the Mono code from UnixMarshal  and UnixEncoding, as called from FileNameMarshaler, at least enough to -- as they say in the UnixEncoding FAQ -- be able to simply pass and receive strings with file paths to our P/Invoke syscall wrappers and let the custom marshaler figure out the UTF-8 (or other) conversion from string to char* and back.  Then our DllImports could be similar to theirs for syscalls like open(2) and readlink(2), etc., and our invocations of them would be clean too.  (Note that MPH in their code refers to their libMonoPosixHelper.so library, which as I said above, wraps things like the arch-and-libc-specific stat(2) calls.)
I believe Mono is licensed under the MIT license, so hopefully we could just pull some of that code into VFSForGit if you're keen not to have an outright dependency on a pre-built Mono package.

Whew.  OK, so, this PR doesn't actually get deeply involved in any of those musings; that's all for the (near) future.  What this PR does do is implement @kivikakk's work to call our "native" libprojfs API, and avoid using Mono in the ProjFS.Linux code itself, although it retains such a dependency in MirrorProvider.Linux for at least the time being.  Please do take a look over it and let me know if anything else needs a fixup before it could be merged in features/linuxprototype.  And thanks very much for all the help!
/cc @kivikakk, @wrighty

Oh, and I should add, @jrbriggs, that the CI test failure is (I'm virtually certain) unrelated to this PR.  I've bumped into this transient CI failure last week, and it went away when the failing test ran a second time.  So I think it must be a bug in the CI tests which was introduced recently.
The specific error message is:
Failed : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.PrefetchVerbTests.PrefetchCleansUpPackDir()
  C:\Repos\GVFSFunctionalTests\enlistment\..\.gvfsCache is expected to have only one folder. Actual folders: C:\Repos\GVFSFunctionalTests\.gvfsCache\5aa3c69dc0ac42d39714896f33f37ff0,C:\Repos\GVFSFunctionalTests\.gvfsCache\97dc78053d8f4e79aeb15ed21a4a08db

and at a wild guess I'm wondering if it has something to do with the changes from #941?  Anyway, I'm pretty certain it's nothing to do with the Linux work.  :-)

@chrisd8088 This is merged, if you want to rebase up. Thanks!

Thank you!  And I'll rebase soon; that would be great as it sounds like it'll fix the CI issue.
Much appreciated!