text:
update doc site

Updates the doc site to include changes required for https://github.com/GoogleCloudPlatform/google-cloud-php/pull/373

LGTM

authors: dwsupplee jdpedrie

repo: GoogleCloudPlatform/google-cloud-php


text:
Update ReadMe to reflect quality levels of client libraries

We will soon have client libraries at different quality levels. Let's make sure we reflect this information in our top-level ReadMe file the moment we cut the new release.
The update for PHP's ReadMe has already be done (as a Pull Request for now) and can be used as the canonical example to follow. The list below highlights the main changes to follow for this repo.
General

[ ] Remove the text "This project supports the following Google cloud Platform services:"

Listing Beta client libraries

[ ] Create a section to show the Beta client libraries (see image right below for text & layout)

[ ] Make the term Beta link to the Versioning section of the ReadMe (see image right below)

[ ] Add the term (Beta) next to each API name (see image right below for text and visual):

Listing Alpha client libraries

[ ] Create a section to show the Alpha client libraries (see image right below for text and layout)

[ ] Make the term Alpha link to the Versioning section of the ReadMe (see image right below)

[ ] Add the term (Alpha) next to each API name (see image right below for text and visual):

Versioning section

[ ] If the Versioning section doesn't exist, add one.

[ ] Add the following content in the Versioning section:

I assume we can close this issue?

source: gharchive/issue

repo: GoogleCloudPlatform/google-cloud-python

license_type: permissive

license_source: github-api


text:
Adding scope to error reporting client.

/cc @jonparrott
Fixes #3263
FWIW I have no idea if this is the correct scope, I couldn't find one in the official docs but I just based it off the scopes in the discovery doc

@waprin I take your merging as an affirmation that the scope I picked was correct?

It's right as far as I know and the docs go.

source: gharchive/pull-request

authors: dhermes waprin


text:
add derivative image builds for oslogin

add the same kind of derivative image build and test steps as we have in guest agent build.

/lgtm

authors: hopkiw zmarano

repo: GoogleCloudPlatform/guest-test-infra

license_source: bigquery


text:
Make net container invisible to the end users.

Kubelet now only reports ContainerStatus. PodStatus / PodCondition is observed at master side based on a set of ContainerStatus. There is no other way to get PodIP except net container for master side.
This is very confusion to the end user, #3427, #3429, ...
Now we are finalizing on v1beta3 API, including PodStatus & ContainerStatus. We can make net container completely invisible to the end users by finishing the following steps:

Expose network related errors at API level
Generate PodStaus directly from Kubelet

once PodStatus generated by kubelet, PodIP can be removed from ContainerStatus.

@thockin @brendandburns @bgrant0607

I think reporting PodStatus rather than just container status is most important. How hard is that?

@bgrant0607 Used to be hard since there are many dependencies when I first report Status back. Now it is totally feasible. I already started to write PRs for this. :-)

One more PR required to close this one.

repo: GoogleCloudPlatform/kubernetes


text:
rkt: Support ports with no names

rkt support assumes all ports have names while this is not always the case in Kubernetes. We should create default port names in these situations.
/cc @yifan-gu @jonboulle @dchen1107

Yes. Maybe something like protocol:port such as TCP:80 ?

SGTM

as long as you make sure it is unique in the pod, which means you actually
have to test it and add a suffix if needed
On Tue, May 5, 2015 at 9:38 AM, Yifan Gu notifications@github.com wrote:

Yes. Maybe something like protocol:port such as TCP:80 ?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/7710#issuecomment-99134513
.

@thockin OK, then prefix with the container name should be good IMO

I don't think we defend against exposing the same protocol-port twice in a
single container, so be defensive.
On Tue, May 5, 2015 at 9:44 AM, Yifan Gu notifications@github.com wrote:

@thockin https://github.com/thockin OK, then prefix with the container
name should be good IMO
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/7710#issuecomment-99136103
.

@thockin Why we expose the same protocol-port twice? Is that something we could add to the validation of the pod spec?

Consider exposing two host ports for the same pod.  I know it is a stretch,
but we don't defend it now.  Should be relatively easy to validate, but the
error message infrastructure we have does not have an obvious function to
call to say that the combination of some fields is not valid.
On Tue, May 5, 2015 at 10:06 AM, Yifan Gu notifications@github.com wrote:

@thockin https://github.com/thockin Why we expose the same
protocol-port twice? Is that something we could add to the validation of
the pod spec?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/7710#issuecomment-99142880
.

authors: thockin vmarmol yifan-gu


text:
Is this repo maintained?

The abstractions provided by MetaController look really nice.   I'd love to use it for a project.
However, it looks like a PR hasn't been merged since March, and the maintainers haven't replied to an issue in about that long.
Is this maintained?

In short, no. I was the only maintainer at the time when I left Google at the end of March. I don't have access to merge anything on this repo since Google still owns it.

Metacontroller is a great project, and it would be terrible to see it wither. @enisoc who would be the most appropriate contact to discuss possible futures for this effort?

@AmitKumarDas has been doing experiments on a fork (https://github.com/AmitKumarDas/metac) and has mentioned that he'd be interested in upstreaming that work if a new home is found for the project.

@enisoc - thanks for all your efforts on this project, I also think it is a great one.  I hope you remain involved in some capacity.

I would be glad to contribute and maintain MetaController in whatever form the community decides. Is there anyone who can start a new home/repo etc? Do we need any approvals from its current owner?

Same here, ive actually finished developing a rabbitmq controller, that creates rabbit resources based on my crd.
I intend to add it into production - is this a risk?

@AmitKumarDas @enisoc I think the airship project (https://www.airshipit.org/) may happy to host this project, but that would also depend on the current owner's desires.

Perhaps @droot can comment on whether Google intends to do anything with this repo.
As for myself, much to my own surprise, it turned out that between a startup and a toddler, I don't have enough free time to maintain this as a side project. However, if someone decides to take on the maintainer role on their own fork, I would be interested in contributing.

I would be interested in helping to maintain this, we've found it to be a really useful abstraction

@droot and I have been talking about this in the background a bit.  I think our team (the KubeBuilder team) can take over maintenance here, but we've got some logistics to figure out about long-term maintenance, new features, etc.
In the short term, we'd like to rebase the internals on controller-runtime, so that we're not maintaining two similar but distinct codebases.

but we're also very happy to have community help as well from anyone who is interested
e.g. @AmitKumarDas @mikebryant

It will be really good to have this embedded into controller-runtime and get more community support.
Let me know if there are any proposals with this investigation & I will be happy to join.

Let me know if there are any proposals with this investigation

I did some hacking last night on replacing the internals with controller-runtime.  There are currently some blockers (e.g. no way to "stop" controllers easily in controller-runtime w/o stopping the entire set of informers).  Some of these might be mitigated if the proposal to move to a sidecar-based approach (e.g. sidecar means you're not starting and stopping controllers on demand).
I'd like to figure out a plan to move towards controller-runtime internals, so any input there would be super-helpful.  If anyone's super-interested in tackling it themselves, I'm happy to provide guidance.
In the mean time, we'll figure out how to get correct permissions set up for this repo.
Additional things that would be helpful immediately from community members:

Issue triage: there are a lot of issues in this repo that seem inactive.  It'd be good to get questions answered, up-to-date bug reports tagged as such, and enhancement requests tagged as such.

@enisoc @DirectXMan12 @AmitKumarDas - just wondering if this could be a kubernetes sig project?

Quite possibly -- we'd need to figure out the logistics, but I think it makes sense to put it under the server-sdk subproject (a.k.a. the KubeBuilder subproject)

Just wondering, if all of us agree to continue with the original purpose of MetaController. In other words, it provides us with couple of controller implementations (abstracts the developers from programming to k8s knowledge) and lets us focus more into business logic side of things.

I'll let others weigh in too, but my take is this:
metacontroller lets you program your controllers in any language, in a "pure" (in the functional programming sense) way, without having to worry about side effects.  You're always going to have to worry about k8s to some degree (e.g. finalizers), but you shouldn't have to worry about trying to connect to k8s directly, make API requests directly etc -- you should just be able to take inputs and return what you want to happen (i.e. the state of the world).

Hi -
My hope is that MetaController would retain the spirit of it's original ethos, in that it enables people like me to program essentially stateless controllers in any language of my choice, only caring about emitting a JSON document (I like the existing format) to describe the resources that I want associated with my CRD.
In it's existing state, it has created a toolkit that gives a very low barrier to entry (for instance I don't need to understand much about controllers, Go, or k8s libraries), and makes it easy as a DevOps/SysAdmin to create "throwaway" operators for my organisation/workplace/life/etc.
For example, an acid test of it's future would be that any changes made going forward would not break existing MetaController operators in the wild (or at least without very good reason...).
It would be good to see some sort of new MetaController road map (https://github.com/GoogleCloudPlatform/metacontroller/issues/9) come out of this, which would help clear up any ambiguities around aspirations.
Thanks,
Piers Harding.

I'd add to the roadmap a support to bring more objects with the sync request,
For example, I have a crd with sensitive values, so I saved them in a secret, addad a ref field in my crd, gave rbac clusterrole permissions to that specific secret (for my custom controller), then used kubernetes API to retrieve the secret in the controller.
Would be nice to define resources that metacontroller will bring to the request (like according to annotations)

So, will this project be moved to the kubernetes-sigs org?

So, will this project be moved to the kubernetes-sigs org?

We need to decide that, and there's logistics to work out, but it seems reasonable to me.
@piersharding I think we're mostly in agreement there, and I don't think any breaking changes would be made w/o introducing a new major version.

Sounds like we should get on call to discuss further on the logistics and the roadmap/approaches? Is there a sig community meeting where we can add this as a agenda topic? or setup a new call?

You can propose it for the kubebuilder meeting next month, but I think there's some stuff to figure out on our end too.

@DirectXMan12 I wanted to propose MetaController for kubebuilder meeting. However, I am not sure of the meeting/doc link.

join the kubebuilder mailing list listed in https://github.com/kubernetes-sigs/kubebuilder#resources and you'll get a calendar invite with the details

We discussed this a bit in the KubeBuilder meeting today.  The KB community is supportive of this.
I think the next step here would be to have someone from the metacontroller side write up a little proposal for this that we can submit to kubernetes.  I'd be happy to review or provide guidance.

Maybe @AmitKumarDas since he's maintaining the only active fork of metacontroller??

metacontroller is just enough abstraction for non GO programmers like me.  it would be great to see this project maintained

All. Just wanted to give an update w.r.t submitting a proposal to add metacontroller to KB community.
I have been busy all these days and have not been able to write the proposal. It will be great if anyone in the community can send out the proposal. I have been talking with some of the metacontroller users to do the same without any success.

Happy New Year Everyone.
Some of us including @alaimo @piersharding @kmova have put together the initial draft proposal to maintain Metacontroller as a project in kubernetes-sigs.
Here is the link to the draft. We would like to hear what others think about this proposal. I would definitely need help from @DirectXMan12 @enisoc @mikebryant @luisdavim & others with their suggestions to help move this proposal forward.
cc @rosenhouse @debianmaster @arielb135 @intlabs

Thanks @AmitKumarDas for the update. And Thanks everyone who is helping with the proposal.
I will review the proposal and leave comments there. Happy to help with the next steps.

any news on this?

@floriankoch you may find latest discussions here
We are waiting for final approval from either @DirectXMan12 or @droot to submit a KEP.

@AmitKumarDas   Thx

authors: AmitKumarDas DirectXMan12 arielb135 debianmaster droot enisoc floriankoch intlabs kmova luisdavim mikebryant piersharding rosenhouse

repo: GoogleCloudPlatform/metacontroller


text:
Add skip_files entry to app.yaml

This is a temporary work-around for a bug in the Cloud SDK [1], where the
node_modules directory is uploaded. Until this bug is fixed, this bug will
ensure that the 1-hello-world example deploys successfully.
Due to the bug in question, the node_modules directory was being uploaded. This
causes issues with the Docker build on Windows, and causes increased build times
in general.
[1] https://code.google.com/p/google-cloud-sdk/issues/detail?id=210

I have similar PRs for all of the existing branches in this repo; let's hash out any issues here, and then I'll send the lot over.

I can handle merging it to other branches on my end (I have a nice script
for it). I'll review and merge this tomorrow AM.
On Wed, Aug 19, 2015, 6:20 PM Zack Newman notifications@github.com wrote:

I have similar PRs for all of the existing branches in this repo; let's
hash out any issues here, and then I'll send the lot over.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/nodejs-getting-started/pull/15#issuecomment-132843651
.

Merged, I'll patch it on to every other branch. Thanks.


text:
WIP - Error Reporting

Here is a possible Error Reporting sample, although I'm not sure our Client Libraries are ready for it. I am also debating using google/cloud-logging instead, since this can accomplish the same task in a more user friendly way.

After looking into it, the integration with Logging is quite minimal, and seems to be very hackish. The error message must be prefixed with PHP Warning:  and it MUST be an exception to string, e.g.:
$exceptionToString = (string) (new Exception('here is my message');
$logMessage = sprintf('PHP Warning: %s', $exceptionToString);

There is also no way to log additional context, such as the user, and there are other restrictions such as a requirement for module and version. Because these rules don't really make sense in many error reporting cases, having a dedicated error reporting sample will be a good investment.

@tmatsuo I think this is a great idea! We can follow Node.js's example
@dwsupplee is this something we can do by submitting PRs to ReportErrorsServiceClient?

@bshaffer Definitely! Those classes exist solely for us to be able to include utility code outside of the autogen GAPIC layer. We've done something similar with Spanner.

@dwsupplee Why are the stubs and credentials helpers being exposed? Those aren't the kinds of functions I had in mind.

Those are unique to Spanner as we needed to expose them in order to fulfill some product requirements. I was only pointing to them as an example of a place we have exposed added functionality before.

@dwsupplee I am thinking of helper functions like $logger->logException(). The logging and error reporting APIs are essentially identical, with the Error Reporting API being a derivative of the Logging API. I am not sure there's a really good reason to recommend using both, especially if we can build one into the other.

looks good with the exception of the linting issues

authors: bshaffer dwsupplee ryanmats

repo: GoogleCloudPlatform/php-docs-samples


text:
Add git to the base image.

This fixes #7.

LGTM

authors: NicholasGorskiGoogle dazuma

repo: GoogleCloudPlatform/ruby-docker


text:
Configuring the webhook manually

I am looking into what it will take for my organization to run this operator, and have same security concerns based on how the webhook is configured.
This application seems to want to manage its own webhook, which means giving it permissions to create, update, and delete mutation webhooks. This is a huge permission, because webhooks can be used to mutate any request or send any request to an external host.
I would really like to be able to enable the webhook functionality, but configure the resources for the webhook myself. This way, there is no possibility of the spark-operator service account creating unexpected webhook configurations.
Is this type of configuration possible? Based on the documentation, it seems like there is only a single flag to enable the webhook functionality and the webhook management functionality.

So basically what you would like to see is a way to plugin your own CA bundle in the MutatingWebhookConfiguration?

Perhaps. Truthfully I'm not really sure what the spark-operator does with regards to managing the webhook. If it's all about generating certs, then yes, plugging in my own CA bundle seems sufficient.
This would probably only require mounting a key and cert, then passing some flags to point to them, correct?


text:
enhancement: bump Google Cloud DLP from 1.0.0 to 3.6.2

Fixes #291

Bump Google Cloud DLP from version 1.0.0 to 3.6.2

Could you also please provide evidence of testing such as affirmation / screenshots / outputs that this version of DLP and pipeline working as expected? I don't believe our testing performs any de-id operation or pipeline (aka "workload") validation yet.  For instance, a comment with "I ran the xyz example and confirmed that data was de-id and re-id as expected" helps.  The goal isn't to create added work or to be detailed, unless you have info handy.
Another option to consider (for a future PR?) is to devise a test using the golang framework that mimics what our pipeline would does with DLP - mainly focus in on DLP crypto ops + template API request we use rather than e2e.  However, confirm with the team since that might cause our automated tests to take too long to be viable for our needs.

Could you also please provide evidence of testing such as affirmation / screenshots / outputs that this version of DLP and pipeline working as expected? I don't believe our testing performs any de-id operation or pipeline (aka "workload") validation yet. For instance, a comment with "I ran the xyz example and confirmed that data was de-id and re-id as expected" helps. The goal isn't to create added work or to be detailed, unless you have info handy.
Another option to consider (for a future PR?) is to devise a test using the golang framework that mimics what our pipeline would does with DLP - mainly focus in on DLP crypto ops + template API request we use rather than e2e. However, confirm with the team since that might cause our automated tests to take too long to be viable for our needs.

I tested for bigquery and pubsub and it's working fine. I was able to see in bigquery that the date was de-id and re-id as expected.
Follow some examples:
Confidential data:
{
  "city": "CANADA",
  "ein": "266641110",
  "ico": "% FOUR SEASONS",
  "income_amt": "57725551",
  "name": "VEBA INC VEBA TR",
  "revenue_amt": "57725551",
  "state": "None",
  "street": "TORONTO ONTARIO M3C 2K8"
}

Non-confidential data:
{
  "ein": "AWWdXDxOKxJ005BZbyGqGaNZalWC0BrRh2M=",
  "name": "AdOdV6RvyIyjwD9cCvexrdGzc6\/1bERiMGckA6QY+6K0",
  "ico": "% FOUR SEASONS",
  "street": "ASnm0YirdAN6ivgs5e2zKVCWOPljMaHCaxGz9xpEeI+4ASlG\/TmEvQ==",
  "city": "CANADA",
  "state": "Zucy",
  "income_amt": 57725551,
  "revenue_amt": 57725551
 }

Pubsub:
{
  "book": "Paradise Lost",
  "author": "lLvwB-3R9S9"
 }

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

De-id

Re-id

/gcbrun

authors: Samir-Cit amandakarina erlanderlo


text:
Added third party extension for packaging type "bundle"

I have added a link to an extension to create images for the packaging type "bundle". See jib issue #2562

Cool! Thanks for adding the link. Could you follow the CLA bot instructions above so that we can merge this?

Never mind. I added it in #58. Thanks for letting us know!

authors: chanseokoh fhossfel

repo: GoogleContainerTools/jib-extensions


text:
extraDirectory doesn't work with symbolic links as either destination or source

Description of the issue:
I have a maven project structure and have used the default jib location of extraDirectory.
src/main/jib/
Added my desired file i.e. 'server.xml' that needed to be placed under '/config' within the base image.
Thus, the structure now looked like this: (As jib requires recreating the structure under 'jib' directory)
src/main/jib/config/server.xml
The destination directory '/config' is actually a symbolic link in the base image.
After jib creates the image, on inspecting it can be seen that the symbolic link has now got replaced with an actual directory. Which breaks the build for me.
Expected behavior:
Symbolic link directories are typical in Java EE server images where these links are provided for deployment or configuration file placement.
Here the 'config' directory is the case for openliberty server.
Would expect this structure to be preserved if possible. Or provide some means of achieving the goal of putting files under images which use a symbolic link as a destination folder.
Environment:
Maven 3.5
Java 8
OS - MacOS
jib-maven-plugin Configuration:
<plugin>
                <groupId>com.google.cloud.tools</groupId>
                <artifactId>jib-maven-plugin</artifactId>
                <version>1.0.2</version>
                <configuration>
                    <from>
                        <image>openliberty/open-liberty:javaee8-java8-openj9</image>
                    </from>
                    <to>
                        <image>demo-project:1.0</image>
                    </to>
                    <container>
                        <appRoot>/apps/</appRoot>
                    </container>
                </configuration>
            </plugin>

Additional Information:
I inspected the image by logging into it with bash (running container). And I can see that the symbolic link 'config' within the server, now got changed to an actual directory.
Let me know if you need more details? This actually should be easily reproducible without requiring any Java or server technology, it's just a matter of how JIB copies the structure on the base image.

Hey @prashantpro. Thanks for bringing this up.
The workaround for this is to just directly reference the target that the link is referencing. I image that would be annoying if you're swapping servers regularly but might be acceptable for a simple case.
We currently have this low priority on our schedule, and given how jib works might consider not solving this. However if we get enough attention we can take another look. So please thumbs up this issue if it is seriously affecting you.

Low priority is fine, I don't think this is a deal breaker.
And yes, that workaround suggested is what I had ended up doing to move ahead.
I brought this up as an issue in case it was something simple to solve that the team could have closed.
The ugliness (opinionated) of the issue is that I need to create multiple directories.
Example of what I needed to do to solve this case:
/src/main/jib/opt/ol/wlp/usr/servers/defaultServer/
Here jib will correctly copy the desired configuration file to destination directory.
Thanks.

I'm going to re-open this as there's a workaround but not a solution.  If others encounter this issue, please describe your situation here.

It took me a while to check it, that jib replaces the symbolic link. A hint at the section could be helpful.

I tried to inject busybox into another base image.  But I could not create symbolic links for busybox aliases.
I wonder if we can have similar features to the ones in Bazel rules_docker.
rules_docker, which has a similar build mechanism, provides two interesting attributes:

tars: this attribute allows users to extract tar archives into the image layer.  It looks to be feasible in Jib to inject given tar archives as extra layers of the target image.
symlinks: this attribute specifies symbolic links to be created in the layer.

So there are two sides of the issue:

source symlinks (creating symlinks in an image): as suggested in https://github.com/GoogleContainerTools/jib/issues/1576#issuecomment-503810403 and supported in Bazel rules_docker, it sounds like a good idea to support this.
destination symlinks (following symlinks in an base image when copying files from <extraDirectories>): this is tough to support. We may need to list file contents of base image layers, statically analyze symlinks, and put files in correct destination directories.

I have the similar case: extraDirectories with symlinked file in them - C++ binaries, which I have to run with my Java application. But JIB just put the copy of the file instead symlink. This increases the size of image significantly.

I have to copy Python binaries. I have run the script from my Java application. Can somebody help if that can be done? If I am copying them it's failing with an error. couldn't follow symbolic link

authors: NitinSharma1991 briandealwis chanseokoh loosebazooka meier297 prashantpro putsev yugui

repo: GoogleContainerTools/jib


text:
Reconsider " If this is a bug, please file an issue at https://github.com/GoogleContainerTools/jib/issues/new"

In about six files. Most cases seem unlikely to be bugs.

Thanks, that is a good point. The word "bug" can be misleading because it may not always be the case that something is broken. Perhaps we can rephrase it to "If you need more assistance with this, please file an issue ..."

I'm not sure I even want to go that far. Given current support for jib, I'd prefer not to create extra issues in the repo and an expectation of unpaid support. I'm happy to receive genuine bugs here, but I'd prefer to leave it at that.

Plus stack overflow is a better channel for general questions than Github.

Yeah, time to rephrase/remove them. They were put in the old days where we were not GA and a lot of things were unsupported and unknown.

Hey, I'd like to take a stab at this :)

Thanks, You can send the review to me if you like. CLA will be required. Google practices TDD so be sure to write or modify tests first before changing the model code.

@elharo  I've just submitted a PR: #3294
Feel free to take a look in your free time
Thanks!

authors: JacekDuszenko chanseokoh elharo mpeddada1


text:
extraDirectories setting is not honored for snapshot jars

Environment:

Jib version: 3.3.1
Build tool: Maven
OS: centos

Description of the issue:
We have extraDirectories in pom.xml to make sure all jar files in  opt/product/libs are packaged into a single layer. But we found that the SNAPSHOT jars in opt/product/libs are extracted to a separate layer.
We know that jib build the SNAPSHOT jars into a separate layers by default, but when we also add the extraDirectories, the files in extraDirectories should not be move to the separate layer.
BTW, we found that when jar files in lib folder are builded into 2 different layers,  the application shows significant performance downgrade...

jib-maven-plugin Configuration:
<extraDirectories>
        <paths>
              <path>
                    <from>target/libs</from>
                    <into>/opt/product/libs</into>
             </path>
           </paths>
 </extraDirectories>

Log output:
Additional Information:

Hi @acappella2017, if you want fine-grained layer control, try Jib Layer-Filter Extension.


text:
report a misleading "401 Unauthorized"

Description of the issue:
report a "401 Unauthorized", but point to 'private-docker.changhongedu.cn/product-upgrade'
Expected behavior:
com.google.cloud.tools.jib.registry.RegistryUnauthorizedException: Unauthorized for private-docker.changhongedu.cn/product-upgrade
this line should be
com.google.cloud.tools.jib.registry.RegistryUnauthorizedException: Unauthorized for hub.c.163.com/azul/zulu-openjdk:8
Environment:
windows 10
maven 3.5.4
jib-maven-plugin 0.9.10
jib-maven-plugin Configuration:
<from>
  <image>hub.c.163.com/azul/zulu-openjdk:8</image>
</from>
<to>
  <image>private-docker.changhongedu.cn/product-upgrade</image>
</to>

Log output:

[DEBUG] TIMING  Building and pushing image
[DEBUG] RUNNING Building and pushing image
[INFO] Retrieving registry credentials for private-docker.changhongedu.cn...
[DEBUG] TIMING  Retrieving registry credentials for private-docker.changhongedu.cn
[DEBUG] RUNNING Retrieving registry credentials for private-docker.changhongedu.cn
[INFO] Getting base image hub.c.163.com/azul/zulu-openjdk:8...
[DEBUG] TIMING  Building application layers
[DEBUG] TIMING  Pulling base image manifest
[DEBUG] Using Maven settings for private-docker.changhongedu.cn
[DEBUG] RUNNING Pulling base image manifest
[DEBUG] RUNNING Building application layers
[DEBUG] TIMED   Retrieving registry credentials for private-docker.changhongedu.cn : 22.613 ms
[INFO] Building classes layer...
[DEBUG] TIMED   Building application layers : 21.77 ms
[INFO] Building resources layer...
[INFO] Building snapshot dependencies layer...
[INFO] Building dependencies layer...
[DEBUG] TIMING  Building snapshot dependencies layer
[DEBUG] TIMING  Building resources layer
[DEBUG] Building application layers : 21.77 ms
[DEBUG] TIMING  Building classes layer
[DEBUG] RUNNING Building resources layer
[DEBUG] RUNNING Building snapshot dependencies layer
[DEBUG] TIMING  Building dependencies layer
[DEBUG] TIMING  Setting up to push layers
[DEBUG] Retrieving registry credentials for private-docker.changhongedu.cn : 22.613 ms
[DEBUG] RUNNING Building classes layer
[DEBUG] TIMING  Authenticating with push to private-docker.changhongedu.cn
[DEBUG] RUNNING Setting up to push layers
[DEBUG] RUNNING Building dependencies layer
[DEBUG] TIMED   Setting up to push layers : 20.982 ms
[DEBUG] RUNNING Authenticating with push to private-docker.changhongedu.cn
[DEBUG] Setting up to push layers : 20.982 ms
[DEBUG] Building resources layer built sha256:788b04502b429b3ef038c576e7d3b5ae90a6e4e011d3a89509035e5b159e59bc
[DEBUG] TIMED   Building resources layer : 677.315 ms
[DEBUG] Building resources layer : 677.315 ms
[DEBUG] Building classes layer built sha256:a944f4f3c341748fd27b9f5c0533e8e87492afc49f6ca4c92a82584799a3080d
[DEBUG] TIMED   Building classes layer : 702.675 ms
[DEBUG] Building classes layer : 702.675 ms
[DEBUG] Building snapshot dependencies layer built sha256:7d07441a36bfd1fcae53adeea9aeb282d603b12d9ce18d0e4c54b49476979565
[DEBUG] TIMED   Building snapshot dependencies layer : 717.751 ms
[DEBUG] Building snapshot dependencies layer : 717.751 ms
[DEBUG] TIMED   Authenticating with push to private-docker.changhongedu.cn : 1106.76 ms
[DEBUG] Authenticating with push to private-docker.changhongedu.cn : 1106.76 ms
[DEBUG] TIMING  Pushing BLOB digest: sha256:a944f4f3c341748fd27b9f5c0533e8e87492afc49f6ca4c92a82584799a3080d, size: 6284
[DEBUG] TIMING  Pushing BLOB digest: sha256:788b04502b429b3ef038c576e7d3b5ae90a6e4e011d3a89509035e5b159e59bc, size: 1159
[DEBUG] TIMING  Pushing BLOB digest: sha256:7d07441a36bfd1fcae53adeea9aeb282d603b12d9ce18d0e4c54b49476979565, size: 288136
[DEBUG] RUNNING Pushing BLOB digest: sha256:788b04502b429b3ef038c576e7d3b5ae90a6e4e011d3a89509035e5b159e59bc, size: 1159
[DEBUG] RUNNING Pushing BLOB digest: sha256:a944f4f3c341748fd27b9f5c0533e8e87492afc49f6ca4c92a82584799a3080d, size: 6284
[DEBUG] RUNNING Pushing BLOB digest: sha256:7d07441a36bfd1fcae53adeea9aeb282d603b12d9ce18d0e4c54b49476979565, size: 288136
[INFO] The base image requires auth. Trying again for hub.c.163.com/azul/zulu-openjdk:8...
[INFO] Retrieving registry credentials for hub.c.163.com...
[DEBUG] TIMING  Retrieving registry credentials for hub.c.163.com
[DEBUG] RUNNING Retrieving registry credentials for hub.c.163.com
[DEBUG] Using Maven settings for hub.c.163.com
[DEBUG] TIMED   Retrieving registry credentials for hub.c.163.com : 5.562 ms
[DEBUG] Retrieving registry credentials for hub.c.163.com : 5.562 ms
[DEBUG] BLOB : digest: sha256:a944f4f3c341748fd27b9f5c0533e8e87492afc49f6ca4c92a82584799a3080d, size: 6284 already exists on registry
[DEBUG] BLOB : digest: sha256:7d07441a36bfd1fcae53adeea9aeb282d603b12d9ce18d0e4c54b49476979565, size: 288136 already exists on registry
[DEBUG] BLOB : digest: sha256:788b04502b429b3ef038c576e7d3b5ae90a6e4e011d3a89509035e5b159e59bc, size: 1159 already exists on registry
[DEBUG] TIMED   Pushing BLOB digest: sha256:7d07441a36bfd1fcae53adeea9aeb282d603b12d9ce18d0e4c54b49476979565, size: 288136 : 78.789 ms
[DEBUG] TIMED   Pushing BLOB digest: sha256:a944f4f3c341748fd27b9f5c0533e8e87492afc49f6ca4c92a82584799a3080d, size: 6284 : 74.492 ms
[DEBUG] Pushing BLOB digest: sha256:7d07441a36bfd1fcae53adeea9aeb282d603b12d9ce18d0e4c54b49476979565, size: 288136 : 78.789 ms
[DEBUG] TIMED   Pushing BLOB digest: sha256:788b04502b429b3ef038c576e7d3b5ae90a6e4e011d3a89509035e5b159e59bc, size: 1159 : 82.856 ms
[DEBUG] Pushing BLOB digest: sha256:a944f4f3c341748fd27b9f5c0533e8e87492afc49f6ca4c92a82584799a3080d, size: 6284 : 74.492 ms
[DEBUG] Pushing BLOB digest: sha256:788b04502b429b3ef038c576e7d3b5ae90a6e4e011d3a89509035e5b159e59bc, size: 1159 : 82.856 ms
[DEBUG] TIMED   Pulling base image manifest : 2045.515 ms
[DEBUG] Pulling base image manifest : 2045.515 ms
[DEBUG] TIMED   Building and pushing image : 2307.967 ms
[DEBUG] Building and pushing image : 2307.967 ms
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.041 s
[INFO] Finished at: 2018-09-06T09:59:16+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:0.9.10:build (default-cli) on project product-upgrade-server: Build image failed, perhaps you should make sure your credentials for 'private-docker.changhongedu.cn' are set up correctly: Unauthorized for private-docker.changhongedu.cn/pr
oduct-upgrade: 401 Unauthorized
[ERROR] Auth failed.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.google.cloud.tools:jib-maven-plugin:0.9.10:build (default-cli) on project product-upgrade-server: Build image failed, perhaps you should make sure your credentials for 'private-docker.changhongedu.cn' are set up correctly
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Build image failed, perhaps you should make sure your credentials for 'private-docker.changhongedu.cn' are set up correctly
    at com.google.cloud.tools.jib.maven.BuildImageMojo.execute (BuildImageMojo.java:140)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: com.google.cloud.tools.jib.registry.RegistryUnauthorizedException: Unauthorized for private-docker.changhongedu.cn/product-upgrade
    at com.google.cloud.tools.jib.plugins.common.BuildStepsRunner.build (BuildStepsRunner.java:206)
    at com.google.cloud.tools.jib.maven.BuildImageMojo.execute (BuildImageMojo.java:136)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: com.google.api.client.http.HttpResponseException: 401 Unauthorized
Auth failed.

    at com.google.api.client.http.HttpRequest.execute (HttpRequest.java:1070)
    at com.google.cloud.tools.jib.http.Connection.send (Connection.java:161)
    at com.google.cloud.tools.jib.http.Connection.get (Connection.java:116)
    at com.google.cloud.tools.jib.registry.RegistryAuthenticator.authenticate (RegistryAuthenticator.java:253)
    at com.google.cloud.tools.jib.registry.RegistryAuthenticator.authenticatePull (RegistryAuthenticator.java:216)
    at com.google.cloud.tools.jib.builder.steps.PullBaseImageStep.call (PullBaseImageStep.java:162)
    at com.google.cloud.tools.jib.builder.steps.PullBaseImageStep.call (PullBaseImageStep.java:57)
    at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly (TrustedListenableFutureTask.java:127)
    at com.google.common.util.concurrent.InterruptibleTask.run (InterruptibleTask.java:57)
    at com.google.common.util.concurrent.TrustedListenableFutureTask.run (TrustedListenableFutureTask.java:80)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Additional Information:
The authorization for 'private-docker.changhongedu.cn' is correct.
'hub.c.163.com' is just a mirror for 'hub.docker.com' and the authorization of 'hub.docker.com' can not be used to 'hub.c.163.com' , so the jib:build report a "401 Unauthorized" message, but the stack trace message give me a misleading to 'private-docker.changhongedu.cn', it should be 'Unauthorized for hub.c.163.com/azul/zulu-openjdk:8', right?

Hi @JaynLau — jib does a lot of things in parallel, and BuildStepsRunner#build() is the join and reports exceptions that may have occurred, so the error messages don't always seem to tie to what's being reported.x
If you run with -DjibSerialize=true, jib will run each part of its pipeline in sequence and what you see should make more sense.  Also see this FAQ item for obtaining a trace of the HTTP traffic to see what's being sent and received.

thanks a lot.

I have to take this back though — looking at the actual exception throwing code in BuildStepsRunner#build(), we are always referencing the target image!  Urp!

Yes, it is! This problem made me to take a whole day to find out my real error.

authors: JaynLau briandealwis


text:
Adding testing for BuildManifestListOrSingleManifestStep

This PR adds testing for BuildManifestListOrSingleManifestStep

This PR will closed without merging to master : We have made a design decision to merge createManifestListTest into createManifestList then in the end createManifestList will be merged into master


text:
Apply allowInsecureRegistries to RegistryAuthenticator too

Tests are completely broken. This is for early discussion. Please review the general approach, not details.
This is about the second part in #720, the issue that allowInsecureRegistries has no effect on RegistryAuthenticator. My approach here is

Refactor the allowInsecureRegistries logic into a lower-level utility-like class, EndpoinCaller.
Both RegistryEndpointCaller and RegistryAuthenticator uses EndpointCaller for handling allowInsecureRegistries.
Rename RegistryException to EndpointException, because it's common that the auth server is different from a registry server.

But at the same time, I think it would be pretty rare that an auth server is insecure. https://github.com/GoogleContainerTools/jib/issues/720#issuecomment-410271972 may be a very special case where SSL validation fails unpredictably possibly due to some issue in the customer's local environment.
So, now I think we don't really need to try to apply allowInsecureRegistries to RegistryAuthenticator at least for now. If we find actual use-cases, we can consider it then.

Per https://github.com/GoogleContainerTools/jib/issues/720#issuecomment-410376321, I'm closing this. If we later find a case where the auth server is required and not secure, we can revisit the branch. (You can always restore a closed PR.) However, as I said in the comment, I think it would be extremely rare that an insecure registry requires talking to an auth server (even if the server is self).


text:
What do you use to run code?

Do you run the code in your private server or do you use some other website through an API that runs the code and sends you the result?

I have hosted this on openshift online. You can run it anywhere with a python environment . The python-telegram-bot library takes care of getting the data from telegram's server to you.

for the /compiler command I use hackerranks api. And for /upcoming , /ongoing I use clists api

My main question is regarding the /compile command since Hackerrank says that they've discontinued the API.

Yeah It does say so on the website but the api is still working.
On Wed, 5 Sep 2018, 00:40 Somnath Rakshit, notifications@github.com wrote:

My main question is regarding the /compile command since Hackerrank says
https://www.hackerrank.com/api/docs that they've discontinued the API.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Gotham13121997/superCodingBot/issues/3#issuecomment-418483922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZNjHBUCVVu7ZLHR5c9Ujop0CQ8PPNasks5uXtA1gaJpZM4WYZQ6
.

You can use the Hackerearth API maybe. Overall, a nice project.

Yeah I was thinking of shifting to it when Hackerrank api stops working.
But it still works apparently.
On Wed, 5 Sep 2018, 00:45 Somnath Rakshit, notifications@github.com wrote:

You can use the Hackerearth API
https://www.hackerearth.com/docs/wiki/developers/v3/ maybe. Overall, a
nice project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Gotham13121997/superCodingBot/issues/3#issuecomment-418485552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZNjHPBUExL3o8fIhlLQkS7pp08K44AFks5uXtFrgaJpZM4WYZQ6
.

They even have a Python SDK for it to make things easy.

license: mit


text:
Improve logging in Accumulo table creation

The method createTable in the TableUtils class in the accumulo-store package should log that it is creating a table, and include the table name. The current logging only specifies the iterators that are being added and does not specify the name of the table. The TABLE_FILE_REPLICATION property should also be logged.

Merged into develop.


text:
Create Product model

Implement Product model via Sequelize:

Must have title, description, price, inventory quantity, image URL(s), and availability.
Must belong to at least one category
If there is no photo, there must be a placeholder photo used

Closed by https://github.com/Graceful-Shoppers/grace-shopper/pull/13

authors: ralmidani thekyriarchy

repo: Graceful-Shoppers/grace-shopper

license: MIT


text:
Compile Flex task is up-to-date after build script changes

Steps to reproduce:

compile your app. for example run gradlew installMobile
Make a change to the build script
compile the app again. It will not recompile even though the build script change can lead to a different binary.

Same thing can happen if you define command line arguments, that change compile flags. for example:
I run gradlew installMobile -isDebug
the build script:
...
boolean isDebug = hasProperty('isDebug') ? true : false;

additionalCompilerOptions = [
    "-define+=CONFIG::DEBUG,$isDebug"
]
...

By default, the compileFlex task does not declare the properties that affect compilation as inputs to the task (only the contents of the src directory are treated as inputs). While there might be some debate that it should, you can work around it by explicitly declaring it yourself via:
compileFlex.inputs.property('additionalCompilerOptions', additionalCompilerOptions)

I do this myself for the packageMobile task where I have a command line argument that can affect the airMobile.target property. I use the convention above to ensure that any change to the property causes the task to rerun if it changes.
Kindly give that a try and let us know how it goes.

thanks it works!

authors: matyasatfp wenslayer

repo: GradleFx/GradleFx


text:
fixed skip_if_private and skip_if_public check

Description
skip_if_public and skip_if_private were wrong.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

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

[ X ] Test A
[ X ] Test B

Test Configuration:

Device Model or Emulator: Samsung S20
Android Verison: 14
Instagram Version: Recommended

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have tested my code in every way I can think of to prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules

Wait, something seems off. I want the bot to only interact to private accounts, but it skips them no matter what I make the filters. I will test more and update if necessary.

Fixed it and it works fine now.

hello, can you merge to develop and not master? :)

repo: GramAddict/bot


text:
gProfiler 1.3.0

After https://github.com/Granulate/gprofiler/pull/403

Now libunwind is broken? https://github.com/Granulate/gprofiler/runs/7340122478?check_suite_focus=true

authors: Jongy michelhe

repo: Granulate/gprofiler


text:
Implement select tool tests and modify test utilities

This PR implements some tests for the select tool, particularly to test for the correct behavior when using the undo/redo functionalities.
This PR additionally improves the testing utilities:

The move_mouse function now accepts an EditorMouseState as input to avoid discarding the previous mouse state as that may result in unintended behavior.
Adds test utilities for the dispatcher.

Part of #595

I'm going to close this for now since it's gone stale. Please feel free to reopen it at any time if you pick it up again, I'd be more than delighted to review it or offer assistance in getting it ready to merge.

Alright, thank you. I apologize for not being able to complete this right now, but I am excited to work on this again when I am able to.

authors: Keavon RahulHi

repo: GraphiteEditor/Graphite


text:
Migrate to Standard CMake format

Migrate the CMake configuration to use the recomended CMake
configuration, allowing us to be easily built against by other CMake
projects.

Coverage decreased (-93.009%) to 0.0% when pulling 58c85089bd071b7fd5fe74ea1f938a04e1d9f7df on CMake into ba8b6ad430ef37ef1df246198e953ac19b92ce17 on master.

authors: Grauniad coveralls

repo: Grauniad/FixedJSONParserCPP


text:
Stay in message section after replying to a message, #89

References issue #89, and allows user to stay in the message section after replying to a message instead of going back to the all messages section.

Great! Thank you very much!

repo: GravityProject/gravity


text:
🛑 Server Gaming is down

In fe5e6a4, Server Gaming (https://game.greathost.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Server Gaming is back up in c8405b3 after 8 minutes.

repo: GreathostRo/upptime


text:
Option to only show key value (not name) in breadcrumb for collections

Is there an option to not show the key name (only the value) in breadcrumbs for collections?
This is an example of what I am seeing:
Tables[TableName:Commission].Fields[DestinationField:AdviserCode].Enabled

But I would prefer to see it as follows:
Tables[Commission].Fields[AdviserCode].Enabled

An option could be as follows:
logic.Config.ShowCollectionKeyName = false;

For multi-key collections, I guess you could separate the values with a comma or some other separator.
Maybe even have a separator option, such as:
logic.Config.CollectionKeySeparator = '|'; // Default = ','

Example results: Tables[MyTable,true] or Tables[MyTable|true]

That feature does not exist.  If you would like to implement I can approve the pull request.

Merged

Sweet. When should I expect the new package?

There is another PR that is not compiling.  I am waiting on another person to fix that.

authors: GregFinzer gordon-matt

repo: GregFinzer/Compare-Net-Objects

license: MS-PL


text:
Hard failure when soft expected

Problem
I have an expr like:
const m = p1.pipe(maybe(), then(p2));
m.parse(onlySatisfiesP2); // Hard failure from p1, when Success expected

Reproduction

minimal demo: https://github.com/cdaringe/email-parser/blob/main/issue.ts#L56
clone and npm install (or pnpm install, as i'm using)
run the module: node -r ts-node/register issue.ts or bun issue.ts

Discussion
It seems in some circumstances Soft is promoted to Hard, but it's not clear when. Further, I expected a soft failure above, wanted the maybe() to catch, then successfully parse using the then(expr). I've tried debugging, and it's a bit wonky to debug, but I see the promotion happening in the Then instance if the Soft failure isn't the first failure. I'm trying to write an email parser, with many optional, leading expressions in the grammar. Any tips would be welcomed. Much appreciated!

// node_modules/.pnpm/parjs@0.16.1/node_modules/parjs/dist/lib/internal/combinators/then.js
                    else if (ps.isSoft) {
                        ps.kind = result_1.ResultKind.HardFail;
                        // if a i > 0 parser failed softly, this is a hard fail for us.
                        // also, propagate the internal expectation.
                        return;
                    }

This is the block. I'm not grokking this block promotes a soft failure to a hard failure. This block prevents my maybe() combinator. Any insight here?

Hi!
I think you are correct that the then combinator is upgrading the soft failure to a hard failure here:
https://github.com/cdaringe/email-parser/blob/main/issue.ts#L41
This is also described here in the readme in more detail https://github.com/GregRos/parjs/#-hard-failure
However, I think fixing your issue is tricky due to a few things:

the parsers you have built parse leading whitespace
onWSP_CRLF_mWSP is not able to differentiate between these two cases:

leading whitespace + CRLF, followed by 1*WSP
only 1*WSP

Now, I'll try to offer some improvements:

You have 2 parsers that both start parsing whitespace. When a parser starts consuming input, it is assumed to be valid (this is exactly the case described in the readme). It may work better for you to parse trailing whitespace instead. This way you can write parsers that have the same names as the tokens in your grammar: so instead of long names such as (example) CRLF_mWSP you can have a parser called CRLF which parses CRLF + trailing whitespace. As for the implementation, you can either bake the trailing whitespace parsing into each parser manually or have a function that returns a parser such as this (untested):

/** Parses the given parser followed by whitespace */
export function token<T>(parjser: p.Parjser<T>): p.Parjser<T> {
  return parjser
    .pipe(
      c.thenq(
        whitespace.pipe(
          c.many(),
          c.must(
            (ws) =>
              ws.length >= 1 || { reason: "at least 1 whitespace character" },
          ),
        ),
      ),
    )
    .expects(`The given token followed by whitespace`);
}

export const crlf = token(p.string("\r\n")).expects("crlf");

I think you can simplify your atLeast implementation to this

export const atLeast = (n: number, t: p.Parjser<string>) =>
  t.pipe(c.exactly<string>(n), flatString);

In general, it may be helpful to add .expects("description of what this parser expects") calls to your parsers. These will be helpful when looking at the stack traces.
In your tests you can have an assertion function that shows the stack traces when things fail. We don't have a good example of this yet so I just built this for you, you can try it out if you want:

/** An assertion that shows a nice stacktrace in case the parsing fails */
function assertParses<T>(
  result: ParjsResult<T>,
  expectedValue: T,
): asserts result is ParjsResult<T> {
  if (!result.isOk) {
    const error = result as ParjsFailure;
    throw new Error(
      `Expected success, got failure: ${error}\n${JSON.stringify(
        error,
        null,
        2,
      )}}`,
    );
  }

  // depending on your testing and assertion libraries, assert a condition
  expect(result.value).toEqual(expectedValue);
}

Some of your token parsers can be simplified by using built in parsers. Here is an example:

export const SP = p.space().expects("SP");
// instead of
export const SP = p
  .charCodeWhere((x) => (x === 0x20 ? true : failSoft("SP")));

I think your atLeast function may have a bug. Try this (untested):

export const atLeast = (n: number, t: p.Parjser<string>) =>
  t.pipe(c.exactly<string>(n), flatString);

Thanks for these great suggestions and advice! I will be picking up my project again shortly and will revisit with your guidance

Closing this as it's been inactive for some weeks now. Feel free to reopen if needed.

authors: barona-mika-vilpas cdaringe

repo: GregRos/parjs


text:
refactor: trying to replace TableGlobalValue, part 1

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Trying to replace TableGlobalValue, part 1. Not introducing incompatible change (for now). Using the new interfaces but return old values.
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)
#1728

@fengjiachun PTAL

repo: GreptimeTeam/greptimedb


text:
feat: implement param parsing of SubmitRegionMigrationTaskHandler

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Implement param parsing of SubmitRegionMigrationTaskHandler
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.
[x]  This PR does not require documentation updates.

Refer to a related PR or issue link (optional)
#2700

@MichaelScofield PTAL


text:
fix: region logical regions after catching up

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Register metric logical regions after invoking catchup
Checklist

[ ] I have written the necessary rustdoc comments.
[x] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

@WenyXu Please describe the PR in detail. What issue does it address? What happened before this patch etc.


text:
Jjgriff93/199 seperate out bootstrap

Resolves #ISSUE
What is being addressed
Describe the current behavior you are modifying. Please also remember to update any impacted documentation.
How is this addressed

Describe the changes made, and if appropriate, why they are addressed this way
Note any pending work (with links to the issues that will address them)
Update documentation

Has the CIS document been consulted / updated?

Are you adding new resources, or modifying existing ones?
Have settings been set in line with the CIS recommendations?

/test

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/Griff-Labs/FlowEHR/actions/runs/4628951026 (with refid 647cba26)
(in response to this comment from @jjgriff93)

/test

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/Griff-Labs/FlowEHR/actions/runs/4629020209 (with refid 647cba26)
(in response to this comment from @jjgriff93)

/test

/test

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/Griff-Labs/FlowEHR/actions/runs/4629590121 (with refid 647cba26)
(in response to this comment from @jjgriff93)

repo: Griff-Labs/FlowEHR


text:
What on earth does this mean. (Running python 3.7.0)

Traceback (most recent call last):
File "C:\Users\susan\Desktop\Liam'sFolder\Coding things\COZMO\tools\Cozmo-Explorer-Tool-master\explorer_tool.py", line 28, in
from flask_socketio import SocketIO, emit, disconnect
File "C:\Users\susan\AppData\Roaming\Python\Python37\site-packages\flask_socketio_init_.py", line 8, in
from socketio import socketio_manage
File "C:\Users\susan\AppData\Roaming\Python\Python37\site-packages\socketio_init_.py", line 3, in
from .client import Client
File "C:\Users\susan\AppData\Roaming\Python\Python37\site-packages\socketio\client.py", line 5, in
import engineio
File "C:\Users\susan\AppData\Roaming\Python\Python37\site-packages\engineio_init_.py", line 8, in
from .asyncio_client import AsyncClient
File "C:\Users\susan\AppData\Roaming\Python\Python37\site-packages\engineio\asyncio_client.py", line 4, in
import aiohttp
File "C:\Users\susan\AppData\Local\Programs\Python\Python37-32\lib\site-packages\aiohttp_init_.py", line 10, in
from .protocol import *  # noqa
File "C:\Users\susan\AppData\Local\Programs\Python\Python37-32\lib\site-packages\aiohttp\protocol.py", line 18, in
from .helpers import reify
File "C:\Users\susan\AppData\Local\Programs\Python\Python37-32\lib\site-packages\aiohttp\helpers.py", line 25
ensure_future = asyncio.async
^
SyntaxError: invalid syntax

No idea. I miss the context in which you get this error message. You tried to run it as a python file with flask installed as mentioned in the readme file?
Please describe what you did and in what order to get to this error.
Also: I see aiohttp in your log, but that is not part of the requirements and not called when installed correctly.

Yes. Ran as a python file and as i stated 3.7. Installed flask, cozmo and the other requirements
Do i need to run it from cmd? I have discord and youtube dl moudules but I dont think they conflict
. Should I run it on 3.6
Thanks let me know

No, it should work fine with 3.7. You might explicitly try to run it with python3.7 explorer_tool.py and see what happens. I am no expert at this kind of debugging though. You might have better luck asking on the Anki forums.

It appears you have an old version of theaiohttp package, this issue should have been fixed since version 2.3.3 (17-Nov-2017).
Update the aiohttp package, pip install aiohttp --upgrade

authors: DrPickens GrinningHermit tgikal

repo: GrinningHermit/Cozmo-Explorer-Tool


text:
Dark theme

Providing a dark theme option would be nice, and could be done with a similar persistent method to margin expansion.

https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme

Dark theme would be so nice. I've just came here to suggest this myself :)

authors: Grinnz deadmarshal

repo: Grinnz/perldoc-browser


text:
Spell Heart Ripper from the SC

@dolio
This spell contains a modified spell_utils. I often need to check if a target has a certain mc_type, and I finally added the check to the spell_utils.

Is this still a WIP? It looks finished...

Is there a better way to handle the XP issue? Other than that the spell is pretty much done and I tested it a fair amount already.

Ah ok cool.
I think in temple+ you can add an arg to the "kill by effect" call that denotes who the attacker is, so you don't have to apply manual damage.

Ah ty for pointing this out to me. Fixed

Ah ty for pointing this out to me. Fixed

Yeah I added it for the Assassin :)
BTW there's a bunch of user bug reports on the Spell Compendium thread, can you look into it?

authors: DudeMcDude Sagenlicht

repo: GrognardsFromHell/TemplePlus


text:
Config to Disable Chaos + SCP win condition / Warhead Detonation = Chaos Win?

I want to change one of my servers to separate the shared win condition between Chaos and SCP, and make it so that if the Warhead goes off, Chaos automatically win. This way, each of the 3 teams has a shared objective:

MTF + Chaos: Evacuate Scientists + D-class
Chaos + SCPs: Fight against Foundation control
MTF + SCPs: Prevent Chaos from activating the nuke

I'm sure there would be some people who would want separate config variables for each of these, in case they don't want warheads to instantly win the game, or for a single SCP to drag out the game against a whole server of MTF.

ci_share_scp_win_condition (default: true)
ci_warhead_detonation_win_condition (default: false)

@Dankrushen Is there a repository or listing of plugins anywhere? I'd like to add my completed plugins there as well.
I see IEventDetonate in the Smod2 API, but I don't see any way to forcefully end the round (fire an event).
There's also IEventRoundEnd, but how can that prevent Chaos Insurgency and SCPs from having a shared victory condition?

We actually just have discord channels for plugins:

Its not great, hoping someone else would be brave enough to make a proper repo for plugins (and maybe a plugin management plugin)

We will enable events for someone to make this into a plugin

@Grover-c13 If you add an OnWinConditionMet that has an enum of the possible win conditions, with one enum being NO_WIN, with an out parameter specifying the new win condition, that should work.
The latter case seems to require firing events capability.
Anyway, I'll create the plugin for this if the events are in place.

Ive added OnCheckRoundEnd event, it has a new status enum which will give you what youre looking for.

Thanks laserman!


text:
[ag] tuple_view cvref correctness / consistency

[ag] tuple_view elements cvref-qualifiers correctness / consistency
Define what's the expected behavior here.
Questioning
What's semantically are the correct cvref-qualifiers for each elements of a view ?
As-is, csl::ag preserve const-correctness, but not necessary ref-correctness.

Example 1 : misleading ref-qualifier
struct S {
        const int & i;
};
static_assert(std::same_as<
    decltype(csl::ag::as_tuple_view(std::declval<S>())),
    std::tuple<const int &&> // OK const-correctness preserved,
                                             // but here the rvalue-reference is misleading, as it might denote a potential ownership
>);

Example 2 : misleading const-qualifier discard ?
struct S {
    int & i;
};
static_assert(std::same_as<
    decltype(csl::ag::as_tuple_view(std::declval<const S>())),
    std::tuple<int &&> // should be `int &` ? `const int &` ?
>);

Todo

[x] #66
[ ] #64
[ ] Fix the code according, considering any behavior delta as a bug
[ ] Update tests so they match the new behavior (if so)
[ ] Update examples
[ ] Update the documentation accordingly
[ ] Validate #51

preserve original type information while not making copies : https://godbolt.org/z/f9x3bMWYe

repo: GuillaumeDua/CppShelf


text:
Create a new pull request by comparing changes across two branches

PR Checklist
Before creating new PR, please take a look at checklist below to make sure that you've done everything that needs to be done before we can merge it.

[ ] read and followed the CONTRIBUTING.md guide.
[ ] built and tested the changes locally.
[ ] added/updated tests.
[ ] added/updated API documentation.
[ ] added/updated demos.

Codecov Report

Merging #226 (b9c9f8d) into development (1672917) will increase coverage by 1.14%.
The diff coverage is 94.70%.

@@               Coverage Diff               @@
##           development     #226      +/-   ##
===============================================
+ Coverage        75.82%   76.96%   +1.14%
===============================================
  Files              315      315
  Lines            10608    10701      +93
  Branches          2929     2988      +59
===============================================
+ Hits              8043     8236     +193
+ Misses            2564     2463     -101
- Partials             1        2       +1

Impacted Files
Coverage Δ

src/accordion/accordion-group.component.ts
100.00% <ø> (+6.66%)
:arrow_up:

src/alert/alert.module.ts
100.00% <ø> (ø)

src/carousel/carousel.component.html
100.00% <ø> (ø)

src/collapse/collapse.directive.ts
73.03% <0.00%> (ø)

src/datepicker/themes/bs/bs-datepicker-view.html
100.00% <ø> (ø)

...icker/themes/bs/bs-days-calendar-view.component.ts
21.53% <ø> (ø)

src/dropdown/bs-dropdown-container.component.ts
50.00% <0.00%> (-1.43%)
:arrow_down:

src/dropdown/bs-dropdown.module.ts
100.00% <ø> (ø)

src/modal/modal-container.component.ts
44.87% <0.00%> (+7.37%)
:arrow_up:

src/modal/modal-options.class.ts
100.00% <ø> (ø)

... and 69 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: GulajavaMinistudio codecov-commenter

repo: GulajavaMinistudio/ngx-bootstrap


text:
After

Create and implement after conception:
A1(
  A2(), A3()
).after(
  A4(
    A5(), A6()
  )
).call()

#53 Done

repo: Guseyn/cutie


text:
Non existent formkit, because cannot resolve and then when you put it into the component it fails

I wanted to say that from what I learned this seems a very good work. Although I cannot provide a proper starting configuration to make the plugin work. For some reason, it fails to resolve and then it doesn't setup the component.

yeah never mind. For else is facing this. In inertia there is a plugin that is passed so adding a plugin and defaultConfig doesn't work. But any other name does.
the example I found from StackOverflow
import { plugin as FKp, defaultConfig as FKdc } from "@formkit/vue";

So you made it work? can you share what the code for your config looks like so I can see if there is something that could be improved?

Yes.
on the main.js on a Laravel application.
// formkit
instead of
import { plugin, defaultConfig } from "@formkit/vue";
you do
import { plugin as FKp, defaultConfig as FKdc } from "@formkit/vue";
This is because of inertia when creates and setups the app, with
createInertiaApp({
   setup({ el, App, props, plugin }) {

   }
})

the plugin there could not be used as the package's name, therefore you need an alias for that.
For some reason this was happening also locally, don't know why. But if you register this globally it would be fine

authors: GustavoFenilli sibalonat

repo: GustavoFenilli/formkit-addon-inertia


text:
Add : Footer section on webpage

Adding footer section on webpage which include copyright logo and it's details

Adding footer section on webpage which include copyright logo and it's details

@yube01 before adding read carefully how to contribute

Adding footer section on webpage which include copyright logo and it's details

@yube01 go ahead

license: Unlicense


text:
STEPPER_VIRTUAL

Это для чего?
Как я понял для отладки и вывода в графики.

для дёрганья пинов драйвера не через бортовой IO, а например через сдвиговые регистры

repo: GyverLibs/GyverStepper


text:
Validierung / accuracy proof

Möglichkeiten...

Vergleich mit SBB Projekt / ggf. WSL Projekt
overall accuracy proof

Danke, ich verlinke mal mit dem Cloud-Issue, da wir das evtl. aufgreifen.

Danke, ich verlinke mal mit dem Cloud-Issue, da wir das evtl. aufgreifen.

authors: AlexErb Hannes-Ole

repo: HAFL-FWI/Digital-Forest-Monitoring


text:
⚠ SkipTheCommericals has degraded performance

In 97f1dc2, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 3910 ms

Resolved: SkipTheCommericals performance has improved in a799e05.

repo: HDVinnie/TrackerHub


text:
⚠ DesiTorrents has degraded performance

In 011884a, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 2551 ms

Resolved: DesiTorrents performance has improved in 7e96a8c.


text:
🛑 SkipTheCommericals is down

In 8efe5da, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in 108cde3.


text:
⚠ TorrentLeech has degraded performance

In 0ace85a, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 5680 ms

Resolved: TorrentLeech performance has improved in b00eeaf.


text:
⚠ TorrentLeech has degraded performance

In 424ad90, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 4196 ms

Resolved: TorrentLeech performance has improved in b0c2a7f after 6 minutes.


text:
🛑 Nebulance is down

In 70632c2, Nebulance ($NBL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nebulance is back up in 204324f after 1 day, 2 hours, 37 minutes.


text:
🛑 Redacted is down

In b25c940, Redacted ($RED) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Redacted is back up in 29df3c7 after 10 hours, 31 minutes.


text:
⚠ SceneTime has degraded performance

In 38c7c6f, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2096 ms

Resolved: SceneTime performance has improved in 3f0efd3 after 23 minutes.


text:
⚠ SceneTime has degraded performance

In 136f265, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2759 ms

Resolved: SceneTime performance has improved in e92fbf5 after 6 minutes.


text:
⚠ SceneTime has degraded performance

In 43d5837, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2377 ms

Resolved: SceneTime performance has improved in 1c6a073 after 7 minutes.


text:
⚠ Aither has degraded performance

In 3dc987b, Aither ($AIH) experienced degraded performance:

HTTP code: 200
Response time: 5490 ms

Resolved: Aither performance has improved in 4c2f405 after 12 minutes.


text:
🛑 SkipTheCommericals is down

In cab0bf7, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in b0c2bec.


text:
🛑 Telly is down

In 579dbc5, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 10b148c.


text:
🛑 Telly is down

In aa24d75, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 0baccd5.


text:
🛑 Telly is down

In f8e4787, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in e53c36a.


text:
Question about using OpenGraph on large-scale node classification datasets.

The data formats used in OpenGraph are "adj_-1.pkl", "adj_1.pkl", "mask_1.pkl", and in issue 4 you provided a script to convert the original data to these formats.
However, you load the entire dataset at once in the script, which is unacceptable for large-scale datasets like ogbn-*, which have nodes ranging from 2M to 100M.
I noticed that the largest dataset used in the paper is OGBL-collab, which has about 0.2M nodes, and I wonder if OpenGraph can be used for super large datasets, such as obgn-papers100M, which has about 100M nodes.

Thank you for bringing up this issue. I believe this problem is common to both foundation models and vanilla GNNs, so my suggestion would be to try graph sampling algorithms which can reduce computations by focusing on important subgraph structures.

repo: HKUDS/OpenGraph


text:
User Messages II

user messages (if any) appears correctly on top of the page, with updated wording.

To test, uncomment these lines in app.js:

https://github.com/HL7-DaVinci/dtr/blob/f41f4479f8e140dbd8a327797e8ac3d494c6b377/src/App.js#L14-L27
https://github.com/HL7-DaVinci/dtr/blob/f41f4479f8e140dbd8a327797e8ac3d494c6b377/src/App.js#L40-L44

Hello Howard, I'm getting a blank screen above when clicking the SMART App link in the card.

It worked after:

deleting node_modules
npm install

authors: hkong lpdecelles


text:
How to solve 'UnboundLocalError: local variable 'gray' referenced before assignment'

"fisheye/01.checkerboard/main.py"
line 40, in get_K_and_D
gray.shape[::-1],
UnboundLocalError: local variable 'gray' referenced before assignment

I see the problem, sorry for interrupt.

repo: HLearning/fisheye


text:
Accessoires Raumzuordnung

Hallo,
Ist es eigentlich möglich die Geräte bereits mit den korrekten Räumen zu initialisieren? Kann das irgendwo im HomeKit-Node eingestellt werden?
Danke und Gruß

nein, die Bridge hat kein Einfluss darauf, Raumzuordnungen und Umbenennungen existieren nur innerhalb von iOS/iCloud.

Ok Danke

repo: HM-RedMatic/RedMatic-HomeKit