MAC OSX support

I'm on Mac OSX 23.5.0 Darwin Kernel Version 23.5.0 arm64
I would compile the last Daphne version but When I do ,/build.sh I get this error:
checking for architecture... arm64
checking for OS... darwin
checking for OS version... 23.5.0
checking for perf_event workaround level... autodetect
checking for if MIC should be used... no
checking for if NEC should be used... no
checking for xlc... no
checking for icc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for xlf... no
checking for ifort... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
checking for mpicc... no
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... rm: conftest.dSYM: is a directory
rm: conftest.dSYM: is a directory
yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define EXTENSIONS... yes
checking for ANSI C header files... (cached) yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking c_asm.h usability... no
checking c_asm.h presence... no
checking for c_asm.h... no
checking intrinsics.h usability... no
checking intrinsics.h presence... no
checking for intrinsics.h... no
checking mach/mach_time.h usability... yes
checking mach/mach_time.h presence... yes
checking for mach/mach_time.h... yes
checking sched.h usability... yes
checking sched.h presence... yes
checking for sched.h... yes
checking for gethrtime... no
checking for read_real_time... no
checking for time_base_to_time... no
checking for clock_gettime... yes
checking for mach_absolute_time... yes
checking for sched_getcpu... no
checking for timer_create and timer_*ettime symbols in base system... not found
checking for timer_create and timer_*ettime symbols in -lrt... not found
checking for timer_create and timer_*ettime symbols in -lrt -lpthread... configure: error: cannot find timer_create and timer_*ettime symbols neither in the base system libraries nor in -lrt, nor in -lrt -lpthread
The problem is papi that need get_time symbols but MAC OSX doesn't support them. Here the Papi thred: https://github.com/icl-utk-edu/papi/issues/190
What is the right way to compile Daphne?

Thanks for creating this issue, @flashboss. So far, we haven't designed the DAPHNE build workflow to support Mac OSX, since we mainly target Linux platforms (especially Ubuntu as described in the GettingStarted guide). Thus, DAPHNE does not build on Mac OSX natively at the moment. However, there are two possible solutions:

Our general approach to make DAPHNE run on platforms where a native build is not supported [yet] is using pre-built container images. You can find instructions on using these containers in our quickstart guide for users or for developers. Feel free to let us know in case you encounter any problems with those containers.
We are already working on making DAPHNE build natively on Mac OSX, but so far with low priority. As far as I know, @philipportner has made some progress in this direction recently. He might be able to help you best. He is currently out of the office, but I think he should be able to join the discussion beginning of next week. In the meantime, maybe I can help you (even though I don't have a Mac to test with). The concrete problem you are currently facing is that PAPI doesn't support Mac OSX. PAPI is only required for certain extra features of DAPHNE (related to profiling). It should not be difficult to make PAPI an optional dependency in DAPHNE; I will push a commit for that tomorrow and let you know.

Hi @flashboss ,
As @pdamme already mentioned, DAPHNE is currently only supported through docker containers on macOS.
To do so, please pull from main and start the docker container through ./containers/run-docker-example.sh. Once inside you should be able to build DAPHNE via ./build.sh.

@flashboss Using the docker containers is most likely the easiest way to get DAPHNE running on Mac OSX. In case you prefer a native build without docker: I have pushed a commit to main, which enables building DAPHNE without PAPI (and, consequently, without profiling support). Feel free to try ./build.sh --no-papi or ./test.sh --no-papi on your Mac OSX system. We're happy to help if you encounter any further obstacles.

Hi, build through container now is ok.
Building without container I get this error:
lucastancapiano@MacBook-Pro-7 daphne % ./build.sh --no-papi
not using PAPI
[DAPHNE].................................................................................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...Welcome to....................................................................................................................................................................[20.06.24 09:50:54]
[DAPHNE].................................................................................................................................................................................[20.06.24 09:50:54]
[DAPHNE]....___.......................__.............................................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...|       .....................|  ............................................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...| €€€€€€€\  ______    ______  | €€   _______    __....................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...| €€  | €€ |      \  /      \ | €€    \ |       \  /      ...................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...| €€  | €€  \€€€€€€|  €€€€€€| €€€€€€€| €€€€€€€|  €€€€€€..................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...| €€  | €€ /      €€| €€  | €€| €€  | €€| €€  | €€| €€    €€..................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...| €€/ €€|  €€€€€€€| €€/ €€| €€  | €€| €€  | €€| €€€€€€€€..................................................................................................................[20.06.24 09:50:54]
[DAPHNE]...| €€    €€ \€€    €€| €€    €€| €€  | €€| €€  | €€ \€€     ..................................................................................................................[20.06.24 09:50:54]
[DAPHNE]... \€€€€€€€   \€€€€€€€| €€€€€€€  \€€   \€€ \€€   \€€  \€€€€€€€..................................................................................................................[20.06.24 09:50:54]
[DAPHNE].......................| €€......................................................................................................................................................[20.06.24 09:50:54]
[DAPHNE].......................| €€......................................................................................................................................................[20.06.24 09:50:54]
[DAPHNE]........................\€€..................EU-H2020.//.957407..................................................................................................................[20.06.24 09:50:54]
[DAPHNE].................................................................................................................................................................................[20.06.24 09:50:54]
[DAPHNE]..No need to build hwloc again...................................................................................................................................................[20.06.24 09:50:55]
[DAPHNE]..Get Antlr version 4.9.2........................................................................................................................................................[20.06.24 09:50:55]
[DAPHNE]..Download Antlr v4.9.2 java archive.............................................................................................................................................[20.06.24 09:50:55]
[DAPHNE]..Download Antlr v4.9.2 Runtime..................................................................................................................................................[20.06.24 09:51:33]
mkdir: illegal option -- -
usage: mkdir [-pv] [-m mode] directory_name ...

mkdir on macos does not support '--parents' only the short form '-p'

I know it would be more correct to use the container but I think it is right to use -p instead of -parents as it is universal and guarantees greater portability

@flashboss Great to hear that you could make DAPHNE work in the container on Mac OS, so you can already start using DAPHNE. Thanks to @auge, the build script uses mkdir -p now. Feel free to try again.

I have this error now:
ninja: build stopped: subcommand failed.
[DAPHNE]..Applying 0001-antlr-gtest-silence-warnings.patch...............................................................................................................................[22.06.24 08:08:36]
patch: **** can't cd to /Users/lucastancapiano/git/daphne/thirdparty/build/antlr4-cpp-runtime-4.9.2-source/runtime/thirdparty/utfcpp/extern/gtest/: No such file or directory
[2/308] Performing download step (git clone) for 'utfcpp'
FAILED: runtime/utfcpp-prefix/src/utfcpp-stamp/utfcpp-download
cd /Users/lucastancapiano/git/daphne/thirdparty/build/antlr4-cpp-runtime-4.9.2-source/runtime/thirdparty && /usr/local/Cellar/cmake/3.20.0/bin/cmake -P /Users/lucastancapiano/git/daphne/thirdparty/build/antlr4-cpp-runtime-4.9.2-source/runtime/utfcpp-prefix/tmp/utfcpp-gitclone.cmake && /usr/local/Cellar/cmake/3.20.0/bin/cmake -E touch /Users/lucastancapiano/git/daphne/thirdparty/build/antlr4-cpp-runtime-4.9.2-source/runtime/utfcpp-prefix/src/utfcpp-stamp/utfcpp-download
Cloning into 'utfcpp'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Operation timed out
Cloning into 'utfcpp'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Operation timed out
Cloning into 'utfcpp'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Operation timed out
-- Had to git clone more than once:
3 times.
CMake Error at /Users/lucastancapiano/git/daphne/thirdparty/build/antlr4-cpp-runtime-4.9.2-source/runtime/utfcpp-prefix/tmp/utfcpp-gitclone.cmake:31 (message):
Failed to clone repository: 'git://github.com/nemtrif/utfcpp'
ninja: build stopped: subcommand failed.

Hi @flashboss and @pdamme , thanks for the feedback so far. Be assured I am actively working on supporting DAPHNE on macOS and already have solved some of these problems. I will update you on this issue once compiling and running DAPHNE works on macOS @flashboss !

Are there news? Actually I have this error:
build.sh --no-papi
*** Assembler
checking dependency style of gcc... gcc3
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking for fgrep... /usr/bin/grep -F
checking for __atomic builtin atomics... yes
checking for __atomic_compare_exchange_n... yes
checking if __atomic_compare_exchange_n() gives correct results... yes
checking if __int128 atomic compare-and-swap is always lock-free... yes
checking if .proc/endp is needed... no
checking directive for setting text section... .text
checking directive for exporting symbols... .globl
checking for objdump... objdump
checking if .note.GNU-stack is needed... /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: error: 'conftest.o': Invalid/Unsupported object file format
no
checking suffix for labels... :
checking prefix for global symbol labels... none
configure: error: Could not determine global symbol label prefix

Hi @flashboss , I'm working on it but I still have quite some troubles to get it working on macOS.  I will create a branch and draft PR once I have something that runs, even if it may have limited functionality. Until then, please use the docker image.


Fix double protocol in Berg GitHub url

Thanks!

FYI, not sure if you rebased this out on purpose, but it isn't in master anymore.

The root problem is that all changes to any of the gherkin-* projects should be make in the gherkin project, and then push to the gherkin-* projects, see gherkin/CONTIBUTING.md. Because this change was made in this project (and not immediately after the merge pulled to the gherkin project), it was overwritten by the v4.0.0 release when it was pushed from the gherkin project.

I originalmy merged the PR from my phone and didn't notice at the time it was done in the wrong repo. Please send us a new PR in the gherkin repo.


Pull postgresql redhat

This patch series adds postgresql support and support for RHEL 6 based distros with bacula 5.0.x .
This fixes issue https://github.com/puppetlabs/puppetlabs-bacula/issues/23 .

Could you please have a look at #31 and see if that PR makes more sense ?

Thanks for the work you have put in to this pull request. Based on what @pemer said and the lack of activity, this pull request is being closed. If you want to re-submit this pr with the necessary changes, we will look at the new pull request. It may be worth looking into #31


Creating SETUP.md file

A File which guides participants  how to Set up development environment on local machine

I would like to work on this issue. Please assign this to me.

Can I take up this issue?

@falguniraina We could add 2 headers "installation" and the second one being "setup environment". I would really like to enhance this file if you could assign me this issue.

can I work on this issue?


Clip-path-animation

Hii I'm a GSSoc22 contributor and I'm looking to make a pr request in this repo regarding my CSS animation project as clip-path content
The idea behind this project:
Whenever we need to put more info in less place we just use this technique
How does it work :
while loading the webpage on the browser in the right corner there will be an info icon when you will hover on it it will open content hidden in it
for more details refers to this image

for more animation views refer to this video
https://user-images.githubusercontent.com/73521123/167208548-decd888e-6d78-4028-9015-6f4b8d3989a3.mp4

@VidhiBhatt01 please check and assign me


Support policies that are triggered by Metagov events

With this change, a Policy author can specify an event defined in a Metagov plugin as a policy trigger. Example filter block:
```
return action.action_codename == 'metagovaction' and action.event_type == 'opencollective_expense_created'
```

How this works:

Pre-requirement: there is a SlackCommunity (or whatever Community) that has already been configured to enable some Metagov plugin that sends events.

Metagov makes a POST request to the PolicyKit endpoint /metagov/action with a payload that looks like:
    {
         "community": "slack-test123",   # Unique string identifying the community that this action "belongs" to. It was originally defined by PolicyKit.
         "initiator": {"user_id": "miriam", "provider": "discourse"},
         "event_type": "discourse_post_created",
         "data": {"title": "test", "raw": "post text", "category": 0},
     }

The integrations.metagov app in PolicyKit creates a MetagovPlatformAction for this event.

The action.initiator is set to a MetagovUser which has blanket access to "propose" any MetagovPlatformAction in this community.
The action.community is set to the original community in PolicyKit (in this example, the SlackCommunity).

The MetagovPlatformAction does not support execute or revert functionality. It is simply a trigger event. In order to support execution/reversion of actions, we'd need to create individual subclasses of MetagovPlatformAction for each action (eg OpenCollectiveConversation, DiscoursePost, etc.)

When the newly created MetagovPlatformAction event is saved, it triggers a policy evaluation. The logic is to execute all policies where PlatformPolicy.objects.filter(community=action.community). That means any PlatformPolicy that is defined for this SlackCommunity will be tested.

That means Slack policies with filter: return True will execute for metagov actions too, which is maybe not what we want? I don't know how those blanket policies are really used.

@mashton my bad for reviewing out of order....could you resolve the merge conflict? Sorry about that!

Hi @mashton does this still need to be reviewed as is or should I be waiting for you to push more commits?

I need to update it since the most recent merge, I’ll ping you when it’s
ready for review again!
On Fri, Mar 26, 2021 at 10:58 PM Amy Zhang @.***> wrote:

Hi @mashton https://github.com/mashton does this still need to be
reviewed as is or should I be waiting for you to push more commits?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/amyxzhang/policykit/pull/302#issuecomment-808632321,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIWHXRVDTFCBHIM42GF3ZLTFVCVZANCNFSM4ZDAD6LQ
.

This looks good! We'll want to add PolicyKit documentation around these action codenames and event types (once we have a readthedocs page for how to write policies for the different integrations) and eventually surface them in the policy editor too.


⚠ Bofrost.es has degraded performance

In f9ea5d6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1499 ms

Resolved: Bofrost.es performance has improved in a55a4ee after 6 minutes.


Support for Typescript typings

@nanovazquez I don't know how familiar you are with Typescript, but I opened a PR at DefinitelyTyped to have typings for yargs-interactive.  I need to update it now that options is choices.  But I'm thinking the interfaces should probably extend from inquirer at some point.  I'm just not sure what all is passed from yargs-interactive to inquirer here.  Any input on that PR would be helpful.

It's basically a giant repository of typings for projects that aren't written in Typescript or don't provide their own typings.  I had to create my own for https://github.com/Unibeautify/create-unibeautify-beautifier/blob/master/src/create-unibeautify-beautifier.ts so I had typings and didn't have to use require().
Since choices is in inquirer, the OptionData interface I have should probably extend inquirer's Question interface.  I'm not an expert on .d.ts files, but that's a the gist of it.

Closing this issues as the typings are already present in DefintelyTyped. Thanks @stevenzeck!


Update workflow_execution_activity.yaml

Added description and title of read based analysis.
Shall we rename it to "read based taxonomy analysis activity?"

Thanks for reviewing this PR, @sujaypatil96. It's really not a matter of what sounds better. It's a matter of aligning the term name with the term description. In this case, there is good alignment, so I will make that additional change and merge it in.


Invalid constructor parameters exception message

Review the exception message for when an object/type has invalid constructor parameters.
https://github.com/leekelleher/umbraco-ditto/commit/40a41d235d7c722dfe3d0a95d7cdd0b435944cf5#diff-81cfd4fcb771a0cad63163155354443cR290

Do we need to add more to the exception message to explain why the construction parameters are invalid?

Fixed in commit dcf04d89805c902abde8a090a45ee28404d02c3b by adding a more helpful message


[Bug]: Failed to login to SSH session, retrying... /  Error creating controller: RetryError

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://opendevin.github.io/OpenDevin/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug
seems to not be able to login after yesterday's main pull. not surprised if this is my error and i somehow confused myself.
Current OpenDevin version
origin main

Installation and Configuration
make build
make start-backend

Model and Agent
No response
Operating System
WSL2
Reproduction Steps
No response
Logs, Errors, Screenshots, and Additional Context
Starting backend...
INFO:     Will watch for changes in these directories: ['/home/opendevin']
INFO:     Uvicorn running on http://<IP_ADDRESS>:3000 (Press CTRL+C to quit)
INFO:     Started reloader process [22780] using WatchFiles
INFO:     Started server process [22785]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     <IP_ADDRESS>:34034 - "GET / HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34034 - "GET /assets/index-D-eqM5Rw.css HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34034 - "GET /assets/index-BARj30Qf.js HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34034 - "GET /locales/en/translation.json HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34034 - "GET /apple-touch-icon.png HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34066 - "GET /api/options/models HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34066 - "GET /api/options/agents HTTP/1.1" 200 OK
INFO:     ('<IP_ADDRESS>', 34082) - "WebSocket /ws" [accepted]
INFO:     connection open
12:36:21 - opendevin:INFO: agent.py:64 - Using server runtime
12:36:21 - opendevin:INFO: ssh_box.py:206 - SSHBox is running as opendevin user with USER_ID=1001 in the sandbox
12:36:21 - opendevin:INFO: ssh_box.py:242 - Creating new Docker container
12:36:21 - opendevin:INFO: ssh_box.py:659 - Container stopped
12:36:21 - opendevin:WARNING: ssh_box.py:671 - Using port forwarding for Mac OS. Server started by OpenDevin will not be accessible from the host machine at the moment. See https://github.com/OpenDevin/OpenDevin/issues/897 for more information.
12:36:21 - opendevin:INFO: ssh_box.py:644 - Mounting workspace directory: /home/opendevin/workspace
12:36:21 - opendevin:INFO: ssh_box.py:680 - Mounting volumes: {'/home/opendevin/workspace': {'bind': '/workspace', 'mode': 'rw'}, '/tmp/cache': {'bind': '/home/opendevin/.cache', 'mode': 'rw'}}
12:36:21 - opendevin:INFO: ssh_box.py:644 - Mounting workspace directory: /home/opendevin/workspace
12:36:21 - opendevin:INFO: ssh_box.py:691 - Container started
12:36:22 - opendevin:INFO: ssh_box.py:707 - waiting for container to start: 1, container status: running
12:36:23 - opendevin:INFO: ssh_box.py:383 - Connecting to opendevin@localhost via ssh. If you encounter any issues, you can try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8' and report the issue on GitHub. If you started OpenDevin with `docker run`, you should try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8 on the host machine (where you started the container).
12:36:23 - opendevin:ERROR: ssh_box.py:390 - Failed to login to SSH session, retrying...
12:36:28 - opendevin:INFO: ssh_box.py:383 - Connecting to opendevin@localhost via ssh. If you encounter any issues, you can try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8' and report the issue on GitHub. If you started OpenDevin with `docker run`, you should try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8 on the host machine (where you started the container).
12:36:28 - opendevin:ERROR: ssh_box.py:390 - Failed to login to SSH session, retrying...
12:36:33 - opendevin:INFO: ssh_box.py:383 - Connecting to opendevin@localhost via ssh. If you encounter any issues, you can try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8' and report the issue on GitHub. If you started OpenDevin with `docker run`, you should try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8 on the host machine (where you started the container).
12:36:33 - opendevin:ERROR: ssh_box.py:390 - Failed to login to SSH session, retrying...
12:36:38 - opendevin:INFO: ssh_box.py:383 - Connecting to opendevin@localhost via ssh. If you encounter any issues, you can try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8' and report the issue on GitHub. If you started OpenDevin with `docker run`, you should try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8 on the host machine (where you started the container).
12:36:38 - opendevin:ERROR: ssh_box.py:390 - Failed to login to SSH session, retrying...
12:36:43 - opendevin:INFO: ssh_box.py:383 - Connecting to opendevin@localhost via ssh. If you encounter any issues, you can try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8' and report the issue on GitHub. If you started OpenDevin with `docker run`, you should try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8 on the host machine (where you started the container).
12:36:43 - opendevin:ERROR: ssh_box.py:390 - Failed to login to SSH session, retrying...
12:36:43 - opendevin:ERROR: session.py:69 - Error creating controller: RetryError[<Future at 0x7f543a67c8d0 state=finished raised ExceptionPxssh>]
Traceback (most recent call last):
  File "/home/opendevin/.cache/pypoetry/virtualenvs/opendevin-MwVY0VRQ-py3.11/lib/python3.11/site-packages/tenacity/__init__.py", line 470, in __call__
    result = fn(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/opendevin/runtime/docker/ssh_box.py", line 393, in __ssh_login
    raise e
  File "/home/opendevin/opendevin/runtime/docker/ssh_box.py", line 388, in __ssh_login
    self.ssh.login(hostname, username, self._ssh_password, port=self._ssh_port)
  File "/home/opendevin/.cache/pypoetry/virtualenvs/opendevin-MwVY0VRQ-py3.11/lib/python3.11/site-packages/pexpect/pxssh.py", line 424, in login
    raise ExceptionPxssh('Could not establish connection to host')
pexpect.pxssh.ExceptionPxssh: Could not establish connection to host

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/opendevin/opendevin/server/session/session.py", line 67, in _initialize_agent
    await self.agent_session.start(data)
  File "/home/opendevin/opendevin/server/session/agent.py", line 46, in start
    await self._create_runtime()
  File "/home/opendevin/opendevin/server/session/agent.py", line 65, in _create_runtime
    self.runtime = ServerRuntime(self.event_stream, self.sid)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/opendevin/runtime/server/runtime.py", line 35, in __init__
    super().__init__(event_stream, sid, sandbox)
  File "/home/opendevin/opendevin/runtime/runtime.py", line 71, in __init__
    self.sandbox = create_sandbox(sid, config.sandbox_type)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/opendevin/runtime/runtime.py", line 45, in create_sandbox
    return DockerSSHBox(sid=sid)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/opendevin/runtime/docker/ssh_box.py", line 262, in __init__
    self.start_ssh_session()
  File "/home/opendevin/opendevin/runtime/docker/ssh_box.py", line 396, in start_ssh_session
    self.__ssh_login()
  File "/home/opendevin/.cache/pypoetry/virtualenvs/opendevin-MwVY0VRQ-py3.11/lib/python3.11/site-packages/tenacity/__init__.py", line 330, in wrapped_f
    return self(f, *args, **kw)
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/.cache/pypoetry/virtualenvs/opendevin-MwVY0VRQ-py3.11/lib/python3.11/site-packages/tenacity/__init__.py", line 467, in __call__
    do = self.iter(retry_state=retry_state)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/.cache/pypoetry/virtualenvs/opendevin-MwVY0VRQ-py3.11/lib/python3.11/site-packages/tenacity/__init__.py", line 368, in iter
    result = action(retry_state)
             ^^^^^^^^^^^^^^^^^^^
  File "/home/opendevin/.cache/pypoetry/virtualenvs/opendevin-MwVY0VRQ-py3.11/lib/python3.11/site-packages/tenacity/__init__.py", line 411, in exc_check
    raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x7f543a67c8d0 state=finished raised ExceptionPxssh>]

you can try `ssh -v -p 63710 opendevin@localhost` with the password '23874293847283456238754923jjksdflkjsdf83hd8'

Did you?

opendevin@localhost will try to log into the the user opendevin on the localhost, not the docker environment .
previously, i believe, the docker virtual env hostname was a random string, and the the user password was also a random string, but longer. these were automatically generated and provided to the sandbox with make start-backend
then the update for ssh_password
now i beli
my current setup:
Windows Machine > WSL2 Ubuntu >/home/opendevin:$ mkdir workspace
/home/opendevin:$ git pull .
/home/opendevin:$ make clean
/home/opendevin:$ make build -j16
/home/opendevin:$ make start-backend

I only recently started using the directory structure like this to make it as easy as possible for the application to get all of the variables correct.
[core]
workspace_base='/home/opendevin/workspace'
workspace_mount_path_in_sandbox='/home/opendevin/workspace'
workspace_mount_path='/home/opendevin/workspace'
#get_working_directory="/home/opendevin/workspace"
ssh_password="xxxxxxxxxxxxxxxxxxxx"
sandbox_user_id=1001
#enviornment=["SSH_PASSWORD=$SSH_PASSWORD;WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE;SANDBOX_USER_ID=$(id -u)"]
#[volumes]
#bind=["$WORKSPACE_BASE:/opt/workspace_base:rw;/var/run/docker.sock:/var/run/docker.sock:rw;"]
#ssh_hostname='docker.internal.host'
#use_host_network=0

[llm]
model="ollama/command-r:35b-v0.1-q3_K_L"
model_type="ollama/codestral"
api_key="ollama"
base_url="http://<IP_ADDRESS>:11434"
embedding_model="local"

docker virtual env hostname

sandbox container name.

According to your current config, it will start the persistent container.

I have yet to get the chat, the terminal, and the explorer to work at the same time. I've also experimented with a few things.. clearly😅
before, it would generate a random hostname for the container. now it wants to contact localhost, but thats my machine. it's trying to log into the host.

now it wants to contact localhost,

previously, it was the same.

https://i.imgur.com/qsOg2Fr.png

Did you change the ssh password? Please delete the container and check again.

https://i.imgur.com/E1hthcz.png

first one. now it's working?

sorry, i was just showing it was running. its brand new. the error message is below

does the ssh_password need to be the same as the user's actual password? i was assuming this is a random pass that just for the container. i am getting the impression that credentials are getting confused somewhere.

does the ssh_password need to be the same as the user's actual password?

No. Connect to the ssh using wsl

does the ssh_password need to be the same as the user's actual password?

No. Connect to the ssh using wsl

the wsl user.
i have a user named opendevin. the git repo is pulled into their home directory, ie bash /home/opendevin:$ `git clone https://github.com/OpenDevin/OpenDevin.git .

i.imgur.com/qsOg2Fr.png

What's the top left icon?

that is what i did, it's two terminal

Could you increase the retry? https://github.com/OpenDevin/OpenDevin/pull/2101#issuecomment-2134553543

Previously you have the same username for the WSL?

removing my localhost user password allowed me to connect to the shh via wsl, but the docker container was still unable to connect.
https://i.imgur.com/xfQWaq4.png

i have a user named opendevin. the git repo is pulled into their home directory, ie

You have two WSL users?

yes, within the ubuntu environment, i created a new user name opendevin
that user then git clones into their home folder ~/.
this user's sole purpose is to operate opendevin as a service.
this also has worked, but the agent will start writing to phantom directories i can only find when speaking with the bot, not in the shh container.
ie, i'll ask the bot to ls -a, and it will show files that dont exist, but it can read them to me.
should i not be creating the workspace folder? should it exist in the docker container and then i copy out of it?
currently i am using the workspace directory on my localhost.

it will show files that dont exist,

how it will?

Check if you still get this error on a fresh install; test it on a single user.

       self._ssh_password = str(uuid.uuid4())
       self._ssh_port = find_available_tcp_port()

_ssh_password is differnt from ssh_password

That is in conditional branch.

it will show files that dont exist,

how?
Check if you still get this error on a fresh install; test it on a single user.

will do


Some notifications are not disappearing when multiple are opened

Describe the bug
If multiple notifications are triggered within a short amount of time, then some of them will not disappear.
If 3 is opened then 1 will not disappear, 5 open -> 2 will not disappear, 7 open -> 3 and so on.
To Reproduce
Steps to reproduce the behavior:

Go to https://blazor.radzen.com/notification
Click more than 3 times on one of the show notification buttons
See that some of the notifications will not disappear

Expected behavior
Notifications disappears after given time
Desktop (please complete the following information):

OS: Linux
Browser: Firefox
Version: 115.0.2

Additional context
I think this issue may have started after the "Do not hide 2 notifications when clicking close." from release 4.13.6

@technight I tested in in y local repo's, before update in PR #1084 , the same behaivour existed :-(

I belive #1092 should close this issue. The problem was that the loop in RadzenNotification.razor would update the Message parameter of an already existing component when a notification was closed. PR adds the key directive so that the parameters are fixed to the "correct" component instance.


demo using a template?

It would be good to have a demo using a template, something like :
184           <polymer-dragula id="dragula">
185

186               <template is="dom-repeat" items="[[_myItemList]]">
187

188
[[_increment(index)]].

189
[[item.name]] ([[item.code]])

190
<iron-icon icon="editor:drag-handle"></iron-icon>[[item.text]]

191

192               </template>
193

194           </polymer-dragula>

I had to hack polymer-dragula to make this work...here are the relevant bits (this is the polymer-dragular element and the following code is in the attached function :
84               var template = this.queryEffectiveChildren('div').querySelector('template');
185
186               template.addEventListener('dom-change', e => {
187                 var containers = [Polymer.dom(this).children[0]];
188
189                 if (this.drake) {
190                   this.drake.containers = containers;
191                 } else {
192                   var drake = dragula(containers, config);

I've added a property for setting the container class to support the use-case you describe. There is also a demo with this + dom-repeat. Hope this is what you need!

I noticed the demo didn't actually add/remove from the dom-repeat's array - it would be nice if the demo included that, just to prove it to someone considering using it - but when I hacked that into the demo, it still worked just fine, so I'm happy :)
FWIW, I added this code :
   42             <paper-material item-index="[[index]]" elevation="1" class="item">
...
 68       attached: function() {
 69         var self = this;
 70
 71         this.$.dragula.addEventListener('dragula-drop', function(event) {
 72           console.log('dropped');
 73           var items = this.querySelectorAll('.item');
 74           for (var i=0; i<items.length; i++) {
 75             var item = items[i];
 76             console.log('item:', item.itemIndex);
 77           }
 78         });
 79
 80         this.async(function() {
 81           self.push('dragItems', { title: 'Boo!', subtitle: 'Can you see me?' });
 82         }, 1000);
 83       },

If you wanted to consider adding something like that (perhaps an add/remove button would be better).
Your implementation looks better than what I hacked together (shadow/etc work), so I think I'll spend a couple of hours getting it into my real code.
Thanks!

Yup, worked fine, once I'd taken out my hacks...much cleaner. Thanks again :)
Is this element in the bower registry? Might be a good idea.

Yeah I'll look into that! I haven't done this yet because it's not as polished as I'd like... But I guess it's fine for an initial version


OAuth API is not supported

Currently this library does not support Blizzard's OAuth API. It would be good if we could implement it and create a comprehensive package.

This is probably out of scope for our library since there are other options to handle OAuth with Battle.net.
However, once we have an access token the queries could be done using this library.


Weird nz-select search behaviour as a prefix of nz-input-group

Reproduction link
https://stackblitz.com/edit/angular-witztb?file=src/app/app.component.ts
Steps to reproduce
Just open the select drop down menu and try to "search" for something
What is expected?
I'm expecting to see the search icon on right place and have at least some min-width of the select container
What is actually happening?
The width of nz-select container is collapsing so I cannot see the search input and the search icon has bad position

Environment
Info

ng-zorro-antd
9.3.0

Browser
All

select's width is not limited, you should manually set width style.

plz follow @wenqi73 's advice


Support Evaluation Metrics in Card Data

We should be able to add/update model card evaluation metrics in the modelcard metadata (the stuff that is in between the ---s). These updates/additions to model card evaluation data should be validated to make sure no problems occur when pushing to the hub (RE: #2 ).

We are working on this for Autoeval and currently, we decided to add it to dataset metadata as opposed to the model https://github.com/huggingface/autonlp-backend/issues/414

Very helpful link, thank you @nrajani 😄
Some tooling work around this exists in huggingface_hub as well (which looks like its linked in the issue you just shared above):
Model Index Metadata data validation types: https://github.com/huggingface/huggingface_hub/blob/main/src/huggingface_hub/repocard_types.py
Usage to update model index metadata:
https://github.com/huggingface/huggingface_hub/blob/65d3c88a24b648dd65ad76d78f11d76c45a7083c/src/huggingface_hub/repocard.py#L198-L233


Spring Cleaning

Issue #, if available:
Description of changes:

Removed AWS Lambda IAM role - this integration was deprecated on March 20
Added Snyk Cloud IAM role
Updated the parent template (snyk-full.template.yaml) and cleaned up all other templates
Documentation: https://github.com/aws-quickstart/quickstart-snyk-security/pull/48

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@dowen12 any eta when this will merge? :pray:


use pingpong-labs/menus in pingpong-labs/module

Hi, How to use pingpong-labs/menus in pingpong-labs/module?
I have module category and i want use facade category in menu.php in the app/ ,How can I do it ?

@ahmadina - can we close this issue?

Hi @ahmadina,
now I think I unterstood your problem correct, because I had the same problem :)
Since I'm not using the Admin Package, I was not able to attach menu entry.
My screnario is/was the following:
I have a module named "Admin", in this module the admin menu is defined with:
Menu::create('admin-menu', function() ...
I have also a module named "Users" which will be loaded after the admin module.
If I try to append a menu link to the admin-menu via
$leftMenu = Menu::instance('admin-menu');

$leftMenu->url("#", "Test Link");

It doesn't work.
An \Debugbar::info($leftMenu); returns null instead of the existing Menu Object.
Anyway.. I solved the problem with the following.

Create a file named menus.php in the app directory.
Add your menu create statements inside like

<?php

Menu::create('admin-menu', function ($menu)
{
    $menu->setPresenter('Modules\Admin\Presenters\SidebarMenuPresenter');
});

In your module create a new file menus.php
Add the following code in the file

$adminLeftMenu = \Menu::instance('admin-menu');

$adminLeftMenu->dropdown('Users', function ($sub)
	{
		$sub->url("#", "Test");
    	//$sub->route('admin.products.index', 'All Products');
    	//$sub->route('admin.products.create', 'Add New');
	},
	[ 'icon' => 'glyphicon glyphicon-list-alt']
);

Add the Modules/<modulename>/menus.php into the module.json like this:

{
    "name": "Users",
    "alias": "users",
    "description": "",
    "keywords": [],
    "active": 1,
    "priority": 1,
    "providers": [],
    "aliases": {},
    "files": [
        "start.php",
        "menus.php"
    ]
}

Now you have to refresh your browser and it's working...
@gravitano - please correct me, if I'm wrong or if there is an other way to solve this.
Hope this helps :)

Hm weird. I also use the Menu package, and I haven't had any issues with it.
What you say about the null return, it could be caused by a module not yet loaded or something like that.

Hi @nWidart,
i have also checked your code and everything looks good in my modules.
Debugbar told me also, that the module is loaded ( first Admin, second Users ).
For me it's currently a good workaround to define the available menus globally.
Maybe in the next project I will invest some time to get a better solution or I will use your CMS solution ;)

Hi @ahmadina, you can follow @noxify's way to install pingpong/menus in your module. Thanks to @noxify for his explanation :)


Implement a class whitelist for network and postMessage transport

This change switches to using secure foam.box.Contexts with a classlist
injected from data/class_whitelist.json.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #110   +/-   ##
=========================================
  Coverage          ?   63.98%
=========================================
  Files             ?       35
  Lines             ?     1688
  Branches          ?      125
=========================================
  Hits              ?     1080
  Misses            ?      608
  Partials          ?        0

Impacted Files
Coverage Δ

lib/client/api_service.es6.js
34.37% <ø> (ø)

lib/datastore/datastore_container.es6.js
13.69% <0%> (ø)

Continue to review full report at Codecov.

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

Forgot to mention, dependent FOAM2 PR: https://github.com/foam-framework/foam2/pull/658


There's something wrong with the compilation. It wasn't there before.

cargo install --locked --git https://github.com/MystenLabs/sui.git --branch main sui
error:
running: cd "/tmp/cargo-install6nKCYM/release/build/jemalloc-sys-1b5a40304b1640ba/out/build" && "make" "-j" "56"
--- stderr
thread 'main' panicked at 'failed to execute command: No such file or directory (os error 2)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/jemalloc-sys-0.5.2+5.3.0-patched/build.rs:326:19
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: failed to compile sui v1.10.0 (https://github.com/MystenLabs/sui.git?branch=main#43df66ad), intermediate artifacts can be found at /tmp/cargo-install6nKCYM.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

The system I'm using is ubuntu.

have you confirmed that you have the latest version of Rust installed?
rustup update stable

@ybeetle8 are you still running into issues when trying to compile?

@ybeetle8 If this is still a problem, please do let us know. I will close the issue for now.


AJAX support

Are you planning on AJAX support?
I have a large database set which would be mostlikely too big to load inside the component (would make it slower suposedly), so AJAX support would be great.

Awesome, can't wait! :)

@Cannonb4ll The component is in process. See the examples in this page to see the behavior with ajax support https://santiblanko.github.io/#/builder
I think this weekend you can begin to play with the component. Thank you for the feedback.

In this fiddle you can see how to implement the component with ajax support :)
https://jsfiddle.net/santiblanko/dqo6vr57/
In a few days I expect improve the docs with other examples, write some tests and write others components for the search.
Thank you for the interest :)

Thanks mate, will test soon! :)


Hue App is not stable connected to HA-Bridge

Dear all,
My Hue App (iOS) is recognizing the HA Bridge (running on port 80)  , however the connection is not stable. It is  continuously  switching between "Connected" and  "Not Connected". I already entered the latest Hue firmware in the Web-GUI of the HA-Bridge.
Has anyone an idea? The same happend with the android hue app.

I solved it, HA-Bridge was freshly installed and it works fine now. I don´t know where the bug was.


Add PodDisruptionBudget

@regadas, should we expose the config of pod disruption budget in the FlinkCluster or determining it automatically based on JobMode is fine?


RaptorJIT: Bytecodes sometimes fail to decode

RaptorJIT bytecode instructions sometimes do not decode successfully and are rendered as <?> instead. Screenshot:

This is addressed (hopefully properly...) in 56ecffc5670dd93dec96ac66e52c0144463030d4.


New Release

Hey folks, thanks for putting this exporter together. I see that the last current release (v0.12) was from quite some time ago, almost 12 months and there are several fixes in the main branch since then.
Is there anything that's blocking a release of a new version [that you need assistance with]?

Done.


Unclear distinction between 'HYE ' and 'HYE0'

'HYE ' (Armenian) and 'HYE0' (Armenian East) are both mapped to the ISO 639 code hye. What is the difference? My guess is that 'HYE ' is for Armenian in general, either eastern or western. In that case, 'HYE ' should be mapped to hye and hyw.

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

ID: 662c6f54-f90c-52ed-dca2-0f0a0a49fee5
Version Independent ID: 6aa33924-d45e-60c3-a9fd-e317ff662993
Content: Language system tags - Typography
Content Source: typographydocs/opentype/spec/languagetags.md
Product: windows
GitHub Login: @PeterCon
Microsoft Alias: PeterCon

A mapping to hyw will be added to 'HYE '.


Add no_resolve to LoadArgs and wasm_runtime_resolve_symbols so one can

delay resolving of symbols.
This is useful for inspecting the module between loading and instantiating.

Just out of personal curiosity, may I inquire about the purpose of this pull request? Is there a particular use case that our current loading mechanisms are unable to accommodate?

We're

Just out of personal curiosity, may I inquire about the purpose of this pull request? Is there a particular use case that our current loading mechanisms are unable to accommodate?

We're using WAMR along with a scripting runtime and we need to generate dynamic imports. To do this we need to know the function signatures before instantiating the module. So far we've gotten around it by just loading the module first, then inspecting it. Then loading it again. This feels hacky and inefficient. With this functionality we are able to avoid the second load.

We're using WAMR along with a scripting runtime and we need to generate dynamic imports. To do this we need to know the function signatures before instantiating the module. So far we've gotten around it by just loading the module first, then inspecting it. Then loading it again. This feels hacky and inefficient. With this functionality we are able to avoid the second load.

It's good to be informed. There will be some improvements and code refactoring in the area of linking soon. Please stay updated on the progress.

@Andersbakken I found another issue and added a comment, could you help address it so that I can merge the PR?


Making validate_lnurl_pay public

Hi all,
It seems that the validate_lnurl_pay function of the SDK (Rust) is a standalone function that can be made public as it is generic. It looks a lot like the parse function and could be beneficial to many apps that can use it even without using the BreezServices.
What do you think ?
Cheers,

Indeed. We are about to extract out some generic logic (including these functions) to a different crate which the sdk will depend on so the functionality will be exposed as public.

If I may add my 2 cents from the experience gained from implementing the SDK:

Decoding the SuccessAction with the payment_preimage deserves to be part of the public package as well (reason below)

Having a lnurl_pay function that does multiple steps in the background seems to not be the ideal behaviour because the validation of the input happens inside the function, which forces it to return an object with multiple possible error types (LnUrlPayResult). The steps for LNURL pay are:

parse
validate_lnurl_pay
send_payment (normal bolt11 one) from a CallbackResponse
decode_success_action

As you can see, only step iii. is an adapter action on the actual node. Currently the function can either fail with  LnUrlPayError or succeed with an object that itself can be 2 different types of errors. Also, the payment can succeed and the function still fail because of line 420: sha256::Hash::from_str(&details.payment_preimage)?; or line 445: self.persister.insert_payment_external_info.
All of that to say that lnurl_pay should probably be a function that accepts a CallbackResponse and does nothing else. Up to the user to generate that CallbackResponse using the public parse and validate_lnurl_pay. This way, the payment that happens externally and the validation are separated.

Related to #668.


add private flag on add

Had some merge conflict rebase errors. Just tossing and making a new branch


[Docenhancement][Apptemplates-Addition of watercooler section]

Added watercooler section. Please review.

Docs Build status updates of commit 691598d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/water-cooler-home-page.png
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/water-cooler-home-page.png
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/water-cooler-home-page.png
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/water-cooler-home-page.png
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/water-cooler-home-page.png
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 60a299b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 8872f6d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/tdp-configuration.md
:warning:Warning
View
Details

msteams-platform/sbs-send-proactive.yml
:warning:Warning
View
Details

msteams-platform/scenario-index.yml
:warning:Warning
View
Details

:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md
:bulb:Suggestion
View
Details

msteams-platform/assets/UpdateTeamsImages/FindVersionAfterInstallation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/UpdatingTeams.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/UseSpaceToSelectGenerators.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/YoSelectUpdateGen.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Update-Teams/test.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/azure-rsc-configuration.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/graph-permissions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/home-page.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tab-images/shared-channels.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/people-picker-control-capability.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/water-cooler-home-page.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/app-studio-controls.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/shared-channels.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/people-picker-capability.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

msteams-platform/concepts/tdp-configuration.md

Line 23, Column 1: [Warning-duplicate-alt-text] Alt text 'Screenshot showing the Configure page of Teams Developer Portal.' is duplicated. Within an article, alt text must be unique.
Line 40, Column 1: [Warning-duplicate-alt-text] Alt text 'Screenshot showing the Configure page of Teams Developer Portal.' is duplicated. Within an article, alt text must be unique.

msteams-platform/sbs-send-proactive.yml

Line 23, Column 1: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/proactive-helo.png'.
Line 26, Column 1: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png'.
Line 46, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/proactivebot-project.png'.
Line 83, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/app-studio-import-app.png'.
Line 87, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/bot-setup.png'.
Line 95, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/bot-endpoint-address.png'.
Line 120, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/proactive-message-sample.png'.
Line 124, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/uninstall-app.png'.
Line 136, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/proactive-helo.png'.
Line 188, Column 5: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/uninstall-app.png'.
Line 199, Column 1: [Warning-file-not-found] Invalid file link: '~/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png'.

msteams-platform/scenario-index.yml

Line 18, Column 18: [Warning-file-not-found] Invalid file link: './test-scenarioa.yml'.
Line 20, Column 18: [Warning-file-not-found] Invalid file link: './tour-of-csharp/tutorials/numbers-in-csharp.yml'.
Line 22, Column 18: [Warning-file-not-found] Invalid file link: './tour-of-csharp/tutorials/index.md'.
Line 43, Column 18: [Warning-file-not-found] Invalid file link: 'tour-of-csharp/index.md'.
Line 45, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/inside-a-program/index.md'.
Line 47, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/main-and-command-args/index.md'.
Line 51, Column 18: [Warning-file-not-found] Invalid file link: 'fundamentals/types/index.md'.
Line 53, Column 18: [Warning-file-not-found] Invalid file link: 'linq/index.md'.
Line 55, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/concepts/async/index.md'.
Line 59, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/inheritance.md'.
Line 61, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/working-with-linq.md'.
Line 63, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/string-interpolation.md'.
Line 65, Column 18: [Warning-file-not-found] Invalid file link: './tutorials/intro-to-csharp/introduction-to-classes.md'.
Line 72, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-9.md'.
Line 74, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-8.md'.
Line 76, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-7.md'.
Line 80, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/records.md'.
Line 82, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/top-level-statements.md'.
Line 84, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/patterns-objects.md'.
Line 86, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/default-interface-methods-versions.md'.
Line 88, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/mixins-with-default-interface-methods.md'.
Line 90, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/ranges-indexes.md'.
Line 92, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/nullable-reference-types.md'.
Line 94, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/generate-consume-asynchronous-stream.md'.
Line 98, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/breaking-changes.md'.
Line 100, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/version-update-considerations.md'.
Line 107, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/index.md'.
Line 109, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/keywords/index.md'.
Line 111, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/operators/index.md'.
Line 113, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/configure-language-version.md'.
Line 115, Column 18: [Warning-file-not-found] Invalid file link: '../../_csharplang/spec/introduction.md'.

Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/post-publish/application-certification.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/overview.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/build-and-test/app-studio-controls.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md

Line 14, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/open-a-developer-account' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/add-in-submission-guide' will be broken in isolated environments. Replace with a relative link.

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

Docs Build status updates of commit 20aafce:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/tdp-configuration.md
:warning:Warning
View
Details

msteams-platform/scenario-index.yml
:warning:Warning
View
Details

:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md
:bulb:Suggestion
View
Details

msteams-platform/assets/UpdateTeamsImages/FindVersionAfterInstallation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/UpdatingTeams.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/UseSpaceToSelectGenerators.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/YoSelectUpdateGen.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Update-Teams/test.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/azure-rsc-configuration.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/graph-permissions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/home-page.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3688)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tab-images/shared-channels.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/people-picker-control-capability.png
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

msteams-platform/concepts/tdp-configuration.md

Line 23, Column 1: [Warning-duplicate-alt-text] Alt text 'Screenshot showing the Configure page of Teams Developer Portal.' is duplicated. Within an article, alt text must be unique.
Line 40, Column 1: [Warning-duplicate-alt-text] Alt text 'Screenshot showing the Configure page of Teams Developer Portal.' is duplicated. Within an article, alt text must be unique.

msteams-platform/scenario-index.yml

Line 18, Column 18: [Warning-file-not-found] Invalid file link: './test-scenarioa.yml'.
Line 20, Column 18: [Warning-file-not-found] Invalid file link: './tour-of-csharp/tutorials/numbers-in-csharp.yml'.
Line 22, Column 18: [Warning-file-not-found] Invalid file link: './tour-of-csharp/tutorials/index.md'.
Line 43, Column 18: [Warning-file-not-found] Invalid file link: 'tour-of-csharp/index.md'.
Line 45, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/inside-a-program/index.md'.
Line 47, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/main-and-command-args/index.md'.
Line 51, Column 18: [Warning-file-not-found] Invalid file link: 'fundamentals/types/index.md'.
Line 53, Column 18: [Warning-file-not-found] Invalid file link: 'linq/index.md'.
Line 55, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/concepts/async/index.md'.
Line 59, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/inheritance.md'.
Line 61, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/working-with-linq.md'.
Line 63, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/string-interpolation.md'.
Line 65, Column 18: [Warning-file-not-found] Invalid file link: './tutorials/intro-to-csharp/introduction-to-classes.md'.
Line 72, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-9.md'.
Line 74, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-8.md'.
Line 76, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-7.md'.
Line 80, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/records.md'.
Line 82, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/top-level-statements.md'.
Line 84, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/patterns-objects.md'.
Line 86, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/default-interface-methods-versions.md'.
Line 88, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/mixins-with-default-interface-methods.md'.
Line 90, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/ranges-indexes.md'.
Line 92, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/nullable-reference-types.md'.
Line 94, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/generate-consume-asynchronous-stream.md'.
Line 98, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/breaking-changes.md'.
Line 100, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/version-update-considerations.md'.
Line 107, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/index.md'.
Line 109, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/keywords/index.md'.
Line 111, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/operators/index.md'.
Line 113, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/configure-language-version.md'.
Line 115, Column 18: [Warning-file-not-found] Invalid file link: '../../_csharplang/spec/introduction.md'.

Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-first-app-overview.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-and-run.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/post-publish/application-certification.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/overview.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/build-and-test/app-studio-controls.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-personal-tab.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-channel-tab.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-bot.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-messaging-extension.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md

Line 14, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/open-a-developer-account' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/add-in-submission-guide' will be broken in isolated environments. Replace with a relative link.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/tdp-configuration.md
:warning:Warning
View
Details

msteams-platform/scenario-index.yml
:warning:Warning
View
Details

:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md
:bulb:Suggestion
View
Details

msteams-platform/assets/UpdateTeamsImages/FindVersionAfterInstallation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/UpdatingTeams.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/UseSpaceToSelectGenerators.png
:white_check_mark:Succeeded
View

msteams-platform/assets/UpdateTeamsImages/YoSelectUpdateGen.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Update-Teams/test.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/app-badge.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/appScreens.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendee-invitation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/attendeeInvitation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/azure-rsc-configuration.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/badge.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/create-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/createRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/findConversation.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/graph-permissions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/home-page.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/join-room.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/joinRoom.gif
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3688)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tab-images/shared-channels.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/people-picker-control-capability.png
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

msteams-platform/concepts/tdp-configuration.md

Line 23, Column 1: [Warning-duplicate-alt-text] Alt text 'Screenshot showing the Configure page of Teams Developer Portal.' is duplicated. Within an article, alt text must be unique.
Line 40, Column 1: [Warning-duplicate-alt-text] Alt text 'Screenshot showing the Configure page of Teams Developer Portal.' is duplicated. Within an article, alt text must be unique.

msteams-platform/scenario-index.yml

Line 18, Column 18: [Warning-file-not-found] Invalid file link: './test-scenarioa.yml'.
Line 20, Column 18: [Warning-file-not-found] Invalid file link: './tour-of-csharp/tutorials/numbers-in-csharp.yml'.
Line 22, Column 18: [Warning-file-not-found] Invalid file link: './tour-of-csharp/tutorials/index.md'.
Line 43, Column 18: [Warning-file-not-found] Invalid file link: 'tour-of-csharp/index.md'.
Line 45, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/inside-a-program/index.md'.
Line 47, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/main-and-command-args/index.md'.
Line 51, Column 18: [Warning-file-not-found] Invalid file link: 'fundamentals/types/index.md'.
Line 53, Column 18: [Warning-file-not-found] Invalid file link: 'linq/index.md'.
Line 55, Column 18: [Warning-file-not-found] Invalid file link: 'programming-guide/concepts/async/index.md'.
Line 59, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/inheritance.md'.
Line 61, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/working-with-linq.md'.
Line 63, Column 18: [Warning-file-not-found] Invalid file link: 'tutorials/string-interpolation.md'.
Line 65, Column 18: [Warning-file-not-found] Invalid file link: './tutorials/intro-to-csharp/introduction-to-classes.md'.
Line 72, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-9.md'.
Line 74, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-8.md'.
Line 76, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/csharp-7.md'.
Line 80, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/records.md'.
Line 82, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/top-level-statements.md'.
Line 84, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/patterns-objects.md'.
Line 86, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/default-interface-methods-versions.md'.
Line 88, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/mixins-with-default-interface-methods.md'.
Line 90, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/ranges-indexes.md'.
Line 92, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/nullable-reference-types.md'.
Line 94, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/tutorials/generate-consume-asynchronous-stream.md'.
Line 98, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/breaking-changes.md'.
Line 100, Column 18: [Warning-file-not-found] Invalid file link: 'whats-new/version-update-considerations.md'.
Line 107, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/index.md'.
Line 109, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/keywords/index.md'.
Line 111, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/operators/index.md'.
Line 113, Column 18: [Warning-file-not-found] Invalid file link: 'language-reference/configure-language-version.md'.
Line 115, Column 18: [Warning-file-not-found] Invalid file link: '../../_csharplang/spec/introduction.md'.

Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/post-publish/application-certification.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-and-run.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-channel-tab.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-personal-tab.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/deploy-and-publish/overview.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'concepts/build-and-test/app-studio-controls.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-first-app-overview.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-bot.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning-redirected-file-not-removed] Redirected file 'build-your-first-app/build-messaging-extension.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md

Line 14, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/open-a-developer-account' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/add-in-submission-guide' will be broken in isolated environments. Replace with a relative link.

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

Test PR. Closing it