text:
Implement a pattern for dealing with upstream APIs which are slow on the first hit

We've had a couple of PRs recently

https://github.com/badges/shields/pull/7727 - socket.dev
https://github.com/badges/shields/pull/9055 - bundle.js

Both of these are the kind of services that are very "on brand" for shields, but they have this performance characteristic where the first time we call an API endpoint and the cache is cold we trigger a slow thing to happen and the request takes 30 seconds to return a response or whatever. Then once that has happened (package is built or scanned or whatever) the result is cached. Once the original slow process has happened, subsequent requests for the same package (for some period of time) are fast because they are served from cache.
Having discussed this, we think the way forward is to implement a pattern/base class for dealing with this type of service that does something like:

Call the upstream service with a timeout (lets say 3 seconds)
If we get a response inside the timeout threshold, render the badge as normal
If the request times out, return a badge that says something like "building..." or "scanning..." or whatever with a shorter than normal max-age on it (lets say 10 seconds) so we will retry more quickly than usual for badges that get traffic on them but there is still some level of downstream cache acting as a rate limit on the origin servers.

This is an imperfect solution, but it is probably the best-case scenario given the constraints of these upstream APIs.
Implementing this as a re-usable pattern would allow contributors to use it where applicable without having to re-implement it on specific service classes or families.

Thanks for providing a solution for this! How should we add tests to service if it could possibly fail on the first try?

Great question.
Nock has a .replyWithError() function you can use https://github.com/nock/nock#replying-with-errors
So if you mock a request in your service tests, in place of using .reply(200, {valid: 'object'}), you can use .replyWithError({code: 'ETIMEDOUT'})

Force-failing is doable but how do we test successful requests? Unless we can somehow disable (or extend) the _requestJson timeout, we can't safely expect a badge result.

I've just had a bit of a play with BundleJS. Seems like even if we pick a really small module, that doesn't help.
I think the other options I can think of for the live test are:

For the live test, pick a really popular package which has a high likelihood of being cached already at any given time. It wouldn't be our most reliable test, but it wouldn't be the flakiest

Write a test validator that passes if the badge value is either:

a valid value (file size, number of downloads, whatever it is we're trying to validate)
the string "building"

and rely on a test with a mocked response for the functionality test.

Our test suite still runs serially doesn't it? If so I feel like we could leverage that characteristic here.
I.e. have the very first test in the suite for this service make a live request for some package that's known to be a quick scan (a small one presumably?). i think the validation condition can be an OR variant that will pass if the result is either the scan result or the scan pending message variants. then the very last test in the suite can reuse that same package and only expect the scan result.
i'm sure we could introduce some additional delay somewhere in the middle to make the flow a bit more deterministic if we find that to be unacceptably flaky

Sorry for the late reply. Allowing to change request timeout during testing is the most straightforward solution I think. I could easily test failing by setting a really small timeout and test success by a reasonably large timeout.

When we run the service tests, we basically bootstrap a server and then each request calls a URL on it so the badge server we're testing against is a "black box". We can inject a set of config variables once at the start of the test run when we boot it, but there's no setup/teardown for each test and we can't really reach in and mock bits of it under test.
We could make the length of time we're going to pass to options.timeout.request a setting (make this global, rather than per-service). Then make that setting 3000 by default but set it to some much longer value in config/test.yaml. Then rely on .replyWithError({code: 'ETIMEDOUT'}) for the failure case.

Unrelated to the previous post, but just while I'm commenting on this issue: The other service where this pattern would be useful is tokei

authors: calebcartwright chris48s crimx


text:
increase [website] test timeout

Fixes #5261

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 079fda7bd956a24d215273e33397ad8f89c0e4e8

source: gharchive/pull-request

authors: calebcartwright shields-ci

repo: badges/shields

license_type: permissive

license_source: bigquery


text:
Added documentation for custom content Type

I have added the documentation for setting custom content type for upload files.

LGTM

thanks!

authors: LinusU badunk subinsebastien

license: mit


text:
Shell Component

Use asyncio.subprocess instead of subprocess

Closed in dc664e6

source: gharchive/issue

repo: baffelli/pyperator


text:
Add asterisk symbol for "Attribute Code" field.

Framework Version: 0.1.6

Framework Version: 0.1.6

Fixed

repo: bagisto/bagisto

license: MIT

license_source: github-api


text:
address and review are not deleted

the incoming update also redirects the delete buttons to the 404 page and does not delete the review, the address is not deleted

Hi @Arsivpro,
This is because the route method has been changed and your changes are cached. Just try to clear your routes cache,

clear cache and reinstall artisan route:cache same problem persists

It works as I want when I get the route address and delete the route made in the review.

What version are you using?

@ghermans latest version

Do you mean 1.3.1 from composer , or did you cloned the master branch?

@ghermans I am using bagisto 1.3.

Hi @Arsivpro,
If you have taken the latest clone, then make sure you check the views also. Because implementation is also done in the view portion also.
So if you have not customized then make sure you run vendor:publish command or else do it manually.

@Arsivpro and @ghermans,
I am closing this as this is not reproducible in the master branch. There is some implementation missing by @Arsivpro.

authors: Arsivpro devansh-webkul ghermans


text:
Getting translation issue in forget password page for not found email.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.x
Issue Description
While sending the correct email in the forget password input field. So it is showing notification and showing translation issues in the notification.
Preconditions

Admin should not be logged in.

Steps to reproduce

Go to 'Admin panel'
Click on 'forget password'
Send the correct email
Click on the send button
See the error

Expected Result
It should be shown proper notification.
Actual Result
it is showing the translation issue.
Screenshots
No response
Additional context
No response

Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


text:
New fixes for ded branch

Issues with dev server, CORS, compilation, loaders have been resolved
Used several resources and rebuilt repo from most recent working commit

[x] Finish project
[x] Deploy
Route images to img/.png
Add cdns back to index html
Added /dist/bundle.js to script src
Refactor skillList component

create separate skill info component in src
Make skill list compo in src/compo

Add height and width to images
Fix prod webpack config in

Use merge plugin

Use npx with webpack scripts
Add form compo
Finish server dir in separate branch
reincorporate Post css preset env
add jest and cypress tests
Check errors, stats, dev tools after EVERY change

fixed issues by using trace-deprecation, warning, error stats npm scripts
fixed several issues with homebrew and bash on mac (see gitinfo.md docs for more info)
test run deploy to N
gitInfo.md
etlify, some prod issues but believe I fixed them; will create new issue if next deploy doesn't show images and have 100 across board on Lighthouse scores

Add tests and refactor prod branch w/ merge and webworker webpack plugins
redeploy and make a branch with example UI to re-update react-boilerplate repo
Add unique images for each branch and remove placeholder descriptions
adjust sizing/colors of assets and flex boxes (e.g. width, height, srcSet, compress)
add helmet and more seo
add adjusted contact forms or backend from athena repo


text:
select not changeable with v-validate

Versions:

VueJs: 2.1.4
Vee-Validate: 2.0.0-beta.17

Description:
I cannot change a select's value after attaching v-validate.
Try removing the directive to verify that it works without it.
Steps To Reproduce:

Go here: http://jsfiddle.net/gambo/xcha53ub/
Try selecting another option

To clarify this is for the arrow keys. Thanks!

No this is for mouse also!

What browser? Working fine for me for the mouse in Chrome v.  53.0.2785.143

Chrome 54.0.2840.98 on macOS sierra

Thanks!

It has just updated to 55.0.2883.75 when I had a look. Thx to you guys too!

never noticed it before, but I can confirm on  54.0.2840.98 macos.

Very flaky  handling at this stage, related: https://github.com/logaretm/vee-validate/issues/113
Android/Firefox have different problems, Chrome has different ones...

I think I fixed it at least for chrome, should be in the latest build in the repo files, can someone confirm?

I have a MacOs Sierra and Google Chrome Versión 55.0.2883.95 (64-bit), but not working with latest build, I use npm and webpack compiler.

@luis199230 by latest do you mean beta.17 or the files in the dist directory?

yes I use beta.17

I test and see the fix, in this fiddle, show how to use properly. https://jsfiddle.net/92Lmjs6m/13/ v-validate = "" is necessary same v-model = "" if not, don't working.

I'm experience the same issue using the file in the repo.
To solve it for the time being, I'm using v-validate.initial="".

I've tagged a new release feel free to test it and confirm whether if this issue was resolved, if another issue appears feel free to create a new one describing it.

I've updated the fiddle and it seems to be working fine, closing this for now.
http://jsfiddle.net/xcha53ub/6/

cool thx, I'll give it a try!

I'm using the latest release and this is still an issue

Well that is weird, I tried the same fiddle again with beta.18 and it seems to be working fine on Chrome for Windows Version 55.0.2883.87 m (64-bit)
http://jsfiddle.net/xcha53ub/7/

The beta 18 release fixed this issue for me.

Have this problem on all browsers except Firefox on macOS 10.13.6 (safari 11.1.2, opera 54, Chromium 64.0.3260.0) How to fix this?

@hellvesper provide a code sample and I will take a look.

authors: BrandonSurowiec Stephen2 adamfairholm denjaland hellvesper logaretm luis199230 nerdyglasses seuaCoder tiagomatosweb

repo: baianat/vee-validate


text:
dperf运行失败，提示无可用大页，但实际已配置

dperf运行失败，提示无可用大页，但实际在/boot/grub2/grub.cfg已配置

要配置1G大页，你的大页是2M

cat /proc/cpuinfo | grep pdpe1gb  用这个命令查看了不支持1G大页，所以就按照图片中的2设置成了2M大页，最终按照3的方式重新设置成1G大页

2.现在不提示大页的问题了，又继续出现无端口可用的情况，但实际DPDK已经绑定了端口呢，再麻烦您帮忙回复下，谢谢~

图片上传错了，o(╯□╰)o

大页数量多配置一点，比如 1024 个 4M大页
是不是pci配置不对
请把配置贴一下

配置如图：

是不是你的网卡不支持dpdk，查一下DPDK官网支持的网卡列表

谢谢大神，应该是Realtek RTL8111不支持DPDK，还一直奇怪为什么同样配置的方式，另一台机器intel的网卡就配置成功了，这个怎么都不行，终于找到原因了o(╯□╰)o

喜欢dperf，请点个star哦， 谢谢

repo: baidu/dperf


text:
fsutil.makedirs

def makedirs(*paths, **kwargs):
    mode = kwargs.get('mode', 0755)
    uid = kwargs.get('uid')
    gid = kwargs.get('uid')

gid = kwargs.get('uid'), here should be 'gid'?

啊..是!

authors: drmingdrmer sejust

repo: baishancloud/pykit


text:
chore(deps): update module github.com/deepmap/oapi-codegen/v2/cmd/oapi-codegen to v2.4.1

This PR contains the following updates:

Package
Update
Change

github.com/deepmap/oapi-codegen/v2/cmd/oapi-codegen
patch
v2.4.0 -> v2.4.1

Release Notes

deepmap/oapi-codegen (github.com/deepmap/oapi-codegen/v2/cmd/oapi-codegen)
v2.4.1: : A couple of post-release fixes
Compare Source
🐛 Bug fixes

fix(import-mapping): don't produce unused variable when one mapping (#1781) @ottaviohartman

📝 Documentation updates

docs(sponsors): clarify Elastic's 4h/mo (#1783) @jamietanna

👻 Maintenance

build: remove patch version pinning on go directive (#1784) @jamietanna

Sponsors
We would like to thank our sponsors for their support during this release.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Pull Request Test Coverage Report for Build 11083356099
Details

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

Totals

Change from base Build 11082004140:
0.0%

Covered Lines:
1234

Relevant Lines:
1957

💛  - Coveralls

authors: bakito coveralls

repo: bakito/adguardhome-sync


text:
Pool owner changes

https://balancerecosystem.slack.com/archives/C05H1NS8Q8L/p1732621037876599

repo: balancer/frontend-monorepo


text:
Unable to name attribute 'type' in model.

Hi, it seems that using 'type' as name of a model attribute is not working.
At least with memory / disk / mysql adapters
Ex:
module.exports ={
attributes: {
type: {}
}
}
I guess it's because 'type' keyword is used by waterline but in my project case I would have been able to use type as a field name. Does it's expected behaviour ?
Thanks

@mbret Is this still an issue?

authors: CWyrtzen mbret

repo: balderdashy/sails


text:
issue installing sails on osx

Hi,
I have tried to install sails via npm but i have the same problem described in this issue 2678.
My OS version is 10.10.2 and my npm version is 2.5.1, node 0.12.0. when i launch sails i got -bash: sails: command not found.
Thanks in advance.

did you use sudo to install node?  if so, uninstall and install nvm (node version manager), then install node nvm install node, then install sails npm -g i sails, no sudo required.

thank you for your quick response, but i had always the same problem : during the installation it fails on installing ws.
Here is the log :
sails@0.11.0 preinstall /Users/dev/.node/lib/node_modules/sails

node ./lib/preinstall_npmcheck.js

Sails.js Installation: Checking npm-version successful
npm WARN deprecated node-switchback@0.0.4: The 'node-switchback' NPM module is now simply 'switchback'. See https://github.com/node-machine/switchback for latest docs.
npm WARN deprecated grunt-lib-contrib@0.7.1: DEPRECATED. See readme: https://github.com/gruntjs/grunt-lib-contrib
npm WARN deprecated node-switchback@0.0.2: The 'node-switchback' NPM module is now simply 'switchback'. See https://github.com/node-machine/switchback for latest docs.

ws@0.5.0 install /Users/dev/.node/lib/node_modules/sails/node_modules/sails-hook-sockets/node_modules/socket.io/node_modules/engine.io/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)

CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
SOLINK_MODULE(target) Release/bufferutil.node: Finished
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
SOLINK_MODULE(target) Release/validation.node: Finished

ws@0.4.31 install /Users/dev/.node/lib/node_modules/sails/node_modules/sails-hook-sockets/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)`

CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
/Users/dev/.node/bin/sails -> /Users/dev/.node/lib/node_modules/sails/bin/sails.js
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/npm requires ini@'~1.2.0' but will load
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/ini,
npm WARN unmet dependency which is version 1.1.0
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/npm requires mkdirp@'~0.5.0' but will load
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/mkdirp,
npm WARN unmet dependency which is version 0.3.5
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/loopback-workspace/node_modules/loopback requires inflection@'~1.3.8' but will load
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/inflection,
npm WARN unmet dependency which is version 1.2.7
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/loopback-workspace/node_modules/loopback-datasource-juggler requires inflection@'~1.3.7' but will load
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/inflection,
npm WARN unmet dependency which is version 1.2.7
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/loopback-workspace/node_modules/express requires debug@'~2.1.1' but will load
npm WARN unmet dependency /Users/dev/.node/lib/node_modules/strong-cli/node_modules/loopback-workspace/node_modules/debug,
npm WARN unmet dependency which is version 1.0.4
sails@0.11.0 /Users/dev/.node/lib/node_modules/sails
├── sails-build-dictionary@0.10.1
├── cookie@0.1.2
├── cookie-signature@1.0.4
├── grunt-contrib-copy@0.5.0
├── mock-res@0.1.0
├── connect-flash@0.1.1
├── mock-req@0.1.0
├── commander@2.1.0
├── sails-stringfile@0.3.2
├── merge-defaults@0.1.4
├── colors@0.6.2
├── pluralize@0.0.12
├── grunt-sails-linker@0.9.6
├── node-uuid@1.4.2
├── async@0.9.0
├── uid-safe@1.1.0 (base64-url@1.2.1, native-or-bluebird@1.1.2)
├── grunt-contrib-concat@0.3.0
├── reportback@0.1.8 (node-switchback@0.0.4)
├── grunt-contrib-clean@0.5.0 (rimraf@2.2.8)
├── semver@2.2.1
├── rc@0.5.5 (strip-json-comments@0.1.3, deep-extend@0.2.11, ini@1.3.3, minimist@0.0.10)
├── fs-extra@0.8.1 (jsonfile@1.1.1, rimraf@2.2.8, ncp@0.4.2, mkdirp@0.3.5)
├── method-override@2.3.1 (methods@1.1.1, vary@1.0.0, parseurl@1.3.0, debug@2.1.1)
├── anchor@0.10.2 (validator@3.22.2)
├── ejs-locals@1.0.2
├── ejs@0.8.8
├── grunt-cli@0.1.13 (findup-sync@0.1.3, nopt@1.0.10, resolve@0.3.1)
├── grunt-sync@0.0.8 (promised-io@0.3.3)
├── sails-disk@0.10.7 (waterline-errors@0.10.1, async@0.2.10, waterline-criteria@0.11.1, waterline-cursor@0.0.5)
├── captains-log@0.11.11 (rc@0.3.5)
├── glob@3.2.11 (inherits@2.0.1, minimatch@0.3.0)
├── i18n@0.5.0 (sprintf@0.1.5, debug@2.1.1, mustache@1.1.0)
├── grunt-contrib-coffee@0.10.1 (chalk@0.4.0, coffee-script@1.7.1)
├── grunt-contrib-cssmin@0.9.0 (chalk@0.4.0, clean-css@2.1.8, maxmin@0.1.0)
├── grunt-contrib-jst@0.6.0 (chalk@0.4.0, grunt-lib-contrib@0.7.1)
├── include-all@0.1.6 (underscore.string@2.3.1)
├── prompt@0.2.14 (revalidator@0.1.8, pkginfo@0.3.0, read@1.0.5, utile@0.2.1, winston@0.8.3)
├── sails-generate@0.12.2 (sails-generate-api@0.10.0, sails-generate-gruntfile@0.10.10, sails-generate-new@0.10.18, async@0.2.10, sails-generate-generator@0.10.11, sails-generate-adapter@0.10.4, sails-generate-views-jade@0.10.3, sails-generate-views@0.10.3, sails-generate-sails.io.js@0.11.5, sails-generate-backend@0.12.0, sails-generate-frontend@0.11.2, sails-generate-model@0.10.9, sails-generate-controller@0.10.7)
├── lodash@2.4.1
├── grunt-contrib-uglify@0.4.1 (chalk@0.4.0, maxmin@0.1.0, uglify-js@2.4.16)
├── sails-util@0.10.4 (json-stringify-safe@5.0.0, node-switchback@0.0.2, optimist@0.6.1, underscore.string@2.3.3)
├── grunt-contrib-watch@0.5.3 (tiny-lr@0.0.4, gaze@0.4.3)
├── waterline@0.10.18 (switchback@1.1.3, waterline-criteria@0.11.1, waterline-schema@0.1.17, bluebird@2.9.13, deep-diff@0.3.0)
├── express@3.16.0 (basic-auth@1.0.0, merge-descriptors@0.0.2, escape-html@1.0.1, range-parser@1.0.0, fresh@0.2.2, vary@0.1.0, media-typer@0.2.0, parseurl@1.2.0, methods@1.1.0, buffer-crc32@0.2.3, depd@0.4.4, debug@1.0.4, commander@1.3.2, proxy-addr@1.0.1, send@0.8.1, mkdirp@0.5.0, connect@2.25.0)
├── grunt@0.4.2 (which@1.0.9, dateformat@1.0.2-1.2.3, eventemitter2@0.4.14, getobject@0.1.0, async@0.1.22, hooker@0.2.3, nopt@1.0.10, rimraf@2.0.3, exit@0.1.2, minimatch@0.2.14, glob@3.1.21, lodash@0.9.2, coffee-script@1.3.3, underscore.string@2.2.1, iconv-lite@0.2.11, findup-sync@0.1.3, js-yaml@2.0.5)
├── skipper@0.5.5 (string_decoder@0.10.31, dot-access@0.0.3, skipper-disk@0.5.4, async@0.2.10, debug@2.1.1, multiparty@3.2.10, connect@2.25.10)
├── express-handlebars@1.0.3 (graceful-fs@3.0.5, promise@5.0.0, semver@3.0.1, glob@4.4.1, handlebars@2.0.0)
├── grunt-contrib-less@0.11.1 (async@0.2.10, chalk@0.4.0, maxmin@0.1.0, less@1.7.5)
└── sails-hook-sockets@0.11.20 (semver@4.3.1, machinepack-urls@3.1.1, socket.io@1.3.4)`

@mastermind1981 it doesn’t look like you’re using nvm, unless you have it installed into ~/.node
nvm will automatically prepend the node bin path for the installed modules
I use homebrew to install nvm, so:
kris git[master] ~/src/oss/sane
→ type npm && type node
npm is hashed (/Users/kris/.nvm/versions/io.js/v1.4.1/bin/npm)
node is /Users/kris/.nvm/versions/io.js/v1.4.1/bin/node

as you can see, nvm has made both npm and node available on the path.
similarly, after installing sails to global modules:
kris git[master] ~/src/oss/sane
→ type sails
sails is /Users/kris/.nvm/versions/io.js/v1.4.1/bin/sails

one thing to check for is if you have a filed called ~/.npmrc, sometimes people have been instructed to manipulate this file. If you have, then it might break how npm works when installed with nvm.

It's properly installed
type npm && type node
npm is hashed (/Users/dev/.nvm/versions/node/v0.12.0/bin/npm)
node is hashed (/Users/dev/.nvm/versions/node/v0.12.0/bin/node)

and a ls in my  .~/node/bin displays
lrwxr-xr-x  1 root  staff    35B 17 fév 17:07 bower -> ../lib/node_modules/bower/bin/bower
lrwxr-xr-x  1 dev   staff    39B 17 fév 03:16 grunt -> ../lib/node_modules/grunt-cli/bin/grunt
lrwxr-xr-x  1 root  staff    36B 17 fév 17:07 gulp -> ../lib/node_modules/gulp/bin/gulp.js
lrwxr-xr-x  1 root  staff    44B 27 fév 15:48 node-gyp -> ../lib/node_modules/node-gyp/bin/node-gyp.js
lrwxr-xr-x  1 root  staff    38B 27 fév 18:38 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxr-xr-x  1 root  staff    38B 28 fév 00:23 sails -> ../lib/node_modules/sails/bin/sails.js
lrwxr-xr-x  1 root  staff    33B 17 fév 17:07 yo -> ../lib/node_modules/yo/lib/cli.js

and here is the content of my .npmrc
prefix = /Users/dev/.node
prefix = /Users/dev/.node
prefix = /Users/dev/.node
prefix=/Users/dev/.node

Right, nvm doesn't know anything about ~/.node.
$ rm -rf ~/.npmrc ~/.node

and now you should be able to properly install sails.

it works great thanks you very much .
Could you explain to me the solution why removing the folders makes it work?

the .npmrc setting prefix key was causing npm to symlink the bin/* for any modules to ~/.node/bin/*, when they should have been ~/.nvm/versions/{node|io.js}/v{version}/bin/*.  nvm will set the path to the current node's global node_modules.  npm will create the symlink when installing a module that has a bin, if the .npmrc is incorrect, it will to symlink to a nonexistent file.
nvm maintains separate node_modules and npm versions for each version of node that it has installed.  so, if you were to switch node versions, the installed modules would be stable to that version.  The reason for this is that some node modules use native compilation, like bcrypt.  Each version of node has slight variations in how native interfaces are exposed, so nvm keeps your installed modules separate to compensate.
I hope that answers your question.

Very clear so the maximum of people will profit of this explanation. Thank you once again for your reactivity. chapeau

Thank you @kriswill. It works like a charm for me. =)

I'm having a similar issue when I run npm update from the project root directory. I got the following error;
grunt-contrib-less@0.11.1 node_modules/grunt-contrib-less
├── chalk@0.4.0 (has-color@0.1.7, ansi-styles@1.0.0, strip-ansi@0.1.1)
├── async@0.2.10
├── maxmin@0.1.0 (pretty-bytes@0.1.2, gzip-size@0.1.1)
├── lodash@2.4.1
└── less@1.7.5 (graceful-fs@3.0.6, mime@1.2.11, source-map@0.1.43, mkdirp@0.5.0, clean-css@2.2.23, request@2.40.0)
npm ERR! Darwin 14.1.0
npm ERR! argv "/Users/Brad/.nvm/versions/node/v0.12.0/bin/node" "/Users/Brad/.nvm/versions/node/v0.12.0/bin/npm" "update"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! path /Users/Brad/Documents/synchro/synchroApi/node_modules/sails/node_modules/grunt-contrib-jst/node_modules/chalk/node_modules/.bin/strip-ansi
npm ERR! code EEXIST
npm ERR! errno -17

npm ERR! EEXIST, symlink '/Users/Brad/Documents/synchro/synchroApi/node_modules/sails/node_modules/grunt-contrib-jst/node_modules/chalk/node_modules/.bin/strip-ansi'
File exists: /Users/Brad/Documents/synchro/synchroApi/node_modules/sails/node_modules/grunt-contrib-jst/node_modules/chalk/node_modules/.bin/strip-ansi
Move it away, and try again.

My $PATH;
/Users/Brad/.nvm/versions/node/v0.12.0/bin:
/Users/Brad/.nvm/versions/node/v0.12.0/bin:
/Users/Brad/.npm-packages/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/.npm-packages/lib/node_modules:
Here is a link to the npm-debug.log  https://gist.github.com/bmwertman/8e8b943e7608c36286af/revisions

have you tried this?
rm -rf ~/.npmrc ~/.node

I have and have since found that this issue was stemming from upgrading my node version to 0.12.0 using nvm while my npm version was still several versions behind. rolling node back to 0.10.34 cleared this up.

authors: KennedyTedesco bmwertman kriswill mastermind1981


text:
Update robotframework from 4.0 to 4.1.3

This PR contains the following updates:

Package
Update
Change

robotframework
minor
==4.0 -> ==4.1.3

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!

@balena-ci retest

repo: balena-io/autohat


text:
Document Symbol and Workspace symbol descriptions show non alpha numeric characters

Description:
Document symbol and workspace symbol descriptions contain symbol meta information
Affected Versions:
v0.990.2 at least

Check service names with $ sign.

Fix has been merged and hence closing

authors: hevayo nadeeshaan

repo: ballerina-platform/ballerina-lang


text:
Move Transactions internal module to a stdlib

Description:
Transaction internal modules used in desugar should not be exposed to users and they are not a part of stdlib. so that module has to be moved out to a different repo.

Let's go with the repo name "module-ballerinai-transactions"

Moved to stdlib in https://github.com/lasinicl/ballerina-lang/tree/move-trans-internal

authors: gimantha lasinicl mohanvive


text:
[Semantic API] Remove inclusive() method or implement it in a better way

Currently, the inclusive() method in record type symbol relies on the sealed field in the internal record type. But the sealed field is not indicative of an inclusive record type descriptor. Therefore, use of this API may lead to incorrect assumptions about the type descriptor. Need to either properly implement this (for which we may have to keep track of whether the typedesc is an inclusive one or not) or remove this altogether.

Closing since this was fixed in #27679

Closing since this was fixed in #27679


text:
Filter-out the first parameter for lang-lib method calls

Description:
LS suggestions received for lang-lib method-calls filter out the first parameter. but this details is currently present in the documentation. As this may mislead the users when we show the parameter suggestions in the statement-editors parameter tab we need to filter out the first param for lang-lib method calls from the lang-server's documentation endpoint (BallerinaSymbolService's getSymbol service)
Describe your solution(s)
We need to check if the the MethodCall belongs to a Lang-lib, if so we ignore documentation related to the first param of the method.
https://github.com/ballerina-platform/ballerina-lang/blob/master/language-server/modules/langserver-core/src/main/java/org/ballerinalang/langserver/common/utils/CommonUtil.java#L214
Suggested Labels (optional):

Team/vscode

Closing the issue as all the prs to master, 2201.1.x and 2201.2.x branches have been merged


text:
Disable failing test in Service test

Purpose
$subject.

Codecov Report

Merging #15731 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #15731      +/-   ##
============================================
- Coverage      6.91%    6.85%   -0.06%
+ Complexity     1787     1775      -12
============================================
  Files          1384     1384
  Lines         70615    70614       -1
  Branches       9076     9075       -1
============================================
- Hits           4882     4841      -41
- Misses        65236    65274      +38
- Partials        497      499       +2

Impacted Files
Coverage Δ
Complexity Δ

...va/org/ballerinalang/stdlib/task/service/Stop.java
0% <0%> (-31.58%)
0% <0%> (-2%)

...a/org/ballerinalang/stdlib/task/actions/Pause.java
0% <0%> (-29.42%)
0% <0%> (-2%)

.../org/ballerinalang/stdlib/task/actions/Resume.java
0% <0%> (-29.42%)
0% <0%> (-2%)

...ang/stdlib/task/objects/ServiceWithParameters.java
46.42% <0%> (-17.86%)
4% <0%> (ø)

...allerinalang/stdlib/task/objects/AbstractTask.java
56.66% <0%> (-15%)
7% <0%> (-3%)

...lang/stdlib/task/impl/TaskServerConnectorImpl.java
42.85% <0%> (-14.29%)
2% <0%> (-1%)

...a/org/ballerinalang/stdlib/task/objects/Timer.java
74.13% <0%> (-12.07%)
12% <0%> (-1%)

...rg/ballerinalang/stdlib/task/service/Register.java
30% <0%> (-10%)
1% <0%> (-1%)

...g/messaging/artemis/ArtemisTransactionContext.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

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 5c2b2e8...cc4d6d9. Read the comment docs.

authors: Bhashinee codecov-io


text:
Update BBEs

Purpose
Fixes #19107
Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #19134 into ballerina-1.0.x will decrease coverage by 4.78%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           ballerina-1.0.x   #19134      +/-   ##
===================================================
- Coverage            20.51%   15.73%   -4.79%
===================================================
  Files                   52       47       -5
  Lines                 1394     1265     -129
  Branches               216      197      -19
===================================================
- Hits                   286      199      -87
+ Misses                1095     1053      -42
  Partials                13       13

Impacted Files
Coverage Δ

composer/packages/tracing/src/ToolBar.tsx

composer/packages/tracing/src/TraceList.tsx

composer/packages/tracing/src/DetailView.tsx

composer/packages/tracing/src/TraceLogs.tsx

composer/packages/tracing/src/index.ts

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 c04f937...afc7316. Read the comment docs.

authors: codecov-io wggihan


text:
[2201.9.x] Introduce transactionAutoCommitTimeout and transactionCleanupTimeout configuration values for transactions

Purpose
Introduces new configurations to prevent premature commits of long-running transactions before reaching the commit phase.
Related #42922
Approach
This PR introduces two new configurations values for transactions, transactionAutoCommitTimeout and transactionCleanupTimeout.
ballerinai-transaction PR: https://github.com/ballerina-platform/module-ballerinai-transaction/pull/549
Samples
You can change the Config.toml with these two new configs as below.
[ballerina.lang.transaction]
transactionAutoCommitTimeout=120
transactionCleanupTimeout=600

Remarks
ballerinai-transaction PR: https://github.com/ballerina-platform/module-ballerinai-transaction/pull/549
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Tracked with https://github.com/ballerina-platform/ballerina-release/issues/2727

authors: dsplayerX gabilang


text:
Add OpenAPI spec and generated client

Purpose
Integrate the new Twitter (X) OpenAPI specification (Twitter API V2) by generating the client, types, and utilities for the updated API.
Changes

Added the new Twitter (X) OpenAPI spec (Twitter API V2) to the project.
Generated client code based on the new API specification.
Generated type definitions for the updated API endpoints.
Generated utility functions to support the new client and type definitions.

we also need to add a sanitations.md file including all the sanitations we did on the original spec and, the exact command we used to generate the client using the openAPI tool. (A example PR with the expected file structures can be found in https://github.com/ballerina-platform/module-ballerinax-asana/pull/2/files)

@vish-mv lets add the missing docs/license.txt file.

authors: NipunaRanasinghe vish-mv


text:
In Client Connector Action it is mandatory to have a message as a parameter even if it is a GET

When we trying to perform a action like GET on a client connector it is mandatory to have three parameters. Otherwise this[1] error appear.

Final parameter is of type message. This is ideal for a action like POST as there can be a payload that need to be sent. But it is not mandatory for a action like GET as there is no payload to be sent and might not have user set headers. So when developing we have to provide a empty variable of type message to use the GET action.
Is there a reason for message parameter to be mandatory in connector actions?
Can we add like a default parameter if user doesn't provide a parameter value, like in javascript[1]?
ex:-
function setBackgroundColor(element, color = 'rosybrown') {
element.style.backgroundColor = color;
}
[1]. https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Functions/Default_parameters

@shafreenAnfar , @sameera-jayasoma
When we are using a function to invoke a HTTP endpoint, with this approach, it becomes mandatory to define message m = {} before doing the GET call. In resources, we do not have an issue because we already have a message m object in the scope.
Following works with an empty new message.
message m = {};
m = http:ClientConnector.get(endpoint1, "/");

Hence, there is must be no reference to any context from m in the get method and should be able to remove.
Can we remove this parameter for the next release?

Hi All,
This is as per the current design. Mainly influenced by the constraint of not letting function over-loading in ballerina. However, we are in the process of refactoring both server and client connector and as a part of it this is also considered. Following is the issue created for this.
https://github.com/ballerinalang/ballerina/issues/4183
Hence, I will be closing this issue as it will be covered by the above issue.

authors: NipunaMarcus maheeka shafreenAnfar

repo: ballerinalang/ballerina


text:
Back function between views does not work (intermittent)

To reproduce:

Visit at least two items in the side navigation (such as "States" and "Map").
Go back to "States," and select a secondary view from the top nav.
Click a component to activate a popup.
Click outside the popup or click Back. This will close the popup.
Click Back again. This ought to take you to the previous view (the main "States" page). Instead, the URL changes accordingly (to just "/states"), but the current view will not be updated.

Browser and version?
On Thu, Feb 4, 2016, 18:52 mafachu notifications@github.com wrote:

To reproduce:
1 Visit at least two items in the side navigation (such as "States" and
"Map")
2 Go back to "States," and select a secondary view from the top nav
3 Click a component to activate a popup
4 Click outside the popup or click Back This will close the popup
5 Click Back again This ought to take you to the previous view (the main
"States" page) Instead, the URL changes accordingly (to just "/states"),
but the current view will not be updated
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/1132.

I get the same result in all of the following browsers on Mac OS X Yosemite:
Firefox 44
Chrome 45
Safari 9.0.2

What version of Home Assistant are you running?

0.12.0 and 0.13.0.dev0

Steps 3 and 4 are not necessary to reproduce this. Clicking Back from a secondary view to /states after having also visiting a secondary pane (such as /map or /history) will not update the view back to the main /states page.
The problem seems to have to do with the state.view property being blown away on any pane other than /states. I submitted a pull request (#12) for home-assistant-js that should address this. Coincidentally the proposed fix also appears to address Issue #946.

This should have been fixed with the 0.13 release

authors: balloob mafachu rmkraus

repo: balloob/home-assistant


text:
fix(): claim number formatter can accept small x and transfer it uppe…

…rcase
Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

:rocket: Welcome to Baloise ChatOps based GitOps Bot :tada:
- If you want to enable preview environments for this PullRequest, comment with `/preview`.
- If you want to disable the preview environment for this PR, comment with `/undeploy`.
- If you need help or want to see the docs, comment with `/help`.

Make sure to refresh this page after submitting a command.
Preview environments can be redeployed automatically if you enable the webhook for updates to the source branch. :new:

Have fun building awesome apps! :hammer:  :whale2:  :truck:  :ship:

authors: incubator-tekton nobilo

repo: baloise/design-system


text:
Organize CH Open Business Lunch in Basel @ Baloise

https://www.ch-open.ch/workinggroups/open-business-lunch/
Turnus every 2nd Open-X Day
Donnerstag den 20.02.2020  - see #172
Donnerstag den 23.04.2020  - see #173
Donnerstag den 25.06.2020  - see #174
Donnerstag den 24.09.2020  - see #175
Donnerstag den 26.11.2020  - see #176
Location
https://www.baloisepark.ch/de/baloise-park/zahlen-fakten.html
Layout
8.30 - 9.00 : internal pitching @ Open X-Day by @MarkusTiede or @joachimprinzbach
10.30 - 11.00: arrival external participants
11.00 - 12.00: welcome / talk / Q&A
12.00 - 13.00: lunch

Having this https://github.com/baloise/baloise.github.io/issues/12 would be helpful.

title of the OBL
language
slides EN - abstract & presentation DE
abstract
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
speaker
FQN of speaker - details / title e.g. from LinkedIn
time
10.30 - 11.00: arrival external participants
11.00 - 12.00: welcome / talk / Q&A
12.00 - 13.00: lunch
location
https://baloise.github.io/about.html

repo: baloise/open-source


text:
Match widget with pipeline.parameters back & forth

To force a value back in the UI when reloading a tuning, you need to update the Control values... not only the parameters dictionary.

[ ] before running the pipeline, we need to a way to verify that all controls are connected properly to a filter / param (this should be automatic as long as you're using decorators)
[ ]  should be replaced by a unique identifier (like a hash!)!

To clarify things
right now, each GUI has a
self.ctrl which is basically a different view (a dict) of self.pipeline.slider
self.ctrl =  {slider_name1: slider1 , ... } where slider_name1 = slider1.name
self.pipeline.slider = [ slider1, slider2, ....]

license: Unlicense


text:
Chrome/Safari can't handle jQuery in State.data

When asigning a jQuery object to State.data via
History.pushState({my_oject: $('body')}, "title", "http://url.com");

Chrome/Safari throw "TypeError: Converting circular structure to JSON" exception. Firefox processes the request just fine (if you've implemented my fix in issue #93).
This happens because History.getStateString invokes JSON.stringify(cleanedState). I understand this is only used in History.getIdByState help identify unique states. A better method should be developed to ID states since Chome and Safari's JSON encoding is crap.

This is still happening for me using the jquery html4+html5 bundle. Though I'm not sure the native history API lets you store anything beyond a string as a key/value in the state object in any case.

I use native version (with Prototype.js) -- \balupton-history.js-40489d1.zip\balupton-history.js-40489d1\scripts\bundled\html4+html5\native.history.js.
I've got "Converting circular structure to JSON'' error in Chrome (v17) for my site.
I've got "Out of memory" error in IE8.
It works fine in Firefox (v8).

authors: brianfegan clphillips ggierlik


text:
Running into invalid class errors after upgrade to 1.6, does not occur on lower versions.

Running into the following errors as the PeriodicJobBuilder.GetAllJobs(); method is called and it loops through all classes within the assembly looking for the recurring job attributes. Is there a way to exclude/include types that would use the attribute rather than looking at all types?
Could not load type 'Microsoft.EntityFrameworkCore.Metadata.RelationalModelAnnotations' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Could not load type 'Microsoft.EntityFrameworkCore.Metadata.RelationalPropertyAnnotations' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Could not load type 'Microsoft.EntityFrameworkCore.Metadata.Internal.RelationalFullAnnotationNames' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. <s:Microsoft.AspNetCore.Hosting.Diagnostics>
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load type 'Microsoft.EntityFrameworkCore.Metadata.RelationalModelAnnotations' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Could not load type 'Microsoft.EntityFrameworkCore.Metadata.RelationalPropertyAnnotations' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Could not load type 'Microsoft.EntityFrameworkCore.Metadata.Internal.RelationalFullAnnotationNames' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

   at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
   at System.Reflection.RuntimeModule.GetTypes()
   at Hangfire.RecurringJobAdmin.PeriodicJobBuilder.GetAllJobs()
   at Hangfire.RecurringJobAdmin.ConfigurationExtensions.UseRecurringJobAdmin(IGlobalConfiguration config, Assembly assembly)

Hi, @geoffreytran thanks for report this issue, I will fix this issue in the next release.
In the next release, I changed the way how the plugin gets all jobs by attribute.
Please wait for the next release.

Hi @geoffreytran, I released a new version, try it and let me know.

Great! thanks! I did find another issue, I'll create a new one for that.

authors: bamotav geoffreytran


text:
Usage1：CUDA_VISIBLE_DEVICES=0 python3 main.py --c  ./Config/config.cfg  --t_model bilstm --train -p

Usage2：CUDA_VISIBLE_DEVICES=0 python3 main.py --c  ./Config/config.cfg  --t_model cnn --train -p
Both CNN and bilstm models were run on the same data set, but the best results I got were both The Current Best Dev Accuracy: 82.110092, Locate on 12 Epoch.
The Current Best Test Accuracy: accuracy = 84.404174%

CUDA_VISIBLE_DEVICES=0 python3 main.py --c ./Config/config.cfg  --train -p
modify config.cfg for choose cnn or bilstm, see Config readme

Both models ran separately, but the results were the same

All the same

The code I ran and the data set I used was the one you put on github. I didn't make any changes.

modify config.cfg to choose model
model_cnn = True
model_bilstm = False

Thank you, I see

My best dev set accuracy is 2% lower than you

test set accuracy is same as me ?

authors: bamtercelboo feiyangdezhu


text:
🛑 MXN Celo On-ramps is down

In f89d2df, MXN Celo On-ramps ($QUOTE_ENDPOINT) was down:

HTTP code: 500
Response time: 1381 ms

Resolved: MXN Celo On-ramps is back up in 7f3f583 after 10 minutes.

repo: bandohq/upptime-monitor


text:
JSPatch.com更新最新的Framework之后忘记调用sync了

按照之前的版本的习惯，只调用了startWithAppKey
版本已经ready for sale了
有没有办法补救？

没办法了，
不好意思，文档没有强调这点

好吧，我其实看到了sync的介绍。
但是在.h里面，对startWithAppKey的介绍有“传入在平台申请的 appKey。会自动执行已下载到本地的 patch 脚本。”
看到“自动”...“下载” 然后就忘了sync这回事了。


text:
fixed https://github.com/gameboyVito/react-native-ultimate-listview/i…

…ssues/34

还要吗

fix: https://github.com/gameboyVito/react-native-ultimate-listview/issues/30

还要吗

要的，测试过了。bug都不算很严重因为这个库很老，看到你还在频繁更新就PR了 🤓

后面有空可以重新搞一下ListView。  最近真是忙成狗

我合并了哦。 要发布一个版本吗

后面有空可以重新搞一下ListView。 最近真是忙成狗

福报好好享受，合并发布吧，我去看看👀

3.3.4


text:
Add JWT Auth backend support to bank-vaults cli

Add support for JWT Authentication backend. This is mainly a cut and paste and change from the kubernetes one

Allow for custom path mount
Tested locally with a manually started vault since i could not find an included testing for this
Not tested with the operator yet while running in-cluster

 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.

Hi @primeroz, looks great! Could you please sign the CLA as well so I can merge the PR?

@bonifaido I signed the CLA, twice actually, but i can't see the badge or the CI step change. Maybe i am doing something wrong

The GitHub user who made the commits and your user who created the PR differs (I think this causes the issue). Could you rebase the commits to be made by the same user?

@bonifaido I think messed this up i will open a new merge request all from the same user

No problem @primeroz.

authors: CLAassistant bonifaido primeroz

repo: banzaicloud/bank-vaults


text:
Dockerfile improvement

Move nsswitch, tzdata, ca-certificates to builder stage
Dockerfile create a scratch container
Add new Dockerfile.alpine

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
fixes #2160

License
Apache 2.0

What's in this PR?

We want to use scratch instead of alpine
Why?

e.g: security reason, size, etc
Additional context

Checklist

[x] Implementation tested (with at least one cloud provider)
[x] Error handling code meets the guideline
[x] Logging code meets the guideline (TODO)
[x] OpenAPI and Postman files updated, client regenerated (make generate-client) (if needed)
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

Just to make it clear: the primary reason is security. Size does not really matter (alpine is about +6MB)

authors: kozmagabor sagikazarmark

repo: banzaicloud/pipeline


text:
ServiceAccount defaults to 'default' when creating operated resources

Describe the bug
Operated resources are created without a serviceAccount specified, causing the resources to use the default service account for the namespace.  In many environments with restrictive pod security policies, service accounts are created with least privilege necessary to instantiate resources.
Steps to reproduce the issue:
Create any object-kind in thanos-operator that prompts the generation of a deployment, see that said resource is running in 'default' service account instead of the service account installed with the helm chart.
Expected behavior
The thanos-operator would utilize the service account generated by the helm chart, or have the ability to specify the service account to be used when creating operated resources.
Screenshots
ns/monitoring       pod/thanos-operator-6cf7b55df6-jjv6v                                 sa/thanos-operator                               psp/readwritefs                                   state/Running
ns/monitoring       pod/thanos-objstore-bucket-546478d96c-xqzbq                          sa/default                                       psp/restricted                                    state/PendingCreateContainerConfigError
ns/monitoring       pod/thanos-objstore-compactor-5ffd7b764b-9tjjt                       sa/default                                       psp/restricted                                    state/PendingCreateContainerConfigError

Additional context
Utilizing helm-chart version 0.1.0 / operator version banzaicloud/thanos-operator:0.1.0

i was able to use the thanos-operator service account in the objectstore-bucket and objectstore-compactor deployments:
apiVersion: monitoring.banzaicloud.io/v1alpha1
kind: ObjectStore
metadata:
  name: objectstore
spec:
  config:
    mountFrom:
      secretKeyRef:
        name: thanos
        key: object-store.yaml
  bucketWeb:
    label: cluster
    deploymentOverrides:
      spec:
       template:
        spec:
          serviceAccountName: {{ include "thanos-operator-stack.serviceAccountName" $ }}
  {{- with index .Values "thanos-operator" "compact" }}
  compactor:
    deploymentOverrides:
      spec:
        template:
          spec:
            serviceAccountName: {{ include "thanos-operator-stack.serviceAccountName" $ }}
    {{- if .persistentStorage.enabled }}

I can't figure out how to customize the storeendpoint-store service account which blocks me from leveraging gcp workload identity.

authors: PeterGrace joshuasimon-taulia

repo: banzaicloud/thanos-operator


text:
不同类型数据源

请问不同类型数据源要怎么配置？比如oracle与mysql同时使用，主键策略配置

https://github.com/baomidou/dynamic-datasource-spring-boot-starter

authors: onlyforwork qmdx

repo: baomidou/mybatis-plus


text:
一切批量操作无法成功。

当前使用版本(必填,否则不予处理)
mybatisplus3.0.5
该问题是如何引起的？(确定最新版也有问题再提!!!)
应为公司代码原因无法升级到新版本。目前只使用这个版本
重现步骤(如果有就写完整)
正常调用savebatch，以及updateBatchById等操作、
报错信息
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==>  Preparing: UPDATE customer SET customer_name=?, phone=?, media_sources=?, creation_time=?, distribution_resources_status=?, color_status=?, resource_type=?, integral=? WHERE id=?
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==> Parameters: 钱氏(String), 18902059345(String), ,电视(String), 2021-06-04 11:30:22.0(Timestamp), 0(Integer), 0(String), 2(String), 0(Integer), 106(Long)
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==>  Preparing: UPDATE customer SET phone=?, media_sources=?, creation_time=?, distribution_resources_status=?, color_status=?, resource_type=?, integral=? WHERE id=?
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==> Parameters: 18348603328(String), ,电视(String), 2021-06-04 11:30:22.0(Timestamp), 0(Integer), 0(String), 2(String), 0(Integer), 107(Long)
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==>  Preparing: UPDATE customer SET sales_id=?, customer_name=?, phone=?, media_sources=?, creation_time=?, distribution_resources_status=?, color_status=?, resource_type=?, integral=? WHERE id=?
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==> Parameters: 5(Long), 孙氏(String), 17196317162(String), ,电视(String), 2021-06-04 11:30:22.0(Timestamp), 0(Integer), 0(String), 2(String), 0(Integer), 108(Long)
2021-06-07 17:22:06.296 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==>  Preparing: UPDATE customer SET manager_id=?, phone=?, media_sources=?, creation_time=?, distribution_resources_status=?, color_status=?, resource_type=?, integral=? WHERE id=?
2021-06-07 17:22:06.297 [pool-1-thread-3] DEBUG mapper.CustomerMapper.updateById - ==> Parameters: 58(Long), 17661749487(String), ,电视(String), 2021-06-04 11:30:22.0(Timestamp), 0(Integer), 0(String), 2(String), 0(Integer), 109(Long)
并无报错信息，但是执行语句以及字段也打印出来了，但是成功语句并没有。

请检查事务配置，无法复现。 如无法排查原因，请提供一个demo程序给出链接，重提ISSUE。


text:
Hamed550

https://github.com/barry-far/V2ray-Configs/blob/3f4f77d617c2b39f0e433adb142e5d6e8a94030a/All_Configs_Sub.txt#L7

سلام @Hamedz550
این لینک همیشه بروزه و لینک اشتباهی رو کپی کردی 😀
https://raw.githubusercontent.com/barry-far/V2ray-Configs/main/All_Configs_Sub.txt


text:
类似ios 左右翻页

能不能写成，类似ios那种，左右翻页，有特效的那种

No.

repo: barteksc/AndroidPdfViewer


text:
Question: Using fluid-tailwind classes within @tailwindcss/typography config

Hi,
I'm relatively new to Tailwind and its plugins, and I'm trying to use fluid-tailwind with the @tailwindcss/typography plugin.
Specifically, I'd like to overwrite the default font-size of headings and make them responsive without the use of breakpoints.
Is it possible to achieve this when using @tailwindcss/typography? If using @apply isn't possible currently, are there any other ideas you can suggest (besides writing clamp functions)?
I've had no luck making it work with this config tailwind.config.js:
const config: Config = {
  content: {
    files: [
      './src/pages/**/*.{js,ts,jsx,tsx,mdx}',
      './src/components/**/*.{js,ts,jsx,tsx,mdx}',
      './src/app/**/*.{js,ts,jsx,tsx,mdx}',
    ],
    extract,
  },
  theme: {
    fontSize,
    screens,
    fluid: (({ theme }) => ({
      defaultScreens: [theme('screens.sm'), theme('screens.xxl')],
    })) satisfies FluidThemeConfig,
    extend: {
      typography: ((theme) => ({
        DEFAULT: {
          css: {
            h1: {
              '@apply ~text-xl/2xl': {},
            },
          },
        },
      })) satisfies ResolvableTo<Record<string, unknown>>,
    },
  },
  plugins: [fluid, typography],
};

Thanks in advance for your help!

Good question! This may be a Tailwind bug/limitation but I'm waiting to hear back on their Discord. I suppose you could use the prose- variants to accomplish this in the meantime, i.e.
<div class="prose prose-h1:~text-xl/2xl">

Tailwind Play example

authors: abredikis barvian

repo: barvian/fluid-tailwind


text:
Simplified ARIA Label Description for Clarity

What changed? Why?
I noticed a small area for improvement in the code where the description of the ARIA label for the main navigation contains the word "The":
description: 'The ARIA label for the main navigation',

This wording is perfectly functional, but the word "The" doesn't add significant value and can be omitted to make the code more concise. The revised version is:
description: 'ARIA label for main navigation',

Notes to reviewers

Clarity: Simplifying this phrase improves readability without sacrificing meaning.
Consistency: It aligns better with common ARIA description practices, which often favor concise and direct language.
Code Quality: Small refinements like this contribute to maintaining clean, professional, and user-friendly code.

Thank you for considering this improvement!
How has it been tested?
Localy.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@mdqst
Thanks for this contribution; let's leave as-is for now 🙏

authors: cb-heimdall mdqst wbnns

repo: base-org/web


text:
Handling for bad search requests

I added code to abort the processing of the result set when a 400 status code has been returned to account for issue #103 (CLIENTS-597). Added a new test for this case.

@karlra let me know if this is an acceptable solution for you.

@lukebakken @javajolt Updated code as we discussed offline.

:ship: :it:

Tests are still passing post last commit. Merging!

authors: christophermancini lukebakken

repo: basho/riak-php-client


text:
Fix bz1235: vnodes crashing when receiving unexpected handoff

Sync messages sent to vnodes when they are exiting cause them to crash:
https://issues.basho.com/show_bug.cgi?id=1235
After talking to Jon, the decision for now is to prevent vnodes from crashing, and pass an error up to the handoff receiver. The handoff receiver will check for the error, and exit. This will cause the handoff sender to crash, but this an acceptable crash (compared to crashing vnodes). The handoff will eventually be restarted in the future against the proper target node, and complete successfully.

Code looks good, will try and execute it later.

+1 merge.

Just noticed a compile warning on src/riak_core_handoff_receiver.erl:109: Warning: variable 'Err' is unused.  Would be good to clean up before merge.

authors: jonmeredith jtuple


text:
DX-389 Remove Secret from Webhooks

[Urgent] Removed Secrets docs and aligned with Responses.

Bypassing the Review for this one.

repo: basiqio/api-ref


text:
Feature Request: combined RBG + colour temp

i may be wrong but current options allow you to either use the main light with kelvin adjustment OR the RGB light with colour changes.
I would love to be able to have an additional option to use full brightness (and truer daylight colours) of the main white light but the full dim coloured glow of the RGB lights during the night. perhaps a set time to swithc with 60+ second transition as it is difficult to match between the two. I feel like the options already are supposed to support this but I seem to only be able to select RBG or colour temp at the moment?
It would also be nice to be able to select a nighttime colour. In the past I had an automation to turn the bathroom lights to 3% brightness dark purple which ment you dont need to turn the light on to see and minimise impact on sleep. Guess I could easily keep this running but would be nice to have it integrated.
Also, love the graphs in documentation showing how lights change through the day. could these graphs be drawn at the bottom of the options to show you what you have configured?
Im looking forward to seeing this as a native integration in Hassio 0.117!

I have added two switches:

switch.adaptive_lighting_adapt_brightness_NAME
switch.adaptive_lighting_adapt_color_NAME

With it I think you will be able to do what you want.
See the docs here https://deploy-preview-14877--home-assistant-docs.netlify.app/integrations/adaptive_lighting/

@nickg90, could you try the latest commit, I've added a separate_turn_on_commands option.

See https://github.com/basnijholt/adaptive-lighting/issues/29 also.

@nickg90, could you try the latest commit, I've added a separate_turn_on_commands option.

Yes, I think this would let me automate to get what I want more easily. perhaps another suggestion could be to set a sleep RGB colour?
Also, it would be very useful if the integration options included an graph to show how the light brightness changes over 24 hours. im not sure if this is possible, perhaps a link to an graph or something similar?

You can add these sensors https://github.com/basnijholt/home-assistant-config/blob/93d42dba1fc0d1eeaf33e1c2260807bc3cc6d7b4/includes/sensors.yaml#L264-L282

thanks, got graphs working now 👍

Please reopen if you have any more issues.

repo: basnijholt/adaptive-lighting


text:
Fixed env error + edited readme.md

Fixed the following error
"\modrinth-mod-updater-main\updater.py", line 198, in
check_and_update_mod_versions(json_data, db_cursor, log_file_path)
File "\modrinth-mod-updater-main\updater.py", line 105, in check_and_update_mod_versions
if file_entry['env']['server'] == 'required':
KeyError: 'env'"

Add to do list as I found further issues

Version checking, see if a mod is for the "selected version here" is downloaded correctly
Engine checking, check if a mod is for forge, fabric, neoforge, etc..

I had to limit to these changes so far but further changes can be done.

repo: bastrian/modrinth-mod-updater


text:
Add ability to specify pre/post actions for build/run/...

This change gives xcodeproj two more attributes for specifying pre/post actions against build/test etc.
It will run before and after build/test/run and will not spit output to build log, so any additional script ran there should be fast and shall not hang.
In terms of the data structure to pass here, three considerations are given here based on this discussion regarding why we should not have a json style compliticated data structure as a type for attr. One point strikes me is that having a complicated data structure as a type for attr makes query filtering attr a very difficult job.
Comparison of three types here:

string_list
Pros: straight forward, it can be a list of scripts but tied to build and pre-action
Cons:, to extend the feature, in worse case we will need 6+ attr for pre/post * build/test/run, right now we can do pre/post * build which is 2 attr.

string_dict
Pros: can be very specific, such as {type: build, name: 'script name', script: 'some script'} Cons: Each attribute can only host one script for either pre/post. Note that we cannot put listin the dict here or we run into ajson style` data structure (DS).

string_list_dict (base is a dict and each key is string and value is a list of string)
Pros: most complicated DS we can get, so it gives the ability to specify at least the type and its scripts:
{'build': [script1, script2, script3...], "run":[script1, script2, script3]} for pre/post (2 attr).
Cons: limited to key value means that we cannot specify name for script unless the string array itself has some special format within it. We cannot specify other fields such as settingsTarget .

Given above, I am choosing string_list_dict here and follow the sample DS listed above. We are using this already in codebase and it is at least better than additional_prebuild_script where it only accepts a single script string
TODO

[ ] Fix specs

Is it intentional to not add the ability to set the "title" for each action in the first iteration?

Would like to see this as well if possible

Is it intentional to not add the ability to set the "title" for each action in the first iteration?

@tinder-maxwellelliott @thiagohmcruz With current data structure it is not possible to add title.
As discussed in the PR description, we can only specify a list of scripts for a "target" (build/test, run or profile etc.)
I don't think title is needed because the script itself is often descriptive enough and the title does not really add any value.
What do you folks think?

Is it intentional to not add the ability to set the "title" for each action in the first iteration?

@tinder-maxwellelliott @thiagohmcruz With current data structure it is not possible to add title.
As discussed in the PR description, we can only specify a list of scripts for a "target" (build/test, run or profile etc.)
I don't think title is needed because the script itself is often descriptive enough and the title does not really add any value.
What do you folks think?

The title is low priority, I think higher priority is making the pre/post the only api we offer to do some unit of work, i.e. removing  Additional prebuild script

Is it intentional to not add the ability to set the "title" for each action in the first iteration?

@tinder-maxwellelliott @thiagohmcruz With current data structure it is not possible to add title.

As discussed in the PR description, we can only specify a list of scripts for a "target" (build/test, run or profile etc.)

I don't think title is needed because the script itself is often descriptive enough and the title does not really add any value.

What do you folks think?

The title is low priority, I think higher priority is making the pre/post the only api we offer to do some unit of work, i.e. removing  Additional prebuild script

@gyfelton +1 to that, my bad I missed the explanation for the title and agree that it's low priority


text:
Bazel plugin not available in remote development mode (JetBrains Gateway)

Are there any plans regarding support of Clion through JetBrains Gateway?

@alice-ks I meant the latter. You are right, I made the wrong assumption that gateway was using a different api which doesn't seem to be the case as it just launches de clion backend server side. But for now Gateway only seems to work with clion 2021.3.1+ so that's most likely the reason the plugin isn't working yet.

Yeah, the plugin hadn't been compatible with CLion 2021.3 yet. It reached compatibility recently and we pushed a compatible version to the beta channel of the public plugin repository yesterday. See https://github.com/bazelbuild/intellij/issues/3001#issuecomment-1011302963.
You could check it out and see whether it works with a Gateway setup in Clion 2021.3.1. I'd be interested to hear your feedback.

Good and bad news! It installs properly on the host machine and I can access the plugin settings. However, the frontend is missing in the Gateway client. Also, Gateway doesn't have the import new project wizard so you have to configure that over VNC/Projector. I get proper highlighting in bazel files, but there is currently (afaict) no way to sync the project.

Thanks for the feedback.
I guess the new project wizard is missing as Gateway has a connection to only one project. Therefore, the regular functionality to switch between projects is generally missing from the IDE, which in turn also means that creating new projects is not possible. I don't think we can do anything on the plugin's side for improvement at the moment.
I'm a bit surprised to hear that the frontend is missing. When I tested the plugin with IntelliJ 2021.3.0, the sync button showed up in the toolbar. Upon a click, it started a sync and even opened the corresponding tool window. Maybe Clion is different to IntelliJ.

Did you try the plugin with IntelliJ 2021.3.0 through the Gateway client?

I tried launching intelij 2021.3.2 from gateway client. I can't see bazel buttons. Note: this is specifically about the gateway client.

Did you ensure that the plugin is installed in the project you accessed with the Gateway client? When I tested this, the Gateway connection created a separate IDE environment, which only had the bundled plugins available. I needed to manually add the Bazel plugin.

Yup. I installed the bazel plugin. This caused the restart of the project.
When it opened again I didn’t see bazel options for that project.
What did you do to make it work?
On Wed, Jan 26, 2022 at 3:02 AM Alice Kober-Sotzek @.***>
wrote:

Did you ensure that the plugin is installed in the project you accessed
with the Gateway client? When I tested this, the Gateway connection created
a separate IDE environment, which only had the bundled plugins available. I
needed to manually add the Bazel plugin.
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/intellij/issues/3152#issuecomment-1022091276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDSYNEKS6R5HGMGUJGEHMDUX7IDFANCNFSM5LTSIMHA
.
You are receiving this because you commented.Message ID:
@.***>

When I installed IntelliJ manually via disk for the "Plugins" section (not "Plugins on host"). I'm seeing this error:
Failed to execute task com.intellij.openapi.project.DumbServiceMergingTaskQueue$QueuedDumbModeTask@2a9c3757. com/intellij/vfs/AsyncVfsEventsPostProcessor

java.lang.NoClassDefFoundError: com/intellij/vfs/AsyncVfsEventsPostProcessor
	at com.google.idea.blaze.base.sync.libraries.ExternalLibraryManager.<init>(ExternalLibraryManager.java:70)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at com.intellij.serviceContainer.ConstructorInjectionKt.instantiateUsingPicoContainer(constructorInjection.kt:52)
	at com.intellij.serviceContainer.ComponentManagerImpl.instantiateClassWithConstructorInjection(ComponentManagerImpl.kt:876)
	at com.intellij.serviceContainer.ServiceComponentAdapter.createAndInitialize(ServiceComponentAdapter.kt:47)
	at com.intellij.serviceContainer.ServiceComponentAdapter.access$createAndInitialize(ServiceComponentAdapter.kt:12)
	at com.intellij.serviceContainer.ServiceComponentAdapter$doCreateInstance$1.compute(ServiceComponentAdapter.kt:41)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:698)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:646)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeInNonCancelableSection(CoreProgressManager.java:237)
	at com.intellij.serviceContainer.ServiceComponentAdapter.doCreateInstance(ServiceComponentAdapter.kt:40)
	at com.intellij.serviceContainer.BaseComponentAdapter.getInstanceUncached(BaseComponentAdapter.kt:113)
	at com.intellij.serviceContainer.BaseComponentAdapter.getInstance(BaseComponentAdapter.kt:67)
	at com.intellij.serviceContainer.BaseComponentAdapter.getInstance$default(BaseComponentAdapter.kt:60)
	at com.intellij.serviceContainer.ComponentManagerImpl.doGetService(ComponentManagerImpl.kt:595)
	at com.intellij.serviceContainer.ComponentManagerImpl.getService(ComponentManagerImpl.kt:569)
	at com.intellij.openapi.client.ClientAwareComponentManager.getFromSelfOrCurrentSession(ClientAwareComponentManager.kt:37)
	at com.intellij.openapi.client.ClientAwareComponentManager.getService(ClientAwareComponentManager.kt:22)
	at com.intellij.openapi.components.ServiceManager.getService(ServiceManager.java:27)
	at com.google.idea.blaze.base.sync.libraries.ExternalLibraryManager.getInstance(ExternalLibraryManager.java:63)
	at com.google.idea.blaze.base.sync.libraries.BlazeExternalLibraryProvider.getAdditionalProjectLibraries(BlazeExternalLibraryProvider.java:38)
	at com.intellij.util.indexing.roots.AdditionalLibraryRootsContributor.getIndexableFiles(standardContributors.kt:125)
	at com.intellij.util.indexing.FileBasedIndexEx.lambda$getIndexableFilesProviders$12(FileBasedIndexEx.java:479)
	at com.intellij.openapi.application.impl.NonBlockingReadActionImpl$Submission.insideReadAction(NonBlockingReadActionImpl.java:521)
	at com.intellij.openapi.application.impl.NonBlockingReadActionImpl$Submission.lambda$attemptComputation$3(NonBlockingReadActionImpl.java:486)
	at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1084)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.lambda$runInReadActionWithWriteActionPriority$0(ProgressIndicatorUtils.java:75)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.runActionAndCancelBeforeWrite(ProgressIndicatorUtils.java:158)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.lambda$runWithWriteActionPriority$1(ProgressIndicatorUtils.java:115)
	at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:57)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:188)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:624)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:698)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:646)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:623)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:66)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:175)
	at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:57)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.runWithWriteActionPriority(ProgressIndicatorUtils.java:112)
	at com.intellij.openapi.progress.util.ProgressIndicatorUtils.runInReadActionWithWriteActionPriority(ProgressIndicatorUtils.java:75)
	at com.intellij.openapi.application.impl.NonBlockingReadActionImpl$Submission.attemptComputation(NonBlockingReadActionImpl.java:486)
	at com.intellij.openapi.application.impl.NonBlockingReadActionImpl$Submission.executeSynchronously(NonBlockingReadActionImpl.java:421)
	at com.intellij.openapi.application.impl.NonBlockingReadActionImpl.executeSynchronously(NonBlockingReadActionImpl.java:186)
	at com.intellij.util.indexing.FileBasedIndexEx.lambda$getIndexableFilesProviders$13(FileBasedIndexEx.java:479)
	at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)
	at java.base/java.util.Iterator.forEachRemaining(Iterator.java:133)
	at java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
	at com.intellij.util.indexing.FileBasedIndexEx.getIndexableFilesProviders(FileBasedIndexEx.java:481)
	at com.intellij.util.indexing.UnindexedFilesUpdater.getOrderedProviders(UnindexedFilesUpdater.java:359)
	at com.intellij.util.indexing.UnindexedFilesUpdater.updateUnindexedFiles(UnindexedFilesUpdater.java:193)
	at com.intellij.util.indexing.UnindexedFilesUpdater.performScanningAndIndexing(UnindexedFilesUpdater.java:532)
	at com.intellij.util.indexing.UnindexedFilesUpdater.performInDumbMode(UnindexedFilesUpdater.java:522)
	at com.intellij.openapi.project.DumbServiceMergingTaskQueue$QueuedDumbModeTask.executeTask(DumbServiceMergingTaskQueue.java:201)
	at com.intellij.openapi.project.DumbServiceMergingTaskQueue$QueuedDumbModeTask.executeTask(DumbServiceMergingTaskQueue.java:185)
	at com.intellij.openapi.project.DumbServiceGuiTaskQueue.lambda$runSingleTask$1(DumbServiceGuiTaskQueue.java:64)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:188)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:624)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:698)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:646)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:623)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:66)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:175)
	at com.intellij.openapi.project.DumbServiceGuiTaskQueue.runSingleTask(DumbServiceGuiTaskQueue.java:62)
	at com.intellij.openapi.project.DumbServiceGuiTaskQueue.lambda$processTasksWithProgress$0(DumbServiceGuiTaskQueue.java:49)
	at com.intellij.util.io.storage.HeavyProcessLatch.performOperation(HeavyProcessLatch.java:79)
	at com.intellij.openapi.project.DumbServiceGuiTaskQueue.processTasksWithProgress(DumbServiceGuiTaskQueue.java:49)
	at com.intellij.openapi.project.DumbServiceImpl.lambda$runBackgroundProcess$13(DumbServiceImpl.java:613)
	at com.intellij.openapi.util.ShutDownTracker.executeWithStopperThread(ShutDownTracker.java:114)
	at com.intellij.openapi.project.DumbServiceImpl.runBackgroundProcess(DumbServiceImpl.java:609)
	at com.intellij.openapi.project.DumbServiceImpl$5.run(DumbServiceImpl.java:587)
	at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:436)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:120)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsync$5(CoreProgressManager.java:496)
	at com.intellij.codeWithMe.ClientId$Companion$decorateFunction$2.apply(ClientId.kt:238)
	at com.intellij.codeWithMe.ClientId$Companion$decorateFunction$2.apply(ClientId.kt:238)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:244)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:188)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:624)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:698)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:646)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:623)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:66)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:175)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:244)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.ClassNotFoundException: com.intellij.vfs.AsyncVfsEventsPostProcessor PluginClassLoader(plugin=PluginDescriptor(name=Bazel, id=com.google.idea.bazel.ijwb, descriptorPath=plugin.xml, path=~/Library/Application Support/JetBrains/JetBrainsClient213.6777.38/plugins/ijwb, version=2022.01.13.0.1-api-version-213, package=null, isBundled=false), packagePrefix=null, instanceId=4, state=active)
	at com.intellij.ide.plugins.cl.PluginClassLoader.loadClass(PluginClassLoader.java:235)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)

	... 100 more

Hey there,
I gave IntelliJ Ultimate 2021.3.2 a shot today with the latest Bazel plugin to try out the beta support for remote development. My setup is roughly macOS to a Linux host and am seeing the same things as the commenters before me -- there's some evidence the Bazel plugin is loading since you can pull up its preferences pane, but core functionality for the Bazel plugin like opening as a Bazel project and syncing isn't working when running as a JetBrains Client and the headless IJ instance on the remote host.
I think this might on the Bazel plugin side of things. Would it be okay to re-open this issue?

Sure, let's reopen it. I just can't promise that there's anything on the plugin's side we can do to make it work. So far, I'm only aware that dialogs/windows opened by a plugin can prevent the IntelliJ remote server from even starting up properly. Since others reported that a connection to the remote server was possible, that wouldn't be the issue.
I'm a bit surprised about the ClassNotFoundException for AsyncVfsEventsPostProcessor. I haven't tested exactly the Bazel plugin in this remote dev mode, but I've used our internal plugin bundle which contains the Bazel plugin. This superset of the Bazel plugin works within the remote dev mode and doesn't run into the ClassNotFoundException.
AsyncVfsEventsPostProcessor is a class from the IntelliJ platform API. It should be available. If not, that would be an issue with the IntelliJ remote server. Are you sure that the server is starting up properly? Does it run in an environment which allows the IntelliJ platform to properly start up?
Please note that you need to install the Bazel plugin on the remote server/host. If you instead installed it on the local client, that would explain the ClassNotFoundException.

Additionally typically in IntelliJ, we select a bazel project in the IntelliJ startup screen. The gateway doesn't offer that choice and has a different UI for opening projects.

Gateway is a separate product with its own API. At the moment, we can't extend it yet. Even when this becomes possible, we'd need to introduce a separate plugin targeted for Gateway as Gateway doesn't use/include IntelliJ plugins.

Is there any plan to support remote developoment?
There's a workaround which allows bazel working on remote development, sounds like it doesn't need to develop a new plugin for Jetbrains Gateway.
#3249

@liucijus Should this be considered fixed with https://github.com/bazelbuild/intellij/pull/3601?

@liucijus Should this be considered fixed with #3601?

Yes, this should be fixed, @mai93

This was just about one part of the plugin that has a workaround. There is a lot of other stuff missing: https://ij.bazel.build/docs/build-file-support.html
I'm especially missing highlighting and navigation. Can this issue be re-opened? The title of the issue is generic enough to encompass all the functionality, not just importing projects.

I wanted to try that just this afternoon and the strangest thing happens: the project folder appears empty in the project view, as if all the files were somehow excluded. It starts as soon as I install the CLion Bazel extension. If I don't install it, then I can see the files.

Are there any plans to support Jetbrains Gateway out of the box?
Currently on the plugin page I get "Not compatible with the version of your running IDE (Client 2023.2.5, Gateway 2023.2.5)".
I often need to open and close different subprojects and it's kinda inconvenient to follow the sequence specified in #3249 each time. It would be much better to have a plugin in the Client installed.
If there are no plans to do that, I could try to contribute myself.

authors: alice-ks awelless caandewiel goldencz hypdeb liucijus long-stripe mai93 nikunjy oquenchil tandel-pratik

repo: bazelbuild/intellij


text:
Update protobuf to v21.7 (security issue)

There is a security issue in the currently used protobuf version (v21.5). Would be cool to update to ~v21.6~ v21.7

Fixed by #154


text:
[Fix #1309] Add argument handling to MultilineBlockLayout

The cop now registers an offense for arguments on a wrong line.
Auto-correction is also applied to these expressions.
Fixes #1309.

Coverage increased (+0.0%) when pulling ede1562dad0cf921886a14e37bf2aff32bb3b20f on lumeet:1309/improve_multiline_block_layout into 39eaa505defc826079faf1d449bb10280589ef07 on bbatsov:master.

Please, mention the fixed issue in the title of the commit - [Fix ...] ....

There we go. By the way, @bbatsov, I forgot to ask if this a new feature, a change or a bug fix? Depending on how you look at it, it can be any of them. So, you decide. :) Currently it's under the Changes heading.

:+1: Having it listed as a change is fine by me. Thanks!

authors: bbatsov coveralls lumeet

repo: bbatsov/rubocop


text:
Add JSON dependency

Missing JSON dependency can cause problems with some configurations.
Cf : https://youtrack.jetbrains.com/issue/RUBY-19050

json is part of the standard library. We don't need an explicit dependency.

Even if json (or rake or whatever) is part of the standard library, some configurations don't include them by default (full user-side gem installation, helpful to avoid conflict between system gems and user gems).

authors: Kendos-Kenlen bbatsov


text:
[Sands of Salzaar] I'm a noob please help

I have used this plugin in other games and everything was great. And there was a problem with this. Only a very small part of the text is translated. Settings menu, developers.

What is really needed is not translated

All frameworks are included, XUnity.AutoTranslator-MelonMod-IL2CPP-5.2.0, melonloader latest version.
If someone more advanced can help, I'll be eternally grateful.

I've had a similar problem with translations only being generated for the first few minutes of the game loading.

I don't think it's all that simple. The translation works, during the game some pop-up messages "You entered the location Such and such", "Received such and such resources" are translated. How did you solve your problem?


text:
manual-layout-transitions-part-3

原文链接: manual-layout-transitions-part-3

@bboyfeiyu 认领

repo: bboyfeiyu/android-tech-frontier


text:
Online interpreter doesn't reset stdin every time

Repro:

Program: ?!@
Input: -1.5
Expected behavior: always outputs '-1'
Actual behavior: Every other run outputs '5'

I'm probably only resetting stdin once it's fully consumed, and not every single run.

This isn't a problem with the CoffeeScript glue code. C itself is not resetting the position of stdin -- it's ignoring the first 3 characters, whatever they be. I can work around this by adding while (getchar() != EOF) {} before the clearerr call in the wasm entrypoint, that feels very wrong.

I figured out why it doesn't happen when the input changes:
https://github.com/bbrk24/Trilangle/blob/a263c1c7176987ccbc55934c24bf602422bf8221/wasm/in.coffee#L72-L73


text:
Phraseexpress ist outdated, can you please update.

chocolatey/PhraseExpress/PhraseExpress/phraseexpress.nuspec

In fact it is not; only the version shown on Chocolatey is "outdated" but the content of what gets downloaded is always the latest due to the way PhraseExpress posts new downloads (same filename/url every time for new version).
Nevertheless, I've queued a new build w/ the new version #

In fact it is not; only the version shown on Chocolatey is "outdated" but the content of what gets downloaded is always the latest due to the way PhraseExpress posts new downloads (same filename/url every time for new version).
Nevertheless, I queued a new build w/ the new version #

Thanks.
If the version number in chocolatey is not correct, it will not be updated automatically.
Is there any way I can trigger it myself?

cup phraseexpress --force

Thanks. I didn't mean how to install the new version on my client. I meant to create a new package with the right version at chocolatey as maintainer, that it will be updated automaticly with the command cup all.

ah, unfortunately no only maintainers of this repo can do that today. So for now reporting here or on PhraseExpress' entry on chocolatey.org is the best/only way.


text:
build(deps): update scala-library from 2.12.17 to 2.12.18

About this PR
📦 Updates org.scala-lang:scala-library from 2.12.17 to 2.12.18
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #123 (307b218) into main (6f9d35b) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #123   +/-   ##
=======================================
  Coverage   86.36%   86.36%
=======================================
  Files           3        3
  Lines          44       44
  Branches        6        6
=======================================
  Hits           38       38
  Misses          6        6

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter scala-steward


text:
Discontinuation of bcbio-nextgen project

Dear bcbio community,
In 2011, the Harvard Chan Bioinformatics Core began developing bcbio as an open-source framework to tackle challenges in reproducibility and scalability in the field of next-generation sequencing data analysis. Our goal was to apply best practices to applications of sequencing and develop an automated framework that could be widely used by scientists worldwide. This project has been a labor of love for members of our team, and witnessing its growth and impact over the past 13 years has been immensely gratifying. We are deeply grateful to the more than 50 bioinformaticians who have contributed to bcbio. The platform has been cited over 1,400 times, with many papers highlighting significant biological discoveries enabled by our pipelines.
In recent years, changes in personnel, advances in the field, and competing project commitments have made it increasingly challenging to support and continue the development and maintenance of bcbio. At the same time, Nextflow and the nf-core community have seen substantial growth, now hosting numerous globally-used bioinformatics pipelines. We are enthusiastic to join this larger community and to share our best practices within the Nextflow/nf-core framework. We have already contributed to the RNA-seq and small RNA-seq nf-core pipelines and plan to transition other bcbio analyses and new pipelines to nf-core.
We will continue to address bcbio issues that do not require major fixes or new development until the end of the year, after which, we will archive the bcbio-nextgen project on GitHub. We are excited to be launching a suite of open-source analysis templates, bcbioR, for downstream statistical analyses in transcriptomic and epigenomic studies. bcbioR aims to tackle challenges in extracting biological knowledge from complex study designs and data with multiple sources of variability. It offers a collection of flexible templates containing widely accepted genomics methods in commonly used formats, such as Rmarkdown, Rshiny apps, and R/Python scripts, all consolidated into a single R package. The platform integrates seamlessly with outputs from nf-core pipelines, providing a streamlined process from raw data to actionable biological insights. We are committed to assisting users with transitioning to nf-core and extend our heartfelt thanks to everyone who has been a part of the bcbio community.

Thank you to the bcbio-nextgen development team for the incredible effort over the years related to this project.

authors: lpantano mjsteinbaugh

repo: bcbio/bcbio-nextgen


text:
Commit e5b8a305 puts too much GC pressure on G1

Our application's memory allocation profile is mainly driven by scrypt. We have upgraded from BC 1.60 to 1.64 for some time now and we're seeing too many garbage collection cycles coming from 16MB allocations. We tracked down these allocations to commit e5b8a305 where you change V from a two-dimensional array to a one-dimensional array.
What is the reasoning behind this change? Could it be reverted?
We currently look into several options like optimizing G1 to this new allocation pattern or switching completely to another garbage collector. However, our preferred option would be to revert this commit.

The change was made to reduce total memory usage, in reaction to OutOfMemory reports on mobile devices. It replaces what was N separate (small) allocations with a single allocation of the same total storage, but since each allocation has some memory overhead this substantially reduces the total memory footprint.
I would also have expected that to be kinder to the GC in general. Do you have some insight as to why you think this is causing increased GC cycles?

I see. I'm not an expert on scrypt or garbage collection. But as I understand, G1 has some issues with short-lived large allocations.
In our case, we have a heap size of 4GB and a G1 region size of 1MB. Allocating 16MB blocks means that G1 handles them as Humongous Allocations. Our GC logs show that short-lived Humongous Allocations causes G1 to Stop-The-World more often.
We ran one of our use cases with the latest Bouncy Castle version twice. The first time we ran our application with the current master and the second time we reverted commit e5b8a305. As you see from the images, reverting commit e5b8a305 has a major impact on Young GC.
Short-lived small allocations are far better for G1. We know that we are optimizing here for G1 and maybe reverting this commit makes other use cases worse. However, seeing that G1 is the default GC on Java 11 (LTS), we would very much like to see this commit reverted.

Memory (latest):
Memory (commit reverted):
GC Time (latest):
GC Time (commit reverted):

I've pushed a change for SCrypt that tries to strike a balance by chunking the memory allocations into 32KiB chunks (somewhat arbitrary but tested well). Once the change mirrors to GitHub (may take a day), please test it out and let us know whether it addresses your issue.
@schildbach This change affects SCrypt memory allocation. I think it should still be fine for the OOM issues you reported last year, but it might be best if you can test the changes once they're available.

Holy cow, this change takes GC activity to the level it was before. Nice work!
Thanks for taking the time to fix this issue.

Great, thanks for confirming. I still want to hear back from @schildbach before closing this out, but I am not expecting there to be problems.

So originally it used to be n allocations of r32 bytes, then with e5b8a305 it went down to 1 allocation of nr32 bytes, and now its nr/1024 allocations of 32*1024 bytes?

For my n = 65536, r = 8 usecase that's 512 allocations. Sounds easily doable.

@schildbach The allocations can be a little smaller if r is not a power of 2, but that's basically right, and yes, in your case it would be 512 allocations of 32KiB.

authors: fluxroot peterdettman schildbach

repo: bcgit/bc-java


text:
metabase embed

feat: add metabase-embed-url api route
feat: metabase embed style
chore: pass metabase embed env vars to github workflow
chore: pass metabase embed secrets to helm deployment
test: deployment

Implements # <issue number>

@rafasdc thanks again for the help with the header issue. I think this is ready now, can you take another look when you have time? I had to use a library iframe-resizer-react to get the iframe to display with the full width, it looks nice now.

repo: bcgov/CONN-CCBC-portal


text:
Changes are related to related list of Account flexipage & Removing EDRD Users from EDRD(MoH/ PSP) Queues

Changes are related to related list of Account flexipage & Removing EDRD Users from EDRD(MoH/ PSP) Queues

@cgijeffolsen / @RanadheerRG , can you please approve this PR? So That we can start creating packageId and we can get the deployed in staging. As I won't be available from 6PM EST. Thanks for understanding!

repo: bcgov/MoH-SAT