text:
feat(Responsive): add component

Why?
This component is the idea picked from my production project. Breakpoint uses syntax from Grid's device visibility, but has two important differences:

it doesn't require Grid markup, so two close items can have a different visibility
it doesn't render children when they doesn't visible

Warning
Breakpoint adds a listener to window that can cause a performance issue, however it will be solved by #1733.

P.S. Better ideas about the component's name are welcome.

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1872   +/-   ##
=========================================
  Coverage          ?   22.11%
=========================================
  Files             ?      146
  Lines             ?     2501
  Branches          ?        0
=========================================
  Hits              ?      553
  Misses            ?     1948
  Partials          ?        0

Impacted Files
Coverage Δ

src/addons/Breakpoint/Breakpoint.js
5.26% <5.26%> (ø)

Continue to review full report at Codecov.

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

Also need merge with master

Naming
Per the request for naming, I've renamed this component:
<Responsive breakpoints={} />

I think this makes sense as many devs should be familiar with Bootstrap's "responsive utilities", which are classes for the same purpose.
breakpoints
I'm not sure about this prop.  It seems it would be most helpful to set this at the LESS/CSS level instead.  If we did allow overriding a specific <Responsive /> element with different values, what about something like this instead?
<Responsive minWidth={400} />
<Responsive maxWidth={800} />

What is the use case for overriding the value of mobile, etc?

Naming
Agree about Responsive.
breakpoints
I've add it because width that SUI uses variables and it can be possible, that someone override them in own theme. Thats why I think we allow to change used values.

Oh, I see.  I was mistaken in thinking the only='mobile' here was relying on a mobile className and a CSS media query for visibility.  I see now that this is only mimicking the CSS visibility styles.
The only issue I see here is that users with custom CSS breakpoints in their theme would expect this component to respect them, but it won't.  Imagine I set my theme to have a mobile breakpoint of 400px:
<Column only='mobile' />        // only <400px (uses my LESS/CSS value)
<Responsive only='mobile' /> // only <300px (uses defaultProps value)

I'm worried about adding complexity and configuration to the theming process.  It is quite cumbersome already.
My next suggestion was going to be that we should add CSS support for these utilties, however, it looks like SUI core isn't fond of responsive visibility or responsive utilities.  There is a design decision to not permit them.  While I don't agree, chances of getting into CSS core are minimal.
I'm still not comfortable merging this while we have two components with only='device' which would render differently.  We need some kind of way to ensure all components use the same values.

You justly paid attention to these things, but unfortunately I see no other way to solve this problem.
I want to solve the problem with useless rendering, Grid renders all elements in contrast to this component. It's very usefull for navbars and other responsive things.

What if we remove the only prop and go with min/max width props instead?  Users can create the same values locally:
const mediaQueries = { tablet: { minWidth: 768, maxWidth: 992 }  }

<Responsive {...mediaQueries.tablet} />

I would be OK with this as it doesn't suggest to the user that there is any relation between Responsive's only prop and Grid's only prop.

I will think about this, but <Responsive only='mobile' /> looks more intuitive.

You're right, it is very intuitive.  If it used the same CSS as the Grid it would be a no brainer.  Since they will produce 2 different behaviors, I think it becomes unintuitive.
One hack I didn't want to mention was somehow creating a ui grid element and checking the styles.  I would rather not go down that road, but it may get us to where we need to be.

Cool, seems like a good middle ground 👍 Thanks much for the cooperative spirit.

Released in semantic-ui-react@0.73.0

authors: codecov-io layershifter levithomason

repo: Semantic-Org/Semantic-UI-React


text:
fix(Dropdown): prevent calling onChange unless value changed

For the Dropdown component, ensures that onChange is called only if the user selectes a value that is different from the current value of the Dropdown. This is so we can have parity with the regular HTML select.

Excellent work, thank you much!

Released in semantic-ui-react@0.85.0.

source: gharchive/pull-request

authors: levithomason zarend

license: MIT

license_type: permissive

license_source: github-api


text:
Alerts

Do we have smth like this in SUI?
http://s-alert-demo.meteor.com/

#1430

source: gharchive/issue

repo: Semantic-Org/Semantic-UI


text:
Feature request: input+dropdown improvemet as HTML5 Input datalist tag (ComboBox: editable Select)

Feature request: input+dropdown improvemet as HTML5 Input datalist tag (ComboBox: editable Select)
You can insert any value in Input tag and you have a Drop Down icon for introduce optional sugestions with values, labels and Icons as editable select.
Examples:
Input tag with Data List (Drop Down icon show optional values with lavels in Chrome)
link: http://triancal.esy.es/?p=15&t=6.4951905284

NGPrime Input Autocomplete (optional sugestions with Icons)
link: http://www.primefaces.org/primeng/#/autocomplete

Other sugestions:
Input adicional parameters:
X delete Icon shows when has any value (default true).
Undo icon (Default: false). * Go Boton (Default: false)
Select all text when focus default true.
Esc key: Back to initial valueEditable: As Input or Label/Select tag role. (Default: true)
Note: Icons don't alter tag width

Validation improvements:
Realtime Auto Validation border colors while insert text.
Numbers and Text (<, <=, >, >=, !=)
Array of validators with Regular expressions and funtions().
Internacional: examples: "e equal é" or "n diferent ñ"

DropDown adicicional options:
Selected Item background Color (Default: Automatic (good contrast)).
Max items (Default Max number of items in window)
Scrollbar (Default: Enabled with effects)
AutoOpen: open when focus. (Default: false)
Show: Enable dropdown icon only when has values (Default: true)
Automatic: display dropdown icon only when has focus: (default: true), (false=ever showed)
Sort values (Internacional: example "e or é" or "n ñ") (Default: false)
Note: All values are ever shows bellow with a divider.
Multiple: Select some values with checkbox. (Defaut: false)
Search: with hilights sugestions while you type (begin, contain, seam...)(Default: false)
Exclusive: User only can insert DropDown list values default false
Insert component as values
Groups, disable, hidden and dividers.

Thanks.

Thank you for suggestions.

It would be great to have a custom renderer for the elements of the list after a remote search.

I'm not sure I understand the request. We include most of the settings you mention, search, showOnFocus, scrolling, maxItems (through css variables), groups, details etc.
Please see our contributing guide to see how to make more effective suggestions by narrowing the focus to a specific feature.

authors: Cougar84 JesusSD jlukic jokeronaldo


text:
Toggle sidebar and ios class

When you open the sidebar on an ios device, the css class 'ios' is added to the html tag.
But when the sidebar is closed the ios class is not removed. That gives some issues and inconsistency in the ui, scrolling speed etc.
Is this just a bug, or by design? Do have to remove the ios class manually in js?

I don’t have access to an iOS device, but this issue might be related: #4264.

Not sure if it's exactly the same issue, but I got two issues.
One is that you get two different scroll rates.
When the sidebar has been toggled once and the ios class is applied.
You get that smooth fast scrolling (-webkit-overflow-scrolling: touch;)
But then the ios class is not applied, eg. if you refresh the page, you get normal scroll speed.
The second is hard to explain without a video.
When the ios class is applied and you have a fixed top menu. When you pull down like "pull to refresh" in an app, the background is going over the top fixed menu.

Issue is fixed in 2.2.11

authors: Banandrew Emusp


text:
Hz-Seconds Converter

Student, group: Pudov Nikita, 3530901/90203
URL: https://github.com/Npudov/ConverterHzToSeconds
Git approach: git-flow

~/Development/SPbPU/ConverterHzToSeconds (main)
smart@thinkpad$ docker build -t ConverterHzToSeconds .
invalid argument "ConverterHzToSeconds" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
See 'docker build --help'.
~/Development/SPbPU/ConverterHzToSeconds (main)
smart@thinkpad$ docker build -t converter .
Sending build context to Docker daemon  270.8kB
Step 1/5 : FROM adoptopenjdk/openjdk16:latest
 ---> f726a5bfd9ff
Step 2/5 : ARG JAR_FILE=out/*.jar
 ---> Running in b2ca3328b4a6
Removing intermediate container b2ca3328b4a6
 ---> 6aed5bdc7ce6
Step 3/5 : COPY ${JAR_FILE} Converter.jar
COPY failed: no source files were specified

~/Development/SPbPU/ConverterHzToSeconds (main)
smart@thinkpad$ docker build -t ConverterHzToSeconds .
invalid argument "ConverterHzToSeconds" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
See 'docker build --help'.
~/Development/SPbPU/ConverterHzToSeconds (main)
smart@thinkpad$ docker build -t converter .
Sending build context to Docker daemon  270.8kB
Step 1/5 : FROM adoptopenjdk/openjdk16:latest
 ---> f726a5bfd9ff
Step 2/5 : ARG JAR_FILE=out/*.jar
 ---> Running in b2ca3328b4a6
Removing intermediate container b2ca3328b4a6
 ---> 6aed5bdc7ce6
Step 3/5 : COPY ${JAR_FILE} Converter.jar
COPY failed: no source files were specified

fixed

`+

authors: Npudov SemenMartynov


text:
Formatting and hyperparameter settings before merge

Exploration of the KAN hyperparameter space
Really looking forward to doing some sweeps to characterize the KAN performance in different settings (starting similarly with shakespeare_char then moving on to wikitext103).
Some settings:
mlp_variant = kan
kan_poly_order
kan_base_activation
kan_middle_layers (can set these, hopefully this will be compatible with our run_experiments)
use_parallel_mlp
mlp_variant_mlp
mlp_sharing_size
mlp_sharing_sym
Alternatively can try:
linear_variant="kan", but may be better for a much smaller n_embd (else we'll run out of VRAM with default settings)
That being said maybe we won't need as much n_embd with KAN?
Note on stability
Seems there was a div by zero instability only during inference stemming from the forward method of the KAN class.
Clamping this to a small number appears to have addressed it.
Note on training
Seems that the memory taken by KAN is much larger than that for a usual MLP.
We may have to try the new --use_gradient_checkpointing feature in order for some of the explorations to fit into VRAM.
Looking forward : )

Okay, should be good to go, after you merge this PR into your repo, it should update the PR on ReaLLMASIC and then KAN can be merged into the main repo : )

Feel free to reach out via the group chat if you have any questions.

repo: SenmiaoORZ/nanoGPT


text:
Error when clone

Hi, Thanks for sharing the implementation
I can not use git clone on windows, it raise a error below
`
Cloning into 'UniFormer'...
remote: Enumerating objects: 3489, done.
remote: Counting objects: 100% (71/71), done.
remote: Compressing objects: 100% (38/38), done.
remote: Total 3489 (delta 46), reused 35 (delta 33), pack-reused 3418
Receiving objects: 100% (3489/3489), 28.34 MiB | 5.25 MiB/s, done.
Resolving deltas: 100% (1500/1500), done.
error: invalid path 'image_classification/token_labeling/exp/uniformer_small_dim64_tl_224 /run.sh'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
`
I try to follow, but raise another error,
`
cd Uniformer
and run
git restore --source=HEAD :/
error
error: invalid path 'image_classification/token_labeling/exp/uniformer_small_dim64_tl_224 /run.sh'
error: invalid path 'image_classification/token_labeling/exp/uniformer_small_dim64_tl_224 /test.sh'
`
How to fix this error?

I have never met this bug. You can try to download the ZIP files directly.

Hi, with the help of my friends, i solved the error. So, to help a few windows users like me avoid facing the same problem, you can remove white space character after 'uniformer_small_dim64_tl_224'. Thanks

I have made a pull request.

Thanks for your help!

repo: Sense-X/UniFormer


text:
merging vcf files from the same sample before VQSR and CNV

The samples were sequenced in two batches at different points in time, Each batch was analyzed separately with the Sentieon pipeline and we now have two vcfs per sample.  How can we merge the calls in the vcfs before running VQRS and CNV on each sample?

Merging information from the two VCFs is somewhat complex. There will be some discordant calls and it is not clear how the discordant calls should be handled.
Instead of merging the VCFs, you might pass the BAM files from both batches to the variant caller so that it can take advantage of the read information in both datasets to make the most accurate variant calls. If the BAM files from both batches have the same sample readgroup (RGSM), you can pass both BAM files directly to the variant caller:
sentieon driver -i <sample_batch1.bam> -i <sample_batch2.bam> -r <ref> ... \
  --algo Haplotyper ... sample_jointCalls.vcf.gz

If the BAM files from the two batches have different RGSM tags, you might use samtools reheader to replace the RGSM information in one of the BAM files.
The result would be similar to starting from the fastq for both batches and then processing the data using the multi-FASTQ.sh script.

authors: DonFreed grendon

repo: Sentieon/sentieon-scripts


text:
네비게이션 탭 만들기

여행중, 일정 스크린으로 이동할 수 있는 네비게이션 탭을 만들어야합니다.

App Theme이 추가되지 않아서 투명해서 보이지는 않지만 기능은 잘 동작합니다.
다음과 같은 사항이 추가되어야 합니다.

탭 배경 색 추가(테마 설정)
탭 별 텍스트 추가 "여행중", "일정"
탭 클릭시 선택된 탭 강조하는 스타일 추가

repo: SeoulRo/SeoulRo


text:
http https option

add http or https option
    var httpStr = 'http';
    if (useSSL) {
      httpStr += 's';
    }
    final endpoint = '$httpStr://$bucket.s3.$region.amazonaws.com';

Out of curiosity, what's the use case for supporting non HTTPS requests to S3?

I commented in Isseu but
this pattern
https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteEndpoints.html
Does not support SSL connections
Other plugin also supports useSSL option.

authors: Serdnad mkbsugita shinriyo


text:
Add a scale metadata component.

Tested and works!

Looks good!

repo: SerenityJS/serenity


text:
L-3--1. Скласти інтро.

Скласти інтро (вступ), де в 2-4 реченнях описати, чим ти займаєшся, що подобається робити, що хочеться робити краще, що важливо робити, чому ти тут.

I have been working for years in the it-hardware and system integration domains where I've got experience in sales and client-facing, negotiation, managing teams and projects, and deal-closing skills but now I want to switch to the web-development. I'm passionate about new technologies and I'd like challenging tasks so I hope to get the possibility to get new knowledge and skills at the Binary Studio Academy.

repo: SerhiyAndryeyev/homepage


text:
Aws lambda报错 An update is in progress for resource

第一次部署会成功，第二次部署的时候如下提示，如果直接remove掉，然后部署也会直接成功
❯ s deploy
Starting ...
[2022-01-27 10:48:40] [INFO] [S-CLI] - It is detected that your project has the following projects < level2,level4 > to be execute
[2022-01-27 10:48:40] [INFO] [S-CLI] - Start executing project level2
Starting deploy of AWS Lambda "alert-center-aws-notice" to the AWS region "ap-southeast-1".
Start compressing code.
Packing ...
Package complete.
Successful compression code.
✖ Project level2 failed to execute:

ERROR:
The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:ap-southeast-1:xxxxx:function:alert-center-aws-notice

TraceId:     34363bd055061643280528259
Environment: @serverless-devs/s: 2.0.99, core: 0.1.28, s-home: /Users/shaoyun/.s, darwin-x64, node-v14.17.1
Documents:   https://www.serverless-devs.com
Discussions: https://github.com/Serverless-Devs/Serverless-Devs/discussions
Issues:      https://github.com/Serverless-Devs/Serverless-Devs/issues

Please copy traceId: 34363bd055061643280528259 and join Dingding group: 33947367 for consultation.
You can run 's clean --all' to clean Serverless devs.

配置如下
edition: 1.0.0
name: alert-center-aws-notice
access: default
vars:
  region: ap-southeast-1
  role: arn:aws:iam::xxxxx:role/fc-sns-alert-role
  service:
    name: noticeService
    description: Alert center notice service
services:
  level2:
    component: devscomp/lambda
    props:
      region: ${vars.region}
      function:
        name: alert-center-aws-notice
        description: ${vars.service.description}
        role: ${vars.role}
        runtime: nodejs14.x
        codeUri: ./code
        handler: index.handler
        memorySize: 128
        timeout: 60
        environment:
          variables:
            - Key: ALERT_LEVEL
              Value: "2"
  level4:
    component: devscomp/lambda
    props:
      region: ${vars.region}
      function:
        name: alert-center-aws-notice-high-level
        description: ${vars.service.description}
        role: ${vars.role}
        runtime: nodejs14.x
        codeUri: ./code
        handler: index.handler
        memorySize: 128
        timeout: 60
        environment:
          variables:
            - Key: ALERT_LEVEL
              Value: "4"

初步判断是因为更新状态变成了异步的，这可能是有不兼容变更导致的，我需要确定一下aws lambda的现在的更新逻辑，晚一些修复

@anycodes 可有进展

问题已解决，两种方法：

自行修改devscomp/lambda的源码，在lambda函数updateFunctionCode调用后面加入await sleep(3000)延迟即可解决，还有一种方法也是推荐的方法就是在同样位置，通过调用getFunction函数获取lambda函数的最新状态，然后等待状态变为成功再执行updateFunctionConfiguration函数修改lambda配置
直接使用我已发布的修改好的组件 shaoyun/lambda， 修改s.yaml的component为shaoyun/lambda
此BUG更新的时候100%必现，建议官方修复

authors: anycodes shaoyun

repo: Serverless-Devs/Serverless-Devs


text:
remove name selection from landing page

as a rates rebate applicant i don't want anyone to know who owns the property because it could expose my sensitive details

Is that really why we don't want to show that? It's public information.
On Fri, 4 May 2018 at 15:30 ssibbehh notifications@github.com wrote:

as a rates rebate applicant i don't want anyone to know who owns the
property because it could expose my sensitive details
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ServiceInnovationLab/pancake-frontend/issues/103, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHFNCkXcIig68WsB7KUn9FVAvK4-xD1Fks5tu8tKgaJpZM4TyEal
.

Initial testingyshows it feels creepy. We also aren't handling the situation where the ratepayer has been marked private (there are some in this situation)

Fixed

authors: Br3nda leedowsett ssibbehh

repo: ServiceInnovationLab/pancake-frontend


text:
Fix pipeline confusion in class overlap

Resolve #303
Description:

Pipeline confusion in class overlap wasn't working for 2 reasons:

A change was done in the confusion matrix module where classes were now re-ordered by "cluster", by default. The class overlap route code counts on the confusion matrix being ordered by the dataset class order. However, it turns out that this bug was hidden by this second bug.
There was a typo in the module options sent to the confusion matrix. cf_normalized=False instead of cf_normalize=False. This resulted in the confusion matrix being normalized, and so all pipeline confusion scores were 0 or 100% (because the normalized confusion was converted to an int).

I added a new issue in our repo so we can be more robust to that second bug: #305
Checklist:
You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

[x] ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
[x] PRE-COMMIT. You ran pre-commit on all commits, or else, you
ran pre-commit run --all-files at the end.
[x] USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
our users.
[x] DEV CHANGES.

Update the documentation if this PR changes how to develop/launch on the app.
Update the README files and our wiki for any big design decisions, if relevant.
Add unit tests, docstrings, typing and comments for complex sections.

Oh, dear...thank you for noticing and taking care of this!

authors: gabegma lindsaydbrin

repo: ServiceNow/azimuth


text:
Retrieve Prediction Probabilities From Output

Hi, how can I retrieve the probability values associated with a prediction from the model? For example, when predicting a query, I would like to get the probability of selecting each token that the model uses when performing beam search. I tried looking into Hugging Face's built-ins, but they failed.
I added in the arguments, output_scores=True in line 134 in seq2seq/serve_seq2seq.py, but this does not work. When I added the arguments output_scores=True and return_dict_in_generate=True, it throws the following error:
File "/app/seq2seq/utils/pipeline.py", line 78, in __call__
    result = super().__call__(inputs, *args, **kwargs)
  File "/opt/conda/lib/python3.7/site-packages/transformers/pipelines/text2text_generation.py", line 138, in __call__
    result = super().__call__(*args, **kwargs)
  File "/opt/conda/lib/python3.7/site-packages/transformers/pipelines/base.py", line 1027, in __call__
    return self.run_single(inputs, preprocess_params, forward_params, postprocess_params)
  File "/opt/conda/lib/python3.7/site-packages/transformers/pipelines/base.py", line 1034, in run_single
    model_outputs = self.forward(model_inputs, **forward_params)
  File "/opt/conda/lib/python3.7/site-packages/transformers/pipelines/base.py", line 944, in forward
    model_outputs = self._forward(model_inputs, **forward_params)
  File "/opt/conda/lib/python3.7/site-packages/transformers/pipelines/text2text_generation.py", line 161, in _forward
    out_b = output_ids.shape[0]
AttributeError: 'BeamSearchEncoderDecoderOutput' object has no attribute 'shape'

Hi @adamkhakhar, please ask this question upstream on the hf issue board.

authors: adamkhakhar tscholak

repo: ServiceNow/picard


text:
Aaa

Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster

As far I can see, these changes require to:

login to the image repository first
then run the tests using the namespace and repository name

Yes.

If we use quay.io, the repository must be public before using it (and this is a manual step).

Yes, the step is designed to be independent on registry provider, so any configuration for quay has to be done in advance before the tests are executed.

I think this might be problematic when running the tests in a CI pipeline (as multiple tests might be pushing to the same repository name).

I would expect that registry should be able to handle pushing of several images into same repository (while images differ in image tag). Though I haven't tried that yet.

What about to deploy a Docker repository inside of the Openshift test namespace?

For OpenShift that may be an option. For Kubernetes it can be a bit tricky as we have to add those registries to insecure registry list for docker in the node itself. May be worth investigating (and improving the implementation in future).

@Sgitario Comments addressed

repo: Sgitario/kogito-cloud-operator


text:
Help pls

Describe your problem here.

Its my frist nod, i need help
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

From what I see in the error, There is a problem in the instrumental. You may need to change the Instrumental with a newer version of the song.

repo: ShadowMario/FNF-PsychEngine


text:
Add pages for the writing page

Similar to https://github.com/ShaneBonkowski/ShanesGames/issues/231

May be able to wait until I have many more wirings before this is needed.
Render the first 10 writings or so, and then have page buttons on the bottom of count that equal int(total writings / 10)
Clicking a page will re-render the whole screen similar to how search works, with the buttons 1 - 10, or 11 - 20 etc.
Make this play niceley with search, to where I can pass in a filtered writings list and itll work the same way. Displaying the first 10 search results that match, then 11-20 etc. for pages 2 and so on

Closing because now art, writing, and games are going to be shared. See this ticket https://github.com/ShaneBonkowski/ShanesGames/issues/60

repo: ShaneBonkowski/ShanesGames


text:
Support for multiple AD Management Agents

Added the ability to specify the name of the AD Management Agent you want to run. By default, only the AD Management Agent that was created by this module (named "ADMA") can be started, but you may have multiple ones - e.g. in a multi-forest scenario. This small change does not alter the creation process of the default AD Management Agent, it only adds a parameter to the SharePointSync function to be able to start other Management Agents with a different name. When no name is specified, the original "ADMA" management agent will be run.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: thomasvochten sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Submitted my PR from the wrong branch of course, will submit another one

authors: msftclas thomasvochten

repo: SharePoint/PnP-Tools


text:
New command: get tenant app catalog URL

Get URL of the tenant app catalog

command: spo tenant appcatalog get
requires connection to the tenant admin site

For more information see: https://github.com/SharePoint/PnP-PowerShell/blob/master/Commands/Admin/GetTenantAppCatalogUrl.cs

Can I start looking into this?

Absolutely! Appreciate your help!

authors: kshsbala waldekmastykarz


text:
Kept on getting error message for @types/sharepoint

Category

[x] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Just changed my PC, installed the latest generator-sharepoint, performed a git clone on my repository and on some projects this error messages kept on coming up when I'm trying to build(gulp serve) the project and I'm not sure on what's causing this issue. The project is on GA release. I tried to upgrade it to June release and the error still persists. Typescript version on tslint is 2.1.6. Any idea on what's going on?
Update:
I have managed to fix it by checking the version of @types/sharepoint on my old computer (2013.1.6) and the current version is (2013.1.9), I rolled back the version to 2013.1.6 and it works fine on my GA release project. I'm not exactly sure whether this way of changing to old version is actually right, but it works.
[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3604,17): error TS1005: ',' expected.

[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3823,17): error TS1005: ',' expected.

[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3825,19): error TS1005: ',' expected.

[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3827,21): error TS1005: ',' expected.
[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3829,18): error TS1005: ',' expected.
[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3896,21): error TS1005: ',' expected.
[09:00:22] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3944,31): error TS1005: ',' expected.
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(70,42): error TS2314: Generic type 'ListItem<T, any>' requires 2 type
argument(s).

[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3098,31): error TS2314: Generic type 'ListItem<T, any>' requires 2 typ
e argument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3362,33): error TS2314: Generic type 'ListItem<T, any>' requires 2 typ
e argument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3468,33): error TS2314: Generic type 'ListItem<T, any>' requires 2 typ
e argument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3604,19): error TS2368: Type parameter name cannot be 'any'
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3606,33): error TS2314: Generic type 'ListItem<T, any>' requires 2 typ
e argument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3816,39): error TS2314: Generic type 'ListItemCollection<T, any>' requ
ires 2 type argument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3818,61): error TS2314: Generic type 'ListItem<T, any>' requires 2 typ
e argument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3821,59): error TS2314: Generic type 'List<T, any>' requires 2 type ar
gument(s).
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3823,19): error TS2368: Type parameter name cannot be 'any'
[09:00:24] Error - typescript - node_modules\@types\sharepoint\index.d.ts(3823,40): error TS2314: Generic type 'List<T, any>' requires 2 type ar
gument(s).
```

Same for me...

Sounds like the latest version of @types/sharepoint is expecting a newer version of the TypeScript compiler. We will be releasing a new drop of the build tools supporting a newer version of the compiler soon, but for now the best workaround is to stay on the older (2013.1.6) version.

Encountered same issue.
Fix:
If you already have installed the latest version, uninstall the version from the solution:
npm uninstall @types/sharepoint
Use the last working version (2013.1.6):
npm install @types/sharepoint@2013.1.6 --save-dev

I have encountered similar issue. As per your suggestion used 2013.1.6 version.
But now in browser I get error "ERROR ReferenceError: SP is not defined"
I have defined types in tsconfig.json

@nigadeshshank are you loading SP JSOM yourself? While it is present on classic SharePoint pages, it's not available by default on modern pages and in the workbench and you have to load it yourself before you can use it.

@waldekmastykarz  ohh ok.. Thanks. This makes sense. But yesterday I was going through MS documentation and it seems JSOM is not on their agenda anymore but REST is. So I will try to move away from JSOM anyway. But let me give a try for it. Thanks again

REST is definitely the recommended approach as newer APIs are not included in JSOM.

hey any update with this? we're still having to revert our version.

Which version of the SharePoint Framework are you using @kmartindale?

authors: AnupamRanku iclanton jonathanhotono kmartindale nigadeshshank stijnbrouwers waldekmastykarz

repo: SharePoint/sp-dev-docs


text:
Dashboard for Viva Connections web part throws a 'Can't get this dashboard URL' error

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
other (enter in the "Additional environment details" area below)
Developer environment
No response
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version:  Chrome Version 81.0.4044.113 (Official Build) (64-bit)
SPFx version: N/A  (OOTB Dashboard for Viva Connections web part)
Node.js version: N/A

Describe the bug / error
The Dashboard for Viva Connections web part is throwing an error:
ERROR:
Can't get this Dashboard URL. It may not be set up yet, or it may have been deleted.
CALL STACK:
Error: Can't get this Dashboard URL. It may not be set up yet, or it may have been deleted.
at https://modernb.akamai.odsp.cdn.office.net/files/sp-client/dashboard-webpart_en-us_0a0976b5cc110e3b25de.js:1:15363

The site was registered as the home site and the Setup Viva Connections option was used to create the Dashboard.aspx page.  Cards were added to the page and the page was published.  Upon adding the Dashboard for Viva Connections web part to the vertical section in the home page the error was thrown.
Setting a different site in the tenant as the home site and setting up Viva Connections on that site results in the same error for a page on that site, but then causes the dashboard web part to work on the original site (non-home).
Note there is a vanity URL on this tenant, in this case team.cl*.com instead of cl****.sharepoint.com.
Steps to reproduce

Register the site as the home site.
Setup Viva Connections.
Add cards to the Dashboard.aspx page and publish.
Add the Dashboard for Viva Connections web part to a page on the home site.

Expected behavior
The Dashboard web part displays the ACEs on the page.

thx @Annie-Johnson - this is indeed most likely related on the vanity URL model which is quite rare and it might be that there's a regression on that side. Will start internal discussions on this right away, but there's no direct SLA for this channel.
As this is oob feature and not directly related on the development, would recommend opening up also a support case either using admin portal or with premier support (best option if available). Using official support channels have agreed SLA which will help on the resolution speed.

Thanks @VesaJuvonen, I've opened a premier support case.  I appreciate your attention to this!

Thanks @Annie-Johnson - given that this is a special case with the vanity URLs, let me close it from here to avoid any confusion in general. As you have the premier support case open, we'll certainly get this sorted out for your tenant using official support channels.

authors: Annie-Johnson VesaJuvonen


text:
Migrate CSS change from wiki to docs

Category

[x] Content fix
[ ] New article

Related issues
n/a
What's in this Pull Request?

added details from this wiki entry to the docs
added callout to SPFx v1.8.2 release notes

Docs Build status updates of commit 9e2d9f8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/spfx/office-ui-fabric-integration.md
:white_check_mark:Succeeded
View

docs/spfx/release-1.8.2.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

authors: VesaJuvonen andrewconnell


text:
[Bulk] Validation: validation fixes JM 6/10

Category

[x] Content fix
[ ] New article

Related Issues
no issue number - part of the Validation cleanup efforts.
What's in this Pull Request?
This PR fixes 30 issues across 21 files.

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

File
Status
Preview URL
Details

docs/schema/officeitemproperty-element.md
:warning:Warning
View
Details

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md
:warning:Warning
View
Details

docs/schema/option-element-workflowactions.md
:warning:Warning
View
Details

docs/schema/option-element-workflowinfo.md
:warning:Warning
View
Details

docs/schema/other-sharepoint-schemas.md
:warning:Warning
View
Details

docs/schema/outlookfolder-element.md
:warning:Warning
View
Details

docs/schema/outlookitemcustomizations-element.md
:warning:Warning
View
Details

docs/schema/officeitemproperty-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowactions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowinfo.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/other-sharepoint-schemas.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookfolder-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookitemcustomizations-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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

Global effort to fix build validation errors
@VesaJuvonen
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!

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

File
Status
Preview URL
Details

docs/schema/officeitemproperty-element.md
:warning:Warning
View
Details

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md
:warning:Warning
View
Details

docs/schema/option-element-workflowactions.md
:warning:Warning
View
Details

docs/schema/option-element-workflowinfo.md
:warning:Warning
View
Details

docs/schema/other-sharepoint-schemas.md
:warning:Warning
View
Details

docs/schema/outlookfolder-element.md
:warning:Warning
View
Details

docs/schema/outlookitemcustomizations-element.md
:warning:Warning
View
Details

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfo-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/officeitemproperty-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowactions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowinfo.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/other-sharepoint-schemas.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookfolder-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookitemcustomizations-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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 713c515:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/officeitemproperty-element.md
:warning:Warning
View
Details

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md
:warning:Warning
View
Details

docs/schema/option-element-workflowactions.md
:warning:Warning
View
Details

docs/schema/option-element-workflowinfo.md
:warning:Warning
View
Details

docs/schema/other-sharepoint-schemas.md
:warning:Warning
View
Details

docs/schema/outlookfolder-element.md
:warning:Warning
View
Details

docs/schema/outlookitemcustomizations-element.md
:warning:Warning
View
Details

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfo-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/officeitemproperty-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowactions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowinfo.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/other-sharepoint-schemas.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookfolder-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookitemcustomizations-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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 41683b9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/officeitemproperty-element.md
:warning:Warning
View
Details

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md
:warning:Warning
View
Details

docs/schema/option-element-workflowactions.md
:warning:Warning
View
Details

docs/schema/option-element-workflowinfo.md
:warning:Warning
View
Details

docs/schema/other-sharepoint-schemas.md
:warning:Warning
View
Details

docs/schema/outlookfolder-element.md
:warning:Warning
View
Details

docs/schema/outlookitemcustomizations-element.md
:warning:Warning
View
Details

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfo-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/officeitemproperty-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowactions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowinfo.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/other-sharepoint-schemas.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookfolder-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookitemcustomizations-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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

Global effort to fix build validation errors
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!

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

File
Status
Preview URL
Details

docs/schema/officeitemproperty-element.md
:warning:Warning
View
Details

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md
:warning:Warning
View
Details

docs/schema/option-element-workflowactions.md
:warning:Warning
View
Details

docs/schema/option-element-workflowinfo.md
:warning:Warning
View
Details

docs/schema/other-sharepoint-schemas.md
:warning:Warning
View
Details

docs/schema/outlookfolder-element.md
:warning:Warning
View
Details

docs/schema/outlookitemcustomizations-element.md
:warning:Warning
View
Details

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfo-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md
:warning:Warning
View
Details

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/officeitemproperty-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/optimizeforfrequentuse-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-fieldbind-elementruledesignertype-complextypeaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowactions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/option-element-workflowinfo.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/other-sharepoint-schemas.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookfolder-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/outlookitemcustomizations-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfo-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrideinfocollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/overrides-element-searchschemaconfigurationsettings-complextypesps15xsdsearchset.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/owner-element-source-complextypesps15xsdsearchset1.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedclientcallbackrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrecurrencerowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/pagedrowset-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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


text:
Update build-for-teams-me-experience.md

The article "Embedding modern SharePoint pages in Microsoft Teams as personal apps" (https://learn.microsoft.com/en-us/sharepoint/dev/features/embed-pages-to-teams?WT.mc_id=m365-9762-wmastyka) mentions Viva Connections model for the supported experience. Important notice can be useful for the cx to understand recommended model.
Category

[ ] Content fix
[ ] New article
[x] Example checked item (delete this line)

DELETE THIS LINE BEFORE SUBMITTING | For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.

Related issues

fixes #issuenumber
partially #issuenumber
mentioned in #issuenumber

DELETE THIS LINE BEFORE SUBMITTING | If this fixes (aka: closes) or references an issue, please reference it here. This helps maintaining the issue list as it will (1) link the PR to the issue & (2) automatically close the issue when this PR is merged in.

What's in this Pull Request?

DELETE THIS LINE BEFORE SUBMITTING | Please describe the changes in this PR. Sample description or details around bugs which are being fixed.

Submission guidelines

!!IMPORTANT!! - All submissions must complete the baseline sections included in this template. Ignoring or deleting this template may result in closing the issue with the label type:incomplete-submission.
Follow our guidance on How To Create Good Pull Requests.
Target the main branch of this repo.
When changing a page, ensure you update the ms.date front matter wih the current date in the format MM/DD/YYYY.
Review all build checks and address the automated errors, warnings, and suggestions.
NOTE: The live site is based on the live branch. Site owners periodically refresh live branch from the main branch so merged PRs won't immediately appear on the live site. Please be patient to see your changes appear on the live site.

DELETE THIS SECTION BEFORE SUBMITTING

Hey @sasaito, can you sign the CLA? Good changes, but we can't merge them until the contributor signs the CLA. More details here: https://github.com/SharePoint/sp-dev-docs/pull/9878#issuecomment-2302612634

@microsoft-github-policy-service agree company="Microsoft"

authors: andrewconnell sasaito


text:
SharePoint rendering blank page after deploying app customizer

Category

[ ] Question
[x ] Bug
[] Enhancement

Expected or Desired Behavior
Thanks for the New Sample - js-application-intranet-searchbox, this works as expected, however in some cases it gives the following issue
Observed Behavior
Thanks for this sample, it works perfectly fine. However, after adding this extension, intermittently we are getting blank page loads. On removing the externsion, the pages load correctly. Not sure what we are missing here. I'm sharing the http watch logs and console errors as well. Any help is much appreciated,

Any idea what could be the issue here
Thanks for your contribution! Sharing is caring.

Hi @manoj2784 ,
could you check if new version added by @PrasadKasireddy fixed your issue?

repo: SharePoint/sp-dev-fx-extensions


text:
New sample - Command - Mail current view as image

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
NA

What's in this Pull Request?

This PR contains a sample for a list view command set which will send an email of the current list view (filtered or normal) as an image. Example use case - best used in combination with list view formatting i.e. create cool view formatting and mail them as an image to external users.

The sample also has ability to share the image with internal users. If the internal users have access to the list then the sample gives an option to send a link to the view instead of sending the image.

Sharing is caring

Thx Anoop, also a great blog post on this one. Would you be interested in doing a live demon this in our community calls?

Thank you @VesaJuvonen . I am interested in doing a demo of this sample. Would it be on the 22nd?

It could be already this week in 22nd of then next one at 6th of December. Depending on your availability and preference.

Thank you @VesaJuvonen I will do the demo of this on 6th December as I need to get a couple of things ready for this sample.
I can do the demo of Convert to PDF and Copy classic link on 22nd if there is a slot available?

Hi @VesaJuvonen Just wanted to know if a slot is still available on 6th of December to do a demo of this extension?

authors: VesaJuvonen anoopt


text:
🛑 uptime-render is down

In 55c0ace, uptime-render (https://bot-pt3a.onrender.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: uptime-render is back up in bc7bfb2 after 11 minutes.

repo: ShaunHigh/upptime


text:
Recommend defining CompatiblePSEditions

The module manifest has a PowerShell requirement. If this is true, I would also recommend setting CompatiblePSEditions = 'Core'" in the manifest. I know that's the first place I look when checking for compatibility. The module name should be a good indication, but it never hurts to be thorough.

Thanks for the recommendation Jeff. That psd1 format has so many options.
It means a lot to know you've taken a peek at my code, thanks for all the work you do in the powershell space (and for all the QotD content in my twitter feed 😆)

authors: ShaunLawrie jdhitsolutions

repo: ShaunLawrie/PwshSpectreConsole


text:
Property 'book_new' does not exist on type 'IUtils'.

Hello,
When I try to create a new workbook it cannot find 'book_new' (Property 'book_new' does not exist on type 'IUtils')
The function declaration appears in index.d.ts but is not exported in the utils object from xlsx.js
Is it possible to get access in order to manually create a new work book?
Thanks in advance

@claudiadonea4resilient try to manually install the latest version of xlsx
npm i xlsx@0.11.3 --save
if you fetch the lib without the version it currently installs v0.8.*

@claudiadonea4resilient IUtils is not part of the official definitions.
You probably have a copy of ts-xlsx or @types/xlsx hanging around -- try removing them if you have them installed and install xlsx directly.

Thank you, it works just by installing xlsx@0.11.3

repo: SheetJS/js-xlsx


text:
0.17.5 to 0.18.2 invalid array length issue during writeFile

Hi,
just had the time to test 0.18.2 and in runs into a "Range Error: Invalid array length" issue when doing a "XLSX.writeFile(wb, args.fileName)" on a workbook which perfectly works fine with 0.17.5 (we're talking about one sheet with 25000 rows * 186 columns). Replacing xlsx.full.min.js with the 0.17.5 version and it is running and saving fine. 0.18.2 creates the problem.
Only had a quick look at the minimized code (sorry): The error is happening in xlsx.full.min.js at pos 9:22755 (corresponds to function z(e){var r=new Array(e.length);for(var t=0;t<e.length;++t)r[t]=String.fromCharCode(e[t]);return r.join("")} This is most likely the "a2s" function
....so maybe another unicode issue? Would be great if you can check it. In the meantime I try to do more tests on my side checking which data is actually used there.
Small update: Use xlsx.js and it is indeed the a2s(o) function (line 2124). The o.length is in my crashing case 181579121 but when reaching already i=11184812 and setting out[i] to whatever leads to the invalid array length error. Call stack comes from write, write_zip_denouement, write_zip_type....
Using Win11 with Edge 98.0.1108.62 by the way

The function that actually performs the download mantras is expecting a binary string.  That doesn't make sense now that the zip writer builds a Uint8Array by default (the writeFile path and the array / buffer output types now convert from Uint8Array to binary string and back).  This also applies to Deno, since Deno.writeFileSync only operates on Uint8Array
The following patch should work, feel free to submit a PR:
diff --git a/bits/88_write.js b/bits/88_write.js
@@ -45,14 +45,15 @@ function write_zip_typeXLSX(wb/*:Workbook*/, opts/*:?WriteOpts*/)/*:any*/ {
 }
 function write_zip_denouement(z/*:any*/, o/*:?WriteOpts*/)/*:any*/ {
        var oopts = {};
+       var ftype = has_buf ? "nodebuffer" : (typeof Uint8Array !== "undefined" ? "array" : "string");
        if(o.compression) oopts.compression = 'DEFLATE';
-       if(o.password) oopts.type = has_buf ? "nodebuffer" : "string";
+       if(o.password) oopts.type = ftype;
        else switch(o.type) {
                case "base64": oopts.type = "base64"; break;
                case "binary": oopts.type = "string"; break;
                case "string": throw new Error("'string' output type invalid for '" + o.bookType + "' files");
                case "buffer":
-               case "file": oopts.type = has_buf ? "nodebuffer" : "string"; break;
+               case "file": oopts.type = ftype; break;
                default: throw new Error("Unrecognized type " + o.type);
        }
        var out = z.FullPaths ? CFB.write(z, {fileType:"zip", type: /*::(*/{"nodebuffer": "buffer", "string": "binary"}/*:: :any)*/[oopts.type] || oopts.type, compression: !!o.compression}) : z.generate(oopts);
diff --git a/bits/19_fsutils.js b/bits/19_fsutils.js
@@ -13,7 +13,7 @@ function write_dl(fname/*:string*/, payload/*:any*/, enc/*:?string*/) {
        if(typeof _fs !== 'undefined' && _fs.writeFileSync) return enc ? _fs.writeFileSync(fname, payload, enc) : _fs.writeFileSync(fname, payload);
        if(typeof Deno !== 'undefined') {
                /* in this spot, it's safe to assume typed arrays and TextEncoder/TextDecoder exist */
-               if(enc) switch(enc) {
+               if(enc && typeof payload == "string") switch(enc) {
                        case "utf8": payload = new TextEncoder(enc).encode(payload); break;
                        case "binary": payload = s2ab(payload); break;
                        /* TODO: binary equivalent */
diff --git a/misc/19_mjsfs.js b/misc/19_mjsfs.js
@@ -14,7 +14,7 @@ function write_dl(fname/*:string*/, payload/*:any*/, enc/*:?string*/) {
        if(typeof _fs !== 'undefined' && _fs.writeFileSync) return enc ? _fs.writeFileSync(fname, payload, enc) : _fs.writeFileSync(fname, payload);
        if(typeof Deno !== 'undefined') {
                /* in this spot, it's safe to assume typed arrays and TextEncoder/TextDecoder exist */
-               if(enc) switch(enc) {
+               if(enc && typeof payload == "string") switch(enc) {
                        case "utf8": payload = new TextEncoder(enc).encode(payload); break;
                        case "binary": payload = s2ab(payload); break;
                        /* TODO: binary equivalent */

Actually generating the final zip is about twice as fast now in the realm of 25K rows x 200 columns.  In local tests we were able to push ~80K rows x 200 columns of numbers and small text strings before hitting the invalid string length issue in the XML generation.

authors: RScherzer SheetJSDev

repo: SheetJS/sheetjs


text:
matplotlib dependency in setup.py

Starting with v1.13.0, setup.py, specifies matplotlib==3.3.4 as a dependency for the plotting extra.  This seems like an old version of matplotlib to be requiring for a newer version of this package.  Also, according to issue #1069, it looks like this package should be supporting very new versions of matplotlib.  Is the version in setup.py actually the correct dependency?

Hi @DManowitz
yeah it should be fixed as off #1070 but that change is not available as a release just yet.
I am a bit short on time and still haven't got everything dialed for the next patch #1071.
I will try to find some time. If you cannot wait, in the meanwhile, you can use GPy's develop branch as a git-dependency.
Btw. I'm grateful for anybody willing to pick up issues and make contributions.

I will close this issue as it is already adressed as off #1069 . Feel free to give #1071 a thumbs up to increase to show intersted in a patch. No guarantee that this speeds up the process but maybe it gives me some extra motivation :)

authors: DManowitz MartinBubel

repo: SheffieldML/GPy

license_source: bigquery


text:
A question about Semisupervised_TU in pre_training

main.py 320
run_exp_benchmark()
main.py 278 run_exp_benchmark
run_exp_lib(create_n_filter_triples(datasets, feat_strs, nets,
main.py 183 run_exp_lib
cross_validation_with_val_set(
train_eval.py 115 cross_validation_with_val_set
train_loss, _ = train(
train_eval.py 234 train
out1 = model.forward_cl(data1)
res_gcn.py 173 forward_cl
return self.forward_BNConvReLU_cl(x, edge_index, batch, xg)
res_gcn.py 180 forward_BNConvReLU_cl
x_ = F.relu(conv(x_, edge_index))
module.py 1186 _call_impl
return forward_call(*input, **kwargs)
gcn_conv.py 103 forward
edge_index, norm = GCNConv.norm(
gcn_conv.py 90 norm
deg = scatter_add(edge_weight, row, dim=0, dim_size=num_nodes)
scatter.py 27 scatter_add
return scatter_sum(src, index, dim, out, dim_size)
scatter.py 9 scatter_sum
index = broadcast(index, src, dim)
utils.py 12 broadcast
src = src.expand(other.size())
RuntimeError:
expand(torch.cuda.LongTensor{[2, 12108]}, size=[12108]): the number of sizes provided (1) must be greater or equal to the number of dimensions in the tensor (2)
There is a error in scatter_add() function,this error remain that the size of src tensor is not euqal to the size of index tensor.I have tried many times but  it  is still not work.Could you give a solution about this question? Thanks

Hi @ytpjh,
The most possible reason for this issue would be the package version. Please follow https://github.com/Shen-Lab/GraphCL/tree/master/semisupervised_TU#dependencies to set up the environment.
If want to directly deal with this error, I would suggest starting from
res_gcn.py 180 forward_BNConvReLU_cl
x_ = F.relu(conv(x_, edge_index))
Expecially, print out x_.shape, edge_index.max(). It seems that edge_index.max() > x_.shape[0] which means you are trying to do message passing on non-existing nodes.

repo: Shen-Lab/GraphCL


text:
Tool takes a very long time

Hello,
i'm trying to use your tool to source index a very basic project.
So, i update the environment variable set localGitRepo=C:\Git\test
and then I run the actual command
C:\Users\user101\Desktop\sourceIndex_forGit-master\gitIndex.cmd "C:\Git\test" "C:\Git\test\x64\Release"
But then, the first line is rem call gitIndex.cmd "" ""
followed by several errors:

find: '/i': No such file or directory
find: '/c/$Recycle.Bin/S-1-5-18': Permission denied
f>ind: '/c/$Recycle.Bin/S-1-5-21-1035048477-112209276-915462001-1000': Permission denied                                 find: >'/c/$Recycle.Bin/S-1-5-21-1035048477-112209276-915462001-1001': Permission denied
find: '/c/$Recycle.Bin/S-1-5-21-1035048477-112209276-915462001-500': Permission denied
find: '/c/$Recycle.Bin/S-1-5-21-1457439002-884234708-2329215277-500': Permission denied
find: '/c/$Recycle.Bin/S-1-5-21-2500424245-2055191009-4082716798-4653': Permission denied
find: '/c/PerfLogs/Admin': Permission denied

I have also tried to set LocalProjectSrcPath and pdbFilePathOrPdbFolderPath, but I still have the same errors

Hi ,
all those variables are used by your debugger.
the source indexing procedure needn't those variables.
for the source index procedure, you only need to confirm userLocalPathConfig.bat configuration is correct with your current environment.
the line : rem call gitIndex.cmd "%LocalProjectSrcPath%" "%pdbFilePathOrPdbFolderPath%"
it is only a usage example comments.
you can refer to the usage example in test folder.
or in your visual studio project : solution explorer -> right click -> Properties -> Build Events -> Post-Build Event :
Command Line : call C:\myScript\gitIndex.cmd "$(projectDir)" "$(targetdir)$(targetname).pdb"
as a basic test project, you can package them and send it to me (xlshen2002@gamil.com) , I will check it.

Hi ,
all those variables are used by your debugger.
the source indexing procedure needn't those variables.
for the source index procedure, you only need to confirm userLocalPathConfig.bat configuration is correct with your current environment.
the line : rem call gitIndex.cmd "%LocalProjectSrcPath%" "%pdbFilePathOrPdbFolderPath%"
it is only a usage example comments.
you can refer to the usage example in test folder.
or in your visual studio project : solution explorer -> right click -> Properties -> Build Events -> Post-Build Event :
Command Line : call C:\myScript\gitIndex.cmd "$(projectDir)" "$(targetdir)$(targetname).pdb"
as a basic test project, you can package them and send it to me (xlshen2002@gamil.com) , I will check it.

if it works, but it takes a very long time, it is caused by the git version mechanism.
but this implement is a huge source index procedure -- it is slow when source indexing, but much faster when the debugger is using them.
if you like a fast light source index procedure, you can try  :
https://github.com/ShenXiaolong1976/sourceIndexLight_forGit
it is faster when source indexing, but much slower when the debugger is using them because you have to sync all repo files with a special git version which embed into the PDB file.

if it works, but it takes a very long time, it is caused by the git version mechanism.
but this implement is a huge source index procedure -- it is slow when source indexing, but much faster when the debugger is using them.
if you like a fast light source index procedure, you can try  :
https://github.com/ShenXiaolong1976/sourceIndexLight_forGit
it is faster when source indexing, but much slower when the debugger is using them because you have to sync all repo files with a special git version which embed into the PDB file.

index slower , debug faster   -- use :  https://github.com/ShenXiaolong1976/sourceIndex_forGit
index faster  , debug slower  -- use :  https://github.com/ShenXiaolong1976/sourceIndexLight_forGit


text:
8184.11 DEV Add message queue page

Shippable/pm#8184

add message queue page. clicking on message queue button should open this

check if message queue is initialized and installed or not
if not, show the button to initialize message queue
clicking button should call POST /msg route with no params

closing in lieu of new pm.

authors: a-murphy stephanielingwood

repo: Shippable/admiral


text:
[BFCL] How to Evaluate the Spark Giant Model:

Describe the issue
How to evaluate large models, if the URL and API are known, which code needs to be modified, what code needs to be added, and what the logic should be like.
thanks

Hi, Please take a look at this section: https://github.com/ShishirPatil/gorilla/tree/main/berkeley-function-call-leaderboard#contributing
Let me know if you have more questions.

authors: HuanzhiMao lonelysheeep

repo: ShishirPatil/gorilla


text:
Minor typo in contrib.rst

If you have a problem using apparate or see a possible impovement, open an issue in the GitHub issue tracker. Please be as specific as you can.

"impovement"

fixed in PR#20

authors: gsganden htorrence

repo: ShopRunner/apparate


text:
Connect UI extensions dev console with cli

WHY are these changes introduced?
To develop the extensions dev console it would be handy if:

you could connect the UI with real data provided by the CLI.
You could work with vite's dev server so that you have hot module reloading.

In this PR we make these things a little easier.
WHAT is this pull request doing?

Change import.meta.env.VITE_WEBSOCKET_HOST to VITE_CONNECTION_URL
Parse the env var so that we end up with the correct URL, e.g: wss://ngrok.url/extensions
Add a README with steps on how to run the dev console
Replace the start command wth a dev command to run Vite's dev server.  Not sure why we had a start command ?

How to test your changes?

Read the readme.
Follow the steps in the readme.

Post-release steps
None
Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[x] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

Read the readme.
Follow the steps in the readme.

"readme" -- it's more than just a clever name 😁

authors: byrichardpowell dmhenry

repo: Shopify/cli


text:
Use type when using buffered: true

Description
Fixes #1090
In Chrome's DevTools console, we're getting a bunch of these errors:
The PerformanceObserver does not support buffered flag with the entryTypes argument.

We're using a single type, and wrapping it in an array to pass to entryTypes while we have buffered: true. We should just use the type property.
https://developer.mozilla.org/en-US/docs/Web/API/PerformanceObserver/observe

entryTypes: An array of DOMString objects, each specifying one performance entry type to observe. May not be used together with the "type" or "buffered" options.
type: A single DOMString specifying exactly one performance entry type to observe. May not be used together with the entryTypes option.
buffered: A boolean flag to indicate whether buffered entries should be queued into the observer's buffer. Must be used only with the "type" option.

Type of change

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

Checklist

[ ] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

I'm looking forward to the follow up PR that fixes the Deprecated API for given entry type. warnings too :D

I'm looking forward to the follow up PR that fixes the Deprecated API for given entry type. warnings too :D

authors: BPScott atesgoral

repo: Shopify/quilt


text:
[WIP] Unite MessageToSend and ConsumerEvent

Start of #269.

New names: ConsumerEvent becomes ConsumerMessage and in the producer, MessageToSend becomes ProducerMessage. Once we're ready to unite it I'd like to simply call it Message, but right now that is in used internally for messages between client and broker. Can we find a newer name?

Remove encoder interface, and simply use []byte for keys and values.

Still to resolve: Metadata, and Err.

@mkobetic @Shopify/kafka
As discussed in out walkthrough of the new consumer.

Going to close this as this is outdated and I am not so sure about the approach anymore, I'll open an issue instead;

repo: Shopify/sarama