text:
Exception in thread "main" com.google.api.gax.rpc.ResourceExhaustedException: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'speech.googleapis.com/default_requests' and limit 'DefaultRequestsPerMinutePerProject' of service 'speech.googleapis.com' for consumer 'project_number:

In which file did you encounter the issue?
QuickSample.java

Did you change the file? If so, how?
No

Describe the issue
I am getting the above mentioned issue when I try to run this programme. The detailed exception is pasted below

Jun 12, 2019 12:53:03 PM com.google.auth.oauth2.DefaultCredentialsProvider warnAboutProblematicCredentials
WARNING: Your application has authenticated using end user credentials from Google Cloud SDK. We recommend that most server applications use service accounts instead. If your application continues to use end user credentials from Cloud SDK, you might receive a "quota exceeded" or "API not enabled" error. For more information about service accounts, see https://cloud.google.com/docs/authentication/.
Exception in thread "main" com.google.api.gax.rpc.ResourceExhaustedException: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'speech.googleapis.com/default_requests' and limit 'DefaultRequestsPerMinutePerProject' of service 'speech.googleapis.com' for consumer 'project_number:764086051850'.
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:57)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:72)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:60)
at com.google.api.gax.grpc.GrpcExceptionCallable$ExceptionTransformingFuture.onFailure(GrpcExceptionCallable.java:97)
at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1056)
at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1139)
at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:958)
at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:748)
at io.grpc.stub.ClientCalls$GrpcFuture.setException(ClientCalls.java:507)
at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:482)
at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:699)
at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:397)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459)
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:584)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112)
at com.google.cloud.speech.v1.SpeechClient.recognize(SpeechClient.java:244)
at com.google.cloud.speech.v1.SpeechClient.recognize(SpeechClient.java:208)
at com.example.speech.QuickstartSample.main(QuickstartSample.java:62)
Caused by: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'speech.googleapis.com/default_requests' and limit 'DefaultRequestsPerMinutePerProject' of service 'speech.googleapis.com' for consumer 'project_number:764086051850'.
at io.grpc.Status.asRuntimeException(Status.java:532)
... 23 more
I set the credential file as well as suggested in the docs
export GOOGLE_APPLICATION_CREDENTIALS=/Users/asurjit/Downloads/Amar1979-ba0acd0298c9.json
Further, I ran the gcloud auth list command as well and the service account is active.
bash-3.2$ !539
gcloud auth list
Credentialed Accounts
ACTIVE  ACCOUNT

  asurjit@amar1979.iam.gserviceaccount.com

To set the active account, run:
$ gcloud config set account ACCOUNT
Please suggest what I am doing wrong over here.

Hi @asurjit79,
It looks like you are using user credentials. You can use gcloud auth activate-service-account [ACCOUNT] --key-file=KEY_FILE to specify a service account instead.

Thanks @Kurtisvg for your response. I used that as well and set the account name to my service account using the above mentioned command but it didn’t make much difference when I got the same error still.

@asurjit79 Did you still get the same message about using user credentials vs service account?
And just to confirm, you are referring to java-docs-samples/speech/cloud-client/src/main/java/com/example/speech/QuickstartSample.java?

yes @kurtisvg, we are referring about QuickstartSample.java itself.
I think, the error message was same for both user credentials and service account but I will give it one more try.
And would like to paste bit more information about the earlier reply.
bash-3.2$ gcloud auth activate-service-account asurjit79@feisty-etching-243514.iam.gserviceaccount.com --key-file=/Users/asurjit/Downloads/feisty-etching-243514-50537d59011c.json
Activated service account credentials for: [asurjit79@feisty-etching-243514.iam.gserviceaccount.com]

Ok, so I checked the project_number in your original error, and the problem is definitely related to the wrong credentials. So let's try to debug what is going wrong.
How are you executing this code? Can you add the following lines at the top of the QuickStart:
GoogleCredentials credentials = GoogleCredentials.fromStream(new FileInputStream("/path/to/credentials.json"));

// Instantiates a client
try (SpeechClient speechClient = SpeechClient.create(credentials)) {

This should (hopefully?) be a full proof way to make sure we are getting the correct credentials.

Thanks @kurtisvg. SpeechClient.create method is complaining as it is not able to accept GoogleCredentials but looking for SpeechSettings.
"The method create(SpeechSettings) in the type SpeechClient is not applicable for the arguments (GoogleCredentials)"

I am running this from the eclipse IDE itself..anything different I need to use

Nope the IDE is fine - one easy mistake to make is setting environment variables in a terminal and then not getting them then you run your code in Eclipse. You have to specify them in the IDE as shown in this SO post.
I messed up on the snippet I gave you before, the Speech library specifies credentials like this:
    GoogleCredentials credentials = GoogleCredentials.getApplicationDefault();
    System.out.println(credentials);

    SpeechSettings speechSettings =
        SpeechSettings.newBuilder()
            .setCredentialsProvider(FixedCredentialsProvider.create(credentials))
            .build();

    // Instantiates a client
    try (SpeechClient speechClient = SpeechClient.create(speechSettings)) {

That should work correctly (I tested it this time). If using that doesn't fix your problem, then we know we have the right file but it's not the right credentials. Please try to generate a new one be following the steps here.
And - if that doesn't work - come back with the stack trace and we'll see what we can figure out :)

Thanks buddy! It works now. Added environment variable to the run configuration and it solved the problem. Thanks again!!

Glad we got it to work! I'm going to go ahead and close this out.

repo: GoogleCloudPlatform/java-docs-samples


text:
Master logs not uploaded on successful e2e runs or failed test -up

We dump master logs for uploading to GCS on failed e2e runs, but not on successful e2e runs or failed test -up.
We should definitely be dumping those logs for failed cluster-ups, and it would also be nice to throw in the successes too (good to have recent green for comparison).

@ixdy @quinton-hoole

Getting logs uploaded on a failed test -up seems really important for debugging.

+1
There were just a bunch of failures in scalability test suite (run 1623-1628) that failed because not all system pods were running. Since there are no logs, there is no easy way to debug it.
It would be super useful to have all the logs for failed cluster-ups.
cc @davidopp

Unless I'm confused, it looks as if these logs are still not being uploaded.  @dchen1107 @ixdy FYI.

For example:
gs://kubernetes-jenkins/logs/kubernetes-e2e-gce/7500

That particular build was a timeout. When Jenkins kills the job, the log-collecting code never runs.

Another case we won't collect logs is if the cluster fails to initialize. (Which is a really important place to collect logs, but it's not a trivial fix.)

Moving this into post, since it seems unlikely to get fixed in the near term.  @ixdy feel free to correct me if I'm wrong.

We also don't collect logs on test job timeouts, which is frustrating.

We also don't collect logs on test job timeouts, which is frustrating.
+1

#21183 will collect the logs when the cluster fails to initialize.  That's not all the cases listed here, but it's a good one.

I'd like to bump the priority for this further - we don't have any logs to help with debugging #18969, which started to happen more often recently - it seems that #21183 didn't help. cc @davidopp @mml @ixdy @fejta @wojtek-t

I have too many P0s assigned to me already. This is at least 3rd in line right now.

This one is half year old and is P0 for a month...

From discussion with @spxtr on hangouts, a vague plan:

move log-dumping logic from test/e2e/core.go into a standalone command in something like cmd/dumplogs (feel free to bikeshed the name)
update Jenkins to call this command as a post-build step
probably remove test/e2e/core.go and the debug stuff recently added to cluster/gce/util.sh.

Right now the test/e2e/core.go stuff is pretty GCE/GKE specific and uses ssh. We should probably change to a more provider-agnostic method, but this would be a good start.

Hm, actually, post-build step actually won't work, since we tear down the cluster first. But making it a separate command can still let us call it in more places.

FYI - we also need logs from timed-out runs (not only the failed ones).

@wojtek-t moving test/e2e/core.go out into its own binary should help accomplish this.

I'm worried that the best way to do this is to write a bash script that grabs IPs from cluster/{provider}/util.sh's detect-master and detect-nodes functions and just does an ssh and cats the logs. Then we could point test/e2e/core.go at that.
It's sorta difficult to make test/e2e/core.go work on its own.

I think at this point we're happy with anything that usually works. We can work on making in nice and shiny later.

We now get logs when kube-up fails, which recently happened here :)
Still some work to do here, I'll leave this issue open until timeouts are handled properly and test/e2e/core.go points here.

@spxtr - I can't thank you enough!

Ok, #22374 is in so we should get logs for kubernetes-e2e-* jobs and PR Jenkins jobs on timeout.

I'm gonna call this done.

source: gharchive/issue

authors: brendandburns cjcullen gmarek ixdy mml quinton-hoole roberthbailey spxtr wojtek-t

repo: GoogleCloudPlatform/kubernetes

license_type: permissive

license_source: github-api


text:
Update CLI roadmap

# Kubernetes CLI/Configuration Roadmap

See also issues with the following labels:
* [area/config-deployment](https://github.com/GoogleCloudPlatform/kubernetes/labels/area%2Fconfig-deployment)
* [component/CLI](https://github.com/GoogleCloudPlatform/kubernetes/labels/component%2FCLI)
* [component/client](https://github.com/GoogleCloudPlatform/kubernetes/labels/component%2Fclient)

1. Kind-based filtering on object streams -- only operate on the kinds of objects specified. This would make directory-based kubectl operations much more useful. Users should be able to instantiate the example applications using `kubectl create -f <example-dir> ...`
1. Create services before other objects, or at least before objects that depend upon them. Namespace-relative DNS mitigates this some, but most users are still using service environment variables. [#1768](https://github.com/GoogleCloudPlatform/kubernetes/issues/1768)
1. Pretty printing of endpoints

Simple version is done, more complex version needs work.
1. Service address/port lookup command(s)
1. Finish rolling update [#1353](https://github.com/GoogleCloudPlatform/kubernetes/issues/1353)
  1. Friendly to auto-scaling [#2863](https://github.com/GoogleCloudPlatform/kubernetes/pull/2863#issuecomment-69701562)
  1. Rollback (make rollingupdate reversible, and complete an in-progress rolling update by taking 2 replication controller names rather than always taking a file)
  1. Rollover (replace multiple replication controllers with one, such as to clean up an aborted partial rollout)
  1. Write a ReplicationController generator to derive the new ReplicationController from an old one (e.g., `--image-version=newversion`, which would apply a name suffix, update a label value, and apply an image tag)
  1. Use readiness [#620](https://github.com/GoogleCloudPlatform/kubernetes/issues/620)

Done, now that readiness corresponds to Running and is tracked by Kubelet status if the readiness hook is set?
  1. Perhaps factor this in a way that it can be shared with [Openshift’s deployment controller](https://github.com/GoogleCloudPlatform/kubernetes/issues/1743)
  1. Rolling update service as a plugin
1. List supported API versions

Done
1. List supported resources
1. Swagger lookups [#3060](https://github.com/GoogleCloudPlatform/kubernetes/issues/3060)
1. --name, --name-suffix applied during creation and updates
1. --labels and opinionated label injection: --app=foo, --tier={fe,cache,be,db}, --uservice=redis, --env={dev,test,prod}, --stage={canary,final}, --track={hourly,daily,weekly}, --release=0.4.3c2. Exact ones TBD. We could allow arbitrary values -- the keys are important. The actual label keys would be (optionally?) namespaced with kubectl.kubernetes.io/, or perhaps the user’s namespace.
1. --annotations and opinionated annotation injection: --description, --revision
1. Bulk updates (similar to get, create, delete)

Done
1. Imperative updates. We'll want to optionally make these safe(r) by supporting preconditions based on the current value and resourceVersion.
  1. annotation updates similar to label updates
  1. more user-friendly on-command-line json for patch

Do we want to do a more generic one or a less generic one?  OpenShift was looking more at specific topical plugin commands ("add-volume", "set-default-resources"), but not sure how much hand-holding users need.
1. We also want to support the following flavors of more general updates:
  1. whichever we don’t support:
    1. safe update: update the full resource, guarded by resourceVersion precondition (and perhaps selected value-based preconditions)
    1. forced update: update the full resource, blowing away the previous Spec without preconditions; delete and re-create if necessary
  1. diff/dryrun: Compare new config with current Spec
  1. submit/apply/reconcile/ensure/merge: Merge user-provided fields with current Spec. Keep track of user-provided fields using an annotation -- see [#1702](https://github.com/GoogleCloudPlatform/kubernetes/issues/1702). Delete all objects with deployment-specific labels.
1. --dry-run for all commands
1. Support full label selection syntax, including support for namespaces.

Getting close.
1. Wait on conditions [#1899](https://github.com/GoogleCloudPlatform/kubernetes/issues/1899)
1. Make kubectl scriptable: make output and exit code behavior consistent and useful for wrapping in workflows and piping back into kubectl and/or xargs (e.g., dump full URLs?, distinguish permanent and retry-able failure, identify objects that should be retried)
  1. Here's [an example](http://techoverflow.net/blog/2013/10/22/docker-remove-all-images-and-containers/) where multiple objects on the command line and an option to dump object names only (`-q`) would be useful in combination.
1. Easy generation of clean configuration files from existing objects (including containers -- podex) -- remove readonly fields, status
  1. Export from one namespace, import into another is an important use case
1. Derive objects from other objects
  1. pod clone
  1. rc from pod
  1. --labels-from (services from pods or rcs)
1. Kind discovery (i.e., operate on objects of all kinds) [#5278](https://github.com/GoogleCloudPlatform/kubernetes/issues/5278)
1. A fairly general-purpose way to specify fields on the command line during creation and update, not just from a config file
1. Extensible API-based generator framework (i.e. invoke generators via an API/URL rather than building them into kubectl), so that complex client libraries don’t need to be rewritten in multiple languages, and so that the abstractions are available through all interfaces: API, CLI, UI, logs, ... [#5280](https://github.com/GoogleCloudPlatform/kubernetes/issues/5280)
  1. Need schema registry, and some way to invoke generator (e.g., using a container)
  1. Convert run-container to API-based generator
1. Transformation framework
  1. More intelligent defaulting of fields (e.g., [#2643](https://github.com/GoogleCloudPlatform/kubernetes/issues/2643))
1. Update preconditions based on the values of arbitrary object fields.
1. Deployment manager compatibility on GCP: [#3685](https://github.com/GoogleCloudPlatform/kubernetes/issues/3685)

TODO:
* watch
* ssh [#1513](https://github.com/GoogleCloudPlatform/kubernetes/issues/1513)

Exec has landed and is a replacement for ssh
* attach [#1521](https://github.com/GoogleCloudPlatform/kubernetes/issues/1521)

Attach on start remains hard.
* image/registry commands
* do any other server paths make sense? validate? generic curl functionality?
* template parameterization
* dynamic/runtime configuration

Server-side support:

Only finishing v1beta3 is a requirement for 1.0. The others are strong nice-to-haves.

1. Finish v1beta3
1. Default selectors from labels [#1698](https://github.com/GoogleCloudPlatform/kubernetes/issues/1698#issuecomment-71048278)
1. List supported resources [#2057](https://github.com/GoogleCloudPlatform/kubernetes/issues/2057)
1. Stop [#1535](https://github.com/GoogleCloudPlatform/kubernetes/issues/1535)

Implemented
1. Deleted objects [#2789](https://github.com/GoogleCloudPlatform/kubernetes/issues/2789)
1. Clone [#170](https://github.com/GoogleCloudPlatform/kubernetes/issues/170)
1. Resize [#1629](https://github.com/GoogleCloudPlatform/kubernetes/issues/1629)
1. Useful /operations API: wait for finalization/reification
1. Readiness [#620](https://github.com/GoogleCloudPlatform/kubernetes/issues/620)
1. Reverse label lookup [#1348](https://github.com/GoogleCloudPlatform/kubernetes/issues/1348)
1. Field selection [#1362](https://github.com/GoogleCloudPlatform/kubernetes/issues/1362)
1. Field filtering [#1459](https://github.com/GoogleCloudPlatform/kubernetes/issues/1459)
1. Operate on uids

I/we should also file issues for outstanding items without issues, and add lines for newly filed issues (e.g., command flag for run-container).
Readiness is not yet used by rollingupdate.
With respect to patch on the command line: I was thinking of a generic mechanism, but I could see the case for domain-aware commands, also.
I think we need to better factor the command code and library code, and generic functionality vs. domain-aware functionality. Neither should ever convert to the internal representation. Domain-aware functionality (e.g., describe) should target a specific API version. Configuration generators, such as run-container, should be provided as services, or at least as separate plugin commands.

ref #5906

ref #5905

ref #4874

ref #6284

ref #5840

ref #5756


text:
Fix broken left nav bar links to api-references in k8s.io

New .md files for building the new .html  api file  with jekyll - so header and nav are added
In the .html files,

manually changed color from  #ba3925 to #428BCB
removed opening html  and footer tags
set max-width to auto

Also added javascript to override max-width (this works in the html but does not display - WIP)

Thank you @RichieEscarez! This is much better than what I did here:
https://github.com/GoogleCloudPlatform/kubernetes/tree/gh-pages/_tools/release_docs
if we can make the javascript to work, it will be perfect.

@caesarxuchao can you please LGTM this? Ive got another priority I need to work on and can come back to the width javascript override after.

It works on my local build. So LTGM.
FWIW, one other thing I noticed is that when I click api-reference in the left nav bar, the nav bar is scrolled up after loading and its font is larger. I think this is caused by the style defined in the definitions/operations html.

@RichieEscarez: This PR needs a rebase

IIUC, this will be overwritten, whenever we run _tools/import_master_docs.sh again.
We should be updating the tool to do such things.
cc @krousey @thockin

@nikhiljindal, you are right. This is just a temporary fix. We need to look for better way to generate the api-reference html files. The whole process is brittle now.

https://github.com/GoogleCloudPlatform/kubernetes/pull/11833 ran that tool again and essentially reverted this PR

I just opened #11850 that renames the .html files so our temporary fix does not get overwritten/overloaded in gh-pages when the script runs.

Also just opened #11851 to remove the .html files from the api-reference folder so that our temp fix works again. If the doc script gets run again, then per #11850, files with different names will be uploaded and this issue wont occur.

source: gharchive/pull-request

authors: RichieEscarez caesarxuchao nikhiljindal vishh


text:
Deleting OperationHandler for handling /operation endpoint on server

Replaces https://github.com/GoogleCloudPlatform/kubernetes/pull/3697
For https://github.com/GoogleCloudPlatform/kubernetes/issues/3644

Assigning to @bgrant0607 because #3697 that this replaces was.

LGTM

authors: alex-mohr bgrant0607 nikhiljindal


text:
WIP:  Allow reclamation of PersistentVolumes

New pv.Spec.ReclamationPolicy

Allows Recycle/Delete on release.  Retain by default.

New volume plugin interfaces

RecyclableVolumePlugin -- allows recycling of PVs
DeletableVolumePlugin -- allows deletion of PVs from the infrastructure

New PersistentVolumeRecycler controller loop

single threaded initially for correctness
separate from PersistentVolumeClaimBinder because we don't want the binder to block on reclamation tasks
works with the binder to remove or re-add reclaimed volumes to/from the pool of available volumes

Needs implementations:

Basic scrub impl:  run a pod w/ busybox "rm -rf" on the volume

develop/test with HostPath, use for NFS, potentially other volumes

Cloud volumes:  delete via API

PVs deleted from cloud providers as policy will be reprovisioned by #6773
Edit:   The purpose of this PR is to dynamically reclaim used and released resources.  As PersistentVolumeClaims are deleted, their backing PersistentVolumes are released, but they are not yet reusable.  Either they need to be scrubbed of their data before become Available again or the volumes should be deleted from the infrastructure.
The scrubbing use case is a build server using NFS as scratch space.  No need for an admin to reprovision the cluster after the volumes are used up.  Basic scrub is sufficient to put them back into the pool.  Don't use basic scrub at The Fed or the NSA.

@pmorie @thockin would love feedback on the direction, particularly around the new types of volume plugins (to allow some but not all PVs to be recycled or deleted).

I will remove Deleter as an interface to narrow the scope to just Recycler.  I would like confirmation that using new types of plugins is the correct way of handling this, though, so the current Recycler can be implemented and we'll know the future Deleter would be the correct solution.

Gonna take a pass at this today at some point.

Overall LGTM, I'll let it percolate. It'll need a finer-grained review when I have a bit more time for it.

Thanks @thockin.  I'll ping again when ready for a full review.

Thank you very much for the pull request - we sincerely appreciate the work that goes into sending us a change.
We are currently in a feature-freeze and general code slush as we work toward our 1.0 release.  Our initial triage indicates that this is a non-critical change at this time, so we'd like to leave it open and revisit it after 1.0.  We expect the freeze to wrap up in early to mid July.
If you feel that this triage is incorrect, please respond and let us know why.  We're currently accepting changes that meet any of the following criteria:

Changes directly related to v1.0 issues
Changes addressing P0 bugs
Changes to supported platforms to bring them up to par with the primary development platforms
Docs, user experience, and test related fixes

This in on the RH priority list for merge.

We can potentially push it if the risk is seen as high, but I haven't seen that triage performed.

Iff we can turn this around reasonably quickly we can get it in.
On Tue, May 26, 2015 at 12:11 PM, Clayton Coleman notifications@github.com
wrote:

We can potentially push it if the risk is seen as high, but I haven't seen
that triage performed.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8334#issuecomment-105637568
.

Mark is today or tomorrow reasonable or is there more still there?

On May 26, 2015, at 3:47 PM, Tim Hockin notifications@github.com wrote:
Iff we can turn this around reasonably quickly we can get it in.
On Tue, May 26, 2015 at 12:11 PM, Clayton Coleman notifications@github.com
wrote:

We can potentially push it if the risk is seen as high, but I haven't seen
that triage performed.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8334#issuecomment-105637568
.

—
Reply to this email directly or view it on GitHub.

I am only working through the busybox implementation.   debugging it to scrub the volume.  that is all.

The basic implementation is in for HostPath but i'm working through bugs.  Once it's good, I'll apply it to NFS.

Realistically this is a pretty key thing needed to make persistentVolumes useful, which are a 1.0 feature...

So @markturansky is basically full time on figuring this out right!

@eparis hopefully it won't be a long night.  the pod and watch currently works, just need to get the pod scrub command correct.  I'll need a good test, too.

Clearing milestone for now.

Stuck on making the scrubber.  It works from the Docker CLI but I cannot get it to work as a pod.
Any help is appreciated.
This works:
docker run -v /Users/markturansky/site-content/:/scrub busybox /bin/sh -c 'rm -rf /scrub/*'
But fails as a pod.  Just get a "killing [id]" when i describe the pod that was run:
Spec: api.PodSpec{
			RestartPolicy: api.RestartPolicyNever,
			Volumes: []api.Volume{
				{
					Name: uuid,
					VolumeSource: api.VolumeSource{
						HostPath: &api.HostPathVolumeSource{ r.path },
					},
				},
			},
			Containers: []api.Container{
				{
					Name: "scrubber-" + uuid,
					Image: "busybox",
					// delete the contents of the volume, but not the directory itself
					Command: []string{"/bin/sh",},
					Args: []string{"-c", "'rm -rf /scrub/*'"},
					VolumeMounts: []api.VolumeMount{
						{
							Name: uuid,
							MountPath: "/scrub",
						},
					},
				},
			},
			ActiveDeadlineSeconds: &timeout,
		},

... and nevermind.
the single quotes around 'rm -rf' on the Docker CLI are not needed in the pod container args.   Removing the single quotes from Args: []string{"-c", "'rm -rf /scrub/*'"} suddenly makes it work.

@thockin I'm working on an e2e test that uses a claim and volume from examples/persistent-volumes.
I think the code itself is ready for review while I prepare the test.

@bgrant0607's feedback was addressed and any other feedback would be appreciated while I'm developing the e2e test for this feature.  Anything else I need to do to make this merge worthy?

Update:  added e2e test using @jsafrane's NFS server pod but have to work through some mounting issues for the scrubber.   This uncovered the need for better error handling so that PVs aren't recycling forever, instead relying on admin's to manually reclaim them on error.
I'll work through these issues with @jsafrane tomorrow and get this e2e test completed.

@thockin e2e passes, but like the volumes e2e test (on which this was created), it requires privileged, so it won't run in the e2e suite by default.
Here is a full run of the recycler:   https://gist.github.com/jsafrane/6dc167d752a70a570b7e

all green tests, too, FWIW.

This large PR is broken down into smaller, linked PRs.  They should be reviewed and merged roughly in order, as each cherry-picks the the former.

Closing this PR.  All commits accounted for in #9024.

authors: eparis markturansky pmorie saad-ali smarterclayton thockin


text:
feat: Onboard NOAA dataset

Description
ghcnd_by_year
ghcnd_countries
ghcdn_inventory
ghcnd_states
ghcnd_stations
gsod_stations
ghcnd_hurricanes
lightning_strikes_by_year
Checklist

[x] (Required) This pull request is appropriately labeled
[x] Please merge this pull request after it's approved
[x] I'm adding or editing a dataset

[x] The Google Cloud Datasets team is aware of the proposed dataset
[x] I put all my code inside  datasets/noaa and nothing outside of that directory

[x] I'm refactoring or cleaning up some code

@adlersantos Fixes are complete as per your request.  Testing showed one other issue which is now resolved.  Please Review.  Thanks!

license_source: bigquery


text:
refactor, chore(egen): Refactored code according to template guidelines, added code to delete job in cleanup section

This PR includes the following updates:

Adds Colab Enterprise link and other structural changes from the new template.
Changes REGION variable name to LOCATION.
Changes dag variable name to job
Removes os.getenv("IS_TESTING") and import os from the cleanup section.
Adds job.delete() to delete training job in the cleanup section.
Removes code highlight when used at places other than code or variables.
Adds comments for cells needed.
Removes the usage of future tense.
Replaces aip with aiplatform.
Contracts words like is not, do not, You are, etc.

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcbrun

authors: katiemn sumanvita-springml

repo: GoogleCloudPlatform/vertex-ai-samples


text:
Use kubectl to deploy necessary RBAC in mono repo apiservice_test (#73)

The mentioned RBAC includes necessary ClusterRole and ClusterRoleBindings for the backend deployment to work in GKE environment. In Config Sync CI after each test it will try to reset the test git repo to default. Removing this RBAC from git directly is blocked by importer as it detects the commit of removal will reduce the count of cluster resource from more than 1 down to 0.
Thus manually deploying RBAC when test is running in mono repo mode.

/lgtm
/approve

Note: This is a hack to fix a problem that's already been fixed on the main branch in a more robust way, with a 'safety' ClusterRole. Let's make sure this stays only on the v1.13 branch.

@tiffanny29631 Can you update the test on the main branch given that we have already had a safety ClusterRole? The ClusterRole prevents from deleting more than 1 existing cluster-scoped resources from the cluster in one shot.

/retest

@nan-yu I dont think main need updating. The new safety ClusterRole I added ALLOWS tests to delete all their cluster-scoped resources. I added it so that individual tests don't need to do this dance.

/retest

re: https://github.com/GoogleContainerTools/kpt-config-sync/pull/142#issuecomment-1261344293

Note: This is a hack to fix a problem that's already been fixed on the main branch in a more robust way, with a 'safety' ClusterRole. Let's make sure this stays only on the v1.13 branch.

The same change is already in the main branch before the ClusterRole fix was merged. Using kubectl apply bypasses the safety check issue. We can switch back to use Config Sync to manage the RBAC, but it is not worth it.

authors: karlkfi nan-yu sdowell

repo: GoogleContainerTools/kpt-config-sync


text:
Angular: Rename react components

Acceptance Criteria:

React components renamed to Goab
Types renamed to Goab

Closing, as this has been merged into angular-components

repo: GovAlta/ui-components


text:
Added a theme change and an AcrylicBlurWindow with an acrylic effect background.

There are a lot of issues for the acrylic blur window implemented by DWM.

The UI response to move window is too awful. (This problem has been since 19H1, when the method of an acrylic effect was changed.)
ref. http://sourcechord.hatenablog.com/entry/2019/05/17/235928 (Japanese)
cf. How to make an acrylic effect: https://github.com/microsoft/microsoft-ui-xaml/blob/de788345659ba319597161149843504fbe686659/dev/Materials/Acrylic/AcrylicBrush.cpp#L697-L797
When WPF is made completely transparent, HitTest will be passed through. The workaround is to set Alpha = 1/255.
ref. https://github.com/riverar/sample-win32-acrylicblur/blob/e59727c30b29bac4335ca7e91774427982263c97/MainWindow.xaml#L5
Once the acrylic effect is disabled, the acrylic effect cannot be re-enabled. The workaround is to enable the acrylic effect even if the effect is not needed.

(以下の日本語は英語と同じ内容です)
アクリル効果の背景をもつAcrylicBlurWindowの追加，および淡色・濃色の切り替え実装。
DWM実装によるアクリル素材のウィンドウには現在の最新バージョン (May 2020 Update) で以下の問題があります。

ウィンドウ移動のレスポンスが悪い。(19H1 以降，アクリルの表現方法が変化して以降からの問題)
ref. http://sourcechord.hatenablog.com/entry/2019/05/17/235928
cf. アクリル効果の作り方 https://github.com/microsoft/microsoft-ui-xaml/blob/de788345659ba319597161149843504fbe686659/dev/Materials/Acrylic/AcrylicBrush.cpp#L697-L797
WPF側を完全な透過ウィンドウにすると，HitTestがスルーされる。
回避方法は Alpha = 1/255 に設定する。
ref. https://github.com/riverar/sample-win32-acrylicblur/blob/e59727c30b29bac4335ca7e91774427982263c97/MainWindow.xaml#L5
一度アクリル効果を無効化すると，アクリル効果を再有効化できない。
回避方法は透明効果を必要としないときでもアクリル効果を有効化しておくこと。

Avoid crashes for Windows 7.
I also followed the style used in the notification window and designed it to look like the Windows 7 battery window, rather than the DWM expansion window.

(以下の日本語は英語と同じ内容です)
Windows 7向けにクラッシュしないよう回避するコードを追加しました。
また，通知ウィンドウで使われることを想定して，DWM拡張ウィンドウではなく，Windows 7のバッテリーウィンドウと同じようなデザインにしています。

Resolve the 3rd problem.
The AccentState definition was wrong.

license: mit


text:
New Apache version

There's a new version at http://mirror.ventraip.net.au/apache/httpd/ and the old one is not present anymore.
New version: 2.4.23
I can make a pull request once it compiled successfully.

Docker images on Docker Hub updated with latest Apache httpd, as well as latest versions of nghttp2, tini and mod_wsgi-express.

authors: Craeckie GrahamDumpleton


text:
Listen Import Event, dont work editor.on('run:mjml-import:change'

Hi, I'm using the latest version of grapesjsmjml and this solution doesn't work for me. I need to listen to the event when importing, can someone help me?
try this solution, but it doesn't work https://github.com/GrapesJS/mjml/issues/104

Hi
Have you tried to look at the doc in this link
https://grapesjs.com/docs/api/commands.html#commands
Maybe its like this
editor.on('stop:mjml-import:before', (mjml) => {
  console.log(mjml);
})

También estoy intentando usar  this.editor.runCommand('mjml-get-code').html para obtener el html generado, pero tampoco me funciona. Por favor me ayudarías a saber como tener acceso al html y css ?.

I'm also trying to use this.editor.runCommand('mjml-get-code').html to get the generated html, but it doesn't work for me either. Please help me to know how to access html and css ?

try the proposed solution, but it is not importing the mjml code. I need to listen to the event and have access to the mjml code I'm loading.
And here for another functionality I need to access the generated html
to store it in the data base, but using this.editor.runCommand('mjml-get-code').html doesn't work for me

I also have this problem, please help me to know how I can solve it ? error_ core.mjs:7739 ERROR Error: Malformed MJML. Check that your structure is correct and enclosed in  tags.

the wrapper is not generating well the code initially ...

I also have this problem, please help me to know how I can solve it ? error_ core.mjs:7739 ERROR Error: Malformed MJML. Check that your structure is correct and enclosed in tags.
the wrapper is not generating well the code initially ...

the mjml you have is not enclose in mjml tag
Its need to be like this
<mjml>
  <mj-body>

     // the rest of your code in image

  </mj-body>
</mjml>

however, this is the code that is generated by drag and drop (just dragging to create the plant) :/. How can it initialize? because installing the library and making editor.init should generate it automatically.

however, this is the code that is generated by drag and drop (just dragging to create the plant) :/. How can it initialize? because installing the library and making editor.init should generate it automatically.

however, this is the code that is generated by drag and drop (just dragging to create the plant) :/. How can it initialize? because installing the library and making editor.init should generate it automatically.

however, this is the code that is generated by drag and drop (just dragging to create the plant) :/. How can it initialize? because installing the library and making editor.init should generate it automatically.

however, this is the code that is generated by drag and drop (just dragging to create the plant) :/. How can it initialize? because installing the library and making editor.init should generate it automatically.

If I want to create a plant by drag and drop (from the beginning) I am not building the code correctly so it is sold without the initial tags

If I want to create a plant by drag and drop (from the beginning) I am not building the code correctly so it is sold without the initial tags

If I want to create a plant by drag and drop (from the beginning) I am not building the code correctly so it is sold without the initial tags

sorry but i dont really understand what you said and this issue getting a little drag out. You can contact me from telegram for further assistance https://t.me/huuhazozo.

If I want to create a plant by drag and drop (from the beginning) I am not building the code correctly so it is sold without the initial tags

repo: GrapesJS/mjml


text:
Keep selection when clicking in properties after creating text

Create a new text box
Type something
Attempt to modify something in the properties of the newly added text layer (e.g. change the fill colour)
The layer is deselected so the properties disappear.

It would be nice to keep the properties around when the user is trying to edit them.

Hi @Keavon , I’ve looked into the issue and would be happy to work on it. I’ll open a PR soon!

PR #2144  fixes this issue.

repo: GraphiteEditor/Graphite


text:
Implement collaborative editing

does not work at all
does work after all
Notes from early testing:

don't broadcast the download document message
each user has his own working folder
only operations and their responses are exchanged -> server could store all past operations for new users that join
should operations explicitly target one document? (should users be allowed to work on different documents simultaneously)

This change is

Let's put the server into a folder called nanotube.

Closing this for the time being.

authors: Keavon TrueDoctor


text:
Month and year display

create a display that doesnt display only the current week, but also the whole month, or a whole year, or 3 months etc.

Long ticket, expect it to be done dec 9, 2016

this issue has become deprecated per the new pannable grid.

repo: GreaseMonk/android-timetable-core


text:
🛑 Server Ultra is down

In 069e423, Server Ultra (https://ultra.greathost.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Server Ultra is back up in aead212 after 10 minutes.

repo: GreathostRo/upptime

license: MIT


text:
version 1.0.9 is built using an old node.js version

Please recompile with a newer NODE_MODULE_VERSION to support latest nodejs

Please recompile with a newer NODE_MODULE_VERSION to support latest nodejs

Ok, I will fix it in the weekend

Please recompile with a newer NODE_MODULE_VERSION to support latest nodejs

Normally it is fixed, I added FAQ in README to help you.

Hi !
The fix didn't worked for me sadly ...

Hi ! The fix didn't worked for me sadly ...

Are you try to rebuild the projet ?

I have this error with electron-rebuild :
An unhandled error occurred inside electron-rebuild
node-gyp failed to rebuild 'C:\[ ... ]\node_modules\mica-electron'.
For more information, rerun with the DEBUG environment variable set to "electron-rebuild".

Error: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe" failed with exit code: 1"

Do you have an idea ?

No idea but if you run the comand with --debug argument, what it say ?

Nothing more :s
What is the node version you used to compile the package ?

I use v18.10.0

Hi ! The fix didn't worked for me sadly ...

Are you try to rebuild the projet ?

I tried to rebuild the project, and it said Rebuild Complete, but when I try to run, it still have this error

Hi ! The fix didn't worked for me sadly ...

Are you try to rebuild the projet ?

I tried to rebuild the project, and it said Rebuild Complete, but when I try to run, it still have this error

try to do this commands in this order:
npm install mica-electron
cd .\node_modules\mica-electron
node-gyp rebuild
cd ....
npm install electron
npm install electron-rebuild
.\node_modules.bin\electron-rebuild

node-gyp rebuild

I got this error when node-gyp rebuild
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp\lib\configure.js:325:16)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Windows_NT 10.0.25217
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Proj\test-pack\node_modules\mica-electron
gyp ERR! node -v v18.11.0
gyp ERR! node-gyp -v v9.3.0
gyp ERR! not ok

You don't have more details about the error ?

You don't have more details about the error ?

This is all
gyp info it worked if it ends with ok
gyp info using node-gyp@9.3.0
gyp info using node@18.11.0 | win32 | x64
gyp info find Python using Python version 3.10.8 found at "C:\Python310\python.exe"
gyp info find VS using VS2019 (16.11.32901.82) found at:
gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools"
gyp info find VS run with --verbose for detailed information
gyp info spawn C:\Python310\python.exe
gyp info spawn args [
gyp info spawn args   'C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp\gyp\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-I',
gyp info spawn args   'C:\Proj\test-pack\node_modules\mica-electron\build\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\Users\Nevabc\AppData\Local\node-gyp\Cache\18.11.0\include\node\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\Users\Nevabc\AppData\Local\node-gyp\Cache\18.11.0',
gyp info spawn args   '-Dnode_gyp_dir=C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp',
gyp info spawn args   '-Dnode_lib_file=C:\\Users\\Nevabc\\AppData\\Local\\node-gyp\\Cache\\18.11.0\\<(target_arch)\\node.lib',
gyp info spawn args   '-Dmodule_root_dir=C:\Proj\test-pack\node_modules\mica-electron',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\Proj\test-pack\node_modules\mica-electron\build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp: binding.gyp not found (cwd: C:\Proj\test-pack\node_modules\mica-electron) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp\lib\configure.js:325:16)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Windows_NT 10.0.25217
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Nevabc\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Proj\test-pack\node_modules\mica-electron
gyp ERR! node -v v18.11.0
gyp ERR! node-gyp -v v9.3.0
gyp ERR! not ok

You don't have binding.gyp in \node_modules\mica-electron ?

node-gyp rebuild

Oh sorry, I cloned the project from github. node-gyp works now.

Hi ! The fix didn't worked for me sadly ...

Are you try to rebuild the projet ?

I tried to rebuild the project, and it said Rebuild Complete, but when I try to run, it still have this error

try to do this commands in this order:
npm install mica-electron cd .\node_modules\mica-electron node-gyp rebuild cd ....\ npm install electron npm install electron-rebuild .\node_modules.bin\electron-rebuild

I didn't use npm, I just cloned it from github, and it works now. Thank you very much.

authors: GregVido Nevodev Soahr yazninja

repo: GregVido/mica-electron


text:
Tracking Issue: support full-text index

What problem does the new feature solve?
Support full-text index.
What does the feature do?

[x] Creator for full-text index
[x] Integrate with sst writer
[x] CREATE statement support

Implementation challenges
No response

So , there is only one remaining task that integrates the index with the match function? @zhongzc

So , there is only one remaining task that integrates the index with the match function? @zhongzc

Yes, I will send the PR soon.

repo: GreptimeTeam/greptimedb


text:
🛑 walletcheck API endpoint is down

In efc9f59, 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 6301aba.

repo: Grinnode-live/upptime


text:
🛑 walletcheck API endpoint is down

In 60e5cda, 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 494fe46.


text:
Ajax Spider with Context and User

hi, how do you run zap-cli ajax-spider with a context and a user? similar to zap-cli spider -c context -u user

Same. This is a very common pattern and there's no working example for ajax spidering for authorization in CLI for zap-cli or zap in general.  I can do it in GUI - but that's not useful because apparently they're practically separate applications.

Hi @tony , it seems like this tools is no longer being maintained.
my workaround is to run spider before ajax spider since i guess the session after spidering is persisted.
I'm also guessing that we could also run ajax spider by using quick-scan with custom script scanner
only (if im not wrong the scanner id is 50000) after disabling all the custom active-scan script (thus no active-scan script will run).

Thank you for the response @rucciva!

my workaround is to run spider before ajax spider since i guess the session after spidering is persisted.

Can you give me an example of what it looks like in CLI commands?

I'm also guessing that we could also run ajax spider by using quick-scan with custom script scanner
only (if im not wrong the scanner id is 50000) after disabling all the custom active-scan script (thus no active-scan script will run).

An example of this, if such a thing existed would be incredibly valuable!

sure, something like this (assuming you have started the zap daemon before)
zap-cli spider -c "$CONTEXT_NAME" -u "$CONTEXT_USER" "$URL" && zap-cli ajax-spider "$URL"

or with quick-scan
zap-cli quick-scan --ajax-spider  -c "$CONTEXT_NAME" -u "$CONTEXT_USER" --scanners "50000" "$URL"

Thank you! I will give this a try in the AM tomorrow (Texas time)

authors: rucciva tony

repo: Grunny/zap-cli


text:
🛑 fownhost Blog is down

In e7f3b06, fownhost Blog (http://blog.fownhost.ga) was down:

HTTP code: 0
Response time: 0 ms

Resolved: fownhost Blog is back up in b46044f.

repo: Guangsudalao/uptime


text:
Implementation Microsoft Plugin

Please check the implementation of the microsoft mail adress and the settings of the plugin I installed. In case we have to connect with the IT again.

was fixed

authors: GuidaGG ah-bas-und-aer

repo: GuidaGG/vielfaeltig


text:
🛑 API Next - load whole book is down

In bdf5dd6, API Next - load whole book (https://h-edu.cz/content.api/book/book-a/chaptersContent) was down:

HTTP code: 502
Response time: 189 ms

Resolved: API Next - load whole book is back up in 05164f3.

repo: H-edu-dev/upptime


text:
🛑 CSDC OJ is down

In cd76996, CSDC OJ (https://csdc.tw) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CSDC OJ is back up in d6e76af after 19 hours, 55 minutes.

repo: HCHS-CSDC/CSDC-OJ-Uptime


text:
🛑 SkipTheCommericals is down

In 10e62a6, SkipTheCommericals ($STC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheCommericals is back up in b80dc14.

repo: HDVinnie/TrackerHub


text:
🛑 Telly is down

In 895e9bd, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 8f6c762.


text:
🛑 Telly is down

In 9a6ef6a, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in e533ad5.


text:
🛑 Telly is down

In 4caca43, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 066c234.


text:
🛑 Telly is down

In 39ad0c4, Telly ($TLY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Telly is back up in 53473ec.


text:
🛑 SkipTheTrailers is down

In 250812f, SkipTheTrailers ($STT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkipTheTrailers is back up in 29e5b37.


text:
Antenna table from MIRIAD into CASA

Attempts to get any and all PAPER MIRIAD data into CASA result in the following error.
2016-06-13 18:32:37    WARN    MSFitsInput::fillAntennaTable    PAPER there is at least one gap in the antenna sequence found in the FITS AN table. Empty rows will be inserted into the ANTENNA table representing the gaps.
2016-06-13 18:32:37    SEVERE    ms::fromfits    SSMIndex::getIndex - access to non-existing row 4294967295 in /home/user/data/testout2.ms/ANTENNA at File: /var/rpmbuild/BUILD/casa-prerelease/casa-prerelease-4.6.0/casacore/msfits/MSFits/MSFitsInput.cc, line: 588
2016-06-13 18:32:37    SEVERE    importuvfits::::    *** Error ***SSMIndex::getIndex - access to non-existing row 4294967295 in /home/user/data/testout2.ms/ANTENNA at File: /var/rpmbuild/BUILD/casa-prerelease/casa-prerelease-4.6.0/casacore/msfits/MSFits/MSFitsInput.cc, line: 588
I initially thought the warning and the errors were unrelated, but they may in fact be connected.  The error occurs looking for a 'non-existing row' in the measurement set equivalent of the antenna table.  Even a single file with only baseline 0_0 throws this error.

This is an issue with miriad scripts (e.g. correct scripts or pull_antpols.py) that change the number of antennas but apparently do not modify the MIRIAD header in a reasonable way.  Not clear if there is a pyuvdata fix without better understanding headers.  For now, need to be careful about what operations are performed on a miriad files before reading into pyuvdata.  Note that removing a baseline (but not changing the number of antennas) is OK.

Further errors occur in CASA 4.6 that don't occur in 4.5:
2016-06-14 20:14:13    SEVERE    ms::fromfits    Exception: This data set has (1-based) antenna number 32 in the visibility data, but there is no corresponding antenna ID in the FITS AN table. Cannot proceed..
2016-06-14 20:14:13    SEVERE    ms::fromfits+    ... thrown by void casa::MSFitsInput::fillAntennaTable(casa::BinaryTable&) at File: /var/rpmbuild/BUILD/casa-prerelease/casa-prerelease-4.6.0/casacore/msfits/MSFits/MSFitsInput.cc, line: 1726 at File: /var/rpmbuild/BUILD/casa-prerelease/casa-prerelease-4.6.0/casacore/msfits/MSFits/MSFitsInput.cc, line: 588
2016-06-14 20:14:13    SEVERE    importuvfits::::    *** Error ***Exception: This data set has (1-based) antenna number 32 in the visibility data, but there is no corresponding antenna ID in the FITS AN table. Cannot proceed..
2016-06-14 20:14:13    SEVERE    importuvfits::::+    ... thrown by void casa::MSFitsInput::fillAntennaTable(casa::BinaryTable&) at File: /var/rpmbuild/BUILD/casa-prerelease/casa-prerelease-4.6.0/casacore/msfits/MSFits/MSFitsInput.cc, line: 1726 at File: /var/rpmbuild/BUILD/casa-prerelease/casa-prerelease-4.6.0/casacore/msfits/MSFits/MSFitsInput.cc, line: 588
I haven't found any miriad files that I can get into CASA 4.6 so far.

The latter issue is not with MIRIAD, but a general issue with antenna tables written by pyvudata.  (We failed a uvfits -> uvfits -> CASA test.)  Closing this issue and opening another one.

repo: HERA-Team/pyuvdata


text:
如何只下载字幕和封面图?

请问什么参数可以只下载字幕和缩略图,不需要下载视频文件或者也不音频文件,谢谢

目前命令行没有这样的参数，只能通过python写脚本


text:
Specifying image in the test file causes unexpected behaviour

Hello,
If I specify the name of the Docker image to be used such as the following example:
[type=openswitch name="OpenSwitch 1"] ops1
[type=host name="Host 1" image="openswitch/genericx86-64"] hs1
[type=host name="Host 2"] hs2

The behaviour it causes is unexpected. WITHOUT this property the tests run just fine. The following is the stack trace and error message:
========================================================================================================================================================================================= ERRORS ==========================================================================================================================================================================================
_______________________________________________________________________________________________________________________________________________________________________________ ERROR at setup of test_vlan _______________________________________________________________________________________________________________________________________________________________________________
[gw1] linux -- Python 3.4.3 /ws/cambronw/openswitch_tests/.tox/py34/bin/python3.4
Error building topogy in module test_vlan:
Traceback (most recent call last):
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/client.py", line 138, in _raise_for_status
    response.raise_for_status()
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/requests/models.py", line 840, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 409 Client Error: Conflict for url: http+docker://localunixsocket/v1.21/images/openswitch%2Fgenericx86-64%3Alatest/tag?repo=openswitch%2Fgenericx86-64&tag=latest&force=0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology/pytest/plugin.py", line 157, in topology
    topomgr.build()
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology/manager.py", line 296, in build
    raise e
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology/manager.py", line 238, in build
    enode = self._platform.add_node(node)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/platform.py", line 77, in add_node
    node.identifier, **node.metadata
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/nodes/host.py", line 41, in __init__
    super(HostNode, self).__init__(identifier, image=image, **kwargs)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/node.py", line 77, in __init__
    self._autopull()
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/node.py", line 133, in _autopull
    if not self._client.tag(pull_name, image, tag):
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/utils/decorators.py", line 21, in wrapped
    return f(self, resource_id, *args, **kwargs)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/api/image.py", line 269, in tag
    self._raise_for_status(res)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/client.py", line 142, in _raise_for_status
    raise errors.APIError(e, response, explanation=explanation)
docker.errors.APIError: 409 Client Error: Conflict ("b'Conflict: Tag openswitch/genericx86-64:latest is already set to image d3db7be415c0, if you want to replace it, please use -f option'")

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Captured stderr setup ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Build failed at stage "add_node" with "409 Client Error: Conflict ("b'Conflict: Tag openswitch/genericx86-64:latest is already set to image d3db7be415c0, if you want to replace it, please use -f option'")". Calling plugin rollback routine...
-------------------------------------------------------------------------------------------------------------------------------------------------------- generated xml file: /ws/cambronw/openswitch_tests/.tox/py34/tmp/tests.xml --------------------------------------------------------------------------------------------------------------------------------------------------------
================================================================================================================================================================================ slowest 10 test durations ================================================================================================================================================================================
15.51s setup    test_vlan.py::test_vlan
0.00s teardown test_vlan.py::test_vlan
================================================================================================================================================================================ 1 error in 16.67 seconds =================================================================================================================================================================================
ERROR: InvocationError: '/ws/cambronw/openswitch_tests/.tox/py34/bin/py.test --random --durations=10 --junitxml=tests.xml --topology-nml-dir topologies --topology-plot-dir topologies --topology-plot-format svg --topology-platform docker -n=auto -v /ws/cambronw/openswitch_tests/test'
_________________________________________________________________________________________________________________________________________________________________________________________ summary _________________________________________________________________________________________________________________________________________________________________________________________
ERROR:   py34: commands failed

Is your intention to load an openswitch image on a host?

No. On a switch.
Regards,
Walinton Cambronero
HPE Aruba Networking
-------- Original message --------
From: Diego Hurtado notifications@github.com
Date: 01/02/2016 22:34 (GMT-06:00)
To: HPENetworking/topology_docker topology_docker@noreply.github.com
Cc: "Cambronero, Walinton" walinton.cambronero@hpe.com
Subject: Re: [topology_docker] Specifying image in the test file causes unexpected behaviour (#8)
Is your intention to load an openswitch image on a host?
�
Reply to this email directly or view it on GitHubhttps://github.com/HPENetworking/topology_docker/issues/8#issuecomment-178369043.

I just changed the topology definition to the following (my original intent)
# Nodes
[type=openswitch name="OpenSwitch 1" image="openswitch/genericx86-64"] ops1
[type=host name="Host 1"] hs1
[type=host name="Host 2"] hs2

Same problem happened. Here the stack trace:
../../../test_vlan.py::test_vlan
[gw3] ERROR ../../../test_vlan.py::test_vlan

========================================================================================== ERRORS ===========================================================================================
________________________________________________________________________________ ERROR at setup of test_vlan ________________________________________________________________________________
[gw3] linux -- Python 3.4.3 /ws/cambronw/openswitch_tests/.tox/py34/bin/python3.4
Error building topogy in module test_vlan:
Traceback (most recent call last):
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/client.py", line 138, in _raise_for_status
    response.raise_for_status()
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/requests/models.py", line 840, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 409 Client Error: Conflict for url: http+docker://localunixsocket/v1.21/images/openswitch%2Fgenericx86-64%3Alatest/tag?repo=openswitch%2Fgenericx86-64&tag=latest&force=0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology/pytest/plugin.py", line 157, in topology
    topomgr.build()
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology/manager.py", line 296, in build
    raise e
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology/manager.py", line 238, in build
    enode = self._platform.add_node(node)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/platform.py", line 77, in add_node
    node.identifier, **node.metadata
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/nodes/openswitch.py", line 220, in __init__
    **kwargs
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/node.py", line 77, in __init__
    self._autopull()
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/topology_docker/node.py", line 133, in _autopull
    if not self._client.tag(pull_name, image, tag):
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/utils/decorators.py", line 21, in wrapped
    return f(self, resource_id, *args, **kwargs)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/api/image.py", line 269, in tag
    self._raise_for_status(res)
  File "/ws/cambronw/openswitch_tests/.tox/py34/lib/python3.4/site-packages/docker/client.py", line 142, in _raise_for_status
    raise errors.APIError(e, response, explanation=explanation)
docker.errors.APIError: 409 Client Error: Conflict ("b'Conflict: Tag openswitch/genericx86-64:latest is already set to image d3db7be415c0, if you want to replace it, please use -f option'")

----------------------------------------------------------------------------------- Captured stderr setup -----------------------------------------------------------------------------------
Build failed at stage "add_node" with "409 Client Error: Conflict ("b'Conflict: Tag openswitch/genericx86-64:latest is already set to image d3db7be415c0, if you want to replace it, please use -f option'")". Calling plugin rollback routine...
--------------------------------------------------------- generated xml file: /ws/cambronw/openswitch_tests/.tox/py34/tmp/tests.xml ---------------------------------------------------------
================================================================================= slowest 10 test durations =================================================================================
2.48s setup    test_vlan.py::test_vlan
0.00s teardown test_vlan.py::test_vlan
================================================================================== 1 error in 3.66 seconds ==================================================================================
ERROR: InvocationError: '/ws/cambronw/openswitch_tests/.tox/py34/bin/py.test --random --durations=10 --junitxml=tests.xml --topology-nml-dir topologies --topology-plot-dir topologies --topology-plot-format svg --topology-platform docker -n=auto -v /ws/cambronw/openswitch_tests/test'
__________________________________________________________________________________________ summary __________________________________________________________________________________________
ERROR:   py34: commands failed

Seems like :latest was missing from the image specification, this one will do:
[type=openswitch name="OpenSwitch 1" image="openswitch/genericx86-64:latest"] ops1

authors: ocelotl walintonc


text:
Itinerary creation process needs to be defined for admin view

Created an itinerary event and I do not understand the workflow/purpose.  Shouldn't I be able to add location points for this task to go to? Does it get data points from an outside source?

@stevejgordon @schuback @OhMcGoo we need to refine/define the workflow I guess and see if that does/doesn't work with requirements?

@schuback - I can cover this in more detail but the summary of the allReady functionality currently is...

An itinerary event can have tasks defined, which people can volunteer for. I.e. Install smoke alarms in region X on 12th Nov 2016, Driver in region X on 12th Nov 2016
An itinerary event can have requests linked to it, usually added via the API from getasmokealarm. Requests can also be manually created.
Finally itineraries are created. An admin can add team members to the itinerary. These would be any volunteers for tasks occurring on the same date as the itinerary. The admin can then add one or more requests to the itinerary which will be completed in that unit of work. It's these requests which then get shown on the map within the itinerary details page.

I am working on some of the mapping parts at the moment to include route optimization as well.
Not sure if that makes any sense. It's hard to summarise concisely. I'm happy to answer any questions or walk through in more details.

@schuback Just checking in to see if my answer made sense and whether you believe there is more work required as part of the v1 milestone?

@schuback @OhMcGoo let us know how we can help to validate what is desired/not compared to current implementation. thanks

authors: schuback stevejgordon tonysurma

repo: HTBox/allReady


text:
Can't compile vk-cli from AUR

$ yaourt -Si vk-cli
...
WARNING: A deprecated branch based version specification is used for the dependency ncurses. Please use numbered versions instead. Also note that you can still use the dub.selections.json file to override a certain dependency to use a branch instead.
Running pre-generate commands for vk...
/usr/bin/ld: /tmp/.rdmd-1000/rdmd-generateVersion.d-5E3B6B76371B8ACF9EF713A2A285AA37/objs/generateVersion.o: relocation R_X86_64_32 against `_D6object9Throwable7__ClassZ' can not be used when making a shared object; recompile with -fPIC
/tmp/.rdmd-1000/rdmd-generateVersion.d-5E3B6B76371B8ACF9EF713A2A285AA37/objs/generateVersion.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status

uname -a и версии pacman+yaourt и dmd, пожалуйста

Пожалуйста:
Linux 4.5.4-1-ARCH (x86_64)
Pacman v5.0.1 - libalpm v10.0.1
yaourt 1.8.1
dmd 2.071.1-1

Сколнируй репозиторий, сделай checkout issue31 и попробуй сделать dub build

@petRUShka Сколнируй репозиторий, сделай checkout issue31 и попробуй сделать dub build

Вообще довольно трудноуловимый баг

Сделано:
Performing "debug" build using dmd for x86_64.
dcrypto 1.2.2: building configuration "library"...
ncurses ~master: building configuration "library"...
../../.dub/packages/ncurses-master/ncurses/deimos/ncurses/form.d(38,8): Deprecation: module std.c.stdarg is deprecated - Import core.stdc.stdarg instead
vk ~issue31: building configuration "debug"...
source/utils.d(347,5): Deprecation: app.exit is not visible from module utils
Reticulating splines...
Linking...
/usr/bin/ld: /usr/lib/libphobos2.a(object.o): relocation R_X86_64_32 against `__dmd_personality_v0' can not be used when making a shared object; recompile with -fPIC
/usr/lib/libphobos2.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
--- errorlevel 1
dmd failed with exit code 1.

Покажи pacman -Q | grep phobos

@petRUShka Покажи pacman -Q | grep phobos

➤  pacman -Q | grep phobos
libphobos-devel 2.071.1-1

@petRUShka hardening-wrapper стоит?

Да, hardening-wrapper 10-1

@petRUShka Судя по всему проблема в нем

Что с ним нужно сделать? Удалить? Мб стоит поправить PKGBUILD?

После удаления собрался и с помощью dub build и из AUR. Кажется, стоит добавить этот пакет в conflicts...

Да,  добавлю

authors: petRUShka sirikid substanceof


text:
🛑 ConUHacks is down

In 3d57b99, ConUHacks (https://conuhacks.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ConUHacks is back up in 4269a86 after 12 minutes.

repo: HackConcordia/HC-Upptime


text:
Hello World 5 times

What the program do ?

In what programming language it is written?

It prints Hello World 5 times.
It is written in C#.


text:
Test to reproduce: java.lang.IllegalArgumentException: dash lengths all zero (11.0.2) see #71

Test Program

import eu.hansolo.tilesfx.Demo;
import javafx.application.Application;
import javafx.geometry.Pos;
import javafx.scene.Scene;
import javafx.scene.control.Label;
import javafx.stage.Stage;

public class X extends Application
{
    @Override
    public void start(Stage primaryStage)
    {
        Label label = new Label("Hello World");
        label.setAlignment(Pos.CENTER);
        primaryStage.setScene(new Scene(label, 300, 250));
        primaryStage.setTitle("Hello World Application");
        primaryStage.show();
    }

    public static void main(String[] args)
    {
        // launch(args);
        Demo.main(args);
    }
}

Intellij start configuration is:

--module-path /Users/X/Downloads/javafx-sdk-11.0.2/lib --add-modules javafx.graphics,javafx.base,javafx.controls,javafx.fxml

launch is working, application starts, window is shown
Demo.main fails with exception #71

Exception is:

Initialization: 780ms
Exception in Application start method
Exception in thread "JavaFX Application Thread" java.lang.IllegalArgumentException: dash lengths all zero
	at javafx.graphics/com.sun.prism.BasicStroke.set(BasicStroke.java:146)
	at javafx.graphics/com.sun.javafx.sg.prism.NGShape.setDrawStroke(NGShape.java:155)
	at javafx.graphics/javafx.scene.shape.Shape.updatePGShape(Shape.java:943)
	at javafx.graphics/javafx.scene.shape.Shape.doUpdatePeer(Shape.java:998)
	at javafx.graphics/javafx.scene.shape.Shape.access$000(Shape.java:123)
	at javafx.graphics/javafx.scene.shape.Shape$1.doUpdatePeer(Shape.java:131)
	at javafx.graphics/com.sun.javafx.scene.shape.ShapeHelper.updatePeerImpl(ShapeHelper.java:74)
	at javafx.graphics/com.sun.javafx.scene.shape.LineHelper.updatePeerImpl(LineHelper.java:65)
	at javafx.graphics/com.sun.javafx.scene.NodeHelper.updatePeer(NodeHelper.java:102)
	at javafx.graphics/javafx.scene.Node.syncPeer(Node.java:710)
	at javafx.graphics/javafx.scene.Scene$ScenePulseListener.syncAll(Scene.java:2380)
	at javafx.graphics/javafx.scene.Scene$ScenePulseListener.syncAll(Scene.java:2389)
	at javafx.graphics/javafx.scene.Scene$ScenePulseListener.syncAll(Scene.java:2389)
	at javafx.graphics/javafx.scene.Scene$ScenePulseListener.syncAll(Scene.java:2389)
	at javafx.graphics/javafx.scene.Scene$ScenePulseListener.synchronizeSceneNodes(Scene.java:2356)
	at javafx.graphics/javafx.scene.Scene$ScenePulseListener.pulse(Scene.java:2512)
	at javafx.graphics/com.sun.javafx.tk.Toolkit.lambda$runPulse$2(Toolkit.java:412)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at javafx.graphics/com.sun.javafx.tk.Toolkit.runPulse(Toolkit.java:411)
	at javafx.graphics/com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:438)
	at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:519)
	at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:499)
	at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.pulseFromQueue(QuantumToolkit.java:492)
	at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$11(QuantumToolkit.java:320)
	at javafx.graphics/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:96)

Any ideas what's missing to start TilesFx properly?
Thanks in advance
Jens

@HanSolo I also encountered this issue. It is possible that is problem is related on some non findings configurations?
Maybe some missing stylesheets.
Regards

I was able to track it down to the tile. The tile causing this exception is mapTile. What kind of configuration may be missing?

You might want to add 'javafx-web' to the --add-modules because the MapTile is based on the JavaFX WebView.

I can confirm, this solved it. My cmd line is now:

--module-path YOUR_PATH/javafx-sdk-11.0.2/lib --add-modules javafx.graphics,javafx.base,javafx.controls,javafx.fxml,javafx.web

authors: HanSolo chnmrc midi-foot-controller

repo: HanSolo/tilesfx


text:
Instructions on fields in the Buildamic builder display twice

Bug Description
Instructions on fields in the Buildamic builder display twice.
How to Reproduce
Add some instructions for a field in the builder, and look at how it renders when editing entries.
Extra Detail

Environment
Statamic 3.2.2 Pro
Laravel 8.58.0
PHP 8.0.6
edalzell/blade-directives 3.5
handmadeweb/buildamic dev-main

Thanks Jelle,
The bottom instruction was the original that we had, but we had some issues with replicators which prompted us to nest Fields within Statamics publish-field, which seems to include the instruction below the title.
This should now be resolved in https://github.com/HandmadeWeb/buildamic/commit/a6f0bae83c5aedb6232fc4a7ad14202689c9363a

Hi Michael, this is indeed now resolved 🎉

repo: HandmadeWeb/buildamic


text:
v3.1升到v3.2  导致RelativePanel 内容不自适应

代码

V3.1 效果

V3.2 效果

请问如果在V3.2 让 Border  自适应windows 大小。谢谢

测试代码
<Window x:Class="RelativePanel.MainWindow"         xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"         xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"         xmlns:d="http://schemas.microsoft.com/expression/blend/2008"         xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"         xmlns:hc="https://handyorg.github.io/handycontrol"         xmlns:local="clr-namespace:RelativePanel"         mc:Ignorable="d"         Title="MainWindow" Height="450" Width="800">     <hc:RelativePanel>         <Border Background="Red"></Border>     </hc:RelativePanel> </Window>
V3.1 效果

V3.2 效果

3.2 行为和 uwp 中一致，3.1 反而是 bug

@NaBian
那么如果我想在3.2 达到 3.1的效果，请问该怎么办。可能问题简单，但是真心求问

authors: NaBian windsOne

repo: HandyOrg/HandyControl


text:
🛑 French is down

In a56a610, French (https://fr.scratch-wiki.info) was down:

HTTP code: 508
Response time: 1214 ms

Resolved: French is back up in 9f2d6ed.


text:
🛑 English is down

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

HTTP code: 0
Response time: 0 ms

Resolved: English is back up in 398617e after 24 minutes.


text:
🛑 Helite US Site is down

In e358474, Helite US Site (https://www.heliteus.com) was down:

HTTP code: 403
Response time: 341 ms

Resolved: Helite US Site is back up in 146aee4.

repo: Hansen-Distribution/upptime


text:
🛑 Matery博客 is down

In 389c151, Matery博客 (https://www.haoqiyung.ml/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Matery博客 is back up in 177572e.


text:
🛑 AI对话 is down

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

HTTP code: 503
Response time: 227 ms

Resolved: AI绘画 is back up in 83117df after 189 days, 21 hours, 20 minutes.


text:
🛑 Google Scholar is down

In 9fac16c, Google Scholar (https://scholar.haoqiyun.tk/) was down:

HTTP code: 403
Response time: 576 ms

Resolved: Google Scholar is back up in 8de56ae.


text:
🛑 AI调音 is down

In 3b76eef, AI调音 (https://haoqi7-music.hf.space/) was down:

HTTP code: 404
Response time: 52 ms

Resolved: AI对话 is back up in 26ab20b.


text:
🛑 Happy Vibes Bot 5 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 5 is back up in e9adc59.

repo: Happy-Vibes-Bot/status


text:
🛑 Happy Vibes Bot 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 1 is back up in 568a38d.


text:
🛑 Happy Vibes Bot 2 is down

In 46f1667, Happy Vibes Bot 2 ($BOT2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 2 is back up in d6db291.


text:
🛑 Happy Vibes Bot 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Happy Vibes Bot 1 is back up in 435963e.


text:
Modern Menu required ESC to be pressed first before Select works

Description of the bug:
Modern Menu required ESC to be pressed first before Select works
Can you reproduce? If so please list the steps:
Yes, here are the steps to reproduce the bug:

Expected behavior:
Select btn should work before ESC is used, this way a keyboard won't be required
System Information:

OS: Linux RPI 5
GFX Backend: OpenGL

I believe this has already been fixed in LUS, just hasn't been bumped in 2ship yet.

authors: Malkierian retropieuser


text:
没有下拉刷新啊

https://github.com/HarmonyCandies/pull_to_refresh
这个库跟本库合并就完美了 大佬

为什么要合并。。本来就不是一个功能。。两者是独立的个体，不同布局会有不同的下拉刷新效果。。对于个人开发者，根据自身项目封装一套才是合理的。

authors: geeklx zmtzawqlp


text:
Remove screen shake

Remove screen shaking from skills like earthshaker.

This should be easy if the screen shaking is caused by a server packet, otherwise don't know.
It's definitely a viable option for Game Settings, though.

Added in 931457af634ad7e55a9690f0dac4147cf94cd04c

authors: 3vcloud DarkManic HasKha

repo: HasKha/GWToolboxpp


text:
ERROR: Out of memory?

Hey guys, been testing around with layers and what not, i introduced new ppi for my templates and tried generating 250 at 2048x2048 px, now previously ive been able to generate 10k no problem, but these new templates are at 2400ppi and im assuming thats possibly the issue? if anyone can throw me a bone and lmk how to work around that or do i have to decrease the ppi on my templates?
Im a beginner at this, thank you in advance!

are you running this on editor like vscode?

i have same problem .Any idea ? did you solve it ?

Same problem

no solutions yet, tried a fresh re-load of the code and fresh installs of the dependencies yet it still will generate 1 png and give me this error.

you can use external terminal to start the building and dont use Vscode or vs studio .using window cmd will fix this problem .just access the path to the right folder and use the command npm run build and it will work fine ,

I have the same problem for a few days, I can not find a solution, someone knows how to solve it

Has anyone found the answer?

repo: HashLips/generative-art-opensource


text:
Sometimes MDDropdown Menus don't get positioned correctly

Description of the Bug
Sometimes if you open a MDDropdownmenu very early on after running the app, it will create the dropdown in the wrong position.
Code and Logs
from kivy.lang import Builder
from kivymd.app import MDApp
from kivymd.uix.menu import MDDropdownMenu, RightContent
from kivy.properties import ObjectProperty

KV = '''
<RightContentCls>
	disabled: True

	MDIconButton:
		icon: root.icon
		user_font_size: "16sp"
		pos_hint: {"center_y": .5}

	MDLabel:
		text: root.text
		font_style: "Caption"
		size_hint_x: None
		width: self.texture_size[0]
		text_size: None, None

Screen
	GridLayout:
		cols:1
		padding:10

		GridLayout:
			adaptive_height: True
			cols: 2
			pos_hint: {"top": 1}

			MDTextField:
				id: project
				hint_text: "Project"
				text : " "
				icon_right: "arrow-down-drop-circle-outline"
				on_focus: if self.focus: app.callprojectmenu()

			MDTextField:
				id: room
				hint_text: "Room"
				text : " "
				icon_right: "arrow-down-drop-circle-outline"
				on_focus: if self.focus: app.callroommenu()

'''

class RightContentCls(RightContent):
	pass

class Test(MDApp):
	def __init__(self, **kwargs):
		super().__init__(**kwargs)
		self.screen = Builder.load_string(KV)

		projectgroupitems = [{"text":"Project 1"},{"text":"Project 2"}]
		self.projectgroupmenu = MDDropdownMenu(
			caller=self.screen.ids.project,
			items=projectgroupitems,
			position="bottom",
			callback=self.setproject,
			width_mult=4
		)
		roomitems = [{"text": "Room 1"}, {"text": "Room 2"}]
		self.roommenu = MDDropdownMenu(
			caller=self.screen.ids.room,
			items=roomitems,
			position="bottom",
			callback=self.setroom,
			width_mult=4
		)

	def callprojectmenu(self):
		self.projectgroupmenu.open()

	def callroommenu(self):
		self.roommenu.open()

	def setroom(self,instance):
		self.screen.ids.room.text = instance.text

	def setproject(self,instance):
		self.screen.ids.project.text = instance.text

	def build(self):
		return self.screen

Test().run()

Screenshots
https://youtu.be/zkEUEAJr6UM
Versions

OS: Windows 10
Python: 3.7.7
Kivy: 1.11.1
KivyMD: 0.104.1

I've also faced the same issue. When I've used it, the dropdown menu usually ends up in the wrong position after a window resize.

I'm having the same issue. Did you find out how to fix it?

After a quick glance at the kivymd/uix/menu.py file, I realized that calling menu.set_menu_properties(interval) before opening the menu fixes the issue. I'll look into it in detail tomorrow.

Okay, here's what's going on.
When MDDropdownMenu is instantiated, set_menu_properties is called, calculating _start_coords as follows:
self._start_coords = self.caller.to_window(self.caller.center_x, self.caller.center_y)

In some cases, caller.center_x and caller.center_y are not the values we're expecting them to be, because the caller's position has not loaded yet or other reasons. When this happens, the MDDropdownMenu is be placed incorrectly.
In order to fix this, self._start_coords should be updated whenever self.caller.center_x or  self.caller.center_y change. center_x and center_y depend on the numeric properties x and y of a widget, so we can bind them to a function.
Currently, set_menu_properties is called whenever the main window is resized, so I decided to try something similar. I added the following code to the __init__ of MDDropdownMenu:
self.caller.bind(
    x=lambda *_: Clock.schedule_once(self.set_menu_properties, 0.5),
    y=lambda *_: Clock.schedule_once(self.set_menu_properties, 0.5))

Now, whenever the x or y values of the caller change, the set_menu_properties will be called and the _start_coords of the menu will be set to the correct value. In my case, to_window returns incorrect values when set_menu_properties is called instantly after x or y change, probably because the widget tree is still updating. Adding a small delay before calling set_menu_properties fixed this.
I tested this fix on my code and it worked wonderfully. I can upload a minimal working example showing the differences if it's of use. Moreover, I tried this on @pepsakdoek's code and apparently it's working, too. It would be fantastic if @dillon-pinto could try it.
I hope my fix helps people having this issue! I can submit it as a pull request if it's working properly for everybody. 😄

Thanks for looking into it @akaminetzkyp! It partially fixed the bug in my drop-down menus, I have 2 buttons aligned vertically and the fix works only on the right button. I've written up a file that can reproduce the issue, the left button's drop-down menu still ends up in the wrong place after a window resize. Let me know if you're able to reproduce it. Thanks again!
from kivy.lang import Builder
from kivymd.uix.screen import Screen
from kivymd.app import MDApp
from kivy.uix.scrollview import ScrollView
from kivymd.uix.gridlayout import MDGridLayout
from kivymd.uix.button import MDRectangleFlatButton
from kivymd.uix.textfield import MDTextField
from kivymd.uix.boxlayout import BoxLayout
from kivymd.uix.menu import MDDropdownMenu
from kivymd.uix.dropdownitem import MDDropDownItem

class SomeScreen(Screen):
	def __init__(self, **kwargs):
		super(SomeScreen, self).__init__(**kwargs)

		self.grid = MDGridLayout(
			cols=1,
			padding=150,
			spacing=50,
			size_hint=(1, None),
			width=900
		)

		self.grid.bind(
			minimum_height=self.grid.setter('height')
		)

		self.ScrollviewLayout = ScrollView(
			bar_width = 10,
			size_hint=(1, 0.95),
			size=(900, 620),
			pos_hint={'center_x': .5, 'center_y': .4},
			do_scroll_x=False
		)

		self.createMenuButtons()
		self.ScrollviewLayout.add_widget(self.grid)
		self.add_widget(self.ScrollviewLayout)

	def createMenuButtons(self):

		self.button1 =MDRectangleFlatButton()
		self.button1.text = "Button1"
		self.button1.font_size = 15
		self.button1.size=(480, 50)
		self.button1.size_hint=(1, None)
		self.button1.halign='center'
		self.button1.valign='middle'

		self.button2 =MDRectangleFlatButton()
		self.button2.text = "Button2"
		self.button2.font_size = 15
		self.button2.size=(480, 50)
		self.button2.size_hint=(1, None)
		self.button2.halign='center'
		self.button2.valign='middle'

		items1 = [{"icon": "git", "text":  f"{thing}"} for thing in ["Stuff", "More Stuff"]]
		menu1 = MDDropdownMenu(
            caller=self.button1, items=items1,
			width_mult=4,
		)

		items2 = [{"icon": "git", "text": f"{thing}"} for thing in ["Stuff", "More Stuff"]]
		menu2 = MDDropdownMenu(
            caller=self.button2,items=items2,
			width_mult=4,
		)

		self.button1.on_press = menu1.open
		self.button2.on_press = menu2.open

		bl = BoxLayout()
		bl.spacing = 10

		bl.add_widget(self.button1)
		bl.add_widget(self.button2)
		self.grid.add_widget(bl)

class TestApp(MDApp):
    def build(self):
        return SomeScreen()

TestApp().run()

Thanks for checking if the fix works! In my code it's not working all the time, so there's still work to be done.
I'll be pretty busy for a while but I'll try to check this issue again as soon as possible. 😃

No worries! I'll take a look into it too and post updates if I'm able to find a fix.

I've been testing how the bug reacts to sizing. I noticed that, in my case, it happens on window snapping to the edges or corner of the screen. Window snapping doesn't fire the on_resize event handler for the window and holds on to the coordinates before the window snap/resize took place.
So the only way I've found to force the dialog to update the coordinates is by calling set_menu_properties on the first line of MDDropdownMenu's inner open function:
    def open(self):
        """Animate the opening of a menu window."""

        def open(interval):
            self.set_menu_properties(0)

            if not self._calculate_complete:
                return

However, I think this might make some of the binding redundant, including the check_position_caller function. I tested this on Windows so I'm not sure if this is a problem on MacOS or Linux.

That's a fantastic idea! I included it in my code and it looks like it's working properly now.
It would be ideal if we could find a fix that doesn't call set_menu_properties when it's not necessary. However, it looks like your solution is working. Thank you! 🎉

Hi,
could please share an example of how to integrate your following code:
    def open(self):
        """Animate the opening of a menu window."""

        def open(interval):
            self.set_menu_properties(0)

            if not self._calculate_complete:
                return

in the code below?
from kivy.lang import Builder

from kivymd.app import MDApp
from kivymd.uix.menu import MDDropdownMenu

KV = """
#:import toast kivymd.toast.toast

Screen:

    MDToolbar:
        pos_hint: {"top": 1}
        title: "MDDropDownItem"

    MDDropDownItem:
        id: dropdown_item
        text: "Item 0"
        pos_hint: {'center_x': 0.5, 'center_y': 0.6}
        dropdown_bg: [1, 1, 1, 1]
        on_release: app.menu.open()

    MDRaisedButton:
        pos_hint: {'center_x': 0.5, 'center_y': 0.3}
        text: 'Chek Item'
        on_release: toast(dropdown_item.current_item)
"""

class Test(MDApp):
    def __init__(self, **kwargs):
        super().__init__(**kwargs)
        self.screen = Builder.load_string(KV)
        menu_items = [{"icon": "git", "text": f"Item {i}"} for i in range(5)]
        self.menu = MDDropdownMenu(
            caller=self.screen.ids.dropdown_item,
            items=menu_items,
            position="center",
            callback=self.set_item,
            width_mult=4,
        )

    def set_item(self, instance):
        self.screen.ids.dropdown_item.set_item(instance.text)

    def build(self):
        return self.screen

Test().run()

Even if the position of the menu in the above example works fine without your code, it would help to understand how to integrate it in other cases where the issue of the menu wrong position happens. Thank you in advance, some tips will be really helpful

authors: BaggioMarco akaminetzkyp dillon-pinto pepsakdoek

repo: HeaTTheatR/KivyMD


text:
Issue with creating a new environment

I created a new environment by following the steps given in https://github.com/Healthcare-Robotics/assistive-gym/wiki/6.-Creating-a-New-Assistive-Environment.
I created an environment almost similar to BedBathingJacoEnv, but I get an error when I run it using the command python3 -m assistive_gym --env "TaskRobotEnv-v0":
gym.error.UnregisteredEnv: No registered env with id: TaskRobotEnv-v0

Hi Deepak. You may have installed the recent v1.0 of Assistive Gym. I have yet to update the environment creation example for v1.0 (as mentioned in the note at the top of the Wiki page you linked). First, can you check if you have installed v0.1 from this branch?

Hi @Zackory Thanks. v0.1 solved the issue.

repo: Healthcare-Robotics/assistive-gym


text:
ZNC (potential decom?) to Weechat relay

Resolved: [Server] ZNC is back up in f8ecf37.

authors: HeartsDo-Dev heartsbot-dev

repo: HeartsDo-Dev/YnH-Instance-Status


text:
当弹出键盘或者切换键盘的输入方式的时候总会有bug

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

什么bug？

无回应，关闭

repo: HeathWang/HWPanModal


text:
Question: compatible Python 3?

Hi,
I'm a contributor of the French open source project Zeste de Savoir and we think to integrate this project but we have a question: is it compatible with Python 3 or not yet?
Thanks in advance for your answer!

Hi Gerard,
I have not fully adapted it for python 3 yet. I don't think it will take a ton of more work though. If you get to it you can always send me a pull request and I will review and merge it in.

Hi,
2to3 script just ask for compatibility modification such as removing from __future__ import print_function.
I ran tests on a python3 env et everything was good. I think you can use your tox script to generate 2 envs, one with py2 and one with py3 and then run test in those two envs.

Hey,
Any progress on this?
Thanks

Hi Gerard,
I don't have any bandwidth at the moment. You can submit a pull request and I will review if you need it sooner.

authors: GerardPaligot artragis dbkaplan mkohram

repo: Helioscene/dry-rest-permissions

license: isc


text:
[FEATURE] Option to disable "Create a new secret" button

Description
Options to hide both the "Convert text to base64" and/or "Create a new secret" buttons on a shared secret link.
And a way to skip the whole "View the secret" button would be a welcome addition as well heh
Screenshots

Additional information
No response

Hello, @akzkak

You can disable people from creating secrets from the settings page of the application
No, there will not be a "skip the whole view the secret button". The reason for this button is that if the secret opens instantly, it will be opened by social media when you share them (they crawl the url).

Made my frontend private via reverse proxy and only backend /secret themself are public. My goal is to make it as simple for non tech savvy people to receive there secret. So no user accounts required or "unnecessary" stuff on the page.
Understandable.

Can close again if request is simply to obscure. sry

I understand what you mean. I will open the issue again, and see how Hemmelig will behave going forward. I am currently redesigning and changing the features a bit.

authors: akzkak bjarneo


text:
Add context-sensitive grammars

Add context-sensitive grammars to Grammar.jl.
(Parts of) functionality can be copied from ExprRules.
Also see https://github.com/Herb-AI/Search.jl/pull/4#discussion_r1097058513.

The iterators should work the same as in context-free grammar, just call some function to propagate constraints at every expansion (basically filter viable candidates), as in here: https://github.com/Herb-AI/ExprRules.jl/blob/master/src/csgrammar/iterators.jl#L48
The function for propagating constraints: https://github.com/Herb-AI/ExprRules.jl/blob/master/src/csgrammar/iterators.jl#L4


text:
Anchor Texture (Bug???)

Not entirely sure if this would be considered an issue but when you blow up the anchor during the fade out the original anchor texture shows. This happened while around 60-80ms I have no idea if it happens on any lower ping yet.
This isn't a major problem but can look a bit odd when using packs that change the way anchors look.
A bit difficult to see but i tried to get a screenshot and video (video & screenshot taken on east.uspvp.org)

https://github.com/user-attachments/assets/60a1ca8e-0323-422e-9fd3-c11f29687013

Yes that's intended as a placeholder to be visible. I do have plans on making it work with packs but currently it'll keep looking that way. If you don't like it you can change the textures in assets/herosanchoroptimizer/textures or change the model of fake_anchor to be of a respawn anchor

repo: HerobaneNair/herosanchoroptimizer


text:
Personal filters for list pages (Instances/Requests)

As a end user I would like to:

Create a filter for a page (E.g: instances) where I set flags like my email as spoc
Save the filter
From the instance page on top right corner I have a dropdown with all filters I have created
I select a filter and click "apply"

Duplicate of #703 .
Closing this one

repo: HewlettPackard/squest