mcep

Why does the dimension increase after mcep is output from the network? What is the added dimension?

I am not sure if I understand your question. But I you check the paper, they used 1D-CNN to process the 2D spectrum, the second dimension becomes 1 and the third dimension becomes the second dimension in the 2D spectrum, if my memory is correct.

No follow-up response. Close the thread.


Add packages as submodules

This PR does a couple things:

Merges the docs directly into the sdk - this will require re-configuring the readthedocs

Serves as an alternative to https://github.com/dwavesystems/docs/pull/62

Adds the dependencies of the sdk as submodules - this requires pinning the version in the sdk

Other considerations:

To get all of the docs together, this will require adding projects into the sdk that were not previously included in the requirements directly, e.g. dwave-cloud-client
In my opinion this complicates the repo significantly and users who might want to edit the sdk-level documentation might bounce off it
I am not sure how git's symlink support translates to windows - though https://stackoverflow.com/a/52097145/8766655 implies that newer versions of git will support it

As of the first commit only dimod as been added (to show how it could be done). Also the doctests are failing both for syntax errors and because the QPU is not available to circleci.

Merged into dev for now so that the changes are not overwhelming


ResNeSt

Paper
Implement ResNeSt: Split-Attention Networks
TODOs

[x] develop the model in a scalable way (using *Block syntax and nn modules)
[ ] draw the model on figma
[x] write doc
[x] test the model
[ ] get (if possible) the pretrained weights

Done with #198 missing pretrained weights, will do for now

Done with #198 missing pretrained weights, will do for now


Serializing the tree

Hi,
This library looks very interesting. Since I do not want to reconstruct the tree everytime I load my program, I was wondering if there is a way I can go about serializing the tree once I build it. Is there a way to do this efficiently?
Thanks!

@rapoth There is not an integrated method in the library. You would need to walk the tree and serialize it to a format of your choice. Radix tree's are more optimized for in-memory layout than on disk, as opposed to a B-Tree.


[Wait for other anonymous consents issues to be done] Write e2e tests for anonymous consents

General
See master ticket for more details: #3800
Create a PR against the master feature branch.
Cases to cover
The e2e tests should cover the following cases:

Moving from Anonymous User to Logged In Customer - once the user logs in, the consents that were given as an anonymous user are ignored, and the consents of the currently logged in user are restored, see "Moving from Anonymous User to Logged In Customer"
The case when a user is moving from an anonymous user to a registered user, the consents should be transferred (see Moving from Anonymous User to Registered Customer). E.g. if an anonymous user gave a tracking consent, and then the user decided to register, the tracking consent should be automatically given on the back-end once the user registers. However, this is not working as intended when using the OCC APIs. Check if it was fixed in the meantime, if not skip this. UPDATE - we will implement a workaround for this, so this case can still be covered.
In the old accelerator, when an authenticated user logs out, the previously given consents are restored (when the user was anonymous, i.e. was not logged in). See "Moving from Logged In Customer to Anonymous User When Logging Out"
The language change should not affect the anonymous consents state. The language of the consents should change, but not their consentState values.
Giving consent on the registration page
Maybe it would be a good idea to test a required consent (#4462), but not sure how to change the configuration in the run-time, and mark one of the sample consents as required.

PR: vhttps://github.com/SAP/cloud-commerce-spartacus-storefront/pull/4959

PR: GH-4981


Routing not working

Even though I added
$router->add('home/details');
some how the routing is not happening.
Controller is Home
Action is detailsAction

Hi,
in what way isn't it happening? Please can you describe exactly what happens? For example, do you get an error message? Please also include the URL that you're trying.
Thanks,
Dave

@daveh I think you need to add $router->add('{controller}/{action}'); here by default to prevent such issues.

That's a great idea @gonzela2006, done! :+1:

Thank you :+1:


Style-guide - don't import from .../src of dependencies

I haven't seen this mentioned anywhere
because src is considered being private implementation that should not be accessed from the outside.

Could you put an example? I'm not really sure if I follow.

Sorry for not being more clear
Like mentioned in http://stackoverflow.com/a/37695504/217408

import {isString, isArray} from "@angular/common/src/facade/lang";

As far as I know one should not import from the `.../src/... directory of a dependency because it is considered private.

You can't do that anymore, so closing!


Fix RFC 5424 syslog message

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
Remote logging of OPNsense firewalls are problematic (annoying) when the message contains square brackets and quotes.
A clear and concise description of what the problem is including your motivation for the request,
i.e. "For the purpose of [...] I am missing a solution that will [...]."
RFC5424 output contains the following: - [meta sequenceId="726"]
Describe the solution you like
Remove the square brackets, remove the equals sign, remove the slashes, remove the quotes
A clear and concise description of what you want to happen.
(e.g. I would like an input field in the /ui/firewall/alias which would add .... to ....)
Remove the square brackets, remove the equals sign, remove the slashes, remove the quotes
Describe alternatives you considered
no alternatives...
A clear and concise description of any alternative solutions or features you considered.
none
Additional context
If the meta sequence ID is absolute needed in the message consider remove special characters. Ideally, adding a suffix to the procid number would be preferred.
Add any other context or screenshots about the feature request here or links to relevant forum thread or similar

Better fix the parser reading the stream, the brackets are part of RFC5424 (
https://datatracker.ietf.org/doc/html/rfc5424#section-6.5 https://datatracker.ietf.org/doc/html/rfc5424#section-7.3 ,  https://datatracker.ietf.org/doc/html/rfc5424#section-7.3.1)

:(


Fix #18 duplicate reassignment

Addressing #18
Duplicate reassignment will happen when multiple outOfSyncReplicas exist and target broker is still least used broker.
Creating the broker queue each time so we don't need to deal with recovering the brokerQueue for next outOfSyncReplica

could we start with adding a unit test that can reproduce the issue?

Test added to reproduce issue, updated fix to avoid costly operations.

@kabochya  Thanks for making the fix!


Text Overflow

I think this maybe a pbta system problem, I'm not sure. The text overflow over the tabs.
This happens with the the module FW. You just need to create an agent and add more than 3 lines.

Link: https://github.com/Rangertheman/fwrpg-for-pbta/issues/30

Just made a new release that should fix these issues. Let me know if you're still having these issues or something similar pops up.

Just made a new release that should fix these issues. Let me know if you're still having these issues or something similar pops up.

Worked. Thank you.


SVG in a form -- is it possible to have the SVG code added inline on the page?

Hi, I'm trying to add an SVG to my form and for styling reasons (ie. setting fill colors for paths) I'd like to have the actual SVG code on the page without creating a separate custom component for the image, if possible.
In this example, the first item works when displaying an SVG from a URL. The second item does not work... the SVG doesn't get added to the DOM.
fields: FormlyFieldConfig[] = [
   {
     key: 'image',
     template: '<img src="image.svg">',
     templateOptions: {},
   },
   {
     key: 'image2',
     template:
       '<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path fill="#fff" d="M8 22h2l5-8.5h5.5c.8 0 1.5-.7 1.5-1.5s-.7-1.5-1.5-1.5H15L10 2H8l2.5 8.5H5L3.5 8H2l1 4-1 4h1.5L5 13.5h5.5L8 22z"/></svg>',
     templateOptions: {},
   },
 ];

Live example:
https://stackblitz.com/edit/angular-formly-json-model-ovhyvj?file=src/app/app.component.ts
Maybe this isn't possible but if anyone has any ideas it'd be much appreciated. Thanks!

to bypass sanitizing template HTML content, you should explicitly set true to safeHtml:
templateOptions: {
  safeHtml: true,
},

https://stackblitz.com/edit/angular-formly-json-model-gfprqa?file=src/app/app.component.ts

@aitboudad wow, thanks so much! Works great! I really appreciate it.


File Upload Problem

Hello,
I ran the application using the Docker file, but I'm getting this error when I want to upload a file. Where can I be making a mistake? Can you help me?
Error;

I'm guessing your procmon events don't fall into any of these categories: https://github.com/yampelo/beagle/blob/master/beagle/transformers/procmon_transformer.py#L15
I only had a handful of procmon exports available, and they may not have been thorough enough to cover all the values of the Operation field
Would you be willing to share your CSV? Or at least let me know the values of the Operation field you have in your CSV, you can do this easily using pandas:
import pandas as pd
df = pdf.read_csv(path_to_procmon_csv)
df.Operation.value_counts()

I have the same problem in the "Windows Event Log" file.
Windows Event and Procman file: https://yadi.sk/d/VsCMFq5_nztO7w

hey, can you reupload the files?

I have the same problem. So I edited the csv to only contain readfile events. These are in the https://github.com/yampelo/beagle/blob/master/beagle/transformers/procmon_transformer.py#L15.
I also ran the docker with logger at debug info and added a logger entry to the procmon_transformer. The logger statement never showed up.
So I've attached the csv so you can try. (zipped)
Procmon.zip

Found what prevented me from reading in the procmon files.
If you use 24-hour convetion in Windows procmon will use that. a bug assumes that if no 'AM' string present in the log line time is PM. If you add 12 hours to 16 the time is 28 hours which is illegal, this causes an non caught exception in the processor threat.
Created a pull request to fix the bug.


Show error on invalid page

Signed-off-by: Ariana Isabel Hlavaty<EMAIL_ADDRESS>Contributes to #218
What did you do?
Added a Not Found page and a redirect to the landing page after 2 seconds
Why did you do it?
Open issue requested these changes
How have you tested it?
Locally
Were docs updated if needed?

[ ] No
[ ] Yes
[X] N/A

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[X] My changes generate no new console logs
[X] Fixes entire issue
[ ] Partial fix for issue

The Not Found page currently looks like this

:

+1 with your suggestions!
Thank you @arianahl!

@GeraldMit @upkarlidder what do you think of this? I think it's a great update.

I agree!

I've added the AppHeader and translation. I also took the liberty of adding the Spanish translation to it.
New updated page looks like this

:


Add basic detail functionality

I don't know if this is the procedure for commiting individual changes to the central repository (Felix's repository). If not, let me know.
This branch is basically the same than "feature1" which Francisco created on Friday. I have fixed a couple of things and added a basic detail functionality.

Hector, Felix will add you as a collaborator on the repo, and then you can push code directly to it, so someone doesn't have to merge your changes.


Added buttons to collapse and expand all schemas in the tables view

http://g.recordit.co/qHdvyZpbgT.gif

the best way would be to remove the text http://recordit.co/hbbvGqZOc8


ExecJS::ProgramError: TypeError: bundle.render is not a function

I get this error when after I just set up a fresh installation of Rails. I did everything according to the README

Seems related to the component_name - see node_modules/svelte_ujs_ng/svelte_ujs/index.js
  static serverRender(component_name, props) {
    const requireComponent = require.context('components', true)
    const bundle = requireComponent('./' + component_name).default
    const {html} = bundle.render(props)

    return html
  }

Ok I can confirm it works with these versions:

Ruby 2.7.2 (for svelte-rails-demo app - which needs mimemagic 0.3.5)
Rails 6
Webpacker 4.2.2
Node 14

There are issues with newer versions of Node and Webpack that need to be resolved.
To get puma to install on Mac Big Sur in the demo app I also needed gem install puma:4.3.5 -- --with-cflags="-Wno-error=implicit-function-declaration" (from https://github.com/puma/puma/issues/2304)
You also need to use the version of svelte_ujs that is in this svelte-rails repo - it is linked from package.json to ..\svelte-rails which includes svelte_ujs/getSvelteEnvironments.js.

This package.json works with my project
{
  "name": "svelte-my-demo",
  "private": true,
  "scripts": {
    "start": "webpack-cli serve --mode development"
  },
  "dependencies": {
    "@rails/actioncable": "^6.0.0",
    "@rails/activestorage": "^6.0.0",
    "@rails/ujs": "^6.0.0",
    "@rails/webpacker": "4.2.2",
    "svelte": "^3.23.2",
    "svelte-preprocess": "^4.9.8",
    "svelte-loader": "^2.13.6",
    "svelte_ujs": "../svelte-rails",
    "svelte_ujs_ng": "^0.3.4",
    "turbolinks": "^5.2.0"
  },
  "version": "0.1.0",
  "devDependencies": {
    "webpack-dev-server": "^3"
  }
}

This error seems to come about from upgrading svelte-loader from 2.13.6 to 3.1.2

It does work with Rails 7.0.0 alpha 2 and Ruby 3.0.0 as long as svelte-loader stays on 2.13.6 (and below 3.0.0).
Here's another package.json:
{
  "name": "svelte-my-demo",
  "private": true,
  "scripts": {
    "start": "webpack-cli serve --mode development"
  },
  "dependencies": {
    "@rails/actioncable": "^7.0.0-alpha2",
    "@rails/activestorage": "^7.0.0-alpha2",
    "@rails/ujs": "^7.0.0-alpha2",
    "@rails/webpacker": "^6.0.0-rc.6",
    "svelte": "^3.44.2",
    "svelte-loader": "~2.13.6",
    "svelte-preprocess": "^4.9.8",
    "svelte_ujs": "^0.0.2",
    "svelte_ujs_ng": "^0.3.4",
    "turbolinks": "^5.3.0-beta.1"
  },
  "version": "0.1.0",
  "devDependencies": {
    "webpack-dev-server": "^3.11.3"
  }
}

Here's a related issue (https://github.com/sveltejs/svelte-loader/issues/191) and PR (https://github.com/sveltejs/svelte-loader/pull/159)
Change log: https://github.com/sveltejs/svelte-loader/blob/master/CHANGELOG.md#30
config\webpack\loaders\svelte-ssr.js needs to have compilerOptions:
module.exports = {
  test: /\.svelte$/,
  use: [{
    loader: 'svelte-loader',
    options: {
      compilerOptions: {
        generate: 'ssr',
        css: false
      },
      emitCss: false
    }
  }],
}

Maybe config\webpack\loaders\svelte.js also needs this:
    {
      loader: 'svelte-loader',
      options: {
        compilerOptions: {
          dev,
        },
        hotReload: true,
        hydratable: true,
        emitCss: true,
        preprocess: sveltePreprocess()
      }
    }

... and it should work on svelte-loader > 3.0.0

One caveat is the styling is broken in prerender: true mode...
You can set prerender: false to fix this as a workaround (non-SSR):
<%= svelte_component :Hello, {name: 'Svelte'}, {prerender: false} %>
Probably related to the WebPack version... see https://github.com/sveltejs/svelte-loader/issues/169
Unfortunately Webpacker 6 is totally different which makes it hard to upgrade to Webpack 5+ 😭
For example: https://github.com/shakacode/react_on_rails_tutorial_with_ssr_and_hmr_fast_refresh/pull/9


Consolidate retrieve_acronym and to_snake_case functions

This is not a bug or high priority, so closing for now.


Use newer EPER (0.97.6p1)

EPER only supports binary match specs since 0.8.6 - we're on 0.78
This is really usefull when debugging replication latency
https://github.com/massemanet/eper/issues/25
https://github.com/massemanet/eper/commit/5c2807370894e0cf6c7365565d67b6a0bdb75c50

What level of testing have you done? I guess since it is eper it should have zero impact on riak except when an operator is attached and debugging?

Compiled it manually and deployed to Riak 2.2.5 devrel cluster - notes here - https://gist.github.com/bryanhuntesl/4cfce0f51a24b2b5d59b0b0111bb438c#gistcomment-2636622

+1 from me. We must never stand in the way of "sheer joy"


Add NestJS Framework

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add an action for scrolling a line to the top middle or bottom of the screen

Can use the built-in vscode command revealLine as defined on this page

closed by #58


Distance often quite low, regardless of faces - How to improve accuracy?

I've been doing some tests today and am using the following images:

The bottom 4 images are all the same person and the top 4 are different people. Comparing the bottom, third from the left with the first top image (the female) gets  0.4439...
All of them are below 0.6. Many are 0.41 to 0.50.
Do you have any suggestions on how to improve the accuracy?

Additionally, despite the bottom 4 being the same person, there is a stronger match between them with the images of other people in many cases.

I get a distance of 0.8425371094302093 compraing the top left image with the bottom third.
Can you show me what you are doing (code snippet). Are you performing face detection or pass the whole image into the recognition net?
Are you using an Intel GPU?

Thanks for the prompt reply!
It doesn't seem to matter what machine I test on... iPhone 6 in Safari reports almost the same (like .01 difference here and there) as Chrome on my Windows 10 machine with an Nvidia card and Firefox on my Pixel 2.
I'm passing the whole photo in. Here's the snippet:
`$(document).ready(function () {
$(document).on('click', '.btn', function () {
var _ = $(this);
Compare(_.data("img1"), _.data("img2"));
});
    });

    async function Compare(img1, img2) {
        await faceapi.loadFaceRecognitionModel('/Content/FaceAPIModels');
        const descriptor1 = await faceapi.computeFaceDescriptor(img1);
        const descriptor2 = await faceapi.computeFaceDescriptor(img2);
        const distance = faceapi.euclideanDistance(descriptor1, descriptor2);
        alert(distance);
    }`

And here's the button tag for the image comparison:
<input type="button" value="Compare S1 and O3" class="greenbutton btn" data-img1="s1" data-img2="o3" />
If you have suggestions or a different code sample I should try, that would be fantastic.

 Therefore you can use faceapi.allFaces as in the face recognition examples and as stated in the readme and introduction article.


[Pickup city UBS_Order form] The error massage doesn't appear and the frame is not highlighted in red in the fields name and surname when user enter not valid date  in section "Personal date and "The recipient is another person " in step 2 Personal data

Environment:
Windows 10 Home (Version 22H2)
Chrome version 108.0.5359.71
MacOS version 12.6.1 (21G217)
Chromе version 107.0.5304.110
Reproducible: always,
**Build found:**27/02/2023
Preconditions
The user should be authorized

Co To (https://www.pick-up.city/#/ubs)
Sign in as authorized user
Click on the profile and choose the item 'UBS-user'
Click on button ' Нове Замовлення'
Fill up all necessary items on Step 1

Steps to reproduce

Enter in fields  "Name" and "Surname" in section  "Personal date and "The recipient is another person 2. not valid date (e.g  Окс.ана Мель.ниченко)

Actual result
The error massage doesn't appear and the frame is not highlighted in red in the fields name and surname when user enter not valid date  in section "Personal date and "The recipient is another person " in step 2 Personal data

Expected result
The error massage does appear: "Only letters and hyphen, space, apostrophe are allowed"  and the frame is highlighted in red
User story and test case links
E.g.: "User story #2531(https://github.com/ita-social-projects/GreenCity/issues/2531)
Labels to be added
"Bug", Priority ("pri: Low "), Severity ("severity:Trivial "), Type ("UI, "Functional"),

The bug isn't fixed on the prod  environment

We have no access to the Pick up city UBS


chore(action): fix a11ywatch action remote api

upgrades the action to fix an issue with the json interface returned.
add white space trim for jwt storing.
add stable working local action - ( remove EXTERNAL for local action usage )

Hi, going through open-source projects and putting PR's since the action was in BETA for the interface. The api and interface is now stable after these changes for web scanning.

Thank you very much, @j-mendez!
Did I understand correctly that A11ywatch should post a comment here with a breakdown?

Thank you very much, @j-mendez!
Did I understand correctly that A11ywatch should post a comment here with a breakdown?

Hi @ramonh yes, we just deployed the API changes now. Please re-run the github action to see if it succeeded. By default the action should report to the PR using the default github action bot user.


How to share a styled component

@mxstbr , I've started using react-boilerplate and styled-components with this as my only experience with webpack so I come to ask some help in order to support the ecosystem.
I really wan't to share some work made using styled components, but I can't get my webpack configuration to work.
I have folders of components using for example has import :
import React from 'react';
import styled from 'styled-components';
import cn from 'classnames';
import defaultThemeProps from 'styled/themes/bootstrap/atoms/Abbr';
import React from 'react';
import styled from 'styled-components';
import cn from 'classnames';
import Close from 'components/bootstrap/atoms/Close';
import defaultThemeProps from 'styled/themes/bootstrap/atoms/Alert';
import { alertVariant } from 'styled/helpers/bootstrap/mixins/alert';
import { borderRadius } from 'styled/helpers/bootstrap/mixins/border-radius';
import { srOnly } from 'styled/helpers/bootstrap/mixins/screen-reader';
import onClickOutside from 'react-onclickoutside';
import defaultThemeProps from 'styled/themes/bootstrap/molecules/DropDown';
import { borderRadius } from 'styled/helpers/bootstrap/mixins/border-radius';
import { boxShadow } from 'styled/helpers/bootstrap/mixins/box-shadow';
import { navDivider } from 'styled/helpers/bootstrap/mixins/nav-divider';
import { hoverFocus, plainHoverFocus } from 'styled/helpers/bootstrap/mixins/hover';
import { buttonGroup } from 'styled/helpers/bootstrap/utilities/buttonGroup';

All the bootstrap mixins and components are rewritten in a react-boilerplate app.
Every component have 100% unit test using the exact same config as react-boilerplate.
I also have all the documentation with example using our  Bootstrap styled-component, with some adjustment for fitting the need of styled-components.
For example, we don't use reset, and we have a few utilities that need and can be injected using the injectGlobal and an utility. It's convenient and completely customization.
My idea was to start new components only from that lib that own the basic css and customization I need for styling.
I would like to be able to import my component like this :
import A from 'bootstrap-styled/A'
import Link from 'bootstrap-styled/Link'
import Dropdown from 'bootstrap-styled/Dropdown'
import { fade } from 'bootstrap-styled/helpers/mixins/animation'

I use to create npm package in ES5, this become a bit to hard to start with the webpack documentation. Would anyone share a webpack gist so I can start building my component for dist?

If you are using react-boilerplate (so all your webpack tooling is setup), we can call this package bootstrap-styled. So anything you export default from your index.js will be whats at the root.
node_modules/bootstrap-styled/index.js
export default 'hello';

->
import thing from 'bootstrap-styled';
console.log(thing); // => 'hello'

So if you want 'bootstrap-styled/Link', well that is just a file system path. so you can place Link.js next to index.js and anything you export from there will be as desired. Which would look like this.
node_modules/bootstrap-styled/Link.js
export default () => (
  <div> Hi! </div>
);

->
import thing from 'bootstrap-styled';
React.render(<thing/>); // => <div> Hi! </div>

Check out MDN for decenent but brief documentation.

@nelix, thanks for your answer, I got all that first part, but I didn't get how you exported Link.
Did you mean import thing from 'bootstrap-styled/Link'; ?
I was looking at this plugin https://github.com/kadirahq/react-cdk but I wasn't able to configure it to work the same as in react boilerplate :/
So if you tell me I can use the exact same projet, this will be much easier

I mean in your library, the filename is literally Link.js.
If your library's entry point had
Lol.js bah.js index.js
then you could import 'libname/filename' (with or without the .js extension) or import 'libname' to get the index
I honestly would try reading an article or the new webpack docs, the boiler plate can shelter you from solving some hard to learn problems the burn you when you have a big technical debt an cannot do any fault isolation.

@nelix , I have try to read docs and articles but most of them are not up to date or/and use a bunch of different plugins.
If you have good article that could help me understand the 3.3.3 / 3.4 of the boilerplate, I would be happy to read it.

@nelix, I am just thinking that the way it is configured, webpack only build one chunked file, so I guess the options of building with the current webpack configuration is not possible.
Is there any other alternative ? Would it be possible to have a documentation for that ? I think this is somehow important for everyone.

Why are you not exporting them as named export in your entry file?
export { A } from './A.js'
export { Link } from './Link.js'

So you can import them like:
import {
  A,
  Link
} from 'styled-bootstrap'

If you're using webpack@2 you can find really good documentation at https://webpack.js.org/. You're probably searching for the externals option so React and styled-components aren't included in your bundle.

can we reopen this ?

Why are you not exporting them as named export in your entry file?

I have more than just components (tags), I also have all the mixins and helpers bootstrap have.
I have functionalities that can be used to inject part of bootstrap, for examples to injectSpacing to be used in injectGlobal.
Thing like this, exporting everything in one file is not very conveniant.
I have copied the react-boilerplate configuration and removed everything I though it wasn't usefull for that.
I need to reorganize the folders and import while making it as a module so I've just added the A components and all the mixins, would you mind have a look to my webpack config and see how I could prepare this for releasing it correctly ?

I forgot the link https://github.com/kopaxgroup/bootstrap-styled


Dot Net Core support

When is dot net core support coming?
By the way...Thank you for creating this awesome project. This should have way more stars. Very useful.

Hi @CloudBranch thank you for your kind words!
I publish a single NuGet that contains both .NET Framework as well as .NET Standard, and use it in .NET Core projects all the time.  Was there something else that you were looking for beyond that?
Cheers, Joel

Hi @CloudBranch please re-open if there is something needed beyond .NET standard.  It works in .NET Core use cases.  Cheers!


[IN PROGRESS - No Merge] - HTTP Transport Support

[IN PROGRESS] HTTP Transport - HTTP Transport Support

Woot


Downloads appear empty

I have several galeries downloaded. I can see the images through a file manager but when i try to see them through the app it shows no downloaded galeries.

Could you tell me your Android version?
Check if in your folders there is a file called .nomedia, it should be hidden by default, if you open it it should contain a number

Android version 9
Software version Q720CS10N
I am unable to see any of the downloaded galleries. I can see when they are downloading but once they finish they are no longer listed

I downgraded to 2.2.0 and confirmed it functions in that version. Once i updated it broke again. FYI


MTR Version for 1909 not listed in Release Notes

MTR version highlighted as being the minimum required for 1909, is not a version that MS have provided any release notes for. How do you obtain MTR <IP_ADDRESS>?
Another thing to point out is that some Lenovo Hub 500 devices have been reported as having 2004 as an available update for them, yet it is not recommended to use due to issues.
Why is 2004 showing as an available update if it is not supported on MTR devices?
Cheers
Jrich1

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

ID: 7ecd6ee6-8850-f346-5684-9c5d2444789f
Version Independent ID: a55a7a01-211d-147a-5332-b68e1051a2a1
Content: Version Support - Microsoft Teams
Content Source: Teams/rooms/rooms-lifecycle-support.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@Jrich1 Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Indexes replication issue

Hello,
I created an index, use it and works perfectly. But then when I tried to sync it gave me an error that i dont have access for that.
Im using pouchdb-authentication and for now all users have all permissions.
What is the correct way to fix this?

Delete the index after usage so hopefully it doesnt get synced?
Use Query instead of find?
Maybe there is a way to use find with preexisting indexes created in the remote db?
Filter the replication so it doesnt sync design documents

Thanks!!

It depends on which kind of backend you're trying to sync with. Keep in mind that Mango queries are only supported in Cloudant, Couch 1.7, and Couch 2.0.
In general, though, it sounds like your particular issue is a 403 related to not having permissions to create _design documents. In those cases the simplest solution is to use filtered replication to avoid syncing _design documents. Hope that helps!


chore: bdd-spring-1583404849 to 0.0.1

chore: Promote bdd-spring-1583404849 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Configuring parameter names

We are using this plugin, and allowing a username or an email. Having the ability to specify the post params to be "username" instead of "email" or "pwd" instead of "password" would be a really nice addition.

@blacketastic2 How did you figure out all? I still can't manage to get all working with custom parameter names.


Add a better example

Add a real world example with some real data etc.

Simple fruit stand example added in 8c18bc5b55044b01799e0eff997dc5f07f4cedeb.


Missing png image in docs

There is a missing image at the following page:
_notebooks/core/_notebooks/core/tellurium_stochastic_files/tellurium_stochastic_6_0.png
https://tellurium.readthedocs.io/en/latest/_notebooks/core/tellurium_stochastic.html?highlight=gillespie

Any docs under _notebooks should be ignored. I would like to hide it from search but I don't think that's possible. All the relevant docs are incorporated under Usage examples by commit 5ed2ead8db14c3629bfe1bcea7810cec54db882b. Still needs to be merged into master though.


Failed to compile on Linux ARM64

Host : Ubuntu devel 21.04 ARM64
Compiler : GCC 10.2 / Clang 12.0
Log :

I believe it works now. If not, please reopen.


Electron binaries

This is essentially a duplicate of #905, just rebased against the current node-serialport, fixes issue #812. All code credit goes to @suda
A few things to note, it appears the npm test scripts can't be run in a powershell context, the 'tick' is unicode and appveyor's powershell incorrectly encodes it, resulting in failed builds. This is avoided by cmd IF statements instead of powershell if statements.
Electron doesn't run globally, so we can't run regular tests, there's a 'load electron and serialport' test, but perhaps we should increase coverage.
Node 5 is added, since that's what electron is still using.
I've marked 1.4.6 as the latest electron, trivial to add other versions if we need. We should test binary compatibility across electron to get maximum coverage.

Current coverage is 85.28% (diff: 100%)

Merging #1015 into master will increase coverage by 0.48%

@@             master      #1015   diff @@
==========================================
  Files            14         13     -1
  Lines           737        666    -71
  Methods         123        111    -12
  Messages          0          0
  Branches        175        156    -19
==========================================
- Hits            625        568    -57
+ Misses          112         98    -14
  Partials          0          0

Powered by Codecov. Last update 908b753...c5c541e


Rename boolean properties

Properties with a boolean dataype need to be renamed after the form 'isName', ref #396. This relates to the following properties:
CollectionDescriptionScheme.distinctObjects
ObjectGroup.currentCollection
ObjectGroup.knownToContainTypes
RecordLevel.derivedCollection
SchemeMeasurementOrFact.mandatoryMetric
SchemeMeasurementOrFact.repeatableMetric
SchemeTerm.mandatoryTerm
SchemeTerm.repeatableTerm
The name will need changing in...

ltc_standard_terms_draft.csv (https://github.com/tdwg/cd/blob/review/standard/terms/ltc_standard_terms_draft.csv)
ltc_skos_mapping.csv (https://github.com/tdwg/cd/blob/review/standard/terms/ltc_skos_mapping.csv)
ltc_datatypes.csv (https://github.com/tdwg/cd/blob/review/standard/terms/ltc_datatypes.csv)
json schema defs for the relevant terms (https://github.com/tdwg/cd/tree/review/standard/json-schema)
json examples, wherever present (https://github.com/tdwg/cd/tree/review/examples/class-level json examples)

Closed by #426

Wiki Section 2.2. 'Collection Description Schemes' text updated to match in revision c68dd85


Pose Track: Get human part descriptors.

Hi MediaPipe,
First, I want to say it's a great project!
Next, I wanted to ask for your help. As part of a research project I am doing, I am using MediaPipe to extract human joints.
I wanted to ask if there is away to extract the human part descriptors and not the final landmarks?
Thanks for any kind of help!
Asaf,

Hello @asafjo23
Would you please elaborate what do you mean by "human part descriptors"?

Hi ayushgdev,
Thanks for the quick response, really appreciate it.
As far as I know, most pose detectors (or at least the bottom up approach) are locating the human body parts before regressing to final keypoints.
That means, there is a step where there is more infromation about the body part beside the coordinates (like visual fetures). I refered to this information as the body parts descriptors.
So I wanted to ask if there is a way to extract this information from the pose detector (I think it's blaze pose), maybe from one of it's layers? or any other component.
I hope I was managed to clarify my wish.
Thanks again :-)

Hello @asafjo23 No there is no such information available in the MediaPipe pose detection models. The only outputs MediaPipe pose detection models produce are coordinates, world coordinates, and segmentation mask. The landmarks/coordinates also contain visibility and presence of each landmark. For more information about the model, you can refer to the documentation and the model card page.

OK @ayushgdev , Thanks for you kind help :-)

Can we close this issue @asafjo23 ?

Yes, I will close it.


[KYUUBI #1567] [Bug] Kyuubi beeline can not connect to kerberized Kyuubi

Why are the changes needed?
Failed to connect to kerberized Kyuubi with Kyuubi beeline.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

Before:

After:

[ ] Run test locally before make a pull request

cc @turboFei @pan3793

Let's change the PR title to Expose HADOOP_CONF_DIR to fix ...

merging to master/1.4


skip prompt during installing stackdriver agent

https://github.com/GoogleCloudPlatform/dataproc-initialization-actions/issues/297

I signed it!

Replaced the 'echo "Y"' with 'yes'.

the stackdriver-agent init action script cannot fixed by simplely passing 'yes' to prompt up.
Actually an easier way to install Stackdriver agent is add property 'dataproc:dataproc.monitoring.stackdriver.enable=true' in the create cluster command, for exmaple: "gcloud dataproc clusters create test-cluster --properties 'dataproc:dataproc.monitoring.stackdriver.enable=true'"
Close this pull request.


Power toys

Description of the new feature / enhancement
hide icon in tray system
Scenario when this would be used?
minimalizm
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/9526


allow input options to be an array

This is to also allow input options without value to be passed in front of input path, otherwise ffmpeg will complain.

@bikeath1337 Can you please review ? Thanks!

Can you describe this PR better? It's only by looking at your code, that I think you're requesting this because you want to use an advanced streaming option -ar that has no key/value pair.

Yes that is correct. I want to pass '- re'  option in front of the input parameter which does not have a value

@pirvudoru thank you for the providing a PR with coverage! I had some issues with my github configuration, so I merged this via my fork. It's merged here https://github.com/streamio/streamio-ffmpeg/commit/a20c9efb0f948e22accea40e5a7d9f76433dd5a7.


could you help me to add an item functionality to the example of invoices?

in such way that when selecting  a new item from a selection field  in the invoice detail , the description and price of the invoice detail fields could be  filled automatically  with their corresponding values of the  item collection. Thanks

@hulaigann hey, sorry for late answer. Did you solved the problem?

Hi Petar.
I found a way  of doing it.  Basically writing all the code  into the
events_code label  of the definition's page . So the user can  populates
automatically  the fields associated to the item (price and description) of
the invoice detail form when he selects the item from the combo .
"events_code": "'change select[name=itemId]': function(e, t) {
var prodId = $(e.target).val();
p = Items.findOne(prodId);
$('input.form-control[name=description]').val(p.description);
$('input.form-control[name=price]').val(p.price);
}"
I don't know if there is an  easier  or shortest way to do that. In such
case please make me know. I will apreciate a lot.
I take this opportunity to congratulate you on this great work, and offer
my assistance on those things that can bring you.
(Sorry for my english , my native language is spanish)
2016-04-27 12:47 GMT-06:00 Petar Korponaić<EMAIL_ADDRESS>
@hulaigann https://github.com/hulaigann hey, sorry for late answer. Did
you solved the problem?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/perak/kitchen-site/issues/294#issuecomment-215190186

@hulaigann currently there is not better way, but it will be soon. Working on a new GUI and improving CLI... just a little bit more patience :)
GUI Preview video here: https://www.youtube.com/watch?v=NBtFs1c4qhQ
:+1:
P.S. my English is far from perfect too :)


[Appfundamentals][revampdoc][1587213]

Revamp document WIP

Docs Build status updates of commit 21d07af:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 11, Column 140: [Warning-file-not-found] Invalid file link: '~concepts/design/understand-use-cases.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 30566c4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 11, Column 140: [Warning-file-not-found] Invalid file link: '../concepts/design/understand-use-cases.md'.
Line 11, Column 268: [Warning-file-not-found] Invalid file link: '../concepts/extensibility-points.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/concepts/design/understand-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 11, Column 140: [Warning-file-not-found] Invalid file link: '../concepts/design/understand-use-cases.md'.
Line 11, Column 268: [Warning-file-not-found] Invalid file link: '../concepts/extensibility-points.md'.

msteams-platform/concepts/design/understand-use-cases.md

Line 46, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/design/map-use-cases.md'.
Line 48, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs.md'.
Line 49, Column 3: [Warning-file-not-found] Invalid file link: '../bots/design/bots.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/concepts/design/understand-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 11, Column 140: [Warning-file-not-found] Invalid file link: '../concepts/design/understand-use-cases.md'.
Line 11, Column 268: [Warning-file-not-found] Invalid file link: 'concepts/extensibility-points.md'.

msteams-platform/concepts/design/understand-use-cases.md

Line 46, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/design/map-use-cases.md'.
Line 48, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs.md'.
Line 49, Column 3: [Warning-file-not-found] Invalid file link: '../bots/design/bots.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1dcd005:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6bf480b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

Docs Build status updates of commit 3eae71a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

Docs Build status updates of commit 2ffe619:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

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

Docs Build status updates of commit 2b98cf0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

@heath-hamilton, @sathya-raveendran
A gentle reminder for tech review/sign-off.
Please provide your comments as we will be merging this PR on Thursday, April 8th. If we do not receive any comments, we will still merge the PRs.
In case of any gaps, please raise a doc-bug.
Thank you.

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 0c04d7a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 0c04d7a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 1f9ae27:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 6bf05f0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 7f7a82b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 4e707d8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 421d27b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 27f9910:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 27f9910:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 104, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/design/map-use-cases.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md

Line 103, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/overview.md'.

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

Docs Build status updates of commit 77b6928:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

Docs Build status updates of commit 31fa0bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

Docs Build status updates of commit 020bd46:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/extensibility-points.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

Hi @sathya-raveendran - have incorporated your comments. Request you to provide your approval.
Thank you.

@heath-hamilton - thank you. :)


Integrate Phytos31

Name/Affiliation/Title
John, UCSC, protector of code (aka maintainer)
Purpose of the PR
Add support for the Phytos31 leaf wetness sensor
Development Environment
Linux spruce 6.8.2-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000 x86_64 GNU/Linux
PlatformIO Core, version 6.1.7
Used ST-Link V3 MINIE
Test Procedure
Connect the Phytos31 sensor to the V+ terminal and ground V- to put in single ended configuration. First run the example code to see raw voltage outputs printed over UART. Place hand on Phytos31, the output should change.
In the same configuration run the default env and check for changes on Dirtviz under cell name demo.
Additional Context
Python protobuf package dependency versions has been updated to hopefully fix #73. Also, the publish-to-testpypi is reconfigured to only run on workflow dispatch (#35).
Closes #35
Closes #58
Closes #73

I didn't delete syscalls.c or sysmem.c because I don't have my testing set up with me. So I can't verify it doesn't break everything.


fix(risedev): fix ci-compaction-test

Signed-off-by: Runji Wang<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Correct a file name to fix the main-cron CI.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)
https://github.com/risingwavelabs/risingwave/pull/6678#issuecomment-1338785485

Duplicated with #6741? 👀


Simplify code and fix test

These are some clean up, so I just send in one PR.
And I add a go.mod file.

I didn't realize go1.3 is still in travis config. So I reverted the code to use unix.Dup2 directly.


Finding the most popular/hot games currently

Hey, so in v3 there was the "popularity" field which kind of helped me to get the most popular games,
but now(v4) i don't know what i should rely on, the ratings on igdb is not something i can rely on, there is low number of raters there and are sometimes very inaccurate imo.
I'm trying to get the hottest online games played currently, like "among us", "league of legends", "dota 2", "fortnite", "Call of duty" etc...
Getting the top games in twitch could also help.
What should i do? thanks.

Sorry for the late response. Popularity will come back eventually, but in the meantime, you can query Twitch with the same token that you use for IGDB, or use our "ratings". For deeper discussion, join us in the #api channel on discord: https://discord.gg/igdb