text:
Custom Endpoint Support

Let's add support for any custom endpoint across the board. We already have support for Datastore, PubSub and (soon) Bigtable. For the most part supporting them has just been some minor configuration changes, so we should be able to support it everywhere.

[ ] GOOGLE_CLOUD_BIGQUERY_ENDPOINT
[ ] GOOGLE_CLOUD_BIGTABLE_ENDPOINT
[ ] GOOGLE_CLOUD_COMPUTE_ENGINE_ENDPOINT // GCE_ENDPOINT?
[ ] GOOGLE_CLOUD_DATASTORE_ENDPOINT
[ ] GOOGLE_CLOUD_DNS_ENDPOINT
[ ] GOOGLE_CLOUD_LANGUAGE_ENDPOINT
[ ] GOOGLE_CLOUD_LOGGING_ENDPOINT
[ ] GOOGLE_CLOUD_PREDICTION_ENDPOINT
[ ] GOOGLE_CLOUD_PUBSUB_ENDPOINT
[ ] GOOGLE_CLOUD_RESOURCE_MANAGER_ENDPOINT
[ ] GOOGLE_CLOUD_SPEECH_ENDPOINT
[ ] GOOGLE_CLOUD_STORAGE_ENDPOINT
[x] GOOGLE_CLOUD_TRANSLATE_ENDPOINT - #1674
[ ] GOOGLE_CLOUD_VISION_ENDPOINT

Small title change to make sure it's clear we want to support "http://any-uri" as opposed to only official service emulators.

@danoscarmike might also be interested in the idea like this.

I'm would be super excited to see this feature merged in the next release (custom endpoints are very very helpful for people who operate behind forward proxies).
I can open a PR in the next days that puts a function very similar to {Datastore|PubSub}.prototype.determineBaseUrl_ in common.utils and then use it across the different services.
Rodrigo

Are these individual environment variables? That seems lousy. I would much rather have this be a parameter that can be passed to clients.

PubSub does expose a parameter (vs. other services that use environment variables):
https://github.com/GoogleCloudPlatform/google-cloud-node/blob/a64ad81517045196cf5a3f468ea15aad1e2c25da/packages/pubsub/src/index.js#L83
I prefer the parameter approach as well. @lukesneeringer any other comments on the suggested changes? I can start writing some code for GCE

The other primary comment I have is whether or not the client objects wrap a common object (I think they do). If they do, then the best answer is to place the apiEndpoint parameter there. If not, then it would need to be applied to each object.
It looks like it needs to be explicitly passed -- see here in Spanner, for instance. That value just needs to change to options.apiEndpoint || 'spanner.googleapis.com'. Similar in every gRPC-based API.

I believe this was originally a @jgeewax request to have env vars for each. I think the nice part of env vars is you don't have to modify your code depending on where your app is running.
Either way, we should expose at least an override via options.apiEndpoint for all APIs. Thank you for volunteering @rmanyari!

I believe this was originally a @jgeewax request to have env vars for each. I think the nice part of env vars is you don't have to modify your code depending on where your app is running.

You can always have your code set a value based on your own environment variable. Not so much the converse.

Silly question. I'm extracting determineBaseUrl in ./packages/common and ./packages/common-grpc. Before calling common.utils.determineBaseUrl in ./packages/compute/src/index.js I have to do:
> npm link ../packages/common

to pickup my local changes. I'm not 100% sure how the publishing process works for this project. Should I submit a PR for the changes in common and common-grpc first and then bump the version in the other service packages before submitting the changes or is there a clever way of building everything that I'm missing out?

It's fine to put it in one PR. We don't have automated releases, so I'll be manually testing / publishing anyway :)
Just a tip, we have an npm run script that you can run from the root directory of the project:
$ npm run link-common

Just opened a PR. A few things:
I only added support for bigquery, bigtable, compute, datastore, dns and language since the change set is already getting big. If everything looks OK, I can continue with the 2nd half.
The build is failing because there are changes under common that are not picked up by the build. Should the build do npm run link-common before trying to run the tests?
It has the no CLA label since I don't think I was added (yet) to the list of authorized contributors at the company I work for. I already got cleared internally, this should go away soon

@alexander-fenster do we still want environment variable support for endpoints, or is an option, i.e. config.apiEndpoint = 'http://my-api.com' good enough?

We have 3 different API types:
Not supported

REST (nodejs-common)

Already supported!

GRPC (nodejs-common-grpc):

new Firestore({ baseUrl: 'http://my-custom-endpoint' })

GAPIC:

new Datastore({ servicePath: 'http://my-custom-endpoint' })

options.apiEndpoint is what our REST APIs have used before, and I'm not sure if any still do.
options.baseUrl is what we used in common-grpc. I believe Firestore is the only API still using that module for API requests.
options.servicePath is a term right from gRPC, and thus GAPIC. We transparently accept it, as all user options are passed right through to GAPIC.

Does anyone have thoughts on how we should support this concept of a custom API endpoint?

I might be a little bit out of context, but having a possibility to override the endpoint via the environment variable might be valuable (e.g. for testing purposes). I don't think it's a high priority request though.

So... good news!  This is now a high priority thing 🙃 Let's track it over in #2928

This issue also covered env vars to change the API endpoint, which was a Googler-requested feature at one point. I can see the value for the user, but it would also be the same as a small modification the user can make themselves with the same net effect:
$ echo $GOOGLE_CLOUD_BIGQUERY_ENDPOINT
https://my-custom-endpoint

new Storage({
  apiEndpoint: process.env.GOOGLE_CLOUD_BIGQUERY_ENDPOINT
})

That's a really good question :) I've never heard this request.  Is this primarily a testing thing? (cc @broady)

authors: JustinBeckwith alexander-fenster callmehiphop jmuk lukesneeringer rmanyari stephenplusplus


text:
Fix pub/sub with 0 nanos

Closes #1925
Sometimes seconds/nanos are a string, so I decided to use != null check instead.

I signed it!

Coverage remained the same at 100.0% when pulling 2043359063611f81c174a0aa7d6e338cb79583a3 on arbesfeld:master into fd22ba5aaa5dca27a395495612d63eed4a622786 on GoogleCloudPlatform:master.

Coverage remained the same at 100.0% when pulling 2043359063611f81c174a0aa7d6e338cb79583a3 on arbesfeld:master into fd22ba5aaa5dca27a395495612d63eed4a622786 on GoogleCloudPlatform:master.

Coverage remained the same at 100.0% when pulling 2043359063611f81c174a0aa7d6e338cb79583a3 on arbesfeld:master into fd22ba5aaa5dca27a395495612d63eed4a622786 on GoogleCloudPlatform:master.

Thank you!

source: gharchive/pull-request

authors: arbesfeld coveralls stephenplusplus

repo: GoogleCloudPlatform/google-cloud-node

license_type: permissive

license_source: github-api


text:
readme: remove Dependency CI

It's been 5 months of pending builds: https://dependencyci.com/github/GoogleCloudPlatform/google-cloud-node?page=23
And if you go before that, we always had failed builds because of things we can't control-- dependencies of dependencies of dependencies, etc. Is it cool to remove this?
cc @lukesneeringer

Coverage remained the same at 100.0% when pulling 92afbf0ed92e5944ea11fa9029c30e76ec9adca4 on stephenplusplus:spp--remove-dependency-ci into 5883af7c1ffccfae644683d8d45acf1d62c544bf on GoogleCloudPlatform:master.

👍

authors: callmehiphop coveralls stephenplusplus


text:
[Spanner] Unable to set a nullable column to null

It seems like the code below is preventing us from setting a nullable column's value to null
https://github.com/GoogleCloudPlatform/google-cloud-php/blob/master/Spanner/src/Operation.php#L86
If there is an alternative way, please let me know how to update a nullable column with a null value.

It also reproduced in my environment.
The code of reproduction was attached below.
Code
use Google\Cloud\Spanner\SpannerClient;
use Google\Cloud\Spanner\KeySet;
use Ramsey\Uuid\Uuid;

const DDL = <<<DDL
CREATE TABLE `NullTestTable` (
  `ID` STRING(36) NOT NULL,
  `NullableColumn` STRING(255),
) PRIMARY KEY (`ID`)
DDL;

$spanner = new SpannerClient(['projectId' => $projectId]);
$db = $spanner->connect($instanceId, $databaseId);

$operation = $db->create([
    'statements' => [DDL],
]);
$operation->pollUntilComplete();

$db->delete('NullTestTable', new KeySet(['all' => true]));

$rowId = Uuid::uuid4()->toString();

printf(' --- start inserting with "hello"'.PHP_EOL);
$db->insert('NullTestTable', ['ID' => $rowId, 'NullableColumn' => 'hello']);

$rowBefore = $db->execute('SELECT * FROM `NullTestTable` LIMIT 1')->rows()->current();
printf('row.NullableColumn: %s'.PHP_EOL, $rowBefore['NullableColumn']);

printf(' --- start updating with null'.PHP_EOL);
$db->update('NullTestTable', ['ID' => $rowId, 'NullableColumn' => null]);

$rowAfter = $db->execute('SELECT * FROM `NullTestTable` LIMIT 1')->rows()->current();
printf('row.NullableColumn: %s'.PHP_EOL, $rowAfter['NullableColumn']);

Output
 --- start inserting with "hello"
row.NullableColumn: hello
 --- start updating with null
row.NullableColumn: hello

@jdpedrie I think this should be assigned to you, but you're not a member of the project. So, assigning @tmatsuo and @dwsupplee instead.

thanks @broady. not sure why i didn't show up there. i took ownership.

source: gharchive/issue

authors: broady castaneai jdpedrie taka-oyama

repo: GoogleCloudPlatform/google-cloud-php


text:
Output says "Publishing  to Compute Engine." when deploying to GAE Flex

The console output says "Publishing  to Compute Engine." when deploying to GAE Flex.
This was a little confusing at first even if GAE Flex is backed by GCE

Also as a note I had a failed deployment and it says the correct thing:
"Failed to deploy project to App Engine Flex"

license_source: bigquery


text:
Add KubectlContextProvider.

Cleanup GkeStepViewModelTests.

@quoctruong PTAL.


text:
Update the ASP.NET Core on GCE warning message.

PTAL.
Updated with a screenshot of the new warning message.
After consideration, I decided auto-selecting "Don't show this warning again" was not a great idea. If someone quickly clicks through the warning, they would have no way to get back to it, and would be left wondering what it was.


text:
Add more documents for each resource in the templates and therefore in the generated configs

For example, it could be useful if the generated configs can have the usage instructions for bastion-vm above the module.

obsolete, won't fix


text:
VPC subnet definitions are overly restrictive

The current requirements for a VPC created through resources/network/vpc require that each subnet's address range be a sub-block of the network_address_range parameter.  This requirement is set by specifying subnets via a new_bits parameter, and the Terraform using the cidrsubnets function.
These requirements remove the ability for a user to precisely the define the subnets and address ranges they wish to use, as well as requires all created subnets to have a common prefix.  This prevents (admittedly obtuse) situations like subnets in a VPC containing completely different address ranges (mixing 10. with 192.168., etc, etc).
I would like to see the ability to specify each subnet which should be created by explicitly defining it's CIDR, rather than setting the network_address_range and new_bits variables.

For record: we are designing a backwards-compatible solution for this extra functionality and have the implementation work planned as a high priority for the 1.x series of the Toolkit. We will update the schedule as we make progress.

This has been incorporated on the develop branch of the HPC Toolkit and will be included in our next tagged release. Please see #392 for details.
We will leave this issue open until the fix is in a tagged release.

authors: ghost tpdownes

repo: GoogleCloudPlatform/hpc-toolkit


text:
Node Termination handler may still be necessary

The current README states this handler is deprecated in favor of the new Graceful Node Shutdown:

⚠ Deprecation Notice
As of Kubernetes 1.20, Graceful Node Shutdown replaces the need for GCP Node termination handler. GKE on versions 1.20+ enables Graceful Node Shutdown by default. Refer to the GKE documentation and Kubernetes documentation for more info about Graceful Node Shutdown (docs, blog post).

I have been using the Node Termination handler with GKE < 1.20, using pre-emptibles with GPUs.  The handler was needed to avoid a race condition on node restart that sometimes caused pods not to correctly recognize the GPU.
I have moved to GKE 1.21.1-gke.2200 and found the same error I would get with version <1.20 without the Node Termination handler.  This handler happens only occasionally, so it seems like potentially the same race condition.

ImportError: libcuda.so.1: cannot open shared object file: No such file or directory

I filed the following GKE issue.
https://issuetracker.google.com/issues/192809336
For the moment, I would ask that this repo not be deprecated.

At the very least, it seems that the handler is useful through the 1.21 series of releases:
https://issuetracker.google.com/issues/204415098

Hi @chrisroat! The GKE issue was closed recently. Are you still facing any problems with node shutdowns so you still need the node termination handler?

I no longer maintain the (closed-source) project that was hitting the issue.  We had forked this repo to add the ability to handle spot instances.
@erichamc would be able to test, though I don't think it would be high priority to check.  For reference, the symptom was that the cluster's gpu workloads would not restart properly after node preemptions.  Over time, a cluster might -- if it had enough preemptions to trigger the issue -- show failing workloads unable to find the nvidia libraries.  [@erichamc -dropping the termination handler would amount to dropping the null_resource stanzas in infrastructure/apps/k8s/kubectl.tf]

authors: chrisroat torbendury


text:
Creating a pod with Celery image doesn't work. Also, create->start container endless loop.

I am trying to set up a pod that contains a Celery image. I created a simple replication controller to use the celery dockerfile:
{
  "id": "celery-controller",
  "kind": "ReplicationController",
  "apiVersion": "v1beta1",
  "desiredState": {
    "replicas": 1,
    "replicaSelector": {"name": "celery"},
    "podTemplate": {
      "desiredState": {
        "manifest": {
          "version": "v1beta1",
          "id": "celery",
          "containers": [{
            "name": "celery",
            "image": "dockerfile/celery",
            "cpu": 100,
            "ports": [{"containerPort": 9876, "hostPort": 9876}]
          }]
        }
      },
      "labels": {
        "name": "celery",
      }
    }
  },
  "labels": {
    "name": "celery"
  }
}

From looking at the documentation (https://registry.hub.docker.com/u/dockerfile/celery/dockerfile/), I expected that when I start this controller I would see that pip installs the celery package. However, this doesn't happen. In fact, even pip itself is not installed.
The results of docker ps are:
$ sudo docker ps
CONTAINER ID        IMAGE                   COMMAND               CREATED             STATUS              PORTS                    NAMES
9372d9000fbe        kubernetes/pause:go     "/pause"              17 minutes ago      Up 17 minutes       0.0.0.0:9876->9876/tcp   k8s_POD.a5cea3a_celery-controller-gziey.default.api_e1d5ea0c-c0f0-11e4-92de-0800279696e1_8e8936f7
6c053213d869        google/cadvisor:0.8.0   "/usr/bin/cadvisor"   31 minutes ago      Up 31 minutes                                k8s_cadvisor.8d424740_cadvisor-agent.file-6bb810db-kubernetes-minion-2.file_e8804cbb62b8adb446577bcf28197c52_23a640b5
d75dcbf4ec4f        kubernetes/pause:go     "/pause"              32 minutes ago      Up 32 minutes       0.0.0.0:4194->8080/tcp   k8s_POD.252debe0_cadvisor-agent.file-6bb810db-kubernetes-minion-2.file_e8804cbb62b8adb446577bcf28197c52_54a98ef9

I thought I might be missing something simple, but when I run $ cluster/kubectl.sh describe pod celery-controller-gziey, I get strange output that suggests there might be a bug somewhere:
current-context: "vagrant"
Running: cluster/../cluster/vagrant/../../_output/dockerized/bin/linux/amd64/kubectl --kubeconfig=/home/karl/.kubernetes_vagrant_kubeconfig describe pod celery-controller-gziey
Name:				celery-controller-gziey
Image(s):			dockerfile/celery
Host:				10.245.1.4/10.245.1.4
Labels:				name=celery
Status:				Running
Replication Controllers:	celery-controller (1/1 replicas created)
Conditions:
  Kind		Status
  Ready 	None
Events:
FirstSeen			LastSeen			Count	From			SubobjectPath				Reason		Message
Mon, 02 Mar 2015 15:29:13 +0000	Mon, 02 Mar 2015 15:29:13 +0000	1	{kubelet 10.245.1.4}	implicitly required container POD	created		Created with docker id 9372d9000fbe752c7dd6b7ad0ade17d3fa3fddb4eac4b0b50e1815497ddb4405
Mon, 02 Mar 2015 15:29:13 +0000	Mon, 02 Mar 2015 15:29:13 +0000	1	{kubelet 10.245.1.4}	implicitly required container POD	pulled		Successfully pulled image "kubernetes/pause:latest"
Mon, 02 Mar 2015 15:29:13 +0000	Mon, 02 Mar 2015 15:29:13 +0000	1	{kubelet 10.245.1.4}	implicitly required container POD	started		Started with docker id 9372d9000fbe752c7dd6b7ad0ade17d3fa3fddb4eac4b0b50e1815497ddb4405
Mon, 02 Mar 2015 15:29:14 +0000	Mon, 02 Mar 2015 15:29:14 +0000	1	{scheduler }							scheduled	Successfully assigned celery-controller-gziey to 10.245.1.4
Mon, 02 Mar 2015 15:32:33 +0000	Mon, 02 Mar 2015 15:32:33 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			pulled		Successfully pulled image "dockerfile/celery"
Mon, 02 Mar 2015 15:32:34 +0000	Mon, 02 Mar 2015 15:32:34 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			created		Created with docker id 0b1d152c91503aa19238fcc547302d37e1063f52c48b0d08d9010d23b95d501c
Mon, 02 Mar 2015 15:32:34 +0000	Mon, 02 Mar 2015 15:32:34 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			started		Started with docker id 0b1d152c91503aa19238fcc547302d37e1063f52c48b0d08d9010d23b95d501c
Mon, 02 Mar 2015 15:32:43 +0000	Mon, 02 Mar 2015 15:32:43 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			created		Created with docker id be84906e41489d5ee3abe20101652a5720a2de2cd469a99a98206231f3dd64e0
Mon, 02 Mar 2015 15:32:43 +0000	Mon, 02 Mar 2015 15:32:43 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			started		Started with docker id be84906e41489d5ee3abe20101652a5720a2de2cd469a99a98206231f3dd64e0
Mon, 02 Mar 2015 15:32:53 +0000	Mon, 02 Mar 2015 15:32:53 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			created		Created with docker id 6a027b874dc98450ff654529a92a1fa37ccbffb37163710685bbadeff182dd34
Mon, 02 Mar 2015 15:32:54 +0000	Mon, 02 Mar 2015 15:32:54 +0000	1	{kubelet 10.245.1.4}	spec.containers{celery}			started		Started with docker id 6a027b874dc98450ff654529a92a1fa37ccbffb37163710685bbadeff182dd34
etc.
etc.
etc.

This started->created->started loop continues on and on.
I am using the latest version of the Kubernetes master (commit 6c5b3901).
Am I doing something wrong here? Is anyone else able to get a Celery image up and running?
Or have I perhaps found some kind of bug?

What are you trying to do with celery? That docker image appears to be designed to be a base image upon which other layers are expected to be added. The default command is "bash" -- it doesn't actually do anything on its own.

Yes, this was confusion on my part over the lifecycle of a docker container. I didn't realise that the container would be automatically rescheduled after the container stops without doing anything. This can be closed.

repo: GoogleCloudPlatform/kubernetes


text:
Stop using named ports in examples and scripts.

even if we can't turn it off completely yet (TBD) we can stop endorsing it.

@thockin Why is this a bad practice ?

We're going to change "name" to "description"  to indicate that it's a human readable description, not a referenceable name.

authors: brendandburns sub-mod thockin


text:
Add animated presentation detailing the Kubernetes GitHub Flow to developer docs

As suggested by/discussed with Tim Hockin.

Did you re-offer this PR?
On Wed, Mar 4, 2015 at 5:14 PM, Quinton Hoole notifications@github.com
wrote:

Closed #5082 https://github.com/GoogleCloudPlatform/kubernetes/pull/5082
.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5082#event-246463593
.

Yeah, that's the branch that I subsequently deleted.
On Mar 4, 2015 22:53, "Tim Hockin" notifications@github.com wrote:

Did you re-offer this PR?
On Wed, Mar 4, 2015 at 5:14 PM, Quinton Hoole notifications@github.com
wrote:

Closed #5082 <
https://github.com/GoogleCloudPlatform/kubernetes/pull/5082>
.
—
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/kubernetes/pull/5082#event-246463593
.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5082#issuecomment-77315861
.

authors: quinton-hoole-google thockin


text:
Port minion registry to generic etcd

Ported minion registry to genericetcd storage
Call validation.ValidateMinionUpdate via nodeStrategy
master and service registry have an interface to node storage instead of registry

And I'm not sure the last commit is right. In #2115 PUT the same body returns 409 , but test cases were updated to return 200 except Node resource.

@dchen1107 : assigning to you, but please feel free to outsource to someone else.

!! Glad you post it today, I was going to do the same thing.
I also plan to add a status store for posting node status later, like this:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/registry/pod/rest.go#L75
Just want to check with you if that is on your radar?

You mean newly implment nodes/status api to update status like here, right?
I don't understand the context, but I can help to do that.

Yes. nodes/status.  I already started looking at it, but contribution welcome!  Let's get this in first though.
Ping me on irc (deyuan) if you plan to work on it.  We don't want dupliate work : )

Please do it. Then, I'll look other registries for porting.

e2e tests passed with a fix.

fyi, I'm already porting replication controller

@smarterclayton Moved MatchMinion to pkg/registry/minion/rest.go, and removed this since e2e tests passed.
@bprashanth Rebased to #5534.
e2e tests passes except for monitoring and cadvisor, but it seems by other problems?

@kazegusuri if it's unrelated flake and you don't see an open issue, please file one. fyi i usually rerun specific tests with ginko when one or two fail https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/devel/development.md

Rebased to HEAD and verfied all e2e passed. PTAL.

one last comment then LGTM

Needs rebase. If possible please merge this PR today - it'll make my life a bit easier.

Rebased to HEAD and verified e2e test passed. Please review again since sourcecode was changed a little.
The main change is stop using node interface and use node registry as is.

Will merge on green

authors: bprashanth ddysher gmarek kazegusuri satnam6502 smarterclayton


text:
Configure MonitoringResource for TimeSeries

Currently the second argument of Exporter.Export() is meant for the common resource among all records stored via a meter, and the resource is the counterpart of MonitoredResource in TimeSeries.
In OpenCensus, the interface for MonitoredResource is defined apart from the protobuf and controlled separately. Similarly to OpenCensus, OpenTelemetry exporter should have the extra care for MonitoredResource.
For now, it just returns "global" resource. (hard coded)

@dashpole could you confirm if this is still the case or not?

I confirmed that metrics attributes work perfectly in this code, so when switching to generic_task, I think we need to have it move all labels that are not defined for the monitored_resource as well. WDYT?

Yeah, similar to the collector exporter's resource_filters option, it would be nice to be able to elevate additional resource attributes to metric labels.  I don't think we should do that for all additional labels, though, as detectors (e.g. for language or env, etc) often generate a very large number of attributes.  By default, we shouldn't add additional labels

We support all the monitored resources listed above except dataflow_job. We can open a separate issue to track support for dataflow if it's requested.

authors: damemi dashpole ymotongpoo


text:
Logs without timestamps are skewed after a network outage

Observed Behavior
If a network outage occurs and retry on failure is enabled, queued logs without timestamps will be given a much newer timestamp than expected. This is because the current time is assigned only when the google logging entry is created and not when logs reach the exporter for the first time. If a user does not understand this behavior beforehand, this can appear as an unexplained clock skew after an outage.
Potential Solution
This could be solved by defaulting to the observed timestamp of the log when a timestamp does not exist, as noted here: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/7e416c3ba3a366ddcc8791a738af17d1610eacd2/exporter/collector/logs.go#L385

Thanks @jmwilliams89, will look into fixing this. In the meantime, you can probably use a transform processor in your collector to set the timestamp you want as a workaround. But we should try to fall back to the observed_time when available.

This should be fixed by #640 and will be in the next release


text:
chore: (language) removed unsupported samples

Devsite update: cl/365253385
go/cloud-ai-2021-snippet-cleanup

PTAL @bshaffer

I do not agree that these samples should be removed so you will need to find someone else to approve and merge this

authors: bshaffer munkhuushmgl

repo: GoogleCloudPlatform/php-docs-samples


text:
Adds laravel example

These tests won't pass until after https://github.com/GoogleCloudPlatform/php-docker/pull/136 and https://github.com/GoogleCloudPlatform/appengine-sidecars-docker/pull/19 are live.

This is ready for another look


text:
feat: create output for version

Description
It would be really handy if the action created a few outputs that would be useful for later steps like:

tag: 1.0.0
commit: 62a67966c87f04fba1944c0fe548b018864bad71

@jef this seems like it would be a pretty reasonable addition. I think we'd need to make release-please return an object with this information when run programmatically perhaps?

That's a good question. If release-please uses @actions/core, this could make this pretty straight forward (hopefully)!
https://github.com/actions/toolkit/tree/master/packages/core#inputsoutputs

Or how ever this action interacts with release-please to be able to return that information. Then run core.setOutput on that value since release-please is outside of this action's scope.

authors: bcoe jef


text:
Spark operator not running in one of the examples [Spark-Pi]

I followed the quick start guide and use the spark-pi application in the samples.
The problem are the following:

All computation is run on the driver pod instead of the executor pod.
No executor pod/s has been spinned up

My understanding is the driver pod will just get the results from executor pod. In the yaml, we defined 1 executor but it looks like its not being used. Why is the executor pod not created and the driver pod doing all the work?

Hi, @vvavepacket.
executor pods will be killed when jobs is finished. so you can't see the executor pods.
You can set arguments.
eg:
arguments:
- "10000"

it will run long time  so that you can find executor pods


text:
Add ASM to a hipstershop deployment on a Sandbox

We need to add istio support, but likely having Anthos Service Mesh is even better option to illustrate how it helps observe the apps.

ASM looks like it requires an Anthos subscription. I think we'd be better off using OSS Istio for now. We can use this as a template: https://github.com/GoogleCloudPlatform/bank-of-anthos-scripts/blob/master/install/istio/install_istio.sh

Discussed this with Nick, he's going to try handling this, and we'll check back in next week.
Nick:

Here's how we added Istio upstream, but that method is stuck at 1.4, so we're better off using the OSS directions instead
This is a script we used to enable Istio 1.6 in a different project
This looks like another attempt to provision istio using terraform, but I'm not familiar enough with Terraform to say if it's useful for us

Let me know if you run into any issues

This has been resolved in #139

repo: GoogleCloudPlatform/stackdriver-sandbox


text:
fix: Change "postgresql" to "postgres"

Background:

See Google-internal: b/350774994#comment8.
Currently, the Cloud Console "Database type" drop-down uses postgres but our Terraform database_type input variable expects postgresql.
Sorry about the miscommunication.

Solution:

I'm updating the Terraform to use postgres instead of postgresql.

Feel free to review and approve. But do not merge. Need to decide on this PR or cl/678683958.

We went with cl/678683958.


text:
Support google_storage_bucket_object export

While the information already exported from GCS is very useful, it would also be useful to be able to replicate/export the directory and file "tree" ("tree" as we know that GCS is actually a flat filesystem).
Can this capability be added? Does it make sense?

Generically, all of the objects' contents data isn't backed up by the tool.  Disks aren't dumped or archived, storage buckets aren't copied or dumped, message queues aren't read, databases aren't dumped, etc.
I can see why you'd want that, but terraform usually doesn't provision contents like that and terraformer seems by design not to back them up.  You'd want to combine a backup tool for the objects' contents, and terraformer to ensure that the objects are all recreated so that you can restore their contents.
Perhaps a way to do full object data dumps would make sense as an extension or fork of Terraformer, so that it would be all in one.  But it's a slightly different problem.  And brings into play all the backup software issues (incremental vs full backups, size of backups and storage management, frozen point in time snapshot or rolling backup with possible time inconsistency across objects, ability to restore individual objects or sets of objects vs full restore, etc etc.).

authors: CelsoSantos georgewilliamherbert

repo: GoogleCloudPlatform/terraformer


text:
Terraformer imported Datadog dashboard not preserving order

Hi, I tried to import Datadog dashboard using terraformer.
However, the imported .tf file doesn't seem to preserve either the group order or the widget order.
So, if I apply the .tf, basically the dashboard graphs are randomly shuffled.
I am using Terraformer 0.8.2.0, and Datadog provider 3.11.0. Both the latest version.
Here is how to reproduce.

Create a dashboard randomly. I created one with two groups ("Group 3", then "Group 2") and 2 graphs per group, titled "4", "3" in Group 3; Titled "2", "1" in "Group 2".

{"title":"TestBoard","description":"## Title\n\nDescribe this dashboard. Add links to other dashboards, monitors, wikis,  and docs to help your teammates. Markdown is supported.\n\n- [This might link to a dashboard](#)\n- [This might link to a wiki](#)","widgets":[{"id":3162817219040794,"definition":{"title":"Group 3","type":"group","show_title":true,"layout_type":"ordered","widgets":[{"id":398899176012522,"definition":{"title":"4","title_size":"16","title_align":"left","show_legend":true,"legend_layout":"auto","legend_columns":["avg","min","max","value","sum"],"time":{},"type":"timeseries","requests":[{"response_format":"timeseries","queries":[{"name":"query1","data_source":"metrics","query":"avg:system.cpu.user{*}"}],"style":{"palette":"dog_classic","line_type":"solid","line_width":"normal"},"display_type":"line"}]},"layout":{"x":0,"y":0,"width":4,"height":2}},{"id":3549571517443056,"definition":{"title":"3","title_size":"16","title_align":"left","show_legend":true,"legend_layout":"auto","legend_columns":["avg","min","max","value","sum"],"time":{},"type":"timeseries","requests":[{"response_format":"timeseries","queries":[{"name":"query1","data_source":"metrics","query":"avg:system.cpu.user{*}"}],"style":{"palette":"dog_classic","line_type":"solid","line_width":"normal"},"display_type":"line"}]},"layout":{"x":4,"y":0,"width":4,"height":2}}]},"layout":{"x":0,"y":0,"width":12,"height":3}},{"id":8411657921683638,"definition":{"title":"Group 2","type":"group","show_title":true,"layout_type":"ordered","widgets":[{"id":7827610054614036,"definition":{"title":"2","title_size":"16","title_align":"left","show_legend":true,"legend_layout":"auto","legend_columns":["avg","min","max","value","sum"],"time":{},"type":"timeseries","requests":[{"response_format":"timeseries","queries":[{"name":"query1","data_source":"metrics","query":"avg:system.cpu.user{*}"}],"style":{"palette":"dog_classic","line_type":"solid","line_width":"normal"},"display_type":"line"}]},"layout":{"x":0,"y":0,"width":4,"height":2}},{"id":3118368310491542,"definition":{"title":"1","title_size":"16","title_align":"left","show_legend":true,"legend_layout":"auto","legend_columns":["avg","min","max","value","sum"],"time":{},"type":"timeseries","requests":[{"response_format":"timeseries","queries":[{"name":"query1","data_source":"metrics","query":"avg:system.cpu.user{*}"}],"style":{"palette":"dog_classic","line_type":"solid","line_width":"normal"},"display_type":"line"}]},"layout":{"x":4,"y":0,"width":4,"height":2}}]},"layout":{"x":0,"y":3,"width":12,"height":3}}],"template_variables":[],"layout_type":"ordered","is_read_only":false,"notify_list":[],"reflow_type":"fixed","id":"imt-6r3-tza"}

Import the dashboard many times:

mkdir -p /tmp/testboard/{1..10}
for i in /tmp/testboard/{1..10}; do terraformer import datadog --resources=dashboard --filter=dashboard=imt-6r3-tza --path-output=$i; done

Check the dashboard.tf, it is expected to be [{Group 3: 4, 3}, {Group 2: 2, 1}]. However this is what I got:

----------/tmp/testboard/1
  title        = "TestBoard"
      title       = "Group 2"
          title       = "1"
          title       = "2"
      title       = "Group 3"
          title       = "4"
          title       = "3"
----------/tmp/testboard/2
  title        = "TestBoard"
      title       = "Group 2"
          title       = "1"
          title       = "2"
      title       = "Group 3"
          title       = "3"
          title       = "4"
----------/tmp/testboard/3
  title        = "TestBoard"
      title       = "Group 2"
          title       = "2"
          title       = "1"
      title       = "Group 3"
          title       = "3"
          title       = "4"
----------/tmp/testboard/4
  title        = "TestBoard"
      title       = "Group 2"
          title       = "1"
          title       = "2"
      title       = "Group 3"
          title       = "4"
          title       = "3"
----------/tmp/testboard/5
  title        = "TestBoard"
      title       = "Group 2"
          title       = "1"
          title       = "2"
      title       = "Group 3"
          title       = "4"
          title       = "3"
----------/tmp/testboard/6
  title        = "TestBoard"
      title       = "Group 2"
          title       = "1"
          title       = "2"
      title       = "Group 3"
          title       = "4"
          title       = "3"
----------/tmp/testboard/7
  title        = "TestBoard"
      title       = "Group 2"
          title       = "2"
          title       = "1"
      title       = "Group 3"
          title       = "3"
          title       = "4"
----------/tmp/testboard/8
  title        = "TestBoard"
      title       = "Group 2"
          title       = "2"
          title       = "1"
      title       = "Group 3"
          title       = "4"
          title       = "3"
----------/tmp/testboard/9
  title        = "TestBoard"
      title       = "Group 2"
          title       = "1"
          title       = "2"
      title       = "Group 3"
          title       = "3"
          title       = "4"
----------/tmp/testboard/10
  title        = "TestBoard"
      title       = "Group 2"
          title       = "2"
          title       = "1"
      title       = "Group 3"
          title       = "3"
          title       = "4"

Looks like Group level is sorted by name, and the graph order is undetermined everytime when import.

By the way, this is introduced in v0.8.19, because v0.8.18 works fine.

I think this causes by the same reason in https://github.com/GoogleCloudPlatform/terraformer/issues/1316

This issue must be resolved. Latest version (v0.8.19) is completely unusable for datadog dashboard because of this problem.

This issue still exists in v0.8.22.

Hey, is there any workaround to go over this issue? the last version doesn't look stable when it comes to import Datadog dashboards

@bshbair I've resorted to exporting my DataDog dashboards as JSON, and then providing that JSON to a new datadog_dashboard_json resource in Terraform. I do suggest saving your JSON file separately and loading that up in the resource using the file(...) function:
resource "datadog_dashboard_json" "example_dash" {
  dashboard = file("${path.module}/dashboard_templates/example_dash.json")
}

Any updates?

Was this issue ever resolved?

Can we reopen this issue? It shouldn't have been closed in the first place, in my opinion.

authors: CostinTanasoiu alexwilkerson brianstrauch bshbair chinuy ikuwow weichuliu


text:
At 3:2: object expected closing RBRACE got: EOF (import plan, aws securityhub)

What happened
terraformer-aws import plan ./generated/aws/terraformer/plan.json
2022/11/30 07:32:50 aws Connecting....
2022/11/30 07:32:50 aws save securityhub
2022/11/30 07:32:50 At 3:2: object expected closing RBRACE got: EOF

Expected
Work without error.
More info
environment
$ terraform --version && ../terraformer/terraformer-aws --version && tree .terraform/
Terraform v1.3.5
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v4.43.0
version v0.8.22
.terraform/
└── providers
    └── registry.terraform.io
        └── hashicorp
            └── aws
                └── 4.43.0
                    └── linux_amd64
                        └── terraform-provider-aws_v4.43.0_x5

6 directories, 1 file

plan works fine
$ ../terraformer/terraformer-aws plan aws --resources="securityhub" --regions=us-east-1 --profile="ipi"
2022/11/30 07:12:53 aws importing region us-east-1
2022/11/30 07:12:55 aws importing... securityhub
2022/11/30 07:12:58 aws done importing securityhub
2022/11/30 07:12:58 Number of resources for service securityhub: 3
2022/11/30 07:12:58 Refreshing state... aws_securityhub_standards_subscription.tfer--arn-003A-aws-003A-securityhub-003A-us-east-1-003A-994276127279-003A-subscription-002F-cis-aws-foundations-benchmark-002F-v-002F-1-002E-2-002E-0
2022/11/30 07:12:58 Refreshing state... aws_securityhub_account.tfer--994276127279
2022/11/30 07:12:58 Refreshing state... aws_securityhub_standards_subscription.tfer--arn-003A-aws-003A-securityhub-003A-us-east-1-003A-994276127279-003A-subscription-002F-aws-foundational-security-best-practices-002F-v-002F-1-002E-0-002E-0
2022/11/30 07:12:59 Filtered number of resources for service securityhub: 3
2022/11/30 07:12:59 Saving planfile to generated/aws/terraformer/plan.json

import plan got error
2022/11/30 07:13:47 aws Connecting....
2022/11/30 07:13:47 aws save securityhub
2022/11/30 07:13:47 At 3:2: object expected closing RBRACE got: EOF

terreform says those files are well-formed, but terraformer has parsing error.
$ terraform plan

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
$ terraform validate
Success! The configuration is valid.


text:
google: Add role_entity to google_storage_bucket_acl

GCP provider checks "role_entity" attribute for retrieving GCS ACL.
https://github.com/terraform-providers/terraform-provider-google/blob/d43a1795b4c1ee45d15d83ba33b588448f3ff392/google/resource_storage_bucket_acl.go#L202
This PR adds "role_entity" to attributes of google_storage_bucket_acl.

Thanks!

authors: sergeylanzman yukirii


text:
Add support for IBM cloud provider

This PR adds support for IBM CLOUD provider.
List of supported resources:

ibm_cos

ibm_resource_instance
ibm_cos_bucket

ibm_iam

ibm_iam_user_policy
ibm_iam_access_group
ibm_iam_access_group_members
ibm_iam_access_group_policy
ibm_iam_access_group_dynamic_rule

ibm_container_vpc_cluster

ibm_container_vpc_cluster
ibm_container_vpc_worker_pool

ibm_database_etcd

ibm_database

ibm_database_mongo

ibm_database

ibm_database_postgresql

ibm_database

ibm_database_rabbitmq

ibm_database

ibm_database_redis

ibm_database

ibm_is_instance_group

ibm_is_instance_group
ibm_is_instance_group_manager
ibm_is_instance_group_manager_policy

ibm_is_vpc

ibm_is_vpc
ibm_is_vpc_address_prefix
ibm_is_vpc_route

ibm_is_subnet
ibm_is_instance
ibm_is_security_group

ibm_is_security_group_rule

@anilkumarnagaraj Good job! thanks!!
Few issues:

signed CLA
delete logs.println in resources
delete logs.fatal and return error. logs.Fatal exit program, if you want import many resources, one of them can close program
licence in files
goroutines issue - I don't find any line with wait for finished in all goroutines

@anilkumarnagaraj Can you signed CLA?

@googlebot I signed it!

authors: anilkumarnagaraj sergeylanzman


text:
Found a flaky test in DockerManifestEntryTemplateTest.java

Environment:

Jib version:
Build tool:  gradle-6.9.2
OS: MacOS

Description of the issue:
Found a flaky test in DockerManifestEntryTemplateTest.testToJson
https://github.com/GoogleContainerTools/jib/blob/440bd4897c6c427cc9a491128aa76c72378d605b/jib-core/src/test/java/com/google/cloud/tools/jib/docker/json/DockerManifestEntryTemplateTest.java#L52
When comparing JSON strings, since JSON is inherently unordered (the order of keys in JSON objects is not guaranteed), it's not reliable to compare JSON strings directly if the order of the keys may vary. This makes this test flaky i.e. non-deterministic. Instead, we should parse the JSON strings into objects and compare the objects semantically.
Expected behavior:
We use Jackson's ObjectMapper to convert the JSON strings into JsonNode objects. Then it compares these JsonNode objects with the equals method, which does a deep comparison of the content without considering the order of the keys.
ObjectMapper mapper = new ObjectMapper();
JsonNode actual = mapper.readTree(JsonTemplateMapper.toUtf8String(loadManifest));
JsonNode expected = mapper.readTree(expectedJson);
Assert.assertEquals(expected, actual);

I've also raised a tentative PR - https://github.com/harshith2000/jib/pull/2
Steps to reproduce:

I utilized the open-source tool NonDex to detect this assumption by altering the order of returned exception types.
To replicate:

Clone the Repository:
https://github.com/GoogleContainerTools/jib.git

Integrate NonDex:

Add the following snippet to the top of the build.gradle file:
plugins {
  id 'edu.illinois.nondex' version '2.1.1-1'
}

Add to the end of the build.gradle file:
apply plugin: 'edu.illinois.nondex'
subprojects {
  apply plugin: 'edu.illinois.nondex'
}

Execute Test with Gradle:

./gradlew --info test --tests com.google.cloud.tools.jib.docker.json.DockerManifestEntryTemplateTest.testToJson

Run NonDex:

./gradlew --info nondexTest --tests=com.google.cloud.tools.jib.docker.json.DockerManifestEntryTemplateTest.testToJson --nondexRuns=2

Log output:
com.google.cloud.tools.jib.docker.json.DockerManifestEntryTemplateTest > testToJson FAILED
    org.junit.ComparisonFailure: expected:<[{"[Config":"config.json","RepoTags":["testregistry/testrepo:testtag"],"Layers":["layer1.tar.gz","layer2.tar.gz","layer3.tar.gz"]]}]> but was:<[{"[RepoTags":["testregistry/testrepo:testtag"],"Layers":["layer1.tar.gz","layer2.tar.gz","layer3.tar.gz"],"Config":"config.json"]}]>
        at org.junit.Assert.assertEquals(Assert.java:117)
        at org.junit.Assert.assertEquals(Assert.java:146)
        at com.google.cloud.tools.jib.docker.json.DockerManifestEntryTemplateTest.testToJson(DockerManifestEntryTemplateTest.java:52)

Please let me know if you have any questions.

Unfortunately, the issue is that in reality we need to verify the syntactic equality in the context of container images, whose great importance I cannot stress enough. In reality, the test is not flaky, and doing semantic comparison can actually be harmful in that the test will succeed when they are not the exact same literal string. The purpose of the test is really to verify that they are literally the same string, not to see they are semantically equal.

Unfortunately, the issue is that in reality we need to verify the syntactic equality in the context of container images, whose great importance I cannot stress enough. In reality, the test is not flaky, and doing semantic comparison can actually be harmful in that the test will succeed when they are not the exact same literal string. The purpose of the test is really to verify that they are literally the same string, not to see they are semantically equal.

I understand. But since we're comparing JSON strings, they cannot be the same strings all the time, right?

In practice, the library always generates the same string; fortunately, there seems no randomness for the same input string. We've upgraded the library version many times, but we haven't seen any regression so far. If we spot any change to the string in a newer library version, then we need to investigate. The test is to catch this situation.

In practice, the library always generates the same string; fortunately, there seems no randomness for the same input string. We've upgraded the library version many times, but we haven't seen any regression so far. If we spot any change to the string in a newer library version, then we need to investigate. The test is to catch this situation.

Understood.
I also found similar flaky tests in other files, as well.
https://github.com/harshith2000/jib/pull/1

repo: GoogleContainerTools/jib


text:
Return BlossomResponse for standard HTTP methods

Relevant issue: #2
Description:
Makes all public methods return BlossomResponse
Checklist:

[x] Code Quality
[x] Pep-8
[x] Tests (if applicable)
[x] Success Criteria Met
[x] Inline Documentation
[x] Wiki Documentation (if applicable)
[x] Bubbles https://github.com/GrafeasGroup/Bubbles-V2/pull/5
[x] tor_ocr https://github.com/GrafeasGroup/tor_ocr/pull/39
[X] tor https://github.com/GrafeasGroup/tor/pull/217
[X] tor_archivist https://github.com/GrafeasGroup/tor_archivist/pull/27

Closing for now, as this is not actively worked on anymore. Feel free to re-open when needed!

authors: MaxVanDeursen TimJentzsch

repo: GrafeasGroup/blossom-wrapper

license: MIT


text:
Add Federation Support

A basic implementation of federation. Some issues I have and could use guidance:

[x] Using AnyCodable as a dependency Used the Map type from GraphQL
[ ] Where to store JSONEncoder/Decoder for reusability
[ ] Users having to implement FederationContext/FederationResolver and copying the SDL in directly
[ ] How to apply directives to fields/types (ie: @key(fields: "id"), @inaccessible, @shareable )
[x] Supporting older versions of Swift (any FederationContext requires 5.7) Updated FederationResolver protocol to offer a method for older versions of Swift

How to apply directives to fields/types (ie: @key(fields: "id"), @inaccessible, @shareable )
@NeedleInAJayStack is directive support already in Graphiti?

How to apply directives to fields/types (ie: @key(fields: "id"), @inaccessible, @shareable )

@NeedleInAJayStack is directive support already in Graphiti?

Not at the moment, but it's deinitely a highly sought-after feature

Not at the moment, but it's deinitely a highly sought-after feature

I can work on that feature - would you prefer directive support before merging in federation?

Awesome, thank you so much @samisuteria! Yeah, from my understanding federation support typically uses custom directives so solving custom directives first in a general way makes sense to me. Thanks again, and great work so far!

Federation can work without directives in the application code. If you are writing schema first (I'm not sure the split between schema-first and code-first in the GraphQL ecosystem) you can enable federation without directives. As long as the service sdl query returns the schema federation will work correct.
query {
   _service { sdl }
}

If you check out the samisuteria/graphiti branch on https://github.com/samisuteria/apollo-federation-subgraph-compatibility/ and run make test subgraph=swift-graphiti you'll see it passes all tests except federated tracing (which seems like a much larger project based on: https://www.apollographql.com/docs/graphos/metrics/sending-operation-metrics#tracing-format) and it appears about half the subgraph libraries have warning levels of support for it https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs .
*************
Federation v1 compatibility
*************
_service PASS
@key (single) PASS
@key (multi) PASS
@key (composite) PASS
repeatable @key PASS
@requires PASS
@provides PASS
federated tracing WARNING

*************
Federation v2 compatibility
*************
@link PASS
@shareable PASS
@tag PASS
@override PASS
@inaccessible PASS

I still plan on working on adding directive/sdl support for Graphiti but I think this PR is ready for review and can be used by people who are schema-first.

I still plan on working on adding directive/sdl support for Graphiti but I think this PR is ready for review and can be used by people who are schema-first.

Sounds good for me. Nice work 👍 . While It's probably a bit awkward atm given you can't really fully do schema-first or use directive with Graphiti, those feature can be separated and worked on later with future PR / releases.

Great info @samisuteria! Thanks for walking me through that, and in that case I'm totally ok with this going in before directive support.
Sorry about the delay - I'll get a review in this weekend.

@samisuteria See what you think of this twist on your implementation: https://github.com/NeedleInAJayStack/Graphiti/tree/federation_jay
If you're okay with it, we can pull those commits into this MR.

@NeedleInAJayStack I really like the changes on your branch and the Key implementation / mapping to the Resolver argument types is a much better way to implement federation.
The syntax for defining keys in the schema seems like complicated (anytime you have multiple builder closures in a function).
What do you think of something like this? It would just require keys: [KeyComponent<ObjectType, Resolver, Context>] to be mutable.
Type(Product.self) {
    Field("id", at: \.id)
    Field("sku", at: \.sku)
    Field("package", at: \.package)
    Field("variation", at: \.variation)
    Field("dimensions", at: \.dimensions)
    Field("createdBy", at: \.createdBy)
    Field("notes", at: \.notes)
    Field("research", at: \.research)
}
.key(at: ProductResolver.getProduct1) {
    Argument("id", at: \.id)
}
.key(at: ProductResolver.getProduct2) {
    Argument("sku", at: \.sku)
    Argument("package", at: \.package)
}
.key(at: ProductResolver.getProduct3) {
    Argument("sku", at: \.sku)
    Argument("variation", at: \.variation)
}

@samisuteria Ooo, I love that idea. You're right, looks cleaner and better preserves the public API

@samisuteria I just implemented your suggestion on my branch. If you like it, feel free to pull those commits into this MR. Thanks again!

Just pulled in the changes - thank you so much for the help on this :)

This is a useful dockerfile if you're on Apple Silicon and want to test older versions of Swift:
FROM swift:5.6-focal as swift5.6

WORKDIR /build

# Cache dependencies
COPY ./Package.* ./
RUN swift package resolve

COPY . .
RUN swift test --parallel

FROM swiftarm/swift:5.5.3-debian-buster as swift5.5

WORKDIR /build

# Cache dependencies
COPY ./Package.* ./
RUN swift package resolve

COPY . .
RUN swift test --parallel

FROM swiftarm/swift:5.4.3-focal-multi-arch as swift5.4

WORKDIR /build

# Cache dependencies
COPY ./Package.* ./
RUN swift package resolve

COPY . .
RUN swift test --parallel

FROM swift:latest

WORKDIR /build

# Make sure all stages actually run
COPY --from=swift5.6 ./build ./build-5.6
COPY --from=swift5.5 ./build ./build-5.5
COPY --from=swift5.4 ./build ./build-5.4

repo: GraphQLSwift/Graphiti

license: mit


text:
Issue #83

Maybe this'll build the docker image.

Try http://www.appveyor.com/

repo: GrappigPanda/notorious


text:
build!: v2 rho prepare

Description

bump cosmos-sdk to v0.46.x ( currently v0.46.0 )
remove swap functionality ( circuit breaker enabled and deprecated on cosmos-hub )
bump package name to liquididty/v2

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5afef73). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #15   +/-   ##
=========================================
  Coverage          ?   24.13%
=========================================
  Files             ?       39
  Lines             ?    11289
  Branches          ?        0
=========================================
  Hits              ?     2725
  Misses            ?     8264
  Partials          ?      300

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 5afef73...f474dc4. Read the comment docs.

Hi @dongsam, can you please bump to sdk 0.46-rc1 ? we need this for rho, Thank you!

Hi @yaruwangway, I just released v2.0.0-rc1 which is based sdk 0.46.0-rc1

First of all, we released v2.0.0-rc3 based on the PR branch. We will release official v2.0.0 after confirming that there is no conflict or issue with other modules in the Rho upgrade PR

https://github.com/Gravity-Devs/liquidity/releases/tag/v2.0.0
final v2.0.0 released, which is using cosmos-sdk v0.46.0

authors: codecov-commenter dongsam

repo: Gravity-Devs/liquidity


text:
测试有问题

请看图

没安装selenium这个包，试试pip install selenium==3.141

安装好selenium包后，运行又有错误。
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 108, in execfile
exec(compile(f.read(), filename, 'exec'), namespace)
File "C:/Users/Administrator/.goldminer3/projects/e557dbd9-e743-11e9-acce-00ff1c4aa94a/main.py", line 7, in
benchmark='hs000300')
TypeError: get_strategy() got an unexpected keyword argument 'benchmark'

Md还没完全更新，已更新示例。

我呢是非常想要你这个包，但是测试多次，都无法运行。
错误如下：
AttributeError: 'NoneType' object has no attribute 'quit'

你可能没安装好chrome和chromedriver，版本更新后已经有邮件反馈可用，如果你用不了以后麻烦截下图给你的运行环境。

repo: GraySilver/wencai


text:
2.8 Pre-release bugs

HQM Questbook
The "In of the Prancing Pony" should read "Inn of the Prancing Pony"
Also in that quest, the location point for Ethan is set for upstairs and should be near him.

HQM Questbook
Maybe you could write this blurb in the quest "Choose Wisely"
The fate of Middle Earth hangs in the balance and it is up to you to choose a side  -  forever leaving your imprint in the world of Arda.

HQM Questbook
(My fault hehe)
Quest - "To Osgiliath"
There should be three tasks - unfortunately you will need to re-do the tasks because the one that needs to be added is first. It will confuse players if we don't change this...I am so sorry.

Location Task
Title: Commander of the South Army
Location: 85625 67 63440

Location Task
Title: Finding a Scout
Location: 79667 64 65655

Location Task
Title: Supply Locations
Crate 1: 79547 69 65599
Crate 2: 79731 67 65773
Crate 3: 79561 65 65939

HQM Questbook
Quest - Festival of the Dancing Fireflies
Location is wrong and up in the air :(
Sky Ritual
Location: 55082 69 22236

HQM Questbook
Quest - The Stage is Set

Reducing Threat
Location task: Mount Doom 92691 115 60651

Power of Mount Doom
Detection task: 0/1 palantir shard

Informing the Order
Khamul Location: 67731 60 21148

NPC quest: Job Board - Bree/Archet

NPC (Sybilla Lytton) asks you to kill pigs but then the quest log says warg fur.
NPC (Philippa Sadler) asks you for Orc bones but the quest log says raw porkchop

All HQM corrections made, NPC stuff is all that remains

HQM Job Board - Eriador
"Trying to Leave"
Dwarf Camp has no coords

Alright, fixed all of the job board quests to reflect the proper trigger for availability, also corrected the coords that were missing in HQM.

Done and Done!

repo: GreatOrator/TolkienCraftII-Map


text:
🛑 Server Gaming is down

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

HTTP code: 403
Response time: 1801 ms

Resolved: Server Gaming is back up in 71ce98d after 3 minutes.

repo: GreathostRo/upptime


text:
🛑 Server Ultra is down

In 8af7bb6, Server Ultra (https://ultra.greathost.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Server Ultra is back up in 84db0ef after 2 minutes.


text:
🛑 Server Ultra is down

In 75d8853, Server Ultra (https://ultra.greathost.ro) was down:

HTTP code: 403
Response time: 1532 ms

Resolved: Server Ultra is back up in a5435b0.


text:
🛑 Server Ultra is down

In 8d564fd, Server Ultra (https://ultra.greathost.ro) was down:

HTTP code: 403
Response time: 1281 ms

Resolved: Server Ultra is back up in 58892d8 after .


text:
🛑 Server Gaming is down

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

HTTP code: 403
Response time: 7876 ms

Resolved: Server Gaming is back up in 97ac630 after .


text:
🛑 Server Gaming is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Server Gaming is back up in 44eff41 after 5 hours, 34 minutes.


text:
Research into Intel XEON emissions with different models

What: Generate some data regarding emissions for the same chip/util across different models.
Why: So we can start rigorously comparing data from multiple models
SoW:

[ ]  Generate 3 simple IMPLs that represent 1hrs worth of computation on an Intel Xeon (or some common sku).
[ ] Have 3 impls, one for low utilization (hovering around 15%), another for medium (hovering around 50%) and one for high (hovering around 90%).
[ ] Run the impls through the Boavista CPU. Boavizta Cloud and CCF models to see how they rack up.
[ ] On the cloud and CCF models you need to pick a VM which has the same chip across all 3 clouds.

Deliverable:

A table that looks somewhat like this:

Sku
Model
Vendor
10%
50%
90%

Intel Xeon (some model)
Boavizta Cloud
GCP
X mWh
X mWh
X mWh

Intel Xeon (some model)
Boavizta Cloud
Azure
X mWh
X mWh
X mWh

Intel Xeon (some model)
Boavizta Cloud
AWS
X mWh
X mWh
X mWh

Intel Xeon (some model)
CCF
GCP
X mWh
X mWh
X mWh

Intel Xeon (some model)
CCF
AWS
X mWh
X mWh
X mWh

Intel Xeon (some model)
CCF
Azure
X mWh
X mWh
X mWh

Intel Xeon (some model)
Bovizta CPU
---
X mWh
X mWh
X mWh

A useful tool to find micro arch from instance type for AWS: https://instances.vantage.sh/

As discussed today the CPU we'll be comparing against is XEON Platinum 8259 - Cascade Lake

Hi Asim
Here's the table for the Intel Xeon Platinum 8529 (Cascade lake)
Please note that the Boavizta CPU model, passing the processor name (row 2), is falling back to some default values because it doesn't have actual data to use, so this should be considered unreliable and maybe omitted - left it in here so you can make that decision yourself!

Sku
Model
Vendor
CPU energy @ 10% (kwh)
CPU energy @ 50% (kwh)
CPU energy @ 100% (kwh)

m5n.large
Boavizta Cloud
AWS
0.0222
0.0278
0.0229

Xeon Platinum 8259
Bovizta CPU
n/a
0.2500
0.5555
0.8333

m5n.large
CCF
AWS
0.0019
0.0046
0.0079

n2-standard-2
CCF
GCP
0.0019
0.0043
0.0073

D2 v4
CCF
Azure
0.0019
0.0046
0.0079

Thanks @jmcook1186
Running through some back of the napkin calculations, so the TDP of the Intel Xeon Platinum 8529 is about 210W.
If running at 1 hr then that's 210 Wh = 0.21 kWh.
So... given it has 24 cores and 48 threads. At 100% that's about 0.004375 kWh per vCPU per hour running at 100%.
If the m5n.large is a single core/2 vCPU instance then at 100% =~ 0.00875 kWh. Which is close to what it's reporting on the CCF front so that looks good!
The Boavizta Cloud doesn't make a lot of sense to me however. the energy usage isn't going up, in fact it goes down from 50% to 100%! Are you using the Boavizta API or our Boavizta IMP? Could you try the API directly to make sure it's not something wrong with our logic?
For row 2, is this just a name mapping thing - would it work if we entered whatever name they use for "Intel Xeon Cascade Lake"

Hi @jawache - thanks for catching the error in the Boavizta Cloud row - the 100% value was a typo, now corrected.
Using the API directly yields very similar values for 10% and 100% utilization, but strangely the result for 50% utilization == result for 100% utilization on the API... (i.e. both 50% and 100% utilization yield a result of 0.0555 kwh).

So assigning this for now to @gnanakeethan to

[ ] Investigate and verify the differences between Boavizta Cloud API vs our Implementation results.
[ ] Clarify why Boavizta CPU is returning the above data? Cascade Lake is a very popular chip, if we need to enter a different set of characters the represent cascade lake lets do so.

Results

Quite significant differences between models and approached.
My Learnings:

Mapping chips models -> instance types -> raw data is very challenging. Harder than actually getting the numbers was just figuring out if the models supported certain instance types/chips.
Each model does something different when they see an instance type/microarch they don't know. CCF underestimates/Boavizta, unsure, confusing numbers.
The raw data all these models are based off is 2 years old now, modern families of chips are not represented at all which means.

Age of data sets is inconsistent.

Azure, AWS, GCP instance types are inconsistent (from different time period).
Different granularity for different cloud providers. Some cloud providers, say exactly which chip they are using, others say roughly.
CCF doesn't recognize new instances.
Document this heavily, guides - model guides.

@jawache I have added documentation specific to the docs/implementations folder on ccf-imp branch with #74

Closing and creating a new ticket to discuss what the guides/readme should contain.

authors: gnanakeethan jawache jmcook1186

repo: Green-Software-Foundation/ief


text:
Replace heavy mathjs dependency with a lighter one

Removed MathJS to make the package lighter

I completely understand the need  for a smaller math parser - it is large.
However I'm also not overly keen on moving to something with a different syntax - With expr-eval it seems that you have to create a Parser object for each use, then evaluate it separaretly.
That's not to say I'm completely averse to it.
I'm wondering if it may be better to use the reduced version of MathJS (https://github.com/josdejong/mathjs-expression-parser), which would keep the syntax the same and only mean a change in the NPM include.
Also, looking at the package sizes, it looks like reduced MathJS (41kb) is smaller that expr-eval (68kb).

Does expr-eval provide any benefits over the reduced MathJS package?

I don't think so, I just wanted something similar to eval to remplace MathJS so the package is lighter. Though I think it's a good idea to add a reduced version of MathJS to make it lighter.

I've created another pull request (#87) which uses the reduced version of MathJS, to keep the syntax consistent.
Although it wasn't used, thank you for your contribution. It's really appreciated.

Just to let you know, I've released a patch version that uses the reduced size version of MathJS, which halves the package size: https://bundlephobia.com/result?p=rpg-dice-roller@3.1.4
There's still some bundle size changes I want to make, but it's difficult at the moment when I'm having to bundle UMD files for nodeJS. Once NodeJS fully supports ES imports then I can scrap those, which will reduce the filesize even more.

authors: GreenImp yunseok

repo: GreenImp/rpg-dice-roller


text:
Draft book chapter

Starting a draft of the turing way book chapter on a google doc We will create a PR on the Turing Way at a later stage.

We should mine the raspberry discussion document from yesterday. I'll not link it here (this is public and we're supposed to wait until after CW23) but it's on slack

Of use: https://www.cdcs.ed.ac.uk/digital-humanities-climate-coalition

authors: andreww c-martinez

repo: GreenScheduler/cats


text:
implement square function

It'd be nice to have a function that would square whatever was passed in. Can someone write this please?
def square(x):
"""Returns the squared value of x
"""

Perhaps write some tests too?

Ill try this

authors: GregHilston mtnskiier

repo: GregHilston/github-tutorial-calculator


text:
Support for grouped DS4k with KickStands?

Hey Gregory, would be great if it could support the grouped devices of DS and Kickstands or build something like a light group in HA :)
Is this possible?
Thanks in advance,
Thomas

I'll look into getting this done sometime in the next week if things aren't too busy.  I only have one device though, so testing might be tough.

Great 😃
Another question, should it find the DS4K and the Kickstands right now?
As I have 1x DS4K and 2x Kickstands and only the DS is found. Is this how it should be? :)

@XRyu Sorry for the radio silence.  I'm looking into probably rewriting this so it better supports multiple devices/groups/etc.  When I get something up and going I'll send it your way and you can help test/give feedback if you're still willing/able.

@GregoryDosh great! I wish i would understand the development but i dont understand it that good and don't have much time to learn python (new job).
Another idea would be to use something like the source-attribute in media_player for input change, this would be really great, instead of using scripts to change the HDMI-Input

authors: GregoryDosh XRyu


text:
🛑 walletcheck API endpoint is down

In 3e8ac9d, walletcheck API endpoint (https://grinnode.live:8080/walletcheck/grin1zxwrf5yaxlyps4mpx3n7j9kp4su3gzgpdhfk2sgv56q0prcdlzls9e6e0y) was down:

HTTP code: 0
Response time: 0 ms

Resolved: walletcheck API endpoint is back up in 5ba0daa.

repo: Grinnode-live/upptime


text:
pdfx.sty:  error No color profile found to use for RGB screen colors..

Ao compilar localmente, o compilador retorna o erro descrito acima. Ele aponta para a linha 1303 do arquivo pdfx.sty, mas nada muito informativo se encontra ali.
Mais alguem com o mesmo problema?

Oi, Hudson!
Estava com o mesmo erro, mas como o pdf era gerado mesmo assim, fui deixando pra lá.
O problema foi resolvido quando instalei o pacote icc-profiles na minha distribuição Linux, como informado aqui:
https://tex.stackexchange.com/questions/380798/no-color-profile-found-to-use-for-rgb-screen-colors

@Rhalah valeu pelo retorno. Acessei o link. Parece ser isso mesmo que você descreveu. Minha distro não disponibiliza esse pacote.
Resolvi removendo o arquivo pdfx.sty.  Funcionando perfeitamente agora.

authors: Rhalah hbenevides


text:
🛑 Homepage is down

In d87660f, Homepage (https://www.dlya.top) was down:

HTTP code: 409
Response time: 7535 ms

Resolved: Homepage is back up in 3ffc4e5.

repo: Guangsudalao/uptime


text:
(Feature request) Bulk decompilation

Some sort of feature to decompile everything in a bytecode file back out to its original filenames (that is, if debug information is embedded in the bytecode) would be greatly appreciated for modding projects - as in this project's current state, it can't really be used to modify a game's code, only poke around it a bit. In a similar vain, I would also love to see a tool in the GUI that allows partial code changes to be made in the decompiler pane without having to fully decompile and recompile the entire game - as sometimes, functions cannot be decompiled to begin with (especially switch statements!) and have to be reversed by hand.

Well, as you can see, nothing here is really complete. There are a lot of missing features. I originally intended to try modding myself but I spent all my time working on those tools instead. This means those tools were never really used (to my knowledge) to create anything. All the features currently implemented are for me to explore and debug the tools.
That being said, I never implemented bulk decompilation because decompilation itself is incomplete. As you can see #5, a lot of work remains to make this 100% functional (loops especially).

repo: Gui-Yom/hlbc


text:
added flow

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

[ ] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

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

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

In the .gitignore file, there is no newline at the end of the file. It's a good practice to ensure that every file ends with a newline to avoid issues with some tools and version control systems.

In the .github/workflows/ai_check.yml file, change troublshooting to troubleshooting.

repo: GuillermoGaete/throttler-test


text:
Changing the attributes

I love your work and I want to replicate it for my research. Which file should I modify if I want different attributes from the one in the paper? For example, changing the skin complexion and also eye sizes

Same question....I want to swap attributes like jaw, hairline etc.


text:
[提议]Docker网页result直接输出m3u 和 txt

现在的result是一个HTML, 不能直接导入网址
建议直接输出m3u和txt

不太清楚你的问题描述，目前是支持输出m3u/txt文件和页面的

现时页面不是一个正规的m3u, 只是一个HTML, 不能直接在播放器导入
希望能够输出m3u/txt页面

你把地址复制到播放器试试，是可以播放的

提醒一下，地址后缀你如果添加了/result查看的是文件的文本内容，/log查看的是日志内容，播放器使用需要去除地址的/result

明白, 谢谢

repo: Guovin/TV


text:
Enable SSL for the connection

Fixes #6 for me
But I'm not sure if everyone else is using SSL-only connections, or if I'm just missing something in the Aptible configuration. So YMMV

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant dominics


text:
Added basic UI

Your console app should behave in the same way as it is in the example.
Create a app.rb file that will serve as your console app entry-point. It should have methods that do the following:

List all books.
List all people.
Create a person (teacher or student, not a plain Person).
Create a book.
Create a rental.
List all rentals for a given person id.

In your main.rb define the entry point, this will be a method called main that is invoked at the end of your file. This method should do the following:

Present the user with a list of options to perform.
Lets users choose an option.
If needed, ask for parameters for the option.
Have a way to quit the app.

Can u stop pushing to avoid invalidation @H-Ramalan, Your code is under review Please.

authors: H-Ramalan OLIPLICHE

repo: H-Ramalan/school-library


text:
后台 返回的 json 轮播 只有 一张图时， 无法禁止手指滑动图片

不让Indicator和不让滚动都可以通过属性做到， 但是唯独没有看到禁止用手去滑动该图片的事件啊， 就是说还是可以滑动， 由办法能解决这个问题吗？

这功能暂时没有,当初写的时候也没考虑~这个你可以自行Google,类似于'viewpager 禁止滚动'

能否告诉， 你图片的高度算法是什么
itemWidth * 360 * 1.0f / 640
这个和bb_scale属性有什么关联，
比如我现在高度想变成170px， 这个计算方法是什么

Demo中图片原始宽高640*360,根据图片比例和手机屏宽计算出高度,从而保证图片显示的正确性,不会被过多裁剪或者变形.
你想要170px的话~可以在设置xml中设置Banner高度170px,在代码设置下ImageView的高度为170px就可以了


text:
各位大佬，问下如何支持RTL布局？ 翻转的话，就不显示TAB文字了。

同上。

同上

在布局文件中新键 layout_tab 文件将原本最外层的 RelativeLayout 布局 改为 ConstraintLayout 即可显示 tab 文字 但滑动时依然是从左往右 需要改变滑动方向

authors: amosxb qvitasoyq


text:
🛑 Telly is down

In 47a1bec, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 197bb00.

repo: HDVinnie/TrackerHub


text:
🛑 Telly is down

In 24885c4, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 19ffa17.


text:
⚠ Telly has degraded performance

In 485e5eb, Telly ($TLY) experienced degraded performance:

HTTP code: 200
Response time: 1447 ms

Resolved: Telly performance has improved in 92ef4cb.


text:
🛑 SkipTheCommericals is down

In b5fef6a, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in c5095d0.


text:
🛑 AlphaRatio is down

In 85151f4, AlphaRatio ($AR) was down:

HTTP code: 502
Response time: 267 ms

Resolved: AlphaRatio is back up in 1fd01ac.


text:
🛑 SkipTheCommericals is down

In 95d56c5, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in 36609eb.


text:
🛑 SkipTheTrailers is down

In ee64a63, SkipTheTrailers ($STT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheTrailers is back up in 747dc2d.


text:
⚠ SceneTime has degraded performance

In cda9a8d, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1381 ms

Resolved: SceneTime performance has improved in b3c29f3 after 8 minutes.


text:
🛑 Redacted is down

In e2775c6, Redacted ($RED) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Redacted is back up in 1c3dca5 after 6 minutes.


text:
⚠ SceneTime has degraded performance

In 7a794e3, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1318 ms

Resolved: SceneTime performance has improved in 60f0736 after 6 minutes.


text:
🛑 Telly is down

In 271d83a, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 698ac55.


text:
⚠ Anthelion has degraded performance

In bee3cb4, Anthelion ($ATH) experienced degraded performance:

HTTP code: 200
Response time: 6774 ms

Resolved: Anthelion performance has improved in 6a36dac.


text:
🛑 SkipTheCommericals is down

In efd9324, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in da05317.


text:
🛑 SkipTheCommericals is down

In 07513b7, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in 9a99673.


text:
Dataset Statistics.

Get statistics per relation type for our train and val sets.

This is done

repo: HEmile/iswc-challenge


text:
🛑 ivm-meyer is down

In eec9d03, ivm-meyer (https://ivm-meyer.de) was down:

HTTP code: 503
Response time: 5664 ms

Resolved: ivm-meyer is back up in 79d0d94.

repo: HINTERLAND-software/uptime


text:
Add support for NamedTuples, support NumPy 1.25 (fixes #597)

The functions in numpy.linalg which returned tuples in version <= 1.24 have switched to using a different NamedTuple type for each function. To support this I've added the necessary Box and VSpace registrations.

Thanks for looking into this! Could you maybe also release a new version 1.6 on pypi to make these changes accessible for dependent projects?

Yes, will do.

Should be done now, lmk if you have any issues.

authors: fjosw j-towns

repo: HIPS/autograd


text:
Hide credential

Issue that this pull request solves
Closes: #521
Proposed changes
Have added .env files and hidden all the credentials to it. All credential and backend API data is secure.
Brief description of what is fixed or changed
Moved the URL's and keys to .env files
Types of changes
Put an x in the boxes that apply

[x] Bugfix (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)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes does not break the current system and it passes all the current test cases.

Screenshots
Please attach the screenshots of the changes made in case of change in user interface
Other information
NOTE: Remove the credentials from variables.json from config folder as now it is of no use and it's not required as the credentials is shifted to .env files
Also add the .env files to .gitignore and update the document for other users to access the API links for backend.

Ok Sure, I'll make the required changes

I've made the required changes @Kajol-Kumari

@Kajol-Kumari ,
all the changes required were made and variable.json is too deleted.

repo: HITK-TECH-Community/Community-Website


text:
Could QuickInfo add Opcode and Description info

QuickInfo tooltip offers the following feature,

Could QuickInfo support the following info(It is from https://github.com/HJLebbink/asm-dude/wiki/IMUL ),

I had two reasons not to add that info in the performance info.

I cannot do that without handpicking the descriptions and opcodes for each combination of instruction and operand. The performance info is from Agner Fog and the descriptions are from the wiki. These sources are not very comparable. I think it would be difficult to figure out (with some Python) which description should be matched to a performance line. E.g. line with IMUL r8 and IMUL m8 should have the same description and IMUL r,r would be described differently.

Other issue is that there is no obvious place to put that description on a line. The descriptions of IMUL are short compared to those of others.

If you have an idea how to solve both issue, do let me know. I do think that having the description would be useful.

I think we don't need handpick those info. AsmDude can add option in Visual Studio's Options window, which just like,

When "Performance" is enabled, Quickinfo displays performance info. When "Description" is enabled, Quickinfo displays the descriptions are from the wiki.
There are 1457 instructions in the wiki, which descriptions are the same with Intel's manual,e.g.,

Sorry for the unrelated question, but my AsmDude doesn't How to show the opcode when I hover over an instruction. It does show pretty much everything else. Anybody knows if there's an option that I have to enable for this? I can't figure it out.

authors: HJLebbink KeyC0de matt-elson

repo: HJLebbink/asm-dude


text:
Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.

Version
1.0.0
Installation Type
Official Docker Compose
Service Name
DongTai-Core
Describe the details of the bug and the steps to reproduce it
windows平台上运行自动安装时报错找不到agent.jar，路径处理未兼容windows
PS E:\work\dongtai> java -jar .\agent.jar -m install -p 26420
[cn.huoxian.dongtai.iast] trying attach dongtai to process 26420, agent address is /E:/work/dongtai/agent.jar
[cn.huoxian.dongtai.iast] attach failed
com.sun.tools.attach.AgentLoadException: Agent JAR not found or no Agent-Class attribute
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(HotSpotVirtualMachine.java:117)
at com.secnium.iast.agent.AttachLauncher.attach(AttachLauncher.java:21)
at com.secnium.iast.agent.Agent.main(Agent.java:41)
engine install success for pid: 26420
Additional Information
No response
Logs
No response

Thanks for the feedback, the test recurrence has been arranged.

We expect to fix this issue in version 1.0.4

repo: HXSecurity/DongTai


text:
READ ME file, anyone?

We still need to write a nice READ ME file.
Any volunteer? 🤓

I will try my best to do it 🤓

and for what exaclty. we haven't recieved any project yet. readme.md files are used to write something about the project and participants on the project.

https://github.com/HackYourFutureBelgium/workflows/blob/master/deliverables/group-introduction-repo.md
Check the assignment carefully.
We need to make an READ ME file explaining the purpose of our project and also briefly introducing members of the group.
Our coaches explain and mention it so many times on slack..

I finished writing the README file you can check it now

I finished writing the README file you can check it now

authors: GabriellaLohy emran-ai saidakf


text:
Update ko-kr.xml

Dear Haato3o
Thanks for your works

Dear Haato3o Thanks for your works

Agreed. This is an incredible project and tool! Very excited for it to get a beta release in the future!

authors: WetU conchors


text:
+がマイナスの扱いになっている。

操作手順

〜したら
〜になった

本来の想定

〜したら
〜になってほしい

操作環境

OS
OSバージョン
ブラウザ
ブラウザバージョン

// return decimalPointCalculate(f1.add(f2), decimalPoint)
return decimalPointCalculate(f1.add(f2), decimalPoint)
ここがsubtractになっていたため、addに訂正した。


text:
Logout using ng2-idle

My problem is that when click on the logout button ng2-idle continues working. And to try to solve this problem I set again the setIdle and setTimeout functions for 1 second.
However, when the user is transferred to the login screen, the app takes 1 second to give the timeout.
I like to know if have any way of forcing the timeout or end ng2-idle after click the logout button that call logout() function.
 import {Component} from '@angular/core';
 import {Router} from "@angular/router";
 import {Http, Headers} from "@angular/http";
 import {NgClass} from '@angular/common';
 import {Observable} from "rxjs/Observable";
 import 'rxjs/Rx';
 import {HeaderService} from './header.service';
 import {Idle, DEFAULT_INTERRUPTSOURCES} from 'ng2-idle/core';

 @Component({
      selector: 'my-header',
      templateUrl: './js/app/header/header.component.html',
      styleUrls: ['./js/app/header/header.component.css']
 })

 export class HeaderComponent {
      nome = localStorage['nome'];
      constructor(private _router: Router, private _http: Http, private _headerService: HeaderService, private idle: Idle) {
           idle.setIdle(5);
           idle.setTimeout(1800);
           idle.setInterrupts(DEFAULT_INTERRUPTSOURCES);

           idle.onTimeoutWarning.subscribe((countdown:number) => {
             console.log('TimeoutWarning: ' + countdown);
           });

           idle.onTimeout.subscribe(() => {
             console.log('Timeout');
             localStorage.clear();
             this._router.navigate(['/auth', {sessionExpirate: 'true'}]);
           });
           idle.watch();
      }

      logout() {
           this.idle.setIdle(1);
           this.idle.setTimeout(1);
           this.idle.setInterrupts(DEFAULT_INTERRUPTSOURCES);
           this._headerService.exit()
                .subscribe(
                     data => {
                          this.idle.onTimeout.subscribe(() => {
                               console.log('Timeout');
                               localStorage.clear();
                               this._router.navigate(['/auth']);
                     },
                     error => console.log(error)
                )}
           )
      }
 }

I got to work, follows the change in the logout() function:
 logout() {
     this.idle.stop();
     this._headerService.exit()
         .subscribe(
             data => {
                 localStorage.clear();
                 this._router.navigate(['/auth']);
             },
                 error => console.log(error)
         )
 }


text:
First time selecting date requires two clicks

When I select a date from the calendar for the first time, the first click on the date doesn't trigger the event and thus requiring another click to trigger the event. I cross checked with the project example and this doesn't happen with the examples you have. How can I prevent this behavior? Usually such behavior  with onClick event can be prevented by preventDefault method. #help #discussion

The cause of the issue unknown but it is not happening anymore ...


text:
Update Factorial

What the program do ?

In what programming language it is written?

This pull request contains conflicts. Please fix it and reopen


text:
在配置项可配置是否自动下载。 开启后，下载下来的图片打不开，不知道啥原因，

'download' => [
'image'         => false,
'voice'         => false,
'video'         => false,
'emoticon'      => true,
'file'          => false,
'emoticon_path' => $path.'emoticons',
],

image => true
最近的反馈来看，有可能微信修改过图片的返回值导致下载失败

这个能处理吗大神

authors: 529834149 HanSon fywtat

repo: HanSon/vbot


text:
Error when modifying dependencies list

I encountered this when I was editing the dependencies list of this version. I deleted 2 or 3 entries, then I added 2 new entries. After pressing Save, it did not save and an error occurred.

hmm.. after removing an entry for LM Items and then pressing save, it saved. I just added that dependency afterwards and that worked.

I don't keep logs so this is impossible for me to repo. if this occurs again, please note the time and check your browser console for the response of the network call and include it.

repo: HangarMC/Hangar


text:
Persist mainpage search filters when going back

Is your feature request related to a problem?
Currently, pressing the back button in your browser to return to the main page resets any entered search keywords and the page number.
Describe the solution you'd like.
Entered search terms and the page number should be part of the URL, so that the back function works properly.
Describe alternatives you've considered.
Opening results in a new tab every time.
Other
No response

maybe is fixed by having the filters be persisted in the url? maybe can be done together with #833

authors: Malfrador MiniDigger


text:
A Database Merging Problem

Hangfire.Mongo:0.7.22
The steps are as follows：
1.There are multiple working containers running on k8s.
2.Some unexpected databases were deleted.
The following error occurred：
2022-12-21 03:03:19.5075 INFO Migration failed in Hangfire.Mongo.Migration.Steps.Version13.SumCounters 2022-12-21 03:03:19.5075 INFO    at Hangfire.Mongo.Migration.Strategies.MongoMigrationStrategy.ExecuteMigration(IMongoDatabase database, MongoSchema fromSchema, MongoSchema toSchema)    at Hangfire.Mongo.Migration.Strategies.DropMongoMigrationStrategy.ExecuteMigration(IMongoDatabase database, MongoSchema fromSchema, MongoSchema toSchema)    at Hangfire.Mongo.Migration.Strategies.MongoMigrationStrategy.Execute(MongoStorageOptions storageOptions, IMongoDatabase database, MongoSchema fromSchema, MongoSchema toSchema)    at Hangfire.Mongo.Migration.MongoMigrationManager.Migrate(MongoBackupStrategy backupStrategy, MongoMigrationStrategy migrationStrategy)    at Hangfire.Mongo.Migration.MongoMigrationManager.MigrateIfNeeded(MongoStorageOptions storageOptions, IMongoDatabase database)    at Hangfire.Mongo.MongoStorage..ctor(MongoClient mongoClient, String databaseName, MongoStorageOptions storageOptions)    at Hangfire.Mongo.MongoStorage..ctor(MongoClientSettings mongoClientSettings, String databaseName, MongoStorageOptions storageOptions)

@pughua,
Thanks for posting.
I'm not sure how replicate this. Are you saying the database was deleted?
Thanks

@gottscj
Yes, the database has been deleted. Mongodb automatic reconstruction.

@pughua,
it seems the data is corrupted or not all data has been reconstructed. Are you expecting the node to run migrations?

closing due to inactivity

authors: gottscj pughua


text:
🛑 Portal is down

In 2e61428, Portal (https://scratch-wiki.info) was down:

HTTP code: 508
Response time: 1330 ms

Resolved: Portal is back up in a9d0b77 after 58 minutes.


text:
🛑 Portal is down

In d36355c, Portal (https://scratch-wiki.info) was down:

HTTP code: 508
Response time: 1095 ms

Resolved: Portal is back up in 1c01cfa after 16 minutes.


text:
🛑 Hungarian is down

In 5930e2d, Hungarian (https://hu.scratch-wiki.info) was down:

HTTP code: 508
Response time: 379 ms

Resolved: Hungarian is back up in 893f76f.


text:
🛑 English is down

In cc67430, English (https://en.scratch-wiki.info) was down:

HTTP code: 508
Response time: 1157 ms

Resolved: English is back up in 8ef0c99 after 8 minutes.


text:
🛑 Indonesian is down

In 466a8cd, Indonesian (https://id.scratch-wiki.info) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Indonesian is back up in 3519e63 after 15 minutes.


text:
🛑 AI对话 is down

In 20baef0, AI对话 (https://haoqi7-question.hf.space/) was down:

HTTP code: 503
Response time: 230 ms

Resolved: AI绘画 is back up in dd97ef8 after 189 days, 12 hours, 22 minutes.


text:
🛑 Happy Vibes Bot 5 is down

In 2e8ea65, Happy Vibes Bot 5 ($BOT5) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 5 is back up in 1e86123.

repo: Happy-Vibes-Bot/status


text:
🛑 Happy Vibes Bot 5 is down

In 51972bc, Happy Vibes Bot 5 ($BOT5) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 5 is back up in 51ca5fb.


text:
🛑 Happy Vibes Bot 1 is down

In e4d939b, Happy Vibes Bot 1 ($BOT1) was down:

HTTP code: 404
Response time: 4252 ms

Resolved: Happy Vibes Bot 1 is back up in 20d0819.


text:
🛑 Happy Vibes Bot 3 is down

In 8ba6df2, Happy Vibes Bot 3 ($BOT3) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 3 is back up in 3755d7f.


text:
🛑 Happy Vibes Bot 1 is down

In d4d58c3, Happy Vibes Bot 1 ($BOT1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 1 is back up in f4d8515.


text:
🛑 Happy Vibes Bot 4 is down

In d1e005c, Happy Vibes Bot 4 ($BOT4) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 4 is back up in 2f2068c.


text:
🛑 Happy Vibes Bot 3 is down

In 6f2d5c1, Happy Vibes Bot 3 ($BOT3) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 3 is back up in f87519b.


text:
🛑 Happy Vibes Bot 2 is down

In 5fb38f7, Happy Vibes Bot 2 ($BOT2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 2 is back up in 907ea17.


text:
General corrections, bug fixes, and code simplification

I simplified a bit the code and standardized it using native Node functions over external libraries such as BCrypt as it tends to break if you run it in different architectures that are not AMD64 (ELF header errors) or when you are using it in a cross-architecture way like having a docker container running as AMD with a volume in an M1 MacBook.
Also standardized the use of Promises for non-promisified functions like randomBytes and pbkdf2 using Node's native util package.
I also fixed a bug with the header validation logic that wasn't splitting the Bearer token from the Authorization header so it would always give us the "HDB token error" message, this logic was also missing the hashing of the received token to match against the one in DB, so I took the opportunity to use the GH token received since it wasn't being used in the response.
This is a summary of what's been done:

Remove bcrypt as it often breaks if you change archs (ARM vs amd64)
Use native Node.js crypto functions to simplify code
Remove callbacks and standardize Promise usage with Promisify
Remove unused dependencies and parameters
Remove the dead reply line
Use GH token to generate session
Hash the received token before matching in DB
Fix header validation logic

These changes look good. Thanks for the improvement!

authors: kevashcraft khaosdoctor


text:
License

Hey,
I'm wondering about license of this provider. I have some plans to maybe use it, propably also fork and change some small things. I'm not sure that I'm allowed or not. Can I ask about adding a license file on the github level?:)

Hi Vallher, thanks for rasing this. I have added an MIT licence hope this is helpful to you?
Id be interested to see what you get up to with this. I tried to encourage AppD to work on config as code as their competitors support this e.g. New Relic. If we get enough users wanting this we may have more leverage.
Harry

authors: HarryEMartland Vallher


text:
Fix for missing org.apache.http.legacy library dependency

Fixes #24

@HarelM could you just glance over this and make sure I haven't made a silly mistake? :)
If it's all good, we can merge and close this.

Looks fine to me :-)

authors: HarelM RaddishIoW


text:
Skip deleting trunk branch

Hi! In my case, I have some PRs from main -> dev branches for keeping those up to date.
Is it possible to wrap the entire contents below in a condition like (branch != trunk_branch)
https://github.com/HaywardMorihara/gh-tidy/blob/b1c79a6e1b3d9fa3b7273a55df4c9da2da191d05/gh-tidy#L136-L144

Hey!
So you're saying you sometimes have branches where you're merging changes from main (the trunk branch) into a development branch?

yes, correct.
just to keep dev synchronized

Oops, yup that's what I meant haha
Okay, yeah I think that makes sense. I might be able to get to this soon, but feel free to push up a pull request with the change.
Long-Term Though-To-Self: Would be nice to be able to configure "protected branches" for your repo that would never be automatically deleted

Yeah, protected-branch support sounds great (especially if it is configurable through a flag)
I have created #42 for trunk branch check in the meantime

Approved & merged! Thank you!

authors: HaywardMorihara pritamrungta

repo: HaywardMorihara/gh-tidy

license: Unlicense


text:
Readthedocs issue with Emmental

Describe the bug
Fix the readthedocs issue with Emmental
To Reproduce
There are some sphinx.ext.autodoc.importer._MockObject in the current readthedoc.
Expected behavior
Have the correct inheritance information.
See https://github.com/HazyResearch/fonduer/pull/329 for context on this bug.

This was just merged: https://github.com/readthedocs/sphinx-autoapi/issues/183.
So, we may be able to do some workaround now.

I've just acknowledged this issue myself.
This issue https://github.com/snorkel-team/snorkel/pull/1274 may be relevant?

mocks and type hints don't work together very well (agronholm/sphinx-autodoc-typehints#70)

Is this still an issue?
I can't find any _MockObject in the readthedocs. (see the search result at https://readthedocs.org/projects/fonduer/search/?q=_MockObject)

authors: HiromuHota SenWu lukehsiao

repo: HazyResearch/fonduer


text:
Make dropdown values more compact

The fill/outline valueVariants on the Dropdown have lots of padding, and have a large font size. The difference between the height of the three variants is huge. To get these closer in-line with each other and the design

reduce the font size
reduce the padding
add border to fill variant so it matches the size of the outline

Current:

Design:

Hey there can I contribute to this

repo: Headstorm/foundry-ui


text:
build: prepare for kotlin DSL migration

Most of the changes required to migrate the build scripts to Kotlin DSL can be implemented up front and as supported in the Groovy DSL. Update the Gradle build script and settings to

Use " instead of '
Use parentheses for function calls
Exclude parentheses for core plugins, as these will be treated differently
Use task prefix to differentiate task config vs plugin config
Use .set() for some config known to use Kotlin val

TIS21-SHED

@JosephKelly FYI, we can do a lot of the work upfront without having to actually switch to Kotlin. I'm thinking this is probably the easiest way to start, get all repos standardised and then big-bang move everything to Kotlin to avoid haven't a mix of DSLs.
This is the post-migration part: https://github.com/Health-Education-England/tis-trainee-details/compare/build/migrateGradleToKotlinDsl...build/migrateGradleToKotlinDsl2?expand=1


text:
Multiple errors for swift 3

Multiple build time errors

Referred previous issue: https://github.com/Hearst-DD/ObjectMapper/issues/579
I'm using v1.5.0 and Xcode 8.3.3
I've cleaned the derived data folder and also cleaned project the tried building, still getting the same issue. Any suggestions?

1.5.0 doesn't support Swift 3. Use at least 2.0.0 version for Swift 3

authors: Ssrana devxoul

repo: Hearst-DD/ObjectMapper