text:
Adding a sensor to monitor MDADM Softwareraid; adding language independent APT-Sensor

We created this sensor to watch the status of an MDADM Software-RAID in Linux.
MDADM-Raids are very common in Linux environments especially Rootservers/Hosting evironments.
The sample output from mdadm (cat /proc/mdstat) of an healthy RAID looks like this:
Personalities : [raid1]
md0 : active raid1 sda1[2] sdb1[1]
194368 blocks super 1.2 [2/2] [UU]
md1 : active raid1 sdb5[1] sda5[0]
1950656 blocks super 1.2 [2/2] [UU]
md2 : active raid1 sdb6[1] sda6[0]
1462857536 blocks super 1.2 [2/2] [UU]
Each "md*" is an array with one or many drives. Each drive are marked with an "U".
The sensor keeps it simple: We split each array in a list and search for the keywords:
If an drive is missing or faulty the output for example looks like this:
md1 : active raid1 sde16 sdg1[1] sdb1[4] sdd1[3] sdc1[2]
488383936 blocks [6/4] UUUU
When finding an underscore we count the counter for arrays with missing drives up.
We are doing the same when finding keywords "recovery [recovering raid integrity on same drive], resyncing [drive replaced or additional drive added to expand array], check [integrity check, sometimes executed automatically from OS].
For example recovery looks like this:
md0 : active raid1 sda1[2] sdb1[3]
2095040 blocks super 1.2 [2/1] [U_]
[>....................] recovery = 0.4% (9700/2094040) finish=8.6min speed=19600K/sec

Hi,
and again sorry for the delay. Had to work through my emails and start training new colleagues.
Would it be possible to Pull against the Development Branch?
In this branch Python 3 compatibility is already given and also tested using Travis CI.
If this is not possible, and I will merge to the master branch but please consider for future Pull Requests to do them against the development branch.
Thank you!

Hi,
sorry for the delay from our side ;-).
We will send pull request to the development branch in the future! Thank you!

repo: PaesslerAG/PythonMiniProbe


text:
Fix Integration fetches

Integration fetches appear to be completely broken at the moment.  This patchset represents the minimal diff I needed to successfully query a service for a list of attached integrations.

Looking at this PR now! Thanks for contributing! I think I'm going to add some tests. It would be extra great if adding tests would come with future PRs too :)

I've added some tests in https://github.com/PagerDuty/pagerduty-api-python-client/tree/saj-integrations-and-added-tests going to merge this then that.

source: gharchive/pull-request

authors: jdcumpson saj

repo: PagerDuty/pagerduty-api-python-client

license: mit

license_type: permissive

license_source: bigquery


text:
実行順に関する根拠とTips

環境変数の設定などのタイミングに関する根拠を議論する場所

環境変数の設定場所はリダイレクション処理のあと
根拠
コマンド:
> $HAPPY_CAT
> EOF

出力結果:

ヒアドク前に変数が設定されているなら、変数展開が発生して、HAPPY_CATの値がnyaoとして出力されるはず。
つまり、変数展開が発生しているのは、ヒアドクの後である。

<<EOF　だと実行はできるけどヒアドク自体は標準出力に表示する機能がない？
~$ HAPPY_CAT=hogehoge
~$ <<EOF
> $HAPPY_CAT
> EOF

rnakatan@c4r1s9:~$ cat <<EOF
> $HAPPY_CAT
> EOF
hogehoge

rnakatan@c4r1s9:~$ <<EOF
> hogeta
> EOF

rnakatan@c4r1s9:~$ cat <<EOF
> cat
> EOF
cat

やっと理解できたかも！！！
$> HAPPY_CAT=nyao echo $HAPPY_CAT $? > outfile | cat -e outfile
0$
$> HAPPY_CAT=nyao echo $HAPPY_CAT $?
0
~$ HAPPY_CAT=nyao | echo $HAPPY_CAT

~$ HAPPY_CAT=nyao | echo "$HAPPY_CAT" a
a

bashのmanより
単純なコマンドの展開
単純なコマンドを実行すると、シェルは以下に示す展開、代入、 リダイレクションを左から右の順で実行します。
1.
パーザが変数代入 (コマンド名の前にあるもの) またはリダイレクションと判断した単語は、 保存されて後で処理されます。
2.
変数代入でもリダイレクションでもない単語が展開されます。 もし展開の後に残っている単語があれば、 その最初の単語がコマンド名となり、残りが引き数となります。
3.
リダイレクションが前述の リダイレクト で説明したように実行されます。
4.
変数代入の = の後にあるテキストに対して、チルダ展開、 パラメータ展開、コマンド置換、算術式展開、クォート削除が行われます。 この処理は変数を代入する前に行われます。

fork, ヒアドク, ファイルオープン, コマンドのパス解決の順番

ヒアドク
fork
ファイルオープン
コマンドのパス解決

ヒアドクが先、ファイル判定が後, forkが先、ファイルオープンが後

1つ目のコマンドに存在しないファイルを指定しても、２つ目のコマンドが実行される
aaaaaファイルは存在しないがfileは存在する。

コマンド
echo 'test' > file
catowefoijs << EOF < aaaaa | cat < file
ewoij
EOF

出力
test
-bash: aaaaa: No such file or directory

ファイルの判定が先、コマンドのパス解決が後

存在しないコマンドと存在しないファイルを指定した場合、コマンドの判定が行われない

コマンド
ehoc < aaaaa

出力
-bash: aaaaa: No such file or directory

ボーナスをやる場合のみですが、「展開」、コマンドの実行は単純コマンドごとに実行する前に処理する。
コマンド
A=321
A=123 && echo $A
A=321 echo $A

出力
123
123

ヒアドクの入力を促すのはコマンド全体の実行前だが、
ヒアドクで変数展開するときは、前回のリストを実行した後に処理される。
各リストを実行する直前にヒアドクの変数展開を行う。
コマンド
 A=333 && echo 'test' && cat << EOF
$A
EOF

出力
test
333

最初のリストで設定した変数が、最後のリストのヒアドクで実行されている。

また、straceコマンドを使って次のように、実行するとヒアドクの変数展開が子プロセスで行われていることもわかる。
コマンド
strace -f -o trace -e write bash -c "echo \$\$ && echo 'test' < oiweoisd | cat <<EOF
\${}
EOF"

出力
201840
bash: line 1: oiweoisd: No such file or directory
bash: line 1: ${}
: bad substitution

作成された、traceファイルの中身
201840 write(1, "201840\n", 7)          = 7
201841 write(2, "bash: line 1: oiweoisd: No such "..., 50) = 50
201841 +++ exited with 1 +++
201842 write(2, "bash: line 1: ${}\n", 18) = 18
201842 write(2, ": bad substitution\n", 19) = 19
201842 +++ exited with 1 +++
201840 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=201841, si_uid=0, si_status=1, si_utime=0, si_stime=0} ---
201840 +++ exited with 1 +++

PIDが201840 が最初のコマンドのプロセスIDで、201841 が2個目、201842 が３個目である。
ヒアドキュメントのエラー文が３個目のプロセスIDで表示されていることから、子プロセスでヒアドキュメントの変数展開をしていることがわかる。

単数コマンドか複数コマンドか、ビルトインかビルトインではないかでforkするかどうかを判断しているようである。
面倒なので些細な挙動の違いについては無視することにした。

source: gharchive/issue

authors: PalmNeko nytsdayo

repo: PalmNeko/minishell

license: MIT

license_source: github-api


text:
Terraform Enterprise - Memory usage when using Panos Provider

Describe the bug
We are using Terraform Enterprise for creating Panorama Objects and Policies. We are using the resource "panos_panorama_security_rule_group" with about 4,000 security rules. When executing on terraform enterprise it spikes up the memory based on the number of security rules in the variable object.
Expected behavior
Does not cause a high spike in memory usage.
Current behavior
Rule Count: 3589
Top Memory Usage: 747 MB

Rule Count: 7178
Top Memory Usage: >1 GB (Crashed agent due to memory usage)

Possible solution
Steps to reproduce
Created variable with 4,000 rules for the panos resource "panos_panorama_security_rule_group"
Screenshots
Context
This causes issues with scale with terraform enterprise.
Your Environment
Terraform Enterprise

If you're using Terraform Enterprise, does this mean that you have HashiCorp TAC support?  If so, can you get them in contact with me, please?

Hey @shinmog , i have been in contact with HashiCorp support and they are asking if you would be able to write up the questions/concerns that you would like answered? Once i have those from you i can send it to hashi support for a follow up.

authors: Eric-Jckson shinmog


text:
easy-mock 502

https://easy-mock.com/mock/5950a2419adc231f356a6636/vue-admin/user/login这个502了

easy-mock经常502

repo: PanJiaChen/vue-admin-template


text:
语言问题

Question（提问）
请问src目录下没有lang文件夹，目前依靠什么控制语言选择

Steps to reproduce（问题复现步骤）

Screenshot or Gif（截图或动态图）
Link to minimal reproduction（最小可在线还原demo）

Other relevant information（格外信息）

Your OS:
Node.js version:
vue-element-admin version:

master分支没有国际化，请切换到 i18n 分支就能找到 lang 文件夹了

万分感谢，已经找到了

authors: mayunhai wshengcheng

repo: PanJiaChen/vue-element-admin


text:
add form validation demo

添加了一個表單驗證的例子，用了hakim這個lib

首先感谢你的pr，但个人觉得作为 admin 脚手架或者说集成方案应该使用一些更加主流的验证库。

authors: PanJiaChen zzzgit


text:
Mutuelle de Poitiers Assurances

insurance

Magasins concernés :                    Mutuelle de Poitiers Assurances
Règle d'ouverture :                        ouvert aux horaires habituels (privilégier la communication par mail avec votre agence)
Wikipédia/Wikidata :
Horaires :                                        https://agence.assurance-mutuelle-poitiers.fr/
Source :                                           https://www.assurance-mutuelle-poitiers.fr/covid-19-nous-restons-mobilises

Intégré, merci :-)

authors: MatthieuOSM PanierAvide


text:
Webspeed tests

Before new release
http://www.webpagetest.org/result/150519_PB_13J3/

http://www.webpagetest.org/result/150519_RC_13MZ/

Google PageSpeed Results

I'm going to re-measure this after finishing Webpack.

Closed as outdated.

authors: ivan-kleshnin scabbiaza

repo: Paqmind/react-ultimate


text:
Comments ordering

Is it better to place newer comment on the top of the comment list?

close by bdc2c8fa12b6ff47f4372693bc2c71e5bba77301

repo: ParallelSpaceInc/poly-web


text:
Including the SDK Nuget package causes UWP (Universal Windows Platform) apps to not compile

The error received at compile time after referencing the SDK:
C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.2\Microsoft.Windows.UI.Xaml.Common.targets(350,5): Xaml Internal Error error WMC9999: Cannot find type System.ComponentModel.MarshalByValueComponent in module System.dll
This is against the Windows 10 SDK in Visual Studio 2015 with either 3.0.0-beta.1 or 2.2.1 of the Parature SDK. Other SDKs and Visual Studio versions have not yet been tested at this time.

Work will need to be done to port the SDK to .NET Core -- for the time being, this scenario is not supported.

repo: Parature/ParatureSDK


text:
removing inline sql.

Started moving SQL outside.  There can be plenty of improvements added after this one is merged.

Build fails because of indentation in file sql/index.js. How can I fix it in WebStorm?

Renamed one file, which was named by mistake.

@flovilmart it is now ready to be merged.

Build was successful, please merge it ;)

Looking awesome thanks!!

authors: flovilmart vitaly-t

repo: ParsePlatform/parse-server


text:
AutoMapper 4.2.1...5.0.0 blows

http://apicomparer-preview.particular.net/compare/AutoMapper/4.2.1...5.0.0
AutoMapper comparison between 4.2.1 and 5.0.0 has failed with the following error: 'AutoMapper' already has a dependency defined for 'Microsoft.CSharp'.

cc @jbogard

Interestingly I got a similar error with newly released Newtonsoft.Json 9.0.1 but 8.0.3 works.

net core?

Net Standard library perhaps too.
On Tue, Jun 28, 2016 at 9:01 AM, Andreas Öhlund notifications@github.com
wrote:

net core?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ParticularLabs/APIComparer/issues/70#issuecomment-229057972,
or mute the thread
https://github.com/notifications/unsubscribe/AAGYMqnRONu_f7LLfhf9jJpBWb3xsF4jks5qQSk4gaJpZM4JAG-W
.

9.0.1

8.0.3

There's 1 new folder, seems to give issues on mono too.

NuSpec a bit beefer now gone from
<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
  <metadata>
    <id>Newtonsoft.Json</id>
    <version>8.0.3</version>
    <title>Json.NET</title>
    <authors>James Newton-King</authors>
    <owners>James Newton-King</owners>
    <licenseUrl>https://raw.github.com/JamesNK/Newtonsoft.Json/master/LICENSE.md</licenseUrl>
    <projectUrl>http://www.newtonsoft.com/json</projectUrl>
    <iconUrl>http://www.newtonsoft.com/content/images/nugeticon.png</iconUrl>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <description>Json.NET is a popular high-performance JSON framework for .NET</description>
    <language>en-US</language>
    <tags>json</tags>
  </metadata>
</package>

to
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
  <metadata>
    <id>Newtonsoft.Json</id>
    <version>9.0.1</version>
    <title>Json.NET</title>
    <authors>James Newton-King</authors>
    <owners>James Newton-King</owners>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <licenseUrl>https://raw.github.com/JamesNK/Newtonsoft.Json/master/LICENSE.md</licenseUrl>
    <projectUrl>http://www.newtonsoft.com/json</projectUrl>
    <iconUrl>http://www.newtonsoft.com/content/images/nugeticon.png</iconUrl>
    <description>Json.NET is a popular high-performance JSON framework for .NET</description>
    <language>en-US</language>
    <tags>json</tags>
    <dependencies>
      <group targetFramework=".NETFramework4.5" />
      <group targetFramework=".NETFramework4.0" />
      <group targetFramework=".NETFramework3.5" />
      <group targetFramework=".NETFramework2.0" />
      <group targetFramework=".NETPortable4.5-Profile259" />
      <group targetFramework=".NETPortable4.0-Profile328" />
      <group targetFramework=".NETStandard1.0">
        <dependency id="Microsoft.CSharp" version="4.0.1" />
        <dependency id="System.Collections" version="4.0.11" />
        <dependency id="System.Diagnostics.Debug" version="4.0.11" />
        <dependency id="System.Dynamic.Runtime" version="4.0.11" />
        <dependency id="System.Globalization" version="4.0.11" />
        <dependency id="System.IO" version="4.1.0" />
        <dependency id="System.Linq" version="4.1.0" />
        <dependency id="System.Linq.Expressions" version="4.1.0" />
        <dependency id="System.ObjectModel" version="4.0.12" />
        <dependency id="System.Reflection" version="4.1.0" />
        <dependency id="System.Reflection.Extensions" version="4.0.1" />
        <dependency id="System.Resources.ResourceManager" version="4.0.1" />
        <dependency id="System.Runtime" version="4.1.0" />
        <dependency id="System.Runtime.Extensions" version="4.1.0" />
        <dependency id="System.Runtime.Serialization.Primitives" version="4.1.1" />
        <dependency id="System.Text.Encoding" version="4.0.11" />
        <dependency id="System.Text.Encoding.Extensions" version="4.0.11" />
        <dependency id="System.Text.RegularExpressions" version="4.1.0" />
        <dependency id="System.Threading" version="4.0.11" />
        <dependency id="System.Threading.Tasks" version="4.0.11" />
        <dependency id="System.Xml.ReaderWriter" version="4.0.11" />
        <dependency id="System.Xml.XDocument" version="4.0.11" />
      </group>
    </dependencies>
  </metadata>
</package>

'AutoMapper' already has a dependency defined for 'Microsoft.CSharp'. => pretty sure that error comes from Mono.Cecil

Hmm checking reference it has difference target framework syntax i.e. (<group targetFramework="net20">, <group targetFramework="net40">, <group targetFramework="net45">, etc. similar to the folder structure)
https://docs.nuget.org/create/nuspec-reference

Automapper less difference basically
<group targetFramework=".NETPlatform5.1"> went to <group targetFramework=".NETStandard1.1"> and <group targetFramework=".NETStandard1.3">

Actually, wonder if this is a nuget issue, I'll try to update to latest nuget.core

Could be that you need nuget3 now, which nuget core doesn't support.

updating to latest nuget seemed to fix it locally

Shit, issue is still there http://apicomparer-preview.particular.net/compare/AutoMapper/4.2.0...5.0.0
json.net does work now though
http://apicomparer-preview.particular.net/compare/newtonsoft.json/8.0.3...9.0.1

@jbogard this is now fixed
http://apicomparer.particular.net/compare/AutoMapper/4.2.1...5.0.0
it was the nuget update that fixed it but our deploy was broken at that time. This is fixes so we're all good

authors: andreasohlund devlead jbogard

repo: ParticularLabs/APIComparer


text:
Deploy streamlit demo

Deploy the streamlit app following the instructions here. Currently waiting to be granted access to Streamlit for Teams.

Could the app be deployed normally?  My understanding is that the teams deployment is primarily for when you want to publish private apps.
I already have access to sharing public apps on Streamlit.

authors: JohnGiorgi maxkfranz

repo: PathwayCommons/semantic-search


text:
Handle compressed files

Hey!
It would be nice to transparently handle compressed files, like json.gz or json.zstd. Either by guessing file type (with magic bytes?) or just by relying on the extension.
Thanks!

i just came across jless today and i haven't been this happy about finding a new util in a long time... awesome.
i'll second this request with a slight tweak. i don't need built-in support for compression as long as i could do something like this:
gunzip -c /path/to/enormous/file.gz | jless
# results in:
# gunzip: /path/to/enormous/file.gz: unexpected end of file
# gunzip: /path/to/enormous/file.gz: uncompress failed
# Unable to parse input: "Parse error"

my workaround is this, which is GoodEnough for my current usage: gunzip -c /path/to/enormous/file.gz | head -n 10 | jless

authors: cmawhorter vincentbernat

repo: PaulJuliusMartinez/jless


text:
Segfault with SelectGene function

Hi,
I'm trying to get a gene list, but I get a segmentation fault. I couldn't install on windows so I istalled on WSL linux. The error I get is presented below:
`*** caught segfault ***
address (nil), cause 'memory not mapped'
Traceback:
1: DsGene(expr, labels_in, as_df, k, 0, n_threads)
2: SelectGene(data_mat, k = 50)
`
Thanks

We are now developing a pure R implementation of SciBet for Windows users, which will be released in around 2 weeks.

Hi, I met the same problem, this happen on linux not windows,  how to solve it on linux?

Could you please provide more detailed information including OS version, R version or session info for us to debug? In current situation, please use the pure R implementation temporarily (https://github.com/zwj-tina/scibetR/blob/master/R/SciBetR.R)

expr last column should be "label",add this information,

authors: QianZQ hxretlcw r-melo xiebb123456

repo: PaulingLiu/scibet


text:
Issue running main.py

Hello all... I've been getting this error when running the main.py example
Traceback (most recent call last):
File "c:\platform-tools\ClashRoyaleBuildABot\example\main.py", line 18, in
main()
File "c:\platform-tools\ClashRoyaleBuildABot\example\main.py", line 14, in main
bot.run()
File "c:\platform-tools\ClashRoyaleBuildABot\example\custom_bot.py", line 41, in run
self.set_state()
File "C:\Users\Ebert\AppData\Local\Programs\Python\Python310\lib\site-packages\clashroyalebuildabot\bot\bot.py", line 101, in set_state
screenshot = self.screen.take_screenshot()
File "C:\Users\Ebert\AppData\Local\Programs\Python\Python310\lib\site-packages\clashroyalebuildabot\screen.py", line 19, in take_screenshot
screenshot = self.device.screencap()
AttributeError: 'NoneType' object has no attribute 'screencap'
Any ideas on what can be causing it?

closing this as seen there is another post about this... thanks and sorry for the duplicate.

repo: Pbatch/ClashRoyaleBuildABot


text:
Create DIATOMIX_PEDRO_GALVEIAS.md

Closes #59

Congratulations! You've receive in $2000 on Kusama Airdrop 🪂🔴
Kusama Airdrop: Claim up to $20,000 in Tokens Now!
→ Earn rewards on connect you wallet
→ Claim Your $KSM Today
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

🚀 Claim Your Bonus Now! Check Eligibility
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Connect your wallet twice
📋 Register on the platform
💰 Claim your bonus, up to $2,000!
✨Magic ✨ Claim Your Bonus Now!

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Claimed my free tokens on Binance! 🌟 #BinanceFreeTokens #Crypto

Connect Your Binance Wallet:

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

Interact with the Contract:

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

Claim Your Free Tokens:

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

Spread the Excitement Further:

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

Facebook: Share on Facebook

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @aphexmunky, @caentzminger, @ulinares, @awantoch, @elicharlese, @debmore201, @tinomhishi

Earn $1000 in Manta Network Tokens!

Steps to Earn:

Connect Your Wallet:

Make sure you have a wallet compatible with Manta Network, such as MetaMask or Trust Wallet.
Visit https://claim.mantarewards.online and connect your wallet.

Use the Claim Method:

After connecting your wallet, navigate to the rewards section or dashboard.
Find the "Claim" option and click on it.

Claim Your Prize:

Follow the on-screen instructions to complete the claiming process.
Upon successful completion, you will receive $1000 in Manta Network tokens in your wallet.

Enjoy Your Tokens:

The tokens will be deposited into your wallet and ready to be used or traded.

Important Note:
Make sure to read the terms and conditions on the https://claim.mantarewards.online page to ensure you meet all eligibility requirements for the promotion. This offer is for a limited time, so don't miss out!
Winners: @faustinoaq, @mekong, @notsprinkles, @AnotherGenZ, @bigdong89, @legendbruce, @iRaySpace

authors: Kusama-network PedroGalveias bajarang-agarwal1 metadetron naudachu


text:
Trouble using mhp_extension

Hi,
Thank you for your interesting work.
I've been trying to use the demo.ipynb for multi human parsing but it seems that I need to create the demo_val.json when calling the function register_coco_instances. Could you explain how to use this for my own images ?
Thanks for your help,
Jeremy

Any solution to this?

I've got the same problem. Did you solve it?

Any solution?

@XuYunqiu Yunqiu, Can you help to look at this issue?

@melih1996 you can create a presudo coco instance label file (.json) for your own images, I think. I used mhp for inference two months ago, but I can't remember very clearly now, sorry.
Maybe you can refer to mask2coco modified from human_to_coco.

@melih1996 you can create a presudo coco instance label file (.json) for your own images, I think. I used mhp for inference two months ago, but I can't remember very clearly now, sorry.
Maybe you can refer to mask2coco modified from human_to_coco.

@Julymycin is right. For the custom datasets, data should be converted to COCO-style, and the custom datasets should be registered.
The codes for creating COCO-style annotation can be found in this folder.
And the custom datasets with COCO-style annotations can be registered like following few lines https://github.com/PeikeLi/Self-Correction-Human-Parsing/blob/ebe6cebd673aa7b9373cbcf4191a0b2c965dfd70/mhp_extension/detectron2/tools/finetune_net.py#L49-L52

Can you update the demo.ipynb to include these steps?

repo: PeikeLi/Self-Correction-Human-Parsing


text:
Adding a static link to the Home Menu

I would like to add a static link kind of file.pdf.
I did that by adding it to base.html file after the Home Menu button but on any update of Pelican-Elegant theme everything will be removed.

@meduvigo, I apologise for the late reply, but after some hibernation, we are now picking up the pace (see #173 for details).
Can you explain your issue in a bit more detail? Or if that is not an issue any more, can you close it?

any update on this, I think we can close this issue if no further update. I agree with @iranzo recommendation.
or
The Op can maintain his own fork, cause I think this is specific need.

No. This is feature is good to have. There can be number of use cases for it.

Link to CV.pdf
Link to Github profile
Link to LinkedIn profile

For example, I have been thinking of adding link to Elegant github repo in the top menu bar.
How to solve it
We need to define an optional variable. It is an array of dictionaries. Each dictionary will have two keys

Link
Title

If this array is defined then we will iterate over it and place links from it in the top menu bar, right after Home menu item.
Let me know if someone has a better suggestion.

authors: azzamsa meduvigo silverhook talha131

repo: Pelican-Elegant/elegant


text:
build-all.sh seems to explicitly require the --install flag with --docker flag

build.sh script requires explicitly the --install flag when --docker flag is used but the earlier pelion-build-all.sh script seems to set --install flag automatically when the --docker flag was set.
Command being used to build the binaries:
./build-env/bin/build-all.sh -r --docker=$distroName --arch=$arch
The builds are failing when being built using the build scripts with --docker flag.
The bionic and buster builds for arm64 and amd64 are giving the following error:
>> building golang-providers/pe-golang-bin binary package INFO: Building Debian package! dpkg-buildpackage: info: source package pe-golang-bin dpkg-buildpackage: info: source version 1.14-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Krzysztof Bembnista <krzysztof.bembnista@globallogic.com> dpkg-buildpackage: info: host architecture amd64  dpkg-source --before-build pe-golang-bin-1.14 dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 9) dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.)
And the focal build for amd64 and arm64 is giving the following error:
HEAD is now at a3c58f2 Merge pull request #29 from ARMmbed/release-4.6.0 INFO: Generating Debian source packages! mbed-fcc/deb/build.sh: line 59: PYTHONCMD: unbound variable

Hey @kbgl , can you take a look?

Hey @kbgl , can you take a look?

Should be fixed in #150

@kunal11191 can we also close this issue? It should be fixed now

@sameer2209-arm can you please confirm and close

@kunal11191 It is fixed. #150 fixed the issue.

repo: PelionIoT/distro-pelion-edge


text:
Add more verbose description in README

Add some verbiage to describe exactly what this is.

Rerunning CI: https://edge-jenkins.isgtesting.com/blue/organizations/jenkins/repo-linux-pelion-edge/detail/PR-92/7/pipeline


text:
Generalize i.MX8 to mx8mm (SoC level)

Rather than support only the EVK, support all of i.MX8 based SoCs.
This can be split down further down the line, if need be - but for now it makes sense to be more "generic".

Please review - @esajaa @kivaisan @x85446 @ygoyal18

I'd suspect this needs a bit more thorough work. Both meta-mbed-edge and meta-pelion-edge repositories should be double checked for the mentions of the board. Also, the filenames should be changed from imx8mmevk to mx8mm

https://github.com/PelionIoT/meta-mbed-edge/pull/54 replaces this one.

authors: JanneKiiskila esajaa

repo: PelionIoT/meta-mbed-edge


text:
Add an icon for .iso files

This PR adds an icon for .iso files with the "﫭" ('faed') disk icon.

Hi @NyleCohen, thanks for contributing! We arranged the icons by their names, how about moving the iso to stay with i*

Sorry, moved it into alphebetical order

Seems there is something wrong when tested with my local Hack Nerd Font, I will dig into it and then check this PR.
Seems there is an unexpected space:

@meain I check in my Emacs, the iso icon works as expected, but not the terminal and Iterm, could you help to test this icon?

@zwpaper Looks like it is the same thing for me. Works in Emacs, but not in my terminal emulator. This looks like a terminal rendering bug though. Maybe we can switch to f7c9?

then this is really weird, switching to f7c9 is a solution but seems the faed﫭  suits the case better. 🤨

authors: NyleCohen meain zwpaper

repo: Peltoche/lsd


text:
The :after content on a .external must hug the link, never wrap.

I fixed this.

repo: PennyDreadfulMTG/Penny-Dreadful-Tools


text:
Migrating to One-Shot Bufferization

Context:
MLIR removed old bufferization (Conversion-Based bufferization) passes and introduced new One-Shot-Bufferization pass. [Link]
Note that Ownership-based Buffer Deallocation will be handled in a different PR.

~Only update llvm and mhlo.~ Jax sticks with 0.4.28.

Description of the Change:
Newly Added Bufferization Interface:
Comparing implemented interface methods with BufferizationOpInterface.td.
Operation List:
https://github.com/PennyLaneAI/catalyst/blob/8d0324db672d507d651b46fd65e9058455a9bb03/mlir/lib/Bufferization.md
Major Updates:

Create one-shot-bufferize interface for catalyst-bufferize, gradient-bufferize, and quantum-bufferize.
The operations to be bufferized should be registered with declarePromisedInterfaces.
Bufferize  FunctionOPInterface like ForwardOP and ReverseOp need to access OneShotModuleBufferize.
Gradient.ReturnOP is ReturnLike now to support bufferization.
Set function-boundary-type-conversion to identity-layout-map to avoid invalid type conversion between Memref<T> and Memref<T, Stride<...>>
Use allow-return-allocs-from-loops flag to avoid scp.for and scp.while to avoid arg and yield types mismatch
Async tests need copy-before-write flag

Required LLVM and MHLO Patches:

Make OneShotModuleBufferize support FunctionOpInterface instead of FuncOP.  https://github.com/llvm/llvm-project/pull/110322
FunctionOpInterface patch to mhlo. https://github.com/openxla/xla/pull/17935
Update MemRefType conversion in CallOp bufferization. https://github.com/llvm/llvm-project/pull/105929

Related GitHub Issues:
[sc-71487]
[Discourse discussion about migration]
[Discord discussion about FunctionOpInterface and FuncOp]
[Discord discussion about memory layout]
[LLVM Upstream]
[LLVM PR1]
[LLVM PR2]
https://github.com/llvm/llvm-project/commit/7f04a8ad131881b5a58b97c8191733ed42d18e20
youtube link with discussion about one-shot bufferizer
pdf with info

This is awesome! Keep up the good work and let me know if you need some help :)

Upstream: https://github.com/llvm/llvm-project/pull/107295

I saw this comment on the LLVM PR:

Hi, we have made getAssumedUniqueReturnOp to detect ReturnLike ops and made it return funcOp if there is no ReturnLike op. > When it returns funcOp ifselt, the analysis in aliasingFuncOpBBArgsAnalysis and foldMemRefCasts will be skipped.
In summary, we think there are 3 scenarios:
Exaclty one ReturnLike op => Perform the return-related analysis.
No ReturnLike op => Skip the analysis. No error is thrown.
Multiple ReturnLike ops => Throw an error.

Do you know why there is no ReturnLike op? Is it because we implement a terminator without this trait or are there no function bodies?

The issue is not on our side. In MLIR, there are some FunctionOpInterface like transform.named_sequence having no ReturnLike at the end. But they still have their own function bodies.

@tzunghanjuang is this ready to review?

@erick-xanadu. Yes it's ready for review.

Only update llvm and mhlo. Jax sticks with 0.4.28.

Is this safe? normally we have them synced up exactly 🤔

Only update llvm and mhlo. Jax sticks with 0.4.28.

Is this safe? normally we have them synced up exactly 🤔

The .dep-version file hasn't been updated and neither the submodules. I think the only update is updating our compiler to use the one-shot bufferization.

Yes, I tried to make this update less complex. LLVM and MHLO are still under the original (main's) version. I have remove this line of description.

Adding do-not merge label to wait after the release.

authors: dime10 erick-xanadu tzunghanjuang

repo: PennyLaneAI/catalyst


text:
Simplify VJP/JVP/Grad/Jacobian frontend

Description of the Change:
Simplify the unflatten of VJP/JVP/grad/Jacobian and covers more edge cases.

This will be really nice to have in 😎
@rmoyard I think a lot of docstrings/codeblocks (especially the quickstart, sharp bits page, etc.) will likely also need to be updated 🤔

@josh146 I am double checking the docs

I have found some changes in the quickstart and sharp bits, and updated them

@dime10 I have added a note in each function that we support function that returns any pytree-like shape


text:
Info Endpoint

Initial implementation of https://github.com/Peripli/specification/pull/27

Pull Request Test Coverage Report for Build 289

16 of 21 (76.19%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 85.412%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

api/info/info_controller.go
4
9
44.44%

Totals

Change from base Build 279:
-0.2%

Covered Lines:
1089

Relevant Lines:
1275

💛  - Coveralls

Can this be tested with a simple integration test?

Not sure if inside the controller is the place to validate that token_issuer_url actually has openid provided configuration, but generally a validation should be present

authors: coveralls dpanayotov georgifarashev

repo: Peripli/service-manager


text:
Automated release

This is an automated pull request to update from branch feat/new-release-20240531112202

@TorinAsakura Код глянул:
Отсутствие упоминания rees в коде - подобного не наблюдаю
Корректность изменений - Все изменения в порядке на мой взгляд

repo: PersonaClick/ios-sdk


text:
TreeView Performance

Tree View with large datasets, slows my entire application, even then the TreeViews state is not changing, it will slow the entire render loop...
Collapsing all items gets the speed up again.
Perhaps data virtualization needs implementing.
https://github.com/VitalElement/AvalonStudio/commit/c385dfb9971979909885e4e42b765a227ba5e3b1 will repro, open the Sample Project in AvalonStudio once it opens...
open a text file, then try and move the caret by holding down button, it will be slow,
then collapse the treeview to top level, and try moving caret again.... it will be fast.

Actually I think the performance for this case can be achieved quite simply - just don't render controls that are outside the bounds of a parent with ClipToBounds = true.

Ok thanks will give it a go later and report back

This didn't seem to make any difference, perhaps its not rendering, and something is still processing all the items in the treeview?

Ran the profiler without clip to bounds...

must be in the rendering

and with clip to bounds...

then when collapsed there is a huge reduction in cpu usage

Sorry, I don't understand... I've not changed anything yet so the ClipToBounds optimization isn't there yet.

ah sorry I thought you meant that ClipToBounds was ready and you were talking about virtualization

Clip to bounds has worked wonders, thank you.

authors: danwalmsley grokys

repo: Perspex/Perspex


text:
Add support for new octree surface format (Imaris 9)

The new Surfaces format in Imaris 9 is no longer a triangular mesh but octree-based.

Hi, Brad. I would need an Imaris 9 file to work with--I don't have access to Imaris anymore and my current job is not microscopy focused. I'd be willing to look into it as a weekend project, though.

authors: PeterBeemiller bburan

repo: PeterBeemiller/ImarisReader


text:
Possible drain vector in TokenWithInvariants.sol?

I think 7d7ef27b12f15318871c44512b70737176d23c5f might have introduced an attack vector. Also not sure what is meant by "griefing" in that commit.
As I understand, the contract demonstrates how recursive calls to withdraw() and fraudulent calls to deposit(...) would be stopped by a balance check and a throw. I assume it's thought that this.balance >= totalSupply is an acceptable state. It could happen, say, if someone sent more ether than the number of tokens they claim with deposit(amount). Then anyone could withraw the excess, but not so much that the function modifier checkInvariants() would fail.
However, if it was possible to force the contract into thinking that totalSupply has reduced without a reduction in this.balance, then it would be possible to subsequently withdraw the excess without triggering the modifier.
Just learning Solidity ATM, so can't provide actual working exploit code - sorry about that. Consider this two-stage attack:
First, recursively call withdraw() from contract A that has a balance in TWI as balanceOf[A]. Proceed as in the known race-to-empty attack, but at the bottom call, return the stolen ether, and transfer owned tokens to B. (The latter is similar to what TheDAO exploit did.)
After this execution, this.balance of TWI won't have changed, totalSupply will be reduced, and token balance will be transferred from A to B. (Faux stack in next comment.)
Second, execute a "classic" race-to-empty from contract B, up to the same number of times as in the first case. (No faux stack.)
This allows for the withdrawal of up to half of the ether in TWI, and rendering it useless due to totalSupply being reduced to zero. That is, half the tokens are used to extact the ether, and half are burned.

Faux stack for first stage:
totalSupply  this.balance  balanceOf[A]  balanceOf[B]  contract: call
---------------------------------------------------------------------
100          100           10            0             A: TWI.withdraw()
100          100           10            0              TWI: balance = balanceOf[msg.sender];
100          100           10            0              TWI: A.call.value(balance)()
100          90            10            0               A: TWI.withdraw()
100          90            10            0                TWI: balance = balanceOf[A];
100          90            10            0                TWI: A.call.value(balance)()
100          80            10            0                 A: TWI.call(20)("transfer", "B", "10")  // 20 == initial balanceOf[A] * number of desired recursive calls, both known pre-execution
100          100           10            0                  TWI: <transfer(B,10) body run>         // 10 == initial balanceOf[A]
100          100           0             10                 TWI: checkInvariants()                 // passes
100          100           0             10                A: return()                             // depth limit reached, mission accomplished
100          100           0             10               TWI: totalSupply -= balance;
90           100           0             10               TWI: balanceOf[A] = 0;                   // useless
90           100           0             10               TWI: checkInvariants()                   // passes
90           100           0             10              A: return()                               // not deep enough, didn't send anything back
90           100           0             10             TWI: totalSupply -= balance;
80           100           0             10             TWI: balanceOf[A] = 0;                     // useless
80           100           0             10             TWI: checkInvariants()                     // passes
80           100           0             10            A: return()                                 // initial call

Sorry if this is an inappropriate venue for such guesses. Also if TWI.call(<stolenBalance>)("transfer", "B", "10") is not actually possible - again, I'm still learning.

Yeah, I think this works. Well spotted!
To rephrase for my own benefit, and anyone else following along: If you return the ether stolen by a race-to-empty attack before any of the invariants are checked, then the totalSupply will be reduced by the amount you fraudulently withdraw, but the invariants will pass. Then you can perform a second race-to-empty, and the fraudulently lowered totalSupply will mean that the invariants don't see any problem with your large withdrawal.
The original motivation for loosening the invariants was to prevent people "donating" Ether to the contract, and thereby locking all actions.
With the current design of Ether, a possible solution would be to go back to checking strict equality, and reject any Ether transfer that isn't a deposit. This wouldn't work for other tokens, though, where you can't reject transfers. Alternatively, you can have your guards be more intelligent and specific: check that the totalSupply changes by the expected amount at the end of the function. (Function-specific guards aren't discussed in the article, but may be more generally useful than permanent invariants.)
This easily qualifies for the bounty mentioned in the article, so feel free to send me an Ethereum address.

Yay!
0x1488e30b386903964b2797c97c9a3a678cf28eca

Sent! (Since this was the first bug bounty claimed, and since it was a major issue and not just a typo, I sent a bit more than the nominal amount mentioned in the article.)

Ooh this is nice.
Token systems are in general not nearly 'paranoid' enough, it's cool to see this documented and fixed.

This was a brilliant attack, congrats!

Since this issue seems to be getting a bit of attention, I want to make sure it's clear that this code was demonstrating a single security technique, and intentionally left in the race-to-empty vulnerability. Real code should avoid known attacks like race-to-empty, and should have more security checks than a single invariant. This was an excellent attack that shows the necessity of defense in depth!

I'd like to ask a question about line 4.
totalSupply  this.balance  balanceOf[A]  balanceOf[B]  contract: call
---------------------------------------------------------------------
...
100          90            10            0               A: TWI.withdraw()

Won't this fail checkInvariants? (i.e. if (this.balance < totalSupply) throw;)
I still think this contract is hackable but I'm not sure it can be done the way the trace above
suggests.

Would like thoughts on checking the invariant as a precondition too.  Did I miss something or would this fix it?
modifier checkInvariants {
    if (this.balance < totalSupply) throw;
    _
    if (this.balance < totalSupply) throw;
  }

@ethers: I don't think it fixes it, unfortunately. The attacker can return the withdrawn Ether each time before calling the next withdrawal.

@PeterBorah I'm not so sure. I just recently wrote out a full worked example following @veox 's notes above and have run it successfully on a private node. There are two phases to the attack, one where you increase the difference between the contract's ether balance and totalSupply (transferring the tokens away at the last moment) and one where you perform the multiple withdraws.
In the first part of the attack the attacking contract gives back all its ether to TokenWithInvariants in the final transfer call but it's important (for @veox's attack) that it is only done at this point. The key part to their attack is that at the end this.balance is higher than totalSupply. If we simply gave back the value with each call to withdraw then we wouldn't be able to create this differential which is really important for the second part of the attack. I think @ethers' suggestion of putting the check before the _ in checkInvariants will actually do the trick. At least it does for my worked example but there may be some other way to use reentrancy to attack this modified version.
I have written up @veox's  attack in a self-contained repo which is private for the moment. I've been wanting to ask the community whether it is okay to publish things like this. My feeling is that it's okay to talk about the generalities of attacks but not necessarily to give step-by-step instructions, which my repo absolutely does. (I'm new to Ethereum and needed to spell out every step for myself.)
If you're interested I could make you a collaborator on my repo so that you could have a look.

In the first part of the attack the attacking contract gives back all its ether to TokenWithInvariants in the final transfer call but it's important (for @veox's attack) that it is only done at this point.

@sseefried: Perhaps I'm missing something, but I don't think this is true. The key part of the attack is repeatedly invoking the decrease of totalSupply. That decrease (on line 29) is guaranteed to happen unless the transfer fails. In this phase of the attack, where the Ether ends up is irrelevant, except to the invariants.
I'd be happy to take a look at your private repo. Personally, I see no problem in publishing code that illustrates certain attacks, especially against code that isn't actually being used. Hackers won't be discouraged by having to write their own code, and sharing knowledge and examples to test against is valuable.

In the first part of the attack the attacking contract gives back all its ether to TokenWithInvariants in the final transfer call but it's important (for @veox's attack) that it is only done at this point.

@sseefried: Perhaps I'm missing something, but I don't think this is true. The key part of the attack is repeatedly invoking the decrease of totalSupply. That decrease (on line 29) is guaranteed to happen unless the transfer fails. In this phase of the attack, where the Ether ends up is irrelevant, except to the invariants.
In the second phase, it is of course necessary to keep the money, but at that point the totalSupply is lowered, and this can be done safely.
I'd be happy to take a look at your private repo. Personally, I see no problem in publishing code that illustrates certain attacks, especially against code that isn't actually being used. Hackers won't be discouraged by having to write their own code, and sharing knowledge and examples to test against is valuable.

@PeterBorah I was wrong and you were absolutely right. If you pass back the value on the recursive withdraw calls and then on the final transfer call you pass back the remaining value then you have successfully done the first phase of the attack. I implemented it in my repo and it worked like a charm. Thanks for letting me know.

@ethers: OT in relation to this issue, but that modifier currently won't work as expected for functions that return, so careful.
For an example see this article by Dennis Peterson (search for mutex).

@veox Indeed, I submitted this PR before https://github.com/PeterBorah/smart-contract-security-examples/pull/5/files

For posterity's sake: the v0.4 changes in Solidity render the described attack impossible. Specifically, introduction of the built-in payable modifier.
A minimal straightforward update of TokenWithInvariants to Solidity v0.4 would be adding payable to deposit(), and leaving transfer() unpayable (by default). Therefore, one wouldn't be able to "return the stolen ether with transfer()", which was a key point.
In a way, this issue is OK to close. :)

authors: PeterBorah el33th4x0r ethers sseefried veox vessenes


text:
How to download to the brick?

Hi there!
The instructions read, "Once connected you can start a running program by choosing its slot."
However it doesn’t say where or how to choose its slot.  Can you please elaborate?
Thanks in advance!
Philip

Hey @dphaine , there are two ways to select a slot:

When you use the "LEGO Hub: Run program" you will be asked for a slot and also the type of the program you are uploading. This is show on the screenshots just below the text you quoted above.
The other way is by specifying a predefined file header comment as explained here: https://github.com/PeterStaev/lego-spikeprime-mindstorms-vscode#automatic-uploadstart-of-a-python-file

Thank you for your quick response Peter!
The (obvious) bit that we missed was Cmd-Shift-P and then start typing the command.  It might be nice to include this for the noobs.
Big thanks for creating this tool. The Lego editor is painfully buggy so we look forward to using vscode.
Philip

On Aug 6, 2022, at 7:55 AM, Peter Staev @.***> wrote:
Hey @dphaine , there are two ways to select a slot:
When you use the "LEGO Hub: Run program" you will be asked for a slot and also the type of the program you are uploading. This is show on the screenshots just below the text you quoted above.
The other way is by specifying a predefined file header comment as explained here: https://github.com/PeterStaev/lego-spikeprime-mindstorms-vscode#automatic-uploadstart-of-a-python-file
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Yes, the Ctrl+Shift+P is one way to run the program. But also you can use the buttons at the top right of the editor:

Just keep in mind that the first one ("Run Python File") is the default python one that executes locally, which can't work as locally you do not have the hub sepcific libs. Just look for the "Lego Hub:" prefixed ones, those are the ones coming from this extension :)

authors: PeterStaev dphaine


text:
🛑 Petra Documentation is down

In fd78005, Petra Documentation (https://docs.thepetra.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Petra Documentation is back up in ad3aa37 after 11 minutes.

repo: PetraHQ/status


text:
Create Dockerfile

to use it:
install docker
build image
$ docker build . -t focus-stack:latest
then run any way you like
$ docker run -it --rm focus-stack:latest image1.png image2.png
or
$ docker run -it --rm -v $PWD/images_to_stack:/mnt/photos focus-stack bash -c "focus-stack --output=/mnt/photos/res.png /mnt/photos/A1ROI1_IMG-IN-WELL-1Z*.png"

I'm not sure it makes sense to include a Dockerfile that hardcodes one specific revision.
Maybe it would make more sense to have one that actually builds the software?
For just running the software, you could use the AppImage which should work on most Linux distributions without need of installing dependencies.

Thanks.

authors: PetteriAimonen barakplasma

repo: PetteriAimonen/focus-stack


text:
[Clinical Site] Add date/time for notifications

Similar with trial-participant

@Mastaleru https://github.com/PharmaLedger-IMI/clinical-site-ssapp/commit/ffaf3721415fdb6c98452ee64f4857f258241e95

order them by date even if the notification was read

authors: Mastaleru cosmintuca

repo: PharmaLedger-IMI/eco-iot-pmed-workspace


text:
Current Version won't start

Hi, in the current master version:
when I start the project it crashes with:
"Parser Error: Cannot find member "fullscreen_kay_name" in base "OptionsConstants""
When I comment out the lines 50, 66 and 75 in the options_menu_controller.gd it will start.
It may be the options_constants.gd missing const fullscreen_key_name = "fullscreen_mode".
See https://github.com/Phazorknight/Cogito/commit/e923d40175f08ec1cbb19ab10a44c7569d624278, since I am still not able to cherry pick, be it my own stupidity or github ...

That's odd, I've updated the OptionsConstants on my end and they should've been included in the commit. Will look into it.
Fullscreen_key_name is deprecated. Was replaced with windowmode_key_name.

If fullscreen_key_name is deprecated @Phazorknight, then it's possible that you have updated OptionsConstants, but rather the file options_menu.gd wasn't included in your commit, as that file still references fullscreen_key_name:
https://github.com/Phazorknight/Cogito/blob/901a2bef817bbcfbc5e3b3d3ef35568b14e53145/COGITO/EasyMenus/Scripts/options_menu_controller.gd#L50
https://github.com/Phazorknight/Cogito/blob/901a2bef817bbcfbc5e3b3d3ef35568b14e53145/COGITO/EasyMenus/Scripts/options_menu_controller.gd#L66

Edit: Just saw your comment.
Sorry, yeah, updating the options constants for the new menu in turn broke the old menu and any of it's references, which includes the PauseMenu scene and the MainMenu scene.
Will update those to use the new Options, which will fully deprecated the old one, so prepare for that. Will try to get this done today.

Okay, I've just released a quick fix for this in https://github.com/Phazorknight/Cogito/commit/c328226998c00f9a0672b9e6dd61e95c9cc8e720
This basically removes any references to the old options menu / PauseMenu in the current demo scenes and MainMenu scene.
I'm considering this specific issue closed, but will continue to properly deprecate/remove the old options and update in this thread: #55

authors: FailSpy Phazorknight ksjfhor

repo: Phazorknight/Cogito


text:
rename the docker-compose.yml file

Renaming the docker-compose.yml file to docker-compose.example would save few keystrokes. Thanks for a a great app.

Thanks.
Sorry, I don't get it. Why would this save keystrokes?

Maybe because I am a novice git user. When I pull the latest, I don't want to override my custom docker-compose.yml file.
On Monday, March 6, 2023 at 07:31:08 AM PST, Marco Kümmel ***@***.***> wrote:

Thanks.
Sorry, I don't get it. Why would this save keystrokes?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Ok, i understand your problem.
But when using dailytxt, there is no need to clone the whole repo. You can just create a single dir and a docker-compose.yml inside it and paste the content from the docker-compose.yml in this repo. This is the "normal" way to deal with it, i would guess.
Cloning the whole repo is actually only necessary, when you're actively developing on dailytxt. For this reason I don't see a necessity to rename the template-file to some "unreal" name.

authors: PhiTux ghajj

repo: PhiTux/DailyTxT


text:
Swift 4.2 support

'UIImageRenderingMode' has been renamed to 'UIImage.RenderingMode'
and
'UIViewContentMode' has been renamed to 'UIView.ContentMode'
and
'UIViewAnimationOptions' has been renamed to 'UIView.AnimationOptions'
and
'kCAMediaTimingFunctionEaseInEaseOut' has been renamed to 'CAMediaTimingFunctionName.easeInEaseOut'

Here you go: #49

authors: saldous weakfl


text:
Upgrade org.postgresql:postgresql 42.2.20 -> 42.2.21

This PR contains the following updates:

Package
Update
Change

org.postgresql:postgresql (source)
patch
42.2.20 -> 42.2.21

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

Suggested commit message:
Upgrade PostgreSQL JDBC 42.2.20 -> 42.2.21

See:
- https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md
- https://github.com/pgjdbc/pgjdbc/compare/REL42.2.20...REL42.2.21

repo: PicnicSupermarket/oss-parent


text:
older ppn not working after wasm update

Expected behavior
I got a licensed PPN which I used xxd to convert to hexadecimal array for use in the JS wasm flavor of porcupine. It used to work, up until recently when it started to break with the error "failed to initialize porcupine."
I see that even on the demo code for JS the byte arrays have changed for the same wake word. Do I need a new PPN file ? Or there is some other postprocess required on the existing ppn ? It will be great if I could get the hexadecimal equivalent of the PPN we recieved.

If you have a licensed file please contact us directly via email. Most probably you had an evaluation licensed that has expired.

authors: ashubham kenarsa

repo: Picovoice/Porcupine


text:
accelerator.wait_for_everyone()时机有问题，导致多机多卡训练显卡利用率上不去

可以参考
https://github.com/kohya-ss/sd-scripts/blob/71e2c91330a9d866ec05cdd10584bbb962896a99/sdxl_train.py#L651

Thx so much. Changed. Would you plz help to check if the changes are correct: https://github.com/PixArt-alpha/PixArt-sigma/commit/dc27d4f8e9e64f1770957fe3cad0c45c1e627a4f

authors: conansherry lawrence-cj

repo: PixArt-alpha/PixArt-sigma


text:
About New3ds done A9LH OTP file

My new3ds have done A9LH use the new method (no need to downgrad 2.1) .
But after finish it, i found TF card [a9lh] Folder don't contain OTP.BIN file.....
I remember before that , OTP file is in the [a9lh].
Now i want to know, is it  necessary to  obtain this file after i done A9LH ? And how ?

the new method for setting up a9lh on New 3DS doesn't use OTP, hence "otpless". if you really want your console's OTP, you need to go to 2.1.

thanks, when i done a9lh. OTP file is useless ?
what situation i need this files ?

You don't need it.

authors: Plailect david-zzj ihaveamac

repo: Plailect/Guide


text:
fix(api): fixes not null restriction in migration

Describe your changes

fixing migration, making null values for sub-sector and region allowed

Issue ticket number and link
Type of change 🧩

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: AnthonyJWalsh mayya-bond-kc

repo: Planning-Inspectorate/back-office


text:
wtf man

from whisper.model import Whisper, ModelDimensions
ModuleNotFoundError: No module named 'whisper'

from whisper.model import Whisper, ModelDimensions ModuleNotFoundError: No module named 'whisper'

from vits import spectrogram
ModuleNotFoundError: No module named 'vits'
xd

export PYTHONPATH=$PWD

export PYTHONPATH=$PWD

export PYTHONPATH=$PWD

FileNotFoundError: [Errno 2] No such file or directory: '/speaker_pretrain/best_model.pth.tar'
FileNotFoundError: [Errno 2] No such file or directory: 'whisper_pretrain\medium.pt'

omg, why are there so many problems with 5.0.....

@MaxMax2016 thx!

export PYTHONPATH=$PWD

FileNotFoundError: [Errno 2] No such file or directory: '/speaker_pretrain/best_model.pth.tar' FileNotFoundError: [Errno 2] No such file or directory: 'whisper_pretrain\medium.pt' FileNotFoundError: [Errno 2] No such file or directory: 'svc_out.wav'

In Install dependencies section of the readme you can find the links of best_model.pth.tar and medium.pt to download them


text:
Allow hiding percentage for CPU and RAM

I have no idea what I'm doing but it seems to have worked 🎉
Closes #35.

Bump! Any opinion on the PR? I've been using it for a month on my machine and it works like a charm!

Thanks for your contribution @m93a
I am going to try it out on my machine.
In the last period I don't have enough time to work on this and I almost stopped using eOS.
That's the main reason I haven't been active on this repo.


text:
fix: Compatibility with HA 2024.1 - import consts from core

Fixes #94
Fixes #98
Import consts from homeassistant.core
See:

https://github.com/home-assistant/core/pull/105657
https://github.com/home-assistant/core/pull/105640

Thank you @michalbundyra!

Ошибка
Не удалось загрузить мастер настройки: {"message":"Invalid handler specified"}

Unfortunately, it looks like none of the open PR's will be merged anytime soon, or at all.

I'm also waiting for those PR to be merged...

authors: Bilalline donparlor homecb mclever michalbundyra


text:
PBool has no PTryFrom instance

It seems like a PTryFrom instance for PBools is missing; however, this seems a bit more involved because you cannot trivially import PData or PAsData into either of the modules Plutarch.Bool or Plutarch.TryFrom

You could put the instance in the module that defines PData possibly

You could put the instance in the module that defines PData possibly

that will not make it an orphan?

We can't even declare a PTryFrom instance because PInner PBool = PBool

authors: L-as MangoIV

repo: Plutonomicon/plutarch-plutus


text:
Plasma Sword not craftable and incorrect name ingame

Ingame the Sword are only obtainable by creative mode

this is a WIP item

authors: Pocky-l arthurcst

repo: Pocky-l/Mekanism-Evolution


text:
Can't start bot

Can't start the bot through python pokecli.py or with docker. I've tried almost everything and it always says "ImportError: No module named googlemaps" or "ValueError: No JSON object could be decoded" even though i deleted, reinstalled, and reloaded everything. All the configs are correct, it says I have googlemaps already installed, and I don't know what to do.

Post you config file, remove your email and pass and other sensitive information. Or try an online JSON file validator.

There is no need to fix anything atm, read this https://github.com/PokemonGoF/PokemonGo-Bot/issues/2540

authors: Budderpants iamhaller iruy

repo: PokemonGoF/PokemonGo-Bot


text:
fixed transfer worker api crash

try catch exception to prevent bot from crashing

@surfaace please avoid using try...catch for dict like this. Use the .get method.

👍

👍

authors: douglascamata surfaace tstumm


text:
Fix api issues when session stale

Fix bot not working after a session stale. api should not be persisted anywhere else than in the bot object.
#5455

👍


text:
[Android] Fix race condition in ConnectionStateStreamHanderl (#468)

Add extra null check and synchronized block in async callback

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

After this commit, the crash no longer happens for me.
I was able to reproduce the crash about 80% of the time before.

Thanks for creating the issue and fixing it! Looks good!

authors: CLAassistant cbreezier mikolak

repo: Polidea/FlutterBleLib


text:
"Read and write combined" example broken

Describe the bug
The "Read and write combined" example appears to be build-broken.

To Reproduce
Steps to reproduce the behavior:

Copy/paste example
Set up appropriate variables

Setup:

Library version: 1.5.0 & 1.11.0
Android Studio version: 3.6.1
JDK version 1_8 (Java 8)

Additional context
I'm very new to ReactiveX so this could be a very simple syntax issue or even a setup issue on my part (apologies if that's the case), but a fix will be useful for other noobs such as myself.

Yup. It should be .doOnSuccess(). Will fix Today

@ChrisSDC Thank you for this report. It is now fixed.

authors: ChrisSDC dariuszseweryn

repo: Polidea/RxAndroidBle


text:
Substrate Point: Forkless upgrades just change the default

I think there is a chance in the Substrate module @kianenigma to really drive home some points that are set up in Game Theory and also in Blockchain. cc @jonasW3F @coax1d
In Game Theory they talk about the default effect. In blockchain we talk about upgrading networks by forking and how the default is to not change the rules at all. If you want to change anything, you can opt in to the change by updating your node.
In Substrate of course you present forkless runtime upgrades which is one of the killer features of Substrate. I think the point to drive home is that Substrate's forkless upgrade feature simply changes the default.
When using Substrate, the default is to follow the onchain governance whereas pre-substrate, the default is to keep the old rules. Even in Substrate you can still have consensus level forks. And if governance decides something you dislike, you still have the ability to "fork off" and keep the old rules. To take such a non-default position, write some new code and update your node. Same as before.
WDYT?

how the default is to not change the rules at all

I think all you said is true, but if you look at substrate at the meta-blockchain level, the default is still to keep not change the rule, but "rule" here means "do as the WASM blob wishes".

Ah yeah! I exactly agree with you. That's also a great point to make. At the meta-protocol level the rules don't change we just keep executing the wasm as always.
So another also useful and also correct way to frame it is that Substrate provides a mechanism to upgrade the state machine from within the state machine without a consensus fork. If you are dissatisfied with the outcomes of this in-runtime game, you can still perform a regular old consensus fork and change the meta protocol rules from "just follow the wasm" to "follow this other wasm that is the same as the old one and possibly censor upgrade transactions if necessary".

I actually like the perspective that @JoshOrndorff is proposing. I think we can agree that the idea behind it is correct, we just need a precise description. I'll try and correct me if I am mistaken in any of the fine nuances here.
All blockchains (including Polkadot) commonly "follow the consensus rules".  But and in contrast to (most?) other blockchains, we form consensus not on static rules but on flexible ones. Concretely, we automatically follow everything that is legitimated by governance and then automatically adopted by all nodes. So, the rule is the same "follow consensus", but it leads to effectively other outcomes. In Polkadot's case, we obtain forkless upgrades while other blockchains are left with hard forks. What is important here is that Polkadot integrates a collective decision-making system into its consensus, something that not many other blockchains have.
Ultimately, if we touch the "default effect" in this topic, we should also highlight the social layer. Since Polkadot does this from the very beginning, its governance process (now OpenGov) is considered legitimate by pretty much every participant, creating a social norm where following changes (again, legitimated by governance) are the default.

authors: JoshOrndorff jonasW3F kianenigma

repo: Polkadot-Blockchain-Academy/pba-content


text:
Error throw when accessing queryAssignedNodes getter

Description
An error is throw when accessing the getter created by queryAssignedNodes with a filter targeting a slot containing nodes that are not elements.
Repository
https://github.com/ErikGrimes/lit-query-assigned-nodes-issue
Steps to Reproduce
Example:

Clone the repo
npm i
npm run storybook
Navigate to "AssignedNodes" -> "Simple"
Open the devtools console
Click boom

Expected Results
No error is throw
Actual Results
Error is thrown
Chrome
decorators.ts:470 Uncaught TypeError: Illegal invocation
    at decorators.ts:470
    at Array.filter (<anonymous>)
    at HTMLElement.get [as slotted] (decorators.ts:466)
    at HTMLElement.__goBoom (AssignedNodes.ts:20)
    at EventPart.handleEvent (parts.ts:532)
    at HTMLButtonElement.EventPart.__boundHandleEvent (parts.ts:490)

Firefox
Uncaught TypeError: 'webkitMatchesSelector' called on an object that does not implement interface Element.

Safari 14
TypeError: Can only call Element.webkitMatchesSelector on instances of Element

Browsers Affected

[x] Chrome
[x] Firefox
[x] Safari 14

Versions

lit-element: v2.4.0
webcomponents: v2.5.0

This was fixed via https://github.com/Polymer/lit-element/pull/1092/files and will be picked up in the next release which we can prioritize.

It was merged in October 2020 while the latest version came out in August 2020, which version fixes it?

authors: ErikGrimes slavoroi sorvell

repo: Polymer/lit-element


text:
Refine API and refactor

WIP (do not merge). Tests do not pass.

does not rely on Polymer
API

startup:

constructor => initialize => createRoot
connectedCallback => enableUpdate => invalidate

update/render:

property change => invalidate =>
(async) shouldUpdate => update
resolves any updateComplete promise

Hey @sorvell, @rictic mentioned this PR in a chat about other lit-element things. Looking through this, I’m noticing that it seems  like there’s no equivalent for _propertiesChanged(). Is that intentional? Right now my team is using that fairly extensively to make GETs after a necessary ID attribute is set at runtime. We could change to a different pattern if that’s what you recommend.

@justinfagnani PTAL Lots of changes per offline discussion:

The property options have been updated.

The update lifecycle has been updated.

The logic in invalidate is especially tricky and could probably use better factoring.

I'm still calling invalidate in connectedCallback rather than when constructed due to some trickiness with ShadyCSS that we can discuss.

TODO

We need to decide if UpdatingElement should be separate and in this package or broken out.

Need to move the render-helpers into lit-html.

The current convention is _ prefix for protected members and __ prefix for private members. However, looks like this convention is not strictly followed. Examples:
  private __isChanging: Boolean = false;
  private _root?: Element|DocumentFragment;
  _firstRendered() {}
  protected _createRoot(): Element|DocumentFragment

Reflecting attributes in the property setter does not work since Safari does not allow an element to produce attributes in the constructor. We will need to move this to update or specially handle this on first invalidate.

@sorvell I'm trying out this branch on npm dev channel and I'm wondering how getters and setters can co-exist with properties. Namely, .prop=${value} does not work with prop getter and setter. But declaring an explicit prop property causes weird issues with the setter being called twice on invalidate with wrong arguments, etc. What is the right way to do this?

Also, the "Declarative rendering" part of the README needs an update

@ernsheong We introduced invalidateProperty(name, oldValue) to help address this. There's a test here.

Tests failing but only on Firefox due to known timeout issue.

authors: ernsheong jolleekin rickcnagy sorvell


text:
this.$ gets polluted with shadow dom of other components

Hi! I am writing a polymer component and think I might have found something not working quite well with polymer (it might as well be that the error is mine, but have not been able to discover it).
The component is something like this:
<link rel="import" href="./bower_components/polymer/polymer.html">

<polymer-element name="sound-library">
	<template>
		<div id="sound-holder">
			<template repeat="{{ sound in sound_library }}">

				<audio class="sl-audio" src="{{ sound.path }}" id="sound_{{sound.name}}">

			</template>
		</audio>
	</template>
	<script>
	(function(){

		Polymer("sound-library", {

			(...)

			ready: function(){

				this.sound_holder = this.$["sound-holder"];

				this.getSoundsFromAttributes();

				this.buildSoundMethods();

			},

			(...)

	})();
	</script>
</polymer-element>

I also have an example document using that code, in which I am using that component twice, like this:
<sound-library beep="assets/beep1.mp3" notification="assets/notif.mp3" cancel="assets/error.mp3" id="sounds"></sound-library>
	<sound-library beep="assets/beep1.mp3" notification="assets/notif.mp3" cancel="assets/error.mp3" id="sounds2"></sound-library>

When I debug the ready method there is no problem the first time it's called (with this = #sounds), but when it's called the second time, I can find in this.$ nodes from #sounds shadow DOM, even those in the template-repeat (and clearly those shouldn't be found).

The problem might be related to the way in which this.$ is set. However, I find it quite strange that no other components have had this bug, so that's why I think the error could be mine.
I am sorry if I have not made myself clear enough, it's the first time I post an issue.
Thank you.
Braulio Valdivielso

I think the problem might be that you have declared your sound_library
array in the prototype of the element. Instead, create them inside the
create method of the element. Only simple variables can be declated in the
prototype - search for 'array' on this page :
https://www.polymer-project.org/docs/polymer/polymer.html
On 4 January 2015 at 11:05, Braulio Valdivielso Martínez <
notifications@github.com> wrote:

Hi! I am writing a polymer component and think I might have found
something not working quite well with polymer (it might as well be that the
error is mine, but have not been able to discover it).
The component
https://github.com/BraulioVM/sound-library/blob/master/element.html is
something like this:

I also have an example
https://github.com/BraulioVM/sound-library/blob/master/examples/basic.html
document using that code, in which I am using that component twice, like
this:

When I debug the ready method there is no problem the first time it's
called (with this = #sounds), but when it's called the second time, I can
find in this.$ nodes from #sounds shadow DOM, even those in the
template-repeat (and clearly those shouldn't be found).
[image: image]
https://cloud.githubusercontent.com/assets/715372/5604573/1137cc56-93c5-11e4-92d3-6da9eb1679ff.png
The problem might be related to the way in which this.$ is set. However, I
find it quite strange that no other components have had this bug, so that's
why I think the error could be mine.
I am sorry if I have not made myself clear enough, it's the first time I
post an issue.
Thank you.
Braulio Valdivielso
—
Reply to this email directly or view it on GitHub
https://github.com/Polymer/polymer/issues/1069.

I should have mentioned that the same is true of reserved_attribute_names
and sounds; and I'm looking at the code here (in case others need to look
quickly):
https://github.com/BraulioVM/sound-library/blob/master/element.html
On 4 January 2015 at 11:17, Waterman, Max max.waterman@intel.com wrote:

I think the problem might be that you have declared your sound_library
array in the prototype of the element. Instead, create them inside the
create method of the element. Only simple variables can be declated in the
prototype - search for 'array' on this page :
https://www.polymer-project.org/docs/polymer/polymer.html
On 4 January 2015 at 11:05, Braulio Valdivielso Martínez <
notifications@github.com> wrote:

Hi! I am writing a polymer component and think I might have found
something not working quite well with polymer (it might as well be that the
error is mine, but have not been able to discover it).
The component is something like this:

id="sound_{{sound.name}}">

        </template>
    </audio>
</template>
<script>
(function(){

    Polymer("sound-library", {

        (...)

        ready: function(){

            this.sound_holder = this.$["sound-holder"];

            this.getSoundsFromAttributes();

            this.buildSoundMethods();

        },

        (...)

})();
</script>

I also have an example document using that code, in which I am using
that component twice, like this:

When I debug the ready method there is no problem the first time it's
called (with this = #sounds), but when it's called the second time, I can
find in this.$ nodes from #sounds shadow DOM, even those in the
template-repeat (and clearly those shouldn't be found).
The problem might be related to the way in which this.$ is set. However,
I find it quite strange that no other components have had this bug, so
that's why I think the error could be mine.
I am sorry if I have not made myself clear enough, it's the first time I
post an issue.
Thank you.
Braulio Valdivielso
—
Reply to this email directly or view it on GitHub.

Ok, just now I saw that the problem had nothing to do with this.$ but with sound_library, and then you have answered!
Thank you very much, you really helped me!

authors: BraulioVM davidmaxwaterman

repo: Polymer/polymer


text:
Missing scrollbars, and mouse wheel not working

https://www.polymer-project.org/docs/start/creatingelements.html
I am using Firefox 34.0.5. I am making the assumption that the web page above is written using Polymer.
I load the webpage in a large Firefox window. It has a scrollbar and the mouse wheel allows scrolling as expected.
I make the navigation window narrower until the navigation panel at the left disappears and a hamburger icon appears. The scrollbar is still visible and the mouse wheel still works.
I click on the hamburger and the navigation panel reappears. However the scrollbar disappears and the mousewheel stops working.
I enlarge the width of the window back to approximately its original size.
The scrollbar is still missing and the mouse wheel is still non-functioning.

This sounds like it should be moved to the Polymer/docs repo.


text:
Polymer.Base.async "infinite loop" condition

Please consider the following contrived usage of Polymer.Base.async:
<link rel="import" href="../polymer/polymer.html">
<script>
  function AsyncAlpha() {
    // Queue a task:
    Polymer.Base.async(function() {
      console.log('alpha');

      // Cause a second task to be queued:
      AsyncBeta();

      // Throw an exception before the first task returns:
      throw new Error('ANY ERROR');
    });
  }

  function AsyncBeta() {
    Polymer.Base.async(function() {
      console.log('beta');
    });
  }

  AsyncAlpha();
</script>

The above example will cause the first task ("alpha") to be re-called in what is effectively an infinite loop. In order to reproduce this condition, a second task ("beta") must be queued before the first task returns, and an exception must be thrown after the second task is queued but before the first task returns.

Yes I had the same issue, when I ported a rather complicated element from 0.5 to 1.0.
A JS error caused an infinite loop when it was thrown in an async callback.

Is this a dup of #1759?

@arthurevans yes, it's a dupe (sorry!). I looked for potential reports of this bug, but didn't notice #1759 for some reason. Thanks for noticing this :beers:

On the other hand, the description of the conditions to produce the error in #1759 is incomplete according to my experience with the bug.

authors: arthurevans cdata timeu


text:
Using native Web Components V1 with Polymer 1.x

Description
If you create a native V1 web component (Chrome only) using a template element (using document.currentScript.ownerDocument to get the template reference) and try to use it in a Polymer element (using an HTML Import) then document.currentScript is null. This isn't the case if you use the element outside of any Polymer element within an application that uses other Polymer elements ("dom-bind" also gives the error).
I suspect the issue might be related to the fact that the V1 element always errors when declared within a template when used with Polymer.
Expected Results
It should just work as expected...
Actual Results
document.currentScript is null, so the element isn't rendered.
Browsers Affected

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari 9
[ ] Safari 8
[ ] IE 11

Versions

Polymer: v1.7
webcomponents: v1 (native)

Ah, I was just being dumb - document.currentScript is null is always null in callbacks when the containing script isn't the main document. I just have to capture document.currentScript outside of my custom element declaration.


text:
Eliminate collection. Fixes #3946

Reference Issue
Fixes #3946: dom-repeat doesn't stamp correctly (which is a 2.x-specific issue; see below for related 1.x issues that this will also solve).
Description
This is a significant change that eliminates the Polymer.Collection abstraction from Polymer 2.x.
This abstraction aimed to assign unique keys to Arrays via a behind-the-scenes store associated per array via WeakMap, along with integration into Polymer's notifying array mutation API's.  The abstraction allowed for two-way binding into elements repeated from arrays by virtue of stable keys providing unique paths to bound array items, with efficient updating of the rendered items via splices.
However, the system was inherently complex and in the end the theoretical efficiency gained did not pay for itself in terms of the cognitive overhead for things like key-based paths (items.#5.value), and a long tail of issues related to lack of support for duplicate array items and primitives via this approach.  Likewise, as #3946 pointed out, it also was fundamentally incompatible with a major goal of the 2.0 release, which is to eliminate the requirement to use set/notifyPath (although the API remains and will still be more optimal in cases) by avoiding use of (default) object identity in Polymer's dirty-checking, since Collections were associated to arrays via object identity.
This change results in dom-repeat simply reacting to items or items.splices by iterating the items array and re-assigning item, index, and origIndex (index of item in original array prior to applying user sort/filter) for each change.  This approach was already basically best-in-class on the dbmon benchmark which always took the "full refresh" code path, and still leaves room for more straightforward optimizations in the future.
Path notifications are still handled, but using the original index in the path where previously key was used (which is possible since the new rendering stores the itemsIdx<->instIndex mapping upon each change to items).  The main breaking changes are that:
a. Polymer.Collection is now removed, and all array notifications are now sent directly with the index rather than the key
b. array.splices observers will still receive an object that only contains indexSplices, but will no longer contain keySplices
Note, this change also resolves (or makes moot) the following 1.x issues; it is likely that these will only be resolved in the 2.x branch due to the nature of the breaking changes required to resolve:

#1913: dom-repeat: Duplicate values result in unsynchronized data
#3062: Duplicate strings in array while using 'dom-repeat' throws error: 'Uncaught Error: unexpected key undefined'
#3377: notifySplices fails to notify about changes in array of primitives

LGTM

authors: kevinpschaaf sorvell


text:
[Question] - Are there the ways to run 'wct test' in Batch mode?

This means that no browsers windows will be opened, only the tests results will be reported in Console.

+1

authors: hyyan pandareloaded

repo: Polymer/web-component-tester


text:
Revert a comment that was merged accidentally.

Ooops!

/gcbrun

repo: PolymerLabs/arcs


text:
<template repeat='{{groups as group}}'>

test

</template>

Fails with Line 1: Unexpected identifier both using the tool and on your interactive version.
Thanks for a great tool that is saving us tons of time :)

Never mind, works with the group in groups syntax.

repo: PolymerLabs/polyup


text:
Functional Component with UseState Hook

It doesn't work if you use component multiple times.
Try author example: https://codesandbox.io/s/vn66kq7mml
Duplicate <Menu />
Run jsfiddle, handleClickOutside is only triggered for the last component added.

Dupplicate of https://github.com/Pomax/react-onclickoutside/issues/329
I switched to react-cool-onclickoutside whichs works fine using hooks.

repo: Pomax/react-onclickoutside


text:
RDP module doesn't shows correct result

Describe the bug
When trying to log in with RDP module, it gives the following error:

But I can log in manually with the same creds:

To Reproduce
Expected behavior
It should output that I can log in or 'pwd3d!'
Crackmapexec info

OS: Kali 2022.4
Version of CME 5.4.0

hi i have the same issue how did you fixed  ?

Hi, there was a bug in the rdp protocol which got fixed with the commit d00a9bafeb0fc6df0718486ded5087b55b0bd50b.
As there was no official release since then it might be possible that your version does not have the bugfix if you downloaded crackmapexec via apt or pip (/pipx).
You can try to clone the repository and install it with pipx install .. That might solve your problem (and maybe was the original problem here).

authors: NeffIsBack lavclash75 prismbreak

repo: Porchetta-Industries/CrackMapExec


text:
No and_surrounding_cells parameter available for Changeset calculations

I ran into issues with correctly generating peering cells when using changesets in my project, but did not have the issue using update_terrain_cells and set_cell. Upon looking into it, I noticed that _widen is being called a second time here when and_surrounding_cells is set to true. I tried calling it a second time in the create_terrain_changeset function here and it fixed my issue. I would suggest the same approach as with update_terrain_cells, where the and_surrounding_cells value is provided. It can be defaulted to false if you are worried about backwards compatibility as well, but there are definitely some use cases where it would be needed. I can put together a PR in like 3 minutes if you want, but I am not sure if there is testing you would want to perform first.

Also I can open a new issue for this but it is at least somewhat related. When using changesets and doing chunk loading, by far the longest remaining frame time is from calling that _widen function mentioned above. When attempting to rework things to run the chunk loading in a WorkerThreadPool task that then kicks off the changeset function (and calls the subsequent group task in BetterTerrain) I have issues with what seems to be neighbor/peering cells. For some reason, the cells retrieved in needed_cells and loaded into types here don't line up with the cells expected to be in types in this line here whenever the code is being run in a separate thread, whether I use changesets or call the set_cell and update_terrain_cells functions. I tried to debug this for a while without much progress since I don't have a lot of background on the peering/neighbor cell logic. @Portponky do you have any insights here that could help?

repo: Portponky/better-terrain

license: Unlicense


text:
Bot vice

New Port for { Game Title }
Game Information

Title: { Game Title }
URL: { Link to project page or source control page }

Submission Requirements
CFW Tests
Ensure your game has been tested on all major CFWs:

[x] AmberELEC
[ ] ArkOS
[ ] JELOS

Resolution Tests
Test all major resolutions:

[ ] 480x320
[ ] 640x480
[ ] 720x720 (RGB30)
[ ] Higher resolutions (e.g., 1280x720)

File Structure

Your port should have the following structure:

portname/

port.json
README.md
screenshot.jpg
cover.jpg
Port Name.sh
portname/

Additional Resources
For an in-depth guide on creating a pull request, refer to: PortMaster Game Packaging Guide

Sorry... made a boo boo in the .sh file

repo: PortsMaster/PortMaster-New


text:
posthog.reset(true) is not available on posthog react native

posthog.reset() results in the device ID being reused for the anonymous ID. By default the existing device ID is reused, but if you'd like a fresh device ID to be generated instead, you should call posthog.reset(true).

reset(true) is not available for react native. Can we have the same feature to allow users with multiple accounts to not be merged in the events? This also prevents adequate testing to be done while developing locally since all previous events with even a different email or unique ID get merged with old data.

Where did you read that? Feels like something that might be outdated.
Current docs are here and indicate it is possible.

Where did you read that? Feels like something that might be outdated.
Current docs are here and indicate it is possible.

passing true results in this error: Argument of type 'boolean' is not assignable to parameter of type 'PostHogPersistedProperty[]'

For react-native the API is slightly different (as you just shared). .reset()will reset all properties but you can pass in a special object to keep some properties if needs be. This is very specific though, so you don't need to worry about it.

repo: PostHog/posthog-react-native


text:
Change the home page design to match the Sherlock theme

This PR changes the design of the home page from the legacy theme to the Sherlock theme.
*Note:
This PR is for the overall rating scores. We need to make it to a swipeable view that will include the 5 question categories.
We also need to update the sort by function. Right now, it is just a placeholder.

I checked the deployment and it's looking great!
One thing—are some text too low contrast with the background?
For example, words like "All Reviews" and the author names are muted on my screen:

authors: jazellemaira nsunami

repo: PostReview/postreview-app


text:
Add Documentation for Auto-documenting/Wiki Resource Module Structure

There are now several resource modules that have moved over to using @BrianFarnhill 's auto documentation/wiki generation structure. These modules are SharePointDsc, xNetworking, xStorage and xDFS (with xCertificate being moved). The repo structure and files in the modules are slightly different to the standard module and so we should provide documentation on how this structure differs.
This was raised in this issue: https://github.com/PowerShell/DscResources/issues/278

Maybe we should hold off on this until we see if issue https://github.com/PowerShell/DscResource.Tests/issues/225 can be a reality or not?

Agreed - hopefully we can find a way to standardize. I just keep running out of time :cry:

Yes me too... Looking into automating labels between reviews and closing issues. 🙂

authors: PlagueHO johlju

repo: PowerShell/DscResources


text:
Update powershell formula to version 7.2.2

PowerShell 7.2.2 released on March 16: https://github.com/PowerShell/PowerShell/releases/tag/v7.2.2

LGTM :shipit:

authors: bmkaiser mgreenegit

repo: PowerShell/Homebrew-Tap