Multiple Web Containers on Same Page

Is your feature request related to a problem? Please describe:
I want to use WebContainer in my docs website where there will be multiple examples with live preview. Currently the webcontainer docs mention that WebContainer.boot() can only be called once. So I am unable to have multiple webcontainers on one page of doc.
Describe the solution you'd like:
A way to call WebContainer.boot() multiple times
Describe alternatives you've considered:
Another alternate approach would be to have some way to unboot. So we can boot the webcontainer that is visible on screen.
Additional context:

:wave: Thanks for the report! We are actually considering lifting the restriction a bit, and allowing to boot() again after a teardown().
We're tracking this internally, so we will update this issue if/when relevant.


Support for optional pull model

As proposed by Lucas here, this issue is a place for collecting ideas on how to implement an optional pull model...

I just created a very simple example on how stuff could look like:
https://gist.github.com/MPK1/8765fc25bb98d437491ebcc6c55d09a9


[AutoRelease] t2-eventgrid-2022-06-13-17101(Do not merge)

https://github.com/Azure/sdk-release-request/issues/2908
Live test fail, detailed info is in pipeline log  (fixed)
https://dev.azure.com/azure-sdk/internal/_build?definitionId=993
BuildTargetingString
azure-mgmt-eventgrid
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/2908

/azp run


Uninterpretable bug with legal_actions check

Hi there, I'm trying to use Openspiel in a project where all games share a common API with PettingZoo, and due to the architecture of the system, the stepping of  the environment looks something like so (modified from the first example code):
P/S: This bug only occurs on backgammon AFAICT.
import random
import pyspiel
import numpy as np

game = pyspiel.load_game("backgammon")
state = game.new_initial_state()
while not state.is_terminal():
    legal_actions = state.legal_actions()

    if state.is_chance_node():
        # Sample a chance event outcome.
        outcomes_with_probs = state.chance_outcomes()
        action_list, prob_list = zip(*outcomes_with_probs)
        action = np.random.choice(action_list, p=prob_list)
        state.apply_action(action)

        for i in range(game.num_players()):
            print("----------")
            print(i)
            print(state.legal_actions(i)) # FAILS HERE

    if not state.is_chance_node():
        # The algorithm can pick an action based on an observation (fully observable
        # games) or an information state (information available for that player)
        # We arbitrarily select the first available action as an example.
        action = legal_actions[0]
        state.apply_action(action)

        for i in range(game.num_players()):
            print("----------")
            print(i)
            print(state.legal_actions(i))

For some reason, when trying to get legal_actions after executing any and all possible chance nodes, the following stack trace is raised:
OpenSpiel exception: /project/open_spiel/games/backgammon.cc:848 board_[player][i] >=
board_[player][i] = -2, 0 = 0
Traceback (most recent call last):
  File "/home/jet/Sandboxes/Shimmy/src/bugfinder.py", line 20, in <module>
    print(state.legal_actions(i))
pyspiel.SpielError: /project/open_spiel/games/backgammon.cc:848 board_[player][i] >= 0
board_[player][i] = -2, 0 = 0

Following this trace leads me to this section of the code in /open_spiel/open_spiel/games/backgammon.cc:
int BackgammonState::CountTotalCheckers(int player) const {
  int total = 0;
  for (int i = 0; i < 24; ++i) {
    SPIEL_CHECK_GE(board_[player][i], 0); // THIS LINE
    total += board_[player][i];
  }
  SPIEL_CHECK_GE(bar_[player], 0);
  total += bar_[player];
  SPIEL_CHECK_GE(scores_[player], 0);
  total += scores_[player];
  return total;
}

I have further tried browsing around the code to see what that SPIEL_CHECK_GE actually does, but cannot seem to find its definition.
So my question is, what is that error and why is it not possible to get legal actions after executing chance nodes?

Could be terminal, maybe? Hard to tell without seeing the state.
Chances are PettingZoo and OpenSpiel are implementing the game differently.
Can you add a try/catch around that line that fails, and print the output of pyspiel.serialize_game_and_state(game, state) ? Then we can try to reload the state to inspect it.

(Might actually be easier to just print the state and the action you're taking each time.)
print(state)
print(f"Taking action {state.action_to_string(player, action)}")

Wait:
        for i in range(game.num_players()):
            print("----------")
            print(i)
            print(state.legal_actions(i)) # FAILS HERE

You're calling legal actions on all the players... why? That might be your answer. Backgammon is turn-based, there's only one player playing at any given turn (including chance).

Ok I've reproduced it in colab. Hmm... yeah.. something is fishy here; definitely seems like a bug (oddly our simulations tests are not catching it).

Thanks for the quick reply! The repo where we are doing the work is here, I've confirmed that this bug only occurs on backgammon.

Ok yeah I see the problem: it appears to be with the script you have above, not in the game (which explains why our simulation tests are not running into it).
It is taking illegal moves and then getting the state into a bad state. Excerpt with fix below:
    #  .
    #  .
    #  .
    if not state.is_chance_node():
        # The algorithm can pick an action based on an observation (fully observable
        # games) or an information state (information available for that player)
        # We arbitrarily select the first available action as an example.
        # action = legal_actions[0]   # PROBLEM WAS HERE -- legal_actions list has not been updated since the last state.apply_action, so the first element in this list can be illegal
        # Fix is to comment the line above, and replace it with:
        action =  state.legal_actions()[0]
        state.apply_action(action)

    # .
    # .
    # .

BTW we added a flag to the RL environment to check for legality of the moves submitted by the agent: https://github.com/deepmind/open_spiel/blob/97a199a3276ef35b932f39dc01786855aa36545f/open_spiel/python/rl_environment.py#L152.
I would recommend enabling this while debugging as it will catch some problems without the mysterious opaque crash in the game state at some other point. (We disable it by default for performance reasons.)

Thanks for the help! Just updating here that the solution above worked. :)


Delete GET /api/students/ (we do not need this endpoints - because it response with data non-attached students to any of Caregivers)

to delete this issue!!!

deleted this issue


[Feature]: Support for rhymes-ai/Aria

🚀 The feature, motivation and pitch
Hope for vllm support rhymes-ai/Aria.
hugging face link is : https://huggingface.co/rhymes-ai/Aria
Alternatives
No response
Additional context
No response
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

See: https://github.com/rhymes-ai/Aria/blob/main/docs/inference.md#3-high-performance-inference-with-vllm

I got the error
ValueError: Model architectures ['AriaForConditionalGeneration'] are not supported for now
when running
vllm serve rhymes-ai/Aria
Does this mean Aria isn't fully supported?

@thanhnguyentung95  To use OOT multimodal model serveing, you need to wrap the Openai Server entrypoint:
from vllm import ModelRegistry
from vllm.model_executor.models import _MULTIMODAL_MODELS

from aria.vllm.aria import AriaForConditionalGeneration

ModelRegistry.register_model(
    "AriaForConditionalGeneration", AriaForConditionalGeneration
)
_MULTIMODAL_MODELS["AriaForConditionalGeneration"] = (
    "aria",
    "AriaForConditionalGeneration",
)

if __name__ == '__main__':
    import runpy
    runpy.run_module('vllm.entrypoints.openai.api_server', run_name='__main__')

Save the above code in a file and run it with python your_file.py <args> just like vllm serve <args>

Quick update that you shouldn't update from _MULTIMODAL_MODELS anymore - we now detect models based on whether they implement the multimodal interface, as described here.


Pedestrian hospitalizations

Pedestrian Hospitalizations per 100k Residents
Pretty straightforward. Like other QOL indicators this is already aggregated, we just need to plug in numbers from csv we get from a link.
The metric we need is calculated for citywide and by borough, but it's calculated by community district instead of puma. The crosswalk xlsx file at [https://www1.nyc.gov/assets/planning/download/office/data-maps/nyc-population/census2010/nyc2010census_tabulation_equiv.xlsx] that Te used in the QOL educational for NTA to PUMA can also be used for CD to puma.
I loop through a dataframe to get the dictionary from CD to puma. I try not use for loops to iterate through dataframes but it was the best way to move forward here.
For PUMAs that span two CD's, I calculate an average between the two CD's and report that number.
Some CD's are null in the source data, the portal says this is for "confidentiality reasons".

Next I can work on getting the .csv in through data library if that's how we want to manage source data

The answer to your last question is yes. It's not the best way to get that info but it was the easiest.
Glad you think the code is clear


Don't know how to build task 'db:multi_spork:clone'

Subj :)

You need to put the gem inside development group as specified inside the readme.


Added BasicGUI.py File

Created a GUI Interface #5

Nice work! Could you integrate the execution of main.py file with it too?

Sure, I have my semester exam tommorow ,I'll do it ASAP.
On 21-Dec-2018 8:18 pm, "Shikhar Johri"<EMAIL_ADDRESS>wrote:

Nice work! Could you integrate the execution of main.py file with it too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/johri002/Automatic-leaf-infection-identifier/pull/17#issuecomment-449407421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkXvdr7C8NcIdSOQY6hEyTECS3d3lDvUks5u7PTUgaJpZM4ZZS2x
.

I have integrated the same file.Kindly check it out.
Sorry for slow response .This was due to end sem exams
Thank You
On 12/21/18, Vishal Singh<EMAIL_ADDRESS>wrote:

Sure, I have my semester exam tommorow ,I'll do it ASAP.
On 21-Dec-2018 8:18 pm, "Shikhar Johri"<EMAIL_ADDRESS>wrote:

Nice work! Could you integrate the execution of main.py file with it too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/johri002/Automatic-leaf-infection-identifier/pull/17#issuecomment-449407421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkXvdr7C8NcIdSOQY6hEyTECS3d3lDvUks5u7PTUgaJpZM4ZZS2x
.


The Double-Bladed Weapon and Spear need better in-hand models.

The double-bladed weapon is being held on the lower blade and not the handle, and the spear is the size of a stick.

fixed in the next update 👍


[REQUEST] ability to use specified proxies and auto stop after x number of to check

Is your feature request related to a problem? Please describe.

Allow the use of specific proxies for specific configs, perhaps an option to load a specified list of proxies for a specific config. (This is needed as some services only available for that particular country)
auto stop the process after to check tab combos reaches a certain threshold. This is to prevent further combos to be sent to the to check and it won't require ob to waste resources and eventually crashing the program. So if consecutive combo keep going to the to check tab, stop the cracking process.

Refer to this https://github.com/openbullet/openbullet/issues/468
This will be done in the scheduler update which is already planned.
Closing the issue as both requests will be tracked elsewhere


requires two operands error, when \yii\db\Expression used  in OR where statement

Hi
I want use \yii\db\Expression with OR , but I get Operator '...' requires two operands , on /yiisoft/yii2/db/QueryBuilder.php line 1381.
my code:
       $query = model::find();
       $condition = 'EXISTS (....)';
       $query->andWhere([
            'OR',
            ['t.user_id' => 10],
            [new \yii\db\Expression($condition)],
        ]);

I changed my a algorithm  and got result. but I think top algorithm Must have worked.

I'm sorry.
I removed [,] fro befor and after new \yii\db\Expression($condition) , and worked.
thanks

we can also use
$query = model::find();
$query->andWhere([ 'OR', "{$this->tblName}.order_status_id!= 3 and {$this->tblName}.order_status_id!= 1"])


findChats | findContacts issue

I'm trying to retrieve the list of chats I have on WhatsApp. I think I need to fetch it from the findChats endpoint and then, using the RemoteJid, make another request to findContacts. However, the response I'm getting is completely unexpected. I'm receiving a list of several objects with the same RemoteJid, and these objects also have pushName as null.
How can I fetch the chats and the contact information for each chat to build the list of active chats?

Esse comportamento ainda persiste?

Sim

Esse comportamento ainda persiste?

Esse comportamento é bem incomum. Delete esses contatos e se reconecta.
Informe aqui se o erro ainda persiste.


How to get the lstpu for windows 10?

Hi google members:
The cts tool need the lstpu binary for test. How to get the lstpu for windows 10? I build the lstpu tools by the following sources but the following comment say only support "k8, armv7a, aarch64" platform. Could you give some suggestions for this.
Thank a lot!
https://github.com/google-coral/tflite/tree/master/cpp/examples/lstpu/Makefile
Allowed CPU values: k8, armv7a, aarch64

I can get the following package for lstpu on windows 10
https://github.com/google-coral/cts/releases/tag/v1.0
coral-cts-windows.zip


I want tot change Moksh Logo on the header

Description:
I wish to change the moksh logo which is on the header
Reason for Change:
current one is also good , But i want to enhance the logo which looks more realistic to meditation as well as related to website
Current Styling:
[Describe the current styling that needs to be changed.]
Proposed Styling:
[Describe the desired styling or changes you would like to see.]
Screenshots or Design Mockups (optional):
iThe image which i wish to add i upload in this section

Additional Information (optional):
[Provide any additional information that may help in understanding or implementing the style change. This can include any specific requirements or constraints.]

Priority Level (optional):

[ ] Low
[ ] Medium
[ ] High

Timeline (optional):
only  1 day to implement this
Possible Implementation Approach (optional):
[If you have any suggestions or ideas on how the style change could be implemented, feel free to provide them here.]

currently not required


Add Rspec spec on controllers

[x] Added RSpec as a gem to your project.
[x] Created a Request spec file for all your controllers.
[x] Made sure that each action I check:

If the response status was correct.
If a correct template was rendered.
If the response body includes the correct placeholder text.

@Nemwel-Boniface; could you please elaborate on the changes on the zoom call? Everything is passing on my side

@Nemwel-Boniface The project is running well and tests passing on my side.

@AnselemOdims; could you mind a zoom call, please?


Change Inbound and Outbound algorithm map from static to instance based

Because of algorithm mapping being static, tests fail since some of the tests update the maps with custom values, other tests see these custom mapped values and fail.
E.g. in CreateAndValidateTokenTests.ExtensibilityTests.cs, inbound alg map is updated
originalAlgorithmValue = ReplaceAlgorithm(newAlgorithmValue, SecurityAlgorithms.RsaSha256Signature, JwtSecurityTokenHandler.InboundAlgorithmMap);
RunAlgorithmMappingTest(jwt.RawData, IdentityUtilities.DefaultAsymmetricTokenValidationParameters, handler, ExpectedException.NoExceptionExpected);
ReplaceAlgorithm(newAlgorithmValue, originalAlgorithmValue, JwtSecurityTokenHandler.InboundAlgorithmMap);
even if the test is putting the original value back, other tests (Multiple X5c) still see the "newalgorithmvalue" and fails.
This is prevented currently using
-[assembly: CollectionBehavior(CollectionBehavior.CollectionPerAssembly)] attribute in assembly info.cs. but we should fix this behavior.

We are just going to remove the mapping.

RC1 fixes. #300


MouseCusor for GShape

Hi:
as well as we know, We can set different mouse cursor for a child widget on flutter use MouseRegion, and I am not sure how to apply set mouse cursor on Shape region.
a solution is :
#1. a Stage level mouse move event handler, and use hittest for check which child already hit, then change mouse cursor ?
#2.  configure mouse curosr for a shape.

Sorry for the super late reply.
As GraphX was originally made to emulate ActionScript API, the only automatic cursor change available from any DisplayObject is basic and click:
var someShape = GShape();
someShape.useCursor = true ;

You can always change the mouse (SystemMouseCursors) yourself though, you have 2 (manual) options in GraphX:
through the stage:
stage?.pointer?.cursor = SystemMouseCursors.resizeDown;
globally (the old AS3 way):
GMouse.cursor = SystemMouseCursors.copy;
So, if you need custom mouse while hovering a GShape you can do this:
theShape.onMouseOver.add((_) {
  GMouse.cursor=SystemMouseCursors.alias;
  theShape.onMouseOut.addOnce((_) => GMouse.basic());
});

Hope it helps.


SWC plugin

Isograph currently has a Babel plugin. We also need an SWC plugin that does the exact same thing: transform iso(`entrypoint Query.foo`) calls to require('@iso/Query/foo/entrypoint').

This should be a fairly easy project if you're looking to get involved with Isograph!

Being worked on by @edmondop

@edmondop how is this going? :D do you have a POC I can help test? 😊

@patrick91 I was keeping this on hold, I asked on a forum about tracing/logging.  Would you have time to ivnestigate this?
https://github.com/swc-project/plugins/discussions/350


findFirstSetBitZeroIdx() does not work correctly for small morton code

The function findFirstSetBitZeroIdx() does not work correctly for small (<= 4byte) morton values when compiling on 64-bit Linux using gcc or clang.
const uint32_t x = 545658634;
unsigned long c;
findFirstSetBitZeroIdx(x, c); // Expected: c == 29

The issue is that internally, the builtin function __builtin_clzll is used for all inputs, i.e. the input variable x is cast to unsigned long long. For the ID above, __builtin_clzll returns 34, which is correct if x were a 64-bit integer.
But that result is substracted from sizeof(morton) * 8, which in this case is 32.
In the end we have 32 - 34 -1, cast to unsigned long, which is an integer overflow.
Possible fix:
*firstbit_location = static_cast<unsigned long>((sizeof(unsigned long long) * 8) - __builtin_clzll(x) - 1);

Fixed in latest release


Parse identifiers with human readable identifier

from #118
Technology Report:
IEC Technology Report Ontology standards in smart cities:2023
IEC Technology Report Cyber security:2019
IEC Technology Report Ontology standards in smart ci:2023
IEC Technology Report Future sustainable transport:2022
IEC Technology Report LVDC:2017
IEC Technology Report City information modelling:2021
IEC Technology Report Nanotechnology:2013

White Paper:
IEC White Paper Edge intelligence:2017
IEC White Paper QIT:2021
IEC White Paper EES:2011
IEC White Paper AI:2018
IEC White Paper Microgrids:2014
IEC White Paper IoT Platform:2016
IEC White Paper IoT:WSN:2014
IEC White Paper Future Factory:2015
IEC White Paper Zero carbon power system:2022
IEC White Paper Stable grid:2018
IEC White Paper GEI:2016
IEC White Paper Smart Cities:2014
IEC White Paper Asset Management:2015
IEC White Paper Safety in the future:2020
IEC White Paper RE-EES:2012
IEC White Paper Semantic interoperability:2019
IEC White Paper Energy Challenge:2010

Trend Report:
IEC Trend Report Digital healthcare:2021
IEC Trend Report DC power distribution:2022
IEC Trend Report Virtual sensors:2022

fixed in #104 and #107


Exception while executing: if test ! -d $HOME/.rbenv/plugins/ruby-build; then echo "Directory does not exist '$HOME/.rbenv/plugins/ruby-build'" 1>&2; false; fi exit status

We are trying to upgrade to Ruby 3 and Rails 6.1. Currently everything works fine with Ruby 2.5.3 and Rails 5.2. When trying to deploy the new upgrade we're getting this error:
/home/ec2-user/.rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/sshkit-1.21.2/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute': Exception while executing as ec2-user@: Exception while executing as ec2-user@: if test ! -d \\$HOME/.rbenv/plugins/ruby-build; then echo "Directory does not exist '\\$HOME/.rbenv/plugins/ruby-build'" 1>&2; false; fi exit status: 1 (SSHKit::Runner::ExecuteError)
Exception while executing: if test ! -d \$HOME/.rbenv/plugins/ruby-build; then echo "Directory does not exist '\$HOME/.rbenv/plugins/ruby-build'" 1>&2; false; fi exit status

With our upgrade no versions of capistrano or rbenv has changed. Here are our versions:
    capistrano (3.16.0)
      airbrussh (>= 1.0.0)
      i18n
      rake (>= 10.0.0)
      sshkit (>= 1.9.0)
    capistrano-bundler (2.0.1)
      capistrano (~> 3.1)
    capistrano-rails (1.6.1)
      capistrano (~> 3.1)
      capistrano-bundler (>= 1.1, < 3)
    capistrano-rbenv (2.2.0)
      capistrano (~> 3.1)
      sshkit (~> 1.3)
    capistrano-rbenv-install (1.2.0)
      capistrano (>= 3.0)
      capistrano-rbenv (>= 2.0)
    capistrano-sidekiq (1.0.3)
      capistrano (>= 3.9.0)
      sidekiq (>= 3.4, < 6.0)
    capistrano-upload-config (0.8.2)
      capistrano (>= 3.0)
    capistrano3-puma (3.1.1)
      capistrano (~> 3.7)
      capistrano-bundler

If I change back and try to deploy ruby 2.5.3 and rails 5.2 everything works fine. All of the gems above are the same in both. The directory $HOME/.rbenv/plugins/ruby-build definitely exists either way.
We have the following defined:
set :rbenv_type, :user
set :rbenv_ruby, ruby_version_from_repo
set :rbenv_prefix, "RBENV_ROOT=#{fetch(:rbenv_path)} RBENV_VERSION=#{fetch(:rbenv_ruby)} #{fetch(:rbenv_path)}/bin/rbenv exec"
set :rbenv_map_bins, %w{rake gem bundle ruby rails sidekiq sidekiqctl puma pumactl}
set :rbenv_roles, :all # default value

Does rbenv work with Ruby 3 and Rails 6.1? Or am I missing something else here? I've noticed this repo hasn't been updated ina. while, should we look for an alternative solution?

In the error message I see there is a backslash before $HOME in the shell script that is being run:
if test ! -d \$HOME/.rbenv/plugins/ruby-build; ...

Likely that is the cause of the error. The shell is looking for the literal $HOME path instead of expanding the variable.
This was discussed in #88. Unfortunately, the fix caused other problems and had to be reverted.
I think the workaround is to use ~ instead of $HOME. Can you try that? Something like this:
set :rbenv_path, "~/.rbenv"

Also, my guess is that the escaping behavior changed in sshkit at some point, and that is why your upgrade caused this error to appear. Can you check if the sshkit version changed pre- and post-upgrade?

Ah yeah I did look at sshkit but running 1.21.2 on both.
I set rbenv_path (with full path) and that did solve it, thanks. I did see that other thread but I think I got confused between rbenv_prefix and rbenv_path. This workaround should be fine for us. Thanks again

Shouldn't you change line 43 to '~/.rbenv' to fix this before closing it?  I got bit by this too without any setting for rbenv_path.


doc animations are not loading

https://docs.labdao.xyz/getting-started/install-plex
Tested in Chrome and Safari

Solved with #305


pacman: Force makepkg to produce .tar files without extended attributes

Extended attributes are not necessary for pacman to work. Extended
attributes may not even be supported by the file system to which we
extract the files.
And worst of all: pacman cannot handle extended attributes, but simply
stops extracting files when it encounters an extended attribute.
This is particularly nasty when creating packages on a system configured
to cache, say, file integrity information about .exe files in extended
attributes, as the created packages will fail to install any .exe files.
The fix is very easy: simply pass the -no-xattrs option to bsdtar.
Signed-off-by: Johannes Schindelin<EMAIL_ADDRESS>

Why does Tea fail? I do not get this failure here.

Tea is not maintained by MSYS2 and is outdated for about year.
Just ignore it.

Tea is not maintained by MSYS2 and is outdated for about year.
Just ignore it.

Okay. Maybe it should be disabled, then, as it is annoying to see that a PR fails when it should not fail.
In any case, AppVeyor passes, and I think my reasoning is sound (it took a day to figure out what was going wrong here, it's good that it was that easy a fix).
Do you agree?

POSIX attributes aren't supported on Windows anyway so this PR should help indeed.

POSIX attributes aren't supported on Windows anyway so this PR should help indeed.

Well, NTFS supports alternate streams, and that is exactly how Cygwin's getfattr accesses extended attributes on Windows...


Use EDS in xDS policy

This PR changes the LB call in xds policy to use EDS protocol to query the balancer for backend addresses. It uses upb-generated files to encode/decode messages in xds policy.
It includes the following changes:

Replaces the nanopb-generated APIs to upb-generated APIs in xds policy for both the backend query part and the load reporting part. If we keep using nanopb in the load reporting part, there will be duplicate definitions of google_protobuf_Duration.
The backend query part uses EDS.
Delete the nanopb-generated files for grpclb.

Ideally, we should depend on external proto files from Envoy to build, but we are falling back to use pre-generated files due to some build issues.
The implementation part of this PR uses upb files that are pre-generated from Envoy.
The xds_end2end_test uses  src/proto/grpc/lb/v2/xds_for_test.proto that is copied from Envoy.

This change is

The changes under client_channel and test/cpp/end2end are ready for review.

Depends on https://github.com/grpc/grpc/pull/19840

Basic Tests C/C++ MacOS: https://github.com/grpc/grpc/issues/19819, https://github.com/grpc/grpc/issues/19802
Basic Tests Node MacOS: https://github.com/grpc/grpc/issues/19422

PR description updated.


Update Downloads.md

fix ms.technology tag

Docs Build status updates of commit 42bbfba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Downloads.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:warning:Warning

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 4, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'riames' is not a valid Microsoft alias.
Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 0edf311:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 4a7d8f9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 96489a2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 1876b6e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/DISM.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md

Line 33, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 4c59c6e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/DISM.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/SSH.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/SetupWifi.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md

Line 33, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/SSH.md

Line 163, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/SetupWifi.md

Line 98, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/DISM.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/SSH.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md

Line 33, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/SSH.md

Line 163, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/DISM.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/PowerShell.md
:bulb:Suggestion

Details

windows-iotcore/connect-your-device/SSH.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md

Line 35, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/PowerShell.md

Line 75, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

windows-iotcore/connect-your-device/SSH.md

Line 163, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

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

File
Status
Preview URL
Details

windows-iotcore/connect-your-device/DISM.md
:bulb:Suggestion

Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md

Line 35, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 779160a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 28fcb5c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/EmbeddedMode.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Fiddler.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 25da568:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/EmbeddedMode.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Fiddler.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/IoTCoreDefaultApp.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/RemoteDebugging.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/UnitTestsForIoTCore.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/DriverDeployment.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/EmbeddedMode.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Fiddler.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/IoTCoreDefaultApp.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/RemoteDebugging.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/UnitTestsForIoTCore.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/DriverDeployment.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/IoTCorePortingTool.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/PeripheralDrivers.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/PinMappings/PinMappingsRPI.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/SoCsAndCustomBoards.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/CommandLineUtils.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/EventTracing.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 757b492:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/EmbeddedMode.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Fiddler.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/IoTCoreDefaultApp.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/RemoteDebugging.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/UnitTestsForIoTCore.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/DriverDeployment.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/IoTCorePortingTool.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/PeripheralDrivers.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/PinMappings/PinMappingsRPI.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/SoCsAndCustomBoards.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/CommandLineUtils.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/EventTracing.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/NetworkPacketCapture.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/secure-your-device/SecureBootAndBitLocker.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2c9be58:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Downloads.md
:white_check_mark:Succeeded

windows-iotcore/Glossary.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/Bluetooth.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/DISM.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/PowerShell.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SetupWifi.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/EmbeddedMode.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Fiddler.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/IoTCoreDefaultApp.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/RemoteDebugging.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/UnitTestsForIoTCore.md
:white_check_mark:Succeeded

windows-iotcore/developer-tools/python.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/DriverDeployment.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/IoTCorePortingTool.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/PeripheralDrivers.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/PinMappings/PinMappingsRPI.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/SoCsAndCustomBoards.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/CommandLineUtils.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/EventTracing.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/NetworkPacketCapture.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/Overview.md
:white_check_mark:Succeeded

windows-iotcore/secure-your-device/SecureBootAndBitLocker.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot-enterprise.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Reference URL is 404

Hi!
Can you update the reference URL: https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.storage.common

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

ID: 910dab69-65c9-d3b9-4bde-a04320ab8f7d
Version Independent ID: d85d233b-9b65-e24a-390f-1dc1e5844b40
Content: Azure Storage client libraries for .NET - Azure for .NET Developers
Content Source: api/overview/azure/storage.md
Service: storage
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@Bafff which API's doc are you looking for? This SDK was deprecated and some of the documents might have been moved around.

@amishra-dev I was looking for this

Maybe if those links are gone forever can you point me for the latest appropriate docs?

Looks like we should remove the Microsoft.Azure.Storage.Common Reference link since no reference page has never existed.
Is there a reason or something specific you're looking in the Common package? The Common package isn't meant to used as a standalone.
For v12 we have the page for the Azure.Storage Namespace if that's what you're looking for.
https://docs.microsoft.com/en-us/dotnet/api/azure.storage?view=azure-dotnet

Ok, thanks!
If you'll remove this link I would be happy :)


UnknownTopicOrPartition on not yet created topic

I'm using kafka-rust simple cosumer within a rust container togheter with a kakfa container.
This is my docker-compose.yml:
zookeeper:
  image: wurstmeister/zookeeper
    ports:
      - "2181:2181"
kafka:
    image: wurstmeister/kafka
    ports:
      - "9092"
    environment:
      KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
      KAFKA_CREATE_TOPICS: "mediator-request:1:3"
      HOSTNAME_COMMAND: "route -n | awk '/UG[ \t]/{print $$2}'"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
request-service:
    build:
      context:  ./RequestService
    restart: always
    ports:
      - 8999:8999
    depends_on:
      - mongo-request
    command: ["/usr/src/app/wait_for_it.sh", "kafka:9092", "-t", "50", "--", "/usr/src/app/target/release/request_service"]

This is the simple consumer client took from kafka-rust example folder.
extern crate kafka;
extern crate env_logger;

use kafka::consumer::{Consumer, FetchOffset, GroupOffsetStorage};
use kafka::error::Error as KafkaError;
fn main() {
    env_logger::init().unwrap();

    let broker = "kafka:9092".to_owned();
    let topic = "mediator-request".to_owned();
    let group = "mediator-request-group".to_owned();

    if let Err(e) = consume_messages(group, topic, vec![broker]) {
        println!("Failed consuming messages: {}", e);
    }
}

fn consume_messages(group: String, topic: String, brokers: Vec<String>) -> Result<(), KafkaError> {
    let mut con = try!(
        Consumer::from_hosts(brokers)
            .with_topic(topic)
            .with_group(group)
            .with_fallback_offset(FetchOffset::Earliest)
            .with_offset_storage(GroupOffsetStorage::Kafka)
            .create()
    );

    loop {
        let mss = try!(con.poll());
        if mss.is_empty() {
            println!("No messages available right now.");
            return Ok(());
        }

        for ms in mss.iter() {
            for m in ms.messages() {
                println!("{}:{}@{}: {:?}", ms.topic(), ms.partition(), m.offset, m.value);
            }
            let _ = con.consume_messageset(ms);
        }
        try!(con.commit_consumed());
    }
}

In docker-compose i have specified to wait until kafka is ready to accept connections, before start kafka-rust client. But unfortunately i can't wait for kafka creation of 'mediator-topic', so my rust client exited with UnknownTopicOrPartition exception.
Is there any workaround to address this particular issue?

This is outside the scope of kafka-rust. You'll have to figure out a way to wait until the topic exists before running your consumer. In this repo's own integration tests, we did something kind of clumsy, which was to look for a log line in the Kafka docker container, e.g.
docker-compose logs kafka | grep 'Created topic <topic_name>'`

Something better might be to use the official Kafka shell utilities to query the brokers for their topic metadata.


Markdown extention ?

Hi again !
Is there a chance you already have built the markdown extension that convert the exported markdown block to html code ?

What we have in another project is a Sphinx extension. Maybe it can help?
https://github.com/edunumsec2/book/blob/master/src/exts/logic.py

Ok, thanks.
I think that I'll stick to web component inclusion for now.
That more than useful enough for a mkdocs usage.
Thanks for your helpfulness and patience.

OK, no problem!

Hello,
Just so you know, I've finally integrated your app for a simple usage with mkdocs.
That's here : https://mkdocs-logic.forge.apps.education.fr
Thanks again for your work !

Hey @davy39,
This is really great! Awesome!
How are you following up the the updates I'm going to make? Are there specific things from your fork that we should integrate in the main build for your convenience?
Cheers,
J.-P.

Hi,
For now, I've only worked on the mkdocs extension part, hacking your bundle without modifying its source.
It would be great to add an option to the editor ( <logic-editor pymkdownx ....), then use it in the editor to make the markdown output look like {.logic} instead of {logic} :
const markdownBlock = ``\`\`\`{${pymkdownx ? '.'}logic}\n:height: ${embedHeight}\n${modeParam}\n${fullJson}\n\`\`\``

This way i could automatize bundle built from your sources to include it within pymkdown extension.
Do you think that could be the way to do it ?

Sure, looks good. Can you show me the code modifications that you made?
Would it be acceptable if, in order to enable this, you have to call some global setup method like Logic.setExportOptions(...) somewhere?

This was finalized in 793785bd7e4a528e5be3a724c1b8787404ef4e3f.


Use readable form for all size and duration options in config file

What type of enhancement is this?
Configuration, User experience
What does the enhancement do?
There are still many options don't use ReadableSize and ReadableDuration.
grpc
https://github.com/GreptimeTeam/greptimedb/blob/0a9972aa9a24c8a68d9d4fa93f5273924fe6c854/src/frontend/src/service_config/grpc.rs#L24-L27
heartbeat
https://github.com/GreptimeTeam/greptimedb/blob/0a9972aa9a24c8a68d9d4fa93f5273924fe6c854/src/servers/src/heartbeat_options.rs#L20-L23
meta client
https://github.com/GreptimeTeam/greptimedb/blob/9e33ddceeaf14a87f12f3a502d22eda734608533/src/meta-client/src/lib.rs#L22-L31
Implementation challenges
No response

Hi, I would like to work on this one


Texture flaws.

Changing textures via texture atlas editing wont change water that is close-up (still_water_0).  When using both methods with empty .tga file in conjunction with terrain-atlas folder water is changed but then flowers are black.
You can test it with the texture that i attached here. When you delete .tga that is empty texture will change and water that is close will still be default one. I dont know where to change close-up water texture i hope you know. Please take a look at that. The only way that seems to work is to have custom terrain.meta.
testing.zip

Try searching the "environment" folder.

facepalm


Fixed minor rendering issue in documentation code blocks

Some of the code blocks on the quickstart page had an issue where they were rendered as two separate <pre>, making them inconsitent with the others.
Before:

After:

:sparkles: :cake: :sparkles: Thanks @bmispelon!

:rabbit2: :racehorse: :tada:


"no target window" message when running cellulose upon GUI startup on CPU

After downloading everything and walking through the installation steps, when I startup python -m cellpose, the GUI opens, followed shortly by the following message -
qt.pointer.dispatch: skipping QEventPoint(id=1 ts=0 pos=0,0 scn=578.492,284.411gbl=578.492,284.411 Released ellipse=(1x1. 0) vel=0,0 press=-578.492,-284.411 last=-578.492,-284.411 ^ 578.492,284.411) : no target window
An image of the message is attached (with the no target window highlighted - (https://github.com/MouseLand/cellpose/files/13246017/CellPose.message.pdf)
I can load an image, but Cellpose doesn't do anything with it, it can't analyze the image, just beachballs perpetually. Any insights into the error or the source would be a tremendous help.
thanks,
Dan

I'm not 100% sure. Can you try to completely removed the environment (conda env remove -n <name of env>), and then try to reinstall it?

closing due to inactivity


Update FocusManager platform check to include iOS

Both iOS and Android run into issues when the FocusManager starts responding to app lifecycle changes.
Fortunately, this feature is primarily meant for desktop platforms, so the problem can be resolved with a platform check.
fixes https://github.com/flutter/flutter/issues/148475

Currently, the test 'flutter create should tool exit if the template manifest cannot be read' is failing (on multiple branches, not just this one).
My guess is that expectLater has a bug where it doesn't actually await the futures like it should, so the test only succeeds when the future finishes quickly enough.

FYI: this PR introduced a memory leak
https://github.com/flutter/flutter/issues/148985


Doesn't work without the VimL code?

Hey @jacobsimpson,
I have been playing with this and if I understand this comment the vim-example-lua-plugin.vim could be deleted and then the print statement in vim-example-lua-plugin.lua should be executed but I don't see that behavior. Am I interpreting it wrong?

Sorry, I read too fast. The code can be removed, not the file 🙄

@jacobsimpson sorry again but what its the point of the plugin/vim-example-lua-plugin.lua file? It doesn't seem to be called at all

I think you are correct, and it is not getting executed at all. I'm investigating whether or not I am missing something, but it seems to me that it should be deleted.

I removed the file, and some other code that was complicating the example.


Load comics in Hi-DPI

For several months/years now, XKCD comics are in retina definition. However, through the app, they are displayed in standard definition.
This is the HTML of the comic display on the xkcd website :

<img src="//imgs.xkcd.com/comics/russells_teapot.png"
     title="..."
     alt="Russell's Teapot"
     srcset="//imgs.xkcd.com/comics/russells_teapot_2x.png 2x">

So I guess we could reasonably add "_2x" on all images download and, if it doesn't work, default on the standard quality.

Nice, thanks ! Once this is out, I'll probably reinstall the app then :)


8 create database

deploy postgres in docker
add liquibase to backend
create default, dev and docker spring profiles
create first to tables using liquibase
create optional database fixtures
dockerise backend in dockerfile for compose
documentation

Issue is saying >create database<
Surely I can create the entities in the code, it wasn't mentioned in the ticket


Can allure plugin use JSON file format?

What are you trying to achieve?
allure plugin should generate JSON format instant of XML format file
What do you get instead?

Provide console output if related. Use --verbose mode for more details.

Provide test source code if related

### Details

* CodeceptJS version: 3.0.6
* NodeJS Version: v14.16.1
* allure-commandline: 2.13.8
* Operating System: macOS cataline 10.15.7
* **Puppeteer** || webdriverio || protractor || testcafe version (if related)
* Configuration file: codecept.conf.js

plugins: {
    allure: {
      enabled: true,
      outputDir: "./output",
      fullPageScreenshots: true,
      screenshotsForAllureReport: true,
      useCucumberStepReporter: true,
    },
  },

We support Allure 1.x at this moment which generates xml format. If you want Allure 2.x you can ask Allure team to support codeceptjs


Azure Data Studio is very slow on my mac

 I recently installed Azure Data Studio on my mac and it works very slow, what should I do to address this issue?

Azure Data Studio Version:1.41.2
OS Version:13.1

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

@Bahar-Pasha does it help?

@Bahar-Pasha are you using Mac with Apple Silicon and Intel version of Azure Data Studio? If so, please try the Apple Silicon version which will be much faster: https://github.com/microsoft/azuredatastudio#download-the-latest-azure-data-studio-release

I downloaded Apple Silicon Version

@Bahar-Pasha does it help?

I guess it is faster but I am new to SQL and need more time to work with it. Anyway, thanks for your help.

GO command does not work on my Azure data Studio , where should I define it in the setting so that it works ?

@Bahar-Pasha could you please elaborate a bit more? what do you mean by GO command not working?


Automator: update istio/api@master dependency in istio/istio@master

Generated by Automator - 2022-06-02T01:31:32+00:00

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
a303e8505a679b46a4a65992b4312701a6e50249
link
true
/test integ-security-multicluster_istio

integ-pilot-multicluster_istio
aca11250d946d18c74f3186bdf32cc74e329286b
link
true
/test integ-pilot-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
aca11250d946d18c74f3186bdf32cc74e329286b
link
true
/test integ-pilot-multicluster_istio

integ-security-multicluster_istio
aca11250d946d18c74f3186bdf32cc74e329286b
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Update to 1.4.6

This updates the mongo dependency to the latest available version.

@jwalton Thank you, use peer dependency now.


Remove dummy vpc for private-zone module

Background

Update README.md
Remove dummy vpc for private-zone module

Unfortunately, there was Terraform issue for determining count value of aws_vpc.dummy.

│ Error: Invalid count argument
│
│   on .terraform/modules/private_zone/modules/private-zone/main.tf line 19, in resource "aws_vpc" "dummy":
│   19:   count = try(var.primary_vpc_association.vpc_id, null) != null ? 0 : 1
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created. To work around
│ this, use the -target argument to first apply only the resources that the count depends on.

Does this mean this module will still fail if there is no default VPC in the region where you try to set up the VPC association with a Private Zone. I mean: in any version of this module?


Add joystick support and version info in loader

Adds in joystick control for scrolling lists of games in the loader.
Also displays a game's version in the metadata display section.
(replaces the display of game size / blocks)

Awesome, it's like you read Jon's mind since it was only mentioned today that it's weird the joystick does nothing in the menu 😆
I think we've got room to keep the block size if it's shuftied down a bit. It can be useful for setting expectations when launching/flashing games. Though better handling of flash contents is on the TODO list for... sometime in the future!

P.S. welcome back! 😁 and thank you!


Weird instability when running my app in debug, linked to tsduck libraries

This is quite possibly not an issue with tsduck, but I'm bit lost.
With a release build all is working ok, I'm using the new channel XML API and it seems to work.
However, when I run my app in debug I get some really basic issues; see attached I'm just passing a valid std::string p into ts::UString::fromUTF8 but when I step into this function the string it has received is garbage. Many levels later it crashes down inside the visual C runtime.
I initially thought this might be because I was linking my debug build against release tsduck libraries, but the same thing happens when linking against the tsduck debug libraries.
The rest of my code functions fine in debug; it's only when calling into the tsduck functions that this seems to be happening.

Just to add, I only get this issue linking against tsduck.lib for use with the DLL. If I link against tsducklib.lib then it works fine.

Well, this is a Visual Studio debugger issue. We cannot really help here. With experience, we all learn that we should not blindly trust debuggers. What they display and what is in C++ objects are not always the same. Try to add traces in the code to check if the string is what it should be. The Microsoft C++ compiler also has code generation bugs whan handling temporary objects (see here). Again, Windows is not the ideal development platform. You will learn 😉

Thanks - well it's not just when running in the debugger. Simply running the debug exe outside VS produces the same eventual call to abort() due to whatever corruption has occurred (in the end it finds the string it's handling is crazy long).
Maybe it's something in my debug settings, although I cannot see what.
It's also odd that my program functions fine, it's only when I call into the tsduck library that it goes wrong. I've linking against many other third party libraries and I've never seen this (libcurl, libconfig, libav, libVLC, SDL, SDL_ttf, freetype, etc etc).
That's not to say it's caused by tsduck, just that I've not come across it before :o)

The libraries you mention are written in C and manipulate simpler objects.  Many people are hit by the code generation bug I mentioned and Microsoft simply responds after 6 months that it may be fixed one year after the report.
Just to check if you are hit by the Microsoft C++ compiler bug, try to first create a ts::UString object which is initialized by you std::string, then pass the ts::UString object to the function.

I tried that, but it gives the same result i.e. crashes inside FromUTF8.
It works only with a hardcoded u"my path goes here" string. In fact, I replaced all the calls in that function with hardcoded strings to test, but it then crashes inside searchSeviceInternal inside the call to net.clear().
So I think my issue is more fundamental than the Microsoft bug you mention. As I say, if I link to the debug static lib it all works fine, it's only when using the DLL.

The same code is compiled twice by the Microsoft C++ compiler: once for the static library and once for the DLL. You say that one works and the other one crashes. Welcome in Windows world... We cannot do anything remotely without diving into the generated code. At best, try to isolate this into one small source code, one small application which reproduces the problem and post the code here.

Ok, looks like it was my own incompetence; a typo in one of my build scripts meant it ended up trying to run in debug using the release tsduck DLL.
Thank you for taking the time to try and help me and I'm very sorry to waste your time.

I've seen some packet loss but it also appears using the WinTV software so I'm not sure if that is DS related,

WinTV and other TV watching applications are based on DirectShow.

a typo in one of my build scripts meant it ended up trying to run in debug using the release tsduck DLL.

One thing I have discovered is your love of Windows :)

Exactly, the same typo would have been harmless on Linux :))


validates_uniqueness_of embedded_document with key

class Seller
  include Mongoid::Document
  field :seller_id, :type => Integer
  field :name, :type => String
  embeds_many :seller_products
  key :seller_id
end

class SellerProduct
  include Mongoid::Document
  field :product_id, :type => Integer
  key :product_id
  embedded_in :seller, :inverse_of => :seller_products
  validates_uniqueness_of :product_id
end

Validates_uniqueness_of doesnt work if i set my key to be :product_id
Uniqueness validator criteria becomes:
<Mongoid::Criteria
selector: {:product_id=>10, :_id=>{"$ne"=>"10"}},
options:  {},
class:    SellerProduct,
embedded: true>
When i remove the key it works
#<Mongoid::Criteria
selector: {:product_id=>1, :_id=>{"$ne"=>BSON::ObjectId('4eaf0733a5d09fb9ef000006')}},
options:  {},
class:    SellerProduct,
embedded: true>

Yup, that's a bug.


Update the supported addon version to 0.0.12

Fixed in https://github.com/rwz/ember-cli-rails/commit/57813fd67faf6418a6a324092e93a8e1794dc692

Thanks @MichaelVdheeren and @rwz.
Closing this issue since the change made its way into master.


2 coroutine comunicate with 2 channel aborted

when i use two channel for comunication, call push, it will aborted because of ordinator.current === 0

consider code like this:
class A
{
void MainLoop();
private:
coroutine::Channel ch1_;
coroutine::Channel ch2_;
};
void A::MainLoop()
{
auto f = &{ch2_.push(1);};
auto co1 = coroutine::create(f);
ch1_.consumer(co1);
auto f2 = &{ch2.pop();};
auto co2 = coroutine::create(f2)
ch2_.consumer(co2);
while(1)
{
coroutine::resume(co1);
coroutine::resume(co2);
}
}
i find that，when i call ch2_.push, it will aborted！I don't know is it a bug or it does not allow using like this.

Channel design pattern works like:
mainloop call push() to dispatch an object to one channel, and push() will auto resume coroutine of this channel;
this coroutine pop() and handles an object until it yields itself. when no object in channel, pop() will auto yield this coroutine.
In asymmetric coroutine, one routine is not allowed to resume()  another coroutine.
resumt() must be called by mainloop of thread.
Since push() will auto resume coroutine of channel, push() is not allowed to be called in coroutine,
it will trigger assert false in code.


weird issue client thinks server shuts down, server thinks client shuts down

So this is weird, overall the server and docker is working good. Some performance issues but i guess thats "normal".
I start:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='MineCraftVanilla' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -p '25565:25565/tcp' -v '/mnt/user/appdata/minecraft-vanilla':'/data':'rw' -e OPS=name1,name2 -e WHITELIST=name1,name2,name3 -e PVP=false -e EULA=TRUE -e ENABLE_AUTOPAUSE=TRUE -e VERSION=1.17.1-rc2 -e INIT_MEMORY=1G -e MAX_MEMORY=6G --restart=unless-stopped --log-opt max-size=50m --log-opt max-file=1 -e ENABLE_ROLLING_LOGS=true 'itzg/minecraft-server'
Server shows something like:
... no clients connected closing server (the auto loop thing)
Client shows:
... server closed connection...
In the log is nothing special, only thing i noticed is that some things are double like
[Autopause loop] Client connected - waiting for disconnect
[Autopause loop] Client connected - waiting for disconnect
is there anything like this known? Im using a script which presses left mouse button every 10 second (its a bot) which is farming some mobs... and its always disconnected... after 10 min or sometimes after 3 hours... i dont get it.
I have player-idle-timeout=0 so even if bot stopped, it should just stay in the game, right?

It seems like the docker is restarting without notice?
E.g. today morning the docker shows a runtime of 1h instead of 10 hours or something...


httpUseRanges doesn't work when requiredSegmentsPriority: 0

Hi, thanks again for this new feature. Testing it with requiredSegmentsPriority: 0 it doesn't appear to be working as i don't see 206 partial content anymore. Any idea how to fix this?
thanks

This feature works on slow peers when a segment becomes required (i.e. close to moving playhead) but it is still downloading over P2P. Then to have stable playback we cancel P2P download and continue HTTP download.
With requiredSegmentsPriority 0 segments never become required.
It is not recommended to have requiredSegmentsPriority set to 0 because required segments is playback buffer. Without buffer playback is not stable.


[DOP-11677] - add workflow for dev-release in test-pypi

Change Summary

add workflow for publishing dev release to test.pypi.org

Related issue number

Checklist

[x] Commit message and PR title is comprehensive
[x] Keep the change as small as possible
[ ] Unit and integration tests for the changes exist
[ ] Tests pass on CI and coverage does not decrease
[ ] Documentation reflects the changes where applicable
[ ] docs/changelog/next_release/<pull request or issue id>.<change type>.rst file added describing change
(see CONTRIBUTING.rst for details.)
[x] My PR is ready to review.

Нужно обновить setup.py по аналогии с onetl, сейчас в .dev подставляется переменная, актуальная только для Gitlab


Make README.md slightly friendlier to beginners

Explicitly mentions the need to do a yarn install and removes the line claiming that console_error_panic_hook is included.
Commit e59a8c58c removed console_error_panic_hook from Cargo.toml, but didn't fully excise other places where it was mentioned.
FWIW, yesterday I converted my program to use web-sys and wasm-pack using yew-wasm-pack-template as an example. Thank you very much for making this. It made things easy. My changes here are mere nits that surprised me and might surprise others.
I tried getting console_error_panic_hook to work, first in my program, then in this template and was unsuccessful even when I added it back to Cargo.toml.
I didn't see a reason why console_error_panic_hook was (partially) recently removed, but my guess is that it stopped working for some reason.

I'd even go for not mentioning yarn but npm since the latter has more popularity

I agree, npm is preferred


basic_fields handles initializer-lists.

This is very convenient for my requests library that (for now) uses the fields structure directly.

I don't think we should keep adding stuff like this, and also we are in the release cycle so it is too late to add a new API

It is meant for 1.82.

You should write a free function init_fields that lets you construct with an initializer-list, keep it in your library, and not add it to beast


Make share photo after upload

Hi there,
As title, how to make share public photo with photoID after upload?
Thanks

This library is not supported to make the share URL.
However, you can get the raw URL via photo.rawUrl.
import GPhotos from 'upload-gphotos';
(async () => {
const gphotos = new GPhotos({
  username<EMAIL_ADDRESS>  password: 'YOUR_PASSWORD'
});
await gphotos.login();
const photo = await gphotos.fetchPhotoById('PHOTO_ID');
console.log(photo.rawUrl);
})();

I've read your code and understood a bit. I'm trying to write a function to create a shared link. Thanks you.

I'll close temporary.
If anyone have issue, please create new issue.


Resolve upstream ReactNative android build blocker

Problem
Facebook broke Android builds last Friday, here's a full breakdown of the cause.
Solution
To fix, we should bump React Native to the latest hotfix release, to resolve an Android build issue that is blocking us from making Android releases.
Manually set the gradle RN version.

This is being handled internally, no need for contributors.

Okay, so the hotfix is only a few hours old, so the RN-updater and diff table haven't yet been updated.
I assume there are likely no breaking changes, but given that we have previously made changes ourselves, I wonder if it's worth attempting this simple fix in the meantime...

The above fix is even simpler than this, as it doesn't require a React-native bump, or library deploy. I'm going to make this change locally in App and if it works we can discuss next steps.

PR: https://github.com/Expensify/App/pull/12510


translation:/content/docs/concepts/index.md #154

Chinese translation, update the markdown.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gyliu513
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS [gyliu513]

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

/ok-to-test

I signed it!

@googlebot  I signed it!


Method not found: 'Void Microsoft.Rest.HttpOperationException.set_Request(System.Net.Http.HttpRequestMessage)'.

When receiving any message with a simple MessagesController like:
        public async Task<HttpResponseMessage> Post([FromBody] Activity activity)
        {

            if (activity != null)
            {
                // one of these will have an interface and process it
                switch (activity.GetActivityType())
                {
                    case ActivityTypes.Message:
                        await Conversation.SendAsync(activity, MakeRoot);
                        break;

                    case ActivityTypes.ConversationUpdate:
                        //await SetCustomerId(activity);
                        break;
                    case ActivityTypes.ContactRelationUpdate:
                    case ActivityTypes.DeleteUserData:
                    case ActivityTypes.Ping:
                    case ActivityTypes.Typing:
                        _logger.Debug($"Activity type {activity.GetActivityType()}");
                        break;
                    default:
                        _logger.Error($"Unknown activity type ignored: {activity.GetActivityType()}");
                        break;
                }
            }
            return new HttpResponseMessage(HttpStatusCode.Accepted);
        }

We are getting the message:

Method not found: 'Void Microsoft.Rest.HttpOperationException.set_Request(System.Net.Http.HttpRequestMessage)'

This exception in thrown from the BotState class for all of the Get<DataKind>DataWithHttpMessagesAsync methods. It seems to specifically relate to code trying to contact the BotState REST service.
Part of my question is how does all of this behave when the bot state service is down? The other part is obviously how do I solve this?

This looks like an assembly binding failure -- are you using Microsoft.Rest.ClientRuntime 1.8.2?

Yes I am. I found the problem in the end. I had the emulator open which was
opening Microsoft.Rest.ClientRuntime <IP_ADDRESS> and then I was having the
"first loaded wins" problem.
On Thu, 21 Jul 2016 at 16:01, dandriscoll<EMAIL_ADDRESS>wrote:

This looks like an assembly binding failure -- are you using
Microsoft.Rest.ClientRuntime 1.8.2?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/783#issuecomment-234281537,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACf75Z51oxbe-fR8EhDoItw3Yz6Kjtn6ks5qX4nNgaJpZM4JRvSC
.


module templates incorrectly assume external_reference will follow S-Code and G-Code conventions and case

BLUF:
please drop the use the "|upper" in creation of the href in a table's card element.
When customizing STIX objects for use by the attack-website generation on our internal site, we discovered that the pelican templates for groups (specifically, but elsewhere as well) are inconsistent when creating the cards for groups and other tables.
For the display name, upper case by default may be appropriate for table uniformity of appearance.  Unfortunately, forcing the href to use a specific case or perhaps use a different URL can result in an invalid URL.
For example from the enterprise ATTACK:
...
"external_references": [
    {
        "source_name": "mitre-attack",
        "external_id": "G0001",
        "url": "https://attack.mitre.org/groups/G0001"
    },
....
    "name": "Axiom",
....

The site generation code will create a directory /groups/G0001.
And the ID field for the card in the group table will look like:

     G0001

That comes from the group-index.html template in modules/groups/templates, specifically starting at line 47:

                                {% for row in parsed.groups_table %}

                                             {{row.id|upper}}

                                             {{row.name}}

Note the "|upper" directive
The problem comes, when the ID case may not natively be upper
for example an intrusion set named "SomeFineGroupName"  has an external reference appears as:
{
    "source_name": "mitre-attack",
    "url": "https://my-attack-website.myorg.com/groups/MyCustomNotUpperCaseCode"
    "external_id": "MyCustomNotUpperCaseCode"
}

The resulting directory entry will be generated as  /group/MyCustomNotUpperCaseCode, matching the ID in the stix object.
The resulting card for the groups table however, will result in an ref such as:

     MYCUSTOMNOTUPPERCASECODE

The solution is to drop the "|upper" directive in the href, while keeping the label as is if desired.

Just to clarify, I'm asking you to change the template to remove the upper directive from the href generation for datasource, software and groups:

                                             {{row.id|upper}}

                                             {{row.name}}


3.0.6 xcode compile error

Hi,
I noticed xcode is complaining about missing semi-colons here: https://github.com/PeelTechnologies/react-native-tcp/commit/ff3576578a18f27908b63ad3b824b9566924ae02#commitcomment-20414082

odd, maybe a merge error, i'll take a look

added semis, thanks


add on missing splattributes and remove @class

Fixes some styling for https://github.com/cardstack/cardstack/pull/1584

The historical reason for the @class usage was for when we were using a component with the component helper. Just want to double-check whether that applies in these cases at all?

The historical reason for the @class usage was for when we were using a component with the component helper. Just want to double-check whether that applies in these cases at all?

I can't find any at the moment, but wondering if buttons will need this, and if this should apply to Boxel::Button.


Previous element not loading when loop=true and itemsPerView > 1

This is a (multiple allowed):

[x] bug

Swiper Version: "swiper": "^4.2.0"

Platform/Target and Browser Versions: any

Live Link or JSFiddle/Codepen or website with isssue: https://stackblitz.com/edit/github-ph1huz

What you did

loop = true
itemsPerView = 3

Click itemsPerView (3) times up.
Expected Behavior
To see an element previous to the current one
Actual Behavior
No elements are shown previous to the current one

Add this parameter for example loopedSlides: 4