Fix calling out to elastix command

Closes https://github.com/almarklein/pyelastix/issues/1

Thank you for the PR! This fix is now a part of #20 and it will be shipped with the new release.

Why hasn't this small but essential fix been merged into the main branch and released? Or alternatively @soupault's branch been released as the official version? If pyelastix is installed from pip or conda it is currently broken!

@bamford thanks for the heads-up. Maintaining an open source package can be a burden, and lack of time is always a problem. As for me, my interests have shifted to other areas, so I would be happy if others take over maintenance of this package.
As for now, #20 has now been merged. We can do a release, or is there anything else you'd like to do first @soupault ?

@almarklein I think it would be fine to make a release as-is. I don't have any big plans on changing the API, currently. Several major bugs have been fixed, so many people should benefit from that.

Ok, I'll push to Pypi

done!

Thank you for your very quick response! Sorry if my comment yesterday came across a bit blunt. I completely appreciate the problem: the more useful things you produce, the more you are expected to look after! Many thanks to both of you for putting together and maintaining this software.


Lift code freeze

Lift code freeze as outlined in https://groups.google.com/forum/#!topic/kubernetes-dev/n-vqlX-HHSM
CC @foxish

This change is

Lgtm

+1 LGTM 👍

Merging based on ok from @saad-ali

Verified with @caesarxuchao that his and @smarterclayton's large PRs are stable:

Yuju sent me a flake that's caused by https://github.com/kubernetes/kubernetes/pull/36673
https://github.com/kubernetes/kubernetes/issues/37560
otherwise so far so good
I don't think it's enough to keep freezing the queue
We can fix the flake

Restarting merge queue to pick up changes


EPIC [wins] Support upgrading wins version / config on Windows hosts

This issue is an Epic that tracks several other issues around supporting wins upgrades to the version or configuration across all hosts in a Windows cluster.
Tasks

[x] Support .\wins.exe up[grade] (https://github.com/rancher/wins/issues/23)
[x] Create build images for wins (https://github.com/rancher/wins/issues/24)
[x] Add Helm chart for wins upgrade (https://github.com/rancher/wins/issues/20)
[x] Expose Helm chart on Rancher Helm repository (https://github.com/rancher/rancher/issues/31504)

Note
Related to https://github.com/rancher/rancher/issues/28327, which requires wins upgrades across Windows hosts in the cluster to be able to be deployed

All tested in Monitoring+v2+Windows+Support document. Closing.


Ruby: Migrate Packman Metadata Generation

First part in stopping using packman.

Codecov Report

Merging #992 into master will increase coverage by <.01%.

@@             Coverage Diff              @@
##             master     #992      +/-   ##
============================================
+ Coverage     85.24%   85.24%   +<.01%
- Complexity     3367     3374       +7
============================================
  Files           341      343       +2
  Lines         13413    13443      +30
  Branches       1532     1533       +1
============================================
+ Hits          11434    11460      +26
- Misses         1544     1547       +3
- Partials        435      436       +1

Impacted Files
Coverage Δ
Complexity Δ

.../api/codegen/transformer/PackageMetadataNamer.java
20% <ø> (-5%)
1 <ø> (ø)

...ansformer/ruby/RubyPackageMetadataTransformer.java
100% <100%> (ø)
4 <4> (?)

...le/api/codegen/gapic/MainGapicProviderFactory.java
94.31% <100%> (+0.15%)
15 <ø> (ø)
:x:

...gen/transformer/ruby/RubyPackageMetadataNamer.java
66.66% <66.66%> (ø)
3 <3> (?)

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 2c296d3...ece6c10. Read the comment docs.

@jmuk Could you please help take a look at this? Thanks!

Added other generated files from packman.


The ListTeplate Large Element Type has not effect

The list rendered on FB is always the same no matter if I use ListTemplate.newBuilder(ListTemplate.TopElementStyle.LARGE) or ListTemplate.newBuilder(ListTemplate.TopElementStyle.COMPACT)
ListTemplate.newBuilder(ListTemplate.TopElementStyle.LARGE)                  .addElements()                     .addElement("title1")                     .subtitle("subTitle1")                     .imageUrl("http://example.com/1.png")                     .buttons(Button.newListBuilder().addUrlButton("t1", "http://example.com/1").toList().build())                 .toList()                     .addElement("title2")                     .subtitle("subTitle2")                     .imageUrl("http://example.com/2.png")                     .buttons(Button.newListBuilder().addUrlButton("t2", "http://example.com/2").toList().build())                 .toList()                 .done()                 .build();
I cannot figure out if this is a problem with the library or with FB though because the json this sends is:
{    "recipient":{       "id":"1928466753845863"    },    "message":{       "attachment":{          "type":"template",          "payload":{             "top_element_style":"large",             "elements":[                {                   "title":"title1",                   "subtitle":"subTitle1",                   "image_url":"http://example.com/1.png",                   "buttons":[                      {                         "url":"http://example.com/1",                         "title":"t1",                         "type":"web_url"                      }                   ]                },                {                   "title":"title2",                   "subtitle":"subTitle2",                   "image_url":"http://example.com/2.png",                   "buttons":[                      {                         "url":"http://example.com/2",                         "title":"t2",                         "type":"web_url"                      }                   ]                }             ],             "template_type":"list"          }       }    } }
which seems correct to me. It is like the ** "top_element_style":"large"** is treated like COMPACT.

Hi, thanks for reporting this issue.
I checked the FB documentation and it seems that the JSON is still right. There were no API changes. Also "large" is the default if there is no "top_element_style" specified.
According the docs "top_element_style is always rendered as compact style on web right now". So please make sure that you use the Messenger mobile App to verify the behavior.
If it still doesn't work please file a bug here: https://developers.facebook.com/bugs/

@menwn does this behavior still occur? Otherwise I would close this issue.

@maxgrabenhorst I did not have the opportunity to test again. I will try to do it over the weekend and let you know.

Close this issue now. Please reopen if still relevant.


Why yellow?

I'm just curious... how did the creator of this logo come up with yellow, and that shade of yellow?

I'm also curious. Someone asked me this week if I based the color of my book's cover (Eloquent JavaScript) on the logo, which I didn't, since the book predates this logo by a few months. But it is a very similar shade of yellow. So now I'm wondering, for vanity reasons, if the logo color was inspired by this cover? @voodootikigod Any input?


I Lost Z datasets

Development environment used

Z Open Editor version:
Editor Platform

[x] Visual Studio Code
[ ] Red Hat CodeReady Workspaces
[ ] Eclipse Che
[ ] Standalone Theia

Editor Platform Version:
Operating System (on which VS Code runs such as Windows 10 2004, otherwise name and version of platform such as OpenShift v4.3):
Java Version (when using VS Code or Theia, execute java -version and paste the details here):
[ ] Related to RSE API?

RSE API Plugin version:
Zowe CLI version:
Node.js version:

Logs attached (see here how to get them): yes/no

Problem Description
Detailed steps for reproducing the problem:

First step

Observed behavior

Expected behavior

@Mertens1 can you provide more details? Was this related to using Zowe Explorer? If yes, can you file an issue here? https://github.com/zowe/vscode-extension-for-zowe/issues

Yes it was when us using zowe, the issue I have is that the file path was
not found for Java_11 Home, my comuter shows java as an app rather than a
file, if I see it correct
Thanks
Tom Mertens
On Thu, Mar 2, 2023, 2:56 PM Peter Haumer @.***> wrote:

@Mertens1 https://github.com/Mertens1 can you provide more details? Was
this related to using Zowe Explorer? If yes, can you file an issue here?
https://github.com/zowe/vscode-extension-for-zowe/issues
—
Reply to this email directly, view it on GitHub
https://github.com/IBM/zopeneditor-about/issues/327#issuecomment-1452466771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2CU5WBGKJQGFD5IPRZTBCTW2D3ORANCNFSM6AAAAAAVNP3OR4
.
You are receiving this because you were mentioned.Message ID:
@.***>

For Zowe Explorer and accessing data sets you do not need Java. Perhaps try the Slack channel #zowe-explorer on openmainframeproject.slack.com.
I assume you also installed Z Open Editor, which is the COBOL, PL/I, REXX, HLASM editor that requires Java. If you want to get that working you need to find out where Java was installed, which is different if you are on Windows vs Mac, as well which Java distribution you are using. If you are not familiar with Java I would recommend to install it with an automated installer app that typically creates a JAVA_HOME environment variable for you that our editor will find and use.
The default for IBM's Semeru Java distribution is /Library/Java/JavaVirtualMachines/ibm-semeru-open-11.jdk/Contents/Home on Mac and C:\Program Files\Semeru\jdk-<IP_ADDRESS>-openj9\ on Windows. If you use Oracle then it would be in different folder, but similar to those.
This page has more details on configuring Java: https://ibm.github.io/zopeneditor-about/Docs/getting_started.html

Most courses you can unenroll, I do not see that I can in Fundamentals and
Concepts course, is there a way I can unenroll and restart, the problem
began last fall, vsc1 went good, no problems now after starting back in
fundamentals challenge or reoing vsc1 I can not get back into dat sets that
IBM put forth for students. Here is what I have  zowe cli is not being
read, I will uninstall and reinstall zowe cli everything else is ok,
Thanks
Have a great weekend
Ps winners never quit and quitters never win
Tom Mertens
From: Peter Haumer @.>
Sent: Thursday, March 2, 2023 4:27 PM
To: IBM/zopeneditor-about @.>
Cc: Mertens1 @.>; Mention @.**>
*Subject: *Re: [IBM/zopeneditor-about] I Lost Z datasets (Issue #327)
For Zowe Explorer and accessing data sets you do not need Java. Perhaps try
the Slack channel #zowe-explorer on openmainframeproject.slack.com.
I assume you also installed Z Open Editor, which is the COBOL, PL/I, REXX,
HLASM editor that requires Java. If you want to get that working you need
to find out where Java was installed, which is different if you are on
Windows vs Mac, as well which Java distribution you are using. If you are
not familiar with Java I would recommend to install it with an automated
installer app that typically creates a JAVA_HOME environment variable for
you that our editor will find and use.
The default for IBM's Semeru Java distribution is /Library/Java/
JavaVirtualMachines/ibm-semeru-open-11.jdk/Contents/Home on Mac and C:\Program
Files\Semeru\jdk-<IP_ADDRESS>-openj9\ on Windows. If you use Oracle then it
would be in different folder, but similar to those.
This page has more details on configuring Java: https://ibm.github.io/
zopeneditor-about/Docs/getting_started.html
—
Reply to this email directly, view it on GitHub
https://github.com/IBM/zopeneditor-about/issues/327#issuecomment-1452643670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2CU5WDTP2MHRA2AFV6FDEDW2ENGRANCNFSM6AAAAAAVNP3OR4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Mertens1, I understand. This site is for problems with IBM Z Open Editor, i.e. the editor for writing programs. For Zowe we have other sites as mentioned above. We try to help here if we can, but we do need much more details about your problem. Exact steps to reproduce the problem, error codes, log files etc.
There are also several courses out there that utilize our editor and Zowe, so I do not know which one you are referring to. It would definitely be best to contact the course providers for help. I am sure they list help forums or channels as well.

Thank, where do I contact course providers please? Tom Mertens From: Peter HaumerSent: Friday, March 3, 2023 5:39 PMTo: IBM/zopeneditor-aboutCc: Mertens1; MentionSubject: Re: [IBM/zopeneditor-about] I Lost Z datasets (Issue<EMAIL_ADDRESS>I understand. This site is for problems with IBM Z Open Editor, i.e. the editor for writing programs. For Zowe we have other sites as mentioned above. We try to help here if we can, but we do need much more details about your problem. Exact steps to reproduce the problem, error codes, log files etc.There are also several courses out there that utilize our editor and Zowe, so I do not know which one you are referring to. It would definitely be best to contact the course providers for help. I am sure they list help forums or channels as well.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
Assuming you are doing IBM's Z Xplore, I found this: https://ibmzxplore.influitive.com/forum/t/contact-support/115
They also have a forum: https://ibmzxplore.influitive.com/forum/

Closing for now.


can not found the ffmpeg in vcpkg.io website

[Describe the bug
https://vcpkg.io/en/packages.html
can not found the ffmpeg package.
and the display result is wrong.

@xiaoyifang Please open an issue to https://github.com/vcpkg/vcpkg.github.io/issues. Thanks.

https://github.com/vcpkg/vcpkg.github.io/issues/85


Version for VS 2022 Preview

.NET 6 Preview 7 requires VS2022 Preview 3 - can you publish a compatible version?
Thanks

Version that works on VS 2019 and  VS 2022 is available on the marketplace.


Error when introspecting Azure SQL Server database

I started a new Prisma project from scratch and followed the Microsoft SQL Server connector guide then I ran the introspect command and the following error was thrown.
Error
Error: [libs/sql-schema-describer/src/getters.rs:21:14] called `Result::unwrap()` on an `Err` value: "Getting data_type from Resultrow ResultRow { columns: [\"column_name\", \"data_type\", \"character_maximum_length\", \"column_default\", \"is_nullable\", \"is_identity\", \"table_name\", \"constraint_name\", \"numeric_precision\", \"numeric_scale\"], values: [Text(Some(\"location\")), Text(None), Integer(Some(-1)), Text(None), Boolean(Some(true)), Integer(Some(0)), Text(Some(\"carg_client_origins\")), Text(None), Integer(None), Integer(None)] } as String failed"

Versions

Name
Version

Platform
darwin

Node
v15.11.0

Prisma CLI
2.19.0

Binary
c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d

Can you share some information about your database schema? Then we could try to reproduce your problem.
We have end to end tests for running against Azure SQL Server at https://github.com/prisma/e2e-tests/tree/dev/databases/sqlserver-azure-sql, so we know that it fundamentally works.

This is the schema of the table that is throwing error when trying to introspect:
create table carg_client_origins
(
	id int identity
		primary key,
	address nvarchar(255),
	number int,
	complement nvarchar(255),
	zip_code nvarchar(255),
	province nvarchar(255),
	created_at datetime,
	updated_at datetime,
	location geography,
	city nvarchar(255)
)
go

Introspection will work for geometry in the next version. You'll get an unsupported type to your schema, but you can write your queries as raw if you need the data. Just remember to return data that maps to some of the existing prisma types.


abnormal myoblast migration

Add new term:
abnormal myoblast migration (a child of abnormal muscle precursor cell migration MP:0003090)
DEF: any anomaly in the orderly movement of a myoblast  from one site to another during development; a myoblast is a mononucleate cell type that, by fusion with other myoblasts, gives rise to the myotubes that eventually develop into striated muscle fibers
SYN: abnormal myoblast cell migration

Added new term:
abnormal myoblast migration MP:0030945


Is benchmark available with mc?

Hello, s3p looks very interesting. Has anyone compared performance with mc?
s3p supports parallel list and mc support parallel threads.

The real question is if MC supports parallel listing. There are several tools which support parallel copying, but I found that wasn't enough to get the performance I needed.


Support older ZD/Unleashed

Older ZD and UL don't use the XSS cookie, so change login to look for redirect to .html page and only add XSS header if XSS cookie is found.

Added CSRF Token fallback. Tested on ZD 10.1.2, ZD 10.5.1, Unleashed 200.7


add request money URI generator

Please add a method to generate receive money links, eg:
key.request_money_uri(amount_bch=0.001, label="Product one", msg="thank you")
format:
bitcoincash:[?amount=][&label=][&message=]
details: https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki
This URI could be used for 3rd party QR generator library.

These are so easy to generate that I've never once bothered.
I'm open to adding it, just not convinced it needs it.


Bad Error Message when Wire, Reg not used

Problem
val internal_wire = UInt()
internal_wire := io.in * 2
io.out := internal_wire

You will get a FIRRTL error saying that internal_wire is not defined. The error is far worse to manage when the name wasn't detectable. This issue is particularly relevant when porting from chisel2 to chisel3; however, it could easily come up when writing new RTL.
Proposal
My advised strategy is for the Wire, Reg, Literal, etc. constructions to also tag the datatype's nodes with information of what they are in the hardware graph (wires, regs, literals, etc.). Then, operations like connects or arithmetic, throw an error when involving operands not actually on the hardware graph.
You run into an issue with ports (as all current code does val io = // raw Data instantiation here). This is where my proposal to declare IOs as part of the Module constructor arguments comes into play. (The Module constructor can then tag the granted IO with the port information).

I would support a better (earlier) error message in this case but don't have time to implement it at the moment.  I'd happily review a PR.

What do you think about the Port/io (sub)issue I brought up?

Is the I/O thing not just a special case of declaring-hardware-inside-bundles?

I'm thinking of this:
class TestModule extends Module {
  val io = new Bundle {
    val in = Bool().asInput
    val out = Bool().asOutput
  }
  val internalwire = Wire(Bool())
  val internalreg = Reg(Bool())
  internalreg := internalwire // case1
  internalwire := UInt(1) // case 2
  io.out := io.in // case 3
}

Case 1 is fine. Both internalwire and internalreg were created after invocations of Wire and Reg were able to decorate the input Bool with information that they are wires and regs, respectively.
Case 2 is similarly fine because UInt(1) is a literal and thus actual 'hardware'.
Case 3 is problematic. We don't know that io.out and io.in are actual hardware since, at the time they execute, at best we know they are just Bundle. (Namely, Bundle of what).
The 'hack' would be to record this as a 'potential problem,' wait until the Module is fully constructed (Module.pop or whatever), go in decorate io with details it is a Port (at the same time, we check to make sure everything is nicely directioned, etc.). Then, review all the potential problems again to see if they are actual problems. First, this is hacky and, second, every potential problem would ideally capture a stack trace that can be thrown in the case it is a 'true problem.'
My proposal was to do instead:
class TestModule extends Module {
val io = Port(new Bundle {
val in = Bool().asInput
val out = Bool().asOutput
})
io.out := io.in
}
// or
class TestModule extends Module(new Bundle {
val in = Bool().asInput
val out = Bool().asOutput
}) {
io.out := io.in
}

I favor the latter because it lets Module be type parameterized on it's IO. So, instead of Module we have Module[IOT]. e.g. Queue[UInt] <: Module[QueueIO[UInt]]. This simplifies writing libraries that want to wrap modules and still expose their IO to the type system. One use case is that you can build a generic test harness 'for free' (without having to introduce your own shim class that is constraining the IO for you). e.g. "QueueTester(dut: () => Module[QueueIO[UInt]]) extends BasicTester"

The other use is (and the one I am really targeting) is being able to seamlessly replace a module with a mocked version of it. Rather than relying on chisel to figure out that two modules are identical (which requires fully elaborating each version), just explicitly elaborate only 1 copy. Then, all other use sites use the mocked version of it.

Bindings system fixed this... a long time ago...


Public symbol search

With no file open, try public symbol search shortcut - doesn't work
Open an sbt file, shortcut works but yields can't read prop. post of undefined since there's no client for the sbt file.

My error in #227

This error is still valid.
Problem is twofold:

shortcut is only for scala scope in editor, should probably be global
Need to define what instance to use when no active scala file. Should probably be the same as for the error panel so maybe need to state-ify "last used instance"

Dupe. More info in later #270.


Bug: tic tac toe game

Tic tac toe game crashes when draw is there. Fix it by adding an if statement or any other method.

@Shreyaar12 Once try Tic tac toe with AI :')

@raj03kumar
Sure, you can incorporate ai with tic tac toe and improve the game

assign me this

@raj03kumar
Sure, you can incorporate ai with tic tac toe and improve the game

Already it is incorporated to the website
Play game no.17 tic tac toe with AI

@sirajlekhak Assigned this issue to you. Kindly fix the crash when draw is there in game no. 1. Go through the guidelines and contributing.md for successful merge. Kindly complete it within a week. All the best to your work...

@raj03kumar I saw this issue is opened for 3 weeks. if not completed assign it to me


Allow Belongs to many relationship to sync id's with distinct pivot values

The behavior of the method syncWithPivotValues() is to sync  all entered id's with a particular set of value(s) to pivot column(s)
Example
$user->roles()->syncWithPivotValues([1,2,3],[ 'status' => 'active' ]);
//will produce this array after mapping
array(
  '1' => [ 'status' => 'active'],
  '2' => [ 'status' => 'active'],
  '3' => [ 'status' => 'active'],
)

But what I wanted was the ability to have different pivot column values for each role_id. More like so:
//notice the different values for each role_id
array(
  '1' => [ 'status' => 'active'],
  '2' => [ 'status' => 'inactive'],
  '3' => [ 'status' => 'pending'],
)

Now for the user's roles to all have a different status in one short at syncing; This can be possible with a new method syncWithAssocPivotValues()
$user->roles()->syncWithAssocPivotValues([1,2,3],[
           ['status' => 'active'],
           ['status' => 'inactive'],
           ['status' => 'pending'],
        ];

Why do you use 2-space tabs?

Please resubmit this with passing coding standards, thanks.


Fix new in 2.0 callout

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/26aa22896728001f01e4a461d1fc36daf6bd871e/


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit 928ebe4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Revert "run_qemu: switch mkosi to not build unified kernel images"

mkosi.generic.conf.tmpl: re-enable UnifiedKernelImages
This reverts commit 92ac46548ca7d933383ec8617311052bf6a3d12a
The build of the Unified Kernel Image was disabled 18 months ago but no one can remember now what problem this solved at the time. It should be possible to just ignore this byproduct.
For some unknown reason, reverting this fixes the build on Ubuntu 22.04 with mkosi version 12:
running: sudo -E mkosi -i -f --autologin build
Error: Sorry, --without-unified-kernel-images is not supported in
UEFI mode on this distro.

Reverting this also helps the (upcoming) compatibility with mkosi v15+ because this option has been entirely removed from mkosi v15+! Quoting any recent mkosi/NEWS.md:
    v15

    We also remove the WithoutUnifiedKernelImages= switch as building
    unified kernel images is trivial and fast these days.

Hopefully fixes the Ubuntu 22 build failure seen at
https://github.com/pmem/run_qemu/actions/runs/12130559207/job/33821135406?pr=64
+ sudo -E mkosi -i -f --autologin build
running: sudo -E mkosi -i -f --autologin build
‣ Error: Sorry, --without-unified-kernel-images is not supported in UEFI mode on this distro.

The build of the Unified Kernel Image was disabled 18 months ago but no one can remember now what problem this solved at the time.

Maybe it was some "ukify not found" error? I got this error on Ubuntu 24, fixed by installing systemd-ukify in (bigger) #69
Not a problem on Ubuntu 22 (and others) where systemd was monolithic.


Design high-level spec

@DylanBaker, writing down my thoughts in this issue which we can use for our initial design and division of work. Happy to break this up into separate issues as well if that's easier. Let me know what you think!
User interface
Right now I'm envisioning two CLI commands, one to run the content validator fonz content and one to run the queries to check for database errors fonz sql (naming quite obviously open to feedback).
API endpoints of interest
Start a new development mode session
Documentation: Session > Update Session
It's not entirely clear how to do this, I don't see the specification for the request in the documentation, but this seems to be the right endpoint to switch from prod to dev mode. This endpoint is also in beta so is subject to change.
Some other relevant information from the Workspace documentation here:

The dev workspace is local to each Looker user. Changes made to project/model files in the dev workspace only affect that user, and only when the dev workspace is selected as the active workspace for the API session. (See set_session_workspace()).

The dev workspace is NOT unique to an API session. Two applications accessing the Looker API using the same user account will see the same files in the dev workspace. To avoid collisions between API clients it’s best to have each client login with API3 credentials for a different user account.

Changes made to files in a dev workspace are persistent across API sessions. It’s a good idea to commit any changes you’ve made to the git repository, but not strictly required. Your modified files reside in a special user-specific directory on the Looker server and will still be there when you login in again later and use update_session(workspace_id: “dev”) to select the dev workspace for the new API session.

Check out branch
Documentation: Projects > Checkout New Git Branch
Parse LookML
Documentation: LookmlModel > Get LookML Model
The idea here is to download the names of all fields from each explore and store them by explore name for later querying.
Build a query
Documentation: Query > Create Query
Looker queries have to be created before they can be run. Here's where we pass all of the fields, model name, and view name to construct our query for a given explore.
Run a query
Documentation: Query > Run Query
Run content validation
Documentation: Content > Validate Content
This is an API 3.1 only endpoint (currently in beta status) and also requires the Content Validation Labs Feature to be enabled. Maybe we make this more of a stretch goal since the Looker features required here seem less stable.
There's an example of how to use this in Looker's Python API sample code repo.
Python class design
Stubbing out a rough draft of the core class and important methods.
from typing import Sequence, List, Dict, Any

JsonDict = Dict[str, Any]

class Fonz:
    def __init__(client_id: str, client_secret: str, branch: str):
        """Instantiate Fonz and save authentication details and branch."""
        self.client_id = client_id
        self.client_secret = client_secret
        self.branch = branch

    def connect(branch: str) -> None:
        """Authenticate, start a dev mode session, check out specified branch."""

    def get_dimensions(explore: str) -> List[str]:
        """Get dimensions for a specified explore from the LookmlModel endpoint."""

    def create_query(dimensions: Sequence) -> str:
        """Build a Looker query using all the specified dimensions."""

    def run_query(query_id) -> JsonDict:
        """Run a Looker query by ID and return the JSON result."""

    def validate_content() -> JsonDict:
        """Validate all content and return any JSON errors."""

Hey 👋. This is awesome. My notes, is no particular order:
Passing argument
On the CLI commands, those two definitely make sense. I think there are four things that would need to be passed in the run:

URL
Client ID
Client Secret
Development Branch

The first three are likely to always be the same, whereas the fourth is likely to change on each call. Do you have any preference thoughts on declaration? (I see the three options as in a config file, as an environment variable, and as a CLI argument.) I think any of those could work for the first three. For the development branch, I think a file is least useful as it would be the most difficult way to dynamically change.
Additional Connect command
I think it would be good to have a connect command, to give people the ability to test their credentials.
Getting into a dev environment.
I'm slightly confused by the Workspace and Session API docs.
From the docs:

There are two predefined workspaces available: “production” and “dev”.

There are endpoints to GET all the workspaces, but it doesn't really explain whether you can have any workspaces other than those two. There isn't one to create a workspace (and I'm not aware of a way of doing it in the UI.)
All that to say, yes, I think you're right about the Session endpoint being the correct one. I think we just need to hit it with dev and it should switch over.
3.0 vs 3.1
Have you worked with the 3.1 API yet? I haven't, though at the Hackathon last week they were strongly pushing us to use it.
It feels like using 3.1 is the thing we should do for future-proofing, but it means we can't use the pypi lookerapi package (which make not be a huge loss anyway).
Another alternative is that we let the user control which one to use (particularly as if they are self-hosted they could still be on an old one) but we would need to add extra logic for that.
Endpoints and Class structure
Otherwise, this all looks good to me. Makes complete sense.  Do you have an idea as to how you think we could break up the development?
Testing
One thing I have not done a huge amount of before is testing external APIs. I'd love to do testing really well on this. (It seems hypocritical to not do so). We will need to mock the APIs, which I haven't done but am keen to learn. Have you got any experience there?


PullTest

PullTest

Testing what happens when we close without merging pull request.

What is this terrible request?


improve performance by reworking the port scan

This results in decreasing the fast scan time
from 0.309s to 0.020s for localhost on my machine.
Expose the underlying errors in the public api,
to allow users to handle these themselves.

Hi @lu4p, thanks for the PR. Overall i lke these changes. I have some minor complaints but nothing worth bothering you over. I have a few planned expansions that would have filled in some structs but that can be re-added later.


app.asar is not built properly after code signing the mac app. without code sign app.asar is built properly and the desktop works fine.

Closing as duplicate of https://github.com/mattermost/desktop/issues/2181


Switch command checking to Map for speed improvements and better maintainability

The way I did it is even better.


Lock Versions + Rerun npm i

Locks package versions
Updates package-lock files (they were out of step)

I get locking down the packages in package.json, but why lockdown packages inside the package-lock?

That's the auto-output from npm, I think I missed it when finishing up the last prettier/eslint PR

I get locking down the packages in package.json, but why lockdown packages inside the package-lock?

That's the auto-output from npm, I think I missed it when finishing up the last prettier/eslint PR, if you have a moment could you pull this branch and verify you don't get a diff after running npm run update-all?

I just did this and there was no diff. 👍


Raster data sources' units field is ignored

I forgot to implement checking units for raster data sources, so the current output pretends everything is in metres even if the data source was in feet.

Note also that the Seattle LIDAR file configured in datasources.json is actually in metric, not feet as that JSON currently claims.  When fixing this bug, I will also correct that error.


proposal: slices, sort: randomize sort order of equal elements in tests

Proposal Details
Go's (non-stable) sort functions don't guarantee a particular ordering for equal elements. However, since the order of equal elements is always the same for a number of releases, tests tend to accumulate dependencies on the ordering of equal elements by accident.
In Google codebase we noticed that a large number of tests depended on the order of equal elements when the sorting algorithm was changed to pdqsort in April 2022 (http://go.dev/cl/371574). We needed to fix all of these to be able to release pdqsort internally. Recently http://go.dev/cl/624295 changed how equal elements are ordered. In the 2½ years since pdqsort was introduced a few tests have already started to depend on the order of equal elements again.
This is a classic example of Hyrum's Law

With a sufficient number of users of an API,
it does not matter what you promise in the contract:
all observable behaviors of your system
will be depended on by somebody.

Fixing tests when the order of equal elements changes is a lot of work and makes upgrading to a new Go version harder. It's also surprisingly hard to understand if the order of equal elements actually matters (i.e. if stable sort should have been used) or if the order of equal elements was depended upon accidentally. Both problems can be mitigated sufficiently by randomizing the order of equal elements on each test run. That way, tests that depend on the order of equal elements provide a very early signal of problem.
Google already did this for C++ some time ago and it's working very well:

https://libcxx.llvm.org/DesignDocs/UnspecifiedBehaviorRandomization.html
https://reviews.llvm.org/D96946
https://danlark.org/2022/04/20/changing-stdsort-at-googles-scale-and-beyond/

Related Issues and Documentation

proposal: sort: return equal values in non-deterministic order #13884 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

I assume that this would be implemented with the use of testing.Testing(), which means that it might also slow down benchmark performance, right? is this fine to do?

@mateusz834, I left out any implementation details, but I would be very surprised if this can't be implemented in a way that doesn't impact performance in production. If no such mechanism is available, the slowdown should be a trivially predictable branch.

What changed since the last proposal (#13884):

A stronger emphasis in the documentation did not help, we're still seeing tests depending on the order of equal elements
One of the reasons for pushing back was that it's sending the wrong message: "We will deliberately surprise you with our algorithms because of something that doesn't really matter to you." (@robpike). One argument that I didn't see in the discussion is that it's very hard to understand if someone intended the order of equal elements to be stable or not once the algorithm changes.
We now had multiple changes in the order of equal elements. I think it's fair to expect more in the future.

Sorry for the misunderstanding. You are correct of course. I am sure there are cases where it matters. The pervious proposal suggested an opt-out mechanism for tests that should also work for benchmarks.


DEV:TRAJ:Trajectory does not support deletion of station (low priority)

Per SLB "Issues found in Drillflow V0.14 image" email:
(low priority) Trajectory does not support deletion of station

Item noted not solved by SLB- active classified for next sprint
ETA TBD pending @TessForGithub2 current sprint support bandwidth


Accessibility and Usability Improvements

Many improvements to keyboard controls (switches, dropdown menus)
Dark mode for fonts cheat sheet
Fix: Skip to Content color improvements for light mode
Fix: Angular component search URL now ends with a /
Improved: Faster loading Angular components with fetchpriority="high"

does it not have deploy preview ?

does it not have deploy preview ?

unfortunately, not right now. I need to set it up separately to the main deployed site because we don't want changes going to production site until a new release ships... so modus-icons.trimble.com will always show the site as it was on last npm release and deploy previews would show state of the site from main branch.


Build Docker images for RISC-V

Because why not? This now makes even more sense as MIPS is adopting RISC-V now.

The support of RISC-V was removed because there are no stable releases of alpine for that architecture yet.


Uncaught TypeError: m.suggest is not a function

Getting Uncaught TypeError: m.suggest is not a function when starting to type.
<div mass-autocomplete>
   <input class="form-control"  ng-model="client"  mass-autocomplete-item="client_names">
</div>

Angular: v1.3.15

Whats the object client_names ?
If it's just a list of clients then it wont work. client_names should be an object with at least a suggest function.
Check out the examples here


Occasionally last_seen is updated seemingly randomly by using the portal

I've gone digging through all bits of code that can change this property and can't find any that could cause this outside of a door swipe. I also checked the last seen page on the new portal and I can't see any evidence of this bug so I'm closing this for now. To be clear: this definitely used to happen, but it seems like it got fixed at some point (probably accidentally).


oai review

reviewed oai_dc and mods_36 conversion in comparison to old conversion
added required field MetadataPrefix to delete record request, and did this for all inserted formats. See also change in oai-service that retroactively inserts records with this method

replaced by https://github.com/ugent-library/biblio-backoffice/pull/1358


Adjust Average Block Time Value for 9.2.0

The code has the same 10 minute target time that we've had from the start.  While this dual difficulty adjustment process runs better than any single routine we've tested to date, the average block time on testnet runs closer to 13 minutes (12-14 minutes typical).
I think we should reduce the target to 8 or 9 minutes and testnet the code - and adjust the target so that we get closer to a 10 minute average block time in the real world.

I think this is going to go away as we level off.

Zero called it.


[Request]: Move tasks + add task button

What kind of feature do you want?
Add the ability to remove non recurring done tasks to the history folder instead of leaving them in their place if its possible
+
if u can add a button to create tasks and specify where you want to be i.e  + button :
whats the name of the task?
recurring?
diff?
path?
Additional questions

[ ] I want to work on this feature request

Hello, @mrazarny. Thank you for your suggestion.
It's a pity but I'm not planning to implement a feature for moving tasks inside the vault at the moment.
However, if someone suggests a pull request for it, I'll be happy to consider it. As for your second request, yes, I'll definitely add a button for creating new tasks. This feature will be included in either version 1.3 or 1.4.

Ty buddy
btw your plugin literally is the exact same way as i wanted it to be its almost perfect for my use case so (Ty)
btw another idea 😅
i actually was scrolling in the plugin shop when i saw it and was just like how is this only 715 downloads
so i would recommend to either change the plugin name to make it more popular in search or the description
i.e
from : "task management with rewards system"
to: "Gamify your task/todo management with rewards system"

Hey @mrazarny, my plugin is quite new—I only uploaded it a month ago. So far, it hasn't been mentioned on popular platforms like YouTube etc. The only reference I've found is in this article about new Obsidian plugins New Obsidian Plugins, which briefly talks about it.
Thanks for a new description, I'm considering updating the description on your suggestion. However, I recall that updating descriptions in the Obsidian community plugins requires contacting moderation, which can take a long time 😅

Grind manager is good but the other one is better ya also i faced a problem basically i have some doing task and todo tasks but i can only filter either to do + doing so i think if u can add that to filters todo+doing ill appreciate it totally

for the name your suggestion is good i don't have ideas right now as i was foing math exams so im burn out right now so if u wanna to chat about features or anything massage me on reddit "MRAZARNY"

Grind manager is good but the other one is better ya also i faced a problem basically i have some doing task and todo tasks but i can only filter either to do + doing so i think if u can add that to filters todo+doing ill appreciate it totally

for the name your suggestion is good i don't have ideas right now as i was foing math exams so im burn out right now so if u wanna to chat about features or anything massage me on reddit "MRAZARNY"

btw i faced another thing that I wanna you to change (i m just trying to help)
every/day tag starts counting since yhe the last time i did the habit
for example if i have every day gem habit and ine day i went to the gem at 11pm and marked as done
the task wont appear till 11 pm next day which is frustrating just make it that it resets with day time reset like when 12pm hits all every day recurring resets

@mrazarny, maybe this is a bug, the real implementation of this feature must show tasks on new date and neglect specific time (I didn't do nothing with it in realization), maybe something went wrong with your locale time and plugin count your next day, does all tasks not resets after 12 pm?


Ignore certificate keys.

New

[x ] Template - New .gitignore template
[ ] Composition - Template made from smaller templates
[ ] Inheritance - Template similar to an existing template
[ ] Patch - Template extending functionality of existing template

I can't believe this was not added before. Thanks!


networkmode needs to be moved under hostconfig

resolves #369

Ha. We fixed this at the same time. Beat you to it =)

hahaha until next time! ;)


Stop making people turn around for a download link

File: toolbox/toolbox_install_windows.md
PLEASE, PLEASE, just simply and clearly put the link to download the toolbox on this page. We understood it's legacy and you are promoting Docker Desktop For Windows and may not support toolbox. But my system doesn't meet the requirements. Do you want me to upgrade it right now?
Stop making people turn around and wast time for a simple download link.
This is really ennoying.
Cheers

@guillaumerose @chris-crone @seemethere - FYI.

Hi @lovoni, thanks for your feedback on the download URL. Please note that Docker no longer maintains the download.docker.com URL for Docker Toolbox. You can download the latest version of Docker Toolbox from https://github.com/docker/toolbox/releases.
Docker Toolbox documentation has been updated to reflect this change. For more information, see:

https://github.com/docker/docker.github.io/pull/8969/
https://docs.docker.com/toolbox/overview/

Closing this issue.


Cannot export Keras model TypeError: ('Not JSON Serializable:', b'\n...')

Versions:
Mac OS 10.14.3
TF 2.0.0-dev20190319
import tensorflow as tf
from tensorflow.python import tf2
from tensorflow.keras.layers import Input
from tensorflow.keras.models import Model
print(tf.__version__)

import numpy as np
import pandas as pd
import os
# Goal: predict liquidlinePressure as a function of ambientTemp and current
df = pd.DataFrame([[250, 23.2, 8],
                    [255, 22.5, 7.5],
                    [256, 24.0, 8.5],
                    [258, 24.0, 9],
                    [260, 25.1, 8.5]], columns=['liquidLinePressure', 'ambientTemp', 'current'])
#-----standardizing constants
xmu = [26.0,6.0]
xsigma = [5.0, 3.0]
ymu = [255.0]
ysigma = [41.0]
#------------ prepare inputs and outputs
df = df.values
input_features=['ambientTemp','current']
output_features=['liquidLinePressure']
X=df[:,1:]
X = {input_features[i]:x.reshape(-1,1) for i, x in enumerate(X.T)}
y=(df[:,0:1]-ymu)/ysigma #standardize y's for training, but standardize x's within the model

#--------------using Kera's functional api for standardization of inputs
ambientTemp = Input(shape=(1,), dtype='float', name='ambientTemp')
ambientTemp_enc = ((ambientTemp-xmu[0])/xsigma[0])
current=Input(shape=(1,), dtype='float', name='current')
current_enc = ((current-xmu[1])/xsigma[1])

inputs=[ambientTemp, current]
standardizedIns = [ambientTemp_enc, current_enc]
standardized_inputs = tf.keras.layers.concatenate(inputs)
#--model layers
dense1 = tf.keras.layers.Dense(16, activation='relu')(standardized_inputs)
dense2 = tf.keras.layers.Dense(64, activation='relu')(dense1)
dense3 = tf.keras.layers.Dense(64, activation='relu')(dense2)
standardized_outputs = tf.keras.layers.Dense(1, activation='linear')(dense3)

train_model=Model(inputs=inputs, outputs=standardized_outputs)
train_model.compile(optimizer='adam', loss='mse')
train_model.fit(x=X, y=y, epochs=1, verbose=1, batch_size=64,
 shuffle=True);
train_model.save_weights('trainweights.h5')
train_model.save('train_model.h5')  #this works
train_model.summary()

#--- for tf serving, I would like to return unstandardized outputs
liquidLinePressureMean = ((standardized_outputs*ysigma[0])+ymu[0])
outputs=[liquidLinePressureMean]

export_model=Model(inputs=inputs, outputs=outputs, name='model_that_takes_care_of_standardization.h5')
export_model.build(input_shape=[(None,),(None,)]) #is this line necessary/correct?
export_model.summary()
#traceback occurs below
export_model.save('my_model.h5') #this doesn't work

It is curious that the preprocessing steps can serialize fine, but something goes wrong either with the definition/building of the export_model, or with the postprocessing steps...
(I apologize in advance if this is user error and not a bug-- it seems related to issues [here] (https://github.com/tensorflow/tensorflow/issues/19303) and here both of which have seemingly hacky solutions.

2.0.0-dev20190319
2019-03-25 10:43:07.165064: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
5/5 [==============================] - 0s 26ms/sample - loss: 10.0754
Model: "model"
__________________________________________________________________________________________________
Layer (type)                    Output Shape         Param #     Connected to
==================================================================================================
ambientTemp (InputLayer)        [(None, 1)]          0
__________________________________________________________________________________________________
current (InputLayer)            [(None, 1)]          0
__________________________________________________________________________________________________
concatenate (Concatenate)       (None, 2)            0           ambientTemp[0][0]
                                                                 current[0][0]
__________________________________________________________________________________________________
dense (Dense)                   (None, 16)           48          concatenate[0][0]
__________________________________________________________________________________________________
dense_1 (Dense)                 (None, 64)           1088        dense[0][0]
__________________________________________________________________________________________________
dense_2 (Dense)                 (None, 64)           4160        dense_1[0][0]
__________________________________________________________________________________________________
dense_3 (Dense)                 (None, 1)            65          dense_2[0][0]
==================================================================================================
Total params: 5,361
Trainable params: 5,361
Non-trainable params: 0
__________________________________________________________________________________________________
Model: "model_that_takes_care_of_standardization.h5"
__________________________________________________________________________________________________
Layer (type)                    Output Shape         Param #     Connected to
==================================================================================================
ambientTemp (InputLayer)        [(None, 1)]          0
__________________________________________________________________________________________________
current (InputLayer)            [(None, 1)]          0
__________________________________________________________________________________________________
concatenate (Concatenate)       (None, 2)            0           ambientTemp[0][0]
                                                                 current[0][0]
__________________________________________________________________________________________________
dense (Dense)                   (None, 16)           48          concatenate[0][0]
__________________________________________________________________________________________________
dense_1 (Dense)                 (None, 64)           1088        dense[0][0]
__________________________________________________________________________________________________
dense_2 (Dense)                 (None, 64)           4160        dense_1[0][0]
__________________________________________________________________________________________________
dense_3 (Dense)                 (None, 1)            65          dense_2[0][0]
__________________________________________________________________________________________________
strided_slice (TensorFlowOpLaye [None]               0           dense_3[0][0]
__________________________________________________________________________________________________
mul (TensorFlowOpLayer)         [None]               0           strided_slice[0][0]
__________________________________________________________________________________________________
add (TensorFlowOpLayer)         [None]               0           mul[0][0]
==================================================================================================
Total params: 5,361
Trainable params: 5,361
Non-trainable params: 0
__________________________________________________________________________________________________
Traceback (most recent call last):
  File "minimal_example.py", line 65, in <module>
    export_model.save('my_model.h5')
  File "/Users/jamesmckeown/anaconda2/envs/py36/lib/python3.6/site-packages/tensorflow/python/keras/engine/network.py", line 1319, in save
    save_model(self, filepath, overwrite, include_optimizer)
  File "/Users/jamesmckeown/anaconda2/envs/py36/lib/python3.6/site-packages/tensorflow/python/keras/saving/hdf5_format.py", line 103, in save_model
    default=serialization.get_json_type).encode('utf8')
  File "/Users/jamesmckeown/anaconda2/envs/py36/lib/python3.6/json/__init__.py", line 238, in dumps
    **kw).encode(obj)
  File "/Users/jamesmckeown/anaconda2/envs/py36/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/Users/jamesmckeown/anaconda2/envs/py36/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/Users/jamesmckeown/anaconda2/envs/py36/lib/python3.6/site-packages/tensorflow/python/util/serialization.py", line 69, in get_json_type
    raise TypeError('Not JSON Serializable:', obj)
TypeError: ('Not JSON Serializable:', b'\n\rstrided_slice\x12\x0cStridedSlice\x1a\x0fdense_3/BiasAdd\x1a\x13strided_slice/begin\x1a\x11strided_slice/end\x1a\x15strided_slice/strides*\x16\n\x10shrink_axis_mask\x12\x02\x18\x01*\x10\n\nbegin_mask\x12\x02\x18\x00*\x13\n\rellipsis_mask\x12\x02\x18\x00*\x13\n\rnew_axis_mask\x12\x02\x18\x00*\x0e\n\x08end_mask\x12\x02\x18\x00*\x07\n\x01T\x12\x020\x01*\x0b\n\x05Index\x12\x020\x03')

It is also curious to me that the constants used for unstandardizing the output do not show up as Non-trainable params of the second model.  Is this expected behavior?

Possibly related: https://github.com/keras-team/keras/issues/12473

@mckeown12  Were you ever able to solve this problem? I'm having the same issue and not sure what is causing it. It only occurs with tf-nightly.

I ended up using tf.saved_model.save(export_model, '/path/to/save/model') for tf serving.

Just let us know if there is any resolution to this issue.

Yes, @eralmansouri 's solution works for me to save to .h5 as well.  Replacing the line
liquidLinePressureMean = ((standardized_outputs*ysigma[0])+ymu[0])
with
liquidLinePressureMean = tf.keras.layers.Lambda(lambda x: (x*ysigma[0])+ymu[0])(standardized_outputs)
makes my original example work as expected.

@eralmansouri solution solved the problem in my case. I guess the problem comes from the tensorflow op in keras. I converted two of my tensorflow ops to keras layers and the problem no longer exists.
x = tf.image.resize(x, (IM_H, IM_W))
--> x = tf.keras.layers.Lambda(lambda x: tf.image.resize(x, (IM_H, IM_W)))(x)
and
x = tf.math.divide(x, tf.reduce_max(x))
--> x = tf.keras.layers.Lambda(lambda x: tf.math.divide(x, tf.reduce_max(x)))(x)
The output of the network is still the same after the conversion.

For anyone else having this problem, I had success modifying my code from:
concat = tf.concat([foo, bar], axis=3)

To instead use:
concat = tf.keras.layers.Concatenate(axis=3)([foo, bar])

can confirm @krisives solution solved this issue :)

For anyone else having this problem, I had success modifying my code from:
concat = tf.concat([foo, bar], axis=3)

To instead use:
concat = tf.keras.layers.Concatenate(axis=3)([foo, bar])

@krisives Thank you, helped! (My issue was with using tf.reshape, and instead I used tf.keras.layers.Reshape)


make dialogs focusable

Makes dialogs focus-able, makes it possible
to use dialog headers as modal labels, and
automatically set focus when a dialog is displayed.

Failing tests^^, looks like there is a dialog without a header.

@Abbe98, I checked and there are two tests failing.
I'm not sure why the tests are failing in the following two files:

undo_redo.cy.js
importing-data-into-openrefine.cy.js

I see your branch doesn't have the latest Cypress update that was just merged https://github.com/OpenRefine/OpenRefine/pull/5503  but that shouldn't matter.
I just created a new PR for Cypress 12.4.0 and all of the tests are passing.
You could just trigger a new build to see if the failures are repeatable, or pull the latest master which has the updated Cypress.
You could also try running the Cypress tests locally and see if you still get the errors.

I'm not sure why the tests are failing in the following two files:

@elebitzero yeah I think there is a dialog somewhere without a header, will have a look next time I'm on it to see if the code changes should be hardened or if another change is motivated.

I ended up hardening the changes after considering that enforcement of headers might be a breaking change for some extensions.


Fix issue #1

The old version was compile with mysql 5.5.24 but it was unpinned. We can either pin to that version or move to the new packages. However, mysql 5.7.20 does not ship the mysql.h (or it is not in the expected place) and mysql-connector-c seems to the the job.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


NEST removes null value from after_key Dictionary when aggregating

We have a piece of code to do Composite Aggregation on our data, and in it we're running it on two fields with missing_bucket set to true.
Our issue is that when one of the fields becomes null in the data, the after_key is serialized incorrectly on the next request.
Note: At the bottom. There is an absolute minimal reproduction.
Our code (boiled down):
static void Main(string[] args)
{
    IConnectionPool pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
    IConnection connection = new HttpConnection();

    ConnectionSettings connSettings = new ConnectionSettings(pool, connection);
    connSettings.ThrowExceptions();
    connSettings.DisableDirectStreaming();

    ElasticClient client = new ElasticClient(connSettings);

    // Grouping
    SearchRequest<JObject> search = new SearchRequest<JObject>("some_index", "_doc");
    search.Size = 0;

    List<ICompositeAggregationSource> aggregateList = new List<ICompositeAggregationSource>();
    aggregateList.Add(new TermsCompositeAggregationSource("1")
    {
        Field = "PropertyA.keyword",
        MissingBucket = true
    });
    aggregateList.Add(new TermsCompositeAggregationSource("2")
    {
        Field = "PropertyB.keyword",
        MissingBucket = true
    });

    CompositeAggregation compositeAggregation = new CompositeAggregation("composite")
    {
        Sources = aggregateList
    };

    search.Aggregations = compositeAggregation;

    while (true)
    {
        int pageSize = 10; // We use 1000, 10 is for testing
        compositeAggregation.Size = pageSize;

        ISearchResponse<JObject> result = client.Search<JObject>(search);

        BucketAggregate aggA = (BucketAggregate)result.Aggregations["composite"];

        if (!aggA.Items.Any())
            break;

        // Prepare next request
        // This is what fails the next round
        compositeAggregation.After = aggA.AfterKey;

       // .. work with data ..
    }
}

In the above, ES fails our second (or some subsequent request) with:
DebugInformation

# FailureReason: BadResponse while attempting POST on http://localhost:9200/some_index/_doc/_search?typed_keys=true
# Audit trail of this API call:
 - [1] BadResponse: Node: http://localhost:9200/ Took: 00:00:00.0494512
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 400 from: POST /some_index/_doc/_search?typed_keys=true. ServerError: Type: search_phase_execution_exception Reason: "all shards failed" CausedBy: "Type: illegal_argument_exception Reason: "[after] has 1 value(s) but [sources] has 2" CausedBy: "Type: illegal_argument_exception Reason: "[after] has 1 value(s) but [sources] has 2"""
   at Elasticsearch.Net.Transport`1.HandleElasticsearchClientException(RequestData data, Exception clientException, IElasticsearchResponse response)
   at Elasticsearch.Net.Transport`1.FinalizeResponse[TResponse](RequestData requestData, IRequestPipeline pipeline, List`1 seenExceptions, TResponse response)
   at Elasticsearch.Net.Transport`1.Request[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters)
   at Nest.LowLevelDispatch.SearchDispatch[TResponse](IRequest`1 p, SerializableData`1 body)
   at Nest.ElasticClient.Nest.IHighLevelToLowLevelDispatcher.Dispatch[TRequest,TQueryString,TResponse](TRequest request, Func`3 responseGenerator, Func`3 dispatch)
   at ConsoleApp10.Program.Main(String[] args) in C:\Users\MichaelBisbjerg\source\repos\ConsoleApp10\ConsoleApp10\Program.cs:line 89
# Request:
{
	"aggs": {
		"composite": {
			"composite": {
				"after": {
					"1": "value1"
				},
				"size": 10,
				"sources": [{
						"1": {
							"terms": {
								"field": "PropertyA.keyword",
								"missing_bucket": true
							}
						}
					}, {
						"2": {
							"terms": {
								"field": "PropertyB.keyword",
								"missing_bucket": true
							}
						}
					}
				]
			}
		}
	},
	"size": 0
}
# Response:
{
	"error": {
		"root_cause": [{
				"type": "illegal_argument_exception",
				"reason": "[after] has 1 value(s) but [sources] has 2"
			}
		],
		"type": "search_phase_execution_exception",
		"reason": "all shards failed",
		"phase": "query",
		"grouped": true,
		"failed_shards": [{
				"shard": 0,
				"index": "some_index",
				"node": "Z7iIXKGMQZSRN6MDZ1h3Jg",
				"reason": {
					"type": "illegal_argument_exception",
					"reason": "[after] has 1 value(s) but [sources] has 2"
				}
			}
		],
		"caused_by": {
			"type": "illegal_argument_exception",
			"reason": "[after] has 1 value(s) but [sources] has 2",
			"caused_by": {
				"type": "illegal_argument_exception",
				"reason": "[after] has 1 value(s) but [sources] has 2"
			}
		}
	},
	"status": 400
}
# Exception:
Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 400 from: POST /some_index/_doc/_search?typed_keys=true. ServerError: Type: search_phase_execution_exception Reason: "all shards failed" CausedBy: "Type: illegal_argument_exception Reason: "[after] has 1 value(s) but [sources] has 2" CausedBy: "Type: illegal_argument_exception Reason: "[after] has 1 value(s) but [sources] has 2"""
   at Elasticsearch.Net.Transport`1.HandleElasticsearchClientException(RequestData data, Exception clientException, IElasticsearchResponse response)
   at Elasticsearch.Net.Transport`1.FinalizeResponse[TResponse](RequestData requestData, IRequestPipeline pipeline, List`1 seenExceptions, TResponse response)
   at Elasticsearch.Net.Transport`1.Request[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters)
   at Nest.LowLevelDispatch.SearchDispatch[TResponse](IRequest`1 p, SerializableData`1 body)
   at Nest.ElasticClient.Nest.IHighLevelToLowLevelDispatcher.Dispatch[TRequest,TQueryString,TResponse](TRequest request, Func`3 responseGenerator, Func`3 dispatch)
   at ConsoleApp10.Program.Main(String[] args) in C:\Users\MichaelBisbjerg\source\repos\ConsoleApp10\ConsoleApp10\Program.cs:line 89

When debugging, I clearly see that the aggA.AfterKey is a dictionary consisting of two values, but when it's sent to ES again, it's only with one.
I've reproduced the issue further, with just the serializer, using this code:
 void ReproduceSerializer()
{
    IConnectionPool pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
    ConnectionSettings connSettings = new ConnectionSettings(pool);

    ElasticClient client = new ElasticClient(connSettings);

    using (MemoryStream ms = new MemoryStream())
    {
        Dictionary<string, object> dictionary = new Dictionary<string, object>
        {
            {"1", "C:\\" },
            {"2", null }
        };
        client.RequestResponseSerializer.Serialize(dictionary, ms);

        byte[] d = ms.ToArray();
        string p = Encoding.UTF8.GetString(d);

        /*
         Issue: "p" is just
         {
          "1": "C:\\"
         }

        Rather than:
         {
          "1": "C:\\",
          "2": null
         }
         */
    }
}

What version of the client are you using @LordMike?

NEST 6.6.0 contains a fix to serialize CompositeKey null values (#3575 and #3605)
void Main()
{
	IConnectionPool pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
	ConnectionSettings connSettings = new ConnectionSettings(pool);

	ElasticClient client = new ElasticClient(connSettings);

	using (MemoryStream ms = new MemoryStream())
	{
		Dictionary<string, object> dictionary = new Dictionary<string, object>
		{
			{"1", "C:\\" },
			{"2", null }
		};

		var compositeKey = new CompositeKey(dictionary);

		client.RequestResponseSerializer.Serialize(compositeKey, ms);

		byte[] d = ms.ToArray();
		var s = Encoding.UTF8.GetString(d);

		/*
         serializes to
         {
          "1": "C:\\",
          "2": null
         }
         */
	}
}

Would you be able to upgrade to 6.6.0 and try this?

My bad, it was GoT night last night - we're already running 6.6.0. With 6.6.0 I can reproduce your output by using the CompositeKey.
I can see that the AfterKey is of a type that the CompositeKey directly accepts.. So this should be workable :).
.. but .. is that the accepted solution? Shouldn't the AfterKey output from an aggregation be directly feedable back into the After in the requests?

The CompositeBucketAggregate returns the AfterKey as a CompositeKey:
https://github.com/elastic/elasticsearch-net/blob/20c6e7c7a7dbd80aa0bc3c484c20919f68c96aaa/src/Nest/Aggregations/AggregateDictionary.cs#L196-L207
where bucket.AfterKey is
https://github.com/elastic/elasticsearch-net/blob/f3058c96969e1cc161864c7f5f7817f9c0b73fd3/src/Nest/Aggregations/AggregateJsonConverter.cs#L86-L91
So you can pass the AfterKey straight in. Does this work for you?

So instead of (BucketAggregate)result.Aggregations["composite"];, I do (BucketAggregate)result.Aggregations.Composite("composite"); ... if so, I assume this would work, althought I can't test it right now.
The API here is a bit confusing. I arrived at my initial code by inspecting variables to see what they held. I've skipped the methods on AggregateDictionary entirely.. :|

So instead of (BucketAggregate)result.Aggregations["composite"];, I do result.Aggregations.Composite("composite");

Yes, this will work. The first way should be discouraged because BucketAggregate is an intermediate type used internally to hold the data for a number of different aggregations. At the very least, AfterKey on BucketAggregate should be of type CompositeKey. Will open a PR now to fix this in 7.x, and a PR to obsolete it in 6.x, and use a different property.

I've merged in https://github.com/elastic/elasticsearch-net/pull/3800 to mark AfterKey as obsolete on BucketAggregate to discourage its usage, and introduced a CompositeAfterKey property which is of type CompositeKey and will honour null values when being passed into subsequent composite aggregation calls.


Fix: Config key should be 'constraints' instead of 'constrains'

This PR

[x] adds a failing test
[x] fixes a config key, which should be constraints instead of constrains

Related to #462.

:+1:


stream: Check the key before invoking g_hash_table_remove

Turns out that I hit a bug where pa_stream_unref would
call g_hash_table_remove with a NULL key.
Thanks for the lightweight and smooth error handling from
Glib, g_hash_table_remove generated an ABORT call, crashing
the Unity3D games (e.g. Wizards of Legend) I was trying to start.
Now, I discovered that g_hash_table_lookup CANNOT be called with a NULL
key. That also generate a crash... Ugh...
So, yeah, basically to avoid this bug, run the game and get some nice sound
in the headphones, here's what I did :

check that the key is not NULL (0)
check that the key is actually inside the Hash table
and THEN call g_hash_table_remove.

Note, here's my ~/.asoundrc, just in case :
defaults.pcm.!card Audio
defaults.ctl.!card Audio

Audio being a FiiO USB device where my headphones are connected to :
card 3: Audio [DigiHug USB Audio], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 3: Audio [DigiHug USB Audio], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Signed-off-by: Miouyouyou (Myy<EMAIL_ADDRESS>

I guess that this might not be the good way (TM) of handling such bugs. Searching for why the key is NULL at this point would be far better, but I didn't have enough time to delve into this and... the fix works !

I guess that this might also fix bug #98


Model superposition problem

When embedding small models in a large model and using the Splats rendering mode, there may be issues with the rendering display, and depth judgment was not made. After trying to add depth judgment, the display effect of the model was poor. When using Debug Points rendering mode, the depth and position information of the model are rendered normally, but there is no rendering effect of Splats. I am a novice in the rendering field. Can you guide me on how to balance depth and rendering effects?

Yes, when multiple gaussian splats overlap each other, they often are not "composited" properly. See "Rendering order of multiple Gaussian Splat objects" here https://github.com/aras-p/UnityGaussianSplatting/blob/main/docs/render-pipeline-integration.md#rendering-order-of-multiple-gaussian-splat-objects


lost stacktrace after promise is resolved

Describe the bug
Lost stacktrace after promise is resolved.
$ yarn start
============================== step_1 ==============================
Error
    at Object.next (file:///C:/Projects/rxjs-bug-report-0/src/main.js:13:25)
    # .....
    at file:///C:/Projects/rxjs-bug-report-0/src/main.js:25:1
    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
    at async loadESM (node:internal/process/esm_loader:28:7)
    at async handleMainPromise (node:internal/modules/run_main:113:12)
============================== step_2 ==============================
Error
    at Object.next (file:///C:/Projects/rxjs-bug-report-0/src/main.js:18:25)
    # lost stack trace
finish

Expected behavior
Expect
Stacktrace must be maintained after promise is resolved.
$ yarn start
============================== step_1 ==============================
Error
    at Object.next (file:///C:/Projects/rxjs-bug-report-0/src/main.js:13:25)
    # .....
    at file:///C:/Projects/rxjs-bug-report-0/src/main.js:25:1
    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
    at async loadESM (node:internal/process/esm_loader:28:7)
    at async handleMainPromise (node:internal/modules/run_main:113:12)
============================== step_2 ==============================
Error
    at Object.next (file:///C:/Projects/rxjs-bug-report-0/src/main.js:18:25)
    # .....
    at file:///C:/Projects/rxjs-bug-report-0/src/main.js:25:1
    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
    at async loadESM (node:internal/process/esm_loader:28:7)
    at async handleMainPromise (node:internal/modules/run_main:113:12)
finish

Reproduction code
Error.stackTraceLimit = Infinity;

import { of, mergeMap, tap } from 'rxjs';

const delay = (timeout) => new Promise((resolve) => {
    setTimeout(resolve, timeout);
})

const start = () => {
    of(null).pipe(
        tap(() => {
            console.log('============================== step_1 ==============================');
            console.log(new Error().stack);
        }),
        mergeMap(async () => await delay(1000)),
        tap(() => {
            console.log('============================== step_2 ==============================');
            console.log(new Error().stack);
        }),
    ).subscribe(() => {
        console.log('finish');
    });
}

start();

Reproduction URL
https://github.com/ChoSeoHwan/rxjs-bug-report-0
Version
7.8.1
Environment

NodeJS : 20.11.0
rxjs : 7.8.1

Additional context
No response

Everything that happens after the promise is resolved (when the microtask fires) happens synchronously in nested functions, and is no different than if you were to do something like:
(async () => {
  await delay(1000)
  console.log(new Error().stack);
})()

Or more accurately:
const delay = (timeout) => new Promise((resolve) => {
    setTimeout(resolve, timeout);
});

(async function mergeMapNext() {
  await delay(1000);
  rxjsLogic();
})();

function rxjsLogic() {
  tapNext();
}

function tapNext() {
  innerTapNext();
}

function innerTapNext() {
  userProvidedFunction();
}

function userProvidedFunction() {
  console.log(new Error().stack);
}

That said, I couldn't replicate the issue myself<EMAIL_ADDRESS>And I also tried cloning your repository and checking on the same version of node. I couldn't reproduce the issue.
I would recommend that you look up "why is my stack trace missing in node?" because it seems to be a condition of errors being thrown after promise resolution in specific versions of node? Although I tried the same one and could reproduce the bug.
Regardless, this doesn't seem to have anything to do with RxJS, because we can't really control the call stack produced by new Error().stack.


Extend FakeDatasets for All Tasks

🚀 The feature
Fake Datasets help us to quickly verify and validate if the instantiated model would work fine. This enables quick validation for testing purpose as well as for faster prototyping.
We already have FakeDataset in torchvision for the same, but it supports only ImageClassification as of now.
Motivation, pitch
We should have multiple FakeData classes. Like ImageClassificationFakeData, ObjectDetectionFakeData.
If we do that, we should deprecate FakeData in favor of ImageClassificationFakeData.
We could also think of supporting different formats. E.g. Support xywh as well as xyxy format? Support formats such as Binary masks, boolean masks etc? (Not sure of this need to discuss)
Alternatives
Other libraries are maintaining something similar to test models. These libraries mostly wrap torchvision models into their framework equivalent codes and test on sample datasets.
https://github.com/Lightning-AI/lightning-bolts/blob/master/tests/models/test_detection.py
https://github.com/Lightning-AI/lightning-flash/blob/master/tests/image/detection/test_model.py
https://github.com/oke-aditya/quickvision/blob/master/tests/dataset_utils.py
Additional context
@pmeier please chip in your thoughts!
cc @pmeier

If we want a fake dataset for all of our models, we need to cover the following tasks:

Image / Video classification
Semantic Segmentation
Object Detection, Instance Segmentation, Keypoint Detection
Optical Flow

How does a sample look like for each of these tasks?

We already have FakeDataset in torchvision for the same, but it supports only ImageClassification as of now.

That is only partly true. datasets.FakeData returns Tuple[PIL.Image.Image, int], but we can't pass that into a model directly. You will have to convert the PIL image to a tensor.
Plus, FakeData also supports the transform and target_transform parameters, which contradicts your assessment that it is used for model validation somewhat. If it were, there would be no need for any transforms, because the data is already in the right shape.

We could also think of supporting different formats. E.g. Support xywh as well as xyxy format? Support formats such as Binary masks, boolean masks etc? (Not sure of this need to discuss)

I don't think this is necessary. If the goal is to validate a model, we only need to provide datasets for inputs that our models support.
For testing, we already have functions to create all sort of images, bounding boxes, masks and videos in https://github.com/pytorch/vision/blob/main/test/prototype_common_utils.py. Of course we need to strip out all the torchvision.prototype stuff, but otherwise we can use that. TBH, I wanted to have a torchvision.testing namespace for quite some time that includes functions like make_image_tensor, make_image_pil, make_bounding_box, and the like. That would also make it quite a bit easier for third parties to test their stuff. But this is a different discussion.

Sorry for delay. Although I haven't thought much about this yet.

That is only partly true. datasets.FakeData returns Tuple[PIL.Image.Image, int], but we can't pass that into a model directly. You will have to convert the PIL image to a tensor.

Can we return a Tensor from the dataset? Or a dict[str, Tensor] This would not require target transforms and transforms etc, as they aren't necessary for these functions.

For all new datasets, we can return whatever we want. Of course that should match what the model down the line needs or otherwise the dataset is not useful.
For image classification, we need to keep BC. We can have a image_tensor: bool = False flag on there to enable the option to return tensors directly, but PIL images should still be the default. If we strongly feel that tensors should be the default, we could also go through a deprecation cycle, but IMO so far there is not enough traction for that.


Cloudflare Origin Certs

What is your feature idea?
Support cloudflare origin certs in addition to letsencrypt so we can speed up cluster create times and harden our production stance.
Why is it needed?
letsencrypt runs out of certs consistently effectively making tlds useless for a week at a time.
Is this missing feature preventing you from using kubefirst?

[X] Yes

Code of Conduct

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

@johndietz took over this task due until @jarededwards is back


A Scan has a failure.. Please approve to proceed

Approval required for following Workflow to proceed.

WorkflowName
Workflow#
BranchName
TriggerEvent
LastCommitUser

debug-Api
112
refs/heads/debug
push
Yog4Prog

Issue Details
Found an Issue while performing SCA Scan
:point_right: You are required to Approve (or) Reject the issue
Approve or Reject by commenting in the below section with any of the following keywords
:green_book:  Approved Keys: approved approve lgtm goahead proceed yes
:closed_book: Reject Keys: denied deny reject rejected no abort cancel exit
:point_right: Note: If left uncommented the issue will be closed after the timeout period and the workflow will be marked unsuccessful.

approved


Enhancement: Color management for Houdini workfiles

Changelog Description
This PR adds Houdini workfiles color management

Display: default display, it accepts Colon-separated list of displays, e.g ACES:P3, Read more Active Displays
View: default view, it accepts Colon-separated list of view names, e.g sRGB:DCDM Read more Active Views
Review Colorspace : Review output transform which exposes OCIO Colorspace parameter in opngl nodes, Read more Houdini OpenGL

Things to do:

[x] Set default view and default display: In Houdini this is done via setting OCIO_ACTIVE_DISPLAYS OCIO_ACTIVE_VIEWS
[x] make review creator and validator to use review color space value specified in the settings
[x] update color space data while review extraction
[x] update color space data while houdini image sequence extraction (P.S. It's  the colorspace name assigned to scene_linear role.)
[x] fix the conflict mentioned here https://github.com/ynput/OpenPype/pull/5858#discussion_r1387651765

Testing notes:

Test the hook functionality, case 1:

test : disable global color management, enable  houdini color management, enable  color management/workfile
result : Hook won't work.

Test the hook functionality, case 2:

test : enable global color management, disable houdini color management, enable  color management/workfile
result : Hook won't work.

Test the hook functionality, case 3:

test : enable global color management, enable houdini color management, disable color management/workfile
result : Hook logs to console that workfile settings are disabled.

Test the hook functionality, case 4:

test : enable global color management, enable houdini color management, enable color management/workfile
result : Hook sets the proper environment variables with values specified in the Houdini settings, it logs to console the environment variables and in houdini you are able to see the only color spaces specified in the settings.

Test Review colospace, case 1:

test : leave Review colospace empty
result : default review colorspace will be used when

creating review instances
using Set Review Color Space action if Validate Review Colorspace failed

Test Review colospace, case 2:

test : add you preferred Review colospace value
result : this value will be used when

creating review instances
Validate Review Colorspace will check if ociocolorspace parameter has that value
using Set Review Color Space action if Validate Review Colorspace failed

To me this issue https://github.com/ynput/OpenPype/issues/67 looks similar to https://github.com/ynput/OpenPype/issues/4836 ? Are they duplicates ? if yes, tell me to make this PR close it as well.

@MustafaJafar That does seem like the same thing, but I do want to note that to 'get on par with nuke' and others likely we also need to test:

(Image) Outputs from Houdini should also submit along their colorspace data if they don't already do that, so we should make sure published data for e.g. published renders or COP2 networks include colorspace information if that publish itself can have that information from Houdini of course.
Potentially when loading say an image or anything it'd also automatically set the correct colorspace value - but purely checking out COP2 file nodes I don't see anything with regards to OCIO there at all?

To me this issue #67 looks similar to #4836 ? Are they duplicates ? if yes, tell me to make this PR close it as well.

@MustafaJafar That does seem like the same thing, but I do want to note that to 'get on par with nuke' and others likely we also need to test:

(Image) Outputs from Houdini should also submit along their colorspace data if they don't already do that, so we should make sure published data for e.g. published renders or COP2 networks include colorspace information if that publish itself can have that information from Houdini of course.
Potentially when loading say an image or anything it'd also automatically set the correct colorspace value - but purely checking out COP2 file nodes I don't see anything with regards to OCIO there at all?

This is interesting!
Currently, I have no idea how to achieve that but let's find out!

To me this issue #67 looks similar to #4836 ? Are they duplicates ? if yes, tell me to make this PR close it as well.

@MustafaJafar That does seem like the same thing, but I do want to note that to 'get on par with nuke' and others likely we also need to test:

(Image) Outputs from Houdini should also submit along their colorspace data if they don't already do that, so we should make sure published data for e.g. published renders or COP2 networks include colorspace information if that publish itself can have that information from Houdini of course.
Potentially when loading say an image or anything it'd also automatically set the correct colorspace value - but purely checking out COP2 file nodes I don't see anything with regards to OCIO there at all?

I dont think COP2 has any OCIO-related Nodes and variables. /mat and/out network can allow the users to set up the ocio config for some nodes and general setting itself has the OCIO supports too.
I agree that we should submit along with the colorspace data and we should make published data to include colorspace information.(Although there is already a good for colorspace data, that one may need some refactoring)

As far as I know, Houdini is limited in this topic.
In short:
Houdini implicitly uses scene_linear role by default when reading textures and rendering
Textures

Houdini assumes:

8-bit ➝ sRGB
more than 8-bit ➝ scene_linear

Texture node in materials options are either linear or sRGB or Rec 709,  Only redshift and Vray texture nodes support colorspace setting.

File read node in COP2 options are either linear or sRGB

Render Space

OpenGL ROP: supports applying output transform (I guess it means: it renders in scene_linear then convert to another colorspace), setting output transform is supported in this PR.
Arnold ROP: supports setting render space
Karma  ROP: supports setting render space
Mantra : I didn’t find any colorspace options, therefore I'll assume it's linear.
Red Shift ROP: supports setting render space
USD Render : I don’t know
V-Ray ROP: supports setting render space
RenderMan : I didn’t find any colorspace options, therefore I'll assume it's linear.
Comp ROP: supports LUTs but not colorspace, therefore I'll assume it's linear.

Thanks @MustafaJafar I think if this PR soles the fact that the OCIO config display and view gets set from Settings (if it is set) then I think just fixing up the Review extraction + validator for now might be sufficient for this PR and then take the remainder as per your last comment's finding into a separate Issue and PR.

Checkpoint
Houdini workfile color settings update.

Ayon
OpenPype

Set ociocolorspace parameter for the review rops works as follows:

if workfile settings are enabled, it will use the value exposed in the settings.
if workfile settings are disabled, it will use the default colorspace corresponding to the display & view of the current Houdini session.

Thanks @MustafaJafar I think if this PR soles the fact that the OCIO config display and view gets set from Settings (if it is set) then I think just fixing up the Review extraction + validator for now might be sufficient for this PR and then take the remainder as per your last comment's finding into a separate Issue and PR.

So, the next step is to include the colorspace data in the representation ?
If yes, I think it can be done for render, review and campsite products.
color space is either the exposed value in node parameters or scene_linear role.

Checkpoint
Houdini workfile color settings update.
Ayon OpenPype

Set ociocolorspace parameter for the review rops works as follows:
* if workfile settings are enabled, it will use the value exposed in the settings.

* if workfile settings are disabled, it will use the default colorspace corresponding to the display & view of the current Houdini session.

Admittedly the label on that boolean is confusing - I'd expect it to read "Do not validate review colorspace" or "Ignore review colorspace validation" or whatever. It doesn't in itself override review colorspace, it just says "Do not validate it"
I wonder actually whether we couldn't just expose the ValidateReviewColorspace in publish plug-in settings so that a studio pipeline can set it to be optional, enabled, active or not like other plug-ins allow. With that, we don't need this checkbox here at all and it aligns more with enabling/disabling other plug-ins.

Admittedly the label on that boolean is confusing - I'd expect it to read "Do not validate review colorspace" or "Ignore review colorspace validation" or whatever. It doesn't in itself override review colorspace, it just says "Do not validate it"

check OCIO
check "colorcorrect" parameter
check if "ociocolorspace" parameter has correct value
check if "ociocolorspace" parameter has the same value in the settings

The boolean override_review_color is meant to skip only the fourth check which enable users to override colorspace.

I wonder actually whether we couldn't just expose the ValidateReviewColorspace in publish plug-in settings so that a studio pipeline can set it to be optional, enabled, active or not like other plug-ins allow. With that, we don't need this checkbox here at all and it aligns more with enabling/disabling other plug-ins.

There are many ways to achieve the same thing, I thought it'd be clearer if I put all settings related to colorspace in Houdini/Color management/workfile

Thanks - I see, I initially thought it'd just disable the whole plugin. I still think "allow any color space for reviews" or "do not validate review colorspace" would be better labels.
Also, if the user would not allow any color space for reviews but wants it strictly validated, then the validator shouldn't be optional? So maybe the settings should be closer together still?

Also, if the user would not allow any color space for reviews but wants it strictly validated, then the validator shouldn't be optional? So maybe the settings should be closer together still?

Yes, you are correct and the logic is intertwined!
Let's keep it simple then.
what about:

Workfile color settings should contain Display, View and Review colorspace only
when creating review instance, if color settings are enabled, it will use the  Review colorspace otherwise it will use the default review color space.
Tell admins to keep Review colorspace empty to stick to the default output transform. (I think this is far simple than adding a boolean to the validator)

Regarding my last commit, I don't know what to expect,
Here are some screenshots to show how it looks like on my side.
How it looks like in Houdini view port

How it looks like in DJV

How it looks like in Nuke,

How it looks like in Nuke, after changing colorspace to aces

How it look like in loader,
should I find colorspace data in version info ?

My representation data:
[
    {
        "name": "png",
        "ext": "png",
        "files": [
            "reviewMain.1000.png",
            "reviewMain.1001.png",
            "reviewMain.1002.png",
            "reviewMain.1003.png",
            "reviewMain.1004.png",
            "reviewMain.1005.png",
            "reviewMain.1006.png"
        ],
        "stagingDir": "\\\\storage\\work\\openpype_projects\\RoboPype\\Assets\\Character\\WarRobo\\work\\CFX\\pyblish\\reviewMain",
        "frameStart": 1000,
        "frameEnd": 1006,
        "tags": [
            "review"
        ],
        "preview": True,
        "camera_name": None,
        "colorspaceData": {
            "colorspace": "Output - sRGB",
            "config": {
                "path": "E:\\Ynput\\OpenPype\\vendor\\bin\\ocioconfig\\OpenColorIOConfigs\\aces_1.2\\config.ocio",
                "template": "{BUILTIN_OCIO_ROOT}/aces_1.2/config.ocio"
            }
        }
    }
]

should I find colorspace data in version info ?

I wish, but unfortunately no. It was almost there but this PR https://github.com/ynput/OpenPype/pull/5459 by @fabiaserra got closed down. We should make a new AYON compatible equivalent PR if you can!

I think about adding colorspace data to  houdini image sequence which is the colorspace name assigned to scene_linear role.
what about render products too ?
I think it will be product type wise as some ROPs have explicit render space setting.

what about update color space data for render products ?

I think it's already added!
I can find it in render collectors, mantra collector for example
https://github.com/ynput/OpenPype/blob/d34ac5637e1d8b9c832309efb22fd79d0a94fb2b/openpype/hosts/houdini/plugins/publish/collect_mantra_rop.py#L92-L96
but it doesn't follow the same structure provided by set_representation_colorspace
openpype.pipeline.publish.ColormanagedPyblishPluginMixin.set_representation_colorspace

I have no idea about render publishes, they don't seem to have any extractors or any representation dictionary.

Revisiting the conflict mentioned here https://github.com/ynput/OpenPype/pull/5858#discussion_r1387651765
I woke up with an idea and decided to test it quickly.
Setting environment variables follows this order
where each one will override its predecessor
# Global > Application > Tool > Houdini_project_settings
# e.g.
Global: {"OCIO_ACTIVE_VIEWS": "DCDM"}
Application: {"OCIO_ACTIVE_VIEWS": "P3D65"}
Tool: {"OCIO_ACTIVE_VIEWS": "P3-D60"}
Houdini_project_settings: {"OCIO_ACTIVE_VIEWS": "sRGB"}  # wins

result = {"OCIO_ACTIVE_VIEWS": "sRGB"}

# also, we can do this (I'll disable my Houdini_project_settings )
Global: {"OCIO_ACTIVE_VIEWS": "DCDM"}
Application: {"OCIO_ACTIVE_VIEWS":  ["{OCIO_ACTIVE_VIEWS}", "P3D65" ]}
Tool: {"OCIO_ACTIVE_VIEWS":  ["{OCIO_ACTIVE_VIEWS}", "P3-D60" ]}

result = {"OCIO_ACTIVE_VIEWS" : "DCDM;P3D65;P3-D60"}  # which is ignored because OCIO expects `:` joined string

In my hook, I don't have to worry about anything because self.launch_context.env.get("OCIO_ACTIVE_VIEWS") to do it.
So, here's one simple solution.
OCIO_ACTIVE_VIEWS = self.launch_context.env.get("OCIO_ACTIVE_VIEWS")
houdini_color_settings = \
            self.data["project_settings"]["houdini"]["imageio"]["workfile"]
default_view = houdini_color_settings["default_view"]
default_view = ":".join([default_view, OCIO_ACTIVE_VIEWS] )

so, this will happen if we used environment variables as usual while keeping the value empty

and this will happen if we used both

I've added some tool tips in Ayon settings based upon this comment https://github.com/ynput/OpenPype/pull/5858#discussion_r1403151594

Happy to merge when we get some testing and approvals here.

Quick Note regards review colorspace:

Empty Review colorspace setting keeps review colorspace unmanaged which allows artists to pick any colorspace value

Set Default Review Color Space 🖥 will set OCIO Colorspace parm in the open gl node to the same value of Review colorspace settings. and if setting is empty, it will fall to default according to the default active view and display.

why is there a console window poping up when you click Set default review colorspace?

because of get_default_display_view_colorspace().
These function were added in https://github.com/ynput/OpenPype/pull/5322
https://github.com/ynput/OpenPype/blob/91a1fb1cdbff63442426b1b0e6bb6768a17aa49e/openpype/hosts/houdini/api/colorspace.py#L59-L69
https://github.com/ynput/OpenPype/blob/91a1fb1cdbff63442426b1b0e6bb6768a17aa49e/openpype/pipeline/colorspace.py#L1142-L1162

Because we're splitting OpenPype into ayon-core and individual host addons, this PR would have to be re-created to target one of those.
We're closing it down, but we'll he happy for a new PR to ynput/ayon-core or the host addon repository once it's up.


fix bad format

Fix https://github.com/kubernetes/website/issues/19485

need fix conflicting files or close pr.

need fix conflicting files or close pr.

rebased

why delete annotation? after checking the link, I found no errors
https://kubernetes.io/zh/docs/tasks/configure-pod-container/configure-pod-configmap/

https://kubernetes.io/zh/docs/tasks/configure-pod-container/configure-pod-configmap/

seems fixed

ping @SataQiu
cloud you approve this PR now?


Add Realtime to SERVER

Adds realtime multiplayer functionality to RPG Maker MV, allowing for an "mmo-like" experience.
Realtime multiplayer using Socket.io
Battles are handled in the same scene/map (not a separate battling scene)
Registration and login from remote database
On screen health/mp/level/exp
and more tbh

Most of that is already here.....and the rest can be done with plugins from the community with the exception of the ABS.  For that......I'm not doing that.


do not run tests twice

@ReimarBauer Do you have an idea, why this does not work? On data-retrieval, this (seems to?) works as expected...


[ENHANCEMENT] Decide on default position definitions for eltype and ndims

Right now there is a generic definition for any AbstractArray subtype that the first parameter is eltype and the second is ndims, that is of course incorrect for some AbstractArray subtypes but it is a very convenient definition since most AbstractArrays follow that convention.

We could make it a bit safer and define position(type::Type{<:AbstractVecOrMat}, ::typeof(ndims)) = error("No position.") which would catch many cases I can think of where the current definition is wrong.

We could make it a bit safer and define position(type::Type{<:AbstractVecOrMat}, ::typeof(ndims)) = error("No position.") which would catch many cases I can think of where the current definition is wrong.

Actually never mind, that wouldn't be a good idea since many AbstractVecOrMat are type aliases of an AbstractArray in which case ndims is a type parameter (that happens to be hard-coded to a certain value).


THRIFT-3357: enum_containers option to generate EnumSet/EnumMap

Additional java compiler option to generate EnumSet/EnumMap instead
of HashSet/HashMap where elements/keys are enums.

https://issues.apache.org/jira/browse/THRIFT-3357

I'm perfectly fine to make it default.
Theoretically possible issues is that someone heavily relies on HashMap/HashSet or uses null keys/elements (EnumMap/EnumSet does not allow null keys/elements). But in that case, we indeed, need to make it default to punish them.

Created a new pull request here: https://github.com/apache/thrift/pull/1253