Plugin dont work after update netbox to 2.9.1

Environment
Python version:  3.6.8
NetBox version:  2.9.1
vCenter version:  6.7.0 -->

vCenter NetBox Sync version:

Steps to Reproduce

After run plugin  i see

[root@netbox]# /bin/python3.6 /opt/vcenter-netbox-sync/run.py >/var/log/vcentersync.log
2020-08-23 15:56:17,690 [INFO] Created new HTTP Session for NetBox.
2020-08-23 15:56:17,785 [INFO] Detected NetBox API v2.9.
2020-08-23 15:56:17,786 [INFO] Verifying all prerequisite objects exist in NetBox.
2020-08-23 15:56:17,838 [INFO] NetBox manufacturers object 'VMware' match current values. Moving on.
2020-08-23 15:56:17,866 [INFO] NetBox platforms object 'VMware ESXi' match current values. Moving on.
2020-08-23 15:56:17,895 [INFO] NetBox platforms object 'Windows' match current values. Moving on.
2020-08-23 15:56:17,919 [INFO] NetBox platforms object 'Linux' match current values. Moving on.
2020-08-23 15:56:18,032 [INFO] NetBox sites object 'vCenter' do not match current values.
Traceback (most recent call last):
File "/opt/vcenter-netbox-sync/run.py", line 1601, in
main()
File "/opt/vcenter-netbox-sync/run.py", line 244, in main
nb.verify_dependencies()
File "/opt/vcenter-netbox-sync/run.py", line 1540, in verify_dependencies
self.obj_exists(nb_obj_type=dep_type, vc_data=dep)
File "/opt/vcenter-netbox-sync/run.py", line 1105, in obj_exists
set(vc_data["tags"] + nb_data["tags"])
TypeError: unhashable type: 'dict'

Expected Behavior

Observed Behavior

Same here, even after a cleanup, collect seem to work and stop with unexpected behavior.
also it seem not working properly with vcenter/esxi 7.0 which have been updated on API level.

Probably related to https://github.com/netbox-community/netbox/issues/3703
Can you paste a debug run log + results of GET /api/dcim/sites/?name=vCenter?

2020-08-24 10:00:02,237 [INFO] Verifying all prerequisite objects exist in NetBox.
2020-08-24 10:00:02,268 [INFO] NetBox manufacturers object 'VMware' match current values. Moving on.
2020-08-24 10:00:02,304 [INFO] NetBox platforms object 'VMware ESXi' match current values. Moving on.
2020-08-24 10:00:02,329 [INFO] NetBox platforms object 'Windows' match current values. Moving on.
2020-08-24 10:00:02,358 [INFO] NetBox platforms object 'Linux' match current values. Moving on.
2020-08-24 10:00:02,426 [INFO] NetBox sites object 'vCenter' do not match current values.
2020-08-24 12:00:01,821 [INFO] Created new HTTP Session for NetBox.
2020-08-24 12:00:01,866 [INFO] Detected NetBox API v2.9.
2020-08-24 12:00:01,868 [INFO] Verifying all prerequisite objects exist in NetBox.
2020-08-24 12:00:01,898 [INFO] NetBox manufacturers object 'VMware' match current values. Moving on.
2020-08-24 12:00:01,932 [INFO] NetBox platforms object 'VMware ESXi' match current values. Moving on.
2020-08-24 12:00:01,969 [INFO] NetBox platforms object 'Windows' match current values. Moving on.
2020-08-24 12:00:01,999 [INFO] NetBox platforms object 'Linux' match current values. Moving on.
2020-08-24 12:00:02,069 [INFO] NetBox sites object 'vCenter' do not match current values.
`HTTP 200 OK
Allow: GET, POST, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept
{
"count": 1,
"next": null,
"previous": null,
"results": [
{
"id": 12,
"url": "http://netbox..com/api/dcim/sites/12/",
"name": "vCenter",
"slug": "vcenter",
"status": {
"value": "active",
"label": "Active"
},
"region": null,
"tenant": null,
"facility": "",
"asn": null,
"time_zone": null,
"description": "",
"physical_address": "",
"shipping_address": "",
"latitude": null,
"longitude": null,
"contact_name": "",
"contact_phone": "",
"contact_email": "",
"comments": "A default virtual site created to house objects that have been synced from vCenter.",
"tags": [
{
"id": 10,
"url": "http://netbox..com/api/extras/tags/10/",
"name": "Synced",
"slug": "synced",
"color": "9e9e9e"
},
{
"id": 9,
"url": "http://netbox.**.com/api/extras/tags/9/",
"name": "vCenter",
"slug": "vcenter",
"color": "9e9e9e"
}
],
"custom_fields": {},
"created": "2020-05-13",
"last_updated": "2020-05-13T20:34:40.272068+03:00",
"circuit_count": null,
"device_count": null,
"prefix_count": null,
"rack_count": null,
"virtualmachine_count": null,
"vlan_count": null
}
]
}`

Yes so this script is incompatible with Netbox >= 2.9.0 due to changes in the way tags are created.
Best to stay on 2.8 until a PR is submitted by someone with the necessary changes.

@synackray  can you help ?

Not just the tags, but also the API changes in 2.9.0 for ipam.IPAddress cause the mapping between IP & virtual-machine to not work anymore.

ipam.IPAddress: Removed interface field; replaced with assigned_object generic foreign key. This may represent either a device interface or a virtual machine interface. Assign an object by setting assigned_object_type and assigned_object_id.

this will fix the tag issue: https://github.com/bb-Ricardo/vcenter-netbox-sync/commit/2d3052fd14bc3947b24e1da3927e93e4e44b6355
Will have a look at ip ipam/ipaddress next week.

Well, we got some progress: https://github.com/bb-Ricardo/vcenter-netbox-sync/commit/9447109a12e18703954cd843c7bc2a6adb936285
Now all my items sync again as before.
Please check it out. All changes are also in #132

I have a problem after updating the plug-in, all virtual servers were transferred to Standalone ESXi Host, they were previously synchronized with their server, for example, if the virtual machine is on the <IP_ADDRESS> server, then in the Cluster it will also be synchronized there. Now all VMs are in Standalone ESXi Host.

also, as you can see in the screenshot, some virtual servers are in their clusters, but the main part has moved to Standalone

That's very interesting as I didn't touch this part of code: https://github.com/bb-Ricardo/vcenter-netbox-sync/blame/9447109a12e18703954cd843c7bc2a6adb936285/run.py#L557
"Standalone ESXi Host" is used if the hosts cluster name is the same as the hosts name:
                    cluster = obj.parent.name
                    # We throw the cluster away if it matches the ESXi host
                    # name as it is standalone.
                    if cluster == obj_name:
                        # Store the host so that we can check VMs against it
                        self.standalone_hosts.append(cluster)
                        cluster = "Standalone ESXi Host"

and Line: https://github.com/bb-Ricardo/vcenter-netbox-sync/blob/develop/run.py#L647
                elif vc_obj_type == "virtual_machines":
                    # Virtual Machines
                    log.debug(
                        "Collecting info for virtual machine '%s'", obj_name
                        )
                    # Cluster
                    cluster = obj.runtime.host.parent.name
                    if cluster in self.standalone_hosts:
                        log.debug(
                            "VM is assigned to a standalone ESXi host. Setting "
                            "cluster to 'Standalone ESXi Host'."
                            )
                        cluster = "Standalone ESXi Host"

In my opinion the whole sync needs a complete rewrite. Unfortunately this code is only used in a test environment. It was a POC and after the last NetBox API FU I'm not sure if I'm willing to spend my time on changing code and adapting APIs every time a new NetBox major release is issued.
I have loads of ideas but (https://github.com/bb-Ricardo/vcenter-netbox-sync/issues) but not sure if time allows it.

@bb-Ricardo I keep getting errors like this: [DEBUG] NetBox 400 status reason: {"tags":[["Related objects must be referenced by numeric ID or by dictionary of attributes. Received an unrecognized value: Synced"],["Related objects must be referenced by numeric ID or by dictionary of attributes. Received an unrecognized value: vCenter"]]}
I am on your develop branch

You're on NetBox version 2.9.X?

I am on 2.9.4

@MarcSN311 Not sure if it the exact same problem I ran into, but I had to delete the vCenter and Synced tag before running it.
I am running 2.9.4

I am on a fresh install, I did not have any tags before running the sync.

@fjasboka
do you have a problem with clusters? like mine https://github.com/synackray/vcenter-netbox-sync/issues/129#issuecomment-698996038
or don't you use them?

@SerhiiZahuba I did not run into that issue. It placed all the VMs in the correct cluster and also the ESXi servers.

Strange, I don’t understand what I’m doing wrong. All my virtual machines are migrated to the Standalone ESXi Host section.

@bb-Ricardo I keep getting errors like this: [DEBUG] NetBox 400 status reason: {"tags":[["Related objects must be referenced by numeric ID or by dictionary of attributes. Received an unrecognized value: Synced"],["Related objects must be referenced by numeric ID or by dictionary of attributes. Received an unrecognized value: vCenter"]]}
I am on your develop branch

Any progress on this issue?

currently trying to rewrite this whole process.
Hope I get all of this covered in here: https://github.com/bb-Ricardo/netbox-sync

I went down a rabbit hole and finally can see the light at the end of the tunnel again. This took way longer then expected (as usual).
Here you go: https://github.com/bb-Ricardo/netbox-sync
please test as much as you can: Debug logs are very welcome.

Just gave it a first try and looks very promising! Only thing I've noticed so far is my vlans in vmware are named "123-name-<IP_ADDRESS>/24" and they get imported into netbox with the url encoded %2f instead of a /

Great to hear.
Can you please open an issue for that. Would like to have a look at it.
Thank you.


[W5.8B][T09-A4]Deborah Low

Update developer guide, add non-functional requirements

@deborahlow97
Some comments added. Please close the PR after reading comments.


Prepare 'Production' Spec list

For ITSS venture, we'll need a production ready list for the infrastructure, depending on what the customer requires
For internal use - list can be found here: https://docs.google.com/document/d/17te-QA4ho7TjW0U-sY1XmLNCd6ItWWGzoCi0VlBZ77A/edit#heading=h.khbj6f3vn1mu

Shaun, can you add a description please?

Ticket could be closed off as being tracked in jira here - https://bugster.forgerock.org/jira/secure/RapidBoard.jspa?rapidView=923&projectKey=SAPIG&view=detail&selectedIssue=SAPIG-13


Activity can not receive Event when app in the background.

When I push my App to background, My Activity does not receive Event while Fragment does well.
I post my detail question in here. Any guy can help me?
Thanks in advance.

do you call EventBus.unregister() method in the lifecycle method of your Activity?

This is discussed at length at the mentioned Stackoverflow post. Closing.


Include changed files in function output

Describe your problem
When users run a mutator (e.g. set-annotations), the output doesn't tell them which files changed. The only way a user can figure out which files were affected is by looking through them manually or doing git status or however they might normally be notified of changes to files.
It would be nice if we were able to notify the user which files changed as a result of their running a function in the output of that function.

@grmoon Output similar to apply-setters is what you are looking for ?

@grmoon Output similar to apply-setters is what you are looking for ?

that would be great!

@etefera This would be a good issue if you want to pick up.

This has now been implemented for set-annotations by adding the following functionality to the kustomize api:
https://github.com/kubernetes-sigs/kustomize/pull/4307
And subsequently consuming the new functionality in the set-annotations function:
https://github.com/GoogleContainerTools/kpt-functions-catalog/pull/662

We plan on providing this functionality to the set-labels function as well


Check to ensure no two consecutive check runs share a timestamp.

Uses a simple counter that gets incremented every time we make a new check context. When a check runs, if the context has not changed since last time, we wait a second and look again.
Also fixes race condition.
Fixes #2023

What about something like instead of the routines sleeping on time, a timer tells them when they can run. That way the timer can always set the context before sending the signal

I thought about something like that, maybe using sync.Cond as a signal. But I think there is an additional race there.
If the context is updated and signalled between when the alert detects no-change, and when it subscribes to the signal, you miss a whole check interval. My way you only lose a second.

Kyle and I had a better idea in hangouts. will implement that instead.


Improve range property hints for various collision shapes

Closes #36419.
Helps #19242.
The current limits seem to be unreasonably high for shapes, when you drag a slider it's often too difficult to set a value which wouldn't jump from minimal size/length to a size which covers the whole viewport (meaning it only takes 4 range steps to exceed the shape's size beyond visible screen in most cases). Fine-tuning helps but doing this every time is tiresome.
The maximum ranges:

for 2D: 1024 pixels or greater (was 16384);
for 3D: 128 units or greater (exact ranges as in CSG nodes) (was 4096).

The maximum values for 2D and 3D are picked by an "equal" number of mouse-wheel scrolls it takes to fully enclose a shape for it to become visible inside the editor viewport (in most cases).
Slow stepping for 2D is taken into account: #866, so I didn't change the current step (0.5 pixels).

Again, merge conflicts which I'm not willing to resolve at the moment given this enhancement is not critical, so might be salvageable, but this likely needs more discussion as in #19242.

For 3D shapes, I've just made it consistent with CSG nodes now, yet those don't allow "or_greater", which can be added too. For 2D, this is still the same as described in OP.

Superseded by #59550.


implement new update api for writing systems

reference the update implementation for UpdateEntry

While creating UpdateWritingSystemProxy, I discovered that MiniLcm writing systems have a Font property that's a single string, but LCM writing systems have a Fonts property that's a dict keyed by string. We'll need to decide on how to handle that model mismatch during updates.

The font in the miniLcm version of the Writing system is the default writing system, so maybe a change should just change the default font. I'm not even sure how we would use more than one font, I might need to get info from Jason about it.


 Therefore it will result in a bad DX. We should boil this down to just go get.
Solution
The solution unfortunately is complex, because it is caused by a conflict between the Moby/Docker and Go projects, respectively. There are four ways we can solve this:

Convince Go to revert their decision to break the established tagging convention for go projects. Estimate: impossible.
Convince Docker to change their tagging convention to match Go's new tagging mandate. Estimate: unlikely.
Convince Go and Docker to find a middle ground. Estimate: unlikely.
Solve the problem downstream with a private fork + custom tooling. Estimate: annoying but doable.

Related: https://github.com/dagger/dagger/issues/3367#issuecomment-1278324885
Related: https://github.com/dagger/dagger/issues/3368

Convince Docker to change their tagging convention to match Go's new tagging mandate. Estimate: unlikely.

Update from today's community call: it sounds like they're doing this after all by switching to regular semver!
However we'd still need to wait for a new release of moby/buildkit to be tagged. Maybe that won't be too much trouble.
We can't easily bump to an untagged moby/buildkit either; I tried this and ended up needing to add a replace line to stop the Go CLI from "bumping" (really rewinding) the dependency, which brings us back to square one. Context: https://github.com/dagger/dagger/pull/3560#discussion_r1007075789
The long-term fix, to me, is to bite the bullet and switch to an external engine so the SDK doesn't depend on any of this at all.

Yep - closing, thanks for checking in!


Fixes #7

Fixes an issue where matching is matching the start of a string, rather than the whole string.
Unit / Regression test passing.

Done!

Actually thinking about this.. it might not be the best solution.. what if the pattern ends with a * - then I guess you don't want to add a $ to the regex?

I'll add a test case and find out

Ok that doesn't appear to be a problem, but have added another test case for that anyway.


General container update

Description
This PR will be a general update for containers.

Add runtime configuration for frontend
Automate container build/release to ghcr.io

Fixes # (issue)
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

[ ] Local Pre-commit Checks
[ ] CI/CD Build

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] If applicable - I have commented my code, particularly in hard-to-understand areas
[ ] If applicable - I have made corresponding changes to the documentation
[ ] If applicable - I have added tests that prove my fix is effective or that my feature works
[ ] If applicable - New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Combining PRs as it may be some time before a merge/release.

@jasonb5 v1.0.10 is in "great shape" so we have working CI again.  (Just now fails one linter check but I think we can resolve)

Was this closed by mistake?  It is trivial to change a base branch, IIRC a while ago you could not...


Show checkbox column after long press on any row

Is the library support this feature?

There're all the required pieces to make that happen:

There's showCheckBoxColumn property in table widgets
DataRow has onLongPress event

All you need is to put the table inside a stateful widget, declare event handler for long press event and assign it to all rows, in the handler do setState() and set a bool flag which is used build() to define value for showCheckBoxColumn

That's Great! Thanks.


update slack info in README

Do we want to encourage k8s slack over the CNCF slack (when buildpacks move)?

Do we want to encourage k8s slack over the CNCF slack (when buildpacks move)?

My understanding is that kpack would not be able to move to the cncf slack

I think they just wouldn't automatically migrate it but, we could create a kpack channel.

Oh I must have misunderstood then. I thought kpack had to be in the cncf to have a channel there

My take would be wait until the CNB slack is migrated and then decide where we would prefer the "official" channel to live.

You should be able to create a slack channel in the cncf slack. It's just that we can't migrate it along with the rest of the project I believe.


De-duplication with dupe-magick

Dupe-magick states, "If you need to look for duplicates which can't otherwise be found via md5 checksums e.g. images of different formats or slightly lossy, then this gem can compare or find duplicates based on euclidian distances between points in an 8x8x8 RGB vector cube."
https://rubygems.org/gems/dupe-magick
I think this would be a great feature to have since there isn't a directory of images users can view so duplicates are starting to become an issue.

While I really appreciate your time to create this issue, unfortunately due to the additional get requests on s3 to do this on a worker pool, I'm going to have to reject this.
Once again, thank you for the research and time you put into this issue creation.


Add schema to ModuleType

This PR builds on #327 - I cannot edit the fork so have to create a new PR. I add the extension to the ModuleType data schema, to include the schema and the database migration for production.
@egonw's original contributions are still reflected in the commits.
The only downside: Because the module types are already in the database, the seed script will skip these items. We could revisit this at a later time when #151 has been implemented - to ensure that the database gets updated if anything has changed.

@all-contributors add @egonw for code


Add migration notice

Marks this package as end-of-life and suggests that users migrate to the
core libray in the main Quiver package at
https://github.com/google/quiver-dart.

Coverage remained the same at 100.0% when pulling de07f0764b3b81abd1fd7a8bb50799d777c9032f on end-of-life into 3bc6e67c20f42d77df6c732e494d37fd3a89eb91 on master.


using with pg-error

Is there a way to setup Knex to use the pg-error package? Ultimately, I'm looking for a way to gracefully handle database errors. Open to suggestions!
Thanks!

Maybe you could wire it to be set up by the pool when connection is created?
something like
          pool: {
            min: 0,
            max: 10,
            afterCreate: function (conn, cb) {
              conn.parseE = PgError.parse
              conn.parseN = PgError.parse
            }
          },

Gave it a try, but doesn't seem to be working. The error returned still isn't an instance of PgError.
@moll do you have any idea on how to resolve this?
Thanks!

Almost there, @jamesdixon. One extra listener missing:
connection.connection.on("PgError", emitPgError)

I added some instructions to https://github.com/moll/node-pg-error#using-with-knexjs. Do they help?
PS. @elhigu: I believe the connection returned by afterCreate is one wrapped by Knex/pool. The real Pg.Client lives in connection.connection.

@moll those instructions work beautifully! Thank you for your quick response!

@moll thanks for the infos!


fix: tmux not quitting after MOMA alignment

https://superuser.com/questions/878640/unix-script-wait-until-a-file-exists


feat: add multi-scf-python

An action to auto-publish the new template is necessary: https://github.com/serverless-components/tencent-examples/blob/master/.github/workflows/koa-starter.yml


For a reported metablock, a supermajority vote commits the block

A reported metablock contains the signature root of the trie of the validator votes cast:

[ ] introduce static validator set with voting power
[ ] verify a signature of a vote cast contained in trie
[ ] commit block for supermajority vote asserted

continues #253

Continued in #373


Disable a feature for a specific actor

Hello,
I got an issue with Flipper.
We use Flipper to turn on or off features for specific customers. First we want to enable globally a feature that is ready to be used in production, and then activate or deactivate it for selected customers.
It seems that it is not possbile to deactivate a feature enabled globally, for exemple I expect the feature to be disabled only for the Organization.first while it is still for the others but it is not :
FLIPPER[:cases].enabled?
=> true

FLIPPER[:cases].enabled? Organization.first
=> true

FLIPPER[:cases].disable Organization.first
=> true

FLIPPER[:cases].enabled? Organization.first
=> true

I saw discussion about this here and here.
Will this be a feature for Flipper and if yes do you know when ? Do you suggest a workaround ?
Thank you

Ok, I managed a workaround by rewriting the code to never use global FLIPPER (FLIPPER[:cases].enabled?). I loop on all orgs and apply the logic I want accordingly.

Hi!
Eventually I would like to add deny to flipper as well but we have a few things to get shipped before that so I don't have a timeframe for you right now.

@acouprie another approach is to use a group to define everyone who is allowed access.
Flipper.register(:generally_available) do |user|
  !user.banned?
end

Flipper.enable_group(:cases, :generally_available)


Replace the no-contacts image on the main roster page

This replaces the no-contacts image on the main roster page (it was
using the default contact image we have) with the person core icon.
Fixes #1168

:+1:


refactor cleanup segment flush logic in beta rowset writer

Proposed changes

Cleanup segment writer creation logic and segment flush logic in beta rowset writer.
Remove FlushContext, and pass segment_id, no_compression, flush_schema explicitly.
Fix a bug when NO_COMPRESSION should not be used when adding many small blocks by add_block().
Allocate real segment id in allocate_segment_id(), instead of offset against _segment_start_id.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53 seconds
stream load tsv:          447 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          70.8 seconds inserted 10000000 Rows, about 141K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230707131233_clickbench_pr_174638.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53.56 seconds
stream load tsv:          505 seconds loaded<PHONE_NUMBER>9 Bytes, about 141 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          86.1 seconds inserted 10000000 Rows, about 116K ops/s
storage size:<PHONE_NUMBER>8 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230707214544_clickbench_pr_174648.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.52 seconds
stream load tsv:          447 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          69.6 seconds inserted 10000000 Rows, about 143K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230707140108_clickbench_pr_174671.html

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.97 seconds
stream load tsv:          498 seconds loaded<PHONE_NUMBER>9 Bytes, about 143 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          85.5 seconds inserted 10000000 Rows, about 116K ops/s
storage size:<PHONE_NUMBER>0 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230707221233_clickbench_pr_174673.html

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.18 seconds
stream load tsv:          500 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          88.6 seconds inserted 10000000 Rows, about 112K ops/s
storage size:<PHONE_NUMBER>6 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230709001542_clickbench_pr_174933.html

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 51.14 seconds
stream load tsv:          448 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          70.0 seconds inserted 10000000 Rows, about 142K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230708183936_clickbench_pr_174975.html

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.86 seconds
stream load tsv:          442 seconds loaded<PHONE_NUMBER>9 Bytes, about 161 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          56 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          68.9 seconds inserted 10000000 Rows, about 145K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230708193405_clickbench_pr_174994.html

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 57.31 seconds
stream load tsv:          505 seconds loaded<PHONE_NUMBER>9 Bytes, about 141 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          66 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.4 seconds inserted 10000000 Rows, about 340K ops/s
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230709034454_clickbench_pr_175002.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 44.64 seconds
stream load tsv:          443 seconds loaded<PHONE_NUMBER>9 Bytes, about 161 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          25.7 seconds inserted 10000000 Rows, about 389K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230708201201_clickbench_pr_175000.html

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.58 seconds
stream load tsv:          501 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230710164800_clickbench_pr_175792.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 56.76 seconds
stream load tsv:          508 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          66 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230710215615_clickbench_pr_176006.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 49.46 seconds
stream load tsv:          447 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          26.5 seconds inserted 10000000 Rows, about 377K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230710135700_clickbench_pr_176011.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 54.57 seconds
stream load tsv:          502 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.6 seconds inserted 10000000 Rows, about 349K ops/s
storage size:<PHONE_NUMBER>8 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230711172338_clickbench_pr_176352.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.75 seconds
stream load tsv:          445 seconds loaded<PHONE_NUMBER>9 Bytes, about 160 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          56 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          25.9 seconds inserted 10000000 Rows, about 386K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230711095933_clickbench_pr_176357.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53.04 seconds
stream load tsv:          446 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          25.5 seconds inserted 10000000 Rows, about 392K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230711132747_clickbench_pr_176518.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.82 seconds
stream load tsv:          498 seconds loaded<PHONE_NUMBER>9 Bytes, about 143 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230712020259_clickbench_pr_176737.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.48 seconds
stream load tsv:          445 seconds loaded<PHONE_NUMBER>9 Bytes, about 160 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          26.0 seconds inserted 10000000 Rows, about 384K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230711181115_clickbench_pr_176736.html

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.51 seconds
stream load tsv:          500 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.7 seconds inserted 10000000 Rows, about 348K ops/s
storage size:<PHONE_NUMBER>9 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230712112107_clickbench_pr_176828.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.8 seconds
stream load tsv:          445 seconds loaded<PHONE_NUMBER>9 Bytes, about 160 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          26.2 seconds inserted 10000000 Rows, about 381K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230712032225_clickbench_pr_176827.html

run buildall

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 51.75 seconds
stream load tsv:          511 seconds loaded<PHONE_NUMBER>9 Bytes, about 139 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>9 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230712221552_clickbench_pr_177358.html


fix rst formatting

This fixes RST formatting typos in README.rst that were preventing proper formating at https://pypi.python.org/pypi/census.
I found the lines with bugs by using the setup.py check command:
python setup.py check --restructuredtext --strict --metadata

@fitnr I looked at all of these PRs out of order so I had to manually pull in your fix. Thanks for the PR!


Sets user-select: none to the hover actions so they cannot be selected anymore.

This fixes feedback that we got for the action items, especially as they intenionally don't disappear when clicking on them.

@Tyriar since I think your the most correct owner of this.

Huh, or maybe everyone has touched this file.

Any issue link for this?

In the other repo.
@sandy081 let me know if you have input on this! I'll merge this as this fixes a bug reported from the test plan item.


WIP - Check HTTP pipelining test failure in windows build

Purpose

$subject

Fixes #19883
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #19882 into ballerina-1.0.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.0.x   #19882   +/-   ##
================================================
  Coverage            20.51%   20.51%
================================================
  Files                   52       52
  Lines                 1394     1394
  Branches               216      216
================================================
  Hits                   286      286
  Misses                1095     1095
  Partials                13       13

Continue to review full report at Codecov.

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


Add Leaf micro framework

This has been suggested before. https://github.com/ziadoz/awesome-php/pulls?q=is%3Apr+leaf+is%3Aclosed

but why not?


Exclude archetype not working for management, connectivity or sandbox

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform: 1.0.8
azure provider: 3.0.2
module: 2.3.1
Description
Describe the bug
We are trying to disable some azure policies using the exclude archetype, this applies to the root or our custom landing zones, but doesn't apply to management, connectivity, decommissioned or sandbox
Steps to Reproduce
File is called "archetype_exclusion_decommissioned.json"
{
"exclude_es_decommissioned": {
    "policy_assignments": [
        "Deploy-ASC-Monitoring",
        "Deploy-AzActivity-Log",
        "Deploy-LX-Arc-Monitoring",
        "Deploy-MDFC-Config",
        "Deploy-Resource-Diag",
        "Deploy-VM-Monitoring",
        "Deploy-VMSS-Monitoring",
        "Deploy-WS-Arc-Monitoring"
    ],
    "policy_definitions": [],
    "policy_set_definitions": [],
    "role_definitions": [],
    "archetype_config": {
    "parameters": {},
    "access_control": {}
    }
}
}

This file with Terraform plan
Screenshots
This is what we get when se do exclude_es_root:

This is what we get when planning with exclude_es_decommissioned:

Hi @owejak,
These polices are assigned at the intermediate root management group "es_root" so you would need to exclude them from there.
Or use the "notScopes" to exclude those policies from taking effect on the decommissioned management group.
Hope that helps
Thanks
Jack

This has been handled over email

Trigger ADO Sync


drivers: gpio: add usage and error messages to the gpio shell

Added usage information to the GPIO shell commands help to make them usable without consulting the source, because currently that seems to be the only way to find out what arguments are expected.
I also added an error message when the GPIO device is unavailable.
Formatting is like the ADC shell, which I found more approachable.
This is what it looks like:
gpio - GPIO commands
Subcommands:
  conf   :Configure GPIO
          Usage: conf <device> <index> in/out

  get    :Get GPIO value
          Usage: get <device> <index>

  set    :Set GPIO value
          Usage: set <device> <index> <value>

  blink  :Blink GPIO
          Usage: blink <device> <index>

And the error message: Device fake_device not found or failed to initialize
I wasn't able to run the tests, but it compiled fine for my board.

Sorry, I really want to stay pseudonymous on this account.
If there's any way you or someone else can just "take over" the commit I'd be grateful for that, but I understand if that's not possible.

Sorry, I really want to stay pseudonymous on this account.
If there's any way you or someone else can just "take over" the commit I'd be grateful for that, but I understand if that's not possible.

Sure, as long as you agree to allow us to do that.

Sure, as long as you agree to allow us to do that. Let me check with others first.

Yep, completely ok with me.

I am sorry @itsxaos, we cannot accept code from pseudonymous accounts, it goes against project policy. My apologies.


After a cluster upgrade, replication seems to work but Orchestrator fails to update cluster topology (connection refused)

Hi! I am using DigitalOcean's managed kubernetes and yesterday I replaced a node pool with another, which caused one node per time to be replaced. When the current MySQL master was evicted from a node being replaced, MySQL seemed to failover to the slave, but since then Orchestrator is unable to show the topology in the UI - I did see a message once saying that the cluster had been recovered or something like that, but now all I see is this:

I exec'ed into the orchestrator container and if I run something like
orchestrator -c topology -i mysql-cluster-mysql-0.mysql

All is get is this:
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 CRITICAL dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR ContinuousRegistration: RegisterNode failed: dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 CRITICAL dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 CRITICAL dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 ERROR dial tcp :3306: connect: connection refused
2020-01-07 09:46:33 FATAL dial tcp :3306: connect: connection refused

The replication seems to be working because when I save data the slave has the updated data. However I am not sure of what's going on with the Orchestrator and if there still is a problem. Now it's just me using the cluster but I am worried that these issues might happen regularly once I am in production, because DigitalOcean frequently replaces nodes for security updates etc, besides Kubernetes upgrades.
What can I do to check if my cluster is actually OK and what can I do to prevent issues when cluster updates occur?
I'm not familiar with Orchestrator so forgive me if I am missing something obvious.
Thanks in advance!

In the master's log I see
Access denied for user<EMAIL_ADDRESS>(using password: NO)

And that is the IP of the orchestrator. It's trying to login with no username?

I don't understand, I tried several times restoring from a backup taken before the cluster upgrade and again, the replication seems to work but Orchestrator shows the same thing as shown in the image above plus this:

I deleted the cluster, uninstalled the operator, deleted the namespace and restored from the backup. Always the same. Is there a problem with the current version? I have 0.3.5 now. @AMecea

Hi @vitobotta, please show me the cluster status (kubectl describe mysql <mysql-cluster-name>).
Did you set a password for orchestrator topology? Check the secret <release-name>-mysql-operator-orc to have the right credentials set.

Hi @AMecea ! This is the describe: https://pastebin.com/raw/R5GF5pSY
I didn't set any password.  I restored again and get the same thing but with a lag of 52K seconds or so. I don't understand what happened, never had an issue before

After restoring the master svc doesn't have any endpoints either

Interesting... I restored as a single replica then I tried "Reset slave" on that replica. Orchestrator immediately showed the replica as "Master" instead of "Co master". Then I added another replica by editing the cluster and it's replicating from the master and Orchestrator seems OK now.
What happened? Why is the main replica as co master after restoring from backup? I am now going to delete and try restoring a more recent backup from after the cluster upgrade, to see if that works too.

Yeah that trick seems to have worked with a more recent backup as well. I would appreciate an explanation of how this stuff works and what's the expected behaviour when cluster upgrade etc occur, since I am pretty new to this stuff. Thanks! :)

Shit.. I spoke too soon :p The master service has no endpoints after that....

So if I remove a pod and let recreate it, the endpoints get updated it seems...
However: I first restored the cluster with 2 replicas, then I tried to add a third replica but that one wouldn't start properly, complaining about duplicate primary keys. I tried restoring with three replicas from the beginning and I see this in the third replica:
2020-01-07T14:08:45.442330Z 98 [Note] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='mysql-cluster-mysql-0.mysql.mysql', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='mysql-cluster-mysql-0.mysql.mysql', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2020-01-07T14:08:46.584537Z 98 [Note] Aborted connection 98 to db: 'unconnected' user: 'sys_operator' host: '<IP_ADDRESS>' (Got an error reading communication packets)

I have been using this operator for a few months and haven't had problems with it before. Now I am having problems with replication, orchestrator and restoring from backups properly....
When I install the operator with Helm it installs 0.3.5. Which version should I be using? The Releases page here on Github shows that there are tags for 0.3.2-5, but the last "release" is 0.3.1. Should I be using that one instead?

I am basically unable to restore any backup.... I am trying with several backups from before the cluster upgrade and nothing works. This last attempt I've restored a backup from two days ago with a single replica. It's up and running / ready but no endpoints in the services and Orchestrator shows the single replica as "Co master" with a long lag and in the details panel I see this:

Why is mysql-cluster-mysql-0.mysql.mysql:3306 set as master for itself?
@AMecea I am really sorry to bother you.... but I don't know what else to try :(

There's something wrong with my backups. I tried creating a brand new cluster instead of restoring and all looks good.

I've never encountered this issue before, I will do more debugging. Version v0.3.5 should not be more different than v0.3.1 and I don't think that it's the root cause for this.
Let's move this converstation on slack.

fixed by #447


Question about pre_CT.pt, test data

https://github.com/bowang-lab/MedSAM/blob/7e86549203bda3233afc50b8c8cc41c521d88c9b/pre_CT.py#L146
Hello author.Thanks for your code.
I hane some question, img_embedding should have no effect in testing data, whether it is redundant code?

this is for training data preprocessing.
During inference, you can start with the original image as shown in the tutorial

Thank you for your reply.
Another question is whether the Tr_Release_Part2 data set has been processed like pre_CT.py(except for img embedding, I know that I need to compute img embeddings through another program),
because I want to use my own data set，do I just need to store my data as npz files containing img and gt， and use (precompute_img_embed.py -> train.py) for training?

Hi @peter88510 ,
Yes, the released data has been preprocessed.
The original data should be nii and you can use the pre_CT.py to convert them to npz. You can find the complete introduction to this process in the video tutorial.


Long tap opens context menu

Hi There,
I tried to use hover-on-touch and it kinda works, but after the hover effect the browser displays the context menu (open in new tab etc).
In your demo, it doesn't and works as expected. What am I doing wrong...?

Could you give some details about your code?

I am integrating it in Open Streaming Platform so I kind of inserted the code in there (https://openstreamingplatform.com/)
In 'layout.html" I have this in the head

In the css I have
.zoom {
    transition: transform .2s;
}

.hoverontouch--aktiv .zoom {
  -ms-transform: scale(1.05); /* IE 9 */
  -webkit-transform: scale(1.05); /* Safari 3-8 */
  transform: scale(1.03);
}

/* .zoom:hover {
  -ms-transform: scale(1.05); /* IE 9 */
  -webkit-transform: scale(1.05); /* Safari 3-8 */
  transform: scale(1.03);
} */

and in the HTML this:

                         Live

So, in HTML I added hoverontouch class to the container of the divs that have the zoom class. In Css I disabled the original zoom:hover and replaced it with hoverontouch--aktiv. And in the head included the script.
On my android phone, you 'simple demo' works nicely, long-touching it displays the hover and nothing else happens. On my test openstreamingplatform server, the element does activate the 'zoom' class on long-touch, but then after a small delay the context menu opens (Open in new tab, etc). This happens in FF and Chrome.

Is it already implemented in the online site?

SIte is behind firewall. It's not osp itself, I am just setting osp up for myself.
If you need to look at it, I can make arrangements but it takes a while to make it accessible. Can I email you privately?

I got it working, thanks. Great!!!

Perfect :)


disk-smart: Properly handle Power_On_Hours_and_Msec attribute perfdata parsing

Hi,
and first many thanks for your great collection of monitoring plugins!
I've just found them - clean structure and output, cross-platform, Icinga Directory Basket configurations - loving it and currently migrating step by step most of my checks to use them where possible. 😍
I had one error when using the disk-smart check and some SSDs (namely SanDisk).
The error was when parsing perfdata:
bb@vmh-home2:~$ sudo /opt/centralcfg/scripts/icinga/linuxfabrik-monitoring-plugins/disk-smart/disk-smart3
Traceback (most recent call last):
  File "/opt/centralcfg/scripts/icinga/linuxfabrik-monitoring-plugins/disk-smart/disk-smart3", line 910, in 'module'
    main()
  File "/opt/centralcfg/scripts/icinga/linuxfabrik-monitoring-plugins/disk-smart/disk-smart3", line 866, in main
    disk_report = parse_sections(stdout)
  File "/opt/centralcfg/scripts/icinga/linuxfabrik-monitoring-plugins/disk-smart/disk-smart3", line 773, in parse_sections
    report['attributes'] = parse_section_data_subsection_attributes(sections['data_attributes'])
  File "/opt/centralcfg/scripts/icinga/linuxfabrik-monitoring-plugins/disk-smart/disk-smart3", line 545, in parse_section_data_subsection_attributes
    raw_value = int(raw_value)
ValueError: invalid literal for int() with base 10: '45448h+00m+00.000s'

Those drives don't have a Power_On_Hours integer attribute, but one named Power_On_Hours_and_Msec and a value which is not an integer, example:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  9 Power_On_Hours_and_Msec -O--CK   000   100   000    -    45448h+00m+00.000s

I've fixed the error / added perfdata parsing of that value and also added a smartctl example (EXAMPLE26) and extended the tests.

Hi Bernd, thank you for your contribution!


Strange output in footer

I'm seeing what looks like unformatted/code output in the footer. I'm on latest Jenkins at this time, 2.138.3. I can't recall when this popped up but I'm pretty sure it was when I upgraded to 2.138.x. LMK what debug output I might be able to provide.

Same here on Jenkins 2.138.3 and Plugin version 0.0.10 (also tried 0.0.9)
Looks like the HTML has '<' HTML-encoded:

To remove this message, please click here

Bit more than cosmetic because it also covers the last bits of console output, which are often the most important. :(
Thx for reading

You need to set -Dorg.kohsuke.stapler.jelly.CustomJellyContext.escapeByDefault=false which helps in this case. There are several things broken with this change in Jenkins. See https://jenkins.io/blog/2018/10/10/security-updates/ and https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+2018-10-10+Stapler+security+hardening

Thanks for the note. Is it safe to say the blanket disabling is just a band-aid and a patch should still be made so the plugin itself can handle the reconfiguration?

Indeed, it would be really nice if the plugin could be targeted about disabling the escaping logic.

Same issue, just to report it. It looks like the j:set var="msg" block creates a commented out span, and not what the code is expecting.

+1


Allow webmail access from custom domain or multiple location

See #117

@ddavness Could you please review this? I accidentally closed my other PR

Alright so let me understand @winux1. With this change:

The default /mail endpoint remains accessible (and you cannot remove it as of now, but that's for another issue);
You can use custom nginx configurations to enable webmail on any other endpoints (custom domain/custom path/whatever);
Users will be responsible for the security of those endpoints;

Is that it?


KubeEdge: update viaduct fuzzer path

KubeEdge will move viaduct path to https://github.com/kubeedge/kubeedge/tree/master/pkg in https://github.com/kubeedge/kubeedge/pull/5907, this PR updates the corresponding viaduct path.

PTAL : ) @AdamKorcz


Negative POA shading loss for vertical arrays.

Describe the bug
A user reported finding negative POA shading loss values when using the non-linear self-shading model for vertical arrays.
Forum post: https://sam.nrel.gov/forum/forum-general/4443-negative-pao-front-side-shading-losses.html#12722
Email context: I’d have to dig a bit further but at first glance it appears this diffuse_reduce function has a cosd(180 – tilt) that would return a 0 when tilt = 90, leading to a divide by zero issue for the factors F2 and F3. This function seems to be applied for both the non-linear (https://github.com/NREL/ssc/blob/develop/shared/lib_pvshade.cpp#L567) and linear (https://github.com/NREL/ssc/blob/develop/shared/lib_pvshade.cpp#L511) options, although Janine can correct me if I am wrong. We might need to add in a limit of 89.9 for that equation or something similar.
https://github.com/NREL/ssc/blob/develop/shared/lib_pvshade.cpp#L213
Expected behavior
There should be a warning or an equation limit to prevent this negative shading loss from happening
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

My initial read of this issue was incorrect. It is related to the sky diffuse shading factor. I don't think this factor should ever be greater than 1.


[FEATURE] Bring in support for Python 3.13

Is your feature request related to a problem? Please describe.
The koheesio framework does not currently support Python 3.13, limiting developers from using the latest features and improvements.
Describe the solution you'd like

[ ] Add support for Python 3.13 by updating the pyproject.toml file
[ ] ensuring all dependencies and tests are compatible.
[ ] Update the CI/CD pipeline to include Python 3.13 in the testing matrix.

Describe alternatives you've considered

Not Supporting Python 3.13: Continue supporting up to Python 3.12, but this prevents using new features in Python 3.13.
Partial Support: Update the pyproject.toml file without updating the CI/CD pipeline, allowing use of Python 3.13 without guaranteed compatibility.

Additional context
Supporting Python 3.13 ensures the koheesio framework remains up-to-date, providing developers access to new features and improvements.

Checked the current state (based around 0.9.0rc0):

Tableau dependencies are incompatible with Python 3.13
Snowflake dependencies are incompatible with Python 3.13
JDBCReader test is failing with FAILED tests/spark/readers/test_jdbc.py::TestJdbcReader::test_execute_w_dbtable_and_query - AssertionError: assert 'foo' is None

WIth that, marking this as blocked for now. Will have to revisit this in the future.


Add a test for normalize_doc_attributes under tests/source/configs and tests/target/configs

👋 I'd like to work on this one if it's still up for grabs


Use artifacts v4

v4 having the same commits as v4-beta

@TooManyBees @YiMysty just a heads up, the artifacts v4 actions aren't supported on GHES yet so we have to be careful with releases 👍


[WIP] Newton backport check nova services

Adds post-upgrade task to check running nova services to ensure
all are running in the correct venv.
Includes commit fc40fa1 which is awaiting backport in #2209
Connects rcbops/u-suk-dev#856
(cherry picked from commit d6236c3)

Hi, @dankolbrs. Could you resolve the merge conflicts on this one?

@dankolbrs This looks good, but keep in mind that changes made to the rpc_{post,pre}_upgrade roles will only be tested in the mitaka-13.1 branch. That's the only branch that we run the upgrade job on, and in turn, the post/pre upgrade roles.
That's not to say that these changes in the newton branch aren't useful, they are just not tested.
Also, please make sure to squash these commits. You can do that either through git or through the github UI at the time of merge.

recheck_cit_all - defcore cinder_backup failure

Closing in preference to #2257


Get-GSChromeOSDevice returning weird data

Describe the bug
when running Get-GSChromeOSDevice much of the data is correct, there are various bits that return "Google.Apis.Admin.Directory.directory_v1.Data.ChromeOsDevice+" and whatever the field name is: Google.Apis.Admin.Directory.directory_v1.Data.ChromeOsDevice+RecentUsersData instead of the data that is in that place.
To Reproduce
Steps to reproduce the behavior:

Run Get-GSChromeOSDevice
See data

Expected behavior
I expect to see the proper data in these fields
Maybe I set something up incorrectly, or maybe I'm just stupid (that is highly likely)
Screenshots

Environment (please complete the following information):

OS:  Windows 10 Pro Build 19042
PowerShell Version:  5.1.19041.610
PSGSuite Version:  2.24.0 and 2.36.4

Hi,
You need to use -ExpandProperty in Select-Object in order to expand the nested objects.

Hi,
You need to use -ExpandProperty in Select-Object in order to expand the nested objects.

Ah!  I see now, working as expected when formatted properly... Thank you very much!


MQTT: SmartEVSE publishing to strange topics and incorrect data

I'm seeing some strange topics when monitoring MQTT. Also sometimes correct topics get strange values.
In the screenshot the lasst 4 topics are wrong and MainsCurrentL1 has a strange value.

My SmartEVSE is running v1.7.2.

If you watch the same data on the webserver, "Raw Data", same problem or values ok there?

On the "Raw Data" page the values seem correct.
On the "Raw Data" page it says that MQTT is disconnected yet it is publishing to the broker.

Does reconfiguring your MQTT settings on the webserver page change anything?
I cannot reproduce this at my site.

I tried it. Changed the settings to some random value and saved them. The SmartEVSE indicated that it was disconnected.
Then I changed the settings back to the correct values and saved them. The SmartEVSE connected again and after a few minutes I see the same problem again.
It looks like it has something to do with writing the mainsmeter data to the SmartEVSE over MQTT. When I don't send it everything is working as expected. When I start sending the data again the problem is back.

Does v1.7.1 have the same problem?

Tried v1.7.1 for 15 minutes now and it is working fine.

Are you willing and able to compile yourself?

It is not very complicated, and this way you can find out which commit causes the problem; first do
git checkout (some commit in the middle of v1.7.1 and v1.7.2)    --> test if problem exists work your way down to 1.7.1 else work your way up to 1.7.2 .
Building the firmware

Install platformio-core https://docs.platformio.org/en/latest/core/installation/methods/index.html

Clone this github project, cd to the smartevse directory where platformio.ini is located

Compile firmware.bin: platformio run

Compile spiffs.bin: platformio run -t buildfs

Commit 61f49cf1624630d816774078d07164c65477daff is causing the problems.
Tried a few different commits, but the problems start with that commit.

Interesting, that code updates publishes the currents immediately after they change; Im going to review that code tomorrow....

It might not just be the currents though, my HA complains about some random data in other fields as well

@hmmbob Your problems also arise when you are feeding Mains Currents L1 - L3 via MQTT?
Also problems disappear when stop feeding?
Also problems disappear when using v1.7.1?

I am not feeding L1-L3 through MQTT, but through API (http post). Rollback to 1.7.1 fixes the issue.

Im not, since I dont get to reproduce this problem.
If you want to check free ram, uncomment lines in src/evse.cpp that contain the string "free ram", and check debug log via telnet.
If necessary you can increase stack sizes of different tasks, src/evse.cpp look for comment "Stack size".

Rarely I see this problem. My 2 cents are in the multi-threading area. Since in 1.7.2 the Currents are updated in the void UpdateCurrentData(void) method, which is called from several places. As a proof of concept I moved them back to the mqttPublishData() method. Let you know if the problem disappears.
Ps. I push the current-data via the web-interface, not via MQTT.

I agree that is much more probable; and Im convinced the problem is solved by placing the publish statements back to the publishdata function.
But I dont see that as a solution, since the long term goal is to feed the mqtt server immediately (and only) if values change.
So the solution would be to make the publish routine threadsafe; to do that effectively it is necessary to find out what part of the library is the problem OR move to a threadsafe mqtt library.

mutex.zip
As a proof of concept I placed mutex locks around the publish calls; could someone who can reproduce the problem test this?

The version with the mutex is working fine. No more corrupted data and topics.

Fixed with 2020c53edcfb


Talks Thumbnails Have Unnecessary Space Underneath

When all talks in a row are 16:9, there is unnecessary vertical space underneath the thumbnail:

Should be fixed when we do this: https://github.com/jonfroehlich/makeabilitylabwebsite/issues/314

This is still a problem but not sure how to solve. The issue is that some thumbnails are 4:3 but the newer ones are 16:9. Maybe we could just crop every thumbnail to be a 16:9 ratio?


fix: LSDV-5409: Existing text range cannot be changed into a different label

PR fulfills these requirements

[X] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[ ] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[X] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[X] Frontend

Describe the reason for change
Changes in #1460 caused a regression with non region label handling, ie. text ranges. Small adjustment to just look at the result type again.
Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[X] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[ ] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
Labels

Codecov Report
Patch coverage: 60.00% and project coverage change: -1.99 :warning:

Comparison is base (a7f7bda) 67.66% compared to head (4bee7dd) 65.68%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1508      +/-   ##
==========================================
- Coverage   67.66%   65.68%   -1.99%
==========================================
  Files         437      437
  Lines       27262    27265       +3
  Branches     7235     7133     -102
==========================================
- Hits        18448    17908     -540
- Misses       7624     9357    +1733
+ Partials     1190        0    -1190

Impacted Files
Coverage Δ

src/tags/control/Label.js
92.79% <60.00%> (-1.66%)
:arrow_down:

... and 217 files with indirect coverage changes

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


Not updated and having bugs that are fixed in the official

Either update it or remove it from npm database.
Better make the original a dep on your 'pano' than this fork.

I agree, I'll remove it from the database and make the original the dependency. Thanks for pointing that out!

@Vortelf I tried to unpublish the package from npm but I got the following error:
$ npm unpublish --force
npm WARN using --force I sure hope you know what you are doing.
npm ERR! unpublish Failed to update data
npm ERR! code E500
npm ERR! You can no longer unpublish this version.
npm ERR! Please deprecate it instead:

I've marked every version of the package as deprecated, linking to pchen66/panolens.js in the message. I've also dropped the package version to 0.0.0, and marked the package as deprecated in package.json. I've updated the README to point to the original project as well, and pushed v0.0.0 to npm with the updated README and deprecated flag in package.json.
If @pchen66 would like to take ownership of the package on npmjs.org, I'm happy to transfer it over.
I apologize for the confusion! Thank you for calling this out.

The docs note that,

With the default registry (registry.npmjs.org), unpublish is only allowed with versions published in the last 24 hours. If you are trying to unpublish a version published longer ago than that, contact<EMAIL_ADDRESS>
If needed, I'm happy to contact them.


Add Location Service and Tests

In this PR, we add a service that wraps the Location API from
"https://nominatim.openstreetmap.org/search.php?q={location}&format=jsonv2"
Closes #8

Looks good to me!


Description of slow view query

Describe the bug
With the increase of inserted data, I found that the compute node has the problem of a sharp increase in memory, from 64G to 148G, is there any mechanism to control the memory growth.
As a result of the memory surge, queries become slow, For example, after 2600W data is inserted, it takes one and a half minutes for a view query with 4W data to return a result.
Below are the data fields for the view

To Reproduce
Create a source, then create a materialized view, write the corresponding Kafka more than 20 million data, query the materialized view content, materialized view only more than 40 thousand data, check the response speed
Expected behavior
When the amount of data is too large, whether the amount of data in the memory is balanced with the amount of disks, and whether the persistent data memory is released in time.
Additional context
Maybe I'm not using it correctly, or maybe the database isn't perfect yet.Thank you very much

I found that the compute node has the problem of a sharp increase in memory

Do you know when the sharp increate starts? e.g. when create materialize view, or when query the MV content?

发现计算节点存在内存急剧增加的问题

你知道尖锐的increate什么时候开始吗？例如，创建实体化视图时，或查询 MV 内容时？

Increases as the amount of data increases, not just at query time.

What's your configuration? Would you please paste your docker-compose file here?

Also the full process of running this? e.g. what MV did you create, how's the source look like.

你的配置是什么？你能把你的 docker-compose 文件贴在这儿吗？
docker-compose

Also the full process of running this? e.g. what MV did you create, how's the source look like.

CREATE SOURCE IF NOT EXISTS source_py_gen (
timestamp timestamp,
host_id varchar,
concentration_1 real,
concentration_2 real,
concentration_3 real,
concentration_4 real,
concentration_5 real,
concentration_6 real,
)
WITH (
'connector'='kafka',
'kafka.topic'='connector-distributed',
'kafka.brokers'='broker:29092',
'kafka.scan.startup.mode'='earliest'
)ROW FORMAT JSON;

Only when a view with max and min is created, the memory will explode, and the memory of other views is very stable？

min / max's implementation is significantly different from other aggregators. I guess it is the root cause of your issue.

Also, would you please upgrade to latest version? We've fixed some OOM issues yesterday.

By the way, when are data ingested into Kafka? After all MVs created, or before MV creation?

顺便说一句，数据何时被摄入 Kafka？在创建所有 MV 之后，还是在创建 MV 之前？

After creating the view, write the kafka data

I will close for now since it's been too long. Welcome to try again with the latest version of RisingWave and feel free to reopen if the problem persits. 😊


How exactly do you remove a row from a table?

I've been stumped on this for a couple days..
I created a custom action column with a remove button. Once clicked this handler in griddle.js  fires.
_columnClick = (columnId, columnValue, rowIndex, rowData)
Now how do I remove the row and make the dom re-render?
I tried passing down all the data to this handler and splicing the array at the rowIndex but nothing changes. I am using the alpha version btw.
My set up is:

class actionComponent extends React.Component {

  constructor(props) {
    super(props);
    this.state = {count: props.initialCount};
  }

  render() {
    return (
      <div>
        <button _onClick={this.handleClick}>Delete</button>
      </div>
    );
  }
 }

<Griddle data={fakeData} >
  <RowDefinition keyColumn="id">
    <ColumnDefinition id="name" />
    <ColumnDefinition id="state" />
    <ColumnDefinition id="Actions" customComponent={actionComponent} data={fakeData} />
  </RowDefinition>
</Griddle>

bump

You need to remove data from "fakeData" and the griddle will re-render.

@mlubovac  thanks!


Value cannot be null. Parameter name: project

Problem happens after training completes.
Log file:
Updating nuget dependencies... (Microsoft.ML.ModelBuilder.Utils.Logger.Info)
2021-10-30 03:39:43.1003 INFO Installing nuget package, package ID: Microsoft.ML, package Version: 1.6.0 (Microsoft.ML.ModelBuilder.Utils.Logger.Info)
2021-10-30 03:39:43.1003 DEBUG Value cannot be null.
Parameter name: project
at NuGet.VisualStudio.VsPackageInstallerServices.GetInstalledPackages(Project project)
at Microsoft.ML.ModelBuilder.Utils.Utilities.d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.d__119.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.d__118.MoveNext() (Microsoft.ML.ModelBuilder.Utils.Logger.Debug)

Root cause is that the Project we're trying to use to update the NuGets doesn't exist. I've added some additional logging (will come out in November release). If anyone runs into this problem please let me know we can gather some more info about your project!

Hello @beccamc,
As a side note about me, ML and ML Builder is brand new. This is the first time I am using it.
With that said let's get to my problem. After the training is finished I get the error message: Value cannot be null. Parameter name: project. This error occurred everytime I tried.
The error message said that it had to do with a NuGet package, which is why I installed Microsoft.ML, Microsoft.ML.AutoML & Microsoft.ML.ImageAnalytics additionally by hand. However, the same error message keeps popping up.
The project and the images used are only there for testing, so I would be happy to share my project.

Model Info
Model Info

Scenario: Image Classification

Environment:

Local (CPU)
Intel Core i7-10510U CPU @ 1.80GHz
Memory 16 GB

Data: 3 folders with each 16 PNG-images

Training result
Training result
Best accuracy: 100.00%
Best model: DDN + ResNet50
Training time: 193.40 seconds
Models explored (total): 1
Generated code-behind (MLtesting is the filename): MLtesting.consumption.cs, MLtesting.training.cs

VS Error Window
VS Error Window:
   at NuGet.VisualStudio.VsPackageInstallerServices.GetInstalledPackages(Project project)
   at Microsoft.ML.ModelBuilder.Utils.Utilities.<InstallNugetPackageAsync>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.<UpdateNugetDependenciesAsync>d__119.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.<GenerateCodeBehindFilesAsync>d__118.MoveNext()

Log file
Log file
2022-01-23 18:28:16.9187 INFO Set log file path to C:\Users\username\AppData\Local\Temp\MLVSTools\logs\MLTesting-K4JAV4.txt (Microsoft.ML.ModelBuilder.Utils.Logger.Info)
2022-01-23 18:28:24.4074 DEBUG Object reference not set to an instance of an object.
   at Microsoft.ML.ModelBuilder.Observable.ObservableModel.<ExecuteUpdateHandlerAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.ML.ModelBuilder.Observable.ObservableModel.<HandlePropertyUpdateAsync>d__28.MoveNext() (Microsoft.ML.ModelBuilder.Utils.Logger.Debug)
2022-01-23 18:29:00.6979 DEBUG AutoMLType: Octopus (Microsoft.ML.ModelBuilder.Utils.Logger.Debug)

2022-01-23 18:29:00.6979 TRACE [Source=TextLoader; Binding, Kind=Trace] Channel started (Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.AutoMLService_DiagnosticDataReceived)

=> // I left this part out because it's just stack trace....

===============================================Experiment Results=================================================
------------------------------------------------------------------------------------------------------------------
|                                                     Summary                                                    |
------------------------------------------------------------------------------------------------------------------
|ML Task: ImageClassification                                                                                |
|Dataset:                                                                                |
|Label : Label                                                                                |
|Total experiment time :<PHONE_NUMBER> Secs                                                                        |
|Total number of models explored: 1                                                                              |
------------------------------------------------------------------------------------------------------------------
 (Microsoft.ML.ModelBuilder.Utils.Logger.Info)
2022-01-23 18:32:14.2134 INFO |                                              Top 1 models explored                                             |
------------------------------------------------------------------------------------------------------------------
|     Trainer                              MicroAccuracy  MacroAccuracy  Duration #Iteration                     |
|1    ImageClassification                         1.0000         1.0000     193.4          1                     |
------------------------------------------------------------------------------------------------------------------
 (Microsoft.ML.ModelBuilder.Utils.Logger.Info)

=> // I left this part out because it's just stack trace....

Updating nuget dependencies... (Microsoft.ML.ModelBuilder.Utils.Logger.Info)
2022-01-23 18:32:22.4499 INFO Installing nuget package, package ID: Microsoft.ML, package Version: 1.6.0 (Microsoft.ML.ModelBuilder.Utils.Logger.Info)
2022-01-23 18:32:22.4499 DEBUG Value cannot be null.
Parameter name: project
   at NuGet.VisualStudio.VsPackageInstallerServices.GetInstalledPackages(Project project)
   at Microsoft.ML.ModelBuilder.Utils.Utilities.<InstallNugetPackageAsync>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.<UpdateNugetDependenciesAsync>d__119.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.ML.ModelBuilder.ViewModels.TrainViewModel.<GenerateCodeBehindFilesAsync>d__118.MoveNext() (Microsoft.ML.ModelBuilder.Utils.Logger.Debug)

@21r8390 Sorry for the delay here. Is one of the projects in your solution unloaded?

I haven't written back for a while because I was still testing. It's super fun! ☺
There were some updates, which I have not followed closely. I do not know why, but this error no longer occurs.


update OceanBaseCEContainer for new docker images

Our team has refactored the docker image recently, in addition to bugfixes, some parameters have also been adjusted. https://github.com/oceanbase/docker-images/tree/main/oceanbase-ce
We will ensure the future versions of the long-term support tag 4.2.1-lts will be backward compatible with existing parameters, and will continue to incorporate bug fixes and other optimizations.

@eddumelendez PTAL

Thanks, @whhe !


Update sort-comp for React 16.3+

The sort-comp rule will need to be updated to include the new lifecycle methods (while also keeping the older ones, optionally?).  These include:
getDerivedStateFromProps
getSnapshotBeforeUpdate
UNSAFE_componentWillMount
UNSAFE_componentWillReceiveProps
UNSAFE_componentWillUpdate

Also, componentDidCatch is not listed in current sort-comp rule

I made an attempt to add this feature with #1771
Would love to hear any feedback/suggestions

Closed in #1771.


Draft: Remove OrderedDicts etc except where empirically necessary

It would be good to do a few more checks on this and take a closer look to make sure its what we want before merging, but this seems to preserve the creation order of all workspace objects, as discussed in #936.

@kcormi  - a very concrete check would be to run  text2workspace.py 125.5/comb_hbb.txt -m 125.5 (from the cms Higgs observation area) twice with -v 3 and check the output diff. If they are the same with this PR, then I think you've narrowed down the changes that were really crucial and we can merge this one

@nucleosynthesis, yes good suggestion. I tested this now, and there seems to be a difference in a RooProdPdf print out which I don't understand. I seem to get a same/similar one with the current main branch though. So I'm not sure if its actually related, or if I've just made a silly mistake in trying to test it.
I'll need to investigate a little later, but I'll try to wrap this up soon so we can merge it.

It seems in my tests that I still get a few lines of differences, even when using the fully ordered collections.
It's always just a few lines with the RooProdPdfs, and the difference doesn't seem to be in the pdf itself, but that in one of the two lines printing the pdf out, there is also an error of the style
[#0] ERROR:InputArguments -- RooArgSet::checkForDup: ERROR argument with name CMS_vhbb_stats_TT_ZmmLoose7TeV is already in this set

I'm not sure if it's really a problem, I suspect its not, but I'll try to see if I can track it down regardless.

Here is the stack trace for where the ERROR comes from:
Thread 1 "python" hit Breakpoint 1, RooArgSet::checkForDup (this=0x5555690d37e8, var=..., silent=<optimized out>)
    at /home/rembserj/code/root/roofit/roofitcore/src/RooArgSet.cxx:285
285	   coutE(InputArguments) << "RooArgSet::checkForDup: ERROR argument with name " << var.GetName() << " is already in this set" << endl;
(gdb) bt
#0  RooArgSet::checkForDup (this=0x5555690d37e8, var=..., silent=<optimized out>)
    at /home/rembserj/code/root/roofit/roofitcore/src/RooArgSet.cxx:285
#1  0x00007fffdda81b4c in RooArgSet::canBeAdded (this=<optimized out>, arg=..., silent=<optimized out>)
    at /home/rembserj/code/root/roofit/roofitcore/inc/RooArgSet.h:190
#2  0x00007fffddac9102 in RooAbsCollection::add (this=this@entry=0x5555690d37e8, var=...,
    silent=silent@entry=false) at /home/rembserj/code/root/roofit/roofitcore/src/RooAbsCollection.cxx:436
#3  0x00007fffd780ada4 in RooCollectionProxy<RooArgSet>::add (silent=<optimized out>,
    shapeServer=<optimized out>, valueServer=<optimized out>, var=..., this=<optimized out>)
    at /home/rembserj/spaces/master/install/include/root/RooCollectionProxy.h:192
#4  RooCollectionProxy<RooArgSet>::add (silent=<optimized out>, var=..., this=<optimized out>)
    at /home/rembserj/spaces/master/install/include/root/RooCollectionProxy.h:114
#5  SimpleCacheSentry::addVars (this=this@entry=0x5555690d34f0, vars=...)
    at /home/rembserj/HiggsAnalysis/CombinedLimit/src/SimpleCacheSentry.cc:43
#6  0x00007fffd782afce in FastVerticalInterpHistPdf2Base::initBase (this=0x5555690d3020)
    at /home/rembserj/HiggsAnalysis/CombinedLimit/src/VerticalInterpHistPdf.cc:826
#7  FastVerticalInterpHistPdf2Base::initBase (this=0x5555690d3020)
    at /home/rembserj/HiggsAnalysis/CombinedLimit/src/VerticalInterpHistPdf.cc:813
#8  0x00007fffd782b415 in FastVerticalInterpHistPdf2::evaluate (this=0x5555690d3020)
    at /home/rembserj/HiggsAnalysis/CombinedLimit/src/VerticalInterpHistPdf.cc:895

Indeed, the SimpleCacheSentry (whatever that does) uses a RooArgSet as a container, and is therefore not able to deal with different RooAbsArg instances that have the same name:
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/blob/main/src/SimpleCacheSentry.cc#L32
There is a check if (_deps.containsInstance(*a)) continue; to make sure the same instance is not added twice, but it seems this FastVerticalInterpHistPdf2 uses a list of coefficient, where some coefficients have the same name but are different RooAbsArgs. This might or might not be a bigger problem: RooFit is inconsistent in treating different instances with the same name. For example in a RooWorkspace, there can't be different variables with the same name, everything is unique. But when objects are then copied when doing the NLL fit, there might be independent copies with the same name, depending on what the framework does. This situation should be avoided, because in the worst case these independent instances might get out of sync in value, even though they were mathematically intended to be the same.
I will take a look at text2workspace.py, maybe it's easy to see where these different RooAbsArg instances with the same name come from.
By the way: this is the reason why RooFit models are often magically fixed by writing the workspace to a file and reading it back: like this, all variables with the same name are de-duplicated, which is usually the intent of the model builder.

Confirmed, the errors were harmless: we just tried to fill a collection with the same set of objects twice, and the second time you get an error instead of adding more elements. Can be avoided: https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/952

Thanks @guitargeek -- I will merge this one. I need to double check #952 a little before merging it, but looks fine.


refactor(dom): use native ES6 Map

As stated in the README of es6-map, the algorithmic complexity of the poly-/ponyfill is O(n) not
O(1). As almost all browsers have native ES6 Map support nowadays, we should use them and only
polyfill if needed

Perfect PR, thanks @jvanbruegge


Host usage gif on GitHub's CDN

How to do this: https://vinkla.com/2015/upload-images-github/

Thanks for the PR @svenluijten 👍
Haven't added gifs to a repo README before so ended up taking the easy way out 🙈

Haha, no worries. It's a very little-known trick on GitHub actually 😄


[Communication - Identity] CommunicationIdentityClient [Playback/Live] [AAD] successfully creates a user failing in nightly runs

Communication - Identity nightly test runs are failing with:

Error message:
EnvironmentCredential authentication failed.(status code 400). More details: Cannot read properties of undefined (reading 'error')
Stack trace:
AuthenticationError: EnvironmentCredential authentication failed.(status code 400).
More details:
Cannot read properties of undefined (reading 'error')
at D:\a_work\1\s\common\temp\node_modules.pnpm@azure+identity@2.0.0-beta.6\node_modules@azure\identity\src\credentials\environmentCredential.ts:153:39
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at trace (D:\a_work\1\s\common\temp\node_modules.pnpm@azure+identity@2.0.0-beta.6\node_modules@azure\identity\src\util\tracing.ts:37:20)
at DefaultAzureCredential.getToken (D:\a_work\1\s\common\temp\node_modules.pnpm@azure+identity@2.0.0-beta.6\node_modules@azure\identity\src\credentials\chainedTokenCredential.ts:67:17)
at tryGetAccessToken (D:\a_work\1\s\sdk\core\core-http\src\policies\bearerTokenAuthenticationPolicy.ts:82:26)
at beginRefresh (D:\a_work\1\s\sdk\core\core-http\src\policies\bearerTokenAuthenticationPolicy.ts:93:35)
at BearerTokenAuthenticationPolicy.sendRequest (D:\a_work\1\s\sdk\core\core-http\src\policies\bearerTokenAuthenticationPolicy.ts:249:25)
at ThrottlingRetryPolicy.sendRequest (D:\a_work\1\s\sdk\core\core-http\src\policies\throttlingRetryPolicy.ts:53:22)
at IdentityRestClient.sendOperationRequest (D:\a_work\1\s\sdk\core\core-http\src\serviceClient.ts:519:23)
at CommunicationIdentityClient.createUser (D:\a_work\1\s\sdk\communication\communication-identity\src\communicationIdentityClient.ts:84:28)
at Context. (D:\a_work\1\s\sdk\communication\communication-identity\test\public\communicationIdentityClient.spec.ts:38:49)

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1158287&view=results

this was a temporary error that hasn't appeared again. currently, INT tests are failing due to a problem in the chat gateway (a service that we're calling). resolution is in progress.


ci(cd): remove dev dependencies from package-lock.json

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
172

Relevant Lines:
172

💛  - Coveralls


Relation comments are not being updated for incremental models

Describe the bug
Relation comments for incremental models are only persisted when the relation is first being created. On subsequent incremental runs an updated model description will not be persisted to the relation.
Steps To Reproduce

Create an incremental model with:

model.sql
{{
    config(
        materialized="incremental",
        persist_docs={"relation": true},
    )
}}
select 1 as id

schema.yml
version: 2
models:
  - name: model
    description: "Model Description"

dbt run
Change the model description
dbt run
Check the table comment: describe detail model. The table still has the old model description as table comment.

Expected behavior
After the second dbt run the new model description should be persisted as the table comment.
System information
The output of dbt --version:
Core:
  - installed: 1.8.3
  - latest:    1.8.3 - Up to date!

Plugins:
  - databricks: 1.8.3 - Up to date!
  - spark:      1.8.0 - Up to date!

The operating system you're using:
Ubuntu 22.04
The output of python --version:
Python 3.10.12
Additional context
I'm interested in contributing to this.

I've had a look at the code and it looks like the relation comments are typically persisted as part of the create sql statements, but the insert or merge statements of the incremental runs don't persist relation comments. The persist_docs macro is being called in the incremental materialization, but it only persists column comments currently.
I would propose to add the functionality to persist relation comments in the persist_docs macro if for_relation is set. And change the non-incremental calls to persist_docs to pass for_relation=false (it is true by default).


Fix compile warnings in mantis-connector-iceberg module

There are compile warnings in the code due to:

deprecated APIs
missing @Nullable/@NotNull annotations
incomplete javadocs
lambda can be replaced with method references
raw usage of generic types
unnecessary type parameters (like Map<String> m = new HashMap<String>())
anonymous class can be replaced with lambdas
... and more.

We don't need to solve all of them, but a good coding exercise is to address most those compile warnings when possible. Guidelines are:

Not change code logic, which should be addressed and filed PR separately
Not change public interfaces (class, methods and fields) that would break other modules or applications. But it's safe to rename private fields or methods when necessary.
Prefer readability to more concise code
Improve tests in the module is welcome but not required
Compile and pass all existing tests.

This tracks the effort for the mantis-connector-iceberg module to make the code change scoped.

Sounds good! Thanks for taking this up.


Landbot not showing on Android mobile

Bug
Expected Functionality
Landbot should appear on the resources page on Chrome on android
Actual Functionality
The bot does not appear to be loading
Steps to reproduce

Load the app
click on resources
wait

Screenshots
Device information

Device: Note9
OS: [e.g. iOS8.1]
Browser: Chrome
Version: [e.g. 22]

Other remarks

not sure if this is a bug. working now after a PWA update, but may resurface


openssl doesn't accept ring generated ed25519 key pairs

Rust snippet used to generated the ed25519 key:
extern crate ring; // "0.14" in Cargo.toml
extern crate pem; // "0.6" in Cargo.toml

use ring::rand::SystemRandom;
use ring::signature::Ed25519KeyPair;

fn main() {
	let system_random = SystemRandom::new();
	let key_pair_doc = Ed25519KeyPair::generate_pkcs8(&system_random).unwrap();
	let key_pair_serialized = key_pair_doc.as_ref().to_vec();
	let p = pem::Pem {
		tag : "PRIVATE KEY".to_string(),
		contents : key_pair_serialized,
	};
	println!("{}", pem::encode(&p));
}

Example for a generated key:

-----BEGIN PRIVATE KEY-----
MFMCAQEwBQYDK2VwBCIEIGIsMDbeo5rdiq208eOfvZlm3K9SHOsDUt2FI2js1z9Y
oSMDIQDN0z6SeMgqmKvsBQ8E8qcQW5ZJebea7drLQyq7513ovQ==
-----END PRIVATE KEY-----

If you put the Rust generated key into a file key.pem and then create a CSR and try to sign it, you'll get an error:
$ openssl req -new > cert.csr
$ openssl x509 -in cert.csr -out cert.pem -req -signkey key.pem -days 1001
Signature ok
subject=C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
Getting Private key
unable to load Private key
140392011777152:error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag:../crypto/asn1/tasn_dec.c:1130:
140392011777152:error:0D08303A:asn1 encoding routines:asn1_template_noexp_d2i:nested asn1 error:../crypto/asn1/tasn_dec.c:553:Field=attributes, Type=PKCS8_PRIV_KEY_INFO
140392011777152:error:0907B00D:PEM routines:PEM_read_bio_PrivateKey:ASN1 lib:../crypto/pem/pem_pkey.c:88:

Example CSR (the CSR uses RSA-2048):

-----BEGIN CERTIFICATE REQUEST-----
MIICijCCAXICAQAwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgMClNvbWUtU3RhdGUx
ITAfBgNVBAoMGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMiGv8b1MfACgoi+Wa/hus6/JmzoFO8MTpQtGlJl
sKuHgnaT7OPcOLDKUUiovagsQUU5ebLXn5KoXb9X8YIgEiZ+MJY6cUMQ0Hyqs9Rv
xsy54EsZ5rNidZaPjTixBY7KySGWWS9nW2AsL6HkMh1Oc6LGB02CNtHkGyGcDR2n
znVLWm6OY8KwkN1TP5PNXsCJ+cjLRHEhPD+tCzypkbFDmiriyPBqE4S9r71fWukF
YOyLI4yyEWWPF1znG55epDx3K4HdbqeFgXOE4hFM0KpFu8+cFPfhuliD+B1NYikl
kQqkhyIZSjtncCs95voXBnM1vk051mRSL4DieNTXOVZ750cCAwEAAaAAMA0GCSqG
SIb3DQEBCwUAA4IBAQDC7LQVAmWztt6+KEjDsgRAznus9FMtjuf9Q8e0q9+xu5sW
8hnr5kZEI/khxR+7GIU6miFN/Fe6pPoVXFoQZ3iC0LgR9uTbFFNlzT329MS2ZGyt
9Mkfqqf574zR94AKElMM4lwiBTcrfq3y8sLE4eLDT6wHOavpUb2tqVwSf/RBKo6b
UYDpaG8FpbXC4edgMG+SpZCf8ZRXJuhD5TtM/diN0AcvNKi5SjuB/uj6uKEEJNUW
9MERdpiVQXR394xhw6cho4crMuDWa74S/3B77jCfcg9oahEqKZWXMVAXD+w/BW0h
q2rvPRcZ+b4Gb1r75Roos4VvZ8m7ytOm5ws2TFsE
-----END CERTIFICATE REQUEST-----

Generating an ed25519 key with openssl and using it to sign the CSR works great:
$ openssl x509 -in cert.csr -out cert.pem -req -signkey key2.pem -days 1001
Signature ok
subject=C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
Getting Private key

The version of the openssl CLI is 1.1.1b (ubuntu distro build).
See also https://github.com/est31/rcgen/issues/11 where I use the openssl library to load the private key and where it's giving me a similar "wrong tag" error (I've tried both versions 1.1.1b and 1.1.1c both fail).
See also https://github.com/briansmith/ring/issues/833 which is about the other direction: the default parsing function of ring for ed25519 keys is unable to read certificates generated by openssl at least by the default flags (dunno if there are custom flags/modes to generate certificates that ring wants). It seems that openssl and ring are incompatible to each other which is very sad :/.
If I compare the keys that ring generates with the keys that openssl generates, I note two differences: first the version field is set to 0 (v1) in openssl, while the version field is set to 1 (v2) in ring. Second, ring includes the public key while openssl doesn't. The version fields are set consistently by both to RFC 5958 which states:

version identifies the version of OneAsymmetricKey.  If publicKey
is present, then version is set to v2 else version is set to v1.

Maybe openssl is just unable to read the public key (v2 encoded keys)?
cc @briansmith author of ring.

ring generates PKSC#8 v2 for Ed25519 and (eventually) X25519 so that the public key can be included, so that the pairwise consistency check required by some NIST standards can be done by the receiving side. (NIST doesn't have standards for Ed25519 yet but I expect they will require a pairwise consistency check like they do for RSA, ECDSA, and ECDH if/when they allow Ed25519.)

For the format OpenSSL uses, see RFC 8410.

But using the example from the RFC that includes the public key doesn't seem to work.

For the format OpenSSL uses, see RFC 8410.
But using the example from the RFC that includes the public key doesn't seem to work.

It's PKCS#8 v2 format, like ring generates.

But using the example from the RFC that includes the public key doesn't seem to work.

fwiw, ring doesn't accept it either. Probably because of the additional attribute.

#10468 is a new issue specifically asking for PKCS#8 v2.  We can close this one.

Yeah I realized later that this bug was formulated in a bad way. Opening a new one is a good idea.