N-Gram index/search example

Do you have any example how to do N-gram based search indexing and retrieval?
E.g. I'd like to index the phrase "Search and Storage Server", and when I search for "storaeg" it should have a good chance to find it, because some of the N-grams matches the indexed N-grams ("sto", "tor", "ora").
I think xapian supports some kind of N-grams, but I couldn't find an end-to-end example with xapiand.

Out of the box, xapian doesn’t support ngrams; what it supports is wildcard expansion (which could be used as an alternative to edge ngrams). If what you need are full ngrams, Xapiand currently doesn’t have them, but it’s something that shouldn’t be too hard to implement and definitely something I’d be interesting in adding. For the time being, you’d have to pass the ngrams already formed from your client side, perhaps as a keywords array.

Thanks for the details! Would I be able to query that keyword array with a threshold filter? E.g. return only the results where the array has at least 66% match with the queries N-grams?

Sorry, I don’t quite get what you mean. You can add weights when you query something.


Online Dictionary Collins and Collins (education) API has been changed.

npm test Failed.

fix in commit https://github.com/zlargon/voc/commit/377fb0341c2a2ec8ef216a991b542b66f2b68cc8


Print specific Error message for missing ROI

I am analysing a mcd with multiple ROIs and stumbled upon this error:
2023-05-15 15:11:13,563 WARNING steinbock.preprocessing.imc - Error reading acquisition 72 from file /tmp/tmp63oinnto/6483_Immune/6483_Immune.mcd: MCD file '6483_Immune.mcd' corrupted: invalid acquisition image data offsets
However,  instead of issues with the image offsets, the .txt-file of ROI 72 doesn`t exist.
My suggestion would be to print a more specific error message catching that exception :)

I understand that the message is not informative in your case, however:

steinbock uses mcd files as primary input
if the mcd file is broken AND a matching txt file is available, it will try to recover the data
if not, the error message giving details why the mcd file is broken is logged (which seems to be the case here)

One could of course think of being more verbose and add a message to the log saying that the mcd file is broken AND that no matching txt file has been found for recovery (basically add an else branch to https://github.com/BodenmillerGroup/steinbock/blob/bc10207a5a690254bb4e65089c06004fe3f19b05/steinbock/preprocessing/imc.py#L369C53-L404). I think this would be a good addition @Milad4849


Enable features without vendoring

Description
This PR adds the ability to enable SQLite features (at this point only fts5) via build system options and in doing so allows customising SQLite features without resorting to vendoring (as per https://github.com/vrischmann/zig-sqlite?tab=readme-ov-file#using-the-bundled-sqlite-source-code-file).
This means for example you can take the example of installation via the official package manager (https://github.com/vrischmann/zig-sqlite?tab=readme-ov-file#official-package-manager) and simply add, e.g., .fts5 = true to the options to enable full text search:
const sqlite = b.dependency("sqlite", .{
    .target = target,
    .optimize = optimize,
    .fts5 = true,
});

exe.root_module.addImport("sqlite", sqlite.module("sqlite"));

// links the bundled sqlite3, so leave this out if you link the system one
exe.linkLibrary(sqlite.artifact("sqlite"));

A EnableOptions struct is added enumerating boolean options and instead of a static array with only -std=c99 as an option, we make the flags an ArrayList with the same initial content but use a comptime inline for to iterate over each field of EnableOptions to create a b.option and add to the flags ArrayList when the given flag has been enabled. As reference this is the approach taken in https://github.com/mitchellh/zig-build-libxml2/blob/main/build.zig.
As it stands this PR makes it easy to any SQLITE_ENABLE_* options by adding to the EnableOptions struct. This could be expanded to handle other options and indeed non-boolean options.

Thanks ! this looks great.

Looks a recent zig master has moved std.rand to std.Random...I've updated the PR

Thank you. I'll merge as is because the windows tests failing have nothing to do with your PR.

Amazing, thanks @vrischmann!


feat(upgrade): update to work with hapi 17

What: updates hapi-bookshelf-serializer to work with newest version of hapi (17)
Why: so lens-api can use it
Note:

The easiest way I found to test locally is to use a repo that uses Hapi 17 (like lens-api) and copy in the updated plugin in the node_modules. Then make requests to existing endpoints to make sure nothing is broken
Need to update the version and probably the Readme; TO DO if code looks good

i would recommend the following:

update the version of node being used. 0.10 was deprecated in 2016. create a .node-version file and update .travis.yml.
update the version of hapi in the dev deps to be >= v17
add hapi >= v17 as a peer dependency
remove the circle webhook. there was a mistake that added all our repos to circle, but they shouldnt be.

@tonywuhl couldn't switch over to yarn due to some weird node issue but implemented the other feedback including a linter


Error message when scan or deeplik for configuration

When the wallet is already configured and user re scan(or deeplink) , le wallet makes a call to the server and displays a message "Credential issuance denied". Wallet should not call the server and wallet should display "This wallet is already configured"
When wallet receive an errrior message from wallet provider (update or other), wallet must display the error_description of the error meesage

remove this type of message as there is no credential issuance in this flow

still a wrong wallet message when try to updare for instance


fix: strip js comments

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #45127

I'm not sure why the removeJSComments helper was not being made available, but this PR enables it + fixes the tests in the linked issue.

Do we want to close the other issue? This only fixes these challenges, not the underlying cause.


Elasticsearch highlights/snippet support in Wagtail

Feature Summary
Elasticsearch has a built in highlight functionality, which provides snippets alongside search results. While they're not guaranteed to be 100% accurate, they are very useful to the end user to get a better sense of the results they're looking at.
The Wagtail documentation has no specific mention of highlights, so I assumed they aren't supported. Digging into the code has confirmed my suspicion. Injecting the _score value that comes with a query response, is supported however, so I'm hopeful that this can be added :)
I think this feature could be very useful, and considering that ES handles all of the heavy lifting, it should be rather simple and provide great value.
An example of how I imagine this could be used:
events = EventPage.objects.search("Event", highlights=True)
events[0].highlights = {…}

Alternative: generic annotations?
Another way to go about this is to give the option to annotate the results with arbitrary fields received in the response, similar to how _score works. For example:
>>> events = EventPage.objects.search("Event").annotate(["_score", "highlights"])
>>> for event in events:
...    print(event.title, event._score, event.highlights)
...
("Easter", 2.5, {…}),
("Haloween", 1.7, {…}),
("Christmas", 1.5, {…}),

Other considerations
SearchField indexes rich text as HTML. This becomes a problem with highlights. For now I've been able to write a subclass of SearchField that overrides the get_value method and tosses out the HTML tags. This is something that, if support for snippets/highlights is added, could be useful to users.

I managed to get highlights working by extending the elasticsearch backend.
Extending the ElasticSearch2SearchResults
...
 def _get_es_body(self, for_count=False):
        body = super()._get_es_body(for_count)

        body["highlight"] = {
            "pre_tags": ["<i>"],
            "post_tags": ["</i>"],
            "fields": {"*description": {}, "*body": {}},
            "require_field_match": False,
        }
        return body

Here I'm defining which fields I want to return highlights for. In my models I have events_event_description, news_article_description. ES supports wildcarding these fields.
By default Search returns a queryset of models, and to not break that (i.e. returning a dict with model and highlight), I opted to update the Page's search_description field. That way if there is a match, it will use that, otherwise use the default.
You do this in the _get_results_from_hits method in the same file. Extracting the highlight from the hit and attaching it to the model.
You can also extend the _do_search method and change _source param to True, to have the original source in the hit in _get_results_from_hits. So you can do comparisons on the highlight, or in your case strip out html. I used it to check to see if there was content before or after the highlight to add ellipsis (...) to show additional content.


Tutorial page has text missing

The very first tutorial at
http://ufldl.stanford.edu/tutorial/supervised/LinearRegression/
has text missing at the end of the second paragraph.  It ends with:
For short, we will denote the  [missing text]

Also, on the same page and in the "Function Minimization" subsection, the "Gradient descent" link doesn't seem to lead anywhere.


CIV-11219 Wrong page loads on full admit

JIRA link
https://tools.hmcts.net/jira/browse/CIV-11219
Change description
defendant selects full defence, already paid
on claimant response message should be fixed as miro
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Will be part of post-case-progression-tasks branch


Fix UI tests in CI

          It looks like the CI failure is caused by an update to `bumpalo` that requires a new rustc version. Updating the CI to run ui-tests on `1.60` should fix it.

Originally posted by @jneem in https://github.com/rustwasm/wasm-bindgen/issues/3399#issuecomment-1520945826

Causing CI to fail for every PR after #3395


encapsulate the path in "adb.EXE devices" call

[x] This is a small change
[x] This change has been reported in issue #1737

Please update unit tests.

@noomorph I'm a newcomer could you please point me to the ones that I broke?

I reckon, in ADB.test.js
בתאריך יום ד׳, 6 בנוב׳ 2019, 20:35, מאת Steffen Forkmann <
<EMAIL_ADDRESS>
@noomorph https://github.com/noomorph I'm a newcomer could you please
point me to the ones that I broke?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wix/Detox/pull/1739?email_source=notifications&email_token=AAO7DZJJUTVX4SM4P5PELJDQSME5JA5CNFSM4JJUVRJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDHROEY#issuecomment-550442771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO7DZIVZN773GVMMGDYMX3QSME5JANCNFSM4JJUVRJQ
.

I think the unittests are now fixed


Bad Request: Platform

Hi
I am always getting this error now (during the execution of ./examples/timelineExporterWithDocsAndDetails.py):
{"errors":[{"errorCode":"BAD_REQUEST","errorField":null,"errorMessage":"Bad', 'Request","meta":{"source":"PLATFORM"}}]}
Any idea what's causing / how to fix this?

Hi,
I have got the same error message by executing portfolioExporter.py
Do somebody know how to fix this?

me too, does anyone know the fix please?


[Feature]: Provide configuration to switch on/off login rate limiting on self-hosted instances

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
From Appsmith version v1.9.38 onwards, the users are locked out for 24 hours if they attempt several times to log in with the wrong password and get the error: Your account is suspended for 24 hours. Please reset your password to continue.

However, it is not possible to configure the number of attempts. So we need to give instance admins the possibility of configuring this via the Admin Settings UI, for example.
Why should this be worked on?
By configuring the number of login attempts after which a user gets suspended if entering a wrong password, the instance admins can have more control over how they choose to secure their instance.

Closing this. Lets see how big a problem it really is

Another BE user requested this feature to make the number of login attempts and of reset password attempts configurable.


When can we expect the tutorials - I'd like to follow along with a CFD implementation

Hello,
I am interested in the "Tutorial: Building a Poisson Solver" tutorial and I'd like to follow along with an implementation in a CFD code.
The following aspects would be of particular importance:

What's the fastest way to import, deep copy... the linear system to ginkgo? Assume I have a CSR matrix (columns, row_ptr, values; 3 c++ vectors) and two c++ vectors (x and rhs) which are imported at each timestep (x = 0 applies only to the first timestep! of up to 10.000 timesteps); x and the final residual get copied back to the CFD application at the end of each timestep.
To manage the overall simulation (coupled linear systems), I'll need the following BLAS routines, too: ABS, reduction, axbpy.
I'd like to apply mixed precision iterative refinement fp64/fp32 on the CPU or better fp64(CPU)/fp32(GPU) to leverage modern engineering workstations
I miss an IC or AMG preconditioner which are usually most effective for solving the symmetric matrix of the pressure equation in combination with a CG solver. I'd like to use both mixed precision CG (for symmetric matrices) and BiCGStab (for asymmetric matrices) - GMRES could work for both but it's usually "rough" and less efficient for this application so the simulation needs more time and the results are not so good as the convergence of the coupled system is not so smooth.

klausbu

Hello @klausbu,
thank you for your interest in Ginkgo.

The fastest way to import a linear System or a matrix in general in Ginkgo is with Array<value_type>::view. You can see how it works in the three-pt-stencil-solver Line 192+. You basically create a matrix from a view of your existing vectors, avoiding any copies. However, you should to make sure the data is on the same executor as your solver, otherwise, Ginkgo copies it before calling kernels.
The actual data from the vectors will be updated after each kernel call (so also each iteration) regardless of if the executor of the view match with the solver (if they match, no data will be copied, if they mismatch, data will be copied after each kernel call)
We are on our way to implement an ABS function. With reduction, do you mean norm or dot? We do have a compute_norm2 , compute_dot and axpy (a call to apply).
I don't quite understand what you mean with "fp64(CPU)/fp32(GPU)"? Doing some operations on the CPU and others on the GPU is pretty much always slower than doing everything on the CPU as long as you are memory bound because copying to GPU has lower bandwidth than operating on the CPU.
We do have an example for mixed precision IR here
An AMG preconditioner is on its way (see PR #528 as a first step), an IC does already exist, but it can only be used with the ILU interface. You can create an ICT preconditioner-factory with: auto fact = std::shared_ptr<gko::LinOpFactory>(
     gko::factorization::ParIct<ValueType>::build()
         .with_iterations(parilu_iterations)
         .with_approximate_select(parilut_approx_select)
         .with_fill_in_limit(parilut_limit)
         .on(exec));
 auto precond_factory =
     gko::preconditioner::Ilu<ValueType>::build()
         .with_factorization_factory(fact)
         .on(exec);

If I missed something or have more questions, feel free to ask.

About other matrix operations needed:

ABS() means in this context to convert negative vector elements into positive ones
reduction() means adding-up all vector elements
I'll also need a spmv multiplication

This is the entire calculation to scale the residual which is used for the overall management of the convergence of a simulation:
For matrix Ax = b, residual is defined as res = b - Ax
double x_average = reduction(x)/x_size
create a vector v_x_average with all values set to x_average
vector wA = Ax
vector pA = Ax_average
double normFactor = reduction(ABS(wA - pA) + ABS(b - pA)) + SMALL where SMALL is a very small value to avoid divisions by 0
The scaled residual is then:
double scaled_residual = reduction(ABS(b - wA))/normFactor

ABS() means in this context to convert negative vector elements into positive ones

We are currently working on a get_absolute() implementation that computes the absolute of each vector. That includes both complex values (which will be converted to a real type) and real values, which will act as you described. But that is not yet merged.

reduction() means adding-up all vector elements

This type of reduction can currently be implemented with compute_dot by creating a vector of ones. Alternatively, you can also sum it up yourself (if it is on GPU, you need to copy it to CPU first).

I'll also need a spmv multiplication

We do have SpMV multiplication with each matrix format we have (b = Ax is computed with A->apply(x, b)). That also works with dense matrices.
Currently, you would need to write the filling of the x_average vector, the ABS() and the reduction() function by yourself (should be fairly easy since you can access dense matrix values with at(x, y)). The ABS() function is currently being implemented, but the others will take more time unfortunately.
If you want, I can write an example-code that does what you want, and you can use that as a starting point.

In general, we are currently discussing on how to improve our tutorials and wiki-page, so newcomers have an easy to follow path learning about the Ginkgo interface and capabilities.

@Thomas: Maybe just list the available matrix solvers, LA functions and work in progress (WIP) features somewhere.  The main obstacle is usually to provide/load the raw data (matrix in COO or CSR format, vectors and process(or) boundaries) efficiently, so some practical example would be helpful. I assume here a MPI based multi GPU implementation.
For a CFD implementation (using Ginkgo as external matrix solver library for a "deep" on GPU implementation i.e. flow + matrix solver), the following features would be great (MPI parallelism, PCG with parallel on GPU IC (multi coloured or tiled approach compatible with a scotch domain decomposition), an AMG solver and preconditioner, for some industries an orthomin solver, all for pressure / symmetric matrices. For asymmetric matrices (velocity etc.) PBiCGStab or better PBiCGStab(L) as the latter version tends to converge even smoother would be great (IDR, GMRES, PBiCG etc. are usually less stable and less smooth so one can loose the last bid of lift and drag calculation accuracy).

@klausbu All currently usable solvers can be found here: https://ginkgo-project.github.io/ginkgo/doc/develop/group__solvers.html
We do not have a MPI implementation of Ginkgo, we focus on node level parallelism (using the CPU and GPU efficiently).
We do have Preconditioned CG, but don't have Incomplete Cholesky (from what I know, adding it would not be too difficult).
An AMG solver is on its way (see #528), but we don't have an orthomin solver.
We also do have Preconditioned BiCGStab (but not BiCGStabL).
For feature requests, I will create an Issue, so we can keep track of it.

Please add multi-GPU support to the feature request too.
In my experience, OpenMP/shared memory implementations on the CPU are a lot slower than MPI/distributed memory implementations but you're the experts, high node level performance with multiple GPUs is what I am looking for.

I just added that. @tcojean is actually currently exploring this possibility. However, it is possible that it does not improve performance over a single GPU because pretty much all of our operations are memory-bound. Copying data from one to the other GPU has significantly less bandwidth than the memory bandwidth in one GPU, so getting good performance from it is not trivial.

That's why distributed memory implementations using MPI or GASPI are commonly used, as a single GPU is just not powerful enough and doesn't offer sufficient memory to solve real-world-problems, not to mention when using mixed precision iterative refinement.


Suggestion Needed for making a beautiful, updated , full stack web app for OSSU.

Hi , friends I am a student and a full stack web developer .
Currently I am working as a freelancer ,
I came across OSSU today , and really a great help for self taught dev. , I have also planned to follow this path .
But if we make a beautiful , full of information ,updated web app  and keep maintaining it , It will be quite excellent for anyone to read and understand about OSSU mission , and can follow this path easily.
--> I am interested in making website for OSSU and I will keep maintaining and updating it .
Here are some of my web web app made by me :-
https://fashionbrand.herokuapp.com/     (E-commerce clothing site)
https://spreadjoy.herokuapp.com/  (Book Donate Site by opening New Tabs)
https://dreamtrip-2-0.herokuapp.com/     (Trip-advisor)
https://love-calculator-2-0.herokuapp.com/ (Love-calculator)
https://gentleatif.github.io/v3.codingblocks.com/  (Coding Blocks )
https://gentleatif.github.io/sbi/      (SBI - Landing Page)
My portfolio web site:-
https://portfolio-37bad.web.app/
But , I need financial support for this , so I want to add a contribute button at the end of page , in OSSU web app. So if anyone want to support can support me ,
If you guys are agree on this , please let me know ..

At the moment OSSU is powered by the contributions of time and care from our community. Time to evaluate courses, to moderate communication, to tutor other learners is all donated by individuals dedicated to bringing OSSU to life. I will keep your offer in mind if that changes (if OSSU raises funds to compensate contributors or moves to an optional financial donation system for contributions).
Thank you for reaching out!

您好，邮件已收到，尽快给您回复。

      From  Hu。


Reduce log level of "Offer involves frozen asset"

https://github.com/ripple/rippled/blob/eaff9a0e6aec0ad077f118501791c7684debcfd5/src/ripple/app/tx/impl/CreateOffer.cpp#L163-L164
Please set the loggin level to something below "warn", there are many transactions out there that trigger this warning and it is not actionable on the node operator's side, just noise generated by third parties.

fixed in 0.90.0-b5


lima: 0.13.0 -> 0.14.2

Description of changes
Updates performed

Golang update
Added dependency to xcrun on darwin to detect if can compile with Virtualization.framework
Added dependency to sigtool on darwin for needed codesign command
Modify Makefile to --force codesign due to golang signing aarch64-darwin binaries by default

To inspect upstream changes

Release on GitHub
Compare changes on GitHub

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 206285 run on x86_64-darwin 1

2 packages built:

colima
lima

Built and tested successfully (via colima and docker/docker-compose) on x86_64-darwin.
But ofborg says lima.passthru.tests on aarch64-darwin failed:
> building
> mkdir -p _output/bin
> cp -a ./cmd/lima _output/bin/lima
> # The hostagent must be compiled with CGO_ENABLED=1 so that net.LookupIP() in the DNS server
> # calls the native resolver library and not the simplistic version in the Go library.
> CGO_ENABLED=1 go build -ldflags="-s -w -X github.com/lima-vm/lima/pkg/version.Version=v0.14.1" -tags "no_vz" -o _output/bin/limactl ./cmd/limactl
> codesign --entitlements vz.entitlements -s - ./_output/bin/limactl
> libc++abi: terminating with uncaught exception of type std::runtime_error: file is already signed. pass -f to sign regardless.
> make: *** [Makefile:182: codesign] Abort trap: 6

I have a little feeling that it may be because the binary was already built and not cleaned up or something like that. I added a rm -rf _output and will try again.

Thanks for this.
vz appears not to be supported:
limactl start template://experimental/vz                                                                                ~
? Creating an instance "vz" Proceed with the current configuration
FATA[0005] vm driver 'vz' needs macOS 13 or later (Hint: try recompiling Lima if you are seeing this error on macOS 13)

I assume this is because nixpkgs doesn't use the macOS 13 SDK? All of the required entitlements are present on the executable, but I see that lima's Makefile disables it when the SDK is too old:
https://github.com/lima-vm/lima/blob/baca0e7ecd1b3515f471d2eb60fdbb0864e9a487/Makefile#L19

Thanks for this.
vz appears not to be supported:
limactl start template://experimental/vz                                                                                ~
? Creating an instance "vz" Proceed with the current configuration
FATA[0005] vm driver 'vz' needs macOS 13 or later (Hint: try recompiling Lima if you are seeing this error on macOS 13)

I assume this is because nixpkgs doesn't use the macOS 13 SDK? All of the required entitlements are present on the executable, and I'm running (and building on) macOS 13.1, but I see that lima's Makefile disables it when the SDK is too old:
https://github.com/lima-vm/lima/blob/baca0e7ecd1b3515f471d2eb60fdbb0864e9a487/Makefile#L19

Yeah you're right, looks like xcrun is only running at 10.12 whatever the version of macos installed. I don't know how to tell nix to use a more up to date version of the SDK if available on the host machine.

I'm not that familiar with nix, and especially not with darwin/macOS, but I wanted to share what I tried just in case it's helpful.
I was naively hoping that an overlay like:
(final: prev: {
    lima = prev.lima.override (old: { xcbuild = old.xcbuild.override(_: { sdkVer = "13.0"; }); });
  })

would get things building, but unfortunately it errors with:
building
mkdir -p _output/bin
cp -a ./cmd/lima _output/bin/lima
# The hostagent must be compiled with CGO_ENABLED=1 so that net.LookupIP() in the DNS server
# calls the native resolver library and not the simplistic version in the Go library.
CGO_ENABLED=1 go build -ldflags="-s -w -X github.com/lima-vm/lima/pkg/version.Version=v0.14.2" -tags "" -o _output/bin/limactl ./cmd/limactl
# github.com/Code-Hex/vz/v3
In file included from vendor/github.com/Code-Hex/vz/v3/audio.go:6:
In file included from ./virtualization_11.h:9:
./virtualization_helper.h:25:9: warning: macOS 12.3 API has been disabled [-W#pragma-messages]
#pragma message("macOS 12.3 API has been disabled")
        ^
./virtualization_helper.h:32:9: warning: macOS 13 API has been disabled [-W#pragma-messages]
#pragma message("macOS 13 API has been disabled")
        ^
In file included from vendor/github.com/Code-Hex/vz/v3/audio.go:6:
./virtualization_11.h:10:9: fatal error: 'Virtualization/Virtualization.h' file not found
#import <Virtualization/Virtualization.h>
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 warnings and 1 error generated.
make: *** [Makefile:94: _output/bin/limactl] Error 2

I think lima is pulling in vz, which the lima derivation is building too?
virtualization_helper.h checks the value of __MAC_OS_X_VERSION_MAX_ALLOWED, so this might need to be set/overridden too?

Thanks for the help @jonathanlking will look into the way you did if I can make it work.
I'm also a bit concerned how to implement this to be available for users using nix on machine prior to 13.0 as well as after.

lima provides binaries, and this may be a case where it makes sense to use them for macOS. nixpkgs could provide a lima-binary package so that the user has a choice about which one to use.

lima provides binaries, and this may be a case where it makes sense to use them for macOS. nixpkgs could provide a lima-binary package so that the user has a choice about which one to use.

Could be an idea also.
I'm honestly more concern over having it breaks on users using a version of macos prior to 13.0.

Using 13.x SDK should work even on older version of macos. It only makes new APIs available, but if the program doesn't call them (or only calls them after checking the host os version), it shouldn't cause issues. Lima uses vz to access the Virtualization API, and it has this kind of doc: https://github.com/Code-Hex/vz/blob/957dfd2add9a0badf25dee8cd1dc01a79e8fee06/bootloader.go#L137
// NewEFIBootLoader creates a new EFI boot loader.
//
// This is only supported on macOS 13 and newer, error will
// be returned on older versions.

Of course, vz-based VMs won't work on macos12 and before, but the qemu-based driver should still work without issues.

https://github.com/NixOS/nixpkgs/pull/206285#issuecomment-1370237743
@jonathanlking did you try this on a machine running macos Ventura ?

#206285 (comment) @jonathanlking did you try this on a machine running macos Ventura ?

@dennajort Yes, this is on macOS 13.0.1 running on an M1

To use it, reference apple_sdk_11_0 instead of apple_sdk in your derivation and use pkgs.darwin.apple_sdk_11_0.callPackage instead of pkgs.callPackage. On Linux, this will have the same effect as pkgs.callPackage, so you can use pkgs.darwin.apple_sdk_11_0.callPackage regardless of platform.

I tried this as well, but it doesn't help, as the vz feature requires macOS SDK 13.0, but the most recent nixpkgs has is 11.0 (via the apple_sdk_11_0 stdenv).

My feeling at the moment is that a lima-binary package might be considerably easier 😅

That's what I concluded after trying the apple_sdk_11_0 option. Even if someone started adding support for macOS SDK 13.0 today, it would likely be months before it was ready, if past experience is any guide.

@jonathanlking @dhess
I tried going down that path with the following changes:
diff --git a/pkgs/applications/virtualization/lima/default.nix b/pkgs/applications/virtualization/lima/default.nix
index 29dd9b27232..a282e4c30de 100644
--- a/pkgs/applications/virtualization/lima/default.nix
+++ b/pkgs/applications/virtualization/lima/default.nix
@@ -7,6 +7,8 @@
 , xcbuild
 , sigtool
 , makeWrapper
+, Virtualization
+, Cocoa
 }:

 buildGoModule rec {
@@ -22,6 +24,8 @@ buildGoModule rec {

   vendorSha256 = "sha256-l53MTxLY/uid+0U/eY96l0aBWKImST1gN2BARilh2K0=";

+  buildInputs = lib.optionals stdenv.isDarwin [ Virtualization Cocoa ];
+
   nativeBuildInputs = [ makeWrapper installShellFiles ]
     ++ lib.optionals stdenv.isDarwin [ xcbuild.xcrun sigtool ];

@@ -29,7 +33,8 @@ buildGoModule rec {
   postPatch = ''
     substituteInPlace Makefile \
       --replace 'binaries: clean' 'binaries:' \
-      --replace 'codesign --entitlements vz.entitlements -s -' 'codesign --force --entitlements vz.entitlements -s -'
+      --replace 'codesign --entitlements vz.entitlements -s -' 'codesign --force --entitlements vz.entitlements -s -' \
+      --replace 'MACOS_SDK_VERSION=$(shell xcrun --show-sdk-version | cut -d . -f 1)' 'MACOS_SDK_VERSION=13'
   '';

   # It attaches entitlements with codesign and strip removes those,

diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index 8fa2336e176..601d86d8f43 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -36777,8 +36777,9 @@ with pkgs;

   colima = callPackage ../applications/virtualization/colima { };

-  lima = callPackage ../applications/virtualization/lima {
+  lima = darwin.apple_sdk_11_0.callPackage ../applications/virtualization/lima {
     inherit (darwin) sigtool;
+    inherit (darwin.apple_sdk_11_0.frameworks) Virtualization Cocoa;
   };

   logtop = callPackage ../tools/misc/logtop { };

This then leads to the next errors:
vendor/github.com/Code-Hex/vz/v3/virtualization_helper.h:25:9: warning: macOS 12.3 API has been disabled [-W#pragma-messages]
vendor/github.com/Code-Hex/vz/v3/virtualization_helper.h:32:9: warning: macOS 13 API has been disabled [-W#pragma-messages]
virtualization_12.m:14:52: error: property 'canStop' not found on object of type 'VZVirtualMachine *'
virtualization_12.m:27:42: warning: instance method '-stopWithCompletionHandler:' not found (return type defaults to 'id') [-Wobjc-method-access]
/nix/store/lv5xsqihygkhyb9djf840nhlymi7j77m-apple-framework-Virtualization-11.0.0/Library/Frameworks/Virtualization.framework/Headers/VZVirtualMachine.h:57:12: note: receiver is instance of class declared here
virtualization_12.m:42:18: error: unknown receiver 'VZGenericPlatformConfiguration'; did you mean 'VZSerialPortConfiguration'?
/nix/store/lv5xsqihygkhyb9djf840nhlymi7j77m-apple-framework-Virtualization-11.0.0/Library/Frameworks/Virtualization.framework/Headers/VZVirtualMachineConfiguration.h:16:8: note: 'VZSerialPortConfiguration' declared here
virtualization_12.m:42:56: error: 'init' is unavailable
/nix/store/lv5xsqihygkhyb9djf840nhlymi7j77m-apple-framework-Virtualization-11.0.0/Library/Frameworks/Virtualization.framework/Headers/VZSerialPortConfiguration.h:26:1: note: 'init' has been explicitly marked unavailable here
virtualization_12.m:55:50: warning: instance method '-setDirectorySharingDevices:' not found (return type defaults to 'id') [-Wobjc-method-access]
/nix/store/lv5xsqihygkhyb9djf840nhlymi7j77m-apple-framework-Virtualization-11.0.0/Library/Frameworks/Virtualization.framework/Headers/VZVirtualMachineConfiguration.h:46:12: note: receiver is instance of class declared here
virtualization_12.m:70:88: error: expected expression
virtualization_12.m:70:63: error: use of undeclared identifier 'VZPlatformConfiguration'

According to this pr it should be possible to use vz on sdk 11.0, however the guarding in https://github.com/Code-Hex/vz/blob/957dfd2add9a0badf25dee8cd1dc01a79e8fee06/virtualization_12.m#L9-L20
is not working properly.
Even if get all that to work, it seems fragile to me because the root problem is that we are two major sdk versions behind. So I guess a binary version of lima is indeed the better approach for those who want the bleeding edge experimental vz emulation.

I opened a pr for the lima binary derivation https://github.com/NixOS/nixpkgs/pull/209171.

Thanks for your help on that !
My idea is to not try to fiddle too much with the apple sdk at the moment. As is, if the new apple sdks are added to nix, it may work automatically if I understand ?

lima uname -a works just fine 👍

@ofborg build lima colima


[2.0-wip] [iOS5] Popover example doesn't close (on a special case)

Using iOS5, iPhone 4S and Safari... Popover example doesn't close once you tap to the red "hover for popover" button.
Interestingly, the popover inside the modal works just fine.
Is this because the "well area" is too small to tap?
And is it likely to discover a more intuitive way to interact with tooltips and popovers for touch screens? Like tapping the first time opens it, and tapping the second time closes it?

@fat Can you check this one out?

personally i feel like popover/tooltips are horrible mobile conventions - but i'll take a look into. Basically anything that works off of mouseenter/mouseleave is pretty jank


Given path variable should support the full exposure path

When the validator is called like so:
def rc = validator.isValidRequest(payload, verb, path, queryParams, headers);

the given path might contain the entire path as it is exposed on the API-Gateway. But, the path is used to lookup the schema as defined in API-Specification and obviously it fails, when the path includes the customer specific exposure path.
For example when the Petstore is exposed on the API-Manager customers might configure them with a different exposure path: /api/petstore/v3.
At runtime, a number of variables contain the API-Path, but all of them include the Frontend-API exposure path. For instance: /api/petstore/v3/store/order/123456.
To simplify the use of this plugin, the validator should support such a path, even if it contains the frontend API Exposure path.
This should eliminate the need to manipulate the path variable in the scripting code and thus complicate the code unnecessarily.

The given path might be the FE-API exposure path which is not guaranteed to be part of the API-Specification.
If for example the Petstore is exposed with /petstore/v3 the path we get might be /api/petstore/v3/store/order/78787
and with that, the validation fails with the following error, as the specification doesn't contain this path.
No API path found that matches request '/api/petstore/v3/store/order/78787'.

As part of this new feature, the validator is trying up to 5 times to perform the validation and each time, it's removing the first path of the path:
Validate request: [verb: DELETE, path: '/api/petstore/v3/store/order/1234', payload: 'N/A']
No API path found that matches request '/api/petstore/v3/store/order/1234'.
Retrying validation with reduced path: '/petstore/v3/store/order/1234'] (1/5)
No API path found that matches request '/petstore/v3/store/order/1234'.
Retrying validation with reduced path: '/v3/store/order/1234'] (2/5)
No API path found that matches request '/v3/store/order/1234'.
Retrying validation with reduced path: '/store/order/1234'] (3/5)
# This time the path is found in the API-Specification and the validation is finally performed

To improve the performance, the given original path mapped to the API-Specificaion path found in the API-Specification is internally cached. /api/petstore/v3/store/order/78787 --> /store/order/1234. This cache is limited to 1000 entries.
You can adjust the size of this cache from the script code:
validator.getExposurePath2SpecifiedPathMap().setMaxSize(5000);


ARROW-3700: [C++] Ignore empty lines in CSV files

The option is configurable, as it may be legitimate to parse empty lines as null values in a single-column CSV file (though that's probably uncommon).

Codecov Report

Merging #2907 into master will increase coverage by 1.25%.
The diff coverage is 94.8%.

@@            Coverage Diff             @@
##           master    #2907      +/-   ##
==========================================
+ Coverage   87.22%   88.48%   +1.25%
==========================================
  Files         417      348      -69
  Lines       65219    59810    -5409
==========================================
- Hits        56886    52921    -3965
+ Misses       8239     6889    -1350
+ Partials       94        0      -94

Impacted Files
Coverage Δ

cpp/src/arrow/csv/parser.h
100% <ø> (ø)
:arrow_up:

cpp/src/arrow/csv/options.h
100% <ø> (ø)
:arrow_up:

cpp/src/arrow/csv/csv-parser-test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/arrow/csv/parser.cc
95.74% <100%> (+0.29%)
:arrow_up:

python/pyarrow/tests/test_csv.py
97.43% <100%> (+0.05%)
:arrow_up:

cpp/src/arrow/csv/test-common.h
100% <100%> (ø)
:arrow_up:

python/pyarrow/_csv.pyx
70.87% <50%> (-1.01%)
:arrow_down:

cpp/src/arrow/python/common.h
100% <0%> (ø)
:arrow_up:

rust/src/record_batch.rs

go/arrow/array/table.go

... and 85 more

Continue to review full report at Codecov.

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


[MXNET-1212] Documentation fix on the SSD example

Description
Documentation change regarding the conversation in this PR: https://github.com/apache/incubator-mxnet/pull/13162
@nswamy @andrewfayres @zachgk
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@mxnet-label-bot add [pr-awaiting-review]

The same files are also addressed in #13277  ?

Since @andrewfayres address this as well, this one will be closed


fix(Tooltip): fix useLayoutEffect ssr warning

Overview

PR Checklist

[x] Related to designs: None
[x] Related to JIRA ticket: None
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Don't make me tap the sign.
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.183-alpha.da947b.0@codecademy/gamut-labs@33.1.4-alpha.da947b.0@codecademy/gamut@50.4.2-alpha.da947b.0@codecademy/monaco@0.6.75-alpha.da947b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://62ffea0e73d245367e1fa3f3--gamut-preview.netlify.appDeploy Logs


Issues for taking different input shapes as an input into network.

solved!

@kihyun1118 Can you please share how you solved this issue?


Rewrote documentation

I have completely rewrote all documentation website (https://material-ui-pickers.firebaseapp.com/)

Wow, that's awesome!

@dmtrKovalenko That's great 👍 👍 May I add a jalaali section later?

@alitaheri Yep I think we will add a new section related to localization and completely describe moment, date-fns and jalaali localization :)


the total IOPS could be incorrect.

"The Standard_D8s_v3 can achieve a total of 28,600 IOPS.", why it cann't achieve a total of 28,800 IOPS? I thought 16,000 + 12,800 == 28,800?
Standard_D8s_v3
Cached IOPS: 16,000
Uncached IOPS: 12,800

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

ID: b95355f8-79de-38fd-a0c3-c4e4889b9946
Version Independent ID: 954d1291-f787-41f0-cd0f-4bc0f8a38409
Content: Disk metrics - Azure Virtual Machines
Content Source: articles/virtual-machines/disks-metrics.md
Service: storage
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

@DavidChenLiang, Thanks for the feedback! We are taking a look into this and will get back to you soon.

@DavidChenLiang Firstly, , apologies for the delay in responding here and any inconvenience this issue may have caused.

For more information refer to this article: https://docs.microsoft.com/en-us/azure/virtual-machines/dv3-dsv3-series
I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/ since it's not directly related to the documentation. We'll follow up there. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update installing.html.md.erb

Making a PR as @vikafed probably should put eyes on this before it's committed. Applies to both 1.0 and 1.1. Please ask in #pcf-healthwatch-dev channel if clarification needed. Thanks!

Thanks, @AmberAlston!


pip installation does not have all required dependencies

When installing ophyd via pip i noticed simdetector and similar devices break:
>>> from ophyd.areadetector.detectors import SimDetector
>>> s = SimDetector("SIM:", name="SIM")
>>> s.cam.acquire.put(1)
Traceback (most recent call last):
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 327, in __get__
    return instance._signals[self.attr]
           ~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'cam'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 327, in __get__
    return instance._signals[self.attr]
           ~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'array_size_z'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 329, in __get__
    return instance._instantiate_component(self.attr)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1354, in _instantiate_component
    self._signals[attr] = cpt.create_component(self)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 266, in create_component
    cpt_inst = self.cls(pv_name, parent=instance, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 897, in __init__
    getattr(self, attr)
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 325, in __get__
    print(instance._signals)
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/ophydobj.py", line 580, in __repr__
    info = ", ".join("{}={!r}".format(key, value) for key, value in info)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/ophydobj.py", line 580, in <genexpr>
    info = ", ".join("{}={!r}".format(key, value) for key, value in info)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1644, in __repr__
    return repr(list(self))
                ^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1625, in __len__
    return len(self.__internal_list())
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1607, in __internal_list
    return list(itertools.chain.from_iterable(out))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1602, in <genexpr>
    out = (
          ^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1142, in _get_components_of_kind
    yield component_name, getattr(self, component_name)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 329, in __get__
    return instance._instantiate_component(self.attr)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 1354, in _instantiate_component
    self._signals[attr] = cpt.create_component(self)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/device.py", line 266, in create_component
    cpt_inst = self.cls(pv_name, parent=instance, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/signal.py", line 1531, in __init__
    super().__init__(read_pv, string=string, name=name, **kwargs)
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/signal.py", line 972, in __init__
    self._read_pv = self.cl.get_pv(
                    ^^^^^^^^^^^^^^^
  File "/opt/micromamba/envs/teste-deletar/lib/python3.12/site-packages/ophyd/_dummy_shim.py", line 51, in get_pv
    raise NotImplementedError
NotImplementedError

This does not happen when installing via conda-forge.
@flowln noticed that here there is a fallback to "dummy" in case neither caproto nor pyepics are installed.
The error doesnt happen in conda-forge installations since they come with pyepics and caproto.
Maybe adding these as dependencies in setup.py would fix this?

This was intentional as we do not want to have a hard requirement on a particular epics implementation (or any at all!) at the project metadata level (we also have an optional dependency on Matplotlib) because this is much harder to remove at a packaging (e.g. conda) level.   On the other hand it is very easy for packaging ecosystems to add extra dependencies.
We also have the idea of supporting other control systems (e.g. https://github.com/bluesky/ophyd-tango) and in those use cases they should be able to depend on ophyd without picking up a transient dependency on another control system.
I am inclined to continue to not have a hard dependency, however I think adding extra groups for [caproto] and [pyepics] would be reasonable.

I agree with not adding a hard dependency, however I do think there should be a user-facing warning in the case the dummy layer is used, as it (as shown) can create issues that are not immediately obvious as to what the cause is (maybe adding an explanation to the NotImplementedError raised would be the best place for that).

We can not warn because we do not know we need to warn the user until we hit the error.  We do not want to warn users who will never need epics.

(maybe adding an explanation to the NotImplementedError raised would be the best place for that).

I agree that is the best place for this!


[DataProxy] Select the corresponding configuration parameters according to the type of MQ

Description
The parent issue is:https://github.com/apache/inlong/issues/5431
InLong Component
InLong DataProxy
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

From the current DataProxy implementation analysis, a cluster to which a DataProxy belongs can only handle one type of MQ.
So, the corresponding MQ type is saved according to the return of the Manager, and the corresponding improvement will be made when the subsequent implementation is adjusted.


Add sparsity pattern

Built upon #125 (Commit af0fc3b)

Closed the pull request because the sparsity pattern constructor cannot be generalized to deal with constraints which contain if-statement and min/max functions.


Update

New Soletta module update.
An API is introduced to update Soletta apps. The overall idea is that
different update modules can be used on different Soletta scenarios.
The API is quite straightforwad, with methods to check for updates,
fetch and install them.
A module to update Soletta app statically built running as PID1 is also
presented, to check and showcase the API. This is a simple update, just
Soletta app file is changed.
Node-types were made so one can update the app via fbp - and a sample was
also added.
Note that update module expects that device boots via EFI using an startup.nsh
script, showcased on samples. I'm not sure if we will integrate this somehow
with image generation - but there are more steps to make Linux micro one static
file a reality, though.
Documentation should give a better insight of this new feature.

v2 on #1122 (but it's old already, check #1133 )


[wip] convert Filter to .ts

This is an initial start on converting the filter.js to typescript. Its still a huge WIP but I thought I would start a draft PR so that no one else starts working on the filter.

this is a great start!

@tambien awesome. Thanks for the feedback. I've converted all of it along with the test. Its definitely not perfect yet. I'm a little stuck on the types, I think my knowledge of typescript breaksdown here https://github.com/Tonejs/Tone.js/pull/503/files#diff-6aed955877c105e29b449324d18737ebR45
How do we handle that as a filtertype and a number?


Updated to glium 0.14

Updating dependencies so works with glium 0.14 which had a couple of breaking changes.

Thanks! Looks good


Reproducibility of the Pong result

Hi,
Thanks for sharing the code!
Quick question: do you find the training results reproducible? I'm training the rl network for PONG using your code and the parameters provided, however, the results varies a lot from trial to trial, some converges, some doesn't. I wonder if you also see this?
Thanks!

Yes, you are right. PONG often does not converge in my code.


bokchoy version 0.9.1

I want to push a new version to pypi containing this: https://github.com/edx/bok-choy/pull/202

Just noticed the test failure, looks like a doctest needs to be updated.


Add ReactFlow to Workflow Details page

Description
This PR adds a new ReactFlow instance into the workflow details page.
More details:

Uses the ReactFlow documentation for persisting ReactFlow state (nodes / edges) in a React component via useNodesState() / useEdgesState(), respectively. It also includes defining other flow lifecycle functions, like onDrop(), onDragOver(), and onConnect(). This is where we will define how we want to manipulate the ReactFlow state, and gives us the opportunity for any other data we may need to fetch from redux store (or trigger any API calls ourselves)
Adds a ReactFlowContextProvider in order to persist ReactFlow state. This provider wraps the entire application so all nested components can consume and access contextual values via useContext(). By default, we add a few stub functions to delete nodes and edges, which are not something that comes by default via <ReactFlow> component. We don't add this in redux store since it serves a different purpose (sharing data across components vs. having a centralized datastore), and allows for state changes to be made anywhere and often (updating the ReactFlowInstance, triggering deletion functions, for example).
The workflow state and the low-level ReactFlow JSON I have hardcoded for now; it is still TBD on where this information will live exactly, or how much we want/need to generate on-the-fly.

Next steps:

Integrate the added components in #32 as ReactFlow node types, such that they are visible in the ReactFlow workspace
Improve the workspace state & datastore. Can use hardcoded values for now, but should have the following state for each workflow: 1/ high-level redux store persisting the workspace state, and 2/ low-level ReactFlow JSON. This way, each workflow can be rendered and show a unique workflow state when loading the details page. The exact difference between 1/ and 2/ is still TBD

Demo video w/ hardcoded workspace state:
screen-capture (18).webm
Issues Resolved
Makes progress on #10, #12
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

nit: should we use the newest reactflow version available right now? 11.9.2

nit: should we use the newest reactflow version available right now? 11.9.2

Oh I just realized 11.8.3 -> 11.9.x happened 12 hours ago, just looked at the release date. Anyways we can probably wait as I see they had fast iteration with 11.9.1/2 fixing things in 11.9.0

nit: should we use the newest reactflow version available right now? 11.9.2

Oh I just realized 11.8.3 -> 11.9.x happened 12 hours ago, just looked at the release date. Anyways we can probably wait as I see they had fast iteration with 11.9.1/2 fixing things in 11.9.0

Also, it will be changing to xyflow sometime in the near future: https://wbkd.notion.site/Upcoming-Changes-at-React-Flow-1a443641891a4069927c0a115e915251. Depending on when that happens, we may update to that. The earlier, the better.


URP Support

URP support has been requested. The current the shader is only setup to support HDRP.
Definition of done:
URP branch with similar features to HDRP.

Has there been any development on this enhancement for URP support?

Unfortunately not recently, no. I haven't played with the newer renditions of URP. I'll re-evaluate this when I have some free time. It shouldn't be too difficult and with a little knowledge of shaderlab / URP you could likely port it.

bump :)

Just tested this, it works out of the gate apparently, go wild.


what is fastlane action appium spec_path

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Hi I would like to ask regarding how to use fastlane action appium. I'm not sure what exactly to write in spec_path

Path to Appium spec directory

Thanks!

Sorry I don't understand the question, could you clarify?

Hi thanks for checking,
appium(
  app_path:  "appium/apps/TargetApp.app",
  spec_path: "appium/spec",
  platform:  "iOS",
  caps: {
    versionNumber: "9.1",
    deviceName:    "iPhone 6"
  }
)

In the code above, what is "appium/spec"
is it the folder that contains files like TestXXX.class ?
If you can show an example that would be great, thanks!


Validate components are not granted access to undefined k/v stores

ivan@hecate:~/testing/kvmadness$ spin up
Error: host component error: Component kvmadness is granted access to key-value store 'bibblybobbly', which is not defined

Caused by:
    Component kvmadness is granted access to key-value store 'bibblybobbly', which is not defined
Error: exit status: 1
ivan@hecate:~/testing/kvmadness$ spin up --runtime-config-file runtime-config.toml
Logging component stdio to ".spin/logs/"
Storing default key-value data to ".spin/my_super_duper_store.db"

Serving http://<IP_ADDRESS>:3000
Available Routes:
  kvmadness: http://<IP_ADDRESS>:3000 (wildcard)

(I'm not mad keen on the "host component error" string or the duplicated text, but this is a "should rarely happen" error so I'm wary of changing things that might break existing error paths.)

@rylev I tried adding more pointers and I like it but it really magnifies the effect of the doubling printing:
ivan@hecate:~/testing/kvmadness$ spin up
Error: host component error: One or more components use key-value stores which are not defined.
Check the spelling, or pass a runtime configuration file that defines these stores.
See https://developer.fermyon.com/spin/dynamic-configuration#key-value-store-runtime-configuration
Details:
- Component kvmadness uses store 'bibblybobbly'

Caused by:
    One or more components use key-value stores which are not defined.
    Check the spelling, or pass a runtime configuration file that defines these stores.
    See https://developer.fermyon.com/spin/dynamic-configuration#key-value-store-runtime-configuration
    Details:
    - Component kvmadness uses store 'bibblybobbly'
Error: exit status: 1

I'll see if I can find what's doing this; if it's not an easy and obviously-safe fix, then maybe we just accept it and record a separate issue - again, not something people should run into too often!

Okay I am not sure how to fix the double printing.  validate_app returns an anyhow::Error which the caller wraps in a Error::HostComponentError to conform to the return type of load_app.  HostComponentError is declared as:
    #[error("host component error: {0:#}")]
    HostComponentError(#[source] anyhow::Error),

If I remove the #[source] from the attribute then I get "Error: host component error: One or more components use..." which is fine but I suspect it loses context for other, nastier, things that get turned into HCEs...  If I remove the {0:#} from the attribute, it probably preserves context better (?), but the printout is now "Error: host component error [blank line] Caused by: One or more components use..."  @lann is either of these two changes acceptable and if so do you have a recommendation?  Or should I wrap this error differently so as to avoid the problem altogether?

Or we could create a new ValidationError case and declare it as #[error(transparent)] so it gets passed through without the "host component error" bit.


nvidiaLegacy340 broken on 18.09 with Linux 4.19.2

Issue description
Our current legacy nvidia driver of the 340 branch does not work with kernel version 4.19.2:
[…]
/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/source/include/linux/rtc.h: In function 'rtc_tv_nsec_ok':
/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/source/include/linux/rtc.h:245:22: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  if (to_set->tv_nsec < TIME_SET_NSEC_FUZZ) {
                      ^
/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/source/include/linux/rtc.h:250:22: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  if (to_set->tv_nsec > NSEC_PER_SEC - TIME_SET_NSEC_FUZZ) {
                      ^
/build/kernel/nv.c: In function 'nv_start_rc_timer':
/build/kernel/nv.c:2407:5: error: implicit declaration of function 'init_timer'; did you mean 'init_timers'? [-Werror=implicit-function-declaration]
     init_timer(&nvl->rc_timer);
     ^~~~~~~~~~
     init_timers
/build/kernel/nv.c:2408:28: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
     nvl->rc_timer.function = nvidia_rc_timer;
                            ^
/build/kernel/nv.c:2409:18: error: 'struct timer_list' has no member named 'data'
     nvl->rc_timer.data = (unsigned long) nvl;
                  ^
cc1: some warnings being treated as errors
make[3]: *** [/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/source/scripts/Makefile.build:306: /build/kernel/nv.o] Error 1
make[2]: *** [/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/source/Makefile:1517: _module_/build/kernel] Error 2
make[2]: Leaving directory '/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/build'
make[1]: *** [Makefile:146: sub-make] Error 2
make[1]: Leaving directory '/nix/store/92q2v3lr0ls0p7j3sk0drp05iga3yazs-linux-4.19.2-dev/lib/modules/4.19.2/source'
NVIDIA: left KBUILD.
nvidia.ko failed to build!

NixOS is currently on the 340.104 version, but upstream is on 340.107:
https://www.nvidia.com/download/driverResults.aspx/135161/en-us
I hope that updating to 340.107 resolves the issue, but I don't understand how to update the different checksums for the nvidia driver.
Steps to reproduce
services.xserver.videoDrivers = [ "nvidiaLegacy340" ];
boot.kernelPackages = pkgs.linuxPackages_latest;

Technical details
/nix/store/kic17fw8wil74k04kzh3dha43izrr9j3-bash-interactive-4.4-p23-dev
copying path '/nix/store/kic17fw8wil74k04kzh3dha43izrr9j3-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...

system: "x86_64-linux"
host os: Linux 4.19.2, NixOS, 18.09.1363.b37872d4268 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.3
channels(root): "nixos-18.09.1363.b37872d4268"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

The hashes are located at https://github.com/NixOS/nixpkgs/blob/release-18.09/pkgs/os-specific/linux/nvidia-x11/default.nix#L32
and can be generated like so:
# nix-prefetch-url http://us.download.nvidia.com/XFree86/Linux-x86_64/340.104/NVIDIA-Linux-x86_64-340.104.run
path is '/nix/store/0v30yddx1sdsj2cnzxfvdm8shisn3x8n-NVIDIA-Linux-x86_64-340.104.run'
18k65gx6jg956zxyfz31xdp914sq3msn665a759bdbryksbk3wds

# nix-prefetch-url http://us.download.nvidia.com/XFree86/Linux-x86_64/340.107/NVIDIA-Linux-x86_64-340.107.run
path is '/nix/store/5083hr9iscfzy6yrkldlzp0hbcvgaq84-NVIDIA-Linux-x86_64-340.107.run'
0pv9yv3x0kg9hfkmc50xb54ahxkbnyy2vyy4hj2h0s6m9sb5kqz3

# nix-prefetch-url http://us.download.nvidia.com/XFree86/Linux-x86/340.104/NVIDIA-Linux-x86-340.104.run
path is '/nix/store/i3xjphbmyxz2wwmkkw0cqy5zwhhcm47k-NVIDIA-Linux-x86-340.104.run'
1l8w95qpxmkw33c4lsf5ar9w2fkhky4x23rlpqvp1j66wbw1b473

# nix-prefetch-url http://us.download.nvidia.com/XFree86/Linux-x86/340.107/NVIDIA-Linux-x86-340.107.run
path is '/nix/store/x2ciqxw9br84hvbv32mnj9zdxl8bglgd-NVIDIA-Linux-x86-340.107.run'
0mh83affz6bim26ws7kkwwcfj2s6vkdy4d45hifsbshr82qd52wd

# nix-prefetch-url https://download.nvidia.com/XFree86/nvidia-settings/nvidia-settings-340.104.tar.bz2
path is '/nix/store/hqpgx82ak2xfk0l11f1gf7y8bf527cvp-nvidia-settings-340.104.tar.bz2'
1vvpqimvld2iyfjgb9wvs7ca0b0f68jzfdpr0icbyxk4vhsq7sxk

# nix-prefetch-url https://download.nvidia.com/XFree86/nvidia-settings/nvidia-settings-340.107.tar.bz2
path is '/nix/store/grm94883wjy8lknap52m9naqav9q5vb9-nvidia-settings-340.107.tar.bz2'
1rgaa24acdyqa1rqrx56293vxpskr792njqqpigqmps04llsx703

# nix-prefetch-url https://download.nvidia.com/XFree86/nvidia-persistenced/nvidia-persistenced-340.104.tar.bz2
path is '/nix/store/099v0vs4lgnsx8p9h3ds8l3jwh0jh8pd-nvidia-persistenced-340.104.tar.bz2'
0zqws2vsrxbxhv6z0nn2galnghcsilcn3s0f70bpm6jqj9wzy7x8

# nix-prefetch-url https://download.nvidia.com/XFree86/nvidia-persistenced/nvidia-persistenced-340.107.tar.bz2
path is '/nix/store/9x78zvjfl9wgdgmg6nlq01f4axxgx82f-nvidia-persistenced-340.107.tar.bz2'
0nwv6kh4gxgy80x1zs6gcg5hy3amg25xhsfa2v4mwqa36sblxz6l

Please try:
  legacy_340 = generic {
    version = "340.107";
    sha256_32bit = "0mh83affz6bim26ws7kkwwcfj2s6vkdy4d45hifsbshr82qd52wd";
    sha256_64bit = "0pv9yv3x0kg9hfkmc50xb54ahxkbnyy2vyy4hj2h0s6m9sb5kqz3";
    settingsSha256 = "1rgaa24acdyqa1rqrx56293vxpskr792njqqpigqmps04llsx703";
    persistencedSha256 = "0nwv6kh4gxgy80x1zs6gcg5hy3amg25xhsfa2v4mwqa36sblxz6l";
    useGLVND = false;

    patches = maybePatch_drm_legacy ++ [ ./vm_operations_struct-fault.patch ];
  };

@cyounkins Thanks alot for giving me a hand and teaching me how to get those four hashes! :+1:
Updating to 340.107 indeed resolves this issue. PR: #50841


Dev kmr

resolve some issues where a new controller build was not being properly tested

make sure that the ci tests it's own ability to build images
when a new controller build is being tested force it to build new images rather than used cached ones to ensure that the build process works with the new controller

Forcing this to merge without reviews or passing all of the checks in order to work around the bug this is meant to fix -- the CI now detects the bug that is present in the crucible repo and so it fails.


Scroll to bottom doesn't work correctly in inactive tab

Describe the bug
Scroll to bottom doesn't work correctly in inactive tab - video
To Reproduce

Bookmark this storybook page https://inokawa.github.io/virtua/?path=/story/advanced-chat--default
Open it in a new tab (tab should be inactive while page is loading)
Go to that tab
Result: list is not scrolled to the bottom

Expected behavior
Scroll to bottom works correctly in inactive tab
Platform:

Browser:  reproduced in Chrome and Edge, not reproduced in Safari
Version of this package: 0.31.0

It seems that ResizeObserver doesn't fire on non-active window in some browsers. Scheduled imperative scrolling waits for the resize events so timeout will happen.
As a workaround, you may be able to wait for the tab to be active with document.addEventListener("visibilitychange", callback) and then call imperative scroll. Or maybe we should implement similar logic inside virtua.

Maybe support of initial scroll position (https://github.com/inokawa/virtua/issues/415, https://github.com/inokawa/virtua/pull/422) could solve the issue?
In the real project, where components are heavier than in storybook, this initial scroll to bottom sometimes is noticeable for user.

#415 will not solve this issue, because #415 is just an unimplemented feature but this issue is a browser problem.

I understand. I guessed that if I had ability to set the initial scroll position without extra render cycle, maybe it wouldn't need to wait for resize events and the problem would go away.

A similar issue happens in safari if I switch pages back and forward by swiping. @inokawa do you have any idea why it can happen and how to fix it?
https://github.com/inokawa/virtua/assets/37265338/beb6fbfe-309d-4ac3-9967-09566fcca6a4

Thank you for the report!
In the situation, window is always active but scrollTo has timed out earlier than the initial resize. Maybe we should add a logic to wait for the initial resize and then trigger the scroll only on mount.

Fixed in 0.33.3.


Greedy fusion breaks loop with nested SDFG

Describe the bug
An application of  greedy_fuse breaks one of the loops in CloudSC, as seen in the screenshot below. In this context, ZSINKSUM is both an input and output variable. The variable is correctly initialized but stored in the additional and unnecessary variable __tmp2 that is never passed correctly to the actual function.
Generated code:
DACE_DFI void loop_body_6_1_138_7(double* __restrict__ ZSOLQA, double* __restrict__ ZSINKSUM, int _for_it_73);

{
  double ZSINKSUM_out_1;
  // Tasklet code (T_l4181_c4181)
  ZSINKSUM_out_1 = 0.0;
  __tmp2[0] = ZSINKSUM_out_1;
}

dace::CopyND<double, 1, false, 1>::template ConstDst<1>::Copy( __tmp2, ZSINKSUM + _for_it_69, 1);
loop_body_6_1_138_7(&ZSOLQA[0], &__tmp1[0], (_for_it_69 + 1));
dace::CopyND<double, 1, false, 1>::template ConstDst<1>::Copy( __tmp1, ZSINKSUM + _for_it_69, 1);

To Reproduce

Download the following SDFG: https://polybox.ethz.ch/index.php/s/YC0ugZL7vG73doz
Apply the greedy_fuse from autoopt.

sdfg = dace.SDFG.from_file('CLOUDSCOUTER_unrolled.sdfg')
greedy_fuse(sdfg, False)
sdfg.simplify(verbose=True)

Look for the state starting with _state_l4191_c4191.

Desktop (please complete the following information):

Python 3.10

@alexnick83 contributed a patch fixing this issue in #1307. Unfortunately, with the new master, it fails during simplification:
Traceback (most recent call last):
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/sdfg/validation.py", line 363, in validate_state
    node.validate(sdfg, state, references, **context)
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/sdfg/nodes.py", line 640, in validate
    raise NameError('Data descriptor "%s" not found in nested SDFG connectors' % dname)
NameError: Data descriptor "NSSOPT" not found in nested SDFG connectors

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/generation_gpu_with_new_master/../dace/tests/fortran/cloudsc/generated_sdfgs_new.py", line 517, in <module>
    generate_all_sdfgs(args.specialize, args.stride_transformation, args.target, args.restart_index)
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/generation_gpu_with_new_master/../dace/tests/fortran/cloudsc/generated_sdfgs_new.py", line 432, in generate_all_sdfgs
    sdfg = simplify_sdfg(sdfg, specialize)
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/generation_gpu_with_new_master/../dace/tests/fortran/cloudsc/generated_sdfgs_new.py", line 143, in simplify_sdfg
    sdfg.simplify(verbose=True)
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/sdfg/sdfg.py", line 2471, in simplify
    return SimplifyPass(validate=validate, validate_all=validate_all, verbose=verbose).apply_pass(self, {})
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/transformation/passes/simplify.py", line 115, in apply_pass
    sdfg.validate()
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/sdfg/sdfg.py", line 2440, in validate
    validate_sdfg(self, references, **context)
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/sdfg/validation.py", line 195, in validate_sdfg
    validate_state(edge.dst, sdfg.node_id(edge.dst), sdfg, symbols, initialized_transients, references,
  File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/sdfg/validation.py", line 369, in validate_state
    raise InvalidSDFGNodeError("Node validation failed: " + str(ex), sdfg, state_id, nid) from ex
dace.sdfg.validation.InvalidSDFGNodeError: Node validation failed: Data descriptor "NSSOPT" not found in nested SDFG connectors (at state stateCLOUDSC, node CLOUDSC)
Originating from source code at File "/users/mcopik/projects/2023/dace_gpu/june_clean_generation/dace/dace/frontend/fortran/fortran_parser.py", line 666

Here's the link to the SDFG on which the simplify fails: https://polybox.ethz.ch/index.php/s/WElGWZyB4lR8Ig3

@BenWeber42 To run the generated_sdfgs.py script, you can downgrade fparser to 0.1.2 or merge changes from the mater - we updated code to the breaking API changes in this library.

Downgrading fparser to 0.1.2 allows me to run the generated_sdfgs.py script which seems the fail the same way. I guess I can reproduce the bug this way:
Traceback (most recent call last):
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/sdfg/validation.py", line 378, in validate_state
    node.validate(sdfg, state, references, **context)
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/sdfg/nodes.py", line 640, in validate
    raise NameError('Data descriptor "%s" not found in nested SDFG connectors' % dname)
NameError: Data descriptor "NSSOPT" not found in nested SDFG connectors

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/data/ben/spcl/repos/dace/new_transform_2/tests/fortran/cloudsc/generated_sdfgs.py", line 500, in <module>
    generate_all_sdfgs(args.specialize, args.stride_transformation, args.target, args.restart_index)
  File "/data/ben/spcl/repos/dace/new_transform_2/tests/fortran/cloudsc/generated_sdfgs.py", line 431, in generate_all_sdfgs
    sdfg = simplify_sdfg(sdfg, specialize)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/ben/spcl/repos/dace/new_transform_2/tests/fortran/cloudsc/generated_sdfgs.py", line 143, in simplify_sdfg
    sdfg.simplify(verbose=True)
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/sdfg/sdfg.py", line 2481, in simplify
    return SimplifyPass(validate=validate, validate_all=validate_all, verbose=verbose).apply_pass(self, {})
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/transformation/passes/simplify.py", line 155, in apply_pass
    sdfg.validate()
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/sdfg/sdfg.py", line 2450, in validate
    validate_sdfg(self, references, **context)
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/sdfg/validation.py", line 195, in validate_sdfg
    validate_state(edge.dst, sdfg.node_id(edge.dst), sdfg, symbols, initialized_transients, references,
  File "/data/ben/spcl/repos/dace/new_transform_2/dace/sdfg/validation.py", line 384, in validate_state
    raise InvalidSDFGNodeError("Node validation failed: " + str(ex), sdfg, state_id, nid) from ex
dace.sdfg.validation.InvalidSDFGNodeError: Node validation failed: Data descriptor "NSSOPT" not found in nested SDFG connectors (at state stateCLOUDSC, node CLOUDSC)
Originating from source code at File "/data/ben/spcl/repos/dace/new_transform_2/dace/frontend/fortran/fortran_parser.py", line 666
Invalid SDFG saved for inspection in /data/ben/spcl/repos/dace/new_transform_2/_dacegraphs/invalid.sdfg

The line numbers don't quite match. But there was a commit since your 2nd comment (73579a7877a7f496e181d6bea87dd1c23bc5bf56) which likely explains the differences.

I looked further into this and I believe the issue occurs earlier. In particular, sdfg validates before this section, but fails validation afterwards (with the same error message):
https://github.com/spcl/dace/blob/73579a7877a7f496e181d6bea87dd1c23bc5bf56/tests/fortran/cloudsc/generated_sdfgs.py#L91-L133

This fixes the validation issue after the specialization step: #1398


fix: submit needs a startTransition so there are no race conditions w/ validation

Codecov Report

Merging #7 (fbe5b79) into main (db48c2b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines          356       359    +3
  Branches        63        63
=========================================
+ Hits           356       359    +3

Impacted Files
Coverage Δ

src/index.tsx
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Enable filtering of location records by institution, campus and library. Fixes UIORG-92.

https://issues.folio.org/browse/UIORG-92

yarn run v1.9.4
$ eslint .
/home/jenkins/workspace/folio-org/ui-organization/PR-139/settings/LocationLocations/LocationManager.js
6:1  error  '@folio/stripes-components' should be listed in the project's dependencies. Run 'npm i -S @folio/stripes-components' to add it  import/no-extraneous-dependencies
✖ 1 problem (1 error, 0 warnings)
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


Title missing for dropdown when rendering double oneOf/allOf

Context
When using oneOf using a schemas that themselves have a allOf Elements uses "any (one of)" as title for the dropdown to select the schema options instead of the schema's title, see the image attached at the current behaviour section.
Current Behavior

Expected Behavior
I would expect the title of the schema would be used instead of "any", for example:

Steps to Reproduce
The following spec should reproduce the problem:
openapi: 3.1.0
info:
  title: Test
  description: Test
  version: "1.0.0"
paths:
  /path:
    post:
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Schema'
        required: true
      responses:
        '200':
          description: OK.
components:
  schemas:
    Schema:
      title: Schema
      type: object
      required:
        - kind
      oneOf:
        - $ref: '#/components/schemas/Kind1'
        - $ref: '#/components/schemas/Kind2'
      discriminator:
        propertyName: kind
        mapping:
          kind1: '#/components/schemas/Kind1'
          kind2: '#/components/schemas/Kind2'
    Kind1:
      title: Kind1
      type: object
      allOf:
        - oneOf:
            - $ref: '#/components/schemas/Kind1Part1'
            - allOf:
                - properties:
                    kind:
                      type: string
                      enum:
                        - kind1
                - $ref: '#/components/schemas/Ref'
        - $ref: '#/components/schemas/Kind1Part2'
    Kind2:
      title: Kind2
      type: object
      allOf:
        - oneOf:
            - $ref: '#/components/schemas/Kind2Part1'
            - allOf:
                - properties:
                    kind:
                      type: string
                      enum:
                        - kind2
                - $ref: '#/components/schemas/Ref'
        - $ref: '#/components/schemas/Kind2Part2'
    Kind1Part1:
      title: Kind1Part1
      type: object
      properties:
        kind:
          type: string
          enum:
            - kind1
        kind1_field1:
          description: Field1
          type: string
    Kind2Part1:
      title: Kind2Part1
      type: object
      properties:
        kind:
          type: string
          enum:
            - kind2
        project_id:
          description: Field 1
          type: string
    Kind1Part2:
      title: Kind1Part2
      type: object
      properties:
        kind1_field2:
          description: Field 2
          type: string
    Kind2Part2:
      title: Kind2Part2
      type: object
      properties:
        kind2_field2:
          description: Field2
          type: string
    Ref:
      title: Ref
      type: object
      properties:
        ref:
          type: string
          format: uuid

Running into this same issue. Any pointers on how this can be fixed?

Running into this issue as well. No solutions.

@Thomasdezeeuw I used the spec you provided to try and reproduce the issue. As of the latest version, it seems like Kind1 and Kind2 are correctly rendering as the title of the objects. I'll leave this issue open for a week so you can confirm the issue is resolved.

@falsaffa looks like it's fixed, thanks!


Mailer replay and template test script

This adds a new entrypoint and corresponding script to c7n_mailer, c7n-mailer-replay, for testing templates. It allows the user to point at a sample SQS message (either the raw base64'ed gzip'ed message from the wire, or plain JSON) in a file, and either print the rendered template that would be emailed, print the full emails that would be sent, or actually send the emails (SES only). This helped us quite a bit when working on our templates.

very cool! we've had a few requests for something along these lines. Would you mind signing our contributor license agreement per the readme, direct link https://docs.google.com/forms/d/19LpBBjykHPox18vrZvBbZUcK6gQTj7qv1O5hCduAZFU/viewform

CLA signed (sorry for the oversight, I read that in the README and then completely forgot... I think this is the first code I've ever contributed that required an actual CLA form) and branch rebased on master.

Also, I haven't really added anything in terms of documentation for this. If you can tell me where the docs should go, I'll give writing them up a try.

for docs on the mailer the tools/c7n_mailer/readme.md is probably the most appropriate place, looks like you've already got a placeholder marked out there. we don't yet have tools docs incorporated into the main docs at the moment.

@kapilt I've pushed a commit with some basic documentation added for the script.

awesome, thanks


How to play multiple files with RtspServerFromFile

I have four mp4 files: record1.mp4, record2.mp4, record3.mp4, record4.mp4
Currently I want to implement it, given a fileList=[record1.mp4,record2.mp4]
Use RtspServerFromFile to ignore the first 15 seconds from record1.mp4 and start the output stream. After record1.mp4 has finished playing, continue to record2.mp4.
How should it be implemented and prepareVideo again?

Hello,
Currently it is not supported. To do that you need stop stream totally and start again with the new video file.
The reason to no support this is because you could use different video/audio file config and in this case you can't handle with that. For example:
If you use 2 files totally different like 1280x720 video with audio 44100 sample rate stereo channel and other file with 640x480 video and audio 32000 mono channel.
You can't continue with the second file because you have the stream and encoders configured for the first file.  I'm not totally sure how to handle this feature so it is not developed for now.
Should I develop the way to do it but only supported files with the same configuration?

For now, you can try join all files in one (you will need find a library for it) and then use the result in the library

I'm sorry, I didn't take into account the problem of different bitrates, but are files with the same bitrate OK?
Your library is great. I used it to record video surveillance for 24 hours and save the file every hour.
The problem we are currently encountering is that multiple video files are pushed to one stream and can only be interrupted and then started again. So I would like to ask if there is any smoother switching method.

For now, you can try join all files in one (you will need find a library for it) and then use the result in the library to stream

This is a good approach, but it consumes storage space.

For now, you can try join all files in one (you will need find a library for it) and then use the result in the library to stream

This is a good approach, but it consumes storage space.

Yes, but this is the only way for now. I will mark this issue as enhancement and develop the way to stream multiples files but only if that files are identical in config (video and audio). The files will require:

Same video resolution, audio samplerate and audio channels

I'm not sure if throw a crash in prepareVideo or prepareAudio if you are using different files with different config or just return false in the method.
What do you think is a better idea?

For now, you can try join all files in one (you will need find a library for it) and then use the result in the library to stream

This is a good approach, but it consumes storage space.

Yes, but this is the only way for now. I will mark this issue as enhancement and develop the way to stream multiples files but only if that files are identical in config (video and audio). The files will require:

Same video resolution, audio samplerate and audio channels

I'm not sure if throw a crash in prepareVideo or prepareAudio if you are using different files with different config or just return false in the method. What do you think is a better idea?
Yes, I think it's a better idea.I can't think of any other better solution. Thanks!

Hello,
This feature was added to RootEncoder in the last commit.
In the next release I will add this feature to RTSP-Server
Usage example:

First of all use the class without loop mode:

genericFromFile.setLoopMode(false)

Use onVideoDecoderFinished or onAudioDecoderFinished callbacks (you need choose one) to detect the end of the file and replace the current file with other file:

  override fun onVideoDecoderFinished() {
    genericFromFile.replaceVideoFile(path)
    genericFromFile.replaceAudioFile(path)
    //resync file to avoid audio and video sync issues (recommended because video or audio could take different time to start)
    genericFromFile.reSyncFile()
  }

Hello,
Thank you very much
I think I need to study the "reSyncFile" method. I am not sure if it will cause video stream lag due to high time consumption when running on low-end devices. Thank you again

reSyncFile is optional but I recommend you use it if you can after change the file.
You can use it only on high-end devices if you want.
Also you can check the time in audio and video and only resync if the difference is high. Something like this:
val vTime = genericFromFile.getVideoTime()
val aTime = genericFromFile.getAudioTime()
if (abs(vTime - aTime) >= 0.5) { //async by 0.5s
genericFromFile.reSyncFile()
}

0.5 is a random value (in seconds), you should check the values and use a value that adjust to you.


Test configs for RHEL 10

The all-customizations config is limited to RHEL 8 and 9 because a lot of the customizations aren't supported on RHEL 7.  Let's also add RHEL 10 to the mix.
We were already testing on CentOS 10, which is basically 90+% the same as RHEL 10, so it wasn't completely untested, but it's still good to cover every distro with this.
This PR also:

Adds RHEL 10 to all generic build config lists.
Adds a RHEL 10 oscap config and enables it for all RHEL 10 versions (rhel-10*) for AMI.

So OSCAP is not yet supported on RHEL-10 and also the EC2 (previously RHUI) images are not yet supported.

So OSCAP is not yet supported on RHEL-10 and also the EC2 (previously RHUI) images are not yet supported.

Some of the profiles haven't been enabled yet afaik. I will have to double-check which are and which arent'


Apache HTTP Server Malformed Range and Range-Request Option Handling Remote Denial of Service Vulnerability

Hello, security vulnerabilities were detected in the deployment of Casdoor, but I cannot find any usage of Apache. Could you please advise me on how to upgrade to fix the vulnerability?

@chjuashduq hi, Casdoor doesn't use Apache HTTP server anywhere in the code (it's open source so you can check it by yourself). So it doesn't make sense for Casdoor to have such problem.
Can you share which software or service provided this security report?

是否是casdoor引用的第三方服务中，引用了Apache Http

@chjuashduq你好，Casdoor 没有在代码中的任何地方使用 Apache HTTP 服务器（它是开源的，所以你可以自己检查）。所以 Casdoor 有这样的问题是没有意义的。
您能否分享提供此安全报告的软件或服务？

@chjuashduq hi, Casdoor doesn't use Apache HTTP server anywhere in the code (it's open source so you can check it by yourself). So it doesn't make sense for Casdoor to have such problem.
Can you share which software or service provided this security report?

Is Apache Http referenced by a dependency in any third-party services referenced by Casdoor?

@chjuashduq

please use English in this community, and modify all your existing texts into English, otherwise this issue may be closed.
Also don't post the same issue for twice.

Apache HTTP server is a standalone service developed by C language.  Casdoor has nothing to do with Apache HTTP server.

@chjuashduq

please use English in this community, and modify all your existing texts into English, otherwise this issue may be closed.
Also don't post the same issue for twice.

Apache HTTP server is a standalone service developed by C language.  Casdoor has nothing to do with Apache HTTP server.
If someone has used Apache HTTP server in their deployment (like using as a reverse proxy) and introduced any problems, this is their own issue, not Casdoor's. Please find those people who deployed the services.

Okay. I'm very sorry. This is my first time using the issue function. I'll pay attention in the future. May I ask what web service container Casdoor uses?


Add AWS SDK Install Feature Gate

Add Feature Gate for AWS SDK Installs

/lgtm
My last comment doesn't stop this merging, but something to think about for the installer implementation


Web Service Functionality

Add the functionality for the web service access to the software.
Analysis & Design

[ ] 1. Determine the request format.

Coding

[ ] 1. Add interface to receive POST requests.
[ ] 2. Define parsing of received commands into variables for use within the software.

Testing

[ ] 1. Test for the proper parsing of the POST requests.

Assigned to: Liji Philip.

Hi. Are you attending the presentation tomorrow
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Trystyn Coté @.>
Sent: Tuesday, March 26, 2024 9:20:45 AM
To: trystyncote/remindmail @.>
Cc: Liji Philip @.>; Assign @.>
Subject: Re: [trystyncote/remindmail] Web Service Functionality (Issue #3)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Assigned #3https://github.com/trystyncote/remindmail/issues/3 to @Lijiphilhttps://github.com/Lijiphil.
—
Reply to this email directly, view it on GitHubhttps://github.com/trystyncote/remindmail/issues/3#event-12252144959, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHE2OHRR3JXRIYT4LDQ3F5DY2GG43AVCNFSM6AAAAABE7VOAZ2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGI2TEMJUGQ4TKOI.
You are receiving this because you were assigned.Message ID: @.***>

@Lijiphil Yes, I will be.

Ok
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Trystyn Coté @.>
Sent: Wednesday, April 17, 2024 11:39:42 AM
To: trystyncote/remindmail @.>
Cc: Liji Philip @.>; Mention @.>
Subject: Re: [trystyncote/remindmail] Web Service Functionality (Issue #3)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@Lijiphilhttps://github.com/Lijiphil Yes, I will be.
—
Reply to this email directly, view it on GitHubhttps://github.com/trystyncote/remindmail/issues/3#issuecomment-2061856344, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHE2OHWWCMDKA3V66KUKWRTY52XV5AVCNFSM6AAAAABE7VOAZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRRHA2TMMZUGQ.
You are receiving this because you were mentioned.Message ID: @.***>


Upgrade to intemediary version

atom has tons of dependency updates, and instead of updating by several versions, I would like to tell dependabot to upgrade to an intermediate version instead.
For example the upgrade here: https://github.com/icecream17/atom/pull/8 (now lost - I deleted and reforked) has 504 commits. I don't feel like debugging huge upgrades. So I want to upgrade to maybe 2.0.0 instead, then go step by step to 2.2.8. Is there a way to do this?

Can you use ignore conditions and the forthcoming #2219 to do something like this (e.g. ignore major/minor and only merge in patch until you want minor, then major)?

The version after 1.0.11 is 2.0.0, a major bump
But upgrading to 2.2.8 is also a major bump
So no, disabling things won't help

This hasn't been a common feature request, it seems most folks can use ignore with major/minor to get a close enough approximation of what they want. So closing for now.


.NET Core support

The Microsoft.Azure.CosmosDB.Table library mentioned here is only available for .NET Framework 4.5 and not available under .NET Core.
It seems like there is an older Microsoft.WindowsAzure.Storage library that is available under .NET Core, as mentioned here: https://docs.microsoft.com/en-us/azure/visual-studio/vs-storage-aspnet5-getting-started-tables
And these pages are only linked to from the old Azure Storage in ASP.NET Core page here: https://docs.microsoft.com/en-us/aspnet/core/data/azure-storage/?view=aspnetcore-2.1
So will the new libraries be updated to .NET Core (I don't see any compatibility issues in the code itself) or do we need to keep using the older libraries? Can this guidance be clearly defined on these pages?

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

ID: a9ca205b-55ab-683a-46ee-afc9f6fc239b
Version Independent ID: 065b8cb0-d218-b759-ce69-e8901d89b422
Content: Get started with Azure Table storage and Azure Cosmos DB Table API using .NET
Content Source: articles/cosmos-db/table-storage-how-to-use-dotnet.md
Service: cosmos-db
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@manigandham Thanks for the feedback. We are actively investigating and will get back to you soon.

We're using both products, which offer the same "Table API" interface to clients.
The issue is that there are 2 different clients, the older WindowsAzure.Storage which supports .NET Core and the newer Microsoft.Azure.CosmosDB.Table which does not support .NET Core. They both have slightly different functions and syntax too, so the samples don't match.
Are these 2 libraries going to be merged or should we continue using the WindowsAzure.Storage library for now since we need .NET Core support?

@manigandham Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@manigandham Adding .Net Core/standard support for Microsoft.Azure.CosmosDB.Table is on our roadmap. And yes you should use `Microsoft.WindowsAzure.Storage' until .Net core, support is enabled for Azure Cosmos DB Table API.

#please-close

@manigandham We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Thanks for the confirmation. In that case, and especially since there 2 clients being used with different code semantics, please update the documentation to make it clear as was originally asked.


How do I change the language of C# error hints?

Environment data
Version:   2.1.403
Commit:    04e15494b6
Среда выполнения:
OS Name:     Windows
OS Version:  10.0.17763
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.1.403\
Host (useful for support):
Version: 2.1.5
Commit:  290303f510
.NET Core SDKs installed:
2.1.403 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
VS Code version:
1.28.0 (user setup)
C# Extension version:
1.16.2
Steps to reproduce
Write code that cause an error hint to appear
Expected  behavior
Error hint language is english
Actual behavior
Since omnisharp 1.16 update (don't know if it is the point) I have error hints in my system's language (Russian). But my VSCode locale is English. Where I can set error hints' language back to english? I don't have any localization language packs for .Net in the system.

@luvjungle See workaround steps in https://github.com/OmniSharp/omnisharp-vscode/issues/2513


Better/Cooler Cloud Particles

CloudParticle's implementation is awkward:

Why is it still related to events?
Why is its setup so restrictive?

The following changes address said issues.
Also, I reimplemented the Player's use of cloud particles when jumping to look cooler (IMO) and added impact particles when colliding with the top of a collider.

Note that, at the moment, this PR assumes PR #45 was merged...


[APK Agent Operator] APK operator api controller and httproute controller implemented

Purpose
Added basic controller functionality for API CR and HttpRoute CR. API creation and updating are supported.
Intermediate representation
type APIState struct {
	APIDefinition *v1alpha1.API
	ProdHTTPRoute *gwapiv1b1.HTTPRoute
	SandHTTPRoute *gwapiv1b1.HTTPRoute
}

@NomadXD He'll address the review comments in a new PR. So let's merge this.