Verbose validation error is difficult to understand

Hi, I was validating this Polygon that has a linear rings with different start/end coordinates:
{
    "type": "Feature",
    "geometry": {
        "type": "Polygon",
        "coordinates": [
            [
                [-55.9947406591177, -9.26104045526505],
                [-55.9976752102375, -9.266589696568962],
                [-56.00200328975916, -9.264041751931352],
                [-55.99899921566248, -9.257935213034594],
                [-55.99477406591177, -9.26103945526505],
            ]
        ],
    },
}

And I received the following message:
18 validation errors for Feature
geometry -> type
  unexpected value; permitted: 'Point' (type=value_error.const; given=Polygon; permitted=['Point'])
geometry -> coordinates
  wrong tuple length 1, expected 2 (type=value_error.tuple.length; actual_length=1; expected_length=2)
geometry -> coordinates
  wrong tuple length 1, expected 3 (type=value_error.tuple.length; actual_length=1; expected_length=3)
geometry -> type
  unexpected value; permitted: 'MultiPoint' (type=value_error.const; given=Polygon; permitted=['MultiPoint'])
geometry -> coordinates -> 0
  wrong tuple length 5, expected 2 (type=value_error.tuple.length; actual_length=5; expected_length=2)
geometry -> coordinates -> 0
  wrong tuple length 5, expected 3 (type=value_error.tuple.length; actual_length=5; expected_length=3)
geometry -> type
  unexpected value; permitted: 'LineString' (type=value_error.const; given=Polygon; permitted=['LineString'])
geometry -> coordinates
  ensure this value has at least 2 items (type=value_error.list.min_items; limit_value=2)
geometry -> type
  unexpected value; permitted: 'MultiLineString' (type=value_error.const; given=Polygon; permitted=['MultiLineString'])
geometry -> coordinates
  All linear rings have the same start and end coordinates (type=value_error)
geometry -> type
  unexpected value; permitted: 'MultiPolygon' (type=value_error.const; given=Polygon; permitted=['MultiPolygon'])
geometry -> coordinates -> 0 -> 0
  ensure this value has at least 4 items (type=value_error.list.min_items; limit_value=4)
geometry -> coordinates -> 0 -> 1
  ensure this value has at least 4 items (type=value_error.list.min_items; limit_value=4)
geometry -> coordinates -> 0 -> 2
  ensure this value has at least 4 items (type=value_error.list.min_items; limit_value=4)
geometry -> coordinates -> 0 -> 3
  ensure this value has at least 4 items (type=value_error.list.min_items; limit_value=4)
geometry -> coordinates -> 0 -> 4
  ensure this value has at least 4 items (type=value_error.list.min_items; limit_value=4)
geometry -> type
  unexpected value; permitted: 'GeometryCollection' (type=value_error.const; given=Polygon; permitted=['GeometryCollection'])
geometry -> geometries
  field required (type=value_error.missing)

However this does not happen if Feature is omitted:
{
    "type": "Polygon",
    "coordinates": [
        [
            [-55.9947406591177, -9.26104045526505],
            [-55.9976752102375, -9.266589696568962],
            [-56.00200328975916, -9.264041751931352],
            [-55.99899921566248, -9.257935213034594],
            [-55.99477406591177, -9.26103945526505],
        ]
    ],
}

Result:
1 validation error for Polygon
coordinates
  All linear rings have the same start and end coordinates (type=value_error)

Can you look into that?
Thanks.

@svaccari the first verbose error is because Pydantic will try to check all the geometry types instead of focusing on just the Polygon. Maybe there is something to explore there

Depends on #94 (types as Literals). But this is 90% solved by the following:
from typing_extensions import Annotated
...
Geometry = Annotated[
    Union[Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon],
    Field(discriminator="type"),
]

The error would then just be:
pydantic.error_wrappers.ValidationError: 3 validation errors for Feature
geometry -> Polygon -> coordinates
  All linear rings have the same start and end coordinates (type=value_error)
geometry -> type
  unexpected value; permitted: 'GeometryCollection' (type=value_error.const; given=Polygon; permitted=('GeometryCollection',))
geometry -> geometries
  field required (type=value_error.missing)

I haven't quite figured out getting rid of the GeometryCollection one yet. But at least its significantly improved.

Took a bunch of iterations, but got it:
class Feature(GenericModel, Generic[Geom, Props]):
    ...
    geometry: Annotated[Optional[Geom], Field(discriminator="type")] = None

And then you get
pydantic.error_wrappers.ValidationError: 1 validation error for Feature
geometry -> Union[Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon] -> Polygon -> coordinates
  All linear rings have the same start and end coordinates (type=value_error)


BUILD_LIST_UNPACK opcode is not supported.

BUILD_LIST_UNPACK opcode is not supported.  I don't know if we can support it.  But, it can show up on py3.5 with source code like fn(1, *a, *b) (see https://github.com/numba/numba/pull/3211/commits/b5d3d60d5e57450b124348346aec95f86237e720).  However, it will run fine on 3.6 due to new opcode.

Closing, referred to test works on mainline for upcoming 0.55 release.
from numba import njit
import numpy as np

def check(p):
    # using eval here since Python 2 doesn't even support the syntax
    @njit
    def inner(*args):
        return args
    pyfunc = eval("lambda a: inner(1, *a, *(1, 2), *a)", locals())
    cfunc = njit(pyfunc)
    assert cfunc(p) == pyfunc(p)
# Homogeneous
check((4, 5))
# Heterogeneous
check((4, 5.5))


⚠ ClamAV has degraded performance

In 3837ce7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 63 ms

Resolved: ClamAV performance has improved in 6c215f9.


Time period consolidators have unpredictable consolidation schedules

Expected Behavior

If we create a time period consolidator to create x-minute bars, the x-minute slices start at midnight.
Actual Behavior

If we create a time period consolidator to create x-minute bars, the start time of the first x-minute bar seems random.
Potential Solution

Make the schedule of time period consolidators start at midnight.
Reproducing the Problem

Run
qb = QuantBook()
symbol = qb.AddEquity("SPY").Symbol

consolidator = TradeBarConsolidator(timedelta(minutes=17))
def consolidation_handler(sender: object, consolidated_bar: TradeBar) -> None:
    print(f"Consolidated bar: {consolidated_bar.Time} - {consolidated_bar.EndTime}")
consolidator.DataConsolidated += consolidation_handler

start_time = datetime(2021, 1, 1, 0, 0) - timedelta(minutes=1)
while start_time < datetime(2021, 1, 1, 1, 0):
    start_time += timedelta(minutes=1)
    trade_bar = TradeBar(start_time, symbol, 1, 1, 1, 1, 1, timedelta(minutes=1)) # The datetime is Time, not EndTime
    #print(f'Updating with data {start_time} to {start_time + timedelta(minutes=1)}')
    consolidator.Update(trade_bar)

You get

Consolidated bar: 2020-12-31 23:44:00 - 2021-01-01 00:01:00
Consolidated bar: 2021-01-01 00:01:00 - 2021-01-01 00:18:00
Consolidated bar: 2021-01-01 00:18:00 - 2021-01-01 00:35:00
Consolidated bar: 2021-01-01 00:35:00 - 2021-01-01 00:52:00

In this case, the first consolidated bar spans 17-minutes, but it only consolidated 1 1-minute bar.
Maybe the consolidator constructors should also check if the day can be evenly divided by the time period. For instance if 1440 % minutes != 0, throw an error. This way, members will know if the last consolidated bar in a day will be a smaller size than the rest of the bars the consolidator creates.
System Information

QC Cloud
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

What is the goal of a normal use case? (not QB manufactured)
The TB consolidator is designed to count the minute bars; there are other period based ones who look for specific periods in the data vs the number of bars. The randomness is due to whether there's a bar each minute and when you start the bar.
It would be helpful to know a real-world goal to define the problem better and see if there's an existing solution.
Closing for now till more information, happy to reopen.


Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "mwc-icon" has already been used with this registry

Describe the bug
Exception after building the project with Vite:
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "mwc-icon" has already been used with this registry

Uncompiled version when using the Vite server works fine
To Reproduce
Steps to reproduce the behavior:

Import two components in two different places and import one in the other
Build with Vite
Open your page in the browser
See error

Expected behavior
Custom element doesn't get defined the second time if it already exists. You should add a check if it already exists
Browser Version (please complete the following information):

OS: Windows 11
Browser: All
Version: 0.25.2

Additional context
I think it's related to #1999 but no official fix was pushed. You should put common dependencies in peerDependencies, like he said in this comment: https://github.com/vitejs/vite/issues/1235#issuecomment-745036564

Thanks for the issue. I will discuss with the team during triage on using peerDependencies. In the meantime please try the workaround in https://github.com/material-components/material-web/issues/1999#issuecomment-744718091 regarding bundling everything into one module.
In the long term, we will likely forego the one-component-per-package publishing structure, and instead publish the entirety of MWC in one node package.

Discussed in triage. As mentioned above, we will be merging all the packages in the future and hence will not be tinkering with the peer dependency structure for now. Please continue to use the workaround above until then.


Don't set wiretap if a LoggingHandler exists

Description
Updates NettyAsyncHttpClientBuilder to ignore the wiretap configuration if a Netty LoggingHandler has already been set. wiretap(boolean) that we use sets a very basic LoggingHandler that doesn't have much nuance to it, so blindly setting this does a disservice to anyone who has passed an existing Reactor Netty HttpClient with a configured logger.
This also marks the wiretap API as deprecated with a recommendation to use the Reactor Netty HttpClient builder with a logger configured.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure:azure-core-http-netty


fix: background shadow breaks for fixed columns

Related Issue
#480
Description
The overflowX property being updated to visible does fix the leftIcons visibility issue, but the background shadows vanish for the fixed columns. Updating the value to clip resolves both the issues.
Related PRs
List related PRs against other branches:

branch
PR

master
#498

Impacted Areas in Application
List general components of the application that this PR will affect:
* MaterialTable

Can you show a before and after png pls? So I can verify?

Sorry about that. Should have added it in the first place.
When i modified the overflowX to visible, this is how the table looked with the fixed column. The id column is marked as fixed in this case

Changing it to clip, restores the background shadow as before the fix.

Please let me know if I need to provide any more info on this. :)

No this looks perfect. I'll merge it today and release it subsequently. Thank you for this.


OverlayFlag.clickThrough not working on Android 12

this issue is likely related to this.
https://developer.android.com/about/versions/12/behavior-changes-all#untrusted-touch-events
could you please expose the transparency value of the system alert window.
then we could adapt opacity to make clickthrough overlay work on Android 12 devices

OverlayFlag.clickThrough is working on android 12 the fix is pushed fix clickThrough overlays for Android12 but I didn't publish a new release since then but
you can use it like that
  flutter_overlay_window:
    git:
      url: git@github.com:X-SLAYER/flutter_overlay_window.git

@X-SLAYER thank you very much. i will try that

use it with HTTPS instead of ssh
  flutter_overlay_window:
    git:
      url: https://github.com/X-SLAYER/flutter_overlay_window.git

thank you it works now on my Android 12 test devices.
Only on my OnePlus 7 Pro with Android 11 sometimes the screen input gets blocked randomly after wakung up the device.
the window overlay notification is then in state
"Overlay is activated"
"tap to edit settings or disable"
this is strange because i chose to set another notification title

no that notification it displayed from the android it self some android show an alerts when there is an overlay window

the issue continue to exist on Android 11.  there i have to restart the device because it is not responsive anymore

after more testing i found out that it still blocks touch in some szenarios also on android 12. for example when you open the google play store and press the "install" button on a random app. you will see that the google play app cannot receive touch events

having the same issue with google play store. is there a fix for this?

some apps block the click-through like play store for the moment it can't be done only if you made an accessibility service and put the layout manager into it so it's beyond this package for the moment


docs: modify the size of the architecture diagram

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.296%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
469

Relevant Lines:
515

💛  - Coveralls


.NET Core compatibility

@jbubriski Hi John, I was able to create a .NET Core compatible version of Encryptamajig, and i was wondering if you wanted me to make a pull request or just maintain it on my own. https://github.com/lorddev/utilities


[4.2] Several fixes for de/re/-mangling of generic typealiases

Introduce several fixes for mangling and remangling of generic typealiases:

Mangle the generic arguments of a typealias type directly, rather than (incorrectly) mangling the generic arguments of the underlying nominal type, and also account for nested generic typealiases.
Remangle generic typealiases the same way we remangle generic nominal types
Aside: fix remangling of protocol references (we were missing substitutions)
Type reconstruction: guard against demangling the wrong # of generic arguments. This is a hack to avoid crashing; a more complete fix requires deeper changes to the type reconstruction logic.

Fixes rdar://problem/41444286

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 632f62b5c12a4279779fd320b7335f5c2011ce0b

Ugh, forgot to add my local fixes.

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test

@swift-ci please test source compatibility

I'm abandoning this; there are too many issues with generic type alias mangling to fix on the 4.2 branch at this time. I'll push a separate PR to disable these manglings, and pursue complete fixes only on master.


Keep scheme sorting info in rsync

Issue :
Xcode schemes were not sorted as expected
Cause :
Scheme sorting hint file was included under xcuserdata dir and was not being rsycn due to existing --exaclude pattern.
Change :
Make the existing exclude a little bit more specific.

@yongjincho92 This still seems like a good idea.


[CI] create docker base builder

Motivation
Docker layer caching is not consistent in nightly builds. Create a base builder to improve caching.
Have you read the Contributing Guidelines on pull requests
Yes
Test Plan
Canary result (based off of cba3730, where Docker build step is added to the commit workflow):

https://app.circleci.com/jobs/github/libra/libra/9375
All four docker images completed in ~1 hr, compared 3+ hrs previously.
The subsequent 3 docker images all took advantage of DLC

Canary result is in:

https://app.circleci.com/jobs/github/libra/libra/9375
All four docker images completed in ~1 hr, compared 3+ hrs previously.
The subsequent 3 docker images all took advantage of DLC

This makes a ton of sense, thanks!
Thanks for the script cleanup as well. Have we thought of opening an issue for running shellcheck on docker/*/*.sh in CI ?

Sounds good. Filed in #1248

@bors-libra r=huitseeker

:pushpin: Commit 556f344 has been approved by huitseeker

:hourglass: Testing commit 556f3447a0efc2a3389a3dcd641fde122a0dfa1d with merge bc2aafdb50a81d5b50c96e084597c57374536d7c...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: huitseeker
Pushing bc2aafdb50a81d5b50c96e084597c57374536d7c to master...


Bugfix/memory leak

This PR comprises a bit more than expected.
I was investigating a memory leak taking place in the sparse solver.
I ended up adding callabacks for solvers and mappings, because it was useful to debug memory usage at each BCD iteration.
I also added tests for callbacks, and an example illustrating this very specific usecase for callbacks.
Finally, I did a pass on brain alignment examples for volumes, modifying some figures and reducing the size of handled data to make them run faster.

Thanks, merging!


optimize rule checks - break out of loop once match is found

Is your feature request related to a problem? Please describe.
Posting from internal discussion:
Looking at this code it appears to evaluate matches:

for each rule
for each condition in the rule
for each span in the trace

and at the end it checks that the number of matches == the number of conditions
So conditions are evaluated independently across all spans in the trace, and then ANDed together.
Rules are ORed in that the first rule for which all conditions are matched will be the rule that is evaluated.
This could be optimized - instead of checking against every span, even after a match is made, break out if a match has been found.
Describe the solution you'd like
add this below the span: label on line 71.
if matched == len(rule.Condition) {
    break
}

Additional context
This code adjustment cannot be added as-is, so using this issue as a placeholder to work on it. (Error: label span declared but not used.)

This issue was already addressed in #532. Closing this issue.


Add partial draw support

It should be possible to get hold of an iterator to only generate pixels for part of the screen, as well as the top left and bottom right coordinates of that bounding box. Primitives like lines that don't update their entire bounding box should probably just return their default iterator which gives the same behaviour. The method to get the bounding box should still return the correct values though.
Cc https://github.com/yuri91/ili9341-rs/issues/3#issuecomment-488856622

Closing in favour of #92.


Update BUG report template

Made Bug report template better and efficient
Made it more aligned with GitHub Community Guidelines

I will revisit the templates at a later time, for now I will keep them as is, thank you.


UTM and VMs display issue

Describe the issue
I have UTM VSs display issue. Attached the picture. Is it possible to fix this somehow?
Configuration

UTM Version: 2.0.28
OS Version: 11.3.1
Intel or Apple Silicon?  M1

There is no picture attached. Please upload your screenshot and include the details on your VM configuration as well.

Sorry, forgot to attach picture, my bad :( Fixed this. As for VM configuration - how will this help to solve UTM VM display issue? Some more notes regarding this issue. When I initially created VM - it seems that this entry was displayed correctly. But later, when I closed and reopened UTM - I've such VM display issue :(

Oh I get it now. You’re talking about the layout problem with the sidebar. That’s a known macOS issue: #2335
Duplicate of #2335


Add option to suppress logging of deletion

Though file deletion is strictly associated with data loss and should be logged in production, it is pretty polluting in tests, so the option to suppress it should be added.

Fixed


maven plugin connector error

while loading the project to eclipse and running got error for plugin.please find error screenshot below.
please help how to fix

Hi @satish1729-hash
I understand that you have problems using the software, but please dont write in so many old (and closed) issues and mention everyone. Please keep in mind this is an open source project, which is not actively maintained anymore (since we dont have any rtc available to test as we migrated couple years ago). So all response are in our spare free time :)
My notifications:

If you have some spare time have a look how other open source projects use this code of conduct.
https://www.contributor-covenant.org/version/2/0/code_of_conduct/
For your problem: Which eclipse do you use?  On which os are you? When you continue to suffer problems, you could try to use the rtc2git docker image.

Appreciated your response.i am using eclipse version 2020-09 (4.17.0)

I cannot reproduce this problem with latest eclipse (2020-09 4.17.0).

Did you activated the target platform and followed the step by step?
My target platform for reference (in case you use eclipse classic you need to install eclipse plugin development tools, also described here in the wiki):

Thanks alot for your response.
Yes followed all the steps,may be I will try to setup again,not sure
whether not able to get the respective plugin..
One more help, can you please clarify about source_workspace and
targer_workspace set up.if you can provide details with some example and
screenshot if helps alot.
On Fri, Nov 13, 2020, 6:41 PM Manuel<EMAIL_ADDRESS>wrote:

I cannot reproduce this problem with latest eclipse (2020-09 4.17.0).
[image: grafik]
https://user-images.githubusercontent.com/7139697/99063318-9fc0a980-25a4-11eb-8c26-e7e8ce4bf9c6.png
Did you activated the target platform and followed the step by step
https://github.com/rtcTo/rtc2gitcli/#setup-eclipse-development-environment
?
My target platform for reference (in case you use eclipse classic you need
to install eclipse plugin development tools, also described here in the
wiki https://github.com/rtcTo/rtc2gitcli/wiki/configure-target-platform
):
[image: grafik]
https://user-images.githubusercontent.com/7139697/99063531-ee6e4380-25a4-11eb-82e3-791e5bd12392.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rtcTo/rtc2gitcli/issues/71#issuecomment-726690874,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLJ2K2SBSU5HGBKRII4YFDSPUEL7ANCNFSM4TQJLUGA
.

Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-dependency-plugin:2.1:copy-dependencies (execution: copy-dependencies, phase: process-sources)
Error while downloading 'http://maven.apache.org/xsd/maven-4.0.0.xsd'
i am getting this error, could you please clarify whether any connector directly download and place in plugin path?

Error while downloading 'http://maven.apache.org/xsd/maven-4.0.0.xsd'

Are you behind a proxy? I have no problems downloading this xsd.

One more help, can you please clarify about source_workspace and
targer_workspace set up.if you can provide details with some example and
screenshot if helps alot.

As others already pointed out, in this wiki entry you see how source_workspace and target_workspace is set up with an example.

Thanks alot spending time for me..
Yes I saw the workspace setup wiki page.
Few queries,

In source_workspace setup ,I will mention the components which I want to
migrate,what should be the flow_target for source_workspace ,we can leave
the default one which is appearing ?
In target_workspace it is mentioned that
all the components from stream but with initial base line?how set that base
line for component ,could you please clarify?

3.How source_workspace and target_workspace works ?I mean generally
workspace means it will get the entire stream data based on component
selection.when we give flow target of targer_workspace as source _workspace
will it capture the history change commits from source_workspace ?
On Fri, Nov 13, 2020, 7:10 PM Manuel<EMAIL_ADDRESS>wrote:

Error while downloading 'http://maven.apache.org/xsd/maven-4.0.0.xsd'
Are you behind a proxy? I have no problems downloading this xsd.
One more help, can you please clarify about source_workspace and
targer_workspace set up.if you can provide details with some example and
screenshot if helps alot.
As others already pointed out, in this wiki entry
https://github.com/rtcTo/rtc2gitcli/wiki/Home-of-rtc2gitcli#setup-the-workspaces
you see how source_workspace and target_workspace is set up with an example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rtcTo/rtc2gitcli/issues/71#issuecomment-726704906,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLJ2K7W56EOM52R65ROZETSPUHZ3ANCNFSM4TQJLUGA
.

One more clarification, could you please provide screenshot in which folder
this xsd file should present ?I will try to download the file and place
whether it works
On Fri, Nov 13, 2020, 7:17 PM Jagatha Satish<EMAIL_ADDRESS>wrote:

Thanks alot spending time for me..
Yes I saw the workspace setup wiki page.
Few queries,

In source_workspace setup ,I will mention the components which I want
to migrate,what should be the flow_target for source_workspace ,we can
leave the default one which is appearing ?
In target_workspace it is mentioned that
all the components from stream but with initial base line?how set that
base line for component ,could you please clarify?

3.How source_workspace and target_workspace works ?I mean generally
workspace means it will get the entire stream data based on component
selection.when we give flow target of targer_workspace as source _workspace
will it capture the history change commits from source_workspace ?
On Fri, Nov 13, 2020, 7:10 PM Manuel<EMAIL_ADDRESS>wrote:

Error while downloading 'http://maven.apache.org/xsd/maven-4.0.0.xsd'
Are you behind a proxy? I have no problems downloading this xsd.
One more help, can you please clarify about source_workspace and
targer_workspace set up.if you can provide details with some example and
screenshot if helps alot.
As others already pointed out, in this wiki entry
https://github.com/rtcTo/rtc2gitcli/wiki/Home-of-rtc2gitcli#setup-the-workspaces
you see how source_workspace and target_workspace is set up with an example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rtcTo/rtc2gitcli/issues/71#issuecomment-726704906,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLJ2K7W56EOM52R65ROZETSPUHZ3ANCNFSM4TQJLUGA
.

The xsd allone wont help. I honestly dont know how to install them manually.
I ziped my just downloaded eclipse and uploaded it (will delete it in a few days), this might work (as it contains the installed m2 connector).
https://drive.google.com/file/d/1mUIPvDKiRH_VisoA4EzmEWklMXr1A-xz/view
If it doesnt work just try to setup your eclipse in a proxy-free network/place.

Thanks alot for your help..I will download and check this first.
Could you please clarify on my queries related to workspaces also which are
mentioned din earlier comments.
How to set initial baseline for components in target_workspace I am not
clear .Please share me screenshots if possible.
On Fri, Nov 13, 2020, 8:40 PM Manuel<EMAIL_ADDRESS>wrote:

The xsd allone wont help. I honestly dont know how to install them
manually.
I ziped my just downloaded eclipse and uploaded it (will delete it in a
few days), this might work (as it contains the installed m2 connector).
https://drive.google.com/file/d/1mUIPvDKiRH_VisoA4EzmEWklMXr1A-xz/view
If it doesnt work just try to setup your eclipse in a proxy-free
network/place.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rtcTo/rtc2gitcli/issues/71#issuecomment-726742748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLJ2K5SCI6VA6SVSOMVEY3SPUSLLANCNFSM4TQJLUGA
.

In source_workspace setup ,I will mention the components which I want to migrate,what should be the flow_target for source_workspace ,we can leave the default one which is appearing ?

Flow target should be the stream you want to migrate. If you create the story from a stream thats the default one which is appearing yes.

In target_workspace it is mentioned that all the components from stream but with initial base line?how set that base line for component ,could you please clarify?

There is a wiki entry in rtc2git, see here https://github.com/rtcTo/rtc2git/wiki/Resetting-your-workspace-to-an-older-state

3.How source_workspace and target_workspace works ?I mean generally workspace means it will get the entire stream data based on component selection.when we give flow target of targer_workspace as source _workspace will it capture the history change commits from source_workspace ?

Generally how rtc works (as far as I remember):
Usually RTC Workspaces capture the state of the flow target (usually a stream). When changes are getting published to the flow target(eg stream), you see them in your workspace as incoming changes.
To your question:
Target_workspace (resetted to an old state/code -> initial baseline) has the source_workspace as flow_target. Source workspace has the to be migrating stream as flowtarget. So far you have 1 workspace (target_workspace) with the most oldest codebase and 1 workspace (source_workspace) with the most recent codebase.
This means target_workspace have all changesets (as incoming changes) which source_workspace already have accepted.
So when you accept changeset after changeset in target_workspace you can redo the history. And on each step, we do the same change with git. Thats the idea.

Need your help for one more item,In commit history complete commit message not present in git history .
I tried to modify parameter(commit.message.format) in migration.properties file but could not able to get exact commit message .Could you please provide details how to keep commit message.format value to get complete RTC history commit message to git commit comment .
Example:
RTC history commit message:
123:Test message- change on 20200101
Git history commit message :
123 change on 20200101
So message is trimmed and displayed in git comment .in above example Test message is missing ,content between : and - symbol


X position checking not working

I am making an ai.
The desired result is that when I die in gd, the program saves that place and when I get to a bit before that place, say "yes", but the print('yes') does not run, nor does anything else I put in the if statement.
My code is:
import math
import time
import gd
import jump

Math = math
player = gd.memory.get_memory()
listp = []

while 1:
    if player.is_dead():
        listp.append(Math.floor(player.x_pos))
    try:
        if Math.floor(player.x_pos) + 4 in listp:
            print('yes')
    except:
        pass

I've basically the same issue.
It says "Unresolved attribute reference 'is_dead' for class 'MemoryType'".
My code:
import gd

client = gd.Client()
memory = gd.memory.get_memory()

while 1:
    if memory.is_dead():
        print('dead')


Update the Injection Module

Sponsorship

If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to sponsor the effot via GitHub Sponsors:

[ ] None, please continute to work for me for free :P
[ ] Absolutely, I get value out of this!
[ ] Maybe later
[x] I'm already a sponsor... Woot!

Is your feature request related to a problem?
Keep the module updated.
Describe the solution you'd like
Update all of the dependencies and make it build in the updated build scripts.
Describe alternatives you've considered
N/A
Additional context
N/A

Draft PR pending.


_

I'm assuming this was resolved based on the change in title? Going to close for now, but feel free to reopen if there's something we can take a look at.


Sort data rows before rendering a graph

As described here https://github.com/datahq/datahub-qa/issues/124 if rows are unordered, the graph is not correctly rendered. We want to add small sorting logic prior to rendering that wouldn't have an impact on performance (e.g., we can sort rows only if the length is less than 1000).
Acceptance criteria

[x] the graph here is rendered correctly

[x] https://datahub.io/core/population-global-historical
[x] https://datahub.io/core/household-income-us-historical

Tasks

[x] refactor datapackage-render-js library so in simpleToPlotly function we do sorting
[x] re-build frontend-showcase-js
[x] deploy changes

FIXED see https://datahub.io/core/population-global-historical and https://datahub.io/core/household-income-us-historical


Docker compose file to run dapr sidecar and asp.net core web api

Hi , can someone please help me out get up and run dapr sidecar and asp.net core web API application, please suggest any change need to do in my docker compose file.                                                                              version: '3.4'
services:
deviceapi:
image: ${DOCKER_REGISTRY-}deviceapi
build:
context: .
dockerfile: Dockerfile
ports:
- "3000:80"
depends_on:
- db
networks:
- my-dapr-network
db:
image: "mcr.microsoft.com/mssql/server"
environment:
SA_PASSWORD: "Cr0wc0n@123"
ACCEPT_EULA: "Y"
networks:
- my-dapr-network
deviceapp-dapr:
image: "daprio/daprd:edge"
command: ["./daprd",
"-app-id", "deviceservice",
"-app-port", "5000",
"-placement-host-address", "placement:50006",
"-dapr-grpc-port", "50001",
"-components-path", "/components"]
volumes:
- "./components/:/components"
depends_on:
- deviceapi
network_mode: "service:deviceapi"
placement:
image: "daprio/dapr"
command: ["./placement", "-port", "50006"]
ports:
- "50006:50006"
networks:
- my-dapr-network
redis:
image: "redis:alpine"
ports:
- "6381:6379"
networks:
- my-dapr-network
networks:
my-dapr-network:

Not relevant


update the default cors configs

match the changes from in #3206 and #3199
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

We're not still using Hudson at all since the move to Travis, are we? Can this file just be removed?

These are in use but for local envs i.e. smoke testing the API locally using docker-compose etc. See point 6 in https://github.com/zooniverse/Panoptes#usage.
Noting this will most likely change for k8 deployment.


yarn to npm

Codecov Report
Base: 38.25% // Head: 38.25% // No change to project coverage :thumbsup:

Coverage data is based on head (f6b181c) compared to base (99379d2).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage   38.25%   38.25%
=======================================
  Files          55       55
  Lines        1226     1226
  Branches      218      218
=======================================
  Hits          469      469
  Misses        738      738
  Partials       19       19

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Expand CSS hint functionality

Thanks for an awesome plugin. Just made a donation for you, the first of many I think.
I got hinting to work correctly. But I would like to see expanded CSS functionality like this Sublime Text example, in which after a CSS colon, I get a list of relevant options relating to the CSS property I have on the left:

In CodeMirror, I get a list that is not relevant:

Is there a way developed to do this I am not aware of, or could it be added?
Thanks and good luck with the fundraiser.

Is there a way developed to do this I am not aware of, or could it be added?

The CSS hinter isn't aware of which values are valid with which properties, but it would be able to extend it to do something like that. The only downside is that it'd require a pretty big additional dataset, possibly even with information about the syntax of composite properties (like border or box-shadow) so that it could hint sensibly inside of those.
I don't have plans to work on this though, and we don't keep feature request issues open unless such plans exist, so I'm closing the issue.


Update auth handling

Applies changes from https://github.com/googleapis/gax-php/pull/111 after merge of http transport PR.
Mild refactoring to add AuthWrapper class

cc @pongad

I'm a little confused. Isn't this something we should implement in google/auth?
I believe the idea is, since scope is the same per client, each client reuses a token in memory w/o calling a cache pool, which should save us a little bit of performance.
If this is the case, we could look at a flag for keeping the token in memory in the auth class. The only time this would cause an issue is if the same auth class was used for two different API calls (w/ different scopes), which I doubt is a common use case.

I am not opposed to pushing logic like this into the auth library when appropriate.
The main change here is to make use of the getLastReceivedToken() method in FetchAuthTokenInterface, which right now we don't use at all. If we would rather push that logic into the auth lib, then it would be sufficient to add a new method like getOrFetchAuthToken() that uses getLastReceivedToken() if it is available and valid, and otherwise uses fetchAuthToken().


[🔨common]: create an example page with two playgrounds (uiproots)

I want to see how two customized UIPRoots look and work on the same page.
The user can use the playground on the page more than once.

:tada: This issue has been resolved in version 1.0.0-beta.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bounding box regression done twice?

I was wondering if there is a reason why both the rpn and classifier parts of the model have bounding box regression layers (instead of just in the rpn part). These regression layers also seem to be very different - in the rpn, it generates a regression for every anchor proposal; and in the classifier, it generates class specific regressions.
I haven't been able to find the later regression described in the paper. My best guess here is that it is an add-on for introducing a class biased regression correction.

I haven't been able to find the later regression described in the paper. My best guess here is that it is an add-on for introducing a class biased regression correction.

I think this is correct. It can not be done at the rpn phase because the classification is reduced to object and non-object. The doubled regression says imo that its redefinement is kind of limited. There are papers (e.g. DeepManta) that use even more of these refinement steps and claim that this is good for performance.

Kool, thanks for the tip.
Looking back in the series of papers I eventually found it in the Fast R-CNN paper.


CTRL-SHIFT-F doesn't work; takes me to a completely different application minimized in my tray.

VS Code Version: 1.54.3
OS Version: Windows_NT x64 10.0.19042

Steps to Reproduce:

Open any code folder and type CTRL-SHIFT-F
Doing so takes me to a completely different application minimized in my tray.

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

The other application is probably intercepting the hotkey before VS Code can handle it.

You probably need to fix this in configuration for the OS or the other application


Consider supporting Bidirectional Ping (FKA Echo Protocol)

We need to re-open this PR, clean it up, and then once it gets approved consider supporting the ECHO protocol.
One thing that's ambiguous here is that the Echo protocol is typically something handled by a Connector, which doesn't currently exist in Quilt.
Thus, it's possible that once the ping protocol is finalized, this ticket should be closed and implemented in the Connectors (as opposed to Quilt, which implements sender/receiver logic, as well as lower-level ILPv4 functionality).

Won't fix for now. Will re-open if someone requests this feature in Java.


Improve documentation related to physics collision shapes

Document using convex decomposition in the editor.
Mention that "trimesh" is synonymous with a concave collision shape.
Mention how to create "holes" in a HeightMapShape3D (see https://github.com/godotengine/godot-proposals/issues/2746).
Add performance hints for each collision shape.

This PR will need a separate backport to 3.x.

Thanks!


WIP: Added base for Top 8 Widget

Added some code to prepare for a future Top 8 Widget for Double Elimination tournaments with UI to draw the bracket in a simple manner (Similar to what is described in https://github.com/joaorb64/TournamentStreamHelper/issues/70)

The idea here would be to not necessarily duplicate the player data on the UI to make it as compact as possible, but still be able to report winners and advance a bracket

TODO:

[x] Add match structure for first round
[x] Add bracket structure
[ ] Add selectable win/loss, score reporting
[ ] Export bracket state
[ ] Export Top 8 final results
[ ] Sync selected match with main scoreboard
[ ] Add Top 8 overlay

Gonna rework that in the upcoming weeks


Add mkSimpleFlake?

In https://github.com/srid/haskell-template I'm using flake-parts in place of flake-utils. The minimal code I came up with in order to replace the latter's eachDefaultSystem is as follows:
  outputs = { self, nixpkgs, flake-parts, ... }:
    flake-parts.lib.mkFlake { inherit self; } {
      systems = nixpkgs.lib.systems.flakeExposed;
      perSystem = { self', inputs', pkgs, system, ... }:
        ..

https://github.com/srid/haskell-template/blob/3fc6858830ecee3d2fe1dfe9a8bfa2047cf561ac/flake.nix#L14-L19
Since I imagine most non-monorepos using flake-parts to repeat the above verbatim, would it be worthwhile to expose a function that obviates both systems and perSystem? i.e.
  outputs = { self, flake-parts, ... }:
    flake-parts.lib.mkSimpleFlake { inherit self; } ({ self', inputs', pkgs, system, ... }:
      ...
    );

ie., mkSimpleFlake is like mkFlake but uses all systems built by Hydra, as well as assumes the user specifies a single-module flake.

In your example, you could still import at the perSystem level, but for consistency, reusable ones should be written for the "top level", as that is the more powerful one. Mixing the two will create confusion errors and a mkSimpleFlake that doesn't support those imports would make the solution unnecessarily hard. This would include adding templates, or a nixosConfigurations.example.
A default value for systems might be a good idea. I hope that the need for this option will go away with a flake format redesign.
It gets you halfway there without adding to the learning curve.

  outputs = { self, nixpkgs, flake-parts, ... }:
    flake-parts.lib.mkFlake { inherit self; } {
      perSystem = { self', inputs', pkgs, system, ... }:
        ..

A default value for systems might be a good idea [..] It gets you halfway there without adding to the learning curve.

Agreed, I think that's a good idea. 👍🏿

Interesting project btw. It would be interesting to turn the template into a reusable module. That way you could achieve a new level of user-friendliness, if you capture the most common haskellPackages configuration and "tricks" in options.

And unlike with a template, existing users will benefit from improvements.

Interesting project btw. It would be interesting to turn the template into a reusable module. That way you could achieve a new level of user-friendliness, if you capture the most common haskellPackages configuration and "tricks" in options.

Done! https://github.com/srid/haskell-flake
Perhaps worth creating a page listing all the flake-parts modules in existence. A module registry of some sorts.

Made a start with that in start/index.html earlier. Don't ask me why I wrote that in raw html :joy:; #31

This can be resolved by Nix not requiring the enumeration of supported systems

https://github.com/NixOS/nix/issues/7709

Alternatively, or in addition, a nixpkgs flake module could set a default value. nixpkgs does not have a flakeModule yet.


Main Server Error: No router instance found.

Describe the bug
Main server crashes when main token doesn't exist(?)
To Reproduce
Unclear, maybe remove access token
Expected behavior
Doesn't crash
Logs
Main token does not exist
/node_modules/next/dist/client/router.js:117
        throw new Error(message);
              ^

Error: No router instance found.
You should only use "next/router" on the client side of your app.

    at getRouter (/node_modules/next/dist/client/router.js:117:15)
    at Object.singletonRouter.<computed> [as push] (/node_modules/next/dist/client/router.js:94:24)
    at Object.callback (/.next/server/chunks/551.js:42:29)
    at Timeout._onTimeout (/node_modules/node-async-locks/lib/async-lock.js:95:15)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)

Seems to happen every time you try to play next episode in a show (probably because after that the token is expired or something like that)

Happens everytime you go directly to a Movie/Episode directly via the URL


Merge event json mapping functions into one shared function

Is your feature request related to a problem? Please describe.
Refactoring task.
There are two functions: createEventsEndpoints.ts and loadEvents in DatabaseConnector.ts (native). Merge these two functions into on function to remove code duplication.

Why is this just limited to the events and not also all other mappings of data we save offline?
Also, please check if this is possible or whether there are problems because the mappings/jsons are different. If they are different, it might still be possible to merge those but invalidating the cache would be necessary.

Adjusted description to steffens comment


Change Numero VAT to CPF (VAT not used in Brasil)

Just changed Numero VAT to CPF

Hi @leogold,
Thanks for your contribution.
We cannot merge your request due to conflict with the master branch. Sorry for this inconvenience.
I have pulled manually from your commit into this csv file . Everything related to "VAT number", if there is any further translated strings, please let me know.
Regards,
Sam


Migrate weekly updates to supabase

need to test
we don't need to backfill the old weekly updates. do we?
Resolves MAN-1408

wait what am I talking about. I should just merge it and see if it breaks


Add more tabular datasets

Add datasets such as ANNThyroid, HTRU2, Arrythmia...
Design :

a downloading mechanism via DataDeps/Artifacts,
data transformation to the common format.

Added via https://github.com/aicenter/GenerativeAD.jl/pull/25


remove fapi2 from list of header files going to generate_pyecmd.py

Signed-off-by: Matt K. Light<EMAIL_ADDRESS>

@fenkes-ibm how does this look?


Introduce footer for PWA

skip footer for first version because of style problems with WSK (fixed position on bottom etc.)


enh: add pre-build hook

Currently, images can be build directly from a Dockerfile and pushed to a registry.
Would be nice if something can be started before the kontena app build does the docker building
Use case:

have a dockerfile BUILD that has various extras needed to do the build, making it quite bloated
have a dockerfile RUN that is much smaller and picks up the results from runnnig BUILD (eg via a COPY).

Currently using make to manage this build. Happy just to have some pre-build hook to invoke this makefile.

Yes this would be handy. For example having a node.js app that produces some javascript and html files. With this I could just run some npm commands before docker build instead of running those steps in Dockerfile or manually.


Fix tooltip arrow positioning

Two arrow positioning fixes on small screen:

when position = bottom / top & arrow right

when position = bottom / top & arrow = center the position is not really center:

:tada: I'll work on getting this merged and released tomorrow if nobody has any objections.


Quickstart updates

Some smoothing/readability enhancements on Quickstart

Thanks :+1: Just not sure about why setting --executable_cache_path=/tmp/ipu-ef-cache? I believe compiled functions are already cached without it?

Thanks 👍 Just not sure about why setting --executable_cache_path=/tmp/ipu-ef-cache? I believe compiled functions are already cached by JAX without it?

The IPU hashing means fewer recompiles -- will revert this when we upgrade to the latest JAX compilation cache.


bttv android not installing

Hello I tried installing Bttv Android app and it installing then it cuts to not installed and i have tried to redownlod like 30 times what to do?

i fixed it.


FormatException: Input string was not in a correct format in Unity 2018.3.0f2

" FormatException: Input string was not in a correct format.
System.Globalization.TimeSpanFormat.Format (System.TimeSpan value, System.String format, System.IFormatProvider formatProvider) (at :0)
System.TimeSpan.ToString (System.String format, System.IFormatProvider formatProvider) (at :0)
System.Text.StringBuilder.AppendFormatHelper (System.IFormatProvider provider, System.String format, System.ParamsArray args) (at :0)
System.String.FormatHelper (System.IFormatProvider provider, System.String format, System.ParamsArray args) (at :0)
System.String.Format (System.String format, System.Object[] args) (at :0)
Joycon.Update () (at Assets/JoyconLib_scripts/Joycon.cs:370)
JoyconManager.Update () (at Assets/JoyconLib_scripts/JoyconManager.cs:92) "
Test project is here, added only the latest package provided.
Switch Game.zip

Maybe simply change TimeSpan formatting string from s to t or g might fix this problem. Or just comment those Debug log lines.
Lag to dequeue: {3:s}. Lag between packets (expect 15ms): {4:s} -> {3:t} {4:g}


watch mode with ts-jest conceals TypeScript error and caches wrong result

🐛 Bug Report
Watch mode let's test suites pass regardless of TypeScript errors in the spec file
To Reproduce
Please see the repository that I provided below and follow the reproduction steps in its README.
Expected behavior
Watch mode should not miraculously turn failing tests into passing tests.
Link to repl or repo (highly encouraged)
https://github.com/fischeversenker/ts-jest-error-repro
envinfo
  System:
    OS: Linux 4.19 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: 1.22.10 - /mnt/c/Users/felix/AppData/Roaming/npm/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
  npmPackages:
    jest: ^26.6.3 => 26.6.3

ts-jest is not maintained in this repo, you should report it to them: https://github.com/kulshekhar/ts-jest

Thanks for pointing me to them 🙏
In case anyone stumbles upon this: Here is the follow-up ticket: https://github.com/kulshekhar/ts-jest/issues/2525


[SCE] Relaxed url parsing (issue #3880)

Use scala-uri by default, which is way more relaxed than java.net.URI.
Correctly percent-encoded URIs are then passed to java.net.URI.
If a URI is expected to contain macros with %, percentDecode should be set to false when calling the function stringToUri.

The original plan was to use only scala-uri for parsing (in a very relaxed way) and not java.net.URI.create() any more.
Although this was working well, a consequence was that some URIs were encoded differently as before, thus breaking unit tests in jobs using SCE.
It's possible to fix the unit tests but they probably don't cover all the cases that we have in our customers' pipelines and updating the output of a function that is used for every single event in all the pipeline is risky.
So it was decided to continue to use Java parsing first and in case of failure a very relaxed Scala parsing (no percent decoding).

Superseded by #4076


https://github.com/dotnet/AspNetCore.Docs/issues/11801

Fixes #11801
I've tried to create a sample that synchronously adds log messages to an in-memory queue and has a background worker pull the messages out of the queue to do the asynchronous work of pushing data to SQL Server.
If the team agrees, then we can go back and update this article
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-3.1#aspnet-core-and-ef-core-categories

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: sguitardude sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hello @sguitardude ... It's been challenging for the small team to keep samples up-to-date ... see https://github.com/dotnet/AspNetCore.Docs/issues/5495. In this case, third party providers are heavily recommended, and they use this (or similar) approaches for SQL Server. For example, I know Serilog accumulates and batch-writes to SQL Server. They'll let you know, but don't take it the wrong way if they have to decline. If they can't accept, it's probably just going to be for staffing/maintenance reasons in light of the popularity of third-party providers.

No worries.  I'll check out Serilog and other ways to contribute.
On Thu, Aug 13, 2020, 4:54 PM Luke Latham<EMAIL_ADDRESS>wrote:

Hello @sguitardude https://github.com/sguitardude ... It's been
challenging for the small team to keep samples up-to-date ... see #5495
https://github.com/dotnet/AspNetCore.Docs/issues/5495. In this case,
third party providers are heavily recommended, and they use this (or
similar) approaches for SQL Server. For example, I know Serilog accumulates
and batch-writes to SQL Server. They'll let you know, but don't take it the
wrong way if they have to decline. If they can't accept, it's probably just
going to be for staffing/maintenance reasons in light of the popularity of
third-party providers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/pull/19497#issuecomment-673729043,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBDE6KAP3JD6WOUSZOZ37TSAROHPANCNFSM4P623XAA
.

@sguitardude  can you put this on your GitHub? If so, I can tweet it.


[HUDI-8295] validate utilities bundle with spark

Change Logs
utilities bundle validation was only happening for spark 2.4 and 3.1 but since we got rid of those, it has not been happening for any spark versions
Impact
more ci testing
Risk level (write none, low medium or high below)
low
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

https://github.com/apache/hudi/blob/96e64a9b7e8c40e52d4acd8bc773de3e77b3c089/scripts/release/deploy_staging_jars.sh#L49
looks like its spark3.5 and scala 2.13
btw, did we fix all release scripts to account for scala 2.13 ?

@jonvex : looks like validation is failing for spark3.5 and scala 2.13. can you check it out.
"UT spark-datasource Java Tests & DDL" github actions failed due to flaky TestStructuredStreaming test. you can probably ignore that for now.
anyways, once you push some update based on your investigation for validation failure, it will get retriggered.


kfp-api tests are flaky when asserting response metrics

Bug Description
kfp-api integration tests are flaky and sometimes fail in this part, when trying to assert response metrics with the following error
  File "/home/runner/work/kfp-operators/kfp-operators/charms/kfp-api/tests/integration/test_charm.py", line 264, in test_prometheus_grafana_integration
    response_metric = response["data"]["result"][0]["metric"]
IndexError: list index out of range

This time it happened in track/2.0 but I think I 've seen it in main in the past as well.
Cause
My guess is that this is due to resources and if we increase the retry attempts, it will be resolved.
To Reproduce
Run multiple times the integration CI.
Environment
Github runners,
LXD
  Name  Version        Rev    Tracking      Publisher    Notes
  lxd   4.0.9-a29c6f1  24061  4.0/stable/…  canonical**  -
  /usr/bin/sudo snap install lxd --channel=latest/stable
  snap "lxd" is already installed, see 'snap help refresh'
  /usr/bin/sudo snap refresh lxd --channel=latest/stable
  lxd 5.21.1-10f4115 from Canonical** refreshed

juju (3.1/stable) 3.1.8 from Canonical** installed
charmcraft (candidate) 2.6.0 from Canonical** installed
microk8s (1.25-strict/stable) v1.25.16 from Canonical** installed
juju status:
Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-07313-microk8s  microk8s/localhost  3.1.8    unsupported  10:30:16Z

App                           Version                  Status  Scale  Charm                         Channel         Rev  Address         Exposed  Message
grafana-k8s                   9.2.1                    active      1  grafana-k8s                   1.0/stable       93  <IP_ADDRESS>  no
kfp-db                        mariadb/server:10.3      active      1  charmed-osm-mariadb-k8s       latest/stable    35  <IP_ADDRESS>  no       ready
kfp-viz                                                active      1  kfp-viz                       2.0/stable      985  <IP_ADDRESS>  no
minio                         res:oci-image@1755999    active      1  minio                         ckf-1.8/stable  278  <IP_ADDRESS>  no
mysql-k8s                     8.0.35-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s                     8.0/stable      127  <IP_ADDRESS>   no
prometheus-k8s                2.47.2                   active      1  prometheus-k8s                1.0/stable      159  <IP_ADDRESS>  no
prometheus-scrape-config-k8s  n/a                      active      1  prometheus-scrape-config-k8s  1.0/stable       44  <IP_ADDRESS>   no

Unit                             Workload  Agent  Address     Ports          Message
grafana-k8s/0*                   active    idle   <IP_ADDRESS>
kfp-db/0*                        active    idle   <IP_ADDRESS>  3306/TCP       ready
kfp-viz/0*                       active    idle   <IP_ADDRESS>
minio/0*                         active    idle   <IP_ADDRESS>  9000-9001/TCP
mysql-k8s/0*                     active    idle   <IP_ADDRESS>                 Primary
prometheus-k8s/0*                active    idle   <IP_ADDRESS>
prometheus-scrape-config-k8s/0*  active    idle   <IP_ADDRESS>

Relevant Log Output
tests/integration/test_charm.py::TestCharm::test_prometheus_grafana_integration
-------------------------------- live log call ---------------------------------
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/prometheus-k8s-159
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/grafana-k8s-93
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/prometheus-scrape-config-k8s-44
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [allocating] waiting: installing agent
  prometheus-k8s/0 [allocating] waiting: installing agent
  prometheus-scrape-config-k8s/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [allocating] waiting: installing agent
  prometheus-k8s/0 [executing] maintenance: installing charm software
  prometheus-scrape-config-k8s/0 [idle] active:
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [executing] maintenance: installing charm software
  prometheus-k8s/0 [executing] active:
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [idle] active:
INFO     test_charm:test_charm.py:248 Prometheus available at http://<IP_ADDRESS>:9090
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 1)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 2)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 3)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 4)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 5)
INFO     test_charm:test_charm.py:261 Response status is success
FAILED
tests/integration/test_charm.py::TestCharm::test_remove_application PASSED
------------------------------ live log teardown -------------------------------
INFO     pytest_operator.plugin:plugin.py:783 Model status:

Model     Controller                Cloud/Region        Version  SLA          Timestamp
kubeflow  github-pr-07313-microk8s  microk8s/localhost  3.1.8    unsupported  10:30:16Z

App                           Version                  Status  Scale  Charm                         Channel         Rev  Address         Exposed  Message
grafana-k8s                   9.2.1                    active      1  grafana-k8s                   1.0/stable       93  <IP_ADDRESS>  no
kfp-db                        mariadb/server:10.3      active      1  charmed-osm-mariadb-k8s       latest/stable    35  <IP_ADDRESS>  no       ready
kfp-viz                                                active      1  kfp-viz                       2.0/stable      985  <IP_ADDRESS>  no
minio                         res:oci-image@1755999    active      1  minio                         ckf-1.8/stable  278  <IP_ADDRESS>  no
mysql-k8s                     8.0.35-0ubuntu<IP_ADDRESS>  active      1  mysql-k8s                     8.0/stable      127  <IP_ADDRESS>   no
prometheus-k8s                2.47.2                   active      1  prometheus-k8s                1.0/stable      159  <IP_ADDRESS>  no
prometheus-scrape-config-k8s  n/a                      active      1  prometheus-scrape-config-k8s  1.0/stable       44  <IP_ADDRESS>   no

Unit                             Workload  Agent  Address     Ports          Message
grafana-k8s/0*                   active    idle   <IP_ADDRESS>
kfp-db/0*                        active    idle   <IP_ADDRESS>  3306/TCP       ready
kfp-viz/0*                       active    idle   <IP_ADDRESS>
minio/0*                         active    idle   <IP_ADDRESS>  9000-9001/TCP
mysql-k8s/0*                     active    idle   <IP_ADDRESS>                 Primary
prometheus-k8s/0*                active    idle   <IP_ADDRESS>
prometheus-scrape-config-k8s/0*  active    idle   <IP_ADDRESS>

INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:

unit-kfp-api-0: 10:19:36 ERROR unit.kfp-api/0.juju-log Failed to handle <InstallEvent via KfpApiOperator/on/install[1]> with error: Please add required relation object-storage
unit-kfp-api-0: 10:19:39 ERROR unit.kfp-api/0.juju-log Failed to handle <LeaderElectedEvent via KfpApiOperator/on/leader_elected[21]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:19:40 ERROR unit.kfp-api/0.juju-log Failed to handle <PebbleReadyEvent via KfpApiOperator/on/apiserver_pebble_ready[26]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:19:41 ERROR unit.kfp-api/0.juju-log Failed to handle <ConfigChangedEvent via KfpApiOperator/on/config_changed[31]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:19:47 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to handle <RelationJoinedEvent via KfpApiOperator/on/mysql_relation_joined[41]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:19:47 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to handle <RelationChangedEvent via KfpApiOperator/on/mysql_relation_changed[46]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:19:53 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to handle <RelationChangedEvent via KfpApiOperator/on/mysql_relation_changed[51]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:19:55 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to handle <RelationChangedEvent via KfpApiOperator/on/mysql_relation_changed[56]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-viz-0: 10:19:57 ERROR unit.kfp-viz/0.juju-log kfp-viz:2: execute_components caught unhandled exception when executing configure_charm for relation:kfp-viz
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 294, in get_sdi_interface
    interface = get_interface(charm, relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 388, in get_interface
    instance.get_data()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 172, in get_data
    rel_data = self.unwrap(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 269, in unwrap
    version = self.get_version(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 111, in get_version
    raise errors.UnversionedRelation(relation)
serialized_data_interface.errors.UnversionedRelation: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api

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

Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/charm_reconciler.py", line 92, in reconcile
    component_item.component.configure_charm(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 51, in configure_charm
    self._configure_app(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 88, in _configure_app
    self._configure_app_leader(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 221, in _configure_app_leader
    interface = self.get_interface()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 229, in get_interface
    return get_sdi_interface(self._charm, self._relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 297, in get_sdi_interface
    raise ErrorWithStatus(str(err), WaitingStatus) from err
charmed_kubeflow_chisme.exceptions._with_status.ErrorWithStatus: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api
unit-kfp-api-0: 10:19:58 ERROR unit.kfp-api/0.juju-log kfp-viz:2: Failed to handle <RelationChangedEvent via KfpApiOperator/on/kfp_viz_relation_changed[66]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-viz-0: 10:19:58 ERROR unit.kfp-viz/0.juju-log execute_components caught unhandled exception when executing configure_charm for relation:kfp-viz
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 294, in get_sdi_interface
    interface = get_interface(charm, relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 388, in get_interface
    instance.get_data()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 172, in get_data
    rel_data = self.unwrap(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 269, in unwrap
    version = self.get_version(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 111, in get_version
    raise errors.UnversionedRelation(relation)
serialized_data_interface.errors.UnversionedRelation: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api

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

Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/charm_reconciler.py", line 92, in reconcile
    component_item.component.configure_charm(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 51, in configure_charm
    self._configure_app(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 88, in _configure_app
    self._configure_app_leader(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 221, in _configure_app_leader
    interface = self.get_interface()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 229, in get_interface
    return get_sdi_interface(self._charm, self._relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 297, in get_sdi_interface
    raise ErrorWithStatus(str(err), WaitingStatus) from err
charmed_kubeflow_chisme.exceptions._with_status.ErrorWithStatus: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api
unit-kfp-viz-0: 10:20:00 ERROR unit.kfp-viz/0.juju-log execute_components caught unhandled exception when executing configure_charm for relation:kfp-viz
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 294, in get_sdi_interface
    interface = get_interface(charm, relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 388, in get_interface
    instance.get_data()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 172, in get_data
    rel_data = self.unwrap(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 269, in unwrap
    version = self.get_version(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 111, in get_version
    raise errors.UnversionedRelation(relation)
serialized_data_interface.errors.UnversionedRelation: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api

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

Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/charm_reconciler.py", line 92, in reconcile
    component_item.component.configure_charm(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 51, in configure_charm
    self._configure_app(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 88, in _configure_app
    self._configure_app_leader(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 221, in _configure_app_leader
    interface = self.get_interface()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 229, in get_interface
    return get_sdi_interface(self._charm, self._relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 297, in get_sdi_interface
    raise ErrorWithStatus(str(err), WaitingStatus) from err
charmed_kubeflow_chisme.exceptions._with_status.ErrorWithStatus: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api
unit-kfp-api-0: 10:20:02 ERROR unit.kfp-api/0.juju-log kfp-viz:2: Failed to handle <RelationChangedEvent via KfpApiOperator/on/kfp_viz_relation_changed[76]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-api-0: 10:20:03 ERROR unit.kfp-api/0.juju-log object-storage:1: Failed to handle <RelationChangedEvent via KfpApiOperator/on/object_storage_relation_changed[81]> with error: List of <ops.model.Relation object-storage:1> versions not found for apps: minio
unit-kfp-viz-0: 10:20:05 ERROR unit.kfp-viz/0.juju-log kfp-viz:2: execute_components caught unhandled exception when executing configure_charm for relation:kfp-viz
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 294, in get_sdi_interface
    interface = get_interface(charm, relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 388, in get_interface
    instance.get_data()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 172, in get_data
    rel_data = self.unwrap(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 269, in unwrap
    version = self.get_version(relation)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/serialized_data_interface/sdi.py", line 111, in get_version
    raise errors.UnversionedRelation(relation)
serialized_data_interface.errors.UnversionedRelation: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api

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

Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/charm_reconciler.py", line 92, in reconcile
    component_item.component.configure_charm(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 51, in configure_charm
    self._configure_app(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/component.py", line 88, in _configure_app
    self._configure_app_leader(event)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 221, in _configure_app_leader
    interface = self.get_interface()
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 229, in get_interface
    return get_sdi_interface(self._charm, self._relation_name)
  File "/var/lib/juju/agents/unit-kfp-viz-0/charm/venv/charmed_kubeflow_chisme/components/serialised_data_interface_components.py", line 297, in get_sdi_interface
    raise ErrorWithStatus(str(err), WaitingStatus) from err
charmed_kubeflow_chisme.exceptions._with_status.ErrorWithStatus: List of <ops.model.Relation kfp-viz:2> versions not found for apps: kfp-api
unit-kfp-api-0: 10:20:08 ERROR unit.kfp-api/0.juju-log object-storage:1: Failed to generate container configuration.
unit-kfp-api-0: 10:20:08 ERROR unit.kfp-api/0.juju-log object-storage:1: Failed to handle <RelationChangedEvent via KfpApiOperator/on/object_storage_relation_changed[86]> with error: Waiting for kfp-viz relation data
unit-kfp-api-0: 10:20:11 ERROR unit.kfp-api/0.juju-log object-storage:1: Failed to generate container configuration.
unit-kfp-api-0: 10:20:11 ERROR unit.kfp-api/0.juju-log object-storage:1: Failed to handle <RelationChangedEvent via KfpApiOperator/on/object_storage_relation_changed[91]> with error: Waiting for kfp-viz relation data
unit-kfp-api-0: 10:22:59 ERROR unit.kfp-api/0.juju-log relational-db:6: Relation mysql is deprecated. Remove deprecated mysql relation to unblock.
unit-kfp-api-0: 10:23:00 ERROR unit.kfp-api/0.juju-log relational-db:6: Relation mysql is deprecated. Remove deprecated mysql relation to unblock.
unit-kfp-api-0: 10:23:01 ERROR unit.kfp-api/0.juju-log relational-db:6: Relation mysql is deprecated. Remove deprecated mysql relation to unblock.
unit-kfp-api-0: 10:23:01 ERROR unit.kfp-api/0.juju-log relational-db:6: Relation mysql is deprecated. Remove deprecated mysql relation to unblock.
unit-kfp-api-0: 10:23:33 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to generate container configuration.
unit-kfp-api-0: 10:23:33 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to handle <RelationDepartedEvent via KfpApiOperator/on/mysql_relation_departed[132]> with error: Please add required database relation: eg. relational-db
unit-kfp-api-0: 10:23:34 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to generate container configuration.
unit-kfp-api-0: 10:23:34 ERROR unit.kfp-api/0.juju-log mysql:0: Failed to handle <RelationBrokenEvent via KfpApiOperator/on/mysql_relation_broken[137]> with error: Please add required database relation: eg. relational-db
unit-kfp-api-0: 10:23:52 ERROR unit.kfp-api/0.juju-log relational-db:7: Failed to generate container configuration.
unit-kfp-api-0: 10:23:52 ERROR unit.kfp-api/0.juju-log relational-db:7: Failed to handle <RelationJoinedEvent via KfpApiOperator/on/relational_db_relation_joined[147]> with error: Waiting for relational-db data
unit-kfp-api-0: 10:24:17 ERROR unit.kfp-api/0.juju-log mysql:8: Relation mysql is deprecated. Remove deprecated mysql relation to unblock.
unit-kfp-api-0: 10:24:18 ERROR unit.kfp-api/0.juju-log mysql:8: Relation mysql is deprecated. Remove deprecated mysql relation to unblock.
application-kfp-db: 10:24:37 ERROR juju.worker.caasoperator.runner exited "kfp-db/0": relation scope id "60e4f333-4289-4b6f-8dd5-8bea9986a1ea:r#8#kfp-api": settings 60e4f333-4289-4b6f-8dd5-8bea9986a1ea:r#8#kfp-api not found (not found)
unit-kfp-api-0: 10:24:37 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: relation scope id "60e4f333-4289-4b6f-8dd5-8bea9986a1ea:r#8#kfp-db": settings 60e4f333-4289-4b6f-8dd5-8bea9986a1ea:r#8#kfp-db not found (not found)
unit-kfp-api-0: 10:30:06 ERROR unit.kfp-api/0.juju-log relational-db:7: Failed to handle <RelationDepartedEvent via KfpApiOperator/on/relational_db_relation_departed[213]> with error: Please add required relation object-storage
unit-kfp-api-0: 10:30:07 ERROR unit.kfp-api/0.juju-log relational-db:7: Failed to handle <RelationBrokenEvent via KfpApiOperator/on/relational_db_relation_broken[218]> with error: Please add required relation object-storage
unit-kfp-api-0: 10:30:08 ERROR unit.kfp-api/0.juju-log Failed to handle <PebbleReadyEvent via KfpApiOperator/on/apiserver_pebble_ready[223]> with error: Please add required relation object-storage

INFO     pytest_operator.plugin:plugin.py:855 Forgetting main...
ERROR    websockets.protocol:protocol.py:881 Error in data transfer
Traceback (most recent call last):
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py", line 827, in transfer_data
    message = await self.read_message()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py", line 895, in read_message
    frame = await self.read_data_frame(max_size=self.max_size)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py", line 971, in read_data_frame
    frame = await self.read_frame(max_size)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py", line 1047, in read_frame
    frame = await Frame.read(
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/websockets/framing.py", line 105, in read
    data = await reader(2)
  File "/usr/lib/python3.8/asyncio/streams.py", line 723, in readexactly
    await self._wait_for_data('readexactly')
  File "/usr/lib/python3.8/asyncio/streams.py", line 517, in _wait_for_data
    await self._waiter
  File "/usr/lib/python3.8/asyncio/selector_events.py", line 910, in write
    n = self._sock.send(data)
OSError: [Errno 9] Bad file descriptor

=================================== FAILURES ===================================
________________ TestCharm.test_prometheus_grafana_integration _________________
Traceback (most recent call last):
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/_pytest/runner.py", line 341, in from_call
    result: Optional[TResult] = func()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/_pytest/runner.py", line 262, in <lambda>
    lambda: ihook(item=item, **kwds), when=when, reraise=reraise
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_hooks.py", line 493, in __call__
    return self._hookexec(self.name, self._hookimpls, kwargs, firstresult)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_manager.py", line 115, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_callers.py", line 152, in _multicall
    return outcome.get_result()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_result.py", line 114, in get_result
    raise exc.with_traceback(exc.__traceback__)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_callers.py", line 77, in _multicall
    res = hook_impl.function(*args)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/_pytest/runner.py", line 177, in pytest_runtest_call
    raise e
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/_pytest/runner.py", line 169, in pytest_runtest_call
    item.runtest()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/_pytest/python.py", line 1792, in runtest
    self.ihook.pytest_pyfunc_call(pyfuncitem=self)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_hooks.py", line 493, in __call__
    return self._hookexec(self.name, self._hookimpls, kwargs, firstresult)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_manager.py", line 115, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_callers.py", line 152, in _multicall
    return outcome.get_result()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_result.py", line 114, in get_result
    raise exc.with_traceback(exc.__traceback__)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pluggy/_callers.py", line 77, in _multicall
    res = hook_impl.function(*args)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/_pytest/python.py", line 194, in pytest_pyfunc_call
    result = testfunction(**testargs)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/pytest_asyncio/plugin.py", line 532, in inner
    _loop.run_until_complete(task)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/home/runner/work/kfp-operators/kfp-operators/charms/kfp-api/tests/integration/test_charm.py", line 250, in test_prometheus_grafana_integration
    for attempt in self.retry_for_5_attempts:
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/tenacity/__init__.py", line 347, in __iter__
    do = self.iter(retry_state=retry_state)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/tenacity/__init__.py", line 325, in iter
    raise retry_exc.reraise()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/tenacity/__init__.py", line 158, in reraise
    raise self.last_attempt.result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 437, in result
    return self.__get_result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/home/runner/work/kfp-operators/kfp-operators/charms/kfp-api/tests/integration/test_charm.py", line 264, in test_prometheus_grafana_integration
    response_metric = response["data"]["result"][0]["metric"]
IndexError: list index out of range
------------------------------ Captured log call -------------------------------
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/prometheus-k8s-159
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/grafana-k8s-93
INFO     juju.model:model.py:2069 Deploying ch:amd64/focal/prometheus-scrape-config-k8s-44
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
WARNING  juju.model:model.py:1558 relate is deprecated and will be removed. Use integrate instead.
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [allocating] waiting: installing agent
  prometheus-k8s/0 [allocating] waiting: installing agent
  prometheus-scrape-config-k8s/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [allocating] waiting: installing agent
  prometheus-k8s/0 [executing] maintenance: installing charm software
  prometheus-scrape-config-k8s/0 [idle] active:
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [executing] maintenance: installing charm software
  prometheus-k8s/0 [executing] active:
INFO     juju.model:model.py:2759 Waiting for model:
  grafana-k8s/0 [idle] active:
INFO     test_charm:test_charm.py:248 Prometheus available at http://<IP_ADDRESS>:9090
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 1)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 2)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 3)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 4)
INFO     test_charm:test_charm.py:261 Response status is success
INFO     test_charm:test_charm.py:251 Testing prometheus deployment (attempt 5)
INFO     test_charm:test_charm.py:261 Response status is success
=============================== warnings summary ===============================
tests/integration/test_charm.py: 10 warnings
  /home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/model.py:1558: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
    log.warn("relate is deprecated and will be removed. Use integrate instead.")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED tests/integration/test_charm.py::TestCharm::test_prometheus_grafana_integration - IndexError: list index out of range
============= 1 failed, 5 passed, 10 warnings in 945.42s (0:15:45) =============
Task was destroyed but it is pending!
task: <Task pending name='Task_Pinger' coro=<Connection._pinger() running at /home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/connection.py:613> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f73544d6e20>()]> cb=[gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769, gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769]>
Task was destroyed but it is pending!
task: <Task pending name='Task_Receiver' coro=<Connection._receiver() running at /home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/connection.py:570> wait_for=<Future finished result=None> cb=[gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769, gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769]>
Exception ignored in: <coroutine object Connection._pinger.<locals>._do_ping at 0x7f735213edc0>
Traceback (most recent call last):
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/connection.py", line 606, in _do_ping
    await pinger_facade.Ping()
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/facade.py", line 486, in wrapper
    reply = await f(*args, **kwargs)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/_client1.py", line 9012, in Ping
    reply = await self.rpc(msg)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/facade.py", line 659, in rpc
    result = await self.connection.rpc(msg, encoder=TypeEncoder)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/connection.py", line 667, in rpc
    result = await self._recv(msg['request-id'])
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/connection.py", line 482, in _recv
    return await self.messages.get(request_id)
  File "/home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/utils.py", line 108, in get
    value = await self._queues[id].get()
  File "/usr/lib/python3.8/asyncio/queues.py", line 165, in get
    getter.cancel()  # Just in case getter is not done yet.
  File "/usr/lib/python3.8/asyncio/base_events.py", line 719, in call_soon
    self._check_closed()
  File "/usr/lib/python3.8/asyncio/base_events.py", line 508, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
Task was destroyed but it is pending!
task: <Task pending name='Task-7299' coro=<Connection._pinger.<locals>._do_ping() done, defined at /home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/client/connection.py:604> wait_for=<Future cancelled> cb=[create_task_with_handler.<locals>._task_result_exp_handler(task_name='tmp', logger=<Logger juju....ion (WARNING)>)() at /home/runner/work/kfp-operators/kfp-operators/.tox/integration/lib/python3.8/site-packages/juju/jasyncio.py:39, gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769]>
Task was destroyed but it is pending!
task: <Task pending name='Task-7300' coro=<Event.wait() done, defined at /usr/lib/python3.8/asyncio/locks.py:296> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f73544d6c40>()]> cb=[gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769]>
Task was destroyed but it is pending!
task: <Task pending name='Task-7212' coro=<Event.wait() running at /usr/lib/python3.8/asyncio/locks.py:309> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f735180e910>()]> cb=[gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769, gather.<locals>._done_callback() at /usr/lib/python3.8/asyncio/tasks.py:769]>
integration: exit 1 (946.17 seconds) /home/runner/work/kfp-operators/kfp-operators/charms/kfp-api> pytest -vv --tb native --asyncio-mode=auto /home/runner/work/kfp-operators/kfp-operators/charms/kfp-api/tests/integration --log-cli-level=INFO -s --model kubeflow pid=143038
  integration: FAIL code 1 (963.19=setup[17.02]+cmd[946.17] seconds)
  evaluation failed :( (963.25 seconds)
kfp-api-integration: exit 1 (963.37 seconds) /home/runner/work/kfp-operators/kfp-operators> tox -c charms/kfp-api -e integration -- --model kubeflow pid=142342
  kfp-api-integration: FAIL code 1 (964.28=setup[0.91]+cmd[963.37] seconds)
  evaluation failed :( (964.36 seconds)

Additional Context
No response

Same with https://github.com/canonical/istio-operators/issues/384

Bumped into this in a PR that didn't update any code https://github.com/canonical/kfp-operators/pull/393
https://github.com/canonical/kfp-operators/actions/runs/10366700320/job/28696539467?pr=393
@orfeas-k do we know what causes this flakiness?

@kimwnasptd No, I haven't investigated this. IIRC, increasing the timeout (or the amount of retries) has resolved this in the past, so it could be caused from charms/integration not being ready yet.


update docs of performance test

Please change the title of this pr more accurate, using update docs of performance test instead of update performance test is better.

Pull Request Test Coverage Report for Build 1787

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.634%

Totals

Change from base Build 875:
0.0%

Covered Lines:
11087

Relevant Lines:
19237

💛  - Coveralls

Codecov Report

Merging #4352 into master will decrease coverage by 0.27%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4352      +/-   ##
============================================
- Coverage     54.16%   53.88%   -0.28%
+ Complexity      352      351       -1
============================================
  Files          1046     1047       +1
  Lines         19237    19288      +51
  Branches       3536     3550      +14
============================================
- Hits          10419    10393      -26
- Misses         8161     8238      +77
  Partials        657      657

Impacted Files
Coverage Δ
Complexity Δ

...shardingsphere/sql/parser/core/SQLParseKernel.java
0% <0%> (-100%)
0% <0%> (ø)

...l/parser/core/rule/registry/ParseRuleRegistry.java
0% <0%> (-55.56%)
0% <0%> (ø)

...ser/core/extractor/SQLSegmentsExtractorEngine.java
0% <0%> (-9.1%)
0% <0%> (-1%)

...ackend/text/TextProtocolBackendHandlerFactory.java
72.41% <0%> (-6.9%)
0% <0%> (ø)

.../sql/parser/sql/statement/dml/SelectStatement.java
28.57% <0%> (-4.77%)
0% <0%> (ø)

...ingsphere/sql/parser/visitor/SQLServerVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...hardingsphere/sql/parser/visitor/MySQLVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...phere/sql/parser/visitor/impl/MySQLDALVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...ngsphere/sql/parser/visitor/PostgreSQLVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...ardingsphere/sql/parser/visitor/OracleVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

... and 13 more

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 f26a0c2...1a74e24. Read the comment docs.