NullPointException when building StsClient with overrideEndpoint

Hi team,
I got the following error when connecting Kafka with IAM authentication by using version 2.1.0
...
Caused by: org.apache.kafka.common.KafkaException: java.lang.NullPointerException: The URI scheme of endpointOverride must not be null.
  at org.apache.kafka.common.network.SaslChannelBuilder.configure(SaslChannelBuilder.java:184)
  at org.apache.kafka.common.network.ChannelBuilders.create(ChannelBuilders.java:192)
  at org.apache.kafka.common.network.ChannelBuilders.clientChannelBuilder(ChannelBuilders.java:81)
  at org.apache.kafka.clients.ClientUtils.createChannelBuilder(ClientUtils.java:117)
  at org.apache.kafka.clients.ClientUtils.createNetworkClient(ClientUtils.java:217)
  ... 31 common frames omitted
Caused by: java.lang.NullPointerException: The URI scheme of endpointOverride must not be null.
  at software.amazon.awssdk.utils.Validate.paramNotNull(Validate.java:156)
  at software.amazon.awssdk.core.client.builder.SdkDefaultClientBuilder.endpointOverride(SdkDefaultClientBuilder.java:502)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider$ProviderBuilder.getStsClientBuilder(MSKCredentialProvider.java:289)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider$ProviderBuilder.createSTSRoleCredentialProvider(MSKCredentialProvider.java:342)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider$ProviderBuilder.lambda$getStsRoleProvider$4(MSKCredentialProvider.java:330)
  at java.base/java.util.Optional.map(Optional.java:260)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider$ProviderBuilder.getStsRoleProvider(MSKCredentialProvider.java:307)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider$ProviderBuilder.getProviders(MSKCredentialProvider.java:254)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider.<init>(MSKCredentialProvider.java:108)
  at software.amazon.msk.auth.iam.internals.MSKCredentialProvider.<init>(MSKCredentialProvider.java:104)
  at software.amazon.msk.auth.iam.IAMClientCallbackHandler.lambda$configure$1(IAMClientCallbackHandler.java:54)
  at java.base/java.util.Optional.map(Optional.java:260)
  at software.amazon.msk.auth.iam.IAMClientCallbackHandler.configure(IAMClientCallbackHandler.java:54)
  at org.apache.kafka.common.network.SaslChannelBuilder.configure(SaslChannelBuilder.java:151)
  ... 35 common frames omitted

I used the below config for the connection :-
security.protocol = SASL_SSL sasl.mechanism = AWS_MSK_IAM sasl.jaas.config = software.amazon.msk.auth.iam.IAMLoginModule required  awsRoleArn=fake-role-arn awsStsRegion=ap-southeast-1; sasl.client.callback.handler.class = software.amazon.msk.auth.iam.IAMClientCallbackHandler

It looks like if awsStsRegion not equal to aws-global, will create the override endpoint with URI.create("sts." + stsRegion + ".amazonaws.com"), and this will cause the NullPointException at at software.amazon.awssdk.utils.Validate.paramNotNull(Validate.java:156) because the override endpoint have no https:// prefix.
Could someone please help to look at this issue?

Here is the PR to fix it, it will needs a maintainer review/merge/publish : https://github.com/aws/aws-msk-iam-auth/pull/166

Here is the PR to fix it, it will needs a maintainer review/merge/publish : #166

Great, thanks a lot!

Is this issue a regression? Is there any older version of aws-msk-iam-auth where it was working? We are currently stuck because of this. Any workarounds are appreciated.

Is this issue a regression? Is there any older version of aws-msk-iam-auth where it was working? We are currently stuck because of this. Any workarounds are appreciated.

@kamlakant Yes, it is coming from SDK V2 migration, with 2.0.x you should not have the problem

I´m having this problem with Amazon MSK when using the software.amazon.msk.auth.iam.IAMClientCallbackHandler
someone could help on this?

I´m having this problem with Amazon MSK when using the software.amazon.msk.auth.iam.IAMClientCallbackHandler someone could help on this?

You can use the 2.0.x instead of 2.1.x until a maintainer publish the fix

I´m having this problem with Amazon MSK when using the software.amazon.msk.auth.iam.IAMClientCallbackHandler someone could help on this?

@tjmatosplanet  You can use the 2.0.x instead of 2.1.x until a maintainer publish the fix

Any news here?

@NikolayMetchev The fix is included inside the last version (2.2.0), the problem should be no more here.
@sidyag I think you can close the issue

Closing the issue.


Some private, new, static, and public reported as error

Thanks for reporting! It's a known bug. But I found it very hard to fix.

Hi, I have tried to fix it in ab251cb1c033e8e0045bbee7797f4be328923f43

@HerringtonDarkholme I'm still getting the same error highlighting :(
Interestingly, if I put the private $$popoverInits property all on one line, the highlighting appears as it should.

So is this perhaps a line length setting that needs to be configured for highlighting in yats?

You have to put them in one line when you both have type annotation and variable initialization.
https://github.com/HerringtonDarkholme/yats.vim/blob/master/syntax/basic/class.vim#L58-L61
But I think it might be fixable.

@indiesquidge  Can you try 92c5edd7e0edff41ab95b1dfcf618949a2e49a3d? It might be fixed.

@HerringtonDarkholme that did it! Thank you so much, I appreciate your quick responses and help on getting this fixed :)

@HerringtonDarkholme bad news, there are still cases when the syntax gets all wacky :(

Here's another

I can fix it by not using an implicit return

But implicit returns are a pretty core feature of arrow functions in both ES6 and TypeScript, so it seems fitting for us to get it fixed.
(param1, param2, …, paramN) => { statements }
(param1, param2, …, paramN) => expression
         // equivalent to:  => { return expression; }

// Parentheses are optional when there's only one parameter:
(singleParam) => { statements }
singleParam => { statements }

// A function with no parameters requires parentheses or an underscore:
() => { statements }
_ => { statements }

The second example is hard to fix. As pointed out in https://github.com/HerringtonDarkholme/yats.vim/issues/5
You can bypass the first situation by new Map<string, EvoDropDownControl>()
Vim's syntax highlighting is not powerful enough to describe all language construct (not only TS, but also other languages.)
I don't expect yats can be 100% correct, but it can cover a lot of common usage.

Looks like typescript-vim implements it.

Perhaps we can find a way to take their implementation. I will do some digging.

No it does not.
typescript-vim just skips some highlight semantic. So it make less error too.
For example, typescript-vim does not highlight argument type annotation. I also suspect it just highlight private keyword in more broad situation(say, in a method block, in non class block).
yats' highlight is richer, so it is more error-prone. I'm wondering if this is a good approach, especially in vimscript.

Or the simplest way to fix all error highlight is just removing those error detection highlighting. After all, typescript needs to be compiled.

You are correct that typescript-vim picks up on keywords and methods, but not on argument types (i.e. the highlighting is based on words themselves rather than their context). I prefer your plugin more since it does offer a wider, more colorful range of highlighting. However, typescript-vim doesn't show error highlighting where it shouldn't , and I haven't come across a case where they syntax will blow up on a line error.
I think there is a balance between how "rich" a syntax highlighting plugin is and how it is able to handle the plethora of corner cases without messing subsequent lines.


HTTPS connects

By company uses a confluence server with a https which uses a internal CA.
How do i get 'mark' too connect too the https and work ? Other words how do i add a ca.crt ?

Hi,
you can solve this problem on the system level by adding your self-signed certificate into the pool of trusted certificates
On Ubuntu you can do it like that: https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu
On Arch Linux you can just call trust anchor and pass the path to certificate: https://unix.stackexchange.com/questions/373492/installing-certificates-on-arch

I got it working, thanks

how to use .p12 file ?

@gongzili456 I don't know how to use it with mark. But one thing I'd point is that mark doesn't implement any SSL communication itself, it uses the same ways as other programs, so you just need to install it into the system somehow.


[REVIEW] - [issue-69] - Omit checks for magic-wormhole-relay temporarily

Description of PR
Relates to:  https://github.com/NixOS/nixpkgs/issues/164775
There is an existing issues around daily build, see: https://github.com/Nebulaworks/nix-garage/actions/runs/2385446134
Previous Behavior

Daily builds against nixpkgs master are failing due to twisted dropin.cache conflicts

New Behavior

Disable twisted test until upstream twisted issues with dropin.cache

Tests

Able to build wormhole img successfully
Echo master sha during the workflow: Utilizing sha: d113661156581c835df4fe5521ffc64128772f18
Triggering a dispatch of the daily workflow works as expected
Will also trigger a workflow via publish command (post-approval)

publish

The following docker images:
{ "Name": "docker.io/nebulaworks/ansible-lint", "Digest": "sha256:8d98adef2d3d7f9f6705d4333b74b65d462bfc31cf3ca8b0d353563242f2ad15", "RepoTags": [ "1lj51767l00nnaa9fh8200bmjbxdg2gf", "4yfc0d6fdan57ki1bjq3jbjqmppkwapp", "7qsq9l65llliyry1pga9j1fvnbf08yhx", "837q5ya631p2cw7lllvm2hgpx0v11pqy", "a4brdxng1h1895c4q5l8qvnlvrpyl3mc", "b8zd0f2nnnllxgkigmd3lxb9i938n33g", "cx11fsg47srrbpg41x1kx9zd1ymyqmgr", "gr7cgqvghwcpkkj7br0h3wbyk0hg5cqw", "hqscjlf634xjjgbg2fl7lzxszn7wgb6b", "jjvls57k805vip35hdn9ci97i2wlg7m9", "s22k2b0fw9bpcg6xnwfjc13qlxyngwhl", "wgal6rmrg4smiavzpykf8q70lddbsjiz" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,curl:7.82.0,git:2.35.3,gnumake:4.3,jq:1.6,nss-cacert:3.77,python3:3.10.4-env", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:be87f80b459c6cf1c63a5f04226c26f2d0a4392a08103a52dd9ea136ae783ac6" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt" ] } { "Name": "docker.io/nebulaworks/awsutils", "Digest": "sha256:0589df2c6c5593f088528a7c9dbb0921593684b6c3688c3af1c6f08a97d5fcd1", "RepoTags": [ "062y3vxhs7hap0v279gy1wrcnmmnngy4", "0afjz2x6jzlqbyp6hlsn7xx1j4v595xj", "0q6n72i9f6w35qg70a8fddnh57jr25yb", "0wrw13hq33i9lvliwgrilimblm1by6ga", "1hx4387bjv85cs424znxr9fpbdbm8djk", "43pax9ygdpviwka1lvqkvsxk3qlkg32i", "4iyc3wm1kjz9lwqwsgvjz8g78hdgxc7p", "4yzrc2fjyajqaihgn3jycfjjsrwrdb7z", "548x109glkycnlfpbfa17skqy252d7by", "5cnip2b81k71qbap8493mmvfp02fk6wh", "5dq3sxqy6ql24adppr4abllkpq51ai25", "7ydhw282rks4v1pv3si8iv0cvaamypw5", "9jfmk9gq677qhks1nagk6kagr21b80zh", "9mz9x2m35npczsjgxznwiwlzj85ij9hq", "a2x2gakpv9acj1zp6q4cfk0x34kakh84", "a5d61h3nvmigz60bins2pgwsq7hx63h1", "a5kccnv7dvfjg6p5z0kvv8f4gi8i6cln", "aajc2d2i99cd622pzjyc013z86gckiq8", "axjz9vl56z0lm8jwzlri7cb80zpiiv3j", "b2brn67ymrvbi8izvxvayi4bn4adwa27", "b2xpdz7r5fdlnyyalsxlzncwlvy1gh6m", "bcwvjifcwgd7mzn8gwx86xlnfl5mf030", "br0g08h90amarmcsl8ic7iji74wfzwhk", "c3skllz0pvp6a78nf3c4fck7xcg1yxq5", "c4vyb1p0lch8czxncl0nq685wick8fnd", "dz783iaashdby6phqf9pcydxsw1bbjq0", "f9lc1bvrwz8wbjhccp6dyg2yvzy56npg", "fd6mchdar3ja13ph0jp1s8pnw7ixfahk", "g44npkrgrh2qj2y9j1a9n6frcyd2j45z", "gv99dxfp8hy5w9dl16p9wc7km3mg2n1f", "h952m39vshzpihy6cgmp17gjszqq3vks", "hbqmiwillbddpzdjdl0v8y5h1xxy1bwx", "hc1r0zhhmwdvz0ygyyypq0kav5yw6zfn", "hx1a61jwx4r2crri7iph7ygd19gbqab5", "ib0v6zkv2qqaidwda7sp64pa0jfc0vbs", "k2c75rki35d8z8giwynras8nwrsr1l0z", "k3i9bp4w5ndn7ai6cylbimxybqln4nrc", "kbc4fdqiaiwgbiwxf7gbd123gf01ph2z", "kl55657f4yfpi6b8kj4f1vwgk3jdhvza", "l4vf8g6g8wfahhhc7c1m90sm850s2sf2", "m11a8hm9d6g801l9mdfzsc9n17nzni3g", "mzqlmhc5gl3h3k10bn1l0ghr204n0pqv", "n2m55acawpn7y06h6ifjbyzmn9n44bhy", "nzbazzwdq9vy9rg10jcp2dvc3fs3n1bp", "pbjgfkmi0wqiwd1flzwm7rz8snd50j36", "rrcibw1y1wxbjsjwwpgiw1qmxg7x7a7n", "rss9pb0cmnbhl49in406s3i7hiy466ps", "sg814n929qffnj1xd0637knpgaffzzpf", "sjr0mavplaws1dlxy3vr2880v0jkhh3x", "sy7z5ylf9j3jrbhgd8kcpnnndbch3v4j", "v0z5n26qg181476nkff5licn4p7s1jcn", "v7dw7988kyhzsgjzxaiybhk0a9wsbm2g", "vbp6wk6y3gn143g5sfsfgpih8shr2sml", "w4cwy90aa2b1rrf9nqd5qjcflrjh0129", "xaacyvsd2q0z4yz111zrj8y0za422gh9", "yfws0rvz76xkiq0yid7cqcg0zi98ab1y", "ynizhwjmd25jf0np5wi4wq34fbd6n9db", "zc6w4ys5ka740i167bd0qp6v8f63dp0i" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "awscli:1.22.88,bash:5.1,coreutils:9.0,curl:7.82.0,git-lfs:3.1.4,git:2.35.3,gnutar:1.34,gzip:1.12,jq:1.6,nss-cacert:3.77", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:31d3904ee778486ecba2e05b987150e8f12d0d942cd46332a1fface881e63951" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt" ] } { "Name": "docker.io/nebulaworks/flasksample", "Digest": "sha256:96c7fcca49c569e1bdb9d43270324b3e23747adc2f398f3dbe2099a19e2df0e8", "RepoTags": [ "3hnryiq8q9hy0fm8cfzm92d0yj8anybk", "46436y8vy5dm1pcznyqnbjjsbcqfsa13", "54p4a6ri41prjrp9w9wni8v0bigs8j60", "5dki2i2pwniw5y1jhfrzp6qhsnh3b8nb", "5fi5d6s9qb0ayfxvd4czrwvrk0jv9q1r", "65j7jsrql5qicfadj3dqbinyaaisi5sg", "68rag50ayc9gsi7n4bwdbjq0ah2pcs0a", "6q1rg8nbx5yzhrs8y16l8czmy5xsqncc", "8qzz162pgn7nhbic9g0vw209fs01n6s6", "8wp5sb35h86bygxchcv9cgcsxzh2dc5p", "96j0fwid588a3rdawijlmlswxbfhfl5q", "9dqy2plqw2n9nynz449adx8rd2633a16", "9m2k44fp1v7nvijz8mz7nkac10fs8wgv", "aggzwxjm6v6jfbjbwn1z0fvfp0xiqid6", "biayqv0sg5v36dvnl7yh6gg941gl0ba6", "c34ssc86npknkb6ppmfi4b9zvkxax4a8", "c44zddyvxg5b9qikb28gva9cznsys502", "d7m3af9b424fnb0niqs1s9428vqn7v76", "fgi5b0x05qfav9cg9ly8mn6pz7a2gibc", "fwwz8b6jm0q8m2w0lgw68mila23r08cp", "iiij8fj3jib4qyf6dzm64a9c79wrhk71", "jb78a05hixi8d08zlv5sg6ml3qsfzisd", "jd35ng454lzbzychimd6pcs0sx8w66ng", "jg3sxqk5msyl62asq4252m5faapqq0k7", "jy7q8lrajn09kg58psj6n3hmkj5ga9k4", "ka0wy2kixsvrlaiglz1l0cr76y5dfnam", "kxhh6w3c8fgn4sxw90j573vc2p4imnzh", "kxhq2jcijnkp8qhnlhy47023jcd0rj52", "lb5vs7x46v4skzigvkamsw1121v87gfh", "lrpkr89z5qgb9sacgy266j3yxgrxi80a", "mk0ldb79sxm75wy99zk195dngl3dk5k0", "nyqmq3dsyzgm84ifcv29f4xaa2g60mnr", "p028d080qwsa8mh0lzfm1vvdh1kw7a8m", "rzk3f7a3w0ww8rlzi3401z3bz4mkmrn4", "vq9wsp3l0yx3vmjazfjf7qmv5952pik9", "wq3kagq6zqjfklx4y1s12gqp8fhd32sk", "xsi7aqn2j1bri2wkgc1zzk159m2dib3f", "yi1b05aik0iqjzpxqyy8nfzhy242s2y7", "z0qrlc5rpybi69hljcvdx3hlzac6f3g3", "zzpm4r45shaicn75lgvlnhxfqk3rgm9x" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,flasksample:0.1.0", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:35a4a7f33dc06ab38997070fbaaa563e4f9eb19b9663f36c61b97592f452f347" ], "Env": [] } { "Name": "docker.io/nebulaworks/helmsman-aws", "Digest": "sha256:ee3e8ece734b5937a23a3f008909688e12c6134e7704cbf99621d5508e837bbb", "RepoTags": [ "017agn5z2mr7pacaf09m8icbqwa5g01c", "0r4rskk3b5han0zzncj67sjhkm7lip1w", "144mz9zbhrcip75cyqnp4wac8pz3fxdi", "1bhgpxkhzfc42i0dgxqxaw6bd2lhhap0", "2i051yfnpypb2dljzdbxdz04h3a5qdqc", "2lzm28bwssv9apnf83sxgxwdfymmxm8g", "2vil2iz4gz0lmcqsg92kxylhh4mds6jv", "2w05w5i610g4jqnhcbhv1ayd81gxysds", "30q2z6wbcbn88851pyyyns0bn5km4nwm", "36na3i0psj09247r3mswgf2czazg959m", "37yxlxhpyp3ai1xs464ldif2gmj3yyjr", "3dz3i6lqdnigfnq7mai6vccnmf4fyjbx", "3ml4yvayn282z32hpr50sl7ag5kdca72", "42ygsh6v9ns61hn7yrrvjrpa7dz0ypak", "4szd9xflnkl3ab9h0mzjkfrybzps3hs4", "4x6ah6c8mgyn20awa9xrq16cw1yz9d4s", "52ifj8li3wjpraps049zyq67zqvw7m04", "54hq16h32rh3g6nbxmf755d40mvq30rg", "55836qcrmhfrfvn467n9dcrkpnq033ay", "686gs4mwpvsisq9c45n0f19wmp1zwada", "72rs42ar65syxrgq6w0qyv98n97zkr6n", "787wzh711cg6l2s92vn5rlnkw24jslyd", "7ar2sigpxxyll06yvgan428qn74k0vqm", "7hl8p275d7f3gcnam52s7hg1d307a2ik", "7mc83swh71lgji4ar8fz8a1n13zq934p", "7vc5g5g4m6wvg75s527h5mfimixh1yl0", "91hn17cblaiv1wb26vvwz05m3787c4zv", "9xnr8m6mj35mh6fwxx1nsxp11arvm1sh", "a5kn44776qgdm8dgjmlym4z79qhnm6mn", "ajgcdsjx2hy33jgrvgqxkjfv28bazfz1", "axk5j5bhv0sv9ys1xj4bmhc34kfw5jkn", "bbjyib4li8ipq2yvyak79ck7kw9k2dkx", "cr9n83qbmcxkll790qhsmqk3x4733zdv", "d5vzm6xvcdv93dl327shyc5k8af6vh5f", "fh5ba96qrhkkgilk03srysz5qm7kg0j8", "g9mxjnw3vmxnzc14hbyl5rvjmhrkzdcb", "h6a3l42pl14r96j5y1kcmwf5b4g8d5rg", "hwjzmzm50q20diz32nlmva91cpjjy0gn", "ibx9pd0yzvspf6gczmdmmhmam9sr25wr", "idrymiiylkvrcldbavjf4sjyscvkndkw", "ilpcmfgzgzskzshyd9j8rpxvrs3slxcc", "k345a553cr4aicxcl9l7ns2rjzhiv62v", "k5kcp1pk20jfx24cvjbnhf0h5ax25hxh", "knha5b2p70xhrqyy5awl8djdzisn2sal", "l0mz1yxw70ab4kmqnvjbcxklm088q7l8", "lf015xyadsq38mvllc2cvb0n9dfdj6zc", "lnv4scg68mn4ambxibzq7rswrfapcnrk", "lpsiwff3za9ma0hsvwz9kyvsc8han1nc", "m4p9y2j9jwvrlrzcyk0s7q5b1qh3i4xc", "m9kvdhzskjmvd6lbrmx9n195cm08amgq", "mpgikzzyqmx0x97jq9iwmf7r9xvm7x38", "nlpym68q25fyyzdzq7xd2gcbibbwmfyb", "paks7yd7laypwmpg3i3mbvw937hdgdnc", "pbj9q2qyw511wfy18g8lz9jw2mpc5qvw", "pfvnzcg5m26m0bd6cj4v6g7j6qndi2m0", "rz9fgbx5kvzid11v516zk8l3x31bxph0", "s9nhvzqn3acjcfinaqlsd07hnc7bkm0i", "saj7j4vdgy3infrgn865xlbb5n73lsd9", "sb47bkwd854ws9dc4gzsvnln06pidxjf", "sgv2bi85zdbbznixhpck8w5c29np1w87", "v4mlmsr2lpvjh3pykpg3b3755zsp5yip", "v7jsvzj6gr3p02s2lp36r3i7rlrij76w", "vibjzpbdqxyfxppd37sy8sskbn9knd10", "w01q6nzkxlxa2w0kiai4spxc17mq7a04", "xdahy9hh3fnsws09w7ksi65d27kra0i1", "xym39zji91ga5rbw6p8xbwy5dcbizbn3", "zmz5fxsfpmjdf28mmknxaqwp9ig4kyxa" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "awscli:1.22.88,bash:5.1,coreutils:9.0,helm:3.8.2,helmsman:3.8.1,jq:1.6,kubectl:1.23.5,nss-cacert:3.77", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:4e0588d0d53360e0f3a00dbd1cb817a87408324088e8d47660ab3135d1aa9982" ], "Env": [ "PATH=/bin/", "HELM_PLUGINS=/share/helm/plugins/" ] } /nix/store/afm6v1gw9rk0ihga76gcpvkjcy8y3qk5-docker-image-magic-wormhole-mailbox.tar.gz Getting image source signatures Copying blob sha256:84adf2f6c1d77c5eab4eda9671488d2af5645ba25768ea6c63d2864867dedf33 Copying config sha256:995c05cda04f2e7382561191c9001a892804768817d4c44167329f5f4f5906fe Writing manifest to image destination Storing signatures { "Name": "docker.io/nebulaworks/nwi-pr-utils", "Digest": "sha256:0779d324d703dd93894735c1e9efcc0aed46e79f82e65a76f3f117486fe4c667", "RepoTags": [ "09pymw41x3d1zar4i46pbdjlhf51nc7i", "1qcv3ddhn173p8zzqpps4bgvi96c73gc", "1vvy146w2xc2ia145kn88blwyg9303zi", "4ri9qfysqcry3zzjr1nmfwb0zalfl0li", "5x5r35ws5h8r4pig32s80hw6qfc1wvxw", "6n087vdgnm05ipil8zkrj1ynsw6l1lqd", "7w34va7ghlk4x5pj8h9f6xkb1xq60vlg", "8da78vfisd4431v063f59ybss8n6cgr2", "8glawain89wy3sp6i95ys7l7nyrsw38s", "8s3mm159mxlsgwa57fdfaarcm96m0z1z", "9gga1vwcxr09i95wxzsg0chmswdvsh84", "9n4k95fhxsy144rbnls6biyi74jpiz1m", "9w9qy1d813rxr9kdw4hvbzwjmdswycnp", "af48r4y9qz0rys0z2ph8av42hvg9ffx2", "c8a0x9ddsnb05nv16j8sj8ha4n3giq5h", "ciaif8kc0i1pqwcfpndgb88jpafw65cb", "f0gah5pqksnhf4v79yaf6wzqnf80bmk7", "f4p6mkakbl58807jrhwsbl5p34xr1jmw", "haqgpad651zq3f94zgky4ydz1lw4j93v", "hpaj9r73fl3c65j21lhc2dfpb4x61lrr", "hqg743d0ply68g926p4q71gmzmrzbd84", "hz31r35m48i4sfr43zmnq1xi7ph8cjc6", "imnysry78shjwnaznjlmjhnixrgkhd07", "iqaqf4a5cq85f9xh22dr2d2jxl1bh27a", "jff36955m87va40f8cfzwgwb04gv0yig", "jnd9wmc78n88k1wz6x4rbprwwrh47gbb", "kcg4l097kn841w814d425ar33y4alzsh", "kxfl84j0xyy3xhr0s6ga03xw9y784n5p", "l8azgxbr5xv6if0fa5jraxn61r9if6yq", "ldmmwra6z32jh7bqxp406c5kag8z492k", "lx98kzd4gy5604qhblmx4b8jmywjlf7r", "m6b010vncwjifnjrninllnrs5yvdlsyl", "m84gwswh2k38aif8psvja3mjhxsbp41g", "mkr89zsfj4dbf02b2n124cx6pgh94c9l", "q550kbmhsbm9y7yf5xkg1hghbpl8dgla", "qhf6flqw01v6wwaww9v1jj81k3y995nf", "qw1v97v9pwdhgasd755l33kzh1r1ydss", "r2d3pp1nhczk99084nihchn1rbrakiyf", "w8n8sggdlcaad4cx50jfx5yv1r2z6qvj", "zp9846y8pdd3ydfp8bi170dr4rrprclk" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,tfsec:1.19.0,yamllint:1.26.3", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:cb8109467374f540cac5bff55015d61c50cbfab5e0f5033c08014fb9d91f36f2" ], "Env": [ "PATH=/bin/" ] } { "Name": "docker.io/nebulaworks/pki-validator", "Digest": "sha256:e4593bad42d2ed8411687828e9a71c88019f6da60ff67aecbc06c4b8b3e49065", "RepoTags": [ "0ky9lc8k9cjn8y1yjdrcyjysi4f5mpjn", "12x2y4s04wqd7vzblyknmb4i9wlrbyg7", "171fampm86jhqnb40x2s0n08r4hv55h2", "193ch432hry14dwwgfzw98pr41w36kz6", "2s0sq3h58kpm1gp5sa7xghww5gn9vgaa", "4chfkkzn2pzl98fl56mjfzwwfcccm4dp", "4zdwvwli58ykjiigwqxm6ggwcbivd0ks", "5ydsd6yyfnhilz53bv5f31gwzrpp0yjf", "879vbhnlpb9fihpldnlwd6y2cxh449m7", "8hs2gsf3n1qq8rlg8md4m3571jkddg8g", "a78vqgf0nk9m39f9jz56qcqkz3pg85vi", "bcykjxyzc4wpgfvz7ba4n389vcgls45v", "bsnlb78w0hpzkx4m7ba40lm0qz2212js", "dnvg43r1cpmdjcfphknzgijmg7jx16cn", "fjqp40jq1fvzl1br6mhhr171q27xzm46", "g7hfbpy7vw7xq84zqhqigydyzv60k6s7", "h13qqs6wwmkz9g5hb9ca9hnyzchsp2al", "hg66vz8gd12bc035xaflv9bvyq9xi9yx", "i5h82x58h7qrvcyk2v1gzqwhb6w9kd0s", "ipamimb49hr2xw2l08d1p4r7jg6r5814", "iy254z2954z7zanh9dfbyzw6n00rkych", "jqx100dphlsaqbv9h6abp8ci4a4v7ka5", "kb7qwr49yrsjzvh2kmayga6l0d89cd6d", "kvfqd087z62z3amrvkzpx48l1v0blcdp", "lkr5lv92r9lin6s156x7x005dyikb21n", "lq6c446k04lnv7y5gyrzmq9lign8n265", "pmmsixyc79inwhsifks8vmj53f52i9ph", "pw9il8xx85cgrdszn1vxmv319pyifp72", "qwcky9z36f8q51kd3rjph1fajmgl7d7n", "rhpf73j3qcmzkb5crdjn977iffqd1zqx", "rqs2qm2w6pqkvm8qhg6fpg1ddkjfvyc2", "rwx2sxnrf9b5yyaqyhs28458pzfiw912", "s1l8jmzblv13rnzs9ggsd2xrssalj52a", "v8n2gd8gx7i2hwbmbvpy083gqng3rv4s", "yxdhv9knsflnpfihzksi2m7qix2kircl" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,gawk:5.1.1,gnugrep:3.7,gnumake:4.3,openssl:1.1.1n", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:91f107800fc4b27ddaae5466f0d9d1253b90f6794217cfb6c4cc6c283f602f1f" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt" ] } { "Name": "docker.io/nebulaworks/term-apply", "Digest": "sha256:f24a915f7f6ce73cd903d4ba834baa95eaae21d131d91e0e59b94dc2f0cdcbe0", "RepoTags": [ "3rjls0ixn0q5c0qvaiyd8p296pgrl1jj", "589ykblva4s7mycz50bwfmxkhzg1i2j8", "6b6qszrhrxxkbxixw3hbns8rbck0r1iy", "8gdx02vxik13qygijlhwzy55gw36wkp1", "97a542xvxs9n5czccsh4z7chlrc7zhal", "9akhxf5qhmwkw3ibd7qz08mz6hr6q0vb", "gn3vnccwhwkpicwa0znpvp03sqg98f9b", "gxk9nj760dj16rmrmflym9kwc06phpi5", "jxakhi9b7qk4i49xncflrp6dajbmszja", "k0lg0i9z1p4zf2yk559scvga62bwcmda", "lx6gz40g6xr5wz0yk78bbsp1zlm096hg", "qkmy576gdjx203zxl4sm0xizrdhxiqmw", "srm4d2spzfzljc02dvyjbw8db47g0m9v", "szs31s6f8r4xlj9q6p0hh6fliac6rzz6", "w181ch03lsgd7i0l2lbvrk4rgb14dnx4", "zd3fqn2jb3684pzw68jq27giigh7axaw" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "awscli2:2.5.6,bash:5.1,coreutils:9.0,minio-client:2022-03-17T20-25-06Z,nss-cacert:3.77,term-apply-unstable:2022-05-17", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:eaa14352f9c702667ffa238777a50143f926181281e3e3f78032fbcf69d25f49" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt", "CLICOLOR_FORCE=1", "TA_UPLOAD_DIR=/usr/local/term-apply/resumes", "TA_DATAFILE=/usr/local/term-apply/data/applicants.csv" ] } magic-wormhole-mailbox:afm6v1gw9rk0ihga76gcpvkjcy8y3qk5
have been published on Docker Hub.

@egiffen this ones all ready to go, update the tests section to cover all my findings


ISPN-12565 Converts lifespan and maxidle to seconds

https://issues.redhat.com/browse/ISPN-12565

@wburns if CI is ok wtyt

Changes look good to me. The only question I have is if this is safe to change the returned json? This is only used as of 12.0?

@wburns yes, this was introduced in 12

Integrated into master, thanks @karesti !


ci: depot (attempt 3)

#717  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Separate config params for SCP/SSH options and target host

Currently, the heron.uploader.scp.command.options config value is incorrectly used to build and execute a SCP command, which causes the topology package upload to fail when using the ScpUploader.
A correct scp invocation looks like this: scp <options> <src> <user@host>:<dest>
The current implementation of ScpController formats the command line like this: scp <src> <heron.uploader.scp.command.options>:<dest>
Because scp expects options to be set before specifying the source file, the upload fails if heron.uploader.scp.command.options contains both options and a user@host pair. Note that the documentation gives an incorrect example.
This PR aims to fix this issue by separating the SCP options and user@host pair into two distinct configuration parameters which are then used by the ScpController to format a correct command line.
I'm still unsure whether or not the name connection for the user@host pair is appropriate...

@chgl Thanks for the pull request. Could you update the sample.yaml with the new configurations as well?

how about using destination instead of `connection?
please update sample.yaml
please sign CLA at https://engineering.twitter.com/opensource/cla

Oops, didn't see the sample.yaml. Updated now. @objmagic I signed the CLA before with my GitHub username, just to clarify: do I need to resign for every PR (with the URL)?
I'm not sure how I feel about destination, seems confusing in the context of copying files/scp.

@chgl - if you have signed a CLA before there is no need to sign again.

Looks like you are committing to this code base, first time.

@supunkamburugamuve - everything looks ok?

@kramasamy changes are looking great. thanks @chgl

👍


Please invite me to the GitHub Community Organization

Name
leroy
Discord Username (if applicable)
No response
Additional Context
I found this organization from org list.
I want to grow my skill in development from this organization.

It's great having you contribute to this project
If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

Invitation sent for the GitHub Organisation. Welcome to the community 🎉#
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/jaidevstudio/people
Like this

Tips for practising:
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps

I cannot find the invitation.

sorry for the inconvenience please check agin

I received.
Thanks for the invitation.

Invitation sent for the GitHub Organisation. Welcome to the community 🎉#
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/jaidevstudio/people
Like this

Tips for practising:
Remember contributing to open source is not just about code, its about collaboration, communication and adding value I hope that helps

Make sure follow these steps


Error when flutter  pub global activate flutterpi_tool

When run flutter  pub global activate flutterpi_tool.
Erro happened below:
Failed to build flutterpi_tool:flutterpi_tool:
../../.pub-cache/hosted/pub.flutter-io.cn/flutterpi_tool-0.3.0/lib/src/cache.dart:297:20: Error: The type 'HostPlatform' is not exhaustively matched by the switch cases since it doesn't match 'HostPlatform.windows_arm64'.
 - 'HostPlatform' is from 'package:flutter_tools/src/base/os.dart' ('flutter/packages/flutter_tools/lib/src/base/os.dart').
Try adding a wildcard pattern or cases that match 'HostPlatform.windows_arm64'.
    return switch (host) {

and my flutter doctor is :
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 3.21.0-9.0.pre.26, on macOS 14.2.1 23C71 darwin-x64, locale
    zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[!] Xcode - develop for iOS and macOS (Xcode 15.0)
    ! CocoaPods 1.8.4 out of date (1.13.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that
        responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#updating-cocoapods
      for instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.87.2)
[!] Proxy Configuration
    ! NO_PROXY is not set
[✓] Connected device (2 available)
    ! Error: Browsing on the local area network for iPhone 12 pro . Ensure the device is
      unlocked and attached with a cable or associated with the same local area network as this
      Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

! Doctor found issues in 3 categories.

I had the same problem on Linux
$ flutter pub global activate flutterpi_tool
[...]
Building package executables... (20.1s)
Failed to build flutterpi_tool:flutterpi_tool:
.asdf/installs/flutter/3.19.3-stable/.pub-cache/hosted/pub.dev/flutterpi_tool-0.4.0/lib/src/cache.dart:303:20: Error: Member not found: 'windows_arm64'.
      HostPlatform.windows_arm64 => 'Windows-ARM64',
                   ^^^^^^^^^^^^^
.asdf/installs/flutter/3.19.3-stable/.pub-cache/hosted/pub.dev/flutterpi_tool-0.4.0/lib/src/cache.dart:858:16: Error: The method 'getDirectorySize' isn't defined for the class 'OperatingSystemUtils'.
 - 'OperatingSystemUtils' is from 'package:flutter_tools/src/base/os.dart' ('.asdf/installs/flutter/3.19.3-stable/packages/flutter_tools/lib/src/base/os.dart').
Try correcting the name to the name of an existing method, or defining a method named 'getDirectorySize'.
    return _os.getDirectorySize(directory);
               ^^^^^^^^^^^^^^^^

Doctor:
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.3, on Ubuntu 22.04.4 LTS 6.5.0-35-generic, locale en_US.UTF-8)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] VS Code (version 1.89.1)
[✓] Connected device (2 available)
[✓] Network resources

! Doctor found issues in 2 categories.

@ardera Thanks a lot!


User error does not disappear after new key is entered

Description
Error to enter key -> entered key -> error did not get removed from screen
Steps to reproduce

Create an account
Do not enter any fields and click export
Enter the key field

Additional context

Hedera network
other
Version
0.2.0-alpha.2
Operating system
No response

confirmed issue resolved


Trick LWJGL into thinking that your hardware supports a different resolution?

I own a 3440x1440p monitor and I am looking to run a game (Minecraft) in 2560x1080p in full screen mode to get a performance increase with path-tracing compatible shaders. I currently use the Optifine mod which provides several resolutions to change the game to but none of which are 2560x1080. I scoured through the internet to find a way to accomplish this and I eventually stumbled upon another GitHub issue stating that Minecraft (specifically the Optifine mod) grabs the compatible resolutions from the LWJGL library. Anyway, I'm wondering if there's a way, if any, to add this resolution to the LWJGL library and how exactly to do it.
I'm sorry if this isn't the correct location to ask this, I just wasn't able to access the LWJGL forums as it requires some coding knowledge to register.

LWJGL 3 just uses GLFW to obtain the video modes (if that is what Optifine might be using). And GLFW itself just asks the operating system which video modes it supports and that itself asks the video driver, which in turn asks the display. If your desired resolution does not appear in your display adapter's (or OS'es) display resolution selection dialog, then this is just a solution not supported by your monitor.
There is no way into fooling any part of this chain into thinking that this solution is supported.

Both the Nvidia control panel and Windows display settings allow for the 2560x1080 resolution. When I manually change my monitor to that resolution, Optifine defaults to the closest resolution under 2560x1080 that it supports.
Here is a list of resolutions that Optifine displays even with my resolution at 2560x1080:
https://youtu.be/woQzXFwvkZA

If it helps, here is the direct explanation from the developer:
https://github.com/sp614x/optifine/issues/2147#issuecomment-453281043
Thanks for the response though.

Well, there is not much that can be done here from LWJGL's side. Sadly, Optifine is closed-source, so we can't even see how Optifine uses LWJGL/GLFW exactly and how it might filter out display modes reported by GLFW. I've uploaded a GLFW demo executable that outputs all supported video modes as would LWJGL do: https://www.dropbox.com/s/purgxj04ez6egti/gears.exe?dl=1
If you execute it, it will open a cmd shell and output the video modes as well as render the "gears" demo in a transparent window.

I downloaded the .exe file and ran it. In the cmd shell, it didn't list the 2650x1080 resolution. I'm assuming the problem is that GLFW doesn't recognize the resolution in the first place? Is there anyway we could change that?

I investigated and debugged GLFW a bit further and there is indeed a bug in GLFW causing the resolution 2560 x 1080 to not be reported. The reason is that GLFW checks whether the same resolution is reported more than once.
And it does so by not checking for width and height separately, but by checking for the screen area (which is width x height). And when your monitor reports 1920x1440 and also reports 2560x1080 then only the former will be returned by GLFW (and subsequently by LWJGL3), since width x height in both cases is the same...
I'll report this bug to GLFW.
Functions responsible for this:

https://github.com/glfw/glfw/blob/master/src/win32_monitor.c#L418
https://github.com/glfw/glfw/blob/51bb76c7c3de934b2dd3affcdc297a32e4817835/src/monitor.c#L56-L57

GLFW bug report: https://github.com/glfw/glfw/issues/1555
Thanks for reporting this!

Thanks so much for your help. So all we can really do is wait for the bug to be patched?

Yes.

Okay. Again, thanks. Your help means a lot to me. 👍

I am going to reword this issue and keep it open so we can track the progress of this bug in GLFW and when a new fixed GLFW version is shipped with a new LWJGL3 build.

Thank you @TheJaake for the report and @httpdigest for the investigation! 3.2.3 is being released tomorrow and it would be nice to have this fixed, so I've pushed the change to LWJGL-CI/glfw.

The GLFW issue https://github.com/glfw/glfw/issues/1555 has been fixed now with https://github.com/glfw/glfw/pull/1556 and the change is already integrated in the current LWJGL 3 release. So, closing this now.


Allow logs to go to stdout

At present, logs go to stderr. For Datadog, this means they show up as Errors.
See https://docs.datadoghq.com/agent/docker/log/?tab=containerinstallation (screenshot below).
It would be good to be able to log to stdout natively in descheduler.
descheduler version: 0.22.1
descheduler chart version: 0.22.1

In action:

cc @ingvagabund

Checking https://github.com/kubernetes/klog/blob/main/klog.go there's no option for klog to write into stdout.

@hlascelles how does the datadog consumes the data? Parsing container's stdout/stderr?

Just curious, what are we doing with this: https://github.com/kubernetes-sigs/descheduler/blob/e6314d2/cmd/descheduler/descheduler.go#L32
Which passes to this:
https://github.com/damemi/descheduler/blob/94888e653c6f8d0554f251256cd1dd9eafea4368/cmd/descheduler/app/server.go#L81
Seems like we are trying to specify the output as Stdout, but is that not respected anymore? It seems really odd that klog would not allow stdout

Based on https://github.com/spf13/cobra/blob/master/command.go#L247-L251:
// SetOut sets the destination for usage messages.
// If newOut is nil, os.Stdout is used.
func (c *Command) SetOut(newOut io.Writer) {

So only for the usage text.

@ingvagabund Yes, as I understand it the ageent just streams the STDOUT and STDERR to the Datadog servers.
I have searched their docs (and the agent config) on a way to override the level, but I cannot find a way.

@hlascelles any way to verify the fix in https://github.com/kubernetes-sigs/descheduler/pull/680 by building a container and having the datadog collects the logs?

I will have a look. In the meantime I see that Wordpress docker has the same issue: https://github.com/docker-library/wordpress/issues/311#issuecomment-395514485

I am seeing:
docker build -t descheduler-fix .
=>
Step 6/11 : RUN VERSION=${VERSION} make build.$ARCH
 ---> Running in 2c81f13f89a0
make: *** No rule to make target 'build.'.  Stop.

I was never able to test this because of the build error above, sorry.  I will try the new build.
Also, for the record, here is how (in Datadog) to change any stream with the first char as I,E,W to the correct status:
You will have to add a new Pipeline (go to Logs -> Configuration). Click on add a new pipeline, give it a name and click on create. Next, you will have to click on add processor for this pipeline and select grok parser. Set the following parsing rule:

level_rule %{regex("[IWEiwe]"):level}.*

Click on create button. This should now assign level attribute to your logs. Next, add another processor and select Status Remapper, and type level as the attribute, and click on create.

That is weird, I get the same error running docker build directly. However, running make image (which does a docker build) works for me. @hlascelles could you try make image instead?

for some reason it still reproduces (Datadog user as well) on v0.23.1 and even v0.24.0.

Hey Everyone,
Is there a way to fix this issue from descheduler itself rather than having workaround on the datadog level?
Thank you

I've never found one. I've also found many other k8s utilities work in the same way. I've just added lots of Datadog parsing rules.


Add manageiq/activerecord-virtual_attributes for virtual columns

https://projects.engineering.redhat.com/browse/SSP-844
When creating the icon endpoints to GET the raw image way I inadvertently didn't give the frontend a way to get the Icon ID so they could update the icon.
This PR imports the manageiq/activerecord-virtual_attributes gem so we can use the virtual_column method to specify columns on models. It also sets up the plumbing so our json responses include the virtual attributes.
(the version of the gem in rubygems.org wasn't working so I used the master branch and it is working as expected)

cc @Hyperkid123 going to be adding icon_id to the portfolio_item response so you can update it that way.

@Fryguy @abellotti Can either of you comment on the use of virtual attributes here.  Not sure if there are concerns around filtering or the sort_by functionality that is being added to the manageiq-api-common repo if we enable virtual columns.
Just want to check if this is a safe before we start down this path.

Closing due to the decision to not expose things that aren't actually in the db for filtering reasons. Re-working the relation between icons and portfolio_items instead to put the icon_id on the portfolio_item object.


[Routing] Add a registry to check if a chain allows forwarding

Epic: https://github.com/osmosis-labs/osmosis/issues/4344
Continuation of https://github.com/osmosis-labs/osmosis/pull/4694
Background
We need to check that the chains in the path allow forwarding before sending the transaction to prevent packets from getting stuck in the middle
Suggested Design

Add a new registry

Acceptance Criteria

The registry exists and is tested
XCS checks this before sending the packets

Is this easiest as a new column in the registry table, or as a gating condition for inclusion to the registry, and automatically checked by the contract. (Similar to how we were considering making contracts test that the counterparty is the same as Osmosis)

I was thinking as a column, but only having channels we can route through be accepted might be a better idea 🤔


Enable normal caching of composer installs

In normal composer, caching is handled automatically and at least in terms of bitbucket pipelines (and probably other ci/cd infrastructure) they have pre-built caching that handles the lengthy install each time a build is performed.
Due to the setting in the docker image to change the composer home env, this breaks at least the bitbucket pipelines, but maybe more. Is there any reason to no just leave the composer home env alone and just let it work as intended? I see you have a configured custom cache in the gitlab deployment but it never mentions the actual composer cache, but only the vendor directory.
UDPATE: Simply removing the line in the dockerfile for setting the env, will enable the normal caching to work

Hi there 👋
Thanks for raising this issue.
This was already like that originally but users had issues with binaries not being found automatically from the $PATH variable. See issue https://github.com/lorisleiva/laravel-docker/issues/20.
Defining an explicit directory for COMPOSER_HOME enabled us to fix this issue. Since then I've had a look at other PHP Dockerfiles that include composer and most of them seem to be using this approach.
I'd love to improve this by making it more cache-friendly for CI/CD tools but not if it's going to re-open issue #20.
Let me know your thoughts on this. 👍

While I of course can't test all the ci/cd implementations due to this being docker-ized I would think that all pipelines would work the same...because well otherwise...what's the point of docker. With that said I can say that the modifications in the PR applied in a new image, it does work as expected. I would say that I don't use the pre-installed version of php codesniffer, as I run codesniffer in a pre-commit hook as well so the pipeline check is just for good measure. I'm assuming the pre-installed version of phpcs is what caused that issue in the first place, which for me seems like bad practice and enforces a mentality of "ci will catch it"...IMHO of course.

So it seems that it doesn't actually work in the PR....did some more checking and it seems neither ends up working in bitbucket for using it's built in caches....looks like I need to do more investigation to get it working...

I’m going to close this for now. Feel free to open a new issue if needed. 🙂


encrpypt and save groupsio password

set up job to check token expiry
Changes proposed ✍
What

Update groups.io onboarding to encrypt and save password in database
Set up cron job via job generator service to check token daily and renew if token will expire in 2 days or less

copilot:poem

Why
groups.io tokens are valid for a month so we need a way to renew tokens so we can make groups.io calls without any permissions issues

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Allow setting of "redirect_uri"

sk-auth defaults to https://localhost:3000/api/auth/callback/github with no ability to change it successfully.
Note the s in https.
This is problematic because for localtesting where https isn't used.

The protocol can be set when creating a SvelteKitAuth object.
export const appAuth: SvelteKitAuth = new SvelteKitAuth({ 	providers: [oauthProvider], 	protocol: 'http' });

Thank you! I did the following
import { dev } from '$app/env';

export const appAuth = new SvelteKitAuth({
  protocol: dev ? 'http' : 'https',
  providers: [
    // ...
  ],
  // ...
});


tour: Resource temporarily unavailable on concurrency/1

Context: https://tour.golang.org/concurrency/1
runtime/cgo: pthread_create failed: Resource temporarily unavailable
SIGABRT: abort
PC=0x7f7a7ad8f067 m=0 sigcode=18446744073709551610

goroutine 0 [idle]:

goroutine 1 [running]:
runtime.systemstack_switch()
	/usr/local/go/src/runtime/asm_amd64.s:298 fp=0xc420020780 sp=0xc420020778 pc=0x457770
runtime.main()
	/usr/local/go/src/runtime/proc.go:128 +0x63 fp=0xc4200207e0 sp=0xc420020780 pc=0x42d483
runtime.goexit()
	/usr/local/go/src/runtime/asm_amd64.s:2337 +0x1 fp=0xc4200207e8 sp=0xc4200207e0 pc=0x45a381

Likely a temporary issue, now fixed. Closing.


Missing dependency during unit testing

Category

[x] Question
[ ] Typo
[x] Bug
[ ] Enhancement / Suggestion
[ ] Additional article idea

Expected or Desired Behavior
When I was writing unit tests against the webpart class, I get an error that the @ms/sp-telemetry is missing.
Observed Behavior
While running gulp test I receive the following error:
PhantomJS 2.1.1 (Mac OS X 0.0.0) ERROR
  Error: Cannot find module "@ms/sp-telemetry"
  at /Users/<user>/nodejs/spfx/testing-wp/temp/tests.js:52957

Steps to Reproduce
describe('<HelloWorldWebPart />', () => {
    it('Should open the webpart', () => {
        const mockCtx = new MockWebPartContext();
        const wp = mockCtx.initialize(new HelloWorldWebPart());
    });
});

When I write this in a test I get the error. When I remove const wp = mockCtx.initialize(new HelloWorldWebPart());, all other tests keep working.
When you just do something like this const wp = new HelloWorldWebPart() you get the same error.

@estruyf are you still seeing this issue?

Yes, still the same missing dependency.

Also the same in the new update.

Yes, still the same missing dependency.

This is a known issue. We're working on a solution.

I have the same error on test running if I import in the code:
import { HttpClient } from "@microsoft/sp-http";

Is there a workaround for this issue?

We also have the same problem and need a workaround for this issue.

Have the same issue when running tests
Module not found: Error: Can't resolve '@ms/sp-telemetry'
any help ?

Upgraded to latest sharepoint yoeman generator, and still getting this issue. I have removed node_modules folder, tried npm install / npm install --save-dev. Tried gulp clean. Module still missing.
Is there any update on this issue? Has anyone got around this issue and have a workaround?

I have run the following command to see packages
λ npm -g list --depth=0
removed and updated<EMAIL_ADDRESS>and<EMAIL_ADDRESS>still having issues

Also having issues with this.

Hi All, after some debugging and following @buckyaustin update.
I found that there was a duplicate @assets import within my WebPart, when I remove this the error "Module not found: Error: Can't resolve ms sp-telemetry" was gone and my unit tests started working again.

Not working me .. anu update

Same here. Any updates on this?

@iclanton Can you provide an update on this?
Would be greatly appreciated :).

I checked and found that every method which is making a calll the http service needs to be stub
and it worked for me

@deploymentvsureshk Could be so kind as to create an example (HelloWorld WebPart) to demonstrate it?

Further information that might help.
I have seen this occur on the following
@microsoft/sp-loader.SPComponentLoader.loadCss
@microsoft/sp-loader.SPComponentLoader.loadScript
@microsoft/sp-http.HttpClient
sp-pnp-js.pnp.web.lists
Just using the import statement for these doesn't cause the problem, but using methods within them causes the problem to occur.
I'm assuming there is a common class/method that all of these use that is causing the problem.
You should stub responses from ajax or switch out a class that does the http call for another class that doesn't use http. In my build we switch classes so the http code doesn't get executed. Just by having the methods used in the code base is enough to cause the tests to fail even though they are not invoked in the tests. Commenting out the use of the methods allows gulp test to execute.
Hope this information helps.

Hey I am getting the same error as well. Version 1.2.0 of the SPFx. Seems that  "@ms/sp-telemetry"  package is included with almost all the SPFx libraries. When gulp test is run in the temp folder we get manifest and the @ms/sp-telemetry is hooked to almost every SPFx Library and Application including SPLoader, SPHttp, SPPageContext, SPComponentBase, SPWebPartBase, SPExtensionBase, WebPartWorkbench, SPLoader. However if we go to the SPFx node modules and reverse engeneer for a while we see that this is package is from internal Microsoft NPM server.
"description": "An internal package supporting the SharePoint Framework",
  "devDependencies": {
    "@ms/odsp-utilities-bundle": "~1.1.0",
    "@ms/sp-build-internal-web": "~0.6.1",
    "@ms/sp-telemetry": "~0.2.2",
    "@types/chai": "3.4.34",
    "@types/mocha": "2.2.38",
    "@types/sinon": "1.16.34",
    "@uifabric/styling": "0.15.2",
    "chai": "~3.5.0",
    "gulp": "~3.9.1",
    "sinon": "~1.17.6"
  }

Please remove that package from the loaderConfig so we can test or make it publicly available. Thanks!

This also affects "@microsoft/sp-dialog" where the internal  "@ms/sp-telemetry": "~0.2.2" is in the dev dependencies, But is used extensively in the code.
The missing class is a class to do some logging.
IMHO, It should be moved to the dependencies (from dev) for the module and made public, or all references to the logger should be removed, or a stub alternate provided.
My versions are:
"@microsoft/decorators": "~1.3.0",
    "@microsoft/sp-application-base": "1.3.0",
    "@microsoft/sp-core-library": "~1.3.0",
    "@microsoft/sp-dialog": "1.3.0",
    "@microsoft/sp-http": "^1.2.0",
    "@microsoft/sp-lodash-subset": "~1.3.0",
    "@microsoft/sp-webpart-base": "~1.3.0",

Another observation is that if you try for some reason to create/test new instance of class that uses SPComponentLoader  within .test.ts file then it will throw the @ms/sp-telemetry error and fail all tests. By removing such classes and replacing with mock-ed classes that do now have the reference to SPComponentLoader  might partially solve the issue.

I also get this error if I do this import:
import { SPHttpClient, SPHttpClientResponse } from '@microsoft/sp-http';

I also faced same issue. But what i am having in my .ts file is
import SPHttpClient from '@microsoft/sp-http/lib/spHttpClient/SPHttpClient';
import SPHttpClientResponse from '@microsoft/sp-http/lib/spHttpClient/SPHttpClientResponse';

Since I am importing spHttpClient twice even though for different modules, it is giving error. If I change to import {SPHttpClient,SPHttpClientResponse} from '@microsoft/sp-http'; then it started working.
Hope this is helpful.

@ymihir solution worked for me as well.

With 1.3 this issue prevents testing of spHttpClient.

@VesaJuvonen  - I see this is among the 6 issues still marked as 'status:fixed-next-drop'.  Can someone tell me what that means from an ETA standpoint?

I can reproduce issue in spfx 1.4.0.

Hi,
Thank you for the feedback. Please add a feature request on UserVoice and depending on community interest we may or may not be able to make the fix.

@lahuey - Please correct me if I'm mistaken, but I don't think this is a feature request - it's a bug.

Is this fixed in 1.4.1?

@michel-weber We're still experiencing this issue in 1.4.1.
I saw the tag status:fixed-next-drop so I was under the impression that a fix would be rolled out soon. Is that not the case?
If this has been de-prioritized, does anyone have any docs/blogs explaining how to work around this? This issue is blocking my team from doing any testing on web parts which include REST calls (all of our components do). Thanks for any info.

That was also my understanding. But the tag was added on the 28th of October 2017 - and since then 1.4.0 and 1.4.1 have been released. So I think this issue should be reopened.
@VesaJuvonen Can you look into this? Will this fix be released with the next version (> 1.4.1)?

I think @lahuey is silently saying  "Deal with it" :) . It has always been convenient to turn bug into a feature :) . Considering the fact that the testing scaffold templates are not in the latest framework anymore and the last comment from @patmill here https://github.com/SharePoint/sp-dev-docs/issues/1335. I am not sure if we should still rely on the testing framework that comes with the frameworks anymore.

I have the same problem with import { GraphHttpClient, HttpClientResponse} from '@microsoft/sp-http';
Error: Cannot find module "@ms/sp-telemetry"
have you resolve this problem ?

We are running into the same issue here
Cannot find module '@ms/sp-telemetry' from 'DigestCache.js'
at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:179:17)
at Object. (node_modules/@microsoft/sp-http/lib/spHttpClient/DigestCache.js:3:22)

I have a possible workaround for this!
This worked for me, Your mileage may vary.
I had narrowed down my issue specifically to when i would "new up" an object that didn't even reference anything SP, HTTP, or graph client. I found that instead of newing an object, I casted a general one into my class and ran the tests worked.
I had this
const testObject = new WeatherInfo(params...)
now i have this
const tempObj = {
    param1: ...
    param2: ...
};
const realObjectToTestWith = testObject as WeatherInfo;

Sorry for the double post but I took another stab at my issue and found a fix for me, not a workaround.
Seems I was referencing imports from the same folder, however one group was listed in my index, the other was referenced all the way. For example:
import { ModuleName } From "./provider/module
import { SecondModule } from "./provider"

once i changed the second module to reference all the way instead of using the index.ts file inside the folder my issue went away.
Hope this helps someone.

This is due to if you have any http reference used for TEST
On Saturday, 7 July, 2018, 1:15:53 AM IST, Devin Prejean<EMAIL_ADDRESS>wrote:
Sorry for the double post but I took another stab at my issue and found a fix for me, not a workaround.
Seems I was referencing imports from the same folder, however one group was listed in my index, the other was referenced all the way. For example:
import { ModuleName } From "./provider/module
import { SecondModule } from "./provider"
once i changed the second module to reference all the way instead of using the index.ts file inside the folder my issue went away.
Hope this helps someone.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm running into a similar issue:
Cannot find module "@ms/sp-client-shared" which is being referenced under<EMAIL_ADDRESS>

Hey @adambarrettsmith . I'm running into a similar issue. Wondering if you could update this thread if you found a workaround. Thanks!

For the record:
I was experiencing this on 1.4.1, and ultimately ended up upgrading to 1.6.0-plusbeta which seems to have eliminated the problem.
(Recommendation: use office365-cli to retrieve steps for doing this upgrade, as there are a bunch of minor manual config changes it reports)

I am getting this error  Cannot find module '@ms/sp-client-shared' from 'OAuthTokenProvider.js when I try to run tests for services that use SPHttpClient for rest calls.
In my jest configuration I have
"transformIgnorePatterns": [ "node_modules/(?!(@microsoft/sp-http)|(@microsoft/sp-core-library)|(@microsoft/sp-diagnostics))" ],

Any help or direction in this space would be helpful as I am new to writing tests.
I am using Sinon stubs to mock the functions.

Dear all I am running into this problem when I try to debug a spfx react web part Cannot find module '@ms/sp-telemetry'
Can someone help?

Has this been resolved? I am on SPFx v1.8.0 and I am seeing missing dependencies when trying to unit test my web parts (which are not using React) using Jest. Specifically I am seeing Cannot find module '@ms/sp-telemetry' from 'SPStarter.js' when trying to import SPComponentLoader from @microsoft/sp-loader in my web part. If I remove that from my web part, I then encounter another error: Cannot find module '@ms/sp-client-shared' from 'OAuthTokenProvider.js'.
Am I missing something? Thanks in advance!

Running into the same issue for unit tests in SPFx using jest/sinon.
One of the react components use
import { SPComponentLoader } from '@microsoft/sp-loader';

Tests fail with message
  ● Test suite failed to run

    Cannot find module '@ms/sp-telemetry' from 'SPStarter.js'

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:169:17)
      at Object.<anonymous> (node_modules/@microsoft/sp-loader/lib/SPStarter.js:4:22)

SPFx version 1.8.2
jest : 24.8.0
npm : 6.9.0
node : 10.15.3


Removing a Websocket Errors

Hi, I am currently rending a Websocket when I need to, but when I stop render the Websocket , remove it from children of an object, the Websocket will try to push its props back to the child resulting in an error since non of the object information about the Websocket component exists.
Is there a way around this or to stop the Websocket from pushing its props on close?
Children should be empty but instead gets filled with the below info:

Could you provide a MWE in code?

Below I have linked a basic server from your documentation and then the client server with the breaking websockets.
I have added them as txts because .py is not allowed and I could not paste them nicely.
Websocket Delete Example.txt
Delete Example Server.txt

For code, please use the markdown code blocks available in the editor by clicking the <> symbol. The easiest is typically to pasta a block of code, then highlight the code and click the <> symbol.
I just tried running your example, and I get the error. But it doesn't seem related to the websocket, the error seems related to bugs in the way children are being manipulated in the update_output_sockets callback.

For some reason when I wrapped the code in the code block it excluded large parts of the code.
In relation to the error, although it is a children problem, it is stemmed from when I remove the websocket child. The websocket disconnects and as a result the websocket tries to write its state to the previously existing websocket component, however that no longer exists and so it is just written in the children, but that set of info is not a component and so the dashboard errors. If there is a way to prevent this state from updating or checking if the component still exists before writing, I believe it would solve the issue as the component will not try and write its final death state.

Hi, I suspect that I currently have the same problem using websockets in my dash project, so I wanted to know if there is any news on this? My scenario is that I have a dash app with multiple pages and I only want to keep a websocket connection open if the user is on one specific page. I can connect to the websocket on that specific page, but when I try to change the page (and thereby close and unload the websocket) the app crashes. I hope to hear any updates you might have. Thanks!

Hi, I have encountered the same issue when using a WebSocket in a multipage app and changing away from a page containing one ore more unclosed WebSockets. The full traceback is:
(This error originated from the built-in JavaScript code that runs Dash apps. Click to see the full stack trace or open your browser's console.)
TypeError: t.split is not a function

    at u.value (http://localhost:8050/_dash-component-suites/dash/dcc/async-markdown.js:2:5115)

    at u.value (http://localhost:8050/_dash-component-suites/dash/dcc/async-markdown.js:2:6646)

    at finishClassComponent (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:17295:33)

    at updateClassComponent (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:17245:26)

    at beginWork (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:18755:18)

    at HTMLUnknownElement.callCallback (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:182:16)

    at Object.invokeGuardedCallbackDev (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:231:18)

    at invokeGuardedCallback (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:286:33)

    at beginWork$1 (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:23338:9)

    at performUnitOfWork (http://localhost:8050/_dash-component-suites/dash/deps/react-dom@16.v2_7_0m1669813432.14.0.js:22292:14)

Hi, I also have this issue and it could probably be resolved exactly like @Parker-Bergen suggested... just remove the onclose callback before closing the connection inside componentWillUnmount():
https://github.com/thedirtyfew/dash-extensions/blob/master/src/lib/components/WebSocket.react.js#L78

I have just pushed a release with a potential fix. Could you test if it resolves your issues @m3g4p0p ?
https://pypi.org/project/dash-extensions/0.1.14rc1/

Hi @emilhe, yes cool many thanks, that seems to have fixed the issue. :)


Password reset: receiving an Error Message and no code?

Description:
On Edge, using the Tablet
In order to reset my password for<EMAIL_ADDRESS>there's a box to "Enter the security code you received", however I never ended up receiving a code?
Steps to Recreate:

Go to the Sign In page and click "Reset Your Password"
Input your email<EMAIL_ADDRESS>and click onto the link that gets sent to your inbox
Correctly input the answers to your security questions
Arrive at the page below: observe the error message? And no security code was received. (Tested this out 5 times on my end, same result and error message each time)

Checked in Notify
I see a few "Magic" link emails but non with a security code.

I have now marked the account as verified -- please re-test :)

It worked!!! Thanks so much Tim! :O


Any convenient script to merge multiple library outputs?

msamtools is a promising tool for omics analysis. I was wondering if there's a convenient helper script to combine the gene counts in profile outputs for multiple libraries? Thanks!

@arumugamlab many thanks for your prompt response. I meant merging profile outputs for multiple samples, where each was mapped to the same gene database. For example, salmon has a function called quantmerge to merge or append together outputs based on specified library names and tpm counts for each sample. The output there is a merged table that contains the gene names in the first column and the tpm counts for the various sample libraries in the subsequent columns.

Thank you very much. I'll try this out; closing this ticket for now.


Add validation for phone numbers

Currently we accept any input in the phone number fields.

Closing this in reference to #169


[bug] Plugin function not found, cannot call nsis_tauri_utils::download

Describe the bug
Hi everyone, I have issue when build cross-platform. A few hours ago, it was able to build successfully, but now when trying again it has problems
` Finished release profile [optimized] target(s) in 58.39s
Warn Cross-platform compilation is experimental and does not support all features. Please use a matching host system for full compatibility.
Warn ignoring msi
Info Target: x64
Info Code signing is currently only supported on Windows hosts, skipping...
Running makensis.exe to produce
path/Desktop App_0.1.0_x64-setup.exe
Plugin function not found, cannot call nsis_tauri_utils::download
Error in script "path/src-tauri/target/x86_64-pc-windows-msvc/release/nsis/x64/installer.nsi" on line 447 -- aborting creation process
Error failed to bundle project: No such file or directory (os error 2)```
Reproduction
No response
Expected behavior
Build successfull
Full tauri info output
[✔] Environment
    - OS: Mac OS 14.5.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.14.0
    - npm: 10.7.0

[-] Packages
    - tauri [RUST]: 1.6.8
    - tauri-build [RUST]: 1.5.2
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.5.1 (outdated, latest: 1.6.0)
    - @tauri-apps/cli [NPM]: 1.5.6 (outdated, latest: 1.6.0)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist/desktop-app
    - devPath: http://j317webapp.com:9000/
    - framework: Angular
    - bundler: Webpack

Stack trace
No response
Additional context
No response

can you update the cli version to latest and try again?

Yes sir, it's working well after upgrade tauri-cli version

@khang3052002, could you share your tauri.config.json, please?


Allow lowercase base32 strings if isGoogle is set to true

This PR adds support for lower-case Base32 strings to match the behaviour of Google Authenticator.
_generateCode function now always converts strings to upper-case if isGoogle is set to true before calling base32.decode.
Tested this by importing the key provided in #44 to Google Authentication and checking if it generates the same codes for lower and uppercase secret.
Fixes #44 and #45.

Sorry for the delay, thank you for this PR. I will get this merged and released shortly.

3.1.4 is released with your fix, thank you.

Thank you both!


Shadowrun 5 specific scripts for glitches and initiative

Any tips for best practices on documentation?

There is some discussion in the README.md:

description: A short explanation of the script and it's use that will appear along side the script on Roll20. It is important for this section to be filled out in detail, as it's the primary way users will get information about the purpose and use of the script. Included in the description section needs to be an example use or purpose, list and explanation of API Commands, and any other information necessary to operating the script.

Beyond that, I'd start with a paragraph describing why the script exists and why someone would want to use it, then talk about any commands for it, then talk about any configuration parameters.

There are a few issues. Each script needs to be in it's own folder at the parent level. I know you wanted them to be bundled under a shadowrun folder but our system needs them to be separate. Also your script.json files aren't valid. You can't have returns in your description that aren't encoded. You can use markdown I.E. "\r". Check out the 5e Companion script or TokenMod as examples. Submit a new pull request when you've made these changes so we can get your scripts into the one-click install.

So is it better to have multiple top level folders with an SR5 prefix each, or should I combine them all into a single script, under a single directory?

Either is fine. When I did the 5E Companion and 13th Age Companion scripts I combined them and created API commands to toggle off parts of the functionality. But if you think most people will only want parts of the scripts, turning them each into their own is fine as well.


Error "/lib64/libc.so.6: version `GLIBC_2.18' not found"

Cool project. Very existing!
However I am running csvpp on a Linux system (RHEL 7.9) and I get the following error:
csvpp: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by csvpp)

libc.so.6 exists on the system under these paths:

/usr/lib/libc.so.6
/usr/lib64/libc.so.6

Any idea how to get this running?

@halloleo are you building from source or using one of the release downloads? I just tested on ubuntu and both of those seem to work for me.

csvpp-v0.6.1-5-g18e09e4-x86_64-unknown-linux-musl.tar.gz
@halloleo can you see if this one works?  I think the problem is your system has an outdated glibc, so this is statically built to not need it

Thanks for looing into this.
I didn't built from source -- I just used your release,
I'll try your static exe. The RHEL system I use is quite outdated indeed...

That's what it was, @patrickomatic! When compiled statically it all works beautifully. Thanks a lot!

Great, I'll include statically linked binaries in the releases going forward. Lemme know if you have any other problems


resolve() with a promise as argument has issue

Hi, I'm trying to use this library on IE11. resolve with a promise as argument doesn't pass in argument in the .then() function. Is this a bug?
var promise = new Promise(function (resolve, reject) {
    resolve('result');
});

var promise2 = new Promise(function (resolve, reject) {
    resolve(promise);
});

promise2.then(function(result) {
    // result is undefined
});

@keven425 I am unable to reproduce your issue in IE11.
I created a JSBin with your code above. http://jsbin.com/fovebecuqi/edit?html,js,console,output
result is logged in my console. Are you seeing something different?

I am going to close this issue for now. Please respond if you feel there is still an issue.

@taylorhakes thank you for the reply. Yes, I tried your jsbin in IE11, and it's working as intended. Thank you for verifying.
What confused me was that IE 11 debugger was not displaying request data reliably. Sorry for my late reply.


Add license checker

Purpose

Tool to check the license of files.

It will be called by Github workflow to check project files (except java module)
It can be called manually to verify the package files (except files generated by python package tool):
SOURCE_PACKAGE=pypaimon-0.2.0.tar.gz ./check-licensing.sh

Tests

API and Format

Documentation

+1


How to use RKE to remove worker nodes that are no longer accessible?

Rancher Server Setup

Rancher version: 2.4.5
Installation option (Docker install/Helm Chart): RKE 1.3.2

I've built an RKE cluster that I've had running for a few years now and recently I've had 2 worker nodes go down that can not be recovered. I'm trying to eliminate those 2 worker nodes from one of the clusters but every time I run rke with those 2 nodes removed from the cluster.yml, it seems to get stuck while trying to establish the SSH tunnel to clean out those nodes.
How do I run RKE to remove those 2 nodes from the cluster without them being accessible?

@stevenmcastano did you ever find a solution to this ? Running into the same problem


csv - missing display currency at the time of payment

Andrej can confirm

To have one column in CSV export be populated with instant fiat value at the time of receiving payment. At least in USD, but preferably in a display currency user is using.


Fixes for virtual folders

This covers 2 issues:

Could not rename a virtual folder at all. The option did nothing.
Prevents adding the same foldername twice, showing a message to that effect.

Nice! +5 👍🏻


Package Publishers

The command in the image says kpt init but the correct command is kpt pkg init

@etefera can you please take a look and fix?

Thanks for noticing! There's a PR out now to fix that.


show size of downloaded files

Today when downloading "very large" bottles it can take awhile:
==> Downloading<EMAIL_ADDRESS>==> Downloading from https://akamai.bintray.com/de/de26cfd906d55496acf1eb4927dca3d003e89a771c954495da1f905cf387b17d?__gd
##################################################################        92.0%

Especially on slow connections.  It would be nice if it showed more than just percentage.  Things that come to mind: total size, or possibly even "expected time remaining" in the download.
The motivation for the feature
It's confusing for me not being able to estimate how much longer a download is going to take.  I want to know if it's going to take seconds or minutes or what not.  Or know how much size is left to be able to estimate the same based on the percent already downloaded.
How the feature would be relevant to at least 90% of Homebrew users
Many Homebrew users will run into a larger bottle every so often, would be nice to have some more info to the user as it downloads.
What alternatives to the feature have been considered
Already mentioned above.  Thanks!

Especially on slow connections. It would be nice if it showed more than just percentage. Things that come to mind: total size, or possibly even "expected time remaining" in the download.

This output is from curl and not Homebrew so we cannot change this, sorry.

If you pass -v or set HOMEBREW_VERBOSE=1, curl will use its standard progress meter that displays total download size.

It's too bad curl's output isn't customizable.  I guess workarounds would be to get the size from "the recipe" (maybe just for very large files?) or possibly do a HEAD first to determine it, where possible.  Both a bit painful... :)


Add role support and secondary user store

Purpose

Add doc chages to migration, CLI support for roles and secondary user stores.
Related to wso2/micro-integrator/issues/2571 wso2/micro-integrator/issues/1880

Please add an entry for this in the About this Release page and point to the new pages.


[FEATURE] Option to view parent prompts on 'Validation Insights' and 'Sample Train Visualization'

🚀 Feature
For nested prompts (tree-like), H2O LLM Studio should have an option to display the parent conversations. Currently, on both 'Sample Train Visualization' (datasets tab) and 'Validation Insights' (for a completed experiment) it only shows the 'current' conversation (prompt+answer), without the proper context of previous interactions. For the user of LLM Studio it might be necessary to see such context to evaluate whether the conversation branch makes sense and/or the model gives good answers.

Thanks @luizlf for the issue.
Would you be able to contribute to this?


Add rules to groups

Is there a posibility to add rules to password groups  -so every new password within the group follows the rule?
For example like it is done https://keepass.info/plugins.html#pedcalc

This feature is added in the Version 3.0 release. Thanks for the suggestion!


Coherence <IP_ADDRESS>.7 with Bucket4j 6.2.0 fails with java.io.IOException: Unknown type id 768

We recently upgraded to bucket4j 6.2.0 from previous 4.10.0 and started noticing the below error whenever we execute this code -
`// init bucket registry
NamedCache<String, GridBucketState> cache = CacheFactory.getCache("RateLimit");
//Proxy manager / weak pointer to buckets.
ProxyManager buckets = Bucket4j.extension(Coherence.class).proxyManagerForCache(cache);
Optional existingConfigurationOptional = buckets.getProxyConfiguration(requestKey);`
We have added all the required serializers as listed in the documentation here - https://github.com/vladimir-bukhtoyarov/bucket4j/blob/master/doc-pages/coherence.md
Error stack trace -
java.lang.RuntimeException: java.io.IOException: Unknown type id 768 	at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:416) 	at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:349) 	at com.tangosol.coherence.component.net.extend.RemoteNamedCache$ConverterFromBinary.convert(RemoteNamedCache.CDB:4) 	at com.oracle.common.collections.ConverterCollections$ConverterMap.get(ConverterCollections.java:1558) 	at com.tangosol.coherence.component.net.extend.RemoteNamedCache.get(RemoteNamedCache.CDB:1) 	at com.tangosol.coherence.component.util.SafeNamedCache.get(SafeNamedCache.CDB:1) 	at io.github.bucket4j.grid.coherence.CoherenceProxy.getConfiguration(CoherenceProxy.java:81) 	at io.github.bucket4j.grid.coherence.CoherenceProxyManager.getProxyConfiguration(CoherenceProxyManager.java:64) 	at  Caused by: java.io.IOException: Unknown type id 768 	at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:385) 	at com.tangosol.io.Serializer.deserialize(Serializer.java:89) 	at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:3204) 	at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:412) 	... 27 more Caused by: java.lang.IllegalStateException: Unknown type id 768 	at io.github.bucket4j.serialization.DataStreamAdapter.readObject(DataStreamAdapter.java:118) 	at io.github.bucket4j.serialization.DataStreamAdapter.readObject(DataStreamAdapter.java:109) 	at io.github.bucket4j.serialization.DataStreamAdapter.readObject(DataStreamAdapter.java:49) 	at io.github.bucket4j.grid.GridBucketState$1.deserialize(GridBucketState.java:44) 	at io.github.bucket4j.grid.GridBucketState$1.deserialize(GridBucketState.java:40) 	at io.github.bucket4j.grid.coherence.pof.AbstractBucket4jPofSerializer.deserialize(AbstractBucket4jPofSerializer.java:76) 	at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3619) 	at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2890) 	at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:379) 	... 30 more

Hello @nikhilvaishnavi

The part of stacktrace above tells that problem is related to internal Coherence types not Bucket4j types, because clients are not allowed to specify type numbers less than 1000. So looks that you need the consultation with the Oracle team, or getting help on some Coherence related forums.

@vladimir-bukhtoyarov But the root cause in stack trace seem to originate from Bucket4j where we are trying to deserialize an object which for which no deserializer is defined -
Look at the last trace - Am I reading it wrong ? I did see in the coherence jar there is not type id 768 defined as well but maybe we are requesting for deserializing an object which is not defined in coherence.
Caused by: java.lang.IllegalStateException: Unknown type id 768
at io.github.bucket4j.serialization.DataStreamAdapter.readObject(DataStreamAdapter.java:118)
at io.github.bucket4j.serialization.DataStreamAdapter.readObject(DataStreamAdapter.java:109)
at io.github.bucket4j.serialization.DataStreamAdapter.readObject(DataStreamAdapter.java:49)
at io.github.bucket4j.grid.GridBucketState$1.deserialize(GridBucketState.java:44)
at io.github.bucket4j.grid.GridBucketState$1.deserialize(GridBucketState.java:40)
at io.github.bucket4j.grid.coherence.pof.AbstractBucket4jPofSerializer.deserialize(AbstractBucket4jPofSerializer.java:76)

Yes. You are right. What version of Coherence do you use?

@nikhilvaishnavi I need for <IP_ADDRESS>.7 Coherence distribution to do compatibility testing.
Also I have additional questions:

Where you got this exception of production on production or inside staging environment or on developer's machine? If on production then what is the time to live of records in your cache? Is it real that cache entry had been written by legacy Bucket4j version and was read by a new Bucket4j version?
Did you upgrade Coherence by itself or Bucket4j only?
What happens if not using POF serializer? Does upgrade from 4.10.0 to 6.2.0 works without POF serialization feature?

Attached the coherence jar - coherence-<IP_ADDRESS>.7.jar.zip
Answer to your questions inline -

Where you got this exception of production on production or inside staging environment or on developer's machine? If on production then what is the time to live of records in your cache? Is it real that cache entry had been written by legacy Bucket4j version and was read by a new Bucket4j version?

I am able to see this in my local env (developer's machine). The TTL in prod/local machine is 90 min. All the entries in cache are for new Bucket4j version.

Did you upgrade Coherence by itself or Bucket4j only?

Bucket4J only

What happens if not using POF serializer? Does upgrade from 4.10.0 to 6.2.0 works without POF serialization feature?

I am not clear about this - how do I turn of POF serializing. Note we already use coherence in our application with POF serialization and I was just plugging in bucket4j into our system due to this. If there is a way to do it for bucket4j I am open to try it out

@vladimir-bukhtoyarov I think I may have found the root cause. We have the coherence cache cluster as a separate docker image. What I have come to understand is every time client changes, we need to rebuilt the coherence docker image to pick up any pof related changes as well.
We need to rebuild it with the new client version of bucket4j which resolves this issue.
Thanks for looking into this


The Warning of React lifecycles componentWillMount

I have the same problem, will it be fixed?

I have the same problem then I move to different editor


Namesrv auto discovery not work

The issue tracker is used for bug reporting purposes ONLY whereas feature request needs to follow the RIP process. To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
It is recommended to start a discussion thread in the mailing lists in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
Generally, fixing an issue goes through the following steps:

Understand the issue reported;
Reproduce the unexpected behavior locally;
Perform root cause analysis to identify the underlying problem;
Create test cases to cover the identified problem;
Work out a solution to rectify the behavior and make the newly created test cases pass;
Make a pull request and go through peer review;

As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
BUG REPORT

Please describe the issue you observed:

set a http service to auto discovery namesrvs, when updating, http service return empty, broker would be removed by old namesrv, but broker can not reg in new namesrv
rmqAddressServerDomain=xxx.xxx.xxx.xxx:9898
rmqAddressServerSubGroup=nsaddr
fetchNamesrvAddrByAddressServer=true

bug is here

What did you do (The steps to reproduce)?

What is expected to see?

What did you see instead?

Please tell us about your environment:

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

FEATURE REQUEST

Please describe the feature you are requesting.

Provide any additional detail on your proposed use case for this feature.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

If there are some sub-tasks involved, use -[] for each sub-task and create a corresponding issue to map to the sub-task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

I think the point of the problem is that the http service returns response code 200 and the body is empty.
Maybe it's also an ability to take the cluster out of service?


A better way to do Postgres case-insensitive searching?

Currently we basically do this but it is probably worth revisiting this and taking a good look at citext or collation (which is how we do it on SQLite).
Jarid was researching this in July 2022 for something on Bodega and is the one that showed me citext.

Just in case I forget how to do this. You need to create the CITEXT extension on the table you want to use CITEXT on, and you have to be a super user to do it.
So connect to the db you want to add CITEXT to:
$ psql -U postgres -h <DBHOST> -d <DBNAME>

And then install the extension:
<DBNAME>=> CREATE EXTENSION IF NOT EXISTS citext;

You can check if the extension is on the table by running:
<DBNAME>=> select extname from pg_extension;


Put flags and commands in separate pkg

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e1b258a). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #506   +/-   ##
=========================================
  Coverage          ?   41.11%
=========================================
  Files             ?       49
  Lines             ?    12756
  Branches          ?        0
=========================================
  Hits              ?     5245
  Misses            ?     6212
  Partials          ?     1299

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 e1b258a...26f9104. Read the comment docs.


Incompatibility with docker image: prom/pushgateway:v0.4.0

Hi,
I'm unable to get Pipeline to work with v0.4.0 of the prom/pushgateway Docker image.  (Pipeline works fine with the older v0.3.1 image.)
When running prom/pushgateway v0.4.0, my pipelinle.log file is filled with the following:
`time="2017-06-15 21:34:54.519836" level=error msg="http reply" error="unexpected status code 400 while pushing to http://localhost:9091/metrics/job/telemetry/instance/pipeline_11823492967441504429" instance=pipeline jobName=telemetry pushGWAddress="http://localhost:9091" pushURL="http://localhost:9091/metrics/job/telemetry/instance/pipeline" tag=pipeline
time="2017-06-15 21:34:54.533393" level=error msg="http reply" error="unexpected status code 400 while pushing to http://localhost:9091/metrics/job/telemetry/instance/pipeline_17704715107158349698" instance=pipeline jobName=telemetry pushGWAddress="http://localhost:9091" pushURL="http://localhost:9091/metrics/job/telemetry/instance/pipeline" tag=pipeline  `
Regards,
Michael

same issue rolled back to 0.3.1 and it worked, still no one knows why 0.4.0 is 400 erroring?

It's still a problem with prom/pushgateway v0.5.2.
Probably there was a message type change between v0.3.1 and v0.4.0, that is not updated in Pipeline.
I'll look after it.

👋 same issue here even with v0.8

fails on v1.2.0 as well.


Warnings after updating fontspec to version 2.6d (2017/08/14)

Several fontspec warnings: "only-xetex-feature" are issued recently on code which worked previously.
The MWE taken from here:
\documentclass{minimal}
\usepackage{fontspec}
\setmonofont{Tex Gyre Cursor}
\begin{document}
Hello World
\end{document}

Resulting warning:
*************************************************
* fontspec warning: "only-xetex-feature"
*
* Ignored XeTeX only feature: 'HyphenChar'.
*************************************************

I use XeTeX to compile, but still can see this annoying warning.
PS: the font name should be TeX Gyre Cursor with capital X.


Look into using Advisory Locks

Description
I was linked to: Que a job queue in ruby that claims superior performance by using Advisory locks. This is true advisory locks are faster, and would require some work (since you're essentially implementing you're own concurrency). However, there's several questions left to answer:

What happens to advisory locks in a failover scenario? It seems like they're entirely lost (since they are stored in a shared memory region, and not flushed to disk). We could use a notification here, but notifications aren't completely durable. I still see a row update needing to happen otherwise (which negates the benefits).
Advisory locks seem to use the same shared memory region that PostgreSQL uses for connections. To quote the docs:

Care must be taken not to exhaust this memory or the server will be unable to grant any locks at all. This imposes an upper limit on the number of advisory locks grantable by the server, typically in the tens to hundreds of thousands depending on how the server is configured.

Between the number of connections, and locks for a potentially large job queue this could be really catastrophic. As the number of jobs could create so many locks normal behavior that uses locks can't go through.

Now none of these are necissarily deal breakers (perhaps we can offer an "unsafe" mode of execution that uses locks, for the extra performance gain; where we can then document the pitfalls). That being said research needs to be done in order to determine, what the best way to handle these scenarios are.

FWIW talked to Chris, the lead developer for Que, and got some answers to his experiences:

2. The advisory locks are taken only when the job is locked to be worked, so the limiting factor would be the number of lockers/workers, not the number of jobs (at my last job the job queue got backed up to around a million records once, and it was fine). And if you need that many advisory locks I believe there are configuration options you can use to bump up the limits.```

A couple ideas I think we can take away from the points above:

Could potentially be saved by having each worker place a "placeholder" advisory lock. One that doesn't actually ever get checked, but can be used as detection for when a failover has occurred out from under the application. Then the application in the scheduler loop can re-lock any job IDs it's currently working on.
Another possibility is using an unlogged table. If your worker node id isn't in that table, you've failed over. Relock jobs.

Advisory lock buildup doesn't seem to be too big of a concern. Even amongst our biggest worker fleets at Instructure. I don't think this is something we have to be too concerned about. However we should check what the performance of postgres is when a large number of nodes exist/a large number of locks exist (also to check: how pgbouncer handles these).


Primary key flag in column definition seems to have no effect

Hello! I am using your client for my master thesis. Thank you for your work!
It seems to me that the primary flag in the column definition of an entity has no effect.
It is possible to insert multiple entries with the same string ID into an entity with primary key set for the column.
Furthermore, the CLI command "entity about schema entity" does not list primary information for the columns.
What am I doing wrong?
Many thanks,
Simon

Thanks for your feedback!
Unfortunately, as far as I am aware, Cottontail DB does not yet respect the primary key property, even though it is defined in its gRPC protocol. The information is already sent from the Python client, so as soon as Cottontail DB implements this feature it should work.

thank you for your reply!


Licensing question

Hi! We're using your project for our tool: https://github.com/yakovypg/Chat-Corpora-Annotator
Since there's no license listed, we've assumed it was okay for us to use it. However, we'd like to make sure it's okay. Do you think it could be possible for you to add a license to your project, so we know exactly how to proceed?
Thanks in advance!

Added. It's MIT


Please clarify - sending multiple notifications

Suppose my server is running code that responds to various events and those events tell the server to send push notifications to various tokens at various times. So in real time, my server may want to send 1 or 2 or 20 or 200 push notifications to various tokens (various iOS devices). Because of the way the server code is structured, I will need to use the client.send_notification function instead of send_notfication_batch. My question is this: if we have some number of (token,payload) messages to send, should we loop through all those messages and create the APNsClient object each time, ie one for each message? Or is it best to create the APNsClient once and send all the messages on the same client? Please explain. Thanks.

Also, if I create a client (which opens a connection), how long can I use this client? Does it try to reconnect automatically? For example, if I create a client at the start of a server process that runs forever, waiting to get events for push notifications to send, can I sue this same client forever or will I have to manually recreate it at some point? How can I tell if I need to recreate it? Thanks


custom dataset

I want to train on my own sketch RGB dataset, but I do not think the sketch-rnn repo has the guidance of how to do that.
Is there a way to transform RGB dataset into your dataset format?

Sorry, Our research objective is vector format sketch generation, excluding  of  the RGB format.


Add an option to mark a configuration field as "display field"

In some cases the full name of a deployment might become too long to read, and thus quickly find in a long list of deployments.
It can be useful to have a specific config field (if present) to act as the "display name" of a deployment

What I'm thinking is to add a display feature to features.yaml which would look like:
apiVersion: platz.io/v1beta2
kind: Features
spec:
  display:
    name:
      InputField:
        name: alias
    icon:
      fontAwesome: rocket

With the current default being:
apiVersion: platz.io/v1beta2
kind: Features
spec:
  display:
    name:
      DeploymentName
    icon:
      fontAwesome: question

@popen2 this looks perfect! Does platz pre-install the CRD definitions for features? I'm not familiar with it yet in our environment...

@vmalloc This is not a CRD, it's what features.json does in v0 of chart-ext (docs coming soon).

oh ok... I'll wait then :-)


added Planet Savior game 👍

PR Description 📜
This is a simple browser game built using HTML, CSS, and Vanilla JavaScript. The game involves shooting down asteroids to protect a planet. Here's a beginner-friendly description of the game and its features:
Fixes #2506

Mark the task you have completed ✅

[X] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[X] I have added screenshot for website preview in assets/images
[X] I have added entries for my game in main README.md
[X] I have added README.md in my folder
[X] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

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

@gurjeetsinghvirdee I've added the Game + fixed counting issue of games in the main README.md
Kindly have a review!

@gurjeetsinghvirdee check now!


Couldn't start client PHP Language Server

Severals PHP executable path were indicated correctly inside seetings.json file,
"php.executablePath": "/usr/bin/php"
"php.executablePath": "/usr/bin/php8.0"
"php.executablePath": "/usr/bin/php7.4"
The extension throw the following errors.

What am I doing wrong?
Thanks.

Hi. Can you get the full error. Please look under Pannel, OUTPUT and select on the right "PHP Language Server" and see if there is any output.

One other thing you can also do, is enable extended logging in vscode for PHP Language Server. Open settings, and search for php-intellisense.trace.server. Set to verbose and restart vscode. Output of all LSP messages should be in the previously specified OUTPUT panel.

The parameter php-intellisense.trace.server was set with value verbose,

The problem is related with permissions, the constructor function from RecursiveDirectoryIterator class cannot iterate the /home/antoniojv/Documents/Projects/roisinfrances/data/#innodb_temp directory,

This makes sense because data directory is a bind folder to mysql docker container, if I remove the data directory everything seems to work correctly again,
The question is, Is there a way to exclude directories in the settings file like the php-cs-fixer extension does?
"php-cs-fixer.exclude": [
"/vendor//.php",
"/config//.php",
"/public//.php",
"/bin//.php"
],

Hi!
This helps a lot, thank you.
First I'll make sure that directory traversal failures don't kill the Language Server. Then I'll see what the best way of ignoring folders would be.
Hopefully I'll get a release out soon.

Fixed in v1.0.8 . Errors from reading folders will not stop indexing.
Will work on exclusions later.