sev/ghcb Add #VC handler tests

Adds tests that make sure a #VC exception is raised while executing various instructions and that the #VC handler properly handles them via the ghcb. Instructions tested are cpuid and port IO.
Looking for feedback on the following:

Is the raw-cpuid dependency OK, or would it be better to just use inline asm or something else?
What's a good location to put these? I chose ghcb.rs, but they might make more sense somewhere else.
I have tests for other #VC handler cases such as ones for msrs, dr7, wbinvd, rdtsc, mmio, and other IOIO instructions, but they fail since those cases aren't handled in the svsm handler. I could add these as #[should_panic] if we think they might be useful later.
I did not test these with qemu since it doesn't work on hardware I have. The IOIO tests rely on a "testdev" device that echos characters sent to a specific port. I'm pretty sure qemu has a compatible device, but it might need to be explicitly enabled.

@p4zuu please take a look.

One of the new tests triggers an assertion:
[SVSM] test sev::ghcb::test::test_port_io_16 ...
[SVSM] ERROR: Panic: CPU[0] panicked at kernel/src/sev/ghcb.rs:664:9:
assertion `left == right` failed
  left: 17185
 right: 65535

Is that a known issue?

One of the new tests triggers an assertion:
[SVSM] test sev::ghcb::test::test_port_io_16 ...
[SVSM] ERROR: Panic: CPU[0] panicked at kernel/src/sev/ghcb.rs:664:9:
assertion `left == right` failed
  left: 17185
 right: 65535

Is that a known issue?

The current CPUID #VC handler actually doesn't use the GHCB. It directly looks into the registered CPUID table. That's maybe the reason, the GHCB is not modified while handling a CPUID.

Is the raw-cpuid dependency OK, or would it be better to just use inline asm or something else?

If it's not too much work, I would actually prefer inlining asm here, just to reduce the supply-chain attack surface.
Since this is for testing only, I think we only need a minimal implementation.

What's a good location to put these? I chose ghcb.rs, but they might make more sense somewhere else.

I am unsure too. Actually the CPUID handling of the current #VC handler is not touching the GHCB since it directly reads into the registered CPUID table (instead of calling the HV), so that might be an argument to move this somewhere else.
Moreover, the purpose of this is to verify the #VC handler's behaviors, so I would simply put it into kernel/src/cpu/vc.rs.

I have tests for other #VC handler cases such as ones for msrs, dr7, wbinvd, rdtsc, mmio, and other IOIO instructions, but they fail since those cases aren't handled in the svsm handler. I could add these as #[should_panic] if we think they might be useful later.

Yes, even if we currently don't support those, I agree with adding them as #[should_panic].

I did not test these with qemu since it doesn't work on hardware I have. The IOIO tests rely on a "testdev" device that echos characters sent to a specific port. I'm pretty sure qemu has a compatible device, but it might need to be explicitly enabled.

I can try taking a look at this since I'm using qemu :)

Is the raw-cpuid dependency OK, or would it be better to just use inline asm or something else?

If it's not too much work, I would actually prefer inlining asm here, just to reduce the supply-chain attack surface. Since this is for testing only, I think we only need a minimal implementation.

Rust provides a CPUID function for convenience:
https://doc.rust-lang.org/beta/core/arch/x86_64/fn.__cpuid.html

What's a good location to put these? I chose ghcb.rs, but they might make more sense somewhere else.

I am unsure too. Actually the CPUID handling of the current #VC handler is not touching the GHCB since it directly reads into the registered CPUID table (instead of calling the HV), so that might be an argument to move this somewhere else. Moreover, the purpose of this is to verify the #VC handler's behaviors, so I would simply put it into kernel/src/cpu/vc.rs.

I agree with this.

I have tests for other #VC handler cases such as ones for msrs, dr7, wbinvd, rdtsc, mmio, and other IOIO instructions, but they fail since those cases aren't handled in the svsm handler. I could add these as #[should_panic] if we think they might be useful later.

Yes, even if we currently don't support those, I agree with adding them as #[should_panic].

Perhaps something like #[ignore = "not yet supported"] would be better. #[must_panic] is not really supported inside the SVSM and these tests won't run outside.

One of the new tests triggers an assertion:

This doesn't happen with the google hypervisor, so I'm assuming it's an issue with the qemu testdev device. I'll try to figure out if it intentionally doesn't support 16-bit echos, but if so then I may just need to disable this test or modify qemu. Since I don't have a way of testing with qemu, it'd be nice to get some help here.

If it's not too much work, I would actually prefer inlining asm here, just to reduce the supply-chain attack surface.

Done

I would simply put it into kernel/src/cpu/vc.rs.

Done

Yes, even if we currently don't support those, I agree with adding them as #[should_panic].

Added a bunch more tests. Unfortunately, these tests are untested, but should be a decent starting point once support for those operations are added in the #VC handler.

One of the new tests triggers an assertion:

This doesn't happen with the google hypervisor, so I'm assuming it's an issue with the qemu testdev device. I'll try to figure out if it intentionally doesn't support 16-bit echos, but if so then I may just need to disable this test or modify qemu. Since I don't have a way of testing with qemu, it'd be nice to get some help here.

I've investigated this using QEMU. You need to add the pc-testdev device to the QEMU configuration for the test port to be active. Applying this patch to your branch fixes the tests for me:
diff --git a/scripts/launch_guest.sh b/scripts/launch_guest.sh
index b638303..9ebab2f 100755
--- a/scripts/launch_guest.sh
+++ b/scripts/launch_guest.sh
@@ -14,6 +14,7 @@ SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )
 C_BIT_POS=`$SCRIPT_DIR/../utils/cbit`
 DEBUG_SERIAL=""
 QEMU_EXIT_DEVICE=""
+QEMU_TEST_IO_DEVICE=""

 while [[ $# -gt 0 ]]; do
   case $1 in
@@ -38,6 +39,7 @@ while [[ $# -gt 0 ]]; do
       ;;
     --unit-tests)
       QEMU_EXIT_DEVICE="-device isa-debug-exit,iobase=0xf4,iosize=0x04"
+      QEMU_TEST_IO_DEVICE="-device pc-testdev"
       shift
       ;;
     -*|--*)
@@ -110,6 +112,7 @@ $SUDO_CMD \
     -monitor none \
     -serial stdio \
     $DEBUG_SERIAL \
-    $QEMU_EXIT_DEVICE
+    $QEMU_EXIT_DEVICE \
+    $QEMU_TEST_IO_DEVICE

 stty intr ^C

You need to add the pc-testdev device to the QEMU configuration for the test port to be active.

Thanks! I applied that commit to this PR

We already have read_msr() / write_msr() in kernel/src/cpu/msr.rs, could you reuse those?

Whoops, didn't notice them. Changed to use those.

I'd favor just using slice::from_raw_parts(), which is also less convoluted in my opinion. Also, you can test that at least one byte changed more easily with Iterator::any():

Thanks, I applied that change.

LGTM too, thanks Adam!


New options: quote start and stop strings

--quotechar is not enough in some cases. There can be two different strings enclosing a quote/text.

Examples/evidence?

Yes, the data I have in front of me contains such string-values between ",":
<![CDATA[This is string, and this is the rest of the string]]>

(I would like to convert the data to RDF - and make the result available as Open Data.)

So, XML escaping in a CSV file. I'm not in favour of adding extra code to Tarql to support this special kind of idiocy.
If you do a global search and replace of <![CDATA[ to " and ]]> to ", then with luck a normal CSV reader will be able to handle the file.

special kind of idiocy creativity. (Apologies for the bad language.)

I do not feel offended: I did not create that idiocity ;-)


Update tests.yml

See https://github.com/git-lfs/git-lfs/issues/5749

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


How do I add more attributes to the item feed

Hi @fillup @vanhoavn @simoheinonen
As what I see the usage doc, it only supports "product name", "sku", "product id", "main image", "long/shelf/short description" and something like that.
I would like to add some more attributes and item options like color/size.
How can I add them to feed?
Thanks.

Hi @fillup @vanhoavn @simoheinonen
I am also tried to create configurable product from Item feed api call. But when I pass more attributes. Its through the error only.
Please suggest me.

Those are good questions, I haven't tried that before. Are you structuring the data based on the schemas? The library for serializing the array of data into XML was one I developed for this SDK and its also possible that the structure at some point in there does something I'm not accounting for. Can you provide me with some more examples?

Hi @fillup ,
Actually total first level categories 25 . Each and every category have a separate type of required fields. I found the all the category schema XSD files from following URL
https://developer.walmartapis.com/files/mp/WalmartMarketplaceXSDs-2.1.8.zip
Each category variation options details - http://marketplace.walmart.com/knowledgebase/articles/Article/Supported-Variant-Attribute-Names?q=variations&c=&l=en_US&kb=
For Set Up A Variant Group please refer the following URL. That url have sample xml format request also.
http://marketplace.walmart.com/knowledgebase/articles/Article/How-To-Set-Up-A-Variant-Group?q=variations&c=&l=en_US&kb=


Rebuild with harfbuzz 3.1.1 for compatibility with icu 68

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Grr. With pango upgraded now it's going to be too difficult to get a build that is compatible with icu 68, so there's not much to be done. It's only the latest qt on Windows that is stuck with icu 68, and that problem really needs to be solved there.


FileParameter tries to do JsonConvert.SerializeObject on the Stream

When using a generated client for an API where the input type is a stream, this generates a  FileParameter body input parameter in NSwag. This looks good.
When you look at the generated code by NSwag, it tries to put the stream into a Json Serialized Object, this shouldn't happen. It's not Json! It's a stream where the type is application/octet-stream, so there is no point in serializing. It should put the body.Data (the actual steam). directly on the http request stream instead, no reading at all.
var content_ = new System.Net.Http.StringContent(Newtonsoft.Json.JsonConvert.SerializeObject(body, _settings.Value));
                    content_.Headers.ContentType = System.Net.Http.Headers.MediaTypeHeaderValue.Parse("application/octet-stream");
                    request_.Content = content_;
                    request_.Method = new System.Net.Http.HttpMethod("POST");
                    request_.Headers.Accept.Add(System.Net.Http.Headers.MediaTypeWithQualityHeaderValue.Parse("application/json"));

The latest version where it did work seems to be NSwag.ApiDescription.Client 13.7.0, however, it used a regular IO Stream instead of a FileParameter.

I'm also having this issue

Same here. As result of Json serialization receive Timeouts are not supported on this stream exception.

@RicoSuter Any chance that you will pay attention to this issue in near future?

I'm still encountering this issue in version 14.0.3. @erwinkramer did you find a workaround for this problem?

@rbnpst i'm not working with that tech right now, but my workaround at the time was going back to version 13.7. If you would ask me what i would do if i encounter it today, i'd try out other tooling, like Kiota from Microsoft. Let me know when u try it.

13.7 works for me. Not sure if we want to use an older version for long, but it's good for now. I'll take a look at Kiota. Thanks!


pipenv 2024.2.0 doesn't interpret my src-folder as a folder but as a package (src 0.0.7)

Hello,
I just wanted to report an issue:
Issue description
The title says it all. I have a project folder which contains a Pipfile and a src folder. The content of the src folder should be installed using pipenv install. However, instead of installing my local folder as package "src" it will end up trying to download src-0.0.7 and build a wheel out of it. This should not happen, since I explicitly state that by using the file-keyword. Check the section of my Pipfile below
[packages]
mypackage = {file = "src", editable = true}

In the past, pipenv would install this folder as a package. But now it downloads a package with a corresponding name.
There's a workaround: Inserting a "./" :
[packages]
mypackage = {file = "./src", editable = true}

Expected result
A succesful install of "MyPackage" like in previous versions (2024.0.1 and below) of pipenv.
Actual result
self.distribution.has_ext_modules()
:       AttributeError: 'NoneType' object has no attribute 'has_pure_modules'
:
:
:   note: This error originates from a subprocess, and is likely not a problem
with pip.
:   ERROR: Failed building wheel for src
: ERROR: Could not build wheels for src, which is required to install
pyproject.toml-based projects
ERROR: Couldn't install package: {}
Steps to replicate
In this case, you can just follow my description from above to reproduce it. But basically: just create a folder named src, put your package files in it and specify it in the Pipfile accordingly.
Best regards!

Both 2024.2.0 and 2024.0.3 behave different than previous versions have.
Instead of file we are using path however... so it might be a seperate, but related issues, or totally unrelated.
mypackage gets added to the Pipfile.lock as if it was found on an index.
Expected:
        "mypackage": {
            "editable": true,
            "path": "."
        },

Actual:
        "mypackage": {
            "version": "==1.1.4.post2+git.e6b273aa.dirty"
        },

Please try this branch and help me determine if it resolves your issue:  https://github.com/pypa/pipenv/pull/6282

2024.3.0 has been released.   @fpi1337 could you confirm if your issue persists?

@matteius First of all, thank you for your efforts! :-) But I have a dumb question: since I've installed pipenv 2024.2.0 by using pipx under Debian 12, I am not really sure, how to update it using your released 2024.3.0.
And I don't know if this is of any interest, but I digged in deeper regarding my issue (it's probably fixed by now with this current update) but here are some notable findings (it involves poetry, so I don't know to which degree this counts):
[tool.poetry.dependencies] mypackage = { path = "src", develop = true } python = "^3.8"
poetry export -f requirements.txt > requirements.txt creates a requirements.txt with all the dependencies out of my pyproject.toml. But here's the thing:

if my colleague uses poetry export with this Mac, he gets a requirements.txt with this entry:

mypackage @ file:///Users/xxxx/ourporject/mypackage/src ; python_version >= "3.8" and python_version < "4.0"
If we now use his created requirements.txt containining the entry above to create Pipfile and Pipfile.lock (rm -rf before of course), the reported issue will occur because the Pipfile will contain the entry like this (keep in mind that he set the develop-flag in pyproject.toml to true):
[packages] mypackage = {file = "src"}
This entry of course will prevent pipenv to function properly. It will even ignore inserting the packages in Pipfile.lock which are listed after mypackage @ file:///Users/xxxx/ourporject/src ; python_version >= "3.8" and python_version < "4.0".
But then if I generate (under Debian 12) the requirements.txt, Pipfile and Pipfile.lock using poetry export I'll get a requirements.txt which looks like this:
-e file:///home/fpi/mypackage/src ; python_version >= "3.8" and python_version < "4.0"
This on the other hand creates (pipenv install) a Pipfile which looks like this:
[packages] mypackage = {file = "src", editable = true}
which pipenv install can understand properly. The "editable = true" option does the trick. Even if I set it manually in the the Pipfile, not creating everything from scratch. The -e in the requirements.txt even creates the Pipfile properly on my colleagues Mac (even keeping in mind his "develop=true" option in pyproject.toml) but not the other way around when using his created requirements.txt with mypackage @ file .....
So in general: it seems that the Mac creating workflow of every component (requirements.txt [although created by peotry export], Pipfile and Pipfile.lock) leads to this problem. So everyone else who uses his created Pipfile encounters this issue.
I hope that my description is understandable. If not, come at me again. :)

pipx upgrade pipenv

Thank you! It seems that the issue is fixed on my end. It now runs pipenv install flawlessly, even if it does not contain the editable = true option.


EX2-007 effect is missing from your site

EX2-007 effect is missing from your site. It is listed on the official en.digimoncard.com site.

Fixed!


Drop "written in Rust" from docs landing

Requested by @BurntSushi — and I agree.

Do we want to highlight anything other than "fast"?

Not strongly opposed but what's the problem with this? I feel like it's nice to have consistency in this copy across various sources.

I agree consistency seems nice, but I'm kind of against having this marketing copy in the documentation and CLI descriptions. We already dropped this in the CLI:
❯ uv help
An extremely fast Python package manager.

I think it makes more sense in blog posts and the README?

Okay, cheesy I know but let's bias towards retaining this — if we had a marketing team they'd probably make us :)


eval to title and description in site.registerResource

Server: Return kv['+title'], ['+description']
Client: Interpret kv['+ttile']

Describe site rule as 's/:会議資料//' or 'm/第[0-9]*回'
Apply site rules (include include/exclude) in client

Implemented property_template to transform new property from existing one instead of title, description etc.


Remove live.nixos.org records

I'm going to decommission this machine pretty soon. Should we perhaps look into creating a more permanent solution for livestreaming?
Ref: https://github.com/NixOS/nixos-org-configurations/pull/213#issuecomment-1191177100

cc: @zimbatm

thanks, applied


[FEATURE] Connect-PnPOnline should connect to Admin Console if there is a credential entry for a regular site

Is your feature request related to a problem? Please describe.
I was surprised to see Credentials parameter fails to recognize credential entry https://tenant.sharepoint.com when connecting to https://tenant-admin.sharepont.com and vice versa.
Describe the solution you'd like
Although https://tenant-admin.sharepont.com and https://tenant.sharepoint.com technically are separate entities, it would be great to make stored PnP credential entry created for https://tenatnt.sharepoint.com be used for https//tenant-admin.sharepoint.com connections.
Describe alternatives you've considered
Obviously we can create multiple credential manager entries, however one entry is better than a couple or a few I guess.

@YuriySamorodov - I don't quite understand what you're asking here?
I can use Connect-PnPOnline against the admin url (-admin.sharepoint.com) and use the same credentials from the Credential Manager for example for the root site (contoso.sharepoint.com).
You have 2 different entries in your Credential Manager (one for each site) with the same username/password.

@veronicageek , sorry for the confusion. My idea is to be able utilize just one credential entry for contoso.sharepoint.com, contoso-admin.sharepoint.com and possibly contoso-my.sharepoint.com
From programming perspective that requires adding just a single regex to the equation.
Hope this time I have made myself clear.

Thanks @YuriySamorodov.
I haven't heard or seen that adding 3 entries in the Credentials Manager is a problem, but I'll leave @erwinvanhunen or @gautamdsheth decide 🙂

Thank you @veronicageek! In fact, this is what I have tried first once I got my hands on Add-PnPStoredCredential cmdlet. Should not be considered as a priority anyway. Just my 2 cents.

I have had the same thought as @YuriySamorodov , that finding a way to leverage one credential per tenant would be great. A credential stored at -admin is likely an elevated account, so I would hate for Connect-PnPOnline to fall back to that if it didn't find a credential for tenant or tenant-my. Maybe Connect-PnPOnline could look for tenant if no credential is found for a connection to -admin or -my, kind of like how deeper links like /sites/HR do. Or maybe add a switch like -UseTenantCredentials that looks for an entry for https://tenant.sharepoint.com.
I currently create two credentials for each tenant I connect to. It's not a huge deal, but it would be nice if I could cut that work in half.

Thanks for supporting, @ToddKlindt. To extend my request: the most convenient credential implementation I have seen to date is Connect-ExchangeOnline, where I could fire up PowerShell as a specific user and then run Connect-ExchangeOnline -UserName (whoami /upn) No credentials exposed at all therefore it is pretty safe to hand it off to someone else or keeping in the local knowledgebase.

The question is do we really need this now ?
The current behaviour is such that PnP PowerShell will automatically switch connections between cmdlets .
for example, you connected to /sites/HR and the used Get-PNplist . After that , you used Get-PnPTenantSite .
If you have adequate permissions, you don’t need to connect explicitly to admin site , the cmd works . So, switching between web, site and tenant level cmdlets doesn’t require relogin .
Happy to hear your thoughts on this @ToddKlindt @YuriySamorodov @veronicageek


Package MirageOS

I'd love to be able to play with MirageOS and we have a decent amount of the underlying OCaml machinery and libraries already packaged. Would be cool to make carefully tailored MirageOS images inside Nix.
cc @maurer @vbgl as OCaml users I know of

I've been doing this while doing something else. Will push up what I have soon.

This is done but a bit messy on my local machine. I'll clean it up then push it up later.

I do have mirageOS working under opam2nix (https://github.com/timbertson/opam2nix-packages), if that helps. I don't know if/when it'll be ready to merge into nix proper, but it could be a less arduous way of tracking opam upstream.

Oh that'll be nice. I need it in a non-OCaml package in the short term, unfortunately, so I'll probably merge my work soon regardless, then we can replace it with opam2nix!

Any news on this topic? Thanks.

@copumpkin this would help with my work on VPNKit!

I will be going to Bobkonf this friday (would be nice to meet with any nix-ers! :D ) and there's going to be a tutorial on MirageOS (https://bobkonf.de/2019/mehnert.html). I haven't used any of the ocaml infrastructure yet and I don't know how much work I can put into it over the week, but it would be nice if someone could have another peek at this?
@copumpkin did you manage to post any of your work?

For the record, I tried just using opam and following https://mirage.io/wiki/install and https://mirage.io/wiki/hello-world ; and that seems to have worked pretty much flawlessly. I just tried running the noop example and there were no problems.

I had a very quick chat with Hannes from MirageOS people and he is intrigued. So whoever wants to work on this should contact him, if this is still relevant (because of for example b90908aead3a4bad4d122b3f1d2bfacd0cfd1677 )

I've built the Mirage tool with Nix before: https://github.com/ehmry/mirage-nix

Great! I've long wanted to see something along these lines. That would be @hannesm?
Another thing I've long term wanted to see was replacing the few C bits (Solo5, OCaml) with Rust, and coincidentally enough, we're just in the midst of getting better bare metal Rust cross compilation support thanks to @aaronjanse's work for Redox.
Typically the more obscure toolchains need to be wrangled, the brighter Nix shines, so I figured something like that would be a good opportunity to show of Nix.

Also, Solo5 is in the tree (dd8423f86550ef7a63d704b220d361e977142b29).

Yes, that is me. AFAICT the solo5 toolchain is already packaged in nix, and the mirage utility can be (or is already? -- if not, are there any showstoppers?). Once these pieces are in place, we should think about packaging concrete unikernels into nixOS (I have some ideas about how to achieve that - in the end a configured MirageOS unikernel is an opam package).
So for now, I have two questions:

is the mirage command line utility (opam package mirage) packaged in nixOS?
is it easy to package an opam package into nixOS?

@hannesm So the slickest way to package opam modules with Nix is to on-demand generate the Nix code using tools like that opam2nix. Unfortunately, Nixpkgs doesn't allow generated code on the fly due to an issue with our CI tool (not Nix itself), so we have to vendor the output for opam packages we want to include.
So, to answer your questions

is it easy to package an opam package into nixOS?

Yes, very.

is the mirage command line utility (opam package mirage) packaged in nixOS?

It might not be, but it should be no harder than other opam package. Just a matter of articulating the motivation and vendoring the code that's easy to generate.

I think if you/we start with @ehmry's https://github.com/ehmry/mirage-nix, we won't even be blocked on the previous two steps (it also uses opam2nix). We can go straight to packaging concrete unikernels into NixOS by writing the requisite NixOS modules in there. Once the whole thing works end-to-end, I think there will be no trouble justifying moving the code to Nixpkgs proper :).
That plan allows iterating with the dynamic Nix code generation and only "baking" it at the end, which should be much more ergonomic.

From what I remember, the dependencies of a Mirage unikernel are determined at configuration time, which means that a NixOS module for something Mirage would break the no-import-from-derivation rule in Nixpkgs. That may require then Mirage stuff to be hosted outside the main tree, but that's less of an inconvenience these days.
Also, opam2nix is probably the better way of managing the dependencies than managing them manually. Opam has good metadata so this should be safe to do.
I believe this implies that to realize a configuration written in Nix would require a derivation that calls mirage to generate an Opam package that corresponds to the Nix configuration, processing that package with opam2nix, and then building the unikernel from that.

Yeah, I suspect the Mirage CLI and Nix are going to have a bit of a turf war, but otherwise things should be fine.

To see how far we've come and what challenges we still have to overcome, I tried to build the stub-resolver unikernel from roburio/unikernels today.
I'm pleased to announce that in terms of MirageOS unikernels for the unix target we are basically already there! We are just missing MirageOS libraries here and there, but the fundamentals are there and work fine. My endeavour lead to #107907, #107914 and #107922.
With the following, frankly trivial shell.nix (and the PRs merged into a local nixpkgs) it's a matter of nix-shell --run "mirage configure && mirage build":
let
  pkgs = import <nixpkgs> {};

  op = pkgs.ocamlPackages;

  baseTools = with op; [
    ocaml dune_2 ocamlbuild findlib
  ];

  baseLibraries = with op; [
    mirage mirage-unix mirage-types mirage-types-lwt mirage-logs
    mirage-crypto-rng-mirage mirage-clock-unix mirage-bootvar-unix tcpip
  ];

  unikernelDeps = with op; [
    dns-resolver dns-server logs
  ];
in

pkgs.mkShell rec {
  buildInputs = baseTools ++ baseLibraries ++ unikernelDeps;
}

The predicted turf war between mirage and the nix infrastructure is also not happening, as it is pretty well behaved and uses standard ocaml tools like dune, ocamlfind and ocamlbuild which we have already figured out.
Here's a screenshot of stub-resolver built on NixOS answering a request on my my machine:

Next steps for MirageOS in nixpkgs as I see it would be:

[ ] Package missing mirage libraries
[ ] Add infrastructure for building MirageOS unikernels (should be as lightly altered buildDunePackage) and maybe even deploying it
[ ] Test and figure out other MirageOS targets like Xen

@sternenseemann Congrats! Your PRs all looked perfectly fin to me and I merged them.

The predicted turf war between mirage and the nix infrastructure is also not happening, as it is pretty well behaved and uses standard ocaml tools like dune, ocamlfind and ocamlbuild which we have already figured out.

Glad to be wrong so far!

Test and figure out other MirageOS targets like Xen

...but I suspect once we get into these interesting cross compilation cases, things will emerge :).

I wonder if anyone has tried a statically linked Unix target with Musl, since that's a vageuly kindred spirit of a target to Unikernels.

I wonder if anyone has tried a statically linked Unix target with Musl, since that's a vageuly kindred spirit of a target to Unikernels.

Seems like it is planned, but not yet implemented:
https://github.com/mirage/mirage/issues/880
Although you can probalby achieve it already by messing around in the build files mirage configure generates.

MirageOS 4 related upstream issues/PRs:

https://github.com/mirage/mirage/issues/1217
https://github.com/Solo5/solo5/pull/494
https://github.com/mirage/mirage/pull/1226

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/linux-unikernel/22648/2

I've written hillingar which uses opam-nix to build mirage unikernels. I've written a blog post on the project here: https://ryan.freumh.org/blog/hillingar/

Good catch, this can be closed.

Untrue, MirageOS is not packaged in a meaningful/workable form. Some libraries related to it are packaged, but it is not possible to build/package MirageOS  unikernels.

It's not a matter of missing packages, the problem with Mirage is getting the OPAM configuration stuff working with Nix.

It's not a matter of missing packages, the problem with Mirage is getting the OPAM configuration stuff working with Nix.

Could you expand on this?

The configuration stuff as seen here: https://mirage.io/docs/hello-world

The configuration stuff as seen here: https://mirage.io/docs/hello-world

I'm afraid I don't follow... Could you be more specific about what configuration you forsee having issues working with Nix? I've built multiple mirage unikernels with Nix (see https://github.com/RyanGibb/hillingar/blob/main/src/mirage.nix).

Does anyone have a list of packages that we'd need to package in order to have meaningful and workable MirageOS packaging? If not, how could we compile one?

I would take the dependency closure of the particular unikernel you're looking at building, e.g. the contents of duniverse.

My knowledge is out of date then.


Fix emote map

Only a few of the emotes have the correct image mapped to them. This needs to be fixed, especially considering that this app has now been released.
The video used for the emotes is this one.
This issue is being worked on in the fix/emotes-map branch. A file tracking the mismatched images in available in the Images.md file.

Worked on by @Tatty2004 in #7 and #12


Init behat

do not merge

ok to test

retest this please

@podarok I'm not sure that all sites should be protected with httpauth. It adds layer of customization.


Add CamelCase Transformation

Closes #149824.
Added tests to src/vs/editor/contrib/linesOperations/test/browser/linesOperations.test.ts.
I made some guesses about how to best handle existing capitalization. I decided to retain them. If I lowercased, then if you run it on something that' already camelcase, it would make it all lowercase. Also, I make it so it converts sentences, snake case or kebab case to camelcase. Any other separators it should use?

Thanks @ssigwart


Fixed flaky test

This is to fix the failure in https://github.com/datafaker-net/datafaker/pull/893

closing since this commit was merged as https://github.com/datafaker-net/datafaker/commit/1c4b1cfeec2841d0530ab1f641694cd715701c8e


Fix nested SVGs in iOS #1437

Summary
Fixes #1437  #1495.
Nested SVGs with gradients are rendered now in iOS
In the current implementation nested SVGs don't call the [svg parseReference]; which is needed for the brush creation.
This happens because of this if-clause RNSVGSvgView.m:208-210.
Moved the call of [svg parseReference]; from - (void)drawRect:(CGRect)rect to
- (void)drawToContext:(CGContextRef)context withRect:(CGRect)rect .
Since it also loops through the subviews and is called for all SVGs.
Test Plan
Code shown in #1437.

Compatibility

OS
Implemented

iOS
✅

Android
❌

Checklist

[x] I have tested this on a device and a simulator
[ ] I added documentation in README.md
[ ] I updated the typed files (typescript)
[ ] I added a test for the API in the __tests__ folder

Closing since #1948 has been merged.


Get more location info

Could it use maxminds geo ip database or another source to show which city/state of the proxy in addition to country?

The GeoLite2-City.mmdb database has 51MB uncompressed and in my opinion it doesn't make sense to have in the repo.

@PowerPress thanks for your attention!
Now to get additional geolocation information, you can run once proxybroker update-geo command to update the GeoIP database (to City version).


fix: Chat - Unable to deselect user using The Tab key.

Details

Fixed Issues
$ https://github.com/Expensify/App/issues/47306
PROPOSAL: https://github.com/Expensify/App/issues/47306#issuecomment-2285919336
Tests

Go to FAB > Start Chat
Using the tab key and Enter key select add to group multiple results from the contact lists
Use the arrow and tab key and try to deselect the selected users
Verify user can be deselected using tab key

[x] Verify that no errors appear in the JS console

Offline tests

Go to FAB > Start Chat
Using the tab key and Enter key select add to group multiple results from the contact lists
Use the arrow and tab key and try to deselect the selected users
Verify user can be deselected using tab key

QA Steps

Go to FAB > Start Chat
Using the tab key and Enter key select add to group multiple results from the contact lists
Use the arrow and tab key and try to deselect the selected users
Verify user can be deselected using tab key

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/498adff6-68be-44c0-a757-4d2e2f2f394e

Android: mWeb Chrome
https://github.com/user-attachments/assets/058fed4a-f697-4b48-a1b8-10e5153a4369

iOS: Native
https://github.com/user-attachments/assets/37690bd5-18b9-47b8-8b01-43471f7fd794

iOS: mWeb Safari
https://github.com/user-attachments/assets/48b597b8-e7fb-4470-afce-deef9b9fa870

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/c31f6799-6cff-430f-a716-b7db2ef804d3

MacOS: Desktop
https://github.com/user-attachments/assets/0022242c-3915-435b-9f31-5ed81d38766f

Okay, so I think this is mostly fine! The only changes I'm a bit concerned about are the swaps from imageButton to button, since that's a bit of a different role. Do we feel like this will cause any accessibility issues for users? I'm not sure this is a priority but I saw on the previous PR (which I apparently reviewed haha) that deprecated ACCESSIBILITY_ROLE that we held off on those changes.
It might be fine though?
@stitesExpensify do you have any thoughts here since I know you're interested in accessibility stuff as well?

given that in the react-native docs they say role has precedence over accessibilityRole, and role has no imageButton option, I think we're probably okay? I'll go ahead with this for now and if we get feedback about it we can rethink.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/dangrous in version: 9.0.25-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/dangrous in version: 9.0.25-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Extend ic evm utils with already known tx status

Motivation
Currently, the -32010 response from an rpc endpoint is interpreted as error within the ic-evm-utils library.
As discussed here, the -32010: AlreadyKnown response from an evm rpc endpoint is not a classical error. Rather, it signals that the exact transaction being pushed is in the mempool. The application should have the option to treat this status is an appropriate manner, for example:

waiting for the tx to be mined
waiting for the tx to be dropped
assuming that the tx will be mined (example)

Changes

extend the status enum
check for the error code and respond with the new status instead of an error in this specific case only
update cargo.toml to actually use the local packages

thanks for the changes!
i couldnt push to your remote so i create this branch instead
https://github.com/letmejustputthishere/chain-fusion-starter/pull/40


Add key werification to SCell and SMessage class

need review by @vixentael

Hmm why nobody reviewed or joined this??? @vixentael please?

sorry, missed that

@mnaza fixed indentations https://github.com/cossacklabs/themis/commit/f33f0bc6f05b1564e215867f6614c834c0aa9f5c


Add new game

Is this a game?
Thinking emoji

Your pull request needs further work because of the following reason(s):

You added/changed/deleted 5 files. You can only add three (3) files index.html main.js main.css.
You changed a file called libv86.min.js, this is not one of the three allowed names.
Your main.js file was not found, it is a requirement (even if empty)
Your main.css file was not found, it is a requirement (even if empty)

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

1c158108e7c959df5ee9987e10295879f5351056

CDN
CDN
CDN
(Also follow the rules. main.js, main.css)

This PR has been idle for more than 24 hours, and will now be closed. Feel free to re-open.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

97652786fa820499d055c1efe1c14d243c5d4d87


Fix alignment in "Move topic" menu

At present, in the "Move topic" menu, the spacing between the checkbox options for stream notifications looks off:

We should change the layout to always put the second option on a new line.

could you please assign this issue to me?

@zulipbot claim

@alya can i worl on this issue as a part of outreachy program.

@zulipbot claim

@ChitvanRamani22  I am currently working on this issue.


Add bootstrap-nightfall (

We use a CSS file from https://vinorodrigues.github.io/bootstrap-dark/ to render the UI of the crawler.
Add to NOTICE.


v5.78.0 causing errors on watcher recompilations

Bug report
Looks like PR 16477 introduced a regression for us while running in watch mode for recompilations. Specifically the addition of the if stmt in NormalModuleFactory.js.

What is the current behavior?
The initial build reports no errors but anytime it re-compiles due to a file change, the errors show up. They're all asset related errors and it doesn't seem break the build as far as I can tell. The assets in question are mostly css images but it's also occurring for a json file we're importing in our js code. That initially made me thing it was css-loader related but the json file error throws a wrench in that theory.
The one common feature is that both sets of assets are requested with alias paths but the error messages report the absolute path.
ERROR in ./docs/assets/definitions/default.json 2:11
Module parse failed: Unexpected token (2:11)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| {
>   "default": {
|     "desktop": [
|       {

It's an unexpected error considering importing json files in JS should just work, and does on the initial compilation.
If the current behavior is a bug, please provide the steps to reproduce.
I haven't had time to create a simplified reproduction since our setup is pretty complex but I figured I'd at least report something in case someone else has encountered this before or it sparks an ah-ha moment. If that's ultimately what's needed me or my colleague will try to get something together.

What is the expected behavior?
If the loader for the resources were truly missing, then I'd expect to to affect all assets and it's only affecting some of them.

Other relevant information:
webpack version:  5.78.0
Node.js version: v20.3.0
Operating System: OSX 13.3.1
Additional tools:

Does this still persist in the latest version of webpack.

Yes it does. If there's anything in particular you want me to look into or get logs on, I'm more than happy to do that.


HKG - #asWord("") is unexpected during the proof

Following the issue #1520, we encountered the warnings:
kore-exec: [2020-02-06 20:57:54.711656538] Warning (WarnBottomHook): Evaluating 'BYTES.get' in pattern:
    /* Fn Spa */
    Lbl'UndsLSqBUndsRSqBUnds'BYTES-HOOKED'Unds'Int'Unds'Bytes'Unds'Int{}(
        /* Fl Fn D Sfa Cl */ \dv{SortBytes{}}(""),
        /* Fl Fn D Sfa Cl */ /* builtin: */ \dv{SortInt{}}("0")
    )
has resulted in \bottom.

This happens when the prover tries to apply the rule
    syntax PushOp ::= PUSH ( Int )
 // ------------------------------
    rule <k> PUSH(N) => #asWord(PGM [ PCOUNT +Int 1 .. N ]) ~> #push ... </k>
         <pc> PCOUNT </pc>
         <program> PGM </program>
at step 99.

We suspect that the prover tries to apply the following lemma
    rule #asWord( BUF => #drop(1, BUF) ) requires BUF [ 0 ] ==Int 0  [simplification]

on the term asWord("").
However, the opcode is PUSH1 and the result buffer should be a bytearray of length 1 instead of "".

After @virgil-serbanuta show me the function call stack log, I made the following guess of how #asWord("") is encountered during the execution.
First, #asWord(0) is encountered during the execution (which is expected), and then the following simplification rule is applied before the definition rule.
rule #asWord( BUF => #drop(1, BUF) ) requires BUF [ 0 ] ==Int 0  [simplification]

The result of the simplication is #asWord(""), and then the same simplification rule is tried again and leads to the warnings.
If my guess is correct, the problem should be fixed by #1524

@yzhang90 Was this fixed by #1524.

yes. I closed the issue.


Cloning of transcluded elements fail

Hi @aliok!
First of all, thanks for that awesome plugin!
I found a fancy issue, since you are using $compile on a cloned element,
ngTransclude will fail. e.g: ion-toggle
http://codepen.io/zoltan_papp/pen/dovGVo?editors=101
I am trying to solve it, but any help would be appreciated! ;)
Cheers!

Heya!
I think I may have run into a similar issue as yourself. Seems using ng-bind rather than {{someMustaches}} might fix it?
http://codepen.io/anon/pen/pJPZJz
Looks like the ion-toggle is actually doing its job, but the "Affixed stuff true/false" isn't being updated because when it's compiled it becomes a static string and the data binding is lost.

Hi there!
Unfortunately that seems only a partial solution for me. :(
If you open the console, you can see that it's still crying about ngTransclude.

@texh @aliok
Please review
https://github.com/aliok/ion-affix/pull/9

This project is not maintained anymore. We cancelled our free-time hobby project with Ionic because of too much changed recently in our personal lives and we don't have enough time at all.
I would be happy to reference anyone who would fork the project and maintain it.


Remove user data collection and table (#152)

This PR makes changes to the COURSE_INVENTORY job in order to remove and otherwise minimize collection of user-related data (PII). This is accomplished by modifying the existing AsyncEnrollGatherer class and its associated GraphQL query and adding a migration that drops the user table and an associated foreign key. More details are provided below in the task list. The PR aims to resolve issue #152.

[x] Add migration removing the foreign-key constraint from the enrollment table and dropping the user table.
[x] Remove all code dealing with user from the AsyncEnrollGatherer class and the unnest_enrollment function.
[x] Remove all user fields except _id from the GraphQL query used by AsyncEnrollGatherer.
[x] Add type hints to instance variable setting inAsyncEnrollGatherer.
[x] Update usage of AsyncEnrollGatherer.
[x] Remove pull_sis_user_data_from_udw and subsequent pd.merge usage.
[x] Remove output code for user.
[x] Make naming of course_section CSV consistent with table name.

I pushed the migration number back to 0016 so I can merge this. I'll bump up the number in the other PR, #151. Thanks everyone for the reviews.


[SPARK-15158][CORE] downgrade shouldRollover message to debug level

What changes were proposed in this pull request?
set log level to debug when check shouldRollover
How was this patch tested?
It's tested manually.

Can one of the admins verify this patch?

I tend to agree.

Jenkins test this please

Test build #57884 has started for PR 12931 at commit ae4d603.

Test build #57884 has finished for PR 12931 at commit ae4d603.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57884/
Test PASSed.

Merged build finished. Test PASSed.

Merging into master 2.0


Move progress bar from clk to cli

For issue #104

@hardbyte Thanks as always for your guidance.
I was attempting to find a way to write it with only passing a callback but I had a few issues.
The main issues were that the cli can't instantiate the progress bar without knowing the size of the data, and the clk performs a print, which if done before closing the progress bar leads to a race condition where you will generally get a progress bar at ~99%, then print statement, then another progress bar at 100%.
My solution was a abstract encoding interface class, allowing the progress encoding interface subclass to be passed from the cli into the clk. The clk then handles the entire lifecycle using a 'with' statement. This cleans up the typing issues and means the clk doesn't have to do any specific calls on the progress bar.
Again, I'm not sure if it's a good approach, but it was cleaner than the few other options I could think of.


Use Sistent components and packages

Notes for Reviewers
This PR adds our Sistent components and packages.
Since sistent is all supporting v5 mui so some components are not able to migrate directly to sistent ones it breaks.
Since these components are also using theme colors which is also supporting v4 so the colors are also not applying.
Currently i have used sistent only those components that should not break. I am also trying to migrate some styles to v5 styles components parallel to test.
I will make a another pr to migrate the theming to v5
Signed commits

[ ] Yes, I signed my commits.

@theBeginner86 should i check any other build to confirm that nothing breaks when merged

Let's discuss this on Meshery Development Meeting tomorrow at 8:30 PM IST / 9 AM Central time. Please add this as an agenda item in the meeting minutes.


mobs spawn in upper wall of arena

mobs can still get stuck in upper limits of tilemap.
Possible fix is to increase size of arena.

If raycast ends a pixel short of wall, it returns no collision and enemy is spawned at that location, if its collisionshape is bigger than the distance between the raycast and the wall it is stuck in the wall.
Fix by adding to the length of the raycast or taking into account the collision size of enemies and spawn enemies a certain distance back from end of ray.

Fixed!

Fixed!


How can I user APESuperHUD in Xcode 7.3?

I got some errors while compiling my project, such as:
Type 'UIColor' has no member 'black'.
Should I install a old version with Pods?

Hi, You can use version 0.6.2 (Swift 2.1) or update your project to Swift 3.0


Remove case insensitive Accept header support

Hello!
What was the purpose of finding a HtTp_AccEPT case-insensitive way? It also requires traversing all the giant env hash :sob:  I cannot find any good reason for doing this and think it's a sort of obsolete stuff.
https://tools.ietf.org/html/rfc3875 says that all the HTTP_ things are uppercased.
Even if there's a good reason for doing this we should anyway decide what to do with the fact that Grape accesses Accept header from another middleware Grape::Middleware::Versioner::Header using uppercased 'HTTP_ACCEPT'.

I think this goes all the way back to https://github.com/intridea/grape/commit/f7728b88c8cb33e5a783f7a779c761196d697343, I tried to find any good reason for this and failed. I think you're totally right. Merging.


Rubyのバージョンを3.0にあげる

リリースの CI が落ちてるので Ruby のバージョンを上げる。
ref https://github.com/voyagegroup/ingred-ui/runs/4877991528?check_suite_focus=true
Run gem install -N github_changelog_generator
  gem install -N github_changelog_generator
  shell: /usr/bin/bash -e {0}
ERROR:  Error installing github_changelog_generator:
	There are no versions of io-event (~> 1.0.0) compatible with your Ruby & RubyGems. Maybe try installing an older version of the gem you're looking for?
	io-event requires Ruby version >= 3.0. The current ruby version is <IP_ADDRESS>.
Successfully installed concurrent-ruby-1.1.9
Successfully installed tzinfo-2.0.4
Successfully installed i18n-1.8.11
Successfully installed activesupport-7.0.1
Successfully installed fiber-local-1.0.0
Successfully installed console-1.14.0
Error: Process completed with exit code 1.

安定バージョンだと3.1.0なのか
https://www.ruby-lang.org/ja/downloads/

再現完了、Ruby3.0.x だとエラーは出ない。
Ruby2.7 の場合
$ ruby -v
ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-darwin20]
$ gem install -N github_changelog_generator
Fetching activesupport-7.0.1.gem
Fetching fiber-local-1.0.0.gem
Fetching i18n-1.8.11.gem
Fetching console-1.14.0.gem
Fetching io-event-1.0.2.gem
Fetching concurrent-ruby-1.1.9.gem
Fetching tzinfo-2.0.4.gem
Fetching timers-4.3.3.gem
Fetching async-2.0.0.gem
Fetching async-io-1.32.2.gem
Fetching async-pool-0.3.9.gem
Fetching protocol-http-0.22.5.gem
Fetching protocol-http1-0.14.2.gem
Fetching protocol-hpack-1.4.2.gem
Fetching protocol-http2-0.14.2.gem
Fetching async-http-0.56.5.gem
Fetching ruby2_keywords-0.0.5.gem
Fetching faraday-retry-1.0.3.gem
Fetching faraday-rack-1.0.0.gem
Fetching faraday-patron-1.0.0.gem
Fetching faraday-net_http_persistent-1.2.0.gem
Fetching faraday-net_http-1.0.1.gem
Fetching multipart-post-2.1.1.gem
Fetching faraday-multipart-1.0.3.gem
Fetching faraday-httpclient-1.0.1.gem
Fetching faraday-excon-1.1.0.gem
Fetching faraday-em_synchrony-1.0.0.gem
Fetching faraday-em_http-1.0.0.gem
Fetching faraday-1.9.3.gem
Fetching async-http-faraday-0.11.0.gem
Fetching faraday-http-cache-2.2.0.gem
Fetching multi_json-1.15.0.gem
Fetching public_suffix-4.0.6.gem
Fetching addressable-2.8.0.gem
Fetching sawyer-0.8.2.gem
Fetching octokit-4.22.0.gem
Fetching rainbow-3.1.1.gem
Fetching github_changelog_generator-1.16.4.gem
Successfully installed concurrent-ruby-1.1.9
Successfully installed tzinfo-2.0.4
Successfully installed i18n-1.8.11
Successfully installed activesupport-7.0.1
Successfully installed fiber-local-1.0.0
Successfully installed console-1.14.0
ERROR:  Error installing github_changelog_generator:
	There are no versions of io-event (~> 1.0.0) compatible with your Ruby & RubyGems. Maybe try installing an older version of the gem you're looking for?
	io-event requires Ruby version >= 3.0. The current ruby version is <IP_ADDRESS>.

Ruby3.0 の場合
$ ruby -v
ruby 3.0.3p157 (2021-11-24 revision 3fb7d2cadc) [x86_64-darwin20]
$ gem install -N github_changelog_generator
Fetching rainbow-3.1.1.gem
Fetching ruby2_keywords-0.0.5.gem
Fetching faraday-rack-1.0.0.gem
Fetching faraday-patron-1.0.0.gem
Fetching faraday-retry-1.0.3.gem
Fetching faraday-net_http_persistent-1.2.0.gem
Fetching faraday-net_http-1.0.1.gem
Fetching multipart-post-2.1.1.gem
Fetching faraday-multipart-1.0.3.gem
Fetching faraday-httpclient-1.0.1.gem
Fetching faraday-excon-1.1.0.gem
Fetching faraday-em_synchrony-1.0.0.gem
Fetching faraday-em_http-1.0.0.gem
Fetching faraday-1.9.3.gem
Fetching public_suffix-4.0.6.gem
Fetching addressable-2.8.0.gem
Fetching sawyer-0.8.2.gem
Fetching octokit-4.22.0.gem
Fetching multi_json-1.15.0.gem
Fetching faraday-http-cache-2.2.0.gem
Fetching protocol-http-0.22.5.gem
Fetching protocol-hpack-1.4.2.gem
Fetching protocol-http2-0.14.2.gem
Fetching protocol-http1-0.14.2.gem
Fetching timers-4.3.3.gem
Fetching nio4r-2.5.8.gem
Fetching fiber-local-1.0.0.gem
Fetching console-1.14.0.gem
Fetching async-1.30.1.gem
Fetching async-pool-0.3.9.gem
Fetching async-io-1.32.2.gem
Fetching async-http-0.56.5.gem
Fetching github_changelog_generator-1.16.4.gem
Fetching async-http-faraday-0.11.0.gem
Fetching concurrent-ruby-1.1.9.gem
Fetching tzinfo-2.0.4.gem
Fetching i18n-1.8.11.gem
Fetching activesupport-7.0.1.gem
Successfully installed rainbow-3.1.1
Successfully installed ruby2_keywords-0.0.5
Successfully installed faraday-retry-1.0.3
Successfully installed faraday-rack-1.0.0
Successfully installed faraday-patron-1.0.0
Successfully installed faraday-net_http_persistent-1.2.0
Successfully installed faraday-net_http-1.0.1
Successfully installed multipart-post-2.1.1
Successfully installed faraday-multipart-1.0.3
Successfully installed faraday-httpclient-1.0.1
Successfully installed faraday-excon-1.1.0
Successfully installed faraday-em_synchrony-1.0.0
Successfully installed faraday-em_http-1.0.0
Successfully installed faraday-1.9.3
Successfully installed public_suffix-4.0.6
Successfully installed addressable-2.8.0
Successfully installed sawyer-0.8.2
Successfully installed octokit-4.22.0
Successfully installed multi_json-1.15.0
Successfully installed faraday-http-cache-2.2.0
Successfully installed protocol-http-0.22.5
Successfully installed protocol-hpack-1.4.2
Successfully installed protocol-http2-0.14.2
Successfully installed protocol-http1-0.14.2
Successfully installed timers-4.3.3
Building native extensions. This could take a while...
Successfully installed nio4r-2.5.8
Successfully installed fiber-local-1.0.0
Successfully installed console-1.14.0
Successfully installed async-1.30.1
Successfully installed async-pool-0.3.9
Successfully installed async-io-1.32.2
Successfully installed async-http-0.56.5
Successfully installed async-http-faraday-0.11.0
Successfully installed concurrent-ruby-1.1.9
Successfully installed tzinfo-2.0.4
Successfully installed i18n-1.8.11
Successfully installed activesupport-7.0.1
Successfully installed github_changelog_generator-1.16.4
38 gems installed

一応Changelogも確認しておいてもらえると！

@youchann
Changelogってローカルで動きますか？（トークンがなさそうだったりしてて）

@takurinton
リリース後に生成されたのを確認するでよいよ


Bug: inline diagnostics still showing after calling vim.diagnostic.enable(false)

I'm currently disabling diagnostics for gp.nvim chat windows since markdownlint is not helpful there. This is the autocmd I'm using to achieve that:
M.setup_autocommand = function()
  local disable_gp_chats_diagnostics_group = vim.api.nvim_create_augroup("DisableGpChatsDiagnostics", { clear = true })

  vim.api.nvim_create_autocmd({ "BufNewFile", "BufRead" }, {
    pattern = { "**/gp/chats/**" },
    callback = function()
      vim.diagnostic.enable(false)
    end,
    group = disable_gp_chats_diagnostics_group,
  })
end

This does disable diagnostics in general (no more curly lines, no more icons with the line numbers) but when the cursor is in a line with a diagnostic it still shows up.
After vim.diagnostic.enable(false):

After vim.diagnostic.enable(true):

Should be fixed now. Thanks !

Works great, thank you! ❤


Drag and Drop: Handle situations when a file is dropped outside the dropzone

Currently in Texture Desktop the image replaces the web-view contents.

Fixed via #429


OSIDB-2321: Removed trackers from create flaw form and added the unit tests too

It removes the trackers section from the FlawForm when it is on CREATE mode only.
Implements https://issues.redhat.com/browse/OSIDB-2321

A small comment for the reviewers, I am not sure if that's the best way to prove that the element is not rendered.
https://github.com/RedHatProductSecurity/osim/pull/143/files#diff-967a205363234f686e2f6df964ed2631bc6e26c2ba4f9d69abad87898d0d3461R276

I would recommend to squash these two commits into one and rebase it as such commits which tend to address syntax/linting/etc. are not really adding any value and git history will be much more readable without them. But just my personal preference.

To this point, formatting commits being in dedicated commits makes it possible to ignore them in git history by using an ignore revs file as in #125

I would recommend to squash these two commits into one and rebase it as such commits which tend to address syntax/linting/etc. are not really adding any value and git history will be much more readable without them. But just my personal preference.

To this point, formatting commits being in dedicated commits makes it possible to ignore them in git history by using an ignore revs file as in #125

Yeah, but this is a different scenario.  Having both these commits adds no value, better approach here is to just squash/fixup the commits so the linting error is never introduced in the first place.


Add tests for ipython pretty-printing

This feature was added a little while ago, but without tests.
Also tweaks the printing behavior slightly to more closely match the repr, using str(dtype) instead of repr(dtype).

Another reasonable coverage bump for the core files


fix(): file parse issue resolution

is this still relevant? Can you fix the conflict and let's merge it in that case


fixed pronunciation and added Englísh description fo SQL

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Fixing pronunciation of SQL for Latin readers

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Congrats @vdelar on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


A probrem of gpu_nms() got an unexpected keyword argument 'iou_thresh'

iou_thresh change nms_thresh

Did you fixed this problem? I got the same error

I got the same error!

把出现文件iou thresh改为nms thresh
就可以了。

把出现文件iou thresh改为nms thresh
就可以了。

谢谢，可以了

just change the word iou_thresh to nms_thresh.

thanks. fixed.


urbit: 0.6.0 -> 0.7.1

Motivation for this change
Minor version update
Things done

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

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

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

@GrahamcOfBorg build urbit

The build failure seems to be new on aarch64: https://hydra.nixos.org/job/nixpkgs/staging/urbit.aarch64-linux

Looks like this is a known issue https://github.com/urbit/urbit/issues/970

@etu: Is there a way to say something like platforms = [ linuxExceptAarch64 ]?

@bsima Usually we don't want to go break on one platform where it currently works. And usually we don't want to diverge the versions per platform.
But we usually try to see if upstream may have a patch or something that can be applied in the version in question so we can update the package and get on with it.
But from looking at the issue linked above it doesn't seem like upstream have made any statements other than putting labels on it...

Okay, let's put this on the shelf for now and I'll come back to it in a
few weeks to see if they've made progress. In the meantime, maybe I'll
take a crack at fixing it myself and upstream the patch if I have
time...

Closing in favor of https://github.com/NixOS/nixpkgs/pull/55743


How to get it work with Django-Haystack?

I've already had my Django-Haystack application with SOLR working. I want to build an Django Rest framework API for my application. By doing some research, I found the library drf-haystack. I followed the steps on the Basic Use example on its documentation
But it seems it doesn't work with my current existing Django-Haystack application. I got error about  "A server error occurred. Please contact the administration." Here are some details about my code.
I have a model called Resource:
class Resource(models.Model):
  title = models.CharField(max_length=100)
  author = models.CharField(max_length=30)

For my Django-Haystack app, I have my index class:
class ResourceIndex(indexes.SearchIndex, indexes.Indexable):
  text = indexes.CharField(document=True, use_template=True)
  title = indexes.CharField(model_attr="title")
  author = indexes.CharField(model_attr="author")

For my drf-haystack, I have the following serializer and api view class:
class ResourceSerializer(HaystackSerializer):

  class Meta:
      index_classes = [ResourceIndex]
      fields = [
          "text", "title", "author"
      ]

class ResourceAPIView(HaystackViewSet):
  index_models = [Resource]

  serializer_class = ResourceSerializer

In my urls.py, I have
router = routers.DefaultRouter()
router.register("resource", ResourceAPIView,
                 base_name="resource-api")

urlpatterns = patterns("",
  url(r'^', include(router.urls)),
  url(r'^search/$', MyView.as_view(), name='haystack_search'))

BTW, I am using Django-Haystack 2.5.0 with SOLR and drf-haystack 1.6.1
Does anyone have any idea?

https://drf-haystack.readthedocs.io/en/latest/01_intro.html there is a warning in the intro that saying basic usage code might not work. I guess it was hard for the developer of this library to actually put an example that does work.

Hi,
The library has been developed using ElasticSearch as the search backend. I'm quite busy these days and don't have much time for some really needed maintenance. I'll try to have a look at it soon-ish™.

Closed due to no answers - please reopen if still having problems.


Lazy imports not accessible when accessed by key

https://stackblitz.com/edit/github-yu5k5m?file=index.ts
Here is a trimmed down helper we use all the time demostrating the failure case. We have a more complicated one that is type safe, but is curried e.g. lazyImporter(() => import('./Foo')).getComponent('Bar'). TBH I don't really expect knip to see these, but I would love to be able to tell knip that these cases are ok via a plugin or something. Annotating the hundred+ components with knip ignore isn't really feasible and there isn't a way to determine these via a glob

The rule of thumb: if "Find All References" for the Foo export only returns itself in your IDE, Knip won't be able to find other refs either.
Knip covers more when using the --include-libs flag: https://knip.dev/guides/handling-issues#external-libraries
Not sure it's because this is a demo, but Component is typed any here?
Could you be more specific in how Knip could help here? E.g how to ignore such seemingly non-deterministic cases?

We are also facing the same issue.
The problem with React.lazy is that it doesn't allow you make lazy components that are exported with "named exports". We use ONLY named exports in our codebase, because default exports are generally bad.
So we created an util lazyImport that let use use lazy with named exports.
Of course Knip cannot see these and thus reports come components as unused, even though they are used with this special lazy import. I'm not sure how Knip could help us here, just wanted to report that this is a pain point for us too.

Does "Find all references" on the exported component find usages?

Actually yes.
I used "find all references" on my SimilarProductsSlider component, and it found the 2 usages where we import it like this:
const { SimilarProductsSlider } = lazyImport(
  () => import('@components/SimilarProductsSlider/SimilarProductsSlider'),
  'SimilarProductsSlider',
)

Interesting. Assuming you've tried --include-libs, this might be a bug or solvable in Knip. If you could create minimal repro I might be able to fix it.

@webpro oh sorry i wasn't clear, that was WITHOUT --include-libs. Using --include-libs it actually works (it doesn't report those components as unused).
Maybe the documentation around --include-libs shoudl be expanded with this edgecase, or maybe it could beneficial to most if it was enabled by default (and thus, opt-out).

It's not enabled by default, because what's required for this makes Knip pretty slow especially in larger projects. Not sure how to "auto opt-in", but better docs/discoverability would help for sure. Or some kind of "aggregate flag" to group related flags for easier opt-in. Thanks for the input.

Not sure it's because this is a demo, but Component is typed any here?

that would be b/c of the demo i think, it's correctly typed in normal repos

Could you be more specific in how Knip could help here? E.g how to ignore such seemingly non-deterministic cases?

I'd like to tell Knip that these are usages, ideally with my own plugin. FWIW these cases aren't non-deterministic, they are strictly and correctly typed, but defeat the tool

I'd like to tell Knip that these are usages, ideally with my own plugin. FWIW these cases aren't non-deterministic, they are strictly and correctly typed, but defeat the tool

there isn't a way to determine these via a glob

Sorry, still not sure how to deal with this. At this point I also don't really see how plugins could help here if they can't be determined through glob pattern(s).
The repro should be minimal yet complete/functional (at least from a TS/compiler perspective). In general, the --include-libs flag should behave as expected if TypeScript "Find all references" finds refs (other than itself).

Going to close this issue. Feel free to open a new one, and take the following into account:

Some dynamic patterns are too hard to find, even for TypeScript itself. Would still be good to known about such patterns and at least document better.
Make sure --include-libs is tried as well, it makes a difference in a few dynamic scenarios.
Make sure the repro is minimal, complete and typed correctly.


Additional ways for specifying Scala version

Is your feature request related to a problem? Please describe.
It was suggested that maybe it would be useful to have additional 3.lts and 3.next to have up to date version for 3.3.x line and the  3.4.x+ one
Describe the solution you'd like
3.lts should lead to the current Scala 3 lts version and 3.next to the latest version.
Describe alternatives you've considered
Specify it manually.
Additional context
https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

We might want to support lts and next, too (which generally would be the same as 3.lts and 3.next).
next should point to the most recent stable version.
We might also want informative messages for 2.13.lts, 2.12.lts etc. (there's no formal LTS for Scala 2, but users don't have to know that, so we should explain to them why those versions aren't valid identifiers)

Would 3.next behave any differently from just 3?


Please make contents of wrapper types public

Right now all handle wrappers (NativeTexture, NativeShader, etc.) have private contents. This hinders interop with other native APIs and libraries, which require the raw OpenGL handles.
Please make the contents of these types public, so that they can be created and consumed for interop with native code.
I.e. replace the texture definition with pub struct NativeTexture(pub NonZeroU32);.

I'm curious, are there any plans on making a new release of glow to crates.io that includes this change?


RollupServiceTestTrigger, RollupServiceTest4Trigger and RollupServiceTest5Trigger has not been deployed.

I got some errors when I tested apex classes by clicking the "Run All Tests" button. It seems that missing three triggers below are causing the errors.  I looked into the Package components list but these three triggers were not listed in the components. Has anyone seen this issue?

RollupServiceTestTrigger
RollupServiceTest4Trigger
RollupServiceTest5Trigger

I installed the latest version of the tool in my Developer edition and also in Sandbox from the links below.
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tb0000000ka9e
https://test.salesforce.com/packaging/installPackage.apexp?p0=04tb0000000ka9e
error example:
Class: RollupServiceTest5
Method Name: testPolymorphicRelationshipsRealtime
Error Message: System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Apex Trigger RollupServiceTest4Trigger has not been deployed. Click Manage Child Trigger and try again.: [dlrs__Active__c]
Class: RollupServiceTest6
Method Name: selfRollupDelete
Error Message: System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Apex Trigger RollupServiceTestTrigger has not been deployed. Click Manage Child Trigger and try again.: [dlrs__Active__c]
Class: RollupServiceTest6
Method Name: testContactMergeAsChild
Error Message: System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Apex Trigger RollupServiceTest5Trigger has not been deployed. Click Manage Child Trigger and try again.: [dlrs__Active__c]
Thank you in advance!

Thanks this is a bug. Though its not common to click Run All Tests like this in an org, managed package tests typically run in the original developer org and validate the package code is working. You can run only your "local" tests in your org and not packaged ones using this feature.

Thanks for your reply! I will follow your advice and ignore the error.

Andrew, is there a new version planned or any other way to eliminate & correct this error message ?
Alternatively, we could deinstall the package but encountered some issues there.

@Benudek yeah i can treat this as a bug and try to make the tests fail silently in production org. So in your case you need to do Run All Tests? And this will not help?
What issues are preventing you uninstall btw? You have to remove the triggers first via Manage Child Triggers, but other than that you should be good.

@afawcett  @Benudek
Test failing on production as Triggers not deployed with package like  1.RollupServiceTest5Trigger
2.RollupServiceTest4Trigger
Causing production over all test below <20%.
Installed latest version "Latest Release Version 2.8". Any solution would you like to share.  Thanks in advance and really quick reply will be   appreciated .

Hi @VirendraNaruka this should not be causing any code coverage issue at all. Code coverage is only counted for unmanaged code in your production code. Have you deployed the managed package version of the tool (via package installl link) or just deployed the code for the tool raw / unmanaged into your production org (via deploy to salesforce button)?

Thanks Andrew for reply.
Actually installation goes well without any issue. its  Managed Package .
but   After installation  if you run All test or try to deploy the change
set as default  setting then   Managed package test failed.
Its because Some of Test record created at Managed package but related
Trigger did not deployed with managed package.
I resolved some how but please try installation on dev org and then run all
test.  you will reproduce the issue.
Thanks
On Sat, Apr 15, 2017 at 10:02 AM, Andrew Fawcett<EMAIL_ADDRESS>wrote:

Hi @VirendraNaruka https://github.com/VirendraNaruka this should not be
causing any code coverage issue at all. Code coverage is only counted for
unmanaged code in your production code. Have you deployed the managed
package version of the tool (via package installl link) or just deployed
the code for the tool raw / unmanaged into your production org (via deploy
to salesforce button)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/365#issuecomment-294271632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACEWTAJxOhJsCOga_BJjwyl4rGtBjNv4ks5rwEhkgaJpZM4JcWsi
.

Thanks 👍

v2.9

These errors have resurfaced and similarly, I am now having code coverage issues. I don't believe this managed package to be dragging down the % directly, but if functionality fails and causes my tests to not work, then it does have an impact. Thus, to make sure these are not issues propagating into our APEX code, or the functionality of other managed packages, these should be cleaned up before a release, please.

They were, but we have such extensive validation now that all managed
packages fail their test scripts in our production environment because they
don't succeed the tests.
Best Regards,

BENJAMIN FEAGIN JR., MSc, LC
On Sat, Jun 23, 2018 at 9:27 PM Andrew Fawcett<EMAIL_ADDRESS>wrote:

@kappadragon https://github.com/kappadragon are they the same errors as
above?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/365#issuecomment-399728085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ag0CfVkDw4plYxTTgl2luB3PHqHtSTypks5t_xUcgaJpZM4JcWsi
.


Update pgvector to 0.4.4

Problem
after announcing hnsw, there is a hypothesis that the community will start comparing it with pgvector by themselves. Therefore, let's have an actual version of pgvector in Neon.
Summary of changes
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Thanks for upgrading.
Looking at pgvector's changelog, they improved the following:

Improved cost estimation: We performed SET enable_seqscan = off; in all benchmark tests to force using the indexes (hnsw and ivfflat)
Improved performance of cosine distance: hnsw only supports L2 distance. We only compared hnsw and ivfflat using L2 in the benchmark.

Therefore, the changes should not affect the results seen on the benchmark. I will however run more tests to confirm this.


Very high CADD score for common SV

Hi,
Thank you for deveoping this great tool.
I would like to use CADD-SV in my study. However, I found a few common SV exhibit very high CADD score, one of them is:

Chrom
Start
End
Type
Name
CADD-SV PHRED-score
CADD-SV Raw-score
Raw-Score span
Raw-Score flank
CADD max
CADD sum

1
85440802
85440877
DEL
Beyter_D_2021_chr1:85440802-85440877
31
0.97574
0.53229
0.97574
0.17432
0.30327

1
85440803
85440876
DEL
Abel_HJ_2020_DEL_chr1:85440803-85440876
31
0.97574
0.53566
0.97574
0.17432
0.30327

This deletion is quite common, i.e., in gnomAD-SV, AF=0.15 in East Asian (DEL_1_5559). I noticed that this high CADD score is due to flanking region, I did some search on UCSC browser but didn't find key feature can contribute to it.
I manually check some of the "abnormal" common SV and found they are overlapped by some large deleterious SVs. The above example SV is overlapped by:

Chrom
Start
End
Type
Name
CADD-SV PHRED-score
CADD-SV Raw-score
Raw-Score span
Raw-Score flank
CADD max
CADD sum

1
84762783
85491963
DEL
gnomAD_DEL_chr1:84762783-85491963
36
0.98761
0.98761
0.1672
3.32471
3.66879

Could you give some advice on it?
Thanks,
Han

Hi Han,
I think would you did is the correct way to use CADD-SV Scores.
It is an estimate of pathogenicity. As CADD-SV uses neither allelefrequency nor labelled pathogenic variants, this is a great way to confirm the validity of the score. Also keep in mind that high scores could still be functional even though they are not pathogenic


Changing the settings of the title bar makes it completely inactive

Describe the bug
After changing the settings of the title bar (color of the background and foreground, reset to the system title bar, and turn back to custom) I ran into a problem. The title bar stopped handling any mouse events (dragging a window or clicking buttons) as if it were covered by some invisible element.
Steps to reproduce the bug

Steps to reproduce the behavior:

Navigate to 'Windows' -> 'Titlebar'
Play with title bar settings
Set custom title bar
Try to move the window or close it

Expected behavior
The window is draggable and the title bar button works.
Actual behavior
The custom title bar doesn't handle any events.
Version Info
<IP_ADDRESS>
Windows 10 19044.1706
Gallery version (found on Settings page):
1.3.11.

Hi @wnstngs! Thank you for filing this issue. We are aware of this bug and currently working to get it fixed. Thank you for taking the time to file this though! :)

I'm unable to reproduce this @wnstngs, are you still able to reproduce this?

We've made a number of fixes to the titlebar.  I'm marking it as Fixed in Repo, as I believe the 1.2 upgrade and the other changes have fixed this issue.


[Bug]: Unable to see the workflow

Describe the bug
When I click on Workflow tab in the UI i get the below error
Error occurred while retrieving workflows: 1 validation error for AgentWorkFlowConfig type unexpected value; permitted: 'twoagents', 'groupchat' (type=value_error.const; given=default; permitted=('twoagents', 'groupchat'))
Steps to reproduce
No response
Expected Behavior
No response
Screenshots and logs
No response
Additional Information
No response

Hi @monuminu ,
Does the solution in #1305 address your issue?

I upgraded to autogenstudio-0.0.28a0 and i got this issue. I had to uninstall , clear the folder and install again. My workflow are lost though !

Sorry about that.
And yes, we will need some good versioning scheme to deal with database schema compatibility issues like this.
Added to the roadmap #737

Closing as we added it to the roadmap as a feature request


Disable vulnerable versions of SSL/TLS

Anything below TLS1.1 should be considered unsafe:
https://www.globalsign.com/en/blog/disable-tls-10-and-all-ssl-versions/
Usages:
https://github.com/boostorg/beast/search?q=sslv23&unscoped_q=sslv23

Pull request?

Merged in V233


Heads up: Chrome 65 will change composition events on Android

See the following issues for details and please chime in if you have anything to add.

https://bugs.chromium.org/p/chromium/issues/detail?id=764439#c9
https://bugs.chromium.org/p/chromium/issues/detail?id=812674

Thanks for posting this @javan - I'll leave it open for a little while for visibility.
So far we have been 100% blocked from supporting Android web on Draft.js due to the lack of consistency with other browsers and with the spec in how events are handled, so this doesn't make things worse for Draft.js per say. But we have continued to look for opportunities to add better support for mobile, and this is relevant to that effort.

So far we have been 100% blocked from supporting Android web on Draft.js due to the lack of consistency with other browsers and with the spec in how events are handled

I feel your pain!

so this doesn't make things worse for Draft.js per say

It appears it does make things worse since composition events are now dispatched when moving the cursor.
Here's draft on Chrome 65 beta. This problem doesn't occur on Chrome 64.

!!! Thanks for flagging this. Will look into it later today.

@javan can you give repro steps for that bug you showed? We haven't had luck reproducing it using chrome canary, which is version 66.

Gotcha. In case it helps, I posted steps and a video comparing Chrome 64 and 65 on Android here: https://bugs.chromium.org/p/chromium/issues/detail?id=812674#c23
It’s practically unusable on 65 once you move the cursor.

Merging this into a general Android bug issue - see https://github.com/facebook/draft-js/issues/1895


Protect against web/api 5xx responses

When a build is attempted, but a web/api instance throws a 5xx response, a number of strange behaviors can result:

Builds will get stuck in triggered state
Builds will fail randomly when updating the api fails
5xx responses will be returned from the web servers to users

Part of the resolution to this may be defensive protection around intermittent 5xx responses. This may take some operation changes as well though, as our load balancer should really assume a 5xx response is enough to dislodge the server from the lb group.
Raised from #2255

The first one from the list is solved at #3312
I'm not sure to understand the resolution for this. If the request from the builder fails when hitting the API with a 5xx, what we can do?

I believe we should be able to have the build HTTP calls do a smart retry backoff. eg:

Try call
If it fails, try again
If that fails, try again in 5s
If that fails, try again in 10s
If that fails, raise an exception

If that's the way to go, I suppose we could modify our slumber client API class to do this magic. It would be IO blocking, but I suppose that would be fine.
@agjohnson labeled as Operations so he is maybe thinking in another thing.

Yeah, my original take on this is that if a server is overloaded, we should be detecting this and limiting traffic to the server. It's probably a sign that our web servers are overloaded.
Looks like this is still an issue after Azure move.
Retrying is probably a good first place to be defensive. :+1:


Cannot install plugins

Expected Behavior
Can install plugins successfully
Actual Behavior
Plugins fail to load. When clicking "Install Plugin" from the marketplace installation fails and it shows this:

When installing a plugin from the Plugins tab in preferences it fails to install and shows this message:

This issue occurs for every plugin I've tried.
Reproduction Steps

Open the Plugins tab in Insomnia preferences
Type "insomnia-plugin-save-variables" in the text box, or the name of another plugin
Click "Install Plugin"

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnium Version
v0.2.3-a
What operating system are you using?
Windows
Operating System Version
Windows 10 Build 19045
Installation method
.exe
Last Known Working Insomnium version
N/A

+1

This is an issue in Insomnia as well.
The underlying problem is yarn searching parent directories for package.json files. Note that ignoring yarn warnings will not solve this issue as a malformed json will trigger a yarn error.
Your reproduction steps are insufficient to reproduce the problem. To reproduce the problem, before step 3, write {} to a package.json file in any parent directory (the user home directory, for example).
To fix the issue on an individual basis, find and remove the offending package.json by traversing parent directories.

Thanks you're right, there was a package.json file in my user directory for some reason. I deleted it and am now able to install plugins.


Update full version

Quarto chapter before Targets
Quarto and Targets chapters unlinked
LS3 option added

Thank's a lot @jpramil, in the end we chose to remove the chapter on quarto (a separate insee training will be created in 2025, which makes more sense than in this training on best practices) and I'll revamp the chapter on targets to include it in a broader R in production chapter. I've incorporated your corrections for LS3/GitLab compatibility in #14


The type or namespace name 'ValidateWithoutCoreType' does not exist in the namespace 'Corvus.Json' v4.0.0-preview.20

Firstly, what a great project! I really appreciate the hard work here, I have tested many different types of tooling for generation and this is the only one that can handle this complex large schema with extreme nesting.
When generating the code for my specified schema, I have a few errors appearing on the latest preview version. 4.0.0-preview.20
The type or namespace name 'ValidateWithoutCoreType' does not exist in the namespace 'Corvus.Json' (Referenced below)
return Corvus.Json.ValidateWithoutCoreType.TypeInteger(value, validationContext, level, "type");
No overload for method 'WithResult' takes 3 arguments (Referenced below)
ignoredResult = ignoredResult.WithResult(isValid: true, "Validation maximum - ignored because the value is not a number", "maximum");

You need to update the reference to V4 preview Corvus.Json.ExtendedTypes in your project.

That was exactly it, thank you!


[Cloud.gov] Client side Password Validation

Work card:
https://trello.com/c/tc2CAVkh/439-ui-changing-setting-password-should-show-requirements-beforehand

:+1: awesome new feature!

Looks good @jcscottiii

Needs #2


Turn react-universally into a React Universal Framework

Hi guys !
I was wondering if we could find a way to use react-universally as a dependency.
The problem with starter kits (not especially this one) is that their is no "simple way" to keep them up to date. The "starter kit" dependencies are shared with the "application dependencies" and so is the build process, etc... I think we are all the same, and when a new version of whatever lib comes up with new features, we feel the need to upgrade. That is a real problem in the javascript world as everything is moving so fast. As I see plenty of motivated developers on this project, I was wondering if it couldn't be a smart move, to turn react-universally into a "react universal framework" rather than a "starter kit".
The main idea would be to allow people to use the framework as a dependency of their own project. They would just have to extend the default config in their own project (a little bit like the values) and be able to hook everywhere if the default behavior doesn't fit their needs.
As for the features branches, they could be "framework" plugins (to add redux, relay or whatever).
Based on the current version of react-universally, I really don't think it would be too much work to do the transition. ATM, the only specific folder in the starter kit is the "shared/DemoApp", the rest is quite generic: The Webpack config is all about rules & loaders, the babel config is about plugins we want to use, etc... I would say that 90 / 95% of the content of the others folders is the same for everyone and every project.
I would like to know what you think about this idea.

Hey @Vincz!
Yeah, there have been lots of discussions on this concept, specifically with @bkniffler who has even managed to create a working prototype. :)
I am definitely open to the idea of having a dependency based system, however I have never quite felt that the project has been mature enough for it. I am trying to find the place where the project satisfy enough of my production project needs. Lately I have been trying to create some quite advanced setups (including microservices) and have come up with some friction when using react-universally as a base.  This caused me to do some spiking out of new ideas to play with a new toolchain to control develop, build and deploy.  My experiments have been going really well thusfar and I am quite excited about it's prospects.  I will keep you posted if you are interested in doing some beta testing with me.
Once a decent enough solution has matured we can look at either updating react-universally or maintaining a separate project built for purpose.

@ctrlplusb Just let me know if their is anything I can do to help in some way about this :)

@ctrlplusb keep us posted on the beta testing as well!

Will do 😊

Do you guys have something new on this one?

Hey @sergiokopplin
Yep, I have made a ton of progress, but it's still not quite where I need it to be.  My conservative estimate is that I will have something within the next 1.5 months that could be opened up for some private beta testing.  I would definitely value all of your input 👍

@ctrlplusb thanks for the quick response! Awesome work here! Glad to be part of.

Any updates on this?

@ctrlplusb Hey :) Have you make any progress ? I'm still whiling to help.
I'll soon have a big project to start and I'd love to use the react universally frameworked version :)


fix rainbow sprinkles setup example code

Description
In the example code, a type error occurred when the value of the object element of space was a number rather than a string, so this was corrected.
Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[x] Documentation
[ ] Other (please describe)

Checklist

[x] I have read the contributing guidelines
[x] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[x] Functionality is documented
[x] All code style checks pass
[x] New code contribution is covered by automated tests
[x] All new and existing tests pass

Thanks!


Feedback Plugin Enhancement - Enable Deletion of a Feedback

What do you want to improve?
For the Feedback plugin admins should be able to delete any feedback submitted from users - this will likely need RBAC support as a prerequisite as suggested here: #1334
What is the current behavior?
The received feedback cannot be deleted
What will the new behavior be?
Admins, or generally speaking, anyone that is allowed to visit the global feedback page (with access control) is able to delete any feedback items submitted from users

cc @riginoommen @deshmukhmayur @yashoswalyo

Currently, there is an API for feedback deletion. I feel it makes sense to build RBAC support for the Administration purposes


kotlin dynamic query until function

I try to create dynamic where sql using kotlin but there are not until function
can I make this one and contribute this repo?

Let's take a step back here before proposing code changes. Kotlin provides a lot of exciting opportunities to create a DSL for querying. Please also look at MongoDB first, where we have a similar approach.
We should clarify the goal first before proceeding here.

@mp911de

I wonder one stuff how to get column name?? because in R2dbcEntityTemplate you used DefaultNamingStrategy.INSTANCE for default.
But if people used different type of strategy then kotlin extension can not use like this Book::price gte 100
what about creating new R2dbcEntityTemplate function for creating column name in String type
this is the link: https://github.com/spring-projects/spring-data-relational/pull/1492/commits/acbc8141156a3c107dbfef9a9df3ee3d1faf4b99

Column names are not related at all as the Kotlin extensions work on the property level, effectively creating a Criteria that is getting mapped against the domain object metadata for column name resolution.


Getting timezone from offset

I've read and re-read the documentation and I cannot find how to return the user's current timezone with moment.js or moment-timezone.js
Is there not a format that I can specify that will return the timezone based on the time offset? Seems strange I can go one way but not another.

I realized this doesn't make sense.... offset could match several timezones how do you know which is the correct one.... you can however go from timezone-->offset but not offset-->timezone