Unity SDK 5.3.0, 5.3.1 & 5.4.0 will not build in Unity Cloud Build for iOS

After upgrading firebase from Firebase Unity SDK version 5.2.1 to any of the above versions, the iOS project will fail during archive with the error:
 /Pods/FirebaseDynamicLinks/Firebase/DynamicLinks/FDLURLComponents/FDLURLComponents.m:19:9: 'DynamicLinks/FDLURLComponents/FDLURLComponents+Private.h' file not found
Android is built successfully with the above versions.
The project builds fine when locally after a pod update / install but will never build in Unity's cloud build. When going back to SDK version 5.2.1 it will build successfully again.
Is there a missing dependency when Unity Cloud Build runs? A repo that isn't updated?
This blocks us from upgrading to future versions of the SDK.

It looks like Xcode project integration in the iOS Resolver appears to not be adding the correct set of include paths for the Firebase/DynamicLinks Cocoapod.  In particular, it looks like we're not adding to HEADER_SEARCH_PATHS from here correctly.

Digging through the logs the include path is being added but Xcode is ignoring it...
Applying build setting 'HEADER_SEARCH_PATHS = $(inherited) "${PODS_ROOT}/Headers/Private" "${PODS_ROOT}/Headers/Private/FirebaseDynamicLinks" "${PODS_ROOT}/Headers/Public" "${PODS_ROOT}/Headers/Public/FirebaseAnalytics" "${PODS_ROOT}/Headers/Public/FirebaseAnalyticsInterop" "${PODS_ROOT}/Headers/Public/FirebaseCore" "${PODS_ROOT}/Headers/Public/FirebaseDynamicLinks" "${PODS_ROOT}/Headers/Public/FirebaseInstanceID" "${PODS_ROOT}/Headers/Public/GoogleUtilities" "${PODS_ROOT}/Headers/Public/nanopb" "${PODS_TARGET_SRCROOT}"/Firebase' to build config Debug (1D6058940D05DD3E006BFB54)
UnityEngine.Debug:Log(Object)
Google.Logger:Log(String, LogLevel) (at Z:/tmp/tmp.40FKqscNsW/third_party/unity/unity_jar_resolver/source/VersionHandlerImpl/src/Logger.cs:83)
Google.IOSResolver:Log(String, Boolean, LogLevel) (at Z:/tmp/tmp.jkgKDeCCv7/third_party/unity/unity_jar_resolver/source/IOSResolver/src/IOSResolver.cs:806)
Google.IOSResolver:UpdateProjectDeps(BuildTarget, String) (at Z:/tmp/tmp.jkgKDeCCv7/third_party/unity/unity_jar_resolver/source/IOSResolver/src/IOSResolver.cs:2375)
Google.IOSResolver:OnPostProcessUpdateProjectDeps(BuildTarget, String) (at Z:/tmp/tmp.jkgKDeCCv7/third_party/unity/unity_jar_resolver/source/IOSResolver/src/IOSResolver.cs:2047)
UnityEditor.HostView:OnGUI()

Perhaps PODS_TARGET_SRCROOT isn't set?

Well it turns out PODS_TARGET_SRCROOT isn't set and is actually set per pod project which means that we'll need to expand this in the iOS Resolver.
Changing the include path to "${PODS_ROOT}"/FirebaseDynamicLinks/Firebase fixes the include issue but turns up a compile error in the Dynamic Links pod.

@eladleb as you can see from some of these updates we have some patches to the iOS SDK to build with Unity's default C compiler settings (C99) that fixes compile errors.  In addition, I have a patch lined up to the iOS resolver internally that I should be able to release publicly very shortly that will fix the Dynamic Links source pod integration into the Xcode project that is required for Unity Cloud Build.  Once the new iOS SDK is released along with the new iOS resolver we'll post the workaround to apply to the Unity SDK until we have a new release (likely next week).

Play Services Resolver 1.2.94 contains a fix for building source pods like Dynamic Links
https://github.com/googlesamples/unity-jar-resolver/raw/master/play-services-resolver-<IP_ADDRESS>.unitypackage
However, the Dynamic Links pod still won't compile in the Unity generated project as it's using typeof() rather than __typeof__().  If you really need this to work right now you'll need to write a build step to patch the Xcode project to change the C compiler language dialect from C99 to GNU99.

Hey @stewartmiles, thank you so much for your prompt and thorough investigation, it looks great!
I'll hang tight for the updated Unity SDK or a workaround which doesn't involve an additional build step in Xcode.

I just integrated Unity SDK 5.4.2 and it seems to build correctly in cloud build, thank you so much!


Not an issue

Hey Guys!
I'm here just to say how much I'm thank full for your guys taking your free time to do this program.
The internet is better with people like you.
THANK YOU SO MUCH!
And sucess to you all in all of your projects.
best regards.

I was about to post similiar post :)
I'm glad someone was so motivated to start a project like this!
THANK YOU! <3
And the fact it's beeing made for three OS platforms... Simply WOW!

Thanks!


3D Models

Hello nathan! , When I use this format in JSON wooden_hoe to add 3d models. In game, I cant get this modes with /mgive amakna wooden_hoe:1.2.3,etc..  This format of JSON works in 1,11,2?
https://github.com/elBukkit/MagicPlugin/blob/master/Magic/src/resource-pack/default/assets/minecraft/models/item/wooden_hoe.json#L31
I looked at the json of other resourcepacks with models and this format was in a single line, it affects ?

This RP is set up to only affect unbreakable items.  So if you want to see them in-game you have to do
/mgive wooden_hoe:1
/mitem add unbreakable

Then the custom icon should show up.
Having it all on one line is probably just to compact it or possibly make it less readable (obfuscated).

It's so strange, if I use my own JSON in one line, it works! , but with the format "https://github.com/elBukkit/MagicPlugin/blob/master/Magic/src/resource-pack/default/assets/minecraft/models/item/wooden_hoe.json#L31" not. Any suggestions? hhahahaha


Pass color prop to Base in Slider

Pass the color property to Base for the Slider component so that custom colors passed in are transformed using color-style.
Somewhat (loosely) related to https://github.com/jxnblk/rebass/issues/163

Hey thanks for this, but hopefully this isn't an issue anymore in v1


Fix in askForForgottenPassword POST Controller.

Just a rewriting of the condition to be sure that we set resetPasswordMail to true only if we actually call askPasswordChange()
I used Optional.orElse() to avoid using multiple if and else conditions.

Coverage increased (+0.04%) to 51.183% when pulling eb478ad09cf5e5fb1571782d7f2887ca71676ce7 on alexandrepa:fix_activation into 1eac99796cca6a7d5c567af005c18acae452ba97 on blossom-project:master.


Export parseAs function

I tested it with the Vizer.tv(pt-BR) extension and it worked as expected.
Related with #3

Update: This may be broken if the app merges upstream and applies this commit, as it changes the body of the parseAs function and as a inline function, the usual "hey bro thats a stub" implementation doesnt work and requires a update.
Should i update this PR now to reflect this commit or only after the main app merges upstream changes?

Closing the PR, as this newer commit forces the usage of context sheninagans, and i don't think that enabling context-receivers and importing kotlinx-serialization as compileOnly would be worth it for a single extension function.


IndexError: list index out of range when use SearchGraph

Describe the bug
There is an error: index out of range when I use SearchGraph after updating the library to the last version. In the previous version I had installed it was working well
    smart_searcher = SearchGraph(prompt=self.prompt, config=self.config)
  File "/Users/cesaruribe/workspace/monadical/vctools/vctools/.venv/lib/python3.10/site-packages/scrapegraphai/graphs/search_graph.py", line 57, in __init__
    super().__init__(prompt, config, schema)
  File "/Users/cesaruribe/workspace/monadical/vctools/vctools/.venv/lib/python3.10/site-packages/scrapegraphai/graphs/abstract_graph.py", line 57, in __init__
    self.llm_model = self._create_llm(config["llm"])
  File "/Users/cesaruribe/workspace/monadical/vctools/vctools/.venv/lib/python3.10/site-packages/scrapegraphai/graphs/abstract_graph.py", line 136, in _create_llm
    llm_params["model"] = split_model_provider[1]
IndexError: list index out of range

To Reproduce
Run SearchGraph
Expected behavior
It must work
Screenshots
Desktop (please complete the following information):

OS: MacOS and docker
Browser [e.g. chrome, safari]
Version [e.g. 22]

Ok which model are you using?

I'm using this  {'llm': {'model': 'gpt-4o-mini',...}}

I think you need to add the provider to the model now so openai/gpt-4o-mini

yes we updated yesterday for making more consistent the library. Look at this example https://github.com/ScrapeGraphAI/Scrapegraph-ai/blob/main/examples/openai/smart_scraper_openai.py

Hi, I will close the issue, if you have problems please reopen

known_providers = {"openai", "azure_openai", "google_genai", "google_vertexai",
"ollama", "oneapi", "nvidia", "groq", "anthropic" "bedrock", "mistralai",
"hugging_face", "deepseek", "ernie", "fireworks"}
                    you need to pick up one from this list


Add exhaustive case generation

Would be nice to have something like
enum E {
  case C1(abc)
  case C2(def)
  case C3(ghi)
}

def f(e: E): Bool = match e {
  <press tab or something>
  <generates:
  case C1(abc) => ???
  case C2(def) => ???
  case C3(ghi) => ???
  >
}

Difficult because we cannot parse def f(e: E): Bool = match e { but we must know the type of e.

If we lookup what functions we are inside, we could find the local variables, then find their types, and then add completions like:
match x { ... }
match y {...}
Its not exactly the same, because here you have to choose the variable you want to match on.

Fixed in master.


Blank entry at the start causes subsequent entries to be skewed

Where do the first two entries come from?

The raw (quoted) keys are:
""
":ASPNETCORE_BROWSER_TOOLS"

Fixed in PR: https://github.com/Stravaig-Projects/Stravaig.Extensions.Configuration.Diagnostics/pull/207


Youtube vanced samsung a04e playback not working 30 seconds video stopped

Youtube vanced samsung a04e playback not working 30 seconds video stopped sir problem solved my device I love vanced tem

https://github.com/ReVanced/revanced-discussions/discussions/1037


Item assignment support: ${x}[key] = Keyword

Hello everyone,
This PR fixes #4546.
Adds item assignment support from keyword returns. Here a few examples of capabilities:
${dict}[key] =    Set Variable  value    # dict assign
${dict}[key1][key2] =    Set Variable    value    # nested assign

${list}[0] =     Set Variable  value    # list assign using str index
${list}[${0}] =     Set Variable  value    # list assign using int index
${list}[${other_variable}] =     Set Variable  value    # list assign using variable as index
${list}[1:-1] =     Evaluate  [1,2,3,4]    # list assign using slice as index (passing iterable value)

${dict}[key]   ${list}[0]    @{list}[1] =    Evaluate    (1, 2, 3, 4, 5)    # multiple variables assign
${obj}[1] =      Set Variable     value    # object that implements __setitem__

${str}[1] =     Set Variable     value    # will raise an error stating: "Variable '${str}' of type str does not support item assignment: variable should be mutable and should support a '__setitem__' method."
${list}[] =    Set Variable     value     # will raise an error stating: "Setting value to list variable '${list} at index [] failed: ValueError: invalid literal for int() with base 10: ''

I updated the UG and the Collections docs but it might need a bit more polish and details.
Please let me know how I could improve this PR and hopefully make it through to the v6.2 🙏

RF 6.1 is so much late that we won't have time for RF 6.2 anymore this spring. Once RF 6.1 is out, we'll continue more active development only in the autumn. On a quick look this PR seems to be in so good shape that waiting until autumn would be annoying. If you @Vincema are interested, we can still try to push this to RF 6.1. We try to get it release ASAP, but there's at least the next week still time. I'll review the code changes shortly, and you can then decide do you want to try getting this into 6.1 or not.

Thank you so much for taking the time to review this PR.
I've tried my best to improve the code as per your comments.
Please let me know when/if you need me🙏🙏


Linux?

Doesn't this doc also work for Linux VMs? It doesn't show up in the Linux menu.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d84bf446-324c-da0c-c099-b352849a696d
Version Independent ID: c55004b7-c4f5-290f-d5a7-be39bf961ec7
Content: Create a Windows VM from a specialized VHD in the Azure portal
Content Source: articles/virtual-machines/windows/create-vm-specialized-portal.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the question! We are investigating and will update you shortly.

@dcbrown16 thanks for the question! Yes, it should work for a Linux VM. There isn't really anything in the article that is specific to Windows.

Thanks @cynthn , in that case I would suggest we link it on the Linux VM doc navigation as well to make all of the options clear to Linux users.

@dcbrown16 agreed :) I'll create a work item to create a Linux version and get it into that TOC ASAP. Thank you for the feedback!
#please-close


+1 Caster Level goes up to max of 9

Caster Level is not Spell Level.
in classes/MainUI/PartyEditor.cs
at line 443

PartyEditor.cs ( line 442 -> 461 )
else {
                           var maxLevel = spellbook.Blueprint.MaxSpellLevel; <---
                           var casterLevel = spellbook.CasterLevel;
                           using (UI.HorizontalScope()) {
                               UI.EnumerablePicker<int>(
                                   "Spell Level".bold() + " (count)",
                                   ref selectedSpellbookLevel,
                                   Enumerable.Range(0, casterLevel + 1),
                                   0,
                                   (lvl) => {
                                       var levelText = lvl <= casterLevel ? $"L{lvl}".bold() : $"L{lvl}".grey();
                                       var knownCount = spellbook.GetKnownSpells(lvl).Count();
                                       var countText = knownCount > 0 ? $" ({knownCount})".white() : "";
                                       return levelText + countText;
                                   },
                                   UI.AutoWidth()
                               );
                               if (casterLevel < maxLevel) {
                                   UI.ActionButton("+1 Caster Level", () => spellbook.AddBaseLevel());
                               }

spellbook.Blueprint.MaxSpellLevel will only return max of 9 (depending on spellbook/class could be lower) whereas max caster level for most spellcasting classes is 20 (depending on class)

What happens now and how does it differ from expected result? It might be just a matter of wording - "+1 Caster Level" button seems to increase spellbook level (so 1-9 is correct range, whatever such increase might mean) and not caster level.

Ok, my fix went in - wait for next release (anything later than <IP_ADDRESS>) and check if your problem is fixed!

Fixed thanks!


change function errors but still still updates the record

I get PermissionError: Unable to update record: product:byqu8riqoe8bxfqca5xe when running
const updated = await db.change(id, product);

I am having this same issue with db. change and db.update using javascript or deno with version 1.0.0_beta.9-1

Fixed this today! Thanks :)

@kearfy This error isn't solved for me in 0.6.0.
It works when using an integer as index, but doesn't work if a string was used.
works
  let db_product = await db.change(
    "products:1",
    product
  );

throws error:
  let db_product = await db.change(
    "products:gold-bond-healing-skin-therapy-lotion-with-aloe-20-oz-non-greasy-and-hypoallergenic",
    product
  );

error message
file:///home/user/Projects/bestproductinsight-com/scripts/node_modules/.pnpm/surrealdb.js@0.6.0/node_modules/surrealdb.js/esm/index.js:414
    throw new error(errormessage);
          ^

PermissionError: Unable to update record: products:gold-bond-healing-skin-therapy-lotion-with-aloe-20-oz-non-greasy-and-hypoallergenic
    at Surreal._Surreal_outputHandler (file:///home/user/Projects/bestproductinsight-com/scripts/node_modules/.pnpm/surrealdb.js@0.6.0/node_modules/surrealdb.js/esm/index.js:414:11)
    at Surreal.change (file:///home/user/Projects/bestproductinsight-com/scripts/node_modules/.pnpm/surrealdb.js@0.6.0/node_modules/surrealdb.js/esm/index.js:360:94)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async default (file:///home/user/Projects/bestproductinsight-com/scripts/generate-content/write-to-db.js:17:20)
    at async main (file:///home/user/Projects/bestproductinsight-com/scripts/generate-content/main.js:21:5)

Node.js v18.12.1

I am using a schemafull setup
  BEGIN TRANSACTION;

  REMOVE table categories;
  REMOVE table products;

  DEFINE TABLE categories SCHEMAFULL;
  DEFINE FIELD name ON categories TYPE string;
  DEFINE FIELD products.* ON categories TYPE record(products);

  DEFINE TABLE products SCHEMAFULL;
  DEFINE FIELD name ON products type string;
  DEFINE FIELD imageUrls ON products type array;
  DEFINE FIELD imageUrls.* ON TABLE products TYPE string;
  DEFINE FIELD amazonUrl ON products type string;

  COMMIT TRANSACTION


parent POM cannot be found

When I try to build the classes locally, build fails because parent POM cannot be found in public repository :  com.seovic:oss-parent:1
Can it be deposited?
Hassene

Hi,
Please download full .zip version , the parent pom is located at
https://github.com/aseovic/coherence-tools/blob/master/pom.xml
Regards
Hitesh

The problem is that with the release of 0.6 the parent of coherence-tools changed from org.sonatype.oss:oss-parent:7 to com.seovic:oss-parent:1. The issue here is that com.seovic.oss-parent isn't a valid artifact (at least, not that I can find). Is there a reason why the parent was changed in release 0.6? The only solution I've found so far is manually editing the coherence-tools POM to repoint to the sonatype oss-parent. You can see the commit here: https://github.com/aseovic/coherence-tools/commit/bd501ae2e339aed15206629e8dcf74d842d50ec6#diff-600376dffeb79835ede4a0b285078036


Modify leftnav and tab have no hightLight about #4996

Modify leftnav and tab have no hightLight

Coverage decreased (-0.02%) to 64.608% when pulling 3f281c456a2d7d80dceaa66888fdd1a5e88b0394 on pengpengshui:hightLight into c2c667c6d6abf59ee8718118c26b36b41fe8b8d5 on vmware:master.


State of CI testing with Nix

It's been a long time since I said I would write this summary issue (cc @siddharthist who was interested in particular).
Overall, the current state of CI testing with Nix is documented in the wiki. It is one of the two newly established and officially supported ways of testing projects depending on Coq, the other being opam + Docker (see comparison here). Both setups avoid to rebuild Coq at every test or depend on an outdated opam cache.
Both setups should allow in theory to reuse build artifacts to build reverse-dependencies (e.g. corn which depends on math-classes) or the various packages depending on math-comp. In the case of Docker, it is a matter of generating a Dockerfile and pushing the new image to a Docker registry (either dockerhub when building the master branch, or GitLab's registry when building any branch, see discussion at https://github.com/math-comp/math-comp/pull/256).
In the case of Nix, it requires pushing to a cache on Cachix. This should be very easy to setup as soon as this is tested and documented. However, my initial tests did not work. The main difficulty is to make sure that the exact same derivation is built on the CI that is going to push to Cachix as is required in the depending builds. The problem is that the derivation depends in turn on the source derivation. Depending how it is built, it may be sensible to the name of the directory which contains it.
For instance, the default.nix file of Coq takes it source from the current directory, and this is also the case for the proposed template default.nix in this repository. When building with nix build, the source will be copied to the nix store in a repository like /nix/store/l14sddwdd8lrji8qp900jcd12h4w1sgq-name where name is the name of the directory that contained the sources in the filesystem. This is highly unstable. That's why in Coq's .gitlab-ci.yml, we do not run nix build on the sources but we do nix build -E "import (fetchTarball $CI_PROJECT_URL/-/archive/$CI_COMMIT_SHA.tar.gz) {}". The fetchTarball operation will always copy the sources to a location in the Nix store that only depends on the content of the tarball. Then our template default.nix for projects depending on Coq will load the Coq dependency in the same way (using fetchTarball again).
A similar trick will be needed to be able to make the build artifacts that we upload to Cachix reusable, unless another way of fixing this instability is found (cc @vbgl to which I talked about these issues already).

I'd like to have a look at the future of our templates for building with Nix on CI.
CI with Nix was the first solution that was explored in our templates (before docker-coq existed) but since then, I've had little time to devote to it and meanwhile, @erikmd has made CI with Docker better and better.
Right now, we support three CI providers in our templates: Travis, CircleCI and GitHub Actions. Only our Travis support also includes Nix support.
Reading https://discourse.nixos.org/t/fate-of-travis-ci-nix-language-support/7907, it looks like the Nix community is massively moving over to GitHub Actions and Nix community support for Travis is going to end soon. I have no experience yet with GitHub Actions for Nix but @CohenCyril does (and it looks simple enough).
It seems to me that it would be a bit sad to renounce entirely to CI with Nix, especially because, to me, Nix is still the easiest way to easily get the dependencies one needs to build a project (when using it locally, it seems more flexible than Docker for instance and more powerful than opam).
OTOH, it seems that the flexibility brought by opam regarding multiple version testing cannot be matched by Nix (although @CohenCyril is again more active and knowledgeable than myself on the current evolution of Coq packaging in nixpkgs and the support of multiple package versions). The problem I mentioned in my previous post that sometimes you need to test with the dev version of your dependencies, that might be packaged in opam but not in Nix still looks unsolved to me.
Finally, a minor point regarding this issue:

The problem is that the derivation depends in turn on the source derivation. Depending how it is built, it may be sensible to the name of the directory which contains it.

I was told of a solution about one year ago, but I still haven't tested it yet :facepalm:

Hi! Thanks for pinging me @Zimmi48. I indeed experimented a lot with nix for mathcomp, I am not entirely satisfied with the current result, but I have plans to make it better and extend to all coq packages. With cachix and github actions, it leads to really quick and reproducible CI, and I even intend to provide "copy vo" feature to get started instantaneously e.g. when getting started with a branch that already passed CI.
Regarding multiple version testing I found a very light way to do it, but for now without guards (to assert a given set of versions is going to compile). One might say this is a disadvantage wrt opam, but while preparing nix packages I realized that some combinations I expected to work did not. Indeed, opam lets you describe constraints, but resolution is performed at installation time, leaving the user to deal with potential conflicts. On the other hand, nix forces the package manager to handpick versions that go well together (https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/coq-modules/mathcomp/extra.nix#L206-L287 actually putting all of it in the same file was one of the mistakes I am going to fix). Then CI has to test only a carefully picked set of packages (e.g. https://github.com/math-comp/math-comp-nix/actions/runs/138819891/workflow) and end-users are provided ready-to-uses versions of the various library, but may alter some versions if they mean it (e.g.https://github.com/math-comp/analysis/blob/e2bab6f145d62cde3c15472175983733989e6e14/config.nix is overriding default packages)

@palmskog reported that Cachix's caching has been failing on Travis recently and this is despite the fact that I pushed a fix related to a similar issue just two months ago (b880f68fffa0b770a1fc48168a41dc9cb45789b5). I didn't have time yet to figure out what's going wrong this time, but this hints again that our Nix on Travis support isn't really sustainable. As I mentioned in #73, I'd like to start recommending GitHub Actions as the preferred CI provider but this would be a shame to do so without having a template for Nix testing first. @CohenCyril would you be willing to contribute such a template based on your experience and what you know works fine as of today?

@Zimmi48 I intend to contribute, but with CPP's deadline, it might not be before the end of the month. Is it an emergency?

Thank you.
Not an emergency, of course!

@CohenCyril Friendly reminder of this issue now that the CPP deadline has passed :wink:

Thi task is scheduled for next week!

Due to new critically low build minute limits introduced by Travis CI, we are going to switch coq-community projects that relied on Travis to GitHub Actions (see https://coq.zulipchat.com/#narrow/stream/237663-coq-community-devs.20.26.20users/topic/New.20Travis.20limits.2E). This means that projects won't be tested with Nix anymore until there is a GitHub Action template for Nix. For some projects, it was especially useful because the Nix setup tested the build with make while the opam setup tested the build with dune.
@CohenCyril do you have an update on your progress?

I did not manage to do it so far, the time I allocated for this was too short.
I will try again next week, and if I do not succeed, I wouldn't mind a group session on this at the CUDW (or before).

Concretely, do you messages mean that I should take action to remove the Nix build for the ci of TLC? e.g. https://travis-ci.com/github/charguer/tlc/builds/203743460
(If so, please let me know which line/file/config to remove.)

@charguer The problem is not with Nix, the problem is with Travis. See the Zulip discussion referenced above. You can go to https://travis-ci.com/account/plan to see how many build credits you have left.  This is why we are switching all coq-community projects to GitHub Actions (we've spent more than half of the allowance in just three days). Nix is not yet supported in our GitHub Actions template but should soon be (thanks to Cyril, with my help if needed). To generate GitHub Actions configuration files, you just need to add action: true to your meta.yml file and re-run the generate.sh script.

A use case that is not easily solved by Docker-Coq-Action was raised in https://github.com/coq-community/docker-coq-action/issues/51. It is the one of easily installing any given version of Coq with any given version of Haskell or Python. The Nix-based CI template could be a good fit for this use case.

An update of this issue: we have been working a lot with Cyril at improving the Nix support for the Coq ecosystem. There is now a (still unstable until the first release) coq-nix-toolbox and the templates are soon going to be updated to rely on it for Nix-based CI (#87).
We have also subscribed to a larger Cachix storage for the Coq community. To start with, this will benefit Coq, math-comp and coq-community, but we should be able to include other organizations or users that would benefit from this.
Apart from releasing an initial version of the coq-nix-toolbox and merging the corresponding template PR, other to-do items are:

[ ] Updating the documentation, in particular the one at https://github.com/coq/coq/wiki/Nix.
[ ] Using the coq-nix-toolbox infrastructure in the Coq repo instead of the custom one that we have today.

It looks like Nix CI with Cachix is broken for tarballs once again, I'm getting full 20 min builds every time since about a week, for example: https://github.com/coq-community/aac-tactics/runs/3240237246
I'm guessing this will be fixed by the Nix toolbox? In the meantime, maybe we want to completely avoid Nix CI for all tarball builds.

Yes, sorry that's my fault. I've started the transition of Coq's CI to the toolbox infrastructure. Depending on how much needed this legacy CI setup is, I can either prepare a PR on the Coq side to fix the problem, or we can disable the legacy CI system on the few projects that are left using it.

@Zimmi48 the main problem right now is that we have no CI option for 8.14 right now except using Nix.
As I pointed out in https://github.com/coq-community/aac-tactics/pull/77 the Nix toolbox approach is way too complex for me to handle, so when Docker support for 8.14 arrives, I will disable Nix CI in all my projects.

@palmskog the PR that broke the binary cache for your use case (coq/coq#14590) hasn't yet been backported, so 8.14 testing should still work as before.
I also acknowledge your use case and point of view on the toolbox and will think about providing a simpler, toolbox-compatible, Nix CI setup. I'm expecting this should be quite doable.

But the CI run I linked to (https://github.com/coq-community/aac-tactics/runs/3240237246) was already using 8.14, namely, https://github.com/coq/coq-on-cachix/tarball/v8.14, and I still got the 27 min running time. What do I need to do for 8.14 caching to work?
Sounds good that there could be a simple CI setup for Nix. It looks like we are going to spend several more years of using both coq_makefile and Dune concurrently for many projects, so I think testing them both is essential.

OK, then my interpretation of why it was not working as before wasn't correct. That being said, instead of investigating the reason, I will work at providing a lightweight toolbox-based alternative, that should hopefully also be more robust in the long run.


When will release the training code of alpha-CLIP?

+1

We have launched training code as well as our data. you can finetuning bigger model on your own, we currently don't have plan to finetune due to limited resources.

We have launched training code as well as our data. Sorry for keep you waiting for so long.


Ensure camera area in StandardCamera has no hidden areas

At present, I'm pretty sure the CameraView in the StandardCamera actually takes up the full screen and the bars at the top and bottom are just overlaid on top of it. Instead, the CameraView should only be what is visible and the image that it captures should have the aspect ratio of the visible area.
This definitely raises questions about how this area should be sized and how big the top and bottom bars need to be, but I don't have absolute clarity on that yet, so I would pick fixed sizes for the top and bottom bars and let the camera fill the rest of the space.

I can make a pr for this

Closed via #513


Support for netCDF packing

NetCDF has support for variable packing; by specifying attributes scale_factor and add_offset, data can be packed into smaller data types. 16 bit short integers provide more than enough quantization for suitably scaled temperature data, for instance. See: http://unidata.ucar.edu/software/netcdf/docs/BestPractices.html#bp_Packed-Data-Values
Iris (or rather the underlying netCDF4 python library) unpacks data automatically when loading, but offers no way to pack data when saving. Since this is supported in netCDF4, this should be easy to implement. For this to work, it must be possible to set the add_offset and scale_factor attributes (they are currently reserved/forbidden attribute names). Further, it must be possible to specify a datatype for the packed netCDF variable. The current implementation uses the datatype of the data variable, which is a sensible default, but when packing data you typically want a short integer (but that should be a user choice.)
Using the netCDF4 library, the datatype is set at variable creation and add_offset and scale_factor are then set by calling the variable's setncattr method. But those are really details of the saving process. The cube should have the datatype of the unpacked variable, not the packed datatype. So maybe the user could pass datatype, add_offset and scale_factor as optional keyword arguments to the save method (as a dictionary perhaps?). If they are set we set those ncattrs and change the netcdf datatype. NetCDF4 handles the packing automatically. Does that make sense or should add_offset and scale_factor be set as cube attributes before saving?

Thought about this a bit more. The save method can take iterables as well as just cubes. I think the safe, conservative thing to do is to mimic the netCDF4 api; that is, allow add_offset and scale_factor to be set as cube attributes. The save method should then take (as an optional keyword argument) either a single datatype or a list of datatypes of the same length as the cube iterable, which are then passed to the netCDF4 api.

I have this working now. When I've written some tests I'll submit a pull request.

I added a pull request, so I'm closing this now.


Missing semicolon ";" on these lines: 91,1076,1232,1293.  Won't work if ...

...you "pack" this file.  Now it's working for me :)

Thanks saruman, I applied these changes to the dev branch.


Update signature for Django 3

Upgrading Django from 2.2 to 3.0.5 and getting this error when I try the built in admin for a model with encrypted fields
TypeError: from_db_value() missing 1 required positional argument: 'context'
Looks like the method signature was updated but someone already has a fix: https://luc.lino-framework.org/blog/2019/1128.html

Coverage remained the same at 100.0% when pulling b5426bdfe97de792bbb890aa76d1e669a37a3676 on jrenaut:master into 8f8cadb8a9637e3f5777c98b9a9dd7db1b044374 on orcasgit:master.

Coverage remained the same at 100.0% when pulling b5426bdfe97de792bbb890aa76d1e669a37a3676 on jrenaut:master into 8f8cadb8a9637e3f5777c98b9a9dd7db1b044374 on orcasgit:master.

It looks like something specific of the model field you are using, I can't find that parameter in django 2.2, 3.0 and 3.1 branches.

I think you're right - I upgraded from 0.5 to 0.6 and upgraded a few other outdated packages and it's working now, so I'll close the pull request. I had extended EncryptedField but wasn't doing anything crazy - just needed to encrypt a decimal.
class EncryptedDecimalField(EncryptedField, models.DecimalField):
      pass


Port to axe-core

I have ported your project to the axe-core library. You can find it here.
https://github.com/dylanb/tota11y
There are some significant differences including:

does not support the color contrast suggestion - this could be included by combining the accessibility chrome dev tools as well as axe, or by implementing a function to replicate that
I fixed the ARIA landmarks code to work with HTML5 elements and only include the real landmark roles
I added an "aXe" category, which runs all the axe-core rules and displays generic information with these issues

The axe-core library includes a bunch more rules that the Google library and has support for all the ARIA labelling techniques, so the image rule now supports aria-label, aria-labelledby etc.
There are some other minor differences and I also uncovered a bug in axe-core related to role="presentation" on images...
I would submit it as a PR but I am not sure you are interested in using the axe-core library in addition to the Google library, if you are, I will go ahead an submit the PR, I am also open to collaborating on making the integration as kick-ass as possible.

Hey Dylan! Just poking around your repo, very cool stuff - hope you had fun hacking on it.
I'm unlikely to switch to aXe just because Accessibility DevTools has been so good to us, but I'd love to see your landmarks and img labeling fixes make their way upstream.
I'll close this issue for now, but would love to continue any discussion here.

I could submit the landmarks changes because they are independent of the axe-core library the image changes are dependent on it though.
I actually think you should consider using both libraries. There is a little overlap between the two but what we provide is much more comprehensive.

I'm going to be adding a few more features very soon (got a test for unsemantic buttons landing in the next few days), so I'll be sure to check more axe-core (the docs are really great by the way) and see if it makes sense to include it.
Awesome work, thanks for contributing it to the community :)


Create FUNDING.yml

nice

@professorDeveloper thanks, i am adding a way for people to donate something to me :)


chore: promote jx-aspnet-app002 to version 0.0.3

this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

jx-aspnet-app002
Changes in version 0.0.3
Chores

release 0.0.3 (jenkins-x-bot)
add variables (jenkins-x-bot)

Other Changes
These commits did not use Conventional Commits formatted messages:

Update README.md (hughexp)

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approval


Error with package with a prerelease version ("Invalid Version: 2.1.0pre")

Try knockout - in the console, you'll see Invalid Version: 2.1.0pre.
The data is:
[
    {
        "package": "knockout",
        "downloads": {
            "2.3.0": 633,
            "3.5.0": 2181,
            "3.4.1": 436,
            "3.1.0": 31,
            "2.1.0pre": 1,
            "3.0.0": 829,
            "3.2.0": 450,
            "3.4.0": 781,
            "3.5.0-beta": 10,
            "3.4.2": 5021,
            "2.2.1": 132,
            "3.3.0": 637,
            "3.5.1": 62666,
            "3.5.0-rc": 17,
            "2.1.0": 3
        }
    }
]

as you can see, 2.1.0pre (which is an invalid version) has a download. I think the logic probably needs to be updated to skip over invalid versions in groupByMajor?

I think you're correct!
Thanks for reporting!

I opened https://github.com/NullVoxPopuli/package-majors/pull/16 which will print a message to the console if a library maintainer wants to debug or somethin'

Thanks, makes sense!


update(LIB): update to latest LIB python-setup branch

some strange fail checking out LIB submodule
maybe try to run job again


Spike: deploy and test stac-fastapi

So that we can confidently productionise a STAC API and indexing tool we want to install and import LINZ data to the stac-fastapi.
Tasks

[x] Deploy and configure the tool in a LINZ AWS account (developers geostore-nonprod[1/2/3] account)
[x] Import LINZ's current production metadata (excepting the root catalog) in the Geostore production bucket.
[x] Brief results against the assessment criteria below should be captured in confluence.

See confluence page for research done so far.
Assessment criteria:

cost is acceptable (storage, compute, requests)
can ingest our data automatically from an S3 bucket with acceptable operational or development overhead
the API functionality works well and does what we expect
can index LINZ STAC metadata extensions and make available for search
easily deployed, maintained and configured
performs well with LINZ's full dataset (search speed etc)
list any missing functionality or components

Closing this as done. Thanks @AmrouEmad


DomTerm prompt - support mouse motion and more

The DomTerm terminal emulator supports a number of nice features, including moving the cursor with a mouse click (in the natural way, with a simple button-1 click, without disturbing other mouse operations such as context menu or scrolling).  See https://github.com/fish-shell/fish-shell/issues/4918 . This requires sending certain escape sequences in the prompt.
See this link for how to customize the Fish prompt for DOMTERM.  This also also add a one-character clickable button which hides/shoes the output (and any input lines after the first) of a command (folding).  It also creates "logical structure" in the DOM data structure, which enables CSS styling and copy as well-structured HTML.
This attachment is a suggested patch to README.md:
dt-fish.txt

Correct link is https://github.com/k4m4/terminals-are-sexy

@juzim Fixed, thanks!


Documenting src/components/SplashAnimation/SplashAnimation.jsx to explain functionality

File name: src/components/SplashAnimation/SplashAnimation.jsx

I would like to work on this please!

Great! I assigned you (@deandrehendrix) to the issue. Have fun working on it!


More mods and updates!

Added:

New Version of EditorTabbing
Add hantabaru1014 as Author to EditorTabbing for PR
New Version of UserJoinLeaveNotifications
New Mod CorrectGizmoScaling
New Mod BoundedUIX
New Mod ComponentAttacherSearch

Also added myself as an Author on Art's color drop mod for the PR 🤔

Also add PrecisionBlendShapeBaking

Consider using branches on your fork to make PRs that are only one mod each. Makes it easier to review one at a time versus needing to do 5+ and any issue on one holds up any additional entries.

I'll try to be faster with adding them to the manifest 😅

All good, looking over these at the moment.

I hope the transpiler ones are simple enough 👍

Everything else on this PR looks good. Can be merged after the one thing above is resolved.


color-picker takes 1.2s to activate

I'm just opening this issue to bring to your attention that timecop has consistently told me that color-picker takes 57ms to load, and 1286ms to activate. It's slowing down the startup of atom quite considerably for me.
Perhaps there are some optimisations that can be made somewhere?

+1 on this!


Add headings before the filter selectors

This PR is part of the OKR to improve the connection docs. A quick fix is to make the content filters on the connection topic more usable by adding headings.

Cool! I don't know if this would be better without visually seeing it, but what about a sentence before the filters and numbering the selectors (though practically you can select in any order, I suppose):

To connect to your CockroachDB cluster, select the following:

Your deployment
[filters]
Your language
[filters]
Your ORM or driver

That might be too fussy! But, it came to mind. I like your change though!


Parse embedded variants in case of no slot definiton

A fix for embedded variants issue.
I extract _parser function with name parse_variant_line to become public function and not an internal function of parse_custom_variant.
I reuse parse_variant_line to get slot information from lc timos_line.

@gusman in 1bd5d68 I moved the bof save command to the if block where the bof is configured.
I noticed that otherwise the bof save was not applied, due to model driven mode was enabled

@gusman if you agree with that change, I am good with merging this PR
thanks for looking at that issue


warn when used toolchain is out-of-date

on non-linux hosts, warn when toolchain is out of date.
Example
$ cross build
Warning: using older rustc `1.61.0-nightly (9f4dc0b4d 2022-03-23)` for the target. Current active rustc on the host is `rustc 1.62.0-nightly (879aff385 2022-04-20)`.
 > Update with `rustup update --force-non-host nightly-x86_64-unknown-linux-gnu`

Done, I think :)

bors r+

bors r+

oh ic, there's a mistake with use_codeowners = true

bors r+
maybe it's because of protected branch, lets see

bors r+

👎 Rejected because of missing code owner approval

seriously?...

bors r+
🤞

bors r+


UnderlineNav2 incorrectly calculating nav area when moving pages.

Description
It works fine to move to a page outside the more button, but if you move to a page inside the more button, the more button disappears.
https://user-images.githubusercontent.com/15520015/205739931-7145e7a8-9b76-449b-84de-e2137d7a3237.mov
Steps to reproduce

Reduce window width to check more button
Open more and navigate to another page. After you do it a few times, it will be reproduced.

Version
v35.15.1
Browser
Chrome

@broccolinisoup might you be interested in looking into this in the next few weeks?

Sure @lesliecdubs!
👋🏼 @b6pzeusbc54tvhw5jgpyw8pwz2x6gs, thanks for reporting this. I quickly tried it out but cannot reproduce it. Something worth mentioning though, we released a change on v35.15.0 on the API for exposing aria-current to the API and making the selected prop redundant for selected state. We released this as a minor change because UnderlineNav2 is still draft and unfortunately we are experiencing an issue where some of our recent docs update couldn't make it to the production and UnderlineNav docs were affected by this issue. Apologise for this inconvenience, and we are working on fixing them.
This is the updated docs : https://primer-afcff743b7-13348165.drafts.github.io/drafts/UnderlineNav2 If you could use aria-current to manage the selected state, I really hope you won't experience this issue 🤞🏼 If you have already updated your code before posting the issue or even using aria-current still causes the same problem, could I please ask more information like some code snippets etc?
Thanks again for taking the time to report this!

After updating the react and nextjs packages to the latest version, the problem in the video above was not reproduced, but similar problems still occur. So I changed the title of this issue.
I made an example with codesandbox for reproduction, you can check it out here.
https://codesandbox.io/p/sandbox/primer-underline-nav2-bug-ojlgdh
https://user-images.githubusercontent.com/15520015/206830866-ba8e0e3a-f55d-4247-b195-c2775d822481.mov

@broccolinisoup After updating the react and nextjs packages to the latest version, the problem in the video above was not reproduced, but similar problems still occur. So I changed the title of this issue.
I made an example with codesandbox for reproduction, you can check it out here.
https://codesandbox.io/p/sandbox/primer-underline-nav2-bug-ojlgdh
https://user-images.githubusercontent.com/15520015/206830866-ba8e0e3a-f55d-4247-b195-c2775d822481.mov

Codesandbox was unstable, so I recreated it with stackblitz.
https://stackblitz.com/edit/primer-undelinenav2-issue-2651-2676

👋 @b6pzeusbc54tvhw5jgpyw8pwz2x6gs thanks so much for the stackblitz! That will be very helpful to debug. I'll look into this and see what is going on 👀

👋🏼 @b6pzeusbc54tvhw5jgpyw8pwz2x6gs I had time to look at the issue today and I believe the reason of the issue is aria-current not working properly in the Stackblitz setup. When there is no "selected" state (it is achieved by aria-current), the component behaves unexpectedly. As far as I debugged, the root cause is the route names were not updating properly for most of the link items. See the screenshot please.

I quickly whipped up a working demo on top off the Stackblitz you shared. Here is the link and we documented this on our primer.style docs as well. (Quick note, just realised a typo and will fix it up. It should be as={Link} not s={Link}). Let us know if you have further concerns around this. Thanks!

@broccolinisoup Thanks for pointing out the bug in my code. I confirmed that the problem was solved in the stackblitz you shared. Thank you so much!
However, in my real project, which is not an example, the problem still occurs. I'm using a lot of different layouts for this project, but I think one of them is the problem. I'll check further on what's wrong and if I find reproducible code, I'll share it here in the comments.
So, can we leave this issue open for a while?

No worries! I am glad it was helpful. Yes, we can keep the issue open in the meantime.

Even after fixing the aria-current props bug, my real project still has this bug.
https://user-images.githubusercontent.com/15520015/210181458-5e184439-667a-474d-aac2-8dd5ff52ac8f.mov
The real project used<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and TypeScript.
However, it is not reproducible with the example code. Reproducing failed even though the packages and code of the example code were matched to the real project as much as possible. There are a few more attempts left, but when the next and react packages are updated in the real project, the bug does not occur, so I will close the issue here.
I'll come back again if there's anything to update. Thanks again!

No worries! Sorry to hear that there is still an issue in your real project. Please do let us know if you find a way to reproduce the issue again. Thanks for your time!


Incorrect help texts for all commands

What version of Ctrl-Q are you using?
3.15.2
What version of Node.js are you using? Not applicable if you use the standalone version of Ctrl-Q.
No response
What command did you use to start Ctrl-Q?
.\ctrl-q.exe help
What operating system are you using?
Win10
What CPU architecture are you using?
x86
What Qlik Sense versions are you using?
na
Describe the Bug
When showing Ctrl-Q help, it says "build" instead of "ctrl-q":
Usage: build [options] [command]

Ctrl-Q is a command line utility for interacting with client-managed Qlik Sense Enterprise on Windows servers.
Among other things the tool does bulk import of apps and tasks, manipulates master items and scrambles in-app data.

This is because the esbuild command creates a file called build, and the commander package (probably?) uses the source file name. Needs to be verified.
Expected Behavior
No response
To Reproduce
No response

https://www.npmjs.com/package/commander#name should be used to defined the app name


WPF, .net 8.0 and Splat latest version: IBitmap.ToNative, FromNative, SplatColor.ToNativeBrush and SplatColor.FromNativeColor not found by compiler.

Please note although we can't commit to any timeline, priority will be given to those who are Contributors to the project.
If this is a question please ask on StackOverflow.
Describe the bug
After upgrading to a wpf application to .net 8.0 and to the latest version of splat and splat.drawing, IBitmap.ToNative ,IBitmap.FromNative, SplatColor.ToNativeBrush and SplatColor.FromNativeColor not found by compiler.
Splat version 14.8.12
Downgrading to 14.8.6 then gives me IBitmapLoad not able to be resolved errors.  I don't know if this is related to: https://github.com/reactiveui/ReactiveUI/issues/3696

Please ensure that you are targeting at least windows10.0.17763.0

<TargetFramework>net8.0-windows10.0.17763.0</TargetFramework>

Thank you, that was the problem.


feat: Configuration reload

Add automatic configuration refresh
When the configuration file gets changed, the server reloads the configuration, reconnects to the database pool and executes the migrations again
If the email feature is activated, it also replaces the SMTP transport

[x] Implement
[ ] Feature gate
[ ] Clean up

i'll probably rewrite the pr without using global state. the current implementation is just ugly


weep export produces script code that is not working on mac bash 5.1

There is no -g option for the set command in Bash 5.1 on mac:

This is what worked for me when executing from the bash script:
cmd=$(weep export arn:aws:iam::123:/aaa/sss)
cmd=${cmd//"set -gx"/"export"}
cmd=${cmd//" \""/=\"}
eval $cmd

As you see, I changed the output to:
export NAME=VALUE

format. It would be great if we could get such output as well.

@mikansoro figured out the core issue: weepe uses SHELL env variable to figure out the shell (os.Getenv("SHELL")).
This is not the correct way of doing so. The SHELL variable indicates the default shell, not necessarily one that is used; like one specified in Shebang line of the script.
Solution: don't rely on the SHELL env. I tried quickly to find a go library that resolves shell correctly, but no luck. What works for me is the following shell command:
sh -c 'ps -p $$ -o ppid=' | xargs ps -o comm= -p

This should give the proper shell binary name, like /opt/homebrew/Cellar/fish/3.5.1/bin/fish


Hide the node's price if the node is down

Show the node's price if the node is rentable or rented by the logged-in user

Work in progress:
Condition added in all node cards

Work Completed:
Show the node price if the node is rentable or rented by the logged-in user.

verified on stagging
network : devnet
version : ac03039
dedicated nodes which are down are without prices


sandbox: gas: tube: increase averaged maximum CFL

By tuning the driving script, we could optimize CFLs of each march and
loop. The averaged maximum CFL is improved from 0.286695 to 0.736332.
Running with CPU i5-8265U, Ubuntu mate 18.04, in sequential mode.
issue #128
Steps to Test This Pull Request
Go to solvcon/sandbox/gas/tube and invoke ./go run.
Expected Results
As is
*** *** Step 584/600, 13.5s elapsed, 0.4s left
*** *** CFL = 0.07/0.40 - 0.06/0.42 adjusted: 0/0/0
*** *** Performance of tube:
*** ***   13.4802 seconds in marching solver.
*** ***   0.0230825 seconds/step.
*** ***   6.09518 microseconds/cell.
*** ***   0.164064 Mcells/seconds.
*** ***   0.82032 Mvariables/seconds.
*** *** ##
*** *** Step 592/600, 13.7s elapsed, 0.2s left
*** *** CFL = 0.08/0.40 - 0.06/0.42 adjusted: 0/0/0
*** *** Performance of tube:
*** ***   13.6513 seconds in marching solver.
*** ***   0.0230596 seconds/step.
*** ***   6.08914 microseconds/cell.
*** ***   0.164227 Mcells/seconds.
*** ***   0.821134 Mvariables/seconds.
*** *** ##
*** *** Step 600/600, 13.9s elapsed, 0.0s left
*** *** CFL = 0.08/0.40 - 0.06/0.42 adjusted: 0/0/0
*** *** ************************************************************************
*** *** End run_march . Elapsed time (sec) = 13.8993
*** ****************************************************************************
***
*** ****************************************************************************
*** *** Start run_postloop ...
*** *** ************************************************************************
*** *** Probe result at Pt/0#2014(0,0,0)601:
*** *** - rho = 0.970
*** *** - v = 0.015
*** *** - p = 0.958
*** *** Performance of tube:
*** ***   13.8375 seconds in marching solver.
*** ***   0.0230625 seconds/step.
*** ***   6.08991 microseconds/cell.
*** ***   0.164206 Mcells/seconds.
*** ***   0.82103 Mvariables/seconds.
*** *** Averaged maximum CFL = 0.286695.

To be
*** *** Step 584/600, 12.9s elapsed, 0.4s left
*** *** CFL = 0.21/0.71 - 0.15/0.99 adjusted: 0/0/0
*** *** Performance of tube:
*** ***   12.8693 seconds in marching solver.
*** ***   0.0220365 seconds/step.
*** ***   5.81898 microseconds/cell.
*** ***   0.171851 Mcells/seconds.
*** ***   0.859257 Mvariables/seconds.
*** *** ##
*** *** Step 592/600, 13.1s elapsed, 0.2s left
*** *** CFL = 0.21/0.71 - 0.15/0.99 adjusted: 0/0/0
*** *** Performance of tube:
*** ***   13.0406 seconds in marching solver.
*** ***   0.0220281 seconds/step.
*** ***   5.81676 microseconds/cell.
*** ***   0.171917 Mcells/seconds.
*** ***   0.859585 Mvariables/seconds.
*** *** ##
*** *** Step 600/600, 13.3s elapsed, 0.0s left
*** *** CFL = 0.21/0.70 - 0.15/0.99 adjusted: 0/0/0
*** *** ************************************************************************
*** *** End run_march . Elapsed time (sec) = 13.284
*** ****************************************************************************
***
*** ****************************************************************************
*** *** Start run_postloop ...
*** *** ************************************************************************
*** *** Probe result at Pt/0#2014(0,0,0)601:
*** *** - rho = 0.506
*** *** - v = 0.430
*** *** - p = 0.385
*** *** Performance of tube:
*** ***   13.222 seconds in marching solver.
*** ***   0.0220367 seconds/step.
*** ***   5.81905 microseconds/cell.
*** ***   0.171849 Mcells/seconds.
*** ***   0.859247 Mvariables/seconds.
*** *** Averaged maximum CFL = 0.736332.

LGTM.  But I am not sure I understand the purpose of average CFL.  It is required that $\mathrm{CFL}<1$, but not the average value.

LGTM. But I am not sure I understand the purpose of average CFL. It is required that $\mathrm{CFL}<1$, but not the average value.

It's my bad not elaborating the context well enough. Tuning the driving script is a task a while ago because the result shows CFL too small (see this comment). My goal is to move the shock tube out of sandbox folder and the shock tube becomes an official example on top of the "new (c++ re-written one)" code base.

LGTM. But I am not sure I understand the purpose of average CFL. It is required that $\mathrm{CFL}<1$, but not the average value.

It's my bad not elaborating the context well enough. Tuning the driving script is a task a while ago because the result shows CFL too small (see this comment). My goal is to move the shock tube out of sandbox folder and the shock tube becomes an official example on top of the "new (c++ re-written one)" code base.

Thanks for the elaboration.  I think we should keep in mind that averaging CFL over time does not carry a meaning.


Add unit tests of CDN system

Description
Completed unit test of CDN system

Related Issue
fix #237

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[x] Code compiles correctly.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Codecov Report

Merging #238 (1d61144) into main (83b90a1) will increase coverage by 0.30%.
The diff coverage is 67.94%.

@@            Coverage Diff             @@
##             main     #238      +/-   ##
==========================================
+ Coverage   40.74%   41.04%   +0.30%
==========================================
  Files          60       61       +1
  Lines        4759     4831      +72
==========================================
+ Hits         1939     1983      +44
- Misses       2575     2599      +24
- Partials      245      249       +4

Flag
Coverage Δ

unittests
41.04% <67.94%> (+0.30%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/source/httpprotocol/http_source_client.go
66.66% <66.66%> (ø)

client/daemon/peer/piece_manager.go
67.07% <100.00%> (+0.27%)
:arrow_up:

pkg/util/timeutils/time_utils.go
71.42% <100.00%> (+38.09%)
:arrow_up:

pkg/util/net/iputils/ip_utils.go
61.22% <0.00%> (-4.09%)
:arrow_down:

client/daemon/peer/peertask_stream.go
57.35% <0.00%> (-0.76%)
:arrow_down:

client/daemon/peer/peertask_base.go
32.76% <0.00%> (-0.73%)
:arrow_down:


fix FailoverRpcProvider import

Thanks for taking the time to submit a pull request!
If you haven't already, be sure to take a look at the CONTRIBUTING documentation to get up to speed with the practices in this repository.
When you're ready, switch to the "Preview" tab to select an applicable template:

General template (most common)
Wallet integration template

What problem does this address? That class is just re-exported from near-api-js, so this change should be a no-op.
Importing it like this only adds a dependency reference without adding it to package.json.

What problem does this address? That class is just re-exported from near-api-js, so this change should be a no-op.
Importing it like this only adds a dependency reference without adding it to package.json.

I keep getting this error whenever I start the multichain example and I end up just having to manually make that change in the node_modules.
TypeError: nearAPI.providers.FailoverRpcProvider is not a constructor     at new Provider (index.js:41:21)     at index.js:3054:15     at Generator.next (<anonymous>)     at fulfilled (index.js:27:58)

My guess is this happens because nearAPI is referencing an older version of near-api-js (one which doesn't export FailoverRpcProvider) but somehow  there is a more recent version of @near-js/providers installed as a secondary dependency. So it's important to determine where the issue originates because a fix like this, while convenient, further compounds the dependency issue.
Is there a GitHub issue you could link to this PR where you describe the problem in more detail? Would you mind please creating one if it does not exist and link it to this PR? I'm not sure how to reproduce this from your description.


Add TextAndImage and TextAndIcons to Gitbook documentation

Once we're done modifying the two new components, we should ensure they are added to the Gitbook Prismic Slice documentation with all valuable information and (ideally) examples linked in.

Done, although there's a TODO: for an example of the 'Text and image', which we currently only have on a Visual story behind a toggle.


passing arguments to helper syntax

Hey, @mquandalle! I have this particular markup and had to resort to native spacebars syntax for passing arguments to helper inside {{parentRegion _id}}.
.menu
  +each city
    .item(data-id='#{_id}') #{name} {{parentRegion _id}}

tpl.helpers
  city:-> Geo.find({type:'city'})
  parentRegion: (id)->
    id= new RegExp('^'+id.slice(0,7))
    Geo.findOne({_id:id,type:'region'}).name

I tried using +parentRegion(_id) as in https://github.com/mquandalle/meteor-jade/blob/master/README.md#components but this returned me plain text '+parentRegion(_id)'. So is there a way to do this natively in Jade?
ps more details https://forums.meteor.com/t/solved-call-helper-from-another-helpers-context-or-smth-like-that/

I am having this same issue.
I am trying to do:
input(type='text', name='birthday', placeholder='birthday', value='#{dateFormatter currentUser.profile.birthday}')

Where date Formatter is a global helper. For testing I defined it as so:
UI.registerHelper 'dateFormatter', (date) ->
  return date

So basically jade should output whatever parameter I input. But in the page I also see ''#{dateFormatter currentUser.profile.birthday}' output as a string.

:+1: i would even like to be able to use the parenthesis syntax if possible. Will check it soon if I have time, this one is annoying me too much :  input(value=(myHelper myParam))

I've modified a fork of this package to support passing arguments to helpers, together with a few other useful features. The fork has been released as dalgard:jade.
I will keep the new package in sync with the original, should there be any updates, and generally continue maintenance until, hopefully, the two packages can be merged.


Enables UISegmentedControl touch

@rastersize

Codecov Report

Merging #283 into master will decrease coverage by -0.08%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #283      +/-   ##
==========================================
- Coverage   93.48%   93.41%   -0.08%
==========================================
  Files          72       72
  Lines        5051     5055       +4
==========================================
  Hits         4722     4722
- Misses        329      333       +4

Impacted Files
Coverage Δ

sources/HUBComponentWrapper.m
74.39% <ø> (-0.91%)
:x:

sources/HUBUtilities.h
72.91% <ø> (ø)
:white_check_mark:

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 3ddf2d2...449536f. Read the comment docs.

I was intrigued by the fact that we were traversing the view hierarchy looking for specific subclasses and created an alternative PR - https://github.com/spotify/HubFramework/pull/285

I’d be in favour of merging this (after changing to look for UIControl) and the concept of #285 into a single change. That is:

Look for a gesture controller ala. #285 if not found proceed to,
Go through the view hierarchy and look for a UIControl.

@mhallendal @marmelroy @mumme What do you think of this ☝


Denied error when pulling image

Just trying to pull the image to test it out and it is failing even thought I am logged in.
docker pull ghcr.io/alexjustesen/speedtest-tracker:latest
Error response from daemon: Head "https://ghcr.io/v2/alexjustesen/speedtest-tracker/manifests/latest": denied: denied

I don't think that's something with the registry specifically but you can also try the Docker Hub if GitHub container registry is having issues.
https://hub.docker.com/repository/docker/ajustesen/speedtest-tracker


Complex actions supported?

In Easystroke I have a guesture like this:
38 0 10 Gesture 14 5
39
40 1 1 10
41 0 1 5 0 0 32768 14
42
43 0 65366 0 21 3+wheeldown=page down 5
44
45 1 1 10
46 0 1 1 0 0 32768 14
47
48 67108864 65289 0 3 3+1 5
49
50 1 1 10
51 0 1 2 0 0 32768 14

Which if I hold right_click and use the mouse wheel, it'll send page_up and page_down events. I can not find anyway to replicate this behavior in mouse-actions.

I already have a feature request in place to allow mouse buttons to be used as modifiers, which is what's required to make this possible.
For me it's holding right click and sending on wheel events ctrl+tab/ctrl+shift+tab (so I can scroll through tabs with the mouse wheel.)
When mouse buttons can be used as modifiers, then we can use the rightclick as the modifier and the scroll wheel to send out commands using the 'click' gesture type.


code path

I run the setup.py to install retinanet ,where is the code be install ?

If you are using the NGC container, the installed directory for python API depends on whether you used the -e flag or not in pip install
I f you didn't use it, the location should be in /opt/conda/lib/python3.6/site-packages/retinanet
If you used the -e flag the install directory is the /workspace/retinanet-examples

I don't see the code in the /opt/conda/lib/python3.6/site-packages/retinanet


Table Header Width Bug, When There's Row Selection Configuration

I think there's complains about Table Header and Table Body column mismatch. But I want to dig a little bit deeper, maybe could help you find the root cause.
Test Version v3.1.0, with all the css files there.
OK, so this is the first one. I have the row_selection configurations, something like these:
selectRow = {{
	mode: 'radio',
	selected: [this.activeParameterKey],
}}

I also set some columns' width, to test the alignment problem, I delete unnecessary fields.
<TableHeaderColumn width="300">Key</TableHeaderColumn>
<TableHeaderColumn width="150">Value Type</TableHeaderColumn>
<TableHeaderColumn width="50">Example Values</TableHeaderColumn>
<TableHeaderColumn>Technical Description</TableHeaderColumn>
<TableHeaderColumn>Required</TableHeaderColumn>
<TableHeaderColumn>Server Side</TableHeaderColumn>
<TableHeaderColumn width="200">Heimdall</TableHeaderColumn>
<TableHeaderColumn>Beacon Key</TableHeaderColumn>
<TableHeaderColumn>Event Key</TableHeaderColumn>
<TableHeaderColumn width="200">Value Unit</TableHeaderColumn>

The Results are showing below:

So here's the problem. For the  of selection button column, it takes the width of "Key" column, which is 300. For the  of "Key" column, it takes the width of "Value Type" column, which is 150. For the  of "Value Type" column, it takes the width of "Example Values" column, which is 50. For the  of "Example Values" Column, it takes itself width, which is 50, it is correct.
It looks so wired to me, but it looks like a column takes itself setting of width, but if the column after it has a width setting, it will overwrite current column width setting.
Same things happens to "Heimdall" column, both "Heimdall" and "Server Side" column are setting to 200. Also "Value Unit".
But the width in Table Body is all correct. Do you think this could be fixed soon? Or maybe I could look into the code.

have the same problem, when I go to 3.1.0 I get this bug, when I go back to 3.0.0-beta.11 its all good again
seems like even with hideSelectColumn: true, the selectrow header is being rendered

hi, sorry for lately reply, busy on my work. Maybe you can check https://github.com/AllenFang/react-bootstrap-table/issues/1006 firstly and actually, the unalign issue still happen until now. and it's pretty hard to fix, it maybe a edge case or something, for me I usually cant reproduce this issue, so if you have a repo which can reproduce it, it's welcome :)
BTW, most of people give me the example code, but I always cant reproduce at my local.

Hi @AllenFang, Its pretty easy to reproduce. Just set different width for each TableHeaderColumn and set height and scrollTop for BootstrapTable. Now when the scroll the scroll is enabled, you can see this problem immediately or you can do the either of the following,

open Chrome debugger or inspect an element, (or)
enable column filter and click on any of the column.

i also have this (or similar) issue with 3.1.1 : column width is applied to wrong header columns if selectRow is present.
its very easy to reproduce, just this:
class Items extends React.Component {
  render() {
    return(
      <BootstrapTable data={this.props.items} selectRow={ { mode: 'radio' } } >
        <TableHeaderColumn dataField="ID" isKey={true} width="30">ID</TableHeaderColumn>
        <TableHeaderColumn dataField="Title" width="1000">Title</TableHeaderColumn>
      </BootstrapTable>
      )
    }
}

result:
and then i try same code except without selectRow, then width is applied to correct columns:

class Items extends React.Component {
  render() {
    return(
      <BootstrapTable data={this.props.items}>
        <TableHeaderColumn dataField="ID" isKey={true} width="30">ID</TableHeaderColumn>
        <TableHeaderColumn dataField="Title" width="1000">Title</TableHeaderColumn>
      </BootstrapTable>
      )
    }
}

result:

I'll fix it asap, sorry for lately reply and fixing.

@snusmu, I cant reproduce your issue,

if you have upgrade the react-bootstrap-table, please remember to replace the css file as newest one(react-bootstrap-table.min.css)

Hi Allen, I still have this problem and with this version   "version": "3.1.8"
and I also applied import 'react-bootstrap-table/dist/react-bootstrap-table.min.css' already
this code is workaround for me temporarily if I put width onto datefield='dev' it will break the column size
      <BootstrapTable         data={ dataSource }         deleteRow={ true }         selectRow={ selectRowProp }         options={ options }         cellEdit={ cellEditProp }         insertRow={ true }         exportCSV={ true }         search={ true }         multiColumnSearch={ true }         pagination         keyBoardNav       >           <TableHeaderColumn dataField='dev' isKey={ true } dataSort>dev name</TableHeaderColumn>           <TableHeaderColumn width="200" dataField='status' dataSort>Status</TableHeaderColumn>           <TableHeaderColumn width="200"  dataField='price' dataSort>Price</TableHeaderColumn>       </BootstrapTable>
see the screenshots:
no width for the dataField='dev'

after I put
<TableHeaderColumn width="200" dataField='dev' isKey={ true } dataSort>dev name

Is there any solution yet for this issue?

Hi, just let you know also, if I put the width with px, everything will run smoothly.
So, it would be :
<TableHeaderColumn width="200px" dataField='dev' isKey={ true } dataSort>dev name</TableHeaderColumn>
rather than
<TableHeaderColumn width="200" dataField='dev' isKey={ true } dataSort>dev name</TableHeaderColumn>

@hnandarusdy, got it, but as I know, the width of TableHeaderColumn are support integer, string or string with px.


newName property in SampleApp class in unused

The newName property is the SampleApp class is not used. It's a little confusing since the parameter to addnew is named "newname" as well.

Thanks for the catch! :-)

No problem. Thanks for writing this. I have been playing with it for a couple of days now and just noticed that.


numberList and bulletList controls mixed up??

Is it just me or has anyone noticed the controls "numberList " and "bulletList" seems to be mixed up?
controls={['numberList']} // adding this is giving me bullet points controls to my rte component
controls={['numberList']} // and this is giving me numbered points controls

I think you are trying on an old version. Please use the latest one.


Fix window_get_current_screen for X11 display server

This method used to check which screen contains the top-left corner of the window (and default to the first screen in case none is found), which is not accurate in some cases.
Now the area of overlap with each screen is calculated, so we can get the best candidate based on the window's position.
This makes window_get_current_screen consistent with Windows platform, and fixes an issue where popups appear on the main screen when the main window is slightly moved outside of the desktop on the top or left.

How does this PR compare to the older https://github.com/godotengine/godot/pull/37506? Should we close #37506 since it has lots of conflicts that may not be resolved?

Both are potentially valid changes.
This PR just fixes the way the screen is selected for a given window position on Linux, to make it more reliable, and consistent with Windows platform. It might supersede the X11 part of #37506 but I'm not 100% sure.
#37506 does more general improvements on multi-screen configurations for all platforms. It was done before some heavy changes in the display servers and popup windows, so it would need to be checked again to make sure the way it's implemented still makes sense.

Rebased.

Is this still relevant for current master? Also, there seems to be partial overlap with changes in #41565. Both should likely be rebased and re-tested, and if we can't find an X11 expert to review them, maybe just merged and tested in 4.0 alpha to see how it fares?


Add support for Desktop

Please add support for insetsx Desktop platform.

I'm not familiar with desktop application, does desktop also have window insets?
Or is a stub that returns all zeros sufficient?

@mori-atsushi I think Desktop does not have window insets as such.
But we can have support in the library so that it can be used in KMP applications.
For now, this is what I'm using in desktopMain:
actual val WindowInsets.Companion.navigationBars: WindowInsets
    @Composable
    @NonRestartableComposable
    get() = WindowInsets(0, 0, 0, 0)

actual val WindowInsets.Companion.statusBars: WindowInsets
    @Composable
    @NonRestartableComposable
    get() = WindowInsets(0, 0, 0, 0)

actual val WindowInsets.Companion.systemBars: WindowInsets
    @Composable
    @NonRestartableComposable
    get() = WindowInsets(0, 0, 0, 0)

@ExperimentalSoftwareKeyboardApi
actual val WindowInsets.Companion.ime: WindowInsets
    @Composable
    @NonRestartableComposable
    get() = WindowInsets(0, 0, 0, 0)

@ExperimentalSoftwareKeyboardApi
actual val WindowInsets.Companion.safeDrawing: WindowInsets
    @Composable
    @NonRestartableComposable
    get() = WindowInsets(0, 0, 0, 0)

This is working fine for me.

Thank you for teaching me.
I'm currently working on another feature, so I'll work on this later.

Yes, zero stubs would be enough. We added the library to our Compose experiment: https://github.com/Kotlin/kmm-production-sample/tree/compose-app
and it works perfectly, but I'm waiting for desktop support as well.

Desktop support has been added in v0.1.0-alpha06.
Thank you all for your comments.
https://github.com/mori-atsushi/insetsx/releases/tag/v0.1.0-alpha06

Don't you plan to add web target as well? 😆

Don't you plan to add web target as well? 😆

If you create the Issue, I'll consider it 👍


Implement support for apple-appattest attestation format

Resolves #319

Codecov Report

Merging #322 (0d91c9d) into master (b6f7642) will decrease coverage by 0.36%.
The diff coverage is 57.77%.

@@            Coverage Diff             @@
##           master     #322      +/-   ##
==========================================
- Coverage   77.41%   77.05%   -0.37%
==========================================
  Files          87       88       +1
  Lines        2404     2449      +45
  Branches      402      413      +11
==========================================
+ Hits         1861     1887      +26
- Misses        443      451       +8
- Partials      100      111      +11

Impacted Files
Coverage Δ

Src/Fido2/AttestationFormat/Apple.cs
93.54% <ø> (ø)

Src/Fido2/AuthenticatorAttestationResponse.cs
88.57% <0.00%> (-1.82%)
:arrow_down:

Src/Fido2/AttestationFormat/AppleAppAttest.cs
59.09% <59.09%> (ø)

Src/Fido2/TypedString.cs
21.05% <0.00%> (+5.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[bug]: (specific) Flux Lora's causing AssertionError

Is there an existing issue for this problem?

[X] I have searched the existing issues

Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
4090
GPU VRAM
24
Version number
5.2.0
Browser
Firefox 131.0.3
Python dependencies
No response
What happened
I've added a Lora from DrMando, used the Flux Dev Quantized model (as provided by InvokeAI) added a prompt, and hit generate. Which caused this error:
[2024-10-22 04:57:50,535]::[InvokeAI]::ERROR --> Error while invoking session fe0e6b5c-0f6f-4256-91c8-750d9317b346, invocation d5c79114-75f9-4530-a101-e0d28c4c9b0c (flux_text_encoder):  [2024-10-22 04:57:50,535]::[InvokeAI]::ERROR --> Traceback (most recent call last):   File "G:\Data\Packages\InvokeAI\invokeai\app\services\session_processor\session_processor_default.py", line 129, in run_node     output = invocation.invoke_internal(context=context, services=self._services)   File "G:\Data\Packages\InvokeAI\invokeai\app\invocations\baseinvocation.py", line 290, in invoke_internal     output = self.invoke(context)   File "G:\Data\Packages\InvokeAI\venv\lib\site-packages\torch\utils\_contextlib.py", line 116, in decorate_context     return func(*args, **kwargs)   File "G:\Data\Packages\InvokeAI\invokeai\app\invocations\flux_text_encoder.py", line 51, in invoke     clip_embeddings = self._clip_encode(context)   File "G:\Data\Packages\InvokeAI\invokeai\app\invocations\flux_text_encoder.py", line 100, in _clip_encode     exit_stack.enter_context(   File "contextlib.py", line 492, in enter_context   File "contextlib.py", line 135, in __enter__   File "G:\Data\Packages\InvokeAI\invokeai\backend\lora\lora_patcher.py", line 42, in apply_lora_patches     for patch, patch_weight in patches:   File "G:\Data\Packages\InvokeAI\invokeai\app\invocations\flux_text_encoder.py", line 121, in _clip_lora_iterator     lora_info = context.models.load(lora.lora)   File "G:\Data\Packages\InvokeAI\invokeai\app\services\shared\invocation_context.py", line 370, in load     return self._services.model_manager.load.load_model(model, _submodel_type)   File "G:\Data\Packages\InvokeAI\invokeai\app\services\model_load\model_load_default.py", line 70, in load_model     ).load_model(model_config, submodel_type)   File "G:\Data\Packages\InvokeAI\invokeai\backend\model_manager\load\load_default.py", line 56, in load_model     locker = self._load_and_cache(model_config, submodel_type)   File "G:\Data\Packages\InvokeAI\invokeai\backend\model_manager\load\load_default.py", line 77, in _load_and_cache     loaded_model = self._load_model(config, submodel_type)   File "G:\Data\Packages\InvokeAI\invokeai\backend\model_manager\load\model_loaders\lora.py", line 76, in _load_model     model = lora_model_from_flux_diffusers_state_dict(state_dict=state_dict, alpha=None)   File "G:\Data\Packages\InvokeAI\invokeai\backend\lora\conversions\flux_diffusers_lora_conversion_utils.py", line 171, in lora_model_from_flux_diffusers_state_dict     add_qkv_lora_layer_if_present(   File "G:\Data\Packages\InvokeAI\invokeai\backend\lora\conversions\flux_diffusers_lora_conversion_utils.py", line 71, in add_qkv_lora_layer_if_present     assert all(keys_present) or not any(keys_present) AssertionError
What you expected to happen
I've expected it to work, not exactly sure what to write here.
How to reproduce the problem
No response
Additional context
I've asked DrMando and if he (hopefully) responds, I can attach more info to what he used to train it or where they train it.
Discord username
No response

For training they use CivitAI's Flux Training, especially the "rapid" setting.

I had this also happen when using specific models (checkpoints) of FLUX. Which one are you using?

having same error when trying to use Hyper FLUX 8 Steps LoRA from ByteDance with flux dev qantized

I'm getting this error too, not only for this lora (https://civitai.com/models/781497/dreamy-illustrations-flux-lora?modelVersionId=873972) but also a Lora of my friend that I trained myself on Civitai using rapid lora.


Sometimes edge seems not respecting enclose

Please refer to the following image:

At (7, 0), (7, 3) and (12, 0), the edges do not respect the enclose property and directly go through the node.
This happens if the node spans over 3 or more distance units, only the <row_span> - 2 units in the center will be regarded as node.
Source Code:
  diagram(
    node-stroke: 1pt,
    node-outset: 1mm,
    spacing: (5mm, 5mm,),
    debug: 100,
    {
      node((0, 0), [PC])

      node((2, 0), [Inst. Mem.])

      node([MUX], enclose: ((5, 2), (5, 3)))

      node([Reg. File], enclose: ((7, 0), (7, 1), (7, 2), (7, 3)))
      node((7, 4), [Sign Ext.])

      node([MUX], enclose: ((9, 1), (9, 2)))

      node([ALU], enclose: ((10, 0), (10, 1)))

      node([Data Mem.], enclose: (((12, 0), (12, 1), (12, 2), (12, 3))))
      node([MUX], enclose: ((12, 5), (12, 6)))

      edge((0, 0), "rr", "->")

      edge((2, 0), "r", "->")

      edge((3, 0), "rtrbrr", "->")
      edge((3, 0), "b,rrrr", "->")
      edge((3, 0), "bb,rr", "->")
      edge((3, 0), "bbb,rr", "->")
      edge((3, 0), "bbbb,rrrr", "->")

      edge((5, 2), "rr", "->")

      edge((7, 0), "rrr", "->")
      edge((7, 1), "rr", "->")
      edge((7, 4), "r,tt,r", "->")

      edge((9, 1), "r", "->")

      edge((10, 0), "rr", "->")

      edge((11, 0), "bbbb,rr,b,l", "->")
      edge((12, 0), "rr,bbbbbb,ll", "->")
      edge((12, 5), "llllll,tt,r", "->")
    }
  )

I am using the latest version of fletcher on the main branch.

After reading the manual again, seems that the edge only respect pos but not enclose? Now I am not sure if it is a feature or bug.

You can fix this by setting the snap-to argument of edge().
Usually, edges automatically snap to the nearest node. However, nodes which enclose many points are hard, because what if there are smaller nodes inside? Should the edge snap to the inner node or larger node? I couldn't decide, so instead added the snap-to argument as a manual override.

```typc
diagram(
	node-stroke: 1pt,
	node-outset: 1mm,
	spacing: (5mm, 5mm,),
	debug: 100,
	{
		node((0, 0), [PC])
	node((2, 0), [Inst. Mem.])

	node([MUX], enclose: ((5, 2), (5, 3)))

	node([Reg. File], enclose: ((7, 0), (7, 1), (7, 2), (7, 3)), name: <reg>)
	node((7, 4), [Sign Ext.])

	node([MUX], enclose: ((9, 1), (9, 2)))

	node([ALU], enclose: ((10, 0), (10, 1)))

	node([Data Mem.], enclose: (((12, 0), (12, 1), (12, 2), (12, 3))))
	node([MUX], enclose: ((12, 5), (12, 6)))

	edge((0, 0), "rr", "->")

	edge((2, 0), "r", "->")

	edge((3, 0), "rtrbrr", "->", snap-to: (auto, <reg>))
	edge((3, 0), "b,rrrr", "->")
	edge((3, 0), "bb,rr", "->")
	edge((3, 0), "bbb,rr", "->")
	edge((3, 0), "bbbb,rrrr", "->")

	edge((5, 2), "rr", "->")

	edge((7, 0), "rrr", "->", snap-to: (<reg>, auto))
	edge((7, 1), "rr", "->")
	edge((7, 4), "r,tt,r", "->")

	edge((9, 1), "r", "->")

	edge((10, 0), "rr", "->")

	edge((11, 0), "bbbb,rr,b,l", "->")
	edge((12, 0), "rr,bbbbbb,ll", "->")
	edge((12, 5), "llllll,tt,r", "->", snap-to: (auto, <reg>))
}

)

Yeah, that's a good point. Maybe snapping to the wrong node is better than not snapping at all.


ODS Lib Release - Create a DSM page to clarify this usage process

A current question is to see if the code doc  intro could also be added in this ressources page

Update of this page has been made in https://zeroheight.com/3b9fee398/v/latest/p/0928bb-ods-android-librairy.
It needs to be reviewed and published


Deleting user data in Manitoba switches content to BC

Deleting user data in MB switches the content to BC, but the headers still show "Start settling in Manitoba".
Tested on Staging V 1.70.0 on iPhone XS
https://images.zenhubusercontent.com/99282566/b3388cf6-25d7-4614-bc91-24b9398e8d9c/rpreplay_final1625259217.mp4
Steps to reproduce:

Open the app in Manitoba.
Open Help page
Click "Delete user data"
Notice that the links in the Help page are now for BC211 and BC services
Close the Help page -> go back to Home, the title says "Start settling in Manitoba" but the content is all BC content.

Acceptance Criteria

[ ]  Clicking "Delete user data" clears user questionnaire and bookmarks, but keeps user in the same province, OR forces restart of the app (takes them back to the Welcome screen)

Steps for QA:

Note that also the language selection and province selection menus go awry after deleting user data and being in MB:
https://user-images.githubusercontent.com/21990736/124330785-f9311500-db42-11eb-8d1f-5298d80d3484.MP4

Province reverts to BC on deleting all data: this is as designed, BC is the default province, and when we delete all data from the app, it reverts to the default for all settings, including region.

Except for the fact that the title still says Manitoba. But I would disagree that this is "as designed". Deleting all user data does not equate to a user realizing they will switch provinces. I would do a force exit back to the Welcome screen in that case.


ViewModel is disposed 5-10 secs after scoped composable dispose

ViewModel is disposed ~5-10 secs after scoped composable dispose. In this duration viewModel is alive and the flows inside it is triggered. Why viewmodels are disposed after a curtain amount of time? Shouldn't this be disposed properly with the scoped composable? Thanks in advance.
Ex: Dispose times from logcat
2023-03-20 00:32:28.561 Composable onDispose
2023-03-20 00:32:33.569 ViewModel onCleared

In this case, it is delayed to survive a possible configuration change.
The long answer is:
There are some edge cases when a Composable is disposed and then it's part of the screen's composition after a configuration change (rotation, dark mode, wallpaper-change, etc). In these cases, the library uses the same delay Android recommends to survive state after a configuration change (see WhileSubscribed(5000) in this Android doc page).

The question was answered so closing the issue. Feel free to let me know if you have more questions.

Consider replacing the WhileSubscribed(5000) with what this blogpost describes in order to achieve keeping the flow active during config changes, and stops immediately when the subscribed UI goes away. :)
https://blog.p-y.wtf/whilesubscribed5000

Thanks for the tip @chris6647, I'll take a look.

Thanks to the suggestion from @chris6647 the delay mentioned in this ticket has been remove as part of PR #32
The new behavior (with clear of ViewModel immediately after the Composable is disposed of) is available from version https://github.com/sebaslogen/resaca/releases/tag/3.0.0 🎉


Link to swift.org in README

Add a link to swift.org where "Swift.org" occurs in the README

lgtm, cq+, do the thing

Dupe of #180

As I said in #180, I don't think this really adds anything—it's referring to the online community more than the actual website. Thanks, though.


Employ Travis and Appveyor

Test it works on Windows (#1)

Skipping Appveyor because it costs money. Fixed Travis usage in 8fe8717


typo fixes in docs

I just stumbled upon this library earlier today; thanks for open-sourcing it! I was curious about how it's different from TensorFlow, Theano, Torch, etc. and just read through the docs ... while reading, I found a few minor typos that I fixed on the fly.

Hi rasbt and thank you for your fixes. The main difference here is that this library was built from scratch with the goal of handling large amounts of sparse data (which we have a lot of in Recommendations). It automatically scales across GPUs for Model Parallelism, which is a great benefit as our models go beyond the 12GB memory currently offered in a Titan X, while also increasing the speed as you add more GPUs.
However, it does not  support other features more commonly supported in the other libraries you've mentioned, such as CNNs.
We built it to solve our specific problems, and as it turns out, it does a great job at that :)

@benitezmatias Thanks for the additional info! First, when I read the announcement, I thought, "hm, do we (programmers who are not directly affiliated with the company or research group) really need yet another deep learning library" ... when I read through the FAQ, and as you mentioned, it's pretty awesome to see that DSSTNE tackles a particular use case or niche: Sparse features, which are common in recommendation systems. Although I don't have a particular use case for that at the moment (still in Academia), it's a nice option to have that I will keep on my radar. Actually, I may already have an interesting application in mind down the road (working with protein structural data). In any case, thanks for sharing it with the world :)


[BUG] Reading accented characters cause problem from Excel file

🐛 Bug Report
I am trying to read a file containing Polish-accented characters. Everything seems normal, but JavaScript cannot match it when I check with the equal operator, indexOf, or includes function.
Lib version: 4.3.0
Steps To Reproduce

For example, the word is dzień.
const columns = ["dzień","and so on"];
const workbook = new excelJs.Workbook();
await workbook.xlsx.readFile(filePath);
const dataSheet = workbook.getWorksheet('Sheet');
var row = dataSheet.getRow(1);
var rowColumn = row.values[1];
console.log(MD5(rowColumn.toString()).toString());
console.log(MD5(columns[0]).toString());
console.log(MD5('dzień').toString());
console.log(rowColumn == columns[0]);
console.log('#' + rowColumn + '#')
console.log('#' + columns[0] + '#');

Here is the console output of the code above
47b1c8910533a68444a574ca2907ec29
b46f08c14c441ac65c75d15457f63db4
b46f08c14c441ac65c75d15457f63db4
false
#dzień#
#dzień#

@bahadirarslan Can you provide your excel file and add the MD5 specific code?

@bahadirarslan Can you provide your excel file and add the MD5 specific code?

For MD5, I used crypto-js library
var MD5 = require("crypto-js/md5");
A sample excel file is attached.
polish.xlsx

@bahadirarslan  Your excel cell 'dzień' has an extra space in front of it，remove the space is correct

(async ()=>{
    const columns = ["dzień","and so on"];
    const workbook = new excelJs.Workbook();
    await workbook.xlsx.readFile('polish.xlsx');
    const dataSheet = workbook.getWorksheet('Sheet');
    var row = dataSheet.getRow(1);
    var rowColumn = row.values[1];
    console.log(MD5(rowColumn.toString()).toString());
    console.log(MD5(columns[0]).toString());
    console.log(MD5('dzień').toString());
    console.log(rowColumn == columns[0]);
    for (let index = 0; index < rowColumn.length; index++) {
        const element = rowColumn[index];
        console.log('#index-->' + element + '<--#')
    }
    console.log('#' + rowColumn.length + '#' + columns[0].length)
    console.log('#' + rowColumn + '#')
    console.log('#' + columns[0] + '#');
})()

This is unbelievable.
Thank you, I've never thought such a thing.

@bahadirarslan Since it seems that exceljs is no longer releasing new versions, you can pay attention to this project. @zurmokeeper/exceljs

I will have a look, thank you.


Kpack 1.0.3 breaks source image uploads for some users

Our archive code is too strict in expecting tar files to have directory headers, we should relax that requirement and simply mkdirall when extracting files from tars.

https://buildpacks.slack.com/archives/CQ10WHMT4/p1603990803024300


remove praticle snow

Hello, I hope you're well. I would like to have instructions on how to remove the praticle snow on certain pages. I have integrated it into my site so that it animates on all pages and works correctly, but I would like it to stop when certain pages are opened.

Please open an issue on the tsParticles repository. This is about the website only.


Doc 2525 list tutorial code examples in C#

Code samples for List datatype page.

Closes #213

Task closed by https://github.com/redis/NRedisStack/pull/324


Migrate to shared history dev and prod

@lucasgarfield No offense but shouldn't the PR description be at least what was in the PR it superseded?


Please bump containers upperbound

I have successfully compiled with containers-<IP_ADDRESS> and ghc-8.10.3. Things compile and tests pass.
If you are able to make this change and release a new version, it will allow us to better package this project in gentoo.

Based on a conversation in IRC, we've decided to remove this package from gentoo. Closing this ticket.

Based on a conversation in IRC, we've decided to remove this package from gentoo. Closing this ticket.

Hello @ezzieyguywuf. Noted. Please, let me know if any other request comes up.

Hello @ezzieyguywuf. Noted. Please, let me know if any other request comes up.


Replaced Buffer with TextEncoder

This resolves the issue identified in #3
Buffer only works in Node, whereas TextEncoder works in Browser and Edge runtimes.
It's a tiny change and the existing tests passed. Also tested it on Edge runtime and it works.
Hope this is okay.

@parasdaryanani Thanks so much for the change!
Due to a quirk of our internal setup, I need to accept PRs in our opensource monorepo instead, and then they'll automatically be published here. The corresponding file is here: https://github.com/jetpack-io/opensource/blob/main/typeid/typeid-js/src/base32.ts
Do you mind opening the PR there and I'll accept it?

@loreto sure no worries, all done!

Closing since we already submitted the change in the opensource repo.


feat: add framework name to the test classes BSP request

Implementation of https://github.com/build-server-protocol/build-server-protocol/pull/300
I wanted to do as few changes as possible to not break compatibility or change the codebase completely. For now, I'll create this PR as a draft to see the test results and your opinion about it.

Main question is: am I allowed to modify already defined keys or should I create new ones and include this logic here while leaving already existing keys untouched?

There is an error in tests:
Compile / loadedTestFrameworks from Compile / bspScalaTestClassesItem ((sbt.internal.server.BuildServerProtocol.configSettings) BuildServerProtocol.scala:303)
Did you mean Test / loadedTestFrameworks ?

but I don't know how to deal with it.

loadedTestFrameworks is not implemented in the Compiler config.
You can work around this using Keys.loadedTestFrameworks.?.value that should give you a Option[Seq[Framework]] that you can flatten.

Superseded by https://github.com/sbt/sbt/pull/6830


Made fixes to remove vulnerability and allow extraction and insertion…

… of HMAC a safe way

+1 I think this is a very important security fix that needs to be accepted as soon as possible.

Good catch! Is there any direct risk for people running nodes?

@EliasZ Yes! They can invalidate your node by using your HMAC. This means you can't use the same ETH address with your node again.

Also it makes you vulnerable for any exploits there might be in the dockerized version of redis and postgres.. I would recommend shutting down the node or fixing yourself for now.

This issue has been resolved in commit https://github.com/chainpoint/chainpoint-node/commit/d58fb3ef1af1b501f02f33c3437ddebe8d088056
In the future please report any security related vulnerabilities privately. We can be contacted at<EMAIL_ADDRESS>and we adhere to the principles of responsible disclosure.
https://en.wikipedia.org/wiki/Responsible_disclosure