[Enhancement] support prune shuffle columns

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

like sql:
select * from t0 join[shuffle] t1 on t0.v2 = t1.v2 and t0.v3 = t1.v3;

multi join on-clause predicate, we need shuffle by all columns now, the plan:
MySQL td> explain select * from t0 join[shuffle] t1 on t0.v2 = t1.v2 and t0.v3 = t1.v3;
+-------------------------------------------------------------+
| Explain String                                              |
+-------------------------------------------------------------+
| .............                                               |
| PLAN FRAGMENT 1                                             |
|  OUTPUT EXPRS:                                              |
|   PARTITION: HASH_PARTITIONED: 2: v2, 3:v3                  |
|                                                             |
|   STREAM DATA SINK                                          |
|     EXCHANGE ID: 05                                         |
|     UNPARTITIONED                                           |
|                                                             |
|   4:HASH JOIN                                               |
|   |  join op: INNER JOIN (PARTITIONED)                      |
|   |  hash predicates:                                       |
|   |  colocate: false, reason:                               |
|   |  equal join conjunct: 2: v2 = 5: v2                     |
|   |  equal join conjunct: 3: v3 = 6: v3                     |
|   |                                                         |
|   |----3:EXCHANGE                                           |
|   |                                                         |
|   1:EXCHANGE                                                |
|                                                             |
| PLAN FRAGMENT 2                                             |
|  OUTPUT EXPRS:                                              |
|   PARTITION: RANDOM                                         |
|                                                             |
|   STREAM DATA SINK                                          |
|     EXCHANGE ID: 03                                         |
|     HASH_PARTITIONED: 5: v2, 6: v3                          |
|                                                             |
|   2:OlapScanNode                                            |
|      TABLE: t1                                              |
| .............                                               |
|                                                             |
| PLAN FRAGMENT 3                                             |
|  OUTPUT EXPRS:                                              |
|   PARTITION: RANDOM                                         |
|                                                             |
|   STREAM DATA SINK                                          |
|     EXCHANGE ID: 01                                         |
|     HASH_PARTITIONED: 2: v2, 3.v3                           |
|                                                             |
|   0:OlapScanNode                                            |
|      TABLE: t0                                              |

the enhance:

don't need compute multi-columns hash
imporve global runtime filter effect

after
MySQL td> explain select * from t0 join[shuffle] t1 on t0.v2 = t1.v2 and t0.v3 = t1.v3;
+-------------------------------------------------------------+
| Explain String                                              |
+-------------------------------------------------------------+
| .............                                               |
| PLAN FRAGMENT 1                                             |
|  OUTPUT EXPRS:                                              |
|   PARTITION: HASH_PARTITIONED: 2: v2                        |
|                                                             |
|   STREAM DATA SINK                                          |
|     EXCHANGE ID: 05                                         |
|     UNPARTITIONED                                           |
|                                                             |
|   4:HASH JOIN                                               |
|   |  join op: INNER JOIN (PARTITIONED)                      |
|   |  hash predicates:                                       |
|   |  colocate: false, reason:                               |
|   |  equal join conjunct: 2: v2 = 5: v2                     |
|   |  equal join conjunct: 3: v3 = 6: v3                     |
|   |                                                         |
|   |----3:EXCHANGE                                           |
|   |                                                         |
|   1:EXCHANGE                                                |
|                                                             |
| PLAN FRAGMENT 2                                             |
|  OUTPUT EXPRS:                                              |
|   PARTITION: RANDOM                                         |
|                                                             |
|   STREAM DATA SINK                                          |
|     EXCHANGE ID: 03                                         |
|     HASH_PARTITIONED: 5: v2                                 |
|                                                             |
|   2:OlapScanNode                                            |
|      TABLE: t1                                              |
| .............                                               |
|                                                             |
| PLAN FRAGMENT 3                                             |
|  OUTPUT EXPRS:                                              |
|   PARTITION: RANDOM                                         |
|                                                             |
|   STREAM DATA SINK                                          |
|     EXCHANGE ID: 01                                         |
|     HASH_PARTITIONED: 2: v2                                 |
|                                                             |
|   0:OlapScanNode                                            |
|      TABLE: t0                                              |

run all

[FE PR Coverage check]
:heart_eyes: pass : 106 / 108 (98.15%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/OutputPropertyDeriver.java
2
3
66.67%

:large_blue_circle:
com/starrocks/sql/optimizer/PruneShuffleColumnRule.java
89
90
98.89%

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/ChildOutputPropertyGuarantor.java
5
5
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PreAggregateTurnOnRule.java
3
3
100.00%

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 106 / 108 (98.15%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/OutputPropertyDeriver.java
2
3
66.67%

:large_blue_circle:
com/starrocks/sql/optimizer/PruneShuffleColumnRule.java
89
90
98.89%

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/ChildOutputPropertyGuarantor.java
5
5
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PreAggregateTurnOnRule.java
3
3
100.00%

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 106 / 108 (98.15%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/OutputPropertyDeriver.java
2
3
66.67%

:large_blue_circle:
com/starrocks/sql/optimizer/PruneShuffleColumnRule.java
89
90
98.89%

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/ChildOutputPropertyGuarantor.java
5
5
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PreAggregateTurnOnRule.java
3
3
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 115 / 119 (96.64%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/OutputPropertyDeriver.java
2
3
66.67%

:large_blue_circle:
com/starrocks/sql/optimizer/PruneShuffleColumnRule.java
98
101
97.03%

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/ChildOutputPropertyGuarantor.java
5
5
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PreAggregateTurnOnRule.java
3
3
100.00%

Please run daily tests

[FE PR Coverage check]
:heart_eyes: pass : 115 / 119 (96.64%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/OutputPropertyDeriver.java
2
3
66.67%

:large_blue_circle:
com/starrocks/sql/optimizer/PruneShuffleColumnRule.java
98
101
97.03%

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/ChildOutputPropertyGuarantor.java
5
5
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PreAggregateTurnOnRule.java
3
3
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 116 / 120 (96.67%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/OutputPropertyDeriver.java
2
3
66.67%

:large_blue_circle:
com/starrocks/sql/optimizer/PruneShuffleColumnRule.java
98
101
97.03%

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
2
2
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/ChildOutputPropertyGuarantor.java
5
5
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PreAggregateTurnOnRule.java
3
3
100.00%


Remove unused nats dependencies and submodules

This commit removes unnecessary and unused test setup from the traffic
controller which required four separate nats related dependencies. Those
dependencies were:

github.com/cloudfoundry/yagnats
github.com/nats-io/gnatsd
github.com/nats-io/nats
github.com/nats-io/nuid

Also, within scripts/test we were installing github.com/nats-io/gnatsd
which is no longer necessary. This commit removes that line as well.

I was able to successfully run LATs and scripts/test.


Update user.py

edit reset password link
In case I messed something up, the link for the reset is supposed to be:
https://project-rio-frontend.vercel.app
/login/reset_password/code that gets sent sent via email

do you want the password reset link itself or the base url
for ex, url = https://project-rio-frontend.vercel.app/
and add the password reset portion
or url = https://project-rio-frontend.vercel.app/login/reset_password/codesentinemail

@MORImementos just the base url. If the password reset url changes we'll need to change the section you changed anyway. But the base should be a const

Perfect, thanks Mori


The formula for Iab from Buhmann only works for a.energy = b.energy

https://github.com/DavisThuillier/Ludwig.jl/blob/58fea54dfdad00e7f5e72489b2dddddb42e59dfc/src/integration.jl#L163
If a.energy and b.energy are close to each other but not exactly equal, one would need to use a modified formula which accounts for the small difference between them, similarly to what is done for electron_electron.
But currently the energy contours are exactly the same for all bands (right?), so I imagine this if condition would only be satisfied when a.energy = b.energy anyway.

The energy contours are exactly the same for all the bands, so this condition is indeed satisfied only when a.energy = b.energy. However, before when the centroid of each patch was used for the representative momentum instead of how it is currently done, this check ensured that small energy differences would still be read as living within the same annulus. A much finer check/an annulus index check could now be used instead.


Booking  enhancements

Some features have been requested by Centraliens:

[ ] #141
[x] improves the visibility of accepted / rejected bookings
[x] #138
[x] #139
[x] #140

Some more enhancements that we discussed today :

[ ] The note shouldn't be mandatory
[ ] Show applicant's name on reservation's details (GET endpoint "/bdebooking/bookings/{booking_id}/applicant" exists, and getting booking by id as it is already used certainly also gives the applicant's user id)
[ ] Show entity ("Pour qui?") on each reservation on the calendar or on reservation's details
[ ] It should be possible to remove a room (the endpoint exists, and it is needed because "Barbecue" should be removed)

[ ]  allow Booking managers to accept or reject a booking that is already started

It is already possible for managers to accept or reject a booking that is already started but not ended.
Should it still be possible to accept or reject  a booking that has ended ?

[ ] add the creation date in Booking objects
[ ] sort bookings by creation date instead of reservation date

[ ] Allow admins to confirm past reservations

Solved by #185


Update Composer dependencies (2022-01-05-00-10)

Visual regression test passed!
View the visual regression test report


Uncaught Error: Atom can only handle files < 2MB for now.

[Enter steps to reproduce below:]

...
...

Atom Version: 0.166.0
System: Mac OS X 10.10.2
Thrown From: Atom Core
Stack Trace
Uncaught Error: Atom can only handle files < 2MB for now.
At /Applications/Atom.app/Contents/Resources/app/src/project.js:355

Error: Atom can only handle files < 2MB for now.
  at Project.module.exports.Project.buildBuffer (/Applications/Atom.app/Contents/Resources/app/src/project.js:355:15)
  at Project.module.exports.Project.bufferForPath (/Applications/Atom.app/Contents/Resources/app/src/project.js:332:63)
  at Project.module.exports.Project.open (/Applications/Atom.app/Contents/Resources/app/src/project.js:286:19)
  at Workspace.module.exports.Workspace.openUriInPane (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:485:29)
  at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:412:19)
  at Ipc.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:45:32)
  at Ipc.emit (events.js:110:17)
  at process.<anonymous> (/Applications/Atom.app/Contents/Resources/atom/renderer/api/lib/ipc.js:22:29)
  at process.emit (events.js:118:17)

Commands
  2x -1:41.5 core:select-down (atom-text-editor.editor)
     -1:40.1 core:backspace (atom-text-editor.editor)
     -1:38.7 core:select-down (atom-text-editor.editor)
     -1:38.1 core:backspace (atom-text-editor.editor)
     -1:37.0 core:move-down (atom-text-editor.editor)
     -1:36.7 core:move-up (atom-text-editor.editor)
  2x -1:36.4 core:select-down (atom-text-editor.editor)
     -1:35.6 core:move-up (atom-text-editor.editor)
  2x -1:34.0 core:move-down (atom-text-editor.editor)
     -1:32.0 core:select-down (atom-text-editor.editor)
     -1:31.7 core:move-up (atom-text-editor.editor)
     -1:31.0 core:save (atom-text-editor.editor)
     -0:04.3 core:move-right (atom-text-editor.editor)
     -0:04.1 core:move-up (atom-text-editor.editor)
  4x -0:03.8 core:select-right (atom-text-editor.editor)
  6x -0:00.0 core:save (atom-text-editor.editor)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "fontSize": 13,
    "invisibles": {}
  }
}

Installed Packages
# User
Sublime-Style-Column-Selection, v1.2.2
gulp-snippets, v0.6.0
language-scala, v1.1.0
linter-javac, v0.1.3
linter-scalac, v0.3.3
scala-format, v0.1.2
script, v2.16.0

# Dev
No dev packages

This question has been asked a ton times :joy:
Please have a look at #307

Duplicate of atom/atom#4421 and atom/atom#307. Please subscribe there for updates.


increase the packet number after version negotiation and retry

Fixes #1637.
Note that the same mechanism (using return values of session.closeForRecreating()) could be used to carry over the RTT stats from one session to the next.

Codecov Report

Merging #1685 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1685      +/-   ##
==========================================
- Coverage    87.2%   87.18%   -0.03%
==========================================
  Files          97       97
  Lines        6291     6293       +2
==========================================
  Hits         5486     5486
- Misses        573      575       +2
  Partials      232      232

Impacted Files
Coverage Δ

server.go
86.29% <ø> (ø)
:arrow_up:

session.go
73.3% <100%> (-0.24%)
:arrow_down:

client.go
82.27% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Migrate from cloud-platform-tech-docs-publisher to tech-docs-github-pages-publisher

This PR migrates this repository from cloud-platform-tech-docs-publisher:1.1 to tech-docs-github-pages-publisher:1.2 👍🏼
It removes the need to hold Ruby files in this repository and uses the Docker image directly, simplifying the GitHub workflow. It also means dependabot won't report out of date packages as they're not used apart from generating the static files for this site within the GitHub workflow.

Hopefully resolves #64 @digitalronin?


Add proximal operators

Quadratic objective function, smooth objective functions, smooth objective functions with constraints

Codecov Report

Merging #2 (69d02c0) into master (9a30474) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head 69d02c0 differs from pull request most recent head 01c88a6. Consider uploading reports for the commit 01c88a6 to get more accurate results

@@          Coverage Diff           @@
##           master      #2   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files           4       4
  Lines         154     181   +27
======================================
- Misses        154     181   +27

Impacted Files
Coverage Δ

src/proximal.jl
0.00% <0.00%> (ø)

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 9a30474...01c88a6. Read the comment docs.


Go. Empty test file is generated for samples.go

Description
Empty test file is generated for samples.go
To Reproduce

Open IntelliJ Idea 2022.3 Ultimate
Install plugin built from unit-test-bot/rc2023.3 branch
Create a new Go project
Copy-paste samples.go` into it
Turn 'Experimental languages support' on
Use plugin to generate tests for any/all of the samples

Expected behavior
Tests are supposed to be generated.
Actual behavior
Empty test file is generated.
Visual proofs (screenshots, logs, images)
package simple

Environment
Windows 10 Pro
IntelliJ Idea 2022.3 Ultimate
Go 1.20.1
Additional context
In UTBotJava project tests are generated.
Mar24Go.zip

@Markoutte FYI

Can you delete file simple/supported_types.go and try again?

Can you delete file simple/supported_types.go and try again?

That helped. Will check with both release versions..


MM-17340 - Updating post permalink css

Summary
MM-17340 - Updating post permalink css
Ticket Link
https://mattermost.atlassian.net/browse/MM-17340

Removed QA reviewer; not required before merge. Will be tested post-merge.


added a logger option so we can log errors

Added a logger configuration option so we can log errors.
Log exceptions
Added an explanation about what will happen if no server information is configured in the gem

@adriancole

It fails, I have the feeling jruby is telling me something is wrong. I'll check it tomorrow

#15  supersedes this


typescript

Would you be open to migrating the lib to typescript?
I am on my way to do it in my fork but want to ask you first. Cause merging will get very hard if one is in JS and the other in TS

@farfromrefug
I have merged the typescript version to the master branch please take a look and see if it fits your needs.
Thanks a lot for the help!


API Implement campaign item edit button

Makes the "edit" button on campaign preview point to the actual edit url for each item.
Removes the non-functional "extra options" menu for the time being.
See https://silverstripe.atlassian.net/browse/OSS-1687

Yet again rebased.


Library version 1.7 does not work with Android 6.0

Hi.
With Version 1.7 the ProgressWheel does not show in Android 6 devices, but it works properly with previous versions (Android 5,4…).
But if I downgrade to previous release, version 1.5, ProgressWheel appears correctly with every Android version.
So, the problem is that using version 1.7 of your library, ProgressWheel does not show with Android 6.
I’ve used genymotion to test it: "PREVIEW: Google Nexus 5X -6.0.0 API 23-1080x1920"
Thanks!

I just tested it in Marshmallow (in a Genymotion emulator) and works correctly. Can you check if you have the animations enabled in the emulator? (in the developer options) The main change in 1.7 is that the progress wheel now follows the animation preferences.

Tested on Nexus 5x 6.0.1 (real device), works like a charm :)

I'm closing this as it seems its working properly.

I see someone is back :)


Support existing connectors with Spark local mode in LocalProcessor

What is the purpose of the change
This pull request supports in LocalProcessor all the connectors that have been supported in SparkProcessor.
Brief change log

Add support to read/write with SparkProcessor-supported connectors in LocalProcessor with Spark local mode.
Add test for DataGenSource, PrintSink and BlackHoleSink in LocalProcessorITTest.

Verifying the changes

Most changes in this PR has been covered by the added it tests.
LocalProcessor's ability to read/write HDFS is covered in the e2e example here.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? docs

LGTM! @lindong28 Could you take another look at this PR?

Thanks for the update. LGTM.


3 errors when used in Apple TV project

Xcode 7.1 b3

AFNetworking/AFSecurityPolicy.m:30:27: Implicit declaration of function 'SecItemExport' is invalid in C99

AFNetworking/AFSecurityPolicy.m:30:46: Use of undeclared identifier 'kSecFormatUnknown'

AFNetworking/AFSecurityPolicy.m:30:65: Use of undeclared identifier 'kSecItemPemArmour'

Are you using the 3_0_0_branch? We have tvOS support there.

no, sorry!


[BUG]Sound doesnt work

The sound doesnt work for me.
The click sound doesnt work and the trade sounds doesnt work.
I have the newest one.

It looks like it fixed it, i just had to assign my soundcard\dac to the application in the advanced options for sound, in the app volume\device settings.

im glad that you solved your issue


Send player from specific server [improvement]

It would be coool if you could use a command like
/send Hub-1 Hub-2
in order to teleport players from Hub-1 server to Hub-2 server
Thanks for your time!

This sounds like a great feature to add, however, I am not entirely sure how the plugin should act if there is a player with the same name as a server. Maybe I should add a prefix? (eg: s:server, p:playername)

Well for the server can be used @ or # in front of the server name and then for the players just the name

I have implemented this in build https://github.com/OskarsMC-Plugins/send/actions/runs/843350433, if you have any issues with the feature please open a new issue.


Remove timestamp field from Leaf

Closes #2195
This PR:
Removes timestamp field from Leaf and StoredView.
This PR does not:
Do anything else
Key places to review:
crates/types/src/data.rs

@shenkeyao fixed conflicts, please re-approve
And we have new and exciting CI failures I guess sigh


Azure Vote go dependencies no longer exist

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
These repositories no longer exist, therefore the application does not work.
https://github.com/Azure-Samples/azure-service-operator-samples/blob/480b78f57914e15caf85dcf53044beb7d1201597/azure-votes-sql/cmd/root.go#L24
https://github.com/Azure-Samples/azure-service-operator-samples/blob/480b78f57914e15caf85dcf53044beb7d1201597/azure-votes-postgresql/cmd/root.go#L17
Expected/desired behavior
The samples function.
OS and Version?
Windows 11 with WSL, Golang 1.20.6

@super-harsh - did you fix this in #43? I think halfway fixed because we removed azure-votes-sql, but azure-votes-postgresql I think still will not work as the application has disappeared.

The azure-votes-sql sample has been removed from the repository as it was a v1 sample.
For azure-votes-postgresql, "github.com/Azure/azure-votes-postgresql/pkg/azvotes" references to the internal module and it exists here already.

Closing as per the above.


Kid Section Added

1.Updated Dropdwon

2.On clicking Kid section

3.Created diff section for boys as by default u will go to girl kid section

Hope u like my work.This is done under gssoc-ext and hacktoberfest
Closes #324

@Tejashri-Taral thnku so much.Plzz assign level also which u think i deserve.

@TanviGandhotra Make sure when you raise pr mention issue no. too in future contribution!
I liked your work.

oh ok @Tejashri-Taral  its my first accepted hactoberfest and gssoc-ext pr so happy..


Geometric information parsing (McStas loader mainly)

NMX data loader should be able to retrieve...

detector rotation (x, y, z)
detector position
relative (x, y, z) list (?)
source position
sample position
fast vector list
slow vector list

In the McStas simulation file, there is a h5 group instrument/instrument_xml/ that contains geometry information of the instruments.
McStas loader should be able to parse the xml information to retrieve the information above.
TODO:

[ ] Compare instrument view with mantid

This is the script to load it with mantid and see the instrument view.
It takes at least 5 minutes on my machine to load 7 gigabytes of data... maybe we need to have smaller sample.
import scippneutron as snc
from mantid.simpleapi import Load
data = Load("../../../data/nmx/pulse5_z.h5")
dg = snc.from_mantid(data)
snc.instrument_view(dg)

The smaller sample I made for testing only has event data at the moment.
Does anyone know the best(easiest) way to retrieve part of event data in a nexus file but keep the rest the same...?

It takes at least 5 minutes on my machine to load 7 gigabytes of data... maybe we need to have smaller sample.

Is this an old file with the tiny "broken" chunk size that McStas was using until quite recently? Or is it only a problem with Mantid?

Does anyone know the best(easiest) way to retrieve part of event data in a nexus file but keep the rest the same...?

With Mantid, for a McStas file? Not possible, as far as I know.

Is this an old file with the tiny "broken" chunk size that McStas was using until quite recently? Or is it only a problem with Mantid?

I'm not familiar to that broken chunk issue.
Will it also take a while to load with scipp in this case...? It takes only 3 seconds with scipp.

Does anyone know the best(easiest) way to retrieve part of event data in a nexus file but keep the rest the same...?

With Mantid, for a McStas file? Not possible, as far as I know.

What a shame...
Last time I tried to copy everything with smaller number of event data, it complained while loading so I thought there were some fields that should have consistent length or dimensions.
I'll try again if needed... for now I'll not try to use the mantid with NMX files.


feat: get all whitelisted symbols

Purpose for this PR
Resolves #132

@CjHare
I had thought OZ String lib provided a way to go between string to uint256 but I was mistaken. Casting like I am is sketchy but OZ only provides UintToAddressMap, so this is a workaround to get StringToAddressMap which is ultimately what we want. Thoughts?

superceeded by #215


Account for case sensitivity of diff function

After selecting the 'Synchronize groups' option within 'Servers > LDAP', OPNsense kept stripping me from the 'admins' group. After a great deal of troubleshooting, I determined that the diff function used to examine commonality of group inclusion between LDAP and local is case sensitive, whereas LDAP schemas are not (by default).  It turns out I had added an 'Admins' group to LDAP to conform with the standard capitalization format of LDAP schemas and OPNsense was not recognizing or respecting the sameness between 'Admins' and 'admins' (the latter being OPNsense default).
Noting that duplicate LDAP groups cannot be configured (e.g. attempting to create a group 'admins' when 'Admins' already exists), I've proposed that all user & group variables are normalized with lowercase text prior to analysis.
Although it holds up in various testing scenarios I put it through, this will need to be tested and/or vetted out by developers, as it could be very hacky. Also note that I first installed pkg 'php72-mbstring' in an attempt to address this using mb_strtolower, though I'm not certain this pull request requires it. I'm far from a PHP expert...those 3 "simple" lines took me ~4 hours to arrive at!

@h-town https://github.com/opnsense/core/commit/9b72b85e41d4a78d793dbb96e2a3b10e6706e06a should to the trick, since both ends (OPNsense and the ldap provider) need to be matched case-insensitive.
RFC 2307 doesn't seem very clear about case sensitivity (I couldn't find it), but quite some  implementations seem to expect it to be case insensitive (such as AD)

fantastic, @AdSchellevis.  thanks for circling back to this!!


Dapr Topic subscription does not work on Azure Container Apps

Hello,
I don't see any subscriptions on my topic when deploying my api on azure container app.
In my app environment container, I created a component with the type "pubsub.azure.servicebus.topics" with the metadata for connecting to the namespace.
I've added the code in my api to subscribe to the topic :
app.UseCloudEvents();
app.UseEndpoints(endpoints =>
{
    endpoints.MapSubscribeHandler();
});

When I call "/dapr/subscribe"  in my api, I see the various endpoints with their topics.
Subscription is done locally using Tye.
Is there anything else I need to do for the subscription to work on azure container app?

It's okay, it was just an identity issue.


wineWow64Packages.unstable: 9.7 -> 9.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wineWow64Packages.unstable is: An Open Source implementation of the Windows API on top of X, OpenGL, and Unix
meta.homepage for wineWow64Packages.unstable is: https://www.winehq.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.8 with grep in /nix/store/qhcckdz6750wqx82nbhggprxwd1vl1a1-wine-wow64-9.8
found 9.8 in filename of file in /nix/store/qhcckdz6750wqx82nbhggprxwd1vl1a1-wine-wow64-9.8

Rebuild report (if merged into master) (click to expand)

23 total rebuild path(s)

23 package rebuild(s)

First fifty rebuilds by attrpath

grapejuice
pipelight
vinegar
wine-staging
wine64Packages.staging
wine64Packages.stagingFull
wine64Packages.unstable
wine64Packages.unstableFull
winePackages.staging
winePackages.stagingFull
winePackages.unstable
winePackages.unstableFull
wineWow64Packages.staging
wineWow64Packages.stagingFull
wineWow64Packages.unstable
wineWow64Packages.unstableFull
wineWowPackages.staging
wineWowPackages.stagingFull
wineWowPackages.unstable
wineWowPackages.unstableFull
yabridge
yabridgectl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qhcckdz6750wqx82nbhggprxwd1vl1a1-wine-wow64-9.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wineWow64Packages.unstable https://github.com/r-ryantm/nixpkgs/archive/c8819597e3a2821d3b3c46b750723c25f95104c2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c8819597e3a2821d3b3c46b750723c25f95104c2#wineWow64Packages.unstable

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qhcckdz6750wqx82nbhggprxwd1vl1a1-wine-wow64-9.8
ls -la /nix/store/qhcckdz6750wqx82nbhggprxwd1vl1a1-wine-wow64-9.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @avnik @7c6f434c @bendlas @jmc-figueira @reckenrode for testing.

@ofborg build wineWow64Packages.staging


fixes issue #17

This addresses an issue with installation of setuptools during initial 'make env'.
'make env' also tries to deal more gracefully with previous run of the target. Also, 'pip install' was removed from 'make test' since 'make env' now handles that.

Description

Motivation and Context

How Has This Been Tested?
started new conda environment to test 'make env'.

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

I can confirm that this PR fixes the problem. pip install -U was updating all packages to it's latest version, so seems like setuptools, which was previously installed by conda, needs to remain  in version 27.


Tv program is not available: stremerror.

I get this error on all programs, " - Tv program is not available: stremerror "
Solution:
Open the browser and start playing the episode.
Then start the script to download the episode.

Can you give more insights on your solution or if it still works? It didn't work for me


Loader segfaults in vkEnumeratePhysicalDevices

I have the following icd file installed for the mesa/intel driver :
{
    "file_format_version": "1.0.0",
    "ICD": {
        "library_path": "/home/user/src/lib/libvulkan_intel.so",
        "abi_versions": "1.0.3"
    }
}

And the library gets picked up by the loader according to strace :
access("/home/user/.local/share/vulkan/icd.d/intel_icd.json", F_OK) = 0
access("/home/user/.local/share/vulkan/icd.d/.", F_OK) = 0
access("/home/user/.local/share/vulkan/icd.d/..", F_OK) = 0
getdents(4, /* 0 entries */, 32768)     = 0
close(4)                                = 0
open("/home/user/.local/share/vulkan/icd.d/intel_icd.json", O_RDONLY) = 4
...
open("/home/user/src/lib/libvulkan_intel.so", O_RDONLY|O_CLOEXEC) = 4

Yet the loader segfault when the application calls vkEnumeratePhysicalDevices :
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff706445a in vkEnumeratePhysicalDevices (instance=0x7fffffffda00, pPhysicalDeviceCount=0x7fffffffd47c, pPhysicalDevices=0x7fffffffd8b8)
    at /home/user/src/Vulkan-LoaderAndValidationLayers/loader/trampoline.c:536
#2  0x000000000040341a in init_vk (vc=0x7fffffffd830, extension=0x408550 "VK_KHR_wayland_surface") at main.c:92
#3  0x000000000040534b in init_wayland (vc=0x7fffffffd830) at main.c:842
#4  0x0000000000405a22 in main (argc=1, argv=0x7fffffffdaf8) at main.c:983

Any tip on what I might be doing wrong here?

It looks like you are trying to use Wayland WSI extension, although it is unclear to me why this would cause a crash in EnumeratePhysicalDevices. However, by default the loader isn't built with Wayland support enabled in either LunarG SDK or Github CMake. Try enabling the Wayland support in CMake and see if the issue is resolved.
A second possibility is the "instance" parameter is bad in the call to vkEnumeratePhysicalDevices(), can you double check?
If not, do you have an app that reproduces the SEG FAULT you could share.  Or you could share a vktrace  of the app?

Thanks a lot, indeed recompiling with wayland support fixed the issue.
Now debugging another issue :)

If you have time actually, give a try at the vkcube (https://github.com/krh/vkcube) example on wayland.
I think there might be issues with the physical device and instance creation.


Added some ui tests and resolved bugs

Issue : #40 MacOS panel border bug
#53 Move Util class to src
image path error in windows.
Added iuibehavior tests

On windows the UI now looks like this:

On mac the UI looks like this:

Which is acceptable.


Pins versions of conan to < v2 in the ue4-full images

The conan library has some breaking changes in v2
This adds a build ARG to the full image and default to forcing the version of conan to <v2
Test in Linux on ubuntu 22, and in windows on windows server 2022.
resolves #305

Let's hope your testing was good enough! Merging.

Note that Conan < 2.0 now breaks with modern Python: https://github.com/adamrehn/ue4-docker/issues/336. I believe the proper fix is to teach conan-ue4cli to work with modern Conan instead of locking more and more things to ancient versions.


add function of temperature in the GCEED part

This PR enables to treat temperature in the GCEED part. To use function of temperature, please modify input files as follows.

&system
  iperiodic = 0
  al = 16d0, 16d0, 16d0
-  nstate = 5
+  nstate = 10
  nelem = 2
  natom = 4
  nelec = 10
+  temperature_k = 300.d0
/

@tt-ims san, could you check this PR?

test this please

@mn2007 san, ok, I will check it soon.

I confirmed that the finite-temperature option works. I approve this PR.

Thank you for merging, @tt-ims san.


2021-01-26 06:22:47,025 autosynth [DEBUG] > Running: git log 656b253c1a4bcad06d77d903e1d873e75ef57328 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2021-01-26 06:22:47,029 autosynth [DEBUG] > Running: git add -A
2021-01-26 06:22:47,072 autosynth [DEBUG] > Running: git status --porcelain
2021-01-26 06:22:47,111 autosynth [DEBUG] > Running: git commit -m build(nodejs): add build rules for Node.js library

PiperOrigin-RevId: 352815661

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Wed Jan 20 10:01:58 2021 -0800
Source-Repo: googleapis/googleapis
Source-Sha: 656b253c1a4bcad06d77d903e1d873e75ef57328
Source-Link: https://github.com/googleapis/googleapis/commit/656b253c1a4bcad06d77d903e1d873e75ef57328
[autosynth-redis-276 86c39c32] build(nodejs): add build rules for Node.js library
 1 file changed, 4 insertions(+), 4 deletions(-)
2021-01-26 06:22:47,137 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 86c39c32 build(nodejs): add build rules for Node.js library
2021-01-26 06:22:47,179 autosynth [DEBUG] > Running: git checkout autosynth-redis
Switched to branch 'autosynth-redis'
2021-01-26 06:22:47,208 autosynth [DEBUG] > Running: git diff HEAD..autosynth-redis-276 -- . :(exclude)synth.metadata
2021-01-26 06:22:47,212 autosynth [DEBUG] > Running: git diff HEAD..autosynth-redis-276 -- synth.metadata
2021-01-26 06:22:47,217 autosynth [DEBUG] > Running: git diff HEAD..autosynth-redis-277 -- . :(exclude)synth.metadata
2021-01-26 06:22:47,221 autosynth [DEBUG] > Running: git diff HEAD autosynth-redis-277
2021-01-26 06:22:47,226 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmpems2qohq/autosynth-redis-277.patch
error: cannot apply binary patch to 'Redis/metadata/V1/CloudRedis.php' without full index line
error: Redis/metadata/V1/CloudRedis.php: patch does not apply
error: cannot apply binary patch to 'Redis/metadata/V1Beta1/CloudRedis.php' without full index line
error: Redis/metadata/V1Beta1/CloudRedis.php: patch does not apply
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 104, in synthesize_loop
    return synthesize_loop_single_pr(toolbox, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 126, in synthesize_loop_single_pr
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 152, in synthesize_inner_loop
    synthesize_range(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 170, in synthesize_range
    toolbox.patch_merge_version(young)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 182, in patch_merge_version
    git.patch_merge(sub_branch, patch_file_path)
  File "/tmpfs/src/github/synthtool/autosynth/git.py", line 151, in patch_merge
    executor.check_call(["git", "apply", patch_file_path], cwd=git_repo_dir)
  File "/tmpfs/src/github/synthtool/autosynth/executor.py", line 29, in check_call
    subprocess.check_call(command, **args)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'apply', '/tmpfs/tmp/tmpems2qohq/autosynth-redis-277.patch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating redis. :sob:
Here's the output from running synth.py:
rom protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/Instance.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/Instance.php.
2021-01-27 06:12:03,036 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/ExportInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/ExportInstanceRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/FailoverInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/FailoverInstanceRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/OperationMetadata.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/OperationMetadata.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpgradeInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpgradeInstanceRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ImportInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ImportInstanceRequest.php.
2021-01-27 06:12:03,039 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsDestination.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsDestination.php.
2021-01-27 06:12:03,039 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/CreateInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/CreateInstanceRequest.php.
2021-01-27 06:12:03,039 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsSource.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsSource.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GetInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GetInstanceRequest.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpdateInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpdateInstanceRequest.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/DeleteInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/DeleteInstanceRequest.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesResponse.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesResponse.php.
2021-01-27 06:12:03,041 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Instance.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Instance.php.
2021-01-27 06:12:03,041 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ExportInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ExportInstanceRequest.php.
2021-01-27 06:12:03,049 synthtool [WARNING] > No replacements made in src/**/V*/**/*.php for pattern final class, maybe replacement is no longer needed?
WARNING:synthtool:No replacements made in src/**/V*/**/*.php for pattern final class, maybe replacement is no longer needed?
2021-01-27 06:12:03,056 synthtool [WARNING] > No replacements made in src/**/V*/**/*.php for pattern public function ([s|g]\w{3,})Unwrapped, maybe replacement is no longer needed?
WARNING:synthtool:No replacements made in src/**/V*/**/*.php for pattern public function ([s|g]\w{3,})Unwrapped, maybe replacement is no longer needed?
2021-01-27 06:12:03,232 synthtool [WARNING] > No replacements made in src/**/V*/**/*.php for pattern (.{0,})\]\((/.{0,})\), maybe replacement is no longer needed?
WARNING:synthtool:No replacements made in src/**/V*/**/*.php for pattern (.{0,})\]\((/.{0,})\), maybe replacement is no longer needed?
2021-01-27 06:12:03,232 synthtool [DEBUG] > Wrote metadata to synth.metadata.
DEBUG:synthtool:Wrote metadata to synth.metadata.
2021-01-27 06:12:03,317 autosynth [INFO] > Changed files:
2021-01-27 06:12:03,318 autosynth [INFO] > M Redis/metadata/V1/CloudRedis.php
 M Redis/metadata/V1Beta1/CloudRedis.php
 M Redis/synth.metadata
2021-01-27 06:12:03,318 autosynth [DEBUG] > Running: git log ceaaf31b3d13badab7cf9d3b570f5639db5593d9 -1 --no-decorate --pretty=%s
2021-01-27 06:12:03,322 autosynth [DEBUG] > Running: git log ceaaf31b3d13badab7cf9d3b570f5639db5593d9 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2021-01-27 06:12:03,325 autosynth [DEBUG] > Running: git add -A
2021-01-27 06:12:03,365 autosynth [DEBUG] > Running: git status --porcelain
2021-01-27 06:12:03,407 autosynth [DEBUG] > Running: git commit -m chore: update Go generator, rules_go, and protobuf

PiperOrigin-RevId: 352816749

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Wed Jan 20 10:06:23 2021 -0800
Source-Repo: googleapis/googleapis
Source-Sha: ceaaf31b3d13badab7cf9d3b570f5639db5593d9
Source-Link: https://github.com/googleapis/googleapis/commit/ceaaf31b3d13badab7cf9d3b570f5639db5593d9
[autosynth-redis-277 a71904c4] chore: update Go generator, rules_go, and protobuf
 3 files changed, 4 insertions(+), 4 deletions(-)
 rewrite Redis/metadata/V1/CloudRedis.php (92%)
 rewrite Redis/metadata/V1Beta1/CloudRedis.php (92%)
2021-01-27 06:12:03,434 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at a71904c4 chore: update Go generator, rules_go, and protobuf
2021-01-27 06:12:03,477 autosynth [DEBUG] > Running: git checkout autosynth-redis
Switched to branch 'autosynth-redis'
2021-01-27 06:12:03,504 autosynth [DEBUG] > Running: git diff HEAD..autosynth-redis-277 -- . :(exclude)synth.metadata
2021-01-27 06:12:03,509 autosynth [DEBUG] > Running: git diff HEAD autosynth-redis-277
2021-01-27 06:12:03,513 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmp_prjj7zg/autosynth-redis-277.patch
error: cannot apply binary patch to 'Redis/metadata/V1/CloudRedis.php' without full index line
error: Redis/metadata/V1/CloudRedis.php: patch does not apply
error: cannot apply binary patch to 'Redis/metadata/V1Beta1/CloudRedis.php' without full index line
error: Redis/metadata/V1Beta1/CloudRedis.php: patch does not apply
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 104, in synthesize_loop
    return synthesize_loop_single_pr(toolbox, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 126, in synthesize_loop_single_pr
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 152, in synthesize_inner_loop
    synthesize_range(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 170, in synthesize_range
    toolbox.patch_merge_version(young)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 182, in patch_merge_version
    git.patch_merge(sub_branch, patch_file_path)
  File "/tmpfs/src/github/synthtool/autosynth/git.py", line 151, in patch_merge
    executor.check_call(["git", "apply", patch_file_path], cwd=git_repo_dir)
  File "/tmpfs/src/github/synthtool/autosynth/executor.py", line 29, in check_call
    subprocess.check_call(command, **args)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'apply', '/tmpfs/tmp/tmp_prjj7zg/autosynth-redis-277.patch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating redis. :sob:
Here's the output from running synth.py:
rom protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/Instance.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/Instance.php.
2021-01-27 06:12:03,036 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/ExportInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1beta1/ExportInstanceRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/FailoverInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/FailoverInstanceRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/OperationMetadata.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/OperationMetadata.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpgradeInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpgradeInstanceRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesRequest.php.
2021-01-27 06:12:03,038 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ImportInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ImportInstanceRequest.php.
2021-01-27 06:12:03,039 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsDestination.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsDestination.php.
2021-01-27 06:12:03,039 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/CreateInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/CreateInstanceRequest.php.
2021-01-27 06:12:03,039 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsSource.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GcsSource.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GetInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GetInstanceRequest.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpdateInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpdateInstanceRequest.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/DeleteInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/DeleteInstanceRequest.php.
2021-01-27 06:12:03,040 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesResponse.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListInstancesResponse.php.
2021-01-27 06:12:03,041 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Instance.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Instance.php.
2021-01-27 06:12:03,041 synthtool [INFO] > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ExportInstanceRequest.php.
INFO:synthtool:Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ExportInstanceRequest.php.
2021-01-27 06:12:03,049 synthtool [WARNING] > No replacements made in src/**/V*/**/*.php for pattern final class, maybe replacement is no longer needed?
WARNING:synthtool:No replacements made in src/**/V*/**/*.php for pattern final class, maybe replacement is no longer needed?
2021-01-27 06:12:03,056 synthtool [WARNING] > No replacements made in src/**/V*/**/*.php for pattern public function ([s|g]\w{3,})Unwrapped, maybe replacement is no longer needed?
WARNING:synthtool:No replacements made in src/**/V*/**/*.php for pattern public function ([s|g]\w{3,})Unwrapped, maybe replacement is no longer needed?
2021-01-27 06:12:03,232 synthtool [WARNING] > No replacements made in src/**/V*/**/*.php for pattern (.{0,})\]\((/.{0,})\), maybe replacement is no longer needed?
WARNING:synthtool:No replacements made in src/**/V*/**/*.php for pattern (.{0,})\]\((/.{0,})\), maybe replacement is no longer needed?
2021-01-27 06:12:03,232 synthtool [DEBUG] > Wrote metadata to synth.metadata.
DEBUG:synthtool:Wrote metadata to synth.metadata.
2021-01-27 06:12:03,317 autosynth [INFO] > Changed files:
2021-01-27 06:12:03,318 autosynth [INFO] > M Redis/metadata/V1/CloudRedis.php
 M Redis/metadata/V1Beta1/CloudRedis.php
 M Redis/synth.metadata
2021-01-27 06:12:03,318 autosynth [DEBUG] > Running: git log ceaaf31b3d13badab7cf9d3b570f5639db5593d9 -1 --no-decorate --pretty=%s
2021-01-27 06:12:03,322 autosynth [DEBUG] > Running: git log ceaaf31b3d13badab7cf9d3b570f5639db5593d9 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2021-01-27 06:12:03,325 autosynth [DEBUG] > Running: git add -A
2021-01-27 06:12:03,365 autosynth [DEBUG] > Running: git status --porcelain
2021-01-27 06:12:03,407 autosynth [DEBUG] > Running: git commit -m chore: update Go generator, rules_go, and protobuf

PiperOrigin-RevId: 352816749

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Wed Jan 20 10:06:23 2021 -0800
Source-Repo: googleapis/googleapis
Source-Sha: ceaaf31b3d13badab7cf9d3b570f5639db5593d9
Source-Link: https://github.com/googleapis/googleapis/commit/ceaaf31b3d13badab7cf9d3b570f5639db5593d9
[autosynth-redis-277 a71904c4] chore: update Go generator, rules_go, and protobuf
 3 files changed, 4 insertions(+), 4 deletions(-)
 rewrite Redis/metadata/V1/CloudRedis.php (92%)
 rewrite Redis/metadata/V1Beta1/CloudRedis.php (92%)
2021-01-27 06:12:03,434 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at a71904c4 chore: update Go generator, rules_go, and protobuf
2021-01-27 06:12:03,477 autosynth [DEBUG] > Running: git checkout autosynth-redis
Switched to branch 'autosynth-redis'
2021-01-27 06:12:03,504 autosynth [DEBUG] > Running: git diff HEAD..autosynth-redis-277 -- . :(exclude)synth.metadata
2021-01-27 06:12:03,509 autosynth [DEBUG] > Running: git diff HEAD autosynth-redis-277
2021-01-27 06:12:03,513 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmp_prjj7zg/autosynth-redis-277.patch
error: cannot apply binary patch to 'Redis/metadata/V1/CloudRedis.php' without full index line
error: Redis/metadata/V1/CloudRedis.php: patch does not apply
error: cannot apply binary patch to 'Redis/metadata/V1Beta1/CloudRedis.php' without full index line
error: Redis/metadata/V1Beta1/CloudRedis.php: patch does not apply
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 104, in synthesize_loop
    return synthesize_loop_single_pr(toolbox, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 126, in synthesize_loop_single_pr
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 152, in synthesize_inner_loop
    synthesize_range(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 170, in synthesize_range
    toolbox.patch_merge_version(young)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 182, in patch_merge_version
    git.patch_merge(sub_branch, patch_file_path)
  File "/tmpfs/src/github/synthtool/autosynth/git.py", line 151, in patch_merge
    executor.check_call(["git", "apply", patch_file_path], cwd=git_repo_dir)
  File "/tmpfs/src/github/synthtool/autosynth/executor.py", line 29, in check_call
    subprocess.check_call(command, **args)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'apply', '/tmpfs/tmp/tmp_prjj7zg/autosynth-redis-277.patch']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:

Autosynth passed, closing! :green_heart:


Do not store withdrawal_credentials

The Validator object does not need to store withdrawal_credentials. Instead, we can have a stateless approach where withdrawal operations include a Merkle proof to a historical deposit via historical_roots. To make this safe we can check that deposit.data.withdrawal_credentials == ZERO_HASH for deposits to existing validators.
The general heuristic is that consensus storage is much more expensive than consensus bandwidth. This is especially true for withdrawal_credentials which is read exactly once. In the worst case we can save over 100MB from the beacon state.

Closing this issue because withdrawal_credentialsdoes not need to be stored in RAM by validators (it can be stored on disk). It may also be possible to implement statelessness with without consensus support.
@ralexstokes: You gave a thumbs up. Feel free to reopen the issue :)


Bug with long event names in spall.h

Hi again, got a minor fix here.
The second memcpy within spall_build_begin() needs to use trunc_name_len instead of name_len
https://github.com/colrdavidson/spall-web/blob/17783521e15f1a063bf16a4742bef061553d2de3/spall.h#LL276C35-L276C35

Oops! good catch, fixed.


test(button-group): [button-group] Supplement button-group component test case

PR
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] Other... Please describe: supplement test case

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Supplement button-group component test case
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@all-contributors please add @trueLoving for test


feat: Add merge-method option

As per #103, this adds the option to set which merge method to use (e.g. squash or rebase).
fixes #103

Hi @nathanleiby, AFAIK, custom validation applies for the whole command (merge in our case), not just the flag. Trying to use something standardized, I went over to pflag to see what it had to offer, and find this: https://github.com/spf13/pflag/issues/236
I see four options.

Use/create a fork of pflag while spf13/pflag#236 is waiting.
Write custom validation for the whole command, like described above
Write something in cmd/merge.go
Let either Github or GitLab command validate it.

@cobraz thanks for digging into this.
Elsewhere in the repo we've followed an approach I think is (2) or (3) in your list. Here's an example of validating that the string passed to --throttle can be parsed as a Golang duration. Suggest that we follow the same approach here.

@cobraz I realized I didn't link the suggested code with validation logic. I'm sorry about that! The code I meant to link is here:
https://github.com/Clever/microplane/blob/bc56dbb2d465340f766debc6781978d0e2e1098b/cmd/merge.go#L36-L47
Hope this isn't stepping on your toes too much, but I went ahead and implemented the same sort of check for --merge-method, so we can go ahead and merge your change. Thank you again for the the PR!

Released here: https://github.com/Clever/microplane/releases/tag/v0.0.33


Network Topology Dashboard Update

This PR updates the Network Topology dashboard to include visualizations for
multiple networking layers. It also updates the legends of both graphs to
improve readability.

Currently, the legend is shown as a paragraph, but I can make it more visual as well.

For reviewers, a lot of files needed to be added as a result of the yarn tool being updated from toolkit to the grafana command itself. This update comes with a lot more surrounding configuration, and is needed for anyone wanting to build the plugin locally. The contents of the .config/ folder can be ignored, as they were automatically generated by the command yarn create @grafana/plugin migrate. The additional configuration I needed to get it working was the file webpack.config.ts file. To sum up, the code outside of the plugin directory, and both DiagramController.tsx and DependencyPanel.tsx are the main files within the PR that need to be reviewed.

Why do we have duplicated connections in layer 4/7 Topology? Or are they two different connections?
For Layer 4 Topology, is svc_antrea-test-3 the endpoint of web-server-3?

Why do we have duplicated connections in layer 4/7 Topology? Or are they two different connections?
They are two different connections
For Layer 4 Topology, is svc_antrea-test-3 the endpoint of web-server-3?
Yes, the goal of the layer 4 topology is to show destination Pod and Service, I'll update the legend to reflect that.

Please correct me if I'm wrong. I remember last time we decided to use the chord diagrams to show the flows and use a table to display all the L7 fields. Did I miss anything?

Please correct me if I'm wrong. I remember last time we decided to use the chord diagrams to show the flows and use a table to display all the L7 fields. Did I miss anything?

Not wrong at all, I'm splitting them up into two PRs, with the latter having the second dashboard with the chord diagram and httpvals table. Since httpvals contains nested JSON, some massaging to the data is required.

Do we need a .config folder? I don't see this folder under other plugins?

Yes, as I mentioned in my comment earlier, the .config folder is created as a result of upgrading the tool used to create, build, and sign plugins. Older plugins don't have this since they haven't been rebuilt or upgraded to have it, but it is a necessary folder for anyone wishing to build the plugin locally or make changes to its source code. The additional config file I added was weback.config.ts within the base grafana-dependency-plugin directory, which was provided by a Grafana dev.

Do you think we can add these changes to the e2e test or UT?

The network topology dashboard already has a unit test, which I included when I originally made the dashboard. It simply checks the query to see if it returns expected values.

Can you update network-flow-visibility.md to reflect these changes?

Yes, will do.

Will further update README and changelog to reflect latest changes.

Unit tests are proving to be challenging to setup with updated toolkit versions, will make patch PR for them separately.

Another general comment: if the PR is not ready for review, feel free to convert it to draft. If it is ready, maybe it's better to squash some intermediate and unmeaningful(to reviewers) commits in my opinion.

Instructions for those wanting to deploy the solution for themselves:

pull Antrea PR #5218
pull Theia PR #417 and this PR
execute the included script for build_antrea.sh.zip
deploy flow-visibility.yml from the new theia PR
apply the following: pods.yaml.zip
annotate the pods with the following command: kubectl pod annotate <pod-name> -n <namespace> [visibility.antrea.io/enable-l7=both](http://visibility.antrea.io/enable-l7=both)
kubectl exec into the applied admin pod and run the command curl example.com to get one row, or curl example.com example.com example.com to get multiple rows (it'll take about 2 minutes to populate clickhouse)
open the application layer dashboard to view http values


how convert tranformer network model from tensorflow to pytorch ?

Platform (like ubuntu 16.04/win10):
Python version: python2.7
Source framework with version (like Tensorflow 1.8 with GPU):
Destination framework with version (pytorch with GPU):
Pre-trained model path (transformer network model):
I want convert transformer, which is for NLP and not in MMdnn.extract_model.   How to add new network model supporting in MMdnn.

Hi @owenustc  we are working on NLP models conversion and will ping you if there is any progress. Thanks!


Project references files that are ignored by the VCS

The files in question are the ProximaNova fonts, which I assume cannot be included in this repository for licensing reasons.
And it's such a great font! Unfortunately, this also means that Xcode builds will fail unless

the font is purchased by each contributor (USD$290 was the cheapest I found); or
the font is replaced by either something from the system, or an open-source font like Open Sans.

Option 1 may not be financially viable for some members of the community, and option 2 may not be obvious to a lot of newcomers to the platform, as it's not mentioned in the setup section of the contribution guidelines, but it may become a headache to keep reverting these back to ProximaNova for submission to the App Store.
I'll submit a PR for changes to CONTRIBUTING.md in the meanwhile.

Since this was merged, can we close this?

While the PR addresses some missing setup steps in the contribution guidelines, I think a second item that the community may want to address is whether or not it makes sense to drop the use of a licensed font in the project.
It don't know if there are practical considerations for using ProximaNova, including support for non-Latin characters. It would, however, make it easier a little to merge back PRs that aren't using a bunch of different fonts, as I mentioned above.
If so, I'm happy to submit a second PR to move the project over to either a system or open-source font.

From my cursory understanding, we aren't wed to using custom fonts. @thm could speak more on this. It should be very easy to drop them if we don't think they'd add much to the application. As an aside, they're not a huge impedance either for people that want to make contributions.

We're using Proxima Nova here since that is the primary typeface we use at DuckDuckGo. As a designer I would always prefer to enforce a consistent design-language throughout a product. In that sense I think it adds a lot to the application, because it makes it ours.
I see that removing the typeface in favor of a default font would make things easier for engineers, but deviating from our design-language would negatively impact our branding, and with that, the people who use the app. I don't necessarily believe that a smoother contribution-process warrants this regression unless the contribution in question adds significant value to the app.
Aren't there alternatives to smoothen the process? can't we somehow fall back to a system typeface when Proxima Nova is not detected?

That makes a lot of sense to me—I agree that visual consistency across all platforms is really important. I'll look into the system-font-as-fallback option this weekend and send a PR with a better fix. :+1:

Progress:
I have a custom run script phase that will check the $CONFIGURATION and if it's Debug, it basically does nothing. Otherwise, for Release-* configurations, it should copy the Proxima Nova font files over.
We can then remove the font files from the Copy Bundle Resources phase, and everything ends up rendered in the system font for Debug builds.
However, I'm not entirely sure about the source and destination folders and my script-fu is not strong. :unamused:
Can someone confirm that the files exist in $(SCROOT)/Resources/proximanova-*.otf?
The build script is as follows:
if [ "${CONFIGURATION}" == Debug ] ; then
    echo "Debug configuration."
    # Basically do nothing here and it'll fall back to the system font.
else
    echo "Release configuration."
    cp -r "${SCRIPT_INPUT_FILE_0}" ${BUILD_PRODUCTS_DIR}/${PRODUCT_NAME}.app
    cp -r "${SCRIPT_INPUT_FILE_1}" ${BUILD_PRODUCTS_DIR}/${PRODUCT_NAME}.app
    cp -r "${SCRIPT_INPUT_FILE_2}" ${BUILD_PRODUCTS_DIR}/${PRODUCT_NAME}.app
    cp -r "${SCRIPT_INPUT_FILE_3}" ${BUILD_PRODUCTS_DIR}/${PRODUCT_NAME}.app
fi


Add the Notes about Provisioning OneDrive

Add the Notes about Provisioning OneDrive

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

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

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

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 4604737:
:clock10: Full build: the average full build time is 14 min(s) 15 sec(s), this is based on the last 87 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

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

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 9008b58:
:clock10: Full build: the average full build time is 14 min(s) 15 sec(s), this is based on the last 89 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 9008b58:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Consistent layer naming - addresses #1462

The commit also changes some IPython notebooks.
Layers that were named "y" are now named "softmax" to generate same output as before.

I'm not sure about the changes to the .ipynb files, since renaming the layer from 'y' to 'softmax' will change all channels that were named 'test_y_...', for instance 'test_y_misclass'. There seem to be more of them than 'softmax_...' channels, so I would do the changes the other way around.

Right. So - by assigning the issue to yourself - you mean that you're going to fix it or you want me to create a new pull request?

Sorry for the misunderstanding, since GitHub only lets us assign people with commit rights to the repository, we have started assigning to PRs the person who will be responsible for reviewing/merging them. It also makes it easier for me to have an overview of the PRs and tickets I should review.
If you could update this PR (I don't think you need to create a new one, if there is a conflict you can always git rebase and git push -f to the same branch), that would be great. Thanks!


70 enhancement risk controlled prediction sets for image segmentation

Description
Add 2 multilabel methods
Fixes #70
Type of change
Please remove options that are irrelevant.

New feature (non-breaking change which adds functionality)
This change requires a documentation update

Checklist

[x] I have read the contributing guidelines
[x] I have updated the HISTORY.rst and AUTHORS.rst files
[x] Linting passes successfully : make lint
[x] Typing passes successfully : make type-check
[x] Unit tests pass successfully : make tests
[x] Coverage is 100% : make coverage
[x] Documentation builds successfully : make doc

Codecov Report
Base: 100.00% // Head: 99.68% // Decreases project coverage by -0.31% :warning:

Coverage data is based on head (026cedb) compared to base (1b0d416).
Patch coverage: 98.96% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##            master     #232      +/-   ##
===========================================
- Coverage   100.00%   99.68%   -0.32%
===========================================
  Files           24       26       +2
  Lines         2450     2835     +385
  Branches       267      216      -51
===========================================
+ Hits          2450     2826     +376
- Misses           0        7       +7
- Partials         0        2       +2

Impacted Files
Coverage Δ

mapie/time_series_regression.py
100.00% <ø> (ø)

mapie/tests/test_multi_label_classification.py
98.31% <98.31%> (ø)

mapie/multi_label_classification.py
100.00% <100.00%> (ø)

mapie/_compatibility.py
72.22% <0.00%> (-27.78%)
:arrow_down:

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

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


🦟[Bug Report] Crash: specialized SendViewController.init(store:sender:walletManager:initialAddress:initialRequest:)

Problem
SendViewController is throwing this exception at runtime
Crashlytics Stacktrace
https://console.firebase.google.com/project/litewallet-beta/crashlytics/app/ios:com.litecoin.loafwallet/issues/2b38b89124d9dc29aac5336a16fd5e9e?time=last-seven-days&types=crash&sessionEventKey=9b038fe4054d41c8b0e8d55217eada0d_2014285926999946353
App (Poor) Performance
Please refer to XCode Organizer for details

Resolved in https://github.com/litecoin-foundation/litewallet-engineering/issues/14


machine-controller deployment failed due to invalid openstack auth url parsing

Do you have any idea why the MachineDeployment fails? Where can I configure the OpenStack auth URL so that it can get parsed and eventually create the machine deployment?
What happened:
INFO[09:55:37 CEST] Downloading kubeconfig...
INFO[09:55:38 CEST] Restarting unhealthy API servers if needed...
INFO[09:55:38 CEST] Ensure node local DNS cache...
INFO[09:55:39 CEST] Activating additional features...
INFO[09:55:41 CEST] Applying canal CNI plugin...
INFO[09:56:10 CEST] Creating credentials secret...
INFO[09:56:10 CEST] Installing machine-controller...
INFO[09:56:13 CEST] Installing machine-controller webhooks...
INFO[09:56:14 CEST] Waiting for machine-controller to come up...
WARN[09:56:55 CEST] Task failed, error was: machine-controller-webhook did not come up: failed to list pods: etcdserver: request timed out
WARN[09:57:00 CEST] Retrying task...
INFO[09:57:00 CEST] Waiting for machine-controller to come up...
WARN[09:57:07 CEST] Task failed, error was: machine-controller-webhook did not come up: failed to list pods: etcdserver: leader changed
WARN[09:57:17 CEST] Retrying task...
INFO[09:57:17 CEST] Waiting for machine-controller to come up...
WARN[09:57:32 CEST] Task failed, error was: machine-controller-webhook did not come up: failed to list pods: etcdserver: leader changed
WARN[09:57:52 CEST] Retrying task...
INFO[09:57:52 CEST] Waiting for machine-controller to come up...
INFO[09:59:07 CEST] Creating worker machines...
WARN[09:59:08 CEST] Task failed, error was: failed to deploy Machines: failed to ensure MachineDeployment: failed to create *v1alpha1.MachineDeployment: admission webhook "machine-controller.kubermatic.io-machinedeployments" denied the request: failed to default machineSpec: failed to get a openstack client, due to parse "\"https://openstack.tld.de:13000/v3\"": first path segment in URL cannot contain colon

What is the expected behavior:
v1alpha1.MachineDeployment can be deployed
How to reproduce the issue:
Anything else we need to know?
Information about the environment:
KubeOne version (kubeone version):  1.2.1
Operating system: Ubuntu 21.04
Provider you're deploying cluster on: Openstack
Operating system you're deploying on: CentOS_8.2

@FalcoSuessgott please don't use excessive escaping in the $OS_AUTH_URL.
https://play.golang.org/p/daB-iff3_yW

lmao good catch! You just saved me a few hours :)


"Submit Optimization Jobs" in Optimization -> How-to-Guides talks about quantum computing instead of optimization

This section is supposed to talk about optimization jobs, but instead it talks about quantum computing jobs.
https://docs.microsoft.com/en-us/azure/quantum/how-to-submit-jobs?tabs=tabid-python

@ashwinmayya Thank you for your feedback! We are aware of that, we are currently working on two separates "How to submit jobs" articles for quantum computing and optimization.

Work item in DevOps: #1865777


Tag system

According to discussion in #1353 , I propose my personal project tag system. At project's creation time, the user can generate new tags or choose existing ones for the project. This tags works as "filters" in the open project page.

I implemented the feature quite long time ago when the metadata structure introduced in OpenRefine 2.8 did not exist yet. That's why tags are treated as metadata in the code. I am not expert but if it is logically correct and/or it is better for future developments, we can keep tags separated from metadata. For the visualization part of the discussion: you focused pros and cons, I cannot say which solution is better.

"By showing them, it provides a good access point to edit the tag, but at the same time it take too much space. "
@jackyq2015 Looks like the system is able to handle a relative large number of tags without adversely affecting the display.

@xseris I see. I will test further. I am worry that the editing the metadata and the user metadata might not work properly because the tag takes a column but the current UI does not aware of this. Besides that, you may try to polish the codacy issues as you can(some are irrelevant which you can ignore). Also some basic Unit Test will help also.
I think we can merge it if other developers has no issue.
@ettorerizza It looks good. I really like the navigation bar at the top!

We usually use those tags to (improperly) separate projects coming from
different customers..this because IMHO Refine lacks the cocept of workspace
(i.e. a group of projects).
I think that addition would be VERY useful
On 25 Nov 2017 11:09, "Antonin Delpeuch"<EMAIL_ADDRESS>wrote:

@wetneb commented on this pull request.
Very nice feature! I agree with @ettorerizza
https://github.com/ettorerizza that this should replace the "subject"
field in the project metadata. But we need to think about the migration of
the contents of the "subject" field into the tags: ideally, users who
decide to fill the "subject" fill with OR 2.8 should still have access to
this data in the next release.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenRefine/OpenRefine/pull/1357#pullrequestreview-78999656,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADmeJUetrD_b37_HrOxLFdD1sa_frgFyks5s5-c9gaJpZM4QqI2P
.

I wonder if it would not be a good idea to make the dark blue tags clickable.

@wetneb I disagree with @ettorerizza and purely because of semantics. :)  I'd rather NOT replace the "subject" field.  Here's why:
In Schema.org, DCMI, and even Wikidata itself these are different properties.
Tags can be of the form "lamborghini time trials" or even #michaeljacksonconcerts.
Which is different than the subjects of Automobile Racing and Pop Star.
http://schema.org/keywords
http://pending.schema.org/about
Let's keep these concepts separate, even scientists treat them separate at times.

Agree. I think subject is formal and tag system is more free style. Maybe it can replace the "user defined metadata" instead?

You may be right @thadguidry . I do not have a strong opinion on the question. In Dublin Core, the "Subject" element can be expressed as "keywords, key phrases or classification codes that describe a topic of the resource". In this case, using tags instead of a single subject has the advantage of the polyhierarchy. But I know little Schema.org.

The problem I have with the "subject" field is that it is just free text: that's not very useful to organize your project library. The notion of subject is ill-defined, no importers fill that field because no serious file format will bother providing a field for that… And most users will just not bother filling up that field either, so we'll have a sad empty column taking a lot of space. So yeah, this field is just useless for me, that's why I'd be happy to see it replaced by the tags.
@jackyq2015 I don't understand why you say that "subject is formal and tag system is more free style"… In fact I was about to write the exact opposite!

""subject is formal and tag system is more free style"… In fact I was about to write the exact opposite!"
@wetneb I agree for this particular case. I really like the possibility of adding tags when creating the project. It can become more than just folksonomy. As long as these tags are stored in a separate Json file, this would give users the ability to create and use their own controlled vocabulary.

@wetneb quoted from @ettorerizza :
In Dublin Core, the "Subject" element can be expressed as "keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme".
But the tags is user defined which means you can choose what ever you like and they just have meaning for that user. It is NOT a mandate that they have to chosen from a controller vocabulary. In other words, the tag system could be local and does not have to to published.
Currently since OR's metadata is not standardised, you can argue that subject means something else.  But that's not the point.

@wetneb Careful.  Just because "subject" is not useful to you, doesn't mean that @ostephens and others in OpenRefine's bibliographic world will not appreciate it.  :)
There's no harm in keeping "subject" and it provides value by NOT squashing 2 different concepts, A Tag, and A Subject into one thing.  It is best to keep these 2 concepts separate, especially in regards to any metadata discussion in OpenRefine.  This also helps when having to integrate data with Knowledge Based System (KBS) tools outside of OpenRefine used in libraries and research centers.  Our JDBC export feature will need an option to publish the metadata as well eventually, but can work on that later.  Many Database Schemas have 2 columns for this, one for Subject Matter and one for Tags.
(specifically, for instance in MODS metadata http://www.loc.gov/standards/mods/mods.xsd the
<xs:element ref="subject"/>
versus the
<xs:element ref="relatedItem"/>)

@jackyq2015 if the "Subject" field in OR is meant to be "dc:subject", I think this should be made clear in the UI… The screenshots I have seen did not use it in this way ;-) . But anyway, you can also decide to use a controlled vocabulary for the tags (and you should!). Both of them can be used with a controlled or uncontrolled vocabulary, but the tagging system seems a lot easier to use for that purpose. If you like "dc:subject", then we can decide that each tag is meant to be a value for this property! :)
@thadguidry yeah if people prefer free text over structured lists, fine! I don't actually care about that, I'm just saying that this looks pretty useless to me (and a waste of space) in the current form. But it's clearly not a hill I want to die on…

Just chipping in on the subject vs tag question. I think the key thing to differentiate is 'metadata to help navigate OR projects on your local install' vs 'metadata that may be imported/exported with the project'. I'm in favour of the tag system for local project management, but it may not be the right information to (e.g.) export as 'keywords' if we support metadata export for things like data packages in the future.
I don't have very strong feelings about it, but my instinct is with @thadguidry that 'subject' should be kept for more general purposes and tags should go into a field of their own (which could be 'local-subject' rather than 'tags'?). But it's only an instinct - no strong reasoning to back this up

@jackyq2015 I solved the null pointer exception in tests, but now I get another error: "org.mockito.exceptions.verification.NoInteractionsWanted" that i don't know how to fix it. Can you help me?

"this looks pretty useless to me (and a waste of space) in the current form. "
@wetneb @jackyq2015 Same problem, and even worse, with the metadata "creator". I did not bothered once to fill it. In 99.9% of cases, I am the creator. Should not it be automatically filled in with the username of the session, leaving that field editable?

@xseris Those verifyNoMoreInteractions(project) issue means that your code introduced new invocation against the project other than ALL the verify statements before it. you can find out which invocation you missed from the testng log and add tha to do a verify. It is not that straightforward. But once you does one, rest of them most likely are the same.
@ettorerizza The problem is that OR don't know who you are thus can not fill that for you. we can put a setting as a workaround though

@xseris Great work! I will checkout locally and do some UI testing. If there is no issue found, I will approve this PR. We can have more discussion regarding which field can be replaced with the "tag system" before or even after the merge. It is not I don't like the change. It just take a while to have everyone at the same page. Agree?

@jackyq2015 yeap, I agree

Thank you so much for this work! Here are my thoughts after the changes:

Why are the tags aligned to the right? In a left-to-right language I would expect to see them aligned to the left.
There is no consensus to replace the subject field by the tags. What if we kept the subject field, but without displaying it in the table? (It would only be accessible via the about link. I would do the same for the author and description fields actually) Or, if there is still no consensus for that: changing the position of the tags column so that it is just after the "Name" column.
Tags should be clickable (that was pointed out by others)
The tag input is not as easy to use as it could be - could we use a jQuery plugin for that? Here is a list: http://jquery-plugins.net/tag/tag-input (but that's just a nice plus to have - I'd be happy to merge without that)

@xseris I found some issue with the position of the "tag". we support the "user defined metadata" and I just write down the procedure to do so:
https://github.com/OpenRefine/OpenRefine/wiki/Metadata
Currently the "tag" column always take the last column and it will mess up the "user defined metadata" if there is any ( the tag will take the space of the last user metadata). But if you can move the tag right after the "name" column and that will solve the problem automatically without doing anything else. We can  hide "subject" and "creator" later on if everyone agree. but that can happen after the merge.
So from my side, I only expect that tag column get moved after "name" column(which @wetneb  already pointed out)

@xseris Do you mind I merge your change into my repo from where I am doing some other meta-data feature? All the history can be kept.
I need to add a "Data Package" link besides the "About". I would like to merge your change to avoid more complex  3-way merge in future. Let me know if you are ok with that?  I will move the tag column right after the name column as we discussed.

@jackyq2015 I tried locally but just moving tag column right after the name one does not solve the issue that you raised. This because the setAnyField method seems not to be able to interpret the tag string into an array (tags are actually stored as string array).
I already solved it (and also moved the column right to name) with a workaround. Also the filter bar needed to be refreshed and the tags into the specific cell rebuild. I still have to solve a little GUI problem, but it will not take too much time (max 1 day).
Then you are free to merge all modifications into your repo.

@jackyq2015 You can merge into your repo now

@xseris I merged to my repo:
https://github.com/jackyq2015/OpenRefine/commits/feature/metadata
Looks great! I noticed that there is some sample tags like "big data test1 test2". where those comes from? I have not start to set the tag yet.

@jackyq2015 This is strange, I don't see those tags. There are not even tags injected in the code...

My bad. I think i tested it before.

@thadguidry your review is still marked as "requested changes" - do you still have any concerns?

@jackyq2015 feel free to merge when ready.  You can tackle remaining updates or bug fixes with another pull. Let's merge this as you say to avoid a 3 way merge.  Thanks team !

@xseris Seems when moving mouse point to the "tag" column, there is not menu displayed to add tags any more in the current code base. I tested on your repo and it's the same. could you please take a look and create another PR to fix this issue?


Add a resource type for Signal messenger

Oh cool, this is the first signal group we've seen.
I should probably add it as a resource type.

Originally posted by @bhousel in https://github.com/osmlab/osm-community-index/issues/735#issuecomment-2338901573

Oh wait I was wrong - we do support signal already, but we didn't use the FontAwesome icon.

Hah I was about to comment on original PR saying I found signal value in docs