(BKR-376) better interface to install puppet-agent through install_pe

- standardize on parameter names puppet_agent_version, puppet_agent_sha
- if no puppet_agent_sha is provided default to puppet_agent_version
- support new env vars
  * BEAKER_PUPPET_AGENT_VERSION
  * BEAKER_PUPPET_AGENT_SHA
  * BEAKER_PUPPET_COLLECTION

- examples (puppet-agent installation):
  install_puppet_agent_on(host, { :version => '1.1.0', :default_action => 'gem_install'})
  install_puppet_agent_dev_repo_on(host, { :puppet_agent_sha => 'd3377feaeac173aada3a2c2cedd141eb610960a7', :puppet_agent_version => '<IP_ADDRESS>.    377fe'  })
  install_puppet_agent_pe_promoted_repo_on(host, { :puppet_agent_sha => '<IP_ADDRESS>', :puppet_agent_version => '<IP_ADDRESS>.g1d8334c', :pe_ver => '    .0-rc1'})

- using install_pe/install_pe_on (for versions of PE > 4.0)
set the puppet-agent version through an env var:
  export BEAKER_PUPPET_AGENT_VERSION=1.2.0
can then just call:
  install_pe or install_pe_on(hosts, options)

set the puppet-agent version through the options hash
  options[:puppet_agent_version] = '1.2.0'
  install_pe

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1055/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1054/
Test PASSed.

@anodelman your description doesn't include a sample usage of what changed in the install_pe_on method, which from the title (and ticket) I assume this PR is addressing. Could you explain how this patch actually makes the PE interface easier?

AFAICT, changing line 418 in pe_utils.rb to this:
install_puppet_agent_pe_promoted_repo_on(host, { :version => opts[:puppet_agent_version],
                                                 :sha => opts[:puppet_agent_sha],
                                                 :pe_ver => opts[:pe_ver],
                                                 :puppet_collection => opts[:puppet_collection] })

Would have the same outward facing interface change to install_pe_on. I'm not sure why changing the interface to install_pe_on necessitates changing the interface to the other methods. ie. Why should the options hash to install_puppet_agent_on be the same as the options hash to install_pe_on?

I don't think that the parameters to the install_puppet_agent* methods were well chosen in the first place - so I'm trying to make the code more readable and understandable as a ride along to this.  I think that it is poor form to have some methods understand pe_ver and some understand version and some use version to mean both agent and puppet version and some to use both pe version and agent version (and on and on).  I'm aiming for clarity at what 'version' in each case means.

I disagree with you (I think that version in a method called install_puppet_agent naturally is the version of puppet-agent and that coupling the options hash for every install helper is fragile). But we always think the code we write is more understandable than it probably is and I'm happy to defer to a larger consensus. Do you have a preference, @kevpl ?

while in general I agree with @justinstoller that if a method name makes a parameter name obvious, then it shouldn't be duplicated in the parameter name, in this situation, I agree with @anodelman.  My reasons:

these files are changing rapidly since we're trying to keep up/stay ahead of development & testing
with the modularization effort, things are only going to get more confusing until we fully separate these utils out into their own constructs

Due to these, I think that the less state implied by context, the better.  I know that the short-term solution becomes the long-term solution, and I think over-specifying is an alright thing to live longer than intended.

My concern with these changes is that I think we're making people pass in an explicit variable when there is a reasonable default for one of these values: latest.  I don't believe we have code to put latest into the PM URL as described by @haus in BKR-341.  I'm not able to find it, anyways, so if we have it, please point that out to me.
To be honest, I didn't remember latest until @jpartlow brought it up:
[11:02 AM] Joshua Partlow: If 'latest' is implicit then I think we're okay;
I don't think it's tenable for the test to need to determine the latest
puppet-agent version associated with the current PE version.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1060/
Test PASSed.

Unfortunately, 'latest' doesn't work without additional info:
http://agent-downloads.delivery.puppetlabs.net/4.0/puppet-agent-latest/repos/el/7/PC1/x86_64/puppet-agent-1.2.1-1.el7.x86_64.rpm

You can see that it still have the version number in the rpm name - something that I can't discover.

since this is the case, I'm :+1: in general on this.
Let me know when you've gotten stake holders to a consensus, and if it's still this, I'll merge it.

Let's hold on this till the questions about the 'latest' file get resolved.

Actually, let's merge this and follow up in https://tickets.puppetlabs.com/browse/BKR-377.

I doubt anyone's waiting on me, but FWIW, I'm a :+1: after further discussion.


How to configure swagger using springfox having cxf jaxrs and spring mvc endpoints

I am working on application having cxf jaxrs and spring mvc endpoints.
I need to configure swagger for both the cxf jaxrs and spring mvc endpoints in a single application.
Is it possible to configure swagger using springfox for above application.

CXF isnt supported


Bump dependencies including lodash v4

I'd like to go through and update all the ampersand modules to use lodash v4. Is there a recommended order? Lots of modules seem to depend on other modules.

@cdaringe @wraithgar can you take a look and recommend next steps? I'd like to get everything to lodash v4 asap.

tests pass locally. +1

@samhashemi, no rigid next steps. when the PRs are ready and the deps g2g, ping us and we'll get 'em published.  unifying the lodash dep is simple enough :)

+1

Thanks for merging @pgilad. Can you also bump the npm version?

@AmpersandJS/core-team I pushed version 2.0.0 (https://github.com/AmpersandJS/ampersand-app/commit/40378666843d202b6f0881e042ddd4bfe02da106) but can't publish it to npm. Can anyone take care of that?

I think I have npm permissions for this package- let me try.
Thanks @samhashemi for the work and @pgilad for merging!

Well, looks like I was mistaken and don't have npm perms here.
Side note: I get the warning below when running npm install.  Should it be phantomjs-prebuilt instead of phantomjs?
npm WARN deprecated<EMAIL_ADDRESS>Package renamed to phantomjs-prebuilt. Please update 'phantomjs' package references to 'phantomjs-prebuilt'

@fyockm @pgilad I added you both to npm for this project. Ping me if you find any others that you need.

Published - thanks @lukekarrys!

Also, I'm going to go through the rest of the modules and try to get major versions of everything lodash4 related published today.

@lukekarrys thanks! appreciate the help!

So I think I got to everything yesterday (except for ampersand-view which should get done today, see https://github.com/AmpersandJS/ampersand-view/issues/176). Hopefully we are all Lodash 4-ified now! @samhashemi thanks for all your hard work in this. Let me know if anything is missing.


page rendering in order w/ css + text

Placeholders for each section w/ page rendering.

Merging as part of initial setup


Convert to Tailwind css

📝Changed routes:

/about
/blog

(view full size)
(view full size)

/books

(view full size)

2 deleted routes:

/about.module
/blog.module

Commit 322efbcbfab44a96270234ed43b734db081da6d4 (https://samuelkraft-next-6o7wg59rl.vercel.app).


go vet is failing

go vet is failing with the current code
$ go vet
src/github.com/GoogleCloudPlatform/k8s-multicluster-ingress/app/kubemci/cmd/create.go:204: wrong number of args for format in Errorf call: 1 needed but 2 args
src/github.com/GoogleCloudPlatform/k8s-multicluster-ingress/app/kubemci/cmd/delete.go:156: wrong number of args for format in Errorf call: 1 needed but 2 args
exit status 1
src/github.com/GoogleCloudPlatform/k8s-multicluster-ingress/app/kubemci/pkg/gcp/backendservice/backendservicesyncer_test.go:99: missing argument for Errorf("%v"): format reads arg 2, have only 1 args
src/github.com/GoogleCloudPlatform/k8s-multicluster-ingress/app/kubemci/pkg/gcp/backendservice/backendservicesyncer_test.go:119: arg port for printf verb %s of wrong type: int64
exit status 1
src/github.com/GoogleCloudPlatform/k8s-multicluster-ingress/app/kubemci/pkg/gcp/utils/utils.go:59: missing argument for Errorf("%s"): format reads arg 1, have only 0 args
exit status 1

Is there a way to automatically run "go vet"?

Now that we have the Makefile (https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/pull/62), you can run make vet.
Once we fix the issues listed here, I will run it as part of our automated tests so that PRs will be blocked if it fails.


model.pkl for SI_LULC_

Hi,
Due to memory constraints i am unable to train and produce model.pkl file from SI_LULC...ipynb code for land cover. Can you provide the model.pkl file for 2019 trained dataset. It would be great to run predictictions on that .  Please let me know on this.
Thanks,
Visa

I already responded and attached the model here. Closing


Can safeDump output double quotes?

Greetings,
Is it possible to convert the JS below to the YAML below?
JS:
{ apostrophes: "It's didn't there's" }

YAML:
apostrophes: "It's didn't there's"

In the YAML, I want to wrap the string in double quotes. The string will contain single quotes (apostrophes).
Thanks very much,
Kris

Any chance there is an answer?

Duplicate of #290.
Fixed by https://github.com/nodeca/js-yaml/commit/7b256d7612a4c29cdf5dfd48a15e01c8dbbb5291 in dev branch, gonna be released later.


✨Activate versions feature

Purpose
We fixed the 404 error when trying to access the version feature, so we reactivated the version feature in the doc header.

Duplicate of: https://github.com/numerique-gouv/impress/pull/277


Label support all Unicode?

Looks like label only support latin character(ABCabc...) now, which make it harder to build apps for different language. Support for all Unicode?

If I understand correctly, it depends on the font you are using. You can generate font atlas using msdf-bmfont package from ttf font.
msdf-bmfont --reuse  -i charset.txt -m 512,512 -f json -o arial.ttf.png -s 32 -r 8 -p 1 -t msdf arial.ttf
Connect your font with help next api call:
globe.renderer.fontAtlas.loadFont("arial", '../../fonts/', 'arial.json');

@Zemledelec, please, add if i missed something. Where is npm run font command from package.json?

There is a post I ve made https://levelup.gitconnected.com/msdf-font-rendering-in-webgl-91ce192d2bec. Here you can find how to make unicode glyphs. But be sure that there is only one atlas image, because globus supports only one atlas image now.
As @pavletto said: Here is a charset.txt, try to add a few unicode letters here. Also you can enlarge atlas image size to 1024 or more.
msdf-bmfont.cmd — reuse -i .\charset.txt -m 512,512 -f json -o %1.png -s 32 -r 8 -p 1 -t msdf %1

@yeluoyunfei Close?

@Zemledelec . Thanks for remind, I have not got a chance to check it yet. will check it soon


Improve documentation publish strategy

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1774
Originally created by @mbergeron on 2020-02-21 13:44:06

The number of components in the Meltano distribution is growing, and I think it would be good to take some time to think about a proper deployment strategy.
Components:

meltano PyPI package (A)

Meltano UI
Meltano API
Meltano OAuth Service

meltano Docker Image (A)
http://meltano.com/docs documentation (B)
http://meltano.com/discovery.yml (B)

A
These components are published whenever are tag is pushed on the meltano/meltano repository.
B
These components are up-to-date with the latest master.
The documentation
The main issue is that we currently have deployment strategies (A, B), that are not in sync. Thus, when we do documentation changes, there might be a window where it doesn't match the current published application, as B > A.
Solutions
I think the solution is to synchronize A & B, such as documentation is published at the same time the application is published. We would have to do some CI magic to enable "hotfixes" on the documentation without publishing a new version, with a special [pub-docs] or a manual job/variable.
@DouweM I'll assign this to you to ponder on the idea.

View 1 previous comment from the original issue on GitLab


load data local infile callback not fired

I've encountered a problem lately with LOAD LOCAL DATA INFILE
The functionality works, and rows are added fine to MySQL, but the callback never gets called, and the code hangs. This doesn't seem to always reproduce, but rather "comes and goes", mostly based on the dataset.
A wireshark trace shows that MySQL responds with an OK packet after the LOAD command most times,but sometimes okpacket is not  send, it's hard to reproduce,so i can't know why.

Hi @chacent I'm sorry you're having this issue. I can try to poke at it / stare down the source code to see if I can determine anything, but cannot make any promises without some kind of way to reproduce the issue.

big dataset,and mutil time can repeat the problem

https://github.com/mysqljs/mysql/issues/593#issue-19607038,
same problem

Hi, I'm not saying there is not an issue here, just that it is going to be difficult to figure out without a reproduction case. I will try to look into it as soon as I can, but just without a reproduction case I can't even know I'll be able to reproduce it because there are so many variables involved.

i think this's protocol issue,may some case that okpacket not must?

can i speak chinese?

From my understanding of the protocol ad documented by Oracle (https://dev.mysql.com/doc/internals/en/com-query-response.html#packet-COM_QUERY_Response) the path for INFILE will always end by the server sending back either an OK packet or an ERROR packet after the client sends the empty packet (and the data has completed insert operations).
You can write Chinese here, but since I don't understand it, I will need to run it through a translator, which may or may not do it justice.

问题是这样的，我从sqlserver数据库转换到mysql数据库，每个数据表单独传输（每个表数据都非常大），我重载了_sendLocalDataFile的实现，因为你们的代码会耗尽内存（没有使用流机制）。当传输结束时，我手动发送了EmptyPacket。this.emit('packet', new Packets.EmptyPacket());服务器已经接受了这批数据，但是callback没有被调用，我抓包尝试，但是不能容易的截取到这种问题。我只抓到了一次，但没有保存。我开启了调试，每次调试都没有收到okpacket，并且抓包也确实没有收到okpacket，但我还不确定是不是这样。目前我认为代码本身没有问题，问题出在是不是一定会有okpacket上，我还没有足够的精力来做大量的测试，我怀疑用同一批数据多次调用也可以重现这个bug,我会尽量抽时间来确定这个事情

--> (270) ComQueryPacket
ComQueryPacket {
command: 3,
sql: 'load data local infile '' replace into table t_well fields terminated by ',' enclosed by '\'' escaped by '\\' lines terminated by '\n' (str_id,str_course,date_confirm)' }
<-- (270) ResultSetHeaderPacket
ResultSetHeaderPacket { fieldCount: null, extra: undefined }
........
--> (270) EmptyPacket
EmptyPacket {}
now hangs

Hi @chacent I haven't been able to reproduce so far, so I have no idea what else to tell you. As I linked above, the point at which you are hanging is when the server needs to send back the file path for this module to send the contents of. There really doesn't seem like there is an issue with this module, right? I also haven't been able to get the driver to hang as you show, which makes it pretty much not possible for me to progress further.

I'm going to close this since there hasn't been any follow up with a reproduction case for me to debug.

@dougwilson is it possible to add some usage documentation for LOAD DATA? Is the usage similar to any regular MySQL statement?


fix: capture redirected requests in waterfall

fix #175
Redirected requests have the same requestId which was overriding the original request with the redirected request. As a result the redirected requests was simply not shown in the waterfall.
The solution is to check if the request is issued with the same requestId and simply mimic the usual flow from requestSent -> responseReceived -> LoadingFinished by using the redirected response which is available as part of the event.redirectedResponse data.

Check the below events for a sample website which goes from HTTP -> HTTPS and how 301 works.
{"type":"journey/network_info","@timestamp":1609895099415610.8,"journey":{"name":"check that title is present","id":"check that title is present"},"step":{"name":"go to app","index":1},"payload":{"step":{"name":"go to app","index":1},"timestamp":1609895099415610.8,"url":"http://vigneshh.in/","request":{"url":"http://vigneshh.in/","method":"GET","headers":{"upgrade_insecure_requests":"1","user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.0 Safari/537.36","host":"vigneshh.in","connection":"keep-alive","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9","accept_encoding":"gzip, deflate","accept_language":"en-GB,en;q=0.9"},"mixed_content_type":"none","initial_priority":"VeryHigh","referrer_policy":"strict-origin-when-cross-origin"},"type":"Document","method":"GET","request_sent_time":1012040.277427,"is_navigation_request":true,"status":301,"load_end_time":1012040.365573,"response_received_time":1012040.365573,"response":{"url":"http://vigneshh.in/","status":301,"status_text":"Moved Permanently","headers":{"date":"Wed, 06 Jan 2021 01:04:59 GMT","transfer_encoding":"chunked","connection":"keep-alive","cache_control":"max-age=3600","expires":"Wed, 06 Jan 2021 02:04:59 GMT","location":"https://vigneshh.in/","cf_request_id":"0776d2d4760000f55947917000000001","report_to":"{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report?s=ETVgpWk5MwNmSv7ZSCQ%2B%2F5mWTTcwMGltJh0waEBoj%2FNrzwHHHikgeL5fas7I5zXcmBhvy7DOshY0K%2B7XUlaGOjpzM80ZK6s0AHCB1ptbObHBLe%2FGsWFNgQ%3D%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}","nel":"{\"report_to\":\"cf-nel\",\"max_age\":604800}","vary":"Accept-Encoding","x_content_type_options":"nosniff","server":"cloudflare","cf_ray":"60d18733f9e9f559-SEA"},"headers_text":"HTTP/1.1 301 Moved Permanently\r\nDate: Wed, 06 Jan 2021 01:04:59 GMT\r\nTransfer-Encoding: chunked\r\nConnection: keep-alive\r\nCache-Control: max-age=3600\r\nExpires: Wed, 06 Jan 2021 02:04:59 GMT\r\nLocation: https://vigneshh.in/\r\ncf-request-id: 0776d2d4760000f55947917000000001\r\nReport-To: {\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report?s=ETVgpWk5MwNmSv7ZSCQ%2B%2F5mWTTcwMGltJh0waEBoj%2FNrzwHHHikgeL5fas7I5zXcmBhvy7DOshY0K%2B7XUlaGOjpzM80ZK6s0AHCB1ptbObHBLe%2FGsWFNgQ%3D%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}\r\nNEL: {\"report_to\":\"cf-nel\",\"max_age\":604800}\r\nVary: Accept-Encoding\r\nX-Content-Type-Options: nosniff\r\nServer: cloudflare\r\nCF-RAY: 60d18733f9e9f559-SEA\r\n\r\n","mime_type":"","request_headers":{"host":"vigneshh.in","connection":"keep-alive","upgrade_insecure_requests":"1","user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.0 Safari/537.36","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9","accept_encoding":"gzip, deflate","accept_language":"en-GB,en;q=0.9"},"request_headers_text":"GET / HTTP/1.1\r\nHost: vigneshh.in\r\nConnection: keep-alive\r\nUpgrade-Insecure-Requests: 1\r\nUser-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.0 Safari/537.36\r\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9\r\nAccept-Encoding: gzip, deflate\r\nAccept-Language: en-GB,en;q=0.9\r\n","connection_reused":false,"connection_id":52,"remote_i_p_address":"[2606:4700:3030::681c:133e]","remote_port":80,"from_disk_cache":false,"from_service_worker":false,"from_prefetch_cache":false,"encoded_data_length":673,"timing":{"request_time":1012040.278533,"proxy_start":-1,"proxy_end":-1,"dns_start":0.347,"dns_end":35.274,"connect_start":35.274,"connect_end":50.998,"ssl_start":-1,"ssl_end":-1,"worker_start":-1,"worker_ready":-1,"worker_fetch_start":-1,"worker_respond_with_settled":-1,"send_start":51.102,"send_end":51.187,"push_start":0,"push_end":0,"receive_headers_end":85.369},"response_time":1609895099499.776,"protocol":"http/1.1","security_state":"insecure"},"timings":{"blocked":0.3469999646767974,"queueing":1.1060000397264957,"proxy":-1,"dns":34.92700005881488,"ssl":-1,"connect":15.72399993892759,"send":0.0849999487400055,"wait":34.18199997395277,"receive":1.6710000345483422,"total":88.14600005280226}},"package_version":"0.0.1-alpha.8"}

{"type":"journey/network_info","@timestamp":1609895099505859,"journey":{"name":"check that title is present","id":"check that title is present"},"step":{"name":"go to app","index":1},"payload":{"step":{"name":"go to app","index":1},"timestamp":1609895099505859,"url":"https://vigneshh.in/","request":{"url":"https://vigneshh.in/","method":"GET","headers":{"upgrade_insecure_requests":"1","user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.0 Safari/537.36","method":"GET","authority":"vigneshh.in","scheme":"https","path":"/","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9","sec_fetch_site":"none","sec_fetch_mode":"navigate","sec_fetch_user":"?1","sec_fetch_dest":"document","sec_ch_ua":"\";Not\\\\A\\\"Brand\";v=\"99\", \"Chromium\";v=\"88\"","sec_ch_ua_mobile":"?0","accept_encoding":"gzip, deflate, br","accept_language":"en-GB,en;q=0.9"},"mixed_content_type":"none","initial_priority":"VeryHigh","referrer_policy":"strict-origin-when-cross-origin"},"type":"Document","method":"GET","request_sent_time":1012040.365573,"is_navigation_request":true,"status":200,"load_end_time":1012040.564763,"response_received_time":1012040.567352,"response":{"url":"https://vigneshh.in/","status":200,"status_text":"","headers":{"date":"Wed, 06 Jan 2021 01:04:59 GMT","content_type":"text/html; charset=utf-8","set_cookie":"__cfduid=df3f740b1d7c6b826023178e9eb075e731609895099; expires=Fri, 05-Feb-21 01:04:59 GMT; path=/; domain=.vigneshh.in; HttpOnly; SameSite=Lax","last_modified":"Wed, 17 Jun 2020 21:25:03 GMT","access_control_allow_origin":"*","expires":"Tue, 05 Jan 2021 23:33:29 GMT","cache_control":"max-age=600","x_proxy_cache":"MISS","x_github_request_id":"3A50:9DDA:1D63276:217135C:5FF4F4F0","via":"1.1 varnish","age":"0","x_served_by":"cache-sea4480-SEA","x_cache":"HIT","x_cache_hits":"1","x_timer":"S1609895100.637506,VS0,VE77","vary":"Accept-Encoding","x_fastly_request_id":"530154c96c465eb52b011e3840dd4abdbe458cec","cf_cache_status":"DYNAMIC","cf_request_id":"0776d2d4ec0000f595ecb0c000000001","expect_ct":"max-age=604800, report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\"","report_to":"{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report?s=iGmKNu4iAQOZ%2BSHSlaXGYbHoyQpRBfjQPT91NCwk75y%2B1K%2BoOVynIlQJJkh0UfWhCLB0Had1oyismCAri9wwwJEsteUB79Bc%2Bw%2BZfTREevWB0eJYvA5yvQ%3D%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}","nel":"{\"report_to\":\"cf-nel\",\"max_age\":604800}","strict_transport_security":"max-age=2592000; includeSubDomains","x_content_type_options":"nosniff","server":"cloudflare","cf_ray":"60d18734aee8f595-SEA","content_encoding":"br"},"mime_type":"text/html","request_headers":{"method":"GET","authority":"vigneshh.in","scheme":"https","path":"/","upgrade_insecure_requests":"1","user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.0 Safari/537.36","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9","sec_fetch_site":"none","sec_fetch_mode":"navigate","sec_fetch_user":"?1","sec_fetch_dest":"document","sec_ch_ua":"\";Not\\\\A\\\"Brand\";v=\"99\", \"Chromium\";v=\"88\"","sec_ch_ua_mobile":"?0","accept_encoding":"gzip, deflate, br","accept_language":"en-GB,en;q=0.9"},"connection_reused":false,"connection_id":62,"remote_i_p_address":"[2606:4700:3030::681c:133e]","remote_port":443,"from_disk_cache":false,"from_service_worker":false,"from_prefetch_cache":false,"encoded_data_length":3332,"timing":{"request_time":1012040.367565,"proxy_start":-1,"proxy_end":-1,"dns_start":0.242,"dns_end":36.614,"connect_start":36.614,"connect_end":80.609,"ssl_start":52.111,"ssl_end":80.6,"worker_start":-1,"worker_ready":-1,"worker_fetch_start":-1,"worker_respond_with_settled":-1,"send_start":80.808,"send_end":80.991,"push_start":0,"push_end":0,"receive_headers_end":195.368},"response_time":1609895099698.864,"protocol":"h2","security_state":"secure","security_details":{"protocol":"TLS 1.3","key_exchange":"","key_exchange_group":"X25519","cipher":"AES_128_GCM","certificate_id":0,"subject_name":"sni.cloudflaressl.com","san_list":["sni.cloudflaressl.com","*.vigneshh.in","vigneshh.in"],"issuer":"Cloudflare Inc ECC CA-3","valid_from":1595980800,"valid_to":1627560000,"signed_certificate_timestamp_list":[],"certificate_transparency_compliance":"unknown"}},"timings":{"blocked":0.24199998006224632,"queueing":1.9919999176636338,"proxy":-1,"dns":36.37200000230223,"ssl":28.488999931141734,"connect":43.99500007275492,"send":0.1829999964684248,"wait":114.37699990347028,"receive":1.8300000810995698,"total":199.1899999557063}},"package_version":"0.0.1-alpha.8"}

Verification
Timings for http://vigneshh.in -> NO SSL timing as its HTTP endpoint
{
  "blocked": 0.3469999646767974,
  "queueing": 1.1060000397264957,
  "proxy": -1,
  "dns": 34.92700005881488,
  "ssl": -1,
  "connect": 15.72399993892759,
  "send": 0.0849999487400055,
  "wait": 34.18199997395277,
  "receive": 1.6710000345483422,
  "total": 88.14600005280226
}

Timings for https://vigneshh.in
{
  "blocked": 0.24199998006224632,
  "queueing": 1.9919999176636338,
  "proxy": -1,
  "dns": 36.37200000230223,
  "ssl": 28.488999931141734,
  "connect": 43.99500007275492,
  "send": 0.1829999964684248,
  "wait":<PHONE_NUMBER>0347028,
  "receive": 1.8300000810995698,
  "total":<PHONE_NUMBER>557063
}

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #180 opened

Start Time: 2021-01-06T01:08:48.168+0000

Duration: 13 min 55 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
46

Skipped
0

Total
46

Steps errors
Expand to view the steps failures

Build Docker image

Took 0 min 0 sec . View more details on here

Build Docker image

Took 0 min 0 sec . View more details on here

Log output
Expand to view the last 100 lines of log output

[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/core/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 178B   dist/dsl/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 1.5kB  dist/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 221B   dist/plugins/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 252B   dist/reporters/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 1.0kB  dist/dsl/journey.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 776B   dist/dsl/journey.js.map
[2021-01-06T01:21:36.653Z] npm notice 659B   dist/reporters/json.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 3.0kB  dist/reporters/json.js.map
[2021-01-06T01:21:36.653Z] npm notice 225B   dist/core/logger.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 925B   dist/core/logger.js.map
[2021-01-06T01:21:36.653Z] npm notice 827B   dist/plugins/network.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 7.1kB  dist/plugins/network.js.map
[2021-01-06T01:21:36.653Z] npm notice 221B   dist/parse_args.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/parse_args.js.map
[2021-01-06T01:21:36.653Z] npm notice 757B   dist/plugins/performance.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.0kB  dist/plugins/performance.js.map
[2021-01-06T01:21:36.653Z] npm notice 967B   dist/plugins/plugin-manager.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.9kB  dist/plugins/plugin-manager.js.map
[2021-01-06T01:21:36.653Z] npm notice 3.2kB  dist/core/runner.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 6.6kB  dist/core/runner.js.map
[2021-01-06T01:21:36.653Z] npm notice 342B   dist/dsl/step.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 328B   dist/dsl/step.js.map
[2021-01-06T01:21:36.653Z] npm notice 687B   dist/plugins/tracing.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.5kB  dist/plugins/tracing.js.map
[2021-01-06T01:21:36.653Z] npm notice 1.7kB  README.md
[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/reporters/base.d.ts
[2021-01-06T01:21:36.653Z] npm notice 4.3kB  src/reporters/base.ts
[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/plugins/browser-console.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.2kB  src/plugins/browser-console.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/browser-service.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.0kB  src/browser-service.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/cli.d.ts
[2021-01-06T01:21:36.653Z] npm notice 5.0kB  src/cli.ts
[2021-01-06T01:21:36.653Z] npm notice 2.7kB  dist/common_types.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.5kB  src/common_types.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/core/gatherer.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.1kB  src/core/gatherer.ts
[2021-01-06T01:21:36.653Z] npm notice 3.8kB  dist/helpers.d.ts
[2021-01-06T01:21:36.653Z] npm notice 6.6kB  src/helpers.ts
[2021-01-06T01:21:36.653Z] npm notice 1.8kB  dist/core/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/dsl/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  dist/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  dist/plugins/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  dist/reporters/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.8kB  src/core/index.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  src/dsl/index.ts
[2021-01-06T01:21:36.653Z] npm notice 2.7kB  src/index.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  src/plugins/index.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  src/reporters/index.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/dsl/journey.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.2kB  src/dsl/journey.ts
[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/reporters/json.d.ts
[2021-01-06T01:21:36.653Z] npm notice 5.0kB  src/reporters/json.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  dist/core/logger.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.8kB  src/core/logger.ts
[2021-01-06T01:21:36.653Z] npm notice 2.7kB  dist/plugins/network.d.ts
[2021-01-06T01:21:36.653Z] npm notice 9.7kB  src/plugins/network.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  dist/parse_args.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.0kB  src/parse_args.ts
[2021-01-06T01:21:36.653Z] npm notice 1.8kB  dist/plugins/performance.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.4kB  src/plugins/performance.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/plugins/plugin-manager.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.4kB  src/plugins/plugin-manager.ts
[2021-01-06T01:21:36.653Z] npm notice 4.4kB  dist/core/runner.d.ts
[2021-01-06T01:21:36.653Z] npm notice 9.6kB  src/core/runner.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  dist/dsl/step.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  src/dsl/step.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/plugins/tracing.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.4kB  src/plugins/tracing.ts
[2021-01-06T01:21:36.653Z] npm notice 71.6kB dist/tsconfig.tsbuildinfo
[2021-01-06T01:21:36.653Z] npm notice === Tarball Details ===
[2021-01-06T01:21:36.653Z] npm notice name:          @elastic/synthetics
[2021-01-06T01:21:36.653Z] npm notice version:       0.0.1-alpha.8
[2021-01-06T01:21:36.653Z] npm notice filename:      elastic-synthetics-0.0.1-alpha.8.tgz
[2021-01-06T01:21:36.653Z] npm notice package size:  63.4 kB
[2021-01-06T01:21:36.653Z] npm notice unpacked size: 335.3 kB
[2021-01-06T01:21:36.653Z] npm notice shasum:        fcc52d87c6dc7f52dc4332bab8be44a576e35e08
[2021-01-06T01:21:36.653Z] npm notice integrity:     sha512-LfaYU4QTrXDun[...]L1NDf0L6QA9vg==
[2021-01-06T01:21:36.653Z] npm notice total files:   114
[2021-01-06T01:21:36.653Z] npm notice
[2021-01-06T01:21:36.653Z] elastic-synthetics-0.0.1-alpha.8.tgz
[2021-01-06T01:21:38.563Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-180/src/github.com/elastic/synthetics
[2021-01-06T01:21:38.602Z] [INFO] getVaultSecret: Getting secrets
[2021-01-06T01:21:38.864Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-01-06T01:21:39.784Z] + set +x
[2021-01-06T01:21:40.046Z] Login Succeeded
[2021-01-06T01:21:40.483Z] + date +%Y-%m-%d_%H:%M
[2021-01-06T01:21:40.484Z] + docker build -t docker.elastic.co/observability-ci/synthetics:49a7326aef9a21298c4e4928ecdb5afb830dca73-7.10.0-synthetics -t docker.elastic.co/observability-ci/synthetics:PR-180-7.10.0-synthetics --build-arg STACK_VERSION=7.10.0-synthetics --label BRANCH_NAME=PR-180 --label GIT_SHA=49a7326aef9a21298c4e4928ecdb5afb830dca73 --label TIMESTAMP=2021-01-06_01:21 .
[2021-01-06T01:21:40.484Z] Sending build context to Docker daemon  3.023MB

[2021-01-06T01:21:40.484Z] Error response from daemon: dockerfile parse error line 22: unknown instruction: /USR/SHARE/HEARTBEAT/.NPM
[2021-01-06T01:21:41.483Z] Stage "experimental" skipped due to earlier failure(s)
[2021-01-06T01:21:41.716Z] Failed in branch Matrix - STACK_VERSION = '7.10.0-synthetics'
[2021-01-06T01:21:42.049Z] Running on Jenkins in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-180
[2021-01-06T01:21:42.147Z] [INFO] getVaultSecret: Getting secrets
[2021-01-06T01:21:42.402Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-01-06T01:21:43.237Z] + chmod 755 generate-build-data.sh
[2021-01-06T01:21:43.238Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/runs/1 FAILURE 774799
[2021-01-06T01:21:43.488Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/runs/1/steps/?limit=10000 -o steps-info.json
[2021-01-06T01:21:44.039Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/runs/1/tests/?status=FAILED -o tests-errors.json

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #180 opened

Start Time: 2021-01-06T01:08:48.168+0000

Duration: 13 min 55 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
46

Skipped
0

Total
46

Steps errors
Expand to view the steps failures

Build Docker image

Took 0 min 0 sec . View more details on here

Build Docker image

Took 0 min 0 sec . View more details on here

Log output
Expand to view the last 100 lines of log output

[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/core/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 178B   dist/dsl/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 1.5kB  dist/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 221B   dist/plugins/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 252B   dist/reporters/index.js.map
[2021-01-06T01:21:36.653Z] npm notice 1.0kB  dist/dsl/journey.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 776B   dist/dsl/journey.js.map
[2021-01-06T01:21:36.653Z] npm notice 659B   dist/reporters/json.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 3.0kB  dist/reporters/json.js.map
[2021-01-06T01:21:36.653Z] npm notice 225B   dist/core/logger.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 925B   dist/core/logger.js.map
[2021-01-06T01:21:36.653Z] npm notice 827B   dist/plugins/network.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 7.1kB  dist/plugins/network.js.map
[2021-01-06T01:21:36.653Z] npm notice 221B   dist/parse_args.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/parse_args.js.map
[2021-01-06T01:21:36.653Z] npm notice 757B   dist/plugins/performance.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.0kB  dist/plugins/performance.js.map
[2021-01-06T01:21:36.653Z] npm notice 967B   dist/plugins/plugin-manager.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.9kB  dist/plugins/plugin-manager.js.map
[2021-01-06T01:21:36.653Z] npm notice 3.2kB  dist/core/runner.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 6.6kB  dist/core/runner.js.map
[2021-01-06T01:21:36.653Z] npm notice 342B   dist/dsl/step.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 328B   dist/dsl/step.js.map
[2021-01-06T01:21:36.653Z] npm notice 687B   dist/plugins/tracing.d.ts.map
[2021-01-06T01:21:36.653Z] npm notice 1.5kB  dist/plugins/tracing.js.map
[2021-01-06T01:21:36.653Z] npm notice 1.7kB  README.md
[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/reporters/base.d.ts
[2021-01-06T01:21:36.653Z] npm notice 4.3kB  src/reporters/base.ts
[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/plugins/browser-console.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.2kB  src/plugins/browser-console.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/browser-service.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.0kB  src/browser-service.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/cli.d.ts
[2021-01-06T01:21:36.653Z] npm notice 5.0kB  src/cli.ts
[2021-01-06T01:21:36.653Z] npm notice 2.7kB  dist/common_types.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.5kB  src/common_types.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/core/gatherer.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.1kB  src/core/gatherer.ts
[2021-01-06T01:21:36.653Z] npm notice 3.8kB  dist/helpers.d.ts
[2021-01-06T01:21:36.653Z] npm notice 6.6kB  src/helpers.ts
[2021-01-06T01:21:36.653Z] npm notice 1.8kB  dist/core/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  dist/dsl/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  dist/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  dist/plugins/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  dist/reporters/index.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.8kB  src/core/index.ts
[2021-01-06T01:21:36.653Z] npm notice 1.2kB  src/dsl/index.ts
[2021-01-06T01:21:36.653Z] npm notice 2.7kB  src/index.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  src/plugins/index.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  src/reporters/index.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/dsl/journey.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.2kB  src/dsl/journey.ts
[2021-01-06T01:21:36.653Z] npm notice 1.6kB  dist/reporters/json.d.ts
[2021-01-06T01:21:36.653Z] npm notice 5.0kB  src/reporters/json.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  dist/core/logger.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.8kB  src/core/logger.ts
[2021-01-06T01:21:36.653Z] npm notice 2.7kB  dist/plugins/network.d.ts
[2021-01-06T01:21:36.653Z] npm notice 9.7kB  src/plugins/network.ts
[2021-01-06T01:21:36.653Z] npm notice 1.3kB  dist/parse_args.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.0kB  src/parse_args.ts
[2021-01-06T01:21:36.653Z] npm notice 1.8kB  dist/plugins/performance.d.ts
[2021-01-06T01:21:36.653Z] npm notice 2.4kB  src/plugins/performance.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/plugins/plugin-manager.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.4kB  src/plugins/plugin-manager.ts
[2021-01-06T01:21:36.653Z] npm notice 4.4kB  dist/core/runner.d.ts
[2021-01-06T01:21:36.653Z] npm notice 9.6kB  src/core/runner.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  dist/dsl/step.d.ts
[2021-01-06T01:21:36.653Z] npm notice 1.4kB  src/dsl/step.ts
[2021-01-06T01:21:36.653Z] npm notice 2.1kB  dist/plugins/tracing.d.ts
[2021-01-06T01:21:36.653Z] npm notice 3.4kB  src/plugins/tracing.ts
[2021-01-06T01:21:36.653Z] npm notice 71.6kB dist/tsconfig.tsbuildinfo
[2021-01-06T01:21:36.653Z] npm notice === Tarball Details ===
[2021-01-06T01:21:36.653Z] npm notice name:          @elastic/synthetics
[2021-01-06T01:21:36.653Z] npm notice version:       0.0.1-alpha.8
[2021-01-06T01:21:36.653Z] npm notice filename:      elastic-synthetics-0.0.1-alpha.8.tgz
[2021-01-06T01:21:36.653Z] npm notice package size:  63.4 kB
[2021-01-06T01:21:36.653Z] npm notice unpacked size: 335.3 kB
[2021-01-06T01:21:36.653Z] npm notice shasum:        fcc52d87c6dc7f52dc4332bab8be44a576e35e08
[2021-01-06T01:21:36.653Z] npm notice integrity:     sha512-LfaYU4QTrXDun[...]L1NDf0L6QA9vg==
[2021-01-06T01:21:36.653Z] npm notice total files:   114
[2021-01-06T01:21:36.653Z] npm notice
[2021-01-06T01:21:36.653Z] elastic-synthetics-0.0.1-alpha.8.tgz
[2021-01-06T01:21:38.563Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-180/src/github.com/elastic/synthetics
[2021-01-06T01:21:38.602Z] [INFO] getVaultSecret: Getting secrets
[2021-01-06T01:21:38.864Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-01-06T01:21:39.784Z] + set +x
[2021-01-06T01:21:40.046Z] Login Succeeded
[2021-01-06T01:21:40.483Z] + date +%Y-%m-%d_%H:%M
[2021-01-06T01:21:40.484Z] + docker build -t docker.elastic.co/observability-ci/synthetics:49a7326aef9a21298c4e4928ecdb5afb830dca73-7.10.0-synthetics -t docker.elastic.co/observability-ci/synthetics:PR-180-7.10.0-synthetics --build-arg STACK_VERSION=7.10.0-synthetics --label BRANCH_NAME=PR-180 --label GIT_SHA=49a7326aef9a21298c4e4928ecdb5afb830dca73 --label TIMESTAMP=2021-01-06_01:21 .
[2021-01-06T01:21:40.484Z] Sending build context to Docker daemon  3.023MB

[2021-01-06T01:21:40.484Z] Error response from daemon: dockerfile parse error line 22: unknown instruction: /USR/SHARE/HEARTBEAT/.NPM
[2021-01-06T01:21:41.483Z] Stage "experimental" skipped due to earlier failure(s)
[2021-01-06T01:21:41.716Z] Failed in branch Matrix - STACK_VERSION = '7.10.0-synthetics'
[2021-01-06T01:21:42.049Z] Running on Jenkins in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-180
[2021-01-06T01:21:42.147Z] [INFO] getVaultSecret: Getting secrets
[2021-01-06T01:21:42.402Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-01-06T01:21:43.237Z] + chmod 755 generate-build-data.sh
[2021-01-06T01:21:43.238Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/runs/1 FAILURE 774799
[2021-01-06T01:21:43.488Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/runs/1/steps/?limit=10000 -o steps-info.json
[2021-01-06T01:21:44.039Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-180/runs/1/tests/?status=FAILED -o tests-errors.json

Docker build issue is fixed by #179

Docker build issue is fixed by #179


How can get the adjacent matrix that only cantain k-hop neighbors?

From now on, we recommend using our discussion forum (https://github.com/rusty1s/pytorch_geometric/discussions) for general questions.
❓ Questions & Help
Thank you for your work!
Please, I want to know hot to get the adjacent matrix that only cantain k-hop neighbors?
For example, cora dataset, the edge_index is the complete adjacent matrix. If I want to get the adjacent matrix, which is only contain 2-hop neighbors but not contain 1-hop and x-hop x>2, how can I do?
I m looking forward to your answer! Thank you!

If it is applicable, you could use dense adjacency matrices to achieve that:
adj = torch.zeros(N, N, dtype=torch.long)
adj[edge_index[0], edge_index[1]] = 1

new_adj = (adj @ adj)
new_adj = ((new_adj > 0).to(torch.long) + adj) == 1

If it is applicable, you could use dense adjacency matrices to achieve that:
adj = torch.zeros(N, N, dtype=torch.long)
adj[edge_index[0], edge_index[1]] = 1

new_adj = (adj @ adj)
new_adj = ((new_adj > 0).to(torch.long) + adj) == 1

Thank you for your answer!
Is any sparse approach?

You could use np.isin to filter out the edges that appear in both adj and adj @ adj. That should work for sparse adjacencies.

You could use np.isin to filter out the edges that appear in both adj and adj @ adj. That should work for sparse adjacencies.

I'm sorry for my slowness. Could you be more specific？

Sure. It might look like the following code (note that I didn't test it):
edge_index = ...
edge_index2 = spspmm(...)

idx = edge_index[0] * num_nodes + edge_index[1]
idx2 = edge_index2[0] * num_nodes + edge_index2[1]

mask = torch.from_numpy(np.isin(idx2.numpy(), idx.numpy()))
mask = ~mask  # Invert mask to only contain the elements not in `idx`

edge_index2 = edge_index2[:, mask]

Sure. It might look like the following code (note that I didn't test it):
edge_index = ...
edge_index2 = spspmm(...)

idx = edge_index[0] * num_nodes + edge_index[1]
idx2 = edge_index2[0] * num_nodes + edge_index2[1]

mask = torch.from_numpy(np.isin(idx2.numpy(), idx.numpy()))
mask = ~mask  # Invert mask to only contain the elements not in `idx`

edge_index2 = edge_index2[:, mask]

I m sorry that there is a problem.
All computation is finished on cuda. So it seems that converting to numpy is not feasible.
:)

As far as I know, there is no isin functionality implemented in PyTorch, but you can transfer your tensors to CPU first before calling numpy().

Yes, I didn't do it because transfer to CPU and transfer to GPU can cause problem of speed.
Is there any approaches that can make messege passing only in k-hop neighbor but no other neighbor?
Thank you!

I don't know of any. I also do not think that speed is a deciding factor, as you can usually simply pre-process the 2-hop graph, and therefore only have to do it once.

Hi, I check the code and write it as fellow:
x, edge_index = data.x, data.edge_index

N = x.size(0)

row, col = edge_index
edge_index2 = torch_sparse.spspmm(edge_index, torch.ones([col.size(0)], device='cuda'),
                                    edge_index, torch.ones([col.size(0)], device='cuda'),
                                    N, N, N)

idx = edge_index[0] * N + edge_index[1]
idx2 = edge_index2[0] * N + edge_index2[1]

mask = torch.from_numpy(np.isin(idx2.cpu().numpy(), idx.cpu().numpy()))
mask = ~mask  # Invert mask to only contain the elements not in `idx`

edge_index2 = edge_index2[:, mask]

But it reported the error:
  File "k-hop.py", line 53, in <module>
    edge_index2 = edge_index2[:, mask]
TypeError: tuple indices must be integers or slices, not tuple

How can I fix this error? Thank you!

Hi, I check the code and write it as follow:
x, edge_index = data.x, data.edge_index

N = x.size(0)

row, col = edge_index
edge_index2 = torch_sparse.spspmm(edge_index, torch.ones([col.size(0)], device='cuda'),
                                    edge_index, torch.ones([col.size(0)], device='cuda'),
                                    N, N, N)

idx = edge_index[0] * N + edge_index[1]
idx2 = edge_index2[0] * N + edge_index2[1]

mask = torch.from_numpy(np.isin(idx2.cpu().numpy(), idx.cpu().numpy()))
mask = ~mask  # Invert mask to only contain the elements not in `idx`

edge_index2 = edge_index2[:, mask]

But it reported the error:
  File "k-hop.py", line 53, in <module>
    edge_index2 = edge_index2[:, mask]
TypeError: tuple indices must be integers or slices, not tuple

How can I fix this error? Thank you!

I found it just need to add an _ in spspmm and fix this error.
And how can I check it and insure it dose get k-hop neighbor?


i can't load a image from url

I try to load a image from http://thirdwx.qlogo.cn/mmopen/XYrRG5UShDcrTQs7ZnsUks0uT8AqAPcwNPnwmnHef1c0a5O2ScvubY5iaB9nHCAswFCWJLicic6Z3FLWcXTEYvw1qYOQG2f9gQn/132
param:
{
  name: 'avatar',
  url: 'http://thirdwx.qlogo.cn/mmopen/XYrRG5UShDcrTQs7ZnsUks0uT8AqAPcwNPnwmnHef1c0a5O2ScvubY5iaB9nHCAswFCWJLicic6Z3FLWcXTEYvw1qYOQG2f9gQn/132',
  options: {
    xhrType: PIXI.loaders.Resource.XHR_RESPONSE_TYPE.BLOB,
  },
}

but i find the resource's data is text

example:
https://jsfiddle.net/w6puqrsx/8/

I've fixed your fiddle: https://jsfiddle.net/L6wn9b4p/
There were a number of things causing it not to work

You weren't adding the canvas element correct. I've fixed this with document.body.appendChild(app.view);
You correctly worked out that you needed to manually set a loadType, because your url has no extension, but you'd created a new options object when you were already within the options object
You needed to use the texture of res.test to create the Sprite

Thanks very much for you reply.
发送自 Windows 10 版邮件https://go.microsoft.com/fwlink/?LinkId=550986应用

发件人: Dave Moore<EMAIL_ADDRESS>发送时间: Saturday, August 11, 2018 6:51:48 PM
收件人: englercj/resource-loader
抄送: Cheng; Author
主题: Re: [englercj/resource-loader] i can't load a image from url (#115)
I've fixed your fiddle: https://jsfiddle.net/L6wn9b4p/
There were a number of things causing it not to work

You weren't adding the canvas element correct. I've fixed this with document.body.appendChild(app.view);
You correctly worked out that you needed to manually set a loadType, because your url has no extension, but you'd created a new options object when you were already within the options object
You needed to use the texture of res.test to create the Sprite

―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/englercj/resource-loader/issues/115#issuecomment-412267551, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANtC1KqgXnqZ-7pGShy4eJHSceU2MxJsks5uPrdEgaJpZM4V5Flc.


⚠ Bofrost.at has degraded performance

In e6d48ab, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 934 ms

Resolved: Bofrost.at performance has improved in 5c9706c after 6 minutes.


Connect CSV random patient gen to interview gen

sorry please delete this, i accidentally created an issue in the wrong repo!!

No worries


connection (socket) still open

I call a subreport with following properties:

(Subreport has a different data source / data connection as main report).
Actually I have the problem, that the connection to ES Server will not be closed after report creation is done.
Is there some workaround or fix, that the connection will be closed?
Please can somebody help me? Thank you
additional foundings:
I analyzed the traffic (tcp connections) with wireshark.   per subreport call, there will be opened around 15 tcp connection (with high ports up to arround 30) - only with one, the query will be send to ES. this connection will be closed but some connection (and threads) will stay  and all 5 seconds they made a request to the ES "action = cluster/state". not more...
Is there a way (config) to limit the open threads and tcp connection?
In my productive environment, there are ~15000 tcp connection opened permanently.
Thank you

Is someone from the developers ready to give me a help to this topic. I guess, it will be helpfull for the whole project. Thank you

Will look into this. The traffic you are seeing is coming from the ES client talking to the cluster. We may need to kill the ES client once the report is done and spin up a new one or maybe manage a pool of clients.


Update FAQ.md

Add an FAQ entry for the "profile already running" chromium bug

this should be adjacent to "Why won't hardened-chromium start on Nvidia?"

PR title needs to be semantic


Create Update CryptoSJ.net for v0.20 - IP changed

Update CryptoSJ.net for v0.20 - IP changed
Please note that IP changed . Thanks

Sorry, I couldn't find a previously merged PR from you. Please link it here. Also rename your toml to not have double quotes

tt


Feature/register form

👷 Deploy Preview for cg-eleventy-blog processing.

Name
Link

🔨 Latest commit
e390b5d922e0a715a3dedf64132f0d4e8b1d333d

🔍 Latest deploy log
https://app.netlify.com/sites/cg-eleventy-blog/deploys/65c43997f796b20008e92fe0


Exported path lookup failure causes full page loads

Bug report
Describe the bug
When using an exported app it tries to load the wrong js file. This causes full loads when only a "history push" is expected (even when a link is shallow).
Our specific use case is a modal controlled by the query parameters which now when a full page load happens scrolls up and does not animate in smoothly as expected. It also behaves "properly" in dev.
To Reproduce

Go to https://out-pxzzcijwlg.now.sh/
Make sure to have persistent logs enabled as page load clears it
See how the logs contains a 404 for the missing export path and a full navigation:

GET https://out-pxzzcijwlg.now.sh/_next/static/0nKDPOy4frajWiZ9UFgj~/pages/hello.js net::ERR_ABORTED 404
Navigated to https://out-pxzzcijwlg.now.sh/hello/

Checkout repo from git clone https://github.com/slaskis/test-next-export.git
Build and run it with: yarn && yarn build && yarn export && yarn serve to try it locally

Expected behavior
I expected it to load the same js bundle as when visiting the root page and not a 404.
Screenshots

System information

Version of Next.js: 7.0.0

https://github.com/zeit/next.js/issues/2833#issuecomment-324202757


Gene Ontology Annotations panel needs links

Currently the data is text only, needs links to match the format of the current gene summary page.
Example: http://dictybase.org/gene/DDB_G0288511
Every annotation in that panel links to a local ontology page.


CollectionView: provide cell in selection event

When manipulating the data item in a selection listener, it should be possible to update the cell. One simple option would be to provide a reference to the cell in the selection event so application code can trigger an itemchange event.

https://github.com/eclipsesource/tabris-js/issues/271

As of commit 79b03ff9, CollectionView offers a refresh method that should be used to update the cell.


xDripAPS doesn't work with Token Based Auth.

Note: the actual issue is with the xDripAPS codebase, not oref0. That issue is located here: https://github.com/colinlennon/xDripAPS/issues/2
xDripAPS does not correctly parse Nightscout Token-based-auth URL's, and instead looks for a (nonexistant) API Secret.
Current workaround: Switch back to using API Secret for authentication.

Was this fixed by @renegadeandy in https://github.com/renegadeandy/xDripAPS ?

Closing, per the xdrip issue link it was resolved.


Handling visibility state

The client library needs to handle the visibility state API in order to re-open Web Socket connections that were closed when a tab has been hidden for some time. The following probably is also true for Server-Sent events - that needs testing.  The client library in "wot.js" could listen for "visibilitychange" event on the document to determine when to test if the socket has closed and re-open it. Code that sends to a web socket should likewise test for a closed socket and reopen it - note that this will mean deferring a send until the socket opens.

Note: the server is already tidying up cleanly when connections are dropped for server-sent events and web sockets.

I've added a platform.resubscribe(thing) method and set up a visibility change listener when creating a thing. I've update the Arena adapters for event source and web sockets, but have still to work on ThingWeb and Things Gateway for which I need to track the set of current subscriptions.  ThingWeb requires a separate web socket per property or event that the app has subscribed to. Things Gateway uses one web socket per thing, but requires a subscribe message to be sent over the socket for each property or event the app has subscribed to.
I also need to add a message queue for web sockets in case the client app tries to send a message to the server before the socket opens. The socket open event should then flush the queue.


MPEG-DASH support ?

Wondering if there is any plans to add support for MPEG-DASH ?

There is only support for HLS for now but you could probably do it with some custom filters and these posts:

https://blog.streamroot.io/encode-multi-bitrate-videos-mpeg-dash-mse-based-media-players/
https://tdngan.wordpress.com/2016/11/17/how-to-encode-multi-bitrate-videos-in-mpeg-dash-for-mse-based-media-players/


Visual Studio 2017 Performance Profiler with 1 Node Local Dev Cluster (.net Core)

Has anyone been able to get the VS performance profiler running against a stateless .Net Core 2.0 Project?
Is it possible? If not, is there a timeframe when this will be fixed?

Please re-open if you are still facing this issue, but closing at this time.

I'm trying to run Profiler with an SF app for memory leaks in VS 2022. Does SF support VS Profiler or this is still not supported?


assert hit on non-zero core PM_SOFT_OFF exit in subsys/pm/pm.c:133

Describe the bug
Zephyr assert is hit when powering off and on non-primary/zero core on Intel cAVS2.5 platform running SOF app on Zephyr.
Original bug report to SOF https://github.com/thesofproject/sof/issues/8942 , filing here.
Same assert as https://github.com/zephyrproject-rtos/zephyr/issues/69807 but different scenario

different hw platform (cavs2.5 versus newer platforms)
on non-primary core
when exiting SOFTOFF state

To Reproduce
See https://github.com/thesofproject/sof/issues/8942
Expected behavior
No DSP panic when running SOF test suite.
Impact
High, loss of audio
Logs and console output
Environment (please complete the following information):
See https://github.com/thesofproject/sof/issues/8942
Additional context
This seems to to relate to commit 3e5a593de9f52b0ed96cf99dec21bbea8277e597 ("intel_adsp/cavs: power: Fix INTLEVEL value").

FYI @nashif @teburd @tmleman @marc-hb
This seem similar than Zephyr test case in review at https://github.com/zephyrproject-rtos/zephyr/pull/69365

Can be closed via #70184


[UPDATE] readme, add SwiftLocalNotification pod.

Project URL

Category

Description

Why it should be included to awesome-ios (mandatory)
Checklist

[ ] Has 50 GitHub stargazers or more
[ ] Only one project/change is in this pull request
[ ] Isn't an archived project
[ ] Has more than one contributor
[ ] Has unit tests, integration tests or UI tests
[ ] Addition in chronological order (bottom of category)
[ ] Supports iOS 9 / tvOS 10 or later
[ ] Supports Swift 4 or later
[ ] Has a commit from less than 2 years ago
[ ] Has a clear README in English

@Salarsoleimani We cannot merge your PR yet until you fill all of the contribution guideline requirements. Feel free to open PR once it is ready.
Please check our CONTRIBUTION GUIDELINES


consider downloading ffmpeg and ffprobe from https://github.com/eugeneware/ffmpeg-static

Use https://github.com/eugeneware/ffmpeg-static as it contains both ffmpeg and ffprobe and supports lot of different OS and architectures.
Currently it uses multiple domains. Having all from github.com would be great.
/// URL for the latest published FFmpeg release. The correct URL for the target
/// platform is baked in at compile time.
pub fn ffmpeg_download_url() -> Result<&'static str> {
  if cfg!(all(target_os = "windows", target_arch = "x86_64")) {
    Ok("https://www.gyan.dev/ffmpeg/builds/ffmpeg-release-essentials.zip")
  } else if cfg!(all(target_os = "linux", target_arch = "x86_64")) {
    Ok("https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-amd64-static.tar.xz")
  } else if cfg!(all(target_os = "macos", target_arch = "x86_64")) {
    Ok("https://evermeet.cx/ffmpeg/getrelease")
  } else if cfg!(all(target_os = "macos", target_arch = "aarch64")) {
    Ok("https://www.osxexperts.net/ffmpeg6arm.zip") // Mac M1
  } else {
    Err(Error::msg(
      "Unsupported platform; you can provide your own URL instead and call download_ffmpeg_package directly.",
    ))
  }
}

Great idea, I'm looking into this.

Hey @nathanbabcock I wanted to ask you about the licensing of FFMPEG. Is it legal to include static binaries of ffmpeg directly in our commercial product? I read the FFMPEG legal page but was not so sure about it. Since HypeTrigger also does similar kind of thing(including static binaries in the bundle), I wanted to ask you directly. Thanks

So to answer the question more directly:

Is it legal to include static binaries of ffmpeg directly in our commercial product?

Yes, if your app is non-commercial and you stick to an LGPL build of FFmpeg.

@niraj-khatiwada Great question and I'd encourage you to do your own research to be 100% sure for your own use case, but here is my understanding based on this official source: https://www.ffmpeg.org/legal.html.

The core parts of FFmpeg are LGPL, which do allow for commercial use
However, it may be compiled with extensions that are GPL (for example, certain proprietary codecs) which forbid commercial use

For a given FFmpeg binary, you can check which license applies to it by looking through the configuration flags that are printed out on every command, and check for --enable-gpl and/or --enable-nonfree.
As for ffmpeg-sidecar, some of the auto-downloaded binaries do include nonfree extensions (although the exact builds vary by platform). If you want to commercialize your product, you would want to replace these auto-download sources with your own custom build of FFmpeg that complies with the appropriate licensing terms. For example, if Hypetrigger introduced a paid plan in the future, we would do something similar.
As an aside — I actually think using the "sidecar" methodology offers some big advantages compared to other ways of using FFmpeg, such as static linking. In theory, you could skip bundling FFmpeg with your application entirely, and offer a step at runtime that guides the user to either download an official binary from a 3rd-party source, or provide their own. This would bypass most of the licensing constraints since you would be neither distributing nor linking against any part of the FFmpeg codebase. It would be more akin to the way a website is not bound by the licensing terms of any particular browser that opens it.
But to reiterate, if you are going to build a $10M startup that uses FFmpeg heavily, maybe check with an actual lawyer first :)

This was incredibly helpful Nathan. Thank you so much for your time and effort for this.

Here is what I'm using. Downloading direct binaries can also help in avoid having zip/tar to unpack.
pub fn default_ffmpeg_download_url() -> AppResult<&'static str> {
    if cfg!(all(target_os = "windows", target_arch = "x86_64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffmpeg-win32-x64")
    } else if cfg!(all(target_os = "linux", target_arch = "x86_64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffmpeg-linux-x64")
    } else if cfg!(all(target_os = "linux", target_arch = "aarch64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffmpeg-linux-arm64")
    } else if cfg!(all(target_os = "macos", target_arch = "x86_64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffmpeg-darwin-x64")
    } else if cfg!(all(target_os = "macos", target_arch = "aarch64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffmpeg-darwin-arm64")
    } else {
        Err(AppError::NotSupported("Unsupported platform".into()))
    }
}

pub fn default_ffprobe_download_url() -> AppResult<&'static str> {
    if cfg!(all(target_os = "windows", target_arch = "x86_64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffprobe-win32-x64")
    } else if cfg!(all(target_os = "linux", target_arch = "x86_64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffprobe-linux-x64")
    } else if cfg!(all(target_os = "linux", target_arch = "aarch64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffprobe-linux-arm64")
    } else if cfg!(all(target_os = "macos", target_arch = "x86_64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffprobe-darwin-x64")
    } else if cfg!(all(target_os = "macos", target_arch = "aarch64")) {
        Ok("https://github.com/eugeneware/ffmpeg-static/releases/download/b6.0/ffprobe-darwin-arm64")
    } else {
        Err(AppError::NotSupported("Unsupported platform".into()))
    }
}


[kws_streaming] Issue on Quantization for STREAM_EXTERNAL_STATE_INFERENCE(ds-cnn,  micro:  no feature extractor)

Hi,
I followed kws_streaming/models/cnn_test.py.  Generate "feature.npz" to prepare calibration_data.
feature.zip
I used the code below to convert the stream_state_external model to quantize model. But the final model I got is still float32. Is there anything I did wrong?
quantize_opt_for_size_tflite_stream_state_external folder:  stream_state_external.zip
  npzfile = np.load("feature.npz",allow_pickle=True)
  ttt=npzfile.f.arr_0
  calibration_data = prepare_calibration_data(model,100, ttt)
  def representative_dataset(dtype):
    def _representative_dataset_gen():
        for i in range(len(calibration_data)):
            yield [
                calibration_data[i][0].astype(dtype),  # input audio packet
                calibration_data[i][1].astype(dtype),  # conv state
                calibration_data[i][2].astype(dtype)  # flatten state
                ]
    return _representative_dataset_gen

    with quantize.quantize_scope():
        fd.write(
            utils.model_to_tflite(sess=sess, model_non_stream=model, flags=flags, mode=mode, save_model_path=path_model,
                            optimizations=optimizations,inference_type=tf.int8,experimental_new_quantizer=True,
                            representative_dataset=representative_dataset(np.float32)))

Convert parameters:
converter.inference_type = inference_type
converter.experimental_new_quantizer = experimental_new_quantizer
converter.experimental_enable_resource_variables = True
if representative_dataset is not None:
converter.representative_dataset = representative_dataset
converter.target_spec.supported_ops = [
tf.lite.OpsSet.TFLITE_BUILTINS_INT8, tf.lite.OpsSet.SELECT_TF_OPS
]
converter.inference_input_type = tf.int8
converter.inference_output_type = tf.int8
converter.allow_custom_ops = True
if optimizations:
converter.optimizations = optimizations
tflite_model = converter.convert()

I used latest tf-nightly.

@wenjingyang I do not know what are you going to achieve with your coversion parameters
If you follow example and set converter parameters:
  converter.inference_type = tf.int8
  converter.experimental_new_quantizer = True
  converter.experimental_enable_resource_variables = True
  converter.representative_dataset = representative_dataset

  # this will enable audio_spectrogram and mfcc in TFLite
  converter.target_spec.supported_ops = [
      tf.lite.OpsSet.TFLITE_BUILTINS, tf.lite.OpsSet.SELECT_TF_OPS
  ]
  converter.allow_custom_ops = True
  converter.inference_input_type = tf.int8
  converter.inference_output_type = tf.int8
  converter.optimizations = [tf.lite.Optimize.DEFAULT]

then you will get a fully quantized model with quantized inputs and outputs.
If you set parameters:
  converter.inference_type = tf.int8
  converter.experimental_new_quantizer = True
  converter.experimental_enable_resource_variables = True
  converter.representative_dataset = representative_dataset

  # this will enable audio_spectrogram and mfcc in TFLite
  converter.target_spec.supported_ops = [
      tf.lite.OpsSet.TFLITE_BUILTINS, tf.lite.OpsSet.SELECT_TF_OPS
  ]
  converter.allow_custom_ops = True
  converter.optimizations = [tf.lite.Optimize.DEFAULT]

then your model will be partially quantized: all inputs and outputs will be float including input/output states. All inputs/outputs will be quantized and de-quantized inside of the model.
If you create an issue at google-research without mentioning the owner of the project, then the owner will not be notified and there is no guarantee that the issue will be addressed. I would encourage you to mention the project owner in an issue, for example in case of kws_streaming you can use @rybakov, this way I will get notification and will not miss it.

@rybakov Thanks for your help.
My target is to get a fully quantized model.
I have tried the example  and it works fine. But I can't get any quantization on my ds-cnn model.
I checked the code and found the layer should be quantized  when cnn model is built. So my understanding is that I should use quantized layer when build ds-cnn model. Right?

@wenjingyang quantize.quantize_layer is used for quantization aware training and then it will be used by post-training quantization in tflite.
So, if you are interested in post-training quantization only, then you do not need quantize.quantize_layer with quantization aware training.
Please let me know what error you observe and how to reproduce it.
I would also suggest to try ds_tc_resnet model, with training example. It can be faster and more accurate than ds-cnn.

@rybakov  Thanks.
I generated ds_tc_resnet with your example (--preprocess micro).
My ds_tc_resnet folder:  ds_tc_resnet
I only changed the train/test.py with adding "representative_dataset".  I uploaded my test.py as test.txt since python file can't be uploaded.
You can reproduce this issue when you run the script below. I have highlighted the difference with your script.
$CMD_TRAIN
--data_url ''
--data_dir $DATA_PATH/
--train_dir $MODELS_PATH/ds_tc_resnet/
--mel_upper_edge_hertz 7600
--how_many_training_steps 4,4,2,2
--learning_rate 0.001,0.0005,0.0002,0.0001
--window_size_ms 30.0
--window_stride_ms 10.0
--mel_num_bins 80
--dct_num_features 40
--resample 0.15
--alsologtostderr
*--train 0 *
--use_spec_augment 1
--time_masks_number 2
--time_mask_max_size 25
--frequency_masks_number 2
--frequency_mask_max_size 7
--pick_deterministically 1
*--preprocess micro *
ds_tc_resnet
--activation 'relu'
--dropout 0.0
--ds_filters '128, 64, 64, 64, 128, 128'
--ds_repeat '1, 1, 1, 1, 1, 1'
--ds_residual '0, 1, 1, 1, 0, 0'
--ds_kernel_size '11, 13, 15, 17, 29, 1'
--ds_stride '1, 1, 1, 1, 1, 1'
--ds_dilation '1, 1, 1, 1, 2, 1'
The text.py difference.

@rybakov @wenjingyang hi,I want to covert a  internal states model to int8 quantized  model like below which can load on tflite micro.However,I have no about how to implement  representative_dataset_gen.Any good idea?
with tf.compat.v1.Session() as sess:
  converter = tf.lite.TFLiteConverter.from_saved_model(SAVED_MODEL)
  converter.optimizations = [tf.lite.Optimize.DEFAULT]
  converter.inference_input_type = tf.int8
  converter.inference_output_type = tf.int8
  def representative_dataset_gen():
    for i in range(1000):
      data, _ = audio_processor.get_data(1, i*1, model_settings,
                                         BACKGROUND_FREQUENCY,
                                         BACKGROUND_VOLUME_RANGE,
                                         TIME_SHIFT_MS,
                                         'testing',
                                         sess)
      flattened_data = np.array(data.flatten(), dtype=np.float32).reshape(1, 16000)
      yield [flattened_data]
  converter.representative_dataset = representative_dataset_gen
  tflite_model = converter.convert()
  tflite_model_size = open(MODEL_TFLITE, "wb").write(tflite_model)
  print("Quantized model is %d bytes" % tflite_model_size)


DiffConsoleFormatter - fix output escaping.

for ref: https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3290#issuecomment-348929490
cc @Slamdunk thanks for reporting!
TODO:

[x] Add utest
[x] Target lowest branch

(tested local using the linked fixer)

how do we know that this one works ?

Windows is sad :(

Windows is happy again ;)

I would like to implement github-like/diff-so-fancy colouring (https://github.com/so-fancy/diff-so-fancy#screenshot), but I need this PR for DiffConsoleFormatterTest.
Please ping me when merged @SpacePossum

you started observing the thread by posting in it, you will be pinged automatically for any activity here ;P

😄
I'm so used to unsubscribe notifications that I forgot they can be useful sometimes 🐳


chore: update pysnmplib to 5.0.24

Description
Security update of pysnmplib.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f297dd5) 84.32% compared to head (086dcfd) 84.32%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #948   +/-   ##
========================================
  Coverage    84.32%   84.32%
========================================
  Files           28       28
  Lines         2022     2022
========================================
  Hits          1705     1705
  Misses         317      317

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fixed all race conditions in tests in multiple packages

Fixes #5289
Fixes race conditions in multiple packages (most notably pkg/runtime and pkg/actors, among others), so running go test -race . reports no errors.

Fixes #5289
Now, running go test . -race in pkg/runtime reports no data races

Can you create a PR adding that to the validation steps for our build going forward? Going into the master branch for that is fine.

@yaron2 changed the lock in the runtime
Also:

go test -race passes on pkg/actors too now
added a make test-race with 3 packages that are known to pass. I'll use that for a pipeline in another PR targeting master

/ok-to-perf

/ok-to-perf

Qq on this PR should we add a CI check only for files that currently do not have race and fail if they are introduced later on?
@dapr/maintainers-dapr @ItalyPaleAle

Qq on this PR should we add a CI check only for files that currently do not have race and fail if they are introduced later on?

Yes, @artursouza requested that already:

Can you create a PR adding that to the validation steps for our build going forward? Going into the master branch for that is fine.

I will do that on Monday, I was just waiting for this PR to be merged.


Returning normal Physical ID of DataDog Monitor CloudFormation resource

What does this PR do?
This PR addresses ISSUE 80 so that when DataDog::Monitors::Monitor CloudFormation resource is stacked, instead of returning (e.g.) 2.0185875E7 as "Pyhsical ID" of resource, it actually returns 20185875 (which can then be used easier in the rest of CloudFormation templates as described in the issue).
Description of the Change

Using string instead of number in DataDog::Monitors::Monitor resource JSON schema for MonitorState.MonitorID.type property
Using string instead of number in DataDog::Monitors::Monitor resource JSON schema for Id property (id of the Monitor)
Caused by above two changes and RPDK regenerating new/different model, addressed managing of Monitor IDs in CreateHandler.java, DeleteHandler.java, ReadHandler.java, UpdateHandler.java
Update on auto-generated docs (by RPDK)
Changed type of Monitor ID property in MonitorCRUDTest.java to make tests functional again after main source changes (described above)

Alternate Designs

I have played with alternative of using integer as type for two changed JSON properties instead of string, but that didn't turn out very well as it imposes conversion from Long to Integers in some places and it could create potential issues for those depending on this as the IDs of monitors on DataDog API side are ever-increasing number.

Possible Drawbacks

Customers who depended on scientific-notation in Physical ID of DataDog::Monitors::Monitor (I am in this group) and manipulated it to parse ID of Monitor, will have to change CloudFormation templates to be able to leverage this improvement. But the change is non-breaking for those users, as long as they don't publish new version of Third-Party resource schema (with this fix) to their CloudFormation repository and make it a default one.

Verification Process

Built, tested and packaged with Maven, then packaged with AWS CloudFormation CLI and submitted as new&default version of Third-Party resource to CloudFormation Registry.

export DD_TEST_CF_API_KEY='<REDACTED>'
export DD_TEST_CF_APP_KEY='<REDACTED>'
export DD_TEST_CF_API_URL='https://api.datadoghq.com'
mvn test
#...
mvn package
#...
cfn submit \
>     -v \
>     --dry-run \
>     --endpoint-url 'https://cloudformation.us-east-1.amazonaws.com' \
>     --region 'us-east-1' \
>     --set-default \
>     --no-role
Validating your resource specification...
Dry run complete: /Users/azec/dev/datadog-cloudformation-resources/datadog-monitors-monitor-handler/datadog-monitors-monitor.zip
#...
cfn submit \
>     -v \
>     --endpoint-url 'https://cloudformation.us-east-1.amazonaws.com' \
>     --region 'us-east-1' \
>     --set-default \
>     --no-role
Validating your resource specification...
Creating CloudFormationManagedUploadInfrastructure
CloudFormationManagedUploadInfrastructure already exists. Attempting to update
CloudFormationManagedUploadInfrastructure stack is up to date
Successfully submitted type. Waiting for registration with token '<REDACTED>' to complete.
Registration complete.

Verified JUnit tests are passing

Deployed new CloudFormation template that has several DataDog::Monitoring::Monitor resources. Verified that "Physical ID" showed in CloudFormation console IS NOT in scientific notation anymore, but looks like regular number. See screenshot...

As you can tell there is no anymore E7 suffix in the values of Physical ID of DataDog::Monitoring::Monitor resources.
Additional Notes

There is a change in datadog-monitors-monitor-handler/pom.xml which adds aws-cloudformation-rpdk-java-plugin as dependency in this Maven submodule. I am not confident if it is really required, but I was unable to configure my IntelliJ+Maven plugin to build everything without this. I am willing to remove this part if this is just problem that I have (with some guidance on how to configure project without it).

Release Notes

Review checklist (to be filled by reviewers)

[x] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[x] PR title must be written as a CHANGELOG entry (see why)
[x] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[x] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[x] PR should not have do-not-merge/ label attached.
[x] If Applicable, issue must have kind/ and severity/ labels attached at least.

@bkabrda , I am not sure what/who needs to do PR labeling for it to be officially in the review pipeline, but willing to work through the details together.
Thank you!

Tagging @jirikuncar for visibility...

@jirikuncar , thanks for approving that. I am failing to understand what is the failure on the labeler. I don't have experience with this. Any guidance would be helpful, and I am willing to make changes.
Thanks!

Hey @azec-pdx Sorry for the trouble there, I believe the labeler failure is due to a limitation with forks and can safely be ignored

Hey @azec-pdx Sorry for the trouble there, I believe the labeler failure is due to a limitation with forks and can safely be ignored

Hi @nmuesch , thanks for taking a look? I am wondering if there is any action-items on my end to get that passing.
I have also reached out to DataDog Slack in #integrations hoping to get some traction with this.

@azec-pdx I'll go ahead and close this out based on my last notes on the associated issue - https://github.com/DataDog/datadog-cloudformation-resources/issues/80#issuecomment-729845899


2024-10-24_01-35-04_master-next_python3-botocore

Automatically created.

Successfully created backport PR for kirkstone-next:

#10154

Successfully created backport PR for scarthgap-next:

#10155

Successfully created backport PR for styhead-next:

#10156


The number of trainable parameters in EZ-CLIP(L/14)

Hello,
I'm interested in the result of EZ-CLIP(L/14) and I would like to inquire about the number of trainable parameters it has. I've been exploring its amount of trainable parameters, but I couldn't find this specific detail in the documentation or paper.
Could you provide insight into the total number of trainable parameters in the EZ-CLIP(L/14) model?

Lines 120 to 127 in train.py show you how to get the number of params.

@siatheindochinese Thanks, I'll check myself.


yaml file

Hi Yangyi,
Thanks for your excellent work. I wonder where I can find the tech_texture_export.yaml

Hi, thanks for you feedback! I have uploaded this yaml, or you can just set save_uv: true in tech_texture.yaml.


docker-redis-cluster fails to start up (partially)

docker-redis-cluster is failing to boot up consistently on a linux machine (docker 18.06.0-ce); we're also seeing intermittent errors on mac machines (18.06.1-ce-mac73). Specifically, the cluster seems to come up but only cover about a third of the expected slots.
docker-compose.yml
redis_sessions:
  dns: <IP_ADDRESS>
  image: grokzen/redis-cluster:4.0.9
  environment:
    CLUSTER_ONLY: 'true'

beginning docker-compose logs from failing linux box
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
>>> Creating cluster
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
:7000
:7001
:7002
Adding replica :7004 to :7000
Adding replica :7005 to :7001
Adding replica :7003 to :7002
>>> Trying to optimize slaves allocation for anti-affinity
[WARNING] Some slaves are in the same host as their master
M: 55ce20d0ae2671c67f0108044e3f89ac72fa2d7a :7000
   slots:0-5460 (5461 slots) master
M: 6c6565c2a52c289e64363f44a28c1e0ff7980ba6 :7001
   slots:5461-10922 (5462 slots) master
M:<PHONE_NUMBER>f829dc14bf263132ca0066e94991e5 :7002
   slots:10923-16383 (5461 slots) master
S: 49ed982815367407e0c4320867b8b74d2227a0e2 :7003
   replicates<PHONE_NUMBER>f829dc14bf263132ca0066e94991e5
S: c17fa5d257784134f088c2e6eafde59c79e6a49e :7004
   replicates 55ce20d0ae2671c67f0108044e3f89ac72fa2d7a
S: 45e3c71df75b0d9fabbc8d9c15f122df435721b0 :7005
   replicates 6c6565c2a52c289e64363f44a28c1e0ff7980ba6
/var/lib/gems/2.1.0/gems/redis-3.3.3/lib/redis/client.rb:121:in `call': ERR Invalid node address specified: :7000 (Redis::CommandError)
  from /var/lib/gems/2.1.0/gems/redis-3.3.3/lib/redis.rb:2705:in `block in method_missing'
  from /var/lib/gems/2.1.0/gems/redis-3.3.3/lib/redis.rb:58:in `block in synchronize'
  from /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
  from /var/lib/gems/2.1.0/gems/redis-3.3.3/lib/redis.rb:58:in `synchronize'
  from /var/lib/gems/2.1.0/gems/redis-3.3.3/lib/redis.rb:2704:in `method_missing'
  from /redis/src/redis-trib.rb:941:in `block in join_cluster'
  from /redis/src/redis-trib.rb:939:in `each'
  from /redis/src/redis-trib.rb:939:in `join_cluster'
  from /redis/src/redis-trib.rb:1431:in `create_cluster_cmd'
  from /redis/src/redis-trib.rb:1830:in `<main>'
Can I set the above configuration? (type 'yes' to accept): >>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
==> /var/log/supervisor/redis-1.log <==
43:C 18 Oct 17:47:45.690 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=43, just started
43:C 18 Oct 17:47:45.690 # Configuration loaded
43:M 18 Oct 17:47:45.691 * No cluster configuration found, I'm 55ce20d0ae2671c67f0108044e3f89ac72fa2d7a
43:M 18 Oct 17:47:45.696 * Running mode=cluster, port=7000.
43:M 18 Oct 17:47:45.696 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
43:M 18 Oct 17:47:45.696 # Server initialized
43:M 18 Oct 17:47:45.696 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
43:M 18 Oct 17:47:45.696 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create laten...

I suspect the key is ERR Invalid node address specified: :7000 (Redis::CommandError). On a working mac box, this error doesn't show up, and CLUSTER MEET has additional output after it detailing the different nodes joining the cluster.
This seems likely to be an issue with how we've configured our container. I did try setting REDIS_CLUSTER_IP=<IP_ADDRESS> in docker-compose for the linux user and it did not resolve the issue.

@melinath I think i might have an idea what the issues could be. Not long ago there was discovered an issue with how IP addresses for the cluster was discovered in the scripts that populate supervisord to run the redis-server services. It was updated in this comimt https://github.com/Grokzen/docker-redis-cluster/commit/423a0e4ff5473ca2f84d0107ba2cbc13491c2e1a to use a better solution. I would suggest you try to update either your fork/clone to use the new solution. I guess that you probably have a much later version of the upstream image redis:3.2 on your system that uses a later version of the OS it is running on. When we found out about the issue, i did not see the issue on my local machine as i had an very old version of the redis:3.2 tag so the old solution of looking up the IP worked, but when i pulled home the latest version of the upstream image, it broke and i added the above mentioned commit. My theory is that you have the latest version of the redis:3.2 image, but an older version of the code from this repo that fails.

#52 for reference

Thanks, I'll have folks try that as a solution and get back to you about whether it works.

@melinath Any update on this issue?

I'm not sure it may relate to this issue, but docker-compose down, then up again will work.

exactly, docker-compose down and up resolve the issue, but it also flush all data.
If we incidentally restart the docker, it can not work correctly again

@jindov The data preservation is not part of this container and git-repo. It is intended that it will flush the data and not preserv it between runs.

The mentioned PR above is now merged to remove the data from the last run when restarting the container.

Closing due to inactivity. If issue persist or you find a new issue, please open up a new issue here on Github.


otp_secret is not being saved for preexisting data

I have a User table that has preexisting data, and I start using otp-jwt recently.
It is not working at the beginning because otp_secret column is always empty for preexisting User record
The active record does give the User record a default otp_secret
https://github.com/stas/otp-jwt/blob/37ca55c9b4db9539432b19534551b023d27f226f/lib/otp/active_record.rb#L79-L81
My workaround is to go through each user record and save the default otp_secret
User.all.each do |u|
  u.save()
end

Not sure whether we can make it better by updating the documentation, or always save the default secret if there are otp_secret column is empty

@yininge, thanks for reporting this, you're right, the otp_secret values need to be stored first.
I like the documentation suggestion. If you have time, I'll be happy to merge an update for the readme, if not, I'll try to do it in the next days.
:bowing_man:

Closed as part of #2


Pin karma, karma-mocha dev dependencies

CC @ladanazita @anoonan @ccnixon

Codecov Report

Merging #22 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #22   +/-   ##
======================================
  Coverage    99.2%   99.2%
======================================
  Files           1       1
  Lines         126     126
======================================
  Hits          125     125
  Misses          1       1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 96c770b...9630847. Read the comment docs.


Complete the sample page

Option for toast click handler
Timer settings for the fade-in, fade-out and visible states

Done in version 0.3.0


Restart of Statefulset deletes data

Hello Team,
This is a great work. I am using MongoDB sidecar with Statefulsets but when I delete Statefulsets and create again it deletes the databases which we created. I am using local hostpath storage. This should continue using existing replica config and databases instead of starting afresh cluster. Am I missing any config to handle this issue?
Thanks
Asif J.

@asifhj if you change the set name then you get new volume then the data is lost

@cvallance Any updates on this? If I restart the kubernetes workers, on restart the sidecar creates a new replicaset instead of using the existing one.


Add Enum instead of String type for Events and States

Is it a big deal to change types for events and states to enums? So it will be more consistent to work with framework.

I agree that Enums are more appropriate for defining a finite set of values or states.  However, I chose to deal with Strings because the "state" values are used a keys to hashsets and are updated directly in the database via various ORM implementations (hibernate and mongo).  Since String are final classes, hashCode and equals cannot be overriden.  Additionally, persisting Strings to the database vs. Enums is a bit more straightforward.  So I decided to go with Strings because I felt it would cause less problems when integrating StatefulJ with the various db/orm technologies.
Now, I haven't spent much time investigating supporting Enums - if there was a pull request demonstrating that working with Enums vs. Strings wouldn't be problematic, then I'd be happy to consider it.


"Silent Install" isn't silent

To silently install the agent and configure it to report to a workspace in Azure commercial cloud, from the folder you extracted the setup files to type: setup.exe /qn NOAPM=1 ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_AZURE_CLOUD_TYPE=0 OPINSIGHTS_WORKSPACE_ID="<your workspace ID>" OPINSIGHTS_WORKSPACE_KEY="<your workspace key>" AcceptEndUserLicenseAgreement=1
When running this command from the command line it still pops up the installer GUI and blocks until it's clicked. This doesn't seem to be silent and blocks this process from being automated cleanly.

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

ID: 00a00a3e-a0df-7ee5-4733-7231bd7a024f
Version Independent ID: 94361683-e1e7-7e55-6993-86d3c2486a14
Content: Connect Windows computers to Azure Monitor
Content Source: articles/azure-monitor/platform/agent-windows.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@cgordoncarroll - The command-line shown in the article is correct.  Did you replace  and  with the values copied from the workspace you want the agent to report to and excluded the <> symbols?

Yes, I replaced it with the correct values, without the <> symbols. Any way I invoke it from the command line produces the result below (opens the install gui that requires manual interaction).

@cgordoncarroll - When this behavior occurs, it is because the command-line is incorrect.  I just downloaded the agent and tested it myself with the example and reconfirmed it is correct.  It may be that what you are copy and pasting from the browser is including some character or something that is causing your issue.  Copy/paste into Notepad or some other editor of choice, verify the command-line syntax and values are correct, and then paste into command prompt.

Based on the issue and determining it isn't documentation related, suggesting we #please-close.  If the submitter is still having an issue, suggest it is addressed following the support path.  Thanks.


Props defined based on imported interface, generates its type as null instead of Object

Vue version
3.2.37
Link to minimal reproduction
https://sfc.vuejs.org/#eNp9Us1uwyAMfhWLyzaphXuUVqqmHXraHoBLmjgtVfgRkFZTlXefgSzdtJ8Lwtj+fmxubOccv4zIKlaH1isXIWAc3VYapZ31EZ6tdtB7q0EyLlKU6iWTphalg2opiKjd0ESkCKBOdds6l9NDLZYsW7ECvNaN4+dgDVHfUo+cE0GyCvJLestcFV1OMbpQCRH6Ngk4B279UdCN+9FEpZFj0OuDt9eAnoCTQoBJmokoP2V/sTk05riRLNEtloWAfQ97mK2/XNDE4j2+OwzQqwFXcESDnrx04Lx1OQUqkEQzDkOindtvM8BUIB64yCgP2ezCNQbqNhF937QIVxVPyvxOlDleD2dsY2ZZmnbGxhP6wpYnp7oKzKgP6Ml/4buXvxFYKHWYWqqiM8UNIc1A1TfYBaa1JsSsJ8AGOuyVwQxY53P7+PT/x0hjTptNG7Fmpq3Fz1+SZ8U7HgMt7S7+L5Ns+gDiTvl6
Steps to reproduce

Open the SFC playground
Look at the Comp.vue's generated JS
Check the props type

What is expected?
event type should be Object just like anotherEvent.
What is actually happening?
event type is null
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04 LTS 22.04 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 2.35 GB / 15.57 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v16.14.2/bin/yarn
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 101.0.4951.64
  npmPackages:
    vue: ^3.2.37 => 3.2.37

### Any additional comments?

I want to extract props types from TS to JS.

duplicate of #4294


"Bogați" is listed in the drop-down menu

Description:
"Bogați" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Bogați" in the search bar.

Expected results
The location is listed in the drop-down menu as "Bogați, Argeș".

Fixed! Poti sa retestezi


Multiple ligands docking

Hi, when I give Vina-GPU multiple ligands it shows the error "Command line parse error: too many positional options have been specified on the command line".
Is there a way to run with Multiple ligands docking at a time?

Hi, multiple ligands docking with a single command line such as Vina-GPU --ligand=ligand1.pdbqt, ligand2.pdbqt is not supported in current version of Vina-GPU, we will release a multi-ligand docking verison very soon.
For now, you can run multiple command lines for the purpose of multi-ligand docking. You can write Vina-GPU --ligand1.pdbqt and Vina-GPU --ligand2.pdbqt into a bash file like run.sh and bash run.sh.


Review and optimize the theme directory tree

This issue is imported from pivotal - Originaly created at May 1, 2019 by bstrooband
Do we need to move the theming assets (SASS and TS files) out of the material folder?
The material folder is a left over from the previous Grunt based theme solution. This solution has be rebuilt from the ground up, only the folder structure resides. The old theme name can be removed/renamed from the folder structure. Keeping the base folder might be usefull, in order to distinguish between the source files, test and other front-end related tools.
Estimation: 2 - 4h depending on how rigorously we want to restructure the theme structure.

this has been done (Koen Cornelis - Dec 14, 2020)


Update identity to 2.0.0-beta.4 for quantum jobs

Update identity to 2.0.0-beta.4 for @azure/quantum-jobs
Related epic - https://github.com/Azure/azure-sdk-for-js/issues/14581
Instructions:

Replace tenant id. tenantId now can't be an invalid tenantId, so use the recorder's replaceableVariables to set one like 12345678-1234-1234-1234-123456789012.
Ensure the recorder automatically replaces the value for client-request-id on the outgoing requests to a non-variable value. The latest recorder on master should automatically do this, but please verify.
Re-record the NodeJS tests, since MSAL does some more recordings (one of them being that they verify that the Identity endpoint is available, which is something our previous Identity client didn't do).
If you find any issues while upgrading, please report them in this issue.
Reference PR - https://github.com/Azure/azure-sdk-for-js/pull/15704 and https://github.com/Azure/azure-sdk-for-js/pull/15654

Code complete with PR https://github.com/Azure/azure-sdk-for-js/pull/15801


Fail to export image

Hi,
First thanks for the great work!
Just I encountered this issue when I tried to export atomic block type (image), but finally located the cause of this problem:
// draft-js-export-html/src/stateToHTML.js
renderBlockContent(block: ContentBlock): string {
  ...
  return entityPieces.map(([entityKey, stylePieces]) => {
      let content = stylePieces.map(([text, style]) => {
      ...
      let entity = entityKey ? Entity.get(entityKey) : null;
      let entityType = (entity == null) ? null : entity.getType();
      // entity.getType() returns downcased 'image'
      if (entityType != null && entityType === ENTITY_TYPE.LINK) {
        ...
      } else if (entityType != null && entityType === ENTITY_TYPE.IMAGE) {
        // Did not enter this block since entityType is downcased 'image' while ENTITY_TYPE.IMAGE returns uppercased 'IMAGE'.
        // Use entity.getType().toUpperCase() instead shall fix it
        ...
      } else {
        return content;
      }
    }).join('');

Hope this can be patched asap :)

also found this. Can we have a fix?

I feel like this is an issue with whatever package is storing image with lowercase entityType. But I'm happy to patch our source to account for this case.
Could you give me some detail on what code is creating the entity?

This is now patched. A new version has been published to npm.


Added support for custom reporters

There's currently no way to use custom reporters through gulp-istanbul. The instance of istanbul inside the gulp plugin seems to be different from the one outside the plugin, so it's not possible to register custom reporters in gulp tasks.
I added the functionality to do this, and updated tests and docs.

Updated

LGTM, thanks!

BTW, is there any documentation on writing custom reporters for Istanbul?

Not that I've found, but you can make one quite easily using one of the existing reporters as a guide:
https://github.com/gotwarlost/istanbul/tree/master/lib/report


OSX service installation stores credentials in plaintext

If you install the agent as a service on OSX, the generated plist file contains the credentials in plaintext. It seems like a better approach might be to use the keychain to store the password/token and then the agent could retrieve the password from the keychain at runtime.

dupe of #40