text:
updated jupyter notebooks for data parallel python

Existing Sample Changes
Description
updated jupyter notebooks for data parallel python.
Fixes Issue#
External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[ ] Bug fix (non-breaking change which fixes an issue)
[X ] New feature (non-breaking change which adds functionality)
[ ] Implement fixes for ONSAM Jiras

How Has This Been Tested?
Devcloud
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

Adding @ishaghosh27 to review the README.

repo: oneapi-src/oneAPI-samples


text:
Cannot start onezone with 17.06.0-beta2

I tried to launch onezone with the new version 17.06.0-beta2, but I obtained the error
[root@onezone-test 3_0_oneprovider_onezone_multihost]# ./run_onedata.sh --zone
IMPORTANT: After each start wait for a message: Congratulations! onezone has been successfully started.
To ensure that the onezone is completely setup.
Pulling node1.onezone.localhost (onedata/onezone:17.06.0-beta2)...
17.06.0-beta2: Pulling from onedata/onezone
Digest: sha256:df8e320115ead4d71869de0fee43484054cc82ae2d9f15cf689828b0b8d9c35f
Status: Image is up to date for onedata/onezone:17.06.0-beta2
Creating onezone-INFN-BA ...
Creating onezone-INFN-BA ... done
Attaching to onezone-INFN-BA
onezone-INFN-BA            |
onezone-INFN-BA            | [Errno 39] Directory not empty: '/etc/init.d'
onezone-INFN-BA exited with code 1

the steps I've done are:

create a new CentOS 7 VM (8 CPU, 16GB of RAM)
yum update
install docker
install docker-compose
git clone this repo
modify docker-compose file to suit our site's needs
./run_onedata.sh --zone

can you please provide help?
Cheers,
stefano
p.s. I attach the docker compose file and the content of /etc/init.d directory inside the docker conta
Content_init.d_directory.txt
docker-compose-onezone.txt
iner

@stefanonicotri this issue was resolved with beta6 release. please try it and reopen this issue if needed.

I've just hit the same issue with onedata/onezone:17.06.0-rc8:
Pulling node1.onezone.localhost (onedata/onezone:17.06.0-rc8)...
17.06.0-rc8: Pulling from onedata/onezone
Digest: sha256:7aa98da35928fa53745695b98b57638e5dfdd9c74795b72121fb9ccab582c619
Status: Image is up to date for onedata/onezone:17.06.0-rc8
Creating onezone-1 ... done
Attaching to onezone-1
onezone-1                  |
onezone-1                  | [Errno 39] Directory not empty: '/etc/init.d'

source: gharchive/issue

authors: caifti groundnuty stefanonicotri

repo: onedata/getting-started

license: mit

license_type: permissive

license_source: bigquery


text:
Memory overwrite caused by using global memory

Unexpected memory changes caused by using global memory change global memory to heap memory.
Actual behavior
Cell:(Abs:0x2B98)[A8][FF][FF][FF][6E][6B]
    Size:                              0x58
    Signeture:                         nk
    Flags:                             0x20
    Time stamp:                        2021/09/12 08:56
    Access bits:                       0x2
    Parent offset:                     0x3D8
    Number of subkeys:                 0x0
    Number of volatile subkeys:        0x0
    Subkeys list offset:               0xFFFFFFFF
    Number of key values:              0x1
    Key values list offset:            0x19B8
    Key security offset:               0x178
    Class name offset:                 0xFFFFFFFF
    Largest subkey name length:        0x0
    Largest subkey class name length:  0x0
    Largest value name length:         0xE
    Largest value data size:           0x1
    WorkVar:                           0x0
    Key name length:                   0x8
    Class name length:                 0x0
    Key name:                          46000010

ValueList:(Abs:0x29B8)[F8][FF][FF][FF]
    Size:                              0x8
    Offset #0:                         0x1998

Cell:(Abs:0x2998)[E0][FF][FF][FF][76][6B]
    Size:                              0x20
    Signeture:                         vk
    Value name size:                   0x7
    Data size:                         0x80000001
    Data offset:                       0x1
    Data type:                         0x3
    Flags:                             0x1
    Key name:                          Element
    Data:                              0x1

ValueList:(Abs:0x29B8)[F8][FF][FF][FF]
    Size:                              0x8
    Offset #0:                         0x1998

Cell:(Abs:0x2998)[E0][FF][FF][FF][76][6B]
    Size:                              0x20
    Signeture:                         vk
    Value name size:                   0x7
    Data size:                         0x80000001
    Data offset:                       0x1
    Data type:                         0x3
    Flags:                             0x1
    Key name:                          Element
    Data:                              0x1

What happened
When the key node structure changed by the child key returns to the parent key, the unset is changed and the same value is referenced.
How to fix it to behave as expected
Change to a local variable and allocate heap memory. Since memory usage will increase more than before, we will organize variables.

This commit caused the expected behavior!

license: MIT

license_source: github-api


text:
create docker playground for ease of use

To address 256 and similar issues people have with environment setup having a docker playground will help.

We use killercoda our testing playground.  I can set you up with it if you'd like

https://killercoda.com/starrocks

just extended your docker demo to work with S3 and HMS.  https://github.com/alberttwong/incubator-xtable/tree/main/demo-s3

authors: alberttwong sagarlakshmipathy

repo: onetable-io/onetable


text:
Resize image is always blurry

Let's say I have a 3024 × 4032 image, and I want to resize it to 77x77
I use this framework like so:
let processor = ResizingImageProcessor(targetSize: CGSize(width: 77, height: 77)) >> RoundCornerImageProcessor(cornerRadius: 77/2)
The result is a very blurry image. How do I maintain the same aspect ratio?
Here is the image I am using:
http://imgur.com/a/lKtI9
Thanks.

The unit of image processor is pixel instead of point. If you are trying to set the image to a 77x77 point retina display (I guess you should need so), it means you need to resize it to 2x at least, which means 154x154.
And if you are also targeting an iPhone x Plus 3x display, you need 231x231.

Hey Thanks.
Last question, if I reuse the same processor with the same arguments, and I call it on the same image url, is Kingfisher smart enough to know that a 77x77 resize of this image already has been done before?

Sure.

repo: onevcat/Kingfisher


text:
Add a callback to the Encoder

Work towards https://github.com/dapperlabs/cadence-private-issues/issues/64
Description
It can be useful to have a callback function that gets called during the encoding (e.g: https://github.com/dapperlabs/cadence-private-issues/issues/64), to keep track of the operation.
This PR adds a generic Callback field to the Encoder, which wraps different callback functions. Users of the encoder can register callbacks when they create the encoder. For now, the callback only has one function BeforeEncode which is/should be invoked at the start of each value encoding.
TODO:

For more accurate tracking, BeforeEncode must be invoked during the slab encoding.

[x] Targeted PR against main branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[ ] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report

Merging #287 (43e0f7d) into main (d5384d9) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #287      +/-   ##
==========================================
+ Coverage   69.08%   69.13%   +0.05%
==========================================
  Files          14       14
  Lines        7306     7307       +1
==========================================
+ Hits         5047     5052       +5
+ Misses       1624     1623       -1
+ Partials      635      632       -3

Impacted Files
Coverage Δ

array_debug.go
54.16% <100.00%> (ø)

encode.go
80.95% <100.00%> (+0.30%)
:arrow_up:

map_debug.go
55.50% <100.00%> (ø)

storable.go
65.57% <100.00%> (ø)

storage.go
79.30% <100.00%> (+0.52%)
:arrow_up:

array.go
76.15% <0.00%> (-0.34%)
:arrow_down:

map.go
71.78% <0.00%> (+0.10%)
:arrow_up:

errors.go
22.62% <0.00%> (+2.91%)
:arrow_up:

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

Oh I see. So reporting at the beginning of each slab is sufficient, and don't need to report for each storable?

@SupunS Yes.  Storables implemented by Cadence are elements in atree (leaf) slabs.  Therefore, we don't need to meter storables if we meter slabs.

source: gharchive/pull-request

authors: SupunS codecov-commenter fxamacker

repo: onflow/atree


text:
A few dead link references

These reference links fail, they need to be fixed or removed.
https://academy.ecdao.org/EA_Iso.svg
https://chainmonsters.com/

add references

http-api (node)
testnet/mainnet endpoints
other references in the docs
unity reference
cadence language functions reference
fcl
go
flow status network

https://github.com/onflow/docs/pull/238

authors: bthaile nialexsan

repo: onflow/docs


text:
Docsite links return 404

Problem
The bookmarks on this section return 400s: https://developers.flow.com/tools/fcl-js/tutorials/flow-app-quickstart#introduction
The bookmarks on the right sidebar link to the correct pages.
There might be typo in the URL? Extra x before the #
expected:
https://developers.flow.com/tools/fcl-js/tutorials/flow-app-quickstart#configuration

actual:
https://developers.flow.com/tools/fcl-js/tutorials/flow-app-quickstartx#configuration

Steps to Reproduce

go to link
click links in Introduction section

Context

Closing as this is now fixed.

authors: JeffreyDoyle MrDSGC

repo: onflow/fcl-js


text:
Report system chunk transactions within a block

Closes https://github.com/onflow/flow-cli/issues/911
Description
The last transaction returned from flow.GetTransactionsByBlockID, is the system chunk transaction. We add it as the last transaction in the last collection, so it can be returned from the command:
flow blocks get 53665542 --network=mainnet --include transactions

For contributor use:

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report

Merging #1091 (79f9aa3) into master (6c48d41) will increase coverage by 0.01%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##           master    #1091      +/-   ##
==========================================
+ Coverage   39.50%   39.51%   +0.01%
==========================================
  Files          37       37
  Lines        1858     1870      +12
==========================================
+ Hits          734      739       +5
- Misses       1039     1044       +5
- Partials       85       87       +2

Flag
Coverage Δ

unittests
39.51% <41.66%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

internal/blocks/get.go
65.90% <41.66%> (-9.10%)
:arrow_down:

The solution looks good, but it is a strange problem to have in the first place.
Does flow.GetBlock not return the system collection?

repo: onflow/flow-cli


text:
Don't create machine accounts for non-consensus or collection nodes

Closes https://github.com/onflow/flow-core-contracts/issues/241

Ignores votes that have not been submitted for qc and adds a test case for this

Only call create machine account function if the node is collection or consensus so the account that is registering doesn't have to pay account creation fees

@jordanschalm Can you check out this PR instead? This includes the QC fix as well as a staking collection update for a machine account bug

repo: onflow/flow-core-contracts

license: Unlicense


text:
Add FCLCrypto to default deployed contracts

FCLCrypto contract should be deployed along with default contracts on emulator start
Dev wallet relies on FCLCrypto Contract and currently needs to be manually deployed to avoid an error
when authenticating with FCL ^1.0.0
If added as one of the default contracts on emulator start, this step and error can be avoided.
https://github.com/onflow/fcl-contracts/tree/main/contracts

@gregsantos sorry for late reply, should we prioritize this in this sprint?

No problem @sideninja
Yea, i think it is a good idea to prioritize this sprint as it will address a prominent issue with local development.

why this contract exists btw ? it seems like it is just one function.

@gregsantos I'm finishing up this task, but I would need the https://github.com/onflow/fcl-contracts to become public repo.

@psiemens may need to open as code owner
@bluesign This contract is used in verifying signatures (user, and account-proof)

I understand @gregsantos but as I mentioned earlier[0], especially emulator has so many unnecessary contracts.
To run a single function, deploying a new contract, seems little unnecessary to me. Is there a specific reason for this to be a contract, instead of Function in the script ?
[0] https://github.com/onflow/flow-emulator/issues/170

@bluesign Thanks Deniz, your thoughts on emulator contracts makes sense.
We created the FCLCrypto contract when the cadence Crypto lib was removed and to help with transition to account-proof v2. We may switch back to using a script, making this unnecessary soon. For now it might be better to deploy the contract along with others in the dev-wallet. Closing this in favor of https://github.com/onflow/fcl-dev-wallet/issues/136

authors: bluesign gregsantos sideninja

repo: onflow/flow-emulator


text:
Learn page

Adds the "Learn" page

There was already a "filter" icon but it was not the one used in the designs, so I added the necessary one and called it "filter2.svg" - not ideal but I didn't want to assume the other icon wasn't being used. We may want to rename this.
The pagination is a little tricky because the mobile version only shows 4 items/page while the desktop version shows 12 items/page. To handle this dynamically we'd need to import the current tailwind theme and "resolve" the current values - but the tailwind config is stored outside of the design system and I wasn't sure if we could potentially be passing in different tailwind configs, and how this would resolve. It would still be tricky because we'd need to test the underlying media queries and watch for changes - and there's some problems with Safari's implementation. At the end of the day it just seemed simpler to render the thing content twice, with different page sizes, only showing the appropriate one. Happy to reconsider this implementation if we think it's going to be problematic.
I modified the Pagination component so that it uses <button/> elements instead of divs (much better for a11y) and so that it doesn't allow moving to invalid pages.

I've updated this to use the pagination as discussed yesterday:

All 3 lists of tutorials are paginated
All show 4 items at a time, regardless of screen size
Removed "View tutorials" link from the NFTs section

Also:

Extracted this logic to a component called PaginatedTutorialCardList
Sort tags for consistency when displayed in "All content" section


text:
fix(macOS/#1085): allow opening of files through system protocol

As of right now, if you try to open a file in Oni on macOS either through "Open With" in Finder or with the open command in Terminal.app, Oni activates but doesn't open the file passed in.
This does two main things:

adds file associations to the Info.plist so that we're shown when trying to "Open With" a compatible file:

binds to Revery's new App.onFileOpen event system to trigger opens within Oni2 itself

It also changes the executable in the Info.plist from Oni2 to Oni2_editor -- this is necessary because otherwise the file information gets lost between the processes. From my conversations with @bryphe, this seems to be okay, I just have to make sure that Gatekeeper doesn't interfere with CLI flags.
Addresses #1085. Thank you @raguay for bringing this to our attention!

Regarding the command-line-flag that needs to be ported over, it can be a bit tricky to test! That's because, as far as I know, there isn't a very reliable way to set the 'gatekeeper' quarantine flag, reliably.
So the steps I use to test this are:
Setup: Install npm install -g http-server to have it around

Create the _release/Onivim2.app folder via esy create-release
Run ./scripts/osx/package.sh to create a tar.gz in the publish folder
cd _publish
http-server . <-- start a local http server in the publish folder
Go to a web browser, and navigate to http://127.0.0.1:8080/Onivim2-<commitid>-tar.gz
The tar.gz should be downloaded
Extract the tar.gz, and run Onivim 2. When you download a file - even if its locally - the gatekeeper quarantine bit gets set!
Because the app isn't code signed, you'll need to go to Security & Privacy and allow it to open
Try opening again - this time, you'll get a warning, but you'll be able to Open

Expected: Application should start successfully
Actual: You can see icon bounce in the dock, but it fails to start. Starting it again works!
The reason it's failing to start is because its being passed that extra -psn parameter that isn't handled. Some details on when we hit this before: https://github.com/onivim/oni2/issues/552

Looks like this needs an esy format

@bryphe I somehow missed that! Thanks! Will fix now.

authors: bryphe zbaylin


text:
chnage li to show

how change count li to show?

Hi, do you want to change the display number of a column of li?
This feature is not currently supported, but I will add it in future versions based on your suggestions.
I plan to provide an initialization configuration to control the number of li displayed (only odd numbers can be passed in).

Thank you. i found a way to change the quantity using css.
.ms-mobile-select .ms-wheel,
.ms-mobile-select .ms-wheels{
height: 280px;
}
.ms-mobile-select .ms-select-line{
top: 120px
}
.ms-mobile-select .ms-select-container{
margin-top: 40px;
}
it would also be great if the active element had some class for styling.
Thanks again

repo: onlyhom/mobile-select


text:
Bump k8s deps to 1.25

Proposed Changes
Upgrade the Kubernetes dependencies to v1.25.

From looking at the aggregated API server output:
E0826 16:21:50.225716   22384 wrap.go:57] "apiserver panic'd" method="PATCH" URI="/apis/networking.api.onmetal.de/v1alpha1/namespaces/testns-mds5f/virtualips/vip-jhb8p/status" audit-ID="2bf802a9-3c02-4488-bd5c-3c11302b494f"
http2: panic serving 127.0.0.1:49218: an unexported field was encountered, nested like this: *networking.VirtualIP -> networking.VirtualIP -> networking.VirtualIPStatus -> *v1alpha1.IP -> v1alpha1.IP -> netaddr.IP -> netaddr.uint128 -> uint64

Seems like our IP and IPPrefix types in the common package are causing some marshalling issues.

A bit more logging output:
•E0826 16:21:50.177475   22384 runtime.go:77] Observed a panic: an unexported field was encountered, nested like this: *networking.VirtualIP -> networking.VirtualIP -> networking.VirtualIPStatus -> *v1alpha1.IP -> v1alpha1.IP -> netaddr.IP -> netaddr.uint128 -> uint64
goroutine 3505 [running]:
k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest.func1.1()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:105 +0xa0
panic({0x104b20400, 0x14001d07458})
        /usr/local/go/src/runtime/panic.go:884 +0x204
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104dbbe40?, 0x14002ae8160?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07440})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104c65080?, 0x14002ae8160?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07428})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104c06340?, 0x14002ae8290?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07410})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104de0f40?, 0x14002ae8290?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073f8})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104dd00c0?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073e0})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104dcc0e0?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073c8})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104d00bc0?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073b0})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x1049f2440?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07398})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104d00bc0?, {0x1049f2440?, 0x14001d06588?, 0x14000bda330?}, {0x1049f2440?, 0x14001d062a0?, 0x14001c74068?}, 0x102f19c2c?, 0x0, 0x7)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:257 +0x1268
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104dcc0e0?, {0x104d00bc0?, 0x14001d06588?, 0x1?}, {0x104d00bc0?, 0x14001d062a0?, 0x6?}, 0x6?, 0x0, 0x6)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104dd00c0?, {0x104dcc0e0?, 0x14001d06588?, 0x14001c745c8?}, {0x104dcc0e0?, 0x14001d062a0?, 0x14001c744c8?}, 0x102f19c2c?, 0x0, 0x5)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104de0f40?, {0x104dd00c0?, 0x14001d06588?, 0x24548e0?}, {0x104dd00c0?, 0x14001d062a0?, 0x14001c74678?}, 0x1031055f8?, 0x0, 0x4)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104c06340?, {0x104de0f40?, 0x14002ae8290?, 0x1?}, {0x104de0f40?, 0x14002c0fe10?, 0x6?}, 0x6?, 0x0, 0x3)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:203 +0xe9c
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104c65080?, {0x104c06340?, 0x14002ae8290?, 0x14001c74c58?}, {0x104c06340?, 0x14002c0fe10?, 0x14001c74af8?}, 0x1039c1bcc?, 0x0, 0x2)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104dbbe40?, {0x104c65080?, 0x14002ae8160?, 0x0?}, {0x104c65080?, 0x14002c0fce0?, 0x14001c74d98?}, 0x1032e04ac?, 0x0, 0x1)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x0?, {0x104dbbe40?, 0x14002ae8160?, 0x50?}, {0x104dbbe40?, 0x14002c0fce0?, 0x14001c74f68?}, 0x104326dc0?, 0x0, 0x0)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:203 +0xe9c
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepEqual(0x140014d1740?, {0x104dbbe40?, 0x14002ae8160?}, {0x104dbbe40?, 0x14002c0fce0?}, 0xb0?)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:289 +0x2c8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.DeepEqualWithNilDifferentFromEmpty(...)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:277
k8s.io/apiserver/pkg/endpoints/handlers/fieldmanager.IgnoreManagedFieldsTimestampsTransformer({0x104e2fbf8?, 0x1400242d440?}, {0x104e154f0?, 0x14002ae8160}, {0x104e154f0?, 0x14002c0fce0})
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/fieldmanager/equality.go:161 +0x418
k8s.io/apiserver/pkg/registry/rest.(*defaultUpdatedObjectInfo).UpdatedObject(0xf?, {0x104e2fbf8, 0x1400242d440}, {0x104e154f0, 0x14002c0fce0})
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/rest/update.go:228 +0xd4
k8s.io/apiserver/pkg/registry/generic/registry.(*Store).Update.func1({0x104e154f0, 0x14002c0fce0}, {0xc0ba539f8a843ed8?, 0x2ab802783?})
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/generic/registry/store.go:552 +0x15c
k8s.io/apiserver/pkg/storage/etcd3.(*store).updateState(0x140009b4ab0, 0x140017ebe50?, 0x50?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/storage/etcd3/store.go:868 +0x44
k8s.io/apiserver/pkg/storage/etcd3.(*store).GuaranteedUpdate(0x140009b4ab0, {0x104e2fbf8, 0x1400242d440}, {0x14000388240, 0x3c}, {0x104e154f0?, 0x14002c0fb80}, 0x1, 0x5000?, 0x102f1a01c?, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/storage/etcd3/store.go:387 +0x4c8
k8s.io/apiserver/pkg/storage/cacher.(*Cacher).GuaranteedUpdate(0x140009ec300, {0x104e2fbf8, 0x1400242d440}, {0x14000388240, 0x3c}, {0x104e154f0, 0x14002c0fb80}, 0xf0?, 0x14000ad7ce8?, 0x104253980?, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/storage/cacher/cacher.go:721 +0xd4
k8s.io/apiserver/pkg/registry/generic/registry.(*DryRunnableStorage).GuaranteedUpdate(0x140002be3c0?, {0x104e2fbf8?, 0x1400242d440?}, {0x14000388240?, 0x1045083fd?}, {0x104e154f0?, 0x14002c0fb80?}, 0x1?, 0x1044fd749?, 0x2?, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/generic/registry/dryrun.go:93 +0x168
k8s.io/apiserver/pkg/registry/generic/registry.(*Store).Update(0x140002be3c0, {0x104e2fbf8?, 0x1400242d440}, {0x140018e8cac, 0x9}, {0x104e1a310?, 0x1400242d560}, 0x140013b8be0, 0x14001d0e100, 0x0, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/generic/registry/store.go:540 +0x3a0
github.com/onmetal/onmetal-api/registry/networking/virtualip/storage.(*StatusREST).Update(0x1400195f800?, {0x104e2fbf8?, 0x1400242d440?}, {0x140018e8cac?, 0x5000?}, {0x104e1a310?, 0x1400242d560?}, 0x104e2ee68?, 0x14000364fe0?, 0x78?, ...)
        /Users/i820491/SAPDevelop/git/onmetal/onmetal-api/registry/networking/virtualip/storage/storage.go:89 +0x38
k8s.io/apiserver/pkg/endpoints/handlers.(*patcher).patchResource.func2()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/patch.go:672 +0xa4
k8s.io/apiserver/pkg/endpoints/handlers.(*patcher).patchResource.func3()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/patch.go:678 +0x38
k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest.func1()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:117 +0x7c
created by k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:92 +0xb0

goroutine 3504 [running]:
k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP.func1.1()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/timeout.go:109 +0xa8
panic({0x1049f21c0, 0x140020e03d0})
        /usr/local/go/src/runtime/panic.go:884 +0x204
k8s.io/apiserver/pkg/endpoints/handlers/finisher.(*result).Return(0x14001e35640?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:53 +0xf4
k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest({0x104e2fbf8, 0x1400242d440}, 0x14000365260, 0x45d964b800, 0x104e03fe0)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:126 +0x2a4
k8s.io/apiserver/pkg/endpoints/handlers/finisher.FinishRequest(...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:84
k8s.io/apiserver/pkg/endpoints/handlers.(*patcher).patchResource(0x1400072af00, {0x104e2fbf8?, 0x1400242d440}, 0x140014e2340)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/patch.go:676 +0x7fc
k8s.io/apiserver/pkg/endpoints/handlers.PatchResource.func1({0x104e2ee68, 0x140003651c0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/patch.go:232 +0x1d90
k8s.io/apiserver/pkg/endpoints.restfulPatchResource.func1(0x140003651a0, 0x140014dfc70)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/installer.go:1210 +0x70
k8s.io/apiserver/pkg/endpoints/metrics.InstrumentRouteFunc.func1(0x140003651a0, 0x140014dfc70)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/metrics/metrics.go:528 +0x1d8
github.com/emicklei/go-restful/v3.(*Container).dispatch(0x140004ea900, {0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/github.com/emicklei/go-restful/v3@v3.8.0/container.go:299 +0x488
github.com/emicklei/go-restful/v3.(*Container).Dispatch(...)
        /Users/i820491/go/pkg/mod/github.com/emicklei/go-restful/v3@v3.8.0/container.go:204
k8s.io/apiserver/pkg/server.director.ServeHTTP({{0x1045102f5?, 0x1042ba970?}, 0x140004ea900?, 0x140002baee0?}, {0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/handler.go:146 +0x494
k8s.io/apiserver/pkg/endpoints/filterlatency.trackCompleted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:104 +0x150
net/http.HandlerFunc.ServeHTTP(0x104e2fbf8?, {0x104e2ee68?, 0x14000364fe0?}, 0x4?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithAuthorization.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/authorization.go:64 +0x3a4
net/http.HandlerFunc.ServeHTTP(0x14001a0eec8?, {0x104e2ee68?, 0x14000364fe0?}, 0x103fb2ca4?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackStarted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:80 +0x14c
net/http.HandlerFunc.ServeHTTP(0x105ea9060?, {0x104e2ee68?, 0x14000364fe0?}, 0x5?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/server/filters.WithMaxInFlightLimit.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/maxinflight.go:197 +0x23c
net/http.HandlerFunc.ServeHTTP(0x1049f0e00?, {0x104e2ee68?, 0x14000364fe0?}, 0x1042ba88c?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackCompleted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:104 +0x150
net/http.HandlerFunc.ServeHTTP(0x20?, {0x104e2ee68?, 0x14000364fe0?}, 0x46?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithImpersonation.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/impersonation.go:50 +0x1a8
net/http.HandlerFunc.ServeHTTP(0x14000618000?, {0x104e2ee68?, 0x14000364fe0?}, 0x3e7647b771125e49?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackStarted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:80 +0x14c
net/http.HandlerFunc.ServeHTTP(0x1049f0e00?, {0x104e2ee68?, 0x14000364fe0?}, 0x1042ba88c?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackCompleted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:104 +0x150
net/http.HandlerFunc.ServeHTTP(0x14000618000?, {0x104e2ee68?, 0x14000364fe0?}, 0x3f21d4c74ab56382?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackStarted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:80 +0x14c
net/http.HandlerFunc.ServeHTTP(0x1049f0e00?, {0x104e2ee68?, 0x14000364fe0?}, 0x1042ba88c?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackCompleted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:104 +0x150
net/http.HandlerFunc.ServeHTTP(0x104e2fbf8?, {0x104e2ee68?, 0x14000364fe0?}, 0x10486eaf8?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.withAuthentication.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870900)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/authentication.go:80 +0x484
net/http.HandlerFunc.ServeHTTP(0x104e2fbc0?, {0x104e2ee68?, 0x14000364fe0?}, 0x10486ea78?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filterlatency.trackStarted.func1({0x104e2ee68, 0x14000364fe0}, 0x14001870700)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filterlatency/filterlatency.go:89 +0x2c4
net/http.HandlerFunc.ServeHTTP(0x0?, {0x104e2ee68?, 0x14000364fe0?}, 0x104e1dfb0?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP.func1()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/timeout.go:114 +0x68
created by k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/timeout.go:100 +0x198

goroutine 3503 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x1049f21c0?, 0x140020e0410})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/pkg/util/runtime/runtime.go:75 +0x7c
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x14000f3ef50, 0x1, 0x104e0c640?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/pkg/util/runtime/runtime.go:49 +0x78
panic({0x1049f21c0, 0x140020e0410})
        /usr/local/go/src/runtime/panic.go:884 +0x204
k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP(0x1400054b530, {0x104e2ee68, 0x14000364f40}, 0xdf8475800?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/timeout.go:120 +0x2a8
k8s.io/apiserver/pkg/endpoints/filters.withRequestDeadline.func1({0x104e2ee68, 0x14000364f40}, 0x14001870500)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/request_deadline.go:100 +0x298
net/http.HandlerFunc.ServeHTTP(0x106875878?, {0x104e2ee68?, 0x14000364f40?}, 0x140016977d0?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/server/filters.withWaitGroup.func1({0x104e2ee68?, 0x14000364f40}, 0x14001870500)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/waitgroup.go:77 +0x608
net/http.HandlerFunc.ServeHTTP(0x104e2fbf8?, {0x104e2ee68?, 0x14000364f40?}, 0x10486ea78?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithWarningRecorder.func1({0x104e2ee68?, 0x14000364f40}, 0x14001870400)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/warning.go:35 +0x194
net/http.HandlerFunc.ServeHTTP(0x104c5ee60?, {0x104e2ee68?, 0x14000364f40?}, 0xd?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithCacheControl.func1({0x104e2ee68, 0x14000364f40}, 0x100000003?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/cachecontrol.go:31 +0x11c
net/http.HandlerFunc.ServeHTTP(0x0?, {0x104e2ee68?, 0x14000364f40?}, 0x103fa9540?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/server/httplog.withLogging.func1({0x104e2ee68, 0x14000364f40}, 0x14001870400)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/httplog/httplog.go:110 +0x74
net/http.HandlerFunc.ServeHTTP(0x104e30598?, {0x104e2ee68?, 0x14000364f40?}, 0x105efbed8?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithLatencyTrackers.func1({0x104e22478?, 0x1400188f368}, 0x14001870300)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/webhook_duration.go:57 +0x240
net/http.HandlerFunc.ServeHTTP(0x104e2fbf8?, {0x104e22478?, 0x1400188f368?}, 0x10486ea78?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithRequestInfo.func1({0x104e22478, 0x1400188f368}, 0x14001870200)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/requestinfo.go:39 +0x1b8
net/http.HandlerFunc.ServeHTTP(0x104e2fbf8?, {0x104e22478?, 0x1400188f368?}, 0x102f74518?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.withRequestReceivedTimestampWithClock.func1({0x104e22478, 0x1400188f368}, 0x14001870100)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/request_received_time.go:38 +0x13c
net/http.HandlerFunc.ServeHTTP(0x1068745b8?, {0x104e22478?, 0x1400188f368?}, 0x140013c7620?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.WithMuxAndDiscoveryComplete.func1({0x104e22478, 0x1400188f368}, 0x14001870100)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/mux_discovery_complete.go:52 +0x180
net/http.HandlerFunc.ServeHTTP(0x1068745b8?, {0x104e22478?, 0x1400188f368?}, 0x14002c0f8c0?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/server/filters.withPanicRecovery.func1({0x104e22478?, 0x1400188f368?}, 0x140013c7601?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/filters/wrap.go:73 +0x9c
net/http.HandlerFunc.ServeHTTP(0x104c5ee60?, {0x104e22478?, 0x1400188f368?}, 0x8?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/endpoints/filters.withAuditID.func1({0x104e22478, 0x1400188f368}, 0x14001870000)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/filters/with_auditid.go:66 +0x274
net/http.HandlerFunc.ServeHTTP(0x14001404288?, {0x104e22478?, 0x1400188f368?}, 0x1031dd320?)
        /usr/local/go/src/net/http/server.go:2109 +0x38
k8s.io/apiserver/pkg/server.(*APIServerHandler).ServeHTTP(0x0?, {0x104e22478?, 0x1400188f368?}, 0x45c?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/server/handler.go:189 +0x30
net/http.serverHandler.ServeHTTP({0x14001404288?}, {0x104e22478, 0x1400188f368}, 0x14001870000)
        /usr/local/go/src/net/http/server.go:2947 +0x2c4
net/http.initALPNRequest.ServeHTTP({{0x104e2fbf8?, 0x14001251e60?}, 0x140005d9500?, {0x140005fd770?}}, {0x104e22478, 0x1400188f368}, 0x14001870000)
        /usr/local/go/src/net/http/server.go:3556 +0x1f4
golang.org/x/net/http2.(*serverConn).runHandler(0x105efbed8?, 0x0?, 0x0?, 0x14001945fb0?)
        /Users/i820491/go/pkg/mod/golang.org/x/net@v0.0.0-20220722155237-a158d28d115b/http2/server.go:2243 +0x70
created by golang.org/x/net/http2.(*serverConn).processHeaders
        /Users/i820491/go/pkg/mod/golang.org/x/net@v0.0.0-20220722155237-a158d28d115b/http2/server.go:1951 +0x514
E0826 16:21:50.177504   22384 wrap.go:57] "apiserver panic'd" method="PATCH" URI="/apis/networking.api.onmetal.de/v1alpha1/namespaces/testns-mds5f/virtualips/vip-jhb8p/status" audit-ID="5cd8db98-e952-4833-9e05-9dbb60bd9aa2"
http2: panic serving 127.0.0.1:49218: an unexported field was encountered, nested like this: *networking.VirtualIP -> networking.VirtualIP -> networking.VirtualIPStatus -> *v1alpha1.IP -> v1alpha1.IP -> netaddr.IP -> netaddr.uint128 -> uint64
goroutine 3505 [running]:
k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest.func1.1()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:105 +0xa0
panic({0x104b20400, 0x14001d07458})
        /usr/local/go/src/runtime/panic.go:884 +0x204
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104dbbe40?, 0x14002ae8160?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07440})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104c65080?, 0x14002ae8160?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07428})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104c06340?, 0x14002ae8290?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07410})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104de0f40?, 0x14002ae8290?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073f8})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104dd00c0?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073e0})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104dcc0e0?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073c8})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x104d00bc0?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d073b0})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.makeUsefulPanic({0x1049f2440?, 0x14001d06588?, 0x1400157ed00?})
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:96 +0x138
panic({0x104b20400, 0x14001d07398})
        /usr/local/go/src/runtime/panic.go:890 +0x258
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104d00bc0?, {0x1049f2440?, 0x14001d06588?, 0x14000bda330?}, {0x1049f2440?, 0x14001d062a0?, 0x14001c74068?}, 0x102f19c2c?, 0x0, 0x7)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:257 +0x1268
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104dcc0e0?, {0x104d00bc0?, 0x14001d06588?, 0x1?}, {0x104d00bc0?, 0x14001d062a0?, 0x6?}, 0x6?, 0x0, 0x6)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104dd00c0?, {0x104dcc0e0?, 0x14001d06588?, 0x14001c745c8?}, {0x104dcc0e0?, 0x14001d062a0?, 0x14001c744c8?}, 0x102f19c2c?, 0x0, 0x5)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104de0f40?, {0x104dd00c0?, 0x14001d06588?, 0x24548e0?}, {0x104dd00c0?, 0x14001d062a0?, 0x14001c74678?}, 0x1031055f8?, 0x0, 0x4)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104c06340?, {0x104de0f40?, 0x14002ae8290?, 0x1?}, {0x104de0f40?, 0x14002c0fe10?, 0x6?}, 0x6?, 0x0, 0x3)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:203 +0xe9c
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104c65080?, {0x104c06340?, 0x14002ae8290?, 0x14001c74c58?}, {0x104c06340?, 0x14002c0fe10?, 0x14001c74af8?}, 0x1039c1bcc?, 0x0, 0x2)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x104dbbe40?, {0x104c65080?, 0x14002ae8160?, 0x0?}, {0x104c65080?, 0x14002c0fce0?, 0x14001c74d98?}, 0x1032e04ac?, 0x0, 0x1)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:206 +0x12e8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepValueEqual(0x0?, {0x104dbbe40?, 0x14002ae8160?, 0x50?}, {0x104dbbe40?, 0x14002c0fce0?, 0x14001c74f68?}, 0x104326dc0?, 0x0, 0x0)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:203 +0xe9c
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.deepEqual(0x140014d1740?, {0x104dbbe40?, 0x14002ae8160?}, {0x104dbbe40?, 0x14002c0fce0?}, 0xb0?)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:289 +0x2c8
k8s.io/apimachinery/third_party/forked/golang/reflect.Equalities.DeepEqualWithNilDifferentFromEmpty(...)
        /Users/i820491/go/pkg/mod/k8s.io/apimachinery@v0.25.0/third_party/forked/golang/reflect/deep_equal.go:277
k8s.io/apiserver/pkg/endpoints/handlers/fieldmanager.IgnoreManagedFieldsTimestampsTransformer({0x104e2fbf8?, 0x1400242d440?}, {0x104e154f0?, 0x14002ae8160}, {0x104e154f0?, 0x14002c0fce0})
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/fieldmanager/equality.go:161 +0x418
k8s.io/apiserver/pkg/registry/rest.(*defaultUpdatedObjectInfo).UpdatedObject(0xf?, {0x104e2fbf8, 0x1400242d440}, {0x104e154f0, 0x14002c0fce0})
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/rest/update.go:228 +0xd4
k8s.io/apiserver/pkg/registry/generic/registry.(*Store).Update.func1({0x104e154f0, 0x14002c0fce0}, {0xc0ba539f8a843ed8?, 0x2ab802783?})
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/generic/registry/store.go:552 +0x15c
k8s.io/apiserver/pkg/storage/etcd3.(*store).updateState(0x140009b4ab0, 0x140017ebe50?, 0x50?)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/storage/etcd3/store.go:868 +0x44
k8s.io/apiserver/pkg/storage/etcd3.(*store).GuaranteedUpdate(0x140009b4ab0, {0x104e2fbf8, 0x1400242d440}, {0x14000388240, 0x3c}, {0x104e154f0?, 0x14002c0fb80}, 0x1, 0x5000?, 0x102f1a01c?, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/storage/etcd3/store.go:387 +0x4c8
k8s.io/apiserver/pkg/storage/cacher.(*Cacher).GuaranteedUpdate(0x140009ec300, {0x104e2fbf8, 0x1400242d440}, {0x14000388240, 0x3c}, {0x104e154f0, 0x14002c0fb80}, 0xf0?, 0x14000ad7ce8?, 0x104253980?, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/storage/cacher/cacher.go:721 +0xd4
k8s.io/apiserver/pkg/registry/generic/registry.(*DryRunnableStorage).GuaranteedUpdate(0x140002be3c0?, {0x104e2fbf8?, 0x1400242d440?}, {0x14000388240?, 0x1045083fd?}, {0x104e154f0?, 0x14002c0fb80?}, 0x1?, 0x1044fd749?, 0x2?, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/generic/registry/dryrun.go:93 +0x168
k8s.io/apiserver/pkg/registry/generic/registry.(*Store).Update(0x140002be3c0, {0x104e2fbf8?, 0x1400242d440}, {0x140018e8cac, 0x9}, {0x104e1a310?, 0x1400242d560}, 0x140013b8be0, 0x14001d0e100, 0x0, ...)
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/registry/generic/registry/store.go:540 +0x3a0
github.com/onmetal/onmetal-api/registry/networking/virtualip/storage.(*StatusREST).Update(0x1400195f800?, {0x104e2fbf8?, 0x1400242d440?}, {0x140018e8cac?, 0x5000?}, {0x104e1a310?, 0x1400242d560?}, 0x104e2ee68?, 0x14000364fe0?, 0x78?, ...)
        /Users/i820491/SAPDevelop/git/onmetal/onmetal-api/registry/networking/virtualip/storage/storage.go:89 +0x38
k8s.io/apiserver/pkg/endpoints/handlers.(*patcher).patchResource.func2()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/patch.go:672 +0xa4
k8s.io/apiserver/pkg/endpoints/handlers.(*patcher).patchResource.func3()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/patch.go:678 +0x38
k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest.func1()
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:117 +0x7c
created by k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest
        /Users/i820491/go/pkg/mod/k8s.io/apiserver@v0.25.0/pkg/endpoints/handlers/finisher/finisher.go:92 +0xb0

On hold until the issue in Kubernetes is addressed.
/ref https://github.com/kubernetes/kubernetes/issues/112094

Superseded by https://github.com/onmetal/onmetal-api/pull/546

repo: onmetal/onmetal-api


text:
IndexError: list assignment index out of range

🐞Describe the bug
convert onnx to coreml for yolact(with slice, topK ops)
Trace
345/361: Converting Node Type Gather
346/361: Converting Node Type Gather
347/361: Converting Node Type Concat
348/361: Converting Node Type Concat
349/361: Converting Node Type TopK
350/361: Converting Node Type Slice
Traceback (most recent call last):
File "/home/jiapy/workspace/yolact/model_convert.py", line 223, in
add_custom_layers=True,
File "/home/jiapy/virtualEnv/py3.6torch1.2/lib/python3.6/site-packages/onnx_coreml/converter.py", line 626, in convert
_convert_node_nd(builder, node, graph, err)
File "/home/jiapy/virtualEnv/py3.6torch1.2/lib/python3.6/site-packages/onnx_coreml/_operators_nd.py", line 2486, in _convert_node_nd
return converter_fn(builder, node, graph, err)
File "/home/jiapy/virtualEnv/py3.6torch1.2/lib/python3.6/site-packages/onnx_coreml/_operators_nd.py", line 2053, in _convert_slice
return _convert_slice_ir4v9(builder, node, graph, err)  ## comment by jiapy 20200224, replaced by function below
File "/home/jiapy/virtualEnv/py3.6torch1.2/lib/python3.6/site-packages/onnx_coreml/_operators_nd.py", line 1927, in _convert_slice_ir4v9
starts[current_axes] = ip_starts[i]
IndexError: list assignment index out of range
Process finished with exit code 1
To Reproduce

If a python script can reproduce the error, please paste the code snippet

from onnx_coreml import convert
# Paste code snippet here

model_onnx = onnx.load("./yolact_test.onnx")
print('----convert model to onnx success. ')
# output_onnx = model_onnx(input_onnx)
	onnx.checker.check_model(model_onnx)

	# Print a human readable representation of the graph
	# onnx.helper.printable_graph(model.graph)

	print('----convert model to onnx success. 22')

	# add onnx2coreml conversion part, input_names same as onnx'
	coreml_model = onnx_coreml.convert(model_onnx,
									   None,
									   # image_input_names=['image']
									   minimum_ios_deployment_target='13',
									   add_custom_layers=True,
									   # custom_conversion_functions={"Slice": _convert_slice}
									   # disable_coreml_rank5_mapping=True
									   )
	coreml_model.save("./yolact_test.mlmodel")

If applicable, please attach ONNX model

If model cannot be shared publicly, please attach it via filing a bug report at https://developer.apple.com/bug-reporting/

If model conversion succeeds, however, there is numerical mismatch between the original and the coreml model, please paste python script used for comparison (pytorch code, onnx runtime code etc.)

System environment (please complete the following information):

coremltools version  (3.3):
onnx-coreml version (1.2):
OS (Linux):
How you install python ( virtualenv):
python version (e.g. 3.6):
-pytorch 1.2
any other relevant information:

Additional context
error occured after TopK ops

@bhushan23 Do you have some advice for this issue?

@dzyjjpy apologies for delayed response.
What is your ONNX opset version for given model?
according to https://github.com/onnx/onnx/blob/master/docs/Changelog.md#Slice-1 Slice should have one input and in that case slice start and end indices should be present for all given axes, which is the assumption for slice ir v9 variant. If it's opset version 10 then it should have more than one inputs.
Sharing onnx model here would be useful.

repo: onnx/onnx-coreml


text:
Add numerical test for onnx.Scan op

Add numerical test for onnx.Scan op
Currently the execution results and reference answers do not match when the batch size != 2.
We need confirm the reference answers are correct with another way.
TODOs.

[x] Currently the execution results and reference answers do not match, and need confirm the reference answers are correct.
[x] Fix the reference answer or the onnx-mlir implementation to match the outputs and the reference answers.

@AlexandreEichenberger Yes. This PR is ready for review. Thank you.

@jenkins-droid test this please

@jenkins-droid test this please

@jenkins-droid test this please

@jenkins-droid test this please

@jenkins-droid test this please

@jenkins-droid test this please

Jenkins Linux amd64 Build #6785 [push] Add numerical test for o... started at 03:44

Jenkins Linux ppc64le Build #5897 [push] Add numerical test for o... started at 04:45

Jenkins Linux s390x Build #6800 [push] Add numerical test for o... started at 04:44

Jenkins Linux amd64 Build #6785 [push] Add numerical test for o... passed after 1 hr 3 min

Jenkins Linux s390x Build #6800 [push] Add numerical test for o... passed after 1 hr 36 min

Jenkins Linux ppc64le Build #5897 [push] Add numerical test for o... passed after 1 hr 38 min

authors: jenkins-droid negiyas

repo: onnx/onnx-mlir


text:
Update the front-page of http://onnx.ai/onnx-mlir

This patch is to use a different ONNXAI.md file for the front page of http:/onnx.ai/onnx-mlir, instead of use README.md from the GitHub page, which is to avoid confusion because these two files have two different purposes.
Signed-off-by: Tung D. Le tung@jp.ibm.com

@tungld Have you checked that https://github.com/onnx/onnx-mlir/settings/pages which generates the website does take the ONNXAI.md as the main landing page?
My understanding is that it does not, it just build everything using the README.md. So you would need to rename the ONNXAI.md under the doc  as README.md.
Its ok by me to have a different text in the landing page of GitHub vs onnxai

Have you checked that https://github.com/onnx/onnx-mlir/settings/pages which generates the website does take the ONNXAI.md as the main landing page?

I cannot access https://github.com/onnx/onnx-mlir/settings/pages to see configurations. I checked with my local Jekyll server and it works well with github-pages. The point is README.md is used by default to generate index.html. We can change to use ONNXAI.md to generate index.html. Could we merge to see if it works online, if not we can revert the patch?

Jenkins Linux ppc64le Build #1006 [push] Update onnx-ai webpage (... started at 18:00

Jenkins Linux s390x Build #1884 [push] Update onnx-ai webpage (... started at 18:00

Jenkins Linux amd64 Build #1886 [push] Update onnx-ai webpage (... started at 17:00

Looks like it worked. Thanks

Jenkins Linux s390x Build #1884 [push] Update onnx-ai webpage (... passed after 50 min

Jenkins Linux amd64 Build #1886 [push] Update onnx-ai webpage (... passed after 55 min

Jenkins Linux ppc64le Build #1006 [push] Update onnx-ai webpage (... passed after 1 hr 2 min


text:
🛑 2048 game is down

In e23ffce, 2048 game (https://2048.ononoki.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 2048 game is back up in 48fe4cb after 19 minutes.


text:
404 on https://id.openraadsinformatie.nl/

Repro:

Open https://id.openraadsinformatie.nl/
Choose Alkmaar.
URL https://id.openraadsinformatie.nl/42011 raises 404 error.

Dito:
https://id.openraadsinformatie.nl/26871
https://id.openraadsinformatie.nl/72087
https://id.openraadsinformatie.nl/67509

Will be fixed when https://github.com/openstate/open-raadsinformatie/pull/175 is deployed

repo: ontola/ori-search


text:
Make the self-inner-join optimizer introduce IS_NOT_NULL conditions

Currently, the self-inner-join optimizer does not check if by removing some atoms, it also eliminates implicit IS_NOT_NULL conditions that were induced by implicit joining conditions.
For SPARQL-introduced joins, this behaviour usually does not introduce problems because the
IS_NOT_NULL conditions introduced by the mapping are currently kept.
However, in the future, we would probably would like to remove unnecessary IS_NOT_NULLat anytime so we would have to be careful about this.
Also, we may want that an optimization applied to a (join) node does not change the semantics of its sub-tree (that is, independently of its ancestors).

Re-implemented for 4.0.0-beta-2.

repo: ontop/ontop


text:
Fix sass on recent releases name.

I realize that there's an issue if the crate name is too long.
Please let me know if you would like this done differently.
Before:

After:

Thanks! I also made release name column a bit wider.

authors: Nemikolh onur


text:
🛑 Pagure.io is down

In 6ba1938, Pagure.io (https://pagure.io/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pagure.io is back up in c10a854 after 20 minutes.

repo: onuralpszr/uptime


text:
🛑 Fedora Koji is down

In 4758c1b, Fedora Koji (https://koji.fedoraproject.org/koji/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fedora Koji is back up in 8bce302 after 1 hour.


text:
Feature request: Add option to pass customer device identifier during Activate

Need the option to pass a customer device identifier during Activate that can later be used to identify the device (instead of UUID) for all out of band operation calls to API endpoints.

Currently you can use the --hostname flag to pass pretty much anything you want as an identifier, in addition can add tags post activation with the MPS API endpoint for devices as needed. Perhaps we could look at adding a --tags flag on RPC to provide this data during activation instead of post activation?

@matt-primrose says this should work

authors: msbreton rsdmike

repo: open-amt-cloud-toolkit/rpc-go


text:
:bug: Fixing aws-cli image

Summary
Downloading proper awscli exe based on architecture
Related issue(s)
Fixes #https://github.com/open-cluster-management-io/ocm/issues/737

/approve
/lgtm

repo: open-cluster-management-io/ocm


text:
fix header nav on tablet

resolve https://github.com/open-cluster-management-io/open-cluster-management-io.github.io/issues/375

/approve
/lgtm

authors: Arhell mikeshng


text:
re-enable applifecycle steps

Signed-off-by: Mike Ng ming@redhat.com

@mikeshng do we have code ready?

https://github.com/open-cluster-management-io/multicloud-operators-subscription
The described website instructions should be working already. There are still some work needed to be done on the repo for github actions, enhance readme and remove some more vendor specific references. I should be able to get those done by today. Just want the website have the website updated first because of timezone differences. I am ok if you think we should hold this. Thanks.

ok, @xuezhaojun would you like to take a look at this also? We might need some verification test on https://github.com/open-cluster-management-io/multicloud-operators-subscription also.

/lgtm


text:
Fix patternfly select controls

Signed-off-by: James Talton jtalton@redhat.com

Can you please provide some explanation on what this does?

Can you please provide some explanation on what this does?

Fixes missing borders.

/lgtm

authors: KevinFCormier jamestalton

repo: open-cluster-management/console


text:
update addon enquque ns and addon  update message

Signed-off-by: liuwei liuweixa@redhat.com

/assign @qiujian16

/assign @elgnay

/lgtm

/retest

repo: open-cluster-management/registration


text:
Fix logs page refresh bug

Signed-off-by: Zack Layne zlayne@redhat.com
Related Issue:  open-cluster-management/backlog#10166
Description of changes

Added session storage to persist container selection in logs page

/cc @KevinFCormier @RobDolares

/lgtm

authors: KevinFCormier zlayne

repo: open-cluster-management/search-ui


text:
Add observability architecture

fixed: https://github.com/open-cluster-management/backlog/issues/10208
Signed-off-by: clyang82 chuyang@redhat.com

/assign @qiujian16

/approve
/lgtm

repo: open-cluster-management/website


text:
Support for CLI Extensions by OCM Plugins

What this PR does / why we need it:
The OCM Plugin framework now supports two new features:

definition of configuration types (consumed by the plugin)
definition of CLI commands (for the OCM CLI)

Additionally it is possible to consume logging configuration from the OCM CLI for all
plugin feature commands.
Examples see coding in cmds/cliplugin
Config Types
Config types are just registered at the Plugin Object;
	p := ppi.NewPlugin("cliplugin", version.Get().String())
        ...
	p.RegisterConfigType(configType)

The argument is just the config type as registered at the ocm library, for example:
const ConfigType = "rhabarber.config.acme.org"

type Config struct {
	runtime.ObjectVersionedType `json:",inline"`
	...
}

func (a *Config) ApplyTo(ctx cfgcpi.Context, target interface{}) error {
        ...
}

func init() {
	configType = cfgcpi.NewConfigType[*Config](ConfigType, usage)
	cfgcpi.RegisterConfigType(configType)
}

CLI Commands
CLI commands are simple configured cobra.Command objects.
They are registered at the plugin object with
        cmd, err := clicmd.NewCLICommand(NewCommand(), clicmd.WithCLIConfig(), clicmd.WithVerb("check"))
	if err != nil {
		os.Exit(1)
	}
	p.RegisterCommand(NewCommand())

with coding similar to

type command struct {
	date string
}

func NewCommand() *cobra.Command {
	cmd := &command{}
	c := &cobra.Command{
		Use:   Name + " <options>",
		Short: "determine whether we are in rhubarb season",
		Long:  "The rhubarb season is between march and april.",
		RunE:  cmd.Run,
	}

	c.Flags().StringVarP(&cmd.date, "date", "d", "", "the date to ask for (MM/DD)")
	return c
}

func (c *command) Run(cmd *cobra.Command, args []string) error {
   ...
}

The plugin programming interface supports the generation of an extension command directly from a
cobra command object using the method NewCLICommand from the ppi.clicmd package.
Otherwise the ppi.Command interface  can be implemented without requiring a cobra command..
If the code wants to use the config framework, for example to

use the OCM library again
access credentials
get configured with declared config types

the appropriate command feature must be set.
For the cobra support this is implemented by the option WithCLIConfig.
If set to true, the OCM CLI configuration is available for the config context used in the
CLI code.
The command can be a top-level command or attached to a dedicated verb (and optionally a realm like ocmor oci).
For the cobra support this can be requested by the option WithVerb(...).
If the config framework is used just add the following anonymoud import
for an automated configuration:
import (
        // enable mandelsoft plugin logging configuration.
	_ "github.com/open-component-model/ocm/pkg/contexts/ocm/plugin/ppi/config"
)

The plugin code is then configured with the configuration of the OCM CLI and the config  framework
can be used.
If the configuration should be handled by explicit plugin code a handler can be registered with
func init() {
	command.RegisterCommandConfigHandler(yourHandler)
}

It gets a config yaml according to the config objects used by the OCM library.
Logging
To get the logging configuration from the OCM CLI the plugin has be configured with
	p.ForwardLogging()

If the standard mandelsoft logging from the OCM library is used the configuration can
be implemented directly with an anonymous import of
import (
        // enable mandelsoft plugin logging configuration.
	_ "github.com/open-component-model/ocm/pkg/contexts/ocm/plugin/ppi/logging"
)

The plugin code is then configured with the logging configuration of the OCM CLI and the mandelsoft logging frame work
can be used.
If the logging configuration should be handled by explicit plugin code a handler can be registered with
func init() {
	cmds.RegisterLoggingConfigHandler(yourHandler)
}

It gets a logging configuration yaml according to the logging config used by the OCM library (github.com/mandelsoft/logging/config).
Using Plugin command extensions from the OCM library.
The plugin command extensions can also be called without the OCM CLI directly from the OCM library.
Therefore the plugin objects provided by the library can be used.
Logging information and config information must explicitly be configured to be passed to the
plugin.
Therefore the context attribute clicfgattr.Get(ctx) is used. It can be set via clicfgattr.Set(...).
The logging configuration is extracted from the configured configuration object with target type *logging.LoggingConfiguration.
If the code uses an OCM context configured with a (ocm)utils.ConfigureXXX function, the cli config attribute is set accordingly.
Which issue(s) this PR fixes:

Just rebased and fixed the linter issues

repo: open-component-model/ocm


text:
Order of tables in preview

@sorenabell I'm sure I mentioned it in a previous issue that the order of the tables in the Preview Tables section is important. The reason being we want the tables to follow the contracting process, so :Parties, Planning, Tender, Award, Contract, Documents, Milestones, Amendments.
I can still see that the order of the tables appears to depend on the select tables step.

The order was fixed, please check.

The order looks correct for the examples I have tried but I've now started seeing that some of the tables are not appearing. This was not happening before...
The screenshot shows that I have selected all the tables

However when I proceed to the next step, the Planning and Tenders tables are missing:

Please check once more, maybe not all the latest changes were applied.

@sorenabell I've tested with three different files. All working properly! Thank you :)

authors: sabahfromlondon sorenabell

repo: open-contracting/spoonbill-web


text:
Write blogpost about Slack channel being moved

This relates to #267

@iamjessklein where do you want to post this blogpost? I can start a draft in the meantime

https://docs.google.com/document/d/1ftMA5FYzpqo7DD7dQyLEy_Mz526pFlGpIGEpFHKXABs/edit

authors: dmichl iamjessklein

repo: open-design-kit/opendesignkit


text:
Add sortablity to the Grocery List

Extend ListItems to hold and render a list of items that will slide.
Add sorting function to sort the list after a user has sorted an
element, and send that to the API, so that the whole list can
be updated with the new order in the DB.
When adding a new item, add an order index to it so that it will end up
at the end of the list (like the default behaviour from before), and
send that to the API so that it will stay there if the page is
refreshed.
Add a handle to the ListItem to grab for sorting. It's a bit buggy on
mobile interfaces right now.
Make the sorting handle not display when on a tab other than "All
Items". Sorting only part of the list would be someone of an undefined
function, so we just won't allow it.
Rework the CSS layout so that the destroy button correctly flexes around
the sorting handle.
This CSS rework means we can cleanup a bunch of the margin and absolute
distance hacks to allow for much simpler floating of objects vertically
center and margin distances from each other.
Also fix editing box being a fixed width, now it fits the list size,
while still having a left buffer so that the text lines up with other
lines.
API PR: open-eats/openeats-api#34

Pull Request Test Coverage Report for Build 350

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 61.217%

Totals

Change from base Build 347:
0.0%

Covered Lines:
115

Relevant Lines:
161

💛  - Coveralls

I really like the idea. Thanks for the PR! I've tested it out and everything seems to work quite well. The only thing I noticed was there was some flickering when you change the position of the items. One thing I think would be nice to have is optimistic updates on the order change.

I agree. The two issues left standing as I see them:

Flickering after reorder.
Doesn't work with touch events.

The flickering is because I couldn't figure out how to update the current app state after the user finishes dragging. I only knew how to update the state once the API responded. Obviously should be added, but I'm not totally sure how.
The mobile touch events are quite strange. The drag library is supposed to work with them, but for some reason it doesn't receive the touchDrag events, and the floating item stays forever. It looks very weird on a mobile device if you scroll the page after letting go.
Unfortunately, I am no React dev, so I'm a little past my comfort zone. I was hoping you would know where to point me, but otherwise I'll probably try hacking on it again soon.

I have merged your commit, as well as changed the name of that CSS class. I tested it, and it all works great now. Thanks so much for your help!

authors: RyanNoelk Rycieos coveralls

repo: open-eats/openeats-web


text:
fix: Remove upper-bound version constraint from SCI

Fixes: #170
See: #136, #137, #170

Anticipate similar arguments/discussion as in #137, but opening as a companion to #170 because this is causing me real-world grief today 🙃

No idea why the code coverage report is failing...
At any rate, I'll add the people from the referenced thread.

@kinyoklion Has you opinion on this changed at all since #170 ?

Bumping because this is unfortunately causing an increasing amount of developer friction inside my org.
Including this package breaks our in-house source generators when invoked by IDE-triggered design-time builds in such a way that my normally strong msbuild-foo has thus far been unable to combat.
I would like to get some movement on this today, otherwise I'm looking at needing to publish a forked package to appease a growing horde of angered devs. (This is, of course, a me problem, so I don't mention it to force a decision one way or the other, just to say that it would be nice to hear from folks on whether this is a quick action or something I need to self-serve for the foreseeable future.)
/cc @toddbaert @kinyoklion

Can someone catch me up on why we're going out of our way to set upper-bound constraints in the first place?
Originally, I assumed it was something specific about System.Collections.Immutable that we were depending on (e.g. internal impl details, sketchy reflection, etc.), but now noticing that we do this in a bunch of places, so wondering if this is just an artifact of someone's repo template, or if there's some bigger concern that I'm missing 🤔

I think it was just out of fear of breaking changes in further releases of these dependencies, but I think I'm on board with just removing the upper bounds.

@austindrenski I've removed the upper bound on System.Threading.Channels as well.

authors: austindrenski beeme1mr toddbaert

repo: open-feature/dotnet-sdk


text:
fix: Improve error handling in OpenFeatureClient

This PR
The PR adds the flagKey to EvaluationDetailsBuilder during error handling, providing more context for debugging. It also includes error message within the ResolutionError for more complete error information.
How to test
Modify the NoOpProvider to throw any exception with a message. This should then propergate through to this new error handling

The failures above I don't think are related to my commit above. Not sure how you'd like me to approach resolving that?

@tcarrio do you know what phpstan is failing?

@tcarrio do you know what phpstan is failing?

I can happily fix this as part of this commit? I just need to remove those 3 phpstan ignore declarations.

I'll investigate the phpstan error
In the meantime @schodemeiss could you add or update tests around this? I love the idea of including more exception context in the error. This is a good improvement overall 👍

For both PRs, your commits need to be signed off for the DCO.

If you end up fixing the phpstan error yourself I'll definitely approve that to merge. I have a bigger PR coming down the pipeline that resolved this in #122. You could reference that if necessary. I'll fix in merge conflicts on my end if yours is ready first 😎

I noticed that all the tests in OpenFeatureClientTest are all based on the OpenFeature specification requirements. To test this exception handling, should I pop a test into that file? Or make a new test case specifically for this?

Rebasing now that main has your phpstan fixes

LGTM! Merging ✅

authors: beeme1mr schodemeiss tcarrio

repo: open-feature/php-sdk


text:
下载代码首次构建时，无法获取依赖

Dependency 'org.hzero.starter:hzero-starter-parent:1.5.6' not found
Dependency 'org.hzero.starter:hzero-starter-apollo-config:1.5.6' not found
。。。

编译
开源的HZERO源码若要使用需要进行本地编译打包或上传到私人的maven仓库

本地编译打包

执行hzero-service目录下的install.bat或者install.sh脚本

上传到私人仓库

在hzero-service/pom.xml文件中添加仓库声明
<distributionManagement>
    <repository>
        <id>{Repository Id}</id>
        <name>{Repository Name}</name>
        <url>{Repository Url}</url>
    </repository>
</distributionManagement>

修改hzero-service目录下的install.bat或者install.sh脚本，添加deploy，例如：
mvn clean install -Dmaven.springboot.skip=true -Dmaven.test.skip=true -Dfile.encoding=UTF-8
->
mvn clean install deploy -Dmaven.springboot.skip=true -Dmaven.test.skip=true -Dfile.encoding=UTF-8

再执行脚本

repo: open-hand/hzero


text:
Unable to install using NPM

I am finding the following issue when trying to use NPM to install your library.
pi@raspberrypi:~/.node-red $ npm i https://github.com/open-homeautomation/miflora
npm ERR! addLocal Could not install /tmp/npm-3174-cbd0c9a8/git-cache-e9fd0e4fcfcf/3575b30e3b4e06d460a1088a8b96999dd328cbed
npm ERR! Linux 4.4.50-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "i" "https://github.com/open-homeautomation/miflora"
npm ERR! node v4.8.2
npm ERR! npm  v2.15.11
npm ERR! code EISDIR
npm ERR! errno -21
npm ERR! syscall read
npm ERR! eisdir EISDIR: illegal operation on a directory, read
npm ERR! eisdir This is most likely not a problem with npm itself
npm ERR! eisdir and is related to npm not being able to find a package.json in
npm ERR! eisdir a package you are trying to install.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/.node-red/npm-debug.log
I've checked the log and it seems to be a carbon copy of what is written above.  I'm a bit of a noob with a lot of this so I could really do with a little help!
Please forgive me if I am pointing out an issue that is already raised or resolved elsewhere.

npm is a JavaScript package mager but this is a Python library. You can't use this with JavaScript.

authors: alandonegan open-homeautomation

repo: open-homeautomation/miflora


text:
Lineage View Issue

Affected module
The impact is on the visualisation of the lineage
Describe the bug
The impact is on the display of the lineage, when collapsing or expanding a child of the lineage.
It appears in many lineages of different assets, we see that it appears with complex lineages, with simple ones we have not seen the error reproduced.
For example this is a lineage that looks like this when you open it:

To Reproduce
For example, collapse here.

If I continuing to collapse

Some screenshots sent by our users:

Expected behavior
It always occurs in the same entities, it is easily reproducible.
Version:

OpenMetadata version: 1.3.1

Thanks,
Carlos Sanz

@triquinielas - hey this happens if the reindexing hasn't happened correctly.
Can you reindex and try reproducing ?

@triquinielas we'll close as we have not heard back from you. Please re open it if you are still seeing the issue after proceeding with the steps @karanh37 has defined.

authors: TeddyCr karanh37 triquinielas

repo: open-metadata/OpenMetadata


text:
Make it easier for users to find DBT docs

Create a DBT page in the connector docs that directs users to DBT configuration with the relevant connector procedure.
Link to the DBT page from the introduction page.
Direct users to DBT configuration with the relevant connector procedure from the Lineage > DBT feature docs page.

Fixed.


text:
Fixes #2942 - Fix bugs reported by Sonar issue on release 0.9

Describe your changes :

See #2942 for more details

Type of change :

[x] Bug fix

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[x] I have tagged my reviewers below.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

SonarCloud issues are unrelated to this patch.


text:
[Bug] Exception when calcute train time

推荐使用英语模板 Bug report，以便你的问题帮助更多人。
描述 bug
统计训练时间时，抛出异常“AttributeError: 'Namespace' object has no attribute 'window_size'”
复现流程
在命令行中执行的详细操作
python tools/analysis_tools/analyze_logs.py cal_train_time work_dirs/some_exp/20200422_153324.log.json

相关信息

pip list | grep "mmcv\|mmcls\|^torch" 命令的输出
mmcls                         0.19.0              /home/damon/open-mmlab/mmclassification-v0.19.0
mmcv-full                     1.4.3
torch                         1.10.1
torchvision                   0.11.2

如果你修改了，或者使用了新的配置文件，请在这里写明

[填写这里]

如果你是在训练过程中遇到的问题，请填写完整的训练日志和报错信息
[填写这里]
如果你对 mmcls 文件夹下的代码做了其他相关的修改，请在这里写明
[填写这里]

附加内容
任何其他有关该 bug 的信息、截图等
[填写这里]

Thank you for your report and contribution,  we have noticed your PR. Please sign the CLA so that we can merge that.

Fix in #662

authors: Ezra-Yu xiefeifeihu

repo: open-mmlab/mmclassification


text:
ORM query helpers

Move base classes to a new base.py module
Add query{_test}.py for defining ORM queries with fewer explicit joins

I'm reworking the mappers to use programmatic class definitions and single-table inheritance; closing this for now since it will mostly be obsolete.

repo: open-reaction-database/ord-schema


text:
Bug: when a new Insight page is created user gets redirected to Hub instead of page

Describe the bug
Essentially the title. If I create a new inisght page, instead of getting redirected to the new page, I get redirected to the Insights hub.
Redirecting users to the page the've just created would be a much better experience.
Here's a screencap of the current flow:

Steps to reproduce

Go to the Insights Hub
Click on "Add Insight Page"
Fill out name + add repos
Click on "Create Page"
Get redirected to Hub instead of new page

Browsers
No response
Additional context (Is this in dev or production?)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[X] I agree to follow this project's Contribution Docs

I'll reassign this to myself to help with bandwidth here

repo: open-sauced/app


text:
Feature: Camelcase Javascript to JavaScript

Type of feature
🍕 Feature
Current behavior
This is not a priority but wanted to add this to the Papercut backlog.
Places we need this applied,

Interests in profiles
Interests in profile settings
Insights explore dashboard

Suggested solution
We have a solution in the hot repo for this, but we would need to sanitize content coming from the GitHub API. I believe everything is lowercase.
https://github.com/open-sauced/hot/blob/beta/src/lib/camelCaseToTitleCase.ts
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

can i work on this?

Sure :grinning: , feel free to drop any questions you have :pizza:

authors: TAKANOME-DEV bdougie dev-phantom

repo: open-sauced/insights


text:
setup automation for image build on release

setup automation for image build on release
Signed-off-by: Harshad Reddy Nalla hnalla@redhat.com
Details:

This would set image build automatically on releases.
PR images can also be built.

Reference:
https://quay.io/repository/open-services-group/peribolos-as-service?tab=tags

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from harshad16 after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

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

Needs approval from an approver in each of these files:

OWNERS [tumido]

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


text:
Exception during during install of OpenTelemetry::Instrumentation::ActiveRecord

Description of the bug
We are getting the following exception when booting up a Rails application:
E, [2024-08-19T11:08:47.064333 #45] ERROR -- : OpenTelemetry error: Instrumentation: OpenTelemetry::Instrumentation::ActiveRecord unhandled exception during install: ["/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-instrumentation-active_record-0.7.3/lib/opentelemetry/instrumentation/active_record/instrumentation.rb:45:in `patch_activerecord'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-instrumentation-active_record-0.7.3/lib/opentelemetry/instrumentation/active_record/instrumentation.rb:16:in `block in <class:Instrumentation>'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-instrumentation-base-0.22.6/lib/opentelemetry/instrumentation/base.rb:222:in `instance_exec'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-instrumentation-base-0.22.6/lib/opentelemetry/instrumentation/base.rb:222:in `install'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-registry-0.3.1/lib/opentelemetry/instrumentation/registry.rb:80:in `install_instrumentation'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-registry-0.3.1/lib/opentelemetry/instrumentation/registry.rb:51:in `block (2 levels) in install'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-registry-0.3.1/lib/opentelemetry/instrumentation/registry.rb:46:in `each'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-registry-0.3.1/lib/opentelemetry/instrumentation/registry.rb:46:in `block in install'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-registry-0.3.1/lib/opentelemetry/instrumentation/registry.rb:45:in `synchronize'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-registry-0.3.1/lib/opentelemetry/instrumentation/registry.rb:45:in `install'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-sdk-1.5.0/lib/opentelemetry/sdk/configurator.rb:164:in `install_instrumentation'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-sdk-1.5.0/lib/opentelemetry/sdk/configurator.rb:145:in `configure'", "/app/vendor/bundle/ruby/3.3.0/gems/opentelemetry-sdk-1.5.0/lib/opentelemetry/sdk.rb:66:in `configure'", "/app/config/initializers/opentelemetry.rb:8:in `<top (required)>'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:690:in `load'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:690:in `block in load_config_initializer'", "/app/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.3.4/lib/active_support/notifications.rb:208:in `instrument'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:689:in `load_config_initializer'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:643:in `block (2 levels) in <class:Engine>'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:642:in `each'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:642:in `block in <class:Engine>'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:32:in `instance_exec'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:32:in `run'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:61:in `block in run_initializers'", "/usr/local/lib/ruby/3.3.0/tsort.rb:231:in `block in tsort_each'", "/usr/local/lib/ruby/3.3.0/tsort.rb:353:in `block (2 levels) in each_strongly_connected_component'", "/usr/local/lib/ruby/3.3.0/tsort.rb:425:in `block (2 levels) in each_strongly_connected_component_from'", "/usr/local/lib/ruby/3.3.0/tsort.rb:434:in `each_strongly_connected_component_from'", "/usr/local/lib/ruby/3.3.0/tsort.rb:424:in `block in each_strongly_connected_component_from'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:50:in `each'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:50:in `tsort_each_child'", "/usr/local/lib/ruby/3.3.0/tsort.rb:418:in `call'", "/usr/local/lib/ruby/3.3.0/tsort.rb:418:in `each_strongly_connected_component_from'", "/usr/local/lib/ruby/3.3.0/tsort.rb:352:in `block in each_strongly_connected_component'", "/usr/local/lib/ruby/3.3.0/tsort.rb:350:in `each'", "/usr/local/lib/ruby/3.3.0/tsort.rb:350:in `call'", "/usr/local/lib/ruby/3.3.0/tsort.rb:350:in `each_strongly_connected_component'", "/usr/local/lib/ruby/3.3.0/tsort.rb:229:in `tsort_each'", "/usr/local/lib/ruby/3.3.0/tsort.rb:208:in `tsort_each'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:60:in `run_initializers'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/application.rb:426:in `initialize!'", "/app/config/environment.rb:5:in `<top (required)>'", "/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `require'", "/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'", "/app/vendor/bundle/ruby/3.3.0/gems/zeitwerk-2.6.17/lib/zeitwerk/kernel.rb:34:in `require'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/application.rb:402:in `require_environment!'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/command/actions.rb:20:in `boot_application!'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/commands/console/console_command.rb:105:in `perform'", "/app/vendor/bundle/ruby/3.3.0/gems/thor-1.3.1/lib/thor/command.rb:28:in `run'", "/app/vendor/bundle/ruby/3.3.0/gems/thor-1.3.1/lib/thor/invocation.rb:127:in `invoke_command'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/command/base.rb:178:in `invoke_command'", "/app/vendor/bundle/ruby/3.3.0/gems/thor-1.3.1/lib/thor.rb:527:in `dispatch'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/command/base.rb:73:in `perform'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/command.rb:71:in `block in invoke'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/command.rb:149:in `with_argv'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/command.rb:69:in `invoke'", "/app/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/commands.rb:18:in `<top (required)>'", "/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `require'", "/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'", "/app/bin/rails:4:in `<main>'"] - undefined method `on_load' for module OpenTelemetry::Instrumentation::ActiveSupport

I posted the entire exception for context, but the relevant fragment is this one at the end:
undefined method `on_load' for module OpenTelemetry::Instrumentation::ActiveSupport

Share details about your runtime
Operating system details: Debian 11 Slim "Bullseye"
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.3.4"
RUBY_DESCRIPTION: "ruby 3.3.4 (2024-07-09 revision be1089c8ec) [x86_64-linux]"
Share a simplified reproduction if possible
It's hard to give a standalone repro but I think the issue is the scoping of ActiveSupport.on_load here. Shouldn't it be ::ActiveSupport?

Cc: @bensheldon

Fixed by https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/1123

Thank you for reporting this issue. The latest release should contain a fix for this issue:
https://github.com/open-telemetry/opentelemetry-ruby-contrib/releases/tag/opentelemetry-instrumentation-active_record%2Fv0.7.4

authors: arielvalentin fcbr


text:
docs: Add example and development guide

Closes #110
Context
In the SIG meeting earlier this week we talked about how it would be helpful to be able to test the sandbox work happening in a browser app. This PR sets up an examples directory with a running browser app that links to local packages to make development easier. Also included some instructions for a development workflow.
Changes

Added a basic browser example that uses the document-load instrumentation from the local package.
Added CONTRIBUTING.md outlining a basic development workflow guide.

Not sure if this should be merged into main so I opened this against the auto-instrumentation-poc branch for now.

Might I request a reference and basic explanation on how to disable Zone.js monkey patching currently found here?
https://github.com/angular/angular/blob/main/packages/zone.js/MODULE.md

Might I request a reference and basic explanation on how to disable Zone.js monkey patching currently found here?
https://github.com/angular/angular/blob/main/packages/zone.js/MODULE.md

@jpettit this is an example that is going into the sandbox repo for development purposes. If you would like an explanation / to extend an existing example, I suggest creating an issue in the opentelemetry-js repo or asking about it in the CNCF Slack group.

Closing this PR for now since we have other web examples, will open another PR with development docs

authors: jpettit pkanal


text:
Clarification on docs for adding attributes via decorators

In the documentation at following link:
https://opentelemetry.io/docs/languages/python/instrumentation/#creating-spans-with-decorators
It's mentioned that If you need to add attributes, events, or links then it’s less convenient to use a decorator.

IMO, this sounds a bit misleading statement especially in case of attributes and links, as the user would interpret accordingly and ignore the possibility of configuring the same via decorator.
For ref., PFB Screenshot for adding attributes and this is certainly not inconvenient.

This is because both attributes and links are arguments of  start_as_current_span method.

Hence, it would be helpful to know on the definition of "less convenient" here, or else we can update the documentation accordingly :)

Inconvenience is in eye of the beholder :) As a non-native english speaker I understand as if you have many attributes the decorator would not have that much advantage over adding the span attributes manually.

You understand that but other readers may understand something else.
Being objective, the statement being discussed says that using a decorator is less convenient for a particular purpose. That statement is subjective, I think we should remove it.

FWIW, as the original author of that section, what I was referring to is that if you need to add these things (especially after span creation) then you need to also make a call to get the current span, since there's no implicit span variable available. That makes it more code than if you create the span yourself.
However, after re-reading this about two years later, I think it's fine to drop it.

I actually disagree with this issue. I think if this was in the documentation it would have saved me some time today as a new user if the library

authors: cartermp heyitsaamir ocelotl sushaanttb


text:
putOperationClientDetailedLoggingIsOn , getOperationClientDetailedLoggingIsOn uuid path parameter pattern require a change

For the OAM service to get and put the attribute detailed-logging-is-on ,
As per the uuid pattern defined in specification , APISegment is “bm” . But , as per the config file and the description for the attribute /v1/redirect-service-request-information/service-log-operation , APISegment is “bs”.
Proposal :
For the APIs getOperationClientDetailedLoggingIsOn and putOperationClientDetailedLoggingIsOn , path/uuid pattern needs to be changed from
pattern: '^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bm-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$'
to
pattern: '^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bs-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$'
Impact :
In the server , express framework rejects the request while validating the uuid pattern.
is workaround available ?
Yes.
This shall be tweaked in the api/openapi.yaml file of the server side code.
putOperationClientDetailedLoggingIsOn : The uuid path parameter defined in this need to change the
from pattern: "^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bm-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$"
to pattern: "^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bs-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$"
getOperationClientDetailedLoggingIsOn : The uuid path parameter defined in this need to change the
from pattern: "^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bm-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$"
to pattern: "^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bs-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$"

Check changing the pattern from
pattern: '^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bm-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$'
to
pattern: '^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-c-bs-([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{3})$'

authors: PrathibaJee openBackhaul

repo: openBackhaul/ApplicationPattern


text:
Deleting unsupported performance attributes

It is proposed to remove a couple of performance values, which are not supported by any hardware we had under test so far.
Proposal:
The following attribute to be deleted from the modeling:

MacInterfacePerformanceType::mac-control-frames-ingress
MacInterfacePerformanceType::mac-pause-frames-ingress
MacInterfacePerformanceType::tagged-frames-ingress
MacInterfacePerformanceType::mac-control-frames-egress
MacInterfacePerformanceType::mac-pause-frames-egress
MacInterfacePerformanceType::tagged-frames-egress

Decision at the 5G-xhaul call on Tuesday 2nd of September 2020:
The following attribute shall be deleted from the modeling:
MacInterfacePerformanceType::mac-control-frames-ingress
MacInterfacePerformanceType::mac-pause-frames-ingress
MacInterfacePerformanceType::tagged-frames-ingress
MacInterfacePerformanceType::mac-control-frames-egress
MacInterfacePerformanceType::mac-pause-frames-egress
MacInterfacePerformanceType::tagged-frames-egress
Updating UML and YANG required.

Has been solved with MacInterface_1.0.0-tsp.220314.1200.

repo: openBackhaul/macInterface


text:
🛑 Server is down

In 34667ae, Server ($SERVER_SITE_GET_ENDPOINT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Server is back up in eb41e80 after 23 minutes.

repo: openCONTRABASS/upptime-server