Invalid registration token for new apns-push-type 'location'

Describe your environment

Operating System version: macOS Big Sir, 11.6
Firebase SDK version (iOS): 8.6.0
Library version (server): 8.1.0
Firebase Product: FCM Messaging

Describe the problem
Unable to send the "new" location push notification to the APN server successfully.
The FCM token used was properly tested (after every step) to be able to send visible notifications via the Firebase console.
Steps to reproduce:

Tried to send a fcm message (normal and multicast) with the code below. The lines marked with (x) were tried to exchange to different values and or being omitted.

val message = MulticastMessage
            .builder()
            .addAllTokens(tokenList)
            .setApnsConfig(
                ApnsConfig.builder()
                    .setAps(
                        Aps.builder().setContentAvailable(true) // (x)
                            .build()
                    )
                    .putHeader("apns-push-type", "location")
                    .putHeader("apns-topic", "$iosBundleId.location-query")
                    .putHeader("apns-priority", "5") // (x)
                    .putHeader("apns-expiration", Instant.now().plus(3600, ChronoUnit.SECONDS).epochSecond.toString()) // (x)
                    .build()
            ).build()

firebaseMessaging.sendMulticast(message)

Receiving the FCM error "Invalid Argument" --> "Invalid registration token". Yet the token is valid, testing it via the Firebase console and sending a visible notification through my own server's code. It appears Firebase is restricting this before trying to send the request to the APN server.
Is there any setting, scope or something similar missing to be able to send the location-query push notification through Firebase?
One observation I had was that the token changes from having a prefix seperated by a colon.
Relevant Code
Request
POST https://fcm.googleapis.com/v1/projects/fairenough/messages:send HTTP/1.1
Content-Length: 683
Content-Type: application/json; charset=UTF-8
x-goog-api-format-version: 2
x-firebase-client: fire-admin-java/8.1.0

{"message":{"apns":{"headers":{"apns-push-type":"location","apns-topic":"<bundle-id>.location-query","apns-expiration":"1635411540","apns-priority":"5"},"payload":{"aps":{"content-available":1}}},"data":{"eventId":"93e7728d-9f5e-4acf-b3d4-b69f671a1599","confirmationNeeded":"false","id":"1552","type":"Information","category":"AdhocLocationRequest","entity":"LocationRequests"},"token":"fHddGiu7MENDjdl3-ycL6I:APA91bHvfqSAR3dg2t19Z7moAtM62CEi_fHz6QvDC7KlIujzYVL7LjXoZyM_2RSKSK-KtkYCQUYhOmXU9uY-czMOqFH9bwx-3MbF1jUYFky9ETZq6ZEllugE*******************"}}

Response
Content-Type: application/http
Content-ID: response-1

HTTP/1.1 400 Bad Request
Vary: Origin
Vary: X-Origin
Vary: Referer
Content-Type: application/json; charset=UTF-8

{
  "error": {
    "code": 400,
    "message": "Request contains an invalid argument.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.firebase.fcm.v1.FcmError",
        "errorCode": "INVALID_ARGUMENT"
      },
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "field": "message.token",
            "description": "Invalid registration token"
          }
        ]
      }
    ]
  }
}

Hello @ChristianOrgler, thanks for the post. the FCM team looked at the newly launched Apple Location Push Service Extension feature. We confirmed that currently FCM does not support this feature: it requires some significant system change on the FCM side for FCM to support this feature.
We are currently investigating on adding this feature. I think for now in the short term we may want to update the error message to reduce confusion.

@ChristianOrgler Would you file a feature request on this so we can also see how many developers want the same feature like you.

Thanks for investigating! Yes I will create a ticket right away and reference it here again.
Would you be able to go give a rough timeline in case this feature is wanted by others as well? (to plan if I need to support it on my own until then or I would be able to wait (and contribute if requested)

@ChristianOrgler We haven't received many requests by others yet which is why it would be helpful to file a separate feature request so others can vote on. Currently this effort is not prioritized given low volume of demands.

Hi @chliangGoogle - is this request: 10155562 fine or should I create a new one?

@ChristianOrgler better to create a new one so other developers can search and upvote it.

Ok @chliangGoogle - via this link or here at GitHub?

@ChristianOrgler No, still via github. Here's an example: https://github.com/firebase/firebase-ios-sdk/issues/8968

Created: https://github.com/firebase/firebase-admin-java/issues/620 - how do people upvote on it?

Created: https://github.com/firebase/firebase-admin-java/issues/620 - how do people upvote on it?

@ChristianOrgler they can upvote by clicking on the emoji.
Thank you for filling the feature request!


The lost async servlets

Work toward their restoration. See issue 2598 in the upstream repository.

Resin 4.0.55 doesn't support Servlet 3.1. Servlet 3.1 has the async IO support. We will need Apache Tomcat sooner.

OK. Tomcat 9.0.4 installation is working. Got some benchmark data. Now trying to build APR tomcat-native adapter for faster native I/O. It requires OpenSSL 1.0.2 but Ubuntu 14.04 comes with 1.0.1x.

There are three components here: APR, OpenSSL 1.0.2 and Tomcat native bindings to ARP. They should be build together. Currently I get warnings in Tomcat log file (catalina.out) when trying to load the ARP library.

Managed to make Tomcat 9 to use ARP and OpenSSL 1.0.2.
07-Feb-2018 19:57:05.116 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.16] using APR version [1.5.1].
07-Feb-2018 19:57:05.117 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
07-Feb-2018 19:57:05.119 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]

Played also with the various connector implementations and some tweaks: NIO2 seems the best. But it is loosing against Resin 4.0.53. JSON test heaviest: 4400 rps vs 3550 rps. But Resin already shows saturation - the RPS is falling with the heavier load.

The shell scripts with Tomcat 9.0.4, OpenSSL 1.0.2, Apache APR 1.6.3, Tomcat Native connector compilation, installation and so on are ready.
Also basic setup of server.xml with NIO2 connector.

Pull request submitted: 3319.


Pm/zap token to pt

Coverage decreased (-88.4%) to 6.016% when pulling a4966768be25a1ebaee2de9cfc9a76a238421e60 on pm/zapTokenToPt into 1611fdd855df92a5334e57b3098a63d1f12bd451 on main.


Document PyQt benign errors to avoid confusion

When loading a PyQt window I get
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast

Initial googling suggests some interaction with the nvidia drivers of the host.
I haven't yet found a package I can install to provide swrast_dri.so
More investigation, and comparison to another app, needed.

For comaprison with dls_pmaccontrol, I get the error but the window is displayed.
So perhaps the error can be tolerated.

I've seen these errors too with dls-pmac-control but they seem to be benign for me. Are they stopping your app working?

I thought so, but given that dls-pmac-control works, probably it is something else.

Sure enough, I found the real cause of my problem. It is not related to these messages.
It would be nice to understand exactly what they mean, but I'm not going to do that now.

TODO: add some notes on this in the docs

fixed in 2.0.4


Merge main into 9 restore io functionality

The motivation for this PR is to update the IO branch to enable

easier integration later
testing of the IO checks in the examples folder


Remove translated pages that appear multiple times

Thanks for the PR but this plugin isn't maintained anymore. Please take a look at https://github.com/kapt-labs/djangocms-htmlsitemap


REMEDIATION: Recieved API Response (404)

What would cause a 404 when trying to run 'touch /tmp/hello' on CentOS6.5?  The server has a subscription to its hostname, I don't see anything on the sensu-agent.log on the server showing it got the request and failed on something like permission denied.
Check's config:

{
    "checks": {
        "check_jenkins_locall_http": {
            "interval": 30,
            "handlers": [
                "slack2-p1",
                "remediator"
            ],
            "standalone": false,
            "subscribers": [
              "centosJenkinsMaster"
            ],
            "command": "/usr/lib64/nagios/plugins/check_http localhost -t 30 -p 8080 -R \"Jenkins\"",
            "remediation": {
                "heavy_remediation": {
                    "occurrences": [
                        "1+"
                    ],
                    "severities": [
                        2
                    ]
                }
            }
        },
        "heavy_remediation": {
            "command": "/bin/touch /tmp/hello",
            "subscribers": [],
            "handlers": [
                "slack2-p1"
            ],
            "publish": false
        }
    }
}

server's sensu config:

{
  "client": {
    "safe_mode": false,
    "subscriptions": [
      "sensu-default",
      "centosJenkinsMaster",
      "jenkinsrelease.example.net"
    ],
    "address": "<IP_ADDRESS>",
    "bind": "<IP_ADDRESS>",
    "name": "jenkinsrelease.example.net"
  }
}

I'm having this same issue.  Here's my config:
{
  "checks": {
    "test_please_ignore": {
      "handlers": ["default", "remediator"],
      "command": "/opt/sensu/embedded/bin/ruby /etc/sensu/plugins/check-cmd.rb -c false",
      "interval": 60,
      "subscribers": [ "build" ],
      "publish": true,
      "remediation": {
        "test_please_ignore_rem": {
          "occurrences": ["1+"],
          "severities": [2]
        }
      }
    },
    "test_please_ignore_rem": {
        "handlers": ["default"],
        "command": "echo remediation >> /tmp/remediation",
        "subscribers": [],
        "publish": false
    }
  }
}

Am not seeing /tmp/remediation on the "build" host or the sensu server.  Also I'm not seeing any indication that there was an error or the remediation tried to run.  What am I doing wrong?

Hello there, having the same issue when the sensu server and client are on different machines (or VMs). The remediation works only when server and client are on the same machine (or VM).
If the (unpublished) remediation check is only present on the client, the /var/log/sensu-server.log on the server displays a line like:
{"timestamp":"2015-06-06T10:32:38.764508+0000","level":"info","message":"handler output","handler":{"type":"pipe","command":"/etc/sensu/handlers/remediator.rb","name":"remediator"},"output":["REMEDIATION: Evaluating remediation: xxx-vm {\"apt-cacher-ng-restart\"=>{\"occurrences\"=>[\"1+\"], \"severities\"=>[2]}} #=5 sev=2\n","REMEDIATION: Triggering remediation check 'apt-cacher-ng-restart' for [\"xxx-vm\"]\n","REMEDIATION: Received API Response (404): , exiting.\n"]}

My workaround is to create the unpublished check on the server also (even if it will never run there), just so that the API does not return 404 when queried for the check:
{
  "checks": {
    "apt-cacher-ng-restart": {
      "command": "sudo /usr/sbin/service apt-cacher-ng restart",
      "handlers": [
        "default"
      ],
      "subscribers": [],
      "publish": false,
      "interval": 10
    }
  }
}

After doing this, the remediation check will return as expected on the client.
Note: using sensu 0.18.1 (installed and configured with the sensu-chef cookbook version 2.10.0).

After investigating more on how sensu checks work, I think that the unpublished remediation checks cannot be standalone (defined on the client). It does not help me, and in the end I may have to fallback to ad-hoc remediation handler, which is not DRY at all.

any update on this?  I am using sensu .20 and this still seems to be an issue with the remediator.  Basically just looking for a simple apache restart.
This is the log entry on the server:
 "output":["REMEDIATION: Evaluating remediation: LAMP01 {\"light_remediation\"=>{\"occurrences\"=>    [1, 2], \"severities\"=>[2]}} #=1 sev=2\n","REMEDIATION: Triggering remediation check 'light_remediation' for [\"LAMP01\"]\n","REMEDIATION: Received API Response (404): , exiting.\n"]

Light Remediation Check
root@sensu:/etc/sensu/conf.d# cat light_remediation.json
{

 "checks":{

   "light_remediation": {
       "command": "/usr/sbin/service restart apache2",
       "subscribers": [],
       "handlers": ["debug"],
       "publish": false
       },

    }
}

Finally the actual check
{
   "checks":{
     "apache-status-central":{
        "command":"/etc/sensu/plugins/check-http.rb -u http://lamp01/",
        "interval":30,
        "subscribers":["apache"],
        "handlers":["default","remediator"],

        "remediation": {
         "light_remediation": {
           "occurrences": [1, 2],
           "severities": [2]
          }
        }
      }
  }
}

Client Config on Lamp01
{
   "client": {
    "name": "LAMP01",
    "address": "<IP_ADDRESS>",
    "subscriptions":["linux","apache","LAMP01"]
  }
}

Thanks!

@MikeMester your remediation check definition has a typo (comma at end of line) this could explain why the check returns 404 when the server triggers it (if it is invalid javascript it is probably skipped, maybe with a warning in the log).
You should also update the remediation command to "sudo /usr/sbin/service apache2 restart" and add a sudoers entry as below.
root@xxx:~# cat /etc/sudoers.d/sensu-apache
sensu ALL=(root:sensu) NOPASSWD:/usr/sbin/service apache2 restart

Other than that, your check definitions look fine to me.

awesome!  that is working and i did the sudoers as well.  Thank you

I'm having a similar issue as @MikeMester @jperville Can you take a look at my configuration?
On the sensu server I have the light remediation check
light_remediation.json
{

 "checks":{

   "light_remediation": {
       "command": "/bin/sh /etc/sensu/plugins/puma_restart.sh",
       "subscribers": [],
       "handlers": ["debug"],
       "publish": false
       }

    }
}

And now the actual check
check_memory_puma.json  Note: The check mem warning/critical values are blown up high just to trigger the check and test.  These will be scaled back down once I get this working.
{
   "checks":{
     "memory_puma":{
        "command":"/etc/sensu/plugins/check-mem.sh -w 90000000 -c 100000000",
        "interval":10,
        "subscribers":["rh"],
        "handlers":["default","remediator", "mailer"],

        "remediation": {
         "light_remediation": {
           "occurrences": [1, 2],
           "severities": [2]
          }
        }
      }
  }
}

Here is the endpoint/client configuration
client.json
{
  "client": {
    "name": "university",
    "address": "<IP_ADDRESS>",
    "subscriptions": [
      "linux", "web-server", "rh"
    ]
  }
}

After adding this to sensu, flushing redis, restarting sensu server/api/etc In my sensu-server.log I get the following output.
{"timestamp":"2016-04-19T19:26:47.535032-0500","level":"info","message":"processing event","event":{"id":"cce4da9f-31ff-4e73-8f1d-afcd02cacb79","client":{"name":"university","address":"<IP_ADDRESS>","subscriptions":["linux","web-server","rh"],"version":"0.20.3","timestamp":1461112003},"check":{"command":"/etc/sensu/plugins/check-mem.sh -w 90000000 -c 100000000","interval":10,"subscribers":["rh"],"handlers":["remediator","mailer"],"remediation":{"light_remediation":{"occurrences":[1,2],"severities":[1]},"medium_remediation":{"occurrences":["3-10"],"severities":[1]},"heavy_remediation":{"occurrences":["1+"],"severities":[2]}},"name":"memory_puma","issued":1461112007,"occurrences":1,"refresh":10,"executed":1461112007,"duration":0.012,"output":"MEM CRITICAL - free system memory: 5665 MB\n","status":2,"history":["2","2","2","2","2","2","2","2","2","2","2","2","2","2","2","2","2","2","2","2","2"],"total_state_change":0},"occurrences":43,"action":"create"}}

{"timestamp":"2016-04-19T19:26:48.108427-0500","level":"info","message":"handler output","handler":{"type":"pipe","command":"/etc/sensu/handlers/remediator.rb","name":"remediator"},"output":["REMEDIATION: Evaluating remediation: university {\"light_remediation\"=>{\"occurrences\"=>[1, 2], \"severities\"=>[1]}, \"medium_remediation\"=>{\"occurrences\"=>[\"3-10\"], \"severities\"=>[1]}, \"heavy_remediation\"=>{\"occurrences\"=>[\"1+\"], \"severities\"=>[2]}} #=43 sev=2\n","REMEDIATION: Matchdata: #<MatchData \"1+\" 1:\"1\">\n","REMEDIATION: Triggering remediation check 'heavy_remediation' for [\"university\"]\n","REMEDIATION: Recieved API Response (404): , exiting.\n"]}

And just a sample of the client log on the endpoint
{"timestamp":"2016-04-19T19:29:07.539531-0500","level":"info","message":"publishing check result","payload":{"client":"university","check":{"name":"memory_puma","issued":1461112147,"command":"/etc/sensu/plugins/check-mem.sh -w 90000000 -c 100000000","executed":1461112147,"duration":0.011,"output":"MEM CRITICAL - free system memory: 5665 MB\n","status":2}}}

I'm really confused as to why this is happening.  I'm a bit new to using remediation and really need a hand getting this working.  My purpose is to check for a certain memory threshold then execute a script on the endpoint that restarts puma (rails/ruby app server).  The script works fine, but I'm getting the API 404 error as others have experienced.
Any help?  I'm about to dropkick my computer 👍

Hi @shakycode ,
Your problem is here: "output":["REMEDIATION: Evaluating remediation: >>>university<<< {\"light_remediation\" [snip],
Here is how it works: when the sensu check fails, the remediator handler is invoked; then the remediator handler emits a custom check request ("light_remediation") which is targeted at the affected client only; the "hack" to make the check request go only to the affected client is to make each client subscribe it their own name (which must be unique and cannot be an existing subscription name such as "db" or "web-server").
Try modifying the client.json like this:
{
  "client": {
    "name": "university",
    "address": "<IP_ADDRESS>",
    "subscriptions": [
      "linux", "web-server", "rh", "university"
    ]
  }
}

Then restart the sensu client and report us your success.

@jperville Ok I did exactly what you said.  Restarted the client also flushed redis/restarted sensu on the server to have a clean point.
Here's what my client.json looks like on the university box:
{
  "client": {
    "name": "university",
    "address": "<IP_ADDRESS>",
    "subscriptions": [
      "linux", "web-server", "puma", "university"
    ]
  }
}

I'm still getting the same error after restart everything and flushing redis
{"timestamp":"2016-04-20T05:02:27.542075-0500","level":"info","message":"processing event","event":{"id":"ec7133d6-901d-4bd2-b16b-015fc4f52394","client":{"name":"rh","address":"<IP_ADDRESS>","subscriptions":["linux","web-server","puma","rh"],"version":"0.20.3","timestamp":1461146545},"check":{"command":"/etc/sensu/plugins/check-mem.sh -w 900000 -c 1000000","interval":10,"subscribers":["puma"],"handlers":["default","remediator","mailer"],"remediation":{"light_remediation":{"occurrences":[1,2],"severities":[2]}},"name":"memory_puma","issued":1461146547,"executed":1461146547,"duration":0.014,"output":"MEM CRITICAL - free system memory: 13601 MB\n","status":2,"history":["2","2"],"total_state_change":0},"occurrences":2,"action":"create"}}
{"timestamp":"2016-04-20T05:02:27.557410-0500","level":"info","message":"handler output","handler":{"type":"pipe","command":"cat","name":"default"},"output":["{\"id\":\"ec7133d6-901d-4bd2-b16b-015fc4f52394\",\"client\":{\"name\":\"rh\",\"address\":\"<IP_ADDRESS>\",\"subscriptions\":[\"linux\",\"web-server\",\"puma\",\"rh\"],\"version\":\"0.20.3\",\"timestamp\":1461146545},\"check\":{\"command\":\"/etc/sensu/plugins/check-mem.sh -w 900000 -c 1000000\",\"interval\":10,\"subscribers\":[\"puma\"],\"handlers\":[\"default\",\"remediator\",\"mailer\"],\"remediation\":{\"light_remediation\":{\"occurrences\":[1,2],\"severities\":[2]}},\"name\":\"memory_puma\",\"issued\":1461146547,\"executed\":1461146547,\"duration\":0.014,\"output\":\"MEM CRITICAL - free system memory: 13601 MB\\n\",\"status\":2,\"history\":[\"2\",\"2\"],\"total_state_change\":0},\"occurrences\":2,\"action\":\"create\"}"]}
{"timestamp":"2016-04-20T05:02:28.072295-0500","level":"info","message":"handler output","handler":{"type":"pipe","command":"/etc/sensu/handlers/remediator.rb","name":"remediator"},"output":["REMEDIATION: Evaluating remediation: university {\"light_remediation\"=>{\"occurrences\"=>[1, 2], \"severities\"=>[2]}} #=2 sev=2\n","REMEDIATION: Triggering remediation check 'light_remediation' for [\"university\"]\n","REMEDIATION: Recieved API Response (404): , exiting.\n"]}

Any other thoughts?  I swapped out the rh subscription on all endpoints since one of the endpoints hostname was rh for a general subscription of puma  But I've isolated the university machine for testing and added university to the client.json on university and no luck.  Any other thoughts?
Should I try to put these checks on the actual client too? Or just leave them on the sensu server (master)?

Hi @shakycode,
The check definitions and the remediator plugin go on the sensu server (remediation is incompatible with standalone checks). The client definition ("client.json") go on the sensu client ("university").
Make sure you have restarted the sensu client ("university"); if you are using a graphical frontend such as "uchiwa" can you show me the list of subscriptions for client "university" as seen by the server?
Also, be careful of typos, I once made a typo in "occurrences" and I spent some time figuring out why my remediation was not triggering (in your case it is triggering, but 404, so I think that the server is not aware of the light_remediation check).
Here is a real world, working example, that I have on my server:
root@staging4-backends-lb:/etc/sensu/conf.d/checks# cat fstab-mounts.json
{
  "checks": {
    "fstab-mounts": {
      "command": "check-fstab-mounts.rb",
      "handlers": ["default", "remediator"],
      "subscribers": ["system"],
      "interval": 60,
      "occurrences": 1,
      "refresh": 600,
      "remediation": {
        "fstab-mounts-remediation": {
          "occurrences": ["1+"],
          "severities": [2]
        }
      }
    }
  }
}
root@staging4-backends-lb:/etc/sensu/conf.d/checks# cat fstab-mounts-remediation.json
{
  "checks": {
    "fstab-mounts-remediation": {
      "command": "sudo /bin/mount -a && sudo /sbin/swapon -a",
      "handlers": ["default"],
      "subscribers": [],
      "publish": false,
      "interval": 30
    }
  }
}
root@staging4-backends-lb:/etc/sensu/conf.d/checks# cat ../client.json
{
  "client": {
    "name": "staging4-backends-lb",
    "address": "<IP_ADDRESS>",
    "subscriptions": [
...
      "staging4-backends-lb",
      "system"
    ],
    "node": "staging4:staging4-backends-lb"
  }
}

To test the check, I type 'swapoff -a' and the remediation should trigger, mounting the swap.
Note that since running 'swapon -a' and mounting are privileged action I had to allow the sensu users to run these actions passwordless during the remediation, see below.
root@staging4-backends-lb:/etc/sensu/conf.d/checks# cat /etc/sudoers.d/sensu-mount
sensu ALL=(root:sensu) NOPASSWD:/bin/mount -a
sensu ALL=(root:sensu) NOPASSWD:/sbin/swapon -a

Can you try to run my example on your server?

@jperville Hi there, thanks for the early response.  Here's my setup now:
/etc/sensu/conf.d/checks/check_memory_puma.json
{
  "checks": {
    "memory_puma": {
      "command": "/etc/sensu/plugins/check-mem.sh -w 900000 -c 1000000",
      "handlers": ["default", "remediator", "mailer"],
      "subscribers": ["system"],
      "interval": 10,
      "occurrences": 1,
      "refresh": 10,
      "remediation": {
        "light_remediation": {
          "occurrences": ["1+"],
          "severities": [2]
        }
      }
    }
  }
}

**/etc/sensu/conf.d/checks/light_remediation.json **
{
  "checks": {
    "light_remediation": {
      "command": "/etc/sensu/plugins/puma_restart.sh",
      "handlers": ["default"],
      "subscribers": [],
      "publish": false,
      "interval": 30
    }
  }
}

** end point /etc/sensu/conf.d/client.json **
{
  "client": {
    "name": "university",
    "address": "<IP_ADDRESS>",
    "subscriptions": [
      "linux", "web-server", "system", "university"
    ]
  }
}

In uchiwa here is the list of the subscriptions for University

Even after setting it up nearly identical (I cut/pasted your configuration and just used my script), this is what I get in the sensu-server.log
{"timestamp":"2016-04-20T05:49:08.139697-0500","level":"info","message":"handler output","handler":{"type":"pipe","command":"/etc/sensu/handlers/remediator.rb","name":"remediator"},"output":["REMEDIATION: Evaluating remediation: university {\"light_remediation\"=>{\"occurrences\"=>[\"1+\"], \"severities\"=>[2]}} #=63 sev=2\n","REMEDIATION: Matchdata: #<MatchData \"1+\" 1:\"1\">\n","REMEDIATION: Triggering remediation check 'light_remediation' for [\"university\"]\n","REMEDIATION: Recieved API Response (404): , exiting.\n"]}

I'm ready to give up and restart this stuff manually when alerts come... but that's going against the remediation technique that I'm trying to achieve :(

Can you show a screenshot of the "checks" tab in uchiwa where the light_remediation should be listed?

@jperville Here's the screenshot for checks in uchiwa

Have to go lunch, but the next step we will investigate is if your remediation request made it to the sensu API (which is not same process as the sensu server).

@jperville ok thanks.  Hope to hear from you soon.  You can also reach me directly at<EMAIL_ADDRESS>or on twitter as "shakycode" 👍

@jperville FYI here's an excerpt of my API log from the sensu server:
{"timestamp":"2016-04-20T06:19:59.080800-0500","level":"info","message":"POST /checks/request","remote_address":"<IP_ADDRESS>","user_agent":"Ruby","request_method":"POST","request_uri":"/checks/request","request_body":"{\"check\":\"light_remediation\",\"subscribers\":[\"university\"]}"}

And here's a log excerpt from the university endpoint from the sensu-client.log
{"timestamp":"2016-04-20T06:21:39.250195-0500","level":"warn","message":"previous check command execution in progress","check":{"name":"memory_puma","issued":1461151299,"command":"/etc/sensu/plugins/check-mem.sh -w 900000 -c 1000000"}}
{"timestamp":"2016-04-20T06:21:39.260468-0500","level":"info","message":"publishing check result","payload":{"client":"university","check":{"name":"memory_puma","issued":1461151299,"command":"/etc/sensu/plugins/check-mem.sh -w 900000 -c 1000000","executed":1461151299,"duration":0.013,"output":"MEM CRITICAL - free system memory: 5517 MB\n","status":2}}}

Hope this helps some :)

In my logs, the remediator posts to /request and not to /checks/request.
Can you edit /etc/sensu/handlers/remediator.rb on your sensu server and modify the trigger_remediation method at the end to look like this?
  # Issue a check via the API
  def trigger_remediation(check, subscribers)
    api_request(:POST, '/request') do |req|
      req.body = JSON.dump('check' => check, 'subscribers' => subscribers)
    end
  end

The problem is probably because a route has moved since earlier version, and then the 404 response from API to the remediator is totally justified.
Note: I am using sensu 0.20.6-1, but I started using the remediator plugin around version 0.18.

@jperville OMG YES! editing the remediator.rb and changing the API post path worked like a champ.  I'm all good now!

For information, the code of my remediator plugin is this version (the last one before "good bye" commit) : https://github.com/sensu/sensu-community-plugins/blob/e58c1f3ce39c6c0ca271fadd470c04362e92b190/handlers/remediation/sensu.rb

It looks like we have solved this issue, some users were using broken implementation of the remediator plugin which posted to /checks/request instead of /request, resulting in a deserved 404 response from API.

@jperville thanks so much, I'm remediating!!! Shirt and gift coming your way 👍


[BUG] Unable to subslass property of a property

ECS integration/library project(s) (e.g. Elastic.CommonSchema.Serilog): 1.5.3
ECS schema version (e.g. 1.4.0): 1.5.0
ECS .NET assembly version (e.g. 1.4.2): 1.5.3
Elasticsearch version (if applicable): n/a
.NET framework / OS: ASP.NET Core 3.1
Description of the problem, including expected versus actual behavior:
ECS 1.5 doesn't have property id in HttpRequest, so I decided to subclass it in order to have request id in place. I've tried two things:

I've created CustomHttpRequest which inherits HttpRequest and adds Id property. However, serialized event doesn't contain Id property because System.Text.JsonSerializer has a limited support of lower-level properties: "You can get polymorphic serialization for lower-level objects if you define them as type object"

public class CustomHttpRequest : HttpRequest
{
    [DataMember(Name = "id")]
    public string? Id { get; set; }
}

I've created CustomHttp which inherits Http, adds property of type CustomHttpRequest as Request and hides original property. During serialization it fails with an error "The JSON property name for 'MyNamespace.CustomHttp.Request' collides with another property", obviously serializer doesn't recognize that the property is hidden,

public class CustomHttp : Http
{
    public new CustomHttpRequest? Request { get; set; }
}

I'd expect a standard way of extending lower-level properties (apart from resurrecting this repo and updating it to the latest versions of ECS of course 😃 ).
Steps to reproduce:
See above

We do support injecting new properties on fieldsets by subclassing Entities e.g
https://github.com/elastic/ecs-dotnet/blob/600e7110dc5fde28c5495dc86e1d3d0f9d83adc2/tests/Elastic.CommonSchema.Tests/Serializes.cs#L121-L135
Is that sufficient?

Closing this as the linked test case should provide a way forward to introduce subclasses with extensions.


OneNote plugin : improve finding notebooks, sections and page title

Description of the new feature / enhancement
Current behavior
Currently, it seems running the query in the page content and prioritize those results. This fails to bring up a relevant result.
Examples
If I have a section named MS Office searching for this exact string will return only pages containing this string and not the section itself. It feels strange.
Same if I have this time a page named Test, it will bring up every page containing the string test first instead of rank up the page where the string is in the page name.

Improvement idea

Always rank the results according to where the query is found. First in notebook name, next in section name, next in page title, then in page content.
Allow syntax to filter results according to their type : notebook, section, page title, content
Allow syntax to narrow search like a path but still being fuzzy.
4. If I have multiple pages titled Test in different section and notebook, I’d like to find them according their location. Let’s say current location is Notebook: “Coding”, Section: “Powershell” I could type : c/ps#test to bring up this page as the first and probably only result matching this path.
Add an option to open results in a new OneNote session because I often have one session already opened that I don’t want it to be replaced.

How this last feature could work
Idea 1
As soon as the plugin detects a slash / or backslash \ or a # in the search, it should infer that strings on the left and right of it are in hierarchical relation and # as prefix always to a page title. If it doesn’t find any title. It search for content with this string.
Every page has a path like : onenote:https://d.docs.live.net/some_id/Documents/Notebook/Section%20Title.one#Page Title&section-id={some-guid}&page-id={some-other-guid}&end
Maybe it could be used as a schema. It seems the plugin can access the page location with
@$"{p.Notebook.Name}\{p.Section.Name}\{p.Name}"

Idea 2
A syntax to filter results according to their type. Any idea welcome. Here is mine.

#n: for Notebook
#s: for section
# for page name
if accessible ## any title in content

At least, the # for page name should be the most useful on a daily case to narrow the results to only a few easy to scan.
Most of the query could be like #page name to search for page name containing the page name.
And #page name/string to search any string in the page where name containing page name.
#page name could be in a fuzzy query to return result. To take up the earlier query example : c/ps#test for Notebook: “Coding”, Section: “Powershell”, Page: “Test”I could instead make a query like#n:c/#s:ps/#test. I don’t like it very much but may be easier to implement than the simple c/ps#testor simplyps#test` because not most of the time it will be enough to get exactly the page we want.
Scenario when this would be used?
Get the very notebook or section or note we want to jump into just by passing a prefix.
Supporting information
No response

I just came here to file a similar issue, to get notebook/section titles to show up in search. I like your idea of sorting them based on the hierarchical relevance as well. That could be implemented pretty easily. Is that something you want to tackle?

Unfortunately, not my specialty and no time right now.


Unable to start debugging. No process is associated with this object when starts debugging

Type: Bug Report
OS and Version: Mac os 12.5.1
VS Code Version: 1.71
Embedded Tools Extension Version:v0.3.220909001
Target embedded device: Nucleo F446RE
Description:
When I launch program, I get this error. Next I get information: "ERROR: Unable to start debugging. No process is associated with this object." I'm so confused, because I can open arm-none-eabi-gdb file.

I don't think we've been able to replicate this yet. In discussions we suspect it is a signing issue. See section 5.1 of ST's STM32CubeIDE installation manual. The guide walks you through trusting the STM32CubeIDE.app either via macOS system preferences or the command line. Looking at the error message I would hope that is enough as gdb is within that path. This is the cli command from the docs.
xattr -c /Applications/STM32CubeIDE.app

@robotdad thanks for your reply. I executed this command and now everything works correctly. But when I start debugging without plugged in stm microcontroller I get the same information as above. Please change it to be correct when board is not connected to pc.


Set default data retrieval nr to 50

Set default data retrieval nr to 50. (on the end of the results page currently set to 2500)

this has been done in #2354


feat: add support for blogpost from other (generic) platforms

Description

This Pull Request adds support for blogpost from other platforms in highlights. Leverages the open-graph node library, fetches the open graph data from the given blogpost url provided as highlightLink and uses the image property on the data as the blogspot highlight type social image when posting new highlights.
Implementation Caveat 🤔

No Support for Auto-Summarize

This is specifically because in order to consume the auto-summarize function, the generateDevToBlogHighlightSummary (which is an auto-summary function for the DevTo blogpost) takes two(2) arguments namely the blogTitle and blogMarkdown (which is the blog post content). This implementation uses the open-graph to fetch meta data which satisfies only the blogTitle. There isn't a straight-forward or consistent or lightweight implementation (aside scrapping 🤫) to access the body content of this generic blog post.
In the absence of the body content of this blog post, I hence settled for implementing a notice of no-support for auto-summarize for the auto-summarize feature on the generic blog post for now.
Changes Made

Refactored all DevTo related components and functions, to reflect DevTo*** in its naming to make them more specific to dev.to blog post type
Added a fetchOGData endpoint in the /api route which fetches open-graph data for specified url

const og = require("open-graph");

export default async function handler(req: NextApiRequest, res: NextApiResponse) {
  const url = req.query.url;
  if (req.method === "GET") {
    og(url, (error: any, meta: {}) => {
      if (!error) {
        res.status(200).json({ response: meta });
      } else {
        res.status(200).json({ response: {} });
      }
    });
  }
}

Added GenericBlogOpenGraphImage component which consumes the fetchOGData endpoint, builds and sends response image as returned component node.
Added a isValidURL helper function to validate url input in the highlightLink field on highlight input form.
Integrated the the GenericBlogOpenGraphImage component and isValidURL function in appropriate base components.
Fixed edge case where repository are automatically tagged to blogposts without intentionally tagged repos, resulting in repositories url that do not exist.
Implemented a toast in attempt to add notification for auto-summarize not being supported for blogpost from these generic platform because we do not currently have any means of accessing the exact blog post body content which is one of the required parameter/content for auto-summarize.

const handleGenerateHighlightSummary = async () => {
  ....

  // 🍕🍕🍕 NOTICE HERE 🍕🍕🍕
  if (highlightLink && (!highlightLink.includes("github.com") || !highlightLink.includes("dev.to"))) {
    toast({
      description: "Auto-Summarize not supported for current link!",
      title: "Oops!",
      variant: "warning",
    });
    return;
  }

  ....
};

🍕
What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Fixes #1656
Mobile & Desktop Screenshots/Recordings

Writing a (Generic) Blogpost highlight type
screencast-localhost_3000-2023.10.15-04_00_37.webm
Blogpost (without tagged repos)

Blogpost (with tagged repos)

Demo: Toast for Not Supported Message for Auto-Summarize

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
This PR adds a new package open-graph
[optional] What gif best describes this PR or how it makes you feel?

Hey @babblebey, would you mind fixing up the merge conflict before we proceed to reviewing this pr?

All set @jpmcb
Cc @OgDev-01
🍕

All set @jpmcb
Cc @OgDev-01
🍕

@babblebey would you mind resolving the merge conflicts on this?

Hey @babblebey I'm going to move this to draft mode until you have time to work on it.

Hey apologies @BekahHW, this proved super weird of a conflict to resolve, after many attempts at resolving, It kept coming back asking that I resolve over and over again.
I ended up moving for rebasing and that brought in all the 390 changes 😞
PR still works as it should for sure. I don't know exactly what impact the 390 changes would make on merge whenever it gets there, but I do recognize how uneasy it's become to review this PR now.... So kindly guide me here, will you say I keep this PR as is or would you prefer that I repatch this feature in another new PR that can remove the burden of the out-of-context 300+ file changes!?
Cc @OgDev-01 @jpmcb

At this point this is not reviewable and the PR is getting stale.
My recommendation is create a new PR from a new branch from beta and cherry picking the commits you actually need.
Going to close this PR since this will require git surgery or some serious fixing to get back to unity.

git surgery 😂🤣
I should patch this in less than 24h now, and I just mistakenly clicked "Delete Branch" 🤦🏾


HPA stuck in pending state when HPA is created with metrics type pod/object/external

Version: Master
Steps:

Create a deployment in a RKE cluster
Create a HPA pointing to a the deployment for the metrics type Pod/Object/External

The HPA is stuck in pending state with the below error in API
"the HPA was unable to compute the replica count: unable to get metric testpod: unable to fetch metrics from custom metrics API: no custom metrics API (custom.metrics.k8s.io) registered"

The custom metrics server associated with pod/object/external types is not available by default .
Should these metrics types be disabled in UI ?

It looks like there is no way to detect if users deployed the custom metrics server

I think the error message in the HPA transition message helps?
I don't think we should disable it by default if we cannot detect custom metrics.

The HPA was unable to compute the replica count: unable to get metric sadf: unable to fetch metrics from custom metrics API: no custom metrics API (custom.metrics.k8s.io) registered
@orangedeng is there a way we can check if custom metrics API (custom.metrics.k8s.io) registered or not?
If we can do that, we disable it in UI when it is not registered

Yes, but we need to introduce apiservice.apiregistration.k8s.io resource into Rancher API to do it.

We will add a warning for preview release first. https://github.com/rancher/rancher/issues/20866
But we should remove it once we get this issue fixed

For any cluster, check what version of HPA API is being used. List the version that's being used and that Rancher's requirements is v2beta2 (or whatever it is.

Added the warning for HPA created with metrics type pod/object/external.

Tested with master-head build from Aug 1st.
Create a deployment in a RKE cluster
Create a HPA pointing to a the deployment for the metrics type Pod/Object/External
During the HPA creation, there is a warning :


negative build times

Build times turn up as negative

Backpack's too fast.

It compiles your code before you've even finished writing it.

Hmmmmm.

It needs to be faster.


Hint is being overflowed

Hi currently I am facing this bug on the UI

Any pro tips to fix this one ? Thanks.

I can fix with a little trick with JS

It'd be best to file an issue at Lock's repo for this -- this addon simply links Lock and ember-simple-auth together, and it doesn't touch Lock's styling or behavior in any way.


polish: Overnight row no schedule tomorrow

Notion task: Moon icon is displayed in place of scheduled time when there is no scheduled departure the next morning
If a route is in overnight mode and has no scheduled trips the next service day, we still want to show the row with a moon icon instead of a time. This one takes some hardcoding to test, so reach out if you have any trouble testing locally.

[ ] Tests added?

Having a couple issues with this branch -- might be because my testing methods are outdated. (Just making a comment because didn't want to ping you on slack while you're vacationing!)


Update email address on profile

The email address should be able to be changed without changing the password at the same time.

Hi!
I should explain why, but there is a reason why it's not possible :p
The Gladys Gateway is not a traditional backend:
-> your password is never sent to the backend
-> your private keys are encrypted with a hash composed of the email + password
If you want to change the email or password, the keys need to be encrypted again so the password should be provided (even if it's the same password)
But you're right it's not clear enough right now why :)


Consider supporting superaccessors

trait T1 {
  def x: Int = ???
}

trait T2 extends T1 {
  def y: Int = super.x
}

13:31 ~/Projects/2126/sandbox (HEAD)$ s -Xprint:refchecks
[[syntax trees at end of                 refchecks]] // Test.scala
package <empty> {
  abstract trait T1 extends scala.AnyRef {
    def /*T1*/$init$(): Unit = {
      ()
    };
    def x: Int = scala.Predef.???
  };
  abstract trait T2 extends AnyRef with T1 {
    <superaccessor> <artifact> private def super$x: Int;
    def /*T2*/$init$(): Unit = {
      ()
    };
    def y: Int = T2.this.super$x
  }
}

Unlike other synthetic trees that we filter out in metacp (e.g. extension methods for value classes), superaccessors can't really be synthesized on the fly by SemanticDB consumers, since they are created lazily based on tree contents. This suggests a potential information loss.

Looks like the SuperAccessors phase also sometimes generates methods that start with protected$. I don't fully understand why these methods are created, but unlike super$ methods they aren't filtered out by SemanticDB generators.


Preconfigure fails due to missing MaxMemory for elastic agent config

The preconfigure script gets an error when trying to apply the elastic kubernetes agent profile because it doesn't set a value for MaxMemory which is required. I'm guessing GoCD or the elastic agent plugin changed at some point to require that field.

That sounds odd. I'm sure ive used it off the shelf recently with default configs and not had issues but can check.
Can you report your specific chart, GoCD and plugin versions to avoid confusion?

I can check. I'll admit the setup is a little weird because it's our internal minikube dev setup. We're also using our own GoCD image based on the official one. This was hard to debug because it's hard to see the logs from the preconfigure script.
GoCD version 21.4.0
Elastic Agent Version 3.4.0-196
Our dockerfile for GoCD server
USER root
RUN  cd /home/go \
     && curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" \
     && unzip awscliv2.zip \
     && ./aws/install
ENTRYPOINT ["/docker-entrypoint.sh"]
USER go```

Chart version: 1.39.3

I just tried it with a script locally and what I thought was failing worked. Not sure why. I guess maybe it's not broken. It's hard to debug because the script output doesn't go to the kubernetes logs and if it fails the container stops and I can't read the logs easily because I can't kubectl exec on a dead pod.

I take that back, I tried it with MaxMemory and it worked, if I remove max memory it fails.
Fails:
#!/bin/bash

set -x

SERVICE_ACCOUNT_PATH=/var/run/secrets/kubernetes.io/serviceaccount
KUBE_TOKEN=$(kubectl -n gocd exec --stdin --tty $(kubectl -n gocd get pods | grep gocd-server | awk '{print $1}') -- cat ${SERVICE_ACCOUNT_PATH}/token)
KUBERNETES_SERVICE_HOST=$(kubectl -n gocd exec --stdin --tty $(kubectl -n gocd get pods | grep gocd-server | awk '{print $1}') -- sh -c 'echo $KUBERNETES_SERVICE_HOST')
KUBERNETES_SERVICE_PORT_HTTPS=$(kubectl -n gocd exec --stdin --tty $(kubectl -n gocd get pods | grep gocd-server | awk '{print $1}') -- sh -c 'echo $KUBERNETES_SERVICE_PORT_HTTPS')

curl --fail -i -v -k 'https://gocd.development.example.com/go/api/elastic/profiles' \
  -H 'Accept: application/vnd.go.cd+json' \
  -H 'Content-Type: application/json' \
  -X POST -d '{
    "id": "demo-app",
    "cluster_profile_id": "k8-cluster-profile",
    "properties": [
      {
        "key": "Image",
        "value": "gocd/gocd-agent-docker-dind:v21.3.0"
      },
      {
        "key": "PodConfiguration",
        "value": "apiVersion: v1\nkind: Pod\nmetadata:\n  name: gocd-agent-{{ POD_POSTFIX }}\n  labels:\n    app: web\nspec:\n  serviceAccountName: default\n  containers:\n    - name: gocd-agent-container-{{ CONTAINER_POSTFIX }}\n      image: gocd/gocd-agent-docker-dind:v21.3.0\n      securityContext:\n        privileged: true"
      },
      {
        "key": "PodSpecType",
        "value": "yaml"
      },
      {
        "key": "Privileged",
        "value": "true"
      }
    ]
  }'

Works
#!/bin/bash

set -x

SERVICE_ACCOUNT_PATH=/var/run/secrets/kubernetes.io/serviceaccount
KUBE_TOKEN=$(kubectl -n gocd exec --stdin --tty $(kubectl -n gocd get pods | grep gocd-server | awk '{print $1}') -- cat ${SERVICE_ACCOUNT_PATH}/token)
KUBERNETES_SERVICE_HOST=$(kubectl -n gocd exec --stdin --tty $(kubectl -n gocd get pods | grep gocd-server | awk '{print $1}') -- sh -c 'echo $KUBERNETES_SERVICE_HOST')
KUBERNETES_SERVICE_PORT_HTTPS=$(kubectl -n gocd exec --stdin --tty $(kubectl -n gocd get pods | grep gocd-server | awk '{print $1}') -- sh -c 'echo $KUBERNETES_SERVICE_PORT_HTTPS')

curl --fail -i -v -k 'https://gocd.development.example.com/go/api/elastic/profiles' \
  -H 'Accept: application/vnd.go.cd+json' \
  -H 'Content-Type: application/json' \
  -X POST -d '{
    "id": "demo-app",
    "cluster_profile_id": "k8-cluster-profile",
    "properties": [
      {
        "key": "Image",
        "value": "gocd/gocd-agent-docker-dind:v21.3.0"
      },
      {
        "key": "PodConfiguration",
        "value": "apiVersion: v1\nkind: Pod\nmetadata:\n  name: gocd-agent-{{ POD_POSTFIX }}\n  labels:\n    app: web\nspec:\n  serviceAccountName: default\n  containers:\n    - name: gocd-agent-container-{{ CONTAINER_POSTFIX }}\n      image: gocd/gocd-agent-docker-dind:v21.3.0\n      securityContext:\n        privileged: true"
      },
      {
        "key": "PodSpecType",
        "value": "yaml"
      },
      {
        "key": "MaxMemory",
        "value": "1G"
      },
      {
        "key": "Privileged",
        "value": "true"
      }
    ]
  }'

+ SERVICE_ACCOUNT_PATH=/var/run/secrets/kubernetes.io/serviceaccount
+++ kubectl -n gocd get pods
+++ grep gocd-server
+++ awk '{print $1}'
++ kubectl -n gocd exec --stdin --tty development-gocd-server-665879b8b7-dbcmk -- cat /var/run/secrets/kubernetes.io/serviceaccount/token
Defaulted container "gocd-server" out of: gocd-server, vault-authenticator (init), ssh-key-render (init), opsgenie-secret-render (init), users-render (init), gocd-analytics-plugin-js-init-container (init)
+ KUBE_TOKEN=eyJhbGciOiJSUzI1NiIsImtpZCI6ImQ5R3NVa3llcnBKbmZpUTZRbHBYQVhuS1NfbFZSZDkxTnVNbnRaNkp6emMifQ.eyJhdWQiOlsiaHR0cHM6Ly9rdWJlcm5ldGVzLmRlZmF1bHQuc3ZjLmNsdXN0ZXIubG9jYWwiXSwiZXhwIjoxNjk4ODU2NzMyLCJpYXQiOjE2NjczMjA3MzIsImlzcyI6Imh0dHBzOi8va3ViZXJuZXRlcy5kZWZhdWx0LnN2Yy5jbHVzdGVyLmxvY2FsIiwia3ViZXJuZXRlcy5pbyI6eyJuYW1lc3BhY2UiOiJnb2NkIiwicG9kIjp7Im5hbWUiOiJkZXZlbG9wbWVudC1nb2NkLXNlcnZlci02NjU4NzliOGI3LWRiY21rIiwidWlkIjoiZDcyM2RiNmUtZTYzZi00YTA4LTk2OWEtZDc1YmM0NDczNDdmIn0sInNlcnZpY2VhY2NvdW50Ijp7Im5hbWUiOiJkZXZlbG9wbWVudC1nb2NkIiwidWlkIjoiMGI3ZTJmZGItOWQxYy00NzdlLWI4YWUtNzIzNDFmMjJiZGZkIn0sIndhcm5hZnRlciI6MTY2NzMyNDMzOX0sIm5iZiI6MTY2NzMyMDczMiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50OmdvY2Q6ZGV2ZWxvcG1lbnQtZ29jZCJ9.SIwPPOdt4-4K6-fuwAz_ZTbcdevNFt7GghylwEdW346a0mn2Eu8x6FX9bstGV23snB6lAt2Z2eXEJR9CuPLbhO4Suyg3rjt8fou7GYZCgf3xRKqb42tzcfRIplc-OZVM0TjTU3am-Qy5IU4m2b3GQkkmd_bUryGOCmx470zGqGQK3m2sBsFX95bD5g2Y7pVobfcivu_IPX4AEAsQ_3_AZ3j4jZ_gw74HEHRRx0-h32xHeAknzapHpgPbFVqNHXH2fBM18geLEZ76_8i4dVJyz5TpclU_EA8dTpfb3lvJp_IklTZulwQ9yvpPol5HEEamKIFFW3eYV0t3MfaVqWXuig
+++ kubectl -n gocd get pods
+++ grep gocd-server
+++ awk '{print $1}'
++ kubectl -n gocd exec --stdin --tty development-gocd-server-665879b8b7-dbcmk -- sh -c 'echo $KUBERNETES_SERVICE_HOST'
Defaulted container "gocd-server" out of: gocd-server, vault-authenticator (init), ssh-key-render (init), opsgenie-secret-render (init), users-render (init), gocd-analytics-plugin-js-init-container (init)
+ KUBERNETES_SERVICE_HOST=$'<IP_ADDRESS>\r'
+++ kubectl -n gocd get pods
+++ grep gocd-server
+++ awk '{print $1}'
++ kubectl -n gocd exec --stdin --tty development-gocd-server-665879b8b7-dbcmk -- sh -c 'echo $KUBERNETES_SERVICE_PORT_HTTPS'
Defaulted container "gocd-server" out of: gocd-server, vault-authenticator (init), ssh-key-render (init), opsgenie-secret-render (init), users-render (init), gocd-analytics-plugin-js-init-container (init)
+ KUBERNETES_SERVICE_PORT_HTTPS=$'443\r'
+ curl --fail -i -v -k https://gocd.development.example.com/go/api/elastic/profiles -H 'Accept: application/vnd.go.cd+json' -H 'Content-Type: application/json' -X POST -d '{
    "id": "demo-app",
    "cluster_profile_id": "k8-cluster-profile",
    "properties": [
      {
        "key": "Image",
        "value": "gocd/gocd-agent-docker-dind:v21.3.0"
      },
      {
        "key": "PodConfiguration",
        "value": "apiVersion: v1\nkind: Pod\nmetadata:\n  name: gocd-agent-{{ POD_POSTFIX }}\n  labels:\n    app: web\nspec:\n  serviceAccountName: default\n  containers:\n    - name: gocd-agent-container-{{ CONTAINER_POSTFIX }}\n      image: gocd/gocd-agent-docker-dind:v21.3.0\n      securityContext:\n        privileged: true"
      },
      {
        "key": "PodSpecType",
        "value": "yaml"
      },
      {
        "key": "Privileged",
        "value": "true"
      }
    ]
  }'
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying <IP_ADDRESS>:443...
* TCP_NODELAY set
* Connected to gocd.development.example.com (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
*  start date: Nov  1 16:35:13 2022 GMT
*  expire date: Nov  1 16:35:13 2023 GMT
*  issuer: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55ff426c02f0)
> POST /go/api/elastic/profiles HTTP/2
> Host: gocd.development.example.com
> user-agent: curl/7.68.0
> accept: application/vnd.go.cd+json
> content-type: application/json
> content-length: 719
>
* We are completely uploaded and fine
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* The requested URL returned error: 422
* stopped the pause stream!
* Connection #0 to host gocd.development.example.com left intact
curl: (22) The requested URL returned error: 422```

I cannot replicate this, and the chart works fine OOTB with the chart-suggested plugin versions.
While I don't think there has been any change to MaxMemory validation (it's optional, and only relevant for non-YAML configuration anyway) - your plugin version is 3 years old and perhaps there is/was an API compatibility issue. Rather than dig further into the server and plugin logs etc - it's probably a more effective use of time to just validate the versions and use a more recent elastic agent plugin version at the very least.
If your GoCD version is 21.4.0 there should be no issue with using the latest version of the plugin from a compatibilit standpoint.


Add new members for libuv/zos

@libuv/collaborators I've been asked by @zsw007 if we can add @gabylb and @laijonathan, who both work with him at IBM, to @libuv/zos. While I have maintainer role for that team, I cannot add them to it as they are not members of the libuv organization.

They should have received invitations just now.

I can see they've now accepted and are in the team. Thank you.


chore(main): release audit 1.21.0

:robot: I have created a release beep boop
1.21.0 (2023-02-14)
Features

better license and meta issue titles (e118686)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-audit/releases/tag/audit-v1.21.0 :sunflower:


HADOOP-17925. BUILDING.txt should not encourage to activate docs profile on building binary artifacts.

https://issues.apache.org/jira/browse/HADOOP-17925
If -Pdocs is activated, hadoop-client depends on xerces. The dependency was added by HADOOP-14835 to fix jdiff error. We are avoiding unwanted dependency by building documentations alone in the second pass after building binary artifacts. The BUILDING.txt just should not encourage to activate -Pdocs on building binary artifacts.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m  9s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
27m 28s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shadedclient
20m 51s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

67m 39s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3509/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3509

Optional Tests
dupname asflicense codespell

uname
Linux a53eb31a50d3 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a10371c171281a005ab017eb4ed4bbb3a9a7bac1

Max. process+thread count
593 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3509/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


[BUG] Memory / RAM Spike

Which version of OB2 is this
What were you doing?
How many jobs?
How many bots?
How long has it been running for?
Do you have bot log enabled in the settings? It can cause high ram usage
Please provide a memory dump according to this issue https://github.com/openbullet/OpenBullet2/issues/149

the latest version 0.1.14
nothing
1
200
6 hours
nope
dont have one

it happns and i get this error:
fail: Microsoft.EntityFrameworkCore.Update[10000]
An exception occurred in the database while saving changes for context type 'OpenBullet2.ApplicationDbContext'.
System.InvalidOperationException: A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.
at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList1 entriesToSave, CancellationToken cancellationToken)          at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(DbContext _, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)          at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)       System.InvalidOperationException: A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.          at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()          at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(DbContext _, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
fail: Microsoft.EntityFrameworkCore.Update[10000]
An exception occurred in the database while saving changes for context type 'OpenBullet2.ApplicationDbContext'.
System.InvalidOperationException: A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.
at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList1 entriesToSave, CancellationToken cancellationToken)          at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(DbContext _, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)          at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)       System.InvalidOperationException: A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.          at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()          at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(DbContext _, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
fail: Microsoft.EntityFrameworkCore.Query[10100]
An exception occurred while iterating over the results of a query for context type 'OpenBullet2.ApplicationDbContext'.
System.InvalidOperationException: A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.
at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()
at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable1.Enumerator.MoveNext()       System.InvalidOperationException: A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.          at Microsoft.EntityFrameworkCore.Internal.ConcurrencyDetector.EnterCriticalSection()          at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable1.Enumerator.MoveNext()
warn: Microsoft.AspNetCore.Server.Kestrel[22]
As of "05/24/2021 14:27:17 +00:00", the heartbeat has been running for "00:00:12.3095509" which is longer than "00:00:01". This could be caused by thread pool starvation.
warn: Microsoft.AspNetCore.Server.Kestrel[22]
As of "05/24/2021 14:44:28 +00:00", the heartbeat has been running for "00:00:09.8339812" which is longer than "00:00:01". This could be caused by thread pool starvation.

Are you getting plenty of hits? Are you using a database hit output or a file system hit output?
Please, if you can, next time it happens make a dump of the memory and send it to me so I can inspect it, thanks.

Are you getting plenty of hits? Are you using a database hit output or a file system hit output?
Please, if you can, next time it happens make a dump of the memory and send it to me so I can inspect it, thanks.

yes im getting hits for sure, and i have it saving to the DB, i tried making a dump but file is too large or not accepted its a .DMP extension i made it from the task manager while it was freezing

Please disable the "bot logging" options as that heavily consumes RAM. It's supposed to be used just for testing that a config works, not to run it for long periods of time.

Please disable the "bot logging" options as that heavily consumes RAM. It's supposed to be used just for testing that a config works, not to run it for long periods of time.

ok thanks ! i disabled it, ill leave it running overnight see what happens

ok so disabled the log option been running for 10 hrs 200 bots, not consol errors


Bad inference after 70k step using faster_rcnn_resnet152_pets (model zoo)

Hello to every one, Am training a bird specie object detection. I have  6 (with 525 image, 75 pictures per class) classes and using:
software and libraire

tensorflow1.15
python3.6

model:

faster_rcnn_resnet152_pets.config

Laptop:

OMEN 15 which have RTX graphic card (6Go) on Ubuntu 18.04.

The level:
loss:1.4247278, step: 75185
The loss still decreasing but slowly.
I started the training since yesterday and I stopped the training and continued at this morning at the saved checkpoint as you can know.
But at this stage, I saved and export the model.*-7108 to test test prediction, but i did not get prediction and no boxes was drawn, only if I decrease the treshold from 0.6 to 0.1, i get some false and true prediction.
My question is: does that means my model was not learned very well? or should I continue the training until I reach 200k step.

An now still learning:


React : test for modernComponent

Is this test valid @pspeter3? Regarding : https://github.com/Asana/typed-react/commit/9008be2f41c56bdd975213a08c97f1847333b15d

Yeah, that's a great test for that. Thanks!


Configurable grid size

I would like to request a feature to make the size of the canvas configurable. This would be very useful for megabase design, as many such designs are chunk-oriented (32x32 or multiple thereof). I have found myself carefully laying down walls to indicate my boundaries, then having to delete them carefully by hand afterward.

I've been thinking that I should add this too but to make the size of the grid configurable I need to use the middle of the grid as the origin for all entity positions. Currently the origin is the upper left corner. This is quite simple in theory but having entities with negative x and y will have unexpected side effects and will break some logic.
Anyway, I'm just saying that I would like to add this but it will take time to test all the functionality of the editor with this new change.

@cajopa I've done some work on this and came to the conclusion that there is a much simpler solution.
What do you think about a chunk overlay that could be turned on and off from the settings?
Implementing a chunk overlay would be much easier than adding the logic necessary to make the editor shrink and expand based on a blueprint.
I will also make the editing area bigger - probably 1000x1000. The area itself doesn't have any performance impact, filling it with entities would ofc.

That sounds like an elegant solution - I'm a big fan of writing less code. You might have to implement some logic for placing blueprints along those chunk boundaries, though. Perhaps always place the top left at the corner of a chunk?

I think I will align the chunk grid so that the origin (0, 0) of the editor area is the mid point of a chunk. This way if you have a blueprint that is exactly 32x32 it will fit perfectly inside because the mid point of blueprints is also at (0, 0).

@cajopa I've implemented this. Let me know what you think!


Cannot exclude Query

Version: 11.8
We exclude the following query, but query still stand in report.
what we use is: --exclude-query "^(INSERT INTO ce_task_input)"
It is worth to mention that, Query bind size is approximately 72mb hex in bytea type of input_data column
Here is the actual query and log line:
2022-07-20 09:30:40 +03 [17399]: dbuser,db=dbname,app=PostgreSQL JDBC Driver,client=<IP_ADDRESS> LOG:  duration: 942.503 ms  bind : INSERT INTO ce_task_input (task_uuid, created_at, updated_at, input_data) VALUES ($1, $2, $3, $4)
2022-07-20 09:30:40 +03 [17399]: user=usonarcube,db=pguyap,app=PostgreSQL JDBC Driver,client=<IP_ADDRESS> DETAIL:  parameters: $1 = 'AXIbTRJ9Lf3qZSmclwfE', $2 = '1758298634800', $3 = '1758298634800', $4 = '\x504b0304140008080800cf33f454000000000000 ......................... (up to 72MB long bytes, one line)
The table definition is:
CREATE TABLE ce_task_input (
task_uuid varchar(40) NOT NULL,
input_data bytea NULL,
created_at int8 NOT NULL,
updated_at int8 NOT NULL,
CONSTRAINT pk_ce_task_input PRIMARY KEY (task_uuid)
);

Commit e4da5f2 might fix this issue.

Thanks.
Yes, fixed.


CPU Basic doesn't have data in Node Exporter Full dashboard

variable got remove or it's value reset, go to dashboards, node exporter full, click settings icon on top, go to variables, create/set job to

it's definition in upstream node exporter full is valid checking their master and the commit id/revision tele pulls from https://github.com/rfmoz/grafana-dashboards/blob/5fcf5a2cd30dd7cdb9886d386e6ac3fe1c418864/prometheus/node-exporter-full.json
not sure what I did to reset/remove it, but it was working initially, then stopped working, now I fixed


[Caloris2] [Github Code] Add configuration flag on Github connectors to enable code syncing

As a started visible from poke only
See https://github.com/dust-tt/dust/issues/2324

This one is done


Bug on Vue3.0.4.

Description of the bug
I have installed package and tested with example in the docs, but I always get this error:

Can you try updating to<EMAIL_ADDRESS>and see if that solves your problem?

@valgeirb thank you, it does solve the problem. Is there any other way around with not updating?

No I don't think so, I think this error is because Popper uses v-bind in CSS that was introduced in<EMAIL_ADDRESS>- you should be able to upgrade your Vue dependency without any problems though.


signin form can not get email and password

i am follow this lesson. i now studying client package, when i create signin form  but signin button press, in handleFormSubmit function email and password alway undefine.
Could you help me!!

+1
I have gone over the code time and time again, and cannot see any difference between files.
import React, {Component} from 'react';
import {reduxForm} from 'redux-form';
class SignIn extends Component {
handleFormSubmit({email, password}) {
    console.log(email, password);
}

render() {

    const { handleSubmit, fields: {email, password}} = this.props;

    return (
        <form onSubmit={handleSubmit(this.handleFormSubmit.bind(this))}>
            <fieldset className="form-group">
                Email:
                <input {...email} className="form-control" />
            </fieldset>
            <fieldset className="form-group">
                Password:
                <input {...password} type="password" className="form-control" />
            </fieldset>
            <button action="submit" className="btn btn-primary">Sign in</button>
        </form>
    );
}

}
export default reduxForm({
form: 'signin',
fields: ['email', 'password']
})(SignIn);

@ttson24 I believe this is due to changes in redux-form
if you downgrade redux-form to use version ^5.3.3 (delete node modules and npm install again) then you should get the values as expected.
i ran into the same issues then remembered there is an updated version of react router in the previous course Stephen uploaded `Moden React with Redux
hope this helps

+1 for the downgrade to<EMAIL_ADDRESS>works.

thank a lot, i ran.!!!


implemented in tensorflow

Hello! I wanna apply the OLE loss in tensorflow. Do you have a plan to develop tensorflow version of  implementation? Thanks!

Hello and thanks a lot for your interest.
We would love to see a tensorflow version but we are not working on it yet.
However the currently available implementation is basically Numpy so it should be easy to adapt (direct link).


Stripping the trailing backslashes off the current path in IonTabs.svelte

There's been an issue with the tab bar navigation for a while, where if the current url is for example pages/homepage/, with homepage being a tab page, navigating through the tabbar to a new page eg. pages/notifications would lead to a 404 error after navigating to pages/homepage/notifications instead.
Noticed in the code that during the splitting of the current path, a trailing backslash would lead to the current tab variable having an empty string, instead of, in this case containing the actual current tab which should've been homepage.
The workaround proposed here is to use regex which matches trailing backslashes (one or more) and removes them, before continuing with the rest of the path splitting process.

Accepted - thanks!


generate_wrappers.sh has hardcoded singularity path

generate_wrappers has /usr/bin/singularity
could it be just "singularity"?
I have installed singularity as module.

Hi,
Yes that could be fixed, there is a PR for that in #17. I'm going to have a look at that that there are not unexpected issues w.r.t infinite loops or similar.
Could you say how dynamic it would need to be?

Set when running wrapper generation -> changing singularity in $PATH after creating a python/conda installation has no effect
Fully dynamic -> singularity used from $PATH every time you launch a wrapper?

Hi,
thx for commenting.
I think fully dynamic might be ideal. However, for my use case the 1st option would probably be enough.

Hi,
This has now been fixed by #20. I just merged that so master and tag v0.3.2 now contains the fixes.
Let me know if it does not work as expected. Ran trough basics test on our systems, and seemed to be ok.
There is now an extra option in the global config.  singularity_executable_path
You can set this to whatever valid path or command name which will be used for invoking singularity / apptainer during build and startup:
singularity_executable_path: '/usr/bin/singularity' -> same as old behavior
singularity_executable_path: '/my/custom/path/to/singularity'
singularity_executable_path: 'singularity' we will pull just whatever is in $PATH at the time, the wrappers will also select singularity just from $PATH
singularity_executable_path: '$MY_CUSTOM_SINGULARITY' -> evaluated at runtime so the content of the variable would be hardcoded to the generated wrappers.
We do some basic sanity checks for the set value, and error and exit early if we notice:

The command does not exist
The command does not look like a valid apptainer/singularity command -> e.g <command> --help does not contain exec/shell/pull.


Inference not generating unique samples

I'm testing the inference notebook with the provided pre-trained models, but I'm not sure what the output of the generator script is supposed to be.
When running the extract melody generator it proceeds to convert the entire POP1k7 dataset (midi files). I canceled this and reduced the number of midi files in Dataset. It writes files to the output folder, but the melody is the exact same as the original midi file. Even after changing the temperature and other settings it writes the same melody.
How is the generator supposed to work? Or did I miss something?

@audiomax-ai Thanks for your question and feedback...
POP Melody Transformer is for melody arrangement/detection. It does not generate any music. It only labels notes in the provided midi files as melody notes or as an accompaniment notes. It is basically a melody notes classifier.
If you want to generate music and if you want something simple to get going and play around with, I would suggest to check out my latest model/implementation as it is based on POP Melody Transformer:
https://github.com/asigalov61/Tiny-Music-Transformer
This is a very simple and small music transformer that uses priming from the training dataset to generate very nice output. You can run it and train it in Google Colab in less than 10 hours on any of their GPUs.
Check it out. The generator code/colab is already up there and I will add the training code very shortly.
Otherwise, I would also recommend to check out Allegro Music Transformer. It is also a pretty simple and efficient implementation that works good as a tutorial.
https://github.com/asigalov61/Allegro-Music-Transformer
Hope this answers your questions.
Alex


Latest release isn't on NPM.

GitHub Releases has 0.12.7
NPM only has 0.12.6

Just updated to 0.13.0! 🎉


parse file contents using token parser

TokenParser is very similar to DelimitedDataParser, but it has to be able to cope with input that crosses 'handleData' invocations. This means we can avoid having growable buffers, so long as we can guess how long a line is allowed to be for a given input (which we can do for everything, right now, I think).
I've deliberately left the implementation in a fully inlined state - there is some repetition in there that could be cleverly factored out. That 'cleverly' word put me off though.
There probably aren't enough test cases for TokenParser, and I probably missed some finals somewhere (but I added some others elsewhere).
I removed some extraneous detail from DelimitedDataParser in addition.

I don't think this is required any more, as FileLoader.load() will read a file in its entirety.


Pul Request

Institution/School Name
EE Plinio Barreto
Instiution/School Website
{Website URL}
Email Users
Please place an x between the square brackets if yes

[ X] Students
[ X] Academic/Teaching Staff
[ ] Other/Support Staff
[ ] Alumni

Education Levels
Please place an x between the square brackets if yes

[ ] Post-graduate research
[ ] Graduate School
[ ] College (University) or Undergraduate School or equivalent
[ ] Community College or equivalent
[X ] High School or equivalent
[ ] Elementary School or equivalent

@uJ0hn First stage of verification passed, official domain is facebook.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.facebook.com/eepadreafonsopaschotte/photos/a.1553874981530258/2542295379354875/?type=3

@uJ0hn Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

You can provide us with any of the following as the proof:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

@uJ0hn You might miss my previous comment. Please react.

@uJ0hn I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Android app release fails to install on some devices

Environment
React Native Environment Info:
System:
OS: Linux 4.15 Linux Mint 19.1 (Tessa)
CPU: (4) x64 Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz
Memory: 3.39 GB / 7.66 GB
Shell: 4.4.19 - /bin/bash
Binaries:
Node: 10.15.0 - ~/Documents/nodejs/bin/node
npm: 6.7.0 - ~/Documents/nodejs/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 23, 24, 25, 26, 27, 28
Build Tools: 27.0.3, 28.0.2, 28.0.3
System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-24 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom_64, android-27 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.58.3 => 0.58.3
npmGlobalPackages:
apsl-react-native-button: 3.1.1
react-native-button-component: 0.2.28
react-native-cli: 2.0.1
react-native-elements: 0.19.1
react-native-vector-icons: 6.1.0
Description
When I release my app and trying to install it on my Samsung Galaxy S5 active running Android Marshmallow version 6.0.1, the installation fails.
Some of my beta testers also experienced the same on Android 6 and Android 7.
However, the app installs and runs successfully on my Infinix Hot 5 running Android 7.
And it also works when I install and run it on an Android emulator running Android 6.
So I'm kind of confused.
Here's my package.json file

{
  "name": "iVoc",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "axios": "^0.18.0",
    "eslint-plugin-react-native": "^3.6.0",
    "native-base": "^2.10.0",
    "react": "16.6.3",
    "react-native": "0.57.8",
    "react-native-elements": "1.0.0",
    "react-native-firebase": "^5.2.0",
    "react-native-gesture-handler": "^1.0.12",
    "react-native-indicators": "^0.13.0",
    "react-native-loading-spinner-overlay": "^1.0.1",
    "react-native-paper": "^2.4.0",
    "react-native-popup-menu": "^0.14.2",
    "react-native-vector-icons": "^6.1.0",
    "react-navigation": "^3.0.9",
    "react-navigation-material-bottom-tabs": "^1.0.0",
    "react-redux": "^6.0.0",
    "realm": "^2.22.0",
    "redux": "^4.0.1"
  },
  "devDependencies": {
  },
  "jest": {
    "preset": "react-native"
  }
}

Reproducible Demo
I just have to open Android Studio, generate the signed apk and install it on my phone running Android 6.0.1 for the installation to fail.

What is the output when you run adb install <your_apk> on that device? It sometimes contains more information.

@bartolkaruza indeed it contains more information.
So I found this error Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES] that is caused because I only signed my apk with version 2 signature.
All I had to do was to tick also the version 1 signature to support older devices.
Thank you @bartolkaruza ;)

you should re-sign your apk by using the keystore which with timestamp


Linting libraries phase 1

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

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

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?
[x] Yes - updated typescript, I don't actually know if it's breaking anything
[ ] No

Other information

I had to update typescript to 3.3.4000 in order to fix a fatal error when running linting

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

I updated the workflow to run linting on the libraries as this is an on going effort #401, the rest will come later

I tried to keep refactoring to a minimum, but some times the linting rules required a refactor - or my sanity 😉

In some places I just gave up and added ignore comments 😭

Just noticed the CI is silently failing :(

(node:2968) UnhandledPromiseRejectionWarning: Error: Nx failed to execute runtimeCacheInputs defined in nx.json failed:
Command failed: type .eslintrc
at Hasher. (/home/runner/work/akita/akita/node_modules/@nrwl/workspace/src/tasks-runner/hasher.js:59:27)
at Generator.throw ()
at rejected (/home/runner/work/akita/akita/node_modules/@nrwl/workspace/src/tasks-runner/hasher.js:6:65)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:2968) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)
(node:2968) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@NetanelBasal any idea why the CI stopped running on this PR?

No


[bug] Display issues on smartphones of healthchheck results table

cc @jmgiaever

Hi, thanks for the fix @robertsLando and to report the issue for me @AlCalzone :))


feat: add migration mode option to Install-EsxiCertificate

cmdlet Install-EsxiCertificate add "EnsureAccessibility" options add cmdlet "Get-EsxiHostVsanMaintenanceModePrecheck"

cmdlet Install-EsxiCertificate add "EnsureAccessibility" options
add cmdlet "Get-EsxiHostVsanMaintenanceModePrecheck"

Type

[x] Bugfix
[x] Enhancement or Feature
[ ] Code Style or Formatting
[x] Documentation
[ ] Refactoring
[ ] Chore
[ ] Other
Please describe:

Breaking Changes?

[x] Yes, there are breaking changes.
[ ] No, there are no breaking changes.

Test and Documentation

[x] Tests have been completed.
[x] Documentation has been added or updated.

Issue References

Closes #32
Closes #100
Additional Information

@garlicNova The Install-VCFCertificate cmdlet is the one which is exposed to the user.
Hence for the user to use the changes made for Install-EsxiCertificate for ensureAccesibility, we must allow configuration of the parameters from Install-VCFCertificate. Could you please make that change.

Passing to @bhumitra for next review.

Thanks! I'll rebase and merge.


Divs overlapping or with Positive Z - index are not rendering correctly in html2Canvas

I have 2 divs over lapping each other with different background font and colors. When I converted the html2image the parent div content is also getting visible with the child div content and content is getting over lapped. Tried with Z-index but no luck. How to handle the Div over div cases in html2canvas.

I wan the red content which is parent div to be covered by the green content.

Hi @sudheer524, I believe overlapping divs should normally be handled correctly. I'd recommend you post a jsFiddle with example code that illustrates the problem - the jsFiddle link I've included has the current version of html2canvas already attached as an external resource.

Hi @eKoopmans
Here is my Js Fiddle linek.
https://jsfiddle.net/69kc2t2y/15/
When clicked on to Image check there is overlapping issue for html content and image generated.

Hi @eKoopmans
Intially I used addhtml to download the image to pdf. I have changed my code to use your html2pdf and added z-index to my child div. It got worked.
Thanks a lot :)

Great, you're welcome! Yeah on your initial problem it looks like z-index was all you needed. Sorry I couldn't help earlier, it's been a busy few days.
P.S. Looks like your problem is resolved, if it is then don't forget to close it.


Update Readme 061322

Some minor copy-edits to the readme file.

This looks good to me, thanks for catching all of the typos, punctuation and grammatical issues!


Test: Fix Unit tests for BLE MQTT

Fix Unit tests for BLE MQTT
Description
Fix Unit tests for BLE MQTT
Checklist:

[ X ] I have tested my changes. No regression in existing tests.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run unit-tests

/bot run unit-tests

/bot run unit-tests


Fixed snake game

Fixed the snake game and added the home button to the left top.
PR Description 📜
I have fixed the snake game. The snake is visible now and game is working. I also aligned the home button to top left and made hiscore to HighScore.
Fixes #3118

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.

Add your screenshots(Optional) 📸

Thank you @sakshii00 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @sakshii00 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀

Hey @sakshii00,
You can't work on a closed issue 👀!
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Could you please assign this PR to me? @kunjgit

@kunjgit Sorry to trouble you again but please assign this PR to me. Thank you!


State becoming unavailable and won't recover until Home Assistant is restarted

Hi,
I have the issue that at some time (after few days) the states of the integration become "unavailable" and won't recover until I restart Home Assistant.
I don't see anything in HA logs, but I also don't have the debug log of this integration enabled. I have used same e-mail address as the Zonneplan app on my phone uses, could that be a problem?
I will enable the debug logging and let you know when it happens again

The issue started this morning again. Now having some logging. Seems that at some point the service returns 503 Service Unavailable and then the integration does not recover from that:
2022-03-18 10:16:55 INFO (MainThread) [custom_components.zonneplan_one.coordinator] _async_update_data: start
2022-03-18 10:16:55 DEBUG (MainThread) [custom_components.zonneplan_one.api] ZonneplanAPI response header: <CIMultiDictProxy('Date': 'Fri, 18 Mar 2022 09:16:55 GMT', 'Server': 'Apache', 'Content-Length': '299', 'Connection': 'close', 'Content-Type': 'text/html; charset=iso-8859-1')>
2022-03-18 10:16:55 DEBUG (MainThread) [custom_components.zonneplan_one.api] ZonneplanAPI response status: 503
2022-03-18 10:16:55 ERROR (MainThread) [custom_components.zonneplan_one.coordinator] Authentication failed while fetching zonneplan_one data: 503, message='Service Unavailable', url=URL('https://app-api.zonneplan.nl/user-accounts/me')
2022-03-18 10:16:55 DEBUG (MainThread) [custom_components.zonneplan_one.coordinator] Finished fetching zonneplan_one data in 0.346 seconds (success: False)
2022-03-18 10:16:55 INFO (MainThread) [custom_components.zonneplan_one.config_flow] __init__
2022-03-18 10:16:55 DEBUG (MainThread) [custom_components.zonneplan_one.config_flow] reauth {'auth_implementation': 'zonneplan_one', 'token': {'token_type': 'Bearer', 'expires_in': 28800, 'access_token': '**REDACTED**', 'refresh_token': '**REDACTED**', 'expires_at':<PHONE_NUMBER>.465228}, 'email': '**REDACTED**'}

After this happens, the zonneplan_one component doesn't log anything anymore (it happened almost 4 hours ago).

Tagging you @fsaris :)

don't you get an notification to re-authenticate the app in this case? With version 0.0.10 this should be improved

Can you test version 0.0.10 to see if it's still happens?

I’ve just installed it via HACS, let’s see how it goes! 👏


Service now tasks

These are to create RITMS in service now via API as a post provisioning task

These tasks can be used to update an existing RIEM or create a new RITM upon provisioning or day 2 like reconfigure


Solve www redirect issue

When request is redirected with 301, the request become GET.

Turned off redirect from domain.ltd to www.domain.ltd and solves this issue.


fixing css issues

Candidate transactions:

Voter transactions:

Pull Request Test Coverage Report for Build 329

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.47%

Totals

Change from base Build 327:
0.0%

Covered Lines:
92

Relevant Lines:
103

💛  - Coveralls

Yeah, np, can you check it for me

Not sure, I think the ID collumn is useless here because it doesn't represent anything (click on page 2, it will still be ID 1 to 10). But we can keep it I guess.
But I see you made the opposite of what I thought, you made the spacing between row the same as the spacing between "masternode" and "vote" instead of the opposite, can you change that? I think it takes too much space.

Yep, vote for removing id column

@pqv199x did you fixed the spacing on the status and vote button?

I think we remove ID column in homepage, candidate detail, and replace withNumber column, Number will grow up from 1 to n. It is just for count

@khaihkd I agree, the ID collumn is actually always useless and give no usefull informations. I think it could be good to remove it everywhere.
I don't think a Number column would be usefull tho. it will just 1-10 all the time :/

Also the ID on the Candidate list could be named "Rank" instead and be tied to their rank

merged it, for fixing the space, do in another PR


Provision of Microsoft 365 learning pathways template failed

I tried to provision the Microsoft 365 Learning Pathways template to my Office 365 Tenant but I received an email saying that it failed.
PnP Correlation ID: 345eed21-814c-4965-be5f-df4f98ef006c

Hi, Thanks for your feedback. I'm closing this item because it is now outdated.


⚠ Jenkins Plugins Artifactory has degraded performance

In 42f7ec8, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1384 ms

Resolved: Jenkins Plugins Artifactory performance has improved in f7db3ac after 12 minutes.


New cop Rails/DelegateAllowBlank

Adds a new cop to catch usage of allow_blank as an option to ActiveSupport's delegate method. allow_blank is not a supported option and fails silently. The correct option is allow_nil. Other parts of Rails have allow_blank as an option, such as some validations.
Please let me know if there are more idiomatic ways to do this, especially using def_node_matcher.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.

Mmm, I think this is out of scope, wouldn't it be better if ActiveSupport detected invalid usage?

The same argument could be made for all of the Rails cops, no?

Most of Rails cops choose a preferred style over a few valid, non-deprecated styles. In this case, it would be detecting invalid usage. But I guess if this is a very common mistake, then it's fine. Maybe I just don't like it because I've never run into this confusion.

I think that https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/rails/not_null_column.rb and https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/rails/save_bang.rb are kind of similar

Rails/NotNullColumn is definitely similar. Not my cup of tea, but if the other one was accepted by the mantainers, maybe this will be accepted as well :)

I think that https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/rails/not_null_column.rb and https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/rails/save_bang.rb are kind of similar

I agree with this. The question is, however, how common is the mistake this cop is aiming to prevent. We can't really have cops for every method that accepts arguments via a hash.

The idea behind the allow_nil delegate option is to delegate via try so delegations on nil objects don't raise but just return nil.
The idea behind the allow_blank option in rails validators is to consider blank objects as valid, regardless of the validator's result.
Apparently some people mistakenly use allow_blank for Rails delegate, but I don't know how common that is.

@connorjacobsen ping :-)

@bbatsov What are your thoughts?

I was wondering how common do you think this problem is in the wild?

Honestly, I'm not sure. Any guesstimate I made would just being pulling numbers out of thin air.

Well, OK. Rebase this PR and update the changelog for the current version and let's have this merged. Hopefully it will be useful.

@bbatsov Changes made, ready for another pass.

@connorjacobsen The build is failing.

Sorry about that. Fixed.