LLM tool call not shown for streamed response

Description
The Logfire UI nicely shows the tool call by an LLM for non-streamed responses

But for streamed responses the Assistant box is empty.

Code to reproduce
# Test logfire streamed responsea

from openai import Client

import logfire

logfire.configure()
logfire.instrument_openai()

client = Client()

response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Create a Superhero named Monkey Boy."}],
    stream=True,
    stream_options={"include_usage": True},
    tool_choice={"type": "function", "function": {"name": "return_superhero"}},
    tools=[
        {
            "type": "function",
            "function": {
                "name": "return_superhero",
                "parameters": {
                    "properties": {
                        "name": {"title": "Name", "type": "string"},
                        "age": {"title": "Age", "type": "integer"},
                        "power": {"title": "Power", "type": "string"},
                        "enemies": {
                            "items": {"type": "string"},
                            "title": "Enemies",
                            "type": "array",
                        },
                    },
                    "required": ["name", "age", "power", "enemies"],
                    "type": "object",
                },
            },
        },
    ],
)
for chunk in response:
    print(chunk)

Related (closed) issue: https://github.com/pydantic/logfire/issues/54
Python, Logfire & OS Versions, related packages (not required)
logfire="0.50.1"
platform="macOS-15.0.1-arm64-arm-64bit"
python="3.10.12 (main, Jul 15 2023, 09:54:16) [Clang 14.0.3
(clang-14<IP_ADDRESS>.1)]"
[related_packages]
requests="2.32.3"
pydantic="2.8.2"
openai="1.52.0"
protobuf="4.25.3"
rich="13.7.1"
tomli="2.0.1"
executing="2.0.1"
opentelemetry-api="1.25.0"
opentelemetry-exporter-otlp-proto-common="1.25.0"
opentelemetry-exporter-otlp-proto-http="1.25.0"
opentelemetry-instrumentation="0.46b0"
opentelemetry-proto="1.25.0"
opentelemetry-sdk="1.25.0"
opentelemetry-semantic-conventions="0.46b0"

I'm AFK but this sounds familiar and I see an old logfire version, can you please check if this still happens with the latest versions of logfire and openai?

Thanks, I should have checked with latest versions. It is still an issue. I have opened PR https://github.com/pydantic/logfire/pull/545 now to address this.


🐞 Text was accidentally hidden when the Enter key was pressed

Description
When switching the input method to Chinese or Japanese and typing part of the text, press the Enter button a few times, the text is accidentally hidden
https://github.com/user-attachments/assets/d97e53ce-ec60-4977-9ab0-27b714726943
To Reproduce

When switching the input method to Chinese or Japanese
and typing part of the text,
press the Enter button a few times,
the text is accidentally hidden

Expected Behavior
Fixed text being hidden by accident
Version Information
CodeEdit: [e.g. 0.2.x-alpha.y]
macOS: [e.g. 15.4]
Xcode: [e.g. 14.2]
Additional Context
No response
Screenshots
No response

This should be fixed with the linked PR, I'm going to close this but please re-open it if the issue persists.


Refactor network prune-merge tool for performance

The network prune and merge tool (introduced with #177) allows for simple adjustments to the routing hydrofabric to reduce the number of short segments.
However, that tool is not efficient enough to process the entire CONUS Full Resolution NWM routing dataset.
This issue will be resolved when the tool has been re-factored to execute for the full domain.

@awlostowski-noaa
I'm adding this network-adjustement-related issue into the v02 milestone due June 1 2021. I think that in general, any issues we track for the work we are doing with the GID team can be captured under that head. When we get to the beginning of summer, if we do not have a sufficient solution with respect to segment lengths, we can make a more specific milestone.

@awlostowski-noaa
I'm adding this network-adjustement-related issue into the v02 milestone due June 1 2021. I think that in general, any issues we track for the work we are doing with the GID team can be captured under that head. When we get to the beginning of summer, if we do not have a sufficient solution with respect to segment lengths, we can make a more specific milestone.


Docker CLI discards aliases defined in ~/.bash_profile

When I launch Kitematic's Docker CLI, it doesn't source my ~/.bash_profile. It would be jolly if either it did or there were a separate rc (e.g. ~/.dockerclirc) file loaded automatically when the CLI starts.
When I launch Kitematic's Docker CLI, it appears to source my ~/.bash_profile, evidenced by env vars being set, but does not preserve any of the aliases defined therein.

The CLI should be loading your default shell - How did you assert that the .bash_profile wasn't loaded?

Hrm. It appears you're correct. I do see my env vars set. However, the CLI seems to have discarded all of my aliases (which is what I originally noticed).

@birdonfire If the env is set, then aliases should follow too - Are they all set within your .bash_profile or .bashrc?
See: http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html

Closing this due to lack of feedback. Please re-open if needed.

I have the same issue. There is my Dockerfile:
# https://hub.docker.com/_/php/
FROM php:5.5.23-fpm

LABEL maintainer "Lesnykh Ilia"

USER www-data

ADD .bash_profile /var/www/.bash_profile

SHELL ["/bin/bash", "-c"]

RUN source /var/www/.bash_profile

Then after container built I run docker exec -it CONTAINER_NAME bash I did not see my aliases defined into /var/www/.bash_profile. But if I execute source /var/www/.bash_profile manually – everything is ok.

@Aliance sourcing during build, does nothing.
Run it as part of your CMD or simply move it to a location BASH is looking for.


how to apply key bindings

What's the secret sauce to get either of these to work in the custom_key_bindings example in Windows Terminal? Am I specifying the handler wrong?
    // rl.bind_sequence(
    //     KeyEvent {
    //         0: KeyCode::Char('H'),
    //         1: Modifiers::CTRL,
    //     },
    //     Cmd::Kill(Movement::BackwardChar(1)),
    // );

    rl.bind_sequence(KeyEvent::ctrl('h'), Cmd::Kill(Movement::BackwardChar(1)));

I am not sure (and I don't have access to a windows desktop right now) but I guess it is because on unix, there is no way to make the distinction between Ctrl-h and Ctrl-H: https://github.com/kkawakam/rustyline/blob/master/src/keys.rs#L93
And we apply the same logic on Windows!

For the record, I've tried it with upper and lower and neither works on Windows. I added some debugging and it appears to be registered properly. It just doesn't trigger when you tyle Ctrl-h or Ctrl-H
    Finished dev [unoptimized + debuginfo] target(s) in 1.01s
     Running `C:\CarTar\debug\examples\custom_key_bindings.exe`
Event: [KeySeq([KeyEvent(Tab, NONE)])] Handler: ["conditional"]
Event: [KeySeq([KeyEvent(Char('E'), CTRL)])] Handler: ["conditional"]
Event: [KeySeq([KeyEvent(Char('H'), CTRL)])] Handler: ["Kill(BackwardChar(1))"]
Event: [KeySeq([KeyEvent(Char('X'), CTRL), KeyEvent(Char('E'), CTRL)])] Handler: ["Suspend"]
Event: [KeySeq([KeyEvent(Char('f'), ALT)])] Handler: ["conditional"]
>

You may be able to spot the issue by activating debug traces.
Just add this line:
https://github.com/kkawakam/rustyline/blob/master/examples/example.rs#L82-L84
fn main() -> rustyline::Result<()> {
    env_logger::init(); // <--

And then:
set RUST_LOG=rustyline=debug
cargo run --example custom_key_bindings 2> debug.log

I did that (without the redirection), and typed time in and then hit ctrl+h 3 times.
So,

We must fix this line:
https://github.com/kkawakam/rustyline/blob/master/src/keys.rs#L36

            '\x08' => E(K::Backspace, mods ^ CTRL),

or remove the CTRL bit when c.is_control() here:
https://github.com/kkawakam/rustyline/blob/master/src/tty/windows.rs#L204

You must use Backspace in your custom bindings.

Or to keep the distinction between the backspace key and ctrl-h, we need to fix this:
https://github.com/kkawakam/rustyline/blob/master/src/tty/windows.rs#L180
                        winuser::VK_BACK => K::Backspace,

And skip https://github.com/kkawakam/rustyline/blob/master/src/keys.rs#L36 on windows.
I will be able to test on windows tomorrow...

https://github.com/prompt-toolkit/python-prompt-toolkit/pull/1384

I changed this:
           '\x08' => E(K::Backspace, mods),           // '\b'

to this:
            '\x08' => E(K::Char('H'), mods | M::CTRL), // '\b'

and it seems to work fine on windows now.

Thanks.
I will test this branch tomorrow:
https://github.com/gwenn/rustyline/blob/windows_keys/src/keys.rs#L38-L39

See #547

Looks good. Ship it! :)

Version 9.0.0 released.


[release-1.18] LowNodeUtilization: log when a node is unschedulable

Fixes: #381

/lgtm
/assign @damemi


Pilot attempt for 'aggressive edits' on CHANGELOG.md

@lattner As promised. This goes up to SE-0111.

Looks great!


Compiling libtensorflow for ios issues : can't fine Eigen/Core

Click to expand!
Issue Type
Build/Install
Source
source
Tensorflow Version
tf 2.10
Custom Code
No
OS Platform and Distribution
MacOs ventura 13.0
Mobile device
No response
Python version
No response
Bazel version
5.3.2
GCC/Compiler version
clang 14.0 (Xcode shipped)
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Hello !

I am not able to build libtensorflow.so for ios.
I just `./configure` and accepted all defaults.

I can build for my mac:
`bazel build -c opt //tensorflow:libtensorflow.so`
but cross compiling for ios
`bazel build -c opt --config=ios //tensorflow:libtensorflow.so`

gives me this error

`
ERROR: /Users/SX/Documents/soundx-ai/vendor/tensorflow/tensorflow/cc/saved_model/BUILD:319:11: Compiling tensorflow/cc/saved_model/metrics.cc failed: (Aborted): wrapped_clang_pp failed: error executing command external/local_config_cc/wrapped_clang_pp '-D_FORTIFY_SOURCE=1' -fstack-protector -fcolor-diagnostics -Wall -Wthread-safety -Wself-assign -fno-omit-frame-pointer -g0 -O2 -DNDEBUG ... (remaining 32 arguments skipped)
In file included from tensorflow/cc/saved_model/metrics.cc:16:
In file included from ./tensorflow/cc/saved_model/metrics.h:25:
In file included from ./tensorflow/core/lib/monitoring/counter.h:19:
In file included from ./tensorflow/tsl/lib/monitoring/counter.h:85:
In file included from ./tensorflow/tsl/lib/monitoring/collection_registry.h:109:
In file included from ./tensorflow/tsl/lib/monitoring/collected_metrics.h:28:
In file included from ./tensorflow/tsl/lib/monitoring/metric_def.h:24:
In file included from ./tensorflow/tsl/lib/monitoring/types.h:22:
In file included from ./tensorflow/tsl/platform/types.h:21:
In file included from ./tensorflow/tsl/platform/bfloat16.h:20:
./third_party/eigen3/Eigen/Core:1:10: fatal error: 'Eigen/Core' file not found
#include "Eigen/Core"

I have a eigen3 lib installed with brew, in my /opt/homebrew/Cellar/eigen/3.4.0_1/include/eigen3/Eigen/Core, but I did not get how I could give this information to bazel. I'm not able to play with the path directly.
Any clue to solve this problem ?
Thank you!

### Standalone code to reproduce the issue

```shell
bazel build -c opt --config=ios //tensorflow:libtensorflow.so

Relevant log output
No response

OK I was able to solve my problem myself. I had to manually call the bazel rule "install_eigen_headers" from third_party/eigen3
Is it normal I have to call it myself ?

@simdax,
Could you please try installing TensorFlow v2.10 with compiler Clang from xcode 10.14 with Bazel 5.1.1 as those are tested build configurations & please take a look at this official doc link for the reference and check if you are facing the same error. Thank you!

I can be even more specific. One of the failing project is
saved_model:util
bazel build -c opt //tensorflow/cc/saved_model:util works
bazel build -c opt //tensorflow/cc/saved_model:util --config=ios don't works

Hi @simdax ,
Could you please confirm what option you have chosen while configuring ./configure for below option.
Do you wish to build TensorFlow with iOS support? [y/N]:
If you missed choosing y  then it might not be supporting IOS. Please cross check and try with y option for above configuration part and lets know if still facing issue.
Thankyou!

Yes I can confirm that. One of the problem is linked to the "if_mobile" option in bazel. All the sources built with it failed.
I think TF is assuming building for IOS need to be TFlite, which is not my case ?

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Pattern mismatch

I'm extracting images using ctapipe from the muonic shower, simulated in CORSIKA at an energy of 1e5 GeV. The coordinates of the four telescopes given in CORSIKA are as follows-
x(cm)   y(cm)   z(cm)
0       -8485     0            TEL. 1
8485     0        0            TEL. 2
0        8485     0            TEL. 3
-8485     0        0            TEL. 4
I'm attaching the telescopic images that I've got. I've arranged the telescopic images in accordance with the aforementioned geometric location.

While I was going through the slides presented by F. Montanet in ESIPAP 2014, I saw the telescopic images (labelled as 1,2,3,4 in green color font) given in slide no 92 ( the screenshot is attached below).

Even though the parameters in the input card may differ, the pattern of the image should have matched. I've expected diametrically opposite triggerings for oppositely located telescopes (as I can see in the screenshot). Why does the image obtained via ctapipe doesn't hold the pattern? Am I misunderstanding something or is there any internal rotation happening?
I'm using the following function to extract images-
def` display_event(event, source):
      ntels = `len(event.r0.tels_with_data)
      for ii, tel_id in enumerate(event.r0.tels_with_data):
                                nn = int(ceil(sqrt(ntels)))
                                ax = plt.subplot(nn, nn, ii + 1)
                                geom = source.subarray.tel[tel_id].camera.geometry
                                disp = CameraDisplay(geom, ax=ax)
                                disp.pixels.set_antialiaseds(False)
                                disp.autoupdate = False
                                disp.cmap = 'RdBu_r'
                                chan = 0
                                image = event.dl1.tel[tel_id].image
                                mask = tailcuts_clean(source.subarray.tel[tel_id].camera.geometry, image, picture_thresh=10, boundary_thresh=5)
                                cleaned = image.copy()
                                cleaned[~mask] = 0
                                disp.image = cleaned

It seems your simulations are made with azimuth=180 degrees, which means you also have to rotate your cameras by 180 degrees. Also if the zenith angle is larger than 0, you would have to modify the telescope positions such that they are projected onto a plane normal to the pointing direction.

Please see #1564, where there is an example on how to do this.


CAV Flow View #4: Map

This is the parent ticket of CAV Flow "Map" view.

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.
Belonging to Epics:

[EPIC] [@telmodias] #337 - Views: CAV Flow

Children:

[x] #460 - UI of CAV Flow View #4: Map
[ ] #461 - Frontend of CAV Flow View #4: Map
[ ] #462 - Firebase for CAV Flow View #4: Map

Design Elements:
(1) MAP
Map
Pointer Icon on the bottom toolbar and on the Map
(2) REQUEST SUMMARY
Headline
Text Summary
Requester Profile Image
(3) FULL REQUEST
Profile Data

Name / request date. stars. distance
Request Data
** Headline
** Full text of Request
Volunteer UI
** Input Text
** Submit Button


add docs-test

from https://github.com/d3/d3/pull/3673
fix a few malformed links; the automatic renumbering of duplicate links with -1 seems fragile, so we make them explicit rather than making the link checker smarter.

I think it might be an leftover from when you crawled the generated HTML, because there is an A tag here for downloading the pre-built UMD bundles:
https://github.com/observablehq/plot/blob/2d4a2f63283b817c6f1aa75b2715d006a68f68e9/docs/getting-started.md?plain=1#L85-L86
But the new code only looks for Markdown links, so I think we don’t need this exemption anymore. (And I think it’s okay that you can opt-out of link checking by using an A element instead of a Markdown link.)

Oh, I see now. It’s just crawling the files and breaking on the symlink to dist/plot.umd.js because it hasn’t been built. Yeah. There’s no need to stat .js files. I’ll revert the last commit.


Compile latest branch in Visual Studio failing

I'm trying to compile Marksman on Windows using Visual Studio 2017.
However it seems that the SnipeSharp API Reference doesn't seem to match the code.
The marksman code trying to call SearchFilter / Location / Statuslabel cannot as theirs no a constructor to take 1 argument. (all the constructors take 0 arguments in the class) so error CS1729 pops up 11 times.
What SnipeShare version are you using? - I've tried each of the forked versions but can't seem to find one that makes it work.
Or do you have any Windows build instructions?

You are correct, Marksman is using an updated version of the SnipeSharp API.
To build Marksman, you will need to use our version of the API here.


Look at Fotoware APIs

Relevant links

https://www.fotoware.com/integrations
https://learn.fotoware.com/Integrations_and_APIs/001_The_FotoWare_API
https://api.fotoware.com/

Without knowing more about the Fotoware product and without having access to a license in order to try a prototype, it's difficult to tell how easy or difficult it would be to make a Sanity integration.
That being said, they have a REST API with documentation and they list integrations with several other products/platforms, including WordPress, Microsoft Office, Adobe CC, Episerver, and more - so it's definitely possible to integrate it with different types of products.
This integration with Enonic is written in JavaScript, so that could be a source of inspiration: https://github.com/enonic/app-fotoware
The mention of a webhook system in order to receive updates about any changes in Fotoware could also be very interesting for us: https://github.com/enonic/app-fotoware/blob/master/docs/index.adoc#webhooks


DS - Icon Library

Status

Discovery: Done
Design: Done
Implementation: In progress

Discovery

[x] Design: Initial discovery on icon libraries
[x] VADS: Set up their USWDS/Material icons
[x] Engineering: Review VADS icons and determine what we can reference from them

Design

[x] Design: Determine VADS/USWDS/Material replacement for all mobile app icons
[x] Design: Export non-VADS icons for implementation

Implementation

[ ] Engineering: Update Icon component
[ ] VADS: Will need their support to add mobile icons to their files
[ ] Engineering: Update all icons in icon library
[ ] Engineering: Swap out the icons in our components (Is this something design can help with?)
[ ] Design: Swap out the icons in Figma (1 sprint)
[ ] Flagship: Update icons (Could they do this with the Icon component?)

Project Status Overview
The Mobile Design System team would like to use an Icon Library to make incorporating approved and consistent icons in the Mobile App easier.
Project Objective:

Determine strategy for creating an icon library
Build Icon Library

Current Dependencies / Blockers

Blockers

Blocker
Team / Owner
Est to Resolution

Internal dependency ?

External dependency ?

Project Timeline

Milestones

Monthly Update for Stakeholders

Updates

Month
Project Health
Progress & Key Accomplishments
Issues/Risks/Blockers

03/24
On Track
Coordinating with VADS around their timing of switching to Material icons

Month Year
.....

Month Year

Month Year

Detailed Project Scope
Problem Statement
Assumptions

Assumptions that need to be true for this project
1.)
2.)
3.)

Risks

Risks identified and accepted by stakeholders
1.)
2.)
3.)

Project Scope

Items in and out of scope

In Scope
Out of Scope

Important Project Links

Links

Github Epic
Github VA Mobile Page

Product Brief

Product Canvas
Design

Discovery
Mockups
Final Design
Figma File

Research

Research Plan
Research Results and Findings
-Analytics
-Decision Log

Team Members
Contact List
VA:

Mobile OCTO Product Leads:  Ryan Thurlwell
VA OCTO Product Leads:
External Team 1 & Role: VADS, Matt Dingee
External Team 1 & Role:

Ad Hoc:

Mobile Team: Global, Health and Benefits, Design System, QA, API
Mobile Team Lead:  Kelly Lein
FE Engineering: Narin Ratana
Design: Jessica Woodin

Questions

Open Questions

Closed Questions

Question
Answer
Owner

Change / Decision Log
Product will need to create on in the Github folder and link it here.
Checklist

Toggle Product Checklist
Project Kickoff & Requirements Gathering

[ ] PM to create new Github epic and fill out accordingly (Type - Epic, Template - Epic Ticket

[ ]  Updated so it is seen in Mobile and External Github Boards - may need to view this epic in Github and not Zenhub

[ ] PM to create new Github folder for feature or update existing

[ ] Create a separate document for the project's decision log - link it here

[ ] Other:

Q2 SWAG:
UX - 0.5 sprint
FE - 2 sprints


Ability to poll and update the status of  the lights?

Hi, I find tha a number of bulbs will show a ‘connection error’ but the status will update if a value/request is sent. Is there a way (a command) that can be sent to update the status value.  Maybe I could set it to poll every x seconds/minutes ?

Connection errors are fixed with v1.7.0.
You just need to set your poll interval in your bridge settings once.


Force world save before shutdown/restart

We discovered the hard way that restarting the Docker container will cause a rollback of the server world (20 minutes?) because it appears to only save the state on a periodic cadence.
Is there a way to manually force a save before executing a restart? Or, can I otherwise bring down the container in a way that will trigger a save?
A game "cheat" exists to perform a save, but I read that it doesn't work, and cheats allegedly can't be executed on a multiplayer server anyway?
Thanks!

That is because of an outdated container image. If you pull the latest version the world will be saved on shutdown. Iron Gate changed the way the server is being shut down from creating a file to signal a shutdown to sending a SIGINT which broke the shutdown script. See https://github.com/lloesche/valheim-server-docker/issues/13


[Automation] automation account/configuration/hrwg/runtime-environment/source-control: Add support for some uncovered commands

Related aaz PR: https://github.com/Azure/aaz/pull/391

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

az automation account list-keys
az automation account show-linked-workspace
az automation configuration create/show/list/show/update/delete/show
az automation configuration show-content
az automation runtime-environment create/show/list/show/update/delete/show
az automation runtime-environment package create/show/list/show/update/delete/show
az automation source-control sync-job stream show/list

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Automation


[BUG]: Unable to find M365 groups in Configure communications step - Upgrade Wizard

On the Configure communications methods page, when trying to configure group, it does not display all of the M365 security groups even though the user is an owner of the group and the group is an M365 group so by definition, mail enabled.

@medicineshow is this for the CoE starter kit or Creator Kit?

It's the wizard in the Creator Kit

@denise-msft  Apologies but i was slightly shocked at getting the response after 7 months. Unfortunately we have not had much time in the recent months to look at the CoE but my original issue was as stated. On that Configure communications methods page, it did not display all of the M365 security groups that I would have access to. However it does look like you have updated the app since then and include the ability to search by Object ID so i would consider this resolved thank you.

The point I believe is you posted this in the wrong place. This is for the
Power App Creator kit, not the CoE.
Regards,
Steven Perry
@.***
On Wed, Jul 19, 2023, 8:02 AM Mark Enfield @.***> wrote:

@denise-msft https://github.com/denise-msft Apologies but i was
slightly shocked at getting the response after 7 months. Unfortunately we
have not had much time in the recent months to look at the CoE but my
original issue was as stated. On that Configure communications methods
page, it did not display all of the M365 security groups that I would have
access to. However it does look like you have updated the app since then
and include the ability to search by Object ID so i would consider this
resolved thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/powercat-creator-kit/issues/224#issuecomment-1641958169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNR6PVDCFAV3WYXRKFNJKTXQ7EGHANCNFSM6AAAAAATEKLKHI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


append vm deletion check

What type of this PR

Bug fixes

append check for vm delete. The vm pod should be deleted when subnet for ns has been changed.
Which issue(s) this PR fixes:
Fixes #(issue-number)

已回合release-1.8和release-1.9分支


[CARBONDATA-1774] [PrestoIntegration] Not able to fetch data from a table with Boolean data type in presto

Not able to fetch data from a Carbon table with Boolean data type in presto
Jira Link :https://issues.apache.org/jira/browse/CARBONDATA-1774
Problem: It was not Supported in last release we should support it now
Solution Add The support For Boolean Stream Readers to read boolean data type from carbon
New Classes Added
1.BooleanStreamReader.java
Classes Changed
1.CarbonVectorizedRecordReader:  To include the boolean type in its measure type
2.StreamReaders: If cluase is added in case java type is boolean
How Testing IS Done
1.Test Case Are Added for Boolean Data Type In PrestoAllDataType
2.mvn clean install is passing

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2260/

restest this please

@chenliang613 please review this pr

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1038/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2515/

retest this please

retest sdv please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2269/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1048/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2281/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1059/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1067/

please rebase @anubhav100

@chenliang613 rebase done

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1153/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2369/

retest this please

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1155/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2371/

retest this please

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2376/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1160/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2377/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1161/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2381/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1165/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2580/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2585/

retest this please

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2586/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2410/

retest this please

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1186/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2413/

retest this please

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1188/

@chenliang613 I have rebased the code please review it seems like CI is unstable it keeps on failing but I have clean build on my machine

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2417/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1192/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2420/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1196/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2457/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1231/


Security updates

This activity includes,

Security Support in IGNITE.
Fix for intermittent failures while running TCs as a package.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Send post-payment Invoices with Checkout

https://stripe.com/docs/payments/checkout/post-payment-invoices
How do I set InvoiceCreation to true with this SDK?
when using
stripe.sessions.create(...)

created PR
https://github.com/vapor-community/stripe-kit/pull/155

resolved with the pr
https://github.com/vapor-community/stripe-kit/pull/156


System-wide Push to Talk

Would adding support for system-wide Push to Talk be possible? Currently, it will only work if the window has focus (as stated by Discord on the browser version itself), but is there any workaround?

I don't know if it is possible, but it's worth a try

This should be possible. You can use Electron GlobalShortcut https://www.electronjs.org/docs/latest/api/global-shortcut for a system-wide keyboard shortcut.
The only concern is finding and running the Discord javascript that enables the microphone and transmits the audio.

The only concern is finding and running the Discord javascript that enables the microphone and transmits the audio.

I've got two ideas in mind:

Abusing the mic off button of the Discord client, not clean at all but will work fine
Using a preload script to wrap a custom function around the browser's sound API, to have control over the stream requested by Discord and mute it whenever the globalShortcut is not pressed

My only concern about the second one is the CPU usage, we will need to keep an eye on the activity monitor while testing it


improvement in protect.html

issue #18 completed
Improvement of the interface.

[X] New feature (non-breaking change which adds functionality)

Checklist:

[X] I have made this from my own
[ ] I have taken help from some online resourses
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Excellent work. Thanks for contributing


SQLAlchemy Cache Issues

This is pretty simple to override but just giving you a heads up that the current sqlalchemy definition does not work with MySQL since it requires a length specified for varchar columns: VARCHAR requires a length on dialect mysql
class FullLLMCache(Base):  # type: ignore
    """SQLite table for full LLM Cache (all generations)."""

    __tablename__ = "full_llm_cache"
    prompt = Column(String, primary_key=True)
    llm = Column(String, primary_key=True)
    idx = Column(Integer, primary_key=True)
    response = Column(String)

It also failed with sqlalchemy < 1.4 due to a bad import btw, you may want to pin your requirements.
I'm also curious what the purpose of the idx column is. Seems to always be set to 0 when testing with the sqlite cache.

thanks for flagging - sqlalchmey should be fixed
idx column is used when multiple prompts are sent to api at once. in most cases, only one prompt is sent so will often be 0


[doc] add common questiosn and answers

how to write contextual pattern?
how to transform regex?
how to access the regex group in fix? https://discord.com/channels/1107749847722889217/1113524796316200980/1154685358609551400

added


ci: add ensureJITFastest

This commit adds bench.check make target to ensure that JIT is the
fastest engine among others.  There was a performance degration
in #287 which has been resolved in #316, but only found manually.
The target sets a linker flag in vs/bench_test.go which results in running
TestFacIter_JIT_Fastest  instead of BenchmarkFacIter_Invoke.
The target bench make target doesn't set the flag so
BenchmarkFacIter_Invoke is run and produces rich benchmark output
into stdout and doesn't run `TestFacIter_JIT_Fastest.

OK cool this works
JIT   137134	      8126 ns/op
interpreter   523346	      2434 ns/op
wasmer-go   897148	      1441 ns/op
wasmtime-go   406878	      3125 ns/op
--- FAIL: TestFacIter_JIT_Fastest (5.13s)
    --- FAIL: TestFacIter_JIT_Fastest/interpreter (0.00s)
        assertion_compare.go:332:
            	Error Trace:	bench_fac_iter_test.go:169
            	Error:      	"8125.853340528242" is not less than "2434.2552403190243"
            	Test:       	TestFacIter_JIT_Fastest/interpreter
            	Messages:   	[JIT engine must be faster than interpreter. Run BenchmarkFacIter_Invoke with ensureJITFastest=false instead to see the detailed result]
    --- FAIL: TestFacIter_JIT_Fastest/wasmer-go (0.00s)
        assertion_compare.go:332:
            	Error Trace:	bench_fac_iter_test.go:169
            	Error:      	"8125.853340528242" is not less than "1440.9133754965735"
            	Test:       	TestFacIter_JIT_Fastest/wasmer-go
            	Messages:   	[JIT engine must be faster than wasmer-go. Run BenchmarkFacIter_Invoke with ensureJITFastest=false instead to see the detailed result]
    --- FAIL: TestFacIter_JIT_Fastest/wasmtime-go (0.00s)
        assertion_compare.go:332:
            	Error Trace:	bench_fac_iter_test.go:169
            	Error:      	"8125.853340528242" is not less than "3124.905979187865"
            	Test:       	TestFacIter_JIT_Fastest/wasmtime-go
            	Messages:   	[JIT engine must be faster than wasmtime-go. Run BenchmarkFacIter_Invoke with ensureJITFastest=false instead to see the detailed result]
FAIL


Scrollbar can stay active even if mouse button is relesed

Using Atom 1.0.5 on Windows 7 64-bit.
Steps to reproduce:

Click and hold on the dragging thing on the scroll bar with the left mouse button (like when you are scrolling).
While continuing to hold the button, move your mouse out towards the center of the screen (away from the scroll bar's area).
Click and release the middle mouse button (the scroll wheel button).
Let go of the left mouse button.

What happens:

The icon of the scroll bar stays as a square (rather than the small rounded style) like when you click and hold on it.
If you move your mouse back to the scroll bar, the scroll bar's position will follow your mouse, even when no buttons are pressed.

Clicking on the scroll bar again fixes the issue.

This is also present in Chrome 44, so I don't think this is Atom-specific.
Can you please report this to Chromium's bug tracker instead?  Thanks.


Adjusted asn1 encoder so that it doesn't include empty attributes

Fixes https://github.com/kurtbrose/pyjks/issues/34

Ah, seems like the tests are pinned against pyasn1 0.1.7, which doesn't support ifNotEmpty.

@mahmoud What do you think? Should we require pyasn1 v0.3.2 or higher, og should I make it work with older versions?

So, 0.3.2 has been out for about a year, that seems pretty reasonable. I also went through the changelog line by line since 0.1.7 and didn't see anything that looked breaking for our use, so I'm OK with a requirement upgrade. A few behaviors might change for some corner-case users, but that's what the issue tracker is for. :)
Don't forget to update the requirements.txt as well as making the setup.py >= entry. Thanks!

I had to go up to 0.3.5, as there was some bugs in 0.3.2, .3 and .4. It came out just shy of a year ago, hope it's ok.
I also snuck in some other small changes.

LGTM! Thanks! :)


Integration tests for REMS disabled

Proposed solution

See #513
DoD (Definition of Done)

Testing

With #596, this is not relevant any more.


Access name of iRODS Owner for a Collection or DataObject

It would be very useful to have access to the the owner of a particular file or collection so this could be displayed on a UI, especially for collections that are shared between multiple users. This may ultimately be part of a larger ACL feature but in the short term could this be made available via a .Owner string attribute that would be part of IRodsObj or similar?
Simon.

Looks like that information is being passed to GoRods:
https://github.com/jjacquay712/GoRods/blob/master/collection.go#L412
However it's not being saved to the Collection or DataObj struct upon initialization:
https://github.com/jjacquay712/GoRods/blob/master/collection.go#L58
https://github.com/jjacquay712/GoRods/blob/master/dataobj.go#L56
I'll setup some interface methods and implement them for both object types so you can get access to that data. In the meantime, some of that info can be grabbed using the DataObj.Stat() method:
https://godoc.org/github.com/jjacquay712/GoRods#DataObj.Stat
statInfo, _ := myDataObj.Stat()

owner := statInfo["ownerName"].(string)

New methods available for DataObj and Collection:
GetOwnerName() string
GetCreateTime() int // Unix epoch time
GetModifyTime() int  // Unix epoch time

Hi John,
I can confirm this is working nicely, many thanks.


Add tag to render the react-refresh script

I wanted to raise another suggestion for django-vite.
When working with @vitejs/plugin-react-refresh, we need to include this script to enable HMR.
<script type="module">
  import RefreshRuntime from 'http://localhost:3000/@react-refresh'
  RefreshRuntime.injectIntoGlobalHook(window)
  window.$RefreshReg$ = () => {}
  window.$RefreshSig$ = () => (type) => type
  window.__vite_plugin_react_preamble_installed__ = true
</script>

It would be fantastic if we could have a {% vite_react_refresh_tag %} or something similar to render this script. It would only render the script if DEBUG is true.
Thanks again for your wonderful work on this library.
Ref: https://vitejs.dev/guide/backend-integration.html

Duplicate of #14

I think this has been done with #53 but not released yet?

I think this has been done with #53 but not released yet?

Seems like it is released now in version 2.1.0 🎉


map scalebar and north arrow

The main map could greatly benefit from a scalebar and maybe a north arrow. A linear measurement tool might also be nice.

This is an enhancement that referenced in #225. The linear measurement tool is another enhancement that we are looking into.


fix: keystone panic on invalid auth token

这个 PR 实现什么功能/修复什么问题:
修正：验证keystone token的管理token无效时报nil pointer panic
是否需要 backport 到之前的 release 分支:

release/2.10.0
release/2.11
release/2.12

/area keystone

Codecov Report

Merging #3046 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master   #3046   +/-   ##
======================================
  Coverage    7.17%   7.17%
======================================
  Files         478     478
  Lines       76801   76801
======================================
  Hits         5509    5509
  Misses      70829   70829
  Partials      463     463

Flag
Coverage Δ

#aFlag
7.17% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/keystone/tokens/handlers.go
0% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

pkg/util/seclib2/seclib.go
95.74% <0%> (+4.25%)
:arrow_up:

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 06ad008...56ddb1f. Read the comment docs.

/lgtm

/approve


The timeoutlen set to 0 disables keymaps which need consecutive typing

Neovim version
NVIM v0.8.1 Build type: Release LuaJIT 2.1.0-beta3 Compiled by<EMAIL_ADDRESS>Features: +acl +iconv +tui See ":help feature-compile"     system vimrc file: "$VIM/sysinit.vim"   fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.8.1/share/nvim"  Run :checkhealth for more info
Operating system/version
macOS 12.6
Terminal name/version
wezterm 20220905-102802-7d4b8249
$TERM environment variable
xterm-256color
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
Upgrade to commit after https://github.com/ayamir/nvimdots/commit/136c6f525301c5f23d1fac8c4468b102500ea8be
Expected behavior
All keymaps should work normally.
Actual behavior
After upgrading to commit after https://github.com/ayamir/nvimdots/commit/136c6f525301c5f23d1fac8c4468b102500ea8be, keymaps start with <leader> or other keys stop working, while keymaps like <C-d>, <A-t>, <A-d> still work.
Additional information
In commit https://github.com/ayamir/nvimdots/commit/136c6f525301c5f23d1fac8c4468b102500ea8be, it seems that the timeoutlen is supposed to be handled by the plugin better_escape, and fallback to the option in core/options.lua. Therefore, it could be the plugin's issue.

After upgrading to commit after https://github.com/ayamir/nvimdots/commit/136c6f525301c5f23d1fac8c4468b102500ea8be, keymaps start with or other keys stop working, while keymaps like , , still work.

Such as what?

After upgrading to commit after 136c6f5, keymaps start with or other keys stop working, while keymaps like , , still work.

Such as what?

<A-t> and <C-d>

keymaps start with <leader> or character like gD

You can pull to the latest config and everything works normally.

BTW, which-key.nvim can handle timeoutlen=0 normally. So please set timeoutlen=300 if you removed which-key.nvim by yourself.

I pulled to the latest config and it works. So I will close this issue


Support JAX arrays as an interface

Feature request: Support JAX arrays as an interface.
For example, currently, using a JAX array as a Parameter.value yields the following error:
TypeError: <class 'jaxlib.xla_extension.ArrayImpl'> is not a valid type for a Constant value.

This error is raised here because JAX arrays are not in the INTERFACES list.

unfortunately it won't be as easy. There are lots of other things that would need to be added to support this.
Why exactly do you want to set a parameter value to a jax array? Is it possible to convert the jax array to numpy then proceed from there?

@Transurgeon Converting the JAX array to a NumPy array also works, and is what I'm doing right now. I was wondering if it might be more efficient to avoid that conversion somehow. For concreteness, I'm using jax.pure_callback to use CVXPY's solver as a subroutine many, many times for large batches of arrays in a large program.

Hey @carlosgmartin I just read a bit about this and found that JAX arrays implement the array interface protocol standardized by NumPy.  See here for more details on interoperability with NumPy. This could mean that inside of cvxpy it would be possible to support any datatype which implement the __array_interface__ and the __array__() method. But like I said before, a lot of the codebase would need to be changed to allow this generality.
Your use-case seems quite interesting! Do you mind sharing a minimal example to us, so we could have a starting point? I am not really familiar with JAX let alone its pure_callback method, so some additional explanations would also be nice, thanks!

@Transurgeon Here's a minimal example:
import cvxpy as cp
import jax
import numpy as np
from jax import numpy as jnp, random
from matplotlib import pyplot as plt

@jax.jit
def solve(A):
    A_param = cp.Parameter(A.shape)
    x = cp.Variable(A.shape[1])

    objective = cp.Maximize(x.sum())
    constraints = [A_param @ x <= 1]
    problem = cp.Problem(objective, constraints)  # type: ignore

    def f(A):
        A_param.value = np.array(A)
        problem.solve(solver="CLARABEL")
        return jnp.array(x.value)

    return jax.pure_callback(
        f, jnp.empty(x.shape), A, vmap_method="sequential"
    )

def main():
    key = random.key(0)
    A = jnp.abs(random.normal(key, [10**3, 100, 2]))
    x = jax.vmap(solve)(A)
    plt.plot(*x.T, ".", ms=1)
    plt.show()

if __name__ == "__main__":
    main()


Receiver selector broken in IE 11

When trying to change Receiver from the front page, on IE 11, on 0.18.0, the dropdown shows, but selecting it does nothing. It works in Chrome.

Looks like this ie11 was last released in 2015? Is there an org-level policy on browser support? @brian-brazil
https://en.wikipedia.org/wiki/Internet_Explorer_11

We've no policy or precedent on this offhand.


⚠ Bofrost.de has degraded performance

In 71ae189, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1993 ms

Resolved: Bofrost.de performance has improved in cb6c1e9 after 10 minutes.


PATCH: fix(tree): allow node.id to be a string

[ ] I have tested my component
[ ] I have updated the documentation or there is no documentation needed

Libraries that use the DS (need to merge first)

[ ] BCF Components
[ ] BIMData Components
[ ] Building maker

Repos that use the DS (and that I need to check after libraries have been merged)

[ ] Viewer
[ ] Platform
[ ] SDK
[ ] Marketplace
[ ] Documentation

:tada: This PR is included in version 2.2.1-beta.4 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


German translation

I translated the strings.xml into German.

Hi, thank you for contribution! I see you translated string only in :app module, could you please translate other strings in features/feature-fonts and features/feature-themes? And then I'll merge your PR with all strings

I added the feature-fonts and feature-themes translations.


Detect sync pool with non-ptr objects

Partially implemented by a ruleguard rule, but we can do better with a manual analysis.


[CWS] only run btfhub sync job on Friday

What does this PR do?
This job currently runs everyday, which is not super useful. What we really need is to ensure the job runs before the agent freeze, and is updated regularly enough. Every fridays is a good frequency for this.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


fix ubiome file model

The DataFile model is only for files intended for return/display.
The only exception for exposing raw user uploads is Data Selfie.
All other DataFile cases are the result of our data process, not
original uploads.

:+1:


[boost-python] Build error

Copy issue body from E:/GitHub/vcpkg/installed/vcpkg/issue_body.md
issue_body.md

Error message:
E:\GitHub\vcpkg\buildtrees\boost-python\src\ost-1.83.0-6ed3e7b75b.clean\include\boost/python/numpy/internal.hpp(29): fatal error C1083: Cannot open include file: 'numpy/arrayobject.h': No such file or directory

What's this.How to solve it?Is there some module I install failed?

Have you installed the numpy component of python locally? Your log show: <include>/C:/Users/ÌÆ¿/AppData/Local/Programs/Python/Python311/Lib/site-packages/numpy/core/include.
Because the numpy component is detected, boost-python will compile the numpy related files.
You can check whether there is such a file numpy/arrayobject.h in directory C:/Users/ÌÆ¿/AppData/Local/Programs/Python/Python311/Lib/site-packages/numpy/core/include.

Yes,I find this file in C:/Users/ÌÆ¿/AppData/Local/Programs/Python/Python311/Lib/site-packages/numpy/core/include.

So,I should uninstall numpy first?

You can modify your User name ÌÆ¿, it may be that vcpkg does not recognize this character and cannot find the file.

If I modify it,most software will couldn't work.

So,I should uninstall numpy first?

Then you can try to uninstall numpy.


Add units

Pull Request Test Coverage Report for Build 757

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 745:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


POST 500 directline.postActivity

My environment is VS2017.
I selected the Bot Framework template ->botBuilderEchoBot

Run the application and Configured the end point in the Bot Emulator.

i sent a message and received this exception POST500directline.postActivity
With the above steps the application is working fine in others system.
Is there any configuration issue with my system?
This is the Code that i am using:
using System.Net;
using System.Net.Http;
using System.Threading.Tasks;
using System.Web.Http;
using Microsoft.Bot.Builder.Dialogs;
using Microsoft.Bot.Connector;
namespace EchoBot
{
[BotAuthentication]
public class MessagesController : ApiController
{
///
/// POST: api/Messages
/// Receive a message from a user and reply to it
///
public async Task Post([FromBody]Activity activity)
{
if (activity.GetActivityType() == ActivityTypes.Message)
{
await Conversation.SendAsync(activity, () => new Dialogs.RootDialog());
}
else
{
HandleSystemMessage(activity);
}
var response = Request.CreateResponse(HttpStatusCode.OK);
return response;
}
    private Activity HandleSystemMessage(Activity message)
    {
        string messageType = message.GetActivityType();
        if (messageType == ActivityTypes.DeleteUserData)
        {
            // Implement user deletion here
            // If we handle user deletion, return a real message
        }
        else if (messageType == ActivityTypes.ConversationUpdate)
        {
            // Handle conversation state changes, like members being added and removed
            // Use Activity.MembersAdded and Activity.MembersRemoved and Activity.Action for info
            // Not available in all channels
        }
        else if (messageType == ActivityTypes.ContactRelationUpdate)
        {
            // Handle add/remove from contact lists
            // Activity.From + Activity.Action represent what happened
        }
        else if (messageType == ActivityTypes.Typing)
        {
            // Handle knowing that the user is typing
        }
        else if (messageType == ActivityTypes.Ping)
        {
        }

        return null;
    }
}

}
This is log message:
"{\r\n  "message": "An error has occurred.",\r\n  "exceptionMessage": "An error occurred while sending the request.",\r\n  "exceptionType": "System.Net.Http.HttpRequestException",\r\n  "stackTrace": "   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Rest.RetryDelegatingHandler.<>c__DisplayClass11_0.<b__1>d.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Rest.RetryDelegatingHandler.d__11.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Microsoft.Bot.Connector.Conversations.d__9.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Connector.ConversationsExtensions.d__9.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.AlwaysSendDirect_BotToUser.d__4.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\ConnectorEx\\BotToUser.cs:line 124\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.InputHintQueue.d__4.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\ConnectorEx\\BotToUser.cs:line 184\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.AutoInputHint_BotToUser.d__3.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\ConnectorEx\\BotToUser.cs:line 146\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.MapToChannelData_BotToUser.d__3.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\ConnectorEx\\BotToUser.cs:line 295\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.LogBotToUser.d__4.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\ConnectorEx\\IActivityLogger.cs:line 131\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.DialogContext.d__12.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Dialogs\\DialogContext.cs:line 87\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Extensions.d__14.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Dialogs\\IDialogContext.cs:line 150\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()\r\n   at EchoBot.Dialogs.RootDialog.d__1.MoveNext() in c:\\users\\jeevan.ganta\\source\\repos\\EchoBot\\EchoBot\\Dialogs\\RootDialog.cs:line 26\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.DialogTask.ThunkResume1.<Rest>d__5.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 164\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Internals.Fibers.Wait2.<Microsoft-Bot-Builder-Internals-Fibers-IWait-PollAsync>d__19.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Fibers\\Wait.cs:line 0\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Internals.Fibers.Frame1.<Microsoft-Bot-Builder-Internals-Fibers-IFrameLoop<C>-PollAsync>d__9.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Fibers\\\\Fiber.cs:line 0\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Internals.Fibers.Fiber1.<Microsoft-Bot-Builder-Internals-Fibers-IFiberLoop-PollAsync>d__16.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Fibers\\Fiber.cs:line 0\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at Microsoft.Bot.Builder.Internals.Fibers.Wait2.Microsoft.Bot.Builder.Internals.Fibers.IAwaiter<T>.GetResult() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Fibers\\\\Wait.cs:line 378\\r\\n   at Microsoft.Bot.Builder.Dialogs.Chain.LoopDialog1.d__3.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Dialogs\\Chain.cs:line 752\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.DialogTask.ThunkResume1.<Rest>d__5.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 164\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Internals.Fibers.Wait2.<Microsoft-Bot-Builder-Internals-Fibers-IWait-PollAsync>d__19.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Fibers\\Wait.cs:line 0\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Internals.Fibers.Frame1.<Microsoft-Bot-Builder-Internals-Fibers-IFrameLoop<C>-PollAsync>d__9.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Fibers\\\\Fiber.cs:line 0\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Internals.Fibers.Fiber1.<Microsoft-Bot-Builder-Internals-Fibers-IFiberLoop-PollAsync>d__16.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Fibers\\Fiber.cs:line 244\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.DialogTask.d__23.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Dialogs\\DialogTask.cs:line 321\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.ReactiveDialogTask.d__3.MoveNext() in D:\\a\\1\\s\\CSharp\\Library\\Microsoft.Bot.Builder\\Dialogs\\DialogTask.cs:line 376\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Bot.Builder.Dialogs.Internals.ScoringEventLoop1.<Microsoft-Bot-Builder-Base-IEventLoop-PollAsync>d__5.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\ScoringEventLoop.cs:line 87\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.EventLoopDialogTask.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 435\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.SetAmbientThreadCulture.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\ConnectorEx\\\\PostToBot.cs:line 103\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.QueueDrainingDialogTask.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__4.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 455\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.PersistentDialogTask.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 481\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.PersistentDialogTask.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 485\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.ExceptionTranslationDialogTask.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__2.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\Dialogs\\\\DialogTask.cs:line 403\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.SerializeByConversation.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__4.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\ConnectorEx\\\\PostToBot.cs:line 129\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.PostUnhandledExceptionToUser.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__5.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\ConnectorEx\\\\PostToBot.cs:line 156\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.PostUnhandledExceptionToUser.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__5.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\ConnectorEx\\\\PostToBot.cs:line 169\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Internals.LogPostToBot.<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder\\\\ConnectorEx\\\\IActivityLogger.cs:line 109\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Conversation.<SendAsync>d__11.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder.Autofac\\\\Dialogs\\\\Conversation.cs:line 182\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at Microsoft.Bot.Builder.Dialogs.Conversation.<SendAsync>d__6.MoveNext() in D:\\\\a\\\\1\\\\s\\\\CSharp\\\\Library\\\\Microsoft.Bot.Builder.Autofac\\\\Dialogs\\\\Conversation.cs:line 108\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()\\r\\n   at EchoBot.MessagesController.<Post>d__0.MoveNext() in c:\\\\users\\\\jeevan.ganta\\\\source\\\\repos\\\\EchoBot\\\\EchoBot\\\\Controllers\\\\MessagesController.cs:line 21\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__31.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()",\r\n  "innerException": {\r\n    "message": "An error has occurred.",\r\n    "exceptionMessage": "The remote name could not be resolved: 'http'",\r\n    "exceptionType": "System.Net.WebException",\r\n    "stackTrace": "   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)\r\n   at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)"\r\n  }\r\n}"
@dandriscoll  @HenrikFrystykNielsen @nwhitmont @EricDahlvang

Closing the issue assuming it as resolved. Please reopen a new issue if it still persists.

having this issue. tried setting ngrok as per documentation https://github.com/microsoft/botframework-emulator/wiki/Tunneling-(ngrok), still getting the same error. In emulator Inspector-JSON I am getting the log message as posted above.

Because your tunnel(ngrok) is disconnect or not configured.
We must config  tunnel(ngrok) when we debug bot local.


change name and location of solutions in marketplace

new Marketplace UI is merged in. won't be using this now


Fall back to summary set in front matter

Hugo's auto-generated page .Summary is often of no use to me so I write my own as a page variable.  This means, however, that I need to change common templates (e.g. RSS feed) to use said variable.
Is there any interest in a patch that would alter .Summary so that if a page variable called summary was available it used that value rather than auto-generating one from the content?

Hey,
Short answer is yes, and I'm a little bit surprised that we did not already do so.
To create the least amount of surprises, I suggest that we check for summary in the following order:

The summary split option.
The summary value in front matter (new)
Auto-summary as the last resort

Okay will take a look at this.


GraphQL is breaking

Running a Gizmo query g.V("<someId>").All() returns about 1150 results. Running the GraphQL query:
{
    nodes(id: "<someId>") {
      http://www.w3.org/1999/02/22-rdf-syntax-ns#type @opt
    }
}

returns a 503 because of a query timeout.
Edit: The Gizmo query returns after about 5 sec.

Fiddled around some more. Without the @opt it works fine, so it seems the problem is there.

Hmmm, my phrasing might have been a bit ambiguous. The main point was that GraphQL seems to take a lot more time than Gizmo to do essentially the same thing, namely retrieve some directly related (optional) thing(s) given a starting point. I should mention that I have about 5 million quads in my Postgres backed Cayley, which is probably part of the reason why it is so slow. Nevertheless, the discrepancy between the two APIs seemed like something you would want to know about.

I understand this, and I think I know why it might take so long for @opt query.
The thing I don't understand is how can it return 1150 results for a query that selects a single node. This is what I'm trying to ask.

Ah, sorry, that was a bad typo on my part. I meant g.V("<someId>").Out().All() indeed (I understand your previous message a lot better as well now).

OK, makes sense now :) Then an equivalent GraphQL query should be something like:
{
    nodes(id: "<someId>") {
      any: * {
        http://www.w3.org/1999/02/22-rdf-syntax-ns#type @opt
      }
    }
}

Although I'm not sure we support this star syntax.
Still not sure how a one-node GraphQL in your first post can timeout. Maybe something is broken in id queries.

@steffansluis I need more information about this one. Can you please send exact queries you run? If you could provide a test data as well it would be ideal.

I assume it's the same as #740.


Cannot use adamw_8bit and paged_adamw_8bit with qlora+fsdp

Reminder

[X] I have read the README and searched the existing issues.

System Info
latest llamafactory version
Reproduction
I'm using the latest llamafactory version to run sft(qlora+fsdp) for llama3.1 70B with 8xA100. It works with default optim, but with 8bit adam, i get the following error:
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/transformers/trainer.py", line 1938, in train
[rank0]:     return inner_training_loop(
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/transformers/trainer.py", line 2341, in _inner_training_loop
[rank0]:     self.optimizer.step()
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/accelerate/optimizer.py", line 172, in step
[rank0]:     self.optimizer.step(closure)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/optim/lr_scheduler.py", line 130, in wrapper
[rank0]:     return func.get(opt, opt.class)(*args, **kwargs)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/optim/optimizer.py", line 484, in wrapper
[rank0]:     out = func(*args, **kwargs)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/bitsandbytes/optim/optimizer.py", line 287, in step
[rank0]:     self.update_step(group, p, gindex, pindex)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/bitsandbytes/optim/optimizer.py", line 546, in update_step
[rank0]:     F.optimizer_update_8bit_blockwise(
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/bitsandbytes/functional.py", line 1774, in optimizer_update_8bit_blockwise
[rank0]:     prev_device = pre_call(g.device)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/bitsandbytes/functional.py", line 463, in pre_call
[rank0]:     torch.cuda.set_device(device)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/cuda/init.py", line 418, in set_device
[rank0]:     device = _get_device_index(device)
[rank0]:   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/cuda/_utils.py", line 34, in _get_device_index
[rank0]:     raise ValueError(f"Expected a cuda device, but got: {device}")
[rank0]: ValueError: Expected a cuda device, but got: cpu
Expected behavior
No response
Others
No response

is it because i use use_unsloth_gc=True?


Features/show fps

The widget is by default placed on the top left corner of the web page. A screenshot:

~75fps looks surprising high (my benchmark was usually 35/60) so I'm not sure if I did it right. I wrap stats.begin() and stats.end() around everything within draw() of the p5 instance.

75fps looks surprising high (my benchmark was usually 35/60) so I'm not sure if I did it right. I wrap stats.begin() and stats.end() around everything within draw() of the p5 instance

That's finding the fps of the draw loop. This is different from the fps of pose recognition. Pose recognition runs asynchronously, updating the global data structure (and sending the new data to the server) whenever BlazePose signals that a new pose is ready. The draw loop runs at a fixed rate (unless some code is taking more than 1/60 seconds, in which case it has to run slower). It will use the same pose for rendering multiple frames, so that the rendering fps could be 60 while the pose recognition fps could be much slower. Also, the fps for image data (from the web cam), pose data from the local user, and pose data from other users, could all be running at different frame rates (although if any of them is faster than the rendering fps, the user won't see that).

I move the usage of stats.js code from sketch.ts to blazePose.js to reflect pose detection frequency:
export async function initializeBlazePose(
  video: HTMLVideoElement
): Promise<void> {

  // omitted content

  async function loop() {
    loopIsRunning = true;
    while (true) {
      // stats begin
      stats.begin();

      // omitted content

      // stats end
      stats.end();
    }
  }
}

The FPS display looks closer to reality now:

Looks great, almost there. I recommend changing sketch.ts back to its original state, instead of the lines that are added and then commented out. You can do this manually, or from the command line via git checkout main -- src/sketch.ts

Done!


uncurried types get leaked

Unfortunately we can not make it an abstract type, I wonder if we can do some adhoc things to avoid expanding types in Js module.
cc @cristianoc

Already done in master.


Rewrite in ES6

This PR cleans up this project into a proper ES6 package
TODO:

[x] Port the source code over
[x] Port the tests over
[x] Verify on Windows
[x] Verify on OS X
[ ] Fix up the README

Thanks for this @paulcbetts, #1 was just merged so conflicts abound :hammer:

@lukeapage So, I kinda rewrote this without reading #1 first, but what do you think about this:

Port back the use of Jetpack like #1, this library looks great
Use debug instead of the custom logging framework, I think it's more standard and lets people turn on/off noisy output

Sounds good to me.  I'd advise against the await keyword since its not yet stage 4 and wont be in es2016..  still better to have an unfinished standard than coffeescript though imo.

@paulcbetts please ping me when this is ready for review :eyes:

@kevinsawicki Will look at this tomorrow

@kevinsawicki I'm gonna finish this today then you can have an :eyeglasses:

@kevinsawicki This should be :gem:

Guys, how're things going here? Do you have plans to review it, @kevinsawicki?
Is it a final version, @paulcbetts?

Published in 2.0.0, thanks for this @paulcbetts


Type Member.Roles returns a string array

Currently the struct Member has a field 'Roles' that returns type []string
I think the return of type []Role would be better here, or is there an API limitation that prevents this?

This is what the API returns. It's a list of role ID's you need to actually grab the roles from
s.State.Guild(guildID).Roles

Thank you!
//offtopic
But that means that the official client has to check for every message the roles in its state. That's looks not very efficient, or it is some ReactJS state magic :-)

They probably put the roles in the equivalent of a map[string]*Role, very efficient to grab a role that way.


Where is the doc for cloud messaging service?

I am wandering here since 2 hours. How can you people be so bad at maintaining a proper doc.
Your link takes me here  https://firebase.google.com/docs/cloud-messaging/server
Another link this https://firebase.google.com/docs/reference/admin/node/admin.messaging
All I want to send notifications from a node server. I am unable find a proper doc.
https://firebase.google.com/docs/reference/admin/node/TopicMessage
Why android is mentioned on this page?

Please spend some time reading and following the content, instead of skimming over it. The page you've linked above has an entire section covering the Admin SDKs:

Firebase Admin SDK for FCM
The Admin FCM API handles authenticating with the backend and facilitates sending messages and managing topic subscriptions....
To set up the Firebase Admin SDK, see Add the Firebase Admin SDK to Your Server. If you already have a Firebase project, start with Add the SDK. Then, once the Firebase Admin SDK is installed, you can start writing logic to build send requests.

Note that there are many different ways to send FCM notifications, and the page you've linked to is the common landing page (getting started page) for FCM. It has links to other pages that go into more details about each different approach for sending notifications.

https://firebase.google.com/docs/reference/admin/node/TopicMessage
Why android is mentioned on this page?

android is a valid property in the FCM notification payload (alongside apns, webpush and others). So it is listed as it should be.


Support automatically Name Loop Variable in IRBuilder (#716)

We can reuse typical names like [i, j, k] before we start using suffix. As for loop pops, we can also pop the name index so it generates
for i:
for j:
for j:


improve: 新建vercel部署教程

I'd like to add a vercel deployment doc. Is is necessary?

Welcome, contributor!
Yes, please, but only if you figured out how to do it since I don't want to bother your time too long. But it should be pretty easy to setup and get it distributed by referencing the documentation from vitepress.dev.
And, please kindly take a look on #13 where we do also need buttons on README.md pages for folks who interested in building their own copy of Nolebase or VitePress with Obsidian. And such need was introduced and requested in #11.
IMO, I think it may not be easy enough and migrated completed for the Nolebase to be a standalone template for everyone to try out on their own, but rather need a long time to allow us to create the replicated modules and plugins in nolebase/integrations.
Would it be possible and easy enough to create a separated page for such tutorial on how to deploy on Vercel, Netlify  (I can work on this), and GitHub Actions (I can work on this)? Or will you perfer to include the section into the README.md and 笔记/index.md?
Please feel free to work on the documentation in either ways, I accept both of the solution I said above.


upgrade default k8s cluster to 1.18

https://aws.amazon.com/about-aws/whats-new/2020/10/amazon-eks-supports-kubernetes-version-1-18/
Use Case

Proposed Solution

Other

[ ] :wave: I may be able to implement this feature request

This is a :rocket: Feature Request

EKS 1.18 and latest 1.17 introduces EFS csidriver in cluster by default, which breaks the deployment of EFS csi driver via Helm chart. The current mainline branch also is broken by this change, we’re pending on a new Helm chart release of EFS csi driver.
See https://github.com/kubernetes-sigs/aws-efs-csi-driver/issues/267 for detail info.


non-deterministic test failures

We ran HTR with the shardrefine branch at the request of @lightsighter. Our regression tests are randomly failing their tolerance checks in debug mode. I don't have much useful info to share at the moment, but @mariodirenzo will be doing some analysis with legion spy to get some clues.
@elliottslaughter, could you please add this to #1032 ?

I've done some additional testing and found that this issue is not specific to shardrefine. It was difficult to identify in our CI because it only seems to fail one test about 1/20th of the time.
This regression was introduced between the 48d22ec and 149be33 commits of control_replication. Are there any commits within those two that would be the most suspicious? We can then revert them and see if the regression disappears, as opposed to iterating through each one.
Thanks

You're saying that 48d22ec works correctly all the time or that is the first commit that you notice that fails?
Unfortunately, most of the changes in that commit range come from Realm so we're probably going to need to binary search, but none of the Realm changes jump out as immediately scary to me. There's actually only three Legion changes in that range: one adding support for initial futures in future map all-reduces (which you don't use), one adding checks that users don't mix color allocation modes for partitions (which would fail deterministically if you hit it), and one improving the Legion shutdown protocol (which won't impact any running code). If you want to check any of those Legion changes, the one to remove is f8d66ead as it's possible that influences a future reduction somewhere.

48d22ec is the first one that fails. I’ll try your suggestion, thanks

Ok, if 48d22ec is the first one that fails we need to go back further to properly bound the set of commits that can be the cause.

48d22ec is a merge commit that merges in several changes from master. Keep going backwards through the commits until you find a commit that is stable, e.g. the next one back is probably 5f8bc7b4.

Mike, 5f8bc7b4 had issues that we fixed together. The code does not even run on that commit.
As written by @cmelone, 149be33, which is the commit just before 5f8bc7b4, works fine. It must be something between 149be33 and 48d22ec and we can't bisect further. We need to start reverting specific sets of commits.

As written by @cmelone, 149be33, which is the commit just before 5f8bc7b4, works fine

I don't think that's accurate. The order of commits from oldest to newest is:
5f8bc7b - August 15th
48d22ec - August 15th
149be33 - August 18th
48d22ec comes between 5f8bc7b and 149be33.  And @cmelone said:

48d22ec is the first one that fails.

But if it is also failing that means it's possible that is not the first one that fails. It's possible that the failure was introduced even earlier.

Mike, 5f8bc7b4 had issues that we fixed together. The code does not even run on that commit.

You may need to cherry-pick in the Realm changes to the machine model parsing to determine if the cause of the non-determinism occurred even earlier than 48d22ec.

Sorry, I misread your comment. I thought you were proposing to bisect at f8d66ea.
Last time I chatted with @cmelone, I understood that   48d22ec works fine and that 149be33 fails

Reverting f8d66ead1 solves the issue...

Reverting f8d66ead1 solves the issue...

That commit comes after 48d22ec, but you said that 48d22ec was failing also...

@lightsighter apologies, I checked again and 48d22ec succeeds.

@cmelone This commit adds support for an initial value for future reductions in index task launches. Are you actually using that functionality? I'd be pretty surprised if this was actually the commit that is the first one that fails as it should all result in a no-op if you're not even using that feature. How many times do you do the runs when checking a commit? Is it always on the same allocation of nodes?

Yes, same allocation of nodes and I was running the same execution 50 times per commit. However, I tried a more recent commit (1efeabc) and I can't reproduce after running >150 times. Something must have changed since fd5f489 (the last commit that failed). If you'd like, I can close this, or I can do some more testing over the weekend to know the root cause of this issue, if we run into it in the future.

I think you should do some more testing to convince yourself that the issue is actually fixed. Certainly bugs were found and fixed in the intermediate time frame, but none that sound like the failure mode that we have here where things were silently getting the wrong answer. It's up to you guys to decide when you want to close the issue, but it's hard to say if we fixed the issue if we never understood the root cause.

I agree with Mike, let's keep this issue around.
I do not think that we should keep doing active testing specifically for this issue but we keep an eye on our CI and see if it starts failing again with the same mode.

I have not seen this reappear in our CI, but I went back and did some additional testing to find out what the root cause might be. It would probably be easier to disregard the earlier commits discussed on this thread for simplicity's sake.
Commit 39a6b0ee26a0a077e0fc37d5e1654ebedaf89815 fails repeatedly, but I have ran our test case 1200 times on commit 039d79a60f65307d0533b595bd21f5e5ccc6c44c and it has only succeeded.
Does this make sense in context of the failure mode? (the simulation giving erroneous output and failing our tolerance checks).

I did fix at least one bug with execution fences in that second commit. I don't see why the first commit would have caused any problems though as it was exclusively about the padded instances (usually their failure mode would be an illegal memory access). It sounds though like you've done some more rigorous testing though now, which at least should improve our confidence that we fixed whatever the error is.

Just to clarify, 39a6b0 isn't where the bug originated, but where it was last observed. So the second commit definitely fixed the bug.
@mariodirenzo, are you satisfied with these findings?


Concurrency implement can't work

Dispatch Lock after check atSubscribe, it's work at signal routine
Lock before it work at concurrency

Problem:
If we call Dispatch in Subscribe, it will cause deadlock(check before atSubscribe check)
But if we check after atSubscribe check, in Concurrency program, we will meet race condition

So I let it meet Deadlock temporary. Make sure it's work for real world, not for test

I will create a new issue to describe the problem accurate.


fix(crosswalk): fix build

Description

fix cherry-pick mistakes of https://github.com/tier4/autoware.universe/commit/eb134333639523cc1c74b23667998fbe5e93e212
build failed in
https://evaluation.tier4.jp/evaluation/reports/39b89374-45b2-5c16-b180-58e9ddfed30f?project_id=prd_jt
/home/autoware/autoware.proj/src/autoware/universe/planning/behavior_velocity_crosswalk_module/src/scene_crosswalk.cpp: In member function ‘tier4_autoware_utils::Polygon2d behavior_velocity_planner::CrosswalkModule::getAttentionArea(const PathWithLaneId&, const std::pair<double, double>&) const’:
/home/autoware/autoware.proj/src/autoware/universe/planning/behavior_velocity_crosswalk_module/src/scene_crosswalk.cpp:750:60: error: ‘p_ego_front’ was not declared in this scope
  750 |     const auto ego_one_step_polygon = createOneStepPolygon(p_ego_front, p_ego_back, ego_polygon);
      |                                                            ^~~~~~~~~~~
/home/autoware/autoware.proj/src/autoware/universe/planning/behavior_velocity_crosswalk_module/src/scene_crosswalk.cpp:750:73: error: ‘p_ego_back’ was not declared in this scope
  750 |     const auto ego_one_step_polygon = createOneStepPolygon(p_ego_front, p_ego_back, ego_polygon);
      |                                                                         ^~~~~~~~~~
gmake[2]: *** [CMakeFiles/behavior_velocity_crosswalk_module.dir/build.make:104: CMakeFiles/behavior_velocity_crosswalk_module.dir/src/scene_crosswalk.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:137: CMakeFiles/behavior_velocity_crosswalk_module.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
---
Failed   <<< behavior_velocity_crosswalk_module [8min 8s, exited with code 2]

Tests performed

build in my local
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

https://evaluation.tier4.jp/evaluation/reports/325d2014-4984-5b60-bbd6-59d8af82591c?project_id=prd_jt


Added correlated request for Moya.Response.

PR addresses issue discussed in #473. It is non-breaking change. Appropriate unit-test added to ensure that request is provided upon receiving a response.

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

          1 Warning

:warning:
Consider adding supporting documentation to this change. Documentation can be found in the docs directory.

SwiftLint found issues
Warnings

File
Line
Reason

Moya+Internal.swift
102
Function should have 5 parameters or less: it currently has 6

  Generated by :no_entry_sign: danger

Current coverage is 67.22% (diff: 88.88%)

Merging #650 into master will increase coverage by 0.15%

@@             master       #650   diff @@
==========================================
  Files            16         16
  Lines           653        653
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            438        439     +1
+ Misses          215        214     -1
  Partials          0          0

Powered by Codecov. Last update 7adb73a...93c4bca

Thanks a lot for contributing to Moya! I've invited you to join the Moya GitHub organization – no pressure to accept! If you'd like more information on what that means, check out our contributor guidelines and feel free to reach out with any questions.


Base64 encoding binary field data before saving to JSON

We store some data in binary fields in Dynamo which can't be backed up as-is to JSON. This small change just base64 encodes binary fields before saving as JSON.

@nathanwelch - can you add an option for this behavior?

@dylanlingelbach Done and added to the command line args and readme. Let me know if you see any issues with it.

@nathanwelch - this looks good. I'll try to get this merged in and released tonight.

@nathanwelch - published as version 0.2.0


KAFKA-7020: Error when deleting topic with access denied exception

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

can anyone look into this PR? This is very important to us. We're running Kafka under Windows.


CI job cpu (ubuntu-18.04, 3.9, oldest, stable) failing with Segmentation fault

🐛 Bug
The CI job cpu (ubuntu-18.04, 3.9, oldest, stable) has been failing quite consistently on recent PRs with a seg fault:
/home/runner/work/_temp/a06dced7-640c-436b-bbb1-c17e205bf64d.sh: line 2:  3542 Segmentation fault      (core dumped) coverage run --source pytorch_lightning -m pytest pytorch_lightning tests -v --durations=50 --junitxml=junit/test-results-Linux-py3.9-oldest-stable.xml
Recent runs:
https://github.com/PyTorchLightning/pytorch-lightning/runs/4597791363?check_suite_focus=true
https://github.com/PyTorchLightning/pytorch-lightning/runs/4598799055?check_suite_focus=true
https://github.com/PyTorchLightning/pytorch-lightning/runs/4599551767?check_suite_focus=true
https://github.com/PyTorchLightning/pytorch-lightning/runs/4589679232?check_suite_focus=true
This job is often the only failing job, making the whole CI red. However this job is not required to merge a PR, so contributors aren't strongly motivated to fix it. As part of https://github.com/PyTorchLightning/pytorch-lightning/issues/9445 I believe we should either mark this test as required or delete it, with a personal preference for deleting it.
cc @carmocca @akihironitta @borda

Duplicate of #11184