Add functionality to ignore the ExitStatus

This is an implementation for #240
This commit introduces CheckExitStatus (default: true) for plugin
execs. If CheckExitStatus is set to false, the process will ignore
the exit status and will set the action to sucess even when the
invoked backup mechanism exited with an exit code != 0.
The support is currently only built into the mysql plugin.
Unfortunately this is implemented using the strings "true" or
"false" because of my lacking go skills.
But it works. I have tested it using a DEV shield-boshdeployment
release.
Note that I have tried to use boolean values for CheckExitCode. The problem I did run in was, that if the struct consist of bool, then go will evaluate it to false (go zero values) and there is no way to figure out if the code was set and we need to know since it’s optional.
A workaround would be to work with pointers CheckExitCode *bool, since an empty pointer always is nil and would allow something like:
if opts.CheckExitCode != nil {
  CheckExitCode = opts.CheckExitCode
}

But this somehow did not work (probably because I am too stupid for it :) ). So consider it as a solutions, but not as a really nice one...

@jhunt I’ve thought about this and the only viable way I see right now would be to have something like a general option which can be used for the plugins. Then this could be patched into Exec (always check) and ExecWithOptions (make it configurable).
For an example, the mysql plugin could get configured as:
{
  "general_check_exit_code": "true",
  "mysql_user": "root",
  "mysql_password": "not-the-password",
  "mysql_host": "<IP_ADDRESS>",
  "mysql_port": "3306"
}

Then the Run(p Plugin) in plugin/plugin.go would neet to be enhanced to parse additional info into opts which then should make this generic and usable for all plugins. What do you thin!

Another option is to lift the functionality out of the plugins altogether, and have a flag on the target / store to "ignore non-zero plugin exit codes".  Mechanism-wise, we should be able to just let shield-pipe know about the new flag, communicate it through the agent/worker channel, and it should just work.
Unfortunately, these types of changes require uniform upgrades, and we have lots of users with distributed setups who may not be able to upgrade plugins right away.
We also have changes in the works that would more tightly couple plugin-agent-core interaction, to allow things like front-end enumeration of available plugins and available options, so I'd really like to get those done before we make other changes to the remote side of the architecture.

I‘ll close this for now since there are big changes coming and i currently do not have the time to invest here. :(


WIP: Fix bugs in Brain

This PR disables the rendering call each time a mesh is added to the scene in favour of only one call when everything is setup.
Quoting https://github.com/pyvista/pyvista/pull/935#issue-500086898:

There are 2 main reasons for this:

Huge speed gain when hiding and displaying meshes.
It looks much more professionnal when clicking a button to see all the changes at once.

@GuillaumeFavelier locally on master with a script similar to:

import os.path as op
import mne
data_path = mne.datasets.sample.data_path()
sample_dir = op.join(data_path, 'MEG', 'sample')
subjects_dir = op.join(data_path, 'subjects')
inv = mne.minimum_norm.read_inverse_operator(op.join(
    sample_dir, 'sample_audvis-meg-vol-7-meg-inv.fif'))
    # sample_dir, 'sample_audvis-meg-oct-6-meg-inv.fif'))
evoked = mne.read_evokeds(op.join(sample_dir, 'sample_audvis-ave.fif'))[0]
evoked.apply_baseline((None, 0)).pick_types(meg=True)
stc, res = mne.minimum_norm.apply_inverse(
    evoked, inv, return_residual=True, pick_ori='vector')

initial_time = 0.1
# stc, kwargs = stc, dict(overlay_alpha=0.5, brain_alpha=0.5, vector_alpha=0.)
stc, kwargs = stc.magnitude(), dict(alpha=0.5, surface='white')
kwargs['src'] = inv['src']
meth = stc.plot_3d if isinstance(stc, mne.VolSourceEstimate) else plot
brain = meth(
    subjects_dir=subjects_dir, initial_time=initial_time,
    clim='auto', hemi='both', views=['sag', 'axi', 'cor'],
    view_layout='horizontal', smoothing_steps='nearest', verbose=True,
    time_viewer=False, size=(800, 300), background='k',
    **kwargs)

I see this "flashing" (sorry the window disappears -- I'm talking about the meshes and outlines appearing and disappearing):

And on this branch and latest PyVista master it doesn't seem to be improved much. Do you see the same thing? Can you see if it can be improved?
Actually with this example script it's a bit worse -- the display doesn't update until I click on the window (ignore the "blue brain" in the background -- the window produced by the script above will appear on top of it, flash for a bit, then not display the final image until I click on the window to bring it to focus):

Thanks for reporting, I can reproduce. I will investigate in this PR (already opened).

For me, 0372cd2 improved the situation greatly. In plot_source_estimates(), show() is called last, when everything else is set basically. Could you try it now @larsoner ?

@GuillaumeFavelier I'm +1 for backporting, any reason not to?

I see no problem here :+1:

Thanks @GuillaumeFavelier

Nope, not backporting -- the conflict due to the TimeViewer / Brain refactor was ugly

Ouch, my bad. I thought it was straightforward to cherry-pick this.

Actually I think I figured it out: 35662d07f8cb31c104ee36e94b9484ff05424b21


Can't create a custom Bootstrap-Vue b-form-select component

Versions

vee-validate: 2.1.5
vue: 2.5.22

Describe the bug
I followed the documented example for using VeeValidate to wrap a custom (Vuetify) component and tried to apply the same to Bootstrap-Vue. VeeValidate's ValidationProvider and the <b-form-select> component from Bootstrap-Vue don't appear to play together well. However, I don't experience the same issue when I use the default errors injected from VeeValidate.
To reproduce
Steps to reproduce the behavior:

Go to the Codesandbox demo below
Tab to focus the first dropdown
Use the arrow keys to select 'Female'
(Note that the inline error message flickers for a split second)
Select the default 'Select' (null) option
At this point it'll only flicker, but the error will not remain
Tab down to the Animal dropdown
Perform the same test again and select the first element, then select the default 'Select' (null) option

Expected behavior
A clear and concise description of what you expected to happen.
Demo link
https://codesandbox.io/s/4xpn18nqw9
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 71

Additional context
Add any other context about the problem here.

Sorry I never addressed this, VeeValidate 3.0 has just been released and it seems to be working fine now:
here is an updated sample:
https://codesandbox.io/s/vue-template-forpx


Edge Dev is not found

See Downstream Issue: https://github.com/httptoolkit/httptoolkit/issues/401
I have installed MS Edge Dev via winget.
The application is present in the default install directory C:\Program Files (x86)\Microsoft\Edge Dev\Application and in the Start Menu C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Edge Dev.lnk.
The definition file for Edge does not mention edge dev at all.
https://github.com/vweevers/win-detect-browsers/blob/8f5df151f1e495564058ab50b0894577a51ced0b/lib/browsers.js#L113-L121
The Paths for Edge and Edge Beta are defined, and this.startMenu().
https://github.com/vweevers/win-detect-browsers/blob/8f5df151f1e495564058ab50b0894577a51ced0b/lib/finder.js#L157-L165
This argument is not provided which, from what I see, would always result in an invalid registry path being checked (argument is stringified to "undefined").
The argument is not provided falls back to the binary name which doesnt work for Edge.
Edge Dev would be present in the registry path that startMenu checks, if the check was working correctly.
(Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\StartMenuInternet\Microsoft Edge Dev\shell\open\command exists)
What needs to be done:

Add default install path for Microsoft Edge Dev
Make sure that startMenu() is really a valid usage of the function; plenty of your definitions use it without argument but this will never work from what I understand.

startMenu works (in general) because of the || (startEntry = this.bin). Whether it works for Edge doesn't really matter if we can find Edge through other means.
PR is welcome to add the install path of Edge Dev. That should suffice.

I'll make a PR.
I'd like to also add channel detection for Edge.
Sadly the edge binary does not actually have metadata that indicates that it is a beta.
The fact that it's a beta seems to be mainly signaled by a msedge.VisualElementsManifest.xml file in the same folder as the binary.
Is it okay to read this file in the post function of the detection and then check the channel via regex? One may argue that this is rather slow. The alternative is assuming that it's always installed in the default path and just getting the channel from that.


Add support for daemonization

This pull request introduces several enhancements and updates to the project. The major additions are as follows:

Daemonization Support: Added functionality to run the program as a daemon with the -d flag. This allows the program to run as a background process.
Dropping privileges: Introduced a flag to specify the user that the program should run as. For example, go2rtc might need root permissions in order to bind to a network port number lower than 1024 (as is the case in many Unix-like systems), but it does not need those permissions to handle incoming network connections once the port is open.
Signal Handling: Added signal handlers for SIGQUIT, SIGTERM, SIGSEGV, and SIGHUP. This improves the program's ability to handle different types of system signals and makes the program more robust. Additionally, the signal notifications in the shell package have been updated to include SIGQUIT and SIGSEGV.

All these changes apply only to unix-like systems. for windows stubs are implemented

Lots of code. It needs to be carefully analyzed all of it.

Lots of code. It needs to be carefully analyzed all of it.

The Way of the Maintainer :)

Up 🙄


Checksum

Create file meta data and log output.
Upload of data tbd
Removed types for FileList and SelectedFile - using dom types

Merging this because it's blocking some other branches. :+1:


Probe camera angles ?

How to change the orientation of the probe to take another camera angle in VR?
(And with the Vive controllers, the indicators of the colored buttons are very confusing ; like press green button, but where??? and wich hand?)
Great Mod by the way;)

@yohaskan You should be able to rotate the probe by launching the probe, then touching the probe launcher with your left hand, while holding it with your right hand. No tutorial for that yet.
As for the buttons, it's not very easy to make it obvious in the game. You can go to SteamVR's input mapping settings for Outer Wilds and see the mappings there. Green is always the same as jump, blue is always the same as interact.

Ok thanks, i'll check that


affix-nav  bottom border changes as you scroll down from the top

Note the width of the ```1 bottom border under "Latest Download" here after the page first loads.

Then as I scroll down the page and the nav jumps to live, that same border shrinks the line gets shorter.

I'm seeing this on more than one affix nav page, so I suspect it is a global bug.

When I watch the affix-nav closely in the inspector, it seems to me that width of the element changes when it leaves our two column block and jumps to its fixed position.
At that point, I suppose it is no longer a floating child element as it was before. Maybe there's some way for it to inherit the parent column's width but I haven't found it yet.


make remove secret return not found

The issue is mentioned in https://github.com/docker/docker/issues/31909#issuecomment-287340378
Signed-off-by: allencloud<EMAIL_ADDRESS>

As with #2042, I think this needs to be handled in the engine based on the gRPC return code. I know it might take a significant refactor to get there, but unless there's an urgent problem, I think dealing with this in the engine is way better.

@allencloud closing this here per https://github.com/docker/swarmkit/pull/2042#issuecomment-287755179; let us know if you need help on implementing it in docker/docker 👍


Bridges

wrong move sorry :)

Thanks for the project btw.
I had an amazing time and discovered great artists on it, totally fittted my use of recommandations on music streams.
Currently customizing your well thought UX as an exploration prototype interface for another project :)

@mcoenca Great to hear that. Good luck ! :)


Add system.metadata.table_comments table

Related to https://github.com/prestosql/presto/pull/529

I'm checking the failed cause about convention based test.

@electrum Thank you for your reviews. Applied your comments and added NPE at
https://github.com/prestosql/presto/blob/852367d666dc1cf91950a7dbc85b2824e108677e/presto-main/src/main/java/io/prestosql/connector/system/TableCommentSystemTable.java#L113

Catching NPE seems wrong. Let’s add a commit before this that fixes the Cassandra connector.

@electrum Sent the PR to fix it (https://github.com/prestosql/presto/pull/592). Let me rebase after the PR is merged.

@ebyhr Please rebase and then assign back to me

@electrum Rebased. The travis failed by timed out (https://api.travis-ci.com/v3/job/194801727/log.txt).
(I don't have the permission to change assignees)

@electrum Thank you for your review. Updated.


Problem in /utils/dirs.go#CopyFile()

Hi!
I found when copying files, it could not copy the symbol links correctly.  It will always follow the symbol link, so some dependency issues will occur.
I think it should be
func CopyFile(src, dst string, makeDir bool) error {
	info, err := os.Lstat(src)
        ...
}

instead of
func CopyFile(src, dst string, makeDir bool) error {
	info, err := os.Stat(src)
        ...
}

Thank you for the report! What do you mean by "when copying files"? Are you using the utils package directly? The DockerSlim code uses it only when it needs to copy additional files based on the include-paths command line parameter. The main files DockerSlim discovers are copied using another method...
You are right about the Lstat() call though. There's a couple of other places with the same problem, but it's not relevant there because the files are already pre-filtered into regular and link files.

Thank you for your reply!  Indeed, I use the utils package directly. And as you said, the CopyFile() has no effect on the main files DockerSlim discovers.
I really appreciate docker-slim, thanks again.

It'll be fixed in a few days either way. Thank you for catching the bug!


ANVIL_KEY_HELPER  and KeyID aren't part of the library

In types.h there are types related to keyboards, that aren't really part of Vulkan. Should probably moved to another header, as some Vulkan platforms might not have keyboards going forward.

Sorry for getting back to you so late. Since I don't have any strong feelings about this, I'll just go and move these types to a separate header.
This change will be included in the next Anvil update.


Update Dev Container

Configure WSLg X-Server redirection for audio and GUI applications
Exclude Conan from the image as we have switched to using CPM
Incorporate BuildKit frontend in Dockerfile
Mount APT cache, however it is ignored in Github Actions https://github.com/moby/buildkit/issues/1512
Share pre-built image using GitHub Packages
Transfer VSCode extensions and settings to the .vscode folder as those properties in devcontainer.json prevent offline container launch

Codecov Report
Patch coverage has no change and project coverage change: -13.37 :warning:

Comparison is base (5bf4f34) 25.30% compared to head (631d45a) 11.94%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #37       +/-   ##
===========================================
- Coverage   25.30%   11.94%   -13.37%
===========================================
  Files           6        5        -1
  Lines         249      201       -48
  Branches      138      140        +2
===========================================
- Hits           63       24       -39
+ Misses        179      149       -30
- Partials        7       28       +21

Flag
Coverage Δ

Linux
11.94% <0.00%> (-5.60%)
:arrow_down:

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/ftxui_sample/main.cpp
6.21% <0.00%> (-4.85%)
:arrow_down:

... and 5 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


How to Change the "Starting Flexx App"?

Hello,
How to Change the "Starting Flexx App"?

In Python's site-packages/flexx/app directory, file _assetstore.py line 36:

Indeed. Other than changing the source, this text cannot be changed.


Pluggable Modules for Avro Serialization

This PR adds the AvroSerializer interface, with accompanying implementations using Apache and Jackson, which allows for abstraction of the Avro serialization implementations, and its dependencies, in our client libraries. In cases where a client library needs to interact with Avro serialization and de-serialization it should add an option to its builder to accept AvroSerializer, this will allow for client libraries to be agnostic to the underlying implementation. It is still undecided whether AvroSerializer will have a service provider interface (SPI) or libraries using Avro will take a dependency on one of the implementing libraries, which is overrideable if a customer wants to use another implementation.
Example: EventHubs
EventHubClient eventHubClient = new EventHubClientBuilder()
    .connectionString(connectionString)
    .serializer(avroSerializer) // This is a potential representation of the change in a client library.
    .buildClient();

@srnagar @JonathanGiles


Replace flake8 with ruff

Replaces flake8 with ruff. Also fixes a few lint errors that show up because of that.
Total time on my machine:

flake 1.415 sec
ruff 0.05 sec

The important question: what have I done with the from typing import * custom extension that we had? I've disabled the rule. I plan to change all from typing import * into from typing import List, Dict before merging this PR.

Re import *: A pretty good way of doing this would be search and replace with all names in typing:
from typing import Any, ClassVar, Generic, Optional, Tuple, Type, TypeVar, Union, AbstractSet, Iterable, Iterator, MutableMapping, MutableSequence, MutableSet, Sequence, Dict, List, Set, cast, overload

... and then running ruff check --fix ., which would remove unused imports.

https://github.com/edgedb/edgedb/pull/6874 has a few problems with the new f-string syntax and flake8, upgrading to ruff fixes that.

Should we investigate whether ruff would take a patch to support from typing import * nicely?


gojq: init at 0.12.7

Motivation for this change
This is an implementation of jq command written in Go language. You can also embed gojq as a library to your Go products.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 162301 run on x86_64-linux 1

1 package built:

gojq


Added addons for other terraform provider

Solved this issue https://github.com/oam-dev/kubevela/issues/2457
Adding support for:

AWS
GCP
VSPHERE
EC

Here are some guide:

add template.yaml in vela-templates/addons/
run go run ./vela-templates/gen_addons.go to generate file
reinstall vela-core and try vela addon enable terraform/provider-xxx to test your addon.

Your job helps a lot!

Hi, do you have any problem with the guide? Files in vela-templates/addons/ are needed, files in chart are generated. All files should be commited. :)

It would be better to add files in vela-template but if @emanuelr93 doesn't have more time, this is acceptable.

Replaced with https://github.com/oam-dev/kubevela/pull/2672.


robots-txt: extend host to support boolean value (automatic resolving)

Context
Following the pattern of how sitemap option is done, the host could also be resolved automatically from the Astro config site value, so it could be both boolean or string(s):
sitemap

Type
Required
Default value

Boolean / String / String[]
No
true

As I have checked both inspiration packages accepts sitemap as string (gatsby-plugin-robots#options and generate-robotstxt) and leaves consumer responsible for the values they pass, but astro-robots-txt package targets Astro framework, so it does automatic sitemap resolving which is smart. Why couldn't it do the same for host value?
Proposed change
host

Type
Required
Default value

Boolean / String
No
undefined

Having that in mind, available host types would be Boolean or  String and reflect the following flows:

host: undefined -> default (same as is now, host is omitted)
host: true -> would resolve host automatically via Astro site prop and will include it into sitemap
host: 'any-string-value.com' -> would print out the custom value (as it works now)

TODO

Make host prop be available as Boolean / String

Thanks for the issue.
Your idea looks not bad. I'll do.

@alextim Awesome! Thanks for quick reply and improvement 🙏 We can close this task as done.


Add contributing guidelines

see https://github.com/blog/1184-contributing-guidelines

Closed by 1580467a1434b6daa51204591ad49379a2823fb5


libp11-kit.so.0 should not be excluded as it is not presend on many systems

I can confirm this because on my full featured gentoo laptop with full KDE installed and many crypto application the library doesn't come installed by default, hence I can imagine it is missing on many lighter environments, I have noticed it running the AppImage generated via OBS that you can get here
https://download.opensuse.org/repositories/home:/g10h4ck:/branches:/home:/AsamK:/RetroShare/AppImage/
I had to install app-crypt/p11-kit manually otherwise the appimage fail to start with the following error
retroshare: error while loading shared libraries: libp11-kit.so.0: cannot open shared object file: No such file or directory
the library is explicitely listed in https://github.com/AppImage/AppImages/blob/master/excludelist and also on the build log it is in excludelist
https://build.opensuse.org/build/home:g10h4ck:branches:home:AsamK:RetroShare/AppImage/x86_64/RetroShare/_log

Well, Gentoo is not one of the supported distributions because there is no clear "default install" baseline nor a Live ISO image, to my knowledge. We will continue to observe whether this issue also exists for the supported distributions.

they release a live DVDhttps://wiki.gentoo.org/wiki/Project:RelEng/LiveDVD/20160514

It's from 2016... is that what people still use?

Yeah!
It is the current live Gentoo version
Cheers!

We may consider looking into it once Gentoo can be booted with https://github.com/probonopd/SystemImageKit/.

+1


FCFB-18 Number with symbol in between gives -1

For example, Wisconsin submitted 8+01 and the bot used -1 for the defensive number. Looks like maybe an issue if the number has a symbol in between.

This is also the case with letters. I submitted 7y54 and got -1

The desired result is probably what it does for the offense

Fixed with FCFB-10


step-value not updating

Is this related to the width of the screen?
Seems to work ok in a broader view.

Could you please provide a fiddle showing this issue? (Please fork this one: http://jsfiddle.net/pq7yr6d6/)

http://jsfiddle.net/maartenfb/6jr0eha4/
Only seems to happen when decreasing the page width to phone like size.

Indeed there is a bug. This is due to this line: https://github.com/rzajac/angularjs-slider/blob/master/rzslider.js#L655 . I already had problem due to it but I don't know what is its purpose... It might be here only for optimization purpose but in small screen cases, it leads to a bug. I think that removing this line fix your problem...

commenting out that line fixed it :-)
Thanks.

Also I noticed that when you clicked on a increase/decrease button, there is a delay to update the slider. This is due to the throttle value here: https://github.com/rzajac/angularjs-slider/blob/master/rzslider.js#L294 . Setting a lower value than 350 reduce this lag.


FlinkCDC 在 insert 部分 支持 where 条件过滤

CDCmysql 表：A（startup_mode:initial)
目标表：B
insert into B
select *
from A
where id >10000
运行之后，我看日志，FLINK依然会把 表A 全表进行 切分操作，而不是 按照 id>10000 做快照进行同步，请问有什么方法可以不要A表全量快照切分吗？很慢的。

I think we need a filtering logic for the chunk key column in the snapshot phase.

CDC 中 WHERE 条件不能下推，什么时候能解决呢，感觉很二！

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!


Can't install on Laravel 5.6

After installing via composer using the command : composer require 'kordy/ticketit:0.*'
We are having the below error

Any help will be highly appreciated.
FYI , we are using laravel 5.6

Somehow you installed an old version. This bug was fixed more than 2.5 years ago! https://github.com/thekordy/ticketit/commit/bd4c8f96635bdff81019dd161ce0ea6bb2dc9ebd

Thanks for providing the information on the same.
I tried the same however still i am facing another issue as below :

Yes this worked!


[Sprig App] SkyFall

Author name
Author: Meowkewok
About your game
What is your game about?
Dodge Meteorites and survive as long as possible!
How do you play your game?
A/D- Movement
J- Reset
L- Lose

Thanks for your submission! I like your game a lot, but after a few rounds of meteors there's often a round that's impossible, and while that would normally be fine I worry it doesn't hit the required 1 minute of playtime. Do you think you could add more features or change the meteor spawning mechanics so the game lasts longer? If you did, I would be happy to approve your game!

I think that I fixed it, but I do not know how to update the PR. should I make a new one?


Fixing the venue JSON orphan issue.

Docs Build status updates of commit 78baaa0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:warning:Warning
View
Details

BingMaps/v8-web-control/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md

Line 32, Column 23: [Warning: file-not-found - See documentation] Invalid file link: '..\styling\map-style-sheet-entries.md'.

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md

Line 21, Column 63: [Warning: file-not-found - See documentation] Invalid file link: '../v8-web-control/index.md'.
Line 21, Column 104: [Warning: file-not-found - See documentation] Invalid file link: '../v8-web-control/modules/venue-map-module/venuemap-class.md'.
Line 21, Column 129: [Warning: file-not-found - See documentation] Invalid file link: '../v8-web-control/modules/venue-map-module/venuemapoptions-object.md'.

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md

Line 27, Column 41: [Warning: file-not-found - See documentation] Invalid file link: '../articles/bing-maps-tile-system.md'.

BingMaps/v8-web-control/TOC.yml

Line 714, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/address.md'.
Line 716, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/entity.md'.
Line 718, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/floor.md'.
Line 720, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/geometry.md'.
Line 722, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/inner.md'.
Line 724, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/label.md'.
Line 726, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/rectangle.md'.
Line 728, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venue.md'.
Line 730, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/sample.md'.
Line 732, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venueTile.md'.

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

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

File
Status
Preview URL
Details

BingMaps/v8-web-control/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml

Line 714, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/address.md'.
Line 716, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/entity.md'.
Line 718, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/floor.md'.
Line 720, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/geometry.md'.
Line 722, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/inner.md'.
Line 724, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/label.md'.
Line 726, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/rectangle.md'.
Line 728, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venue.md'.
Line 730, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/sample.md'.
Line 732, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venueTile.md'.

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

Docs Build status updates of commit 238fe19:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/v8-web-control/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml

Line 710, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/index.md'.
Line 714, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'venue-map-module/venue-json/address.md'.
Line 716, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'venue-json/entity.md'.
Line 718, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/floor.md'.
Line 720, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/geometry.md'.
Line 722, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/inner.md'.
Line 724, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/label.md'.
Line 726, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/rectangle.md'.
Line 728, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venue.md'.
Line 730, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/sample.md'.
Line 732, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venueTile.md'.

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

Docs Build status updates of commit 4417dff:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/v8-web-control/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml

Line 710, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/index.md'.
Line 714, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'address.md'.
Line 716, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'venue-json/entity.md'.
Line 718, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'venue-map-module/venue-json/floor.md'.
Line 720, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/geometry.md'.
Line 722, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'v8-web-contro/modules/venue-map-module/venue-json/inner.md'.
Line 724, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'bingmaps/v8-web-contro/modules/venue-map-module/venue-json/label.md'.
Line 726, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/rectangle.md'.
Line 728, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venue.md'.
Line 730, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/sample.md'.
Line 732, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venueTile.md'.

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

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

File
Status
Preview URL
Details

BingMaps/v8-web-control/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml

Line 710, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/index.md'.
Line 713, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'address.md'.
Line 715, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'venue-json/entity.md'.
Line 717, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'venue-map-module/venue-json/floor.md'.
Line 719, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/geometry.md'.
Line 721, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'v8-web-contro/modules/venue-map-module/venue-json/inner.md'.
Line 723, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'bingmaps/v8-web-contro/modules/venue-map-module/venue-json/label.md'.
Line 725, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/rectangle.md'.
Line 727, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venue.md'.
Line 729, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/sample.md'.
Line 731, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venueTile.md'.

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

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

File
Status
Preview URL
Details

BingMaps/v8-web-control/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml

Line 710, Column 17: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/index.md'.
Line 714, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'address.md'.
Line 716, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'venue-json/entity.md'.
Line 718, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'venue-map-module/venue-json/floor.md'.
Line 720, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/geometry.md'.
Line 722, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'v8-web-contro/modules/venue-map-module/venue-json/inner.md'.
Line 724, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'bingmaps/v8-web-contro/modules/venue-map-module/venue-json/label.md'.
Line 726, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/rectangle.md'.
Line 728, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venue.md'.
Line 730, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/sample.md'.
Line 732, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'modules/venue-map-module/venue-json/venueTile.md'.

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

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

File
Status
Preview URL
Details

BingMaps/v8-web-control/modules/venue-map-module/address.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/entity.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/floor.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/geometry.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/inner.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/label.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/rectangle.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/sample.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venue.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/address.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/entity.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/floor.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/geometry.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/inner.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/label.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/rectangle.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/sample.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venue.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venues-json/venueTile.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venueTile.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/venues-json/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/address.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue address JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/address.md(2,8), v8-web-control/modules/venue-map-module/venues-json/address.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue address JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/address.md(17,1), v8-web-control/modules/venue-map-module/venues-json/address.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue address JSON class represents an address of a venue map or entity within a venue map. Includes Properties and Example.' is duplicated in 'v8-web-control/modules/venue-map-module/address.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/address.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/entity.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue entity JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/entity.md(2,8), v8-web-control/modules/venue-map-module/venues-json/entity.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue entity JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/entity.md(17,1), v8-web-control/modules/venue-map-module/venues-json/entity.md(17,1)'. First level headings must be unique within a docset.
Line 32, Column 23: [Warning: file-not-found - See documentation] Invalid file link: '../../../../styling/map-style-sheet-entries.md'.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue entity JSON class encapsulates an individual entity on the floor of a venue. Includes Properties and Example.' is duplicated in 'v8-web-control/modules/venue-map-module/entity.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/entity.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/floor.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue floor JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/floor.md(2,8), v8-web-control/modules/venue-map-module/venues-json/floor.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue floor JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/floor.md(17,1), v8-web-control/modules/venue-map-module/venues-json/floor.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue floor JSON class encapsulates an individual floor of a venue that contains each entity on that floor.' is duplicated in 'v8-web-control/modules/venue-map-module/floor.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/floor.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/geometry.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue geometry JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/geometry.md(2,8), v8-web-control/modules/venue-map-module/venues-json/geometry.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue geometry JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/geometry.md(17,1), v8-web-control/modules/venue-map-module/venues-json/geometry.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue geometry JSON class encapsulates a polyline or polygon geometry within a venue entity.' is duplicated in 'v8-web-control/modules/venue-map-module/geometry.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/geometry.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/inner.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue inner JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/inner.md(2,8), v8-web-control/modules/venue-map-module/venues-json/inner.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue inner JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/inner.md(17,1), v8-web-control/modules/venue-map-module/venues-json/inner.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue inner JSON class encapsulates a hole within a polygon geometry. This class is part of the venue JSON class structure.' is duplicated in 'v8-web-control/modules/venue-map-module/inner.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/inner.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/label.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue label JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/label.md(2,8), v8-web-control/modules/venue-map-module/venues-json/label.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue label JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/label.md(17,1), v8-web-control/modules/venue-map-module/venues-json/label.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue label JSON class encapsulates the position and contents of a text label to try to apply to an entity.' is duplicated in 'v8-web-control/modules/venue-map-module/label.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/label.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/rectangle.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue rectangle JSON class  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/rectangle.md(2,8), v8-web-control/modules/venue-map-module/venues-json/rectangle.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue rectangle JSON class' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/rectangle.md(17,1), v8-web-control/modules/venue-map-module/venues-json/rectangle.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Venue rectangle JSON class encapsulates an oriented rectangle. This class is part of the venue JSON class structure.' is duplicated in 'v8-web-control/modules/venue-map-module/rectangle.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/rectangle.md(3,14)'.

BingMaps/v8-web-control/modules/venue-map-module/sample.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Venue JSON sample  - Bing Maps' is duplicated in: 'v8-web-control/modules/venue-map-module/sample.md(2,8), v8-web-control/modules/venue-map-module/venues-json/sample.md(2,8)'. Titles must be unique within a docset.
Line 17, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Venue JSON sample' is duplicated with other articles: 'v8-web-control/modules/venue-map-module/sample.md(17,1), v8-web-control/modules/venue-map-module/venues-json/sample.md(17,1)'. First level headings must be unique within a docset.
Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'The Venue JSON sample includes such sample data as schema, id, name, type, xy, address, defaultFloor, bbox, and floors.' is duplicated in 'v8-web-control/modules/venue-map-module/sample.md(3,14)', 'v8-web-control/modules/venue-map-module/venues-json/sample.md(3,14)'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 036a82b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/v8-web-control/modules/venue-map-module/entity.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venue.md
:warning:Warning
View
Details

BingMaps/v8-web-control/modules/venue-map-module/venueTile.md
:warning:Warning
View
Details

BingMaps/venues/index.md
:bulb:Suggestion

Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/entity.md

Line 32, Column 23: [Warning: file-not-found - See documentation] Invalid file link: '../../../../styling/map-style-sheet-entries.md'.

BingMaps/v8-web-control/modules/venue-map-module/venue.md

Line 22, Column 63: [Warning: file-not-found - See documentation] Invalid file link: '../../../index.md'.
Line 22, Column 104: [Warning: file-not-found - See documentation] Invalid file link: '../venuemap-class.md'.
Line 22, Column 129: [Warning: file-not-found - See documentation] Invalid file link: '../venuemapoptions-object.md'.

BingMaps/v8-web-control/modules/venue-map-module/venueTile.md

Line 28, Column 54: [Warning: file-not-found - See documentation] Invalid file link: '../../../../articles/bing-maps-tile-system.md'.

BingMaps/venues/index.md

[Suggestion: file-not-redirected - See documentation] File BingMaps/venues/index.md was deleted without redirection. To avoid broken links, add a redirection.

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 0128c25:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/v8-web-control/modules/venue-map-module/venue.md
:warning:Warning
View
Details

BingMaps/venues/index.md
:bulb:Suggestion

Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venue.md

Line 22, Column 104: [Warning: file-not-found - See documentation] Invalid file link: '../venuemap-class.md'.

BingMaps/venues/index.md

[Suggestion: file-not-redirected - See documentation] File BingMaps/venues/index.md was deleted without redirection. To avoid broken links, add a redirection.

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 a8ab8d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

BingMaps/v8-web-control/modules/venue-map-module/address.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/entity.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/floor.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/geometry.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/inner.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/label.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/rectangle.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/sample.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venue.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/modules/venue-map-module/venueTile.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/TOC.yml
:white_check_mark:Succeeded
View

BingMaps/venues/index.md
:white_check_mark:Succeeded

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


Fix imdario/mergo version

Fixing https://github.com/score-spec/score-compose/issues/188 by running go mod edit -replace<EMAIL_ADDRESS>I then was able to successfully run:
go mod tidy
go get -u all

And, after the merge into main, Dependabot is now back to normal:


Improved version of "View: Toggle Editor Group Sizes" (workbench.action.toggleEditorWidths)

We can temporarily maximize an editor tab with https://github.com/microsoft/vscode/issues/196722 which works great.
You can also use "View: Toggle Editor Group Sizes" (workbench.action.toggleEditorWidths) which reduces the size of other editor groups. In this case the original editor size is not restored, but kind of divided equally.
Sometimes when I use "View: Toggle Editor Group Sizes" I wish it could respect vertically aligned editor groups and only shrink the rest.
For example, I find myself comparing a main log files with 2 secondary ones:

When I want to focus on both secondary and I try to use "View: Toggle Editor Group Sizes" I get only one maximized.
So in this case have to do it manually by dragging the resize widgets, not as convenient and fast as toggling it using the command.

One thing to note, in some situations the split node can be horizontal so the user might want it instead to respect the horizontal alignment. This can be easily shown with the previous example using the command "Toggle Vertical/Horizontal Editor Layout" (workbench.action.toggleEditorGroupLayout)

Request

A new command similar to "View: Toggle Editor Group Sizes" that enlarges the current editor groups in the same split node

I would make it a single command and detect the direction, but there could be a command for horizontal/vertical

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


chore: add translations for API screens

Summary | Résumé
PR to add translations for the API screens.

@anikbrazeau starting this PR for when you have some time to start adding the strings
There's a bunch on the form-builder file
i.e.
"responseDeliveryHelpWithApi": {

Added a couple of commits to the form builder file to update the French strings and match some tweaks in English as well!

Created a first bilingual version of the READ.ME that we can tweak later as well.


Update Waifu2x icon

Waifu2x favicon has been updated:
 ->

Isn't the waifu2x domain http://waifu2x.udp.jp/ ? 🤔
I'm not very up to date with things but that's the one you're redirected to when clicking the option no?

Oops. my bad. Closing the PR.


Bug fix for error logging.

The current implementation of error logging always returns empty hash as error type in logs. Casting class to string first will allow this field to be populated properly.

jruby-1.7.19 :001 > InvalidClientStatusChange.to_json
 => "{}"
jruby-1.7.19 :002 > InvalidClientStatusChange.to_s.to_json
 => "\"Backbeat::InvalidClientStatusChange\""

👍


nether seed

Hi
I was wonder since the nether generation hasn't changed is it possible to get the seed of the 1.18 world by cracking the nether?

The reason It doesn't work anymore is because Minecraft uses a new random number generator I think, so, no.


Visual outcome heavily influenced by the theme chosen in the settings

Describe the bug
Hello, and thanks a lot for your hard  work!
I've noticed that the custom CSS is only applied to some elements, while the rest retains the visual style of the theme I or the user pick in the settings.
To Reproduce

Set custom CSS:

@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/base.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/accentlist.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/type/dark.css');

Change theme in Settings > Display

Screenshots
WMC Theme:

Apple TV Theme:

Comments
Am I doing something wrong? Is there a specifi Jellyfin theme I should pick in the dropdown for your theme to work as intended?
Thank you!

Yes, that is how CSS overrides work.

Thanks, yes I'm aware of how CSS overrides work, thing is these imported styles don't override everything and I was wondering why, as they lead to particularly broken results with some like the AppleTV theme.
I don't have any theme called "Default", but I guess you're referring to Dark and Light?

Anyway it seems to be working great with Dark, which is what I wanted, so I'll stick to that.
Thank you for your reply


Port forwarding only works with this /usr/sbin/sshd listener 0 of 10-100 startups running

ADD ISSUE DESCRIPTION HERE
So I have hausra graphql running on hasura:8080
I cannot access it through my rails server sending requests to it without this running:
/usr/sbin/sshd listener 0 of 10-100 startups
Sometimes it does not startup with my codespaces leaving it with connection refused to the server
Currently even with that running, now my codespaces is stuck loading. (wont even load the extensions)
and the graphql request is stuck in fetch pending...
Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36
Embedder: codespaces

@dinushkaherath can you share a screenshot of where you're stuck loading? Can you also share the console output from the devtools?

@alexr00
one issue - workspace stuck loading

other issue - main issue cannot send requests to my hasura server

Thanks @dinushkaherath. Because your forwarded ports are private, you need to provide GitHub authentication in order to access them at the https://dinushkaherath-oak-atlantic-.... url. This is expected and just how private forwarded ports work. A few things you can try:

You can make your ports public (right-click on the port in the "Ports" view and "Change privacy"). This means that anyone can access your forwarded port, so of course use at your own discretion. This gets rid of the authentication requirement.
If you're trying to access the port from a service that is running on the same Codespace, you can try using localhost:8080 instead of the whole https://dinushkaherath-oak-atlantic-.... url in your POST.

Please let me know if either of those works for you as it will confirm the issue!
I'm not sure about the workspace not loading issue. @cmbrose in case you have an idea.

@alexr00 I have been trying to use localhost:8080, and placing all containers on the same shared network - my postgres container, with no luck as to the localhost usage (maybe this is because it's from a client side javascript post?)
How can I provide github authentication, I really wouldnt want to rewrite all my requests to include it...
Is it possible for any requests from github run services (my rails server) attach the auth token along with it when I'm in the browser?

(maybe this is because it's from a client side javascript post?)

If it's client side then you are correct: using localhost will not work.

How can I provide github authentication, I really wouldnt want to rewrite all my requests to include it...
Is it possible for any requests from github run services (my rails server) attach the auth token along with it when I'm in the browser?

@cmbrose might be able to answer this.

Also any way to automatically set a port to public?

There is currently no way to automatically set a port to be public.

:wave: @dinushkaherath it looks like you are using the codespace in the browser - is it possible to use the vscode extension instead? That will allow PF to run directly on localhost of your machine rather than through githubpreview.dev. That should allow you to bypass authentication, although it will only work with private ports. If you change the port to public it will go back to the gitbhubpreview.dev url and you may run into this again.

Is there a default ENV var like CODESPACES that shows whether its running in the browser or in VSCode?

I mean are you using the codespace in a browser - chrome/safari/edge/firefox - or are you using it in the desktop vscode application? My recommendation is using the desktop application.

Mainly using it in the browser

Yeah, so could you try it in desktop? That will use localhost as the port forwarding address instead of githubpreview.dev which might make this work better.

it works in desktop with localhost. Is there a way I can programmatically distinguish if its running in browser vs in desktop?

I'm not aware of any way to determine that programmatically. The issue is that it's the same machine which you connect to whether you are in desktop or browser (you could even connect from both at the same time) and so even if there was a method, we would probably run into a lot of confusing scenarios.
That said, I don't think your scenario will work at all in browser right? In that case, what is the benefit of knowing that you are in a browser?

Well currently I have a ENV var https://#{ENV['CODESPACE_NAME']}-8080.githubpreview.dev/ for if CODESPACES true
and put the port to Public so it works in browser, but not desktop (which would be localhost instead)

So it would be nice to see maybe like if I'm running in desktop version I can use localhost

Thanks for replies @cmbrose!
@dinushkaherath how are you setting that env var? Depending on where you're setting it there might be a way to determine browser vs. desktop.

Hmmmm I'm setting it from my Rails App, maybe I could do a javascript check for window url...

Thanks


Conda

Added conda packaging

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   63.38%   63.38%
=======================================
  Files           3        3
  Lines          71       71
=======================================
  Hits           45       45
  Misses         26       26

Continue to review full report at Codecov.

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


Thanks very much

when I use the api funciton, I have a error like this:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.opensea.io', port=443): Max retries exceeded with url: /api/v1/collection/cryptopunks (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x0000010A51A36D90>: Failed to establish a new connection
I had check my web and vpn.

Hi @kaifeitudou ,
Seems unrelated to the wrapper library. Is this still an issue? Feel free to re-open if needed.

Thank you very much.


Installation Problem

I have a server where I can not upgrade  my system (I use RHEL 5.5) I have some issue on library. If I try to use  pre compiled  version I have this error:
/pizzly: symbol lookup error: ./pizzly: undefined symbol: _ZNSt7__cxx117collateIcE2idE
Could you please help me?
thanks so much

The binary works with centos 6 (rhel 6) or later. Because we use c++14, which requires a recent gcc this was the best I could do.
If you have access to another machine you can move the fusion.txt files there and run them there.
I will look into making this work for older systems, but I don't know if it will work properly.

thanks so much!

I've put some effort into this and it seems that gcc 5 and later is not compatible with rhel 5 since the glibc is too old. This makes it pretty much impossible to distribute binaries for older systems, so we will be focusing on centos/rhel 6 or later.


Unable to install this plugin

I'm unable to install this plugin. Install give the error:

<EMAIL_ADDRESS>preinstall C:\Users\AGARAG~1\AppData\Local\Temp\apm-install-dir-117017-17680-lop6d7\node_modules.staging\modular-snippets-3279cda4
mkdir -p "${ATOM_HOME:-$HOME/.atom}"/snippets

La sintassi del nome del file, della directory o del volume non è corretta.
Errore occorso durante l'elaborazione: ${ATOM_HOME:-$HOME/.atom}/snippets.
That means file, directory or volume syntax error

I am having the same issue on my Win7 machine

me too, on Windows 10

Hello.  Same issue:
The filename, directory name, or volume label syntax is incorrect.
Error occurred while processing: ${ATOM_HOME:-$HOME/.atom}/snippets.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\user\AppData\Local\Temp\apm-install-dir-11759-13264-1gihbxb.4xyainqaor\package.json'
I'm running atom which was installed through Chocolatey if that makes a difference.

This error hasn't been resolved yet, right? Because it still occurred to me too (Win10) --> the log-file mentioned to be sent does not exist after the installation fails, because it's a temporary directory.
If the above commit can solve, please merge.

Same won't install on Windows
Installing<EMAIL_ADDRESS>failed

mkdir -p "${ATOM_HOME:-$HOME/.atom}"/snippets

This is not going to get updated is it?
I was really hoping to be able to have project-specific snippets.

Dirty workaround to make installation work:

download this package source code from Github
Unpack in .atom\packages\atom-modular-snippets
Edit with Notepad file: package.json
Delete line:     "preinstall": "mkdir -p "${ATOM_HOME:-$HOME/.atom}"/snippets"
run commandline/terminal (cmd)
Change directory to package folder (cd "C:\Users[xxxxx].atom\packages\atom-modular-snippets")
Type in: apm install
Create /snippets folder ("C:\Users[xxxxx].atom\snippets")
Profit (I've made it to work)
If something goes wrong do: apm uninstall atom-modular-snippets

If you can fix the line "preinstall": "mkdir -p "${ATOM_HOME:-$HOME/.atom}"/snippets" and fork this package, please do so :)


Tests are failing with an exception

Are the tests passing for other people?  They fail with an exception for me.  I'll work this out but figured it would be worth checking here.
/epc/t/313/pysunspec/venv/bin/python scripts/pysunspec_test.py
pySunSpec version: 1.0.7
Test device path: /epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/devices

Traceback (most recent call last):
  File "scripts/pysunspec_test.py", line 13, in <module>
    test.test_all()
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/test_all.py", line 58, in test_all
    (count_run, count_passed, count_failed) = module.test_all(pathlist, stop_on_failure)
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/test_device.py", line 577, in test_all
    if test(pathlist) is True:
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/test_device.py", line 418, in test_device_from_pics
    d1.from_pics(filename='pics_test_device_1.xml', pathlist=pathlist)
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/device.py", line 127, in from_pics
    raise SunSpecError('Error loading PICS: %s' % str(e))
sunspec.core.util.SunSpecError: Error loading PICS: Block index out of range: 1

Or, with an except removed to see the original trace:
/epc/t/313/pysunspec/venv/bin/python scripts/pysunspec_test.py
pySunSpec version: 1.0.7
Test device path: /epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/devices

Traceback (most recent call last):
  File "scripts/pysunspec_test.py", line 13, in <module>
    test.test_all()
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/test_all.py", line 58, in test_all
    (count_run, count_passed, count_failed) = module.test_all(pathlist, stop_on_failure)
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/test_device.py", line 577, in test_all
    if test(pathlist) is True:
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/test/test_device.py", line 418, in test_device_from_pics
    d1.from_pics(filename='pics_test_device_1.xml', pathlist=pathlist)
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/device.py", line 120, in from_pics
    model.from_pics(m)
  File "/epc/t/313/pysunspec/venv/lib/python2.7/site-packages/sunspec/core/device.py", line 481, in from_pics
    raise SunSpecError('Block index out of range: %s' % (str(block_index)))
sunspec.core.util.SunSpecError: Block index out of range: 1

You must checkout the sunspec/models repository then things work better.  In my fork I added it as a submodule (7e483f9bc6fb23d1e51bb4f043df4b707b138db5).

This error is not at all obvious, I just spent too much time tracking this down on my own, until thinking to take a look at the closed issues. I discovered the fix only after reverting to 1.0.6 and noticing the models directory. Why not just include the models directory in 1.0.7 to save people like me trouble?

I am sorry this caused you to waste some time. The models are included with every release. The pysunspec-1.07.zip is the 1..0.7 release in the standard Python format. If you install the release in the standard way, the models are included. If you pull the source code directly, you will only get the source code. The models are in a separate repository because they are used in other places and are independent of any on the Python projects.

As in 7e483f9, the models could be included as Git submodules.  That would at least use the 'standard' Git tool for linking repositories.  That said, many people would still likely miss it (myself included).  Seems to me that it would be reasonable to have an explicit check for that directory which raises an exception when it is not found and provides both a direct message as to what is wrong ('Models are not available in standard location') as well as instructions to correct the issue ('Checkout http://github.com/sunspec/models into the ... directory').  Or, Git submodules instructions, if that is how they will be acquired.  Libraries and applications also often allow for environment variables to specify non-standard locations for 'external' resources.
Another approach focusing on the Python side would be to integrate fetching of the modules into setup.py.  Though, the checks and error reporting listed above would likely still be applicable.
If models isn't going to become a Git submodule I would recommend it exist outside of the checked-out pysunspec Git repository rather than as a subdirectory.  I personally find nested unrelated repositories confusing.


unable to start cloud recording in plugnmeet

plugnmeet client and recording server are in different servers.

error log:
2024-01-23T05:16:32.388Z info: Main: 0
2024-01-23T05:16:40.859Z info: new recording task for RM_jf2Cc9sBHhmh
2024-01-23T05:16:44.195Z error: connect ECONNREFUSED <IP_ADDRESS>:80

2024-01-23T05:18:07.109Z info: Main: 0
2024-01-23T05:18:15.615Z info: ffmpeg options: -y,-i ,../recording_files/node_01/RM_jf2Cc9sBHhmh/RM_jf2Cc9sBHhmh-1705986992291.webm,-movflags,faststart,-c:v,copy,-preset,veryfast,../recording_files/node_01/RM_jf2Cc9sBHhmh/RM_jf2Cc9sBHhmh-1705986992291.mp4
2024-01-23T05:18:16.622Z info: page on close
2024-01-23T05:18:16.717Z info: browser on disconnected
2024-01-23T05:18:17.178Z info: new recording task for RM_jf2Cc9sBHhmh
2024-01-23T05:18:20.008Z error: connect ECONNREFUSED <IP_ADDRESS>:80
2024-01-23T05:18:20.455Z error: connect ECONNREFUSED <IP_ADDRESS>:80
2024-01-23T05:18:24.385Z info: Conversion done to here: ../recording_files/node_01/RM_jf2Cc9sBHhmh/RM_jf2Cc9sBHhmh-1705986992291.mp4
2024-01-23T05:18:27.834Z error: connect ECONNREFUSED <IP_ADDRESS>:80

2024-01-23T05:18:20.008Z error: connect ECONNREFUSED <IP_ADDRESS>:80
It wasn't able to connect.

but 80 port doesn't use for recording

yes. configs are already their. but when starting cloud recording following error occurred.

logs:
2024-01-26T06:52:24.040Z info: new recording task for RM_XQyPAzpr489E
2024-01-26T06:52:31.135Z info: Conversion done to here: ../recording_files/node_01/RM_XQyPAzpr489E/RM_XQyPAzpr489E-1706251885984.mp4
2024-01-26T06:52:34.675Z error: connect ECONNREFUSED <IP_ADDRESS>:80
2024-01-26T06:53:50.950Z info: Conversion done to here: ../recording_files/node_01/RM_XQyPAzpr489E/RM_XQyPAzpr489E-1706247949885.mp4
2024-01-26T06:53:54.395Z error: connect ECONNREFUSED <IP_ADDRESS>:80

config.yaml:
recorder:
  id: node_01
  max_limit: 10
  # you can set it true, if you want to get MP4 as output
  # this will require more times & CPU for encoding
  post_mp4_convert: true
  # use it if you want to use custom chrome
  custom_chrome_path: ""
  # this is optional. You can set the width and height of recorded virtual window which will result in
  # recorded video with same resolution
  width: 1800
  height: 900
  # this is optional. using this variable you can change the DPI for xvfb virtual window, change this to
  # improve the picture clarity but with impact on performance and compatibility
  xvfb_dpi: 200
  copy_to_path:
    # plugnmeet-server should have access this path otherwise user can't download recordings.
    # this path can be NSF or other network path too but make sure nodejs has permission
    # to write this path.
    main_path: "../recording_files"
    # this is optional. If you set this path then it will be included with recording
    # and store in database. This path should be inside main_path. Sometime user want to
    # use specific recording directory for this particular recorder.
    sub_path: "node_01"
  # You can use post-processing scripts for a further process the recording
  # you can find example from post_processing_scripts/example.js
  #post_processing_scripts:
  # should be a full path & make sure nodejs has permission to access
  #  - "./post_processing_scripts/example.js"
# here you can set your custom ffmpeg options
ffmpeg_options:
  recording:
    # any option to set before -i
    pre_input: ""
    post_input: "-movflags faststart -c:v copy -preset veryfast"
  rtmp:
    # any option to set before -i
    pre_input: ""
    post_input: "-c:v libx264 -x264-params keyint=120:scenecut=0 -b:v 2500k -video_size 1280x720 -c:a aac -b:a 128k -ar 44100 -af highpass=f=200,lowpass=f=2000,afftdn -preset ultrafast -crf 5 -vf format=yuv420p -tune zerolatency"
plugNmeet_info:
  # http://localhost:8080
  host: plugnmeet.example.com
  api_key: ############################
  api_secret: #####################################
  # join_host is optional. Use it if plugNmeet-client installed in different place
  # if it's live server then should be https link otherwise won't work.
  # format: https://PLUG_N_MEET_SERVER_DOMAIN/?access_token=
  join_host: "https://plugnmeet.example.com/?access_token="
websocket_server:
  host: "ws://localhost"
  port: 4000
  # openssl rand -hex 10
  # OR
  # cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 10 | head -n 1
  auth_token: ##################################3
redis_info:
  host: localhost
  port: 6379
  username: ""
  password: "####################"
  db: 7
#  use_tls: false
#  To use sentinel remove the host key above and add the following
#  sentinel_master_name: plugnmeet
#  sentinel_addresses:
#    - redis-sentinel-host-1:26379
#    - redis-sentinel-host-2:26379
#    - redis-sentinel-host-3:26379
#  If you use a different set of credentials for sentinel add
#  sentinel_username: user
#  sentinel_password: pass


Project status

Update: I don't have much bandwidth for this project these days, but happy to help with anything critical, and/or help transition knowledge to new maintainers.
cc @RichardLitt

Thanks for updating me, @harlantwood. :) I will be working on this more this quarter. I'm not sure I need much more knowledge to maintain this.

Excellent.

Let's close this as I've got it and it isn't actionable. Thanks again, @harlantwood.


Updata README.md

Fix typo

Codecov Report

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

@@            Coverage Diff            @@
##             master     #108   +/-   ##
=========================================
  Coverage          ?   88.66%
  Complexity        ?      665
=========================================
  Files             ?       47
  Lines             ?     1465
  Branches          ?        0
=========================================
  Hits              ?     1299
  Misses            ?      166
  Partials          ?        0

Continue to review full report at Codecov.

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

@sunshuzhou Thanks for this PR!


missing camera access permissions issue#111

Thanks for the contribution but I'm closing this as it's no longer relevant for v2.


Update the "Events and Timelines" docs page

What
That doc page was named "Events and Timelines", but no mention was made of what event are. This PR fixes this, as well as add rust and c++ version of the example snippet.
The code snippets are incomplete and thus excluded from roundtrip tests. Supporting hide-able stubs would allow fixing this (https://github.com/rerun-io/landing/issues/515).

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)
[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

rebase on main to fix CI

Arg and of course it fails linting... we really need #4047


Update styling customization documentation links and add to all elements

Once the articles in https://github.com/vaadin/vaadin-themable-mixin/wiki find their final place on vaadin.com, update the links in all element API docs to point to that instead of the current Lumo theme documentation on cdn.vaadin.com (for example: https://github.com/vaadin/vaadin-context-menu/blob/master/vaadin-context-menu.html#L196)
Add the same link to all existing elements – some of them are missing the link (like grid and button).

The articles have found their place now:
https://vaadin.com/docs/v14/themes/themes-and-styling-overview.html

More likely to be this URL: https://vaadin.com/docs/latest/theming/overview/

More likely to be this URL: https://vaadin.com/docs/latest/theming/overview/


update to latest API

Resolved in https://github.com/mpsd-computational-science/octopus-toolchain-docs/pull/5 .


Remove own

Replaces https://github.com/Tradeshift/elasticsearch-srv-discovery/pull/2
This is done to avoid trying to connect to your self when joining a cluster

There is a lot of logger.info on this one. It adds about 30 lines for logging on a normal ES startup.
But it's very usefull when the cluster is not forming to have that output.

:+1:


[Bug]: Fix vulnerability flagged by dependabot

Contact Details
No response
Tell us the project / group you are associated with
Community (Default)
What happened?
Vulnerabilities flagged by dependabot:
https://github.com/vmware-tanzu/graph-framework-for-microservices/security/dependabot
Describe the expected behavior
No response
What version are you running?
No response
How critical is this bug to you?
Blocker - solution is unusable
How can we recreate the bug?
No response
Any debug data that you are able to share?
No response
What is your operating system?
None
Any additional / relevant info
No response

New JIRA Created with ID: https://jira.eng.vmware.com/browse/NPT-906