Prometheus adapter issue with metrics from external rabbitmq

I am trying to implement HPA using external metrcis from a rabbitmq cluster hosted on AWS with an EKS cluster(v1.19) using promethues adapter.
Below works as expected
bash-5.1$ kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1 | jq .
{
  "kind": "APIResourceList",
  "apiVersion": "v1",
  "groupVersion": "custom.metrics.k8s.io/v1beta1",
  "resources": [
    {
      "name": "services/rabbitmq_queue_messages_input",
      "singularName": "",
      "namespaced": true,
      "kind": "MetricValueList",
      "verbs": [
        "get"
      ]
    },
}

Below is the query directly to prometheus server which delivers correct data:
$curl  http://<IP_ADDRESS>:58102/api/v1/query?query=rabbitmq_queue_messages
{"status":"success","data":{"resultType":"vector","result":[{"metric":{"__name__":"rabbitmq_queue_messages","cluster":"RabbitMQ-cluster","durable":"true","instance":"prometheus-amqp-metrics:9419","job":"prometheus-amqp-metrics","policy":"ha-all-AWS-OWNED-DO-NOT-DELETE","queue":"input","self":"1","vhost":"vhost"},"value":[1622138944.006,"2"]}]}}

"prometheus-amqp-metrics" is exporter service  in 'prometheus' namespace
Adapter rule is below:
    - seriesQuery: '{__name__=~"^rabbitmq_.*"}'
      seriesFilters:
      - is: ^rabbitmq_queue_messages$
      resources:
        overrides:
          job :
           resource: service
      name:
        matches: "^(.*)_messages$"
        as: "rabbitmq_queue_messages_input"
      metricsQuery: 'rate(rabbitmq_queue_messages{queue="input"})[2m]'

But I am not able to get the metric using below :
$kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1/namespaces/prometheus/services/prometheus-amqp-metrics/rabbitmq_queue_messages_input
Error from server (NotFound): the server could not find the metric rabbitmq_queue_messages_input for services

Not sure if it is supported on I am missing something. I have tried with k8s-prometheus-adapter-amd64:v0.6.0 and k8s-prometheus-adapter-amd64:latest

From what you shared, you are using custom-metrics and not external metrics. For your particular use case, I would advise you to switch to external metrics since your rabbitmq isn't tied to any Kubernetes resource. You will be able to find the external metrics documentation here: https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/docs/externalmetrics.md.
That being said, this would currently require your metrics to have at least a namespace label which as far as I can tell isn't your case. As of #380, it will be possible to use the external metrics API on metrics that aren't tied to a Kubernetes namespace, but this improvement hasn't been released yet. If you can afford to build your own image of the project on the master branch, then you'll be able to benefit from this improvement.

Thank you @dgrisonnet for your response. I had looked at using external metrics. Deploying the Prometheus adapter in the default configuration, it does not enable v1beta1.external.metrics.k8s.io . I am following this link https://github.com/kubernetes-sigs/prometheus-adapter/pull/302/commits/936bda2ef0ca6441980cb3bb5b7462c8175e8a99 to install external metrics but getting some issue with it which I am trying to troubleshoot
bash-5.1$ kubectl get apiservice v1beta1.external.metrics.k8s.io
NAME                              SERVICE                               AVAILABLE                      AGE
v1beta1.external.metrics.k8s.io   prometheus/custom-metrics-apiserver   False (FailedDiscoveryCheck)   13m

I read somewhere that external metrics is not supported on EKS which I suspect to be true.
To confirm, the namespace label will be needed in my metrics even with external metrics API, right. If so, I am considering overriding any existing label to namespace in the adapter resources rule after my external metrics API is working, not sure if it will work.

Thank you @dgrisonnet for your response. I had looked at using external metrics. Deploying the Prometheus adapter in the default configuration, it does not enable v1beta1.external.metrics.k8s.io . I am following this link  to install external metrics but getting some issue with it which I am trying to troubleshoot
bash-5.1$ kubectl get apiservice v1beta1.external.metrics.k8s.io
NAME                              SERVICE                               AVAILABLE                      AGE
v1beta1.external.metrics.k8s.io   prometheus/custom-metrics-apiserver   False (FailedDiscoveryCheck)   13m

I read somewhere that external metrics is not supported on EKS which I suspect to be true.
To confirm, the namespace label will be needed in my metrics even with external metrics API, right. If so, I am considering overriding any existing label to namespace in the adapter resources rule after my external metrics API is working, not sure if it will work.

Hey @neeraj201 sorry for the late reply, were you able to fix your issues?
If you not, could you please share your prometheus-adapter config alongside prometheus-adapter logs?

@dgrisonnet, thanks for the follow-up. Yes, it is still an issue. I will recreate the setup again next week and provide the requested information.


Refactor edit mode and make compatible with diva viewer

This takes care of part of #341 and resolves #343.
Changes

Refactor most editing features to a new folder called UnifiedEdit.
Create a DivaEdit class.
Have most editor tools take selectors as inputs to set event listeners. Previously these were hard coded.

~This should not be merged until more testing is performed.
The pull request exists to check compatibility with develop, ensure tests are running through travis, and get feedback.~

Currently dealing with an issue where at times there are multiple insert handlers being called for a single click resulting in multiple elements being inserted instead of one.

Issue arises when the user clicks on a staff line, triggering one action on the svg container and one on the inner 'definition-scale' element. This can be fixed by only applying the listener to the container svg.

Have you done all tests to check compatibility for this? Can we merge?

@vigliensoni A few commits were just added, but most tests have been done. Should be close to the point of merging soon.

Minor UI fixes need to be made first but after that this seems ready to merge.


change Low/Medium/High color in Recycler view at runtime

I have a recycle view whose view gets updated in every 30 seconds. I am able to change the color on Indicator but speed view color is changed to another color.
I guess the issue is with the recycled views.
first time image : (this is what it looks when the view is created for the first time.)

But after the refresh or down in the list view I see this ;

I have checked the code
this.mediumSpeedColor = mediumSpeedColor;         if (!isAttachedToWindow())             return;         updateBackgroundBitmap();         invalidate();
I guess the recycled view is already attached to the window.
Please suggest what to do?

So you want to change indicator color or speedometer color?
May you show me the code.

i want to change both of them. as in first image. but when i scroll down or the list refresh only the color of indicator changes not the color of speedometer

Try to call speedometer.invalidate() after you change the the bar color.

That's weird!
Give me xml tag for SpeedView and code where you change the color, i will try to fix it.

java code (adapter's onBindViewHolder)
` switch (state) {
        case Running:

            vehileViewHolder.statusColour.setBackground(mContext.getResources().getDrawable(R.drawable.state_green_circle));

            vehileViewHolder.speedView.setLowSpeedColor(mContext.getResources().getColor(R.color.n_green_dot));
            vehileViewHolder.speedView.setMediumSpeedColor(mContext.getResources().getColor(R.color.n_green_dot));
            vehileViewHolder.speedView.setHighSpeedColor(mContext.getResources().getColor(R.color.n_green_dot));
            vehileViewHolder.speedView.setIndicatorColor(mContext.getResources().getColor(R.color.n_green_dot));

            vehileViewHolder.speedView.invalidate();
            break;

        case Overspeed:
            vehileViewHolder.statusColour.setBackground(mContext.getResources().getDrawable(R.drawable.state_red_circle));

            vehileViewHolder.speedView.setLowSpeedColor(mContext.getResources().getColor(R.color.n_red_dot));
            vehileViewHolder.speedView.setMediumSpeedColor(mContext.getResources().getColor(R.color.n_red_dot));
            vehileViewHolder.speedView.setHighSpeedColor(mContext.getResources().getColor(R.color.n_red_dot));
            vehileViewHolder.speedView.setIndicatorColor(mContext.getResources().getColor(R.color.n_red_dot));
            vehileViewHolder.speedView.invalidate();
            break;

    }`

XML ;
<com.github.anastr.speedviewlib.SpeedView
android:id="@+id/speedView"
android:layout_width="90dp"
android:layout_height="wrap_content"
android:layout_alignParentRight="true"
android:layout_centerVertical="true"
android:layout_toLeftOf="@id/iv_blur_icon"
android:paddingRight="10dp"
app:sv_endDegree="360"
app:sv_indicator="NeedleIndicator"
app:sv_indicatorWidth="8dp"
app:sv_lowSpeedColor="@color/four_f"
app:sv_mediumSpeedColor="@color/four_f"
app:sv_lowSpeedPercent="75"
app:sv_maxSpeed="200"
app:sv_mediumSpeedPercent="100"
app:sv_minSpeed="0"
app:sv_speedTextFormat="INTEGER"
app:sv_speedTextPosition="CENTER"
app:sv_speedTextSize="@dimen/home_list_item_content_text_size"
app:sv_speedometerMode="TOP"
app:sv_speedometerWidth="5dp"
app:sv_startDegree="180"
app:sv_trembleDegree="2"
app:sv_unitTextSize="@dimen/home_list_item_address_bottom_margin"
app:sv_withTremble="true" />

I am so busy at this time, and there are too many issues need to handle...
I don't know when i will finish it up, but if you are in a hurry you can extenda SpeedView and override onAttachedToWindow() method like this:
@Override
    protected void onAttachedToWindow() {
        super.onAttachedToWindow();
        updateBackgroundBitmap();
        invalidate();
   }

Don't change anything else.
This resolve your issue until next version.

Thanks @anastr . It worked.
One more thing is there any library like this in iOS?

unfortunately No, you have to look for other lib.

fixed in V 1.3.0.


Opening an invalid library has unexpected behavior on the frontend

If you try to open the page of a library that does not exists, like /libraries/blablabla, it does not display an error. In fact, it throws a console error trying to parse the response from the API, because the API returns a 500 status code with an HTML error message, when the front-end is expecting an application/json response.
Additionally, the frontend will also cache the current library, which means in this case it will cache the invalid blablabla library as the default when the user returns to Kamu, instead of not caching it or keeping the previous one on the cache.
Expected behavior

The API should return a 404 instead of a 500
The frontend should display the standard error page from ErrorBoundary when a parsing error occurs
The frontend should not set an invalid library as the user's current library

Fixed
The error boundary won't be called by design, this is a limitation on React handling asynchronous code. An error boundary will only catch errors in the rendering of components.
Fixed


make sure that incoming data packets don't get overwritten on the same day

from #101 from @kathryn-willi
suggestion: A way to make sure files don't get overwritten on the same day... If we replace the current write_csv() call in api_puller with the following code that includes the full end_dt:
write_csv(one_df,               paste0(dump_dir, "/", site, "_",                      str_replace(str_replace(substr(end_dt, 1, 16), "[:\\s]", "_"), ":", ""),                      ".csv"))

this has been incorporated in my fork, I just need to open a PR for it

ahh, yes. Good catch and looking forward to the fix!


chore: update digitalcredentials/vc to 5.0.0

Upgrade digitalcredentials/vc to 5.0.0
Notable Changes: https://github.com/digitalcredentials/vc/pull/9

Oh yeah sure will do that!

@mirceanis Not sure if all of the updates are from the 5.0.0 upgrade, please take a look.


Fix building on gcc>=12 and Clang >=13 by including  explicitly.

Include <iterator> explicitly for building on gcc12, clang13 and higher.

Thank you! This is definitely a better way than my overthought attempt.
That's what I get for programming after 20 hours of no sleep.


HTTP::Params [] and fetch returns only first element

Snippet
require "http"

body = "sld=kemal&tlds[]=com&tlds[]=net&tlds[]=io"
params = HTTP::Params.parse body

pp params["tlds[]"] # => "com"

Normally i'd expect tlds[]to be ["com", "net", "io"] as it's being parsed correctly. However  [] and fetch returns only first element as seen in https://github.com/crystal-lang/crystal/blob/master/src/http/params.cr#L122
Accessing the array as "tlds[]" also feels a bit unconventional and one would expect to access it via "tlds" but that's a topic for another issue

From the docs:

If you call the key tlds[], why should it be accessed under any key except tlds[]? You could just as easilly send sld=kemal&tlds=com&tlds=net&tlds=io and then how would you access that?

Thank you @RX14. I didn't know that fetch_all existed for this purpose 👍
About accessing sld=kemal&tlds[]=com&tlds[]=net&tlds[]=io most of the popular web frameworks Sinatra, Rails e.g will allow you to use it like params['tlds'] but i'm not sure if it's coming from Rack.

The [] suffix for query params/urlencoded seems to be very inconsistent between languages: http://stackoverflow.com/a/9547490/2035962
The spec doesn't seem to mention it, so I would say that Ruby and PHP are wrong here and Crystal should stick to the less magic way of doing things.

Notice that Rails also propose a syntax for sending hash/array in params. jQuery adopted the same encoding which was pretty handy. I would say that any serialization beyond the standard should be implemented by a shard / framework.

Thank you all for your insights 💯

NB: I would probably use it ;-).
It's just that there is no a clear winner option for this, since impacts on the client side of the http app.
Welcome to kemalcr/deep-params (?)

Hehe, this is pretty common and it's already supported in Crystal sld=kemal&tlds[]=com&tlds[]=net&tlds[]=io.
I agree with @RX14 accessing it like fetch_all("tlds[]") is explicit and fine.


How can I access the pervious fulfilled result up in the chain?

I have the following requirement, and I need to access the pervious fulfilled result in the last then?
firstly {
	when(fulfilled: tasks.map(ImageProcessor.shared.process))
}.then { images in
	when(fulfilled: images.map(ImageUploader.shared.upload))
}.then { urls in
	//TODO: need to get back (URL, CGSize) tuple
	//PostUploader.shared.upload([(URL,CGSize)])
}

OK. I have found that it's covered in the FAQ section. Thanks.


Code generation should be triggered automatically

Running Gradle build task fails for examples project because code isn't generated before tests.
As a workaround run generateCode before running tests.
Also infrastructure (e.g. EventHandler) may depend on generated code so code generation should be triggered before jvmMain compile or maybe before the whole compile task.

Fixed in v0.3


decide on automated testing approach

[x] unit tests
[ ] automated tests

we don't test the UI, we try to meet 80% code coverage requirement

non-unit tests:

there are: a) A+, b) some kind of web server (probably a dockerized nginx with course materials injected) run locally inside the travis build for testing the APIs
those a) and b) are run elsewhere to provide infrastructure for manual testing


Error about collision checking in practical-exercises?

Hi, there
I recently do the practical-exercises as your tutorial says 4.3) Collision checking
But when I run in python, I meet an error:
 File "example_q4_contact.py", line 22, in <module>     dist = robot.checkCollision(idx)                             File "/home/xxx/pinocchio/doc/d-practical-exercises/src/robot_hand.py", line 295, in checkCollision     dist = va.collision(vb, self.data)                             File "/home/xxx/pinocchio/doc/d-practical-exercises/src/robot_hand.py", line 61, in collision     if all(0 <= ab <= 1): ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
As the tutorial says Pinocchio also implement a complete and efficient collision checking based on FCL, also not used in the tutorial, which means this way of collision checking is used temporary just for exercise. If I'm right, then where could I find the tutorial that Pinocchio implement based on FCL, not just exercise?
Wish you have a nice day!

Will fix it. Thanks for this report.

What do you mean by tutorial?

The way used for collision checking in robot_hand.py is not the FCL way. Maybe use FCL in robot_hand.py will better as a tutorial.
We should use native API as much as possible, rather than "make" a new one.

You're right. We wanted to mask a lot of FCL API to allow end users.
But it remains possible to use the classic API of FCL.
Maybe, it would be nice for someone to do it. @littleggghost Do you think you may write such an example? Thanks in advance for your contribution to Pinocchio.

Well, I will do that if I have the time. As a beginner, there is still a long way to go.

If you already know FCL, it just a matter of seeing how the functions for collision detection are working. All these details are located here: here for updating the placement of the collision meshes and here for calling FCL funtions.
And of course, we can help you.

Is these functions have python wrapper now?

I want to make a collision test:
A box falls freely to the ground, causing bouncing and rolling till stop, and we can check it on gepetto-viewer.
Should I start a new issue?
And any advices?

I started to change this tutorial to go to FCL detection collision. I then stopped because of some data resulting of FCL algorithms not properly bound to python-pinocchio. Related to #638

Hi, @nmansard
What do you think of my collision test as I mentioned above?

I want to make a collision test:
A box falls freely to the ground, causing bouncing and rolling till stop, and we can check it on gepetto-viewer.
Should I start a new issue @jcarpent
And any advices?

Hi, @jmirabel
I noticed you are familiar with FCL. Could you check this exercise?

We have in mind to make hpp-fcl more robust (and unit-tested) but there is no timeline yet. I have no time to allocate to this. I could provide some guideline if anyone is willing to handle this.

@littleggghost To make the story short, when starting hpp-fcl the team did not wanted to redo another collision library. But all the PR to fcl were ignored forcing us to do a fork. When the fcl library was reboot it was mostly to work on the CPP interface not on correcting the algorithms. @florent-lamiraux could give a more accurate account on this.

This issue has been fixed by #725.


Support breakpoints

Would be nice if this extension would respect breakpoints set in the npm script being run.

+1

This is a duplicate of https://github.com/Microsoft/vscode/issues/2726#issuecomment-180318655


Cannot connect to Docker deamon: how to debug?

Running into the following failure:
stillwater@sw-desktop-300:~$ sudo ./docker-relay &
[1] 41
stillwater@sw-desktop-300:~$ docker images
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

[1]+  Stopped                 sudo ./docker-relay

From a PS, confirmed that the docker deamon is running
PS C:\Users\tomtz> docker info
Client:
 Debug Mode: false

Server:
 Containers: 36
  Running: 36
  Paused: 0
  Stopped: 0
 Images: 26
 Server Version: 19.03.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.9.184-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.63GiB
 Name: docker-desktop
 ID: 7TG2:NXNU:DPH4:PK2T:OKQT:6AZC:DCNM:NVH5:QHY6:3I7Y:QPBL:XQXR
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 126
  Goroutines: 119
  System Time: 2019-09-07T14:10:57.2339252Z
  EventsListeners: 1
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false
 Product License: Community Engine

So, how do I debug what is failing?

turned out to be incorrect permissions on my docker-relay.

for anyone running into a similar issue, job management is useful here:
dont specify background($ at the end) when invoking sudo ... if your auth isn't cached; instead use CTRL+Z to suspend your job, and bg to run the most-recently-suspended job in the background.
eg:
(the ^Z below is when CTRL+Z is entered, after entering the password for sudo ...)
ethan@coip:~$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

ethan@coip:~$ ./docker-relay
2020/01/13 15:21:43 socat[281] E bind(5, {AF=1 "/var/run/docker.sock"}, 22): Permission denied

ethan@coip:~$ sudo !!
sudo ./docker-relay
[sudo] password for ethan:
^Z
[1]+  Stopped                 sudo ./docker-relay

ethan@coip:~$ bg
[1]+ sudo ./docker-relay &

ethan@coip:~$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

ethan@coip:~$


Differentiate Handle.effectiveType (to see if a set of types will resolve) from Handle.resolveEffectiveType.

This allows effectiveType to be used for speculative resolution inside strategies.
Note that this uncovered a more fundamental problem around type cloning:
There's a clone() method on type which works on individual types. However, type variables work by linking all instances of the same variable to a single TypeVariable object, which means that cloning can't maintain type variable information. So clone() flattens out type variables to their resolved values.
This means that clone() can't be used to try speculative type changes (like what strategies are trying to do with effectiveType), because all the linkages are lost and the effect of the change isn't correctly evaluated.
To get around this, I've added a cloneWithResolutions() method; but there's an important caveat here: it can only be used with an understanding of the domain of the test that the clone is going to be used for. In this case, we only care about this specific handle and it's connections, so it's OK to cloneWithResolutions() across that set of types.
This investigation also uncovered some bugs with the way we were cloning shapes, and a place where shapes were being cloned but shouldn't have been.

Makes sense, thanks for working on this!

I'm going to revert this change for now because it's not possible to develop on Linux right now as it sad-tabs right away. It also could be causing performance issues on OSX -- though we don't see crashes @seefeldb is seeing things run very slowly.
We can look at reducing a test case and relanding.


Define query terms to search for on Publication / Dataset sources that have searchable interfaces

Figshare (Dataset source), Pubmed (Publication source), and others have searchable interfaces and/or APIs which allow us to more or less directly import the metadata about the individual resources, which will then be need to be mapped to our schema.
prelim list (plus variations with capitalization and hyphenation):
Severe acute respiratory syndrome coronavirus 2
COVID19
SARS-2
SARS-CoV2
SARS-CoV-2
HCoV-19
SARS2
2019-nCoV
COVID-19
COVID-19 virus
Wuhan coronavirus
Wuhan seafood market pneumonia virus
Human coronavirus 2019
novel coronavirus 2019
novel coronavirus NOTE: need to be careful about this one, since this was also the original name for MERS

Primarily taken from NCBI Taxonomy ID: 2697049 synonyms

I've seen 'ARDS coronavirus' used early on.  Like 'novel coronavirus', it could capture some MERS stuff, but if an additional filter on the publication date is used, you should be able to restrict it to just sar-cov2.


Wal-e error: “ pg_stop_backup still waiting for all required WAL segments to be archived”

I've been trying to use wal-e to take incremental backup of my postgresql database by following this blog. I've a database on my postgresql and using an AWS S3 bucket. while I'm using the following command
sudo -u postgres /usr/bin/envdir /etc/wal-e.d/env /usr/local/bin/wal-e backup-push /var/lib/postgresql/10/main
it shows this

Any help on this?
Thanks :)

@proteeti13 I have faced the same problem today. Have you already solved it?

Couldn't solve it. I spent a lot of time figuring out but failed. Now started reading the documentation of Barman :( @greylord1996

@proteeti13 hey, i'm also experiencing the same issue.
In my case (I'm using digital ocean a s3 interpolated object) its because boto is expecting me to insert a aws:kms key despite the fact i'm not running with aws s3.
`Traceback (most recent call last):
File "src/gevent/greenlet.py", line 716, in gevent._greenlet.Greenlet.run
File "/usr/local/lib/python3.6/dist-packages/wal_e/worker/upload.py", line 53, in call
self.gpg_key_id)
File "/usr/local/lib/python3.6/dist-packages/wal_e/worker/worker_util.py", line 40, in do_lzop_put
k = blobstore.uri_put_file(creds, url, tf)
File "/usr/local/lib/python3.6/dist-packages/wal_e/blobstore/s3/s3_util.py", line 57, in uri_put_file
k.set_contents_from_file(fp, encrypt_key=True)
File "/usr/local/lib/python3.6/dist-packages/boto/s3/key.py", line 1309, in set_contents_from_file
chunked_transfer=chunked_transfer, size=size)
File "/usr/local/lib/python3.6/dist-packages/boto/s3/key.py", line 762, in send_file
chunked_transfer=chunked_transfer, size=size)
File "/usr/local/lib/python3.6/dist-packages/boto/s3/key.py", line 963, in _send_file_internal
query_args=query_args
File "/usr/local/lib/python3.6/dist-packages/boto/s3/connection.py", line 671, in make_request
retry_handler=retry_handler
File "/usr/local/lib/python3.6/dist-packages/boto/connection.py", line 1071, in make_request
retry_handler=retry_handler)
File "/usr/local/lib/python3.6/dist-packages/boto/connection.py", line 940, in _mexe
request.body, request.headers)
File "/usr/local/lib/python3.6/dist-packages/boto/s3/key.py", line 896, in sender
response.status, response.reason, body)
boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request
InvalidArgumentServer Side Encryption with KMS managed key requires HTTP header x-amz-server-side-encryption : aws:kmskpex-spacetx000000000000000208c19$
2018-08-06T01:57:45Z <Greenlet "Greenlet-23" at 0x7f4e1882a348: <wal_e.worker.upload.WalUploader object at 0x7f4e188894a8>(<wal_e.worker.pg.wal_transfer.WalSegment object at)> failed with S3ResponseError`

any news here?

Sorry guys. I couldn't solve it :(

just now, noticed that https://github.com/wal-g/wal-g this has configuration regarding kms. maybe that is related


fix button left up

It should bring you to the previous page but it is always bringing to index.html right now

It is in includes, menu.html, instead of site.baseurl in
<a href="{{ site.baseurl }}" class="brandLogo brandLogo--small
it should be something indicating the previous visited page...

And now it is not even appearing...


lyft/protoc-gen-validate has disappeared

the dependency https://github.com/lyft/protoc-gen-validate seems to have disappeared...

The redirects should be working again. I will update this to point to https://github.com/envoyproxy/protoc-gen-validate in the next few days.


Add dependency injection to label & parent functions

Using #105 as a basis I've made the label and parent functions injectable (including any resolves from the state and the $scope of the last view).
Added ability for promises to be returned from these functions.
Added ability for states to have themselves as parents.

Coverage decreased (-4.008%) to 90.698% when pulling 055dc39b8ea785ed313260c1c161a75a3b0d4c95 on woodwardsoftware:feat-injection into e6e92aa5722d8e8036d405bdd9a5b2dea15da31e on ncuillery:master.

Coverage decreased (-3.8%) to 90.95% when pulling 17e101d4a566cf744e7b93152a50ff60f5f82511 on woodwardsoftware:feat-injection into e6e92aa5722d8e8036d405bdd9a5b2dea15da31e on ncuillery:master.

Is this integrated with the current release ?

Any news?


Typographical error

There is a typographical error here.
'Retrieves' instead of 'Retries'
(https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/get-pnpterm?view=sharepoint-ps#description)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1f40a8d9-6370-c6d6-1084-8d3c9fa590d1
Version Independent ID: d5f61b47-0910-ce00-3fa3-7eeec5640e8c
Content: Get-PnPTerm (PnP.Powershell)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTerm.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: pamgreen

Hello @mohrehm
how are you?
Even though the PnP documentation articles are on this repository, I need to kindly redirect you to open PnP cmdlets issues/pull requests here, in that repository, where a member of the PnP community will be able to correct the article/review your PR with your feedback.
The documentation for PnP cmdlets is then synced from that repo into this one.
Thank you!

@get-itips Thank you very much for the contribution and sharing this explanation. @mohrehm Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Delay in bot responses for #.

What I observed while testing workflow with WhatsApp bot is, every time when I add # to go to the previous step, it takes 4 minutes to get an update response
Originally posted by @Nik720 in https://github.com/Samagra-Development/SamagraX-community/discussions/3#discussioncomment-528433

@nik720, Can you provide more information (formID) and the step at which you pressed # along with the XLSX of the form on that issue. That would enable us to reproduce it.

@ChakshuGautam @aayushkedia95  sorry for late, here are the scenario
FormID: SamagraX_AK_Test
Input steps: Hi AKBot => 1 => # (at any step it will reproduce)

FormID: digital_content_workflow_without_group_01
Input steps: Hi Tara => 1 => # (at any step it will reproduce)
XLSX: https://docs.google.com/spreadsheets/d/1PTEFJoAhRsvlvoZSbNiFQoB6-Yqxl6l4/edit#gid=1148196142

CC @vinukumar-vs @vrayulu

Thanks for the screenshots. I am seeing the same behavior as well. I think this is due to the last pushed code as we have not seen this behavior before.

Can you please also check that some of the HTML tags are not working in the WhatApp bot?

Hi @Nik720, xMessages inherently supports a subset of styling mentioned here. So anything in the transformer (ODK in this case) should be formatted either through this or we could have a transformer that does this conversion post the ODK transformer (and HTML tags transformer).

@Nik720 This is closed now. Please test.