RealOps or something like that.

Sometimes it's hard to provide constructors for One and Zero because the constructors require additional state. In cases like that, it'd still be useful if either Real didn't depend on One and Zero, or there was a separate RealOps trait that didn't depend on them.
Edit: Also, I guess the other constructors in Real would also have to not be there.

Do you have a concrete example of a type with such stateful constructors?

In my case, reverse mode AD needs each number to have a reference to a tape. But now that I think about it, generic math without being able to construct numbers is pretty useless, so I think just removing the constructors is a pretty stupid idea. Sorry about that!


Paket installed packages are not available for projects

Description
I'm currently using Ubuntu 20.04, and I have the .NET SDK 6.0.101 installed. The Paket version that is installed in the project is the 6.2.1.
I have this project https://github.com/64J0/Fsharp-Kubernetes-Yaml-Gen where I'm trying to install Expecto using paket but for some reason, it is not working properly. I have followed all the steps in the Paket docs to start using this tool but it does not work.
$ dotnet new tool-manifest
$ dotnet tool install paket
$ dotnet paket init

$ dotnet paket add Expecto --version 9.0.4 --project ./Fsharp-K8s.Test/Test.fsproj
$ dotnet paket add Expecto.BenchmarkDotNet --version 9.0.4 --project ./Fsharp-K8s.Test/Test.fsproj
$ dotnet paket add Expecto.FsCheck --version 9.0.4 --project ./Fsharp-K8s.Test/Test.fsproj
$ dotnet paket add Expecto.Hopac --version 9.0.4 --project ./Fsharp-K8s.Test/Test.fsproj

$ dotnet tool restore
$ dotnet paket install
$ dotnet paket restore

Repro steps

Close the repository https://github.com/64J0/Fsharp-Kubernetes-Yaml-Gen.
Try to install the Paket dependencies.
Try to build the project dotnet build.
See the error messages.

Expected behavior
I was expecting that Paket would be able to add the packages I want to the projects I want.
Actual behavior
The project is not building because it can't find the Expecto files that should have been added by Paket to the project.

Known workarounds
If I install the package with nuget it works fine (except from some warnings related to conflicts):
$ dotnet add ./Fsharp-K8s.Test/Test.fsproj package Expecto --version 9.0.4

I changed the .fsproject to use the version 5.0 of dotnet and now the project is working fine with Paket. What should we do to make this project compatible with the latest version of dotnet?

Just saw right now that the integration with Dotnet 6 is still on alpha, so it is just a matter of time. Cool. https://github.com/fsprojects/Paket/blob/master/RELEASE_NOTES.md

Any news? Still not working when trying to use in a  .NET 6 project to install Expecto.

I was also encountering this with paket 7.1.5. Interestingly, downgrading to 6.2.1 fixed it for me.


Fix PfcpAddNodeWithSeid preferIPv4

Set preferIPv4 to 1 (true) in PfcpAddNodeWithSeid when family as AF_INET

Thanks for the PR!


Using only GDMP GDExtension, extra classes are created

I only have one GDExtension activated e.g. GDMP
Not all classes generated are relevant to the  specific GDExtension e.g. GDMP

This is not a big issue right now. However when one need to create individual Nuget for each GDExtension. this could cause extra work to track

This is indeed a big issue right now, currently, we obtain classes through the ClassDB API, which only gives us a list of strings, and there is no way of knowing which one is a GDExtension class. Our current approach is really jank, which leads to these editor types flying around.
As mentioned by @ZerxZ, our feature request is there, we should have proper support once it's merged.


Support multiple SubscriberClient and PublisherClient instances in ServiceCollection by the notion of Keyed service

Current ServiceCollection Extensions that assist with registering SubscriberClinet and PublisherClient does not support Keyed service registration that was introduced with .NET 8.0.
Having multiple singletons registered the consumer must iterate (taking a dependency of IEnumerable<SubscriberClient>/IEnumerable<PublisherClient>) through existing instances looking for the one that has the desired SubscriptionName/TopicName.
This is somewhat cumbersome and can be avoided using the newer registration mechanizm.
I propose multitargeting PubSub client to .NET 8.0 and adding conditional compilation to add support for Keyed service registration in the ServiceCollectionExtensions class.
I can prepare this change if the community agrees in the value of said change.

Here are some good examples:
https://andrewlock.net/exploring-the-dotnet-8-preview-keyed-services-dependency-injection-support/

Thanks, we'll have a look.

Note that we can't do this just yet, as we're not building with the .NET 8 SDK yet, for internal CI reasons. We're hoping to resolve those, but it does mean this definitely won't happen very soon.

Sorry to hear that .NET 8 SDK cannot be used. The point is moot, so to speak, for now.

We are tracking this internally. As per #12561 (comment) before we are able to do this, we need to:

Be able to build in .NET 8, which we can't at the moment for internal reasons.
Decide wether we want libraries to explicitly target .NET 8.

For now, I'm closing the feature request as we cannot support it. Once we remove blockers and made a decision on targetting .NET 8, we may reopen, but that will all be later in the year. Sorry this might no be want you want to hear.


Fixed one more signature

This fixes this issue in 1.14.31
[SolastaUnfinishedBusiness] [Error] HarmonyLib.HarmonyException: Patching exception in method null ---> System.ArgumentException: Undefined target method for patch method static System.Collections.Generic.IEnumerable`1<HarmonyLib.CodeInstruction> SolastaUnfinishedBusiness.Patches.ApplyForms_Patch::Transpiler(System.Collections.Generic.IEnumerable`1<HarmonyLib.CodeInstruction> instructions)
  at HarmonyLib.PatchClassProcessor.PatchWithAttributes (System.Reflection.MethodBase& lastOriginal) [0x00047] in <255414689d344b1385ae719f6cce8c55>:0
  at HarmonyLib.PatchClassProcessor.Patch () [0x00068] in <255414689d344b1385ae719f6cce8c55>:0
   --- End of inner exception stack trace ---
  at HarmonyLib.PatchClassProcessor.ReportException (System.Exception exception, System.Reflection.MethodBase original) [0x00127] in <255414689d344b1385ae719f6cce8c55>:0
  at HarmonyLib.PatchClassProcessor.Patch () [0x00093] in <255414689d344b1385ae719f6cce8c55>:0
  at SolastaUnfinishedBusiness.Api.ModKit.ModManager`2[TCore,TSettings].Enable (UnityModManagerNet.UnityModManager+ModEntry modEntry, System.Reflection.Assembly assembly) [0x0008f] in <942a01f68f30431488f73c09af8f4d85>:0

there is still this issue:
[SolastaUnfinishedBusiness] [Error] HarmonyLib.HarmonyException: Patching exception in method System.Boolean CursorLocationBattleFriendlyTurn::IsValidAttack(GameLocationCharacter attacker, GameLocationCharacter defender, CursorType& attackCursor) ---> System.FormatException: Method System.Boolean CursorLocationBattleFriendlyTurn::IsValidAttack(GameLocationCharacter attacker, GameLocationCharacter defender, CursorType& attackCursor) cannot be patched. Reason: Invalid IL code in (wrapper dynamic-method) CursorLocationBattleFriendlyTurn:CursorLocationBattleFriendlyTurn.IsValidAttack_Patch0 (CursorLocationBattleFriendlyTurn,GameLocationCharacter,GameLocationCharacter,CursorDefinitions/CursorType&): IL_00d7: call      0x00000023

  at HarmonyLib.PatchFunctions.UpdateWrapper (System.Reflection.MethodBase original, HarmonyLib.PatchInfo patchInfo) [0x0008c] in <255414689d344b1385ae719f6cce8c55>:0
  at HarmonyLib.PatchClassProcessor.ProcessPatchJob (HarmonyLib.PatchJobs`1+Job[T] job) [0x000bb] in <255414689d344b1385ae719f6cce8c55>:0
   --- End of inner exception stack trace ---
  at HarmonyLib.PatchClassProcessor.ReportException (System.Exception exception, System.Reflection.MethodBase original) [0x0010f] in <255414689d344b1385ae719f6cce8c55>:0
  at HarmonyLib.PatchClassProcessor.Patch () [0x00093] in <255414689d344b1385ae719f6cce8c55>:0
  at SolastaUnfinishedBusiness.Api.ModKit.ModManager`2[TCore,TSettings].Enable (UnityModManagerNet.UnityModManager+ModEntry modEntry, System.Reflection.Assembly assembly) [0x0008f] in <942a01f68f30431488f73c09af8f4d85>:0

that I'm not sure how to fix - I think the IsValidAttack maybe now has one more parameter, but I'm not sure how to pass it through the proxy - this issue I'm leaving to you.

this fix seems to be already implemented. As for IsValid attack - I sent PR with a fix

Thanks. This has been fixed already.


Add Obee Network-token

为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项

[ ] logo 尺寸：120*120 px
[ ] logo 背景：透明
[ ] 代币有至少一笔成功的转账记录
[ ] 此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
[ ] .json 和 .png 文件名一致（包括大小写）

项目资料：
Obee Network官网：https://obee.top
Obee Network 产品：https://www.obee.vip
Obee Network项目白皮书：https://obee.top/whitepaper/OBEE-Whitepaper-cn.pdf
Obee Network 安卓下载链接：https://obee.top/package/ObeeNetwork-en.apk
Obee Network 详细介绍：https://bbs.nuls.io/t/obee-network-information-links-obee-network/2219?u=obeenetwork
项目介绍：
Obee Network社交平台将是普通用户进入区块链时代的第一款社交产品，是基于区块链社交的激励平台，构建了一套完整的去中心化的社交网络。
让用户在Obee Network上看见全球用户的创作，论坛、热帖、应用和电影。让社交没有边界性，随时随地都可以和其他用户分享精彩的瞬间。
Obee Network是激励型社交平台，Obee Network社交平台具备内容发布系统，评论转发，账户体系，商品，账户体系，新闻博客，活动等模块。
团队背景：技术团队拥有区块链开发专家，对智能合约开发、跨链机制有深入的研究。开发团队成员都拥有3年以上的区块链架构和社交产品开发经验，负责Obee Network生态的技术开发和部署。产品团队曾就职Facebook，Tencent等企业，拥有深度分析能力、资源整合、创新等能力，负责Obee Network生态的功能设计。
媒体报道：
Twitter: https://twitter.com/ObeeNetwork;
Telegram: https://t.me/ObeeNetwork;
Reddit: https://www.reddit.com/user/ObeeNetwork/;
Medium: https://medium.com/@ObeeNetwork/
收录的交易所：Uniswap
https://uniswap.info/token/0x3678d8cc9eb08875a3720f34c1c8d1e1b31f5a11
Uniswap 流动性奖励声明：https://bbs.nuls.io/t/obee-network/2195?u=obeenetwork
转账所需 Gas Limit（对 ERC-20 项目方）:（默认为 60000）

Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists

[ ] logo dimensions: 120*120 px
[ ] logo background: Transparent
[ ] At least one transaction on the token contract
[ ] For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
[ ] Same document name for both .json and .png (Including capitalization)

Project Background:
Obee Network website: https://obee.top
Obee Network products: https://www.obee.vip
Obee Network Android download link: https://obee.top/package/ObeeNetwork-en.apk
Obee Network project white paper: https://obee.top/whitepaper/OBEE-Whitepaper-en.pdf
Obee Network detailed introduction: https://bbs.nuls.io/t/obee-network-information-links-obee-network/2219?u=obeenetwork
Project Introduction:
The Obee Network social platform will be the first social product for ordinary users to enter the era of blockchain. It is an incentive platform based on blockchain social interaction and has built a complete decentralized social network.
Let users see the creations, forums, hot posts, applications, and movies of users from all over the world on Obee Network. Let social without boundaries, you can share wonderful moments with other users anytime, anywhere.
Obee Network is an incentive-based social platform. The Obee Network social platform has modules such as content publishing systems, comment forwarding, account system, products, account system, news blogs, and events.
Project team background: The technical team has blockchain development experts and has in-depth research on smart contract development and cross-chain mechanisms. The members of the development team have more than 3 years of experience in blockchain architecture and social product development and are responsible for the technical development and deployment of the Obee Network ecosystem. The product team has worked on Facebook, Tencent, and other companies, has in-depth analysis capabilities, resource integration, innovation, and other capabilities, and is responsible for the functional design of the Obee Network ecosystem.
Media publications:
Twitter: https://twitter.com/ObeeNetwork;
Telegram:https://t.me/ObeeNetwork;
Reddit:https://www.reddit.com/user/ObeeNetwork/;
Medium:https://medium.com/@ObeeNetwork/
Tradeable exchanges:
Uniswap
https://uniswap.info/token/0x3678d8cc9eb08875a3720f34c1c8d1e1b31f5a11
Uniswap liquidity reward statement：https://bbs.nuls.io/t/about-obee-networks-reward-statement-for-liquidity-providers/2196?u=obeenetwork
Recommended Gas Limit (For ERC-20 project teams) for the transaction: (Default is 60,000)

Thx

为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项
logo 尺寸：120*120 px
logo 背景：透明
代币有至少一笔成功的转账记录
此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
.json 和 .png 文件名一致（包括大小写）
项目资料：
Obee Network官网：https://obee.top
Obee Network 产品：https://www.obee.vip
Obee Network项目白皮书：https://obee.top/whitepaper/OBEE-Whitepaper-cn.pdf
Obee Network 安卓下载链接：https://obee.top/package/ObeeNetwork-en.apk
Obee Network 详细介绍：https://bbs.nuls.io/t/obee-network-information-links-obee-network/2219?u=obeenetwork
官方公告：https://obee.top/cn-notice.html#
项目介绍：
Obee Network社交平台将是普通用户进入区块链时代的第一款社交产品，是基于区块链社交的激励平台，构建了一套完整的去中心化的社交网络。
让用户在Obee Network上看见全球用户的创作，论坛、热帖、应用和电影。让社交没有边界性，随时随地都可以和其他用户分享精彩的瞬间。
Obee Network是激励型社交平台，Obee Network社交平台具备内容发布系统，评论转发，账户体系，商品，账户体系，新闻博客，活动等模块。
团队背景：技术团队拥有区块链开发专家，对智能合约开发、跨链机制有深入的研究。开发团队成员都拥有3年以上的区块链架构和社交产品开发经验，负责Obee Network生态的技术开发和部署。产品团队曾就职Facebook，Tencent等企业，拥有深度分析能力、资源整合、创新等能力，负责Obee Network生态的功能设计。
媒体报道：
Twitter: https://twitter.com/ObeeNetwork;
Telegram: https://t.me/ObeeNetwork;
Reddit: https://www.reddit.com/user/ObeeNetwork/;
Medium: https://medium.com/@ObeeNetwork/
收录的交易所：Uniswap
https://uniswap.info/token/0x3678d8cc9eb08875a3720f34c1c8d1e1b31f5a11
Uniswap 流动性奖励声明：https://bbs.nuls.io/t/obee-network/2195?u=obeenetwork
转账所需 Gas Limit（对 ERC-20 项目方）:（默认为 60000）
Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists
logo dimensions: 120*120 px
logo background: Transparent
At least one transaction on the token contract
For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
Same document name for both .json and .png (Including capitalization)
Project Background:
Obee Network website: https://obee.top
Obee Network products: https://www.obee.vip
Obee Network Android download link: https://obee.top/package/ObeeNetwork-en.apk
Obee Network project white paper: https://obee.top/whitepaper/OBEE-Whitepaper-en.pdf
Obee Network detailed introduction: https://bbs.nuls.io/t/obee-network-information-links-obee-network/2219?u=obeenetwork
Official Announcement ：https://obee.top/notice.html
Project Introduction:
The Obee Network social platform will be the first social product for ordinary users to enter the era of blockchain. It is an incentive platform based on blockchain social interaction and has built a complete decentralized social network.
Let users see the creations, forums, hot posts, applications, and movies of users from all over the world on Obee Network. Let social without boundaries, you can share wonderful moments with other users anytime, anywhere.
Obee Network is an incentive-based social platform. The Obee Network social platform has modules such as content publishing systems, comment forwarding, account system, products, account system, news blogs, and events.
Project team background: The technical team has blockchain development experts and has in-depth research on smart contract development and cross-chain mechanisms. The members of the development team have more than 3 years of experience in blockchain architecture and social product development and are responsible for the technical development and deployment of the Obee Network ecosystem. The product team has worked on Facebook, Tencent, and other companies, has in-depth analysis capabilities, resource integration, innovation, and other capabilities, and is responsible for the functional design of the Obee Network ecosystem.
Media publications:
Twitter: https://twitter.com/ObeeNetwork;
Telegram:https://t.me/ObeeNetwork;
Reddit:https://www.reddit.com/user/ObeeNetwork/;
Medium:https://medium.com/@ObeeNetwork/
Tradeable exchanges:
Uniswap
https://uniswap.info/token/0x3678d8cc9eb08875a3720f34c1c8d1e1b31f5a11
Uniswap liquidity reward statement：https://bbs.nuls.io/t/about-obee-networks-reward-statement-for-liquidity-providers/2196?u=obeenetwork
Recommended Gas Limit (For ERC-20 project teams) for the transaction: (Default is 60,000)

@sfsy520

thank you very much

非常抱歉，此token已经有代币信息，如需修改，请重新提交PR


EMP-374: Added CRM4 report API end-point and unit tests

What
Link to story
Describe what you did and why.
Checklist
Before you ask people to review this PR:

[ ] Tests should be passing: ./gradlew test
[x] Github should not be reporting conflicts; you should have recently run git rebase main.
[x] Avoid mixing whitespace changes with code changes in the same commit. These make diffs harder to read and conflicts more likely.
[x] You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
[x] You should have checked that the commit messages say why the change was made.

LGTM


break when n feature added

Ok, I got a bit bitchy through here, but this PR is not easy to evaluate.
There's a new feature that will have some effect -- but since you're the one whose got his head wrapped around the requirements you're better positioned to know if it makes sense.  You  didn't say anywhere in this PR with either documentation or unit tests what exactly the new feature is supposed to do. So how am I to judge it?

ok @jaberg  -- I've address all (I think) of what you asked for ... the PR is tested via its usage in eccv12 ... where the code uses the new features.
I think that we should evaluate both new pieces of code simultaneously .. and THEN once we agree on the design, write seperate tests for hyperopt alone.
it should NOT break compatilibty with hyperopt mongotrials at all, nothing about the new code should affect other calls that don't use the new features ... if it does can you point me to where it might?

On Wed, Feb 22, 2012 at 10:00 AM, Dan Yamins <
<EMAIL_ADDRESS>
wrote:

ok @jaberg  -- I've address all (I think) of what you asked for ... the PR
is tested via its usage in eccv12 ... where the code uses the new features.
could you point me to where?

I think that we should evaluate both new pieces of code simultaneously ..
and THEN once we agree on the design, write seperate tests for hyperopt
alone.
it should NOT break compatilibty with hyperopt mongotrials at all, nothing
about the new code should affect other calls that don't use the new
features ... if it does can you point me to where it might?

I raised this in connection to the delete_ids function, which I think you
deleted.

ok something happened that made the diff not show comments anymore, so replying here:
"""
It shouldn't really ... I think there's no interaction. (e.g. any setting of both parameters should lead to "reasonable" behavior ... but let's think through that more thoroughly)
"""
I like to know how my programs work a little more precisely than this (!?)

@jaberg:  the tests I'm referring to are:  everything in eccv12/tests/test_eccv12_experiments.py

On Wed, Feb 22, 2012 at 10:12 AM, Dan Yamins <
<EMAIL_ADDRESS>
wrote:

@jaberg:  the tests I'm referring to are:  everything in
eccv12/tests/test_eccv12_experiments.py

Ok, which branch?

@jaberg:
1) re knowing how things work precisely ... I don't know hyperopt well enough to make definitive statements about it.   I thought through this issue, but your input would be great.
2) re which branch: dan_develop_new

On Wed, Feb 22, 2012 at 10:17 AM, Dan Yamins <
<EMAIL_ADDRESS>
wrote:

@jaberg:

re knowing how things work precisely ... I don't know hyperopt well
enough to make definitive statements about it.   I thought through this
issue, but your input would be great.

I appreciate that, and I tried to make a clarifying statement here
https://github.com/jaberg/hyperopt/pull/83#commitcomment-996384

re which branch: dan_develop_new

ok, but I don't know the testing strategy in that file (and there isn't a
single comment or docstring in sight btw).
Which of those tests (all?) assert that the new mechanism doesn't run too
many or too few jobs?  The new mechanism is designed specifically and
solely to run the right number of jobs right?

I should add:  that i think much of the important testing for this will come from the asynchronous tests stuff we talked about yesterday.

will push some comments in test_eccv12_experiments  momentarily

On Wed, Feb 22, 2012 at 10:25 AM, Dan Yamins <
<EMAIL_ADDRESS>
wrote:

I should add:  that i think much of the important testing for this will
come from the asynchronous tests stuff we talked about yesterday.

Hmm, if you're talking about TestAsyncError, it won't help because it
doesn't call experiment.run

That's what I was hoping, that we could use TestAsyncError .... maybe there's something simple way to adapt it so we COULD use it for this purpose?

On Wed, Feb 22, 2012 at 10:31 AM, Dan Yamins <
<EMAIL_ADDRESS>
wrote:

That's what I was hoping, that we could use TestAsyncError .... maybe
there's something simple way to adapt it so we COULD use it for this
purpose?
I don't think that makes sense - TestAsyncError works specifically on the
basis of replacing exp.run in order to achieve a more control over the
order and nature of interactions with the BanditAlgo.  If you look at the
code of that class, I think you'll see that it doesn't make sense to call
exp.run.

I see.   but the concept of being able to simulate asynchronous environments as a way to test the effects of exp.run does make sense .. I can envision tests I'd want to run.

How about adding at least one test to test_base.py:TestCoinFlipExperiment in hyperopt that uses this new argument, and shows that it acts as a correct governor at least in the simple case of jobs that don't crash, in a sync execution.
If you want to get trickier, look at test_mongoexp at how those async experiments are done, and add a new test case there that uses the new mechanism in the same way as ECCV12 (with N=maxint) and assert that at least in the context of non-failing jobs that the right number of trials gets done.
I agree that there are more elaborate tests one would like to do, but as a first draft I think this would be a bare minimum.

OK I added the basic coinflip test experiment ... still working on the mongoexp async experiments ...

OK several tests in have been added, in TestCoinFlip and
test_mongoexp.TestExperimentWithThreads
what else needed before merge of this and eccv12: dan_develop_new?
On Wed, Feb 22, 2012 at 10:47 AM, James Bergstra <
<EMAIL_ADDRESS>
wrote:

How about adding at least one test to test_base.py:TestCoinFlipExperiment
in hyperopt that uses this new argument, and shows that it acts as a
correct governor at least in the simple case of jobs that don't crash, in a
sync execution.
If you want to get trickier, look at test_mongoexp at how those async
experiments are done, and add a new test case there that uses the new
mechanism in the same way as ECCV12 (with N=maxint) and assert that at
least in the context of non-failing jobs that the right number of trials
gets done.
I agree that there are more elaborate tests one would like to do, but as a
first draft I think this would be a bare minimum.

Reply to this email directly or view it on GitHub:
https://github.com/jaberg/hyperopt/pull/83#issuecomment-4106574

had a couple of little comments, but looks good. Thanks for adding the tests.

Merged!


[New term] No-code

1. Please describe why this term needs to be added
What this term is about? (briefly)

See https://en.wikipedia.org/wiki/No-code_development_platform

Why this term needs to be added? (briefly)

Identifies whether non-developers can be consumers of a tool

2. Checklist

[X] The suggested term fits the cloud native definition or is essential to understanding cloud native terms. (We hope to avoid adding general or broad terminologies)
[X] There is no existing issue yet. (shift+click to check existing issues)
[X] I understand that maintainers will assess if the term should be part of the Glossary. (Please be patient)
[X] I want to work on this term. (If not checked, maintainers will assign another volunteer)

(Note)
Maintainers will assign a label after assessment procedure.
(from triage/awaiting to triage/accepted or triage/not accepted)
A contributor can be assigned to this issue after the issue get the triage/accepted label.
The assignee needs to check Style Guide.

Thanks for your suggestion. After some deliberation with the maintainers, we decided not to include this term because it is not specific to cloud native but rather a more general dev concept.


fix: image and link to project board (#33)

closes #33
Before

After

thank you for contributing


Tag fails to load, resulting in config not working.

I am running Hexlands 4.0.0 on 1.19.2. On launch I get the following error:
[31Oct2023 23:05:33.424] [Worker-Main-19/ERROR] [net.minecraft.tags.TagLoader/]: Couldn't load tag [hexlands:hexlands (from hexlands-forge-1.19.2-4.0.0.jar), hexlands:hexlands_overworld_only (from hexlands-forge-1.19.2-4.0.0.jar), gardenofglass:gardenofglass (from gardenofglass-1.11.jar)] as it is missing following references: hexlands:hexlands (from hexlands-forge-1.19.2-4.0.0.jar),  	hexlands:hexlands_overworld_only (from hexlands-forge-1.19.2-4.0.0.jar),  	gardenofglass:gardenofglass (from gardenofglass-1.11.jar) [31Oct2023 23:05:33.424] [Worker-Main-19/ERROR] [net.minecraft.tags.TagLoader/]: Couldn't load tag [#minecraft:normal (from Default)] as it is missing following references: #minecraft:normal (from Default)
As a result, Hexlands completely ignores the datapack worlgen file.
This is file .minecraft/kubejs/data/minecraft/dimension/overworld.json :
{
	"type": "minecraft:overworld",
	"generator": {
		"type": "hexlands:hexlands",
		"seed": 0,
		"settings": "minecraft:overworld",
		"hex_settings": {
			"biome_scale": 8,
			"hex_size": 40,
			"hex_border_threshold": 0.95,
			"bottom_border": {
				"min_height": 62,
				"max_height": 65,
				"state": {
					"Name": "nyagibits_bytes:flake",
					"Properties": {}
				}
			}
		},
		"biome_source": {
			"type": "multi_noise",
			"preset": "overworld"
		},
		"forge:use_server_seed": false
	}
}

How do I fix this?

Tag failing to load is typically caused by one of the elements failing to load, probably an error in your datapack somewhere. In either case, I am not supporting 1.19 anymore so good luck.

I'm not sure it's something unique to their datapack - I get the same error in a fresh, vanilla 1.19.2 Minecraft with only hexlands-forge-1.19.2-4.0.0 and no other mods:
[17:15:12] [Worker-Main-7/ERROR] [minecraft/TagLoader]: Couldn't load tag [hexlands:hexlands (from hexlands-forge-1.19.2-4.0.0.jar), hexlands:hexlands_overworld_only (from hexlands-forge-1.19.2-4.0.0.jar)] as it is missing following references: hexlands:hexlands (from hexlands-forge-1.19.2-4.0.0.jar),  	hexlands:hexlands_overworld_only (from hexlands-forge-1.19.2-4.0.0.jar) [17:15:12] [Worker-Main-7/ERROR] [minecraft/TagLoader]: Couldn't load tag [#minecraft:normal (from Default)] as it is missing following references: #minecraft:normal (from Default)
In that case, it still works, but in my in-progress mod that uses hexland as a dependency, datapack validation fails for everything. I also get this error:
Caused by: com.google.gson.JsonParseException: Error loading registry data: Unknown registry key in ResourceKey[minecraft:root / minecraft:worldgen/chunk_generator]: hexlands:hexlands missed input: {"minecraft:overworld":{"type":"minecraft:overworld","generator":{"type":"hexlands:hexlands","settings":"minecraft:overworld","biome_source":{"type":"minecraft:multi_noise","preset":"minecraft:overworld"},"hex_settings":"hexlands:overworld"}}}; Missing overworld dimension
Could be that one's my fault somehow, but there's barely anything going on in my mod yet, and the resources/data folder is empty.
Anyway, I get that you're not supporting 1.19, but if you have any insight at all into this, it'd be appreciated! I'm happy to do a PR for you if there's a fix I can implement.


window.onerror in /

Error in ClashLeaders
window.onerror in /
Uncaught exception: ReferenceError: Undefined variable: localStorage
View on Bugsnag
Stacktrace
https://www.clashleaders.com/static/js/index.ae36d8c147c8bd0cb5cb.js:1 -

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
window.onerror in /


Better rendering of Types and Defaults

Is your feature request related to a problem? Please describe.
Currently, this library will show the full path of any non-builtin Type Annotations. This often causes the description section to be squished and making the docs less desirable to read.
As well as this, default values are repred rather than just disaplying their name, for large objects like IntFlags, this can make the documentation even harder to read.
Couple both of these issues and you have some very messy docs.
Here is an example from your own docs.
Currently:

Desired:

From my own docs, here is a worst case example of a Type Annotation displaying its full path, plus this library repring the default

As you can see description gets squished to the point it may as well not be there
Describe the solution you'd like
An option to only display the name of the Type, not its path. And another option to not repr the default value, and instead show its name
Describe alternatives you've considered
I have tried writing the type in my docstrings, hoping this library would use that, however it will ignore that and use my type annotations instead.

Hey! Totally agree :slightly_smiling_face:
Let me give you a glimpse of the new handler capabilities:
Table style:

SpaCy style:

List style (default not displayed yet, not sure how we should display it):

Types are rendered as written in the source. Ideally defaults will automatically cross-reference objects as well.
If type and default are squishing the description too much, the spacy style can help. The least problematic style will always be the list one.
What do you think?

This makes me very happy. I think most of my pestering will be solved once we get that handler 😅

New handler is here! https://mkdocstrings.github.io/handlers/overview/#about-the-python-handlers
I would greatly appreciate if you could give it a try @LordOfPolls, even if you don't adopt it (as it's still experimental) and just report back some issues :slightly_smiling_face:
I'll close this for now as I'll likely not work on the legacy handler anymore, but feel free to further comment or reopen :slightly_smiling_face:


Search: improve the look&feel of the modal

Currently, the modal looks "fine". However, it's pretty basic and it could be improved in a lot of ways. I'm opening this issue here to get some feedback about what are those improvements we can do? related to look&feel, style, content, etc.

There is some extra context in https://readthedocs.slack.com/archives/C029M3W01KR/p1696954421985799?thread_ts=1696940708.523109&cid=C029M3W01KR


Numpy fails without black

Describe the bug
Importing numpy fails unless imported alongside black.
Steps To Reproduce
Steps to reproduce the behavior:
# flake.nix
{
  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
    utils.url = "github:numtide/flake-utils";
  };

  outputs = {
    self,
    nixpkgs,
    utils,
  }:
    utils.lib.eachDefaultSystem (system: let
      pkgs = import nixpkgs { inherit system; };
    in {
      devShell = pkgs.mkShell {
        buildInputs = [pkgs.pre-commit] ++ (with pkgs.python39.pkgs; [numpy]);
      };
    });
}

Then run
nix-develop
python -c 'import numpy'

Expected behavior
numpy should import without errors
Instead we get
Traceback (most recent call last):
  File "/nix/store/qg0d8c64ky1zvwa14rmaqd7m38jcg832-python3.9-numpy-1.21.6/lib/python3.9/site-packages/numpy/core/__init__.py", line 22, in <module>
    from . import multiarray
  File "/nix/store/qg0d8c64ky1zvwa14rmaqd7m38jcg832-python3.9-numpy-1.21.6/lib/python3.9/site-packages/numpy/core/multiarray.py", line 12, in <module>
    from . import overrides
  File "/nix/store/qg0d8c64ky1zvwa14rmaqd7m38jcg832-python3.9-numpy-1.21.6/lib/python3.9/site-packages/numpy/core/overrides.py", line 7, in <module>
    from numpy.core._multiarray_umath import (
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/nix/store/qg0d8c64ky1zvwa14rmaqd7m38jcg832-python3.9-numpy-1.21.6/lib/python3.9/site-packages/numpy/__init__.py", line 150, in <module>
    from . import core
  File "/nix/store/qg0d8c64ky1zvwa14rmaqd7m38jcg832-python3.9-numpy-1.21.6/lib/python3.9/site-packages/numpy/core/__init__.py", line 48, in <module>
    raise ImportError(msg)
ImportError:

IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.10 from "/nix/store/ddhcwc8k9ma093n5vlpa9l617p4q2cax-python3-3.10.5/bin/python"
  * The NumPy version is: "1.21.6"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Original error was: No module named 'numpy.core._multiarray_umath'

Additional context
I found that adding black as in:
buildInputs = [pkgs.pre-commit] ++ (with pkgs.python39.pkgs; [numpy black]);

eliminates the error if that's any clue, although the version is still 1.21.6.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
 - host os: `Linux 5.4.0-120-generic, Ubuntu, 20.04.4 LTS (Focal Fossa), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - channels(ethanbro): `"home-manager"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Sorry for the false alarm here! The issue was that I was running python3.10 when numpy was failing! Running numpy inside python3.9 works :)


Add Rescue, split parameters and the sponge struct, and sharing some components

This PR is to the experimental repo.
It adds Rescue (untested) and separates the parameters from the sponge struct.
More updates are incoming:

tests with more decent parameters for one common curves
more tests on Rescue

One thing that pops up during this change:

Rescue and Poseidon share a lot of code in common---because they are merely different permutation, but the sponge structure is similar. We may extract more code from here.

You mentioned that the only difference between Rescue and Poseidon are their permutations. Do you see that the general structure will be similar for newer Sponges? Would it be worth just introducing a Permutation trait that we can simply swap out?

Good point. Reading Wikipedia, ideally (duplex) sponges would only differ in terms of the permutation function.
Let me cc @ValarDragon for some opinions. Basically, the implementations of Rescue and Poseidon share a lot of the code, and the only difference is in the permutations. So, we are thinking to structure the code in a way that avoids duplication. What do you think?

Good point. Reading Wikipedia, ideally (duplex) sponges would only differ in terms of the permutation function.
Let me cc @ValarDragon for some opinions. Basically, the implementations of Rescue and Poseidon share a lot of the code, and the only difference is in the permutations. So, we are thinking to structure the code in a way that avoids duplication. What do you think?

Yes and possibly allow less effort for implementing similar Sponges with the same structure in the future.

Sorry, somehow I missed this ping. I think the scaffolding we should do given our recent sponge conversations is to have a SpongeTrait, and then build out a trait where all you do is specify a permutation, and then it handles the rest


Write custom TXT record

Is there a way to specify the TXT records via config? So it is not a generated hash or something. I want to use static CNAME records to point to the acmedns temporary TXT records.
_acme-challenge CNAME my-specified-name.acme-dns.mydomain.com

I realized a workaround the other day - you can just manipulate the database (which is either sqlite or postgresql).


Remove datasets dependency

Proposal: Can we remove datasets from the list of requirements.txt?
As far as I can see, there is no dependency on it in bigbench, except for bigbench/benchmark_tasks/chess_state_tracking/scripts/requirements.txt, and those scripts don't even seem to rely on it as far as I can tell.
The datasets==1.17.0 version is interfering with trying to get bigbench into HF.
If datasets is needed in bigbench, can we avoid specifying the version to make it compatible with datasets importing bigbench?

I think we can remove the version number. I actually think we should more generally relax version numbers (https://github.com/google/BIG-bench/pull/705) so that BIG-bench plays better with other software projects. I understand that there are also risks associated with this though.
@ajslone might have some wisdom about the dangers of removing the version number.

I think limiting ourselves with next major version like in #705 is safer than just putting minimal version, at least for core dependencies (which is hard to judge for me, so I'd leave it to maintainers)

Yes, totally agree. I was doing some experimentation that really should have been done in a different branch.
I will revert it back to #705.
Thanks, and sorry for the confusion.


I want to ask question about NoWeb

Basically i have run WAHA on my system with Command
docker run -it --rm -p 3000:3000/tcp --name waha devlikeapro/waha
here it ren on WEBJS but i want to run it on NOWEB when i run using command
docker run -it -e "WHATSAPP_DEFAULT_ENGINE=NOWEB" devlikeapro/waha
then how to create session or send message

You need to combine all arguments in the command:
docker run -it --rm -p 3000:3000/tcp --name waha -e "WHATSAPP_DEFAULT_ENGINE=NOWEB" devlikeapro/waha

Here's full commands and docker compose "almost" ready for production:
https://waha.devlike.pro/docs/how-to/install/


Ft 74 Room authentication

Which Issue was this PR made for?

Closes #74

What is within the scope with this PR
What is NOT in the scope with this PR
Related Issue
Other sidenotes that reviewer should be aware of

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

Need to add notification for when password is incorrect.

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

[ ] fix test
[ ] don't allow empty password
[ ] update readme

don't allow empty password

I think password should be optional

Yeah I actually agree I'll just add "(optional)" in the label

Very weird. Running npx playwright test within /client works, but make test in the home directory doesn't work.
Not totally sure what's going.

Made password optional

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

net::ERR_CONNECTION_REFUSED

Socketio is failing to connect making the test fail just for make test (working for npx playwright test).
Any ideas? @Njima1572

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

net::ERR_CONNECTION_REFUSED

more specifically, xhr poll error
Socketio is failing to connect making the test fail just for make test (working for npx playwright test). Any ideas? @Njima1572
Thing I've tried:

upgrade both server and client socket.io's to latest versions
add {transports: ['websocket']} to io() parameter

Since I realized this bug wasn't caused by this pr, I'm commenting out the broken tests for now to be fixed in: #320

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com

AUTOMATED: Deployed to https://pr-312.dev.mochatto.com


SPOI-8561 Record reader example app

@amberarrow Could you please review this?

Note that this is dependent on https://github.com/apache/apex-malhar/pull/326 which is not yet merged. Thus, this PR is only for the review for now.

@amberarrow parent PR apache/apex-malhar#326 is merged now. This PR is for example app for record-reader. Could you please review this?

Please add a row to the table in the parent directory README.md with a brief description of what the example does (order is alphabetic).

Trimmed CustomerTxnData file
Added entry in the parent README.md

In the current implementation, output is written to the Console. So, we cannot monitor the output files directly. Are you suggesting to write to fileoutput rather than console? But, earlier in the JIRA discussion we decided for Console output to keep it simple.
Could you please suggest why checking the output is really important? Just checking if output files exists may not be sufficient if we are really focusing on validating the functionality. Adding validation logic to the example app would make it complex unnecessarily. Thus, IMO it should be OK to skip the check for output files.
Awaiting for your feedback on this.

@amberarrow Updated the PR to incorporate review comments.

It will be good to have the unit test verify the result. That will be necessary to automate testing of apps as part of certification.

@tweise Commit 1565003 does some verification in the unit test; were you looking for additional verification or just responding to the earlier question from Yogi ?

@amberarrow changed as per your comment.
@tweise Awaiting for your answer to the ram's question.

Rather than just counting, should the verification not also check that a particular record was correctly parsed?

@tweise In my understanding, intent of the example app is do demonstrate how to use a particular operator/feature in question.
We already have unit tests to verify the individual operators.
Intricacies like end to end verification of data will be part of certification. But, that can be done outside the app as well. Even if we decide to build the app for verification, that app will be part of QA and not the examples.
Increasing the complexity in the example app would make it difficult to understand. Hence, I was trying to keep the verification to minimal.
Awaiting for your feedback on this.

Examples not only illustrate the application code. Documentation and testing is equally if not more important. Users need to see and be easily able to adapt the recommended approach for testing their own app instead of "figure yourself". End to end data verification is IMO part of the package and cannot be thrown over the fence. Running the tests can be automated elsewhere.

@tweise Updated the PR to do the verification of results. Could you please review this?

The README file now seems out of sync with the code: it mentions "ToConsole" which no longer exists.
Also, could you remove the 2 comment lines, one with ToConsole and the other with TODO  in ApplicationTest.java ?
Rest looks good.

@amberarrow Updated the PR. Could you please review?


security/acme-client: certificate renewal fails

Hey,
Since 21.6.2017 I get the following error in my acme log (It should be obvious, but the host/domain names are sanitised):
[Sat Sep 2 00:00:01 CEST 2017] | 'subdomain.example.net'' is not a issued domain, skip.
[Sat Sep 2 00:00:01 CEST 2017] | Renew: 'subdomain.example.net''
[Sat Sep 2 00:00:01 CEST 2017] | DOMAIN_PATH='/var/etc/acme-client/home/subdomain.example.net''
[...]
[Fri Jul 21 00:00:01 CEST 2017] | 'subdomain.example.net' is not a issued domain, skip.
[Fri Jul 21 00:00:01 CEST 2017] | Renew: 'subdomain.example.net'
[Fri Jul 21 00:00:01 CEST 2017] | DOMAIN_PATH='/var/etc/acme-client/home/subdomain.example.net'

These are the corresponding lines from system log:
Sep 2 00:00:05 | opnsense:  /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php:  AcmeClient: unable to import certificate: subdomain.example.net
Sep 2 00:00:05 | opnsense:  /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php:  AcmeClient: unable to import certificate, file not found:  /var/etc/acme-client/certs/58d16bf8caff73.73035884/cert.pem
Sep 2 00:00:05 | opnsense:  /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php:  AcmeClient: issued/renewed certificate: subdomain.example.net
Sep 2 00:00:01 | configd.py: [5d07fe8e-f899-468f-a450-cfea2c575859] Reloading filter
Sep 2 00:00:00 | configd.py: [60e1d13e-e6ff-4643-a99a-f451b13e9ba3] cronjob running to sign or renew certificates

And this is from the crash report:
[01-Sep-2017 18:04:16 Europe/Berlin] PHP Warning:  cert_action_validator(): Node no longer exists in /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php on line 122
[02-Sep-2017 00:00:05 Europe/Berlin] PHP Warning:  cert_action_validator(): Node no longer exists in /usr/local/opnsense/scripts/OPNsense/AcmeClient/certhelper.php on line 122

The cron job was working before. Last successful run was on 20.5.2017, which is the issue date of my now expired certificate. I'll have a cron job for nightly updates which makes me sure it was working ok on OPNsense 17.1.5.
I assume some change between 20.5 and 20.6 must have broken my cron job. It could have been an update (OPNsense 17.1.6-17.1.8) or some changed configuration. Unfortunately my configuration history (diag_confbak.php) ends mid August. But I'm quite sure to not have altered the Let's encrypt configuration.
Common name: subdomain.example.net
Multi-Domain (SAN): host.subdomain.example.net
Last Acme Status: internal error
Validation method is http_portfwd_on_wan
So what comes to my mind, that might be special:

I use a SAN entry, which has one more level than the domain name
I have dynamic IPv4 and IPv6 addresses
I use a DynDNS hostname, but my domain provider only supports IPv4

@Woi Thanks for your report! I'm not aware of any such issue and can't reproduce it.
Can you update to the current release of OPNsense, 17.7.1?
Can you try to manually renew the certificate from the WebUI?

Thanks for the plugin and your support :)
I'm running OPNsense 17.7.1_2-amd64. It also fails when triggered from the WebUI.
Just for clarification: The problem exists since 21.6 and reoccurs every night. Last successful renewal was on  20/21.5. Between 20/21.5 and 21.6 no renewal was triggered.

According to the acme.sh source, the error "is not a issued domain" is displayed if acme.sh can't find the (previously created) configuration file for this domain.
@Woi Have you changed the domain name? Or did you reinstall OPNsense? In any case the file seems to be lost.
Can you try to remove the Certificate from the LE GUI and re-create it? This way it should not be handled as "renewal" but instead acme.sh would try to recreate everything. (Note that the "old" certificate will remain in OPNsense's Certificate Managed and not be deleted.)

I followed your directions and deleted and recreated the certificate. It was a bit rough, but now I have a working certificate again :)
Regarding the root cause of my problem: You made a very good guess :) I replaced my Alix-Board with an APU2 at the time in question. I used /diag_backup.php to backup and restore the configuration from a file. So backup and/or restore missed a some bits of ACME configuration.

I used /diag_backup.php to backup and restore the configuration from a file. So it looks like backup and/or restore missed some bits of ACME configuration.

I'll try to fix this in the next release.

Nice. Give me a shout if you like me to test your patch.


I would like to ask, what is the swr cache strategy and where is the default cache? Is it in memory?

Bug report
Description / Observed Behavior
What kind of issues did you encounter with SWR?
Expected Behavior
How did you expect SWR to behave here?
Repro Steps / Code Example
Or share your code snippet or a CodeSandbox link is also appreciated!
Additional Context
SWR version.
Add any other context about the problem here.

Hello, I just don't know where the data after the interface request is cached
At present, after the interface request, the content display in the cache will be obtained first, but it is not clear where the data is cached.

How to achieve the above documentation description? Where exactly is it stored? I can not find


[#137] Fix jump to future issue

Coverage increased (+0.2%) to 81.321% when pulling dc7d562fa3ec06f245086f8d0974dbaa0c84137e on xuziheng1002:master into 40591fc6ec7793b76e42842cde8c6292f6f623a8 on javrasya:master.

Coverage increased (+0.2%) to 81.321% when pulling dc7d562fa3ec06f245086f8d0974dbaa0c84137e on xuziheng1002:master into 40591fc6ec7793b76e42842cde8c6292f6f623a8 on javrasya:master.

Thanks for the PR @xuziheng1002, I dropped a comment on a line. Apart from that, it looks good and it is ready to be merged to master


ship stopped writing new blocks

eosio-2.0.7, Ubuntu 18.04. The node has resynched Telos from genesis. All of a sudden, it stopped writing state history logs, without any messages related to the moment when it stopped (log level is set to error).
config.ini (producer_api_plugin was added several hours after this happened):
chain-state-db-size-mb = 65536
reversible-blocks-db-size-mb = 2048

wasm-runtime = eos-vm-jit
eos-vm-oc-enable = true

p2p-accept-transactions = false
api-accept-transactions = false

http-server-address = <IP_ADDRESS>:8802
p2p-listen-endpoint = <IP_ADDRESS>:9802
p2p-server-address = :9857

access-control-allow-origin = *

#verbose-http-errors = true
contracts-console = true

max-clients = 100

plugin = eosio::chain_plugin
plugin = eosio::chain_api_plugin
plugin = eosio::db_size_api_plugin

plugin = eosio::producer_api_plugin

plugin = eosio::state_history_plugin
trace-history = true
chain-state-history = true
trace-history-debug-mode = true
state-history-endpoint = <IP_ADDRESS>:8082

sync-fetch-span = 10

p2p-peer-address = p2p.telosarabia.net:9876
p2p-peer-address = telos.cryptolions.io:9871
p2p-peer-address = telos.eosdublin.io:9876

root@eosio:/srv/telos# ls -al data/state-history/
total 291419499
drwxr-xr-x 2 root root            6 Sep  6 13:31 .
drwxr-xr-x 6 root root            6 Sep  6 13:31 ..
-rw-r--r-- 1 root root    831008728 Sep  9 08:12 chain_state_history.index
-rw-r--r-- 1 root root<PHONE_NUMBER>50 Sep  9 08:12 chain_state_history.log
-rw-r--r-- 1 root root    831008728 Sep  9 08:12 trace_history.index
-rw-r--r-- 1 root root<PHONE_NUMBER>38 Sep  9 08:12 trace_history.log
root@eosio:/srv/telos# ls -al data/blocks/
total 47089027
drwxr-xr-x 3 root root            5 Sep  6 13:31 .
drwxr-xr-x 6 root root            6 Sep  6 13:31 ..
-rw-r--r-- 1 root root    877516224 Sep 10 07:29 blocks.index
-rw-r--r-- 1 root root<PHONE_NUMBER>11 Sep 10 07:29 blocks.log
drwxr-xr-x 2 root root            3 Sep  6 13:31 reversible

After restarting nodeos, it prints the blocks range in state history, and doesn't collect any new data. The websocket is responding, but obviously not delivering any traces.
In attached log, I restarted nodeos with default logging at Sep 10 07:32:54.It started printing "missed a block in trace_history.log"
telos.nodeos.log

the node went on with the head block, so it's difficult to reproduce or test a bugfix. But what it should've done is stop and not continue after there was a failure.

Have you been able to do this successfully before?  Just trying to determine if something may have changed recently that caused this.

no, it's the first time that I see the state history data corrupted. But what is a systematic problem, is that nodeos prints a warning and goes ahead, instead of aborting if the data is corrupted.

Just experienced it with 2.0.6 on WAX on two independent servers within a couple of days. It just stops updating state history silently. The network has been experiencing intensive forks. This behavior is quite random. I'm maintaining 4 ship servers on WAX, and only one falls out at a time.

It looks like it's related to increased forks frequency, so #10080 might be related

We have seen this several times on EOS recently where we get this warning with every block:
missed a block in chain_state_history.log
    {"name":"chain_state_history"}
    nodeos  state_history_log.hpp:92 write_entry

And we have to stop the node and restore from backup to fix it.

in my case, logging was limited to error level, so no logs here

We have seen this several times on EOS recently where we get this warning with every block:

Do you have a full log available. Interested in if there was a warn/error before this started warning on every block. Once in this state it really can't recover without a restore from backup.

in my case, logging was limited to error level, so no logs here

Would recommend you run with at least warn level logging.

We have seen this several times on EOS recently where we get this warning with every block:

Do you have a full log available. Interested in if there was a warn/error before this started warning on every block. Once in this state it really can't recover without a restore from backup.

Looking closer, it actually happened with a restart (we do auto stop + zfs snap + start). On stop it put this in the log:
corrupted size vs. prev_size
And then when it started it had the missed block in state history issue.

see "crash on exit with error "corrupted size vs. prev_size"  https://github.com/EOSIO/eos/issues/8450

see "crash on exit with error "corrupted size vs. prev_size" #8450

Yep, I thought that one was fixed long ago but doesn't look like it.

whatever the cause is, nodeos should stop if it cannot keep writing the ship data. Currently this failure is difficult to detect because it keeps sending empty ship data via websicket.

Had a WAX SHiP node start missing blocks in the SHiP logs and see the following just before it started missing blocks:
fc: exeption: 8 out_of_range_exception: Out of Range write datastream of length 11327 over by -51
{"method:"::"write", "len":"11327","over":"-51"}
nodeos datastream.cpp:6 throw_datastream_range_error

Had this error occurring again few days ago, and that was the only node where I forgot to put ``read-mode=head`.  It was isolated from speculative transactions though:
p2p-accept-transactions = false
api-accept-transactions = false

Could also be related to https://github.com/EOSIO/eos/issues/9972

One more occasion, and this time it's not at head block: I was resynching a Telos ship node from genesis, and it stopped about halfway through the history (last block in blocks log: 103875765, current heads block is above 180M)

attached, is the log from the Telos node (log level is set to error). The node started from near the genesis on Nov 12 , then stopped on Nov 14 12:06:20.   later on, I tried to start it on Nov 17.
telos_ship.log

the error is quite definitely related to how busy the storage is for ship files. Seems like the write operation times out too early.


Test cluster provisioning on Azure - Test Release 1.4

For more details see instructions posted in #1768.
Operating Systems to be tested:

[x] Ubuntu 20.04
[x] CentOS 7

Supported Kubernetes versions (choose only one operating system -- for example, you can test 1.23.3 on all operating systems, and then test other versions only on Ubuntu):

[x] 1.23.3
[x] 1.22.6
[x] 1.21.9
[x] 1.20.15

External cloud provider testing (choose only one operating system; preferably test on each supported Kubernetes version):

[x] Create a cluster with .cloudProvider.external enabled

Make sure to enable the default-storage-class addon (see the Epic for more details)

Upgrades:

[x] 1.22.6 -> 1.23.3
[x] 1.21.9 -> 1.22.6
[x] 1.20.15 -> 1.21.9

For each test, you should:

Create a LoadBalancer Service and point to some test pod (e.g. Nginx pod). The LB should be reachable and serve the content as expected
Create an AzureDisk PV and attach it to the pod

pv are bit slow to attach to new node compare to other cloud providers but works as expected


Kubedb CRD wont be installed

We have RKE provisioned k8s cluster.
Our k8s is on version 1.12.4
Maybe you could help us? Or have any idea?
It just newly provisioned cluster, there was nothing deployed before.
kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"f49fa022dbe63faafd0da106ef7e05a29721d3f1", GitTreeState:"clean", BuildDate:"2018-12-14T06:59:37Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
What we get on deploy:
curl -fsSL https://raw.githubusercontent.com/kubedb/cli/0.9.0/hack/deploy/kubedb.sh | bash
checking kubeconfig context
k8s-test-2
Downloading onessl ...
checking whether extended apiserver feature is enabled
KUBEDB_BYPASS_VALIDATING_WEBHOOK_XRAY=false
KUBEDB_CATALOG=all
KUBEDB_DOCKER_REGISTRY=kubedb
KUBEDB_ENABLE_ANALYTICS=true
KUBEDB_ENABLE_APISERVER=true
KUBEDB_ENABLE_MUTATING_WEBHOOK=true
KUBEDB_ENABLE_RBAC=true
KUBEDB_ENABLE_STATUS_SUBRESOURCE=true
KUBEDB_ENABLE_VALIDATING_WEBHOOK=true
KUBEDB_IMAGE_PULL_POLICY=IfNotPresent
KUBEDB_IMAGE_PULL_SECRET=
KUBEDB_NAMESPACE=kube-system
KUBEDB_OPERATOR_NAME=operator
KUBEDB_OPERATOR_TAG=0.9.0
KUBEDB_PURGE=0
KUBEDB_RUN_ON_MASTER=0
KUBEDB_SERVICE_ACCOUNT=kubedb-operator
KUBEDB_UNINSTALL=0
KUBEDB_USE_KUBEAPISERVER_FQDN_FOR_AKS=true
KUBEDB_WEBHOOK_SIDE_EFFECTS=sideEffects: None
Wrote ca certificates in  /root/k8s-test-2
Wrote server certificates in  /root/k8s-test-2
deployment.apps/kubedb-operator created
secret/kubedb-server-cert created
service/kubedb-operator created
apiservice.apiregistration.k8s.io/v1alpha1.validators.kubedb.com created
apiservice.apiregistration.k8s.io/v1alpha1.mutators.kubedb.com created
serviceaccount/kubedb-operator created
clusterrole.rbac.authorization.k8s.io/kubedb-operator reconciled
clusterrolebinding.rbac.authorization.k8s.io/kubedb-operator reconciled
rolebinding.rbac.authorization.k8s.io/kubedb-server-extension-server-authentication-reader reconciled
clusterrolebinding.rbac.authorization.k8s.io/kubedb-server-auth-delegator reconciled
clusterrole.rbac.authorization.k8s.io/kubedb:core:admin reconciled
clusterrole.rbac.authorization.k8s.io/kubedb:core:edit reconciled
clusterrole.rbac.authorization.k8s.io/kubedb:core:view reconciled
clusterrole.rbac.authorization.k8s.io/appscode:appcatalog:admin reconciled
clusterrole.rbac.authorization.k8s.io/appscode:appcatalog:view reconciled
validatingwebhookconfiguration.admissionregistration.k8s.io/validators.kubedb.com created
mutatingwebhookconfiguration.admissionregistration.k8s.io/mutators.kubedb.com created
waiting until kubedb operator deployment is ready
waiting until kubedb apiservice is available
waiting until kubedb crds are ready
installing KubeDB Elasticsearch catalog
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"
unable to recognize "STDIN": no matches for kind "ElasticsearchVersion" in version "catalog.kubedb.com/v1alpha1"

Can you provide the log of kubedb-operator deployment pod?

Hi
We have upgraded all components and started to use Centos 7 as OS. After that we have had no problems.
Thank you for that kind of a nice solution :D


Undefined offset 0

For some reason everytime i load on to my website i am given these errors:

the file 1.php is my index.php.
here are my lines of code:

Someone please help me

It looks like you are trying to include/require userInfo.php before the user is logged in.

It looks like you are trying to include/require userInfo.php before the user is logged in.
Edit:
Also on another note, It seems you aren't loading steamauth.php at the top of your file, otherwise you shouldn't be getting that first error.

How would i go about fixing that in the code?

Check if the user is logged in before including the file.
Checkout the demo.php file for more info.

Check if the user is logged in before including the file.
Checkout the demo.php file for more info.

I had done this, it still doesnt work.

Firstly, you need to move your DOCTYPE to after the steamauth.php require
<?php
require ('steamauth/steamauth.php');
?>
<!DOCTYPE html>

and you need to check if the user is logged in before you try and get their info:
if(!isset($_SESSION['steamid']))
    require ('steamauth/userInfo.php');


Hide avatar for centered titles on small phones

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes
This is a small bug fix for "small" phones in landscape mode where we always emulate a system-style title view. Specifically, we don't want to show the avatar in this case. See verification images.
Binary change
Total increase: 2,912 bytes
Total decrease: 0 bytes

File
Before
After
Delta

Total
31,694,192 bytes
31,697,104 bytes
⚠ 2,912 bytes

 Full breakdown

File
Before
After
Delta

AvatarTitleView.o
196,304 bytes
197,912 bytes
⚠ 1,608 bytes

__.SYMDEF
4,768,584 bytes
4,769,888 bytes
⚠ 1,304 bytes

Verification

Visual Verification
Screenshots taken on an iPhone 14 Pro simulator.

Before
After

Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

Do we show an Avatar for centered titles on large iPhones or iPads? If not, we should update the title to not include "on small phones". The code looks like it's just checking leading vs centered, and nothing about phones.

This is only a problem when we the system wants to draw a 32px navigation bar, that is, on a small phone in landscape mode (or more precisely, both compact horizontal and vertical size classes).


 This seems to be after a recent change.
This is what it looks like:

Here's an affected link.
Here's the gist that provides the markdown

@kusma which browser do you use?
I see your CLA (in Chrome, Firefox and Safari) as follows:

Still, don't like the added anchor links, but it is an old issue. I'll try to find a quick fix for the link icons.
Sorry, but I could not reproduce your view.

@KharitonOff: I experienced this using Chrome. However, it seems the problem has been resolved now. Perhaps it was something in github's end?


confuse menu

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.69

Steps to Reproduce:
https://code.visualstudio.com/updates/v1_69#_minimap-context-menu
I think the menu is making users confuse

'Size' users will usually think of as width

hard to unstandard what is scale about minimap

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.69.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


dapr init -k --dev command needs more documentation

To make setting up a development environment on Kubernetes easier, the dapr init -k command now supports a --dev option which deploy Redis and Zipkin containers to Kubernetes identical to the self-hosted mode.

This Initialize Dapr in your local environment overview should be updated to make it clear that this option is now available for K8s. https://v1-12.docs.dapr.io/getting-started/install-dapr-selfhost/. Either create a new topic or maybe enhance this one to add Kubernetes
Example needed for dapr init -k --dev in the examples section
Add an example here  https://v1-12.docs.dapr.io/reference/cli/dapr-init/#kubernetes-environment

/assign

@mikeee - Will you be doing a PR for this?

I'll pick this up today.


colmena build fails when meta.nixpkgs = import-from-derivation ...

Hi, I'm using import-from-derivation to obtain my nixpkgs copy (to be able to inject version info from git into .version-suffix -- I haven't switched to flakes) for meta.nixpkgs = ..., in hive.nix.
However that breaks colmena build:
$ colmena build --show-trace
[INFO ] Enumerating nodes...
trace:  nixpkgsPinnedSrc: /nix/store/n31jsavkyn5ykkqmrf77140lqbfgz90n-nixpkgs-source
error: while evaluating the attribute 'meta.machinesFile' at /tmp/.tmptFR5Yd:474:3:
while evaluating the attribute 'meta' at /tmp/.tmptFR5Yd:294:7:
while evaluating 'mkNixpkgs' at /tmp/.tmptFR5Yd:298:27, called from /tmp/.tmptFR5Yd:339:6:
while evaluating the attribute 'nixpkgs' at /home/bf/colmena-issue-repro/hive.nix:3:5:
cannot import '/nix/store/n31jsavkyn5ykkqmrf77140lqbfgz90n-nixpkgs-source', since path '/nix/store/ln3aj7prhxb8y9yim5fg25lrslgyp9yv-nixpkgs-source.drv' is not valid, at /home/bf/colmena-issue-repro/hive.nix:25:10
[ERROR] -----
[ERROR] Operation failed with error: Nix exited with error code: 1

But if I take the Nix expressions from colmena and build it with nix-build (I hope I did it right), then it works:
$ nix-build ./build-with-colmena.nix
trace:  nixpkgsPinnedSrc: /nix/store/n31jsavkyn5ykkqmrf77140lqbfgz90n-nixpkgs-source
/nix/store/hckmh391x4frcib469jvfrgwlbk6pprz-colmena-hive

And since the above command successfully realized the missing .drv file from the error above, subsequent colmena build now works:
$ colmena build --show-trace
[INFO ] Enumerating nodes...
trace:  nixpkgsPinnedSrc: /nix/store/n31jsavkyn5ykkqmrf77140lqbfgz90n-nixpkgs-source
trace:  nixpkgsPinnedSrc: /nix/store/n31jsavkyn5ykkqmrf77140lqbfgz90n-nixpkgs-source
[INFO ] Selected all 1 nodes.
host1 ✅ 0s Built "/nix/store/qriwcxwmd2pazsj271y90xg789by036l-nixos-system-nixos-21.05.git.c4cbbed"

I have tried a bit of debugging in colmena (patching the source) but haven't found the root cause for this difference. Why does colmena build not work with IFD here, when the underlying Nix expressions do? Does it pass some option to nix-instantiate that disables IFD? Where? How to disable it?
The files referenced above are here:

hive.nix
{
  meta = {
    nixpkgs =
      let
        fetchGitWithVersionSuffix = { url, ref, rev }:
          let
            base = builtins.fetchGit { inherit url ref rev; };
            basePkgs = import base { config = {}; overlays = []; };
          in
            basePkgs.runCommandLocal "nixpkgs-source" { } ''
              mkdir -p "$out"
              (shopt -s dotglob; cp -r "${base}/"* "$out")
              echo ".git.${base.shortRev}" > "$out/.version-suffix"
            '';
        # Using builtins.fetchGit works, fetchGitWithVersionSuffix only works
        # with `nix-build ./build-with-colmena.nix`, not with `colmena build`.
        nixpkgsPinnedSrc = fetchGitWithVersionSuffix {
        #nixpkgsPinnedSrc = builtins.fetchGit {
          url = "https://github.com/NixOS/nixpkgs.git";
          ref = "refs/heads/release-21.05";
          rev = "c4cbbed186cc00066fd1998b5d915fe37f197135";
        };
        pinnedPkgs = builtins.trace" nixpkgsPinnedSrc: ${nixpkgsPinnedSrc}" (
                     #builtins.trace" nixpkgsPinnedSrc.drv: ${nixpkgsPinnedSrc.drvPath}"
        (import nixpkgsPinnedSrc { config = {}; overlays = []; }));
      in
        pinnedPkgs;
  };

  host1 =
    { pkgs, ... }:
    {
      fileSystems."/".device = "/dev/sda";
      boot.loader.grub.devices = [ "/dev/sda" ];
    };
}

build-with-colmena.nix
let
  colmenaSrc = builtins.fetchGit {
    url = "https://github.com/zhaofengli/colmena";
    ref = "refs/heads/release-0.2.x";
    rev = "e95dc850f3e715219cf9e0651cd53f63b79e0e11";
  };
  hiveEvaluated = import "${colmenaSrc}/src/nix/eval.nix" {
    rawHive = import ./hive.nix;
  };
in
  hiveEvaluated

Tip: after one successful build, remove the fetched nixpkgs source (and .drv) to be able to reproduce the colmena build issue: nix-store --delete /nix/store/n31jsavkyn5ykkqmrf77140lqbfgz90n-nixpkgs-source /nix/store/ln3aj7prhxb8y9yim5fg25lrslgyp9yv-nixpkgs-source.drv.

First of all, I think this specific usecase can be done without IFD:
let
  nixpkgs = builtins.fetchGit {
    url = "https://github.com/NixOS/nixpkgs.git";
    ref = "refs/heads/release-21.05";
    rev = "c4cbbed186cc00066fd1998b5d915fe37f197135";
  };
in {
  meta = {
    nixpkgs = import nixpkgs {};
  };

  defaults = {
    system.nixos.version = "21.05-${nixpkgs.shortRev}";
  };

  host1 =
    { pkgs, ... }:
    {
      fileSystems."/".device = "/dev/sda";
      boot.loader.grub.devices = [ "/dev/sda" ];
    };
}

IFD doesn't work in this case because Colmena is using nix-instantiate --eval in read-only mode. A simpler way to reproduce is:
# simple-ifd.nix
let
  nixpkgs = builtins.fetchGit {
    url = "https://github.com/NixOS/nixpkgs.git";
    ref = "refs/heads/release-21.05";
    rev = "c4cbbed186cc00066fd1998b5d915fe37f197135";
  };
  pkgs = import nixpkgs {};
  drv = pkgs.writeText "some.nix" "123";
in import drv

This fails:
nix-instantiate --eval --json simple-ifd.nix

However, this succeeds:
nix-instantiate --eval --json --read-write-mode simple-ifd.nix

What do other deployment tools do? From a cursory look, NixOps always appends --read-write-mode by default (which came from https://github.com/NixOS/nixops/pull/279), and morph doesn't do that.
I currently can't think of any cases where we would not want store paths to be built when we do an --eval, so let's add this so IFD works. For colmena eval, this can also make things less confusing because currently store paths returned in the default eval mode are not valid.

Thank you!


resumptionToken link for other verbs; oai stylesheet

The "Show More" link in oai stylesheet has its verb fixed to "ListSets". When you are listing records, the link should have the verb set to "ListRecords" and similarly when listing identifiers

Hi, thanks for this bug fix! We need a corresponding JIRA issue to be created for this bug, so we have a record of why code was changed, and we can plan for when to accept this PR. You may create a new ticket here: https://jira.duraspace.org/secure/CreateIssue!default.jspa Ideally you would also either amend your commit to reference this ticket, or (much easier) just change your branch name to reference the ticket. That helps maintain the link between JIRA and GitHub.

Well, created an issue https://jira.duraspace.org/browse/DS-2412, created a new branch called DS-2412 and made a new pull request #839 ; hope it's better now...


Order of operations - documentation

Hi,
Is it possible to add a section documenting order of operations?
For example - is deduplication carried out before or after filtering\trimming?
Thank you

See also #411

Still an open question, we would be happy for an answer or documentation. thank you


[Splendor] Remove bottom most display of active player

Before removing this, make sure that it is possible to discard money using the topmost player view.


animated download button added

GSSOC' 23
#379

@hashfx
Looking forward to more contributions from you. 🧑💻

Thank you so much for your contribution.🌟
Make sure to ⭐ and follow me.

I would love to connect with you all ❤

https://www.linkedin.com/in/om-gawande/


FCS alignment: propagate specifier ranges in CheckFormatString.fs

This is part of a series of alignment PRs related to step (2) of the planning note https://github.com/Microsoft/visualfsharp/issues/589.
This manually incorporates the FCS change to report specifier ranges in CheckFormatString.fs.   The collected ranges are currently ignored by the Visual F# Tools but are used by FCS and the Visual F# Power Tools to colorize format strings.  Collecting the ranges is harmless.
Incorporating this change will make it easier to align FCS and Visual F# Tools in the future and to incorporate FCS and Visual F# Power Tools functionality into the Visual F# Tools.

Merged, thanks

Closing in favour of https://github.com/Microsoft/visualfsharp/pull/679


Fix eigen quaternion coeffs problems

Eigen::Quaternion .coeffs() returns the coefficients in a different order to the order that the constructor expects.
This PR looks to find and fix all the places where I screwed that up.

I agree. Both of those are definitely nicer wrapped in a temporary vector. I also noticed another simplification I could make, which I added in a follow up commit.

@TrentHouliston can I grab a review pls :pleading_face:


import/export issue

i wrote a test case to experiment memory import. (see below)
my intention is to share a single "mem" instance. i believe it's the spec-wise correct behavior.
it works as i expected for other engines. (i tested with the reference interpreter, wabt, wasmer, wasmtime, toywasm)
unfortunately, it didn't work for wamr. it seems wamr creates two instances for "mem".
is it an intended divergence from the spec? i can understand both behaviors can have valid use cases.
while i can "fix" sub_module_instantiate to use shared instances for dependencies,
i feel it actually needs a bigger surgery to fix properly.
IMO, import/export processing should be done at instance level, not module level.
how do you think?
(module (memory (export "m1") 1))

(register "mem")

(module
(memory (import "mem" "m1") 0)
(func (export "inc") (param $i i32) (i32.store (local.get $i) (i32.add (i32.const 1) (i32.load (local.get $i)))))
)

(register "sub")

(module
(memory (import "mem" "m1") 0)
(func (export "inc") (import "sub" "inc") (param $i i32))
(func (export "get") (param $i i32) (result i32) (i32.load (local.get $i)))
)

(assert_return (invoke "get" (i32.const 0)) (i32.const 0))
(assert_return (invoke "inc" (i32.const 0)))
(assert_return (invoke "get" (i32.const 0)) (i32.const 1))
(assert_return (invoke "inc" (i32.const 0)))
(assert_return (invoke "get" (i32.const 0)) (i32.const 2))

YES, it is a design choice about whehter one sub-module should have multiple instances if it is imported multiple times.
In above case,  module sum and module main(I am going to call the third module "main") create their own module mem instance and create two linear memories. So both functions inc() and get() actually operate differnt linear memories.

inc() writes the No.2 linear memory via sub.inc() while get() reads the No.1 linear memory.
The most reason of this choice is we want keep a private memory for every module. I guess there are some stories how an unsafe 3rd library successl peek user data inlight us.
WAMR is using a loading-time-link mechanism. It is similar with the process of ld searchs and loads all shared libraries used by a program.  It is an old fashioned way and looks reasonable if there are only .wasm files until host-made runtime objects involved.  wasm-c-api provides another way to link at instantiation wasm_instance_new().  Lucky, all those divergence will be merged in the "component model feature".

WAMR is using a loading-time-link mechanism. It is similar with the process of ld searchs and loads all shared libraries used by a program. It is an old fashioned way and looks reasonable if there are only .wasm files until host-made runtime objects involved. wasm-c-api provides another way to link at instantiation wasm_instance_new().

i haven't noticed wamr has a separate link logic for wasm-c-api. thank you.
memory kind is not implemented there though.

Lucky, all those divergence will be merged in the "component model feature".

is there anyone working on it for wamr?

is there anyone working on it for warm?

not for now.

WAMR is using a loading-time-link mechanism. It is similar with the process of ld searchs and loads all shared libraries used by a program. It is an old fashioned way and looks reasonable if there are only .wasm files until host-made runtime objects involved. wasm-c-api provides another way to link at instantiation wasm_instance_new().

i haven't noticed wamr has a separate link logic for wasm-c-api. thank you. memory kind is not implemented there though.

i looked at the wasm-c-api implementation a bit.

only funcs and globals are implemented.
funcs is implemented only for host functions.
globals are not shared among instances. instead, a separate global is created in importing instance.

Yes. WAMR tends to only link with functions now. And we may reconsider the design during implementing the Component Module proposal.
https://github.com/bytecodealliance/wasm-micro-runtime/issues/1168

The most reason of this choice is we want keep a private memory for every module. I guess there are some stories how an unsafe 3rd library successl peek user data inlight us.

in that case, it's better to make the request fail explicitly, rather than behaving in an incompatible way silently.

i want to use instantiate-time linking for my application.
do you think it makes sense to introduce a WAMR_BUILD_xxx option for this?


possible plotting error

Fix possible plotting error in class posteriorPredictionPlot
Point estimate seems to be inconsistent with 95% credible region plots when plotting with some datasets.

This is not actually a bug, it's just a by-product of the way how I am implementing it.
Even so, it's possibly not the best way as it looks weird and wrong.

Solution
I think the best solution is to simply plot a random subset of the samples, as below.


Add examples that can be used when building to actually verify if there are breaking changes

Examples will be used for testing SDK etc.

@craicoverflow Java and JS have those in very minimal level - Just doing list on resource

Done by @craicoverflow

If you think about it, these examples will give us a false sense of whether there are breaking changes, as the examples only test one or two methods out of potentially hundreds.

Yes.. That is minimum we have. There is separate issue for testing all API:
https://github.com/redhat-developer/app-services-sdk-go/issues/128


Support set sidebar_action.open_at_install option

Feature Request
With firefox add-on, it will open sidebar after add-on installed by default, how can I set sidebar_action.open_at_install option?
Is your feature request related to a bug?
N/A
What are the alternatives?
N/A
But I think WXT can provide a hook to modify manifest.json? for example, postManifest to modify the json object?

Looks like I have a TODO for this: https://github.com/wxt-dev/wxt/blob/ea0e40c269c8100e5ee2cb9ed92b833ec7b738ad/src/core/utils/manifest.ts#L333-L337
You can modify the manifest in the "build:manifestGenerated" hook for now. https://wxt.dev/api/wxt/interfaces/WxtHooks.html#build-manifestgenerated


merge package from arlac77/npm-package-template-esm-only

.travis.yml

chore(travis): add node versions -10,-11,-12
chore(travis): add master to branches.only
chore(travis): add /^greenkeeper/.*$/ to branches.only

Codecov Report

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

@@           Coverage Diff           @@
##           master     #545   +/-   ##
=======================================
  Coverage   75.94%   75.94%
=======================================
  Files           2        2
  Lines         474      474
=======================================
  Hits          360      360
  Misses        114      114

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 291c7d7...71c2a40. Read the comment docs.

Coverage remained the same at 76.225% when pulling 71c2a40abd2d3a6fb014e94d5b4876d698ad39ae on npm-template-sync-1 into 291c7d7571263fd182cc5f5a45f20e8e778aed4a on master.

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New package for yubikey-manager-qt

Motivation for this change
I own a few Yubikeys, USB keys for FIDO2 U2F auth. There is a new graphical  manager appliation based on Qt5 (similar to yubikey-manager-neo) from Yubico.
This is my first try writing a Nix expression for a new package, a probably made some mistakes. Please advice.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-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)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

...and @delroth was slightly faster than me :sweat_smile:

@Ma27 and @delroth thank you so much! I (hopefully) fixed all the issues you mentioned and pushed a fixup commit. I'll squash the last two commits on your mark.

Thanks a lot for stepping through the feedback. Although the program starts for me, it doesn't detect a YubiKey for me (yubikey-personalization-gui is installed in my nixos-config and detects it). Am I missing any additional udev rules? In that case we should document this i.e. in doc/package-notes.xml.

Thanks a lot for stepping through the feedback. Although the program starts for me, it doesn't detect a YubiKey for me (yubikey-personalization-gui is installed in my nixos-config and detects it). Am I missing any additional udev rules? In that case we should document this i.e. in doc/package-notes.xml.

I also had a hard time to figure this out...
You need to have the pcscd service (from pcsclite) configured for the program to work. (services.systemd.pcslite.enabled = true; if I remember correctly -- I am not at home right now)
And you need the udev rules from libu2f-host enabled for Firefox to recognize the stick for authentication. (`services.udev.packages = [ libu2f-hosts ];')

The service you're reffering to is called pcscd. With it enabled the GUI seems to work :+1:

Works here too, thanks!

I pushed a second commit onto your branch (that can be easily removed if needed) that does some minor cleanup as explained in the commit message. If the commit is fine for you and with it the package remains functional for you, I'd approve and merge :)

@Ma27 LGTM, and still works for me, thank you!

@avdv thanks!


Update contributing

Motivation and context

Updated installation documentation

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage remained the same at 65.365% when pulling 591fa2030c8ab7b843640c5a77fb4ef0e72a572a on zm/update-contributing into 5d0963934f1ced90716b6eb4270a9513b6d1c78b on develop.


Option to show number of indows on the workspace

This seems probably like a strange request, but some workspace/app combinations work better in floating mode. However in those cases it would be nice to know of windows hidden behind others. Would this be easy to implement?
Using custom in combination with swaymsg -t get_tree | jq somefilter seems somewhat wastefull

I was able to achieve something similar for Hyprland workspaces with a custom module that listens to events - documentation here:

https://wiki.hyprland.org/IPC/

For example, in ~/.config/waybar/scripts/hyprland_clients.sh:
#!/bin/sh

: "${XDG_RUNTIME_DIR:?Environment variable XDG_RUNTIME_DIR not set}"
: "${HYPRLAND_INSTANCE_SIGNATURE:?Environment variable HYPRLAND_INSTANCE_SIGNATURE not set}"

handle() {
  case "$1" in
    workspace* | focusedmon* | openwindow* | closewindow* | movewindow*)
      update_active_clients
    ;;
  esac
}

update_active_clients() {
  active_clients=$(hyprctl activeworkspace -j | jq -r .windows)
  echo "$active_clients"
}

# Initial update
update_active_clients

# Listen to events and handle them
socat -U - UNIX-CONNECT:"$XDG_RUNTIME_DIR/hypr/$HYPRLAND_INSTANCE_SIGNATURE/.socket2.sock" | while IFS= read -r line; do
  handle "$line"
done

and then in  ~/.config/waybar/config.jsonc:
    // ...

    "modules-left": [
        "custom/hyprland_clients",
        "hyprland/workspaces"
    ],

    // ...

    "custom/hyprland_clients": {
        "exec": "~/.config/waybar/scripts/hyprland_clients.sh",
        "format": "[{}]"
    },

    // ...


Refresh README

[x] - specify it's an R package
[x] - Check the nested directory issue for downloading
[x] - clarify download instructions - highlight that you must follow them precisely
[x] - Specify whether there are any other functions in the package
[x] - add more examples
[ ] - explain how the function works

I'm inclined to cover the last bullet point with more in-depth documentation for the specific function (rather than in the README)


"session timed out" login dialog needs to works with MFA

We need to ensure that the login popup you get when you've logged out due to inactivity still works with MFA.
You can reproduce by logging out in a new tab then clicking on a page in the site tree.
Notes:

Requires the MFA modal or Sudo mode first

@silverstripeux can we please have a chat and talk this one out? Would we assume password and/or MFA is required here?

From the planning meeting it was discussed that requiring password and MFA to reactivate the session after session timeout might be a little complicated to do, as in addition to entering the password, the user would be taken to a new page and required to validate their MFA before being redirected back to where they left off without clearing any unsaved changes they may have.
An alternative option was to not have MFA on session timeouts, using only the password, as it can be assumed that the user had to enter MFA verification to get into the CMS in the first place.

Seems to be working for me with the following steps:

Log in
Perform MFA verification
Go to the Pages section
Open the logout link in a new tab and close it
In the original tab, click on a page in the site tree
Re-authentication dialog shown, enter password and "Let me back in"
Continue to navigate the CMS successfully

It shouldn't prompt you for MFA at this point, and doesn't appear to be doing so.
@brynwhyman do you agree?

Do you just want to double check that a user can't change the request payload when "resuming" to get around MFA (given they know someone elses password). The original concern was that the client sent through a member ID or something when "resuming" the session.

The user is assigned a tempid token, which is used to identify them which lasts for 72 hours by default. It then proceeds to compare the password you provide against a Member it finds with this token. TBH I think the security aspect of this part of silverstripe/framework should be discussed via the security mailing list if it were scrutinised and found to have defects.

Thanks for reviewing this @robbieaverill, I had been thinking of previous discussions where we thought we might want to implement MFA into the session timeout dialog. Closing this issue as "investigated with no further action required".

Sounds good to me. I think this can be closed then.


Arm ampere support

Proposal
The operator does not seem to support arm64. Is it possible that you add support to it?
Use-Case
Install it in hetzner ampere
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response

@tzahifadida Only the operator image supports the arm. Our product images do not support it because not all versions of our PG distributions support it. As soon as we have all the needed RPMs, we will add them.


Marketplace not visible in 365 admin center.

Lab: 1
Exercise: 1
Task: 3
Step: 2
We're told to go to "Marketplace" to get the licences, but this isn't showing the 365 Admin center in most tenants.  It's still Billing / Puchase services.

Resolved with PR #41, thanks @AnnetteGill!


Add Release and Debug profiles for Linux and Windows

Needed for updates to build pipeline

I don't quite understand why this is required? Why are we adding the entire conan config repo into main here?

2 reasons -

Because the release and build pipeline will be updated to use Release/RelWithDebInfo until post-MVP (when we decide on using/not using Debug, mapping optimizations to respective compilers, etc).
By having all of the profiles available now, this will allow from-source consumers to easily build with Conan until we move off - this should effectively work post-Conan 2.0 (which seems like we'll be on sooner than us moving off of Conan).

FWIW, these all do work as I can run Engine_Tests with each configuration, but I will also throw a caveat that unless it's a contributor/maintainer to the Engine OR if someone needs to poke with a from-source build, users should not be using Debug. (Which neither the SDK, the Engine README, or our pipelines will reference).

Also I'd just want to throw out there that the configs without a specification default to Release on purpose (this was how we previously had it before any of the CI refactoring)

I still don't get why we have to pull in all of our conan config profiles to achieve that?


Trouble getting the mnist example to converge

I have not been able to get the mnist example to converge. Even after days of training (8-CPU system, no GPU) following the standard mnist example in the kit with no change (run as: python main.py --dataset mnist --is_train True), the d_loss/g_loss values just bounced around 1.3/0.7 with little sign of getting any better. I have not observed any error messages so far.
Is it expected that the mnist example will require a lot more computing power than I have in order to make it converge? If there are some hidden problems then what should I look for?

I meet the same problem,it just can't converge.
But the picture in the samples folder are getting more and more clear.

for GAN, however, convergence is likely an indication of failure...

I suggest you not to use my code but just a reference code. This code is one of my earliest practice with TensorFlow and now there are "too" many good papers and its implementation in generative model fields which published and open-sourced after DCGAN is appeared.

https://github.com/openai/improved-gan/
https://github.com/openai/pixel-cnn
https://github.com/openai/iaf
https://github.com/openai/InfoGAN
and literally a lot and it's hard to find...

What's the algorithms used to generate MNIST digitals? I found a lot of source programs using label information, that original paper not contains.
            h0 = tf.nn.relu(self.g_bn0(linear(z, self.gfc_dim, 'g_h0_lin')))
            h0 = tf.concat(1, [h0, y])

            h1 = tf.nn.relu(self.g_bn1(linear(h0, self.gf_dim*2*s4*s4, 'g_h1_lin')))
            h1 = tf.reshape(h1, [self.batch_size, s4, s4, self.gf_dim * 2])

@auroua  Yes , just like "conditional adversarial networks"
Adding label to training data will makes result realistic in general.

the loss  just bounced around 1.3/0.7 means "converge" in my experiments.


multi-line rows in tables

Is it possible to have a multi-line row in a table ?
I test pandoc "grid_tables" syntax and "" without success. A syntax is already supported in react-markdown?

Not as far as I know. It's not part of the markdown spec. You could always ask in the remark ecosystem - they allow you to get more nitty-gritty.


Don't throw when grabbing injected provider

Summary
window.top may throw DOMException, we should not let this error blocking us from continuing
How did you test your changes?

Review Error for nateReiners @ 2024-06-21 20:31:14 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help


Department Discord Role Whitelist

Describe the feature
If a department is whitelisted. Person will be approved automatically if they have the proper Discord role for Department. Otherwise, it will be pending approval.
Additional Context
No response

this is not possible because we don't know what officer this role should apply to. This was already discussed a really long time ago: #433