Funding Xopowo Team

Where’s the value in Xopowo?
We believe Xopowo's true value is two-fold.
Firstly, the team takes ownership of web maintenance across the entire Yearn ecosystem. This maintenance work allows other yTeams to innovate and ship products knowing they will be supported by Xopowo (and working with contributors they trust).
However Xopowo's true value and potential lies in our ability to ship new and innovative projects that have the potential to make a real impact and generate real revenue. These projects are varied, such as the prior total revamp of yearn.fi(nance) or entirely new products like dump.services.
Furthermore, Xopowo is able to take projects from idea inception all the way to market in a self-reliant manner without reliance or dependency on other teams or individuals.
In short: Xopowo is committed to supporting existing Yearn projects while innovating and shipping new ones.
Mini dump.services case study
(tldr; a huge success)
Launch date: May 3rd
Partnership with CoW, SAFE in the works.
In the first 24 hours of being live:
140k views
270 RTs
730 likes
75 comments
Engagement from some of the biggest names on CT (Cobie, Degen Spartan, etc)
Peak of 600 visitors to site with constant ~40.
$122,377 of value transacted in first 12 hours.
Scope
The Xopowo Team (pronounced Horosho Team) has been working behind the scenes and has successfully created several projects around Yearn. The team handles everything from prototyping to launching functional products to the market.
Additionally, the team is committed to improving and maintaining the projects all the projects created by Yearn's frontend team.
Revenue generating websites (60% effort)

yearn.finance

OP staking
yCRV
yBribe
veYFI

yAudit
dump.services
more new stuff to come

Infrastructure (10% effort)

Web lib | Web Template
yDaemon

Meta
Risk

Strategic (15% effort)

B2B Dashboard
ape.tax
yearn.clinic
NFTreasury.click
Macarena.finance

Cutting out (15% effort)

Ledger plugin
yWorld
yBrand
yHack
Bowswap
yVempire | yMigrate
yearn-issues
Vaults at Yearn
ySync
Yearn SDK

Plan
The Xopowo team is committed to continuing to create products that bring new users to Yearn through innovative approaches and new functionality.
To make this possible, it is important to maintain the current website. We, therefore, propose that the Xopowo team maintains Yearn's website, in addition to creating new projects.
Additionally, the team is going to be searching for additional funding opportunities through grants from other projects. This funding will enable the team to create products that bring added value to Yearn, such as integrations with other protocols and complementary functions that enhance the user experience.
In the future, the Xopowo Team may seek to reduce its dependence on grants from Yearn and move towards a revenue-sharing scheme. The team believes that this approach will help align its incentives with Yearn's interests while also promoting sustainable growth.
People

Major
Evan
saltyfacu
draper
0xBasic
Chef
0xMirim
Itzabelli

And other contributors via bounties.
Money
We propose a dual approach to funding contributions toward the development and maintenance of our projects. Firstly, we plan to distribute a grant to each person working on a project.
Secondly, we will use bounties to fund isolated contributions or contributions linked to projects in maintenance mode. This approach will enable us to incentivize individual contributors, ensuring the continued success and growth of our projects.
Our breakdown:

Description
Token
Amount

Contributors
DAI
69500

Contributors
YFI
5.1

Infra
DAI
2000

~60% of the grant funding is allocated toward engineers

Amount

71,500 DAI per month
5.1 YFI per month

Wallet address
0x4F909396A75FE9d59F584156A851B3770f3F438a
Reporting
Monthly

Monthly Report 05.2023
Macarena

https://github.com/yearn/macarena-finance/pull/32
https://github.com/yearn/macarena-finance/pull/33

Yearn.fi

https://github.com/yearn/yearn.fi/pull/150
https://github.com/yearn/yearn.fi/pull/151
https://github.com/yearn/yearn.fi/pull/152
https://github.com/yearn/yearn.fi/pull/153
https://github.com/yearn/yearn.fi/pull/154
https://github.com/yearn/yearn.fi/pull/155
https://github.com/yearn/yearn.fi/pull/156
https://github.com/yearn/yearn.fi/pull/158
https://github.com/yearn/yearn.fi/pull/160
https://github.com/yearn/yearn.fi/pull/161
https://github.com/yearn/yearn.fi/pull/163
https://github.com/yearn/yearn.fi/pull/165
https://github.com/yearn/yearn.fi/pull/167
https://github.com/yearn/yearn.fi/pull/168
https://github.com/yearn/yearn.fi/pull/170
https://github.com/yearn/yearn.fi/pull/171
https://github.com/yearn/yearn.fi/pull/172
https://github.com/yearn/yearn.fi/pull/176
https://github.com/yearn/yearn.fi/pull/178
https://github.com/yearn/yearn.fi/pull/180
https://github.com/yearn/yearn.fi/pull/183
https://github.com/yearn/yearn.fi/pull/186
https://github.com/yearn/yearn.fi/pull/187
https://github.com/yearn/yearn.fi/pull/189
https://github.com/yearn/yearn.fi/pull/190
https://github.com/yearn/yearn.fi/pull/191
https://github.com/yearn/yearn.fi/pull/195
https://github.com/yearn/yearn.fi/pull/198
https://github.com/yearn/yearn.fi/pull/201
https://github.com/yearn/yearn.fi/pull/215

Web Lib

https://github.com/yearn/web-lib/pull/239
https://github.com/yearn/web-lib/pull/245
https://github.com/yearn/web-lib/pull/248
https://github.com/yearn/web-lib/pull/249
https://github.com/yearn/web-lib/pull/250

Web Template

https://github.com/yearn/web-template/pull/83

Reviews + Contributor

https://github.com/yearn/web-lib/pull/243
https://github.com/yearn/yearn.fi/pull/206
https://github.com/yearn/yearn.fi/pull/192
https://github.com/yearn/yearn.fi/pull/214
etc...

Monthly Report 06.2023
Karelian Pie
Yearn.fi

https://github.com/yearn/yearn.fi/pull/225
https://github.com/yearn/yearn.fi/pull/226
https://github.com/yearn/yearn.fi/pull/228
https://github.com/yearn/yearn.fi/pull/229
https://github.com/yearn/yearn.fi/pull/230
https://github.com/yearn/yearn.fi/pull/231
https://github.com/yearn/yearn.fi/pull/234
https://github.com/yearn/yearn.fi/pull/235
https://github.com/yearn/yearn.fi/pull/239
https://github.com/yearn/yearn.fi/pull/241
https://github.com/yearn/yearn.fi/pull/242
https://github.com/yearn/yearn.fi/pull/243
https://github.com/yearn/yearn.fi/pull/247
https://github.com/yearn/yearn.fi/pull/248
https://github.com/yearn/yearn.fi/pull/250
https://github.com/yearn/yearn.fi/pull/251
https://github.com/yearn/yearn.fi/pull/252
https://github.com/yearn/yearn.fi/pull/253
https://github.com/yearn/yearn.fi/pull/254
https://github.com/yearn/yearn.fi/pull/255
https://github.com/yearn/yearn.fi/pull/258
https://github.com/yearn/yearn.fi/pull/260
https://github.com/yearn/yearn.fi/pull/264

Web lib

https://github.com/yearn/web-lib/pull/259
https://github.com/yearn/web-lib/pull/260
https://github.com/yearn/web-lib/pull/261
https://github.com/yearn/web-lib/pull/269
https://github.com/yearn/web-lib/pull/275

Macarena

https://github.com/yearn/macarena-finance/pull/43
https://github.com/yearn/macarena-finance/pull/44
https://github.com/yearn/macarena-finance/pull/45

ySync

https://github.com/yearn/ySync/pull/93
https://github.com/yearn/ySync/pull/96

Reviews

https://github.com/yearn/yearn.fi/pull/208
https://github.com/yearn/yearn.fi/pull/210
https://github.com/yearn/yearn.fi/pull/207
https://github.com/yearn/yearn.fi/pull/223
https://github.com/yearn/yearn.fi/pull/222
https://github.com/yearn/yearn.fi/pull/205
https://github.com/yearn/yearn.fi/pull/214
https://github.com/yearn/yearn.fi/pull/217
https://github.com/yearn/yearn.fi/pull/219
https://github.com/yearn/yearn.fi/pull/220
https://github.com/yearn/yearn.fi/pull/211
etc...

Monthly Reports 06.2023
0xBasic
Yearn-Assets
Also worked on velo icons with help from dudesahn

https://github.com/yearn/yearn-assets/commit/4db1bb6b68ad0c7a75a1b3bf01025d2c22cfbaa7
https://github.com/yearn/yearn-assets/commit/abb3c9c82ba2acefd0f95272a95ca132382d3ca9

yDaemon
Update meta/risk

https://github.com/yearn/ydaemon/commit/e84ea33fe503a437215c75af46d7ecad658bc44d
https://github.com/yearn/ydaemon/commit/d10ce20855f024528a50a4075a1d89c8f5dfbc77
https://github.com/yearn/ydaemon/commit/05585ffe6c4726ba909214431efbc3fc83ff42d4
https://github.com/yearn/ydaemon/commit/df68bd47154f554894e5054ff4bbc917beaeecdb
https://github.com/yearn/ydaemon/commit/19311b0ad3c661443a0d3ebca47168c1877f96cc
https://github.com/yearn/ydaemon/commit/13b4e1dec0d7b624e720b25bda8168689ea4af31

Itzabelli
yearnfi
Fixes, updates, maintenance

https://github.com/yearn/yearn.fi/pull/244
https://github.com/yearn/yearn.fi/pull/245
https://github.com/yearn/yearn.fi/pull/246
https://github.com/yearn/yearn.fi/pull/249

ape-tax
Fixes, updates, maintenance

https://github.com/saltyfacu/ape-tax/pull/215
https://github.com/saltyfacu/ape-tax/pull/216

Mirim
ape-tax
Working towards V3 integration, migrated to wagmi as pre-req, tested with foundry (anvil)

https://github.com/saltyfacu/ape-tax/pull/214

Solved merge conflicts to bring V3 branch up to speed with separate changes

https://github.com/saltyfacu/ape-tax/pull/196/commits/9120c6ac5be01c29abe2bf20a19ba7c8948928ef

yPartners
Deployed new version to production

https://github.com/yearn/yPartners/pull/178

yDaemon
Reviews

https://github.com/yearn/ydaemon/pull/273
https://github.com/yearn/ydaemon/pull/276
https://github.com/yearn/ydaemon/pull/283

Major
yDaemon
Fixes, updates, maintenance

https://github.com/yearn/ydaemon/commit/3790f2499e2c17a1415876b3d829c789383cb7a0
https://github.com/yearn/ydaemon/commit/eea4845f84579b02d7bb5ab56fb058387250d330
https://github.com/yearn/ydaemon/commit/c5223c4c0b86fa60e27228fb2f85ee7d2ac08ad6
https://github.com/yearn/ydaemon/commit/38405de750ff92ace1850066aa4ee7ca6cdf7cea
https://github.com/yearn/ydaemon/commit/cc24b65aadc96d800cf2187d084d73d816d6be76
https://github.com/yearn/ydaemon/commit/75a5dae2652c47bcad0fefea38881f29b9d432e3
https://github.com/yearn/ydaemon/commit/e8e9023465d742fab045236952a4bfa6fb915e4e

yearnfi
Fixes, updates, maintenance

https://github.com/yearn/yearn.fi/pull/205
https://github.com/yearn/yearn.fi/commit/a833d5cbbf1ea5f9afab2095496f103c46c08b10
https://github.com/yearn/yearn.fi/commit/1268de2a9eca5273a0a998c95347ac0b5b663079
https://github.com/yearn/yearn.fi/commit/d879716ddd6d0dcaff61a8f665c31b40972f88f9
https://github.com/yearn/yearn.fi/commit/2247df7fef28bbcf34b1c0f5f2d1d8de5bf84ff4
https://github.com/yearn/yearn.fi/commit/f5f62b0f51db202744042b90d4c18b428a6b5d51
https://github.com/yearn/yearn.fi/commit/fb416208e41ef33ee726e55bedd77ea04a7d40c6
https://github.com/yearn/yearn.fi/commit/7bcd548da54de7d578284c647788ad43355d0bf2
https://github.com/yearn/yearn.fi/commit/a3938192969a5dc26222f1507d97d2e6e5ea78f2
https://github.com/yearn/yearn.fi/commit/4a495e5adc1d549b59d43844f3823bc45e56b6a0
https://github.com/yearn/yearn.fi/commit/f9bf708eca0c1135a8436ae2d0d677080c527e2e
https://github.com/yearn/yearn.fi/commit/84d2ccc699ec067a316f69b6aa208d8e88a2db9a
https://github.com/yearn/yearn.fi/commit/6d8951ebab551793b8ef7384e853c34d887c9d14
https://github.com/yearn/yearn.fi/commit/0053d9261a3789efffd9c3cee0eacd136bed8668
https://github.com/yearn/yearn.fi/commit/9af7b64b7c2e1109b9bf0caa49547a7152dd4918
https://github.com/yearn/yearn.fi/commit/296b8919531753a366fdda95a677d05a54deeba1
https://github.com/yearn/yearn.fi/commit/36e1f4a53713f753e913b1213d075e9313b67b79
https://github.com/yearn/yearn.fi/commit/75a3c6c8560806711c9fc7974dfc92a0fa73119d
https://github.com/yearn/yearn.fi/commit/7764959a5859f36ced6456d178715757b69bd295
https://github.com/yearn/yearn.fi/commit/d7fe67daab24b6bf34e4adcf33aca9cb53655c1d

Monthly Report 07.2023
Karelian Pie
Yearn.fi

https://github.com/yearn/yearn.fi/pull/248
https://github.com/yearn/yearn.fi/pull/258
https://github.com/yearn/yearn.fi/pull/268
https://github.com/yearn/yearn.fi/pull/270
https://github.com/yearn/yearn.fi/pull/278
https://github.com/yearn/yearn.fi/pull/280
https://github.com/yearn/yearn.fi/pull/281
https://github.com/yearn/yearn.fi/pull/282
https://github.com/yearn/yearn.fi/pull/284
https://github.com/yearn/yearn.fi/pull/285
https://github.com/yearn/yearn.fi/pull/288
https://github.com/yearn/yearn.fi/pull/289
https://github.com/yearn/yearn.fi/pull/292
https://github.com/yearn/yearn.fi/pull/293
https://github.com/yearn/yearn.fi/pull/303

Web lib

https://github.com/yearn/web-lib/pull/281
https://github.com/yearn/web-lib/pull/287
https://github.com/yearn/web-lib/pull/288
https://github.com/yearn/web-lib/pull/289

ySync

https://github.com/yearn/ySync/pull/101
https://github.com/yearn/ySync/pull/102
https://github.com/yearn/ySync/pull/106
https://github.com/yearn/ySync/pull/107

Reviews

https://github.com/yearn/yearn.fi/pull/298
https://github.com/yearn/yearn.fi/pull/306
https://github.com/yearn/yearn.fi/pull/307
https://github.com/yearn/yearn.fi/pull/304
etc...

Monthly Report 07.2023
Itzabelli
ape-tax
https://github.com/saltyfacu/ape-tax/pull/219
https://github.com/saltyfacu/ape-tax/pull/222
https://github.com/saltyfacu/ape-tax/pull/224
https://github.com/saltyfacu/ape-tax/pull/225
yearn-fi
https://github.com/yearn/yearn.fi/pull/277
https://github.com/yearn/yearn.fi/pull/286
https://github.com/yearn/yearn.fi/pull/287
https://github.com/yearn/yearn.fi/pull/306
https://github.com/yearn/yearn.fi/pull/307
yearn-devdocs
https://github.com/yearn/yearn-devdocs/pull/334
0xMirim
ape-tax
https://github.com/saltyfacu/ape-tax/pull/221

https://github.com/saltyfacu/ape-tax/pull/221/commits/57e6e3f24b7fe44f6fcd3f376d969b9d08d09aaa
https://github.com/saltyfacu/ape-tax/pull/221/commits/489462d92dbea711da1b24785b215d6029d9668f
https://github.com/saltyfacu/ape-tax/pull/221/commits/10601a4bd7c3aaf7887bf79cb4c661f2ac06c66c
https://github.com/saltyfacu/ape-tax/pull/221/commits/bfdbf4c9f9aa14166649b391c92a5df3ed2c7a06
https://github.com/saltyfacu/ape-tax/pull/221/commits/c09bc06770cf5f2b97f933b91b3a6f2f38cb8241
https://github.com/saltyfacu/ape-tax/pull/221/commits/1a41ab902c119dedc29c17b86ca74ed82c0030d1
https://github.com/saltyfacu/ape-tax/pull/221/commits/93c34944a63861f6d0115ec0534a9074e175ca6f
https://github.com/saltyfacu/ape-tax/pull/221/commits/431a116cc1d3616ded74292fb6d69ef19faa0b28
https://github.com/saltyfacu/ape-tax/pull/221/commits/32ac010b86eeb5d704f8c5cf5fc7483eddc0e891
https://github.com/saltyfacu/ape-tax/pull/221/commits/c96ce55d071f8632a7e59514bf156c4aa130edad
https://github.com/saltyfacu/ape-tax/pull/221/commits/46250ad8c7a4c57af326f580428414be7e3a7211
https://github.com/saltyfacu/ape-tax/pull/221/commits/80f3d9ae53559411ec848da08702f611e564fbd5
https://github.com/saltyfacu/ape-tax/pull/221/commits/25b61b9257c19129f28bf82cb823cd8f9a5daa65
https://github.com/saltyfacu/ape-tax/pull/221/commits/213fa313bba8cc49d2ed22b5d080c88b4fa720e9

https://github.com/saltyfacu/ape-tax/pull/214

https://github.com/saltyfacu/ape-tax/pull/214/commits/6afc41057be46814fdffdb06b10962030b69e1dd
https://github.com/saltyfacu/ape-tax/pull/214/commits/a1dc68cc3d7a97eb00abc5cdee7ee6a2e096d62f
https://github.com/saltyfacu/ape-tax/pull/214/commits/e40ec488ffce8668c45f86510302d43a4942a91e

https://github.com/saltyfacu/ape-tax/pull/217
web-lib
https://github.com/yearn/web-lib/pull/282
Issues
https://github.com/saltyfacu/ape-tax/issues/220
https://github.com/saltyfacu/ape-tax/issues/223
https://github.com/saltyfacu/ape-tax/issues/218
Reviews
https://github.com/saltyfacu/ape-tax/pull/224
https://github.com/yearn/ydaemon/pull/287
https://github.com/yearn/ydaemon/pull/294
https://github.com/yearn/ydaemon/pull/297
https://github.com/yearn/ydaemon/pull/298
0xBasic
yDaemon
Updates to meta/risk
https://github.com/yearn/ydaemon/pull/304
https://github.com/yearn/ydaemon/pull/298
https://github.com/yearn/ydaemon/pull/297
https://github.com/yearn/ydaemon/pull/296
https://github.com/yearn/ydaemon/pull/294
https://github.com/yearn/ydaemon/pull/292
Retire vaults
https://github.com/yearn/ydaemon/pull/303
https://github.com/yearn/ydaemon/pull/302
Assets
With help from Icon Team/dudesahn
https://github.com/yearn/yearn-assets/pull/259
https://github.com/yearn/yearn-assets/pull/251
Rebased to tokenAssets
https://github.com/SmolDapp/tokenAssets/pull/48
https://github.com/SmolDapp/tokenAssets/pull/44
https://github.com/SmolDapp/tokenAssets/pull/39
https://github.com/SmolDapp/tokenAssets/pull/34
https://github.com/SmolDapp/tokenAssets/pull/30
https://github.com/SmolDapp/tokenAssets/pull/26
Dudesahn
Assets
https://github.com/yearn/yearn-assets/pull/263
https://github.com/yearn/yearn-assets/pull/262
https://github.com/yearn/yearn-assets/pull/261
https://github.com/yearn/yearn-assets/pull/260
https://github.com/yearn/yearn-assets/pull/250
Major
yDaemon
https://github.com/yearn/ydaemon/pull/299
https://github.com/yearn/ydaemon/pull/293
https://github.com/yearn/ydaemon/commit/1ec946134a34f88681197fa463dda8ce167efcb6
https://github.com/yearn/ydaemon/commit/fdd0ffd26581383761c6791aef0145956ffb1aa0
https://github.com/yearn/ydaemon/commit/9d6cd7b2b6e39b0550df93e10ac7643e41491221
https://github.com/yearn/ydaemon/commit/db35da16c3fe739f45781c0065854258380cc442
https://github.com/yearn/ydaemon/commit/a823c48703f6e935ac2f947fa07af322b386f086
https://github.com/yearn/ydaemon/commit/8620b3ef38741c9762b9ed4e048aa51da40d8887
https://github.com/yearn/ydaemon/commit/8d685c25688cc1cd83504deb57ba828dbd495565
yearn.fi
https://github.com/yearn/yearn.fi/pull/308
https://github.com/yearn/yearn.fi/pull/297
https://github.com/yearn/yearn.fi/pull/295
https://github.com/yearn/yearn.fi/pull/276
https://github.com/yearn/yearn.fi/pull/270


RestrictChatMemberAsync does not send until_date correctly

Steps to reproduce:
call RestrictChatMemberAsync with untilDate = DateTime.UtcNow.AddDays(2)
Expected  behavior
Field sent as unixtime int. according to docs https://core.telegram.org/bots/api#restrictchatmember
User restricted only for 2 days
Actual behavior
Sent as string datetime until_date":"2018-03-07T09:28:46.0342526Z","
User restricted forever
Environment data
NuGet Package Version: 13.4.0
.NET Version:  4.6.1
IDE: VS2017
App: Desktop

Looks like fixed in 14.2.0-rc-452


Fixed css bug for Facebook sign up text in site footer

Motivation
Wanted to contribute to my first open-source project!
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Before

After

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Create new PR if needed then


Remove var Mgr as return value of Mgr.Restart() in the example

Example was not compiling

@QWERTIOX it appears that due to go module semantics, the package registry was serving an outdated version. I have updated things and it should be all fixed now. Simply use github.com/servusdei2018/shards/v2 in place of github.com/servusdei2018/shards.


Coverage report folder isn't being created on Windows 10 after running tests

Has been fixed by https://github.com/trekhleb/angular-library-seed/commit/a5715987222d047923790ec9e5a104a2251a3a52


Name fields on Participant and LobbyInfo packets now converts to UTF-8

In actual UDP specification there's mention about encoding of "name" field.
It's should be encoded to UTF-8 format, but it's not in project.
Might also be actual for F1 2020 telemetry.

Before

After


When set indicatorSizeMatchesTitle to YES the title color will not change properly

When set indicatorSizeMatchesTitle to YES the title color will not change properly, the selected title will not change to its selected color

Can't reproduce this, any  more info or screenshot would be great

Fixed and pushed to cocoapods 0.4


OnShareCompleteResult : -1006

Hello,
I'm testing out the example on two Quest 2 headsets. Point Cloud Sharing is enabled on both headsets, they're both connected to the same router. When I create an anchor and share it, it does annouce that it was successfully shared to the cloud, the next line says OnShareCompleteResult : -1006, then the Share Anchor button becomes red and the anchor never appears to the other headset.

Thank you for reporting this issue. We are working to improve the return result to include more information on -1006.
You will need to create an app in the Meta Quest Org Manager and associate this app with the sample.
Please complete the following steps:

Create an app on the Meta Quest Org Manager: https://developer.oculus.com/resources/publish-intro/
Copy the App ID (found under "API" tab in App Manager) and add it to the OculusPlatformSettings.asset in the Unity sample.
Request User ID and User Profile permissions (found under "Data Use Checkup" tab in App Manager).


The map is always 0 when i train in my dataset

I used my own dataset to train in ms-dayolo, the data contains only one class. I have changed the classes and filters in ms-dayolo.cfg file.
But the result of map is always 0. For check, i used source domain data to train in original yolov5 and used target domain data to valid. The map is normal, so the labels are fine. And i also used source domain data to replace target data( both of source and target set are use the source domain data), map still 0.
I can't find the wrong, what should i do to solve this problem?

And the loss is also 0

I solved this problem by reconstruct the dataset as show in the data folder

hi,i encountered the same problem,could you tell me how did you solve it? thanks a lot!

Sorry, I didn't solve this problem.
biubiu
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "Mazin-Hnewa/MS-DAYOLO"                                                                                @.>;
发送时间: 2024年9月11日(星期三) 晚上11:06
@.>;
@.>;"State @.>;
主题: Re: [Mazin-Hnewa/MS-DAYOLO] The map is always 0 when i train in my dataset (Issue #14)
hi,i encountered the same problem,could you tell me how did you solve it? thanks a lot!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>


cloudopting-crane test environment

We need to have an environment setup with cloudopting-crane

The crane environment will be created with the new "full platform" test environment


Not able to create a bundle with the inject parameter set to true

I am trying to create bundle with inject parameter set to true.
The main problem is that after running the script i can't see any injected bundle property inside the config.js script, therefore importing a dependency from the generated bundle won't work as expected.
'inject' set to true should inject the bundle into the config.js file, something like this:
bundles: {
    "dist/bundle.js": [
      "script1.js",
      "script2.js"
    ]
  },

The log output is the following:
gulp-jspm: calling jspm.bundle('app/widget/main.js - angular','/var/folders/mx/yj__58p93jv7s8v7n2t8snhw0000gn/T/gulp-jspm__build.js116816-7758-c6d3gt',{"inject":true,"minify":false,"mangle":false,"fileName":"b1"});``
As i can read on the official jspm api, there are only a few options available excluding inject:
https://github.com/jspm/jspm-cli/blob/master/docs/api.md#bundle-options
Is this supposed to work somehow?
Thank you for your suggestion!

Same here, cannot get inject to work. Seems there's currently no gulp plugin supporting inject.

I don't maintain gulp-jspm anymore, see issue #45 - Looking for a maintainer / fork.
Thanks for creating the issue.


Current published version

Hi,
i am currently using 0.0.132.
from powershell gallery it loosk like 0.0.135 is out:
https://www.powershellgallery.com/packages/PSWriteHTML/0.0.135
but when i run "Update-Module -Name PSWriteHTML"
i get a long weird error,
Get-PSGalleryApiAvailability : PowerShell Gallery is currently unavailable.  Please try again later.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\<IP_ADDRESS>\PSModule.psm1:2038 char:13

        Get-PSGalleryApiAvailability -Repository (Get-SourceName  ...

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (:) [Get-PSGalleryApiAvailability], InvalidOperationException
FullyQualifiedErrorId : PowerShellGalleryUnavailable,Get-PSGalleryApiAvailability

WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2'.
PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'PSWriteHTML'. Try Get-PSRepository to see all available registered module repositories.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\<IP_ADDRESS>\PSModule.psm1:2052 char:20

...           $sid = PackageManagement\Install-Package @PSBoundParameters

                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

Thoughts of what can be the problem?

I would say it's related to TLS 1.0 -> https://evotec.xyz/powershellgallery-disables-support-for-tls-1-0-breaking-install-module/
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
install-module powershellget -force -SkipPublisherCheck -Scope CurrentUser -AllowClobber

You're using highly outdated PowerShellGet.

Man you are good!  Many thanks!
I am on Srv2016 due to other tools limitation, and on the default PS version - so you were absolutely right.
thanks a lot!


MetaData API

In the create function of the meta data api there is no description of the options to create custom fields on Standard Objects like Contacts. The first parameter which takes a string says CustomObject but should that change with a standard object?
The code is the example below. Is there a way change this code to work on standard objects?
// creating metadata in array var metadata = [{   fullName: 'TestObject1__c',   label: 'Test Object 1',   pluralLabel: 'Test Object 1',   nameField: {     type: 'Text',     label: 'Test Object Name'   },   deploymentStatus: 'Deployed',   sharingModel: 'ReadWrite' }]; conn.metadata.create('CustomObject', metadata, function(err, results) {   if (err) { console.err(err); }   for (var i=0; i < results.length; i++) {     var result = results[i];     console.log('success ? : ' + result.success);     console.log('fullName : ' + result.fullName);   } });

I have tried and failed to write it this way
var metadata = [{   fullName: 'Contact',   konnectid__MindBodyID__c: {     type: 'Text',     label: 'MindBody ID'   },   deploymentStatus: 'Deployed',   sharingModel: 'ReadWrite' }]; conn.metadata.create('CustomObject', metadata, function(err, results) {   if (err) { console.err(err); }   for (var i=0; i < results.length; i++) {     var result = results[i];     console.log('success ? : ' + result.success);     console.log('fullName : ' + result.fullName);   } });

Did you find a way to create a field on standard objects?

Even though Salesforce named the metadata type "CustomObject" it works identical for both custom and standard objects.
The users of my application have created hundreds of fields using this API.

Make sure you are always passing an array to the metadata
Make sure the fullname is accurate objectName.FieldName
Make sure the data format is correct

You can use the describeSObject API to get examples
OR you can use the tooling query API to query existing CustomField's to get examples (e.x. SELECT Id, Metadata, DeveloperName, ManageableState, FullName, NamespacePrefix FROM CustomField LIMIT 1)

Here is a basic example (using upsert, but it is an identical process):

const fieldMetadata = [
    {
      "fullName": "Account.test_field_for_jsforce_example__c",
      "caseSensitive": false,
      "externalId": true,
      "inlineHelpText": "External ID for migration purposes",
      "label": "test field for jsforce example",
      "length": 255,
      "required": false,
      "trackHistory": false,
      "type": "Text",
      "unique": false
    }
]

conn.metadata.upsert('CustomField', metadata, (err, results) => {
      if (err) {
        console.log(err);
      }
        console.log(results);
    });

Hello Marc, I have to stop, I have toddlers in my home now and I am unable
To finish what I started. This disappoints me and I have to help someone in my family
Mamie
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Marc Höffl<EMAIL_ADDRESS>Sent: Saturday, April 27, 2019 12:45:33 PM
To: jsforce/jsforce
Cc: Subscribed
Subject: Re: [jsforce/jsforce] MetaData API (#819)
Did you find a way to create a field on standard objects?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jsforce/jsforce/issues/819#issuecomment-487306178, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCLYOQUJPAJTR7RLO2BQQLPSSGL3ANCNFSM4FZQF4YA.

No Marc, I have been caring for small children and I have to stop here until I can
Return so sorry and thanks for all the help and assistance.
Mamie
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Marc Höffl<EMAIL_ADDRESS>Sent: Saturday, April 27, 2019 12:45:33 PM
To: jsforce/jsforce
Cc: Subscribed
Subject: Re: [jsforce/jsforce] MetaData API (#819)
Did you find a way to create a field on standard objects?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jsforce/jsforce/issues/819#issuecomment-487306178, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCLYOQUJPAJTR7RLO2BQQLPSSGL3ANCNFSM4FZQF4YA.

Thanks,
I got it working with the CustomField. Just confusingly documented API :)

Hello Marc thank you for your help, sorry I was not able to respond in
Timely manner.
Mamie
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Marc Höffl<EMAIL_ADDRESS>Sent: Wednesday, May 8, 2019 3:23:21 PM
To: jsforce/jsforce
Cc: Mamie Sharrieff; Comment
Subject: Re: [jsforce/jsforce] MetaData API (#819)
Thanks,
I got it working with the CustomField. Just confusingly documented API :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/jsforce/jsforce/issues/819#issuecomment-490636997, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCLYOUMRVBPD6KD2GSX3CLPUMZDTANCNFSM4FZQF4YA.


Configure tests to run automatically on push

Configure the test suites to run automatically in GitHub actions after a push.
Due to the need for database secrets in the '.env' file, this will likely require the use of GitHub action secrets.

Closed in PR #21
Running the workflow on every push was deemed too frequent, so it was changed to whenever a pull request is opened


[ALS-4721] Add named dataset modal and button.

Adds a modal to the data export flow that allows a user to name and save their query/dataset id.
Returns the user to the original modal on complete/cancel.

Fix save button state after changing query parameters.


MatDateRangeInput separator not showing

What are you trying to do?
I am trying to set MatDateRangeInput focus state programmatically via _updateFocus method, and _shouldHideSeparator  return false, this should show the separator, but it is not showing.
What troubleshooting steps have you tried?
The separator is not showing.
Reproduction
Steps to reproduce:

MatDateRangeInput._updateFocus('program')

Environment

Angular:12.0.4
CDK/Material:12.0.4
Browser(s):chrome

Directly via the DOM API, same as you would any other input in your application.


test for metrics targeting LiveView, EKG, Prometheus

there were some issues with metrics not showing up in LiveView. In some cases this has to do with a change in configuration, the metric is not forwarded to LIveViewBK anymore. Or, in other cases, changes to the code were renaming metrics or the tracer context name and thus the metric was not routed correctly to the LiveView backend anymore.
A test for the presence of these metrics :

a special configuration directing all tracers to a log file
then, verify that the metrfics appear with correct names

To test the correct routing of metrics in the configuration:

verify that flags are set: TurnOnLogging and TurnOnLogMetrics
check minimum severity level
verify that tracers are turned on: e.g. TraceBlockFetchDecisions ...
verify that "options: mapBackends: " contains the correct routing to the LiveView backend:

  mapBackends:
    cardano.node.BlockFetchDecision.peers:
      - EKGViewBK
      - kind: UserDefinedBK
        name: LiveViewBackend
    cardano.node.ChainDB.metrics:
      - EKGViewBK
      - kind: UserDefinedBK
        name: LiveViewBackend
    cardano.node.metrics:
      - EKGViewBK
      - kind: UserDefinedBK
        name: LiveViewBackend
    cardano.node.Forge.metrics:
      - EKGViewBK

(the EKGViewBK is for EKG and Prometheus)

we need to track the metrics available through Prometheus from tag to tag.

how many metrics are available with a specific tag
what metrics were add/removed in a specific tag
etc

https://github.com/input-output-hk/cardano-node/issues/2113

in order to have access to Prometheus metrics:

install Prometheus on node
add a port for it in the node config

  "hasPrometheus": [
    "<IP_ADDRESS>",
    12100
  ],

go to http://NODE_IP:12100/metrics and get the list of metrics

metrics are still changing - https://github.com/input-output-hk/cardano-node/issues/2187

https://github.com/input-output-hk/cardano-node-tests/pull/368

https://github.com/input-output-hk/cardano-node-tests/pull/368


Fixed SR-642 Code completion does not instantiate concrete element type of optional Set

Could you add a test?

... and it would be best if the test didn't use Set, but used a mock type instead.  Set can change in future.

I added a test case and added a line break so that the lines are only 80-ish columns. Thanks for the hint with the mock type, wouldn’t have thought about that

Sorry, don't know how these changes happened between my tests and and the commit. Hope everything is fine now ;-)

@swift-ci Please test


Added options to allow IDP to dynamically change values of Name ID and attributes when creating a SAML response.

PR for an issue #87

@mvastola Hi, MIke! Do you have any thoughts on this?

@jphenow is this still being blocked? I can see this being super useful for me down the line :)

@Zogoo did you include this PR in your fork ?

@mjobin-mdsol yeah i already merged into my fork and using my some other repo.

Yea I think this makes sense. Can merge master in and add a note to the README? I believe we have a place where you could describe this option from the controller perspective at least.

@jphenow, I have added a new wiki page for configurations and how to override with options in the "controller".
https://github.com/saml-idp/saml_idp/wiki/IdP_Configuration
And I realized that we already have lots of options never mentioned in the README. So, I would suggest to merge this pull request for now and later we can contribute our documents including name id overriding.
What do you think about it?

Yea I think this makes sense. Can merge master in and add a note to the README? I believe we have a place where you could describe this option from the controller perspective at least.

@jphenow, I have added a new wiki page for configurations and how to override with options in the "controller".
https://github.com/saml-idp/saml_idp/wiki/IdP_Configuration
And I realized that we already have lots of options never mentioned in the README. So, I would suggest to merge this pull request for now and later we can contribute our documents including name id overriding.
What do you think about it?

Yea that makes sense - the comment was more aspirational about not getting further off on the README, but I don't think this really needs to block on those README changes

Yea that makes sense - the comment was more aspirational about not getting further off on the README, but I don't think this really needs to block on those README changes

Sorry, guys. It's been already 2 years since I got the homework to write the instruction in the Wiki to get this merged.
It would be nice if I could have a separate ticket to write the doc as you guys suggested.
I can resolve the conflicts of the files in a timely manner.

Sorry, guys. It's been already 2 years since I got the homework to write the instruction in the Wiki to get this merged.
It would be nice if I could have a separate ticket to write the doc as you guys suggested.
I can resolve the conflicts of the files in a timely manner.

@jphenow, @hamaron I have resolved the conflict for this pull request. Because the conflict came from my branch and it was easier to resolve it by my side. But, could you guys also double check that I didn't do any miss.
And let's merge this pull request as soon as possible.

@jphenow, @hamaron I have resolved the conflict for this pull request. Because the conflict came from my branch and it was easier to resolve it by my side. But, could you guys also double check that I didn't do any miss.
And let's merge this pull request as soon as possible.

v0.14.0 released with this addition.


filter the ocp3

should also filter the OCP3 cluster since the addon was only support to be installed on OCP4+ cluster.

/assign @clyang82


can't open intergrated terminal in dir ,named with chinese words

VSCode Version: Code 1.3.1 (e6b4afa53e9c0f54edef1673de9001e9f0f547ae, 2016-07-12T13:35:06.227Z)
OS Version: Windows_NT ia32 10.0.10586

Steps to Reproduce:
1.open dir named with chinese words, eg: e:\pp\新项目
2.open,vscode in this dir^
3.ctrl+~

Duplicate of #7727


prettify_tablestring(data): messes column parsing if first variable value  has spaces

eg from stata:
acro table  year survivor

This may be one solution - final answer changes spaces in variable values to underscores before sending it to prettify
https://stackoverflow.com/questions/59054403/pandas-dataframe-to-string-with-separator
would need to generalise this line:
df['Country']=df['Country'].str.replace(' ','_')
fro their example into something that looped over the column names

like for col in data.columns:


New version: StochasticPrograms v0.2.0

Registering package: StochasticPrograms
Repository: https://github.com/martinbiel/StochasticPrograms.jl
Created by: @martinbiel
Version: v0.2.0
Commit: fb3983bdefe84a300f5b7e3c4c059907020f5c40
Reviewed by: @martinbiel
Reference: https://github.com/martinbiel/StochasticPrograms.jl/commit/fb3983bdefe84a300f5b7e3c4c059907020f5c40#commitcomment-33823917

Please add
[compat]
julia = "1"

to your project file and retrigger the bot.


address comments from prior PR

Signed-off-by: Jim Bugwadia<EMAIL_ADDRESS>

@yuji-watanabe-jp - I tried to address prior comments from here:
https://github.com/kyverno/KDP/pull/15
Please review. Thanks!


Add better logging and tests to Bind method and simplify Bind err cleanup

Changes proposed in this pull request:

Previously, one defer with if statements cleaned up resources that were created before the method returned an error. This has been split into three defers which are stacked procedure executes, and each of which has better logging.
Also, fix a small bug on broker.go:365, in which an error could be sent to the channel twice.
Refactored part of the test mocks to a more general structure for use with the new tests. Previously, the mocks were more tailor-written to TestUnbind.

Things to check

For any logging statements, is there any chance that they could be logging sensitive data?
Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

Security considerations
I checked the newly logged structs and they do not contain credentials. They are using the appropriate log level.

maybe out-of-scope:
some of these logs are using a dotted notation (i.logger.Error("create-user.aws-iam-error", err)) to indicate scope (I think) and some are using a more free-form (I think) style b.logger.Error("bind: defer: error deleting user", derr, ...)
are either of these formats consumed/interpreted by other stuff? or are these just for people?

@bengerman13 Good question. Errors printed to the logger are only used by us. Errors returned by functions could reach users. The colon approach is more conventional for Go programs, but this project uses the dot approach more frequently. It looks like all of the error strings added here are only logged, not returned, so we should be ok. Let me know what you think.

yeah, if these are for operators, the mix/match seems fine to me :+1:


Fishing message should correspond to the tool being used

A good way to do this would be to associate the correct message with every tool instance, then apply that message here.

Can you give me an example message that should be associated with a tool?

For example..
You cast out your net... for nets
You cast out your line for rods
There are some others, but you get the idea


VM_IF and VM_IF_CONST dont do what vm.i says they do

vm.i says for VM_IF and VM_IF_CONST that @param N is the "Number of values to be removed from the stack if the result is true."
but looking at the code you can see that the stack pointer is reduced regardless of if the statement was true or not.
void vm_if_const(SCRIPT_CTX * THIS, UBYTE condition, INT16 idxA, INT16 B, UBYTE * pc, UBYTE n) OLDCALL BANKED {
    INT16 A;
    if (idxA < 0) A = *(THIS->stack_ptr + idxA); else A = script_memory[idxA];
    UBYTE res = FALSE;
    switch (condition) {
        case VM_OP_EQ: res = (A == B); break;
        case VM_OP_LT: res = (A <  B); break;
        case VM_OP_LE: res = (A <= B); break;
        case VM_OP_GT: res = (A >  B); break;
        case VM_OP_GE: res = (A >= B); break;
        case VM_OP_NE: res = (A != B); break;
    }
    if (res) THIS->PC = pc;      //// THESE TWO LINES ARE THE ISSUE
    if (n) THIS->stack_ptr -= n; ////
}

putting the second if statement if (n) into the first one would fix this.

Hi @DavidMeagher1 thanks for spotting this, I've checked with the dev who wrote that code and it's just a case of the documentation being incorrect. The engine code is stored in a different repo, so I'll update the docs there to correct this. Thanks

I've fixed this now in
GBVM: https://github.com/chrismaltby/gbvm/commit/4dc5117660d100f92b4ede0a386e774a38d46e3e
which I have scripts to auto update
GB Studio: https://github.com/chrismaltby/gb-studio/commit/483074e5d5099678e6ef8ea34d1481618c068438
GB Studio Docs: https://github.com/chrismaltby/gb-studio-docs/commit/f3a4032fb92e1591bc55d6283217bc0f789c1e26
The docs site is on a new branch which won't go live until GB Studio 4 launches officially


Projects page: Allow multiple filters to be “active” at one time(eg ‘tech’, ‘stages’, ‘events’, ‘topics’). Show those filters on the screen to the user.

The projects page currently can only be viewed by one tag, stage, etc at a time. A member may, though, be looking for a combination of tags, or may be interested in more than one stage.
For example: "I want to find javascript projects that are not drifting or hibernating."

This would also set the stage for filtering projects out from default views that are "dead" in some respect (vaguely defined, never went anywhere, etc) but that we don't actually want to delete.

https://codeforphilly.org/projects

@rmcmillen50 How about adding a tiny plus on each filter, with a hover bubble saying 'Combine Filter'?

Yes, and...... Ideally we show something similar to say, LinkedIn or any job search site, where the user sees all the active filters in play. Let me see if I can attach this screenshot mockup I just made!

so @aharley40, I added the "plus signs" you mentioned (well, that i think you meant :) ) on the left hand side. Then I suggest we add a horizontal section above the list of projects that shows what active filters are being used. You mentioned the "combine filters" idea.... I think we should just combine filters by default if I user clicks multiple. Then, the visual X's on each active filter would give people the ability to remove the filter if they wish. thoughts?

Good Idea. I'll add a bubble to the top displaying the currently used tags. I could only include the deletion x's if we use the combine filter idea. Currently, clicking a filter causes a page refresh, and, I don't think the user will expect it to combine unless explicitly told. I think it'd be easier on the user to display help bubbles as they hover over the icons to add or delete the filter from the list.

well - to be clear - I think the most ideal experience is async project results updating when a user selects additional filters to their "query". So page doesn't refresh, just the project results section. The platform would be essentially assuming each additional tag is adding a new WHERE  (AND) clause condition to the SQL.


Getting versions from iojs and nodejs

I did some changes in scraper.js.
Now you can get all node versions from nodejs.org and  iojs.io
First time doing some open source contribution so if is rude to open a PR like this please tell me how I can help.

Hi, this seems great. Hopefully will keep the guys asking about IO.js happy


chore(GroupTheory): reformat deprecation dates

Try to have the date on the same line as the attribute: this makes it easier to rewrite these into machine-readable form.
One date is was added: the deprecation was in the same PR as nearby lemmas.

Thanks! :tada:
bors merge


iqra

iqra university

@junaidkhan90 Please rename lib/domains/pk/edu/iqra to lib/domains/pk/edu/iqra.txt

@junaidkhan90 Pull request merged. I renamed the file for you.


When calling /api/races/driver_data/{driver_name}, getting back some empty string lap_numbers

When I call /api/races/driver_data/{driver_name}, I'm sometimes getting back radios with an empty string as the lap_number, as well as a "NaT" lap_date_start.
Since lap_avg_sentiment contains the average sentiment for every lap that means I'm also getting a lap sentiment for this empty string lap. See example attached.
leclerc_2023_canada.json

In _set_radio_lap_number we use pandas.merge_as_of, and unfortunately if there is no nearest timestamp that is nearest, it will fill in an NaT for the lap timestamp and an empty string for the lap number.
We use the default backward for the direction param:

A “backward” search selects the last row in the right DataFrame whose ‘on’ key is less than or equal to the left’s key.

Response after the changes:
response_1733261418281.json


Fix to-dns network policy in garden namespace for node-local-dns if non-ip based policy engine is used.

How to categorize this PR?

/area networking
/kind enhancement
What this PR does / why we need it:
Fix to-dns network policy in garden namespace for node-local-dns if non-ip based policy engine is used.
Network policies are enforced by different means depending on the CNI. Some rely
on IPs, others work mostly on pod identities and ignore IPs mostly. (Calico falls
into the first category. Cilium is an example for the second category.)
To allow Seeds to run in both environments even with node-local-dns being enabled
the to-dns network policy must allow connections to the pod and its IP. The former
was missing here.
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
There is an analogous to-dns network policy in the shoot's kube-system namespace, which already included this block. The network policy is differently structured, though.
Release note:

Operation of a seed using cilium as networking provider and node-local-dns is now working.

Tested on a seed with node-local-dns enabled and cilium. Without this fix the kube-state-metrics pod was stuck in a crashloop backoff, applying the PR resolved the issue. I guess this is the expected behaviour.
/lgtm
/cc @DockToFuture

Tested on a seed with node-local-dns enabled and cilium. Without this fix the kube-state-metrics pod was stuck in a crashloop backoff, applying the PR resolved the issue. I guess this is the expected behaviour.

Yes, this is one of the visible results.
I hope that we do not need to wait for a review of @DockToFuture as this might take another month due to parental leave.


Bump to version 3.10.0

Codecov Report

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

@@           Coverage Diff           @@
##           master     #542   +/-   ##
=======================================
  Coverage   67.56%   67.56%
=======================================
  Files          14       14
  Lines         407      407
  Branches       44       44
=======================================
  Hits          275      275
  Misses        118      118
  Partials       14       14

Continue to review full report at Codecov.

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

@jrief :+1:


feat: i16 types

Required Functionality
Currently Synth allows me to generate data for int4 and int8 Postgres types using the i32 and i64 generator. However, it is not possible to generate data for a int2 Postgres type.
This is because Postgres requires bytes lengths to match exactly. Hence the i32 and i64 generator cannot be used.
Proposed Solution
Adding an i16 type to Synth will allow me to fill an int2 Postgres field.
Use case
Filling int2 Postgres fields

#405 is merged


zombienet: detect required binaries

Printing suggestions on how to fix those.

Current dependencies on/for this PR:

main

PR #194   👈

This stack of pull requests is managed by Graphite.


Simulating with trained models

I've started investigating whether it's possible to run stable MD simulations using models trained on SPICE.  I'm opening this issue as a place to describe my results and discuss approaches.
As a starting point, I tried running simulations with the most accurate of the five models described in the paper.  As part of the analysis, I had sorted every molecule in the dataset by MAE across all its samples.  Intuitively, I would expect that molecules with low error would be more likely to be stable than ones with high error.  So I took the sorted list of molecules and chose 21 that were evenly spaced over the first third of the list.  This gives us an assortment of molecules that cover a range of MAE, but all of them are ones on which the model is at least reasonably accurate.
For each molecule, I had OpenFF-Toolkit generate a conformation with generate_conformers().  This gives us a conformation that isn't energy minimized but should be generally reasonable.  I used the model to compute the potential energy and mean force magnitude (over all atoms).  If the mean force was less than 2000 kJ/mol/nm, I attempted to run a short MD simulation (5 ps at 300K with a time step of 0.5 fs) and recorded whether it was stable.  I considered a simulation to be stable if at the end, the potential energy was negative and the mean force magnitude was less than 5000 kJ/mol/nm.  That isn't a very stringent test, but it's good enough to detect most cases where the simulation is obviously unstable.
Next I went back to the conformation generated by OpenFF-Toolkit, performed an energy minimization, and repeated the process again: compute the energy and mean force, and attempt a simulation if the mean force is less than 2000 kJ/mol/nm.
Here are the results.  All energies are in kJ/mol, and all forces are in kJ/mol/nm.

SMILES
MAE
Initial Energy
Initial Force
Initial Stable
Minimized Energy
Minimized Force
Minimized Stable

O.[Br-]
0.52
-697.07
174.04
Yes
-1098.26
4.70
Yes

CF.O
1.16
-2137.35
379.27
Yes
-3016.61
6.78
Yes

CF.c1c[nH+]c[nH]1
1.44
-3444.68
1385.62
No
-51228.83
295.14
No

CNC(C)=O.O
1.66
-3919.71
2905.47

-27933.60
197892.18

C1COCOC1.c1ccccc1
1.83
-1597.14
13229.65

-200872.56
238.82
No

CCSc1c(Cl)c(Cl)nc(Cl)c1Cl
2.00
-10025.96
6219.34

-91788.04
101.68
Yes

BrCCBr.C=C
2.19
-3509.03
1497.34
Yes
-8341.84
185.78
Yes

Brc1nc(Br)c2[nH]cnc2n1
2.36
-2326.06
1118.34
Yes
-5735.17
5314.33

COC=O.c1c[nH]cn1
2.53
-4924.22
4972.37

-37282.98
49163.46

FCF.Oc1ccccc1
2.69
-5243.82
1844.34
Yes
-17793.25
3832.58

CC(C)=O.CI
2.85
-2624.62
2091.93

-9437.92
9966.54

CC1(C)Oc2cc(C(=O)c3ccncc3F)cc(O)c2[C@@H]2CC@HCC[C@H]21
3.00
67250.36
976154.64

-37277040.00
75624193.94

NS(=O)(=O)Oc1ccc2c(c1)OCC=C2
3.14
7196.77
34369.72

-120631.40
1771573.72

CC(C)=O.CC(N)=O
3.28
-3794.45
2386.33

-13649.93
103504.58

CC(I)I
3.41
-2027.48
400.34
Yes
-2574.42
3.05
Yes

CNC(N)=[NH2+].[F-]
3.52
-2136.38
6432.99

-7764.10
15876.81

CC1(O)CCC(C(C)(O)C(=O)O)C(=O)C1
3.63
2083.24
27395.65

-275149.12
6261686.46

c1ccc2c(C[n+]3csc4ccccc43)cccc2c1
3.73
144824.92
277838.14

-9574604.00
45962222.49

O=C([O-])C12CCC(CC1)[NH2+]2
3.83
-2885.28
5103.62

-66048.79
692112.47

CNC(=O)C@HNC(=O)C@@HNC(C)=O
3.93
109911.96
203436.32

-34306652.00
40925424.19

CCCCS(=O)(=O)c1sc2nc3c(cc2c1N)CCCC3
4.02
516.54
172413.99

-9241010.00
14776114.24

Some observations:

There exist molecules for which it's able to run a stable simulation, at least for 5 ps.  So it's a start!
When the initial force magnitude is low enough for simulating to be reasonable, the simulation usually but not always is stable.
For the majority of molecules, the energy minimizer manages to get into a region where the model is clearly inaccurate, the energy decreases drastically, and the minimizer gives up.  Pay especial attention to the Minimized Force column.  The minimizer used a tolerance of 10 kJ/mol/nm, so if everything worked correctly the value should be less than that.  In fact it only managed to do that in 3 of 21 cases.  There were a few others where it at least managed to get the force down into a reasonable range before giving up.  But in the majority of cases, the force is larger after minimization than before.
As expected, minimization and simulation tend to work better on the molecules with lower MAE on the dataset, but there are exceptions.

I analyzed the cases where the optimizer led to huge forces.  In every case, it did it by putting two atoms directly on top of each other (distance between them on the order of 1e-5 nm or less).  It's not surprising the model would have no idea what to do in that case, since there's no training data with atoms right on top of each other.  You would hope there would be enough of a barrier to keep them from getting too close, but L-BFGS works through line minimizations that are pretty good at jumping over barriers.
A possible solution would be to add an explicit repulsion term to the model.  For example, SpookyNet includes a ZBL potential as a prior to ensure physically realistic behavior at short distances.  That seems like a good thing to try.

Starting with a physically motivated "prior" potential and forcing the ML model to learn the difference sounds like a good approach if the domain of desired application matches the domain over which the model is reasonable.
The SpookyNet paper describes the ZBL potential as:

It would appear that this should describe a domain including both bonded and noncovalent interactions, which is useful to us.
I am still very much hoping we can eliminate the need for formal charges from our model, since it vastly complicates things by making the model dependent on a specific cheminformatics model and drastically limits its domain of applicability. Since @raimis has achieved equivalent performance without the need for these charges, can we first push the model as far as we can without the need for charges while including something like ZBL to eliminate regions outside out training domain?
One other note about our domain of applicability: Since we used thermalized samples from an MM potential, we effectively excluded anything in the high-energy region of the MM model---as well as snapshots near minima---from our domain of applicability (though some small amount of extrapolation is expected from this region since we use QM forces even though we constrain to MM positions).
@peastman : Do you know if our QM-generated dataset ended up including snapshots with gradients that were close to a minimum? If not, and we want users to be able to minimize these structures, why don't we add some OptimizationDatasets for some subsets, so that we also include data in the vicinity of minima?

Do you know if our QM-generated dataset ended up including snapshots with gradients that were close to a minimum?

Nearly half the data in the dataset was for low energy conformations close to local minima.  See the paper for a descriptions of how it was generated.

Ah, yes---low energy with respect to MM. (I had forgotten about that!)
Were you able to verify the QM force magnitudes were also low for these conformations? I realize a test of the hypothesis that minimized MM conformations were also close to being QM minima (or at least low-force snapshots) would have been a good addition to the manuscript.

I've been training models with a variety of physical priors.  Here's what I've tried so far, and what effect each one has.
ZBL repulsive potential
This models the screened Coulomb repulsion between nuclei at short distances.  Adding it had no significant effect on the accuracy of fitting data.  A model including it came in right in the middle of the five models I had trained before.  But it has a huge effect on stability.  I tested the same 21 molecules as before, and this time it successfully minimized and simulated 17 of them (compared to five before).  That's only for 1000 steps, so it's not the most rigorous test, but it's still a huge improvement.
D2 dispersion correction
Including this maybe helped accuracy a little bit?  I trained two models including it.  Both of them ended up with better than average accuracy for the previous five models, but not as good as the best of them.  If it does help, the benefit is smaller than the variation between models.
Coulomb interaction
I implemented a Coulomb interaction between atoms, scaled by erf(alpha*r) to reduce the effect at short distances.  I haven't yet implemented any way for the model to predict charges, so this was limited to fixed, pre-assigned partial charges.  I tried two different sets of charges: formal charges, which give only a very approximate picture of how charge is distributed in the molecule, and MMFF94 charges, which give a more realistic distribution while still being conformation-independent and fast to compute.
Both made the model worse.  Formal charges only hurt accuracy a little bit.  MMFF94 charges hurt it more.

Thanks for the reports!
Can you link to the implementations of these models in a PR somewhere?
An important consideration is to keep the potential free from singularities and ensure C2 continuity. Are we careful to select priors with both properties? (The energy can be large at r=0, but singularities cause significant problems for many sampling strategies and alchemical methods. C2 continuity is required for molecular dynamics integrators to provide some guarantee of accuracy.)
In terms of other potential physical priors I've seen used, this paper uses GFN2-xTB as a reference model, with the ML model predicting the difference between reference and QM (delta-learning). While it would take a good amount of effort to implement GFN2-xTB, the xtb Python package would make it straightforward to precompute the GFN2-xTB contributions for each snapshot and assess how well this method would work for accuracy; dynamics simulation would be more difficult to check.
For charges, I still really like the Behler charge model that provides a way to treat both polarization and charge transfer. Would it be possible to try something like this without too much added complexity?

All implementations are in TorchMD-Net (though the PR with the Coulomb implementation hasn't been merged yet).  The dispersion and Coulomb priors are both free from singularities.  As we've discussed several times already, the repulsion prior is singular at r=0 because that's an accurate description of the physical system.  The repulsion between two atoms really does go to infinity as they approach each other.

the repulsion prior is singular at r=0 because that's an accurate description of the physical system.

These models are not trained on any data close to r=0 and are not at all intended to or capable of modeling the correct energetics near r=0. There is no reason they need to be singular at r=0, since this regime is far from the regime in which these models are valid or accurate. Unmodified simulations will not visit this regime, but enhanced sampling techniques and alchemical modifications will certainly visit these regimes, where complicated and inconvenient modifications would be needed if the potential is singular at r=0. My point is that this can be avoided by simply using a functional form free of singularities to model this region that is outside the domain of applicability of our model.

There are a number of models of that sort, that start with a semi-empirical method and train a neural network to make it more accurate. Those models are quite interesting, but they're useful for different applications. Even the fastest semi-empirical models are far slower than the sorts of ML models I've been looking at. They aren't practical for MD simulations of the sort we want to run. Think of them as a faster alternative to DFT instead of a more accurate alternative to force fields.

There are a number of models of that sort, that start with a semi-empirical method and train a neural network to make it more accurate. Those models are quite interesting, but they're useful for different applications. Even the fastest semi-empirical models are far slower than the sorts of ML models I've been looking at. They aren't practical for MD simulations of the sort we want to run. Think of them as a faster alternative to DFT instead of a more accurate alternative to force fields.

Is the main issue the energy computation by variational optimization or dominant eigenvalue computation, or the integral computations? I keep wondering if ultra-simple models---like extended Hückel models with distance-dependent matrix elements---might be sufficient for our purposes in a physical reference potential.

These models are not trained on any data close to r=0

That's the reason for using a physical prior.  The ZBL potential was parametrized based on scattering data for a variety of elements.  It gives an excellent match to experiment down to very short distances.

My point is that this can be avoided by simply using a functional form free of singularities to model this region that is outside the domain of applicability of our model.

You can of course create a soft-core version of any potential, if that's required for a particular application.  Right now my goal is to create the most physically accurate model I can, including behaving physically at short distances.

Is the main issue the energy computation by variational optimization or dominant eigenvalue computation, or the integral computations?

No idea.  I've never worked on an implementation of a semi-empirical method.

It gives an excellent match to experiment down to very short distances.

I might have missed this in my reading, but the ZBL model in TorchMDNet contains an implementation of an approximation fit sometime prior to 1982 to calculations using the pre-1977 free-electron method of interatomic potentials that is itself an approximation to earlier multiconfiguration self-consistent field quantum chemical methods. That doesn't mean it isn't useful, but its accuracy in that regime cannot simply be assumed.

You can of course create a soft-core version of any potential, if that's required for a particular application. Right now my goal is to create the most physically accurate model I can, including behaving physically at short distances.

Let's align on the domain of applicability and intended applications at our next in-person meeting. I have a feeling we've diverged here, and would like to better understand the range of applications you are envisioning where accurate energetic behavior near r=0 will be meaningful and how you're intending to validate the behavior for those applications.
It's critical to remember that these are all models, and the important thing about models is how useful and predictive they are in the domains and applications of interest.

No idea. I've never worked on an implementation of a semi-empirical method.

There's a brief description of the Extended Hückel Method (EHM) in this paper by Oles Isayev, though they do the opposite of what we're considering: Use ML to predict the parameters for the EHM Hamiltonian matrix, and then diagonalize to get orbital energies.

That doesn't mean it isn't useful, but its accuracy in that regime cannot simply be assumed.

Here is something we can say with complete confidence: any potential that doesn't diverge as r approaches zero is not physically accurate.  Actually, the physics in that limit is exceptionally simple.  The electrons no longer provide any meaningful screening, so it's just the Coulomb repulsion between the bare nuclei.  Any interaction that does something different in that limit is unphysical.

There's a brief description of the Extended Hückel Method (EHM) in this paper by Oles Isayev,

There have been several models of that sort published.  See also
https://aip.scitation.org/doi/10.1063/5.0021955
https://www.pnas.org/doi/full/10.1073/pnas.2120333119

Here is something we can say with complete confidence: any potential that doesn't diverge as r approaches zero is not physically accurate. Actually, the physics in that limit is exceptionally simple. The electrons no longer provide any meaningful screening, so it's just the Coulomb repulsion between the bare nuclei. Any interaction that does something different in that limit is unphysical.

Except nuclei fuse, and doing so releases a large quantity of energy, rather than consumes infinite energy as you suggest. This model breaks down in describing what happens when you actually put two nuclei on top of each other. It simply isn't meant to describe that regime.
Fortunately, none of our application domains or use cases requires we accurately describe what happens near r=0, as I previously noted. We are in the business of making useful models for biomolecular modeling and simulation and drug discovery.
It certainly is a good step forward to incorporate a physical model that better describes asymptotic behavior (though we should allow the parameters to be fit as well). But the point is that we should be favoring utility in our domains and use cases of interest over accuracy or asymptotic behavior in domains far outside our domain of applicability and use cases.

Yeah, I'm not worried about simulating nuclear fusion. :)  We can leave the strong force out of our models.  It will still be accurate down to displacements of about $10^{-6}$ nm.
Like I said before, once you create a physically accurate model it's easy to modify it to make a soft core version.  For example, replace $\frac{1}{r}$ by $\frac{1}{r+\epsilon}$, and you're free to pick whatever value of $\epsilon$ is best for your application.  Or multiply by $\mathrm{erf}(\alpha r)$ where $\alpha$ sets the length over which it's softened.  But if you start by creating a soft-core version, it's harder to go the other way.

I've been running some experiments using delta learning with a semi-empirical reference.  I compute the forces and energies with GFN2-xTB, then train an ET model on the difference between that and DFT.  This makes the residual forces and energies much smaller, and training goes a lot faster.  But the final model consistently ends up being a worse fit than what we get directly learning the DFT data.
Here's another interesting model based on a semi-empirical method: https://arxiv.org/abs/2210.11682.  It uses DFTB, representing the interaction functions as splines that are learned from data.  The lead author is now in Tom's group.  From discussions with him, it's not quite ready to use yet (it only supports H, C, N, and O), but it will hopefully get there soon.

I've always wondered if an absolutely minimal semiempirical method like NDDO or MNDO could be sufficient. I know these methods require some integrals, but they seem feasible to speed up. Ther are a number of semiempirical methods implemented within scine sparrow, for example.
I'm not sure if I understand DFTB well enough to know if it is a suitable approach for a reference potential.

https://github.com/lanl/PYSEQM has a PyTorch implementation of MNDO.  Also AM1 and PM3.

But the final model consistently ends up being a worse fit than what we get directly learning the DFT data.

Do you use any descriptors calculated at the GFN2 level as input to the model as well, Orbnet Denali seems to be a good model which uses this method and works for charged molecules, it might be good to compare with what they report in the paper.

No, it was just doing straightforward delta learning.  It was mostly just a proof of concept to see what would happen.  Using descriptors from GFN as inputs to the model would be more complicated, because we would need to be able to compute gradients of those descriptors.


when I come into detail Vc from tableView,and then back the tableView,the image reload once again,but before I came into the detail page ,the table cell image should be cached already.hope your reply

please provide sample code. Can you reproduce it on the demo project?

I am sorry,the project is bigger,and I think I can describe it clearly.the problem is that ,I have a tableView ,and the cell has an image ,then set the image .
[mainImgView sd_setImageWithURL:[NSURL URLWithString:dict[@"poster_img"]]placeholderImage:[UIImage imageNamed:@"pic"]];
I scroll to the bottom ,(the table has about 50 rows ,that is to say it has 50 pics)
then  i select one row ,and then jump to the detail page,but when I back to the tableView ,I scroll to the top slowly,the pic in the row request from the web again. hope your help.
@mythodeia

can you replicate this issue in the demo project?

I will make a demo only for  that ,could you leave your email for me ?
@mythodeia

i think it would be easier to test the demo project. if the demo project works then there must be something wrong with your code. if you still cannot find it then you can post a sample demo project here so everyone can have a look and provide assistance

ok,wait a moment

I am very sorry for that ,I find the problem,some people in my team clear the image data,and not tell me .thank you for your help.@mythodeia


app.panel.disableSwipe throwing error

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 2.2.5

Platform and Target: Cordova

What you did
In previous parts of my code i am enabling the right panel swipe option. app.panel.enableSwipe('right');
Later in my code after i am done with the right panel i want to disable the right panel swipe action. app.panel.disableSwipe('right');
Expected Behavior
I expect the system to disable the swipe action without issue.
Actual Behavior
A js error is thrown in the console and it then locks up the rest of my application.
Uncaught TypeError: panels.forEach is not a function     at Object.disableSwipe (framework7.js:14811)     at Framework7.<anonymous> (my-app.js:273)     at framework7.js:3047     at Array.forEach (<anonymous>)     at framework7.js:3046     at Array.forEach (<anonymous>)     at Framework7.emit (framework7.js:3040)     at framework7.js:3053     at Array.forEach (<anonymous>)     at View.emit (framework7.js:3052)

Fixed by #2380


added new command

closes #118
here is an example of creating a new c slight project and running it:

here is an example of creating a new rust slight project and running it:

Signed-off-by: Dan Chiarlone<EMAIL_ADDRESS>

Does this work in Win?

Does this work in Win?

@Mossaka ~ Yes! I've tested it on Windows and it works fine. Although, I'll probably have to adapt the bindings rule 'cause of chmod.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2209 ms

Resolved: Bofrost.at performance has improved in 2351d7a.


Update Redis Cache advanced settings to reference TLS options #13912

Added note referencing minimum TLS version setting in Advanced Settings blade
Updated screenshot to show setting, which was added after the previous screenshot were last updated

Fixes #13912

@BernieWhite @wesmc7777 Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
We'll close this PR. Thank you


Added Sort Ago

@itzaayush I think you may have mistaken the name of the project for a wiki of sorting algorithms. This project is an implementation of a sorting algorithm dubbed "Wikisort". It's not a collection of demos of sorting algorithms! :-)

Thanks for the assist @timmyjose, yeah this is just a poorly named sorting algorithm rather than a collection of user-submitted sorting algorithms. Cheers!


[2/x] feat: add workaround for wasm memory.grow op translation

This PR is stacked onto #193 PR and should be merged after that

@bitwalker I updated the expected tests and this PR is ready for review and merge along with #193

Looks like this will have to be rebased as well. Sorry about that, I think this is due to me force pushing changes to my treeify PR, but you had based your branches on the initial version, so now the whole stack is messed up, my bad :(

No worries!


[Bug] I get this when running just patch-gmod

Here is the log, explains it all
just patch-gmod
--2023-09-25 16:32:08--  https://github.com/solsticegamestudios/GModCEFCodecFix/releases/download/20230731/GModCEFCodecFix-Linux
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/192249688/6475ebc7-8366-4a14-88d8-ee5805b3b478?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230925%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230925T213208Z&X-Amz-Expires=300&X-Amz-Signature=36e7d37d7e207324edffa829acf3a6cd0a624b0aaf9d1be6c830d281963a3d1e&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=192249688&response-content-disposition=attachment%3B%20filename%3DGModCEFCodecFix-Linux&response-content-type=application%2Foctet-stream [following]
--2023-09-25 16:32:09--  https://objects.githubusercontent.com/github-production-release-asset-2e65be/192249688/6475ebc7-8366-4a14-88d8-ee5805b3b478?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230925%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230925T213208Z&X-Amz-Expires=300&X-Amz-Signature=36e7d37d7e207324edffa829acf3a6cd0a624b0aaf9d1be6c830d281963a3d1e&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=192249688&response-content-disposition=attachment%3B%20filename%3DGModCEFCodecFix-Linux&response-content-type=application%2Foctet-stream
Resolving objects.githubusercontent.com (objects.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22128672 (21M) [application/octet-stream]
Saving to: ‘/tmp/patch-gmod/GModCEFCodecFix-Linux/GModCEFCodecFix-Linux’

GModCEFCodecFix-Linux                          100%[===================================================================================================>]  21.10M  1.98MB/s    in 12s

2023-09-25 16:32:22 (1.72 MB/s) - ‘/tmp/patch-gmod/GModCEFCodecFix-Linux/GModCEFCodecFix-Linux’ saved [22128672/22128672]

/tmp/justpgDGny/patch-gmod: line 358: /tmp/patch-gmod/GModCEFCodecFix-Linux: Is a directory

Fixed in latest version


[SC] Fix local call message value zero

See https://github.com/stratisproject/StratisFullNode/pull/662#issuecomment-902379004

@rowandh I believe this fix was merged to release/<IP_ADDRESS>... can you confirm? If so it was also then merge to 1.2 already.

@fassadlr looks like the fix is in but not the tests, so we should still merge this.


Not retrieving URL from browser

I noticed on the example script 'Examples/Example7_Page_URL_From_Hover.ahk', the url is retrieved correctly on my main computer, but not on most computers I have tested, in those others it simply returns null on oEl.value, no matter which browser is used.
Can you please fix it or help me to get a workaround to work on all devices? Thanks.

Interesting, I've tested in all my Chromium-based apps (Chrome, Edge, Discord, Notion, VSCode) and it works as expected.
Could you try changing the line oEl := oAcc.Normalize({RoleText:"document", not:{Value:""}}) to oEl := oAcc.Normalize({Role:15, not:{Value:""}}) to see whether it makes a difference?

Interesting, I've tested in all my Chromium-based apps (Chrome, Edge, Discord, Notion, VSCode) and it works as expected.
Could you try changing the line oEl := oAcc.Normalize({RoleText:"document", not:{Value:""}}) to oEl := oAcc.Normalize({Role:15, not:{Value:""}}) to see whether it makes a difference?

Thanks, this works! Can you please explain why?
Also, that workaround noticed it isn't working when using the following way:
oAcc := Acc.ElementFromChromium("ahk_id " hwnd) instead of oAcc := Acc.ElementFromPoint(), I was using it that way in my custom script before, is there a way to make it work for this other method as well?

It stemmed from the fact that I assumed RoleText will be in English, but I'm guessing that if your computer is set up in a different language then RoleText is also in that language. The role number however stays the same.
What exactly are you trying to achieve? I tested replacing oAcc := Acc.ElementFromPoint() with try MouseGetPos(,, &hwnd), oAcc := Acc.ElementFromChromium("ahk_id " hwnd) and it worked as expected (it doesn't work in Firefox because it isn't a Chromium app).

Ah, that makes total sense now.
I don't remember why I noticed something that made me thought it wasn't working with oAcc := Acc.ElementFromChromium("ahk_id " hwnd), (I'm pretty sure it wasn't Firefox related) but I did the tests again and it is working.
So, I'm mainly using oAcc := Acc.ElementFromChromium("ahk_id " hwnd) because I noticed this way it works even when the cursor is not on the viewport/page area, (I need it to work no matter where the cursor is pointing), as for example when using oAcc := Acc.ElementFromPoint() it doesn't work if the cursor is pointing on the browser tabs section or somewhere else outside the browser window.
Now I need to implement a workaround to make it work that way on Firefox as well. No matter where the cursor is pointing, detect the url as long as the window is on top (as for example when navigating through tabs via keyboard, Ctrl + 1, Ctrl + 2).
Can you please help me to implement something to make it work like that on Firefox? Thanks..

Try this modified GetUrl function from the GetUrl() gist:
#Requires AutoHotkey v2.0

; Version: 2<IP_ADDRESS>
; https://gist.github.com/7cce378c9dfdaf733cb3ca6df345b140

GetUrl(WinTitle?, WinText?, ExcludeTitle?, ExcludeText?) {
    static S_OK := 0, TreeScope_Descendants := 4, UIA_ControlTypePropertyId := 30003, UIA_DocumentControlTypeId := 50030, UIA_EditControlTypeId := 50004, UIA_ValueValuePropertyId := 30045
    if !(hWnd := WinExist(WinTitle?, WinText?, ExcludeTitle?, ExcludeText?))
        throw TargetError("Target window not found")
    IUIAutomation := ComObject("{FF48DBA4-60EF-4201-AA87-54103EEF594E}", "{30CBE57D-D9D0-452A-AB13-7AC5AC4825EE}")
    eRoot := ComValue(13, 0)
    HRESULT := ComCall(6, IUIAutomation, "Ptr", hWnd, "Ptr*", eRoot)
    if (HRESULT != S_OK) {
        throw Error("IUIAutomation::ElementFromHandle()", -1, HRESULT)
    }
    winClass := WinGetClass("A")
    ctrlTypeId := (winClass ~= "Chrome" ? UIA_DocumentControlTypeId : UIA_EditControlTypeId)
    value := Buffer(8 + 2 * A_PtrSize, 0)
    NumPut("UShort", 3, value, 0)
    NumPut("Ptr", ctrlTypeId, value, 8)
    condition := ComValue(13, 0)
    if (A_PtrSize = 8) {
        HRESULT := ComCall(23, IUIAutomation, "UInt", UIA_ControlTypePropertyId, "Ptr", value, "Ptr*", condition)
    } else {
        HRESULT := ComCall(23, IUIAutomation, "UInt", UIA_ControlTypePropertyId, "UInt64", NumGet(value, 0, "UInt64"), "UInt64", NumGet(value, 8, "UInt64"), "Ptr*", condition)
    }
    if (HRESULT != S_OK) {
        throw Error("IUIAutomation::CreatePropertyCondition()", -1, HRESULT)
    }
    eFirst := ComValue(13, 0)
    HRESULT := ComCall(5, eRoot, "UInt", TreeScope_Descendants, "Ptr", condition, "Ptr*", eFirst)
    if (HRESULT != S_OK) {
        throw Error("IUIAutomationElement::GetRootElement()", -1, HRESULT)
    }
    propertyValue := Buffer(8 + 2 * A_PtrSize)
    HRESULT := ComCall(10, eFirst, "UInt", UIA_ValueValuePropertyId, "Ptr", propertyValue)
    if (HRESULT != S_OK) {
        throw Error("IUIAutomationElement::GetCurrentPropertyValue()", -1, HRESULT)
    }
    ObjRelease(eFirst.Ptr)
    ObjRelease(eRoot.Ptr)
    try {
        pProperty := NumGet(propertyValue, 8, "Ptr")
        return StrGet(pProperty, "UTF-16")
    }
}

That works, thankss, I appreciate it!


The "ResolvePackageDependencies" task failed unexpectedly.

After running "yo aspnetcore-spa" and creating an Aurelia (or Angular) .csproj for VS 2017, I get this error message immediately upon opening the project in VS.
Full error:
MSB4018	The "ResolvePackageDependencies" task failed unexpectedly.
System.IO.FileNotFoundException: Could not load file or assembly 'System.IO.FileSystem, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'System.IO.FileSystem, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Microsoft.NET.Build.Tasks.LockFileCache.LoadLockFile(String path)
at Microsoft.NET.Build.Tasks.LockFileCache.GetLockFile(String path)
at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.get_LockFile()
at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.ReadProjectFileDependencies()
at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.ExecuteCore()
at Microsoft.NET.Build.Tasks.TaskBase.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()

Additional info:
The project built without errors at first after running "yo aspnetcore-spa".  But I started receiving this error at some point after running the app.  I deleted the project and started over and it was the same thing:  it worked initially, but then I started getting the error again (no changes were made).

Do you have the latest VS2017 installed or some RC version of it perhaps?

From the VS2017 About dialog:
Microsoft Visual Studio Professional 2017
Version 15.1 (26403.3) Release
So it is not a RC.

@JordanMarr I think you must be running an old version of generator-aspnetcore-spa. Can you please update to the latest and try again? Or can you confirm what version of generator-aspnetcore-spa you have?
Your error sounds like the same thing that was reported here: https://github.com/aspnet/JavaScriptServices/issues/620


Fix import path

I got import path error below with  using vtubestudio version 1.8.0 and 1.9.0 at webpack build phase. 1.6.1 works fine for me.
ERROR in ./node_modules/vtubestudio/lib/plugin.js 71:12-26
Module not found: Error: Can't resolve 'src' in '/Users/satetsu888/work/vts-plugin/node_modules/vtubestudio/lib'
...

It seems to be simple miss typing, so patched.

Thanks for finding that. I'll merge and republish.

Republished as<EMAIL_ADDRESS>


Adjust XPath docs

Update XPath and Retrieve docs based on the discussion I had with @NatasaKralj

@Yiyun333 great work with this PR so far! Let me know what you think of the comments.
A note on the XPath Tokens doc: would it help clarify the text "A XPath query always starts with the tokens //" by adding "A full XPath query..."? The emphasis is just for clarity, not to add to the text.

@NatasaKralj  Added.


[$250] Create automated tests for Workspace Profile, Members and Categories pages

Problem
New API commands introduced as part of the Simplified Collect project don't have automated tests, which can lead to bugs and unexpected behavior when these commands are updated.
Solution
Add automated tests for the commands below:

[ ] Test UpdateWorkspaceDescription
[ ] Test AcceptJoinRequest
[ ] Test UpdateWorkspaceMembersRole
[ ] Test RequestWorkspaceOwnerChange
[ ] Test AddBillingCardAndRequestPolicyOwnerChange
[ ] Test SetWorkspaceRequiresCategory
[ ] Test CreateWorkspaceCategories
[ ] Test RenameWorkspaceCategory
[ ] Test SetWorkspaceCategoriesEnabled
[ ] Test DeleteWorkspaceCategories

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011452b1c44ee7036a
Upwork Job ID:<PHONE_NUMBER>746893312
Last Price Increase: 2024-04-23
Automatic offers:

hoangzinh | Reviewer | 0
tienifr | Contributor | 0

I think @tienifr's proposal looks good. Gonna assign them to this issue.

Thanks @hoangzinh , seems like, with the deploy freezer, we're going to have a LOT of issue come due for payment at/around the same time

Contributor: @tienifr  paid $250 via Upwork
Contributor+: @hoangzinh paid $250 via Upwork.
I don't think we need a regression test here. @luacmartins , comment and reopen if you disagree.

No requession test needed


Only show twitch player when live

https://dev.twitch.tv/docs/api/reference/#get-streams

Implemented in #26


Error log at Server startup. No block found.

Minecraft 1.7.10
Forge: 1.7.10 - <IP_ADDRESS>4
Mod: Archimedes Ships Plus 1.7.10 1.8.1
This error is as old as I can remember doing things with my Server, but I forgot how I am able to fix it, or even if it is a critical issue. I haven't tweaked the Main.cfg, so this is the file that was created after the Server started.
Main.cfg
This is the error log:
[Server thread/WARN] [MovingWorld/MovingWorld]: No block found for ArchimedesShips:floater at block_densities[0]
[Server thread/WARN] [MovingWorld/MovingWorld]: No block found for ArchimedesShipsPlus:balloon at block_densities[1]

This is the whole log file of the server: LINK

Those lines are clearly just warning, "WARN", so unless i'm wrong, that would not be the cause of a crash.
If you were to send the log file again (because it say s it was removed), then someone might be able to figure out whats crashing your server,

Those lines are clearly just warning, "WARN", so unless i'm wrong, that would not be the cause of a crash.
If you were to send the log file again (because it say s it was removed), then someone might be able to figure out whats crashing your server,

Correct, this is not a fatal error.


The description of atomicint does not make any reference to its safety under threading

Problem or new feature
Although that's quite clear from the description of the methods, it would be awesome to also get its main use case in the main description.
Suggestions
There's a (very brief) description of atomic data types in the native types page, which could be linked; also atomic operations are described in the numerics tutorial. Linking and/or expanding them could contribute to improvement.

atomicint has nothing to do with thread safety, nor do any atomic types. Atomic operations, which are not the same as atomic types, have to do with thread safety. Atomic types are about using the proper size type for the underlying hardware. I'd say the existing documentation on atomic operations that is linked to is fine:

The language offers some operations that are guaranteed to be performed atomically, i.e. safe to be executed by multiple threads without the need for locking with no risk of data races.

The clarification you just inserted could be also a good idea. Any improvement will help, anyway.

# atomicint, but not thread safe
➜  ~ raku -e 'my atomicint $a = 0; await (^100).map({ start { sleep 0.1; $a++ } }); say $a'
91

# no atomicint, but thread-safe (but don't do this)
➜  ~ raku -e 'my int $a = 0; await (^100).map({ start { sleep 0.1; cas $a, {$_+1}; } }); say $a'
100


Completeness?

What is the completeness of this api? in relation say to https://github.com/ipfs/js-ipfs-api ?
Many people are using ipfs from python and they've asked me this question lots. I think it would be good to have a spec completeness markdown checklist.

As far as I am aware, this is where things are. This is drawn from here.
There were a few items in the spec that I'm not sure how to implement (node_start and node_stop), and a few that people on IRC said to hold off on because they might have security implications.
Core

[x] version
[ ] node

[x] id
[ ] start - not implemented due to unclear spec
[ ] stop - not implemented due to unclear spec

[x] block

[x] get
[x] put
[x] stat

[x] object

[x] data
[x] get
[x] links
[x] new
[x] patch
[x] put
[x] stat

[x] refs

[x] local

[ ] repo

[ ] init - not implemented due to security concerns
[x] stat
[x] gc
[ ] config get - not implemented due to security concerns
[ ] config put - not implemented due to security concerns

[x] pin

[x] add
[x] ls
[x] rm

Extensions

[ ] name (ipns)

[ ] name publish
[ ] resolve

[ ] dns

[ ] resolve

[ ] tar

[ ] add
[ ] cat

[ ] tour

[ ] list
[ ] next
[ ] restart

[x] files

[x] add - see #49
[x] cat
[x] get - see #48

[ ] stat

[ ] bw

[ ] mount
[ ] bootstrap

[ ] add
[ ] list
[ ] rm

[ ] bitswap - see #47

[ ] stat
[ ] unwant
[ ] wantlist

[x] log

[x] level
[x] tail

Actually, the above is a checklist from the wrong API? I'm confused about the discrepancies between this and this.
@jbenet What is the difference in intention between those two specs?
Here is the functionality of py-ipfs-api compared against the Apiary:
NOTE: Not all of the following are tested currently.

[x] add
[ ] bitswap

[ ] stat
[ ] wantlist
[ ] unwant

[x] block

[x] get
[x] put
[x] stat

[ ] bootstrap

[x] add
[ ] list
[x] rm

[x] cat
[ ] commands
[x] config

[x] config
[x] replace
[x] show

[x] dht

[x] findpeer
[x] findprovs
[x] get
[x] put
[x] query

[ ] diag

[ ] cmds
[ ] cmds clear
[ ] cmds set-time
[ ] net
[ ] sys

[x] dns
[x] file ls
[ ] files

[x] rm
[ ] flush
[x] mv
[x] cp
[x] ls
[x] mkdir
[x] stat
[x] read
[x] write

[x] get
[x] id
[x] log

[x] level
[x] ls
[x] tail

[x] ls
[x] name

[x] publish
[x] resolve

[ ] object

[x] data
[ ] diff
[x] get
[x] links
[x] new
[x] patch append-data
[x] patch add-link
[x] patch rm-link
[x] patch set-data
[x] put
[x] stat

[x] pin

[x] add
[x] ls
[x] rm

[x] ping
[x] refs

[x] refs
[x] local

[ ] repo

[ ] fsck
[x] gc
[ ] stat
[ ] verify
[ ] version

[x] resolve
[ ] stats

[ ] bitswap
[ ] bw
[ ] repo

[ ] swarm

[x] addrs
[ ] addrs local
[x] connect
[x] disconnect
[ ] filters
[x] filters add
[x] filters rm
[x] peers

[ ] tar

[ ] add
[ ] cat

[ ] tour

[ ] tour
[ ] list
[ ] next
[ ] restart

[ ] update
[x] version

And some pythonic candy:

[x] add str
[x] add json
[x] get json
[x] add pyobj
[x] get pyobj

cc @diasdavid @RichardLitt they can maybe explain more.
On Mon, Aug 15, 2016 at 17:28 Christopher Waldon<EMAIL_ADDRESS>wrote:

Actually, the above is a checklist from the wrong API? I'm confused about
the discrepancies between this
http://docs.ipfs.apiary.io/#reference/bitswap/get and this
https://github.com/ipfs/specs/blob/master/public-api/core/README.md.
@jbenet https://github.com/jbenet What is the difference in intention
between those two specs?
Here is the functionality of py-ipfs-api compared against the Apiary:
NOTE: Not all of the following are tested currently.

add
bitswap

stat
wantlist
unwant

block

get
put
stat

bootstrap

add
list
rm

cat
commands
config

config
replace
show

dht

findpeer
findprovs
get
put
query

diag

cmds
cmds clear
cmds set-time
net
sys

dns
file ls
files

rm
flush
mv
cp
ls
mkdir
stat
read
write

get
id
log

level
ls
tail

ls
name

publish
resolve

object

data
diff
get
links
new
patch append-data
patch add-link
patch rm-link
patch set-data
put
stat

pin

add
ls
rm

ping
refs

refs
local

repo

fsck
gc
stat
verify
version

resolve
stats

bitswap
bw
repo

swarm

addrs
addrs local
connect
disconnect
filters
filters add
filters rm
peers

tar

add
cat

tour

tour
list
next
restart

update
version

And some pythonic candy:

add str
add json
get json
add pyobj
get pyobj

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/py-ipfs-api/issues/42#issuecomment-239934820,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIcoeefNHtrOTwH2s1IzOn6UGHDXbsiks5qgNoSgaJpZM4IuHG1
.

@whereswaldon with regards to bitswap, they both list the same commands, care to list what is the discrepancy you see?
Another great resource to help is: https://github.com/ipfs/interface-ipfs-core, we have a bunch of the API defined at https://github.com/ipfs/interface-ipfs-core/tree/master/API and with tests (for js, but that can be translated to python, here https://github.com/ipfs/interface-ipfs-core/tree/master/src). Currently, both js-ipfs and js-ipfs-api follow this interface.

@diasdavid Not with regards to bitswap, but in general. Both of those seem like feature inventories, but not necessarily the same features. One lists "files add", "files get", and "files cat" while the other has "get", "add", "cat" a tons of different commands under the "file" and "files" namespaces. They just don't seem to align, and I don't understand why.
I'll take a look at those tests. It would be nice to port them to Python. Thank you!

The "files" is a specific case, see: https://github.com/ipfs/specs/issues/98


casperjs 1.1-beta executing asynchronously at CLI level

The CLI for casperjs is executing asynchronously from the command line. The command finishes executing before casperjs itself does any work. As a result, the command always has an exit code of 0 even when tests fail. This is causing issues with build tools that utilize casperjs. The error scenarios are as follows.

Build tool calls capserjs.
It complete successfully and immediately since execution of the tests are being delegated to another thread.
Build tool reports successful build.
Casperjs finally executes sometime later and reports a failed test.

It looks like 1.0.4 executes synchronously and might remedy the issue until it's addressed. Can you make 1.0.4 available via npm?

Can you share a minimal working example code in which this behaviour can be seen?

After retesting it looks like this may have been an issue with the build tool itself. I may have mixed tests while I was dealing with the issue and attributed the behavior to the wrong component at the time. Sorry for the confusion and thanks for the reply. Closing this issue.


Cannot convert return expression of type 'Promise<>' to return type 'Guarantee<[]>'

PromiseKit version: 6.2.0
Xcode version: 9.2
Hi guy!
I have some problems when updating from ver 4.x to 6.x. However, mostly I can resolve by reading doc. But I have the only issue:
let promise = Promise<[DAIPNumber]>.pending()

firstly{
    UIApplication.shared.isNetworkActivityIndicatorVisible = true
    return getIPNumbers(withAPI: .incomingPhoneNumber)
}.done{ ipNumbers in
    promise.resolver.fulfill(ipNumbers)
}.ensure {
    UIApplication.shared.isNetworkActivityIndicatorVisible = false
}.catch { error in
    promise.resolver.reject(error)
}

return promise.promise

It always shows me the error when I put 2 lines in the firstly. If I remove the first line, it's ok. Please show me my issue if I missing something.
Thanks!

Impossible to help since you don't say what the error is or which line it happens on.

Like at the very least your code is identical to the much shorter:
UIApplication.shared.isNetworkActivityIndicatorVisible = true

return firstly {
    getIPNumbers(withAPI: .incomingPhoneNumber)
}.ensure {
    UIApplication.shared.isNetworkActivityIndicatorVisible = false
}

Hi mxcl,
Thanks for your response.
firstly{
    UIApplication.shared.isNetworkActivityIndicatorVisible = true
    return getIPNumbers(withAPI: .incomingPhoneNumber)
}

Got the error at the return.

Specify the return type or do what I did in my above example where I make the firstly one line.

Yes, because of it could be 2 line in the firstly with the previous version and I still see in your doc, we could put 2 lines. Thanks for your help.


CloudCompare, pdal, libe57format, MeshLabXML

Motivation for this change
This adds various 3D point cloud processing tools, including CloudCompare, one of the main point cloud GUI softwares.
Required for that:

Making available both LASzip 2 and LASzip 3, see https://github.com/libLAS/libLAS/issues/144, CC @michelk
Adding the pdal library

Also:

MeshLabXML, cc @FRidh or @jonringer for some Python packaging style review

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I've tested tested running CloudCompare on Ubuntu with nixGL, built on a NixOS builder. @chpatrick has run it on NixOS desktop.
MeshLabXML is only packaged, and not significantly tested (but that is fine).

@jonringer Thanks, much appreciated. I have incorporated all feedback.

Result of nixpkgs-review pr 91523 1

10 packages built:
- LASzip
- LASzip2
- cloudcompare
- grass
- libLAS
- libe57format
- pdal
- python27Packages.meshlabxml
- python37Packages.meshlabxml
- python38Packages.meshlabxml