Read logical maps as go maps in Readany

As reported on #103, logical maps are currently read as the nested repeated structure used for their physical storage. This appears to be due to discarding the logical map in favor of a logical group. Attempting to work around this by providing a schema results in panics, as reported on #40, #57. This change adds a test for and fixes both of those cases. It also masks or fixes a resulting test panic; a deeper review is required for that.

(*columnLoader).open: use mapType instead of groupType when the schema indicates a logical map
reconstructFuncOfMap: handle map types and instantiation correctly when operating on an interface{} value
makeNodeOf: questionable: don't panic for [][]uint8 case assuming it's actually []string

The makeNodeOf change is meant to address the panic in TestReader's map_of_repeated_values case that started with the change to (*columnLoader).open. While I'm fairly confident in the other changes, I'm very shaky here. However all tests passed for me, so I've included it as a potential fix.
There may be compatibility concerns here. This change alters visible behavior change for the described scenario, as Read[any] will now return a map {k: v, ...} equivalent to the one written, instead of the surprising, thus arguably buggy, {"key_value": []{{"key": k, "value": v}, ...}}.

Do I need to take further steps to verify the CI fix, or otherwise secure further review?


Failed to build latest wasi-sdk from source

Since wasi-sdk is only released officially for amd64, we need builds for other machine types such as aarch64.  Pulling all of its history can take
# way too long, and we are not interested in it, after all.
# --force and --remote are required to avoid the following error from git:
# "error: Server does not allow request for unadvertised object"
RUN git submodule update --init --recursive --depth 1 --force --remote
RUN make package
FROM scratch
COPY --from=base /home/wasisdk/wasi-sdk/dist/ /opt/wasi-sdk/

However, after a couple of hours building the project, libc++abi.so fails to build:
 > [base 8/8] RUN make package:
7860.3 [1040/1141] Building CXX object libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_demangle.cpp.o
7860.3 [1041/1141] Linking CXX shared library lib/libc++abi.so
7860.3 FAILED: lib/libc++abi.so
7860.3 : && /home/wasisdk/wasi-sdk/build/install/opt/wasi-sdk/bin/clang++ --target=wasm32-wasi --sysroot=/home/wasisdk/wasi-sdk/build/install/opt/wasi-sdk/share/wasi-sysroot -fPIC -fdebug-prefix-map=/home/wasisdk/wasi-sdk=wasisdk://v21.4ga1b80857c490+m  --target=wasm32-wasi-preview2 -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections  -Wl,-z,defs -Wl,--color-diagnostics  -nostdlib++ --unwindlib=none -shared  -o lib/libc++abi.so libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_aux_runtime.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_default_handlers.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_demangle.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_exception_storage.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_guard.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_handlers.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_vector.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_virtual.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_exception.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_stdexcept.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_typeinfo.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/abort_message.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/fallback_malloc.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/private_typeinfo.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/stdlib_new_delete.cpp.o libcxxabi/src/CMakeFiles/cxxabi_shared_objects.dir/cxa_noexception.cpp.o  -lc  -lunwind_shared  -lc && :
7860.3 wasm-ld: warning: unknown -z value: defs
7860.3 wasm-ld: error: unable to find library -lunwind_shared
7860.3 clang++: error: linker command failed with exit code 1 (use -v to see invocation)
7860.3 [1042/1141] Building CXX object libcxxabi/src/CMakeFiles/cxxabi_static_objects.dir/fallback_malloc.cpp.o
7860.3 [1043/1141] Building CXX object libcxxabi/src/CMakeFiles/cxxabi_static_objects.dir/cxa_demangle.cpp.o
7860.3 ninja: build stopped: subcommand failed.

I am unsure whether the error above is related to the Docker image configuration, such as a missing dependency. Building LLVM from source takes a long while, so unfortunately a trial-and-error process to find out the root issue is very time-costly.
Do you know why this issue occurs, and how it could be solved?

our ci builds and pushes docker images for arm64. https://github.com/WebAssembly/wasi-sdk/blob/a1b80857c4904d43e3823afd07480f64e62fab6d/.github/workflows/main.yml#L188
i guess you can follow/use it.

RUN git submodule update --init --recursive --depth 1 --force --remote

i suppose this checks out wrong versions.

i suppose this checks out wrong versions.

Could you please explain why? I see the CI workflow uses --depth 32 to avoid the "error: Server does not allow request for unadvertised object" condition, but this could be apparently solved with --force --remote as well. Do you think this is the wrong approach?

it's just my reading of documentation of --remote in git submodule --help

@midokura-xavi92 do you still think this is a problem in wasi-sdk? if so, can you explain? otherwise, can you close?


Allow external dependencies

Resolves https://github.com/python/typeshed/issues/5768 (on stub_uploader side)
In https://github.com/python/typeshed/issues/5768#issuecomment-1251375258 consensus was seemingly reached on Akuli's idea, that external dependencies for stub packages are fine, as long as we validate that the external dependency is a dependency of the upstream package.
The most important part of the implementation is the validation we perform. This happens in verify_typeshed_req and verify_external_req. To help lock things down, Metadata does not expose access to elements of requires without validation.
We rely on PyPI's API to find the dependencies of the upstream. I believe this might not work if our stub has external dependencies and the upstream does not publish wheels. This is not the case currently (as proven by test), does not seem too likely, and it's unclear how to do safely, so will leave as a TODO for the future.
We use uploaded_packages.txt as the source of truth for what is a typeshed dependency. This is important to avoid potential badness around addition and deletion, for instance, if something is added to typeshed, but the distribution is created by someone else before stub_uploader uploads it.
The other set of changes is that I delete most of the graph code that existed previously. The graph code was added in
https://github.com/typeshed-internal/stub_uploader/pull/1 and was previously load bearing for security. The idea being to ensure that the graph of transitive dependencies was fully contained within typeshed. This is no longer the case, so we can remove most of it.
I still have some graph code in here, but it's no longer load bearing for security. I keep it around to better preserve uploading semantics, since it seems like it could matter in some edge case scenarios (such as multiple packages being uploaded for the first time that depend on each other). Since we don't have custom needs, we can get away with using the new-ish graphlib from stdlib.
While the graph code has been removed, note that we do still run validation on transitive dependencies for each package. This is accomplished by recursive_verify. (I think the non-transitive validation is probably sufficient, but running this before uploading each package can't hurt)
I added some special-casing for types-gdb. As Akuli pointed out, this avoids us accidentally trusting a gdb package on PyPI if ever someone attempts to add external dependencies to types-gdb.
New code paths have tests. I audited test coverage to make sure of this.

Bump :-)

@hauntsaninja Hm, it looks like one of added tests is broken on master, could you please check?


feat(observability): Automatically update k8s vector container versions

Update the vector mainnet and testnet container versions in the k8s repo, when the DRE repo version changes.

It looks good, but if we are going this route, maybe we should also add the bases/apps/service-discovery?

Sounds good, let's do that!


Add Graticule rendering test

New test (picked from #14714) as the existing tests did not prevent #15076/#15077 confusing the view projection world extent with the graticule projection (EPSG:4326) extent (both use degrees but are otherwise unrelated) and breaking graticule rendering in the Reprojection with EPSG.io Search example while still passing all existing tests.

What about a rendering test for a case that is not broken? If I look at the reference image you added, I feel like the graticule should continue beyond 60°W, no?

If the right side meridian label was in view it would be 65° 41' 24" W as defined by the view projection world extent (based on the EPSG.io bbox for the projection in the example).  But that would need more than a 256 x 256 rendering test:

It should not attempt to draw beyond that, which happened with #15076 when any of the suggested local projections were used in the example.

Thanks for the explanation, @mike-000


Tides should only affect oceans

Fixing this requires either a) removing tides completely or b) delineating areas as ocean.

Tides have been removed.


Ensure scope has no duplicates

Make sure scope list only has unique elements.

Change  OAuthOptions to use Hashset for Scope list
Change OpenIDConnectOptions to use HashSet for scope list
Change OpenIDConnectOptions  to new options pattern for scope defaults

No known APIs break with duplicate scope values.
However Facebook breaks for duplicate field values so it seems a good idea to guard against duplicate scope values as well  using the same methodology.
It is quite possible that a future API may not be so accommodating of duplicate values.
PS I cant get tests running but tested used social sample and OpenIDConnect sample (Google authority)

Hi @mikes-gh, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


Adalight output device on Windows

Hi,
I have asked this question before.
On the windows version of hyperion.ng what do you have to set the output device to in order for usb led devices like adalight to work. I have tried so many things with tty and comm ports but it's just not recognizing it.
Last time you said I should ask on the forums but I can't post on the forums for some reason. Also, you are the developers so who better to ask than you.

Thank you

@Rickexe

I have tried so many things

You might want to share what you tried, which debug output (logs) you have seen and what what environment you have tried running with.
The template tries guiding you providing the information we seem to be relevant getting in a position better addressing your question. Please bear in mind that not everybody has every device on our end and devices too often have some specific challenges, plus Windows is a quite new development.
So putting yourself in our shoes might help in understanding that the more information one share the higher the opportunity is getting things clarified and resolved (plus following some netiquette makes in general things running more smoothly).


New html formatter produces very large report files

The new html formatter produces very large report files. Please consider reducing the size or providing the old html formatter as an option to switch back to for 6.x.x
We have been using cucumber 4 for a number of years and recently made the changes to first upgrade to 5.7.0 and then on to 6.8.1. Our tests are running fine and although the new html formatter is much easier to read and use for debugging of test failures for our build (which currently runs 423 scenarios that invoke selenium for ui testing).
Our 423 scenarios produce an html report file of 314MB which when we are storing this test artifact uses up a lot of space fast.

Hi @ben-nc2 - we're aware that the large size can be a problem.
How big were your HTML reports prior to upgrading to v6?
Screenshot sizes should be identical between v5 and v6, so the increase in size might come from elsewhere. I think it might have to do with the large number of duplicated stepDefinition messages on Cucumber-JVM, as well as the inclusion of more JavaScript.
Some things we can try to minimize the size:
More space-efficient message format
Some options:

Use binary representation and use a more compact protobuf library
Keep using NDJSON, but don't include messages.js + the protobuf library in the bundle
Use msgpack

More space efficient JavaScript

Tree shaking
Minification

Fewer messages

Cucumber-JVM outputs all the step definition messages once for every single scenario. It only needs to be outputted once.

@aslakhellesoy running with 5.7.0 html reports were 7MB in size where all tests have passed. The same tests running with 6.8.1 create html reports of 310MB in size. If it would be helpful to share both I can check with my employers if the information is sensitive or not.

Hi @ben-nc2 having some example reports would be very helpful! If you're allowed to share, you can email them to aslak hellesoy smartbear com (add dots and @)

I hope the example reports I emailed help you find ways to reduce the overall size of the report files.
I'm very willing to test any alpha/beta releases against the same scenarios to provide a direct comparison if that is at all helpful.

I can think of a few options:
a. Fix Cucumber JVM to only emit step definition once.
b. Externalize attachments when creating the html report
c. Use a different encoding then Base64 to reduce the overhead and make zipping more efficient
d. Filter out messages that are not used by the html report.
None of these are ideal.
a. Is a significant amount of work.
b. Removes the SPA nature.
c. Assumes the attachments are the problem
However after running a suite of ~550 scenarios without any screenshots:
$ ls -l --block-size=M cucumber.ndjson
142M nov  5 22:48 cucumber.ndjson
$ cat cucumber.ndjson | cut -d \" -f 2 | sort | uniq -c
   8934 attachment
    112 gherkinDocument
  10584 hook
      1 meta
    469 pickle
    112 source
 380583 stepDefinition
    441 testCase
    441 testCaseFinished
    441 testCaseStarted
      1 testRunFinished
      1 testRunStarted
  11399 testStepFinished
  11399 testStepStarted
$ sed '/${"stepDefinition/d' cucumber.ndjson > stripped.ndjson
$ ls -l --block-size=M stripped.ndjson
-rw-rw-r-- 1 mpkorstanje mpkorstanje  15M nov  5 22:31 stripped.ndjson

So originally the file was 142M and after removing stepDefinition messages only 15M remains. So that removes about 90%. So the attachments
While d. requires that the MessagesToHtmlWriter knows the implementation details of cucumber/react it would be a pretty significant optimization overall at this point in time. If the html report does use the step definitions in the future then we have the same problem back.
@aslakhellesoy for the short term could do something like https://github.com/cucumber/cucumber/pull/1236. And it would be even better if react could output a list of messages it consumes because then the filter could be generated in all implementations.

@ben-nc2 if you don't mind building snapshots you could add the following to the HtmlFormatter in cucumber-jvm.
    private void write(Envelope event) {
        if (event.hasStepDefinition() || event.hasHook()) {
            return;
        }

a. Is a significant amount of work.

Why do you think it's a significant amount of work @mpkorstanje?
I think I understand why we need a new instance of each step definition for each scenario. Can't we emit step definition messages once without changing that?

@ben-nc2 if you don't mind building snapshots you could add the following to the HtmlFormatter in cucumber-jvm.
    private void write(Envelope event) {
        if (event.hasStepDefinition() || event.hasHook()) {
            return;
        }

I see you have proposed this over in #1236 - I think we should fix this differently.

Fixing this in Cucumber JVM is a problem because the glue is currently not immutable. So there must be a distinct set for each runner/thread.
Additionally because parameter types influence the the regexs in the glue, and because Cucumber JVM supports scenario scoped glue we are forced to use a parameter type registry per scenario. This in turn means we generate and new set of regexs for each scenario. And thus emit a new set of step definitions.
Because each step definition has a unique identifier all must be emitted. Otherwise it's not possible to link back.
Fixing this is possible but it requires a redesign of how glue is discovered and shared between threads.
Once that is in place it should be fairly easy to determine if a step definition can be reused or not.

I, for one, like the new test summary output at the top of the formatted html output so please keep that.  Anyone know how to get pretty_inspect method to print output to the html file.  That is no longer working and instead prints a #.

Cucumber JVM 6.9.0 has been released and will be available in Maven Central soonish. This includes a workaround to reduce the size of the html report.

Thanks guys, have got it running locally and it does make a sizeable difference in our reports.

Our current HTML reports are around 10MB, but they mostly contain ignored tests, since we execute every Cucumber test separately (so we can parallelise them easier on our build servers). This results in 100s of 10MB files, with mostly ignored information.
Is there a way to not have these ignored tests in the HTML output, so we can make these reports significantly smaller?


Fix docker tag in README example

The 2 tag doesn't exist, it's v2.0.0

Sorry, there was a mistake in the setup on docker hub! I've fixed the regexes and there is now a 2 tag: https://hub.docker.com/r/thomseddon/traefik-forward-auth/tags


[SP-5445] Backport of PDI-18630 - VFS Process files Copy operation fa…

…ils sporadically fails with "Unable to get VFS File object for filename" (9.0 Suite)

:white_check_mark: Build finished in 21m 20s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4747, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Correct markup in javadoc for unbalanced braces

Use <code>{</code> instead of {@code {}, as the latter one is
invalid. It works in the current javadoc, as it is accompanied
with the equally invalid closing statement {@code }}, which
balances the used braces in the {@code ...} fragments and combines
the first invalid statement with the last one.

Coverage remained the same at 95.016% when pulling 40c873aac47d1a071156ff3b6025d7f3518b7e3c on FSchumacher:javadoc-markup into d704c0dc70a2f861c043785822854b4a0605ac6b on apache:master.


Create Modal pop-up HTML code

use HTML to create the pop-up box that requests user input for favourite artist.
Modal should include:

text that says something like 'Want to know what kind of Pokémon you'd be based on your favourite artist?'
a label for the input field
an input field
a submit button eg 'Go!'

Done in pull request #73


Rate limiting for scheduling

Scheduling is the first operation we should start to rate-limit, as it is most expensive. Foremost, this protects against bad/rogue client implementations.
My suggestion (taking into account the state before Project 6 is implemented:

Make a new field on GenericAssets: max-actuation-rate (a timedelta). How often we allow someone to re-compute things for their asset is a business decision I believe, so this is where it belongs.
Update the postUdiEvent endpoint, so it checks when the last scheduling job happened and if it was too recently, it does not make a new one, or it schedules one into the future (in this option we also need to check if in the future a scheduling job already exists).
When Project 6 is implemented, we have moved schedulers to actuators, but most of this logic should still be usable.

Curious to hear @Flix6x thoughts.

I like it. I think this parameter would also be suited for being coupled to the organisation account instead: for example, a "plan" JSON column for Accounts similar to our "attributes" JSON column for GenericAssets.

I agree that this has consequences for the "plan" of customers, as pricing could be derived from this (among other things).
Why a JSON column?
Also, they might want to rate Assets differently within their account.

Why a JSON column?

A max_actuator_frequency field feels like it would be part of a blob of attributes assigned to something.

they might want to rate Assets differently within their account.

True. I'd start with implementing the default value on the Account plan, and we could consider whether it makes sense to write plan searching logic like we have attribute searching logic on the Sensor class, which first checks whether the attribute exists on the Sensor, and if it doesn't, looks for the attribute on the GenericAsset. Similarly, we could elevate a plan attribute search on the GenericAsset to a plan attribute search on the Account.

A max_actuator_frequency field feels like it would be part of a blob of attributes assigned to something.

Well, in relational databases, we'd usually make a table called "plan", with a foreign key to Account, and store plan details there. That's what I'd recommend.


[Bug]: Stops working when used in chat textarea

What happened?
Hi, first of all thank you for this plugin!
I may be using it as not intended, but I'm attaching it to a chat textarea. It works perfectly, the emoji is inserted into the textarea. However, if you click the 'open popup' button a second time the console displays this error:

Any idea what could be causing it?
How to reproduce the bug
See above
Package Version
latest
PHP Version
8.3
Laravel Version
11
Which operating systems does with happen with?
macOS
Notes
No response

Hi! Thanks for reporting the issue, can you please provide the code that you use to initialize the textarea with the emoji picker? Thanks!

I had the same issue. This is my sample code.
                    Forms\Components\Textarea::make('message')
                        ->hintAction(EmojiPickerAction::make('emoji-messagge'))
                        ->label('Text Message')
                        ->columnSpanFull()
                        ->rows(8),

@manugando It works. Thank you so much

@gavinhewitt could you try to update to the latest version (1.0.3) to see if your issue is solved too? Thanks!

@gavinhewitt could you try to update to the latest version (1.0.3) to see if your issue is solved too? Thanks!

Thank you so much! I'm on holiday with a really sucky connection :( I'll report back when I have better access!

@manugando Thank you, works!

@manugando Thank you, works!


A cause of "CUDA out of memory" problem

I have met RuntimeError: CUDA out of memory.   problem. And I found solution in  GPU is not utilized while occur RuntimeError: cuda runtime error: out of memory at.

albanD said:
Hi,
Tensorflow has the bad habbit of taking all the memory on the device and prevent anything from happening on it as anything will OOM.
There was a small bug in pytorch that was initializing the cuda runtime on device 0 when printing that has been fixed.
A simple workaround is to use CUDA_VISIBLE_DEVICES=2. This will hide all devices but the one you specify and will make sure you never use other devices.

Dear @whxf
Please take a look on the newest code.
I try to reduce as many the contiguous operations as possible with broadcasting.
Hope it helps.


Support ...attributes on elements in a components template

<div ...attributes></div>

Fixed by https://github.com/rwjblue/ember-angle-bracket-invocation-polyfill/pull/9


Why do I have this error in Chrome DevTools's Manifest tab?

Why do I have this error in Chrome DevTools's Manifest tab?

Richer PWA Install UI won't be available on desktop. Please add at least one screenshot with the form_factor set to wide.

Richer PWA Install UI won't be available on mobile. Please add at least one screenshot for which form_factor is not set or set to value other than wide.

Can I generate these screenshow with pwa-asset-generator too?

You need to take screenshots of your app and add them to your manifest. PAG does not take screenshots of your app, and realistically can never do that because only you know which parts of the app you want to showcase. You can read more about the feature here: https://developer.chrome.com/blog/richer-pwa-installation/

Leaving this open because it might make sense for PAG to let the developer link to screenshots that should be included in the manifest.


Find a better way to get the CC jar

Kind of annoying how the CC jar URL pattern changes with each version, would be nice to find a universal alternative

regex

You could trawl this page and look for a download link of a specific file. The download link should redirect to the Jar. I have some sample trawling code for a website I wrote a while back.

the page's contents could change, though. i was thinking of making a centralized service ccdownload.info which serves the link to the latest cc jar (not redistribution) and also supports version e.g. ccdownload.info/1.60

on second thought - curseforge has an api - you could use that instead of trawling the page.

I've been looking at the curseforge API but there isn't one that lists files for projects - at least, not one that I can find.

curseforge also has an api, however it doesn't document anytgin

my rbowser just died

insteasd of a centralized service, howabout a github repo with a latest file and a file for each version?

There seems to be an API endpoint for files https://minecraft.curseforge.com/api/projects/67504/files?token=<your token> but it always gives me this error {"errorCode":1100,"errorMessage":"You do not have permission to access this method."}

Hopefully when (or if...) CC eventually goes open source there will be a maven repository containing it. For now I'm closing this.


[ENH] add version to cli

Closes #318
Closes #309

Changes proposed in this pull request:

remove warning in doc build by ignoring version and cli modules from the doc build
add a --version action to the CLI
add version to doc

Checklist (for reviewers)
This section is for the PR reviewer

[x] PR has an interpretable title with a prefix (e.g. [BUG], [DOC], [ENH], [MAINT])
Refer to NumPy Development Guide for a full list
[x] PR links to GitHub issue with mention Closes #XXXX
[x] Tests pass
[ ] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions

@Remi-Gau do you have an idea why there are now 2 Read the Docs checks (one of them is never running)?

Yup I tested something on read the docs.
But already nuked the project.

Looks good to me overall, but maybe add a test to nipoppy_cli/tests/test_parser.py?

done


Following upgrade to latest verions, no longer have access to table data.

Preflight Checklist

[x] I have installed the latest version of Storage Explorer.
[x] I have checked existing resources, including the troubleshooting guide and the release notes.
[x] I have searched for similar issues.

Storage Explorer Version
1.36.0
Regression From
I didn't record what version was installed
Architecture
x64
Storage Explorer Build Number
No response
Platform
All
OS Version
No response
Bug Description
Unable to retrieve child resources
ProducerError:{
"name": "Electron Net Error",
"message": "net::ERR_NAME_NOT_RESOLVED",
"stack": "Error: net::ERR_NAME_NOT_RESOLVED\n    at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:115482)\n    at SimpleURLLoaderWrapper.emit (node:events:519:28)",
"cause": {}
}
Steps to Reproduce
Re-start Microsoft Azure Storage Exporter
Actual Experience
When I start MASE I can't access tables view.
Unable to retrieve child resources
ProducerError:{
"name": "Electron Net Error",
"message": "net::ERR_NAME_NOT_RESOLVED",
"stack": "Error: net::ERR_NAME_NOT_RESOLVED\n    at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:115482)\n    at SimpleURLLoaderWrapper.emit (node:events:519:28)",
"cause": {}
}
Expected Experience
No response
Additional Context
No response

I am getting the same problem, why is this closed, how was this resolved?
Thank you


Update macOS to 15

macOS 15.x in the GitHub Actions page is marked as AMD64 supported which means we don't need to freeze to 13.x permanently. windows-2025 on other hand is not available yet as the devs are currently working on it.

Closing this as i got it wrong, the AMD64 macos 15 is exclusive to azure devops. :tinfoilhat:


apis: add allocateOnce in reservation

Signed-off-by: saintube<EMAIL_ADDRESS>Ⅰ. Describe what this PR does

Update with allocateOnce API in Reservation.
Ⅱ. Does this pull request fix one issue?

#440
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[X] I have written necessary docs and comments
[X] I have added necessary unit tests and integration tests
[X] All checks passed in make test

/assign @eahydra @hormes @jasonliu747 @buptcozy

/approve


Feature - overlay file revisions and max filesize

Added configuration parameters and implementation for

the maximum filesize per file to copy to the overlay directory
running counter as revision number for already existing files in the overlay directory

Nice!


"Error reading bindings.json: invalid character 'x' in string escape code"

Description of the problem or steps to reproduce
Following the custom keybind docs page, I'm trying to bind Ctrl-/ to Undo to replicate the default emacs setup. I used the "raw" command to see what micro thought this key sequence was, and got
EventKey: Ctrl-_: "\x1f"
So in my bindings.json I added
"\x1f": "Undo",
But when I relaunched micro, I got this error:
Error reading bindings.json: invalid character 'x' in string escape code
Is there any way I can bind something to Ctrl /?
Specifications
Commit hash: 5044ccf6 (2.0.7)
OS: Manjaro Linux
Terminal: Gnome Terminal

Just in case, does this work?
"\\x1f": "Undo",
I don't think it will, but we never know…

You can bind Ctrl-/ by using CtrlUnderscore.


feat: update to ember 3.22

closes #522

Seems github actions got stuck because the workflow file was updated

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CMake FetchContent fails when called before idf_component_register (IDFGH-8469)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
ESP-IDF v5.1-dev-992-gaf28c1fa21
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
No response
What is the expected behavior?
For some reason using the CMake FetchContent module before registering a component fails spectacularly.
include(FetchContent)
FetchContent_Declare(...)

file(GLOB_RECURSE SOURCES *.c *.cpp)
idf_component_register(SRCS  ${SOURCES} ...)

What is the actual behavior?
CMake errors out. See "Build or installation Logs." for further details.
Steps to reproduce.
1.) Create new project from hello_world example
2.) Copy/paste any FetchContent_Declare call before idf_component_register, e.g:
      include(FetchContent)
      FetchContent_Declare(
        fmt
        GIT_REPOSITORY https://github.com/fmtlib/fmt.git
        GIT_TAG 9.1.0
        GIT_PROGRESS TRUE)
      FetchContent_MakeAvailable(fmt)

Build or installation Logs.
CMake Error at /home/vinci/esp/esp-idf/tools/cmake/component.cmake:224 (message):
  CMake Warning (dev) at build_properties.temp.cmake:8:

    Syntax Warning in cmake code at column 47

    Argument not separated from preceding token by whitespace.

  Call Stack (most recent call first):

    /home/vinci/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:3 (include)

  This warning is for project developers.  Use -Wno-dev to suppress it.

  fatal: not a git repository (or any parent up to mount point /)

  Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

  CMake Error at /usr/share/cmake/Modules/FetchContent.cmake:1149
  (define_property):

    define_property command is not scriptable

  Call Stack (most recent call first):

    /usr/share/cmake/Modules/FetchContent.cmake:1300:EVAL:1 (__FetchContent_declareDetails)
    /usr/share/cmake/Modules/FetchContent.cmake:1300 (cmake_language)
    /home/vinci/Develop/VSCode/hello_world/main/CMakeLists.txt:2 (FetchContent_Declare)
    /home/vinci/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:106 (include)
    /home/vinci/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:124 (__component_get_requirements)

More Information.
No response

Thank you for the detailed explanation. Unfortunately, this only confirms my assumption that ESP-IDF is generally working against CMake and not with it. The reason people use CMake in the first place is because everybody else does so. "CMake has a beautiful syntax and is a pleasure to work with" is a sentence nobody ever has nor ever will say... By introducing the concept of components ESP-IDF basically take the one and only thing away from CMake it excels at. Maybe I'm missing something, but currently I really can't see the point of it all?

Adding the component with FetchContent would be my preferred way yes. When and where do I append the path to EXTRA_COMPONENT_DIRS though? If I wrap the FetchContent calls in an "CMAKE_BUILD_EARLY_EXPANSION"-if the folder doesn't seem to exist the first time when CMake is executed in script mode.

(The thing I explained above regarding CMAKE_BUILD_EARLY_EXPANSION applies to component CMakeLists.txt files only, so in the project you don't have to deal with that.)

Ok, this finally makes this issue an actual bug. :smile:
For some reason I don't understand yet this only seems to work with the example you've just posted. Maybe because it contains an actual "component"?
Trying to add any other repository (let's stick with the fmt example)
cmake_minimum_required(VERSION 3.16)

# use FetchContent to download esp-protocols repository
include(FetchContent)
FetchContent_Declare(
  fmt
  GIT_REPOSITORY https://github.com/fmtlib/fmt.git
  GIT_TAG 9.1.0
  GIT_PROGRESS TRUE)
FetchContent_MakeAvailable(fmt)

include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(hello_world)

results in another CMake error
CMake Error at /home/vinci/esp/esp-idf/components/xtensa/project_include.cmake:3 (message):
  Internal error, toolchain has not been set correctly by project (or an
  invalid CMakeCache.txt file has been generated somehow)
Call Stack (most recent call first):
  /home/vinci/esp/esp-idf/tools/cmake/build.cmake:398 (include)
  /home/vinci/esp/esp-idf/tools/cmake/build.cmake:617 (__build_process_project_includes)
  /home/vinci/esp/esp-idf/tools/cmake/project.cmake:440 (idf_build_process)
  CMakeLists.txt:15 (project)

Hence my question before where I should had put the set(EXTRA_COMPONENT_DIRS...). I simply was expecting for calls to FetchContent to fail in this place as well.

Once again, thank you for the crystal clear explanation. I was just about to write something along the lines of "I'm going to stick with the component manager"... and then some things about how everything else feels like a workaround and calls to FetchContent/MakeAvailable are outright dangerous because you never know what the CMakeLists.txt file of the project your fetching actually does... if it even has one at all.
The "idf_as_lib" example also doesn't particularly appeal to me to be honest although I see the use cases of course. Funnily enough I was even one of the first contributes to LVGLs CMake compatibility, but I simply passed whatever there already was on to some "ESP-IDF" CMake function or file or so. :stuck_out_tongue_closed_eyes:
The solution I now found for me is to simply invoke CMake directly. That way I can control whatever toolchain file gets picked and I don't need to worry about CMake running in script mode or anything. Also I don't loose any of the IDF tool benefits like 'idf.py monitor' or such.
Oh and btw, the path in the esp-protocols example you've posted earlier (this one)
${CMAKE_CURRENT_BINARY_DIR}/_deps/esp-protocols-src/components/mdns
could be written as
${esp-protocols_SOURCE_DIR}/components/mdns
Thanks again for all your help! Really appreciate it.

I'm sure you know this, but for others who might stumble on this ticket I'll note that it is still possible to write a library which works with normal CMake and IDF (and Zephyr) at the same time. LVGL is one such example: https://github.com/lvgl/lvgl/blob/master/CMakeLists.txt

I'm currently failing miserably to write even the simplest component so I though I should take a look at LVGL. Turns out LVGL isn't working either.
I even tried adding it to the component manager
dependencies:
  idf: ">=5.0"
  espressif/esp_tinyusb: ">=1.0.2"
  espressif/mdns: ">=1.0.7"
  lvgl:
    path: lvgl
    git: https://github.com/lvgl/lvgl.git

Which results in a huge Python traceback...
Traceback (most recent call last):

    File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
      return _run_code(code, main_globals, None,
    File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
      exec(code, run_globals)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/prepare_components/__main__.py", line 6, in <module>
      main()
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/prepare_components/prepare.py", line 124, in main
      args.func(args)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/prepare_components/prepare.py", line 27, in prepare_dep_dirs
      ComponentManager(
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/core.py", line 62, in wrapper
      return func(self, *args, **kwargs)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/core.py", line 438, in prepare_dep_dirs
      downloaded_component_paths, downloaded_component_version_dict = download_project_dependencies(
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/dependencies.py", line 111, in download_project_dependencies
      solution = solver.solve()
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/version_solver/version_solver.py", line 34, in solve
      self.solve_manifest(manifest)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/version_solver/version_solver.py", line 53, in solve_manifest
      self.solve_component(requirement)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_manager/version_solver/version_solver.py", line 56, in solve_component
      cmp_with_versions = requirement.source.versions(
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_tools/sources/git.py", line 136, in versions
      commit_id = self._checkout_git_source(version, temp_dir, selected_paths=[self.component_path])
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_tools/sources/git.py", line 52, in _checkout_git_source
      return self._client.prepare_ref(
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_tools/git_client.py", line 41, in wrapper
      return func(self, *args, **kwargs)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_tools/git_client.py", line 72, in wrapper
      return func(self, *args, **kwargs)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_tools/git_client.py", line 133, in prepare_ref
      self.run(checkout_command)
    File "/home/vinci/.espressif/python_env/idf5.1_py3.10_env/lib/python3.10/site-packages/idf_component_tools/git_client.py", line 183, in run
      raise GitCommandError(

  idf_component_tools.git_client.GitCommandError: 'git --work-tree
  /tmp/tmp_xia4uwq --git-dir
  /home/vinci/.cache/Espressif/ComponentManager/b_git_023cb0a1 checkout
  --force 162e451396cfe974786a58d3738af745a29f5979 -- lvgl' failed with exit
  code 1

  error: pathspec 'lvgl' did not match any file(s) known to git

I'm sorry but this is really starting to piss me off. How the f* are people using ESPs in the real world? My best guess is that everyone is copy pasting source files like back in 1980...

The reason for this failure is that there is no subdirectory lvgl (which you have specified in path) in https://github.com/lvgl/lvgl.git
You can add lvgl like this: https://github.com/espressif/esp-bsp/blob/f9a521aaf96722e4ea0bf43794eaebf80388f5e4/esp32_s3_usb_otg/idf_component.yml#L11

I see, that's what path does. Thank you for clearing that up.
The component manager still needs a lot of documentation work, but it seems it's well on its way (https://github.com/espressif/idf-component-manager/pull/17)

No problem, I do agree with you it looks very frustrating when it fails like that!
Component manager documentation improvements are underway and we'll add a better message for this type of error.
If you are looking into LVGL, I may suggest also esp_lvgl_port component which includes an implementation of LVGL port layer on top of ESP-LCD. In example of its usage can be seen in this esp-box component: https://github.com/espressif/esp-bsp/blob/master/esp-box/esp-box.c.

By there way, there is now a sample of using CMake FetchContent inside an IDF component:
https://github.com/erhankur/esp32-spdlog/blob/08e076789e46572cc4f8219cbea6d07ada914bd4/components/spdlog/CMakeLists.txt#L15

I'd like to add my sentiment about the arcane way IDF has been integrated in with cmake.
It would have been easy enough to add a set of Kconfig functions to tie a cmake add_custom_target() or an add_custom_command() to a native cmake target rather than an idf_component.  All of the custom targets would then depend on a single sdkconfig file which when changed will regenerate everything necessary.
The other option would be to add them in as CMake Native Cached variables and options for each component.  The CMakeLists.txt in each of the directories would then be able to contain ALL of the configuration (Kconfig) and all of the definition of the module, and tie the defines to the native cmake targets An example for esp_idf/components/log would be:
# Configuration

# Add Config documentation here.
# Note with this you don't need the independent LOG_DEFAULT_LEVEL_<NONE|ERROR|WARN|INFO...> or LOG_MAXIMUM_LEVEL_<*>

set(LOG_DEFAULT_VALUE 3 CACHE STRING "Default log verbosity 0=none 1=error 2=warn 3=info 4=debug 5=verbose")
set(LOG_MAXIMUM_VALUE 3 CACHE STRING "Maximum log verbosity 0=none 1=error 2=warn 3=info 4=debug 5=verbose")
set(LOG_COLORS ON CACHE BOOL "Use ANSI terminal colors in log output")
set(LOG_TIMESTAMP_SOURCE 0 CACHE STRING "Log Timestamp 0=rtos 1=system")

add_library(log STATIC)
add_library(idf::log ALIAS log)

target_sources(log
    PRIVATE
       include/esp_log_internal.h
       include/esp_log.h
       esp_log_private.h
       log_buffers.c
       $<IF:$<STREQUAL:${IDF_TARGET},linux>, log_linux.c, log_freertos.c>
       # $ENV{IDF_PATH}/components/log/log_noos.c - for bootloader but leaving out for now.
       log/log.c
)

target_include_directories(log SYSTEM # System required for bugs in headers see below.
    PUBLIC
         include
)

target_compile_definitions(log
  # Note all public since used in headers only, but if only used in underlying c files they would be private.
   PUBLIC
        CONFIG_LOG_DEFAULT_LEVEL=${LOG_DEFAULT_LEVEL}
        CONFIG_LOG_MAXIMUM_LEVEL=${LOG_MAXIMUM_LEVEL}
        CONFIG_LOG_COLORS=${LOG_COLORS}
        CONFIG_LOG_TIMESTAMP_SOURCE=${LOG_TIMESTAMP_SOURCE }
)

target_compile_options(log
    PRIVATE
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-cast-qual>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-declaration-after-statement>
        $<$<COMPILE_LANG_AND_ID:C,Clang,GNU>:-Wno-implicit-function-declaration>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-implicit-int-conversion>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-missing-prototypes>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-padded>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-pointer-arith>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-shorten-64-to-32>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-sign-conversion>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-unused-macros>
        $<$<COMPILE_LANG_AND_ID:C,Clang,GNU>:-Wno-unused-variable>
        $<$<COMPILE_LANG_AND_ID:C,Clang>:-Wno-zero-length-array>
)

target_link_libraries(log
    PUBLIC
        idf::sdkconfig
        idf::esp_rom
    PRIVATE
        idf::esp_common
)

I've found new pain points which bug me...

ESP-IDF and the whole component thing ignores CMake's target_compile_features.
The component manager ignores global compile options.

This leads to situation where I have to specify the C++ standard I'd like to use twice. Once globally with add_compile_options to satisfy "non-component" libs and once with target_compile_options to satisfy ESP-IDF components...


Moves and fixes RPhenoscape vignette so it renders

This moves the RPhenoscape vignette to using 01_ as a prefix, resulting in it getting rendered first. Otherwise, pkgdown::build_site() doesn't get to it because the PARAMO vignette fails (#3).
Also fixes it up by including the library(rphenoscape) command, as otherwise all the package's function would need to be prefixed.

FYI @wdahdul.


Why are Objects and Arrays Stringified? -- Can't properly access data in GraphQL query

Hi,
I'm encountering a problem when I need to query data such as Objects and Arrays.
At line 34 of the plugin's gatsby-node.js is written:
https://github.com/storyblok/gatsby-source-storyblok/blob/185a8b67f8ea54b2ba5305247f57671e845e81dd/gatsby-node.js#L34
That creates the schema for fields_ such as fields_fieldname_string, fields_fieldname_number, fields_fieldname_boolean.
I need to access other types of fields such as field_fieldname_array and field_fieldname_object that are present inside the stringified content but not in the fields_ schema
I overcame this limitations by adding to the IF statement before, two more values to the array, in order to add that functionality in the plugin.
I can't find why this solutions is not provided by default, and if you are going to add it. It is needed.
Another question is: why do you stringify those types? What are the rationals behind?
Thx

The reason of stringifying those types is because Gatsby doesn't allow a JSON type.
See following issue in Gatsby:
https://github.com/gatsbyjs/gatsby/issues/8142#issuecomment-423832748
Gridsome, the equivalent framework in the Vue.js world has this type (See https://github.com/storyblok/gridsome-source-storyblok/blob/master/utils/create-schema.js#L21) so maybe opening an issue on Gatsby or making a PR on their repository will help us doing it without needing to encode the JSON to a string.

Thanks,
so you are saying, accordingly to Gatsby documentation, that is not possibile to replicate the GraphQL schema I get on the http://gapi-browser.storyblok.com/playground.
Example of my query and schema is:

So every kind of pre-selection I did, because I'll get only the stringified content, I will have to do it manually in the gatsby-node file, am I right?

Not sure if something has changed since this was first opened, but I just had a look at running this plugin locally in my Gatsby install and commenting out line 42 of gatsby-node.js, it still processes the data and it now makes all the content available via GraphQl and hasn't resulted in any errors.
Is this likely to cause issues with other data types other than my specific setup?
https://github.com/storyblok/gatsby-source-storyblok/blob/master/gatsby-node.js#L42
await Sync.getAll('stories', {
      node: 'StoryblokEntry',
      params: getStoryParams(language, options),
      process: (item) => {
        for (var prop in item.content) {
          console.log(item)
          if (!item.content.hasOwnProperty(prop) || ['_editable', '_uid'].indexOf(prop) > -1) {
            continue;
          }
          const objectType = Object.prototype.toString.call(item.content[prop])
                                                      .replace('[object ', '')
                                                      .replace(']', '')
                                                      .toLowerCase()

          if (['number', 'boolean', 'string'].indexOf(objectType) === -1) {
            continue;
          }

          const type = prop == 'component' ? '' : ('_' + objectType)

          item['field_' + prop + type] = item.content[prop]
        }
        // item.content = stringify(item.content)
      }
    })

This is really a major problem blocking common usages like displaying a preview of blog posts. In the official gatsby blog post https://www.storyblok.com/tp/gatsby-multilanguage-website-tutorial#build-a-multilanguage-navigation you fetch all blog posts and then filter is JS only few you need to just display preview... https://github.com/storyblok/gatsbyjs-multilanguage-website/blob/master/src/components/ArticleTeaser.js
  const { articles, authors } = useStaticQuery(graphql`
  query Articles {
    articles: allStoryblokEntry(filter: {field_component: {eq: "blogpost"}}) {
      edges {
        node {
          name
          full_slug
          content
        }
      }
    }
...
let article = articles.edges.filter(({ node }) => node.full_slug === blok.article.cached_url)

The desired solution would be to have the ability to fetch items data like this:
query HomePage {
  featuredBlogPosts { // this is the multi options stories entry
    name
}
}

cc @lisilinhart

@amykapernick's perfectly works for me. Can @onefriendaday or somebody else from Storyblok please give a statement on whether this can become a pull request or if there are any issues with this?
Especially as v2.0.0 has just been released a few days ago, such a breaking change would have perfectly fit into it.

Commenting out "item.content = stringify(item.content)" will lead to problems when you use a file type with the same name in multiple content types with different types. It will throw an error at the build.

I understand. Inline Fragments will probably help with that. If I find the time, I will work on a PR for this...

@onefriendaday could you give a more specific case where it fails? Based on your description I've tried to recreate the issue but can't. Thanks!

Hello @michelesketchin are you still having problems with this?

feel free to re-open this issue if it’s still on going


Bedrock client auto-configuration support external AwsCredentialsProvider and AwsRegionProvider

Re-write Bedrock BedrockAwsConnectionConfiguration to use AwsCredentialsProvider and AwsRegionProvider to manage Amazon Bedrock AI model connections.
With this change, Spring-AI will provide the capability to customize the AwsCredentialsProvider and AwsRegionProvider configurations. Also with this feature, Spring-AI has capabilities compatible with Spring Cloud AWS credential management.

Hi @wmz7year, thanks for taking a pick at this.
Before we start reviewing it i have to point that the <artifactId>spring-cloud-aws-starter</artifactId>  is not acceptable.
In fact no boot starter in a library code is ok.
So please cherry pick only the necessary minim of dependency.  Often the awspring starters will try to bring the entire AWS ecosystem into your project.

Maybe there is another solution for the compatibility between Spring-AI and Spring-Cloud-AWS.
Sprint AI defined connection properties in BedrockAwsConnectionConfiguration and created AwsCredentialsProvider in BedrockAwsConnectionConfiguration.
But currently, we don't use AwsRegionProvider to manage the region configuration.
So maybe we can keep the current BedrockAwsConnectionConfiguration and the other BedrockClients's auto-configuration conditions; maybe only check 'AwsCredentialsProvider' and AwsRegionProvider, not dependency with BedrockAwsConnectionProperties.
So this will be compatible with Spring-Cloud-AWS and not necessarily integrated with it.
How do you think about this, if this is ok I'll change the PR @tzolov

Hi @tzolov could you check this out again? I removed spring-cloud-aws dependency and provided new capabilities with custom AwsCredentialsProvider and AwsRegionProvider .

Thank you @wmz7year , PR LGTM


Grad is NaN

Hello,
Thank you for your great work.
While attempting to fine-tune the videomamba on my own dataset, I encountered some issues. When I chose a batch size of 4 and used two H800 GPUs for training, everything worked well. However, when I increased the batch size to 8/16/32, the loss looks great, but the gradients of the parameters became NaN, preventing the model from training.
Could you please provide some guidance on how to resolve this gradient issue when using larger batch sizes?

Hi! Can you use a smaller learning rate? Besides, maybe you can try to adapt the optimizer hyperparameters, such as β1, β2, ϵ = 0.9, 0.98, 1e-6.

Hi,
I'm facing the same issue. I've tried different learning rates, but I still get NaN occasionally.

Hi,
I'm facing the same issue.Have you solved it

Hi,
I'm facing the same issue.Have you solved it


Can't close edit button/link when logged in

I have the option to close the "No Issues Detected" notification in my map journal, but there's no "X" next to the "Edit" button/link.  This is less than ideal when demoing the map journal to others.

@brianshepard -- This is currently only an issue in Firefox.  If it's feasible for you to use Chrome for your demonstrations you'll be able to close the Edit button.


Keyboard Shortcuts should be dismisable by pressing the esc key

When opening the keyboard shortcuts via ? I want it to be dismissed when pressing the esc keybaord. I'm surprised this does not work. I think refined-github broke this since without the plugin enabled (incognito mode) this work.

I was gonna add it but apparently it can be closed with the same key you open it with: ?

Still we should also allow ESC since by default GitHub allows it too.

After you click the header of the shortcuts box it, esc will close it. It sounds like they expect that to work already, can you report it to GitHub?

Isn't this something that we (refined-github) destroy though? If I use GitHub without any extensions I can press esc and close the dialog regardless where I've clicked before.

Interestingly, esc already works with this modal on Safari. Seems like it might just be a bug in GitHub's code.


Fix for singularity module to properly run MPI

@pelahi can you just confirm these are the changes that were tested with the singularity/3.8.6-askap module?

The full propagation of this template through spack has not been tested but is difficult to test as I need the spack installed singularity. Should be fine.


Add group_by parameter to bm25 and hybrid

core PR: https://github.com/weaviate/weaviate/pull/4477

Codecov Report
Attention: Patch coverage is 58.44156% with 32 lines in your changes are missing coverage. Please review.

Project coverage is 94.99%. Comparing base (22d588a) to head (17f6863).

Files
Patch %
Lines

integration/test_collection_openai.py
20.00%
20 Missing :warning:

integration/test_collection.py
84.00%
4 Missing :warning:

weaviate/collections/queries/bm25/generate.py
40.00%
3 Missing :warning:

weaviate/collections/queries/hybrid/generate.py
40.00%
3 Missing :warning:

weaviate/collections/queries/bm25/query.py
80.00%
1 Missing :warning:

weaviate/collections/queries/hybrid/query.py
80.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##           dev/1.25     #978      +/-   ##
============================================
- Coverage     95.14%   94.99%   -0.15%
============================================
  Files           175      175
  Lines         17983    18050      +67
============================================
+ Hits          17110    17147      +37
- Misses          873      903      +30

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.