[Network] VNET gateway should support configuration of active-active gateways

This is a new feature which was also announced in Ignite last year. Please refer to the Powershell cmdlet documentation or get in touch with me.

Reference:
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershell

That’s a good place to start. If you need any help let me know.
From: Travis Prescott<EMAIL_ADDRESS>Sent: Tuesday, February 14, 2017 9:55 AM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Aanand Ramachandran<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] The command to add a virtual network gateway doesnt have an option to configure active-active gateways (#2050)
Reference:
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershellhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvpn-gateway%2Fvpn-gateway-activeactive-rm-powershell&data=02|01|aanandr%40microsoft.com|c5b8c06c99514a0e285008d45502a1e8|72f988bf86f141af91ab2d7cd011db47|1|0|636226917170631971&sdata=x9x98zZ6WccqsC%2FXEwLbjA%2F74JvTY4blGvT3PmeWJtA%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F2050%23issuecomment-279783536&data=02|01|aanandr%40microsoft.com|c5b8c06c99514a0e285008d45502a1e8|72f988bf86f141af91ab2d7cd011db47|1|0|636226917170631971&sdata=EjNd5eWbkpdNi4DqDAja%2BMYp9xzplJ7QYUhSFbCsPo8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV3chTFyc5Yyy_qShSEjrA6E3tj6mxChks5rceqCgaJpZM4L-0kg&data=02|01|aanandr%40microsoft.com|c5b8c06c99514a0e285008d45502a1e8|72f988bf86f141af91ab2d7cd011db47|1|0|636226917170631971&sdata=1fylkXMeWDuxZ5sdIpNmcX%2BnA2YPIshuBIGAPZm44DE%3D&reserved=0.


Backpack readiness probe

Improve backpack readiness probe to check for /tmp/indexed which is created after a successful execution of stockpile-wrapper

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:01:39

/rerun all

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:01:48

/rerun all

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:01:59


Make Modmail Bot better

Hello. I have figured out how to make the Modmail bot better and have commands support.
Note: I can't figure out how to do a pull request properly since I can't upload files, I am doing it here in the next comment.

``py
import discord
from discord.ext import commands
intents = discord.Intents.default()
intents.message_content = True
client = discord.Client(intents=intents)
client = commands.Bot(command_prefix= commands.when_mentioned_or('>'), intents=intents)
@client.event
async def on_ready():
await client.change_presence(activity=discord.Activity(type=discord.ActivityType.watching, name="My DMs"))
print("Modmail Bot Version 2 Ready to Go")
@client.event
async def on_message(message):
if message.author == client.user:
return
if str(message.channel.type) == "private":
modmail_channel = discord.utils.get(client.get_all_channels(), name="modmail")
await modmail_channel.send(f"{str(message.author)} | {str(message.author.id)}: " + message.content)
elif str(message.channel) == "modmail" and message.content.startswith("<"):
member_object = message.mentions[0]
    index = message.content.index(" ")
    string = message.content
    mod_message = string[index:]

    await member_object.send("[" + message.author.display_name + "]" + mod_message)

await client.process_commands(message)

@client.command()
async def ping(ctx):
await ctx.send(f'PONG!\nLatency: {round(client.latency * 1000)}ms')
@client.command()
async def setupmodmail(ctx):
channel = await guild.create_text_channel('modmail')
guild = ctx.guild
channel = discord.utils.get(guild.text_channels, name="modmail")
role = discord.utils.get(guild.roles, name="@everyone")
await channel.set_permissions(role, send_messages=False, read_messages=False)
await ctx.send("The Modmail channel has been set up.")
client.run("")
``

import discord
from discord.ext import commands

intents = discord.Intents.default()
intents.message_content = True
client = discord.Client(intents=intents)
client = commands.Bot(command_prefix= commands.when_mentioned_or('>'), intents=intents)

@client.event
async def on_ready():
    await client.change_presence(activity=discord.Activity(type=discord.ActivityType.watching, name="My DMs"))
    print("Modmail Bot Version 2 Ready to Go")

@client.event
async def on_message(message):
    if message.author == client.user:
        return
    if str(message.channel.type) == "private":
        modmail_channel = discord.utils.get(client.get_all_channels(), name="modmail")
        await modmail_channel.send(f"**{str(message.author)} | {str(message.author.id)}:** " + message.content)
    elif str(message.channel) == "modmail" and message.content.startswith("<"):
        member_object = message.mentions[0]

        index = message.content.index(" ")
        string = message.content
        mod_message = string[index:]

        await member_object.send("[" + message.author.display_name + "]" + mod_message)

    await client.process_commands(message)

@client.command()
async def ping(ctx):
    await ctx.send(f'PONG!\nLatency: {round(client.latency * 1000)}ms')

@client.command()
async def setupmodmail(ctx):
    channel = await guild.create_text_channel('modmail')
    guild = ctx.guild
    channel = discord.utils.get(guild.text_channels, name="modmail")
    role = discord.utils.get(guild.roles, name="@everyone")
    await channel.set_permissions(role, send_messages=False, read_messages=False)
    await ctx.send("The Modmail channel has been set up.")

client.run("")

Thank you. I have reviewed the code and feel it is suitable to be merged to my code. I have updated the readme and it is now have the new code. Thank you.

I will close this as I assume this has been resolved


support protobuf specification version 3

This PR is primarily to support protobuf version 3 specification.

julia code generator plugin updated to interface to protoc version 3
serializer now packs primitive fields by default (decoders are required to interpret fields in both packed and unpacked form)
new api isfilled_default to distinguish fields set with deserialized data from those set with defaults (with proto3 all fields are marked as optional)
support oneof specification

new api which_oneof retruns the field set in the oneof group
setting a field in the group unsets others

support map types

maps are now generated as Julia Dict
optionally generate maps as arrays, when a compatibility flag (env JULIA_PROTOBUF_MAP_AS_ARRAY=1) is passed to protoc plugin.
decoder can interpret either type

support protobuf well known types

pre-generated and included in the package as a separate module google.protobuf
some of them have additional changes to make them compatible with Julia (e.g. working around to handle circular dependencies)
to use them, add ProtoBuf/gen to the list of includes while generating code
and refer to them as usual Julia module: using ProtoBuf; using google.protobuf

new symbols added to keyword list: Base, DataType, Any, Enum
miscellaneous optimizations, logging and test script enhancements

Will be testing this further before merging.
ref: #55 #69

Tests have passed and also works fine with the packages where I'm using this.
Will merge.


fix(versions): update Activiti/activiti-cloud-notifications-graphql versions into master

UpdateBot pushed maven dependency: org.activiti.cloud.notifications.graphql:activiti-cloud-notifications-graphql-dependencies to: 7.1.169

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.notifications.graphql:activiti-cloud-notifications-graphql-dependencies 7.1.169


Atom is causing numerous taskgated errors on macOS

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When launching Atom from the Finder (or Alfred) it will cause many taskgated errors, per second:

This causes the system to peg and the fans to turn on, which is hot and kills battery life.
Launching atom from the terminal (inside or outside of tmux) does not reproduce the issue.
Steps to Reproduce

Launch Atom from Dock
Observe numerous taskgated errors in Console.app, increased system load
Terminate Atom
Launch Atom from terminal
Observe that no excessive taskgated events are generated.

Expected behavior: Launching Atom should not cause my system to peg
Actual behavior: It pegs, many security events are generated
Reproduces how often: 100% (On my system)
Versions
$ atom --version
Atom    : 1.27.2
Electron: 1.7.15
Chrome  : 58.0.3029.110
Node    : 7.9.0

$ apm --version
apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.27.2
python 2.7.15
git 2.17.0

$ system_profiler SPSoftwareDataType
Software:

    System Software Overview:

      System Version: macOS 10.12.6 (16G1408)
      Kernel Version: Darwin 16.7.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: Thneed
      User Name: Andrew Burns (aburns)
      Secure Virtual Memory: Enabled
      System Integrity Protection: Enabled
      Time since boot: 2:34

Additional Information
I think this is related to atom/atom#13084 as I can mitigate the issue by adding the following section to my Info.plist:
<key>LSEnvironment</key>
<dict>
     <key>ATOM_DISABLE_SHELLING_OUT_FOR_ENVIRONMENT</key>
     <string>true</string>
</dict>

/usr/local/bin/zsh -ilc 'command env' does execute and returns the expected environment; however ps aux | grep 'command env' | grep -v grep does show that the task seems to hang when executed from Atom.

Thanks for the report - I see some of what you describe but not everything with Atom 1.27.2 on macOS 10.12.6.

Observe numerous taskgated errors in Console.app, increased system load

I do see the same errors in Console.app after starting Atom (it looks like about 5 errors on startup and it doesn't matter how I start it, I see the same thing from the Dock, command line, or Finder).  I also see if I open a file, another error pops up but otherwise, I don't see any more errors show up.  I also don't notice any large increase in system load in Activity Monitor.
So you see the errors continue to show up when doing nothing in Atom?  If you temporarily reset to factory defaults, does that make any difference?
https://flight-manual.atom.io/hacking-atom/sections/debugging/#reset-to-factory-defaults
Do you see this behavior with other applications?  E.g. VS Code or Slack?
Some refs based on my Google-ing since this doesn't seem to have been brought up before in Atom but has been reported in general:

https://www.google.com/search?q=taskgated+macos+error+-67062
https://www.reddit.com/r/applehelp/comments/3jfxok/what_the_heck_is_up_with_taskgated_process_on_my/
https://discussions.apple.com/thread/7705551
https://github.com/Homebrew/homebrew-core/issues/11378

@rsese Thank you for looking into this.

after starting Atom (it looks like about 5 errors on startup and it doesn't matter how I start it, I see the same thing from the Dock, command line, or Finder). I also see if I open a file, another error pops up but otherwise, I don't see any more errors show up. I also don't notice any large increase in system load in Activity Monitor.

I agree that this is normal behavior and I see that as well (when things are 'good').

So you see the errors continue to show up when doing nothing in Atom?

Correct...  it floods the Console.app and kicks the system into high load.

If you temporarily reset to factory defaults, does that make any difference?

No it does not.  I even tried nuking Atom.app and re-downloading.  Same result.

Do you see this behavior with other applications? E.g. VS Code or Slack?

I do not have VS Code.  Slack, Trello, Basecamp are all "normal".
RE: this reddit post:

My honest feeling is that it's probably some kind of process, possibly being launched at start up that gatekeeper is trying to suppress.(assuming that it isn't a bug).

that is what lead me to start looking at specific apps.
My (uneducated) guess is that atom is attempting to patch the ENV and for some reason that causes taskgated to freak out.  I can see that the zsh process doesn't exit quickly and if I manually kill it then it is respawned (and hangs).
I am also not sure exactly how long this has been happening given that I only occurred if it was first launched from the dock/alfred.
Is there any downside to disabling the env patch from the info.plist like I did?  I assume that functionality is there for a reason :)

Is there any downside to disabling the env patch from the info.plist like I did? I assume that functionality is there for a reason :)

Anything that relies on the environment variables being filled out will fail (such as many packages that launch external programs), if they don't have a separate workaround for macOS giving GUI applications a blank environment.
Atom itself is unlikely to be majorly affected though.

THIS ME ATOM.IO ATOM.IDE INGRID D EALY WHY ALL   Stalking and frauding me
On Friday, September 20, 2019, stale[bot]<EMAIL_ADDRESS>wrote:

Thanks for your contribution!
This issue has been automatically marked as stale because it has not had
recent activity. Because the Atom team treats their issues as their
backlog
https://en.wikipedia.org/wiki/Scrum_(software_development)#Product_backlog,
stale issues are closed. If you would like this issue to remain open:

Verify that you can still reproduce the issue in the latest version
of Atom
Comment that the issue is still reproducible and include:

What version of Atom you reproduced the issue on
What OS and version you reproduced the issue on
What steps you followed to reproduce the issue

Issues that are labeled as triaged will not be automatically marked as
stale.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/17517?email_source=notifications&email_token=ANCLDTXRH6SQ22VDOSVLVMTQKTW3PA5CNFSM4FFHPD6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HEDDY#issuecomment-533610895,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANCLDTWH4TGTKTXEUJL6APLQKTW3PANCNFSM4FFHPD6A
.


New version: VSCodium.VSCodium.Insiders version <IP_ADDRESS>93

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation failed with:

2023-04-03 02:02:35.021 [FAIL] Installer failed security check. Url: https://github.com/VSCodium/vscodium-insiders/releases/download/<IP_ADDRESS>93-insider/VSCodiumSetup-ia32-<IP_ADDRESS>93-insider.exe Result: 0x80004005

@wingetbot run

/azp run


[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


How would one use this library?

As in, compile it so it can be used in projects and stuff, like into an a file or a so file, if i knew more about clang and Makefiles i'd probably write the makefile myself.

Hey @dwaindibbly,
I will add CMake support in the very near future.
I have never got around to it unfortunately!
I will let you know once it is done. Should be ready in a week or so.
Created a new issue to track it: #5
In the meantime feel free to let me know any other concerns.
Thanks for your interest in my project!

Hey @dwaindibbly,
I have now converted the project to use CMake.
You should now be able to clone and build it easily!


Unable to install - "Doesn't work with Google Apps Script"

I'm wondering if I blocked something that is used used to install the app.
I tried using a different G Suite domain, and the app was installed just fine, no complaints.
Sadly, my error message is in Swedish. this little thing appears app the top of the browser window, and there is only an X-button for me to close it.
https://drive.google.com/file/d/1BrNuDpxfd3HNJBUJUm1WZp_hj9LjzeQz/view?usp=sharing
and after I click X, I get this.
https://drive.google.com/file/d/1qu3Hw9AsDLjMuLm2aTSWfGnc8CrX093E/view?usp=sharing
What could it be that I must allow, for the app to be allowed to be installed?
The Chrome extension itself I have allowed. Before that, I was immediately blocked from even trying to install.

This app isn't really a Chrome extension even though it is listed as one in the Chrome Webstore.
Please just use the "Visit Website" button, that should take you straight to the app.
I would like to update this to either be a true Chrome extension or a true web app hosted somewhere else. I'll leave this open so maybe one day it can get there.

Thanks. But, no clue what I must allow so it can be installed?
One of my domains, the one with the error, is very locked down, and without proper error messages, it's hard to figure out what can be done to allow things we want.

I know how to bypass the block now.
I have to allow this URL in my Chrome User Settings / URL Blacklist/Whielist.
<EMAIL_ADDRESS>This is because I blacklist this URL, so I am in control over which Addons/Extensions people can install.
https://accounts.google.com/signin
So, this is no longer an issue for me personally.


Web compiler inconsistencies on @anonymous js-interop constructors and their tear-offs

An @anonymous class constructor when called directly and when called via a tear-off produce different results:
import 'package:js/js.dart';

@JS()
@anonymous
class Item {
  external factory Item({int x = 99, int? y1, int? y2 = null, int z});
}

final tearoff = Item.new;

@JS('Object.entries')
external List entries(Item item);

main() {
  print('\n(x: 100, y1: 101, y2: 102, z: 103)');
  describe('direct', Item(x: 100, y1: 101, y2: 102, z: 103));
  describe('tearoff', tearoff(x: 200, y1: 201, y2: 202, z: 203));

  print('\n(y1: 301, y2: 302, z: 303)');
  describe('direct', Item(y1: 301, y2: 302, z: 303));
  describe('tearoff', tearoff(y1: 301, y2: 302, z: 303));

  print('\n(z:403)');
  describe('direct', Item(z:403));
  describe('tearoff', tearoff(z:403));

  print('\n()');
  describe('direct', Item());
  describe('tearoff', tearoff());
}

describe(String kind, Item item) {
  final map = entries(item).map((e) => e.join(': ')).join(', ');
  print('${kind.padRight(10)}$map');
}

dart2js result:
(x: 100, y1: 101, y2: 102, z: 103)
direct    x: 100, y1: 101, y2: 102, z: 103
tearoff   x: 200, y1: 201, y2: 202, z: 203

(y1: 301, y2: 302, z: 303)
direct    y1: 301, y2: 302, z: 303
tearoff   x: 99, y1: 301, y2: 302, z: 303

(z:403)
direct    z: 403
tearoff   x: 99, y1: null, y2: null, z: 403

()
direct
j1.js:1154: TypeError: null: type 'JSNull' is not a subtype of type 'int'
      throw A.wrapException(A._TypeError__TypeError$forType(object, "int"));
      ^
TypeError: null: type 'JSNull' is not a subtype of type 'int'
    at Object.wrapException (j1.js:336:17)
    at Object._asInt (j1.js:1154:15)
    at Object.Item___new_tearOff (j1.js:2296:42)
    at StaticClosure.call$0 (j1.js:3072:16)
    at main (j1.js:2312:63)
    at j1.js:3333:7
    at j1.js:3312:7
    at dartProgram (j1.js:3327:5)
    at j1.js:3335:3

The differences are a consequence of (1) lowering the constructor tear-off to a Dart static method and (2) the dart2js calling convention that the primary entry point for a method takes all arguments, and the defaulting of arguments is done elsewhere, either (a) at the call site, (b) in a stub that adds the default arguments or (c) via Function.apply. By the time we get to the body of the static method that is the constructor tear-off, there is no way to know which arguments were not provided, or the order of the provided arguments.
@anonymous constructors are a little different to other @JS() external methods. Since they are not a description of some existing JavaScript method, but a description of a desired synthesized object, we have more freedom to make optional argument default values mean something.
Questions:

Should default values be allowed? It does seem like a nice feature for a default value to be interpreted as a directive to provide the property with a default value. A missing default value would then interpreted as constructing an object without that property. y1 and y2 are therefore different in the above example.

Should we forbid tear-offs of @anonymous constructors? If tear-offs are illegal, then there is no possibility for inconsistency.

Related issues: #33395, #41375
/cc @srujzs

I know this is a very late response...
To address the inconsistency between direct calls and tear-offs, forbidding tear-offs is probably worthwhile. The confusion around the inconsistency outweighs the need for an external @anonymous factory tear-off in my opinion.
That being said, the current semantics of external @anonymous factories isn't entirely intuitive either. Like your example illustrates, the front-end currently allows non-null named params with no default values in null-safety for external factories, but we don't really do anything special with that. I don't really want us to do anything with it either, as that should be a bug. For both JS compilers, if arguments are passed at the invocation, we put them in the literal, and otherwise we don't, regardless of nullability or default values.
I like your solution to say that without a default value, we will exclude it. The check would be something like "if the value is null and there is no written initializer for this parameter, exclude it". It is, however, a little confusing why int? x and int? x = null are treated differently. This also avoids the discrepancies between direct calls and tear-offs. It does require a fair bit more code, however, since we need to check what values have the default value versus which ones don't, but if we put it in a declaration, that's okay.
I think we have an opportunity to do something new before Dart 3, and this might be a candidate. I'd only make any new semantics here only impact @staticInterop and inline classes to avoid a big breaking change.
cc @joshualitt @rileyporter


support tracing multiple statements in one line

Example: a = 0; b = 1

This is mostly handled now by running the cell through the black code formatter before tracing. This isn't ideal though, since the code referenced by traceback is formatted differently from the code in the cell.

This has been fixed for a while now that we're inserted hooks before / after statements at the ast level.


feat(next): add option to override rule options

This PR adds an option to override the test and exclude options used in the Webpack module rule created by the Next plugins (both the app dir plugin and the regular one). It does so by adding a second, optional ruleOptions arg to the plugin(s).
The override is optional and falls back to the current defaults.
I think this is useful, for example in cases where shared design-system packages are are built with Style9 and distributed as npm packages or shared inside a monorepo.
The current behavior, which excludes files inside node_modules is a good default, but can prevent the plugin from being useful in some cases, which will then require monkey-patching.
This does add some some API surface, but it designed to be optional and falls back to the defaults so shouldn't affect users that don't require the escape hatch.

Thanks!

Any chance you can cut a release and publish to npm?

Any chance you can cut a release and publish to npm?

I've been a little busy recently, and I was about to add more rule options (like include, etc.).
I will release a new version ASAP.

Opened #4, which add the ability to pass all relevant rule options in the override.
Thanks!


net/http: TestServerKeepAlivesEnabled_h2 failure with "test server has active conns"

2021-02-19T00:03:44-a1e9148/linux-386-longtest
--- FAIL: TestServerKeepAlivesEnabled_h2 (2.01s)
    serve_test.go:5699: test server has active conns
FAIL
FAIL	net/http	63.805s

See previously #21724, #18701, #18127, #18083.
CC @bradfitz @empijei @neild

Provisionally closing as fixed by CL 360854.
greplogs --dashboard -md -l -e 'test server has active conns' --since=2021-11-03


ByteBuf leak when RedissonScoredSortedSet addAll

Expected behavior
No memory leak
Actual behavior
Apparently there is a direct memory leak problem when using Redisson and RedissonScoredSortedSet
We noticed more and more memory being used by our container when started using our service in particular way, storing larger amount of objects than usual, but we couldn't see it in the heap dump.
After enabling paranoid leak detection in netty we got the exceptions:
[ERROR] 2021-07-09 13:03:39.241 [grpc-default-executor-6] ResourceLeakDetector - LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records:
#1:
	io.netty.buffer.AdvancedLeakAwareByteBuf.writeBytes(AdvancedLeakAwareByteBuf.java:616)
	io.netty.buffer.ByteBufOutputStream.write(ByteBufOutputStream.java:66)
	com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2085)
	com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1127)
	com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3911)
	com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:3177)
	org.redisson.codec.JsonJacksonCodec$1.encode(JsonJacksonCodec.java:84)
	org.redisson.command.CommandAsyncService.encode(CommandAsyncService.java:683)
	org.redisson.RedissonObject.encode(RedissonObject.java:302)
	org.redisson.RedissonScoredSortedSet.addAllAsync(RedissonScoredSortedSet.java:376)
	org.redisson.RedissonScoredSortedSet.addAll(RedissonScoredSortedSet.java:364)
	our.service.RedisClient.set(RedisClient.java:34)
(...)
Created at:
	io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:363)
	io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:187)
	io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:173)
	io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:107)
	org.redisson.codec.JsonJacksonCodec$1.encode(JsonJacksonCodec.java:81)
	org.redisson.command.CommandAsyncService.encode(CommandAsyncService.java:683)
	org.redisson.RedissonObject.encode(RedissonObject.java:302)
	org.redisson.RedissonScoredSortedSet.addAllAsync(RedissonScoredSortedSet.java:376)
	org.redisson.RedissonScoredSortedSet.addAll(RedissonScoredSortedSet.java:364)
	our.service.RedisClient.set(RedisClient.java:34)

We are pushing larger set to the cache, about 3000-4000 objects few KB each.
It keeps increasing everytime the data expires (our case 5 minutes) so most certainly set.addAll is causing that. After a couple hours the container hits the limit, but heap stays the same.
Steps to reproduce or test case
Our code is rather simple:
        RScoredSortedSet<ProviderCore> set = client.getScoredSortedSet(key);
        // Make sure the set is empty
        set.clear();

        set.addAll(orderedProviders);

        // Expire in x time units
        set.expire(5, TimeUnit.MINUTES);

The orderedProviders is a Map of 3000-4000 previously mentioned ProviderCore objects.
Redis version
5.0.7
Redisson version
3.11.6 and 3.15.6
Redisson configuration
the codec: JsonJacksonCodec
the rest default
If our use case is wrong then any help appreciated.

+1

Unable to reproduce it with last version. Here is my code:
jvm params:
-Dio.netty.leakDetection.level=paranoid

        RScoredSortedSet<String> set = redisson.getScoredSortedSet("simple");

        Map<String, Double> objects = new HashMap<>();
        for (int i = 0; i < 50000; i++) {
            objects.put(""+i, Double.valueOf(i));
        }
        assertThat(set.addAll(objects)).isEqualTo(50000);

That's not exactly the same thing.
Our objects are few KB each. Here you put just "0" - "49999" which is few bytes.

Here is updated code:
        Map<String, Double> objects = new HashMap<>();
        for (int i = 0; i < 5000; i++) {
            objects.put(""+ RandomString.make(10000), Double.valueOf(i));
        }
        assertThat(set.addAll(objects)).isEqualTo(5000);

Do you see any exceptions in logs?

No exceptions. I will try to prepare a small repository with the problem reproduced.
Also, I think it's strongly connected to the expiration. If you could please set expiry time to e.g. 1 minute and then query it every 90 seconds or so, you should notice a leak (we certainly do)

Setting expiration didn't help.
        for (int j = 0; j < 5; j++) {
            RScoredSortedSet<String> set = redisson.getScoredSortedSet("simple");
            Map<String, Double> objects = new HashMap<>();
            for (int i = 0; i < 5000; i++) {
                objects.put(""+ RandomString.make(10000), Double.valueOf(i));
            }
            assertThat(set.addAll(objects)).isEqualTo(5000);

            set.expire(1, TimeUnit.MINUTES);

            Thread.sleep(90000);
        }


call to Open GL API with no current context

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
TextureViewRender's release api is called after using the livekit's TextureViewRenderer
When the api is called at some time,
"call to Open GL API with no current context" is displayed below in the log.
When shold i call that api?
I called the api in onDestroy of activity or
onDetachedFromRecyclerVoew of recyclerView or
onViewRecycled of recyclerView
Device Info:

Device: [e.g. Google Pixel 4] galaxy s22
OS: [e.g. Android 12] android 13
LiveKit SDK version: 1.2.1

Ok


Docs Update -- Quickstart

Fill in the content of docs/source/quickstart.
I think we can largely copy the content from user/getting-started (then add more detail to the latter).

I'm getting the following error when I try the steps from the from the Getting Started page.
Successfully installed opendp-0.2.0
(venv) HMDC-beamish:asdafsfsad pdurbin$ python
Python 3.9.6 (default, Jun 29 2021, 06:20:32)
[Clang 12.0.0 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from opendp.trans import make_identity
>>> from opendp.typing import SubstituteDistance
>>>
>>> identity = make_identity(M=SubstituteDistance, T=str)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: make_identity() got an unexpected keyword argument 'T'
>>>

Here's what I'm following (the current commit is ba776a2).

unexpected keyword argument 'T'

It looks like this is supposed to be TA=str. I'll fix it in the Getting Started page and use the right form in the Quickstart.


c++ clang: Compile -Wno-null-dereference.

#536 is now breaking travis CI. The right answer is probably a change to the underlying code, but this will suppress what are, for now, spurious build failures.

Travis has passed with clang 3.9.0, which includes the suppressed warning.

Merged into master in commit ec14c17ae66caed11880031b049efb39c4934f40.
I'm trying to get a jvm + a merge from master as of ec14c17ae66caed11880031b049efb39c4934f40 building right now, but GitHub appears to be delayed in webhook requests...


implementation in angular 8

Could You make code for angular?

The code is mostly vanilla jquery js. You can create a connector to wrap this package to make it work with Angular but Angular is not currently supported, that would need to be a separate project.


Its possible to call task_for_pid() in a tweak not an application with ent?

Sorry to disturb u guys. I hooked springboard and want to get the task of an application but task_for_pid return 5(kernel/os failed). I have no idea about this.I have spent many days about this. Pls help…(a tweak only contains dylib so cannot sign with task for pid allow)

No, libraries cannot have entitlements and will run with the entitlements of the process they inject into.


Running scripts under zsh leaves user in bash

As in title. I'd expect them not to change my shell to bash :)

As in title. I'd expect them not to change my shell to bash :)

Does PR #7 fix this issue?

As in title. I'd expect them not to change my shell to bash :)

@sarna PR #7 does fix this issue?

Yup, it's fixed now :)


Fix LUN warm migration

When migrating a LUN disk from ovirt source in warm migration we need to mark the CopyDisk as completed.

and we got lower cognitive complexity!

i thought of it as well :laughing:


Impossible to remove ForeignKey relation

Describe the bug
A clear and concise description of what the bug is.
ForeignKey relations are impossible to remove. No matter what I try, I cannot remove a ForeignKey from an instance.
To Reproduce
Steps to reproduce the behavior:
import asyncio
import datetime
from typing import TYPE_CHECKING, List, Optional

import databases
import ormar
import sqlalchemy

DB_URL = databases.DatabaseURL("sqlite:///bug.sql")

database = databases.Database(DB_URL)
metadata = sqlalchemy.MetaData()

class BaseMeta(ormar.ModelMeta):
    metadata = metadata
    database = database

class Rollout(ormar.Model):
    """Represents a feature rollout."""

    class Meta(BaseMeta):
        tablename: str = "rollouts"

    id: int = ormar.Integer(autoincrement=True, primary_key=True)  # type: ignore
    name: str = ormar.String(max_length=100, unique=True)  # type: ignore
    active: bool = ormar.Boolean(default=False, nullable=False)

class Feature(ormar.Model):
    """Represents a bot feature."""

    class Meta(BaseMeta):
        tablename: str = "features"

    name: str = ormar.String(primary_key=True, max_length=50)  # type: ignore
    rollout: Optional[Rollout] = ormar.ForeignKey(Rollout, nullable=True)  # type: ignore

engine = sqlalchemy.create_engine(str(DB_URL))
metadata.drop_all(engine)
metadata.create_all(engine)

async def main():

    # set up with some prelimary data
    feature = await Feature.objects.create(name="QUICKLINKING")
    rollout = await Rollout.objects.create(name="public_fast_links")

    print(f"{feature.rollout = }")
    print(f"{rollout = }")

    # now link the rollout to the feature
    feature.rollout = rollout
    await feature.update()
    print("linked the feature to the rollout")

    print(f"{feature.rollout = }")

    # now try to unlink the rollout

    await feature.update(rollout=None)
    print("attempted to remove the rollout reference")
    print(f"{feature.rollout = }")

    # we can also use feature.rollout = None with absolutely no change
    feature.rollout = None
    print(f"{feature.rollout = }")

if __name__ == "__main__":
    asyncio.run(main())

Expected behavior
A clear and concise description of what you expected to happen.
The ForeignKey should be removed so i don't continue to have it!
Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

Database backend used: postgres and sqlite
Python version -- 3.9
ormar version -- 0.11.2
pydantic version -- 1.9.1
if applicable fastapi version

Additional context
Add any other context about the problem here.

Duplicate of #301. You need to explicitly call remove.


Potential buffer overrun

Reported by gcc-7.2:
WasmVM/src/Component/Decoder.cpp: In static member function ‘static void Decoder::decode(Store&, Stack&)’:
WasmVM/src/Component/Decoder.cpp:22:6: warning: ‘sprintf’ writing a terminating nul past the end of the destination [-Wformat-overflow=]
 void Decoder::decode(Store& store, Stack& coreStack) {
      ^~~~~~~
WasmVM/src/Component/Decoder.cpp:829:14: note: ‘sprintf’ output 3 bytes into a destination of size 2
       sprintf(codeChr, "%02x", ((std::uint32_t)bincode) & 0xff);
       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The casting from unsigned 32-bit integer is not exactly what sprintf expects.

The bug fix is in #26. Thank you for your reporting.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111484

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112576

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117853

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119550


Client should accept multiple CA certificates

Problem description
The Pravega client currently requires that the caller provide a single CA certificate for validating the connection to the server. However, it is common for a client user to not know exactly which CA certificate to use. In most TLS client implementations, the client will automatically select from a set of multiple CA certificates, based on information provided by the server.
Problem location
TLS
Suggestions for an improvement
Allow the user to provide a CA bundle or a directory containing multiple CA certs. Alternatively, use OpenSSL which should use the OS trust store.

It is preferred that the Pravega Rust Client use the same certs that the OS uses. On Ubuntu, it should use the results of the update-ca-certs command.
Additionally, we should use this opportunity to ensure that TLS 1.3 is supported. It is unknown whether TLS 1.3 is currently supported.


Problem with Homebridge 1.3.5

Hello,
thank you for your great job!
There is a big problem with the home bridge version 1.3.5 - mkdir failed - Homebridge restarts
Please take a look
thank you and best regards
Thomas

There are no issues with homebridge 1.3.5 and mkdir! All is working fine! I think your issue is related to your environment...

The plugin stopped working with the 1.3.5 Upgrade!
Error: EACCES: permission denied, mkdir '/root/.lgtv2'

This is an issue with your file system and not homebridge or the plugin. Homebridge cannot read the file on the specified directory, you need to fix your permission. Maybe you did the homebridge update as a root where previously it was with your user and that might have broken the permissions.

I found this after experiencing the same issue as @ThomasMeyer1970.
I've been using Homebridge for some time now, and my upgrade process has always been the same. I'm running the Docker container, so I basically use Portainer to recreate the container whilst pulling the latest image - has worked flawlessly for ages. Prior to using Portainer, I followed the upgrade steps on your wiki, which is basically what Portainer does but via a GUI.
Nothing has changed in the setup, but there is now an error as @ThomasMeyer1970 has highlighted. So do you have any suggestions as to what to do here @merdok, because right now my Homebridge won't start because of the issue above so I have to disable the plugin to get everything working and is not ideal?

I want to highlight again that the issue is not related to this plugin but to your homebridge installation.
For some reason for you guys the homebridge home directory changed to /root/ probably because you installed homebridge as root user. On the other hand you do not run your homebridge instance with the root user but probably with a normal user hence it is not possible to for homebridge to write the config in that directory.
I see two solutions here for you:

Fix your homebridge installation so that it is installed and run with the correct user.
You can specify in the config.json a custom folder where the plugin should write the preferences. Just check "prefsDir" in the README and specify a path where the user which you are using to start homebridge has write permissions.

Ok, what's with the tone of the replies? We're genuinely trying to be helpful here, but all myself and @ThomasMeyer1970 have received back are snarky replies that just fobs us off. Apologies if we came across any other way, but our installation went from working perfectly to not, and as you are the creator or the plugin that seems to be affected, we've created an issue here with detail that should hopefully help...
I'm running Homebridge in Docker on a Synology NAS (not running DSM 7 yet) and have followed their instructions as to how to install and run Homebridge. This has been working just fine for a few years, but maybe their recent update broke something here.
I also run Homebridge natively on a Raspberry Pi 4, and I tested your plugin there and it seems to work without the error - so it does look more likely that it is down to the Homebridge Docker container now, but this has only really come about because I've tried to help you by providing feedback and useful information, as opposed to just saying "it's not me, it's you".
I don't want to risk wrecking my Homebridge setup by messing around with user permissions, so I tried your second recommendation:

You can specify in the config.json a custom folder where the plugin should write the preferences. Just check "prefsDir" in the README and specify a path where the user which you are using to start homebridge has write permissions.

That didn't work either - I created two new folders within the Homebridge folder lg-webos-tv-prefs and lg-webos-tv-keyfiles and set the paths accordingly in the plugin settings, restarted Homebridge but the same error comes up about /root/.lgtv2.
I guess we'll have to take this to https://github.com/oznu/docker-homebridge.

Plugins should only write to the homebridge storage directory; not the "user" directory.
https://github.com/homebridge/verified#requirements

If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.

https://github.com/oznu/docker-homebridge/issues/397#issuecomment-971551471

@oznu the plugin is writing to the homebridge path "api.user.storagePath()", or is that wrong?
@raspberrycoulis you need to understand that you have some kind of issue with your setup. I cannot repeat myself each time with the same answer over and over again. Since I do not have access to your particular setup I cannot tell you exactly what the issue is on your side, every setup is different and there are many stuff which might affect it which are out my control. I gave you two passionless solutions which based on your information might help you.

@oznu the plugin is writing to the homebridge storage directory "api.user.storagePath()", or is that wrong?

That is correct. I would double check to confirm it's working as expected and the value is being passed through to the third party library.
When using the Docker image the Homebridge storage directory is /homebridge (this is the persistent volume for the Docker container).

@oznu the question is now, why suddenly after the update to 1.3.5 they are getting the wrong storage path with the exact same code. As they say, before the update everything was fine.
@raspberrycoulis and @ThomasMeyer1970 can you please post your config.json entries for the tv to make sure you have nothing wrong entered there?

@oznu the question is now, why suddenly after the update to 1.3.5 they are getting the wrong storage path with the exact same code. As they say, before the update everything was fine.

This is exactly my question too. Plugin worked perfectly until I updated Homebridge today (which uses the :latest tag from Docker, which I understand was updated on 15 November).
Here's the relevant parts of my config with certain elements redacted for security reasons:
        {
            "devices": [
                {
                    "name": "LG TV",
                    "ip": "<IP_ADDRESS>",
                    "mac": "XX:XX:XX:XX:XX:XX",
                    "pollingInterval": 10,
                    "volumeLimit": 100,
                    "volumeControl": "both",
                    "channelControl": true,
                    "mediaControl": false
                }
            ],
            "platform": "webostv"
        },

I've ran my entire config.json through JSONLint and it is valid.

Plugin worked perfectly until I updated Homebridge to version 1.3.5  around 10 days ago.
Here is the part of my config:
   {
        "devices": [
            {
                "name": "LG TV",
                "ip": "<IP_ADDRESS>",
                "mac": "xx:xx:xx:xx:xx:xx",
                "pollingInterval": 5,
                "hideTvService": true,
                "volumeLimit": 100,
                "volumeControl": "both",
                "channelControl": true,
                "appButtons": [
                    {
                        "appId": "com.webos.app.livetv",
                        "name": "LIVE TV"
                    },
                    {
                        "appId": "com.webos.app.hdmi2",
                        "name": "HDMI Input"
                    },
                    {
                        "appId": "com.webos.app.igallery",
                        "name": "Gallery"
                    }
                ]
            }
        ],
        "platform": "webostv"
    }
],
"disabledPlugins": [
    "homebridge-webos-tv"
]

}

config.json looks perfectly fine for both of you. The thing you can try is to add the keyFile property and specify a path to a file in a directory where you have write permissions.

Beating up the developer plugin isn't productive. Look at the code.
Yes, it's coming from the mkdir on the line you referenced. If you look at the persist-path here, you will see that the path is constructed by taking the value of HOME and appending '.' and 'lgtv2' to it. Your HOME variable is defaulting to '/root/'.
Somewhere along the line, lgtv2 is expecting HOME to be properly set.

Is there a way to override the HOME path manually? Looking at the lgtv2 repo, it hasn't been touched for some time, so it seems unlikely that anything will be changed there. However, why would it work just fine for ages, only to break after the Homebridge Docker image was updated 2 days ago?

The line 48 here https://github.com/hobbyquaker/lgtv2/blob/master/index.js#L48 is certainly not perfect, since even when you specify the keyFile this directory is tried to be created which for you fails, that is why specifying the keyFile brings nothing.
Anyway, since you say that it was running before the update that means that the line above, although not ideal, is not the main issue here.
My suspicions is that something changed with the setup how you run homebridge after your recent update. I cannot tell how or what exactly, but somehow your home directory (HOME env variable) is set to /root/ to which homerbidge does not have permissions to write because you probably do not run it with the root user. Maybe you run the update with the root user where before you did it with your normal user? Any plugin which will try to write to your home directory will now always fails since it will always point to /root/

Bizarre. Absolutely nothing has changed in my setup. Nothing. I have updated the Docker container the same way I have always done it and it's worked just fine.
I've got Homebridge running on a Raspberry Pi (non-Dockerised) and the plug-in works fine there so I'll stick with that.

Is there a way to override the HOME path manually?

Perhaps set a HOME environment value in the container?

Is there a way to override the HOME path manually?

Perhaps set a HOME environment value in the container?

Any ideas on how to do that?

Yeah, well i cannot tell what changed but definitely something changed...
I have summited a pull request to the lgtv2 repo to fix the unnecessary creation of the directory when the keyFile is specified, but from experience it might take some time till gets reviewed and merged...

Any ideas on how to do that?

You indicated that you were using Synology...
Same way you did when you initially installed the container. Open the Docker tool on your Synology. Select the container in question, shut it down (if running) and then click Edit. Select Environment and add variable called HOME with an appropriate value. Something that is valid within the container like "/homebridge/home/"

I have just set up my entire homebridge docker instance from scratch. Everything including plugins works perfectly - with the exception of the WEBOS TV plugin! Same error as before - so it's definitely a code problem ...

It has been already cleared that the issue has nothing to do with the latest homebridge update or with this plugin.
You have the issue because something in your system related to the user changed and the HOME environment variable points to a non writable directory. Nothing in that code changed in the past few years.
The dependency which causes the issue indeed is handling the creation of that directory not optimal since it is not necessary to create it and I have already submitted a pull request to fix that, but like already mentioned that code did not change since a very long time. So something in your system has changed which is now causing the issue, until my pull request is not merged you will have to figure out what caused the issue in your system to fix it.

I have just set up my entire homebridge docker instance from scratch. Everything including plugins works perfectly - with the exception of the WEBOS TV plugin! Same error as before - so it's definitely a code problem ...

Hey, just wanted to chime in because I've been experiencing this annoying issue for the last week with a nearly identical setup: a Synology DS718+ running the latest homebridge-docker being managed by portainer. I tried @dennypage's suggestion and everything is finally fixed. Add a HOME variable to /homebridge/home and maybe you won't have to wait for that request to get merged.

oops... Trying this completely broke my instance... Only get this error over and over in the logs:
s6-applyuidgid: fatal: unable to exec tail: Permission denied
s6-applyuidgid: fatal: unable to exec tail: Permission denied
s6-applyuidgid: fatal: unable to exec tail: Permission denied
s6-applyuidgid: fatal: unable to exec tail: Permission denied
s6-applyuidgid: fatal: unable to exec tail: Permission denied


fix(parser): fix enum member parsing

Closes #4449

#4543  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @DonIsaac and the rest of your teammates on  Graphite


Working on Linux

Still need to double check Windows

Coverage decreased (-1.0%) to 79.612% when pulling c09efc9629acf1a75e95b3289e3dce6affafa52b on jiwalker-usgs:master into 1e48605f55d4263e2259f410a931c863a9b20099 on USGS-VIZLAB:master.

@jiwalker-usgs recommendation for the best way to test? Run createMakefiles?

Yeah, run that and do a make on testviz.

@jiwalker-usgs I get that same couldn't make stderr distinct from stdout error everywhere, and then I get Error 1 for figures/relativeAbundanceFig.svg and Error 2 at the very end. Not sure if this passes the issue you were seeing and is just a separate issue in testviz or not.
In console:
setwd('inst/testviz')
createMakefiles()

Then, in Git shell:
lcarr@IGSARMEWLTLRC /d/LRCData/R/vizlab (jiwalker-usgs-master)
$ cd inst/testviz

lcarr@IGSARMEWLTLRC /d/LRCData/R/vizlab/inst/testviz (jiwalker-usgs-master)
$ make
make -f vizlab/make/fetch.make
      0 [main] sh 8412 stdio_init: couldn't make stderr distinct from stdout
make[1]: Entering directory `/cygdrive/d/LRCData/R/vizlab/inst/testviz'
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetchTimestamp funargs=list(viz='siteTextData'
)" \
vizlab/make/callFunction.R vizlab/make/log/fetch/siteTextData_timestamp.Rout
      0 [main] sh 7736 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetch funargs=list(viz='siteTextData')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/siteTextData.Rout
      0 [main] sh 2816 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetch funargs=list(viz='Cuyahoga')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/Cuyahoga.Rout
      0 [main] sh 8368 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetchTimestamp funargs=list(viz='MayflyNymph')
 scripts=c('scripts/fetch/mayflyNymph.R')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/MayflyNymph_timestamp.Rout
      0 [main] sh 6184 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetch funargs=list(viz='MayflyNymph') scripts=
c('scripts/fetch/mayflyNymph.R')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/MayflyNymph.Rout
      0 [main] sh 264 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetchTimestamp funargs=list(viz='carData')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/carData_timestamp.Rout
      0 [main] sh 2344 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetch funargs=list(viz='carData')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/carData.Rout
      0 [main] sh 8424 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetch funargs=list(viz='constant')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/constant.Rout
      0 [main] sh 5232 stdio_init: couldn't make stderr distinct from stdout
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=fetch funargs=list(viz='constant-list')" \
vizlab/make/callFunction.R vizlab/make/log/fetch/constant-list.Rout
      0 [main] sh 3684 stdio_init: couldn't make stderr distinct from stdout
      0 [main] sh 4296 stdio_init: couldn't make stderr distinct from stdout

      0 [main] sh 8836 stdio_init: couldn't make stderr distinct from stdout
fetch.make looks OK!
      0 [main] sh 4176 stdio_init: couldn't make stderr distinct from stdout

make[1]: Leaving directory `/cygdrive/d/LRCData/R/vizlab/inst/testviz'
make -f vizlab/make/process.make
      0 [main] sh 2816 stdio_init: couldn't make stderr distinct from stdout
make[1]: Entering directory `/cygdrive/d/LRCData/R/vizlab/inst/testviz'
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=process funargs=list(viz='CuyahogaShort') scri
pts=c('scripts/process/cuyahoga.R')" \
vizlab/make/callFunction.R vizlab/make/log/process/CuyahogaShort.Rout
      0 [main] sh 8692 stdio_init: couldn't make stderr distinct from stdout
      0 [main] sh 4164 stdio_init: couldn't make stderr distinct from stdout

      0 [main] sh 9160 stdio_init: couldn't make stderr distinct from stdout
process.make looks OK!
      0 [main] sh 7956 stdio_init: couldn't make stderr distinct from stdout

make[1]: Leaving directory `/cygdrive/d/LRCData/R/vizlab/inst/testviz'
make -f vizlab/make/visualize.make
      0 [main] sh 1664 stdio_init: couldn't make stderr distinct from stdout
make[1]: Entering directory `/cygdrive/d/LRCData/R/vizlab/inst/testviz'
export R_LIBS_USER=C:/Users/lcarr/Documents/R/R-3.3.2/library;\
C:/Users/lcarr/Documents/R/R-3.3.2/bin/x64/R.exe CMD BATCH --no-timing --quiet -
-no-save --no-restore "--args fun=visualize funargs=list(viz='relativeAbundanceF
ig')" \
vizlab/make/callFunction.R vizlab/make/log/visualize/relativeAbundanceFig.Rout
      0 [main] sh 8120 stdio_init: couldn't make stderr distinct from stdout
make[1]: *** [figures/relativeAbundanceFig.svg] Error 1
make[1]: Leaving directory `/cygdrive/d/LRCData/R/vizlab/inst/testviz'
make: *** [visualize] Error 2

Those are red herrings, has something to do with your shell I think.  But I do think that it is failing on that figure.  I think my fix should be fine (that it got this far), but I wonder what is causing that to fail.

I'll look in the make logs and let you know.

For fig:
> do.call(cmd.args$fun, if(is.null(cmd.args$funargs)) list() else cmd.args$funargs)
Error in UseMethod("visualize") :
  no applicable method for 'visualize' applied to an object of class "c('relativeAbundance', 'visualizer', 'viz')"
Calls: do.call -> <Anonymous> -> visualize.character -> visualize
Execution halted

Yeah, I don't know how that worked for me, that signature is all wrong.

Merging, but we will make a ticket to get the testviz working.


Plugins could not load from /plugins folder

What happened?
I've downloaded the swagger plugin to /plugins folder and restarted the service.
Anyway it can't load it:
13:07:53.712 INFO | --- Loading plugins (13):
13:07:53.714 INFO | failure, configuration, local-configuration, shared-configuration, access-token
13:07:53.714 INFO | authentication, console, statistics, frontend, storage
13:07:53.715 INFO | maven, status, web
13:07:53.809 INFO |

My folder:
xxx@xxx ~/w/reposilite> exa -la plugins/
.rw-r--r-- 126k xxx 21 May 12:20 swagger.jar

Reposilite version
3.x
Relevant log output
No response

Resolved on Discord, the problem was with invalid JAR file of Swagger plugin.