[URGENT SOMEONE PLEASE HELP] Can someone help me in resolving the issue mentioned in this link https://github.com/kubernetes-incubator/service-catalog/issues/1867

My controller manager is not working and I am getting this issue: https://github.com/kubernetes-incubator/service-catalog/issues/1867
I am not able to add servicecatalog.k8s.io apiservice to my api list(kubectl api-versions) because of which I am not able to register service broker.

@nivedhan-murugavel can you provide more details?  Is your controller-manager pod constantly being restarted because it is failing health checks?
Can you post the kubectl describe output for the catalog controller manager pod?
You could post your controller manager logs ie output from kubectl logs -l app=catalog-catalog-controller-manager -n catalog

@jboyd01 Thanks for the reply.
I am getting following error in controller manager log
I0610 07:09:30.930792       1 round_trippers.go:405] GET https://<IP_ADDRESS>:443/apis/automationbroker.io/v1 200 OK in 0 milliseconds
I0610 07:09:30.930819       1 round_trippers.go:411] Response Headers:
I0610 07:09:30.930826       1 round_trippers.go:414]     Content-Type: application/json
I0610 07:09:30.930830       1 round_trippers.go:414]     Content-Length: 804
I0610 07:09:30.930834       1 round_trippers.go:414]     Date: Sun, 10 Jun 2018 07:09:30 GMT
I0610 07:09:30.930848       1 request.go:874] Response Body: {"kind":"APIResourceList","apiVersion":"v1","groupVersion":"automationbroker.io/v1","resources":[{"name":"jobstates","singularName":"jobstate","namespaced":true,"kind":"JobState","verbs":["delete","deletecollection","get","list","patch","create","update","watch"]},{"name":"servicebindings","singularName":"servicebinding","namespaced":true,"kind":"ServiceBinding","verbs":["delete","deletecollection","get","list","patch","create","update","watch"]},{"name":"serviceinstances","singularName":"serviceinstance","namespaced":true,"kind":"ServiceInstance","verbs":["delete","deletecollection","get","list","patch","create","update","watch"]},{"name":"bundles","singularName":"bundle","namespaced":true,"kind":"Bundle","verbs":["delete","deletecollection","get","list","patch","create","update","watch"]}]}
F0610 07:09:30.931273       1 controller_manager.go:232] error running controllers: unable to start service-catalog controller: API GroupVersion {"servicecatalog.k8s.io" "v1beta1" "clusterservicebrokers"} is not available; found map[schema.GroupVersionResource]bool{schema.GroupVersionResource{Group:"", Version:"v1", Resource:"namespaces"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"nodes/status"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"persistentvolumes/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"deployments"}:true, schema.GroupVersionResource{Group:"networking.k8s.io", Version:"v1", Resource:"networkpolicies"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"deployments/status"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"replicasets"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"daemonsets"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"deployments"}:true, schema.GroupVersionResource{Group:"batch", Version:"v1", Resource:"jobs/status"}:true, schema.GroupVersionResource{Group:"automationbroker.io", Version:"v1", Resource:"servicebindings"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"statefulsets/status"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1beta1", Resource:"localsubjectaccessreviews"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1beta1", Resource:"subjectaccessreviews"}:true, schema.GroupVersionResource{Group:"autoscaling", Version:"v1", Resource:"horizontalpodautoscalers"}:true, schema.GroupVersionResource{Group:"policy", Version:"v1beta1", Resource:"poddisruptionbudgets"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1beta1", Resource:"roles"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"deployments"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"ingresses/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"controllerrevisions"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"statefulsets/status"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1", Resource:"subjectaccessreviews"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1beta1", Resource:"selfsubjectrulesreviews"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"services"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"networkpolicies"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"deployments/scale"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1beta1", Resource:"clusterroles"}:true, schema.GroupVersionResource{Group:"admissionregistration.k8s.io", Version:"v1beta1", Resource:"mutatingwebhookconfigurations"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"replicationcontrollers/status"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"resourcequotas/status"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"services/proxy"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"deployments/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"deployments"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"componentstatuses"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/attach"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/binding"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"secrets"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"services/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"daemonsets/status"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"configmaps"}:true, schema.GroupVersionResource{Group:"autoscaling", Version:"v2beta1", Resource:"horizontalpodautoscalers"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1", Resource:"clusterroles"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"persistentvolumes"}:true, schema.GroupVersionResource{Group:"apiextensions.k8s.io", Version:"v1beta1", Resource:"customresourcedefinitions"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"statefulsets/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"replicasets/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"statefulsets"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"statefulsets"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"replicasets/scale"}:true, schema.GroupVersionResource{Group:"autoscaling", Version:"v2beta1", Resource:"horizontalpodautoscalers/status"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"namespaces/status"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/exec"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/log"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/portforward"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"daemonsets/status"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"deployments/rollback"}:true, schema.GroupVersionResource{Group:"certificates.k8s.io", Version:"v1beta1", Resource:"certificatesigningrequests"}:true, schema.GroupVersionResource{Group:"apiextensions.k8s.io", Version:"v1beta1", Resource:"customresourcedefinitions/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"daemonsets/status"}:true, schema.GroupVersionResource{Group:"authentication.k8s.io", Version:"v1", Resource:"tokenreviews"}:true, schema.GroupVersionResource{Group:"apiregistration.k8s.io", Version:"v1beta1", Resource:"apiservices/status"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"deployments/scale"}:true, schema.GroupVersionResource{Group:"automationbroker.io", Version:"v1", Resource:"serviceinstances"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"replicationcontrollers/scale"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1", Resource:"clusterrolebindings"}:true, schema.GroupVersionResource{Group:"storage.k8s.io", Version:"v1", Resource:"storageclasses"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"replicationcontrollers"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"replicasets/scale"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"replicasets"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1", Resource:"selfsubjectaccessreviews"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/proxy"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"deployments/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"replicasets/scale"}:true, schema.GroupVersionResource{Group:"authentication.k8s.io", Version:"v1beta1", Resource:"tokenreviews"}:true, schema.GroupVersionResource{Group:"certificates.k8s.io", Version:"v1beta1", Resource:"certificatesigningrequests/approval"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"nodes/proxy"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"resourcequotas"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"deployments/status"}:true, schema.GroupVersionResource{Group:"batch", Version:"v1beta1", Resource:"cronjobs"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1beta1", Resource:"clusterrolebindings"}:true, schema.GroupVersionResource{Group:"policy", Version:"v1beta1", Resource:"poddisruptionbudgets/status"}:true, schema.GroupVersionResource{Group:"automationbroker.io", Version:"v1", Resource:"jobstates"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"replicasets"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"replicasets/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"statefulsets/scale"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"daemonsets"}:true, schema.GroupVersionResource{Group:"events.k8s.io", Version:"v1beta1", Resource:"events"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"podsecuritypolicies"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"deployments/scale"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1", Resource:"roles"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"podtemplates"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"replicasets/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"deployments/rollback"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"statefulsets/scale"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"statefulsets/scale"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"namespaces/finalize"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"persistentvolumeclaims"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1beta1", Resource:"selfsubjectaccessreviews"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"replicationcontrollers"}:true, schema.GroupVersionResource{Group:"autoscaling", Version:"v1", Resource:"horizontalpodautoscalers/status"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1beta1", Resource:"rolebindings"}:true, schema.GroupVersionResource{Group:"storage.k8s.io", Version:"v1beta1", Resource:"storageclasses"}:true, schema.GroupVersionResource{Group:"automationbroker.io", Version:"v1", Resource:"bundles"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"events"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"limitranges"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"nodes"}:true, schema.GroupVersionResource{Group:"apiregistration.k8s.io", Version:"v1beta1", Resource:"apiservices"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"daemonsets"}:true, schema.GroupVersionResource{Group:"batch", Version:"v1", Resource:"jobs"}:true, schema.GroupVersionResource{Group:"extensions", Version:"v1beta1", Resource:"ingresses"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta2", Resource:"deployments/scale"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1", Resource:"localsubjectaccessreviews"}:true, schema.GroupVersionResource{Group:"admissionregistration.k8s.io", Version:"v1beta1", Resource:"validatingwebhookconfigurations"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"serviceaccounts"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"controllerrevisions"}:true, schema.GroupVersionResource{Group:"authorization.k8s.io", Version:"v1", Resource:"selfsubjectrulesreviews"}:true, schema.GroupVersionResource{Group:"batch", Version:"v1beta1", Resource:"cronjobs/status"}:true, schema.GroupVersionResource{Group:"rbac.authorization.k8s.io", Version:"v1", Resource:"rolebindings"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"persistentvolumeclaims/status"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1beta1", Resource:"controllerrevisions"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"bindings"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"endpoints"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"pods/eviction"}:true, schema.GroupVersionResource{Group:"", Version:"v1", Resource:"replicationcontrollers/scale"}:true, schema.GroupVersionResource{Group:"apps", Version:"v1", Resource:"statefulsets"}:true, schema.GroupVersionResource{Group:"certificates.k8s.io", Version:"v1beta1", Resource:"certificatesigningrequests/status"}:true}

And I don't see servicecatalog.k8s.io in kubectl api-versions
admissionregistration.k8s.io/v1beta1 apiextensions.k8s.io/v1beta1 apiregistration.k8s.io/v1beta1 apps/v1 apps/v1beta1 apps/v1beta2 authentication.k8s.io/v1 authentication.k8s.io/v1beta1 authorization.k8s.io/v1 authorization.k8s.io/v1beta1 autoscaling/v1 autoscaling/v2beta1 batch/v1 batch/v1beta1 certificates.k8s.io/v1beta1 events.k8s.io/v1beta1 extensions/v1beta1 networking.k8s.io/v1 policy/v1beta1 rbac.authorization.k8s.io/v1 rbac.authorization.k8s.io/v1beta1 storage.k8s.io/v1 storage.k8s.io/v1beta1 v1
@jboyd01  Kindly help me understand what i am missing here.

@nivedhan-murugavel Working on getting a new release of our helm chart pushed out (for v0.1.21) which may fix what you are seeing (it has a fix for missing ca certs which are causing healthz checks to fail on the controller manager).
I'll ping back when it's ready to try.

@carolynvs That would really help. Thanks a lot.
When can i expect it to be fixed, any ETA? And is there any beta version of your fix so that I can try?

@nivedhan-murugavel I tested v0.1.21 and am still able to reproduce this behavior. :-( So no fix yet.
On AKS I am seeing that the controller manager deployment is actually healthy, the /healthz liveliness and readiness probes are just so flaky that k8s is restarting the pod over and over. After editing the deployment manually and deleting those probes, service catalog is working fine for me.
If you try that out, I would really appreciate knowing if everything works fine for you, or if there are still problems.

@nivedhan-murugavel can you post the service catalog API Server and Controller Manager logs?  i.e.,
kubectl logs -l app=catalog-catalog-controller-manager -n catalog
and
kubectl logs -l app=catalog-catalog-apiserver -n catalog  -c apiserver
You might want to put these in a gist, they can be quiet large.

Ok, this doesn't appear to be related to problems with the health check then. Hopefully with the logs, we can figure it out.

@jboyd01 @carolynvs I have added the gist for controller and apiserver logs
controller Manager log gist -- https://gist.github.com/nivedhan-murugavel/ac08dcf2e5e6648e748524d052885cdd
Apiserver log gist -- https://gist.github.com/nivedhan-murugavel/98529f61370ffc3f87c782e91b38ad51

Hi @nivedhan-murugavel, what's the output of kubectl get apiservices ?
The APIService resource tells the aggregator to register your aggregated API. There should be an entry for the service catalog API group. If there isn't, none of the API aggregation stuff is going to work.

Hi @pmorie This is my kubectl get apiservices
NAME                                   AGE v1.                                    2d v1.apps                                2d v1.authentication.k8s.io               2d v1.authorization.k8s.io                2d v1.autoscaling                         2d v1.batch                               2d v1.networking.k8s.io                   2d v1.rbac.authorization.k8s.io           2d v1.storage.k8s.io                      2d v1beta1.admissionregistration.k8s.io   2d v1beta1.apiextensions.k8s.io           2d v1beta1.apps                           2d v1beta1.authentication.k8s.io          2d v1beta1.authorization.k8s.io           2d v1beta1.batch                          2d v1beta1.certificates.k8s.io            2d v1beta1.events.k8s.io                  2d v1beta1.extensions                     2d v1beta1.policy                         2d v1beta1.rbac.authorization.k8s.io      2d v1beta1.servicecatalog.k8s.io          2h v1beta1.storage.k8s.io                 2d v1beta2.apps                           2d v2beta1.autoscaling                    2d

hmmm servicecatalog is in there.  API and Controller logs don't have issues that jump out to me at least. (Thanks for formatting @MHBauer!)

actually, @nivedhan-murugavel , this is different from what you posted 2 days ago in https://github.com/kubernetes-incubator/service-catalog/issues/2100#issuecomment-396129317
Can you try $kubectl get  clusterservicebrokers   and $kubectl get clusterserviceclasses

@jboyd01 I am really sorry for that confusion. I get this error when i run kubectl get clusterservicebrokers
error: the server doesn't have a resource type "clusterservicebrokers"
Thanks @MHBauer for formatting :)

@nivedhan-murugavel, no problem.  2 days ago you ran that get apiservices command and catalog wasn't present in the output but now it is.  Interesting that Kubernetes is saying it doesn't know about clusterservicebrokers though.

@jboyd01 Ya. Because of this I am not able to use aws service broker :(

Really interesting details from the describe apiservices (timeout):
Name:         v1beta1.servicecatalog.k8s.io
Namespace:
Labels:       <none>
Annotations:  <none>
API Version:  apiregistration.k8s.io/v1beta1
Kind:         APIService
Metadata:
  Creation Timestamp:  2018-06-12T15:21:58Z
  Resource Version:    227770
  Self Link:           /apis/apiregistration.k8s.io/v1beta1/apiservices/v1beta1.servicecatalog.k8s.io
  UID:                 58ee2df7-6e54-11e8-897d-0291b40d66f8
Spec:
  Ca Bundle:               LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1ekNDQWMrZ0F3SUJBZ0lCQVRBTkJna3Foa2lHOXcwQkFRc0ZBREFWTVJNd0VRWURWUVFERXdwemRtTXQKWTJGMExXTmhNQjRYRFRFNE1EWXhNakUxTWpFMU4xb1hEVEk0TURZd09URTFNakUxTjFvd0ZURVRNQkVHQTFVRQpBeE1LYzNaakxXTmhkQzFqWVRDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBS1lKCmg4WGpRdFpnS3YrMzN2NjZneEJJK0VEV2dBOTFmWDJSanpVNjRUbVpMN1RyTFozaVFCdzhFckROVmgzMDQwb3IKS1NjUjdTRkVpRHpKT2p1R2JGeXF2N0NITmVPT3VkVVdLTy9TelpzZXQ4Zks2cU5ZK1RaVzdXYmdPTTAzVmg5cAp1dlYvUFRZK1RwWmx4ZkF2NWtWbDBwUTRyZjZhUExWY21mbFcrUGExS25qSUxKZU9KUlgyeEF5TDBCU1lBSWxCCmxzUGpzV2NWaFpyeHcwZ1ZWUjJ1SW1SRG96K2JYTVJGcm1Xbit2TU0vZFRTWlh6YWRYUWhpT1NzOXZVazVkU1cKRkJGNmRQVG9JOFp0UXZpL0NmRnpPTVAwZkNmZitjMEdydFJPZjlEN2d4L3Z6QkJ2a2ZDZU5Qa1lnK0NqUm0wLwpiY1Y0aUtOOWozUHdYMGdjRUpVQ0F3RUFBYU5DTUVBd0RnWURWUjBQQVFIL0JBUURBZ0trTUIwR0ExVWRKUVFXCk1CUUdDQ3NHQVFVRkJ3TUJCZ2dyQmdFRkJRY0RBakFQQmdOVkhSTUJBZjhFQlRBREFRSC9NQTBHQ1NxR1NJYjMKRFFFQkN3VUFBNElCQVFBRXRWTnJaL1U2eGJYSVlnbzR1RHJMcFQ5OHR6a3ViUzlROHlMSkpmTTVUeUZpZW90QQp2aGNzQ1FKN1h4ZW5YOWM0K0lGRlVNelMrTkNOV093VnBBSDkwNjVZbXlJTHhVbERMSTBkeWE5dytudGtDZC8vCnZucmZ2bVNKSks2ZmwyR0pkbHA3YU9pYk12bHkxTEpHcmFrZlJlY2pNVlI3dlFkM3RlTjFBaDhUZ1hNdlROYjMKanM2U3FuM3RZS3JUVzdTWmZpRW43bnZRd0FBU21XMmlobFd4VlJVdmlhaktFc0dGb0NPcHJIeEhoTmEvaDF6YwpmSzJOS1Jsb3ZNK2tSWXorS09iZlVVZGwxWUF3QmIwb25uZC9ERy96KytCSTcyaEV5Ry8xT3pOanUxclZBVXRPCmE2T01hRCtOSzVjaHBycXpwUkdZNmNLZHd3VU05ZmY0aGV1NQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
  Group:                   servicecatalog.k8s.io
  Group Priority Minimum:  10000
  Service:
    Name:            catalog-catalog-apiserver
    Namespace:       catalog
  Version:           v1beta1
  Version Priority:  20
Status:
  Conditions:
    Last Transition Time:  2018-06-12T15:22:16Z
    Message:               no response from https://<IP_ADDRESS>:8443: Get https://<IP_ADDRESS>:8443: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available
Events:                    <none>

@nivedhan-murugavel Did you add back the health checks after we figured out that wasn't the problem? I want to make sure that our poking around hasn't masked the root problem.

@carolynvs  I didnt add that back. I will add and share the output now

@carolynvs I have added readiness and liveness probe back to apiserver-deployment.yaml and controller-manager.yaml file. Started seeing crashloopback for apiserver and controller manager.
logs for controller-manager after adding reading and liveness probe -- https://gist.github.com/nivedhan-murugavel/25940e2479984d54347260b774708f9b
logs for apiserver after adding reading and liveness probe -- https://gist.github.com/nivedhan-murugavel/83d148e671af4d042cf9f541bb019eaf
kubectl describe apiservices -- https://gist.github.com/nivedhan-murugavel/fcf9f54a50c81c8f3ee603d462d88d68
Let me know if you need more information. Thanks in advance

healthz check etcd failed: etcd failed to reach any server

Can you describe the service catalog apiserver? Also maybe a kubectl get pods --all-namespaces to make sure that dns and other key stuff is up.

(x5 over 18m)  kubelet, ip-172-31-28-242.us-west-2.compute.internal  Readiness probe failed: HTTP probe failed with statuscode: 500

That's the type of stuff (along with the client timeout and EOF errors) that I'm trying to hunt down. Thanks for the logs, that panic is very helpful to me!
That said I'm not sure what's wrong with your installation... On the other clusters, I'm seeing that the health checks are flakey and turning them off lets you use service catalog. But it seems like there is more going on for your cluster.

I have created k8s cluster in aws using kops.  Created in specific VPC and subnet. Then tried installing service catalog using helm. Didnt do anything much.

Yes and No. 😂
Yes, that's the trigger for the healthchecks being flakey, they don't seem to handle being on separate nodes well. That's why I don't see that problem on minikube but do on "real" clusters.
No, AFAIK that is not the cause of your problems with getting apiserver to work. For me it's enough to turn off the health probes to stop k8s from flapping my pods. But that wasn't enough to fix your cluster.

I've got a PR open to make the probes optional in the service catalog chart, https://github.com/kubernetes-incubator/service-catalog/pull/2121. Otherwise I haven't had luck figuring out the root cause yet.

Can you please mention someone you know using k8s cluster created in aws using kops and service catalog integrated with that cluster?

I don't know anyone using aws, or kops.

Thanks @carolynvs. Will try once that PR is merged and ready. But as @jboyd01 said, My master is not able to ping the catalog apiserver and when I do kubectl describe apiservices v1beta1.servicecatalog.k8s.io I am seeing FailedDiscoveryCheck
Namespace:
Labels:       <none>
Annotations:  <none>
API Version:  apiregistration.k8s.io/v1beta1
Kind:         APIService
Metadata:
  Creation Timestamp:  2018-06-14T13:26:12Z
  Resource Version:    42514
  Self Link:           /apis/apiregistration.k8s.io/v1beta1/apiservices/v1beta1.servicecatalog.k8s.io
  UID:                 81e6fc9e-6fd6-11e8-b153-02bc125971c4
Spec:
  Ca Bundle:               LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1ekNDQWMrZ0F3SUJBZ0lCQVRBTkJna3Foa2lHOXcwQkFRc0ZBREFWTVJNd0VRWURWUVFERXdwemRtTXQKWTJGMExXTmhNQjRYRFRFNE1EWXhOREV6TWpZeE1sb1hEVEk0TURZeE1URXpNall4TWxvd0ZURVRNQkVHQTFVRQpBeE1LYzNaakxXTmhkQzFqWVRDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBS1dpCjdIQ21KK0FDU0ZKQkF0U1dvZkNDY2lPVXpuT1NrMzNYcjl5dTRLeHhQanJRSC9DeHpBS2t6cks4NkNmZVVHaHMKY0NmWUVucVdpTEQ2bFk0RzNBVVdwd203bTh2dy9jNkR0Qzl4cG5DeGdIYVhpaUlLSmZUWXc1cWhZNVgyemZQSwpNOEY1WTdIdkpES0VjOVJsaVlveHN4NmFLTXQ4VS9Da05JR0M1RHZYbzVja2UrSVVmR0cyZ1UyZ2NhZU41dXd2CkZNeVNBMkxNOHNYUUlnVFJFMTlzeHZZQkNQandlcnRIdnd5K3g0K240SjJDM0RsZFZxSDJkUUF2Ky8zcFRwTzcKcHJlbC9QZlhpdEpwZTN6ZTErRWtTSjhuaU42YWMrVzkySzNpdHVmUlU5TUZMOHJCdE40MXl3N2o5eXNQbEQxNgoxWnFvT2hDWVdvR2tmN1kyRnRjQ0F3RUFBYU5DTUVBd0RnWURWUjBQQVFIL0JBUURBZ0trTUIwR0ExVWRKUVFXCk1CUUdDQ3NHQVFVRkJ3TUJCZ2dyQmdFRkJRY0RBakFQQmdOVkhSTUJBZjhFQlRBREFRSC9NQTBHQ1NxR1NJYjMKRFFFQkN3VUFBNElCQVFBRU5vd2JTOHFyZU5weHJnQ0R2dHFsb0I5THlRVUo1L25FSlA0KzEzazk4NG83K1ZPNApFNFlJTmRuTzYrZmc0TjFUK1RLSC83bWE1YmxrRXJpMVVLZFV3TEd1b294b2FlQ0hxZEZJYTFDdEJHbUlzR05RCjNWelRQWmZySVZCVU1sVFN4aTB3QnlQeU5vYVQxVVZsT1RFclpvMkhkeUhFMDU1UC9iQXFJTDBvNG5ONEFQVGoKYzhpTERrK1Z6cHV2NFJxY0hOZlJaMmpmSDU2VE4wcWl0YWpHWUVsSDdMNTNlSzAxL0s1N08wNEVzUjI3L2FMTgoxdXBEMisvUEZ1RVhXREJzVGdVMUlSK1ZjblNrOWI5MFpJVWdHYkRaRkNLRFRmcHBOQWtUaFB2bE16QlRwZkRzCkZRZVFGQ3lKM0RyVTBjN25ySWdkU2s3UEFRcVIvQjgxZitsQQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
  Group:                   servicecatalog.k8s.io
  Group Priority Minimum:  10000
  Service:
    Name:            catalog-catalog-apiserver
    Namespace:       catalog
  Version:           v1beta1
  Version Priority:  20
Status:
  Conditions:
    Last Transition Time:  2018-06-14T13:26:12Z
    Message:               no response from https://<IP_ADDRESS>:443: Get https://<IP_ADDRESS>:443: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available
Events:                    <none>

To be clear there's more going on with your cluster than what I am currently investigating with the probe issues. 😀
I don't have great ideas on what is wrong however, so I'm hoping that Jay or some other people can help troubleshoot.

@nivedhan-murugavel After syncing with the other maintainers, it's clear from your most recent error messages that this is a problem with your cluster's configuration, and isn't something that we in SIG Service Catalog can help with further.
I am closing this for now and suggest that maybe you follow up with Amazon support, or the k8s slack channels for amazon or kops maybe. This is beyond our ability to assist.
After you get your cluster setup and healthy, I'd suggest a complete reinstall of service catalog. If you are still seeing problems with service catalog after that, let us know.

Hey,
I've run into exactly this issue while deploying service catalog to GKE.
I followed the same troubleshooting steps listed above and when I get to kubectl describe apiservices v1beta1.servicecatalog.k8s.io I noticed that there was also an error connecting to the APIServer.
  Conditions:
    Last Transition Time:  2018-08-24T20:52:28Z
    Message:               no response from https://<IP_ADDRESS>:8443: Get https://<IP_ADDRESS>:8443: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available```

After troubleshooting further from another pod, I noticed a TLS error when querying the APIServer:

```/ # curl -v https://<IP_ADDRESS>:8443
* Rebuilt URL to: https://<IP_ADDRESS>:8443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html```

To workaround this for now, I've set the following values:
`controllerManager.apiserverSkipVerify: true` & `useAggregator: false`.

Essentially the fix is to set `--service-catalog-insecure-skip-verify=true` on the Controller Manager however in the chart you also need to disable use of the Aggregated API for this to work?

@carolynvs Should the ability to disable TLS verification not be depending if using the aggregator or not? I'm happy to raise a PR for this, if you feel this makes sense.

Cheers,
Tom

have any solution?

Get Cluster-IP of your service-catalog server
kubectl -n=kube-system get catalog
Add the IP to no_proxy variable in the kube-apiserver config
vi /etc/kubernetes/manifests/kube-apiserver.yaml
systemctl daemon-reload && systemctl restart kubelet
should work now kubectl get --raw "/apis/metrics.k8s.io/v1beta1/nodes"

I'm having a very similar issue on a cluster deployed to a private VPC connected to an on prem network. I noticed that I am unable to install and get the errrors mentioned above with both a kops and eks cluster on this network topology. I have no issues with any other pods having traffic issues. I was able to install on a standard eks install not attached to this VPC. It appears the underlying network somehow matters with the service catalog. I can't understand why that would matter but it certainly does. Should I look for some underlying network setting? This seems like a problem with the service catalog since all other pods seem to work fine.

Which errors? How are you installing? What values are you setting in
helm that differ from the defaults?
On 4/19/19 11:51:21, 2tim wrote:

I'm having a very similar issue on a cluster deployed to a private VPC
connected to an on prem network. I noticed that I am unable to install
and get the errrors mentioned above with both a kops and eks cluster
on this network topology. I have no issues with any other pods having
traffic issues. I was able to install on a standard eks install not
attached to this VPC. It appears the underlying network somehow
matters with the service catalog. I can't understand why that would
matter but it certainly does. Should I look for some underlying
network setting? This seems like a problem with the service catalog
since all other pods seem to work fine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes-2Dincubator_service-2Dcatalog_issues_2100-23issuecomment-2D484985055&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=e9Q_fL6yJ1tRnDYacvK4VbZTlp3j3KeLby3ygzQR8e8&s=T6l9-IGFD2fbq1AQ9H7MTKQkUk2C2AP7A-SFZMvSZPg&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADFYGAOSHC2GBONJLOBJ6HTPRIICTANCNFSM4FD55CIQ&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=e9Q_fL6yJ1tRnDYacvK4VbZTlp3j3KeLby3ygzQR8e8&s=O6mbVvMG4nIH3BuQweU6Th-cplM0SXWwM7Mos--_v2c&e=.

It’s a default helm install. I was able to talk to someone on the slack
channel for sig-service-catalog and I think it has something to do with the
pod that holds the api server and Etcd containers. The apiserver is not
able to connect to etcd, but only with the private network topology
mentioned. This seems strange since the communication is purely between the
containers in one pod and not outside of the cluster network.
On Fri, Apr 19, 2019 at 2:13 PM Morgan Bauer<EMAIL_ADDRESS>wrote:

Which errors? How are you installing? What values are you setting in
helm that differ from the defaults?
On 4/19/19 11:51:21, 2tim wrote:

I'm having a very similar issue on a cluster deployed to a private VPC
connected to an on prem network. I noticed that I am unable to install
and get the errrors mentioned above with both a kops and eks cluster
on this network topology. I have no issues with any other pods having
traffic issues. I was able to install on a standard eks install not
attached to this VPC. It appears the underlying network somehow
matters with the service catalog. I can't understand why that would
matter but it certainly does. Should I look for some underlying
network setting? This seems like a problem with the service catalog
since all other pods seem to work fine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes-2Dincubator_service-2Dcatalog_issues_2100-23issuecomment-2D484985055&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=e9Q_fL6yJ1tRnDYacvK4VbZTlp3j3KeLby3ygzQR8e8&s=T6l9-IGFD2fbq1AQ9H7MTKQkUk2C2AP7A-SFZMvSZPg&e=
,
or mute the thread
<
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADFYGAOSHC2GBONJLOBJ6HTPRIICTANCNFSM4FD55CIQ&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=e9Q_fL6yJ1tRnDYacvK4VbZTlp3j3KeLby3ygzQR8e8&s=O6mbVvMG4nIH3BuQweU6Th-cplM0SXWwM7Mos--_v2c&e=
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/issues/2100#issuecomment-484989869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHPPPSWXTVYXKJDL2MTKMTPRIKURANCNFSM4FD55CIQ
.

I'm still seeing this error. Please anyone help me resolve this issue. here are my logs.
root@master-1:~# kubectl get pods -n catalog -o wide
NAME                                                  READY   STATUS             RESTARTS   AGE     IP             NODE       NOMINATED NODE   READINESS GATES
catalog-catalog-apiserver-848d64556d-rmphw            1/2     Running            2          2d18h   <IP_ADDRESS>   worker-1
catalog-catalog-controller-manager-5cd85b4768-d4xrg   0/1     CrashLoopBackOff   648        2d18h   <IP_ADDRESS>   worker-1
root@master-1:~# kubectl describe apiservice v1beta1.servicecatalog.k8s.io
Name:         v1beta1.servicecatalog.k8s.io
Namespace:
Labels:
Annotations:
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
Creation Timestamp:  2019-05-31T12:07:16Z
Resource Version:    16807
Self Link:           /apis/apiregistration.k8s.io/v1/apiservices/v1beta1.servicecatalog.k8s.io
UID:                 a1e32195-839c-11e9-a3ed-005056a5efb4
Spec:
Ca Bundle:               LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM5ekNDQWQrZ0F3SUJBZ0lSQU1tQjBKWnB4cmdlN05GdXV1RnYzT0F3RFFZSktvWklodmNOQVFFTEJRQXcKRlRFVE1CRUdBMVVFQXhNS2MzWmpMV05oZEMxallUQWVGdzB4T1RBMU16RXhNakE0TVRkYUZ3MHlPVEExTWpneApNakE0TVRkYU1CVXhFekFSQmdOVkJBTVRDbk4yWXkxallYUXRZMkV3Z2dFaU1BMEdDU3FHU0liM0RRRUJBUVVBCkE0SUJEd0F3Z2dFS0FvSUJBUUR1VWtBTG1MZEQ4R0RWRW1qN21XQ1diRk01SXRVQ3pOVElNeVBQdmZzYmdUYmwKS2pKLzlLSEJKQTdsdnc3dVJQMzJIT0g5U0FYSUxueUpsZmFrSFlwVm5GL2xYRHVHbWh1WWVMVEJYNkxpSXVqTwppcitHcmg2N01jaWhjcGZpM05ncWE0R1Ztc0Y0dXFINVMxQ0luVksxOWNzbkFpOEVnUDRhTElZVGhvNGo2YUxFClFzOStDaWJVSzI5YURER3BaVFlIQkJPV3FCMHJSQnA0VHdTdnpmZ3NjUk05K05aek9MeStuUTl4aFhDckxGZFoKRW1Xa1pCOGk1QVBXb0Vzcmo1RlVqYnQ0aE1IenZ2YUpxY20ycjIrL0VqM29YWlJjbWJ2QWI2bE05ODB1T1E1LwpJWlI4dHViN1F2V3VtdEk2WWh1VDZPSVo2a0FjYlZwMjY2Yy9mNGFaQWdNQkFBR2pRakJBTUE0R0ExVWREd0VCCi93UUVBd0lDcERBZEJnTlZIU1VFRmpBVUJnZ3JCZ0VGQlFjREFRWUlLd1lCQlFVSEF3SXdEd1lEVlIwVEFRSC8KQkFVd0F3RUIvekFOQmdrcWhraUc5dzBCQVFzRkFBT0NBUUVBcXZqQ0Z3UVBib1E0SWNpa3Y4QktWOS9iWlNregpvcW4xM3M3aGloWFRQaDN4eHNxNFRrektja1lrQmxXUHNUYTZscjlFcnR6QUpxSE41UnRlNU1kU2VOM2tFaXZ2ClJSdkpiZlRxNHV0SExRZE9FQ3h5QlpaeXQ0N2l2dzQwMm1Rd1RaaTZxcExjdE5qd3c4d2NTaWlOOFFsZjcyaFUKR0VROEtQc0NXb283dExWMUR5V0ZIL1NjTWNTQXdIT2lPUHRVVlhZOHZFdElKZzRnY0l4UkQ4UmVQQVhEcmVWWApycFRjb3JidmxxZE1TeEo1RXR0eFNRQWg1bDdDZm1INlI0ZlhLMGRtSlZqdXRzV29sdnQwS2ZPUlhmR2YvbnZ2CmpzTnFDQ3RHa3FnbVFVTXl6WGhuKzE2dG1VVUZ0QjFCc2U3enFxTkhwVlpuU0VPRlNEU2lMYWgxcGc9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
Group:                   servicecatalog.k8s.io
Group Priority Minimum:  10000
Service:
Name:            catalog-catalog-apiserver
Namespace:       catalog
Version:           v1beta1
Version Priority:  20
Status:
Conditions:
Last Transition Time:  2019-05-31T12:07:16Z
Message:               no response from https://<IP_ADDRESS>:443: Get https://<IP_ADDRESS>:443: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Reason:                FailedDiscoveryCheck
Status:                False
Type:                  Available
Events:
root@master-1:~# kubectl logs -l app=catalog-catalog-apiserver -n catalog -c apiserver
I0603 06:26:37.330140       1 round_trippers.go:438] POST https://<IP_ADDRESS>:443/apis/authorization.k8s.io/v1beta1/subjectaccessreviews 201 Created in 3 milliseconds
I0603 06:26:37.330187       1 round_trippers.go:444] Response Headers:
I0603 06:26:37.330198       1 round_trippers.go:447]     Audit-Id: 53954d61-8dab-452c-98a1-bc159b30174c
I0603 06:26:37.330202       1 round_trippers.go:447]     Content-Type: application/json
I0603 06:26:37.330204       1 round_trippers.go:447]     Content-Length: 406
I0603 06:26:37.330206       1 round_trippers.go:447]     Date: Mon, 03 Jun 2019 06:25:35 GMT
I0603 06:26:37.330222       1 request.go:942] Response Body: {"kind":"SubjectAccessReview","apiVersion":"authorization.k8s.io/v1beta1","metadata":{"creationTimestamp":null},"spec":{"nonResourceAttributes":{"path":"/healthz","verb":"get"},"user":"system:anonymous","group":["system:unauthenticated"]},"status":{"allowed":true,"reason":"RBAC: allowed by ClusterRoleBinding "system:discovery" of ClusterRole "system:discovery" to Group "system:unauthenticated""}}
I0603 06:26:37.330316       1 handler.go:153] service-catalog-apiserver: GET "/healthz" satisfied by nonGoRestful
I0603 06:26:37.330392       1 pathrecorder.go:240] service-catalog-apiserver: "/healthz" satisfied by exact match
I0603 06:26:37.330462       1 wrap.go:47] GET /healthz: (4.621411ms) 200 [kube-probe/1.13 <IP_ADDRESS>:36412]
root@master-1:~# kubectl logs -l app=catalog-catalog-controller-manager -n catalog
I0603 06:27:51.438881       1 round_trippers.go:438] GET https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s 503 Service Unavailable in 0 milliseconds
I0603 06:27:51.438892       1 round_trippers.go:444] Response Headers:
I0603 06:27:51.438895       1 round_trippers.go:447]     Date: Mon, 03 Jun 2019 06:26:49 GMT
I0603 06:27:51.438898       1 round_trippers.go:447]     Audit-Id: ca4c0c96-5369-429f-b514-6d47b4b41aef
I0603 06:27:51.438900       1 round_trippers.go:447]     Content-Type: text/plain; charset=utf-8
I0603 06:27:51.438902       1 round_trippers.go:447]     X-Content-Type-Options: nosniff
I0603 06:27:51.438904       1 round_trippers.go:447]     Content-Length: 20
I0603 06:27:51.438921       1 request.go:942] Response Body: service unavailable
I0603 06:27:51.438981       1 request.go:1145] body was not decodable (unable to check for Status): couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:"apiVersion,omitempty""; Kind string "json:"kind,omitempty"" }
E0603 06:27:51.438987       1 controller_manager.go:311] Failed to get supported resources from server: the server is currently unable to handle the request
root@master-1:~# kubectl logs -l app=catalog-catalog-controller-manager -n catalog
I0603 06:22:24.632755       1 round_trippers.go:444] Response Headers:
I0603 06:22:24.632758       1 round_trippers.go:447]     Audit-Id: 590bb801-175c-4e17-9a44-cc8ab672f0af
I0603 06:22:24.632760       1 round_trippers.go:447]     Content-Type: text/plain; charset=utf-8
I0603 06:22:24.632762       1 round_trippers.go:447]     X-Content-Type-Options: nosniff
I0603 06:22:24.632764       1 round_trippers.go:447]     Content-Length: 20
I0603 06:22:24.632766       1 round_trippers.go:447]     Date: Mon, 03 Jun 2019 06:21:22 GMT
I0603 06:22:24.632777       1 request.go:942] Response Body: service unavailable
I0603 06:22:24.632833       1 request.go:1145] body was not decodable (unable to check for Status): couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:"apiVersion,omitempty""; Kind string "json:"kind,omitempty"" }
E0603 06:22:24.632848       1 controller_manager.go:311] Failed to get supported resources from server: the server is currently unable to handle the request
F0603 06:22:24.632869       1 controller_manager.go:236] error running controllers: failed to get api versions from server: "timed out waiting for the condition", "the server is currently unable to handle the request"


How to check if opponent is playing an alt animation

Describe your problem here.
I'm trying to make an animation of an object play only when the opponent hits an alt animation. I can get it to work, but only when the note itself is an alt animation, and not when the 'play alt animation' box is checked. How can I set it to also play when the 'play alt animation' box is checked?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

altAnim
https://github.com/ShadowMario/FNF-PsychEngine/wiki/Lua-Script-API:-Variables#gameplay-variables

I'm trying to implement that, but it still isn't working, but only for the altAnim variable
Is this how to correctly make the if statement:
if getProperty('altAnim') == true or noteType == 'Alt Animation' then

You don't use getProperty, it's a shortcut

so its just if altAnim == true or noteType == 'Alt Animation' then to be clear

== true is redundant but yes


[BUG] Can't scroll on DWCj Main Development Page "Welcome to DWCJ"

I have 18 Samples 1 for each 18 Controls and I need to always specify the overflow: scroll attribute in order to scroll and test my samples...

This is most likely not an issue. So I'm closing it.


fix a bug where oldNode was null on every step

Should fix https://github.com/socraticorg/mathsteps/issues/77. As far as I could see there was no point setting oldNode to null in Status.reset. The tests are still passing so I assume I didn't do something completely silly by removing it. Fingers crossed.

yeah, I think this would fix it. Thanks for figuring that out!
I was trying to remember why the reset() function exists at all, to see if this change breaks anything, but it's only used in one place, so let's just scrap reset()?
So instead of this change, can you just delete the reset function, and then in simplifyExpression/stepThrough.js:

delete the line nodeStatus.reset();
change nodeStatus = step(nodeStatus.newNode); into

const nextNode = Status.resetChangeGroups(nodeStatus.newNode);
nodeStatus = step(nextNode);

(or something like that)
How's that sound?

Yeah I think that sounds reasonable.

Should be good to merge!


introduce Boost climatology; scale Boost output; include Brown Carbon for AOD

This PR is non-zero-diff for OH.
It is intended to complete v1.1.0 .
It depends on the following other repositories:
GEOSgcm: 6866df080aa0734737ea5a7d1d4985a67bb9f363
GEOSgcm_GridComp: fbc9b5ca145fbc163eec32bd3c82e68994f38c84
GEOSchem_GridComp: 916c59b9b9a366a6094ec077a4de4f5d6187605e
GOCART: 6e237a8ed45f742a5a68695e0e8180aa096ad188
GEOSgcm_App: 839a2696dc15592bb16fba22c9f0313b4579acaf
Additions:

Added a scaling factor to scale OH by a constant
Added exports for OH
Added NOTES.wiki, instructions on how to compile & use, a duplicate of the GitHub wiki for QuickChem;
this is to help us track how it changes over time
Changes:
Moved to GitHub Actions for label enforcement
Changed OH Boost file to be climatology rather than single month
Changed AOD calculation to include Brown Carbon scattering coefficient

Until this PR is approved, and QuickChem v1.1.0 is released,  the process of building the code is:
Clone GEOSgcm
git checkout 6866df080aa0734737ea5a7d1d4985a67bb9f363
edit components.yaml and make the entry for QuickChem  'main'  instead of v1.1.0
mepo clone
cd to QuickChem
git merge feature/mmanyin/add_brown_carbon
Then build as usual


LDPI sizes is calculated wrong

currently it's calculated 0.5x mdpi (baseline)
but according to http://developer.android.com/guide/practices/screens_support.html it should be 0.75x mdpi

Fixed by #109


File integrity check redux

The first time around it was implemented too primitively and that is my fault for assuming too much 😸
This time I've broken it down into a more robust process:

Get content-length header
Get local file size in bytes
Calculate size in bytes of the metadata added to each track
Subtract metadata size in bytes from the local file size
Add metadata size in bytes to the content-length
Compare the final sizes

Another thing is that we encode files regardless of if they are complete or not, a simple check with mutagen of the track duration against the track duration listed in the metadata before encoding should fix that. (possibly initiating a retry or skip track + error message?

Some findings so far:
Calculating the size of the metadata doesn't seem to be as simple as putting all the metadata into one long string, encoding it as utf-8, and returning the length. Even adding the text for the id3 tags itself it still doesn't seem to add up. Mutagen documentation is kinda crazy but from what I gather there is no clear-cut way of calculating the byte size of metadata.
Seems the simplest solution here is:

Check local filesize before encoding

If local != remote its incomplete, retry a few times then skip if unsuccessful (while printing an error)

Use a temporary filename

Until encoding is complete use a temporary filename (.tmp suffix) so that even if the file is complete but the script is interrupted during the encoding process a user can simply re-run the command and it can skip the download and move right to encoding again for that file.

Leave a temporary file in the output directory:

So that if bandcamp-dl is simply run without a url but a basedir and it finds a not.finished (random name) file in the output directory it simply picks up where it left off (not.finished would be a plain text file containing the url and options for that particular session)

Last one is kinda interesting I could see this being useful for those trying to download everything an artist released and not having to manually restart failed downloads. An option like --retry-all that takes a path and searches directories recursively for not.finished files and automatically finishes the process for each would be neat.
This reminds me that we don't take artist links yet only albums/individual tracks therein, id like to rectify that at some point 😞

All done, I believe I've made it pretty dang robust now 😸


fixes to Django 3.0

@PetrDlouhy,
Thanks for the PR. If you want to fix the tests to passing we could probably get this merged in. You could remove testing for python 2.7.

@epicserve Now the tests are fixed. I had to update django-mptt, so I hope that it was not held down for some reason, that would break something.


strange img loadimage animation

Hello there,
my load image just fades in on first reload but on the following reloads it does a size-animation from left bottom to right top. Is there a way to control or style this animation.
Here is the style:
infscr-loading{
position:fixed;
bottom:20px;
left:50%;

}
you can also take a look at:
http://lovlylinks.tumblr.com/
I guess I have to change something in the source as mentioned here (https://github.com/paulirish/infinite-scroll/issues/91) but I couldnt get anything out of this.
thanks for any advice.

The loading animation actually expends #infscr-loading from width & height : 0 to width & height : auto, in javascript.
You can indeed set the speed to 0, but then all the animations are gone.
So depending on the effet you want on your page, you can override it with CSS.
For example, the CSS below would make sure that the div wouldn't change width (no animation from the left), but would keep the fade and "opening from top to bottom" animation :
#infscr-loading {
	width: auto !important;
}

And if you'd like to get rid of the height and fade animation as well, here is en example :
#infscr-loading {
	width: auto !important; height: auto !important;
	opacity: 1 !important;
}

(As for opacity, be sure to use all the necessary prefixes and syntaxes, as it's not supported in every browser.)
I know using "!important" isn't the best thing in the world, but in this case it's the only way if you want to avoid rewriting the plugin in itself.

Thanks for your solution @mh-nichts!

Infinite Scroll v3 is out!. It's an all new re-write, so take a look at how to upgrade from v2.
Infinite Scroll v3 has a new setup for loading and status elements. See status option. This uses your own HTML.

End of content

No more pages to load

status: '.page-load-status'

I recommend upgrading to v3. Please open a new issue if you run into trouble with Infinite Scroll v3.


feat: support prettier@^3

PR Checklist

[x] Addresses an existing open issue: fixes #40
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
I tested this out locally and it looks like all is well in both v2 and v3. https://github.com/prettier/prettier/wiki/How-to-migrate-my-plugin-to-support-Prettier-v3%3F indicates nothing specific to preprocessors.

@all-contributors please add @joshuakgoldberg for code.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


[Bug]: RTL glitches and i18n missing strings

Version

[x] I'm using version 1.15.1

Known issues

[X] I've checked Known issues

Existing issues

[X] I've checked Existing issues

Advanced Preferences

[X] I've checked Advanced Preferences

What operating system are you using?
macOS
Operating System Version
Sonoma 14.2.1
Reproduction steps

Switch to Hebrew or Arabic
Open the preferences

Reproduces how often: Always
Expected Behavior
Should align neatly
Actual Behavior
Some elements misbehave and some are not translated
The top bar is aligned to the left.
The text under the heart icon is LTR.
The words seconds and minutes are untranslated.
The speaker icon is too close to the text.
Relevant log output
No response
Preferences
No response
Additional information

Code of Conduct

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

Hi,
translations are community effort, you can help here: https://hosted.weblate.org/projects/stretchly/
Unfortunately, I don't speak Hebrew or Arabic so not sure how it should look like. PRs would be appreciated.

@hovancik I am translating this project already :)
The problem is the RTL alignment and the fact that these terms are translated yet appear in the native language regardless, as you can see in the screenshots.

Gotcha, the syncing process to the app is manual, so new translations appear once I make a new version.

Hmmm I highly doubt that, this string was translated around 2 years ago:
https://hosted.weblate.org/translate/stretchly/stretchly/he/?q=minutes&sort_by=-priority%2Cposition&checksum=#history
And it was submitted to the repository:
https://github.com/hovancik/stretchly/blob/7038e073e6048f6f55a292595fbdef01eec2e334/app/locales/he.json#L205
It looks like an i18n issue, I can't verify it with other languages but it does look like it.

Seems like we have it wrong?
    "minutes_one": "דקה",
    "minutes_two": "{{count}} דקות",
    "minutes_many": "{{count}} דקות",
    "minutes_other": "{{count}} דקות",

This https://jsfiddle.net/6bpxsgd4 suggests it should be _one, _two, _other. But not sure why extra element would be an issue.

Ah, other languages have the same issue, will try to look at it. Do you remember if this was issue as well in previous versions?

So it seems it's not issue with i18next but with how I am refreshing translations after changing language. Can you try hitting Cmd+R after changing the language? For me I can see correct translations then:

Or after Stretchly restarts / Preferences gets reopened

Thank you!
What about the RTL glitches I've  mentioned?

Could you please explain / show how the correct one should look like? It's hard for me to imagine what is wrong
The top bar is aligned to the left.
The text under the heart icon is LTR.

Settings should be rightmost, then Scheduling, Themes and About, while the support button should appear leftmost.
Regarding the text on the support button, this is the right form:
תמיכה ב־Stretchly (Starting from the right).
The current wrong layout is:
תמיכה ב־Stretchly
It looks like Stretchly Support instead of vice versa.
Thanks :)

Thanks, regarding Support button, I guess translation should be changed? "heart": "תמיכה ב־Stretchly",
Others seems to fit:

Ah, I think I found it. Is this correct?

Great! It looks way better!
The "Preferred language" box has its combobox arrow aligned to the right instead of left but I think it's a small price to pay after all the great job you've been doing, thank you :)

Thanks for all the feedback, I think I was able to fix the select as well :)

Thank you so much!
One last thing that I've noticed and I'm not sure it's possible to fix without setting the whole system to RTL:

This is what I see on Linux, but no idea what the correct way is:

From what I read in Electron docs, there is no such an option in Menus :(


Move pre-start scripts from init containers into the regular container

By running the pre-start scripts in init containers, they are executed sequentially. In bosh they are all running in parallel.
Describe the solution you'd like
We already have the container-run mechanism to execute post-start scripts, so we could just extend that tool to add support for pre-start scripts as well.
As a side effect this will also cut down significantly on the total number of init containers, as right now one is created for each job in the instance group. Most of them will simply do nothing if the corresponding job doesn't have a pre-start script.
Describe alternatives you've considered
The alternative would be to do nothing. The current mechanism works, and is probably only slightly slower (and has additional clutter in the pod spec for all the additional init containers).

The container-run command is missing a README, but apparently we use it to run  a command and a post-start with optional conditions.
It's also listening to a socket, to start/stop the command?
Now we want to also execute multiple processes in parallel for pre-start?
This sounds more and more like an init system.

This sounds more and more like an init system.

But isn't that already what it is? 😄
I do understand the concern, and wouldn't have suggested doing this if we didn't already have container-run for running post-start processes.
If we don't want to do this, then at least the operator should not generate additional init containers for jobs that don't even have a pre-start script. The generated pod specs look more like un-optimized generated machine code than hand-crafted description that are accessible for human inspection.
I agree though that this is rather low priority.

:)
Note to self:

the operator should not generate additional init containers for jobs that don't even have a pre-start script

This is about BOSH pre-start https://github.com/cloudfoundry-incubator/cf-operator/blob/master/pkg/bosh/bpmconverter/container_factory.go#L127-L135

Based on measuring init container start times, parallelization of pre-start scripts (both BPM and BOSH kinds) wouldn't help. We've optimized the longest running init containers, but for kubecf long startup times are caused by serial startup.


Forms provide more control over when they validate.

Callers can manually validate by calling validate(), or tell the Form to
validate on every change by setting the autovalidate parameter.
Fixes https://github.com/flutter/flutter/issues/7219


HUE-9721 [Django Upgrade] upgrading Django 2.1.15 to 2.2.17

Actually don't why CI passing python3 because it is showing an error name as ModuleNotFoundError: No module named 'djangomako'.
Then i was trying to install the django from  https://github.com/ahmedaljazzar/django-mako.
But after installing this i am getting another error as TypeError: __init__() got an unexpected keyword argument 'loaders'  shown in ss.
So basically this is line https://github.com/cloudera/hue/blob/master/desktop/core/src/desktop/settings.py#L256 where we have loaders as an argument. @romainr

Actually don't why CI passing python3 because it is showing an error name as ModuleNotFoundError: No module named 'djangomako'.
Then i was trying to install the django from  https://github.com/ahmedaljazzar/django-mako.
But after installing this i am getting another error as TypeError: __init__() got an unexpected keyword argument 'loaders'  shown in ss.
So basically this is line https://github.com/cloudera/hue/blob/master/desktop/core/src/desktop/settings.py#L256 where we have loaders as an argument. @romainr

Have you checked if the django mako lib is compatible enough? (or it is actually the good one)
Would be good to test a fresh Python 3 install indeed.
Could be related or not but some commits on top of the older Django https://github.com/cloudera/hue/commit/222225088e9686aecbb62c810f1189589c1f1f32#diff-0eafb3696d5bbab002d3d1ab6dd48a9b679c1c01b13fef0febad7170be006ca2

Have you checked if the django mako lib is compatible enough? (or it is actually the good one)
Would be good to test a fresh Python 3 install indeed.
Could be related or not but some commits on top of the older Django https://github.com/cloudera/hue/commit/222225088e9686aecbb62c810f1189589c1f1f32#diff-0eafb3696d5bbab002d3d1ab6dd48a9b679c1c01b13fef0febad7170be006ca2

Have you checked if the django mako lib is compatible enough? (or it is actually the good one)
Would be good to test a fresh Python 3 install indeed (as the CI container might have the good dependencies already as some pieces are pre-built).
Could be related or not but some commits on top of the older Django 2222250#diff-0eafb3696d5bbab002d3d1ab6dd48a9b679c1c01b13fef0febad7170be006ca2

Checked on a fresh install python3 and it is giving ModuleNotFoundError: No module named 'djangomako'
And not too much written on the github of djangomako (don't think that it is good, not supported after 2.0)
But didn't find the better one for djangomako.

Have you checked if the django mako lib is compatible enough? (or it is actually the good one)
Would be good to test a fresh Python 3 install indeed (as the CI container might have the good dependencies already as some pieces are pre-built).
Could be related or not but some commits on top of the older Django 2222250#diff-0eafb3696d5bbab002d3d1ab6dd48a9b679c1c01b13fef0febad7170be006ca2

Checked on a fresh install python3 and it is giving ModuleNotFoundError: No module named 'djangomako'
And not too much written on the github of djangomako (don't think that it is good, not supported after 2.0)
But didn't find the better one for djangomako.

Have you tried https://github.com/ahmedaljazzar/django-mako/issues/10?
pip3 intall git+https://github.com//ahmedaljazzar/django-mako
(can even experiement with your custom local/remote repo)

Have you tried https://github.com/ahmedaljazzar/django-mako/issues/10?
pip3 intall git+https://github.com//ahmedaljazzar/django-mako
(can even experiement with your custom local/remote repo)

Also http://doconix.github.io/django-mako-plus/
And also read more about Mako: https://www.makotemplates.org/community.html
https://groups.google.com/g/mako-discuss?pli=1
https://groups.google.com/g/mako-discuss/c/gzB0zq2GEKQ/m/zvO7vkBuAQAJ
And if those do not plug-in looks like we will have to port it to Django 2+ (or see how we could transition out of mako for Py3)

Also http://doconix.github.io/django-mako-plus/
And also read more about Mako: https://www.makotemplates.org/community.html
https://groups.google.com/g/mako-discuss?pli=1
https://groups.google.com/g/mako-discuss/c/gzB0zq2GEKQ/m/zvO7vkBuAQAJ
And if those do not plug-in looks like we will have to port it to Django 2+ (or see how we could transition out of mako for Py3)

django-mako-plus

After following the steps given. in http://doconix.github.io/django-mako-plus/install_existing.html#existing-project got this ss https://drive.google.com/file/d/1J6XSzTwO-DMAVhmD1wVxJtUXgJY-XZFr/view?usp=sharing.

Then following the ss I need to add some context_processor in deflaut DjangoTemplate ( I think they are not running in the 'django-mako-plus') and one app in the 'INSTALLED_APP' (settings.py). After adding those Hue opens up but editors are not loading and giving error. (ss -> https://drive.google.com/file/d/1BnfI1ZV91mlrF7TwCYIz6dqUJ7kr0VuV/view?usp=sharing)

change in code (ss -> https://drive.google.com/file/d/17n0svfOMs_WyzxkXRyewdGFKZw_Riys1/view?usp=sharing)

django-mako

after install this there is an error "TypeError: init() got an unexpected keyword argument 'loaders'"
No code change in this.

3 . Also tried with 'djmako' and 'djangox-mako' but not provided the proper documentation and the last development was 6 to 8 years back in those connectors.

And also searching for some documentation related to it. (i.e. what things change in django 2.2 such that it is giving error with django-mako but not found anything which relates it)

Quick debug, FWIW:
./build/env/bin/pip install Django==2.2.17
./build/env/bin/pip install djangomako

vim ~/build/env/lib/python3.8/site-packages/djangomako/backends.py
    self.context_processors = options.pop('context_processors', [])
    options.pop('loaders')  # New line 43
    self.lookup = Environment(**options)

And
TypeError: __init__() got an unexpected keyword argument 'loaders'

Seems gone (but it might break)
ERRORS:
?: (admin.E402) 'django.contrib.auth.context_processors.auth' must be enabled in DjangoTemplates (TEMPLATES) if using the default auth backend in order to use the admin application.
?: (admin.E404) 'django.contrib.messages.context_processors.messages' must be enabled in DjangoTemplates (TEMPLATES) in order to use the admin application.
?: (admin.E406) 'django.contrib.messages' must be in INSTALLED_APPS in order to use the admin application.

And deactivating the Admin app and Hue loaded properly and could execute a query:
git diff
diff --git a/desktop/core/src/desktop/settings.py b/desktop/core/src/desktop/settings.py
index bf673fcce8..24ed46c3e7 100644
--- a/desktop/core/src/desktop/settings.py
+++ b/desktop/core/src/desktop/settings.py
@@ -196,7 +196,7 @@ INSTALLED_APPS = [
     'django.contrib.sites',
     'django.contrib.staticfiles',

-    'django.contrib.admin',
+    # 'django.contrib.admin',
     'django_extensions',

     # 'debug_toolbar',
diff --git a/desktop/core/src/desktop/urls.py b/desktop/core/src/desktop/urls.py
index ecbb9b5069..e33b4d23dd 100644
--- a/desktop/core/src/desktop/urls.py
+++ b/desktop/core/src/desktop/urls.py
@@ -58,7 +58,7 @@ handler403 = 'desktop.views.serve_403_error'
 handler404 = 'desktop.views.serve_404_error'
 handler500 = 'desktop.views.serve_500_error'

-admin.autodiscover()
+# admin.autodiscover()

 # Some django-wide URLs
 dynamic_patterns = [
@@ -221,9 +221,9 @@ dynamic_patterns += [
   url(r'^scheduler/', include('desktop.lib.scheduler.urls'))
 ]

-dynamic_patterns += [
-  url(r'^admin/?', admin.site.urls),
-]
+# dynamic_patterns += [
+#   url(r'^admin/?', admin.site.urls),
+# ]

 if ENABLE_PROMETHEUS.get():
   dynamic_patterns += [

By default we have BTW:
/build/env/bin/pip freeze | grep -i mako
djangomako==1.2.1
Mako==1.0.7

We might want to upgrade or downgrade it to see if cleaner to fix this way.
https://pypi.org/project/Mako/#history

After https://github.com/cloudera/hue/pull/1767
we might not even need the change in djangomako/backends.py
So to retry ./build/env/bin/pip install Django==2.2.17 after and validate.


Description Change?

I'm thinking we should update the description from "TEMPLATE: Meme captioning activity for classes" to "TEMPLATE: Octocat captioning activity for classes" to reflect the change in activity.

Description updated! 👍

Awesome.  Thank you @parkerbxyz.


add code editor

Description

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

close issue #38

需要删除中间的 issue，关联语法为：`close #id`

顶部的标题可以加上 type。例如：`feat: add code editor`

文档记得安排一下～


ERROR TypeError: You provided an invalid object where a stream was expected

I have this error after adding angular-material-fileupload to my app. Funny thing is I cannot reproduce this error in https://stackblitz.com/edit/angular-materia-file-upload. But I don't think this is fault of my error in my code cause error is pointing to matFileUpload.esm.js.MergeMapOperator and I don't use this one.

Please share the deps in package.json.

I also see now that upload and remove buttons doesnt work after this error cause in this https://stackblitz.com/edit/angular-materia-file-upload without error works fine

@Adam-Michalski, Was trying these deps on my side, couldn't replicate the error.
Can you please provide the command which you were trying? Also when i was trying the stackblitz link you posted, the only error i get is
OPTIONS http://localhost:8180/jax-rs-jersey-application-sample net::ERR_CONNECTION_REFUSED
Since i don't have a service running. So did you make sure that the upload service is running?

I have the same issue, I ll come back if I figure it out or have additional details.

Same issue here - same as @idzer0lis. Any fix?

In other projects, I've had this error when there's been a mismatch in RxJS-versions. The internal checks in RxJS fails because Symbol_observable differs in this function and throws.
Experiment with npm ls rxjs and see if you can get consistency.
| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>deduped
+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>deduped
`--<EMAIL_ADDRESS>
When all mine became 6.5, at least my error disappeared.


Hide this Bulb?

i want it to come when i am on the line not always.
Originally posted by @niksingh710 in https://github.com/nvimdev/lspsaga.nvim/discussions/1375

Which bulb are you referring to? The one at the line number column or at the closing brace of the struct?

Which bulb are you referring to? The one at the line number column or at the closing brace of the struct?

to be exact the on } one but if possible would like to hide both.

Did you checkout the docs for the config options?
You can do the following:
require('lspsaga').setup {
  lightbulb = {
    enable = false, -- disables both
    virtual_text = false, -- disables just the one at the end of the line
  },
}

lightbulb = {
    enable = false, -- disables both
    virtual_text = false, -- disables just the one at the end of the line
  },

Sorry for late response, I was AFK.
I can ensure that this works and thanks a lot.
it was hard to find in documentation.


feat: [Draft] [Japanese] support construction_order in path definitions.

Signed-off-by: hsgwa<EMAIL_ADDRESS>Description

Related links
This branch is copied into:
https://github.com/tier4/CARET_analyze/tree/draft_support_construction_order

Notes for reviewers

Pre-review checklist for the PR author

[ ] I've confirmed the contribution guidelines.
[ ] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR has been properly tested.
[ ] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] (Optional) The PR has been properly tested with CARET_report verification.
[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Change to support construction order is made in https://github.com/tier4/CARET_analyze/pull/261
This draft PR is closed now.
(CC: @miyakoshi-dev )


[ddp] add set_params_to_ignore for ColoDDP

Implement #1107

Can we have some unitests?

Can we have some unitests?

Yes, unit test is added


Export visualizations using .carto

Instead of manually created Markdown files, test the .carto export function.

Seems like the data is exported as well, which wouldn't make sense for us (multiple maps on same data + lots of data).

Moreover, the .carto files are binary, so not readable outside CartoDB and not useful for tracking in GitHub. Let's stick with the Markdown files.


Cairo Notification Area: Missing Battery & WiFi Icons (ASUS K55 Laptop) Temporary Fix Inside

Describe the bug
Cairo Notification Area is missing the battery status icon and WiFi list icon.
Steps to reproduce

Install Cairo
Reboot with/without shell assigned
Doesn't display Battery or WiFi List

Expected behavior
A clear and concise description of what you expected to happen.
All Notification and Explorer Trays to be assigned to Cairo
System information:

Windows version: Windows 10 Enterprise LTSC
Cairo version: 0.3.6842.0
32-bit or 64-bit: 64 Bit
In Cairo Settings > Advanced, is Cairo set as shell?: Yes/No Same effects either way.

Additional context
Add any other context about the problem here.
Temporary Fix

Cairo Settings>Menu Bar>Un-Check Enable Notification Area>Re-Check Enable Notification Area (To give restart Cairo option)>Launch Windows Task Manager>Find Windows Explorer>End Task>Click Restart Cairo

Screenshots
Don't think there is a need for this one, if you'd like one I will be happy to reproduce and send and I do it daily
Suggestion
1.Add a feature to force close Windows Explorer first then relaunch Cairo. (Something like a bat file that is linked in the start menu or similar idea)
THE CREAM
I don't like to leave contributors feeling sour. This software is beautiful in the way it operates other than a few minor glitches. I hope to you guys see this threw and someday convert it to a Linux based interface as well. Its very sleek, and the EXACT thing for the person who likes to have a clean operating interface. There is nothing their other then what I want and I've even added my own web link shortcuts to the tray. BEAUTIFUL WORK & STELLAR CODING. Keep it up.

This is implemented in this build if you would like to give it a try before release.

I am wondering if this is still an issue? I believe recent updates should have helped this situation.


rpiCamera saturation parameter

Which version are you using?
v0.22.0
Which operating system are you using?

[ ] Linux amd64 standard
[ ] Linux amd64 Docker
[ ] Linux arm64 standard
[x] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
I have an issue with implementation of https://github.com/aler9/mediamtx/issues/1111 with my rpiCamera NoIR.
I want to set the colors in a grey scale, since i don't want a blue-pink world. The saturation parameter with libcamera sets colors to a greyscale when set to 0, as specified in https://www.raspberrypi.com/documentation/computers/camera_software.html#libcamera-vid :
--saturation			Set image colour saturation <number>

The given  adjusts the colour saturation. The value zero produces a greyscale image, the value 1.0 uses the default amount of sautration, and values greater than 1.0 apply extra colour saturation.
Description
Describe how to replicate the issue
Setting the saturation to 0 in mediamtx.yml parameter or launching docker run with MTX...._SATURATION=0 doesn't set the colors to greyscale mode. It looks like the saturation is in a default value 1.

start the server
publish with ... docker and my own parameters of mediamtx.yml or in docker run parameters
read with ... vlc or frigate on homeassistant with ffmpeg

Did you attach the server logs?

no
Did you attach a network dump?

no

I have the same issue on arm64 standard.  I can't tell if it is a saturation issue or an AWB problem. I have set rpiCameraAWB to greyworld which is accepted fine by the yaml parser but I cannot seem to get rid of the pink.
Does anyone know which file actually reads these yaml settings and processes them for the piOS system? I'm not familiar with go, but am happy to have a look and play to see if I can work out where the problem really is.  Just need a hint as to where to start

Hello, this is caused by the fact that the server interprets the "zero" value as the default value, and replaces it with the default value, which in case of saturation is 1.
This behavior will be changed.

I have the same issue on arm64 standard. I can't tell if it is a saturation issue or an AWB problem. I have set rpiCameraAWB to greyworld which is accepted fine by the yaml parser but I cannot seem to get rid of the pink.
Does anyone know which file actually reads these yaml settings and processes them for the piOS system? I'm not familiar with go, but am happy to have a look and play to see if I can work out where the problem really is. Just need a hint as to where to start

Greyworld has been implemented in AWB for raspivid, but not in Libcamera-vid. I've tried the config.txt parameter awb_auto_is_greyworld=1 too, it seems limited to raspivid too.

Same problem with IMX477 and 462, pink video.

Hello,
I pulled the 0.22.2, i tried both giving the parameter in the run command and in the mediamtx.yml file, it seems like i still can't get my saturation to 0. Is anyone else still having the problem ?

fixed in v0.23.0


Fix links to mashape.com

The API is not available at https://market.mashape.com/dmitrykey/russiansentimentanalyzer.
The correct link — https://rapidapi.com/insider-insider-default/api/russiansentimentanalyzer

hey @overmanager thanks for reporting the issue! I have fixed the README. Code changes coming shortly.


csvs-to-sqlite: linking click version 7 explicitly to pass build

The fix was copied from watson.
Motivation for this change
The application is requesting click in version 7.
related: https://github.com/simonw/csvs-to-sqlite/issues/80
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"

 asbachb@nixo-t14s  ~/dev/src/nix/nixpkgs   fixup/csvs-to-sqlite  nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
$ git -c fetch.prune=false fetch --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0
$ git worktree add /home/asbachb/.cache/nixpkgs-review/rev-009e1287b54111b31a60ad1e9cb530aab762c72a-dirty-1/nixpkgs 9f761047cc4d3a7d6b9bbf498fd4f93864e9b311
Preparing worktree (detached HEAD 9f761047cc4)
Updating files: 100% (27778/27778), done.
HEAD is now at 9f761047cc4 Merge pull request #137425 from SuperSandro2000/typora
$ nix-env --option system x86_64-linux -f /home/asbachb/.cache/nixpkgs-review/rev-009e1287b54111b31a60ad1e9cb530aab762c72a-dirty-1/nixpkgs -qaP --xml --out-path --show-trace
No diff detected, stopping review...
$ git worktree prune

[x] Tested execution of all binary files (usually in ./result/bin/)

 ✘ asbachb@nixo-t14s  ~/dev/src/nix/nixpkgs/result/bin  ./csvs-to-sqlite --help
Usage: csvs-to-sqlite [OPTIONS] PATHS... DBNAME

  PATHS: paths to individual .csv files or to directories containing .csvs

  DBNAME: name of the SQLite database file to create

Options:
  -s, --separator TEXT         Field separator in input .csv
  -q, --quoting INTEGER        Control field quoting behavior per csv.QUOTE_*
                               constants. Use one of QUOTE_MINIMAL (0),
                               QUOTE_ALL (1), QUOTE_NONNUMERIC (2) or
                               QUOTE_NONE (3).

  --skip-errors                Skip lines with too many fields instead of
                               stopping the import

  --replace-tables             Replace tables if they already exist
  -t, --table TEXT             Table to use (instead of using CSV filename)
  -c, --extract-column TEXT    One or more columns to 'extract' into a
                               separate lookup table. If you pass a simple
                               column name that column will be replaced with
                               integer foreign key references to a new table
                               of that name. You can customize the name of the
                               table like so:     state:States:state_name

                               This will pull unique values from the 'state'
                               column and use them to populate a new 'States'
                               table, with an id column primary key and a
                               state_name column containing the strings from
                               the original column.

  -d, --date TEXT              One or more columns to parse into ISO formatted
                               dates

  -dt, --datetime TEXT         One or more columns to parse into ISO formatted
                               datetimes

  -df, --datetime-format TEXT  One or more custom date format strings to try
                               when parsing dates/datetimes

  -pk, --primary-key TEXT      One or more columns to use as the primary key
  -f, --fts TEXT               One or more columns to use to populate a full-
                               text index

  -i, --index TEXT             Add index on this column (or a compound index
                               with -i col1,col2)

  --shape TEXT                 Custom shape for the DB table - format is
                               csvcol:dbcol(TYPE),...

  --filename-column TEXT       Add a column with this name and populate with
                               CSV file name

  --no-index-fks               Skip adding index to foreign key columns
                               created using --extract-column (default is to
                               add them)

  --no-fulltext-fks            Skip adding full-text index on values extracted
                               using --extract-column (default is to add them)

  --just-strings               Import all columns as text strings by default
                               (and, if specified, still obey --shape,
                               --date/datetime, and --datetime-format)

  --version                    Show the version and exit.
  --help                       Show this message and exit.

21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

We could only use this approach if csvs-to-sqlite would be no python package.
/cc @mweinelt @dotlambda

We don't allow these kinds of overwrites for libraries, as they propagate those dependencies, which could lead to collisions.

We could only use this approach if csvs-to-sqlite would be no python package.

Yes, there's no reason for this to be in pythonPackages.
However, watson isn't doing this well at all. I'm making a PR to improve it.

Result of nixpkgs-review pr 137442 at 009e1287 run on aarch64-linux 1

2 packages built successfully:

csvs-to-sqlite (python39Packages.csvs-to-sqlite)
python38Packages.csvs-to-sqlite

I removed the package from pythonPackages and added an override in all-packages. Maybe you can have another look.

However, watson isn't doing this well at all. I'm making a PR to improve it.

https://github.com/NixOS/nixpkgs/pull/137552

@dotlambda Actually I moved the package to another location. But I'm unable to apply the patches to that package as you did in watson. If I apply these I just get an error: error: anonymous function at /home/asbachb/dev/src/nix/nixpkgs/pkgs/tools/misc/csvs-to-sqlite/default.nix:1:1 called without required argument 'buildPythonPackage'.

Actually I moved the package to another location.

Oops, sorry.

But I'm unable to apply the patches to that package as you did in watson. If I apply these I just get an error: error: anonymous function at /home/asbachb/dev/src/nix/nixpkgs/pkgs/tools/misc/csvs-to-sqlite/default.nix:1:1 called without required argument 'buildPythonPackage'.

The new expression's only arguments should be lib, python3, and fetchFromGitHub.


⚠ Cioos National CKAN has degraded performance

In 2b9bfc6, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 5656 ms

Resolved: Cioos National CKAN performance has improved in a1a1074 after 11 minutes.


deleting branch on github

terminal output doesn't change automagically
<ThePhilgrim> oh, I deleted on github, so can you tell me the command?
<Akuli> git fetch --prune

<ThePhilgrim> do I need to fetch --prune when I deleted the branch on github?
<Akuli> yeah
<ThePhilgrim> great
<Akuli> but that's only to get cleaner lola
<Akuli> it doesn't really matter if it's left around otherwise

It is now explained on git-guide, don't know when I fixed it


WASM Preview Fails with Dependency Mismatch

Issue
The WASM preview here currently fails with a mismatch in the version of typing extensions to install. Pyodide 0.23.x bundles typing-extensions==4.5.0, while Pydantic core requires 'typing-extensions >=4.6.0,!=4.7.0'. Full output is below.
System Details
The output is identical whether loading from githubproxy.samuelcolvin.workers.dev or from a local dev server.
The output is identical on: Chrome 114.0 (Windows 10), Chromium  112.0.5615.49 (Ubuntu 22.04.1 LTS), Firefox 114.0 (Windows 10), Firefox 112.0.1 (64-bit) (Ubuntu 22.04.1 LTS).
Suggested Resolution
Remove typing-extensions installation from worker.js here, to allow micropip to install the appropriate version for the included wheel.
I'd be happy to open a PR if it's helpful.
https://github.com/pydantic/pydantic-core/blob/956f99666418fe5fc708260e1b3fc1ac2cd9b41b/wasm-preview/worker.js#L100
Full Output
Running tests against latest pydantic-core release (v2.4.0).
Downloading repo archive to get tests...
Using pyodide version: 0.23.0
Extracting test files (size: 619,704)...
Mounted 92 test files, installing dependencies...
Traceback (most recent call last):
Error: PythonError: Traceback (most recent call last):
  File "/lib/python311.zip/_pyodide/_base.py", line 540, in eval_code_async
    await CodeRunner(
  File "/lib/python311.zip/_pyodide/_base.py", line 365, in run_async
    await coroutine
  File "", line 50, in
  File "", line 40, in main
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 576, in install
    await transaction.gather_requirements(requirements)
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 342, in gather_requirements
    await gather(*requirement_promises)
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 355, in add_requirement
    await self.add_wheel(wheel, extras=set())
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 472, in add_wheel
    await self.gather_requirements(wheel.requires(extras))
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 342, in gather_requirements
    await gather(*requirement_promises)
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 346, in add_requirement
    return await self.add_requirement_inner(req)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 427, in add_requirement_inner
    if self.check_version_satisfied(req):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.11/site-packages/micropip/_micropip.py", line 373, in check_version_satisfied
    raise ValueError(
ValueError: Requested 'typing-extensions!=4.7.0,>=4.6.0', but typing-extensions==4.5.0 is already installed

Selected Assignee: @adriangb

If you know how to fix it yes please make a PR

Might also be worth asking pyodide to update the bundled typing_extensions version? I don't know what the process is for updating those dependencies.

For what it’s worth - just landed a PR to bump typing-extensions to version 4.7.1; that’ll be included in the next major release.


B-29 marker

Looking for a B-29 marker.
Thanks,
Mac

It's now on the list :)

I tried to figure out how to this myself but didn't have any luck. Not sure how to do markers. Same with the T-33
Mac


Error handling

Functions shall throw errors when they fail. Before they returned true  or false

There is an exception: If functions like layer.get(), style.get() oder store.get() do not find the object, because it does exist, then GeoServer returns undefined and does not throw an error. But there is a still an error thrown when GeoServer cannot be reached.
adapted test suite to new approach
in case of error the GeoServer output is added to the Error object using the property geoServerOutput, the normal "human-readable" message is stored in the standard message property. A failing request could be logged like this: await grc.namespaces.delete(nsPrefix)

#### Error message #####
Namespace doesn’t exist

#### GeoServer Response #####
<!doctype html><title>HTTP Status 404 – Not Found</title><h
1>HTTP Status 404 – Not Found

Type Status Report

Message Namespace 'exampl
e-namespace' not found

Description The origin server did not find a current representation for the target r
esource or is not willing to disclose that one exists.

Apache Tomcat/8.5.37

TODO

[x] consider creating reusable error classes
[x] adapt docs with throws statement
[x] Update demo index.js
[x] Add Upgrade Guide  --> an example is added to README
[x] consider testing this new concept in an real application to ensure it works in production
[x] fix indentation of about.js

@chrismayer I refined the error handling approach and made an extra handling for functions like layer.get(), style.get() oder store.get() . See the description in the PR text

@chrismayer this is ready to review again


Fix typo

Thank you for reviewing.

I think it is based on other examples:
https://github.com/felt/geo/blob/122e7a656e3549e09ecf74fae282c8b93f372689/lib/geo/line_stringz.ex#L3
Because here it says it defines the Polygon struct but it should say PolygonZ struct based on the other files.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2297

Questions ?
Please refer to the Backport tool documentation


[$500] Workspace chat not created in real time for submitter if IOU paid with business account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1714277015914689
Action Performed:

User A submits an IOU to User B
User B selects option "Pay with expensify"
Select option "business bank account"
Observe the LHN a new workspace created and moved the IOU to "expense report" for the payer
Switch to user A submitter and observe the LHN

Expected Result:
The report is moved to the user A's new workspace chat and showing the LHN
Actual Result:
Workspace chat not updated for user A in real time
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/485d21ba-eb0f-4895-a22e-a2a9388117c3

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010cfd316c3fbce043
Upwork Job ID:<PHONE_NUMBER>397467136
Last Price Increase: 2024-05-21

Issue OwnerCurrent Issue Owner: @Ollyws

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Asked DB about this one in slack as I can't add a business bank account.

asking why applause didn't try to repro and what the exact repro steps are as this is not clear to me from the FAB options:

thanks @m-natarajan super helpful! reviewed, agree with the Bug report. Adding external!

Upping the bounty

not overdue, updated the bounty - looking for proposals

not sure why it's overdue, just updated bounty yesterday and added update comment.

it is not 6 days overdue :'(

starred @Ollyws was wrong, unstarred and waiting for porpsoals

What is pre-requisite for user A and user B? should both activate bank accounts?, In my case, user B only have Pay elsewhere option, no option for pay with business account even when I activated it.

@wildan-m ir should happen the moment the user "N" goes to pay the IOU with a business bank account, before the VBBA is actually set up.
For more context:

when you go to pay an IOU, you can choose whether to pay it from a personal bank account or a business bank account. If you choose business, then Expensify creatse a workspace for you, And upgrade the IOU to be an expansion port in that workspace, moving it from your DM to the workspace chat.

Let me know if that helps with moving ahead proposing a solution here! Thanks!

bump @wildan-m

@zanyrenney It appears that this issue may need to be replicated using a VPN with a US location. I currently do not have a VPN subscription, so I will skip this issue for now.

Many free VPNs, want to give those a go to repro? https://www.google.com/aclk?sa=l&ai=DChcSEwjc58riueKGAxUujVAGHc5BDpoYABAHGgJkZw&co=1&ase=2&gclid=Cj0KCQjwvb-zBhCmARIsAAfUI2tFB6tMh0StTs_B9EiV4Ulc2jcaCjWEVGsachjx5jDcpvS5YecnDfAaAmDjEALw_wcB&sig=AOD64_1ZKK7OxzOlnoWrBuY5VjlyY3tbEQ&q&nis=4&adurl&ved=2ahUKEwiwr8biueKGAxVZUkEAHREMA9IQ0Qx6BAgJEAE

cc @wildan-m

bump @wildan-m

bumped in the channel as not hearing back here in the GH issue -https://expensify.slack.com/archives/C01GTK53T8Q/p1719226290528439

just tried to repro with a US VPN and i can't repro anymore!?

closing as I can no longer repro and there are over 250 issues closed so i am suspecting this has now been resolved in tandem/ as a side effect of one of those. feel free to reopen if you're still experiencing this!


exc_bad_access(code=1)

Hi,
I'm trying to create a simple example using core location and
RealmMapView but I keep getting the error mentioned in the title.
The issue comes from this line in ABFLocationFetchedResultsController.m:
ABFLocationSafeRealmObject *safeObject = [self safeObjectFromObject:object];
    safeObject->_coordinate = coordinate;
    safeObject->_title = title ? title : @"";
    safeObject->_subtitle = subtitle ? subtitle : @"";

The problem is that [self safeObjectFromObject:object] is returning nil.
object seems to be correct:
(lldb) po object
Location {
	latitude = 37.33156519;
	longitude = -122.03057969;
	title = point;
	subtitle = subtitle;
}

(lldb) po coordinate
 (latitude = 37.331565189999999, longitude = -122.03057969)

I'm using Swift 2.1, ABFRealmMapView (1.7.3) and Realm (0.97.0). I
have an model in the DB called location which I update every time
there is a location update event. I wonder if is a problem on my end
(maybe I'm missing a config value) or if is something in the lib.
I put an example in the following Github repo https://github.com/abuiles/_____RealmMapView
Thanks!

After some debugging, the issue was that I didn't specify a primaryKey in my Location. That fixed the problem.


Unable to run command "heroku run db:migrate"

I'm behind my college proxy which requires username and password. I'm able to push my Rails code to heroku master. But after that, commands like heroku run db:migrate/heroku run rails console are not working, getting EAI_AGAIN: getaddrinfo EAI_AGAIN rendezvous.runtime.heroku.com:5000 error repeatedly. I've exported my  proxy variables. I tried using heroku run:detached, but no progress.

@ajajeetaj what kind of proxy are you behind?  heroku run does not do an HTTP call, it instead connects using TCP over port 5000 and uses its own protocol, so if you only have to use the proxy for HTTP / HTTPS, the proxy should not be interfering.  It also appears that the real problem is DNS resolution.  What is the output of the following command?  (works in Mac / Linux, let me know if you use windows)
dig rendezvous.runtime.heroku.com

My College uses squid proxy to restrict internet usage. When I ran nmap command
sudo nmap -p 1-65000 <IP_ADDRESS>
to see my open ports, then result was
Nmap scan report for tsangpo.iitg.ernet.in (<IP_ADDRESS>)
Host is up (0.00023s latency).
 I get DNS resolution problem when I try to connect to my AWS machine through ssh from my college proxy.

@ajajeetaj From the output of the dig command it looks like it is not able to resolve rendezvous.runtime.heroku.com.  For comparison, here is my ANSWER SECTION for the same command.  It appears that you are using localhost for DNS resolution, so something in your DNS daemon configuration will need to be fixed.  Helping you configure this may be beyond the scope of my abilities depending on your setup.
;; ANSWER SECTION:
rendezvous.runtime.heroku.com. 180 IN	CNAME	ec2-50-19-103-36.compute-1.amazonaws.com.
ec2-50-19-103-36.compute-1.amazonaws.com. 21330	IN A <IP_ADDRESS>

A quick suggestion: switch to OpenDNS.  Should work through your college proxy but you might not be able to resolve on-campus addresses as easily.

please try heroku run rake db:migrate
If you are using rake in your rails app.


[WIP] Add forward request capability

@haphananhtuan Please check if this PR is still needed, I'll close it for now, please re-open it if it's still needed.


fix set TileJSON minZoom and maxZoom values

fix set TileJSON minZoom and maxZoom values

Pull Request Test Coverage Report for Build 1119

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 46.991%

Totals

Change from base Build 1103:
0.0%

Covered Lines:
5590

Relevant Lines:
11896

💛  - Coveralls

Hey thanks for the pull request. Could you add a test case for the issue, to prove out that it was fixed.

@gdey I fixed tests.

@paumas I'm looking at the code changes and I'm trying to understand what was happening in your case which were solved with this code change. Do you have a config with a couple layers you can share that would help me recreate the error in a test case?

@ARolek
Simple reproduce issues.
Example config:
port = ":8080"

[[providers]]
name = "bonn"           # provider name is referenced from map layers
type = "postgis"        # the type of data provider. currently only supports postgis
host = "localhost"      # postgis database host
port = 5432             # postgis database port
database = "bonn"       # postgis database name
user = "tegola"         # postgis database user
password = ""           # postgis database password
srid = 3857             # The default srid for this provider. If not provided it will be WebMercator (3857)

  [[providers.layers]]
  name = "road"
  geometry_fieldname = "wkb_geometry"
  id_fieldname = "ogc_fid"
  sql = "...any sql..."

  [[providers.layers]]
  name = "main_roads"
  geometry_fieldname = "wkb_geometry"
  id_fieldname = "ogc_fid"
  sql = "...any sql..."

[[maps]]
name = "zoning"

  [[maps.layers]]
  name = "road"
  provider_layer = "bonn.road"
  min_zoom = 5
  max_zoom = 10

  [[maps.layers]]
  name = "road"
  provider_layer = "bonn.main_roads"
  min_zoom = 11
  max_zoom = 20

If you try use http://localhost:8080/capabilities/zoning.json, then TileJson minZoom and maxZoom is wrong (minZoom = 5, maxZoom = 10), should be minZoom = 5, maxZoom = 20 .
vector_layers section is correct.

@paumas perfect! I see the bug now. I will add a test case to this PR so we can get it merged in.